Job cancelled while processing inbound IDOcs

Hi All,
we are sceduled job in background processing mode for the program RBDAPP01(Inbound Processing of Idocs),
but job was cancelled due to RAISE_EXCEPTION.
if i cheked in ST22 it is showing as
""The termination occurred in the ABAP program "SAPLMCS2" in "MC_SEND_MAIL".
The main program was "RBDAPP01 ".
The termination occurred in line 108 of the source code of the (Include) program "LMCS2U09""
i didn't understand why it is cancelled ?
can any one pls help me ....
regards,
suresh

Hello,
Sometimes if the Data / Right Data is not present in the IDoc, then it would not help the Standard SAP Program / Programs / Function Modules to fill-in Certain Field Symbols due to which the Short Dump might have occured.
Check the IDocs and try executing the Job again.
Thanks and Regards,
Venkat Phani Prasad Konduri

Similar Messages

Error while processing inbound Idoc (HRMDA_07) with FM IDOC_INPUT_HRMD

Hello,
I have a inbound Idoc of type HRMD_A (basistype HRMD_A07) which is processed by Function module (FM) IDOC_INPUT_HRMD with proofing. After processing an Idoc the status Monitor for ALE messages (BD87) tell me that my Idoc has status 53, which should be the result i would like to have.
Unfortunately when i go to transaction PA20 and check the infotypes, i see that infotype 0302 isn't created. When analyzing this problem i see that during the processing the Infotypes are posted with HR_MAINTAIN_MASTERDATA (dialog mode is 0 and luw_mode = 0 from include LRHA2F02 FORM save_pa_pb_infty) When this is done for infotype 0302 sy-subrc <> 0 the message is A complex application error has occured. This error message is placed in Export parameters
Return and Return1
of HR_MAINTAIN_MASTERDATA. When the program returns to the calling Form it checks if there is message of type E in HR_RETURN (see below) :
CALL FUNCTION 'HR_MAINTAIN_MASTERDATA'
          EXPORTING
            pernr                          = ins_objects-objid       "#EC DOM_EQUAL
            actio                           = 'INS'
            tclas                           = tclas
            dialog_mode               = dial_mode
            luw_mode                  = '0'
            no_existence_check = $cross
            no_enqueue              = $cross
          IMPORTING
            return1                       = return
            hr_return                    = hr_return
          TABLES
            proposed_values    = proposed_values.
        REFRESH proposed_values.
     IF hr_return-msgty = 'E'.                           "note 984409
      CLEAR protocol_error.
      protocol_error-msgty = hr_return-msgty.
      protocol_error-msgid = hr_return-msgid.
      protocol_error-msgno = hr_return-msgno.
      protocol_error-msgv1 = hr_return-msgv1.
      protocol_error-msgv2 = hr_return-msgv2.
      protocol_error-msgv3 = hr_return-msgv3.
      protocol_error-msgv4 = hr_return-msgv4.
      READ TABLE t_hrobjinfty WITH KEY objid = hr_return-pernr
                                       infty = hr_return-infty
                                       subty = hr_return-subty.
      protocol_error-segnum = t_hrobjinfty-segnum.
      protocol_error-routid = 'create_prf_pa_pb_object'
As mentioned above, the error message is only placed in the parameters Return and Return1 and not in HR_RETURN.please read the first reply

Hi,
I think you have preety much done from your end itself .
Could you please tell me what you got in this parameters:
     protocol_error-msgty = hr_return-msgty.
      protocol_error-msgid = hr_return-msgid.
      protocol_error-msgno = hr_return-msgno.
      protocol_error-msgv1 = hr_return-msgv1.
      protocol_error-msgv2 = hr_return-msgv2.
      protocol_error-msgv3 = hr_return-msgv3.
      protocol_error-msgv4 = hr_return-msgv4.
It may help us to track down the issue in more better way .
Thanks!

Processing inbound Idoc ORDERS03 with status 51

Dear ALL
While processing inbound idoc with message type ORDERS03 i am getting a status 51 with below erros
I have maintained the data under VOE2 & VOE4 but not got the solution. We are on SAP ECC6 Version
Customer 1100 is customers purchase organization
Partner no 1109 is customers plant
VKORG, VTWEG, SPART cannot be determined for customer 0000001100 , vendor REN15D
Message no. VG204
Terms of payment in IDoc E1EDK18 have been transferred: Check data
Message no. VG202
Partner number 1109 for customer 0000001100 , partner function WE does not exist.
Message no. VG140
Regards
Arun

Hi,
Vendor 100002 is not maintained in your system. Maintain the same or use some other vendor which is there in your system.
You should be able to post the document.
Regards,
Lalit Kabra

EDI / IDoc : While posting inbound IDocs, IDocs gets into status 56

EDI / IDoc : While posting inbound IDocs, IDocs gets into status 56 with message "EDI: Sender port in control record is invalid".
But if I reprocess the same idoc without doing any changes using RBDINPUT and select radio button to processs idocs for status 56, then it gets successfully posted.
So not getting why this stucks for the first time.
Thanks in Advance..........

i fixed this my self

How to process inbound idoc in R/3 with status 75 - idoc received via qRFC?

Hi gurus,
we are using EOIO for source to R/3, and all the idocs a received in r/3 with this status. But they can't be processed from BD87. How to process these?
Thanks,
Olian
Edited by: Olian Saludew on Sep 11, 2008 11:44 AM

Hi,
Idocs Works on tRFC Queues.
Check this Report to Process Inbound Idocs with Specified Status.
RBDAPP01
Regards
Seshagiri

Process Inbound IDOC

Hi there,
I have an IDOC file store in the application server, I would like to know if exist a funcion module to read this Idoc and process it as inbound message in SAP.
Thanks in advance
Alexis

Hi,
You can use standard program RSEINB00 to process inbound IDoc file.
Regards,
Ferry Lianto

I am trying to process inbound idoc

I am trying to process inbound idoc it will be showing error i.e
51-Purchasing document 8000200 not selectable
Pls give me advise

Hi,
You inbound FI idoc is containing Purchase order no, which is not existing in receiving system, that's the reason you are getting this error.

B1358 error while posting inbound idoc with a FM

Hi
We are trying to post and inbound IDOC with the help of an rfc and eventually creating an invoice from a bdc wrapped in the RFC
The idocs are successfully pushed to R/3 while they are not getting posted and the error code in we02 is as follows
No status record was passed to ALE by the application
Message no. B1358
Diagnosis
The application failed to return a status record to the ALE layer after the IDoc was processed.
This is due to an error in the application function module which processed the inbound IDoc.
Procedure
If you wrote the application function module yourself, you need to change the program.
If the function module in question is a standard application function module, you should consult SAP.
Note: we are using a custom function module
regards
krishna

Hi Krishna,
I assume that your function module processing the IDOC does not follow the ALE/IDOC processing rules.
Please check out the programming guidelines in the SAP Online Help under:
<a href="http://help.sap.com/saphelp_nw70/helpdata/en/78/21758051ce11d189570000e829fbbd/frameset.htm">http://help.sap.com/saphelp_nw70/helpdata/en/78/21758051ce11d189570000e829fbbd/frameset.htm</a>
Important are the parameters and tables that need to be returned, containing the correct IDOC processing status. Please take the IDOC processing quite serious in regards to complete Logical Unit of Works.
Best regards,
SIlvia

Processing Inbound IDOC's from FTP.

Hi,
I have an issue where IDOC's (WPUBON01 & DEBMAS01) are being saved in ftp folder and once these IDOC's are saved, we have to process it in SAP System, i would like to know the simple way of having these IDOC's processed in Unix based SAP system as the IDOC's will be coming in at Real time evey minutes or Seconds.
is there a way to do it with out ABAP process i mean just by using the Unix Scripts or by triggering the SAP background job.
Thanks in Advance.

Hi,
for testing purposes you can trigger inbound IDoc processing in transaction WE16. Otherwise you can schedule program RSEINB00 to periodically import IDoc into system. You can make a copy of that program and made changes if you need to add some extra logic.
Cheers

How to cancel/reverse an inbound idoc?

I wish to cancel then reverse an inbound idoc specifically, WPUUMS01 (sales data compressed) as if the idoc never existed and wasn't processed in SAP.
The said idoc was already processed in SAP and the material and billing documents (in WPER) were already created.
Hope someone could help me on how to go about this.
Thanks!

hello ,
may be u can try to look in for the concerned bapi and then delet tht record via tht bapi for e.g say to delete a create sales order demo code is -
DATA: T_RETURN LIKE BAPIRET2 OCCURS 0 WITH HEADER LINE.
DATA: BAPISDH1X LIKE BAPISDH1X.
PARAMETERS: P_VBELN LIKE VBAK-VBELN.
SET THE DELETION FLAG
BAPISDH1X-UPDATEFLAG = 'D'.
CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
EXPORTING
salesdocument = P_VBELN
order_header_inx = BAPISDH1X
tables
return = T_RETURN
COMMIT WORK.

Error while posting Inbound Idocs-"EDI: Partner profile not available"

Hi,
I am getting the error "EDI: Partner profile not available" Status -56 while creating inboud Idocs.
I have done the following steps so far
1.Created IDOC basic Type and Message Type. (Custom)
2. Created process code to process the IDOC.
3. Use the FM IDOC_INBOUND_WRITE_TO_DB to create the inbound IDOC.
4. Use the FM IDOC_START_INBOUND to process the IDOC.
Is ther anything else that i have to do inorder to post the idoc sucessfully.
Thanks in advance
-Nishant
Edited by: nishant patel on Nov 13, 2009 10:35 AM
Edited by: nishant patel on Nov 13, 2009 10:41 AM

Hi,
Check in WE20 if the partner profile is configured for the idoc type and the message type. That might be the cause of the error.
Also make sure the same partner profile details are sent to the control record. Partner profile details are stored in the table EDP13.
Hope this helps
Regards
Shiva

Job cancelled While loading data from DSO to CUBE using DTP

Hi All,
while i am loading data frm DSO to CUBE the job load is getting cancelled.
in the job overview i got the following messages
SYST: Date 00/01/0000 not expected.
Job cancelled after system exception ERROR_MESSAGE
wt can be the reason for this error as i have successfully loaded data into 2 layers of DSO before loading the data into the CUBE

hi,
Are u loading the flat file to DSO?
then check the data in the PSA in the date field and replace with the correct date.
i think u r using write optimised DSO which is similar to PSA it will take all the data from PSA to DSO.
so clear the data in PSA and then load to DSO and then to CUBE.
If u dont need a date field in CUBE then remove the mapping in transformation in cube and activate and make DTP activate and trigger it it will work.

Error in number range while testing inbound idoc via we19

hi all,
i have done all configurations but while testing the inbound idoc via we19 i am getting an error 'error in assigning number to idoc'..i checked and found that the number range object for idoc is edidoc in it number interval is defined from 1 to 99
i dont think that anything is wrong with the number object..
Can u tell me how dow i eliminate this error?

Increase Higher limit the reason is when you look at current idoc number ( This idoc number already exists ) ,it will not create new idoc number.
System will get the number from SNRO Based on IDOC Object.
Just look at EDIDC and see the current idoc number.
Simple example :
I have one number - 100 ,it is already exists in database,if i insert same record to the database ,did system will accept ?
Thanks
Seshu

Process Inbound IDoc WPUWBW

Hi experts,
I am quite new in SAP, and I am finding a lot of problems trying to make probably the easiest things.
My problem is this:
I am trying to process an inbound IDoc type WPUWBW, and it has status 53, but when I try to view it in the workbench, the system does not recognize the IDoc as good movement type and I can not find the way to insert in one field of the IDoc via we19 transaction the transaction type.How can I make it?And in which field can I insert the transaction type??
Thank you very much in advance!
Best regards,
Ander

Hi Praveen,
First of all thank you very much for your help.
My problem continues, because I am not able to find the field inside the WPUWBW IDoc to insert the transaction type, in my case 1502. But I can find the field to introduce the goods movements type, in my case 7004 in E1WPG02 segment, movement type line.
Thank you very much.
I wait your reply.
Best regards,
Ander

Error in re-processing inbound idocs of status 51

Hi
We are facing problems in reprocessing inbound idoc from BD87 transaction
We have an inbound process code 'STA1' which is pointing to a standard task 'TS30000206'. we have an errored inbound idoc(status 51) of message type 'STATUS' ( standard status change idoc pointing to process code STA1 for a valid port. Whenever we try to process it using BD87 transaction, we are getting errors B1033-'No function module for input process code STA1'.
We dont understand what we were missing. When we try the same for a process code which points to a function module, BD87 reprocesses it correctly.
We tried adding an entry in BD67 with an inbound function module 'APPL_IDOC_INPUT1'. Note that we still had the process code pointing to the same task. This time BD87 reprocessed idoc, but gave 51 again saying that 'Function module not allowed: APPL_IDOC_INPUT1'.
Any pointers or help in this regard will be highly appreciated.

Hi,
Please check IDOC TYPE, MESSAGE TYPE & PROCESS CODE and also check the we30, we42. & try BD87 reprocess of an IDOC.

Job cancelled while processing inbound IDOcs

Similar Messages

Maybe you are looking for