When performing a Journal Posting transaction to SAP, there are multiple options that allows you to configure the user that is performing the posting. This article summarizes those options.
Batch Input the following options are available:
To be able to run these options, the following Add-ons needs to be installed on the SAP System.
Also, both RFC User and Credential are mentioned on this article. The RFC User is defined at the SAP System level on your connection, while a Credential is an independent entity that can be used to authenticate to an external system when executing a job.
In the following context, a Credential always takes precedence to the RFC User.
A Step User or SAP User can be defined on a per-job basis to modify the above behavior. This will be outlined below. This user is defined on the parameter SAP_USER_NAME.
BDC Posting
This posting mode leverages BDC to make the actual posting to the SAP system. This implementation was prior to BAPI posting (which is now preferred). Nevertheless, BDC posting is still available due to particular security requirements.
*BDC posting failures result in interruption of the Posting displaying a single error. This is a key difference to BAPI posting where a complete list of errors is returned, which can ease the testing process.
>BDC< / >CALL_TRAN<
>BDC< is used to create a new Batch Input in SAP under the RFC User or a Credential. The batch input is not executed when using >BDC<
Module called: /JCS/BC_BDC_MAP_STORE
>CALL_TRAN< creates the batch input in memory and also executes it. If an SAP User is specified, it is only used for validation, but the posting is done by the RFC User or credential.
Module called: /JCS/BC_BDC_MAP_EXEC
>CALL_USER<
Involves executing Batch Input, but then under the SAP User defined in the parameter SAP_USER_NAME.
Module called: /JCS/BC_BDC_MAP_EXEC_USER
Implemented in : ROSO-9691 - 9.2.9
BAPI Posting
Bapi posting is a transaction method that leverages different BAPI's to perform the posting. When using the transport, the BAPI calls are done to modules under the /JCS/ namespace.
BAPI calls need to do an AUTHORITY_CHECK as validation at the beginning of the execution.
>CALL_BAPI< / >CALL_CHECK<
>CALL_BAPI< Involves executing BAPI posting under the RFC User or a Credential User, where CALL_BAPI performs an actual posting (if everything is validated successfully)
>CALL_CHECK< performs a simulation posting, under the above conditions
If an SAP User is specified, it is only used for validation, but the posting is done by the RFC User or Credential.
>USER_BAPI< / >USER_CHECK<
>USER_BAPI< leverages BAPI posting using the SAP User defined in the parameter SAP_USER_NAME.
>USER_CHECK< performs a simulation posting, under the above conditions
Implemented in: ROSO-9884 - 9.2.10
Comments
0 comments
Please sign in to leave a comment.