Perform the following tasks to set up this application.
This chapter covers the following topics:
You will need to perform some required setup in other applications. Set up these prerequisites prior to running the application. Refer to the details of these setup requirements provided in the individual application user guides. Depending on your requirements, there may be OPM related or additional setup required.
Set up the following in the Oracle Inventory application.
Inventory Organizations*
Organization Parameters*
Subinventories*
Locators*
Unit of Measure Classes*
Units of Measure*
Unit of Measure Conversions
Master Items
Organization Items
Select the Recipe Enabled indicator on the Process Manufacturing tab to use organization items in formulas and recipes.
(*Required)
See: Oracle Inventory User's Guide
Set up the following in the OPM Cost Management application.
Cost analysis codes
Cost calendar
See: Oracle Process Manufacturing Cost Management User's Guide
Set up the following in the OPM Process Planning application.
Resources
Plant Resources
See:Oracle Process Manufacturing Process Planning User's Guide
Set up the following in the Oracle E-Business Suite System Administrator's application.
The Recipe Designer uses a Thin Client Framework (TCF) technology. Two profile options are set up during the implementation:
TCF:HOST
TCF:PORT
See:
Setting User Profiles,Oracle E-Business Suite Setup Guide.
Profile Categories, Oracle E-Business Suite Setup Guide.
Set up Oracle Process Manufacturing (OPM) Product Development parameters in the Product Development Security Manager responsibility. You can set up parameters for new organizations, or query and modify parameters for existing organizations. Parameter values can vary by organization. These parameters control various functions in the Product Development application. For example, if version control for formulas is enabled for organization PR1, then at the point of saving a formula, the application checks the formula organization to determine whether or not to apply version control rules. Organization PR2 can have a different setting for formula version control.
To enter OPM Product Development parameters
Navigate to the Product Development Parameters window.
Enter Organization as the context inventory organization.
Organization Type is:
Plant for a manufacturing facility.
Laboratory for a research or lab facility.
Formula
Enter Allow Zero Ingredient Quantity as:
No to specify you cannot enter ingredients with zero quantity. An error displays when a zero ingredient quantity is entered. Default.
Yes to specify possible entry of a zero ingredient quantity.
Allow with warning to specify entry of a zero ingredient quantity with a warning message displayed. If you accept the warning, then you can proceed.
Enter Automatic Product Quantity Calculation as:
No to specify that formula product quantities are entered manually. Default.
Yes to specify that formula product quantities are calculated automatically based on the ingredients contributing to yield except for byproducts and distributed proportionally based on the product percentages. It can be changed at the formula level.
Enter Byproduct Active as:
Yes to access the By-Products window. Default.
No to restrict access the By-Products window.
Enter Default Consumption/Yield Type as:
Automatic By Step for automatic consumption of ingredients and automatic yield of products and byproducts as each step is completed. Default.
Manual for ingredients to default to manual consumption and inserted products and byproducts to default to manual yield.
Incremental for inserted items to default to incremental consumption or incremental yield.
Enter Default Formula Status as:
New to make changes at any time, assuming you have security access. Default.
Approved for Laboratory Use for use in laboratory batches and cost rollups for the laboratory.
Approved for General Use for use in production batches.
On Hold to specify the object cannot be used until the status is changed.
Frozen to prevent any further changes to the object and any dependent data.
Obsolete/Archived to specify the object can no longer be used unless the status is changed.
Enter Formula Security for Lot Genealogy as:
No to specify formula security rules are not enforced in lot genealogy. Default.
Yes to specify formula security rules are enforced in lot genealogy.
Enter Mass UOM as:
MASS to specify use of the mass unit of measure type when item quantities are converted to a common unit of measure for scaling, theoretical yield, and total output quantity. Default.
Another valid unit of measure type for conversion purposes. Set up this unit of measure type.
Enter Material Release Type as:
Automatic when ingredients quantities are consumed automatically.
Manual when ingredient quantities are consumed manually.
Incremental when ingredient quantities are backflushed by incremental backflushing.
Automatic by Step when ingredient quantities are consumed automatically as the step is released.
Enter Version Control as:
No to specify version control is not active for formulas. Changes can be made to an existing formula without the need to change its version. Default.
Yes to specify full version control is active for formulas. Changes made to a formula require a new version. This excludes changes to formula status, mark for purge, and the Undelete functionality.
Optional to specify version control is discretionary for formulas. You can create a new version when you update an existing version.
Enter Version Control Attribute Set as a version control attribute set you have created for Formula using the Version Control Attributes user interface. Note that the list of values will display only the corresponding list of version control attribute sets you created for the Formula entity. See: Setting Up Version Control Attribute Sets.
Enter Volume UOM as:
VOL to specify use of the volume unit of measure type when item quantities are converted to a common unit of measure for scaling, theoretical yield, and total output quantity.
Another valid unit of measure type for conversion purposes. Set up this unit of measure type.
Enter Yield UOM as:
MASS to specify use of the mass unit of measure type when item quantities are converted to a common unit of measure for scaling, theoretical yield, and total output quantity. Default.
VOL to specify use of the volume unit of measure type when item quantities are converted to a common unit of measure for scaling, theoretical yield, and total output quantity.
Another valid unit of measure type for conversion purposes. Set up this unit of measure type.
Operation
Enter Default Operation Status as:
New to make changes at any time, assuming you have security access. Default.
Approved for Laboratory Use for use in laboratory batches and cost rollups for the laboratory.
Approved for General Use for use in production batches.
On Hold to specify the object cannot be used until the status is changed.
Frozen to prevent any further changes to the object and any dependent data.
Obsolete/Archived to specify the object can no longer be used unless the status is changed.
Enter Version Control as:
No to specify version control is not active for operations. Changes can be made to an existing operation without the need to change its version. Default.
Yes to specify full version control is active for operations. Changes made to an operation require a new version. This excludes changes to operation status, mark for purge, and the Undelete functionality.
Optional to specify version control is discretionary for operations. You can create a new version when you update an existing version.
Enter Version Control Attribute Set as a version control attribute set you have created for Operation using the Version Control Attributes user interface. Note that the list of values will display only the corresponding list of version control attribute sets you created for the Operation entity. See: Setting Up Version Control Attribute Sets.
Routing
Enter Default Routing Status as:
New to make changes at any time, assuming you have security access. Default.
Approved for Laboratory Use for use in laboratory batches and cost rollups for the laboratory.
Approved for General Use for use in production batches.
On Hold to specify the object cannot be used until the status is changed.
Frozen to prevent any further changes to the object and any dependent data.
Obsolete/Archived to specify the object can no longer be used unless the status is changed.
Enter Step Release Type as:
Automatic to indicate that the step is automatically released or completed when subsequent steps are released or completed.
Manual to indicate that the step is released manually.
Enter Enforce Step Dependency as:
No to specify step dependency is not enforced. Default.
Yes to specify step dependency is enforced.
Enter Version Control as:
No to specify version control is not active for routings. Changes can be made to an existing routing without the need to change its version. Default.
Yes to specify full version control is active for routings. Changes made to the routing header or organization specific details require a new version.
Optional to specify version control is discretionary for routings. You can create a new version when you update an existing version.
Enter Version Control Attribute Set as a version control attribute set you have created for Routing using the Version Control Attributes user interface. Note that the list of values will display only the corresponding list of version control attribute sets you created for the Routing entity. See: Setting Up Version Control Attribute Sets.
Recipe
Enter Default Recipe Status and Default Validity Rule Status as follows:
New to make changes at any time, assuming you have security access. Default.
Approved for Laboratory Use for use in laboratory batches and cost rollups for the laboratory.
Approved for General Use for use in production batches.
On Hold to specify the object cannot be used until the status is changed.
Frozen to prevent any further changes to the object and any dependent data.
Obsolete/Archived to specify the object can no longer be used unless the status is changed.
Enter Process Instruction Paragraph as:
NULL if the process instruction paragraph is not used. Default.
A user-defined paragraph code to define process instruction entry using the standard Text Editor functionality. Process instructions entered in the Recipe Designer are stored against this paragraph code.
Enter Recipe Type as:
Master to indicate that the default recipe type is process cell specific. Master recipes define exactly how a product is made in a specific process manufacturing cell.
Site to indicate that the default recipe type is at the site level. There is one site recipe for each site that makes the product, or some portion of the product. A site recipe has the same structure as a general recipe, but may be modified for the local language and unit of measure. It may also be modified to take into account local material availability, or it may only define a part of the general recipe that is actually performed on the site.
General to indicate that the default recipe type is one general recipe for each specific product variation made by a company. It defines, in an equipment independent manner, the material and process dependencies required to make a product. The general recipe is usually created during or after the pilot plant scaleup of a research and development recipe.
Enter Version Control as:
No to specify version control is not active for recipes. Changes can be made to an existing recipe without the need to change its version. Default.
Yes to specify full version control is active for recipes. Changes made to the recipe header or organization specific details require a new version. This excludes changes to validity rules, step material association, recipe step quantities, customers, recipe status, mark for purge, and the Undelete functionality.
Optional to specify version control is discretionary for recipes. You can create a new version when you update an existing version.
Enter Version Control Attribute Set as a version control attribute set you have created for Recipe using the Version Control Attributes user interface. Note that the list of values will display only the corresponding list of version control attribute sets you created for the Recipe entity. See: Setting Up Version Control Attribute Sets.
Substitution
Enter Default Substitution Status as:
New to make changes at any time, assuming you have security access. Default.
Approved for Laboratory Use for use in laboratory batches and cost rollups for the laboratory.
Approved for General Use for use in production batches.
On Hold to specify the object cannot be used until the status is changed.
Frozen to prevent any further changes to the object and any dependent data.
Obsolete/Archived to specify the object can no longer be used unless the status is changed.
Enter Version Control as:
No to specify version control is not active for recipes. Changes can be made to an existing substitution list without the need to change its version. Default.
Yes to specify full version control is active for substitution lists. Changes made to the item substitution list or organization specific details require a new version. This excludes changes to status, mark for purge, and the Undelete functionality.
Optional to specify version control is discretionary for substitution lists. You can create a new version when you update an existing version.
Laboratory
Enter Costing Source Organization as the default organization for least-cost formulation. All process-enabled inventory organizations are available.
Enter Version Control as:
No to specify version control is not active for formulation specifications. Changes can be made to an existing formula specification without the need to change its version. Default.
Yes to specify full version control is active for formulation specifications. Changes made to the formula specification header or organization specific details require a new version.
Optional to specify version control is discretionary for formulation specifications. You can create a new version when you update an existing version.
You can find Oracle Process Manufacturing (OPM) Product Development parameter set for a local or global organization using the Find Default Configuration Parameters window.
To find Product Development parameters
Navigate to the Find Product Development Parameters window.
Enter any of the following to narrow your search:
Organization name.
Description of the organization.
Organization type as Plant or Laboratory.
Click Find.
The following table lists the profile options for Oracle Process Manufacturing Product Development:
| Profile Option | Description | Default | Options | Recommended Level Change |
| GMD: Automatic Generation Of Step Dependency Attributes | This profile option determines whether step dependency attributes are generated automatically in the Routing Designer | No | No Yes |
Site |
| GMD: Automatic Step Number Generation | This profile option determines whether to generate a step number automatically when adding a step in the Routing Designer window | No | No Yes |
Site |
| GMD: Default Dependency Type | This profile option indicates the default dependency type to use when step dependency attributes are generated automatically | Lab | A valid laboratory organization | Site |
| GMD: Default Lab Organization | This profile option defines the default laboratory to be used in the OPM Product Development application | Lab | A valid laboratory organization | Site |
| GMD: Density | This profile option sets the literal that displays for the Density technical parameter. Do not change this profile option | Density | None | Site |
| GMD: Designer Category Set | This profile option sets the categories that appear in the Item Master list on the Recipe Designer window | Blank | A valid category set | Site |
| GMD: Designer Display New Item Window | This profile option displays the New Item window to add a new item to a formula. When it is set to No, the New Item window does not display | Yes | No Yes |
Site |
| GMD: Display Step Qty In Routing Graph | This profile option is used to display the transfer percentage in the Routing Step Dependency graph | Yes | No Yes |
Site |
| GMD: Display Transfer Pct in Routing Graph | This profile option is used to display the transfer quantity in the Routing Step Dependency graph | Yes | No Yes |
Site |
| GMD: Display Transfer Qty in Routing Graph | This profile option is used to display the transfer quantity in the Routing Step Dependency graph | Yes | No Yes |
Site |
| GMD: Sample Closed Batches | This profile lets you specify whether WIP samples can be taken against closed batches. The Batch list of values in the Item Samples window displays WIP, Completed, and Closed batch statuses, if the Source is WIP, according to the value you select for this profile. Select Yes to enable the creation of samples for WIP, Completed, and Closed batch statuses. Select No to enable the creation of samples for WIP and Completed, but not Closed batch statuses. |
No | No Yes |
Site |
| GMD: Technical Parameter Category Set | This profile option lets you aggregate a group of technical parameters for an item and organization combination. When you enter a valid category set, it displays as the default category on the Technical Parameter Sequences window. | Blank | A valid category set | Site |
| GMD: User Name for ALL | This profile option is the user name that represents all users when creating a product development security profile. The GMD: User Name for ALL profile option is controlled at the site level, because it is the value that formula security uses to indicate that all users for an organization are given a certain level of access to formulas | Null | A valid Oracle Applications user | Site |
| GMD: Workflow Timeout (in Days) | This profile option is used to calculate the time interval for sending reminder notifications to an approver. The value entered is divided by four to determine the time interval for the reminder notifications in days; only four notifications are sent. If this value is null, then the application does not send a reminder notification to the approver. For example, if the value is set to eight, then the approver gets a reminder notification at two-day intervals. After the fourth notification, the initiator is sent a notification that the approver is not responding. | None | Positive whole number of calendar days for the workflow timeout. | Site |
| GMD: Update On-hand Status in All Locators | This profile option controls whether the final sample group disposition can update the status of on-hand lot inventory in all locators or only the locator specified at the time of sample creation. If set to the default value, Yes, this profile option allows the material status change across all locators where on-hand inventory exists for the lot. If set to No, it will strict the material status change to the locator where the sample is created and on-hand inventory exists for the lot. | Yes | No Yes |
Site |
Depending on your security profile, every function may not be available to you. Contact your Product Development Security Manager or Product Development Security Profile Manager if you require access to this information.
See: Setting Up Windows Security
See: Oracle Process Manufacturing Product Development, Formula Security, Part No. E11065-01.
The System Administrator or Product Development Security Manager controls editing privileges by assigning you to the owner organizations you need to access. Each of the windows listed below validates your access privileges. If you do not have access to the Owner Organization, then the data on the window is restricted to query only. Otherwise, data can be queried and edited.
Recipe editing privileges also restrict changes to existing step material associations. Edit text associated to routings, operations, recipes, and recipe validity rules can be restricted so that the associated edit text is query only. You can only update global and local recipe validity rules when they are granted access to the recipe owning organization.
In addition to formula security, following are windows that validate your access privileges:
Process Operation Details Activities (GMDOPRED.fmb)
Operation-Activity Line (GMDOACLN.fmb)
Operation Activity Resource Line (GMDORALN.fmb)
Routing Details (GMDROTED.fmb)
Routing Step Line (GMDRSTLN.fmb)
Routing Step Dependencies (GMDSDPED.fmb)
Recipe Step/Material Association (GMDRSAED.fmb)
Recipe Details (GMDRCPED.fmb)
Recipe Organization Details (GMDRCOED.fmb)
Recipe Validity Rules (GMDRVRED.fmb and GMDRVRSM.fmb)
Routing Designer (GMDRTDSG.fmb)
Routing Properties (Routing Designer) (GMDRTDSG.fmb)
Routing Preferences (Routing Designer)
Recipe Designer (GMDRCDSG.fmb)
Recipe Properties (Recipe Designer) (GMDRCDSG.fmb)
Recipe Preferences (Recipe Designer)
Step Properties (Routing Designer) (GMDRTDSG.fmb)
See: Setting Up Security Profiles
See: Oracle Process Manufacturing Product Development, Formula Security, Part No. E11065-01.
Formula Classes group formulas with similar characteristics and requirements for reporting purposes. For example, use a formula class to classify all formulas for ACRYLIC paints, or to classify all formulas for ORGANIC paints. Food seasoning formulas could be grouped under a SEASONINGS class. Specify the formula class in the Formula Details window. Defining formula classes is optional. Formula classes are set up using the Formulator responsibility.
Analyze all formulas for common properties that are used to classify them.
To set up formula classes
Navigate to the Formula Classes window.
Enter the Class code that identifies formulas with similar characteristics or requirements. Required.
Enter a brief Description of the classification you are adding. Required.
Additional Information: Choose Find from the View menu to display the Find Formula Classes window. Enter appropriate fields to narrow your search, and click Find.
Group operations with similar characteristics and requirements for reporting purposes. For example, set up classes for MIXING, HEATING, DRYING, or GRINDING. Defining process operation classes is optional.
Analyze all operations for common properties that are used to classify them.
To set up process operation classes
Navigate to the Process Operation Classes window.
Enter the Class code that identifies operations with similar characteristics or requirements. Required.
Enter a brief Description of the classification you are adding. Required.
Additional Information: Choose Find from the View menu to display the Find Process Operation Classes window. Enter appropriate fields to narrow your search, and click Find.
Routings are sequenced sets of operations performed in order to complete a production batch. It is useful to set up process routing classes to group process routings with similar characteristics and requirements for reporting purposes. Defining process routing classes is optional. UOM is required if the theoretical process loss is defined for the process routing class.
Analyze all process routings for common properties that are used to classify them.
To set up process routing classes
Navigate to the Process Routing Classes window.
Enter the Class code that identifies routings with similar characteristics or requirements. Required.
Enter a Routing Class Description for the Class code entered. Required.
Enter the UOM for the Class code.
Click Process Loss to display the Process Loss window.
See:
Activities are actions performed during production. For example, mixing and cooling are activities. Set up activities to divide a manufacturing process into logical breakpoints. You can improve working methods and reduce time by analyzing and refining the granularity of activities, to complete activities performed in operations in the shortest possible time with the least effort to deliver the appropriate level of quality.
Cost analysis codes are assigned to activities so that proper cost calculations are computed. You need to set up cost analysis codes to define activities.
See: Defining Cost Analysis Codes, Oracle Process Manufacturing Cost Management User's Guide.
To set up activities
Navigate to the Activities window.
Enter an Activity Code for the name of the activity. Activities are the components that make up an operation. Required.
Enter a brief Description of the activity. Required.
Enter the Cost Analysis Code. This code is set up in the OPM Cost Management application. Required.
Additional Information: Choose Find from the View menu to display the Find Activities window. Enter appropriate fields to narrow your search, and click Find.
Most organizations manufacture a variety of similar products that are often grouped into product lines or families. The same technical parameters are likely to be relevant to the products within a product family, and to the ingredients used to manufacture those products. For example, viscosity is likely to be relevant to all lubricants, while opacity or contrast ratio is likely to be relevant to all paints.
Laboratory organizations are inventory organizations defined as laboratories in the Product Development parameters. Items defined in a formula are organization-specific, and laboratory organizations are used to group these items (ingredients) for product formulas. This enables you to view technical parameters linked from a laboratory to a batch, and perform organization-specific validations.
Although production batches are generated from a plant or a lab, you can view local technical parameters that are linked from a lab to a production batch produced in a plant. Items defined in a formula are organization-specific. Validations are performed in product development to ensure that the formula items are enabled in production for organization-specific validity rules. This validation is performed when there is a validity rule status change. This validation is deferred for global validity rules.
To set up laboratory organizations
Navigate to the Product Development Parameters window.
Select Find to navigate to the Find Product Development Parameters window.
Search for an existing Inventory organization using any of the following criteria:
Organization
Description
Organization Type
Select Find to display an applicable record.
The selected record displays values in the Organization and Description fields.
In the Organization Type region, enable the Laboratory check box. .
You can set the type as both a plant and a laboratory.
Laboratories are used to group technical parameters. Select the parameter applicable to your product type.
For example, in the Formula tabbed region, set the Mass UOM type and the Volume UOM type parameters for converting density in the Simulator calculations.
Save your work.
Technical parameters are characteristics of items to measure and calculate. These parameters are either global or lab-specific attributes that are ultimately associated with items in a formula. These are not item specific, however a laboratory organization is required to create them. There are several types of technical parameters. For example, a gravimetric technical parameter for percent solids by weight (w/w) is Weight%. Technical Parameters can function as expressions, numeric ranges, list values, character values, or link to quality tests. The Density technical parameter must be set up for every item in a formula using the Item Technical Data window. Density is used to calculate weight and volume totals and percents.
Supported technical parameter types include:
Weight Percent – entered as a percent for each ingredient. A total weighted percent is computed for the product.
Volume Percent – entered as a percent for each ingredient. A total weighted percent by volume is computed for the product. Density technical data is used to convert from weight to volume.
Specific gravity – entered as the relative density for a specific ingredient. Specific gravity is used to compute the specific gravity for the product.
Cost – entered as a cost per unit for each ingredient or byproduct. Cost is used to compute the total unit cost for the product.
Equivalent Weight – entered as the equivalent weight for the product. Equivalent weight is calculated by setting up the technical parameter for an atomic weight and entering technical data for the total positive ionic valence to account for equivalent weight of a material.
Quantity per Weight – entered as the quantity of the material required for the formula/batch divided by the weight in another unit of measure.
Expression or Product Expression – entered as a calculated technical parameter that uses the supported mathematical functions or individual values from other technical parameters entered.
For each type of technical parameter, specify the constraints on the data for that parameter, such as the minimum and maximum values.
When using global technical parameters across multiple labs, technical parameters must be independent of the lab organization. To create a global technical parameter, do not enter an organization. The Organization field displays the default organization defined in the profile GMD: Default Lab Organization. Technical parameters that belong to different labs are queried on this window. The record is protected if your current responsibility does not have access to the lab organization displayed.
Ensure you have completed the following prerequisites:
Define a laboratory organization.
Determine the hierarchy of technical parameters to set up. For example, density, gram percent, gram molecular weight, formula weight, and osmolality are developed to sequence in a hierarchy that can be rolled up to the product level.
To use expressions in technical parameters:
| Symbol | Meaning | Example |
|---|---|---|
| + | Addition | PARAM1+PARAM2 Adds PARAM1 to PARAM2 |
| - | Subtraction | PARAM1-PARAM2 Subtracts PARAM2 from PARAM1 |
| * | Multiplication | PARAM1*PARAM2 Multiplies PARAM1 and PARAM2 |
| / | Division | PARAM1/PARAM2 Divides PARAM1 by PARAM2 |
| POWER | Exponentiation | POWER(PARAM1,2) Raises PARAM1 to the power of 2 POWER(PARAM1,3) Raises PARAM1 to the power of 3 |
| SQRT | Square Root | SQRT(PARAM1) The square root of PARAM1 |
| LOG | Common Logarithm | LOG(PARAM1) The common log of PARAM1 |
| LN | Natural Logarithm | LN(PARAM1) |
| ( ) | Parentheses | (PARAM1+PARAM2)/(PARAM3-PARAM4) Adds PARAM1 to PARAM2 and divides the result by the sum of PARAM3 minus PARAM4. |
| QTY$ | Variable that represents the quantity of an ingredient or byproduct | QTY$*2 Multiplies the quantity of an ingredient or byproduct by 2. |
| VOL$ | Variable that represents the volume of an ingredient or byproduct | VOL$*2 Multiplies the volume of an ingredient or byproduct by 2. |
| ISUM | Sums the parameter or value for all ingredients | ISUM(PARAM1) ISUM(QTY$) ISUM(VOL$) Sums all the ingredient quantities by weight and volume. |
| BSUM | Sums the parameter or value for all byproducts | BSUM(PARAM1) BSUM(QTY$) BSUM(VOL$) Sums all the byproduct quantities by weight and volume. |
Important: Do not put spaces (blanks) in the name of a technical parameter that you use in an expression. (PARM 1)*(PARM 2) cannot be calculated because of extra spaces in the parameter name.
To use fixed expressions in technical parameters:
Certain technical parameters are fixed expressions that sum all ingredients in a formula (also called a formula rollup). Expressions are equations you define that use mathematical operators and previously defined technical parameters.
For example, you can define a technical parameter as a percent solvent (by weight), with each ingredient in a formula contributing a differing portion of its weight to a product as solvent. Use the Technical Parameters window to set up various quantitative relationships between these individual parameters to find the weight of solvent contributed by each ingredient and calculate the sum of these contributions. After determining the total formula weight, the ratio of percent solvent for each product by its weight is calculated.
Calculations such as total weight and total volume are available for use in expressions. When a technical parameter is used within an expression, the product total value of the parameter may be required rather than individual ingredient values.
The Product Expression data type defines technical parameters to roll up to the product value. ISUM and BSUM are functions provided to indicate a total rollup sum to perform on ingredients and byproducts, respectively. The variable QTY$ is the ingredient or byproduct quantity in the standard UOM defined by the UOM Mass type parameter. VOL$ is the ingredient or byproduct quantity in the standard UOM defined by the UOM Volume type parameter. Set up UOM conversions for mass and volume so that Simulator calculations are accurate.
In addition to the technical parameters that you define on the Technical Parameters window, OPM creates a technical parameter for density when you define a laboratory organization. The density technical parameter is used to convert from mass units of measure to and from volume units of measure. It does not use the item specific unit of measure conversions. It does, however, use the regular unit of measure conversions for formulas. Enter data for the DENSITY technical parameter for all items where you must convert mass to volume or volume to mass.
The GMD: Density profile option must be set to Density for the Simulator to calculate values correctly.
If a technical parameter is associated with a quality test, then the data type of the parameter defaults to the test data type. If the test data type is numeric, then you can change the data type to weight percent, volume percent, equivalent weight, or quantity per unit.
Following are typical expressions you can set up:
| Parameter Type | Description | Example |
|---|---|---|
| Weight Percent | The percent of the total weight for a specific parameter. It is often used to measure the total percent solids expressed in the primary inventory UOM. | Fat Percent is 1.2 g% = 1.2 grams of fat per 100 grams of total material Total Solids is 5 oz% = 5 ounces of solids per 100 ounces of total material |
| Volume Percent | This is the percent of the total volume for a specific parameter. It is often used to measure the total percent by volume. | Ethanol percent is 40% by volume = 40 milliliters of ethanol per 100 milliliters of total volume |
| Specific Gravity | The ratio of the mass of a solid or liquid to the mass of an equal volume of distilled water at 4 degrees C (39 degrees F). Also called relative density. | Specific gravity can be applied across any units. The density of pure water is 62.4 pounds per cubic foot. If a sample of ethyl alcohol has a specific gravity of 0.785, then its density is 0.785 * 62.4 = 49 pounds per cubit foot. |
| Cost | The unit cost of an item. | Use the standard or forecasted cost of an item. |
| Equivalent Weight | The atomic weight of a compound divided by the total positive ionic valence. | Sulfuric acid has a gram molecular weight of 98 g. Its total positive ionic valence is +2. Therefore, the equivalent weight of sulfuric acid is 49. |
| Quantity per Unit | Relative amount of material present based on the primary inventory unit of measure versus the unit of a mass assigned. | Assigned unit of mass is in grams, and inventory unit of measure is in pounds. 1 gram = 0.00220462262 pounds. Therefore, 1 kilogram is 2.20462262 pounds. So the quantity per unit is 2.20462262 pounds per kilogram. |
| Expression | The algorithm entered using supported or defined variables for an ingredient or byproduct. | Set up an expression to adjust ingredient or byproduct factors. For example, to calculate dry material weight from a material with a reported 12% moisture content, set up PARAM2=QTY$-(QTY$*0.12). |
| Product Expression | The algorithm entered using supported or defined variables for a product. | Set up a product expression to adjust required factors for the product. For example, it is known that the packaging required is approximately 40% of the weight of the finished product. Set up PARAM3=QTY$*1.4 to estimate the sum of the finished product and its packaging. |
| Derived Cost | An alternate means of deriving cost using an external costing method. | See: To use the Derived Cost technical parameter. |
To use the Derived Cost technical parameter:
Prior to using the Derived Cost technical parameter, set up inventory items and assign them to each laboratory organization where they are used. Create new least cost formulation item categories and category sets and assign the items to these category sets. Set up standard, actual, and lot costs for these items. The laboratory selected when you open the Technical Parameters window is used for the derivation of process costs. The Cost Type field is enabled when you select Process Cost as the cost source. The Cost Type is validated against the cost methods master. If you select Cost Function as the external cost functionality, then the default seeded package GMD_LCF_UTIL.Get_Cost is used. This package can be modified to fetch costs from external cost entities. The function has standard parameters of Item_Id, Organization_Id, Lot_Number, Qty, and UOM. You can select a cost parameter for one technical parameter in each laboratory. This parameter is used to calculate the least cost batch using the default laboratory profile value.
To set up technical parameters
Navigate to the Technical Parameters window.
Enter the code for the Laboratory where you are defining a technical parameter. The Laboratory Description displays. To define a global technical parameter, clear the field.
Enter the name of the technical Parameter. Required.
Enter a Description or statement about what the technical parameter represents. Required.
To link this technical parameter to a test in the OPM Quality Management application, enter the name of the Quality Test. The Test Description displays. Otherwise, leave this field blank.
Select the Data Type to associate with this technical parameter. Enter the information required in the appropriate tab. If a data type requires entry of a unit code, then the unit description displays.
Character is the ASCII character data type:
Enter Minimum as the lowest valid character string value based on the ASCII sort sequence.
Enter Maximum as the highest valid character string value based on the ASCII sort sequence.
Validation List is a valid list of criteria to meet for the technical parameter entered:
Enter Unit Code as the unit of measure for the list.
Enter each line as an alphanumeric character string that meets the criteria for the list named by the parameter.
Boolean is a TRUE or FALSE validation:
No entry is required on this field.
When Boolean is defined as a technical parameter, it is validated as TRUE or FALSE.
Quantity Per Unit is a unit quantity technical parameter.
Product Expression is a technical parameter for an expression to apply to a product.
Expression is a technical parameter for a mathematical expression:
Enter Unit Code as the unit of measure for the expression.
Enter a valid mathematical or PL/SQL expression.
Numeric is the numeric data type.
Weight Percent is a parameter for weight per hundred weight units.
Volume Percent is a parameter for volume per hundred volume units.
Specific Gravity is a parameter for specific gravity.
Cost is a parameter for cost calculation.
Equivalent Weight is a parameter for equivalent weight calculation.
Enter the Unit Code.
Enter the Minimum value.
Enter the Maximum value.
Enter the Decimal Precision as the number of significant digits required.
Derived Cost is the technical parameter used in least cost formulation.
Enter Cost Source as Process Cost when the cost source is from an Oracle Process Manufacturing application, or enter it as External Source when the cost is derived from an outside application.
Cost Type is the cost method used with its Description. Typically, this is a standard cost or actual cost.
Enter Cost Function when you use an external cost functionality. If you use an external cost function, then you need to enter parameters.
Select Default Cost Parameter to use the derived cost for a batch in the OPM Process Execution application. Validity rules display based on this parameter value.
Additional Information: Choose Find from the View menu to display the Find Technical Parameters window. Enter appropriate fields to narrow your search, and click Find.
Enter technical parameter sequences for the laboratory organizations and items that your responsibility can access. After entering the technical parameters for a laboratory organization, specify the order displayed as the technical parameter sequences.
The Technical Parameter Sequences window establishes which technical parameters to use for a simulation, and the order in which they display. All technical parameters defined locally for the laboratory organization are available, but can be deleted on an individual basis. Global technical parameters, as well as technical parameters grouped as item category sets, can be selected for the simulation from this window. There are three levels of flexibility in defining technical parameter sequences: Organization, Organization Item, and Organization Item Category.
When specifying a category, the category list displays all categories defined for the item category set up in Oracle Inventory. The GMD: Technical Parameter Category Set profile option lets you aggregate a group of technical parameters for an item and organization combination. When you enter a valid category set for this profile option, it is displays as the default Category on the Technical Parameter Sequences window.
Expression type technical parameters that refer to other technical parameters must come after the technical parameters they reference in the sequence. For example, if PARM_3 is calculated by multiplying PARM_1 by PARM_2, PARM_3 must come after PARM_1 and PARM_2 in the technical parameter sequences. By default, the DENSITY technical parameter, or its equivalent is 1. Do not change this.
Keep in find the following prerequisites:
Determine if two or more technical parameters are required in a calculation. If they are, verify their proper order prior to sequencing them in the Technical Parameter Sequences window.
If they are, verify their proper order prior to sequencing them in the Technical Parameter Sequences window.
For example, if you want to determine a Brix-to-Acid ratio, first enter the Brix calculation, then the Acid calculation, and finally, the Brix/Acid calculation.
To set up technical parameter sequences
Navigate to the Technical Parameter Sequences window.
Enter the code for the Laboratory where you are setting up technical parameter sequences. The Laboratory Description displays.
Enter the Item to display technical parameters associated with that item. The Item Description displays.
Enter Category to display technical parameters associated with the item class. The Category Description displays.
Parameter Sequence
Global is selected when a global parameter is entered.
Enter the code for a technical Parameter associated with the laboratory organization entered. For example, enter GMW for gram molecular weight.
Enter a Sort number between 1 and 9999 to determine where to display this parameter in the complete list of technical parameters. When entering technical parameter data, the technical parameters are displayed in numerical order based on the number entered in this field. You can enter numbers to accommodate future additions of technical parameters. For example, you can enter 10, 20, 30, to accommodate future addition of technical parameters between 10 and 20, 20 and 30, and so forth.
When Quality Control is selected, the technical parameter links to a quality test.
Description displays the test description entered for quality linked technical parameters.
Additional Information: Choose Find from the View menu to display the Find Technical Parameter Sequences window. Enter appropriate fields to narrow your search, and click Find.
Use the Item Technical Data window to assign one or a series of parameter values to a recipe enabled item, item and lot combination, batch, or formula. Items entered must be recipe enabled. Use this window to derive item technical data from quality test results. Once you have specified a sequence for technical parameters, enter the technical parameter data. Changes made to item technical parameter values also change the properties of a simulation. The Batch and Formula fields in this window are mutually exclusive. Batch fields are disabled if the formula option is selected. Formulas and batches must be accessible to your responsibility. Batches and lots are controlled by their respective inventory organizations.
You can define technical data for all lots derived from a parent lot when item lot control is set to Full Control for the laboratory where you define the technical data.
If an organization and lot value are entered, then batch specific values are entered only for the batches that belong to the lot organization. Item technical data belonging to different laboratories can be queried on this window. The record is protected if your responsibility does not have access to the laboratory.
The application uses the DENSITY technical parameter for unit of measure conversions. Set up the GMD: Density profile option before entering item technical information. Enter values for this technical parameter for all your raw materials. If you set up item technical data, then a density value must be entered for items, and each lot of an item.
If you receive a unit of measure conversion error on the Simulator, then verify that you entered density information for all of your raw materials.
Enter density values as a ratio between the base unit of measure for the mass unit of measure type and the base unit of measure for the volume unit of measure type.
The base unit of measure for each UOM type is the first unit of measure set up for that UOM type. For example, if the base unit of measure for mass is kilograms and the base unit of measure for volume is liters, then enter the density in kilograms per liter rather than pounds per gallon.
You can determine the units of measure that are the base units for mass and volume. The units that display beneath the word Conversion are the base units used for mass and volume.
If you need to enter Item Technical Data for products, and you recalculate those technical parameter values on the Simulator, then data that you entered on the Item Technical Data window is overwritten if you use the Simulator to update the originally entered technical data.
Item Technical Data associates Technical Parameters at the item, formula, and lot levels. Item Technical Data also associates technical parameters with batches.
Ensure you have completed the following prerequisites:
Set up technical parameters.
Set up technical parameter sequences.
To enter technical data for items
Navigate to the Item Technical Data window.
Enter the Laboratory where you are defining item technical data. The Laboratory Description displays. Enter data only for the technical parameters associated with this laboratory. Required.
Enter the Item code to associate to technical data. The Item Description displays. Required.
If you enter technical data for a specific lot:
Enter the inventory Organization that owns the lot.
Enter the Lot number. The lot Description displays.
Select Formula or Batch to target a specific formula or batch for technical data entry:
Enter the Formula and Version to enter formula-specific technical data.
Enter the Plant and Batch number for entering batch-specific technical data.
Details
The name of each technical Parameter defined by the sort sequence for the laboratory organization displays. You cannot edit these fields.
Enter the Value for each technical parameter. You cannot enter or edit this field if the technical parameter value is calculated by the application.
For example, you cannot enter or edit this field if the Value is an Expression or if it is derived from a quality test. The value you enter must satisfy the validation parameters displayed at the bottom of the window if entering a numeric value. Otherwise, the value must be in the LOV if the Validation List method is selected as the Data Type.
The following fields are display only:
Unit is the unit of measure for the technical parameter.
Quality Control indicator. If the indicator is selected, then the value for the technical parameter comes from an OPM Quality Management test or result
Data Type is the technical parameter data type. You cannot edit this field.
Decimal Precision is the number of significant figures assigned to the technical parameter.
Calculate indicator. If the indicator is selected, then the technical parameter is calculated by the application.
Minimum Range is the minimum ranged assigned to the technical parameter.
Maximum Range is the maximum range assigned to the technical parameter.
To find item technical data
Navigate to the Find Item Technical Data window.
Enter any of the following to narrow your search:
Organization to find item technical data for a specific organization. Make no entry here to search for global item technical data.
Item to find item technical data for a specific item. The combination of organization and item refine this search to a specific item in a specific organization.
Lot to find item technical data that is lot-specific.
Formula to find item technical data associated to a specific formula and Version.
Plant to find plant-specific item technical data.
Batch to find batch-specific item technical data.
Marked for Deletion to include only item technical data that is marked for purge.
The following procedures set up Technical Classes and Technical Subclasses for items. Access the Key Flexfield Segments window from the System Administrator responsibility. In formula analysis, view results for the contribution of Technical Class or Technical Subclass in either weight or volume.
To create key flexfields for technical class and technical subclass
Navigate to the Key Flexfield Segments window.
Choose Find from the View menu to find all Key Flexfield Segments entered for the Oracle Inventory Item Categories Flexfield Title. Technical Class and Technical Subclass are Item Categories associated to the Oracle Inventory application. The Key Flexfield Segments window displays all flexfields defined for the Flexfield Title of Item Categories.
Insert a new row to create the Technical Class and Technical Subclass definition.
Enter the Code as TECH_CLASS_SUBCLASS. The Title defaults to the Code.
Enter the Title and Description as Technical Class & Subclass.
Click Segments. The Segments Summary window displays for Technical Class & Subclass.
Enter two segments with the following values, and leave the Value Set blank:
Technical Class, with a Window Prompt of Technical Class and a Column of SEGMENT1
Technical Subclass, with a Window Prompt of Technical Subclass and a Column of SEGMENT2
Save your work.
Click Value Set. The Value Sets window displays.
Enter the Value Set Name as TECHNICAL_CLASS.
Description displays Technical Class.
Enter a Maximum Size.
Choose Save and Proceed. The TECHNICAL_SUBCLASS Value Set Name displays.
Description displays Technical Subclass.
Enter a Maximum Size.
Save your work.
The Segments Summary (Item Categories) - Technical Class & Subclass window displays the entries for Technical Class and Technical Subclass.
Find a Value Set of TECHNICAL_CLASS for Technical Class.
Find a Value Set of TECHNICAL_SUBCLASS for Technical Subclass.
Save your work.
Return to the Key Flexfield Segments window to freeze the flexfield definitions.
Select Freeze Flexfield Definition. A caution message displays to indicate that flexfields can be unfrozen, but that doing so can cause problems once you have entered data in the flexfield.
Click OK.
Click Compile to establish the flexfield structure. The following message displays:
Compiling flexfield definition.
Click OK.
After compilation, a concurrent request is submitted to generate a flexfield view. The following message displays:
The flexfield was compiled successfully. Submitted request to generate flexfield view...
Click OK.
Check completion of the concurrent program by viewing submitted requests.
Define Technical Class & Subclass values.
To define technical class and subclass values
Navigate to the Segment Values window.
Enter the following in the Find Key Flexfield Segments window:
Enter Oracle Inventory as Application.
Enter Item Categories as Title.
Enter Technical Class & Subclass as the Name of the structure created.
Click Find.
Query Technical Class as the Independent Segment.
Enter an appropriate Value, Translated Value, and Description for Technical Class. For example, enter:
Binder as Value, Translated Value, and Description
Solvents as Value, Translated Value, and Description
The values display as allowable values for the Technical Class LOV.
Select Enabled.
Choose Save & Proceed.
Query Technical Subclass as the Independent Segment.
Enter an appropriate Value, Translated Value, and Description for Technical Subclass. For example, enter:
Acrylic as Value, Translated Value, and Description
Alkyd as Value, Translated Value, and Description
Epoxy as Value, Translated Value, and Description
Organic as Value, Translated Value, and Description
The values display as allowable values for the Technical Subclass LOV.
Select Enabled.
To define categories
Navigate to the Codes window. The Find Categories window displays.
Click New.
Enter Technical Class & Subclass.
Enter each Category multisegment flexfield structure to assign meaning to each segment. For example, enter:
Binder.Acrylic for an acrylic binder
Binder.Alkyd for an alkyd binder
Binder.Epoxy for an epoxy binder
Enter an appropriate Value for each Segment.
Click OK. Return to the Categories window.
Enter a unique Description for each Category. For example, Binder.Acrylic could have the Description Binder/Acrylic.
To define category sets
Navigate to the Category Sets window.
Select the appropriate Inventory Organization.
Click OK.
Enter a unique Name and Description for the Category Set. For example, enter:
Technical Classification as Name
Component Technical Classification as Description
Enter the Flex Structure created. For example, enter Technical Class & Subclass.
Verify that the Category Set is controlled at the Master Level. You can assign the same Category Value in all organizations where it is assigned.
Enter the Default Category. For example, enter Binder.Acrylic. The default is used when assigning an item to the Category Set.
Determine if you want to Enforce a List of Valid Categories:
Select this indicator if you want to assign items only to Categories defined as valid for the current Category Set. Enter each of the Valid Categories.
Clear this indicator if you want to assign an item to any Category that has the same flexfield structure as the current Category Set.
Click Assign. The Item Assignments (OPM) Technical Classification, Master Level window displays.
Query the Item to assign to the Category Set.
Select the Category and enter the Segments.
Repeat steps 9 and 10 for each additional Item to assign.
Click Accept.
See: Oracle Inventory User's Guide.
To assign category sets to a process manufacturing class
Navigate to the OPM Category Sets window.
Select the Category Set for the appropriate Process Manufacturing Class. Enter Technical Classification as Category Set.
See:Oracle Inventory User's Guide.
You can create and use version control attribute sets to set up version control at the following entity levels:
Formula - The following table lists and describes the version control attributes at the formula entity level:
| Formula Attribute | Description |
| Description | Brief description of the formula |
| Comments | Remarks or notes entered for the formula |
| Class | Classification assigned to the formula |
| Organization | Organization that owns the formula |
| Owner | Owner of the formula |
| Scaling Allowed | Whether the formula allows scaling or not |
| Packing | Whether the formula is a packaging type formula or not |
| Calculate product quantity | Automatically calculate the quantity for products with the scale type, proportional |
| Quantity | The quantity of ingredients, products and by-products |
| UOM | Unit of measure for ingredients, products and by-products |
| Scale Type | Type of scaling for ingredients, products, and by-products |
| Scale Multiple | Scaling increment for the ingredient |
| Scale Rounding Variance | Percent variance allowed for rounding when scale type is integer |
| Rounding Direction | Acceptable rounding direction when scale type is integer |
| Yield Type | Type of yield for products and by-products |
| Cost Allocation | Cost Allocation for financial rollup |
| By-Product Type | Type of by-product |
| Consumption Type | Type of ingredient consumption |
| Contribute to Yield | Whether the ingredient contributes to yield or not |
| Contribute to Step Qty | Whether the ingredient quantity contributes to step quantity or not |
| Phantom Type | Phantom type of ingredients |
| Buffer | Buffer indicator of ingredients |
| Scrap Factor | Scrap factor as a percentage for ingredients |
| Add or Delete Material | Addition or deletion of ingredients or products or by-products |
| Process Instructions | Process instructions for an ingredient or product or by-product of a formula |
Operation - The following table lists and describes the version control attributes at the operation entity level:
| Operation Attribute | Description |
| Description | Brief description of the operation |
| Class | Classification assigned to the operation |
| Valid From | Date from which operation is valid |
| To | Expiration date of the operation |
| Owner Organization | Owner organization for the operation |
| Minimum Transfer Quantity | Minimum quantity to be produced before the next operation begins |
| Process Qty UOM | Process quantity unit of measure of the operation |
| Yield% | Operation level planned yield percentage |
| Activity Factor | Number of times activity is performed |
| Sequence Dependency | Sequence dependency indicative of the activity |
| Offset Interval | Offset interval between activity start and resource start |
| Breakable | Whether the activity can be broken or not |
| Max Break | Maximum duration of the break |
| Material Scheduled | Whether material consumption is scheduled for the activity or not |
| Process Quantity | Process quantity for the resource |
| Usage | Usage of the resource |
| UOM | Resource usage unit of measure |
| Component Class | Component class for resource |
| Cost Analysis Code | Cost Analysis code for resource |
| Plan Type | Plan type of the resource |
| Count | Number or quantity of the resource used |
| Offset Interval for Resource | Offset interval before start of the resource |
| Scale Type | Scale type of the resource |
| Target | Target value for the process parameter |
| Minimum | Minimum value for the process parameter |
| Maximum | Maximum value for the process parameter |
| Add or Delete Activity | Addition or deletion of activity of an operation |
| Add or Delete Resource | Addition or deletion of a resource of an activity |
| Add or Delete Process | Parameter Addition or deletion of a process parameter of a resource |
| Process Instructions | Process instructions at an operation level |
Routing - The following table lists and describes the version control attributes at the routing entity level:
| Routing Attribute | Description |
| Routing Description | Brief description of the routing |
| Class | Classification assigned to the routing |
| Valid From | Date from which routing is valid |
| To | Expiration date of the routing |
| Owner Organization | Owner organization for the routing |
| Quantity | Process quantity for the routing |
| Quantity UOM | Process quantity unit of measure for the routing |
| Process Loss | Planned loss of material for the routing |
| Enforce Step Dependency | Whether routing enforces step dependency or not |
| Contiguous | Whether the routing is run in contiguous or not |
| Owner | Owner of the routing |
| Fixed Loss | Fixed process loss of the routing |
| Fixed Loss UOM | Fixed process loss unit of measure of the routing |
| Step Quantity | Quantity of material associated to the step |
| Yield% | Planned yield percentage of the step |
| Minimum Transfer Quantity | Minimum quantity to be produced before the next operation begins |
| Release Type | Release type of the step |
| Step dependencies | Dependencies between steps in the routing |
| Process Instructions | Process instructions at an operation level in the routing |
Recipe - The following table lists and describes the version control attributes at the recipe entity level:
| Recipe Attribute | Description |
| Description | Brief description of the recipe |
| Owner Organization | Owner organization for the recipe |
| Planned Loss | Planned loss of material defined as a percentage for the recipe |
| Calculate Step Quantity | Automatically calculate step quantity |
| Owner | Owner of the recipe |
| Contiguous | Whether routings in the recipe are run in contiguous or not |
| Recipe Type | Type of the recipe |
| Fixed Loss | Fixed process loss for the recipe |
| Fixed Loss UOM | Fixed process loss unit of measure for the recipe |
| Enhanced Process Instructions | Enhanced process instructions indicator |
| Plant/Laboratory | Organization specific details of the recipe |
| Customer | Customer details |
| Step Quantity | Quantity of material associated to the step |
| Yield% | Planned yield percentage of the step |
| Step/Material Association | Material association to the steps |
When you create and assign a attribute set for an entity, enable it for the organization, or set the Version Control parameter in the Product Development Parameters form to Yes for an entity, the application creates a new formula, operation, routing, and recipe.
For example, you can create a version control attribute set for Operation, enable it for the organization using the Assign Version Control Set page or use the Operation tab in the Product Development Parameters form to set the Version Control parameter to Yes, and assign the version control attribute set to the Operation entity. This ensures that when updating fields in the Process Operation Details Activities window that are included in the attribute set you created and assigned, you will be able to create a new version of the operation with the same entity names but with a different version number.
Note: Version controlling is not enabled for entities with the status New.
You can use the Version Control Attribute Set page to search for existing attribute sets, create a new attribute set, and assign an attribute set to one or more organizations. You can also use this page to delete existing version control attribute sets.
Note: If you have not created and associated any attribute sets with organization parameters, the basic functionality of version controlling continues. To use version control at the attribute level, create a version control attribute set for an attribute, and enable it for use in the organization.
To search for a version control attribute set
Navigate to the Version Control Attribute Set page.
(N) Product Development Security Manager > Version Control Attributes
Use one or both of the following fields in the Simple Search region to search for attribute sets:
Set Name: Enter the version control attribute set name.
Version Controlled Entity: Select from the following types of entities:
Formula
Operation
Routing
Recipe
Click Go.
The Attribute table displays the attribute sets applicable to your search criteria.
To create a version control attribute set
Navigate to the Version Control Attribute Set page.
Click Create.
Use the Create Version Control Attribute Set page, to provide information for the following fields:
Set Name: Enter a name for the attribute set. It is recommended that you enter a name of up to 32 characters.
Set Description: Enter a description for the attribute set.
Version controlling Entity: Select from the following list of values to indicate the entity that you are creating this version control attribute set for:
Formula
Operation
Routing
Recipe
Click Go.
Based on the version controlling entity that you select in this field, the corresponding list of attributes appear in the Attribute Table.
To enable version control for your selected attributes, select the corresponding Enabled check box.
If you do not want to save and create the version control attribute set, click Cancel.
If you want to save and create the version control attribute set, but also create another new attribute set, click Apply and Create Another. A confirmation message displays and you can continue to create a new version control attribute set on the Create Version Control Attribute Set page.
If you want to save and create this version control attribute set, click Apply. A confirmation message displays and you can see the new version control attribute set in the Version Control Attribute Set page.
To update a version control attribute set
Navigate to the Version Control Attribute Set page.
Use the fields in the Simple Search region to search for the attribute set you would like to update.
Click Go.
The Attribute table displays the attribute sets applicable to your search criteria.
Click the Update icon for the version control attribute set you want to update.
Use the Update Version Control Attribute Set page to select or clear the corresponding Enabled check boxes for the attributes that display for the version control attribute set.
If you do not want to save your updates, click Cancel and return to the Version Control Attribute Set page.
To save your updates, click Apply. A confirmation message displays.
To return to the Version Control Attribute Set page, click the Return to Version Control Attribute Set link.
To delete a version control attribute set
Navigate to the Version Control Attribute Set page.
Use the fields in the Simple Search region to search for the version control attribute set you would like to delete.
Click Go.
The Attribute table displays the attribute sets applicable to your search criteria.
Click the Delete icon for the version control attribute set you want to remove.
A message displays to ask if you want to delete the selected attribute set. Click Yes to delete the set. Click No to retain the set.
To assign a version controlling attribute set
You will need to assign the version control attribute set you created for the entity, be it formula, operation, routing, or recipe, to one or more organizations.
To assign a specific version control attribute set to the version controlling entity, you can use the Assign Version Control Set page to assign an attribute set to multiple organizations at one time, or the Product Development Parameters windows to assign an attribute set to a single organization.
Assigning Version Control Attribute Sets Using Assign Version Control Set page
Navigate to the Assign Version Control Set page.
(N) Product Development Security Manager > Version Control Attribute Set page.
Use the fields in the Simple Search region to search for the version control attribute set you would like to assign to organizations
Click Go.
The Attribute table displays the attribute sets applicable to your search criteria.
Click the Assign icon for the attribute set you would like to assign to one or more organizations.
In the Assign Version Control Set page, select the Enabled check box for the organizations you would like to assign to the version control attribute set.
Note: The organizations that display are organizations with no version control attribute set assigned or which have been assigned the same set you have queried. Organizations assigned to a different version control attribute set do not display.
You can also use this page to remove organization assignments. Clear the Enabled check box for the organization you do not want to assign to the version control set.
Click Cancel, to return to the Version Control Attribute Set page without saving your changes.
Click Apply to save your changes.
To return to the Version Control Attribute Set page, click the Return to Version Control Attribute Set link.
Assigning Version Control Attribute Sets the Using Product Development Parameters window
Navigate to the Product Development Parameters window.
(N) Product Development Security Manager > Organization Parameters.
Use the Product Development Parameters window to enter the context inventory organization in the Organization field.
Select from the following tabs for the version controlled entity to which you want to assign a attribute set:
Formula
Operation
Routing
Recipe
For the Version Control parameter, select from the following list of values in the Parameter Value:
Yes: Select Yes to use version control at the attribute level.
No: Select No if you do not want to use version control at the attribute level. If the value for Version control is set to No, you cannot use version controlling attribute sets, even if you select an attribute set.
Optional: Select Optional to be prompted by the application with the option to select Yes to create a new version, or select No to save changes in the current version. You will also be able to select Cancel to discard the changes.
In the Version Control Attribute Set, use the Parameter Value list of values to select an attribute set you have created. Note that the list of values will display only the corresponding list of attribute sets you created for the version controlling entity.
Click Save.
For more information on the Product Development Parameters window, see Setting Up Parameters.