Skip to Content

Financial Closing Cockpit- a step by step example ( Part I )

Example with program: TFC_COMPARE_VZ – Comparison: Documents and Transaction Figures

For more details: Have a look on SAP Course: Financial Closing AC205


SAP Help:

I am looking forward to your feedback, answer and discussion.

1.Find the functions under following menu path:


2.How to add units in organisational command structure:

Take a look/and add some more if needed with clococ.

SAP has already entered controlling area and company code.

          You can organise your closing activities per organisational command structure if necessary.


3.How to make a template:

In Closing Cockpit we work with so called: task list template. Later you can add in this task list template all your activities for your closing activities.

            We use function: Clococ and go to Create Template



Here we can see the closing hierarchy which I have mentioned in point 2.

            Just try it out, the system will add all the structure automatically for you.


4.Now you can add your tasks under this folder:

Just go to the folder, right mouse and add task


I have added in SAP Financial Closing Cockpit:

System should run program TFC_COMPARE_VZ automatically with variant z_cloco.

I have entered this variant before. You also can add the variant during your work in FI closing cockpit.

We have some different types of tasks.

We also can enter offset time in accordance to cut off date of month end closing.



5.Enter Task List:

Call Function clocot. We will choose our “z_test”.


Then I will create periodic task list.


I have entered the data, and set status to released.



Then we take a look in closing cockpit about status of our task.

Our expectation is: The job has been ended successfully. 😉

6.We go to Closing Cockpit:

We use function: cloco


We can see the task has been ended successfully without errors.

I am looking forward to your valuable feedback.

All the best erwin

You must be Logged on to comment or reply to a post.
  • Hi Erwin,

    i think the biggest leverage of the tool are the dependencies between the tasks and the integration with the batch job monitor that creates job names containing both the underlying program as well as variant names. i also wasn’t aware of other CLOCOn transaction except for CLOCOC. have they been added to the Financial Closing Cockpit (Add-In) as it seems to be a product separate from Closing Cockpit?

    users should also be made aware of the LOCAL_CLOSE switch that enables the tool for the business client.

    this tool is so much better than the spreadsheets that most organizations use for managing their close.



    • Hello Gregory and Vekant,

      Thank you for your feedback.

      Yes of course you are right I shall show dependencies and job monitor.

      My idea was to show in an first step how how you can enter a job.

      I will will work out deoendencies and job monitor in a second step.

      Also entering information and attaching documents.

      Thank you.

      All the best


    • Hello,

      Thank you for your nice and motivating words. 😳

      A pleasure that this document is helpful for you.

      Yes, it is important bringing down complexity in simple words.

      all the best erwin


    Hi Erwin,

    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

    • Hi Frank,

      Not sure if you still need a response, but I’ll provide one anyways!

      You can’t call a dynpr program ‘report type F’ (it must be able to execute in background mode and generate a spool file- batch enabled).

      There are alternatives for most of the items you listed:

      CO43: instead of SAPLKAZB,  use RKAZCO43
      KKAO: instead of SAPMKKAC, use SAPKKA07
      CO88: instead of SAPLKO71,  use RKO7CO88
      KE30: can only call this as a transaction, not a program.



  • Can you please add how you i can schedule the task run on a specific date /Time each month? I understand that the key date is the date on which the task is schedule to run, but how to set the time? Also can you please add some dependencies in the scheduling.

    Thank you very much

  • Hi Nice blog.


    I have a question, have any one tried consolidating all the task over due emails to a particular user into one email? if any one tried how did you achieve this. I have tried using couple of BADIs but its not working.




  • Hi Erwin,

    very interesting blog, thank you!


    Do you have any idea, in which SAP tables the execution of the different tasks (program, job, transaction, note, flow definition) is logged? Most interesting for me are the planned and actual timestamps.

    I would very much appreciate your help! Thanks in advance,