DBomheaderforexplosionOut (SAP Cloud SDK

java.lang.Object
- com.sap.cloud.sdk.datamodel.odata.helper.VdmObject<ObjectT>
- - com.sap.cloud.sdk.datamodel.odata.helper.VdmComplex<DBomheaderforexplosionOut>
  - - com.sap.cloud.sdk.s4hana.datamodel.odata.namespaces.billofmaterials.DBomheaderforexplosionOut

public class DBomheaderforexplosionOut
extends VdmComplex<DBomheaderforexplosionOut>

Original complex type name from the Odata EDM: DBomheaderforexplosionOut

Nested Class Summary

Nested Classes
Modifier and Type Class and Description

static class DBomheaderforexplosionOut.DBomheaderforexplosionOutBuilder

Nested Classes
Modifier and Type	Class and Description
`static class`	`DBomheaderforexplosionOut.DBomheaderforexplosionOutBuilder`

Field Summary
- Fields inherited from class com.sap.cloud.sdk.datamodel.odata.helper.VdmObject
  changedOriginalFields

Constructor Summary

Constructors
Constructor and Description
`DBomheaderforexplosionOut()`
DBomheaderforexplosionOut(Boolean alternative_item, String alt_item_group, Boolean alt_nxt_lvl, Boolean assembly_indicator, Boolean assign_effect_vals, BigDecimal assy_scrap_itm_mat, Boolean as_selection_cond, BigDecimal base_qty_nxt_lvl, String base_unit_nxt_lvl, String base_uom, String batch_entry, Boolean batch_mgmt, String bill_of_material, BigDecimal bill_of_material_base_quant, String bill_of_material_component, BigDecimal bill_of_material_comp_quant, String bill_of_material_item_category, String bill_of_material_item_number, BigDecimal bill_of_material_item_quantity, String bill_of_material_item_unit, String bill_Of_Material_Root, String bill_of_material_root_variant, String bill_of_material_variant, String bill_of_material_variant_usage, String bom_change_number, Boolean bulk_material, String b_o_m_alternative_text, String b_o_m_alt_nxt_lvl, String b_o_m_category, String b_o_m_cat_nxt_lvl, String b_o_m_component_description, BigDecimal b_o_m_explosion_level, String b_o_m_hdr_matl_hier_node, String b_O_M_Hdr_Root_Matl_Hier_Node, String b_o_m_header_base_unit, BigDecimal b_o_m_header_quantity_primary, String b_o_m_item_description, String b_o_m_item_is_discontinued, String b_o_m_no_nxt_lvl, String b_o_m_usage_nxt_lvl, String change_number, String chg_to_eng_chg_number, String classProperty, String classification, String class_type, String commodity_code, String comp_maint_status, BigDecimal comp_scrap_itm, BigDecimal comp_scrap_itm_mat, String config_mat_var, Boolean config_multi_level, Boolean conf_bom_nxt_lvl, String cost_element, String counter, Boolean co_product, String created_by_user, String currency, String customs_preference, Boolean dat_hist_nxt_lvl, Boolean deletion_indicator, BigDecimal delivery_time_in_days, Boolean del_Ind_nxt_lvl, BigDecimal denominator, String discont_group, String distribution_key, String doc, String document_part, String document_type, String document_version, String doc_number, Boolean doc_reqd, String doc_status, String doc_type, String doc_version, LocalDateTime effective_out_date, Boolean engineering_design, String exception_bom, String explosion_type, Boolean fixed_price_co_prod, Boolean fixed_quantity, String follow_up_grp, Boolean follow_up_item, String follow_up_product, String formula_key, BigDecimal goods_receipt_duration_in_days, String goods_recipient, String header_record_id, LocalDateTime header_validity_end_date, LocalDateTime header_validity_start_date, Boolean hl_configuration, String individual_coll, String internal_obj_no, String intra_material, String issuing_plant, String is_b_o_m_item_spare_part, Boolean is_c_a_d, String is_material_provision, Boolean is_phantom_item, Boolean is_software_component, String item_category, String item_description_line_2, String item_identification, String item_node, Boolean item_sign, String last_changed_by_user, LocalDateTime last_change_date, BigDecimal lead_time_offset, String long_text_lang, String low_level_code, String maintenance_status, BigDecimal material_component_price, String material_group, Boolean material_is_configurable, String material_Name, String material_type, BigDecimal mat_purity_in_perc, BigDecimal moving_price, Boolean multiple_sel, String m_r_p_type, Boolean net_scrap_indicator, String no_cu_instances, String no_of_sheets, BigDecimal no_var_size_items, BigDecimal numerator, String object_description, String object_type, String obj_dep_assgt_no, BigDecimal operation_scrap_perc, String oper_lto_unit, BigDecimal oper_lt_offset, String org_area, String page_format, String page_number, BigDecimal path, BigDecimal path_predecessor, String plant, Boolean plant_maintenance, String plant_sp_matl_status, LocalDateTime plt_sp_status_valid_from, Boolean pm_assembly, String price_control, BigDecimal price_unit, String priority, Boolean procured_externally, String prodn_supply_area, Boolean production_relevant, String production_supply_area, String production_version, String prod_order_issue_location, String profit_center, String purchase_org, String purchasing_group, String purchasing_organisation, BigDecimal qty_var_size_item, LocalDateTime record_creation_date, Boolean recurisve, Boolean recurs_allowed, String reference_point, String relevancy_to_costing, String relevant_to_sales, Boolean required_component, String requirement_segment, String revision_level, BigDecimal scrap_qty_bun, String serial_no_profile, BigDecimal size1, BigDecimal size2, BigDecimal size3, String size_unit, Boolean soft_comp_indicator, String sort_string, String special_procurement_type, String special_proc_typ_itm, String special_proc_typ_mastr, String spec_proc_costing, BigDecimal standard_price, String status_text, String stock_segment, String storage_location, String strategy, Boolean sub_item_indicator, String supplier, Integer table_row, String tech_status_from, Boolean test_hist_nxt_lvl, String totals_record_id, String unit_of_measure, String unloading_point, String uom_usage, BigDecimal usage_probability, LocalDateTime validity_end_date, LocalDateTime validity_start_date, String valuation_category, Boolean variants_nxt_lvl, String x_plant_material_status, LocalDateTime x_plt_status_valid_from)

Method Summary

All Methods Static Methods Instance Methods Concrete Methods
Modifier and Type	Method and Description
`static DBomheaderforexplosionOut.DBomheaderforexplosionOutBuilder`	`builder()`
`protected boolean`	`canEqual(Object other)`
`boolean`	`equals(Object o)`
`protected void`	`fromMap(Map<String,Object> inputValues)`
`String`	`getAlt_item_group()` Constraints: Not nullable, Maximum length: 2
`Boolean`	`getAlt_nxt_lvl()` Constraints: none
`Boolean`	`getAlternative_item()` Constraints: none
`Boolean`	`getAs_selection_cond()` Constraints: none
`Boolean`	`getAssembly_indicator()` Constraints: none
`Boolean`	`getAssign_effect_vals()` Constraints: none
`BigDecimal`	`getAssy_scrap_itm_mat()` Constraints: Not nullable, Precision: 5, Scale: 2
`String`	`getB_o_m_alt_nxt_lvl()` Constraints: Not nullable, Maximum length: 2
`String`	`getB_o_m_alternative_text()` Constraints: Not nullable, Maximum length: 40
`String`	`getB_o_m_cat_nxt_lvl()` Constraints: Not nullable, Maximum length: 1
`String`	`getB_o_m_category()` Constraints: Not nullable, Maximum length: 1
`String`	`getB_o_m_component_description()` Constraints: Not nullable, Maximum length: 40
`BigDecimal`	`getB_o_m_explosion_level()` Constraints: Not nullable, Precision: 2, Scale: 0
`String`	`getB_o_m_hdr_matl_hier_node()` Constraints: Not nullable, Maximum length: 40
`String`	`getB_O_M_Hdr_Root_Matl_Hier_Node()` Constraints: Not nullable, Maximum length: 40
`String`	`getB_o_m_header_base_unit()` Constraints: Not nullable, Maximum length: 3
`BigDecimal`	`getB_o_m_header_quantity_primary()` Constraints: Not nullable, Precision: 13, Scale: 3
`String`	`getB_o_m_item_description()` Constraints: Not nullable, Maximum length: 40
`String`	`getB_o_m_item_is_discontinued()` Constraints: Not nullable, Maximum length: 1
`String`	`getB_o_m_no_nxt_lvl()` Constraints: Not nullable, Maximum length: 8
`String`	`getB_o_m_usage_nxt_lvl()` Constraints: Not nullable, Maximum length: 1
`BigDecimal`	`getBase_qty_nxt_lvl()` Constraints: Not nullable, Precision: 13, Scale: 3
`String`	`getBase_unit_nxt_lvl()` Constraints: Not nullable, Maximum length: 3
`String`	`getBase_uom()` Constraints: Not nullable, Maximum length: 3
`String`	`getBatch_entry()` Constraints: Not nullable, Maximum length: 1
`Boolean`	`getBatch_mgmt()` Constraints: none
`BigDecimal`	`getBill_of_material_base_quant()` Constraints: Not nullable, Precision: 13, Scale: 3
`BigDecimal`	`getBill_of_material_comp_quant()` Constraints: Not nullable, Precision: 13, Scale: 3
`String`	`getBill_of_material_component()` Constraints: Not nullable, Maximum length: 40
`String`	`getBill_of_material_item_category()` Constraints: Not nullable, Maximum length: 1
`String`	`getBill_of_material_item_number()` Constraints: Not nullable, Maximum length: 4
`BigDecimal`	`getBill_of_material_item_quantity()` Constraints: Not nullable, Precision: 13, Scale: 3
`String`	`getBill_of_material_item_unit()` Constraints: Not nullable, Maximum length: 3
`String`	`getBill_of_material_root_variant()` Constraints: Not nullable, Maximum length: 2
`String`	`getBill_Of_Material_Root()` Constraints: Not nullable, Maximum length: 8
`String`	`getBill_of_material_variant_usage()` Constraints: Not nullable, Maximum length: 1
`String`	`getBill_of_material_variant()` Constraints: Not nullable, Maximum length: 2
`String`	`getBill_of_material()` Constraints: Not nullable, Maximum length: 8
`String`	`getBom_change_number()` Constraints: Not nullable, Maximum length: 12
`Boolean`	`getBulk_material()` Constraints: none
`String`	`getChange_number()` Constraints: Not nullable, Maximum length: 12
`String`	`getChg_to_eng_chg_number()` Constraints: Not nullable, Maximum length: 12
`String`	`getClass_type()` Constraints: Not nullable, Maximum length: 3
`String`	`getClassification()` Constraints: Not nullable, Maximum length: 8
`String`	`getClassProperty()` Constraints: Not nullable, Maximum length: 18
`Boolean`	`getCo_product()` Constraints: none
`String`	`getCommodity_code()` Constraints: Not nullable, Maximum length: 17
`String`	`getComp_maint_status()` Constraints: Not nullable, Maximum length: 15
`BigDecimal`	`getComp_scrap_itm_mat()` Constraints: Not nullable, Precision: 5, Scale: 2
`BigDecimal`	`getComp_scrap_itm()` Constraints: Not nullable, Precision: 5, Scale: 2
`Boolean`	`getConf_bom_nxt_lvl()` Constraints: none
`String`	`getConfig_mat_var()` Constraints: Not nullable, Maximum length: 18
`Boolean`	`getConfig_multi_level()` Constraints: none
`String`	`getCost_element()` Constraints: Not nullable, Maximum length: 10
`String`	`getCounter()` Constraints: Not nullable, Maximum length: 8
`String`	`getCreated_by_user()` Constraints: Not nullable, Maximum length: 12
`String`	`getCurrency()` Constraints: Not nullable, Maximum length: 5
`String`	`getCustoms_preference()` Constraints: Not nullable, Maximum length: 1
`Boolean`	`getDat_hist_nxt_lvl()` Constraints: none
`Boolean`	`getDel_Ind_nxt_lvl()` Constraints: none
`Boolean`	`getDeletion_indicator()` Constraints: none
`BigDecimal`	`getDelivery_time_in_days()` Constraints: Not nullable, Precision: 3, Scale: 0
`BigDecimal`	`getDenominator()` Constraints: Not nullable, Precision: 5, Scale: 0
`String`	`getDiscont_group()` Constraints: Not nullable, Maximum length: 2
`String`	`getDistribution_key()` Constraints: Not nullable, Maximum length: 4
`String`	`getDoc_number()` Constraints: Not nullable, Maximum length: 25
`Boolean`	`getDoc_reqd()` Constraints: none
`String`	`getDoc_status()` Constraints: Not nullable, Maximum length: 2
`String`	`getDoc_type()` Constraints: Not nullable, Maximum length: 3
`String`	`getDoc_version()` Constraints: Not nullable, Maximum length: 2
`String`	`getDoc()` Constraints: Not nullable, Maximum length: 22
`String`	`getDocument_part()` Constraints: Not nullable, Maximum length: 3
`String`	`getDocument_type()` Constraints: Not nullable, Maximum length: 3
`String`	`getDocument_version()` Constraints: Not nullable, Maximum length: 2
`LocalDateTime`	`getEffective_out_date()` Constraints: Not nullable, Precision: 0
`Boolean`	`getEngineering_design()` Constraints: none
`String`	`getException_bom()` Constraints: Not nullable, Maximum length: 4
`String`	`getExplosion_type()` Constraints: Not nullable, Maximum length: 2
`Boolean`	`getFixed_price_co_prod()` Constraints: none
`Boolean`	`getFixed_quantity()` Constraints: none
`String`	`getFollow_up_grp()` Constraints: Not nullable, Maximum length: 2
`Boolean`	`getFollow_up_item()` Constraints: none
`String`	`getFollow_up_product()` Constraints: Not nullable, Maximum length: 40
`String`	`getFormula_key()` Constraints: Not nullable, Maximum length: 2
`BigDecimal`	`getGoods_receipt_duration_in_days()` Constraints: Not nullable, Precision: 3, Scale: 0
`String`	`getGoods_recipient()` Constraints: Not nullable, Maximum length: 12
`String`	`getHeader_record_id()` Constraints: Not nullable, Maximum length: 1
`LocalDateTime`	`getHeader_validity_end_date()` Constraints: Not nullable, Precision: 0
`LocalDateTime`	`getHeader_validity_start_date()` Constraints: Not nullable, Precision: 0
`Boolean`	`getHl_configuration()` Constraints: none
`String`	`getIndividual_coll()` Constraints: Not nullable, Maximum length: 1
`String`	`getInternal_obj_no()` Constraints: Not nullable, Maximum length: 18
`String`	`getIntra_material()` Constraints: Not nullable, Maximum length: 40
`String`	`getIs_b_o_m_item_spare_part()` Constraints: Not nullable, Maximum length: 1
`Boolean`	`getIs_c_a_d()` Constraints: none
`String`	`getIs_material_provision()` Constraints: Not nullable, Maximum length: 1
`Boolean`	`getIs_phantom_item()` Constraints: none
`Boolean`	`getIs_software_component()` Constraints: none
`String`	`getIssuing_plant()` Constraints: Not nullable, Maximum length: 4
`String`	`getItem_category()` Constraints: Not nullable, Maximum length: 1
`String`	`getItem_description_line_2()` Constraints: Not nullable, Maximum length: 40
`String`	`getItem_identification()` Constraints: Not nullable, Maximum length: 8
`String`	`getItem_node()` Constraints: Not nullable, Maximum length: 8
`Boolean`	`getItem_sign()` Constraints: none
`protected Map<String,Object>`	`getKey()`
`LocalDateTime`	`getLast_change_date()` Constraints: Not nullable, Precision: 0
`String`	`getLast_changed_by_user()` Constraints: Not nullable, Maximum length: 12
`BigDecimal`	`getLead_time_offset()` Constraints: Not nullable, Precision: 3, Scale: 0
`String`	`getLong_text_lang()` Constraints: Not nullable, Maximum length: 2
`String`	`getLow_level_code()` Constraints: Not nullable, Maximum length: 3
`String`	`getM_r_p_type()` Constraints: Not nullable, Maximum length: 2
`String`	`getMaintenance_status()` Constraints: Not nullable, Maximum length: 15
`BigDecimal`	`getMat_purity_in_perc()` Constraints: Not nullable, Precision: 5, Scale: 2
`BigDecimal`	`getMaterial_component_price()` Constraints: Not nullable, Precision: 12, Scale: 3
`String`	`getMaterial_group()` Constraints: Not nullable, Maximum length: 9
`Boolean`	`getMaterial_is_configurable()` Constraints: none
`String`	`getMaterial_Name()` Constraints: Not nullable, Maximum length: 40
`String`	`getMaterial_type()` Constraints: Not nullable, Maximum length: 4
`BigDecimal`	`getMoving_price()` Constraints: Not nullable, Precision: 12, Scale: 3
`Boolean`	`getMultiple_sel()` Constraints: none
`Boolean`	`getNet_scrap_indicator()` Constraints: none
`String`	`getNo_cu_instances()` Constraints: Not nullable, Maximum length: 6
`String`	`getNo_of_sheets()` Constraints: Not nullable, Maximum length: 3
`BigDecimal`	`getNo_var_size_items()` Constraints: Not nullable, Precision: 13, Scale: 3
`BigDecimal`	`getNumerator()` Constraints: Not nullable, Precision: 5, Scale: 0
`String`	`getObj_dep_assgt_no()` Constraints: Not nullable, Maximum length: 18
`String`	`getObject_description()` Constraints: Not nullable, Maximum length: 40
`String`	`getObject_type()` Constraints: Not nullable, Maximum length: 1
`BigDecimal`	`getOper_lt_offset()` Constraints: Not nullable, Precision: 3, Scale: 0
`String`	`getOper_lto_unit()` Constraints: Not nullable, Maximum length: 3
`BigDecimal`	`getOperation_scrap_perc()` Constraints: Not nullable, Precision: 5, Scale: 2
`String`	`getOrg_area()` Constraints: Not nullable, Maximum length: 10
`String`	`getPage_format()` Constraints: Not nullable, Maximum length: 4
`String`	`getPage_number()` Constraints: Not nullable, Maximum length: 3
`BigDecimal`	`getPath_predecessor()` Constraints: Not nullable, Precision: 4, Scale: 0
`BigDecimal`	`getPath()` Constraints: Not nullable, Precision: 4, Scale: 0
`Boolean`	`getPlant_maintenance()` Constraints: none
`String`	`getPlant_sp_matl_status()` Constraints: Not nullable, Maximum length: 2
`String`	`getPlant()` Constraints: Not nullable, Maximum length: 4
`LocalDateTime`	`getPlt_sp_status_valid_from()` Constraints: Not nullable, Precision: 0
`Boolean`	`getPm_assembly()` Constraints: none
`String`	`getPrice_control()` Constraints: Not nullable, Maximum length: 1
`BigDecimal`	`getPrice_unit()` Constraints: Not nullable, Precision: 5, Scale: 0
`String`	`getPriority()` Constraints: Not nullable, Maximum length: 2
`Boolean`	`getProcured_externally()` Constraints: none
`String`	`getProd_order_issue_location()` Constraints: Not nullable, Maximum length: 4
`String`	`getProdn_supply_area()` Constraints: Not nullable, Maximum length: 10
`Boolean`	`getProduction_relevant()` Constraints: none
`String`	`getProduction_supply_area()` Constraints: Not nullable, Maximum length: 10
`String`	`getProduction_version()` Constraints: Not nullable, Maximum length: 4
`String`	`getProfit_center()` Constraints: Not nullable, Maximum length: 10
`String`	`getPurchase_org()` Constraints: Not nullable, Maximum length: 4
`String`	`getPurchasing_group()` Constraints: Not nullable, Maximum length: 3
`String`	`getPurchasing_organisation()` Constraints: Not nullable, Maximum length: 4
`BigDecimal`	`getQty_var_size_item()` Constraints: Not nullable, Precision: 13, Scale: 3
`LocalDateTime`	`getRecord_creation_date()` Constraints: Not nullable, Precision: 0
`Boolean`	`getRecurisve()` Constraints: none
`Boolean`	`getRecurs_allowed()` Constraints: none
`String`	`getReference_point()` Constraints: Not nullable, Maximum length: 20
`String`	`getRelevancy_to_costing()` Constraints: Not nullable, Maximum length: 1
`String`	`getRelevant_to_sales()` Constraints: Not nullable, Maximum length: 1
`Boolean`	`getRequired_component()` Constraints: none
`String`	`getRequirement_segment()` Constraints: Not nullable, Maximum length: 40
`String`	`getRevision_level()` Constraints: Not nullable, Maximum length: 2
`BigDecimal`	`getScrap_qty_bun()` Constraints: Not nullable, Precision: 13, Scale: 3
`String`	`getSerial_no_profile()` Constraints: Not nullable, Maximum length: 4
`String`	`getSize_unit()` Constraints: Not nullable, Maximum length: 3
`BigDecimal`	`getSize1()` Constraints: Not nullable, Precision: 13, Scale: 3
`BigDecimal`	`getSize2()` Constraints: Not nullable, Precision: 13, Scale: 3
`BigDecimal`	`getSize3()` Constraints: Not nullable, Precision: 13, Scale: 3
`Boolean`	`getSoft_comp_indicator()` Constraints: none
`String`	`getSort_string()` Constraints: Not nullable, Maximum length: 10
`String`	`getSpec_proc_costing()` Constraints: Not nullable, Maximum length: 2
`String`	`getSpecial_proc_typ_itm()` Constraints: Not nullable, Maximum length: 2
`String`	`getSpecial_proc_typ_mastr()` Constraints: Not nullable, Maximum length: 2
`String`	`getSpecial_procurement_type()` Constraints: Not nullable, Maximum length: 2
`BigDecimal`	`getStandard_price()` Constraints: Not nullable, Precision: 12, Scale: 3
`String`	`getStatus_text()` Constraints: Not nullable, Maximum length: 16
`String`	`getStock_segment()` Constraints: Not nullable, Maximum length: 40
`String`	`getStorage_location()` Constraints: Not nullable, Maximum length: 4
`String`	`getStrategy()` Constraints: Not nullable, Maximum length: 1
`Boolean`	`getSub_item_indicator()` Constraints: none
`String`	`getSupplier()` Constraints: Not nullable, Maximum length: 10
`Integer`	`getTable_row()` Constraints: none
`String`	`getTech_status_from()` Constraints: Not nullable, Maximum length: 12
`Boolean`	`getTest_hist_nxt_lvl()` Constraints: none
`String`	`getTotals_record_id()` Constraints: Not nullable, Maximum length: 1
`Class<DBomheaderforexplosionOut>`	`getType()`
`String`	`getUnit_of_measure()` Constraints: Not nullable, Maximum length: 3
`String`	`getUnloading_point()` Constraints: Not nullable, Maximum length: 25
`String`	`getUom_usage()` Constraints: Not nullable, Maximum length: 1
`BigDecimal`	`getUsage_probability()` Constraints: Not nullable, Precision: 3, Scale: 0
`LocalDateTime`	`getValidity_end_date()` Constraints: Not nullable, Precision: 0
`LocalDateTime`	`getValidity_start_date()` Constraints: Not nullable, Precision: 0
`String`	`getValuation_category()` Constraints: Not nullable, Maximum length: 1
`Boolean`	`getVariants_nxt_lvl()` Constraints: none
`String`	`getX_plant_material_status()` Constraints: Not nullable, Maximum length: 2
`LocalDateTime`	`getX_plt_status_valid_from()` Constraints: Not nullable, Precision: 0
`int`	`hashCode()`
`void`	`setAlt_item_group(String alt_item_group)` Constraints: Not nullable, Maximum length: 2
`void`	`setAlt_nxt_lvl(Boolean alt_nxt_lvl)` Constraints: none
`void`	`setAlternative_item(Boolean alternative_item)` Constraints: none
`void`	`setAs_selection_cond(Boolean as_selection_cond)` Constraints: none
`void`	`setAssembly_indicator(Boolean assembly_indicator)` Constraints: none
`void`	`setAssign_effect_vals(Boolean assign_effect_vals)` Constraints: none
`void`	`setAssy_scrap_itm_mat(BigDecimal assy_scrap_itm_mat)` Constraints: Not nullable, Precision: 5, Scale: 2
`void`	`setB_o_m_alt_nxt_lvl(String b_o_m_alt_nxt_lvl)` Constraints: Not nullable, Maximum length: 2
`void`	`setB_o_m_alternative_text(String b_o_m_alternative_text)` Constraints: Not nullable, Maximum length: 40
`void`	`setB_o_m_cat_nxt_lvl(String b_o_m_cat_nxt_lvl)` Constraints: Not nullable, Maximum length: 1
`void`	`setB_o_m_category(String b_o_m_category)` Constraints: Not nullable, Maximum length: 1
`void`	`setB_o_m_component_description(String b_o_m_component_description)` Constraints: Not nullable, Maximum length: 40
`void`	`setB_o_m_explosion_level(BigDecimal b_o_m_explosion_level)` Constraints: Not nullable, Precision: 2, Scale: 0
`void`	`setB_o_m_hdr_matl_hier_node(String b_o_m_hdr_matl_hier_node)` Constraints: Not nullable, Maximum length: 40
`void`	`setB_O_M_Hdr_Root_Matl_Hier_Node(String b_O_M_Hdr_Root_Matl_Hier_Node)` Constraints: Not nullable, Maximum length: 40
`void`	`setB_o_m_header_base_unit(String b_o_m_header_base_unit)` Constraints: Not nullable, Maximum length: 3
`void`	`setB_o_m_header_quantity_primary(BigDecimal b_o_m_header_quantity_primary)` Constraints: Not nullable, Precision: 13, Scale: 3
`void`	`setB_o_m_item_description(String b_o_m_item_description)` Constraints: Not nullable, Maximum length: 40
`void`	`setB_o_m_item_is_discontinued(String b_o_m_item_is_discontinued)` Constraints: Not nullable, Maximum length: 1
`void`	`setB_o_m_no_nxt_lvl(String b_o_m_no_nxt_lvl)` Constraints: Not nullable, Maximum length: 8
`void`	`setB_o_m_usage_nxt_lvl(String b_o_m_usage_nxt_lvl)` Constraints: Not nullable, Maximum length: 1
`void`	`setBase_qty_nxt_lvl(BigDecimal base_qty_nxt_lvl)` Constraints: Not nullable, Precision: 13, Scale: 3
`void`	`setBase_unit_nxt_lvl(String base_unit_nxt_lvl)` Constraints: Not nullable, Maximum length: 3
`void`	`setBase_uom(String base_uom)` Constraints: Not nullable, Maximum length: 3
`void`	`setBatch_entry(String batch_entry)` Constraints: Not nullable, Maximum length: 1
`void`	`setBatch_mgmt(Boolean batch_mgmt)` Constraints: none
`void`	`setBill_of_material_base_quant(BigDecimal bill_of_material_base_quant)` Constraints: Not nullable, Precision: 13, Scale: 3
`void`	`setBill_of_material_comp_quant(BigDecimal bill_of_material_comp_quant)` Constraints: Not nullable, Precision: 13, Scale: 3
`void`	`setBill_of_material_component(String bill_of_material_component)` Constraints: Not nullable, Maximum length: 40
`void`	`setBill_of_material_item_category(String bill_of_material_item_category)` Constraints: Not nullable, Maximum length: 1
`void`	`setBill_of_material_item_number(String bill_of_material_item_number)` Constraints: Not nullable, Maximum length: 4
`void`	`setBill_of_material_item_quantity(BigDecimal bill_of_material_item_quantity)` Constraints: Not nullable, Precision: 13, Scale: 3
`void`	`setBill_of_material_item_unit(String bill_of_material_item_unit)` Constraints: Not nullable, Maximum length: 3
`void`	`setBill_of_material_root_variant(String bill_of_material_root_variant)` Constraints: Not nullable, Maximum length: 2
`void`	`setBill_Of_Material_Root(String bill_Of_Material_Root)` Constraints: Not nullable, Maximum length: 8
`void`	`setBill_of_material_variant_usage(String bill_of_material_variant_usage)` Constraints: Not nullable, Maximum length: 1
`void`	`setBill_of_material_variant(String bill_of_material_variant)` Constraints: Not nullable, Maximum length: 2
`void`	`setBill_of_material(String bill_of_material)` Constraints: Not nullable, Maximum length: 8
`void`	`setBom_change_number(String bom_change_number)` Constraints: Not nullable, Maximum length: 12
`void`	`setBulk_material(Boolean bulk_material)` Constraints: none
`void`	`setChange_number(String change_number)` Constraints: Not nullable, Maximum length: 12
`void`	`setChg_to_eng_chg_number(String chg_to_eng_chg_number)` Constraints: Not nullable, Maximum length: 12
`void`	`setClass_type(String class_type)` Constraints: Not nullable, Maximum length: 3
`void`	`setClassification(String classification)` Constraints: Not nullable, Maximum length: 8
`void`	`setClassProperty(String classProperty)` Constraints: Not nullable, Maximum length: 18
`void`	`setCo_product(Boolean co_product)` Constraints: none
`void`	`setCommodity_code(String commodity_code)` Constraints: Not nullable, Maximum length: 17
`void`	`setComp_maint_status(String comp_maint_status)` Constraints: Not nullable, Maximum length: 15
`void`	`setComp_scrap_itm_mat(BigDecimal comp_scrap_itm_mat)` Constraints: Not nullable, Precision: 5, Scale: 2
`void`	`setComp_scrap_itm(BigDecimal comp_scrap_itm)` Constraints: Not nullable, Precision: 5, Scale: 2
`void`	`setConf_bom_nxt_lvl(Boolean conf_bom_nxt_lvl)` Constraints: none
`void`	`setConfig_mat_var(String config_mat_var)` Constraints: Not nullable, Maximum length: 18
`void`	`setConfig_multi_level(Boolean config_multi_level)` Constraints: none
`void`	`setCost_element(String cost_element)` Constraints: Not nullable, Maximum length: 10
`void`	`setCounter(String counter)` Constraints: Not nullable, Maximum length: 8
`void`	`setCreated_by_user(String created_by_user)` Constraints: Not nullable, Maximum length: 12
`void`	`setCurrency(String currency)` Constraints: Not nullable, Maximum length: 5
`void`	`setCustoms_preference(String customs_preference)` Constraints: Not nullable, Maximum length: 1
`void`	`setDat_hist_nxt_lvl(Boolean dat_hist_nxt_lvl)` Constraints: none
`void`	`setDel_Ind_nxt_lvl(Boolean del_Ind_nxt_lvl)` Constraints: none
`void`	`setDeletion_indicator(Boolean deletion_indicator)` Constraints: none
`void`	`setDelivery_time_in_days(BigDecimal delivery_time_in_days)` Constraints: Not nullable, Precision: 3, Scale: 0
`void`	`setDenominator(BigDecimal denominator)` Constraints: Not nullable, Precision: 5, Scale: 0
`void`	`setDiscont_group(String discont_group)` Constraints: Not nullable, Maximum length: 2
`void`	`setDistribution_key(String distribution_key)` Constraints: Not nullable, Maximum length: 4
`void`	`setDoc_number(String doc_number)` Constraints: Not nullable, Maximum length: 25
`void`	`setDoc_reqd(Boolean doc_reqd)` Constraints: none
`void`	`setDoc_status(String doc_status)` Constraints: Not nullable, Maximum length: 2
`void`	`setDoc_type(String doc_type)` Constraints: Not nullable, Maximum length: 3
`void`	`setDoc_version(String doc_version)` Constraints: Not nullable, Maximum length: 2
`void`	`setDoc(String doc)` Constraints: Not nullable, Maximum length: 22
`void`	`setDocument_part(String document_part)` Constraints: Not nullable, Maximum length: 3
`void`	`setDocument_type(String document_type)` Constraints: Not nullable, Maximum length: 3
`void`	`setDocument_version(String document_version)` Constraints: Not nullable, Maximum length: 2
`void`	`setEffective_out_date(LocalDateTime effective_out_date)` Constraints: Not nullable, Precision: 0
`void`	`setEngineering_design(Boolean engineering_design)` Constraints: none
`void`	`setException_bom(String exception_bom)` Constraints: Not nullable, Maximum length: 4
`void`	`setExplosion_type(String explosion_type)` Constraints: Not nullable, Maximum length: 2
`void`	`setFixed_price_co_prod(Boolean fixed_price_co_prod)` Constraints: none
`void`	`setFixed_quantity(Boolean fixed_quantity)` Constraints: none
`void`	`setFollow_up_grp(String follow_up_grp)` Constraints: Not nullable, Maximum length: 2
`void`	`setFollow_up_item(Boolean follow_up_item)` Constraints: none
`void`	`setFollow_up_product(String follow_up_product)` Constraints: Not nullable, Maximum length: 40
`void`	`setFormula_key(String formula_key)` Constraints: Not nullable, Maximum length: 2
`void`	`setGoods_receipt_duration_in_days(BigDecimal goods_receipt_duration_in_days)` Constraints: Not nullable, Precision: 3, Scale: 0
`void`	`setGoods_recipient(String goods_recipient)` Constraints: Not nullable, Maximum length: 12
`void`	`setHeader_record_id(String header_record_id)` Constraints: Not nullable, Maximum length: 1
`void`	`setHeader_validity_end_date(LocalDateTime header_validity_end_date)` Constraints: Not nullable, Precision: 0
`void`	`setHeader_validity_start_date(LocalDateTime header_validity_start_date)` Constraints: Not nullable, Precision: 0
`void`	`setHl_configuration(Boolean hl_configuration)` Constraints: none
`void`	`setIndividual_coll(String individual_coll)` Constraints: Not nullable, Maximum length: 1
`void`	`setInternal_obj_no(String internal_obj_no)` Constraints: Not nullable, Maximum length: 18
`void`	`setIntra_material(String intra_material)` Constraints: Not nullable, Maximum length: 40
`void`	`setIs_b_o_m_item_spare_part(String is_b_o_m_item_spare_part)` Constraints: Not nullable, Maximum length: 1
`void`	`setIs_c_a_d(Boolean is_c_a_d)` Constraints: none
`void`	`setIs_material_provision(String is_material_provision)` Constraints: Not nullable, Maximum length: 1
`void`	`setIs_phantom_item(Boolean is_phantom_item)` Constraints: none
`void`	`setIs_software_component(Boolean is_software_component)` Constraints: none
`void`	`setIssuing_plant(String issuing_plant)` Constraints: Not nullable, Maximum length: 4
`void`	`setItem_category(String item_category)` Constraints: Not nullable, Maximum length: 1
`void`	`setItem_description_line_2(String item_description_line_2)` Constraints: Not nullable, Maximum length: 40
`void`	`setItem_identification(String item_identification)` Constraints: Not nullable, Maximum length: 8
`void`	`setItem_node(String item_node)` Constraints: Not nullable, Maximum length: 8
`void`	`setItem_sign(Boolean item_sign)` Constraints: none
`void`	`setLast_change_date(LocalDateTime last_change_date)` Constraints: Not nullable, Precision: 0
`void`	`setLast_changed_by_user(String last_changed_by_user)` Constraints: Not nullable, Maximum length: 12
`void`	`setLead_time_offset(BigDecimal lead_time_offset)` Constraints: Not nullable, Precision: 3, Scale: 0
`void`	`setLong_text_lang(String long_text_lang)` Constraints: Not nullable, Maximum length: 2
`void`	`setLow_level_code(String low_level_code)` Constraints: Not nullable, Maximum length: 3
`void`	`setM_r_p_type(String m_r_p_type)` Constraints: Not nullable, Maximum length: 2
`void`	`setMaintenance_status(String maintenance_status)` Constraints: Not nullable, Maximum length: 15
`void`	`setMat_purity_in_perc(BigDecimal mat_purity_in_perc)` Constraints: Not nullable, Precision: 5, Scale: 2
`void`	`setMaterial_component_price(BigDecimal material_component_price)` Constraints: Not nullable, Precision: 12, Scale: 3
`void`	`setMaterial_group(String material_group)` Constraints: Not nullable, Maximum length: 9
`void`	`setMaterial_is_configurable(Boolean material_is_configurable)` Constraints: none
`void`	`setMaterial_Name(String material_Name)` Constraints: Not nullable, Maximum length: 40
`void`	`setMaterial_type(String material_type)` Constraints: Not nullable, Maximum length: 4
`void`	`setMoving_price(BigDecimal moving_price)` Constraints: Not nullable, Precision: 12, Scale: 3
`void`	`setMultiple_sel(Boolean multiple_sel)` Constraints: none
`void`	`setNet_scrap_indicator(Boolean net_scrap_indicator)` Constraints: none
`void`	`setNo_cu_instances(String no_cu_instances)` Constraints: Not nullable, Maximum length: 6
`void`	`setNo_of_sheets(String no_of_sheets)` Constraints: Not nullable, Maximum length: 3
`void`	`setNo_var_size_items(BigDecimal no_var_size_items)` Constraints: Not nullable, Precision: 13, Scale: 3
`void`	`setNumerator(BigDecimal numerator)` Constraints: Not nullable, Precision: 5, Scale: 0
`void`	`setObj_dep_assgt_no(String obj_dep_assgt_no)` Constraints: Not nullable, Maximum length: 18
`void`	`setObject_description(String object_description)` Constraints: Not nullable, Maximum length: 40
`void`	`setObject_type(String object_type)` Constraints: Not nullable, Maximum length: 1
`void`	`setOper_lt_offset(BigDecimal oper_lt_offset)` Constraints: Not nullable, Precision: 3, Scale: 0
`void`	`setOper_lto_unit(String oper_lto_unit)` Constraints: Not nullable, Maximum length: 3
`void`	`setOperation_scrap_perc(BigDecimal operation_scrap_perc)` Constraints: Not nullable, Precision: 5, Scale: 2
`void`	`setOrg_area(String org_area)` Constraints: Not nullable, Maximum length: 10
`void`	`setPage_format(String page_format)` Constraints: Not nullable, Maximum length: 4
`void`	`setPage_number(String page_number)` Constraints: Not nullable, Maximum length: 3
`void`	`setPath_predecessor(BigDecimal path_predecessor)` Constraints: Not nullable, Precision: 4, Scale: 0
`void`	`setPath(BigDecimal path)` Constraints: Not nullable, Precision: 4, Scale: 0
`void`	`setPlant_maintenance(Boolean plant_maintenance)` Constraints: none
`void`	`setPlant_sp_matl_status(String plant_sp_matl_status)` Constraints: Not nullable, Maximum length: 2
`void`	`setPlant(String plant)` Constraints: Not nullable, Maximum length: 4
`void`	`setPlt_sp_status_valid_from(LocalDateTime plt_sp_status_valid_from)` Constraints: Not nullable, Precision: 0
`void`	`setPm_assembly(Boolean pm_assembly)` Constraints: none
`void`	`setPrice_control(String price_control)` Constraints: Not nullable, Maximum length: 1
`void`	`setPrice_unit(BigDecimal price_unit)` Constraints: Not nullable, Precision: 5, Scale: 0
`void`	`setPriority(String priority)` Constraints: Not nullable, Maximum length: 2
`void`	`setProcured_externally(Boolean procured_externally)` Constraints: none
`void`	`setProd_order_issue_location(String prod_order_issue_location)` Constraints: Not nullable, Maximum length: 4
`void`	`setProdn_supply_area(String prodn_supply_area)` Constraints: Not nullable, Maximum length: 10
`void`	`setProduction_relevant(Boolean production_relevant)` Constraints: none
`void`	`setProduction_supply_area(String production_supply_area)` Constraints: Not nullable, Maximum length: 10
`void`	`setProduction_version(String production_version)` Constraints: Not nullable, Maximum length: 4
`void`	`setProfit_center(String profit_center)` Constraints: Not nullable, Maximum length: 10
`void`	`setPurchase_org(String purchase_org)` Constraints: Not nullable, Maximum length: 4
`void`	`setPurchasing_group(String purchasing_group)` Constraints: Not nullable, Maximum length: 3
`void`	`setPurchasing_organisation(String purchasing_organisation)` Constraints: Not nullable, Maximum length: 4
`void`	`setQty_var_size_item(BigDecimal qty_var_size_item)` Constraints: Not nullable, Precision: 13, Scale: 3
`void`	`setRecord_creation_date(LocalDateTime record_creation_date)` Constraints: Not nullable, Precision: 0
`void`	`setRecurisve(Boolean recurisve)` Constraints: none
`void`	`setRecurs_allowed(Boolean recurs_allowed)` Constraints: none
`void`	`setReference_point(String reference_point)` Constraints: Not nullable, Maximum length: 20
`void`	`setRelevancy_to_costing(String relevancy_to_costing)` Constraints: Not nullable, Maximum length: 1
`void`	`setRelevant_to_sales(String relevant_to_sales)` Constraints: Not nullable, Maximum length: 1
`void`	`setRequired_component(Boolean required_component)` Constraints: none
`void`	`setRequirement_segment(String requirement_segment)` Constraints: Not nullable, Maximum length: 40
`void`	`setRevision_level(String revision_level)` Constraints: Not nullable, Maximum length: 2
`void`	`setScrap_qty_bun(BigDecimal scrap_qty_bun)` Constraints: Not nullable, Precision: 13, Scale: 3
`void`	`setSerial_no_profile(String serial_no_profile)` Constraints: Not nullable, Maximum length: 4
`void`	`setSize_unit(String size_unit)` Constraints: Not nullable, Maximum length: 3
`void`	`setSize1(BigDecimal size1)` Constraints: Not nullable, Precision: 13, Scale: 3
`void`	`setSize2(BigDecimal size2)` Constraints: Not nullable, Precision: 13, Scale: 3
`void`	`setSize3(BigDecimal size3)` Constraints: Not nullable, Precision: 13, Scale: 3
`void`	`setSoft_comp_indicator(Boolean soft_comp_indicator)` Constraints: none
`void`	`setSort_string(String sort_string)` Constraints: Not nullable, Maximum length: 10
`void`	`setSpec_proc_costing(String spec_proc_costing)` Constraints: Not nullable, Maximum length: 2
`void`	`setSpecial_proc_typ_itm(String special_proc_typ_itm)` Constraints: Not nullable, Maximum length: 2
`void`	`setSpecial_proc_typ_mastr(String special_proc_typ_mastr)` Constraints: Not nullable, Maximum length: 2
`void`	`setSpecial_procurement_type(String special_procurement_type)` Constraints: Not nullable, Maximum length: 2
`void`	`setStandard_price(BigDecimal standard_price)` Constraints: Not nullable, Precision: 12, Scale: 3
`void`	`setStatus_text(String status_text)` Constraints: Not nullable, Maximum length: 16
`void`	`setStock_segment(String stock_segment)` Constraints: Not nullable, Maximum length: 40
`void`	`setStorage_location(String storage_location)` Constraints: Not nullable, Maximum length: 4
`void`	`setStrategy(String strategy)` Constraints: Not nullable, Maximum length: 1
`void`	`setSub_item_indicator(Boolean sub_item_indicator)` Constraints: none
`void`	`setSupplier(String supplier)` Constraints: Not nullable, Maximum length: 10
`void`	`setTable_row(Integer table_row)` Constraints: none
`void`	`setTech_status_from(String tech_status_from)` Constraints: Not nullable, Maximum length: 12
`void`	`setTest_hist_nxt_lvl(Boolean test_hist_nxt_lvl)` Constraints: none
`void`	`setTotals_record_id(String totals_record_id)` Constraints: Not nullable, Maximum length: 1
`void`	`setUnit_of_measure(String unit_of_measure)` Constraints: Not nullable, Maximum length: 3
`void`	`setUnloading_point(String unloading_point)` Constraints: Not nullable, Maximum length: 25
`void`	`setUom_usage(String uom_usage)` Constraints: Not nullable, Maximum length: 1
`void`	`setUsage_probability(BigDecimal usage_probability)` Constraints: Not nullable, Precision: 3, Scale: 0
`void`	`setValidity_end_date(LocalDateTime validity_end_date)` Constraints: Not nullable, Precision: 0
`void`	`setValidity_start_date(LocalDateTime validity_start_date)` Constraints: Not nullable, Precision: 0
`void`	`setValuation_category(String valuation_category)` Constraints: Not nullable, Maximum length: 1
`void`	`setVariants_nxt_lvl(Boolean variants_nxt_lvl)` Constraints: none
`void`	`setX_plant_material_status(String x_plant_material_status)` Constraints: Not nullable, Maximum length: 2
`void`	`setX_plt_status_valid_from(LocalDateTime x_plt_status_valid_from)` Constraints: Not nullable, Precision: 0
`protected Map<String,Object>`	`toMapOfFields()`
`String`	`toString()`

Methods inherited from class com.sap.cloud.sdk.datamodel.odata.helper.VdmObject
getChangedFields, getCustomField, getCustomField, getCustomFieldNames, getCustomFields, getSetOfCustomFields, getSetOfFields, getSetOfNavigationProperties, hasCustomField, hasCustomField, rememberChangedField, resetChangedFields, setCustomField, setCustomField, toMap, toMapOfCustomFields, toMapOfNavigationProperties

Methods inherited from class java.lang.Object
clone, finalize, getClass, notify, notifyAll, wait, wait, wait

- Constructor Detail
  - DBomheaderforexplosionOut
```
public DBomheaderforexplosionOut()
```
  - DBomheaderforexplosionOut
```
public DBomheaderforexplosionOut(@Nullable
                                 Boolean alternative_item,
                                 @Nullable
                                 String alt_item_group,
                                 @Nullable
                                 Boolean alt_nxt_lvl,
                                 @Nullable
                                 Boolean assembly_indicator,
                                 @Nullable
                                 Boolean assign_effect_vals,
                                 @Nullable
                                 BigDecimal assy_scrap_itm_mat,
                                 @Nullable
                                 Boolean as_selection_cond,
                                 @Nullable
                                 BigDecimal base_qty_nxt_lvl,
                                 @Nullable
                                 String base_unit_nxt_lvl,
                                 @Nullable
                                 String base_uom,
                                 @Nullable
                                 String batch_entry,
                                 @Nullable
                                 Boolean batch_mgmt,
                                 @Nullable
                                 String bill_of_material,
                                 @Nullable
                                 BigDecimal bill_of_material_base_quant,
                                 @Nullable
                                 String bill_of_material_component,
                                 @Nullable
                                 BigDecimal bill_of_material_comp_quant,
                                 @Nullable
                                 String bill_of_material_item_category,
                                 @Nullable
                                 String bill_of_material_item_number,
                                 @Nullable
                                 BigDecimal bill_of_material_item_quantity,
                                 @Nullable
                                 String bill_of_material_item_unit,
                                 @Nullable
                                 String bill_Of_Material_Root,
                                 @Nullable
                                 String bill_of_material_root_variant,
                                 @Nullable
                                 String bill_of_material_variant,
                                 @Nullable
                                 String bill_of_material_variant_usage,
                                 @Nullable
                                 String bom_change_number,
                                 @Nullable
                                 Boolean bulk_material,
                                 @Nullable
                                 String b_o_m_alternative_text,
                                 @Nullable
                                 String b_o_m_alt_nxt_lvl,
                                 @Nullable
                                 String b_o_m_category,
                                 @Nullable
                                 String b_o_m_cat_nxt_lvl,
                                 @Nullable
                                 String b_o_m_component_description,
                                 @Nullable
                                 BigDecimal b_o_m_explosion_level,
                                 @Nullable
                                 String b_o_m_hdr_matl_hier_node,
                                 @Nullable
                                 String b_O_M_Hdr_Root_Matl_Hier_Node,
                                 @Nullable
                                 String b_o_m_header_base_unit,
                                 @Nullable
                                 BigDecimal b_o_m_header_quantity_primary,
                                 @Nullable
                                 String b_o_m_item_description,
                                 @Nullable
                                 String b_o_m_item_is_discontinued,
                                 @Nullable
                                 String b_o_m_no_nxt_lvl,
                                 @Nullable
                                 String b_o_m_usage_nxt_lvl,
                                 @Nullable
                                 String change_number,
                                 @Nullable
                                 String chg_to_eng_chg_number,
                                 @Nullable
                                 String classProperty,
                                 @Nullable
                                 String classification,
                                 @Nullable
                                 String class_type,
                                 @Nullable
                                 String commodity_code,
                                 @Nullable
                                 String comp_maint_status,
                                 @Nullable
                                 BigDecimal comp_scrap_itm,
                                 @Nullable
                                 BigDecimal comp_scrap_itm_mat,
                                 @Nullable
                                 String config_mat_var,
                                 @Nullable
                                 Boolean config_multi_level,
                                 @Nullable
                                 Boolean conf_bom_nxt_lvl,
                                 @Nullable
                                 String cost_element,
                                 @Nullable
                                 String counter,
                                 @Nullable
                                 Boolean co_product,
                                 @Nullable
                                 String created_by_user,
                                 @Nullable
                                 String currency,
                                 @Nullable
                                 String customs_preference,
                                 @Nullable
                                 Boolean dat_hist_nxt_lvl,
                                 @Nullable
                                 Boolean deletion_indicator,
                                 @Nullable
                                 BigDecimal delivery_time_in_days,
                                 @Nullable
                                 Boolean del_Ind_nxt_lvl,
                                 @Nullable
                                 BigDecimal denominator,
                                 @Nullable
                                 String discont_group,
                                 @Nullable
                                 String distribution_key,
                                 @Nullable
                                 String doc,
                                 @Nullable
                                 String document_part,
                                 @Nullable
                                 String document_type,
                                 @Nullable
                                 String document_version,
                                 @Nullable
                                 String doc_number,
                                 @Nullable
                                 Boolean doc_reqd,
                                 @Nullable
                                 String doc_status,
                                 @Nullable
                                 String doc_type,
                                 @Nullable
                                 String doc_version,
                                 @Nullable
                                 LocalDateTime effective_out_date,
                                 @Nullable
                                 Boolean engineering_design,
                                 @Nullable
                                 String exception_bom,
                                 @Nullable
                                 String explosion_type,
                                 @Nullable
                                 Boolean fixed_price_co_prod,
                                 @Nullable
                                 Boolean fixed_quantity,
                                 @Nullable
                                 String follow_up_grp,
                                 @Nullable
                                 Boolean follow_up_item,
                                 @Nullable
                                 String follow_up_product,
                                 @Nullable
                                 String formula_key,
                                 @Nullable
                                 BigDecimal goods_receipt_duration_in_days,
                                 @Nullable
                                 String goods_recipient,
                                 @Nullable
                                 String header_record_id,
                                 @Nullable
                                 LocalDateTime header_validity_end_date,
                                 @Nullable
                                 LocalDateTime header_validity_start_date,
                                 @Nullable
                                 Boolean hl_configuration,
                                 @Nullable
                                 String individual_coll,
                                 @Nullable
                                 String internal_obj_no,
                                 @Nullable
                                 String intra_material,
                                 @Nullable
                                 String issuing_plant,
                                 @Nullable
                                 String is_b_o_m_item_spare_part,
                                 @Nullable
                                 Boolean is_c_a_d,
                                 @Nullable
                                 String is_material_provision,
                                 @Nullable
                                 Boolean is_phantom_item,
                                 @Nullable
                                 Boolean is_software_component,
                                 @Nullable
                                 String item_category,
                                 @Nullable
                                 String item_description_line_2,
                                 @Nullable
                                 String item_identification,
                                 @Nullable
                                 String item_node,
                                 @Nullable
                                 Boolean item_sign,
                                 @Nullable
                                 String last_changed_by_user,
                                 @Nullable
                                 LocalDateTime last_change_date,
                                 @Nullable
                                 BigDecimal lead_time_offset,
                                 @Nullable
                                 String long_text_lang,
                                 @Nullable
                                 String low_level_code,
                                 @Nullable
                                 String maintenance_status,
                                 @Nullable
                                 BigDecimal material_component_price,
                                 @Nullable
                                 String material_group,
                                 @Nullable
                                 Boolean material_is_configurable,
                                 @Nullable
                                 String material_Name,
                                 @Nullable
                                 String material_type,
                                 @Nullable
                                 BigDecimal mat_purity_in_perc,
                                 @Nullable
                                 BigDecimal moving_price,
                                 @Nullable
                                 Boolean multiple_sel,
                                 @Nullable
                                 String m_r_p_type,
                                 @Nullable
                                 Boolean net_scrap_indicator,
                                 @Nullable
                                 String no_cu_instances,
                                 @Nullable
                                 String no_of_sheets,
                                 @Nullable
                                 BigDecimal no_var_size_items,
                                 @Nullable
                                 BigDecimal numerator,
                                 @Nullable
                                 String object_description,
                                 @Nullable
                                 String object_type,
                                 @Nullable
                                 String obj_dep_assgt_no,
                                 @Nullable
                                 BigDecimal operation_scrap_perc,
                                 @Nullable
                                 String oper_lto_unit,
                                 @Nullable
                                 BigDecimal oper_lt_offset,
                                 @Nullable
                                 String org_area,
                                 @Nullable
                                 String page_format,
                                 @Nullable
                                 String page_number,
                                 @Nullable
                                 BigDecimal path,
                                 @Nullable
                                 BigDecimal path_predecessor,
                                 @Nullable
                                 String plant,
                                 @Nullable
                                 Boolean plant_maintenance,
                                 @Nullable
                                 String plant_sp_matl_status,
                                 @Nullable
                                 LocalDateTime plt_sp_status_valid_from,
                                 @Nullable
                                 Boolean pm_assembly,
                                 @Nullable
                                 String price_control,
                                 @Nullable
                                 BigDecimal price_unit,
                                 @Nullable
                                 String priority,
                                 @Nullable
                                 Boolean procured_externally,
                                 @Nullable
                                 String prodn_supply_area,
                                 @Nullable
                                 Boolean production_relevant,
                                 @Nullable
                                 String production_supply_area,
                                 @Nullable
                                 String production_version,
                                 @Nullable
                                 String prod_order_issue_location,
                                 @Nullable
                                 String profit_center,
                                 @Nullable
                                 String purchase_org,
                                 @Nullable
                                 String purchasing_group,
                                 @Nullable
                                 String purchasing_organisation,
                                 @Nullable
                                 BigDecimal qty_var_size_item,
                                 @Nullable
                                 LocalDateTime record_creation_date,
                                 @Nullable
                                 Boolean recurisve,
                                 @Nullable
                                 Boolean recurs_allowed,
                                 @Nullable
                                 String reference_point,
                                 @Nullable
                                 String relevancy_to_costing,
                                 @Nullable
                                 String relevant_to_sales,
                                 @Nullable
                                 Boolean required_component,
                                 @Nullable
                                 String requirement_segment,
                                 @Nullable
                                 String revision_level,
                                 @Nullable
                                 BigDecimal scrap_qty_bun,
                                 @Nullable
                                 String serial_no_profile,
                                 @Nullable
                                 BigDecimal size1,
                                 @Nullable
                                 BigDecimal size2,
                                 @Nullable
                                 BigDecimal size3,
                                 @Nullable
                                 String size_unit,
                                 @Nullable
                                 Boolean soft_comp_indicator,
                                 @Nullable
                                 String sort_string,
                                 @Nullable
                                 String special_procurement_type,
                                 @Nullable
                                 String special_proc_typ_itm,
                                 @Nullable
                                 String special_proc_typ_mastr,
                                 @Nullable
                                 String spec_proc_costing,
                                 @Nullable
                                 BigDecimal standard_price,
                                 @Nullable
                                 String status_text,
                                 @Nullable
                                 String stock_segment,
                                 @Nullable
                                 String storage_location,
                                 @Nullable
                                 String strategy,
                                 @Nullable
                                 Boolean sub_item_indicator,
                                 @Nullable
                                 String supplier,
                                 @Nullable
                                 Integer table_row,
                                 @Nullable
                                 String tech_status_from,
                                 @Nullable
                                 Boolean test_hist_nxt_lvl,
                                 @Nullable
                                 String totals_record_id,
                                 @Nullable
                                 String unit_of_measure,
                                 @Nullable
                                 String unloading_point,
                                 @Nullable
                                 String uom_usage,
                                 @Nullable
                                 BigDecimal usage_probability,
                                 @Nullable
                                 LocalDateTime validity_end_date,
                                 @Nullable
                                 LocalDateTime validity_start_date,
                                 @Nullable
                                 String valuation_category,
                                 @Nullable
                                 Boolean variants_nxt_lvl,
                                 @Nullable
                                 String x_plant_material_status,
                                 @Nullable
                                 LocalDateTime x_plt_status_valid_from)
```
- Method Detail
  - getType
```
@Nonnull
public Class<DBomheaderforexplosionOut> getType()
```
    Specified by:
    
    getType in class VdmObject<DBomheaderforexplosionOut>
    
    Returns:
    
    The class of this object.
  - toMapOfFields
```
@Nonnull
protected Map<String,Object> toMapOfFields()
```
    Overrides:
    
    toMapOfFields in class VdmObject<DBomheaderforexplosionOut>
  - fromMap
```
protected void fromMap(Map<String,Object> inputValues)
```
    Overrides:
    
    fromMap in class VdmObject<DBomheaderforexplosionOut>
  - getKey
```
@Nonnull
protected Map<String,Object> getKey()
```
    Overrides:
    
    getKey in class VdmObject<DBomheaderforexplosionOut>
    
    Returns:
    
    The compound key of this object.
  - builder
```
public static DBomheaderforexplosionOut.DBomheaderforexplosionOutBuilder builder()
```
  - getAlternative_item
```
@Nullable
public Boolean getAlternative_item()
```
    Constraints: none
    Original property from the Odata EDM: alternative_item
    
    The alternative items are chosen when a production order is created.
    
    Returns:
    
    This indicator allows you to enter more than one component for an item, which can be used as alternative items.
  - getAlt_item_group
```
@Nullable
public String getAlt_item_group()
```
    Constraints: Not nullable, Maximum length: 2
    Original property from the Odata EDM: alt_item_group
    
    As soon as you enter an alternative item group, you see an additional dialog box with the following data: ranking order, strategy, usage probability.You can maintain alternative items in the following situations:Alternative positions with specific usage probabilityThese alternative items are incorporated with a specific usage probability. Enter the usage probability for each alternative item in the group, so that:dependent requirements are determined in requirements planningdependent requirements are changed to a reservation in the production orderAlternative positions as informationYou can enter an alternative item for information purposes. This item would then, for example, only be taken into account in situations involving missing parts.As there should be neither dependent requirements nor a reservation for this item, enter no usage probability.Enter the same character string to denote the alternative items of an alternative item group.Enter the same strategy for all alternative items in the alternative item group.Alternative items are valuated in the following way:Dependent requirements determinationRequirements planning determines the dependent requirements according to the usage probabilities that have been entered.If the usage probability is 0%, then no procurement is planned for the item. For information purposes, however, dependent requirements with 0 as quantity are created.Withdrawal postingYou can control the withdrawal posting for the resevation in the production order in the following way:Withdrawal according to usage probability (manual change is possible)Withdrawal if there is 100% availability(Check ranking order and strategy)Example: See Strategy for alternative position
    
    Returns:
    
    Consolidation of alternative items within a BOM. Every material in the assembly can be included in the alternative item group.
  - getAlt_nxt_lvl
```
@Nullable
public Boolean getAlt_nxt_lvl()
```
    Constraints: none
    Original property from the Odata EDM: alt_nxt_lvl
    
    Returns:
    
    This indicator controls that alternatives can be entered for this bill of material.
  - getAssembly_indicator
```
@Nullable
public Boolean getAssembly_indicator()
```
    Constraints: none
    Original property from the Odata EDM: assembly_indicator
    
    You can use this indicator to restrict the selection of items in the BOM explosion. In this case, only the items that are PM assemblies are shown.The indicator does not interrupt the explosion of the BOM to the lowest lever. There are two steps to the BOM explosion:First, the system explodes the entire BOM, regardless of the indicators selected to restrict items. You do not see the result of this explosion on the screen.Second, the system reads the indicators selected to restrict items, such as the PM assembly indicator.These indicators work as filters. The explosion result you see on the screen only includes the items that fulfil the selection criteria.
    
    Returns:
    
    This indicator shows that this item is part of a technical object (assembly) for which maintenance tasks are planned and carried out.
  - getAssign_effect_vals
```
@Nullable
public Boolean getAssign_effect_vals()
```
    Constraints: none
    Original property from the Odata EDM: assign_effect_vals
    
    If you set the indicator, the following applies:If you only use date validity, you can override the date that the system uses to determine the components. To do this, you set certain change numbers as valid or invalid.If you use parameter effectivity, you can assign values to the effectivity parameters. As well as this you can set certain change numbers to valid or invalid and thus override the parameter variant (the values you previously assigned).
    
    Returns:
    
    Indicates whether you can assign values to the effectivity parameters or override the date, when you explode an assembly or a finished product.
  - getAssy_scrap_itm_mat
```
@Nullable
public BigDecimal getAssy_scrap_itm_mat()
```
    Constraints: Not nullable, Precision: 5, Scale: 2
    Original property from the Odata EDM: assy_scrap_itm_mat
    
    The assembly scrap is used in materials planning to calculate the lot size of the assembly. The system increases the quantity to be produced by the scrap quantity calculated.If the material is an assembly, specify the percentage scrap as required.If the quantity to be produced is 200 pieces and you specify an assembly scrap of 10%, you are reckoning with a scrap quantity of 20 pieces. As a result, 220 pieces are produced.The system increases the quantity to be produced for all of the assembly's components accordingly.
    
    Returns:
    
    Percentage scrap that occurs during production of the material if the material is an assembly.
  - getAs_selection_cond
```
@Nullable
public Boolean getAs_selection_cond()
```
    Constraints: none
    Original property from the Odata EDM: as_selection_cond
    
    If you select this indicator, the classification of the item is taken into account when the object is configured.You can only select this indicator if you have classified the item first (entered a class type).
    
    Returns:
    
    Indicator for defining classification as a selection condition.
  - getBase_qty_nxt_lvl
```
@Nullable
public BigDecimal getBase_qty_nxt_lvl()
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    Original property from the Odata EDM: base_qty_nxt_lvl
    
    In Customizing (bills of material), you can define a value that then becomes the default value when you create a bill of material.
    
    Returns:
    
    A quantity used as a reference by all component quantities in a bill of material.
  - getBase_unit_nxt_lvl
```
@Nullable
public String getBase_unit_nxt_lvl()
```
    Constraints: Not nullable, Maximum length: 3
    Original property from the Odata EDM: base_unit_nxt_lvl
    
    The system determines this unit of measure from the material master record.You cannot make changes, because the stocks of a material are managed in this unit of measure.
    
    Returns:
    
    Unit of measure used to enter the base quantity of a result and/or assembly. It is the reference figure for all component quantities for this bill of material.
  - getBase_uom
```
@Nullable
public String getBase_uom()
```
    Constraints: Not nullable, Maximum length: 3
    Original property from the Odata EDM: base_uom
    
    You define the base unit of measure and also alternative units of measure and their conversion factors in the material master record.Since all data is updated in the base unit of measure, your entry is particularly important for the conversion of alternative units of measure. A quantity in the alternative unit of measure can only be shown precisely if its value can be shown with the decimal places available. To ensure this, please note the following:The base unit of measure is the unit satisfying the highest necessary requirement for precision.The conversion of alternative units of measure to the base unit should result in simple decimal fractions (not, for example, 1/3 = 0.333...).Inventory ManagementIn Inventory Management, the base unit of measure is the same as the stockkeeping unit.ServicesServices have units of measure of their own, including the following:Service unitUnit of measure at the higher item level. The precise quantities of the individual services are each at the detailed service line level.BlanketUnit of measure at service line level for services to be provided once only, and for which no precise quantities can or are to be specified.
    
    Returns:
    
    Unit of measure in which stocks of the material are managed. The system converts all the quantities you enter in other units of measure (alternative units of measure) to the base unit of measure.
  - getBatch_entry
```
@Nullable
public String getBatch_entry()
```
    Constraints: Not nullable, Maximum length: 1
    Original property from the Odata EDM: batch_entry
    
    This indicator refers to the components of an order, not to the finished product to be manufactured. You have the following options:The batches can be determined when the goods issue is posted.The batches must be entered in the order before it is released.The batches must be entered in the order before the goods issue is posted, but not necessarily before the order is released.If you use pick parts, the batches are determined in the transfer order and then confirmed to the order. If there is no direct link between the transfer order and the production order/process order (for example, with release order parts or crate parts), you must enter the batches in the production order/process order manually.The batches are determined automatically when the order is released.
    
    Returns:
    
    Defines when batches have to be determined when using the PP/WM interface.
  - getBatch_mgmt
```
@Nullable
public Boolean getBatch_mgmt()
```
    Constraints: none
    Original property from the Odata EDM: batch_mgmt
    
    Returns:
    
    Indicator that specifies that the material is managed in batches.
  - getBill_of_material
```
@Nullable
public String getBill_of_material()
```
    Constraints: Not nullable, Maximum length: 8
    Original property from the Odata EDM: bill_of_material
    
    The system assigns this number internally. These numbers are irrelevant to the user. You access the BOM by entering the object (for example, material or equipment) to which the BOM belongs.The system stores the following information under this number:all alternatives in a multiple BOMall variants in a variant BOMBOMs that are allocated to more than one plant
    
    Returns:
    
    Number used in combination with the BOM category to uniquely identify a BOM or a BOM group.
  - getBill_of_material_base_quant
```
@Nullable
public BigDecimal getBill_of_material_base_quant()
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    Original property from the Odata EDM: bill_of_material_base_quant
    
    You normally enter the quantity without a +/- sign (e.g. 66).For the following materials, you enter the quantity with a negative sign (e.g. 22-):Materials that are flagged as co-productsIntra materials (Process industries)When the display function is called, the system calculates the component quantity dependent in the input quantity and the base quantity.Input quantityCurrent component quantity = ------------------ * Saved component quantityBase quantity
    
    Returns:
    
    Quantity of the component that is entered with reference to the base quantity of the product.
  - getBill_of_material_component
```
@Nullable
public String getBill_of_material_component()
```
    Constraints: Not nullable, Maximum length: 40
    Original property from the Odata EDM: bill_of_material_component
    
    A master record is usually maintained in the system for a component.
    
    Returns:
    
    Material number of the components that you enter, change or display as part of the BOM.
  - getBill_of_material_comp_quant
```
@Nullable
public BigDecimal getBill_of_material_comp_quant()
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    Original property from the Odata EDM: bill_of_material_comp_quant
    
    The quantity is usually entered without a +/- sign (e.g. 66).For the following materials, you enter the quantity with a negative sign (e.g. 22-):Materials that are flagged as co-productsIntra materials (Process industries)When the display function is called, the system calculates the current component quantity dependent on the input unit of measure and the base unit of measure.Input unit of measureCurrent component quantity = ------------------ * Saved component quantityBase quantity
    
    Returns:
    
    Quantity in the component, that is entered with reference to the base quantity in the product.
  - getBill_of_material_item_category
```
@Nullable
public String getBill_of_material_item_category()
```
    Constraints: Not nullable, Maximum length: 1
    Original property from the Odata EDM: bill_of_material_item_category
    
    This categorization allows you to process data that is relevant to the individual items in a BOM. The item category is used to control field selection, default values for BOM maintenance, triggering of specific system activities, and so on.Stock itemThis item category is used to manage material data that allows an item to be kept in stock.Document itemThis item category is used to manage document data that allows you to process original application data (for example, graphics created with a graphics program).Class item (for configurable BOMs)In configurable material BOMs, you can enter a class as a placeholder for selectable items. The class can contain either materials or documents.When you assign characteristic values while configuring the BOM, the system replaces the node with an object that has the same values as those assigned to the characteristic of the configuration. This makes BOMs with a larger number of variants easier to maintain, as you do not have to enter all items manually and assign a selection condition to them.Class items can be relevant to MRP.PM structure elementThis item is used to structure an equipment (PM assembly) for design purposes only.If you want to maintain a material for use as a PM structure element, use material type IBAU.
    
    Returns:
    
    Categorization of the items in a BOM according to set criteria, such as whether they refer to an object (for example, material master or document info record) or whether they are kept in stock.
  - getBill_of_material_item_number
```
@Nullable
public String getBill_of_material_item_number()
```
    Constraints: Not nullable, Maximum length: 4
    Original property from the Odata EDM: bill_of_material_item_number
    
    Returns:
    
    This number refers to the sequence of BOM components.
  - getBill_of_material_item_quantity
```
@Nullable
public BigDecimal getBill_of_material_item_quantity()
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    Original property from the Odata EDM: bill_of_material_item_quantity
    
    You usually enter the quantity without a +/- sign (for example, 66).For the following materials, you enter the quantity with a - sign(for example, 22-):Materials that are marked as co-productsIntra materials (in process industries)In display functions, the system calculates the current component quantity from the required quantity and the base quantity.Required quantityCurrent component quantity = ------------------ * Saved component quantityBase quantity
    
    Returns:
    
    Quantity of the component, which is entered in relation to the base quantity of the product.
  - getBill_of_material_item_unit
```
@Nullable
public String getBill_of_material_item_unit()
```
    Constraints: Not nullable, Maximum length: 3
    Original property from the Odata EDM: bill_of_material_item_unit
    
    You define the base unit of measure and also alternative units of measure and their conversion factors in the material master record.Since all data is updated in the base unit of measure, your entry is particularly important for the conversion of alternative units of measure. A quantity in the alternative unit of measure can only be shown precisely if its value can be shown with the decimal places available. To ensure this, please note the following:The base unit of measure is the unit satisfying the highest necessary requirement for precision.The conversion of alternative units of measure to the base unit should result in simple decimal fractions (not, for example, 1/3 = 0.333...).Inventory ManagementIn Inventory Management, the base unit of measure is the same as the stockkeeping unit.ServicesServices have units of measure of their own, including the following:Service unitUnit of measure at the higher item level. The precise quantities of the individual services are each at the detailed service line level.BlanketUnit of measure at service line level for services to be provided once only, and for which no precise quantities can or are to be specified.
    
    Returns:
    
    Unit of measure in which stocks of the material are managed. The system converts all the quantities you enter in other units of measure (alternative units of measure) to the base unit of measure.
  - getBill_Of_Material_Root
```
@Nullable
public String getBill_Of_Material_Root()
```
    Constraints: Not nullable, Maximum length: 8
    Original property from the Odata EDM: Bill_Of_Material_Root
    
    The system assigns this number internally. These numbers are irrelevant to the user. You access the BOM by entering the object (for example, material or equipment) to which the BOM belongs.The system stores the following information under this number:all alternatives in a multiple BOMall variants in a variant BOMBOMs that are allocated to more than one plant
    
    Returns:
    
    Number used in combination with the BOM category to uniquely identify a BOM or a BOM group.
  - getBill_of_material_root_variant
```
@Nullable
public String getBill_of_material_root_variant()
```
    Constraints: Not nullable, Maximum length: 2
    Original property from the Odata EDM: bill_of_material_root_variant
    
    Returns:
    
    Alternative BOM
  - getBill_of_material_variant
```
@Nullable
public String getBill_of_material_variant()
```
    Constraints: Not nullable, Maximum length: 2
    Original property from the Odata EDM: bill_of_material_variant
    
    Returns:
    
    Alternative BOM
  - getBill_of_material_variant_usage
```
@Nullable
public String getBill_of_material_variant_usage()
```
    Constraints: Not nullable, Maximum length: 1
    Original property from the Odata EDM: bill_of_material_variant_usage
    
    Returns:
    
    BOM usage
  - getBom_change_number
```
@Nullable
public String getBom_change_number()
```
    Constraints: Not nullable, Maximum length: 12
    Original property from the Odata EDM: bom_change_number
    
    If you make a change with reference to a change number, or create anobject with a change number, the following functions are at your disposal:The system determines the effectivity parametersThe conditions that the change is effective under can be defined in the change master record as follows:Changes with a date effectivity (valid from date)Changes with parameter effectivity (for example: serial no. effectivity)Log of the changes madeDocumentation for the changesRevision level to indicate the change status of a material or documentChanges released for the different areas in the company.
    
    Returns:
    
    Number used to uniquely identify a change master record.
  - getBulk_material
```
@Nullable
public Boolean getBulk_material()
```
    Constraints: none
    Original property from the Odata EDM: bulk_material
    
    The dependent requirements of bulk materials are not relevant to materials planning. This means they are not taken into account for net requirements calculation. Therefore planning for bulk materials should be consumption-based.If bulk materials are subject to material requirements planning, you must create planned independent requirements for them.Dependent requirements are only created in the planned order for information purposes and they can be displayed there. Dependent requirements for bulk material are not shown in the MRP list or the stock/req. list.You can maintain this indicator in both the material master record an the BOM item. The indicator in the material master record has higher priority.If a material is always used as a bulk material, set the indicator in the material master record.In this case, the Bulk material indicator in material master record is automatically set in the BOM item.If a material is only used as a bulk material in individual cases, set the indicator in the BOM item.To improve system performance, you can define in the IMG for MRP that no dependent requirements are to be created for bulk material items. However, this also means that you see no information on bulk material components in the planned order or production order.
    
    Returns:
    
    This indicator defines a BOM item as a bulk material, which is available directly at the work center (for example, washers or grease).
  - getB_o_m_alternative_text
```
@Nullable
public String getB_o_m_alternative_text()
```
    Constraints: Not nullable, Maximum length: 40
    Original property from the Odata EDM: b_o_m_alternative_text
    
    This information only applies to this individual alternative and variant.If you want to maintain a long text, choose the symbol to the right of the field. The system displays a different symbol for each situation:@0O@ Create long text@0Q@ Change long text@0P@ Display long text
    
    Returns:
    
    This text describes an alternative and a variant.
  - getB_o_m_alt_nxt_lvl
```
@Nullable
public String getB_o_m_alt_nxt_lvl()
```
    Constraints: Not nullable, Maximum length: 2
    Original property from the Odata EDM: b_o_m_alt_nxt_lvl
    
    Returns:
    
    BOM Alternative (Next Level)
  - getB_o_m_category
```
@Nullable
public String getB_o_m_category()
```
    Constraints: Not nullable, Maximum length: 1
    Original property from the Odata EDM: b_o_m_category
    
    Material BOM - linked to a materialEquipment BOM - linked to an equipmentOrder BOM - linked to material, sales order and sales order item.
    
    Returns:
    
    This key defines a BOM according to the object (such as material or equipment) to which it is linked.
  - getB_o_m_cat_nxt_lvl
```
@Nullable
public String getB_o_m_cat_nxt_lvl()
```
    Constraints: Not nullable, Maximum length: 1
    Original property from the Odata EDM: b_o_m_cat_nxt_lvl
    
    Material BOM - Reference to materialEquipment BOM - Reference to equipmentOrder BOM - Reference to material, sales order, and sales order item
    
    Returns:
    
    Key that differentiates BOMs with regard to the object reference (for example, material or equipment).
  - getB_o_m_component_description
```
@Nullable
public String getB_o_m_component_description()
```
    Constraints: Not nullable, Maximum length: 40
    Original property from the Odata EDM: b_o_m_component_description
    
    Returns:
    
    Object description (item)
  - getB_o_m_explosion_level
```
@Nullable
public BigDecimal getB_o_m_explosion_level()
```
    Constraints: Not nullable, Precision: 2, Scale: 0
    Original property from the Odata EDM: b_o_m_explosion_level
    
    The BOM level and the path together identify the exact position of a phantom assembly in a BOM.A BOM contains the following phantom assemblies (Phan.Ass.) and materials:Material A___________________________________________Phan.Ass. B Phan.Ass. C Material D_____________ ___________Phan.Ass. E Mat. F Mat. G Mat. HMat. JTo enable the user to trace the positions of phantom assemblies in the BOM, the BOM levels and paths are assigned according to the following logic:Each BOM level is assigned a numberEach path in the BOM is assinged a numberIn the following BOM, the first number indicates the BOPM level, and the second indicates the path. Materials that are not phantom assemblies are assigned level and path number 0. However, if a material is a component of a phantom assembly, it inherits the level and path numbers from the phantom assembly.Material A(0/0)___________________________________________Phan.Ass. B Phan.Ass. C Material D(1/1) (1/2) (0/0)_____________ ___________Phan.Ass. E Mat. F Mat. G Mat. H(2/1) (1/1) (1/2) (1/2)Mat. J(2/1)
    
    Returns:
    
    The BOM level and the path are only relevant for planning with phantom assemblies.
  - getB_o_m_hdr_matl_hier_node
```
@Nullable
public String getB_o_m_hdr_matl_hier_node()
```
    Constraints: Not nullable, Maximum length: 40
    Original property from the Odata EDM: b_o_m_hdr_matl_hier_node
    
    Returns:
    
    Alphanumeric key uniquely identifying the material.
  - getB_O_M_Hdr_Root_Matl_Hier_Node
```
@Nullable
public String getB_O_M_Hdr_Root_Matl_Hier_Node()
```
    Constraints: Not nullable, Maximum length: 40
    Original property from the Odata EDM: B_O_M_Hdr_Root_Matl_Hier_Node
    
    Returns:
    
    Alphanumeric key uniquely identifying the material.
  - getB_o_m_header_base_unit
```
@Nullable
public String getB_o_m_header_base_unit()
```
    Constraints: Not nullable, Maximum length: 3
    Original property from the Odata EDM: b_o_m_header_base_unit
    
    The system takes this unit from the material master.The unit cannot be changed, because stock of the material is managed using this unit.
    
    Returns:
    
    Unit of measure in which the base quantity of a product or assembly is entered. It is used as the base unit for all component quantities in this BOM.
  - getB_o_m_header_quantity_primary
```
@Nullable
public BigDecimal getB_o_m_header_quantity_primary()
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    Original property from the Odata EDM: b_o_m_header_quantity_primary
    
    Using this customizing function, you can define a value which is set as a default when you create a bill of material.
    
    Returns:
    
    Quantity to which all component quantities in a BOM relate.
  - getB_o_m_item_description
```
@Nullable
public String getB_o_m_item_description()
```
    Constraints: Not nullable, Maximum length: 40
    Original property from the Odata EDM: b_o_m_item_description
    
    If this text length (two lines of 40 characters each) is not sufficient, you can also enter a long text by choosing menu option Extras -> Long text -> Item.When you create an item long text, the first 80 characters of the BOM item text are copied to the long text.If you change the BOM item text, the first 80 characters of long text are automatically changed, too. If you change the first two lines of the BOM item long text, the short text is automatically changed.Note:For text items, this text is copied to the component description field on the item overview.
    
    Returns:
    
    Text of up to 40 characters, which forms the first of two lines of text describing the item.
  - getB_o_m_item_is_discontinued
```
@Nullable
public String getB_o_m_item_is_discontinued()
```
    Constraints: Not nullable, Maximum length: 1
    Original property from the Odata EDM: b_o_m_item_is_discontinued
    
    If this indicator is set, the system transfers the dependent requirements in materials planning to the follow-up material if they are no longer covered by warehouse stocks. However, this requires:The part to be discontinued and the follow-up material to be planned using material requirements planning (MRP)The base unit of measure of the follow-up material to be the same as that of the part to be discontinuedNoteIn subcontracting, uncovered requirements are not switched to the follow-up material after the effective-out date. This is indicated by a corresponding exception message (58) in the MRP list.
    
    Returns:
    
    Identifies the material as a part to be discontinued and includes it in the discontinued parts procedure in materials planning.
  - getB_o_m_no_nxt_lvl
```
@Nullable
public String getB_o_m_no_nxt_lvl()
```
    Constraints: Not nullable, Maximum length: 8
    Original property from the Odata EDM: b_o_m_no_nxt_lvl
    
    The system performs number assignment internally, and is not relevant for the user. The user works with the corresponding BOMs by entering an object (e.g. material, equipment) to which the BOM belongs.The system uses this number to save:All alternatives for a multiple BOMAll variants for a variant BOMBOMs that are assigned to more than one plant
    
    Returns:
    
    Number that, alongside the BOM category, uniquely identifies a bill of material and/or a BOM group.
  - getB_o_m_usage_nxt_lvl
```
@Nullable
public String getB_o_m_usage_nxt_lvl()
```
    Constraints: Not nullable, Maximum length: 1
    Original property from the Odata EDM: b_o_m_usage_nxt_lvl
    
    By selecting different indicators, you specify the maximum value of the item status and control whether the item must/can be processed in the specific area (for example, production), or whether processing is allowed at all.You can maintain separate BOMs containing different items for a material in the company areas Production and Pricing:Production bill of material:The BOM creates items that are relevant for production. These items are copied into the planned order. The dependent requirement is determined and is also copied to the production order during conversion. Production is triggered using the production order with the production of the material.Pricing bill of material:The BOM creates items that are relevant for determining material input costs for a product.If, for example, you create a pricing with a quantity structure, the BOM and all items relevant for determining the production costs are determined automatically.
    
    Returns:
    
    Key that defines the areas (for example, production) where the bill of material can be used.
  - getChange_number
```
@Nullable
public String getChange_number()
```
    Constraints: Not nullable, Maximum length: 12
    Original property from the Odata EDM: change_number
    
    If you make a change with reference to a change number, or create anobject with a change number, the following functions are at your disposal:The system determines the effectivity parametersThe conditions that the change is effective under can be defined in the change master record as follows:Changes with a date effectivity (valid from date)Changes with parameter effectivity (for example: serial no. effectivity)Log of the changes madeDocumentation for the changesRevision level to indicate the change status of a material or documentChanges released for the different areas in the company.
    
    Returns:
    
    Number used to uniquely identify a change master record.
  - getChg_to_eng_chg_number
```
@Nullable
public String getChg_to_eng_chg_number()
```
    Constraints: Not nullable, Maximum length: 12
    Original property from the Odata EDM: chg_to_eng_chg_number
    
    If the object has been changed using a change number, the system determines this change number automatically.Three change numbers (N1, N2 and N3) define the validity periods of the item:N1 N2 N3I-----------I----------------------I---------------->1.1.96 6.1.96 12.2.96If you change the item within the validity period of change number N1, the system enters N2 in Change number to.If you change the item within the validity period of change number N2, the system enters N3 in Change number to.
    
    Returns:
    
    Number used to identify the change master, which will determine the subsequent validity period of the object (material, for example).
  - getClassProperty
```
@Nullable
public String getClassProperty()
```
    Constraints: Not nullable, Maximum length: 18
    Original property from the Odata EDM: class
    
    Returns:
    
    Name used to uniquely identify a class within a class type.
  - getClassification
```
@Nullable
public String getClassification()
```
    Constraints: Not nullable, Maximum length: 8
    Original property from the Odata EDM: classification
    
    Returns:
    
    Classification number
  - getClass_type
```
@Nullable
public String getClass_type()
```
    Constraints: Not nullable, Maximum length: 3
    Original property from the Odata EDM: class_type
    
    Returns:
    
    Uniquely identifies the class type
  - getCommodity_code
```
@Nullable
public String getCommodity_code()
```
    Constraints: Not nullable, Maximum length: 17
    Original property from the Odata EDM: commodity_code
    
    The Harmonized System contains code numbers for all goods that an be transported across national or regional boundaries. Goods are coded according to this nomenclature when declaring the import or export of goods to the proper authorities. The specification of standard commodity codes in declarations enables the authority to tally the quantities of imported or exported goods of specific goods categories for statistical purposes (INTRASTAT).
    
    Returns:
    
    Official code number based on the Harmonized Commodity Description and Coding System (HS).
  - getComp_maint_status
```
@Nullable
public String getComp_maint_status()
```
    Constraints: Not nullable, Maximum length: 15
    Original property from the Odata EDM: comp_maint_status
    
    Returns:
    
    Maintenance status of complete material
  - getComp_scrap_itm
```
@Nullable
public BigDecimal getComp_scrap_itm()
```
    Constraints: Not nullable, Precision: 5, Scale: 2
    Original property from the Odata EDM: comp_scrap_itm
    
    The assembly scrap is used in materials planning to calculate the lot size of the assembly. The system increases the quantity to be produced by the scrap quantity calculated.If the material is an assembly, specify the percentage scrap as required.If the quantity to be produced is 200 pieces and you specify an assembly scrap of 10%, you are reckoning with a scrap quantity of 20 pieces. As a result, 220 pieces are produced.The system increases the quantity to be produced for all of the assembly's components accordingly.
    
    Returns:
    
    Percentage scrap that occurs during production of the material if the material is an assembly.
  - getComp_scrap_itm_mat
```
@Nullable
public BigDecimal getComp_scrap_itm_mat()
```
    Constraints: Not nullable, Precision: 5, Scale: 2
    Original property from the Odata EDM: comp_scrap_itm_mat
    
    The component scrap is used in material requirements planning to determine the input quantities of the components. When the BOMs are exploded, the system increases these input quantities of the components by the calculated scrap quantity.ExampleInput quantity 200 piecesComponent scrap 10 %Scrap quantity 20 pieces---> 220 pieces are usedYou can find examples for the calculation in relation to the indicator for net scrap in the section net scrap.If an assembly scrap is valid for a superordinate assembly, the system adds both scrap types together.If you have entered component scrap in the bill of material, the value in the latter is valid. In other cases, the value in the material master record is valid.
    
    Returns:
    
    Entry in percent that arises during production of the material, when the material is a component.
  - getConfig_mat_var
```
@Nullable
public String getConfig_mat_var()
```
    Constraints: Not nullable, Maximum length: 18
    Original property from the Odata EDM: config_mat_var
    
    Behind this object number lies the assignment of a variant to the valuation of the generally configurable material.The valuation is as follows:Gen.config.material BicycleVariant Blue bicycleChar.value BlueThe system internally saves, for example, the number 20. Behind this number is the characteristic value "blue" and the variant "blue bicycle" .
    
    Returns:
    
    Sequential number used to assign any objects in a class type.
  - getConfig_multi_level
```
@Nullable
public Boolean getConfig_multi_level()
```
    Constraints: none
    Original property from the Odata EDM: config_multi_level
    
    Returns:
    
    Configured on multiple levels
  - getConf_bom_nxt_lvl
```
@Nullable
public Boolean getConf_bom_nxt_lvl()
```
    Constraints: none
    Original property from the Odata EDM: conf_bom_nxt_lvl
    
    Combinable assembliesare used during sales variant processingcontain selectable parts that can be used alongside the non-variable parts in the variant to be produced.
    
    Returns:
    
    Indicator that controls that combinable assemblies (assemblies with variable composition) are permitted.
  - getCost_element
```
@Nullable
public String getCost_element()
```
    Constraints: Not nullable, Maximum length: 10
    Original property from the Odata EDM: cost_element
    
    which is to be debited with the goods issue, if you have entered a consumption account, orfor which an account assignment check is to be carried out.This entry is used in various areas:in MRP for purchase requisitionsin costing for pricingYou can only enter a G/L account for which a G/L account master is maintained in the appropriate company code.
    
    Returns:
    
    Number of the G/L account
  - getCounter
```
@Nullable
public String getCounter()
```
    Constraints: Not nullable, Maximum length: 8
    Original property from the Odata EDM: counter
    
    Returns:
    
    Identifies the activity posting.
  - getCo_product
```
@Nullable
public Boolean getCo_product()
```
    Constraints: none
    Original property from the Odata EDM: co_product
    
    Enter a negative quantity.Example: 6- You can only enter an item as a co-product if:The material master (MRP 2 view) contains the Material can be a co-product indicator. (For some material types, such as raw materials for example, the co-product indicator is hidden in the standard SAP system.)You enter the item as a stock item
    
    Returns:
    
    Indicator showing that the item is a co-product.
  - getCreated_by_user
```
@Nullable
public String getCreated_by_user()
```
    Constraints: Not nullable, Maximum length: 12
    Original property from the Odata EDM: created_by_user
    
    Returns:
    
    Name of user who created the record.
  - getCurrency
```
@Nullable
public String getCurrency()
```
    Constraints: Not nullable, Maximum length: 5
    Original property from the Odata EDM: currency
    
    Returns:
    
    Currency key for amounts in the system.
  - getCustoms_preference
```
@Nullable
public String getCustoms_preference()
```
    Constraints: Not nullable, Maximum length: 1
    Original property from the Odata EDM: customs_preference
    
    A preference agreement allows countries which do not belong to the same trading area to offer each other more favorable customs duties.
    
    Returns:
    
    Set the indicator if the material is entitled to preferential treatment under the terms of a trade agreement between countries.
  - getDat_hist_nxt_lvl
```
@Nullable
public Boolean getDat_hist_nxt_lvl()
```
    Constraints: none
    Original property from the Odata EDM: dat_hist_nxt_lvl
    
    Returns:
    
    Label that shows the BOM and/or BOM group has been historically (this means, by entering a change number) created and/or changed. This change number is only valid for a certain amount of time.
  - getDeletion_indicator
```
@Nullable
public Boolean getDeletion_indicator()
```
    Constraints: none
    Original property from the Odata EDM: deletion_indicator
    
    This indicator is relevant for changes that were made with reference to a change number, and where the effectivity has been defined using a new effectivity type.
    
    Returns:
    
    Indicator shows that the BOM header or the BOM item with reference to the change number has been deleted.
  - getDelivery_time_in_days
```
@Nullable
public BigDecimal getDelivery_time_in_days()
```
    Constraints: Not nullable, Precision: 3, Scale: 0
    Original property from the Odata EDM: delivery_time_in_days
    
    When an order-specific BOM is exploded, a purchase requisition is produced via an MRP program.
    
    Returns:
    
    Gives the delivery time for the material in days.
  - getDel_Ind_nxt_lvl
```
@Nullable
public Boolean getDel_Ind_nxt_lvl()
```
    Constraints: none
    Original property from the Odata EDM: del_Ind_nxt_lvl
    
    This indicator is relevant for changes that were made with reference to a change number, and where the effectivity has been defined using a new effectivity type.
    
    Returns:
    
    Indicator shows that the BOM header or the BOM items with reference to the change number have been deleted.
  - getDenominator
```
@Nullable
public BigDecimal getDenominator()
```
    Constraints: Not nullable, Precision: 5, Scale: 0
    Original property from the Odata EDM: denominator
    
    To convert a quantity, whose unit of measure is not the same as the base unit of measure, into the base unit of measure, the system requires a quotient:Quantity (in alternative unit of measure) = quotient * quantity (in base unit of measure)Enter the number of units of the alternative unit of measure (denominator) that corresponds to the number of units of the base unit of measure (numerator).The alternative unit of measure is kilogram (kg). The base unit of measure is piece (PC). 5 kg correspond to 3 pieces.5 kg = 3 PC => 1 kg = 3/5 PCIn this case, the quotient is therefore 3/5 (the numerator being 3 and the denominator 5).You may enter only whole numbers in the numerator and denominator fields; that is, if 3.14 m² correspond to one piece, you must enter integer multiples (314 m² = 100 PC). In this case, the quotient is therefore 100/314 (the numerator being 100 and the denominator 314).
    
    Returns:
    
    Denominator of the quotient that specifies the ratio of the alternative unit of measure to the base unit of measure.
  - getDiscont_group
```
@Nullable
public String getDiscont_group()
```
    Constraints: Not nullable, Maximum length: 2
    Original property from the Odata EDM: discont_group
    
    You can control the discontinuation as follows:Simple discontinuationAn item that is to be discontinued is replaced by a an item that is is to be introduced to the BOM.Settings in the material master record (materials planning):The discontinuation indicator value 1 is set in the material master record of the item to be discontinued.Settings in the BOM:The follow-up group of the item to be introduced and the discontinuation group of the item to be discontinued must have the same value.Dependent parallel discontinuationOne group of materials is replaced by another group. If an item is to be discontinued (main item), another item (dependent item) is also discontinued.Settings in the material master record (materials planning):Material of the main item to be discontinued: value 1Material of the dependent item: value 3Settings in the BOM:Both the main item and the dependent parallel item to be discontinued are identified by the same discontinuation group.Both the follow-up group of the items to be introduced and the discontinuation group of the items to be discontinued must have the same value.You can only enter a discontinuation group for an item if the discontinuation indicator (material master, MRP 4 view) supports discontinuation.A discontinued item is replaced by a follow-up item. In the follow-up item, you maintain a follow-up group.Example for a simple discontinuationItem 0010 (material M-1) is to be discontinued and replaced by follow-up item 0010 (material M-2).Discontinuation indicator in the material master record M-1: value 1Item Mat. DisconGrp FollGrp 0010 M-1 A1 -0010 M-2 - A1Example for a Parallel discontinuationItems 0010 (material M-1) and 0011 (material M-2) to be discontinued are replaced by items 0010 (material M-3) and 0011 (material M-4) to be introduced.Discontinuation indicator in the material master record:M-1: value 1 (main discontinued item)M-2: value 3 (dependent discontinued item)Item Mat. Discontinuation group Follow-up group0010 M-1 ,A1 -0011 M-2 ,A1 -0010 M-3 - A10011 M-4 - A1Abbreviations:Item. ItemMat. MaterialDisconGrp Discontinuation groupFollGrp. Follow-up group
    
    Returns:
    
    This freely-definable character string is used to group together related items to be discontinued in a BOM.
  - getDistribution_key
```
@Nullable
public String getDistribution_key()
```
    Constraints: Not nullable, Maximum length: 4
    Original property from the Odata EDM: distribution_key
    
    This means that the MRP controller can plan a daily supply of partial quantities (distributed over the validity period of the RS header) for repetitive manufacturing.
    
    Returns:
    
    Determines the split to be used for distributing the run schedule quantity (into partial quantities) over the validity period of the planned order or the production order. In so doing, the relationship between time and the consumption of components is established.
  - getDoc
```
@Nullable
public String getDoc()
```
    Constraints: Not nullable, Maximum length: 22
    Original property from the Odata EDM: doc
    
    Together with the document version, the document number is used as information for technical services. It is displayed in various lists.
    
    Returns:
    
    Number of the drawing that exists for this object.
  - getDocument_part
```
@Nullable
public String getDocument_part()
```
    Constraints: Not nullable, Maximum length: 3
    Original property from the Odata EDM: document_part
    
    Design departments, for example, can use document parts to divide up large documents such as design drawings into pages.
    
    Returns:
    
    Section of a document which is maintained as an independent document.
  - getDocument_type
```
@Nullable
public String getDocument_type()
```
    Constraints: Not nullable, Maximum length: 3
    Original property from the Odata EDM: document_type
    
    Returns:
    
    Part of the document key, which categorizes documents according to their distinguishing features and the organizational procedures which result from them.
  - getDocument_version
```
@Nullable
public String getDocument_version()
```
    Constraints: Not nullable, Maximum length: 2
    Original property from the Odata EDM: document_version
    
    A new version is assigned after the original files have been edited in the following processing situations:The new processing status varies from the original in a certain way (for example, text change sin a text file).You want the original processing status to remain the same (for example, documentation of project progress).
    
    Returns:
    
    Number which identifies the version of a document.
  - getDoc_number
```
@Nullable
public String getDoc_number()
```
    Constraints: Not nullable, Maximum length: 25
    Original property from the Odata EDM: doc_number
    
    Returns:
    
    This number is the main part of the document key, which is used to identify the document.
  - getDoc_reqd
```
@Nullable
public Boolean getDoc_reqd()
```
    Constraints: none
    Original property from the Odata EDM: doc_reqd
    
    Changes to the inspection lot or usage decision are recorded by change documents and displayed in the change history for these objects.Status changes are recorded in status management and displayed in the status history.
    
    Returns:
    
    Causes changes to inspection lots for this material to be documented by the system.
  - getDoc_status
```
@Nullable
public String getDoc_status()
```
    Constraints: Not nullable, Maximum length: 2
    Original property from the Odata EDM: doc_status
    
    If a status network is defined for the document type you canchoose a status among the entry possibilities which is supported inthe current processing situation when you create orchange.You can find more information with an additional colored release indicator:If the document version is releasedIn which time interval the version is releasedYou define the status network in Customizing work step Define document type level Define document status.
    
    Returns:
    
    This key shows the document status.
  - getDoc_type
```
@Nullable
public String getDoc_type()
```
    Constraints: Not nullable, Maximum length: 3
    Original property from the Odata EDM: doc_type
    
    Together with the document number and the document version, the document type represents the key for document management. It is the main criterion for controlling document management. The document type controls field selection and the available statuses for a document info record.
    
    Returns:
    
    Subdivides the documents into groups that are subject to the same organizational processes.
  - getDoc_version
```
@Nullable
public String getDoc_version()
```
    Constraints: Not nullable, Maximum length: 2
    Original property from the Odata EDM: doc_version
    
    Together with the document number, the document version is used as information for technical services. It is displayed on various lists.
    
    Returns:
    
    Version number of an in-house technical document for this object.
  - getEffective_out_date
```
@Nullable
public LocalDateTime getEffective_out_date()
```
    Constraints: Not nullable, Precision: 0
    Original property from the Odata EDM: effective_out_date
    
    From this date, the system reassigns the dependent requirements that are no longer covered by warehouse stock of the discontinued material to the follow-up material. This is done as part of material requirements planning.Enter a date if you want to plan the discontinuation of a material for the long term.
    
    Returns:
    
    Date from which the stocks of the material are to be used up. As soon as no more stock exists for this material, it is to be replaced by the follow-up material.
  - getEngineering_design
```
@Nullable
public Boolean getEngineering_design()
```
    Constraints: none
    Original property from the Odata EDM: engineering_design
    
    This item status indicator is used to control:Subsequent processing in related application areasSelection of items in the BOM explosionWhether you can set and remove this indicator, or whether the system makes an unchangeable setting, depends on the BOM usage you selected on the initial screen. You can find further information in Customizing for bills of material under General Data -> BOM Usage -> Define BOM usages.
    
    Returns:
    
    Indicates that this item is relevant to the area responsible for producing a functional design for production.
  - getException_bom
```
@Nullable
public String getException_bom()
```
    Constraints: Not nullable, Maximum length: 4
    Original property from the Odata EDM: exception_bom
    
    In the following situations, for example, an assembly is not exploded:REKIrecursiveness recognized by systemNREKrecursiveness allowedNBERauthorization group for component is not covered by user profileCONVA conversion error occurred during quantity calculation, due to a conversion factor between the quantity units that was too high. Therefore, the quantity displayed on the result screen for BOM explosions is not reliable.
    
    Returns:
    
    This character string explains why the system did not explode the assembly.
  - getExplosion_type
```
@Nullable
public String getExplosion_type()
```
    Constraints: Not nullable, Maximum length: 2
    Original property from the Odata EDM: explosion_type
    
    You can define an explosion type that transfers dependent requirements for phantom assemblies.For example, the explosion type is relevant to materials that have the following special procurement types:Phantom assemblyPhantom in planningDirect production (collective order)Direct procurementYou can also define whether the following functions are performed for the item:Long-term planningDeterming individual and collective requirements
    
    Returns:
    
    This is used to control the explosion of an item when determining dependent requirements.
  - getFixed_price_co_prod
```
@Nullable
public Boolean getFixed_price_co_prod()
```
    Constraints: none
    Original property from the Odata EDM: fixed_price_co_prod
    
    A material marked as a fixed price co-product is not costed using a joint production process.If the material is an output material of a process with several co-products, the costs for the fixed price co-product are taken from the process costs using the net realizable-value method.Set this indicator if the material is a co-product, but the costs are not to be determined using an apportionment method; instead, a preset price is to be used for the material.The price for the fixed price co-product is taken from a cost estimate without quantity structure; alternatively, a price from the material master is used.You can only set this indicator if you have also set the co-product indicator for the material.Fixed-price co-products are shown in the itemization as items of category M (not A, as is the case with normal co-products), albeit with negative quantities and values.
    
    Returns:
    
    indicates the material as a fixed price co-product.
  - getFixed_quantity
```
@Nullable
public Boolean getFixed_quantity()
```
    Constraints: none
    Original property from the Odata EDM: fixed_quantity
    
    A fixed quantity is not allowed for the following items:alternative itemco-productIf the component quantity isfixed,The quantity fixed quantity is not in proportion to the assembly being produced or the order quantity.The quantity for provision of material is fixed.not fixed,The quantity is in proportion to the quantity of the assembly being produced or the order quantity.The quantity for provision of material is in proportion to the order quantity.
    
    Returns:
    
    This indicator shows that the component quantity is always the same.
  - getFollow_up_grp
```
@Nullable
public String getFollow_up_grp()
```
    Constraints: Not nullable, Maximum length: 2
    Original property from the Odata EDM: follow_up_grp
    
    You can control the discontinuation in the following way:Simple discontinuationSettings in the material master record (MRP 4 view):The discontinuation indicator value 1 is set In the material master record of the material to be discontinued.Settings in the BOM:The value of the follow-up group of the item to be introduced and the discontinuation group of the item to be discontinued must be the same.Dependent parallel discontinuationOne group of materials is replaced by another group of materials. When an item (main item) is discontinued, another item (dependent item) is also discontinued.Settings in the material master record (materials planning):Material of the main item to be discontinued: discontinuation indicator value 1Material of the dependent item: value 3Settings in the BOM:The main item and the dependent parallel item to be discontinued are identified by the same discontinuation group.The value of the follow-up group of the item to be introduced and the discontinuation group of the item to be discontinued must be the same.You can only maintain an item as a follow-up item when you enter it for the first time. The field value cannot be changed after you have entered and saved the item.The follow-up item(s) that are to replace the item to be discontinued must have the same value in the Discontinuation group field as the item to be discontinued has in the Follow-up group field (see the example below).The follow-up item defined in the BOM overrides any follow-up material defined in the material master record.You can only maintain the follow-up group for one item if:the component is planned to a schedule (for example, a warehouse item)the base unit of measure of the materials is identicalExample of a simple discontinuationfItem 0010 to be discontinued (material M-1) is replaced by item 0010 to be introduced (material M-2).Discontinuation indicator in the material master record M-1: value 1Item Material Discontinuation group Follow-up group0010 M-1 A1 -0010 M-2 - A1Example of a parallel discontinuationthe items 0010 (material M-1) and 0011 (material M-2) are replaced by the items 0010 (material M-3) and 0011 (material M-4) to be ntroduced.Discontinuation indicator in the material master record:M-1: Value 1 (main discontinued item)M-2: Value 3 (dependent discontinued item)Item Material Discontinuation group Follow-up group0010 M-1 A1 -0011 M-2 A1 -0010 M-3 - A10011 M-4 - A1Abbreviations:Item. ItemMat. MaterialDisconGrp Discontinuation groupFollGrp. Follow-up group
    
    Returns:
    
    This is a freely-definable character string which is assigned to linked follow-up items in a bill of material. The follow-up group shows which follow-up item(s) are to replace the item to be discontinued.
  - getFollow_up_item
```
@Nullable
public Boolean getFollow_up_item()
```
    Constraints: none
    Original property from the Odata EDM: follow_up_item
    
    This means that, if dependent requirements for parts to be discontinued are not covered by stocks of the material, the dependent requirements are transferred to this follow-up item.The follow-up item defined in the BOM overrides any follow-up material defined in the material master record.In discontinuation data dataset, you use the follow-up group to define which item this item is to replace.The discontinued item to be replaced by this follow-up item must have the same value in the Discontinuation group field as the follow-up item has in the Follow-up group field (see example).For simple discontinuation, item 0010 (material M-1) is to be discontinued and replaced by follow-up items 0010 (material M-2) and 0011 (material M-3).Item Mat. FollInd. DisconGrp FollGrp 0010 M-1 - - E10010 M-2 X E1 -0011 M-3 X E1 -Abbreviations:Mat. MaterialFollInd. Follow-up indicatorDisconGrp Discontinuation groupFollGrp. Follow-up group
    
    Returns:
    
    This indicator shows that the item is a follow-up item.
  - getFollow_up_product
```
@Nullable
public String getFollow_up_product()
```
    Constraints: Not nullable, Maximum length: 40
    Original property from the Odata EDM: follow_up_product
    
    In the material master record and also in the bill of material (BOM), you can define a follow-up material for a material to be discontinued. The follow-up material defined in the BOM has a higher priority than that in the material master record.You must always specify a follow-up material in the material master record for the system to know a follow-up material if none has been specified in the BOM.Simple discontinuationA component to be discontinued is replaced with a follow-up component at a particular date.In the material master record of the component to be discontinued, you must set discontinuation indicator 1, enter a follow-up component, and specify an effective-out date.Dependent parallel discontinuationA group of materials is replaced with a group of materials; that is, if one component is to be discontinued (the main component), another component must also be discontinued (the subordinate component).In the material master record of the main component to be discontinued, you must set discontinuation indicator 1, enter a follow-up component, and specify an effective-out date. In the material master record of the subordinate component, you must set discontinuation indicator 3.
    
    Returns:
    
    Number of the material that the system uses in materials planning to replace the material to be discontinued once its warehouse stock is depleted.
  - getFormula_key
```
@Nullable
public String getFormula_key()
```
    Constraints: Not nullable, Maximum length: 2
    Original property from the Odata EDM: formula_key
    
    You want to calculate the volume of a rolled sheet of metal. This has a variable length and height, but a constant width (500 MM).The following are used in the calculation:SI units that are defined in CustomizingLength: M (meters)Volume: M3 (cubic meters)In the variable-size item, you only enter the variable values (size 1 and size 2) with a unit of measure that can be derived from the SI unit of the dimension.Example for dimension Length: MM (milllimeters), CM (centimeters), DM (decimeters), and M (meters)The variable-size item formula uses the SI unit, so you must enter the constant width in the formula in the SI unit (meters).Example: ROMS1 * ROMS2 * 0.5 (M)You can enter units of measure for calculating the variable-size item quantity with a formula. The quantity is always calculated in the SI unit of the dimension, such as M3 (cubic meters) for volume.
    
    Returns:
    
    Key that represents the algorithm for calculating the variable-size item quantity.
  - getGoods_receipt_duration_in_days
```
@Nullable
public BigDecimal getGoods_receipt_duration_in_days()
```
    Constraints: Not nullable, Precision: 3, Scale: 0
    Original property from the Odata EDM: goods_receipt_duration_in_days
    
    Returns:
    
    Number of workdays required after receiving the material for inspection and placement into storage.
  - getGoods_recipient
```
@Nullable
public String getGoods_recipient()
```
    Constraints: Not nullable, Maximum length: 12
    Original property from the Odata EDM: goods_recipient
    
    Returns:
    
    Specifies the recipient for whom the material or the service is destined.
  - getHeader_record_id
```
@Nullable
public String getHeader_record_id()
```
    Constraints: Not nullable, Maximum length: 1
    Original property from the Odata EDM: header_record_id
    
    Returns:
    
    Indicator: header info record
  - getHeader_validity_end_date
```
@Nullable
public LocalDateTime getHeader_validity_end_date()
```
    Constraints: Not nullable, Precision: 0
    Original property from the Odata EDM: header_validity_end_date
    
    Returns:
    
    End of validity period of an object (such as material, BOM, or routing) in the SAP System.
  - getHeader_validity_start_date
```
@Nullable
public LocalDateTime getHeader_validity_start_date()
```
    Constraints: Not nullable, Precision: 0
    Original property from the Odata EDM: header_validity_start_date
    
    Returns:
    
    Specifies the start date for the validity period of an object (such as material, BOM, or routing).
  - getHl_configuration
```
@Nullable
public Boolean getHl_configuration()
```
    Constraints: none
    Original property from the Odata EDM: hl_configuration
    
    Returns:
    
    Indicator: this item is relevant to the area which is responsible for shipping the product.
  - getIndividual_coll
```
@Nullable
public String getIndividual_coll()
```
    Constraints: Not nullable, Maximum length: 1
    Original property from the Odata EDM: individual_coll
    
    Individual requirementsRequirement quantities of the dependent material are stated individually.Collective requirementsRequirement quantities of the dependent material are grouped together.You can maintain this indicator in the following places:In the material master recordFor the explosion type of the BOM item (in Customizing for Basic Data in Define Explosion Types)The setting for the explosion type overrides that in the material master record.If the material is assigned to a material type that does not allow quantity-based inventory management in this plant, you can set the indicator to individual requirements only.If the stock is to be managed in sales order stock or project stock, the indicator must be set to one of the following options:Individual and collective requirementsIndividual requirements onlyIf a material managed in project stock is to be procured from another plant using a cross-company-code stock transport order, the indicator must be set to 2 (collective requirements) in the issuing plant because, in this specific context, individual project stock management is not possible in both plants.
    
    Returns:
    
    Indicator determining whether the following requirements are allowed for the dependent requirements of the material:
  - getInternal_obj_no
```
@Nullable
public String getInternal_obj_no()
```
    Constraints: Not nullable, Maximum length: 18
    Original property from the Odata EDM: internal_obj_no
    
    Here, the object number refers to the assignment of a variant to a plant-specific configurable material via the values assigned.The value assignment is as follows:General configurable material Racing bicycleVariant Blue racing bicycleCharacteristic value BlueThe system stores, for example, the number 20 internally. Behind this number lies the characteristic value "blue" for the variant "blue racing bicycle".
    
    Returns:
    
    Consecutive number used to assign objects within a class type.
  - getIntra_material
```
@Nullable
public String getIntra_material()
```
    Constraints: Not nullable, Maximum length: 40
    Original property from the Odata EDM: intra_material
    
    Returns:
    
    Character string used to identify an intra material.
  - getIssuing_plant
```
@Nullable
public String getIssuing_plant()
```
    Constraints: Not nullable, Maximum length: 4
    Original property from the Odata EDM: issuing_plant
    
    This entry is only taken into account for plant maintenance activities in the department responsible for plant maintenance.
    
    Returns:
    
    Area of validity of an item relevant to plant maintenance which is different from the validity area of the BOM (Plant).
  - getIs_b_o_m_item_spare_part
```
@Nullable
public String getIs_b_o_m_item_spare_part()
```
    Constraints: Not nullable, Maximum length: 1
    Original property from the Odata EDM: is_b_o_m_item_spare_part
    
    In a BOM explosion, you can use this indicator to restrict item selection.The indicator does not interrupt the explosion of the BOM to the lowest level. There are two steps to the BOM explosion:First, the system explodes the entire BOM, regardless of the indicators selected to restrict items. You do not see the result of this explosion on the screen.Second, the system reads the indicators selected to restrict items, such as the Spare part indicator.These indicators work as filters. The explosion result, you see on the screen only the items that fulfil the selection criteria. In this case, only the items with the spare part indicator you selected are shown.In the IMG for BOMs, you can group spare parts together according to various points of view - for example, according to different maintenance cycles.Spare part group A contains spare parts that need to be replaced after a machine runtime of 100 hours, whereas spare part group B contains spare parts that only need to be replaced after a machine runtime of 500 hours.
    
    Returns:
    
    This key defines the item as a spare part.
  - getIs_c_a_d
```
@Nullable
public Boolean getIs_c_a_d()
```
    Constraints: none
    Original property from the Odata EDM: is_c_a_d
    
    Returns:
    
    Information: data for the assembly/component was generated in a CAD system and transferred into the SAP system via an interface.
  - getIs_material_provision
```
@Nullable
public String getIs_material_provision()
```
    Constraints: Not nullable, Maximum length: 1
    Original property from the Odata EDM: is_material_provision
    
    In the BOM explosion, you can use this indicator to restrict the items selected.There are two types of material provision:Material provided by a vendorMaterial provided by a customerYou can also use the material provision indicator to identify the subcontracting type for a part. The following indicators are available:Refurbishment material to SC (value S in standard SAP system)Refurbishment material from SC (value X in standard SAP system)Subsequent delivery (value F in standard SAP system)If you do not enter information in this field, the components are provided to the subcontractor as consumable materials (initial value in the standard SAP system).Material provided by a vendorThis indicator controls material requirements planning. Maintain this indicator for BOM components only if the material master record of the header material supports subcontracting (Special procurement field).The special procurement key for subcontracting means that all components of the BOM are provided free of charge to a subcontractor for further processing. The items are copied to a subcontract order.If the item is provided to a vendor, do not enter any material provision indicator.Dependent requirements are generated for this item.If the item is already at a vendor's premises and is not provided by us, do enter an indicator.No dependent requirements are generated for this item.Material provided by a customerThis indicator is not currently active.
    
    Returns:
    
    This key indicates that the item is subject to material provision.
  - getIs_phantom_item
```
@Nullable
public Boolean getIs_phantom_item()
```
    Constraints: none
    Original property from the Odata EDM: is_phantom_item
    
    Returns:
    
    Indicator specifies whether the item in question is a phantom assembly.
  - getIs_software_component
```
@Nullable
public Boolean getIs_software_component()
```
    Constraints: none
    Original property from the Odata EDM: is_software_component
    
    Returns:
    
    Indicator: Software component
  - getItem_category
```
@Nullable
public String getItem_category()
```
    Constraints: Not nullable, Maximum length: 1
    Original property from the Odata EDM: item_category
    
    This categorization allows you to process data that is relevant to the individual items in a BOM. The item category is used to control field selection, default values for BOM maintenance, triggering of specific system activities, and so on.Stock itemThis item category is used to manage material data that allows an item to be kept in stock.Document itemThis item category is used to manage document data that allows you to process original application data (for example, graphics created with a graphics program).Class item (for configurable BOMs)In configurable material BOMs, you can enter a class as a placeholder for selectable items. The class can contain either materials or documents.When you assign characteristic values while configuring the BOM, the system replaces the node with an object that has the same values as those assigned to the characteristic of the configuration. This makes BOMs with a larger number of variants easier to maintain, as you do not have to enter all items manually and assign a selection condition to them.Class items can be relevant to MRP.PM structure elementThis item is used to structure an equipment (PM assembly) for design purposes only.If you want to maintain a material for use as a PM structure element, use material type IBAU.
    
    Returns:
    
    Categorization of the items in a BOM according to set criteria, such as whether they refer to an object (for example, material master or document info record) or whether they are kept in stock.
  - getItem_description_line_2
```
@Nullable
public String getItem_description_line_2()
```
    Constraints: Not nullable, Maximum length: 40
    Original property from the Odata EDM: item_description_line_2
    
    You can also enter a long text by choosing menu option Details --> Long text --> Item long text.If the text comprises less than three lines, it is stored in the BOM item. Otherwise, it is stored as a long text in the text database.
    
    Returns:
    
    Text of up to 40 characters, which forms the second of two lines of text describing the item.
  - getItem_identification
```
@Nullable
public String getItem_identification()
```
    Constraints: Not nullable, Maximum length: 8
    Original property from the Odata EDM: item_identification
    
    Returns:
    
    Alphanumeric character string, with which you uniquely identify a BOM item.
  - getItem_node
```
@Nullable
public String getItem_node()
```
    Constraints: Not nullable, Maximum length: 8
    Original property from the Odata EDM: item_node
    
    Returns:
    
    BOM item node number
  - getItem_sign
```
@Nullable
public Boolean getItem_sign()
```
    Constraints: none
    Original property from the Odata EDM: item_sign
    
    Returns:
    
    +/- sign
  - getLast_changed_by_user
```
@Nullable
public String getLast_changed_by_user()
```
    Constraints: Not nullable, Maximum length: 12
    Original property from the Odata EDM: last_changed_by_user
    
    Returns:
    
    Name of Person who Changed Object
  - getLast_change_date
```
@Nullable
public LocalDateTime getLast_change_date()
```
    Constraints: Not nullable, Precision: 0
    Original property from the Odata EDM: last_change_date
    
    Returns:
    
    Date of Last Change
  - getLead_time_offset
```
@Nullable
public BigDecimal getLead_time_offset()
```
    Constraints: Not nullable, Precision: 3, Scale: 0
    Original property from the Odata EDM: lead_time_offset
    
    This value is not included in lead-time scheduling for a task list.You can enter:A positive number of daysThe component is not required until after the start date.A negative number of daysThe component is required before the start date.Assembly AS-11 (start date 05/13/1998):Component Lead-time offset Finish dateM-01 2+ 05/15/1998M-02 2- 05/11/1998M-03 0 05/13/1998Component M-01 is not required until 2 days after the start date for the superior assembly.Component M-02 is required 2 days before the start date for the superior assembly, so the finish date for this component is 05/11/1998.The lead-time offset for component M-03 is 0, so the start date for the superior assembly is the same as the finish date for this component.Note:This information does not tell you the start date for the components, because the data required (such as in-house production time, processing time, or interoperation time) is not shown.
    
    Returns:
    
    This value shows the lead-time offset (in workdays) for the component in relation to the start date for production of the superior assembly.
  - getLong_text_lang
```
@Nullable
public String getLong_text_lang()
```
    Constraints: Not nullable, Maximum length: 2
    Original property from the Odata EDM: long_text_lang
    
    Returns:
    
    Language: The long text was stored in this language
  - getLow_level_code
```
@Nullable
public String getLow_level_code()
```
    Constraints: Not nullable, Maximum length: 3
    Original property from the Odata EDM: low_level_code
    
    The level that is set in the material master record represents the level at which the material will be planned. This means that the material will only be planned once all assemblies in which it occurs have been planned and exploded.The low-level code is set internally in the material master record when the BOM is maintained.
    
    Returns:
    
    The lowest level that a material appears in any product structure of the company. The low-level code controls the sequence in which the material is planned in an MRP run: First the materials with low-level code 0 are planned, then the materials with low-level code 1, and so on. The lower the low-level code, the higher the number that is assigned to the material.
  - getMaintenance_status
```
@Nullable
public String getMaintenance_status()
```
    Constraints: Not nullable, Maximum length: 15
    Original property from the Odata EDM: maintenance_status
    
    Which user departments may maintain a material master record of a particular material typeWhich user departments have already maintained the material master record at a particular hierarchy levelThe overall maintenance status is made up of the individual maintenance statuses. The individual maintenance statuses have the following meaning:User department Maintenance statusWork scheduling AAccounting BClassification CMRP DPurchasing EProduction resources/tools FCosting GBasic data KStorage LForecasting PQuality management QWarehouse management SSales VPlant stocks XStorage location stocks Z
    
    Returns:
    
    The maintenance status records:
  - getMaterial_component_price
```
@Nullable
public BigDecimal getMaterial_component_price()
```
    Constraints: Not nullable, Precision: 12, Scale: 3
    Original property from the Odata EDM: material_component_price
    
    Returns:
    
    Price for external processing.
  - getMaterial_group
```
@Nullable
public String getMaterial_group()
```
    Constraints: Not nullable, Maximum length: 9
    Original property from the Odata EDM: material_group
    
    You can use material groups to:Restrict the scope of analysesSearch specifically for material master records via search helps
    
    Returns:
    
    Key that you use to group together several materials or services with the same attributes, and to assign them to a particular material group.
  - getMaterial_is_configurable
```
@Nullable
public Boolean getMaterial_is_configurable()
```
    Constraints: none
    Original property from the Odata EDM: material_is_configurable
    
    If this indicator is set, you can assign a variant class to the material, making it possible to use it as a configurable material.You can set the indicator manually in the material master record, irrespective of the material type.
    
    Returns:
    
    Indicator that determines that the material is configurable.
  - getMaterial_Name
```
@Nullable
public String getMaterial_Name()
```
    Constraints: Not nullable, Maximum length: 40
    Original property from the Odata EDM: Material_Name
    
    You can enter one material description in each of any number of languages.In principle, you enter the material description on the data screen of the first user department for which you enter data, and in your logon language. You can overwrite the material description on the Basic Data screen.
    
    Returns:
    
    Text containing up to 40 characters that describes the material in more detail.
  - getMaterial_type
```
@Nullable
public String getMaterial_type()
```
    Constraints: Not nullable, Maximum length: 4
    Original property from the Odata EDM: material_type
    
    The material type defines certain attributes of the material and has important control functions.
    
    Returns:
    
    Key that assigns the material to a group of materials such as raw materials, operating supplies or trading goods.
  - getMat_purity_in_perc
```
@Nullable
public BigDecimal getMat_purity_in_perc()
```
    Constraints: Not nullable, Precision: 5, Scale: 2
    Original property from the Odata EDM: mat_purity_in_perc
    
    Returns:
    
    Average material purity in %
  - getMoving_price
```
@Nullable
public BigDecimal getMoving_price()
```
    Constraints: Not nullable, Precision: 12, Scale: 3
    Original property from the Odata EDM: moving_price
    
    Moving average pricePeriodic unit price (only if the material ledger is activated for the material)The system calculates the moving average price automatically by dividing the material value in the stock account by the total of all storage location stocks in the plant concerned. It changes the price with each valuation-relevant movement.The system changes the periodic unit price if you settle the material ledger and then save the data.The valuation of stocks at moving average price or periodic unit price means that the price of the material is adapted to the continual fluctuations in the procurement price.If the material ledger is activated for the material, the material's settlement control determines whether this price is the moving average price or the periodic unit price.
    
    Returns:
    
    Price of the material. This can be one of the following:
  - getMultiple_sel
```
@Nullable
public Boolean getMultiple_sel()
```
    Constraints: none
    Original property from the Odata EDM: multiple_sel
    
    Returns:
    
    This indicator influences the status of a configuration in cases where a class item has been replaced by more than one object. Only if the configuration scenario allows manual changes to the BOM (order BOM or sales order with manual changes) can a class item be temporarily replaced by more than one object. However, before you save, the selection must be restricted to one object by using a manual object search. If you leave the configuration while the class item is still replaced by more than one object, only the first object is saved or transferred to the calling application. The "Multiple Selection" indicator has the following effect in interactive configuration: the configuration is still consistent if the class item has been replaced by more than one object. Without this indicator, the configuration is inconsistent if the class item has been replaced by more than one object. In low-level configuration (MRP, for example), only one object is used to replace the class, whether or not the "Multiple Selection" indicator is set.
  - getM_r_p_type
```
@Nullable
public String getM_r_p_type()
```
    Constraints: Not nullable, Maximum length: 2
    Original property from the Odata EDM: m_r_p_type
    
    Manual reorder point planningAutomatic reorder point planningForecast-based planningMaterial requirements planning with forecasts for unplanned consumptionMaster production scheduling (MPS)Demand-driven replenishment
    
    Returns:
    
    Key that determines whether and how the material is planned. You have the following options:
  - getNet_scrap_indicator
```
@Nullable
public Boolean getNet_scrap_indicator()
```
    Constraints: none
    Original property from the Odata EDM: net_scrap_indicator
    
    You must set this indicator if you want assembly scrap to be ignored.You must set this indicator if you enter operation scrap.You can set this indicator if you only enter component scrap, to calculate scrap on the basis of the net required quantity for the assembly.Bill of material:Assembly MAT-1:Required quantity 100 piecesAssembly scrap 2%Component MAT-2:Component quantity 100 piecesDepending on the applicable scrap and the net indicator, the following 6 quantities are required for component MAT-2 for a required quantity of 100 pieces of MAT-1:1 2 3 4 5 6 Comp 5% - 5% 5% - -Op. 6% 6% - - - -Net ind X X X - - X---------------------------------------------------------------------Qty 11130 10600 10500 10710 10200 10000KeyComp Component scrapOp. Operation scrapNet ind Net indicatorQty Quantity calculated for component MAT-2 in pieces
    
    Returns:
    
    This indicator determines whether scrap for the component is calculated on the basis of the net required quantity (the required quantity without assembly scrap from the material master record).
  - getNo_cu_instances
```
@Nullable
public String getNo_cu_instances()
```
    Constraints: Not nullable, Maximum length: 6
    Original property from the Odata EDM: no_cu_instances
    
    If a pole always has two cross arms, you set the number of instances for the cross arm to 2.
    
    Returns:
    
    Specifies the number of instances of the compatible unit that are required.
  - getNo_of_sheets
```
@Nullable
public String getNo_of_sheets()
```
    Constraints: Not nullable, Maximum length: 3
    Original property from the Odata EDM: no_of_sheets
    
    Returns:
    
    Number of pages that the technical document contains.
  - getNo_var_size_items
```
@Nullable
public BigDecimal getNo_var_size_items()
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    Original property from the Odata EDM: no_var_size_items
    
    Returns:
    
    Number of variable-size items required for the assembly .
  - getNumerator
```
@Nullable
public BigDecimal getNumerator()
```
    Constraints: Not nullable, Precision: 5, Scale: 0
    Original property from the Odata EDM: numerator
    
    To convert a quantity, whose unit of measure is not the same as the base unit of measure, into the base unit of measure, the system requires a quotient:Quantity (in alternative unit of measure) = quotient * quantity (in base unit of measure)Enter the number of units of the alternative unit of measure (denominator) that corresponds to the number of units of the base unit of measure (numerator).The alternative unit of measure is kilogram (kg). The base unit of measure is piece (PC). 5 kg correspond to 3 pieces.5 kg = 3 PC => 1 kg = 3/5 PCIn this case, the quotient is therefore 3/5 (the numerator being 3 and the denominator 5).You may enter only whole numbers in the numerator and denominator fields; that is, if 3.14 m² correspond to one piece, you must enter integer multiples (314 m² = 100 PC). In this case, the quotient is therefore 100/314 (the numerator being 100 and the denominator 314).
    
    Returns:
    
    Numerator of the quotient that specifies the ratio of the alternative unit of measure to the base unit of measure.
  - getObject_description
```
@Nullable
public String getObject_description()
```
    Constraints: Not nullable, Maximum length: 40
    Original property from the Odata EDM: object_description
    
    Returns:
    
    Object description (assembly)
  - getObject_type
```
@Nullable
public String getObject_type()
```
    Constraints: Not nullable, Maximum length: 1
    Original property from the Odata EDM: object_type
    
    Via settings in Customizing (Bill of mat. -> Item data), you can define a language-dependent abbreviation which the system displays on the General item overview screen.
    
    Returns:
    
    Key which assigns the BOM item to a group of objects which have basic features in common, such as material or document.
  - getObj_dep_assgt_no
```
@Nullable
public String getObj_dep_assgt_no()
```
    Constraints: Not nullable, Maximum length: 18
    Original property from the Odata EDM: obj_dep_assgt_no
    
    Returns:
    
    Number of Object with Assigned Dependencies
  - getOperation_scrap_perc
```
@Nullable
public BigDecimal getOperation_scrap_perc()
```
    Constraints: Not nullable, Precision: 5, Scale: 2
    Original property from the Odata EDM: operation_scrap_perc
    
    This entry is used to override the assembly scrap for materials of high value.If operation scrap is maintained, you avoid the situation whereby too much of the material is planned in MRP for the components of subsequent operations.If you make an entry for operation scrap, you must also select the operation scrap net indicator (Net field).You can find examples of scrap under net scrap.
    
    Returns:
    
    Scrap that is expected in one operation for the quantity of a component to be processed.
  - getOper_lto_unit
```
@Nullable
public String getOper_lto_unit()
```
    Constraints: Not nullable, Maximum length: 3
    Original property from the Odata EDM: oper_lto_unit
    
    Returns:
    
    Unit for lead-time offset for operation
  - getOper_lt_offset
```
@Nullable
public BigDecimal getOper_lt_offset()
```
    Constraints: Not nullable, Precision: 3, Scale: 0
    Original property from the Odata EDM: oper_lt_offset
    
    (In the Project System read activity for operation.)The following areas evaluate the operation related lead-time offset:Plant maintenance ordersNetworksProduction ordersProcess ordersMaintain the following times dependently of the +/- sign:Lead-time offset - positive valueComponent can be available after the operation start dateLead time - negative valueComponent must be available before the operation start dateOperation start date 0010: 05.13.1998, 9 a.m.Operation start date 0020: 05.14.1998, 2 p.m.---------------------------------------------------------Component Operation Lead-time offset (h) End dateM-01 0010 2+ 05.13.1998, 11 a.m.M-02 0020 2- 05.14.1998, 12 a.m.The component M-01 does not have to be available until 2 hours after the start time of the allocated operation 0010.Because the component M-02 must be available 2 hours before the start time of the allocated operation, the end time is 12 a.m.
    
    Returns:
    
    Time that the component lead-time offset states with reference to the start date of the allocated operation.
  - getOrg_area
```
@Nullable
public String getOrg_area()
```
    Constraints: Not nullable, Maximum length: 10
    Original property from the Odata EDM: org_area
    
    On the characteristics screen of the class, you can assign characteristics to the organizational areas you have defined for the class.
    
    Returns:
    
    These organizational areas are allowed for the characteristics of this class.
  - getPage_format
```
@Nullable
public String getPage_format()
```
    Constraints: Not nullable, Maximum length: 4
    Original property from the Odata EDM: page_format
    
    Returns:
    
    Page format of the internal technical document for this object.
  - getPage_number
```
@Nullable
public String getPage_number()
```
    Constraints: Not nullable, Maximum length: 3
    Original property from the Odata EDM: page_number
    
    Returns:
    
    Number of the page in the document on which the material can be found.
  - getPath
```
@Nullable
public BigDecimal getPath()
```
    Constraints: Not nullable, Precision: 4, Scale: 0
    Original property from the Odata EDM: path
    
    Using the route of predecessor and component, you can reconstruct the exact structure of a bill of material.The level and/or the route are only relevant for planning using dummy assemblies.Level and route show you the exact position of a dummy assembly within a bill of material.A BOM contains the following dummy assemblies (DummyAs) and materials:Material A___________________________________________DummyAs B DummyAs C Material D_____________ ___________DummyAs E Mat. F Mat. G Mat. HMat. JIn order to track the position of the assemblies within the BOM structure, the levels and routes are assigned according to the following logic:A level number is assigned for each BOM levelA route number is assigned for each BOM pathIn the following BOM, the first number refers to the level, the second number the route. If the material is not a dummy assembly, the number '0' is assigned as level and/or route. If the material is a component of a dummy assembly however, then the component inherits the level and route from the dummy assembly.Material A(0/0)___________________________________________DummyAs B DummyAs C Material D(1/1) (1/2) (0/0)_____________ ___________DummyAs E Mat. F Mat. G Mat. H(2/1) (1/1) (1/2) (1/2)Mat. J(2/1)
    
    Returns:
    
    Direction for exploding a component.
  - getPath_predecessor
```
@Nullable
public BigDecimal getPath_predecessor()
```
    Constraints: Not nullable, Precision: 4, Scale: 0
    Original property from the Odata EDM: path_predecessor
    
    Using the route of predecessor and component, you can reconstruct the exact structure of a bill of material.The level and/or the route are only relevant for planning using dummy assemblies.Level and route show you the exact position of a dummy assembly within a bill of material.A BOM contains the following dummy assemblies (DummyAs) and materials:Material A___________________________________________DummyAs B DummyAs C Material D_____________ ___________DummyAs E Mat. F Mat. G Mat. HMat. JIn order to track the position of the assemblies within the BOM structure, the levels and routes are assigned according to the following logic:A level number is assigned for each BOM levelA route number is assigned for each BOM pathIn the following BOM, the first number refers to the level, the second number the route. If the material is not a dummy assembly, the number '0' is assigned as level and/or route. If the material is a component of a dummy assembly however, then the component inherits the level and route from the dummy assembly.Material A(0/0)___________________________________________DummyAs B DummyAs C Material D(1/1) (1/2) (0/0)_____________ ___________DummyAs E Mat. F Mat. G Mat. H(2/1) (1/1) (1/2) (1/2)Mat. J(2/1)
    
    Returns:
    
    Direction for exploding a component.
  - getPlant
```
@Nullable
public String getPlant()
```
    Constraints: Not nullable, Maximum length: 4
    Original property from the Odata EDM: plant
    
    Returns:
    
    Key uniquely identifying a plant.
  - getPlant_maintenance
```
@Nullable
public Boolean getPlant_maintenance()
```
    Constraints: none
    Original property from the Odata EDM: plant_maintenance
    
    Items that are relevant to plant maintenance are used in maintenance BOMs (material BOMs that are relevant to plant maintenance, equipment BOMs, and functional location BOMs).This item status indicator is used to control:Subsequent processing in related application areasSelection of items in the BOM explosionWhether you can set and remove this indicator, or whether the system makes an unchangeable setting, depends on the BOM usage you selected on the initial screen. You can find further information in Customizing for bills of material under General Data -> BOM Usage -> Define BOM usages.
    
    Returns:
    
    Indicates that this item is relevant to plant maintainance procedures.
  - getPlant_sp_matl_status
```
@Nullable
public String getPlant_sp_matl_status()
```
    Constraints: Not nullable, Maximum length: 2
    Original property from the Odata EDM: plant_sp_matl_status
    
    Materials management (for example, in purchasing and in inventory management)Production planning and controlPlant maintenanceWarehouse managementCosting with a quantity structureThe plant-specific material status restricts the usability of the material for the plant concerned, that is, it defines whether a warning or error message is displayed if you include the material in a particular function.The material may be a part under development or one to be discontinued.
    
    Returns:
    
    Indicates whether, for a specific plant, the material may be used in the following areas:
  - getPlt_sp_status_valid_from
```
@Nullable
public LocalDateTime getPlt_sp_status_valid_from()
```
    Constraints: Not nullable, Precision: 0
    Original property from the Odata EDM: plt_sp_status_valid_from
    
    The valid-from date of the material status is considered only if it precedes or is the same as the planning date; that is, if the valid-from date is later than the planning date, it is not considered, even if it is within the planning horizon.ExampleI<-------------Planning horizon------------->I-----I--------------------I-----------------------I-->Planning date Valid-from date TimeIn this case, the valid-from date is not considered in materials planning since it is later than the planning date.PurchasingThe valid-from date of the material status is checked against the current date.ExampleYou block the material for purchasing from May 1, xxxx. A purchase order is created for the material on April 28, xxxx with a delivery date of May 10, xxxx. In this case, the valid-from date May 1, xxxx is checked against the purchase order date April 28, xxxx and the purchase order is allowed. Had you created the purchase order on May 3, xxxx, an error message would have been issued.
    
    Returns:
    
    Materials planning
  - getPm_assembly
```
@Nullable
public Boolean getPm_assembly()
```
    Constraints: none
    Original property from the Odata EDM: pm_assembly
    
    You can use this indicator to restrict the selection of items in the BOM explosion. In this case, only the items that are PM assemblies are shown.The indicator does not interrupt the explosion of the BOM to the lowest lever. There are two steps to the BOM explosion:First, the system explodes the entire BOM, regardless of the indicators selected to restrict items. You do not see the result of this explosion on the screen.Second, the system reads the indicators selected to restrict items, such as the PM assembly indicator.These indicators work as filters. The explosion result you see on the screen only includes the items that fulfil the selection criteria.
    
    Returns:
    
    This indicator shows that this item is part of a technical object (assembly) for which maintenance tasks are planned and carried out.
  - getPrice_control
```
@Nullable
public String getPrice_control()
```
    Constraints: Not nullable, Maximum length: 1
    Original property from the Odata EDM: price_control
    
    Standard priceMoving average priceIf the material ledger is activated for the material, this indicator, together with the material's price determination indicator, determines at which of the following prices the material is valuated:Standard priceMoving average pricePeriodic unit price
    
    Returns:
    
    Indicates the price control used to valuate the stock of a material. You have the following options:
  - getPrice_unit
```
@Nullable
public BigDecimal getPrice_unit()
```
    Constraints: Not nullable, Precision: 5, Scale: 0
    Original property from the Odata EDM: price_unit
    
    10 litres of gasoline cost $12. The price unit here is 10.
    
    Returns:
    
    Number of units of measure that refer to the price.
  - getPriority
```
@Nullable
public String getPriority()
```
    Constraints: Not nullable, Maximum length: 2
    Original property from the Odata EDM: priority
    
    With respect to withdrawal postings, the ranking order determines which material components from the alternative item group should be taken into account for the reservation in the production order.Withdrawal according to usage probabilityFor all items that should be reserved, maintain:strategy (value 1 or no entry)ranking order (only effects the material sort)usage probabilityWithdrawal on 100% availabilityFor all items that should be reserved, maintain:ranking orderIf you do not enter the ranking order, the system checks the items in the order that they are transmitted to the availability check.strategy (value 2)usage probabilityThree items (0060 und 0065 and 0070) are assigned to an alternative item group and are given the following values for ranking order:position ranking order0060 30065 20070 1This means that the system reads item 0070 first.
    
    Returns:
    
    Position of an item in an alternative item group.
  - getProcured_externally
```
@Nullable
public Boolean getProcured_externally()
```
    Constraints: none
    Original property from the Odata EDM: procured_externally
    
    Returns:
    
    Indicator: procured externally
  - getProdn_supply_area
```
@Nullable
public String getProdn_supply_area()
```
    Constraints: Not nullable, Maximum length: 10
    Original property from the Odata EDM: prodn_supply_area
    
    The PSA is used in Kanban and JIT Outbound processing and in Extended Warehouse Management.
    
    Returns:
    
    The production supply area (PSA) serves as a place for interim storage on the shop floor and is used to make material directly available for production purposes.
  - getProduction_relevant
```
@Nullable
public Boolean getProduction_relevant()
```
    Constraints: none
    Original property from the Odata EDM: production_relevant
    
    Items with this indicator are copied to the planned order, and the system calculates dependent requirements for them. When the planned order is converted to a production order, the system automatically copies these items to the production order.This item status indicator is used to control:Subsequent processing in related application areasSelection of items in the BOM explosionWhether you can set and remove this indicator, or whether the system makes an unchangeable setting, depends on the BOM usage you selected on the initial screen. You can find further information in Customizing for bills of material under General Data -> BOM Usage -> Define BOM usages.
    
    Returns:
    
    Indicates that the item is relevant to the production process.
  - getProduction_supply_area
```
@Nullable
public String getProduction_supply_area()
```
    Constraints: Not nullable, Maximum length: 10
    Original property from the Odata EDM: production_supply_area
    
    The PSA is used in Kanban and JIT Outbound processing and in Extended Warehouse Management.
    
    Returns:
    
    The production supply area (PSA) serves as a place for interim storage on the shop floor and is used to make material directly available for production purposes.
  - getProduction_version
```
@Nullable
public String getProduction_version()
```
    Constraints: Not nullable, Maximum length: 4
    Original property from the Odata EDM: production_version
    
    The production version determines the following:the BOM alternative for a BOM explosionthe task list type, the task list group and the task list group counter for allocation to task listslot-size restrictions for repetitive manufacturing
    
    Returns:
    
    Key which determines the various production techniques according to which a material can be manufactured.
  - getProd_order_issue_location
```
@Nullable
public String getProd_order_issue_location()
```
    Constraints: Not nullable, Maximum length: 4
    Original property from the Odata EDM: prod_order_issue_location
    
    If the material is a component, it is the issuing storage location to which a backflush is posted.If the material is produced, it is the receiving storage location to which the receipt of the material is posted.
    
    Returns:
    
    In the case of a material produced in-house, this is the key of the storage location that is copied to the planned order, production order, or run schedule quantity.
  - getProfit_center
```
@Nullable
public String getProfit_center()
```
    Constraints: Not nullable, Maximum length: 10
    Original property from the Odata EDM: profit_center
    
    Returns:
    
    Key which together with the controlling area uniquely identifies a profit center.
  - getPurchase_org
```
@Nullable
public String getPurchase_org()
```
    Constraints: Not nullable, Maximum length: 4
    Original property from the Odata EDM: purchase_org
    
    Returns:
    
    Denotes the purchasing organization.
  - getPurchasing_group
```
@Nullable
public String getPurchasing_group()
```
    Constraints: Not nullable, Maximum length: 3
    Original property from the Odata EDM: purchasing_group
    
    Internally, the purchasing group is responsible for the procurement of a material or a class of materials.Externally, it is the medium through which contacts with the vendor are maintained.
    
    Returns:
    
    Key for a buyer or a group of buyers, who is/are responsible for certain purchasing activities.
  - getPurchasing_organisation
```
@Nullable
public String getPurchasing_organisation()
```
    Constraints: Not nullable, Maximum length: 4
    Original property from the Odata EDM: purchasing_organisation
    
    Returns:
    
    Denotes the purchasing organization.
  - getQty_var_size_item
```
@Nullable
public BigDecimal getQty_var_size_item()
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    Original property from the Odata EDM: qty_var_size_item
    
    The quantity of the variable-size item shown is per piece (PC)If you change a field that affects the calculation of the variable-size item quantity (for example, size or formula), the system only recalculates the quantity if you delete the existing quantity first.To do this, delete the contents of the Qty Var-sz item field.Size 1: 200Size 2: 300Size unit of measure: MMVariable size item unit: SQMCalculation of variable-size item quantity:A = Size 1 * Size 2A = 200 MM * 300 MMA = 0,06 SQM--> The variable-size item quantity for each piece is: 0.06 SQMThe value calculated is required in MRP, in order to calculate the total quantity of the raw material requirement for the component.If 10 pieces are required for the component, the variable-size item quantity is: 10 * 0.06 SQM = 0.6 SQM.
    
    Returns:
    
    Quantity of variable-size item, which the system calculates from the sizes entered. If you wish you can enter a variable-size item formula for the. calculation.
  - getRecord_creation_date
```
@Nullable
public LocalDateTime getRecord_creation_date()
```
    Constraints: Not nullable, Precision: 0
    Original property from the Odata EDM: record_creation_date
    
    Returns:
    
    Date on which the record was created.
  - getRecurisve
```
@Nullable
public Boolean getRecurisve()
```
    Constraints: none
    Original property from the Odata EDM: recurisve
    
    In BOM maintenanceyou can switch off the recursiveness check by setting the Recursiveness allowed indicatorrecursiveness is usually recognized online and prevented by an error messagein exceptional circumstances, recursiveness is not recognized until the BOM is updatedIn this case, the system sets the BOM is recursive indicator.Explosion path of BOM M10-----------------> |M10|| -----| / \| ---- ----| M3 M2| ---- ----| / \| ----- ------ |M10| M4----- ----
    
    Returns:
    
    Indicator set by the system if the exploded BOM for an object contains the object itself as an item.
  - getRecurs_allowed
```
@Nullable
public Boolean getRecurs_allowed()
```
    Constraints: none
    Original property from the Odata EDM: recurs_allowed
    
    If you set the Indicator: recursiveness allowed, no recursiveness check is made for the item concerned: you can create a recursive BOM.
    
    Returns:
    
    Indicator: controls whether the system checks the BOM for recursiveness.
  - getReference_point
```
@Nullable
public String getReference_point()
```
    Constraints: Not nullable, Maximum length: 20
    Original property from the Odata EDM: reference_point
    
    Returns:
    
    Creates a logical link between BOM items and network activities.
  - getRelevancy_to_costing
```
@Nullable
public String getRelevancy_to_costing()
```
    Constraints: Not nullable, Maximum length: 1
    Original property from the Odata EDM: relevancy_to_costing
    
    For the Standard Cost Estimate and the calculation of planned costs for a Work Order, this indicator specifies whether the item is included in costing.A BOM item or operation for which the indicator for relevancy to costing is X is fully relevant to costing.A BOM item or operation without an indicator for relevancy to costing is not relevant to costing at all.For Inventory Costing, you can link relevancy to costing indicators to factors for the fixed and variable costs so that the item values can be adjusted in costing depending on the valuation variant. You do this in Customizing for Product Cost Controlling.A BOM item or operation has the indicator for relevancy to costing A, which you have linked in Customizing for Product Cost Controlling to a fixed factor of 0.8 and a variable factor of 0.8. The BOM item or operation is costed in inventory costing at 80% of the fixed costs and 80% of the variable costs.For output materials (that is, materials for which the co-product indicator has been set in the material master and that have a negative BOM item), the relevance to costing indicator has no effect on the BOM item.The BOM usage that you selected on the initial screen determines whether this field is ready for input. For more information, see Customizing under Production -> Basic Data -> Bill of Material -> General Data -> BOM Usage -> Define BOM Usages.
    
    Returns:
    
    Controls the extent to which a BOM item, operation, or suboperation in the routing is included in costing.
  - getRelevant_to_sales
```
@Nullable
public String getRelevant_to_sales()
```
    Constraints: Not nullable, Maximum length: 1
    Original property from the Odata EDM: relevant_to_sales
    
    For example, in sales order processing vor variant products, you see items that are relevant to sales as order items for the header material.This item status indicator is used to control:subsequent processing in related application areaswhich items are selected in the BOM explosionThe indicator does not interrupt the explosion of the BOM to the lowest lever. There are two steps to the BOM explosion:First, the system explodes the entire BOM, regardless of the indicators selected to restrict items. You do not see the result of this explosion on the screen.Second, the system reads the indicators selected to restrict items, such as the Relevant to sales indicator.This status indicator works as a filter. The explosion result you see on the screen only includes the items that fulfil the selection criteria. In this case, only the items that are relevant to sales are shown.
    
    Returns:
    
    This indicator shows that this item is relevant to the sales and distribution area of a company.
  - getRequired_component
```
@Nullable
public Boolean getRequired_component()
```
    Constraints: none
    Original property from the Odata EDM: required_component
    
    Returns:
    
    If this class is used as a class item in a configurable object, this setting has the following effect in interactive configuration: the configuration is incomplete until the class item has been replaced by an object. In low-level configuration (MRP, for example), the "Required component" indicator has no further effects.
  - getRequirement_segment
```
@Nullable
public String getRequirement_segment()
```
    Constraints: Not nullable, Maximum length: 40
    Original property from the Odata EDM: requirement_segment
    
    Customer 1 accepts quality 1 and 2 while customer 2 accepts only quality 1. This results in 2 different requirement segments which can be assigned to different stock segments.
    
    Returns:
    
    Indicates additional information about the type of requirement. You can freely define which requirement segments are satisfied by which stock segments using segmentation strategies in the transaction Segmentation Strategy Maintenance .
  - getRevision_level
```
@Nullable
public String getRevision_level()
```
    Constraints: Not nullable, Maximum length: 2
    Original property from the Odata EDM: revision_level
    
    You can assign a revision level if you use a change number that has a specific valid-from date to make a change.Proceed as follows:Changing a MaterialYou can assign a revision level to a material when you process the material master record itself, or you can enter a revision level in the BOM header when you process a material BOM.Changing a DocumentYou define for each document type whether revision levels are active for documents. Define a document status that has the released indicator. As soon as you process a document of this document type with a change number and assign this status, a revision level is assigned automatically.Before you can assign a revision level, you must define the revisionlevel. From the main R/3 menu, choose Logistics -> Central functions -> Engineering change management, then Revision level -> Material rev. level or Revision level -> Document rev. level.To define how revision levels are assigned, go to Customizing step Set up control data.
    
    Returns:
    
    A revision level, together with a change number, identifies a version of a material or document.
  - getScrap_qty_bun
```
@Nullable
public BigDecimal getScrap_qty_bun()
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    Original property from the Odata EDM: scrap_qty_bun
    
    Returns:
    
    Calculated Scrap Quantity in Base Unit of Measure
  - getSerial_no_profile
```
@Nullable
public String getSerial_no_profile()
```
    Constraints: Not nullable, Maximum length: 4
    Original property from the Odata EDM: serial_no_profile
    
    Returns:
    
    Freely definable four-digit key that provides unique identification for a serial number profile.
  - getSize1
```
@Nullable
public BigDecimal getSize1()
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    Original property from the Odata EDM: size1
    
    Variable-size item data for a sheet of metal:Size Description Entry1 Length 2002 Width 300No. of variable-size items: 10Size unit: MMStockkeeping unit for sheet metalin material master: SQMCalculation of variable-size item quantity:A = Size 1 * Size 2A = 200 MM * 300 MMA = 60.000 SQMM--> Quantity of variable-size item per sheet: 0.06 SQM10 sheets are entered in the component, so the variable-size item requirement is:10 * 0.06 SQM = 0.6 SQM.
    
    Returns:
    
    One dimension of the variable-size item, used as a variable in the variable-size item formula.
  - getSize2
```
@Nullable
public BigDecimal getSize2()
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    Original property from the Odata EDM: size2
    
    Variable-size item data for a sheet of metal:Size Description Entry1 Length 2002 Width 300No. of variable-size items: 10Size unit: MMStockkeeping unit for sheet metalin material master: SQMCalculation of variable-size item quantity:A = Size 1 * Size 2A = 200 MM * 300 MMA = 60.000 SQMM--> Quantity of variable-size item per sheet: 0.06 SQM10 sheets are entered in the component, so the variable-size item requirement is:10 * 0.06 SQM = 0.6 SQM.
    
    Returns:
    
    One dimension of the variable-size item, used as a variable in the variable-size item formula.
  - getSize3
```
@Nullable
public BigDecimal getSize3()
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    Original property from the Odata EDM: size3
    
    Variable-size item data for a sheet of metal:Size Description Entry1 Length 2002 Width 300No. of variable-size items: 10Size unit: MMStockkeeping unit for sheet metalin material master: SQMCalculation of variable-size item quantity:A = Size 1 * Size 2A = 200 MM * 300 MMA = 60.000 SQMM--> Quantity of variable-size item per sheet: 0.06 SQM10 sheets are entered in the component, so the variable-size item requirement is:10 * 0.06 SQM = 0.6 SQM.
    
    Returns:
    
    One dimension of the variable-size item, used as a variable in the variable-size item formula.
  - getSize_unit
```
@Nullable
public String getSize_unit()
```
    Constraints: Not nullable, Maximum length: 3
    Original property from the Odata EDM: size_unit
    
    Please note:If you do not enter a unit of measure for the size, the system enters the default unit stored in the IMG for BOMs under Control data.The size unit and variable-size item unit are interdependent.Example:Variable-size item data for a metal sheet-----------------------------------------Size Dimension Entry1 Length 2002 Width 300Size unit for variable-size item: MMIf you do not enter a formula, the system uses the standard formula: Size 1 * Size 2 (result -> area).= 200 MM * 300 MM= 60,000 MM2Either the variable-size item unit must have the dimension area (MM2, CM2, M2, and so on), or conversion factors must be maintained in the material master.
    
    Returns:
    
    Unit of measure for sizes 1 to 3.
  - getSoft_comp_indicator
```
@Nullable
public Boolean getSoft_comp_indicator()
```
    Constraints: none
    Original property from the Odata EDM: soft_comp_indicator
    
    Returns:
    
    Indicator: Software component
  - getSort_string
```
@Nullable
public String getSort_string()
```
    Constraints: Not nullable, Maximum length: 10
    Original property from the Odata EDM: sort_string
    
    Returns:
    
    String which can be defined as required for sorting components for display.
  - getSpecial_procurement_type
```
@Nullable
public String getSpecial_procurement_type()
```
    Constraints: Not nullable, Maximum length: 2
    Original property from the Odata EDM: special_procurement_type
    
    You use special procurement when you want to be able to override the procurement type in the material master or define the procurement type more precisely.If the procurement type is in-house, you can nevertheless force the system to ignore the BOM and routing, and process the material as if it were externally procured, by specifying the special procurement as external.Enter the special procurement type to which you want to restrict the selection.If you procure a material externally, you may want to choose the special procurement type Consignment. If you produce the material in-house, it may be appropriate to choose Production in other plant.If a material has a routing but no BOM, it is treated as an externally procured material even if the procurement type is in-house. Both the BOM and the routing are ignored.However, if you specify the special procurement type as in-house, the routing is included even if the material has no BOM.
    
    Returns:
    
    Allows you to define the procurement type more exactly. The system determines the procurement type from the material type.
  - getSpecial_proc_typ_itm
```
@Nullable
public String getSpecial_proc_typ_itm()
```
    Constraints: Not nullable, Maximum length: 2
    Original property from the Odata EDM: special_proc_typ_itm
    
    Enter the special procurement type to which you want to restrict the selection.If you procure a material externally, you may want to choose the special procurement type Consignment. If you produce a material in-house, it may be appropriate to choose Production in other plant.
    
    Returns:
    
    Allows you to define the procurement type more closely. The procurement type is determined from the material type.
  - getSpecial_proc_typ_mastr
```
@Nullable
public String getSpecial_proc_typ_mastr()
```
    Constraints: Not nullable, Maximum length: 2
    Original property from the Odata EDM: special_proc_typ_mastr
    
    Enter the special procurement type you want to restrict the selection to.For externally processed materials you can, for example, select the consignment order special procurement type. For in-house produced materials the production in another plant special procurement plant may be appropriate.
    
    Returns:
    
    Allows determination of the procurement type. The system determines the procurement type from the material type.
  - getSpec_proc_costing
```
@Nullable
public String getSpec_proc_costing()
```
    Constraints: Not nullable, Maximum length: 2
    Original property from the Odata EDM: spec_proc_costing
    
    If you enter a special procurement type in the Costing view of the material master record, it is used in costing.If you do not enter a special procurement type in the costing view of the material master record, the system uses the special procurement type in the MRP view.If you want to cost a material as externally procured by ignoring the existing quantity structure in the system when costing, the following options are available:In the MRP view of the material master record, enter procurement type F and no special procurement type (neither in the MRP view nor in the Costing view).In Customizing for Product Cost Planning, create a new special procurement type (procurement type: F and special procurement type: blank) and enter this special procurement type in the material's Costing view.If you want to cost a material by ignoring the BOM but including the routing, go to Customizing for Product Cost Planning and create a new special procurement type (procurement type: E; special procurement type: E) and enter this special procurement type in the material's Costing view.
    
    Returns:
    
    Key that you use to specify the material's procurement type predetermined by the material type in more detail for costing.
  - getStandard_price
```
@Nullable
public BigDecimal getStandard_price()
```
    Constraints: Not nullable, Precision: 12, Scale: 3
    Original property from the Odata EDM: standard_price
    
    The valuation of material stocks at standard prices means that all goods movements are valuated at the same price over an extended period.Price variances (for example, purchase price higher than standard price) upon goods receipt or invoice receipt are posted by the system to price difference accounts. This does not affect the standard price.
    
    Returns:
    
    Standard price of the material
  - getStatus_text
```
@Nullable
public String getStatus_text()
```
    Constraints: Not nullable, Maximum length: 16
    Original property from the Odata EDM: status_text
    
    Returns:
    
    Description of the current document status.
  - getStock_segment
```
@Nullable
public String getStock_segment()
```
    Constraints: Not nullable, Maximum length: 40
    Original property from the Odata EDM: stock_segment
    
    Returns:
    
    Segment assigned to a stockable item. The valid stock segment is defined in the segmentation strategy and the strategy is assigned to the material in the material master.
  - getStorage_location
```
@Nullable
public String getStorage_location()
```
    Constraints: Not nullable, Maximum length: 4
    Original property from the Odata EDM: storage_location
    
    Returns:
    
    Number of the storage location in which the material is stored. A plant may contain one or more storage locations.
  - getStrategy
```
@Nullable
public String getStrategy()
```
    Constraints: Not nullable, Maximum length: 1
    Original property from the Odata EDM: strategy
    
    This strategy is ignored in material requirements planning (MRP).The withdrawal posting for the reservation in the production order can be selected as follows:According to usage probability (manual changes possible)For all items that you want to reserve, enter:Strategy (value 1 or no entry)Priority (only influences how materials are sorted)Usage probabilityWithdrawal if 100% availabilityFor all items that you want to reserve, enter:Strategy (value 2)PriorityIf you do not enter a priority, the system checks the items in the sequence in which they are transferred to the availability check.Usage probabilityEnter the same strategy for all alternative items in an alternative item group.Withdrawal if 100% availability (strategy 2)This strategy uses ATP logic to check availability in the defined ranking order.Gross requirements: 100 piecesM UP (%) RO RQ ATP qty Issue qtyA 20 1 20 30 0B 30 2 30 150 100C 50 3 50 180 0KeyM MaterialUP Usage probabilityRO Ranking orderRQ Requirements quantityThe first material in the ranking order that is supplied 100% on the requirement date is reserved in the required quantity (material B).If a partial withdrawal is carried out in a production order, when additional partial withdrawals take place, no further checks are carried out for this production order. Additional partial withdrawals result from the alternative item, from which the first withdrawal took place.If when using strategy 2 none of the alternative items cover the requirements 100%, the availability check for all items will confirm the available. A reservation only occurs for the available quantity.
    
    Returns:
    
    This value defines how items in an alternative group are selected for withdrawal postings.
  - getSub_item_indicator
```
@Nullable
public Boolean getSub_item_indicator()
```
    Constraints: none
    Original property from the Odata EDM: sub_item_indicator
    
    Sub-items do not have an operational significance and changes arenot stored with history.
    
    Returns:
    
    Indicator: this BOM item has sub-items.
  - getSupplier
```
@Nullable
public String getSupplier()
```
    Constraints: Not nullable, Maximum length: 10
    Original property from the Odata EDM: supplier
    
    Returns:
    
    Specifies an alphanumeric key that uniquely identifies the supplier in the SAP system.
  - getTable_row
```
@Nullable
public Integer getTable_row()
```
    Constraints: none
    Original property from the Odata EDM: table_row
    
    Returns:
    
    Row number in a primary or secondary table index.
  - getTech_status_from
```
@Nullable
public String getTech_status_from()
```
    Constraints: Not nullable, Maximum length: 12
    Original property from the Odata EDM: tech_status_from
    
    All products produced in this phase are of the same type and option model.It can be used to describe the change statuses of a multi-level BOM which cannot be expressed in terms of an effectivity period (for example, lead-time offset).
    
    Returns:
    
    Organizational term, which describes the start of a production and planning unit for the product.
  - getTest_hist_nxt_lvl
```
@Nullable
public Boolean getTest_hist_nxt_lvl()
```
    Constraints: none
    Original property from the Odata EDM: test_hist_nxt_lvl
    
    Returns:
    
    Label that shows the BOM and/or BOM group has been historically (this means, by entering a change number) created and/or changed. This change number defines the validity of the technical status.
  - getTotals_record_id
```
@Nullable
public String getTotals_record_id()
```
    Constraints: Not nullable, Maximum length: 1
    Original property from the Odata EDM: totals_record_id
    
    Returns:
    
    Totals record indicator
  - getUnit_of_measure
```
@Nullable
public String getUnit_of_measure()
```
    Constraints: Not nullable, Maximum length: 3
    Original property from the Odata EDM: unit_of_measure
    
    The system determines the unit as follows:Material items with a material master record - base unit of measure from the material master record.Class items - unit defined in the additional data of the class.Additional units for material items with a material master record:For material items, you can maintain alternative units of measure to the base unit of measure in the material master.In bills of material, not all alternative units of measure are taken into account - only the unit of issue.Possible values are:base unit of measureunit of issueunits of measure that have the same dimension as either the base unit of measure or the unit of issueIf you enter no unit, the system proposes a unit from the material master if the item has a material master:If the unit of issue was entered on the storage detail screen, the system copies this unit. Otherwise, it copies the base unit of measure.
    
    Returns:
    
    The unit for the component quantity.
  - getUnloading_point
```
@Nullable
public String getUnloading_point()
```
    Constraints: Not nullable, Maximum length: 25
    Original property from the Odata EDM: unloading_point
    
    Returns:
    
    Specifies the point at which the material is to be unloaded (for example, ramp 1).
  - getUom_usage
```
@Nullable
public String getUom_usage()
```
    Constraints: Not nullable, Maximum length: 1
    Original property from the Odata EDM: uom_usage
    
    Proportion unitsProduct units
    
    Returns:
    
    You use this key to specify the units of measurement you want to use in addition to the base unit of measure and the alternative units of measure. The following additional units of measurement are supported:
  - getUsage_probability
```
@Nullable
public BigDecimal getUsage_probability()
```
    Constraints: Not nullable, Precision: 3, Scale: 0
    Original property from the Odata EDM: usage_probability
    
    The usage probability is always taken into account for requirements planning.Maintain selected usage probabilityRequirements planning for alternative items is based on the usage probability.Quantities are suggested based on the usage probability for the withdrawal posting according to strategy 1. You can plan in excess for the alternative items since the usage probability is not limited to 100%. You can change the proposed quantities. Maintain no usage probability If you do not enter a usage probability, the alternative item just serves as information that can be evaluated, for example, in a situation with a missing part.You receive a warning since dependent requirements with 0 as quantity are created.Withdrawal based on usage probabilityStrategy: value 1An alternative item group is maintained for each assembly. This alternative item group contains four materials with differing usage probabilities. Dependent requirements are passed on with 100 as quantity.Material Usage probability (%) RequirementM-1 70 70M-2 20 20M-3 20 20M-4 0 no requirementIn this case, the materials are planned in excess since the sum of the usage probabilities is greater than 100%.
    
    Returns:
    
    Percentage probability that a material will be used in the assembly.
  - getValidity_end_date
```
@Nullable
public LocalDateTime getValidity_end_date()
```
    Constraints: Not nullable, Precision: 0
    Original property from the Odata EDM: validity_end_date
    
    Returns:
    
    Valid-to date
  - getValidity_start_date
```
@Nullable
public LocalDateTime getValidity_start_date()
```
    Constraints: Not nullable, Precision: 0
    Original property from the Odata EDM: validity_start_date
    
    Returns:
    
    Specifies the start date for the validity period of an object (such as material, BOM, or routing).
  - getValuation_category
```
@Nullable
public String getValuation_category()
```
    Constraints: Not nullable, Maximum length: 1
    Original property from the Odata EDM: valuation_category
    
    In the case of split valuation, this indicator also determines which valuation types are allowed, that is, the criteria by which stocks can be valuated.
    
    Returns:
    
    Determines whether stocks of the material are valuated together or separately.
  - getVariants_nxt_lvl
```
@Nullable
public Boolean getVariants_nxt_lvl()
```
    Constraints: none
    Original property from the Odata EDM: variants_nxt_lvl
    
    Only used internally for storing the technical type.
    
    Returns:
    
    Label that shows a bill of material was created as a variant document structure.
  - getX_plant_material_status
```
@Nullable
public String getX_plant_material_status()
```
    Constraints: Not nullable, Maximum length: 2
    Original property from the Odata EDM: x_plant_material_status
    
    Materials management (for example, in purchasing and in inventory management)Production planning and controlPlant maintenanceWarehouse managementCosting with a quantity structureThe cross-plant material status restricts the usability of the material for all plants, that is, it defines whether a warning or error message is displayed if you include the material in a particular function.The material may be a part under development or one to be discontinued.
    
    Returns:
    
    Indicates whether the material may be used in the following areas for all plants:
  - getX_plt_status_valid_from
```
@Nullable
public LocalDateTime getX_plt_status_valid_from()
```
    Constraints: Not nullable, Precision: 0
    Original property from the Odata EDM: x_plt_status_valid_from
    
    The valid-from date of the material status is considered only if it precedes or is the same as the planning date; that is, if the valid-from date is later than the planning date, it is not considered, even if it is within the planning horizon.ExampleI<-------------Planning horizon------------->I-----I--------------------I-----------------------I-->Planning date Valid-from date TimeIn this case, the valid-from date is not considered in materials planning since it is later than the planning date.PurchasingThe valid-from date of the material status is checked against the current date.ExampleYou block the material for purchasing from May 1, xxxx. A purchase order is created for the material on April 28, xxxx with a delivery date of May 10, xxxx. In this case, the valid-from date May 1, xxxx is checked against the purchase order date April 28, xxxx and the purchase order is allowed. Had you created the purchase order on May 3, xxxx, an error message would have been issued.
    
    Returns:
    
    Materials planning
  - setAlternative_item
```
public void setAlternative_item(@Nullable
                                Boolean alternative_item)
```
    Constraints: none
    Original property from the Odata EDM: alternative_item
    
    The alternative items are chosen when a production order is created.
    
    Parameters:
    
    alternative_item - items.
  - setAlt_item_group
```
public void setAlt_item_group(@Nullable
                              String alt_item_group)
```
    Constraints: Not nullable, Maximum length: 2
    Original property from the Odata EDM: alt_item_group
    
    As soon as you enter an alternative item group, you see an additional dialog box with the following data: ranking order, strategy, usage probability.You can maintain alternative items in the following situations:Alternative positions with specific usage probabilityThese alternative items are incorporated with a specific usage probability. Enter the usage probability for each alternative item in the group, so that:dependent requirements are determined in requirements planningdependent requirements are changed to a reservation in the production orderAlternative positions as informationYou can enter an alternative item for information purposes. This item would then, for example, only be taken into account in situations involving missing parts.As there should be neither dependent requirements nor a reservation for this item, enter no usage probability.Enter the same character string to denote the alternative items of an alternative item group.Enter the same strategy for all alternative items in the alternative item group.Alternative items are valuated in the following way:Dependent requirements determinationRequirements planning determines the dependent requirements according to the usage probabilities that have been entered.If the usage probability is 0%, then no procurement is planned for the item. For information purposes, however, dependent requirements with 0 as quantity are created.Withdrawal postingYou can control the withdrawal posting for the resevation in the production order in the following way:Withdrawal according to usage probability (manual change is possible)Withdrawal if there is 100% availability(Check ranking order and strategy)Example: See Strategy for alternative position
    
    Parameters:
    
    alt_item_group - alternative item group.
  - setAlt_nxt_lvl
```
public void setAlt_nxt_lvl(@Nullable
                           Boolean alt_nxt_lvl)
```
    Constraints: none
    Original property from the Odata EDM: alt_nxt_lvl
    
    Parameters:
    
    alt_nxt_lvl -
  - setAssembly_indicator
```
public void setAssembly_indicator(@Nullable
                                  Boolean assembly_indicator)
```
    Constraints: none
    Original property from the Odata EDM: assembly_indicator
    
    You can use this indicator to restrict the selection of items in the BOM explosion. In this case, only the items that are PM assemblies are shown.The indicator does not interrupt the explosion of the BOM to the lowest lever. There are two steps to the BOM explosion:First, the system explodes the entire BOM, regardless of the indicators selected to restrict items. You do not see the result of this explosion on the screen.Second, the system reads the indicators selected to restrict items, such as the PM assembly indicator.These indicators work as filters. The explosion result you see on the screen only includes the items that fulfil the selection criteria.
    
    Parameters:
    
    assembly_indicator - are planned and carried out.
  - setAssign_effect_vals
```
public void setAssign_effect_vals(@Nullable
                                  Boolean assign_effect_vals)
```
    Constraints: none
    Original property from the Odata EDM: assign_effect_vals
    
    If you set the indicator, the following applies:If you only use date validity, you can override the date that the system uses to determine the components. To do this, you set certain change numbers as valid or invalid.If you use parameter effectivity, you can assign values to the effectivity parameters. As well as this you can set certain change numbers to valid or invalid and thus override the parameter variant (the values you previously assigned).
    
    Parameters:
    
    assign_effect_vals - explode an assembly or a finished product.
  - setAssy_scrap_itm_mat
```
public void setAssy_scrap_itm_mat(@Nullable
                                  BigDecimal assy_scrap_itm_mat)
```
    Constraints: Not nullable, Precision: 5, Scale: 2
    Original property from the Odata EDM: assy_scrap_itm_mat
    
    The assembly scrap is used in materials planning to calculate the lot size of the assembly. The system increases the quantity to be produced by the scrap quantity calculated.If the material is an assembly, specify the percentage scrap as required.If the quantity to be produced is 200 pieces and you specify an assembly scrap of 10%, you are reckoning with a scrap quantity of 20 pieces. As a result, 220 pieces are produced.The system increases the quantity to be produced for all of the assembly's components accordingly.
    
    Parameters:
    
    assy_scrap_itm_mat -
  - setAs_selection_cond
```
public void setAs_selection_cond(@Nullable
                                 Boolean as_selection_cond)
```
    Constraints: none
    Original property from the Odata EDM: as_selection_cond
    
    If you select this indicator, the classification of the item is taken into account when the object is configured.You can only select this indicator if you have classified the item first (entered a class type).
    
    Parameters:
    
    as_selection_cond -
  - setBase_qty_nxt_lvl
```
public void setBase_qty_nxt_lvl(@Nullable
                                BigDecimal base_qty_nxt_lvl)
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    Original property from the Odata EDM: base_qty_nxt_lvl
    
    In Customizing (bills of material), you can define a value that then becomes the default value when you create a bill of material.
    
    Parameters:
    
    base_qty_nxt_lvl -
  - setBase_unit_nxt_lvl
```
public void setBase_unit_nxt_lvl(@Nullable
                                 String base_unit_nxt_lvl)
```
    Constraints: Not nullable, Maximum length: 3
    Original property from the Odata EDM: base_unit_nxt_lvl
    
    The system determines this unit of measure from the material master record.You cannot make changes, because the stocks of a material are managed in this unit of measure.
    
    Parameters:
    
    base_unit_nxt_lvl - for all component quantities for this bill of material.
  - setBase_uom
```
public void setBase_uom(@Nullable
                        String base_uom)
```
    Constraints: Not nullable, Maximum length: 3
    Original property from the Odata EDM: base_uom
    
    You define the base unit of measure and also alternative units of measure and their conversion factors in the material master record.Since all data is updated in the base unit of measure, your entry is particularly important for the conversion of alternative units of measure. A quantity in the alternative unit of measure can only be shown precisely if its value can be shown with the decimal places available. To ensure this, please note the following:The base unit of measure is the unit satisfying the highest necessary requirement for precision.The conversion of alternative units of measure to the base unit should result in simple decimal fractions (not, for example, 1/3 = 0.333...).Inventory ManagementIn Inventory Management, the base unit of measure is the same as the stockkeeping unit.ServicesServices have units of measure of their own, including the following:Service unitUnit of measure at the higher item level. The precise quantities of the individual services are each at the detailed service line level.BlanketUnit of measure at service line level for services to be provided once only, and for which no precise quantities can or are to be specified.
    
    Parameters:
    
    base_uom - enter in other units of measure (alternative units of measure) to the base unit of measure.
  - setBatch_entry
```
public void setBatch_entry(@Nullable
                           String batch_entry)
```
    Constraints: Not nullable, Maximum length: 1
    Original property from the Odata EDM: batch_entry
    
    This indicator refers to the components of an order, not to the finished product to be manufactured. You have the following options:The batches can be determined when the goods issue is posted.The batches must be entered in the order before it is released.The batches must be entered in the order before the goods issue is posted, but not necessarily before the order is released.If you use pick parts, the batches are determined in the transfer order and then confirmed to the order. If there is no direct link between the transfer order and the production order/process order (for example, with release order parts or crate parts), you must enter the batches in the production order/process order manually.The batches are determined automatically when the order is released.
    
    Parameters:
    
    batch_entry -
  - setBatch_mgmt
```
public void setBatch_mgmt(@Nullable
                          Boolean batch_mgmt)
```
    Constraints: none
    Original property from the Odata EDM: batch_mgmt
    
    Parameters:
    
    batch_mgmt -
  - setBill_of_material
```
public void setBill_of_material(@Nullable
                                String bill_of_material)
```
    Constraints: Not nullable, Maximum length: 8
    Original property from the Odata EDM: bill_of_material
    
    The system assigns this number internally. These numbers are irrelevant to the user. You access the BOM by entering the object (for example, material or equipment) to which the BOM belongs.The system stores the following information under this number:all alternatives in a multiple BOMall variants in a variant BOMBOMs that are allocated to more than one plant
    
    Parameters:
    
    bill_of_material -
  - setBill_of_material_base_quant
```
public void setBill_of_material_base_quant(@Nullable
                                           BigDecimal bill_of_material_base_quant)
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    Original property from the Odata EDM: bill_of_material_base_quant
    
    You normally enter the quantity without a +/- sign (e.g. 66).For the following materials, you enter the quantity with a negative sign (e.g. 22-):Materials that are flagged as co-productsIntra materials (Process industries)When the display function is called, the system calculates the component quantity dependent in the input quantity and the base quantity.Input quantityCurrent component quantity = ------------------ * Saved component quantityBase quantity
    
    Parameters:
    
    bill_of_material_base_quant -
  - setBill_of_material_component
```
public void setBill_of_material_component(@Nullable
                                          String bill_of_material_component)
```
    Constraints: Not nullable, Maximum length: 40
    Original property from the Odata EDM: bill_of_material_component
    
    A master record is usually maintained in the system for a component.
    
    Parameters:
    
    bill_of_material_component -
  - setBill_of_material_comp_quant
```
public void setBill_of_material_comp_quant(@Nullable
                                           BigDecimal bill_of_material_comp_quant)
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    Original property from the Odata EDM: bill_of_material_comp_quant
    
    The quantity is usually entered without a +/- sign (e.g. 66).For the following materials, you enter the quantity with a negative sign (e.g. 22-):Materials that are flagged as co-productsIntra materials (Process industries)When the display function is called, the system calculates the current component quantity dependent on the input unit of measure and the base unit of measure.Input unit of measureCurrent component quantity = ------------------ * Saved component quantityBase quantity
    
    Parameters:
    
    bill_of_material_comp_quant -
  - setBill_of_material_item_category
```
public void setBill_of_material_item_category(@Nullable
                                              String bill_of_material_item_category)
```
    Constraints: Not nullable, Maximum length: 1
    Original property from the Odata EDM: bill_of_material_item_category
    
    This categorization allows you to process data that is relevant to the individual items in a BOM. The item category is used to control field selection, default values for BOM maintenance, triggering of specific system activities, and so on.Stock itemThis item category is used to manage material data that allows an item to be kept in stock.Document itemThis item category is used to manage document data that allows you to process original application data (for example, graphics created with a graphics program).Class item (for configurable BOMs)In configurable material BOMs, you can enter a class as a placeholder for selectable items. The class can contain either materials or documents.When you assign characteristic values while configuring the BOM, the system replaces the node with an object that has the same values as those assigned to the characteristic of the configuration. This makes BOMs with a larger number of variants easier to maintain, as you do not have to enter all items manually and assign a selection condition to them.Class items can be relevant to MRP.PM structure elementThis item is used to structure an equipment (PM assembly) for design purposes only.If you want to maintain a material for use as a PM structure element, use material type IBAU.
    
    Parameters:
    
    bill_of_material_item_category - (for example, material master or document info record) or whether they are kept in stock.
  - setBill_of_material_item_number
```
public void setBill_of_material_item_number(@Nullable
                                            String bill_of_material_item_number)
```
    Constraints: Not nullable, Maximum length: 4
    Original property from the Odata EDM: bill_of_material_item_number
    
    Parameters:
    
    bill_of_material_item_number -
  - setBill_of_material_item_quantity
```
public void setBill_of_material_item_quantity(@Nullable
                                              BigDecimal bill_of_material_item_quantity)
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    Original property from the Odata EDM: bill_of_material_item_quantity
    
    You usually enter the quantity without a +/- sign (for example, 66).For the following materials, you enter the quantity with a - sign(for example, 22-):Materials that are marked as co-productsIntra materials (in process industries)In display functions, the system calculates the current component quantity from the required quantity and the base quantity.Required quantityCurrent component quantity = ------------------ * Saved component quantityBase quantity
    
    Parameters:
    
    bill_of_material_item_quantity -
  - setBill_of_material_item_unit
```
public void setBill_of_material_item_unit(@Nullable
                                          String bill_of_material_item_unit)
```
    Constraints: Not nullable, Maximum length: 3
    Original property from the Odata EDM: bill_of_material_item_unit
    
    You define the base unit of measure and also alternative units of measure and their conversion factors in the material master record.Since all data is updated in the base unit of measure, your entry is particularly important for the conversion of alternative units of measure. A quantity in the alternative unit of measure can only be shown precisely if its value can be shown with the decimal places available. To ensure this, please note the following:The base unit of measure is the unit satisfying the highest necessary requirement for precision.The conversion of alternative units of measure to the base unit should result in simple decimal fractions (not, for example, 1/3 = 0.333...).Inventory ManagementIn Inventory Management, the base unit of measure is the same as the stockkeeping unit.ServicesServices have units of measure of their own, including the following:Service unitUnit of measure at the higher item level. The precise quantities of the individual services are each at the detailed service line level.BlanketUnit of measure at service line level for services to be provided once only, and for which no precise quantities can or are to be specified.
    
    Parameters:
    
    bill_of_material_item_unit - enter in other units of measure (alternative units of measure) to the base unit of measure.
  - setBill_Of_Material_Root
```
public void setBill_Of_Material_Root(@Nullable
                                     String bill_Of_Material_Root)
```
    Constraints: Not nullable, Maximum length: 8
    Original property from the Odata EDM: Bill_Of_Material_Root
    
    The system assigns this number internally. These numbers are irrelevant to the user. You access the BOM by entering the object (for example, material or equipment) to which the BOM belongs.The system stores the following information under this number:all alternatives in a multiple BOMall variants in a variant BOMBOMs that are allocated to more than one plant
    
    Parameters:
    
    bill_Of_Material_Root -
  - setBill_of_material_root_variant
```
public void setBill_of_material_root_variant(@Nullable
                                             String bill_of_material_root_variant)
```
    Constraints: Not nullable, Maximum length: 2
    Original property from the Odata EDM: bill_of_material_root_variant
    
    Parameters:
    
    bill_of_material_root_variant -
  - setBill_of_material_variant
```
public void setBill_of_material_variant(@Nullable
                                        String bill_of_material_variant)
```
    Constraints: Not nullable, Maximum length: 2
    Original property from the Odata EDM: bill_of_material_variant
    
    Parameters:
    
    bill_of_material_variant -
  - setBill_of_material_variant_usage
```
public void setBill_of_material_variant_usage(@Nullable
                                              String bill_of_material_variant_usage)
```
    Constraints: Not nullable, Maximum length: 1
    Original property from the Odata EDM: bill_of_material_variant_usage
    
    Parameters:
    
    bill_of_material_variant_usage -
  - setBom_change_number
```
public void setBom_change_number(@Nullable
                                 String bom_change_number)
```
    Constraints: Not nullable, Maximum length: 12
    Original property from the Odata EDM: bom_change_number
    
    If you make a change with reference to a change number, or create anobject with a change number, the following functions are at your disposal:The system determines the effectivity parametersThe conditions that the change is effective under can be defined in the change master record as follows:Changes with a date effectivity (valid from date)Changes with parameter effectivity (for example: serial no. effectivity)Log of the changes madeDocumentation for the changesRevision level to indicate the change status of a material or documentChanges released for the different areas in the company.
    
    Parameters:
    
    bom_change_number -
  - setBulk_material
```
public void setBulk_material(@Nullable
                             Boolean bulk_material)
```
    Constraints: none
    Original property from the Odata EDM: bulk_material
    
    The dependent requirements of bulk materials are not relevant to materials planning. This means they are not taken into account for net requirements calculation. Therefore planning for bulk materials should be consumption-based.If bulk materials are subject to material requirements planning, you must create planned independent requirements for them.Dependent requirements are only created in the planned order for information purposes and they can be displayed there. Dependent requirements for bulk material are not shown in the MRP list or the stock/req. list.You can maintain this indicator in both the material master record an the BOM item. The indicator in the material master record has higher priority.If a material is always used as a bulk material, set the indicator in the material master record.In this case, the Bulk material indicator in material master record is automatically set in the BOM item.If a material is only used as a bulk material in individual cases, set the indicator in the BOM item.To improve system performance, you can define in the IMG for MRP that no dependent requirements are to be created for bulk material items. However, this also means that you see no information on bulk material components in the planned order or production order.
    
    Parameters:
    
    bulk_material - example, washers or grease).
  - setB_o_m_alternative_text
```
public void setB_o_m_alternative_text(@Nullable
                                      String b_o_m_alternative_text)
```
    Constraints: Not nullable, Maximum length: 40
    Original property from the Odata EDM: b_o_m_alternative_text
    
    This information only applies to this individual alternative and variant.If you want to maintain a long text, choose the symbol to the right of the field. The system displays a different symbol for each situation:@0O@ Create long text@0Q@ Change long text@0P@ Display long text
    
    Parameters:
    
    b_o_m_alternative_text -
  - setB_o_m_alt_nxt_lvl
```
public void setB_o_m_alt_nxt_lvl(@Nullable
                                 String b_o_m_alt_nxt_lvl)
```
    Constraints: Not nullable, Maximum length: 2
    Original property from the Odata EDM: b_o_m_alt_nxt_lvl
    
    Parameters:
    
    b_o_m_alt_nxt_lvl -
  - setB_o_m_category
```
public void setB_o_m_category(@Nullable
                              String b_o_m_category)
```
    Constraints: Not nullable, Maximum length: 1
    Original property from the Odata EDM: b_o_m_category
    
    Material BOM - linked to a materialEquipment BOM - linked to an equipmentOrder BOM - linked to material, sales order and sales order item.
    
    Parameters:
    
    b_o_m_category -
  - setB_o_m_cat_nxt_lvl
```
public void setB_o_m_cat_nxt_lvl(@Nullable
                                 String b_o_m_cat_nxt_lvl)
```
    Constraints: Not nullable, Maximum length: 1
    Original property from the Odata EDM: b_o_m_cat_nxt_lvl
    
    Material BOM - Reference to materialEquipment BOM - Reference to equipmentOrder BOM - Reference to material, sales order, and sales order item
    
    Parameters:
    
    b_o_m_cat_nxt_lvl -
  - setB_o_m_component_description
```
public void setB_o_m_component_description(@Nullable
                                           String b_o_m_component_description)
```
    Constraints: Not nullable, Maximum length: 40
    Original property from the Odata EDM: b_o_m_component_description
    
    Parameters:
    
    b_o_m_component_description -
  - setB_o_m_explosion_level
```
public void setB_o_m_explosion_level(@Nullable
                                     BigDecimal b_o_m_explosion_level)
```
    Constraints: Not nullable, Precision: 2, Scale: 0
    Original property from the Odata EDM: b_o_m_explosion_level
    
    The BOM level and the path together identify the exact position of a phantom assembly in a BOM.A BOM contains the following phantom assemblies (Phan.Ass.) and materials:Material A___________________________________________Phan.Ass. B Phan.Ass. C Material D_____________ ___________Phan.Ass. E Mat. F Mat. G Mat. HMat. JTo enable the user to trace the positions of phantom assemblies in the BOM, the BOM levels and paths are assigned according to the following logic:Each BOM level is assigned a numberEach path in the BOM is assinged a numberIn the following BOM, the first number indicates the BOPM level, and the second indicates the path. Materials that are not phantom assemblies are assigned level and path number 0. However, if a material is a component of a phantom assembly, it inherits the level and path numbers from the phantom assembly.Material A(0/0)___________________________________________Phan.Ass. B Phan.Ass. C Material D(1/1) (1/2) (0/0)_____________ ___________Phan.Ass. E Mat. F Mat. G Mat. H(2/1) (1/1) (1/2) (1/2)Mat. J(2/1)
    
    Parameters:
    
    b_o_m_explosion_level -
  - setB_o_m_hdr_matl_hier_node
```
public void setB_o_m_hdr_matl_hier_node(@Nullable
                                        String b_o_m_hdr_matl_hier_node)
```
    Constraints: Not nullable, Maximum length: 40
    Original property from the Odata EDM: b_o_m_hdr_matl_hier_node
    
    Parameters:
    
    b_o_m_hdr_matl_hier_node -
  - setB_O_M_Hdr_Root_Matl_Hier_Node
```
public void setB_O_M_Hdr_Root_Matl_Hier_Node(@Nullable
                                             String b_O_M_Hdr_Root_Matl_Hier_Node)
```
    Constraints: Not nullable, Maximum length: 40
    Original property from the Odata EDM: B_O_M_Hdr_Root_Matl_Hier_Node
    
    Parameters:
    
    b_O_M_Hdr_Root_Matl_Hier_Node -
  - setB_o_m_header_base_unit
```
public void setB_o_m_header_base_unit(@Nullable
                                      String b_o_m_header_base_unit)
```
    Constraints: Not nullable, Maximum length: 3
    Original property from the Odata EDM: b_o_m_header_base_unit
    
    The system takes this unit from the material master.The unit cannot be changed, because stock of the material is managed using this unit.
    
    Parameters:
    
    b_o_m_header_base_unit - unit for all component quantities in this BOM.
  - setB_o_m_header_quantity_primary
```
public void setB_o_m_header_quantity_primary(@Nullable
                                             BigDecimal b_o_m_header_quantity_primary)
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    Original property from the Odata EDM: b_o_m_header_quantity_primary
    
    Using this customizing function, you can define a value which is set as a default when you create a bill of material.
    
    Parameters:
    
    b_o_m_header_quantity_primary -
  - setB_o_m_item_description
```
public void setB_o_m_item_description(@Nullable
                                      String b_o_m_item_description)
```
    Constraints: Not nullable, Maximum length: 40
    Original property from the Odata EDM: b_o_m_item_description
    
    If this text length (two lines of 40 characters each) is not sufficient, you can also enter a long text by choosing menu option Extras -> Long text -> Item.When you create an item long text, the first 80 characters of the BOM item text are copied to the long text.If you change the BOM item text, the first 80 characters of long text are automatically changed, too. If you change the first two lines of the BOM item long text, the short text is automatically changed.Note:For text items, this text is copied to the component description field on the item overview.
    
    Parameters:
    
    b_o_m_item_description -
  - setB_o_m_item_is_discontinued
```
public void setB_o_m_item_is_discontinued(@Nullable
                                          String b_o_m_item_is_discontinued)
```
    Constraints: Not nullable, Maximum length: 1
    Original property from the Odata EDM: b_o_m_item_is_discontinued
    
    If this indicator is set, the system transfers the dependent requirements in materials planning to the follow-up material if they are no longer covered by warehouse stocks. However, this requires:The part to be discontinued and the follow-up material to be planned using material requirements planning (MRP)The base unit of measure of the follow-up material to be the same as that of the part to be discontinuedNoteIn subcontracting, uncovered requirements are not switched to the follow-up material after the effective-out date. This is indicated by a corresponding exception message (58) in the MRP list.
    
    Parameters:
    
    b_o_m_item_is_discontinued - in materials planning.
  - setB_o_m_no_nxt_lvl
```
public void setB_o_m_no_nxt_lvl(@Nullable
                                String b_o_m_no_nxt_lvl)
```
    Constraints: Not nullable, Maximum length: 8
    Original property from the Odata EDM: b_o_m_no_nxt_lvl
    
    The system performs number assignment internally, and is not relevant for the user. The user works with the corresponding BOMs by entering an object (e.g. material, equipment) to which the BOM belongs.The system uses this number to save:All alternatives for a multiple BOMAll variants for a variant BOMBOMs that are assigned to more than one plant
    
    Parameters:
    
    b_o_m_no_nxt_lvl -
  - setB_o_m_usage_nxt_lvl
```
public void setB_o_m_usage_nxt_lvl(@Nullable
                                   String b_o_m_usage_nxt_lvl)
```
    Constraints: Not nullable, Maximum length: 1
    Original property from the Odata EDM: b_o_m_usage_nxt_lvl
    
    By selecting different indicators, you specify the maximum value of the item status and control whether the item must/can be processed in the specific area (for example, production), or whether processing is allowed at all.You can maintain separate BOMs containing different items for a material in the company areas Production and Pricing:Production bill of material:The BOM creates items that are relevant for production. These items are copied into the planned order. The dependent requirement is determined and is also copied to the production order during conversion. Production is triggered using the production order with the production of the material.Pricing bill of material:The BOM creates items that are relevant for determining material input costs for a product.If, for example, you create a pricing with a quantity structure, the BOM and all items relevant for determining the production costs are determined automatically.
    
    Parameters:
    
    b_o_m_usage_nxt_lvl -
  - setChange_number
```
public void setChange_number(@Nullable
                             String change_number)
```
    Constraints: Not nullable, Maximum length: 12
    Original property from the Odata EDM: change_number
    
    If you make a change with reference to a change number, or create anobject with a change number, the following functions are at your disposal:The system determines the effectivity parametersThe conditions that the change is effective under can be defined in the change master record as follows:Changes with a date effectivity (valid from date)Changes with parameter effectivity (for example: serial no. effectivity)Log of the changes madeDocumentation for the changesRevision level to indicate the change status of a material or documentChanges released for the different areas in the company.
    
    Parameters:
    
    change_number -
  - setChg_to_eng_chg_number
```
public void setChg_to_eng_chg_number(@Nullable
                                     String chg_to_eng_chg_number)
```
    Constraints: Not nullable, Maximum length: 12
    Original property from the Odata EDM: chg_to_eng_chg_number
    
    If the object has been changed using a change number, the system determines this change number automatically.Three change numbers (N1, N2 and N3) define the validity periods of the item:N1 N2 N3I-----------I----------------------I---------------->1.1.96 6.1.96 12.2.96If you change the item within the validity period of change number N1, the system enters N2 in Change number to.If you change the item within the validity period of change number N2, the system enters N3 in Change number to.
    
    Parameters:
    
    chg_to_eng_chg_number - object (material, for example).
  - setClassProperty
```
public void setClassProperty(@Nullable
                             String classProperty)
```
    Constraints: Not nullable, Maximum length: 18
    Original property from the Odata EDM: class
    
    Parameters:
    
    classProperty -
  - setClassification
```
public void setClassification(@Nullable
                              String classification)
```
    Constraints: Not nullable, Maximum length: 8
    Original property from the Odata EDM: classification
    
    Parameters:
    
    classification -
  - setClass_type
```
public void setClass_type(@Nullable
                          String class_type)
```
    Constraints: Not nullable, Maximum length: 3
    Original property from the Odata EDM: class_type
    
    Parameters:
    
    class_type -
  - setCommodity_code
```
public void setCommodity_code(@Nullable
                              String commodity_code)
```
    Constraints: Not nullable, Maximum length: 17
    Original property from the Odata EDM: commodity_code
    
    The Harmonized System contains code numbers for all goods that an be transported across national or regional boundaries. Goods are coded according to this nomenclature when declaring the import or export of goods to the proper authorities. The specification of standard commodity codes in declarations enables the authority to tally the quantities of imported or exported goods of specific goods categories for statistical purposes (INTRASTAT).
    
    Parameters:
    
    commodity_code -
  - setComp_maint_status
```
public void setComp_maint_status(@Nullable
                                 String comp_maint_status)
```
    Constraints: Not nullable, Maximum length: 15
    Original property from the Odata EDM: comp_maint_status
    
    Parameters:
    
    comp_maint_status -
  - setComp_scrap_itm
```
public void setComp_scrap_itm(@Nullable
                              BigDecimal comp_scrap_itm)
```
    Constraints: Not nullable, Precision: 5, Scale: 2
    Original property from the Odata EDM: comp_scrap_itm
    
    The assembly scrap is used in materials planning to calculate the lot size of the assembly. The system increases the quantity to be produced by the scrap quantity calculated.If the material is an assembly, specify the percentage scrap as required.If the quantity to be produced is 200 pieces and you specify an assembly scrap of 10%, you are reckoning with a scrap quantity of 20 pieces. As a result, 220 pieces are produced.The system increases the quantity to be produced for all of the assembly's components accordingly.
    
    Parameters:
    
    comp_scrap_itm -
  - setComp_scrap_itm_mat
```
public void setComp_scrap_itm_mat(@Nullable
                                  BigDecimal comp_scrap_itm_mat)
```
    Constraints: Not nullable, Precision: 5, Scale: 2
    Original property from the Odata EDM: comp_scrap_itm_mat
    
    The component scrap is used in material requirements planning to determine the input quantities of the components. When the BOMs are exploded, the system increases these input quantities of the components by the calculated scrap quantity.ExampleInput quantity 200 piecesComponent scrap 10 %Scrap quantity 20 pieces---> 220 pieces are usedYou can find examples for the calculation in relation to the indicator for net scrap in the section net scrap.If an assembly scrap is valid for a superordinate assembly, the system adds both scrap types together.If you have entered component scrap in the bill of material, the value in the latter is valid. In other cases, the value in the material master record is valid.
    
    Parameters:
    
    comp_scrap_itm_mat -
  - setConfig_mat_var
```
public void setConfig_mat_var(@Nullable
                              String config_mat_var)
```
    Constraints: Not nullable, Maximum length: 18
    Original property from the Odata EDM: config_mat_var
    
    Behind this object number lies the assignment of a variant to the valuation of the generally configurable material.The valuation is as follows:Gen.config.material BicycleVariant Blue bicycleChar.value BlueThe system internally saves, for example, the number 20. Behind this number is the characteristic value "blue" and the variant "blue bicycle" .
    
    Parameters:
    
    config_mat_var -
  - setConfig_multi_level
```
public void setConfig_multi_level(@Nullable
                                  Boolean config_multi_level)
```
    Constraints: none
    Original property from the Odata EDM: config_multi_level
    
    Parameters:
    
    config_multi_level -
  - setConf_bom_nxt_lvl
```
public void setConf_bom_nxt_lvl(@Nullable
                                Boolean conf_bom_nxt_lvl)
```
    Constraints: none
    Original property from the Odata EDM: conf_bom_nxt_lvl
    
    Combinable assembliesare used during sales variant processingcontain selectable parts that can be used alongside the non-variable parts in the variant to be produced.
    
    Parameters:
    
    conf_bom_nxt_lvl -
  - setCost_element
```
public void setCost_element(@Nullable
                            String cost_element)
```
    Constraints: Not nullable, Maximum length: 10
    Original property from the Odata EDM: cost_element
    
    which is to be debited with the goods issue, if you have entered a consumption account, orfor which an account assignment check is to be carried out.This entry is used in various areas:in MRP for purchase requisitionsin costing for pricingYou can only enter a G/L account for which a G/L account master is maintained in the appropriate company code.
    
    Parameters:
    
    cost_element -
  - setCounter
```
public void setCounter(@Nullable
                       String counter)
```
    Constraints: Not nullable, Maximum length: 8
    Original property from the Odata EDM: counter
    
    Parameters:
    
    counter -
  - setCo_product
```
public void setCo_product(@Nullable
                          Boolean co_product)
```
    Constraints: none
    Original property from the Odata EDM: co_product
    
    Enter a negative quantity.Example: 6- You can only enter an item as a co-product if:The material master (MRP 2 view) contains the Material can be a co-product indicator. (For some material types, such as raw materials for example, the co-product indicator is hidden in the standard SAP system.)You enter the item as a stock item
    
    Parameters:
    
    co_product -
  - setCreated_by_user
```
public void setCreated_by_user(@Nullable
                               String created_by_user)
```
    Constraints: Not nullable, Maximum length: 12
    Original property from the Odata EDM: created_by_user
    
    Parameters:
    
    created_by_user -
  - setCurrency
```
public void setCurrency(@Nullable
                        String currency)
```
    Constraints: Not nullable, Maximum length: 5
    Original property from the Odata EDM: currency
    
    Parameters:
    
    currency -
  - setCustoms_preference
```
public void setCustoms_preference(@Nullable
                                  String customs_preference)
```
    Constraints: Not nullable, Maximum length: 1
    Original property from the Odata EDM: customs_preference
    
    A preference agreement allows countries which do not belong to the same trading area to offer each other more favorable customs duties.
    
    Parameters:
    
    customs_preference - agreement between countries.
  - setDat_hist_nxt_lvl
```
public void setDat_hist_nxt_lvl(@Nullable
                                Boolean dat_hist_nxt_lvl)
```
    Constraints: none
    Original property from the Odata EDM: dat_hist_nxt_lvl
    
    Parameters:
    
    dat_hist_nxt_lvl - created and/or changed. This change number is only valid for a certain amount of time.
  - setDeletion_indicator
```
public void setDeletion_indicator(@Nullable
                                  Boolean deletion_indicator)
```
    Constraints: none
    Original property from the Odata EDM: deletion_indicator
    
    This indicator is relevant for changes that were made with reference to a change number, and where the effectivity has been defined using a new effectivity type.
    
    Parameters:
    
    deletion_indicator -
  - setDelivery_time_in_days
```
public void setDelivery_time_in_days(@Nullable
                                     BigDecimal delivery_time_in_days)
```
    Constraints: Not nullable, Precision: 3, Scale: 0
    Original property from the Odata EDM: delivery_time_in_days
    
    When an order-specific BOM is exploded, a purchase requisition is produced via an MRP program.
    
    Parameters:
    
    delivery_time_in_days -
  - setDel_Ind_nxt_lvl
```
public void setDel_Ind_nxt_lvl(@Nullable
                               Boolean del_Ind_nxt_lvl)
```
    Constraints: none
    Original property from the Odata EDM: del_Ind_nxt_lvl
    
    This indicator is relevant for changes that were made with reference to a change number, and where the effectivity has been defined using a new effectivity type.
    
    Parameters:
    
    del_Ind_nxt_lvl - deleted.
  - setDenominator
```
public void setDenominator(@Nullable
                           BigDecimal denominator)
```
    Constraints: Not nullable, Precision: 5, Scale: 0
    Original property from the Odata EDM: denominator
    
    To convert a quantity, whose unit of measure is not the same as the base unit of measure, into the base unit of measure, the system requires a quotient:Quantity (in alternative unit of measure) = quotient * quantity (in base unit of measure)Enter the number of units of the alternative unit of measure (denominator) that corresponds to the number of units of the base unit of measure (numerator).The alternative unit of measure is kilogram (kg). The base unit of measure is piece (PC). 5 kg correspond to 3 pieces.5 kg = 3 PC => 1 kg = 3/5 PCIn this case, the quotient is therefore 3/5 (the numerator being 3 and the denominator 5).You may enter only whole numbers in the numerator and denominator fields; that is, if 3.14 m² correspond to one piece, you must enter integer multiples (314 m² = 100 PC). In this case, the quotient is therefore 100/314 (the numerator being 100 and the denominator 314).
    
    Parameters:
    
    denominator - of measure.
  - setDiscont_group
```
public void setDiscont_group(@Nullable
                             String discont_group)
```
    Constraints: Not nullable, Maximum length: 2
    Original property from the Odata EDM: discont_group
    
    You can control the discontinuation as follows:Simple discontinuationAn item that is to be discontinued is replaced by a an item that is is to be introduced to the BOM.Settings in the material master record (materials planning):The discontinuation indicator value 1 is set in the material master record of the item to be discontinued.Settings in the BOM:The follow-up group of the item to be introduced and the discontinuation group of the item to be discontinued must have the same value.Dependent parallel discontinuationOne group of materials is replaced by another group. If an item is to be discontinued (main item), another item (dependent item) is also discontinued.Settings in the material master record (materials planning):Material of the main item to be discontinued: value 1Material of the dependent item: value 3Settings in the BOM:Both the main item and the dependent parallel item to be discontinued are identified by the same discontinuation group.Both the follow-up group of the items to be introduced and the discontinuation group of the items to be discontinued must have the same value.You can only enter a discontinuation group for an item if the discontinuation indicator (material master, MRP 4 view) supports discontinuation.A discontinued item is replaced by a follow-up item. In the follow-up item, you maintain a follow-up group.Example for a simple discontinuationItem 0010 (material M-1) is to be discontinued and replaced by follow-up item 0010 (material M-2).Discontinuation indicator in the material master record M-1: value 1Item Mat. DisconGrp FollGrp 0010 M-1 A1 -0010 M-2 - A1Example for a Parallel discontinuationItems 0010 (material M-1) and 0011 (material M-2) to be discontinued are replaced by items 0010 (material M-3) and 0011 (material M-4) to be introduced.Discontinuation indicator in the material master record:M-1: value 1 (main discontinued item)M-2: value 3 (dependent discontinued item)Item Mat. Discontinuation group Follow-up group0010 M-1 ,A1 -0011 M-2 ,A1 -0010 M-3 - A10011 M-4 - A1Abbreviations:Item. ItemMat. MaterialDisconGrp Discontinuation groupFollGrp. Follow-up group
    
    Parameters:
    
    discont_group - BOM.
  - setDistribution_key
```
public void setDistribution_key(@Nullable
                                String distribution_key)
```
    Constraints: Not nullable, Maximum length: 4
    Original property from the Odata EDM: distribution_key
    
    This means that the MRP controller can plan a daily supply of partial quantities (distributed over the validity period of the RS header) for repetitive manufacturing.
    
    Parameters:
    
    distribution_key - the validity period of the planned order or the production order. In so doing, the relationship between time and the consumption of components is established.
  - setDoc
```
public void setDoc(@Nullable
                   String doc)
```
    Constraints: Not nullable, Maximum length: 22
    Original property from the Odata EDM: doc
    
    Together with the document version, the document number is used as information for technical services. It is displayed in various lists.
    
    Parameters:
    
    doc -
  - setDocument_part
```
public void setDocument_part(@Nullable
                             String document_part)
```
    Constraints: Not nullable, Maximum length: 3
    Original property from the Odata EDM: document_part
    
    Design departments, for example, can use document parts to divide up large documents such as design drawings into pages.
    
    Parameters:
    
    document_part -
  - setDocument_type
```
public void setDocument_type(@Nullable
                             String document_type)
```
    Constraints: Not nullable, Maximum length: 3
    Original property from the Odata EDM: document_type
    
    Parameters:
    
    document_type - organizational procedures which result from them.
  - setDocument_version
```
public void setDocument_version(@Nullable
                                String document_version)
```
    Constraints: Not nullable, Maximum length: 2
    Original property from the Odata EDM: document_version
    
    A new version is assigned after the original files have been edited in the following processing situations:The new processing status varies from the original in a certain way (for example, text change sin a text file).You want the original processing status to remain the same (for example, documentation of project progress).
    
    Parameters:
    
    document_version -
  - setDoc_number
```
public void setDoc_number(@Nullable
                          String doc_number)
```
    Constraints: Not nullable, Maximum length: 25
    Original property from the Odata EDM: doc_number
    
    Parameters:
    
    doc_number -
  - setDoc_reqd
```
public void setDoc_reqd(@Nullable
                        Boolean doc_reqd)
```
    Constraints: none
    Original property from the Odata EDM: doc_reqd
    
    Changes to the inspection lot or usage decision are recorded by change documents and displayed in the change history for these objects.Status changes are recorded in status management and displayed in the status history.
    
    Parameters:
    
    doc_reqd -
  - setDoc_status
```
public void setDoc_status(@Nullable
                          String doc_status)
```
    Constraints: Not nullable, Maximum length: 2
    Original property from the Odata EDM: doc_status
    
    If a status network is defined for the document type you canchoose a status among the entry possibilities which is supported inthe current processing situation when you create orchange.You can find more information with an additional colored release indicator:If the document version is releasedIn which time interval the version is releasedYou define the status network in Customizing work step Define document type level Define document status.
    
    Parameters:
    
    doc_status -
  - setDoc_type
```
public void setDoc_type(@Nullable
                        String doc_type)
```
    Constraints: Not nullable, Maximum length: 3
    Original property from the Odata EDM: doc_type
    
    Together with the document number and the document version, the document type represents the key for document management. It is the main criterion for controlling document management. The document type controls field selection and the available statuses for a document info record.
    
    Parameters:
    
    doc_type -
  - setDoc_version
```
public void setDoc_version(@Nullable
                           String doc_version)
```
    Constraints: Not nullable, Maximum length: 2
    Original property from the Odata EDM: doc_version
    
    Together with the document number, the document version is used as information for technical services. It is displayed on various lists.
    
    Parameters:
    
    doc_version -
  - setEffective_out_date
```
public void setEffective_out_date(@Nullable
                                  LocalDateTime effective_out_date)
```
    Constraints: Not nullable, Precision: 0
    Original property from the Odata EDM: effective_out_date
    
    From this date, the system reassigns the dependent requirements that are no longer covered by warehouse stock of the discontinued material to the follow-up material. This is done as part of material requirements planning.Enter a date if you want to plan the discontinuation of a material for the long term.
    
    Parameters:
    
    effective_out_date - material, it is to be replaced by the follow-up material.
  - setEngineering_design
```
public void setEngineering_design(@Nullable
                                  Boolean engineering_design)
```
    Constraints: none
    Original property from the Odata EDM: engineering_design
    
    This item status indicator is used to control:Subsequent processing in related application areasSelection of items in the BOM explosionWhether you can set and remove this indicator, or whether the system makes an unchangeable setting, depends on the BOM usage you selected on the initial screen. You can find further information in Customizing for bills of material under General Data -> BOM Usage -> Define BOM usages.
    
    Parameters:
    
    engineering_design - production.
  - setException_bom
```
public void setException_bom(@Nullable
                             String exception_bom)
```
    Constraints: Not nullable, Maximum length: 4
    Original property from the Odata EDM: exception_bom
    
    In the following situations, for example, an assembly is not exploded:REKIrecursiveness recognized by systemNREKrecursiveness allowedNBERauthorization group for component is not covered by user profileCONVA conversion error occurred during quantity calculation, due to a conversion factor between the quantity units that was too high. Therefore, the quantity displayed on the result screen for BOM explosions is not reliable.
    
    Parameters:
    
    exception_bom -
  - setExplosion_type
```
public void setExplosion_type(@Nullable
                              String explosion_type)
```
    Constraints: Not nullable, Maximum length: 2
    Original property from the Odata EDM: explosion_type
    
    You can define an explosion type that transfers dependent requirements for phantom assemblies.For example, the explosion type is relevant to materials that have the following special procurement types:Phantom assemblyPhantom in planningDirect production (collective order)Direct procurementYou can also define whether the following functions are performed for the item:Long-term planningDeterming individual and collective requirements
    
    Parameters:
    
    explosion_type -
  - setFixed_price_co_prod
```
public void setFixed_price_co_prod(@Nullable
                                   Boolean fixed_price_co_prod)
```
    Constraints: none
    Original property from the Odata EDM: fixed_price_co_prod
    
    A material marked as a fixed price co-product is not costed using a joint production process.If the material is an output material of a process with several co-products, the costs for the fixed price co-product are taken from the process costs using the net realizable-value method.Set this indicator if the material is a co-product, but the costs are not to be determined using an apportionment method; instead, a preset price is to be used for the material.The price for the fixed price co-product is taken from a cost estimate without quantity structure; alternatively, a price from the material master is used.You can only set this indicator if you have also set the co-product indicator for the material.Fixed-price co-products are shown in the itemization as items of category M (not A, as is the case with normal co-products), albeit with negative quantities and values.
    
    Parameters:
    
    fixed_price_co_prod -
  - setFixed_quantity
```
public void setFixed_quantity(@Nullable
                              Boolean fixed_quantity)
```
    Constraints: none
    Original property from the Odata EDM: fixed_quantity
    
    A fixed quantity is not allowed for the following items:alternative itemco-productIf the component quantity isfixed,The quantity fixed quantity is not in proportion to the assembly being produced or the order quantity.The quantity for provision of material is fixed.not fixed,The quantity is in proportion to the quantity of the assembly being produced or the order quantity.The quantity for provision of material is in proportion to the order quantity.
    
    Parameters:
    
    fixed_quantity -
  - setFollow_up_grp
```
public void setFollow_up_grp(@Nullable
                             String follow_up_grp)
```
    Constraints: Not nullable, Maximum length: 2
    Original property from the Odata EDM: follow_up_grp
    
    You can control the discontinuation in the following way:Simple discontinuationSettings in the material master record (MRP 4 view):The discontinuation indicator value 1 is set In the material master record of the material to be discontinued.Settings in the BOM:The value of the follow-up group of the item to be introduced and the discontinuation group of the item to be discontinued must be the same.Dependent parallel discontinuationOne group of materials is replaced by another group of materials. When an item (main item) is discontinued, another item (dependent item) is also discontinued.Settings in the material master record (materials planning):Material of the main item to be discontinued: discontinuation indicator value 1Material of the dependent item: value 3Settings in the BOM:The main item and the dependent parallel item to be discontinued are identified by the same discontinuation group.The value of the follow-up group of the item to be introduced and the discontinuation group of the item to be discontinued must be the same.You can only maintain an item as a follow-up item when you enter it for the first time. The field value cannot be changed after you have entered and saved the item.The follow-up item(s) that are to replace the item to be discontinued must have the same value in the Discontinuation group field as the item to be discontinued has in the Follow-up group field (see the example below).The follow-up item defined in the BOM overrides any follow-up material defined in the material master record.You can only maintain the follow-up group for one item if:the component is planned to a schedule (for example, a warehouse item)the base unit of measure of the materials is identicalExample of a simple discontinuationfItem 0010 to be discontinued (material M-1) is replaced by item 0010 to be introduced (material M-2).Discontinuation indicator in the material master record M-1: value 1Item Material Discontinuation group Follow-up group0010 M-1 A1 -0010 M-2 - A1Example of a parallel discontinuationthe items 0010 (material M-1) and 0011 (material M-2) are replaced by the items 0010 (material M-3) and 0011 (material M-4) to be ntroduced.Discontinuation indicator in the material master record:M-1: Value 1 (main discontinued item)M-2: Value 3 (dependent discontinued item)Item Material Discontinuation group Follow-up group0010 M-1 A1 -0011 M-2 A1 -0010 M-3 - A10011 M-4 - A1Abbreviations:Item. ItemMat. MaterialDisconGrp Discontinuation groupFollGrp. Follow-up group
    
    Parameters:
    
    follow_up_grp - material. The follow-up group shows which follow-up item(s) are to replace the item to be discontinued.
  - setFollow_up_item
```
public void setFollow_up_item(@Nullable
                              Boolean follow_up_item)
```
    Constraints: none
    Original property from the Odata EDM: follow_up_item
    
    This means that, if dependent requirements for parts to be discontinued are not covered by stocks of the material, the dependent requirements are transferred to this follow-up item.The follow-up item defined in the BOM overrides any follow-up material defined in the material master record.In discontinuation data dataset, you use the follow-up group to define which item this item is to replace.The discontinued item to be replaced by this follow-up item must have the same value in the Discontinuation group field as the follow-up item has in the Follow-up group field (see example).For simple discontinuation, item 0010 (material M-1) is to be discontinued and replaced by follow-up items 0010 (material M-2) and 0011 (material M-3).Item Mat. FollInd. DisconGrp FollGrp 0010 M-1 - - E10010 M-2 X E1 -0011 M-3 X E1 -Abbreviations:Mat. MaterialFollInd. Follow-up indicatorDisconGrp Discontinuation groupFollGrp. Follow-up group
    
    Parameters:
    
    follow_up_item -
  - setFollow_up_product
```
public void setFollow_up_product(@Nullable
                                 String follow_up_product)
```
    Constraints: Not nullable, Maximum length: 40
    Original property from the Odata EDM: follow_up_product
    
    In the material master record and also in the bill of material (BOM), you can define a follow-up material for a material to be discontinued. The follow-up material defined in the BOM has a higher priority than that in the material master record.You must always specify a follow-up material in the material master record for the system to know a follow-up material if none has been specified in the BOM.Simple discontinuationA component to be discontinued is replaced with a follow-up component at a particular date.In the material master record of the component to be discontinued, you must set discontinuation indicator 1, enter a follow-up component, and specify an effective-out date.Dependent parallel discontinuationA group of materials is replaced with a group of materials; that is, if one component is to be discontinued (the main component), another component must also be discontinued (the subordinate component).In the material master record of the main component to be discontinued, you must set discontinuation indicator 1, enter a follow-up component, and specify an effective-out date. In the material master record of the subordinate component, you must set discontinuation indicator 3.
    
    Parameters:
    
    follow_up_product - discontinued once its warehouse stock is depleted.
  - setFormula_key
```
public void setFormula_key(@Nullable
                           String formula_key)
```
    Constraints: Not nullable, Maximum length: 2
    Original property from the Odata EDM: formula_key
    
    You want to calculate the volume of a rolled sheet of metal. This has a variable length and height, but a constant width (500 MM).The following are used in the calculation:SI units that are defined in CustomizingLength: M (meters)Volume: M3 (cubic meters)In the variable-size item, you only enter the variable values (size 1 and size 2) with a unit of measure that can be derived from the SI unit of the dimension.Example for dimension Length: MM (milllimeters), CM (centimeters), DM (decimeters), and M (meters)The variable-size item formula uses the SI unit, so you must enter the constant width in the formula in the SI unit (meters).Example: ROMS1 * ROMS2 * 0.5 (M)You can enter units of measure for calculating the variable-size item quantity with a formula. The quantity is always calculated in the SI unit of the dimension, such as M3 (cubic meters) for volume.
    
    Parameters:
    
    formula_key -
  - setGoods_receipt_duration_in_days
```
public void setGoods_receipt_duration_in_days(@Nullable
                                              BigDecimal goods_receipt_duration_in_days)
```
    Constraints: Not nullable, Precision: 3, Scale: 0
    Original property from the Odata EDM: goods_receipt_duration_in_days
    
    Parameters:
    
    goods_receipt_duration_in_days -
  - setGoods_recipient
```
public void setGoods_recipient(@Nullable
                               String goods_recipient)
```
    Constraints: Not nullable, Maximum length: 12
    Original property from the Odata EDM: goods_recipient
    
    Parameters:
    
    goods_recipient -
  - setHeader_record_id
```
public void setHeader_record_id(@Nullable
                                String header_record_id)
```
    Constraints: Not nullable, Maximum length: 1
    Original property from the Odata EDM: header_record_id
    
    Parameters:
    
    header_record_id -
  - setHeader_validity_end_date
```
public void setHeader_validity_end_date(@Nullable
                                        LocalDateTime header_validity_end_date)
```
    Constraints: Not nullable, Precision: 0
    Original property from the Odata EDM: header_validity_end_date
    
    Parameters:
    
    header_validity_end_date -
  - setHeader_validity_start_date
```
public void setHeader_validity_start_date(@Nullable
                                          LocalDateTime header_validity_start_date)
```
    Constraints: Not nullable, Precision: 0
    Original property from the Odata EDM: header_validity_start_date
    
    Parameters:
    
    header_validity_start_date -
  - setHl_configuration
```
public void setHl_configuration(@Nullable
                                Boolean hl_configuration)
```
    Constraints: none
    Original property from the Odata EDM: hl_configuration
    
    Parameters:
    
    hl_configuration -
  - setIndividual_coll
```
public void setIndividual_coll(@Nullable
                               String individual_coll)
```
    Constraints: Not nullable, Maximum length: 1
    Original property from the Odata EDM: individual_coll
    
    Individual requirementsRequirement quantities of the dependent material are stated individually.Collective requirementsRequirement quantities of the dependent material are grouped together.You can maintain this indicator in the following places:In the material master recordFor the explosion type of the BOM item (in Customizing for Basic Data in Define Explosion Types)The setting for the explosion type overrides that in the material master record.If the material is assigned to a material type that does not allow quantity-based inventory management in this plant, you can set the indicator to individual requirements only.If the stock is to be managed in sales order stock or project stock, the indicator must be set to one of the following options:Individual and collective requirementsIndividual requirements onlyIf a material managed in project stock is to be procured from another plant using a cross-company-code stock transport order, the indicator must be set to 2 (collective requirements) in the issuing plant because, in this specific context, individual project stock management is not possible in both plants.
    
    Parameters:
    
    individual_coll - the material:
  - setInternal_obj_no
```
public void setInternal_obj_no(@Nullable
                               String internal_obj_no)
```
    Constraints: Not nullable, Maximum length: 18
    Original property from the Odata EDM: internal_obj_no
    
    Here, the object number refers to the assignment of a variant to a plant-specific configurable material via the values assigned.The value assignment is as follows:General configurable material Racing bicycleVariant Blue racing bicycleCharacteristic value BlueThe system stores, for example, the number 20 internally. Behind this number lies the characteristic value "blue" for the variant "blue racing bicycle".
    
    Parameters:
    
    internal_obj_no -
  - setIntra_material
```
public void setIntra_material(@Nullable
                              String intra_material)
```
    Constraints: Not nullable, Maximum length: 40
    Original property from the Odata EDM: intra_material
    
    Parameters:
    
    intra_material -
  - setIssuing_plant
```
public void setIssuing_plant(@Nullable
                             String issuing_plant)
```
    Constraints: Not nullable, Maximum length: 4
    Original property from the Odata EDM: issuing_plant
    
    This entry is only taken into account for plant maintenance activities in the department responsible for plant maintenance.
    
    Parameters:
    
    issuing_plant - the BOM (Plant).
  - setIs_b_o_m_item_spare_part
```
public void setIs_b_o_m_item_spare_part(@Nullable
                                        String is_b_o_m_item_spare_part)
```
    Constraints: Not nullable, Maximum length: 1
    Original property from the Odata EDM: is_b_o_m_item_spare_part
    
    In a BOM explosion, you can use this indicator to restrict item selection.The indicator does not interrupt the explosion of the BOM to the lowest level. There are two steps to the BOM explosion:First, the system explodes the entire BOM, regardless of the indicators selected to restrict items. You do not see the result of this explosion on the screen.Second, the system reads the indicators selected to restrict items, such as the Spare part indicator.These indicators work as filters. The explosion result, you see on the screen only the items that fulfil the selection criteria. In this case, only the items with the spare part indicator you selected are shown.In the IMG for BOMs, you can group spare parts together according to various points of view - for example, according to different maintenance cycles.Spare part group A contains spare parts that need to be replaced after a machine runtime of 100 hours, whereas spare part group B contains spare parts that only need to be replaced after a machine runtime of 500 hours.
    
    Parameters:
    
    is_b_o_m_item_spare_part -
  - setIs_c_a_d
```
public void setIs_c_a_d(@Nullable
                        Boolean is_c_a_d)
```
    Constraints: none
    Original property from the Odata EDM: is_c_a_d
    
    Parameters:
    
    is_c_a_d - system via an interface.
  - setIs_material_provision
```
public void setIs_material_provision(@Nullable
                                     String is_material_provision)
```
    Constraints: Not nullable, Maximum length: 1
    Original property from the Odata EDM: is_material_provision
    
    In the BOM explosion, you can use this indicator to restrict the items selected.There are two types of material provision:Material provided by a vendorMaterial provided by a customerYou can also use the material provision indicator to identify the subcontracting type for a part. The following indicators are available:Refurbishment material to SC (value S in standard SAP system)Refurbishment material from SC (value X in standard SAP system)Subsequent delivery (value F in standard SAP system)If you do not enter information in this field, the components are provided to the subcontractor as consumable materials (initial value in the standard SAP system).Material provided by a vendorThis indicator controls material requirements planning. Maintain this indicator for BOM components only if the material master record of the header material supports subcontracting (Special procurement field).The special procurement key for subcontracting means that all components of the BOM are provided free of charge to a subcontractor for further processing. The items are copied to a subcontract order.If the item is provided to a vendor, do not enter any material provision indicator.Dependent requirements are generated for this item.If the item is already at a vendor's premises and is not provided by us, do enter an indicator.No dependent requirements are generated for this item.Material provided by a customerThis indicator is not currently active.
    
    Parameters:
    
    is_material_provision -
  - setIs_phantom_item
```
public void setIs_phantom_item(@Nullable
                               Boolean is_phantom_item)
```
    Constraints: none
    Original property from the Odata EDM: is_phantom_item
    
    Parameters:
    
    is_phantom_item -
  - setIs_software_component
```
public void setIs_software_component(@Nullable
                                     Boolean is_software_component)
```
    Constraints: none
    Original property from the Odata EDM: is_software_component
    
    Parameters:
    
    is_software_component -
  - setItem_category
```
public void setItem_category(@Nullable
                             String item_category)
```
    Constraints: Not nullable, Maximum length: 1
    Original property from the Odata EDM: item_category
    
    This categorization allows you to process data that is relevant to the individual items in a BOM. The item category is used to control field selection, default values for BOM maintenance, triggering of specific system activities, and so on.Stock itemThis item category is used to manage material data that allows an item to be kept in stock.Document itemThis item category is used to manage document data that allows you to process original application data (for example, graphics created with a graphics program).Class item (for configurable BOMs)In configurable material BOMs, you can enter a class as a placeholder for selectable items. The class can contain either materials or documents.When you assign characteristic values while configuring the BOM, the system replaces the node with an object that has the same values as those assigned to the characteristic of the configuration. This makes BOMs with a larger number of variants easier to maintain, as you do not have to enter all items manually and assign a selection condition to them.Class items can be relevant to MRP.PM structure elementThis item is used to structure an equipment (PM assembly) for design purposes only.If you want to maintain a material for use as a PM structure element, use material type IBAU.
    
    Parameters:
    
    item_category - (for example, material master or document info record) or whether they are kept in stock.
  - setItem_description_line_2
```
public void setItem_description_line_2(@Nullable
                                       String item_description_line_2)
```
    Constraints: Not nullable, Maximum length: 40
    Original property from the Odata EDM: item_description_line_2
    
    You can also enter a long text by choosing menu option Details --> Long text --> Item long text.If the text comprises less than three lines, it is stored in the BOM item. Otherwise, it is stored as a long text in the text database.
    
    Parameters:
    
    item_description_line_2 -
  - setItem_identification
```
public void setItem_identification(@Nullable
                                   String item_identification)
```
    Constraints: Not nullable, Maximum length: 8
    Original property from the Odata EDM: item_identification
    
    Parameters:
    
    item_identification -
  - setItem_node
```
public void setItem_node(@Nullable
                         String item_node)
```
    Constraints: Not nullable, Maximum length: 8
    Original property from the Odata EDM: item_node
    
    Parameters:
    
    item_node -
  - setItem_sign
```
public void setItem_sign(@Nullable
                         Boolean item_sign)
```
    Constraints: none
    Original property from the Odata EDM: item_sign
    
    Parameters:
    
    item_sign -
  - setLast_changed_by_user
```
public void setLast_changed_by_user(@Nullable
                                    String last_changed_by_user)
```
    Constraints: Not nullable, Maximum length: 12
    Original property from the Odata EDM: last_changed_by_user
    
    Parameters:
    
    last_changed_by_user -
  - setLast_change_date
```
public void setLast_change_date(@Nullable
                                LocalDateTime last_change_date)
```
    Constraints: Not nullable, Precision: 0
    Original property from the Odata EDM: last_change_date
    
    Parameters:
    
    last_change_date -
  - setLead_time_offset
```
public void setLead_time_offset(@Nullable
                                BigDecimal lead_time_offset)
```
    Constraints: Not nullable, Precision: 3, Scale: 0
    Original property from the Odata EDM: lead_time_offset
    
    This value is not included in lead-time scheduling for a task list.You can enter:A positive number of daysThe component is not required until after the start date.A negative number of daysThe component is required before the start date.Assembly AS-11 (start date 05/13/1998):Component Lead-time offset Finish dateM-01 2+ 05/15/1998M-02 2- 05/11/1998M-03 0 05/13/1998Component M-01 is not required until 2 days after the start date for the superior assembly.Component M-02 is required 2 days before the start date for the superior assembly, so the finish date for this component is 05/11/1998.The lead-time offset for component M-03 is 0, so the start date for the superior assembly is the same as the finish date for this component.Note:This information does not tell you the start date for the components, because the data required (such as in-house production time, processing time, or interoperation time) is not shown.
    
    Parameters:
    
    lead_time_offset - production of the superior assembly.
  - setLong_text_lang
```
public void setLong_text_lang(@Nullable
                              String long_text_lang)
```
    Constraints: Not nullable, Maximum length: 2
    Original property from the Odata EDM: long_text_lang
    
    Parameters:
    
    long_text_lang -
  - setLow_level_code
```
public void setLow_level_code(@Nullable
                              String low_level_code)
```
    Constraints: Not nullable, Maximum length: 3
    Original property from the Odata EDM: low_level_code
    
    The level that is set in the material master record represents the level at which the material will be planned. This means that the material will only be planned once all assemblies in which it occurs have been planned and exploded.The low-level code is set internally in the material master record when the BOM is maintained.
    
    Parameters:
    
    low_level_code - controls the sequence in which the material is planned in an MRP run: First the materials with low-level code 0 are planned, then the materials with low-level code 1, and so on. The lower the low-level code, the higher the number that is assigned to the material.
  - setMaintenance_status
```
public void setMaintenance_status(@Nullable
                                  String maintenance_status)
```
    Constraints: Not nullable, Maximum length: 15
    Original property from the Odata EDM: maintenance_status
    
    Which user departments may maintain a material master record of a particular material typeWhich user departments have already maintained the material master record at a particular hierarchy levelThe overall maintenance status is made up of the individual maintenance statuses. The individual maintenance statuses have the following meaning:User department Maintenance statusWork scheduling AAccounting BClassification CMRP DPurchasing EProduction resources/tools FCosting GBasic data KStorage LForecasting PQuality management QWarehouse management SSales VPlant stocks XStorage location stocks Z
    
    Parameters:
    
    maintenance_status -
  - setMaterial_component_price
```
public void setMaterial_component_price(@Nullable
                                        BigDecimal material_component_price)
```
    Constraints: Not nullable, Precision: 12, Scale: 3
    Original property from the Odata EDM: material_component_price
    
    Parameters:
    
    material_component_price -
  - setMaterial_group
```
public void setMaterial_group(@Nullable
                              String material_group)
```
    Constraints: Not nullable, Maximum length: 9
    Original property from the Odata EDM: material_group
    
    You can use material groups to:Restrict the scope of analysesSearch specifically for material master records via search helps
    
    Parameters:
    
    material_group - them to a particular material group.
  - setMaterial_is_configurable
```
public void setMaterial_is_configurable(@Nullable
                                        Boolean material_is_configurable)
```
    Constraints: none
    Original property from the Odata EDM: material_is_configurable
    
    If this indicator is set, you can assign a variant class to the material, making it possible to use it as a configurable material.You can set the indicator manually in the material master record, irrespective of the material type.
    
    Parameters:
    
    material_is_configurable -
  - setMaterial_Name
```
public void setMaterial_Name(@Nullable
                             String material_Name)
```
    Constraints: Not nullable, Maximum length: 40
    Original property from the Odata EDM: Material_Name
    
    You can enter one material description in each of any number of languages.In principle, you enter the material description on the data screen of the first user department for which you enter data, and in your logon language. You can overwrite the material description on the Basic Data screen.
    
    Parameters:
    
    material_Name -
  - setMaterial_type
```
public void setMaterial_type(@Nullable
                             String material_type)
```
    Constraints: Not nullable, Maximum length: 4
    Original property from the Odata EDM: material_type
    
    The material type defines certain attributes of the material and has important control functions.
    
    Parameters:
    
    material_type - trading goods.
  - setMat_purity_in_perc
```
public void setMat_purity_in_perc(@Nullable
                                  BigDecimal mat_purity_in_perc)
```
    Constraints: Not nullable, Precision: 5, Scale: 2
    Original property from the Odata EDM: mat_purity_in_perc
    
    Parameters:
    
    mat_purity_in_perc -
  - setMoving_price
```
public void setMoving_price(@Nullable
                            BigDecimal moving_price)
```
    Constraints: Not nullable, Precision: 12, Scale: 3
    Original property from the Odata EDM: moving_price
    
    Moving average pricePeriodic unit price (only if the material ledger is activated for the material)The system calculates the moving average price automatically by dividing the material value in the stock account by the total of all storage location stocks in the plant concerned. It changes the price with each valuation-relevant movement.The system changes the periodic unit price if you settle the material ledger and then save the data.The valuation of stocks at moving average price or periodic unit price means that the price of the material is adapted to the continual fluctuations in the procurement price.If the material ledger is activated for the material, the material's settlement control determines whether this price is the moving average price or the periodic unit price.
    
    Parameters:
    
    moving_price -
  - setMultiple_sel
```
public void setMultiple_sel(@Nullable
                            Boolean multiple_sel)
```
    Constraints: none
    Original property from the Odata EDM: multiple_sel
    
    Parameters:
    
    multiple_sel - more than one object. Only if the configuration scenario allows manual changes to the BOM (order BOM or sales order with manual changes) can a class item be temporarily replaced by more than one object. However, before you save, the selection must be restricted to one object by using a manual object search. If you leave the configuration while the class item is still replaced by more than one object, only the first object is saved or transferred to the calling application. The "Multiple Selection" indicator has the following effect in interactive configuration: the configuration is still consistent if the class item has been replaced by more than one object. Without this indicator, the configuration is inconsistent if the class item has been replaced by more than one object. In low-level configuration (MRP, for example), only one object is used to replace the class, whether or not the "Multiple Selection" indicator is set.
  - setM_r_p_type
```
public void setM_r_p_type(@Nullable
                          String m_r_p_type)
```
    Constraints: Not nullable, Maximum length: 2
    Original property from the Odata EDM: m_r_p_type
    
    Manual reorder point planningAutomatic reorder point planningForecast-based planningMaterial requirements planning with forecasts for unplanned consumptionMaster production scheduling (MPS)Demand-driven replenishment
    
    Parameters:
    
    m_r_p_type -
  - setNet_scrap_indicator
```
public void setNet_scrap_indicator(@Nullable
                                   Boolean net_scrap_indicator)
```
    Constraints: none
    Original property from the Odata EDM: net_scrap_indicator
    
    You must set this indicator if you want assembly scrap to be ignored.You must set this indicator if you enter operation scrap.You can set this indicator if you only enter component scrap, to calculate scrap on the basis of the net required quantity for the assembly.Bill of material:Assembly MAT-1:Required quantity 100 piecesAssembly scrap 2%Component MAT-2:Component quantity 100 piecesDepending on the applicable scrap and the net indicator, the following 6 quantities are required for component MAT-2 for a required quantity of 100 pieces of MAT-1:1 2 3 4 5 6 Comp 5% - 5% 5% - -Op. 6% 6% - - - -Net ind X X X - - X---------------------------------------------------------------------Qty 11130 10600 10500 10710 10200 10000KeyComp Component scrapOp. Operation scrapNet ind Net indicatorQty Quantity calculated for component MAT-2 in pieces
    
    Parameters:
    
    net_scrap_indicator - quantity (the required quantity without assembly scrap from the material master record).
  - setNo_cu_instances
```
public void setNo_cu_instances(@Nullable
                               String no_cu_instances)
```
    Constraints: Not nullable, Maximum length: 6
    Original property from the Odata EDM: no_cu_instances
    
    If a pole always has two cross arms, you set the number of instances for the cross arm to 2.
    
    Parameters:
    
    no_cu_instances -
  - setNo_of_sheets
```
public void setNo_of_sheets(@Nullable
                            String no_of_sheets)
```
    Constraints: Not nullable, Maximum length: 3
    Original property from the Odata EDM: no_of_sheets
    
    Parameters:
    
    no_of_sheets -
  - setNo_var_size_items
```
public void setNo_var_size_items(@Nullable
                                 BigDecimal no_var_size_items)
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    Original property from the Odata EDM: no_var_size_items
    
    Parameters:
    
    no_var_size_items -
  - setNumerator
```
public void setNumerator(@Nullable
                         BigDecimal numerator)
```
    Constraints: Not nullable, Precision: 5, Scale: 0
    Original property from the Odata EDM: numerator
    
    To convert a quantity, whose unit of measure is not the same as the base unit of measure, into the base unit of measure, the system requires a quotient:Quantity (in alternative unit of measure) = quotient * quantity (in base unit of measure)Enter the number of units of the alternative unit of measure (denominator) that corresponds to the number of units of the base unit of measure (numerator).The alternative unit of measure is kilogram (kg). The base unit of measure is piece (PC). 5 kg correspond to 3 pieces.5 kg = 3 PC => 1 kg = 3/5 PCIn this case, the quotient is therefore 3/5 (the numerator being 3 and the denominator 5).You may enter only whole numbers in the numerator and denominator fields; that is, if 3.14 m² correspond to one piece, you must enter integer multiples (314 m² = 100 PC). In this case, the quotient is therefore 100/314 (the numerator being 100 and the denominator 314).
    
    Parameters:
    
    numerator - measure.
  - setObject_description
```
public void setObject_description(@Nullable
                                  String object_description)
```
    Constraints: Not nullable, Maximum length: 40
    Original property from the Odata EDM: object_description
    
    Parameters:
    
    object_description -
  - setObject_type
```
public void setObject_type(@Nullable
                           String object_type)
```
    Constraints: Not nullable, Maximum length: 1
    Original property from the Odata EDM: object_type
    
    Via settings in Customizing (Bill of mat. -> Item data), you can define a language-dependent abbreviation which the system displays on the General item overview screen.
    
    Parameters:
    
    object_type - material or document.
  - setObj_dep_assgt_no
```
public void setObj_dep_assgt_no(@Nullable
                                String obj_dep_assgt_no)
```
    Constraints: Not nullable, Maximum length: 18
    Original property from the Odata EDM: obj_dep_assgt_no
    
    Parameters:
    
    obj_dep_assgt_no -
  - setOperation_scrap_perc
```
public void setOperation_scrap_perc(@Nullable
                                    BigDecimal operation_scrap_perc)
```
    Constraints: Not nullable, Precision: 5, Scale: 2
    Original property from the Odata EDM: operation_scrap_perc
    
    This entry is used to override the assembly scrap for materials of high value.If operation scrap is maintained, you avoid the situation whereby too much of the material is planned in MRP for the components of subsequent operations.If you make an entry for operation scrap, you must also select the operation scrap net indicator (Net field).You can find examples of scrap under net scrap.
    
    Parameters:
    
    operation_scrap_perc -
  - setOper_lto_unit
```
public void setOper_lto_unit(@Nullable
                             String oper_lto_unit)
```
    Constraints: Not nullable, Maximum length: 3
    Original property from the Odata EDM: oper_lto_unit
    
    Parameters:
    
    oper_lto_unit -
  - setOper_lt_offset
```
public void setOper_lt_offset(@Nullable
                              BigDecimal oper_lt_offset)
```
    Constraints: Not nullable, Precision: 3, Scale: 0
    Original property from the Odata EDM: oper_lt_offset
    
    (In the Project System read activity for operation.)The following areas evaluate the operation related lead-time offset:Plant maintenance ordersNetworksProduction ordersProcess ordersMaintain the following times dependently of the +/- sign:Lead-time offset - positive valueComponent can be available after the operation start dateLead time - negative valueComponent must be available before the operation start dateOperation start date 0010: 05.13.1998, 9 a.m.Operation start date 0020: 05.14.1998, 2 p.m.---------------------------------------------------------Component Operation Lead-time offset (h) End dateM-01 0010 2+ 05.13.1998, 11 a.m.M-02 0020 2- 05.14.1998, 12 a.m.The component M-01 does not have to be available until 2 hours after the start time of the allocated operation 0010.Because the component M-02 must be available 2 hours before the start time of the allocated operation, the end time is 12 a.m.
    
    Parameters:
    
    oper_lt_offset - operation.
  - setOrg_area
```
public void setOrg_area(@Nullable
                        String org_area)
```
    Constraints: Not nullable, Maximum length: 10
    Original property from the Odata EDM: org_area
    
    On the characteristics screen of the class, you can assign characteristics to the organizational areas you have defined for the class.
    
    Parameters:
    
    org_area -
  - setPage_format
```
public void setPage_format(@Nullable
                           String page_format)
```
    Constraints: Not nullable, Maximum length: 4
    Original property from the Odata EDM: page_format
    
    Parameters:
    
    page_format -
  - setPage_number
```
public void setPage_number(@Nullable
                           String page_number)
```
    Constraints: Not nullable, Maximum length: 3
    Original property from the Odata EDM: page_number
    
    Parameters:
    
    page_number -
  - setPath
```
public void setPath(@Nullable
                    BigDecimal path)
```
    Constraints: Not nullable, Precision: 4, Scale: 0
    Original property from the Odata EDM: path
    
    Using the route of predecessor and component, you can reconstruct the exact structure of a bill of material.The level and/or the route are only relevant for planning using dummy assemblies.Level and route show you the exact position of a dummy assembly within a bill of material.A BOM contains the following dummy assemblies (DummyAs) and materials:Material A___________________________________________DummyAs B DummyAs C Material D_____________ ___________DummyAs E Mat. F Mat. G Mat. HMat. JIn order to track the position of the assemblies within the BOM structure, the levels and routes are assigned according to the following logic:A level number is assigned for each BOM levelA route number is assigned for each BOM pathIn the following BOM, the first number refers to the level, the second number the route. If the material is not a dummy assembly, the number '0' is assigned as level and/or route. If the material is a component of a dummy assembly however, then the component inherits the level and route from the dummy assembly.Material A(0/0)___________________________________________DummyAs B DummyAs C Material D(1/1) (1/2) (0/0)_____________ ___________DummyAs E Mat. F Mat. G Mat. H(2/1) (1/1) (1/2) (1/2)Mat. J(2/1)
    
    Parameters:
    
    path -
  - setPath_predecessor
```
public void setPath_predecessor(@Nullable
                                BigDecimal path_predecessor)
```
    Constraints: Not nullable, Precision: 4, Scale: 0
    Original property from the Odata EDM: path_predecessor
    
    Using the route of predecessor and component, you can reconstruct the exact structure of a bill of material.The level and/or the route are only relevant for planning using dummy assemblies.Level and route show you the exact position of a dummy assembly within a bill of material.A BOM contains the following dummy assemblies (DummyAs) and materials:Material A___________________________________________DummyAs B DummyAs C Material D_____________ ___________DummyAs E Mat. F Mat. G Mat. HMat. JIn order to track the position of the assemblies within the BOM structure, the levels and routes are assigned according to the following logic:A level number is assigned for each BOM levelA route number is assigned for each BOM pathIn the following BOM, the first number refers to the level, the second number the route. If the material is not a dummy assembly, the number '0' is assigned as level and/or route. If the material is a component of a dummy assembly however, then the component inherits the level and route from the dummy assembly.Material A(0/0)___________________________________________DummyAs B DummyAs C Material D(1/1) (1/2) (0/0)_____________ ___________DummyAs E Mat. F Mat. G Mat. H(2/1) (1/1) (1/2) (1/2)Mat. J(2/1)
    
    Parameters:
    
    path_predecessor -
  - setPlant
```
public void setPlant(@Nullable
                     String plant)
```
    Constraints: Not nullable, Maximum length: 4
    Original property from the Odata EDM: plant
    
    Parameters:
    
    plant -
  - setPlant_maintenance
```
public void setPlant_maintenance(@Nullable
                                 Boolean plant_maintenance)
```
    Constraints: none
    Original property from the Odata EDM: plant_maintenance
    
    Items that are relevant to plant maintenance are used in maintenance BOMs (material BOMs that are relevant to plant maintenance, equipment BOMs, and functional location BOMs).This item status indicator is used to control:Subsequent processing in related application areasSelection of items in the BOM explosionWhether you can set and remove this indicator, or whether the system makes an unchangeable setting, depends on the BOM usage you selected on the initial screen. You can find further information in Customizing for bills of material under General Data -> BOM Usage -> Define BOM usages.
    
    Parameters:
    
    plant_maintenance -
  - setPlant_sp_matl_status
```
public void setPlant_sp_matl_status(@Nullable
                                    String plant_sp_matl_status)
```
    Constraints: Not nullable, Maximum length: 2
    Original property from the Odata EDM: plant_sp_matl_status
    
    Materials management (for example, in purchasing and in inventory management)Production planning and controlPlant maintenanceWarehouse managementCosting with a quantity structureThe plant-specific material status restricts the usability of the material for the plant concerned, that is, it defines whether a warning or error message is displayed if you include the material in a particular function.The material may be a part under development or one to be discontinued.
    
    Parameters:
    
    plant_sp_matl_status -
  - setPlt_sp_status_valid_from
```
public void setPlt_sp_status_valid_from(@Nullable
                                        LocalDateTime plt_sp_status_valid_from)
```
    Constraints: Not nullable, Precision: 0
    Original property from the Odata EDM: plt_sp_status_valid_from
    
    The valid-from date of the material status is considered only if it precedes or is the same as the planning date; that is, if the valid-from date is later than the planning date, it is not considered, even if it is within the planning horizon.ExampleI<-------------Planning horizon------------->I-----I--------------------I-----------------------I-->Planning date Valid-from date TimeIn this case, the valid-from date is not considered in materials planning since it is later than the planning date.PurchasingThe valid-from date of the material status is checked against the current date.ExampleYou block the material for purchasing from May 1, xxxx. A purchase order is created for the material on April 28, xxxx with a delivery date of May 10, xxxx. In this case, the valid-from date May 1, xxxx is checked against the purchase order date April 28, xxxx and the purchase order is allowed. Had you created the purchase order on May 3, xxxx, an error message would have been issued.
    
    Parameters:
    
    plt_sp_status_valid_from -
  - setPm_assembly
```
public void setPm_assembly(@Nullable
                           Boolean pm_assembly)
```
    Constraints: none
    Original property from the Odata EDM: pm_assembly
    
    You can use this indicator to restrict the selection of items in the BOM explosion. In this case, only the items that are PM assemblies are shown.The indicator does not interrupt the explosion of the BOM to the lowest lever. There are two steps to the BOM explosion:First, the system explodes the entire BOM, regardless of the indicators selected to restrict items. You do not see the result of this explosion on the screen.Second, the system reads the indicators selected to restrict items, such as the PM assembly indicator.These indicators work as filters. The explosion result you see on the screen only includes the items that fulfil the selection criteria.
    
    Parameters:
    
    pm_assembly - are planned and carried out.
  - setPrice_control
```
public void setPrice_control(@Nullable
                             String price_control)
```
    Constraints: Not nullable, Maximum length: 1
    Original property from the Odata EDM: price_control
    
    Standard priceMoving average priceIf the material ledger is activated for the material, this indicator, together with the material's price determination indicator, determines at which of the following prices the material is valuated:Standard priceMoving average pricePeriodic unit price
    
    Parameters:
    
    price_control -
  - setPrice_unit
```
public void setPrice_unit(@Nullable
                          BigDecimal price_unit)
```
    Constraints: Not nullable, Precision: 5, Scale: 0
    Original property from the Odata EDM: price_unit
    
    10 litres of gasoline cost $12. The price unit here is 10.
    
    Parameters:
    
    price_unit -
  - setPriority
```
public void setPriority(@Nullable
                        String priority)
```
    Constraints: Not nullable, Maximum length: 2
    Original property from the Odata EDM: priority
    
    With respect to withdrawal postings, the ranking order determines which material components from the alternative item group should be taken into account for the reservation in the production order.Withdrawal according to usage probabilityFor all items that should be reserved, maintain:strategy (value 1 or no entry)ranking order (only effects the material sort)usage probabilityWithdrawal on 100% availabilityFor all items that should be reserved, maintain:ranking orderIf you do not enter the ranking order, the system checks the items in the order that they are transmitted to the availability check.strategy (value 2)usage probabilityThree items (0060 und 0065 and 0070) are assigned to an alternative item group and are given the following values for ranking order:position ranking order0060 30065 20070 1This means that the system reads item 0070 first.
    
    Parameters:
    
    priority -
  - setProcured_externally
```
public void setProcured_externally(@Nullable
                                   Boolean procured_externally)
```
    Constraints: none
    Original property from the Odata EDM: procured_externally
    
    Parameters:
    
    procured_externally -
  - setProdn_supply_area
```
public void setProdn_supply_area(@Nullable
                                 String prodn_supply_area)
```
    Constraints: Not nullable, Maximum length: 10
    Original property from the Odata EDM: prodn_supply_area
    
    The PSA is used in Kanban and JIT Outbound processing and in Extended Warehouse Management.
    
    Parameters:
    
    prodn_supply_area - make material directly available for production purposes.
  - setProduction_relevant
```
public void setProduction_relevant(@Nullable
                                   Boolean production_relevant)
```
    Constraints: none
    Original property from the Odata EDM: production_relevant
    
    Items with this indicator are copied to the planned order, and the system calculates dependent requirements for them. When the planned order is converted to a production order, the system automatically copies these items to the production order.This item status indicator is used to control:Subsequent processing in related application areasSelection of items in the BOM explosionWhether you can set and remove this indicator, or whether the system makes an unchangeable setting, depends on the BOM usage you selected on the initial screen. You can find further information in Customizing for bills of material under General Data -> BOM Usage -> Define BOM usages.
    
    Parameters:
    
    production_relevant -
  - setProduction_supply_area
```
public void setProduction_supply_area(@Nullable
                                      String production_supply_area)
```
    Constraints: Not nullable, Maximum length: 10
    Original property from the Odata EDM: production_supply_area
    
    The PSA is used in Kanban and JIT Outbound processing and in Extended Warehouse Management.
    
    Parameters:
    
    production_supply_area - make material directly available for production purposes.
  - setProduction_version
```
public void setProduction_version(@Nullable
                                  String production_version)
```
    Constraints: Not nullable, Maximum length: 4
    Original property from the Odata EDM: production_version
    
    The production version determines the following:the BOM alternative for a BOM explosionthe task list type, the task list group and the task list group counter for allocation to task listslot-size restrictions for repetitive manufacturing
    
    Parameters:
    
    production_version -
  - setProd_order_issue_location
```
public void setProd_order_issue_location(@Nullable
                                         String prod_order_issue_location)
```
    Constraints: Not nullable, Maximum length: 4
    Original property from the Odata EDM: prod_order_issue_location
    
    If the material is a component, it is the issuing storage location to which a backflush is posted.If the material is produced, it is the receiving storage location to which the receipt of the material is posted.
    
    Parameters:
    
    prod_order_issue_location - the planned order, production order, or run schedule quantity.
  - setProfit_center
```
public void setProfit_center(@Nullable
                             String profit_center)
```
    Constraints: Not nullable, Maximum length: 10
    Original property from the Odata EDM: profit_center
    
    Parameters:
    
    profit_center -
  - setPurchase_org
```
public void setPurchase_org(@Nullable
                            String purchase_org)
```
    Constraints: Not nullable, Maximum length: 4
    Original property from the Odata EDM: purchase_org
    
    Parameters:
    
    purchase_org -
  - setPurchasing_group
```
public void setPurchasing_group(@Nullable
                                String purchasing_group)
```
    Constraints: Not nullable, Maximum length: 3
    Original property from the Odata EDM: purchasing_group
    
    Internally, the purchasing group is responsible for the procurement of a material or a class of materials.Externally, it is the medium through which contacts with the vendor are maintained.
    
    Parameters:
    
    purchasing_group -
  - setPurchasing_organisation
```
public void setPurchasing_organisation(@Nullable
                                       String purchasing_organisation)
```
    Constraints: Not nullable, Maximum length: 4
    Original property from the Odata EDM: purchasing_organisation
    
    Parameters:
    
    purchasing_organisation -
  - setQty_var_size_item
```
public void setQty_var_size_item(@Nullable
                                 BigDecimal qty_var_size_item)
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    Original property from the Odata EDM: qty_var_size_item
    
    The quantity of the variable-size item shown is per piece (PC)If you change a field that affects the calculation of the variable-size item quantity (for example, size or formula), the system only recalculates the quantity if you delete the existing quantity first.To do this, delete the contents of the Qty Var-sz item field.Size 1: 200Size 2: 300Size unit of measure: MMVariable size item unit: SQMCalculation of variable-size item quantity:A = Size 1 * Size 2A = 200 MM * 300 MMA = 0,06 SQM--> The variable-size item quantity for each piece is: 0.06 SQMThe value calculated is required in MRP, in order to calculate the total quantity of the raw material requirement for the component.If 10 pieces are required for the component, the variable-size item quantity is: 10 * 0.06 SQM = 0.6 SQM.
    
    Parameters:
    
    qty_var_size_item - enter a variable-size item formula for the. calculation.
  - setRecord_creation_date
```
public void setRecord_creation_date(@Nullable
                                    LocalDateTime record_creation_date)
```
    Constraints: Not nullable, Precision: 0
    Original property from the Odata EDM: record_creation_date
    
    Parameters:
    
    record_creation_date -
  - setRecurisve
```
public void setRecurisve(@Nullable
                         Boolean recurisve)
```
    Constraints: none
    Original property from the Odata EDM: recurisve
    
    In BOM maintenanceyou can switch off the recursiveness check by setting the Recursiveness allowed indicatorrecursiveness is usually recognized online and prevented by an error messagein exceptional circumstances, recursiveness is not recognized until the BOM is updatedIn this case, the system sets the BOM is recursive indicator.Explosion path of BOM M10-----------------> |M10|| -----| / \| ---- ----| M3 M2| ---- ----| / \| ----- ------ |M10| M4----- ----
    
    Parameters:
    
    recurisve -
  - setRecurs_allowed
```
public void setRecurs_allowed(@Nullable
                              Boolean recurs_allowed)
```
    Constraints: none
    Original property from the Odata EDM: recurs_allowed
    
    If you set the Indicator: recursiveness allowed, no recursiveness check is made for the item concerned: you can create a recursive BOM.
    
    Parameters:
    
    recurs_allowed -
  - setReference_point
```
public void setReference_point(@Nullable
                               String reference_point)
```
    Constraints: Not nullable, Maximum length: 20
    Original property from the Odata EDM: reference_point
    
    Parameters:
    
    reference_point -
  - setRelevancy_to_costing
```
public void setRelevancy_to_costing(@Nullable
                                    String relevancy_to_costing)
```
    Constraints: Not nullable, Maximum length: 1
    Original property from the Odata EDM: relevancy_to_costing
    
    For the Standard Cost Estimate and the calculation of planned costs for a Work Order, this indicator specifies whether the item is included in costing.A BOM item or operation for which the indicator for relevancy to costing is X is fully relevant to costing.A BOM item or operation without an indicator for relevancy to costing is not relevant to costing at all.For Inventory Costing, you can link relevancy to costing indicators to factors for the fixed and variable costs so that the item values can be adjusted in costing depending on the valuation variant. You do this in Customizing for Product Cost Controlling.A BOM item or operation has the indicator for relevancy to costing A, which you have linked in Customizing for Product Cost Controlling to a fixed factor of 0.8 and a variable factor of 0.8. The BOM item or operation is costed in inventory costing at 80% of the fixed costs and 80% of the variable costs.For output materials (that is, materials for which the co-product indicator has been set in the material master and that have a negative BOM item), the relevance to costing indicator has no effect on the BOM item.The BOM usage that you selected on the initial screen determines whether this field is ready for input. For more information, see Customizing under Production -> Basic Data -> Bill of Material -> General Data -> BOM Usage -> Define BOM Usages.
    
    Parameters:
    
    relevancy_to_costing - costing.
  - setRelevant_to_sales
```
public void setRelevant_to_sales(@Nullable
                                 String relevant_to_sales)
```
    Constraints: Not nullable, Maximum length: 1
    Original property from the Odata EDM: relevant_to_sales
    
    For example, in sales order processing vor variant products, you see items that are relevant to sales as order items for the header material.This item status indicator is used to control:subsequent processing in related application areaswhich items are selected in the BOM explosionThe indicator does not interrupt the explosion of the BOM to the lowest lever. There are two steps to the BOM explosion:First, the system explodes the entire BOM, regardless of the indicators selected to restrict items. You do not see the result of this explosion on the screen.Second, the system reads the indicators selected to restrict items, such as the Relevant to sales indicator.This status indicator works as a filter. The explosion result you see on the screen only includes the items that fulfil the selection criteria. In this case, only the items that are relevant to sales are shown.
    
    Parameters:
    
    relevant_to_sales -
  - setRequired_component
```
public void setRequired_component(@Nullable
                                  Boolean required_component)
```
    Constraints: none
    Original property from the Odata EDM: required_component
    
    Parameters:
    
    required_component - interactive configuration: the configuration is incomplete until the class item has been replaced by an object. In low-level configuration (MRP, for example), the "Required component" indicator has no further effects.
  - setRequirement_segment
```
public void setRequirement_segment(@Nullable
                                   String requirement_segment)
```
    Constraints: Not nullable, Maximum length: 40
    Original property from the Odata EDM: requirement_segment
    
    Customer 1 accepts quality 1 and 2 while customer 2 accepts only quality 1. This results in 2 different requirement segments which can be assigned to different stock segments.
    
    Parameters:
    
    requirement_segment - segments are satisfied by which stock segments using segmentation strategies in the transaction Segmentation Strategy Maintenance .
  - setRevision_level
```
public void setRevision_level(@Nullable
                              String revision_level)
```
    Constraints: Not nullable, Maximum length: 2
    Original property from the Odata EDM: revision_level
    
    You can assign a revision level if you use a change number that has a specific valid-from date to make a change.Proceed as follows:Changing a MaterialYou can assign a revision level to a material when you process the material master record itself, or you can enter a revision level in the BOM header when you process a material BOM.Changing a DocumentYou define for each document type whether revision levels are active for documents. Define a document status that has the released indicator. As soon as you process a document of this document type with a change number and assign this status, a revision level is assigned automatically.Before you can assign a revision level, you must define the revisionlevel. From the main R/3 menu, choose Logistics -> Central functions -> Engineering change management, then Revision level -> Material rev. level or Revision level -> Document rev. level.To define how revision levels are assigned, go to Customizing step Set up control data.
    
    Parameters:
    
    revision_level -
  - setScrap_qty_bun
```
public void setScrap_qty_bun(@Nullable
                             BigDecimal scrap_qty_bun)
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    Original property from the Odata EDM: scrap_qty_bun
    
    Parameters:
    
    scrap_qty_bun -
  - setSerial_no_profile
```
public void setSerial_no_profile(@Nullable
                                 String serial_no_profile)
```
    Constraints: Not nullable, Maximum length: 4
    Original property from the Odata EDM: serial_no_profile
    
    Parameters:
    
    serial_no_profile -
  - setSize1
```
public void setSize1(@Nullable
                     BigDecimal size1)
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    Original property from the Odata EDM: size1
    
    Variable-size item data for a sheet of metal:Size Description Entry1 Length 2002 Width 300No. of variable-size items: 10Size unit: MMStockkeeping unit for sheet metalin material master: SQMCalculation of variable-size item quantity:A = Size 1 * Size 2A = 200 MM * 300 MMA = 60.000 SQMM--> Quantity of variable-size item per sheet: 0.06 SQM10 sheets are entered in the component, so the variable-size item requirement is:10 * 0.06 SQM = 0.6 SQM.
    
    Parameters:
    
    size1 -
  - setSize2
```
public void setSize2(@Nullable
                     BigDecimal size2)
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    Original property from the Odata EDM: size2
    
    Variable-size item data for a sheet of metal:Size Description Entry1 Length 2002 Width 300No. of variable-size items: 10Size unit: MMStockkeeping unit for sheet metalin material master: SQMCalculation of variable-size item quantity:A = Size 1 * Size 2A = 200 MM * 300 MMA = 60.000 SQMM--> Quantity of variable-size item per sheet: 0.06 SQM10 sheets are entered in the component, so the variable-size item requirement is:10 * 0.06 SQM = 0.6 SQM.
    
    Parameters:
    
    size2 -
  - setSize3
```
public void setSize3(@Nullable
                     BigDecimal size3)
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    Original property from the Odata EDM: size3
    
    Variable-size item data for a sheet of metal:Size Description Entry1 Length 2002 Width 300No. of variable-size items: 10Size unit: MMStockkeeping unit for sheet metalin material master: SQMCalculation of variable-size item quantity:A = Size 1 * Size 2A = 200 MM * 300 MMA = 60.000 SQMM--> Quantity of variable-size item per sheet: 0.06 SQM10 sheets are entered in the component, so the variable-size item requirement is:10 * 0.06 SQM = 0.6 SQM.
    
    Parameters:
    
    size3 -
  - setSize_unit
```
public void setSize_unit(@Nullable
                         String size_unit)
```
    Constraints: Not nullable, Maximum length: 3
    Original property from the Odata EDM: size_unit
    
    Please note:If you do not enter a unit of measure for the size, the system enters the default unit stored in the IMG for BOMs under Control data.The size unit and variable-size item unit are interdependent.Example:Variable-size item data for a metal sheet-----------------------------------------Size Dimension Entry1 Length 2002 Width 300Size unit for variable-size item: MMIf you do not enter a formula, the system uses the standard formula: Size 1 * Size 2 (result -> area).= 200 MM * 300 MM= 60,000 MM2Either the variable-size item unit must have the dimension area (MM2, CM2, M2, and so on), or conversion factors must be maintained in the material master.
    
    Parameters:
    
    size_unit -
  - setSoft_comp_indicator
```
public void setSoft_comp_indicator(@Nullable
                                   Boolean soft_comp_indicator)
```
    Constraints: none
    Original property from the Odata EDM: soft_comp_indicator
    
    Parameters:
    
    soft_comp_indicator -
  - setSort_string
```
public void setSort_string(@Nullable
                           String sort_string)
```
    Constraints: Not nullable, Maximum length: 10
    Original property from the Odata EDM: sort_string
    
    Parameters:
    
    sort_string -
  - setSpecial_procurement_type
```
public void setSpecial_procurement_type(@Nullable
                                        String special_procurement_type)
```
    Constraints: Not nullable, Maximum length: 2
    Original property from the Odata EDM: special_procurement_type
    
    You use special procurement when you want to be able to override the procurement type in the material master or define the procurement type more precisely.If the procurement type is in-house, you can nevertheless force the system to ignore the BOM and routing, and process the material as if it were externally procured, by specifying the special procurement as external.Enter the special procurement type to which you want to restrict the selection.If you procure a material externally, you may want to choose the special procurement type Consignment. If you produce the material in-house, it may be appropriate to choose Production in other plant.If a material has a routing but no BOM, it is treated as an externally procured material even if the procurement type is in-house. Both the BOM and the routing are ignored.However, if you specify the special procurement type as in-house, the routing is included even if the material has no BOM.
    
    Parameters:
    
    special_procurement_type - the material type.
  - setSpecial_proc_typ_itm
```
public void setSpecial_proc_typ_itm(@Nullable
                                    String special_proc_typ_itm)
```
    Constraints: Not nullable, Maximum length: 2
    Original property from the Odata EDM: special_proc_typ_itm
    
    Enter the special procurement type to which you want to restrict the selection.If you procure a material externally, you may want to choose the special procurement type Consignment. If you produce a material in-house, it may be appropriate to choose Production in other plant.
    
    Parameters:
    
    special_proc_typ_itm - material type.
  - setSpecial_proc_typ_mastr
```
public void setSpecial_proc_typ_mastr(@Nullable
                                      String special_proc_typ_mastr)
```
    Constraints: Not nullable, Maximum length: 2
    Original property from the Odata EDM: special_proc_typ_mastr
    
    Enter the special procurement type you want to restrict the selection to.For externally processed materials you can, for example, select the consignment order special procurement type. For in-house produced materials the production in another plant special procurement plant may be appropriate.
    
    Parameters:
    
    special_proc_typ_mastr - material type.
  - setSpec_proc_costing
```
public void setSpec_proc_costing(@Nullable
                                 String spec_proc_costing)
```
    Constraints: Not nullable, Maximum length: 2
    Original property from the Odata EDM: spec_proc_costing
    
    If you enter a special procurement type in the Costing view of the material master record, it is used in costing.If you do not enter a special procurement type in the costing view of the material master record, the system uses the special procurement type in the MRP view.If you want to cost a material as externally procured by ignoring the existing quantity structure in the system when costing, the following options are available:In the MRP view of the material master record, enter procurement type F and no special procurement type (neither in the MRP view nor in the Costing view).In Customizing for Product Cost Planning, create a new special procurement type (procurement type: F and special procurement type: blank) and enter this special procurement type in the material's Costing view.If you want to cost a material by ignoring the BOM but including the routing, go to Customizing for Product Cost Planning and create a new special procurement type (procurement type: E; special procurement type: E) and enter this special procurement type in the material's Costing view.
    
    Parameters:
    
    spec_proc_costing - detail for costing.
  - setStandard_price
```
public void setStandard_price(@Nullable
                              BigDecimal standard_price)
```
    Constraints: Not nullable, Precision: 12, Scale: 3
    Original property from the Odata EDM: standard_price
    
    The valuation of material stocks at standard prices means that all goods movements are valuated at the same price over an extended period.Price variances (for example, purchase price higher than standard price) upon goods receipt or invoice receipt are posted by the system to price difference accounts. This does not affect the standard price.
    
    Parameters:
    
    standard_price -
  - setStatus_text
```
public void setStatus_text(@Nullable
                           String status_text)
```
    Constraints: Not nullable, Maximum length: 16
    Original property from the Odata EDM: status_text
    
    Parameters:
    
    status_text -
  - setStock_segment
```
public void setStock_segment(@Nullable
                             String stock_segment)
```
    Constraints: Not nullable, Maximum length: 40
    Original property from the Odata EDM: stock_segment
    
    Parameters:
    
    stock_segment - the strategy is assigned to the material in the material master.
  - setStorage_location
```
public void setStorage_location(@Nullable
                                String storage_location)
```
    Constraints: Not nullable, Maximum length: 4
    Original property from the Odata EDM: storage_location
    
    Parameters:
    
    storage_location - locations.
  - setStrategy
```
public void setStrategy(@Nullable
                        String strategy)
```
    Constraints: Not nullable, Maximum length: 1
    Original property from the Odata EDM: strategy
    
    This strategy is ignored in material requirements planning (MRP).The withdrawal posting for the reservation in the production order can be selected as follows:According to usage probability (manual changes possible)For all items that you want to reserve, enter:Strategy (value 1 or no entry)Priority (only influences how materials are sorted)Usage probabilityWithdrawal if 100% availabilityFor all items that you want to reserve, enter:Strategy (value 2)PriorityIf you do not enter a priority, the system checks the items in the sequence in which they are transferred to the availability check.Usage probabilityEnter the same strategy for all alternative items in an alternative item group.Withdrawal if 100% availability (strategy 2)This strategy uses ATP logic to check availability in the defined ranking order.Gross requirements: 100 piecesM UP (%) RO RQ ATP qty Issue qtyA 20 1 20 30 0B 30 2 30 150 100C 50 3 50 180 0KeyM MaterialUP Usage probabilityRO Ranking orderRQ Requirements quantityThe first material in the ranking order that is supplied 100% on the requirement date is reserved in the required quantity (material B).If a partial withdrawal is carried out in a production order, when additional partial withdrawals take place, no further checks are carried out for this production order. Additional partial withdrawals result from the alternative item, from which the first withdrawal took place.If when using strategy 2 none of the alternative items cover the requirements 100%, the availability check for all items will confirm the available. A reservation only occurs for the available quantity.
    
    Parameters:
    
    strategy -
  - setSub_item_indicator
```
public void setSub_item_indicator(@Nullable
                                  Boolean sub_item_indicator)
```
    Constraints: none
    Original property from the Odata EDM: sub_item_indicator
    
    Sub-items do not have an operational significance and changes arenot stored with history.
    
    Parameters:
    
    sub_item_indicator -
  - setSupplier
```
public void setSupplier(@Nullable
                        String supplier)
```
    Constraints: Not nullable, Maximum length: 10
    Original property from the Odata EDM: supplier
    
    Parameters:
    
    supplier -
  - setTable_row
```
public void setTable_row(@Nullable
                         Integer table_row)
```
    Constraints: none
    Original property from the Odata EDM: table_row
    
    Parameters:
    
    table_row -
  - setTech_status_from
```
public void setTech_status_from(@Nullable
                                String tech_status_from)
```
    Constraints: Not nullable, Maximum length: 12
    Original property from the Odata EDM: tech_status_from
    
    All products produced in this phase are of the same type and option model.It can be used to describe the change statuses of a multi-level BOM which cannot be expressed in terms of an effectivity period (for example, lead-time offset).
    
    Parameters:
    
    tech_status_from -
  - setTest_hist_nxt_lvl
```
public void setTest_hist_nxt_lvl(@Nullable
                                 Boolean test_hist_nxt_lvl)
```
    Constraints: none
    Original property from the Odata EDM: test_hist_nxt_lvl
    
    Parameters:
    
    test_hist_nxt_lvl - created and/or changed. This change number defines the validity of the technical status.
  - setTotals_record_id
```
public void setTotals_record_id(@Nullable
                                String totals_record_id)
```
    Constraints: Not nullable, Maximum length: 1
    Original property from the Odata EDM: totals_record_id
    
    Parameters:
    
    totals_record_id -
  - setUnit_of_measure
```
public void setUnit_of_measure(@Nullable
                               String unit_of_measure)
```
    Constraints: Not nullable, Maximum length: 3
    Original property from the Odata EDM: unit_of_measure
    
    The system determines the unit as follows:Material items with a material master record - base unit of measure from the material master record.Class items - unit defined in the additional data of the class.Additional units for material items with a material master record:For material items, you can maintain alternative units of measure to the base unit of measure in the material master.In bills of material, not all alternative units of measure are taken into account - only the unit of issue.Possible values are:base unit of measureunit of issueunits of measure that have the same dimension as either the base unit of measure or the unit of issueIf you enter no unit, the system proposes a unit from the material master if the item has a material master:If the unit of issue was entered on the storage detail screen, the system copies this unit. Otherwise, it copies the base unit of measure.
    
    Parameters:
    
    unit_of_measure -
  - setUnloading_point
```
public void setUnloading_point(@Nullable
                               String unloading_point)
```
    Constraints: Not nullable, Maximum length: 25
    Original property from the Odata EDM: unloading_point
    
    Parameters:
    
    unloading_point -
  - setUom_usage
```
public void setUom_usage(@Nullable
                         String uom_usage)
```
    Constraints: Not nullable, Maximum length: 1
    Original property from the Odata EDM: uom_usage
    
    Proportion unitsProduct units
    
    Parameters:
    
    uom_usage - measure and the alternative units of measure. The following additional units of measurement are supported:
  - setUsage_probability
```
public void setUsage_probability(@Nullable
                                 BigDecimal usage_probability)
```
    Constraints: Not nullable, Precision: 3, Scale: 0
    Original property from the Odata EDM: usage_probability
    
    The usage probability is always taken into account for requirements planning.Maintain selected usage probabilityRequirements planning for alternative items is based on the usage probability.Quantities are suggested based on the usage probability for the withdrawal posting according to strategy 1. You can plan in excess for the alternative items since the usage probability is not limited to 100%. You can change the proposed quantities. Maintain no usage probability If you do not enter a usage probability, the alternative item just serves as information that can be evaluated, for example, in a situation with a missing part.You receive a warning since dependent requirements with 0 as quantity are created.Withdrawal based on usage probabilityStrategy: value 1An alternative item group is maintained for each assembly. This alternative item group contains four materials with differing usage probabilities. Dependent requirements are passed on with 100 as quantity.Material Usage probability (%) RequirementM-1 70 70M-2 20 20M-3 20 20M-4 0 no requirementIn this case, the materials are planned in excess since the sum of the usage probabilities is greater than 100%.
    
    Parameters:
    
    usage_probability -
  - setValidity_end_date
```
public void setValidity_end_date(@Nullable
                                 LocalDateTime validity_end_date)
```
    Constraints: Not nullable, Precision: 0
    Original property from the Odata EDM: validity_end_date
    
    Parameters:
    
    validity_end_date -
  - setValidity_start_date
```
public void setValidity_start_date(@Nullable
                                   LocalDateTime validity_start_date)
```
    Constraints: Not nullable, Precision: 0
    Original property from the Odata EDM: validity_start_date
    
    Parameters:
    
    validity_start_date -
  - setValuation_category
```
public void setValuation_category(@Nullable
                                  String valuation_category)
```
    Constraints: Not nullable, Maximum length: 1
    Original property from the Odata EDM: valuation_category
    
    In the case of split valuation, this indicator also determines which valuation types are allowed, that is, the criteria by which stocks can be valuated.
    
    Parameters:
    
    valuation_category -
  - setVariants_nxt_lvl
```
public void setVariants_nxt_lvl(@Nullable
                                Boolean variants_nxt_lvl)
```
    Constraints: none
    Original property from the Odata EDM: variants_nxt_lvl
    
    Only used internally for storing the technical type.
    
    Parameters:
    
    variants_nxt_lvl -
  - setX_plant_material_status
```
public void setX_plant_material_status(@Nullable
                                       String x_plant_material_status)
```
    Constraints: Not nullable, Maximum length: 2
    Original property from the Odata EDM: x_plant_material_status
    
    Materials management (for example, in purchasing and in inventory management)Production planning and controlPlant maintenanceWarehouse managementCosting with a quantity structureThe cross-plant material status restricts the usability of the material for all plants, that is, it defines whether a warning or error message is displayed if you include the material in a particular function.The material may be a part under development or one to be discontinued.
    
    Parameters:
    
    x_plant_material_status -
  - setX_plt_status_valid_from
```
public void setX_plt_status_valid_from(@Nullable
                                       LocalDateTime x_plt_status_valid_from)
```
    Constraints: Not nullable, Precision: 0
    Original property from the Odata EDM: x_plt_status_valid_from
    
    The valid-from date of the material status is considered only if it precedes or is the same as the planning date; that is, if the valid-from date is later than the planning date, it is not considered, even if it is within the planning horizon.ExampleI<-------------Planning horizon------------->I-----I--------------------I-----------------------I-->Planning date Valid-from date TimeIn this case, the valid-from date is not considered in materials planning since it is later than the planning date.PurchasingThe valid-from date of the material status is checked against the current date.ExampleYou block the material for purchasing from May 1, xxxx. A purchase order is created for the material on April 28, xxxx with a delivery date of May 10, xxxx. In this case, the valid-from date May 1, xxxx is checked against the purchase order date April 28, xxxx and the purchase order is allowed. Had you created the purchase order on May 3, xxxx, an error message would have been issued.
    
    Parameters:
    
    x_plt_status_valid_from -
  - toString
```
public String toString()
```
    Overrides:
    
    toString in class VdmObject<DBomheaderforexplosionOut>
  - equals
```
public boolean equals(Object o)
```
    Overrides:
    
    equals in class VdmObject<DBomheaderforexplosionOut>
  - canEqual
```
protected boolean canEqual(Object other)
```
    Overrides:
    
    canEqual in class VdmObject<DBomheaderforexplosionOut>
  - hashCode
```
public int hashCode()
```
    Overrides:
    
    hashCode in class VdmObject<DBomheaderforexplosionOut>

Class DBomheaderforexplosionOut

Nested Class Summary

Field Summary

Fields inherited from class com.sap.cloud.sdk.datamodel.odata.helper.VdmObject

Constructor Summary

Method Summary

Methods inherited from class com.sap.cloud.sdk.datamodel.odata.helper.VdmObject

Methods inherited from class java.lang.Object

Constructor Detail

DBomheaderforexplosionOut

DBomheaderforexplosionOut

Method Detail

getType

toMapOfFields

fromMap

getKey

builder

getAlternative_item

getAlt_item_group

getAlt_nxt_lvl

getAssembly_indicator

getAssign_effect_vals

getAssy_scrap_itm_mat

getAs_selection_cond

getBase_qty_nxt_lvl

getBase_unit_nxt_lvl

getBase_uom

getBatch_entry

getBatch_mgmt

getBill_of_material

getBill_of_material_base_quant

getBill_of_material_component

getBill_of_material_comp_quant

getBill_of_material_item_category

getBill_of_material_item_number

getBill_of_material_item_quantity

getBill_of_material_item_unit

getBill_Of_Material_Root

getBill_of_material_root_variant

getBill_of_material_variant

getBill_of_material_variant_usage

getBom_change_number

getBulk_material

getB_o_m_alternative_text

getB_o_m_alt_nxt_lvl

getB_o_m_category

getB_o_m_cat_nxt_lvl

getB_o_m_component_description

getB_o_m_explosion_level

getB_o_m_hdr_matl_hier_node

getB_O_M_Hdr_Root_Matl_Hier_Node

getB_o_m_header_base_unit

getB_o_m_header_quantity_primary

getB_o_m_item_description

getB_o_m_item_is_discontinued

getB_o_m_no_nxt_lvl

getB_o_m_usage_nxt_lvl

getChange_number

getChg_to_eng_chg_number

getClassProperty

getClassification

getClass_type

getCommodity_code

getComp_maint_status

getComp_scrap_itm

getComp_scrap_itm_mat

getConfig_mat_var

getConfig_multi_level

getConf_bom_nxt_lvl

getCost_element

getCounter

getCo_product

getCreated_by_user

getCurrency

getCustoms_preference

getDat_hist_nxt_lvl

getDeletion_indicator

getDelivery_time_in_days

getDel_Ind_nxt_lvl

getDenominator