Introduction :
SAP Profitability and Performance Management (PaPM) Remote Function Adapter offers you the capability to post your results directly to SAP S/4 HANA, eliminating the extra steps of
- Downloading results from SAP Profitability and Performance Management (PaPM) and uploading the same into SAP S/4 HANA. OR
- Writing the result to a SAP Business Warehouse ADSO and then using the BAPI (BAPI_ACC_DOCUMENT_POST) which requires customizing the BAPI and enhancing ABAP logic
The RFA Finance Accounts Payable function type (RFA FI-AP), allows you to post your SAP Profitability and Performance Management (PaPM) calculations to SAP S/4 HANA (in BSEG, BKPF and ACDOCA tables). It uses the standard SAP accounting interface BAPI_ACC_DOCUMENT_POST,
This helps you in, mass posting of SAP Accounting Documents as opposed to creating individual entries using the standard SAP transaction code (like FB60 – used for Vendor Account document posting).
Solution :
The Fields in the input function should be mapped to the components of the RFA Function Type. The input function requires at least
- “GL Account”
- “Account key” (also known as Transaction Key)
- Amount in Document Currency (GL)
- Amount in Document Currency (Payable)
The above two Amount fields should have entries for each side (debit and credit)
Since the RFA FI-AP uses standard accounting interface (BAPI), the inputs are validated against standard SAP Financial Accounting (SAP FI) validation rules, the posting will happen once all the fields are successfully validated.
Example – In the Function type RFA FI-AP, you have defined a certain GL account that requires a transaction key then you need to supply a valid transaction key as part of your posting entry.
Input Function
Any input function type like Allocation, Calculation, Join, View etc can be used as an input function for the RFA FI-AP function type as long as it has the necessary fields that are required from posting perspective
A SAP Document number is generated for each line
In our example, we used the JOIN function type. The output of the join function type is shown below
RFA FI-AP Configuration
Select Finance Account Payable as Remote Function Adapter Type. The RFC Destination is populated automatically based on the RFC connection set up at the environment level.
In our example the RFC Destination: is shown as blank as the RFC connection is maintained at the Environment level.
Input Tab
The input tab should contain the main source of data to be posted to SAP, which is the JOIN function type called as “Invoice Posting Preparation”
Signature Tab
The document number field (BELNR) is added in the Action section so that it can be mapped to one of the output fields. The Document number (per line item) generated in SAP after successfully posting is returned and stored in this field
Rules Tab
Like the Standard SAP Accounting tables (BKPF – Header) and (BSEG – Item), the RFA FI-AP function type also has Header and Item fields in it. Some components are marked as mandatory as these are part of the standard SAP Financial Accounting (SAP-FI) validations that need to happen for a successful posting
Whenever you create an invoice in SAP using the transaction code for document entry (such as FB60 – Enter Vendor Invoice), the fields like GL-Account Supplier etc. are mandatory. therefore these fields need a valid value.
Hence, in the RFA FI-AP Rule configuration, these fields cannot be left blank and need a value that is part of your standard SAP Financial Accounting (SAP-FI) configuration.
There are some other fields which are also mandatory, such as
- Header – username, posting date, document date, vendor number, GL Account and company code
- Line Item – GL account, tax code, accounting key and amount.
These are mandatory as they also form a part of standard SAP Financial Accounting (SAP-FI) validations.
Other fields that are mandatory depending on the characteristics or attributes of the data entered into some of the fields, such as Profit and Loss GL accounts needs a Cost Center.
Looking at the rules below, you can identify by the description of the component whether it is header-related or line item-related.
In our example, all of the relevant header and line item components have been mapped to the appropriate fields in the input function.
You can activate the RFA FI-AP function- “Invoice Posting” by clicking on the Activate button:
Upon successful activation, you can Run the RFA FI-AP function- “Invoice Posting” by clicking on the Run button.
The results can be seen including the SAP document numbers automatically generated for the postings.
Results :
The output of the Invoice Posting generated after running the function is shown below
As the records in SAP Profitability and Performance Management (SAP PaPM) have successfully posted into SAP (BKPF and BSEG), the Accounting document numbers generated in SAP are now available in SAP Profitability and Performance Management (PaPM) as shown below
You can verify the results in SAP using transaction code FBL3N – GL Account Line Item Display
Or FB03 – Display Document. Click on the Header button to see header information
Conclusion :
We can use the RFA in SAP Profitability and Performance Management (PaPM) to post entries in to Accounts Payable. This can be further enhanced to post TAX related entries as well which I will cover in my next Blog
References :
I would like to give credit for following references that helped in writing this blog
Remote Function Adapter
Database Connection
RFC Destination
Summary :
To wrap up, I have shown how we can use ‘SAP Profitability and Performance Management (PaPM) – Remote Function Adapter’ function type to create mass posting in SAP S/4 HANA.
I thank you for reading through my first blog in SAP Profitability and Performance Management (PaPM).
Kindly requesting you to leave your feedback and comments.
I would encourage you to follow the topics in https://community.sap.com/topics/profitability-and-performance-management for more enlightenment on SAP Profitability and Performance Management (PaPM).