Deletion of PO in 2LIS_02_ITM

[Former Member]

Hi

can any one explain me on How the cancellation of Purchase order that is extracted to BW using 2LIS_02_ITM Data Source

If a PO is cancelled in ECC how does it is going to avaliable in BW when extracted using 2LIS_02_ITM

Thanks in advance

[dennis_scoville4 · Accepted solution]

If a PO is cancelled or flagged for deletion in R3/ECC, the extractor will know that this change in the record has been performed and will send the record to BW with a value of X (cancellation) or R (flagged for deletion) in the ROCANCEL field.

In the Transformation, the ROCANCEL field on the DataSource would be mapped to 0RECORDMODE. During the load process, the record that already exists in the target DSO will be removed. Further up the flow, however, the record will be loaded into the InfoCube and both the original record and the cancellled/flagged for deletion record will exist until the requests that have loaded both records have been compressed with zero elimination.

There is a caveat that I feel I should warn you about...If a record is phyiscally deleted in the source SAP application, it will not be extracted for deletion in BW because the R3/ECC delta processes have no way of knowing that the physical deletion of record has been done. In those cases, you would be left with "orphan" records and will have to create a custom solution or devise a process to re-sync your data on a periodic basis.

[Former Member · Accepted solution]

Thnk you so much... it was a great help to handle one of the major escalated issues pertaining to the same issue that deleted PO's are not getting removed from the list of open PO's