EDI validation Error: Segment GS(Functional Group Header) at guideline

Hi,
I am working on EDI 272 transaction(inbound).
I created ECS file for EDI 272 and validated the EDI 272 data with ECS file in the B2B document editor. Validation was sucess in the B2B document editor
when I upload the same ECS file and tested the same in B2B. I am using EDI version 4020.
I am getting the following error,
Segment GS(Functional Group Header) at guideline position 0200 is missing. This segment's standard option is Mandatory.{br}{br}This segment was expected after:{br}{tab}Segment Count: 1{br}{tab}Character: 105

Hi Anuj,
I created new ECS file without Envelope.
Now I am getting the following exception
<errorCode>AIP-51505</errorCode>
<errorText>5020: An invalid character was encountered in a data element.</errorText>
<errorDescription>
<![CDATA[Machine Info: (dgia21a.cccis.com)
Element ISA11 data type must be 'Alphanumeric'. Segment ISA is defined in the guideline at position 010.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Position: 11 {br}{tab}Characters: 82 through 83 ]]>
</errorDescription>
<errorSeverity>2</errorSeverity>
<errorDetails>
<parameter name="InterchangeControlStandard_RepeatingSeparator" value=""/>
<parameter name="InterchangeTrailerControlNumber" value="000000001"/>
<parameter name="InterchangeChildCount" value="1"/>
<parameter name="InterchangeTime" value="1417"/>
<parameter name="InterchangeUsageIndicator" value="T"/>
<parameter name="ErrorScope" value="Interchange"/>
<parameter name="SubelementDelimiter" value=""/>
<parameter name="RepeatingSeparator" value=""/>
<parameter name="InterchangeSecurityInfo" value=" "/>
<parameter name="InterchangeReceiverQual" value="ZZ"/>
<parameter name="DecimalSeparator" value=""/>
<parameter name="InterchangeAuthorizationInfoQual" value="00"/>
<parameter name="ElementDelimiter" value=""/>
<parameter name="InterchangeComponentElementSep" value=""/>
<parameter name="InterchangeControlVersion" value="00402"/>
<parameter name="InterchangeAckRequested" value="0"/>
<parameter name="InterchangeSenderQual" value="ZZ"/>
<parameter name="InterchangeReceiverID" value="BBBBBBBBBBBB"/>
<parameter name="ReleaseCharacter" value=""/>
<parameter name="InterchangeDate" value="001212"/>
<parameter name="SegmentDelimiter" value=""/>
<parameter name="InterchangeControlNumber" value="000000001"/>
<parameter name="InterchangeAuthorizationInfo" value=" "/>
<parameter name="InterchangeSenderID" value="AAAAAAAAAAAA"/>
<parameter name="InterchangeSecurityInfoQual" value="00"/>
</errorDetails>
</Exception>

Similar Messages

  • 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 in creating function group

    Hi
    In my z function group, do i need to declare all the parameters used in function modules explicitly in any top include?.it was not declared as such in the standard function group from which i copied .

    Hello ,
    Sometimes when u copy any standard function group into ZFuntion group u will get some systax errors saynig some varaible is not defined .
    then
    goto SE37
    Enter the fucntion module  and get into function bulinder
    select EDIT Menu option and Interface Submenu option inthat u will find GLOBALIZE PARAMETERS and LOCALIZE PARAMETERS  Just do that operation u will be free of errors.
    regards

  • EDI validation error

    I am getting following error message 
    Error: 1 (Field level error)
    SegmentID: CTT
    Position in TS: 123536
    Data Element ID: CTT01
    Position in Segment: 1
    Data Value: 061766
    6: Invalid character in data element
    when I check data my CTT looks like  CTT~061766
    I tried to set allow leading and trailing space and zero under validation in trading partner configuration. It is perfectly works in my local machine.
    When I do same setting on my test environment , it doesn't work and give above error. 
    Please suggest me what could be wrong there.

    There are no such property anywhere else than on the Agreement!
    Can you do one more test
    - Submit the document that is working (without the leading zero)
    - Have a PassThru SendPort subscribe to it, and set this Port in a Stopped state.
    - Examine the Context of the suspended message, and verify that the Agreement where "Allow leading and trailing zeros" are in fact recognized as the Agreement used for this message.
    Morten la Cour

  • How to find out error segments in a group of Idocs

    Hi,
    1. For every 5 minutes Idocs are coming in to R3 from some third party systems, and this scenerio some of the Idocs are in failed status as well.
    My doubt is how to see the all segments at a time, since there might be some problem with the data, so I need to check the each and every segment all time.  Is there any way to findout all segments at a time for the group of the idocs of the same message type.
    2. How to find out the error in segments of the idoc.
    Many thanks in advance.
    Thanks.
    Ahmed.

    Hi Mujeeb Ahmed 
    I dont have SAP System in front. Any way check the menu bar, there you can fine SEGMENT WITH ERROR OPTION
    Regards
    Kumar

  • EDI: Syntax error in IDoc (mandatory group missing)

    Hi Idoc Experts !
    The error pasted in subject is what i'm getting when i'm calling function module MASTER_IDOC_DISTRIBUTE.
    THE IDOC IS GETTING GENERATED BUT HAS SYNTAX ERRORS WITH STATUS/ERROR CODE :26.
    I'm tryin to generate an IDOC with following details:
    Direction         1     Outbox
    Current status    26
    Basic type        WMMBID02
    Extension
    Message type      WMMBXY
    Partner no.       XEROX
    Partn.Type        LS
    Port              170_INVRPT
    Can anyone be of some help?
    Points guaranteed for authentic answers !
    Thanks,
    Sachin Soni

    Hi,
    While passing the idoc data, you are not passing the mandatory segment and passing the child segment. Try to add the data for the mandatory segment.
    Check and find the mandatory segments on the IDoc through WE30 .And check if all this segments are populated in the IDoc which failed ( WE02).
    Regards,
    Soumya.

  • AIP-51505 - "Segment ISA(Interchange Control Header)"

    Support,
    I seem to be having an issue with one of my trading partner setups.. I am pretty sure it is something silly but can't seem to be able to track it down. I have checked the delimiters in the partner setup as well as run the data thru the data analyzer and it all checked out. I am kinda at a loss on this one.
    Thank you for all the help
    Jaden
    Error
    Segment ISA(Interchange Control Header) at guideline position (N/A) is missing. This segment's standard option is Mandatory.{br}{br}This segment was expected after:{br}{tab}Segment Count: 0{br}{tab}Character: 1021
    Document wire message
    ISA~00~ ~00~ ~ZZ~Allied ~ZZ~UPS ~070801~2117~U~00401~000001054~0~P~+'GS~PO~Allied~UPS~20070801~2117~1054~X~004010'ST~850~1054'BEG~00~SA~57192~87007~20070724'DTM~010~20070724'TD5~~2~000001_DHL_A_2DA'N1~ST~19427~92~7984'N3~500 Oracle Pkwy'N4~Redwood City~CA~96504~US'N1~BT~19427~92~7984'N3~500 Oracle Pkwy'N4~Redwood City~CA~96504~US'PO1~1.1~2~EA~~~VP~50939~BP~6199~DV~255480'PID~F~~~~Standard Item'PO1~2.1~5~EA~~~VP~50939~BP~6197~DV~255481'PID~F~~~~Standard Item'PO1~4.1~5~EA~~~VP~50939~BP~6197~DV~255483'PID~F~~~~Standard Item'PO1~5.1~3~EA~~~VP~149~BP~7191~DV~255484'PID~F~~~~Sentinel Standard Desktop'PO1~6.1~4~EA~~~VP~2814~BP~4191~DV~255485'PID~F~~~~Vision Pad - Gold'PO1~7.1~4~EA~~~VP~50939~BP~6199~DV~255486'PID~F~~~~Standard Item'PO1~8.1~4~EA~~~VP~50936~BP~6198~DV~255487'PID~F~~~~3PL Test Item with Serial Control'PO1~9.1~5~EA~~~VP~149~BP~7191~DV~255488'PID~F~~~~Sentinel Standard Desktop'PO1~10.1~5~EA~~~VP~2814~BP~4191~DV~255489'PID~F~~~~Vision Pad - Gold'SE~29~1054'GE~1~1054'IEA~1~000001054'

    For some reason the data compressed a little with the last post. Here is the data and the ISA seems fine to me.
    Jadeen
    ISA~00~ ~00~ ~ZZ~Allied ~ZZ~UPS ~070801~2117~U~00401~000001054~0~P~+'GS~PO~Allied~UPS~20070801~2117~1054~X~004010'ST~850~1054'BEG~00~SA~57192~87007~20070724'DTM~010~20070724'TD5~~2~000001_DHL_A_2DA'N1~ST~19427~92~7984'N3~500 Oracle Pkwy'N4~Redwood City~CA~96504~US'N1~BT~19427~92~7984'N3~500 Oracle Pkwy'N4~Redwood City~CA~96504~US'PO1~1.1~2~EA~~~VP~50939~BP~6199~DV~255480'PID~F~~~~Standard Item'PO1~2.1~5~EA~~~VP~50939~BP~6197~DV~255481'PID~F~~~~Standard Item'PO1~4.1~5~EA~~~VP~50939~BP~6197~DV~255483'PID~F~~~~Standard Item'PO1~5.1~3~EA~~~VP~149~BP~7191~DV~255484'PID~F~~~~Sentinel Standard Desktop'PO1~6.1~4~EA~~~VP~2814~BP~4191~DV~255485'PID~F~~~~Vision Pad - Gold'PO1~7.1~4~EA~~~VP~50939~BP~6199~DV~255486'PID~F~~~~Standard Item'PO1~8.1~4~EA~~~VP~50936~BP~6198~DV~255487'PID~F~~~~3PL Test Item with Serial Control'PO1~9.1~5~EA~~~VP~149~BP~7191~DV~255488'PID~F~~~~Sentinel Standard Desktop'PO1~10.1~5~EA~~~VP~2814~BP~4191~DV~255489'PID~F~~~~Vision Pad - Gold'SE~29~1054'GE~1~1054'IEA~1~000001054'

  • Exception text in error segment of the header

    Hello All,
    It is well documented in SDN on how to add trace messages and then raise an runtime exception error that will stop message mapping process.
    References:
    /people/alessandro.guarneri/blog/2006/01/26/throwing-smart-exceptions-in-xi-graphical-mapping
    /people/sap.user72/blog/2005/02/23/raising-exceptions-in-sap-xi-mapping
    The exception text can be extracted from the Trace segment in SXMB_MONI. This is an acceptable way but not the best one. The "error information" button only indicates to the exception but one needs to dig out the text from the trace section.
    The ideal scenario would be to be able to write to the error segment of the message header (for e.g. "Additonal Text" section).  Has anybody worked on this / what are the mechanisms to achive this from UDF/Java functions.
    Regards,
    Varadharajan.

    Interesting Requirement. If you can figure a way out, believe me this is worth a Blog on SDN
    Meanwhile, Can you have a look at my blog and check if this can help you as a workaround,
    /people/bhavesh.kantilal/blog/2006/07/25/triggering-xi-alerts-from-a-user-defined-function
    Regards
    Bhavesh

  • Function Group

    Hi Guys,
    I have created a FunctionModule,assigned to a Function Group(lets take it up as FG123),and transported to quality without any error and activated.But the thing is,while excuting FunctionModule,am gettin an error msg tat Function group(FG123)contains error.What could be the problem?
    Please help me out in this regard.
    Warm Regards,
    Mohandoss P.

    Hi,
    Have you activated the function group?
    Why don't you create the function group with 'ZXXX
    Ok if it is activated what type of error it is giving?
    missing the include or what?
    Go to the function group & Function pool,
    And check all the include modules.
    You will come to know.
    Regards,
    madan.

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

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

    Hi All,
    Im facing the below error EDI: Syntax error in IDoc (segment cannot be identified).
    And this error is coming only for few idocs rest are getting processed successfully.
    Message no. E0078
    Diagnosis
    The segment E1EDP03 does not occur at the current level of the basic type ORDERS05 (extension ).
    This error can have several reasons:
    The segment E1EDP03 is assigned to a group whose header segment does not occur.
    The segment E1EDP03 does not exist in the syntax description of the basic type ORDERS05 (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.
    Procedure
    Please check the IDoc or the syntax description of the basic type ORDERS05 (extension ).
    Please suugest.
    Thanks,
    Spandana

    Hi,
    Is this standard program or custom program?
    you might be appending the Z segment instead of inserting it. Always best practice is get the index of the segment and instert it.
    If all the data is not populated then segment position will change incase of appending. Please check your code and revert back.
    Refer the below link for detailed information.
    IDOC Status 26: EDI: Syntax error in IDoc (segment cannot be identified).
    Thank you

  • 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

  • Error while transporting a Function Group!

    HI ABAPers!
         We have created many function modules in a single function group. While we are trying to transport the function group we succeeded in releasing the function group from the development server to the quality system. But while we are trying to import the same function group from the quality system, it is throwing an error 'FUNCTION GROUP NOT FIT IN SIZE'. what might be the reason for this behaviour and what would be the remedy? Please help this out and points would be awareded for the solutions.
    Regards,
    Kiran

    Hi,
    just an hint (i don't know if it will help u).
    Try in se37 trx , menu "Utilities", shoul be "Repair function group" (o something like that).
    Sometimes u have to do also with standard FM.
    In second step, use unconditional mode -126 in your transport (call to your system admin ho to do that).
    Hope it helps
    Bye
    Andrea
    Pls reward if it helps

  • Read-only radio group losing value on validation error

    It took quite a while to track this down, but I think I've got it narrowed down properly. I have an APEX form for updating a record in a databse table with a radio group which is conditionally read-only. If that radio group has a value AND is read-only, when the form is submitted and hits a validation error, the value of the radio group is lost.
    For example, the radio group SUBMITTED_FOR_APPROVAL is set to Y and is read-only for a given user. That user then changes something else on the form and submits it. However, the form now hits a validation error for some field. When the form reloads with the validation error displayed, all the fields are restored except the read-only radio group which is now blank. If a select list is used with the identical read-only condition, it works fine. Likewise, if a radio group is used, but the read-only condition is removed, it works fine. It is only when it is a radio group and it is read-only, that the value does not appear to be submitted to the session with all the form values whent he form is submitted.
    Is this a bug or am I simply missing something?
    Apex 3.1.2
    Rgds/Mark M.

    It's using a shared component LOV cleverly called LOV_YN which consists of a static LOV with
    1 Display=Yes, Return=Y
    2 Display=No, Return=N
    The settings in the LOV section on the item iteself:
    Named LOV: LOV_YN
    Display Extra values: No Dynamic translation: Not translated
    Number of columns: 2 Display null: No
    Null display value is blank as is null return value
    Item was setup as a radio group and was only converted over to a select list to work around this issue. Let me know what else you need and thanks again.
    Rgds/Mark M.

Maybe you are looking for