If you are using Oracle Advanced Planning Scheduler (ASCP), you must set up Oracle Process Manufacturing (OPM) data so that it can be properly processed. You must understand the differences in data structure between Oracle Applications and OPM in order to properly set up and use the OPM data with ASCP.
This chapter covers the following topics:
Set up these prerequisites prior to running the application. Refer to the details for setting up these requirements provided in the individual application user's guides indicated. Depending on your individual requirements, there may be additional setup required.
Set up the following in the Oracle Inventory application. Refer to the Oracle Inventory User's Guide for details.
Inventory Organizations
Required.
Organization Parameters
Required.
Units of Measure Classes
Required.
Units of Measure
Required.
Unit of Measure Conversions
Master Items
Organization Items
The following item attributes need to be set up for the items to be recognized and used in OPM Process Planning:
Select the Recipe Enabled and Process Execution Enabled attributes on the Process Manufacturing tab to use organization items in formulas and recipes.
Set up the following in the Oracle Process Manufacturing Product Development application. Refer to the Oracle Process Manufacturing Product Development User's Guide for details.
Formulas
Routings
Recipes
Validity rules
Set up the following in the Oracle Bills of Material application. Refer to the Oracle Bills of Material User's Guide for details.
Workday Calendar
Exception Template
Assign Workday Calendar to Organization
Set up the following in the Oracle Bills of Material application. Refer to the Oracle Advanced Supply Chain Planning User's Guide for details.
Create Sources
Create Database Link to Destination
Create Planning Flexfields
Run Refresh Snapshot Process
Create Destinations
Create Database Link to Destination
Define Source Instances
Run Collections
Define Sourcing Rules
Define Assignment Sets
Create Supply Chain Plan
When the suggestions are brought over to OPM and the profile is enabled, all suggestions that are grouped by the launched plan's group ID are input as parameters to the Auto Release of Planning Suggestions for the APS concurrent program. While implementing the suggestions, the concurrent program generates a log, which lists the implementation successes and failures.
Default
N
Options
N - Do not auto implement APS suggestions
Y - Yes auto implement APS suggestions
Recommended Change Level
Site, Application, Responsibility, User
This profile option indicates the default maximum days.
9999
Not applicable
Site, Application, Responsibility, User
Establishes the default MPS/MRP schedule.
Default
SCHD
Options
Any valid schedule defined in Master Production Scheduling application.
Recommended Change Level
Site, Application, Responsibility, User
This profile option represents the exception code value that is entered. You can use the existing Exception codes to represent unavailable hours for a resource in a Plant. If for some reason you do not want to use the existing Exception codes to show the unavailable hours of a Resource, you can enter the Unavailable hours in the window manually and these rows are shown as Manual Entry rows in the window. The profile option value Manual is used to show that the rows entered by the user are manual entries and are not from the Exception codes.
Default
Manual
Options
Manual
Null
Recommended Change Level
Not applicable
When the profile option is enabled, the onhand quantities of OPM items that are flagged as "Experimental" are passed in the collection process to ASCP for planning.
Default
No
Options
No - Do not collect onhand quantities for experimental items
Yes - Collect onhand quantities for experimental items
Recommended Change Level
Site
The profile option enables you to implement production order suggestions from APS as Firmed batches.
Default
Null
Options
No - The application does not create Firmed batches irrespective of the firm planned order being Firmed.
Yes - The application creates Firmed batches, if the firm planned order is Firmed.
Recommended Change Level
Site
The profile option enables you to allow the OPM Process Planning application to use the calendar associated with the organization for batch creation, during the implementation of APS suggestions.
Default
Null
Options
No - The application does not use the calendar associated with the organization for batch creation.
Yes - The application uses the calendar associated to the organization for batch creation.
Recommended Change Level
Site, Application, Responsibility, User
When the profile option is enabled, production batches are created with updated activity offsets during the implementation of APS suggestions.
Default
Null
Options
No - The application creates batches without updated activity offsets.
Yes - The application creates batches with updated activity offsets.
Recommended Change Level
Site, Application, Responsibility, User
When setting up OPM data to use with ASCP, consider the differences between Oracle Applications and OPM for the following data:
Formulas
Recipes
Routings
Resources
MPS Schedule Parameters
Sales Order Demand
Batches
Formulas in OPM are the same as bills of material (BOMs) in Oracle Applications. Oracle Applications has different rules from OPM for BOMs and routings.
When setting up formulas, consider the following:
If an OPM formula is used in multiple recipes with different validity rules for a product or for coproducts, ASCP effectively views different formulas. A different formula is reported for coproducts with validity rules.
ASCP expects one or many product per bill of material (in OPM, a formula).
Linear fixed scaling; and integer is implemented the same as in OPM.
Item quantities are reported in the primary UOM.
Contribute to yield, steps is recognized in ASCP.
APS uses recipes to determine formula, routing, and validity rule assignments for a product. APS looks at the data in certain recipe fields first, then, if no data was entered in the fields at the recipe level, APS retrieves the data from the same fields in other windows. You can override the following fields in other windows by changing the field values in a recipe:
Step Quantity - You use the Step Quantity field when computing the resource usage. If you enter a value in the Step Quantity field in the Recipe Details window, this value overrides the step quantity defined in the Routings window.
Factor - You use the activity Factor field to indicate how many times you must perform an activity per operation. If you enter a value in the Factor field on the Recipe: Organization Details window, this value overrides the activity factor defined in the Operation Details: Activities window.
Usage - You use the resource Usage field to indicate the amount of the resource consumed (usually expressed in hours) during the activity step. If you enter a value in the Usage field on the Recipe: Organization Details window, this value overrides the Usage field in the Operation Details Activity-Resource window.
Process Qty - You use the Process Qty field to indicate the total quantity of material processed by the resource during the activity step. If you enter a value in the Process Qty field on the Recipe: Organization Details window, this value overrides the Usage field in the Operation Details Activity-Resource window.
When setting up validity rules in OPM, consider the following:
A validity rule defines the primary product.
If the validity rule is global, then it is applied to all inventory organizations where the item can be produced.
The following validity rule functions can be used with ASCP:
Minimum and maximum quantities
Start and end effective dates
Preference (to break ties)
The OPM routing maps closely to the Oracle Bill of Materials routing but there are some restrictions. When setting up routings in OPM, consider the following:
The flexibility that OPM has for the routing quantity is restricted by Oracle Applications because the quantity must be in the unit of measure of the product being routed to scale properly. The integration takes care of any necessary conversions, but the user interface shows the converted quantity and unit of measure instead of the original quantity and unit of measure defined in OPM.
Resources are assigned a Plan Type indicating primary (1), auxiliary (2), or secondary (0) on the Resource window.
ASCP uses resource count and usage quantity information. You record resource count and usage quantity information in the Operations window. For example, if two identical blenders are used for mixing, enter 2 in the Count field. If the resource can mix 200 gallons per hour, enter 200 in the Process Quantity field and 1 in the Usage Quantity field.
Routing quantity uses the base UOM of the recipe product and is converted to the UOM of product.
OPM step equals Oracle Applications operation.
OPM activity equals Oracle Applications operation resource sequence.
OPM routing resource equal Oracle Applications operation resource.
Each activity must have ONLY one primary resource per step. If there were more, the first is selected and the others are ignored. If none exists, then activity is not reported.
Oracle Applications must know the items consumed at each step in the routing in order to calculate the capacity used at each step. Refer to the Oracle Process Manufacturing Product Development User's Guide for details on defining this association.
The Resource Information window defines a relationship between an organization and the resource. In Oracle Applications:
The resource is associated with an inventory organization. ASCP will have all the resources defined as a department in an inventory organization.
You can use ASCP to develop capacity plans for your resources. The resource inventory organization indicates to ASCP the need to perform capacity planning. The ASCP capacity planning functionality assumes that all resource capacity is measured in to the unit of measure you set up in the Profile Option MSC:Hour or is convertible to that UOM. The Assigned Quantity field on the Resource Information window indicates the number/quantity of the resource used in the specified inventory organization for which you are defining production costs and usage availability. The number you enter depends on how broad a resource categorization you are defining. For example, if you defined the resource as Blender 1 (a specific machine) you would enter 1. If you use three blenders in the production line, and you defined the resource as Blenders (rather than defining each individual machine) enter 3.
The cost of using a resource for one unit of measure (for example, the cost of running a mixer for one hour) that you define in OPM Cost Management is also used by ASCP, but this cost needs to be recorded in the Planning Cost field on the Resource Information window. ASCP assumes the unit of measure for all resources is an hour.