SAP Ariba Services Technical Realization Document - Ferromex

INTERNAL
Project Technical Realization Document
Customer Name: Ferromex
Customer Project: Sourcing-CIG Migration

TABLE OF CONTENTS
PROJECT IDENTIFICATION....................................................................................................................... 2
REVISION HISTORY ................................................................................................................................... 3
1. OVERVIEW .................................................................................................................................. 3
1.1. Purpose ....................................................................................................................................... 3
1.2. Customer Landscape ................................................................................................................. 4
1.3. Architecture Diagram ................................................................................................................. 4
1.4. Ariba Solutions ........................................................................................................................... 4
1.5. Interfaces .................................................................................................................................... 5
1.6. Technical Assumptions.............................................................................................................. 5
1.7. Out of Scope Items ..................................................................................................................... 5
1.8. Relationship to other documentation ........................................................................................ 5
2. ARIBA TECHNICAL DETAILS ..................................................................................................... 5
2.1. Sourcing...................................................................................................................................... 5
2.1.1. Request for Quotation ................................................................................................................ 6
2.2. Ariba Contract Management ............................................................ Error! Bookmark not defined.
3. CLOUD INTEGRATION GATEWAY ............................................................................................10
3.1. CIG Portal...................................................................................................................................10
3.2. CIG Mapping ..............................................................................................................................11
3.3. CIG Addon .................................................................................................................................11
4.3.1 Add-on Configuration of Master Data Integration ....................................................................11
4.3.2 Add-on Configuration of Outbound Transactions (ECC to Ariba) ...........................................11
4.3.3 Add-on Configuration of Inbound Transactions (Ariba to ECC)..............................................11
4.3.4 CIG Addon Configurations ........................................................................................................11
4.3.5 CIG Addon Customizations.......................................................................................................12
3.4. CIG Security ...............................................................................................................................12
3.5. Cloud Connector .......................................................................................................................12
4. MISCELLANEOUS......................................................................................................................13
4.1. SSO ............................................................................................................................................13
PROJECT IDENTIFICATION
Project Name
Sourcing-CIG Migration
Customer Name
Ferromex Grupo Mexico
SAP Ariba Project Manager Customer Project Manager
Jorge Herrera ___________
REVISION HISTORY
Author Document Location (repository/path/name)
Carlos Perdomo ___________
Document
Version Status Date (dd-mmm-yyyy)
Classification
0.1 Draft 14-12-2021 Internal
1. OVERVIEW
1.1. Purpose
© 2020 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. All other product and service names mentioned are the trademarks of their respective companies. Please see http://www.sap.com/trademark for
additional trademark information and notices
3
In this document you will be able to understand the technical view of the Ariba Network and application
configurations. Also, this document will provide Cloud Integration Gateway configuration and customizations
details for integration with SAP ERP.
1.2. Customer Landscape
System Details
ERP ECC 6.0 EHP 8.0 SP20(QAS) SP11(PRD)
Middleware N/A
Adapter CIG Addon
Ariba Buyer Network

ID
AN1011093303
Realm ID Parent/Child/Upstream URL
Ariba Realm ferromex-T Upstream http://ferromex-T.sourcing.ariba.com/
ferromex Upstream http://ferromex.sourcing.ariba.com/
1.3. Architecture Diagram
1.4. Ariba Solutions
Following are the Ariba solutions that will be implemented as part of this project.
4
Strategic Procurement
Sourcing
1.5. Interfaces
Following are the list of interfaces included in current scope.
Source Integration
Item # Name of the Interface Destination System Format
System Tool
1 RFQ ERP Ariba Sourcing cXML CIG
Ariba
2 Award – Purchase Order ERP cXML CIG
Sourcing
Ariba
3 Award – Contract ERP cXML CIG
Sourcing
Ariba
4 PO or AO response ERP cXML CIG
Sourcing
1.6. Technical Assumptions
• Two Non-production ERP environments and one Production environment will be integrated as part of
this project.
• ERP and Middleware connectivity is established as part of infrastructure readiness
1.7. Out of Scope Items
• SAP Functional configuration details in Materials Management module

• IT Firewall Rule
• SAP BASIS Configurations
1.8. Relationship to other documentation
Document Description Location
Architecture Review Customer Landscape Architecture Review - TEAMS
Middleware Strategy SAP recommendation for Middlware Middleware Strategy - TEAMS
2. Ariba Technical Details
2.1. Sourcing
5
Process Flow
Integration Workflow
2.1.1. Request for Quotation
Overview
RFQ and award integration with SAP Ariba Sourcing includes the following features:
• SAP RFQ and Award integration with SAP Ariba Sourcing

• Award integration using material master item data
The SAP RFQ and award integration with SAP Ariba Sourcing features enable you to create SAP Ariba
Sourcing events based on the information received from an ERP system. These features can also send
award data to an ERP that the ERP uses to create a purchase order or a contract. The Award integration
using material master item data feature enables you to send SAP Ariba Sourcing award data to an SAP
ERP without creating an RFQ on the ERP.
Prerequisites
6
• Your SAP Ariba Sourcing installation must be configured for master data integration with SAP
ERP.
• Ariba Administrator enables Sourcing integration with ERP by running the scheduled task,
EnableSourcingERPIntegration. This task ensures that all cXML QuoteRequest documents
received in SAP Ariba Sourcing are treated as sourcing requests rather than spot quote events.
• Ariba Administrator must configure an Ariba Network endpoint. An Ariba Network buyer
account must be configured to route QuoteRequest documents to SAP Ariba Sourcing.
• Ensure that you enable the SAP Ariba Cloud Integration Gateway for SAP Ariba Sourcing. To
configure SAP Ariba Cloud Integration Gateway, you must be a member of the Integration
Admin or Customer Administrator group.
• To use all the functionalities that SAP Ariba for SAP Ariba Contracts provides, ensure that SAP
Ariba Customer Support enables the cXML New Format and cXML Version 34 Added Feature
options in your SAP Ariba Strategic Sourcing Suite site.
• Buyers and suppliers must configure the required rules and necessary settings in their Ariba
Network, SAP Ariba Sourcing, and SAP Ariba Contracts user accounts to send and receive
quoteRequest, quoteMessage, and contract Request for material items and service line item
hierarchies.
Workflow
• A buyer creates a Request for Quotation (RFQ) having material items or service items on the
SAP ERP system.
• SAP Ariba Cloud Integration Gateway creates a cXML QuoteRequest document that contains
specific information required to create a sourcing request for material or service items and
sends it to SAP Ariba Sourcing through Ariba Network.
• SAP Ariba Sourcing processes the QuoteRequest and creates a sourcing request. A sourcing
manager approves the request, creates a sourcing event, and invites suppliers to participate
based on the criteria specified in the QuoteRequest document and the sourcing request
template.
• Suppliers bid on the sourcing event and SAP Ariba Sourcing creates an award for the winning
bid.
• SAP Ariba Sourcing sends the award as a QuoteMesage back to the ERP system.
• Based on the information in the QuoteMesage for the award, SAP Ariba Cloud Integration
Gateway creates a purchase order or contract on the SAP ERP system.
• SAP Ariba Cloud Integration Gateway also sends a confirmation when the contract has been
updated or deleted on the SAP ERP system.
Limitations
Request for quotations and contracts
• SAP ERP can only create purchase orders or outline agreements from SAP Ariba Sourcing
awards.
• SAP ERP only accepts awarded quote messages to generate purchase orders or outline
agreements (contracts). Awards are not generated within SAP ERP.
• Network vendor master data integration is not supported.
• The update operation for request for quotations transfers only line item changes, not header-
level changes, into the Sourcing Request.
• Attachments are not transferred to purchase orders in SAP ERP.
• SAP Ariba Sourcing does not support deletion of the entire contract after it has been published.
You can only delete the line items in a contract.
7
• Although SAP Ariba Contract allows you to terminate a contract, information that the contract
is terminated is not sent correctly to SAP ERP. As a result, SAP Ariba Cloud Integration
Gateway does not support integration for terminated contracts.
Request for quotations with service items
Overview
Buyers using SAP Ariba Sourcing and SAP Ariba Contracts integrated with SAP ERP can add one or
multiple service items in a request for quotation.
The request for quotation can include service item (category D) with up to five-level hierarchy (one
parent item and four-level child hierarchy). The request for quotation can include the following:
Service item (category D) with up to five-level hierarchy (one parent item and four-level child hierarchy)
• One or more service specifications

• Service outlines with up to four-level hierarchies
SAP Ariba Cloud Integration Gateway supports end-to-end integration of only service child items of
standard line types.
When SAP ERP receives the award containing service items from SAP Ariba Sourcing and creates a
purchase order or contract, SAP Ariba Cloud Integration Gateway processes the service items in the
purchase order or contract. Each service item hierarchy can include spend limits (Overall Limit)
towards the total cost of unplanned service line items in the award. The Overall Limit is the maximum
value towards the total of all unplanned services.
Buyers using SAP Ariba Sourcing and SAP Ariba Contracts integrated with SAP ERP can add one
or multiple service items in a request for quotation.
Limitations
• The last level outline must contain at least one service specification. For example, if the service
item has a four-level hierarchy, ensure that you do not leave the fourth-level hierarchy blank.
The last service item in a request for quotation containing hierarchies cannot be left empty.
• This functionality requires SAP ERP 6.0, EHP 4 and greater. Attempting to create a purchase
order with a 5-level deep hierarchy when using EHP3 or lower generates an error message in
PO Message tab.
• Request for quotations cannot contain spend limits (Overall limit and Expected value).
• The pricing conditions are only supported at the line item-level in purchase orders.
• The contracts support pricing conditions only at the service specification level.
• Service hierarchies are not supported for order confirmations.
• Although SAP Ariba Cloud Integration Gateway sends the header-level and line-item level text
description, users on SAP Ariba Sourcing can only view the text descriptions for internal and
external users at the line-item level. SAP Ariba Sourcing does not allow users to view the text
descriptions for internal and external users at the header level.
• SAP ERP supports the different item categories for material and service line items. However,
SAP Ariba Sourcing only supports standard and service line items (material items and service
items-category D). Customers can use the other item categories by customizing and making
the necessary custom changes.
• An alternative service specification number must always be of a higher sequence. When you
add service specifications to a service line, ensure that you first add a Basic Line before adding
an alternative service specification. Ensure that you mark the service specification as an
alternative service specification with a higher line number. For example, you have service
specifications with line numbers 10, 20, and 30. When you specify an alternative service
specification, you can specify line number 20 as an alternative service specification to line
8
number 10 service specification. Similarly, line number 30 can be an alternative to service
specification with line numbers 10 or 20. However, line number 10 cannot be marked as an
alternative service specification to line number 20 or 30.
Quote Message
Overview
When a buyer sends the QuoteRequest to SAP Ariba Sourcing, SAP Ariba Sourcing processes the
QuoteRequest and creates a sourcing request. The sourcing manager approves the request, creates
a sourcing event, and invites suppliers to participate based on the criteria specified in the
QuoteRequest document and the sourcing request template.
SAP Ariba Sourcing sends the award as a QuoteMesage back to the ERP system. Based on the
information in the QuoteMesage for the award, SAP Ariba Cloud Integration Gateway creates a
purchase order, framework order, or contract (outline agreement) on the SAP ERP system.
• If the award contains the reference document type as framework order and the document
category as FO, SAP Ariba Cloud Integration Gateway creates a purchase order of framework
order type with the Validity Start and Validity End dates on the SAP ERP system.
• The contract that SAP Ariba Cloud Integration Gateway creates against the award also contains
the Validity Start and Validity End date information.
9
3. CLOUD INTEGRATION GATEWAY
3.1. CIG Portal
Projects Connection
IDs Product Document Types
Name Name
Development Landscape
QuoteRequest
AN ID: AN1011093303 -T
Sourcing DEV Ariba Sourcing DEVCLNT400 QuoteMessage
P User ID: P000563
QuoteMessageContract
Quality Landscape
QuoteRequest
AN ID: AN1011093303 -T
Sourcing DEV Ariba Sourcing QASCLNT400 QuoteMessage
P User ID - P000563
Production Landscape
QuoteRequest
AN ID: AN1011093303 QuoteMessage
Sourcing Ariba Sourcing BWP
P User ID - P000563 ContractRequest
Following Screen Shot display document types in CIG portal
10
3.2. CIG Mapping
Solution Source document type Source field Target document type Target field (Xpath)
(Ariba (eg: ORDERS05) (Xpath) (eg:OrderRequest)
Network/ Ariba
Buying/ Ariba
Sourcing)
Ariba Sourcing QuoteMessageOrder(cXML) LeadTime QuoteMessageOrder(Addon) PLAN_DEL
Ariba Sourcing REQOTE QuoteRequest ExternalNote
3.3. CIG Addon
CIG Addon Ariba Cloud Integration Gateway 1.0 add-on for SAP ERP (ARBCI1) SP 0015
Ariba Cloud Integration Gateway 1.0 add-on for SAP ERP (ARBCI2) SP 0011
4.3.1 Add-on Configuration of Master Data Integration
ERP
Transaction
Ariba Transaction Consumer Proxy Software S4 Software
Ariba Solution Service: Direction Document Type Code
Name Name Compone Component
IDOC/PROXY
nt
Outbound
AribaMasterDataRequestMessage CO_ARBCIG_MASTE
SRC PROXY (S/4HANA Master Data ARBCI1 ARBCI1
SourcingMasterDataImpor (CIG) R_DATA_REPLICAT
to Ariba)
4.3.2 Add-on Configuration of Outbound Transactions (ECC to Ariba)
Transaction
Ariba ERP Software
Service: Document Type Code Ariba Transaction Name Consumer Proxy Name Message type
Solution Component
IDOC/PROXY
AN PROXY DocumentStatusUpdateRequest Document Status Update CO_ARBCIG_DOCUMENT_STATUS_UPDT ARBCI1
SRC IDOC ARBCIG_REQOTE Quote Request REQOTE ARBCI1
SRC PROXY QuoteMsgConfirmation Ariba Sourcing Status Updates CO_ARBCIG_QUOTE_MSG_CONFIRMATN ARBCI1
SRC PROXY PurchasingContractERPConfirmation Ariba Contract Response CO_PUR_PURGCONTRMNTCO ARBCI2
4.3.3 Add-on Configuration of Inbound Transactions (Ariba to ECC)
Transaction ERP
Message
Ariba Solution Service: Document Type Code Ariba Transaction Name Consumer Proxy Name Software
type
IDOC/PROXY Component
SRC PROXY PurchasingContractERPCreateRequest Ariba Sourcing Contracts QUOTEMSGPURCHASINGCONTRACT_ASY ARBCI2
SRC PROXY quotemessageorder Ariba Sourcing Purchase Order QUOTEMSGPURCHASEORDER_ASYNC_IN ARBCI1
SRC PROXY PurchasingContractERPRequest_V1 Ariba Sourcing Service Items QUOTEMESSAGEPURCHASINGCONTRACT ARBCI1
4.3.4 CIG Addon Configurations

11
Document Location
CIG installation guide CIG Installation - TEAMS
CIG installation guide for Ferromex (ES) CIG Installation - TEAMS
SAP Ariba Cloud Integration Gateway SAP Ariba Cloud Integration Gateway installation guide - SAP
installation guide Help Portal
CIG Configuration ECC for Ferromex MS Teams - Cutover
4.3.5 CIG Addon Customizations
Document Location
N/A N/A
3.4. CIG Security
How is the password protected in CIG uses SAP Identity Provider and therefore it takes care of all the
CIG? How many failed logins, security associated to the passwords. Identity Authentication does
type of password protection? not store plain text passwords in the database, but only their iterated
random-salted secure hash values. The random salt is at least 512
bits, and it is different for each password. Only generic hash
functions are used with minimum 512 bits key length. No default
passwords are delivered, used, or accepted anywhere.
How secure is CIG? What are its CIG as all Ariba applications goes through a detail yearly Penetration
chances of being hacked? What test which tests for all the vulnerabilities within our applications,
all supplier data would be allowing us to fix or path any security whole that can be found in our
accessible if CIG security is applications. All our transactional data is only kept for 90 days in CIG
penetrated? and all of that is stored in an encrypted database with AES 256 bit.
Where are CIG servers located CIG servers are in Europe EU1 and US Datacenter and all the
and what kind of security is security is managed by SAP. SAP published all the details of the
maintained at those location security management about their DC in the following URL
where CIG is hosted - L1, L2, L3 https://www.sap.com/about/trust-center/data-center.html
etc.?
3.5. Cloud Connector
Document Location
Cloud Connector - SAP HELP Cloud Connector - SAP Help Portal
Installation of Cloud Connector https://tools.eu1.hana.ondemand.com/#cloud
Cloud connector installation guide Installation - SAP Help Portal
12
4. MISCELLANEOUS
4.1. SSO
Ferromex does not have SSO enable
13
www.sap.com/contactsap
© 2018 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.
The information contained herein may be changed without prior notice. 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 or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services 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 developmen ts, 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 no t 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, and they should not be relied upon in making purchasing decisions.
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. All other
product and service names mentioned are the trademarks of their respective companies. See www.sap.com/copyright for additional trademark information and notices.
14

SAP Ariba Services Technical Realization Document - Ferromex

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SAP Ariba Services Technical Realization Document - Ferromex

Uploaded by

Copyright:

Available Formats

INTERNAL

Project Technical Realization Document

Customer Name: Ferromex

Customer Project: Sourcing-CIG Migration

Ferromex Grupo Mexico

SAP Ariba Project Manager Customer Project Manager

Jorge Herrera ___________

Author Document Location (repository/path/name)

Carlos Perdomo ___________

0.1 Draft 14-12-2021 Internal

1.2. Customer Landscape

ERP ECC 6.0 EHP 8.0 SP20(QAS) SP11(PRD)

Adapter CIG Addon

Ariba Buyer Network

Realm ID Parent/Child/Upstream URL

Ariba Realm ferromex-T Upstream http://ferromex-T.sourcing.ariba.com/

ferromex Upstream http://ferromex.sourcing.ariba.com/

1.3. Architecture Diagram

1.4. Ariba Solutions

Following are the list of interfaces included in current scope.

1 RFQ ERP Ariba Sourcing cXML CIG

1.6. Technical Assumptions

1.7. Out of Scope Items

• SAP Functional configuration details in Materials Management module

1.8. Relationship to other documentation

Document Description Location

Architecture Review Customer Landscape Architecture Review - TEAMS

Middleware Strategy SAP recommendation for Middlware Middleware Strategy - TEAMS

2. Ariba Technical Details

2.1.1. Request for Quotation

• SAP RFQ and Award integration with SAP Ariba Sourcing

Request for quotations and contracts

Request for quotations with service items

• One or more service specifications

3.1. CIG Portal

Following Screen Shot display document types in CIG portal

Ariba Sourcing QuoteMessageOrder(cXML) LeadTime QuoteMessageOrder(Addon) PLAN_DEL

Ariba Sourcing REQOTE QuoteRequest ExternalNote

3.3. CIG Addon

4.3.1 Add-on Configuration of Master Data Integration

4.3.2 Add-on Configuration of Outbound Transactions (ECC to Ariba)

AN PROXY DocumentStatusUpdateRequest Document Status Update CO_ARBCIG_DOCUMENT_STATUS_UPDT ARBCI1

SRC IDOC ARBCIG_REQOTE Quote Request REQOTE ARBCI1

SRC PROXY QuoteMsgConfirmation Ariba Sourcing Status Updates CO_ARBCIG_QUOTE_MSG_CONFIRMATN ARBCI1

SRC PROXY PurchasingContractERPConfirmation Ariba Contract Response CO_PUR_PURGCONTRMNTCO ARBCI2

4.3.3 Add-on Configuration of Inbound Transactions (Ariba to ECC)

SRC PROXY PurchasingContractERPCreateRequest Ariba Sourcing Contracts QUOTEMSGPURCHASINGCONTRACT_ASY ARBCI2

SRC PROXY quotemessageorder Ariba Sourcing Purchase Order QUOTEMSGPURCHASEORDER_ASYNC_IN ARBCI1

SRC PROXY PurchasingContractERPRequest_V1 Ariba Sourcing Service Items QUOTEMESSAGEPURCHASINGCONTRACT ARBCI1

4.3.4 CIG Addon Configurations

CIG installation guide CIG Installation - TEAMS

CIG installation guide for Ferromex (ES) CIG Installation - TEAMS

CIG Configuration ECC for Ferromex MS Teams - Cutover

4.3.5 CIG Addon Customizations

3.4. CIG Security

3.5. Cloud Connector

Cloud Connector - SAP HELP Cloud Connector - SAP Help Portal

Installation of Cloud Connector https://tools.eu1.hana.ondemand.com/#cloud

Cloud connector installation guide Installation - SAP Help Portal

Ferromex does not have SSO enable

You might also like