FCc Templates

The described templates are used to created process definitions in the FCc scenario.

FCA_FCc_Process_Event_Template

With ECC6 EHP3, one can use the SAP Financial Closing cockpit together with ProcessClosed A process is a Process Definition that is submitted into a queue. When users request the execution of a chain, a process server creates a record in the Job table, calculates the start time and sets the status to Assigned. Automation Engine. Both products provide additional information that can be utilized by the processes that need to be executed.

This template makes this additional information directly available without the need to create it again for each process definition. The Template is a process which allows the implementation of a single process but also of sequences and process steps. This process is called a process definition.

Parameters

The process parameters will be described in the order they are defined in the process. There is only one runtime parameter defined. All the other parameters are handled via the On-Change Action (details below). In general if a parameter has an input value (no replacements) then it is not replaced.

Group: Technical

  • SID – This parameter provides an overwrite capability for the SAP SID to the Target System determination mechanism. This mechanism determines automatically where the process needs to be run. This is done based on the Organization Structure the task resides in.
  • SID_CLIENT – This parameter provides an overwrite capability for the SAP Client to the Target System determination mechanism.
  • SID_USER – This parameter provides an overwrite capability for the SAP_USER_NAME.
  • TASK_NO – This is an information field defining the tasks identification number. Especially with a bigger number of tasks to be implemented, a unique identifier for the task is a great help in communication.

Group: RunTime Parameters in this group are automatically retrieved. If an overwrite is required for a parameter, then it can be pre-filled and is not overwritten.

  • KOKRS – The value is retrieved from the FCc parameter SAP_CC__KOKRS_S and converted so that it can be used for mapping. It contains the Controlling Area.
  • BUKRS – The value is retrieved from the FCc parameter SAP_CC__BUKRS_S and converted so that it can be used for mapping. It contains the Company code.
  • WERKS – The value is retrieved from the FCc parameter SAP_CC__WERKS_S_and converted so that it can be used for mapping. It contains the Plant code.
  • TASKLIST_END_DATE – The value is retrieve from the FCc parameter SAP_CC__LDAY_P and converted so that it can be used for mapping. It contains the Task List date (also called Ultimo) in yyyyMMdd format.
  • TASKLIST_PERIOD – The value is retrieve from the FCc parameter SAP_CC__PERIOD_P and converted so that it can be used for mapping. It contains the Task List fiscal period in NUMC(3) format.
  • TASKLIST_YEAR – The value is retrieve from the FCc parameter SAP_CC__GJAHR_P and converted so that it can be used for mapping. It contains the Task List fiscal year.
  • SAP_SYSTEMS – The value of this field is derived using the following rule :
  • CLIENT – See SAP_SYSTEMS parameter.
  • SAP_USER_NAME – The value is derived depending on the method defined in Application Customizing. Default is "Executor", which means the value is retrieved from the FCc parameter SAP_CC_EXECUTIVE (if there is no SID_USER override) and converted from Global User identification to the Local User IDClosed Th unique identifier of a required for the target system. If more than one user is referenced, the first User defined is used.
  • LANGUAGE – The value is retrieved from the User Detail of the Target System user defined in SAP_USER_NAME. If there is no Language defined, then the Language is retrieved from the Organizational Structure.
  • Group: SAP_CLOSING_COCKPIT – The fields in this group are provided by the FCc automatically.
  • SAP_FCC_TFC_INST_ITEM$ITEM – (EHP5+) This parameter contains the ID required to retrieve the Task-Details. It is used to retrieve the details for later processing.
Tip: Currently the SAP_FCC_TFC_INST_ITEM$ITEM parameter is not part of the Template delivered. It can be added if needed and its content is automatically copied to TASK_ITEM.
  • TASK_ITEM (AddOn) – This parameter contains the ID required to retrieve the Task-Details. It is used to retrieve the details for later processing.
  • SAP_FCC_SYST$SYSID (EHP5+/AddOn) – Contains the SID from which the Task was started.
  • SAP_FCC_SYST$MANDT (EHP5+/AddOn) – Contains the Client from which the Task was started.
  • SAP_CC_RESPONSIBLE – Contains the responsible user defined in the Task. The user(s) is formatted as <Agent Type>:<Agent>
  • SAP_CC_EXECUTIVE – Contains the executive user defined in the Task. The user(s) is formatted as <Agent Type>:<Agent>
  • SAP_CC_RES_USR_SMTP – Contains the email address defined in the FCc system for the responsible user. Contains a list of email addresses from the Agent
  • SAP_CC_EXE_USR_SMTP – Contains the email address defined in the FCc system for the executive user. Contains a list of email addresses from the Agent
  • SAP_CC__LDAY_P – Contains the Task Lists date (Ultimo) in Range format.
  • SAP_CC__PERIOD_P – Contains the Task Lists fiscal period in Range format.
  • SAP_CC__GJAHR_P – Contains the Task Lists fiscal year in Range format.
  • SAP_CC__KOKRS_S – Contains the Controlling Areas defined for this Task.
  • SAP_CC__BUKRS_S – Contains the Company Codes defined for this Task.
  • SAP_CC__WERKS_S – Contains the Plant Codes defined for this Task.
  • SAP_CC_FACTORYCAL_ID – Contains the SAP Factory Calendar-ID defined for the Task.
  • SAP_CC_ESTIMATED_RUNTIME – Contains the Estimated Runtime defined in the Task (Minutes).
  • SAP_CC_CONTEXT_ID – Contains the identifier of the Task List. It has two parts, the Template and the instance number.
  • SAP_CC_CONTEXT_DESCR – Contains the Task List description.
  • SAP_CC_TASK – Contains the Task description.
  • SAP_CC_MAX_START_DELAY – Defines how long the Task may be delayed before completion.
  • SAP_CC_VERSION – Contains the FCc version used. It is only filled in the AddOn version.
  • SAP_CC_SCHEDID (AddOn) – Contains the Schedule Manager ID of the Task. It can be used for the retrieval of the Basic / Detail lists of certain robots.
  • SAP_INTEGRATED (AddOn) – This parameter is passed back to the Financial Closing Cockpit. It defines if the ABAP's used in this automation are registered in the Financial Closing Cockpit.
Note:

The SAP_INTEGRATED parameter will be filled automatically by a validation rule. The check is activated via application customizing.

  • SAP_APPSAPI_STARTED_ACTION – Defines the notification to be used when the Task is started. For more details, see the notifications documentation.
  • SAP_APPSAPI_OVERDUE_ACTION – Defines the notification to be used when the Task is overdue. For more details, see the notifications documentation.
  • SAP_APPSAPI_RUNLIMIT_ACTION – Defines the notification to be used when the Task is running for too long. For more details, see the notifications documentation.
  • SAP_APPSAPI_FINISHED_ACTION – Defines the notification to be used when the Task is finished without errors. For more details, see the notifications documentation.
  • SAP_APPSAPI_ERROR_ACTION – Defines the notification to be used when the Task is finished with errors. For more details, see the notifications documentation.
  • SAP_APPSAPI_CHAIN_GET_OUTPUT – Defines what output is returned to the FCc.
    • A=All output is passed (also from children).
    • M=All output of child tasks which also have this parameter set.
    • F=Only upload the outputs defined in TASK_OUTPUTS.

Group: Infrastructure

  • TASK_TITLE – Defines the TaskDescription so that it becomes clear which task is executed. If it is left empty, the process definition description is used. Additionally, the following is added to the description to easily recognize from where the Task is started: <description> – <SAP_CC_TASK> [<SAP_CC_ CONTEXT_ID> - <TASK_NO> CA=<KOKRS> CC=<BUKRS>]
  • RULE – Validation Rule to apply. An Example for a validation rule on Task-Level would be the TaskDetails which gives an overview of the Task details.

    In Application Customizing default rules can be defined which run for all process definitions.

  • On-Change Action – This action performs the following preparations (Scheduled status only):
    • If Task is a restart, it retrieves and adds any wait & trigger events from original Task that the current did not raise
    • Determine the Task Details and store them on process level
    • Determine the process parameters to be derived as described above
    • Template and Replacement processing
    • Create Events for notifications if required
    • Determine the QueueClosed Processes are executed in queues. A queue can be open or held. While a queue is held, no new processes are started in the queue. to use for this Task. It uses the following rules for that :
    • Retrieve the Queue from the OrgUnit table using the OrgStructure
    • Retrieve the Queue from the SAP System defined via the SAP_SYSTEMS parameter.
  • Pre-Running Action – This action executes the following rules :
    • Determine the Task Description to be shown
  • Post-Running Action – This action provides a mechanism to execute predefined activities on Task List / Task level.
    • Run Validation Rules defined
    • Determine if ABAP programs are registered
    • Cleanup Utility tasks

FCA_SAP_SubProcess_Template

This template can be used to model sub processes which may be included in several process definitions.

Parameters

  • SAP_SYSTEMS – Refer to FCA_FCc_Process_EventClosed An object that symbolises a raised event definition._Template
  • CLIENT – Refer to FCA_FCc_Process_Event_Template
  • SAP_USER_NAME – Refer to FCA_FCc_Process_Event_Template
  • LANGUAGE – Refer to FCA_FCc_Process_Event_Template
  • TASK_TITLE – Refer to FCA_FCc_Process_Event_Template
  • _PARAMETER_TEMPLATE – Refer to FCA_FCc_Process_Event_Template
  • RULE – Refer to FCA_FCc_Process_Event_Template
  • RULE_RESULT – Refer to FCA_FCc_Process_Event_Template