Ariba P2P Requisition XML Upload

This integration uploads purchase order information from Ariba to SAP Fieldglass.

Connector Overview

Component

Detail

Company Type

Buyer

Version Type

API-V1.0

API-A-V1.0

Format

XML

Prerequisites

Company Details Setting must be turned on for Integration – Ariba P2P Requisition XML Upload.

User role permission must be turned on for Upload Data and Download Data.

Buyer must have system permissions at Ariba ERP System.

Predecessors

Work Order

Statement of Work

Work Order Revision

Statement of Work Response

Projects

Related Connectors

N/A

File Formatting

Data Dictionary

Elements and Attributes

Data Type

Length

Min/Max Occurrences

Value(s)/Format

Description/Use/Field Rules

AribaRequisitionUpdate/ExternalReqId Text 16 1/1

Valid SAP Fieldglass Work Order ID or Statement Of Work ID or Project ID

Examples:

XXXXWO00000001

XXXXTQ00000001

XXXXPJ00000001

 Unique identifier
AribaRequistionUpdate/UniqueName Text 100 0/1   Unique name given to requisition.
AribaRequistionUpdate/PoNumber Text 100 1/1   Purchase Order Number
AribaRequistionUpdate/StatusString Text 100 1/1

Valid values are:

Ordered

Denied

Indicates status of requisition.
AribaRequistionUpdate/Message Text 100 1/1

Valid values are:

Ordered

Indicates status message.

The Ariba P2P Requisition XML Upload XML Schema Definition is also available at the link below if that format is preferred for the description of the connector:

https://xxxx.us.fieldglass.cloud.sap/schema/InSiteWorkOrder.xsd

https://xxxx.us.fieldglass.cloud.sap/schema/InSiteSOW.xsd

https://xxxx.us.fieldglass.cloud.sap/schema/InSiteSOWR.xsd

Unique Identifier

  • ExternalRef ID field

Assumptions/Tips

  • Upload user will have access to the Ariba system since buyer will have Ariba punchout enabled.

Errors

The following errors can occur when processing this upload file:

Possible Errors and Resolutions

Error Message

Resolution

Error in parsing xml data. Please check the xml format.

The XML file contains malformed XML that could not be parsed. Verify the file is well-formed XML and validate it against the AribaRequisitionUpload.xsd schema for your company before uploading again.

Invalid values for ExternalReqId

The value in the ExternalReqId element does not match any active Work Order, Statement of Work, or Project in SAP Fieldglass. Verify the ExternalReqId value is correct and that the referenced object exists and is accessible in your company.

Invalid XML Format specified in the file

The XML cannot be unmarshalled into the expected AribaRequisitionUpdate structure. Ensure the file follows the AribaRequisitionUpload.xsd schema, that all element names are spelled correctly, and that the file is not empty or corrupt.

Missing data for Extrinsic

A mandatory custom field passed as an Extrinsic element is missing from the file. Review the custom field requirements for the referenced Work Order or Statement of Work and include all mandatory Extrinsic elements with valid values.

Missing data for ExternalReqId

ExternalReqId is required. Enter the Work Order, Statement of Work, or Project reference ID in the ExternalReqId element.

Missing data for Message

Message is required when StatusString is DENIED. Enter a rejection reason in the Message element.

Missing data for PoNumber

PoNumber is required when StatusString is ORDERED. Enter the purchase order number in the PoNumber element.

Missing data for StatusType

StatusType is required. Enter one of the accepted values: ORDERED, DENIED in the StatusString element.

SOW {0} is missing punchout info. Push the SOW again or contact SAP Fieldglass.

The Statement of Work referenced in ExternalReqId ({0}) does not have the required punchout flag set. In SAP Fieldglass, open the Statement of Work and push it to Ariba again to resend the punchout request. If the issue persists, contact SAP Fieldglass support.

This record has been archived. Contact your System Administrator if you believe you should have access to the record.

The Work Order, Statement of Work, or Project referenced in ExternalReqId is archived and cannot be updated. Contact your System Administrator to restore access to the record if needed.

Work Order {0} is missing punchout info. Push the Work Order again or contact SAP Fieldglass.

The Work Order referenced in ExternalReqId ({0}) does not have the required punchout flag set for its sequence. In SAP Fieldglass, open the Work Order and push it to Ariba again to resend the punchout request. If the issue persists, contact SAP Fieldglass support.