Inbound IDOC Error handling

Hi,
I am using message type PORDCR1 to create a purchase order. This is calling a BAPI_PO_CREATE1 to create the PO inside. Now I have coded some validation in user exit that is available in Pre processing. So when there is any any error i populate the table bapi_return.
Now what is happeing after executtion of user exit it continues the function module and find out if there are any more errors. After execution it shows all the errors.
My requirement is when ever i get an error in user - exit it should stop further processing and write that error in log.
Can anybody please suggest me how can we do this.
Thanks,
Neha.

Think this as your last option:
1) create and attach ZBAPI_PO_CREATE1 in ALE Config
2) COPY your User Exit code at the start and it it gets through then only submit BAPI_PO_CREATE1

Similar Messages

Custom inbound Idoc error handling/ Workflow

Dear Experts,
I have a requirement where in I created a custom inbound idoc, but now i need to handle the errors in the workflow and notify the users thru workflow on an error.
Can some one please provide me a step by step guide on how to create a organizational unit, position and assign users to the position... and any other steps that need to be configured to notify the user on the error.
I'm pretty new to all these organizational uints and workflow related stuff. Any step by step would really be helpful.
Thanks for your time.
-Amit.
Moderator message: sorry, these forums cannot replace proper training, if there is step by step guides out there, then please use the search functions.
Edited by: Thomas Zloch on Oct 31, 2010 11:50 AM

Vittal,
1. If your requirement is for a SAP Standard Basic Message type and a Z extension: Then you simply have to find out the 'Standard Task' associated with basic type. You shouldn't worry about extensions. The standard task will be triggered at input error.
2. If your requirement is for a Z basic type i.e. you have created a customer IDOC for a custom processing: There are many dependencies on how you can achieve this. Firstly, you need to know how you're are processing this Z_IDOC. Are you using a standard FM or custom workflow or custom FM? There should be some triggering event within the processing of this Z_IDOC which will raise a certain flag when the error you want to capture happens (or when there is a generic error). You can configure this event in binding objects to trigger a workflow task. If you take a look at any standard tasks, you'll get an idea how the triggering event happens.
Once the workflow task (you can use custom task or use a standard task i.e. by triggering a standard event within the IDOC processing program) is triggered, you can either send it to SAP inbox, e-mail, trigger another processing etc. This is altogether another story.
So bottomline: For custom IDOC processing, you need to trigger an event when error happens. This can be a custom event or a standard event. This event should be linked to a task (custom/standard - check in SWETYPV). Bind all of these in PFTC. Once the task is triggered, you can do whatever you want to do with it.

Idoc error handling for error status 51

hi all,
I am trying to set up inbound idoc error handling. For that I have activated task TS00008068.
This task gets triggered for all error statuses except error status 51.
Could you please help me understand why it doesn't trigger the task for error status 51?
KR,
Vithal

Standard task 8068 is triggered for IDOC syntax, partner profile issues etc. The error message 51 is probably coming in from an inbound function module.
Firstly there isn't a single standard task that will be triggered for all errors. Each IDOC error, depending on the events triggered, will fire a predefined standard task. For example, you're trying to process an order inbound and the IDOC is successfully created and passed on to application. Then the inbound FM will attempt to create an order and probably fail at determining a sales order or a ship to etc due to a missing setup. Then a different event is triggered which is attached to standard task 8046. That is different from 8068.
Here is small subset of error 'vs' tasks:
Message       Workflow Task
SHPCON      TS20000051
INVOIC      TS00008057
ORDERS      TS00008046
SDPICK       TS00008031
WMMBXY TS00008009
So you have to choose the IDOC which you want to activate WF task. Then look at the event that is associated with it. Then make sure the event is linked to the message type and routing is active.

Outbound Idoc error handling through workflow

Hi,
I am trying to set up the workflow for outbound error handling. I found that there is a task TS00007989 which need to set up.
How this task can be triggered when outbound idoc error occurs in the system?
Kr,
Vithalprasad
Edited by: Vittalprasad on Jun 9, 2010 11:52 AM

Hi,
Have a look
Outbound IDoc Error Handling via Workflow
Outbound idoc error handling through workflow

Inbound IDOC error 51 Application Document not posted

Inbound IDOC error 51: Item: 002 Goods/Service number not entered So application document not posted.
Please help me out

hi
check whether service number is available in the idoc if not check the field mapping

Regarding idocs error handling

HI . i want to learn idoc error handling on sap xi side because my current project is in PRODUCTION They implemented lot of idocs so is there any documents(guides ) regarding error handling of idocs for both sender and receiver side.

Hi
Please refer File to IDOC Scenario..
the 2nd post (Troubleshooting IDOC scenario) from Swarup Sawant , you will get a very good understanding
as lots of reference links are attached with different scenarios.
Regards,
Srinivas

Scheduling agreement inbound idoc error.

Hi Experts,
I am creating an Scheduling Agreement with DELFOR02 inbound idoc, while creation the Scheduling Agreement system is giving error regarding Scheduling Agreement not found. In fact I have create the Scheduling agreement by T-code VA31. And I check the table VLPKM, there are relevant record stored.
Then I maintain the view V_T663A to not check everything when inbound idoc recevie. and tried agan in t-code BD87. the system give me another message Make an entry in all required fields.
How can I handle these error messages?
Thanks..
Regards....

Does any one has ideas for that?
Thanks.

Inbound IDOC error while processing Invoice

Hi All,
I received the following error while processing an Invoice on an inbound IDOC:
Field BSEG-MEINS - does not exist in the screen SAPMF05A 0300
Message no. 00349
Diagnosis
The specified field does not exist on the screen
Procedure
Check your batch input data
Any assistance will be greatly appreciated.
Thanks, Inno

Hi
Please check which G/L Accounts were involved and verify that the Field BSEG-MEINS was set to 'optional' in Transaction OB14. The correct Field Status Variant
for the Company Code can be viewed with Transaction OBY6 and the Field
Status Group for G/L Account can be found with Transaction FS00 under
the Create/bank/inter Tab. This should eliminate the Error 00 349.
Regards
Javier

Inbound idoc error in 51 Status of at least one serial number of item

Dear Experts,
There is one inbound IDOC which is in error with status 51 showing error Status of at least one serial number of item is not allowed.
Can you please advice why this error is coming.
Thanks & Regards,
Nikhil Kanegaonkar.

An inbound IDOC in error will have the status 51, & it is marked for deletion it has a status of 68.
http://www.dataxstream.com/2009/10/mass-status-change-sap-idoc/
http://wiki.sdn.sap.com/wiki/display/ABAP/IDoc+Statuses
Edited by: Krupaji on May 6, 2011 2:38 PM

Inbound IDOC error :51 Passed with out Message Type to ALE Layer

Hi,
I am struct wtih the inbound IDOC scenario ..XI able to send IDOC but at ECC side it is in 51 red status and the error message is
"IDOC passed without Message type to ALE Layer"
Do I need to pass these segment values in Message Mapping? I didnt mapped any MESTYP,SNDPOR,SNDPRT and so on.. disabled these fields...
Could any one light on this issue?
Thanks
Rajeev

>
rajeev raj wrote:
> Hi,
>
> I am passing values in MM as below:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <ZPORDCR01>
> <IDOC BEGIN="Constant">
> <EDI_DC40 SEMENT="Constant">
> <TABNAM>Constant</TABNAM>
> <DIRECT>Constant</DIRECT>
> <IDOCTYP>ZOrders</IDOCTYP>
> <CIMTYP>Constant</CIMTYP>
> <MESTYP>Z_Orders</MESTYP>
> <SNDPOR>B0009</SNDPOR>
> <SNDPRT>LS</SNDPRT>
> <SNDPFC>LS</SNDPFC>
> <SNDPRN>PD_100</SNDPRN>
> <RCVPOR>DEV</RCVPOR>
> <RCVPRT>LS</RCVPRT>
> <RCVPRN>Dev10</RCVPRN>
> <REFINT>GB</REFINT>
> <REFGRP>MTI</REFGRP>
> <REFMES></REFMES>
> <ARCKEY>20090909</ARCKEY>
> </EDI_DC40>
> <E1PORDCR SEGMENT="Constant">
>
> I am forwarding these values in MM... IDOC is successfully reaching in ECC but with 51 error in red... Logical system, post and message types are avaliable in Control record of the IDOC which received wiht errors in ECC.
>
> Thnaks
> Rajeev
Fill the TABNAME as EDI_DC40 and Direct as 2 (represents the inbound direction) and resend the idoc and check
Rajesh

Inbound Idoc error

Hi ,
I am getting error in Inbound idoc as follows "CC. .EX.593 does not exist" when i go to BD 87
and process it says "order is not valid for making status changes ".
can some one please guide how to solve this error "CC. .EX.593 does not exist"?
Thanks,
Pradeep.

This is a data problem .Closing it.
Edited by: Pradeep Akula on Jun 15, 2011 7:10 AM

Invoic inbound IDOC error.Please help!

Hello:
When I posted AP document by IDOC triggerred by output RD04 in billing document, this inbound idoc always failed with error message:The transaction was terminated by the user.
My message type is INVOIC.
Do you know why this error happened?
Thanks

message is "You are not authorized to use Transaction FB01".So I am wondering if the error message "The transaction was terminated by the user" is also caused by authorization problem.
It seems yes. Why dont you try with proper authorization?
Reddy

MRESCR01 inbound IDOC error: "Object type 'TRANSID ' has no relationship '

Hello,
I am trying to get an inbound IDOC from XI to a SAP R/3 System.
It's an extended idoc (MRESCR01) for create orders.
The error at /we02 in the inbound system is:
Object type 'TRANSID ', key '0A1F032A59B345D027B002DE ', log.system ' ' has no relationship 'OUTTID '
Message no. RL007
Diagnosis
All the roles used in relationships of type 'OUTTID' should be found for object type 'TRANSID' with key '0A1F032A59B345D027B002DE' in logical system ''.
System Response
No such roles were found.
Further information:
XI process message succesfully, with the Z segments extended information. But, at the WE02, only one of the 3 extended segments arrives to SAP R/3.
Thanks a lot for your help, best regards

thanks shridar and michal for response.
these solution solved the problem of the segments. now the 5 arrives to SAP R/3.
but i keep getting the error and IDOC is not processed:
IDOC STAT = Status 51
Object type 'TRANSID ', key '0A1F032A59B345D03A7A0A26 ', log.system ' ' has no relationship 'OUTTID '
Message no. RL007
Diagnosis
All the roles used in relationships of type 'OUTTID' should be found for object type 'TRANSID' with key '0A1F032A59B345D03A7A0A26' in logical system ''.
System Response
No such roles were found.
Thanks and best regards,

IDoc error handling using workflows

Hi,
I have a requirement to generate IDocs in the Source system and process them in the target system. The IDoc message type is HRMD_ABA. And I am using standard processes to generate them and post them using PFAL and RBDAPP01 program respectively.
All this is working fine. But now I need to include error handling in the source and the target systems which would send mails to a User's Outlook mailbox whenever there is an error. I mean to say, we need more functionality than just monitor them through WE05 transaction.
Can any one tell me how this can be achieved. I have been looking into the program RSEIDOCA which would send workflows to SAP Inbox, but I need to send it to Outlook Inbox.
And I have heard that there is a workflow process which would help me to do this.
All your answers would be highly appreciated.
Thank you in advance,
Sid.

Hi,
First Step:
You have to maintain the e-mail-address in SU01 for required users.
Second Step:
SCOT Configuration
Third Step:
Depends on your SAP Version do configuration SWNADMIN
Or excuting the report RSWUWFML2 as the background job.
Thanks and Regards,
Prabhakar Dharmala

Inbound IDOC error - status code 52- application document not fully posted

Hi,
In Inbound IDOC, the status code is 52 ---> Application document is not fully posted(satus of the inbound idoc is in yello colour). I want to reprocess this idoc in BD87 t.code in order to convert the yellow colour to green colour. Before reprocessing the IDOC, i need to rectify the problem and then reprocess the idoc in bd87. am i correct? if yes, what i need to do to solve the error --->application document not fully posted. Please guide me friends.
Thanks in advance.
Regards,
Sri

HI
If you are FM to process the inbound IDOC,
possibilities are like below .
Reason 1 :
In partner profiles, check is it trigger immediately or not ? for particular partner profile which u r using .
reason 2 :
If you are using BDC code to update the data .if any screen contains error then also you will get the status in yellow .
reason 3 :
Have you tried with TCODE BD87 , might be it is processing error also .
i have worked on same probelm so if u r not solved with the issue after trying above 3 reasons .
reply me back .

Inbound IDOC Error handling

Similar Messages

Maybe you are looking for