PUBLIC

Document Version: 2311 – 2023-11

SAP Business Network and SAP Fieldglass

Integration Guide
SAP Business Network
© 2023 SAP SE or an SAP affiliate company. All rights reserved.

THE BEST RUN

Content

SAP Business Network with SAP Fieldglass Integration Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

Key Concepts in Integrating SAP Business Network with SAP Fieldglass . . . . . . . . . . . . . . . . . . . . 4

Information Flow Between SAP Fieldglass and SAP Business Network . . . . . . . . . . . . . . . . . . . . . . . . . . 6

New SAP Fieldglass Suppliers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Helpful Hints About SAP Fieldglass Orders and Invoices on SAP Business Network . . . . . . . . . . . . 9
Support for Tax Invoice Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
Information for Supplier Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

cXML for SAP Fieldglass Orders and Invoices Sent to SAP Business Network . . . . . . . . . . . . . . . . .11
ERP Invoice Copies from SAP Fieldglass . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Reconciled SAP Fieldglass Invoices for ERP Systems Integrated with SAP Business Network . . . . . . . . . . 12
From, To, and Sender Credentials of SAP Fieldglass Orders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Extrinsics to Prevent Suppliers from Acting on SAP Fieldglass Documents. . . . . . . . . . . . . . . . . . . . . . . 12
Tax Invoicing Extrinsics for ERP Invoice Copy Attachments from SAP Fieldglass . . . . . . . . . . . . . . . . . . . 13

Integration of SAP Business Network and SAP Fieldglass . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Basic Steps for Integrating SAP Business Network and SAP Fieldglass . . . . . . . . . . . . . . . . . . . . . . . . . 15
Gather Configuration Information for SAP Business Network and SAP Fieldglass . . . . . . . . . . . . . . . . . . 16
Synchronize Master Data Between the SAP Business Network and SAP Fieldglass . . . . . . . . . . . . . . . . . 17
Configuring SAP Business Network Routing of SAP Fieldglass Invoices. . . . . . . . . . . . . . . . . . . . . . . . . .17
Configuring SAP Fieldglass to Send Data to SAP Business Network . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

Troubleshooting SAP Business Network Integration with SAP Fieldglass . . . . . . . . . . . . . . . . . . . . 19

Issues with a Supplier's Ariba Network ID. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Issues with SAP Fieldglass Invoices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

SAP Business Network and SAP Fieldglass Integration Guide

2 PUBLIC Content
SAP Business Network with SAP Fieldglass
Integration Guide

This guide is for SAP Business Network buyer administrators who need to configure integration between SAP
Business Network with SAP Fieldglass.

Integration between SAP Business Network and SAP Fieldglass lets buyers deliver SAP Fieldglass invoices to the
ERP system through SAP Business Network.

This guide applies to:

• SAP Business Network

Related Guides

SAP Ariba Solutions and SAP Fieldglass Integration Guide

SAP Business Network and SAP Fieldglass Integration Guide

SAP Business Network with SAP Fieldglass Integration Guide PUBLIC 3
Key Concepts in Integrating SAP Business
Network with SAP Fieldglass

Integration between SAP Business Network and SAP Fieldglass enables buyers to use their existing connection
between SAP Business Network and their ERP system to deliver invoices from SAP Fieldglass to the ERP system.

In addition, suppliers gain visibility into their SAP Fieldglass transactions on the SAP Business Network.

Suppliers are not charged for invoices that are sent from SAP Fieldglass to SAP Business Network

This SAP Business Network feature is applicable to buyers using the following document automation features:

• Purchase order automation

• Invoice automation
• Payment automation

 Note

This feature is not applicable to SAP Business Network buyers using SAP Ariba Buying and Invoicing or SAP
Ariba Buying. There is a separate implementation those buyers. For more information, see the SAP Ariba
Buying solutions and SAP Fieldglass integration guide.

When this feature is configured, SAP Fieldglass services procurement spending is tracked in the ERP system and
on SAP Business Network. SAP Fieldglass sends orders and reconciled invoices to SAP Business Network, and
SAP Business Network sends the reconciled invoices to the ERP system, via an adapter, for payment. For non-PO
invoicing, SAP Fieldglass sends reconciled invoices but not order information.

Enabling Integration with SAP Fieldglass

To enable integration between SAP Business Network and SAP Fieldglass, please have your Designated Support
Contact log a service request. An SAP Ariba Customer Support representative will follow up to complete the
request.

Prerequisites

In order to use this feature, the buying organization must meet the following requirements:

• The buyer must be registered on SAP Business Network.

• The buyer must have a subscription to SAP Fieldglass.
• In the SAP Business Network buyer account, the following invoicing rules must be enabled:
• Allow suppliers to send invoices to this account.
• Allow suppliers to send invoice attachments.

SAP Business Network and SAP Fieldglass Integration Guide

4 PUBLIC Key Concepts in Integrating SAP Business Network with SAP Fieldglass
 • Your procurement application can download invoice attachments (MIME multipart messages). (This
rule appears only when the rule Allow suppliers to send invoice attachments is enabled.)
• The buyer must have an SAP Business Network trading relationship with suppliers referenced in SAP Fieldglass
documents.
• Configuring this feature requires several steps in SAP Fieldglass and on SAP Business Network.
• Buyers who want SAP Business Network to send reconciled SAP Fieldglass invoices to the ERP system must
have the appropriate SAP Business Network adapter configured.
• In systems where SAP Fieldglass sends invoice information to SAP Business Network and an external ERP
system pays the invoice, remittance information from the ERP system is sent back to SAP Fieldglass. To
support this flow, your SAP Business Network account must include the following entitlement, which SAP Ariba
sets for you: Upload CSV Payment Proposals/Payment Batch.
• For SAP Business Network buyer accounts that must send documents to multiple end points, the SAP
Business Network account must have the Ariba Open Network option and end point support enabled. (SAP
Ariba sets these options.)

Limitations

• There is no quick enablement for SAP Fieldglass suppliers on SAP Business Network. The supplier must be
registered and have a valid Ariba Network ID in order for SAP Business Network to accept the SAP Fieldglass
order.
• SAP Business Network receives invoice status updates from the ERP system but does not send those status
updates back to SAP Fieldglass.
• Early payment discounts are not supported for SAP Fieldglass invoices.
• SAP Business Network does not handle payment of SAP Fieldglass invoices.
• This feature does not yet support the multi-ERP feature of SAP Business Network (for buyer accounts
integrated with multiple business applications). This is because SAP Fieldglass does not include a system
ID in documents it sends to SAP Business Network. If the SAP Business Network buyer account is set up for
multi-ERP support, documents from SAP Fieldglass are routed to the default system ID.

SAP Business Network and SAP Fieldglass Integration Guide

Key Concepts in Integrating SAP Business Network with SAP Fieldglass PUBLIC 5
Information Flow Between SAP Fieldglass and SAP
Business Network
A diagram and list of steps describe the end-to-end flow of information between SAP Fieldglass and SAP Business
Network once integration is configured in SAP Fieldglass and on SAP Business Network.

Figure 1: Integration Workflow Between SAP Fieldglass and SAP Business Network

The following steps explain the workflow diagram:

1. In SAP Fieldglass, the requester (for example, a hiring manager) creates and submits the work order or SOW in
SAP Fieldglass.
2. The work order or SOW progresses through the approval flow in SAP Fieldglass.
3. When the work order or SOW is approved in SAP Fieldglass:
• If the buyer has configured this feature to treat SAP Fieldglass invoices as PO invoices, SAP Fieldglass
sends the order to the supplier account on SAP Business Network.
• If the buyer has configured this feature to treat SAP Fieldglass invoices as non-PO invoices, SAP Fieldglass
does not send order information to SAP Business Network.
4. SAP Fieldglass sends the work order or SOW to the supplier via the SAP Fieldglass network.
5. The supplier accepts the work order or SOW. The worker or contractor submits timesheets, expense receipts,
schedules, and other documents to SAP Fieldglass.
6. In SAP Fieldglass, the documents submitted by the worker or contractor are matched to the work order or
SOW and submitted for approval.

SAP Business Network and SAP Fieldglass Integration Guide

6 PUBLIC Key Concepts in Integrating SAP Business Network with SAP Fieldglass
7. When the submitted documents are approved, SAP Fieldglass creates an invoice. Any invoice reconciliation
activities occur in SAP Fieldglass.
8. SAP Fieldglass sends the reconciled invoice to SAP Business Network as an ERP copy invoice that includes the
invoice as an attachment. The invoice on SAP Business Network is not editable.
9. If the invoice is a PO invoice, SAP Business Network matches the invoice to the PO using the PO ID.
10. SAP Business Network sends the invoice information to the ERP system in the form of an invoice reconciliation.
11. The ERP system receives the invoice reconciliation and processes payment.
12. SAP Business Network receives payment info from the ERP system, converts it to remittance advice, and
sends it to SAP Fieldglass.

SAP Business Network and SAP Fieldglass Integration Guide

Key Concepts in Integrating SAP Business Network with SAP Fieldglass PUBLIC 7
New SAP Fieldglass Suppliers

New suppliers registering with a buyer on SAP Fieldglass after the initial implementation of this feature must first
register on SAP Business Network and then provide Ariba Network ID (ANID) during the SAP Fieldglass registration
process.

Providing the Ariba Network ID to SAP Fieldglass enables SAP Fieldglass and SAP Business Network to route
documents correctly. When a buyer’s SAP Fieldglass site is integrated with SAP Business Network, suppliers
cannot register with the buyer on SAP Fieldglass without entering a value for the Ariba Network ID.

 Note

SAP Fieldglass does not validate the Ariba Network IDs entered by suppliers during registration. If a supplier
enters an incorrect ID or a meaningless value (as a temporary measure to complete registration, for example),
in order to correct the ID, the supplier must contact SAP Fieldglass with the correct Ariba Network ID in order
for SAP Fieldglass to update the supplier’s company profile. An incorrect supplier Ariba Network ID in SAP
Fieldglass prevents the supplier from getting paid via the integrated system.

SAP Business Network and SAP Fieldglass Integration Guide

8 PUBLIC New SAP Fieldglass Suppliers
Helpful Hints About SAP Fieldglass Orders and
Invoices on SAP Business Network

Orders and invoices sent from SAP Fieldglass to SAP Business Network are treated differently from other orders
and invoices because the actual transactions between buyers and suppliers occur on the SAP Fieldglass network,
not on SAP Business Network.

Purchase Orders

• For orders sent from SAP Fieldglass to SAP Business Network, any revisions that occur in SAP Fieldglass are
also sent to SAP Business Network.
• Because orders from SAP Fieldglass are fulfilled via the SAP Fieldglass network, suppliers and buyers viewing
the order on SAP Business Network see the following message at the top of the order: This purchase order
has already been fulfilled. There is no option for resending a status update.
• The status of the order on SAP Business Network does not reflect any fulfillment activities done by suppliers
via SAP Fieldglass.

Invoices

• Reconciliation of SAP Fieldglass invoices occurs in SAP Fieldglass only, not on SAP Business Network.
• Invoices sent from SAP Fieldglass are in standard invoice format rather than services invoice format.
• SAP Business Network receives invoice information from SAP Fieldglass in the form of ERP invoice copies. The
invoice does not specify a submit method, origin, or source document.
• SAP Business Network invoicing rules are not applied to invoices from SAP Fieldglass, except for the following,
which must be enabled:
• Allow suppliers to send invoices to this account.
• Allow suppliers to send invoice attachments.
• Your procurement application can download invoice attachments (MIME multipart messages). (This
rule appears only when the rule Allow suppliers to send invoice attachments is enabled.)
• On SAP Business Network, PO-based invoices from SAP Fieldglass are matched to POs based on the PO ID
only. The accounting on the invoice can be different from the accounting on the PO. (SAP Business Network
disregards PO accounting.)

SAP Business Network and SAP Fieldglass Integration Guide

Helpful Hints About SAP Fieldglass Orders and Invoices on SAP Business Network PUBLIC 9
Support for Tax Invoice Requirements
Integration between SAP Business Network and SAP Fieldglass can be configured to adhere to the buyer’s tax
invoicing requirements from SAP Fieldglass. The ERP invoice copy that SAP Fieldglass sends to SAP Business
Network includes a tax invoice as an attachment.

Related Information

Tax Invoicing Extrinsics for ERP Invoice Copy Attachments from SAP Fieldglass [page 13]
Calculate Tax for SAP Fieldglass Invoices

Information for Supplier Users

SAP Business Network treats SAP Fieldglass orders and invoices differently from other orders and invoices
because the actual transactions between buyers and suppliers occur on the SAP Fieldglass network rather than on
SAP Business Network.

• SAP Business Network doesn't notify suppliers about SAP Fieldglass orders and invoices.
• Suppliers can't use their SAP Business Network account to create service entry sheets, confirm orders, send
ship notices, or create or edit invoices for orders associated with SAP Fieldglass work orders or SOWs.

SAP Business Network and SAP Fieldglass Integration Guide

10 PUBLIC Helpful Hints About SAP Fieldglass Orders and Invoices on SAP Business Network
cXML for SAP Fieldglass Orders and Invoices
Sent to SAP Business Network

ERP Invoice Copies from SAP Fieldglass [page 11]

Reconciled SAP Fieldglass Invoices for ERP Systems Integrated with SAP Business Network [page 12]

From, To, and Sender Credentials of SAP Fieldglass Orders [page 12]

Extrinsics to Prevent Suppliers from Acting on SAP Fieldglass Documents [page 12]

Tax Invoicing Extrinsics for ERP Invoice Copy Attachments from SAP Fieldglass [page 13]

ERP Invoice Copies from SAP Fieldglass

SAP Fieldglass sends invoices to SAP Business Network as cXML CopyRequest documents (ERP invoice copies).

Depending on how the SAP Fieldglass buyer account is configured, the CopyRequest can include an embedded
invoice (the tax invoice) as an attachment.

There are two sets of credentials involved in each SAP Fieldglass invoice sent to SAP Business Network: One set for
the envelope (the CopyRequest) and one set for the embedded invoice.

The credentials in the header of the CopyRequest are as follows:

• The From credentials indicate the buyer’s Ariba Network ID.

• The To credential indicates the supplier’s Ariba Network ID.
• The Sender credential indicates the system sending the document on behalf of the From entity.
The Sender credential also includes information that designates the invoice as a SAP Fieldglass invoice. This
information is in the UserAgent extrinsic:

 Sample Code

<Sender>
<Credential domain="NetworkID">
<Identity>AN01000000001</Identity>
<SharedSecret>xxxxxxx1z</SharedSecret>
</Credential>
<UserAgent>Fieldglass</UserAgent>
</Sender>

The credentials of the invoice embedded within the CopyRequest are as follows:

• The From credential indicates the supplier’s Ariba Network ID.

• The To credential indicates the buyer’s Ariba Network ID.
• The Sender credential indicates the system sending the document on behalf of the From entity.

SAP Business Network and SAP Fieldglass Integration Guide

cXML for SAP Fieldglass Orders and Invoices Sent to SAP Business Network PUBLIC 11
Reconciled SAP Fieldglass Invoices for ERP Systems
Integrated with SAP Business Network
In configurations where SAP Business Network is integrated with an ERP system, SAP Business Network sends the
SAP Fieldglass reconciled invoices to the ERP system in ProviderDataRequest documents.

The ProviderDataRequest includes the original invoice cXML with a different payload ID and a document
reference to the original invoice. The SAP Business Network account can be configured to include a PDF of the
reconciled invoice as an attachment to the ProviderDataRequest. The ProviderDataRequest is used only
for sending the reconciled invoice to the ERP system. After the reconciled invoice is sent to the ERP system, the
ProviderDataRequest ceases to exist.

From, To, and Sender Credentials of SAP Fieldglass

Orders
In cXML orders sent from SAP Fieldglass to SAP Business Network:

• The From and Sender credentials indicate the buyer's Ariba Network ID.
• The To credential indicates the supplier’s Ariba Network ID.

Extrinsics to Prevent Suppliers from Acting on SAP

Fieldglass Documents
The cXML for SAP Fieldglass orders and invoices contains extrinsic elements that prevent suppliers from taking
action on the document on SAP Business Network and to prevent accumulation of network transaction service
fees.

Purpose on SAP Busi-

Extrinsic Document type Value Location ness Network

AribaNetwork.Leg Order Yes Header Prevent accumulation

acyOrders of network transaction
service fees.

Ariba.collaborat Order No Header Prevents collaboration

ionAllowed on the order.

Ariba.confirmati Order No Header Prevents suppliers from

onAllowed creating order confir-
mations.

SAP Business Network and SAP Fieldglass Integration Guide

12 PUBLIC cXML for SAP Fieldglass Orders and Invoices Sent to SAP Business Network
 Purpose on SAP Busi-
Extrinsic Document type Value Location ness Network

Ariba.invoicingA Order No Header Prevents suppliers from

llowed creating invoices for the
order.

AribaNetwork.Leg Invoice Yes Header Prevents accumulation

acyInvoices of network transaction
service fees and dis-
ables invoice notifica-
tions.

Ariba.SpendCateg Order (within the (Value identifies labor Item (within In orders, prevents sup-
ory SpendDetail ele- or consulting and other SpendDetail ele- pliers from creating
ment only), Invoice services.) ment) ship notices for the or-
der. Can be used to
identify SAP Fieldglass
orders and invoices.

SAP Fieldglass determines the value of the Ariba.SpendCategory extrinsic based on commodity code. Only two
specific commodities are supported: Contingent Labor and Consulting SOW. For any other commodity codes,
SAP Fieldglass uses the value Other Services in the SpendCategory extrinsic.

Following is an example of the Ariba.SpendCategory extrinsic within the SpendDetail element of an order:

 Sample Code

<SpendDetail >
<Extrinsic name="SpendCategory">Contingent Labor</Extrinsic>
</SpendDetail>

Following is an example of the Ariba.SpendCategory extrinsic in an invoice:

 Sample Code

<InvoiceDetailItem>
<Extrinsic name="Ariba.SpendCategory">Contingent Labor</Extrinsic>
</InvoiceDetailItem>

Tax Invoicing Extrinsics for ERP Invoice Copy

Attachments from SAP Fieldglass
When SAP Fieldglass is integrated with SAP Business Network, the ERP invoice copy that SAP Fieldglass sends to
SAP Business Network can include tax invoice extrinsics that carry information about the invoice attached to the
ERP invoice copy so that the invoices can conform to the organization’s tax invoice standards.

The purpose of the extrinsics is to communicate information about tax invoices and supplier self-signed invoices.

SAP Business Network and SAP Fieldglass Integration Guide

cXML for SAP Fieldglass Orders and Invoices Sent to SAP Business Network PUBLIC 13
When configuring SAP Fieldglass for integration with SAP Business Network, an SAP Fieldglass representative
configures which extrinsics are included in the header of the ERP invoice copy when sending SAP Fieldglass
invoices to SAP Business Network.

The following table lists several examples of tax invoicing extrinsics and describes their use in ERP invoice copies
from SAP Fieldglass.

Extrinsic Value when included in SAP Fieldglass ERP invoice copy

taxInvoiceAttachmentName Specifies the file name of the tax invoice attached to the ERP
invoice copy from SAP Fieldglass.

 Note
We recommend that this extrinsic be included for all SAP
Fieldglass accounts configured for tax invoicing.

taxInvoiceNumber Specifies the external invoice number of the attached invoice,

for example, the invoice number assigned by SAP Fieldglass.

taxInvoiceFormat Indicates the format of the tax invoice attachment. Example

values are: PDF, NFE, CFDI, EDIXML, SDI.

taxInvoiceRepresentation Indicates whether the invoice is a tax invoice. If the value is Tax,
the invoice is a tax invoice. This extrinsic is used for recogniz-
ing external tax invoices.

taxInvoiceVerification Indicates the signing status of the tax invoice. It has two possi-
ble values, Signed and Not Signed. This extrinsic is used
for processing external tax invoices.

signatureProvider For invoices that are digitally signed, this field indicates the sig-
nature provider, for example, Self-Signed or the provider
name.

signatureVerifier Indicates the platform that verifies the signature of the invoice
and generates the verification report, for example, BM4, BNG,
Ariba Network. This property is not used for signed cXML.

SAP Business Network and SAP Fieldglass Integration Guide

14 PUBLIC cXML for SAP Fieldglass Orders and Invoices Sent to SAP Business Network
Integration of SAP Business Network and SAP
Fieldglass

SAP Ariba and SAP Fieldglass representatives work together with the buyer to configure this feature. Some steps
require action on the part of the buying organization, some require action on the part of SAP Ariba or SAP
Fieldglass, and some involve the cooperation of multiple parties.

Basic Steps for Integrating SAP Business Network and SAP Fieldglass [page 15]

Gather Configuration Information for SAP Business Network and SAP Fieldglass [page 16]

Synchronize Master Data Between the SAP Business Network and SAP Fieldglass [page 17]

Configuring SAP Business Network Routing of SAP Fieldglass Invoices [page 17]

Configuring SAP Fieldglass to Send Data to SAP Business Network [page 18]

Basic Steps for Integrating SAP Business Network

and SAP Fieldglass
A table lists the basic steps for configuring integration between the SAP Business Network and SAP Fieldglass.

Step Required? Responsible party

Implementation planning and requirements

Make a plan that includes the order in Yes The buyer and members of an SAP Ariba
which the configuration steps are per- and SAP Fieldglass implementation team
formed, the data needed for each sys-
tem, and primary contacts from each
team.

Ensure that the buying organization Yes The buyer

meets the requirements for this feature
before beginning implementation.

Information gathering for connecting solutions

Make sure SAP Fieldglass, SAP Ariba, Yes The buyer and members of an SAP Ariba
and the SAP Business Network buyer ad- and SAP Fieldglass implementation team
ministrator have the access and security
information they need to connect the two
solutions.

Master data synchronization

SAP Business Network and SAP Fieldglass Integration Guide

Integration of SAP Business Network and SAP Fieldglass PUBLIC 15
Step Required? Responsible party

In the buyer’s SAP Business Network ac- Yes SAP Ariba, with the help of the buyer
count, upload any SAP Fieldglass suppli-
ers that are not already associated with
the account.

Enable the suppliers for transacting with Yes SAP Ariba (and the suppliers, who must
the buyer via the SAP Business Network, accept the SAP Business Network invita-
and add the Ariba Network IDs to the tion in order to be enabled)
supplier records in SAP Fieldglass.

SAP Business Network Buyer account configuration

On the SAP Business Network, configure Yes SAP Business Network buyer administra-
an end point for sending invoice reconcili- tor
ation documents to the ERP system.

Enable the SAP Business Network ac- No SAP Ariba

count to send a PDF attachment of the
reconciled SAP Fieldglass invoice to the
ERP system.

SAP Fieldglass administration

Configure SAP Fieldglass to send appli- Yes SAP Fieldglass

cable information to the SAP Business
Network.

Gather Configuration Information for SAP Business

Network and SAP Fieldglass
In order for data to be passed between SAP Business Network and SAP Fieldglass, each solution must have the
access and security information of the other systems involved in the integration.

• Provide the SAP Fieldglass representative with the buyer Ariba Netok ID.
• If SAP Business Network will send invoice information to the ERP system, make sure the SAP Business
Network buyer administrator has the end point URL, security password, and certificate or shared secret for
accessing the ERP system through an SAP Business Network adapter.

Next Steps

SAP Ariba and the buyer work together to synchronize supplier data between SAP Fieldglass and SAP Business
Network.

SAP Business Network and SAP Fieldglass Integration Guide

16 PUBLIC Integration of SAP Business Network and SAP Fieldglass
Synchronize Master Data Between the SAP Business
Network and SAP Fieldglass
When integrating SAP Fieldglass and SAP Business Network, SAP Ariba and the buyer work together to
synchronize data between the systems involved.

• SAP Fieldglass suppliers must be uploaded to the SAP Business Network buyer account.
• The SAP Fieldglass suppliers must be enabled for transacting with the buyer via the SAP Business Network.
This includes supplier acceptance of the SAP Business Network invitation. (Contractors registered on the SAP
Fieldglass network do not need to be on the SAP Business Network.)
• The Ariba Network IDs of the suppliers must be added to the supplier records in SAP Fieldglass.
• The Ariba Network ID and shared secret of the buyer must be provided to SAP Fieldglass.

Next Steps

An SAP Business Network buyer administrator configures document routing for SAP Fieldglass invoice
information.

Configuring SAP Business Network Routing of SAP

Fieldglass Invoices
When an invoice is created in SAP Fieldglass, SAP Fieldglass sends ERP invoice copies to SAP Business
Network. To have SAP Business Network send SAP Fieldglass invoice reconciliation documents to the ERP system
(through an adapter), you create an SAP Business Network end point for the ERP system to receive the invoice
reconciliations.

Prerequisites

End point support must be enabled for the SAP Business Network account. An SAP representative sets this for you.

Context

You can also have SAP Business Network send reconciled invoices to the ERP system. To do so, have an SAP
representative configure your SAP Business Network buyer account to enable the setting Generate an invoice
copy as PDF attachment to the reconciled invoice.

SAP Business Network and SAP Fieldglass Integration Guide

Integration of SAP Business Network and SAP Fieldglass PUBLIC 17
Procedure

1. In the SAP Business Network buyer account, choose Account settings Manage Profile .

The Configuration page opens.

2. Click Business End Points (cXML Setup).

The Configure Business End Points page opens.

3. To create the end point, click Create, provide an end point ID, authentication method, and URL for the ERP
adapter.
4. Select Yes, I want to receive documents through the POST method instead of through the cXML
GetPending method, and click Save.
5. Click Configure Document Routing.
6. For the Invoice Reconciliation document type, select the end point to the ERP adapter, and click OK.

Next Steps

The last step in integrating SAP Fieldglass and SAP Business Network involves initiating the flow of data from SAP
Fieldglass to SAP Business Network.

Configuring SAP Fieldglass to Send Data to SAP

Business Network
When integrating SAP Business Network with SAP Fieldglass, an SAP Fieldglass representative must configure SAP
Fieldglass to send order and invoice data to SAP Business Network.

An SAP Fieldglass representative does the following:

• Enables the option Ariba Supplier Network Integration in the SAP Fieldglass company profile for the buyer.
• Configures SAP Fieldglass to send invoices and, optionally, work orders and SOWs (for PO-based invoicing)
to SAP Business Network. This step involves enabling the appropriate integration adapter and configuring the
integration properties (for example, end points, credentials, and extrinsics).

This document does not cover how to perform configuration tasks in SAP Fieldglass.

SAP Business Network and SAP Fieldglass Integration Guide

18 PUBLIC Integration of SAP Business Network and SAP Fieldglass
Troubleshooting SAP Business Network
Integration with SAP Fieldglass

Troubleshooting SAP Fieldglass integration issues might involve investigation on all the integrated applications.

Issues with a Supplier's Ariba Network ID

One of the steps involved in implementing this feature is establishing a trading relationship between the buyer and
the SAP Fieldglass suppliers on SAP Business Network. If an SAP Fieldglass supplier chooses not to accept the
SAP Business Network invitation, the SAP Fieldglass supplier record won't be associated with an Ariba Network ID,
so orders and invoices involving that supplier will not flow through SAP Business Network.

Suppliers registering with an SAP Fieldglass buyer after the initial implementation of this release must enter their
Ariba Network ID manually during the SAP Fieldglass registration process. If documents are not flowing correctly
to the supplier’s SAP Business Network account, it might be because the supplier did not enter the correct Ariba
Network ID.

Related Information

New SAP Fieldglass Suppliers [page 8]

Issues with SAP Fieldglass Invoices

Here are some tips for correcting issues with invoices from SAP Fieldglass.

Invoice Error Correction

For invoice reconciliation issues with invoices sent from SAP Fieldglass, conduct troubleshooting in SAP Fieldglass.

To correct the error in SAP Fieldglass, the user creates a new invoice.

 Note

If the new invoice in SAP Fieldglass will have the same invoice number as the original invoice, SAP Business
Network must be configured to allow reuse of invoice numbers. The SAP Business Network buyer administrator

SAP Business Network and SAP Fieldglass Integration Guide

Troubleshooting SAP Business Network Integration with SAP Fieldglass PUBLIC 19
 can allow reuse of invoice numbers by turning on the transaction rule Allow suppliers to reuse invoice
numbers.

Error Handling Workflow for ERP Rejection of SAP Fieldglass Invoices

This information is applicable only if SAP Business Network is integrated with SAP Fieldglass without SAP Ariba
Procurement solutions.

Following are two examples of situations that might cause an external ERP system to reject an SAP Fieldglass
invoice:

• Tax reconciliation: In some cases, the external ERP system handles tax-related invoice reconciliation. However,
with SAP Fieldglass invoices, all invoice reconciliation occurs in SAP Fieldglass. If there’s a difference in the way
the ERP system and SAP Fieldglass handle tax-related invoice reconciliation, the ERP system might reject the
SAP Fieldglass invoice.
• Invoices with an amount of zero: SAP Fieldglass can generate invoices with a rate of zero for statements of
work (SOWs) that track resources and hours but not expenses. Some ERP systems reject invoices with amount
of zero.

The following high-level steps describe what happens when the ERP system sends an error rejecting an invoice that
originated in SAP Fieldglass.Detailed steps follow each of the following diagrams.

Figure 2: Error Handling Workflow for ERP Rejection of SAP Fieldglass Invoices

1. The external ERP system receives the invoice information in the form of a provider data request from SAP
Business Network.
2. The ERP system validates the invoice information, rejects it, and sends an error message to SAP Business
Network.
3. SAP Business Network receives the status update and identifies the corresponding invoice as an SAP
Fieldglass invoice through the extrinsic Ariba.SpendCategory, which is set to Contingent Labor.
4. SAP Business Network reverses the corresponding purchase order for the invoiced amount and sends the
status update to SAP Fieldglass. The status update includes the reason for the error and states that the invoice
needs to be corrected in SAP Fieldglass.
5. SAP Fieldglass acknowledges receipt of the error and reverses the purchase order for the invoiced amount. The
error is posted in a comment on the invoice in SAP Fieldglass.

SAP Business Network and SAP Fieldglass Integration Guide

20 PUBLIC Troubleshooting SAP Business Network Integration with SAP Fieldglass
6. In SAP Fieldglass, a user corrects the error and submits a new invoice document.
7. The invoicing flow continues as usual.

SAP Business Network and SAP Fieldglass Integration Guide

Troubleshooting SAP Business Network Integration with SAP Fieldglass PUBLIC 21
Important Disclaimers and Legal Information

Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:

• Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements
with SAP) to this:

• The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.

• SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

• Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering an SAP-hosted Web site. By using such links,
you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.

Videos Hosted on External Platforms

Some videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any
advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within the
control or responsibility of SAP.

Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by
SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use the
experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your feedback
(e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and
phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example
code unless damages have been caused by SAP's gross negligence or willful misconduct.

Bias-Free Language
SAP supports a culture of diversity and inclusion. Whenever possible, we use unbiased language in our documentation to refer to people of all cultures, ethnicities, genders,
and abilities.

SAP Business Network and SAP Fieldglass Integration Guide

22 PUBLIC Important Disclaimers and Legal Information
SAP Business Network and SAP Fieldglass Integration Guide
Important Disclaimers and Legal Information PUBLIC 23
www.ariba.com

Copyright © 2023 Ariba, Inc. All rights reserved.

This documentation, as well as the Ariba solutions, software and/or

services described in it, contain proprietary information. They are
provided under a license or other agreement containing restrictions on
use and disclosure and are also protected by copyright, patent and/or
other intellectual property laws. Except as permitted by such agreement,
no part of the document may be reproduced or transmitted in any form
by any means, electronic, mechanical or otherwise, without the prior
written permission of Ariba, Inc.

Ariba, Inc. assumes no responsibility or liability for any errors or

inaccuracies that may appear in the documentation. The information
contained in the documentation is subject to change without notice.

Ariba and Ariba products and services mentioned herein as well as

their respective logos are trademarks or registered trademarks of
Ariba, Inc. in the United States and other countries. Please see http://
www.ariba.com/legal/trademarks for additional trademark information
and notices.

Ariba Sourcing solutions (On Demand and software) are protected

by one or more of the following patents, including without limitation:
U.S. Patent Nos. 6,199,050; 6,216,114; 6,223,167; 6,230,146; 6,230,147;
6,285,989; 6,408,283; 6,499,018; 6,564,192; 6,871,191; 6,952,682;
7,010,511; 7,072,061; 7,130,815; 7,146,331; 7,152,043;7,225,152; 7,277,878;
7,249,085; 7,283,979; 7,283,980; 7,296,001; 7,346,574; 7,383,206;
7,395,238; 7,401,035; 7,407,035; 7,444,299; 7,483,852; 7,499,876;
7,536,362; 7,558,746; 7,558,752; 7,571,137; 7,599,878; 7,634,439;
7,657,461; 7,693,747; 8,364,577; and 8,392,317. Patents pending.

Other Ariba product solutions are protected by one or more of the

following patents:

U.S. Patent Nos. 6,199,050, 6,216,114, 6,223,167, 6,230,146, 6,230,147,

6,285,989, 6,408,283, 6,499,018, 6,564,192, 6,584,451, 6,606,603,
6,714,939, 6,871,191, 6,952,682, 7,010,511, 7,047,318, 7,072,061,
7,084,998; 7,117,165; 7,225,145; 7,324,936; 7,536,362; 8,364,577; and
8,392,317. Patents pending.

Certain Ariba products may include third party software or other

intellectual property licensed from a third party. For information
regarding software or other intellectual property licensed from a third
party, go to http://www.ariba.com/copyrights.cfm.

THE BEST RUN