Create an SAP Transaction with More than One Method

To run an SAP transaction that uses more than one SAP function, do the procedure in this topic.

Figure: General Configuration screen

General Configuration screen
Figure: SAP Configuration screen

SAP Configuration screen
Figure: General Configuration screen

General Configuration screen

Prerequisites

Good to Know

How to Start

  1. Open Process Builder.

    For information about how to open this screen, refer to Process Builder.


    Open Process Builder
  2. In Process Builder, in the Activity Library, open the SAP Integration tab.

    Open SAP Integration
  3. On the SAP Integration tab, drag the Begin Transaction activity onto your process.

    Drag Begin Transaction

Procedure

  1. Complete the fields on the General Configuration screen.

    For more information, refer to Configure General Options for a SAP Activity.

  2. To complete the configuration, click OK.
  3. On the SAP Integration tab, drag the Call Function Call SAP Function icon activity onto your process immediately after your Begin SAP Transaction activity
  4. Complete the fields on the General Configuration screen.

    For more information, refer to Configure General Options for a SAP Activity.

  5. Click Call Function Call SAP Function icon.
  6. On the SAP Configuration screen, in the SAP field, select your SAP access token.

    To create a new access token, click Create Add Token icon. For more information, refer to Access Token for SAP.

  7. Complete this field as necessary.
    Field NameDefinition

    BAPI Method Name
    Function:
    Specifies the name of the BAPI method.
    Accepted Values:
    A valid BAPI method name.

    Click the Schema Mapping Schema Mapping icon button to open the BAPI Method Search Results screen and select a method.

    Default Value:
    None
    Accepts Process Data Variables:
    No
    Limitations:

    Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?

  8. To connect the input data to the SAP system to your process schema, complete this field as necessary:
    Field NameDefinition

    Input Mapping
    Function:
    Connects the SAP API input parameter to your process schema.
    To Open this Field:
    1. On the SAP Configuration screen, click the Input tab.
    Accepted Values:
    Click the Schema Mapping Schema Mapping icon button to open the Schema Mapper screen.

    Use this screen to connect the input to the data model for your process.

    Default Value:
    None
    Example:
    Refer to:
  9. To connect output data from the SAP function to your process, complete this field as necessary:
    Field NameDefinition

    Output Mapping
    Function:
    Connects the SAP API output parameter to your process schema.
    To Open this Field:
    1. On the SAP Configuration screen, click the Output tab.
    Accepted Values:
    Click the Schema Mapping Schema Mapping icon button to open the Schema Mapper screen.

    Use this screen to connect the output to the data model for your process.

    Default Value:
    None
    Example:
    Refer to:
  10. (Optional) To connect to the SAP database with the credentials of the user who completes the eForm, complete these fields as necessary.

    For more information, refer to Get Data from SAP with a Secure User Account.

    Field NameDefinition

    Use end user credentials from secure credential store
    Function:
    Specifies to connect to the SAP database with the credentials of the user who completes the eForm.

    This improves the security and traceability of an SAP transaction.

    The runtime app user must have an SAP user account.

    To Open this Field:
    1. On the SAP Configuration screen, click the Advanced Configuration tab.
    Accepted Values:
    • Selected - Lets you use the credentials of the specified user to connect to SAP database.
    • Deselected - Does not let you use the credentials of the specified user.
    Default Value:
    Deselected

    User Name
    Function:
    Specifies the user name of the person whose credentials are used to connect the SAP database.
    To Open this Field:
    1. On the SAP Configuration screen, click the Advanced Configuration tab.
    2. Click User Name.
    Accepted Values:
    Default Value:
    None
    Accepts Process Data Variables:
    Yes

    Clear SAP credentials from secure credential store after successful completion of the task
    Function:
    Deletes the SAP user password in the AgilePoint database after the task is complete.

    By default, the password is encrypted when it is stored in the AgilePoint database, and is deleted when the process instance is complete.

    To Open this Field:
    On the SAP Configuration screen, click the Advanced Configuration tab.
    Accepted Values:
    • Selected - Deletes the user password from the AgilePoint database after the task is complete.
    • Deselected - Deletes the password when the process instance is complete.
    Default Value:
    Deselected
  11. On the SAP Integration tab, drag the End Transaction End SAP Transaction icon activity onto your process immediately after your last Call SAP Function activity
  12. Complete the fields on the General Configuration screen.

    For more information, refer to Configure General Options for a SAP Activity.

  13. To complete the configuration, click OK.