Text Material Preview
© SAP SE AR822 1 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 HOME Course Title LOGO HERE @ Copyright. All rights reserved. Transactional Data Integration Supplier Lifecycle Performance (SLP) Integration 1 Procurement Transactions Integration Sourcing Transactions Integration 3 2 © SAP SE AR822 2 3© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ Supplier Lifecycle Performance (SLP) Integration © SAP SE AR822 3 HOME Course Title LOGO HERE @ Copyright. All rights reserved. About This Lesson @ Copyright. All rights reserved. Lesson 1: Overview By the end of this lesson, you will be able to: • Recognize architecture scenarios/flows • Describe what a Unified Vendor Model is • Identify standard services for supplier data integration This lesson includes the following topics: i. Architecture scenarios ii. Unified Vendor Model iii. Supplier data standard services © SAP SE AR822 4 HOME Course Title @ Copyright. All rights reserved. Overview SAP Ariba Supplier Lifecycle and Performance integration to SAP ERP and SAP S/4HANA architecture scenarios Scenario 1 Scenario 2 Updates © SAP SE AR822 5 HOME Course Title @ Copyright. All rights reserved. Overview Unified Vendor Model (UVM) The UVM provides a common Webservices(MDG) format for SAP Applications. ü Buyers can use the Unified Vendor Model to integrate Business Partner & Vendor Master Data between the ERP>>>Master Data Governance (MDG)>>>Supplier Lifecycle Performance (SLP), using CIG. ü The integration allows you to replicate Vendor Master Data in ERP & SLP. ü Buyers can integrate Supplier Organization data with ERP by using the direct-connectivity integration method or by using a middleware. ü The integration between SLP, ERP & MDG is bi-directional and enables you to replicate Vendor Master Data as Business Partners in ERP & SLP. ü The outbound integration from ERP to SLP is achieved through Business Partner interfaces provided by MDG & standard SAP programs such as DRF programs. ü Transaction code DRFOUT is used for initial replication of Business Partners from ERP to SLP. © SAP SE AR822 6 HOME Course Title @ Copyright. All rights reserved. Overview Inbound & outbound Supplier data can be integrated using the following standard services: Ø BusinessPartnerSUITEBulkReplicateRequest_In Ø BusinessPartnerSUITEBulkReplicateRequest_Out Ø BusinessPartnerSUITEBulkReplicateConfirmation_In Ø BusinessPartnerSUITEBulkReplicateConfirmation_Out © SAP SE AR822 7 HOME Course Title LOGO HERE @ Copyright. All rights reserved. About This Lesson @ Copyright. All rights reserved. Lesson 2: Integration Prerequisites By the end of this lesson, you will be able to: • Identify the integration prerequisites for varied situations and solutions. This lesson includes the following topics: i. Common Prerequisites ii. Prerequisites for Existing Customers iii. Prerequisites for SLP iv. Prerequisites for CIG v. Prerequisites for SAP System © SAP SE AR822 8 HOME Course Title @ Copyright. All rights reserved. Integration Prerequisites: common prerequisites Minimum software requirements – ü SAP EHP6 for SAP ERP 6.0 with non-SAP S/4HANA database (SAP_APPL 606 SP05) ü SAP EHP6 for SAP ERP 6.0 with SAP S/4HANA database (SAP_APPL 606 Minimum supported version) ü SAP Business Suite Foundation 731 is a combination of ERP6+ CRM+ SCM +PLM + SRM © SAP SE AR822 9 HOME Course Title @ Copyright. All rights reserved. Integration Prerequisites: Common prerequisites Configure the MDG or DRF integration for suppliers: • Enable business functions to replicate MDG-S function. • Setup Customer Vendor Integration (CVI), define a replication model and assign target system for the replication model or outbound implementation. CVI helps in replicating the Vendor/Customer as Business Partner and vice-versa. Once CVI is configured, whenever there is a new entry in Vendor master we will automatically have an entry created as Business Partner. MDG is a centralized system to manage supplier data from different systems. DRF is a framework used for data replication to external system, and here we are using same to send supplier data to SLP. © SAP SE AR822 10 HOME Course Title @ Copyright. All rights reserved. Integration Prerequisites: for existing customers An existing SM customer using SAP Ariba cloud integration release 9.0 and earlier, ensure that you do the following – Ø Disable the polling client /ARBA/CO_POLLING_CLIENT_REQRES Ø Disable the two standard proxies for the URL access path: • CO_MDG_BP_RPLCTRQ for outbound supplier data integration from SAP ERP • CO_MDG_BP_RPLCTCO for outbound confirmations from SAP ERP You no longer need the table /ARBA/SM_SEQNUM to integrate SM with CIG /ARBA/CO_POLLING_CLIENT_REQRES • To fetch supplier records from SM, the ERP first sends the request using DC and then supplier records are pulled from SM to ERP using a pulling mechanism. • Previously the pulling mechanism was used to pull the data from SAP Ariba; similar to a Pending queue concept in which Supplier records were pulled from SAP Ariba. However, this was not real time. • Now it is a push only mechanism that uses Cloud Connector and records are updated in real-time. (Customers can also use PI). © SAP SE AR822 11 HOME Course Title @ Copyright. All rights reserved. Integration Prerequisites: for Supplier Lifecycle Performance (SLP) In SLP we have the option of onboarding suppliers in bulk using an Excel file import functionality. (Optional) To use mass registration invitation waves to onboard existing suppliers to SLP, So once those waves are created, specify how the suppliers in them will be synchronized to ERP ü Contact your SAP Ariba Customer Support representative for the following: Ø Configure the site ID and enable the integration of supplier data for your SLP ü Set up the ERP system credentials in SLP ü Specify how and when suppliers created in SLP are first synchronized to ERP ü (Optional) To validate approved supplier requests in MDG-S and check for duplicates before suppliers are created in SLP, set up the MDG-S validation and approval requirement ü (Optional) To use MDG approval processes to require approval of supplier changes made in SLP or in ERP as well, set up the ERP approval requirement © SAP SE AR822 12 HOME Course Title @ Copyright. All rights reserved. Integration Prerequisites: for Cloud Integration Gateway (CIG) SAP Ariba Supplier Lifecycle and Performance requires the following document types in the Document Type page on the SAP Ariba Cloud Integration Gateway portal:– ü BusinessPartnerSUITEReplicateRequest ü BusinessPartnerSUITEReplicateConfirmation © SAP SE AR822 13 HOME Course Title @ Copyright. All rights reserved. Integration Prerequisites: for SAP System ü Configure and set-up the following connections in order to send and receive the supplier data from CIG – Ø Outbound transaction messages sent to CIG • SLP Confirmation Out Request • SLP Outbound Request Ø Inbound transaction messages sent from CIG • SLP Confirmation In Request • SLP Inbound Request ü If you want to use the certificate-based authentication, configure the digital certificates/keys and provide the necessary authorizations. ü If you want to customize the supplier information, see the section, Configuring SAP Process Integration in the SAP Ariba Cloud Integration Gateway configuration guide. © SAP SE AR822 14 HOME Course Title LOGO HERE @ Copyright. All rights reserved. About This Lesson @ Copyright. All rights reserved. Lesson 3: Supplier Lifecycle (SLP) Flow By the end of this lesson, you will be able to: • Complete configuration for SLP in different configuration scenarios such as in SLP, in CIG, and in SAP System. This lesson includes the followingAll rights reserved. 2.1 RFQ Flows: Configure in SAP System - Transaction Specific Settings (TSS) Activity iii. Implement a Customer Exit for Request for Quotation To implement customer exit for RFQ (continued) – 11. Go back & click Components, then double-click the enhancement EXIT_SAPLEINM_011 12. In the next screen that appears, double-click INCLUDE ZXM06U33, press Enter © SAP SE AR822 105 HOME Course Title @ Copyright. All rights reserved. 2.1 RFQ Flows: Configure in SAP System - Transaction Specific Settings (TSS) Activity iii. Implement a Customer Exit for Request for Quotation To implement customer exit for RFQ (continued) – 13. Copy & paste the code INCLUDE arbcig_quote_request_011, click Activate 14. Go back & Activate the user exit also. © SAP SE AR822 106 HOME Course Title @ Copyright. All rights reserved. 2.1 RFQ Flows: Configure in SAP System - Transaction Specific Settings (TSS) Activity iv. Configure the SRVMAPKEY for Service RFQ Buyer users need to configure this setting only if the Service RFQ transfer from SAP System to Ariba Network fails. • This usually occurs when the business function LOG_MM_P2PSE_1 is not active on your SAP System. • Users need to implement the SAP Note 2372821 only if the standard field SRVMAPKEY is not activated on your SAP System. • The standard field SRVMAPKEY in the SAP Table ESLL stores Service PO Item ID information. • The service map key is required to identify the line numbers for the service lines. • If the SRVMAPKEY is not available, the Item ID does not populate the line numbers for the service lines correctly & the integration will fail. © SAP SE AR822 107 HOME Course Title @ Copyright. All rights reserved. 2.2 RFQ Flows: Configure in CIG In this section, user needs to perform following activities. All these are discussed in CIG Configuration session. Here we will focus on only those configurations in CIG which are very specific to RFQ integration: • Enable CIG for your Ariba Sourcing Realm. • Provide Basic Information in the project in CIG for “Product = Ariba Sourcing”. • Define Connection information to establish connectivity between CIG & your SAP system. • Define Cross Reference for Parameter for RFQ (Doc Type – QuoteRequest) • Define Cross References for UOM. • Define Cross References for Lookup Table. • Review project configuration & Confirm the Project. • Test the Project. • Deploy the Project. © SAP SE AR822 108 HOME Course Title @ Copyright. All rights reserved. 2.2 RFQ Flows: Configure in CIG To define values in parameters: 1. Select the Document Type = QuoteRequest in Parameters tab, click Add 2. Edit the entry 3. Enter values for the parameters in the TEST Environment and PROD Environment & click Save. If you want to have different value in PROD Environment, uncheck the box Use same values. 4. Enter parameter values for another Document Type as needed or click Next. In this section you need to define values in the parameter fields which you want to map. • The transactions & the related parameters are added by the administrator. • You can define the values for both test & production environments. © SAP SE AR822 109 HOME Course Title @ Copyright. All rights reserved. 2.2 RFQ Flows: Configure in CIG To maintain fields that support more than one value in the Cross Reference Lookup table of the CIG: 1. Select the Document Type = QuoteRequest in Lookup Table tab 2. Edit the Lookup Value field: QuoteRequestMatchingType 3. Enter values for the fields in the TEST Environment and PROD Environment & click Save 4. Enter Lookup Values for another Document Type as needed or click Next. In this section you need to define lookup values which you want to map. Users need to maintain certain fields that Ariba requires for document types per transaction. SAP Ariba recommends that you maintain fields that support more than one value in the Cross Reference Lookup table of the CIG. © SAP SE AR822 110 HOME Course Title @ Copyright. All rights reserved. 2.3 RFQ Flows: Configure in Ariba Network RFQ Flows - Configure in Ariba Network PRE-REQUISITES ü This particular set of activities are performed by Ariba Customer Support either during the activation of AN Buyer Account or at the time of enabling new solution for customer. ü Customers need to contact Ariba Custom Support when they are ready to adopt the solution ACTIVITIES (I-V) AN Admin Activities I. Enable Open Network & Enable End Point II. Enable Multi ERP (if you are using Multi-ERP setup) III. Enable Quote Automation (only if you want to send RFQ to Ariba Discovery) AN Buyer Account Admin Activities IV.Define System IDs & End Point IDs V. Configure Document Routing © SAP SE AR822 111 HOME Course Title @ Copyright. All rights reserved. 2.3 RFQ Flows Configure in Ariba Network Activity I: Ariba Network Admin - Enable Open Network & Enable End Point RFQ integration from SAP System to Ariba Sourcing is realized via Ariba Network. Thus, in order to route the RFQ (QuoteRequest) document to SAP Ariba Sourcing, an End Point needs to be defined. In Ariba Network, to define End Point, the particular Buyer Account needs to be enabled for Open Network. © SAP SE AR822 112 HOME Course Title @ Copyright. All rights reserved. 2.3 RFQ Flows Configure in Ariba Network Activity I: Ariba Network Admin - Enable Open Network & Enable End Point Once the Buyer Account is enabled for Open Network, Business End Points (cXML and OData Setup) link will be available to define End Points. © SAP SE AR822 113 HOME Course Title @ Copyright. All rights reserved. 2.3 RFQ Flows: Configure in Ariba Network Activity II: Ariba Network Admin - Enable Multi ERP (if you are using Multi-ERP setup) If you are using Multi ERP setup, you would need to define backend System IDs to route the documents to the respective SAP System. In Ariba Network, to define System ID, the particular Buyer Account needs to be enabled for Multi ERP. For this purpose also, enablement of Open Network is required. © SAP SE AR822 114 HOME Course Title @ Copyright. All rights reserved. 2.3 RFQ Flows: Configure in Ariba Network Activity II: Ariba Network Admin - Enable Multi ERP (if you are using Multi-ERP setup) Once the Buyer Account is enabled for Multi ERP, Business Application IDs and End Points (cXML and OData Setup) link will be available to define System IDs & End Points. © SAP SE AR822 115 HOME Course Title @ Copyright. All rights reserved. 2.3 RFQ Flows: Configure in Ariba Network Activity III: Ariba Network Admin - Enable Quote Automation (only if you want to send RFQ to Ariba Discovery) If you wish to use Ariba Discovery capabilities for sourcing process, you can route the RFQ documents to Ariba Discovery instead of SAP Ariba Sourcing. To achieve that, in Ariba Network, the particular Buyer Account needs to be enabled for Quote Automation. © SAP SE AR822 116 HOME Course Title @ Copyright. All rights reserved. 2.3 RFQ Flows: Configure in Ariba Network Activity IV: Ariba Network Buyer Account Admin - Define System IDs & End Point IDs If you are using Multi ERP setup, once the required setup is enabled for your Buyer Account, you would need to define backend System IDs & End Point IDs to route the documents to the respective applications – Ariba Sourcing or SAP System. To define System IDs & End Point IDs: 1. Login to you’re an Buyer Account & click Administration 2. Click Configuration 3. Click on Business Application IDs and End Points (cXML and OData Setup) link – The Configure Business Applications IDs page appears. © SAP SE AR822 117 HOME Course Title @ Copyright. All rights reserved. 2.3 RFQ Flows: Configure in Ariba Network Activity IV: Ariba Network Buyer Account Admin - Define System IDs & End Point IDs To define System IDs & End Point IDs (continued): 4. Click on Create button – the Create a System ID page appears. 5. Provide required details & click Save. Please note that The System ID field should be filledwith the system ID value exactly matching with your backend system ID value. © SAP SE AR822 118 HOME Course Title @ Copyright. All rights reserved. 2.3 RFQ Flows: Configure in Ariba Network Activity IV: Ariba Network Buyer Account Admin - Define System IDs & End Point IDs To define System IDs & End Point IDs (continued): 6. To define End Point, click System ID under List of System IDs – the Manage Business Application ID: page appears. 7. Click End Point © SAP SE AR822 119 HOME Course Title @ Copyright. All rights reserved. 2.3 RFQ Flows: Configure in Ariba Network Activity IV: Ariba Network Buyer Account Admin - Define System IDs & End Point IDs To define System IDs & End Point IDs (continued): 8. Click Create 9. Create 2 End Points as mentioned in the below: • Create End Point to route the RFQ documents to Ariba Sourcing & provide following information: • End Point ID: Ariba • Select an Integration Type: Select cXML • Select an Authentication Method: Shared Secret or Certificate • Post URL: URL of Ariba Sourcing application suffixed by Buyer AN ID • Tick the Yes, I want to receive documents through the POST method instead of through the cXML GetPending method check box. • Click Save. © SAP SE AR822 120 HOME Course Title @ Copyright. All rights reserved. 2.3 RFQ Flows: Configure in Ariba Network Activity IV: Ariba Network Buyer Account Admin - Define System IDs & End Point IDs To define System IDs & End Point IDs (continued): 9. Create 2 End Points as mentioned in the below…(continued…): • Create End Point to route the Quote Message / Award & Contract documents to your backend SAP System & provide following information: • End Point ID: CIG • Select an Integration Type: Select cXML • Select an Authentication Method: Shared Secret or Certificate • Post URL: URL of CIG • (TEST – https://testacig.ariba.com/http/receiveCXML or PROD - https://acig.ariba.com/http/receiveCXML) • Tick the Yes, I want to receive documents through the POST method instead of through the cXML GetPending method check box. • Click Save. The Shared Secret or Certificate should match with that provided in Ariba Sourcing site profile © SAP SE AR822 121 HOME Course Title @ Copyright. All rights reserved. 2.3 RFQ Flows: Configure in Ariba Network Activity IV: Ariba Network Buyer Account Admin - Define System IDs & End Point IDs To define System IDs & End Point IDs (continued): 10. Click Done. You will be navigated to Configure Business Applications IDs page. 11. Click Save. You will be navigated to Configuration page. © SAP SE AR822 122 HOME Course Title @ Copyright. All rights reserved. 2.3 RFQ Flows: Configure in Ariba Network Activity IV: Ariba Network Buyer Account Admin - Define System IDs & End Point IDs To define System IDs & End Point IDs (continued): 12. Click Done © SAP SE AR822 123 HOME Course Title @ Copyright. All rights reserved. 2.3 RFQ Flows: Configure in Ariba Network Activity V: Ariba Network Buyer Account Admin - Configure Document Routing Once System IDs & End Point IDs are defined, you need to Configure Document Routing to define which End Point the particular document should be sent to – SAP Ariba Sourcing or SAP System. To configure Document Routing: 1. Login to your AN Buyer Account, click Administration & Configuration 2. Click on Business Application IDs and End Points (cXML and OData Setup) – the Configure Business Applications IDs page appears. 3. Click the System ID for which you want to configure document routing – the Manage Business Application ID: page appears. © SAP SE AR822 124 HOME Course Title @ Copyright. All rights reserved. 2.3 RFQ Flows: Configure in Ariba Network Activity V: Ariba Network Buyer Account Admin - Configure Document Routing To configure Document Routing (continued): 4. Click End Point 5. Click on Configure Document Routing – the Configure Document Routing page appears. © SAP SE AR822 125 HOME Course Title @ Copyright. All rights reserved. 2.3 RFQ Flows: Configure in Ariba Network Activity V: Ariba Network Buyer Account Admin - Configure Document Routing To configure Document Routing (continued): 6. .Select End Point from the drop down list for following documents: • Request for Quotations • Quotes • Contract Request • Contract Status Update Request 7. Click OK. © SAP SE AR822 126 HOME Course Title @ Copyright. All rights reserved. 2.4 RFQ Flows: Configure in SAP Ariba Sourcing In this section, user needs to perform following activity. Here we will focus on only those configurations in Ariba Sourcing which are very specific to RFQ integration: Enable Sourcing ERP Integration This is a prerequisite to all the transaction documents flowing from and to SAP Ariba Sourcing. • This task will enable ERP integration for Sourcing projects. If you have not ran this Scheduled Task, integration to SAP Ariba Sourcing will fail. • This task ensures that all cXML QuoteRequest documents received in Ariba Sourcing are treated as sourcing requests rather than Spot Quote events. • Users need to contact Ariba Customer Support to complete this activity. © SAP SE AR822 127 HOME Course Title @ Copyright. All rights reserved. About This Lesson @ Copyright. All rights reserved. Lesson 3. Quote Message / Award Flows By the end of this lesson, you will be able to: • Describe the Quote Message Configurations and flow. This lesson is made up of 3 sub-sections: 3.1 SAP Ariba Sourcing: Define Enumerations 3.2 Ariba Network: Cross reference / parameter 3.3 CIG: Cross reference / parameter 3.4 SAP System © SAP SE AR822 128 HOME Course Title @ Copyright. All rights reserved. 3. Quote Message / Award Flows Quote Message / Award: When suppliers bid on the Sourcing Event & SAP Ariba Sourcing creates an Award for the winning bid, SAP Ariba Sourcing sends the Award as a QuoteMesage back to the SAP System. • Based on the information in the QuoteMesage for the award, CIG creates either a Purchase Order or a Contract (Outline Agreement) on the SAP System. • If the Award contains the reference Document Type as framework order & the Document Category as FO, CIG creates a Purchase Order of Framework Order type with the Validity Start & Validity End dates on the SAP System. • To create a Purchase Order or a Framework Order, users need to maintain the Cross Reference Parameter in CIG. © SAP SE AR822 129 HOME Course Title @ Copyright. All rights reserved. 3. Quote Message / Award Flows SAP Ariba Cloud Integration Gateway sends a confirmation to SAP Ariba Sourcing after creating a PO; FO or Contract. The confirmation message contains the following information: ü SAP Contract ID & Date ü SAP PO ID & Date ü Sourcing Event ID ü Vendor ID ü Status Code – 200 (Received successfully) or 503 (Failure) ü Status Text – Success or Failure © SAP SE AR822 130 HOME Course Title @ Copyright. All rights reserved. 3.1 Quote Message / Award Flows: SAP Ariba Sourcing: Define Enumerations Quote Message / Award Flows: SAP Ariba Sourcing: Define Enumerations This is required to define whether the Quote Message should be consumed in SAP System as a Purchase Order or a Contract. • Users need to contact Ariba Customer Support to get this activity done. © SAP SE AR822 131 HOME Course Title @ Copyright. All rights reserved. 3.1 Quote Message / Award Flows: SAP Ariba Sourcing: Define Enumerations Quote Message / Award Flows: SAP Ariba Sourcing: Define Enumerations The file ariba.sourcing.integration.documenttype.xls will define the Document Type ü Purchase Order (F) ü Contract (K) The Excel file downloaded from Ariba Sourcing Admin site needs to filled in with these values & then will be uploaded for the specific customer realm. Enumeration Display Value Value ariba.sourcing.integration.documenttype @aml.sourcing.RFxExt/PODocumentTypeLabel F ariba.sourcing.integration.documenttype @aml.sourcing.RFxExt/ContractDocumentTypeLabel K © SAP SE AR822 132 HOME Course Title @Copyright. All rights reserved. 3.1 Quote Message / Award Flows: SAP Ariba Sourcing: Define Enumerations Quote Message / Award Flows: SAP Ariba Sourcing: Define Enumerations The file ariba.sourcing.integration.documentcategory.xls will define the Document Category ü Value Contract (WK) ü Material Contract (MK) ü Standard Purchase Order (NB) ü Framework Order (FO) The Excel file downloaded from Ariba Sourcing Admin site needs to filled in with these values & then will be uploaded for the specific customer realm. Enumeration Display Value Value ariba.sourcing.integration.documentcategory @aml.sourcing.RFxExt/WKDocumentCategoryLabel WK ariba.sourcing.integration.documentcategory @aml.sourcing.RFxExt/MKDocumentCategoryLabel MK ariba.sourcing.integration.documentcategory @aml.sourcing.RFxExt/NBDocumentCategoryLabel NB ariba.sourcing.integration.documentcategory @aml.sourcing.RFxExt/NBDocumentCategoryLabel FO © SAP SE AR822 133 HOME Course Title @ Copyright. All rights reserved. 3.2 Quote Message / Award Flows: Ariba Network: Cross reference / parameter Quote Message / Award Flows: Ariba Network: Cross reference / parameter There is no configuration required in Ariba Network specific to Quote Message / Award integration from SAP Ariba Sourcing to SAP System. © SAP SE AR822 134 HOME Course Title @ Copyright. All rights reserved. 3.3 Quote Message / Award Flows: configuration in CIG –Cross Reference Configuration – Parameter Quote Message / Award Flows: in CIG In this section, user needs to perform following activities. All these are discussed in CIG Configuration session. Here we will focus on only those configurations in CIG which are very specific to QM / Award integration: ü Enable CIG for your Ariba Sourcing Realm. ü Provide Basic Information in the project in CIG for “Product = Ariba Sourcing”. ü Define Connection information to establish connectivity between CIG & your SAP system. ü Define Cross Reference for Parameter for either of following: Ø Quote Message for Purchase Order (Doc Type – QuoteMessageOrder) Ø Quote Message for Material Contract (Doc Type – QuoteMessageContract) Ø Quote Message for Service Contract (Doc Type – QuoteMessageContractServices) ü Review project configuration & Confirm the Project. ü Test the Project. ü Deploy the Project. © SAP SE AR822 135 HOME Course Title @ Copyright. All rights reserved. In this section you need to define values in the parameter fields which you want to map. The transactions & the related parameters are added by the administrator. You can define the values for both test & production environments. Follow these steps to define parameters: 1. Select the Document Type = QuoteMessageOrder (for example) in “Parameters” tab & click Add. 2. Edit the entry. 3. Enter values for the parameters in the TEST Environment and PROD Environment & click Save. If you want to have different value in PROD Environment, uncheck the box Use same values. 4. Enter parameter values for another Document Type as needed or click Next. 3.3 Quote Message / Award Flows: configuration in CIG –Cross Reference Configuration – Parameter © SAP SE AR822 136 HOME Course Title @ Copyright. All rights reserved. Parameters: Parameter Description Example Values AccountAssignmentCategory Supports the accounting information of the buyer organization. F SurchargeAbs Supports the summary amount for the additional charges in the QuoteMessageOrder document. Applicable only when taxes & allowances are applied. ZB00 SurchargePercentage Supports the AdditionalCost percentage amount in the QuoteMessageOrder document. Applicable only when taxes & allowances are applied. ZA00 Asset Supports the Asset information for the buyer organization. 100 CostCenter Supports information about the Cost Center. 9010 DiscountAbs Supports the details of the deductions available for the items. Applicable only when taxes & allowances are applied. RB00 DiscountPercentage Supports the details of the percentage of deductions available for the items. Applicable only when taxes & allowances are applied. RA00 DefaultCompanyCode Supports information about the Company Code. 1 DefaultPurchasingGroup Supports information about the PurchasingGroup.ID for the buyer. 1 DefaultPurchasingOrg Supports information about the PurchasingOrganization.ID for the buyer. 1 3.3 Quote Message / Award Flows: configuration in CIG –Cross Reference Configuration – Parameter © SAP SE AR822 137 HOME Course Title @ Copyright. All rights reserved. Parameters continued: Parameter Description Example Values GLAccount Supports information about the General Ledger Accounts. 417000 GrossPrice Supports the Gross Pricing Condition of the service item. PB00 HeaderTextID Supports the long text description ID specified at the header-level. K01 LineTextID Supports the long text description ID specified at the line item level. K01 Order Supports the order ID. This field is required when the account assignment category is set to F. 100060 TotalPrice Supports the gross pricing condition of the service item. PRS SpotQuoteID Supports the ID for the request for quotations sent for Quote Automation to Ariba Network & SAP Ariba Discovery. F02 AssetSubNumber Supports the sub-number when the AccountingSegment ID information is set to A. 123 WBSElement Supports the WBS Element accounting information. 34232 • Similar type of parameters are required to be defined for QuoteMessageContract & QuoteMessageContractServices. • The information can be found in SAP Ariba Cloud Integration Gateway Configuration Guide. 3.3 Quote Message / Award Flows: configuration in CIG –Cross Reference Configuration – Parameter © SAP SE AR822 138 HOME Course Title @ Copyright. All rights reserved. 3.4 Quote Message / Award Flows: SAP System Quote Message / Award Flows: SAP System - Cross reference / parameter There is no Application specific configuration required in SAP System for Quote Message / Award integration from SAP Ariba Sourcing to SAP System. © SAP SE AR822 139 140© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ Procurement Transactions Integration © SAP SE AR822 140 HOME Course Title @ Copyright. All rights reserved. About This Lesson @ Copyright. All rights reserved. Lesson 1: Transaction Data Overview By the end of this lesson, you will be able to: • Describe the methods of how you can export transactional data from SAP Ariba Procurement solutions to SAP System • Identify supported and unsupported transactions • Describe the SAP Ariba Procurement integration process This lesson includes the following topics: i. List of supported and unsupported transactions ii. SAP Ariba Procurement integration process overview iii. SAP Ariba Procurement integration real time budget check process overview © SAP SE AR822 141 HOME Course Title @ Copyright. All rights reserved. Transaction Data Overview The SAP Ariba Procurement solutions integrated with SAP System via CIG can export transactional data to SAP System via following methods: ü Direct Connectivity using SAP Cloud Connector ü Mediated Connectivity using SAP PI / PO or SAP CPI Note: In this session we will explore the Direct Connectivity flow. © SAP SE AR822 142 HOME Course Title @ Copyright. All rights reserved. Transaction Data Overview Supported Procurement transactions: ü Requisition; Change & Cancel Requisition (for SAP only) ü Purchase Orders; Change, Cancel & Close Purchase Orders ü Goods Receipts ü Invoice / Payment Requests ü Service Procurement ü Advance Payment ü Asset Management ü Stock Availability & Reservation ü Purchase Order Header Status ü Close Purchase Orders ü Contract / Outline Agreement (for SAP only) ü Advance Payment Remittance ü Payment Remittance ü ERP-initiated Service Entry Sheet ü ERP-initiated Purchase Requisition Unsupported Procurement transactions: X File Channel transactional data integration for SAP Ariba Procurement solutions X Expense Report © SAP SE AR822 143HOME Course Title @ Copyright. All rights reserved. Transaction Data Overview SAP Ariba Procurement Integration Process Overview Ø In Ariba Procurement solution, users create Purchase Requisition & upon approving it fully, Purchase Order will be generated in Ariba Procurement to send it to SAP System. Ø SAP System will validate the Purchase Order data & sends back SAP Purchase Order ID to SAP Ariba Procurement. Ø User can then change or cancel the Purchase Order as required which will be again sent to SAP System for affecting the changes as done. SAP System sends back the confirmation of such changes either by modifying the existing Purchase Order data or canceling the complete Purchase Order as the case may be. Ø User can then create Receipts of such Purchase Order in SAP Ariba Procurement upon receiving the ordered goods. Goods Receipts can be created for partial or full quantity of the Purchase Order. Ø All the Receipts created in SAP Ariba Procurement will be sent to SAP System for record & SAP System sends back its Receipt ID to SAP Ariba Procurement. Ø User can then create Invoice against such Purchase Orders. Invoice also can be created either for partial or full quantity of the Purchase Order. Ø All the invoices created in Ariba Procurement solution will be sent to SAP System for record & SAP System sends back its Invoice ID to Ariba Procurement. Ø Upon reaching the due date of the invoice, user can create Remittance / Payment of such eligible invoices in SAP System & the Remittance information will be sent to SAP Ariba Procurement. Remittances can be created either for partial or full amount of the Invoice. © SAP SE AR822 144 HOME Course Title @ Copyright. All rights reserved. Transaction Data Overview Ariba Procurement Integration Real Time Budget Check – SAP ERP only Types of budget check: ü Budget check on Internal order and WBS ü Budget check on Funds Management For this, you need to configure the budget/spend amounts for the fiscal year for each expense category. The transaction flow: Ø Budget is allocated via the Purchase Requisition (PR). Ø The PR is simulated in SAP during budget check. Ø Then, once the Purchase Order (PO) is sent to SAP, the budget is allocated and once invoice is posted to SAP, the budget is consumed. Budget check functionality is available on Purchase Requisition ONLY. Budget check functionality is not available for Purchase Order and Invoice. © SAP SE AR822 145 HOME Course Title @ Copyright. All rights reserved. Transaction Data Overview SAP Ariba Procurement Integration Real-Time Budget Check Process Overview User creates a Purchase Requisition in SAP Ariba Procurement solution & before submitting it, performs a budget check. Depending upon the budget configuration & availability of budget in SAP System, a response is displayed as “Success” or “Failed”. (Budget is not yet consumed.) When user submits the Requisition, budget check is done again against the accounting fields. If budget is available, Requisition status changes to “Submitted”. In SAP System, the value of the Requisition amount is consumed for that account and is pre-committed. After the Requisition approval process in SAP Ariba Procurement, a Purchase Order is created. A Purchase Order amount for the account is now said to be committed. Once the Invoice is generated & sent to SAP System for the said Purchase Order, budget gets consumed in SAP System. If funds management is configured in SAP System, there is additional step called as “Get Funds Management” that the user can perform before submitting Purchase Requisition or it is done explicitly when user submits Requisition. Even during budget check the fund details are derived explicitly. “Get Fund Management” pulls all the FM fields in to requisition based on the derivation rules set in SAP System. When user performs budget check FM fields are received from SAP System. “Get Fund Management” can be also be performed while creating Non-PO Invoice. This will pull all the FM fields into Non-PO Invoice based on the derivation rules set in SAP System. FM Fields – Fund; FM Area; Grant; Functional Area; Budget Period; Commitment Item; Funds Centre etc. © SAP SE AR822 146 HOME Course Title @ Copyright. All rights reserved. SAP Ariba Procurement ERP or S/4HANA Buyer SAP Ariba Cloud Integration Gateway SAP Ariba Buying and Invoicing Master Data for Organizational, Accounting, Cross/application Configuration, Supplier, Users Master Data for Organizational, Accounting, Cross/application Configuration, Supplier, Users Catalogs SAP Cloud Platform (Messaging, data mapping, and transformation) Catalogs Requisition Requisition Contracts Contracts Purchase Order Purchase Order Purchase Order Status Purchase Order Status Budget Check Budget Check Goods Receipt SAP Ariba Cloud Integration Gateway user interface (Configuration wizard Mapping repository Test Central, Monitoring) Goods Receipt Goods Receipt Status Goods Receipt Status Advance Payments Advance Payments Service Sheet Service Sheet Service Sheet Response Service Sheet Response Invoices Invoices Invoice Status Invoice Status © SAP SE AR822 147 HOME Course Title @ Copyright. All rights reserved. About This Lesson @ Copyright. All rights reserved. Lesson 2: Purchase Order Flow By the end of this lesson, you will be able to: • Recognize the supported types of purchase order • Describe the purchase order integration flow between SAP Ariba Procurement solutions and SAP System and its pre-requisites • Understand the limitations of the purchase order integration flow This lesson includes the following topics: i. List of asynchronous & synchronous integration events ii. List of parameters to be enabled in the purchase order integration flow iii. SAP Ariba Cloud Integration configuration in sap Ariba Procurement, CIG and SAP System © SAP SE AR822 148 HOME Course Title @ Copyright. All rights reserved. About This Lesson @ Copyright. All rights reserved. Lesson 2: Purchase Order Flow This lesson also includes the following activities: 2.1 SAP Ariba Cloud Integration Specific Configuration in SAP Ariba Procurement 2.2 SAP Ariba Cloud Integration Specific Configuration in CIG 2.3 SAP Ariba Cloud Integration Configuration in SAP System © SAP SE AR822 149 HOME Course Title @ Copyright. All rights reserved. Purchase Order Flow The following types of Purchase Order 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 System & sets the unit price to 1. Purchase Order Buyers create a Purchase Order to request for product or services from suppliers. The Purchase Order is sent from SAP Ariba Procurement solution to SAP System. Upon approval the SAP Ariba Procurement solution would send it to Ariba Network. © SAP SE AR822 150 HOME Course Title @ Copyright. All rights reserved. Purchase Order Flow Buyers using SAP Ariba Procurement solutions integrated with SAP System can also send Purchase Order closure information from SAP Ariba Procurement solutions to SAP System. • Buyers need to ensure that the purchase order information in SAP Ariba Procurement solutions and SAP System are in sync to improve the fund allocation and utilization. • Upon receiving the Purchase Order closure information, SAP System releases any unused funds that were allocated for the Purchase Order and sets any open quantity to zero. • Buyers can specify a status while closing the 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 151 HOME Course Title @ Copyright. All rights reserved. Purchase Order Flow Buyers can send attachments & comments from AribaProcurement 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. IMPORTANT LIMITATIONS– • 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 • For more information regarding limitations, please refer to the SAP Ariba Cloud Integration Gateway overview guide. © SAP SE AR822 152 HOME Course Title @ Copyright. All rights reserved. Purchase Order Flow Pre-requisites: ü Required asynchronous & synchronous integration events are enabled in your SAP Ariba Procurement realm. ü Required parameters are enabled in your SAP Ariba Procurement realm. ü Required Cross-Reference parameters are maintained in SAP Ariba Cloud Integration Gateway (CIG). © SAP SE AR822 153 HOME Course Title @ Copyright. All rights reserved. Purchase Order Flow List of asynchronous & synchronous integration events to be enabled: ü Export Purchase Orders Asynchronously ü Import Purchase Order Status Asynchronously ü Export Change Purchase Orders 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 ü Export Purchase Order Close Status synchronously © SAP SE AR822 154 HOME Course Title @ Copyright. All rights reserved. Purchase Order Flow List of parameters to be enabled: ü Application.Procure.EnableTaxesChargesAndDiscount ü Application.Purchasing.RenumberReqLineItemSplits ü Application.Purchasing.PullCloseOrderStatusAckFromERP ü Application.Purchasing.PushCloseOrderStatusToERP ü Application.Purchasing.AllowPurchaseOrderLineClose ü Application.Procure.UseCancelOrderIntegration ü Application.Procure.EnableServiceItemFieldInRequisition ü Application.Procure.AllowAttachmentToERP ü Application.Ordering.AllowOrderAttachmentToERP ü Application.Approvable.AllowedAttachmentExtensions © SAP SE AR822 155 HOME Course Title @ Copyright. All rights reserved. Purchase Order Flow Limitations: ü SAP System supports file name of attachments up to 50 characters including extension. ü SAP Ariba Procurement solutions do not support exporting zero value amount for line items in amount-based purchase orders. ü SAP System supports maximum 40 characters in line item text for create & change purchase orders. ü Attachments for service line items in purchase orders are supported only at the parent line level & not at the child line level. ü Service hierarchy support is only up to two levels. For more information regarding limitations, please refer to the SAP Ariba Cloud Integration Gateway overview guide. © SAP SE AR822 156 HOME Course Title @ Copyright. All rights reserved. Purchase Order Flow Activities: 2.1 SAP Ariba Cloud Integration Specific Configuration in SAP Ariba Procurement 2.2 SAP Ariba Cloud Integration Specific Configuration in CIG 2.3 SAP Ariba Cloud Integration Configuration in SAP System © SAP SE AR822 157 HOME Course Title @ Copyright. All rights reserved. Purchase Order Flow There are 4 sub-activities in this section: 2.1.1 Enablement – In order to access the CIG portal, the Buyer user needs to enable the following in their SAP Ariba Procurement solution realm: Feature Toggles, Parameters, CIG Access, Integration Events. 2.1.1: These configurations have been covered in other unit(s) within this course and therefore will not be covered in this lesson.. 2.1.2 Set the Order Method 2.1.3 Review & Accept Changes to the Data Definition 2.1.4 Update WS Namespace Activity 2.1 SAP Ariba Cloud Integration Specific Configuration in SAP Ariba Procurement © SAP SE AR822 158 HOME Course Title @ Copyright. All rights reserved. Activity 2.1.2 SAP Ariba Cloud Integration Specific Configuration in Ariba Procurement - Set the Order Method The Buyer user needs to set the “Ordering Method” to send the Purchase Order data to SAP System. For this you need to raise a Service Request with SAP Ariba Customer Support. • Ordering Method “ariba.sap.server.SAPPOERP” is meant for sending the Purchase Order data to SAP System ONLY. • Ordering Method “ariba.sap.server.SAPPOERPCC” is meant for sending the Purchase Order data to SAP System & CC (Carbon Copy) to your connected Ariba Network Buyer account. Purchase Order Flow © SAP SE AR822 159 HOME Course Title @ Copyright. All rights reserved. To Review & Accept the Data Definition Changes: 1. Login to your SAP Ariba Procurement as Buyer Administrator & under Manage menu, select Core Administration. 2. Expand Integration Manager menu, click Data Definition. The Buyer must review (and accept) any changes in Data Definitions in order to avail new functionalities or enhancements done to the existing functionalities as appropriate to your requirements. Activity 2.1.3 SAP Ariba Cloud Integration Specific Configuration in Ariba Procurement - Review & Accept Changes to the Data Definition Purchase Order Flow © SAP SE AR822 160 HOME Course Title @ Copyright. All rights reserved. To Review & Accept the Data Definition Changes (continued): 3. Search for Purchase Order task by selecting Web Services format. All the tasks will be listed for the selection criteria. If there are any such changes to Data Definition, you can see the “Status” column is indicating “Changed” remark else it will be “Unchanged”. 4. Upon receiving search results, look for Export Purchase Orders Asynchronously task. Select Review from the Actions dropdown list located on the right side of the displayed task. Activity 2.1.3 SAP Ariba Cloud Integration Specific Configuration in Ariba Procurement - Review & Accept Changes to the Data Definition Purchase Order Flow © SAP SE AR822 161 HOME Course Title @ Copyright. All rights reserved. To Review & Accept the Data Definition Changes (continued): 5. The element which has changed will have Needs Review status & the details of changes will reflect in green color under Field Order of that element. Review the changes done to the structure & click on Accept Field Changes button. Activity 2.1.3 SAP Ariba Cloud Integration Specific Configuration in Ariba Procurement - Review & Accept Changes to the Data Definition Purchase Order Flow © SAP SE AR822 162 HOME Course Title @ Copyright. All rights reserved. To Review & Accept the Data Definition Changes (continued): 6. Once changes done to all the elements are reviewed & accepted, click Publish All Changes to make them available for integration. Note: you need to accept changes made to all the elements of the task. The system will not allow you to publish the changes unless you do so. Activity 2.1.3 SAP Ariba Cloud Integration Specific Configuration in Ariba Procurement - Review & Accept Changes to the Data Definition Purchase Order Flow © SAP SE AR822 163 HOME Course Title @ Copyright. All rights reserved. You need to update the WS Namespace. Users need to contact Ariba Customer Support for updating the namespace. • This is required to match with the namespace defined in the XSLT mappings. • In the XML file from SAP Ariba Procurement, the target namespace will appear as (for example): “xmlns="urn:Ariba:Buyer:vrealm_1234". • User need to have the target namespace as “xmlns="urn:Ariba:Buyer:vsap“. Our XSLT mappings work with this namespace only. Activity 2.1.4 SAP Ariba Cloud Integration Specific Configuration in Ariba Procurement – Update WS Namesapce Purchase Order Flow © SAP SE AR822 164 HOMECourse Title @ Copyright. All rights reserved. SAP Ariba Cloud Integration Specific Configuration in CIG Buyer users need to perform following activities: 1. Add / update SAP System information or ensure that the information sent from your SAP System is available in CIG. 2. Create the Project for Ariba Procurement product. 3. Add a Connection. 4. Define Cross-References Parameters & Lookup Values for the Document Type PurchaseOrderExportRequest based on your requirements. 5. Ensure that your realm ID is correctly selected. 6. Confirm & Test the project to get ready for deployment to Production. Activity 2.2 SAP Ariba Cloud Integration Specific Configuration in CIG Purchase Order Flow These configurations have been covered in other unit(s) within this course and therefore will not be covered in this lesson.. © SAP SE AR822 165 HOME Course Title @ Copyright. All rights reserved. SAP Ariba Cloud Integration Specific Configuration in SAP System There are 3 sub-activities in this section: 2.3.1 Global Settings 2.3.2 General Settings 2.3.3 Transaction Specific Settings Activity 2.3 SAP Ariba Cloud Integration Specific Configuration in SAP System Purchase Order Flow © SAP SE AR822 166 HOME Course Title @ Copyright. All rights reserved. Global Settings Ensure that following Global Settings are configured: ü Maintain Certificates ü Send SAP Information to CIG ü Maintain Parameters for Attachments Support ü Maintain BAdIs as per your requirements Activity 2.3.1 SAP Ariba Cloud Integration Specific Configuration in SAP System – Global Settings Purchase Order Flow © SAP SE AR822 167 HOME Course Title @ Copyright. All rights reserved. General Settings To navigate to general settings in SAP ERP and SAP S/4 HANA for Ariba Network transactions: 1. Run the transaction code SPRO – The Customizing: Execute Project screen appears. 2. Click SAP Reference IMG – The Display IMG screen appears. 3. Navigate to: Ø Integration with Other SAP Components Ø SAP Ariba Cloud Integration Gateway Ø SAP Ariba Procurement Integration Ø General Settings In order to enable the flow of messages between SAP System & SAP Ariba Procurement solutions, under General Settings user needs to: ü Setup the Interface ü Implement BAdIs for Setting Up the Interface Activity 2.3.2 SAP Ariba Cloud Integration Specific Configuration in SAP System – General Settings Purchase Order Flow © SAP SE AR822 168 HOME Course Title @ Copyright. All rights reserved. General Settings (Interface set-up) • This task is a one-time activity. • This will establish endpoints for web services. • The Logical Port setting is overwritten each time you run the interface settings for outbound web services. • You can execute the interface settings any time there is an update relevant to outbound web services. Activity 2.3.2 SAP Ariba Cloud Integration Specific Configuration in SAP System – General Settings (Interface set-up) Purchase Order Flow © SAP SE AR822 169 HOME Course Title @ Copyright. All rights reserved. Steps to follow to setup interface: 1. Navigate to: Ø SAP Ariba Procurement Integration Ø General Settings Ø Setup the Interface using the transaction code SPRO 2. Expand Setup the Interface, click IMG-Activity for Configure the Connections to Send Messages – the Interface Setup Program for Ariba Procurement screen appears. 3. Either click Select All (to select all listed transactions for both Outbound & Inbound flows) or select the flows individually. 4. In the Connection Instances section, select one of the following to indicate if the connection is to a Production instance or a Test instance of CIG. • Connect to Cloud Integration Gateway Production Instance • Connect to Cloud Integration Gateway Test Instance Activity 2.3.2 SAP Ariba Cloud Integration Specific Configuration in SAP System – General Settings (Interface set-up) Purchase Order Flow © SAP SE AR822 170 HOME Course Title @ Copyright. All rights reserved. Steps to follow to setup interface…(continued…): 5. In the Logon Data section, select one of the following types of authentication methods: • Select User ID / Password & enter authentication information to connect to CIG. • Select X.509 SSL Client Certificate & choose the Certificate Name (ARIBA, for example). 6. In the HTTP Proxy Options section, enter values for following fields: • Name of Proxy Host • Port Number of Proxy Host 7. Select Outbound Messages if already not selected. 8. In the Inbound messages sent from SAP Ariba Cloud Integration Gateway section, select Inbound Messages (if not already selected). 9. Click Execute Activity 2.3.2 SAP Ariba Cloud Integration Specific Configuration in SAP System – General Settings (Interface set-up) Purchase Order Flow © SAP SE AR822 171 HOME Course Title @ Copyright. All rights reserved. Upon running the report, you will get to see the results as shown in the example in the screenshot below: After you run the report, you can also view the status of the report message status using the TCode SLG1, using the object: ARBACIG_INTERFACE, and subobject: IF_LOGS. Activity 2.3.2 SAP Ariba Cloud Integration Specific Configuration in SAP System – General Settings (Interface set-up) Purchase Order Flow © SAP SE AR822 172 HOME Course Title @ Copyright. All rights reserved. If you are using middleware: 1. Ensure that the middleware parameter is enabled – ENABLE_PI_MIDDLEWARE or ENABLE_MIDDLEWARE. 2. Ensure that you have maintained required configuration under Global Settings >>> Customize SLD API and Integration Engine-Admin for PI Integration as discussed in Integration using SAP PI / PO Middleware lesson. 3. Setup the interface under SAP Ariba Procurement Integration >>> General Settings using the transaction code SPRO 4. Configure Interface Setup as described in step#1 to step#9 in the earlier slides. Additionally, you will need to provide following information in the step#5, the Logon Data section: Ø URL Host: Middleware host URL Ø Path Prefix: Middleware path prefix Activity 2.3.2 SAP Ariba Cloud Integration Specific Configuration in SAP System – General Settings (Interface set-up) Purchase Order Flow © SAP SE AR822 173 HOME Course Title @ Copyright. All rights reserved. General Settings (Interface set-up with BAdIs) When setting up the interface, you have the option to implement the BAdI to modify any parameters. • This BAdI is used for all SAP Ariba solutions. • The parameter IP_SOLUTION indicates the SAP Ariba solution for which BAdI is configured. Based on the solution you require, choose one of the possible values in the IP_SOLUTION field: • BUY - SAP Ariba Buying and Invoicing • SRC - SAP Ariba Sourcing and SAP Ariba Contracts • AN - Ariba Network Activity 2.3.2 SAP Ariba Cloud Integration Specific Configuration in SAP System – General Settings (Interface set-up with BAdIs) Purchase Order Flow © SAP SE AR822 174 HOME Course Title @ Copyright. All rights reserved. To implement the BAdI, perform the following steps: 1. Navigate to: Ø Ariba Procurement Integration Ø General Settings Ø Setup the Interface using the transaction code SPRO 2. Click IMG-Activity for the BAdIs for Setting Up the Interface – the Create Enhancement Implementation popup appears. 3. Implement the BAdI: Ø BAdI name: ARBCIG_AUTO_INTERFACE Ø Implementation methods: • CHANGE_MESSAGE_OUT: To change message parameters for outbound IDocs • CHANGE_MESSAGE_IN: To change message parameters for inbound IDocs • CHANGE_PARTNER_HEADER: To change partner header for IDocs • CHANGE_OUT_IDOC_IN: To change outbound IDocs message control • CHANGE_PROXY: To change parameters when setting up service name or logical port for proxies Activity 2.3.2 SAP Ariba Cloud Integration Specific Configuration in SAP System – General Settings (Interface set-up with BAdIs) Purchase Order Flow © SAP SE AR822 175 HOME Course Title @ Copyright. All rights reserved. Transaction Specific Settings To configure purchaseorder transaction: 1. Run the truncation code SPRO – the Customizing: Execute Project screen appears. 2. Click SAP Reference IMG – the Display IMG screen appears. 3. Navigate to: Ø Integration with Other SAP Components Ø SAP Ariba Cloud Integration Gateway Ø SAP Ariba Procurement Integration Ø Application Specific Settings Activity 2.3.3 SAP Ariba Cloud Integration Specific Configuration in SAP System – Transaction Specific Settings Purchase Order Flow All the supported transaction for SAP Ariba Procurement Integration are listed under Application Specific Settings. © SAP SE AR822 176 HOME Course Title @ Copyright. All rights reserved. Details on how to configure each of the supported procurement transaction are available in the SAP Ariba Cloud Integration Gateway Configuration Guide. • There is no specific configuration required in SAP System to receive purchase order messages from SAP Ariba Procurement. However, we will look into the configuration required for pulling Purchase Order Header Status from SAP System to SAP Ariba Procurement. • In case, you receive or invoice a purchase order in SAP System (not recommended), in SAP Ariba Procurement solutions it will be yet “to be received” & / or “to be invoiced”. • When purchase orders are in a Received, Receiving, Invoiced, or Invoicing state, the SAP Ariba Procurement solutions cannot cancel them. Similarly, when purchase orders have been received or invoiced in SAP ERP, the cancel export to SAP System fails. • The Purchase Order Header Status is sent from SAP System to SAP Ariba Procurement when a particular PO is either Received or Invoiced in SAP System. • In the Purchase Order Header Status message a flag is sent to SAP Ariba Procurement Solution which disables the “Cancel” button on the SAP Ariba Procurement purchase order. You then cannot cancel that purchase order in SAP Ariba Procurement. Activity 2.3.3 SAP Ariba Cloud Integration Specific Configuration in SAP System – Transaction Specific Settings Purchase Order Flow © SAP SE AR822 177 HOME Course Title @ Copyright. All rights reserved. About This Lesson @ Copyright. All rights reserved. Lesson 3: Receipt Flow By the end of this lesson, you will be able to: • Define the supported receipt types • Describe the receipt integration flow between SAP Ariba Procurement solutions and SAP System This lesson includes the following topics: i. Ariba Cloud Integration configuration in SAP Ariba Procurement, CIG and SAP System © SAP SE AR822 178 HOME Course Title @ Copyright. All rights reserved. About This Lesson @ Copyright. All rights reserved. Lesson 3: Receipt Flow This lesson also includes the following activities: 3.1 SAP Ariba Cloud Integration Specific Configuration in SAP Ariba Procurement 3.2 SAP Ariba Cloud Integration Specific Configuration in CIG 3.3 SAP Ariba Cloud Integration Configuration in SAP System 3.4 End-to-End Process Walkthrough from SAP Ariba Procurement to SAP System © SAP SE AR822 179 HOME Course Title @ Copyright. All rights reserved. Receipt Flow Goods Receipt A receipt is an acknowledgment of the goods that have arrived. The SAP Ariba provided integration code integrates receipts as goods receipts with Movement Type: 101 Buyers can create a negative receipt in the SAP Ariba Procurement solutions to reverse some received quantity as a result of incorrect shipment or errors. SAP Ariba provided integration code integrates negative receipts as goods receipts with Movement Type as 102. For amount-based receipts, the SAP 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 180 HOME Course Title @ Copyright. All rights reserved. Receipt Flow Activities: 3.1 SAP Ariba Cloud Integration Specific Configuration in SAP Ariba Procurement 3.2 SAP Ariba Cloud Integration Specific Configuration in CIG 3.3 SAP Ariba Cloud Integration Configuration in SAP System © SAP SE AR822 181 HOME Course Title @ Copyright. All rights reserved. There are 2 sub-activities in this section: ü Enablement ü Review & Accept Changes to the Data Definition Receipt Flow 3.1: These configurations have been covered in other unit(s) within this course and therefore will not be covered in this lesson. Activity 3.1 SAP Ariba Cloud Integration Specific Configuration in SAP Ariba Procurement © SAP SE AR822 182 HOME Course Title @ Copyright. All rights reserved. To configure SAP Ariba Cloud Integration Specific Configuration in CIG: 1. Add / update SAP System information or ensure that the information sent from your SAP System is available in CIG. 2. Create the Project for Ariba Procurement product. 3. Add a Connection. 4. Define Cross-References Parameters & Lookup Values based on your requirements. 5. Ensure that your realm ID is correctly selected. 6. Confirm & Test the project to get ready for deployment to Production. Receipt Flow Activity 3.2 SAP Ariba Cloud Integration Specific Configuration in CIG 3.2: These configurations have been covered in other unit(s) within this course and therefore will not be covered in this lesson. © SAP SE AR822 183 HOME Course Title @ Copyright. All rights reserved. There are 3 sub-activities in this section: 3.3.1 Global Settings 3.3.2 General Settings 3.3.3 Transaction Specific Settings Receipt Flow Activity 3.3 SAP Ariba Cloud Integration Specific Configuration in SAP System © SAP SE AR822 184 HOME Course Title @ Copyright. All rights reserved. Ensure that following configurations of Global Settings section are in place: ü Maintain Certificates ü Send SAP Information to CIG ü Maintain Parameters for Attachments Support ü Maintain BAdIs as per your requirements Receipt Flow Activity 3.3.1 SAP Ariba Cloud Integration Specific Configuration in SAP System – Global Settings © SAP SE AR822 185 HOME Course Title @ Copyright. All rights reserved. To navigate to general settings in SAP ERP and SAP S/4 HANA for Ariba Network Transactions: 1. Run the transaction code SPRO – The Customizing: Execute Project screen appears. 2. Click SAP Reference IMG – The Display IMG screen appears. 3. Navigate to: Ø Integration with Other SAP Components Ø SAP Ariba Cloud Integration Gateway Ø SAP Ariba Procurement Integration Ø General Settings Receipt Flow Activity 3.3.2 SAP Ariba Cloud Integration Specific Configuration in SAP System – General Settings © SAP SE AR822 186 HOME Course Title @ Copyright. All rights reserved. To navigate to general settings in SAP ERP and SAP S/4 HANA for Ariba Network Transactions: 1. Run the transaction code SPRO – The Customizing: Execute Project screen appears. 2. Click SAP Reference IMG – The Display IMG screen appears. 3. Navigate to: Ø Integration with Other SAP Components Ø SAP Ariba Cloud Integration Gateway Ø SAP Ariba Procurement Integration Ø General Settings Receipt Flow Activity 3.3.2 SAP Ariba Cloud Integration Specific Configuration in SAP System – General Settings © SAP SE AR822 187 HOME Course Title @ Copyright. All rights reserved. In order to enable the flow of messages between SAP System & SAP Ariba Procurement solutions, under General Settings user needs to: ü Setup the Interface ü Implement BAdIs for Setting Up the Interface Receipt Flow Activity 3.3.2 SAP Ariba Cloud Integration Specific Configuration in SAP System – General Settings © SAP SE AR822 188 HOME Course Title @ Copyright. All rights reserved. Users can maintain a parameter to set the timeout in order to prevent it from getting locked in SAP System. To maintain parameters for Goods Receipt, perform the following steps: 1. Navigate to: Ø Integration with Other SAP ComponentsØ SAP Ariba Cloud Integration Gateway Ø SAP Ariba Procurement Integration Ø Application Specific Settings Ø Goods Receipt. 2. Expand Goods Receipt & click IMG-Activity for Maintain Parameters for Goods Receipt Create – the Parameters - Receipt Export Request screen appears. 3. Maintain the parameter mentioned in the following table: Parameter Name Description Supported values GOODS_RECEIPTS_CREATE Configure time-out settings (in seconds) for the goods receipt export task to prevent it from being locked in the SAP System. - Variable Name: GOODS_RECEIPTS_CREATE - Field Name: Leave it blank - Number: 0000 - Variant: Provide a variant for SAP Ariba Procurement solutions. VREALM2 (example) - Partition: Provide a partition for SAP Ariba Procurement solutions. PREALM2 (example) - Low: 5 Receipt Flow Activity 3.3.3 SAP Ariba Cloud Integration Specific Configuration in SAP System – Transaction Specific Settings This wait time is mainly to check if the PO is locked for any other activity & wait for the PO get released. © SAP SE AR822 189 HOME Course Title @ Copyright. All rights reserved. About This Lesson @ Copyright. All rights reserved. Lesson 4: Invoice Flow By the end of this lesson, you will be able to: • Define the supported invoice types and discount scenarios • Describe the invoice integration flow between SAP Ariba Procurement solutions and SAP System This lesson includes the following topics: i. SAP Ariba Cloud Integration configuration in SAP Ariba Procurement, CIG and SAP System © SAP SE AR822 190 HOME Course Title @ Copyright. All rights reserved. About This Lesson @ Copyright. All rights reserved. Lesson 4: Invoice Flow This lesson also includes the following activities: 4.1 SAP Ariba Cloud Integration Specific Configuration in SAP Ariba Procurement 4.2 SAP Ariba Cloud Integration Specific Configuration in CIG 4.3 SAP Ariba Cloud Integration Configuration in SAP System © SAP SE AR822 191 HOME Course Title @ Copyright. All rights reserved. Invoice Flow The following types of invoices are supported: ü PO-based Invoice ü Non-PO Invoice ü Non-PO Invoice for one time vendors ü Service Invoice ü Line Level Credit Memo ü Header Level Credit Memo Invoice: Invoices can be sent by suppliers on Ariba Network to buyers on SAP Ariba Procurement solutions or can be directly created by buyers within SAP Ariba Procurement solutions. After reconciliation, these invoices are exported / sent to SAP System. Enable the following Asynchronous Integration events: ü Export Payment Requests Asynchronously ü Import Payment Requests Status Asynchronously © SAP SE AR822 192 HOME Course Title @ Copyright. All rights reserved. Invoice Flow Invoice (continued…): 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). © SAP SE AR822 193 HOME Course Title @ Copyright. All rights reserved. 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. Invoice Flow For more information regarding limitations, please refer to the SAP Ariba Cloud Integration Gateway overview guide. © SAP SE AR822 194 HOME Course Title @ Copyright. All rights reserved. Invoice Flow Activities: 4.1 SAP Ariba Cloud Integration Specific Configuration in SAP Ariba Procurement 4.2 SAP Ariba Cloud Integration Specific Configuration in CIG 4.3 SAP Ariba Cloud Integration Configuration in SAP System © SAP SE AR822 195 HOME Course Title @ Copyright. All rights reserved. There are 4 sub-activities in this section: 4.1.1 Enablement 4.1.2 Review & Accept Changes to the Data Definition 4.1.1 & 4.1.2: These configurations have been covered in other unit(s) within this course and therefore will not be covered in this lesson. 4.1.3 Required Exception Rules are configured 4.1.4 Required Tax Configurations are maintained . If you are on CIG-AddOn SP4 or above, and adopting FI-based Invoice feature, then you must update Data Definition for Export Payment Requests Asynchronously Invoice Flow Activity 4.1 SAP Ariba Cloud Integration Specific Configuration in SAP Ariba Procurement © SAP SE AR822 196 HOME Course Title @ Copyright. All rights reserved. Buyer users need to perform following activities in this section: 1. Add / update SAP System information or ensure that the information sent from your SAP System is available in CIG. 2. Create the Project for Ariba Procurement product. 3. Add a Connection. 4. Define Cross-References Parameters & Lookup Values for the Document Type PaymentExportRequest based on your requirements. 5. Ensure that your realm ID is correctly selected. 6. Confirm & Test the project to get ready for deployment to Production. Invoice Flow Activity 4.2 SAP Ariba Cloud Integration Specific Configuration in CIG © SAP SE AR822 197 HOME Course Title @ Copyright. All rights reserved. There are 3 sub-activities in this section: 4.3.1 Global Settings 4.3.2 General Settings 4.3.3 Transaction Specific Settings Invoice Flow Activity 4.3 SAP Ariba Cloud Integration Specific Configuration in SAP System © SAP SE AR822 198 HOME Course Title @ Copyright. All rights reserved. Ensure that following configurations of Global Settings section are in place: ü Maintain Certificates ü Send SAP Information to CIG ü Maintain Parameters for Attachments Support ü Maintain BAdIs as per your requirements Invoice Flow Activity 4.3.1 SAP Ariba Cloud Integration Specific Configuration in SAP System – Global Settings © SAP SE AR822 199 HOME Course Title @ Copyright. All rights reserved. To navigate to General Settings in SAP ERP and SAP S/4 HANA for Ariba Network Transactions: 1. Run the transaction code SPRO – the Customizing: Execute Project screen appears. 2. Click SAP Reference IMG – the Display IMG screen appears. 3. Navigate to – Ø Integration with Other SAP Components Ø SAP Ariba Cloud Integration Gateway Ø SAP Ariba Procurement Integration Ø General Settings Invoice Flow Activity 4.3.2 SAP Ariba Cloud Integration Specific Configuration in SAP System – General Settings © SAP SE AR822 200 HOME Course Title @ Copyright. All rights reserved. In order to enable the flow of messages between SAP System & SAP Ariba Procurement solutions, under General Settings user needs to: ü Setup the Interface ü Implement BAdIs for Setting Up the Interface Invoice Flow Activity 4.3.2 SAP Ariba Cloud Integration Specific Configuration in SAP System – General Settings © SAP SE AR822 201 HOME Course Title @ Copyright. All rights reserved. Users can maintain a parameter to set the timeout in order to prevent it from getting locked in SAP System. To maintain parameters for Invoice, perform the following steps: 1. Navigate to: Ø Integration with Other SAP Components Ø SAP Ariba Cloud Integration Gateway Ø SAP Ariba Procurement Integration Ø Application Specific Settings Ø Invoice 2. Expand Invoice & click IMG-Activity for Maintain Parameters for Invoice – the Parameters - Payment Export Request screen appears. 3. Maintain the parameter mentioned in the table: Parameter Name Description Supported values INVOICE_PUSH Configure time-out settings (in seconds) for the invoice export task to prevent it from being locked in the SAP System. - Variable Name: INVOICE_PUSH - Field Name: Leave it blank - Number: 0000 - Variant: Provide a variant forSAP Ariba Procurement solutions. VREALM2 (example) - Partition: Provide a partition for SAP Ariba Procurement solutions. PREALM2 (example) - Low: 5 Invoice Flow Activity 4.3.3 SAP Ariba Cloud Integration Specific Configuration in SAP System – Transaction Specific Settings © SAP SE AR822 202 LOGO HERE @ Copyright. All rights reserved. Section Complete Congratulations! You have now completed this Section! © SAP SE AR822 203topics: 3.1 – Ariba Cloud Integration specific configuration in SLP. • 3.1.1 Set up ERP in SLP • 3.1.2 Setting up Supplier data synchronization from SLP to ERP • 3.1.2a Set up initial Supplier data synchronization • 3.1.2b Control the ongoing synchronization of data from suppliers in mass registration waves • 3.1.3 Configuring MDG-S validation and approval of supplier creation in SLP • 3.1.3a Requiring MDG-S validation & approval of supplier creation in SLP • 3.1.3b How to require MDG-S validation & approval of supplier creation in SLP • 3.1.4 Configuring ERP approval of updates to supplier data in SLP • 3.1.4a Requiring ERP approval for updates to supplier data in SLP • 3.1.4b How to require ERP approval for supplier data updates in SLP • 3.1.5 Connecting ERP vendor fields to SLP questionnaires 3.2 – Ariba Cloud Integration specific configuration in CIG. 3.3 – Ariba Cloud Integration configuration in SAP system. 3.3.1 Configurations for MDG 3.3.2 Define a replication model for supplier data integration 3.3.3 Configure connection to CIG 3.3.4 Configuration to monitor errors © SAP SE AR822 15 HOME Course Title @ Copyright. All rights reserved. Supplier Lifecycle (SLP) Flow: SAP Ariba Cloud Integration Gateway specific configuration in SLP SAP Ariba Cloud Integration specific configuration in SLP There are 5 activities in this section: 5 Connecting ERP vendor fields to SLP questionnaires 4 Configuring ERP approval of updates to supplier data in SLP 3 Configuring MDG-S validation and approval of supplier creation in SLP 2 Setting up Supplier data synchronization from SLP to ERP 1 Set up ERP in SLP © SAP SE AR822 16 HOME Course Title @ Copyright. All rights reserved. Supplier Lifecycle (SLP) Flow: SAP Ariba Cloud Integration specific configuration in SLP © SAP SE AR822 17 HOME Course Title @ Copyright. All rights reserved. Supplier Lifecycle (SLP) Flow: SAP Ariba Cloud Integration specific configuration in SLP Step 1 of 7 1. On the dashboard, navigate to Manage >>> SM Administration. © SAP SE AR822 18 HOME Course Title @ Copyright. All rights reserved. Supplier Lifecycle (SLP) Flow: SAP Ariba Cloud Integration specific configuration in SLP Step 2 of 7 2. Click on ERP Integration. © SAP SE AR822 19 HOME Course Title @ Copyright. All rights reserved. Supplier Lifecycle (SLP) Flow: SAP Ariba Cloud Integration specific configuration in SLP Step 3 of 7 3. Click Integration Type © SAP SE AR822 20 HOME Course Title @ Copyright. All rights reserved. Supplier Lifecycle (SLP) Flow: SAP Ariba Cloud Integration specific configuration in SLP Steps 4-7 of 7 4. Choose SAP Ariba Cloud Integration Gateway (Recommended) in the Select Integration Type dropdown list 5. Enter the system ID in the ERP Business System ID field 6. Enter the Ariba SLP Site ID in the SAP Ariba Business System ID field 7. Click Save © SAP SE AR822 21 HOME Course Title @ Copyright. All rights reserved. Supplier Lifecycle (SLP) Flow: SAP Ariba Cloud Integration specific configuration in SLP ERP Business System ID field: This is the system ID of the SAP ERP system. The SAP Ariba Supplier Management solutions uses this system ID to send the supplier data to the corresponding ERP system. For example, ABCCLNT002 . • After an integration connection with SAP ERP is established, this field is automatically populated with the name your SAP ERP system uses to identify SM. • In default configurations, this is the SAP Ariba customer site name you set as the User ID in your integration method configuration, and you do not have to change that setting. • However, if your SAP ERP configuration uses a custom naming scheme to identify external systems instead, you must specify the customer site name for your SLP site here. • Ensure that the customer site name is an exact match to the name SAP Ariba used to create your site. If you are unsure of your customer site name, contact an SAP Ariba representative. © SAP SE AR822 22 HOME Course Title @ Copyright. All rights reserved. Supplier Lifecycle (SLP) Flow: SAP Ariba Cloud Integration specific configuration in SLP There are 2 sub activities in this section – 1. Set-up initial Supplier data synchronization 2. Control the ongoing synchronization of data from suppliers in mass registration waves © SAP SE AR822 23 HOME Course Title @ Copyright. All rights reserved. Integration Prerequisites: for Supplier Lifecycle Performance (SLP) If the Customer ERP uses MDG approval workflows for changes of vendor records sent from SLP, then changes from SLP can require ERP approval. Set-up initial Supplier data synchronization Supplier data synchronization can either be manual or automatic by specifying supplier sync status. • Once the initial synchronization of new supplier data with the ERP occurs, updates are automatically passed between SLP and ERP using CIG. Automatic Synchronization • occurs based on settings defined to send Supplier record from SLP to ERP • will sync all Suppliers with that Status in SM with ERP Manual Synchronization • an ERP synchronization link appears in the upper right corner of the Supplier 360 view • The Category Manager clicks the synchronization link when they are ready to transact with supplier based on defined status © SAP SE AR822 24 HOME Course Title @ Copyright. All rights reserved. Supplier Lifecycle (SLP) Flow: SAP Ariba Cloud Integration specific configuration in SLP Set-up initial Supplier data synchronization Steps 1 of 7 1. On the dashboard Home page, click the Manage dropdown menu and select SM Administration © SAP SE AR822 25 HOME Course Title @ Copyright. All rights reserved. Supplier Lifecycle (SLP) Flow: SAP Ariba Cloud Integration specific configuration in SLP Set-up initial Supplier data synchronization Steps 2 of 7 2. Click on ERP Integration © SAP SE AR822 26 HOME Course Title @ Copyright. All rights reserved. Supplier Lifecycle (SLP) Flow: SAP Ariba Cloud Integration specific configuration in SLP Set-up initial Supplier data synchronization Steps 3-5 of 7 3. Click Initial supplier synchronization and choose either Automatic synchronization or Manual synchronization. 4. For Manual synchronization, choose one of the following statuses for initial synchronization (see table below for descriptions): • Not Invited • Invited • In Registration • Pending Approval • Registered • Qualified 5. Click Save © SAP SE AR822 27 HOME Course Title @ Copyright. All rights reserved. Supplier Lifecycle (SLP) Flow: SAP Ariba Cloud Integration specific configuration in SLP Set-up initial Supplier data synchronization Steps 6-7 of 7 6. For Automatic synchronization, choose following options for initial synchronization ü When supplier record is created in SLP (Not invited). ü When a supplier is registered. ü When a supplier is qualified. 7. Click Save © SAP SE AR822 28 HOME Course Title @ Copyright. All rights reserved. Integration Prerequisites: for Supplier Lifecycle Performance (SLP) Control the ongoing synchronization of data from suppliers in mass registration waves To setup ongoing synchronization, the user needs to be a member of the SM ERP Administrator group. Mass Registration • Mass registration invitations allow you to issue automatic registration invitations to large numbers of suppliers to bring them on board quickly. • These mass registration invitations are organized into waves (groups) so that your company can coordinate its supplier or category management resources to process a large number of registrations. Ongoing Synchronization • By default, once a supplier is initially synchronized with SAP ERP, all updates, including registration data, are synchronized automatically as they occur and (if applicable) are approved in SAP Ariba Supplier Management solutions. • When the registration data is generated by a mass registration wave, SLP will use the ongoing synchronization setting to sync thedata with SAP ERP. © SAP SE AR822 29 HOME Course Title @ Copyright. All rights reserved. Supplier Lifecycle (SLP) Flow: SAP Ariba Cloud Integration specific configuration in SLP Ongoing data synchronization for Mass Registration Steps 1 of 5 1. On the dashboard Home page, click the Manage dropdown menu and select SM Administration © SAP SE AR822 30 HOME Course Title @ Copyright. All rights reserved. Supplier Lifecycle (SLP) Flow: SAP Ariba Cloud Integration specific configuration in SLP Ongoing data synchronization for Mass Registration Steps 2 of 5 2. Click ERP Integration © SAP SE AR822 31 HOME Course Title @ Copyright. All rights reserved. Supplier Lifecycle (SLP) Flow: SAP Ariba Cloud Integration specific configuration in SLP Ongoing data synchronization for Mass Registration Steps 3-5 of 5 3. Expand the Ongoing supplier synchronization area, then choose the mass invitation wave for which you want to control synchronization from the dropdown menu. • If you use the ongoing synchronization setting, the moment you apply this setting, suppliers in the specified wave stop being synchronized with the ERP. • Instead, the next ongoing synchronization occurs on the date and time you specify. After that date, automatic ongoing synchronization starts again for the suppliers in the wave. 4. Choose the date you want ongoing synchronization to start again for suppliers in the wave. 5. Click Save. © SAP SE AR822 32 HOME Course Title @ Copyright. All rights reserved. Supplier Lifecycle (SLP) Flow: SAP Ariba Cloud Integration specific configuration in SLP There are 2 sub activities in this section – 1. Requiring MDG-S validation & approval of supplier creation in SLP 2. How to require MDG-S validation & approval of supplier creation in SLP © SAP SE AR822 33 HOME Course Title @ Copyright. All rights reserved. Integration Prerequisites: for Supplier Lifecycle Performance (SLP) Requiring MDG-S validation & approval of supplier creation in SLP • This setting is designed for customers who maintain corporate-level business partners (both suppliers & customers) in MDG-S and use MDG-S to perform duplicate SAP Business Partner Screening & vendor record enrichment. • Also customers who want to initiate supplier requests & manage supplier lifecycles in SLP. • The setting allows you to send approved supplier requests to MDG-S, where they are validated against both supplier & customer business partners. • Any duplicates are identified, and information such as address and Dun & Bradstreet ID are validated & corrected if necessary based on the information in MDG-S, which is always the source-of-truth in this scenario. • This concept mainly prevails in US. D-U-N-S Number, a unique nine digit identification number, for each physical location of your business. © SAP SE AR822 34 HOME Course Title @ Copyright. All rights reserved. Integration Prerequisites: for Supplier Lifecycle Performance (SLP) If the Customer ERP uses MDG approval workflows for changes of vendor records sent from SLP, then changes from SLP can require ERP approval. Requiring MDG-S validation & approval of supplier creation in SLP • When the Enable external validation of supplier creation in ERP or MDG setting is not enabled and a supplier request is finally approved, SLP creates a new supplier record in the database automatically. This is the default behavior. To override default behavior: Activate “Enable external validation” so that the record will go to MDG for validation before creating record in ERP. • The “Enable external validation” of supplier creation in ERP or MDG setting is designed to work with ERP configurations that use MDG-S for supplier master data management. • It does not work with SAP ERP configurations that do not include MDG-S. • An integration setting allows you to require that approved supplier requests be validated in MDG-S module before SLP creates the new supplier database record. • Contact your SAP Ariba Customer Support to enable this setting. © SAP SE AR822 35 HOME Course Title @ Copyright. All rights reserved. Integration Prerequisites: for Supplier Lifecycle Performance (SLP) Requiring MDG-S validation & approval of supplier creation in SLP Overview – • This setting is designed for customers who maintain corporate-level business partners (both suppliers & customers) in MDG-S and use MDG-S to perform duplicate SAP Business Partner Screening & vendor record enrichment. • Also customers who want to initiate supplier requests & manage supplier lifecycles in SLP. • The setting allows you to send approved supplier requests to MDG-S, where they are validated against both supplier & customer business partners. • Any duplicates are identified, and information such as address and Dun & Bradstreet ID are validated & corrected if necessary based on the information in MDG-S, which is always the source of truth in this scenario. © SAP SE AR822 36 HOME Course Title @ Copyright. All rights reserved. Integration Prerequisites: for Supplier Lifecycle Performance (SLP) •This concept mainly prevails in US. D-U-N-S Number, a unique nine digit identification number, for each physical location of your business. • In SLP there is no way to merge multiple supplier records or SMID. So every time a new supplier is created it will be validated in the MDG system and if any duplicate found it will be marked as inactive. • This validation occurs before the supplier record is created in SLP, which is especially important for preventing the creation of duplicate supplier records under some circumstances. • By default, SLP only check for duplicate suppliers within the SAP Ariba vendor database. • In cases where there is a second approved supplier request for what MDG-S recognizes as an already existing & synchronized supplier, there can be duplicate separate records in SLP that correspond to one supplier record with multiple SM_ID key mappings in MDG-S. MDG-S then replicates data for the supplier back with both SAP Ariba supplier records. • There is currently no way to merge the records in SAP Ariba, and users might register, qualify, invite to sourcing events, or add to contracts one or the other of the duplicate supplier objects, causing them to accumulate separate transaction & activity histories. © SAP SE AR822 37 HOME Course Title @ Copyright. All rights reserved. Integration Prerequisites: for Supplier Lifecycle Performance (SLP) Requiring MDG-S validation & approval of supplier creation in SLP High-Level Workflow – 1. An internal user at your company wants to work with a supplier, does not recognize the supplier as an existing supplier when performing a search in SAP Ariba, and creates a new supplier request. 2. Instead of creating the supplier record at this point, SLP will add an automatic task: MDGS Validation 3. The supplier request moves from status: In Approval to status: In External Approval 4. MDG-S performs one of the two actions based on whether or not a match is found to an existing supplier or customer business partner: • MDG-S sends the supplier request back to SLP with a new, unique ERP vendor ID. • SLP create a new supplier record based on the request and the supplier moves to Not Invited registration status. MATCH NOT FOUND • MDG-S adds the new, unique SM_ID sent in the request to the mapping tables in the existing business partner. • MDG-S sends a replication request back to SLP with the SM_ID and the ERP vendor ID for the existing supplier. • SLP reconcile the replication request and verifies whether or not the ERP vendor ID assigned by MDG-S matches a supplier in SLP. • SLP send an email notification to the requester and all active team members in the supplier request project. MATCH FOUND © SAP SE AR822 38 HOME Course Title @ Copyright. All rights reserved. Integration Prerequisites: for Supplier Lifecycle Performance (SLP) Requiring MDG-S validation & approval of supplier creation in SLP • SMID gets added to the existingBP table and MDG sends back the req with ERP vendor ID which is then reconciled in SLP with existing supplier. • If there is a matching supplier, SM create a supplier record for the originating supplier request but marks it as inactive with an ERP integration status of duplicate. • Inactive suppliers do not show in search results or on the dashboard and cannot be added to sourcing events or contracts. The supplier record is just for historical purposes only. • An Email to let the requester know that the request was denied because MDG-S found a duplicate supplier redirecting them to the existing matched supplier in SAP Ariba Supplier Management solutions is sent. © SAP SE AR822 39 HOME Course Title @ Copyright. All rights reserved. Integration Prerequisites: for Supplier Lifecycle Performance (SLP) How to require MDG-S validation & approval of supplier creation in SLP • For MDG-S validation & approval of supplier creation in SLP, approved supplier requests are validated & checked for duplicates in MDG-S before supplier creation, and duplicate requests are matched to existing suppliers. • To modify integration settings, you must be a member of the SM ERP Administrator group. © SAP SE AR822 40 HOME Course Title @ Copyright. All rights reserved. Integration Prerequisites: for Supplier Lifecycle Performance (SLP) How to require MDG-S validation & approval of supplier creation in SLP Customer Support Admin will follow these steps: 1. On the dashboard, navigate to Manage >>> SM Administration. 2. Click on Feature Control. 3. In the Feature Control page, select Feature list as External Approval 4. Select Enabled button 5. Click Update. © SAP SE AR822 41 HOME Course Title @ Copyright. All rights reserved. Integration Prerequisites: for Supplier Lifecycle Performance (SLP) How to require MDG-S validation & approval of supplier creation in SLP SM Admin will follow these steps: 1. On the dashboard, navigate to Manage >>> SM Administration. 2. Click ERP Integration. 3. In the Supplier profile update synchronization area, check Enable external validation of supplier creation in ERP or MDG. 4. Click Save. © SAP SE AR822 42 HOME Course Title @ Copyright. All rights reserved. Supplier Lifecycle (SLP) Flow: SAP Ariba Cloud Integration specific configuration in SLP Configuring ERP approval of updates to supplier data in SLP There are 2 sub activities in this section – 1. Requiring ERP approval for updates to supplier data in SLP 2. How to require ERP approval for supplier data updates in SLP © SAP SE AR822 43 HOME Course Title @ Copyright. All rights reserved. Supplier Lifecycle (SLP) Flow: SAP Ariba Cloud Integration specific configuration in SLP Configuring ERP approval of updates to supplier data in SLP: Requiring ERP approval for updates to supplier data in SLP • The Enable external ERP approval integration setting requires external ERP approval for changes to supplier registration data in SLP. • The Enable external ERP approval integration setting ensures Changed Vendor data in SM is approved in External ERP • By default, integration between SLP and ERP is bi-directional. • MDG Approval Workflow: The update request that SLP sends to ERP is designed to feed into existing MDG workflows. • Custom Approval Workflow : ERP must receive the update requests from SLP. • The external ERP should support an approval process for updates to vendor records • The external ERP approval requirement applies only to updates in supplier registration projects. • Also in registration projects, it only applies to fields that are mapped to the vendor database since only those fields are synchronized with ERP. • Supplier Registration Project: Suppliers update the registration questionnaire and internal users can update associated internal surveys on an ongoing basis. • Whatever data supplier is maintained in the supplier registration phase we are integrating all those info with ERP vendor master fields, so if any changes is made to this data and the filed is an ERP integrated filed then all those info will get validated in MDG. • If there is no violation, it will get updated making sure the data is exactly the same. © SAP SE AR822 44 HOME Course Title @ Copyright. All rights reserved. Supplier Lifecycle (SLP) Flow: SAP Ariba Cloud Integration specific configuration in SLP Configuring ERP approval of updates to supplier data in SLP: Requiring ERP approval for updates to supplier data in SLP High-level work flow: 1. In SLP, registered supplier submits an update to one or more mapped fields in the registration questionnaire Example: the supplier might move and update its address in the registration questionnaire, and those address fields are mapped to the vendor database address fields. 2. In SLP, updates for supplier-facing questionnaire are approved either automatically or manually. 3. SLP send a request for update to ERP that includes the new data. 4. ERP receives the update request & processes it through its approval flow. 5. An ERP vendor administrator either accepts the changes, accepts a modified form of the changes, or rejects the changes. 6. The vendor record in ERP now reflects these actions by either including the changes from SLP or remaining unchanged. 7. ERP sends the complete current vendor record back to SLP using DRF. 8. SLP updates the vendor database to match the vendor record sent by ERP. 9. In either case, the SLP vendor record replicates the current, approved SAP ERP vendor record. 10.SLP sends an email notification to the supplier registration project owner, and supplier's primary supplier manager indicating whether the update was approved or rejected in SAP ERP. 11.The notification includes the status of the update; if it was rejected, the notification also includes the error message from SAP ERP, which the category or supplier manager can use to correct the update & submit it again. © SAP SE AR822 45 HOME Course Title @ Copyright. All rights reserved. Supplier Lifecycle (SLP) Flow: SAP Ariba Cloud Integration specific configuration in SLP Example: A registered supplier (who is also integrated with ERP), makes a change to their registration data (i.e. address) Ø Once the address is changed, the change request will go to ERP for validation. Ø ERP will receive the request and pass it to approval flow and Ø The ERP vendor admin will have an option either to accept or reject the changes § Whatever action the vendor admin will perform on the change req based on that the vendor record in ERP will get updated or remain unchanged. § In both cases the vendor record is sent back to SLP using DRF, and the same gets updated in SLP vendor DB. Configuring ERP approval of updates to supplier data in SLP: Requiring ERP approval for updates to supplier data in SLP © SAP SE AR822 46 HOME Course Title @ Copyright. All rights reserved. Supplier Lifecycle (SLP) Flow: SAP Ariba Cloud Integration specific configuration in SLP Configuring ERP approval of updates to supplier data in SLP: Requiring ERP approval for updates to supplier data in SLP Additional information: • If additional updates for the same supplier occur in SLP while a previous update is still in approval in ERP, SLP retains those updates and only sends them to ERP after receiving the response to the previous update • If you require approval of supplier updates in SAP ERP, you will typically set the approval task for registration questionnaire updates in SLP to auto-approve, since you are managing changes in SAP ERP. • If there are multiple updates happening in the registration data, for the first time when the change request goes to ERP, SLP will wait for the response before sending subsequent update request. © SAP SE AR822 47 HOME Course Title @ Copyright. All rights reserved. Supplier Lifecycle (SLP) Flow: SAP Ariba Cloud Integration specific configuration in SLP Configuring ERP approval of updates to supplier data in SLP: How to require ERP approval for supplierdata updates in SLP • For external ERP approval of supplier data updates in SLP, changes to any mapped fields in supplier profiles must be approved in the integrated ERP system before they are committed to the SLP vendor database. • To modify integration settings, you must be a member of the SM ERP Administrator group. © SAP SE AR822 48 HOME Course Title @ Copyright. All rights reserved. Supplier Lifecycle (SLP) Flow: SAP Ariba Cloud Integration specific configuration in SLP How to require ERP approval for supplier data updates in SLP: A SM ERP Administrator group member must follow these steps: 1. On the dashboard, navigate to Manage >>> SM Administration. 2. Click ERP Integration. 3. In the Supplier profile update synchronization area, check Enable external ERP approval. 4. Click Save. Configuring ERP approval of updates to supplier data in SLP: How to require ERP approval for supplier data updates in SLP This option enables tasks for External ERP approval when ever there is any change to supplier registration profile. © SAP SE AR822 49 HOME Course Title @ Copyright. All rights reserved. Supplier Lifecycle (SLP) Flow: SAP Ariba Cloud Integration specific configuration in SLP Connecting ERP vendor fields to SLP questionnaires SLP uses forms, questionnaires & internal surveys to gather information about suppliers. • To map a question to a vendor database field, a template creator needs to add questions to a supplier form, questionnaire, or internal survey in one of the supplier management project templates • Add the vendor field to the Supplier Field Mapping field on the Add Question page. • There are several field mapping values that are used only internally in SLP projects, but the majority of the values correspond directly to vendor field names in the ERP business partner model (Customer & Vendor). • The flow between ERP Vendor fields & SLP questionnaires is bi-directional. © SAP SE AR822 50 HOME Course Title @ Copyright. All rights reserved. Supplier Lifecycle (SLP) Flow: SAP Ariba Cloud Integration Gateway specific configuration in CIG In CIG, we will need to create a project for SLP Integration. Users need to perform following activities: 1. Add / update SAP System information or ensure that the information sent from your SAP System is available in CIG 2. Create the Project for SLP under Ariba Sourcing product. 3. Add a Connection. 4. Confirm & Test the project to get ready for deployment to Production. © SAP SE AR822 51 HOME Course Title @ Copyright. All rights reserved. Supplier Lifecycle (SLP) Flow: SAP Ariba Cloud Integration Gateway specific configuration in SAP System There are 4 sub activities in this section – 1. Configurations for MDG 2. Define a replication model for supplier data integration 3. Configure connection to CIG 4. Configuration to monitor errors © SAP SE AR822 52 HOME Course Title @ Copyright. All rights reserved. Supplier Lifecycle (SLP) Flow: SAP Ariba Cloud Integration Gateway specific configuration in SAP System Sub-activity 1: Configurations for MDG In the event that the customer does not have a separate MDG system and they wish to use SLP integration, the customer may choose to enable BusinessPartner related standard SAP Services. Thus, for the integration between ERP & SLP (that use the unified vendor model), the customer must activate the following business functions: • CA_BP_SOA • CA_SUPPLIER_SOA • DRF_FOUNDATION - used to send supplier info out of SAP system to Ariba SLP. • MDG license is not required to activate these above-listed business functions • Set up the customer-vendor integration(CVI), define a replication model and assign a target system for the replication model or outbound implementation. Ø CVI replicates BP as Vendor and vice-versa (as well as Customer as BP and vice-versa). © SAP SE AR822 53 HOME Course Title @ Copyright. All rights reserved. Supplier Lifecycle (SLP) Flow: SAP Ariba Cloud Integration Gateway specific configuration in SAP System Sub-activity 2: Define a replication model for supplier data integration For the outbound integration between ERP and SLP to work, you must configure the data replication settings on ERP. Please follow these steps to define a Replication Model – 1. Run the transaction code DRFIMG from the ERP user interface – The Display IMG window appears. 2. Click Data Replication>>>Define Custom Settings for Data Replication>>>Define Technical Settings>>>Define Technical Settings for Business Systems – The Change View "Define Business Systems": Overview window appears. 3. To define a new business system & to maintain the logical system for the receiving systems, click New Entries. © SAP SE AR822 54 HOME Course Title @ Copyright. All rights reserved. Supplier Lifecycle (SLP) Flow: SAP Ariba Cloud Integration Gateway specific configuration in SAP System Sub-activity 2: Define a replication model for supplier data integration For the outbound integration between ERP and SLP to work, you must configure the data replication settings on ERP. Please follow these steps to define a Replication Model (continued)- 4. In the New Entries: Overview of Added Entries window, enter the name of the Business System (Customer Site name); Logical System ID of your SAP system & RFC Destination. • RFC destination is not required or makes more sense only in case of multi-ERP for replication purpose otherwise if customer has only one ERP, it is not needed. 5. Click Save 6. Select the newly-created business system & then select Define Bus. Systems, BOs. © SAP SE AR822 55 HOME Course Title @ Copyright. All rights reserved. Supplier Lifecycle (SLP) Flow: SAP Ariba Cloud Integration Gateway specific configuration in SAP System Sub-activity 2: Define a replication model for supplier data integration For the outbound integration between ERP and SLP to work, you must configure the data replication settings on ERP. Please follow these steps to define a Replication Model (continued)- 7. Click New Entries; select the business object type (for example, Supplier), click Save. © SAP SE AR822 56 HOME Course Title @ Copyright. All rights reserved. Supplier Lifecycle (SLP) Flow: SAP Ariba Cloud Integration Gateway specific configuration in SAP System Sub-activity 2: Define a replication model for supplier data integration For the outbound integration between ERP and SLP to work, you must configure the data replication settings on ERP. Please follow these steps to define a Replication Model (continued)- 8. Go back to the Display IMG window. To define a replication model: • click Data Replication, • click Define Custom Settings for Data Replication, • click Define Replication Models © SAP SE AR822 57 HOME Course Title @ Copyright. All rights reserved. Supplier Lifecycle (SLP) Flow: SAP Ariba Cloud Integration Gateway specific configuration in SAP System Sub-activity 2: Define a replication model for supplier data integration For the outbound integration between ERP and SLP to work, you must configure the data replication settings on ERP. Please follow these steps to define a Replication Model (continued)- 9. The Change View "Define Replication Model": Overview window appears. 10. Click New Entries to enter a name for the replication model & add a description. © SAP SE AR822 58 HOME Course Title @ Copyright. All rights reserved. Supplier Lifecycle (SLP) Flow: SAP Ariba Cloud Integration Gateway specific configuration in SAP System Sub-activity 2: Define a replication model for supplier data integration For the outbound integration between ERP and SLP to work, you must configure the data replication settings on ERP. Please follow these steps to define a Replication Model (continued)- 11. Select the line that contains the newly-added replication model & click Assign Outbound Implementation. Create a new entry & enter the following values using the input help: ü Outbound Implementation: 986_3 Outbound Impl. for BP/REL via Servicesü Communication Channel: Replication via Services ü Filter time: Filter After Change Analysis *We will be using outbound implementation model as 986_3. This is SAP’s standard outbound implementation for Business Partner. © SAP SE AR822 59 HOME Course Title @ Copyright. All rights reserved. Supplier Lifecycle (SLP) Flow: SAP Ariba Cloud Integration Gateway specific configuration in SAP System Sub-activity 2: Define a replication model for supplier data integration For the outbound integration between ERP and SLP to work, you must configure the data replication settings on ERP. Please follow these steps to define a Replication Model (continued)- 12. Mark the line & choose Assign Target Systems for Repl. Model /Outb.Impl. • Create a new entry & enter the business system name for the receiving system that you created in Step 4. © SAP SE AR822 60 HOME Course Title @ Copyright. All rights reserved. Supplier Lifecycle (SLP) Flow: SAP Ariba Cloud Integration Gateway specific configuration in SAP System Sub-activity 2: Define a replication model for supplier data integration For the outbound integration between ERP and SLP to work, you must configure the data replication settings on ERP. Please follow these steps to define a Replication Model (continued)- 13. Click Assign Outbound Parameter. Create a new entry, enter the following values & save. ü Outb. Parameter: PACK_SIZE_BULK ü Outb. Parameter value: For example, 1000 © SAP SE AR822 61 HOME Course Title @ Copyright. All rights reserved. Supplier Lifecycle (SLP) Flow: SAP Ariba Cloud Integration Gateway specific configuration in SAP System Sub-activity 2: Define a replication model for supplier data integration For the outbound integration between ERP and SLP to work, you must configure the data replication settings on ERP. Please follow these steps to define a Replication Model (continued)- 14. Go back to the Define Replication Model view. Optionally, you can also add an expiration time for the log. 15. Save the replication model. © SAP SE AR822 62 HOME Course Title @ Copyright. All rights reserved. Supplier Lifecycle (SLP) Flow: SAP Ariba Cloud Integration Gateway specific configuration in SAP System Sub-activity 2: Define a replication model for supplier data integration For the outbound integration between ERP and SLP to work, you must configure the data replication settings on ERP. Please follow these steps to define a Replication Model (continued)- 16. Select the newly-created replication model & click Activate. • With this we are done for the replication model config and next we will go to DRFOUT report which will send the supplier record from ERP. • Whatever outbound implementation and replication model you have created that you have to maintain in the selection screen of thr DRFout report. © SAP SE AR822 63 HOME Course Title @ Copyright. All rights reserved. Supplier Lifecycle (SLP) Flow: SAP Ariba Cloud Integration Gateway specific configuration in SAP System Sub-activity 3: Configure connection to CIG Procedure to configure connection to CIG – 1. Run the transaction code SPRO – The Customizing: Execute Project page appears. 2. Click SAP Reference IMG –The Display IMG page appears. © SAP SE AR822 64 HOME Course Title @ Copyright. All rights reserved. Supplier Lifecycle (SLP) Flow: SAP Ariba Cloud Integration Gateway specific configuration in SAP System Sub-activity 3: Configure connection to CIG Procedure to configure connection to CIG (continued) – 3. Navigate to --> Integration with Other SAP Components -> SAP Ariba Cloud Integration Gateway -> SAP Ariba Strategic Sourcing Suite Integration -> General Settings -> Setup the Interface 4. Click Configure the connections to send messages – the Interface Setup Program for SAP Ariba Strategic Sourcing page appears. © SAP SE AR822 65 HOME Course Title @ Copyright. All rights reserved. Supplier Lifecycle (SLP) Flow: SAP Ariba Cloud Integration Gateway specific configuration in SAP System Sub-activity 3: Configure connection to CIG Procedure to configure connection to CIG (continued) – 3. Navigate to --> Integration with Other SAP Components -> SAP Ariba Cloud Integration Gateway -> SAP Ariba Strategic Sourcing Suite Integration -> General Settings -> Setup the Interface 4. Click Configure the connections to send messages – the Interface Setup Program for SAP Ariba Strategic Sourcing page appears. © SAP SE AR822 66 HOME Course Title @ Copyright. All rights reserved. Supplier Lifecycle (SLP) Flow: SAP Ariba Cloud Integration Gateway specific configuration in SAP System Sub-activity 3: Configure connection to CIG Procedure to configure connection to CIG (continued) – 5. Under Interface Setup for Web Services Ø Select one of the following to indicate if the connection is to a Production instance or a Test instance of CIG: Ø Connect to Cloud Integration Gateway Production Instance Ø Connect to Cloud Integration Gateway Test Instance Ø Select one of the following types of authentication methods: Ø Select User ID / Password & enter authentication information to connect to CIG. Ø Select X.509 SSL Client Certificate & choose the Certificate Name. Ø Enter the following values if you are using a middleware. The following fields appear only when you enable the ENABLE_MIDDLEWARE parameter in the Global Settings section: Ø URL Host: Enter the host URL for the middleware. Ø Path Prefix: Enter the path prefix for the middleware. © SAP SE AR822 67 HOME Course Title @ Copyright. All rights reserved. Supplier Lifecycle (SLP) Flow: SAP Ariba Cloud Integration Gateway specific configuration in SAP System Sub-activity 3: Configure connection to CIG Procedure to configure connection to CIG (continued) – 6. In the HTTP Proxy Options section, enter values for following fields: Ø Name of Proxy Host Ø Port Number of Proxy Host 7. Select below mention Outbound messages: Ø SLP Confirmation Out Request Ø SLP Outbound Request 8. Select below mention Inbound messages: Ø SLP Confirmation In Request Ø SLP Inbound Request 9. Click Execute © SAP SE AR822 68 HOME Course Title @ Copyright. All rights reserved. Supplier Lifecycle (SLP) Flow: SAP Ariba Cloud Integration Gateway specific configuration in SAP System Sub-activity 4: Configuration to monitor errors Errors may occur during the inbound and/or outbound transaction between ERP & CIG. In order to monitor for errors, please follow these steps: 1. Go to transaction code SRT_MONI 2. Web Service Utilities: Message Monitor window appears. 3. Specify the filters and click the Execute icon – The Web Service Utilities: Message Monitor page lists the errors, if any © SAP SE AR822 69 70© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ Sourcing Transactions Integration © SAP SE AR822 70 HOME Course Title @ Copyright. All rights reserved. About This Lesson @ Copyright. All rights reserved. Lesson 1: Overview By the end of this lesson, you will be able to: • Recognize supported and unsupported transactions via SAP Ariba Sourcing • Illustrate the Sourcing Transactions Integration Process © SAP SE AR822 71 HOME Course Title @ Copyright. All rights reserved. Overview Sourcing Transactions Integration Overview SAP Ariba Sourcing solutions integrated with SAP system(s) via CIG can export transactional data to SAP system(s) via the following methods: ü Direct Connectivity using SAP Cloud Connector ü Mediated Connectivity using SAP PI / PO or SAP CPI Note: In this session we will explore the Direct Connectivity flow. The SAP Ariba Sourcing integration is technically realized via the Ariba Network as the central entry (and exit) point to allow the sourcing professional to determine the best way to source the spend. © SAP SE AR822 72 HOME Course Title @ Copyright. All rights reserved. Overview • Request for Quotation (RFQ) • Award / Quote Message (QM) • Contract Request (CR) • Scheduling Agreement (SA) • Purchase Info Record (PIR)• Bill of Materials integration (BOM) Supported transactions: • SAP Ariba Supplier Information and Performance Management Un-supported transactions: © SAP SE AR822 73 HOME Course Title @ Copyright. All rights reserved. Overview: Integration process Sourcing Transactions Integration Process Overview Ø From SAP System, Purchasing Organization or Buyer creates Purchase Requisition having material items or service items & based on that Purchase Requisition, RFQ or Quote Request can be created. Ø RFQ can also be created directly in SAP System without referring to a Purchase Requisition. Ø The RFQ gets sent to SAP Ariba Sourcing via CIG & Ariba Network which will then create a Sourcing Request in Ariba Sourcing. CIG creates a cXML QuoteRequest document that contains specific information required to create a Sourcing Request. Ø To generate a Sourcing Request, a Request for Quotation created in SAP System must be defined as a Strategic Sourcing Document Type. SAP System requires a mandatory vendor field in RFQ, so users need to create a “placeholder supplier” for strategic sourcing documents. Ø Strategic sourcing documents are converted into a cXML QuoteRequest document & the placeholder vendor information is automatically discarded during conversion in CIG. • if various departments have a requirement for a laptop bag, then all these are aggregated into a PR. • Purchase requisitions are internal documents you use to request your Purchasing department to procure a particular quantity of a material or a service for a particular date. • Purchase requisitions are either created manually by the department responsible or automatically by MRP. • The Purchase Dept. in the Organization calls / requests for the quotation for the products against which PR was raised. © SAP SE AR822 74 HOME Course Title @ Copyright. All rights reserved. Overview: Integration process overview Integration Process Overview (continued) - Ø SAP Ariba Sourcing processes the QuoteRequest & creates a Sourcing Request. A Sourcing Manager approves the request, creates a Sourcing Event & invites suppliers to participate in the bid based on the criteria specified in the QuoteRequest document & the Sourcing Request template. Ø Once suppliers are invited, notification email will be sent to them for participating in bidding process. Ø Suppliers bid on the Sourcing Event & Ariba Sourcing creates an Award for the winning bid. Ariba Sourcing sends the award as a QuoteMessage back to the SAP system. Ø Based on the information in the QuoteMessage for the award, either a Purchase Order or a Contract will get created in the SAP system. © SAP SE AR822 75 HOME Course Title @ Copyright. All rights reserved. Overview: Integration process overview Integration Process Overview (continued) - Ø SAP system sends a confirmation to Ariba Sourcing after creating a Purchase Order or a Contract. Ø When Ariba Contracts sends a Contract, CIG creates a Contract on the SAP system & sends a response confirming the creation of the Contract on the SAP system. It also sends a confirmation when the Contract has been updated or deleted on the ACM. Ø The confirmation message contains the Purchase Order ID or Contract ID & the status code. A status code of 200 when received successfully else it will be treated as failure to create the Purchase Order or Contract. Ø Buyers can create a Sourcing Event or Contract Line Items Document (CLID) directly from Ariba Sourcing or Ariba Contracts. These Sourcing Events do not need an associated QuoteRequest from the SAP system. • If users create a custom StrategicSourcingDocType & select that custom document type when creating a RFQ, then they must maintain the same custom document type in SAP Ariba Cloud Integration Gateway cross reference section. • For details of Prerequisites & Limitations of RFQ; QM & Contract, please refer to SAP Ariba Cloud Integration Gateway Overview Guide. © SAP SE AR822 76 HOME Course Title @ Copyright. All rights reserved. SAP Ariba Strategic Sourcing – Request for Quotation & Award © SAP SE AR822 77 HOME Course Title @ Copyright. All rights reserved. SAP Ariba Strategic Sourcing – Contract Scheduling Agreement © SAP SE AR822 78 HOME Course Title @ Copyright. All rights reserved. About This Lesson @ Copyright. All rights reserved. Lesson 2: Request for Quotation (RFQ) Flows 2.1 Configure in SAP System I. Global settings II. General settings a. Interface b. BAdIs III.Transaction specific settings a. Message output b. Maintain parameters c. Customer exit d. SRVMAPKEY 2.2 Configure in CIG I. Cross-reference config 2.3 Configure in Ariba Network I. AN Admin Activities II. AN Buyer Account Admin Activities 2.4 Configure in SAP Ariba Sourcing I. Sourcing ERP © SAP SE AR822 79 HOME Course Title @ Copyright. All rights reserved. Request for Quotation (RFQ) Flows SAP System users can create & send a RFQ as follows: Ø By creating a request for quotation from the SAP ERP System & sending a QuoteRequest cXML document to Ariba Sourcing. Ø By creating an RFQ event that originates in the SAP ERP system & sending it across to Ariba Network, where an RFQ event is created & published on SAP Ariba Discovery. SAP System users can create RFQ with material items or service line items as follows: Ø By creating a new Request for Quotation Ø By creating a Request for Quotation against a Purchase Requisition Ø By creating a Request for Quotation against a Contract (Outline Agreement) ü SAP System users can add one or multiple service items in a RFQ. ü The request for quotation can include service item (category D) with up to five-level hierarchy (one parent item and four-level Outline hierarchy). ü Users can send attachments & comments from SAP System to Ariba Sourcing solutions. ü Attachments at the header-level & line item-level for new & change RFQ are supported. ü To add attachments to RFQ, users need to configure the DMS on SAP System. ü The size of the attachments for both inbound & outbound documents cannot exceed 100 MB. Attachments can additionally have a payload of up to 40 MB. ü If the attached file is encrypted or protected with password, Ariba Network does not decrypt the file for the end user of the attachment. ü Text descriptions at the header-level & line-item level for internal & external users are supported. ü If user creates a RFQ against a Purchase Requisition, the text description for both the internal & external users available in the Purchase Requisition appears in the RFQ. © SAP SE AR822 80 HOME Course Title @ Copyright. All rights reserved. Request for Quotation (RFQ) Flows Limitations: ü SAP System supports file name of attachments up to 50 characters including extension. ü SAP System supports maximum 40 characters in line item text for create & change Request For Quotations . ü Attachments for service line items in Request For Quotations are supported only at the parent line level & not at the specification line level. For more information on limitations, please refer to the SAP Ariba Cloud Integration Gateway Overview Guide. © SAP SE AR822 81 HOME Course Title @ Copyright. All rights reserved. 2.1 RFQ Flows: Configure in SAP System There are 3 sub activities in this section: I. Global settings II. General settings a. Interface Setup b. BAdIs III.Transaction specific settings a. Define Message Output Control Maintain parameters b. Interface Setup c. Implement Customer Exit d. Configure SRVMAPKEY © SAP SE AR822 82 HOME Course Title @ Copyright. All rights reserved. Global Settings Ensure that following configurations of the Global Settings section are in place – ü Maintain Certificates ü Create RFC Destination ü Create Port Definition ü Create Logical System ü Send SAP Information to CIG ü Maintain Parameters for Attachments Support ü Maintain BAdIs as per your requirements Further details regarding these configurations are covered within learning unit: AddOn – SPRO Configuration 2.1 RFQFlows: Configure in SAP System Global Settings © SAP SE AR822 83 HOME Course Title @ Copyright. All rights reserved. 2.1 RFQ Flows: Configure in SAP System - General Settings General Settings are configured by the User in order to send/receive documents between CIG, the SAP System & SAP Ariba Sourcing solutions. There are two areas that must be configured: a. Setup the Interface b. BAdIs for setting up the Interface Navigate to General Settings in SAP ERP and SAP S/4 HANA for Ariba Network Transactions: ü Run the transaction code SPRO, the Customizing: Execute Project screen appears. ü Click SAP Reference IMG, the Display IMG screen appears. ü Navigate to – Integration with Other SAP Components >>> SAP Ariba Cloud Integration Gateway >>> SAP Ariba Strategic Sourcing Integration >>> General Settings © SAP SE AR822 84 HOME Course Title @ Copyright. All rights reserved. 2.1 RFQ Flows: Configure in SAP System - General Settings: Setup the Interface Setup the Interface Ø This task is a one-time activity. Ø This will establish endpoints for Web Services. Ø The Logical Port setting is overwritten each time you run the interface settings for outbound web services. Ø You can execute the interface settings any time there is an update relevant to outbound web services. © SAP SE AR822 85 HOME Course Title @ Copyright. All rights reserved. 1. Navigate to Setup the Interface under SAP Ariba Strategic Sourcing Integration >>> General Settings >>> Setup the Interface using the transaction code SPRO. + + 2. Expand Setup the Interface & click IMG-Activity for Configure the Connections to Send Messages – The Interface Setup Program for Ariba Strategic Sourcing screen appears. 2.1 RFQ Flows: Configure in SAP System - General Settings: Setup the Interface © SAP SE AR822 86 HOME Course Title @ Copyright. All rights reserved. 3. In the Interface Setup for IDOC section: Ø Tick the Quote Request check box to set up the IDOC for outbound document. Ø Enter the Logical System name in the Receiver Logical System field to send the documents from the SAP System to CIG. Ø Enter the port name in the Receiver Port Name. 4. In the Interface Setup for Web Service section, either click Select All to select all listed transactions for both Outbound & Inbound flows or select the flows individually. Web Services is required for QM(Inbound)) 2.1 RFQ Flows: Configure in SAP System - General Settings: Setup the Interface © SAP SE AR822 87 HOME Course Title @ Copyright. All rights reserved. 5. In the Logon Data section: Ø Select one of the following to indicate if the connection is to a Production instance or a Test instance of CIG: ü Connect to Cloud Integration Gateway Production Instance ü Connect to Cloud Integration Gateway Test Instance Ø Select one of the following types of authentication methods: ü Select User ID / Password & enter authentication information to connect to CIG. ü Select X.509 SSL Client Certificate & choose the Certificate Name. 6. In the HTTP Proxy Options section, enter values for following fields: Ø Name of Proxy Host Ø Port Number of Proxy Host 7. Select Outbound Messages if already not selected, then click Execute. 2.1 RFQ Flows: Configure in SAP System - General Settings: Setup the Interface © SAP SE AR822 88 HOME Course Title @ Copyright. All rights reserved. Upon running the report, you will get to see the results as shown in this example: After you run the report, you can also view the status of the report message status using the TCode SLG1, using the object: ARBACIG_INTERFACE, and sub-object: IF_LOGS. 2.1 RFQ Flows: Configure in SAP System - General Settings: Setup the Interface © SAP SE AR822 89 HOME Course Title @ Copyright. All rights reserved. If you are using middleware: 1. Make sure that middleware parameter is enabled – ENABLE_PI_MIDDLEWARE or ENABLE_MIDDLEWARE 2. Also ensure that you have maintained required configuration under Global Settings >>> Customize SLD API and Integration Engine-Admin for PI Integration as discussed in Integration using SAP PI / PO Middleware section. 3. Setup the Interface under SAP Ariba Strategic Sourcing Integration >>> General Settings using the transaction code SPRO 4. Configure Interface Setup as described in step#1 to step#7 in the earlier slides. Additionally, you will need to provide following information in the step#5, the Logon Data section: Ø URL Host: Middleware host URL Ø Path Prefix: Middleware path prefix 2.1 RFQ Flows: Configure in SAP System - General Settings: Setup the Interface © SAP SE AR822 90 HOME Course Title @ Copyright. All rights reserved. BAdIs definition: A business add-in (BAdI) is a source code plug-in provided by SAP to enhance existing ABAP code. The enhancement technique uses the object-oriented method and business add-ins to map the specific requirements involved in business process. These are customer specific, and are not provided by standard code in SAP. Implementation of BAdI(s) is optional. When setting up the interface, you can optionally implement the BAdI to modify any parameters. • This BAdI is used for all the Ariba solutions. The parameter IP_SOLUTION indicates the Ariba solution for which BAdI is configured. • Based on the solution you require, choose one of the possible values in the IP_SOLUTION field: 1. BUY - SAP Ariba Buying and Invoicing 2. SRC - SAP Ariba Sourcing and SAP Ariba Contracts 3. AN - Ariba Network 2.1 RFQ Flows: Configure in SAP System - General Settings: Setup BAdIs © SAP SE AR822 91 HOME Course Title @ Copyright. All rights reserved. BAdI implementation steps: 1. Navigate to SAP Ariba Strategic Sourcing Integration >>> General Settings >>> Setup the Interface using the transaction code SPRO. 2. Click IMG-Activity for the Business Add-Ins (BAdIs) – the Create Enhancement Implementation pop-up appears. 3. Implement the BAdI Ø BAdI name: ARBCIG_AUTO_INTERFACE Ø Implementation methods: • CHANGE_MESSAGE_OUT: To change message parameters for outbound IDocs • CHANGE_MESSAGE_IN: To change message parameters for inbound IDocs • CHANGE_PARTNER_HEADER: To change partner header for IDocs • CHANGE_OUT_IDOC_IN: To change outbound IDocs message control • CHANGE_PROXY: To change parameters when setting up service name or logical port for proxies 2.1 RFQ Flows: Configure in SAP System - General Settings: Setup BAdIs © SAP SE AR822 92 HOME Course Title @ Copyright. All rights reserved. Transaction Specific Settings (TSS) Navigate to configure Ariba Network transactions: 1. Run the truncation code SPRO – the Customizing: Execute Project screen appears 2. Click SAP Reference IMG – the Display IMG screen appears 3. Navigate to Integration with Other SAP Components >>> Ariba Cloud Integration Gateway >>> Ariba Strategic Sourcing Integration >>> Application Specific Settings 2.1 RFQ Flows: Configure in SAP System - Transaction Specific Settings (TSS) © SAP SE AR822 93 HOME Course Title @ Copyright. All rights reserved. For sending RFQ to CIG & then to SAP Ariba Sourcing, you need to perform following activities – i. Define Message Output Control for Request for Quotation ii. Maintain parameters for Request for Quotation iii. Implement a Customer Exit for Request for Quotation iv. Configure the SRVMAPKEY for Service Purchase Order 2.1 RFQ Flows: Configure in SAP System - Transaction Specific Settings (TSS) © SAP SE AR822 94 HOME Course Title @ Copyright. All rights reserved. Buyer users need to maintain the condition records & output types to process RFQs sent from the SAP System. To maintain the condition records & output types: 1. Navigate to Integration with Other SAP Components >>> Ariba Cloud Integration Gateway >>> SAP Ariba Strategic Sourcing Integration >>> Application Specific Settings >>> Request for Quotation (RFQ) using the transaction code SPRO. 2. Expand Request for Quotation (RFQ) section & click IMG-Activity for Define Message Output Control for Request for Quotation – TheConditions for Output Control page appears. 3. Select application EA & click Output Types. The Display View "Output Types": Overview page appears. 2.1 RFQ Flows: Configure in SAP System - Transaction Specific Settings (TSS) Activity i. Define Message Output Control for Request for Quotation © SAP SE AR822 95 HOME Course Title @ Copyright. All rights reserved. To maintain the condition records & output types (continued) – 4. Click the output type maintained for the RFQ. (example: choose NEU), click Change. The Change View "Output Types": Overview page appears. 5. Click New Entries, the New Entries: Details of Added Entries screen appears. 6. On the General Data tab, select 0001 DocType/PurchaseOrg/Vendor in the Access sequence field. 2.1 RFQ Flows: Configure in SAP System - Transaction Specific Settings (TSS) Activity i. Define Message Output Control for Request for Quotation © SAP SE AR822 96 HOME Course Title @ Copyright. All rights reserved. To maintain the condition records & output types (continued) – 7. On the Default tab, enter the following values: ü Dispatch time: Send immediately (when saving the application) ü Transmission Medium: EDI ü Partner Function: LS 8. Click Save 9. Click the output type maintained for the request for quotation. For example, NEU & double-click Processing routines. The Change View "Processing routines": Overview page appears. 10. In the Processing routines section, create an entry as follows: ü Transmission Medium: EDI ü Program: RSNASTED ü FORM routine: EDI_PROCESSING 2.1 RFQ Flows: Configure in SAP System - Transaction Specific Settings (TSS) Activity i. Define Message Output Control for Request for Quotation © SAP SE AR822 97 HOME Course Title @ Copyright. All rights reserved. To maintain the condition records & output types (continued) – 12. In the Partner Functions section, create an entry as follows: ü Medium: EDI ü Function: LS ü Description: Logical System 13. Save the changes & go to the Conditions for Output Control page. 14. Click the output type maintained for the request for quotation (example: NEU), double-click Condition records. The Output Types dialog box appears. 15. Click the relevant output type (example: NEU), click Condition records – the Key Combination popup appears. 2.1 RFQ Flows: Configure in SAP System - Transaction Specific Settings (TSS) Activity i. Define Message Output Control for Request for Quotation © SAP SE AR822 98 HOME Course Title @ Copyright. All rights reserved. To maintain the condition records & output types (continued) – 16. Click the Purchasing Output Determination: Doc Type/Purch. Org./Vendor, click Enter 17. Maintain the following parameters by creating a new entry: ü Purchasing Doc Type: Choose a purchasing doc type. For example, AN. ü Purch. Organization: Choose a purchasing organization. ü Vendor: Choose a vendor. 18. Click Save 19. Click Execute 2.1 RFQ Flows: Configure in SAP System - Transaction Specific Settings (TSS) Activity i. Define Message Output Control for Request for Quotation © SAP SE AR822 99 HOME Course Title @ Copyright. All rights reserved. Buyer users need to maintain the parameters to send the text descriptions at the header-level & line-item level for internal & external users in RFQ. To maintain the text descriptions parameters: 1. Navigate to Integration with Other SAP Components >>> Ariba Cloud Integration Gateway >>> SAP Ariba Strategic Sourcing Integration >>> Application Specific Settings >>> Request for Quotation (RFQ) using the transaction code SPRO. 2. Expand Request for Quotation (RFQ) section & click IMG-Activity for Maintain parameters for Request for Quotation – the Parameters – Request for Quotation page appears. 3. Maintain the parameters as mentioned in the table within this activity. 2.1 RFQ Flows: Configure in SAP System - Transaction Specific Settings (TSS) Activity ii. Maintain parameters for Request for Quotation © SAP SE AR822 100 HOME Course Title @ Copyright. All rights reserved. 2.1 RFQ Flows: Configure in SAP System - Transaction Specific Settings (TSS) Activity ii. Maintain parameters for Request for Quotation Variable Name Required for.. Field Name Number Variant Partition Low RFQ_EXTERNAL_NOTE To send the long text description specified at the header-level for external users in the Request for Quotation EKKO 0 The unique variant name for the SAP Ariba Sourcing solution in SAP System. The unique site name for the SAP Ariba Sourcing solution in SAP System. Enter the text ID for the long text description for external users. A01 (For example). RFQ_EXTERNAL_NOTE To send the long text description specified at the line-item level for external users in the Request for Quotation EKPO 0 The unique variant name for the SAP Ariba Sourcing solution in SAP System. The unique site name for the SAP Ariba Sourcing solution in SAP System. Enter the text ID for the long text description for external users. A01 (For example). RFQ_INTERNAL_NOTE To send the long text description specified at the header-level for internal users in the Request for Quotation EKKO 0 The unique variant name for the SAP Ariba Sourcing solution in SAP System. The unique site name for the SAP Ariba Sourcing solution in SAP System. Enter the text ID for the long text description for internal users. A03 (For example). RFQ_INTERNAL_NOTE To send the long text description specified at the line-item level for internal users in the Request for Quotation EKPO 0 The unique variant name for the SAP Ariba Sourcing solution in SAP System. The unique site name for the SAP Ariba Sourcing solution in SAP System. Enter the text ID for the long text description for internal users. A03 (For example). RFQ_ENABLED To enable the RFQ integration. This parameter setting allows SAP Ariba Sourcing to receive and process RFQs from SAP system. 0 The unique variant name for the SAP Ariba Sourcing solution in SAP System. The unique site name for the SAP Ariba Sourcing solution in SAP System. Enter X to enable the RFQ integration. © SAP SE AR822 101 HOME Course Title @ Copyright. All rights reserved. 2.1 RFQ Flows: Configure in SAP System - Transaction Specific Settings (TSS) Activity iii. Implement a Customer Exit for Request for Quotation Buyer users need to implement the following customer exit for RFQ. Users can enhance the RFCs provided by Ariba by adding customer exits or make changes to enhancement points. To implement customer exit for RFQ: 1. Navigate to Integration with Other SAP Components >>> Ariba Cloud Integration Gateway >>> SAP Ariba Strategic Sourcing Integration >>> Application Specific Settings >>> Request for Quotation (RFQ) using the transaction code SPRO. 2. Expand Request for Quotation (RFQ) section & click IMG-Activity for Implement a Customer Exit for Request for Quotation – The Project Management of SAP Enhancements page appears. 3. Provide Project name, click Create 4. Click Enhancement Assignments – the Create Object Directory Entry pop-up appears. © SAP SE AR822 102 HOME Course Title @ Copyright. All rights reserved. 2.1 RFQ Flows: Configure in SAP System - Transaction Specific Settings (TSS) Activity iii. Implement a Customer Exit for Request for Quotation To implement customer exit for RFQ (continued) - 5. Provide an existing Package name (or click Local Object) 6. Enter the user exit name, MM06E001, press Enter 7. Go back & click Components © SAP SE AR822 103 HOME Course Title @ Copyright. All rights reserved. 2.1 RFQ Flows: Configure in SAP System - Transaction Specific Settings (TSS) Activity iii. Implement a Customer Exit for Request for Quotation To implement customer exit for RFQ (continued) – 8. Double-click the enhancement EXIT_SAPLEINM_002 9. In the next screen that appears, scroll down, double-click INCLUDE ZXM06U02, press Enter 10. Copy & paste the code INCLUDE arbcig_quote_request_002, click Activate © SAP SE AR822 104 HOME Course Title @ Copyright.
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
- CCFA-200 Exam Questions Supreme Preparation Supply
- CPC-SEN Exam Questions Effortless Method To Clear Exam