Skip to end of metadata
Go to start of metadata

Purpose

The purpose of this page is to clarify the behavior of the MBOM Wizard for specific requirements and use cases. 

Starting point to derive a Bill of Material (BOM) is the Bill of Documents (BOD) and its linked Material Masters.

Overview

Different customers expect different behavior of the MBOM wizard. The MBOM wizard has a default behavior which will be described here. 

Summarize quantity for different document components with same material

The default behavior for this scenario shall be, that in BOM there is material quantity summarized:

BOD
- Component (DIR) A – Material 0815 - Quantity 1
- Component (DIR) B – Material 0815 - Quantity 1
- Component (DIR) C – Material 0815 - Quantity 1
BOM
- Component Material 0815 - Quantity 3


If in customer specific requirements several positions in BOM are required, the bom_item_group feature has to be used:

BOD
- Component (DIR) A – Material 0815 - Quantity 1 - bom_item_group 100
- Component (DIR) B – Material 0815 - Quantity 1 - bom_item_group 100
- Component (DIR) C – Material 0815 - Quantity 1 - bom_item_group 200
BOM
- Component Material 0815 - Quantity 2
- Component Material 0815 - Quantity 1

 

No linked Material for DIR ->no BOM

When a BOM is derived from a BOD, the DIRs shall have a linked Material. If not, the process is cancelled with an error.

If the BOD-item with a DIR w/o linked Material has field SORTF="*:WU" then you can derive a BOM. In this case, the BOD item is ignored.

You can also use your own explosion scenario for the BOD before deriving a BOM, see How to derive a Bill of Material (BOM)#06-AdvancedBillofMaterialmaintenance. With an own explosion scenario you can control which BOD items (which SORTF values) shall be considered.


No linked Material for component

Symptom

CDESK_SRV_MESSAGES | 217    | No material assigned to component of document ...

Reason

One component of the BOD ha no material assigned.

Solution 1

The error is an intended behavior. You have to either set the EXCLUDE - Flag for this component in CAD (exclude and keep children or exclude and ignore children) or use the explosion scenario to suppress this component with a specific SORTF or RES4 value. 

Solution 2

The error is an intended behavior. If you are not able to use the Solution 1 features, you can implement the BAdI: CDESK_SRV_MBOM. In Method: AFTER_MBOM_MAP_FROM_BOD - Change table CT_MESSAGE_MBOM and replace type value "E" with value "W" for the upper listed message. 

  METHOD if_cdesk_srv_mbom~after_mbom_map_from_bod.
* Show Warning instead of error
    LOOP AT ct_message_mbom ASSIGNING FIELD-SYMBOL(<ls_message_mbom>).
      IF <ls_message_mbom>-type EQ 'E' AND <ls_message_mbom>-number EQ '217'.
        <ls_message_mbom>-type = 'W'.
      ENDIF.
    ENDLOOP.
  ENDMETHOD.

(warning) To display the warning message you need at least frontend version 5.2.4.0 / 1.1.4.0.  

Related Content

Related Documents

-

Related SAP Notes/KBAs

-

__________________________________________________________________________________________________________

 

  • No labels