Tasks to be completed when documenting an SAP Transaction, Report or Message code.

 1. Title of the page = SAP Transaction code, SAP Report or SAP Message

2. Add the following Labels, respectively : 

    • SAP Transaction => "sap_transaction", Transaction code "xxxx"

    • SAP Report => "sap_report"

    • SAP Message => "sap_msg"

3. On the left section, describe the steps. On the right section, insert respective print screens and additional guidelines, if needed (e.g. Main selections of the transaction...)




Use transaction code: ZWFA15P


: Initial Screen








Go to transaction ZWFA15P, select the variant of the company code to be analyzed (for example for ZFR3, choose ZFR3_CLOSING) and Validate  and select the corresponding company.

Document Type:

  • WA: Goods issue
  • WL: Goods issue/delivery

Movement Code:

  • 453 : TP returns to own
  • 454 : TP own to returns
  • 457 : TP Returns to own QI.
  • 459 : TP Ret. to own blckd.
  • 460 : TP Own blckd to ret.

TP: Transfer to company's own stock





The outcome of this report allow us to compare COGS amount in FI and in COPA and find out where do discrepancies come from : 

  • The material master record (if the material has a Standard Cost Estimate)
  • The invoice whose number appears on this report
  • The order




All differences by material should be analyzed in detail and corrected, according to this file.



A check by plant/material can be done after corrections have been applied. The file FI COPA CONTROL.xlsm gives an example of the report. The corrections are recorded in the FI column in the KE30 report ZZZ-SOLV01.


  • Manual Postings in account 98350050 with cost center XXXX-9200 (XXXX stands for company code);
  • Manual Postings in COPA derivation accounts 98154199, 98258199 and 98254199;
  • MR11 postings in account 98150363 (documents beginning with  48*).

At the end of the analysis and correction process, the gap should be equal or near 0.