To start with CIG, download and install CIG AddOn in SAP ERP or SAP S/4 HANA and enable CIG settings on Ariba Apps. Also, download and install Cloud Connector within customer firewall. Cloud connector will be used for inbound communication from CIG to S4 HANA/ ERP.
Settings at S4 HANA/ SAP ERP:
- Maintain certificates in Trust Manager (t-code - STRUST) - Import root certificate of CIG in SSL Client SSL Client (Anonymous)
- RFC destination to connect to CIG from S4 HANA/ ERP (t-code - SM59) - Connection type will be 'G' type (HTTPS connection to External system). Target host - testacig.ariba.com ( for test system) and acid.ariba.com ( for production system). Path prefix - /cxf/receiveIDOC ( for Ariba Network & Ariba Sourcing Integration) , /cxf/receiveERPIDOC ( for Ariba Retail Integration).
- Create a port (t-code - WE21) - type XML HTTP, content type - Text/XML, SOAP Protocol
- Create logical system for ARIBA CIG using t-code BD54
- Send SAP Information to SAP Ariba ClG (t-code - SPRO) - the information such as SAP version, System ID, System Time Zone, System Client, and ERP Software Component, Domain, Port etc. This task is a one-time activity.
Settings at Ariba Network:
Create users and assign necessary permissions to access and configure CIG and enable CIG.
Permission:
- Ariba Cloud Integration Gateway Configuration - allows you to create, modify and maintain projects in CIG
- Ariba Cloud Integration Gateway Access - allows you to view and search projects in CIG.
Configuration in CIG:
While accessing CIG very first time, if you have not synced SAP data with CIG, you need to provide required information of your SAP System. It is recommended to send your backend SAP system information before accessing and configuring your CIG account very first time.
Steps for creating Ariba Cloud Integration Project:
Section 1: Basic Information
Project Name: Any meaningful name
Product: Ariba Network/ Ariba Procurement/ Ariba Sourcing
Section 2: Connection
Add New Connection or select from Reusable Connections table
For creating new connection, provide the below details:
- Transport Type: Addon (white integration via Cloud Connector)/ HTTPS (while using middleware)
- Environment: TEST or PRODCUTION or TEST/PRODUCTION
- Name: Any meaningful name
- System ID: Choose your SAP system's logical System ID
Connect to Backend
- Document Type: ANY/ Specific document type
- Domain name: Virtual host name of your sap system maintained in CC
- Port: Virtual port number of your sap system maintained in CC
- Client ID: Your SAP system's client ID
- Location ID: Location ID of CC
- Authentication: Basic/Certificate
Connect Trading Partner to CIG
Authentication type : Basic/ Certificate
Section 3: Mappings
In the CIG Buy Side Integration, standard mappings are developed in XSLT and stored in Database. You don't need to perform any activities in this step.
Section 4: Cross Reference
- Parameter - Select document type and define related values for both test and production environments
- UOM Template - it is required for Ariba Network and Ariba Sourcing. Download UOM.csv file. Define the corresponding SAP ERP value for each Ariba Network specific UOM. For e.g. Ariba UOM - EA, Customer UOM - EACH. Select the System ID for which you would like to upload UOM maps and upload.
- Lookup Table - Select Document type, expand template node and enter customer value and Ariba value for Lookup Table for test and production environments.
- Realm ID - select the Realm you like the project to connect to. This is important when you have multi- ERP environment and creating different projects for each back end system
Section 5: Test
Run test for executing the test scenarios using TestCentral
Click on the Go-Live button
Custom Mapping in CIG
CIG -> My configuration -> Mappings -> Select the transaction for which you want to do the customisation -> Select system ID
Custom Routing
It is used to route transaction documents to the specific ERP client system based on the system ID of the ERP system and certain conditions.
No comments:
Post a Comment