Describing SAP Ariba 2602 Release Features

Objective

After completing this lesson, you will be able to describe new or changed features for SAP Integration Suite, managed gateway for spend management and SAP Business Network in the SAP Ariba 2602 release.

Enhancements to Supporting Lean Services Procurement Integration between SAP S/4HANA and SAP Business Network Commerce Automation using SAP Integration Suite, managed gateway for spend management and SAP Business Network AddOn

Business Details

This feature enhances lean services procurement integration between SAP S/4HANA and SAP Business Network Commerce Automation using the SAP Integration Suite, managed gateway for spend management and SAP Business Network AddOn component, S4CI1. This feature allows buyers and suppliers to exchange all the lean service documents such as service orders, service sheets, and invoices.

As part of this feature, the following additional functionalities are supported:

  • Unplanned (enhanced limit service type) lean services.
  • Comments at the line item level and header level for lean service entry sheets.
  • Split by amount for enhanced limit service type is supported for S4CORE versions 109 and later.

The following functionalities are supported for both planned and unplanned lean services:

  • Updating an SES, auto-SES, final SES, unplanned services with item hierarchy, and enhanced limit with contract reference ID.
  • Suppliers can cancel the SES under the following conditions:
    • The SES is neither approved nor rejected.
    • The SES is approved but not invoiced.

Previously, you could only configure this feature using OPD (Output Parameter Determination). Now, you can also use NACE to configure this feature.

Note

This enhancement addresses some of the use cases that were flagged as limitations in the 2511 feature Supporting Lean Services Procurement Integration between SAP S/4HANA and SAP Business Network Commerce Automation using SAP Integration Suite, managed gateway for spend management and SAP Business Network AddOn (BPI-509).

Implementation Details

General Prerequisites

  • You must have the latest add-on component, S4CI1, installed:
    • SAP S/4HANA
      • ARBCI1 10S: SP24
      • S4CI1 100: SP01

    Existing buyers using SAP Integration Suite, managed gateway for spend management and SAP Business Network can install the add-on based on the following criteria:

    • SAP S/4HANA
      • If you are using ARBCI1 10S:
        • Upgrade to the latest version ARBCI1 10S: SP24
        • Install SAP S4CINT 100: SP01

    If you are a new customer, ensure that you configure the Managed Gateway for Spend&Network portal. For more information, please see SAP Integration Suite, Managed Gateway for Spend Management and SAP Business Network Installation Guide.

  • You need to use the SAP S/4HANA 2025 SP00 or higher versions.
  • To trigger the PO output type when you make changes to a Purchase Order in SAP S/4HANA, the OSS SAP Note 3430273 must be implemented. This note is valid for S4CORE versions 108 through 109.
  • Manage activation of application object type as follows:
    1. Log on to the SAP GUI in the SAP S/4HANA Cloud Private Edition system.
    2. Run the transaction SPRO and choose SAP Reference IMG.
    3. Choose Cross-Application ComponentsOutput ControlManage Application Object Type Activation.
    4. For the Purchase_Order application object type, in the Status field, set the value accordingly:
      • To use OPD: Set it to Application Active.
      • To use NACE: Set it to Application Inactive.
    5. Save the changes.
  • Define mapping of external system and logical port for outbound services for SES as follows:
    1. Log on to the SAP GUI in the SAP S/4HANA Cloud Private Edition system.
    2. Run the transaction SPRO and choose SAP Reference IMG.
    3. Choose Integration with Other SAP ComponentsIntegration for PurchasingBasic SettingsDefine Communication Systems for Outbound Messages.
    4. Choose New Entries and enter the following data:
      External System IDProxy Class of Logical PortLogical Port
      <ANID of buyer system e.g.: AN02005439245-T>CO_MMPUR_SES_STATUS_NOTIF_OUT<SERVICEENTRYSHEET_LP>
    5. Choose NextFinish.
  • Download the WSDL definition files for service users as follows:
    1. Log on to the SAP GUI in the SAP S/4HANA system.
    2. Run the transaction SE80.
    3. Choose the Package object type. In the Package Name field, enter IG_S4CI_SRV_SOA.
    4. Expand Enterprise ServicesService Consumers, and choose the CLASCO_S4CINT_PURCHASE_ORDER_OUT service consumer.
    5. In the right section, choose the WSDL tab.
    6. Choose Save to file and enter a name for the WSDL definition.
  • Implement the customer exit to support lean services in order confirmation as follows:
    1. Run the transaction code SPRO.
    2. Click SAP Reference IMG.
    3. Navigate to Integration with Other SAP ComponentsIntegration with Procurement ApplicationsApplication Specific SettingsOrder Confirmation.
    4. Click on the IMG-Activity for Implement Customer Exit to Support Lean Services in Order Confirmation.
    5. Enter a name in the Project field. For example, ZOR. If you already have an existing SAP project for enhancement, use the same project.
    6. Click Create and enter a description in the Short Text field.
    7. Click Save.
    8. Click Enhancement assignments. The Create Object Directory Entry screen appears.
    9. Choose the package.
    10. Save the changes. The SAP Enhancements in Enhancement Project <object name> page appears.
    11. Enter MM06E001 in the Enhancement field and then press Enter.
    12. Click Components.
    13. Double-click EXIT_SAPLEINM_009. The program INCLUDE - ZXM06U21 appears.
    14. Double-click INCLUDE - ZXM06U21 in the Function Builder: Display EXIT_SAPLEINM_009 page to create the program.
    15. Enter the following include: INCLUDE ARBCIG_INCL_LEAN_OC_04 IF FOUND.
    16. Save the entries.
    17. Click the Activate button to go back to the CMOD screen.
    18. Activate the customer exit in the CMOD screen.

Limitations

  • Attachments are not supported.
  • SAP S/4HANA does not support splitting by quantity or percentage for services with enhanced limits.

Configuration

You can also choose to implement the BAdIs for using lean services.

To configure using OPD, perform the following steps:

  1. Configure the SOAP service.
  2. Configure the interface setup.
  3. Configure the output parameter determination.
  4. Edit the WSDL definition files.
  5. Configure the partner profile.

To configure using NACE, perform the following steps:

  1. Configure the interface setup.
  2. Define message output control for all document types.
  3. Implement routine to suppress IDocs for lean or enhanced limit purchase order.

Technical Details

ProductSAP Integration Suite, Managed Gateway for Spend Management and SAP Business Network
EnablementCustomer-managed
Reference Number

NGPROCINT-382

NGPROCINT-449

User TypeBuyer

Integration Support to Import Purchase Contracts from SAP ERP to SAP Ariba Buying Solutions via Web Services

Business Details

With this feature, you can import purchase contracts from SAP ERP into SAP Ariba buying solutions using web services via SAP Integration Suite, managed gateway for spend management and SAP Business Network. The imported purchase contracts are automatically converted into compliance contracts. If you are using SAP S/4HANA 2022 or later releases, you can also import contracts that include lean services with item hierarchies.

Note

Only purchase contracts with Split Accounting Type set to Percentage can be imported.

Implementation Details

General Prerequisites

Ensure that the SAP Ariba buying solution is integrated with SAP S/4HANA through SAP Integration Suite, managed gateway for spend management and SAP Business Network AddOn.

Limitations

  • If you're using SAP S/4HANA 2022 or later releases and trying to import purchase contracts with the new add-on component, S4CI1, note that the DRF functionality does not support MMSRV contracts.
  • Attachments are not supported.

Configuration

You can import purchase contracts using one of the following ways:

  • Using the ARBCIG_CONTRACT_EXPORT program. To do so, perform the following steps:
    1. Configure the SOAP service to link SAP Integration Suite, managed gateway for spend management and SAP Business Network and the SAP Ariba buying solution.
    2. Execute the ARBCIG_CONTRACT_REPORT program.
  • If you are using SAP S/4HANA 2022 or later releases, and using the lean service procurement capability, you can import purchase contracts using the new add-on component, S4CI1.

    To use the new add-on component, perform the following steps:

    • Prerequisite: You must have the latest add-on component, S4CI1, installed:
      • SAP ERP
        • ARBCI1 100: SP 0024 or later
      • SAP S/4HANA
        • ARBCI1 10S: SP 0024 or later
        • S4CI1 100 : SP01 or later

      Existing buyers using SAP Integration Suite, managed gateway for spend management and SAP Business Network can install the add-on based on the following criteria:

      • SAP ERP
        • If you are using ARBCI1 100:
          • Upgrade to the latest version ARBCI1 100: SP 0024 or later
      • SAP S/4HANA
        • If you are using ARBCI1 10S:
          • Upgrade to the latest version ARBCI1 10S: SP 0024 or later
          • Install SAP S4CI1 100 : SP01 or later
    1. Configure the endpoints to link SAP Integration Suite, managed gateway for spend management and SAP Business Network and the SAP Ariba buying solution.
    2. Configure the DRF.

You can choose to implement the S4CINT_CONTRACTDET BAdI to customise the logic to import purchase contracts.

Technical Details

ProductSAP Integration Suite, Managed Gateway for Spend Management and SAP Business Network
EnablementCustomer-managed
Reference NumberBPI-591
User TypeBuyer

Migration of SAP Integration Suite, Managed Gateway for Spend Management and SAP Business Network to SAP BTP, Cloud Foundry Environment

Business Details

SAP Business Technology Platform (BTP) has announced the end-of-life for SAP BTP, Neo environment. Starting Q1, 2026, we're migrating SAP Integration Suite, managed gateway for spend management and SAP Business Network from SAP BTP, Neo environment to SAP BTP, Cloud Foundry environment. Depending on the data center, the migration for various managed gateway instances is carried out in phases.

Note

Ensure that you regularly check https://support.ariba.com/item/view/214285 for information on migration dates and tasks to be performed.

What do Customers have to do?

  • As a buyer, you must configure new SAP Cloud Connector sub accounts and if you leverage IP allow listing, ensure that you allow the new URLs prior to your migration date.
  • As a supplier, if you leverage IP allow listing, ensure that you allow the new URLs prior to your migration date.

What is not changing during this migration?

  • Integration URLs
  • Certificates or authentication mechanism
  • Functionality/UIs
  • All customer data, including transactional and configuration data

Steps to follow

  • Determine your SAP Integration Suite Managed Gateway Data Center
  • Confirm if you use SAP Cloud Connector
  • Add new SAP BTP Cloud Foundry Subaccounts
    • Use correct Region (eu10, us10, or ae01)
    • Use the provided Subaccount ID and One-time Passcode (OTP)
    • Maintain the same Location ID
    • Maintain Cloud-to-On-Premise settings
    • Configure for both TEST and PROD
  • Confirm if you leverage IP Allow Listing and update accordingly

Note

For answers to common questions about the migration from the Neo environment to the Cloud Foundry environment, see Frequently Asked Questions.

Technical Details

ProductSAP Integration Suite, Managed Gateway for Spend Management and SAP Business Network
EnablementAutomatically On
Reference NumberSISGW-1059
User Type

Buyer

Supplier

Related Resources

For information about all the new or changed features in recent SAP Ariba releases, see What's New in SAP Procurement and SAP Business Network.