Closing Cockpit

CLOSING COCKPIT:
<REMOVE UNNEEDED IN SLIDE MASTER: CONFIDENTIAL | RESTRICTED | HIGHLY RESTRICTED> DOCUMENT USE IN ACCORDANCE WITH COMPANY POLICIES
Index:
Purpose & Key Features Benefits Prerequisites Configuration Closing Activities
Purpose:
Closing cockpit is the structured interface for executing transactions and programs that form part of complex processes, such as closing processes.
Closing cockpit required for period-end closing of individual financial statements providing a simplified overview of the entire closing process.
Key Features:
Closing cockpit enables the period-end close run smoothly and provides the basis for the companys financial and management reporting. Achieving this objective has two aspects. The first is to manage the organization of people, accountability of the closing tasks. The second is to eliminate error-prone and time-consuming tasks. Speeding up the period-end closing process has been a longstanding objective for almost every company. After the US Securities and Exchange Commission (SEC) demanded quicker preparation of financial statements, fast closing became even more important to US public companies. Faster close enables fast identification, investigation, and elimination of accounting issues. It allows companies to react faster as conditions change, perform better, and make significant improvements in total cost of ownership (TCO).
Benefits:
Closing Cockpit for period-end closing enables companies to close their books faster and more efficiently. It Groups all Relevant Closing Activities and gives Clerks and Management a better overview of tasks that have already been carried out or that are still open. It reduces errors through transparency and support for compliance via a concise overview of the closing status and remaining tasks. Significantly reduced time to reconcile intercompany activities. It improves employees productivity and reduced costs. Closing cockpit adds business value because it creates transparency and supports compliance by providing a perfect overview of the closing status and drilldown to all details.
Prerequisites:
Closing cockpit available from mySAP ( T-code: CLOCOC ) Any program or transaction used for closing (Including Z transactions/program), needs to be in the table (SCMATRANSACT And SCMAPROGRAMS) Check the table entry in SE16 Table BTCOPTIONS for Value As information please refer the SAP Note 325118
Configuration
Menu Path
Simple Customization
CLOCOC - Closing Cockpit (Manage Templates and Task Lists)
Organizational Hierarchy
You can create your own Hierarchy (by selecting New Org Hierarchy) depending on the requirement is the same or not meeting the requirements
Create Template
Message
Once the template is ready you can import the template from Closing Cockpit or from Schedule Manager.
Add tasks to the organizational structure by selecting right click of the mouse
Organizational Structure
Creation of Task list for closing activities

Before creating task, you need to create list of tasks along with variants, which will ease out the work, while adding Task. Following is the Sample Task list and Variant.
Task Run Business Area's Assignment report Run Depreciation in Test Run Verify Depreciation Posting Log Asset Balances Logistic Invoice Verification Background Check Automatic Clearing Reconciliation of Financial Documents and transactional figures Open New CO Posting Period Open FI Period Price update - Release Standard Price Display Billing Due List Customer Master Data Comparison List GR/IR Balances Reconcile PA to G/L Carry forward Receivables and Payables Balance Carry Forward Profit Center - Carry forward Actual balance Year End Closing - Assets Asset Fiscal Year Change Program SAPF181 RAPOST2000 RAPOST2001 RABEST_ALV01 RMBABG00 SAPF124 SAPF190 OKP1 OB52 SAPRCK23 SDBILLDL RFDKAG00 RM07MSAL RCOPCA44 SAPF010 SAPFGVTR RCOPCA34 RFNRIV20 RAJABS00 RAJAWE00 TEST TEST TEST TEST TEST TEST TEST TEST TEST TEST TEST Variant TEST TEST TEST TEST TEST TEST TEST
Task created without the Variant, will be similar to online execution of transaction
Program and Variant, Transaction for execution

Offset in Days Relative to Key Date of a Task List
The day when the task is to be performed is specified in relation to a key date valid for a template or task list. The offset specifies how many days before (negative offset) or after (positive offset) the key date the task should be performed. If the task is to be performed on the same day as the key date, the value of the offset is zero.
Program with Variant
Example
The key date is October 28. Task 1 should be performed on October 25: Offset -3 Task 2 should be performed on November 2: Offset +5
Enter the Program Variant (If the variant is not entered the execution is Manual) Use Offset in Days and Time If required enter the time required for execution Select critical Path depending on the requirements
10
Template ready duly defined Program
Document and Notes Critical Path Tasks/Program Transaction
Once you are through with the template please save the template.
11
Define Dependencies
You can display these predecessor relationships under Dependencies. When you enter a relationship between programs and transactions here, this relationship is checked during subsequent processing in the application (CLOCO), thereby ensuring the correct sequence is applied.
After saving the template create the task list.
12
Once the task list is release on the screen you will find the icon is activated for scheduling the activities. Scheduling the same by clicking (selecting all the task) and then schedule . Once the tasks are scheduled you will get the message as below.
Can see the status of each of the activities
13
Status of activities after scheduling

Graphical status
Normal View
14
All the results can be seen in the spool (Tr-Code SP02)
Execute the transaction by right click of mouse
15
Use of flow definitions

yYou can use the flow definitions for creating the task in chronological order. yEasy configuration of Workflow. yBundling the activities can be done yDo not forget to activate the workflow. yYou can create a flow definition using the following elements as steps:
with the quick info text Workflow: Start/End Workflow with the quick info text Program:Assign Program with Variant with the quick info text Flow Definition: Assign Flow Definition with the quick info text User Decision: Assign User Decision with the quick info text Fork: Assign Parallel Processing
16
Closing Activities:
Creation of Task List for Closing Activities Requirement gathering Template:
Sample Template
Typical Closing Activities list:
Closing Activities
17

Closing Cockpit

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Closing Cockpit

Uploaded by

Copyright:

Available Formats

CLOSING COCKPIT:

CLOCOC - Closing Cockpit (Manage Templates and Task Lists)

Creation of Task list for closing activities

Program and Variant, Transaction for execution

Program with Variant

Template ready duly defined Program

Document and Notes Critical Path Tasks/Program Transaction

After saving the template create the task list.

Can see the status of each of the activities

Status of activities after scheduling

All the results can be seen in the spool (Tr-Code SP02)

Execute the transaction by right click of mouse

Use of flow definitions

Typical Closing Activities list:

You might also like