What Are The New Update Methods Since P12002?

1.	What Are The New Update Methods Since P12002?
Answer» a. DIRECT delta — data is transferred to BW delta queue for each document posting; useful for low volume CUSTOMERS. b. queued delta — extraction data is collected for the affected application instead of being collected in an extraction queue; serialization is ensured; for large volume customers . c. non serialized V3 UPDATE — the data in the updating run are read without regard to the SEQUENCE from update TABLES. a. direct delta — data is transferred to BW delta queue for each document posting; useful for low volume customers. b. queued delta — extraction data is collected for the affected application instead of being collected in an extraction queue; serialization is ensured; for large volume customers . c. non serialized V3 update — the data in the updating run are read without regard to the sequence from update tables.

Answer»

a. DIRECT delta — data is transferred to BW delta queue for each document posting; useful for low volume CUSTOMERS.
b. queued delta — extraction data is collected for the affected application instead of being collected in an extraction queue; serialization is ensured; for large volume customers .
c. non serialized V3 UPDATE — the data in the updating run are read without regard to the SEQUENCE from update TABLES.

a. direct delta — data is transferred to BW delta queue for each document posting; useful for low volume customers.
b. queued delta — extraction data is collected for the affected application instead of being collected in an extraction queue; serialization is ensured; for large volume customers .
c. non serialized V3 update — the data in the updating run are read without regard to the sequence from update tables.

Discussion

No Comment Found

Related InterviewSolutions

I Encountered An Issue While Executing An Ess Employee Leave Request (ws20000081). To Explain Further, When An Employee Creates A Leave Request Through Ess, It Goes To His Manager. If The Request Is Logon To R/3 And His Manager Approves The Leave Request Through The Same R/3 Workplace, The Request Goes Back Out From That Screen. This Scenario Works Fine. However, The Problem Starts When I Do The Same Request From His Manager's Portal And I Press The "approve" Button, I Get The Message Saying "information Sent Successfully". I Will Then Press The "ok" Button, And Then Press The Button "quit". When I Double Checked, The Workflow Is Still Sitting At The Manager's Inbox. My Question Is Why Doesn't This Work From The Manager's Portal When The Same Function Is Working Inside The R/3?
Is There Anyway To Undelete Work Items In Sap Workflow After I Have Logically Deleted Them Already?
How Do You Set Up A User To Receive A Pop-up Reminder When He/she Gets A New Wf Message?
Is It Possible To Create Timed Events?
How Do You Set The Workflow In The Transaction Pb40 Of Hr For Functional Mobility?
I Am Currently Using A Standard Task Ts 00008314 (bus2038) To Launch Work Flow When Notification Is Created. Given This, How Can I Define Notification Type (only M1)? Subsequently, How I Can Launch A Pop Up Or Express Message When Notification Is Created?
Is It Possible To Download My Workflows?
It Is A Policy In Our Company That The Security Department Extends The User Validity Period Of Each User Id Every Year End I.e. From 12.31.2005 To 12.31.2006. We Have To Do This Manually Every Year And This Year, I Was Trying To Find Out How To Assign The Validity Period To A Much Later Date Than The Usual Annual Cut Off. Is There A Better Way To Configure This Without Going Through Each User Id Manually?
Is It True That Workflow Is Position Based And Not Person Based? Does It Mean That When A User Quits A Job, The Workflow Will Not Be Affected?
I Have Created A Situation Wherein The 'z' Object In 'swo1' Was Transposed To 'obsolete' By Mistake. After This, I Am Not Able To Edit The Object Anymore. This Message Appears Each Time I Try To Delete The Obsolete Misstep: "obsolete Object Types Cannot Be Changed Again." How Can I Reverse The Mistake?