Analyzing Request for Quotation (RFQ) and Quote Message Configurations

Objective

After completing this lesson, you will be able to describe the Request for Quotation (RFQ) and Quote Message Configurations and flow.

Overview

Sourcing Transactions Integration Overview

SAP Ariba Sourcing solutions integrated with SAP system(s) via CIG can export transactional data to SAP system(s) via the following methods:

Direct Connectivity using SAP Cloud Connector
Mediated Connectivity using SAP PI / PO or SAP CPI

Note

In this session we will explore the Direct Connectivity flow.

The SAP Ariba Sourcing integration is technically realized via the Ariba Network as the central entry (and exit) point to allow the sourcing professional to determine the best way to source the spend.

Supported transactions:

Request for Quotation (RFQ)
Award / Quote Message (QM)
Contract Request (CR)
Scheduling Agreement (SA)
Purchase Info Record (PIR)
Bill of Materials integration (BOM)

Un-supported transactions:

SAP Ariba Supplier Information and Performance Management

Overview: Integration process

Sourcing Transactions Integration Process Overview

From SAP System, Purchasing Organization or Buyer creates Purchase Requisition having material items or service items & based on that Purchase Requisition, RFQ or Quote Request can be created.
RFQ can also be created directly in SAP System without referring to a Purchase Requisition.
The RFQ gets sent to SAP Ariba Sourcing via CIG & Ariba Network which will then create a Sourcing Request in Ariba Sourcing. CIG creates a cXML QuoteRequest document that contains specific information required to create a Sourcing Request.
To generate a Sourcing Request, a Request for Quotation created in SAP System must be defined as a Strategic Sourcing Document Type. SAP System requires a mandatory vendor field in RFQ, so users need to create a "placeholder supplier" for strategic sourcing documents.
Strategic sourcing documents are converted into a cXML QuoteRequest document & the placeholder vendor information is automatically discarded during conversion in CIG.
- If various departments have a requirement for a laptop bag, then all these are aggregated into a PR.
- Purchase requisitions are internal documents you use to request your Purchasing department to procure a particular quantity of a material or a service for a particular date.
- Purchase requisitions are either created manually by the department responsible or automatically by MRP.
- The Purchase Dept. in the Organization calls / requests for the quotation for the products against which PR was raised.

Overview: Integration Process Overview

SAP Ariba Sourcing processes the QuoteRequest & creates a Sourcing Request. A Sourcing Manager approves the request, creates a Sourcing Event & invites suppliers to participate in the bid based on the criteria specified in the QuoteRequest document & the Sourcing Request template.
Once suppliers are invited, notification email will be sent to them for participating in bidding process.
Suppliers bid on the Sourcing Event & Ariba Sourcing creates an Award for the winning bid. Ariba Sourcing sends the award as a QuoteMessage back to the SAP system.
Based on the information in the QuoteMessage for the award, either a Purchase Order or a Contract or a Scheduling Agreement will get created in the SAP system.
SAP system sends a confirmation to Ariba Sourcing for all of the above document type.
When Ariba Contracts sends a Contract or Scheduling Agreement, CIG replicates same on the SAP system & sends a response confirming the creation of the Contract or Scheduling Agreement on the SAP system. It also sends a confirmation when the Contract or Scheduling Agreement has been updated or deleted on the ACM.
The confirmation message contains the Purchase Order ID or Contract ID & the status code. A status code of 200 when received successfully else it will be treated as failure to create the Purchase Order or Contract.
Buyers can create a Sourcing Event or Contract Line Items Document (CLID) directly from Ariba Sourcing or Ariba Contracts. These Sourcing Events do not need an associated QuoteRequest from the SAP system.

Note

If users create a custom StrategicSourcingDocType & select that custom document type when creating a RFQ, then they must maintain the same custom document type in SAP Ariba Cloud Integration Gateway cross reference section.
For details of Prerequisites & Limitations of RFQ, QM, Scheduling Agreement & Contract, please refer to SAP Ariba Cloud Integration Gateway Overview Guide.

SAP Ariba Strategic Sourcing – Request for Quotation and Award

Workflow diagram illustrating integration between SAP Ariba Sourcing, SAP ERP/S4HANA, Ariba Network, and suppliers for sourcing and procurement.

SAP Ariba Strategic Sourcing – Contract Scheduling Agreement

Flowchart showcasing SAP Ariba Sourcing integration with SAP ERP/S4HANA and Ariba Network for contract management and supplier collaboration.

Request for Quotation (RFQ) Flows

SAP System Users Can Create & Send a RFQ as Follows:

By creating a request for quotation from the SAP ERP System & sending a QuoteRequest cXML document to Ariba Sourcing.
By creating an RFQ event that originates in the SAP ERP system & sending it across to Ariba Network, where an RFQ event is created & published on SAP Ariba Discovery.

SAP System Users Can Create RFQ with Material Items or Service Line Items as Follows:

By creating a new Request for Quotation.
By creating a Request for Quotation against a Purchase Requisition.
By creating a Request for Quotation against a Contract (Outline Agreement).
SAP System users can add one or multiple service items in a RFQ.
The request for quotation can include service item (category D) with up to five-level hierarchy (one parent item and four-level Outline hierarchy).
Users can send attachments & comments from SAP System to Ariba Sourcing solutions.
Attachments at the header-level & line item-level for new & change RFQ are supported.
To add attachments to RFQ, users need to configure the DMS on SAP System.
The size of the attachments for both inbound & outbound documents cannot exceed 100 MB. Attachments can additionally have a payload of up to 40 MB.
If the attached file is encrypted or protected with password, Ariba Network does not decrypt the file for the end user of the attachment.
Text descriptions at the header-level & line-item level for internal & external users are supported.
If user creates a RFQ against a Purchase Requisition, the text description for both the internal & external users available in the Purchase Requisition appears in the RFQ.

Limitations:

SAP System supports file name of attachments up to 50 characters including extension.
SAP System supports maximum 40 characters in line item text for create & change Request For Quotations.
Attachments for service line items in Request For Quotations are supported only at the parent line level & not at the specification line level.

Note

For more information on limitations, please refer to the SAP Ariba Cloud Integration Gateway Overview Guide.

RFQ Flows: Configure in SAP System

There are 3 sub activities in this section:

Global settings
General settings
1. Interface Setup
2. BAdIs
Transaction specific settings
1. Define Message Output Control
2. Interface settup
3. Implement Customer Exit
4. Configure SRVMAPKEY

Request for Quotation Flow – Ariba Cloud Integration Specific 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 Ariba Sourcing & Ariba Procurement integration. Define unique values of variant & partition for your Ariba realms. This is required by our various export programs to apply filters & parameters while exporting data for a specific Ariba solution.

Maintain BAdIs as per your requirements to further massage the data for filters & parameters before storing it in Ariba specific tables.

Request for Quotation Flow – Ariba Cloud Integration Specific Configuration in SAP System. General Settings

To navigate to general settings in SAP ERP and SAP S/4 HANA for SAP Ariba Sourcing 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 → SAP Ariba Strategic Sourcing Integration → General Settings

SAP IMG screen displaying configuration menu for SAP Ariba Strategic Sourcing Suite Integration, highlighting the General Settings section.

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.

RFQ Flows: Configure in SAP System - Transaction Specific Settings (TSS)

Transaction Specific Settings (TSS)

Navigate to configure Ariba Network transactions:

SAP Implementation Guide (IMG) screen showing SAP Ariba Strategic Sourcing Integration configuration with highlighted General Settings and Application Specific Settings.

Run the truncation code SPRO – the Customizing: Execute Project screen appears
Click SAP Reference IMG – the Display IMG screen appears
Navigate to Integration with Other SAP Components → Ariba Cloud Integration Gateway → Ariba Strategic Sourcing Integration → Application Specific Settings

For sending RFQ to CIG & then to SAP Ariba Sourcing, you need to perform following activities:

Define Message Output Control for Request for Quotation
Maintain parameters for Request for Quotation
Configure TextIDs for Buyer and Supplier in RFQ
Implement a Customer Exit for Request for Quotation
Configure the SRVMAPKEY for Service RFQ

Activity i. Define Message Output Control for Request for Quotation

Buyer users need to maintain the condition records & output types to process RFQs sent from the SAP System.

To maintain the condition records & output types:

Navigate to Integration with Other SAP Components → Ariba Cloud Integration Gateway → SAP Ariba Strategic Sourcing Integration → Application Specific Settings → Request for Quotation (RFQ) using the transaction code SPRO.
Expand Request for Quotation (RFQ) section & click IMG-Activity for Define Message Output Control for Request for Quotation – The Conditions for Output Control page appears.
Select application EA & click Output Types. The Display View "Output Types": Overview page appears.
Click the output type maintained for the RFQ. (example: choose NEU), click Change. The Change View "Output Types": Overview page appears.
Click New Entries, the New Entries: Details of Added Entries screen appears.
On the General Data tab, select 0001 DocType/PurchaseOrg/Vendor in the Access sequence field.
On the Default tab, enter the following values:
- Dispatch time: Send immediately (when saving the application)
- Transmission Medium: EDI
- Partner Function: LS
Click Save.
Click the output type maintained for the request for quotation. For example, NEU & double-click Processing routines. The Change View "Processing routines": Overview page appears.
In the Processing routines section, create an entry as follows:
- Transmission Medium: EDI
- Program: RSNASTED
- FORM routine: EDI_PROCESSING
Click Save.
In the Partner Functions section, create an entry as follows:
- Medium: EDI
- Function: LS
- Description: Logical System
Save the changes & go to the Conditions for Output Control page.
Click the output type maintained for the request for quotation (example: NEU), double-click Condition records. The Output Types dialog box appears.
Click the relevant output type (example: NEU), click Condition records – the Key Combination popup appears.
Click the Purchasing Output Determination: Doc Type/Purch. Org./Vendor, click Enter.
Maintain the following parameters by creating a new entry:
- Purchasing Doc Type: Choose a purchasing doc type. For example, AN.
- Purch. Organization: Choose a purchasing organization.
- Vendor: Choose a vendor.
Click Save.
Click Execute.

Activity ii. Maintain Parameters for Request for Quotation

Buyer users need to maintain the parameters to send the text descriptions at the header-level & line-item level for internal & external users in RFQ.

To maintain the text descriptions parameters:

SAP screen for Parameters - Request for Quotation, showing variable names, field names, number variants, partitions, and values for RFQ configuration.

Navigate to Integration with Other SAP Components → Ariba Cloud Integration Gateway → SAP Ariba Strategic Sourcing Integration → Application Specific Settings → Request for Quotation (RFQ) using the transaction code SPRO.
Expand Request for Quotation (RFQ) section & click IMG-Activity for Maintain parameters for Request for Quotation – the Parameters – Request for Quotation page appears.
Maintain the parameters as mentioned in the table within this activity.

Variable Name	Required for..	Field Name	Variant	Partition	Low
RFQ_EXTERNAL_NOTE	To send the long text description specified at the header-level for external users in the Request for Quotation.	EKKO	The unique variant name for the SAP Ariba Sourcing solution in SAP System.	The unique site name for the SAP Ariba Sourcing solution in SAP System.	Enter the text ID for the long text description for external users.A01 (For example).
RFQ_EXTERNAL_NOTE	To send the long text description specified at the line-item level for external users in the Request for Quotation.	EKPO	The unique variant name for the SAP Ariba Sourcing solution in SAP System.	The unique site name for the SAP Ariba Sourcing solution in SAP System.	Enter the text ID for the long text description for external users.A01 (For example).
RFQ_INTERNAL_NOTE	To send the long text description specified at the header-level for internal users in the Request for Quotation.	EKKO	The unique variant name for the SAP Ariba Sourcing solution in SAP System.	The unique site name for the SAP Ariba Sourcing solution in SAP System.	Enter the text ID for the long text description for external users.A03 (For example).
RFQ_INTERNAL_NOTE	To send the long text description specified at the line-item level for internal users in the Request for Quotation.	EKPO	The unique variant name for the SAP Ariba Sourcing solution in SAP System.	The unique site name for the SAP Ariba Sourcing solution in SAP System.	Enter the text ID for the long text description for external users.A03 (For example).
RFQ_ENABLED	To enable the RFQ integration. This parameter setting allows SAP Ariba Sourcing to receive and process RFQs from SAP system.		The unique variant name for the SAP Ariba Sourcing solution in SAP System.	The unique site name for the SAP Ariba Sourcing solution in SAP System.

Activity iii. Configure TextIDs for Buyer and Supplier in RFQ

Buyer users need to maintain the parameters to send the text descriptions at the header-level & line-item level for internal & external users in Service RFQ.

To maintain parameters:

Navigate to Integration with Other SAP Components → Ariba Cloud Integration Gateway → SAP Ariba Strategic Sourcing Integration → Application Specific Settings → Request for Quotation (RFQ) using the transaction code SPRO.
Expand Request for Quotation (RFQ) section & click IMG-Activity for Configure TextIDs for Buyer and Supplier in RFQ – Change View Configure TextIDs for Buyer and Supplier in RFQ page appears.
Maintain the parameters as mentioned in the table on next slide

Text Object	Text Description	Required for	Visible To Suppliers
ESLL	LLTX	To send the long text description specified at the header-level for external users in the request for quotation.	Select "X true" to enable visibility to suppliers. Select "– false" to disable visibility to suppliers.
ESLL	LLTX	To send the long text description specified at the line-level for external users in the request for quotation.	Select "X true" to enable visibility to suppliers. Select "– false" to disable visibility to suppliers.

SAP screen for Configure Text IDs for Buyers and Suppliers, showing text objects, description IDs, and supplier visibility settings (true/false).

Activity iv. Implement a Customer Exit for Request for Quotation

Buyer users need to implement the following customer exit for RFQ. Users can enhance the RFCs provided by Ariba by adding customer exits or make changes to enhancement points.

To implement customer exit for RFQ:

Navigate to Integration with Other SAP Components → Ariba Cloud Integration Gateway → SAP Ariba Strategic Sourcing Integration → Application Specific Settings → Request for Quotation (RFQ) using the transaction code SPRO.
Expand Request for Quotation (RFQ) section & click IMG-Activity for Implement a Customer Exit for Request for Quotation – The Project Management of SAP Enhancements page appears.
Provide Project name, click Create.
Click Enhancement Assignments – the Create Object Directory Entry pop-up appears.
Provide an existing Package name (or click Local Object).
Enter the user exit name, MM06E001, press Enter.
Go back & click Components.
Double-click the enhancement EXIT_SAPLEINM_002.
In the next screen that appears, scroll down, double-click INCLUDE ZXM06U02, press Enter.
Copy & paste the code INCLUDE arbcig_quote_request_002, click Activate.
Go back & click Components, then double-click the enhancement EXIT_SAPLEINM_011.
In the next screen that appears, double-click INCLUDE ZXM06U33, press Enter.
Copy & paste the code INCLUDE arbcig_quote_request_011, click Activate.
Go back & Activate the user exit also.

Activity v. Configure the SRVMAPKEY for Service RFQ

Buyer users need to configure this setting only if the Service RFQ transfer from SAP System to Ariba Network fails.

This usually occurs when the business function LOG_MM_P2PSE_1 is not active on your SAP System.
Users need to implement the SAP Note 2372821 only if the standard field SRVMAPKEY is not activated on your SAP System.
The standard field SRVMAPKEY in the SAP Table ESLL stores Service RFQ 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 & the integration will fail.

RFQ Flows: Configure in CIG

In this section, user needs to perform following activities. All these are discussed in CIG Configuration session.

Here we will focus on only those configurations in CIG which are very specific to RFQ integration:

Enable CIG for your Ariba Sourcing Realm.
Provide Basic Information in the project in CIG for "Product = Ariba Sourcing".
Define Connection information to establish connectivity between CIG & your SAP system.
Define Cross Reference for Parameter for RFQ (Doc Type – QuoteRequest).
Define Cross References for UOM.
Define Cross References for Lookup Table for RFQ (Doc Type – QuoteRequest).
Review project configuration & Confirm the Project.
Test the Project.
Deploy the Project.

In this section you need to define values in the parameter fields 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.

To define values in parameters:

Select the Document Type = QuoteRequest in Parameters tab, click Add.
Edit the entry.
Enter values for the parameters in the TEST Environment and PROD Environment & click Save. If you want to have different value in PROD Environment, uncheck the box Use same values.
Enter parameter values for another Document Type as needed or click Next.

Cross Reference - Parameter

QuoteRequest –

RFQ Dummy Vendor:

In SAP, it is mandatory to provide a vendor ID to create an RFQ. But the purpose of sending RFQ document to Ariba Sourcing is to find a suitable vendor / supplier. Thus, Ariba Sourcing doesn’t need vendor information in RFQ / Sourcing Request.

In this parameter, Ariba recommends to maintain the vendor ID used in RFQ creation in SAP system. If you do so, the vendor information will not be mapped in the cXML to be sent to Ariba Sourcing.

If you don’t maintain this parameter, then in Ariba Sourcing you will see the vendor added to the list of bidding suppliers in Sourcing Project. You can then remove this vendor manually from the list.

RFQ Flows: Configure in CIG

In this section you need to define lookup values which you want to map.

Users need to maintain certain fields that Ariba requires for document types per transaction.

SAP Ariba recommends that you maintain fields that support more than one value in the Cross Reference Lookup table of the CIG.

To maintain fields that support more than one value in the Cross Reference Lookup table of the CIG:

SAP Cloud Integration Gateway showing Cross Reference Configuration's Lookup Table mapping Ariba Values to Customer Values for TEST and PROD environments.

Select the Document Type = QuoteRequest in Lookup Table tab.
Edit the Lookup Value field: QuoteRequestMatchingType.
Enter values for the fields in the TEST Environment and PROD Environment & click Save.
Enter Lookup Values for another Document Type as needed or click Next.

Cross Reference - Lookup Table

QuoteRequest –

Quote Request Matching Type:

Based on the solution you subscribed for, Ariba Network routes the RFQ document either to Ariba Discovery (Quote Automation Solution) or to Ariba Sourcing site (Strategic Sourcing Solution).

In both the scenario, cXML structure of the QuoteRequest message remains same. For Quote Automaton, defining Quote Request Matching Type is mandatory as based on that suppliers will be invited to bid against that RFQ. Thus, you need to maintain mapping of Quote Request Matching Type with specific document types that you will use to create RFQ in

Though maintaining this mapping has no relevance to the Strategic Sourcing Flow, since we use the same cXML structure, you need to maintain this mapping in Cross Reference Lookup Table.

If you don’t maintain this mapping, Ariba Network will reject the QuoteRequest document.

RFQ Flows: Configure in Ariba Network

RFQ Flows - Configure in Ariba Network

Note

From the list of activities listed below, AN Admin Activities are performed by Ariba Customer Support either during the activation of AN Buyer Account or at the time of enabling new solution for customer.
Customers need to contact Ariba Custom Support when they are ready to adopt the solution.

ACTIVITIES (I-V)

AN Admin Activities

Enable Open Network & Enable End Point
Enable Multi ERP (if you are using Multi-ERP setup)
Enable Quote Automation (only if you want to send RFQ to Ariba Discovery)
AN Buyer Account Admin Activities
Define System IDs & End Point IDs
Configure Document Routing

Activity I: Ariba Network Admin - Enable Open Network & Enable End Point

RFQ integration from SAP System to Ariba Sourcing is realized via Ariba Network.

Ariba Open Network settings with Convert to Ariba Open Network option selected, including update buttons and flow configuration dropdown.

Thus, in order to route the RFQ (QuoteRequest) document to SAP Ariba Sourcing, an End Point needs to be defined.

Configuration screen showing End Point settings with Enable end point support selected and additional options for Multi ERP support.

In Ariba Network, to define End Point, the particular Buyer Account needs to be enabled for Open Network.

Once the Buyer Account is enabled for Open Network, Business End Points (cXML and OData Setup) link will be available to define End Points.

Ariba Network Configuration page listing various settings, highlighting Business End Points (cXML and OData Setup) for integration preferences.

Activity II: Ariba Network Admin - Enable Multi ERP (If You Are Using Multi-ERP Setup)

If you are using Multi ERP setup, you would need to define backend System IDs to route the documents to the respective SAP System.

Ariba Open Network settings screen with Convert to Ariba Open Network enabled and various configuration options for buyer preferences.

In Ariba Network, to define System ID, the particular Buyer Account needs to be enabled for Multi ERP. For this purpose also, enablement of Open Network is required.

Settings page displaying Enable multiple ERP support under Multi ERP, along with end point support configurations and update options.

Once the Buyer Account is enabled for Multi ERP, Business Application IDs and End Points (cXML and OData Setup) link will be available to define System IDs & End Points.

SAP Ariba Network Configuration page displaying various settings, with Business Application IDs and End Points (cXML and OData Setup) highlighted.

Activity III: Ariba Network Admin - Enable Quote Automation (Only If You Want to Send RFQ to Ariba Discovery)

If you wish to use Ariba Discovery capabilities for sourcing process, you can route the RFQ documents to Ariba Discovery instead of SAP Ariba Sourcing.

To achieve that, in Ariba Network, the particular Buyer Account needs to be enabled for Quote Automation.

Configuration screen displaying options for Quote Automation, Enable ASV Intelligent PO, and Other Buyer Entitlement with checkboxes.

Activity IV: Ariba Network Buyer Account Admin - Define System IDs & End Point IDs

If you are using Multi ERP setup, once the required setup is enabled for your Buyer Account, you would need to define backend System IDs & End Point IDs to route the documents to the respective applications – Ariba Sourcing or SAP System.

To define System IDs & End Point IDs:

Login to you’re an Buyer Account & click Administration.
Click Configuration.
Click on Business Application IDs and End Points (cXML and OData Setup) link – The Configure Business Applications IDs page appears.
Click on Create button – the Create a System ID page appears.
Provide required details & click Save. Please note that The System ID field should be filled with the system ID value exactly matching with your backend system ID value.
To define End Point, click System ID under List of System IDs – the Manage Business Application ID: ＜System ID＞ page appears.
Click End Point.
Click Create.
Create 2 End Points as mentioned in the below:
- Create End Point to route the RFQ documents to Ariba Sourcing & provide following information:
  - End Point ID: Ariba
  - Select an Integration Type: Select cXML.
    Select an Authentication Method: Shared Secret or Certificate
  - Post URL: URL of Ariba Sourcing application suffixed by Buyer AN ID.
  - Tick the Yes, I want to receive documents through the POST method instead of through the cXML GetPending method check box.
  - Click Save.
  Note
  The Shared Secret or Certificate should match with that provided in Ariba Sourcing site profile.
- Create End Point to route the Quote Message / Award & Contract documents to your backend SAP System & provide following information:
  - End Point ID: CIG
  - Select an Integration Type: Select cXML
  - Select an Authentication Method: Shared Secret or Certificate
  - Post URL: URL of CIG
  - TEST – https://testacig.ariba.com/http/receiveCXML or
  - PROD - https://acig.ariba.com/http/receiveCXML)
  - Tick the Yes, I want to receive documents through the POST method instead of through the cXML GetPending method check box.
  - Click Save.
Click Done. You will be navigated to Configure Business Applications IDs page.
Click Save. You will be navigated to Configuration page.
Click Done.

Activity V: Ariba Network Buyer Account Admin - Configure Document Routing

Once System IDs & End Point IDs are defined, you need to Configure Document Routing to define which End Point the particular document should be sent to – SAP Ariba Sourcing or SAP System.

To configure Document Routing:

Login to your AN Buyer Account, click Administration & Configuration.
Click on Business Application IDs and End Points (cXML and OData Setup) – the Configure Business Applications IDs page appears.
Click the System ID for which you want to configure document routing – the Manage Business Application ID: ＜System ID＞ page appears.
Click End Point.
Click on Configure Document Routing – the Configure Document Routing page appears.
Select End Point from the drop down list for following documents:
- Request for Quotations
- Quotes
- Contract Request
- Contract Status Update Request
Click OK.

RFQ Flows: Configure in SAP Ariba Sourcing

In this section, user needs to perform following activity. Here we will focus on only those configurations in Ariba Sourcing which are very specific to RFQ integration: Enable Sourcing ERP Integration.

This is a prerequisite to all the transaction documents flowing from and to SAP Ariba Sourcing.

SAP Ariba's Scheduled Tasks interface, highlighting the EnableSourcingProjectIntegrationTask with its status, last run, and actions.

This task will enable ERP integration for Sourcing projects. If you have not ran this Scheduled Task, integration to SAP Ariba Sourcing will fail.
This task ensures that all cXML QuoteRequest documents received in Ariba Sourcing are treated as sourcing requests rather than Spot Quote events.
Users need to contact Ariba Customer Support to complete this activity.

Quote Message / Award Flows

When suppliers bid on the Sourcing Event & SAP Ariba Sourcing creates an Award for the winning bid, SAP Ariba Sourcing sends the Award as a QuoteMesage back to the SAP System.

Based on the information in the QuoteMesage for the award, CIG creates either a Purchase Order or a Contract (Outline Agreement) or a Scheduling Agreement on the SAP System.
If the Award contains the reference Document Type as framework order & the Document Category as FO, CIG creates a Purchase Order of Framework Order type with the Validity Start & Validity End dates on the SAP System.
To create a Purchase Order or a Framework Order, users need to maintain the Cross Reference Parameter in CIG.

Note

Ensure that you have raised an SR with Ariba Customer Support to execute "Enable Sourcing ERP Integration" task.

Ariba Cloud Integration Gateway sends a confirmation to Ariba Sourcing after creating a PO, FO, Scheduling Agreement or Contract.

The confirmation message contains the following information:

SAP Contract ID & Date
SAP PO ID & Date
Sourcing Event ID
Vendor ID
Status Code – 200 (Received successfully) or 503 (Failure)
Status Text – Success or Failure

Quote Message / Award Flows: SAP Ariba Sourcing: Define Enumerations

This is required to define whether the Quote Message should be consumed in SAP System as a Purchase Order, a Contract or a Scheduling Agreement.

SAP’s Administration interface under Customization Manager, highlighting specific enumerations for document types with export options.

Users need to contact Ariba Customer Support to get this activity done.

The file ariba.sourcing.integration.documenttype.xls will define the Document Type

Purchase Order (F)
Contract (K)
Scheduling Agreement (L)

The Excel file downloaded from Ariba Sourcing Admin site needs to filled in with these values & then will be uploaded for the specific customer realm.

Enumeration	Display Value	Value
ariba.sourcing.integration.documenttype	@aml.sourcing.RFxExt/PODocumentTypeLabel	F
ariba.sourcing.integration.documenttype	@aml.sourcing.RFxExt/ContractDocumentTypeLabel	K
ariba.sourcing.integration.documenttype	@aml.sourcing.RFxExt/SchedulingAgreementTypeLabel	L

The file ariba.sourcing.integration.documentcategory.xls will define the Document Category

Value Contract (WK)
Material Contract (MK)
Standard Purchase Order (NB)
Framework Order (FO)
Scheduling Agreement (LP)
Scheduling Agreement Release (LPA)

The Excel file downloaded from Ariba Sourcing Admin site needs to filled in with these values & then will be uploaded for the specific customer realm.

Enumeration	Display Value	Value
ariba.sourcing.integration.documentcategory	@aml.sourcing.RFxExt/WKDocumentCategoryLabel	WK
ariba.sourcing.integration.documentcategory	@aml.sourcing.RFxExt/MKDocumentCategoryLabel	MK
ariba.sourcing.integration.documentcategory	@aml.sourcing.RFxExt/NBDocumentCategoryLabel	NB
ariba.sourcing.integration.documentcategory	@aml.sourcing.RFxExt/NBDocumentCategoryLabel	FO
ariba.sourcing.integration.documentcategory	@aml.sourcing.RFxExt/LPDocumntCategoryLabel	LP
ariba.sourcing.integration.documentcategory	@aml.sourcing.RFxExt/LPADocumntCategoryLabel	LPA

Quote Message / Award Flows: Ariba Network

There is no configuration required in Ariba Network specific to Quote Message / Award integration from SAP Ariba Sourcing to SAP System.

Please ensure that you have performed following configuration activities that are already covered in Request for Quotation flow lesson:

Raise SR with Ariba Customer Support to enable following features on your AN Buyer account:
- Enable End Point
- Enable Multi-ERP (if you are using Multi-ERP setup)
- Enable Quote Automation (only if you want to send RFQ to Ariba Discovery)
Define System IDs & End Points in your AN Buyer account
Configure Document Routing in your AN Buyer account

Quote Message / Award Flows: Configuration in CIG –Cross Reference Configuration – Parameter

In this section, user needs to perform following activities. All these are discussed in CIG Configuration session. Here we will focus on only those configurations in CIG which are very specific to QM / Award integration:

Enable CIG for your Ariba Sourcing Realm.
Provide Basic Information in the project in CIG for "Product = Ariba Sourcing".
Define Connection information to establish connectivity between CIG & your SAP system.
Define Cross Reference for Parameter for either of following:
- Quote Message for Purchase Order (Doc Type – QuoteMessageOrder)
- Quote Message for Material Contract (Doc Type – QuoteMessageContract)
- Quote Message for Service Contract (Doc Type – QuoteMessageContractServices)
- Quote Message for Scheduling Agreement (Doc Type– QuoteMessageSchedulingAgreement)
Define Cross References for UOM.
Define Cross References for Lookup Table not required for Quote Message.
Review project configuration & Confirm the Project.
Test the Project.
Deploy the Project.

In this section you need to define values in the parameter fields 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.

Follow these steps to define parameters:

Select the Document Type = QuoteMessageOrder (for example) in "Parameters" tab & click Add.
Edit the entry.
Enter values for the parameters in the TEST Environment and PROD Environment & click Save. If you want to have different value in PROD Environment, uncheck the box Use same values.
Enter parameter values for another Document Type as needed or click Next.

Parameters:

Parameter	Description	Example Values
AccountAssignmentCategory	Supports the accounting information of the buyer organization.	F
SurchargeAbs	Supports the summary amount for the additional charges in the QuoteMessageOrder document. Applicable only when taxes & allowances are applied.	ZB00
SurchargePercentage	Supports the AdditionalCost percentage amount in the QuoteMessageOrder document. Applicable only when taxes & allowances are applied.	ZA00
Asset	Supports the Asset information for the buyer organization.	100
CostCenter	Supports information about the Cost Center.	9010
DiscountAbs	Supports the details of the deductions available for the items. Applicable only when taxes & allowances are applied.	RB00
DiscountPercentage	Supports the details of the percentage of deductions available for the items. Applicable only when taxes & allowances are applied.	RA00
DefaultCompanyCode	Supports information about the Company Code.	1
DefaultPurchasingGroup	Supports information about the PurchasingGroup.ID for the buyer.	1
DefaultPurchasingOrg	Supports information about the PurchasingOrganization.ID for the buyer.	1
GLAccount	Supports information about the General Ledger Accounts.	417000
GrossPrice	Supports the Gross Pricing Condition of the service item.	PB00
HeaderTextID	Supports the long text description ID specified at the header-level.	K01
LineTextID	Supports the long text description ID specified at the line item level.	K01
Order	Supports the order ID. This field is required when the account assignment category is set to F.	100060
TotalPrice	Supports the gross pricing condition of the service item.	PRS
SpotQuoteID	Supports the ID for the request for quotations sent for Quote Automation to Ariba Network & SAP Ariba Discovery.	F02
AssetSubNumber	Supports the sub-number when the AccountingSegment ID information is set to A.	123
WBSElement	Supports the WBS Element accounting information.	34232

Note

Similar type of parameters are required to be defined for QuoteMessageContract, QuoteMessageContractServices & QuoteMessageSchedulingAgreement.
The information can be found in SAP Ariba Cloud Integration Gateway Configuration Guide.

Quote Message / Award Flows: SAP System

Other than executing Interface Setup program (as described in General Settings section) to configure inbound proxy for the following messages, there is no Application Specific configuration required in SAP System for Quote Message / Award integration from Ariba Sourcing to SAP System.

Ariba Sourcing Purchase Order
Ariba Sourcing Contracts
Ariba Sourcing Service Items
Scheduling Agreement

Next lesson