Oracle_EBS_Core Functions (MFG) (1)

1. INV: Items

Refer to "Introduction to the Core Functions of Oracle EBS (DIS)". canca

1. INV: Transactions basic inventory transactions

Refer to "Introduction to the Core Functions of Oracle EBS (DIS)". canca

1. BOM: Bills of Material

Application: Bills of Material

Responsibilities: Bills of Material

1. 1. Basic Business Learning

in summary

The ultimate solution to the problem of BOM (Bill of Materials) is the standardization of materials and quantities used in the production process. The accuracy is required to be above 98%, and it must be continuously compared with the scene to gradually reach 100%.

BOM is the business-driven core of manufacturing enterprises. WIP, OPM, COST, MPS/MRP, etc. run directly on the basis of BOM. Without a stable and clear BOM, there is no ERP.

BOM is a composition structure diagram of a product, which defines the parts and quantities required to produce a specific material. Each part may also have their BOM structure, resulting in a multi-level product structure tree.

For example, a bicycle that requires two rims for one wheel is relatively rare! It can be seen that to produce a bicycle, 2 * 2 rims are required

The maintenance and change of BOM actually involves at least the following departments: Engineering Department/R&D Center, Planning Department, Manufacturing Department, and Finance Department.

From different perspectives, BOM has different classifications.

From the perspective of design and manufacturing, according to bom_bill_of_materials.assembly_type

1. Engineering BOM is maintained in the engineering module

Engineering BOM basically reflects the BOM on engineering drawings, such as the BOM designed by CAD.

The actual maintenance in EBS is not much different from the manufacturing BOM; the main difference is that the engineering BOM cannot be used for production, and engineering materials and other engineering BOMs can be selected as components during maintenance.

1. The manufacturing BOM is maintained in the BOM module or "implemented" by the engineering BOM - converted from production

The manufacturing BOM reflects the BOM currently used in the actual production of the workshop, that is, the specifications and quantities of parts that should be input according to the standards during the product production process.

From the perspective of component supply, according to bom_inventory_components.wip_supply_type

1. Ordinary parts Components of supply type other than Phantom

WIP component requirements are calculated according to normal logic: only look at the components of one layer of BOM.

1. Phantom Components that supply type Phantom

For WIP component requirements, skip virtual parts, and directly use the components under it as WIP requirements; ignore the process route of virtual parts.

The virtual part is only distinguished from the perspective of its parent part. In fact, if you open the job directly, there is no difference from other assembly parts.

From the perspective of product type, according to mtl_system_items_b.bom_item_type

1. Standard BOM

The most common common BOM, theoretically all components are necessary, and the quantity is also the standard consumption.

Modules such as WIP and CST use standard BOM, and OM actually implements standard BOM.

1. Model BOM

It is used for the CTO (ATO, PTO) sales method of OM, so it can be divided into ATO BOM and PTO BOM.

The enterprise defines a product model in advance, some of the components are mandatory (Mandatory), and some are optional (Optional); in the above two components, a category (Option Class) may be defined, as long as the Just select one or more of the categories. If the model BOM is defined nestedly, it will be very complicated.

According to the model, the customer finally selects a satisfactory composition plan; we open SO to place an order according to the customer's plan.

SO will create an Item and its BOM according to the selection result. Because this kind of item is usually set to be generated by "<raw material code>*<serial number>", it is also called "asterisk item"; the corresponding BOM is called "configuration BOM", which has no difference from the standard BOM .

1. Option class BOM

For the components used in the model BOM, refer to the above description.

For example, the display in the computer model can be used as an option, and the company can provide multiple models for customers to choose from.

Sometimes you feel that the "Option BOM" is similar to the "Model BOM", that's right, the difference is that the former can only be used as a component of the latter, and is not available for customers to order independently. ^o^!

1. Plan BOM

The difference between the planned BOM and the standard BOM is that its component usage has a percentage, so when doing Forecasts expansion, MPS will multiply the percentage layer by layer to obtain the expansion plan quantity.

Items of the plan type cannot define Routing, BOM has no output rate, no convolution cost, no supply/delivery and other information, in short, the plan BOM only cares about quantity!

From the perspective of formula primary and secondary, according to bom_bill_of_materials.alternate_bom_designator

1. main BOM

The most commonly used product structure is the main BOM by default in the use of each module, such as cost convolution, opening JOB, MRP calculation, OM model BOM, etc. Cost convolution and opening JOB can be manually selected to replace the BOM.

1. replace BOM

After creating the main BOM, you can create a parallel formula—replacing the BOM, which means that the same product can also be produced with other formulas (different materials, different quantities), which is more direct and easier to control than using substitute materials.

When doing engineering BOM, you can usually create a series of alternative BOMs to compare their composition, process, and cost.

1. 1. core function process

Standard BOM learning process

Prerequisite Refer to "Detailed Example of Oracle EBS Full Module Settings" to set BOM
   ↓                             
Review Item Review the BOM Tab page properties in the material definition, refer to "INV: Items"
   ↓
Review Profile Review important Profile settings
   ↓
Define Primary BOM Define the main BOM
   ↓                             
Define Alternate Define Alternative
   ↓
Define Alternate BOM Define Alternative BOM
   ↓                             
View Indented BOM View BOM Multi-level List
   ↓                             
View Item Where Used View Material Usage
   ↓                             
Modify Component Invalid Components, Add New Components

1. 1. Review Profile

prefab file

N: Sys/Profiles/System

Focus on the following Profile settings:

 

1. 1. Define Primary BOM

main BOM

N: BOM/Bills/Bills

The BOM in EBS is defined independently in layers , but in no particular order. For example, in the above-mentioned "Bicycle Composition Structure Diagram", the BOM of the bicycle can be defined first, and then the BOM of the wheel can be defined; it can also be defined in reverse. In the end, they all form a product structure tree in the same way. Relatively, the parent node is called "assembly" or "parent part", and the child node is called "component" or "child part".

 

In the picture above, the assembly is "960001", and the components are "910001" and "960002".

 

In the picture above, the assembly is "960002", and the components are "910002" and "910003".

In this way, layers can be defined theoretically without limitation; Oracle ERP currently allows up to 60 layers of BOM, but the actual implementation should be as flat as possible.

Commonly used fields are detailed, and the bold part must be mastered:

 

The BOM data defined in our practice in this chapter is as follows:

 

 

1. 1. Define Alternate

Alternative number

N: BOM/Setup/Alternates

Define the substitution number HUAJHUA:

 

1. 1. Define Alternate BOM

replace BOM

N: BOM/Bills/Bills

The only difference from the Primary BOM is that the substitution number needs to be defined under "Assembly", assuming that the quantity of the formula HUAJHUA is different from the main formula.

HUAJHUA of 960001：

 

HUAJHUA of 960002 (Note: Come back to define after reading "View Indented BOM"!)

 

The BOM data defined in our practice in this chapter is as follows:

 

1. 1. View Indented BOM

multilevel list

N: BOM/Bills/Indented Bills

As discussed above, when BOM is defined, it is defined hierarchically and independently, and the complete BOM should be a tree structure. Indented Bills shows this tree in an indented manner, called "BOM multi-level list".

" BOM multi-level list" is from the perspective of assembly parts, which materials are recursively used for production.

First enter the query interface, we first check the main BOM:

 

The data meaning of this query interface is: Expand the current 960001 main BOM to see which components are directly and indirectly used, up to 10 layers. The result is (click the + sign in the lower left corner to expand), which is an upright tree:

Here we focus on Quantity and Extended Quantity, the latter is multiplied layer by layer by the former.

Then check the "multi-level list" of the replacement BOM, before defining the 960002 replacement formula:

 

After defining the 960002 substitution recipe:

 

EBS follows the following rules when expanding the multi-level list: subject to the top-level substitution number, first use the BOM with the same substitution number in the sub-level to expand, if not, use the main BOM until the leaf node (material without BOM definition) .

1. 1. View Item Where Used

Where materials are used

N: BOM/Bills/Item Where Used

 

"Where materials are used" is from the perspective of components, which assemblies are used, and can be recursive to the top assembly!

The meaning of the interface in the above picture is: query which assemblies are currently used directly or indirectly by 910002, and you can find up to 10 floors online. The result is as follows, an inversion of the multilevel list:

 

1. 1. Modify Component

Modified components

N: BOM/Bills/Bills

For component modification, such as modifying the quantity, supply method, output rate, etc., you can directly modify the corresponding line, which is simple and direct, but cannot keep traces. There are 2 suggested methods: one is to "copy" a line for modification and invalidate the original line; the other is to do it through ECO (Engineering Change Order).

Here method 1 is used to first find out the BOM to be modified, fill in the "expiration date" in the row to be modified, save it; add a new record, and enter the same serial number and new component information.

 

In this way, a new version (Version) of the BOM is actually generated. For example, 27-OCT-2006 16:43:05 and before is one version, and 27-OCT-2006 16:46:40 and after is another version; strictly In other words, within the gap between these two times, there is another version.

1. 1. other important issues

Revision and Version

Although the version number is not marked, the previous "Modify Component" has a valid time range to distinguish, so that the BOM has different Versions at different points in time; on the other hand, Item can create a Revision (revision number) to BOMs created by Items with different revision numbers have different versions, of course.

So, in general, different BOM versions can be maintained in these two ways.

How to write BOM SQL

1. in Form and package

The system standard API should be used to expand: apps.bompexpl.exploder_userexit, which can expand any level of multi-level list , including the cost of the specified type. We don't need to write the function to expand the BOM by ourselves, and we don't need to use SQL to fetch it directly, which can ensure the greatest code robustness and compatibility.

1. In daily SQL, it is also necessary to refer to this standard API to write. The following is an example of taking a single-layer BOM at the current point in time (Sysdate), and Revision is still missing :

SELECT mst.segment1 assembly_item,
       boms.alternate_bom_designator alternate,
       bics.item_num,
       msic.segment1 component_item,
       bics.component_quantity,
       bics.effectivity_date,
       bics.disable_date
  FROM inv.mtl_system_items_b        mst,
       apps.bom_bill_of_materials    boms,
       apps.bom_inventory_components bics,
       inv.mtl_system_items_b        msic
 WHERE mst.organization_id = boms.organization_id
   AND mst.inventory_item_id = boms.assembly_item_id
   AND boms.bill_sequence_id = bics.bill_sequence_id
   AND boms.organization_id = msic.organization_id
   AND bics.component_item_id = msic.inventory_item_id
      --Item
   AND mst.bom_enabled_flag = 'Y'
   AND mst.bom_item_type IN (1, 2, 3, 4) --Dependent
      --BOM Header
   AND boms.assembly_type = 1 --1 Manufature,2 ENG
   AND nvl(boms.effectivity_control, 1) <= 3
      --BOM Line
   AND nvl(bics.disable_date, SYSDATE) >= SYSDATE
   AND bics.effectivity_date <= SYSDATE
   AND bics.implementation_date IS NOT NULL
   AND nvl(bics.eco_for_production, 2) = 2
      --Filters
   AND mst.organization_id = 82
   AND mst.segment1 LIKE '96%'
 ORDER BY 1, 2 NULLS FIRST, 3

Optional reading: Allowed component types for different types of BOMs

《115bomug.pdf》/Bills of Material/Overview of Bills of Material/Components

Optional reading: Component properties allowed by different types of BOM

《115bomug.pdf》/Bills of Material/Overview of Bills of Material/Components

How to share BOM

N: Tools/Copy or Common

The BOM of an organization can be shared with other organizations under the same main organization , or even with other materials of the same organization, as long as the BOM Item Type of the materials is the same . This can reduce the maintenance workload. The BOM of XXX company is maintained in the same organization, and then Common to the whole group!

Always note: Sharing only shares one layer of BOM, and the BOM of its components needs to be shared again; if it is cross-organization, the supply sub-library/slot cannot be shared; make sure that components and substitute materials exist in the target organization, otherwise they cannot be shared.

There are two ways of sharing: one is copying, which can be modified and maintained independently after copying; the other is reference, also called Common, BOM is still maintained in the original organization/raw material, and the target organization/target material BOM can no longer be maintained, the system stipulates Common BOM can no longer be commoned by other Items, otherwise the program will be very difficult to find.

In addition, for CTO sales companies, the BOM is maintained in a common organization, and the SO verification organization is usually the Master organization, so the BOM Common must be transferred to the master organization.

substitute material

N: Button/Substitute

Standard BOM can set substitute materials (not to be confused with substitution numbers), that is, components can be replaced by other materials, and the quantities do not need to be equal; this only affects MRP, not WIP.

Avoid BOM circular definitions

N: Tools/Check for Loops

When defining BOM, we actually only focus on one layer, and don’t care about the BOM definition of the component itself. If A uses B, B uses C, and C uses A, if it is expanded with a multi-level list, it is actually an infinite loop , the system provides this check function to prevent the occurrence of loops.

BOM maintenance monitoring

Every time a BOM or its components are created, modified, or deleted, the system records the Business Event in the background. If monitoring is required, just define a subscription to achieve the purpose of monitoring. For example, if the quantity is modified, a notification will be sent to a specific person. , I feel it is a good function.

Batch Edit

N: BOM/Bills/Mass Change

A means of increasing maintenance efficiency that can be used independently of ECO.

You can define a series of conditions - the BOM range to be changed, and then set the Action - modify the content, such as adding component B, deleting component A and other rich modification methods.

Compare two BOMs

N: BOM/Bills/Comparison

You can compare any organization and any BOM to see the differences in materials and quantities

How to delete the BOM

N: BOM/Delete Groups

Unified deletion through the deletion group, so that it can be uniformly checked whether there are constraints such as transaction processing, and can be deleted only if there is no.

Restrictions

N: BOM/Setup/Constraint

Set the constraints when BOM is deleted, the default is enough!