In this article

Overview

You can use this Snap to create a record in the selected Coupa resource, for example accounts, suppliers, approvals, and contracts by using the relevant resource APIs. You can use this Snap only to select the resource in which the record is to be created; all record-related parameters must be passed through an upstream Snap such as the Mapper Snap.

SnapLogic Documentation > Coupa Create > Coupa_Overview.jpg

Prerequisites

Valid Coupa account with appropriate permissions.
Resource parameters compliant with the resource's schema.

Limitations

None.

Snap Views

Type

Format

Number of Views

Compatible Upstream and Downstream Snaps

Description

Input

Document

Min: 1
Max: 1

Mapper Snap
Copy Snap

The record details as a JSON document.

Output

Document

Min: 0
Max: 1

Coupa Read
Document to Binary + File Writer

Details of the record along with the record ID. Level of detail varies according to the configuration of the Response Type field. Each record is assigned a unique ID.

Error

Error handling is a generic way to handle errors without losing data or failing the Snap execution. You can handle the errors that the Snap might encounter while running the Pipeline by choosing one of the following options from the When errors occur list under the Views tab. The available options are:

Stop Pipeline Execution: Stops the current pipeline execution when the Snap encounters an error.
Discard Error Data and Continue: Ignores the error, discards that record, and continues with the rest of the records.
Route Error Data to Error View: Routes the error data to an error view without stopping the Snap execution.

Learn more about Error handling in Pipelines.

Snap Settings

Asterisk (*): Indicates a mandatory field.
Suggestion icon (): Indicates a list that is dynamically populated based on the configuration.
Expression icon (): Indicates whether the value is an expression (if enabled) or static (if disabled). Learn more about Using Expressions in SnapLogic.
Add icon (): Indicates that you can add fields in the fieldset.
Remove icon (): Indicates that you can remove fields from the fieldset.

Field Name	Field Type	Description
Label* Default Value: Coupa Create Example: Coupa Create Users	String	The name for the Snap. We recommend you update the Snap name, if there is more than one of the same Snap in your Pipeline.
Response Type Default Value: all Example: shallow	String	Specifies the level of detail required in the Snap's output. You can configure this keeping in mind the available memory and likely processing time that it would take to execute this Snap. Available options are: all: Output contains all details of the record created. none: No output. limited: Output contains only the ID. shallow: Output contains ID and the direct child attributes of the record. See API Return Formats for more details.
API Path* Default Value: N/A Example: suppliers	String/Expression	The API name associated with the target resource. Select the target resource from the suggestions in the field. Suggestions vary based on the account.
Snap Execution Default Value: Execute only Example: Validate & Execute	Dropdown list	Specifies the execution type: Validate & Execute: Performs limited execution of the Snap (up to 50 records) during Pipeline validation; performs full execution of the Snap (unlimited records) during Pipeline execution. Execute only: Performs full execution of the Snap during Pipeline execution; does not execute the Snap during Pipeline validation. Disabled: Disables the Snap and, by extension, its downstream Snaps.

Example

Creating an Account Type Record

This example demonstrates how to create a record for a specific Coupa account type.

SnapLogic Documentation > Coupa Create > Pipeline.png

Download the example Pipeline.

Parameters for the resource record to be created must be supplied through an upstream Snap. You can use Snaps such as JSON Generator, Mapper, or even File Reader if the parameters are present in the SLDB. In this example, we pass the parameters directly using the Mapper Snap. When you connect a Mapper Snap to the Coupa Create Snap, the selected Coupa resource's schema is not readily available in the Mapper Snap. Validate the Pipeline once to get the target resource schema in the Mapper Snap. After the schema is available, you can map the input data to the corresponding fields.

The Mapper Snap is configured as follows:

SnapLogic Documentation > Coupa Create > Mapper_Settings.png