Purchasing
Link for information in help.sap.com
Information from SAP content
Datasources
Setup Table Structure : MC02M_0(HDR)SETUP
Deleting Setup tables : LBWG - Application : 02
Setup Table deletion job name : RMCSBWSETUPDELETE
Setup Table Filling Job Name : RMCENEUA
Filling setup tables : OLI3BW
Points to Remember
- Purchasing Extractors do not bring records which are incomplete. i.e. EKKO-MEMORY = 'X' - Incomplete.
- PO Item marked for deletion in ECC but the same is not reflecting in BW via delta/full loads. Click HERE
EKKO
EKPO
EKBE
EKKN
Transactions
ME23n
ME2L ( Account Assignment )
2LIS_02_ITM
In LBWE, it says EKKO-SYDAT but it is from EKPO (*)
2LIS_02_ACC
Base Tables
EKKO - Header
EKPO - Item
EKKN - Account Assignment in Purchasing Document
2LIS_02_ACC- NETWR
Even though the extract structure shows EKKN as the base table for this field, it is actually calculated using a formula ( Check SAP notes Link for more )
For documents with specified purchase order quantity, such as purchase order documents, the net purchase order value is calculated as follows:
NETWR = EKPO-NETWR / EKPO-MENGE * EKKN-MENGENet purchase order value = Net purchase order value of item / Item quantity * Quantity posted to account
For documents with target purchase order quantity, such as contracts, the net purchase order value is calculated as follows:
NETWR = EKPO-ZWERT / EKPO-KTMNG * EKKN-MENGENet purchase order value = Target value of item / Target quantity of item * Quantity posted to account
In the extractor structure value of LOEKZ is from EKPO but there is no data coming from the extractor. LOEKZ is passed to ROCANCEL internally and if ROCANCEL is mapped in the DSO, those items are deleted as LOEKZ is deletion indicator. If you need LOEKZ value, fetch it in the enhancement in a zfield.
SAP Notes Link
https://help.sap.com/saphelp_nw70/helpdata/en/f3/487053bbe77c1ee10000000a174cb4/frameset.htm
No comments:
Post a Comment