How can I use organizational units other than Controlling Area, Company Code or Plant for task scheduling in AFC?
Issue / Observation
You are implementing SAP S/4HANA Cloud for advanced financial closing (AFC). As part of automating the month-end closing process, you want to set up, for example, tasks for one of the following reports:
- SD Billing Run (report RV60SBAT, “Creating Background Jobs for Billing”).
- SD Intercompany Billing (report RVPKMASS96, “Collective Processing of Resource-Related Billing”).
These reports (and all other standard SD reports) use “Sales Organization” as the main organizational structure, while AFC seems to only support Company Code, Controlling Area and Plant as organizational units. Now, you want to know how to proceed to include, for example, “Sales Organization” as organizational unit into AFC and the report variants.
Background
Values maintained on organizational unit folders of type Company Code, Controlling Area or Plant are automatically applied to every underlying folder and task in the closing hierarchy, reducing the parameter maintenance effort significantly (see also the blog SAP S/4HANA Cloud for advanced financial closing: What is a good practice for the closing structure ?).
However, it can be necessary to centrally maintain other parameter values as well, for example if:
- Your entity close is based on other organizational units.
- You collect a set of reports with the same input parameters in one folder.
This can be achieved as follows.
Step-By-Step Guide
- Remote System (ABAP): Create AFC Parameter Type
First, if there is not yet a suitable one, we need to define the AFC parameter type in the customer namespace (in our example ZSORG – Sales Org Units). This can be done via one of the following options:
- SPRO (Cross-Application Components -> Advanced Financial Closing – Local Settings):
- View FCCX_V_PTYPE_VAL (transaction SM30):
- SPRO (Cross-Application Components -> Advanced Financial Closing – Local Settings):
- Remote System (ABAP): Map Parameter Type
Then, we need to map the report parameter to the AFC parameter type (in our example, VKOR1 to ZSORG, but potentially also an appropriate predelivered one). This can be done via one of the following options:
- SPRO (Cross-Application Components -> Advanced Financial Closing – Local Settings):
- Cluster FCCX_VC_PROMAINT (transaction SM34):
- AFC: Synchronize Master Data
Background changes are synchronized automatically every 24 hours. If required, synchronization can be triggered manually in the Monitor Communication Systems app.
- AFC: Maintain Parameter Values on Folders
After that, we can maintain values for the new AFC parameter type on folder level (in our example ZSORG = ‘S001’):
Tip: It’s also possible to assign multiple values or ranges here. These are then applied during scheduling.
- AFC: Schedule Job
The parameter value maintained on folder level is used in all underlying tasks:
Summary
Using parameter types and assigning them on any structural or organizational unit folder of your closing structure in task list templates, you can represent any organizational unit required to automate closing tasks. With this blog, you’ve learned how that concept applies to the “Sales Organization” and SD-related tasks.
For more information on SAP S/4HANA Cloud for advanced financial closing, check out the following links:
Follow us via @SAP and #AdvancedFinancialClosing, or myself via Thomas Luecking
Disclaimer
Please note that SAP S/4HANA Cloud for advanced financial closing gets frequent updates and enhancements. Therefore, the current features and functions may not be exactly as described here. For the latest information, you can refer to the product documentation on the SAP Help Portal.
Please note that the information given here or any related document and SAP’s strategy and possible future developments, products and or platforms directions and functionality are all subject to change and may be changed by SAP at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver the functionality described here or any related material or code. Instead, the information is for informational purposes only. It may not be incorporated into a contract. SAP assumes no responsibility for errors or omissions in this document, except if such damages were caused by SAP’s intentional or gross negligence.
Okumaya devam et...