1. Run RSA3 to check if there is any data available related to your data source (eg.

2LIS_02_ITM):

2. If data is there in RSA3, then go to Tcode LBWG to delete the setup table content by entering the application name. (eg. 02 for Purchasing). If no data is available in RSA3, go to step 3.

Confirm the deletion:

3. Got o Tcode SBIW and select Logistics Application

4. Go to LO Customizing Cockpit (Tocde: LBWE) and select Purchasing

5. Deactivate the extract structure

6. Click OK in transport request window. (If no transport# is available, create a new request for it)

7. Maintain the extract structure (left side) and select the fields of your choice from Communication structure (right side):

8. Select a transport in the transport request window. If necessary, create a new one for it.

choose a development class (eg. Z001) and save.

Click OK to continue

Click OK in the message window to continue:

Procedure Now choose the maintenance screen of the DataSource. After that, the status display (traffic light) jumps from red to yellow. Please make note of the following before you transport the changed structure MC02M_0ITM into another system: o Run the transport when the target system is not being booked. Otherwise you will need to initialize it because documents are lost during this time. o None of the clients in the target system in the V3 update for the application 02 should contain data. If you are unsure, start the V3 update of the application 02 in all clients. o If there is still data in the central delta management of the target system, it must be retrieved by BW before the transport takes place. o If you have already reconstructed within this target system, it may be that the data still exists in the reconstruction tables. After the transport, you can no longer transfer these entries into BW. You must delete the contents of the reconstruction tables of the application 02 in the target system and run another reconstruction if need be. o If there is an update log in the target system, you cannot read the log data of the application 02 after the transport has been run. You can only read it again once data is booked and the last log entry overwritten. Use the report RMCSBWCC to display a log for the changed extract structure in the target system, to see if any of the above problems exist. An additional switch deletes all update logs for the application of the selected extractor. Please also note that you must reactivate the transfer structures when you change the extract structure after replicating a DataSource. 9. Active the DataSource for this extract structure.

10. Give the transport request number and continue.

11. Choose Selection and Hide fields and Save

12. Activate Updating.

You have activated the extraction of an extraction structure. By setting the V3 update to active for the affected application, update entries that contain "collective processing" modules are created for every document change. These cannot be processed automatically either immediately or later, as is possible for a V1 or V2 update. You have to start the process for these update entries explicitly. For logistics extraction, you can set the time that you want to begin the explicit start- up using the function "Job control". If changes are made to the ABAP dictionary objects used in the update module between the time of creating an update entry and the V3 update process, the update entries can no longer be updated and an update termination ensues. In this situation you can only delete the update entry. The data belonging to it is lost. If you chose the update mode 'Queued Delta' for the affected application, whenever a document change is made, entries are generated in an extraction queue.

These entries are not processed automatically. You have to explicitly trigger processing of these entries in the extraction queue. For logistics extraction, you can set the time point for this explicit start-up using the Job Control function. If changes are made to the ABAP dictionary objects used in the module between the time when an entry is generated in an extraction queue and the processing of this entry, this queue entry can no longer be processed, and causes a runtime error. If this happens, you can only delete the queue entry - the data that belongs to it has been lost. Procedure You must inform your system administrator about this, so that they can ensure in the future that no open update entries or entries in the extraction queue (under Log.-Queue Overview in the system before the following activites are performed: o R/3 support package import o R/3 Upgrade o PlugIn support package import o PlugIn Upgrade 13. Fill in setup table. (Back to Tcode SBIW, and select the program for your module. Eg. Purchasing)

14. Give a new name for the run and execute the program to fill in setup table

15. Go to Tcode RSA3 to check data in setup table

16. Go to BW to replicate the data source.

17. Create infoPackage for initialization and schedule the job.

18. Go to R/3, and run LBWE to setup delta update mode

select update mode

If you select Direct delta, jump to step 20. 19. Schedule V3 job to collect delta records

Configure the Start Date, and schedule the job

click Start date and setup periodic job and save

Click Schedule job. And monitor the job by clicking Job Overview

Press F5 to see the details of this job.

20. Input new PO using Tcode ME21N

Ignore the warning message and click save.

21. Check the new POs in RSA7. Select the Data Source (eg. 2LIS_02_ITM) and then click Display icon.

Click Run to see the content in delta queue.

22. Go to BW, create a new infoPackage for delta load.

Confirm to continue.

23. Schedule the delta infoPackage to load the new POs. from R3.