SAP Offline Word Template - wiki.myftp.orgwiki.myftp.org/sap/bp/.../DSF_S4HANA1709_BB_ConfigGuide_EN_XX.d… · Web viewIt comprises settings in SAP S/4HANA system such as the maintenance

Configuration GuideSAP S/4HANAMai 2017English

CUSTOMER

Ariba Network and Backend Customizing

Table of Contents1 Purpose 3

2 Preparation 42.1 Prerequisites 4

3 Configuration 53.1 Default Transaction Rules 5

3.1.1 Purchase Order Rules 53.1.2 Ariba Buyer Contracts Site Setup Rules 63.1.3 Order Confirmation and Ship Notice Attachment Rules 73.1.4 Quick Enablement Rules 73.1.5 Order Confirmation and Ship Notice Rules 83.1.6 Service Sheet Rules 123.1.7 Invoice Rules 123.1.7.1 General Invoice Rules 123.1.7.2 PO Invoice Field Rules 143.1.7.3 PO and Non-PO Invoice Field Rules 153.1.7.4 Invoice Address Rules 163.1.7.5 Blanket Purchase Order Invoice Rules 173.1.7.6 Invoice Payment Rules 183.1.7.7 VAT Rules 193.1.7.8 Online Invoice Form Rules 203.1.8 D-U-N-S Number Rule 213.1.9 Invoice PDF 21

3.2 Business Application IDs 223.3 CXML Setup 223.4 Supplier Enablement 23

3.4.1 Establish Relationship 233.4.2 Assign Private ID 24

4 Manual SAP S/4HANA System Configuration for the Ariba Network Integration 254.1 Define Basic Message Settings 254.2 Schedule job 254.3 Define Credentials and End Points for Ariba Network 264.4 Assign Network ID to Company Codes 264.5 Map Company Code for Invoice Verification 274.6 Map Tax Codes for Invoice Verification 274.7 Map Tax Categories for CC Invoice 284.8 Output Control 29

4.8.1 BRF+ Settings 294.8.2 NAST Settings 304.8.2.1 Define Conditions for Output Control 314.8.2.2 Map Application and Output Type to cXML Message 32

2

CUSTOMER © 2015 SAP SE or an SAP affiliate company. All rights reserved.

Ariba Network and Backend Customizing Table of Contents

5 Manual Build Steps 33

Typographic Conventions 34

Ariba Network and Backend Customizing Table of Contents

CUSTOMER© 2015 SAP SE or an SAP affiliate company. All rights

reserved. 3

1 PurposeThis document describes the required settings for an Ariba Network Buyer Account integrated with SAP S/4HANA system. It comprises settings in SAP S/4HANA system such as the maintenance of the Ariba Network ID along with a password as well as settings in the Ariba Network buyer account.The SAP S/4HANA system to Ariba Network integration supports the exchange of purchase orders, supplier invoices and invoice status updates.

4


Ariba Network and Backend Customizing Configuration

2 Preparation

2.1 PrerequisitesYou have access to your Ariba Network buyer account. This includes: The Ariba account's Ariba Network ID (ANID). This is an identification of your account, typically in

a form like: AN0103183749 or similar The logon credentials (user and password) for browser access to the Ariba account. The shared secret, used for machine to machine communication when SAP S/4HANA system

connects to the Atiba Network

NotePlease make sure that you did the setup of the technical integration with the Ariba network, described in the document "Technical Integration Configuration - Integration with Ariba Network" (respective "DSE_S4HANAX_BB_ConfgGuide_EN_XX"), prior to the settings in this configuration guide. For more information see the Administration Guide for the Implementation of SAP S/4HANA, on premise edition, which is linked in the content library (included in the documentation package).

Ariba Network and Backend Customizing Purpose


reserved. 5

3 ConfigurationThe Ariba Network can be configured to meet customer requirements. This chapter describes settings in the Ariba Network Buyer account configured by the customer.As the Ariba Network allows for a flexible configuration of the process, this document provides a straight forward setup that allows the integration between SAP S/4HANA system and the Ariba Network.

3.1 Default Transaction Rules

General Procedure1. Log on to your Ariba Network Buyer account. (typically via: buyer.ariba.com)2. Go to the Administration tab and choose Configuration.3. On the Configuration screen, choose Default Transaction Rules. 4. On the Default Transaction Rules screen, the available settings are grouped (e.g. Purchase Order

Rules). The following sub-chapters correspond with these groups.

Note: Transaction rules marked as “Optional” can be set according to your individual requirements (for more information about this rules please refer to the info button nearby each rule). For transaction rules marked other than “Optional” (e.g. “Activation required” or “Do not activate”) you have to make the setting accordingly, otherwise the integration may not work. You may also find transaction rules that are not covered in this document. These apply to features that are not applicable to an SAP S/4HANA system to Ariba Network integration and are therefore not listed. You do not need to make settings for them in the Ariba Network.

3.1.1 Purchase Order Rules

UseMake settings for purchase order integration with the Ariba Network.

ProcedureSelect the Override default purchase order rules checkbox.

6



Ariba Network Transaction Rule

Rule Setting Default Remarks

Allow change orders for fully shipped orders

Optional Please keep in mind that order confirmations and ship notices are not being forwarded to your SAP S/4HANA system. These documents will remain on the Ariba network and are accessible through the Buyer Account.

Allow change orders for partially shipped orders

Optional

Retain confirmation status for unchanged line items on change orders

Optional

Enable ship notice tracking on change orders

Optional

Allow change orders in invoice aggregation

Optional

Allow cancel orders for fully shipped orders

Optional

Allow cancel orders for partially shipped orders

Optional



reserved. 7

3.1.2 Ariba Buyer Contracts Site Setup Rules


Rule Setting Default SAP S/4HANA Integration Dependency

Allow suppliers to access your Ariba procurement applications for collaborative invoicing, requisitioning, managing time and expense sheets, and creating service sheets

Do not activate

3.1.3 Order Confirmation and Ship Notice Attachment RulesUnder Order Confirmation and Ship Notice Attachment Rules, you can define the following rules:


Rule Setting Default SAP S/4HANA Integration Dependency

Allow suppliers to include attachments with order confirmations

Optional Please keep in mind that order confirmations and ship notices are not being forwarded to your SAP S/4HANA system. These documents will remain on the Ariba network and are accessible through the Buyer Account.All attachments handled by the Ariba Network have a size limit of 10 MB!

Leave attachments online

Optional

Allow suppliers to include attachments with ship notices

Optional

Leave attachments online

Optional

8



3.1.4 Quick Enablement RulesUnder Quick Enablement Rules, you can define the following rule:



Allow Quick Enablement

Activation required

Ariba Network Quick Enablement allows buying organizations to create new Ariba Network accounts on behalf of suppliers. They create these accounts by specifying the supplier’s company information in a Correspondent element in the header of purchase order requests to the supplier. Ariba Network uses this information to create the supplier’s account.SAP S/4HANA supports quick enablement of suppliers. This requires a flag in the maintenance of Ariba Network suppliers, to select suppliers for which quick enablement is to active.For more information on quick enablement go to: https://connect.ariba.com/AC After you logged on, you can go to the Search-Tab. In the Search-field you should enter Buyer Administration Guide and then click on the Submit button. Please open the entry Buyer Administration Guide and search in the pdf-document for Quick Enablement.

3.1.5 Order Confirmation and Ship Notice RulesUnder Order Confirmation and Ship Notice Rules, you can define the following rules:



Allow suppliers to send order confirmations for material orders.

Optional Please keep in mind that order confirmations and ship notices are not being forwarded to your SAP S/4HANA system. These documents will remain on the Ariba network and are accessible through the Buyer Account.

Allow suppliers to send order confirmations for material orders at the line-item level

Optional

Allow suppliers to send order confirmations for service orders.

Optional

Allow suppliers to send order confirmations for service orders at the

Optional



reserved. 9

https://connect.ariba.com/AC

line-item levelAllow suppliers to confirm or reject an entire purchase order multiple times

Optional

Send suppliers an automatic reminder of unconfirmed orders after a specified number of days

Optional

Require suppliers to fully confirm line items before fulfillment

Do not activate

Require suppliers to create an order confirmation before creating a ship notice

Optional

Allow suppliers to send ship notices to this account

Optional

Delivery dates are required for order confirmation and ship notice

Optional

Require an estimated shipping date on order confirmations

Do not activate

Require an actual or estimated shipping date on ship notices

Do not activate

Require ship notice type on ship notices

Do not activate

Allow suppliers to add delivery and transport information to ship notices

Optional

Allow suppliers to send non-PO ship notices through cXML.

Optional

Allow zero-quantity line items in ship notices sent through cXML.

Optional

Allow multiple orders and scheduling agreement releases in ship notices

Optional

10



Require suppliers to provide a unique asset serial number for each purchase order line item on a ship notice

Optional

Require the total count of shipment serial numbers not to exceed the total quantity shipped for line items on ship notices

Optional

Require the Packing Slip ID to be unique on ship notices

Do not activate

Allow suppliers to create invoice number automatically from Packing Slip ID when creating a ship notice

Do not activate

Require suppliers to provide a Global Individual Asset ID for line items on ship notices that conforms to the Serial Shipping Container Code (SSCC) format

Do not activate

Require suppliers to provide a unique Global Individual Asset ID for line items on ship notices

Do not activate

Do not allow suppliers to change line item description on order confirmations.

Optional

Allow suppliers to increase item quantities on order confirmations

Optional

Apply line item quantity tolerance to order confirmations

Optional

Apply line item unit price tolerance to order confirmations

Optional



reserved. 11

Allow suppliers to change the currency for unit price on order confirmations

Optional

Apply line item subtotal amount tolerance to order confirmations

Optional

Apply line item delivery date tolerance to order confirmations

Optional

Allow suppliers to increase item quantities on ship notices

Optional

Apply line item quantity tolerance to ship notices

Optional

Allow suppliers to confirm or reject an entire purchase order multiple times

Optional

Allow suppliers to send order confirmations for material orders at the line-item level

Optional

Allow suppliers to send order confirmations for service orders at the line-item level

Optional

Require suppliers to enter a comment at the order confirmation line item level when there are any changes.

Do not activate

Allow suppliers to change advanced pricing details on order confirmations at the line-item level

Optional

Require suppliers to provide a reason when they reject an order

Optional

12



Require suppliers to provide a reason when they reject an order at the line-item level

Optional

Allow suppliers to enter the estimated shipping date on order confirmations at the line-item level

Optional

Allow suppliers to enter comments on order confirmations at the line-item level for confirmed or backordered items

Optional

Allow suppliers to change the supplier part ID on order confirmations at the line-item level

Optional

Allow suppliers to edit estimated shipping dates, delivery dates, and quantities.

Optional

Allow check for estimated shipping or delivery dates in the past when order confirmations are submitted

Optional

3.1.6 Service Sheet RulesService sheets are currently not supported by SAP S/4HANA system, therefore, do not select any checkbox.

3.1.7 Invoice Rules

3.1.7.1 General Invoice RulesUnder Invoice Rules, go to General Invoice Rules and define the following rules:



reserved. 13



Allow suppliers to send invoices to this account

Activation required

Activation required if you want to receive invoices via the Ariba Network!

Ignore country-based invoice rules

Optional

Allow suppliers to send invoices with service information

Do not activate

Require line-item credit memo to reference another invoice

Optional

Allow suppliers to send invoice attachments

Optional A limit of 10 MB per attachment exists.Note that the activation of this entry required an activation of the next entry

Your procurement application can download invoice attachments (MIME multipart messages).

Activation required

This option is only visible if the previous one is activated

Require suppliers to send invoice attachments

Do not activate

Require suppliers to send credit memo attachments

Do not activate

Allow suppliers to send non-PO invoices

Optional

Allow suppliers to send invoices with a contract reference.

Do not activate

Require suppliers to create an order confirmation for the PO before creating an invoice

Optional

Require suppliers to create invoice with line item quantity greater than zero.

Activation required

Require suppliers to create invoice with line item price

Activation required

14



greater than zero.Require suppliers to create a ship notice for the PO before creating an invoice

Optional

Allow suppliers to send invoices if a PCard or credit card was included in the order

Optional

Allow suppliers to send header credit memos and debit memos

Optional

Allow suppliers to send line-item credit memo

Activation required

Require suppliers to provide a reason for each credit memo

Optional

Allow suppliers to cancel invoices they create

Optional

Allow suppliers to reuse invoice numbers

Optional

Allow suppliers to enter advanced pricing details at line item level

Do not activate

Allow suppliers to change advanced pricing details at the line-item level

Activation required

Allow the Bill To Address to be mapped to the corresponding system ID for non-PO invoices sent through cXML, CVS, or EDI

Do not activate

Allow case-insensitive invoice matching

Optional

Require suppliers to include only shipped quantities on

Optional



reserved. 15

invoices.Require suppliers to include only received quantities on invoices.

Optional

Allow suppliers to add allowances and charges to invoices.

Optional

3.1.7.2 PO Invoice Field Rules1. Under Invoice Rules, go to PO Invoice Field Rules and define the following rules:

16





Allow suppliers to change the currency for unit price

Do not activate

Allow suppliers to change the unit price

Optional

Allow suppliers to change the unit of measure

Do not activate

Allow suppliers to increase item quantities

Optional

Allow suppliers to increase line item subtotals

Optional

Allow suppliers to change part numbers.

Do not activate

Allow suppliers to change auxiliary part id

Optional

Allow suppliers to add line items to PO invoices

Optional

Require invoice Sold To Name and Country to match PO Bill To Name and Country (or Sold To information if available).

Do not activate

2. Choose Save.You return to the Configuration screen.

3.1.7.3 PO and Non-PO Invoice Field Rules

Note Note that starting with service package 2, this add-on works with non-PO invoices.

Procedure1. Under Invoice Rules, go to PO and Non-PO Invoice Field Rules and define the following rules:



reserved. 17



Require suppliers to provide line item descriptions

Do not activate

Require suppliers to choose from your list of valid tax values

Optional

Allow suppliers to create a tax rate and type for invoices and credit memos

Optional

Allow net amounts to exceed subtotals

Optional

Allow invoices to be back-dated the specified number of days

Optional

Allow shipping tax entered at header level

Optional

Require suppliers to provide their tax ID on invoices

Do not activate

Allow suppliers to add shipping and special handling costs and tax details as separate invoice lines

Optional

Require suppliers to enter taxes at line item level

Do not activate

Require suppliers to provide order information

Optional

Allow suppliers to enter discounts at the header level

Optional

3.1.7.4 Invoice Address Rules

Procedure1. Under Invoice Rules, go to Invoice Address Rules and define the following rules:

18




Rule Setting

Default Remarks

Require a Bill To address on invoices

Do not activate

Require a Sold To address on invoices.

Do not activate

Require a From address on invoices.

Do not activate

Require a Remit To address on invoices

Do not activate

Require Ship From and Ship To addresses on invoices

Do not activate

Enforce strict address validation for required address fields

Do not activate

3.1.7.5 Blanket Purchase Order Invoice Rules

UseBlanket purchase orders are currently not supported by SAP S/4HANA system.

Procedure1. Under Invoice Rules, go to Blanket Purchase Order Invoice Rules and define the following rules:



Enable BPO-specific invoice rules

Do not activate

Note: the next settings under Blanket Purchase Order Invoice Rules group are only visible, if you activate this setting!

Allow suppliers to change the currency for unit price

Do not activate

Allow suppliers to change the unit price

Do not activate

Allow suppliers to Do not



reserved. 19

change the unit of measure

activate

Allow suppliers to increase item quantities

Do not activate

Allow suppliers to increase line item subtotals

Do not activate

Allow suppliers to change part numbers

Do not activate

Require suppliers to provide line item descriptions

Do not activate

Require suppliers to choose from your list of valid tax values

Do not activate

Allow suppliers to create a tax rate and type for invoices and credit memos

Do not activate

Allow net amounts to exceed subtotals

Do not activate

Allow suppliers to change line item descriptions when creating invoices for BPOs

Do not activate

Allow Ship To information in BPOs to be changed in invoices

Do not activate

Require suppliers to create a ship notice for the BPO before creating an invoice

Do not activate

Allow suppliers to increase item quantities on ship notices

Do not activate

Apply line item quantity tolerance to ship notices

Do not activate

20



3.1.7.6 Invoice Payment Rules


Rule Setting

Default Remarks

Allow suppliers to change payment net term as shown on purchase orders

Optional

Allow suppliers to change payment discount terms as shown on purchase orders

Optional

Allow suppliers to omit payment terms in PO invoices.

Optional

Require suppliers to provide penalty information or terms on invoices

Optional

Require suppliers to provide discount information or terms on invoices

Optional

Require suppliers to provide net term information on the invoice

Optional

Require suppliers to include bank account details on invoices

Optional

3.1.7.7 VAT Rules

Procedure1. Under Invoice Rules, go to VAT Rules and define the following rules:



Require customer's VAT/Tax ID

Do not activate

Require supplier's VAT/Tax ID

Do not activate



reserved. 21

Require suppliers to provide VAT information in invoice headers or line items

Activation required

Require supply date when VAT is chosen as tax category

Do not activate

Require tax amounts in local currency

Do not activate

Require subtotal and amount due in local currency

Do not activate

Require explanation for zero rate VAT

Do not activate

Require detailed tax information in tax summaries

Do not activate

Show your company's default VAT ID.

Do not activate

Display text boxes for buyer and supplier VAT IDs in invoice headers

Do not activate

Require your company's VAT ID only for intra-EU trade

Do not activate

Require VAT details only for domestic trade

Do not activate

Require VAT details only for domestic and intra-EU trade

Do not activate

Display invoice totals as Subtotal, Tax Amount, and Amount Due

Do not activate

Allow suppliers to submit self-signed invoices

Do not activate

Choose Save.You return to the Configuration screen.

22



3.1.7.8 Online Invoice Form Rules

Procedure1. Under the Heading Invoice Rules, go to Online Invoice Form Rules and define the following rules:


Rule Setting

Default Remarks

Allow suppliers to use remittance addresses without remittance IDs

Keep it activated

Activated

Allow suppliers to change Ship To information as shown on purchase orders

Do not activate

Allow suppliers to change Bill To information as shown on purchase orders

Optional

Default Bill To Address OptionalDefault Sold To Address

Do not activate

Configure List of Customer (Sold to) addresses with VAT IDs

Do not activate

Copy Bill To address on purchase orders to Sold To address on invoices

Do not activate

3.1.8 D-U-N-S Number Rule

Procedure1. Under D-U-N-S Number Rule, define the following rule:



reserved. 23


Rule Setting

Default Remarks

Do not require suppliers to enter their D-U-N-S number

Keep activated

The checkbox is selected.

D-U-N-S number is not validated

3.1.9 Invoice PDFYou may want to have a PDF copy of each invoice attached to the invoice. This can only be enabled through Ariba. Contact Ariba and ask for the following setting.

3.2 Business Application IDsThis configuration is only possible if your Ariba Network account has been activated for integration with more than one SAP S/4HANA system (Multi-ERP). Otherwise, it’s a 1:1connection and you have to skip this chapter.

Prerequisite Your Ariba Network account supports multi-ERP.

Procedure1. Log on to the Ariba Network (AN) with your Buyer account.2. Go to the Administration tab and choose Configuration.3. On the Configuration screen, choose Business Application IDs [and End Points] (cXML and OData

Setup).Reminder: if your Ariba Network account is not activated for multi-ERP, you will not find this link.

4. On the Configure Business Applications IDs screen, choose the Create.5. Define your SAP S/4HANA system using the following name: Systemname-CLNT-Clientnumber, for

example EH6CLNT103.

24



6. Maintain the address information as required. The Unique Address ID links the Bill To Address to the system ID. It is suggested to enter the system ID for the Unique Address ID too.

7. Save.8. Click Done. You have defined your SAP S/4HANA system in the Buyer Ariba Network.

3.3 CXML Setup

Use In this activity, you create the following settings: You do not specify your website's URL for receiving ProfileRequest documents. Instead of the POST method, you want to receive documents through the cXML GetPending

method.

Procedure1. Log on to the Ariba Network (AN) with your Buyer account.2. Go to the Administration tab3. Choose Configuration. 4. On the Configuration screen, depending on the actual setup of your Ariba account choose:

o cXML Setup ORo Business Application IDs (cXML and OData Setup) ORo Business Application IDs and End Points (cXML and OData Setup)

Now you have to maintain the profile URL and post URL. Depending on the actual setup of your Ariba account, you already may have reached the screen where the maintenance of the profile URL and post URL is possible. If this is the case, continue with the first instruction from the list below (#5).If the current screen does not allow the maintenance of the two URLs but shows a List of System IDs, click the System ID of your SAP S/4HANA system. Depending on the actual setup of your Ariba account, you may now have reached the screen where the maintenance of the profile URL and post URL is possible. If this is the case, continue with the first instruction from the list below (#5).Finally on the Manage Business Application ID: <System ID> screen, select tab End Point and select the End Point ID you want to make settings for.

5. In the Profile URL section, find the Profile Url field. 6. If the field is not empty, delete the content. The field should be blank.7. In the section Post Url look for the indicator: “Yes, I want to receive documents through the POST

method instead of through the cXML GetPending method.” The indicator should be unchecked.8. In the Post Url section, find the POST URL field.9. If the field is not empty, delete the content. The field should be blank.10. Save.



reserved. 25

3.4 Supplier Enablement

3.4.1 Establish Relationship

Prerequisite The supplier has to be enabled. If this is not the case, the supplier has to be enabled by the Ariba Support Organization.

Procedure1. Log on to the Ariba Network (AN) with your Buyer account. 2. Navigate to the Supplier Enablement tab and choose the Active Relationships subtab.

If you find the supplier, you want to connect with, in the Current Suppliers table, you can continue with section Assign Private ID.If the supplier is not in the Current Suppliers table, there is no active relationship with the supplier yet. Continue with the following steps:

3. Choose Search for Suppliers (NOT Search)4. Fill in appropriate search criteria and choose Search. 5. Select the supplier found, and choose Actions and Add to Selected Suppliers.6. You have to review the supplier’s profile. The profile can also be downloaded.7. In the Selected Suppliers overview, open the supplier by choosing its link. 8. To establish the relationship, choose Request a Relationship.

Note Note that the supplier has to accept the relationship. As long as the supplier has not accepted it, the supplier does not appear under Active Relationships.

3.4.2 Assign Private ID

UseSupplier master records in SAP S/4HANA system use IDs for identification. Customers with several ERP and/or SAP S/4HANA systems may even use different IDs assigned to the same supplier in each respective system. The settings described in this chapter link a supplier in the Ariba Network (as identified per it’s ANID) to the supplier IDs used in the customer’s and other systems.

Procedure1. Log on to the Ariba Network (AN) with your Buyer account.

26



2. Navigate to the Supplier Enablement tab and choose Active Relationships.3. Choose More Actions → Edit.4. On the Edit Preferences for Supplier: <your supplier name> screen, go to the Enter supplier

identifiers for the procurement application sub screen and choose Add.5. Relevant for Multi-ERP: In the Add Supplier Unique Key dialog box, choose one of your systems and

enter the relevant vendor ID for this system (Vendor ID, for example, 300000).6. In the example, this tells the Ariba Network that this supplier has the ID 300000 in system

<System ID> (this is the System ID of your SAP S/4HANA system). 7. Relevant for Single-ERP: First field is Vendor ID (for example, 300000)8. In the dialog box, choose Save.9. Repeat steps 5 and 6 for all your systems.10. Choose Save on the Edit Preferences for Supplier: <your supplier name> screen.



reserved. 27

4 Manual SAP S/4HANA System Configuration for the Ariba Network Integration

4.1 Define Basic Message Settings

UseIn this activity, you decide which messages are to be routed through the Ariba Network.

Procedure1. Access the transaction using the following navigation path:

Transaction Code

SPRO

IMG Menu Integration with Other SAP Components → Business Network Integration → Integration with the Ariba Network → Framework Settings → Define Basic Message Settings

2. Set the flag to Active for messages you want to send to or receive from the Ariba Network3. Save your entries.

4.2 Schedule job

UseMessages (e.g. Invoices) received in the Ariba Network buyer account need to be picked up by SAP S/4HANA system regularly. In this activity, you schedule a batch job that connects to the Ariba Network and picks up new messages.


Transaction Code SM36

Menu System → Services → Jobs → Define Job

28



Schedule report ARBFND_FETCH_CXML_MESSAGES_NEW to run every 2 minutes.

4.3 Define Credentials and End Points for Ariba Network

UseIn this activity, you create basic settings for authentication towards the Ariba Network.


Transaction Code

SPRO

IMG Menu Integration with Other SAP Components → Business Network Integration → Integration with the Ariba Network → Framework Settings → Define Credentials and End Points for Ariba Network

2. Choose New Entries and create the following settings:

Ariba Network ID

Shared Secret

Test Account

Enable System ID System ID

Enable End Points

ANID of your buyer account

Shared secret set for the buyer account

Identifies a test system

Used if multiple buyer systems use the same Ariba Network buyer account. In case you are unsure what best fits your situation, enable it.

System ID (if enabled)

An Ariba Network ID can have multiple end points. An end point is a document routing placeholder that ensures documents from Ariba Network are sent to the required destinations (system).

3. Save your entries.

If you need to enable end points make the required settings here. For more information on end points go to: https://connect.ariba.com/AC After you logged on, you can go to the Search-Tab. In the Search-field you should enter Buyer Administration Guide and then click on the Submit button. Please open the entry Buyer Administration Guide and search in the pdf-document for End points.



reserved. 29

https://connect.ariba.com/AC

4.4 Assign Network ID to Company Codes


Transaction Code

SPRO

IMG Menu Integration with Other SAP Components → Business Network Integration → Integration with the Ariba Network → Application-Specific Settings → Assign Ariba Network ID to Company Code


Ariba Network ID Company Code Company NameANID of your buyer account

Company Code The company code’s name


4.5 Map Company Code for Invoice Verification


Transaction Code

SPRO

IMG Menu Integration with Other SAP Components → Business Network Integration → Integration with the Ariba Network → Application-Specific Settings → Define Application-Specific Mapping Settings → Define Mapping Settings for Invoices → Incoming Invoice: Map Company Codes for Logistics Invoice Verification


Supplier Supplier Name Name of Partner in CXML

Company Code Company Name

Supplier ID The supplier’s name

What the supplier sends across as <billTo> invoices

The corresponding company code in the buyer’s system

Company code description


30



4.6 Map Tax Codes for Invoice Verification


Transaction Code

SPRO

IMG Menu Integration with Other SAP Components → Business Network Integration → Integration with the Ariba Network → Application-Specific Settings → Define Application-Specific Mapping Settings → Define Mapping Settings for Invoices → Incoming Invoice: Map Tax Codes for Logistics Invoice Verification


Supplier Supplier Name

Tax Category in CXML

Tax Rate in CXML

Country Tax Code Tax Code Description

Supplier ID

Supplier’s name

For example, vat

For example, 7 (for 7 %)

Country for which you make the setting

Tax code used in the buyer’s system

Description of the tax code


4.7 Map Tax Categories for CC Invoice

UseOut coming invoices (invoices which are sent from S/4HANA Cloud to Ariba Network) carry information such as applicable taxes, tax rates, and tax amounts.In this activity, you map the tax categories (such as vat or sales tax) to tax codes used in your system (these settings are country-specific). This is required for each of your suppliers. You may make settings leaving the field Supplier empty thus applying this setting to all respective suppliers (wildcard).


Transaction Code

SPRO

IMG Menu Integration with Other SAP Components → Business Network Integration → Integration with the Ariba Network → Application-Specific Settings → Define Application-Specific Mapping Settings → Define Mapping Settings for Invoices → CC Invoice: Map Tax Category for cXML Invoice



reserved. 31


Supplier Supplier Name

Country Tax Code Tax Code Description

Tax Category in CXML

Supplier ID

Supplier’s name

Country for which you make the setting

Tax code used in the buyer’s system

Description of the tax code

For example, vat


4.8 Output Control

UseIn this activity, you define settings relevant for the output of purchase orders and supplier invoices. There are two methods of output management, which can be used: Output Management via message control (NAST) New output management

Note Note that for the supplier invoice you can use only the Output Management via message control (NAST).

By default, output management via NAST is active. If you want to use the New Output Management for the purchase order, make the following steps:1. Access the transaction using the following navigation path:

Transaction Code

SPRO

IMG Menu Integration with Other SAP Components → Business Network Integration → Integration with the Ariba Network → Application-Specific Settings → Define Message Output Control → Method 2: Use SAP S/4HANA-Based Output Management → Activate SAP S/4HANA-Based Output Management for Purchasing Documents

2. On the Change View "Activation of New Output Management for Purchasing Docume" screen, select the following mode:Mode New output management is active


32



4.8.1 BRF+ Settings

UseIn this activity, you define settings relevant for the output of purchase orders, if you use the New output management.

Procedure Purchase Order1. Access the transaction using the following navigation path:

Transaction Code

SPRO

IMG Menu Integration with Other SAP Components → Business Network Integration → Integration with the Ariba Network → Application-Specific Settings → Define Message Output Control → Method 2: Use SAP S/4HANA-Based Output Management → Define Business Rules for Output Determination

2. On the Define Business Rules for Output Determination screen, under Select Business Rules, select the following criteria:

Screen Element User Action and ValuesShow Rules For Purchase Order

Determination Channel

3. For every supplier that you would like to send purchase orders via the Ariba Network, create a business rule:

Output Type Receiver ID ChannelPURCHASE_ORDER (Purchase Order)

Supplier XML (XML)

4. Activate and save your entries.



reserved. 33

4.8.2 NAST Settings

UseIn this activity, you define settings relevant for the output of purchase orders and supplier invoices, if you use the Output Management via message control (NAST).

4.8.2.1 Define Conditions for Output Control


Transaction Code

SPRO

IMG Menu Integration with Other SAP Components → Business Network Integration → Integration with the Ariba Network → Application-Specific Settings → Define Message Output Control → Method 1: Use Message Control (NAST) → Define Conditions for Output Control

2. On the Conditions for Output Control screen, select for Purchase Order:1. EF Purchase Order and choose Condition records.2. On the Output Types screen, select the entry Neu Purchase Order and choose Condition

records.3. In the Key Combination dialog box, choose Purchasing Output Determination: Document Type4. On the "Change Purchase order (NEU): Selection" screen, make following entry:Purchasing Doc. Type NB

5. Select Execute (F8).6. On the Change Condition Records (Purchase order): Fast Change screen, make following

settings:

Doc. Type Funct Partner Medium Date/TimeNB VN 10300080 (please

enter your own supplier number)

8 (Special function)

4 (Send immediately)

7. Save your entries.3. To define the conditions for the Invoice Verification on the Conditions for Output Control screen,

select:1. MR Invoice Verification and choose Condition records.2. On the Output Types screen, select the entry ARCC Ariba Carbon Copy (for CC Invoice) or ARSU

Ariba Status Update (for Invoice Status Update) and choose Condition records.3. In the Key Combination dialog box, choose CoCde.4. On the "Change Ariba Carbon Cop (ARCC): Selection" screen, make following entry:

34



Company Code e.g. 1000

5. Select Execute (F8).6. On the Change Condition Records (Ariba Carbon Copy): Fast Change screen, make following

settings:

CoCode Funct Partner Medium Date/Timee.g. 1000 VN 10300080 (please

enter your own supplier number)

8 (Special function)

4 (Send immediately)


4.8.2.2 Map Application and Output Type to cXML Message


Transaction Code

SPRO

IMG Menu Integration with Other SAP Components → Business Network Integration → Integration with the Ariba Network → Application-Specific Settings → Define Message Output Control → Method 1: Use Message Control (NAST) → Map Application and Output Type to cXML Message

2. On the Change View "Map Application and Output Type to cXML Message": Overview screen, choose New Entries and create following settings:

Application for Output Conditions

Output Type

cXML Message Type Application Component ID

EF NEU ORDR BNS-ARI-SE-ERPMR ARCC CCINVC BNS-ARI-SE-ERPMR ARSU STAT BNS-ARI-SE-ERP




reserved. 35

5 Manual Build StepsFor the configuration activities described in this document, no manual build steps are required.

36



Typographic ConventionsType Style Description

Example Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options.Textual cross-references to other documents.

Example Emphasized words or expressions.EXAMPLE Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of

a programming language when they are surrounded by body text, for example, SELECT and INCLUDE.Example Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source

text, and names of installation, upgrade and database tools.Example Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.<Example> Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the

system.EXAMPLE Keys on the keyboard, for example, F2 or ENTER .



reserved. 37

www.sap.com/contactsap

© 2015 SAP SE or an SAP affiliate company. All rights reserved.No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. Please see http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.National product specifications may vary.These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company products andservices are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark

http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark