Error Handling in IDoc
Hi Friends,
Can anybodytell me any procedure for Idoc error Handling (Restart and Recovery) of IDocs that occured in error status. What could be be the possible ways apart from BD87.Thanks in advance for ur gr8 help!!!
It really depends on they type of error.
For transactions that need data remediation, the preferred method of posting is via SAP Workflow (xaction So01 for the inbox).
For things that did not post due to missing config, etc. use BD87 (assuming the config now exists).
If you have specific questions post them and I will try to help.
Similar Messages
-
Re : How to Error Handling In Idoc /ALE.
Hi This is Arief ,
I tranfer the Data Through ALE from One Client To Other Client some of Data not Posted ......how check other client wither Data Posted or not ....
How to error Handling In IDocs.....pls Help me.......
Kind Regards
Arief .SHi
The exception handling for idocs
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b7f1543d711d1893e0000e8323c4f/frameset.htm
Exception handling in File to IDoc Scenario
For RFCs
Re: Passing SAP Exceptions to a sync SOAP Call
Error Handling when using RFC
Exception Handling while Calling RFC - BPM
handle exceptions in remote function modules -
could any one please tell me how to process the IDOC if errors occur ( for ex status 56.) in Inboun or Outbound IDOC.
Hi,
Please refer the link below:
http://searchsap.techtarget.com/tip/0,289483,sid21_gci1268508,00.html
Thanks,
Sriram Ponna. -
IDOC to SOAP asynchronous scenario Error handling
Need an expert!!!!!!!!! advise on error handling for IDOC--PI--
SOAP scenario.This is a asynchronous scenario where PI is calling a Legacy system using SOAP adapter.My question is how i can do error handling in this scenario.If i get an alert in pi with payload variable that would be fine, do i need to use BPM and if that is tthe case what will be steps.
Appreciate your help.
ManishHello Manish,
My question is how i can do error handling in this scenario.
Use the standard alert framework. Search on SDN / SAP Help for details.
do i need to use BPM and if that is tthe case what will be steps.
BPM is not required to raise alerts, as this is an async call.
Regards,
Neetesh -
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 -
Error Handling in File to Multiple IDOC Scenario?
Hello Experts,
My scenario is file with Multiple records and I want to send it to SAP system.If there will be 10 Records in my file I need to create 10 IDOC in Target system.
I can use below of the two options.
1) File to Multiple Idoc (1.N Mapping)
2) Using BPM
3)Directly place the file in SAP application server and process it via ABAP Program.
However I am not clear in which option error handling will be more effective.Please suggest.
Basically I want to handle If out of 10 records 9 are correct and 1 record is not correct then I should be able to report within PI without affecting 9 correct records.Is it possible 9 records will be sent to SAP system and PI will only show error for 1 incorrect record.
Also I will be doing this scenrio for transaction data with huge size (1 Million Records).Which approach will be more effective in this case.
Thanks,
PushkarHi Patel,
I want to handle If out of 10 records 9 are correct and 1 record is not correct then I should be able to report within PI without affecting 9 correct records.Is it possible 9 records will be sent to SAP system and PI will only show error for 1 incorrect record.
when working on graphical mapping, the target structure is created when there are no errors in all records of source structure.
suppose if we have validation error in 9th and 10th record, then we can not process the first eight records and inturn we can not store the two error records in XI for further.
i suggest you the third option, you can directly place the file in SAP application server and process it via ABAP Program.
this is far better because you can do more customizations as you have to deal with millions of records.
Regards,
Pradeep A. -
For IDOC monitoring, analysis and error handling in ALE & idoc
Hello...experts..can u please tell me about idoc monitoring,analysis and error handling..and can u please tell as per interview point of view in this area..if availble can u send material about this...
thx
Message was edited by:
durga kottapalliHi,
Reprocessing IDocs with errors
Outbound (BD88)
Once the error has been determined and corrected it is not necessary to resend the IDoc again. You simply resend the IDocs that have already been generated.
Using the IDoc overview screen you need to take note of the following for each IDoc that was not processed:
Error number: 2, 4, 5, 25, 29
Error number: 30 (Execute Check IDoc dispatch to process)
IDoc number
Using the Error number, the IDoc number and the transaction BD88 , with the required message type you can resend the IDoc. Match the error number with this transaction and execute the function for the IDocs incorrectly processed.
Just check the below link, u will get all IDOC related Interview questions
http://www.allsaplinks.com/idoc_sample.html
http://www.allsaplinks.com/
http://www.sappoint.com/abap.html
http://www.sap-img.com/
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
http://www.sappoint.com/abap.html
http://sap.ittoolbox.com/documents/popular-q-and-a/extending-a-basic-idoc-type-2358
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://expertanswercenter.techtarget.com/eac/knowledgebaseCategory/0,295197,sid63_tax296858_idx0_off50,00.html
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
http://help.sap.com/saphelp_47x200/helpdata/en/dc/6b7eee43d711d1893e0000e8323c4f/frameset.htm
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sap-img.com/
http://www.allsaplinks.com/
Regards,
Suresh.
Message was edited by:
SureshKumar Ramamoorthy -
Error handling in bdc Fb01along with erros in Idoc.
Hi,
Can any one send me the sample code for the error handling in bdc Fb01along with erros in Idoc. Actually, mail should be sent
Thanks
Avi.Hi,
This may help you.
<b>FORM send_mail USING receiver.
CLEAR: w_lines,tbl_packing_list,tbl_object_header,
tbl_contents_txt, tbl_receivers.
REFRESH:tbl_packing_list, tbl_object_header,
tbl_contents_txt,tbl_receivers.
SORT tbl_err.
DELETE ADJACENT DUPLICATES FROM tbl_err COMPARING ALL FIELDS.
IF NOT tbl_err[] IS INITIAL.
Preparing the email.
PERFORM prepare_email.
ELSE.
If sy-subrc NE 0.
MOVE sy-subrc TO w_code.
ENDIF.
EXIT.
ENDIF.
Get the content of header e-mail document data
PERFORM document_data.
Get details of the error file attached (like type of file and format)
PERFORM packing_list.
Get receiver mail id's
tbl_receivers-receiver = receiver.
tbl_receivers-rec_type = 'C'.
tbl_receivers-express = c_flag.
tbl_receivers-sap_body = c_flag.
APPEND tbl_receivers.
Call FM to send E-mails to receivers
CALL FUNCTION 'SO_NEW_DOCUMENT_ATT_SEND_API1'
EXPORTING
document_data = st_document_data
put_in_outbox = 'X'
TABLES
packing_list = tbl_packing_list
object_header = tbl_object_header
contents_txt = tbl_contents_txt
receivers = tbl_receivers[]
EXCEPTIONS
too_many_receivers = 1
document_not_sent = 2
document_type_not_exist = 3
operation_no_authorization = 4
parameter_error = 5
x_error = 6
enqueue_error = 7
OTHERS = 8.
ENDFORM. " send_mail
*& Form prepare_email
text
--> p1 text
<-- p2 text
FORM prepare_email.
E-Mail body content
IF NOT w_lifnr IS INITIAL.
CONCATENATE text-015 w_docnum text-016
INTO tbl_contents_txt-line
SEPARATED BY space.
ENDIF.
APPEND tbl_contents_txt.
CLEAR tbl_contents_txt.
E-mail error file attachment header
CONCATENATE text-063 text-064
text-065 text-066 c_comma
INTO tbl_contents_txt-line
SEPARATED BY c_comma.
APPEND tbl_contents_txt.
CLEAR tbl_contents_txt.
E-mail error file attachment content
LOOP AT tbl_err.
CONCATENATE w_docnum tbl_err-v_segnum
tbl_err-msg tbl_err-type
INTO tbl_contents_txt-line
SEPARATED BY c_comma.
CONCATENATE c_linefeed tbl_contents_txt-line c_comma
INTO tbl_contents_txt-line.
APPEND tbl_contents_txt.
CLEAR tbl_contents_txt.
ENDLOOP.
ENDFORM. " prepare_email
*& Form document_data
text
--> p1 text
<-- p2 text
FORM document_data.
CLEAR w_line.
IF NOT w_lifnr IS INITIAL.
CONCATENATE text-075 text-027 sy-datum sy-uzeit INTO w_line
SEPARATED BY c_uscore.
ENDIF.
st_document_data-obj_name = w_line.
st_document_data-obj_descr = w_line.
st_document_data-priority = 1.
st_document_data-obj_prio = 1.
ENDFORM. " document_data
*& Form packing_list
text
--> p1 text
<-- p2 text
FORM packing_list.
CLEAR w_lines.
DESCRIBE TABLE tbl_err LINES w_lines.
READ TABLE tbl_contents_txt INDEX w_lines.
tbl_packing_list-head_start = 1.
tbl_packing_list-head_num = 1.
tbl_packing_list-body_start = 1.
tbl_packing_list-body_num = 1.
tbl_packing_list-doc_type = 'RAW'.
APPEND tbl_packing_list.
tbl_packing_list-head_start = 1.
tbl_packing_list-head_num = 0.
tbl_packing_list-body_start = 2.
tbl_packing_list-body_num = w_lines + 1.
tbl_packing_list-doc_type = 'CSV'.
tbl_packing_list-obj_descr = 'Error_Attachment'(060).
IF NOT w_lifnr IS INITIAL.
tbl_packing_list-obj_name = 'Idoc Number is'(072).
ENDIF.
tbl_packing_list-doc_size = 255 * ( w_lines + 1 ).
APPEND tbl_packing_list.
ENDFORM. " packing_list
</b>
Thanks
Manju. -
Error handling limitations in XI3.0 SP11 when using IDOC's
Backround: Sending IDOC's from XI to a 6.20 SAP system with ALEAUD turned on.
We have found a couple of limitations with XI 3.0 SP11 regarding error handling and are wondering what other XI Developers are doing to work around them:
1) Unable to generate Alerts from global Alert Rules (PMI) in a BPM
2) Unable to handle IDOC negative acknowledgments in a BPM
3) Unable to generate Alerts from Alert Rules (PMI) for negative IDOC acks when NOT using a BPM
So far we are designing around these issues by using deadline monitoring steps in BPM's to handle IDOC posting errors and raising an Alert (the beauty of this workaround is that the BPM will automatically continue when the IDOC data is corrected and posted), and for non-BPM interfaces the errors must be handled in the receiving SAP system.
We have sent these issues in to OSS but the replies have come back stating that it is 'by design'.
Thx,
Jason.Did you get any better solution now?
Regards
Mike -
Regarding Error handling and customisation in RFC, Idocs and Proxy
Hi,
I wanted to compare RFC, Proxy and Idocs on the basis of the amount of customisation required in ECC when sending data from ECC to XI using the above stated means and also the error handling provided in these methods.
Please let me know in detail if possible.
Regards,
SampadaHi ,
Check this blog to know when to use which adapter:
/people/ravikumar.allampallam/blog/2005/08/14/choose-the-right-adapter-to-integrate-with-sap-systems
we use proxy in sap 6.0 version or higher.
Basically used for adapter less communication
& very high volume of data has to be transfered.
Step for Configuration fo IDOC in R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
In SLD System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name.
Regards,
Vinod. -
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 AMHi,
Have a look
Outbound IDoc Error Handling via Workflow
Outbound idoc error handling through workflow -
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 -
Error handling problem with outbound idoc status 02 and XML HTTP Port
I set up an ALE scenario to send master data out of SAP via an XML HTTP port. All goes well until the idoc receives error 02.
It looks like idocs in this error status with the use of an XML HTTP port can not be reprocessed via the standard SAP techniques. Program RBDAGAIN takes them out of the list for reprocessing (even though the connection is back up and running).
Is there any solution to still use the standard ALE error handling ?Hi Karin,
Looks like based on note 701597, you can only reprocess these idocs manually via a workitem. I qouted the relevant text below:
3. Error handling with status '02':
An HTTP IDoc in status '02' should not automatically be sent once again.
Up to now, the RBDAGAIN report was used to resend incorrect IDocs.
However, this report was adjusted and now deletes all IDocs in status 02
to be routed to a HTTP port from the list of selected IDocs. IDocs to a
HTTP port in status '02' should only be sent manually via a work item.
Regards:
Rex -
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,
VinothHey 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 -
Idoc/ALE error handling, send to external email
Hi all,
I'm developing an IDoc inbound interface for purchase order create using PORDCR1. For the error handling functionality, I need to send an external email describing all of the validation error happened in user-exit EXIT_SAPFKCIM_002. Please kindly tell me how to cater the functionality. I won't use workflow because the error handling can't describe all the error, it just displaying the first error encountered. I also don't want to create any custom object since message type PORDCR1 is available. I think creating a custom FM is a possible way, but if there is another way, please tell me how.
Thanks,
TeddyHi Teddy,
A custom FM is the easiest and simple way.There may be other ways.
Regards,
Atish
Maybe you are looking for
-
I purchased this Ipod two years ago. I was using it in a docking station and got along quite well. Now I cnnot use it withou running a cord from the ipod to the station. Anyone help me?
-
My cellcom line doesn't work with my iPhone here in Israel, why? Is there any way I can solve this issue?
-
I need an AC Adapter for Satellite P300
I'm from Canada first off, I know this is a Europe forum... Ok, so my question is my AC stopped working and it's not covered under the warrenty, So I was hoping that you guys could put me in the right direction of getting an adapter cheap, whether of
-
Question about dataset in demo photo Gallery V.2
So I'm going to try and be as specific as possible. I'm trying to use the code on the Spry demo page to create a gallery and I'm stuck on how to get it to load my .xml files instead of the china, egypt, and paris files. The only reference I see to a
-
Calling Web Dynpro-Model of Application-Service doesnu00B4t work.
Hello! I have created a Composite Application with Entity- and Application-Services. I have also created the WebDynpro-Model and use it in another WebDynpro application to call the services. I have a Entity-Service 'PollCatalogue' and an Application