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: 

: Initial Screen


See how to solve possible errors in step 4.


Enter the transaction in the SAP command field: 

 

Next screen opens: 



Select the applicable variant. 

Click on  

Next screen show up: 

 

Select  .

Search for Variants and select the Variant of your team - are for:

  • 3S-DACH-NL-UK
  • 3S-UK CH-PL
  • 3S_BE_FR
  • 3S_IB_IT
  • 3S_SOLEXIS_US 




Each variant have all the companies in the team scope with the current Fiscal Year and with the Processing Status "Complete" marked with and X. 

(will be reviewed by Vasco)

worddav83f87b4b298020a11d9b402b22712191.png




Post the documents that were parked

Run the transaction  . 

You get the next screen: 

Click on "select all"  . 

Click on save  to post all documents. 

You get the next screen: 

The system posts all documents that were parked. Normally the documents have been saved as "complete" don´t create errors, except if the period for the posting is closed. 
If some errors appear, the system gives us the reason of the reject.

You can see next an example: 

Rejected documents have to be corrected by local accounting before end of the month using transaction FBV2.

If the period is closed when the FBV0 is performed, the system will give the following message:

 

In this case, there are 2 options:

  • Modify the period. It may only be done after analyzing the impact on the closure with the SBS Team leader and the local accounting.
  • Post the document in the following period after agreement of the local accounting. (See 4.4.2) 



Solve errors, if necessary






In case of inaccurate data in the parked document the "Complete" status should be removed in order to avoid the posting of the document by other users. 


Enter the document by double clicking the document in transaction "FBV0" and "Parking" the document as shown in the pictures:

worddav6b7cc3883eefe680be86d4d8262b320b.png

worddave54707de5e48862fdb1b3e7497259b5c.png

SBS informs the author of the parked document (via ticketing) that the document must be reviewed. 


If the parked document with posting date in month "m" has to be posted in the period "m+1", the FBV0 has to be performed as follows: 

Select the document: 

worddav6b7cc3883eefe680be86d4d8262b320b.png

Next go to "list" and select "create batch input": 

SAP will gives you the following message: 



Run the transaction SM35 and select the line corresponding to the session that you create before with your user. 

Process  and select "process/foreground" and do  . 

The next screen opens: 

Change the document date and the posting date, entering the 1st day of the following month. 

"Enter" (on each screen as long as the document is posted) see documentation regarding transaction SM35.


In case you get the following error message, you can´t post the parked document directly. 

 


The solution is to create batch input and process it on SM35 – display errors only. 
Select the related item:

 


Create the batch input session.

 

In SM35, select the batch session created and processes it with "display errors only" option.

Press Enter, until doc is posted.