Skip to end of metadata
Go to start of metadata

Overview of the existing processes

(warning) Be aware, that you only should use one option within one system. Otherwise, this may lead to inconsistencies.

Legacy processes 1

01 - Automatic maintain BOM during Checkin (mainly used in NX integration projects)

After each check-in of a CAD assembly the material BOM is created, if also a Material exists and is linked to the header and components of the Bill of Documents. The Material BOM is derived directly from information in CAD system (plm_metainf-cad.xml). The SAP function module CSAP_MAT_BOM_MAINTAIN is called to store the BOM.

Summary

  • Automatic called in the save / checkin process without UI.
  • The items are send using the Meta-Information from CAD.
  • Used FM: /DSCSAG/MAT_BOM_MAINTAIN (CSAP_MAT_BOM_MAINTAIN)
  • BAdI: /DSCSAG/MATERIAL_01 - methods matbom_before_maintain() and matbom_after_maintain()
  • Frontend - settings can be done in <ECTR installation directory>\customize\config\default.txt. 
default.txt
# 2.4 Material / Material BOM settings
...
# Define how to update a BOM. Set to true, ECTR will update a material BOM 
# on checkin of a document with component references. 
# true:  Update a material BOM on checkin of a document with component references 
# false: BOMs can only be updated manually
plm.bom.updateAtCheckin = true

02 - Maintain BOM directly from CAD (mainly used in old integration projects)

  • Manually called in the CAD Application
  • The items are send using the Meta-Information from CAD.
  • Used FMs: /DSCSAG/MAT_BOM_RFC_CREATE (RFC_CREATE_BILL_OF_MATERIAL) and /DSCSAG/MAT_BOM_RFC_CHANGE (RFC_CHANGE_BILL_OF_MATERIAL)
  • BAdI: /DSCSAG/MATERIAL_01 - methods matbom_rfc_create_before(), matbom_rfc_create_after(), matbom_rfc_change_before(), matbom_rfc_change_after()
  • Frontend settings can be done in default.txt
  • Currently "blacklisted" in S/4 systems.

03 - CDESK BOM Wizard (mainly used by "ex CDESK" - customers)

The CDESK_BOM_WIZARD derives the Material BOM from a Bill of Documents, if also a Material exists and is linked to the header and components of the Bill of Documents.

  • Manually called in ECTR or configured in automatic save.
  • The items are read in backend from the bill of documents (BOD).
  • Attention: No callbacks possible in BADIs because of JCo and ECTR.
  • Used FM: /DSCSAG/CDESK_BOM_WIZARD ( (info) CDESK_BOM_WIZARD )
  • Frontend - settings can be done in api_definitions2.xml and in dtype.xml
  • Backend - settings can be done in CDESK_CUS - transaction.
  • Not available in SAP S/4HANA, as this is part of CAD-Desktop, see S/4 simplification list.
  • Does not handle "explosion scenarios".
  • Does not handle DMUCAD fields to suppress or exclude positions.
  • OMF: "fnc.cdesk.bom.wizard"

04 - Derive BOM from Document Structure

  • Manually called in ECTR.
  • The items are read from the BOD and written to the BOM with CSAP_MAT_BOM_MAINTAIN
  • Not possible to handle customer specific BOM fields.
  • OMF "fnc.mat.bom.complete" / Process "PlmProcessMaterialBomGenerateFromDocStr"

Current maintained processes 2

05 - Maintain BOM manually via ECTR

  • Manually called in ECTR.
  • No items are send to backend, user has to change or insert them manually
  • Used FMs: /DSCSAG/MAT_BOM_RFC_CREATE (RFC_CREATE_BILL_OF_MATERIAL)
  • OMF "fnc.mat.bom.change"

06 - Advanced Bill of Material maintenance - SAP GUI

  • Manually called in ECTR.
  • The item are read in backend from the BOD (and DMU_METAINF DB table).
  • Used FM: CDESK_SRV_MBOM_WIZARD
  • Settings can be done in api_definitions2.xml
    • A default explosion scenario if defined in api_definitions2.xml "BOM_DERIVE".
    • The explosion scenario can be changed with transaction CDESK_CUS or CAD_SRV_CUS (S4).

    • You can define your own explosion scenario to control the explosion of the Bill of Documents before deriving the Bill of Materials, see also How to configure different load scenarios, step 1
    • CAD-Fields for explosion scenario "BOM_DERIVE":

      If you like to exclude a component with RES4 e.g. "UGS:PW" or SORTF "UGS:CS" you have to add additional rows with behavior "ST" (STOP). 

      (warning) It is not possible to exclude a component and keep children with an entry in SORTF or RES4. You have to use the DMUCAD instance values in CAD system for this instead. 

  • OMF Multi: "fnc.api.generic2(CDESK_SRV_MBOM_WIZARD_MULTI_DOC)"
  • OMF Single: "fnc.api.generic2(CDESK_SRV_MBOM_WIZARD_SINGLE_DOC)"



07 - Advanced Bill of Material maintenance - ECTR UI

  • Manually called in ECTR.
  • The item are read in backend from the BOD (and DMU_METAINF DB table).

Step 1: Start the process via the context menu manually

This step uses the object menu function "OmfDeriveMatBom" (entry in menu_macros.txt fnc.derive.mat.bom).

Step 2: Define parameters to derive a BOM

After defining the settings the function module "CDESK_SRV_MBOM_DERIVE" is executed.

Step 3: Review the proposed result. When clicking "OK" the BOM is saved.

When you are OK, the function module "CDESK_SRV_MBOM_MAINTAIN_MULTI" saves the Bill of Material.


08 - Derive versioned Bill of Material - ECTR UI

  • Manually called in ECTR.
  • The item are read in backend from the BOD (and DMU_METAINF DB table).

Step 1: Start the process via the context menu manually

This step uses the object menu function "OmfDeriveMatBom" (entry in addons\changeRecord\customize\config\menu_macros.txt → fnc.derive.mat.bom(VMBOM) ).

Step 2: Define parameters to derive a BOM

After defining the settings the function module "/DSCSAG/VB_MBOM_DERIVE" is executed.

Step 3: Review the proposed result. When clicking "OK" the BOM is saved.

When you are OK, the function module "/DSCSAG/VB_MBOM_MAINTAIN_MULTI" saves the Bill of Material.

1 Not in focus for further enhancement, no improvements of existing processes planed. It is not recommended to use this functions in new projects.

2 Further enhancements and improvements are in backlog and planed for future releases.

 

 

 

 



  • No labels