1 Reply Latest reply: Dec 31, 2008 1:12 PM by Siva Kumar RSS

BOM not saving

Dhananjay Patil
Currently Being Moderated

Hi Gurus,

I have got a issue related to Bill of Material.I am trying to create a BOM by entering Material,Plant,Usage Group (Group BOM )and Alternative BOM. then in the next screen I enter the Component with item Category L and tried to save the BOM, but it is not allowing me to save the BOM It is giving me error message Express Document "Update was terminated"

When I checked the error log it is giving "Error Info...   29 281: Maximum low-level code 999 reached"

Can you please help me in this

 

Regards

Dhananjay

  • Re: BOM not saving
    Siva Kumar
    Currently Being Moderated

    Hi,

     

    Refer the OSS Note:Note 484640 - Update termination 29281: Maximum low-level code 999 reached

    as below:

     

    Aprt from this there are other OSS Notes: 97783, 69231 also available..

     

    ===========================================================================

    Note 484640 - Update termination 29281: Maximum low-level code 999 reached

     

    Symptom

     

    The BOM update terminates with the error

               29 281: Maximum low-level code 999 reached

     

     

    Update termination in detail (via Transaction SM13):

    Module ID       Module name                      Module type Status

             1      BOM_POST                        V1 NICHT NACHVB.  err

             2      BOM_POST_V2_MAT                V2 NORMAL         init

     

    Function module     BOM_POST

    Status              Update was terminated

    Report              LCSRCF10

    Error text          29 281: Maximum low-level code 999 reached

     

    Other terms

     

    CS01, CS02, CS05, DISST, DISST_SET_MAT, recursive, SAPLCSRC

     

    Reason and Prerequisites

     

    Cause for update termination: data inconsistency.

    The BOM update terminates in the low-level code assignment with error 29281 (Maximum low-level code 999 reached) when the BOM header material is already being used as a co-product (STPO-KZKUP = 'X'), although the material in the material master is not defined as a co-product (MARA-KZKFG = ' ') and the header material is being used recursively in the BOM structure.

     

    Example 1:      A    MARA-KZKUP = ' '

                     

     

                    B

     

                    A    STPO-KZKUP = 'X'

     

    Example 2:

              A  in plant 0001 , MARA-KZKUP = ' '

               

     

              B                          B  in plant 0002

     

                                        A    STPO-KZKUP = 'X'

     

     

    Cause for data inconsistency:

    A material can only be used as a co-product in BOMs if this material is defined as a co-product in the respective plant segment (MARC) of the material master.

    As soon as the material concerning a plant is defined as a co-product (MARC-KZKUP), indicator MARA-KZKUP is also set automatically at group level.

    In the material master, indicator 'co-product' can be initialized without checking the usage of the material in BOMs. In the material master record maintenance the missing check can not be implemented since the material master record maintenance would have to lock the entire BOM maintenance if the indicator 'co-product' is changed. This is not feasible.

     

    Solution

     

    Create the analysis report ZZ_KZKUP (see correction instructions) and execute the report initially in TEST mode (parameter TEST = 'X'). The report lists all the materials, which are used as a co-product in BOMs, although these materials are not defined as a co-product in the material master. In addition, the report lists all the plants, in which the data inconsistency was selected.

    If you execute report ZZ_KZKUP in UPDATE mode (parameter TEST = ' '), the data inconsistency is corrected by the report setting indicator MARA-KZKUP in all the listed materials and also indicator MARC-KZKUP for all the listed plants.

     

    ===========================================================================

  • Re: BOM not saving
    Dhananjay Patil
    Currently Being Moderated

    Closed this thread