Integrate Period-End Processes by Linking Custom-Developed Programs to the Closing Cockpit

  • by Gaurav Agarwal, Principal Consultant, SAP S/4HANA Finance, Infosys Limited
  • July 16, 2013
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)
Key Concept

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.

For information on the detailed standard SAP process for configuring Closing Cockpit, see Janet Salmon’s article, “Configure SAP Financial Closing Cockpit to Start Close Tasks in Multiple Systems.”

This article focuses only on the aspect of linking custom-developed programs to the Closing Cockpit.


Gaurav Agarwal

Gaurav Aggarwal is SAP S/4HANA lead consultant at Infosys Limited. He has more than 14 years of experience, including 11 years in SAP Finance. He has expertise in both SAP FI and Controlling (CO) with integration to other modules in manufacturing and process industries. He is a chartered accountant and SAP Certified Financial Consultant. He holds a bachelor’s degree in commerce and is a techno-functional expert with thorough knowledge of the necessary ABAP for functional experts. He is a veteran in G/L, AR, AP, banking, FA, Travel Management, and closing cockpit and has handled greenfield implementation, upgrades and conversions, rollouts, and support projects.

See more by this author


No comments have been submitted on this article. 

Please log in to post a comment.

To learn more about subscription access to premium content, click here.