| Status | |
|---|---|
| Owner | The person responsible for driving this decision and documenting it. Type @ to mention people by name |
| Stakeholders | The business stakeholders involved in making, reviewing, and endorsing this decision. Type @ to mention people by name |
| Jira Request ID | |
| Jira Development ID |
High- Level Specification
| Implementing System | S/4 Hana |
|---|---|
| Invoked by/Invokes | |
| Business Process Reference | 03.04.03.05. Process PO Output |
Functional Overview
Indirect Purchase Order created in S/4 Hana originating in Ariba Guided Buying is send to the Business Network. Ariba Guided Buying originated Purchase Order is identified by the custom document type - ZAR.
Direct Purchase Order created in S/4 is send to the Business Network. Standard Purchase Order is identified by the document type NB.
Supplier receives Purchase Order via Business Network based on his integration setup. For the light integrated suppliers, Purchase Orders are sent via eMail and available in the Business Network Suppliers account. Supplier can access Business Network account once the Trading Relationship is created.
Fully integrated Suppliers integrate Purchase Orders from Business Network to their ERP System.
Interface is triggered via the standard Output Control of the Purchase Order in S/4 Hana. IDOC message is send to CIG where it's translated into cXML message that is send to the Business Network. In the Business Network the PO is routed to the suppliers account in a case the trading relationship is created with the supplier. If the supplier doesn't have the trading relationship created yet, PO is sent to him via email along with the invitation to join Syensqo Business Network.
Scope and Objectives
This document describes S/4 Hana outbound interface for sending Purchase Order information into Business Network and the basic configuration needed in all the components in order for this interface to be operational.
Message is generated real time via the S/4 standard Output Control. Type of the IDOC is ARBCIG_ORDERS.
Process Flow Diagram
| Step | Description | Comment |
|---|---|---|
| 1. | Indirect Purchase Order is created in S/4 Hana from Guided Buying | |
| 2. | Indirect Purchase Order is created with the document type ZAR | |
| 3. | Output control defined for the document type ZAR triggers IDOC generation | |
| 4. | IDOC of type ARBCIG_ORDERS is generated and send over to CIG | |
| 5. | CIG receives the message and applies the standard mapping over the IDOC, generates cXML document | |
| 6. | cXML document is sent to the Business network | |
| 7. | Business network receives the cXML order in the buyers account and routes it to the suppliers account, if account is created - trading relationship is already established with the supplier |
| Step | Description | Comment |
|---|---|---|
| 1. | Direct Purchase Order is created in S/4 Hana from Guided Buying | |
| 2. | Direct Purchase Order is created with the document type NEU | |
| 3. | Output control defined for the document type NEU triggers IDOC generation | |
| 4. | IDOC of type ARBCIG_ORDERS is generated and send over to the CIG | |
| 5. | CIG receives the message and applies the standard mapping over the IDOC, generates cXML document | |
| 6. | cXML document is sent to the Business network | |
| 7. | Business network receives the cXML order in the buyers account and routes it to the suppliers account, if account is created - trading relationship is already established with the supplier |
Assumptions
Describe any assumptions that have been made in the process of completing this design. What functionality is expected of configuration or other developments that pass information to this development and/ or retrieve the information processed by it (performance, triggers, exceptions, etc.)
Dependencies
Indicate any dependencies or constraints that may impact development, in terms of requirements from internal or external applications or teams, limited access to legacy systems, time constraints or data restrictions. Also, please specify schedule dependencies e.g. interface or batch jobs that must run prior to execution.
Security, Integrity and Controls
To detail the security requirements for processing this object, any data integrity issues associated with the object and the teams that will be responsible for processing the object, i.e. authorization/roles required to who can execute the interface, encryption requirement, etc.
Configuration Requirements
Specify the configuration requirements for this object. Like in case of substitution/ routine specify the configuration needed
Special Requirements
Specify any special requirements or considerations that may impact the interface based on specific locations, regulatory compliance or system limitations. Clearly outline requirements e.g. localization rules for countries like China
If the interface interacts with third-party systems such as Icertis, describe any additional integration, security or authentication considerations that must be taken into account.
Design Rationale
This template section may be used to specify the custom API design. The requirement can be for an API provider which means the API will be designed in the system or can be for an API consumer which means that an API will be consumed in the system.
API Use
Populate the type of the API use in this section. Will the API be Consumed or Provided.
Data Structure
The following fields will be used to provide the required data structure of the interface:
| Parent | Field | Description | Mandatory (Y/N) | Data Type |
|---|---|---|---|---|
Calculation and Validation
Populate the table below to list the calculation and validation rules per field. Can be deleted if not needed.
| Parent | Field | Rule Type | Rule Instruction |
|---|---|---|---|
eDocument mapping
Populate the table below to list the mapping for edocument implementations. Can be deleted if not needed.
| General | Syensqo XML (Target) | SAP eDoc Standard Mapping (Source) | Custom Mapping (Source) | ||||||
|---|---|---|---|---|---|---|---|---|---|
| S-NR | Flow (SD/FI/MM/ALL) | Field Details | Condition | Syensqo XML Node | Syensqo XML Field | SAP eDoc Standard Node | SAP eDoc Standard Field | Fixed Value | Custom Logic |
| Conditional / Mandatory | Header / Header Tax / Header Value / Header Extension / Sender / Sender Extension / Receiver / Receiver Extension / Item / Item Tax / Item Value / Item Extension | ||||||||
Processing Logic
Describe the processing requirement in the System
Delta or Full Load Requirements
Please describe change tracking requirements, i.e. transferring only delta, or always full load
Interface Alert & Monitoring
Please describe any alert & monitoring requirement for business users and support organization, i.e. AIF
Language Requirements
Specify multi language requirements
User Interface Requirements
Capture the requirements for the user interface (UI) associated with the interface. It should provide a clear description of how users will interact with the interface and how information will be presented to ensure usability and accuracy.
Sequencing
Please describe delivery requirements driven by message sequencing, i.e. specific order, impact of disruption of sequence, are duplicates allowed, etc.
Volumetrics
Provide volumetrics details: Initial load volumes, Number of Records, Expected Frequency, Expected Long term Growth)
Performance Consideration
Specify if there are any specific performance factors that need to be taken into consideration during development i.e. interface must be able to handle 100 posting per-hour, etc.
Error Handling
Detail how errors will be handled: Notification, Restart/ Recovery and Re-Processing Procedures
Testing
How to Test
Please provide some guidance and/or test data to help the developer unit test the interface. Please include both positive and negative testing (to validate error situations handling)
The developer will need to test repeatedly, so where appropriate provide instructions to reverse the actions performed so the test may be run again, or explain how to create new input data to the test. In particular, the developer will need logons for test users representing the various roles within the approval process.
Test Conditions and Expected Results
| ID | Condition | Expected Results |
|---|---|---|
Test Considerations/Dependencies
List any considerations essential for application test planning (e.g., test this before ABC along with DEF separate from GHI). If the development encompasses a user interface, explain how to test it. List any insights as to how this component could be tested the most efficiently.
Other Information
Development Details
Package
| Package Name | Parent Package |
|---|---|
Other Development Objects
| Object Type | Object Name | Purpose/High Level Logic | Design Rationale Reference |
|---|---|---|---|
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.
