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

Similar Messages

  • 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 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

  • 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

  • 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.

  • 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

  • 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

  • How to find Correct IDoc Status in SAP

    Hi All,
    I need some help on IDoc scenario, I have custom program to create Idoc and as well it will send IDoc to XI. I want to know idoc staus in the program to update custom table whether idoc sent successfully or not but idoc giving status as 03 (Data passed to port OK) irrespective of idoc send or not, actually idoc not sent to xi when I check SM58 showing error.
    Please advice me how to find correct idoc status inside program itself.
    **-----Create IDoc
      CALL FUNCTION 'IDOC_OUTBOUND_WRITE_TO_DB'
        TABLES
          int_edidd      = i_edidd
        CHANGING
          int_edidc      = wa_int_edidc
        EXCEPTIONS
          idoc_not_saved = 1
          OTHERS         = 2.
      COMMIT WORK.
      i_edidc = wa_int_edidc.
      APPEND i_edidc.
      REFRESH i_edidd.
    **-----Send Idoc
      CLEAR i_edidd.
    **-------Send Idoc to XI
      CALL FUNCTION 'EDI_OUTPUT_NEW'
        EXPORTING
          onl_option = 'B'
          error_flag = ' '
        TABLES
          i_edidc    = i_edidc
          i_edidd    = i_edidd.
      COMMIT WORK.
      READ TABLE i_edidc INDEX 1.
    **-----Update Dispatch order status based on Idoc status.
      IF sy-subrc =  0 AND i_edidc-status ='03'.
        znxi01_update c_03 i_edidc-docnum.
        gw_success_record = gw_success_record + 1.
      ELSE.               " Error in Data Transfer
        znxi01_update c_02 i_edidc-docnum.
        gw_fail_record = gw_fail_record + 1.
      ENDIF.

    Hi Anil,
    for setting IDOC Status you can send back a IDOC of type <i>ALEAUD01</i>.
    The function IDOC_INPUT_ALEAUD takes automatically this IDOC and writes the status to the origin IDOC.
    Regards Mario

  • IDOC status at 30, but in we05 it is 03

    Hello Gurus!!
    My program generates an IDOC and as soon as the idoc is generated it the status is 03 then i have todo something else.
    Within the program when i am cheking the status is 30 but actually in transaction we05 the status is 03.
    I have cheked the partner profiles and transfer_idocs_immeadiately has already been selected.
    I have already gone thru the forum but no valid solution was given,
    There is no need to change any ALE configurations / port configurations because everything just work fine. It is only that within the program i am not able to catch the status 03. the proram is not waiting untill the idoc status is 03. it is capturing only the status 30.
    Is there any thing that i can do within the program? should i capture the idoc number and then check the idoc status from EDID4?
    Please answer o this questions ASAP.
    Regards.

    Initially when you create the outbound idocs then status is 30. then you have to run the program RSEOUT00 to process the idoc then after the processing the status changes to 03.
    But the Program RSEOUT00 is optional. In the partner profile (WE20) If you select the option  'Collect Idocs', then you have to schedule the program RSEOUT00 to process the Idocs otherwise if you have choose the option 'Transfer idoc immediately', you don't need to do anything.
    Thanks,
    Srinivas

  • Idoc status 03 in SAP but in XI idoc not showing

    Hi Experts,
    in my SAP to file scenario, idoc is created successfully with status 03, but idoc  is not coming to PI.
    It is not happening always. some times, idocs are missing. But not able to find any error in PI.
    Please guide me how to get the missed idoc.
    Thanks,
    Swapnashree

    this is old interface and it only gave issue this time. In ECC side, when I checked, out of 4 idocs one idoc is with 03 status and other three were with 39 status.
    But all in green status. No error.
    RFC destination and all are correct.
    Actually I am not able to see the complete error text in TRFC . that message class is not maintained. Our functional team informed that they added XX text and re import idoc and it worked. Please suggest.

  • IDOC status on 03 but not recieved on target system

    Hi,
    We are recieving inbound idoc from external system and processing Inbound IDOC on SAP system, after processing inbound idoc on SAP we are sending status outbound idoc to external system.
    The above functionality was working fine before upgradation.
    after upgradation we have recreated RFC (TCP/IP) connection, updated at port level and also configured the new SAP system details ( sid, Hostname, service programsname...) on external system correctly.
    Now we are recieving inbound idoc from external system on upgraded system,after processing inbound idoc details on SAP system, generating outbound idoc from SAP and it reaching the outbound prot sucessfully on 03 status with green light.
    But external system is not recieving the IDOC. How to find why idoc is not reaching external system even though it is sucessfully passed at outbound port level with green light status 03.
    We have also checked the SM58 for TRFC entries but we didn't identified any entries on SM58. Please help us on this issue
    Thanks,
    Raju

    Hi Raju,
    As  mentioned by The specified item was not found., the one common problem for the IDocs not being sent might be a missing COMMIT WORK. I.e. when using the standard SAP API's for sending outbound IDocs, SAP actually creates the IDoc and registers an update function for sending the IDoc out. So without the COMMIT WORK, the IDoc usually exists on the database (implicit or database commmits), is in status 03, but hasn't been sent out and cannot be found in the outbound RFC queue (because SAP never tried to send it).
    If you're convinced that a COMMIT WORK is happening (and after trying to send the outbound IDoc) then I'd try the following: Replace the used RFC destination (or re-define it temporarily) with one that points to the same system from where you're sending. If you don't see the IDocs as inbound IDocs or in the outbound RFC queue, the sending never happens. (Ok, might be a moot point if you completely trust your external system, but usually it's good to even rule out the most unlikely causes - if it's simple.)
    So if this didn't help, maybe you can provide some further insight into how you're creating/sending the outbound IDocs. This could help us in trying to get some answer, but for a starter the COMMIT WORK mentioned by The specified item was not found. is in my opinion the best candidate.
    Cheers, harald
    p.s.: Even if you're using ALE, I don't think it could be due to anything in your distribution model as mentioned by The specified item was not found.. If you wouldn't have setup the distribution model, the SAP API's should create a master IDoc in memory and then no communication IDocs (since there's no recipients or due to filtering) and thus there should be no outbound IDocs on the database.

  • Idoc at status 51, however outbound delivery created

    Hi Gurus,
    We have peculiar issue , where in outbound delivery is getting created through IDoc. The inbound idoc has status 51 however delivery got created.  Any idea how is it possible?.
    Thanks in advance.

    Dear Math,
    Have you got the solution for the above. If you get can you tell me please because even i got the same error message while processing the IDOC
    status 51 after status 53. Outbound delivery is updated but not the sales order.
    can you please help me

  • Is it possible to create a custom IDOC status?

    Is it possible to create a custom idoc status on table TEDS1?
    I have looked through customising and cannot seem to find a way to create a new idoc status.
    Has anybody done this?

    Hello Chester..
    hope this link will be helpful,
    Re: IDOC status
    *********Please reward points ,if found useful

  • How to create an IDOC Status.

    Hi All,
    I have a requirement to create an IDOC Status, which should be a copy of existing status.
    How to accomplish the same.
    Regards,
    Neha

    Hi Neha,
    You can create the Idoc status, if it is an Inbound Idoc. Copy the Existing process code & add it to u r Inbound Partner Profile. In the process code u can create the status..Check the below code.
    if gv_error_status <> 0.
            condense gt_msgv-msgv1 no-gaps.
            translate gt_msgv-msgv1 to upper case.  "#EC TRANSLANG
            set extended check on.
            read table idoc_contrl index 1.
            idoc_status-status = '68'.
            idoc_status-uname  = sy-uname.
            idoc_status-repid  = sy-repid.
            idoc_status-routid = gv_funcname.
            idoc_status-docnum = idoc_contrl-docnum.
            idoc_status-msgv1 = gt_msgv-msgv1.
            idoc_status-msgv2 = gt_msgv-msgv2.
            append idoc_status.
            idoc_status-status = '51'.
            idoc_status-uname  = sy-uname.
            idoc_status-repid  = sy-repid.
            idoc_status-routid = gv_funcname.
            idoc_status-docnum = idoc_contrl-docnum.
            append idoc_status.
    endif.
    I hope this help you.
    Regards
    Rajendra

  • CVI7 initial partial order is created with status SY but it is not distrib.

    hi,
    In CVI7 initial partial order is created with status SY but it is not distributed to recepient list attached with documnet which required to be sent,
    Please any one can let me know the process flow for this,

    hi,
    In CVI7 initial partial order is created with status SY but it is not distributed to recepient list attached with documnet which required to be sent,
    Please any one can let me know the process flow for this,
    Hi guru's,
    the above problem is sorted with help of workflow and basis consultant as in SWU3 RFC destination was not enabled,
    as now it is enabled, workflow is getting triggered but after creating distribution package it is generating error saying no receipient found,
    the mail is not reaching the SAP INBOX,
    Kindly let me know whether i missing any config.

Maybe you are looking for