This part I will show that how to configure PI ESR and generate ABAP proxy consumer in ABAP system.
Request data type in ERP side:
Response data type in ERP side:
Request data type in 3rd Party
The JDBC XML format can be found in SAP help in the 5 part Reference
In this scenario I want to use JDBC Adapter to execute a store procedure, so should use the XLM format as below:
Format of EXECUTE Statement
<StatementName>
<storedProcedureName action=" EXECUTE">
<table>realStoredProcedureeName</table>
<param1 [isInput="true"][isOutput=true]type=SQLDatatype>val1</param1>
</storedProcedureName >
</StatementName>
PS: <table> element is optional, I leave out in the data type.
Element name ”SP_GET_SUPERIOR_APPROVER” is the store procedure name.
Reponse data type in the 3rd party side:
PS: The element name “Procedure_response” is required according to element name “Procedure” in request data type;
I don’t find the explain for “reponse_1” and “row” in SAP help, but they could be found in PI message monitor.
Request message type in ERP side:
Reponse message type in ERP side:
Request message type in 3rd party side:
Response message type in 3rd party side:
PS: The response message type name must be “<reqmt>_response”, <reqmt> is the request message type name.
Service interface in ERP side:
Outbound and Synchronous.
Service interface in 3rd party side:
Request message mapping:
From ERP request message type to 3rd request message type
The value for action should be “EXECUTE” for store procedure.
Response message mapping:
Tcode: SM59
The RFC destination name must be: “SAP_PROXY_ESR”
Input the PI server host and port in “Target Host” and “Service No.”, the “Path Prefix” must be “/rep”.
Tcode: SPROXY
Double click the Service Consumers(Service Interface in PI) “SI_A2J”
Activate!
The links of other parts:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
8 | |
5 | |
5 | |
4 | |
4 | |
4 | |
3 | |
3 | |
3 | |
3 |