Configuring SAP Ariba templates (for asynchronous APIs)
The SAP Ariba data extraction for asynchronous API's (Procurement, Sourcing, Analytical Reporting) is based on either Standard View Templates or Custom View Templates.
Reporting view templates are used to specify the filters that determine what data will be returned in response to an API request. A reporting view template specifies the type of transaction to report on, the reporting fields to be included in the API response, and selection filters to select relevant transactions for inclusion.
When deciding which template type you should use:
Standard view template | Custom view template | |
|---|---|---|
Columns | Fixed set of columns | All columns accessible via API |
Benefits | No missing records due to column selection. | Ability to customize columns. |
Points to consider | May miss relevant columns. | Can cause invalid JSON response leading to missing records. |
Standard view templates
Standard View Templates only contain the absolute standard columns which exist in every SAP Ariba system.
Using the standard view template can help to speed up the extraction and avoid the internal server error and invalid response format error.
However, this of course comes with limiting the number of available fields.
In order to enable standard templates, you need to create a new table execution configuration in the data connection for each table:
If standard templates are enabled, only the standard columns will be extracted.
Custom view templates
Custom view templates are used as default and include all via the API available columns in the respective SAP Ariba system.
As the available columns for this scenario depend on the respective SAP Ariba system, a generally applicable overview over all tables together with their columns cannot be provided.