Go Coding

Author: Rudramani Pandey

  • How to Deploy BSP Application on the Fiori Launchpad

    Introduction

    In this article we will discuss how to deploy BSP Application on the Fiori Launchpad. If you are looking to deploy your UI5 Application directly on the Fiori Launchpad to the Neo Environment, then click here and if to the Cloud Foundry Environment, then click here.

    A BSP Application stands for Business Server Page Application is a Web Application created using UI5/Fiori and executed in a web browser. It is an on premise UI5 Application. In this article we will not focus upon the creation and processing of BSP Application rather focus on its deployment over the Launchpad.

    Prerequisite

    Following are the prerequisite of the BSP App Deployment:

    • You need to have a UI5 Application already in place and ready for deployment
    • The UI5 App should have a unique App id maintained in manifest.json
      How to Deploy BSP Application on the Fiori Launchpad
    • The WebIDE should be connected to the respective SAPUI5 ABAP Repository System
      How to Deploy BSP Application on the Fiori Launchpad
    • The UI5 App should be error free and no duplicate ID’s should be used throughout the App
    • You should have a package and transport requests (both workbench and customizing request) in place

    Steps to Deploy BSP Application on the Fiori Launchpad

    1.      Upload the SAP UI5 Application as a BSP Application to the Gateway Server

    2.      Create a Launchpad Role in LPD_CUST Transaction

    3.      Create a Semantic Object in /UI2/SEMOBJ Transaction

    4.      Create a Catalog, Target Mapping and Static Tile

    5.      Create a Group and Add the Catalog

    6.      Create a PFCG Role for the Catalog and Group

    7.      Test your App on Fiori Launchpad

     

    Errors Faced During Deployment

    While deploying a UI5 Application as a BSP application, you might face given errors:

    • You don’t have the needed Authorizations to deploy
    • Authorization error when connecting to Gateway from WebIDE
    • You get an error when your system is selected in the first step of the wizard
    • WebIDE deploy error ,Not able to access Gateway system from WEB IDE
    • CSRF token validation failed while deploying extended fiori application to ABAP Repository
    • Cannot select the system. Check the configuration for ABAP Development Tools
    • Error Connecting to ABAP Repository from webIDE.
    • CSRF token validation failed” error when trying to reach /sap/bc/adt/cts/transportchecks service
    • Cannot deploy application XYZ: Remote creation in customer namespace not possible
    • Cannot deploy application XYZ: SAP object YYY cannot be assigned to package ZZZ
    • No development license for user XYZ
    • Object X is already locked in request Y of user Z
    • Cannot deploy the application. Virus scan server error. No virus scan profile is selected as the default
    • Cannot deploy the application: Request XYZ is not a local request
    • Cannot deploy application <app name>: HTTP Status 504 – An internal application error occurred
    • Cannot deploy application <app name>: Resource XYZ does already exist
    • File <namespace/<app name>/index.html NOT found!

    If you face any of the error mentioned above, follow the given steps to trace the error root cause:

    1. Run ST22 transaction to check any dump raised in backend
    2. Run /IWFND/ERROR_LOG transaction to check Gateway error log
    3. Run your Inspect Element in browser (Ctrl + Shift + I) and read the error and the solution mentioned there
    4. Check the error resolution mentioned here
    5. Check SAP Notes for your error here

  • SAP Ariba Mapping Workbooks

    Preface – This post is part of the SAP Ariba series.

    Introduction

    SAP Ariba Mapping Workbooks are the sample files provided by Ariba that is used for the inbound and outbound transactions of data between SAP Ariba Procurement Solutions and SAP ERP. In the outbound transaction of data, data is transformed from Xml file format to cXml format and then imported to Ariba Procurement Solution. Similarly, for inbound data transactions, data is transformed from cXml to Xml file format and then pushed to the SAP ERP system.

    As mapping workbooks are just the sample files, it can be customized based on business needs. The organization can customize the mapping of fields between Xml and cXml depending upon the organization‘s requirements. The mapping workbooks contain information about the manner in which fields are mapped between Xml and cXml files. You can download the workbook from connect.ariba.com.

    How to download the SAP Ariba Mapping Workbooks

    Below are the steps to download the mapping workbooks:

    1. Log in to connect.ariba.com by providing valid credentials (user ID and password). In case you do not have a user ID and password contact your Ariba Account executive.
    2. On the Home tab, in Product Summary page click on Ariba Cloud Integration. On click, it will open the Ariba Cloud Integration page.
    3. In the Ariba Cloud Integration page under the Integration Toolkit section, click Integration Tools for Ariba Procure-to-Pay. This will open Integration Tools for Ariba Procure-to-Pay page.
    4. Under this navigate to Integration Tools for SAP, go to Tool and click on Mapping Workbooks.

    This will open the Mapping Workbooks for Ariba Procurement Solutions Integrated with SAP for Cloud Integration X.0 page.

    1. Click on download and provide the download location to download the mapping file in your system. The mapping workbooks for all the transactions will be downloaded in ZIP format.
    2. Extract the downloaded file and customized the mappings are per the business needs.

  • SAP Ariba – SAP ERP Transports

    Preface – This post is part of the SAP Ariba series.

    Introduction

    For integrating SAP Ariba Procurement Solution to SAP ERP you must download and import SAP ERP transports to your Procurement Solution. The installation process is the same for first-time installation as well as for the upgrades. You must specify a target client when adding the transports to the import queue. Defining the target client is needed as the transports contain both clients dependent as well as client independent configurations. To specify the target client you should use T-code STMS (SAP Transport Management System).

    The sequences to install the transport are provided in Readme.txt file present in the ZIP file downloaded from connect.ariba.com. For real-time integration of SAP ERP to SAP Ariba Procurement Solution, you need to configure SAP ERP after the import of transport is completed.

    SAP Ariba – SAP ERP Transports: Transport Management System Configuration

    Steps to configure TMS:

    1.      Domain Controller setup

    1. Open Sap Logon and log in to the system which is decided to be Domain Controller
    2. In client 000, go to transaction STMS
    3. The system will ask you to create the transport domain if the Domain Controller is not configured. Select the create proposal and save
    4. If the domain controller is already present, you will be logged onto the domain controller.

    2.      Adding SAP system to Transport Domain

    1. Log on to the SAP system that is to be added as the domain.
    2. In client 000, go to transaction STMS
    3. TMS will check the configuration file cfg and propose to join the domain if Domain Controller is already present and the system is not added.
    4. System status will be waiting as it still needs the approval to be included in the transport domain
    5. To approve, logon to Domain Controller system. In client 000, go to transaction STMS and navigate to Overview and then click Systems.
    6. New systems are visible. Go to SAP System and Approve.

  • SAP Ariba Integrating Transactional Data

    Preface – This post is part of the SAP Ariba series.

    Introduction

    Before going into the SAP Ariba Integrating Transactional Data we will understand what is transaction data, what type of business information comes under transaction data and some important T-codes in sap related to transaction data.

    Transaction data is a business document that is created out of master data like material master data, vendor master data and keeps changing on a daily basis. A daily transaction detail, production details come under transaction data.

    SAP Ariba Integrating Transactional Data

    In SAP Ariba transaction data includes invoice, receipt, purchase order.

    Important transactions for Transaction Data:

    • Invoice : MIRO
    • Goods receipt : MIGO
    • Purchase Order: ME21n, ME22n, ME23n
    • Sales Order: VA01, VA02, VA03

    Methods for integrating transaction data:

    1. File channel option
    2. Web services channel
    3. User interface option
    4. Mediate connectivity integration

    Integration Using File Channel option

    You import or export the data using scheduled integration events or run the code manually from Ariba Administrator. Executable program code is defined for each file channel integration event and is scheduled to run which extracts the CSV file from Ariba and exports it to the ERP system.

    Data integration process flow chart using file channel integration
    Data integration process flow chart using file channel integration

    As we have mentioned the transaction data is downloaded using integration events in CSV file format. The process is followed up by a data transfer tool. Data transfer tool pushes these downloaded CSV files to the ERP system. In the SAP ERP system, custom RFC programs are designed to read the data from the CSV file. Further RFC/BAPI programs create the data in SAP ERP and send it back to Ariba Procurement Solution.

    Integration Using Web Services Channel

    The web services channel uses SOAP URL configured by Ariba Administrator for integration purposes. For outbound events (like request) SOAP URL is generated automatically to be present in generated WSDL and also it needs to be explicitly configured by Ariba Administrator.

    <IncomingHttpServerURL> / <ContextRoot> / soap / <realm name> / <event name>

    where,

    IncomingHttpServerURL and ContextRoot: fetched from AppInfo.xml file

    soap: static alias for Web Servlet Services

    event name: name of event

     

    Integration Using User Interface Option

    In SAP Ariba Procurement Solution buyers can easily integrate transaction data using Direct Connectivity.

    Data integration process flow chart using User Interface integration
    Data integration process flow chart using User Interface integration

    In the user interface integration process, SAP ERP sends the SOAP request to SAP Ariba containing the entire essential informations wrapped in a request header for the successful extraction of transaction data. The main prerequisite for user interface integration is to download the transport requests in the SAP ERP system.

    Integration Using Mediate Connectivity

    In SAP Ariba Procurement Solution buyers can integrate SAP ERP and SAP Ariba systems using SAP Process Integration layer through Mediate Connectivity. There are two ways through which buyers can connect to SAP Ariba.

    The first way is to use client certificates. SAP PI Keystores stores the certificates and keys that the user creates in SAP PI. The view can be used to group the certificates and keys.

    The second way is to use shared secret authentication. To use this method users must configure the shared secret in the Communication channel of SAP PI.

  • SAP Ariba Master Data Integration

    Preface – This post is part of the SAP Ariba series.

    Before going into the SAP Master Data Integration with Ariba, we will understand what is master data and what can it be used for?

    Master data is the core data for any business organization which is rarely changed over the period of time. It plays a very crucial role in the business process. The master data of the organization covers products, employees, suppliers, and customers.

    List of SAP Master Data

    1. Customer Master Data
    2. Vendor Master Data
    3. Material Master Data
    4. Bill of Material
    5. Routing
    6. Purchase information Records
    7. Conditions Records

    Methods of importing Master Data from ERP to Ariba system

    1. Data transfer tool
    2. Ariba Integration Toolkit through Direct Connectivity
    3. SAP Process Integration
    4. Configure manually from Ariba Administrator console

    List of master data imported to Ariba Procurement Solution

    1. Account assignment category
    2. Accounting field display status
    3. Asset accounts
    4. Company Code
    5. Cost centers
    6. Currency conversion rate
    7. General ledger accounts
    8. Internal orders
    9. Language-specific names for data imports
    10. Material groups
    11. Payment terms
    12. Plants
    13. Purchasing group
    14. Purchasing organization
    15. Remittance location
    16. Supplier locations
    17. Tax code
    18. User and user groups
    19. Vendors

    Pre-requisites for importing master data

    1. Transport request must be downloaded and imported to ERP system
    2. SAP Note 1402826, 1716777 must be implemented
    3. Authorization object must be created
    • To maintain authorization object, go to Tcode SU21 -> create new Authorization Object

    Mapping fields in SAP ERP and SAP Ariba

    For importing and exporting the data, you need to maintain the mapping of fields in ERP and Ariba Procurement Solution. The field names or naming convention of fields maintained in Ariba Procurement and ERP is different. So as to display the names maintained in Ariba, mapping is needed. Otherwise, Ariba Procurement Solution will display the field names from ERP.

    Creating roles for authorization object

    To create roles for authorization object

    1. Go to T-code PFCG and enter the role name.
    2. Click Single Role open authorization tab
    3. Click Change Authorization Data. If you manually select the Authorization to provide the name in Authorization Object box, make sure you enter /ARB and click Continue button
    4. To change the roles provide the parent node details in the Authorization page and proceed further. You can see the /ARB object class which is created previously. Click Program Name and ensure the following values are maintained:

    Object: /ARBA/PROG

    Field Name: PROGRAM

    Provide the transaction data report name under Value Interval. Save it and regenerate the profiles.

  • SAP Ariba – Buyers and Supplier Terms

    Preface – This post is part of the SAP Ariba series.

    Introduction

    As we know that SAP Ariba connects buyers and suppliers on a single platform, Ariba has set some terms applicable for the use of online services by buyers and suppliers of goods and services. In this article we will explore more about SAP Ariba – Buyers and Supplier Terms.

    Terms of Use – Suppliers

    As a supplier in Ariba Network, if you choose any of the online services provided by Ariba, your use of the services will be subject to both the General Terms as well as the Solution Terms of the online services.

    For details related to Terms of Use for suppliers, navigate to below link:

    https://service.ariba.com/Authenticator.aw/ad/termsCenter?tou=supplier

    Term of Use – Buyers

    As a buyer in Ariba Discovery services, your use of the services will be subject to both the General Terms as well as the Solution Terms of the online services but if you disagree with terms of services, Ariba Discovery feature is not allowed to use. In general terms, we can also say that the “solution terms” of services are only applicable to the Buyers accessing the Ariba Discovery site.

    For details related to Terms of Use for buyers, navigate to below link:

    https://service.ariba.com/Authenticator.aw/ad/termsCenter?tou=marketplace

    Apart from SAP Ariba – Buyers and Supplier Terms, Ariba also provides various online services to users which also has some Terms and Policies applicable to it. Below are some Terms and Policies for the services provided by Ariba:

    TERMS AND POLICIES FOR SERVICES

    • Long-Term document Archiving: These terms are only applicable to suppliers who use the Long Term Document Archiving feature in Ariba .
    • Dynamic Discounting Credit Memos: These terms are only applicable to suppliers who request early payments in countries that require credit memos for dynamic discounting.
    • Country Coverage: This provides the list of supported counties issuing invoices, their retention period, physical archiving storage location, and their archive provider.

    TERMS AND POLICIES FOR PAYMENTS

    • Ariba Pay: In addition to the Terms of Use for suppliers, Ariba Payable terms and policies are also applicable for suppliers.
    • Supply Chain Financing: In addition to the Terms of Use for suppliers, Supply Chain Financing services terms and policies are also applicable for suppliers.

    TERMS AND POLICIES FOR OPTIONAL SERVICES

    • Cloud Integration Gateway: These services are only applicable to suppliers that utilize the Cloud Integration Gateway services as activated from Ariba Network. The activation of services serves as the consent of the terms of Cloud Integration Gateway Services.
    • Master Content Services: These services are only applicable to suppliers that utilize the services as activated from Ariba Network. The activation of services serves as the consent of the terms of Master Content Services.

    The detailed description of the Terms and Policies of the above-mentioned services provided by Ariba is provided in the below-mentioned link:

    https://service.ariba.com/Authenticator.aw/ad/termsCenter

  • Configuring SAP Ariba Procurement Solution

    Preface – This post is part of the SAP Ariba series.

    Introduction

    For all export tasks in web-based integration, Ariba Administrator is responsible for configuring the URL for SAP Process Integration. In this article we will explore more about “Configuring SAP Ariba Procurement Solution”.

    Generic URL:

    SoapURL=http:///XISOAPAdapter/MessageServlet?channel=:<BusinessSystemName>:<Communication_Channel_Name>;

    Example:

    SoapURL=”http://<PIserver>:<port> sapnw01 : 50000/XISOAPAdapter/MessageServlet?channel=: BS_Procurement:CC_ChangePurchaseOrder_WSDL_Sender”;

    Where,

    • Server name : sapnw01
    • Port: 50000
    • Business System Name: BS_Procurement
    • Communication Channel Name: CC_ChangePurchaseOrder_WSDL_Sender

    Receiving Tolerances

    In Ariba Procurement Solution, users can update the details of their orders. For this SAP ERP and SAP Ariba systems should receive the information in the same way. For example, both systems must have the same receiving tolerance.

    Configure the following settings in system parameters to set the receiving tolerances:

    • Procure.OverReceivingOperator
    • Procure.OverReceivingPercentage
    • Procure.OverReceivingQuantity
    • Procure.OverReceivingValue
    • Procure.UnderReceivingOperator
    • Procure.UnderReceivingQuantity
    • Procure.UnderReceivingValue
    • Procure.UnderReceivingPercentage

    The above parameter values are set from Service Manager; you need to submit the request with Ariba Contact and the Ariba Customer Support representative will contact you.

    How to enable the generation of ERP Order by Default

    When a user creates requisition for the first time, an ERP order is generated. To generate the ERP order by default, default behavior must be changed.

    Steps to generate ERP Order by Default

    1. Log in to the Service Manager as superuser
    2. Under Site Manager navigate to Customer Sites
    3. Log in as Customer Support Admin
    4. Click Customization Manager
    5. Click the Advanced tab and select Parameters
    6. Under Search Filter search other methods and click edit
    7. Move sap.server.SAPPOERP to the top and click ok and save it

    Specifying the preferred ordering method

    The preferred ordering method is basically the format in which the PO is sent. Users can specify the preferred ordering method for the Purchase Orders sent to suppliers.

    User can choose from the below-supported formats:

    • URL
    • Online
    • Fax
    • cXML
    • Print

    To set the preferred ordering method, you need to submit the request with Ariba Contact and the Ariba Customer Support representative will contact you.

    By default, the ordering method is set to the URL. To download the PO in *.csv format, the user needs to set the ordering method to Print.

    Specifying Unique Purchase Order number

    In Ariba Procurement Solution, the default purchase order number starts with EP10.

    To specify the preferred unique number for the purchase order, you need to submit the request with Ariba Contact and the Ariba Customer Support representative will contact you.

    Enable Cancel Order Integration

    To enable cancel order integration in Ariba Procurement Solution, the value of parameter Application.Procure.UseCancelOrderIntegration should be set to YES.

    To set the value of the mentioned parameter you need to submit the request with Ariba Contact and the Ariba Customer Support representative will contact you.

    Enable creation of Split Orders based on Currency

    In SAP ERP system, the requisition of line items having different currencies is not supported. To overcome this scenario the order should be split based on currencies.

    Steps to enable split orders:

    1. Log in to the Service Manager as superuser
    2. Under Site Manager navigate to Customer Sites
    3. Log in as Customer Support Admin
    4. Click Customization Manager
    5. Click Field Configuration
    6. In Browse Classe, search for procurelineitem
    7. Provide the value for Create Field, Label for field, Expression
    8. Click Advanced tab and choose Split Order on this Field
    9. Click Customizing and publish the order by clicking Publish

    Specifying ad-hoc ship to addresses

    In Ariba Procurement Solution, users can add ad-hoc addresses while creating the requisition or by editing the existing purchase order. Adding an ad-hoc address is enabled once the user enables the Application.Procure.AllowAdhocShipToAddress in their Ariba Procurement Solution account.

    You can learn more about Configuring SAP Ariba Procurement Solution here from SAP’s official website.

  • Difference between Update function module and Regular function module

    Preface – This post is part of the Differences in ABAP for Interviews series.

    Introduction

    Before discussing the difference between Update function module and Regular function module in SAP ABAP, let’s have a short introduction of the two.

    Function modules are procedures that have a set of re-usable statements with importing, exporting parameters, etc. They are created in ABAP workbench using the Function Module Builder. They play an important role in updating and in the interaction between different SAP systems, between SAP systems and remote systems through remote calls.

    There are 3 Processing types of function module:

    1. Regular Function Module
    2. Remote-Enabled Function Module
    3. Update Module

    Regular Function Module

    Regular Function Module and Update Function module consists of a block of statements that are made available globally all over the SAP landscape.

    Update Module

    The Update function module is a function module for which the processing type property of the function builder is set to Update Module. This function module is not executed immediately but is scheduled for execution in a special work process called update work process. For this purpose, the name of the update function module along with the actual parameter is registered in the database table VBLOG as a log record.

    Syntax to register the function module to the log table:

    CALL FUNCTION <function_name> IN UPDATE TASK

    [EXPORTING p1 = a1 … fn = an] [TABLES  f1 = a1 … fn = an

     The actual execution of the program is triggered by the COMMIT WORK statement. The values of the actual parameters are received by the formal parameter of the function module from the VBLOG table. After registration of the function module, if the COMMIT WORK is not triggered then the function module is not executed and the entries are deleted from the log table when the program ends.

    The regular function module does not need to be registered to be called. This is executed immediately whenever a call to this function module is made. Sy-subrc can be checked for success and failure.

    Syntax to call a Regular function module:

    CALL FUNTION  <function_name>

    [EXPORTING  p1 = a1 … fn = an] [IMPORTING  f1 = a1 … fn = an] [CHANGING   f1 = a1 … fn = an] [TABLES     f1 = a1 … fn = an] [EXCEPTIONS e1 = r1 … en = rn

    [ERROR_MESSAGE = rE] [OTHERS = ro]].

    Now, let’s have a look at their difference.

    Difference between Update function module and Regular function module

    Update Function Module Regular Function Module
    It needs to be registered first in the log table There is no need to register
    It is executed when COMMIT WORK statement is triggered. It is executed immediately when a call is made to this function.
    Sy-subrc is undefined after execution Sy-subrc can be checked after the execution

     

  • Difference between User Exits and Customer Exits

    Preface – This post is part of the Differences in ABAP for Interviews series.

    Introduction

    Before discussing the difference between User Exits and Customer Exits in SAP ABAP, let’s have a short introduction of the two.

    The enhancement allows the user to add their functionalities to the SAP standard applications without modifying the original application. Enhancement Framework is used to modify the standard SAP behavior as per the customer requirements. There are different ways to add custom functionalities in standard codes. User Exit and Customer Exit are among them.

    User Exits

    User exits are implemented in the form of subroutines and hence also called FORM EXITs. They are collected in Include and are attached to the SAP standard program. They are empty subroutines where one can fill their source code. They are the type of system enhancements originally developed for R/3 SD(Sales and Distribution). Technically they modify the existing code.

    Syntax:

    FORM USEREXIT_XXXX
    INCLUDE ZZUSEREXIT_XXXX
    ENDFORM.

    Customer Exits

    Customer exits act as hooks where one can hang their new functionalities. These are created for specific programs, screens, and menus within the standard applications. Technically, they are enhancements as they provide add-on functionality. They are used for all modules like MM, SD, FICO, PP etc.

    There are 3 types of Customer Exits:

    1. Function Module Exits

      It is implemented as a call to the function module. It allows the developer to add code in include that is implemented in a function module at a specific location in an SAP application program.

    Syntax:  CALL CUSTOMER-FUNCTION ‘910’

    1. Screen Exits

      It allows the customers to add fields to a screen in the SAP program via sub-screen which is called within standard screen’s flow logic.

    Syntax:  CALL CUSTOMER-SUBSCREEN CUSTOM_SRC

    1. Menu Exits

      These are implemented by SAP and are reserved menu entries in the GUI interface. It allows adding functionalities to menus.

    Syntax:   +CUS (additional item in GUI status)

    Now, let’s have a look at their difference.

    Difference between User Exits and Customer Exits

    User Exits Customer Exits
    It is implemented in the form of subroutine It is implemented for specific programs, screens, and menu within standard applications
    It is technically a modification as existing code are changed It is technically an enhancement as this provides add-on functionality
    It refers to SD module only It refers to all modules like MM, SD, FICO, PP etc.
    All variables, structures, internal tables, etc. are exposed to be viewed and/or changed Only variables, structures, and tables that are passed into the function through the interface are restricted to be viewed and/or changed
    It requires an access key It does not require any access key
    Changes remain after the upgrade Changes are lost after upgrade
    It gets automatically activated whenever the application/program is activated To implement this, a project is created in CMOD then activated

     

  • SAP Ariba Configuration with SAP ERP

    Preface – This post is part of the SAP Ariba series.

    Introduction

    SAP Ariba Network can seamlessly connect to different SAP business suits with the help of add-ons that comes with Ariba Network integration 1.0. In this article we will explore SAP Ariba Configuration with SAP ERP.

    Why integration is needed?

    Integration of SAP Ariba with SAP ERP allows the users to manage the procurement process in SAP Ariba with the integration of the business records already deployed in the SAP ERP system. The integration of Ariba P2P and P2O includes the data load from the ERP system to the Ariba system. It covers data related to suppliers, organizations, and purchases.

    The integration provides the full transparency of transactions of data between the system reflecting the changes and modifications in both systems.

    How does the process works?

    For the purchase of goods, the process starts with the creation of PR’s (Purchase Requisition) for catalog and non-catalog items, this then undergoes for approval of the related approver. Once the PR is completely approved by the designated approver, the PO (Purchase order) is created in SAP Ariba. The process flow of PR creation to PO creation takes place at Ariba platform.

    Once the PO is created in the Ariba platform, the PO data is replicated to ERP system. The process comes to end with the release of the invoice.

    Software pre-requisites for integration

    • SAP ERP system 6.0 or higher
    • SAP Ariba Downstream 13s or higher
    • SAP Ariba Integration Toolkit
    • SAP NetWeaver PI 7.1 or higher (optional )

    Different ways of integration

    There are four ways of performing SAP Ariba Configuration with SAP ERP:

    • File-based integration
    • Web services-based integration
    • Direct connectivity
    • Using middleware connectivity

    File based-integration

    The data is exported from the Ariba Procurement Solution in *.csv format. It is then processed by ABAP program and then replicates it to SAP ERP. After the data replication to the ERP system, the status of the transaction is fetched from ERP and then update back to SAP Ariba. SAP Ariba supports *.csv file format for import and export.

    SAP Ariba Configuration with SAP ERP

    Web-Based Integration

    This integration use middleware’s like SAP PI, SOA to establish integration. SAP PI is by default available and it does not require any manual configuration for setup, whereas using SOA manual configuration is needed. SOAP messages are generated based on WSDL and are forwarded using SAP PI.

    Direct Connectivity Integration

    In the direct connectivity process, master data (in *.csv format) is transferred from SAP ERP to SAP Ariba system in the form of SOAP messages.

    Mediated Connectivity Integration

    In the mediated connectivity integration process, both SAP PI and SOAP messages methods can be used (data can be passed as SOAP messages).

    To use SAP PI to exchange the data, you need to specify the sender and receiver communication channel. For SAP PI/PO integration, Ariba has provided Ariba Network Adapter commonly now as add-ons which allow to send and receive data in cXml format.