BW extractor 2LIS_02_SCL showing different results for REEWR and DMBTR

[LanderVantomme]

Hi,

I'm trying to report on purchase price evolution, based on the 2LIS_02_SCL BW extractor. For some particular cases, this extractor is showing wrong invoice prices.

BWGEO is filled in using one of these formulas: 

1. Invoice Qty * Invoice Value / Total Invoice Quantity
2. EKET-MENGE * EKBE_DMBTR / EKBE-MENGE

The result for both of these formulas is different for one particular case though, because Invoice Value (REEWR) and Amount in Local Currency (DMBTR) contains different values as you can see here: 

Situation is that the GR was done on the PO, then IR at wrong price, then reversal of the IR + new IR with the correct price. BWGEO in the extractor is showing a price of 101.23, which is totally incorrect.

Anybody knows where

1. the value in REEWR is coming from or
2. how we can assure that this calculation is based on the DMBTR value?

Thanks!

[vishalakshmi]

REEWR (Cumulative Receipt Value):

This field usually reflects cumulative values for receipt quantities or values in purchasing.
It is typically sourced from tables such as EKET (Scheduling Agreement Schedule Lines) for scheduling agreement data.
The cumulative values can also be derived from the aggregation of data from the MSEG (Document Segment: Material) table which records material movements.

DMBTR (Amount in Local Currency):

This field indicates the amount in the local currency.
The primary table for this data is the EKPO (Purchasing Document Item) table, where the local currency amounts for purchase order items are maintained.
For goods movements, DMBTR values are recorded in the BSEG (Accounting Document Segment) table, which stores the financial document data.

REEWR (Cumulative Receipt Value): This field is usually accumulated from the values of goods receipts (GRs) and invoices received (IRs). It is supposed to reflect the total value received against a purchase order or schedule line.

DMBTR (Amount in Local Currency): This field reflects the value of transactions in the local currency, and it is directly sourced from financial postings and invoice entries.

Analyzing the Specific Case:

Initial GR and IR: When the goods receipt is done, the system updates the REEWR and DMBTR with the received quantity and value.
Incorrect IR and Reversal: If an invoice is posted at an incorrect price, it affects REEWR. When this invoice is reversed and a new one is posted, ideally the system should correct REEWR to reflect the accurate cumulative value.
Discrepancy in Calculation: If there’s a discrepancy in REEWR and DMBTR values due to incorrect IR postings and reversals, the calculated BWGEO will be incorrect.
Ensuring Correct Calculation
To ensure that the calculation is based on the DMBTR value, you can take the following steps:

Investigate Table Data:

EKET: Check the quantities and values in the schedule lines.
EKBE: Analyze the history of goods movements and invoice receipts. Look for any anomalies or incorrect postings.
BSEG: Verify the accounting entries to ensure they reflect the correct amounts.
Adjust Extractor Logic:

Custom Logic for BWGEO: You may need to adjust the logic in your extractor to prioritize DMBTR over REEWR for calculating BWGEO.
Formula Adjustment: Ensure the calculation formula explicitly uses DMBTR for deriving the invoice price.
ABAP
Copy code
BWGEO = EKET-MENGE * EKBE-DMBTR / EKBE-MENGE
Data Consistency Check:

Ensure that the data in ECC (ERP Central Component) tables (like EKET, EKBE, and BSEG) is consistent.
Implement consistency checks in your data extraction routines to flag discrepancies.
Technical Implementation
Enhancement Spot in Extractor: Implement an enhancement in the 2LIS_02_SCL extractor to ensure it uses DMBTR for the BWGEO calculation.

ABAP
Copy code
IF <some_condition>. " Check if the scenario matches the problematic case
BWGEO = EKET-MENGE * DMBTR / EKBE-MENGE.
ELSE.
BWGEO = REEWR / EKET-MENGE. " Default calculation
ENDIF.
ABAP Debugging: Use ABAP debugging tools to step through the extractor logic and ensure that it’s correctly fetching and calculating the values.

Please focus on calculations.