High- Level Specification

Functional Overview

A receipt is an acknowledgment of the goods that have arrived. The receiving process starts when an order has been sent to a supplier and the supplier ships goods in exchange. When the shipment arrives, the person who receives those items, submits a receipt to acknowledge that the items have indeed arrived.

Negative receipt can also be created in Ariba Buying to reverse some received quantity because of incorrect shipment or manual errors.

This document describes S/4HANA System inbound interface for sending goods receipt information from Ariba Buying to S/4HANA System for POs received in Ariba Guided Buying. Goods receipt data from Ariba Guided Buying will be exported to S/4HANA System via web service and loaded in S/4HANA as GR material document. 

Buyers using the Ariba Guided Buying integrated with S/4HANA System can create receipts using a standard SAP delivered Business Application Programming Interface (BAPI).

The following steps explain how a receipt export integration event works:

1. When Buyer creates a receipt in Ariba Guided Buying, the receipt object instance is auto approved.
2. When the receipt is auto approved one copy transmits to Ariba Network and S/4HANA System via CIG and the respective Receipt status is then sent back to Ariba Guided Buying.
3. The RFC returns a receipt line number and any error information to Ariba Guided Buying.

The format of the messages that are sent through the web services from Ariba Buying to S/4HANA System and the format of the expected responses from S/4HANA System are defined in WSDL files (Web Service Description Language). These files furthermore contain details about the web service end points like URLs and port numbers.

The export of data through web services is always initiated by Ariba Buying. Once a transaction has been completed in Ariba Buying, it immediately sends out a SOAP message to the configured web service end point.

The CIG transforms that SOAP message and passes the data from that message in the right format to the S/4HANA System backend. The S/4HANA System then returns either a success or error message (including error details) to the CIG. This reply from the S/4HANA System is finally sent back to Ariba Guided Buying as SOAP message through web services.

Ariba web services are only used for exporting transactional data from the Ariba Guided Buying and sending it (via CIG) to the corresponding S/4HANA System.

Scope and Objectives

. The following Receipt web service integration events will be used:

• Export Receipts Asynchronously

There will be no scheduled task of data transmission as data is transferred in real-time.  Each submission of transactional data from Ariba Buying to the S/4HANA System requires a response from the receiving S/4HANA system that the data was successfully received and imported, or details about the error that occurred during the import. The receipts are being exported to S/4HANA with this event and the CIG document type is- ReceiptExportRequest.

• Import Receipts from an External Application Asynchronously

For web services, this success/failure notification is sent in real time as web service response to the original request. With this real time event, the status is sent back to Ariba Buying and the CIG document type for this event is- ReceiptAsyncImportPullRequest.

Service Entry Sheet / Service Sheet (SES)

A service item is an item on an order that represents a service to be performed by a supplier.

Service procurement (or procurement of service items) is a set of features that allows buyers and suppliers to manage orders for service items starting from requisitioning, ordering, tracking, to invoicing in a collaborative way.

SES are documents that describe the goods and services that suppliers deliver to fulfil a service procurement.

SES can be created in the following way:

• Suppliers create SES with reference to a service order on Ariba Network using the SES wizard.

Those SES are then validated and must be approved in Ariba Buying.  When SES is fully approved, the service sheet is transmitted to S/4HANA System 

• Requester can create SES with reference to a service order in Ariba Guided Buying and then the SES is transmitted to S/4HANA System via CIG 

Once SES is created and copied to S/4HANA system, a user with Field Service Administrator group authorization can Force Reject service sheet that is already processed. Once SES is force rejected, status of it is changed to Rejected.

The following SES web service integration events will be used:

• Export Service Sheets Asynchronously

There will be no scheduled task of data transmission as data is transferred in real-time.  The SES are being exported to S/4HANA System with this event and the CIG document type is- ServiceSheetExportRequest.

• Import Service Sheet Approval Statuses

For web services, this success/failure notification is sent in real time as web service response to the original request. With this real time event, the status is sent back to Ariba Guided Buying and the CIG document type for this event is- ServiceSheetAsyncResponsePullRequest.

• Import Service Sheet Status Response Asynchronously

Use the Import Service Sheet Status Response Asynchronously web service to receive service sheet status response asynchronously from external systems to SAP Ariba solutions.

• Export Service Sheet Status Asynchronously

Use the Export Service Sheet Status Asynchronously web service to send service sheet status asynchronously from SAP Ariba solutions to external systems

• Import Service Sheet Response Asynchronously

Use the Import Service Sheet Response Asynchronously web service to asynchronously receive the response about the creation of the service sheet.

• Export Service Sheet Response to External System Asynchronously

Exports service sheet creation information and response asynchronously to an external application.

Process Flow Diagram

Assumptions

Dependencies

Security, Integrity and Controls

Configuration Requirements

Special Requirements

Design Rationale

Data Structure

Source Structure

The following fields will be used to provide the required information for this interface:

Target Structure

The following fields will be used to provide the required information for this interface:

Mapping and Calculation

Processing Logic

Processing within Source

Processing within Middleware

Processing within Target

Interface Dependency

Interface Constraints

Delivery Requirements

Delta or Full Load Requirements

Interface Alert & Monitoring

Interface Reporting

Language Requirements

User Interface Requirements

Volumetrics

Performance Consideration

Error Handling

Testing

How to Test

Test Conditions and Expected Results

Test Considerations/Dependencies

Other Information

Development Details

Package

Other Development Objects

Appendix

See also

Change log

Workflow history