Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

With posting creation (Test run is not marked)

  • When the documents are created:

    • The document generated in each step is informed in field Comment

    • The 3rd step is split by cost element 60980*

Potential errors show up in RED in field Comment


Hide If
groupconfluence-users

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...)




Status
colourBlue
titleStep 1


Use transaction code:

Info

Page_title
: Initial Screen


Go to transaction Z1FZ1K_INTERNAL_MARGIN and fill the fields according to the screen on the right




Status
colourBlue
titleStep 2

When running the transaction in test mode there are some useful information that can be checked


  • Green line - The document that triggers the Internal Margin flow
  • Blue lines - The postings to be created in SAP




Status
colourBlue
titleStep 3

With posting creation (Test run is not marked) we can see:

  • The document generated in each step is informed in field Comment

  • The 3rd step is split by cost element 60980*



When attempting multiple executions for the same business case:

  • The field Comment informs that the postings have already been done


Potential errors show up in RED in field Comment





Status
colourBlue
titleStep 4

If necessary to reverse the transaction in Real Mode, the logic is the same.


Note
titleNote

The reversal is done for the for all the internal margin flows within the same company.