High- Level Specification

Functional Overview

Reply messages are sent to Ariba Guided Buying after successful processing - in the technical terms -  of the Receipt message received from Ariba Guided Buying. Reply message can contain either way positive reply after the message from Ariba Guided Buying has not raised any validation issue or the details of the error message. Due to the asynchronous nature of the Receipt create interface, reply message for these events is sent as a dedicated separate message and it's not part of the Receipt interface. 

• In a case of a successful processing in S/4 Hana, reply message contains ARIBA_GR_NO - the unique reference of the Receipt Created in Ariba Guided Buying and MAT_DOC_NO - stored in the ERPReceiptNumber - the Receipt ID assigned in S/4 Hana
• In a case of validation errors occurring in S/4 Hana, reply message contains ARIBA_GR_NO and the list of error messages generated by S/4 Hana validation logic

Message is initiated within CIG Addon, mediated by the CIG where it's translated into SOAP message to be received by Ariba Guided Buying

Scope and Objectives

This document describes S/4 Hana sending outbound message sent after the processing of Receipt Create inbound message. This is a specific message type for Receipts only, as opposite to the generic message used by other transactional documents, for example Purchase Order.

Integration event Import Receipt Status Asynchronously must be enabled in Ariba Guided Buying. 

Process Flow Diagram

Process flow is identical with ERP-68  - functional specification describing PO Create / Change and Cancel

Assumptions

• Ariba Guided Buying is utilized for integration of Purchase Orders and Receipt with S/4HANA System.
• Ariba source object and S/4HANA System target field mappings, including custom fields, will be updated based on mapping requirements in S/4HANA System

Dependencies

• All configurations should already be implemented before the interface is deployed.
• Ariba Buying packages have been successfully installed and configured in S/4HANA System.
• The connection information for Web-Services based integration have been successfully configured in Ariba Buying.
• Receipt parameters have been configured in Ariba Guided Buying.
• Master data loaded in Ariba Guided Buying is synchronized with S/4HANA System.

Security, Integrity and Controls

The following are the Security and Authorization considerations for this interface:

• Define a Web Services Security certificate and/or the shared secret key to use to secure the End Point connection.
• Access to interface parameters in Ariba Guided Buying are being addressed by Ariba standard security controls. Only authorized person with Ariba administrator’s role can access/ change interface parameters.
• Web service security configuration allows secure communications protocol provides a means for applying security to Web services.

Configuration Requirements

Prerequisite for this interface is the configuration from ERP-68 Functional Specification. On top of this

Ariba Configuration

Integration event Import Receipt Status Asynchronously must be enabled

CIG Addon Configuration

Parameter ENABLE_FEH must be set to X in order to for S/4 Validation errors to be sent back to Ariba Guided Buying

Special Requirements

Not Applicable

Design Rationale

Not Applicable

API Use

Not Applicable

Data Structure

Source Structure and Target Structure

Standard mappings are a subject to change and are not linked in this documentation, latest excel sheet can be downloaded from CIG → Resources → Implementation Guides → Mapping Specs → Ariba Buyer

• ResponseGoodsReceipt (Soap to Proxy)

Mapping contains basic field mapping from RPC Structure to the SOAP message with the basic logic explained

Processing Logic

Processing within Source

Message is triggered within ARBCIG_GOODS_RECEIPT_CREATE after the Receipt processing logic is finished. Reply is sent from the SEND_RESPONSE form, which collects the error messages if any and calls function ARBCIG_SAP_RESPONSE_TO_P2P for the transaction type ReceiptAsyncImportPullRequest.

In a case the reply message has to be customized, BADI ARBCIG_ERP_RESPONSE_TO_P2P is available

Processing within Middleware

At this moment, standard transformation as referenced above is in place. In a case of any custom field is needed, custom field will be mapped in the CIG to the predefined custom field structure in the SAP

Processing within Target

In the case the reply message from S/4 Hana containsERPReceiptNumber and no errors, processing status of the Receipt is moved from Awaiting Processing to the final step - Processed. In the case the error message is returned from S/4 Hana, Receipt is in status Processing Failed with the error message displayed

Interface Alert & Monitoring

Language Requirements

Not Applicable

User Interface Requirements

Not Applicable 

Sequencing

Not Applicable

Volumetrics

Taking into account we target for 50-100 Pos a day, assume half of the POs are Materials that requires receiving - target for Receipts created a day would be 25-50

Performance Consideration

There are no specific performance requirements or considerations related to this interface.

Error Handling

If the Receipt Reply message fails to be delivered to Ariba Guided Buying, there's no automatic recovery in place. In such case, Receipt in Ariba Guided Buying are stuck in the Awaiting Processing state and the issue has to be investigated in the CIG transaction tracker and SRT_MONI on the SAP side. 

Testing

How to Test

testing is identical with  ERP-68 functional specification - the tests for the PO Create / Change / Cancel takes assume the reply message is delivered from S/4 Hana

Other Information

Development Details

Package

Other Development Objects

Appendix

See also

Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.

Change log