Skip to Content

SAP Concur Delete activity

Introduction

An SAP Concur Delete activity, using its SAP Concur connection, deletes object data from SAP Concur and is intended to be used as a target to consume data in an operation.

Create an SAP Concur Delete activity

An instance of an SAP Concur Delete activity is created from an SAP Concur connection using its Delete activity type.

To create an instance of an activity, drag the activity type to the design canvas or copy the activity type and paste it on the design canvas. For details, see Creating an activity instance in Component reuse.

An existing SAP Concur Delete activity can be edited from these locations:

Configure an SAP Concur Delete activity

Follow these steps to configure an SAP Concur Delete activity:

Step 1: Enter a name and select an object

In this step, provide a name for the activity and select an object. Each user interface element of this step is described below.

SAP Concur Delete activity configuration step 1

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

  • Select an Object: This section displays objects available in the SAP Concur endpoint.

    Note

    Some objects are supported only for specific versions of the SAP Concur REST API. If the Version selected in the connection does not match the API version that supports that object, an error will occur when loading the data schema in step 2:

    • The Vendors object is supported only for v3.0.

    • The VendorGroup object is supported only for v3.1.

    • 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 or the word Refresh to reload objects from the SAP Concur endpoint. This may be useful if objects have been added 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 name of the object.

      • Description: The description of the object.

    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

Any request or response schemas are displayed. Each user interface element of this step is described below.

SAP Concur Delete activity configuration step 2

  • Data Schemas: These data schemas are inherited by adjacent transformations and are displayed again during transformation mapping.

    The SAP Concur connector uses the SAP Concur REST API selected during connection configuration. Refer to the API documentation for information on the schema nodes and fields.

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

  • 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 Delete activity, complete the configuration of the operation by adding and configuring other activities, transformations, or scripts as operation steps. You can also configure the operation settings, which include the ability to chain operations together that are in the same or different workflows.

Menu actions for an activity are accessible from the project pane and the design canvas. For details, see Activity actions menu in Connector basics.

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

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.