IDOC status 56 Interlocutor Number

Hi all,
I am sending an IDOC ORDERS05 to a SAP System. In my SAP system I am getting a IDOC in status 56 because I am not sending Interlocutor EDI Number.
Can anyone tell me which field of the header of idoc is for this Interlocutor EDI Number? (In my case 8008)
Thanks for all.

Maintain for inbound IDocs the SNDPRN (partner number) and the SNDPRT (partn.type) in the EDI_DC40 fields. [Also check this link.|http://help.sap.com/saphelp_sm32/helpdata/en/52/16ac2a543311d1891c0000e8322f96/content.htm]
Also make sure your partner and the IDoc is maintained in the WE20 partner profile.
Edited by: Konrad Thalheim on Mar 22, 2011 5:34 PM

Similar Messages

What is the Successfull processed IDOC status number?

Hi Experts
What is the Successfull processed IDOC status number?
arjent Please.
Thanks in advance
Sekhar

Hi Chandra,
Below are IDoc Process Codes
For outboud Idocs:
1 IDoc created
2 Error passing data to port
3 Data passed to port OK
4 Error within control information of EDI subsystem
5 Error during translation
6 Translation OK
7 Error during syntax check
8 Syntax check OK
9 Error during interchange handling
10 Interchange handling OK
11 Error during dispatch
12 Dispatch OK
13 Retransmission OK
14 Interchange Acknowledgement positive
15 Interchange Acknowledgement negative
16 Functional Acknowledgement positive
17 Functional Acknowledgement negative
18 Triggering EDI subsystem OK
19 Data transfer for test OK
20 Error triggering EDI subsystem
21 Error passing data for test
22 Dispatch OK, acknowledgement still due
23 Error during retransmission
24 Control information of EDI subsystem OK
25 Processing despite syntax error (outbound)
26 Error during syntax check of IDoc (outbound)
27 Error in dispatch level (ALE service)
28 Not used
29 Error in ALE service
30 IDoc ready for dispatch (ALE service)
31 Error - no further processing
32 IDoc was edited
33 Original of an IDoc which was edited
34 Error in control record of IDoc
35 IDoc reloaded from archive
36 Electronic signature not performed (timeout)
37 IDoc added incorrectly
38 IDoc archived
39 IDoc is in the receiving system (ALE service)
40 Application document not created in receiving system
41 Application document created in receiving system
42 IDoc was created by test transaction
50 IDoc added
For Inound Idocs
51 Error: Application document not posted
52 Application document not fully posted
53 Application document posted
54 Error during formal application check
55 Formal application check OK
56 IDoc with errors added
57 Test IDoc: Error during application check
58 IDoc-Copy from an R/2 connection
59 Not used
60 Error during syntax check of IDoc (inbound)
61 Processing despite syntax error (inbound)
62 IDoc passed to application
63 Error passing IDoc to application
64 IDoc ready to be transferred to application
65 Error in ALE service
66 IDoc is waiting for predecessor IDoc (serialization)
67 Not used
68 Error - no further processing
69 IDoc was edited
70 Original of an IDoc which was edited
71 IDoc reloaded from archive
72 Not used, only R/2
73 IDoc archived
74 IDoc was created by test transaction
Regards,
Satish

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 53 in employee replication from SAP HR

Hi experts,
We are having some problems in CRM BP creation with role employee.
We are using CRM 5.0 and SAP ECC 6.0 and we are trying to replicate employees information to CRM from HR.
After read the notes 934372, 615896, 550055, 363187, 312090 we made the next configuration steps in our systems:
R/3:
- Creation of connection port (trans. WE21)
- Creation of logical system (trans. WE20) and assignment of outbound message HRMD_ABA
- Creation of distribution model (trans. BD64) with all filters indicated in note 312090
CRM
- Creation of logical system (trans. WE20) and assignment of inbound message HRMD_ABA
- Creation of conversion between basic types HRMD_A05 and HRMD_ABA01 (trans. WE70) as described in note 312090
- Creation of conversion between message types HRMD_A and HRMD_ABA (trans. WE73) as described in note 312090
- Creation of external number range ZE from HR01200001 to HR01299999 (using PA04 in R3 we found the number range between 01200001 and 01299999)
- Creation of BP Grouping with the same name of number range (ZE) checked to be external too
- Update of table T77S0 (using SM30):
HRALX HRAC X
HRALX PBPON OFF
HRALX PBPHR ON
HRALX PBPON ON
HRALX PNUMB 3
HRALX PPROL BUP003
HRALX PSUBG ZE
PLOGI PLOGI MV
We know we should have the same value in R3 and CRM for PLOGI/PLOGI, so we created in CRM MV because that is the plan version used in R3. To create it, we just manually add a new row in table T778P and then selected it in table T77S0. Is this the correct way to create a plan version?
After these steps, in R3 we execute program RHALEINI with parameters:
- Plan version = MV
- Object type = P
- Object ID = an active employee
- Reporting period = all
- Transfer mode = Insert
- Receiving system:
Receiving partner No = DCRCLNT300 (logical system created in WE20)
Message type = HRMD_ABA
And everything looks fine in R3.
In CRM, using trans. WE05, we can see that the iDoc is created, apparently without problems with status 53 - "Applicaton document posted" but the business partner is never created.
Did we miss some configuration steps?
Should we do something more after see the iDoc in CRM to create BP?
Thanks in advance.
Alda

hi pratk bhai,
ya i have done the same setting what Ada has mentioned eariler,
and as of your suggestion to maintatin the mandatory infotype, i have even done tht,
after running RHALEINI in R3, the status is all green here.
when i run the tcode BD87 to check the Idoc status its showing fine (Error free).
now, through tcode se38 the report CRMHRALE_CENTRAL_PERSON shows all the employees as status green,,
but the partner number is not getting generated. ( i have used HRALX-PNUMB= 3 (Prefeexing the number range coming from R3)).
kindly advice me what should be done in order to generate a BP number for the replicated HR Employee.
best regards,
Madhup

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

File -- XI -- IDoc ( IDoc Status 56)

Iam trying to post IDoc(cremas03) with File --> XI --> Idoc Scenario.
I got message processed successful in SXMB_MONI.
However on ECC5.0(R/3) I got Idoc status 56.
EDI: Partner profile inbound not available
Message no. E0337
Diagnosis
An inbound partner profile could not be found with the following key:
/T20CLNT400/LS//CREMAS////
This involves the key fields of table EDP21:
-SNDPRN partner number of sender
-SNDPRT partner type of sender
-SNDPFC partner function of sender
-MESTYP logical message type
-MESCOD logical message code
-MESFCT logical message function
-TEST    test flag
Procedure
Please check the inbound partner profiles.
Execute function
On IDOC Display (We02) I found following info:
Technical Short Info
Direction : 2
current status: 56
Basic type: cremas03
Message type: cremas
Partner No: T20CLNT400
On Idoc control Record:
Typeinfo tab:
Basic Type: CREMAS03
Message Type: CREMAS
Partner Tab:
Recipient
Port:   (Spaces)
Partner No: ID3CLNT550
Partner Type: LS
Sender
Port: SAPSXI
Partner No: T20CLNT400
Partner type: LS
Tech Info:
Sap rel : 640
On Partner Profiles:(WE20)
ID3CLNT550 ( in this case receiver) was defined as Logical Sytem and Inbound message type CREMAS
Would someone please guide me what to do as Iam learner of XI.
Thanks a lot

Here it is.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:IDocOutbound xmlns:SAP="http://sap.com/xi/XI/Message/30">
<SAP:TABNAM>EDI_DC40</SAP:TABNAM>
<SAP:MANDT>400</SAP:MANDT>
<SAP:DOCREL>640</SAP:DOCREL>
<SAP:DOCNUM>0000000000046232</SAP:DOCNUM>
<SAP:DIRECT>2</SAP:DIRECT>
<SAP:IDOCTYP>CREMAS03</SAP:IDOCTYP>
<SAP:CIMTYP />
<SAP:MESTYP>CREMAS</SAP:MESTYP>
<SAP:MESCOD />
<SAP:MESFCT />
<SAP:SNDPOR>SAPSXI</SAP:SNDPOR>
<SAP:SNDPRN>T20CLNT400</SAP:SNDPRN>
<SAP:SNDPRT>LS</SAP:SNDPRT>
<SAP:SNDPFC />
<SAP:RCVPOR>SAPECC</SAP:RCVPOR>
<SAP:RCVPRN>ID3CLNT550</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
<SAP:RCVPFC />
<SAP:TEST />
<SAP:SERIAL />
<SAP:EXPRSS />
<SAP:STD />
<SAP:STDVRS />
<SAP:STATUS />
<SAP:OUTMOD />
<SAP:SNDSAD />
<SAP:SNDLAD />
<SAP:RCVSAD />
<SAP:RCVLAD />
<SAP:STDMES />
<SAP:REFINT />
<SAP:REFGRP />
<SAP:REFMES />
<SAP:CREDAT>0000-00-00</SAP:CREDAT>
<SAP:CRETIM>00:00:00</SAP:CRETIM>
<SAP:ARCKEY>BAA624009F6311DA8AD3003048805A88</SAP:ARCKEY>
</SAP:IDocOutbound>
Following data was defined in receiver system, Client 550
Inbound parameters:( With we20)
PartnerNo: ID3CLNT550
Type: LS
Inbound parameters:
Partner Role : LS
Message Type: CREMAS
Process Code : CRE1
Trigger immediately
PartnerNo: ID3CLNT550
Partner Type: LS
Inbound parametrs:
Partner role:   <---- blank here ..does this matter ?
Message Type: CREMAS
Process Code: CRE1
Trigger immediately

IDOC Status 68 & 51

Hi,
There is an IDOC with status 68 (Error - no further processing) , Earlier it was in status 51 with the status text "INVALID DATE' .
How to find out for which particular date field's the error is being thrown..?? what is the approach to find out the root cause of the issue.?? the IDOC is being sent to R3 through XI.
Plz give suggestions on how to tackle the issue.
Thanks in advance,
Jai

Hi ,
The idoc Status for 59 and 51 for indound idoc is....
68 Error - no further processing
51 Application document not posted
the possible solution is checkthe Partner profile for the Idoc and Port number..
and go to T_code we20 and check the Partner.and check the Syntax in the application tool bar...
then you will come to know the problem..
Regards,
Prabhudas

Any BADI returning the 'IDOC Status' during IDOC generation.

Hello All,
I need a BADI which is being called during any IDOC generation and which returns the 'IDOC Status' i.e. Pass/Fail etc.
So far I am able to find BADIs like 'IDOC_DATA_MAPPER' or ''IDOC_DATA_INSERT'' but such BADIs only return the IDOC document number.. they do not return any information on IDOC Status (the field Status field remains blank).
Can any one suggest some solution on this please.
Regards
Vikas Gupta

Hi Erik,
Thanks for your reply, though i was able to get the status from BADI IDOC_DATA_MAPPER itself (earlier there were some config issues...which were creating some problems) but thanks for letting me know about table EDIDS, it helped at places.
Regards
Vikas Gupta

IDoc status 51 - LSMW for Creating Purchasing Info Records

Dear All,
My req is to create a Conversion for Purchasing Info Records. LSMW's IDoc method is used to develop this conversion wherein Message Type "INFREC" and Basic Type "INFRECMASS01" are being used.
In the 14th step (Start IDoc Processing), I 'am getting the IDoc status "51" and Status Text "Application document not posted". If I double click on respective IDoc number, I got its Control record, Data records, and Status records; in the status records I can see "51" in Red color with the message "Function module not allowed: IDOC_INPUT_INFREC". If I double click on this it asks me to check the process code...
Request you guys to resolve the issue....
Solution will b rewarded.. Thanks in advance....

I shouldnot use basic type INFREC01 instead of NFRECMASS01.
'coz Within the FM there is a check for basic type like:
check idoc type
if f_idoc_control-idoctp c_idoctp_infrec01. " INFREC01
raise wrong_function_called.
endif.
Even one can go to WE57 and see the basic Type INFREC01 assigned to the FM IDOC_INPUT_INFREC, hence one shud use this basic type...

IDoc status 51 - LSMW for Creating Purchasing Info Records using IDoc meth

Dear All,
My req is to create a Conversion for Purchasing Info Records. LSMW's IDoc method is used to develop this conversion wherein Message Type "INFREC" and Basic Type "INFRECMASS01" are being used.
In the 14th step (Start IDoc Processing), I 'am getting the IDoc status "51" and Status Text "Application document not posted". If I double click on respective IDoc number, I got its Control record, Data records, and Status records; in the status records I can see "51" in Red color with the message "Function module not allowed: IDOC_INPUT_INFREC". If I double click on this it asks me to check the process code...
Request you guys to resolve the issue....
Solution will b rewarded.. Thanks in advance....

U should use basic type INFREC01 instead of NFRECMASS01.
Within the FM there is a check for basic type like:
check idoc type
    if f_idoc_control-idoctp <> c_idoctp_infrec01. " INFREC01
      raise wrong_function_called.
    endif.
Edited by: Joyjit Ghosh on Sep 15, 2008 4:57 PM

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

IDOC Status message

HI
I have to pick IDOC status message in my report program. For this I am referring the table EDIDS. My doubt is some times the IDOC status message is storing in the field STATXT and some times the idoc status message is storing in the fields STAPA1, STAPA2, STAPA3,STAPA4. How come I know I mean from which field I need to pick status message in my report program. I am giving idoc number as input to the table EDIDS. If possible please send me the sample code to resolve this problem. I will give points.
Thanks a lot in advance.

Hi,
STAPA1, 2, 3 & 4 are the place holder values for the message..
If you have a message in SE91..like
Sales order & created.
The & will be given in the program where it displays the message.
MESSAGE s208(00) WITH vbak-vbeln.
The vbak-vbeln value will be stored in field STAPA1.
Thanks
Naren

Updating IDoc Status through PI

Hello Experts,
We are sending an IDoc to a third party system through PI 7.1. From there we are planning that they will send a acknowledgement. It will contain the Idoc number and its status (whether it got processed at their end or not).
The requirement is that according to the status we have to update the IDoc status in R/3 system through PI 7.1.
Kindly elaborate on how to do this? Are there some scenarios done like this?
Thanks in advance,
Suraj Sawarkar

Hi Suraj,
Check this: call the RFC 'WDLD_EDI_STATUS_SET'. Pass it the Idoc number(s) and status.
Another alternative is given here
http://sap.ittoolbox.com/groups/technical-functional/sap-dev/post-idoc-status-record-using-an-rfc-2539010
Regards
Suraj

Reg idoc status check

Hi i have to check the idoc status 51 or 68 how to write the code

Execute the program RC1_IDOC_SET_STATUS.
enter the Idoc number , present status , New status and execute.
Check this link
http://www.erpgenie.com/sapedi/idoc_statuses.htm
Regards

IDOC status 56 Interlocutor Number

Similar Messages

Maybe you are looking for