The closing cockpit is a very powerful tool in SAP Financial System which provides a structured interface for executing transactions and programs that form part of complex processes such as periodic and annual closing processes. The tree structure supports processes within an organizational structure such as a company code, as well as scenarios impacting multiple organizational structures. The closing cockpit as a tool is very useful in scenarios:

1. The activities are repeated periodically

2. Multiple people are responsible for completion of tasks

3. The activities are performed in a chronological order

4. A collaborative view is required by all people or units involved with a clear overview for dependencies

Two of the basic structural elements of a closing cockpit configuration is:

1. Template – The template contains the list of steps to be executed, the sequence in which they need to be executed

2. Task List – The task list contains the information contained in the template along with the actual date of execution.

The major steps in the configuration for a closing cockpit have been listed in the diagram below:

Drawing 1.JPG

The path for accessing the closing cockpit configuration is as under:

Drawing 1.JPG

The transaction for this is CLOCOC

The first prerequisite for configuring the closing cockpit is to register the programs in the table SCMATRANSACT. This can be done using SM30 or the closing cockpit configuration itself as shown below:

Drawing 1.JPG

The complete list of programs which are already registered is shown. You can add additional programs including custom programs by clicking on “New Entries” as below:

Drawing 1.JPGDrawing 1.JPG

Drawing 1.JPG

Just like the programs, all the transactions which need to be execute from closing cockpit must also be registered as shown below:

Drawing 1.JPG

Drawing 1.JPG

Similar to Programs, you can add the custom Z or Y Transactions as well to the closing cockpit in addition to the standard transaction codes. Once the above prerequisites have been completed, we are now ready to start the configuration steps  for the closing cockpit.

Creation of Organizational Hierarchies

The configuration starts with the creation of organizational hierarchy. The creation of organizational hierarchy allows to distribute the closing process in terms of organizational structures. If org elements like profit center are used in SAP system, it essentially means that segregation can be done at this level as well.

Drawing 1.JPG

Follow the path shown in the screen shot above to start creating the Organizational Hierarchy. If the standard delivered organizational elements are not sufficient for the Business Requirement, you can add more organizational elements for Closing Cockpit as shown below:

Drawing 1.JPG

Drawing 1.JPG

Drawing 1.JPG

Add the field value which needs to be added for creating the organizational hierarchy. When the field has been added, now you can specify the name of your organizational hierarchy as below:

Drawing 1.JPG

Creation of Template

A template is used to create the individual steps in a process chain. The template is therefore a collection of tasks which need to be executed in a particular sequence keeping in orientation the overall process and organizational units involved.The steps to configure organizational template is as under:

Drawing 1.JPG

Be mindful of the fact that the Create Template is available only in the change mode for T Code CLOCOC.

Drawing 1.JPG

A pop up box will appear in which you can define the name of the template and also link the same to the Closing Hierarchy. You can also link it to a Factory Calender and define other time dependent attributes for the template.

Drawing 1.JPG

When you press enter, the template is saved. Now you create all the subfolders in the order in which the activities need to be executed.This represents a systematic view of completing the closing activities.

Drawing 1.JPG

You can right clock to modify a folder properties or to create a new sub folder

Drawing 1.JPG

Once the folders have been created, now we need to add the task to in the form of individual activities that need to be performed as part of the overall process in the task list. This can be an execution of a transaction code or a program. For creating a task in sub folder, right click on the same and click on add task as shown below

Drawing 1.JPG

Drawing 1.JPG

The tasks can be created in the following types:

–      Program with Variant

–      Program without variant

–      Transaction

–      Notes

–      Flow Definition

You can specify the planned run time of the activity. If the same has a deadline for completion, the same can be marked as “Critical Path” and it will display accordingly in the cockpit. You can also specify the usage of the task highlighting the usage of the same, whether the same is used in month end or period end or year end closing.

Drawing 1.JPG

In the closing cockpit, you can also portray dependencies for a preceding step as well for a task. This allows that the preceding task is completed first successfully before execution of the current task in hand. This is an important step to plan a smooth closing.

Drawing 1.JPG

Click on any task and on the Dependencies tab, right click to add a dependent task

The task will than show up as a preceding task as shown below

Drawing 1.JPG

The next step in the configuration is the generation of the task list. Follow the steps as shown below

Drawing 1.JPG

Drawing 1.JPG

Here the name of the task list and template is same. This means that we are generating the same out of task list template. The key date is entered along with the type of closing and fiscal year details. By default task list is not in released status.While saving, if the task is ok, save it as released. This will allow the task to be scheduled.

Drawing 1.JPG

Once all the tasks are in released, these can now be scheduled as part of month end processes.

Drawing 1.JPG

There are standard templates for closing cockpit delivered which can also be used.Drawing 1.JPG

Depending on the requirements, you can create your own task list or use the standard ones.

To report this post you need to login first.

41 Comments

You must be Logged on to comment or reply to a post.

      1. Shihab MS

        HI Sanil,

        Appreciated.

        Could you explain the relevance of adding customer transaction and program into that table & which program you have updated there.

        Shihab

        (0) 
        1. Sanil Bhandari Post author

          Hi Shihab

          The requirement for adding transactions (both SAP delivered and custom) as well as programs is because they need to be appear in the table SCMATRANSACT and SCMAPROGRAMS respectively. If the transactions and programs do not appear in these tables, you would not be able to create a task for them in the closing cockpit. The program I have added is for illustrative purpose. You may choose the required program based on your business need, be it SAP delivered or your custom program.

          Let me know if I have been able to answer your question.

          Thanks & regards

          Sanil Bhandari

          (0) 
    1. Sanil Bhandari Post author

      You are correct Gregory. It takes times getting used to, but is very very useful and collaborative tool especially for today’s organization which have shared service centers serving multiple markets. It helps in a fast close.

      Thanks & Regards

      Sanil Bhandari

      (0) 
  1. ManiKumar Yandrapu

    Hi Sanil,

    Well document Sanil, I must say this document will guide us what is SAP Cockpit & how it is work in real time enviornment / critical periodic processes & also who dealt with several orgnizations under one tree.

    Regards

    Mani Kumar

    (0) 
  2. Kamal Kumar Ray

    Hi Sanil ,

    Thanks for sharing the detailed document on closing cockpit , its really good..!!

    Just a question ,i want to set up 2 factory calendar in a single template for 2 different folders , can you let me know the configuration set up.it will be great help .

    Thanks
    kamal

    (0) 
  3. Frank Jensen

    Hi Sanil,

    and thank you for this very helpful introduction to Closing Cockpit.

    We are implementing this for one of our customers, but we are experiencing problems with calling some programs from CLOCOC, see below list.

    Tcode / PGM
    CO43 / SAPLKAZB (dynpro pgm)
    KKAO / SAPMKKAC (dynpro pgm)
    CO88 / SAPLKO71 (dynpro pgm)
    KE30 / SAPMKCEE (COPA reports)
    Do you have any experience regarding how we can include these programs in Closing Cockpit??? Because we are not allowed to create these programs, and it is not possible to operate with selection variants for these programs as well. So, if we need these programs in the cockpit, how do we include these?

    I thank you in advance for your reply.

    Best regards
    Frank Jensen

    (0) 
  4. Ramesh Rajan

    Hi Nice blog.

     

    Can any one suggest how to achieve the following requirement, if already had performed.

     

    We have a addon Financial Closing cockpit, and now the requirement is to to consolidate all the emails that workflow sends out as individual emails to the users to one email per day. Tried to implement Custom notifications, Custom Notification Scenarios BADIs. But not getting the result.

     

    any help or suggestions would be appreciated.

     

    Thanks

    Hima Akkineni

    (0) 

Leave a Reply