PE outbound error

Hi, erveryone,
I got an PE outbound error when I test an integration process, when I double click 'PE'in SXMB_MONI, I was brought to <Event Queue Browser>.
I heard someone said that the technical details could be viewed in the workflow log, but where can I get into this tool?
I searched through this forum, and try to use SXMB_MONI_BPE/SWWL, but I can't find any process instance.
Is there any more workflow specific configuration needed?

HI,
but I can't find any process instanchee.
>>>I think, Integration process is not triggered.
Check the Reciever etc.
i.e you need to have 2 reciever determintions.
1) SOurce->Integration Process
2) Integration Process ->Reciever
Check all, also check SXI_CACHE for the runtime version of BPM.. So that if there is any error in the runtime version , the return code will other than 0. check this. it should be zero.
Have a look into this doc for the monitoring-
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/e7bc3a5a-0501-0010-1095-eb47159e169c
Regards,
Moorthy

Similar Messages

Outbound error IDoc reprocessing

I have a scenario like whenever an outbound idoc is in error status, should be able to correct the idoc n reprocess it.
Suppose outbound idoc is in status 02. System process code will notify the agent assigned in partner profile. When i execute the workitem and corrected the port and try to reprocess, this status is set to 30. My requirement is once i correct the port status should become 03. How do we acheive this ? (not through report rseout00 )
1. In general scenario how do we handle outbound error idocs?
2. Is system process codes are used only for notifications or error processing?
Inputs will be appreciated regd outbound error reprocessing .
Thanks.

Hi Indira,
1. In general scenario how do we handle outbound error idocs?
You can use transaction BD87 to monitor the IDoc statuses.
and use the following programs to reprocess outbound and inbound error IDoc(s).
RBDAGAI2 - Re-processing of IDocs after ALE Input Error
RBDAGAIE - Reprocessing of Edited IDocs
RBDAGAIN - Process Outbound IDocs with Errors Again
RBDAGAIP - New Posting of Partially Posted IDocs
RBDMANI2 - Manual Processing of IDocs: Post IDocs Not Yet Posted
RBDINPUT
2. Is system process codes are used only for notifications or error processing?
The process code ise used in both ALE and EDI framework to identify the function module or API (Application Programming Interface) to be invoked for subsequent processing. Inbound as well as outbound interfaces use process code but for different purposes. Outbound process codes are stored in table TEDE1, while inbound process codes are stored in TEDE2.
Hoep this will help.
Regards,
Ferry Lianto

ALE outbound error handling

Hi gurus,
I've implemented some ALE systems successfuly. I mean the distribution of information is alright but, now, I want to get some notification when any outbound error occurs.
I,ve filled the 'Post processing: permited agent' tab in the partner profile (both for partner and message type) but it doesn't work. I suppose I need to do something else.
Can anybody help me with this matter?
Thank you in advance.
JM Parra.

Hi,
Just an added information
Message Type : ALEAUD,is present which is used to give successful notification/confirmation in case of the posting of the IDocs, this Message type should be configured on the inbound side( Partner Profile and the Distribution Model) after which an IDoc of ALEAUD Message Type would be generated and the segments in this IDoc would contains the details of the Message Type(Including IDoc no) for which the confirmation is generated.
Thanks
Krithika

File to Idoc - Outbound Error

Hi,
I am doing File to IDOC scenario. I got error
in "Message has error status at outbound status" .. When
I opend that messeage then i got this ...
<SAP:IDOCTYP>ZIDOCIN</SAP:IDOCTYP>
<SAP:CIMTYP />
<SAP:MESTYP>ZMTIDOCIN</SAP:MESTYP>
<SAP:MESCOD />
<SAP:MESFCT />
<SAP:SNDPOR>SAPX11</SAP:SNDPOR>
<SAP:SNDPRN>Logi_01</SAP:SNDPRN>
<SAP:SNDPRT>LS</SAP:SNDPRT>
<SAP:SNDPFC />
<SAP:RCVPOR>SAPA11</SAP:RCVPOR>
<SAP:RCVPRN>A11CLNT200</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
<SAP:RCVPFC />
<SAP:TEST />
Can any one tell me what to do to solve this.
thx,
Ansar.

Hi,
There is somethig worng with your Partner Function while defining the the Partner Profile, please check it. The Partner function is optionla and see if you need it
Go thru the link,
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b80b543d711d1893e0000e8323c4f/content.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660
Thanks,
Prakash
Thanks,
Prakash

EDI outbound error

Hi All
we are working on EDI outbound messages and facing the following error
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">APPLICATION_PROGRAM_ERROR</SAP:Code>
<SAP:P1>Z_ABAP_MAPPING_IDOC_TO_FLAT</SAP:P1>
<SAP:P2>SAP-ABAP</SAP:P2>
<SAP:P3>UNCAUGHT_EXCEPTION</SAP:P3>
<SAP:P4>Program Z_ABAP_MAPPING_IDOC_TO_FLAT===CP Include Z_ABAP_MAPPING_IDOC_TO_FLAT===CM001 Line 1</SAP:P4>
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error in mapping program Z_ABAP_MAPPING_IDOC_TO_FLAT (type SAP-ABAP, kernel error ID UNCAUGHT_EXCEPTION) An exception with the type CX_SY_REF_IS_INITIAL occurred, but was neither handled locally, nor declared in a RAISING clause Dereferencing of the NULL reference.</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
How can i solve this error.
Regards
Ashwin Kumar

HI Ashwin
I think this exception you need to catch it in the ABAP..
This may help u- http://help.sap.com/saphelp_47x200/helpdata/en/55/bff20efe8c11d4b54a006094b9456f/content.htm
just cross verify with this guide-
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e3ead790-0201-0010-64bb-9e4d67a466b4
Cheers..
Vasu
** Reward Points if found useful **

IDoc outbound errors - mail send step in WF to send info-mail to enduser

Hello specialists
I searched quite a lot in the forums now. I found lot of info but nothing regarding my issue.
I need to send an info-mail to the end user creating purchase orders. But only if the idoc (outbound ORDERS) could not be sent (failing for some reason, i.e. if rfc connection fails). This is what I've done to achieve this:
- in WE40 I linked my WF to process code EDIO
- the WF-BATCH user has an email address assigned to it (in SU01)
- the mail sending step in my WF is configured like this:
recipient type = G (organizational object)
Expression = &_WORKITEM.CREATEDBYUSER.ID& (this contains the enduser id)
subject = Test for &WORKITEM.CREATEDBYUSER.ID&
When testing the mail can not be delivered (error SO23).
When setting recipient type to U (E-Mail address) and giving a valid e-mail address, then it works fine (SCOT, etc. is configured and mailing to external systems works). But setting the e-mail address hard coded style in the mail send step is not an option here!
It seems that the send mail step (SELFITEM.SENDTASKDESCRIPTION) always requires a valid e-mail address. Is it not able to handle SAP user id's ?
Thanks in advance for some guideance on this one.
Renaud
Edited by: Renaud Desarzens on Feb 11, 2010 3:00 PM

Hello and thanks for your help.
I was able to solve it like this:
- don't use mail send step
- instead, add new activity with a new task (SELFITEM.SENDTASKDESCRIPTION)
- in the bindings (workflow -> step) set:
B --> &TYPEID&
&_WORKITEM.CREATEDBYUSER.ID& --> &ADDRESSSTRINGS&
Seems that the mail send step doesn't allow TYPEID to be "B" because each time I tried to tweak the generated bindings that way it messed up the recipient type and expression I set before.
Regards
Renaud

IDOC OutBound Error 29: Entry in outbound table not found?

Dear All,
 I configed the customized IDOC,and used BD64,WE20 Generate Partner Profile.the partner type is u2018LSu2019,In We20,I clicked the check button .There is no error in check.Other config also correct.
My outbound program main code is :
WA_IDOC_CONTROL_RECORD-MESTYP = 'ZMSGTYPE_WE81'.
WA_IDOC_CONTROL_RECORD-IDOCTP = 'ZIDOCTYPE_WE30'.
Receiver
WA_IDOC_CONTROL_RECORD-RCVPOR = 'A000000003'. "Port
WA_IDOC_CONTROL_RECORD-RCVPRN = 'target100'. "Partner number
WA_IDOC_CONTROL_RECORD-RCVPRT = 'LS'."Partner type
WA_IDOC_CONTROL_RECORD-RCVPFC = 'LS'."Partner function
Sender
wa_idoc_control_record-sndpor = 'A000000001'. "Port
wa_idoc_control_record-sndprn = 'source500'. "Partner number
wa_idoc_control_record-sndprt = 'LS'. "Partner type
WA_IDOC_CONTROL_RECORD-SNDPFC = 'LS'."Partner function
DATA L_ITEM TYPE I.
LOOP AT GT_IDOC.
 L_ITEM = L_ITEM + 1.
 WA_EDIDD-SEGNAM = 'ZSEG_WE31'.
 WA_EDIDD-SEGNUM = L_ITEM.
 WA_EDIDD-SDATA = GT_IDOC.
 APPEND WA_EDIDD TO IT_EDIDD.
ENDLOOP.
CLEAR L_ITEM.
SORT IT_EDIDD BY SEGNUM.
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
 EXPORTING
 MASTER_IDOC_CONTROL = WA_IDOC_CONTROL_RECORD
 OBJ_TYPE = ''
 CHNUM = ''
 TABLES
 COMMUNICATION_IDOC_CONTROL = IT_COMMUNICATION_IDOC_CONTROL
 MASTER_IDOC_DATA = IT_EDIDD
 EXCEPTIONS
 ERROR_IN_IDOC_CONTROL = 1
 ERROR_WRITING_IDOC_STATUS = 2
 ERROR_IN_IDOC_DATA = 3
 SENDING_LOGICAL_SYSTEM_UNKNOWN = 4
 OTHERS = 5
IF SY-SUBRC <> 0.
 MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ELSE.

hi Sun,
The value 'X' means ABAP_TRUE, which means the outbound ALE settings for your message type are OK.
Did you check the sy-subrc value after the FM 'MASTER_IDOC_DISTRIBUTE' is called ? and if yes what is the value ?
Also did u check the IT_EDIDD table, whether is contains any values ?
If all of the above is fine then call the FM 'EDI_DOCUMENT_DEQUEUE_LATER' by passing the document number of the outbound IDoc created, this number you will from the 'communication_idoc_control' table which you need to pass to your FM MASTER_IDOC_DISTRIBUTE.
for your reference attached is code for it
 CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
 EXPORTING
 master_idoc_control = wf_edidc
 TABLES
 communication_idoc_control = int_comm_cntl
 master_idoc_data = int_edidd
 EXCEPTIONS
 error_in_idoc_control = 1
 error_writing_idoc_status = 2
 error_in_idoc_data = 3
 sending_logical_system_unknown = 4
 OTHERS = 5.
if sy-subrc = 0.
APPEND LINES OF lt_idoc_comm_control TO g_idoc_comm_control.
endif.
LOOP AT g_idoc_comm_control.
 CALL FUNCTION 'EDI_DOCUMENT_DEQUEUE_LATER'
 EXPORTING
 docnum = g_idoc_comm_control-docnum.
ENDLOOP.
{/code}
hope this will solve your problem
Edited by: Ashwinee on Dec 26, 2008 12:09 PM

Restart: Outbound Error in SXMB_MONI

Hi ALL
I have an error in SXMB_MONI in outbound status. couldnt see any worklogs in PE also. The message status shows success but error in outbound. Howto restart the message.
1. IP is 0 in sxi_cache
2. CC configuration are correct
thkx
Prabhu

Prabhu,
you cant reprocess the sucessfull processed message by the intergatin server.if need to send the smae data again use you need to change the std report program
RSXMB_SUPPORT_RESTART. you copy this program to u zprogram and commet the following
check if support is requested
perform support restart
using l_imo
execute this and give the GUID of ur processed message it will reprocess it again.
But this not advised one to do it in production or QA envirnoments
Thanks
Sreeram.G.Reddy

Outbound Error Processing via Workflow

Hi..
Can anybody help ??
I want to trigger my own workflow (Customized workflow not standard), whenever an outbound IDOC is in error status.
Please help !!
Dev

Hi,
Please check this link...
http://help.sap.com/saphelp_nw2004s/helpdata/en/b6/7fe03c19758e71e10000000a114084/frameset.htm
Regards,
Raja Sekhar

OUTBOUND- ERROR HANDLING USING WORKFLOW

Hi Gurus,
Can any one tell me about workflow & how to do error handling using WORKFLOW in OUTBOUND IDOC.Below are the points , Please check it & send me reply.
1.Value not found for Custom IDoc fields.
2. Partner Profile not maintained correctly.
3. Syntax error in IDoc.
4. IDoc ready for dispatch (ALE Service).
Regards,
Chiranjeevi.

Hi,
FOr most of your requirements, there is already std. SAP IDOC error Single-step tasks.
Have a look at WE46 transaction.
Also, if you go to SWO1 and search with "IDOC*", you will get all the BO's even.
It's pretty straightfwd. Also, in Partner Profiles, WE20, for each of the IDOC type, there is one "Post.Processing AGent", whom if you set up correctly, will be the person receiving this Errored IDOC mails.
Hope this helps
venu

ALE / IDOC Outbound Error Handling

Hi Experts,
I got an error in Outbound Process.
An IDOC gets the status 36 - Timed out.
Can anyone tell me how can i resolve this Error?.
Thanks in advance,
Sudhakar

Hi ,
Best option is to keep a sql trace on the outbound idoc which will tell you at which perform or functional module ,the performance is taking time to fetch .
all check with basis in terms of timed out ,they would have set a paramater for time out in terms of mins or hrs.

Outbound error "No cross-system business area has been assigned to bu. area

Hi everyone,
i have idoc failed in outbound with error No cross-system business area has been assigned to business area 0001
Thanks in advance
Soufiene

Hi Fernando,
The issue is from HR , an entry for an employee was entered and suppose not it generated idoc failed.
Thanks
Soufiene
Edited by: Soufiene Tchantchane on Sep 7, 2011 10:32 PM

Bdoc outbound Error

Hello,
Intermittently we get the following BDOC error when updating the BP in CRM and replicating to R/3.
Error: standard entry does not exist for communication type Faxs
Any ideas as to what this could be as I can't seem to find what entry, if any, is missing on the ERP side.
Regard
Chan

Hi Chan,
You have 3 options to resolve the issue:
1. In order to avoid error message XR002 you must set the Standard
Indicator Validity in the maintained telephone in BP transaction.
You can find this indicator in the yellow arrow near the telephone
number. Here you must press the button "Standard Indicator Validity".
2. In customizing you have the possibility to switch off the time
dependency of the addresses causing the XR002.
3. The error occurs due to missing ADRU entries for the communication
data (Email, Phone, Fax etc).
The function modules used in data exchange assumes that there is
an ADRU entry for all addresses. This assumption is partially correct.
If an address is created in Basis release 6.40 and above, then for all
communication data of that address ADRU entries will be created.
But if a Business Partner(with address) is created in release 6.20 or
below and system is upgraded to 7.0, ADRU entries for the communication
data of those addresses are not automatically created. When the user
opens that BP in change mode & modifies the communication data and
saves it then ADRU entrys for that BP's communication data are created.
SAP Development has provided a correction report in note 966185 and
in the attachment I've added to this message.
Please create a Z Report in the Test System and copy the code
in Z_ADRU_BP.txt. This report takes the BP as a parameter and creates
the ADRU entry for the BP. The report has a testmode in which no DB
changes are made but only the log is generated. You can try it for a BP
and then trigger a BDoc for this to see if it is working correctly.
Once this works please create a Z report and copy the code in.
ZADRU_CREATE.txt and execute it. This loops through all the
communication tables (ADR2...ADR13) for all the BPs and creates the
corresponding ADRU entries.
Also check the following notes
1128628 Incorrect communication usages generated in BP inbound
1127070 Incomplete retrieval of address usages
1129212 Default telephone/mobile was not determined correctly
1224351 BP DX:Outbound incorrect when ADRU entries are missing
thanks
Willie

Siebel outbound error

Hi All,
has anybody encountered the following error when renaming the "dialing list" file to receive an outbound dialer call on Siebel Client?
09:43:15 pg3A-pim1 HEARTBEAT_RESP message received from MR application does not correspond to an outstanding request. Ignoring.
Thanks in advance,

Hi Fabien,
I am Cisco SE in India just want to have a chat with you for 10 minutes can please you share your number on my email [email protected]

ABAP Proxy Outbound Error

hello everybody,
i have the next scenario ABAP Proxy->XI->RFC, the problem is that in the sender system I'm getting the next error in SXMB_MONI of sender system:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:ErrorHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
<SAP:Context />
<SAP:Code p1="401" p2="Unauthorized" p3="" p4="">HTTP.HTTP_STATUS_CODE_NEQ_OK</SAP:Code>
<SAP:Text language="EN">HTTP status code 401 : Unauthorized</SAP:Text>
</SAP:ErrorHeader>
the status is system error, can anyone help me with this error, cause messages are not aariving to Integration Server, thanks in advance.
Regards,
Julio Cesar

Hi Julio
Check Following Steps:
1:Have you insterted the correct URL of your Integration Server?
XMB.TargetURL=http://<host>:<ICM_Port>/sap/xi/engine?type=entry
2: Is the user and password correct?
XMB.User=XIAPPLUSER
XMB.Password=*****
3: Are the read permissions in the source directory correct?
file.sourceDir=/usr/sap/...
4: Be sure you use the ICM Port in my case 8000, e.g.
XMB.TargetURL=http://server:8000/sap/xi/engine?type=entry
If you use SLD information also include
XMD.SLDConfiguration=SLDaccessor in the file.
Check also that the XI user has the right profiles in the XI ABAP instance.
Thanks
Abhishek Mahajan
***Reward points if helpful*********

PE outbound error

Similar Messages

Maybe you are looking for