Inbound idoc status 53 but nothing is updated in transaction level

Hi All
I am using we19 test tool to process routing idoc LOIROU02 (inbound processing)with some test values. After executing using standard inbound function module in R/3 4.7, I am getting a status 53 ( application document posted). This idoc is used for changing routings in PP module to allocate operations for BOM components in a master BOM material and Group. After processing, I went to routing transaction and checked but nothing is updated for operations. Do anyone knows why then the application document is successfully posted and giving status 53.
Any response is appreciated
Thanks

Hi All,
I am using inbound process code ED00 ( Display using workitem) , Identification TS30200088, with/o Ale service, Processing by task. I get the idoc in my business work place when I execute it through we19. From the business work place inbox, I got to edit idoc and End process for gettign the status 53. I am not sure why it is not updating the DB?
Thanks
Ricky

Similar Messages

I get a notice that says a security and stability update is recommended for Fire Fox 3.6.15. When I click to update a bar appears showing attempt to contact but nothing ever updates.

I get a notice that says a security and stability update is recommended for Fire Fox 3.6.15. When I click to update a bar appears showing attempt to contact but nothing ever updates.

Sometimes the updater gets in a funny state - Go to http://www.mozilla.org/en-US/firefox/new/ and download the full installer. Close Firefox and run the installer

CRMXIF_ORDER_SAVE_M02 Idoc status 53, but no transaction created in CRM

Hi,
Via transaction WE19, I have filled idoc CRMXIF_ORDER_SAVE_M02.
When I click on "standard inbound", the idoc is generated and get the status 53 which seems to be OK, but no Transaction is created in CRM.
Any idea ?
I've tried to fill more fields of the idoc structure but nothing changed.
Is there a step I am missing ?
What's the use of these fields in the idoc structure ?
APPL_SNAME
DATAX
Thanks for any help !
Aussie

Hi Aussie,
In transaction WE19 for the Idoc CRMXIF_ORDER_SAVE_M02.
It has no problem with data instead check the receiver Port, sender port, Partner No,
Partner type, role . If these didnot match then the data will not be reflected in CRM.
regarding APPL_SNAME: it is not relevant with the problem, its a structure of teh description.
Please see the ports.
have a nice day!!
receiver Port , sender port, Partner No, type, role Partner profile not maintained
Name of structure for the technical description
With regards,
Lakshmi Narayana

Error Inbound IDoc - Status 51

Hi,
i am new in working with SAP and I am trying to integrate an inbound IDoc type WPUBON via WE19 transaction, l solved all the issues related with ports and partner profiles(they were the first errors). But when I want to check if the process has been done well with the WE05 transaction I get two error messages, both of them with status 51:
The transactions for intermediate document 0000000000052247 could not be written
Message no. /POSDW/INPUT004
Document flow: Error reading model data of object relationship se
Message no. /POSDW/CORE028
Diagnosis
Error reading model data of object relationship se
System Response
The document links could not be updated.
Procedure
Contact your system administrator.
Procedure for System Administration
Check the format of the document links transferred to the POS Workbench.
Thank you very much in advance!!
Best regards,
Ander
Edited by: AAnder on Nov 3, 2010 11:46 AM

General process for a correct IDOC infrastructure is:
Create RFC destination --> SM59 (You can point to local machine for tests)
Create RFC port to process IDOC --> WE21 with the RFC create before
Create FILE port to process IDOC --> WE21
Create LOGICAL SYSTEM (BD54) --> IDOC2FILE
Define partner in WE20 with partner type "LS" --> WE20 ... add message
RECEIVER port ( created in WE21 )
FROM WE19 GENERAte IDOC with LOCAL SYSTEM as sender And FILE PORT as receiver
WE19 is FOR TEST...
tell me if you can understand, sorry for my english ....

Inbound Idoc Status

Hi Gurus,
I have Inbound Idoc which is working fine ,
but it's status is showing
51 Error: Application document not posted.
What does this mean, My Idoc FM is doing all it's part which required.
Can any please suggest me .
Thanks ,
Raj

Hello,
         What you've coded looks good. Another way of error Handling can be found as below. In the below Example, I am validating the Handling Unit Number got from the IDoc.
Validation for Handling Unit ID (EXIDV2 From IDOC) - Begin
CLEAR: i_vekp.
SELECT venum
         exidv
         exidv2
         FROM vekp INTO CORRESPONDING FIELDS OF
         TABLE i_vekp
         WHERE venum NE space AND
               exidv NE space AND
               exidv2 = wa_z1ctrlmm-exidv2.
IF sy-subrc EQ 0.
    DESCRIBE TABLE i_vekp.
    IF sy-tfill GT 1.
      CLEAR: wa_idoc_status.
      CLEAR: wa_vendor.
      READ TABLE i_vendor INTO wa_vendor INDEX 1.
      ws_c_flag             = c_x.
      wa_idoc_status-docnum = wa_idoc_control-docnum.
      wa_idoc_status-status = c_51.
      wa_idoc_status-msgty = c_e.
      wa_idoc_status-msgid = c_msgclas.
      wa_idoc_status-msgno = '004'.
      wa_idoc_status-msgv1 = wa_vendor-v_batch.
      APPEND wa_idoc_status TO i_idoc_status.
      CLEAR: wa_idoc_status.
      Here, I am not updating the IDOC_STATUS directly. Instead, I've taken one Temporary Table I_IDOC_STATUS and finally, after all the Validations are done & all the Statuses are updated in the I_IDOC_STATUS, I am updating the IDOC_STATUS Table at the end of the Function module as below.
IF Err_Flag = space.
    wa_idoc_status-docnum = wa_idoc_control-docnum.
     wa_idoc_status-status = c_53.
     wa_idoc_status-msgty = c_s.
     wa_idoc_status-msgid = c_msgclas.
     wa_idoc_status-msgno = '007'.
     append wa_idoc_status to I_IDoc_status.
else.
     wa_idoc_status-docnum = wa_idoc_control-docnum.
     wa_idoc_status-status = c_51.
     wa_idoc_status-msgty = c_e.
     wa_idoc_status-msgid = c_msgclas.
     wa_idoc_status-msgno = '004'.
     append wa_idoc_status to I_IDoc_status.
endif.
IDOC_STATUS[] = I_IDOC_STATUS[].
ENDFUNCTION.
This is how a typical Error Handling technique should be while processing a Custom Inbound Function Module. At any point in time during the Function Module, catching the Message, either Success or Failure is important otherwise, you may end up posting the IDoc with Status 51 or 62 or 64 Status which doesn't make any sense.
Thanks and Regards,
Venkat Phani Prasad Konduri

Idoc Status 53 but Applicaton document not posted message type PORDCR

Hi,
Need your help. I am using message type PORDCR and Basic type PORDCR04 to create Purchase order through inbound Idocs. I am getting correct status '53' Application document posted along with the new Purchase order number. When I am trying to see it in EKKO / or ME23N I could not see this purchase order.
Can anyone please let me know what could be the possible reason for document is not getting posted in in database but Idoc status is correct.?
Thanks in advance.
Regards,
Deepak

check SM13 and ST22 to see if there are any errors there

Inbound IDOC status is strucked at 64

Hi,
My rerequirement is as follws.
Inbound IDOC process:
Through inbound IDOC i have to create the new sales orders and need to change some information to existing sales orders means 2 cases.
1) Create new sales order
2) Change existing order.
Iu2019ve generated two example IDOCs from order interface
one for an u2018order addu2019 and one for an u2018order changeu2019.
The times each IDOC reached each status are shown below:
IDOC 1677672 u2013 Order ADD
Status: 50 Started         Time:    09:54
            64 IDOC ready               09:54
            62 Direct Call                 10:39
            53 Order Created           10:39
IDOC 1677684 u2013 Order CHANGE
Status: 50 Started         Time:    12:50
            64 IDOC ready               12:50
            62 Direct Call                 12:50
            53 Changes on Y-table   12:50
Can anybody explain why the first IDOC had to wait for the scheduled
u2018IDOC PROCESSINGu2019 job to run, before it moved from status 64 to 62. But
the second IDOC appears to have been processed automatically without
waiting for the next run of the scheduled job?
Obviously, the u2018automaticu2019 processing of the change IDOC is the way we
would prefer it to work all the time).
Can any body explain in first case why it's taking time and in second case it's processed immidiately.
Regards,
Janardhan

Hi,
I believe you are using two different message types for this purpose. One to create order and one to change order. Did you check the partner profiles for these? May be partner profile(WE20) for creating order is set as "Collect Idocs" whereas the partner profile for the message type to change order is se as "Trigger immediately".
Hope it helps.
Regds,
Rudra

Hii Inbound idoc status

Hii
i have a requirement where when an Zidoc is being process if a certain condition is met we should insert in a custom table and not process the IDOC
What status should i put the IDOC in a sort of stand by process so that the user can process it later on with either BD87 or a FM IDOC_INPUT??
I have try putting in a sort of warning message but neither BD87 or the FM can process idoc with status 52
i have put it status 64 but client won't accept it since he recognise idoc comming from external system as 64.

Hi,
use my form for finishing IDOC processing from the time I did not uses OO...
*&      Form append_idoc_status
*       Create IDOC status record from system message fields
*       This is always the last action for processing one single
*       IDOC
FORM append_idoc_status
USING    ps_edidc        TYPE edidc
CHANGING pt_idoc_status TYPE ty_t_bdidocstat.
DATA:
    ls_bdidocstat TYPE bdidocstat.
* this Routine must be called only once per IDOC
MOVE-CORRESPONDING ps_edidc TO ls_bdidocstat.
* transfer message data
ls_bdidocstat-msgty    = sy-msgty.
ls_bdidocstat-msgid    = sy-msgid.
ls_bdidocstat-msgno    = sy-msgno.
ls_bdidocstat-msgv1    = sy-msgv1.
ls_bdidocstat-msgv2    = sy-msgv2.
ls_bdidocstat-msgv3    = sy-msgv3.
ls_bdidocstat-msgv4    = sy-msgv4.
ls_bdidocstat-repid    = sy-repid.
* update IDOC status
CASE ls_bdidocstat-msgty.
    WHEN 'S' OR 'I'.
      ls_bdidocstat-status = c_idoc_posted_ok.
    WHEN 'W'.
      ls_bdidocstat-status = c_idoc_not_fully_posted.
    WHEN 'E' OR 'A'.
      ls_bdidocstat-status = c_idoc_not_posted .
ENDCASE." ls_bdidocstat-msgty.
APPEND ls_bdidocstat TO pt_idoc_status.
ENDFORM.                    " append_idoc_status
A precondition is that your processing issues a MESSAGE ... INTO lv_dummy with lv_dummy of TYPE STRING.
Regards,
Clemens

Inbound idoc status 62

hi,
am getting the sales order as inbound with status 62.
can anybody reply how to rectify this problem.
but in we19 i have executed privious idocs it will give the status 53,

Hi Sathish,
Please check the following links given below:
IDOC:
http://www.sapbrainsonline.com/ARTICLES/TECHNICAL/idoc/SAP_IDOC_structure_introduction.html
Status codes:
http://publib.boulder.ibm.com/tividd/td/ITMAN/SC23-4812-00/en_US/HTML/sa51mst256.htm
Regards
Satish

IDOC status 03 but no XML generated

Hi Experts,
I am facing a problem related to idoc i.e. I am getting idoc status 03, still no XML created at the server directory.
Scenario is: A custom idoc is created with a z report which selects data & send idoc as an XML file in the server directory
IDOC (the first \ represents root as it is a unix server, 2nd \ is a saparator nd then IDOC is a folder to save XML files). Folder IDOC is having all permission(777). When i send idoc using the report is fives status 30 & after that when process it through BD87 it gives a status message 03.
I checked the partner profile, port etc. Even in port access test is OK.
I even tried putting directory as //IDOC , /IDOC but then no access possible error came. only work with
IDOC & gives status message 03.
But no idoc is reaching at the other end i.e.
IDOC.
Can anyone tell me how to fix this problem. Is the problem at SAP end of Unix end.
Regards,
Nik

Hi,
Check the Port configuration.In this case mostly problem form port configrations only.
Check Directory,Outbound file paramters in the port configuration.
Thanks,
radha.

IDOC status 30 but partner profile is set to send immediately (04)

Hi guys,
I have a problem with idocs not being sent immediately... The outputs, the EDI partner profiles are all set up correctly...
it is configured to send immediately however, it's not doing so... prior to upgrade to ECC 6.0 it's working fine... now its not...
However, in BD87 thru manual release of IDocs, it is working fine...
Is there any changes to ECC 6.0 for this matter? or is there anything that needs to be set up other than those mentioned above in order for it to work in ECC 6.0?
Thanks a lot!

Mark, have you looked at the OSS notes? By 'IDOC status 30' it finds 300+ notes, this is really a wide-spread issue.
The most recent one is 150202, which actually recommends collecting the IDocs instead of having "send immediately" because it saves the RFC resources. This is not really an ABAP issue, so you might want to discuss this with your Basis admin.
Also, from my experience, even with "mission critical" processes the users, in fact, never feel any real difference between "immediate" and 5-10 min. Sometimes (due to a technical problem, for example) nothing goes on for 30+ min. and no one even notices.

IDOC status 53 but no document is posted

All,
I am sure this would be answered earlier but not able to find the thread.
Can somebody please let me know, when I process the IDOC using WE16, I get status 53 but dont find document as posted.
Thanks
Sameer

Hi,
Check the config stuff if you are usng the right IDoc...See partner profiles and the message types.
thanks

Apps icon shows updates, but nothing in updates window

Hey everyone,
I have the usual number of apps to be updated next to the Apps Icon under Library in iTunes, but when I click "X updates available", there's nothing to update.
Any thoughts?
cheers,
Daz.

A work around found by Fly150
Go into your puchased tab and download each update (you'll find the app icons with little update banners on them.)
Alternatively, if you sync with a computer, you can use the iTunes on your computer to download the updates then sync them onto your device.
Or you can be patient and wait for Apple to fix the issue

Idoc status green but data not posted correctly to destination system.

Hi,
Can anyone help me out with idoc problem that I am facing.
The problem has come out with outbound idoc.
The status of the idoc is green when it has been sent but the objects that has been sent with that idoc are not getting posted in the destination system.Some of them are posted correctly but some of them are not.
What may be the reason behind this.
Regards,
Rachana.

Good morning
What was the resolution here? We are siitng with the same problem, but IDoc's are correct, but data packet not processed.
Thanks, have a nice day
Cj

HRMD_A Inbound Idoc with process Code:HRMD not updated in SAP

Dear friends,
I'm facing a problem with Personnel data creation in SAP (this is not a SAP HR system).
I have a data file with Personnel data, in WE19, I use idoc_input_hrmd to process the data (with basic type: hrmd_a06). Idoc has been created with status '53'. However, when I check in SAP, t-code PA30 with the Personnel number, the record does not exist. Checked infotype tables PA0000, PA0001, PA0002 and PA0003 as well, no luck.
I wonder where does the data go? Is it sitting somewhere in the system and waiting to be processed?
Please help!!!!!

Hi
Authorizations might be one of the reason.
So IDOC transfered but no records to be writeen to DB.
regards
vijay

Inbound idoc status 53 but nothing is updated in transaction level

Similar Messages

Maybe you are looking for