SAP PI / SAP PO: Interface Development with Standard Adapter
- Descrição
- Currículo
- FAQ
- Revisões
This is one of the detailed course that is designed to cover all the aspects of Interface Development with SAP PI / SAP PO tool that can help you learn a skill and build your career in Integration space.
What SAP PI / SAP PO Adapters are covered?
You will learn Interface Development for following Adapters:
-
IDOC_AAE
-
RFC
-
FILE
-
FTP
-
REST
-
JDBC
-
HTTP_AAE
-
SOAP (WEBSERVICE)
-
MAIL
What Interface Scenarios are covered?
This course covers the following Interface Scenarios:
-
File with File Content Conversion
-
File with Availability Time Planning (ATP)
-
File Adapter Scheduling
-
JDBC to JDBC Scenario
-
Synchronous Interface with HTTP_AAE Adapter
-
Webservices with SOAP (Publish in Service Registry, Generate WSDL)
-
Token Authentication with REST
-
ECC to PO Connection
-
Order Scenario with IDOC
-
Lookup with RFC
-
Send email with Mail Adapter
What will your learn in this course?
This course will prepare you to:
-
Build End to End Interface with SAP PO / SAP PI Process Integration Tool.
-
How to do Client Transport from ESR and ID.
-
Learn How to use the Standard Adapter and Build Interface.
-
How to Monitor your Interface via PIMON tool.
-
How to Test your Interface with tools like RWB, SOAPUI and PostMan
-
Build Interface with Configuration Scenarios.
What Topics are covered in this Course?
-
End to End Development of Interface.
-
Integration Scenarios.
-
Standard Adapter Configuration.
-
Mapping Techniques with RFC Lookup.
-
Testing of the Interface with RWB, SOAPUI and Postman
-
Monitoring of Interface with PIMon.
Course based on:
-
SAP PO 7.5
Downloads:
-
Download Interface Code (TPZ)
-
Source Code
-
Supported Structures of XSD
All the hands-on training is shown on the Live PO 7.5 system so that you can do it yourself later.
-
5
Check the SAP PO AEX Software Version -
6
Understand the Difference between JRE and JDK
-
7
Download and Configure Java on your Local Machine
-
8
Download and Configure NWDS
-
9
Configure NWDS with SAP PO System
-
10
Understanding NWDS Environment
-
11
Checklist to Verify the Required Software and Tools
-
12
Resources and Links
-
13
Understanding Manufacturing Company Landscape
-
14
Integration Scenarios with Company SAP PO Integration Tool
-
15
Integration Scenarios with Company SAP ECC ERP System
-
16
Integration Scenario with Company ShopFloor System
-
17
Integration Scenarios with Company HR System
-
18
Integration Scenarios between Company and its Customer
-
19
Integration Scenarios between Company and its Supplier
-
20
Integration Scenario Summary
-
21
Business Requirement for File to File Interface
-
22
File to File Interface Requirement
-
23
Configuring the systems in SLD
SLD Object Name:
PRODUCT: TECHIEPRESS
SWCV: TECHIEPRESS 1.0
TECHNICAL SYSTEM: TS_ECC_800_TP_GLOBAL - 3rd Party
BUSINESS SYSTEM: ERP_ECC_800_TP_GLOBAL - 3rd Party
-
24
Designing the File to File Interface
-
25
Sample Data for the Interface
-
26
Developing the ESR Objects
Here are the objects that need to be created in ESR:
SWCV: TECHIEPRESS
Namespace: http://techiepress.com/F2F/SupplierPayments
Source Interface: SI_OUT_ASYNC_SP_F2F_SOURCE
Source Message Type: MT_F2F_SOURCE
Source Data Type: DT_F2F_SOURCE
Target Interface: SI_IN_ASYNC_SP_F2F_TARGET
Target Message Type: MT_F2F_TARGET
Target Data Type: DT_F2F_TARGET
Operation Mapping: OM_SP_FTP_LOCAL_to_CITIBANK_FTP
Message Mapping: MM_SP_FTP_LOCAL_to_CITIBANK_FTP
Source:
Records
row
ID
CODE
FIRSTNAME
LASTNAME
AMOUNT
REMARKS
Target:
Records
row
ID
CODE
NAME
REFERENCE
AMOUNT
DATE
REMARKS
UDF: getMessageID
String MessageID;
java.util.Map param = container.getTransformationParameters();
MessageID = (String) param.get (StreamTransformationConstants.MESSAGE_ID);
return MessageID;
-
27
Developing the ID Objects
Folder: F2F_SUPPLIER_PAYMENTS
Configuration Scenario: CS_F2F_SUPPLIER_PAYMENTS
Source Business System: ERP_ECC_800_TP_GLOBAL
Target Party: PY_BANK_CITIBANK_GLOBAL
Target System: CO_BANK_CITIBANK_GLOBAL
Source Channel: CC_FILE_TECHIEPRESS_SENDER
Target Channel: CC_FILE_CITIBANK_RECEIVER
OM_SP_FTP_LOCAL_to_CITIBANK_FTP
-
28
Configure Channels with FTP Folders
-
29
File Content Conversion Configuration
-
30
Testing the File Interface
-
31
File Content Conversion Documentation
-
32
Interface Assumptions
-
33
Bonus: Scheduling and ATP Channel Configuration
-
34
Transport Objects from ESR and ID
-
35
Download the Interface Objects
-
36
Scenario 1: Build a Interface with File Adapter using NFS
-
37
Scenario 2: Build a Interface without File Content Conversion
-
38
Scenario 3: Performing the following Test cases for the Interface
-
39
Scenario 4: Change the Scheduling as per the requirement
-
40
Topics covered so far
-
41
Integration Requirement for JDBC to JDBC Scenario
-
42
Understanding the JDBC Adapter
-
43
Download the Sample Data
-
44
Build the Tables in Oracle DB
-
45
Developing SLD Objects
PRODUCT: TECHIEPRESS
SWCV: TECHIEPRESS 1.0
TECHNICAL SYSTEM: TS_SHOPFLOOR_TP_GLOBAL - 3rd Party
BUSINESS COMPONENT: BS_SHOPFLOOR_TP_GLOBAL - 3rd Party
TECHNICAL SYSTEM: TS_ADP_TP_GLOBAL - 3rd Party
BUSINESS COMPONENT: BS_ADP_TP_GLOBAL - 3rd Party
-
46
Developing ESR Objects
SWCV: TECHIEPRESS
Namespace: http://techiepress.com/J2J/WorkersUpdate
Data Type:
DT_J2J_SOURCE
DT_J2J_TARGET
Message Type:
MT_J2J_SOURCE
MT_J2J_TARGET
Interface:
SI_OUT_ASYNC_WU_J2J_SOURCE
SI_IN_ASYNC_WU_J2J_TARGET
Message Mapping:
MM_WU_JDBC_SHOPFLOOR_to_ADP_JDBC
Operation Mapping:
OM_WU_JDBC_SHOPFLOOR_to_ADP_JDBC
-
47
Developing ID Objects and Testing the Interface
Scenario: CS_J2J_WORKERS_UPDATE
Folder: J2J_WORKERS_UPDATE
Source Business System: BS_SHOPFLOOR_TP_GLOBAL
Target Business System: BS_ADP_TP_GLOBAL
Sender Communication Channel: CC_JDBC_WU_TP_SENDER
Receiver Communication Channel: CC_JDBC_WU_TP_RECEIVER
Interface:
SI_OUT_ASYNC_WU_J2J_SOURCE
SI_IN_ASYNC_WU_J2J_TARGET
Operation Mapping:
OM_WU_JDBC_SHOPFLOOR_to_ADP_JDBC
-
48
Download the Interface Objects
-
49
Scenario 1: Build Interface to pull the records from Database and save in File
-
50
Scenario 2: Pick file and Update in the Database
-
51
Scenario 3: Delete records from Database after it is picked up
-
52
Resources and Links
-
53
Integration Requirement for SOAP to SOAP Scenario
-
54
Understanding the SOAP Adapter
-
55
Build Webservice using Eclipse
https://www.eclipse.org/downloads/packages/release/2018-12/r/eclipse-ide-java-developers
-
56
Test Webservice with SOAPUI Tool
https://www.soapui.org/
-
57
Test Webservice from WSNavigator
http://<host>:<port>/wsnavigator
-
58
Develop SLD Objects
-
59
Develop ESR Objects
TECHIEPRESS
http://techiepress.com/S2S/GetSerialNumber
DT_S2S_REQUEST_SOURCE
DT_S2S_RESPONSE_SOURCE
MT_S2S_REQUEST_SOURCE
MT_S2S_RESPONSE_SOURCE
WSDL External Definition
SI_OUT_SYNC_SERIAL_S2S_SOURCE
SI_IN_SYNC_SERIAL_S2S_TARGET
MM_SERIAL_REQUEST_SOAP_SHOPFLOOR_to_APPLE_SOAP
MM_SERIAL_RESPONSE_SOAP_SHOPFLOOR_to_APPLE_SOAP
OM_SERIAL_SOAP_SHOPFLOOR_to_APPLE_SOAP
-
60
Develop ID Objects
CS_S2S_GET_SERIAL_NUMBER
S2S_GET_SERIAL_NUMBER
BS_SHOPFLOOR_TP_GLOBAL
PY_CUST_APPLE_GLOBAL
BS_CUST_APPLE_GLOBAL
CC_SOAP_SERIAL_TP_SENDER
CC_SOAP_SERIAL_APPLE_RECEIVER
TECHIEPRESS
http://techiepress.com/S2S/GetSerialNumber
-
61
Extract WSDL of the PO Interface
-
62
Testing the Interface with SOAPUI
-
63
Download the Interface Objects
-
64
Download the WebService Eclipse Code
-
65
Scenario 1: Build and Register Service in Service Registry
-
66
Scenario 2: Export WSDL for your Interface
-
67
Scenario 3: Use SOAPUI to call the Interface via the WSDL.
-
68
Integration Requirement for HTTP to HTTP Scenario
-
69
Understanding the HTTP_AAE Adapter
-
70
Build the HTTP Program using Eclipse
-
71
SLD Objects
-
72
Develop HTTP Interface
CS_H2H_GET_SERIAL_NUMBER
H2H_GET_SERIAL_NUMBER
BS_SHOPFLOOR_TP_GLOBAL
PY_CUST_APPLE_GLOBAL
BS_CUST_APPLE_GLOBAL
SI_OUT_SYNC_SERIAL_H2H_SOURCE
SI_IN_SYNC_SERIAL_H2H_TARGET
http://techiepress.com/H2H/GetSerialNumber
CC_HTTP_GET_SERIAL_SF_TP_SENDER
CC_HTTP_GET_SERIAL_APPLE_RECEIVER
-
73
Testing the HTTP Interface with PostMan Tool
-
74
Download the Interface Objects
-
75
Download the Jersey API Eclipse Code
-
76
Scenario 1: Create a HTTP to FILE Interface. Dump the request file in the FTP.
-
77
Scenario 2: Use POSTMAN tool to send message to your HTTP Interface
-
78
Scenario 3: Fetch www.yahoo.com page from SAP PO system.
-
79
Overview of REST Interface
-
80
Understanding the REST Sender Adapter
-
81
Understanding the REST Receiver Adapter
-
82
REST Sender Adapter Interface Design Walkthru
-
83
REST Sender to FTP Interface
-
84
REST Receiver Adapter Interface Design Walkthru
-
85
HTTP to REST Receiver Interface
-
86
Scenario 1: Build your own REST to File Interface.
-
87
Scenario 2: Call the REST Interface from Postman tool.
-
88
Scenario 3: Call the REST Interface from SOAPUI Tool
-
89
Get the SAP ECC System Details
LOGICAL SYSTEM: SE37 / OWN_LOGICAL_SYSTEM_GET /
RFC DESTINATION: SM59
PROGRAM ID: SM51 / <PROGRAM ID>
PORT: WE21 /
PARTNER PROFILE: WE20 /
------------------
Find out the details for your System:
HOST NAME:
CLIENT:
PROGRAM ID:
LOGICAL SYSTEM:
MESSAGE SERVER PORT:
INSTANCE NUMBER / SYSTEM NUMBER:
DISPATCHER PORT:
-
90
Scenario 1: Connect your SAP PO with ECC
