Text Material Preview
© SAP SE AR822 1 AR822 SAP Ariba Integration: Cloud Integration Gateway Collection 2008 © SAP SE AR822 2 HOME Course Title LOGO HERE @ Copyright. All rights reserved. Outline SAP Ariba Cloud Integration Gateway: Overview and Getting Started Master Data Integration Network Integration Transactional Data Integration Migration, Multiple ANIDs, and More © SAP SE AR822 3 HOME Course Title LOGO HERE @ Copyright. All rights reserved. SAP Ariba Cloud Integration Gateway: Overview and Getting Started Getting Started with CIG 1 Cloud Connector Integration Add-Ons Configure SAP Ariba Add-On 4 3 2 CIG Configuration 5 Content Based Routing Custom Mapping Tool 7 6 © SAP SE AR822 4 4© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ Getting Started with CIG © SAP SE AR822 5 HOME Course Title @ Copyright. All rights reserved. About This Lesson @ Copyright. All rights reserved. Lesson 1: Quick Overview & Features By the end of this lesson, you will be able to: • Match SAP Ariba Cloud Integration Gateway features to their associated benefit(s) This lesson includes the following topics: i. Quick CIG video ii. 10 Key Features © SAP SE AR822 6 HOME Course Title @ Copyright. All rights reserved. CIG 10 Key Features The following pages display details of each of the icons below. A self-service setup wizard Helpful Deployment Guides & Standard Mapping Repository Work-Saving Developer Tools & Test Central One-Click Deployment & Connect-Once Functionality / Single Sign-On Support different communication protocols © SAP SE AR822 7 HOME Course Title @ Copyright. All rights reserved. CIG 10 Key Features 1. A self-service setup wizard ü The end user answers a series of basic technical questions & CIG uses these answers to derive all the necessary transaction configurations ü The wizard assists the end user through each step of the process and automates the historically complex task of integration © SAP SE AR822 8 HOME Course Title @ Copyright. All rights reserved. CIG 10 Key Features 2. Helpful Deployment Guides ü Comprehensive documentation addresses deployment details every step of the way 3. Standard Mapping Repository ü Maintained by SAP Ariba ü Supports multiple data standards used across a wide array of industry verticals, making it easy to align customers’ data and formatting requirements © SAP SE AR822 9 HOME Course Title @ Copyright. All rights reserved. CIG 10 Key Features 4. Work-Saving Developer Tools ü Test connection ü Document Validator transforms the data & validates the schema to ensure accuracy and acceptability 5. Test Central ü Self-test framework ü Lowers overall testing & setup time ü Allows you to go live with integrated transactions on Ariba Network far faster than before ü Test reports © SAP SE AR822 10 HOME Course Title @ Copyright. All rights reserved. CIG 10 Key Features 6. One-Click Deployment ü Enables you to launch integration projects moments after verification is complete 7. Connect-Once Functionality ü Lets you leverage your initial integration setup across all your accounts, which means you can reuse project configurations and modify them with ease 8. Single Sign-On ü Access CIG from AN or Ariba Apps ü Permission-based Control © SAP SE AR822 11 HOME Course Title @ Copyright. All rights reserved. CIG 10 Key Features 9. Transaction tracker with search capability ü Monitoring - Makes it easy to monitor & manage your Ariba Network transactions & attachments ü Search filters - Search filters include start & end date, buyer, & inbound or outbound direction. You can get Source & Target payloads; Attachments if any & Processing logs ü Reprocess failed transactions to ensure successful delivery 10. Transaction Tracker & Support different communication protocol ü Support for AS2, HTTPS, VAN, & RNIF communications protocols ü Ensures security across all your Ariba Apps transactions ü Support Basic or Certificate-based Authentication - Gives you the flexibility to manage your connections through certificate-based or basic authentication © SAP SE AR822 12 HOME Course Title @ Copyright. All rights reserved. About This Lesson @ Copyright. All rights reserved. Lesson 2: Supplier Integration By the end of this lesson, you will be able to: • Identify supplier integration prerequisites • Describe how the Integration Wizards improve end user experience This lesson includes the following topics: i. Supplier integration prerequisites ii. Integration wizard © SAP SE AR822 13 HOME Course Title @ Copyright. All rights reserved. Supplier Integration: Prerequisites Pre-requisites for getting started: • An active Supplier Account on Ariba Network that is configured to send & receive transaction documents from Cloud Integration Gateway • A valid trading Buyer-Supplier relationship on Ariba Network © SAP SE AR822 14 HOME Course Title @ Copyright. All rights reserved. Supplier Integration: Wizard The Integration Wizard automates complex integration tasks by asking a series of easy-to-answer questions. The answers provided by the supplier help Cloud Integration Gateway derive transaction configurations. What’s more, the supplier can reuse all these configurations for future integrations with other customers. • Once the supplier enables CIG within their Ariba Network account, they will then simply access the CIG Navigator and create a project through wizard. • With a project, a supplier sets an endpoint for the connection with the Ariba Network, configures, and tests – this can be done with one or more customers in a single project. This intuitive Integration Configuration Wizard quickly guides the supplier through these steps: 1. Create Project 2. Add Customer(s) 3. Define connectivity 4. Configure data format- Set up your mapping using data maps 5. Define cross-reference data - enter data as cross reference between you & your partner 6. Self-test (using Test Central)- Create a test script & schedule the testing 7. Deploy to Production (“go live”) Create Project Add Customer(s) Configure Data format Define Connectivity Deploy to Production Define Cross Reference data Self-test using Test Central © SAP SE AR822 15 HOME Course Title @ Copyright. All rights reserved. About This Lesson @ Copyright. All rights reserved. Lesson 3: Buyer Integration By the end of this lesson, you will be able to: • Differentiate between previous and current CIG architecture • Recognize supported systems and solutions • List the steps to integrate SAP backend with Ariba Network or Ariba Apps using CIG This lesson includes the following topics: i. Previous vs. Current Architecture ii. Supported solutions and Support Policy iii. Steps to integrate SAP backend with Ariba Network or Ariba Apps using CIG © SAP SE AR822 16 HOME Course Title @ Copyright. All rights reserved. Buyer Integration: Previous and Current Architecture Previous Architecture Current Architecture Transports deployed on the SAP system to enhance interfaces and do some transformation. Add-on to be deployed on SAP, which will be lightweight and only enhance interfaces . Mappings and custom mapping done in PI/PO. Mappings and custom mapping in SAP Ariba Cloud Integration Gateway. Customer need to upgrade both transports and PI. Upgrades to SAP Ariba Cloud Integration Gateway will be done by SAP, customer needs to upgrade add-on . Lookup from SAP PI/PO back to system to fetch additional data from SAP. No lookup from CIG back to backend system Interfaces are enhanced to fetch all the data from SAP. All IDocs are extended. Lot of configuration in PI and some configuration in Transports. Most of the configuration will be done in CIG in one central place using wizard. SAP PI used for central monitoring. CIG is used for central monitoring. Test framework to deployed separately. Test framework available in CIG. © SAP SE AR822 17 HOME Course Title @ Copyright. All rights reserved.status updates to and from Ariba Network ü Enriched outbound messages so that no callback for additional data lookup is needed ü Shipment through SAP Service Marketplace ü Support for Attachments and Comments Ø All interfaces have a baseline support for attachments and comments Ø Using SAP GOS on header and DMS on item level where SAP Object supports that. Ø BAdIs for custom logic. ü CIG add-on Bug Fixes delivered via SAP Notes and preliminary correction instructions © SAP SE AR822 101 LOGO HERE @ Copyright. All rights reserved. About This Lesson @ Copyright. All rights reserved. Lesson 2: Transition Paths By the end of this lesson, you will be able to: • Differentiate between transition paths. This lesson includes the following topics: i. Transition path from CI solutions to CIG ii. Transition path from SAP Business Suite AddOn solutions to CIG. © SAP SE AR822 102 LOGO HERE @ Copyright. All rights reserved. SAP Ariba Cloud Integration Gateway Transition Paths – Transition from CI solutions to CIG SAP PICI -9 Tr an sp or ts cXML messages (https; Multipart Mime) With SAP Cloud Platform Integration Buyer Supplier IDOCs /Web Services (SOAP) CI-9 CIG Buyer SupplierIDOCs /RFCs/Web Services (SOAP) SAP © SAP SE AR822 103 LOGO HERE @ Copyright. All rights reserved. SAP Ariba Cloud Integration Gateway Transition Paths –Transition from Business-Suite Add-On to CIG SAP cXML (SOAP) With SAP Cloud Platform Integration Buyer Supplier SAP IDOCs /Web Services (SOAP) Business Suite Add-On / Native CIG Buyer Supplier © SAP SE AR822 104 LOGO HERE @ Copyright. All rights reserved. Transition Paths: Configuration Installation Download Add- On and Cloud Connector Install Add-On and Cloud Connector Enable CIG Enable CIG on AN Receive User ID and password Technical Configuration Set up basic connection Certificate HTTP and IDOC endpoints Send SAP Connectivity data Credential, Host Name, Port -----------à Receive SAP connectivity data Create Connection Scenario Configuration Automatic setup for IDOC/Web Service Maintain application specific settings Create Cross References Enhancements Create Extensions Implement BAdIs Add Custom XSLT Test and Go Live Deploy to Production Test via Test Central Push to Production SAP Cloud Integration Gateway (CIG) As we move forward in this unit, we will be focused on the Add-On Installation In this unit, we will focus on high-level configuration activities involved while deploying CIG integration solutions with Direct Connectivity option using SAP Cloud Connector. © SAP SE AR822 105 LOGO HERE @ Copyright. All rights reserved. Transition Paths: 3-Step Process • Automated End-to-End Testing via pre-defined scripts in Test Central • Buyers can also add their own test cases, including customizations Testing • In SAP: Extension Framework in Add-On Interfaces • In CIG: Custom Mapping Tool can be used for additional data mapping. Extensions • Enable CIG buy-side account • Install and configure Add- On • Push Configurations automatically to CIG Configurations © SAP SE AR822 106 LOGO HERE @ Copyright. All rights reserved. About This Lesson @ Copyright. All rights reserved. Lesson 3: Download Add-on Software Components By the end of this lesson, you will be able to: • Download Add-On Software Components This session includes the following topic: • How to access SAP Service Marketplace • How to download AddOn © SAP SE AR822 107 LOGO HERE @ Copyright. All rights reserved. SAP Ariba Cloud Integration Gateway add-on for SAP ERP (Download) You can download SAP ERP and SAP S/4HANA software components and their support packages from the SAP Software Download Center on the SAP Service Marketplace at – https://support.sap.com/swdc or https://launchpad.support.sap.com/ General instructions for the installation of add-ons can be found in SAP Note 1841471 (Release strategy for ABAP add-ons for interface components). This SAP Note provides information about planning the installation of the ABAP add-on for interface components on application back-end systems. © SAP SE AR822 108 LOGO HERE @ Copyright. All rights reserved. Download Add-on Software Components Step 1 of 6 • Login to https://support.sap.com or https://launchpad.support.sa p.com • Click Download Software © SAP SE AR822 109 LOGO HERE @ Copyright. All rights reserved. Download Add-on Software Components Step 2 of 6 • Click INSTALLATION & UPGRADES • Select By Alphabetical Index (A-Z). • Click A © SAP SE AR822 110 LOGO HERE @ Copyright. All rights reserved. Download Add-on Software Components Step 3 of 6 • Search for ARIBA CLOUD INT SAP ERP or ARIBA CLOUD INT S/4 HANA © SAP SE AR822 111 LOGO HERE @ Copyright. All rights reserved. Download Add-on Software Components Step 4 of 6 • Under DOWNLOADS, select [package] © SAP SE AR822 112 LOGO HERE @ Copyright. All rights reserved. Download Add-on Software Components Step 5 of 6 • Click INSTALLATION © SAP SE AR822 113 LOGO HERE @ Copyright. All rights reserved. Download Add-on Software Components Step 6 of 6 • Check the box(es) of the AddOn component(s) you want to install. Note: • Click on 51052888 (Ariba Cloud Integr. Gateway add-on SAP ERP for EHP0-EHP8) to download ARBCI1-100 software component. • Click on 51052874 (Ariba Cloud Integr. Gateway add-on SAP ERP for EHP4-EHP8) to download ARBCI2-100 software component. • Click on 51053120 (Ariba Cloud Integr. Gateway add-on SAP ERP for Retail) to download ARBCGR-100 software component. • Add them to your Download Basket and complete Download. © SAP SE AR822 114 LOGO HERE @ Copyright. All rights reserved. About This Lesson @ Copyright. All rights reserved. Lesson 4: Download Add-on Support Packages By the end of this lesson, you will be able to: • Download Add-on Support Packages This lesson includes the following topics: i. Download add-on support packages without the use of SAP PI / PO middleware ii. Download add-on support packages with the use of SAP PI / PO middleware © SAP SE AR822 115 LOGO HERE @ Copyright. All rights reserved. Download Add-on Support Packages: 2 Scenarios Scenario 1: walks us through the simple steps to download add-on support packages – without the use of SAP PI / PO middleware. Scenario 2: walks us through the simple steps to download add-on support packages – with the use of SAP PI / PO middleware. © SAP SE AR822 116 LOGO HERE @ Copyright. All rights reserved. Download Add-on Support Packages – without using SAP PI / PO middleware Step 1 of 9 • Login to https://support.sap.com • Click Download Software There are standard SAP Notes for general instructions (applicable to all types on AddOn & not just Ariba AddOn) available in https://support.sap.com ØGeneral instructions to install AddOn – 1841471 ØGeneral instructions to uninstall AddOn – 2011192 © SAP SE AR822 117 LOGO HERE @ Copyright. All rights reserved. Download Add-on Support Packages – without using SAP PI / PO middleware Step 1 of 7 • Click SUPPORT PACKAGES & PATCHES • Select By Alphabetical Index (A-Z) • Click A © SAP SE AR822 118 LOGO HERE @ Copyright. All rights reserved. Download Add-on Support Packages – without using SAP PI / PO middleware Step 2 of 7 • Search for ARIBA CLOUD INT SAP ERP or ARIBA CLOUD INT S/4 HANA © SAP SE AR822 119 LOGO HERE @ Copyright. All rights reserved. Download Add-on Support Packages – without using SAP PI / PO middleware Step 3 of 7 • Under DOWNLOADS, select [package] © SAP SE AR822 120 LOGO HERE @ Copyright. All rights reserved. Download Add-on Support Packages – without using SAP PI / PO middleware Step 4 of 7 • Select COMPRISED SOFTWARE COMPONENT VERSIONS © SAP SE AR822 121 LOGO HERE @ Copyright. All rights reserved. Download Add-on Support Packages – without using SAP PI / PO middleware Step 5 of 7 • Select the component for SAP Ariba AddOn • ARBCI1 100 – mandatory for all customers irrespective ofthe EHP level their on • ARBCI2 100 – contract services feature – integrate contracts from SAP Ariba Sourcing to SAP – only required if the buyer contracts have a services item (requires EHP 4 or higher in SAP ERP) • ARBCIGR 100 – only required if customer wants to integrate Article Master Data to SAP Ariba Sourcing. • Select the Pass-through component for the coinciding SAP PI/PO © SAP SE AR822 122 LOGO HERE @ Copyright. All rights reserved. Download Add-on Support Packages – without using SAP PI / PO middleware Step 6 of 7 • Click SUPPORT PACKAGES © SAP SE AR822 123 LOGO HERE @ Copyright. All rights reserved. Download Add-on Support Packages – without using SAP PI / PO middleware Step 7 of 7 • Select the support package that you want to install & add them to your download basket. • Repeat this step for each component version. © SAP SE AR822 124 LOGO HERE @ Copyright. All rights reserved. Download Add-on Support Packages – with SAP PI / PO middleware Step 1 of 5 • Login to https://support.sap.com • Click Download Software In addition to the AddOn software components, you also need to download pass-through software components for SAP PI / PO middleware. © SAP SE AR822 125 LOGO HERE @ Copyright. All rights reserved. Download Add-on Support Packages – with SAP PI / PO middleware Step 2 of 5 • Click SUPPORT PACKAGES & PATCHES • Select By Category © SAP SE AR822 126 LOGO HERE @ Copyright. All rights reserved. Download Add-on Support Packages – with SAP PI / PO middleware Step 3 of 5 • Select SAP Content © SAP SE AR822 127 LOGO HERE @ Copyright. All rights reserved. Download Add-on Support Packages – with SAP PI / PO middleware Step 4 of 5 • Select ESR CONTENT (XI CONTENT) © SAP SE AR822 128 LOGO HERE @ Copyright. All rights reserved. Download Add-on Support Packages – with SAP PI / PO middleware Step 5 of 5 • Select the package you want to install • Add them to your Download Basket and complete Download © SAP SE AR822 129 LOGO HERE @ Copyright. All rights reserved. About This Lesson @ Copyright. All rights reserved. Lesson 5: Copying content from SAP Client 000 By the end of this lesson, you will be able to: • Copy content from SAP Client 000 © SAP SE AR822 130 LOGO HERE @ Copyright. All rights reserved. Copying content from SAP Client 000 Client 000 is the golden client of the SAP system. • As per SAP’s standard practice, all the customized objects are delivered to the client 000 only. • This is where the SAP customer needs to copy the required content to their other clients as needed. • Tip: this must be copied to the production client before the master data import. 10 Steps: 1. Using TCode SPRO navigate to Integration with Other SAP Components>SAP Ariba Cloud Integration Gateway>Master Data Integration>Enhancements>Maintain Field Map for Master Data and Catalog Upload Request 2. Click IMG-Activity for Maintain Field Map for Master Data and Catalog Upload Request. (The Change View "Table to maintain mapping of SAP to Buyer fields" Overview screen appears.) 3. From the menu, navigate to Utilities>Adjustment 4. Enter the R/3 connection which points to the client 000, Click Yes 5. Click Yes on the resulting screen. The Overview: Adjustment screen appears. Choose the [entries which you want to adjust] 6. Click Adjust The Detail View 7. Click All 8. Click Back twice to return to Change View "Table to maintain mapping of SAP to Buyer fields": Overview • The data has been changed by adjustment 8. Click Yes to confirm Change Data? 9. Click Save 10. Enter the transport number (if prompted) © SAP SE AR822 131 LOGO HERE @ Copyright. All rights reserved. Cloud Connector © SAP SE AR822 132 LOGO HERE @ Copyright. All rights reserved. About This Lesson @ Copyright. All rights reserved. Lesson 1: SAP Cloud Platform Cloud Connector (CC) Defined By the end of this lesson, you will be able to: • Describe what the SAP Cloud Platform Connector (CC) does. This lesson includes the following topics: i. Description of CC ii. Quick Tips iii. Flow overview © SAP SE AR822 133 LOGO HERE @ Copyright. All rights reserved. SAP Cloud Platform Cloud Connector (CC) Defined A brief overview of SAP Cloud Platform Cloud Connector (CC): • The CC serves as the link between SAP Cloud Platform and existing on premise systems. • It combines an easy setup with a clear configuration of the systems that are exposed to SAP Cloud Platform. • The cloud connector runs as on premise agent in a secured network and acts as a reverse invoke proxy between the on premise network and SAP Cloud Platform. • Due to its reverse invoke support, you don't need to configure the on premise firewall to allow external access from the cloud to internal systems. • A single CC supports connectivity with multiple backend SAP systems. © SAP SE AR822 134 LOGO HERE @ Copyright. All rights reserved. SAP Cloud Platform Cloud Connector (CC) Defined Installation Quick Tips Cloud Connector needs to be installed as the integration agent in the On-Premise network and can then be used to establish a persistent SSL tunnel to SCP accounts. Prerequisites for successful installation of the Cloud Connector can be located in the SAP Help Portal’s SAP Cloud Platform Connectivity guide Ø To establish this tunnel, the Cloud Connector Administrator has to authenticate himself against the related SCP account of which he must be member. Ø In Cloud Connector add, the SCP (SAP Cloud Platform) Account to establish SSL Tunnel between the SCP (SAP Cloud Platform) account and Cloud Connector. Ø If you install the Cloud Connector in a network segment that is isolated from the backend systems, you need to make sure that the exposed hosts and ports are still reachable and open them in the firewall protecting them © SAP SE AR822 135 LOGO HERE @ Copyright. All rights reserved. SAP Cloud Platform Cloud Connector (CC) Defined SAP Ariba Network CIG on SAP Cloud Platform Customer Network CPI (Cloud Platform Integration) Messaging Mapping Transformation CIG Portal UI Configuration Wizard Mapping Repository Test Central Monitoring SSL Tunnel SAP Ariba source-to-settle solutions buyer supplier SAP ERP CIG Add-On for ERP CIG Add-On for S/4HANA SAP Cloud Connector SOAP / IDOC https • The Cloud Connector (CC) here acts as a security agent of your backend SAP ERP or SAP S/4HANA on-premise system. • It masks the identity of your backend system so that it’s not exposed to external cloud applications, in our case the cloud application is CIG. • Using a unique combination of four field values, it establishes a secure tunnel between the CPI application (in our case that is CIG) & a specific installation of Cloud Connector. This combination is unique per Cloud Connector installation. • CC is usually installed in a DMZ & is exposed to internet. In CIG Integration scenario, we are using Cloud Connector only for inbound communication to the backend SAP ERP system. Documents inbound to backend SAP ERP system are sent using SOAP protocol (SOAP or IDOC over SOAP). © SAP SE AR822 136 LOGO HERE @ Copyright. All rights reserved. About This Lesson @ Copyright. All rights reserved. Lesson 2: Hardware Requirements and Product Availability By the end of this lesson, you will be able to: • Identify hardware requirements • Recognize product availability • Locate source-of-truth documentation This lesson includes the following topics: i. Hardware requirements ii. Product availability © SAP SE AR822 137 LOGO HERE @ Copyright. All rights reserved. Hardware Requirements and Product Availability Hardware Requirements: üMemory: 2 GB RAM (min), recommended 4 GB üHard Disk Space: 3 GB (min), recommended 20 GB üCPU: Single core 3 GHz (min), recommended dual core 2 GHz ü 64-bit Operating Systems: Ø Windows 7, Windows 8.1, Windows 10, Windows Server 2008 R2, Windows Server 2012, or Windows Server 2016 R2; Ø Linux Enterprise Server 11, Linux Enterprise Server 12; Ø MacOS X 10.7 (Lion), Mac OS X 10.8 (Mountain Lion); Mac OS X 10.9 (Mavericks), Mac OS X 10.10 (Yosemite); Mac OS X 10.11 (El Capitan) üSupported JDKs version : 7 or 8 Requirements change overtime, view the latest here: https://help.sap.com/viewer/cca91383641e40ffbe03bdc78f00f681/Cloud/en- US/e23f776e4d594fdbaeeb1196d47bbcc0.html © SAP SE AR822 138 LOGO HERE @ Copyright. All rights reserved. Hardware Requirements and Product Availability Operating System Version Cloud Connector Version Windows 7, Windows Server 2008 R2 2.x SUSE Linux Enterprise Server 11, Redhat Enterprise Linux 6 2.x Mac OS X 10.7 (Lion), Mac OS X 10.8 (Mountain Lion) 2.x Windows 8.1, Windows Server 2012, Windows Server 2012 R2 2.5.1 and higher SUSE Linux Enterprise Server 12, Redhat Enterprise Linux 7 2.5.1 and higher Mac OS X 10.9 (Mavericks), Mac OS X 10.10 (Yosemite) 2.5.1 and higher Windows 10 2.7.2 and higher Mac OS X 10.11 (El Capitan) 2.8.1 and higher Windows Server 2016 2.9.1 and higher Windows Server 2019 2.11.3 and higher Product Availability: Product availability changes overtime, view the latest here: https://help.sap.com/viewer/cca91383641e40ffbe03bdc78f00f681/Cloud/en- US/e23f776e4d594fdbaeeb1196d47bbcc0.html © SAP SE AR822 139 LOGO HERE @ Copyright. All rights reserved. About This Lesson @ Copyright. All rights reserved. Lesson 3: Download and configure the Cloud Connector By the end of this lesson, you will be able to: • Download and configure the Cloud Connector © SAP SE AR822 140 LOGO HERE @ Copyright. All rights reserved. Download and Configuration Steps 1-3 of 13 Steps to download & configure Cloud Connector: 1. Access https://tools.hana.ondemand.com from a web browser. Click CLOUD 2. Scroll down to the Available Cloud Connectors section; based on operating system you are using click on the link provided in the Download column. 3. Save the file. • Additionally, you can control the resources available for the cloud applications in those systems. • Thus, you can benefit from your existing assets without exposing the whole internal landscape. • If you install the Cloud Connector in a network segment that is isolated from the backend systems, you need to make sure that the exposed hosts and ports are still reachable and open them in the firewall protecting them. © SAP SE AR822 141 LOGO HERE @ Copyright. All rights reserved. Download and Configuration Steps 4-5 of 13 4. Once the file is saved, start installation & provide the necessary information in the wizard such as – Ø Installation folder location Ø Port Ø Your JDK path 5. Once the installation is complete, you will be able to find it in Installed Apps. © SAP SE AR822 142 LOGO HERE @ Copyright. All rights reserved. Download and Configuration Steps 6-7 of 13 6. In a web browser, enter: https://: Ø refers to the machine on which the CC has been installed. If you install it on your machine, you can enter localhost. Ø is the CC port provided during installation. Default port is 8443. 7. On the login screen, enter User Name & Password as Administrator / manage (small case). © SAP SE AR822 143 LOGO HERE @ Copyright. All rights reserved. Download and Configuration Step 8 of 13 8. When you log in first time, you must change the password before you continue forward. Shadow (Backup Installation) • This is a generic feature of Cloud Connector; not a requirement of CIG • If something goes wrong with the Master installation, the Shadow will act as back-up and ensure that docs continue to flow to your SAP system – may be installed physically or virtually • This blog provides guidance for Master, and Shadow Installation: is available in this blog: https://blogs.sap.com/2016/06/30/setting-up-high-availability-for-hana-cloud- connector/ © SAP SE AR822 144 LOGO HERE @ Copyright. All rights reserved. Download and Configuration Steps 9-10 of 14 P User needs to have CC role to be able to connect. 9. Provide required information to create Account A. Landscape Host – eu1.hana.ondemand.com B. Account Name – aff5426a3 (for Test Account) or a8f3ed22c (for PROD Account). C. Display Name – Any of your choice D. Account User – P User ID that you have received in email when CIG was enabled on Ariba Network. E. Password – P User password you have set. F. Location ID – Any unique ID identifying the location of this Cloud Connector for a specific account. • This Location ID needs to be unique across all customers. Recommendation for Location ID is to use human readable name identifying the Cloud Connector installation location inside you organization prefixed with company name (to make the Location ID unique across customers) e.g. MYCMP_GB_TEST G. Host – A suitable proxy host from your network and the port that is specified for this proxy. You need to specify a proxy server that supports SSL communication. H. Port – Port of the proxy. 10. Click Save © SAP SE AR822 145 LOGO HERE @ Copyright. All rights reserved. Download and Configuration Step 11 of 14 11. Once your subaccount is created, click Cloud To On-Premise, then click + to add information about your backend system. © SAP SE AR822 146 LOGO HERE @ Copyright. All rights reserved. Download and Configuration Step 12 of 14 In general, Cloud Connector supports different types of on-premise back ends such as S/4 HANA; SAP PI; any other SAP system or even Non-SAP system. However, in case of integration via CIG, we need to select ABAP System for SAP ERP or SAP HANA for SAP S/4 HANA on-premise system. In case of integration via CIG, we need to select Principle Type as NONE. Using CIG, the Certificate Based Authentication is not supported via Cloud Connector. 12. Provide information about your backend system: A. Back-end Type – ABAP System (for example). B. Protocol - HTTPS C. Internal Host – Your backend system host name. D. Internal Port – Port of your backend system host. E. Virtual Host – Any dummy / random value to identify your Internal Host name. F. Virtual Port – Any dummy / random value. G. Principal Type – None. H. Description – For your CC connection to your specific backend system. I. Check the box Check Internal Host to assure the connectivity to your backend system (not pictured) J. Click Finish (not pictured) © SAP SE AR822 147 LOGO HERE @ Copyright. All rights reserved. Download and Configuration Step 13 of 14 13. Once you are done, you can see the backend system information listed. If you have multi ERP setup, click again on + & add the information of another backend system. Details about security status: Risk https://help.sap.com/viewer/cca91383641e40ffbe03bdc78f00f681/Cloud/en-US/e7ea82a4bb571014a4ceb61cb7e3d31f.html © SAP SE AR822 148 LOGO HERE @ Copyright. All rights reserved. Download and Configuration Further defining access control. When connecting to any SAP system – you must provide permission to Cloud Connector in order to access the required services All web services will be accessible if you enter URL Path "/" in Resource Accessible table while defining access. © SAP SE AR822 149 LOGO HERE @ Copyright. All rights reserved. Download and Configuration The URL path for the web services on the on premise ERP system can be found using the TCode SICF. This is an admin activity. Select "Path and all sub-paths" as Access Policy to provide access to all folders under the defined URL Path. Your SAP Cloud Connector is installed; configured & ready to use. Further defining access control. © SAP SE AR822 150 LOGO HERE @ Copyright. All rights reserved. Download and Configuration Further defining access control. In this example the URL is /sap/bc/srt/xip/arba/ © SAP SE AR822 151 LOGO HERE @ Copyright. All rights reserved. Configure SAP Ariba Add-on © SAP SE AR822 152 LOGO HERE @ Copyright. All rights reserved. About This Lesson @ Copyright. All rights reserved. Lesson 1: Overview © SAP SE AR822 153 LOGO HERE @ Copyright. All rights reserved. OverviewThe AddOn for SAP Ariba Cloud Integration Gateway allows you to send or receive documents from SAP Ariba solutions and SAP ERP or SAP S/4HANA (on-premise) systems. This AddOn has multple nodes to enable you to perform required configuration activities in a sequential manner. In this AddOn, you will typically find nodes for Global Settings; General Settings and Application Sepcific Settings. Gobal Settings are the set of configuration acitivities you need to perform irrespective of the integration of any SAP Ariba solutions - Ariba Network Integration or SAP Ariba Strategic Sourcing Solution or SAP Ariba Procurement Integration. General Settings are the set of configuration acitivities you need to perform for a specific integration irrespective of any transactions / documents that you are adpoting. Application Specific Settings are the set of configuration acitivities you need to perform for that specific transaction / document. When you donwload AddOn from SAP Service Marketplace, a file with .SAR extension gets downloaded. SAP's Add-On Installation Tool (transaction code - SAINT) enables users to install and / or upgrade AddOns directly from their standard SAP system. You do not need to access the operating system or restart the system. Prior to installation, numerous import conditions are checked to ensure that only AddOn that fit the available SAP system can be installed. Follow the Instrcution Wizard to complete the process. This activity is carried out by SAP BASIS Admin person / team. © SAP SE AR822 154 LOGO HERE @ Copyright. All rights reserved. About This Lesson @ Copyright. All rights reserved. Lesson 2: Define Authorizations By the end of this lesson, you will be able to: • Discuss the importance of defining authorizations • Define required authorizations using out-of-box authorization objects, and/or classes/programs in the SAP system. This lesson includes the following topic: i. Authorization definition © SAP SE AR822 155 LOGO HERE @ Copyright. All rights reserved. Define Authorizations Once the AddOn software component is downloaded from SAP Service Marketplace & installed on your SAP system, user needs to perform following activities to install SAP Ariba AddOn: • Define authorizations to run supported transactions • Enable integration through middleware (optional if you are using mediated connectivity) • Define Global Settings. • Configure Attachment & Comments • Map Variants & Partitions • Customize Parameter & Pre-filter Values To define required authorizations, you can use out-of-box authorization objects, classes & programs in the SAP system. Create roles (any number) using TCODE SU21 and assign the roles to the user using TCODE SU01. • Authorization objects are part of role that one has to create. The following authorization objects & classes are provided by SAP Ariba: Ø ACIG: Authorization Object class Ø ARBCIG_CLS: Authorization Object for Ariba Class Objects Ø ARBCIG_RFC: Authorization Object for RFC Ø ARBCIG_PRG: Authorization Object for program execution Ø ARBCIG_SPR: Authorization Object for Add On Special Programs © SAP SE AR822 156 LOGO HERE @ Copyright. All rights reserved. Define Authorizations The SAP ERP or SAP S/4 HANA user which you will define in CIG project connection for Transport Type AddOn should have following authorizations: B_ALE_RECV Ø This authorization is required for receiving inbound IDocs through RFC. Ø You must define this authorization object type to receive & process inbound IDocs successfully. Ø It enables you to ensure that a user that was set-up specifically for communication purposes is authorized to process defined types of messages. Ø When IDOCs are received, the first thing that the receiving system does is check that the authorization for receiving messages is present. If this is not the case then the receiving program is immediately terminated. • S_SERVICE Ø This authorization is required for receiving inbound Web Service. Ø You must define this authorization object type to receive & process inbound Web Service successfully. Ø The Web service runtime executes an authority check for every Web service invocation; this is similar to authority checks for starting a transaction or remotely calling an RFC function. © SAP SE AR822 157 LOGO HERE @ Copyright. All rights reserved. Define Authorizations • ARGCIG_CLS & ARBCIG_RFC: These objects do get called internally from a CIG communication user. • ARGCIG_PRG & ARBCIG_SPR: These are required to execute programs / reports such as Interface Setup; SAP Data Sync; etc. These authorization objects need to be assigned to designated users via transaction code – SU21 © SAP SE AR822 158 LOGO HERE @ Copyright. All rights reserved. About This Lesson @ Copyright. All rights reserved. Lesson 3: Enable Integration via Middleware By the end of this lesson, you will be able to: • Enable integration via middleware © SAP SE AR822 159 LOGO HERE @ Copyright. All rights reserved. Enable integration via middleware Users have the option to use a middleware to route transaction documents from an SAP system to CIG. To enable the middleware: 1. Navigate to Global Settings using the transaction code SPRO. 2. Click IMG-Activity for Enable Integration via Middleware – The Parameters – “Enable Integration via Middleware” screen appears. With this CIG AddOn release, only SAP PI / PO & SAP CPI middleware are supported. © SAP SE AR822 160 LOGO HERE @ Copyright. All rights reserved. Enable integration via middleware To enable the middleware (continued): 3. Click on “Modify” button & select one of the following variable names : ü The “ENABLE_MIDDLEWARE” to enable SAP Cloud Platform Integration ü The “ENABLE_PI_MIDDLEWARE” to enable SAP NetWeaver Process Integration 4. Enter “X” for Low value 5. Click Save. © SAP SE AR822 161 LOGO HERE @ Copyright. All rights reserved. About This Lesson @ Copyright. All rights reserved. Lesson 4: Define Global Settings By the end of this lesson, you will be able to: • Understand the series of configuration acitivities involved in Global Settings and their purpose. © SAP SE AR822 162 LOGO HERE @ Copyright. All rights reserved. Define Global Settings To navigate to global settings in SAP ERP and SAP S/4HANA: ü 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 >>> Global Settings © SAP SE AR822 163 LOGO HERE @ Copyright. All rights reserved. Define Global Settings In order to establish the connectivity with CIG, under global settings user needs to: i. Maintain Certificates ii. Create RFC Destination iii. Create Port Definition iv. Create Logical System v. Configure Receiver Port vi. SAP Data Sync – Send SAP system information to CIG The following slides provide a summary of these six settings. For more detailed instructions on how to configure each of these settings, please review the attached document. © SAP SE AR822 164 LOGO HERE @ Copyright. All rights reserved. Define Global Settings – Maintain Certificates Maintain certificates to authenticate the users & clients, and to ensure a secure HTTPS connection to CIG: 1. Navigate to Maintain Certificates under “Global Settings” using the transaction code SPRO. 2. Click IMG-Activity for Maintain Certificates • This activity is usually performed by your SAP Basis person. • The information given here is just an example only. © SAP SE AR822 165 LOGO HERE @ Copyright. All rights reserved. Define Global Settings – Maintain Certificates When you click on Maintain Certificates, the Trust Manager screen appears. Import SSL Server Certificate for HTTPS connection: This is the root certificate of CIG. 1. On the Trust Manager screen, click SSL Client SSL Client(Anonymous) 2. Click the Import Certificates button • The certificate you needto upload here is the Loadbalancer certificate which you will find in Resource section of CIG portal. • Please choose the certificate for an appropriate environment - TEST or PRODUCTION. • Download the certificate and save it on the local drive of application server of your SAP system. © SAP SE AR822 166 LOGO HERE @ Copyright. All rights reserved. Define Global Settings – Maintain Certificates Import SSL Server Certificate for HTTPS connection - continued 3. Navigate to the local drive in your computer where you have saved the SSL server certificate of CIG, select the certificate & press Enter. 4. Click Allow to import the certificates. © SAP SE AR822 167 LOGO HERE @ Copyright. All rights reserved. Define Global Settings – Maintain Certificates Import SSL Server Certificate for HTTPS connection - continued 5. Click Add to Certificate List & you will see a message that you have added the certificates successfully. © SAP SE AR822 168 LOGO HERE @ Copyright. All rights reserved. Define Global Settings – Maintain Certificates Ensure that you save the newly added certificates. This notifies the ICM about the new certificates you have just imported. © SAP SE AR822 169 LOGO HERE @ Copyright. All rights reserved. Define Global Settings – Maintain Certificates Import SSL Server Certificate for HTTPS connection…(continued…): 6. After you have saved the entries in the STRUST, run the transaction code SMICM © SAP SE AR822 170 LOGO HERE @ Copyright. All rights reserved. Define Global Settings – Maintain Certificates Import SSL Server Certificate for HTTPS connection…(continued…): 7. On the menu Administration, click ICM >>> Restart, click Yes © SAP SE AR822 171 LOGO HERE @ Copyright. All rights reserved. Define Global Settings – Maintain Certificates Import SSL Server Certificate for HTTPS connection…(continued…): 8. In the popup Internet Communication Manager, “Do you really want to restart all ICM processes in the system?”, click Yes Internet Communication Manager (ICM) The ICM ensures that communication between the SAP System (SAP Web Application Server) and the outside world via HTTP, HTTPS and SMTP protocols works properly. • ICM acts as listener and any URL (with a server and port combination) that comes from the outside world will be transferred to the local handler. • The ICM and the SAP Web Dispatcher use the same code basis. • The main difference between them is that the Web dispatcher performs load balancing, and passes requests to ICMs on the connected application servers rather than to work processes. © SAP SE AR822 172 LOGO HERE @ Copyright. All rights reserved. Define Global Settings – Maintain Certificates Import Client / User Certificate for certificate based authentication: ü Ensure that you have the Client / User certificate that you have received from an SAP Ariba trusted Certificate Authority (CA). ü Import the private key of the certificate into the SAP Business Suite system by using the Trust Manager. ü You can only import certificates in the Personal Security Environment (PSE) format. ü Certificates in other formats must first be converted to the PSE format. ü Use the command line tool SAPGENPSE to do the conversion. ü Install the SAPGENPSE tool with the SAP Cryptographic Library installation package. • EXAMPLE: to convert the P12 (Public-Key Cryptography Standards) format to PSE format, enter the following command line: sapgenpse import_p12 -v -r -p • This is not required if you are routing the transaction documents through a middleware. • To get information about the CAs currently trusted by Ariba or to register a CA to be trusted by SAP Ariba, contact Ariba Support. • For more information, you can see The SAP Cryptographic Library Installation Package [external document]. © SAP SE AR822 173 LOGO HERE @ Copyright. All rights reserved. Define Global Settings – Maintain Certificates Import Client / User Certificate for certificate based authentication: 1. Click Maintain Certificates under “Global Settings” using the transaction code SPRO; then click IMG-Activity for Maintain Certificates. The Trust Manager screen appears © SAP SE AR822 174 LOGO HERE @ Copyright. All rights reserved. Define Global Settings – Maintain Certificates Import Client / User Certificate for certificate based authentication (continued): 2. Click Environment, and select SSL Client Identities © SAP SE AR822 175 LOGO HERE @ Copyright. All rights reserved. Define Global Settings – Maintain Certificates Import Client / User Certificate for certificate based authentication (continued): 3. Click New Entries 4. Click in the box below Identity, and type “ARIBA” (example only); in the Description box, type “Ariba Network Client” (example only) 5. Click Save © SAP SE AR822 176 LOGO HERE @ Copyright. All rights reserved. Define Global Settings – Maintain Certificates Import Client / User Certificate for certificate based authentication 6. Import the private key of the certificate into the SAP system by using the Trust Manager (transaction STRUST). Ø To create PSE for the newly added SSL Client ID, select the newly created ARIBA SSL Client ID Ø Click PSE, click Import © SAP SE AR822 177 LOGO HERE @ Copyright. All rights reserved. Define Global Settings – Maintain Certificates Continued… Ø Select the file. click Allow Ø Enter the password for the certificate if required © SAP SE AR822 178 LOGO HERE @ Copyright. All rights reserved. Define Global Settings – Maintain Certificates Continued… Ø To save, click PSE > Save as > SSL Client Ø Enter “ARIBA” as the SSL Client Ø Navigate to the Own Certificate group box on the Trust Manager screen, and double click the certificate to add it to the Certificate List. © SAP SE AR822 179 LOGO HERE @ Copyright. All rights reserved. Define Global Settings – Maintain Certificates Import Client / User Certificate for certificate based authentication Import the root certificate into the SAP system by using Trust Manager as follows: Ø Double-click the SSL Client Identity ARIBA that you have created. © SAP SE AR822 180 LOGO HERE @ Copyright. All rights reserved. Define Global Settings – Maintain Certificates Import Client / User Certificate for certificate based authentication Ø Navigate to the Certificate group box and choose imported certificate. Click Add to Certificate List to add the imported certificate to the certificate list. You can now see the newly added certificate in the Certificate List of the Trust Manager. © SAP SE AR822 181 LOGO HERE @ Copyright. All rights reserved. Define Global Settings – Maintain Certificates Import Client / User Certificate for certificate based authentication 4. Use transaction SMICM to activate the changes and restart the Internet Communication Manager (ICM). • Click Administration • Click ICM • Click Restart • Click Yes For more information, go to the SAP documentation portal and search for the phrase “Using the ICM Monitor.” © SAP SE AR822 182 LOGO HERE @ Copyright. All rights reserved. Define Global Settings – Maintain Certificates Import Client / User Certificate for certificate based authentication…(continued…): Your certificate must be from one of the Trusted Certificate Authorities as SAP Ariba Cloud Integration Gateway does not support loading any new certificate authorities. List of Trusted Certificate Authorities: A list of Trusted Certificate Authorities can be found in SAP Help Portal by searching for “Trusted Certificate Authorities” © SAP SE AR822 183 LOGO HERE @ Copyright. All rights reserved. Define Global Settings – Create RFC Destination RFC Destination RFC Destination is needed for transmitting IDocs because it allows you to connect from an ABAP system to an external system. • Before creating an RFC destination for CIG, ensure that you have access to credentials (P User & password) which were provided when you enabledthe CIG setting on Ariba Network. • You may need to create 2 RFC destinations – one for Ariba Network Integration & another one for SAP Ariba Applications (Retail Article Master Data) Integration. © SAP SE AR822 184 LOGO HERE @ Copyright. All rights reserved. Define Global Settings – Create RFC Destination Create RFC Destination to connect to CIG. For creating the same follow these steps: 1. Navigate to Global Settings using the transaction code SPRO. 2. Click IMG-Activity for Create RFC Destination © SAP SE AR822 185 LOGO HERE @ Copyright. All rights reserved. Define Global Settings – Create RFC Destination The Configuration of RFC Connections screen appears. 3. Click HTTP Connections to External Server 4. Click Create © SAP SE AR822 186 LOGO HERE @ Copyright. All rights reserved. Define Global Settings – Create RFC Destination 5. Maintain the fields for the following parameters: Ø RFC Destination Ø Description Ø Under Technical Settings tab, maintain the following parameters for Target System Settings: • Target Host: testacig.ariba.com (for test system) or acig.ariba.com (for production system) • Service No.: 443 • Path Prefix (for Ariba Network & Ariba Sourcing Integration): /cxf/receiveIDOC • Path Prefix (for Ariba Retail Integration): /cxf/receiveERPIDOC Ø (Optional) HTTP Proxy Options: • Proxy Host: proxy.ariba.com (for example). • Proxy Service: 8080 (for example). Example of RFC Destination for Ariba Network Integration © SAP SE AR822 187 LOGO HERE @ Copyright. All rights reserved. Define Global Settings – Create RFC Destination Example of RFC Destination for Ariba Applications (Retail Article Master Data) Integration © SAP SE AR822 188 LOGO HERE @ Copyright. All rights reserved. Define Global Settings – Create RFC Destination 6. On the Logon & Security tab, choose the following: ü Logon Procedure: Basic Authentication. ü User: Enter CIG username. ü Password: Enter CIG password ü SSL: Active. ü SSL Client Certificate: ANONYM SSL Client (Anonymous) 7. Click Save © SAP SE AR822 189 LOGO HERE @ Copyright. All rights reserved. Define Global Settings – Create RFC Destination If you are using middleware: 1. Navigate to Global Settings using the transaction code SPRO. 2. Click IMG-Activity for Create RFC Destination – the Configuration of RFC Connections screen appears. 3. Configure one of the followings – Ø For single stack Process Integration, create RFC destination of type T – • Click TCP/IP Connections, click Create, and configure the settings. Ø For dual-stack Process Integration, create RFC destination of type 3 • Click ABAP Connections, click Create, and configure the settings. © SAP SE AR822 190 LOGO HERE @ Copyright. All rights reserved. Define Global Settings – 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. To create port definition for outbound IDocs, perform the following steps: 1. Navigate to Global Settings using the transaction code SPRO. 2. Click IMG-Activity for Create Port Definition © SAP SE AR822 191 LOGO HERE @ Copyright. All rights reserved. Define Global Settings – Create Port Definition The Ports in IDoc processing screen appears. 3. Click XML HTTP and click Create – The Add XML HTTP Port screen appears. © SAP SE AR822 192 LOGO HERE @ Copyright. All rights reserved. Define Global Settings – Create Port Definition 4. Enter the following parameters: Ø Port: CIGPORT (for example) Ø RFC destination: HCI_CON (for example) (use the RFC destination that you created earlier). 4. Choose Content Type as Text/XML 5. Check the SOAP Protocol box. 6. Click Save. Create separate ports for Ariba Network integration & SAP Ariba applications integration providing the respective RFC Destination you have created in earlier step. © SAP SE AR822 193 LOGO HERE @ Copyright. All rights reserved. Define Global Settings – Create Port Definition If you are using middleware: 1. Navigate to Global Settings using the transaction code SPRO. 2. Click IMG-Activity for Create Port Definition – The Ports in IDoc processing screen appears. 3. Click Transactional RFC and click Create – The Create tRFC Port screen appears. 4. Select Own port name and enter a name. You can also select Generate Port Name to let the system create port name. © SAP SE AR822 194 LOGO HERE @ Copyright. All rights reserved. Define Global Settings – Create Port Definition If you are using middleware (continued) 5. Enter the following parameters: Ø Port: MDLWRPORT (for example) Ø Select IDoc record types for the version of your SAP. Ø RFC destination: HCI_CON (for example) (use the RFC destination that you created earlier). 6. Click Save. © SAP SE AR822 195 LOGO HERE @ Copyright. All rights reserved. Define Global Settings – Create Logical System To create a receiver logical system for outbound IDocs, perform the following steps: 1. Navigate to Global Settings using the transaction code SPRO. 2. Click IMG-Activity for Create Logical System © SAP SE AR822 196 LOGO HERE @ Copyright. All rights reserved. Define Global Settings – Create Logical System The Change View “Logical Systems”: Overview screen appears. 3. Click New Entries – the New Entries: Overview of Added Entries screen appears 4. Enter the following parameters: Ø Log. System: Logical System Name (ARIBA for example) Ø Name: Enter a description for the logical system. 5. Click Save © SAP SE AR822 197 LOGO HERE @ Copyright. All rights reserved. Define Global Settings – Configure Receiver Ports Users need to configure separate ports for sending IDoc data to: ü Ariba Network & Ariba Sourcing (Transaction Data) ü Ariba Sourcing (Retail / Article Master Data) ü Middleware (for mediated connectivity customers) To configure a receiver port for outbound IDocs, perform the following steps: 1. Navigate to Global Settings using the transaction code SPRO & click IMG-Activity for Configure Receiver Port – the Change View "Table for Storing Receiving Port Solutions": Overview screen appears. © SAP SE AR822 198 LOGO HERE @ Copyright. All rights reserved. Define Global Settings – Configure Receiver Ports The Change View "Table for Storing Receiving Port Solutions": Overview screen appears. 2. Click New Entries © SAP SE AR822 199 LOGO HERE @ Copyright. All rights reserved. Define Global Settings – Configure Receiver Ports The New Entries: Overview of Added Entries screen appears. 3. Enter the following values in the Table for Storing Receiving Port Solutions section: Ø IDOC: Select value from dropdown based on the solution you are adopting. (For example: IDOC for Ariba Network; IDOC for SAP Ariba Applications or IDOC Send through Middleware. Ø Receiver Port: Enter the receiver port for the IDOC type that you selected. 4. Click Save © SAP SE AR822 200 LOGO HERE @ Copyright. All rights reserved. Define Global Settings – SAP Data Sync SAP Data Sync User needs to send SAP system information such as such as, version, system ID, system time zone, system client, and ERP software component to CIG. Prerequisites: ü SSL server certificates for HTTPS connection should have been imported before sending SAP system information to CIG. ü P User ID for CIG is created. Information sent to CIG includes – SAP Version, System ID, System Time Zone, System Client, and ERP Software Component; Domain; Port; etc. • This information is used while creating a project to connect CIG to your SAP system. • Also, based on the AddOn SP version, CIG will understand which XSLT transformation / mappings version to pick for that customer. • To run this, the User needs “ARBCIG_SPR: Authorization Object for Add On Special Programs” authorization object. © SAP SE AR822 201 LOGO HERE @ Copyright. All rights reserved. DefineGlobal Settings – SAP Data Sync To send SAP system information to CIG, perform these steps: 1. Navigate to Global Settings using the transaction code SPRO. 2. Navigate to Send SAP Information to SAP Ariba Cloud Integration Gateway. 3. Click IMG-Activity for Synchronize SAP Information with SAP Ariba Cloud Integration Gateway – The Synchronize SAP Information with SAP Ariba Cloud Integration Gateway screen appears. © SAP SE AR822 202 LOGO HERE @ Copyright. All rights reserved. Define Global Settings – SAP Data Sync 4. Enter the following SAP Ariba Cloud Integration Gateway credentials in SOA Manager Credentials to Setup Initial Connection with CIG section: Ø User Name (your P User name) Ø Password (your P User password) Ø Name of Proxy Host (your organization proxy) Ø Port Number of Proxy Host Ø Proxy User (Proxy user name) Ø Proxy User Password 5. Select Data Center: Ø Data Center for Europe Ø Data Center for China 6. Connection Instances, select one of the following options: Ø Connect to Cloud Integration Gateway Test Instance: Select this if you are setting up a test instance. Ø Connect to Cloud Integration Gateway Production Instance: Select this if you are setting up a production instance. © SAP SE AR822 203 LOGO HERE @ Copyright. All rights reserved. Define Global Settings – SAP Data Sync The SAP ERP or SAP S/4 HANA information is now sent to the SAP Ariba Cloud Integration Gateway: © SAP SE AR822 204 LOGO HERE @ Copyright. All rights reserved. Define Global Settings – SAP Data Sync More about SAP Data Sync: • This task is a one-time activity. • Even if you are integrating via a middleware, you need to send this info to CIG for identifying which XSLT mappings version to pick. • When you upgrade your SAP ERP or SAP S/4HANA system, the upgrade information is automatically transmitted to the SAP Ariba Cloud Integration Gateway. • After you run the report, you can view the status of the report message status using the TCode SLG1, the object: ARBCIG_UTILITY, and the sub-object; SYSTEMINFO © SAP SE AR822 205 LOGO HERE @ Copyright. All rights reserved. Define Global Settings - Configure attachments and comments Transactions Attachments Supported? Comments Supported? Document type Credit memo Yes Yes CreditMemoMsg Ship notice request Yes Yes DsptchdDelivNotifMsg FI-based ERP-initiated invoice Yes Yes ARBCIG_FIDCC2 Invoice Yes Yes ARBCIG_INVOIC Liability transfer Yes Yes LiabilityTransfer MM-based ERP-initiated invoice Yes Yes ARBCIG_GSVERF Order confirmation Yes Yes ARBCIG_ORDRSP Order enquiry Yes Yes ARBCIG_ORDENQ PayMeNow Yes Yes ARBCIG_FIDCCH Payment remittance request Yes Yes ARBCIG_REMADV Purchase order Yes Yes ARBCIG_ORDERS Remittance advice Yes Yes RemittanceAdvice Scheduling agreement release Yes Yes ARBCIG_DELINS Service sheet Yes Yes ServiceEntrySheetRequest Service sheet response Yes Yes ServiceEntrySheetResponse Advance Ship notice Yes Yes DsptchdDelivNotifMsg The table below lists which documents support attachments and/or comments for Network Integration flows: Attachments are supported at the: • Header level using the SAP Generic Object Services (GOS) • Line level using the SAP Document Management System (DMS) Comments are supported as: • Text Object © SAP SE AR822 206 LOGO HERE @ Copyright. All rights reserved. Define Global Settings - Configure attachments and comments Transactions Attachments Supported? Comments Supported? Document type Component consumption request Yes No ComponentConsumption Component acknowledgment No No ComponentAcknowledgement Document status update No No DocumentStatusUpdateRequest Invoice status update No No InvoiceStatusUpdateRequest Payment proposal No No PaymentProposalRequest Product activity message No No ProductActivityMessage Product replenishment message No No ProductReplenishment Receipt request No No ReceiptDetailRequest The table below lists which documents support attachments and/or comments for Network Integration flows (continued): Attachments are supported at the: • Header level using the SAP Generic Object Services (GOS) • Line level using the SAP Document Management System (DMS) Comments are supported as: • Text Object © SAP SE AR822 207 LOGO HERE @ Copyright. All rights reserved. Define Global Settings - Configure attachments and comments The table below lists which documents support attachments and/or comments for Procurement Integration flows: Messages Attachments Supported? Comments Supported? Document type Advance Payment No No AdvancePaymentExportRequest Master data request No No AribaMasterDataRequestMessage Catalog upload request No No CatalogUploadRequest Language No No LanguageExports Payment Export Yes No PaymentExportRequest Purchase Order Yes Yes PurchaseOrderExportRequest Purchase Order Cancel No No PurchaseOrderCancelExportRequest Purchase Order Change Yes Yes PurchaseOrderChangeExportRequest Purchase Order Close No No PurchaseOrderCloseStatusExportRequest PurchaseOrderERPHeaderStatusAsyncImportRequest No No PurchaseOrderERPHeaderStatusAsyncImportRequest Purchase order header status No No PurchaseOrderHeaderStatus Receipt export request No No ReceiptExportRequest Derivation No No RequisitionDeriveAccountingExportRequest Real time budget export No No RequisitionRealTimeBudgetExportRequest Service sheet No No ServiceSheetExportRequest Service sheet response No No ServiceEntrySheetResponse © SAP SE AR822 208 LOGO HERE @ Copyright. All rights reserved. Define Global Settings - Configure attachments and comments The table below lists which documents support attachments and/or comments for Sourcing Integration flows: Messages Attachments Supported? Comments Supported? Document type Request for quotations Yes Yes QuoteRequest QuoteMessage Contracts No Yes ContractRequest Attachments are supported at the: • Header level using the SAP Generic Object Services (GOS) • Line level using the SAP Document Management System (DMS) Comments are supported as: • Text Object © SAP SE AR822 209 LOGO HERE @ Copyright. All rights reserved. Define Global Settings - Configure attachments and comments In the scenario where user wants to send attachments at line level for IDoc and proxy inbound documents, perform the following steps: 1. Navigate to Global Settings>Supporting Attachments & Comments >Support Attachments using the transaction code SPRO. 2. Click IMG-Activity for Maintain Parameters for Line Level Attachment from Cloud Integration Gateway © SAP SE AR822 210 LOGO HERE @ Copyright. All rights reserved. Define Global Settings - Configure attachments and comments The Parameters - Attachment screen appears. 3. Maintain the following parameters: • DOCUMENT_TYPE • DMS_STORAGE_CATEGORY Parameter Name Supported Values DOCUMENT_TYPE Variable Name: DOCUMENT_TYPE Field Name: Leave it blank Number: 0000 Low: DRW (for example) Document type maintained here will be used to create attachment in DMS system. The document type is used to categorize documents according to their distinguishing features and the organizational procedures that result from them. The description of the document type is language-dependent. Examples: DRW - Engineering / Design Document Q00 - QM Manual DMS_STORAGE_CATEGORY Variable Name: DMS_STORAGE_CATEGORY Field Name: Leave it blank Number: 0000 Low: SAP-SYSTEM (for example) Storage Category maintained here will be used to create attachment in DMS system. This storage category is linked to a content repository, so it could again be stored in a SAP database or an archive link server. CV01N t-code • This is used only for Outbound attachment processing: /nCV01N © SAP SE AR822 211 LOGO HERE @ Copyright. All rights reserved. Define Global Settings - Configure attachments and comments Steps to implement BAdI customization to support attachments: 1. Navigate to Global Settings>>>Support Attachments using the transaction code SPRO. 2. Click IMG-Activity for Business Add-Ins (BAdIs) – the Information popup appears.3. Click Continue – the Create Enhancement Implementation popup appears. 4. Implement the BAdI – Ø BAdI Name – ARBCIG_ES_ATTACHMENT_UTIL Users can implement BAdI to support attachments in the scenario where certain standard transaction interfaces do not support attachments. © SAP SE AR822 212 LOGO HERE @ Copyright. All rights reserved. Define Global Settings - Configure attachments and comments Steps to implement BAdI customization to support attachments (continued): 5. Implementation Methods – Ø PRE_ATTACHMENT_PROCESS – To reprocess the attachment information. Ø POST_ATTACHMENT_PROCESS – To post-process the attachment information. Ø ATTACH_GOS_OBJECT_INSERT – To modify parameters before GOS object is inserted. Ø ATTACH_GOS_BIN_REL_CREATE – To modify parameters before GOS binary relation is created. Ø ATTACH_DMS_DOC_CREATE – To modify the parameters before creating the DMS document. Ø ATTACH_DMS_DOC_CHECKIN – To modify the parameters before the DMS document is checked-in. Ø READ_DMS_DOC_MODIFY – To modify parameters before reading the DMS document. © SAP SE AR822 213 LOGO HERE @ Copyright. All rights reserved. Define Global Settings - Configure attachments and comments To implement BAdI customization to support comments, perform the following steps: 1. Navigate to Global Settings>>>Support Comments using the transaction code SPRO. 2. Click IMG-Activity for Business Add-Ins (BAdIs) – The Information popup appears. 3. Click Continue – The Create Enhancement Implementation popup appears. 4. Implement the BAdI – Ø BAdI Name – ARBCIG_ES_COMMENT_UTIL • Comments are always supported as a Text object at both the header and line level. • Use BAdI in the scenario where user wants store comments in any other transaction related fields than the default provided. • In CIG we will configure the Header Text ID and Line Item Text ID. • Inbound à Do not Maintain à Do not Map • Outbound à Do not Maintain à Send everything For doctypes that do not support comments by default, user can implement BAdI to support comments: © SAP SE AR822 214 LOGO HERE @ Copyright. All rights reserved. Define Global Settings - Configure attachments and comments To implement BAdI customization to support comments, perform the following steps (continued): 5. Implementation Methods – Ø PRE_PROCESS_COMMENT – To reprocess the comment information. Ø POST_PROCESS_COMMENT – To post-process the comment information. While implementing BAdI method PRE_PROCESS_COMMENT, to run your custom code and skip the default processing, clear the flag C_PROCEED per document type © SAP SE AR822 215 LOGO HERE @ Copyright. All rights reserved. Define Global Settings – Map Variants and Partitions Map Variations and Partitions User can maintain the unique variant name and the partition for SAP Ariba Procurement & Sourcing. User can specify the defined values when you configure parameters for different transactions for each solution. Partition is the unique name of your site. If you do not want to maintain a variant and partition for a solution, you can add a blank record for the solution. SAP Ariba Sourcing does not need a variant or partition information, but you need to configure these values so that Ariba integration code could differentiate the parameters maintained for Procurement & Sourcing solutions. There are certain parameters maintained to execute Master Data & Transaction Data exports. To differentiate which solution you want to export master data to, users need to maintain the Variant & Partition for each solution (Procurement & Sourcing). Example: We have the table ARBCIG_TVARV – This table is used by both Ariba P2P and Ariba Sourcing. This table does not have solution (like P2P or SRC). There are some parameters (for ex: TEMP_DIR) which is used by both Ariba Sourcing and Ariba P2P. The same parameter TEMP_DIR may behave differently for Ariba sourcing and Ariba P2P. Hence this node is to co-relate variant and partition( present in ARBCIG_TVARV) to Solutions(present in this node). © SAP SE AR822 216 LOGO HERE @ Copyright. All rights reserved. Define Global Settings – Map Variants and Partitions To maintain variants & partition to Procurement & Sourcing solutions, perform the following steps: 1. Navigate to Global Settings>>>Support Comments using the transaction code SPRO. 2. Click IMG-Activity for Map Variant and Partition to Procurement and Sourcing © SAP SE AR822 217 LOGO HERE @ Copyright. All rights reserved. Define Global Settings – Map Variants and Partitions To maintain variants & partition to Procurement & Sourcing solutions (continued) The Change View "Ariba table for Variant and Partition: Master": Overview screen appears. 3. Maintain following parameters: Parameter Name Description Supported Values Variant The unique variant name for the SAP Ariba solutions in SAP ERP. VREALM_1 (for example) Partition The unique name of your site for the SAP Ariba solutions in SAP ERP. PREALM_1 (for example) Solution SAP Ariba solution name. SAP Ariba Procurement solutions or SAP Ariba Sourcing solution © SAP SE AR822 218 LOGO HERE @ Copyright. All rights reserved. Define Global Settings – Customize parameters and pre-filter values Global Settings – Customize parameters and pre-filter values To implement BAdI to customize parameter and pre-filter values, perform the following steps: 1. Navigate to Global Settings>>>BAdI to Customize Parameter and Prefilter Values using the transaction code SPRO. 2. Click IMG-Activity for Business Add-In(BAdIs) – The Information popup appears. 3. Click Continue – The Create Enhancement Implementation popup appears. 4. Implement the BAdI – Ø BAdI Name – ARBCIG_PARAM_CHANGE Ø Implementation Method – CHANGE_VALUES to modify parameter values. This BADI is to massage the data before storing the values to TVARV.Buyer Integration: Supported Systems SAP ERP SAP S/4HANA Back-end SAP EHP0 for SAP ERP 6.0 (SAP_APPL 600 SP22) SAP EHP2 for SAP ERP 6.0 (SAP_APPL 602 SP12) SAP EHP3 for SAP ERP 6.0 (SAP_APPL 603 SP11) SAP EHP4 for SAP ERP 6.0 (SAP_APPL 604 SP12) SAP EHP5 for SAP ERP 6.0 (SAP_APPL 605 SP09) SAP EHP6 for SAP ERP 6.0 with non-HANA DB (SAP_APPL 606 SP05) SAP EHP6 for SAP ERP 6.0 with HANA DB (SAP_APPL 606 Minimum supported version) SAP EHP7 for SAP ERP 6.0 (SAP_APPL 617 Minimum supported version) SAP EHP8 for SAP ERP 6.0 (SAP_APPL 618 Minimum supported version) SAP_BASIS 700 SP27 is the SAP Basis version for all the above SAP ERP versions On-Premise Edition1610; On-Premise Edition1709; On- Premise Edition1809 & On-Premise Edition1909. AddOn for SAP ERP & SAP S/4HANA SAP Ariba Cloud Integration Gateway, Add-On for SAP ERP SAP Ariba Cloud Integration Gateway, Add-On for SAP S/4HANA Software Components ARBCI1 100 – For EhP 0 & higher (Base Component) ARBCI2 100 – For EhP 4 & higher (For SAP Ariba Sourcing Services Contract Feature Only) ARBCIGR 100 – For EhP 0 & higher (For RETAIL Article Master Data integration only) ARBCI1 10S (Base Component) ARBCI2 10S (For SAP Ariba Sourcing Services Contract Feature Only) ARBCIGR 10S (For RETAIL Article Master Data integration only) Add-On Language English SAP Process Integration (PI) / Process Orchestration (PO) SAP PI 7.1; SAP PI 7.3; SAP PO 7.4 & SAP PO 7.5 RETAIL TIP: Before you install the Ariba Cloud Integration for RETAIL Version 1.0 (ARBCIGR 100) software component, you must install the following software packages: • ARBCI1 100 SP01 (Software package specific to SAP Ariba) • EA-RETAIL EhP0 SP22 (Enterprise software package) Use ARBCI2 100 if you want to use SAP Ariba Sourcing or SAP Ariba Contracts © SAP SE AR822 18 HOME Course Title @ Copyright. All rights reserved. Buyer Integration: Supported Solutions © SAP SE AR822 19 HOME Course Title @ Copyright. All rights reserved. Buyer Integration: Support Policy Support Policy SAP Ariba only supports the two versions of the support pack – Current version (version n) & the version preceding the current version (version n-1) for SAP Ariba Cloud Integration Gateway. Example “End-of-Life” Notice: CI Solutions & SAP Business Suite AddOn EoL: 31-December-2023 © SAP SE AR822 20 HOME Course Title @ Copyright. All rights reserved. Buyer Integration: Steps to Integrate using CIG Steps to integrate SAP backend with Ariba Network or Ariba Apps using CIG: Srl Activity Environment Description 1 Download & install AddOn. SAP ERP or SAP S/4HANA SAP Service Marketplace. 2 Enable SAP Ariba Cloud Integration Gateway Ariba Network or Ariba Applications Enable CIG settings on Ariba Apps 3 Download & install Cloud Connector. Within customer firewall SAP Development Tools. 4 Set up Global Settings. SAP ERP or SAP S/4HANA § Maintain Certificates § Define RFC Destination § Define Port Definition § Define Logical System 5 Send SAP connectivity data to CIG. SAP ERP or SAP S/4HANA Synchronize SAP information with CIG. 6 Create & setup integration project CIG § Ensure the ERP connection details are available. § Confirm SAP connectivity information. § If unavailable, configure the settings and create the connection. 7 Set up middleware (optional) SAP NW PI / PO or SAP CPI (Private Tenant) § Enable integration in SAP system § Configure middleware 8 Maintain General Settings. SAP ERP or SAP S/4HANA § Set up the Interface. § Configure Doc Status Update. IMPORTANT: It is critical to complete this step before any other task listed hereafter so that the P User ID is generated, which is needed in performing many of the remaining tasks. © SAP SE AR822 21 HOME Course Title @ Copyright. All rights reserved. Buyer Integration: Steps to Integrate using CIG Steps to integrate SAP backend with Ariba Network or Ariba Apps using CIG: Srl Activity Environment Description 9 Import Master Data SAP ERP or SAP S/4HANA Run the application specific master data events. 10 Configure Transactions SAP ERP or SAP S/4HANA Configure transactions flows as required. 11 Specify cross-reference values. CIG Define the values for parameters that are mapped from SAP backend. 12 Implement extensions and BAdIs. SAP ERP or SAP S/4HANA For customization on SAP backend. 13 Add customization via Mapping Tool. CIG Use custom Mapping Tool to map any customized parameters on SAP backend to cXML / SOAP. 14 Review configuration. CIG Examine project configurations. 15 Test project. CIG Perform testing. 16 Get ready for deployment. CIG Scheduling and activating the project on the production environment. CUSTOMIZATION TIP: Ariba strongly recommends having customization requirements identified at the initial stage of the project itself. © SAP SE AR822 22 HOME Course Title @ Copyright. All rights reserved. About This Lesson @ Copyright. All rights reserved. Lesson 4: Supported Systems, Software, & Data Flows By the end of this lesson, you will be able to: • Recognize CIG supported solutions and document flows We will cover multiple supported flows within: i. Ariba Network Integration ii. SAP Ariba Sourcing Integration iii. SAP Ariba Procurement Integration iv. Master Data Native Integration v. SAP Ariba Guided Buying Integration with S/4HANA Cloud © SAP SE AR822 23 HOME Course Title @ Copyright. All rights reserved. Supported Data Flows: Ariba Network Integration Standard Purchase Orders Blanket Purchase Orders Scheduling Agreement Release Purchase Orders Service Purchase Orders © SAP SE AR822 24 HOME Course Title @ Copyright. All rights reserved. Supported Data Flows: Ariba Network Integration Standard Purchase Order: • Buying organization requests products or services through its SAP ERP or SAP S/4 HANA system. • The CIG maps the request (IDoc) to a cXML OrderRequest and sends it to Ariba Network. • Ariba Network then routes the Purchase Order to the appropriate supplier using the supplier’s preferred order routing method. • There is no corresponding OrderResponse document. Instead, Ariba Network transmits a generic response. When the AddOn sends a OrderRequest document to Ariba Network, it responds with a synchronous cXML document that contains one of the following status codes: • 2xx, to indicate that Ariba Network has accepted the document. • 4xx, to indicate that a permanent error has occurred and the error has been logged. • 5xx, to indicate that a transient error occurred. • The CIG then resends the document with the same payload ID for the specified number of retry attempts © SAP SE AR822 25 HOME Course Title @ Copyright. All rights reserved. Supported Data Flows: Ariba Network Integration Blanket Purchase Orders (BPO): • Buyers can create and send Blanket Purchase Orders (BPOs) or changed Blanket Purchase Orders from the SAP system to suppliers on the Ariba Network. • The Blanket Purchase Order or the Change Blanket Purchase Order contains line items that specify the item category B (Limit) only. • You can also create a Blanket Purchase Order having line items that specify the item category B against a single or multiple outline agreements (OLA). • Ariba Network does not support mixed item categories in a single Blanket Purchase Order. BPO is – Used to allow multiple delivery dates over a period of time, Often negotiated to take advantage of predetermined pricing. It is normally used when there is a recurring need for expendable goods. © SAP SE AR822 26 HOME Course Title @ Copyright. All rights reserved. Supported Data Flows: Ariba Network Integration Scheduling Agreement Release: • Buyers can send a Scheduling Agreement Release as a Purchase Order (release order) to a supplier when they require material or non-material items for an extended period of time. • These Scheduling Agreement Releases contain schedules lines with details on the line item, quantity, and the different delivery dates for an extended period of time. The scheduling agreement releasesdo not contain any pricing information. • You can create either a Forecast Delivery Schedule or JIT (Just-in-time) Delivery Schedule against a scheduling agreement release. Releases inform the vendor of which quantities of a material are to be delivered on which date. Forecast Delivery Schedule contains schedule lines for line items required over a longer period of time, spanning multiple weeks or months. JIT Delivery Schedule contains line items required over a shorter period of time, spanning multiple days or even times in a day. © SAP SE AR822 27 HOME Course Title @ Copyright. All rights reserved. Supported Data Flows: Ariba Network Integration Service Purchase Order: • Purchase Orders with lines that specify category D are considered as Service Purchase Orders on Ariba Network. • Hierarchy is supported in Service Purchase Orders with service line-items in up to five levels of hierarchy (1 parent and 4 child levels). Hierarchy feature is available only on SAP ERP 6.0, EhP 4 and higher. • Following additional service line types are supported in Service Purchase Orders with planned service hierarchies Ø Blanket – Amount Based Ø Contingency Ø Informatory Contingency – Describes a service that is not essential to perform an order. Informatory – This type of service line is used to provide additional information about any other service line. © SAP SE AR822 28 HOME Course Title @ Copyright. All rights reserved. Supported Flows: Ariba Network Integration Order Inquiries Order Confirmation Order Confirmation for Scheduling Agreement & Scheduling Agreement Release Order Confirmation Approval Ship Notice Update Ship Notice Cancel Ship Notice © SAP SE AR822 29 HOME Course Title @ Copyright. All rights reserved. Supported Flows: Ariba Network Integration Order Inquiries: When an ERP buyer creates a Purchase Order and requires suppliers to confirm their purchase order or deliver items by the delivery date, they specify the number of days on which suppliers must receive reminders. When suppliers do not confirm or deliver items against the purchase order within the stipulated time, they receive these reminders. These reminders are called Inquiries. Buyers can send an Order Inquiry and request information on the following: • Delivery schedule for materials ordered against line items for an entire purchase order • Delivery date for line items having schedule lines • Reminder on the outstanding line items • Overall status of line items or the purchase order • Additional comments Suppliers can respond to these inquiries with an Order Confirmation or a response to the inquiry raised against line items in the Purchase Order. After the supplier responds to the inquiry, SAP ERP or SAP S/4HANA AddOn does not send reminders to suppliers on Ariba Network. This feature allows both buyers and suppliers to collaborate and handle processing of purchase orders efficiently. Buyers can: • Send inquiries for changed Purchase Orders. • Create up to three reminders for a purchase order in an SAP ERP or SAP S/4HANA system. Common use cases to send inquiries: 1) Delivery date approaching 2) Delivery date crossed 3) OC not received © SAP SE AR822 30 HOME Course Title @ Copyright. All rights reserved. Order Confirmation: When a supplier confirms the line items in a Purchase Order, the supplier sends an Order Confirmation from Ariba Network to the SAP ERP or SAP S/4 HANA system. The AddOn supports receiving Order Confirmations from Ariba Network for the following: • Confirmation or rejection of entire purchase order items that contain service line items. • Confirmation of orders with or without delivery dates at the header or line-level. • Confirmation of orders containing partially confirmed, rejected, and back-ordered line items. • Confirmation of orders containing line items with multiple schedule lines (delivery dates). • Comments at the header and line-item levels. A PO item that contains service line items can only be confirmed or rejected in its entirety, not at the individual service line-item level If a delivery date is provided in Ariba Network when creating a confirmation request, the delivery date is derived from the confirmation Request cXML. Otherwise the delivery date is determined from the corresponding PO item. Supported Flows: Ariba Network Integration © SAP SE AR822 31 HOME Course Title @ Copyright. All rights reserved. Supported Flows: Ariba Network Integration Order Confirmation for Scheduling Agreement & Scheduling Agreement Release: Buyers can configure the Confirmation Control Keys to receive or block Order Confirmations for Scheduling Agreement & Scheduling Agreement Releases from their suppliers. The Order Confirmation document type for Scheduling Agreement & Scheduling Agreement Release supports the following: • Confirmation of the entire Scheduling Agreement & Scheduling Agreement Release. • Confirmation of orders containing partially confirmed line items. • Attachments at header level & Comments at header & line item level. • Tolerance limits being sent along with Confirmation Control Keys from SAP system to Ariba Network. • Evaluation of tolerances done within Ariba Network, with no further tolerance evaluation in SAP ERP on receiving the order confirmation. © SAP SE AR822 32 HOME Course Title @ Copyright. All rights reserved. Supported Flows: Ariba Network Integration Order Confirmation Approval: The Order Confirmation approval feature enables you to accept Order Confirmations submitted by the supplier, which are out of tolerance for quantity, delivery date & price. • This feature does not help you modify the original tolerance levels set for the quantity, delivery date & price in the Purchase Order. • A deviation in the quantity, delivery date & price in the Order Confirmation triggers an alert on the Ariba Network buyer portal. On the Ariba Network buyer portal, you can approve or reject the deviation. • This feature also supports Order Confirmation approvals for quantity & delivery date at the schedule line level. Deviations in price are supported at line item level. • Enabling the Order Confirmation approval feature replaces the existing Order Confirmation workflow. This feature does not apply to services. Services use the Order Confirmation workflow. • The Order Confirmation approvals include the Order Confirmation details as an attachment. Based on the approval that the buyer provides, the Order Confirmation approvals update the Purchase Order in SAP ERP and a Change PO is sent to Ariba Network. © SAP SE AR822 33 HOME Course Title @ Copyright. All rights reserved. Supported Flows: Ariba Network Integration Ship Notice: Suppliers send a ship notice from Ariba Network when the they are ready to ship the items on the Purchase Order. You can receive ship notices with the following from Ariba Network suppliers: • A single Ship Notice against multiple Purchase Orders. • Multiple Ship Notices against a single or multiple line items in a Purchase Order. • Ship Notices against Purchase Orders having line items with zero quantity to indicate the items are not shipped. • Ship Notices against a Purchase Order having material line-items. • Ship Notices against Purchase Orders having the BatchID for the line items. You need to configure your SAP system to accept Ship Notices against multiple Purchase Orders. © SAP SE AR822 34 HOME Course Title @ Copyright. All rights reserved. Supported Flows: Ariba Network Integration Update Ship Notice: When a supplier changes values for the line items in ship notices, SAP ERP updates the inbound delivery document on the SAP ERP system with the changes. • Suppliers can change values for line items in the ship notice created against a single or multi-line Purchase Order, Scheduling Agreement, or a Ship Notice containing line items created against a Purchase Order and Scheduling Agreement. • The edited ship notices that suppliers send from Ariba Network can store comments& attachments. • Following changes are allowed while updating the Ship Notice: 1. Deletion of Line Item 2. Addition of Line Item 3. Quantity 4. Delivery Date 5. Unit of Measure 6. Supplier Batch ID You must enable “Allow suppliers to edit existing ship notices” rule in the Default Transaction Rules - Order Confirmation and Ship Notice Rules section. © SAP SE AR822 35 HOME Course Title @ Copyright. All rights reserved. Supported Flows: Ariba Network Integration Cancel Ship Notice: When suppliers submit a cancel ship notice, the associated ship notice is removed from the Confirmations tab and the inbound delivery is deleted in SAP system. • When a ship notice is canceled, it is assumed that no products have been received for that delivery. • Suppliers cannot cancel a ship notice after receiving the associated goods receipt. © SAP SE AR822 36 HOME Course Title @ Copyright. All rights reserved. Supported Flows: Ariba Network Integration Receipt Request Receipt with Corrections and Returns Service Sheet ERP-initiated Service Sheet Service Sheet Response Invoice Service Invoice The following pages display details of the icons below. © SAP SE AR822 37 HOME Course Title @ Copyright. All rights reserved. Supported Flows: Ariba Network Integration Receipt Requests: Buyer generates Receipts in SAP system and send them to suppliers. When Receipt data is successfully posted in Ariba Network, buyers can see the Receipts in their online Outbox. • When buyers send a receipt for the goods received, the receipt also contains the delivery note in the header. • Buyers can create receipts only for standard Purchase Orders. SAP ERP and SAP S/4HANA AddOn retrieve receipt records based on the date on which the query to fetch the records was last run as well as on the material document number. © SAP SE AR822 38 HOME Course Title @ Copyright. All rights reserved. Supported Flows: Ariba Network Integration Receipt with Corrections and Returns: Buyers can send Receipts having returns and corrections for the line items shipped against Purchase Orders. A negative value in the line item quantity denotes that there was a correction to the items received or returned. • The following movement types support returns and corrections in Receipts: Ø 101, 103, and 105 to send received quantities Ø 102 to send corrections on the received quantity Ø 122, 124, and 161 to send returned quantities Ø 123 to send corrections on the returned quantities Here is how items are calculated as received or returned: • Buyers and suppliers on Ariba Network can view the details on the returns and corrections for line items in the purchase order on the purchase order details and the order history pages. • The line items in the purchase order on Ariba Network also display the number of items received or returned. • Buyers can create and use custom Movement Types. © SAP SE AR822 39 HOME Course Title @ Copyright. All rights reserved. Supported Flows: Ariba Network Integration Service Sheet: A service sheet is created by supplier against a Purchase Order containing service type line items. Buyers can receive Service Sheets containing the following: • Service Sheets with or without hierarchy • Service Sheets containing unplanned service lines. ERP-initiated Service Sheet: Buyer can create & send Service Entry Sheets from SAP system on behalf of a supplier. The approved Service Entry Sheets are then sent to Ariba Network & can additionally be sent to SAP Ariba Invoice Management. • An ERP-initiated Service Entry Sheet supports attachments & comments. The attachments are supported at the header level of the document. • The feature accelerates the process of service procurement as buyers do not have to wait for the supplier to send the service entry sheet. Service Sheet Response: Service Sheet Response is either an approval of rejection of the Service Sheet sent by the Buyer from SAP System to the Supplier on Ariba Network. © SAP SE AR822 40 HOME Course Title @ Copyright. All rights reserved. Supported Flows: Ariba Network Integration Invoice: Suppliers send Invoices from Ariba Network to buyers on the SAP ERP or SAP S/4 HANA system. Types of Invoices supported: Ø PO-based Invoice Ø Non-PO based Invoice containing accounting information Ø Header-level Credit Memos against Purchase Order based invoices created on Ariba Network and then reconciled in the SAP Ariba Procurement Solution. Ø Header-level Credit Memos against Non-PO Invoices created in the SAP Ariba Procurement Solution. Service Invoice: Suppliers can create Invoices against Purchase Order containing service type line items based on approved Service Sheets. • Buyers can receive and process invoices with up to five-levels hierarchy created against Purchase Orders containing service type line items from Ariba Network. These invoices can also contain attachments. • Buyers can receive invoices containing the following: Ø Invoices with or without hierarchy Ø Invoices containing unplanned service lines. © SAP SE AR822 41 HOME Course Title @ Copyright. All rights reserved. Supported Flows: Ariba Network Integration Summary Invoice Direct Invoicing of Purchase Order Service Items ERP-Initiated Invoices Invoice Status Update Scheduled Payments (Payment Proposal) and Dynamic Discounting (Pay Me Now) © SAP SE AR822 42 HOME Course Title @ Copyright. All rights reserved. Supported Flows: Ariba Network Integration Summary Invoice: Summary Invoices for multiple Purchase Orders are supported. Integrated suppliers can send Summary Invoices for multiple Purchase Orders containing material items and non- material Purchase Orders having the standard item category. Summary Invoices created against multiple Purchase Orders contain the following: Ø Multiple line items from multiple Purchase Orders Ø Line items containing complete and partial quantities Summary invoices for service purchase orders are not supported • Summary Invoice © SAP SE AR822 43 HOME Course Title @ Copyright. All rights reserved. Supported Flows: Ariba Network Integration Direct Invoicing of Purchase Order Service Items: Suppliers can directly invoice a Purchase Order having the service type items. • The SAP ERP and SAP S/4HANA supports integration of invoices containing service type line items created by the supplier for service sheets auto-generated on Ariba Network. • Auto-generated service sheets for invoices created against purchase orders with service type items contain the following: Ø Line items with or without child items Ø Line items with taxes © SAP SE AR822 44 HOME Course Title @ Copyright. All rights reserved. Supported Flows: Ariba Network Integration ERP-Initiated Invoices: Invoices created on an SAP system is called an ERP-Initiated Invoices or ERP CC Invoices. These invoices created in SAP ERP or SAP S/4 HANA are then uploaded to Ariba Network. • The SAP Ariba AddOn also supports transmission of Invoices that are created through self billing. • ERP buyers can send ERP-initiated or CC Invoices from the SAP ERP or SAP S/4 HANA system (SAP ERP MM and FI Invoices) to Ariba Network using the IDOC transmission method. • Buyers can use the GSVERF03 IDoc (Extended IDoc type – ARBCIG_GSVERF) to send MM invoices and the FIDCCP2 IDoc (Extended IDoc type – ARBCIG_FIDCC2) to send FI invoices. • The ARBCIG_GSVERF and ARBCIG_FIDCC2 IDoc types are enhanced to include new segments to get additional information on the Name, Street, and City for the vendor. Buyers can customize and add segments to include additional information for vendors. • The Invoice Plan is a utility allowing you to specify when and for which amount you wish to create invoices. The creation of the invoice is independent of the receipt of the goods or the service (service entry). © SAP SE AR822 45 HOME Course Title @ Copyright. All rights reserved. Supported Flows: Ariba Network Integration ERP-Initiated Invoices (continued): IDoc transmission method can beused for the following: • Transmission of Invoices created through ERS (Evaluated Receipt Settlement). • Transmission of manually created PO-based Invoices against multiple Purchase Orders (Summary Invoices) with single and multiple line items. The line-items can contain material, advanced pricing details, and unplanned delivery cost items. • Transmission of manually created non-PO Invoices containing Material, GL Account, Contract, Internal Order, WBS Elements and Cost Center items. • Transmission of Invoices created through the Invoice plan containing both periodic and partial items. • Transmission of Credit Memos for FI and MM Invoices. © SAP SE AR822 46 HOME Course Title @ Copyright. All rights reserved. Supported Flows: Ariba Network Integration Invoice Status Update: Buyers can send and receive the statuses of invoices created on SAP ERP, SAP S/4HANA, or Ariba Network when the status for invoices is updated on SAP ERP or SAP S/4HANA. The Invoice Status Update (ISU) transaction processes invoices that are Ø Created Ø Changed Ø Reversed Ø Canceled Ø Parked or Parked invoices that have been deleted on the SAP system Ø Paid © SAP SE AR822 47 HOME Course Title @ Copyright. All rights reserved. Supported Flows: Ariba Network Integration Scheduled Payments (Payment Proposal) and Dynamic Discounting (Pay Me Now): • The Ariba Discount Professional solution allows buyers to request or offer early settlement in exchange for a discount from suppliers. Buying organizations use Scheduled Payments to tell suppliers about planned payments. • These documents (PaymentProposalRequest) list scheduled payment dates, discount amounts, and net amounts. • If suppliers choose schedule payments for early settlement, Ariba Network sends the updated Scheduled Payments back to the buying organization. • Updated Scheduled Payment documents are then used to update the payment schedule and discount amount in the buying organization’s SAP system. SAP Ariba Payables subscription is required to use these functionalities. © SAP SE AR822 48 HOME Course Title @ Copyright. All rights reserved. Supported Flows: Ariba Network Integration Supply Chain Finance Payment Remittance Request Payment Remittance Advice Supply Chain Collaboration – Subcontracting Supply Chain Collaboration – Consignment Supply Chain Collaboration – Return Process Supply Chain Collaboration – Forecast Collaboration © SAP SE AR822 49 HOME Course Title @ Copyright. All rights reserved. Supported Flows: Ariba Network Integration Supply Chain Finance (SCF): This allows third party funders to provide financing for early payment to a supplier in exchange for discounts on the total invoice amount. • The supplier receives funds early at a discount and the buyer increases DPO by extending terms. • Each trading participant may therefore meet its working capital objective. The financing is facilitated by an SCF provider such as Prime Revenue who has relationships with one or more funders to pay approved invoices early in exchange for payment from the buyer on the net due date (at maturity). Ø Buyers send payment proposals for approved invoices and credit memos marked for Supply Chain Financing to Ariba Network from your SAP ERP or SAP S/4HANA system. Ø The Supply Chain Financing provider sends the supplier a TradeRequest document to make an early payment to a supplier. Ariba Network sends you the remittance advice with details on the early payment to the supplier Ø Buyers can receive payment remittances for payments made by the provider to suppliers on Ariba Network. A remittance advice for payments made against approved invoices and credit memos from Ariba Network is then sent to your SAP ERP or SAP S/4HANA system. Days payable outstanding (DPO) is a company's average payable period. Days payable outstanding tells how long it takes a company to pay its invoices from trade creditors, such as suppliers. © SAP SE AR822 50 HOME Course Title @ Copyright. All rights reserved. Supported Flows: Ariba Network Integration Payment Remittance Request (Outbound): Buyers can send a PaymentRemittanceRequest to notify suppliers when payment is made. Payment Remittance Advice (Inbound): • If you have subscribed to make payments from a Supply Chain Financing (SCF) provider, you can receive payment remittances for payments made by the provider to suppliers on Ariba Network. • You can receive remittance advice for payments made against approved invoices and credit memos from Ariba Network to your SAP system. • Payment Remittance Advice requests are sent by SCF Provider via Ariba Network to notify suppliers; buyers & SAP system about external payment made directly from Ariba Network. It sends PaymentRemittanceAdviceRequest documents to suppliers as well as to SAP ERP system to create necessary accounting document. © SAP SE AR822 51 HOME Course Title @ Copyright. All rights reserved. Supported Flows: Ariba Network Integration Supply Chain Collaboration - Subcontracting: • Subcontract PO – Purchase Order raised by buyer to contract manufacturer about the components , cost of manufacturing and required delivery date of the finished product after subcontract process. • Order Confirmation (OC) • Component Ship Notice – Information about the components which are shipped by buyer. • Component Acknowledgement – Acknowledgment of components’ which was sent by buyer through component ship notice. • Product Activity Message – Carry out the component’s vendor stock in subcontract process • Component Consumption Request – Carry out the consumption of components recorded by the supplier and creates consumption document in SAP / Manufacturing visibility of the supplier production process. • Ship Notice Request • GRN • Invoice Sending serial numbers for subcontracting components and standard items in the following transaction documents: • Purchase Order (standard Purchase Order and Subcontracting Purchase Order) • Ship Notice • Component Ship Notice • Receipt • Component Consumption Request © SAP SE AR822 52 HOME Course Title @ Copyright. All rights reserved. Supported Flows: Ariba Network Integration Supply Chain Collaboration – Consignment: • Consignment PO – Purchase order raised by the buyer to supplier about the information of the consignment stock (Required date , Material, Shipping Address etc.). • Order Confirmation (OC) • Ship Notice • GRN • Product Activity Message (Consignment Withdrawals) – Information about the consignment stock used by the buyer from supplier stock. • Consignment settlement/Invoice – Invoice raised by the buyer to the supplier based on the withdrawal consumption. © SAP SE AR822 53 HOME Course Title @ Copyright. All rights reserved. Supported Flows: Ariba Network Integration Supply Chain Collaboration – Return Process: • Return PO - Purchase order raised by the buyer to supplier about the information of the return materials. • Return Delivery - Information about the materials which are shipped by buyer w.r.t return PO. • Credit memo – Credit memo raised by the supplier to the buyer for return goods. Supply Chain Collaboration – Forecast Collaboration: • Forecast Product Activity message - Sending requirement of the buyer materials (Demand) to the supplier. • Forecast Product Replenishment – Commit by the supplier in response to forecast Product Activity message. © SAP SE AR822 54 HOME Course Title @ Copyright. All rights reserved. Supported Flows: Ariba Network Integration Supply Chain Collaboration – Supplier Managed Inventory (SMI) Supply Chain Collaboration – Quality Notifications Supply Chain Collaboration – Quality Inspection Supply Chain Collaboration – Quality Certificate © SAP SE AR822 55 HOME Course Title @ Copyright. All rights reserved. Supported Flows: Ariba Network Integration Supply Chain Collaboration – Supplier Managed Inventory (SMI): • SMI Scheduling Agreement - Sending requirement of the buyer materials (Demand andInventory position) to the supplier. • SMI Product Activity Message / Inventory Demand • SMI Product Replenishment / SMI Commit / Delivery Schedule Lines- Commit by the supplier in response to SMI Product Activity message. • Ship Notice Request • GRN • Invoice © SAP SE AR822 56 HOME Course Title @ Copyright. All rights reserved. Supported Flows: Ariba Network Integration Supply Chain Collaboration – Quality Notifications (QN): Buyers can send notifications to suppliers informing them of quality-related issues in components or finished goods. • Suppliers can inform buyers of problems relating to goods & services and respond to the quality issues raised by the buyer. • Buyers & suppliers can send and receive quality notifications to address the following issues: Ø Defect Analysis Ø Complaint against Buyers Ø Complaint against Suppliers Ø Deviation reported by Suppliers Supply Chain Collaboration – Quality Inspection: Buyers can send suppliers a request to inspect the quality of goods sent by them. Ø Upon receiving the request, suppliers inspect the quality of goods & send the results of the quality inspection to the buyer. Ø Buyers confirm their decision based on the quality inspection result. Ø Buyers can send the task status for a quality notification as “successful” to indicate that the quality notification task is complete & closed. When buyers send the status “Successful,” Ariba Network sets the task for the quality notification as “Closed.” Ø Suppliers can send the task status for the quality notification as “Closed” & SAP ERP stores the status as “Successful.” • QN ensures that buyers and suppliers have a real time end-to-end visibility throughout the order fulfillment process. • SAP ERP buyers use the master data report to download the quality notification codes from their SAP ERP system and upload them on Ariba Network. © SAP SE AR822 57 HOME Course Title @ Copyright. All rights reserved. Supported Flows: Ariba Network Integration Supply Chain Collaboration – Quality Certificate: • Buyers can receive Ship Notices containing Quality Certificate from suppliers on Ariba Network. Buyers create the quality certificate records for the inbound delivery on the SAP ERP system. • Buyers can ensure the quality of components or material items by requesting for & mandating the quality certificates for components & materials items that suppliers ship them. Ø Mark the quality certificates as a mandatory or an optional requirement at the line-item level in Purchase Order. Ø Specify if material items require a quality certificate at the line-item level in Purchase Order. Ø Mark the quality certificates as a mandatory or optional requirement when sending a request for the quality inspection of goods. © SAP SE AR822 58 HOME Course Title @ Copyright. All rights reserved. Supported Flows: SAP Ariba Sourcing Integration Master Data Contract Scheduling Agreement Quote Request / RFQ Quote Message / Award © SAP SE AR822 59 HOME Course Title @ Copyright. All rights reserved. Supported Flows: SAP Ariba Sourcing Integration Master Data: Master data consists of general information that resides on SAP system that Ariba Sourcing uses to build and process data in transactions. Buyers using CIG can seamlessly integrate master data from the SAP system to the Ariba Sourcing solutions using the following options: • Full Load • Incremental Load SAP ERP buyers integrated with Ariba Sourcing or Ariba Contracts can import the following master data: • Organizational Data such as Company Code; Purchasing Org; Plant; Plant-Purchasing Org & Purchasing Group. • Cross/Application Configuration Data such as Payment Terms & INCO Terms. • Material Master Data such as Material Master; Item Category; ERP Commodity Code & Purchase Info Records (PIR). • When buyers import the master data for the first time, Ariba recommends that you choose the Full load mode. • Buyers can use the incremental load for subsequent run to import master data records that have been added, modified, or deleted since the last master data import event. • When importing master data for the first time, SAP Ariba recommends to choose the Full Load mode. For subsequent addition, modification, or deletion run use the incremental load. • Material master data contains large volume of information. For best performance, always set filters that specify the criteria based on which you can import smaller subsets. © SAP SE AR822 60 HOME Course Title @ Copyright. All rights reserved. Supported Flows: SAP Ariba Sourcing Integration Contract: A contract is a voluntary agreement between two or more parties (buyer & supplier) that is enforceable at law as a binding legal agreement over an extended period of time. Types of Contracts supported in SAP Ariba Sourcing Integration with SAP system: Value Contract – This is an agreement that customer will order a specific value of reasonable products during a specified period. In SAP system, Value Contract is referred using Agreement Type “WK”. Quantity Contract – This is an agreement that customer will order a specific quantity of reasonable products during a specified period. In SAP system, Quantity Contract is referred using Agreement Type “MK”. The flow: • SAP Ariba Contracts sends a contract document • CIG creates a contract on the SAP system & sends a response confirming the creation of the contract on the SAP system. • CIG also sends a confirmation to Ariba Contracts when the contract has been updated or deleted on the SAP system. • CIG sends a confirmation message for contracts created as follows: Ø If you are using SAP ERP 6.0 EHP0 to EHP3, SAP Ariba Cloud Integration Gateway sends the QuoteResponse confirmation message. Ø If you are using SAP ERP 6.0 EHP4 or above, SAP Ariba Cloud Integration Gateway sends the SAP ERP standard confirmation message. Buyers can also create a sourcing event or contract line items document (CLID) with multiple service line items directly from SAP Ariba Sourcing or SAP Ariba Contracts. These sourcing events do not need an associated RFQ from SAP System. © SAP SE AR822 61 HOME Course Title @ Copyright. All rights reserved. Supported Flows: SAP Ariba Sourcing Integration Scheduling Agreement: A Scheduling Agreement is a long-term purchase agreement with the vendor in which a vendor is bound for supplying of material according to predetermined conditions. Details of the delivery date and quantity communicated to the vendor in the form of the delivery schedule. • SAP Ariba Contracts can send contracts with the document category, scheduling agreement and with the document type, LP (without release) or LPA (with release). • Buyers can also specify a custom document type for the contract on CIG. © SAP SE AR822 62 HOME Course Title @ Copyright. All rights reserved. Supported Flows: SAP Ariba Sourcing Integration Quote Request / RFQ: Quote Request is a form of invitation that is sent to vendors to submit quotation indicating pricing and their terms and conditions. Quote Request / RFQ contains details about goods or services, quantity, date of delivery and date of bid on which it is to be submitted. SAP System users can create & send a Request for Quotation as follows: Ø Send RFQ / Quote Request cXML document to SAP Ariba Sourcing. Ø Send RFQ to the Ariba Network where an RFQ event is created and published on SAP Ariba Discovery. Buyers can create requests for quotation with material items or service line items (category D with up to five-level hierarchy – one parent item and four-level child) as follows: Ø Create a new request for quotation Ø Create a request for quotation against a purchase requisition Ø Create a request for quotation against a contract (outline agreement) © SAP SE AR822 63 HOME Course Title @ Copyright. All rights reserved. Supported Flows: SAP Ariba Sourcing Integration Quote Request / RFQ (continued): RFQ supports: • Attachments at the header-level and line item-level for new and change requestsfor quotations. • The size of the attachments for both inbound and outbound documents cannot exceed 100 MB. Attachments can additionally have a payload of up to 40 MB. • Text descriptions at the header-level and line-item level for internal and external users. • CIG also sends the currency of the target value in Quote Request document. When the currency is not available in the RFQ, CIG sends the company code currency. Ensure that the attached files have unique names and the names do not have blank spaces. When the outbound documents attachment URL contain special characters, buyers must ensure that: ü The attachment URL is encoded using the UTF-8 compliant ühttp:// is not encoded in the URL for attachments © SAP SE AR822 64 HOME Course Title @ Copyright. All rights reserved. Supported Flows: SAP Ariba Sourcing Integration Quote Message / Award: Quote Message is a reply to the Quote Request based on the best bid by a vendor. Quote Award is the best Quote identified & approved by Sourcing Manager for creating Purchase Order or Contract in SAP ECC. When RFQ / Quote Request is sent to Ariba Sourcing, suppliers bid on the sourcing event & Ariba Sourcing creates an award for the winning bid. Ariba Sourcing then sends the award as a Quote Message back to the SAP system. Based on the information in the Quote Message for the award, CIG creates either Purchase Order (PO); Framework Order (FO) or Contract (OLA) in the SAP system. SAP Ariba Cloud Integration Gateway sends a confirmation to SAP Ariba Sourcing after creating a PO; FO or OLA. 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 © SAP SE AR822 65 HOME Course Title @ Copyright. All rights reserved. Supported Flows: SAP Ariba Procurement Integration Master Data Purchase Requisition ERP-initiated Purchase Requisition Demand Aggregation for ERP- initiated Purchase Requisitions Work Order- Based ERP- initiated Purchase Requisitions Purchase Order Goods Receipt ERP-initiated Service Sheets Advance Payment Service Sheet Invoice Non PO Invoice Contract from Outline Agreements (OLA) © SAP SE AR822 66 HOME Course Title @ Copyright. All rights reserved. Supported Flows: SAP Ariba Procurement Integration Master Data Buyers using the Ariba Procurement solutions integrated with SAP System can do the following: • Import master data for Supplier; Supplier Location; Payment Terms; Remittance Location & User data between the Ariba Procurement solutions & SAP system. • Integrate master data directly from SAP System to Ariba Procurement solutions seamlessly. • Run the Incremental Load while running the master data events directly. • Integrate master data from SAP system to Ariba Procurement solutions in a Federated Process Control-enabled environments. Different types of master: • Supplier • User & User Groups • Enterprise Structure / Organizational Data – Purchase Organization, Plant, Company Code; Purchase Group, Plant Purchase Organization; etc. • Accounting Data – Asset, Cost Center; General Ledger; Internal Order; WBS Element; etc. • Cross/Application Configuration Data: Account Assignment Category; Account Category Field Status; ERP Commodity Code; Payment Terms; Tax Code; Currency Conversion; etc. • Funds Management Data (for Real Time Budget Check feature – SAP only). © SAP SE AR822 67 HOME Course Title @ Copyright. All rights reserved. Supported Flows: SAP Ariba Procurement Integration Purchase Requisition: This document is available for integration with your SAP system only if Real Time budget Check feature is enable on your Ariba Procurement Solutions. Ø It allows to check the available budget in your SAP system before the purchase requisition is approved. When the purchase requisition is approved, the procurement application creates a purchase order against the purchase requisition and sends it to suppliers. Ø The budget check functionality is available only for WBS elements, Internal Orders, Funds Management, and Grants Management in SAP ERP. • There are certain SAP Notes that need to be implemented & parameters to be enabled. • For Real Time Budget Check feature, certain configurations need to be maintained. • The details are available in SAP Ariba Cloud Integration Gateway Overview guide. © SAP SE AR822 68 HOME Course Title @ Copyright. All rights reserved. Supported Flows: SAP Ariba Procurement Integration ERP-initiated Purchase Requisition: • Buyers can create a Purchase Requisition for materials in SAP system & export it to SAP Ariba Procurement solutions. • Buyers can also delete or cancel the Purchase Requisition. • Buyers can do either full or incremental export of the Purchase Requisition to SAP Ariba Procurement solutions. • Full export would send only the new Purchase Requisitions that were not sent to SAP Ariba Procurement solutions. • Incremental export would include the Purchase Requisitions that were updated on ERP & any new requisitions that were created since the last date of export. • The export supports the following categories of Purchase Requisition: Ø Material Ø Limit • CIG supports Purchase Requisitions with only standard document type. • If the budget check is enabled, editing the same Purchase Requisition simultaneously on both SAP system &s SAP Ariba Procurement solutions could result in data loss. © SAP SE AR822 69 HOME Course Title @ Copyright. All rights reserved. Supported Flows: SAP Ariba Procurement Integration Demand Aggregation for ERP-initiated Purchase Requisitions: A demand aggregation for Purchase Requisitions combines multiple Purchase Requisitions into a single requisition. • To enable demand aggregation using CIG, configure the Aggregate Requisition option in the Interface Setup Program. • CIG supports demand aggregation of Purchase Requisitions created using Material Requirement Planning. When a demand aggregation request is submitted in SAP Ariba Procurement solutions, it deletes the individual Purchase Requisitions created using Material Requirement Planning & a consolidated Purchase Requisition is created. © SAP SE AR822 70 HOME Course Title @ Copyright. All rights reserved. Supported Flows: SAP Ariba Procurement Integration Work Order-Based ERP-initiated Purchase Requisitions: If the Plant Maintenance module is enabled in SAP system, you can use planned maintenance work orders to procure maintenance & repair services for your plants & machinery. • SAP system generate Purchase Requisitions for the items listed in the work orders. • The Work Order-Based Requisitions are sent to SAP Ariba Procurement solutions & flow to the procurement operations desk for approval by procurement operations desk agents. • To send work order-based requisitions to SAP Ariba Procurement solutions, select the Work Order Requisition option in the ARBCIG_BUY_PR_EXP export program. • Enable parameter Application.Purchasing.WorkOrderReqRfqSupport in SAP Ariba Procurement solutions. Also enable the procurement operations desk. © SAP SE AR822 71 HOME Course Title @ Copyright. All rights reserved. Supported Flows: SAP Ariba Procurement Integration Purchase Order: Buyers create a purchase order to request for product or services from suppliers. From Ariba Procurement solutions purchase order is sent to SAP system & upon approval the Ariba Procurement solutions would send it to Ariba Network. The following types of purchase orders are supported – Ø Standard Purchase Orders (New; Change, Cancel & Close) Ø Service Purchase Orders (New; Change, Cancel & Close) For amount-based purchase orders, the Ariba Procurement solutions map the amount to the quantity in SAP ERP, and sets the unit price to 1. Enable the following asynchronous integration events: ü Export Purchase Orders Asynchronously ü Import Purchase Order Status Asynchronously ü Export Change PurchaseOrders Asynchronously ü Import Change Purchase Orders Status Asynchronously ü Export Cancel Purchase Orders Asynchronously ü Import Cancel Purchase Order Status Asynchronously ü Import Purchase Order ERP Header Status Asynchronously Enable Export Purchase Order Close Status synchronous integration event for close purchase order. © SAP SE AR822 72 HOME Course Title @ Copyright. All rights reserved. Supported Flows: SAP Ariba Procurement Integration Purchase Order (continued…): • Buyers using Ariba Procurement solutions integrated with SAP system can also send Purchase Order closure information from SAP Ariba Procurement solutions to SAP System & vice versa. • Buyers need to ensure that the purchase order information in SAP Ariba Procurement solutions and SAP system is in sync to improve the fund allocation and utilization. • Upon receiving the PO closure information, SAP system releases any unused fund that was allocated for the purchase order and sets any open quantity to zero. • Buyers can specify a status while they close a purchase order. Status in SAP Ariba Procurement solutions Status in SAP ERP Order Closed for Receiving Delivery Complete Order Closed for Invoicing Final Invoice Order Closed for All Actions Delivery Complete and Final Invoice © SAP SE AR822 73 HOME Course Title @ Copyright. All rights reserved. Supported Flows: SAP Ariba Procurement Integration Purchase Order (continued…): Buyers can also send plant information from Ariba Procurement solutions to SAP system. • If you want to send plant information at line level in a Purchase Requisition or a Purchase Order, you must set the Application.Procure.AllowAdhocShipToAddress parameter to false in SAP Ariba Procurement solutions. • When Purchase Requisition or Purchase Order contains the SAP Plant Entity field, SAP Ariba Cloud Integration Gateway maps UniqueName field in the SAPPlant Cluster Root to the plant field in SAP ERP System. • If the Application.Procure.AllowAdhocShipToAddress parameter is set to true in SAP Ariba Procurement Solutions, you can enter the address manually for the Purchase Requisition or Purchase Order. In that case, SAP Ariba Cloud Integration Gateway maps the UniqueName field in the ShipTo field of Purchase Requisition or Purchase Order to the plant field in SAP ERP System. If the plant address is provided only at the header level of Purchase Requisition or Purchase Order, it is used in the ShipTo address field irrespective of the Application.Procure.AllowAdhocShipToAddress parameter is set to false. © SAP SE AR822 74 HOME Course Title @ Copyright. All rights reserved. Supported Flows: SAP Ariba Procurement Integration Purchase Order (continued…): • Buyers can send attachments & comments from SAP Ariba Procurement solutions to SAP system. • In SAP system, the attachments and comments are processed as follows: Ø Header level using the SAP Generic Object Services (GOS) for purchase orders. Ø Line level using the SAP Document Management System (DMS) for purchase orders. • The limit for the number of attachments per line item is 20 & the limit for combined attachment size is 100 MB. • Comments are supported for purchase orders at both the header and the line level to enter free form text that can be associated with a purchase order. Some of the important limitations – (For other limitations, please refer to the SAP Ariba Cloud Integration Gateway Overview guide. ü Zero value amount for line items in amount-based purchase orders not supported ü Header-level credit memos and line-level credit memos with tax code are not supported © SAP SE AR822 75 HOME Course Title @ Copyright. All rights reserved. Supported Flows: SAP Ariba Procurement Integration Goods Receipt: A receipt is an acknowledgment of the goods that have arrived. Ariba provided integration code integrates receipts as goods receipts with Movement Type as 101. • Buyers can create a negative receipt in the Ariba Procurement solutions to reverse some received quantity as a result of incorrect shipment or manual errors. Ariba provided integration code integrates negative receipts as goods receipts with Movement Type as 102. • For amount-based receipts, the Ariba integration code maps the amount to the quantity in SAP system, and sets the price to 1. In a receipt, if you have both accepted quantity and rejected quantity, only accepted quantity is integrated with the SAP ERP system. All rejected quantities are ignored. Enable the following Asynchronous Integration events: ü Export Receipts Asynchronously ü Import Receipt Status Asynchronously © SAP SE AR822 76 HOME Course Title @ Copyright. All rights reserved. Supported Flows: SAP Ariba Procurement Integration ERP-initiated Service Sheets: You can create & send Service Entry Sheets from SAP system on behalf of a supplier. • The approved Service Entry Sheets are then sent to SAP Ariba Procurement solutions. • The feature accelerates the process of Service Procurement as buyers do not have to wait for the supplier to send the Service Entry Sheet. • You need to enable Load External SES in Ariba Buying in SAP Ariba Procurement solutions. • Only approved Service Entry Sheets in SAP system are sent to SAP Ariba Procurement solutions. However, editing or deletion of ERP-initiated Service Entry Sheets is not supported. • ERP-initiated Service Entry Sheets with hierarchy are not supported. © SAP SE AR822 77 HOME Course Title @ Copyright. All rights reserved. Supported Flows: SAP Ariba Procurement Integration Advance Payment: This transaction enables buyers to make advance payments for a purchase order to a supplier. • Ariba Procurement solutions sends fully approved advance payment request documents to the SAP system to process the payments. • The SAP system sends a confirmation to Ariba Procurement solutions when the advance payment is successfully processed. Ø The advance payment amount can be adjusted against the invoice during invoice reconciliation. There are certain SAP Notes & BAdIs need to be implemented. The details are available in SAP Ariba Cloud Integration Gateway Overview guide. Only purchase order based advance payments are supported. An advance payment referencing multiple purchase orders is not supported. Enable the following Asynchronous Integration events: Ø Export Advance Payments Asynchronously Ø Import Advance Payment Status Asynchronously Ø Export Cancel Advance Payments Asynchronously Ø Import Cancel Advance Payment Status Asynchronously © SAP SE AR822 78 HOME Course Title @ Copyright. All rights reserved. Supported Flows: SAP Ariba Procurement Integration Service Sheet: Suppliers create service sheets to describe the service they are offering. Service sheets can contain both service and material goods lines. You can create a service sheet for one or more service lines on an associated service order & send it to the SAP System. • Buyers on the SAP Ariba Procurement solutions can create: Ø Service Sheets without hierarchy. Ø Service Sheets containing planned and unplanned service lines. Ø Service Sheets with accounting splits on single & multiple service lines- both on parent line (split in the Limits tab) and child line. • SAP system sends a response in the form of either approval (with Service Sheet number) or revocation. The following are not supported on the SAP Ariba Procurement solutions: ü Service sheets with hierarchy ü Attachments ü Comments ü Modifying Account Assignment Category during service sheet creation Enable the following Asynchronous Integration events: ü Export Service Sheets Asynchronously ü Import Service Sheets Response Asynchronously © SAP SE AR822 79 HOME Course Title @ Copyright. All rights reserved. Supported Flows: SAP Ariba Procurement Integration Invoice: Invoices can be sent by suppliers on Ariba Network to buyers on Ariba Procurement Solutions or can be directly created by buyers within Ariba Procurement solutions. After reconciliation, these invoices are exported/ sent to SAP system. The following types of invoices are supported: Ø PO-based Invoice Ø Non-PO Invoice Ø Service Invoice Ø Line Level Credit Memo Ø Header Level Credit Memo Enable the following Asynchronous Integration events: ü Export Payment Requests Asynchronously ü Import Payment Requests Status Asynchronously © SAP SE AR822 80 HOME Course Title @ Copyright. All rights reserved. Supported Flows: SAP Ariba Procurement Integration Invoice (continued): The following discount scenarios are supported: Ø Discounts entered at the header and line-level on a PO based invoice. Ø Discounts entered at header and line-level on a non-PO based invoice. Ø Discounts entered at header and line on a line-level credit memo. Shipping & Handling Charges are sent to SAP system: Ø Shipping & handling charges with taxes – as service lines for direct posting to General Ledger (G/L) accounts. Ø Shipping & handling charges – as unplanned delivery cost. Attachments: Processed only at header level using the SAP Generic Object Services (GOS). Some of the important limitations: • Parked invoices are not supported. • Comments are not supported for invoices. • Assets as an account assignment category is not supported for non-PO based invoice. • Attachments at the line level are not supported for invoices. • Refer SAP Ariba Cloud Integration Gateway Overview guide for further limitation details. © SAP SE AR822 81 HOME Course Title @ Copyright. All rights reserved. Supported Flows: SAP Ariba Procurement Integration Non PO Invoice The following are supported: Ø Non-PO FI Invoice Ø Withholding Tax in Non-PO FI Invoice Ø Non-PO FI Invoice for One-Time Vendor Some of the important limitations: • Comments are not supported for invoices. • The withholding tax is not supported at the line item level. • Refer SAP Ariba Cloud Integration Gateway Overview guide for further limitation details. FI – SAP’s Finance module – used for all accounting processes; this module integrates with CIG buy-side. © SAP SE AR822 82 HOME Course Title @ Copyright. All rights reserved. Supported Flows: SAP Ariba Procurement Integration Contract from Outline Agreements (OLA): Contracts from Outline Agreements, Purchase Requisition or Request For Quotation containing service items (SAP Item Category D items) that have multiple-level hierarchy on their SAP system can be sent to Ariba Procurement solutions via CIG. You can export contract to the SAP Ariba Procurement solutions for the following: Ø Single Line Contracts Ø Multiple Line Contracts Ø Service Line Contracts Ø Contracts containing Split-Accounting Ø Contracts containing Tiered Pricing Ø Contracts containing Term Pricing © SAP SE AR822 83 HOME Course Title @ Copyright. All rights reserved. Supported Flows: Master Data Native Integration (MDNI) This feature currently supports only full load export of the following master data objects: Ø Company Codes Ø Cost Centers Ø Plant Ø Asset / Asset Class Ø Material Group Ø Purchasing Organizations Ø Exchange Rate Ø Purchasing Group Ø Internal Order Ø Currency Ø Plant Purchasing Organization Ø Tax Code Ø Payment Terms Ø Account Assignment Category Ø General Ledger Account © SAP SE AR822 84 HOME Course Title @ Copyright. All rights reserved. Supported Flows: Ariba Guided Buying Integration with S/4 HANA Cloud (2NV) • Master Data* • Purchase Requisition • Purchase Orders • Goods Receipts / Service Entry Sheets • Invoice / Payment Requests *Master Data integration for Guided Buying is not supported via CIG. Instead the Master Data is sent via the microservice Ariba MDNI (Master Data Native Interfaces). © SAP SE AR822 85 SAP Ariba Cloud Integration Gateway Buy Side Overview – Supported Flows – Ariba Network Integration with S/4 HANA Cloud (42K) © SAP SE AR822 86 HOME Course Title @ Copyright. All rights reserved. SAP Ariba Cloud Integration Gateway Buy Side Overview – Supported Flows – Ariba Network Integration with S/4 HANA Cloud (42K) ü Request for Quotation ü Purchase Orders ü Order Confirmation ü Advance Ship Notice ü Goods Receipt / Service Entry Sheet ü Invoice ü Invoice Status Update ü Payment / Remittance © SAP SE AR822 87 SAP Ariba Cloud Integration Gateway Buy Side Overview – Supported Flows – SAP Ariba Sourcing Integration with S/4 HANA Cloud (4BL) © SAP SE AR822 88 HOME Course Title @ Copyright. All rights reserved. SAP Ariba Cloud Integration Gateway Buy Side Overview – Supported Flows – SAP Ariba Sourcing Integration with S/4 HANA Cloud (4BL) ü Request for Quotation / Quote Request ü Quote Message / Award © SAP SE AR822 89 SAP Ariba Cloud Integration Gateway Buy Side Overview – Supported Flows – SAP Ariba Contracts Integration with S/4 HANA Cloud (4AZ) © SAP SE AR822 90 HOME Course Title @ Copyright. All rights reserved. SAP Ariba Cloud Integration Gateway Buy Side Overview – Supported Flows – SAP Ariba Contracts Integration with S/4 HANA Cloud (4AZ) ü Contract / Scheduling Agreement ü Contract Status Update © SAP SE AR822 91 SAP Ariba Cloud Integration Gateway Buy Side Overview – Supported Flows – SAP Ariba Guided Buying Integration with S/4 HANA Cloud via Central Procurement (3EN) © SAP SE AR822 92 HOME Course Title @ Copyright. All rights reserved. SAP Ariba Cloud Integration Gateway Buy Side Overview – Supported Flows – SAP Ariba Guided Buying Integration with S/4 HANA Cloud via Central Procurement (3EN) ü Purchase Requisition ü Purchase Orders ü Goods Receipts / Service Entry Sheets ü Invoice / Payment Requests © SAP SE AR822 93 SAP Ariba Cloud Integration Gateway Buy Side Overview – Supported Flows – SAP Ariba Contracts Integration with S/4 HANA Cloud via Central Procurement (4BO) © SAP SE AR822 94 HOME Course Title @ Copyright. All rights reserved. SAP Ariba Cloud Integration Gateway Buy Side Overview – Supported Flows – SAP Ariba Contracts Integration with S/4 HANA Cloud via Central Procurement (4BO) ü Contract ü Purchase Order © SAP SE AR822 95 SAP Ariba Cloud Integration Gateway Unsupported Flows © SAP SE AR822 96 HOME Course Title @ Copyright. All rights reserved. SAP Ariba Cloud Integration Gateway Unsupported Flows • Network Integration: ü Payment remittance using Payment Integration Toolkit (PITK) • Sourcing Integration: ü SAP Ariba Supplier Information and Performance Management (SIPM) ü Requests for Quotations (RFQs) via the Fiori UI (using SAP S/4 HANA on-prem) • Procurement Integration: ü File Channel transactional data integration for SAP Ariba Procurement solutions ü Expense Report SAP Ariba Spend Analysis © SAP SE AR822 97 LOGO HERE @ Copyright. All rights reserved. Integration Add-Ons © SAP SE AR822 98 LOGO HERE @ Copyright. All rights reserved. About This Lesson @ Copyright. All rights reserved. Lesson 1: Add-on Definition and Benefits By the end of this lesson, you will be able to: • Describe the benefits of using AddOn This lesson includes the following topics: i. AddOn Definition ii. AddOn Benefits © SAP SE AR822 99 LOGO HERE @ Copyright. All rights reserved. Add-On Defined Definition: An add-on is an SAP application that is technically dependent on and can only be installed on top of another application. Software solutions developed on SAP systems are delivered to the customer as add-ons. In this unit, we will focus on learning about this specific add-on: SAP Ariba Cloud Integration Gateway add-on for SAP ERP © SAP SE AR822 100 LOGO HERE @ Copyright. All rights reserved. AddOn Benefits CIG add-on for SAP ERP – the facts: ü Aligned with overall SAP strategy and standard processes ü Same solution works for SAP ERP and S/4HANA, as well as Ariba Network and SAP Ariba solutions ü Easy configuration via SPRO ü Easy to customize ü Heavy processing is moved to SAP Ariba Cloud Integration Gateway ü No deployment of PI / PO content needed. (Except for mediated connectivity) ü Smooth upgrade / update for the customers with Software Update Manager ü Easy monitoring ü Automatic
More content from this subject
Why Small Practices Benefit from Medical Billing Services- A Complete Guide to the IAPP CIPT Exam
- Osta ekologisk ullmatta netistä _ SE Mattor
- Trusted Medical Billing Company to Maximize Your Practice Revenue
- C_ACTIVATE05-demo
- EX442 Dumps with Comprehensive Answer Indicators - Study Savvy
- Refine Your Preparation with the Benefit of EX183 Dumps PDF
- EX403 Dumps with Exhaustive Answer Answers - Ready Wiser
- EX436 Dumps with Itemized Answer Guides - Train Savvy
- Get Ready for AACE International CCP Certification with Verified Questions Dumps
- Free GitHub-Foundations Actual Exam Questions [2024]