I/B Idoc Status 56 - Reason Required

Hi,
We have a PI system and R/3 System. PI sending some idoc to R/3. In this case Idoc is failing and giving status message as 56. Can any one tell me reason why it is giving error like.
Error messages are like this:
Status Text:- IDoc: 0000000001230201 Status: IDoc with errors added
T001 Text :- EDI: Partner profile not active
Please let me know in which system do i need to the changes and how can i do these changes.
I am new to this concept.
Thanks,
Sekhar.J

Hi Sekhar,
From PI perspective everything is fine, you were able to create an IDOC structure and push it to R/3 system and there is also successfully created but it has failed with the error 56. It is due to invalid partner profile, check the transaction WE20 whether a partner profile has been created for that partner or not, if it is created then whether the message type is configured for that partner or not.
The error is basically due to invalid partner profile and you need to correct that in WE20 transaction, once you correct that then you can reprocess the idoc through BD87 transaction.
Thanks,
Mahesh.

Similar Messages

IDOC Status 26: EDI: Syntax error in IDoc (segment cannot be identified).

Hi All,
I have created IDOC extension for IDOC Basic type "PROACT01" and have followed all required necessary steps but getting IDOC
Status 26. EDI: Syntax error in IDoc (segment cannot be identified). The exact error is:
Please check Error Details and the details of the steps I followed for Setting up IDOC Extension:
Error Detail :
EDI: Syntax error in IDoc (segment cannot be identified)
Message no. E0078
Diagnosis
The segment ZPROSEG does not occur at the current level of the basic type PROACT01 (extension PROACTEX).
This error can have several reasons:
The segment ZPROSEG is assigned to a group whose header segment does not occur.
The segment ZPROSEG does not exist in the syntax description of the basic type PROACT01 (extension PROACTEX).
The sequence of segments in the group in which the segment appears is incorrect.
Previous errors ('mandatory' segment or group missing) may be due to this error.
Procedure
Please check the IDoc or the syntax description of the basic type PROACT01 (extension PROACTEX).
Can you please look at this problem and suggest what is wrong with IDOC Extension/Custome Segment?
Below is the Details of the Steps which I have followed:
1. Tcode WE31 - Created new custom Segment ZPROSEG with 4 fields. Released segment.
2. TCode WE30 - Created IDOC Extension PROACTEX for Basic Type PROACT01. Released IDOC extension.
Here when I run syntax check warning appears "No predecessors exist". I am not sure if its okay!!
3. TCode WE82 - Added Extension PROACTEX in the Message Type PROACT with BASIC Type PROACT01.
4. TCode WE20 - Added IDOC Extension PROACTEX in the predefined partner profile in WE20 transaction.
5. Added the following code in the Customer Exit EXIT_SAPLWVMI_001 include ZXWVMIU01 .
DATA segnam(27).
READ TABLE dedidd WITH KEY segnam = 'ZPROSEG'.
IF sy-subrc NE 0.
LOOP AT dedidd WHERE segnam = 'E1EDP31'.
CLEAR dedidd.
dedidd-segnam = 'ZPROSEG'.
zproseg-matnr = 'Mat1'.
zproseg-lgort = '001'.
zproseg-gernr = 'SNo1'.
zproseg-labst = 2.
dedidd-sdata = zproseg.
APPEND dedidd.
ENDLOOP.
ENDIF.
Finally ran transaction WVM2 (Transfer of Stock & Sales Data) to generate IDOC, its creating IDOC but when checked IDOC in WE05 its getting Status Error "26".
Looking forward for your reply.
Many thanks in advance.

Hello,
Actually you are appending the Z segment instead of inserting into the correct position. So the segment is added at the last, so hierarchy of segments is collapsed.
So get the index of the previous segment E1EDP31 and increase the index by 1 and INSERT the Z segment with that new index as below.
LOOP AT dedidd WHERE segnam = 'E1EDP31'.
lv_index = sy-tabix. " <<--
ADD 1 TO lv_index. " <<--
CLEAR dedidd.
dedidd-segnam = 'ZPROSEG'.
zproseg-matnr = 'Mat1'.
zproseg-lgort = '001'.
zproseg-gernr = 'SNo1'.
zproseg-labst = 2.
dedidd-sdata = zproseg.
*APPEND dedidd.
INSERT dedidd INDEX lv_index. " <<---
ENDLOOP.
Here actually we are insering the record inside the LOOP and it regenerates the index again. It is not actually a good practice.
So the best practice is get the index and generate the segment inside the loop, store them into another internal table, come out the loop and insert the Z segments into DEDIDD by looping the new internal table.

How can I pass value in status and reason for rejection using BAPI_LEAD_CREATEMULTI when creating multiple lead

Hello,
I want pass value in STATUS and Reason for rejection according to requirement when i am creating multiple lead using BAPI_LEAD_CREATEMULTI. Please help me how can i pass value. Please give some sample code that in which table i have to pass values and please also tell me INPUT_FIELDS values. Please help me
Regards,
Kshitij Rathore

Hello,
Please help me for solve this problem. I am trying to solve problem from last 4 days but i didn't get any solution.
Regards,
Kshitij Rathore

IDOC STATUS 29 to 68

Hi all,
Customer request is change idoc status from 29 to 68.
68 = no further processing inbound side
31 = no further processing outbound side
if i change status of idoc from 29 to 68 using Fn module IDOC_STATUS_WRITE_TO_DATABASE
Data of idoc is vanishing.
I observed that if i change status of idoc from 29 to 31 then there is no data loss in idoc with same Fn module.
Is there any way to change idoc status from 29 to 68 without losing the Idoc data.
anyway for both 68 & 31 meanings are same , but customer requires 29 to 68.
if u have any idea please suggest me.

Hi Suneel,
If the program does't exits then try this ...
DATA: L_EDIDC_TAB       LIKE EDIDC      OCCURS 1 WITH HEADER LINE,
      L_IDOC_STATUS_TAB LIKE BDIDOCSTAT OCCURS 1 WITH HEADERLINE,
      L_IDOC_CONTROL    LIKE EDIDC.
    L_IDOC_STATUS_TAB-DOCNUM = <your IDoc number>.
    L_IDOC_STATUS_TAB-STATUS = '68'.
    APPEND L_IDOC_STATUS_TAB.
    CALL FUNCTION 'IDOC_STATUS_WRITE_TO_DATABASE'
         EXPORTING
              IDOC_NUMBER               = L_EDIDC_TAB-DOCNUM
         IMPORTING
              IDOC_CONTROL              = L_IDOC_CONTROL
         TABLES
              IDOC_STATUS               = L_IDOC_STATUS_TAB
         EXCEPTIONS
              IDOC_FOREIGN_LOCK         = 1
              IDOC_NOT_FOUND            = 2
              IDOC_STATUS_RECORDS_EMPTY = 3
              IDOC_STATUS_INVALID       = 4
              DB_ERROR                  = 5
              OTHERS                    = 6.
Regards,
Ferry Lianto

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 is not coming to '03'

Hi,
When I run my program, it is giving IDoc status as 30. When I go and see in WE05, it is showing same status. It's not getting 03 status.
I know that we can bring the status to 03 by executing the program RSEOUT00. But I want this to come from my program where I have used MASTER_IDOC_DISTRIBUTE function module.
Generally, even though I get status 30 in the program, when I go and see in WE05, 03 status is displayed. But I don't know what happend this time, it is showing 30 status even in WE05 also.
Please tell me what could be the reason.
Regards,
Suman.

Hello,
Check if there are any dumps in the system
Or
if there are any authorization issues.
IF there are dumps, then the system usually stops autoprocessing the idocs and you might need to schedule the program at periodic intervals to get the idoc in status 03.
Thanks,
Sushil Joshi

Need to change the Idoc Status based on the Text in the Idoc

Hi All,
I have developed Idoc--SOAP Sync Process Scenario Using BPM and Works Perfectly.
I have used STATUS.SYSTAT01 Idoc to capture the Response that is comming from the Webservice.
I have mapped the response Text( Success or Fail) to one of the field in the Response Idoc, this is perfect.
Requirement:
1) If the Response Idoc Field receives Success Text means the Idoc Status shld be in Green Status.
2) If the Respnse Idoc Field Receives FAIL means the Idoc Status shld be in RED Status.
How can i Do this. please suggest me......
Regards

Hi Santhosh,
YES, I have to Capture the Response from Webservice in SAP R/3 by using STATUS.SYSTAT01 Idoc.
I have mapped the response from webservice to the one of the field in the Idoc.
If this field contains Success as text means the Idoc Status in We05 shld be 53 else it shld be 56
With out changing the FM code, can we use any other process to achieve this???
@ Mario
Can u please Allobarate your views more based on my requirement
Regards

IDOC status not changed

SAP support
I am not able to change the IDOC status...
I have also processed the IDOCs many times..
Guidance required...
Kamal

Dear Kamal
Please check your entry in SM12 an delete it and again reprocess it with the help of Tcode Bd87
Thanks
Amit Shivhare

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

Any FM/methods to update idoc segments without changing idoc status

Hi All,
My requirement is a reprocessor program which fills up some fields in the idoc segment before posting. So, after updating the segments, the idoc status should remain as before.
Is there any function modules or methods to update idoc fields in segments without changing the idoc status?
I have tried the FMs EDI_DOCUMENT_OPEN_FOR_EDIT, EDI_CHANGE_DATA_SEGMENT and EDI_DOCUMENT_CLOSE_EDIT, but it changes the idoc status.
Thanks,
Arun Mohan

As for FM to do this, i don't know if there are any, but i think you can go directly to the tables with the IDOC data and change them without triggering the changes in status like FM do. Still, i am not sure this is completely true, but you could give it a try. Also, i don't know if this is the best way to do it, because of those legal/audit questions mentioned by Thomas.
Here is a sample code of a program we have to change a field in a segment of WPUUMS.
*& Report YRE00021INTPG
REPORT yre00021reppg.
TABLES: edid4 ,
        edidc ,
        mean .
* Variaveis Auxiliares
DATA: t_edidc TYPE edidc OCCURS 0 WITH HEADER LINE.
DATA: t_edid4 LIKE edid4 OCCURS 0 WITH HEADER LINE .
DATA: BEGIN OF t_docs OCCURS 0,
        docnum LIKE edidc-docnum ,
      END OF t_docs.
DATA: wa_e1wpu02 LIKE e1wpu02 .
DATA: wa_e1wpu03 LIKE e1wpu03 .
DATA: t_itedidd LIKE edi_dd40 OCCURS 0 WITH HEADER LINE ,
      t_itedidc LIKE edi_dc40 OCCURS 0 WITH HEADER LINE ,
      fw_itedidc LIKE edi_dc40 ,
      fw_itedidd LIKE edi_dc40 .
DATA: l_matnr TYPE mara-matnr,
      l_tam TYPE i.
DATA: l_idoc_number TYPE edidc-docnum.
* Ecran de selecção
SELECTION-SCREEN : BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
SELECT-OPTIONS: s_docnum FOR edid4-docnum ,
                s_credat FOR edidc-credat DEFAULT sy-datum ,
                s_cretim FOR edidc-cretim .
PARAMETER:      p_mestyp LIKE edidc-mestyp DEFAULT 'WPUUMS' ,
                p_status LIKE edidc-status DEFAULT '51' .
*SELECTION-SCREEN SKIP.
*PARAMETER:      p_ean11 TYPE mean-ean11.
SELECTION-SCREEN : END OF BLOCK b1.
AT SELECTION-SCREEN.
IF p_status <> '51'.
    MESSAGE e001(yre) WITH 'Apenas pode modificar IDOCS com erro'.
ENDIF.
IF p_mestyp <> 'WPUUMS'.
    MESSAGE e001(yre) WITH 'Apenas pode lançar WPUUMS'.
ENDIF.
*AT SELECTION-SCREEN ON p_ean11.
* SELECT SINGLE * FROM mean WHERE
*    ean11 = p_ean11.
* IF sy-subrc <> 0.
*    MESSAGE e001(yre) WITH 'Ean não existente'.
* ENDIF.
START-OF-SELECTION.
SELECT docnum INTO TABLE t_docs FROM edidc
                     WHERE status = p_status
                     AND   mestyp = p_mestyp
                     AND   docnum IN s_docnum
                     AND   credat IN s_credat
                     AND   cretim IN s_cretim .
CHECK sy-subrc = 0 .
LOOP AT t_docs.
    CLEAR : wa_e1wpu02.
    SELECT * FROM edidc INTO TABLE t_edidc
      WHERE docnum = t_docs-docnum.
    CHECK sy-subrc = 0.
    SELECT * FROM edid4 INTO TABLE t_edid4
                  WHERE docnum = t_docs-docnum AND
                        segnam = 'E1WPU02'.
    CHECK sy-subrc = 0.
    SORT t_edid4 BY segnum.
    LOOP AT t_edid4 .
      wa_e1wpu02 = t_edid4-sdata.
      WRITE wa_e1wpu02-artnr TO l_matnr NO-ZERO.
      CONDENSE l_matnr.
*      l_tam = STRLEN( l_matnr ).
*      IF l_tam <= 6.
        SELECT SINGLE ean11 INTO wa_e1wpu02-artnr FROM ytre00004 WHERE
          codcurto = l_matnr.
        IF sy-subrc = 0.
          WRITE : /1 'Código ', l_matnr, ' alterado para ', wa_e1wpu02-artnr.
        ELSE.
          WRITE : /1 'Código ', l_matnr, ' não encontrado na tabela de conversão'.
          CONTINUE.
        ENDIF.
*        CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
*          EXPORTING
*            input = p_ean11
*          IMPORTING
*            output = wa_e1wpu02-artnr.
*      ENDIF.
      UPDATE edid4 SET   sdata   = wa_e1wpu02
                   WHERE docnum = t_edid4-docnum
                   AND   counter = t_edid4-counter
                   AND   segnum = t_edid4-segnum .
      IF sy-subrc <> 0 .
        ROLLBACK WORK .
        WRITE: / t_edid4-docnum .
      ELSE.
        COMMIT WORK.
      ENDIF.
    ENDLOOP.
ENDLOOP.
END-OF-SELECTION.

IDOC status 52 - Document not fully posted

Hi all,
On transferring HR data from R/3 to CRM shows two IDOCs, one which is posted- status 53, and the other with status 52 - document not fully posted. IDOC details show that central person for employee and relationships could not be created. The org. structure is replicated but employees are not.
Now there seems to be a reason behind this, this is the second time I am having problems with IDOCs during HR/CRM integration I have had the same problem when earlier a system client copy was taken and faced the IDOC transfer problem in the copied client. In fresh installations the integration works fine. Are there any system buffers to be refreshed or anything else on the technical side or am I missing settings on the CRM side ?
Please help ASAP.
Regards.
PS: the RFC's are working fine as well and already gone through note 550055

Dear Haseeb,
Thanx for your quick response.
For an employee(18730) 1st idoc has been generated on 03.06.2013 from ECC to CRM with these infotypes data (0,1,105) but idoc status is 52, and again changed on 04.06.2013 infotype (2) and idoc hase been generated but status is 52 in CRM and same again changed on 06.06.2013 infotype (6) and idoc hase been generated but status is 52 in CRM. But still Business partner has not been created in CRM.
We are facing for few employees related this issue.
I have been checked SLG1 and WE02 in both ECC & CRM, Please find the attached screen shots for your kind reference.
Please let me know is any other process to solve my issue.
Thanks & regards
Rajasekhar S

IDOC status 62 - IDOC passed to application

Hello Experts,
Am posting a inbound sales order custom/extended IDOC into the system from WE19, but, when I saw it in WE02/05, its showing status 62 - IDOC passed to application, i checked ST22 run time error. there is no error and also checked triggering timings, its trigger IMMEDIATELY in WE20 fo rthat partner!!
Pls. let me kniow the reasona and fixing idea.
Thank you

I think you're going to want to debug through the process code (set a breakpoint in that function) and determine if you get a clean exit from there. If so, you should see a new status in your control record and in your status table as you exit the function call. It sounds like you've got an abnormal termination/exit from the process code, in which case the IDOC status is falling back to the last recorded status. If this is not the case, then perhaps you've got a commit handling issue where an explicit commit is expected to finish the process but never happens.

IDoc status error 51 : A company code cannot be determined for LS

Hi,
We are trying to post an Idoc into R/3 but getting the IDoc status code 51 : A company code cannot be determined for LS
What could be the possible reason?
Should we use Party in Receiver IDoc scenarios?

Hi,
I have quite the same problem. I built an IDOC with WE19 and I have the message "A company code cannot be determined for LI 0000031004".
As explained in note OSS 117808, the partner number (31004) and partner type (LI) are read from the control record of the IDOC. I enter this values in OBCA and OBCE customizing points, to determine the company code 'LC'. It doesn't work.
PT Rao, what do you call "activate partner profile" ?
Thanks in advance.
Regards,
Arnaud

IDOC status to sender system

I configured IDoc within 2 clients in same server, when I send IDoc to receiver it is giving 03 (success) but in receiving system IDoc gives error 51 as some data is not maintained, i am using "Z" function module for inbound IDoc
question - how to send that same error message to the sender

Hi Ankush ,
question - how to send that same error message to the sender?
I have done the same requirement . Please find the below Procedure
-> before ending of the Custom function module check whether Idoc is Success or not .
   IF (error)
LOOP AT idoc_status INTO wa_idoc_status
                      WHERE   docnum = idoc_data-docnum . "Loop the Idoc Status table
l_i = 0.
CALL FUNCTION 'FORMAT_MESSAGE'
EXPORTING
   id              = wa_idoc_status-msgid
   lang            = '-D'
   no              = wa_idoc_status-msgno
   v1              = wa_idoc_status-msgv1
   v2              = wa_idoc_status-msgv2
   v3              = wa_idoc_status-msgv3
   v4              = wa_idoc_status-msgv4
IMPORTING
   msg             = l_msg
EXCEPTIONS
   not_found       = 1
   OTHERS          = 2
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
l_i = l_i + 1.
CASE l_i .
    WHEN c_1.
      MOVE l_msg TO   wa_zf40-error_msg1.
    WHEN c_2.
      MOVE l_msg TO   wa_zf40-error_msg2.
    WHEN c_3.
      MOVE   l_msg TO   wa_zf40-error_msg3.
    WHEN c_4.
      MOVE l_msg   TO   wa_zf40-error_msg4.
    WHEN c_5.
      MOVE   l_msg TO   wa_zf40-error_msg5.
ENDCASE.
ENDLOOP.
->Now create a Ztable to make the error descrptions.(Matian some Key fields to identify the Idoc .
->After this create   a RFC to read the entries .
I hope this helps to you.Please let me know if u have any query.
Rgds
Sree M
Edited by: Sree Merugu on Mar 27, 2008 6:22 PM

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

I/B Idoc Status 56 - Reason Required

Similar Messages

Maybe you are looking for