Analyzing Required Configurations

Objective

After completing this lesson, you will be able to explain how to configure Purchase Order Flows in an SAP System, CIG, and in Ariba Network.

Purchase Order Flow

A Purchase Order (PO) is a commercial document and first official offer issued by a buyer to a seller, indicating material or service types, quantities, and agreed prices for products or services.

  • It is used to control the purchasing of products and services from external suppliers.
  • Acceptance of a purchase order by a seller forms a contract between the buyer and seller.
  • A contract does not exist until the purchase order is accepted.

Types of Purchase Orders Supported:

  • Standard Purchase Orders
  • Blanket Purchase Orders
  • Scheduling Agreement Release Purchase Orders
  • Service Purchase Orders
  • Subcontracting Purchase Orders
  • Consignment Purchase Orders
  • Purchase Orders with Returns

Additional Information:

  • Schedule lines in a Purchase Order are supported.
  • A Standard Purchase Order can have lines with catalog material or non-catalog material.
  • A Service Purchase Order, using SAP ERP 6.0 EHP 0, can only have a single-level hierarchy (one parent and child line item). However, using SAP ERP 6.0 EHP 4 & higher, you can send a Service PO with service line items in up to five levels of hierarchy (1 parent and 4 child levels).
  • A Blanket PO with item category "B" is supported.
  • Price Basis Quantity (PBQ) along with different types of Account Assignment Category is supported.
  • Defining 2 way or 3 way match is also supported.

Pre-requisites:

  • Standard NACE or Output Determination configuration should be in place.
  • SAP Ariba AddOn package downloaded in your SAP system.
  • Ensure that the parameter ORDER_ENABLED is set.
    • ORDER_ENABLED – Enables you to bypass the SAP Ariba code in case it is causing issues in customer specific scenario.
  • SAP Cloud Connector installed & configured (for Direct Connect option).
  • Supported middleware should be configured (for Mediated Connect option).
  • CIG enabled through your AN Buyer Account & you have P User info.
  • SAP system information is sent to CIG.
  • AN Buyer and Supplier relationship should exist.

Configuration in SAP System – Global Settings

Ensure that following configurations of Global Settings section are in place:

  • Define Authorizations: Make sure that users working on CIG AddOn configurations have necessary authorizations / roles assigned.
  • Enable Integration through Middleware: This is an optional activity. Maintain a parameter if you are integrating via any of the supported middleware.
  • Maintain Certificates: This is a mandatory activity to establish SSL handshake / connectivity between SAP system & CIG. Upload Loadbalancer certificate of CIG in the Trust Manager.
  • Create RFC Destination: RFC Destination is needed for transmitting IDocs. It allows you to connect from an ABAP system to an external system. Before creating an RFC destination for CIG, ensure that you have maintained CIG’s Loadbalancer certificate in the Trust Manager & you have P User & password information handy.
  • Create Port Definition: A port is the communication channel through which IDocs are sent. The port describes the technical link between the sending and receiving systems. Port Definition is needed to specify the way in which the IDocs are transferred to the EDI subsystem.
  • Create Logical System: The value created here will be used in Interface Setup program for generating outbound parameters of Partner Profile under TCode WE20.
  • Configure Receiver Port: Assign ports created to a specific IDoc flow based on the solutions you are adopting.
  • Send SAP Information to CIG: Run this (SAP Data Sync) report to send specific set f information from SAP system to CIG. This information will be used during project creation & for applying accurate mapping set to your documents.
  • Maintain Parameters for Attachments Support: This is an optional activity. You can maintain certain parameters to send or receive attachments for the documents where SAP standard UI doesn’t support it by default.
  • Map Variants & Partitions: Applicable only for SAP Ariba Sourcing Integration & SAP Ariba Procurement Integration. Define unique values of variant & partition for your SAP Ariba realms. This is required by our various export programs to apply filters & parameters while exporting data for a specific SAP Ariba solution.
  • Maintain BAdIs as per your requirements to further massage the data for filters & parameters before storing it in Ariba specific tables.

Configuration in SAP System – General Settings

To navigate to general settings in SAP ERP and SAP S/4 HANA for Ariba Network Transactions

  • Run the transaction code SPRO – The Customizing: Execute Project screen appears.
  • Click SAP Reference IMG – The Display IMG screen appears.
  • Navigate to –
    • Integration with Other SAP Components → SAP Ariba Cloud Integration Gateway → Ariba Network Integration → General Settings
    SAP IMG screen displaying structure for SAP Ariba integration settings. Highlighted folders include Ariba Network Integration and General Settings.

Ensure that following configurations of General Settings section are in place:

  • Setup the Interface: This program helps you to automatically create Inbound & Outbound parameters in Partner Profile for IDocs and Logical Ports & Service Names in SOAMANAGER for Web Services / Proxies.
  • BAdIs for Setting Up Interface: When setting up the interface, you can optionally implement the BAdI to modify any parameters.
  • Create Partner Profile for House Bank: Since the Setup Interface program will always configure interface for IDocs only against the partner function of type LS (Logical System), you would need to need to manually configure outbound parameters for REMADV & PAYEXT (under partner type B) to generate Payment Remittance documents & send it to Ariba Network & also optionally send the info to bank.
  • Configure Document Status Update: Using the document status update functionality, you can monitor status of all transactions that:
    • You send from your SAP ERP or SAP S/4 HANA system through CIG to suppliers on the Ariba Network.
    • Send the document status update for transactions that you receive from suppliers on the Ariba Network.
  • Enable Supply Chain Collaboration (SCC): If you want to enable Supply Chain Collaboration related functionality, then you need to maintain required parameter. This is purely based on requirement. Since Enable SCC is a toggle driven feature in AN, we also have provided same flexibility in AddOn code.
  • Enable Vendors: In this activity, user needs to maintain the vendor & company code combination in ARBCIG_AN_Vendor table (via SPRO node) for all the SAP vendors that are registered as suppliers on Ariba Network. Thus, the documents are filtered & sent to Ariba Network only for such SAP vendors who are registered suppliers on Ariba Network.
  • Maintain Vendor for the Outbound Transaction: This is an additional filter for outbound transactions. Maintaining "Enable Vendors" table is prerequisite for this activity. Here user needs to select the vendors that are already added in ARBCIG_AN_Vendor table & then maintain one or more message types for each vendor in ARBCIG_OB_VENDOR table (via SPRO node). This configuration helps you to further specify or filter message types per vendor that you wish to send to Ariba Network. If this table is not maintained, CIG AddOn code will only refer to AN Vendor table & will send all the message types for the vendors available in ARBCIG_AN_VENDOR table to Ariba Network.
  • Enable External Format Conversion: You can configure SAP system to convert the format of data to external format before sending it to Ariba Network. This parameter helps you to remove leading zeros of the object IDs such as Purchase Order Number; Material Number; Item Number; G/L Account; Asset; WBS Element; Cost Center; Internal Order; etc.
  • Plant Specific Time Zone Conversion: User can configure SAP system to send delivery date with Plant time zone instead of System time zone for PO/SA/SAR transaction.

Configuration in SAP System – Transaction Specific Settings

Configure Ariba Network Transactions

In this section, we will look into the configurations of sample IDOC outbound (Purchase Order) transactions required on the SAP AddOn to map the transactions and messages to cXML and send to Ariba Network.

  • Run the Tcode SPRO
    • The Customizing: Execute Project screen appears.
  • Click SAP Reference IMG
    • The Display IMG screen appears.

Navigate to:

  • Integration with Other SAP Components
  • SAP Ariba Cloud Integration Gateway
  • Ariba Network Integration
  • Application Specific Settings
SAP IMG screen highlighting Ariba Network Integration. Subsections include General Settings and Application Specific Settings with detailed configuration options.

All supported transactions for Ariba Network Integration are listed under Application Specific Settings.

Purchase Order

To send a Purchase Order from an SAP System to Ariba Network, you need to perform following activities:

  • Define Message Output Control for Purchase Orders
  • Maintain Parameters for Purchase Orders
  • Configure Implicit Enhancements for Change & Cancel Orders
  • Configure Service Map Key for Service Orders
  • Implement Customer Exit for Purchase Orders
  • Mapping setting for Purchase Order/SA/SAR Outbound

Purchase Order- Define Message Output Control

Steps

  1. Navigate to:

    • Integration with Other SAP Components.
    • SAP Ariba Cloud Integration Gateway.
    • Ariba Network Integration.
    • Application Specific Settings.
    • Purchase Order.
    SAP IMG screen highlighting Ariba Network Integration, Application Specific Settings, and subcategories Purchase Requisition and Purchase Order for configurations.

  2. Expand the Purchase Order section & click IMG-Activity for "Define Message Output Control for Purchase Order."

    SAP IMG screen with Ariba Network Integration expanded. Highlighted option is Define Message Output Control for Purchase Order under configurations.
    • The Conditions for Output Controlscreen appears.

  3. Select EF and click Output types.

    SAP Output Control screen showing Output Types tab. Highlighted entry is EF for Purchase Order under application-specific settings.

    The Display View "Output Types": Overview screen appears.

  4. Click NEU (for example) & click Change.

    SAP screen displaying Output Types overview. Highlighted entry is NEU for Purchase Order under application EF configuration settings.

  5. Double-click NEU (for example).

    SAP screen showing Change View Output Types: Details. NEU (Purchase Order) and Access Sequence 0001 under General Data tab are highlighted.

    The Change View "Output Types": Details screen appears.

  6. On the General Data tab, for Access sequence choose 0001 DocType/PurchaseOrg/Vendor.

  7. On the Default values tab, create following entry:

    SAP screen showing Change View Output Types: Details with Default values section highlighted for NEU (Purchase Order) configuration.
    • Dispatch Time: Send immediately (when saving the application)
    • Transmission Medium: EDI
    • Partner Function:LS
    • Click Save & go back to the Change View "Output Types": Overview screen

  8. Click NEU (for example) & then double-click Processing routines.

    SAP screen displaying Change View Output Types: Overview. Highlighted are Processing routines section and NEU Purchase Order entry.

    The Display View "Processing routines": Overview screen appears.

  9. In the Processing Routines section, create following entry:

    SAP Change View: Processing Routines screen showing the EDI processing routine highlighted for Output Type NEU and Application EF.
    • Transmission Medium: EDI
    • Program: RSNASTED
    • Form Routine: EDI_PROCESSING
    • Click Save.

  10. Click NEU (for example) & then double-click Partner Functions.

    SAP screen showing Change View Output Types: Overview. The Partner functions section and Output Type NEU (Purchase Order) highlighted.

    The Display View "Partner functions": Overview screen appears.

  11. In the Partner Functions section, create following entry:

    SAP Change View: Partner Functions screen displaying Output Type NEU and EDI medium with Logical System highlighted.
    • Medium: EDI
    • Function: LS
    • Name: Logical System
    • Click Save.

  12. Select application EF and click Condition records.

    The Output Types popup appears.

    SAP screen showing Conditions for Output Control. The EF application for Purchase Order is highlighted under Condition records tab.

  13. Click NEU (for example) & then click Condition records.

    SAP screen displays Conditions for Output Control, highlighting Application EF Purchase Order and Output Type NEU in a popup.

    The Key Combination popup appears.

  14. Maintain the required key combination for

    • Purchasing Output Detrmination: Doc.Type/Purch.Org/Vendor:
    • Purchasing Doc Type: NB
    • Purch. Organization: US001 (for example)
    SAP Change Output - Condition Records NEU screen showing Application EF and key combination selection for Doc.Type/Purch.Org/Vendor.
    SAP Change Purchase Order (NEU): Selection screen highlighting fields Purchasing Doc. Type with dropdown showing Standard PO (NB).

    Click Execute.

    The Change Condition Records (Purchase order): Fast Change screen appears.

  15. In the Condition Recs section, enter the following:

    SAP system showing Change Condition Records for purchase orders, highlighting condition records, vendor, partner, and communication details.
    • Vendor: 100005 (for example)
    • Name:
    • Function: LS (for example)
    • Partner: T90CLNT90 (for example)
    • Medium: EDI (for example)
    • Date/Time: Send immediately (when saving the application) (for example)
    • Language: EN (for example)

    Click Save.

Purchase Order- Maintain Parameters

Buyer users need to maintain the few parameters to send Purchase Orders or Subcontracting Purchase Orders to suppliers. Buyer users also need to maintain parameters to send copies of Subcontracting Purchase Orders to multiple contract manufacturer suppliers on Ariba Network.

SAP IMG screen displaying navigation path for configuring Maintain Parameters for Purchase Order under Purchase Order settings in SAP system.

Navigate to:

  • Integration with Other SAP Components
  • SAP Ariba Cloud Integration Gateway
  • Ariba Network Integration
  • Application Specific Settings
  • Purchase Order

  • Expand the Purchase Order section & click IMG-Activity for "Maintain Parameters for Purchase Order"

The Parameters – Purchase Order screen appears.

  • Maintain parameters as mentioned in the table.
SAP screen displaying Parameters - Purchase Order table with variable names, field names, numerical values, and corresponding low-value entries.
Parameter NameDescriptionSupported Values
ORDER_ENABLEDEnable or disable the SAP Ariba provided enhancements for purchase order.

- Variable Name: ORDER_ENABLED

- Field Name: Leave it empty

- Number: 0000

- Low: X to enable or blank

REGIO_DESC_ENABLEDEnable this parameter to populate Region / Regio description in the IDoc segment.

- Variable Name: REGIO_DESC_ENABLED

- Field Name: Leave it blank

- Number: 0000

- Low: X to enable or blank

CSC_COPY_SUPPLIER_PARVW

Required for multi-tier purchase orders for SAP Ariba Supply Chain Collaboration.

Use this parameter to send more than one copy of the multi-tier purchase order or receipt.

- Variable Name: CSC_COPY_SUPPLIER_PARVW

- Field Name: Leave it blank

- Number: 0000

- Low: For example YL.

CSC_COPY_SUPPLIER_PARVW

Required for multi-tier purchase orders for SAP Ariba Supply Chain Collaboration.

Use this parameter to send more than one copy of the multi-tier purchase order or receipt.

- Variable Name: CSC_COPY_SUPPLIER_PARVW

- Field Name: Leave it blank

- Number: 0000

- Low: For example YL.

DELIVER_TO_PARVWMention the partner function to fetch the partner details for "Deliver To" partner function.

- Variable Name: DELIVER_TO_PARVW

- Field Name: Leave it blank

- Number: 0000

- Low: YS or YL, for example.

ARIBA_SRVMAPKEYRequired for service purchase orders that have service line number & use the service map key activated on the SAP ERP or SAP S/4HANA system.

- Variable Name: ARIBA_SRVMAPKEY

- Field Name: Leave it blank

- Number: 0000

- Low: X to enable or blank

PRINT_RELV_CHK_ENABLEDRequired to enable change purchase orders output based on print-relevant field settings.

- Variable Name: PRINT_RELV_CHK_ENABLED

- Field Name: Leave it blank

- Number: 0000

- Low: X (to enable) or leave it blank (to disable).

Purchase Order- Configure Implicit Enhancements

Buyer users need to configure implicit enhancements to send Purchase Order to Ariba Network.

Steps

  1. Run the TCode SE38

    ABAP Editor initial screen in SAP, with program field populated as LEINMF0Q, highlighting display button and subobject options.

    The ABAP Editor: Initial screen appears.

  2. Enter LEINMF0Q for Program & click Display

    The Choose Program for LEINMF0Q popup appears.

  3. Click Select.

    SAP screen displaying Choose Program for LEINMF0Q dialog box with listed options and Select button highlighted for user confirmation.

    Note

    As standard SAP’s ORDERS IDoc is not capable of handling PO changes & deletion by default, this enhancement helps to enable the IDoc to send change & cancel / delete info to AN.

  4. Click Enhance in the application toolbar.

    ABAP Editor screen displaying Display Include LEINMF0Q, showing code editor, Choose Program dialog box, and highlighted Select button.

  5. Select SAPLEINM from the popup.

  6. Click Edit → Enhancement Operations → Show Implicit Enhancement Optionsto display a line after the lesen-beleg form.

    ABAP Editor screen showing Enhancement Operations menu under Edit tab, highlighting the Show Implicit Enhancement Options option for selection.

  7. Right-click the line below FORM lesen_beleg & select:

    • Enhancement Implementation.
    • Create Implementation.
    ABAP Editor screen showcasing code with Enhancement Operations menu expanded, highlighting Create Implementation option for enhancement operations.

  8. Click Code on the Choose Type of Enhancement popup to display Select or Create Enhancement Implementation buttons.

    SAP ABAP Editor screen showing enhancement creation for LEINMF0Q. User selects 'Code' enhancement type in the dialog box.

  9. Click Create Enhancement Implementation button.

    SAP ABAP Editor showing the enhancement list for LEINMF0Q. User selects an enhancement implementation from the popup window.

  10. Enter a name & description for the enhancement & press Enter.

    SAP ABAP Editor showing the Create Enhancement Implementation popup. User enters name and short text for the implementation.

  11. In the package popup, specify your Z or Y package or Local Object, press Enter & save the package to a transport request.

    SAP ABAP Editor Create Object Directory Entry popup. User specifies a package and clicks Local Object for enhancement implementation.

  12. Enter the include: INCLUDE ARBCIG_ORDER_REQUEST_LEINMF0Q IF FOUND.

    SAP ABAP Editor showing an inactive enhancement ZCHANGE created for LEINMF0Q. User accesses the Enhancements menu for actions.

  13. Activate the enhancement and save it.

Purchase Order - Configure Service Map Key

This functionality is actually built for SAP SRM and SAP Ariba is using that. It is available from EhP 4+ (Enhancement Pack).

  • Configure this setting only if your service purchase order transfer from ERP to Ariba Network fails.
  • This usually occurs when the business function LOG_MM_P2PSE_1 is not active on your SAP ERP system.
    • To have the SRVMAPKRY generated, customer needs to turn on the Business Function (BF) – LOG_MM_P2PSE_1.
  • You only need to implement the SAP Note (#2372821) if the standard field SRVMAPKEY is not activated on your SAP ERP system.
  • The standard field SRVMAPKEY in the SAP Table ESLL stores service purchase order Item ID information.
  • The service map key is required to identify the line numbers for the service lines.
  • If the SRVMAPKEY is not available, the Item ID does not populate the line numbers for the service lines correctly and the SAP Process Integration mappings fail.

Purchase Order- Implement Customer Exit

The INCLUDE ARBCIG_ORDER_REQUEST_002 is called from the customer exit for outbound purchase orders.

Steps

  1. Navigate to:

    • Integration with Other SAP Components
    • SAP Ariba Cloud Integration Gateway
    • Ariba Network Integration
    • Application Specific Settings.
    SAP Display IMG screen showing navigation to Ariba Network Integration and selecting Purchase Order under application-specific settings.

  2. Expand the Purchase Order section & click IMG-Activity for "Implement Customer Exit for Purchase Order."

    SAP Display IMG screen showing Purchase Order settings with the option to Implement a Customer Exit for Purchase Order selected.

    The Project Management of SAP Enhancements screen appears.

  3. Create a new customer exit. ZARIBAPO (for example) & click Create.

    SAP Project Management of Enhancements screen. User enters project ZARIBAPO and clicks Create to manage enhancement attributes.

  4. In the package popup, specify your Z or Y package or Local Object, press Enter & save the package to a transport request.

    Attributes of Enhancement Project ZARIBAPO screen in SAP. User specifies package details and clicks Local Object to proceed further.

  5. Click Enhancement Assignments;

    • Enter the user exit name MM06E001 & press Enter.
    Attributes of Enhancement Project ZARIBAPO in SAP, showing project details. User clicks Enhancement assignments tab to manage assignments.
    SAP Enhancements screen under Project ZARIBAPO. User inputs enhancement MM06E001 to assign it to the enhancement project.

  6. Go back & click Components. Then double-click the enhancement name EXIT_SAPLEINM_002.

    Attributes of Enhancement Project ZARIBAPO in SAP. User selects the Components tab to configure assigned components for the project.

  7. In the new screen that appears, double-click INCLUDE ZXM06U02.

    Function Builder screen showing EXIT_SAPLEINM_002 function module. User accesses source code and includes ZXM06U02 for implementation.

  8. In the new screen that appears, double-click INCLUDE ZXM06U02.

  9. Click Activate.

    ABAP Editor displaying ZXM06U02 include. User adds arbcig_order_request_002 code snippet and clicks save button to confirm changes.

  10. Go back & click Components & then double-click the enhancement name EXIT_SAPLEINM_011.

    Attributes of Enhancement Project ZARIBAPO screen. User selects the Components tab to review or modify the project's assigned components.
    Z_SAPII project with assigned enhancements and function exits for MM06E001 user exits in SAP environment.

  11. In the new screen that appears, double-click INCLUDE ZXM06U33.

    Function Builder displays EXIT_SAPLEINM_011 source code, including importing parameters, tables, exceptions, and custom include ZXMO6U33 implementation.

  12. Enter the include: INCLUDE ARBCIG_ORDER_REQUEST_011 IF FOUND.

    ZXMO6U33 with code snippet 'INCLUDE arbcig_order_request_011 IF FOUND' and highlighted change icon.

  13. Click Activate.

  14. Go back & activate user exit as well.

    Project Management of SAP Enhancements screenshot displays project ZARIBAPO with options for attributes, enhancement assignment, components, and documentation.

Purchase Order- Mapping Setting for Purchase Order/SA/SAR Outbound

This configuration filters out account assignment details such as G/L Account, Profit or Cost Center etc. at the company code level, when the purchase order is sent from SAP to Ariba Network via CIG. In the case of Invoice Pro, the customer may choose to send organization data in the PO to Ariba Network.

SAP Implementation Guide screen displaying the path to configure Mapping Setting for Purchase Order/SA/SAR Outbound under Ariba Network Integration.
SAP configuration screen showing the table view of Further mapping settings for purchase order outbound with editable company code fields.

Navigate to:

  • Integration with Other SAP Components
  • SAP Ariba Cloud Integration Gateway
  • Ariba Network Integration
  • Application Specific Settings.
  • Expand Purchase Order section & click IMG-Activity for "Mapping Setting for Purchase Order/SA/SAR Outbound"

The Change View Further mapping settings for Purchase Order Outbound Ov screen appears.

  • Maintain parameters as mentioned:
Parameter NameDescription
Do not Send Account Assignment DataFor any company code, user can choose not to send the account assignment data by selecting the checkbox against that company code.
Do not Send Additional Data for SAP Ariba Invoice ManagementFor any company code, user can choose not to send additional data like Org data by selecting the checkbox against that company code.

Configuration in CIG

In this section, we will only focus on the configurations in CIG which are very specific to Purchase Order integration:

  • Enable CIG for your Ariba Network Buyer Account.
  • Provide Basic Information in the project in CIG for "Product = Ariba Network".
  • Define Connection information to establish connectivity between CIG & your SAP system.
  • Define Cross Reference for Parameter for Purchase Order (Doc Type – OrderRequest)
  • Define Cross References for UOM.
  • Define Cross Reference for Lookup Table not required for Ariba Network PO Integration.
  • Review project configuration & Confirm the Project.
  • Test the Project.
  • Deploy the Project.

Cross Reference Configuration - Parameter

You will need to define values in the parameter fields in which you want to map. The transactions & the related parameters are added by the administrator. You can define the values for both test & production environments.

Steps

  1. Select the Document Type = OrderRequest in Parameters tab & click Add.

    SAP Cloud Integration Gateway interface showing Cross Reference Configuration screen with options to add, test, and manage document types.

  2. Edit the entry.

    Cross Reference Configuration screen in SAP Cloud Integration Gateway displaying document types with options to test, edit, or delete.

  3. Enter values for the parameters in the TEST Environment and PROD Environment & click Save.

    SAP Cloud Integration Gateway screen for configuring ReceiptRequest parameters in TEST and PROD environments with options to save or cancel.

    If you want to have different value in PROD Environment, uncheck the box Use same values.

  4. Enter parameter values for another Document Type as needed or click Next.

    SAP Cloud Integration Gateway screen displaying Cross Reference Configuration with dropdown options for document types and navigation controls.

Configuration in CIG: Cross Reference Configuration - Parameter

  • Header Text ID SAR: Provide the text ID of a specific comment field at header level of your Scheduling Agreement Release (SAR) which you would want to map & send to Ariba Network.
  • PO Line Text ID: Provide the text ID of a specific comment field at line item level of your Purchase Order which you would want to map & send to Ariba Network.
  • PO Default Lang: Always maintain en for English.

    SA Line Text ID SAR: Provide the text ID of a specific comment field at line item level of your Scheduling Agreement Release (SAR) which you would want to map & send to Ariba Network.

  • PO Line Text ID: Provide the text ID of a specific comment field at header level of your Purchase Order which you would want to map & send to Ariba Network.

Note

Text ID: The Text ID is an identifier to differentiate between various types of texts / comments. In SAP system, you can find more than one text / comment fields at header as well as line item level. Each of these text / comment fields are identified by a unique Text ID.

Configuration in Ariba Network

In this section, we will only focus on the configurations in CIG which are very specific to Purchase Order integration:

  • Specify Default Transaction Rules
  • Define Active Relationships with the suppliers you would want to trade

Specify Default Transaction Rules

Steps

  1. Login to you’re AN Buyer account; click on Administration & then click on Configuration.

    SAP Ariba Network interface showing the Administration menu with Configuration options, vendor enablement status, and progress summaries.

  2. Click on Default Transaction Rules.

    SAP Ariba Network Configuration screen displaying options to update company settings, highlighting the Default Transaction Rules section for customization.

  3. Specify the rules by checking boxes against individual rules & click Save.

    SAP Ariba Network screen showing Default Transaction Rules configuration, focusing on Payment Batch Transmission Rules and Purchase Order Rules options.

    Note

    Specifying Invoice Transaction Rules is completely based on business requirements of individual customer.

Define Supplier Relationships

Steps

  1. Login to you’re an Buyer account; click on Supplier Enablement & then click on Active Relationships.

    SAP Ariba Network interface showing Supplier Enablement menu, highlighting Active Relationships and Search for Suppliers options for supplier management.

  2. Click on Search for Suppliers button.

  3. Search any of the parameters such as Company name; Supplier’s ANID; etc. & click Search.

    SAP Ariba Network's Search Suppliers screen, showing supplier search criteria, including ANID, company name, D-U-N-S Number, and location filters.

  4. In the Search Results, click on Request Relationship link against your desired supplier.

    SAP Ariba Network search results screen displaying a supplier's details with options to view catalogs or request a business relationship.

  5. On the Supplier Detail page, check the box to confirm review & verification of the supplier profile & click on Request a Trading Relationship button.

    SAP Ariba Network screen displaying Supplier Detail, with an option to verify a supplier's profile and request a trading relationship.

  6. Popup window will appear to confirm that the trading relationship with supplier is established. Click Done.

    SAP Ariba Network notification confirming the establishment of a trading relationship with a supplier, featuring the Done button for completion.

  7. Once the supplier accepts & approve the trading relationship request, you can see the supplier in your Current Suppliers section under Active Relationships page.

    SAP Ariba interface showing Supplier Enablement tab, with Alerts, supplier list table, and highlighted Ariba CI Training entry.

  8. You can also see the notification of new supplier getting added under Alerts & Messages section.

  9. You then need to define SAP Vendor ID for that supplier. Click on More Actions button & select Edit from the dropdown.

    SAP Ariba interface in Supplier Enablement tab showing supplier list, More Actions dropdown expanded with the Edit option highlighted.

  10. On the next page, scroll down to Unique Supplier ID Configuration section, click Add to define SAP Vendor ID.

    SAP Ariba interface showing Unique Supplier ID Configuration with an empty table and Add button highlighted at the bottom.

  11. In the Add Supplier Unique Keypopup, enter 10 digit SAP Vendor ID & click Save. Make sure that you also add any leading zeros in the vendor ID.

    Add Supplier Unique Key pop-up in SAP Ariba with Vendor ID field filled and Save button highlighted for submission.

  12. Your Ariba Network Supplier is now associated with an SAP Vendor ID. Click Save.

Learning

SAP FacebookSAP YoutubeSAP LinkedIn