Académique Documents
Professionnel Documents
Culture Documents
Purpose: The purpose of this template is to collect all integration requirements during the scoping and prepare the realize pha
integration.
Business consultants can enter the requirements on Level 0 making sure that every integration has a scope item for the busine
that business settings can be aligned.
Integration Experts collect all requirements into one list and start collecting all needed information for the setup (Level L1). Exa
grouped in series to structure the research by tool or logical unit. Adjust the template to your project, add and remove column
needed in your implementation project.
Once completed the reviewed and approved integration scenarios are transferred to the Backlog to be realized in the next pha
Instructions for completing the list are published in the SAP Activate Methodology for S/4HANA cloud.
https://roadmapviewer-supportportal.dispatcher.hana.ondemand.com/#/group/BE47098A-617A-43EF-A27E-DFD801D70483/r
Link to document:
This document and its instructions are updated regularly. Before use check for updates in the SAP Roadmap Viewer
https://support.sap.com/content/dam/SAAP/SAP_Activate/S4H_471%20Integration%20Scenario%20List.xlsx
Role: Business Consultant
Integration ID Fit-to-Standard Workshop Business Area
Example
Example 1 yes HR
Example 2 yes Logistics
Example 3 yes Finance
Integration Scenario and API List
Business Information and Tracking
Integrations are used in business processes, name the Title of the scope item of column F
Scope items for the business process.
Various integrations are delivered from SAP Title of the scope item of column H
as out of the box integration scope items.
They are found in the Best Practice
Explorer under Integration
Is a End to End process flow for Describe the high level integration
the business process available? containing the business object used. This
See task: Complete Process information is needed to find the right
models interfaces in the following steps
The business information is handed over Name the implementation team member that can be
to an integration specialist/expert. Name contacted for more details if needed.
the implementation team member that
can be contacted for more details if
needed.
If SAP is providing an Is the integration designed by the Track the status on the creation Track the
integrated solution, then customer? of the setup guides. status on the
mark this as No Yes: a setup guide and a test creation of
Yes means that the script needs to be written by the the setup
implementation team has to customer. See task Complete guide.
the necessary steps for the Setup Guides
integration. No: A setup guide is provided by
SAP and can be downloaded
from SAP Best Practice Explorer:
https://rapid.sap.com/bp/
Add the Add the involved systems (add more columns if All integrations that are
involved needed) reviewed, have a setup guide
systems (add and a process model and a test
more columns script, can be added into the
if needed) backlog for the realize phase.
S/4CLD EC Yes
3rd party S/4CLD
S/4CLD SAP Cloud Platform n/a
Optional:
scoping
decision
Is the
integratio
n after
detail
review
descoped?
Scenario ID Interface ID Series A
Example 1 Example 1
Example 2 Example 2
Example 3 Example 3
Example 4 Example 4
Example 5 Example 5
Example 6 Example 6
Integration Scenario and API L
Technical Details
Automatically Create / Update / Read and Delete Sales Orders in S4HC SPS S/4HC
Suppliers send Purchase Order Confirmation back to S4HC Supplier S/4HC
Create Bank Statements in S4HC PNC S/4HC
External systems can create billing document in S4HC Sales S/4HC
Send Customer Invoice to Customer Systems S/4HC Customer
Delivery Confirmation S/4HC SPS
Direction from S/4HC Technical Owner Functional Owner Frequency Series B
https://api.sap.com/shell/discover/contentpackage/SAPS4HANACloud/api/API_SALES_ORDER_SRV?section=RESOURCE
https://api.sap.com/shell/discover/contentpackage/SAPS4HANACloud/api/CO_EDI_ORDER_REQUEST_OUT
https://api.sap.com/shell/discover/contentpackage/SAPS4HANACloud/api/BANKSTATEMENTPOST_IN
https://api.sap.com/shell/discover/contentpackage/SAPS4HANACloud/api/BILLINGDOCUMENTREQUEST_IN
https://api.sap.com/shell/discover/contentpackage/SAPS4HANACloud/api/CO_EDI_INVOICE_REQUEST_OUT?section=OVERVIE
https://api.sap.com/api/API_OUTBOUND_DELIVERY_SRV
Communication
Interface Subtype Common Communication User
Scenario
1QI / BD9 Y
2EJ Y
J59 N
1Z6/ 19M Y
2EL N
1ZQ N
Outbound Services Communication Authentication (X.509
/ Basic/ OAuth 2.0/None)
Basic
Basic
Basic
Basic
X.509
X.509
Third Party Data Required (Ariba/
Inbound Services Communication Authentication Success Factors/ Hybris / Sales
(X.509 / Basic/ OAuth 2.0) Force /None)
Basic Sales Force
X.509 None
Basic None
Basic None
X.509 None
Basic None
Target System Deployment (Cloud/On Custom Fields Required Go Live
Series D Gaps (Y/N)
Premise/SAP System/SFTP) (Y/N) Critical (Y/N)
SFTP N N/A N
On Premise (In House System) N N/A Y
On Premise (In House System) N N/A Y
Cloud Y N/A Y
SFTP N N/A N
SFTP N N/A Y
Client Comments
*We will require business partner data and sales order data from Sales Force.
*Outbound Texts for Integration with the supplier will be defined prior to configuration.
*Bank Statement Number required by client.
*Custom fields required on Billing Document
*Can we send invoice to multiple sources?
*Frequency needs to be on a nightly basis
Questions/Assumptions