Quick: 3] Price list with release status

 Report name: Price list with release status

>> Field Mapping validation

Extra Field:

1) load_date

2) RELEASE_STATUS

fiels under A006

PL_SALES_ORG_ID 

PL_DISTRIBTN_CHANNEL_ID

PL_PRICE_LIST_ID

PL_CnTy

PL_MATERIAL

PL_VALID_START_DATE

PL_VALID_END_DATE

>> Join validation

join name: A006 Pricing Master

Fix: Implement explicit JOIN to A006 table on appropriate keys

join name: KONP Pricing Conditions

Fix: No Fix Required

join name: TCURR Currency Conversion

Validation Review of Your Comment: NOT JOINED; FDD documents detailed conversion logic

In your code:

No TCURR table is used

No exchange rate logic exists

Amount is directly taken from salesorders

Why this Fails

code:

CAST(so.Rate AS decimal(17,2)) AS `PL_List Price Amount`
so.rate_unit AS `PL_Unit_CURRENCY`

This means:

• Amount is in original transaction currency

• No conversion to reporting currency

If your dataset contains:

Currency	Amount
USD	100
EUR	100
INR	100

Your report will treat them as equal 
Which is financially incorrect

Proper TCURR Join Logic

code:

ON source_currency = TCURR.FCURR
AND target_currency = TCURR.TCURR
AND TCURR.KURST = 'M'
AND document_date BETWEEN TCURR.GDATU range

>> Filter Validation

Filter name: Release Status

Fix: AND so.RELEASE_STATUS IN ('RELEASED', 'ACTIVE')

Filter name: Validity Date Range (Start)

Fix: depend on A006

Filter name: Validity Date Range (End)

Fix: 

>> Derived Field

Field name: Currency Conversion (Multi-step)

Fix:

Field Name: Release Status Display

Fix:

>> Data Quality Check:

DQ-01: Transactional Currency

DQ-02: Company Code Currency

DQ-03: Group Currency Conversion

DQ-04: Indirect Currency Path

DQ-05: Price List Release Status

DQ-06: Historical Data Retention

DQ-07: Date Validity Check

Fix : Pending

>> Action items