Professional Documents
Culture Documents
Configuration Guide and Transaction Step
Configuration Guide and Transaction Step
Configuration Guide
and
Transaction Steps
Closing cockpit –
Fast Close
Closing cockpit – Config Guide
Table of Contents
1. Purpose.................................................................................................3
2.1. Objective...............................................................................................3
3. Configuration.......................................................................................4
4. Transaction.......................................................................................12
5. Annexure.............................................................................................12
1. Purpose
This configuration guide provides the information which you need to set up for this
POC.
2.1. Objective
An organization is interested in reducing the time required for closing the books
each month. They are using SAP version ECC6.0 and are stable on SAP
system. They need transparency and require an audit trail of the entire closing
process. The current closing process does not satisfy their compliance
requirements
Scope :
The scope of this document covers scenario mentioned above. This document is created
on ECC 6.0 enhancement pack 3.0
3. Configuration
The prerequisite is that all transactions and program that need to be executed as a part
of closing activity should be specified in table SCMATRANSACT and SCMAPROGRAMS
respectively.
Org levels:
Create Template
Individual steps of a closing process are structured using a template.
Sub folders may be created for structuring the closing activities. In the change template
mode, right click on the org structure and select “create sub folder”
Create Tasks
Into each subfolder a task may be assigned. A task may be a program with variant (for
background processing), a program without variant (for foreground processing), a
transaction code (for foreground execution), a note (giving instructions or
documentation) or a flow definition.
When a flow definition is executed (or scheduled to be executed), all of the related
programs are processed by the system in the specified sequence, and then the results
are made available for analysis under Detailed Information.
SAP standard has delivered a few flow definitions. Additional may be created as
required.
Sample flow definition (SAP delivered - 1-CM-OBJ-1 for period end activities of
manufacturing orders)
This is an additional function that is only available when SAP Central Process Scheduling
(CPS) is implemented. SAP CPS is not a part of SAP ERP. However, Closing Cockpit
provides a connection to SAP CPS.
Define Dependencies
The task list lists the programs or transactions to be executed in a chronological order.
However, over and above such definition if there is a need to have a predecessor for a
particular task, the same may be defined using dependencies. By defining dependencies
it is ensured that programs and transactions can only be scheduled or executed once the
predecessor activities have been processed successfully (without errors).
4. Transaction
5. Annexure
http://help.sap.com/erp2005_ehp_04/helpdata/en/42/f890415ae3a109e10000000a155
106/frameset.htm