Tree for BOMs

I'm trying to create a tree for Bill of Materials from Oracle Applications 11.5.10. In other words, I'd like to create a HTML DB report that simply shows a BOM in a tree format that someone can explode/collapse/view. I use the following SQL code right now to display it. I hard-code the "assembly_item_id" to run this ad-hoc, currently.
select bic.component_item_id Component ,
msi.segment1 Name,
msi.description Description,
bic.component_quantity Quantity,
lpad( ' ', level*2 ) || level
from bom_bill_of_materials bbm
,bom_inventory_components bic
, mtl_system_items msi
where bbm.bill_Sequence_id = bic.bill_sequence_id
and msi.inventory_item_id = bic.component_item_id
and msi.organization_id = bbm.organization_id
start with bbm.assembly_item_id = 271962
and bbm.organization_id = 85
connect by prior bic.component_item_id = bbm.assembly_item_id;
Anyway, is there a way to create a tree in HTML DB from this data?
Thanks!
Steve

Earl,
You're so cool to help me out - here you go:
DBMS_METADATA.GET_DDL('TABLE','BOM_STRUCTURES_B','BOM')
CREATE TABLE "BOM"."BOM_STRUCTURES_B"
(     "ASSEMBLY_ITEM_ID" NUMBER,
     "ORGANIZATION_ID" NUMBER NOT NULL ENABLE,
     "ALTERNATE_BOM_DESIGNATOR" VARCHAR2(10),
     "LAST_UPDATE_DATE" DATE NOT NULL ENABLE,
     "LAST_UPDATED_BY" NUMBER NOT NULL ENABLE,
     "CREATION_DATE" DATE NOT NULL ENABLE,
     "CREATED_BY" NUMBER NOT NULL ENABLE,
     "LAST_UPDATE_LOGIN" NUMBER,
     "COMMON_ASSEMBLY_ITEM_ID" NUMBER,
     "SPECIFIC_ASSEMBLY_COMMENT" VARCHAR2(240),
     "PENDING_FROM_ECN" VARCHAR2(10),
     "ATTRIBUTE_CATEGORY" VARCHAR2(30),
     "ATTRIBUTE1" VARCHAR2(150),
     "ATTRIBUTE2" VARCHAR2(150),
     "ATTRIBUTE3" VARCHAR2(150),
     "ATTRIBUTE4" VARCHAR2(150),
     "ATTRIBUTE5" VARCHAR2(150),
     "ATTRIBUTE6" VARCHAR2(150),
     "ATTRIBUTE7" VARCHAR2(150),
     "ATTRIBUTE8" VARCHAR2(150),
     "ATTRIBUTE9" VARCHAR2(150),
     "ATTRIBUTE10" VARCHAR2(150),
     "ATTRIBUTE11" VARCHAR2(150),
     "ATTRIBUTE12" VARCHAR2(150),
     "ATTRIBUTE13" VARCHAR2(150),
     "ATTRIBUTE14" VARCHAR2(150),
     "ATTRIBUTE15" VARCHAR2(150),
     "ASSEMBLY_TYPE" NUMBER NOT NULL ENABLE,
     "COMMON_BILL_SEQUENCE_ID" NUMBER NOT NULL ENABLE,
     "BILL_SEQUENCE_ID" NUMBER NOT NULL ENABLE,
     "REQUEST_ID" NUMBER,
     "PROGRAM_APPLICATION_ID" NUMBER,
     "PROGRAM_ID" NUMBER,
     "PROGRAM_UPDATE_DATE" DATE,
     "COMMON_ORGANIZATION_ID" NUMBER,
     "NEXT_EXPLODE_DATE" DATE,
     "PROJECT_ID" NUMBER,
     "TASK_ID" NUMBER,
     "ORIGINAL_SYSTEM_REFERENCE" VARCHAR2(50),
     "STRUCTURE_TYPE_ID" NUMBER,
     "IMPLEMENTATION_DATE" DATE,
     "OBJ_NAME" VARCHAR2(30),
     "PK1_VALUE" VARCHAR2(240),
     "PK2_VALUE" VARCHAR2(240),
     "PK3_VALUE" VARCHAR2(240),
     "PK4_VALUE" VARCHAR2(240),
     "PK5_VALUE" VARCHAR2(240),
     "EFFECTIVITY_CONTROL" NUMBER,
     "IS_PREFERRED" VARCHAR2(1)
) PCTFREE 20 PCTUSED 80 INITRANS 10 MAXTRANS 255 NOCOMPRESS LOGGING
STORAGE(INITIAL 131072 NEXT 131072 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 4 FREELIST GROUPS 4 BUFFER_POOL DEFAULT)
TABLESPACE "APPS_TS_TX_DATA"
DBMS_METADATA.GET_DDL('TABLE','BOM_COMPONENTS_B','BOM')
CREATE TABLE "BOM"."BOM_COMPONENTS_B"
(     "OPERATION_SEQ_NUM" NUMBER NOT NULL ENABLE,
     "COMPONENT_ITEM_ID" NUMBER,
     "LAST_UPDATE_DATE" DATE NOT NULL ENABLE,
     "LAST_UPDATED_BY" NUMBER NOT NULL ENABLE,
     "CREATION_DATE" DATE NOT NULL ENABLE,
     "CREATED_BY" NUMBER NOT NULL ENABLE,
     "LAST_UPDATE_LOGIN" NUMBER,
     "ITEM_NUM" NUMBER,
     "COMPONENT_QUANTITY" NUMBER NOT NULL ENABLE,
     "COMPONENT_YIELD_FACTOR" NUMBER NOT NULL ENABLE,
     "COMPONENT_REMARKS" VARCHAR2(240),
     "EFFECTIVITY_DATE" DATE NOT NULL ENABLE,
     "CHANGE_NOTICE" VARCHAR2(10),
     "IMPLEMENTATION_DATE" DATE,
     "DISABLE_DATE" DATE,
     "ATTRIBUTE_CATEGORY" VARCHAR2(30),
     "ATTRIBUTE1" VARCHAR2(150),
     "ATTRIBUTE2" VARCHAR2(150),
     "ATTRIBUTE3" VARCHAR2(150),
     "ATTRIBUTE4" VARCHAR2(150),
     "ATTRIBUTE5" VARCHAR2(150),
     "ATTRIBUTE6" VARCHAR2(150),
     "ATTRIBUTE7" VARCHAR2(150),
     "ATTRIBUTE8" VARCHAR2(150),
     "ATTRIBUTE9" VARCHAR2(150),
     "ATTRIBUTE10" VARCHAR2(150),
     "ATTRIBUTE11" VARCHAR2(150),
     "ATTRIBUTE12" VARCHAR2(150),
     "ATTRIBUTE13" VARCHAR2(150),
     "ATTRIBUTE14" VARCHAR2(150),
     "ATTRIBUTE15" VARCHAR2(150),
     "PLANNING_FACTOR" NUMBER NOT NULL ENABLE,
     "QUANTITY_RELATED" NUMBER NOT NULL ENABLE,
     "SO_BASIS" NUMBER,
     "OPTIONAL" NUMBER,
     "MUTUALLY_EXCLUSIVE_OPTIONS" NUMBER,
     "INCLUDE_IN_COST_ROLLUP" NUMBER NOT NULL ENABLE,
     "CHECK_ATP" NUMBER NOT NULL ENABLE,
     "SHIPPING_ALLOWED" NUMBER,
     "REQUIRED_TO_SHIP" NUMBER,
     "REQUIRED_FOR_REVENUE" NUMBER,
     "INCLUDE_ON_SHIP_DOCS" NUMBER,
     "INCLUDE_ON_BILL_DOCS" NUMBER,
     "LOW_QUANTITY" NUMBER,
     "HIGH_QUANTITY" NUMBER,
     "ACD_TYPE" NUMBER,
     "OLD_COMPONENT_SEQUENCE_ID" NUMBER,
     "COMPONENT_SEQUENCE_ID" NUMBER NOT NULL ENABLE,
     "BILL_SEQUENCE_ID" NUMBER NOT NULL ENABLE,
     "REQUEST_ID" NUMBER,
     "PROGRAM_APPLICATION_ID" NUMBER,
     "PROGRAM_ID" NUMBER,
     "PROGRAM_UPDATE_DATE" DATE,
     "WIP_SUPPLY_TYPE" NUMBER,
     "PICK_COMPONENTS" NUMBER,
     "SUPPLY_SUBINVENTORY" VARCHAR2(10),
     "SUPPLY_LOCATOR_ID" NUMBER,
     "OPERATION_LEAD_TIME_PERCENT" NUMBER,
     "REVISED_ITEM_SEQUENCE_ID" NUMBER,
     "COST_FACTOR" NUMBER,
     "BOM_ITEM_TYPE" NUMBER,
     "FROM_END_ITEM_UNIT_NUMBER" VARCHAR2(30),
     "TO_END_ITEM_UNIT_NUMBER" VARCHAR2(30),
     "ORIGINAL_SYSTEM_REFERENCE" VARCHAR2(50),
     "ECO_FOR_PRODUCTION" NUMBER,
     "ENFORCE_INT_REQUIREMENTS" NUMBER,
     "COMPONENT_ITEM_REVISION_ID" NUMBER,
     "DELETE_GROUP_NAME" VARCHAR2(10),
     "DG_DESCRIPTION" VARCHAR2(240),
     "OPTIONAL_ON_MODEL" NUMBER,
     "PARENT_BILL_SEQ_ID" NUMBER,
     "MODEL_COMP_SEQ_ID" NUMBER,
     "PLAN_LEVEL" NUMBER,
     "FROM_BILL_REVISION_ID" NUMBER,
     "TO_BILL_REVISION_ID" NUMBER,
     "AUTO_REQUEST_MATERIAL" VARCHAR2(1),
     "SUGGESTED_VENDOR_NAME" VARCHAR2(240),
     "VENDOR_ID" NUMBER,
     "UNIT_PRICE" NUMBER,
     "OBJ_NAME" VARCHAR2(30),
     "PK1_VALUE" VARCHAR2(240),
     "PK2_VALUE" VARCHAR2(240),
     "PK3_VALUE" VARCHAR2(240),
     "PK4_VALUE" VARCHAR2(240),
     "PK5_VALUE" VARCHAR2(240),
     "FROM_END_ITEM_REV_ID" NUMBER,
     "TO_END_ITEM_REV_ID" NUMBER,
     "OVERLAPPING_CHANGES" NUMBER,
     "FROM_OBJECT_REVISION_ID" NUMBER,
     "FROM_MINOR_REVISION_ID" NUMBER,
     "TO_OBJECT_REVISION_ID" NUMBER,
     "TO_MINOR_REVISION_ID" NUMBER,
     "FROM_END_ITEM_MINOR_REV_ID" NUMBER,
     "TO_END_ITEM_MINOR_REV_ID" NUMBER,
     "COMPONENT_MINOR_REVISION_ID" NUMBER,
     "FROM_STRUCTURE_REVISION_CODE" VARCHAR2(30),
     "TO_STRUCTURE_REVISION_CODE" VARCHAR2(30),
     "FROM_END_ITEM_STRC_REV_ID" NUMBER,
     "TO_END_ITEM_STRC_REV_ID" NUMBER
) PCTFREE 35 PCTUSED 50 INITRANS 10 MAXTRANS 255 NOCOMPRESS LOGGING
STORAGE(INITIAL 131072 NEXT 131072 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 4 FREELIST GROUPS 4 BUFFER_POOL DEFAULT)
TABLESPACE "APPS_TS_TX_DATA"
DBMS_METADATA.GET_DDL('TABLE','MTL_SYSTEM_ITEMS_B','INV')
CREATE TABLE "INV"."MTL_SYSTEM_ITEMS_B"
(     "INVENTORY_ITEM_ID" NUMBER NOT NULL ENABLE,
     "ORGANIZATION_ID" NUMBER NOT NULL ENABLE,
     "LAST_UPDATE_DATE" DATE NOT NULL ENABLE,
     "LAST_UPDATED_BY" NUMBER NOT NULL ENABLE,
     "CREATION_DATE" DATE NOT NULL ENABLE,
     "CREATED_BY" NUMBER NOT NULL ENABLE,
     "LAST_UPDATE_LOGIN" NUMBER,
     "SUMMARY_FLAG" VARCHAR2(1) NOT NULL ENABLE,
     "ENABLED_FLAG" VARCHAR2(1) NOT NULL ENABLE,
     "START_DATE_ACTIVE" DATE,
     "END_DATE_ACTIVE" DATE,
     "DESCRIPTION" VARCHAR2(240),
     "BUYER_ID" NUMBER(9,0),
     "ACCOUNTING_RULE_ID" NUMBER,
     "INVOICING_RULE_ID" NUMBER,
     "SEGMENT1" VARCHAR2(40),
     "SEGMENT2" VARCHAR2(40),
     "SEGMENT3" VARCHAR2(40),
     "SEGMENT4" VARCHAR2(40),
     "SEGMENT5" VARCHAR2(40),
     "SEGMENT6" VARCHAR2(40),
     "SEGMENT7" VARCHAR2(40),
     "SEGMENT8" VARCHAR2(40),
     "SEGMENT9" VARCHAR2(40),
     "SEGMENT10" VARCHAR2(40),
     "SEGMENT11" VARCHAR2(40),
     "SEGMENT12" VARCHAR2(40),
     "SEGMENT13" VARCHAR2(40),
     "SEGMENT14" VARCHAR2(40),
     "SEGMENT15" VARCHAR2(40),
     "SEGMENT16" VARCHAR2(40),
     "SEGMENT17" VARCHAR2(40),
     "SEGMENT18" VARCHAR2(40),
     "SEGMENT19" VARCHAR2(40),
     "SEGMENT20" VARCHAR2(40),
     "ATTRIBUTE_CATEGORY" VARCHAR2(30),
     "ATTRIBUTE1" VARCHAR2(240),
     "ATTRIBUTE2" VARCHAR2(240),
     "ATTRIBUTE3" VARCHAR2(240),
     "ATTRIBUTE4" VARCHAR2(240),
     "ATTRIBUTE5" VARCHAR2(240),
     "ATTRIBUTE6" VARCHAR2(240),
     "ATTRIBUTE7" VARCHAR2(240),
     "ATTRIBUTE8" VARCHAR2(240),
     "ATTRIBUTE9" VARCHAR2(240),
     "ATTRIBUTE10" VARCHAR2(240),
     "ATTRIBUTE11" VARCHAR2(240),
     "ATTRIBUTE12" VARCHAR2(240),
     "ATTRIBUTE13" VARCHAR2(240),
     "ATTRIBUTE14" VARCHAR2(240),
     "ATTRIBUTE15" VARCHAR2(240),
     "PURCHASING_ITEM_FLAG" VARCHAR2(1) NOT NULL ENABLE,
     "SHIPPABLE_ITEM_FLAG" VARCHAR2(1) NOT NULL ENABLE,
     "CUSTOMER_ORDER_FLAG" VARCHAR2(1) NOT NULL ENABLE,
     "INTERNAL_ORDER_FLAG" VARCHAR2(1) NOT NULL ENABLE,
     "SERVICE_ITEM_FLAG" VARCHAR2(1) NOT NULL ENABLE,
     "INVENTORY_ITEM_FLAG" VARCHAR2(1) NOT NULL ENABLE,
     "ENG_ITEM_FLAG" VARCHAR2(1) NOT NULL ENABLE,
     "INVENTORY_ASSET_FLAG" VARCHAR2(1) NOT NULL ENABLE,
     "PURCHASING_ENABLED_FLAG" VARCHAR2(1) NOT NULL ENABLE,
     "CUSTOMER_ORDER_ENABLED_FLAG" VARCHAR2(1) NOT NULL ENABLE,
     "INTERNAL_ORDER_ENABLED_FLAG" VARCHAR2(1) NOT NULL ENABLE,
     "SO_TRANSACTIONS_FLAG" VARCHAR2(1) NOT NULL ENABLE,
     "MTL_TRANSACTIONS_ENABLED_FLAG" VARCHAR2(1) NOT NULL ENABLE,
     "STOCK_ENABLED_FLAG" VARCHAR2(1) NOT NULL ENABLE,
     "BOM_ENABLED_FLAG" VARCHAR2(1) NOT NULL ENABLE,
     "BUILD_IN_WIP_FLAG" VARCHAR2(1) NOT NULL ENABLE,
     "REVISION_QTY_CONTROL_CODE" NUMBER,
     "ITEM_CATALOG_GROUP_ID" NUMBER,
     "CATALOG_STATUS_FLAG" VARCHAR2(1),
     "RETURNABLE_FLAG" VARCHAR2(1),
     "DEFAULT_SHIPPING_ORG" NUMBER,
     "COLLATERAL_FLAG" VARCHAR2(1),
     "TAXABLE_FLAG" VARCHAR2(1),
     "QTY_RCV_EXCEPTION_CODE" VARCHAR2(25),
     "ALLOW_ITEM_DESC_UPDATE_FLAG" VARCHAR2(1),
     "INSPECTION_REQUIRED_FLAG" VARCHAR2(1),
     "RECEIPT_REQUIRED_FLAG" VARCHAR2(1),
     "MARKET_PRICE" NUMBER,
     "HAZARD_CLASS_ID" NUMBER,
     "RFQ_REQUIRED_FLAG" VARCHAR2(1),
     "QTY_RCV_TOLERANCE" NUMBER,
     "LIST_PRICE_PER_UNIT" NUMBER,
     "UN_NUMBER_ID" NUMBER,
     "PRICE_TOLERANCE_PERCENT" NUMBER,
     "ASSET_CATEGORY_ID" NUMBER,
     "ROUNDING_FACTOR" NUMBER,
     "UNIT_OF_ISSUE" VARCHAR2(25),
     "ENFORCE_SHIP_TO_LOCATION_CODE" VARCHAR2(25),
     "ALLOW_SUBSTITUTE_RECEIPTS_FLAG" VARCHAR2(1),
     "ALLOW_UNORDERED_RECEIPTS_FLAG" VARCHAR2(1),
     "ALLOW_EXPRESS_DELIVERY_FLAG" VARCHAR2(1),
     "DAYS_EARLY_RECEIPT_ALLOWED" NUMBER,
     "DAYS_LATE_RECEIPT_ALLOWED" NUMBER,
     "RECEIPT_DAYS_EXCEPTION_CODE" VARCHAR2(25),
     "RECEIVING_ROUTING_ID" NUMBER,
     "INVOICE_CLOSE_TOLERANCE" NUMBER,
     "RECEIVE_CLOSE_TOLERANCE" NUMBER,
     "AUTO_LOT_ALPHA_PREFIX" VARCHAR2(30),
     "START_AUTO_LOT_NUMBER" VARCHAR2(30),
     "LOT_CONTROL_CODE" NUMBER,
     "SHELF_LIFE_CODE" NUMBER,
     "SHELF_LIFE_DAYS" NUMBER,
     "SERIAL_NUMBER_CONTROL_CODE" NUMBER,
     "START_AUTO_SERIAL_NUMBER" VARCHAR2(30),
     "AUTO_SERIAL_ALPHA_PREFIX" VARCHAR2(30),
     "SOURCE_TYPE" NUMBER,
     "SOURCE_ORGANIZATION_ID" NUMBER,
     "SOURCE_SUBINVENTORY" VARCHAR2(10),
     "EXPENSE_ACCOUNT" NUMBER,
     "ENCUMBRANCE_ACCOUNT" NUMBER,
     "RESTRICT_SUBINVENTORIES_CODE" NUMBER,
     "UNIT_WEIGHT" NUMBER,
     "WEIGHT_UOM_CODE" VARCHAR2(3),
     "VOLUME_UOM_CODE" VARCHAR2(3),
     "UNIT_VOLUME" NUMBER,
     "RESTRICT_LOCATORS_CODE" NUMBER,
     "LOCATION_CONTROL_CODE" NUMBER,
     "SHRINKAGE_RATE" NUMBER,
     "ACCEPTABLE_EARLY_DAYS" NUMBER,
     "PLANNING_TIME_FENCE_CODE" NUMBER,
     "DEMAND_TIME_FENCE_CODE" NUMBER,
     "LEAD_TIME_LOT_SIZE" NUMBER,
     "STD_LOT_SIZE" NUMBER,
     "CUM_MANUFACTURING_LEAD_TIME" NUMBER,
     "OVERRUN_PERCENTAGE" NUMBER,
     "MRP_CALCULATE_ATP_FLAG" VARCHAR2(1),
     "ACCEPTABLE_RATE_INCREASE" NUMBER,
     "ACCEPTABLE_RATE_DECREASE" NUMBER,
     "CUMULATIVE_TOTAL_LEAD_TIME" NUMBER,
     "PLANNING_TIME_FENCE_DAYS" NUMBER,
     "DEMAND_TIME_FENCE_DAYS" NUMBER,
     "END_ASSEMBLY_PEGGING_FLAG" VARCHAR2(1),
     "REPETITIVE_PLANNING_FLAG" VARCHAR2(1),
     "PLANNING_EXCEPTION_SET" VARCHAR2(10),
     "BOM_ITEM_TYPE" NUMBER NOT NULL ENABLE,
     "PICK_COMPONENTS_FLAG" VARCHAR2(1) NOT NULL ENABLE,
     "REPLENISH_TO_ORDER_FLAG" VARCHAR2(1) NOT NULL ENABLE,
     "BASE_ITEM_ID" NUMBER,
     "ATP_COMPONENTS_FLAG" VARCHAR2(1) NOT NULL ENABLE,
     "ATP_FLAG" VARCHAR2(1) NOT NULL ENABLE,
     "FIXED_LEAD_TIME" NUMBER,
     "VARIABLE_LEAD_TIME" NUMBER,
     "WIP_SUPPLY_LOCATOR_ID" NUMBER,
     "WIP_SUPPLY_TYPE" NUMBER,
     "WIP_SUPPLY_SUBINVENTORY" VARCHAR2(10),
     "PRIMARY_UOM_CODE" VARCHAR2(3),
     "PRIMARY_UNIT_OF_MEASURE" VARCHAR2(25),
     "ALLOWED_UNITS_LOOKUP_CODE" NUMBER,
     "COST_OF_SALES_ACCOUNT" NUMBER,
     "SALES_ACCOUNT" NUMBER,
     "DEFAULT_INCLUDE_IN_ROLLUP_FLAG" VARCHAR2(1),
     "INVENTORY_ITEM_STATUS_CODE" VARCHAR2(10) NOT NULL ENABLE,
     "INVENTORY_PLANNING_CODE" NUMBER,
     "PLANNER_CODE" VARCHAR2(10),
     "PLANNING_MAKE_BUY_CODE" NUMBER,
     "FIXED_LOT_MULTIPLIER" NUMBER,
     "ROUNDING_CONTROL_TYPE" NUMBER,
     "CARRYING_COST" NUMBER,
     "POSTPROCESSING_LEAD_TIME" NUMBER,
     "PREPROCESSING_LEAD_TIME" NUMBER,
     "FULL_LEAD_TIME" NUMBER,
     "ORDER_COST" NUMBER,
     "MRP_SAFETY_STOCK_PERCENT" NUMBER,
     "MRP_SAFETY_STOCK_CODE" NUMBER,
     "MIN_MINMAX_QUANTITY" NUMBER,
     "MAX_MINMAX_QUANTITY" NUMBER,
     "MINIMUM_ORDER_QUANTITY" NUMBER,
     "FIXED_ORDER_QUANTITY" NUMBER,
     "FIXED_DAYS_SUPPLY" NUMBER,
     "MAXIMUM_ORDER_QUANTITY" NUMBER,
     "ATP_RULE_ID" NUMBER,
     "PICKING_RULE_ID" NUMBER,
     "RESERVABLE_TYPE" NUMBER,
     "POSITIVE_MEASUREMENT_ERROR" NUMBER,
     "NEGATIVE_MEASUREMENT_ERROR" NUMBER,
     "ENGINEERING_ECN_CODE" VARCHAR2(50),
     "ENGINEERING_ITEM_ID" NUMBER,
     "ENGINEERING_DATE" DATE,
     "SERVICE_STARTING_DELAY" NUMBER,
     "VENDOR_WARRANTY_FLAG" VARCHAR2(1) NOT NULL ENABLE,
     "SERVICEABLE_COMPONENT_FLAG" VARCHAR2(1),
     "SERVICEABLE_PRODUCT_FLAG" VARCHAR2(1) NOT NULL ENABLE,
     "BASE_WARRANTY_SERVICE_ID" NUMBER,
     "PAYMENT_TERMS_ID" NUMBER,
     "PREVENTIVE_MAINTENANCE_FLAG" VARCHAR2(1),
     "PRIMARY_SPECIALIST_ID" NUMBER,
     "SECONDARY_SPECIALIST_ID" NUMBER,
     "SERVICEABLE_ITEM_CLASS_ID" NUMBER,
     "TIME_BILLABLE_FLAG" VARCHAR2(1),
     "MATERIAL_BILLABLE_FLAG" VARCHAR2(30),
     "EXPENSE_BILLABLE_FLAG" VARCHAR2(1),
     "PRORATE_SERVICE_FLAG" VARCHAR2(1),
     "COVERAGE_SCHEDULE_ID" NUMBER,
     "SERVICE_DURATION_PERIOD_CODE" VARCHAR2(10),
     "SERVICE_DURATION" NUMBER,
     "WARRANTY_VENDOR_ID" NUMBER,
     "MAX_WARRANTY_AMOUNT" NUMBER,
     "RESPONSE_TIME_PERIOD_CODE" VARCHAR2(30),
     "RESPONSE_TIME_VALUE" NUMBER,
     "NEW_REVISION_CODE" VARCHAR2(30),
     "INVOICEABLE_ITEM_FLAG" VARCHAR2(1) NOT NULL ENABLE,
     "TAX_CODE" VARCHAR2(50),
     "INVOICE_ENABLED_FLAG" VARCHAR2(1) NOT NULL ENABLE,
     "MUST_USE_APPROVED_VENDOR_FLAG" VARCHAR2(1) NOT NULL ENABLE,
     "REQUEST_ID" NUMBER,
     "PROGRAM_APPLICATION_ID" NUMBER,
     "PROGRAM_ID" NUMBER,
     "PROGRAM_UPDATE_DATE" DATE,
     "OUTSIDE_OPERATION_FLAG" VARCHAR2(1) NOT NULL ENABLE,
     "OUTSIDE_OPERATION_UOM_TYPE" VARCHAR2(25),
     "SAFETY_STOCK_BUCKET_DAYS" NUMBER,
     "AUTO_REDUCE_MPS" NUMBER(22,0),
     "COSTING_ENABLED_FLAG" VARCHAR2(1) NOT NULL ENABLE,
     "AUTO_CREATED_CONFIG_FLAG" VARCHAR2(1) NOT NULL ENABLE,
     "CYCLE_COUNT_ENABLED_FLAG" VARCHAR2(1) NOT NULL ENABLE,
     "ITEM_TYPE" VARCHAR2(30),
     "MODEL_CONFIG_CLAUSE_NAME" VARCHAR2(10),
     "SHIP_MODEL_COMPLETE_FLAG" VARCHAR2(1),
     "MRP_PLANNING_CODE" NUMBER,
     "RETURN_INSPECTION_REQUIREMENT" NUMBER,
     "ATO_FORECAST_CONTROL" NUMBER,
     "RELEASE_TIME_FENCE_CODE" NUMBER,
     "RELEASE_TIME_FENCE_DAYS" NUMBER,
     "CONTAINER_ITEM_FLAG" VARCHAR2(1),
     "VEHICLE_ITEM_FLAG" VARCHAR2(1),
     "MAXIMUM_LOAD_WEIGHT" NUMBER,
     "MINIMUM_FILL_PERCENT" NUMBER,
     "CONTAINER_TYPE_CODE" VARCHAR2(30),
     "INTERNAL_VOLUME" NUMBER,
     "WH_UPDATE_DATE" DATE,
     "PRODUCT_FAMILY_ITEM_ID" NUMBER,
     "GLOBAL_ATTRIBUTE_CATEGORY" VARCHAR2(150),
     "GLOBAL_ATTRIBUTE1" VARCHAR2(150),
     "GLOBAL_ATTRIBUTE2" VARCHAR2(150),
     "GLOBAL_ATTRIBUTE3" VARCHAR2(150),
     "GLOBAL_ATTRIBUTE4" VARCHAR2(150),
     "GLOBAL_ATTRIBUTE5" VARCHAR2(150),
     "GLOBAL_ATTRIBUTE6" VARCHAR2(150),
     "GLOBAL_ATTRIBUTE7" VARCHAR2(150),
     "GLOBAL_ATTRIBUTE8" VARCHAR2(150),
     "GLOBAL_ATTRIBUTE9" VARCHAR2(150),
     "GLOBAL_ATTRIBUTE10" VARCHAR2(150),
     "PURCHASING_TAX_CODE" VARCHAR2(50),
     "OVERCOMPLETION_TOLERANCE_TYPE" NUMBER,
     "OVERCOMPLETION_TOLERANCE_VALUE" NUMBER,
     "EFFECTIVITY_CONTROL" NUMBER,
     "CHECK_SHORTAGES_FLAG" VARCHAR2(1),
     "OVER_SHIPMENT_TOLERANCE" NUMBER,
     "UNDER_SHIPMENT_TOLERANCE" NUMBER,
     "OVER_RETURN_TOLERANCE" NUMBER,
     "UNDER_RETURN_TOLERANCE" NUMBER,
     "EQUIPMENT_TYPE" NUMBER,
     "RECOVERED_PART_DISP_CODE" VARCHAR2(30),
     "DEFECT_TRACKING_ON_FLAG" VARCHAR2(1),
     "USAGE_ITEM_FLAG" VARCHAR2(1),
     "EVENT_FLAG" VARCHAR2(1),
     "ELECTRONIC_FLAG" VARCHAR2(1),
     "DOWNLOADABLE_FLAG" VARCHAR2(1),
     "VOL_DISCOUNT_EXEMPT_FLAG" VARCHAR2(1),
     "COUPON_EXEMPT_FLAG" VARCHAR2(1),
     "COMMS_NL_TRACKABLE_FLAG" VARCHAR2(1),
     "ASSET_CREATION_CODE" VARCHAR2(30),
     "COMMS_ACTIVATION_REQD_FLAG" VARCHAR2(1),
     "ORDERABLE_ON_WEB_FLAG" VARCHAR2(1),
     "BACK_ORDERABLE_FLAG" VARCHAR2(1),
     "WEB_STATUS" VARCHAR2(30),
     "INDIVISIBLE_FLAG" VARCHAR2(1),
     "DIMENSION_UOM_CODE" VARCHAR2(3),
     "UNIT_LENGTH" NUMBER,
     "UNIT_WIDTH" NUMBER,
     "UNIT_HEIGHT" NUMBER,
     "BULK_PICKED_FLAG" VARCHAR2(1),
     "LOT_STATUS_ENABLED" VARCHAR2(1),
     "DEFAULT_LOT_STATUS_ID" NUMBER,
     "SERIAL_STATUS_ENABLED" VARCHAR2(1),
     "DEFAULT_SERIAL_STATUS_ID" NUMBER,
     "LOT_SPLIT_ENABLED" VARCHAR2(1),
     "LOT_MERGE_ENABLED" VARCHAR2(1),
     "INVENTORY_CARRY_PENALTY" NUMBER,
     "OPERATION_SLACK_PENALTY" NUMBER,
     "FINANCING_ALLOWED_FLAG" VARCHAR2(1),
     "EAM_ITEM_TYPE" NUMBER,
     "EAM_ACTIVITY_TYPE_CODE" VARCHAR2(30),
     "EAM_ACTIVITY_CAUSE_CODE" VARCHAR2(30),
     "EAM_ACT_NOTIFICATION_FLAG" VARCHAR2(1),
     "EAM_ACT_SHUTDOWN_STATUS" VARCHAR2(30),
     "DUAL_UOM_CONTROL" NUMBER,
     "SECONDARY_UOM_CODE" VARCHAR2(3),
     "DUAL_UOM_DEVIATION_HIGH" NUMBER,
     "DUAL_UOM_DEVIATION_LOW" NUMBER,
     "CONTRACT_ITEM_TYPE_CODE" VARCHAR2(30),
     "SUBSCRIPTION_DEPEND_FLAG" VARCHAR2(1),
     "SERV_REQ_ENABLED_CODE" VARCHAR2(30),
     "SERV_BILLING_ENABLED_FLAG" VARCHAR2(1),
     "SERV_IMPORTANCE_LEVEL" NUMBER,
     "PLANNED_INV_POINT_FLAG" VARCHAR2(1),
     "LOT_TRANSLATE_ENABLED" VARCHAR2(1),
     "DEFAULT_SO_SOURCE_TYPE" VARCHAR2(30),
     "CREATE_SUPPLY_FLAG" VARCHAR2(1),
     "SUBSTITUTION_WINDOW_CODE" NUMBER,
     "SUBSTITUTION_WINDOW_DAYS" NUMBER,
     "IB_ITEM_INSTANCE_CLASS" VARCHAR2(30),
     "CONFIG_MODEL_TYPE" VARCHAR2(30),
     "LOT_SUBSTITUTION_ENABLED" VARCHAR2(1),
     "MINIMUM_LICENSE_QUANTITY" NUMBER,
     "EAM_ACTIVITY_SOURCE_CODE" VARCHAR2(30),
     "LIFECYCLE_ID" NUMBER,
     "CURRENT_PHASE_ID" NUMBER,
     "OBJECT_VERSION_NUMBER" NUMBER(9,0),
     "TRACKING_QUANTITY_IND" VARCHAR2(30),
     "ONT_PRICING_QTY_SOURCE" VARCHAR2(30),
     "SECONDARY_DEFAULT_IND" VARCHAR2(30),
     "OPTION_SPECIFIC_SOURCED" NUMBER,
     "APPROVAL_STATUS" VARCHAR2(30),
     "VMI_MINIMUM_UNITS" NUMBER,
     "VMI_MINIMUM_DAYS" NUMBER,
     "VMI_MAXIMUM_UNITS" NUMBER,
     "VMI_MAXIMUM_DAYS" NUMBER,
     "VMI_FIXED_ORDER_QUANTITY" NUMBER,
     "SO_AUTHORIZATION_FLAG" NUMBER,
     "CONSIGNED_FLAG" NUMBER,
     "ASN_AUTOEXPIRE_FLAG" NUMBER,
     "VMI_FORECAST_TYPE" NUMBER,
     "FORECAST_HORIZON" NUMBER,
     "EXCLUDE_FROM_BUDGET_FLAG" NUMBER,
     "DAYS_TGT_INV_SUPPLY" NUMBER,
     "DAYS_TGT_INV_WINDOW" NUMBER,
     "DAYS_MAX_INV_SUPPLY" NUMBER,
     "DAYS_MAX_INV_WINDOW" NUMBER,
     "DRP_PLANNED_FLAG" NUMBER,
     "CRITICAL_COMPONENT_FLAG" NUMBER,
     "CONTINOUS_TRANSFER" NUMBER,
     "CONVERGENCE" NUMBER,
     "DIVERGENCE" NUMBER,
     "CONFIG_ORGS" VARCHAR2(30),
     "CONFIG_MATCH" VARCHAR2(30)
) PCTFREE 10 PCTUSED 70 INITRANS 10 MAXTRANS 255 NOCOMPRESS LOGGING
STORAGE(INITIAL 131072 NEXT 131072 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 4 FREELIST GROUPS 4 BUFFER_POOL DEFAULT)
TABLESPACE "APPS_TS_TX_DATA"
So sorry about the length, but not much I could do. :)

Similar Messages

  • Report  for bom wise target and actual cost as well as qty at line item

    Dear Experts,
    Is there any standard tcode for bom wise target and actual cost as well as qty at line item level for the month.
    there is one tcode s_alr_87013127 but user has to double click in order to get line item details.
    I want to see line item wise breakup/bom wise target and cost cost as well as qty.
    Thanks in advance.
    regards
    RK

    Dear experts,
    I am still looking for a revert.
    regards
    RK

  • Report for BOM materials

    Dear Experts,
    i have scenario which i need to capture but do not have any standard report and for that reason i am going in for Z development of the reports. please guide me so as to which field to be pulled to get the desired output.
    Scenario:
    We create Purchase order with a version control
    1. First version has the data which act as baseline and we want to compare rest of the  versions as variance
    2. If the line item in PO is a subcontracting material with L- then the subcomponents will be present as a BOM
    3. when i ammend the PO for the Qty the BOM items also get ammended but do not reflect in the version control - display changes
    4. I want to capture the PO with each line item against which there is qty change and also the material BOM change due to qty change.
    Is there any table from which i capture the data.
    Pl. help me out it would be of great help
    Thanks & Regards,
    Farhan

    Hi
    the following tables might be useful
    MAST
    STKO - Header Table of BOM
    STPO - Item Level for BOM
    MAKT
    regards
    maniraj

  • The standard report for BOMs of a material with a selected period?

    Hi Gurus
    Is there any  standard report for BOMs of a material with a selected period?

    Hi,
    You will have to develop a report for your requirement,
    The following tables will be used for the report
    MAST-WERKS
    STPO-MATNR
    MARA-MAKTX
    STPO-BMENG
    STPO-POSNR
    STPO-IDNRK
    STPO-MAKTX
    STPO-DATUV
    STPO-MENGE
    STKO-MEINS
    STPO-AVOAU
    Regards
    Merwyn

  • Unable to enter multiple Schedule lines for BOM material in Sales Order

    Hi All,
    We have a Sales Order where in which we cannot add additional schedule lines for BOM material.
    The schedule lines are greyed out, user was able to add schedule lines earlier.
    I have checked all assignments in VOV6, VOV7 and everything seems to be fine and no changes have been made to item category being used.
    Please provide a solution for this.
    PFB link in which similar situation posted in this community but the final resolution method is not discussed.
    http://scn.sap.com/message/13201504#13201504
    Regards,
    Samiksh

    Hi Samiksh,
    Pls check for that particular customer, only complete delivery allowed(c) is set in the CMR or CMIR. If so, you can't enter multiple schedule lines for that customer.. it would be grayed out in the sales order schedule lines except confirmed line.
    or check the problematic sales order at item level shipping tab if the par del/item is set to 'C'
    With regards
    S.Siva

  • Problem in creating a bapi for bom

    hai all,
    i am trying to create a bapi for bom using csap_mat_bom_create, but it am getting sy-subrc value as 1.
    and displaying error message as the function module name itself.
    is there any solution dor it.

    Hello,
    Try to use that bapi :
    BAPI_MATERIAL_BOM_GROUP_CREATE
    Thierry

  • Planning of Dependent Requirements for BOM Components in Make to Order scen

    Hi Friends - I want to execute a full cycle Make to Stock Scenario with Materials planning using MRP.
    The scenario will include BOM Components with Routing.
    The process flow I want to execute -
    1. Create a Sales Order for a Finished Product (Product should have a BOM for Production)
    2. Do the product Materials Planning for the Sales Order through MD50
    3. Get all the dependent material requirements (both for products as Planned Order and also for BOM Components - all the BOM components should also be planned)
    4. Convert Planned Order for Product to Production Order
    5. Convert Planned Orders for BOM components to Purchase Requisition
    6. Confirm Production Order
    To execute this I have done the following
    1. I have created a Material Master data for Finished Product (FERT).
    2. I have assigned Item Category Group - NORM, and General Item Category group as NORM
    3. I have assigned MRP Type PD in MRP 1 View and Strategy Group 20 (Make to Order Production) in MRP 3 View.
    4. Now created a Universal (Type 3) BOM for the product with one material component.
    5. Now also created a Routing for the Material with two operations having PP01 a control key.
    6. Now created a standard sales order for the product.
    7. Executed the MD50 for the Sales Order Item.
    Now where do I find the BOM components for this material in the Sales Order?
    After executing the planning Run MD50 I am only getting the requirements for Product only. I can't see any dependent requirements for the BOM components.
    How do I make sure that the BOM components are also planned while the product is planned?
    I have checked the component Stock Requirement List - there are no requirements generated from the Sales Order Product BOM.
    Pls help me on this. How to do this so that the raw material components are also planned?
    Thanks
    Purnendu

    Hi Dhaval, Sandeep, Ashok - Thanks a lot for your replies.
    I have checked the Planned Order Created through Planning Run.
    If I click on the Components Tab I am getting following message
    No material components were determined
    Message no. 61027
    Diagnosis
    Until now, no BOM explosion has been carried out or no BOM has been created for this material yet.
    Procedure
    Either explode the bill of material for this material, or
    create the components manually by processing the planned order in change mode.
    If I try to explode the BOM through Header Menu - Edit> Explode BOM
    I am getting the same message.
    If I click on the Bill of Material Tab - I am getting the same above messge.
    Ashok - I have tried both the Selection Method -
    Nil - Selection by Order Quant.
    1 - Selection by Explosion Date
    But with no effect.
    Waiting for your advice.
    Thanks and warm regards
    Purnendu

  • User exit for BOM

    hello,....
    problem: using BOM in VA01...for free goods material.....
    I am working on user exit for BOM...I need to write a code in FV45SFCO_CONFIGURATION_SET_STM under this we have call customer funcion '003'
    if we click on this we will enter in include ZXVVAU12.....In this including I need to write the code(user exit) by using XSTB table and the values in that table I have to populate in XVBAP.......for the BOM Explosion........when we use VA01......
    so please tell me how can i write the code in that exit ...by getting the data from XSTB to XVBAP........by using the field STLAL (It is Alternative BOM in BOM Screen)...for example if I select '05' (stlal) BOM type.....the values in XSTB populate in XVBAP...
    anyone help me on this........
    Otherwise give me any other sample code for the userexit BOM so that I will learn...a lot from that....
    Thanks in advance,
    Madhu

    Hi Madhu,
    You can try something like this to read XSTB in user exits EXIT_SAPFV45S_003.
    DATA: XT_XSTB LIKE STANDARD TABLE OF SDSTPOX WITH HEADER LINE.
    FIELD-SYMBOLS: <XSTB> TYPE TABLE.
    DATA: FIELD_NAME(30) VALUE '(SAPFV45S)XSTB[]'.
    ASSIGN (FIELD_NAME) TO <XSTB>.
    XT_XSTB[] = <XSTB>.
    READ TABLE XT_XSTB WITH KEY STLAL = '05'.
    IF SY-SUBRC = 0.
    ....                      <--- your logic to move to VBAP
    ENDIF.
    Regards,
    Ferry Lianto

  • Free good for bom material

    hai i am new to sap , can any one tell me how to post free good for bom material !!

    Hi,
    Being a new member, one quick advice would be to search SDN and related forums before posting a new question, since this issue has been discussed many times.
    To answer your question, Free Goods does not support BOM.
    Please check [here|http://help.sap.com/saphelp_46c/helpdata/en/dd/55fa34545a11d1a7020000e829fd11/frameset.htm] for detailed explanation.
    Regards,
    Amit

  • More than 1 line items in bdc using table controls for BOM

    Hi....
    how do u update more than one line item for BOM using BDC table control.......
    is there any specific command for doing that.......
    hav tried d following code bt it takes the flatfile i/p FOR 2 LINE ITEMS as 2 different BOM'S.....
    would appreciate ur help....plz provide code.............
    REPORT zbdc4_cs01
           NO STANDARD PAGE HEADING LINE-SIZE 255.
    INCLUDE bdcrecx1.
    DATA : a TYPE i,
           b type i,
           c type i.
    DATA : BEGIN OF it_rec OCCURS 0,
           rec(200) TYPE c,
           END OF it_rec.
    DATA : BEGIN OF ctab OCCURS 0,
           matnr(18),
           werks(4),
           stlan(1),
           END OF ctab.
    DATA : BEGIN OF xtab OCCURS 0,
           idnrk(18),
           menge(13),
           postp(1),
           END OF xtab.
    DATA : BEGIN OF itab OCCURS 0,
           matnr(18),
           werks(4),
           stlan(1),
           idnrk(18),
           menge(13),
           postp(1),
           END OF itab.
    START-OF-SELECTION.
      CALL FUNCTION 'GUI_UPLOAD'
        EXPORTING
          filename            = 'C:/TEST4.TXT'
          filetype            = 'ASC'
          has_field_separator = 'X'
        TABLES
          data_tab            = it_rec.
      LOOP AT  it_rec.
        a = strlen( it_rec-rec ).
        if a = 55.
        itab-matnr = it_rec-rec+0(18).
        itab-werks = it_rec-rec+18(4).
        itab-stlan = it_rec-rec+22(1).
        itab-idnrk = it_rec-rec+23(18).
        itab-menge = it_rec-rec+41(13).
        itab-postp = it_rec-rec+54(1).
        APPEND itab.
        elseif a > 55.
        itab-matnr = it_rec-rec+0(18).
        itab-werks = it_rec-rec+18(4).
        itab-stlan = it_rec-rec+22(1).
        itab-idnrk = it_rec-rec+23(18).
        itab-menge = it_rec-rec+41(13).
        itab-postp = it_rec-rec+54(1).
        APPEND itab.
        itab-idnrk = it_rec-rec+55(18).
        itab-menge = it_rec-rec+73(13).
        itab-postp = it_rec-rec+86(1).
        APPEND itab.
        endif.
      ENDLOOP.
      PERFORM open_group.
      LOOP AT itab.
        PERFORM bdc_dynpro      USING 'SAPLCSDI' '0100'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'RC29N-STLAN'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '/00'.
        PERFORM bdc_field       USING 'RC29N-MATNR'
                                       itab-matnr.           "'3000000107'.
        PERFORM bdc_field       USING 'RC29N-WERKS'
                                       itab-werks.              "'UN02'.
        PERFORM bdc_field       USING 'RC29N-STLAN'
                                       itab-stlan.              "'1'.
        PERFORM bdc_field       USING 'RC29N-STLAL'
        PERFORM bdc_field       USING 'RC29N-DATUV'
                                      '11.08.2008'.
        PERFORM bdc_dynpro      USING 'SAPLCSDI' '0110'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '/00'.
        PERFORM bdc_field       USING 'RC29K-BMENG'
                                      '1'.
        PERFORM bdc_field       USING 'RC29K-STLST'
                                      '1'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'RC29K-EXSTL'.
        PERFORM bdc_dynpro      USING 'SAPLCSDI' '0111'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'RC29K-LABOR'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '/00'.
        PERFORM bdc_dynpro      USING 'SAPLCSDI' '0140'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'RC29P-POSTP(01)'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '/00'.
        PERFORM bdc_field       USING 'RC29P-IDNRK(01)'
                                       itab-idnrk.             "'1000000232'.
        PERFORM bdc_field       USING 'RC29P-MENGE(01)'
                                       itab-menge.              "'100'.
        PERFORM bdc_field       USING 'RC29P-POSTP(01)'
                                       itab-postp.             "'L'.
        PERFORM bdc_dynpro      USING 'SAPLCSDI' '0130'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '/00'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'RC29P-POSNR'.
        PERFORM bdc_field       USING 'RC29P-POSNR'
                                      '0010'.
        PERFORM bdc_field       USING 'RC29P-IDNRK'
                                      '1000000232'.
        PERFORM bdc_field       USING 'RC29P-MENGE'
                                      '100'.
        PERFORM bdc_field       USING 'RC29P-MEINS'
                                      'KG'.
        PERFORM bdc_dynpro      USING 'SAPLCSDI' '0131'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '/00'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'RC29P-POTX1'.
        PERFORM bdc_field       USING 'RC29P-SANKA'
                                      'X'.
        PERFORM bdc_dynpro      USING 'SAPLCSDI' '0140'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'RC29P-POSNR(01)'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '/00'.
        PERFORM bdc_dynpro      USING 'SAPLCSDI' '0140'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'RC29P-POSNR(01)'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '=FCBU'.
        PERFORM bdc_transaction USING 'CS01'.
      ENDLOOP.
      PERFORM close_group.

    Hi
    Check this sample code for the Table Control in BDC:
    data: fnam(20) type c.
    move 1 to id.
        loop at TI_STAGING WHERE VENDOR = IT_STAGING-VENDOR AND DOCDATE = IT_STAGING-DOCDATE.
          concatenate 'RM06E-EPSTP(0' id ')' into fnam.
          perform bdc_field       using fnam TI_STAGING-itmcategory.
          concatenate 'EKPO-KNTTP(0' id ')' into fnam.
          perform bdc_field       using fnam TI_STAGING-accassignment.
          concatenate 'EKPO-EMATN(0' id ')' into fnam.
          perform bdc_field       using fnam TI_STAGING-material.
          concatenate 'EKPO-TXZ01(0' id ')' into fnam.
          perform bdc_field       using fnam TI_STAGING-shortxt.
          quan = ti_staging-poqty.
          concatenate 'EKPO-MENGE(0' id ')' into fnam.
          perform bdc_field       using fnam quan.
          concatenate 'RM06E-EEIND(0' id ')' into fnam.
          perform bdc_field       using fnam TI_STAGING-deliverydate.
          netpr = ti_staging-netpr.
          concatenate 'EKPO-NETPR(0' id ')' into fnam.
          perform bdc_field       using fnam netpr.
          concatenate 'EKPO-MATKL(0' id ')' into fnam.
          perform bdc_field       using fnam TI_STAGING-mategroup.
          concatenate 'EKPO-WERKS(0' id ')' into fnam.
          perform bdc_field       using fnam TI_STAGING-plant.
          ID = ID + 1.
        ENDLOOP.
    Regards,
    Vishwa.

  • Do we document BOM information for each item in BR100 for BOM?

    Hi,
    I'm working on BR100 for BOM. I noticed that in BR100 BOM template there is not a section for the documentation of BOMs for each item. I wonder if the standard is not documenting any of that information in this document?
    Thanks a lot,
    Robert

    Hello Robert,
    BR100 explain all setups steps for modules.
    BOM for each item is not 'setup' but 'Data Management'.

  • LSMW FOR BOM CREATING.

    Hi Guys,
    I have a requirement where i create lsmw for bom upload using batch input. I m trying to create only one source structure and source fields assigned to this source structure but when finally im executing it its creating the first line item correctly but for all the second line items onwards its saying that Alternative already exists... My functional guy says that its creating just the first component in the bom and for the second component its trying to create another bom...and while its checking for the header which is already created its giving us error..
    I dont know how to handle this.....guys its a little urgent....plz help me out.
    here is a snap shot of the errors..
    10:25:44     Session BOM-CREATE is being processed by user KALVALV in mode N on server psdux07                              0                                                           0     S     00     300
    10:25:44     Creating BOM for material 10000240     CS01     1     SAPLCSDI     0140     7     S     29     030
    10:25:45     Transaction was processed successfully     CS01     1                                                           0     S     00     355
    10:25:45     Alternative 1 already exists     CS01     2     SAPLCSDI     0100     1     E     29     003
    10:25:45     Transaction error     CS01     2                                                           0     S     00     357
    10:25:45     Creating BOM for material 10000346     CS01     3     SAPLCSDI     0140     7     S     29     030
    10:25:45     Transaction was processed successfully     CS01     3                                                           0     S     00     355
    10:25:45     Alternative 1 already exists     CS01     4     SAPLCSDI     0100     1     E     29     003
    10:25:45     Transaction error     CS01     4                                                           0     S     00     357
    10:25:45     Creating BOM for material 10000347     CS01     5     SAPLCSDI     0140     7     S     29     030
    10:25:46     Transaction was processed successfully     CS01     5                                                           0     S     00     355
    10:25:46     Alternative 1 already exists     CS01     6     SAPLCSDI     0100     1     E     29     003
    10:25:46     Transaction error     CS01     6                                                           0     S     00     357
    10:25:46     Creating BOM for material 10000785     CS01     7     SAPLCSDI     0140     7     S     29     030
    10:25:46     Transaction was processed successfully     CS01     7                                                           0     S     00     355
    10:25:46     Alternative 1 already exists     CS01     8     SAPLCSDI     0100     1     E     29     003
    10:25:46     Transaction error     CS01     8                                                           0     S     00     357
    10:25:46     Creating BOM for material 10001252     CS01     9     SAPLCSDI     0140     7     S     29     030
    10:25:46     Transaction was processed successfully     CS01     9                                                           0     S     00     355

    Hi,
    You need to define the two structure header and detail. Both files should have the key fields:
    For example: Both file have Plant, Material Number, BOM Usage & Valid From.
    Then BGR00 and BICSK should be mapped to BOM_HEADER and BICSP to BOM_DETAIL structure.
    Then just do the mapping and should work.
    Hope this helps.
    Regards,
    Bharati Singh

  • One pricing condition for BOM and other for individual component

    Hello SAP gurus,
    We have two pricing condition types created and assigned in the pricing procedure which has been created with reference to PR00 and condition records are maintained for both the condition types.
    But, we want only one pricing condition type to be triggered in the sales order depending on the usage of material in the sales order. As we are selling the same material individually and as well as a component in a bundle ( BOM).
    i.e, when one pricing condition for BOM component and other for individual component
    What are the configuration steps to be taken care to get this scenario?
    Thanks in advance.
    Regards,
    KB
    Edited by: K.byla on Jan 21, 2010 1:20 PM

    Hi Sagar,
    Thanks for your response.
    Yes, we are maintaining only one material. The same material is used to sell individually and also in a BOM.
    As i have mentioned earlier, whenever the material is sold individually it should pick condition type say 'YR00' and when the same material is sold as a bundle ( BOM) , it should pick condition type " YR01" in same the pricing procedure.
    For both the condition types, the condition records are maintained.
    To give the scenario details,
    A material "X" is sold individually as a single component and the same material is also used for selling bundled with other material "Y" and the bundled material as "Z"
    means, Z=X+Y
    Pricing procedure used is say ZRA000 which contains currently the price cond type YR00.
    Now for the bundle (BOM) involvement i want to use the same pricing pricing proc. and add the new cond YR01 in it so that the system will pick the cond.type YR00 when the material is sold individually and YR01 is taken as the price when the material is sold as a bundle against the item X.
    Need to know the steps for this scenario and do i need to maintain a specific requirement ? please suggest.
    BR,
    KB

  • Function Module for BOM for posting BOM component long text

    Is there any SAP provided Function Module for posting BOM components long
    text if so please let me know as it is very urgent for me.

    Hello Sridevi,
    The following customer exits are available for BOM, please check the excect one.
    http://help.sap.com/saphelp_46c/helpdata/en/4a/d286ba5a1111d3b47b006094b9d648/frameset.htm
    Hope this helps.
    Regards
    Arif Mansuri

  • How to run MRP for BOM as well as ROL items

    We have only one plant. I  want to run MRP for BOM items as well as ROL items.  MRP can be  run plant wise thru tcode MD01.  I want to run mrp for only ROL items.
    Please suggest
    Regards,
    ( Rajneesh Gulati )
    Edited by: Rajneesh  Gulati on Jun 20, 2008 11:33 AM

    As I understand for Quartz, I think you should create a security subject for it in your code. I guess the background tasks in Quartz work in separate threads. It is not recommended in EJB application. you can use EJB timer service instead.
    -Albert

Maybe you are looking for

  • How can I make Safari and Firefox remember a password?

    I changed some of my website passwords recently.  In most cases, Safari and Firefox asked me if I wanted them to remember the new password, I said Yes (I'm not on a shared computer), and when I entered my email address or username, it would appear in

  • IMovie 06/ Sony HDR-HC 9 compatibility

    My Sony HDR-HC9 works with iMovie 08, but not 06. My Sony DCR-TRV110E works with iMovie 06, but not 08. Can anyone explain ?

  • E-Recruitment WF help

    Hello. I am working in our e-Recruitment system. When a manager releases a requisition to the HR Advisor, I would like to trigger a workflow to send an email to that HR Advisor. The manager would click the forward button, then the Confirm button to t

  • I am unable to add wires to any vi on one of my computers.

    I am unable to add wires to any vi on one of my computers. The installation was performed by a previous coworker.  I cannot contact him.  I'm not sure if he had some special settings which cause this or not.  I copied all of the Tools/Options setting

  • TLB Profile parameters in TLB Order

    Hi When we create TLB orders in interactive TLB, the system uses the TLB profile attached in the T-lane master data.  However we have the option of selecting a different TLB PROFILE during the run.    After we create such orders with TLB profile diff