Integration ID: Fit-to-Standard Workshop Business Area
Integration ID: Fit-to-Standard Workshop Business Area
Example
Example 1 yes HR
Yes Logistics
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 hich level the integration
the busines sprocess available? containing the business object used. This
See task: Complete Process information is needed to find the right
models interfaces in the following steps
2EL
Role: Technical Consultant
Business Contact Technical Best
Contact Practice
Setup
done by
The business information is handed over Name the customer?
If SAP is
to an integration specialist/expert. Name implemen Yes or No
providing
the implementation team member that tation an
can be contacted for more details if team integrated
needed. member solution,
that can then mark
be this as No
contacted Yes
for more means
details if that the
needed. implemen
tation
team has
Sally to the
Jo Miller Winter necessary
Yes
steps for
the
Frank integratio
Anette Bauer Hoffmann n.Yes
Alexander
Ralph Schultz Jones No
No
nical Consultant
Custom Driven Setup instruction available?
no n/a
yes
no n/a
Yes n/a
Test Script available? System 1 System2 Integration
definition
complete and
added to
Track the status on the creation Add the involved systems (add Add the Backlog?
All integrations
of the setup guide. more columns if needed) involved that are
systems (add reviewed, have
more a setup guide
columns if and a process
needed) model and a
test script, can
be added into
the backlog for
the realize
phase.
n/a
Optional: scoping decision
Example 1 Example 1
Example 2 Example 2
Example 3 Example 3
Example 4 Example 4
Example 5 Example 5
Example 6 Example 6
Example 7 Example 7
Example 8 Example 8
Example 9 Example 9
Example 10 Example 10
Example 11 Example 11
Example 12 Example 12
Integration Scenario and API
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
Receive/Acknowledge/Change/Cancel customer Sales Order via EDI B/2BNOW S/4HC
Send Advance Shipping Notification (ASN) to customer via EDI S/4HC B/2BNOW
Send Invoice to customer via EDI S/4HC B/2BNOW
Send/Acknowledge/Change/Cancel customer Purchase Order via EDI S/4HC B/2BNOW
Receive Advance Shipping Notification (ASN) from Supplier via EDI B/2BNOW S/4HC
Receive Invoice from Supplier via EDI B/2BNOW S/4HC
Direction from S/4HC Technical Owner Fuctional 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=OVERVI
https://api.sap.com/api/API_OUTBOUND_DELIVERY_SRV
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_INVOICE_REQUEST_OUT?section=OVERVI
https://api.sap.com/shell/discover/contentpackage/SAPS4HANACloud/api/CO_EDI_ORDER_REQUEST_OUT
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
X.509
X.509
X.509
Basic
Basic
Basic
Third Party Data Required (Ariba/
Inbound Services Communication Authentication (X.509
Success Factors/ Hybris / Sales
/ Basic/ OAuth 2.0)
Force /None)
Basic Sales Force
X.509 None
Basic None
Basic None
X.509 None
Basic None
X.509 None
X.509 None
X.509 None
Basic None
Basic 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
AS2 N N/A Y
AS2 N N/A Y
AS2 N N/A Y
SFTP N N/A Y
SFTP N N/A Y
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