Skip Headers

Oracle Process Manufacturing System Administration User's Guide
Release 12.1
Part Number E13654-04
Go to Table of Contents
Contents
Go to previous page
Previous
Go to next page
Next

OPM System Setup

This topic explains how to set up and manage the OPM System Administration functions. This includes Document Types, Users, and Organizations, as well as several others.

This chapter covers the following topics:

Querying Document Types

Documents are used to categorize transaction activity that is generated from many OPM functions including inventory, sales, purchasing, and production. OPM documents are categorized by type, each recording different kinds of information related to different transactions. Document types and organizations are defined before document ordering.

Note: Do not modify the document types supplied with OPM.

Use the Document Types window to query the following document types.

To find a document type:

  1. Navigate to the Find Document Types window.

  2. Enter any of the following criteria to narrow the search:

  3. Select Marked for Deletion as Yes to search for document types marked for deletion.

  4. Click Find.

To view a document type:

  1. Navigate to the Document Types window.

  2. The following information displays:

Querying a Document Order

Use the Document Ordering window to view the document number assignment for each type of document. A document is an online window that creates a financial, inventory, or resource transaction. Different document numbers are assigned for each document type and organization. All document numbers are prefaced with an organization code; therefore, multiple organizations can use the same number ranges and still uniquely identify their documents.

Numbers can be assigned to documents manually or automatically.

To find a document order:

  1. Navigate to the Find Document Orderings window.

  2. Enter any of the following criteria to narrow the search:

  3. Select the Assignment Type as:

  4. Select Marked for Deletion as Yes to search for document orders marked for deletion.

  5. Click Find. The Document Ordering window displays the information.

To view a document order:

  1. Navigate to the Document Ordering window.

  2. The following information displays:

Querying Geography Codes

Use the Geography Codes window to view geography codes. Geography codes are used to reference geographical areas on purchase orders, customer receipts, and other documents that contain addresses.

To find a geography code:

  1. Navigate to the Find Geography Codes window.

  2. Enter the Type which defines the type of geography code. Valid values are:

  3. Enter the Code identifying the geographical area; for example, NY for New York.

  4. Enter the Description describing the geography code.

  5. Click Find.

To view geography codes:

  1. Navigate to the Geography Codes window.

  2. The following information displays:

Querying Organizations

Organizations are entities for assigning resources, warehouses, general ledger accounts, and other cross-application items. An organization, can be a company, a plant, or both. A company is a legal entity that must maintain a balanced set of books. A plant is an organization that manufactures goods.

Both companies and plants are classified as organizations in OPM.

Parent organizations can have multiple child organizations. Child organizations can have independent resources and warehouses that are accounted for on the parent general ledger. You can also have independent organizations. Organizational setup accommodates multi-company accounting.

Organizational Hierarchies

In setting up an organization, you must specify the organization's parent organization. In this way, organizational hierarchies can be constructed. For example, a company can have several subsidiary companies, and each company can have several plants.

To find organizations:

  1. Navigate to the Find Organizations window.

  2. Enter any of the following criteria to narrow your search:

  3. Select Marked for Deletion as Yes to search for organizations that are marked for deletion.

  4. Click Find.

To view organizations:

  1. Navigate to the Organizations window.

  2. The following fields are display only:

Editing Paragraphs

Paragraphs in Oracle Process Manufacturing (OPM) are structures that are used to store and categorize text. OPM is installed with one default paragraph per database table, the General Text paragraph. When you select Edit Text and access the Text Editor window, by default, the edited text is put into this General Text paragraph.

The Paragraph window lets you specify different paragraphs that can be associated with tables. After selecting Edit Text, a list of valid paragraphs displays in the Text Paragraph Selection window, even if the only available paragraph code is General Text. Choose one to proceed.

Paragraph codes control whether text prints on hardcopy documents such as orders or shipping forms or what language your text is stored in. The default General Text paragraph is set up as display only, but it can be changed to enable printing.

Most OPM windows enable you to associate text with the document or record you are working with. To add or update text, select Edit Text from the Actions menu, choose the Paragraph you want to associate the text with, and access the Text Editor window. You can display the entered text online and can be print on hard copies of documents.

If you are creating or editing a purchase order header on the Purchase Orders window, then you can select Edit Text from the Actions menu and add the text associated with the document. If you are creating or editing purchase order lines on the Purchase Order Lines window, then you can add text to each line, associated with each line of the document. The text you add is associated only with the purchase order line that was highlighted when you selected Edit Text.

When you display the Text Editor, the entered text is associated only with the paragraph code and record you are working with. For example, if you enter text for a line in an order using the General Text paragraph, then that text is associated only with that line on that order.

Note: Paragraph codes are linked to specific database tables when they are set up; therefore, you cannot see the same list of paragraphs from every OPM window.

For example, you can create a paragraph on the Batch Header table (pm_btch_hdr). When you select Edit Text from the Actions menu, this paragraph displays as an option on the Text Paragraph Selection window. If you have defined a paragraph for Routing Instructions, then select the Routing Instructions paragraph. The entered text is stored in this paragraph.

To create paragraphs:

  1. Navigate to the Paragraphs window.

  2. Enter the database Table Name linking this paragraph.

  3. Enter the Code that identifies this paragraph. If you are creating subparagraphs, then each subparagraph has the same paragraph code as the main paragraph.

  4. Enter a Sub Paracode when you have one paragraph related to another paragraph. Subparagraphs are printed beneath the main paragraph in numerical order. Subparagraph codes must be integers, determining the order the subparagraphs are printed. The subparagraph code for the main paragraph is the default value 0.

  5. Determine whether the paragraph text is to be included when documents are printed. Select the Nonprintable value as Yes if the text does not print, and the value No if the text does print.

  6. Enter a maximum 40-character Description. This description displays when you select paragraphs when entering text.

  7. Save the changes.

Querying Reason Codes

Reason codes provide information on increases or decreases in inventory. They are used to flag transactions and attach reasons to them.

For example, you have a batch of product that cannot be shipped because the color is wrong. If this is a common occurrence, then you can set up a reason code that identifies these situations.

To find a reason code:

  1. Navigate to the Find Reason Codes window.

  2. Enter any of the following criteria to narrow your search:

  3. Click Find.

To view a reason code:

  1. Navigate to the Reason Codes window.

  2. The following fields are display only:

Viewing Reason Code Security

To prevent or reduce the risk of using an incorrect reason code, reason codes are secured by:

Any document type that has reason code functionality is required to let you assign which reason codes are valid for the specific document type. A reason code must be associated with both a Document Type and a Responsibility in order for the Reason Code to be used on a given window.

At least one of the Document Type fields and one of the Responsibility fields must have a value.

The Reason Code being secured always appears in the header block of the window. The fields in the detail block can be used as follows:

To view a reason code:

  1. Navigate to the Reason Code Security window.

  2. Reason code is the code that identifies the reason and displays with a brief description.

  3. The following fields display in the Security Definitions section of the window:

Editing Session Parameters

In addition to providing current system session information, the Session Parameters window enables you to change your default organization and default schedule by selecting the new entry using the List of Values and clicking OK. You can specify whether you want the change to affect only the current session or all sessions until the default organization value is changed.

Note: OPM lets you choose only an organization that you are authorized to specify as defined through the User Organizations window.

To edit session parameters:

  1. Navigate to the Sessions Parameter window.

  2. Verify that the following fields are correct:

  3. Enter the Organization code for the default organization. You must be authorized to select this code as specified through the User Organizations window.

  4. Enter the default Schedule for this session.

  5. Save the changes.

Editing Text Tokens

Text tokens are codes or short descriptions that represent longer descriptions or messages. These tokens are set up on the Text Token window.

After selecting Edit Text from the Actions menu and invoking the Text Editor, specify a token instead of typing the full description of the text by entering a token preceded by a period. Press Tab, and the token is converted to the text it represents.

For example, you might set up a text token called Fragile that represents the text: Fragile, Handle with Care. Whenever you want to include these instructions on a document, you can type Fragile on the Text Editor window rather than typing the message text. You can also use the LOV function to select a text token. After selecting from the list of values, press Tab.

To record the text that is printed when you enter the token, select Edit from the Actions menu and enter the text on the Text Editor window.

To find text tokens:

  1. Navigate to the Find Text Tokens window.

  2. Enter the following criteria to narrow your search:

  3. Click Find.

To view text tokens:

  1. Navigate to the Text Tokens window.

  2. The following fields display:

Units of Measure

The Unit of Measure window is used to add and maintain Units of Measure (UOM) definitions. A UOM definition consists of a UOM code, a description, a type, and the conversions between the reference UOM and all other UOMs of the same type.

Before you can maintain, purchase, or sell inventory, you must define the UOMs against the item quantities that are measured.

Note: The order you set up UOMs is of utmost importance. The first UOM value that you define for a given UOM type becomes the reference against all other UOMs of the same UOM type. All subsequent UOMs defined for the specified UOM type require conversion against this reference UOM.

All conversions specified on the Units of Measure window are conversions between the same UOM types. Conversions across UOM types must be defined individually for each item.

Refer to the Oracle Inventory User's Guide for more information.

After setting up UOM types, set up the actual UOM values on the Unit of Measure window. The first UOM that you set up for each UOM type becomes the reference UOM, also called base or standard UOM, for that type. All other UOMs of this type are defined in relation to the reference UOM.

For example, if you set up L (liters) as the first UOM for the UOM type VOL (volume), then you have to define each new volume UOM in terms of liters; therefore, if the new volume is GAL (gallons), then it must be defined in relation to liters. As such, you specify a two-way conversion between GAL (gallons) and L (liters) and L (liters) and GAL (gallons) in the Conversion column.

The two-way conversion equation is as follows:

The factor between the newly entered UOM, in this example GAL (gallons), and the reference UOM, L (liters), and vice versa, is entered in the Conversion Factor column. You only need to enter the conversion factor going “one way”; the other conversion factor is automatically calculated.

Note: Altering the UOM conversion once inventory has been created can corrupt inventory balances.

The new UOM is available to the session where you entered the UOM and to all users beginning OPM sessions after you enter it. If you change a conversion, then the change does not take effect in the current session. You must log out of OPM and then log in again. Note that this is not recommended.

New Unit of Measure Functionality

Oracle Process Manufacturing (OPM) is now using the Oracle Inventory Unit of Measure windows for the creation of UOMs, as well as viewing existing UOMs. You can access these windows from either the Oracle Inventory menu or from the Oracle Process Manufacturing System Administration menu.

These windows let you use mixed case when creating your UOMs and their descriptions. All UOMs are three characters, the Oracle Financials standard. You can also create a 25 character name for each UOM in addition to the description.

The Unit of Measure Classes window in Oracle Inventory lets you set up new Base Units of Measure. This is the same as the OPM Unit of Measure Type window, with more information. The Oracle Inventory window lets you set both a name and a description for each UOM.

The Unit of Measure window is the same as the OPM Unit of Measure window, with additional information similar to the Unit of Measure Classes window, where you are able to have both a description and a name for each UOM.

The Unit of Measure Conversions window, also displayed by the Conversions button on the Unit of Measure Classes window, is used for setting the conversion factors. This window replaces the conversion section of the OPM Unit of Measure window.

The Unit of Measure LOVs have also changed. The LOV now features three columns to accommodate both new and existing UOMs. An LOV looks as follows:

UOM UOM Name Description
CNT CNT Count Base
EACH EACH Each
Lbs Pounds Pounds (1kg = 2.2 pounds)

In this example, the CNT and EACH are carried over from OPM, where there was no UOM Name. Therefore, the UOM duplicates into the name field. The Lbs UOM is from the Oracle Inventory application, and shows a different UOM Name. This carries forward with all new UOMs.

Refer to the Oracle Inventory User's Guide for details on the Oracle Inventory Unit of Measure windows.

Viewing User Organization

Use the User Organizations window to view the number of organizations assigned to a user. Once assigned, a user can work only with an organization from among these authorized organizations.

To view user organizations:

  1. Navigate to the User Organizations window.

  2. User Name displays the name of the user for whom the organizations are assigned.

  3. The following fields display in the Organizations section of the window:

Viewing User Planning Classes

TheUser Planning Classes window lets you view the planning classes associated to users.

Note: Refer to the Oracle Process Manufacturing Process Planning User's Guide for additional information on how User Planning Classes are defined and used.

To view user planning classes:

  1. Navigate to the User Planning Classes window.

  2. User displays the user name with a brief description.

  3. The following fields display in the Planning Classes section of the window:

Lookups

The Process Manufacturing Systems Lookups window lets you maintain lookups. Each Lookup has a code and a meaning. For example, Lookup type YES_NO has a code Y with meaning Yes, and a code N with a meaning No.

To view the Lookups window:

  1. Navigate to the Process Manufacturing Systems Lookups window.

  2. The following fields are display only:

Actions Menu

From the Actions menu, the Edit Text option lets you edit information. You can edit text in the Edit Text window only if you navigate from the Paragraphs or the Text Tokens window.

Edit Text

If there is only one paragraph code associated with the table, then the Text Editor window appears. If there is more than one paragraph associated with the table, then the Select Text Paragraph window appears first.

Note: If you navigate to the Edit Text window from the Paragraphs or the Text Tokens window, then you can edit text.

To edit text:

  1. Navigate to the Edit Text option from the Actions menu. If the Select Text Paragraph window displays, then select a line, and click Edit Text. If not, then the Text Editor window displays.

  2. View the following fields for accuracy:

  3. Enter the appropriate Text.

  4. Click Paragraph to return to the previous window to select another paragraph to edit.

  5. From the Select Text Paragraph window, view the following fields for accuracy:

Setting Up Profile Options

During your implementation, you set a value for selected profile options to specify how your System Administration application is configured. System Administration uses the GMA: Workflow Delimiter profile option.

Your System Administrator sets user profile options at one or more of the following levels: Site, Application, Responsibility, and User. Use the Personal Profile Options window to view or set your profile options at the user level. Consult your Oracle E-Business Suite System Administrator's Guide for a list of profile options common to all Oracle Applications.