Ariba P2P/P2O (Using Operational Reporting API)
Run Mode: BACKGROUND AND DIALOG Aggregation: NOT SUPPORTED Iteration: NOT SUPPORTED Duplicate Check: NOT SUPPORTED
Metadata retrieval: SUPPORTED Extraction Strategy: INDUVIDUAL SELECTION AND KEY BASED SELECTION Special Permissions: NONE
This source type generates an openAPI query, extracts data via the Operational Reporting API, compares data in SAP Solution Manager.
The Operational reporting API for procurement enables you to extract and report on the transactional procurement data that you need to make operational decisions, such as invoices to pay or purchase requisitions that need approval.
Parameters
The following parameters must be entered:
| Parameter | Description |
|---|---|
| OAuth Destination | RFC connection to the authentication service which is an HTTPS service which the username and password must be saved which will generate the token |
| OpenAPI Destination | The other destination to be created will be the service to the HTTP service which holds the Operational Reporting API. |
| Realm | The Ariba Realm for the P2P/P2O service |
| API Key | API Key of the application |
The following fields are non-editable and generated by the tool | |
| Query | OpenAPI query generated from the data model. |
Metadata
The CDC Source type for P2P/P2O provides the following tables.
The tables are:
- CDC_CopyOrder
- CDC_DirectOrder
- CDC_ERPOrder
- CDC_Invoice
- CDC_InvoiceRequisition
- CDC_Recipt
- CDC_Requisition
Each table has custom fields pertaining to the type and all tables have few fields in common:
- createDate
- updateDate
- status
Only one date field can be selected at a given time. By default, all statuses are selected
Filters
The following fields are filterable using CDC:
| Field Name | Object filter supported? | Instance filter supported? | Combine with |
|---|---|---|---|
createDate and updateDate
| Date/Time must be given in the format: YYYY-MM-DDTZHH:MM and must always be a range and the timespan cannot be more than 31 days and not more than 30 days in the past | Date/Time can use relative time filters like $TODAY. | All |
status
| Depending on the table it can have different statuses. | No | All |
Supported filter Values for status
| Document type | Status |
|---|---|
| Requisition |
|
| Purchase order including ERPOrder, DirectOrder, and CopyOrder |
|
| Receipt |
|
| Invoice |
|
| Invoice Reconciliation |
|
Limitations
Due to the CDC Source type making use of the API, it is limited in a few ways. These are:
- When the ARIBA source type is a primary source type, the createDate/updateDate filter is mandatory and must be between two time frames and cannot be more than 30 days in the past. Relative time filters are advised.
- Filters can only be applied to the fields as detailed in the filters section. Other combinations are not possible.
View creation on Ariba P2P/P2O
The cross-database comparison for Ariba P2P/P2O works with views provided from the Operational Reporting API. Not all views are supported however. We make use of few custom views for each document type. When the comparison is run, the tool tries to create a view using the reporting API, this view is created depending on the date field selected. For example, if you select the view CDC_Requisitions and select the date filter as create_date, a custom view will be created with the CDC_Requisitions_CR. This view will then be used for extracting data. Please note that the view will be created only once when the comparison is successfully run for the first time.