Reprocessing Idoc's with 51 and 54 status.

Hi Gurus,
My client wants to reprocess Idocs with status 51 and 54 by Batch job.
Is there Any program which can reprocess both status 51 and 54.
After the Idocs get reprocessed it should update the Shipment end in the Shipment document.
Thanks in advance!!!
Regards,
Aslam

Hi,
program to reporcess depends on status. Run report RBDINPUT. Here when selecting status 51 you will be redirected to report RBDMANI2 (as stated by Génia). For status 54, you can reprocess idocs manually with tcode we19.
Regards,
JM

Similar Messages

IDoc Control Record and Status Record Code, where is it!!!

Hi,
Where can i see the code for generation of control record and status record of IDoc.
   Thanks in advance for your answers

hi ,
1.first create an segment with the fields u want tcode we31 relase it .
2. create an idoc and assign segment to it tcode we30.
3.crate a message type tcode we81
4.assign that message to idoc tcode we 82.
do the ale configarations .
now u can write the code in our sender system
*1.     Create parameters/select-options for input data. i.e., message type, logical system.
parameters : p_mestyp like edmsg-msgtyp default 'ZKKUMSG',
             p_logsys like tbdlst-logsys obligatory.
*2.     Create Data objects for control record, data record and database table.
data : c_segment like edidd-segnam value 'ZKKUSEG',        "Data record (IDoc)-Segment type
       c_idoctp like edidc-idoctp value 'ZKKUIDOC'.            "Control record (IDoc)-Basic type
data : begin of i_tab occurs 0,
          ZKSNO   like ZKSTD-ZKSNO,
          ZKSNAME like ZKSTD-ZKSNAME,
       end of i_tab.
data : w_itab like i_tab.
data : s_segment like ZKKUSEG.
data : i_edidd like edidd occurs 0 with header line.
data : i_control_record like edidc.
data : i_comm_idoc like edidc occurs 0 with header line.
*3.     Select the data from responding tables into internal table for a defined condition.
here you have take ur internal table
*select single zsno zsname from zkiran into corresponding fields of itab where zsno = p_sno.
*4.     create control record into internal table.
i_control_record-mestyp = p_mestyp.         "Message Type
i_control_record-idoctp = c_idoctp.         "Basic type
i_control_record-rcvprt = 'LS'.             "Partner Type of Receiver
i_control_record-rcvprn = p_logsys.         "Partner Number of Recipient
*5.     create data record into internal table.
*i_edidd-segnam =   c_segment.
loop at i_tab into w_itab.
s_segment-zksno    = w_itab-ZKSNO.                     "Application Data
s_segment-zksname = w_itab-ZKSNAME.
i_edidd-sdata     = s_segment.
i_edidd-segnam    = c_segment.
clear w_itab.
append i_edidd.
endloop.
*6.     Process ALE Service Layer using the function module MASTER_IDOC_DISTRIBUTE. It returns the corresponding IDoc No.s.
call function 'MASTER_IDOC_DISTRIBUTE'
exporting
    master_idoc_control            = i_control_record
tables
    communication_idoc_control     = i_comm_idoc
    master_idoc_data               = i_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.
endif.
*7.     Display Communication IDocs.
loop at i_comm_idoc.
write : / 'Communication IDoc No. is : ', i_comm_idoc-docnum.
endloop.
*8.     Commit Work.
commit work.
i hope this sample code help u .
thanks

IDOC - Projects / WBS and Status

Hi Expert
In my testing I find that only realesed (I0002) project travel througth the master system into the host system. Someone knows or has a list about the status of Project / WBS that the IDOCs takes to transfer by the master system???
Thanks in advance.

Hi Expert
In my testing I find that only realesed (I0002) project travel througth the master system into the host system. Someone knows or has a list about the status of Project / WBS that the IDOCs takes to transfer by the master system???
Thanks in advance.

Idoc failed with status 51 for Warning/Information messages

Hi All,
We are trying to create some Sales Orders with the help of Idocs. We are facing some problem as mentioned below.
1.There are some warning messages/information messages written in standard Sales Order User Exit USEREXIT_SAVE_DOCUMENT_PREPARE
2.As soon as the Idoc processing reaches any of these messages, it considers them as ERROR message and Idoc fails with the status as 51 which is not expected.
3.Also, I see that the Sales Order is saved with the data that has been passed in the Idoc.
Is this the standard behavior ?? (Or) Is there any EDI related configuration setting which can be used to suppress these kind of messages in Idoc Processing ??
Any help on this would be highly appreciated.
Thanks,
Babu Kilari

if your IDOC has status 51 then it is not posted, hence your sales order cannot be created from this IDOC. of course this error behaviour can be originated by the user exit.
please read OSS note Note 747631 - Some tips when testing idoc_input_orders

Reprocess Idocs

Hi,
To Reprocess Idocs in Outbound and Inbound, Should I use Tran: BD87 ?
What is use of this Report: RBDMANI2 ?
Thanks,
Srini

Hi,
Yes you have to use BD87 in order to reprocess the idocs.
Report rbdmani2 is used for manually processing the idocs.
But normally we use BD87 to reprocess the idocs as you have an option to select and reprocess the idocs from a list of idocs displayed. In the report you have to select the idocs yourself and reprocess it.
KR Jaideep,

Status for idoc to edit and reprocess it

Hi ,
I have a senario in which i need to hold the idocs for invoice coming as inbound in SAP .
Then once the PO is created editing the Invoice idocs to add PO by editing the IDOC and reprocess the same idoc and post invoice corresponding to PO in SAP and then change the status of that idoc to 53.
Can someone help me,with the status that i need to set to only have the idocs in SAP .
And then use those idocs to edit anf add PO and save it for status 32 (idoc edited).
And run some standard program to change the status to 53 with invoice created.
Thanks,
Richa

Richa,
You can set the idoc status to '51' in the customer exit of inbound idoc processing function module . Check the TABLES/CHANGING/EXPORT parameter of FM for something like EX_PROTT .. here you can pass the error message after checking the PO number ..
I'm not sure how are you linking Accounting document to PO.. you can use your logic to update the PO/set the idoc in error status in customer exit .
-Tushar Shukla

Reprocessing IDOCS with status 52

Hi all,
I facing a problem with IDOC status 52.
After correcting the error it had given, I want to reprocess it again.
Kindly tell me any report or transaction name for reprocessing IDOC with status 52.
Regards,
Rahul

Hi Rahul,
You can use the below Programs for IDocs Reprocessing:
RBDMANI2 : Reprocess Idocs manually
RBDMANIN : Posting of IDocs with Status 51
RBDMOIND : Outbound Idocs status 03->12
RSEOUT00 : For Processing 30 Status IDocs
RBDAPP01 : For Processing 64 Status IDocs
RBDAGAIN : Reprocess Incorrect Outbound IDocs
RBDAGAI2 : Reprocessing of IDocs after ALE Input Error
Regards
Aneesh.

Reprocessing IDOC with status 52

Hi,
I got status 52 for one of the IDOCs, I want to reprocess it . When I use BD87 & BD73, those are not working.
Please tell me any other way to process it.
Thanks & Regards
Vijay

Hi..Vijay,
There are already many threads with the same question.
pls search for your query before posting.
Eg:
Re: Idoc status 52 -> How to make it green i.e. 53
Reprocessing IDOCS with status 52
regards,
Padma

Issues with Reprocess Idoc

Hi all,
The developement for BOM interface is done.
it is working fine.But my client extented requirement like this
after processing IDOC , if there is any status 51 idocs available.
he will do reprocess from BD87. that time some part of code in FM needs to be triggered.
I am not able make Difference b/w first IDOC number and Reprocess IDoc number.
means for keeping conditon , i need one unique differenet between new IDOC and Reprocess IDOC.
Is there any point to know that properties.
thanks in Advance,
regards,
JBR

Hi,
Reprocessing a idoc would not create a new IDoc, only the status of the IDoc would be changed if the error with which it was already occuring has been modified.
Thanks
Krithika

IDOCs: possible to reprocess in "parallell" mode from status 51?

We loaded approx 5000 idocs via LSMW, and forgot to check the "Parallell processing" checkbox under the parallell proc-tab when initiating the "Start idoc processing"-step.
The idocs are in CRM, using IPC in the processing, and without the parallell option on, the IPC_RFC_DISPATCHER shuts down after approx 100 idocs. Remaining idocs fail (to status 51).
Now, I can start reprocessing of the idocs using BD87, but keep on getting the same error, thus I have to restart the IPC approx 50 times. I therefore want to start the reprocessing using RBDAPP01 with the parallell option checked, but RBDAPP01 it tells me it cannot find the IDOCs.
I guess I need to alter the status from 51 to 64 before running RDBAPP01.
For status change, I searched the forums, and found reference to program RC1_IDOC_SET_STATUS, but this seems unavailable in CRM. Is there another way?
Or maybe another way to invoke parallell processing from status 51?
I will appreciate any hints on this matter.

Hello Hans,
try to execute report RBDMANI2, to process the IDOCs in status 51.
Best regards
Stephan

IDoc created with status 03 checked via we02, but couldnt find in XI

Hi all:
Could you please do me a favor? implement a idoc to idoc issue. it has been created successfully .
as It is found that the idoc created with status of 03 -
data dispatched to port ok (rather than 12 dispatch ok). however, I couldn't find it via SXMB_MONI on XI, there must be something wrong . coudl you please give me a hint ?
Thank you very much!!!

hi,
you need to check transaction SM58 (remove the user from it) and F8
it might be the reason that you didn't create a port in IDX1 on XI/PI
but you will see that in SM58
Regards,
Michal Krawczyk

Info IDoc received with status 8 in BI but Data available in source system

Hello Experts,
I am loading Budget Period (attributes) into PSA in BI.
Budget Period data Loading Issue : No data available while loading. But source system ie ECC has data in that data source
Data source: 0PU_BDGTID_ATTR
This is full load.
I checked that whether I am making any mistake during data selection. I could not find any issue. Message while loading data into PSA (Yellow Traffic light)
No data available
Diagnosis
The data request was a full update.
In this case, the corresponding table in the source system does not
contain any data.
System Response
Info IDoc received with status 8.
Procedure
Check the data basis in the source system.
Already looked this thread and googled also.
Re: IDoc received with status 8.
Check points:
sm58 - NO issue
BD87 in ECC (RSINFO Idoc status: 03) -sucessful
BD87 in BI (RSINFO Idoc status : 53)
ST22 - NO issue
sm37 - Job is successful (I could see Idoc no in ECC source system in Job log)
I am not sure if I am missing any thing.
Thanks
Rana

Hi all,
I've got exactly the same issue with several extractors. I'm inialising the Master Data in a all new system, in the Quality the loads succeeded but in Prod it failed.
For instance with the basic DataSource "0FUNCT_LOC_TEXT", I've made the following test:
RS3 (R/3) - > 0 data
ST22 -> no short dump
WE05 (Idoc) - > everything is ok
I reactivated the Datasource in R/3 (RSA5) and then deleted it and replicated it in BW but the same issue occured.
Any ideas?
Thanks
jak

IDOC is Getting Fail with - 56 Status EDI Partner profile not available

Hi,
I am trying to Post invoice Data into IDOC on ECC Side.
My Scenario is File u2013 XI u2013 ECC(IDOC).
But It is Getting Fail with 56 Status u201C EDI: Partner profile not available u201C
On Control record I am getting this
Port                      BLANKKKKKKKKKK
Partner Number              CLNTDEC110      Logical system for Client
Partn.Type       LS                    Logical system
Function                                  BLANKKKKKKKKKK
Port                            SAPDPI
Partner number             CLNTSAMPLE
Partn.Type                      LS         Logical system
Partner Role                   BLANKKKKKKKKKK
My configurations are Like this :----
On ECC Side MY SID is DEC
On ECC side I have two logical system in CLNTDPI100 for PI
                         CLNTDEC110 for ECC.
I have Partner profile on ECC system on CLNTDPI100 logical system    - we20
Added message type in inbound side of partner Profile (INVOIC-INVOIC02)
ON SAP PI/ XI System MY SID is DPI
IDX 1 has Port name SAPDEC
On Message mapping EDI_DC40 is mapping with constants with below given value
<INVOIC02>
   <IDOC BEGIN="">
      <EDI_DC40 SEGMENT="">
         <TABNAM> </TABNAM>
         <DIRECT>2</DIRECT>
         <IDOCTYP> </IDOCTYP>
         <MESTYP>INVOIC</MESTYP>
         <SNDPOR>SAPDPI</SNDPOR>
         <SNDPRT>LS</SNDPRT>
         <SNDPRN>CLNTDPI100</SNDPRN>
         <RCVPOR>SAPDEC</RCVPOR>
         <RCVPRT>LS</RCVPRT>
         <RCVPRN>CLNTDEC110</RCVPRN>
      </EDI_DC40>
Regards
PS

Check the following :
in We 02 which partner number is displayed just in the posted IDOC -> 2nd coloum in the IDOC list .and verify if the
same you have in Partner profile. Actually this details comes from ECC business system's logical system name which you give in SLD.
in we 19 - take the error iDOC numner and open the IDOC ->click on the first line -> check entries as you mentioned
above sender port should be PI port not empty.you need to check the partner profiles properly
follow these steps
1. create a RFC destination of tyoe H for Pi system- 2. create a Port and assigen the RFC destination to it
3 create logical system for PI BD54 PICLNT001 say , 4 with the same name create a partner profile in We20
    in parter profile maintain the inbbound message parameters and add the PI port as receiver port in it .Give the basic type also .
now
for sender details in ur case PI : u have port (defined in PI IDX1),patner number (LS defined in ECC PICLNT001), parter type LS.
for receiver you have port defined (as above), partner number the logical system for ECC system.
in we 19 ,, edit the control record as above and go to the tab inbound processing and test the internal posting
it should work fine. in the adapte specific attribuet for receiver ECC system , maitain the same LS name , if any wrong entry is
there then change the LS in sld to poing to correct LS/
refer this
http://www.riyaz.net/blog/xipi-settings-in-r3-partner-system-to-receive-idocs/technology/sap/26/
Regards,
Srinivas

Idocs neding in 64 status and not processed further

Hi
We have inbound idocs of FIDCC2 message type, which are set to be triggered immediately. However we have noticed that sometimes (not always) these idocs are in 64 status and are not processed further. We have to manually reprocess them.
What could be the problem? Where should we start investigating?
Any help would be appreciated.
Thanks
Mick

I think the comment by Gautham Vangaveti is probably correct.
We hit the same issue occassionally. We have IDOCS as trigger immediately, but at the time they try to process, there are no available work processes which can handle the IDOC and they sit at status 64.
There is an oss note 1333417 which describes the situation
https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1333417
And unhelpfully suggests changing over to processing by batch job, which is not always appropriate.
It may be worth enlisting help from you Basis team to try and indentify if those going to status 64 are occuring at the same time each day, and maybe looking to see what other processes are running at that time. If the load on the system can be managed then the problem may go away, it did for us.
Otherwise, Basis may be able to increase the number of work process which may also resolve the issue.

Email on Idoc Failure with Status 56 64 68 69 70

We have standard inbound idoc processing for Basic Type : DELVRY01 and Message Type : DESADV using the function module IDOC_INPUT_DESADV1.
We currently have a requirement to send an email, when any of these type of Idocs fail with status 56, 64, 68, 69 and 70.
Where would be best place to provide this solution to send an email to a particular user when the Idoc fails with the above status?

Hello Saleem,
One approach would be to consider workflow based on object type IDOCAPPL. The start condition for the workflow could be the triggering of the event errorProcessCompleted. You could filter further by status and your message type (DESADV ) to only start the workflow for the errors that you mentioned. The workflow could then send an email.
You will need to verify the details for your own scenario.
Good luck,
Greg Kern

Reprocessing Idoc's with 51 and 54 status.

Similar Messages

Maybe you are looking for