0% found this document useful (0 votes)
441 views60 pages

S4H - 471 Integration Scenario List

This document provides a template for collecting integration requirements and scenarios. It includes instructions for completing the template which are published in the SAP Activate Methodology. The template collects information like integration IDs, involved systems, business areas, and status of setup guides, test scripts, and integration definitions. This information is used to define integration flows in SAP Business Technology Platform and track integration requirements through realization.

Uploaded by

Rafael Silva
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLSX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
441 views60 pages

S4H - 471 Integration Scenario List

This document provides a template for collecting integration requirements and scenarios. It includes instructions for completing the template which are published in the SAP Activate Methodology. The template collects information like integration IDs, involved systems, business areas, and status of setup guides, test scripts, and integration definitions. This information is used to define integration flows in SAP Business Technology Platform and track integration requirements through realization.

Uploaded by

Rafael Silva
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLSX, PDF, TXT or read online on Scribd

Integration Scenario and API Lis

Release date : Q3/ 2019

Purpose: The purpose of this template is to collect all integration requirements during the scoping and prepare the realize pha
This information is used in a followup task to define SAP Business Technology Platform iFlows.
Requirements on the tab Integration scenarios are usually collected during the fit-to-Standard Analysis or in scoping activities
validated for feasability and not checked for duplicates. It is important to review the findings as a whole before entering the it

Instructions for completing the list are published in the SAP Activate Methodology for S/4HANA cloud.
[Link]

Link to document:

This document and its instructions are updated regularly. Before use check for updates in the SAP Roadmap Viewer
[Link]
Role: Business Consultant
Integration ID Fit-to-Standard Workshop Business Area

Unique ID to track Was this integration discussed in a Name the business


details and Fit-to-Standard workshop? area where the
decisions integration is used

Example

Example 1 yes HR

Example 2 yes Logistics

Example 3 yes Finance

Yes Logistics
Integration Scenario and API List
Business Information and Tracking

Scope Item (Business Process) ID Scope Item (Business Process) Title

Integrations are used in business processes, name the Title of the scope item of column F
Scope items for the business process.

J12 Time Recording - Project-Based Services

J45 Procurement of Direct Materials

J59 Accounts Receivable

J13 Advanced Shipping Notice


Scope Item (Integration Setup) ID Scope Item (Integration Setup) Title

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

Employee Integration - Employee Central


JB1 Integration

not available not available

1MV Machine learning: Cash Application

Jb7 856 Advanced Shipping Notice


Process Flow Available? Details

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

Person hired in EC, records time in


yes S/4CLD

no Import POs from 3rd Party system

Manifest, bill of lading involved in a


no
shipment
EDI EDI Integration

Does the customer currently use EDI or


Which scope item would be applicable to
will they have a need for EDI EDI Integration
Yes/No

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 implement Yes or No
providing
the implementation team member that ation team an
can be contacted for more details if member integrated
needed. that can solution,
be then mark
contacted this as No
for more Yes
details if means
needed. that the
implement
ation team
has to the
Sally necessary
Jo Miller Winter steps
Yes for
the
integratio
Frank n.
Anette Bauer Hoffmann Yes
Alexander
Ralph Schultz Jones No

No
nical Consultant
Custom Driven Setup instruction available?

Is the integration designed by the customer? Track the status on the


Yes: a setup guide and a test script needs to be written creation of the setup guides.
by the customer. See task Complete Setup Guides
No: A setup guide is provided by SAP and can be
downloaded from SAP Best Practice Explorer:
[Link]

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 S/4CLD EC Yes

3rd party S/4CLD


SAP Cloud
n/a S/4CLD Platform n/a

n/a
Optional: scoping decision

Is the integration 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
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

Interface Name Business Area

Sales Order Creation Sales


Sourcing and Procurement with Suppliers Integration Procurement
Post Bank Statements Finance
Billing Document Sales
Customer Invoice Procurement
EDI - 940 - Integration Warehouse Management
EDI - 850/855/860 - Orders Integration Sales
EDI - 856 ASN Integration Sales
EDI - 810 - Invoice Integration Sales
EDI - 850/855/860 - Integration Procurement
EDI - 856 - ASN Integration Procurement
EDI - 810 - Invoice Integration Procurement
tion Scenario and API List

Functional Desc Source System Target System

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

Inbound SPS Peter Miller Realtime


Inbound Supplier Peter Miller Scheduled
Inbound PNC Sarah Jones Realtime
Inbound Sales Peter Miller Realtime
Outbound SAP Frank Huber Scheduled
Outbound SPS Peter Miller Scheduled
Inbound B/2BNOW Scheduled
Outbound B/2BNOW Scheduled
Outbound B/2BNOW Scheduled
Outbound B/2BNOW Scheduled
Inbound B/2BNOW Scheduled
Inbound B/2BNOW Scheduled
API Available (Y/N) S4 HANA Cloud API Name

Y Sales Order - Create, Update, Cancel and Delete


Y Purchase Order - Send, Update, Cancel
Y Bank Statement - Post
Y Billing Document - Create
Y Customer Invoice - Send
Y Create, Read, Update, Delete Outbound Delivery
Y Sales Order - Create, Update, Cancel and Delete
Y
Y Customer Invoice - Send
Y Purchase Order - Send, Update, Cancel
Y
Y
API URL

[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]

[Link]
[Link]
Communication
Interface Subtype Common Communication User
Scenario

OData SAP_COM_0109 SPS_SALES_USER


SOAP SAP_COM_0224 SUPPLIER_PO_USER
OData SAP_COM_0316 PNC_BANK_USER
SOAP SAP_COM_0120 BILLING_USER
SOAP SAP_COM_0223 CUST_INVOICE_USER
SOAP SAP_COM_0008 S4HC_USER
SOAP
SOAP
SOAP
SOAP
SOAP
SOAP
iFlow Required
Scope Items Series C
(Y/N)

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

*All items will be maintained in inventory prior to sales order creation.


*Purchase Order data sent from S/4HC will use Outbound Services provided in Comm. Arrangement.
*Bank statements provided by PNC will not require any custom fields.
*Client will need to determine what fields will be required.
*If multiple sources required, will they also be realtime or scheduled?
*Will SPS send a delivery notification after outbound delivery sent?
SAP Project Team Comments

*Additional configuration required for Sales Force integration.


*In this scenario, we will need to upload certifcate to CPI for user authenticaiton.
*SOAP payload provided by PNC will post to S/4HC. S/4HC will return bank statement number to PNC as confirmation.
*We will need to define frequency of inbound billing documents from external systsem.
*Work with client to determine requirements for frequncy and duration.
*Inbound notifications will use inbound services within Communication Arrangement.
Column33 Column34 Column35 Column36 Column37 Column38
Column39 Column40 Column41 Column42 Column43 Column44
Column45 Column46 Column47 Column48 Column49 Column50
Column51 Column52 Column53 Column54 Column55 Column56
Column57 Column58 Column59
Scenario ID Interface ID

Use Scenario
ID from
Integration
Scenario
Sheet
Integrations using SAP Cloud
Technical Details

Interface Name Third-party system Version

Name the Third-party Verson of third-party


system (see also Sheet: system
Integration Scenario)
SAP Cloud Platform Open Connectors

Source system/ Target


Connector available (yes/no)
system (S/T)

S: Source Check the list of available connectors if Opne


or Conector Builder is needed.
TTarget [Link]
m/home/full-list
rs

Link to connector Link to Process Model

e.g. [Link] Review requirement


provider-setup description from Fit-
to-Standard, and
detail if necessary
Integration Trigger
Data Object Timed
Requirement (Event/Timed)

Link additional e.g. Material Master Is the integration If the


documents from scheduled or event integration s
Requirement that triggerd timed, what is
describe the needed the fre
integration add more
columns if needed
Expected Volume related integrations Proof of Concept

e.g. 1000 orders per day List related Was a proof of concept delivered during he
integrations from sales/evaluation cycle? (yes/No)
Tab API list
Expected Go-Live for
Column33 Column34 Column35 Column36
integrated scneario

Expected go live
Column37 Column38 Column39 Column40 Column41 Column42
Column43 Column44 Column45 Column46 Column47 Column48
Column49 Column50 Column51 Column52 Column53 Column54
Column55 Column56 Column57 Column58 Column59
Integration using EDI
Technical Details

Integrated or Depenant Mapping


ID EDI Business Process Systems Specs
Any system that requires information
Name of the business process: to be completed or validated to Yes or No: If
Ex. Inbound Invoicing complete a transaction 'Yes' Attach

Ex. 1 Inbound Purchase Order Integrated with B/2BNOW Yes

Ex. 2 Inbound Purchase Order Integrated with CPI Yes


Managed File EDI
Trf Protocol Transaction
Ex: 810 Invoice Transaction
Resources Systems (MFT) Inbound/Outboun
Type Volume
d or 850
Purchase Order
Ex: S/4HANA Cloud or Inbound/Outboun Each communication
Ex: In-House or 3rd Party Database(Oracle/DB2) Ex: AS2 or sFTP d counts as a transaction

B/2BNOW = 3rd Party S/4HANA SFTP 850 300 per month

In House S/4HANA SFTP 850 300 per month


Error Code/ Description Error Handling

Ex: 2 - Syntax version not supported


or 12 - Invalid Value

B/2BNOW reaches out to Walmart to


Customer sends over a purchase
order with inaccurate part numbers identify the correct part numbers and
resends over the purchase order

Inhouse team would trouble to


S/4HANA DB is not responding identify the point failure in the
connection

You might also like