<p>about your learning experience to help us improve.</p>

You've completed

cleanFiles/bookmap_SystemSetupGuide_v2-3_en-US_learning-sap-com_lsc-prod.zip (MMCP-DROPZONE) - 2023-10-25T12:50:34.000Z

Implementing Steps for Integration

<div id="content"><div class="parentsection"><div class="section"><p tabindex="0">Integration involves 3 main steps: Getting the environment ready, configuring the solution, and then reviewing and deploying the solution. The three videos in this unit will provide you with a high level overview of these steps.</p></div></div><div class="parentsection"><div class="section"><div tabindex="0"><h3>Step 1: Getting the Environment Ready</h3></div><p tabindex="0"></p><div class="kalturaVideoLessonWrapper"><div id="1_cy4faaz2" data-testid="video" class="kalturaVideoLessonContainer"></div></div></div></div><div class="parentsection"><div class="section"></div></div><div class="parentsection"><div class="section"><div tabindex="0"><h3>Step 2: Configuring the Solution</h3></div><p tabindex="0"></p><div class="kalturaVideoLessonWrapper"><div id="1_6uw3zyz7" data-testid="video" class="kalturaVideoLessonContainer"></div></div></div></div><div class="parentsection"><div class="section"><div tabindex="0"><h3>Step 3: Reviewing and Deploying</h3></div><p tabindex="0"></p><div class="kalturaVideoLessonWrapper"><div id="1_v2sgzoe0" data-testid="video" class="kalturaVideoLessonContainer"></div></div></div></div></div>

Steps to Integration

Administering SAP Integration Suite, managed gateway for spend management and SAP Business Network

Integration Part 1.mp4

In an earlier lesson, we learned about the buyer landscape in a typical CIG integration scenario. In this lesson, we will discuss the activities or steps involved in configuring the CIG add-on solution end-to-end and deploying the CIG project. These are high-level steps and each one of the steps may involve various activities. Please note that these are just guidelines and should not be considered as SAP Ariba recommendations. For better understanding, these activities are categorized into three logical groups. A. Getting the environment ready B. Configuring the solution and C. In this video, we will discuss the activities involved in getting your environment ready. The first activity is to download and install the CIG add-on software components. Based on your backend on-premise SAP system type, which could be SAP ECC or SAP S4HANA on-premise, you need to download the relevant CIG add-on software components from SAP Service Marketplace and install it on your SAP system. This activity is typically carried out by SAP basis team in your project. The next activity is to enable CIG. You will need to enable CIG from your SAP Ariba solution based on your respective SAP Ariba subscription. This is an important step which needs to be performed in the initial phase of your project. This establishes connectivity of the Ariba solution with CIG. By enabling CIG, you will be receiving information about the P user ID which gets assigned to you. The P user information is needed in many configuration activities. The next activity is to download, install, and configure SAP Cloud Connector. Here you would need to download the software component for the SAP Cloud Connector from SAP Development Tools Portal based on the operating system of the machine on which you want to install SAP Cloud Connector. This is a very lightweight component which can be installed in a few minutes. Once installation is successful, you will need to configure the SAP Cloud Connector to receive documents from CIG which are inbound to your backend on-premise SAP system. The next activity is to define global settings in CIG add-on SPRO. These are the set of configuration activities which are mandatory irrespective to the SAP Ariba solution you are adopting. The configurations done here will be used across the integration flows, such as Ariba Network Integration, SAP Ariba Sourcing Integration, and SAP Ariba Buying and Invoicing Integration. The main activities are Maintain Certificates, Define RFC Destination, Define Port Definition, Define Logical System, Configure Receiver Port, and Map the Variant and Partition for SAP Ariba solutions. Then in the next activity, you will send SAP information to CIG. In this activity, you will execute a pre-delivered report in CIG Add-on SPRO to send specific information to your CIG account. This information is unique to your SAP system and critical for achieving integration via CIG. You can choose to enter this information manually in your CIG portal directly, but SAP Ariba strongly recommends sending the information using this automated report to avoid any kind of human errors. After sending SAP information to CIG, you will need to start creating an integration project. An integration project needs to be created for a specific product such as network integration, sourcing integration, or procurement integration. Project creation is an activity which you will complete in phases. At any point, you can save the project data you have entered and resume the remaining activities at a later stage as necessary. And finally, setup middleware. This is an additional but optional activity in the situation where you are deploying the solution with the mediated connectivity option. Here you will need to install and configure the pass-through components provided for the specific middleware, SAP PI or SAP CPI Private Tenant.

Integration Part 2.mp4

In the earlier video, we discussed the activities involved in getting your environment ready. Now in this video, let's talk about the next group of activities that are required to configure the solution. The first activity in this group is to maintain general settings in CIG add-on SPRO. These are the set of configuration activities which are mandatory for a specific integration irrespective of how many documents you are adopting under that integration. Each integration, such as Ariba Network Integration, SAP Ariba Sourcing Integration, and SAP Ariba Buying and Invoicing Integration, has its own and separate activity of general settings. The main activity here is to execute Set Up the Interface program. This program will automatically create inbound and outbound parameters in the Partner Profile for IDOC type documents, Service Definition and Logical Ports in SOA Manager for proxy or web service type documents. The next activity is to import master data. In the scenario where you have subscription to any of the SAP Ariba sourcing or SAP Ariba buying and invoicing features, you would need to have necessary configurations in place in order to import master data objects from your back-end on-premise SAP system into SAP Ariba application. Please note that your SAP system will always be the source of truth for master data. There is a specific report provided in CIG add-on to extract required master data objects and send that to your SAP Arriba realm. The next activity is configuring the transactions or documents. In this activity you will be working on configuring transaction flows or documents which are involved in the integration solution you have subscribed for. In CIG add-on SPRO, there are separate nodes available for each of the transaction or documents under a specific integration such as network integration, sourcing integration, or procurement integration. These nodes have a set of activities arranged in the sequential manner for you to complete your configuration for a specific transaction document in the given order. After that, you need to specify cross-reference values in the CIG project for the documents you are adopting. Here you will need to specify values additionally for mappings and lookups for certain predefined fields in CIG Portal. This activity goes hand in hand with configuring transactions in CIG Addon SPRO. So ideally, you should perform this activity for a specific transaction or document concurrently with configuring transactions in CIG add-on SPRO. Until here, you have completed all the basic configurations and you can proceed with implementing extensions in BADIS and SAP system. Once all the basic configuration for required transactions or documents are in place, you can proceed with customizing the standard integration mappings to accommodate your business-specific requirements. In CIG Add-on, SAP Ariba has provided numerous customer exits and BADIS to address your customization requirements. In order to complete your deployment cycle swiftly, SAP Ariba strongly recommends having customization requirements identified at the initial stage of the project itself. Lastly, after addressing your customization requirements in SAP System, you need to map the custom fields via a mapping tool. In the CIG portal, the custom mapping tool helps you quickly map custom fields of source document with target document. There are various node functions available to define additional logic in custom mapping. However, it is always recommended that you maintain customizations with complex logic in your source system or application. Derive the field value you want to map and then use the custom mappings tool in the CIG portal to map the source field with the target field.

Integration part 3.mp4

In earlier two videos, we discussed the activities involved in getting your environment ready and configuring the solution. Now, in this video, let's talk about the last group of activities that are required to configure the solution. The first activity in the group is to review CIG project configuration. In CIG Portal, once all project creation steps are completed, you have an option to review the configuration done in each step. Make sure that all the values defined are accurate and correspond to the respective environment, test or production. Don't confirm the project before review, and then only proceed with testing. The next activity is Testing CIG Project. Once the project is reviewed and confirmed, you can proceed with testing the configured transaction documents. The CIG provides you with two options. First, automated testing using the Test Central tool, which is a much faster way of completing the testing of your business use cases. Next, manual testing, where you will adopt the conventional approach of having your testing team execute all the business use cases manually. Please note, if you wish to use Test Central, you need to have Required Configuration in place. The final activity is CIG Project Deployment. Once the testing of all required business use cases is done and your testing confirms that the results, which indicates all the required quality criteria are achieved, you can deploy the CIG project to production. It means your CIG project will be available in your production environment and you can start transacting in real time with your vendors. Please note that deploying CIG projects to production does not change the process of moving from test or quality landscape to production landscape of your back-end or on-premise SAP system. You still need to manage that separately as usual. This is how you can have your landscape configured and ready for end-to-end document flow.