The integration of AE in the Closing Cockpit is the key to the activation of executable objects via tasks in the SAP Financial Closing Cockpit. The corresponding installation guide is provided in the chapter Installing the SAP Financial Closing Cockpit Integration. This document describes the general mode of operation and use.
After a successful AE Internal Webservice installation and Closing Cockpit integration, you can assign executable objects to the Closing Cockpit templatesPre-defined 'workflows' for specific components/tasks, e.g. Tomcat, SubVersion.. The required steps and the execution behavior are described below.
Log on to the SAP system and call the transaction CLOCOC. Open a template (Edit) and select the command "Add taskAn executable object that is running. Tasks are also referred to as activities." via the context menu from any location in the organization structure. Specify all required values in the displayed dialog. Select "Program" for the option Type of task and enter /UC4/CC_REPORT in the corresponding field. Now select or create an appropriate variant.
This variant stores the name of the objectAutomation Engine controlled activities and processes are structured in the form of objects. See also: Task to be executed. All other fields are optional and will be passed on to the activated object as additional values via the read buffer.
Call the input assistance (F4) for the field Name of a object to display all executable objects of the clientA closed environment within an Automation Engine system where you can create and run objects. A client name consists of a 4-digit number that must be indicated when a user logs on to the Automation Engine system. Users and their rights are also defined in clients. A particular Automation Engine object type. that was specified in the particular RFC connection. Name, type, title and path of the objects are displayed.
The additional fields in the variant dialog can be used to pass additional values on to the activated object. The names of the script variables that are provided for the object in the input buffer are listed below:
Parameter/Field | Name of the AE Script variableIt stores or retrieves values dynamically at runtime. An individual Automation Engine object type. |
---|---|
Controlling area | KOKRS |
Period | PERIO |
Fiscal year | GJAHR |
The additional parameters can be used to write self-defined values to the read buffer. The column variable defines the name of the read buffer variable.
The values of this script variableA placeholder for a value within a script. can be read using the scriptA particular Automation Engine object type. element :READ in the script.
Example:
:READ&KOKRS#,,'KOKRS',
Store the variant and the task. Now create a task listShows entities in a grid view from the template.
Use the transaction CLOCO to execute task lists of the Closing Cockpit. Open a task list that includes object activating tasks. Include these tasks and check their states.
If a task has been executed and its statusThis represents the condition of a task (such as active, blocked, generating). is shown in SAP as "Completed", then it ended with the status ENDED_OK in the AE system. Every other AE status causes the output "Error" in the Closing Cockpit.
To display the AE jobAn Automation Engine object type for a process that runs on a target system. reportA report provides more detailed information about a task's execution or a component., open the spool of the relevant task in the Closing Cockpit. This spool includes all AE report types (ACT, REP, LOG,...) and the RunIDShort for "run number". It is a number that provides unique information about a task's execution. The RunID can include 7 to 10 digits. It is assigned by the Automation Engine component . of the executed AE task.
In the configurationA set of constituent components that make up a system. This includes information on how the components are connected including the settings applied. of the Closing Cockpit (CLOCOC), you can also define dependencies for tasks that start programs or transactions. Do so by opening a template or task list and calling the view "Dependencies". Tasks can be inserted in this Dependency area via drag and drop. This functionPre-defined run book template in the Automation Engine. One single step only, e.g. Start Windows Service, Copy file,… is also supported in tasks that call objects. A dependency can be used to determine that a task can only start when a particular task has ended.
See also:
AE Integration in SAP Closing Cockpit
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |