Show TOC

Object documentationStandard Task TS04000019: Approve PD Form

 

You use this standard task to send a form to a user for approval. The approver can execute the following functions in the relevant form application:

  • Approve or reject the content of the form. The approver cannot change the content of the form.

  • Return the form to the process initiator (optional)

  • Save a draft (optional)

    Caution Caution

    When a user executes this standard task, the data is not saved in the back-end system.

    End of the caution.

Standard Task: 04000019

ID: Approve

Name: Approve PD (Personnel Development) Form

Structure

Processor Assignment

You can use this standard task for HCM Processes and Forms workflow templates for organizational processes, and store a corresponding agent assignment rule for the workflow steps.

For more information, see Agent Assignment Rules.

Authorization Check

The A (Approve) activity is used for the P_ASRCONT authorization object.

For more information, see Authorization Concept of HCM Processes and Forms.

User Interface Control

When you initiate a work item with this standard task, a form application with the following views is available:

  • Approve

  • Completed

    The user receives a confirmation that the data has been sent successfully. The work item disappears from the user's Universal Worklist.

When the corresponding work item is executed, the following elements are available on the user interface:

  • A form in which the user can check data. The user cannot edit the data.

  • Approve and Reject buttons, which the user can choose to complete the processing of the form. The data is then sent to the workflow environment and the system continues with the next step in the workflow.

  • Save Draft and Back to Author buttons (optional)

Process Control

If you use this task, you must also do the following tasks in the relevant workflow step:

  • Data flow of task container

  • Rule for agent determination with respective data flow to rule container

  • Programming exit CL_HRASR00_POBJ_WF_EXIT

Container Definition: Import Elements

  • Form (FORM) – Mandatory

    This element specifies which form scenario is used when the workflow step is executed. It consists of a structure with the following fields, which you have to define for use with this task:

    • Form Scenario (FORM_SCENARIO) – Mandatory

      Enter the form scenario that is to be used within the workflow step.

    • Form Scenario Version (FORM_SCENARIO_VERSION) – Mandatory

      Enter the version of the form scenario that you want to be used.

    • Do Not Save Directly (SUPPRESS_SAVE) - Mandatory

      You can use this field to override the entries in the SEND_VARIATION element.

      • Enter an X if the data is not to be written to the database even if the value A (Save (Do Not Tolerate Errors)) is set in the SEND_VARIATION element.

      • Enter nothing if the data is to be saved according to the settings in the SEND_VARIATION element.

    Data type (Data Type tab page in the ABAP Dictionary Data Type field): Type name HRASR00_FORM_KEY_ELEMENT

  • Form Scenario View (FORM_SCENARIO_STAGE) - Mandatory

    Enter the scenario step that is to be used for the workflow step. You must have already defined the step in the Create Form Scenario Customizing activity (view cluster HRASR00FSCN).

    When defining the data flow in the workflow container, you can use a value help (F4) for the FORM_SCENARIO_STAGE field. This allows you to access your Customizing entries. You can use the value help in the Workflow column and, in the subsequent dialog box, the value help for the field in the Temporary Check Results of Table column. If the column is not visible, you can use the Enter Constant function.

    Data type (Data Type tab page, ABAP Dictionary Reference field): Structure HRASR00_PROCESS_MODELLING and field FORM_SCENARIO_STAGE

  • Processor role (PROCESSOR_ROLE) – Optional

    Here you enter the role of the processor who generally executes the workflow step. If you do not specify a processor role, the HR Administrator (HRASRA) processor role is assigned in the standard release. It is necessary to enter the processor role, for example, for Data Tracking at the process-step level and for Message Mapping.

    For more information, see Customizing for Personnel Management under Start of the navigation path HR Administrative Services Next navigation step Configuration of Forms/Processes Next navigation step Process Configuration Next navigation step Set Up Processes Next navigation step Determine Processor Roles End of the navigation path.

    Data type (Data Type tab page, ABAP Dictionary Reference field): Structure HRASR00_PROCESS_MODELLING and field PROCESSOR_ROLE

  • Save Draft button (SAVE_DRAFT_BUTTON_VISIBLE) – Optional

    You use this element to specify whether a button is provided to the user to temporarily save the entries in the form. Once the user has temporarily saved the data and the step is not yet completed, the corresponding work item continues to be available to the user in the universal worklist for processing with all previously entered data.

    • X = Save Draft button is visible

      The user can save the current processing status of the form using the Save Draft button.

    • " " = Not visible

      The Save Draft button is not visible and is therefore not available to the user (default setting).

    Data type (Data Type tab page, ABAP Dictionary Reference field): Structure HRASR00_PROCESS_MODELLING and Field BUTTON_IS_ENABLED

  • Back button (BACK_BUTTON_VISIBLE) – Optional

    You use this element to specify whether a button is provided to the user to return a form to the initiator of a process.

    • X = Back to Author button is visible

      The user can return the form to the initiator by choosing the Back to Author button. In this case, the processing status (PROCSTATE, see below) receives the value BACK. Note that you must take account of this behavior in subsequent modeling of the workflow.

    • BLANK = Not visible

      The Back to Author button is not visible and is therefore not available to the user (default setting).

    Data type (Data Type tab page, ABAP Dictionary Reference field): Structure HRASR00_PROCESS_MODELLING and Field BUTTON_IS_ENABLED

Container Definition: Export Elements

  • Processing Status (PROCSTATE) – Optional

    You can use this element to specify that the processing status is to be transferred from the workflow step to the workflow container once the work item is completed (data flow: workflow <- Edit Form step). If the processing status is known in the workflow container, you can process the other workflow steps in accordance with the processing status.

    The processing status can have the following values:

    • APPROVED

      This value is set when the user has chosen the Approve function. ○

    • REJECTED

      This value is set when the user has chosen the Reject function.

    • BACK

      This value is set when the user has chosen the Back to Author function.

    To transfer the processing status to the workflow container, you must have previously created a suitable container element in the workflow container:

    • For example, element = PROCSTATE

    • For example, name = processing status

    • Data type (Data Type tab page, ABAP Dictionary Reference field): Structure HRASR00_PROCESS_MODELLING and field PROCESSING_STATUS

  • Container element notify_via_e-mail - Optional

    You use this container element to specify whether an e-mail notification is sent to the next agent involved in a process. If e-mail notification is set to X = TRUE, an e-mail is sent to the agent, advising them that there is a work item waiting to be processed. They can access the work item directly from the body of the e-mail. If it is set to _ = FALSE, no e-mail is sent; the agent can access work items to be processed in the UWL.

  • Container element BUSINESS_STATUS - Optional

    You use this container element to specify whether the business status is visible to the user in the process browser. If business status is set to X = TRUE, you can see the business status for the request step. If it is set to _ = FALSE, only the processing status is displayed; the business status cannot be seen.