Configure SAP Financial Closing Cockpit to Start Close Tasks in Multiple Systems
- by Janet Salmon, Product Manager, SAP AG
- October 15, 2008
See improvements made to SAP Financial Closing Cockpit in Enhancement Package 3 that allow it to integrate with SAP Central Process Scheduling by Redwood and to create close tasks in other systems.
SAP Central Process Scheduling by Redwood (SAP CPS) is designed to integrate process automation for SAP and non-SAP applications across distributed and heterogeneous systems. For financial teams this means that you can centralize your close process by using CPS to initiate close tasks, such as a depreciation run or an allocation, in systems other than the SAP ERP Central Component system in which the Closing Cockpit resides.
At the Financials 2008 conference, I noticed a lot of interest in the improvements made to the closing processes in SAP Financial Closing Cockpit with SAP Enhancement Package (EhP) 3. From EhP 3 for SAP ERP 6.0, Closing Cockpit is integrated with SAP Central Process Scheduling for SAP NetWeaver 7.0 by Redwood (SAP CPS). This allows you to set up a central template for all your close tasks in Closing Cockpit and to use SAP CPS to route close tasks from your central SAP ERP Central Component (ECC) 6.0.3 system to other remote systems, whether these are other ECC systems containing Financials data, SAP R/3 systems on lower release levels, or non-SAP systems containing data that affects the close process. SAP CPS is available for installation on the SAP NetWeaver stack from SAP NetWeaver 7.0 Support Package 14.
I’ll explore the cross-client and cross-system scheduling available in the latest EhP in 12 steps. I’ll describe the system I’m working with in the example scenario before going into Closing Cockpit integration features with SAP CPS.
Would you like to see this full item?