Author: Rudramani Pandey

  • Constructor in a Class

    Preface – This post is part of the SAP ABAP OData Tutorial series.

    Introduction

    Focusing on the concept of the constructors in a class, we will discuss what is a constructor and its type with an example. So, a constructor can be understood as a special method in a class that is automatically called when an object is created. It does not require any explicit method call.

    Definition

    A constructor is a special method in a class that is invoked at the time object is created or instantiated.

    Type of Constructors

    Constructors are of two types:

    • Instance constructor
    • Static constructor

    Instance Constructors

    The instance constructor is the predefined instance method of the class called constructor. There are few points to consider while declaring the constructor. They are:

    • The name of the constructor method, irrespective of the class name or type, must be always CONSTRUCTOR.
    • It is declared using a method statement in the visibility section of the class.
    • The method signature can only have importing parameters or exceptions. There are no exporting parameters included.
    • The instance method can be used to set default values in the class.
    • The instance method anyhow can access both instance as well as static variables.
    • It is called each time the object is created.

    Static Constructors

    The static constructor is the predefined static method of the class called as class_constructor. There are few points to consider while declaring the static constructor. They are:

    • The name of the class_constructor method must be CLASS_CONSTRUCTOR.
    • It is declared using CLASS_METHODS statement in the public section of class.
    • The method signature cannot contain importing or exporting parameters or exceptions.
    • The static method can be used to set default values globally.
    • The static method can only access the static variables.
    • It is called exactly once before the class is accessed for the first time.

     

    Example

    Let’s spot one simple example:

    CLASS  demo DEFINITION.
    
           PUBLIC SECTION.
    
                 METHODS:  CONSTRUCTOR.                                                         “Instance Constructor”
    
                 CLASS_METHODS: CLASS_CONSTRUCTOR.                             “Static Constructor”
    
    END CLASS.
    
    CLASS  demo IMPLEMENTATION.
    
           METHOD CONSTRUCTOR.
    
                    WRITE: “Instance Constructor is initiated”.
    
           END METHOD.
    
           METHOD CLASS_CONSTRUCTOR.
    
                    WRITE: “Static Constructor is initiated”.
    
           END METHOD.
    
    END CLASS.
    
    **class object creation**
    
    DATA: demo_obj TYPE REF TO demo.
    
    CREATE  OBJECT  demo_obj.

    OUTPUT

    Static Constructor is initiated

    Instance Constructor is initiated

     

    In the definition part of the class, the CONSTRUCTOR is the instance constructor defined using Methods and static constructer is defined as CLASS_CONSTRUCTOR using class_methods. And their implementations are given the IMPLEMENTATION part. When the object  demo_obj is created, the instance and static constructor is called.

    As we can see that the output displays static constructer implementation before the instance constructor, this is because the CLASS_CONSTRUCTOR method is triggered before the CONSTRUCTOR method.

  • SAP Ariba Reporting Options

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

    Introduction

    SAP Ariba provides reporting options and feature that is included with all modules and also includes upstream, downstream, sourcing, procure-to-order, procure-to-pay and others. In this article we will explore more about SAP Ariba Reporting Options.

    In earlier days we need to perform SQL quires to retrieve the required data, however now through the easy interface for reporting, the need to write SQL queries is abolished.

    This enables the users to run pre-packaged reports commonly known as standard reports as well as custom reports on the Ariba solution. Below are the lists of the reports supported in Ariba System:

    • Pre-packaged reports
    • Custom reports
    • Multi-fact reports
    • Compound reports
    • Exporting reports

    To create a custom report in Ariba Solution:

    • Login to the Ariba system and click on create.
    • Then click Analytical Report

    Permission to create custom reports is given to specific groups

    The users with the basic permissions are able to access pre-packaged reports and public reports as read-only users under manage in Ariba Solution. The public reports are the custom reports which are saved publicly for all to use. Under pre-packaged reports, there are various documents from different modules such as sourcing, contacting, P2P (Procure-to-pay) and many others. Also, Ariba Reporting allows adding the reports to your Ariba Solution accounts dashboard based on your requirement and reporting purposes.

    As the pre-packaged reports are the standard reports by Ariba we cannot modify them however, you can adjust it by specifying filters. You can also specify the report properties though integration events by modifying the CSV file that pulls report data. The integration events that can be used are:

    • ReportQueryPull Integration Event: The ReportQueryPull event is used to define Ariba Queries API queries associated with each report.

    In default configuration ReportQueryPull Integration Event reads from below path:

    BuyerServerRoot/variant/data/ReportQuery.csv

    • ReportMetaPull Integration Event: This event defines the visual appearance and properties of reports. ReportMetaPull Integration Event reads data of following CSV files from BuyerServerRoot/variant/data:
      • csv: Describes the attribute that applies to the entire report.
      • csv File: Describes how to restrict access to reports.
      • csv File: Describes attribute of a particular column.
  • SAP Ariba Supplier Membership Fees

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

    Introduction

    As we know that Ariba Network is globally recognized as the digital platform for connecting the organizations with suppliers for trading purposes, it offers the option of membership fee to help the suppliers to gain the maximum benefit provided by the Ariba Network, this comes under the Supplier Membership Program (SME). In this article we will explore more about SAP Ariba Supplier Membership Fees.

    Supplier Membership Program has two components:

    • The subscription packages
    • The network transaction services

    Subscription Package

    The subscription package includes the plans which charge the fees based on the number documents transacts annually with the customers as well as it is based on the technology usage. The subscription plans provided by SAP Ariba are:

    • Ariba Network Standard: This is designed for the low-level suppliers or we can say for the new suppliers in Ariba Network. It includes the fundamental functionalities that are needed for the procurement process.
    • Ariba Network Select: This subscription enables the suppliers to build the additional collaborative commerce capabilities that will act as an add-on to deal better with the customers.
    • Ariba Network Premier: The premier subscription enables the suppliers to enhance collaborative commerce capabilities through integration and provide technical support to automate the procurement processes.
    • Ariba Network Enterprise: The enterprise subscription enables the suppliers to enhance collaborative commerce capabilities through Ariba Integration Connector, to enable the connectivity to back-end system, program management services and validation services.
    • Ariba Network Enterprise Plus: It includes the enterprise subscription plan as well as it delivers the services that can be needed to make collaborative commerce a competitive advantage.

    SAP Ariba Supplier Membership Fees

    Below table shows the plans, their monthly charges and transaction threshold:

    Plan Monthly Charges Transaction Threshold
    Standard account Free $50,000 to $250,000
    Select $50 $50,000 to $250,000
    Premier $495 $250,000 to $1,000,000
    Enterprise $2495 $1,000,000 to $10,000,000
    Enterprise Plus $7495 $10,000,000 or more

    Note: To get the latest and updated information regarding the SAP Ariba Pricing, you can visit here.

    The subscription fee for standard plan if free of cost until the supplier has reached the limit of five transaction or crosses the chargeable transaction volume threshold.

    SAP Ariba also provides five paid subscriptions levels which depend on the number of annual transactions of documents based on currency. The five levels are:

    • Premium: The premium plan includes unlimited access to portal, catalogs, customer support, reporting and supply chain collaboration.
    • Bronze: It includes all the features of the premium plan as well as the benefit of eCommerce consult team, Ariba achievement badges and free discovery RFI/RFQ responses.
    • Silver: It includes all the features of the bronze plan as well as provides the cXml and EDI integration, technical support and express integration support.
    • Gold: It includes all the features of the silver plan and additionally it provides unlimited responses to sales opportunities, eCommerce consultation services and priority support.
    • Platinum: It includes all the features of gold plan as well as it includes Ariba Live pass and extended Ariba Integration Support.

    Network Transaction Services

    The NTS enables the supplier to collaborate with the customers during the different procurement processes like order process, invoice and other related documents as well as managing the catalog in Ariba Network. The NTS fee is based on the volume of documents transacted annually with the customers.

     

  • SAP Ariba Integration with S/4 Hana

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

    Introduction

    Ariba Network is a digital platform where buyers and suppliers connect for business transactions and to explore new business opportunities. Integration of Ariba Network with S/4 HANA on-premise and cloud follows two different methodologies. In this article we will explore more about SAP Ariba Integration with S/4 Hana.

    Types of Integration

    On-premise Integration

    On-premise S/4 HANA integration follows the same connectivity method which is followed for ECC system connectivity (by using BAPI or Intermediate Document).

    Cloud Integration

    For cloud integration of S/4 HANA with SAP Ariba the communication arrangement is set up in Communication Management of HANA system. Services like oData and SOAP must be configured in communication arrangements of the S/4 HANA system.

    The integration with SAP S/4 HANA cloud allows process:

    • Discount Management
    • Invoice Collaboration
    • Payment
    • Purchase Order Collaboration
    • Service Procurement

    Ways to connect SAP S/4 HANA with SAP Ariba system

    There are three ways to connect SAP S/4 HANA with SAP Ariba system:

    • Direct Connectivity: Ariba provides direct connectivity option under account settings. The Direct Connectivity method does not use any middleware for the integration of the SAP Ariba Network system and HANA.
    • Mediated connectivity using HCL: For the integration using HCL. a system connection is established between Ariba Network and S/4 HANA using SAP HANA Cloud Integration
    • Mediate connectivity using PI: For the integration using PI, middleware is used to establish a connection between SAP Ariba and SAP S/4 HANA.

    Advantages

    By digitalizing and integrating the end-to-end process, promotes the organization to achieve some objectives. The benefits are:

    • Lower total cost of ownership: You can avoid third party integration, maintenance and also the middle-ware cost.
    • Rapid ROI: An organization can achieve a fast return of investment compared to capital invested.
    • Quick and smooth deployment: SAP Ariba native, pre-built integration provides easy deployment with fewer risks.
    • Compliance: The ease to use of software’s increases the service quality provided by users which results in higher compliance.
    • Efficiency: The use of a standard interface across all the applications will eventually result in higher efficiency by adapting the changes quickly and resulting in fewer errors.
    • Effectiveness: The integration produces optimized data providing transparent and complete visibility, stronger collaboration and reliable KPI.
  • SAP Ariba Best Practices for Integration

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

    Introduction

    The best practices optimized for S/4 HANA provides ready to run digitalized logistic and operational business processes that cover the fundamental business process as well as the integration and migration fundamentals to be performed in an organization, delivered through SAP Activate. Now looking into what is SAP Activate? SAP Activate is a combination of SAP best practices, methodologies, guided configuration which simplifies the use of SAP S/4 HANA. In this article we will explore more about SAP Ariba Best Practices for Integration.

    SAP Ariba Best Practices for Integration

    The best practices for SAP S/4 HANA provide quarterly updates regarding the latest innovation in your solution or we can conclude that the main goal is to enable the users to take the advantages of the potentials through S/4 HANA fitting in your business needs.

    The SAP Best Practice for SAP S/4 HANA Cloud can enable the organization to improve the finance, sourcing and procurement, supply chain, sales, services, application platform and infrastructure, SAP S/4 HANA Cloud integration, SAP S/4 HANA Cloud Extensibility and many more business areas.

    Steps to follow to check best practices

    • Open https://rapid.sap.com/bp/ and log in with valid username and password
    • Navigate to SAP S/4 HANA and then click on Integration
    • To get the brief idea of the best practices, follow the link under best practices page

    SAP Ariba Developer Responsibilities

    The role of SAP Ariba Developer requires expertise in the following mentioned areas:

    • Experience of Ariba Integration with SAP ERP system.
    • Technical knowledge of Ariba as well as the knowledge of Ariba products
    • Experience of Ariba On-Demand Implementation.
    • Experience in SAP Ariba Procurement solutions including SAP Ariba Guided Buying, SAP Ariba Buying and Invoicing, SAP Ariba Catalog Management, SAP Ariba Invoice Management.
    • Knowledge of SAP Ariba Payables and Supply Chain Collaborations.
    • Knowledge of SAP Ariba integration with SAP S/4 HANA.
    • Experience of implementing NOTES.
    • Knowledge of implementing best practices for integration.
    • Knowledge of customizing the solution as per the business requirements.
  • SAP Ariba Configurable Workflow

    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

     

     

     

  • SAP Ariba Solution Areas

    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.

  • SAP Ariba Logging and Auditing

    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.
  • SAP Ariba Security Details

    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

  • SAP Ariba Installation

    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
    1. 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)