Proxy Connection Setup
ECC System
1. Create Logical System in BD54 for PO system
2. Create RFC Destination AEX_POD in SM59 of Type G, which will point to the PO system
Target Host :<Host Name of AAE server>
Service No. :< HTTP Port Number of AAE server>
Path : /XISOAPAdapter/MessageServlet?ximessage=true
3. (Optional for multiple AAE as sub parameter of IS_URL)
Define the sender ID in SXMSIF
Party - *
Service - *
Interface Name - Outbound
Interface Namespace - Outbound
3. SXMB_ADM
Integration Engine Configuration
Role of Business System - Application System
Cooresponding Integration Server : dest://RFC
Go to Edit -> Change Configuration
Category - Runtime
Parameter IS_URL
Subparameter =
Value = dest://(RFC Destination which we created in above step)
Manage Queues - Choose “Register Queues”
4. SM59 - RFC Destination SAP_PROXY_ESR in SM59 system of Type G.
Target Host: <Server Name> or <IP address>
Service Number: <Port Number>
Path Prefix: /rep
Logon : Basic Authentication with user role SAP_XI_IS_SERV_USER
5. SLDAPICUST - Transaction and configure entry for PO system in ECC System
Select access via HTTP, enter an Alias, the hostname of the SLD (AEX), port and the user to be used to connect to the SLD
6. SLD Data Supplier
Option 1
Change the entries in SLD > Administration > Details > Profile(Choose ALL)
Go to RZ70,
Gateway Host - <ABAP Host>
Gateway Service - sapgw<InstanceNo> - check in SMGW
Option 2
Check the entries in SLD > Administration > Details > Data Suppliers
Update the same details in RZ70
Gateway Host - <PI Host>
Gateway Service - sapgw<InstanceNo>
In case of issues, try gw/acl_mode =0 parameter in PI/PO SCS profile and restart system
Verify all with SLDCHECK tcode.
How to Set Up the Communication between ABAP Backend and SOAP adapter
Overview: Configuration-Guide for ABAP backend
Queue Monitoring
Queue - SMQ2
QName - XBTS**** - Outbound Message
QName - XBTR**** - Inbound Message
queues-issues-in-sap-pi-and-ecc
Function Module to trigger alert from ABAP: SALRT_CREATE_API
Schedule job to restart messages in error: rsxmb_restart_messages
I have 2 options for the file to proxy async scenario if the message goes in error in ECC -
1. Send an email in the proxy code and generate a message in application log (tcode SLG1) or Z table
2. Use the FEH (forward error handling technique)
http://scn.sap.com/people/michal.krawczyk2/blog/2011/02/24/pixi-forward-error-handling-feh-for-asynchronous-proxy-calls-with-the-use-of-error-and-conflict-handler-ech
FEH is for forwarding the msgs to Post Processing Office tool, which has the options of repeat, confirm and discard for an error msg. it replaces standard fault msgs by using ECH framework for exception handling. Fault message structure purpose is to handle only application error messages. This will not solve your requirement. Alternatively, change the ABAP proxy to handle the error and return a clean status. Exception handling (try/catch) should be used were ever dangerous code is being used.
Forward Error handler is a technology available in the ABAP Runtime, based on SAP's ECH ( Error and Conflict Handler Framework). This leverages the SAP Post processing office. It has support only for Asynchronous messages with an integration pattern involving inbound ABAP Proxies. Error monitoring and display is done within the post processing office ( transactions /SAPPO/PPO2 and /SAPPO/PPO).
Blogs
POV - FEH or AIF or Custom Error Handling
How To Setup Forward Error Handling in PI Scenarios
FEH for asynchronous proxy calls with the use of ECH
Forward Error Handling – A short look at SAP Business Suite Ehp 4