Error in Idoc ORDERS02 in PEINH field

Hi all
We have SRM 7 and ECC 6.4, we use scenario MM-SUS.
When I send a PO from MM to SUS, the idoc ORDERS02 is sending ok. But in PI I found an error "rRequest/PurchaseOrder/Item/Price/NetUnitPrice/Ba"
The PI team informs me that this error occurs in the PEINH field.
Any suggestion of solution?

Sudha
Generally the Idoc structure get disturbed if any of the mandatory segments are missing or the edidd internal table is not populated as specified in IDOC type.
You can use the error status 26, but dont forget to
populate the error type "E" in the internal tables.
please let me know if this helps

Similar Messages

Tax and pricing info are not flowing into Idoc orders02-eledp04 and 05

Hi,
We are carrying out SRM5.5 -SUS and ECC6.0 Integration using PI 7.
We are configuring for the MM-SUS Scenario.
Now,to accomodate the Tax / Pricing we have installed the add on
component LOCINSUS and we are having doubts on how to use it:
1) Tax and pricing information are not flowing into IDOC- orders02
(e1edp04 and e1edp05 segments are not present in the created IDOC). The
condition print indicator in checked on ECC System and we have also
implemented SAP note 995986.
2)In create ASN transaction , we are not able to see the Excise Invoice
Number and Date field in Basic data tab as expected from SAP Library
document although we have installed the Localization Add on component.
Please help us to reso1ve these issues,
Regards,
Mani
099890-22217.

Mani,
Did you resolve this issue, because we are having the same issue in ECC6 with IDoc ORDERS02.
If you did resolve this issue could you please let us know how, much appreciated.
Bill.

Idoc Error - EDI: Syntax error in IDoc (segment cannot be identified)

Hi All,
have created a new reduced message type for our new vendor A/C group through BD53. Also done reqd config for sending the vendor master through this message type. .
I have created couple of vendors for testing with X01 with withholding tax functionality and when try to send these vendors , Idocs are getting failed .
When I create vendor without withholding tax functionality , idoc is getting posted succesfully . If create vendor with entries in the feild whih are related to withholding tax . Idocs are getting failed .
If I see the status in WE05 ,Idocs which are posted succefully are showing the basic type as CREMAS03 . For idocs which are getting failed have the basic type as CREMAS04 and also the extension as Z1CREMAS . I don`t understand why the system is defaulting CREMA04 & Z1CREMAS when I send the vendor master with withholding tax feild entries.
I am not much familiar with ALE /Idoc set up. Please can any body help me to resolve the issue.
The error message in we05 as below
EDI: Syntax error in IDoc (segment cannot be identified)
Message no. E0078
Diagnosis
The segment Z1LFA1M does not occur at the current level of the basic type CREMAS04 (extension Z1CREMAS).
This error can have several reasons:
The segment Z1LFA1M is assigned to a group whose header segment does not occur.
The segment Z1LFA1M does not exist in the syntax description of the basic type CREMAS04 (extension Z1CREMAS).
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 CREMAS04 (extension Z1CREMAS).
Thanks

Hi,
I don`t understand what do you mean release after adding segment.
Message type works i.e. Idoc get posted if I send with the vendor w/o withholding tax field entries. Idoc fails when send vendor with withholding tax field entry.
Regards

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.

Issue:EDI: Syntax error in IDoc (mandatory segment missing):Idoc extention

Hi all,
I have extended the the standard IDOC MATMAS05 classification view with structure as below-
E1MARAM                        Master material general data (MARA)--->Mandatory segment
     Z1KLART                        KLART --->Extended chaild to E1MARAM
         Z1CLASS                        segment for class --->Extended chaild to Z1KLART
         Z1CHARACTERISTIC               CHARACTERISTIC --->Extended chaild to Z1KLART
     E1MARA1                        Additional Fields for E1MARAM
     E1MAKTM                        Master material short texts (MAKT) --->Mandatory segment(Child   to
E1MARAM )
I am getting an error in IDOC fro material master as:EDI: Syntax error in IDoc (mandatory segment missing ).
Diagnosys By system is :*The segment E1MAKTM has the attribute 'Mandatory' in the syntax description of the basic type MATMAS05 (customer enhancement ZMATMAS05). However, the segment is missing in the IDoc. The segment number logged in the status record identifies the item before which the segment is missing.
This error may have been triggered by an unidentifiable segment before the expected mandatory segment.*
Please help to resolve the issue.
Thank you.
Edited by: sanu debu on Apr 30, 2009 11:25 AM
Edited by: sanu debu on Apr 30, 2009 11:31 AM

Hi,
   You cannot add an segment in the middle of other segments.
YOu have to add any segment at the last.
If you want to add a segment as the child of another segment, it should be added after the last child of the parent segment.
In you case, you have to add your segment after the E1CUCFG segment.(NOt under that segement)
Regards,
Ravi Kanth Talagana

Error in IDOC: XML IDoc conversion: No known segments identified

Hi Team
i am facing error in my scenario. When we are testing my interface, another Interface is picking up the Messages and resulting into an error.
There is no mapping involved in my scenario.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
<SAP:P1>XML IDoc conversion: No known segments identified</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error: XML IDoc conversion: No known segments identified</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
please help me out
thanx in advance

Hi,
Do The following:
1) Delete the IDX2 entry and try to reimport once again....and in the IR also do the same.
2) Have a look into this SAP Note- 742093
3) Check the IDX1 entry , RFC destination entry... may be not pointing correctly.
4) If any field which is mandatory in the idoc must not be disabled...take care about it.
Hope this will help you...
Regds,
Pinangshuk.

EDI: Syntax error in IDoc (mandatory group/segment missing)

hi EDI/IDoc experts,
Need you help urgently. According to the requirement, i need populate a segement E1IDT01 of basic type PEXR2002 . I added the code , then run and generate an idoc , the new segment
E1IDT01 was populated, but Syntax error 26 happend. Error message as below.   It also strange that i can see E1IDKU5 populate out as usual, but some others segment disappeared , i am sure that in my code ,i didn't changed any variable related to other segement . how can i fix this problem?
EDI: Syntax error in IDoc (mandatory group missing)
Message no. E0079
Diagnosis
The segment group E1IDKU5 has the attribute 'Mandatory' in the syntax description of the basic type PEXR2002 (customer enhancement ). However, the segment group is missing in the IDoc. The segment number logged in the status record identifies the item before which the segment group is missing.
Procedure
Please check the IDoc or the syntax description of the basic type PEXR2002 (customer enhancement ).

Hi all,
Thanks so much for your concern!
Finally ,this problem has been figured out .
Requirement is user want to use segment E1IDT01 in idoc to populate the long text they maintained in accounting document vendor item line (use FB01 to create accounting doc).
Why I made out " EDI: Syntax error in IDoc (mandatory group/segment missing)" this message out ,because I didn't fill data correctly. I missed to keep SY-TABIX in momory .
when we use Function module ,or do..enddo...or read table it_table. we should be careful that SY-TABIX is changed .So we can't just use MODIFY EDIDD_TABLE INDEX SY-TABIX in the last . we should define a local variable to keep SY-TABIX in memory and then use it to modify EDIDD_TABLE.
Follow is the final code.
IF SEGMENT_NAME = 'E1IDT01'.
TABLES :STXL.
* Define for long text getting
DATA: LIT_TLINE LIKE TLINE   OCCURS 0 WITH HEADER LINE.
DATA: LV_STRING(2000) TYPE C.
DATA: LV_TDNAME TYPE THEAD-TDNAME,
        LV_ID     TYPE THEAD-TDID     VALUE '0001',
        LV_LANG   TYPE THEAD-TDSPRAS VALUE 'E' ,
        LV_OBJ    TYPE THEAD-TDOBJECT VALUE 'DOC_ITEM'.
data:   LV_LINE   TYPE I,                " long Text lines
        LV_LEN    TYPE I,                " long Text length
        LV_TABIX LIKE SY-TABIX.
* Clear memory
CLEAR:LV_TDNAME,
        LV_STRING,
        LV_LINE,
        LIT_TLINE, LIT_TLINE[],
        LV_LEN,
        LV_TABIX.
* Keep sy-tabix memory using a variable--This is the key point
LV_TABIX = SY-TABIX.
* Combine TDNAME with company code + accounting doc + fiscal year + item number.
    CONCATENATE REGUP_DATA-BUKRS REGUP_DATA-BELNR
                 REGUP_DATA-GJAHR REGUP_DATA-BUZEI INTO LV_TDNAME.
* When vendor item has long text , read long text into lv_string
    SELECT SINGLE *
      FROM STXL
      WHERE TDOBJECT = LV_OBJ
        AND TDNAME   = LV_TDNAME
        AND TDID     = LV_ID
        AND TDSPRAS = 'E'.
    IF SY-SUBRC = 0.
      CALL FUNCTION 'READ_TEXT'
        EXPORTING
          CLIENT   = SY-MANDT
          ID       = LV_ID
          LANGUAGE = LV_LANG
          NAME     = LV_TDNAME
          OBJECT   = LV_OBJ
        TABLES
          LINES    = LIT_TLINE.
      IF NOT LIT_TLINE[] IS INITIAL.
        DESCRIBE TABLE LIT_TLINE LINES LV_LINE.
        DO LV_LINE TIMES.
          READ TABLE LIT_TLINE INDEX SY-INDEX.
          CONCATENATE LV_STRING LIT_TLINE-TDLINE INTO LV_STRING.
        ENDDO.
        LV_LEN = STRLEN( LV_STRING ).
* Make sure we only need less than 840 charicters
        IF LV_LEN > 840.
          LV_STRING = LV_STRING+0(840).
          LV_LEN    = 840.
        ENDIF.
* Populate Vendor item long text with segment E1IDT01 start from
* Fields TXT03 to TXT14.
         EDIDD_TABLE-SDATA+147(LV_LEN) = LV_STRING.
        MODIFY EDIDD_TABLE INDEX LV_TABIX.
      ENDIF.
    ENDIF.
ENDIF.

Error During IDoc Processing

Hi friends,
i want to transfer data in between two systems.
i have created my own message type = ZSACH
Basic type = ZSACH1
segement = ZSACH
model view = new_model
when i am execuiting this IDOC by using the program i am getting the error as
EDI: Syntax error in IDoc (segment cannot be identified)
here i am giving the coding what i have write in my program
parameters :p_logsys like tbdlst-logsys.
data : gen_segment like edidd-segnam value 'ZSACH1'.
data : control_dat like edidc,
       control_dat1 like edidd,
      gen_data like zsach .
tables : zsach1.
data: begin of inttab occurs 0,
        lname type zsach1-lname,
        fname type zsach1-fname,
      end of inttab.
data :
      int_edidd like edidd occurs 0 with header line,
      int_edidc like edidc occurs 0 with header line.
select * from zsach1 into corresponding fields of table inttab.
if sy-subrc ne 0.
message 'no data' type 'I'.
exit.
endif.
control_dat-mestyp = 'ZSACH'.
control_dat-idoctp = 'ZSACH1'.
control_dat1-segnam = 'ZSACH'.
control_dat-rcvprt = 'LS'.
control_dat-rcvprn = p_logsys.
loop at inttab.
gen_data-lname = inttab-lname.
gen_data-fname = inttab-fname.
int_edidd-segnam = gen_segment.
int_edidd-sdata = gen_data.
append int_edidd.
endloop.
call function 'MASTER_IDOC_DISTRIBUTE'
exporting
    master_idoc_control                  = control_dat
*   OBJ_TYPE                             = ''
*   CHNUM                                = ''
tables
    communication_idoc_control           = int_edidc
    master_idoc_data                     = int_edidd
exceptions
   error_in_idoc_control                = 1
   error_writing_idoc_status            = 2
   error_in_idoc_data                   = 3
   sending_logical_system_unknown       = 4
   others                               = 5
if sy-subrc <> 0.
message id sy-msgid type sy-msgty number sy-msgno.
else.
loop at int_edidc.
    write :/ 'IDOC GENERATED',int_edidc-docnum.
endloop.
commit work.
endif.
<Added code tags>
can anyone give better solution for this error..
i have searched in SDN but i can't get the better document
thanks in advance.
Regards,
kk
Moderator Message: Please use "code tags" to format your code.
Edited by: Suhas Saha on Nov 9, 2011 12:59 PM

Hello kk,
It is very clear from the error message
EDI: Syntax error in IDoc (segment cannot be identified)
that there is some problem with the segment name.
When i look at your code snippet i can see there is a mismatch in the segment names passed in the IDoc control rec & the data rec.
control_dat1-segnam = 'ZSACH'.
int_edidd-segnam = gen_segment. "gen_segment like edidd-segnam value 'ZSACH1'
BR,
Suhas
PS: Before searching in SDN try to put-in some self-effort, saves time actually

Reason for errors in IDOCS ? pls tell small scenarios

hi pls tell practical scenarios reason for errors in idocs? all ale configuration are done.

goto se16 and look at table EDIDS....in that look at field status text...you will see different reasons when something goes wrong in idoc generation...
there should be a lot of practical scenario examples for you inside it...

Regarding EDI: Syntax error in IDoc (segment cannot be identified)

Hi,
My requirement is that I was adding two diffrent field values under two diffrent segments as "E1EDKA1" and "E1EDK02" in outbound invoice IDOCS, INVOIC02 (process code: SD09 - IDOC_OUTPUT_INVOIC).
I am getting the IDOC number through Tcode "VF02". Can any body give me idea how to check that syntax error in debug mode.
Please find the following error details using TCODE "WE02".
*EDI: Syntax error in IDoc (segment cannot be identified)*
*Message no. E0 078*
*Diagnosis*
*The segment E1EDKA1 does not occur at the current level of the basic type INVOIC02 (extension ).*
*This error can have several reasons:*
*The segment E1EDKA1 is assigned to a group whose header segment does not occur.*
*The segment E1EDKA1 does not exist in the syntax description of the basic type INVOIC02 (extension ).*
*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.*
Please help me to resolve this problem. <REMOVED BY MODERATOR>
Regards,
Skumar.
Edited by: Alvaro Tejada Galindo on Apr 28, 2008 1:09 PM

It seems that you added segment E1EDKA1 at a place where it is not supposed to be. That's where this error is coming from. The structure of every IDOC is definded by SAP standard and you cannot change the sequence or the level of standard segments. If you require a certain field at a certain level you have to add that field to a Z-segment and then add that Z-segment where appropriate in your extension.
Hope that helps,
Michael

ORDERS02 segment E1EDKT1 field TDID permitted values

Hi all!
In the documentation of IDOC ORDERS02 (WE60) for segment E1EDKT1 and field TDID I can see a number of permitted values, e.g.:
TDID Text ID
Internal length 000004 External length 000004 Offset 000063
Data type CHAR Data element EDI4451_A
Permitted values:
'001' Purchase order header
'002' Purchase order memos
'003' Sales order header text
'004' Sales order item text
'005' Bill header text
'006' Bill item text
'007' General information
'PMD' Reason for payment
'WE' Goods import
'TR' Transit trade
'DK' Services, capital transactions, other
'FD' Financial document
'0013' Terms of payment
'0010' Form supplement text
Question: Where can I find the config for adding more text IDS, that is allowing other texts to be used in ORDERS02? I assume it's config, but please point me to where I can find where this list of text IDs is maintained.
Thanks!
Best regards,
::Ellen

Hi Ellen,
The values possible for the text ids depends on the configuration of the text ids for the business document for which the ORDERS02 idoc is used...
For example, if the idoc is used to create a sales order then the possible values would be from the following path in SPRO..
Sales and Distribution --> Basic Functions --> Text Control --> Define TExt Types --> sales document(header/item) --> Display
For a purchase order...
Material Management --> Purchasing --> Purchase Order --> Texts for Purchase Order --> Define TExt types for Header/Item Texts...
Thanks,
Renjith

Error message is not telling which field causing the issue!

Hello
I am developing the Adobe Interactive Form and launching this form from WebDynPro ABAP application, fine.
This form has tonns of dropdown fields, mandatory fields, greyed out fields. Fine.
I am filling the list the drop-down fields from webdynpro ABAP, but, i am filling list for only 80% of the drop-down fields, rest 20 % is not filling at all (bcz, business want to have those 20% dropd-owns on the form by thinking going further they require, this moment they dont need so they dont want to fill the lists)
Now the form is launching on the browser, fine. But when user submits it i am getting the below erro:
The Entered Value Is Not on the List of Valid Values. (I am guessing this error is talking about the DROPDOWN fields only)
I hv tonns of drop-down fields, so, its very difficult for me to go and trace each and every drop-down fielld!! But, i checked all the populated/entered values in the drop-down fields, they are all fine. Sone dropd-down fields are GREYED OUT, they are defaulted from webdynpro ABAP
Pls. let me know How can know which field/drop-down is causing this issue? Wht are the possible causes for this error? Error is not telling which fields is making issue?
How can i trace and how can i fix it, pls. let me know
Thank you

Thank you for your tips.
But, as of my knowledge every thing (case sensitive, list box entries) are fine, not sure, why am getting this error! I will double chk again.
But, thing is.... actually, i have 4 pages, depending on the logged in user, i will HIDE the pages (say, for me the 3 rd page will be hidden), i am hiding the pages by using JavaScript in the form.
So, this error is not coming if i execute/launch all the 4 pages, but, its coming if i hide any page for any user!!
By chance, do we debug to figure out which FIELD is CAUSING issue/this error?
From where this message is coming, i mean, from the SAP's JAVA stack? Wht is the message ID and #?
or is it Adobe's/Form's error?
Thank you

Error in Idoc with status 26

Hi,
IDOC showing an error messge when syntex check.
EDI: Syntax error in IDoc (segment cannot be identified)
Diagnosis:
The segment E1EDP19 does not occur at the current level of the basic type ORDERS01 (extension ).
This error can have several reasons:
The segment E1EDP19 is assigned to a group whose header segment does not occur.
The segment E1EDP19 does not exist in the syntax description of the basic type ORDERS01 (extension ).
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.
Please help me....
Regards,
Sudha

Hi,
I have pasted a portion of my code:
DATA: BEGIN OF GT_EDIDC OCCURS 0.
        INCLUDE STRUCTURE EDIDC.
DATA :END OF GT_EDIDC.
DATA: BEGIN OF GT_EDIDC1 OCCURS 0.
        INCLUDE STRUCTURE EDIDC.
DATA :END OF GT_EDIDC1.
DATA: BEGIN OF GT_EDIDD OCCURS 0.
        INCLUDE STRUCTURE EDIDD.
DATA :END OF GT_EDIDD.
DATA : BEGIN OF GT_Z1ZPSOBJLOC OCCURS 0.
        INCLUDE STRUCTURE Z1ZPSOBJLOC. ' segment name
DATA : END OF GT_Z1ZPSOBJLOC.
* Control Record
FORM BUILD_CONTROL_RECORD .
GT_EDIDC-MESTYP = C_MESTYP.
GT_EDIDC-IDOCTP = C_IDOCTP.
GT_EDIDC-DIRECT = C_1.
APPEND GT_EDIDC.
ENDFORM.                    " built_control_record
*&      Form built_data_record
* Data record
FORM BUILD_DATA_RECORD .
LOOP AT GT_Z1ZPSOBJLOC INTO WA_Z1ZPSOBJLOC.
    GT_EDIDD-MANDT = SY-MANDT.
    GT_EDIDD-SEGNAM = C_SEG.
    GT_EDIDD-SDATA = WA_Z1ZPSOBJLOC.
    APPEND GT_EDIDD .
PERFORM DISTRIBUTE_DATA.
ENDLOOP.
ENDFORM.                    " built_data_record
*&      Form distribute_data
* Distribute Data
FORM DISTRIBUTE_DATA .
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
    EXPORTING
      MASTER_IDOC_CONTROL            = GT_EDIDC
    TABLES
      COMMUNICATION_IDOC_CONTROL     = GT_EDIDC1
      MASTER_IDOC_DATA               = GT_EDIDD
    EXCEPTIONS
      ERROR_IN_IDOC_CONTROL          = 1
      ERROR_WRITING_IDOC_STATUS      = 2
      ERROR_IN_IDOC_DATA             = 3
      SENDING_LOGICAL_SYSTEM_UNKNOWN = 4
      OTHERS                         = 5.
CASE SY-SUBRC.
      WHEN 1.
      MESSAGE E004.
    WHEN 2.
      MESSAGE E005.
    WHEN 3.
      MESSAGE E006.
    WHEN 4.
      MESSAGE E007.
    WHEN 5.
      MESSAGE E008.
    WHEN OTHERS.
* Do Nothing
ENDCASE.
COMMIT WORK.
* Clear IDOC data internal table after use
CLEAR GT_EDIDD.
REFRESH GT_EDIDD.
ENDFORM.                    " distribute_data
Hope it proves useful.
Regards,
Gayathri

Material Master - Error M3 826 Maintenance status of field ... to screen

Hi Experts of the Material Master,
I am getting the error M3 826 "Maintenance status of field MARA-BEHVO does not correspond to status of screen K" when all screens are selected in the Create Material Master transaction.
Here is my situation: I have added the fields MARA-BEHVO and MARA-TEMPB both of status L (Storage) to a screen called "Phys. Characteristics", which has status K (Basic data).
This produces the error message above in standard SAP. I didn't want to change the customizing of the screen to allow L, because this screen is also used by other material types.
I had to copy the screen MGD1 2701 (Phys. Characteristics) to my custom program for Material Master screens anyhow, as the number of fields and their descriptions had to be adjusted.
The program was created using the activity "Create Program for User Subscreens" in SPRO.
in the coding of ZMGD1 screen 2701 I have added this code behind the standard module FELDAUSWAHL to manipulate the standard logic that would blend out L fields on a K screen.
LOOP AT SCREEN.
*   Material Type
    IF mara-mtart = 'ZPNT'.
*     Screen-Names of the 3 fields
      IF screen-name = 'MARA-TEMPB' OR
         screen-name = 'MARA-BEHVO'.
        screen-active      = 1.
        screen-invisible   = 0.
        screen-output      = 1.
*       Change or Create transaction
        IF sy-tcode = 'JP27' OR sy-tcode = 'JP28'.
          screen-input       = 1.
          screen-required    = 1.
        ENDIF. "transaction code JP27 or JP28
        MODIFY SCREEN.
      ENDIF. "screen-name
    ENDIF. "Material Type ZPNT
ENDLOOP.
It all works fine when only a number of screens (but including the modified) screens are selected for creation.
But it fails with the message above on the modified screen when all screens are selected.
Any ideas?
Ralf

from the message, it appears that ZZKUNNR is a custom field attached to your MARA table. So, it is your System specific. I don't see ZZKUNNR available in MARA. If you look at the transaction code OMT3B (configuration for material master data screens), you can find K - Basic Data Screen in Maintenance Status field.
You may look in this area to fix your issue. Because yours is a custom field, its tough to analyse further.
Reward points, if it helps!
Regards

Error sending Idoc's to SAP

Hi,
I'm getting error in file-XI-SAP scenario. File is read and transformed to Idoc ok, but then I get this kind of error message in SXMB_MONI:
<SAP:Stack>Error: Basic type 'HRMD_A01' is unknown</SAP:Stack>
What I'm I missing in the scenario?

Hi Tapio,
Take a look at this link:
http://help.sap.com/saphelp_nw04/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
Error: No IDocs could be sent to the SAP BW using RFC.
Hope it helps you.
Cheers,
Chandra

Error in Idoc ORDERS02 in PEINH field

Similar Messages

Maybe you are looking for