Connecting an Application

Purpose

With this process, the Framework for the Principle of Dual Control (CA-GTF-TS-PDC) offers you the option of releasing objects or operations of your application using a principle of dual. treble or quadruple control.

Use this process if you wish to define an additional release objector if you wish to connect a new application to the Framework for the Principle of Dual Control .

Process Flow

If you wish to connect an application to the Framework for the Principle of Dual Control, you need to carry out the following steps :

  1. Define the name for the release object.

    The maximum length for the name is 10 characters. This name is used as part of the following names:

    • Name of the transfer structure

      Prefix _STR_ release object _RELEASE

    • Names of the function modules

      Prefix _API_ release object _ method _CB

      The maximum length for these names is 30 characters.

    • Names of the parameter transaction and view variants

      Prefix _ release object _REL01, VV_TBCA_REL_RULE_ release object , VV_TBCA_RTW_LINK_ release object

      The prefix should not be more than 4 characters long. It identifies your application (BCA has already been used).

  2. Create the transfer structure. Naming convention: Prefix _STR_ release object _RELEASE

    This structure contains all the fields in the application that can be selected as release attributesin the Customizing settings. The Framework for the Principle of Dual Control uses the release attributes to decide whether an object or operation is relevant for release, and which release procedure is involved. The release attributes also serve as criteria for user determination.

  3. Define the release object in the context of the Framework for the Principle of Dual Control :

    In view B_TBCA_OBJ_CAT make an entry for the release object with the following values:

    Field name

    Required entry

    Object type

    Release object

    Long text

    Description for the release object (anything you want)

    Structure

    Name of the previously defined transfer structure

  4. Make the function modules needed for the release object available (see Functionality and Interfaces for the API Function Modules ).

  5. In view V_TBCA_REL_FM make the entries for the API function modules for the release object for each activity with the following values:

    Field name

    Entry/action

    Object type

    Release object

    Activity

    Activity

    Function module

    Name of the function module that executes the activity

    Function supported

    Set the indicator if the activity is supported by the release object.

  6. Create a parameter transaction for IMG activity Assign Release Object to Release Procedure with the following values:

    Field name

    Entry/action

    Transaction code

    Prefix _ release object _REL01

    Short text

    Assign release object to release procedure

    Start object

    Transaction with parameters (parameter transaction)

    Transaction text

    Keep proposed short text

    Default values for transaction

    BCA_CUS_REL_PROC

    Skip initial screen

    Select

    Default values: Name of the screen field

    P_OBJCAT

    Default values: Value

    Release object

    Using this parameter transaction you define in the application Customizing settings if and when the release object is to be forwarded to the release process and which release procedure is to be chosen on the grounds of which criteria.

  7. For view V_TBCA_REL_RULE create a view variant for IMG activity Assign Release Object to Release Procedure with the following values:

    Field name

    Entry/action

    Table/view

    V_TBCA_REL_RULE

    Maintenance view variant

    VV_TBCA_REL_RULE_ release object

    Due to the length of the name, you can only use part of the release object name

    Short description

    Assign rules to release steps

    Tables/ join conditions: Tables

    V_TBCA_REL_RULE

    View fields: Table fields

    Select all

    Selection conditions: Table fields

    OBJECT_CAT with selection condition EQ ‘ release object

    See also Creating Maintenance View Variants .

    Using this view variant, in the application Customizing settings you define which processors are to receive a work item via the release workflow for which release step.

  8. For view V_TBCA_RTW_LINK create a view variant for IMG activity Assign Release WF and Release Procedure WF to Release Procedures.

    Field name

    Entry/action

    Table/view

    V_TBCA_REL_LINK

    Maintenance view variant

    VV_TBCA_RTW_ release object

    Due to the length of the name, you can only use part of the release object name

    Short description

    Assign workflow template to release procedure of assign release wf and release procedure wf to release procedures

    Tables/ join conditions: Tables

    V_TBCA_REL_LINK

    View fields: Table fields

    Select all

    Selection conditions: Table fields

    OBJECT_CAT with selection condition EQ ‘ release object

    See also Creating Maintenance View Variants .

    Using this view variant, in the sample Customizing settings and/or in the application Customizing settings you assign a release workflow and a release procedure workflow ( subworkflow) to every release procedure of a release object.

  9. Insert the three IMG activities at an appropriate place in the Implementation Guide (IMG).

    General texts PDC_PROCEDURE, PDC_RULE and PDC_WORKFLOW are available to you for documenting these IMG activities.

  10. In the sample Customizing settings, for each release object assign a release workflow and a release procedure workflow (subworkflow) to every useable release procedure.

    To do this you can either use the workflow template provided with the Framework for the Principle of Dual Control (see Release Object ReleaseProcessBCA (General Release Object) or your own template, by copying the one provided and modifying it to suit your requirements.

  11. In the application source text, insert the following calls of the function modules for the Framework for the Principle of Dual Control at the appropriate places:

    Function module

    Insert

    BCA_API_REL_CHECK_ATTRIB checks if the operation/object is relevant for release

    Before the data for release is saved.

    BCA_API_REL_CALL starts the release procedure if the operation/object is relevant for release

    After the data for release is saved.

    This means that for operations involving release, before you save the data you must call the Framework for the Principle of Dual Control (BCA_API_REL_CHECK_ATTRIB) to check whether this operation or object is relevant for release. Then you save the data on the database and call the Framework for the Principle of Dual Control a second time (BCA_API_REL_CALL). With this call, the release procedure (workflow) is started, if applicable. You must always call the Framework for the Principle of Dual Control in this sequence and always using the two function modules. To generate a workflow event, after you call function module BCA_API_REL_CALL you must issue a COMMIT WORK for the application.

    You will find a description of the function modules and the corresponding parameters in the system.

  12. In the application in the Extras menu point, insert the Display Release History function. Use function module BCA_API_REL_HISTORY_DISPLAY to do this. Use the ICON_HISTORY icon if you also want to offer this function via a pushbutton.

    You will find a description of the function module and the corresponding parameters in the system.

Result

You have created the option of releasing the processing of an object in the application using a principle of multiple control.