Skip to end of metadata
Go to start of metadata

Introduction

An SAP Concur Create activity creates an object into an SAP Concur endpoint and is intended to be used as a target to consume data in an operation. After configuring an SAP Concur connection, you can configure as many SAP Concur activities as you like for each SAP Concur connection.

Creating an SAP Concur Activity

From the design canvas, open the Connectivity tab of the design component palette:

Connectivity tab

Use the Show dropdown to filter on Endpoints, and then click the SAP Concur connection block to display activities that are available to be used with an SAP Concur connection:

SAP Concur activities

To create an activity that can be configured, drag an SAP Concur Create activity from the palette to the operation.

For more information about the parts of an operation and adding activities to operations, see Operation Creation and Configuration.

Configuring an SAP Concur Create Activity

Follow these steps to configure an SAP Concur Create activity:

Step 1: Enter a Name and Select an Object

SAP Concur Create Activity Configuration Step 1

  • Name: Enter a name to use to identify the SAP Concur Create activity. The name must be unique for each SAP Concur Create activity and must not contain forward slashes (/) or colons (:).

  • Select an Object: This section displays objects available in the SAP Concur endpoint. When reopening an existing activity configuration, only the selected object is displayed instead of reloading the entire object list.

    • Selected Object: After an object is selected, it is listed here.

    • Search: Enter any part of the object name into the search box to filter the list of objects. The search is not case-sensitive. If objects are already displayed within the table, the table results are filtered in real time with each keystroke. To reload objects from the endpoint when searching, enter search criteria and then refresh, as described below.

    • Refresh: Click the refresh icon Refresh icon or the word Refresh to reload objects from the SAP Concur endpoint. This may be useful if you have recently added objects to SAP Concur. This action refreshes all metadata used to build the table of objects displayed in the configuration.

    • Selecting an Object: Within the table, click anywhere on a row to select an object. Only one object can be selected. The information available for each object is fetched from the SAP Concur endpoint:

      • Object Name: The object name from SAP Concur.

      • Description: The object description from SAP Concur.

    TIP: If the table does not populate with available objects, the SAP Concur connection may not be successful. Ensure you are connected by reopening the connection and retesting the credentials.

  • Save & Exit: If enabled, click to save the configuration for this step and close the activity configuration.

  • Next: Click to temporarily store the configuration for this step and continue to the next step. The configuration will not be saved until you click the Finished button on the last step.

  • Discard Changes: After making changes, click to close the configuration without saving changes made to any step. A message asks you to confirm that you want to discard changes.

Step 2: Review the Data Schemas

SAP Concur Create Activity Configuration Step 2

  • Data Schema: The request and response data schemas for SAP Concur are displayed. If the operation uses a transformation, the data schemas are displayed again later during the transformation mapping process, where you can map to target fields using source objects, scripts, variables, custom values, and more.

    The SAP Concur connector uses the SAP Concur REST API v3. Refer to the API documentation for information on the schema fields.

    • Request:

      Request Schema Field/NodeNotes
      EntityNode of the entity
      UserLogin ID of the user performing the update
      AttendeeNode of the attendee
      CompanyName of attendee's Company
      Custom 19Custom field data
      Custom 18Custom field data
      ExternalIDUnique identifier assigned to attendee
      Custom 13Custom field data
      Custom 12Custom field data
      Custom 11Custom field data
      Custom 10Custom field data
    • Response:

      Response Schema Field/NodeNotes
      EntityNode of the entity
      indexThis value is used to identify the record
      ResponseNode of the response
      IDThe unique identifier of the resource
      URIThe URI to the resource
      ErrorNode of the error
      MessageThe error message
      Server-TimeTime the error was generated, based on the SAP Concur server's time zone
      IdID of the error within SAP Concur
  • Refresh: Click the refresh icon Refresh icon or the word Refresh to regenerate schemas from the SAP Concur endpoint. This action also regenerates the schema in other locations throughout the project where the same schema is referenced, such as in an adjacent transformation.

  • Back: Click to temporarily store the configuration for this step and return to the previous step.

  • Finished: Click to save the configuration for all steps and close the activity configuration.

  • Discard Changes: After making changes, click to close the configuration without saving changes made to any step. A message asks you to confirm that you want to discard changes.

Next Steps

After configuring an SAP Concur Create activity, complete the configuration of the operation by adding and configuring other activities, transformations, or scripts as operation steps. You can also configure an operation's operation settings, which include the ability to chain operations together that are in the same or different workflows.

After an SAP Concur activity has been created, menu actions for that activity are accessible from the project pane in either the Workflows or the Components tabs, and from the design canvas. See Activity Actions Menu for details.

SAP Concur Create activities can be used as a target with these operation patterns:

Other patterns are not valid using SAP Concur Create activities. See the validation patterns on the Operation Validity page.

A typical use case is to use an SAP Concur Create activity in the Two-Transformation Pattern. In this example, the first transformation (SAP Concur Create Request) creates a request structure that is passed to the SAP Concur Create activity. The second transformation (SAP Concur Create Response) receives the response structure, which is then written to a variable by a Variable Write activity (Write SAP Concur Create Response) and a message is then logged by the Write to Operation Log script:

SAP Concur Create operation

To use the activity with scripting functions, write the data to a temporary location and then use that temporary location in the scripting function.

When ready, deploy and run the operation and validate behavior by checking the operation logs.

  • No labels