on 2007 Sep 10 7:22 AM
Hi all,
what is LO mathod...........what is the difference between them..........
What V3 update process.
Thanks in advance,
Regards,
Bhaskar
Hi Bhaskar,
V3 is an update mode.... that means.. LO supports V3 update mode.... V3 -> Asynchronous Background Update Method Here by seeing name itself we can understand this. I.e. it is Asynchronous Update Method with background job.
-
A.Direct Delta:- In case of Direct delta LUWs are directly posted to Delta Queue (RSA7) and we extract the LUWs from Delta Queue to SAP BW by running Delta Loads. If we use Direct Delta it degrades the OLTP system performance because when LUWs are directly posted to Delta Queue (RSA7) the application is kept waiting until all the enhancement code is executed.
B.Queued Delta: - In case of Queued Delta LUWs are posted to Extractor queue (LBWQ), by scheduling the V3 job we move the documents from Extractor queue (LBWQ) to Delta Queue (RSA7) and we extract the LUWs from Delta Queue to SAP BW by running Delta Loads. Queued Delta is recommended by SAP it maintain the Extractor Log which us to handle the LUWs, which are missed.
but LIS does't supports this V3 update mode..so, every one preffered LO only...
regards
@jay
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
LIS Extraction is Based on Information Structure.
Create Field Catalogs (MC18) Similar to Info Object Catalog.
Create Information Structure (MC21) Similar to info Cube.
Set up the Update Rules (MC24) Similar to Update rules.
Goto T-code LBW0.
Give the Information Structure Name
See the Present Setting for the Information Structure
( IF Datasource is not generated )Generating the Data Source
Deactivating the Delta Update LBW1
Do the changes to the updating and Save it
Running the Statistical setup to fill
the data into Information Structure
Goto SBIW and follow the path
Version Maintenance :
Normally it is 000 version So load the data to version &(A and copy the data from this version to 000
Date of Termination :
Date of termination to be in past
Click on Execute
We can cross check using RSA3
Copy the data from the version &(A to 000 using LBW2
Using RSA6 transport the Data Source
Replicate the Data Source in SAP BW and Assign it to Info source and Activate
In SAP R/3 Goto LBW1 and set the updating to No Updating and Save
Go Back to SAP BW and Create the Infopackage and run the Initial Load
Once the Initial delta is successful before running delta load we need to enable delta updating in SAP R/3
Once the Delta is activated in SAP R/3 we can start running Delta loads in SAP BW.
LO Extraction
First Activate the Data Source from the Business Content using LBWE
For Customizing the Extract Structure LBWE
Maintaining the Extract Structure
Generating the Data Source
Once the Data Source is generated do necessary setting for
Selection
Hide
Inversion
Field Only Know in Exit
And the save the Data Source
Activate the Data Source
Using RSA6 transport the Data Source
Replicate the Data Source in SAP BW and Assign it to Info source and Activate
Running the Statistical setup to fill
the data into Set Up Tables
Goto SBIW and follow the path
We can cross check using RSA3
Go Back to SAP BW and Create the Infopackage and run the Initial Load.
Once the Initial delta is successful before running delta load we need to set up V3 Job in SAP R/3 using LBWE.
Once the Delta is activated in SAP R/3 we can start running Delta loads in SAP BW.
Update Methods
Serialized V3 Update
Direct Update
Queued Delta
Non Serialized V3 Update
Serialized V3 Update:Since the V3 update actually does not recognize the serialized processing of update data, the Serialized V3 Update function was created through several corrections in SAP Basis in order to also be able to serialize
The serialized V3 update can only ensure the correct sequence of extraction data for a document if the document is not repeatedly changed within the span of a second.
Furthermore, the serialized V3 update can only ensure the correct sequence of extraction data for a document if the times are permanently and exactly synchronized for all instances in a system. This is because the creation time of the update record, which is determined by the local time for the application server, is used for sorting the update data.
In addition, the serialized V3 update can only ensure the correct sequence of extraction data for a document if it previously had no errors in the V2 update. This is because the V3 update only processes the update data that is successfully processed with the V2 update.
Independently of the serialization, update errors that occur in the V2 update of a transaction and which cannot be reposted have the consequence that the V3 updates for the transaction that are still open can never be processed. This can thus lead to inconsistencies in the data in the BW system.
Hope it will helps you...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Bhaskar ,
<b>LIS</b> is old technique through which we can load the data. Here we use typical delta and full up-loading techniques to get data from an logistics application, it uses V1 and V2 update, it means that it was a synchronous or asynchronous update from the application documents to LIS structures at the time when the application document was posted.
<b>LO Cockpit</b> is new technique i think from bw 3.0 ( i am not sure) which uses V3 which is an update that you can schedule, so it does not update at the time when you process the application documents, but it will be posted at a later stage.
<b>Another big difference between LO and LIS is that,</b>
You have separate datasources for header level, item level and schedule line level available in LO, you can choose at which level you want to extract your data and switch off others, which results in reduced data.
we do not have this flexibility with LIS structures with Plug-In 2001.2 S2xx-Structures have been replaced by Logistics Extraction Cockpit. However, R/3 releases 4.x support S2xx-Structures and Logistics Extraction Cockpit in parallel.
With new LBWE extractors there are a lot of benefits:
- Detailed Extraction: extraction can be deactivated (e.g. Schedule Line Data) leads to leaner extractors with less volume.
Document Changes: only BW-relevant data changes will be updated (less upload volume).
- LIS-Tables are not updated reduced data volume due to avoided redundancy.
- Update with Batch-Process (V3) -> no load on daily business (but now there are available different delta methods as the direct delta...)
- No LIS-Know How necessary.
- Functional Enhancements easy to be done.
- Central, uniform maintenance tool for logistics applications (LBWE)
- No Delta-Tables (SnnnBIW1/-2) no double update, no double Data-Storage
- A lot of flows are covered: Purchasing,Inventory Controlling, Shop Floor Control, Quality Management, Shipment, Sales, Shipping, Billing, Plant Maintenance, Customer Service, Retailing.
Blogs by Roberto on LO,
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1522. [original link is broken] [original link is broken] [original link is broken]
/people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146
/people/sap.user72/blog/2004/12/23/logistic-cockpit-delta-mechanism--episode-two-v3-update-when-some-problems-can-occur
/people/sap.user72/blog/2005/01/19/logistic-cockpit-delta-mechanism--episode-three-the-new-update-methods
regards
@jay
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
70 | |
10 | |
10 | |
7 | |
6 | |
6 | |
6 | |
5 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.