Attaching Error Status to Outbound IDOC. ?

Hello Experts,
We have a scenario in SAP PI / XI were upon creation of a Sales Order , Purchase Order or Material Master Flow to Non-SAP System through SAP PI/XI , the IDOC shouldn't flow to SAP PI following a validation on Material Group.
The IDOC is triggered through Output Type , there is a custom Z function module which create outbound communication IDOC. This output type is attached to a Process Code ZSO, ZMPO defined for respective scenarios defined above.
Currently i am attaching the the status = 07 to control data structure & the IDOC is getting created but is having error.
Is this the right practice to follow for attaching error message Outbound IDOC.
Awaiting for your response.
Best Regards
Priyesh Shah

It depends on the business requirement.
in a previous project, if there was any error during the validation of the data within the iDoc before it is created and sent, i would trigger an error and send the error to the person who created the data with the error for them to correct. they would then correct the error within the document and save and the iDoc would be triggered and sent correctly.

Similar Messages

How to update the status of Outbound IDOC in case of error

I want to know about how to update the status of Outbound IDOC in case of error.
I am using message control functionality here.

HI,
If u r using the standard message and basic type
u can do it in the FM attached to the basic and message type.There u need to write ur own message instead of standard SAP message..chek if there r any userexits available in the FM..where u can overwrite ur own message ..
If u r using the Zmessage and Zbasic type
then u need to declare an internal table of EDIDS structure and then append ur message to the internal table..
idoc_status-docnum = idoc_contrl-docnum.
idoc_status-msgty = <message type>
idoc_status-msgid = message-id.
idoc_status-msgno = message-number.
idoc_status-msgv1 = message-message_v1.
idoc_status-repid = sy-repid.
idoc_status-status = <give the error status>.
APPEND idoc_status.
Reward if u find useful
Regards,
Nagaraj

Message has error status at outbound side File To Idoc Scenario

hi ,
In my File to Idoc scenario , when i go to sxmb_moni , i found that its showing red flag at Outbound Status Tab and showing message "Message has error status at outbound side".
When i go to IDX5 and and select my idoc and click on Transaction Id it shows "Password logon no longer possible - too many faile" .
Please suggest what may be the problem ?
Regards,
Rohit

1. First check the RFC destination name used in receiver Idoc adapter communication channel.
2. As i said earlier, in sm59 transaction in XI gui, u can check same rfc destination under type 3. There check the logon credentials and the username.
3. Now goto the R3 system GUI and check in su01 that same user is locked or not. If locked unlock it.
4. And if u change the password of that user, then do the similar change in XI -> sm59 -> rfc destination logon credential
Regards,
Prateek

BPM Scenario: Message has error status on outbound side

Hi All,
        I am doing one BPM scenario. In my scenario i am collecting 12 different type of idocs in BPM and bundling these idocs and sending these to the 12 different files.
        If i send 12 idocs from the R/3 then my scenario is working perfectly fine. If i send less than the 12 idocs that time i am getting the error message as "Message has error status on outbound side" with red flag.
           Can you please explain what minght be the problem. I have already checked in SM58,SMQ1 and SMQ2.
Thanks & Regards,
Purushotham

Hi Nutan,
        I hv configured my scenario as follows
1. Start
2. Block ( Deadline and Control step for cancell the process)
   3. Fork(Necessary branches 12)
      4. Loop(12 loops)
          Under loop
          a. Receive Step
          b. Container Operation( For count)
          c. Container Operation(For append)
5. Fork( Necessary branches 12)
    6. Transformation
    7. Send
8 Stop
This is my scenario. In the first Fork step i am checking end condition as total number of idocs is reached then i am sending all the data to the target system. If the idocs are not reaching with in 1 hour then i am cancelling the process.
        Now can you please tell me what is the problem.
Thanks & Regards,
Purushotham

Error status on outbound side

Hi experts,
I am in JDBC to IDOC scenario and right now i face following error in SXI_MONITOR (black and white flag in status field BUT Red flag in outbound status):
"Message has error status on outbound side"
This is a heavy interface (up to 8MB) but, in the past, we did not receive this error. I saw that there is an entry in SM58 from the PIAFUSER that says "Lock table overflow"
Thus, I set the parameter enque/tablesize up to 8192 MB but after restarting the system it did not work either, a new entry in SM58 is shown.
If i analyse the runtime tab of the response of the message i can see
<SAP:AdapterStatus>007</SAP:AdapterStatus> --> for an erroneous interface execution (payload=7,2MB)
<SAP:AdapterStatus>006</SAP:AdapterStatus> --> for a successful execution (payload 6.5 MB)
Can anyone plz, help me on this?
I cannot explain why we did not face this in the past.
Can you please explain how the lock table works? and what does the overflow means?
Thanks a lot in advance and best regards,
David

Hi Sai,
Ive checked what you mentioned but cannot see the point there. Maybe you can help me:
Enqueue Operations 847
rejected 17
Error occured 0
Dequeue Operations 604
Error occured 0
Dequeue All Operations 661
Cleanup Operations 0
Backup Operations 1
Read Operations 21
Compress Operations 0
Verify Operations 0
Records written 58408
to the backup file 2
Maximum Number of Lock Owners 58406
Maximum Fill level 4
Current Fill Level 0
Maximum Number of Lock Arguments 58406
Maximum Fill level 14
Current Fill Level 0
Maximum Number of Lock Entries 58406
Maximum Fill level 14
Current Fill Level 0
Update; Fill Level at Maximum 1
Current Fill Level 0
Time in Lock Table /Seconds 0.073970s
Wait for Lock Table /Seconds 1.691441s
Time in Lock Server /Seconds 0.000000s
Besides, i dont think it is gonna be a matter of disk spaces as all of them have, at least, 3.0 Gb of free space.
Any other clue? I increased the enque/table_size up to 65 MB and the lock table overflow in SM58 still remains!!!
Thanks a lot and best regards,
David

Message has Error status on outbound side - in ABAP inbound proxy !!

Hi All,
One interesting question for you guys. I have got one of the scenarios like File to ABAP inbound proxy. Message are going properly, no errors in receiving system. But on PI moni I can able in "outbound status" column in red colored flag. No all the messages couple of them with u201CMessage has Error status on outbound side ". Why please?
Regards
San

Hi ,
Please check whether the correct data is coming from sender side . and check the j2ee engine runtime parameters.
Cheers,
Meera
Edited by: MeeravaliDudekula on Oct 18, 2010 2:36 PM

Message has a error status on outbound side

hi all
when iam doing bpm alert , in sxmb_moni iam getting the message
"message has a error status on outbound side" error flag is coming.
Regards
Raju

HI,
Check receiver agreement and reciever determination.
Regards,
AKshay.

Error Handling for Outbound IDOC - COSMAS (Cost Center Master)

Hi,
I need to trigger a mail to SAP inbox whenever a outbound idoc fails for any reason.
I know how to do it for inbound or outbound transaction data, but not sure how to do error handling for outbound master data.
Could one of you help me understand the same.
Thanks in Advance,
Vinoth

Hey Vinoth,
Do you want decide the recipient of the mail dynamically? am asking because if you give the USER NAME in the partner profile and when ever a IDOC fails a mail will automatically reach the user inbox automatically
let me know if i answered ur question.
Thanks,
Santhosh

Message has error status on outbound side

Hi All.
I'm doing file to file scenario.configured everything, showing success message in SXMB_MONI but with error flag at outbound status
My R/3 system is : SAP ERP Central Component 5.0
But I'm unable to find the related product for this system from the following systems
SAP R/3 4.5, 4.6 and 4.7version
I have selected : SAP R/3 ENTERPRISE, 47X110 IDS on idesecc
my question is whether i created technical system wrong or any other mistake i have done for this problem?
pls suggest a suitable solution for my problem.
thanks,
Manoj

Hi,
My message contains following information.
- <SAP:IDocOutbound xmlns:SAP="http://sap.com/xi/XI/Message/30">
<SAP:TABNAM>EDI_DC40</SAP:TABNAM>
<SAP:MANDT>100</SAP:MANDT>
<SAP:DOCREL>640</SAP:DOCREL>
<SAP:DOCNUM>0000000000036231</SAP:DOCNUM>
<SAP:DIRECT>2</SAP:DIRECT>
<SAP:IDOCTYP>CREMAS03</SAP:IDOCTYP>
<SAP:CIMTYP />
<SAP:MESTYP>CREMAS</SAP:MESTYP>
<SAP:MESCOD />
<SAP:MESFCT />
<SAP:SNDPOR>SAPTX1</SAP:SNDPOR>
<SAP:SNDPRN>LS_SAP</SAP:SNDPRN>
<SAP:SNDPRT>LS</SAP:SNDPRT>
<SAP:SNDPFC />
<SAP:RCVPOR>SAPRD1</SAP:RCVPOR>
<SAP:RCVPRN>LS_SAP800</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
<SAP:RCVPFC />
<SAP:TEST />
<SAP:SERIAL />
<SAP:EXPRSS />
<SAP:STD />
<SAP:STDVRS />
<SAP:STATUS />
<SAP:OUTMOD />
<SAP:SNDSAD />
<SAP:SNDLAD />
<SAP:RCVSAD />
<SAP:RCVLAD />
<SAP:STDMES />
<SAP:REFINT />
<SAP:REFGRP />
<SAP:REFMES />
<SAP:CREDAT>0000-00-00</SAP:CREDAT>
<SAP:CRETIM>00:00:00</SAP:CRETIM>
<SAP:ARCKEY>B07DF8A0A03811DBADD00003BAF07785</SAP:ARCKEY>
</SAP:IDocOutbound>
I'm unable to find where is this SAPTX1 .
Actually i created SAPRD1 port in XI pointing to R/3 and SAPXD1 port in SAP pointing to XI
SAP logical system as LS_SAP800 but idon't from where LS_SAP is coming
Thanks
manoj.

Error handling for outbound idoc

could you tell how to handle an outboun idoc error

Hi Jaya Krishna,
The Outbound erroe occurs because of so many reasons.It may be due to less repetations of data in segment , or if reciever is not available . U can process the IDOC-Outboubnd with help of following TCODES
1. TO check status - we02
2. To get list of process codes for Inbnd and Outbnd IDOCs - we64
3. TO check IDOC is sent to receiver or not- sm58
4. To trace IDOC - bdm2
5.To check status of tRFC executiojn- bd75
Followins is the very useful blog to solve your all problems , refer to that
1. /people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process
2. /people/kevin.wilson2/blog/2006/11/13/ale-scenario-development-guide
Regards.
Note: Reward if useful

ERROR STATUS 2 IN IDOCS

Hello Experts,
as i am running infopack in BI dev client 300 which extracts data from ECC dev client 250.
the infopack is with yellow status and showing 10000 from 0 records
details showing
Info IDoc 1 : sent, not arrived ; Error passing data to port
Data Package 1 : arrived in BW ; Processing : Selected number does not agree with transferred n
when i am checking the IDOC in ECC DEV its status is appearing 02 Error passing data to port
( Could not find code page for receiving system)
please help me to know as well as solve the error

Hi Dear,
       Please Check the Source System:-
         >RSA1>Source Sytem-->Right Click -->Check
       if it is ok.
      Activate the source System.
      if the same thing happen again, then:-
            check the role of the bakgroud user. there are some roles that should be assigned to them.
             asign proper role to background user of both (R/3 and BW).

Outbound IDoc Error: Status Code 37 'Sender Port' is invalid

Hi
I have an Error when the Outbound IDoc is triggered.
It shows that 'Sender Port in Control Record is invalid'.
Status Code: 37.
I know that there are some issues with the Sender Port Definition.
Please help me out to solve this problem using some checkpoints at each and every step.
Reward Points Assured.
Regards,
Baburaj

Hi Baburaj Manickam
Good
Follow this simple procedure
1) Send an outbound IDOC data(MATMAS) to a flat file on client1(SENDER).
- Create File Port (WE21) for outbound file.
- Maintain Distribution Model (BD64) for sender ->receiver system.
- Create Partner Profile (WE20) for logical system.
- You can use this program RBDSEMAT (t/code BD10) to generate IDoc MATMAS file(s).
_ Then you can FTP the file(s) to receiver system.
2) Upload the flat file as an IDOC on the inbound sytem
which is Client2(RECIEVER).
- Create File Port (WE21) for inbound file.
- Maintain Distribution Model (BD64) for receiver -> sender system.
- Create Partner Profile (WE20) for logical system.
- You can use this program RSEINB00 to upload IDoc MATMAS file(s).
INBOUND IDOC PROCESSING:
Firstly attach your idoc to a process code.
In the process cod you can tell the system that the specified program should be triggered whenever an idoc of that type comes to the system.
Then you want to have a Z-function module for your idoc processing, if I understand correctly.The steps should be:
1. Create a z function module for idoc inbound posting (copy from a function module idoc_input_*).
2. Set Function Modules as Inbound: - Transaction BD51
3. Assign Function Modules to Logical Messages and Idoc types:- Transaction WE57
4. Create process codes : Transaction WE42, and link the z-function module.
5. Create partner profile: transaction WE20 and attach the message type and process code.
6. In the Z- function module, extract data from the idoc segments, do whatever processing you want to do, and then call BAPI_CREATE_SALES_ORDER_FROMDAT2.
Try the Trasaction WE19 for testing your inbound and outbound IDOCs
Good Luck and Reward me for the same
Thanks
Ashok.N

IDOC: Update ERROR status

Hi Experts !!!!!!
I am creating outbound IDOC for Informatica as middleware.
Once transaction is saved in SAP, customized workflow will start on a trigger event and create IDOC using MASTER_IDOC_DISTRIBUTE. Before calling MASTER_IDOC_DISTRIBUTE i am doing few mandatory field validations.
My requirement is to generated IDOC, even validation fails and set status to '26'. I also need to set customized message in error status mentioning why IDOC failed.
Can anyone suggest how to achieve this.
Regards,
Rushikesh

Hi,
Did you configure partner profile with appropriate information?
Thanks,
Ganga

Idoc Error : Status 63

Hi,
Please let me know how to resolve error status 63 in idocs.
Regards ,
Shankar GJ
Edited by: Shankar GJ on Mar 11, 2008 5:45 AM

Hi,
IDoc status 63: Missing or incorrect partner profile
To receive an IDoc in the SAP system from the external system, you must define the outbound partner profile for the message type and all relevant partners.
For more information, see Interfaces ® External Systems ® Configure Warehouse Management ® Communication Ext. System -> R/3 ® Maintain Partner Profile in the Implementation Guide for Warehouse Management.
If the system cannot find the partner (that is, the connected partner system) for receiving the IDocs, proceed as follows:
Define the missing partner profile.
Trigger receipt of all existing IDocs, which the system has not yet been able to process, again.
For this error, the system triggers a workflow work item for the standard task Input: Error processing with IDoc and sends a message to the inbox of the corresponding user.
From the inbox, you trigger the subsequent transmission of the IDocs which contained errors.
Errors in partner profiles normally only occur in the test run.
Taken from below link!!
Processing Technical IDoc Errors
Reward if helpful..
Thanks,
Sathish Raj

OutBound IDOC Processing

Hi Experts,
I am getting the following error while sending outbound IDOC (Multiple IDOCS as a single message) to SAP-XI.I am trying to send the IDOC using WE19 transaction and getting the following error.
500 error during parsing of SOAP Header.Status record 02
Thanks
Ajay Garg

HI,
500 error during parsing of SOAP Header.Status record 02
The Idoc Status code 02 indicates as 02---> Error passing data to port
And the 500 error of parsing of SOAP header is internal server error.
HTTP 500 can be any problem at XI. Plz chk all the setting on the XI side.
Check this SAP SOAP Note for FAQ-856597 (Question No 1)
By default, the SOAP adapter sends the SOAP message with the content type text/xml.
When you check "Do not use SOAP envelope", the default contnet type is application/xml.
You can change the content type like this: Go to the SOAP receiver communication channel module tab. Add the module "localejbs/AF_Modules/MessageTransformBean" before the standard module. Add the parameter name Transform.ContentType and value text/xml.
Check out this
/people/varadharajan.krishnasamy/blog/2007/01/09/troubleshooting-soap-message--xi
One way of testing ur scenario
/people/michal.krawczyk2/blog/2005/08/25/xi-sending-a-message-without-the-use-of-an-adapter-not-possible
Can you refer below steps for troubleshooting. it may help you
Troubleshooting IDOC scenario
1. Start with checking the status in sm58 of sender R/3
Follow the steps
No message in found in XI in IDOC to FILE scenario
2. Try deleating the IDoc from IDX2 and refiring the same.
3. Check your RFC destination definition (the one pointing to your XI server) to confirm that it is of type '3' (R/3 system) and not 'T' (TCP/IP).
In your ID, in the Sender Business System --> Adapter Specific Identifiers, give the logical name for the business System pointing to the R3 system
4. Monitor the SM58 in R/3 for IDOC status.
5. Trouble shooting file to IDOC and IDOC to file
/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/error%2bhandling%2bin%2bfile-idoc%2bscenario
Refer below links for indepth troubleshooting
File to IDOC, trouble shooting
Thanks
Swarup
Edited by: Swarup Sawant on May 26, 2008 11:15 AM

Attaching Error Status to Outbound IDOC. ?

Similar Messages

Maybe you are looking for