Hello everyone! I am thrilled to announce the release of the new Remote Function Adapter (RFA) Type: “Post Journal Entries for Group Reporting” which is now available in SAP Profitability and Performance Management (PaPM) SP21 release.
In this blogpost, I’ll provide you with an overview of the functionality of the new RFA Type “Post Journal Entries for Group Reporting”. The new RFA type enables you to post and simulate journal entries in group reporting in SAP S/4HANA using the synchronous inbound service API_CNSLDTNGRPJRNLENTR.
Please note that SAP S/4HANA provides the API_CNSLDTNGRPJRNLENTR service. Group Reporting is only available from S/4HANA 2022 onwards and is published on the SAP API Business Hub. For more information about this API, see SAP API Business Hub or APIs for Group Reporting.
For more information about how to configure the new RFA Type, please visit PaPM Application Help. For more technical details about the new RFA Type, see SAP Note 3269787 - FS-PER-OP Rel 3.0 SP21 - New RFA Type Post Journal Entries for Group Reporting and RFA Per....
I will also show you how to configure the “Post Journal Entries for Group Reporting” RFA Type on PaPM On-Premise, as well as how to validate the results.
First, you must configure the Database Connection and HTTP RFC Destination on the Source System. Here are some examples for your reference.
To use the Remote Function Adapter, you need an input function that maps fields from the input function to the components on the Rules tab. You can use a Model Table, Model View, or the result of another function as long as it contains the necessary fields.
In this example, I will use a Model Table as the input function.
Now let’s configure the Remote Function Adapter by maintaining the header section as follows:
Remote Function Adapter Type = “Post Journal Entries for Group Reporting”
HTTP RFC Destination = Maintained RFC connection at “HTTP Connections to ABAP Systems” type as in the example below (QWR_002_HTTPS)
After you have configured the header section, it is now time to configure the Input tab. Assign the Model Table in the Input Function field as shown in the screenshot below.
Then configure the Signature tab by assigning the fields in the Selection and Action sections as shown in the screenshot below.
Now comes the most important part, in which you must map the fields correctly. In my example, all mandatory components have been mapped to the appropriate fields from the input function.
Please note that the component below has intentionally hard-coded values.
The hard-coded values differentiate the result when running the RFA function. If you maintain 'X' as the value for the “control-sim_fg” component, a simulation run will be executed without generating a document number or postings to the SAP S/4HANA system. However, if you maintain " as the value for the same component, it will generate a document number and postings will be done in the SAP S/4HANA system.
Once the field mapping is complete, choose Activate and then Run the function. The result should have the same data when using our input, but with document numbers generated by the function. These document numbers should fill the Consolidation Number field. Please keep in mind that all mapped records will be posted to the S/4HANA system.
To validate the posting capability of the new RFA Type, you can perform either of the following steps:
In the target system, launch transaction code SE16N. This will open the General Table Display screen.
In this screen, assign “ACDOCU” in the Table field, and the generated document number in the Document Number field. Then choose the Execute button.
In the target system, launch transaction code /n/UI2/FLP. In the Home page, go to the Consolidation Data Preparation section, then choose the Display Group Journal Entries tile.
In this screen, search for entries by using the Document Number search criteria.
Congratulations! You have now learned how to use the Remote Function Adapter’s functionality.
I hope you found this blog post helpful and informative. If so, feel free to share it with your colleagues. If you have any questions or comments, please feel free to post them in the SAP Community Questions section. Also, if you want to read more blog posts about SAP Profitability and Performance Management, you may check out these SAP Community Blog Posts.
Thank you for taking the time to read this post!
In this blogpost, I’ll provide you with an overview of the functionality of the new RFA Type “Post Journal Entries for Group Reporting”. The new RFA type enables you to post and simulate journal entries in group reporting in SAP S/4HANA using the synchronous inbound service API_CNSLDTNGRPJRNLENTR.
Please note that SAP S/4HANA provides the API_CNSLDTNGRPJRNLENTR service. Group Reporting is only available from S/4HANA 2022 onwards and is published on the SAP API Business Hub. For more information about this API, see SAP API Business Hub or APIs for Group Reporting.
For more information about how to configure the new RFA Type, please visit PaPM Application Help. For more technical details about the new RFA Type, see SAP Note 3269787 - FS-PER-OP Rel 3.0 SP21 - New RFA Type Post Journal Entries for Group Reporting and RFA Per....
I will also show you how to configure the “Post Journal Entries for Group Reporting” RFA Type on PaPM On-Premise, as well as how to validate the results.
First, you must configure the Database Connection and HTTP RFC Destination on the Source System. Here are some examples for your reference.
- Database Connection - configure the database connection at Environment Level (choose “DBCON” or “DEFAULT” from the list)
- HTTP RFC Destination – assign the configured RFC destination type “H”.
To use the Remote Function Adapter, you need an input function that maps fields from the input function to the components on the Rules tab. You can use a Model Table, Model View, or the result of another function as long as it contains the necessary fields.
In this example, I will use a Model Table as the input function.
Fiscal Year (ZE_FISCALYR) | Consolidation Version (ZE_CONVERSION) | Fiscal Period (ZE_FISCALPRD) | Consolidation Chart Of Accounts (ZE_CONSCHARTOFACCT) | Consolidation Document Type (ZE_CONSDOCTYPE) | Document Item Text (ZE_DOCITMTXT) | Consolidation Unit (ZE_CONSUNIT) | Consolidation Posting Item (ZE_CONSPOSTITEM) | Financial Statement Item (ZE_FINSTATEITM) | Sub Item (ZE_SUBITEM) | Amount In Local Currency (ZE_AMTLOCALCURR) | Local Currency (ZE_LOCALCURR) |
| 2021 | B10 | 012 | Y1 | B1 | PAPM GROUP REPORTING ADAPTER | 1000 | 1 | 111100 | 900 | 10.00 | USD |
| 2021 | B10 | 012 | Y1 | B1 | PAPM GROUP REPORTING ADAPTER | 1000 | 2 | 111100 | 915 | -10.00 | USD |
Now let’s configure the Remote Function Adapter by maintaining the header section as follows:
- Configure the RFA Function – Header
Remote Function Adapter Type = “Post Journal Entries for Group Reporting”
HTTP RFC Destination = Maintained RFC connection at “HTTP Connections to ABAP Systems” type as in the example below (QWR_002_HTTPS)
After you have configured the header section, it is now time to configure the Input tab. Assign the Model Table in the Input Function field as shown in the screenshot below.
Then configure the Signature tab by assigning the fields in the Selection and Action sections as shown in the screenshot below.
Now comes the most important part, in which you must map the fields correctly. In my example, all mandatory components have been mapped to the appropriate fields from the input function.
| Component | Name | Declaration Type | Is Mandatory | Field |
| control-grouping | Document Grouping By | Input | Yes | ZE_BASEUNIT |
| control-ordering | Document Order By | Input | No | |
| control-sim_fg | Simulation | Input | No | " |
| gr-FiscalYear | FiscalYear | Input | Yes | ZE_FISCALYR |
| gr-ConsolidationVersion | ConsolidationVersion | Input | Yes | ZE_CONVERSION |
| gr-FiscalPeriod | FiscalPeriod | Input | Yes | ZE_FISCALPRD |
| gr-ConsolidationChartofAccounts | ConsolidationChartofAccounts | Input | Yes | ZE_CONSCHARTOFACCT |
| gr-ConsolidationDocumentType | ConsolidationDocumentType | Input | Yes | ZE_CONSDOCTYPE |
| gr-DocumentItemText | DocumentItemText | Input | No | |
| gr-ConsolidationUnit | ConsolidationUnit | Input | Yes | ZE_CONSUNIT |
| gr-ConsolidationGroup | ConsolidationGroup | Input | No | |
| gr-ConsolidationUnit1 | ConsolidationUnit1 | Input | No | |
| gr-ConsolidationUnit2 | ConsolidationUnit2 | Input | No | |
| gr_item-ConsolidationPostingItem | ConsolidationPostingItem | Input | Yes | ZE_CONSPOSTITEM |
| gr_item-FinancialStateItem | FinancialStateItem | Input | Yes | ZE_FINSTATEITM |
| gr-item-ConsolidationVersion | ConsolidationVersion | Input | Yes | ZE_CONVERSION |
| gr_item-SubItem | SubItem | Input | Yes | ZE_SUBITEM |
| gr_item-AmountInLocalCurrency | AmountInLocalCurrency | Input | No | ZE_AMTLOCALCURR |
| gr_item-LocalCurrency | LocalCurrency | Input | No | ZE_LOCALCURR |
| gr_item-AmountInGroupCurrency | AmountInGroupCurrency | Input | No | |
| gr_item-GroupCurrency | gr_item-GroupCurrency | Input | No | |
| gr_item-AmountInTransactionCurrency | AmountInTransactionCurrency | Input | No | |
| gr_item-TransactionCurrency | TransactionCurrency | Input | No | |
| gr_res-ConsolidationDocumentNumber | Document Number of an Accounting Document | Output | Yes | ZE_CONSDOCNUM |
| gr_res-ConsolidationVersion | Consolidation Version | Output | No | |
| gr_res-FiscalPeriod | Posting Period | Output | No | |
| gr_res-ConsolidationChartOfAccounts | Consolidation Chart Of Accounts | Output | No |
Please note that the component below has intentionally hard-coded values.
The hard-coded values differentiate the result when running the RFA function. If you maintain 'X' as the value for the “control-sim_fg” component, a simulation run will be executed without generating a document number or postings to the SAP S/4HANA system. However, if you maintain " as the value for the same component, it will generate a document number and postings will be done in the SAP S/4HANA system.
| Component | Comment |
| control-sim_fg | ‘X’ for simulation ” for real run |
Once the field mapping is complete, choose Activate and then Run the function. The result should have the same data when using our input, but with document numbers generated by the function. These document numbers should fill the Consolidation Number field. Please keep in mind that all mapped records will be posted to the S/4HANA system.
| Fiscal Year (ZE_FISCALYR) | Consolidation Version (ZE_CONVERSION) | Fiscal Period (ZE_FISCALPRD) | Consolidation Chart Of Accounts (ZE_CONSCHARTOFACCT) | Consolidation Document Type (ZE_CONSDOCTYPE) | Document Item Text (ZE_DOCITMTXT) | Consolidation Unit (ZE_CONSUNIT) | Consolidation Posting Item (ZE_CONSPOSTITEM) | Financial Statement Item (ZE_FINSTATEITM) | Sub Item (ZE_SUBITEM) | Amount In Local Currency (ZE_AMTLOCALCURR) | Local Currency (ZE_LOCALCURR) | Consolidation Document Number ( ZE_CONSDOCNUM ) |
| 2021 | B10 | 012 | Y1 | B1 | PAPM GROUP REPORTING ADAPTER | 1000 | 1 | 111100 | 900 | 10.00 | USD | 1000000124 |
| 2021 | B10 | 012 | Y1 | B1 | PAPM GROUP REPORTING ADAPTER | 1000 | 2 | 111100 | 915 | -10.00 | USD | 1000000124 |
To validate the posting capability of the new RFA Type, you can perform either of the following steps:
- Via SAP GUI
In the target system, launch transaction code SE16N. This will open the General Table Display screen.
In this screen, assign “ACDOCU” in the Table field, and the generated document number in the Document Number field. Then choose the Execute button.
- Via Fiori Launch Pad
In the target system, launch transaction code /n/UI2/FLP. In the Home page, go to the Consolidation Data Preparation section, then choose the Display Group Journal Entries tile.
In this screen, search for entries by using the Document Number search criteria.
Congratulations! You have now learned how to use the Remote Function Adapter’s functionality.
I hope you found this blog post helpful and informative. If so, feel free to share it with your colleagues. If you have any questions or comments, please feel free to post them in the SAP Community Questions section. Also, if you want to read more blog posts about SAP Profitability and Performance Management, you may check out these SAP Community Blog Posts.
Thank you for taking the time to read this post!
- SAP Managed Tags:
| User | Count |
|---|---|
| 3 | |
| 3 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 |
