In SAP BW/4HANA you realize that standard content data Source (New GL Balances) is delivering incorrect values into the first persistent data layer in SAP BW/4HANA. Which options do you have to…

Question

Options

• ACheck entries in table RSDDSTATEEXTRACT in SAP ERP
• BUse program RODPS_REPL_TEST in SAP ERP
• CUse PSA maintenance in SAP BVW'HANA
• DUse transaction RSA3 (Extractor checker) SAP ERP

• A
  10% (3)
• B
  77% (24)
• C
  13% (4)

Explanation

When troubleshooting an extractor issue delivering bad data into BW/4HANA, the critical constraint in the question is "in the SAP ERP source system" - both correct answers are tools that run directly on ERP, where the extraction logic lives.

Why B and D are correct:

• RSA3 (Extractor Checker) is the classic transaction in SAP ERP for simulating a DataSource extraction, letting you inspect raw values at the point of extraction before any BW transformation occurs - ideal for confirming whether the issue originates in ERP.
• RODPS_REPL_TEST is a program in SAP ERP used to test ODP (Operational Data Provisioning) extractors, which is the modern framework underlying standard content DataSources like New GL Balances - it lets you simulate the replication and validate the data being sent.

Why A and C are wrong:

• Table RSDDSTATEEXTRACT is a BW-side table tracking extraction state/request metadata, not an ERP object - and it reveals when data was pulled, not what the extractor logic returned.
• PSA maintenance exists in BW/4HANA (the receiving system), not in ERP, and BW/4HANA largely replaces PSA with ADSOs anyway - it can show what arrived in BW but cannot diagnose the ERP extractor itself.

Memory tip: Extractor issues → go to the source. RSA3 = "check what ERP is extracting"; RODPS_REPL_TEST = "test the ODP pipeline from ERP." If the tool lives in BW/4HANA, it's already one step too late to diagnose the root cause.

No community discussion yet for this question.