ABAP Proxy Receiver Asynchronous EOIO

Hi,
Is it possible to Guaranteeing the Sequence of Asynchronous Messages for ABAP Proxy Receiver(EOIO)?
If yes, how can I configure?
Thanks,
Kiara.

Hi Stefan,
Thank you.
One quick question.
In case if I use JMS>PI>RFC(Async) then also no need of maintaining EOIO for RFC Receiver Async?
On JMS sender we are maintaining EOIO.
Reason for this request is currently we are using JMS>PI>RFC Async. We are using EOIO on JMS sender, but some times sequence of messages is missing.
Can you please let us know the cause of this issue.
Thanks,
Kiara.

Similar Messages

Mail Sender to Abap Proxy Receiver with Attachements

Hi All,
Scenario: I need to create a ticket in Solman from a mail. I intend to do the scenario as Mail sender to Abap Proxy receiver asynchronous.
I have configured my sender mail adapter and am able to get the mails in XI. The attachements also appear in Inbound payload as MailAttachement-1, MailAttachement-2 etc. I have checked use mail packege and keep attachements in sender adapter.
Transport Protocol: IMAP4
Message Protocol: XIPAYLOAD
Queries:
1. My Inbound Data Type is the mail Package -- ximail30_xsd. Here in sxmb_moni I can see the mail attributes like from, to and the mail body in content. But How can I read the attachements in my message mapping.
2. How can I pass these attachements to Abap Proxy ( I do not need to alter attachments only pass to proxy ). These attachements have to be attached to the Solman ticket in SOLMAN server.
Appreciate your kind response to my above queries.
Thanks.
Regards,
Siddhesh S.Tawate
PS: I have tried using PayloadSwapBean in adapter module but still the content at source remains same.

Hi,
Please find below the part of code that might help you. I have given code only responsible for attachements part of the ticket.
loop at lt_attach into l_attachment.
        count = count + 1.
        if count = 1.
          first_line = 1.
        endif.
        l_type = l_attachment->GET_CONTENT_TYPE( ).
        split l_type at '"' into l_type
                                 file_name
                                 l_name.
        l_name = file_name.
        split file_name at '.' into file_name
                                    file_type.
        l_xstring = l_attachment->GET_BINARY_DATA( ).
        strlen = xstrlen( l_xstring ).
        Compute int = ( strlen div 255 ).
        Compute rem = ( strlen mod 255 ).
        if rem <> 0.
          int = int + 1.
        endif.
        count1 = int.
        if count = 1.
          last_line = count1.
        else.
          if int = 1.
            first_line = last_line.
          else.
            last_line = first_line + count1.
          endif.
        endif.
        wa_APPX_HEADERS-APPXNO = count.
        wa_APPX_HEADERS-DESCR = l_name.
        wa_APPX_HEADERS-FILETYP = file_type.
        wa_APPX_HEADERS-FILENAM = l_name.
        wa_APPX_HEADERS-FILEFM_UL = 'BIN'.
        wa_APPX_HEADERS-FIRSTL = first_line.
        wa_APPX_HEADERS-LASTL = last_line.
        wa_APPX_HEADERS-FILELEN = strlen.
        wa_APPX_HEADERS-LAST_USR = sy-uname.
        GET TIME STAMP FIELD wa_appx_headers-TIMESTAMP.
        append wa_APPX_HEADERS to it_APPX_HEADERS.
        while count1 <> 0.
          count1 = count1 - 1.
          if count1 <> 0.
            wa_APPX_LINES_bin-LINE = l_xstring+0(255).
            shift l_xstring left by 255 places in BYTE MODE.
          ELSE.
            wa_APPX_LINES_bin-LINE = l_xstring.
          endif.
          append wa_APPX_LINES_bin to it_APPX_LINES_bin.
          clear: wa_APPX_LINES_bin, wa_APPX_LINES.
        endwhile.
        first_line = last_line + 1.
        clear: strlen, count1, file_name, file_type, l_type, int, rem, l_xstring, l_attachment.
      endloop.
CALL FUNCTION 'BAPI_NOTIFICATION_CREATE'
        EXPORTING
          NOTIF_EXT                = wa_NOTIF_EXT
        NOTIF_CRM                = wa_NOTIF_CRM
IBASE_DATA               =
     IMPORTING
       NUMBER                   = Refnum
       NUMB                     = Numb
       REFNUM                   = Ticket_No
       SYSID                    = SYSID
        TABLES
          NOTIF_PARTNERS           = it_NOTIF_PARTNERS
        NOTIF_NOTES              = it_NOTIF_N_EXT
          NOTIF_SAP_DATA           = it_NOTIF_SAP_DATA
        NOTIF_TEXT_HEADERS       = it_NOTIF_TEXT_HEADERS
        NOTIF_TEXT_LINES         = it_NOTIF_TEXT_LINES
        APPX_HEADERS             = it_APPX_HEADERS
        APPX_LINES               = it_APPX_LINES
        APPX_LINES_BIN           = it_APPX_LINES_BIN
         RETURN                   = RETURN
Please observe how first and last line of attachement is calculated. That is what created problem for me initially.
Hope this helps.
Regards,
Siddhesh S.Tawate

Sender Abap Proxy -- Receiver JDBC , catch communication channel exceptions

Hi All,
I have a sender abap proxy and a receiver jdbc asynchronous interface.
Now under some circumstances when I send some junk data for an update query(which satisfies metadata requirement but wrong primary key) it shows chequered flag in both XI and r/3.
But in communication channel it shows error.
Queries:
1. How do I handle this.
2. Since this is triggered from Abap wht will be subrc when method ends in this particular case.
3. Is there any possibility of program goin into dump?
Regards,
Prem

You can catch the exception in cx_ai_system_fault.
http://help.sap.com/saphelp_nw70/helpdata/en/75/a55c3cff8ca92be10000000a114084/content.htm
DATA:
lo_mes TYPE REF TO
     [Client proxy class],
l_sys_exc TYPE REF TO
        cx_ai_system_fault,
l_app_exc TYPE REF TO
        cx_ai_application_fault.
CREATE OBJECT lo_mes.
TRY.
CALL METHOD
lo_mes->EXECUTE_SYNCHRONOUS
    EXPORTING
      OUTPUT    = ls_request
    IMPORTING
      INPUT     = ls_response.
CATCH cx_ai_system_fault
            INTO l_sys_exc.
* handle system error
    EXIT.
CATCH cx_fault_1
            INTO l_app_exc.
* handle application error 1
CATCH cx_fault_n
            INTO l_app_exc.
* handle application error n
CATCH cx_ai_application_fault
            INTO l_app_exc.
* handle other
* application errors
ENDTRY.
Thanks,
Beena.

IDOC to abap proxy- Receiver Service Cannot be converted into ALE logical

Dear all,
I have idoc to abap proxy -
R3 to SRM scenario.
I am getting the error Receiver service cannot be converted to ale logical system.
I have check the receiver bs SRM_BS , adapter specific attributes ... im getting the logical system ( this is not the problem)
i am using receiver XI adapter
with XI 3.0 as protocol
and http destination with /sap/xi/engine?type = receiver
i can see the data in the moni of receiver SRM system but it shows a red flag
pls help

Hi kiran,
i have checked all the RFC destinations ... seems OK
problem is in SRM moni .. sender service and sender interface are not visible.
trace ::::
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
- 
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine/?type=entry</Trace>
<Trace level="1" type="T">COMMIT is done by XMB !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- 
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="1" type="T">system-ID = SR5</Trace>
<Trace level="1" type="T">client = 300</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = RFCADMIN_SR5</Trace>
<Trace level="1" type="Timestamp">2008-06-01T16:27:03Z CET</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- 
<Trace level="1" type="T">Message-GUID = DD2FF717DAE395F186DF001560A1C7CB</Trace>
<Trace level="1" type="T">PLNAME = RECEIVER</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline = RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Get definition of internal pipeline = SAP_RECEIVER</Trace>
<Trace level="1" type="T">Queue name : XBTR0003</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTR0003</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface *</Trace>
<Trace level="1" type="T">select interface namespace</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--start receiver interface action determination</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface SupplierPortalTradingPartner_CreateOrChange_In*</Trace>
<Trace level="1" type="T">select interface namespace http://sap.com/xi/SRM/SupplierEnablement</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline RECEIVER</Trace>
<Trace level="1" type="T">system-ID = SR5</Trace>
<Trace level="1" type="T">client = 300</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = RFCADMIN_SR5</Trace>
<Trace level="1" type="Timestamp">2008-06-01T16:27:04Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
<Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
- 
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
<Trace level="1" type="B" name="Inbound Framework" />
- 
- <asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
- <asx:values>
<CX_ERROR href="#o3314" />
</asx:values>
- <asx:heap xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:abap="http://www.sap.com/abapxml/types/built-in" xmlns:cls="http://www.sap.com/abapxml/classes/global" xmlns:dic="http://www.sap.com/abapxml/types/dictionary">
- <cls:CX_SY_NO_HANDLER id="o3314">
- <CX_ROOT>
<TEXTID>1F09B73915F6B645E10000000A11447B</TEXTID>
<PREVIOUS href="#o3313" />
<KERNEL_ERRID>UNCAUGHT_EXCEPTION</KERNEL_ERRID>
- <INTERNAL_SOURCE_POS>
<PROGID>496</PROGID>
<CONTID>1564</CONTID>
</INTERNAL_SOURCE_POS>
</CX_ROOT>
<CX_NO_CHECK />
- <CX_SY_NO_HANDLER>
<CLASSNAME>CX_BBPX1_STD_MESSAGE_FAULT</CLASSNAME>
</CX_SY_NO_HANDLER>
</cls:CX_SY_NO_HANDLER>
- <cls:CX_BBPX1_STD_MESSAGE_FAULT id="o3313">
- <CX_ROOT>
<TEXTID>65B8FEB5F43CC949B7CD662AB888ED34</TEXTID>
<PREVIOUS />
<KERNEL_ERRID />
- <INTERNAL_SOURCE_POS>
<PROGID>496</PROGID>
<CONTID>1738</CONTID>
</INTERNAL_SOURCE_POS>
</CX_ROOT>
<CX_DYNAMIC_CHECK />
<CX_AI_APPLICATION_FAULT />
- <CX_BBPX1_STD_MESSAGE_FAULT>
<AUTOMATIC_RETRY />
<CONTROLLER />
<NO_RETRY />
- <STANDARD>
<CONTROLLER />
<FAULT_TEXT>An error occured within an XI interface: Exception occurredE:BBP_BUPA_SUPPLIER:089 -Unable to determine logical system of sender; check your data Programm: CX_BBP_BD_ERROR===============CP; Include: CX_BBP_BD_ERROR===============CM002; Line: 57</FAULT_TEXT>
<FAULT_URL />
<FAULT_DETAIL />
</STANDARD>
</CX_BBPX1_STD_MESSAGE_FAULT>
</cls:CX_BBPX1_STD_MESSAGE_FAULT>
</asx:heap>
</asx:abap>
</Trace>
<Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
</SAP:Trace>
fault message says the sender is not having logical sys...but my sender sys is showing logical system in adapter specific attributes
pls help
points will be awarded

IDoc Sender - XI - Proxy Receiver with EOIO?

Hi all,
1) I'm sending custom Message Type/IDoc to XI using function module MASTER_IDOC_DISTRIBUTE from 4.7 ERP/6.2 Basis system.
2) In XI's integration engine I will be mapping the IDoc record layout to my proxy record layout. XI is Netweaver 04/6.4 Basis
3) The last step is to use the Proxy adapter to send the data to my receiver which is a BW Netweaver 04S/7.0 Basis system.
I know how to guarantee EOIO during step 3 and within my receiving system. Can I guarantee steps (1) and (2) above use QoS EOIO? If so any thoughts/discussion on how to do that would be appreciated.
Thanks!

Hi Shaun,
unfortunately in this case there is no chance..
You could pack idocs and send them all togheter, this is a queue-like processing but is not a robust and stable approach.
All you can do is to enqueue starting from XI configuring the right entries in table IDXQUEUE.
Regards,
Sergio

ABAP Proxy Receiver

Hi,
While i am trying to acces the transaction sproxy in my receiver R/3 system i am getting amessage saying "No connection to integration builder(only local data visible)"
Thanks and Regards,
Jishi

Hi,
Did u make proper entries in you <b>Receiver system's exchange profile..?</b>
U need to set the following parameters to connect from your Receiver system to the XI Server.
com.sap.aii.connect.repository.name
com.sap.aii.connect.repository.httpport
com.sap.aii.connect.repository.contextRoot
com.sap.aii.connect.integrationbuilder.startpage.url
com.sap.aii.applicationsystem.serviceuser.name
com.sap.aii.applicationsystem.serviceuser.pwd
Cheers,
Siva Maranani.

Sender Abap Proxy -- Receiver JDBC MaxDB

Hi Experts,
Please, PI works with MaxDB database?
What is the procedure? Need to install drivers?
SO is Linux.
Thanks for the help!

Hi,
>>>>Please, PI works with MaxDB database?
yes
>>>What is the procedure? Need to install drivers?
yes you need to install the driver - the rest is the same as with any other DB
Regards,
Michal Krawczyk

JDBC to ABAP PROXY ASYNCHRONOUS SENARIO

Hi Experts
JDBC to ABAP PROXY ASYNCHRONOUS SENARIO IN PI 7.4 ?
Can you tell me any one step by step procedure
BR,
Sagar

Hi Sagar
Check the documents below and you will be able to create the whole scenario.
JDBC sender part:
SAP PI Adapter Series: JDBC Adapter Configuration
ABAP proxy receiver part:
Step-by-step FTP to ABAP Proxy - Process Integration - SCN Wiki

Fault Message for inbound asynch ABAP proxy

Hi All,
I've got scenario File -> XI -> ABAP proxy all asynchronous.
Inside a proxy I'm throwing an exception using fault message.
I don't see application error in SXMB_MONI on XI, I can see that only in SXMB_MONI on receiving system.
Is it possible to have flag Application Error on XI monitor as well ?
Best Regards,
Tomasz

Jai,
I've checked that many times.
I'll describe my scenario in more details.
1. From the file I'm receiving a lot of items and trying to process as much as possible in one proxy call.
2. Those ones which are causing errors are sent out to XI (outbound proxy) one by one. XI sends them to the same interface which is used in 1. step where I have condition which checks for single item and when it's wrong then exception is thrown.
One SCM box is sender and receiver which my cause that problem.
Tomasz

ABAP Proxy implementation in R/3.

Hi,
I will develop an interface R/3 - XI using ABAP Proxy. XI should trigger the execution of a process in R / 3. This process can take much, so I am concerned about time-out parameters.
1. It is possible to run in background mode a ABAP proxy and asynchronously?
2. If the ABAP Proxy runs asynchronously, SAP can generate a time-out because the program takes too long?
Thanks in advance.

Hi,
I guess ABAP proxy always runs in the backgound mode as long as you are not executing it manually using SPROXY transaction. and the time out parameters in SAP will decide proxy time out.

ABAP Proxy comm channel not seen in Comm Channel monitoring

We have configured JDBC sender to ABAP proxy receiver.
We are unable to see the receiver channel in comm channel monitoring. Is this normal or are we missing something?
Also, the XI adapter cannot be seen in adapter monitoring...I hope thats fine...
We are able to generate the ABAP proxy but we need to see the comm channel to troubleshoot.
Any help will be appreciated.
Thanks

Hi SAP PI,
As with the above commens this link may help u how to debug proxies.. you may try with this..
For -- Debugging Proxies
https://weblogs.sdn.sap.com/pub/wlg/4098--Debugging [original link is broken] [original link is broken] [original link is broken]
For -- Testing Proxies
XI: Debug your inbound ABAP Proxy implementation
regards,
Kishore

SWCV not seen in ABAP Proxy

We have created some SWCVs. But some can be seen whereas some others cannot be seen!
The source and target systems are the same and all are JDBC sender to ABAP proxy receiver scenarios to the same client of ECC.
Only the products are different.
Can someone please help?
Thanks

Hi,
While dealing with the ABAp Proxies we have to activate the Settings in SAP R/3 System
How do you activate ABAP Proxies?
And also make sure that you have activated the newly created SWCV and do SLD Cache and SXI_Cache
Regards
Seshagiri

Attachments via ABAP Proxy

I have come across one client requirment where he needs to send the txt/pdf file as an attachment from R/3, currently that interface is using the ABAP Proxy, is there any idea about How to send the attachments via ABAP Proxy?

Hi,
Refer
XI: RFC or ABAP Proxy ? ....ABAP Proxies with attachments
/people/michal.krawczyk2/blog/2006/04/19/xi-rfc-or-abap-proxy-abap-proxies-with-attachments
Problem sending xls file in an attachment via ABAP proxy
Receive mail with PDF attachment into XI and send to ABAP proxy
http://help.sap.com/saphelp_nw70/helpdata/en/51/d5cd16235e4643ae8ec92395c4ad97/frameset.htm
Thanks
Swarup

Problem receiving acknowledgement: abap proxy == file adapter

Hi experts,
I am developing an asynchrone interface using PI 7.0. The scenario is: SAP ==> FILE.
In SAP I have created an abap proxy in wich I requested an acknowledgement when calling from the abap code. In PI I have created an Integration Process with a receive step, and a send step. In de send step I am asking for a transport acknowledgement.
When I test the interface and I look in the SXMB_MONI in PI, I see the acknowledgement given back to the IP, but in the SAP backend system I don't receive anything in the abap proxy which had send the original message. In de SXMB_MONI from SAP I see a "?" Still awaiting acknowledgement.
Can anyone help me with this scenario? I really need an acknowledgement from the file adapter in the calling abap proxy.
Regards, Jeroen

You need to crate a REceiver Agreement for this sender...
The Integration Server sends an acknowledgment message back to the sender (CENTRAL_BACK). It uses the name of the sender system for logical and technical backward routing.
If the sender is addressed using an ABAP proxy, you must define a corresponding receiver agreement for this sender.
http://help.sap.com/saphelp_nw04/helpdata/en/29/345d3b7c32a527e10000000a114084/content.htm
-SM

File to ABAP proxy with EOIO

Hi Experts,
I am working on File to ABAP proxy scenario. The requirement is to have EOIO from end to end.
Which means the files have to be sent to target system (R/3) in the same order as they are placed in the file location. I have two questions regarding this.
1. Do I have to create 2 queues, one in PI and one in R/3 to acheive this? In File Sender CC we have option of specifying queue name but in XI Receiver CC, I do not see such option. How to handle this?
2.For picking the files from folder if I use NFS, then I have option of specifying 'Processing Sequence' as 'By Date' to pick the files based on timestamp. But if I am using FTP, how can I make sure that the files are sent to Integration engine based on timestamp?
Please provide your valuable inputs.
Thanks and regards,
Prasad

Hi,
1. Do I have to create 2 queues, one in PI and one in R/3 to acheive this? In File Sender CC we have option of specifying queue name but in XI Receiver CC, I do not see such option. How to handle this?
1 queue is okay. Just specify it in the Sender File CC.
2.For picking the files from folder if I use NFS, then I have option of specifying 'Processing Sequence' as 'By Date' to pick the files based on timestamp. But if I am using FTP, how can I make sure that the files are sent to Integration engine based on timestamp?
Processing Sequence is not supported for FTP and is only for NFS.
If you have to use processing sequence, then do an FTP, bring the files to an NFS directory and then use the processing sequence accordingly.
Hope this helps.
Regards,
Neetesh

ABAP Proxy Receiver Asynchronous EOIO

Similar Messages

Maybe you are looking for