Some of the steps listed are Required and some are Optional. You need to perform Optional steps only if you plan to use the related feature or complete certain business functions.
While you can set up Oracle Bills of Material in many different ways, and defer optional set up steps until you are ready to use the corresponding functionality, we recommend you use the order suggested in the following list.
For each step, a Context section indicates whether you need to repeat the step for each set of books, set of tasks, inventory organization, HR organization, or other operating unit under Multiple Organizations.
Set Profile Options (Required)
Profile options specify how Oracle Bills of Material controls access to and processes data. In general, profile options can be set at one or more of the following levels: site, application, responsibility, and user.
Oracle Bills of Material users use the Personal Profile Values form to set profile options only at the user level. System administrators use the System Profile Values form to set profile options at the site, application, responsibility, and user levels. See: Oracle Bills of Material Profile Options.
Context: Perform this step once for each entity, that is, organization operating unit, business group, or legal entity.
Define Exception Templates (Optional)
You can define your own exception templates. When you assign an exception template to your workday calendar, you can assign workday exceptions to account for plant workday differences-such as holidays, scheduled maintenance, or extended downtime.
Context: Perform this step once per installation.
Define and Build your Workday Calendar (Required)
You define a workday calendar for one or more organizations, and assign an exception set to each calendar. For each workday calendar and exception set, you assign a list of holidays or workday exceptions. You then define shifts for your workday calendar, and assign any shift workday exceptions.
After you define your workday calendar information, you build your workday calendar with the exception set. If you associate one calendar with multiple organizations, you can build your workday calendar with multiple exception sets to account for workday differences across organizations.
Attention: If you use Oracle Master Scheduling/MRP, choose the calendar options 445 weekly quarter pattern or 544 weekly quarter pattern if you want to report MRP information in weeks and months. Otherwise, if you choose 13 period calendar or Regular calendar months, you can only report MRP information in monthly buckets.
Context: Perform this step once per installation.
Assign Workday Calendar to Organization (Required)
You assign a workday calendar and exception set to each of your organizations. You can share the same workday calendar across organizations with either the same or a different exception set for each organization.
Default: If you skip this step, <enter value here> will be used as the default value.
Context: Perform this step once per organization.
Define Bill of Material Parameters (Required)
You assign the maximum number of bill of material levels for bill explosions, loop checks and implosions. For assemble to order manufacturers, you assign configuration item information.
Oracle Cost Management does require that you assign values to each parameter if you compute an organization's manufacturing costs based on bill of material and routing information defined in Oracle Bills of Material.
Context: Perform this step once per organization.
Define Department Classes (Optional)
You can define department classes to group departments and to identify manufacturing cells. This information is for your reference only.
Context: Perform this step once per organization.
Define Resources (Optional)
You can define a resource as anything of value, except material and cash, required to manufacture, cost, and schedule products. Resources include people, tools, and labor purchased from a supplier.
Context: Perform this step once per organization.
See: Defining a Resource.
Define Resource Setup Information (Optional)
Define resource setup information to create a performance model for machines and resources that includes time needed to change from one setup to another.
Context: Perform this step once per organization.
Define Resource Groups (Optional)
You can group department resources by resource group to facilitate bill of resource generation and capacity planning in Oracle Capacity.
Context: Perform this step once per installation.
See: Defining a Resource.
Define Competencies for Resources
You can define competencies for resources while assigning employees to the resources. The competency, skill levels and qualification must match the requirements for the resource. You can only add those resources that meet the requirements to the resource instance. The skill definition of the resource cannot be changed if there are employee instances assigned to the resource.
Note: If you want to change the skills for the resource, then delete all employee instances for the resource and then change the skills.
Define Competencies for Routings
Define the competencies required for both standard and non-standard operations and update competencies as required.
Define Competencies for Standard Operations
You can define the competencies of the resource to perform the operation.
Define Simulation Sets (Optional)
You can group deviations to available resource capacity for resource shifts and use each set in shop floor scheduling and capacity planning.
Context: Perform this step once per installation.
See: Defining a Resource.
Define Locations (Optional)
You define delivery locations for departments with outside processing resources.
Context: Perform this step once per organization.
See: Defining a Resource.
Define Departments (Optional)
You can define departments as areas within your organization where you perform work and/or collect costs.
Context: Perform this step once per organization.
See: Defining a Department.
Assign Resources and Resource Shifts to Departments (Optional)
You can assign resources to a department and then assign shifts to those resources. You can group department resources by resource group, and assign a simulation set with capacity modifications for each resource shift.
Default: If you skip this step, <enter value here> will be used as the default value.
Context: Perform this step once per organizational department.
Define Overheads (Optional)
You can define resource overhead by using the Define Overhead form. Each overhead sub-element has a default basis, default activity, and absorption account. The overhead absorption account offsets your corresponding overhead cost pool in the general ledger.
Context: Perform this step once per organizational resource.
See: Defining a Resource.
Associate Overheads with Departments (Optional)
You can assign overhead rates or amounts to your department by cost type and department. The cost rollup uses the assigned basis type to allocate the overhead charge. The cost rollup assigns the activity to the calculated overhead cost. You can define pending rates and use the cost rollup/update process to change the pending rates to Frozen overhead rates.
Context: Perform this step once per organizational department.
See: Defining a Department.
Define Alternates (Optional)
You can define any number of alternate names that you use when you create alternate bills of material and routings. You use alternate bills and routings to produce an identical product using a different bill or routing. You can apply the same alternate name to a bill of material and a routing.
Context: Perform this step once per organization.
Define Standard Bill of Material Comments (Optional)
You can define any number of standard bill of material comments that you can assign to your bills of material.
Context: Perform this step once per organization.
Define Standard Instructions (Optional)
You can define any number of operation instructions that you can assign to a routing operation or standard operation.
Context: Perform this step once per organization.
Define Change Order Types (Optional)
You can define mass change order types, using your own terminology, to describe mass changes to your manufacturing bills of material.
Default: If you skip this step, Oracle shipped change order types will be used as the default value.
Context: Perform this step once per installation.
Define Delete Statements and Constraints (Optional)
Oracle Bills of Material provides a list of rules to determine if an item, bill of material or routing can be deleted and a list of delete instructions. Each rule insures data integrity across all Oracle Manufacturing applications. You can add to this list with your own business rules to further restrict the entities that can be deleted. You write each of your delete constraints as a SQL select statement that either prevents or lets a user delete an item, bill, or routing. Once the delete constraint selects the data to be deleted, the delete statement provides the SQL delete statement used to delete the selected data.
Default: If you skip this step, Oracle shipped delete constraints and statements will be used as the default values.
Context: Perform this step once per organization.
Define Lookups (Optional)
Oracle Applications provides a consolidated method across all applications for defining codes. Bills of Material codes you can define include:
Bonus Codes
Scrap Codes
Resource Down Codes
Resource Capacity Change Reasons
Context: Perform this step once per organization.
See: Defining Lookups.
Assign View-only Privileges to Forms (Optional)
The system administrator can assign view-only privileges to certain forms by user. For example, most users do not need the ability to define or update department information. The system administrator can restrict all but the user who maintains department information from adding or updating departments, while still enabling everyone to view the Departments window.
Context: Perform this step once per responsibility.