BOM Explosion messages

Dear Friend,
I got below 2 messages in sales orders while BOM Explosin
1)Material XXXXXX has status-under development
2)material XXXXXX is not copied from BOM.
after bom exploded in sales order excluding material XXXXXX.
please inform what id the reason of this messages & how to rectify it.
regards,
N.M.PAWAR

Hi
Please check the Material Master Record of this material. Guess, there should be value (11-under development) in the field X-distibution chain status in the general data area of the tab Sales org1.
The F1 help details of that field is given below for your information...
Cross-distribution-chain material status
Indicates whether the material may be used in individual functions in Sales and Distribution for all distribution chains.
Use
The cross-distribution-chain material status restricts the usability of the material for all the distribution chains, that is, it defines whether a warning or error message is displayed if you include the material in a particular function.
Example
The material may be a part under development or one to be discontinued.
Thanks,
Ravi

Similar Messages

BOM explosion in subcontracting PR

Hi...
I have one issue of BOM explosion in subcontracting PR.
I have created BOM, routing & PV. Production version maintained in info record.
While creating manaul subcontracting PR , BOM is not exploded giving error message as "Not possible to determine any components".
I have checked validity of BOM, PV found ok.
Also Proc. type X & Spl. proc type 30 maintained.
Any suggestion to the problem appreciated
Regards
Tushar

Dear Tushar,
Check this link
[Sub contracting PO - BOM components are not seen;
Regards
Madhu

MRP RUN- KIT BOM explosion not working

We setup one layer BOM’s for our maintenance KITs as parent material and components as child material. For example KIT is TS10000-K1 and components are TS10001, TS10002 etc setup as next layer with in the BOM. Both KITS and components are defined as material types ERSA (Spare parts). These one layers BOMs are setup as production BOMs and expected to create purchase requisitions for KITS and components by exploding BOMs during MRP runs. We use purchase requisitions and convert them into POs to procure both KITS and components. We DO NOT USE Panned orders and Production orders.
The safety stocks / reorder point are considered as demand for KITS and components as we do not have any external demand for KITS and components.
MRP run is creating purchase requisitions automatically for both KITS and components as per safety stocks and reorder point defined in MRP Views of Material Master. This is working as expected.
The issue is: KIT BOM’s are not exploding to generate purchase requisitions for the dependent components of KIT BOM. Please suggest the way to resolve this issue.
Split valuation: Also we plan to use split valued KITS with both new and refurbished. So we need BOM explosion for split valued KITS
also (after the 1st issue is resolved).
I verified the following items to make sure the required configuration and data setup is defined correctly.
1) Planning file activated Plant - OMDU
2) Executed MRP run with Total Planning - MDBT and MD02 (single item, multiple levels)
3) BOM explosion for MRP activated- OS23
4) MRP type in MRP1 view- PD and VB (I tried both separately but BOM is not exploding).
5) Procurement type “F” (MRP 2 view) and lot size “EX”
6) Planning strategy in MRP 3 view (tested w/o planning strategy and with strategies 10 and 40. But BOM is not exploded)
7) BOM status and usage (status is active and usage is for production-CS02 and OS20)
8) BOM Validity date (Valid)
9) BOM structure in CS12 (BOM is exploding in CS11)
10) Availability check
11) Selection of BON ID to have BOM usage indicator assign (OS31).
12) No alternate BOMs or production versions or work scheduling view are used.
Please review the above 2 issues and suggest any workable solution. Thanks in advance!
NOTE: I extensively used MRP with multi-level BOM explosion in my earlier projects without any issue. However the above issue is a bit strange why one layer BOM is not exploded in this case.
Regards
Srini

Hi
Thanks for your response. I reviewed all SAP notes and none of them are applicable to my scenario.
1808396 - BOM changes not considered by MRP: I have not changed BOMs.
1781324 - MD11: Valid BOM alternative is not found. We do not have alternative BOMs.
1791009 - No BOM explosion after changing production version: We am not using production versions.
Our Material KITS are PM spare assemblies set up as BOMs and consists of individual spare parts as components. We are creating purchase requisitions and not planned orders. We are not using PP functionality/Production orders.
MRP is generating purchase requisitions for KITS and components as per ROP and safety stocks. In other words it is working as expected. The issue is BOMs which are parent assemblies are not exploding to the next lower level components.
Please note that I am not getting any error messages when MRP is executed.
Regards
Srini.

How about this implementation of BOM Explosion(simulate stack)

REPORT YZWX00301_06 LINE-SIZE 142
                     LINE-COUNT 65
                     MESSAGE-ID YM1
                     NO STANDARD PAGE HEADING .
INCLUDE
INCLUDE: YXXI00050.
*TABLES use table define
TABLES: MARA,        " Material General Table
        MARC,        " Plant Data for Material
        MDMA,        " MRP Area table
        EORD,        " Vendor table
        A018,        " Vendor material mapping table
        KONP,        " Vendor condition table
        MAST,        " Material BOM table
        STPO,        " Material BOM Component table
        STAS.        " Material BOM Component table detail
*CONSTANTS define
CONSTANTS:
C_DAT_X        TYPE C VALUE 'X',
C_MODE         LIKE dxfields-fileoper VALUE 'R',
C_MASK         LIKE dxfields-filemask VALUE '.',
C_FLG_LOCATION TYPE C VALUE 'A',
C_DFPATH(15)   TYPE C VALUE '\bmwx\'.
Work Area Define
---- build stack structure -
DATA: BEGIN OF WK_STACK,
        LEVEL(1)      TYPE C,            "Save Level
        QUANT         TYPE I,            "Save Quantity
      END OF WK_STACK.
---- BOM work area -
DATA: BEGIN OF WK_BOM,
         LEVEL(1)     TYPE C,            "BOM LEVEL
         MATNR        LIKE MARC-MATNR,   "MATERIAL      18
         POSTP        LIKE STPO-POSTP,   "ITEM CATEGORY 1
         MENGE        LIKE STPO-MENGE,   "BOM COMPONENT 13
         DATUV        LIKE STPO-DATUV,   "VALID FROM    10
         DATUB        LIKE STPO-DATUV,   "VALID TO      10
END OF WK_BOM.
---- DATA work area -
DATA: BEGIN OF DATAITEM,
         LEVEL(1)     TYPE C,            "BOM LEVEL
         MATNR        LIKE MARC-MATNR,   "MATERIAL
         POSTP        LIKE STPO-POSTP,   "ITEM CATEGORY
         MENGE        LIKE STPO-MENGE,   "BOM COMPONENT
         DATUV        LIKE STPO-DATUV,   "VALID FROM!!!
         DATUB        LIKE STPO-DATUV,   "VALID TO
         EKGRP        LIKE MARC-EKGRP,   "PURCHASE ORG
         LIFNR        LIKE EORD-LIFNR,    "Vendor code     10
         MARK(1)      TYPE C,             "Mark
         KBETR        LIKE KONP-KBETR,    "Rate price      11
         KONWA        LIKE KONP-KONWA,    "Currency        5
         KPEIN        LIKE KONP-KPEIN,    "Unit Qty        5
         KMEIN        LIKE KONP-KMEIN,    "Condition Unit 3
         DATAB        LIKE A018-DATAB,    "Condition from 10
         DATBI        LIKE A018-DATBI,    "Condition to    10
       END OF DATAITEM.
---- File Line work area -
DATA: BEGIN OF LINE,
         WERKS(4)     TYPE C,                               "Plaint   4
         MATNR(18)    TYPE C,             "Material Number 18
         EKGRP(3)     TYPE C,             "Purchase Group 3
         LIFNR(10)    TYPE C,             "Vendor code     10
         VDATU        LIKE EORD-VDATU,    "Vendor valid from 10
         BDATU        LIKE EORD-BDATU,    "Vendor valid to   10
         MARK(1)      TYPE C,             "Mark
         KSCHL(4)     TYPE C,             "Condition type 4
         KBETR(18)    TYPE C,             "Rate price      11
         KPEIN(5)     TYPE C,             "Rate unit       5
         KONWA(5)     TYPE C,             "Currency        5
         KMEIN(3)     TYPE C,             "Condition Unit 3
         DATAB        LIKE A018-DATAB,    "Condition from 10
         DATBI        LIKE A018-DATBI,    "Condition to    10
       END OF LINE.
*Local Data Object Define
DATA: WK_CNT TYPE I,                   "Count variable
       WK_LVL TYPE I,                   "BOM level
       WK_QTY TYPE I.                   "BOM component qty
DATA: WK_LIFNR LIKE EORD-LIFNR,
      WK_MATNR LIKE MARC-MATNR.
*Internal Table define
DATA TAB_STACK LIKE STANDARD TABLE OF WK_STACK.   "STACK TABLE
DATA TAB_BOM   LIKE STANDARD TABLE OF WK_BOM.     "FOR BOM
DATA TAB_DATA LIKE STANDARD TABLE OF DATAITEM.   "FOR ALL
Parameter in Block1
SELECTION-SCREEN BEGIN OF BLOCK B1 WITH FRAME.         "TITLE TEXT-001.
PARAMETERS:
P_WERKS LIKE MARC-WERKS DEFAULT 'WX01',              "Plant
P_STLTY LIKE STPO-STLTY DEFAULT 'M',                 "BOM Category
P_MATNR LIKE MARC-MATNR OBLIGATORY,                  "Material
P_STDAT LIKE EORD-VDATU OBLIGATORY DEFAULT SY-DATUM. "Standard Date
SELECTION-SCREEN END OF BLOCK B1.
Parameter in Block2
SELECTION-SCREEN BEGIN OF BLOCK B2 WITH FRAME.
SELECTION-SCREEN BEGIN OF LINE.
PARAMETERS: P_SCREEN RADIOBUTTON GROUP R1.     "Screen output
SELECTION-SCREEN COMMENT 03(21) TEXT-001.
SELECTION-SCREEN POSITION 32.
PARAMETERS: P_FILE RADIOBUTTON GROUP R1.       "NTFILE output
SELECTION-SCREEN COMMENT 34(17) TEXT-002.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN END OF BLOCK B2.
Parameter in Block3
SELECTION-SCREEN BEGIN OF BLOCK B3 WITH FRAME.
PARAMETERS:
P_NTFILE(45) TYPE C    LOWER CASE OBLIGATORY.
P_PCFILE      LIKE RLGRAP-FILENAME.
SELECTION-SCREEN END   OF BLOCK B3.
INITIALIZATION
INITIALIZATION .
CLEAR : WK_CNT,
           WK_LVL,
           WK_QTY,
           WK_MATNR,
           WK_STACK,
           WK_BOM,
           DATAITEM.
WK_LVL = 0.
WK_QTY = 1.
REFRESH: TAB_STACK,
           TAB_DATA,
           TAB_BOM.
*&      AT SELECTION-SCREE ON VALUE-REQUEST
*AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_NTFILE.
PERFORM F_SHOW_FILE_POPUP CHANGING P_NTFILE.       "Popup display
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_PCFILE.
PERFORM F_FILENAME_GET USING P_PCFILE
                      CHANGING P_PCFILE.
*&      Form F_FILENAME_GET
--> ST_DAT_PATH     : Preset path
<-- ST_DAT_FILENAME : Selected file name
FORM F_FILENAME_GET USING st_dat_path
                 CHANGING st_dat_filename.
CALL FUNCTION 'WS_FILENAME_GET'
    EXPORTING
      def_filename     = SPACE
      def_path         = st_dat_path
      mask             = ',.,.,'
      mode             = '0'
      title            = 'TXT-file select'
    IMPORTING
      filename         = st_dat_filename
    EXCEPTIONS
      inv_winsys       = 1
      no_batch         = 2
      selection_cancel = 3
      selection_error = 4
      OTHERS           = 5.
IF sy-subrc <> 0.
    MESSAGE s002(yf1) WITH 'F_FILENAME_GET' sy-subrc.
ENDIF.
ENDFORM.                    "F_FILENAME_GET
MAIN PROCESS
START-OF-SELECTION.
---- Check material -
PERFORM CHECK_PROD.
---- get vendor data -
PERFORM GET_VENDOR_DATA.
---- output screen/file -
IF P_SCREEN = 'X'.
    PERFORM SET_OUTPUT.            "Output to screen directly
ELSEIF P_FILE = 'X'.
    IF P_PCFILE <> ''.
      PERFORM DOWNLOAD_DATA.       "Write data into ntfile
    ELSE.
      MESSAGE E007(00) WITH 'P_PCFILE'.
    ENDIF.
ENDIF.
END-OF-SELECTION.
ULINE (142).
WRITE: /002 'Component Material Count:', WK_CNT.
TOP-OF-PAGE
TOP-OF-PAGE.
WRITE: /002 'Product:', 013 P_MATNR,
          030 '****** BOM Price List ******',
          070 SY-DATUM,
          095 'PAGE:',
          100 SY-PAGNO.
ULINE (142).
WRITE: /001   '|Level',
          007   '|Material',
          026   '|Cat',
          030   '|Quantity',
          044   '|From',
          055   '|To',
          066   '|PurG',
          071   '|Vendor',
          082   '|MK',
          085   '|Price',
          101   '|Crncy',
          107   '|UnitQty',
          115   '|Unit',
          120   '|From',
          131   '|To',
          142   '|'.
ULINE (142).
*&FORM CHECK_PROD
text
-->p1      text
<--p2      text
FORM CHECK_PROD.
SELECT SINGLE * FROM MARC
                 WHERE WERKS = P_WERKS           " Plant
                 AND   MATNR = P_MATNR           " Material
                 AND   DISPR IN ('F100','F200'). " Product
IF SY-SUBRC = 0.
    PERFORM CHECK_BOM1 USING MARC-MATNR MARC-WERKS. " CHECK_BOM1
ELSE.
    MESSAGE E022.
ENDIF.
ENDFORM.                                         " CHECK_PROD
*&FORM CHECK_BOM1
text
-->p1      text
<--p2      text
FORM CHECK_BOM1 USING VALUE(FP_MATNR) VALUE(FP_WERKS).
SELECT SINGLE * FROM MAST
                  WHERE MATNR = FP_MATNR     AND      "Material
                        WERKS = FP_WERKS.             "Plant
IF SY-SUBRC = 0.
    PERFORM PUSH_STACK USING WK_LVL WK_QTY.   "Save parent attribute
    PERFORM CHECK_BOM2 USING MAST-STLNR.                    "Check BOM2
ENDIF.
ENDFORM.                                                    "CHECK_BOM1
*&FORM CHECK_BOM2
text
-->p1      text
<--p2      text
FORM CHECK_BOM2 USING VALUE(FP_STLNR).
SELECT * FROM STPO
           WHERE STLTY = P_STLTY        AND        "BOM category
                 STLNR = FP_STLNR.                 "BOM number
    PERFORM POPOUT_WK.                  "Pop out to work area
    WK_BOM-LEVEL = WK_LVL.              "Current BOM level
    WK_BOM-MATNR = STPO-IDNRK.          "Material number
    WK_BOM-POSTP = STPO-POSTP.          "ITEM Category
    WK_QTY       = STPO-MENGE * WK_QTY. "For Stack
    WK_BOM-MENGE = WK_QTY.              "BOM Component qty
    PERFORM CHECK_BOM3 USING STPO-STLTY STPO-STLNR STPO-STLKN.
    PERFORM CHECK_BOM1 USING STPO-IDNRK P_WERKS.
ENDSELECT.
PERFORM POPOUT_STACK.
ENDFORM.                                                    "CHECK_BOM2
*&FORM CHECK_BOM3
text
-->p1      text
<--p2      text
FORM CHECK_BOM3 USING VALUE(FP_STLTY) VALUE(FP_STLNR) VALUE(FP_STLKN).
SELECT SINGLE * FROM STAS
                  WHERE STLTY = FP_STLTY        "BOM category
                  AND   STLNR = FP_STLNR        "BOM number
                  AND   STLKN = FP_STLKN        "BOM item
                  AND   DATUV <= P_STDAT        "Valid from
                  AND   LKENZ = ' ' .           "Valid
IF SY-SUBRC = 0.
    WK_BOM-DATUV = STAS-DATUV.                  "Valid from
ENDIF.
SELECT SINGLE * FROM STAS
                  WHERE STLTY = FP_STLTY        "BOM category
                  AND   STLNR = FP_STLNR        "BOM number
                  AND   STLKN = FP_STLKN        "BOM item
                AND   DATUV > P_STDAT         "Valid from
                  AND   LKENZ = 'X' .           "Invalid
IF SY-SUBRC = 0.
    SELECT SINGLE * FROM STAS
                   WHERE STLTY = FP_STLTY        "BOM category
                   AND   STLNR = FP_STLNR        "BOM number
                   AND   STLKN = FP_STLKN        "BOM item
                   AND   DATUV > P_STDAT         "Valid from
                   AND   LKENZ = 'X' .           "Invalid
    IF SY-SUBRC = 0.
      WK_BOM-DATUB = STAS-DATUV.          "Valid to
      APPEND WK_BOM TO TAB_BOM.
    ENDIF.
ELSE.
    WK_BOM-DATUB = '99991231'.          "Manul input
    APPEND WK_BOM TO TAB_BOM.
ENDIF.
ENDFORM.                                                    "CHECK_BOM3
*&FORM PUSH_STACK
text
-->p1      text
<--p2      text
FORM PUSH_STACK USING VALUE(FP_LVL) VALUE(FP_QTY).
WK_STACK-LEVEL = FP_LVL + 1.
WK_STACK-QUANT = FP_QTY.
APPEND WK_STACK TO TAB_STACK.    "Push stack
SORT TAB_STACK BY LEVEL.         "Sort table by level
ENDFORM.                           "PUSH_STACK
*&FORM PUSH_STACK
text
-->p1      text
<--p2      text
FORM POPOUT_STACK.
DESCRIBE TABLE TAB_STACK LINES WK_CNT.
IF WK_CNT > 0.
    DELETE TAB_STACK INDEX WK_CNT.     "Popout stack
    SORT TAB_STACK BY LEVEL.           "Sort table by level
ENDIF.
ENDFORM.                               "POPOUT_STACK
*&FORM POPOUT_WK
text
-->p1      text
<--p2      text
FORM POPOUT_WK.
DESCRIBE TABLE TAB_STACK LINES WK_CNT.
IF WK_CNT > 0.
    READ TABLE TAB_STACK INTO WK_STACK INDEX WK_CNT.   "Popout stack
    IF SY-SUBRC = 0.
      WK_LVL = WK_STACK-LEVEL.                         "Current Level
      WK_QTY = WK_STACK-QUANT.                         "Parent Qty
    ENDIF.
ENDIF.
ENDFORM.                    "POPOUT_WK
*&FORM DOWNLOAD_DATA
text
-->p1      text
<--p2      text
FORM DOWNLOAD_DATA.
DATA: L_RETURN     TYPE   SY-SUBRC.
PERFORM GUI_DOWNLOAD
              TABLES
                 TAB_DATA
              USING
                 P_PCFILE
                 'X'
              CHANGING
                 L_RETURN.
IF L_RETURN <> 0.
    MESSAGE S020.
ELSE.
    MESSAGE S021.
ENDIF.
ENDFORM.                    " DOWNLOAD_DATA
*&FORM GET_VENDOR_DATA
text
-->p1      text
<--p2      text
FORM GET_VENDOR_DATA.
LOOP AT TAB_BOM INTO WK_BOM.
    CLEAR DATAITEM.
    SELECT * FROM MARC
            WHERE WERKS = P_WERKS             "Plant
              AND MATNR = WK_BOM-MATNR.       "Material
      DATAITEM-EKGRP = MARC-EKGRP.
      SELECT SINGLE * FROM MARA
                      WHERE MATNR = MARC-MATNR    AND   "Material number
                            MTART IN ('1211','1221').
      IF SY-SUBRC = 0.
        SELECT COUNT(*) FROM EORD
                       INTO (WK_CNT)
                 WHERE WERKS = P_WERKS        AND "Plaint
                       MATNR = WK_BOM-MATNR   AND "Material
                       VDATU <= P_STDAT        AND "Valid-From
                       BDATU > P_STDAT.            "Valid-To
        IF WK_CNT > 1.
          DATAITEM-MARK = '*'.
        ELSEIF WK_CNT = 0.
          MOVE-CORRESPONDING WK_BOM TO DATAITEM.
          APPEND DATAITEM TO TAB_DATA.
        ENDIF.
        SELECT * FROM EORD
                 WHERE WERKS = P_WERKS        AND "Plaint
                       MATNR = WK_BOM-MATNR   AND "Material
                       VDATU <= P_STDAT        AND "Valid-From
                       BDATU > P_STDAT.            "Valid-To
          MOVE-CORRESPONDING WK_BOM TO DATAITEM.
          DATAITEM-LIFNR = EORD-LIFNR.             "Vendor code
          SELECT * FROM A018
                    WHERE LIFNR = EORD-LIFNR AND "Vendor code
                          MATNR = EORD-MATNR AND "Material
                          EKORG = EORD-EKORG AND "Purchase org
                          DATAB <= P_STDAT     AND "Valid-from
                          DATBI >   P_STDAT.         "Valid-to
            DATAITEM-DATAB = A018-DATAB.    "Condition From
            DATAITEM-DATBI = A018-DATBI.    "Condition To
            IF SY-SUBRC = 0.
              SELECT * FROM KONP
                       WHERE KNUMH = A018-KNUMH   AND   "Cnd Number
                             KSCHL = A018-KSCHL   AND   "Cnd Type
                             KAPPL = A018-KAPPL.        "Cnd Cat
                DATAITEM-KBETR = KONP-KBETR.            "Price
                DATAITEM-KONWA = KONP-KONWA.            "Currency
                DATAITEM-KPEIN = KONP-KPEIN.            "Price Unit
               DATAITEM-KMEIN = KONP-KMEIN.            "Unit of Material
                APPEND DATAITEM TO TAB_DATA.            "Append TAB_DATA
              ENDSELECT.
            ENDIF.
          ENDSELECT.
        ENDSELECT.
      ELSE.
        MOVE-CORRESPONDING WK_BOM TO DATAITEM.
        APPEND DATAITEM TO TAB_DATA.
      ENDIF.
    ENDSELECT.
    IF SY-SUBRC <> 0.
      MOVE-CORRESPONDING WK_BOM TO DATAITEM.
      APPEND DATAITEM TO TAB_DATA.
    ENDIF.
ENDLOOP.
ENDFORM.                    "GET_DATA
*&      Form SET_OUTPUT
      text
--> p1        text
<-- p2        text
FORM SET_OUTPUT .
CLEAR WK_CNT.
LOOP AT TAB_DATA INTO DATAITEM.
    WRITE: /001   '|', 002 DATAITEM-LEVEL,   "Material Number
            007   '|', 008 DATAITEM-MATNR,   "Purchase Grp
            026   '|', 027 DATAITEM-POSTP,   "Item category
            030   '|', 031 DATAITEM-MENGE,   "BOM Component qty
            044   '|', 045 DATAITEM-DATUV,   "BOM valid from
            055   '|', 056 DATAITEM-DATUB,   "BOM valid to
            066   '|', 067 DATAITEM-EKGRP,   "Purchase Org
            071   '|', 072 DATAITEM-LIFNR,   "Vendor
            082   '|', 083 DATAITEM-MARK,    "Mark flag
            085   '|', 086 DATAITEM-KBETR,   "Price
            101   '|', 102 DATAITEM-KONWA,   "Currency
            107   '|', 108 DATAITEM-KPEIN,   "Unit Qty
            115   '|', 116 DATAITEM-KMEIN,   "Unit OM
            120   '|', 121 DATAITEM-DATAB,   "Cnd From
            131   '|', 132 DATAITEM-DATBI,   "Cnd To
            142   '|'.
    WK_CNT = WK_CNT + 1.
ENDLOOP.
ENDFORM.                    " SET_OUTPUT

Prabhu Peram,
Thanks very much.
I want to show an idea of BOM explosion by constructing a stack.
BOM explosion uses first-root-searching and pushes the "root" material into stack.If the "root" has no left-child,pops out the "root" material and searchs the right-child....and completes the entire BOM explosion.
Message was edited by:
        Mic chen
Message was edited by:
        Mic chen

BOM explosion from Production Order

Hi All,
I understand from SAP Help files that we can explode BOM from Production Order using Read PP Master Data. But it also says, that we cannot do this if items have already been issued out. So would like to know is there anyway out to ensure that the production order is reading the latest version of BOM.
The reason i want to know is because, at present the BOM keeps getting updated & so the work order has to reflect the new items. The BOM contains about 300 or more items, so manual changes is very tedious & error prone at the moment. Furthermore some components are outsourced. So i want to receive them back & post new materials for them. Hope my problem is clear & await inputs
Vivek

Hi All,
Thanks for the inputs. I think for the situation am facing, the Order change management method, should be of help, as the BOM changes does not take place on scheduled dates, for me to fix the BOM explosion dates & assign them. As of now the BOM gets changed, depending the customer requirements, which is unpredictable.
Clarification required:
1. The profile which is created using OPL7 & assigned in OPL9 is unique, i.e. for any change numbers of BOM will always follow the profile entered in 'Overall Profile' in Work Scheduling view & i do not need to create new profiles for each new change number of BOM
2. Once i run the COCM with the new change number, in the production order - components view will i be able to see any error message for those items which no longer feature in the new version of BOM? & will the materials added in the new BOM automatically feature in that list or do i have to manually add these to the order & if so, how will i know which materials need to be added?
Hope the clarifications sought are clear, await inputs
Vivek

No BOM explosion in assembly order

Dear Experts,
I am running a assembly order, type PP04 which is directly created from a sales order. During the creation, the BOM is exploded.
My question is that how can I disable the BOM explosion as I want to enter all the components according to our customer rule instead of a predefined BOM.
If there is no BOM of that material, there will be a error message when saving the production order.
Thanks.
Claude

Hi,
following settings to be made in Customization for the Assembly Order If you don'twant to explode the BOM
1) Create the selection ID with priority & BOM usage in OPJI
2) Create the BOM Application & Assign the selection ID created in above step & Also mantain the following cheks in OPJM
uncheck the Sales Order explosion indicator--OPJM
3)Assign the above Application to the Order type & Plant in OPL8
Thanks,
Rajanikanth

How to restrict other plant material assigned to SA BOM explosion

Dear Experts
One of our client havea issue of assigning wrong material to the scheduling agreement BOM explosion.
Actually there are two different plant code one for manufacturing plant and another one trading.Subcontractor activity will be carried out in trading plant , but users assigning the BOM components from manufacturing plant material.
So they are sending material to vendor from manufacturing plant and receiving material to trading plant.But finance guy don't want do like that.
How to restrict other material (material not part of SA plant)assignment to SA BOM explosion
Thanks in advance
Regards
SS

Thanks for your reply.
In BOM creation CS01 , if plant is differ from header to line item system will give error message M3 351
"Material &&&&&& not maintained in plant &&&&".
Like that i want to make it in ME38 BOM explosion also.If plant is differ from scheduling agreement line item to BOM line item system should give error message.
For the above scenario I need the solution
SS

BOM explosion while MRP run

hi all
I have a FERT for which raw materials are assigned in the BOM. but while running MRP, the BOM is not being exploded and the list doesnt show the raw materials.
I have checked in the Overall maintenance of the plant parameters in MRP in SPRO and the required paramenters are maintained.The scenario is MTS - strategy 10.but still the BOM is not exploded.
Could anyone solve my query
Thank you in advance
chandra

Hi Chandra,
Could you please check if there was an exception message "50 or 52"? If so then it can be beacuse for the BOM explosion date system is not able to get a BOM.
If there were no exception messages then check in MRP4 view of the FERT material for dependent requirement defination. This should be blank.
Hope this helps..
Regards,
Prasobh
Reward your points if this was helpful.

BOM explosion not done because there is no free item number anymore

Hello,
I have a problem with BOM explosion when creating a sales order.
All the following actions are done with VA01 :
- I enter a material (main item 10) with a rejection reason, so the BOM explosion is not done :OK.
- Then I add the same material (main item 20) without rejection code, so the BOM explosion is done, it means sub items 21, 22., ...,31,32 are determined:OK
- Finally, I remove the rejection code on item 10, the problem is that there is no place anymore to do the BOM explosion because I have 12 sub items (10 +12 = 22 and it is not possible as I have already an item 20).
I have a popup with message V1-142 (There are not enough item numbers free for a structure explosion).
I know that it is possible to change the increment with VOV8, but my customer want to keep this one: 10 by 10 for main item and 1 by 1 for sub item.
He told me that he think that there is a user exit in order to put the remaining sub items at the end of the sales order like this
10 main item A
11 sub item 1 (A)
12 sub item 2 (A)
19 sub item 9 (A)
20 second main item (B)
21 sub item 1 (B)
22 sub item 2 (B)
32 sub item 12 (B)
33 sub item 10 (A)
34 sub item 11 (A)
35 sub item 12 (A)
Maybe it's a strange idea, but could you please tell me what are the different possibilities to manage sub items when there is no place to put them :
- put a higher increment in VOV8? Ok but my customer don't agree
- other solutions?
Thanks.

Hello,
Did you ever find a solution for this? The notes mentioned in the earlier post dont appear to be relevent for 6.0.
I have a similar issue when dealing with Cross Sell items. When it tries to insert the additional items I get the V1142 message, then the items are copied at the end of the list but the higher level item reference is incorrect for the cross sell items.
I do not want to change the increments but it appears to be the only option.
Any ideas are appreciated.

BOM Explosion for Multiple Process Orders

Hi,
I hope someone can assist me with the following: Is there a report I can run or transaction I can do to have BOM explosion for multiple Process Orders? I would like to input process orders for a week and see the BOM details per PO.
Thanks

Dear Sukendar,
1.For this requirement you have to go for a Z report and you can give the Functional Spec's to prepare
this report to your ABAP consultant.Prepare the input format,logic of the program and the output format.
In the logic part you can make use of this Functional Modules's CSAP_MAT_BOM_READ or
CSEP_MAT_BOM_READ or CS_BOM_EXPLOSION or CS_BOM_EXPL_MAT_V2 .
2.Using CEWB helps you to identify all the material that's having the BOM,but here the report does not
shows you the level by level by BOM for a FERT.
Check and revert back.
Regards
Mangalraj.S

BOM Explosion needed on PO and/or Delivery for Stock Transfer PO Process

Good afternoon,
I have been researching the SDN and web for a solution to my problem to no avail so far.
The business problem I need to solve is the requirement for our STPO process to explode certain BOM's that are transfered from one company/plant to another company/plant in order to record batch/serial # component information by the delivering plant on the delivery and verification of the batch/serial # in the receiving plant during MIGO processing of the delivery. This is needed by our Service Mgmt department in order to track servicable items within the Finished Good (medical devices industry).
It appears on the SDN that a BOM can not be exploded on a non-Subcontracting PO (which would be ideal for us), but barring this problem, we are trying to have the BOM explode in the Delivery created from the STPO via the VL10B transaction.
The STPO generates a Delivery doc with type NLCC and item category NLC. I have maintained the material master for the BOM material to have an Item Category Group of ERLA, and I have modified Item Category Determination in configuration in Logistics Execution for deliveries to include ERLA, usage V, and NLC as default item category. But, the deliveries generated from the STPO still do not explode, like what normally happens if the delilvery of the BOM was created from a standard Order.
The components for the BOM need to be displayed on the Delivery (if not the STPO), so the cleark can record the Batch/Serial #'s for each component. Then when the receiving plant posts the Goods Receipt for the delivery a user exit we have (based on movement type and material document code) builds a Service Mgmt table that is then processed to De-install the BOM and components from the former plant and install the BOM and components at the receiving plant (and then subsequently at the ultimate customer's location when a normal sale is made), generating a new Functional Location.
Has anyone here had to do anything like this before? Would any of you have any ideas on how this BOM explosion might work on the PO or Delivery?
Thanks in advance.
Scott.

No responses to this question.
Subject dropped.

BOM Explosion needed on Delivery for Intercompany Stock Transfer Order

Good afternoon,
I have been researching the SDN and web for a solution to my problem to no avail so far.
The business problem I need to solve is the requirement for our STPO process to explode certain BOM's that are transfered from one company/plant to another company/plant in order to record batch/serial # component information by the delivering plant on the delivery and verification of the batch/serial # in the receiving plant during MIGO processing of the delivery. This is needed by our Service Mgmt department in order to track servicable items within the Finished Good (medical devices industry).
It appears on the SDN that a BOM can not be exploded on a non-Subcontracting PO (which would be ideal for us), but barring this problem, we are trying to have the BOM explode in the Delivery created from the STPO via the VL10B transaction.
The STPO generates a Delivery doc with type NLCC and item category NLC. I have maintained the material master for the BOM material to have an Item Category Group of ERLA, and I have modified Item Category Determination in configuration in Logistics Execution for deliveries to include ERLA, usage V, and NLC as default item category. But, the deliveries generated from the STPO still do not explode, like what normally happens if the delilvery of the BOM was created from a standard Order.
The components for the BOM need to be displayed on the Delivery (if not the STPO), so the cleark can record the Batch/Serial #'s for each component. Then when the receiving plant posts the Goods Receipt for the delivery a user exit we have (based on movement type and material document code) builds a Service Mgmt table that is then processed to De-install the BOM and components from the former plant and install the BOM and components at the receiving plant (and then subsequently at the ultimate customer's location when a normal sale is made), generating a new Functional Location.
Has anyone here had to do anything like this before? Would any of you have any ideas on how this BOM explosion might work on the PO or Delivery?
Thanks in advance.
Scott.

No responses to this question.
Subject dropped.

How to restrict BOM explosion in Quotation and Sales Order

Dear all,
How can we restrict BOM main item explosion in Sales Order.
this BOM main item is having special order items which have to generate purchase requisition (item category - BANC),
with out exploding bom main item, can we generate a purchase requisition for BOM subitems, can any body explain me that how can we do that.
your suggestions will be highly appreciated.
thank you
Raghu Ram

Hi Raghu Ram,
The BOM explosion is controlled by item category.
In the item category configuration screen, under "Bills of Material/ Configuration", you can see "Structure Scope" field.
Select the one which is applicable to your case:-
"blank" - Do not explode material structure
A - Explode single-level BOM
B - Explode multi-level BOM
C - Configuration, no BOM explosion
D - Configuration, poss. with BOM explosion
E - Structure from Customer_Function (product selection)
Hope this helps
Regards,
Nicole

BOM Explosion Number in Sales Order

Hi Experts,
For a make-to-order case, I would like to assign a predefined BOM explosion number with fixed key date to a sales order item. Instead of manually assigning the BOM explosion number to the sales order item, is there any way to let the system automatically assign the BOM explosion number?
As I read from SAP Library under the BOM Explosion Number (Fixed Key Date), it states "The system can automatically specify the BOM explosion number when entering planned independent requirements or customer independent requirements or when entering the sales order." So is there any configuration to be done in advance to enable the BOM explosion number to be automatically assigned to sales order item?
Thanks,
SW

I tried also setting up the material and its BOM determination by specifying only 1 BOM out of multiple BOMs. Still,
1. When I add the said material into sales order line and save the sales order, the BOM explosion number value never appear automatically in the sales order line.
2. When I run the planning on the sales order through MD50, the planned results do not have the BOM explosion number attached.
I think your advice is more applicable to selection of a BOM from multiple BOMs instead of determining the fixed key date based on appropriate BOM explosion number, correct me if I am wrong.
Regards

BOM explosion in sales order

Hi Experts,
I have met a problem in BOM explosion in sales order.
I have maintained the BOM with usage 5 and the conversion between header material and component of the BOM. But in the sales order entry, no matter how many qty I entered for the header material, after the BOM explosion, the qty of component is 1.
Can anyone help?
Regards,
Emily

Hi,
Go to CS02 and select ur bom and go to components give 1 that means 1;1
hope u get it
regards,
sadanandam kasarla

BOM Explosion messages

Similar Messages

Maybe you are looking for