Defining Proxy Overview

Objective

After completing this lesson, you will be able to describe how to configure receipt flow and Advanced Ship Notice (ASN) flow.

Proxy Overview

Proxies are executable interfaces that are generated for the target application language like ABAP / JAVA.

  • Proxies are used when ABAP applications (SAP ECC) need to send and receive data.
  • Proxies bypass the adapters and provide adapter less communication with the JAVA/ABAP business systems in landscape.
  • Proxies are generated from the WSDL description of interface objects and have same attributes as message interface. There are ABAP and JAVA proxies available.
  • Proxies can be used for Inbound and Outbound interfaces.
  • Proxies for outbound interfaces are called Client Proxies.
  • Proxies for inbound interfaces are called Server Proxies.

Supported Proxy Flows

Transaction NameInterface TypeDirection
Liability TransferCustom ProxyInbound
Remittance AdviceCustom ProxyInbound
Component Consumption RequestCustom ProxyInbound
Component AcknowledgementCustom ProxyInbound
Product Replenishment MessageCustom ProxyInbound
Service EntrySheetProxyInbound
Advance ShipNoticeEnterprise ServiceInbound
Credit Memo CancelCustom ProxyInbound
Quality NotificationCustom ProxyInbound
Quality Inspection ResultCustom ProxyInbound
Order Confirmation ApprovalCustom ProxyInbound
Replenishment OrderCustom ProxyInbound
FI Invoice ERP RequestCustom ProxyInbound
Quality Inspection RequestCustom ProxyOutbound
Remittance CancellationCustom ProxyOutbound
Quality Inspection DecisionCustom ProxyOutbound
ERPInitiated Service SheetCustom ProxyInbound
Invoice StatusUpdate ProxyCustom ProxyOutbound
Payment Proposal ProxyCustom ProxyOutbound
RequisitionCustom ProxyOutbound
Service Entry Sheet Response ProxyCustom ProxyOutbound
Product Activity MessageCustom ProxyOutbound
Receipt ProxyCustom ProxyOutbound
ShipNotice RequestEnterprise ServiceOutbound
Despatched Delivery NotificationEnterprise ServiceOutbound

Receipt Flow

Buyers generate receipts in the SAP system and send them to suppliers. When receipt data is successfully posted in Ariba Network, buyers can see the receipts in their online Outbox.

  • When buyers send a receipt for the goods received, the receipt also contains the delivery note in the header.
  • Buyers can only create receipts for standard Purchase Orders.

Receipt with Corrections and Returns:

Buyers can send Receipts with returns and corrections for the line items shipped against Purchase Orders. A negative value in the line item quantity denotes that there was a correction to the items received or returned. The following movement types support returns and corrections in Receipts:

  • 101, 103, and 105 to send received quantities
  • 102 to send corrections on the received quantity
  • 122, 124, and 161 to send returned quantities
  • 123 to send corrections on the returned quantities

Note

Buyers and suppliers on Ariba Network can view the details on the returns and corrections for line items in the purchase order on the purchase order details and the order history pages. The line items in the purchase order on Ariba Network also display the number of items received or returned.

Pre-requisites:

  • Configure the processing routines to create goods receipts on the SAP system.
  • Set up the user profile parameter to activate the collective slip for goods receipts.
  • Standard NACE or Message Determination configuration should be in place.
  • SAP Ariba AddOn package downloaded in your SAP system.
  • SAP Cloud Connector installed & configured (for Direct Connect option).
  • Supported middleware should be configured (for Mediated Connect option).
  • CIG is enabled through your AN Buyer Account & you have P User info.
  • SAP system information is sent to CIG.
  • AN Buyer and Supplier relationship should exist.
  • Receipts for Blanket Purchase Orders are not supported.

Receipt Flow - Configuration in SAP System

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

  • Define Authorizations
  • Enable Integration through Middleware
  • Maintain Certificates
  • Create RFC Destination (Not applicable for Receipt Integration)
  • Create Port Definition (Not applicable for Receipt Integration)
  • Configure Receiver Port (Not applicable for Receipt Integration)
  • Create Logical System (Not applicable for Receipt Integration)
  • Send SAP Information to CIG
  • Maintain Parameters for Attachments Support
  • Map Variants & Partitions (Not applicable for Ariba Network Integration)
  • Maintain BAdIs as per your requirements

To navigate to general settings in SAP ERP and SAP S/4 HANA for Ariba Network Transactions

  • Run the transaction code SPRO – The Customizing: Execute Project screen appears.
  • Click SAP Reference IMG – The Display IMG screen appears.
  • Navigate to –
    • Integration with Other SAP Components → SAP Ariba Cloud Integration Gateway → Ariba Network Integration → General Settings
SAP IMG screen showing navigation to Ariba Network Integration and General Settings, highlighting SAP Ariba integration configuration options in the structure tree.

Ensure that following configurations of General Settings section are in place:

  • Setup the Interface
  • BAdIs for Setting Up Interface
  • Create Partner Profile for House Bank (Not applicable for Receipt Integration)
  • Configure Document Status Update
  • Enable Supply Chain Collaboration (based on requirement)
  • Enable Vendors
  • Maintain Vendor for the Outbound Transaction
  • Enable External Format Conversion
  • Plant Specific Time Zone Conversion

Transaction Specific Settings

SAP IMG screen showing Ariba Network Integration, highlighting General Settings and Application Specific Settings under SAP Ariba Cloud Integration Gateway configuration.
  • Run the transaction code SPRO – The Customizing: Execute Project screen appears.
  • Click SAP Reference IMG – The Display IMG screen appears.
  • Navigate to:
    • Integration with Other SAP Components
    • SAP Ariba Cloud Integration Gateway
    • Ariba Network Integration
    • Application Specific Settings

All the supported transactions for Ariba Network Integration are listed under Application Specific Settings.

Information on how to configure each of the supported Network transactions is in the SAP Ariba Cloud Integration Gateway Configuration Guide.

In this section, we will look into the configurations of a sample Proxy outbound (Receipt) transaction required on the SAP AddOn to map the transactions and messages to cXML and send it to Ariba Network.

To send a Receipt from an SAP System to Ariba Network, you need to perform following activities –

  • Define Message Output Control for Returns & Corrections
  • Maintain Parameters for Receipt Request
  • Configure User Profile Parameters to Activate Collective Slip after Receipt
  • Maintain Printer Default Values for Returns and Corrections in Receipts

Transaction Specific Settings - Define Message Output Control for Returns and Corrections

Steps

  1. Navigate to:

    • Integration with Other SAP Components
    • SAP Ariba Cloud Integration Gateway
    • Ariba Network Integration
    • Application Specific Settings
    SAP IMG screen displaying SAP Ariba Cloud Integration Gateway structure, highlighting Receipt Request under Application Specific Settings for integration configuration.

  2. Expand the Receipt Request section & click IMG-Activity for "Define Message Output Control for Returns and Corrections"

    The Conditions for Output Control screen appears.

    SAP IMG screen highlighting Define Message Output Control for Returns and Corrections under Receipt Request settings for output configuration management.

  3. Select ME Inventory Management & click Output types.

    SAP Conditions for Output Control screen, Output types tab selected, highlighting ME for Inventory Management in the application description list.

    The Display View "Output Types": Overview screen appears.

  4. Click the Change button, double-click Output Type WE03.

    SAP Change View “Output Types” screen showing output type selection for ME application, highlighting WE03 GR Note Version 3 entry.

    The Change View "Output Types": Details screen appears.

  5. On the General Data tab, for Access sequence choose: 0003 Trans.Type/Print Vers./Indic.

    SAP Change View “Output Types” Details screen for WE03 GR Note Vers.3, displaying access sequence, output program, and configuration settings.

  6. Click the tab Default Values, retain the following values in the tab:

    • Dispatch Time: Send immediately (when saving the application)
    • Transmission Medium: Special function
    • Partner Function: LS
    SAP Change View Output Types Details screen, Default values tab selected for WE03 GR Note Vers.3, displaying dispatch time and partner function.

  7. Click Save, then go back to the main screen.

  8. From the main screen, choose ME Inventory Management & click Output Types.

    SAP Conditions for Output Control screen with Output types tab selected, showing application codes CF and CV with corresponding descriptions.
    Highlighted SAP application code ME for Inventory Management in the Output Control configuration screen, used for inventory-related output types.

    The Display View "Output Types": Overview screen appears.

  9. Choose WE03; double-click Processing routines.

    SAP Output Types overview screen showing navigation tree. Processing routines is highlighted. Output type WE03 GR Note Vers.3 is selected in the list.

    Enter the following values:

    • Program: ARBCIG_RECEIPT_PUBLISH
    • FORM routine: SEND_GOODSRECIPT_SAVED
    SAP Processing routines overview for Output Type WE03, Application ME. Special function row highlighted with ARBCIG_RECEIPT_PUBLISH and SEND_GOODSRECEIPT_SAVED displayed.

  10. Press Enter & Save the entry.

  11. Click ME Inventory Management & then click Condition records.

    SAP Conditions for Output Control screen with Condition records tab highlighted. Applications CF and CV with descriptions are displayed in the table.
    SAP application list with ME Inventory Management highlighted between MD Direct Procurement and MR Invoice Verification in the displayed selection.

    The Output Types popup appears.

  12. Double-click the output type: WE03.

    SAP Conditions for Output Control screen with ME Inventory Management selected, Output Types window open, WE03 GR Note Vers.3 highlighted.

    The Change GR Note Vers.3 (WE03): Selection screen appears.

  13. Enter the following information:

    • Trans./Event Type: WE
    • Print Version: 3 (Collective Slip)
    • Print Item: 1 (Material Document Printout)
    SAP Change GR Note Vers.3 (WE03) Selection screen showing Trans./Event Type WE, Print Version 3, Print item 1 highlighted.

  14. Click Execute.

    The Change Condition Records (GR Note Vers.3): Fast Change screen appears.

  15. Maintain the following parameters for the partner function:

    • Function: LS
    • Medium: Special function or Print output
    • Date/Time: Send immediately (when saving the application)
    • Language: EN
    SAP Change Condition Records screen for GR Note Vers.3, showing Trans./Event Type WE, Print Version 3, language set to EN.

  16. Click Save.

Transaction Specific Settings - Maintain Parameters for Receipt Request (SP0001)

SAP Parameters - Receipt Request screen showing table with Variable Name GOODSRECEIPT, field names for movement types, and corresponding numbers and values.

  • Run the transaction code SPRO – The Customizing: Execute Project screen appears.

  • Click SAP Reference IMG – The Display IMG screen appears.
  • Navigate to:
    • Integration with Other SAP Components
    • SAP Ariba Cloud Integration Gateway
    • Ariba Network Integration
    • Application Specific Settings
  • Expand the Receipt Request section & click IMG-Activity for "Maintain Parameters for Receipt Request"

The Parameters – Receipt Request screen appears.

  • Maintain parameters as mentioned in the table.

Parameter NameDescriptionSupported values
GOODSRECEIPTSpecify a movement type such as 101, 103, 104. To specify another movement type, create the same variable & field name in another row and increment the Number value to 2.
  • Variable Name: GOODSRECEIPT
  • Field Name: RECEIPT_MVT
  • Number: 0000
  • Low: 101, 103, 104, for example
GOODSRECEIPTCan be left blank or provide a movement type, for example 102.
  • Variable Name: GOODSRECEIPT
  • Field Name: RECEIPT_MVT_REVERSAL
  • Number: 0000
  • Low: 102, for example.
GOODSRECEIPTSpecify a movement type such as 122, 124, or 161 or can be left blank. To specify another movement type, create the same variable and field name in another row and increment the Number value to 2.
  • Variable Name: GOODSRECEIPT
  • Field Name: RETURN_MVT
  • Number: 0000
  • Low: 122, 124, 161, for example.
GOODSRECEIPTCan be left blank or provide a movement type, for example 123.
  • Variable Name: GOODSRECEIPT
  • Field Name: RETURN_MVT_REVERSAL
  • Number: 0001
  • Low: 123, for example.

Transaction Specific Settings - Maintain Parameters for Receipt Request (SP0002 and Above)

SAP Change View Allowed ReceiptRequest Messages: Overview screen with New Entries button and empty table for Mvmt Type and Stock Type.

  • Run the transaction code SPRO – The Customizing: Execute Project screen appears.

  • Click SAP Reference IMG – The Display IMG screen appears.
  • Navigate to:
    • Integration with Other SAP Components
    • SAP Ariba Cloud Integration Gateway
    • Ariba Network Integration
    • Application Specific Settings
  • Expand the Receipt Request section & click IMG-Activity for "Maintain Parameters for Receipt Request"

The Change view "Allowed ReceiptRequest Messages": Overview screen appears.

  • Maintain parameters as mentioned in the table.
Parameter NameSupported values
MVMT Type
  • Ex: 101, 103, 104, for example
Stock Type
  • Unrestricted-use
  • Quality Inspection
  • Blocked

Transaction Specific Settings - Configure User Profile Parameters to Activate Collective Slip After Receipt

SAP Display IMG screen showing SAP Ariba Cloud Integration Gateway structure, including Global Settings, Ariba Network Integration, and Application Specific Settings.
SAP Receipt Request menu showing Configure User Profile Parameters to Activate Collective Slip after Receipt highlighted among related configuration options.
  • Navigate to:
    • Integration with Other SAP Components
    • SAP Ariba Cloud Integration Gateway
    • Ariba Network Integration
    • Application Specific Settings
  • Expand the Receipt Request section & click IMG-Activity for "Configure User Profile Parameters to Activate Collective Slip after Receipt"
SAP Maintain User Profile screen showing parameter NDR with value 'X' for print via output control in MM - Inventory management.

The Maintain User Profile screen appears

  • In the Parameters tab, maintain following values:
    • Set/Get parameter ID: NDR
    • Parameter value: X
    • Short Description: Print via output control in MM-Inventory management.

Click Save.

Transaction Specific Settings - Maintain Printer Default Values for Returns and Corrections in Receipts

SAP Display IMG screen with Maintain Printer Default Values for Returns and Corrections in Receipts highlighted under Application Specific Settings, Receipt Request.
  • Navigate to:
    • Integration with Other SAP Components
    • SAP Ariba Cloud Integration Gateway
    • Ariba Network Integration
    • Application Specific Settings
  • Expand the Receipt Request section & click IMG-Activity for "Maintain Printer Default Values for Returns and Corrections in Receipts"
SAP screen for adding new entry with condition type, plant, storage location, output device set, and print immediately option selected.

The Change View "Print Parameters": Overview screen appears.

  • Click New Entries – The New Entries: Details of Added Entries screen appears.
  • Maintain following values:
    • CType (Condition Type): WE03
    • Plant: 001 (For example)
    • Stor. Location: 001 (For example)
    • OutputDevice: Select the printer of your location.
    • Print immediately: (Optional) Check the checkbox for the option.
  • Click Save.

Receipt Flow - Configuration in CIG

The user will need to perform the following activities. All these are discussed in CIG Configuration session. In this lesson, we will only focus on the configurations in CIG that are specific to Receipt integration:

  • Enable CIG for your Ariba Network Buyer Account.
  • Provide Basic Information in the project in CIG for "Product = Ariba Network".
  • Define Connection information to establish connectivity between CIG & your SAP system.
  • Define Cross Reference for Parameter for Receipt (Doc Type – ReceiptRequest)
  • Define Cross References for UOM.
  • Define Cross Reference for Lookup Table not required for Ariba Network Receipt Integration.
  • Review project configuration & Confirm the Project.
  • Test the Project.
  • Deploy the Project.

Cross-Reference Configuration - Parameter

You need to define values in the parameter fields that you want to map. The transactions & the related parameters are added by the administrator. You can define the values for both test & production environments.

Follow these steps to define parameters:

Steps

  1. Select the Document Type = ReceiptRequest in "Parameters" tab & click Add.

    SAP Cloud Integration Gateway Project Wizard showing Cross Reference Configuration step, with ReceiptRequest document type selected and Add button highlighted.

  2. Edit the entry.

    Document type ReceiptRequest highlighted in the list, with edit icon selected under Action column for configuration in SAP Cloud Integration.

  3. Enter values for the parameters in the TEST Environment and PROD Environment & click Save. If you want to have different value in PROD Environment, uncheck the box Use same values.

    ReceiptRequest configuration screen showing test and production environment fields, use same values checkbox, and Save or Cancel options highlighted.

  4. Enter parameter values for another Document Type as needed or click Next.

    SAP Cloud Integration Gateway Cross Reference Configuration screen with document type dropdown expanded, showing multiple options, and Next button highlighted.

Receipt Flow - Configuration in CIG - Cross-Reference Configuration - Parameter

Cross Reference – Parameter:

  • Comp Acknw Line Text ID: Provide the text ID of a specific comment field at line item level that you would want to map in a Component Acknowledgement received from Ariba Network. This is only used in Supply Chain Collaboration flow.
  • Receipt Default Lang: Always maintain "en" for English.
  • Comp Acknw Header Text ID: Provide the text ID of a specific comment field at header level that you would want to map in a Component Acknowledgement received from Ariba Network. This is only used in Supply Chain Collaboration flow.

Note

Text ID: The Text ID is an identifier to differentiate between various types of texts / comments. In SAP system, you can find more than one text / comment fields at header as well as line item level. Each of these text / comment fields are identified by a unique Text ID.

Receipt Flow - Configuration in Ariba Network

Please note that there is no configuration required in Ariba Network specific to Receipt integration.

Thus, it is not covered in this lesson.

Advanced Ship Notice (ASN) Flow

An Advanced Ship Notice (ASN) is a document that provides detailed information about a pending delivery. The purpose of an ASN is to notify the customer when shipping occurs and provide physical characteristics about the shipment so the customer can be prepared to accept delivery.

Suppliers send a ship notice from Ariba Network when the they are ready to ship the items on the Purchase Order. You can receive the following ship notices from Ariba Network suppliers:

  • A single Ship Notice against multiple Purchase Orders.
  • Multiple Ship Notices against a single or multiple line items in a Purchase Order.
  • Ship Notices against Purchase Orders having line items with zero quantity to indicate the items are not shipped.
  • Ship Notices against a Purchase Order having material line-items.
  • Ship Notices against Purchase Orders having the BatchID for the line items.

You need to configure your SAP system to accept Ship Notices against multiple Purchase Orders.

Additional Information:

  • To use confirmation control keys, you need to specify the confirmation control key in Purchase Orders.
  • The Manufacturer Part ID is included in the ASN created against the PO if it is mentioned while creating the PO.
  • The manufacturer Part ID is available in order confirmations and ship notices for material type HERS only.

Pre-requisites:

  • Ariba AddOn package should be available (downloaded) in your SAP system.
  • SAP Cloud Connector should be installed & configured (for Direct Connect option).
  • Supported middleware should be configured (for Mediated Connect option).
  • CIG is enabled through your AN Buyer Account & you have P User info.
  • SAP system information is sent to CIG.
  • AN Buyer & Supplier relationship should exist.
  • Purchase Order configuration should be in place.

Advanced Ship Notice (ASN) Flow – Configuration in Ariba Network

Specify default transaction rules

Steps

  1. Login to your Ariba Network Buyer account.

    • Click on Administration
    • Click on Configuration
    SAP Ariba Network screen showing Administration menu with Configuration option highlighted, vendor enablement status, and vendor summary widgets displayed.

  2. Click on Default Transaction Rules.

    SAP Ariba Network configuration screen with Default Transaction Rules option highlighted, allowing users to review and update company settings and preferences.

  3. Specify the rules by checking boxes against individual rules, click Save.

    Order Confirmation and Ship Notice Rules screen showing various supplier confirmation options, with checkboxes and radio buttons for configuration in SAP Ariba.

    Note

    Specifying ASN Transaction Rules is completely based on business requirements of individual customer.

Advanced Ship Notice (ASN) Flow – Configuration in CIG

In this topic we will focus on the configurations in CIG that are very specifc to ASN integration.

  • Enable CIG for your Ariba Network Buyer Account.
  • Provide Basic Information in the project in CIG for "Product = Ariba Network".
  • Define Connection information to establish connectivity between CIG & your SAP system.
  • Define Cross Reference for Parameter for ASN (Doc Type – ShipNoticeRequest)
  • Define Cross References for UOM.
  • Define Cross Reference for Lookup Table not required for Ariba Network ASN Integration.
  • Review project configuration & Confirm the Project.Test the Project.
  • Deploy the Project.

Cross-Reference Configuration - Parameter

You need to define values in the parameter fields that you want to map. The transactions & the related parameters are added by the administrator. You can define the values for both test & production environments.

Follow these steps to define parameters:

Steps

  1. Select the Document Type = ShipNoticeRequest in "Parameters" tab & click Add.

    SAP Cloud Integration Gateway Cross Reference Configuration screen with ReceiptRequest document type selected, Add button highlighted, and navigation steps shown.

  2. Edit the entry.

    ReceiptRequest document type highlighted with edit icon selected in Action column, showing configuration options for test and production environments in SAP

  3. Enter values for the parameters in the TEST Environment and PROD Environment & click Save. If you want to have different value in PROD Environment, uncheck the box Use same values.

    ReceiptRequest configuration screen showing test and production environment fields, use same values checkbox, and Save or Cancel buttons highlighted.

  4. Enter parameter values for another Document Type as needed or click Next.

    SAP Cloud Integration Gateway Cross Reference Configuration screen with document type dropdown expanded, Next button, and navigation step highlighted in Project Wizard.
    • Default Lang: Always maintain "en" for English.
    • Line Text ID ASN: Provide the text ID of a specific comment field at line item level of your inbound delivery in SAP system that you would want to map in an ASN received from Ariba Network.
    • Header Text ID DDN: Provide the text ID of a specific comment field at header level of your invoice in SAP system that you would want to map in an invoice received from Ariba Network.
    • Line Text ID DDN: Provide the text ID of a specific comment field at line item level of your invoice in SAP system that you would want to map in an invoice received from Ariba Network.
    • Header Text ID ASN: Provide the text ID of a specific comment field at header level of your inbound delivery in SAP system that you would want to map in an ASN received from Ariba Network.

    Note

    Text ID: The Text ID is an identifier to differentiate between various types of texts / comments. In SAP system, you can find more than one text / comment fields at header as well as line item level. Each of these text / comment fields are identified by a unique Text ID.

Advanced Ship Notice (ASN) Flow – Configuration in SAP Systems

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

  • Define Authorizations
  • Enable Integration through Middleware
  • Maintain Certificates
  • Create RFC Destination (Not applicable for ASN Integration)
  • Create Port Definition (Not applicable for ASN Integration)
  • Configure Receiver Port (Not applicable for ASN Integration)
  • Create Logical System (Not applicable for ASN Integration)
  • Send SAP Information to CIG
  • Maintain Parameters for Attachments Support
  • Map Variants & Partitions (Not applicable for Ariba Network Integration)
  • Maintain BAdIs as per your requirements

To navigate to general settings in SAP ERP and SAP S/4 HANA for Ariba Network Transactions

  • Run the transaction code SPRO – The Customizing: Execute Project screen appears.
  • Click SAP Reference IMG – The Display IMG screen appears.
  • Navigate to –
    • Integration with Other SAP Components → SAP Ariba Cloud Integration Gateway → Ariba Network Integration → General Setting
SAP Display IMG screen showing navigation to Ariba Network Integration and General Settings under SAP Ariba Cloud Integration Gateway structure.

Ensure that following configurations of General Settings section are in place:

  • Setup the Interface
  • BAdIs for Setting Up Interface
  • Create Partner Profile for House Bank (Not applicable for ASN Integration)
  • Configure Document Status Update
  • Enable Supply Chain Collaboration (based on requirement)
  • Enable Vendors
  • Maintain Vendor for the Outbound Transaction
  • Enable External Format Conversion
  • Plant Specific Time Zone Conversion

Transaction Specific Settings

To configure Ariba Network transactions:

  • Run the transaction code SPRO – The Customizing: Execute Project screen appears.
  • Click SAP Reference IMG – The Display IMG screen appears.
  • Navigate to:
    • Integration with Other SAP Components
    • SAP Ariba Cloud Integration Gateway
    • Ariba Network Integration
    • Application Specific Settings
SAP Display IMG screen showing navigation to Application Specific Settings under Ariba Network Integration in SAP Ariba Cloud Integration Gateway.

All the supported transactions for Ariba Network Integration are listed under Application Specific Settings.

Information on how to configure each of the supported Ariba Network transactions is detailed out in SAP Ariba Cloud Integration Gateway Configuration Guide.

In this session we will look into the configurations of sample Proxy inbound (ASN) transaction required on the SAP AddOn to map the transactions and messages received from Ariba Network to the SAP Proxy structure.

To receive ASNs sent by suppliers from Ariba Network to SAP System, you need to perform following activities:

  • Configure Advance Ship Notice to Receive Ship Notices with Zero Quantities.
  • Maintain Carrier Details for Vendors
  • Export the Packaging Data for Handling Units to Ariba Network

Advanced Ship Notice (ASN) Flow – Configuration in SAP System – Transaction Specific Settings

Transaction Specific Settings

Configure Advance Ship Notice to Receive Ship Notices with Zero Quantities

Steps

  1. Navigate to:

    • Integration with Other SAP Components
    • SAP Ariba Cloud Integration Gateway
    • Ariba Network Integration
    • Application Specific Settings
    SAP IMG screen showing navigation path. Advance Ship Notice highlighted for configuration.

  2. Expand the Advanced Ship notice section & click IMG-Activity for "Configure Advance Ship Notice to Receive Ship notices with Zero Quantities".

    SAP IMG menu highlighting “Configure Advance Ship Notice to Receive Ship Notices with Zero Quantities” option under Advance Ship Notice section.

    The Deliveries: Item Categories-picking": Overview screen appears.

    • Click Position & then enter ELN as the Item category.
    • For ELN, ensure that the checkbox Relevant for picking is blank.
    • Click Save.

    The Deliveries: Item Categories-picking": Overview screen appears.

  3. Click Position & then enter ELN as the Item category.

    SAP screen showing “Deliveries: Item categories - picking” overview, with popup for adding item category ELN, and Position button highlighted.

  4. For ELN, ensure that the checkbox Relevant for picking is blank.

    SAP screen showing “Deliveries: Item categories - picking” overview, with ELN Inbound Delivery selected, and Save button highlighted in toolbar.

  5. Click Save.

Transaction Specific Settings - Maintain Carrier Details for Vendors

Steps

  1. Navigate to:

    • Integration with Other SAP Components
    • SAP Ariba Cloud Integration Gateway
    • Ariba Network Integration
    • Application Specific Settings

  2. Expand the Advanced Ship notice section & click IMG-Activity for "Maintain carrier details for Vendors"

    SAP IMG menu showing path to “Maintain Carrier Details for Vendors” option under Advance Ship Notice in Ariba Network Integration settings.

    The Change View "Shipping Notification: Carrier Mapping": Overview screen appears.

  3. Maintain Ariba Carrier Domain, Ariba Carrier ID and Vendor ID.

    SAP GUI toolbar with navigation, save, back, exit, and help icons at the top of a configuration overview screen.

    Click Save.

Export the Packaging Data for Handling Units to Ariba Network

Steps

  1. Navigate to:

    • Integration with Other SAP Components
    • SAP Ariba Cloud Integration Gateway
    • Ariba Network Integration
    • Application Specific Settings

  2. Expand the Advanced Ship notice section & click IMG-Activity for "Export the Packaging Data for Handling Units to Ariba Network"

    SAP IMG menu highlighting “Export the Packaging Data for Handling Units to Ariba Network” under Advance Ship Notice in Ariba Network Integration.

    The Export screen appears.

  3. Choose path for File output, give the file name as "INSTRUCTIONS".

    SAP screen for exporting packaging data to Ariba Network, highlighting file path selection field for output directory and file name.

Demo – Advanced Ship Notice

In this demo we will:

  • Review and Send Ship Notice as Supplier
  • Review Ship Notice in Buyer Inbox
  • Validate Ship Notice Request Status in CIG
  • Validate Ship Notice Details in SAP ECC

Learning

SAP FacebookSAP YoutubeSAP LinkedIn