IDOC status 30 even if I set transfer IDoc immediately in we20

Hi All,
I am creating Bommat IDocs using 'MASTER_IDOC_DISTRIBUTE' .I am getting the 30 status instead of getting status 3.
Even if I set transfer IDoc immediately in we20.
Please let me know how to resolve this.
Thanks,
Vinay.

Hi Vinay parakala
Schedule back ground job to program RSEOUT00 regularly to process the 30 status idoc....
Your program generates the idoc ... and RSEOUT00 will process you idocs which are in 30 status...
i hope above info helps you
Note: enter Message type BOMMAT in program RSEOUT00
Thanks
Ramesh

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.

Idoc Status error 29 for Out bound Idoc( Receiver of IDoc is its own logic)

I try to create the Out bound Idoc with messag type WMMBXY ( basic Idoc type - WMMBID02 ).
which is configured with the out put type XXXX in VT01N( shippment creation). But I am getting the error status 29 in the Idoc.
Only I am passing the sender, receiver port , partner type and partner function to the communication structure.
Could you please tell me , what is the issue with the partner type configuration .

Hi,
Error 29 occurs when there is an incomplete or no partner profile maintained.
Check whether you have done the correct partner profile settings in WE20 outbound parameters.
For the partner no defined in Idoc check whether there is an entry(under partner type LI, KU or LS)
with correct message type WMMBXY and Idoc type WMMBID02. Also check for message function code.
Regards,
Savitha

Outbound IDoc status set as 31

Hi Friends,
I am working on the outbound IDoc interface IDOC_OUTPUT_ORDRSP. I modify/add few segments based on the business conditions using the user-exit EXIT_SAPLVEDC_003 (ZXVEDU15). According to the business need, I have to set the IDoc status record as 31. Now IDoc is being created with status record as 30. Is there any way to set the status record with status 31 within the scope of this IDoc interface IDOC_OUTPUT_ORDRSP.
Pls let me know if any user exit for this same purpose. If not possible to set status explain me the reason for that.
Thanks
Hari

Hi,
You can use this standard program RC1_IDOC_SET_STATUS to change IDoc status 30 to another status.
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.
Reward points
Regards
Message was edited by:
 skk

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 ALEAUD01.
The function IDOC_INPUT_ALEAUD takes automatically this IDOC and writes the status to the origin IDOC.
Regards Mario

Transfer IDOC Immed.

Hi
I’ve created a Z message type to transfer transactional data from SAP EEC6 to external system (MES) using iDOCs.
Distribution model was created and profiles were updated in WE20 (outbound parameters).
Radio button “Transfer IDOC Immed.” was also set.
When we create idocs, they are not transferred immediately. In BD87 they are assigned to status 30.
However, they are successfully transferred when using program RSEOUT00.
Why is setting “Transfer IDOC Immed.” ignored?
Thanks
W

Hi Eng Swee
Thanks for your prompt response.
Yes we are using a custom program to generate idoc (we used FM MASTER_IDOC_DISTRIBUTE).
We’ve changed it now to ALE_IDOCS_CREATE together with EDI_DOCUMENT_DEQUEUE_LATER.
All is working except for the logical system that we must hardcode in the program.
With FM MASTER_IDOC_DISTRIBUTE this was not required.
Is there a way to get past this?
Regards
W

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

IDoc Status Messages

Hi All, Is there any Function Module or standard report which will list out all the Status messages of an IDoc...Basically i need to capture all the segments which are in error state... In EDIDS table i am not able to link to a particular segment.
Please help me out
Thank You,
Regards,
Swaroop Patri...

HI,
ALE/IDOC Status Codes/Messages----
01 Error --> Idoc Added
30 Error --> Idoc ready for dispatch(ALE Service)
then goto SE38 --> Execute the Program RBDMIDOC
29 Error --> ALE Service Layer
then goto SE38 --> Execute the Program RSEOUT00
03 Error --> Data Passed to Port ok
then goto SE38 --> Execute the Program RBDMOIND
12 Error --> Dispatch ok
Inbound Status Codes
50 Error --> It will go for ALE Service Layer
56 Error --> Idoc with Errors added
51 Error --> Application Document not posted
65 Error --> Error in ALE Service Layer
Regards
Sudheer

Error in idoc status

hI all,
can any one tell me "ERROR_WRITING_IDOC_STATUS " why this exception will raise.
Thanks,
Prakash .S

Just check this.
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
        EXPORTING
             VALUE(MASTER_IDOC_CONTROL) LIKE EDIDC STRUCTURE EDIDC
               " Control record of master IDoc
             VALUE(OBJ_TYPE) LIKE SERIAL-OBJ_TYPE DEFAULT ''
             VALUE(CHNUM) LIKE SERIAL-CHNUM DEFAULT ''
       TABLES
              COMMUNICATION_IDOC_CONTROL STRUCTURE EDIDC
               " Control records of created comm. IDocs
              MASTER_IDOC_DATA STRUCTURE EDIDD
               " Data records of master IDoc
       EXCEPTIONS
              ERROR_IN_IDOC_CONTROL
               " Incorrect entry in IDoc control record
              ERROR_WRITING_IDOC_STATUS
               " Error when writing IDoc status records
              ERROR_IN_IDOC_DATA
               " Incorrect entry in IDoc data records
              SENDING_LOGICAL_SYSTEM_UNKNOWN
               " Own logical system unknown

Remove Idoc Status Message

Hi,
Is there any way we could remove the IDoc status message after IDoc posted successfully? I have created the customized idoc status and want to remove the standard message since it is overlapping message.
Any helps is very much appreciated.
Thanks.
regards,
Faread

Hi,
IDOC systat01 can be used to change
the IDOC status very easily
(you put the idoc number and new idoc status basically)
http://help.sap.com/saphelp_46c/helpdata/EN/75/4b3c1cd14811d289810000e8216438/content.htm
REgards,
Vasanth

EDI - 753Routing Request and 754 Routing Instructions transactions- what SAP ECC6 EDI output type, msg type, msg code, basis idoc is best practice to generate the idoc?

One of our Trading Partner wishes to implement the 753 Routing Request and 754 Routing Instructions. Can anyone give me best practice answer the following Questions? We are on SAP ECC6 R3
What Application? i.e. V2, V7?
What output condition to use? i..e. LALE, LAT2, SEDI????
What Message type? i.e SHPADV?
What Basic Idoc Type? i.e SHPMNT05?
What Message Code? i.e. SHPM?
What Process Code? i.e. SHPM??
What Function Module? i.e. IDOC_OUTPUT_SHPMNT??
Does the SAP Transpotation Module have to be configured for this to be implemented?
Your comments are greatly appreciated, we have until Nov 1 to be compliant?

Good Morning,
While I did not get any responses from my question, yes, I was able to determine what needed to be configured. I hope the below will help you: This is for SAP ECC6
The output application for the 753 Routing Request is "V7"
The output type is "SEDI"
Transmission medium is "6"
The Basic Idoc type is "Shipmnt05"
when setting up your Partner Profile (WE20) add:Message Partner Role "SP" with Message type "SHPADV', Message coed "753", Basic Type "SHPMNT05", Message Control add Application "V7", Message type "SEDI", Process Code "SHPM".
also http://scn.sap.com/thread/698368 pages 14 and 15 were helpful.
I have not configured the Inbound 754. For now the inbound 754 Routing Instructions will be emailed to our traffic department.
Thank you,
Have a great day,
jane

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.

Idocs are unable to transfer from R3 to PI system, IDOC status is 03

Hello Gurus,
Idocs are unable to transfer from R3 to PI system, IDOC status is 03
in sm58 getting below error
RFC are working fine
"EDISDEF: Port SAPCEP segment defn Z2SH_DESCR000 in IDoc type MATMAS03 CIM"
Regrds
vamsi

Hi,
I am also facing same problem, Can any one suggest me what is the issue..

How can i set the IDOC Status to 03 without doing a "COMMIT WORK"

Hello Geeks,
I want to set the status of the Outgoing IDOC to 03 , without doing a "COMMIT WORK" . Actually only after i do a commit work are my IDOCs dispatched. But with a commit work the IDOCs are dispatched immidiately. I do not want to dispatch it immidiately. Instead i want to hol the IDOCs till my LUW finishes , but the IDOC status should be set to "03" instead of "30".
Thanks,
Bashir

Hi,
After collecting all the idocs which are under status 30, run the program RSEOUT00 to change the status from 30 to 03.
If you want to do this process automatically then set the program RSEOUT00 in background.
Regards,
Lokeswari.

Set idoc status

Dear experts,
i have an idoc which i work with. My Problem is:
how can i set the idoc status to 51 and mark it as corrupted ?
or how can i let the system mark it like this if it is not possible to do it myself ?
Thanks a lot and best regards
René

Presumably, the 51 status has been triggered by some error condition in your process code. That error condition should have a message associated with it. You should have a table or structure that stores these messages and then at the end of your processing, add those messages to the IDOC_STATUS table. You can also add messages for status 53 (such as the document numbers that you have created), status 68, or any other status value. Look at examples of standard process code and you'll see what I mean but here are a few code snippets:
Conditional error message:
    GV_IDOC_ERROR_FLAG = 'X'.
    GV_STATUS          = C_IDOC_STATUS_51.
    MESSAGE E199(ZCORP) WITH GS_DEL-VBELN INTO GV_MESSAGE.
    PERFORM F9999_ADD_MESSAGE.
Setting the status, adding the messages to the IDOC in a subroutine at the end of processing:
CLEAR IDOC_STATUS.
LOOP AT GT_MESSAGES INTO GS_MESSAGES.
    IDOC_STATUS-DOCNUM = P_DOCNUM.
    IDOC_STATUS-STATUS = GV_STATUS.
    IDOC_STATUS-MSGTY = GS_MESSAGES-MSGTY.
    IDOC_STATUS-MSGID = GS_MESSAGES-MSGID.
    IDOC_STATUS-MSGNO = GS_MESSAGES-MSGNO.
    IDOC_STATUS-MSGV1 = GS_MESSAGES-MSGV1.
    IDOC_STATUS-MSGV2 = GS_MESSAGES-MSGV2.
    IDOC_STATUS-MSGV3 = GS_MESSAGES-MSGV3.
    IDOC_STATUS-MSGV4 = GS_MESSAGES-MSGV4.
    APPEND IDOC_STATUS.
    CLEAR IDOC_STATUS.
ENDLOOP.
IF SY-SUBRC NE 0.
    IDOC_STATUS-DOCNUM = P_DOCNUM.
    IDOC_STATUS-STATUS = GV_STATUS.
    APPEND IDOC_STATUS.
    CLEAR IDOC_STATUS.
ENDIF.

IDOC status 30 even if I set transfer IDoc immediately in we20

Similar Messages

Maybe you are looking for