Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
cancel
Showing results for 
Search instead for 
Did you mean: 
Former Member
0 Kudos

Issue: Even when Deletion Indicator is marked for a PO Item in P20, the same is not reflected in BW via delta/full repair loads.

Data Source:2LIS_02_ITM,

Note: Field LOEKZ of table EKPO is the deletion indicator for an item in P20. It is mapped to BW fields 0DEL_FLAG and 0ITEM_DEL via direct assignment.

Root Cause: If a PO Item in P20 is not statistically relevant, the value for LOEKZ field will not be extracted by the extractor:2LIS_02_ITM, instead if a non statistical PO is marked for deletion in P20, then the record mode=’R’ will be generated for that particular record and LOEKZ field will not be populated .

Note: PO Items are statisticaaly relevant  when it has a purchasing order history (goods receipt, invoices, etc.), and/or has the final delivery flag set, and/or has the final invoice flag set.

Solution: For any non statistical PO the field /N42/S_PODELIND is populated as 1. This is due to the following code written in the end routine of transformation 2LIS_02_ITM->/NSN/MM0_D16 as below.

In this code, when ever there is an update mode=R ( ROCANCEL = R), the field /N42/S_PODELIND is getting populated as 1. Thus, the field /N42/S_PODELIND (PO Deletion Indicator) is marked whenever a line item is deleted for a non statistical PO.

Hence, if the flag /N42_S_PODELIND/0DEL_FLAG is marked in BW system , it refers to the deletion of that particular line item of a PO.

Conclusion: While checking in BW, whether a PO Item has been marked for deletion or not, both fields 0DEL_FLAG and /N42/S_PODELIND should be considered.

2 Comments
Labels in this area