In this article

Overview

You can use this Snap to execute the SAP Business API (BAPI) with the given input data. The BAPI input schema and output schema must correctly map data into the SAP BAPI.

Snap Type

SAP Execute Snap is a Write-type Snap.

Prerequisites

Have the SAP BASIS administrator setup the user to be used in the appropriate SAP clients with certain set of authorizations. To execute a BAPI as part of your application program, you must have the appropriate authorizations set up in respective master records. The documentation provided with the BAPI contains information about the required authorizations. Any attempts to execute a BAPI that fail as a result of insufficient authorization are reported back to the calling application.

Limitations and Known Issues

None.

Support for Ultra Pipelines

Works in Ultra Pipelines. 

Snap Views

Snap Settings

Image Removed

Field Name		Field Type	Description
Label* Default Value: SAP Execute Example: SAP BAPI Create Orders		String	Specify a unique and meaningful name for the Snap.
BAPI List configuration	Use this field set to configure the list of BAPIs to return. This field set contains the following fields.
	BAPI List config key Default Value:OBJECTTYPE Example: RELEASED_FUNC	Dropdown list	Select a key to configure the BAPI list that is being returned. The available options are: OBJECTTYPE SHOW_RELEASE BAPIS_POTENTIAL BAPIS_NEW BAPIS_OLD RELEASED_BAPI RELEASED_FUNC
	BAPI List config value	String	Define a value to configure the BAPI list that is being returned. Learn more about object types.
BAPI* Default Value: N/A Example: BAPI_MONITOR_GETLIST		String/Expression/Suggestion	Specify the BAPI on the SAP server to be executed. This is the ABAP name.
Start Stateful Call Sequence Default Value: Deselected		Checkbox	Select this checkbox to create a stateful session for calling one (or more) BAPIs. Note A Session ID is required if you want to create a stateful call sequence. Info Ensure to select this checkbox for the Snap where you define your first BAPI call in the Pipeline. Do not select the Commit after BAPI execute checkbox for this Snap, to extend the stateful session and call more BAPIs using this Pipeline (downstream to this Snap). 'Sequence' implies that the output from a BAPI call is needed for the next BAPI call to run.
Commit after BAPI execute Default Value: Deselected		Checkbox	Select this checkbox to end the stateful session and commit when no exception is raised; else, the BAPI controls the commits. Info Ensure to select this checkbox for the Snap where you define your last BAPI call in the Pipeline. Do not select the Start Stateful Call Sequence checkbox for this Snap. Do not select both Start Stateful Call Sequence and Commit after BAPI execute checkboxes for all other BAPI calls between the first and the last calls in the sequence. For example, Second BAPI call in a 3-call sequence; Second, Third, and Fourth BAPI calls in a 5-call sequence.
Session ID Default Value: [None] Example:xyz987		String/Expression	Specify the string to identify a specific session. All Snaps in a specific stateful call sequence must be in the same session ID, and there should be only call sequence running in a session at a time. If you do not provide any session ID, the Snap runs in its own session.
Date conversion format Default Value: yyyyMMdd Example: yyyyMMdd		String/Expression	Specify the format to convert string input values into SAP date/datetime fields in SimpleDateFormat. If you do not specify any value, then no conversion is done and the SAP client displays an error when an input view string is mapped to SAP date/datetime field.
Output date time as Text Default Value: Deselected		Checkbox	Select to output date and time as a String data type instead of a DateTime object.
Error handling	Use this field set to define error path and values for handling errors. If any error paths and their error values match a corresponding value in the output document, then the document is routed to the error view (if enabled), or the Snap fails (if error view is disabled). If you do not define the error handling, the Snap will not by default fail or route anything to the error view if the RETURN[*].TYPE value is 'E'.
	Error path Default Value: $RETURN[*].TYPE Example: $RETURN[*].TYPE	String/Expression	Specify the error path to which the errors should route.
	Error value Default Value: E Example: R	String/Expression	Specify the value for the error.
Max request attempts* Default Value: 3 Example:5		Integer	Specify the maximum number of SAP connection attempts to make in case of a failure. When you specify 0, the Snap makes infinite connection attempts.
Request retry interval Default value: 5 Example: 5		Integer	Specify the time in seconds to wait before retrying the request.
Route errors Default value: Deselected		Checkbox	Select this checkbox to write configuration errors to the error view. If the error is non-recoverable, the errors (especially connection errors such as exception handling) are routed to the error view with relevant information.
Reload Function Metadata Default value: Deselected		Checkbox	Select this checkbox to reload the metadata (latest schema) for the current BAPI function before executing the BAPI function. Note Loading of metadata may take some time depending on the network speed.
Snap Execution Default value: Execute only Example: Validate & Execute		Dropdown list	Multiexcerpt include macro name Execution_Detail_Write page SOAP Execute

Examples

The following examples demonstrate how to retrieve data, insert data in SAP using the applicable BAPI, and how to display an error.

[
    {
        "ITM_NUMBER": "1",
        "ORDER_HEADER_IN": {
            "SALES_ORG": "3020",
            "DIVISION": "00",
            "DISTR_CHAN": "30",
            "DOC_TYPE": "TA",
            "PURCH_NO_C": "000004454"
        },
        "PARTN_NUMB": "0000003041",
        "PARTN_ROLE": "AG"
    }
]

Expand
title Sequence of BAPI calls in a Pipeline
The following Pipeline demonstrates a sequence of 3 BAPI calls on service notifications using an SAP instance. Download this Pipeline. In this example Pipeline, a Mapper (Feed Notification Data) is used to prepare the sample attributes for the notification. The output displays the notification attributes. We are using three SAP Execute Snaps to call the following BAPI functions in that sequence. BAPI_SERVNOT_CREATE : To create a service notification using Create Svc Notification Snap. BAPI_SERVNOT_SAVE : To save a service notification using SAP Execute Snap. BAPI_TRANSACTION_COMMIT: To execute external commit when using BAPIs using Save Svc Notification Snap. SAP Execute Snap to call BAPI_SERVNOT_CREATE and create an SAP service notification. SAP Execute Snap to call BAPI_SERVNOT_SAVE and save the SAP service notification. Select the Start Stateful Call Sequence check box to indicate the   beginning of the BAPI sequence. Do not select the Commit after BAPI execute check box. Do not select both the checkboxes in this Snap, as this BAPI is an intermediate call in the BAPI sequence. Mapper Snap to extract the notification number from the saved notification. SAP Execute Snap to call BAPI_TRANSACTION_COMMIT and commit  transaction (save service notification). JSON Formatter Snap to format the output after committing the transaction. Do not select the Start Stateful Call Sequence check box. Select the Commit after BAPI execute check box in this Snap to  indicate the end of the BAPI sequence. File Writer Snap to write the formatted output into a file New_BAPI_Seq_PL_Output.JSON

Downloads

Related Content

• BAPIs