'Idoc has wrong status'

Hi SDN,
Good morning to all of you. I came infrom of you with a small quaery related to IDOC. My query is sales order is going to be created via IDOCs (Which came from XI) through FM IDOC_INPUT_ORDERS. While creating the SO we are generating the mails to users if any errors will be encountered, but here every thing is working fine and some times it is generating mail with the message 'Idoc has wrong status' for successful also. Not for all only for few sucessfull SO's it is generating mail. Please suggest me any configuration i need to check or any thing else. Please suggest me....Appriciate your valuable suggestions......Waiting for your valuable reposnse.....
Regards,
Kumar

Hi Santosh,
Thanks for your immediate response. It is giving me status 53.
Regards,
Kumar

Similar Messages

IDOC STATUS - 51 " IDOC HAS TEST STATUS"

I am trying to simulate store orders using WVFB transaction. Idoc is getting generated , but with the staus : 51 " IDOC HAS TEST STATUS". In WPER its not showing any erros. Idoc is - ORDERS05.
Pls let me know, from where its getting test flag.

Rajaram Karthigayan
The IDOC is getting the status 51 saying that an error has occurred assigning the data in the segment.
This segment is a MANDATORY segment.
IDoc status 51 - Application document not posted,
Follow these link
http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a6743507d11d18ee90000e8366fc2/frameset.htm
http://eai.ittoolbox.com/groups/technical-functional/seebeyond-l/idoc-status-51-error-has-occurred-assigning-the-data-in-the-segment-375696
Thanks
Sandeep sharma
PS: if helpful please reward points

PAYEXT IDOC has recurring statuses

Hi
We are using the standard message type PAYEXT to send IDOCs to banks for payments to vendors. The IDOCs are set to be created via F110 payment run. Then a periodically scheduled job for RSEOUT00 sends the IDOCs out. When the IDOCs are created via the payment run, they are set to status 30 (Receiver exists , No filters , No conversion , No version change), which has the user's username. When BD87 runs the IDOC status changes to 03 (IDoc written to file), which has the SAP_BATCH username (the username with which the BD87 was scheduled with).
This system has been working fawlessly for over 6 yrs.
Just one day this month, all the IDOCs that were created for PAYEXT message type, began with had the correct status of 30 & then 03 with the correct user-ids and statuses as above & for some strange reason again a status 30 (with SAP_BATCH username and error status: Could not write IDoc to file) and 03 (SAP_BATCH username and success status: *IDoc written to file*) and then continued as usual. The difference in the first & second status 30 is 3 secs. This has caused duplicate payments to the Vendor.
This whole situation was reset when 1 IDOC failed and everything was back to ususal.
We do not have any custom code to set any statuses. We have posted this to SAP & have been waiting for 2 days to respond.
Any help will be greatly appreciated.
Thanks
Ashwini

Hello,
In my case Inbound - IDOC was generated & process in one thread. there was bug in code which was creating another thread to proces same IDOC.
One thread was processing IDOC with correct status of 53, another was trying to process IDOC it was putting status of 51 on same idoc
Both statuses were on same IDOC.
The possibility of creating new idoc hapens when system try to create IDOC.
In your case, It's just processing of IDOC which happens two times. so new IDOC will not be created.
Regards,
Sameer Desai

No authorization for changing Customer Centrally- Idoc in Error Status 51

Hi Experts,
We are implementing MDM for one of the client.
The client runs a modification scenario in MDM for Customer Master.
He modifies a customer record in MDM and this record is transfered from MDM to ECC via PI through Idocs.
We are using standard Idocs for Customer Master which is DEBMDM
There are 2 Idoc's generated in ECC by PI from DEBMDM as DEBMAS and ADRMAS.
ADRMAS Idoc is succesfull in ECC and the corresponding record is modified.
Now the issue is that the corresponding DEBMAS Idoc goes into Error 51.
The Error details is as below:
                                                                                No authorization for changing vendor Centrally
Message no. F2326
System Response
You cannot access the requested data.
Procedure for System Administration
If necessary, include an entry in the user's authorization profile for
    the authorization object and parameters specified below.
Authorization object:
o   F_KNA1_APP
Parameters:
o   Activity: 02
    o   Application authorization : *
We gave the respective authorization object to the RFC User ID used in PI RFC created to connect to ECC.
Also we have given the user id Tcode authorization like XD01/02/03.
But this error still persists.
Request to throw some light on this.
Cheers
Dhwani

Check these threads
[Re: IDOC STATUS - 51 " IDOC HAS TEST STATUS|IDOC STATUS - 51 " IDOC HAS TEST STATUS";
[Error Inbound IDoc - Status 51|Error Inbound IDoc - Status 51;
thanks
G. Lakshmipathi

Production order confirmation thru IDoc , IDoc has been processed twice

Hi Experts,
Good day.
I have a problem with my Production orders confirmation using IDoc automatic processing.
I have an IDoc that has successfully confirmed a Production order, the Idoc has a status of 53.
However, after a month, the Idoc has been used again on a different Production order confirmation, and the IDoc resulted again to status 53.
Could you kindly confirm if this a SAP standard behavior or an error? If this is an error, is there any available SAP notes that I can use.
Here is the spec of our system:
ECC 5.00 - SP SAPKH50015
Please kindly provide us your idea on this.
Thank you very much.
Kind regards,
Rosalinda Ines Aben
PP Support

Hi Rosalinda, i have the same problem. You found some solution ?
Thanks a lot !!!.
Federico Cicerchia

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

One of the IDOCs has an specific error message (status 51 Idoc not posted)

Dear Experts,
ple. provide the solution for my issue.
In my list of compaines one of the company had an external partner(warehouse) who takes care of their products.
Communication between that external partner software and my system(PVS) is happen through IDOCs.
But one of the IDOCs has an specific error message ( status 51 and status text : Specification for units and quantites containe error),
acctually we are receiving picking meterials from the external system to my system.
I can able to see the Inbound Idoc and status, I am not able to see the Outbound Idoc, then how can I test why its happening this problem and I how can I give the analysis properly please suggest me.
Thanks in advance
Suresh

Suresh,
Welcome to SDN. Adding to Jürgen Comment, Just double click on status 51 (at node), then in next screen there will be one information (long text) button, just click on it. Some times it will give good details about the error. the information can also suggest direct trasaction to correct the customization, some times!
try for ur case.
Reddy

IDOC 51 status "Serialization: A more recent IDoc has already been processe

HI all,
i got 7800+ idocs with status 51, and the message is...
Serialization: A more recent IDoc has already been processed.
why it happens?
how to avoid this error?

For ALE use below link.
http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a66c9507d11d18ee90000e8366fc2/frameset.htm
ALE IMG (transaction SALE)
   Model and Implement Business Processes
    Configure Master Data Distribution
      Set-Up Data for Sending and Receiving Serialization
        Serialization by Message Type
Thanks,
Narayan

How to delete a IDOC which has the status 51.

Hi,
I am trying to delete the IDOC(status 51) from WE02. But not able to delete out, because set delete indicator is disable mode.
Please let me know is there any way to delete the failure IDOC which is status 51.
And also let me know how to findout the user or usergroup who receives the mail through WORKFLOW when an IDOC was failed.
Thanks,
Vinay.

hi vinay,
Tx. WE11
Prg. -- RSETESTD
In the abovesaid program the following fm is used for deletion of idoc. But before the deletion of idoc`s there are several other procedures to be followed. For further reference, explore the abovesaid program.
CALL FUNCTION 'EDI_DOCUMENT_DELETE'
        EXPORTING
          document_number        = gd_edidc-docnum
        EXCEPTIONS
          idoc_does_not_exist    = 1
          document_foreign_lock = 2
          idoc_cannot_be_deleted = 3
          not_all_tables_deleted = 4
          OTHERS                 = 5.
      IF NOT syst-subrc IS INITIAL.
        MESSAGE ID syst-msgid TYPE syst-msgty NUMBER syst-msgno
            WITH syst-msgv1 syst-msgv2 syst-msgv3 syst-msgv4.
      ENDIF.
This is the code found in the abovesaid program.
Still if you`re not satisfied with my answer, revert back to me with my server details.
Else reward points.
Regards
GUDURI

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

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

IDoc-to-File: Status=processed succesfully but file is not always delivered

Hi Experts,
I have a problem with a IDoc-to-File scenario. I generate an IDoc and send it to the XI-System. Afterwards a XML-file is created which should be transmitted to a filesystem or to a ftp server (I tested with both). In the SXMB_MONI the Message has the Status "Processed Succesfully" and the Acknowledgement-Status "Still awaiting acknowledgement". The problem is that not all files arrive the destination succesfully. sometimes they arrive and sometimes not. and always the same status in the sxmb_moni.
if a message not arrived the destination, in the message monitoring in the runtime workbench there is the status "To Be Delivered". If one Message has the status "To Be Delivered" the following messages get this status too.
the communication-channel-monitoring says that "the communication channel is correctly configured and started"
Can you help me? I don't know where the problem is. could it be that the adapter-engine has some problems?
Thanks and best regards
Christopher

hi,
I clicked on details in the message monitoring but the fields "error category" and "error code" are empty. Then I checked the audit log in the message monitoring. there are the following three entries
2008-01-28 14:08:56 Success Message successfully received by messaging system.
2008-01-28 14:08:56 Success Using connection File_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2008-01-28 14:08:57 Success Message successfully put into the queue.
and here the audit log of a message which could be transmitted correctly:
2008-01-28 10:33:10 Success Message successfully received by messaging system.
2008-01-28 10:33:10 Success Using connection File_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2008-01-28 10:33:10 Success Message successfully put into the queue.
2008-01-28 10:33:10 Success The message was successfully retrieved from the receive queue.
2008-01-28 10:33:10 Success The message status set to DLNG.
2008-01-28 10:33:10 Success Delivering to channel: FILEPORT_TO_PICC
2008-01-28 10:33:10 Success MP: entering
2008-01-28 10:33:10 Success MP: processing local module localejbs/CallSapAdapter
2008-01-28 10:33:10 Success File adapter receiver: processing started; QoS required: ExactlyOnce
2008-01-28 10:33:10 Success File adapter receiver channel FILEPORT_TO_PICC: start processing: party " ", service "X22_PICC"
2008-01-28 10:33:10 Success Write to file "/tmp/xi/PICC/INV_5075_4000102108_20070109_103310.XML" as binary, size 410 bytes
2008-01-28 10:33:10 Success File processing complete
2008-01-28 10:33:10 Success MP: leaving
2008-01-28 10:33:10 Success The message was successfully delivered to the application using connection File_http://sap.com/xi/XI/System.
2008-01-28 10:33:10 Success The message status set to DLVD.
2008-01-28 10:33:10 Success Acknowledgement creation triggered for type: AckNotSupported
2008-01-28 10:33:10 Success Acknowledgement sent successfully for type: AckNotSupported
can you say me where the problem is?
thanks and regards
chris

ERROR B191 - IDoc has its own logical system as receiver

I everybody, i'm tryng to execute a package to charge a ODS from another ODS (Datamart) but the process ends with the error "IDoc has its own logical system as receiver", can you help me with is?
What should be the reason for this error? What can i make to solve it?
Thanks to all

Hi Reddy,
please let me know how did u solve this issue, even i have the same requirement and am gettign status 29.
Thanks
Rakesh

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

Message has error status on outbd side

Hi,
I am doing File to IDoc scenario, in SXMB_MONI i am getting the following error "Message has error status on outbd side". I am not using BPM and this interface was working fine earlier .
Any clues!!!!!!!!!!
Regards
Swatantra

Hi Vijay,
Cross check whether you have done these:-
SLD-
1) Create a Product/Software Component
2) Technical System pointing to R/3 system
3) Business System for the above technical system
In the Repository
1) Import the Software component created in the sld
2) Create a namespace,
3) import the idoc and then create sender data type/message type etc and mapping
4) Mapping Rules is depends on the requirement
In the Directory
1) Create a Scenario /import the business system
2) Create Receiver/Interface determination
3) Create communication channels for sender and receiver
4) Sender Agreeement and Receiver Agreement.
Then the file adapter configuration is depend on the input file format.
Also you need to have Logical destionation created in the XI , and the IDX1 entry
In R/3 Port, Partner profiles etc should be created
Have a look into this document~
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
While doing an File -> XI -> IDoc scenario, The Points to noted are:
1. You dont need a DT, MT or a message interface for the IDOC as it itself acts as the Message Interface.
2. You import the IDOC and use the same in your mapping.
3. In this configuration note that you will need a sender agreement for the file.
4. In this configuration note that you will also need a receiver agreement for the IDOC.
For any File -> XI -> IDoc scenario ref:
/people/anish.abraham2/blog/2005/12/22/file-to-multiple-idocs-xslt-mapping
Hope this helps.
Regards.
Praveen

'Idoc has wrong status'

Similar Messages

Maybe you are looking for