Templates
The described templates are used to created process definitions in the FPA scenario
FCA_FPA_Process_Event_Template
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 theTarget 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 theTarget System determination
mechanism.SID_USER
- This parameter provides an overwrite capability for theSAP_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 contains the Controlling Area.BUKRS
- The value contains the Company code.WERKS
- The value contains the Plant code.TASKLIST_END_DATE
- The value contains the Task List date (also calledUltimo
) inyyyyMMdd
format.TASKLIST_PERIOD
- The value contains the Task List fiscal period in NUMC(3) format.TASKLIST_YEAR
- The value contains the Task List fiscal year.SAP_SYSTEMS
- The value of this field is derived using the following rule :- If the field SID / SID_CLIENT is filled, then the corresponding SAP_SYSTEM/CLIENT is determined and used.
- Use the OrgStructure (KOKRS,BUKRS,WERKS) to retrieve the Target SAP System / Client from the OrgStructure details table.
- Use the default FPA System definitions defined in Application Customizing
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 converted from Global User identification to the Local User ID required for the target system.LANGUAGE
- The value is retrieved from the User Detail of the Target System user defined inSAP_USER_NAME
. If there is no Language defined, then the Language is retrieved from the Organizational Structure.
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. Addition 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>]
_VALIDATION_RULE
- Validation Rule to apply. An Example for a validation rule on Task-Level would be theTaskDetails
which gives an overview of the Task details. Note: In Application Customizing default rules can be defined which run for all process definitions.Pre-Running Action
- This action executes the following rules :- Determine the Task Description to be shown
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 were not raised by the current task.
- 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 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.
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_FPA_Process_Event_TemplateCLIENT
- Refer to FCA_FPA_Process_Event_TemplateSAP_USER_NAME
- Refer to FCA_FPA_Process_Event_TemplateLANGUAGE
- Refer to FCA_FPA_Process_Event_TemplateTASK_TITLE
- Refer to FCA_FPA_Process_Event_Template_PARAMETER_TEMPLATE
- Refer to FCA_FPA_Process_Event_TemplateRULE
- Refer to FCA_FPA_Process_Event_TemplateRULE_RESULT
- Refer to FCA_FPA_Process_Event_Template
financeTopic