See how you can link the custom-developed programs to your Closing Cockpit and follow a discussion on the special settings and prerequisites related to this process. Learn how to:
• Link your custom-developed solutions to the Closing Cockpit for better integration with period-end activities to receive full reporting capabilities for executing custom-developed programs inside the Closing Cockpit
• Use two options to link custom-developed programs to the Closing Cockpit
• Use two ways to change the default layout for the spool for program SCMABOX so that users see the output in a consistent way (e.g., a sufficient number of columns in output)
Closing Cockpit is a standard SAP tool to monitor and control the entire period-end closing cycle. Therefore, it is important that it cover all the custom-developed programs. However, there is a special way to link these specific custom-developed programs to the Closing Cockpit to ensure that on execution in the Closing Cockpit, the SAP system displays the spools and job logs correctly and also picks the variant with dynamic variables correctly.
Organizations generally have custom-developed programs for business requirements that are not met in a standard SAP system (e.g., converting a credit card file from a bank into a format that an SAP system can recognize, such as KR1025 or GL1025). These custom-developed programs are not needed when business requirements are met by a standard SAP system or when a business relies on an easy manual workaround or uses a third-party tool. This program needs to be incorporated into the period-end closing activities (Closing Cockpit) to ensure an end-to-end process. In my example, the end-to-process begins with receiving the credit card file from the bank, moves to uploading the file into an SAP system, and ends with posting the file in an SAP system.
This article focuses only on the aspect of linking custom-developed programs to the Closing Cockpit.