Category: SAP

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

Introduction

SAP Ariba provides easy to use workflow design for your company which does not need any configuration from the external source. Although you can modify the rules with the help of specified settings and also it becomes easy to build, test and deploy the workflow with workflow builder. In this article we will explore more about SAP Ariba Configurable Workflow.

Invoicing and payment workflow

The general purpose of SAP Ariba Invoicing Solution, SAP Ariba Buying and Invoicing and SAP Ariba Invoice Management is the same.

Depending upon the invoice process flow configuration, the invoice is created. After the invoice is submitted, SAP Ariba invoicing creates an approvable invoicing document. When the invoice is completely approved, the two documents are created:

• Invoice Reconciliation document (IR): It is used to resolve discrepancies in purchase order such as the mismatch of quantity in orders.
• Payment Request Document: It is used to generate payment once the invoice is reconciled.

In case the advance payment is made for the purchase order, a payment manager is added to the approval flow of the invoice reconciliation document. The role of the payment manager is to adjust the payments against the invoice. To find any discrepancy in the IR, the reconciliation processor matches the IR to existing PO, contracts, receipts and validates it according to the site’s configuration. One of the two cases that can happen in this process: either the inconsistency is found in IR or there is no inconsistency.

If inconsistencies are present in IR, they must be manually reconciled and are displayed as an exception on the IR document. Once the exceptions are resolved by the handlers they are sent to the responsible person for the approval to pay the supplier.

On the other hand if there are no discrepancies in the IR, it is sent directly to the responsible person for the approval to pay the supplier.

Once the final approval is received for the IR, the invoice status changes to Reconciled and the payment to the supplier is scheduled.

 

Ariba also supports other configurable workflows such as SAP Ariba Contract Invoicing, Ariba Services Invoicing and many others.

Refer to the below link for the existing SAP Ariba Configurable Workflow:

https://www.ariba.com/solutions/solutions-overview/financial-supply-chain/invoice-management

 

 

 

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

Introduction

SAP Ariba digitally transforms the business to collaborate with the suppliers to enhance the business areas and strengthened their relationship on the Ariba platform by providing various solutions. In this article we will explore all the SAP Ariba Solution Areas.

SAP Ariba solution areas are supplier management, strategic sourcing, direct spend, procurement, and financial supply chain.

Supplier management

Managing the end-to-end relationships with suppliers, including the supplier information, lifecycle, spends and risk, SAP Ariba Supplier Management makes the procurement process smooth all in a single platform.

Supplier management includes:

• Supplier Risk Management: By this feature you can reduce the degree of risk by helping the buyers to make apt decisions before purchase. This can be achieved by making risk assessment and due diligence an integral part of the procurement process.
• Supplier Lifecycle Management: SAP Ariba Supplier Lifecycle Management manages the suppliers from initial to out phase. This enables the suppliers to update and maintain their information to provide an accurate record to buyers.

Strategic Sourcing

With the help of Strategic Sourcing Procurement Solution, managing the sourcing, contracting, and spend analysis process for all three materials (direct, indirect and punchout materials) as well as services is quite manageable.

Direct spend

Direct spend solution can integrate easily with SAP ERP, PLM and SAP Integrated Business Planning System. It helps to connect to people, partners and information for the business. Digitalizing the entire supply chain process and digital procurement solutions that support direct spend.

Procurement

Achieving the high rate of market value by managing the risk and controlling the costs, the procurement solution of SAP Ariba provides visibility to the broadcast set of capabilities on the market.

• Procure-to-pay: It provides a fast buying experience while controlling the spending and navigating the savings to bottom line.
• Guided buying: It brings the buyers and suppliers together for business transaction of goods.
• Spot buy: For the procurement of non-sourced good use SAP Ariba Spot Buy.

Financial supply chain

The key to a strong successful financial supply chain solution is to make payables strategic. Digitalizing the payables and invoices reduce the extra cost of manual activity for the financial process.

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

Introduction

In SAP Ariba the log files for Ariba Buyers are located in BuyerServerRoot/logs and some log files include logical node name. For example – metrics-Nodel.csv. To view and download the log files, administrators can access the Log Files task in Ariba Administrator. In this article we will explore the aspects of SAP Ariba Logging and Auditing.

SAP Ariba Logging and Auditing: Log files in Log Directories

Below is the list of log files in log directories:

File Name	Description
BuyerNode1Log.txt	Main log file for Ariba Buyer
LogDBLog.txt	Contains messages generated during the data loading process
AribaBuyerbuyerserver1InspectorAuditLog.txt	Logs messages generated by Inspector activity
AibaMetaConfigurationLog.txt	Logs messages associated with metadata XML files
AribaOrderTransmitterLog.txt	Logs order transmission messages
classMetrics-nodename.txt metrics-nodename.csv	Contains Ariba Buyer performance data
configuration.txt	Contains messages generated during configurations
configureasmsharedlog.txt	Contains messages generated by Ariba Spend Management integration program
dbinit.txt	Contains messages generated during the database initialization process
emptychannel.channel.txt	Created when initdb is run with emptychannel option
EmptyDBLog.txt	Logs messages associated with the emptydb phase of initdb
initchannel.channel.txt	Logs messages generated during channel initialization process
installlog.txt	Logs messages generated during the installation
j2eeSetupLog.txt	Records the running of j2eeSetup script. The script is invoked by configure command
loadchannel.channel.txt	Created when initdb is run with loadchannel option
LoadMetaLog.txt	Logs messages associated with LoadMeta phase of initdb
AuthServiceInstallLog.txt WebLogServiceInstallLog.txt	Contains messages associated with the installing and starting window services

 

SAP Ariba Logging and Auditing: Categories and Logging Levels

In Ariba Procurement Solution, each log message in the main log file (BuyerNode1Log.txt) has an associated category and levels.

Categories: the group of related log messages belongs to the same category. For example, the log messages related to approvable transactions are the part of approvable log message category.

Logging Levels: Logging levels are classified at the category class. Basically it indicates the importance of a log message.

SAP Ariba Logging and Auditing: Logging Levels for Default Configuration

Below are the logging levels for default configuration:

• Error – This is the indication of a fatal error in the system.
• Warning – This serves as the cautionary advice to avoid potential problems.
• Info – This provides the essential information that might be necessary for diagnosing problems in case of errors.
• Debug – these are intended for use during the implementation phase and debugging phase.

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

Introduction

In the time of increasing data security issues, SAP Ariba ensures the privacy and protection of sensitive information’s provided by its customers. Ariba provides the data encryption of personally identifiable information (PII) and other sensitive information like computer name, passwords present in Ariba Configuration files. The data is encrypted before it is store in the database.

SAP Ariba Security Details

SAP Ariba provides data security for the following solutions:

• SAP Ariba Contracts
• SAP Ariba Sourcing
• SAP Ariba Supplier Information Management
• SAP Ariba Supplier Information and Performance Management

In default configuration data encryption is disabled. User needs to enable the encryption option by creating the Service Request using Designated Support Contact (DSC) and Ariba Customer Support will contact for the further process.

For data encryption in Ariba Buyer Configuration file, user needs to pass aribaencrypt command and use string as an argument. The aribaencrypt command will encrypt the data and store it in Parameter.table (Parameter.table is a table file having extension .table which is used for assigning the parameter to specified values. It is the main configuration file for Ariba Buyer.) without altering the meaning of data and its functionality.

Ariba Administrator Tasks

For a complete security, there is also a need to secure the data which is accessible through the Ariba Administrator profile.

Methods to control access to data through Ariba Administrator:

• First level security can be achieved by using the EditPermissionPull integration event. Users can provide access to files like configuration files, log files by specifying in EditPermission.csv file and importing the CSV file through the EditPermissionPull integration event.

Directory for EditPermission.csv (default configuration)::

config/variants/Plain/partitions/None/data

• Integration events and scheduled tasks. By using the ExecutePermissionPull integration event this can be secured. Users can assign permission to specific events and tasks in ExecutePermission.csv file and importing the CSV file through the ExecutePermissionPull integration event.

Directory for ExecutePermission.csv (default configuration)::

config/variants/Plain/partitions/None/data

• Workspace and task permissions need to change from the workspace configuration file.
• To restrict access to particular objects in Ariba Configuration file, assign read and edit permission to objects in ObjectPermission.csv and then load the CSV file with the ObjectPermissionPull integration event.

Directory for ObjectPermission.csv (default configuration):

config/variants/Plain/partitions/None/data/ObjectPermission.csv

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

Introduction

In SAP Ariba there are some activities involved while installation. Below are the activities listed:

• SAP Ariba Notes Installation
• SAP Ariba Adapter Installation
• SAP Ariba BASIS customization
• SAP Ariba functional configuration setting
• SAP Ariba technical web services configuration
• SAP Ariba adapter customization (depending upon business needs)

 

SAP Ariba Notes Installation

Following are the list of SAP NOTES that are required to be deployed on SAP ERP system:

• 1884125: Technical adjustments for Ariba integration
• 1832628: BAPI for service PO Entry Sheet and Contract: esll-extrow
• 2053181: Exit to create output message during deletion of Service Entry Sheets (Ariba Integration)
• 1878009: Ariba integration in the logistics invoice verification
• 1968355: Ariba integration part II: Parking invoices from Ariba
• 2053181: Exit to create output message during deletion of Service Entry Sheets (Ariba Integration)
• 1535132: Independent saving of application log
• 1834548: Retrofit of ME_PO_CONFIRM – technical documentation
• 1908480: ME 808 when deleting and adding confirmations
• 1885572: ME_PO_CONFIRM proposes wrong confirmation type
• 1669829: Unable to generate LP with X.509 client cert. w/o WSDL
• 1954584: FI_DOCUMENT_CHANGE: Unable to change WSKTO for vendors
• 1964766: Exit for creating payment advice notes for SAP applications
• 1967254: Exit to create payment advice notes (Ariba Integration)
• 1984803: Adjustment of check-logic in function module SAPPO/API_CHECK_METHOD_MODULE
• 1987211: Error when jumping to the application log
• 1918732: Ariba Network Integration for SAP ERP: Mapping Documentation

SAP Ariba Adapter Installation

Steps to install SAP Ariba Adapter:

1. Log in to support.ariba.com using valid credentials (user ID and password)
2. User needs to have a DSC (Designated Support Contact) ID. New users can register from https://support.ariba.com
3. Search for SAP Network Adapter for SAP NetWeaver
4. Import required AN adapter files which are available in *.tpz format into SAP Enterprise Service Repository.

Following is the list of AN adapter files:

• tpz
• tpz
• Adapter.tpz
• Basis.tpz
• tpz
• xml
• tpz

5. Import Ariba Network product and component definitions into System Landscape Directory. These are available in *.zip format.

Consider the below list of files:

• SoftwareCatalog.zip
• SoftwareCatalog.zip
• SoftwareCatalog.zip
• SoftwareCatalog.zip

To fix any issue related to importing below transactions can be used:

• SLG1 – Display Logs transaction code
• SXI_MONITOR – Message Monitor transaction code
• SBGRFCMON – bgRFC Monitor transaction code

There are some cXml message types which are used to enable the above mentioned processes. Below is the list of message types used:

• ConfirmationRequest (inbound)
• OrderRequest (outbound)
• InvoiceDetailRequest (outbound)
• PaymentProposalRequest (inbound)
• PaymentProposalRequest (outbound)
• InvoiceDetailRequest (inbound)
• PaymentRemittanceRequest (outbound)
• PaymentRemittanceStatusUpdateRequest (outbound)
• ShipNoticeRequest (inbpund)
• ServiceEntryRequest (inbound)
• ReceiptRequest (outbound)
• StatusUpdateRequest (outbound)

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.

5. 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.
6. Extract the downloaded file and customized the mappings are per the business needs.

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.

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.

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.

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.

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.