Understanding Stock Availability & Reservation

Objective

After completing this lesson, you will be able to describe how to configure Stock Reservation Integration in SAP Ariba Procurement, CIG and SAP System.

Stock Availability – Overview

Inventory Management in Storage Location is an important process for any plant operations. To make any transaction at inventory level, stock update information is essential to decision making.

In SAP every goods movement at Storage Location level will result in increase or decrease of unrestricted stocks.

  • Visibility in stock information before making decision for procurement is not currently available for SAP Ariba Procurement users.
  • With this new feature, users can check the latest available stocks for unrestricted use.
  • Unrestricted stock is the stock which is readily available for use. Buyers using CIG can check the unrestricted stock of a material on the catalog before placing an order on Ariba Procurement.
  • When a buyer checks for the stock, the unrestricted stock information is fetched from the IMS & displayed. A scheduled job on the IMS periodically checks the SAP system for the unrestricted stock of a material at a storage location.
  • SAP system updates the IMS with the requested stock details. The stock details are sent to IMS in batches defined by the batch size configured on SAP system.
  • New fields are introduced in Catalog Syndication feature to help get the required information for Stock Availability feature: Material Number; Material Group; Plant; Storage Location & In Stock (identifier).
  • Only that inventory item / material will get pushed from SAP Ariba Procurement to IMS which has "In Stock" flag set to True. You need to implement BAdI to set this flag for the inventory items which you would like to push to IMS. BAdI Name: ARBCIG_BUY_CATALOG_EXPORT.

The Stock availability feature provides users the up-to-date information of unrestricted stock levels from SAP system.

Flowchart illustrates SAP Ariba Procurement retrieving inventory stock information from SAP IMS and displaying it to the user.

Prerequisites:

  • Make sure that you have Catalog Syndication feature enabled & implemented before hand to facilitate export of material master data from SAP system to Ariba Procurement.
  • Maintain Storage Location Filter in SAP system for the ARBCIG_BUYER_CATALOG_EXPORT program to allow export of specific storage locations.
  • Maintain the ENABLE_MRO_INVENTORY parameter to include MRO inventory details in the catalog uploads from SAP system to Ariba Procurement.
  • Maintain the INVENTORY_BATCH_SIZE parameter to define the number of records to export in each batch of the inventory. SAP Ariba recommends to maintain 50000 as a batch size.
Task / ActivityEnvironmentDescription
Enable & implement Catalog Syndication featureSAP Ariba Procurement & SAP systemThis feature is prerequisite for Stock Availability feature.
Enable feature & parametersSAP Ariba ProcurementEnable required features & parameters in Ariba Procurement by raising a Service Request (SR).
Enable Integration TasksSAP Ariba ProcurementOn CIG enablement page, select the required integration tasks relevant to the features.
Maintain Parameters & FiltersSAP systemMaintain the provided parameters & filters.
Execute Interface SetupSAP systemExecute Interface Setup program by selecting required web service messages.
Implement BAdISAP systemOptional: To address any additional customization.
Catalog ExportSAP systemExecute Catalog Export Master Data program in SAP to send information of unrestricted inventory material to Ariba Procurement.

Process Flow:

Flowchart explains how SAP Ariba and IMS sync inventory stock data using GSR and DSR for procurement processes.

Failure

In case of failure of any or all batches, IMS will send a request to SAP system to send that specific batch.

  • The last batch in each Transaction ID will have a flag indicating that it’s a last batch.
  • Thus, IMS understands that the response from SAP system is now complete for a specific Transaction ID.

Activity 2.1 SAP Ariba Cloud Integration Specific Configuration in SAP Ariba Procurement

To enable features and parameters, Service Requests (SRs) must be submitted through SAP Ariba Customer Support, as follows:

Field NameParameterDescription
FeatureInventoryReservation 
ParameterApplication.Purchasing.EnableInventoryReservation 
ParameterApplication.Catalog.IS.TenantConfig
  • This is used for setting the frequency for Delta Stock Request. This is to be defined by customer via SR.
  • JASON expression for above parameter where "freq’ to be set by customer for Delta Stock Request via SR – [ { "freq": 10, "tenantId": 122, "catalogQualifier": [ "an70000000004: InventoryItems2","an70000000004: InventoryItems"] } ]
ParameterApplication.Common.EnablePlantBasedDefaultingFor
  • Required Master Data for this parameter: Import Plants Data; Import Plants to Purchase Organization Mapping & Import Storage Location.
  • Values available in Ariba Procurement for these master data objects must match with what is there in Catalog Master Data.
Type DefinitionsMaterial Number; Material Group; Plant; Storage Location & In Stock flag (identifier)
  • This request will add the required custom catalog fields (supplementary attributes) to enable inventory related information to be consumed & displayed in the catalog user interface.

Next, enable CIG in SAP Ariba Procurement, by selecting the following integration tasks:

  • Export Reservation Request Asynchronously
  • Export Reservation Deletion Request Asynchronously

Activity 2.2 SAP Ariba Cloud Integration Specific Configuration in CIG

Buyer users need to perform following activities:

  1. Add / update SAP System information or ensure that the information sent from your SAP System is available in CIG.
  2. Create the Project for Ariba Procurement product.
  3. Add a Connection.
  4. Define Cross References Parameters (not required for Stock Availability Integration).
  5. Define Lookup Values based on your requirements (not required for Stock Availability Integration).
  6. Ensure that your realm ID is correctly selected.
  7. Confirm & Test the project to get ready for deployment to Production.

Note

To know more about these activities, please refer to the CIG Project Configuration unit of the AR822 SAP Ariba Cloud Integration Gateway Administration course on SAP Learning Hub.

Activity 2.3 SAP Ariba Cloud Integration Specific Configuration in SAP System

There are 4 sub-activities in this section:

  • 2.3.1 Global Settings
  • 2.3.2 General Settings
  • 2.3.3 Transaction Specific Settings
  • 2.3.4 BAdI Implementation (optional)

Activity 2.3.1 SAP Ariba Cloud Integration Specific Configuration in SAP System – Global Settings

Ensure that following configurations of Global Settings section are in place –

  • Maintain Certificates
  • Send SAP Information to CIG
  • Maintain Parameters for Attachments Support
  • Maintain BAdIs as per your requirements

Note

To know more about these activities, please refer to the AddOn SPRO - Global Settings unit of the AR822 SAP Ariba Cloud Integration Gateway Administration course on SAP Learning Hub.

A quick recap on these configuration objects relevant to Stock Availability:

  1. Maintain Certificates – For SSL handshake it is mandatory. Upload Loadbalancer certificate of CIG in STRUST.
  2. SAP Data Sync

Activity 2.3.2 SAP Ariba Cloud Integration Specific Configuration in SAP System – General Settings

To set-up General Settings from within SAP Ariba Procurement:

The SAP IMG menu highlighting the SAP Ariba Procurement Integration section and its General Settings sub-option for configuration.
  • Run the transaction code SPRO – the Customizing: Execute Project screen appears.
  • Click SAP Reference IMG – the Display IMG screen appears.

Next, navigate to:

  • Integration with Other SAP Components
  • SAP Ariba Cloud Integration Gateway
  • Ariba Procurement Integration
  • General Settings

In order to enable the flow of messages between Inventory Management System (IMS) & SAP System, the user needs to set-up the following under General Settings:

The Interface Setup Program for SAP Ariba Procurement displays configuration options for stock requests and integration settings.
  • Setup the Interface
  • BAdIs for Setting Up the Interface (optional)
  • Stock Availability Request (Inbound)

Select following Inbound & Outbound webservice messages while executing Interface Setup program:

  • Stock Availability Request (Inbound)
  • Stock Reservation Request (Inbound) - Only needed for reserving inventory items
  • Ingest Stock Request (Outbound)

Activity 2.3.3 SAP Ariba Cloud Integration Specific Configuration in SAP System – Transaction Specific Settings

There are 5 sub-activities in this section:

  • 2.3.3a Configure the Batch Size
  • 2.3.3b Maintain Filters for Storage Location Export
  • 2.3.3c Maintain Sequential Number of Storage Location Address
  • 2.3.3d Maintain Parameter for MRO Inventory Details
  • 2.3.3e Set Filter for Storage Location in Catalog Export

Activity 2.3.3a SAP Ariba Cloud Integration specific configuration in SAP system – Transaction Specific Setting - Configure the Batch Size

You can maintain the parameter to define the number of records to export in each batch when a query is made to update the stock details from SAP system to Ariba Inventory Management System (IMS).

  • SAP system exports the records that are available in ARBCIG_IMS table for requested stock items.
  • This is in one-time activity.
  • SAP Ariba recommends to maintain 50000 as the batch size.
FieldDescription
Parameter NameINVENTORY_BATCH_SIZE
Field NameLeave blank. No action required.
NumberLeave blank. No action required.
VariantThe unique variant name of the Ariba Procurement realm. For example, VREALM_2.
PartitionThe unique partition name of the Ariba Procurement realm. For example, PREALM_2.
LowSpecify the number of records in each batch. For example, 50000.

To configure the Batch Size:

  1. Run the transaction code SPRO

    Navigate to:

    SAP IMG menu highlights SAP Ariba Procurement Integration, focusing on Stock Availability Request and Maintain Parameters for Stock Availability.
    • Integration with Other SAP Components
    • SAP Ariba Cloud Integration Gateway
    • Ariba Procurement Integration
    • Application Specific Settings
    • Stock Availability Request
    • Maintain Parameters for Stock Availability
  2. The Parameters – Stock Check Request page appears.Interface displaying Parameters - Stock Check Request option with Modify highlighted to adjust the INVENTORY_BATCH_SIZE variable configuration.
  3. Click Modify button.
  4. Enter the required details.Parameters - Stock Check Request screen displays configuration for INVENTORY_BATCH_SIZE with values for variant, partition, and limit as 50,000.
  5. Click Save.

Activity 2.3.3b SAP Ariba Cloud Integration Specific Configuration in SAP System – Transaction Specific Setting - Maintain Filters for Storage Location Export

You need to maintain filter for exporting Storage Locations in the ARBCIG_BUYER_CATALOG_EXPORT program to allow export of specific storage locations.

  • Configure a selection criteria to filter the details that need to be included in Catalog Master Data export for the storage locations.
  • This information is required. It is used to send Query Stock Request and Delta Stock Request to fetch the stock information/updates based on defined Storage Locations.
FieldDescription
Variable NameSTORAGE_LOCATION_EXPORT.
Field NameField name that indicates the storage location information in the T001L table. (LGORT).
TypeEnter S as the selection category.
Number0000
VariantThe unique variant name of the Ariba Procurement realm. For example, VREALM_2.
PartitionThe unique partition name of the Ariba Procurement realm. For example, PREALM_2.
SignIndicates whether to include or exclude the value specified in the filter. For example, I.
Option

Specify the condition for the filter. For example, EQ.

LowEnter the filter value for the criterion you set for field. For example, US01.
HighEnter the filter value for the criterion you set for field. For example, US50.

Blank if the option is not BT.

Enter the range of values between Low and High if the option is BT.

To Maintain Filters for Storage Location Export:

  1. Run the transaction code SPRO

    Navigate to:

    SAP IMG menu displays Master Data Integration with focus on Maintain Filters for Cross Application, Procurement, and Sourcing settings.
    • Integration with Other SAP Components
    • SAP Ariba Cloud Integration Gateway
    • Master Data Integration
    • General Settings
    • Maintain Filters
    • Procurement
  2. The Prefilters – Ariba Procurement Master Data page appears.Prefilters - Ariba Procurement Master Data screen enables modifying variables like ACCOUNT_CATEGORY_EXPORT, ACCOUNT_FIELD_EXPORT, and more using the Modify option.
  3. Click Modify button.
  4. Enter the required details.Prefilters - Ariba Procurement Master Data configuration screen highlights variables like STORAGE_LOCATION_EXPORT with values for type, partition, and range.
  5. Click Save.

Activity 2.3.3c SAP Ariba Cloud Integration Specific Configuration in SAP System – Transaction Specific Setting - Maintain Sequential Number of Storage Location Address

A Storage Location can have multiple addresses which have sequential numbers starting from 1.

  • If you specify a sequential number of the storage location address, only the information pertaining to the specified address is exported to SAP Ariba Procurement. If you do not specify a sequential number, the export program exports the information for storage location address with sequential number 1.
  • You need to maintain this parameter for exporting Storage Locations in the ARBCIG_BUYER_CATALOG_EXPORT program.
FieldDescription
Variable NameSEQUENTIAL_ADDRESS_NUMBER
Field NameLeave blank.
Number0000
VariantThe unique variant name of the Ariba Procurement realm. For example, VREALM_2.
PartitionThe unique partition name of the Ariba Procurement realm. For example, PREALM_2.
LowSequential number of Storage Location address. For example, 3.

To Maintain Sequential Number of Storage Location Address:

  1. Run the transaction code SPRO

    Navigate to:

    SAP IMG structure highlights paths for Master Data Integration under Maintain Filters, focusing on Cross Application and Procurement nodes.
    • Integration with Other SAP Components
    • SAP Ariba Cloud Integration Gateway
    • Master Data Integration
    • General Settings
    • Maintain Parameters
    • Procurement
  2. The Parameters– Ariba Procurement Master Data page appears.Parameters - Ariba Procurement Master Data screen allows modifying settings for variables like BALANCE_SHEET_ACCOUNTS and CHANGELOG_RETENTION_DAYS using Modify.
  3. Click Modify button.
  4. Enter the required details.Parameters - Ariba Procurement Master Data screen displays settings for variables like SEQUENTIAL_ADDRESS_NUMBER with relevant details like variants and partitions.
  5. Click Save.

Activity 2.3.3d SAP Ariba Cloud Integration Specific Configuration in SAP System – Transaction Specific Setting - Maintain Parameter for MRO Inventory Details

You need maintain this parameter to include MRO inventory details in the catalog uploads from SAP system to Ariba Procurement. Maintain this parameter for exporting Storage Locations in the ARBCIG_BUYER_CATALOG_EXPORT program.

  • Set the value for this field to extract the storage location.
    • The storage location is used in the catalog CIF file.
    • Enabling this field would allow buyers to set the storage location filter available in the Buyer Catalog Export Program.
  • The value of Stock indicator would be TRUE in the CIF file if the stock is greater than zero. The inventory information is pushed from SAP Ariba Procurement to IMS to fetch the stock details via QSR or DSR only if the inventory item is marked as MRO Inventory.
  • Maintaining this parameter will include: Material Number; Material Group; Plant ID; Storage Location & Stock Indicator in Catalog CIF file.
FieldDescription
Variable NameENABLE_MRO_INVENTORY
Field NameLeave blank.
Number0000
VariantThe unique variant name of the Ariba Procurement realm. For example, VREALM_2.
PartitionThe unique partition name of the Ariba Procurement realm. For example, PREALM_2.
LowSpecify X to include Material Number; Material Group; Plant ID; Storage Location & Stock Indicator in Catalog CIF file .Leave blank if you do not want to include storage location in the Catalog CIF file.

To Maintain Parameter for MRO Inventory Details:

  1. Run the transaction code SPRO

    Navigate to:

    Screenshot of SAP IMG menu displaying navigation paths for various integrations, highlighting Catalog Upload Request under Master Data Integration.
    • Integration with Other SAP Components
    • SAP Ariba Cloud Integration Gateway
    • Master Data Integration
    • General Settings
    • Maintain Parameters
    • Catalog Upload Request
  2. The Parameters– Catalog Upload Request page appears.SAP screen for Parameters - Catalog Upload Request, showing variable names with options to modify configuration and toggle settings.
  3. Click Modify button.
  4. Enter the required details.SAP Parameters screen for Catalog Upload Request, displaying variable names, field names, and configuration details for customization.
  5. Click Save.

Activity 2.3.3e SAP Ariba Cloud Integration Specific Configuration in SAP System – Transaction Specific Setting - Set Filter for Storage Location in Catalog Export

You can set the Storage Location Filter in the ARBCIG_BUYER_CATALOG_EXPORT program to export data for only the specified storage locations.

SAP Buyer Catalog Export screen displaying catalog configuration, filters, storage location filter, and data fields for export formatting.
  • Ensure that you have the necessary authorization to run the master data program.
  • Check the box for this filter while executing Catalog Export program if you want to export information for only the specified set of storage locations as part of the Catalog Master Data export to SAP Ariba Procurement.

Activity 2.3.4 SAP Ariba Cloud Integration Specific Configuration in SAP System – BAdI Implementation (optional)

You can use the BAdI provided for Stock Availability request to massage the data as per your specific custom requirements.

SAP IMG menu highlighting path for BAdI for Stock Availability Request configuration under SAP Ariba Procurement Integration and Business Add-Ins.
  • BAdI implementation is optional.
  • BAdI Name: ARBCIG_STOCK_AVAILABILITY
  • Implementation Method: PREPROCESSING. This method is called before processing a Stock Check request.

Stock Reservation – Overview

Most organizations prefer to fulfill procurement requirements from the inventory first before opting to purchase externally.

  • When a buyer selects a material item from the catalog for procurement, the catalog indicates whether the item is available in the inventory.
  • Buyers can check the available stock of a material while creating a Purchase Requisition & place a request to reserve material items that are present in the inventory before initiating the external purchasing process.
  • A Reservation Request is created in SAP system & a reservation number is sent back to Ariba Procurement. A Reservation Request does not block the available stock.
  • The request is used as an information to make informed decisions on procuring stock for future requirements. The Reservation Request number is quoted by buyers when requesting for stock from the stores.
    • For example, in larger organizations when a Reservation Request is made for an item, the store in-charge can check for the stock available in different plants & storage locations.

The store in charge can then distribute materials from various locations or procure if there is a shortage of stock for a given location.

  • Reservation of stock would ensure that the required quantity of the item is available in stock when required.
  • If the buyer does not receive the reservation number in response to the reservation request, they can resend the request.
  • CIG will identify the transaction & not process a duplicate request, but would attempt to resend the reservation number. The buyer can not modify a reservation request but can delete the request.
  • As a reservation request does not block any stock, a reservation can be made even if the available stock is zero or less than the required quantity.
    • Disable the DisallowReservationOnInsufficientStock parameter in SAP Ariba Procurement to allow this functionality.

Prerequisites:

  • Enable the Enable Inventory Reservation parameter in SAP Ariba Procurement (via SR).
  • Enable the following events while enabling CIG for creation & deletion of reservation request & its response:
    • ReservationAsyncExportRequest
    • ReservationDeleteAsyncExportRequest
    • ReservationAsyncImportPullRequest
    • ReservationDeleteAsyncImportPullRequest
  • Disable the DisallowReservationOnInsufficientStock parameter if you want to allow reservation when the stock is 0 or less than the requested quantity.
  • Make sure that you have enabled & implemented required features & parameters for Stock Availability before hand to have the updated stock information in Ariba Procurement.
  • Configure required inbound & outbound proxies to enable transactions between SAP system & Ariba Procurement for reservation of unrestricted stock.

Restrictions:

  • A reservation request cannot be edited.
  • You cannot add inventory items to change orders.
  • Storage location export from SAP system to Ariba Procurement is supported only through full load.
  • Line item level or header level comments are not supported in a reservation request.

Process Flow:

Flowchart explaining the procurement process in SAP Ariba, detailing catalog search, item selection, quantity reservation, and purchase requisition steps.

Note

+: Multiple reservation documents are created as necessary based on Account Assignment Category & need by date because in SAP the reservation is created using Tcode - MB21 & there Account Assignment Category is linked to the Movement Type field which is at header level & not at line level.

Process Flow Notes:

  • Multiple reservation documents are created as necessary based on Account Assignment Category & need by date because in SAP the reservation is created using Tcode – MB2.
  • The Account Assignment Category is linked to the Movement Type field which is at header level & not at line level.

Additional Notes:

  • Although the material items that you require are present in the inventory, you can choose to procure them through external purchases.
  • You can move the inventory line items to the table that contains the line items for ordering. You can perform this action while creating or editing the Purchase Requisition, or while submitting it, or while approving it.
  • To override inventory reservations, you must belong to the Storeroom Manager group.
  • You can override inventory reservations only in the first version of the Purchase Requisition.

Reservation Document:

Reservation documents are created for inventory items that are requested in a Purchase Requisition (PR).

  • When the first version of the PR is submitted & approved, one or more reservation documents are created.
  • The reservation documents are created by grouping the inventory line items based on the accounting type & the date by which the items are needed.
  • Subsequently, you cannot change the inventory line items in the requisition & therefore, you cannot modify the reservation documents.
  • You can only cancel the reservation documents after the state changes to Reserved.
Reservation Document StatusDescription
ReservingThe reservation document is created & sent to SAP system after the Purchase Requisition is submitted & fully approved.
ReservedA successful reservation notification is received from SAP system.
FailedA reservation failure notification is received from SAP system.
CancellingThe reservation document is cancelled in Ariba Procurement & the cancellation notification is sent to SAP system.
CancelledA successful cancellation notification is received from SAP system.

Configuring Stock Reservation Integration

Activity 4.1 SAP Ariba Cloud Integration Specific Configuration in SAP Ariba Procurement

To enable features and parameters, Service Requests (SRs) must be submitted through SAP Ariba Customer Support, as follows:

NameParameterDescription
FeatureInventoryReservation 
ParameterApplication.Purchasing.EnableInventoryReservation 
ParameterApplication.Catalog.IS.TenantConfig
  • This is used for setting the frequency for Delta Stock Request. This is to be defined by customer via SR.
  • JASON expression for above parameter where "freq’ to be set by customer for Delta Stock Request via SR – [ { "freq": 10, "tenantId": 122, "catalogQualifier": [ "an70000000004: InventoryItems2","an70000000004: InventoryItems"] } ]
ParameterApplication.Common.EnablePlantBasedDefaultingFor
  • Required Master Data for this parameter: Import Plants Data; Import Plants to Purchase Organization Mapping & Import Storage Location.
  • Values available in Ariba Procurement for these master data objects must match with what is there in Catalog Master Data.
Type DefinitionsMaterial Number; Material Group; Plant; Storage Location & In Stock flag (identifier)
  • This request will add the required custom catalog fields (supplementary attributes) to enable inventory related information to be consumed & displayed in the catalog user interface.

Next, enable CIG in SAP Ariba Procurement, by selecting the following integration tasks:

  • Export Reservation Request Asynchronously
  • Export Reservation Deletion Request Asynchronously

Activity: 4.2 SAP Ariba Cloud Integration Specific Configuration in CIG

Buyer users need to perform following activities:

  1. Add / update SAP System information or ensure that the information sent from your SAP System is available in CIG.
  2. Create the Project for Ariba Procurement product.
  3. Add a Connection.
  4. Define Cross References ReservationAsyncExportRequest document type.
  5. Define Lookup Values based on your requirements (not required for Stock Reservation Integration).
  6. Ensure that your realm ID is correctly selected.
  7. Confirm & Test the project to get ready for deployment to Production.

Additional Note:

  • You can define values for the specific movement types per Account Assignment Type for ReservationAsyncExportRequest document type on the Cross Reference page in CIG.
  • If the values are not configured for the movement type, they would default to the following:
    • Project Movement Type – 221
    • Cost Center Movement Type – 201
    • Asset Movement Type – 241
    • Internal Order Movement Type – 261

Note

To know more about these activities, please refer to the CIG Project Configuration unit of the AR822 SAP Ariba Cloud Integration Gateway Administration course on SAP Learning Hub.

Activity: 4.3 SAP Ariba Cloud Integration Specific Configuration in SAP System

There are 4 sub-activities in this section:

  • 4.3.1 Global Settings
  • 4.3.2 General Settings
  • 4.3.3 Transaction Specific Settings
  • 4.3.4 BAdI Implementation (optional)

Activity: 4.3.1 SAP Ariba Cloud Integration Specific Configuration in SAP System- Global Settings

Ensure that following configurations of Global Settings section are in place –

  • Maintain Certificates
  • Send SAP Information to CIG
  • Maintain Parameters for Attachments Support
  • Maintain BAdIs as per your requirements

Note

To know more about these activities, please refer to the AddOn SPRO - Global Settings unit of the AR822 SAP Ariba Cloud Integration Gateway Administration course on SAP Learning Hub.

A quick recap on these configuration objects relevant to Stock Reservation:

  1. Maintain Certificates – For SSL handshake it is mandatory. Upload Loadbalancer certificate of CIG in STRUST.
  2. SAP Data Sync

Activity: 4.3.2 SAP Ariba Cloud Integration Specific Configuration in SAP System- General Settings

SAP IMG menu displaying the path for SAP Ariba Procurement Integration settings, highlighting General Settings under SAP Ariba Cloud Integration Gateway.

To set-up General Settings from within SAP System:

  • Run the transaction code SPRO – the Customizing: Execute Project screen appears.
  • Click SAP Reference IMG – the Display IMG screen appears.

Next, navigate to:

  • Integration with Other SAP Components
  • SAP Ariba Cloud Integration Gateway
  • Ariba Procurement Integration
  • General Settings

In order to enable the flow of messages between Inventory Management System (IMS) & SAP System, the user needs to set-up the following under General Settings:

SAP Ariba Procurement Interface Setup screen showing configuration options for data center, connection instances, logon data, and integration settings.
  • Setup the Interface
  • BAdIs for Setting Up the Interface (optional)

Select following Inbound & Outbound webservice messages while executing Interface Setup program:

  • Stock Availability Request (Inbound)
  • Stock Reservation Request (Inbound) - Only needed for reserving inventory items
  • Ingest Stock Request (Outbound)

Activity: 4.3.3 SAP Ariba Cloud Integration Specific Configuration in SAP System- Transaction Specific Settings

There are no any transaction specific configuration activities in SAP system for Stock Reservation integration.

Activity: 4.3.4 SAP Ariba Cloud Integration Specific Configuration in SAP System- BAdI Implementation (optional)

You can use the BAdI provided for Stock Availability request to massage the data as per your specific custom requirements. BAdI implementation is optional.

SAP IMG path for configuring SAP Ariba Procurement Integration, highlighting BAdI for Stock Reservation Request under Business Add-Ins (BAdIs).

BAdI Name: ARBCIG_STK_RESERVATION

Implementation Methods:

  • PREPROCESSINGCREATE: This method is called before processing a Stock Reservation request.
  • PREPROCESSINGCHANGE: This method is called before deleting a Stock Reservation request.
  • POSTPROCESSING: This method is called after processing a Stock Reservation request.

Learning

SAP FacebookSAP YoutubeSAP LinkedIn