manufacturing apps technical

11i Manufacturing FunctionalFoundationInstructor Guide

D12333GC10

Edition 1.0

May 2001

D32897

Copyright © Oracle Corporation, 2001. All rights reserved.

This documentation contains proprietary information of Oracle Corporation. It is provided under a licenseagreement containing restrictions on use and disclosure and is also protected by copyright law. Reverseengineering of the software is prohibited. If this documentation is delivered to a U.S. Government Agency of theDepartment of Defense, then it is delivered with Restricted Rights and the following legend is applicable:

Restricted Rights Legend

Use, duplication or disclosure by the Government is subject to restrictions for commercial computer softwareand shall be deemed to be Restricted Rights software under Federal law, as set forth in subparagraph (c)(1)(ii)of DFARS 252.227-7013, Rights in Technical Data and Computer Software (October 1988).

This material or any portion of it may not be copied in any form or by any means without the express priorwritten permission of the Education Products group of Oracle Corporation. Any other copying is a violation ofcopyright law and may result in civil and/or criminal penalties.

If this documentation is delivered to a U.S. Government Agency not within the Department of Defense, then it isdelivered with “Restricted Rights,” as defined in FAR 52.227-14, Rights in Data-General, including Alternate III(June 1987).

The information in this document is subject to change without notice. If you find any problems in thedocumentation, please report them in writing to Worldwide Education Services, Oracle Corporation, 500 OracleParkway, Box SB-6, Redwood Shores, CA 94065. Oracle Corporation does not warrant that this document iserror-free.

Oracle and all references to Oracle Products are trademarks or registered trademarks of Oracle Corporation.

All other products or company names are used for identification purposes only, and may be trademarks of theirrespective owners.

Author

Amy Sonczalla, Bill Figini, Bill Sawyer, Leanne Vakoc

Technical Contributors and Reviewers

Charles Pirnat, Tom Marik, Mani Rana, Prasanth Pala, Sachin Patel, ArvydasNakas

This book was published using:

Oracle Tutor


11i Manufacturing Functional Foundation Table of Contentsi

Table of Contents

Applications Architecture .....................................................................................................1-1Applications Architecture ....................................................................................................1-2Objectives ............................................................................................................................1-3Applications Network Architecture .....................................................................................1-4Desktop Tier ........................................................................................................................1-5Forms Client Applet ............................................................................................................1-6JInitiator...............................................................................................................................1-7Application Tier...................................................................................................................1-8Web Server ..........................................................................................................................1-9Forms Server........................................................................................................................1-10Concurrent Processing Server..............................................................................................1-11Accessing Concurrent Processing Output............................................................................1-12Reports Server .....................................................................................................................1-13Administration Server..........................................................................................................1-14Database Tier.......................................................................................................................1-15Database Architecture..........................................................................................................1-16Oracle Applications Database Objects.................................................................................1-17APPS Schema ......................................................................................................................1-18Additional Schemas .............................................................................................................1-19Multiple Organizations Views .............................................................................................1-20Multiple Reporting Currencies ............................................................................................1-21File System Architecture .....................................................................................................1-22APPL_TOP..........................................................................................................................1-23Product Directories ..............................................................................................................1-25Admin Directory..................................................................................................................1-26Bin Directory .......................................................................................................................1-27Forms Directory...................................................................................................................1-28Help Directory .....................................................................................................................1-29HTML Directory..................................................................................................................1-30Include Directory.................................................................................................................1-31Java Directory......................................................................................................................1-32Lib Directory .......................................................................................................................1-33Log and Out Directories ......................................................................................................1-34Media Directory...................................................................................................................1-35Mesg Directory ....................................................................................................................1-36Patch Directory ....................................................................................................................1-37PLSQL and Resource Directories........................................................................................1-38Reports Directory.................................................................................................................1-39SQL Directory .....................................................................................................................1-40AD Directory .......................................................................................................................1-41AU Directory .......................................................................................................................1-42Admin Directory..................................................................................................................1-43Admin Directory Text Files.................................................................................................1-44Common Components Directory .........................................................................................1-45Copying Java Files: apps.zip ...............................................................................................1-46Technology Stack Directories..............................................................................................1-47Database Data Files .............................................................................................................1-48File Types ............................................................................................................................1-49Naming Standards................................................................................................................1-51Database Objects .................................................................................................................1-52Forms File Standards ...........................................................................................................1-55PL/SQL Packages, Procedures and Source Files .................................................................1-56


11i Manufacturing Functional Foundation Table of Contentsii

Reserved Words...................................................................................................................1-57Summary..............................................................................................................................1-58

Applications Basics ................................................................................................................2-1Applications Basics .............................................................................................................2-2Objectives ............................................................................................................................2-3Basic Applications Tools.....................................................................................................2-4Overview of Concurrent Processing ....................................................................................2-6Overview of Flexfields ........................................................................................................2-7Overview of Alerts ..............................................................................................................2-8Overview of Workflow........................................................................................................2-9Summary..............................................................................................................................2-10

ERDs and Applications Technology.....................................................................................3-1ERDs and Applications Technology....................................................................................3-2Objectives ............................................................................................................................3-3Entity Relationship Diagrams (ERDs).................................................................................3-4What is an Entity?................................................................................................................3-5Entities and Instances ..........................................................................................................3-6Attributes .............................................................................................................................3-7Relationships .......................................................................................................................3-8Drawing Entities in ERDs....................................................................................................3-10Drawing Attributes in ERDs................................................................................................3-11Drawing Relationships in ERDs ..........................................................................................3-12Perspectives of Relationships in ERDs................................................................................3-13Reading Relationships in ERDs...........................................................................................3-14Oracle Applications ERD Standards....................................................................................3-15Key Flexfields......................................................................................................................3-18Descriptive Flexfields ..........................................................................................................3-22Flexfield Values...................................................................................................................3-24Concurrent Managers...........................................................................................................3-27Concurrent Processing .........................................................................................................3-30Concurrent Manager Advanced Schedules ..........................................................................3-33Standard Request Submission..............................................................................................3-35Workflow.............................................................................................................................3-38Function Security.................................................................................................................3-41Login Security .....................................................................................................................3-43AuditTrail ............................................................................................................................3-45User Profiles ........................................................................................................................3-47Document Sequences, Folders, Documents on the Navigator .............................................3-49Attachments .........................................................................................................................3-51Document Management and Help .......................................................................................3-53AOL Data Dictionary Information.......................................................................................3-55Currency and Language .......................................................................................................3-58Summary..............................................................................................................................3-60

Development Topics...............................................................................................................4-1Development Topics............................................................................................................4-2Objectives ............................................................................................................................4-3Interface Options .................................................................................................................4-4Interface Table Diagram ......................................................................................................4-6API Diagram........................................................................................................................4-8Development Standards .......................................................................................................4-10Summary..............................................................................................................................4-12

Exploring Applications Database .........................................................................................5-1Exploring Applications Database ........................................................................................5-2Objectives ............................................................................................................................5-3Exploration Basics ...............................................................................................................5-4


11i Manufacturing Functional Foundation Table of Contentsiii

Listing Scripts......................................................................................................................5-6Description Scripts...............................................................................................................5-27Configuration Scripts...........................................................................................................5-32Summary..............................................................................................................................5-43

11i Manufacturing Functional Foundation: Overview.......................................................6-111i Manufacturing Functional Foundation: Overview.........................................................6-2Objectives ............................................................................................................................6-3Agenda.................................................................................................................................6-4Application Development Standards ...................................................................................6-6The Applications Server Directory Structure.......................................................................6-7Database Naming Conventions............................................................................................6-8Development Standards .......................................................................................................6-10Summary..............................................................................................................................6-12Agenda.................................................................................................................................6-13Entity Relationship Diagram Definitions.............................................................................6-14Primary Key.........................................................................................................................6-15Foreign Key .........................................................................................................................6-16Primary Key Relationships ..................................................................................................6-18Foreign Key Example ..........................................................................................................6-19Database Diagramming Conventions ..................................................................................6-20Practice Setup ......................................................................................................................6-21Practice Overview................................................................................................................6-23Practice 1 .............................................................................................................................6-24Practice 1 Solution...............................................................................................................6-25Practice 2 .............................................................................................................................6-26Practice 2 Solution...............................................................................................................6-27Practice 3 .............................................................................................................................6-28Practice 3 Solution...............................................................................................................6-29Practice 4 .............................................................................................................................6-30Practice 4 Solution...............................................................................................................6-31Agenda.................................................................................................................................6-32Oracle Manufacturing Applications.....................................................................................6-33Oracle Inventory ..................................................................................................................6-34Oracle Bills of Material .......................................................................................................6-36Oracle Engineering ..............................................................................................................6-38Oracle Cost Management.....................................................................................................6-40Oracle Work in Process .......................................................................................................6-42Oracle Work in Process Transactions ..................................................................................6-43Oracle Purchasing................................................................................................................6-44Purchasing Transactions ......................................................................................................6-46Agenda.................................................................................................................................6-47Importing Information .........................................................................................................6-48Open Interface Model ..........................................................................................................6-50Managing Open Interface Processing ..................................................................................6-52Data Conversion ..................................................................................................................6-53Detailed Conversion Plan ....................................................................................................6-54Designing the Conversion Process.......................................................................................6-56Developing Conversion Programs .......................................................................................6-58Performing the Conversion..................................................................................................6-59Summary..............................................................................................................................6-60

11i Manufacturing Functional Foundation: Inventory ......................................................7-111i Manufacturing Functional Foundation: Inventory.........................................................7-2Objectives ............................................................................................................................7-3Agenda.................................................................................................................................7-4Oracle Inventory ..................................................................................................................7-6Oracle Inventory Database Summary Diagram ...................................................................7-8


11i Manufacturing Functional Foundation Table of Contentsiv

Inventory Organizations ......................................................................................................7-9Oracle Inventory: Organizations..........................................................................................7-10Defining Organizations........................................................................................................7-12Defining Organization Parameters for Additional Information ...........................................7-13Locators and Subinventories................................................................................................7-14Oracle Inventory: Subinventories and Locators...................................................................7-15Defining Subinventories ......................................................................................................7-17Defining Locators ................................................................................................................7-18Oracle Inventory: Item Master.............................................................................................7-19Defining Items .....................................................................................................................7-21Degree of Item Control ........................................................................................................7-22Oracle Inventory Item Controls ...........................................................................................7-23Defining Item Controls ........................................................................................................7-25Oracle Inventory Item Status ...............................................................................................7-26Life Cycle of a Part: Using Item Status and Attributes........................................................7-28Defining Item Status Codes .................................................................................................7-29Item Categories Example.....................................................................................................7-30Oracle Inventory: Item Categories.......................................................................................7-31Defining Item Categories.....................................................................................................7-33Oracle Inventory: Item Catalogs..........................................................................................7-34Defining Item Catalogs........................................................................................................7-36Practice 1 Setup ...................................................................................................................7-37Practice 1 .............................................................................................................................7-39Practice 1 Solution...............................................................................................................7-40Agenda.................................................................................................................................7-41Oracle Inventory Transaction Flow .....................................................................................7-42Oracle Inventory: Inventory Transactions and Item Controls.............................................7-44Physical Inventory Process ..................................................................................................7-46Oracle Inventory: Physical Inventory ..................................................................................7-47Defining Physical Inventory ................................................................................................7-49ABC Analysis Overview .....................................................................................................7-50Oracle Inventory: ABC Analysis .........................................................................................7-51Defining an ABC Compile ..................................................................................................7-53Cycle Count Overview.........................................................................................................7-54Oracle Inventory: Cycle Count ............................................................................................7-55Oracle Inventory: Demand and Reservation Information....................................................7-57Practice 2 Setup ...................................................................................................................7-59Practice 2 .............................................................................................................................7-60Practice 2 Solution...............................................................................................................7-61Agenda.................................................................................................................................7-62Oracle Applications Open Interfaces for Inventory.............................................................7-63Major Tables: Open Interfaces.............................................................................................7-64Inventory Transactions Open Interface Tables ....................................................................7-65Open Interfaces: Inventory Setups.......................................................................................7-66Inventory Setups Open Interface Tables..............................................................................7-67Summary..............................................................................................................................7-68

11i Manufacturing Functional Foundation: Purchasing....................................................8-111i Manufacturing Functional Foundation: Purchasing.......................................................8-2Objectives ............................................................................................................................8-3Agenda.................................................................................................................................8-4Oracle Purchasing Overview ...............................................................................................8-6Purchasing Process Flow .....................................................................................................8-8Agenda.................................................................................................................................8-9Oracle Purchasing: Entity Relationships .............................................................................8-10Suppliers ..............................................................................................................................8-12Suppliers Window ...............................................................................................................8-13


11i Manufacturing Functional Foundation Table of Contentsv

Oracle Purchasing: Requisitions ..........................................................................................8-14Requisitions Window...........................................................................................................8-16Purchasing Documents ........................................................................................................8-17Oracle Purchasing: Purchasing Documents .........................................................................8-19Purchase Orders Window ....................................................................................................8-21Receiving .............................................................................................................................8-22Receiving Transactions........................................................................................................8-24Practice 1 Setup ...................................................................................................................8-25Practice 1 .............................................................................................................................8-27Practice 1 Solution...............................................................................................................8-28Agenda.................................................................................................................................8-29Purchasing Open Interfaces .................................................................................................8-30Purchasing Open Interface Tables .......................................................................................8-32Summary..............................................................................................................................8-33

11i Manufacturing Functional Foundation: BOM and Engineering ...............................9-111i Manufacturing Functional Foundation: BOM and Engineering ....................................9-2Objectives ............................................................................................................................9-3Agenda.................................................................................................................................9-4Oracle Bills of Material .......................................................................................................9-6Oracle Bills of Material/Engineering Bills of Material Structures ......................................9-8Defining a Bill of Material...................................................................................................9-10Item Revision Control..........................................................................................................9-11Oracle Bills of Material/Engineering Resources and Departments......................................9-12Outside Processing Example ...............................................................................................9-13Defining a Routing ..............................................................................................................9-14Oracle Bills of Material/Engineering Routings ...................................................................9-15Practice 1 Setup ...................................................................................................................9-17Practice 1 .............................................................................................................................9-19Practice 1 Solution...............................................................................................................9-20Practice 2 .............................................................................................................................9-21Agenda.................................................................................................................................9-23Oracle Engineering ..............................................................................................................9-24Oracle BOM/Engineering Change Control..........................................................................9-26Practice 3 Setup ...................................................................................................................9-28Practice 3 .............................................................................................................................9-30Practice 3 Solution...............................................................................................................9-31Agenda.................................................................................................................................9-32Oracle Bills of Material/Engineering Open Interfaces.........................................................9-33Oracle BOM/Engineering Interface Tables .........................................................................9-34Summary..............................................................................................................................9-35

11i Manufacturing Functional Foundation: Work in Process ...........................................10-111i Manufacturing Functional Foundation: Work in Process ..............................................10-2Objectives ............................................................................................................................10-3Agenda.................................................................................................................................10-4Discrete Versus Repetitive Manufacturing Process............................................................10-6Oracle Work in Process Overview.......................................................................................10-7Oracle Work in Process Operations.....................................................................................10-9Oracle Work in Process: Discrete Jobs................................................................................10-11Oracle Work in Process: Repetitive Schedules....................................................................10-13Repetitive Schedules Summary Report ...............................................................................10-15Agenda.................................................................................................................................10-16Oracle WIP Transactions .....................................................................................................10-17Oracle WIP Material Transactions.......................................................................................10-19Material Transactions Window............................................................................................10-21Oracle WIP: Move Transactions..........................................................................................10-22Move Transactions Window................................................................................................10-24


11i Manufacturing Functional Foundation Table of Contentsvi

Oracle WIP: Resource Transactions ....................................................................................10-25Resource Transaction Window............................................................................................10-27Oracle WIP: Completion Transactions ................................................................................10-28Completion Transactions window .......................................................................................10-30Oracle WIP: Work Order-less Completions ........................................................................10-31Work Order-less Completions Window...............................................................................10-33Practice 1 Setup ...................................................................................................................10-34Practice 1 .............................................................................................................................10-36Practice 1 Solution...............................................................................................................10-37Agenda.................................................................................................................................10-39Oracle WIP: Open Interfaces ...............................................................................................10-40Oracle WIP Transactions Open Interface Tables.................................................................10-41Summary..............................................................................................................................10-42

11i Manufacturing Functional Foundation: Cost Management ........................................11-111i Manufacturing Functional Foundation: Cost Management ...........................................11-2Objectives ............................................................................................................................11-3Agenda.................................................................................................................................11-4Oracle Cost Management.....................................................................................................11-6Cost Information..................................................................................................................11-8Agenda.................................................................................................................................11-9Cost Type: Standard ............................................................................................................11-10Cost Types: Average, FIFO, LIFO ......................................................................................11-12Oracle Cost Management Resource and Overhead Costs....................................................11-14Item Cost Summary and Details ..........................................................................................11-16Practice 1 Setup ...................................................................................................................11-17Practice 1 .............................................................................................................................11-19Practice 1 Solution...............................................................................................................11-20Agenda.................................................................................................................................11-21Oracle Cost Management Open Interfaces ..........................................................................11-22Oracle Cost Management Interface Tables..........................................................................11-23Summary..............................................................................................................................11-24


11i Manufacturing Functional Foundation Table of Contentsvii

Preface

Profile

Before You Begin This Course

Before you begin this course, you should have the following qualifications:

• Ability to perform queries and display data using SQL*Plus

• Thorough knowledge and proficiency in navigating Oracle applications

• Working experience with at least one of the Oracle Manufacturingapplication modules

• Working experience with Oracle Applications System Administration,Flexfields, Alerts, and Workflow

Prerequisites

1) At least one of the following Oracle application courses:

• Inventory

• Bills of Material

• Engineering

• Work in Process

• Purchasing

• Cost Management

2) Ability to perform queries and display data with SQL and SQL*Plus

How This Course Is Organized

This is an instructor-led course featuring lecture and hands-on exercises. Onlinedemonstrations and written practice sessions reinforce the concepts and skillsintroduced.


11i Manufacturing Functional Foundation Table of Contentsviii

Related Publications

Oracle Publications

Title Part Number

Installation manuals by platform

Oracle Application Object Library/Workflow Manual A80844-01

Oracle Inventory Technical Reference Manual A90206-01

Oracle Bills of Material Technical Reference Manual A90198-01

Oracle Engineering Technical Reference Manual A90177-01

Oracle Work in Process Technical Reference Manual A81185-01

Additional Publications

• System release bulletins

• Installation and user’s guides

• readme files

• Oracle Magazine


11i Manufacturing Functional Foundation Table of Contentsix

Typographic Conventions

Typographic Conventions in Text

Convention Element ExampleBold italic Glossary term (if

there is a glossary)The algorithm inserts the new key.

Caps andlowercase

Buttons,check boxes,triggers,windows

Click the Executable button.Select the Can’t Delete Card check box.Assign a When-Validate-Item trigger to theORD block.Open the Master Schedule window.

Courier new,case sensitive(default islowercase)

Code output,directory names,filenames,passwords,pathnames,URLs,user input,usernames

Code output: debug.set (‘I”, 300);Directory: bin (DOS), $FMHOME (UNIX)Filename: Locate the init.ora file.Password: User tiger as your password.Pathname: Open c:\my_docs\projectsURL: Go to http://www.oracle.comUser input: Enter 300Username: Log on as scott

Initial cap Graphics labels(unless the term is aproper noun)

Customer address (but Oracle Payables)

Italic Emphasized wordsand phrases,titles of books andcourses,variables

Do not save changes to the database.For further information, see Oracle7 ServerSQL Language Reference Manual.Enter [email protected],where user_id is the name of the user.

Quotationmarks

Interface elementswith long namesthat have onlyinitial caps;lesson and chaptertitles in cross-references

Select “Include a reusable module component”and click Finish.

This subject is covered in Unit II, Lesson 3,“Working with Objects.”

Uppercase SQL columnnames, commands,functions, schemas,table names

Use the SELECT command to viewinformation stored in the LAST_NAMEcolumn of the EMP table.

Convention Element Example


11i Manufacturing Functional Foundation Table of Contentsx

Arrow Menu paths Select File—> Save.Brackets Key names Press [Enter].

Commas Key sequences Press and release keys one at a time:[Alternate], [F], [D]

Plus signs Key combinations Press and hold these keys simultaneously:[Ctrl]+[Alt]+[Del]

Typographic Conventions in Code

Convention Element ExampleCaps andlowercase

Oracle Formstriggers

When-Validate-Item

Lowercase Column names,table names

SELECT last_nameFROM s_emp;

Passwords DROP USER scottIDENTIFIED BY tiger;

PL/SQL objects OG_ACTIVATE_LAYER(OG_GET_LAYER

(‘prod_pie_layer’))

Lowercaseitalic

Syntax variables CREATE ROLE role

Uppercase SQL commands andfunctions

SELECT useridFROM emp;

Typographic Conventions in Navigation Paths

This course uses simplified navigation paths, such as the following example, todirect you through Oracle Applications.

(N) Invoice > Entry > Invoice Batches Summary (M) Query > Find (B) Approve

This simplified path translates to the following:

1. (N) From the Navigator window, select Invoice > Entry > Invoice BatchesSummary.

2. (M) From the menu, select Query > Find.

3. (B) Click the Approve button.

Notations :

(N) = Navigator

(M) = Menu


11i Manufacturing Functional Foundation Table of Contentsxi

(T) = Tab

(I) = Icon

(H) = Hyperlink

(B) = Button

Typographical Conventions in Help System Paths

This course uses a “navigation path” convention to represent actions you performto find pertinent information in the Oracle Applications Help System.

The following help navigation path, for example—

(Help) General Ledger > Journals > Enter Journals

—represents the following sequence of actions:

1. In the navigation frame of the help system window, expand the GeneralLedger entry.

2. Under the General Ledger entry, expand Journals.

3. Under Journals, select Enter Journals.

4. Review the Enter Journals topic that appears in the document frame of thehelp system window.

Getting Help

Oracle Applications provides you with a complete online help facility.

Whenever you need assistance, simply choose an item from the Help menu topinpoint the type of information you want.

To display help for a current window:

1. Choose Window Help from the Help menu, click the Help button on thetoolbar, or hold down the Control key and type 'h'.

A web browser window appears, containing search and navigation frames onthe left, and a frame that displays help documents on the right.

The document frame provides information on the window containing thecursor. The navigation frame displays the top-level topics for yourresponsibility, arranged in a tree control.

2. If the document frame contains a list of topics associated with the window,click on a topic of interest to display more detailed information.


11i Manufacturing Functional Foundation Table of Contentsxii

3. You can navigate to other topics of interest in the help system, or chooseClose from your web browser's File menu to close help.

Searching for Help

You can perform a search to find the Oracle Applications help information youwant. Simply enter your query in the text field located in the top-left frame of thebrowser window when viewing help, then click the adjacent Find button.

A list of titles, ranked by relevance and linked to the documents in question, isreturned from your search in the right-hand document frame. Click on whichevertitle seems to best answer your needs to display the complete document in thisframe. If the document doesn't fully answer your questions, use your browser'sBack button to return to the list of titles and try another.


Applications ArchitectureChapter 1 - Page 1

Applications ArchitectureChapter 1



Applications Architecture

Copyright Oracle Corporat ion, 2001. All rights reserved.®

Applications Architecture

ILT Schedule: Timing Topic120 minutes Lecture120 minutes Total



Objectives


Objectives

After completing this lesson, you should be able todo the following:

• Describe Applications network architecture• Describe Applications database architecture• Describe Applications file system architecture• Describe Applications naming standards



Applications Network Architecture


Applications Network Architecture

DesktopDesktop DatabaseDatabase

Browser

Admin Server

WebServer

Concurrent ProcessingServer

Reports Server

ApplicationApplication

Data

Server

Client

Applet

Forms Server

Browser

Oracle Applications uses the Internet computing architecture. The Internetcomputing architecture shifts software administration from the desktoponto the middle tier, which resides in the data center with the databaseserver, thus lowering administration costs.

The Internet computing architecture is a multi-tier computing model wherevarious functions of the Oracle Applications architecture are distributedamong multiple levels, or tiers. Although many physical machines may beused in a configuration, scalability is derived from processing capabilitieson three separate levels: the desktop tier, the application tier, and thedatabase tier.



Desktop Tier


Desktop Tier

DesktopDesktop

Browser

Client

Applet

Browser

The client interface is provided through a Java applet using a Java-enabled web browser. The client can download the applet on demand andthe applet is cached locally for future use.

Forms Client AppletThe Forms Client Applet is a component of Oracle’s Developer applicationdevelopment tool. The applet sends user requests to the forms server andhandles such responses as screen updates, pop-up lists, and cursormovement. It can display any Oracle Applications screen and supportsfield-level validation, multiple coordinated windows, and data entry aidslike lists of values.

Web Browser/JInitiatorThe Forms Client Applet must run within a Java Virtual Machine (JVM) onthe desktop. For Oracle Applications the JVM is supplied by the JInitiatorprogram, which works in conjunction with the web browser.



Forms Client Applet


Forms Client Applet

DesktopDesktop

Java Enabled Browser

with JInitiator

ClientApplet

JAR files

JAR files

JAR files

Admin Server

WebServer


Reports Server

Forms Server

The Forms Client Applet is a general-purpose applet that supports allOracle Applications products including those with customizations andextensions. The Forms Client is packaged as Java ARchive (JAR) filesthat contain all the Java classes typically required to run OracleApplications forms. JAR files are digitally signed and should not beopened or expanded on-site.

The required and commonly used JAR files are downloaded from the WebServer once at the beginning of the client’s first session. Afterwards itremains in the browser’s local disk cache, ready for future sessions untilan updated version is released. All updates are installed on the applicationtier and downloaded to the client automatically through the use ofJInitiator. Other less commonly used JAR files are downloaded asneeded.



JInitiator


JInitiator

DesktopDesktop

Java Enabled Browser

with JInitiator

ClientApplet

Admin Server

WebServer


Reports Server

Forms Server

JInitiator is Oracle's Java Virtual Machine (JVM) that is implemented onthe desktop client as a plug-in (Netscape Communicator) or ActiveXcomponent (Microsoft Internet Explorer). JInitiator allows OracleApplications to run under the most current Java code set and is thepreferred method of accessing Oracle Applications.

When an end-user enters the desired Oracle Applications signon URLwithin the web browser, the browser will execute Oracle JInitiator. IfOracle JInitiator has not been previously installed, the browser willdownload the necessary installation executable to the desktop client.

Once installed, Oracle JInitiator will run the Forms Client Applet and startan Oracle Applications session.



Application Tier


Application Tier


Admin Server

WebServer


Reports Server

Forms Server

The Application Tier is the location of servers that provide the businesslogic and code processing. This tier is sometimes referred to as the middletier. There are five servers that comprise the application tier:

• The Web Server• The Forms Server• The Concurrent Processing Server• The Reports Server• The Admin Server

This tier provides the communication between the desktop tier and thedatabase tier. The application tier also supports load balancing amongmultiple forms servers to provide optimal scalability and processing.



Web Server


Web Server


Admin Server

WebServer


Reports Server

Forms Server

The Web Server processes the requests it receives over the network fromthe desktop clients. The Web Server consists of an HTTP listener, loadbalancer, and needed modules.

1 The HTTP listener accepts incoming HTTP requests (URLs) fromdesktop tier (browsers). If possible, the HTTP listener services therequest itself, for example, by returning a simple HTML web page.

2 If the page referenced by the URL needs some kind of advancedprocessing, e.g. PL/SQL or Java, the listener passes the request onto the module.

3 The load balancer determines the least loaded Forms Server nameand passes the information back to the desktop tier by means of adynamically created HTML page.

4 The desktop tier can then connect directly to the Forms Server bythe name it has been provided.

5 From this point on, all communication is between the client tier andthe Forms Server with the Forms Server handling thecommunication with the Oracle8i database.



Forms Server


Forms Server


Admin Server

WebServer


Reports Server

Forms Server

The Forms Server hosts the Oracle Applications forms and the formsruntime engine. The Forms Server is a Developer Server component thatmediates the communication between the desktop tier and the Oracle8idatabase, displaying client screens and causing changes in the databaserecords based on user actions. Data is cached on the forms server andprovided to the client as needed, such as when scrolling through multipleorder lines. The Forms Server communicates with the desktop tier in oneof three ways:

• a TCP/IP connection• a standard HTTP connection• a secure HTTPS connection

The Forms Server communicates with the Oracle8i database using Net8.



Concurrent Processing Server


Concurrent Processing Server


Admin Server

WebServer


Reports Server

Forms Server

Most interaction with Oracle Applications data is done through OracleApplications forms. There are also reporting programs and data updatingprograms that periodically need to be run. These programs may contain avery large number of computations, so to ensure that they do not interferewith interactive operations, they can be configured to run on a separatemachine called the Concurrent Processing Server.

Processes that run on the Concurrent Processing Server are calledconcurrent programs, and operate in the background while users continueto work on other tasks. You submit a request to run concurrent programsthrough Oracle Applications forms. This inserts a row into a databasetable specifying the program to be run. A monitoring process reads thetable and assigns the request to one of several concurrent managersrunning on one or more Concurrent Processing Servers. The concurrentmanager then runs the program generating log and output files on theConcurrent Processing Server.



Accessing Concurrent Processing Output


Accessing Concurrent Processing Output


Admin Server

WebServer


Reports Server

Forms Server

The Concurrent Processing Server communicates with the Oracle8idatabase using Net8. The results of a concurrent report are passed backto the Web Review Agent. The Web Review Agent passes a filecontaining the entire report to the Forms Server. The Forms Serverpasses the report back to the user’s browser a page at time.

You can use system settings to control the size of the files and pagespassed through the system.



Reports Server


Reports Server


Admin Server

WebServer


Reports Server

Forms Server

The Reports Server is used to produce reports for Oracle BusinessIntelligence System (BIS) products. This server is automatically installedon the same node as the Concurrent Processing Server, and its reportsare contained in the same directory with regular concurrent processingreports. However, reports generated by the Reports Server are monitoredand administered separately from concurrent reports.



Administration Server


Administration Server


Admin Server

WebServer


Reports Server

Forms Server

The administration server is the machine from which you maintain the datain your Oracle Applications database. You carry out the followingoperations from this server:

Installing and upgrading the databaseThis is only done when installing a new release or upgrading to a newrelease.

Applying database updatesMost bug fixes consist of new files and scripts that update databaseobjects. Use AutoPatch to update software on the database and theapplication tier servers.

Maintaining the Applications dataSome features such as multi-lingual support and Multiple ReportingCurrencies require regular maintenance to ensure updates are propagatedto the additional schemas used by these features. The AD Administrationprogram allows you to do this and other file system and databasemaintenance tasks.



Database Tier


Database Tier

DatabaseDatabase

Data

Server

The database tier holds all the data stored and maintained by the OracleApplications system. It also contains some processing code that is storedin the database to optimize performance. In Release 11i the database alsoincludes the Oracle Applications help files.

More specifically, the database tier contains Oracle8i Server files and anOracle Applications database instance that physically stores the tables,indexes, and other database objects for your installation.

By definition the data server does not communicate directly with thedesktop tier, but rather with the servers on the application tier that mediatethese communications.



Database Architecture


Database Architecture

Oracle8i Oracle8i

DatabaseDatabase

Oracle ApplicationsOracle Applications

File SystemFile System

Business dataBusiness data Processing ProgramsProcessing Programs

Within its multi-tier architecture, Oracle Applications stores its businessdata in Oracle8i database tables. Additional database objects such asindexes and views are used when processing these tables. Other objectslike code modules in the form of stored procedures and Help files are alsocontained in the database.



Oracle Applications Database Objects


Oracle Applications Database Objects

TablesTables

ViewsViews

IndexesIndexes

SequencesSequences

TriggersTriggers

PackagesPackages

Data ObjectsData Objects Code ObjectsCode Objects

SynonymsSynonyms

Oracle Applications uses an Oracle8i database to store its databaseobjects. These objects store both business data as well as some of thecode modules. In general, each application module has its own set ofdatabase objects. These objects can be broadly defined into twocategories.

Data objects are used for storing and accessing business data. Theseobjects include tables, indexes, and sequences.

Code objects are used to process the data. Code objects are stored inthe database and used for optimizing application processing. Code objectsinclude triggers, packages, synonyms and views.



APPS Schema


APPS Schema

GL SchemaGL Schema

INV SchemaINV Schema

APPS SchemaAPPS Schema

ViewsViews

TriggersTriggers

PackagesPackages

SynonymsSynonyms

Oracle Applications is tightly integrated. A procedure in one schema mayaccess data in a second schema and call a function in a third. Toaccomplish this, the procedure needs access to all three schemas.However, maintaining the access rights to all three is time-consuming anderror prone. Using the APPS schema solves this problem.

Each product’s schema grants full privileges to the APPS schema. TheAPPS schema has synonyms to all base product tables and sequences.Tthe APPS schema contains all code objects which access the dataobjects in the product schemas.



Additional Schemas


Additional Schemas

HR HR

PAY

PER

APPLSYSAPPLSYS

AOL

AD

APPLSYSPUBAPPLSYSPUB

APPSAPPS

The data objects for some products are combined within a single schema.For example, tables for the Human Resources products (PER, PAY, etc.)are combined under the HR schema; tables for the ApplicationTechnology Layer products (AOL, AD, etc.) are combined under theAPPLSYS schema.

There is an additional schema, APPLSYSPUB, that is used only duringthe signon process which does not actually own any database objects. Itonly has access to 1 database object, FND_USER_VIEW, and it only hasselect rights on it.

The APPS_MRC schema is used if you install the Multiple ReportingCurrencies option.



Multiple Organizations Views


Multiple Organizations Views

Org_IdOrg_Id Column Column

SO_Headers_All TableSO_Headers_All TableEastern Region

View

Western Region View

You can support multiple organizations running any Oracle Applicationsproduct with a single installation. These different organizations can reflectdifferent sets of books, different business groups, legal entities, operatingunits or inventory organizations. Organizations that share the samefunctional currency, Accounting Flexfield, and calendar can post to thesame set of books.

When you run any Oracle Applications product, you first choose anorganization either implicitly by choosing a responsibility or explicitly in aChoose Organization window. After you have chosen a particularorganization, all forms and reports display information for that organizationonly.

This Multiple Organization Architecture is a virtual partitioning solutionwhich secures information by operating unit using views within the APPSschema. These view definitions use the values in the Org_Id column toguarantee that only the information appropriate for that organization isreturned to the user.



Multiple Reporting Currencies


Multiple Reporting Currencies

Primary Set of BooksPrimary Set of Books Reporting Set of BooksReporting Set of Books

Currency: Currency: USDUSD

Currency: Currency:

BEFBEF

Primary ResponsibilityPrimary Responsibility Reporting ResponsibilityReporting Responsibility

STANDARD DataSTANDARD Data

GroupGroup

MRC DataMRC Data

GroupGroup

APPS_MRC SchemaAPPS_MRC SchemaAPPS SchemaAPPS Schema

The Multiple Reporting Currencies (MRC) feature allows you to report andmaintain accounting records at the transaction level in more than onefunctional currency. You do this by defining one or more reporting sets ofbooks in addition to your primary set of books. In your reporting sets ofbooks, you maintain records in a functional currency other than yourprimary functional currency. The data for the reporting set of books isstored in its own schema having its own tables and views.

MRC is supported for the following products: General Ledger, FixedAssets, Cash Management, Cost Management, Global AccountingEngine, Accounts Payable, Projects, Purchasing, and AccountsReceivable.



File System Architecture


File System Architecture

(to Product(to ProductDirectories)Directories)

(to Log /(to Log /Out andOut and

Java Files)Java Files)

(to Oracle8(to Oracle8and Toolsand Tools

Files)Files)

(to Oracle(to OracleApplicationsApplications

Database DataDatabase DataFiles)Files)

(to Oracle(to Oracle8i Files)8i Files)

<<envenv name>APPL name>APPL <<envenv name>DB name>DB<< env env name >DATA name >DATA

<< env env name >ORA name >ORA

<< env env name >COMN name >COMN

Oracle Applications stores files within several different file systems.Through the next several slides, we will discuss the contents of each ofthese file systems.



APPL_TOP


APPL_TOP

<<envenv name>APPL name>APPL

11.5.011.5.0

fndfndauau

11.5.011.5.0

invinv

11.5.011.5.0

<<dbdb name>. name>.envenv adminadmin

11.5.011.5.0

Administrative FilesAdministrative Files Product FilesProduct Files

The Oracle Applications file system contains the product files for OracleApplications itself. The top level directory path is defined in anenvironment variable APPL_TOP.

For both an installation and upgrade of Oracle Applications, Rapid Installcreates the new APPL_TOP, or top Applications directory and defaults theAPPL_TOP directory value to <db name>APPL. This variable is used insubsequent directory definitions, and is also used as a term to refer to aparticular Oracle Applications file system.

Technical note:The <db name>.env file is a very important file containing parametersdefining the Oracle Applications environment. Typically, Rapid Installcreates the <db name>.env file during the installation. Many of theparameters located in the <db name>.env file define important directorieswithin the Oracle Applications file structure. For example, the APPL_TOPdirectory is identified in the environment parameter APPL_TOP. Additionalparameters point to product top directories.



APPL_TOP


APPL_TOP


11.5.011.5.0

fndfndauau

11.5.011.5.0

invinv

11.5.011.5.0


11.5.011.5.0

Administrative FilesAdministrative Files Product FilesProduct Files

Each product has its own subdirectory. Since products can exist atdifferent version levels, the version is typically reflected in the subdirectoryname. Keep in mind that multiple releases and product versions cannotexist in a single APPL_TOP directory.

The product subdirectory name is defined in an environment variable<PROD>_TOP, where < PROD> is the product short name.

For example, the paths to these directories would be defined in thefollowing declarations in the <db name>.env file:

AU_TOP=APPL_TOP/au/11.5.0FND_TOP =APPL_TOP/fnd/11.5.0INV_TOP=APPL_TOP/inv/11.5.0



Product Directories


Product Directories

<PROD>_TOP<PROD>_TOP

adminadmin javajava mediamedia

binbin htmlhtml liblib mesgmesg

patchpatch

plsqlplsql

formsforms includeinclude loglog outout reportsreports

helphelp resourceresource

sqlsql

The product directory contains many subdirectories that group thedifferent files for that product. A typical product directory will have thesubdirectories shown, however, there may be differences based uponconfiguration.



Admin Directory


Admin Directory




patchpatch

plsqlplsql



sqlsql

driverdriver importimport odfodf sqlsql

The admin subdirectory contains files used by AutoUpgrade to upgradeproducts to the current release. The admin subdirectory has severalsubdirectories of its own:

driver: the upgrade driver files (.drv). The upgrade process is divided intoseveral phases. Phase driver files specify processing by phase. Examplefiles: glseq.drv creates sequences for the General Ledger (GL) productduring the sequence phase; glfile.drv, lists the GL files needed to run theapplication, gldep.drv, specifies dependencies between GL and otherproducts so that upgrade jobs between products are processed in thecorrect order.

import: the import files used to upgrade seed data.

odf: the object description files used to create tables and other databaseobjects.

sql: the SQL scripts and PL/SQL scripts used to upgrade data.



Bin Directory


Bin Directory




patchpatch

plsqlplsql



sqlsql

The concurrent programs, other C language programs and shell scripts foreach product are stored in its respective bin directory. Of particularimportance to Oracle Applications are the FND_TOP/bin and AD_TOP/bindirectories. Some of the programs you will find here include:

f60webmx: the applications form processor (in FND_TOP/bin)FNDLIBR: the concurrent manager (in FND_TOP/bin)startmgr: a Unix shell script to start the concurrent manager (inFND_TOP/bin)fdfcmp: the flexfield compiler (in FND_TOP/bin)FNDMDGEN: a message file generator (in FND_TOP/bin)adadmin: the AD Administration utility (in AD_TOP/bin)adpatch: the AutoPatch utility (in AD_TOP/bin)



Forms Directory


Forms Directory




patchpatch

plsqlplsql



sqlsql

USUS

The forms directory contains Oracle Forms files. Oracle Forms may beportable source files (.fmb files) or generated runtime files (.fmx files). Theinstallation utility generates form files by converting the .fmb source file to.fmx runtime files. The source files are stored in AU_TOP/forms sogeneration of runtime files can be done more easily.

A subdirectory exists for the language(s) installed. This subdirectory isnamed according to the language, e.g., /US for American English forms,/D for German forms, /F for French forms.



Help Directory


Help Directory




patchpatch

plsqlplsql



sqlsqlUSUS

The help directory contains the online help source files. These files areimported into the database during an install or an upgrade to optimize theperformance of online help. Under the help directory, there is a languagedirectory to store the help files for each language in which your arerunning Oracle Applications.



HTML Directory


HTML Directory




patchpatch

plsqlplsql



sqlsql

The html subdirectory contains HTML, Javascript, and Java Server Pagefiles used by various products. These files are used primarily by productsthat have a Self-Service interface. The Javascript (.js) and Java ServerPage (.jsp) files are kept in the main directory. HTML files are kept insubdirectories by language.



Include Directory


Include Directory




patchpatch

plsqlplsql



sqlsql

The include directory contains header (.h) files. These files may berequired by the files contained in the lib directory for the relinking process.

Note: Not all products have an include directory.



Java Directory


Java Directory




patchpatch

plsqlplsql



sqlsql

*.jar*.jar

makemake jarjar

This directory is used to initially store Java files. During installation orupgrade, the files are copied to the directory identified by the JAVA_TOPenvironment variable (this directory is defined in the environment file youcreate during the installation process). This is done to optimizeprocessing.

For each product that uses Java, there will be one or more Java ARchive(JAR) files under the jar directory. There will also be a product specific.dep file under the make directory that specifies the dependenciesbetween this product and other products using Java.



Lib Directory


Lib Directory




patchpatch

plsqlplsql



sqlsql

At some time, you may need to relink Applications programs, for exampleif you upgrade the Oracle8i server. The lib subdirectory contains filespertinent to the process of relinking Applications programs:

object files: (.o files), one for each C program to relink.

library file: (.a file) the compiled C code common to that product’sprograms.

makefile: (.mk file) specifying how to relink the .o file(s) with the .a file(s)to create the newly linked C programs.



Log and Out Directories


Log and Out Directories




patchpatch

plsqlplsql



sqlsql

When the concurrent managers run Oracle Applications reports or dataupdate programs, they write output files as well as diagnostic log files andtemporary files, to directories defined during the installation process.There are two methods for storing log and output files: 1) in each product’slog and out directories, which is the default or 2) a common log and outputsubdirectory.

The log directory holds concurrent log files from each concurrent requestas well as the concurrent manager log files. The out directory holds theconcurrent report output files.

The default locations for these two files are <PROD>_TOP/log and<PROD>_TOP/out, but you can change the default directory and thedefault file names by changing the APPLLOG and APPLOUT environmentvariables in the <db name>.env file.

You can consolidate all product log and out files into one directory bydefining the APPLCSF environment variable in the <db name>.env. Thisparameter identifies a directory to hold all log and output files.



Media Directory


Media Directory




patchpatch

plsqlplsql



sqlsql

The Applications Forms Client Applet displays graphics in the form of .giffiles. The media directory contains all product specific .gif files.



Mesg Directory


Mesg Directory




patchpatch

plsqlplsql

formsforms includeinclude loglog reportsreports


sqlsql

US.US.msgmsg

Applications forms display messages at the bottom of the screen and inpop-up boxes. Applications concurrent programs also print messages intheir log and output files.

These messages can be translated into different languages and are storedin message files separate from the forms and programs. Each product’smesg directory contains one or more files for the language-specificmessages that the product uses:

• .msb files contain the binary messages used at runtime.• a standard American English install will contain a US.msb file.• an equivalent German message file will be titled D.msb.



Patch Directory


Patch Directory




patchpatch

plsqlplsql



sqlsql

driverdriver sqlsql odfodf importimport

115115

Any updates to Oracle Applications data or data model use a directorynamed patch to store the patch files. Patch files are grouped by releasewithin the following subdirectories:

• driver: contains the driver files (.drv). Phase driver files specifyprocessing by phase.

• sql: contains sql (.sql) and PL/SQL (.pls) scripts used to update thedatabase.

• odf: contains object description files (.odf) to update the datamodel.

• import: contains lct and slt files to update the seed data.



PLSQL and Resource Directories


PLSQL and Resource Directories




patchpatch

plsqlplsql



sqlsql

These directories are used for unloading PL/SQL libraries used byApplications reports and forms.

• The files in the plsql subdirectory (.pll files) are used by OracleReports.

• The files in the resource subdirectory (.pll and .plx files) are used byOracle Forms.

After these files are unloaded, they are moved to equivalent subdirectoriesunder the AU_TOP directory.

Note: Not all products have PL/SQL libraries.



Reports Directory


Reports Directory




patchpatch

plsqlplsql



sqlsql

USUS

This directory contains the report files for this product. For each reportthere is a portable binary .rdf file. The AD Administration utility canregenerate these reports by converting them to their executable format(.rex files) and then back to portable format. This is usually recommendedso the PL/SQL is optimally compiled for the platform.

Reports for non-English languages are stored in their own language-specific directory under the reports directory.



SQL Directory


SQL Directory




patchpatch

plsqlplsql



sqlsql

There are many SQL*Plus scripts used by Oracle Applications forconcurrent processing. These scripts typically produce reports or performconcurrent processing. These scripts are stored as .sql files in thissubdirectory.



AD Directory


AD Directory


adadauau

11.5.011.5.0

fndfnd

11.5.011.5.0


11.5.011.5.0 11.5.011.5.0

admin bin libadmin bin lib

AD stands for Applications DBA. The Applications DBA product is a set oftools for installing, upgrading, and administering the Oracle Applicationsenvironment. The ad directory contains utilities such as AutoUpgrade,AutoPatch (adpatch) and the AD Administration (adadmin) utility.



AU Directory


AU Directory


11.5.011.5.0

adadauau fndfnd

11.5.011.5.0


11.5.011.5.0 11.5.011.5.0

javajava reportsreportsadmin forms plsql resourceadmin forms plsql resource

AU stands for Application Utilities. The AU_TOP directory containsproduct files that are consolidated in a single location for optimalprocessing. These files include:

• PL/SQL libraries used by Oracle Reports. These are also stored inthe products’ plsql subdirectories.

• PL/SQL libraries used by Oracle Forms. These are also stored inthe products’ resource subdirectories.

• Oracle Forms source files. These are also stored in the products’forms subdirectories.

• A copy of all Java files used by JInitiator when regenerating thedesktop client jar files. The public copy of all Java files are stored inJAVA_TOP.



Admin Directory


Admin Directory


adadauau fndfnd<<dbdb name>. name>.envenv adminadmin

11.5.011.5.0

adovarsadovars..envenvadconfigadconfig..txttxt adsetenvadsetenv

preupgpreupgloglog

restartrestart<<dbdb name> name>

loglog outout restartrestart

outout

adrelinkadrelink

applprodapplprod..txttxtapploraapplora..txttxt

The APPL_TOP/admin directory contains files and scripts used by theAutoUpgrade utility during the upgrade process. These include:

• a custom environment file defining certain file locations(adovars.env)

• scripts run during the upgrade• text files read by AutoUpgrade• a preupg directory containing product-specific pre-upgrade scripts• log and out directories for upgrade log and output files• a restart directory where AD programs create restart files

Most AD programs put their log, out and restart files in a separate <dbname> subdirectory. The value for <db name> comes from theTWO_TASK or ORACLE_SID parameters. Some programs when run fromthe command line, cannot access the <db name> value and thereforestore their log, out, and restart files in the log, out and restart directoriesdirectly under the APPL_TOP/admin directory.



Admin Directory Text Files


Admin Directory Text Files


adadauau fndfnd<<dbdb name>. name>.envenv adminadmin

11.5.011.5.0

adovarsadovars..envenvadconfigadconfig..txttxt adsetenvadsetenv

preupgpreupgloglog

restartrestart<<dbdb name> name>

loglog outout restartrestart

outout

adrelinkadrelink

applprodapplprod..txttxtapploraapplora..txttxt

There are many text files stored under the admin directory. These files areused by many different utilities. Some of the files include:

• adconfig.txt: environmental configuration variable values• adlinkbk.txt: files adrelink should backup rather than delete• applcust.txt: registered customizations• applora.txt: minimum or required settings for database initialization

parameters• applprod.txt: products available in this release• applterr.txt: territory description for Localizations



Common Components Directory


Common Components Directory

icxcaboicxcabo.zip.zip

loglogoutout htmlhtml adminadmin**javajava utilutil

appsapps

oracleoracle apps.zipapps.zip

fndfnd

jarjar

ApacheApache JRE118JRE118

<<envenv name>COMN name>COMN

icxicx

USUS WebToolsWebTools*.zip*.zip

fndewtfndewt.jar.jarfndswingfndswing.jar.jar

glgl

jarjarjarjar

mrpmrp(unzipped into)(unzipped into)

htmlhtml

*contains*containsRapidRapidInstallInstallscriptsscripts

xmlxml jdbcjdbc

The <env name>COMN, or COMMON_TOP, directory contains directoriesand files that are used across products or are used in conjunction withother third-party products. This directory also contains the consolidatedlog and output directories used by concurrent processing.

Unlike previous releases, Release 11i supports the placement of the javadirectory (JAVA_TOP) and the HTML directory (OAH_TOP) anywhere inyour file system.

Note: Unlike APPL_TOP, there is no environment variable that pointsdirectly to COMMON_TOP. However, if a standard installation or upgradeis done, the environment variable OAD_TOP will point to the directory thatis COMMON_TOP.



Copying Java Files: apps.zip


Copying Java Files: apps.zip

<<envenv name>APPL name>APPL <<envenv name>COMN name>COMN

javajava

oracleoracle

appsapps

glgl

jarjar

fafa

jarjarapps.zipapps.zip

11.5.011.5.0auau

javajava

jdbcjdbc xmlxmlapps.zipapps.zip

Oracle Applications Release 11i makes extensive use of Java. ManyOracle Applications products use Java on the front end for forms and onthe back end for data processing. Java files are installed into OracleApplications product directories and then copied to directories under theCommon Components directory to facilitate processing.

Apps.zip is a patchable archive of all Java class files required by OracleApplications. Individual Java class files are never present on the filesystem. Apps.zip is located in AU_TOP/java and a public copy is storedunder JAVA_TOP. The public copy is the one utilized in a web serverenvironment, as the web server can see the JAVA_TOP stored apps.zipbut, for security reasons, cannot access the APPL_TOP apps.zip directly.



Technology Stack Directories


Technology Stack Directories

(Oracle8i)(Oracle8i)

<<envenv name>ORA name>ORA

8.08.0 iASiAS 8.18.1

binbin liblib

javajava

forms60forms60

reports60reports60

graphics60graphics60

<<envenv name>DB name>DB

ApacheApache

modplsqlmodplsqlApacheApache BC4JBC4J

perlperljservjserv

To take advantage of the technology stack components’ latest features,there are multiple ORACLE_HOME directories under the TechnologyStack directories. This slide shows which technology stack componentsare located in each directory.



Database Data Files


Database Data Files

Disk 1

Disk 2 Disk 3

Disk 4

cntrl01log01alog02arbs01

cntrl02log01blog02bsystem01ctxd01

cntrl03

temp01product

dataproduct

index

The <env name>DATA file system contains the .dbf files that comprise theOracle Applications database itself. The Rapid Install utility installs all thesystem, data, and index files across four disks. You can specify mountpoints and directory names during the installation. Oracle ApplicationsRelease 11i uses an Oracle8i database server.



File Types


File Types

• Executables and component files• DataMerge files• Forms files• Java ARchive files• Log and output files• PL/SQL files• Reports files• Message files

The Oracle Applications file system contains a variety of files. This listdescribes some of the types of files you will find in the file system:

.a Library files that contain compiled C code

.ctl DataMerge control file

.dat DataMerge Import/Export parameter file

.dmp Import/Export data export file

.drv Driver files

.env Environment files in UNIX

.exp DataMerge data export file

.fmb Binary forms files

.fmx Executable forms files

.h C header files

.jar Java Archive files

.log Log files



File Types


File Types

• Executables and component files• DataMerge files• Forms files• Java ARchive files• Log and output files• PL/SQL files• Reports files• Message files

.msb Binary message files

.o Object files us ed t o relink Applicat ions

.odf Object Des cript ion Files

.out Output files

.pdf Acrobat files or report output

.plb PL/SQL package bodies

.pll PL/ SQL s hared libraries

.pls PL/SQL package specifications

.rdf Oracle Reports files (non-executable)

.req Log files from a concurrent reques t

.rex Oracle Reports executables

.sql SQL*Plus s cripts



Naming Standards


Naming Standards

• Database objects• Form file standards• PL/SQL packages and procedures• Reserved words

INSTRUCTOR NOTE:

The definitive source of information on Naming Standards is the OracleApplications Developer's Guide, Release 11i. In Chapter 31 of thatmanual, it discusses these items in much more detail.



Database Objects


Database Objects

• Includes a header with name, purpose, arguments,special usage notes, and creation/update history.

• Tables - prod_objects• Views - table_V or table_criteria_V• Triggers - table_Ti• Synonyms - table or view• Constraints - table_PK, table_Ui, or table_Fi

Tables: prod is the short name of the product. objects is the object storedin the table and should be plural. The table name should be 20 charactersor less.

View: table is the name of the root table the view is based on. The criteriais a qualifier of the objects shown by the view. Use the criteria qualifier ifusing table name alone is not unique, the view is based on a join of 2 ormore tables, the view contains a WHERE clause, or the view is unusual.

Triggers: table is the name of the table on which the trigger is based, andi is a unique ID starting at 1.

Synonyms: Your synonym should have the same name as the table orview it is based on.

Constraints: _PK is for Primary Keys. _Ui is for unique indexes. _Fi isfor foreign keys. table is the name of the table on which the constraint iscreated, while I is a unique id starting at 1. You should name all of yourconstraints so that you can enable or disable them easily.



Database Objects


Database Objects

• Packages - prod_module or prod_description• Procedures - verb_noun• Table Handler - table_PKG• Private Pkgs - package_PRIVATE• Forms PL/SQL - prod_verb_noun

Packages: prod is the product short name, module is a functionalmodule, and description is a one or two word explanation of the purpose.Stored package names should be 24 characters or less.

Packaged Procedures: verb_noun is a brief explanation of the purpose.

Table Handler Package and Procedures: table is the name of the tableon which the package acts. The package name should be 24 charactersor less.

Private Packages: package is the name of the owning package.

Forms PL/SQL Program Units: prod is the product short name, andverb_noun is a brief explanation of the purpose.



Database Objects


Database Objects

• PL/SQL Vars. - variable or X_variable• PL/SQL Global - G_variable

PL/SQL Variables: variable should be a logical, meaningful, and concisename. Precede variable name with X when the variable is used in a SQLstatement, so that there is no possibility of conflicts with database objectnames or confusion as to which are PL/SQL variables and which aredatabaseobjects.

PL/SQL Global Variables: variable should be a logical, meaningful, andconcise name. Precede variable name with G to distinguish globalvariables from local variables.



Forms File Standards


Forms File Standards

• Forms Files - pppggxxx.fmb

ppp is the two or three character product short name, ggis a two–character abbreviation for the functional group,and xxx is a three–character abbreviation for theexplanation of the purpose.

fmb is the suffix for the source binary file, and fmx is thesuffix for the executable binary file.

All file names must be no greater than 8 chars in length plus a threecharacter extension (FILENAME.ext). The files names must be all capsexcept for the extension. This will provide a consistent naming schemeacross all platforms.



PL/SQL Packages, Procedures and Source Files


PL/SQL Packages, Procedures andSource Files

• PL/SQL Stored Package Source File Namespppgxxxs.pls or pppgxxxb.pls

• PL/SQL Table Handlers Source File Namespppgixxs.pls or pppgixxb.pls

• PL/SQL Library File Namespppggxxx.pll, pppggxxx.plx, or pppggxxx.pld

• Icon File Namesppxxxxxx.ico or ppxxxxxx.bmp

PL/SQL packages and procedures are documented slightly differently.Packages do not have Arguments sections and procedures do not need tohave History sections. Begin all SQL and PL/SQL files with the followinglines (after the copyright header):

SET VERIFY OFFWHENEVER SQLERROR EXIT FAILURE ROLLBACK;

End all SQL and PL/SQL files with the following lines:COMMIT;EXIT;

ppp is the two or three character product short name, gg is a one or twocharacter abbreviation for the functional group, and xxx is a characterabbreviation for the explanation of the purpose. s indicate a specificationfile, and b indicates a body file. Each file defines only one packagespecification or body.



Reserved Words


Reserved Words

In addition to all words reserved by Oracle8, PL/SQL,and Oracle Forms, do not use any words that beginwith the following letters (including the wordsthemselves):• FOLDER• CALENDAR• APPCORE



Summary


Summary

In this lesson, you should have learned how to:• Describe Applications network architecture.• Describe Applications database architecture.• Describe Applications file system architecture.• Describe Applications naming standards.


Applications BasicsChapter 2 - Page 1

Applications BasicsChapter 2



Applications Basics


Applications Basics




Objectives


Objectives


• Use basic Applications tools• Describe concurrent processing• Describe flexfields• Describe alerts• Describe workflow



Basic Applications Tools



• (Help) About Oracle Applications• (Help) Record History• (Help) Diagnostics �� Examine• (Help) Diagnostics �� Examine … choose

$DESCRIPTIVE_FLEXFIELD$ block• (Help) Diagnostics �� Examine … choose

$ENVIRONMENT$ block• (Help) Diagnostics �� Examine … choose

$PROFILES$ block• (Help) Diagnostics �� Examine … choose SYSTEM

block … choose LAST_QUERY field

The purpose of the commands shown above.

* Shows Applications version, Form shortname, Form version* Shows primary table/view form is using* Shows values of fields not visible on form* Shows user-friendly names of Descriptive Flexfields* Shows values of primary environment variables* Shows value in effect for any given profile option for that user.* Shows the SELECT statement that was last executed by your form.

Note: Should also mention the FORM_STATUS and ERROR_ITEMfields in this block.






• (Help) Diagnostics �� Display Database Error• (Help) Diagnostics �� Trace (checkbox)• (Navigate) Concurrent �� Program �� Define• Utilities: SQL Trace profile option

The purpose of the commands shown above.

* Shows any database error message.* Turning on/off forms tracing. Trace file (*.trc) is put into

user_dump_dest. If user does not know value of user_dump_dest,they can look at the init.ora file ($ORACLE_HOME/dbs) or run thisstatement. select name, value from v$parameter where name =‘user_dump_dest’;

* You can do two things here. You can check the "Enable Trace"checkbox. This will turn on SQL tracing at the session level for theprogram. For Oracle Reports, you can also put the line"TRACEOPTS=TRACE_ALL" into the "Options" field. This will doReports runtime tracing.

* This profile option can only be set by the System Administrator.



Overview of Concurrent Processing


Overview of Concurrent Processing

• Concurrent requests• Concurrent programs• Concurrent managers

Applications is undergoing a transformation. Prior to 11i, most userinteraction was done through forms. In 11i, the bulk of the interaction isdone through the self-service web forms. Concurrent Processing is inplace to support the forms-based users.

For forms-based users, they can run reports from the data entered into thesystem. When a report is needed, the command to run the report is aconcurrent request. The program that generates the report is a concurrentprogram. Concurrent programs are controlled by a concurrent manager.

Each time a users request a concurrent program to be run, their request isinserted into a database table, and is uniquely identified by a request ID.Concurrent managers read requests from this table.

A concurrent request proceeds through three, possibly four, life cyclestages or phases. Within each phase, a request’s condition or status maychange. The various phases that a concurrent request can go through arePending, Running, Completed, and Inactive.



Overview of Flexfields


Overview of Flexfields

• Key flexfields• Descriptive flexfields

A flexfield is a field made up of sub–fields, or segments. A flexfieldappears on your form as a pop–up window that contains a prompt for eachsegment. Each segment has a name and a set of valid values. There aretwo types of flexfields: key flexfields and descriptive flexfields.

Most organizations use ”codes” made up of meaningful segments(intelligent keys) to identify general ledger accounts, part numbers, andother business entities. Each segment of the code can represent acharacteristic of the entity. Oracle Applications store these ”codes” in keyflexfields. Key flexfields are flexible enough to let any organization use thecode scheme they want, without programming.

Descriptive flexfields provide customizable ”expansion space” on yourforms. You can use descriptive flexfields to track additional information,important and unique to your business, that would not otherwise becaptured by the form.



Overview of Alerts


Overview of Alerts

• Event alerts• Periodic alerts

Oracle Alert is your complete exception control solution. You can defineone of two types of alerts: an event alert or a periodic alert. An event alertimmediately notifies you of activity in your database as it occurs. Aperiodic alert, on the other hand, checks the database for informationaccording to a schedule you define.

An exception reporting system should do the following:* Keep you informed of database exception conditions, as they

occur.* Take predefined actions when it finds exceptions in your database,

without user intervention.* Perform routine database tasks automatically, according to the

schedule you define.* Do all of the above through simple use of your email, both direct

emails and distribution lists.



Overview of Workflow


Overview of Workflow

• Oracle Workflow Builder• Workflow Engine• Workflow Definition Loader• Email integration and internet-enabled workflow• Workflow Monitor

Oracle Workflow lets you automate and continuously improve businessprocesses, routing information of any type according to business rules youcan easily change to people both inside and outside your enterprise.

* Oracle Workflow Builder lets you create, view, or modify a businessprocess with simple drag and drop operations.

* The Workflow Engine embedded in the Oracle8 server monitorsworkflow states and coordinates the routing of activities for aprocess.

* The Workflow Definitions Loader is a utility program that movesworkflow definitions between the database and a flat file.

* Email users can receive notifications of outstanding work items andcan respond to those notifications. And, any user with access to astandard Web browser can be included in a workflow.

* Workflow administrators and users can view the progress of a workitem in a workflow process by connecting to the Workflow Monitorusing a standard Web browser that supports Java.



Summary


Summary

In this lesson, you should have learned how to:• Use basic Applications tools.• Describe the basics of concurrent processing.• Describe the basics of flexfields.• Describe the basics of alerts.• Describe the basics of workflow.


ERDs and Applications TechnologyChapter 3 - Page 1

ERDs and ApplicationsTechnologyChapter 3



ERDs and Applications Technology


ERDs and Applications Technology




Objectives


Objectives


• Read and understand Entity RelationshipDiagrams (ERDs)

• Read and understand Oracle Applications'Applications Technology ERDs



Entity Relationship Diagrams (ERDs)


Entity Relationship Diagrams (ERDs)

•• It describes exactly the information needs of theIt describes exactly the information needs of thebusiness.business.

•• It facilitates discussion.It facilitates discussion.•• It helps to prevent mistakes, misunderstanding.It helps to prevent mistakes, misunderstanding.•• It forms important “Technical Reference”It forms important “Technical Reference”

documentation.documentation.•• It is the basis for the physical creation of databaseIt is the basis for the physical creation of database

objects within the Oracle Applications database.objects within the Oracle Applications database.

Entity Relationship Diagrams, or ERDs, emerged from the work of Dr.Peter Chen and others during the 1970s. They were looking for a meansto simplify the representation of large and complex data storage concepts. ERDs are conceptual models that show entities and relationships. While itreally is that simple, we should answer the question, why?



What is an Entity?


What is an Entity?

• An Entity is:– “Something” of significance to the business

about which data must be known.– A name for the things that you can list.– Usually a noun.

• Examples: objects, events• Entities have instances.

In Oracle Applications, entities are going to be tables.



Entities and Instances


Entities and Instances

PERSONPRODUCT

PRODUCT TYPEEMPLOYMENT CONTRACT

JOBSKILL LEVEL

TICKET RESERVATIONPURCHASE

ELECTIONPRINTER PREFERENCE

DOCUMENT VERSION

John Doe2.5 x 35 mm copper nailnailmy previous contractviolinistfluenttonight: Hamlet in the Royalthe CD I bought yesterdayfor parliament next fall…...

In Oracle Applications, instances are the records stored in the table(entity).



Attributes


Attributes

• Also represents something of significance to thebusiness

• Is a single valued property detail of an entity• Is a specific piece of information that:

– Describes– Quantifies– Qualifies– Classifies– Specifiesan entity.

In Oracle Applications, attributes are the columns of the table (entity).



Relationships


Relationships

• Also represent something of significance to thebusiness

• Express how entities are mutually related• Always exist between two entities (or one entity

twice)• Always have two perspectives• Are named at both ends

In Oracle Applications, relationships are the primary key, foreign keys, andunique indexes that are maintained on the table (entity).



Relationships


Relationships

JOB

waiterwaiter

cookcookwaitresswaitress

managermanager

financial controllerfinancial controllerporterporter

piano playerpiano player

AhmedAhmedJillJill AdamAdam

MariaMaria

EMPLOYEEEMPLOYEE

Numerical observation:• All EMPLOYEES have a JOB• No EMPLOYEE has more than one JOB• Not all JOBS are held by an EMPLOYEE• Some JOBS are held by more than one EMPLOYEE

ShintaroShintaro dish washerdish washer

To equate this diagram to Oracle Applications, you make some simpleconversions.

• EMPLOYEE and JOB are tables.• The EMPLOYEE table has several records, Shintaro, Jill, Ahmed,

Adam, and Maria.• The JOB table has several records, manager, waitress, cook, dish

washer, financial controller, waiter, porter, and piano player.

NOTE: This is an incomplete ERD in that the attributes used to connectthe EMPLOYEE to the JOB are not detailed.



Drawing Entities in ERDs


Drawing Entities in ERDs

• Drawn as a “softbox”• Name singular• Name inside• Neither size,

nor positionhas a specialmeaning

EMPLOYEE

TICKETRESERVATION

JOB ASSIGNMENT

JOB

ORDEREL

ECTI

ON

During design, entities usually lead to tables.



Drawing Attributes in ERDs


Drawing Attributes in ERDs

*o

EMPLOYEE Family Name Addresso Birth Dateo Shoe Sizeo Email

JOB Titleo Description

During design, attributes lead to columns.

**

*

Mandatory attribute, that is, known andavailable for every instanceOptional attribute, that is, unknown orunimportant to know for some instances



Drawing Relationships in ERDs


Drawing Relationships in ERDs

Jobs are held by one or more employees

An employee has exactly one jobAn employee has exactly one job

EMPLOYEE JOB has

held by

During design, relationships lead to foreign keys.



Perspectives of Relationships in ERDs


Perspectives of Relationships in ERDs

EMPLOYEE JOBhashas

held byheld by

mandatory:mandatory: optional:optional:



Reading Relationships in ERDs


Reading Relationships in ERDs

““EachEach P P may be may be split intosplit into one or more one or more Qs Qs””

““EachEach Q Q must be must be part ofpart of exactly oneexactly one P P””

P split intosplit into Qpart ofpart of



Oracle Applications ERD Standards



Table Name

# Primary Key Column 1# Primary Key Column 2

…

# Primary Key Column n

TABLE

Let's start with the basics. Oracle Applications ERDs do not use"softboxes". They use regular rectangles. This has no impact on readingOracle Applications ERDs other than the shape change.

At the top of each entity, or Table, will be the Table Name. Beneath theTable Name is the primary key columns for that Table. There will alwaysbe at least 1 column, and there may be several.

Generally, Oracle Applications does not list mandatory columns. Theseare too numerous to include. However, sometimes for sake of clarity, amandatory column will be included. If so, that column will be marked withan asterisk (�).

NOTE: Generally, Oracle Applications ERDs use size to indicateimportance and relative sizing to other Tables. This is done in the mostgeneric of uses. For almost any case, you could easily find a customer,who because of the special case of their business needs, has Tables thataren't sized in the proportions shown. Use this as a simple guide.






Table Name 1

# Primary Key Column 1

Table Name 2


Foreign KeyConstraint

Delete RuleIndicator

RecursiveForeign Key

This diagram shows how Oracle Applications ERDs diagram relationships.Oracle Applications ERDs use solid lines to indicate mandatoryrelationships where a value entered in the column in the foreign key mustmatch a value in the primary key column. Applications ERDs use dashedlines (- - - - -) to indicate optional relationships where a value entered inthe column in the foreign key must match either a value in the primary keycolumn, or else it must be null. Oracle Applications ERDs also haverecursive foreign keys or pig's ears.

The Delete Rule Indicator determines the action to be taken when anattempt is made to delete a related row in a join table. A line through theforeign key constraint, as shown on the above diagram, indicates that thisaction is restricted.

NOTE: Oracle Applications ERDs are not always clear on foreign keyrelationships. For example, Table 2's primary key is the foreign key intoTable 1 even though it may not be part of Table 1's primary key. As such,the foreign key relationship would be implied rather than explicitlydescribed.






Table Name 1

# Primary Key Col. 1

Table Name 3


Table Name 2

# Primary Key Col. 1

Oracle Applications ERDs use an arc. The arc, shown above with circlesand an arc, is used to specify that, for any given row in a table, a valuemust be entered in one of the arc columns. The remaining columns withinthe arc must be null.

On the next several pages, I’ve reproduced the slides from the AppliedTechnology ERDs. The single best source of the actual diagrams is theAOL Technical Reference Manual (TRM). An online copy of that TRM hasbeen provided in your student materials. Reference that as a better andmore complete source.

NOTE: Over the course of the next several slides, we are going toreproduce the ERD diagrams for Applications Technology objects.Because of the limitation of Powerpoint, these diagrams will be simplifiedcompared to normal ERDs.



Key Flexfields


Key FlexfieldsFND_IFS

FND_SAV FND_IFSTRFND_SFA

FND_FVRS

FND_FVR

FND_CIFS

FND_CIFFND_SAT

FND_FVS

FND_FVQFND_FERL

FND_FVRL

FND_FIRL

FND_VAT

FND_IF

FND_APP FND_TAB FND_FWPWF_RPV

The diagram above shows the Key Flexfields ERD. Because of its size,we had to compress its presentation. The following listing gives you theinformation key for the diagram above.

Abbrev. Table NameFND_IFS FND_ID_FLEX_SEGMENTS

Primary Keys: APPLICATION_IDID_FLEX_CODEID_FLEX_NUMAPPLICATION_COLUMN_NAME

FND_SAV FND_SEGMENT_ATTRIBUTE_VALUESPrimary Keys: APPLICATION_ID

ID_FLEX_CODEID_FLEX_NUMAPPLICATION_COLUMN_NAMESEGMENT_ATTRIBUTE_TYPE

FND_SFA FND_SHORTHAND_FLEX_ALIASESPrimary Keys: APPLICATION_ID

ID_FLEX_CODE



ID_FLEX_NUMALIAS_NAME

FND_IFSTR FND_ID_FLEX_STRUCTURESPrimary Keys: APPLICATION_ID

ID_FLEX_CODEID_FLEX_NUM

FND_FVS FND_FLEX_VALUE_SETSPrimary Keys: FLEX_VALUE_SET_ID

FND_FVRS FND_FLEX_VALIDATION_RULE_STATSPrimary Keys: APPLICATION_ID

ID_FLEX_CODEID_FLEX_NUM

FND_FERL FND_FLEX_EXCLUDE_RULE_LINESPrimary Keys: RULE_LINE_ID

FND_FVR FND_FLEX_VALIDATION_RULESPrimary Keys: APPLICATION_ID

ID_FLEX_CODEID_FLEX_NUMFLEX_VALIDATION_RULE_NAME

FND_FVQ FND_FLEX_VALIDATION_QUALIFIERSPrimary Keys: FLEX_VALUE_SET_ID

ID_FLEX_APPLICATION_IDID_FLEX_CODESEGMENT_ATTRIBUTE_TYPEVALUE_ATTRIBUTE_TYPE

FND_FVRL FND_FLEX_VALIDATION_RULE_LINESPrimary Keys: RULE_LINE_ID

FND_VAT FND_VALUE_ATTRIBUTE_TYPESPrimary Keys: APPLICATION_ID

ID_FLEX_CODESEGMENT_ATTRIBUTE_TYPE



VALUE_ATTRIBUTE_TYPE

FND_FIRL FND_FLEX_INCLUDE_RULE_LINESPrimary Keys: RULE_LINE_ID

FND_CIFS FND_COMPILED_ID_FLEX_STRUCTSPrimary Keys: APPLICATION_ID

ID_FLEX_CODEID_FLEX_NUMCOMPILER_VERSION_NUMSEQUENCELANGUAGE

FND_SAT FND_SEGMENT_ATTRIBUTE_TYPESPrimary Keys: APPLICATION_ID

ID_FLEX_CODESEGMENT_ATTRIBUTE_TYPE

FND_CIF FND_COMPILED_ID_FLEXSPrimary Keys: APPLICATION_ID

ID_FLEX_CODECOMPILER_VERSION_NUMSEQUENCELANGUAGE

FND_IF FND_ID_FLEXSPrimary Keys: APPLICATION_ID

ID_FLEX_CODE

FND_APP FND_APPLICATIONPrimary Keys: APPLICATION_ID

FND_TAB FND_TABLESPrimary Keys: APPLICATION_ID

TABLE_ID

WF_RPV WF_RUNNABLE_PROCESSES_V

FND_FWP FND_FLEX_WORKFLOW_PROCESSES



Primary Keys: APPLICATION_IDID_FLEX_CODEID_FLEX_NUMWF_ITEM_TYPE



Descriptive Flexfields


Descriptive Flexfields

FND_DESCR_FLEX_COLUMN_USAGES

FND_FLEX_VALUE_SETS

FND_DESCRIPTIVE_FLEXS

FND_DESCR_FLEX_CONTEXTS

FND_TABLES

FND_APPLICATION

FND_COMPILED_DESCRIPTIVE_FLEXS FND_DEFAULT_CONTEXT_FIELDS

The diagram above shows the Descriptive Flexfields ERD. Because of itssize, we had to compress its presentation. The following listing gives youthe information key for the diagram above.

Table NameFND_DESCR_FLEX_COLUMN_USAGESPrimary Keys: APPLICATION_ID

DESCRIPTIVE_FLEXFIELD_NAMEDESCRIPTIVE_FLEX_CONTEXT_CODEAPPLICATION_COLUMN_NAME

FND_FLEX_VALUE_SETSPrimary Keys: FLEX_VALUE_SET_ID

FND_DESCR_FLEX_CONTEXTSPrimary Keys: APPLICATION_ID

DESCRIPTIVE_FLEXFIELD_NAMEDESCRIPTIVE_FLEX_CONTEXT_CODE

FND_COMPILED_DESCRIPTIVE_FLEXSPrimary Keys: APPLICATION_ID



DESCRIPTIVE_FLEXFIELD_NAMECOMPILER_VERSION_NUMSEQUENCELANGUAGE

FND_DEFAULT_CONTEXT_FIELDSPrimary Keys: APPLICATION_ID

DESCRIPTIVE_FLEXFIELD_NAMEDEFAULT_CONTEXT_FIELD_NAME

FND_DESCRIPTIVE_FLEXSPrimary Keys: APPLICATION_ID

DESCRIPTIVE_FLEXFIELD_NAME

FND_TABLESPrimary Keys: APPLICATION_ID

TABLE_ID

FND_APPLICATIONPrimary Keys: APPLICATION_ID



Flexfield Values


Flexfield ValuesFND_FVH FND_FVS

FND_IFS

FND_FVNH

FND_FH

FND_FV

FND_FVE

FND_FVRLFND_FVR

FND_RESP FND_FVT

FND_FVRU

FND_TAB

The diagram above shows the Flexfield Value Sets ERD. Because of itssize, we had to compress its presentation. The following listing gives youthe information key for the diagram above.

Abbrev. Table NameFND_FVH FND_FLEX_VALUE_HIERARCHIES

Primary Keys: FLEX_VALUE_SET_IDPARENT_FLEX_VALUECHILD_FLEX_VALUE_LOWCHILD_FLEX_VALUE_HIGH

FND_FVS FND_FLEX_VALUE_SETSPrimary Keys: FLEX_VALUE_SET_ID

FND_IFS FND_ID_FLEX_SEGMENTSPrimary Keys: APPLICATION_ID

ID_FLEX_CODEID_FLEX_NUMAPPLICATION_COLUMN_NAME

FND_FVNH FND_FLEX_VALUE_NORM_HIERARCHY



Primary Keys: FLEX_VALUE_SET_IDPARENT_FLEX_VALUERANGE_ATTRIBUTECHILD_FLEX_VALUE_LOWCHILD_FLEX_VALUE_HIGH

FND_FH FND_FLEX_HIERARCHIESPrimary Keys: FLEX_VALUE_SET_ID

HIERARCHY_ID

FND_FV FND_FLEX_VALUESPrimary Keys: FLEX_VALUE_ID

FND_FVE FND_FLEX_VALIDATION_EVENTSPrimary Keys: FLEX_VALUE_SET_ID

EVENT_CODE

FND_FVRL FND_FLEX_VALUE_RULE_LINESPrimary Keys: FLEX_VALUE_RULE_ID

INCLUDE_EXCLUDE_INDICATORFLEX_VALUE_LOWFLEX_VALUE_HIGH

FND_FVR FND_FLEX_VALUE_RULESPrimary Keys: FLEX_VALUE_RULE_ID

FND_FVRU FND_FLEX_VALUE_RULE_USAGESPrimary Keys: APPLICATION_ID

RESPONSIBILITY_IDFLEX_VALUE_RULE_ID

FND_RESP FND_RESPONSIBILITYPrimary Keys: APPLICATION_ID

RESPONSIBILITY_ID

FND_TAB FND_TABLESPrimary Keys: APPLICATION_ID

TABLE_ID



FND_FVT FND_FLEX_VALIDATION_TABLESPrimary Keys: FLEX_VALUE_SET_ID



Concurrent Managers


Concurrent ManagersFND_CCR

FND_APP

FND_CPS FND_CTPFND_CQS

FND_DG

FND_CPP

FND_CQ

FND_NDS FND_CPR FND_CQP

FND_CR

FND_CQC

FND_USER

FND_CCL

FND_OIDFND_CRCFND_CPG

The diagram above shows the Concurrent Managers ERD. Because of itssize, we had to compress its presentation. The following listing gives youthe information key for the diagram above.

Abbrev. Table NameFND_CCR FND_CONCURRENT_COMPLEX_RULES

Primary Keys: APPLICATION_IDCOMPLEX_RULE_ID

FND_CCL FND_CONCURRENT_COMPLEX_LINESPrimary Keys: APPLICATION_ID

COMPLEX_RULE_IDCOMPLEX_RULE_LINE_ID

FND_CPG FND_CONCURRENT_PROGRAMSPrimary Keys: APPLICATION_ID

CONCURRENT_PROGRAM_ID

FND_CRC FND_CONCURRENT_REQUEST_CLASSPrimary Keys: APPLICATION_ID

REQUEST_CLASS_ID



FND_OID FND_ORACLE_USERIDPrimary Keys: ORACLE_ID

FND_USER FND_USERPrimary Keys: USER_ID

FND_CQC FND_CONCURRENT_QUEUE_CONTENTPrimary Keys: QUEUE_APPLICATION_ID

CONCURRENT_QUEUE_IDTYPE_CODETYPE_APPLICATION_IDTYPE_ID

FND_CR FND_CONCURRENT_REQUESTSPrimary Keys: REQUEST_ID

FND_NDS FND_NODESPrimary Keys: NODE_NAME

FND_CPR FND_CONCURRENT_PROCESSESPrimary Keys: CONCURRENT_PROCESS_ID

FND_DG FND_DATA_GROUPSPrimary Keys: DATA_GROUP_ID

FND_CQP FND_CONCURRENT_QUEUE_PARAMSPrimary Keys: QUEUE_APPLICATION_ID

CONCURRENT_QUEUE_IDNAME

FND_CQ FND_CONCURRENT_QUEUESPrimary Keys: APPLICATION_ID

CONCURRENT_QUEUE_ID

FND_CPP FND_CONC_PROCESSOR_PROGRAMSPrimary Keys: PROCESSOR_APPLICATION_ID

CONCURRENT_PROCESSOR_IDPROGRAM_APPLICATION_ID




FND_CPS FND_CONCURRENT_PROCESSORSPrimary Keys: APPLICATION_ID

CONCURRENT_PROCESSOR_ID

FND_CQS FND_CONCURRENT_QUEUE_SIZEPrimary Keys: QUEUE_APPLICATION_ID

CONCURRENT_QUEUE_IDPERIOD_APPLICATION_IDCONCURRENT_TIME_PERIOD_ID

FND_CTS FND_CONCURRENT_TIME_PERIODSPrimary Keys: APPLICATION_ID

CONCURRENT_TIME_PERIOD_ID




Concurrent Processing


Concurrent Processing

FND_CR

FND_RRLFND_CRAFND_CPA

FND_CD

FND_CRC

FND_LOG

FND_USR

FND_CPS

FND_RES

FND_DGU

FND_DG FND_OID

FND_CRC

FND_CPG

FND_EXE

The diagram above shows the Concurrent Processing ERD. Because ofits size, we had to compress its presentation. The following listing givesyou the information key for the diagram above.

Abbrev. Table NameFND_CPA FND_CONC_PP_ACTIONS

Primary Keys: CONCURRENT_REQUEST_ID

FND_CRA FND_CONC_REQUEST_ARGUMENTSPrimary Keys: REQUEST_ID

FND_RRL FND_RUN_REQ_LANGUAGESPrimary Keys: PARENT_REQUEST_ID

NLS_LANGUAGE

FND_CR FND_CONCURRENT_REQUESTSPrimary Keys: REQUEST_ID

FND_CD FND_CONFLICT_DOMAINSPrimary Keys: CD_ID



FND_RES FND_RESPONSIBILITYPrimary Keys: APPLICATION_ID

RESPONSIBILITY_ID

FND_CRC FND_CONC_RELEASE_CLASSESPrimary Keys: APPLICATION_ID

RELEASE_CLASS_ID

FND_DGU FND_DATA_GROUP_UNITSPrimary Keys: APPLICATION_ID

DATA_GROUP_ID

FND_LOG FND_LOGINSPrimary Keys: LOGIN_ID



FND_USR FND_USERPrimary Keys: USER_ID

FND_CRC FND_CONCURRENT_REQUEST_CLASSPrimary Keys: APPLICATION_ID

REQUEST_CLASS_ID

FND_CPS FND_CONCURRENT_PROGRAM_SERIALPrimary Keys: RUNNING_APPLICATION_ID

RUNNING_CONCURRENT_PROGRAM_IDTO_RUN_APPLICATION_IDTO_RUN_CONCURRENT_PROGRAM_ID



FND_EXE FND_EXECUTABLES



Primary Keys: APPLICATION_IDEXECUTABLE_ID



Concurrent Manager Advanced Schedules


Concurrent Manager AdvancedSchedules

FND_CONC_RELEASE_CLASSES

FND_CONC_REL_CONJ_MEMBERS FND_CONC_RELEASE_DISJS

FND_CONC_REL_DISJ_MEMBERS

FND_CONC_RELEASE_STATES FND_CONC_RELEASE_PERIODS

FND_CONC_STATE_LOOKUPS FND_CONC_STATE_LOOKUP_TYPES

The diagram above shows the Concurrent Manager Advanced SchedulingERD. Because of its size, we had to compress its presentation. Thefollowing listing gives you the information key for the diagram above.

Table NameFND_CONC_RELEASE_CLASSESPrimary Keys: APPLICATION_ID

RELEASE_CLASS_ID

FND_CONC_REL_CONJ_MEMBERSPrimary Keys: CLASS_APPLICATION_ID

RELEASE_CLASS_IDDISJUNCTION_APPLICATION_IDDISJUNCTION_ID

FND_CONC_RELEASE_DISJSPrimary Keys: APPLICATION_ID

DISJUNCTION_ID

FND_CONC_REL_DISJ_MEMBERSPrimary Keys: DISJUNCTION_APPLICATION_ID



DISJUNCTION_IDPERIOD_OR_STATE_FLAGNEGATION_FLAGSTATE_APPLICATION_IDSTATE_IDPERIOD_APPLICATION_IDPERIOD_ID

FND_CONC_RELEASE_STATESPrimary Keys: APPLICATION_ID

CONCURRENT_STATE_ID

FND_CONC_RELEASE_PERIODSPrimary Keys: APPLICATION_ID

CONCURRENT_PERIOD_ID

FND_CONC_STATE_LOOKUPSPrimary Keys: LOOKUP_TYPE_ID

LOOKUP_VALUE

FND_CONC_STATE_LOOKUP_TYPESPrimary Keys: LOOKUP_TYPE_ID



Standard Request Submission


Standard Request SubmissionFND_RGU

FND_APP

FND_RS

FND_RRAFND_RSS FND_RG

FND_RSP FND_RSA

FND_RR FND_DF

FND_CPG FND_RES

The diagram above shows the Standard Request Submission ERD.Because of its size, we had to compress its presentation. The followinglisting gives you the information key for the diagram above.

Abbrev. Table NameFND_RGU FND_REQUEST_GROUP_UNITS

Primary Keys: APPLICATION_IDREQUEST_GROUP_IDREQUEST_UNIT_TYPEUNIT_APPLICATION_IDREQUEST_UNIT_ID

FND_RS FND_REQUEST_SETSPrimary Keys: APPLICATION_ID

REQUEST_SET_ID

FND_RSS FND_REQUEST_SET_STAGESPrimary Keys: SET_APPLICATION_ID

REQUEST_SET_IDREQUEST_SET_STAGE_ID



FND_RRA FND_RUN_REQ_PP_ACTIONSPrimary Keys: PARENT_REQUEST_ID

REQUEST_SET_PROGRAM_IDSET_APPLICATION_IDREQUEST_SET_IDSEQUENCE

FND_RG FND_REQUEST_GROUPSPrimary Keys: APPLICATION_ID

REQUEST_GROUP_ID

FND_RSP FND_REQUEST_SET_PROGRAMSPrimary Keys: SET_APPLICATION_ID

REQUEST_SET_IDREQUEST_SET_PROGRAM_ID

FND_RSA FND_REQUEST_SET_PROGRAM_ARGSPrimary Keys: APPLICATION_ID

REQUEST_SET_IDREQUEST_SET_PROGRAM_IDDESCRIPTIVE_FLEX_APPL_IDDESCRIPTIVE_FLEXFIELD_NAMEAPPLICATION_COLUMN_NAME

FND_RR FND_RUN_REQUESTSPrimary Keys: PARENT_REQUEST_ID

REQUEST_SET_PROGRAM_IDSET_APPLICATION_IDREQUEST_SET_ID

FND_DF FND_DESCRIPTIVE_FLEXSPrimary Keys: APPLICATION_ID

DESCRIPTIVE_FLEXFIELD_NAME



FND_RES FND_RESPONSIBILITY



Primary Keys: APPLICATION_IDRESPONSIBILITY_ID




Workflow


WorkflowWF_AA

WF_ACT

WF_AAV

WF_PA WF_AT

WF_IAS

WF_ITY WF_ITM

WF_IA WF_IAV

WF_MA WF_NA

WF_MSG WF_NOT

WF_RR WF_RRA

The diagram above shows the Workflow ERD. Because of its size, wehad to compress its presentation. The following listing gives you theinformation key for the diagram above.

Abbrev. Table NameWF_AA WF_ACTIVITY_ATTRIBUTES

Primary Keys: ACTIVITY_ITEM_TYPEACTIVITY_NAMEACTIVITY_VERSIONNAME

WF_AAV WF_ACTIVITY_ATTR_VALUESPrimary Keys: PROCESS_ACTIVITY_ID

NAME

WF_ACT WF_ACTIVITIESPrimary Keys: ITEM_TYPE

NAMEVERSION

WF_PA WF_PROCESS_ACTIVITIES



Primary Keys: INSTANCE_ID

WF_AT WF_ACTIVITY_TRANSISTIONSPrimary Keys: FROM_PROCESS_ACTIVITY

RESULT_CODETO_PROCESS_ACTIVITY

WF_IAS WF_ITEM_ACTIVITY_STATUSESPrimary Keys: ITEM_TYPE

ITEM_KEYPROCESS_ACTIVITY

WF_ITY WF_ITEM_TYPESPrimary Keys: NAME

WF_ITM WF_ITEMSPrimary Keys: ITEM_TYPE

ITEM_KEY

WF_IA WF_ITEM_ATTRIBUTESPrimary Keys: ITEM_TYPE

NAME

WF_IAV WF_ITEM_ATTRIBUTE_VALUESPrimary Keys: ITEM_TYPE

ITEM_KEYNAME

WF_MA WF_MESSAGE_ATTRIBUTESPrimary Keys: MESSAGE_TYPE

MESSAGE_NAMENAME

WF_NA WF_NOTIFICATION_ATTRIBUTESPrimary Keys: NOTIFICATION_ID

NAME

WF_MSG WF_MESSAGESPrimary Keys: TYPE



NAME

WF_NOT WF_NOTIFICATIONSPrimary Keys: NOTIFICATION_ID

WF_RR WF_ROUTING_RULESPrimary Keys: RULE_ID

WF_RRA WF_ROUTING_RULE_ATTRIBUTESPrimary Keys: RULE_ID

NAMETYPE



Function Security


Function Security

FND_MENU_ENTRIES FND_ENABLED_PLSQL

FND_MENUS

FND_APPLICATION

FND_FORM_FUNCTIONS FND_RESP_FUNCTIONS

FND_FORM FND_RESPONSIBILITY

The diagram above shows the Function Security ERD. Because of itssize, we had to compress its presentation. The following listing gives youthe information key for the diagram above.

Table NameFND_MENU_ENTRIESPrimary Keys: MENU_ID

ENTRY_SEQUENCE

FND_ENABLED_PLSQLPrimary Keys: PLSQL_TYPE

PLSQL_NAME

FND_MENUSPrimary Keys: MENU_ID

FND_FORM_FUNCTIONSPrimary Keys: FUNCTION_ID

FND_RESP_FUNCTIONSPrimary Keys: APPLICATION_ID



RESPONSIBILITY_IDACTION_IDRULE_TYPE

FND_FORMPrimary Keys: APPLICATION_ID

FORM_ID

FND_RESPONSIBILITYPrimary Keys: APPLICATION_ID

RESPONSIBILITY_ID




Login Security


Login Security

FND_URG FND_RES

FND_SG FND_APP

FND_ASFND_DGU

FND_OID FND_DG

FND_LSF FND_LR

FND_SESS

FND_LOG FND_UL

FND_USER

The diagram above shows the Login Security ERD. Because of its size,we had to compress its presentation. The following listing gives you theinformation key for the diagram above.

Abbrev. Table NameFND_URG FND_USER_RESP_GROUPS

Primary Keys: USER_IDRESPONSIBILITY_IDRESPONSIBILITY_APPLICATION_IDSECURITY_GROUP_ID

FND_RES FND_RESPONSIBILITYPrimary Keys: APPLICATION_ID

RESPONSIBILITY_ID

FND_SG FND_SECURITY_GROUPSPrimary Keys: SECURITY_GROUP_ID




FND_DGU FND_DATA_GROUP_UNITSPrimary Keys: APPLICATION_ID

DATA_GROUP_ID

FND_AS FND_APPLICATION_SERVERSPrimary Keys: SERVER_ID



FND_SESS FND_SESSIONSPrimary Keys: SESSION_ID

FND_LRF FND_LOGIN_RESP_FORMSPrimary Keys: LOGIN_ID

LOGIN_RESP_IDFORM_APPL_IDFORM_IDSTART_TIME

FND_LR FND_LOGIN_RESPONSIBILITIESPrimary Keys: LOGIN_ID

LOGIN_RESP_ID

FND_LOG FND_LOGINSPrimary Keys: LOGIN_ID

FND_UL FND_UNSUCCESSFUL_LOGINSPrimary Keys: USER_ID

ATTEMPT_TIMELOGIN_NAMETERMINAL_ID

FND_USER FND_USERPrimary Keys: USER_ID



AuditTrail


AuditTrail

FND_ORACLE_USERID FND_AUDIT_SCHEMA

FND_COLUMNS FND_AUDIT_COLUMNS

FND_TABLES FND_AUDIT_TABLES

FND_AUDIT_GROUPS

The diagram above shows the AuditTrail ERD. Because of its size, wehad to compress its presentation. The following listing gives you theinformation key for the diagram above.

Table NameFND_ORACLE_USERIDPrimary Keys: ORACLE_ID

FND_AUDIT_SCHEMAPrimary Keys: SCHEMA_ID

FND_COLUMNSPrimary Keys: APPLICATION_ID

TABLE_IDCOLUMN_ID

FND_AUDIT_COLUMNSPrimary Keys: TABLE_APP_ID

TABLE_IDCOLUMN_IDSCHEMA_ID




TABLE_ID

FND_AUDIT_TABLESPrimary Keys: AUDIT_GROUP_ID

AUDIT_GROUP_APP_IDTABLE_APP_IDTABLE_ID

FND_AUDIT_GROUPSPrimary Keys: APPLICATION_ID

AUDIT_GROUP_ID



User Profiles


User Profiles

FND_PROFILE_OPTIONS

FND_RESPONSIBILITY

FND_USER

FND_USER_RESP_GROUPS

FND_PROFILE_OPTION_VALUES

FND_APPLICATION

The diagram above shows the User Profiles ERD. Because of its size, wehad to compress its presentation. The following listing gives you theinformation key for the diagram above.

Table NameFND_PROFILE_OPTION_VALUESPrimary Keys: APPLICATION_ID

PROFILE_OPTION_IDLEVEL_IDLEVEL_VALUELEVEL_VALUE_APPLICATION_ID

FND_USER_RESP_GROUPSPrimary Keys: USER_ID

RESPONSIBILITY_IDRESPONSIBILITY_APPLICATION_IDSECURITY_GROUP_ID

FND_PROFILE_OPTIONSPrimary Keys: APPLICATION_ID

PROFILE_OPTION_ID



FND_USERPrimary Keys: USER_ID

FND_RESPONSIBILITYPrimary Keys: APPLICATION_ID

RESPONSIBILITY_ID




Document Sequences, Folders, Documents on theNavigator


Document Sequences, Folders,Documents on the Navigator

FND_DOC_SEQUENCE_ASSIGNMENTS FND_DOC_SEQ_CATEGORIES

FND_DOC_SEQ_AUDIT

FND_DOC_SEQ_USERS FND_DOCUMENT_SEQUENCES

FND_DEFAULT_FOLDERS

FND_FOLDERS

FND_FOLDER_COLUMNS

FND_USER_DESKTOP_OBJS

FND_DESKTOP_OBJECTS

The diagram above shows the Document Sequences, Folders, andDocuments on the Navigator ERDs. Because of their size, we had tocompress the presentation. The following listing gives you the informationkey for the diagrams above.

Table NameFND_DOC_SEQUENCE_ASSIGNMENTSPrimary Keys: DOC_SEQUENCE_ASSIGNMENT_ID

FND_DOC_SEQUENCE_CATEGORIESPrimary Keys: APPLICATION_ID

CODE

FND_DOC_SEQUENCE_AUDITPrimary Keys: DOC_SEQUENCE_ID

DOC_SEQUENCE_VALUE

FND_DOC_SEQUENCE_USERSPrimary Keys: DOC_SEQUENCE_ID

DOC_SEQUENCE_ASSIGNMENT_ID



USER_ID

FND_DOCUMENT_SEQUENCESPrimary Keys: DOC_SEQUENCE_ID

FND_DEFAULT_FOLDERSPrimary Keys: FOLDER_ID

FND_FOLDER_COLUMNSPrimary Keys: FOLDER_ID

SEQUENCE

FND_FOLDERSPrimary Keys: FOLDER_ID

FND_USER_DESKTOP_OBJECTSPrimary Keys: DESKTOP_OBJECT_ID

FND_DESKTOP_OBJECTSPrimary Keys: DESKTOP_OBJECT_ID



Attachments


Attachments

FND_AD

FND_DOC

FND_DC

FND_DCU

FND_AF

FND_DOCT FND_DST

FND_DLT

FND_DLR

FND_DD

FND_AB FND_ABE

FND_DE

The diagram above shows the Attachments ERD. Because of its size, wehad to compress its presentation. The following listing gives you theinformation key for the diagram above.

Abbrev. Table NameFND_AD FND_ATTACHED_DOCUMENTS

Primary Keys: ATTACHED_DOCUMENT_ID

FND_DOCT FND_DOCUMENTS_TLPrimary Keys: DOCUMENT_ID

LANGUAGE

FND_DST FND_DOCUMENTS_SHORT_TEXTPrimary Keys: MEDIA_ID

FND_DOC FND_DOCUMENTSPrimary Keys: DOCUMENT_ID

FND_DLT FND_DOCUMENTS_LONG_TEXTPrimary Keys: MEDIA_ID



FND_DLR FND_DOCUMENTS_LONG_RAWPrimary Keys: MEDIA_ID

FND_DC FND_DOCUMENT_CATEGORIESPrimary Keys: CATEGORY_ID

FND_DD FND_DOCUMENT_DATATYPESPrimary Keys: DATATYPE_ID

LANGUAGE

FND_DCU FND_DOC_CATEGORY_USAGESPrimary Keys: DOC_CATEGORY_USAGE_ID

FND_DE FND_DOCUMENT_ENTITIESPrimary Keys: DOC_ENTITY_ID

FND_AF FND_ATTACHMENT_FUNCTIONSPrimary Keys: ATTACHMENT_FUNCTION_ID

FND_AB FND_ATTACHMENT_BLOCKSPrimary Keys: ATTACHMENT_BLK_ID

FND_ABE FND_ATTACHMENT_BLK_ENTITIESPrimary Keys: ATTACHMENT_BLK_ENTITY_ID



Document Management and Help


Document Management and Help

FND_LOBACC FND_LOBS FND_HDOC

FND_HTARFND_HTREE

FND_DNODES FND_DPRODS FND_DFUNC

FND_DPFS

FND_DFP

FND_DPPS

The diagram above shows the Document Management and Help ERDs.Because of their size, we had to compress the presentation. The followinglisting gives you the information key for the diagrams above.

Abbrev. Table NameFND_DNODES FND_DM_NODES

Primary Keys: NODE_ID

FND_DPRODS FND_DM_PRODUCTSPrimary Keys: PRODUCT_ID

FND_DFUNC FND_DM_FUNCTIONSPrimary Keys: FUNCTION_ID

FND_DPFS FND_DM_PRODUCT_FUNCTION_SYNTAXPrimary Keys: PRODUCT_FUNCTION_ID

FND_DFP FND_DM_FUNCTION_PARAMETERSPrimary Keys: PARAMETER_ID

FND_DPPS FND_DM_PRODUCT_PARAM_SYNTAX



Primary Keys: PRODUCT_PARAMETER_ID

FND_LOBACC FND_LOB_ACCESSPrimary Keys: ACCESS_ID

FND_LOBS FND_LOBSPrimary Keys: FILE_ID

FND_HDOC FND_HELP_DOCUMENTSPrimary Keys: FILE_ID

FND_HTREE FND_HELP_TREEPrimary Keys: FILE_ID

FND_HTAR FND_HELP_TARGETSPrimary Keys: FILE_ID

TARGET_NAME



AOL Data Dictionary Information


AOL Data Dictionary InformationFND_APPLICATION

FND_TABLESFND_VCOLS FND_VIEWS FND_SEQS

FND_PKCOLS FND_PKEYS

FND_FKCOLS FND_FKEYS

FND_INCOLS FND_INDEXES

FND_COLUMNS

The diagram above shows the AOL Data Dictionary ERD. Because of itssize, we had to compress its presentation. The following listing gives youthe information key for the diagram above.

Table NameFND_APPLICATIONPrimary Keys: APPLICATION_ID

FND_VIEW_COLUMNSPrimary Keys: APPLICATION_ID

VIEW_IDCOLUMN_SEQUENCE

FND_VIEWSPrimary Keys: APPLICATION_ID

VIEW_ID

FND_SEQUENCESPrimary Keys: APPLICATION_ID

SEQUENCE_ID




TABLE_ID

FND_PRIMARY_KEY_COLUMNSPrimary Keys: APPLICATION_ID

TABLE_IDPRIMARY_KEY_IDPRIMARY_KEY_SEQUENCE

FND_PRIMARY_KEYSPrimary Keys: APPLICATION_ID

TABLE_IDPRIMARY_KEY_ID

FND_FOREIGN_KEY_COLUMNSPrimary Keys: APPLICATION_ID

TABLE_IDFOREIGN_KEY_IDFOREIGN_KEY_SEQUENCE

FND_FOREIGN_KEYSPrimary Keys: APPLICATION_ID

TABLE_IDFOREIGN_KEY_ID

FND_INDEX_COLUMNSPrimary Keys: APPLICATION_ID

TABLE_IDINDEX_IDCOLUMN_SEQUENCE

FND_INDEXESPrimary Keys: APPLICATION_ID

TABLE_IDINDEX_ID

FND_COLUMNSPrimary Keys: APPLICATION_ID



TABLE_IDCOLUMN_ID



Currency and Language


Currency and Language

FND_LOOKUP_VALUES FND_LANGUAGES

FND_LOOKUP_TYPES FND_NEW_MESSAGES

FND_APPLICATION

The diagram above shows the Currency and Language ERD. Because ofits size, we had to compress its presentation. The following listing givesyou the information key for the diagram above.

Table NameFND_LOOKUP_VALUESPrimary Keys: LOOKUP_TYPE

LANGUAGELOOKUP_CODESECURITY_GROUP_IDVIEW_APPLICATION_ID

FND_LANGUAGESPrimary Keys: LANGUAGE_CODE

FND_LOOKUP_TYPESPrimary Keys: LOOKUP_TYPE

SECURITY_GROUP_IDVIEW_APPLICATION_ID

FND_NEW_MESSAGES



Primary Keys: APPLICATION_IDLANGUAGE_CODEMESSAGE_NAME




Summary


Summary

In this lesson, you should have learned how to:• Read and understand Entity Relationship

Diagrams (ERDs).• Read and understand Oracle Applications'

Applications Technology ERDs.


Development TopicsChapter 4 - Page 1

Development TopicsChapter 4



Development Topics


Development Topics




Objectives


Objectives


• Describe the interface options available withinOracle Applications

• Describe solid standards for using theseinterfaces



Interface Options


Interface Options

• What is an interface?• Interface Tables• Application Programming Interfaces (APIs)• Other methods

We are going to use the following definition for interfaces. An interface willallow you to:

import data from a variety of environments, including yourown system, previous systems, data collection devices,external systems, and others in the easiest way possible.

review the results of import runs, including validation,review, update, re-imports, and error identification.

export data from Oracle Applications products for use inother systems.

Given these broad characteristics, let's explore the methods by which wecan bring data in an Oracle Applications instance while adhering to ourdefinition.

1. INTERFACE TABLES

Throughout Oracle Applications' products, Oracle developers havedeveloped Interface Tables and programs. The Interface Tables allow you



to load your data, and then to run an Application concurrent program.That concurrent program will take the data from the Interface Table,validate it, and import it into your Applications' instance.

This sort of interface satisfies all of our requirements. It is relatively easy,just get your data into the Interface Table. Two, it checks the data beforeimporting it. And three, in many cases, these same tables are used toexport data, where appropriate.

There are numerous Interface Tables in the Oracle Applications products.In fact, they are too numerous to mention here. Refer to the appropriateproduct course for detailed information on these Interface Tables and theirusage.

2. APPLICATIONS PROGRAMMING INTERFACES (APIs)

Sometimes you want or need tighter integration to Oracle Applicationsthan can be provided with Interface Tables. In those cases, OracleApplications provides APIs.

APIs allow for tight integration into the Oracle Applications product. Thereare also 3rd-party products that integrate into Oracle Applications andextend its integration capabilities.

While more complex than Interface Tables, APIs do provide a pre-definedmethod to integrate into Oracle Applications.

3. OTHER METHODS

This seems like a catch all category, and it is. Oracle Applications alsoprovides other methods for data import and export. The most common ofthese is through spreadsheets.

Several Oracle Applications products allow for data upload and downloadvia spreadsheets. The spreadsheet formats are pre-defined. But, themechanics of the upload or download are quite simple.

Any else? Oracle Applications also support data uploads and downloadsto Oracle Discoverer and word processing files. While I think that coversthe bases, Oracle Applications is a growing product that adapts to newand evolving standards. So, who knows. By the time you read this, theremay be new standards that have been released, or are just about to maketheir appearance.



Interface Table Diagram


Interface Table Diagram

Data Source

InterfaceTable

DestinationProduct

ErrorsTable

ValidateMaintain

Loader

ConcurrentProgram

Here is a basic example of the Interface Table methodology.

The first thing to note is the Loader (in some cases also called, Feeders).The Loader is responsible for uploading and downloading data from theInterface Table. It should also be noted that some Interface Tables areInbound-only, some are Outbound-only, and some are both.

There are no restrictions on your Loader. As long as it can ultimatelycommunicate with the Interface Table in your Oracle Applications'instance, you can use it as a loader. This is also the basic mechanismthat is used for transferring data with spreadsheets, word processing files,and others.

Once the data is into the Interface Table, it must be validated. Validationis generally handled through a concurrent program. In some cases thisconcurrent program is part of the import process. In others, it is aseparate validation program.

In either case, invalid data is separated and noted. This can be donethrough the generation of a report. It can also be done by moving theinvalid records into an Error Table.



Once validation is complete, there may need to be maintenance on thedata to correct errors or inconsistencies. This is typically done by a formbuilt by the product development team for this purpose.

With the data ready to go, the concurrent program takes the data from theInterface Table and loads it into the Application. As noted previously,validation may be occurring at this point or separately.

IMPORTANT NOTE:It is critical to note how the data is imported. At NO TIME are you writingdata into or from the product tables. The only tables you write or read arethe Interface Tables.



API Diagram


API Diagram

Data Source

BusinessObject API

DestinationProduct

Call

PerformBusinessFunction

ReturnError

ReturnResult

Here is a basic example of the API methodology.

It should be noted that this method is distinctly different from the InterfaceTable methodology. First off, the data is not staged. The data is sentdirectly through the API. This has an implication. API methods are forsingle-record data importing. Interface Tables are for mass dataimporting. Of course, you could do mass imports with API, but it will beslower, and performance is always a concern.

Another implication is that the API communicates directly with the DataSource, letting it know if the import was successful. This implies that theData Source must be more than a data source. It must be able to handleunsuccessful attempts to move data into the product.

Using an API also implies a bigger responsibility of programs and codeoutside of Oracle Applications. The Data Source must handle errors, musthandle data maintenance, and all the other jobs that our interfaces mustdo.

IMPORTANT NOTE:It is critical to note how the data is imported. At NO TIME are you writingdata into or from the product tables. Only the API writes or reads from the



product tables. The API is responsible for communicating with your datasource.



Development Standards



• Document• Follow the documentation• Adhere to the rules• Check your data

DOCUMENT:

One of the most overlooked part of any interface project is documentation.Why? Mostly because it is the unglamorous part of the process. But, it isabsolutely critical to your success.

Oracle Applications is a mission critical application. You are maintainingthe data that runs your company on it. Having a system that is notdocumented is a glaring hole in your long-term viability. All thisvulnerability, and it turns out to be simple to collect the basics.

1. Document the source of your data. Where is it coming from,and most importantly, how do you reproduce that source (if itis not self-maintaining).

2. Document the method by which you move data from thesource to the Interface Table or to which API. Are you usingSQL*Loader, spreadsheets, C programs?

3. Document the data format. A simple description by column ofthe data your are moving.

FOLLOW THE DOCUMENTATION:



It is quite amazing when you consider that the interfaces, both InterfaceTables and APIs, are documented in their product manuals. Use thesesources. If you do not have the manual on the interface you are trying touse, you are missing the center of the puzzle.

ADHERE TO THE RULES:

Read the descriptions of the Interface Tables and APIs. Follow what thedocumentation says. Don't assume that you can short-cut the process,even though your short-cut "seems" to do the same. Oracle Applicationsis a complex, inter-related product. Those assumptions are not safe.

It is critical to note how the data is imported. At NO TIME are you writingdata into or from the product tables. Only the API writes or reads from theproduct tables or the concurrent programs that service the Interface Table.Do not wite or read directly!

CHECK YOUR DATA:

The single biggest cause of problems with Interface Tables and APIs ismisformatted data. You are either NOT putting the right data into the rightcolumns of the Interface Table. Or, you are not passing the properarguments in the proper format to the API. In over 90% of the problemswith the interfaces, the net result is data. Check it!



Summary


Summary

In this lesson, you should have learned how to:• Describe the interface options available within

Oracle Applications.• Describe solid standards for using these

interfaces.


Exploring Applications DatabaseChapter 5 - Page 1

Exploring ApplicationsDatabaseChapter 5



Exploring Applications Database


Exploring Applications Database

ILT Schedule: Timing Topic60 minutes Demonstration60 minutes Total



Objectives


Objectives


• Use SQL scripts to explore Oracle Applicationsdatabase objects

In the chapters on the "Applications Architecture" and "ERDs andApplications Technology", there is an assumption that the student knowshow to use SQL*Plus to explore and confirm the statements made.

This lesson is in place to help those students who need some assistancewith those skills. It will also help those students who don't need help,because it will add a trick or two that they might not have seen.



Exploration Basics


Exploration Basics

• Logging in to SQL*Plus• Running SQL scripts• Listing scripts• Description scripts• Configuration scripts

LOGGING IN TO SQL*PLUS:

Logging in to SQL*Plus is dependent upon where you are trying to do thelogin. Basically, you can login to SQL*Plus from the machine where thedatabase is running or from another machine. Getting all the details ofthis set-up is well beyond the scope of this class. You need SQL*Netguides to configure your settings if you need help with this.

What this section does cover is the usernames and passwords that aredefaults on your database. (NOTE: These are only the defaults.Usernames and passwords can be changed. In fact, Oracle recommendsthat these passwords be changed.)

Default Username Default Password======================= ===========================APPS APPSAPPLSYSPUB PUBAPPLSYS APPS<PROD> <PROD> (examples follows)GL GLAR ARSYSTEM MANAGER



SYS CHANGE_ON_INSTALL

The most important username/password to the student is that for theAPPS schema. This is the username/password that will be used forrunning our exploration scripts.

RUNNING SQL SCRIPTS:

To run a SQL script, you can do 1 of 2 things. From the command line,put at @ followed by the script name at the end of the command. Forexample:

sqlplus apps/apps @script1.sql

The other method is to invoke the script inside of SQL*Plus by typing @followed by the script name. For example:

$ sqlplus apps/apps

SQL*Plus: Release 8.1.6.0.0 - Production on Wed Jan 24 08:30:19

(c) Copyright 1999 Oracle Corporation. All rights reserved.

Connected to:Oracle8i Enterprise Edition Release 8.1.6.1.0 - ProductionWith the Partitioning optionJServer Release 8.1.6.1.0 - Production

SQL> @script1.sql

TYPES OF SCRIPTS:

There are 3 major categories that clearly delineate the scripts we will useto explore the database, listing scripts, description scripts, andconfiguration scripts.

Listing scripts help us determine the name of something specific. Listingscripts will be used to show us that something exists, or a list of all thethings of a given type that exist. Description scripts are used to give usdetails about any given object. Configuration scripts are used to give usinformation about how our database and its environment are setup.



Listing Scripts


Listing Scripts

• Count Database Objects by Type• List Product Dependencies• List Pinned Objects• List Objects

What follows are several scripts that will list the various objects in yourdatabase. These scripts are:

1. Count Database Objects by Type2. List Product Dependencies3. List Pinned Objects4. Various List Object Scripts, including List Database Links,

Functions, Indexes, Java Classes, Java Resources,Java Source, LOBs, Packages, Package Bodies,Procedures, Sequences, Synonyms, Tables, Triggers,Types, and Views.

The scripts are reproduced here for your use. We give them defaultnames, but you are welcome to rename them when you use them on yourdatabase.

SCRIPT = Count Objects by TypeNAME = CNTOBJS.sqlDESCRIPT= This script will count the various database objects

by type that are present in the Applicationsdatabase where the script is run.



REM ***** COUNT OBJECTS BY TYPE

CLEAR COMPUTES

CLEAR BREAKS

REPHEADER LEFT 'COUNT OBJECTS BY TYPE' SKIP 2

COL DateInf FORMAT A19 HEADING 'Runtime Information'

COL Object_Type FORMAT A18 HEADING 'Object Type'

COL Status FORMAT A7 HEADING 'Status'

COL Objcnt FORMAT 9999999999 HEADING 'Count'

SET PAGESIZE 1000

SET LINESIZE 80

SET NEWPAGE 0

SET VERIFY OFF

ACCEPT Owner_List PROMPT 'Input Schema to Count or %for All: '

SELECT to_char(sysdate,'DD-MM-YYYY HH24:MI:SS')

DateInf FROM sys.dual;

REPHEADER OFF

BREAK ON REPORT

COMPUTE SUM OF Objcnt ON REPORT

SELECT object_type, status, count(*) objcnt

FROM DBA_OBJECTS

WHERE Owner like '&&Owner_List'

GROUP BY object_type, status;

SCRIPT = List Product DependenciesNAME = LISTPRODDEP.sqlDESCRIPT= Many Applications products depend upon

functionality from other Applications products.These relationships are called Dependencies.This script will list, by product, the additional



products that are needed for the originalproduct to run.

REM ***** LIST PRODUCT DEPENDENCIES

CLEAR COMPUTES

CLEAR BREAKS

REPHEADER LEFT 'LIST PRODUCT DEPENDENCIES' SKIP 2


COL Application FORMAT A38 HEADING 'Application'

COL Requires FORMAT A38 HEADING 'Requires theApplication'

SET PAGESIZE 66

SET LINESIZE 80

SET NEWPAGE 0



REPHEADER OFF

BREAK ON APPLICATION SKIP 2

SELECT a3.application_name Application,

a4.application_name Requires

FROM fnd_application a1, fnd_application a2,

fnd_application_tl a3, fnd_application_tl a4,

fnd_oracle_userid o1, fnd_oracle_userid o2,

fnd_product_dependencies fpd

WHERE

a2.application_id=fpd.required_application_id

AND a1.application_id=fpd.application_id

AND o2.oracle_id=fpd.required_oracle_id

AND o1.oracle_id=fpd.oracle_id

AND a2.application_id=a4.application_id

AND a1.application_id=a3.application_id



ORDER BY 1,2;

SCRIPT = List Pinned ObjectsNAME = LISTPINNED.sqlDESCRIPT= In order to improve performance, Oracle

Applications pins into memory many of itsPL*SQL packages. This has implications forperformance and patching. Performance willimprove with pinned packages. And forpatching, a package must be unpinned, updated,and then re-pinned in order for the patch tobe effective. This script lists the currentlypinned packages.

REM ***** LIST PINNED OBJECTS

CLEAR COMPUTES

CLEAR BREAKS

REPHEADER LEFT 'LIST PINNED OBJECTS' SKIP 2


COL Type FORMAT A12 HEADING 'Type'

COL Object FORMAT A36 HEADING 'Object'

COL Loads FORMAT 99990 HEADING 'Loads'

COL Execs FORMAT 9999990 HEADING 'Execs'

COL Kept FORMAT A4 Heading 'Kept'

COL "TOTAL SPACE (K)" FORMAT A20

SET PAGESIZE 66

SET LINESIZE 80

SET NEWPAGE 0



REPHEADER OFF

SELECT owner || '.' || name OBJECT , type,



to_char(sharable_mem/1024,'9,999.9')

"SPACE(K)", loads, executions execs, kept

FROM v$db_object_cache

WHERE type in ('FUNCTION','PACKAGE',

'PACKAGE BODY','PROCEDURE')

AND owner not in ('SYS')

ORDER BY owner, name;

SELECT to_char(sum(sharable_mem)/1024,'9,999,999.9')

"TOTAL SPACE (K)"

FROM v$db_object_cache

WHERE type in ('FUNCTION','PACKAGE',

'PACKAGE BODY','PROCEDURE')

AND owner not in ('SYS');

SCRIPT = LIST DATABASE LINKSNAME = LISTDBLINKS.sqlDESCRIPT= This script lists all database links.

REM ***** LIST DATABASE LINKS

CLEAR COMPUTES

CLEAR BREAKS

REPHEADER LEFT 'LIST DATABASE LINKS' SKIP 2


COL Owner FORMAT A30 HEADING 'Owner'

COL DB_Link FORMAT A50 HEADING 'Database Link'

SET PAGESIZE 66

SET LINESIZE 85

SET NEWPAGE 0

SET VERIFY OFF

ACCEPT Owner_List PROMPT 'Input Owner or % for All: '

ACCEPT Link_List PROMPT 'Input DB Link or % for All: '





REPHEADER OFF

BREAK ON OWNER SKIP 2

COMPUTE COUNT OF DB_LINK ON OWNER

SELECT Owner, DB_Link FROM DBA_DB_LINKS


AND DB_Link like '&&Link_List'

ORDER BY Owner, DB_Link;

SCRIPT = LIST FUNCTIONSNAME = LISTFUNCS.sqlDESCRIPT= This script will list all functions.

REM ***** LIST FUNCTIONS

CLEAR COMPUTES

CLEAR BREAKS

REPHEADER LEFT 'LIST FUNCTIONS' SKIP 2



COL Object_Name FORMAT A40 HEADING 'Function Name'


SET PAGESIZE 66

SET LINESIZE 80

SET NEWPAGE 0

SET VERIFY OFF


ACCEPT Name_List PROMPT 'Input Function Name or % forAll: '

ACCEPT Status_List PROMPT 'Input Status or % for All:'



REPHEADER OFF




COMPUTE COUNT OF OBJECT_NAME ON OWNER

SELECT Owner, Object_Name, Status

FROM DBA_OBJECTS

WHERE Object_Type='FUNCTION'

AND Owner like '&&Owner_List'

AND Object_Name like '&&Name_List'

AND Status like '&&Status_List'

ORDER BY Owner, Object_Name;

SCRIPT = LIST INDEXESNAME = LISTINDEXES.sqlDESCRIPT= This script lists all indexes.

REM ***** LIST INDEXES

CLEAR COMPUTES

CLEAR BREAKS

REPHEADER LEFT 'LIST INDEXES' SKIP 2



COL Index_Name FORMAT A30 HEADING 'Index Name'

COL Table_Name FORMAT A30 HEADING 'Table Name'

COL Uniqueness FORMAT A10 Heading 'Uniqueness'


SET PAGESIZE 66

SET LINESIZE 132

SET NEWPAGE 0

SET VERIFY OFF


ACCEPT Index_List PROMPT 'Input Index Name or % forAll: '

ACCEPT Table_List PROMPT 'Input Table Name or % forAll: '






REPHEADER OFF


COMPUTE COUNT OF INDEX_NAME ON OWNER

SELECT Owner, Index_Name, Table_Name, Uniqueness,

Status

FROM DBA_INDEXES


AND Index_Name like '&&Index_List'

AND Table_Name like '&&Table_List'


ORDER BY Owner, Index_Name;

SCRIPT = LIST JAVA CLASSESNAME = LISTJCLASSES.sqlDESCRIPT= This script lists all Java Class objects.

REM ***** LIST JAVA CLASSES

CLEAR COMPUTES

CLEAR BREAKS

REPHEADER LEFT 'LIST JAVA CLASSES' SKIP 2



COL Java_Name FORMAT A60 HEADING 'Name'


SET PAGESIZE 66

SET LINESIZE 132

SET NEWPAGE 0

SET VERIFY OFF




ACCEPT Object_List PROMPT 'Input Java Class Name or %for All: '




REPHEADER OFF


COMPUTE COUNT OF STATUS ON OWNER

SELECT Owner, DBMS_JAVA.LONGNAME(Object_Name)

Java_Name, Status

FROM DBA_OBJECTS


AND 2 like '&&Object_List'


AND Object_Type = 'JAVA CLASS'

ORDER BY Owner, 2;

SCRIPT = LIST JAVA RESOURCESNAME = LISTJRES.sqlDESCRIPT= This script lists all Java Resource objects.

REM ***** LIST JAVA RESOURCES

CLEAR COMPUTES

CLEAR BREAKS

REPHEADER LEFT 'LIST JAVA RESOURCES' SKIP 2



COL Java_Name FORMAT A60 HEADING 'Long Name'


SET PAGESIZE 66

SET LINESIZE 132

SET NEWPAGE 0



SET VERIFY OFF


ACCEPT Object_List PROMPT 'Input Java Resource Name or% for All: '




REPHEADER OFF




Java_Name, Status

FROM DBA_OBJECTS




AND Object_Type = 'JAVA RESOURCE'

ORDER BY Owner, 2;

SCRIPT = LIST JAVA SOURCESNAME = LISTJSRC.sqlDESCRIPT= This script lists all Java Source objects.

REM ***** LIST JAVA SOURCES

CLEAR COMPUTES

CLEAR BREAKS

REPHEADER LEFT 'LIST JAVA SOURCES' SKIP 2



COL Java_Name FORMAT A60 HEADING 'Long Name'


SET PAGESIZE 66



SET LINESIZE 132

SET NEWPAGE 0

SET VERIFY OFF


ACCEPT Object_List PROMPT 'Input Java Source Name or %for All: '




REPHEADER OFF




Java_Name, Status

FROM DBA_OBJECTS




AND Object_Type = 'JAVA SOURCE'

ORDER BY Owner, 2;

SCRIPT = LIST LOBsNAME = LISTLOBS.sqlDESCRIPT= This scripts lists all LOB objects.

REM ***** LIST LOBS

CLEAR COMPUTES

CLEAR BREAKS

REPHEADER LEFT 'LIST LOBS' SKIP 2



COL Table_Name FORMAT A30 HEADING 'Table'



COL Column_Name FORMAT A60 HEADING 'LOB Column orAttribute'

SET PAGESIZE 66

SET LINESIZE 132

SET NEWPAGE 0

SET VERIFY OFF


ACCEPT Table_List PROMPT 'Input Table Name or % forAll: '

ACCEPT Col_List PROMPT 'Input Column Name/Attribute or% for All: '



REPHEADER OFF


COMPUTE COUNT OF COLUMN_NAME ON OWNER

SELECT Owner, Table_Name, Column_Name

FROM DBA_LOBS


AND Table_Name like '&&Table_List'

AND Column_Name like '&&Col_List'

ORDER BY Owner, Table_Name, Column_Name;

SCRIPT = LIST PACKAGESNAME = LISTPKGS.sqlDESCRIPT= This script lists all Packages.

REM ***** LIST PACKAGES

CLEAR COMPUTES

CLEAR BREAKS

REPHEADER LEFT 'LIST PACKAGES' SKIP 2





COL Object_Name FORMAT A40 HEADING 'Package Name'


SET PAGESIZE 66

SET LINESIZE 80

SET NEWPAGE 0

SET VERIFY OFF


ACCEPT Name_List PROMPT 'Input PAckage Name or % forAll: '




REPHEADER OFF




FROM DBA_OBJECTS

WHERE Object_Type='PACKAGE'





SCRIPT = LIST PACKAGE BODIESNAME = LISTPKBODS.sqlDESCRIPT= This script lists all Package Bodies.

REM ***** LIST PACKAGE BODIES

CLEAR COMPUTES

CLEAR BREAKS

REPHEADER LEFT 'LIST PACKAGE BODIES' SKIP 2





COL Object_Name FORMAT A40 HEADING 'Package Body Name'


SET PAGESIZE 66

SET LINESIZE 80

SET NEWPAGE 0

SET VERIFY OFF


ACCEPT Name_List PROMPT 'Input Package Body Name or %for All: '




REPHEADER OFF




FROM DBA_OBJECTS

WHERE Object_Type='PACKAGE BODY'





SCRIPT = LIST PROCEDURESNAME = LISTPROCS.sqlDESCRIPT= This script lists all Procedures.

REM ***** LIST PROCEDURES

CLEAR COMPUTES

CLEAR BREAKS

REPHEADER LEFT 'LIST PROCEDURES' SKIP 2





COL Object_Name FORMAT A40 HEADING 'Procedure Name'


SET PAGESIZE 66

SET LINESIZE 80

SET NEWPAGE 0

SET VERIFY OFF


ACCEPT Name_List PROMPT 'Input Procedure Name or % forAll: '




REPHEADER OFF




FROM DBA_OBJECTS

WHERE Object_Type='PROCEDURE'





SCRIPT = LIST SEQUENCESNAME = LISTSEQS.sqlDESCRIPT= This script lists all Sequences.

REM ***** LIST SEQUENCES

CLEAR COMPUTES

CLEAR BREAKS

REPHEADER LEFT 'LIST SEQUENCES' SKIP 2




COL Sequence_Owner FORMAT A30 HEADING 'Owner'

COL Sequence_Name FORMAT A30 HEADING 'Sequence'

COL Min_Value FORMAT 9999999990 HEADING 'Min Value'

COL Max_Value FORMAT 9999999990 HEADING 'Max Value'

COL Increment_By FORMAT 9999999990 HEADING 'Increment'

COL Cycle_Flag FORMAT A5 HEADING 'Cycle'

COL Order_Flag FORMAT A5 HEADING 'Order'

SET PAGESIZE 66

SET LINESIZE 132

SET NEWPAGE 0

SET VERIFY OFF


ACCEPT Name_List PROMPT 'Input Sequence Name or % forAll: '



REPHEADER OFF

BREAK ON SEQUENCE_OWNER SKIP 2

COMPUTE COUNT OF SEQUENCE_NAME ON SEQUENCE_OWNER

SELECT Sequence_Owner, Sequence_Name, Min_Value,Max_Value,

Increment_By, Cycle_Flag, Order_Flag

FROM DBA_SEQUENCES

WHERE Sequence_Owner like '&&Owner_List'

AND Sequence_Name like '&&Name_List'

ORDER BY Sequence_Owner, Sequence_Name;

SCRIPT = LIST SYNONYMSNAME = LISTSYNS.sqlDESCRIPT= This script lists all Synonyms.

REM ***** LIST SYNONYMS

CLEAR COMPUTES



CLEAR BREAKS

REPHEADER LEFT 'LIST SYNONYMS' SKIP 2



COL Synonym_Name FORMAT A30 HEADING 'Synonym'

SET PAGESIZE 66

SET LINESIZE 80

SET NEWPAGE 0

SET VERIFY OFF


ACCEPT Name_List PROMPT 'Input Synonym Name or % forAll: '



REPHEADER OFF


COMPUTE COUNT OF SYNONYM_NAME ON OWNER

SELECT Owner, Synonym_Name

FROM DBA_SYNONYMS


AND Synonym_Name like '&&Name_List'

ORDER BY Owner, Synonym_Name;

SCRIPT = LIST TABLESNAME = LISTTABLES.sqlDESCRIPT= This script lists all Tables.

REM ***** LIST TABLES

CLEAR COMPUTES

CLEAR BREAKS

REPHEADER LEFT 'LIST TABLES' SKIP 2





COL Table_Name FORMAT A30 HEADING 'Table'

COL Num_Rows FORMAT 9999999990 HEADING '# of Rows'

SET PAGESIZE 66

SET LINESIZE 80

SET NEWPAGE 0

SET VERIFY OFF


ACCEPT Name_List PROMPT 'Input Table Name or % forAll: '



REPHEADER OFF


COMPUTE COUNT OF TABLE_NAME ON OWNER

SELECT Owner, Table_Name, Num_Rows

FROM DBA_TABLES


AND Table_Name like '&&Name_List'

ORDER BY Owner, Table_Name;

SCRIPT = LIST TRIGGERSNAME = LISTTRIGS.sqlDESCRIPT= This script lists all Triggers.

REM ***** LIST

CLEAR COMPUTES

CLEAR BREAKS

REPHEADER LEFT 'LIST ' SKIP 2





COL Trigger_Name FORMAT A30 HEADING 'Trigger'

COL Trigger_Type FORMAT A16 HEADING 'Trigger Type'

COL Triggering_Event FORMAT A30 HEADING 'TriggeringEvent'


SET PAGESIZE 66

SET LINESIZE 132

SET NEWPAGE 0

SET VERIFY OFF


ACCEPT Name_List PROMPT 'Input Trigger Name or % forAll: '

ACCEPT Type_List PROMPT 'Input Trigger Type or % forAll: '

ACCEPT Event_List PROMPT 'Input Triggering Event or %for All: '




REPHEADER OFF


COMPUTE COUNT OF TRIGGER_NAME ON OWNER

SELECT Owner, Trigger_Name, Trigger_Type,Triggering_Event, Status

FROM DBA_TRIGGERS


AND Trigger_Name like '&&Name_List'

AND Trigger_Type like '&&Type_List'

AND Triggering_Event like '&&Event_List'


ORDER BY Owner, Trigger_Name;

SCRIPT = LIST TYPESNAME = LISTTYPES.sql



DESCRIPT= This script lists all Types.

REM ***** LIST TYPES

CLEAR COMPUTES

CLEAR BREAKS

REPHEADER LEFT 'LIST TYPES' SKIP 2



COL Type_Name FORMAT A30 HEADING 'Type'

COL Typecode FORMAT A27 HEADING 'Type Code'

COL Attributes FORMAT 9999999990 HEADING '# of Attr'

COL Methods FORMAT 9999999990 HEADING '# of Meth'

SET PAGESIZE 66

SET LINESIZE 132

SET NEWPAGE 0

SET VERIFY OFF


ACCEPT Name_List PROMPT 'Input Type Name or % for All:'



REPHEADER OFF


COMPUTE COUNT OF TYPE_NAME ON OWNER

SELECT Owner, Type_Name, Typecode, Attributes, Methods

FROM DBA_TYPES


AND Type_Name like '&&Name_List'

ORDER BY Owner, Type_Name;

SCRIPT = LIST VIEWSNAME = LISTVIEWS.sql



DESCRIPT= This script lists all Views.

REM ***** LIST VIEWS

CLEAR COMPUTES

CLEAR BREAKS

REPHEADER LEFT 'LIST VIEWS' SKIP 2



COL View_Name FORMAT A30 HEADING 'View'

COL View_Type FORMAT A30 HEADING 'View Type'

COL Text_Length FORMAT 9999999990 HEADING 'Length'

SET PAGESIZE 66

SET LINESIZE 132

SET NEWPAGE 0

SET VERIFY OFF


ACCEPT Name_List PROMPT 'Input View Name or % for All:'



REPHEADER OFF


COMPUTE COUNT OF VIEW_NAME ON OWNER

SELECT Owner, View_Name, View_Type, Text_Length

FROM DBA_VIEWS


AND View_Name like '&&Name_List'

ORDER BY Owner, View_Name;



Description Scripts


Description Scripts

• Describe Database Configuration• Describe Database Users• Describe Objects

What follows are several scripts that will describe the various objects inyour database. These scripts are:

1. Describe Database Configuration2. Describe Database Users3. Various Describe Object Scripts, including List Database Links,

Functions, Indexes, Java Classes, Java Resources,Java Source, LOBs, Packages, Package Bodies,Procedures, Sequences, Synonyms, Tables, Triggers,Types, and Views.

NOTE: In this discussion, we are not going to give you samples of thescripts for description. That would be too lengthy. Rather, we will discussthe Database Views that maintain the information you need. Those staticviews are discussed at the end of the scripts.

The scripts are reproduced here for your use. We give them defaultnames, but you are welcome to rename them when you use them on yourdatabase.

SCRIPT = Describe Database Configuration



NAME = DESCDBCONF.sqlDESCRIPT=This script will report on the configuration of the

database as it currently existings.

REM ***** DESCRIBE DATABASE CONFIGURATION

CLEAR COMPUTES

CLEAR BREAKS

SET HEADING ON

SET PAGES 1000

SET LINESIZE 80

SET VERIFY OFF

COL Segment_Name FORMAT A12

COL TSpace FORMAT A10

COL Initial FORMAT 99999999

COL Next FORMAT 99999999

COL Min FORMAT 999999

COL Max FORMAT 999999

COL Pct FORMAT 990

COL Status FORMAT A10

COL Bytes FORMAT 999999999

COL File_Name FORMAT A37

COL ID FORMAT 99

BREAK ON TSPACE

REPHEADER LEFT 'Database Configration' SKIP 2



REPHEADER OFF

SELECT ' ' FROM SYS.DUAL;

SELECT 'ROLLBACK SEGMENTS:' FROM SYS.DUAL;

SELECT Segment_Name, Tablespace_Name TSpace,

Initial_Extent "INITIAL", Next_Extent "NEXT",



Min_Extents Min, Max_Extents Max,

Pct_Increase Pct, Status

FROM DBA_ROLLBACK_SEGS

ORDER BY Tablespace_Name, Segment_Name;

SELECT 'TABLESPACES:' FROM SYS.DUAL;

SELECT Tablespace_Name TSpace,

Initial_Extent "INITIAL", Next_Extent "NEXT",

Min_Extents Min, Max_Extents Max,

Pct_Increase Pct, Status

FROM DBA_TABLESPACES

ORDER BY Tablespace_Name;

SELECT 'DATAFILES:' FROM SYS.DUAL;

SELECT Tablespace_Name TSpace, File_Name,

File_Id "ID", Bytes, Status

FROM DBA_DATA_FILES

ORDER BY Tablespace_Name;

SCRIPT = Describe Database UsersNAME = DESCUSERS.sqlDESCRIPT=This script will describe database users/schemas

REM ***** DESCRIBE DATABASE USERS

CLEAR COMPUTES

CLEAR BREAKS

REPHEADER LEFT 'DESCRIBE DATABASE USERS' SKIP 2

COL User_ID FORMAT 9990 HEADING 'ID'

COL Username FORMAT A12 HEADING 'Username'

COL DT FORMAT A1 HEADING ''

COL Default_Tablespace FORMAT A15 HEADING 'Default'

COL TT FORMAT A1 HEADING ''

COL Temporary_Tablespace FORMAT A12 HEADING'Temporary'



COL Profile FORMAT A18 HEADING 'Profile'

COL Created FORMAT A9 HEADING 'Created'

SET PAGESIZE 1000

SET LINESIZE 80

SET NEWPAGE 0

SET VERIFY OFF

ACCEPT Owner_List PROMPT 'Input User or % for All: '



REPHEADER OFF

SELECT User_ID, substr(Username,1,12) Username,

decode(Default_Tablespace,'SYSTEM','*',null)

DT, Default_Tablespace,

decode(Temporary_tablespace,'SYSTEM','*',

null) TT, Temporary_Tablespace, Profile,

Created

FROM DBA_USERS

WHERE Username like upper('&&User_List')

ORDER BY Username;

DATABASE STATIC VIEWS:

For the objects stored in your Applications database, you will want to knowwhich static view, maintained by the Database, will give you theinformation that you need. The following table shows that information.

Object Type Static ViewDB Links DBA_DB_LINKSFunctions DBA_SOURCE, Where Type='FUNCTION'Indexes DBA_INDEXESJava Classes DBA_SOURCE, Where Type='JAVA CLASS'Java Resource DBA_SOURCE, Where Type='JAVA RESOURCE'Java Source DBA_SOURCE, Where Type='JAVA SOURCE'LOBs DBA_LOBSPackages DBA_SOURCE, Where Type='PACKAGE'



Package Bodies DBA_SOURCE, Where Type='PACKAGE BODY'Procedures DBA_SOURCE, Where Type='PROCEDURE'Sequences DBA_SEQUENCESSynonyms DBA_SYNONYMSTables DBA_TABLESTriggers DBA_TRIGGERSTypes DBA_TYPESViews DBA_VIEWS

Use the Listing Scripts as templates for Description scripts that you maywant to create. Also, use the DESCRIBE command in SQL*Plus to getdetailed descriptions of the available columns of these static datadictionary views.



Configuration Scripts


Configuration Scripts

• Applications Configuration Script• Report Imminent Extent Failure• Report User Space

What follows are several scripts that will report on your currentconfiguration of your database. These scripts are:

1. Applications Configuration Script2. Report Table Sizes3. Report Imminent Extent Failure4. Report User Space

With little doubt, the most useful configuration script is the ApplicationsConfiguration Script. This scripts useful is enhanced because it is actuallyshipped with the Application. The script is reproduced here for study, butyou can find this script in ANY Applications instance in the file$AD_TOP/sql/adutconf.sql

REM $Header: adutconf.sql 115.11 2000/03/07 22:22:08 rlotero ship $REM +===============================================+REM | Copyright (c) 1996 Oracle Corporation |REM | All rights reserved. |REM +===============================================+REM NAMEREM adutconf.sql



REM DESCRIPTIONREM Utility script to display configuration of ApplicationsREM +===============================================+

SPOOL adutconf.lst

SET VERIFY OFFSET PAGES 9999SET LINES 80

COL application_id FORMAT 99990 HEADING "ID"COL application_name FORMAT a40 HEADING "Name"COL application_prefix FORMAT a6 HEADING "Prefix"COL application_short_name FORMAT a10 HEADING "Short name"COL apps FORMAT a8 HEADING "Product"COL basepath FORMAT a8 HEADING "Basepath"COL crby FORMAT 99990 HEADING "By"COL creation FORMAT a11 HEADING "Created"COL current_size FORMAT 999999990 HEADING "Size (K)"COL data_group_id FORMAT 99990 HEADING "ID"COL data_group_name FORMAT a29 HEADING "Data Group Name"COL default_group_flag FORMAT a4 HEADING "Dflt"COL in_dba_users FORMAT a13 HEADING "In DBA_USERS?"COL initial_extent FORMAT 9999990 HEADING "Initial (K)"COL index_tablespace FORMAT a12 HEADING "Index TS"COL install_group_num FORMAT 90 HEADING "IGN"COL installed_flag FORMAT a9 HEADING "Type"COL language_code FORMAT a4 HEADING "Code"COL luby FORMAT 99990 HEADING "By"COL next_extent FORMAT 9999990 HEADING "Next (K)"COL nls_language FORMAT a30 HEADING "NLS Language"COL number_of_extents FORMAT 9999990 HEADING "Num Extents"COL max_extents FORMAT 9999990 HEADING "Max X"COL min_extents FORMAT 9999990 HEADING "Min X"COL module_db_status FORMAT a9 HEADING "DB Status"COL module_short_name FORMAT a8 HEADING "Module"COL module_version FORMAT a8 HEADING "Version"COL oracle_id FORMAT 99990 HEADING "ID"COL oracle_username FORMAT a12 HEADING "Schema"



COL owner FORMAT a10 HEADING "Owner"COL product_group_id FORMAT 990 HEADING "ID"COL product_group_name FORMAT a28 HEADING "Product GroupName"COL product_group_type FORMAT a10 HEADING "Type"COL product_version FORMAT a8 HEADING "Version"COL argument1 FORMAT a20 HEADING "Arguments"COL release_name FORMAT a12 HEADING "Release"COL read_only_flag FORMAT a4 HEADING "Type"COL sizing_factor FORMAT 99990 HEADING "Size%"COL segment_name FORMAT a10 HEADING "Name"COL status FORMAT a9 HEADING "Status"COL tablespace FORMAT a12 HEADING "Main TS"COL tablespace_name FORMAT a10 HEADING "Tablespace"COL temporary_tablespace FORMAT a12 HEADING "Temp TS"COL default_tablespace FORMAT a12 HEADING "Default TS"COL updated FORMAT a11 HEADING "Updated"

promptprompt Oracle Applications Database Configuration Reportpromptpromptprompt All dates are shown in DD-MM-YYYY FORMATprompt

set head offselect 'Report Date : '||to_char(sysdate,'DD-MM-YYYY HH24:MI:SS') , 'Database name: '||value databasefrom v$parameter where name='db_name';set head on

prompt --> Sql*Plus PAUSE settingprompt

show pause

promptprompt --> Sql*Plus NEWPAGE settingprompt



show newpage

promptprompt --> Rollback Segment Information

select dr.segment_name, dr.owner, dr.tablespace_name, dr.initial_extent/1024 initial_extent, dr.next_extent/1024 next_extent, dr.min_extents, dr.max_extents, dr.statusfrom dba_rollback_segs drorder by 1;

prompt --> Rollback Segment Sizes

select ext.segment_name, ext.owner, ext.tablespace_name, sum(ext.bytes)/1024 current_size, count(*) number_of_extentsfrom dba_extents extwhere ext.segment_type = 'ROLLBACK'group by ext.segment_name, ext.owner, ext.tablespace_nameorder by 1;

promptprompt --> Start of Application Information Gatheringprompt

prompt --> Product Group Information

select product_group_id, product_group_name, release_name,product_group_type, argument1

from fnd_product_groups;

prompt --> Multi-Org enabled?

set head offselect decode(multi_org_flag,'N','No','Y','Yes','No')from fnd_product_groups;



set head on

prompt --> Existing Operating Units

select ORGANIZATION_ID, NAMEfrom hr_operating_unitsorder by ORGANIZATION_ID;

prompt --> Multi-Currency enabled?

set head offselect decode(multi_currency_flag,'N','No','Y','Yes','No')from fnd_product_groups;set head on

prompt --> Registered Applications

select application_id, application_short_name, basepathfrom fnd_applicationorder by application_id/

prompt --> Registered ORACLE Schemas

select fou.oracle_id, fou.oracle_username, fou.install_group_num, fou.read_only_flag

, decode(nvl(du.username,' X '),' X ','No','Yes') in_dba_users, nvl(du.default_tablespace,'Unknown') default_tablespace

, nvl(du.temporary_tablespace,'Unknown') temporary_tablespacefrom dba_users du, fnd_oracle_userid fouwhere du.username(+) = fou.oracle_usernameorder by 1/

prompt --> Product Installation Status and other product information

select decode(nvl(a.APPLICATION_short_name,'Not Found'),'SQLAP','AP','SQLGL','GL','OFA','FA','Not Found','id '||to_char(fpi.application_id),



a.APPLICATION_short_name) apps,decode(nvl(o.ORACLE_username,'Not Found'),

'Not Found','id '||to_char(fpi.oracle_id), o.ORACLE_username) ORACLE_username, decode(fpi.status,'I','Installed','S','Shared', 'N','Inactive',fpi.status) status, fpi.db_status, fpi.install_group_num,

fpi.product_version, fpi.sizing_factor,fpi.tablespace, fpi.index_tablespace

from fnd_oracle_userid o, fnd_application a, fnd_product_installations fpiwhere fpi.application_id = a.application_id(+) and fpi.oracle_id = o.oracle_id(+)order by 1,2/

prompt --> Localization Module Information

select decode(a.APPLICATION_short_name,'SQLAP','AP','SQLGL','GL','OFA','FA',a.APPLICATION_short_name) apps, o.ORACLE_username, fmi.module_short_name, fmi.module_version

, decode(fmi.status,'I','Installed','S','Shared', 'N','Inactive',fmi.status) status

, decode(fmi.db_status,'I','Installed', 'N','Inactive',db_status) module_db_statusfrom fnd_oracle_userid o, fnd_application a, fnd_module_installations fmiwhere fmi.application_id = a.application_id(+) and fmi.oracle_id = o.oracle_id(+)order by 1,2,3/

prompt --> Registered Data Groups

select data_group_id, data_group_name , decode(default_group_flag,'N','No','Y','Yes', default_group_flag) default_group_flag



, to_char(creation_date,'DD-MM-YYYY') creation, created_by crby, to_char(last_update_date,'DD-MM-YYYY') updated,

last_updated_by lubyfrom fnd_data_groupsorder by data_group_id/

prompt --> Base language and other Installed languages

select decode(installed_flag,'I','Installed','B','Base','Unknown')installed_flag,language_code, nls_language from fnd_languages

where installed_flag in ('I','B')order by installed_flag;

prompt --> Setting of NLS_NCHAR_CHARACTERSET'

set head offselect VALUE NLS_NCHAR_CHARACTERSET fromV$NLS_PARAMETERSWHERE PARAMETER = 'NLS_NCHAR_CHARACTERSET';set head on

prompt --> Setting of NLS_CHARACTERSET

set head offselect VALUE NLS_CHARACTERSET from V$NLS_PARAMETERSwhere PARAMETER = 'NLS_CHARACTERSET';set head on

prompt --> Setting of NLS_DATE_FORMAT

set head offselect VALUE NLS_DATE_FORMAT from V$NLS_PARAMETERSwhere PARAMETER = 'NLS_DATE_FORMAT';set head on

prompt --> Setting of NLS_NUMERIC_CHARACTERS



set head offselect VALUE NLS_NUMERIC_CHARACTERS fromV$NLS_PARAMETERSwhere PARAMETER = 'NLS_NUMERIC_CHARACTERS';set head on

prompt --> Setting of NLS_LANGUAGE

set head offselect VALUE NLS_LANGUAGE from V$NLS_PARAMETERSwhere PARAMETER = 'NLS_LANGUAGE';set head on

prompt --> Setting of NLS_SORT

set head offselect VALUE NLS_SORT from V$NLS_PARAMETERSwhere PARAMETER = 'NLS_SORT';set head on

prompt --> Replication Package Installed?

set head offselect decode(count(*), 0, ' Not Installed ', ' Yes, Installed ')from all_objectswhere object_name in ( 'REPCOLUMN');set head on

promptprompt --> End of Application Information Gathering

spool offexit;

SCRIPT = REPORT IMMINENT EXTENT FAILURENAME = REPEXTFAIL.sqlDESCRIPT=This script will report on imminent next extent

failures.



REM ***** REPORT IMMINENT EXTENT FAILURE

CLEAR COMPUTES

CLEAR BREAKS

REPHEADER LEFT 'REPORT IMMINENT EXTENT FAILURE' SKIP 2


COL Tablespace FORMAT A10 HEADING "Tablespace"

COL Type FORMAT ALL HEADING "Object Type"

COL Name FORMAT A30 HEADING "Object Name"

COL Partition_Name FORMAT A10 HEADING "Partition"

COL Next_Extent FORMAT 9,999,999,999 HEADING "NextExtent (b)"

SET PAGESIZE 66

SET LINESIZE 80

SET NEWPAGE 0

SET VERIFY OFF



REPHEADER OFF

BREAK ON TABLESPACE

SELECT dbas.Tablespace_Name tablespace,

decode(dbas.segment_type,'TABLE PARTITION',

'TABLE','INDEX PARTITION', 'INDEX',

dbas.segment_type) Type, dbas.segment_name

name, nvl(dbas.partition_name, 'N/A')

Partition_Name, dbas.next_extent

Next_Extent

FROM dba_segments dbas, dba_free_space dbafs

WHERE dbas.segment_type in ('TABLE', 'INDEX',

'TABLE PARTITION', 'INDEX PARTITION')

AND dbafs.tablespace_name =

dbas.tablespace_name

GROUP BY dbas.tablespace_name,



dbas.segment_type, dbas.segment_name,

dbas.partition_name, dbas.next_extent

HAVING max(dbafs.bytes) < dbas.next_extent

ORDER BY 1,2,3,4;

SCRIPT = REPORT USER SPACENAME = REPUSRSPACE.sqlDESCRIPT=This script will report on space usage by user

REM ***** REPORT USER SPACE

CLEAR COMPUTES

CLEAR BREAKS

REPHEADER LEFT 'REPORT USER SPACE' SKIP 2


COL Tablespace FORMAT A15 HEADING 'Tablespace'

COL Username FORMAT A15 HEADING 'User Name'

COL Usage FORMAT 999,999,999 HEADING 'Usage'

COL Quota FORMAT 999,999,999 HEADING 'Quota'

COL Percent FORMAT 9,999.9 HEADING '%'

SET PAGESIZE 66

SET LINESIZE 80

SET NEWPAGE 0

SET VERIFY OFF



REPHEADER OFF

BREAK ON TABLESPACE SKIP 1

COMPUTE SUM OF USAGE ON TABLESPACE

COMPUTE SUM OF QUOTA ON TABLESPACE

SELECT dbatq.tablespace_name TABLESPACE,

dbatq.username, dbatq.bytes Usage,



dbatq.max_bytes QUOTE

FROM dba_ts_quotas dbatq, dba_users dbau,

dba_tablespaces dbat

WHERE dbau.username = dbatq.username

AND dbat.tablespace_name =

dbatq.tablespace_name

AND dbat.status = 'ONLINE'

AND (dbatq.bytes > 0 or dbatq.max_bytes > 0)

ORDER BY dbatq.tablespace_name, dbatq.username;



Summary


Summary

In this lesson, you should have learned how to:• Use SQL scripts to explore Oracle Applications

database objects.


11i Manufacturing Functional Foundation: OverviewChapter 6 - Page 1

11i Manufacturing FunctionalFoundation: OverviewChapter 6



11i Manufacturing Functional Foundation: Overview

Copyright Oracle Corporation, 2001. All rights reserved.®

11i Manufacturing Functional Foundation:Overview



Objectives


Objectives

After completing this lesson, you should be able to dothe following:• Describe application development standards• Discuss Entity Relationship Diagrams (ERDs)• Describe the Oracle manufacturing applications• Describe the benefits of using and the methods for

managing your open interface processing• Discuss data conversion

TopicsThis unit describes the database tables that are affected by setup activitieswithin certain Oracle Manufacturing applications.At the end of this unit, you should be able to identify these tables within eachapplication setup definition and explain the major columns within each table.Additionally, you should be able to understand and use an entity relationshipdiagram from an application technical reference manual to assist you in furtherexploring these database table relationships.



Agenda


Agenda

• Application development standards• Entity Relationship Diagram (ERD) definitions• Oracle manufacturing applications• Open interfaces and data conversion



Agenda


Agenda

• Application development standards• Entity Relationship Diagram definitions• Oracle manufacturing applications• Open interfaces and data conversion



Application Development Standards


Application Development Standards

• Applications server directory structure• Database object naming conventions:

– Database object names– Table and view names– Column names– Index names

• Development standards:– WHO columns– Column order

• Program naming standards



The Applications Server Directory Structure


The Applications Server DirectoryStructure

$APPL_TOP$APPL_TOP

applsysapplsys..envenv fndfnd invinv “custom”“custom”

1.01.0

binbin liblib formsforms ............

1.01.0

The Directory Structure of Oracle Applications Product FilesIn the basic directory structure, a top applications directory holds one set ofproduct files. You create this directory and set the environment variable$APPL_TOP to point to it. AutoInstall sets up a directory tree for each fullyinstalled or dependent product under this directory.A product directory tree starts with a directory that uses the short name of theproduct, such as inv for Oracle Inventory. It also contains a version directoryand various subdirectories for product files.If you will be using custom code and programs, you need to set up a separatedirectory to hold the custom code so that it will not be overwritten during asystem upgrade by the AutoInstall program.



Database Naming Conventions


Database Naming Conventions

Naming StandardsOracle uses certain standards to create tables, columns, views, and indexes.Following these guidelines makes it easier for you to understand the applicationdata structures that support them.Database objects (tables, views, or indexes) should be:

• Unique across all applications• Prefixed with the application short name• Plural• End-user oriented• Concise (avoid unnecessary abbreviations)• Unambiguous

Column names should be:• Unprefixed if not a primary key column• Singular• End-user oriented• Concise (avoid unnecessary abbreviations)• Unambiguous

Index names should:• Reflect the name of the table they index (prefix is the table name)• Be identified as unique indexes by using the suffix _Um, where m is a

number



• Be identified as nonunique indexes by using the suffix _Nm, where m is anumber

Note: One method used to name custom indexes is to begin with “99” and workbackwards. If you name a custom index “N4,” and then in Oracle’s next releasean index named “N4” is used, it will overwrite your custom index.






Standards for DevelopmentColumn NamesAll tables must have the following column names in order to facilitate the WHOquery:LAST_UPDATE_DATE LAST_UPDATED_BYLAST_UPDATE_LOGIN CREATION_DATECREATED_BYThe following columns should be included, although they are not required:REQUEST_ID PROGRAM_APPLICATION_IDPROGRAM_ID PROGRAM_UPDATE_DATEColumn OrderOrder the table columns according to the following priorities:Primary key columns (major to minor)WHO columnsRequired columnsForeign keysOptional columnsAttributes (descriptive flexfield columns)LONG data types

Standards in Programming



Standard AbbreviationsStandard abbreviations make applications easier to understand. The following isa partial list of common abbreviations used in Oracle Applications:AVG AverageID System-generated unique identifierLEN LengthMAX MaximumMIN MinimumMISC MiscellaneousNUM End-user-visible numberSEQ SequenceSPEC SpecificationUOM Unit of measureProgram NamesYou use program naming guidelines to identify the application, location, andfunction of a program. The general program name format is AAAGGDDD,where:AAA is a three-character application prefix, using “X” to fill blanksGG is a two-character group building-block identificationDDD is a three-character letter form descriptionAll program names must be made up of eight characters. Use uppercase lettersfor the program name and lowercase letters for extensions.



Summary


Summary

In this lesson, you have learned how to use:• Directory structure of Oracle Application files• Database object naming conventions:

– Database object names– Table and view names– Column names– Index names

• Application development and program namingstandards



Agenda


Agenda




Entity Relationship Diagram Definitions


Entity Relationship Diagram Definitions

• Primary key• Foreign Key• Diagramming Conventions



Primary Key


Primary Key

PO_HEADERS_ALL TablePO_HEADERS_ALL Table

PO_HEADER_ID VENDOR_ID APPROVED_FLAG . . .

124 58 N . . .

123 57 Y . . .

. . . . . . . . . . . .

The primary key of the table is the column or setof columns that makes every row in that tableunique.

DescriptionGood relational database design ensures data integrity and minimizes dataredundancy. These goals are accomplished by storing the details of an entity(such as item, supplier, and category) only once, and maintaining relationshipsbetween that entity and other entities in the database that need access to itsdetails. For example, an item description is stored only once, but bills ofmaterial that use that item as a component need access to its description. Thedatabase design maintains a relationship between the table that stores the itemattributes (MTL_SYSTEM_ITEMS_B) and the table that represents the bills ofmaterial component (BOM_INVENTORY_COMPONENTS). Since items andcomponents are called entities, these relationships are referred to as entityrelationships.



Foreign Key


Foreign Key

PO_LINES_ALL TablePO_LINES_ALL Table

A foreign key within one table references aprimary key that has been previously definedelsewhere in the database.

PO_HEADER_ID PO_LINE_ID 587

588

589

123

123 124

LINE_NUM ITEM_ID . . .

1 1024 . . .

2 957 . . . 3 587 . . .

DescriptionIn a relational database, foreign key relationships are represented by storing amatching element of data in both tables. Most often, it is the data element (orcombination of elements) that uniquely identifies an entity, the primary key,stored in another table to indicate the relationship between tables. When theprimary key from one table is stored in another table, it is referred to as theforeign key. For example, the primary key of the MTL_SYSTEM_ITEMS_Btable (INVENTORY_ITEM_ID/ ORGANIZATION_ID) is stored as a foreignkey in BOM_INVENTORY_COMPONENTS table. Refer to the applicationTechnical Reference Manual (TRM) for the complete listing of foreign keys.

Multiple Products with Shared Entities• Items:

– Bills of Material/Engineering– Planning– Inventory– Order Management– Work in Process

• Locations:– Inventory– Master Scheduling/MRP– Oracle Payables– Purchasing



• Organizations• Salespersons:

– Oracle Order Management– Oracle Receivables

• Sets of Books:– Fixed Assets– General Ledger– Inventory– Payables– Purchasing– Project Accounting– Receivables– Work in Process



Primary Key Relationships


Primary Key RelationshipsPO_HEADERS_ALLPO_HEADERS_ALL

57 Y . . .

VENDOR_ID APPROVED_FLAG . . .PO_HEADER_ID

124 58 N . . .

. . . . . . . . . . . .

123

LINE_NUM ITEM_ID . . .

1 1024 . . . 2 957 . . .

3 587 . . .

PO_LINE_ID 587

588

589 124

PO_HEADER_ID

123

123

PO_LINES_ALLPO_LINES_ALL

NoteIn the example in the slide, PO_HEADER_ID is the primary key in thePO_HEADERS_ALL table and the foreign key in the PO_LINES_ALL table.



Foreign Key Example


Foreign Key Example

PO_HEADERS_ALL table contains information foryour purchasing documents. Each row containsbuyer information, supplier information, notes,foreign currency information, terms andconditions information, and the document status.

Foreign Key Column

FROM_HEADER_ID

Primary Key Table

PO_HEADERS_ALL

Primary Key Column

PO_HEADER_ID

VENDOR_ID

VENDOR_CONTACT_ID

PO_VENDORS

PO_VENDOR_CONTACTS

VENDOR_ID

VENDOR_CONTACT_ID

VENDOR_SITE_IDPO_VENDOR_SITES VENDOR_SITE_ID

NoteYou can refer to each individual application Technical Reference Manual(TRM) for the full list of tables with their primary and foreign keys. For theexample above, refer to the Oracle Purchasing Technical Reference Manual.You can find a list of these manuals in the Related Publications section of thepreface.



Database Diagramming Conventions


Database Diagramming Conventions

A

A

A B

B

C

B

OptionalityOptionalityMust be relationshipMust be relationship

May be relationshipMay be relationship

Types of Table RelationshipsTypes of Table RelationshipsEach row in Table AEach row in Table Amay be related to a rowmay be related to a rowin Table Bin Table B

Each row in Table AEach row in Table Amust be related to amust be related to arow in Table B; a rowrow in Table B; a rowin Table B may bein Table B may berelated to one or morerelated to one or morerows in Table Arows in Table A

Each row in Table AEach row in Table Amust be related to amust be related to arow in either Table Brow in either Table Bor Table C, but notor Table C, but notbothboth

Database DiagramsA database diagram or entity relationship diagram (ERD) graphically representsthe database tables of an application and the relationships among them. Byunderstanding these diagrams, you can learn which tables are used by aparticular application and how these tables interrelate.The major tables and their relationships are discussed within each Oracleapplication module, with reference to the ERD.Additionally, each Oracle application module has a technical reference manualthat details these relationships. Refer to these technical reference manuals foradditional information regarding the database table relationships. For thepurpose of this course, the primary tables selected are based on the coremanufacturing tasks performed in a business environment.



Practice Setup


Practice Setup

1. Create a new user name for yourself, and assignthe following responsibilities to it:– Manufacturing, Vision Operations– System Administrator– Application Developer

2. Sign back onto the system with your new username.

Add Yourself as a User1 With System Administrator responsibility, navigate to define a new user.

(N) Security > User > Define2 Enter a new user name APPS## (where ## is your terminal number) and a

description for yourself.3 Enter a temporary password - “first” works well. You will need to re-enter it

to confirm it.4 Select “Baker, Catherine” from the List of Values in the “Person” field to

the right of the User Name field. You will get a Caution screen - click OK.5 Select a Customer and a Supplier in the appropriate fields from the List of

Values.6 In the Responsibility region, use the List of Values (LOV) to select the

following Responsibilities:– System Administrator– Manufacturing, Vision Operations (USA)– Application Developer

7 Save your work.8 Close the form.

Log on as Yourself (N) (M) File > Log On



1 Enter your new user name and the temporary password you selected. Thesystem informs you that the password has expired. Enter “Oracle” as thenew password.

2 Select Manufacturing, Vision Operations responsibility.Instructor NotePerform the following setup and practices if they have not been performed inthe Technical Foundation segment of this course.



Practice Overview


Practice Overview

1 Find the code values for the days of the week.2 Find the user id that corresponds to your user

name. Find your encrypted password. (For extra credit, decrypt the password.)3 Find Determine what responsibilities are assigned

to your user name.



Practice 1


Practice 1

1 Find the code values for the days of the week.

InstructionsEnter the following values for Tables, Keys, and Columns:

• Tables: fnd_lookups• Keys: lookup_type• Columns: lookup_type, lookup_code, meaning



Practice 1 Solution


Practice 1 Solution

1 Find the code values for the days of the week.

SQL Code SolutionSELECT

substr(lookup_type,1,15) “Type”,substr(lookup_code,1,5) “Code”,substr(meaning,1,15) “Meaning”

FROMfnd_lookups

WHERElookup_type LIKE ‘DAY_OF_WEEK’



Practice 2


Practice 2

2 Find the user id that corresponds to your username. Find your encrypted password.

(For extra credit, decrypt the password.)


• Tables: fnd_user• Keys: user_name• Columns: user_name, user_id, encrypted_user_password



Practice 2 Solution


Practice 2 Solution

2 Find the user id that corresponds to your username.


substr(user_name,1,10) “Name”,substr(user_id,1,10) “ID”,substr(encrypted_user_password,1,70) “Password”

FROMfnd_user

WHEREuser_name LIKE ‘&UserName%’



Practice 3


Practice 3

3 Find Determine what responsibilities are assignedto your user name.


• Tables: fnd_user, fnd_user_responsibility, fnd_responsibility_tl• Keys: user_name, responsibility_id, application_id, user_id• Columns: user_name, responsibility_name



Practice 3 Solution


Practice 3 Solution

3 Find Determine what responsibilities are assignedto your user name.


substr(usr.user_name,1,10) “User Name”,substr(res.responsibility_name,1,55) “Resp Name”

FROMfnd_user usr,fnd_responsibility_tl res,fnd_user_resp_group ur

WHEREusr.user_name LIKE ‘&UserName%’ ANDres.responsibility_id = ur.responsibility_id ANDur.user_id = usr.user_id



Practice 4


Practice 4

Find the Inventory Organizations in the Visiondatabase and their parent organizations.


• Tables: mtl_parameters, hr_all_organization_units• Keys: organization_id• Columns: organization_id, organization_code, name,

master_organization_id



Practice 4 Solution


Practice 4 Solution

Find the Inventory Organizations in the Visiondatabase and their parent organizations.


• substr(org.organization_id,1,5) “ID”,• substr(org.organization_code,1,5) “Code”,• substr(hr.name,1,30) “Name”,• substr(org.master_organization_id,1,10) “Parent”

FROM• mtl_parameters org,• hr_all_organization_units hr

WHERE• hr.organization_id = org.organization_id



Agenda


Agenda




Oracle Manufacturing Applications


Oracle Manufacturing Applications

• Inventory• Bills of Material• Engineering• Cost Management• Work in Process• Purchasing

Lesson OverviewThe core Oracle Manufacturing applications major functionalities will bediscussed at a very high level to facilitate the database table discussions. Fordetailed application information, attend an individual class covering detailedcontent specific to that application module.



Oracle Inventory


Oracle Inventory

Inventory

Order entry

Internal Internal shipmentshipment

ReceiveReceive DeliverDeliver

InspectInspect

TransferTransfer

Shop floorShop floor

InventoryInventory

SupplierSupplier

ShipmentShipment

ExpenseExpense

DescriptionOracle Inventory maintains quantities on hand using a variety of stockmaintenance tools, controlled transactions, and planning methods.

Organization and Item Definition• Set up inventory structure.• Define stock and nonstock parts.• Establish planning and purchasing attributes.• Track inventory by item, item revision, serial number, or lot number.

Transactions and Maintenance• Receive parts from and return parts to suppliers.• Transfer inventory between organizations directly or as in-transit

shipments.• Add material overhead to the cost of a part.• Conduct inventory cycle counts based on ABC classification.• Record physical inventory counts and adjustments.• Process miscellaneous issues and receipts.• Transfer material between subinventories.• Receive and inspect material returned from a customer.• Track lots and serial numbers for an item.• Return repaired or substitute items to a customer.



Forecasting and Planning• Generate forecasts for future product demand.• Generate or modify requisitions using the min/max or the reorder point

planning methods.



Oracle Bills of Material



• The Oracle engineering products are Oracle Billsof Material and Oracle Engineering.

• You use Oracle Bills of Material to:– Create and maintain production bills of

materials– Create and maintain production resources,

departments, routings, and lead times– Perform mass changes– Delete product information– Maintain the workday calendar

OracleOracleBills of MaterialBills of Material

DescriptionOracle Bills of Material develops and maintains manufacturing bills of material(BOMs) and routings to drive planning, costing, and work-in-process tracking.

Routings• Specify department and resources usage.• Define shop floor controls.• Maintain multiple revisions of routings.• Define Dybanic, lot-based flow routing for operation flexibility.

Bills of Material• Define component usage, yield, and material control.• Integrate with routings for point-of-use definition.• Maintain multiple revisions of bills of material.

Lead TimeCalculate manufacturing lead time to produce goods from routing standards.

Standard CostCalculate standard costs from bills of material and routings.

Views and Reports• Perform a single-level explosion of bills of material (or fully indented

explosions).• Choose to include or exclude costs in the explosion.



• Compare two bills of material or alternative versions of the same bill ofmaterial.

MaintenanceYou can efficiently manage upwards of 1000 inventory organization structuresin a single Application instance, using organization hierarchies. Organizationhierarchies: by establishing hierarchies, you can group organizations together toperform a number of processes across all organizations at any level in thehierarchy. These processes include:

• establishing common bills• deleting BOMs• viewing item usage• exporting multilevel BOMS



Oracle Engineering


Oracle Engineering

• Create and maintain engineering items• Create and maintain engineering bills of materials• Create and maintain engineering resources,

departments, routings, and lead times• Transfer engineering product information to

production• Process engineering change orders• Perform mass changes• Delete product information

Oracle EngineeringOracle Engineering

DescriptionOracle Engineering interacts with other Oracle manufacturing applications toprovide a cohesive integrated business solution. Oracle Engineering helps youdefine product and process specifications. It also provides the informationrequired for effective planning and execution.

Oracle Oracle Engineering• Define engineering and manufacturing bills of material.• Define engineering and manufacturing routings.• Manage product changes with engineering change orders (ECOs).• Create new design specifications using Oracle Engineering.• Determine resource availability using the workday calendar.• Specify detailed resource use.

Introducing New Products• Define engineering items, BOMs, and routings to prototype new product

designs.• Calculate lead times and release engineering prototypes to manufacturing.

Defining Planning Bills• Define planning bills to assist with sales strategy.• Provide BOM maintenance.

Managing Engineering Changes



• Define and implement engineering changes to prototype and productionitems.

• Schedule ECOs manually or with imbedded workflow, or to correspond tothe planned use-up of a specific item.

• Create ECOs across large organization structures at any given level in anorganization hierarchy.

Deleting Obsolete InformationDelete obsolete item and ECO information.



Oracle Cost Management



ProductionProduction ProfitabilityProfitabilityInventoryInventory

AnalysisAnalysis Audit trailAudit trailItemItemcostscosts

DescriptionOracle Cost Management automatically performs the cost accounting for allyour Oracle Inventory, Work in Process, and Purchasing transactions. At anytime, your inventory and work-in-process costs are up-to-date, and yourinventory value matches the cumulative total of your accounting transactions.

Standard Costing• Oracle Cost Management supports standard costing for inventory, bills of

material, and work-in-process costing.• You may use standard costing for one organization and average costing for

another organization.Average Costing

• Oracle Cost Management supports average costing for inventory, bills ofmaterial, and work-in-process costing. Average costs are automaticallyupdated as transactions are processed.

• If you have Oracle Bills of Material installed, you can transact yourinventory at average, and use the standard cost features for product costsimulations and budgeting.

Extensive Cost Simulation CapabilityCreate unlimited sets of product costs, called cost types. Each cost type has itsown items and specific cost controls for the items.



Copy from one cost type to another, mass edit a cost type, run item cost andcomparison reports, roll up costs, or update frozen standard costs by cost type.Each cost type may have its own activities and activity-based costs.

Simultaneous Open PeriodsSet up and maintain simultaneous open periods.Run transactions for the next period and still report inventory balances andquantities from the prior open period using historical inventory valuationreports.This gives you the flexibility to reconcile and analyze the period before youclose it, while you continue to conduct business in the subsequent period.

Period Close and General Ledger TransferClose the earliest open period at any time. Closing a period automaticallytransfers summary or detailed information to the general ledger.Perform interim general ledger transfers at any time, without closing a period.The general ledger transfer passes all accounting entries not transferred sincethe last period close.

Accruals Booked on ReceiptOracle Purchasing updates the accounts payable accrual accounts automaticallyand accrues your uninvoiced receipts.



Oracle Work in Process


Oracle Work in Process

Manufacturing methods include:• Discrete manufacturing• Repetitive manufacturing

Work in Process FunctionalityOracle Work in Process supports discrete, repetitive, assemble-to-order, workorder-less, or a combination of these manufacturing methodsManufacturing SupportBuild discrete jobs, both standard and nonstandard (prototype, rework,maintenance, and special projects)Production SchedulingLoad and sequence repetitive production by assembly and production lineMaterial ControlIssue and return components from and to inventoryShop Floor ControlMove assemblies between and within operations



Oracle Work in Process Transactions


Oracle Work in Process Transactions

InventoryInventory

Raw materialRaw materialinventoryinventory

Finished goodsFinished goodssubinventorysubinventory

Work in ProcessWork in Process

Jobs andJobs andschedulesschedules

Scrap rejectedassemblies

IssueIssuematerialmaterial

CompleteCompletefinishedfinished

assembliesassemblies Move assemblies onthe shop floor and charge resources

DescriptionOracle Work in Process tracks material and production activity on the shopfloor to facilitate inventory control, job scheduling, and costing.

Material IssueRecord material issues to discrete jobs, repetitive schedules, or nonstandardjobs.

Shop Floor MoveRecord production activity and job completions.

Resource Charging• Charge multiple resources option.• Charge resources automatically (based on shop floor moves) or manually, at

either standard or actual labor rates.Other Transactions

• Cost material using standard cost.• Use repetitive schedules to simplify material and production reporting.• Use lot and serial number controlled parts in production moves.



Oracle Purchasing


Oracle Purchasing

RequisitionRequisitionpoolpool

Receive against POReceive against PO Match invoices in PayablesMatch invoices in Payables

AutomaticallyAutomaticallycreatecreate

Maintain documentsMaintain documents

Accept Revise Control

POPO

ManuallyManuallycreatecreate

ApproveApprove

DescriptionOracle Purchasing is a comprehensive procurement solution, designed to reduceadministration costs while focusing on value analysis, strategic supply basemanagement, and contract negotiation.

Requisitioning• Replace paper processing with online requisition generation, purchase order

creation, and document approval.• Regulate document access, control or modification activity, and approval

based on organizational signature and security policies.• Minimize data entry time with time-saving templates, express processing

functions, and default infrastructures.Purchasing

• Control purchasing activity and enable accurate automatic pricing using anapproved supplier list.

• Consolidate purchase requirements from multiple warehouses, plants, orlocations.

ReceivingReceive production items, Maintenance, Receipt and Overhead (MRO) items,and services using a common flexible receiving process.

Business Communication• Facilitate communication between requesters, buyers, receiving staff, and

accounts payable staff using online inquiries and notes.



• Provide access to purchasing information to related functions (marketing,finance, legal, master scheduling, inventory management, production, costaccounting, customer order entry) on an optional basis.

• Manage historical data.



Purchasing Transactions


Purchasing Transactions

• Suppliers• Requisitions• Purchase orders• Receipt and delivery

Transaction FunctionalityPurchasing provides you with request for quotation (RFQ) and quotationfeatures to handle your sourcing needs. You can create an RFQ fromrequisitions, match supplier quotations to your RFQ, and automatically copyquotation information to purchase orders.Additionally, you are able to:

• Review all your purchases with your suppliers to negotiate better discounts• Create purchase orders simply by entering a supplier and item details

Purchasing provides you with the features you need to satisfy your receipt,inspection, transfer, and delivery needs.



Agenda


Agenda




Importing Information



Oracle Manufacturing applications import programsprovide the features you need to fill the followingbasic integration needs:• Import data more easily by using a format that is

consistent with the structure of your new system• Import from a variety of environments• Review the results of an import program

Importing InformationBasic Importing NeedsOracle Manufacturing applications import programs provide the features youneed to fill the following basic integration needs:To import information in the easiest way possible, the format must be consistentwith the structure of the new system.Import information from a variety of environments, including your own andother accounting systems.Import historical data from your previous manufacturing, sales order, or othermanagement systems to keep your records consistent and up-to-date.Review the results of your import run. Identify which data has been successfullyimported and any errors that may have occurred during the import process.Choosing a Feeder ProgramYou must choose a tool for writing a feeder program to extract data from yourexisting application system’s printed reports, flat file, relational database, orother repository of application information. Use your feeder program topopulate an Oracle application import table with the information you want tointroduce to your Oracle manufacturing system.SQL*Loader is a powerful and easy-to-use tool that you can use to write afeeder program. It enables you to map elements of a character-delimited orfixed-format file, such as a listing or flat file, and to specify which columns ofwhich tables they populate.






Benefits of open interfaces:• Using open interfaces to facilitate integration• Converting static data

Importing Information (continued)Benefits of Using Open InterfacesWhen you use open interfaces to facilitate integration, you can:• Integrate applications from different suppliers with Oracle Applications• Integrate your custom applications with Oracle Applications• Integrate data from numerous sources, such as data-collection devices• Ensure validity of any data in your system through use of a common validation function, regardless of the source of the dataOracle Applications open interfaces simplify the process of converting data thatis relatively static from a prior system to Oracle Applications.Do not bypass the open interfaces process. When Oracle Applications are usedto perform a manufacturing function, any change you make may update manytables at once. Oracle Applications then perform an audit to ensure that all ofthe changes are valid. If you modify Oracle Applications data using SQL*Plus,you can change a row in one table without changing rows in all necessaryrelated tables. In this case, you violate the ability to audit and may potentiallydestroy the integrity of your data.



Open Interface Model


Open Interface Model

DestinationapplicationDestinationapplication

Errorstable

(optional)

Source application

Source application

Interfacetable

TemptablesTemptables LoadLoad ValidateValidate

ProcessProcess

MaintainMaintain

Oracle Applications Open Interface ModelSource ApplicationThe source application, or feeder system, is the application that supplies the datayou want to import into Oracle Applications.Interface TableThe interface table is the intermediary table where the data from your sourceapplication temporarily resides. To load data into an Oracle application, youmust enter data into this table.VALIDATE FunctionThe VALIDATE function is a set of programs used by Oracle Applications toensure the integrity of inbound data before the data is moved from the interfacetable to the permanent application tables. The VALIDATE function inserts rowsinto the errors table or updates the error column in the interface table ifvalidation fails. The VALIDATE function resides in the destination application.Errors Table• Stores all errors found by the VALIDATE and PROCESS functions• Enables you to see several errors for the same data row at once• Resides in the destination application• Several open interface tables in an application can share an errors table.• Instead of an errors table, some Oracle Applications open interfaces use anerror column in the interface table and a log file or report to list the error. Forexample, Oracle General Ledger Journal Import always generates a report.



• Entries in an error table or error report are the output of the VALIDATEprocess.• All Oracle Applications open interfaces have either an errors table or an errorcolumn and a log/report file.• LOAD Function• The LOAD function is a program or set of programs that selects andaccumulates data from your source application and inserts it into the OracleApplications interface table.• The programming languages and tools used in the LOAD function depend onthe hardware and system software of your source application. For example,Oracle functions in Oracle Applications that load an open interface are writtenin Pro*C or PL/SQL.• If you are importing data from an application that is not Oracle, you wouldprobably use a procedural language available on the source application, convertit into an ASCII file, and use SQL*Loader to insert the data into the Oracleinterface table.• PROCESS Function• The PROCESS function, or import function, is the program or set of programsthat processes the data from the interface table into the destination tables. It alsoinserts rows into the errors table or updates the error column in the interfacetable if processing errors are encountered.• The PROCESS function resides in the destination application.• Although the VALIDATE function and the PROCESS function meet twodistinct needs, they are frequently invoked through the same concurrent process.Rows are validated first, and then the valid rows are processed.• MAINTAIN Function• The MAINTAIN function is a form-based program that you can use to query,update, and resubmit interface table rows. Some Oracle Applications interfacesdo not have a form-based MAINTAIN function. In those cases, you can reviewthe log file or report for errors, or you can use SQL*Plus to query up andcorrect errors.• If there is a high volume of errors, you may find it preferable to delete all rowsin the interface table, fix the problem in the LOAD function, and reimport. TheMAINTAIN function resides in the destination application.



Managing Open Interface Processing


Managing Open Interface Processing

Using Oracle Applications, you can tailor yourconcurrent process parameters for frequently usedinterfaces to fit the size and load of your system. Allof the parameters listed affect the process function asdescribed earlier.• Batch size• Launching multiple concurrent processes• General prerequisites

Managing Open Interface ProcessingUsing Oracle Applications, you can tailor your concurrent process parameters forfrequently used interfaces to fit the size and load of your system. All of theparameters listed affect the PROCESS function as described earlier.Batch SizeFor frequently used open interfaces, you can use Oracle Applications to determinethe batch size—that is, the number of rows you want processed in one batch. Youset the batch size to reflect your system’s memory restrictions during processing.Launching Multiple Concurrent ProcessesFor high-volume interfaces, you can use some Oracle applications to launch morethan one concurrent process to handle the processing of your data.General PrerequisitesBefore you perform an open interface, you should be familiar with the forms usedto populate the data tables from within the application. It is advisable to walkthrough, or to work with a functional user to walk through, the forms entry fordata population before trying to perform an open interface from the back end.



Data Conversion


Data Conversion

Data ConversionsThe purpose of this section is to give you an understanding of how to performdata conversions from external systems to Oracle Applications products. Theemphasis in this section is on conversion methodology, not on one specificconversion (for example, item conversion).



Detailed Conversion Plan


Detailed Conversion Plan

Movement of DataPlan the movement of data from an external system to Oracle Applications witha conversion project plan. Develop a detailed conversion plan for each entity,listing all design, development, testing, and conversion tasks. Include resource,software, and hardware requirements to successfully convert each entity.

Designing the Conversion Process• Determine what data to convert (for example, convert only active data).• Document business objectives.• Specify time constraints for the conversion, especially for dynamic data.• Determine the appropriate conversion method; do not overlook manual data

entry.• Perform data mapping.• Install all hardware and software required for the conversion.• Scope all coding efforts, including the cleanup of existing data, extract

programs, translation programs, validation programs, and migratingprograms.

• Determine the testing requirements.Developing Programs for Conversion

• Write extract and import programs.• Write scripts to create any interface or translation tables in Oracle RDBMS.• Write validation, translation, and migration programs.



• Write verification scripts and reports.Performing the Conversion

• Clean up existing data before conversion.• Extract and format data from original source.• Create interface tables in Oracle RDBMS.• Validate and translate data.• Import validated data into production tables.• Run reports.



Designing the Conversion Process


Designing the Conversion Process

There are seven steps you should consider whendesigning your conversion process.

1234567

Data VerificationFor each converted entity, design a conversion process from data extractionthrough data verification. Consider business objectives and dependencies foreach point in the process.Reduce the time required to execute the conversion process with accuratedesigns. Plan resources effectively with reasonable time estimates and gooddesign specifications. Be sure to clean up the database before conversion.

Steps for Design1 Examine the business objectives and requirements to determine the data to

be converted.2 Map the source data to the Oracle applications.3 Identify the tools used to extract and import data. Do not disregard manual

data entry.4 Define flat-file configuration.5 Identify any interface tables to create.6 Design any translation and validation programs.7 List the testing phases and procedures.

Instructor NoteThese are points to bring up with your students, because each question isparticular to a customer’s conversion. The goal is to help students considerissues that are critical to their conversion while you explain the conversionmethod.



• What groups in the company must be involved in determining the businessobjectives?

• What technical resources (software and hardware skills) are currentlyavailable in the company?

• What resources can own each of the design steps?



Developing Conversion Programs


Developing Conversion Programs

1. Write extract and import programs2. Write scripts to create interface and translation

tables3. Write validation scripts4. Write verification scripts and reports

Leveraging the Existing InterfacesLeverage the existing interfaces in Oracle Applications to convert data. Writeprograms using detailed design specifications to convert entities where an openinterface does not exist.Review, test, and tune the performance of each program to ensure a clean andtimely conversion. Identify any performance problems before the conversiondate.

Steps to Develop Programs1 Write an extract program from an external system and format the data into a

flat file.2 Write SQL scripts and SQL*Loader files to create interface tables and

upload the data into the interface tables.3 Write translation, validation, and import programs. Remember to populate

the WHO columns.4 Write verification programs or reports.



Performing the Conversion


Performing the Conversion

• Extract and format data• Create temporary interface tables• Upload data to interface tables• Run translation programs• Run validation programs• Migrate data into production tables• Run verification scripts• Run application reports to verify converted data

Ensuring IntegrityAfter designing and developing all elements of the conversion, perform theconversion. Manage any time constraints and ensure the integrity of theconverted data. Minimize the time required to actually convert from the originalsystem to Oracle Applications by reviewing all programs and designs beforeexecuting the conversion process.

Steps to Perform Conversion1 Create a unique application username, and use it to populate the WHO

columns.2 Extract data from the original source; load and format the data in a flat file.3 Create temporary tables using SQL*Loader scripts.4 Use SQL*Loader scripts to upload the data into interface tables.5 Run translation programs on data in the interface tables.6 Run validation programs on data in the interface tables.7 Migrate translated and validated data into the production tables.8 Run verification scripts.9 Run application reports to verify converted data.



Summary


Summary

In this lesson, you have learned how to:• Describe application development standards• Discuss Entity Relationship Diagrams (ERDs)• Describe the Oracle manufacturing applications• Describe the benefits of using and the methods for

managing your open interface processing• Discuss data conversion

TopicsThis unit describes the database tables that are affected by setup activitieswithin certain Oracle Manufacturing applications.At the end of this unit, you should be able to identify these tables within eachapplication setup definition and explain the major columns within each table.Additionally, you should be able to understand and use an entity relationshipdiagram from an application technical reference manual to assist you in furtherexploring these database table relationships.


11i Manufacturing Functional Foundation: InventoryChapter 7 - Page 1

11i Manufacturing FunctionalFoundation: InventoryChapter 7



11i Manufacturing Functional Foundation: Inventory


11i Manufacturing Functional Foundation:Inventory



Objectives


Objectives

After completing this lesson, you should be able todo the following:• Discuss inventory item definition activities• Identify the major tables used in an item definition• Discuss inventory transaction activities• Identify the major tables used in inventory

transactions• Run queries in SQL*Plus against the appropriate

database tables to find a particular inventory item,its status, and its cycle count activity

• Discuss the open interfaces for inventory

Lesson AimThe aim of this lesson is to provide the student an overview of the itemdefinition process in Oracle Inventory and discuss the database tables that arepopulated as a result of item setup activity.Instructor NoteThe primary key for each of the ERD tables is in each table definition in theNotes section of the slides. Example: ‘The primary key is INVENTORY_ID,ORGANIZATION_ID’, where there are two elements that make up the primarykey. Some _INTERFACE and _TEMP names may not have a primary keyassociated with it.An “(o)” following a primary key name indicates that element to be optional.Example: ‘WIP_ENTITY_ID, OPERATION_SEQ_NUM,REPETITIVE_SCHEDULE_ID (o)’. In this example it indicates that theREPETITIVE_SCHEDULE_ID is part of the primary key when you referencespecific Repetitive schedules tables and not part of the primary key when youreference Discrete job tables.



Agenda


Agenda

• Item definition• Inventory transactions• Open interfaces



Agenda


Agenda




Oracle Inventory


Oracle Inventory

Inventory

Order entry

Internal Internal shipmentshipment

ReceiveReceive DeliverDeliver

InspectInspect

TransferTransfer

Shop floorShop floor

InventoryInventory

SupplierSupplier

ShipmentShipment

ExpenseExpense

DescriptionOracle Inventory maintains quantities on hand using a variety of stockmaintenance tools, controlled transactions, and planning methods.

Organization and Item Definition• Set up inventory structure.• Group inventory organizations into multilevel, hierarchical trees for

managing large organization structures.• Define stock and nonstock parts.• Establish planning and purchasing attributes.• Track inventory by item, item revision, serial number, or lot number.

Transactions and Maintenance• Receive parts from and return parts to suppliers.• Transfer inventory between organizations directly or as in-transit shipments.• Create move orders for subinventory transfers.• Receive alerts or notifications about material shortages.• Add material overhead to the cost of a part.• Conduct inventory cycle counts based on ABC classification.• Record physical inventory counts and adjustments.• Track serial controlled items from receipt through work in process and

inventory to the customer sale.Forecasting and Planning



• Generate forecasts for future product demand.• Generate requisitions using the min/max or the reorder point planning

methods.



Oracle Inventory Database Summary Diagram


Oracle Inventory Database Summary Diagram

MTL_PARAMETERS

LOCATOR

SUBINVENTORY

MTL_MATERIAL_TRANSACTIONS

MTL_SYSTEM_ITEMS_B

HR_ALL_ORGANIZATION_UNITS

MTL_ONHAND_QUANTITIESMTL_TRANSACTION_ACCOUNTS

MTL_SYSTEM_ITEMS_TL

Oracle Inventory Item DefinitionAn item definition is defined for inventory items (part numbers), engineeringitems (bills of material), and purchasing items (outside processing). For eachitem definition, you can specify cost information, unit of measure, lead times,physical attributes, and other pertinent business information related to eachunique item.An item is defined in an item master organization. Then, you assign it to otherorganizations that need to recognize this item.(N) Inventory > Items > Item Master



Inventory Organizations


Inventory Organizations

Master OrgMaster OrgOrganizationsOrganizations

Enterprise

VisionOperations

Seattle Boston Dallas



Oracle Inventory: Organizations


Oracle Inventory: Organizations

GL_CODE_COMBINATIONS

GL_SETS_OF_BOOKS

MTL_INTERORG_PARAMETERS

HR_ALL_ORGANIZATION_UNITS

HR_ORGANIZATION_INFORMATION

MTL_PARAMETERS

MTL_PARAMETERSMTL_PARAMETERS is an inventory organization with which an item isassociated. The primary key is the ORGANIZATION_ID.

MTL_INTERORG_PARAMETERSThis table identifies the receiving organizations linked to a particularorganization. You must define the interorganizational relationship before youperform any interorganization transfers.Units of measure, distance, transfer charge, and accounting information are alsospecified in this table. The primary key is FROM_ORGANIZATION_ID,TO_ORGANIZATION_ID.

GL_SETS_OF_BOOKSGL_SETS_OF_BOOKS stores information about the sets of books you definein your general ledger application. Each row includes the set of books name,description, functional currency, and other information. This table correspondsto the Define Set of Books form. The primary key is SET_OF_BOOKS_ID.

GL_CODE_COMBINATIONSThis table stores valid Accounting Flexfield segment value combinations foreach accounting flexfield structure within your general ledger application. Theprimary key is CODE_COMBINATION_ID.

HR_ALL_ORGANIZATION_UNITSHR_ALL_ORGANIZATION_UNITS stores generic information aboutorganizations. An organization can be used for various purposes in Oracle



Manufacturing applications. For example, one organization can represent abusiness group, an ECO department, a planning organization, and an inventoryorganization. The primary key is ORGANIZATION_ID.



Defining Organizations


Defining Organizations

OrganizationOrganization

The first organization you must set up is the BusinessGroup, to which all other organizations belong.

(N) Inventory > Setup > Organizations > Organizations



Defining Organization Parameters for AdditionalInformation


Defining Organization Parameters forAdditional Information

Inventory Parameters (M1)Inventory Parameters (M1)

You can define and update default inventory andcosting parameters for your current organization.

(N) Inventory > Setup > Organizations > Organizations (B) Others



Locators and Subinventories


Locators and Subinventories

Organization

Seattle

Locator:Recv Dept.

Sub Inv.MRB

Locator:Eng Dept.

Locator:Annex

Sub InvR Dept.

Sub Inv.Stores



Oracle Inventory: Subinventories and Locators


Oracle Inventory:Subinventories and Locators

MTL_SECONDARY_LOCATORS

MTL_ITEM_LOCATIONS

MTL_ITEM_SUB_INVENTORIES

MTL_SECONDARY_INVENTORIES


MTL_SYSTEM_ITEMS_B

MTL_PARAMETERS

MTL_SYSTEM_ITEMS_TL

MTL_SYSTEM_ITEMS_BMTL_SYSTEM_ITEMS_B is the definition table for items. This table holds thedefinitions for inventory items, engineering items, and purchasing items. Theflexfield code is MSTK. The primary key for an item is theINVENTORY_ITEM_ID and the ORGANIZATION_ID. The same item couldbe defined in more than one organization. Each row represents an item in anorganization.

MTL_SYSTEM_ITEMS_TLMTL_SYSTEM_ITEMS_TL is a table holding translated Description columnfor Items. The primary key is INVENTORY_ITEM_ID, ORGANIZATION_ID,LANGUAGE.

GL_CODE_COMBINATIONSThis table stores valid Accounting Flexfield segment value combinations foreach accounting flexfield structure within your general ledger application. Theprimary key is CODE_COMBINATION_ID.

MTL_SECONDARY_INVENTORIESMTL_SECONDARY_INVENTORIES is the definition table for thesubinventory. Subinventories are assigned to items, indicating a list of validplaces in which this item may be located. The primary key isSECONDARY_INVENTORY_NAME, ORGANIZATION_ID.

MTL_ITEM_SUB_INVENTORIES



MTL_ITEM_SUB_INVENTORIES maintains a listing of subinventoriesassigned to an inventory or engineering item. The subinventories make up thevalid list of subinventories when transacting a specific item if the user hasspecified that the item must use subinventories from a predefined list. Theprimary key is INVENTORY_ITEM_ID, ORGANIZATION_ID,SECONDARY_INVENTORY

MTL_ITEM_LOCATIONSMTL_ITEM_LOCATIONS is the definition table for stock locators. Theassociated attributes describe the subinventory to which this locator belongs,and the locator physical capacity. The primary key isINVENTORY_LOCATION_ID, ORGANIZATION_ID.

MTL_SECONDARY_LOCATORSMTL_SECONDARY_LOCATORS stores all locators within a subinventory fora specific item. The locators make up the valid list of locators when transactingthat specific item to/from the subinventory when the user has specified that theitem must use locators from a predefined list. The primary key isINVENTORY_ITEM_ID, ORGANIZATION_ID,SECONDARY_LOCATORS.




Defining Subinventories


Defining Subinventories

Subinventories Summary (M1)Subinventories Summary (M1)

Subinventories are unique physical or logicalseparations of material inventory, such as rawinventory, finished goods, or defective material.

(N) Inventory > Setup > Organizations > Subinventories



Defining Locators


Defining Locators

Stock Locators (M1)Stock Locators (M1)

You use locators to identify physical areas whereyou store inventory items. Item quantities can betracked by locator. Items can also be restricted tospecific locators.

(N) Inventory > Setup > Organizations > Stock Locators



Oracle Inventory: Item Master


Oracle Inventory: Item Master

MTL_ITEM_ATTRIBUTES

MTL_SYSTEM_ITEMS_B

MTL_ITEM_STATUS

MTL_ITEM_TEMPLATES

MTL_ITEM_TEMPL_ATTRIBUTES

MTL_PARAMETERS

MTL_STATUS_ATTRIBUTE_VALUES


MTL_ITEM_ATTRIBUTESMTL_ITEM_ATTRIBUTES stores the item attributes, their user-friendlynames if the item is maintained at the item or item/organization level, and thekind of validation required for each attribute. This table is seeded on install orupgrade. The primary key is ATTRIBUTE_NAME.

MTL_ITEM_TEMPL_ATTRIBUTESMTL_ITEM_TEMPL_ATTRIBUTES stores the attributes and attribute valuesfor a template. When a template is created, a row is inserted for each availableitem attribute. When the template is applied to an item, the enabled attributevalues are propagated to the item. The primary key is TEMPLATE_ID,ATTRIBUTE_NAME.

MTL_ITEM_STATUSMTL_ITEM_STATUS is the definition table for a material status code. Thestatus code is a required item attribute and indicates the item status (forexample, active, pending, or obsolete). You may define as many additionalstatus codes as you want. The values of the individual status attributes



associated with an item status are stored inMTL_STATUS_ATTRIBUTE_VALUES. The primary key isINVENTORY_ITEM_STATUS_CODE.

MTL_ITEM_TEMPLATESMTL_ITEM_TEMPLATES is the definition table for item templates. Itcontains the user-defined name and description. When the template is applied toan item, the enabled item attributes are propagated to the item. The primary keyis TEMPLATE_ID.

MTL_STATUS_ATTRIBUTE_VALUESMTL_STATUS_ATTRIBUTE_VALUES stores the attribute values associatedwith an item status code. One record is created for each of the function-enablingattributes for each defined item status code. The primary key isINVENTORY_ITEM_STATUS_CODE, ATTRIBUTE_NAME.




Defining Items


Defining Items

Item Template (M1)Item Template (M1)

When you apply a template to an item, youoverlay or default in the set of attribute values tothe item definition. You can apply the same ordifferent templates to an item multiple times.

(N) Inventory > Setup > Items > Templates



Degree of Item Control


Degree of Item Control

No control?

Credit card orpetty cash

Supplier control?

POs/suppliers

no item #’s

Item liston-hand

Defined

expense items

Defined

stock items



Oracle Inventory Item Controls


Oracle Inventory Item Controls

MTL_LOT_NUMBERS MTL_SERIAL_NUMBERS MTL_ITEM_REVISIONS

MTL_SYSTEM_ITEMS_B


MTL_ITEM_REVISIONSMTL_ITEM_REVISIONS stores revision levels for an inventory item. When anitem is defined, a starting revision record is written out to the table; every itemwill have at least one revision. The primary key is INVENTORY_ITEM_ID,ORGANIZATION_ID, REVISION.

MTL_SERIAL_NUMBERSMTL_SERIAL_NUMBERS stores the definition and current status of all serialnumbers in Oracle Inventory. These serial numbers are also used in other areasof Oracle Manufacturing applications.A serial number can have one of four statuses:

• Defined, but not used• Resides in stores• Issued out of stores• Resides in transit



The primary key is INVENTORY_ID, SERIAL_NUMBER,CURRENT_ORGANIZATION_ID.

MTL_LOT_NUMBERSMTL_LOT_NUMBERS stores the definition and expiration date of all lotnumbers in inventory. A lot number can exist in more than one organization orfor different items. The primary key is INVENTORY_ITEM_ID,ORGANIZATION_ID, LOT_NUMBER.



Defining Item Controls


Defining Item Controls

You can choose between centralized anddecentralized control of item attributes. Definingattribute controls does not determine the value ofan attribute, only the level at which it iscontrolled.

Item Attribute ControlsItem Attribute Controls

(N) Inventory > Setup > Items > Attribute Controls



Oracle Inventory Item Status


Oracle Inventory Item Status

MTL_ITEM_ATTRIBUTES

MTL_STATUS_ATTRIBUTE_VALUES

MTL_ITEM_STATUSMTL_SYSTEM_ITEMS_B

MTL_PENDING_ITEM_STATUS


MTL_ITEM_ATTRIBUTESMTL_ITEM_ATTRIBUTES stores the item attributes, their user-friendlynames if the attribute is maintained at the item or item/organization level, if theattribute is controlled by an item’s status, and the kind of validation required foreach attribute. This table is seeded on install or upgrade. The top eight itemattributes are as follows:

1 Stockable2 Transactable3 BOM allowed4 WIP allowed5 Purchasable6 OE Orderable7 Internal Orderable8 Billable

The primary key is ATTRIBUTE_NAME.



MTL_STATUS_ATTRIBUTE_VALUESMTL_STATUS_ATTRIBUTE_VALUES stores the attribute values associatedwith an item status code. One record is created for each of the function-enablingattributes for each defined item status code. The primary key isINVENTORY_ITEM_STATUS_CODE, ATTRIBUTE_NAME.

MTL_ITEM_STATUSMTL_ITEM_STATUS is the definition table for a material status code. Thestatus code is a required item attribute and indicates the item status (forexample, active, pending, or obsolete). You may define as many additionalstatus codes as you want. The values of the individual status attributesassociated with an item’s status are stored inMTL_STATUS_ATTRIBUTE_VALUES. The primary key isINVENTORY_ITEM_STATUS_CODE.

MTL_PENDING_ITEM_STATUSMTL_PENDING_ITEM_STATUS is used to define and store the history of theitem statuses that have been or will be assigned to an item. This table maintainsthe status history for each item. This table also stores pending statusinformation. The primary key is INVENTORY_ITEM_ID,ORGANIZATION_ID, STATUS_CODE, EFFECTIVE_DATE.



Life Cycle of a Part: Using Item Status and Attributes


Life Cycle of a Part:Using Item Status and Attributes

1. Stock1. Stock2. Trans2. Trans

3. BOM3. BOM

4. WIP4. WIP5.5. Pur Pur

6. OE6. OE

7. Intern7. Intern8. Bill8. Bill

Prototype Ramp Up Live Ramp Down ObsoletePrototype Ramp Up Live Ramp Down Obsolete

N N Y Y Y Y Y Y N N N N Y Y Y Y Y Y N N

Y Y Y Y Y Y Y Y Y Y N N Y Y Y Y N N N N

N N Y Y Y Y N N N N

N N N N Y Y Y Y N N

N N N N Y Y Y Y N N

N N N N Y Y Y Y N N

Life Cycle of a PartThis graph depicts the usage of MTL_ITEM_STATUS andMTL_ITEM_ATTRIBUTES to indicate the stages an item (or part) may gothrough in its life cycle. For example: If a part is still in the prototype stage, itwill not be stockable (1 Stock) or there will be no transaction activity allowed(2. Trans). However, it will be defined in the bill of material (3. BOM) in orderto build the prototype part originally. The remaining categories illustrate thefollowing:5. Pur—part cannot be purchased6. OE—part cannot be ordered7. Intern—part cannot be ordered internally8. Bill—part cannot be invoiced



Defining Item Status Codes


Defining Item Status Codes

You can use statuses to provide default values forcertain item attributes to control the functionalityof an item. When you update the values for astatus, all items to which it is assigned are alsoupdated.

Item StatusItem Status

(N) Inventory > Setup > Items > Status Codes



Item Categories Example


Item CategoriesExample

ItemItem TypeType Country of OriginCountry of Origin SizeSizex1x1 steelsteel U.S.U.S. bigbig

x2x2 wirewire CanadaCanada mediummedium

x3x3 steelsteel CanadaCanada smallsmallx4x4 office supplies office supplies U.S.U.S. bigbig

CategoriesCategories

Category SetCategory Set

Category Sets and CategoriesThere are an infinite number of categories for any item.



Oracle Inventory: Item Categories


Oracle Inventory: Item Categories

MTL_ITEM_CATEGORIES MTL_SYSTEM_ITEMS_B

MTL_CATEGORIES_B

MTL_CATEGORY_SET_VALID_CATS

FND_ID_FLEX_STRUCTURES

MTL_CATEGORY_SETS_B

MTL_DEFAULT_CATEGORY_SETS

MTL_CATEGORIES_TL MTL_CATEGORY_SETS_TL


FND_ID_FLEX_STRUCTURESFND_ID_FLEX_STRUCTURES stores structure information about keyflexfields. The primary key is APPLICATION_ID, ID_FLEX_CODE,ID_FLEX_NUM.

MTL_CATEGORIES_BMTL_CATEGORIES_B is the code combinations table for item categories.Items are grouped into categories within the context of a category set to provideflexible grouping schemes. The primary key is CATEGORY_ID.The item category is a key flexfield with a flexfield code of MCAT.

MTL_CATEGORIES_TLMTL_CATEGORIES_TL is a table holding translated Description column forItem Categories. The primary key is CATEGORY_ID, LANGUAGE.

MTL_CATEGORY_SETS_BMTL_CATEGORY_SETS_B contains the entity definition for category sets. Acategory set is a categorization scheme for a group of items. Items can be



assigned to different categories in different category sets, but can be assigned toonly one category within a category set. The primary key isCATEGORY_SET_ID.

MTL_CATEGORY_SETS_TLMTL_CATEGORY_SETS_TL is a table holding translated Name andDescription columns for Category Sets. The primary key isCATEGORY_SET_ID, LANGUAGE.

MTL_CATEGORY_SET_VALID_CATSMTL_CATEGORY_SET_VALID_CATS defines the valid category list for aparticular category set. If category validation is required, the list of validcategories is stored in this table and is used to restrict category selection for thecategory set. The primary key is CATEGORY_SET_ID, CATEGORY_ID.

MTL_DEFAULT_CATEGORY_SETSMTL_DEFAULT_CATEGORY_SETS stores the identifier of the category setthat acts as the default for a particular functional area. This information is usedto determine the mandatory category sets for an item. It is also used to provide adefault category set for forms and reports that require a category set field valueor parameter. The primary key is FUNCTIONAL_AREA_ID,CATEGORY_SET_ID.

MTL_ITEM_CATEGORIESMTL_ITEM_CATEGORIES stores the item assignments to categories within acategory set. For each assignment, this table stores the item, category set, andthe category. Items can be assigned to multiple categories and category sets, butcan be assigned to only one category in a given category set.This table is populated through either the Define Item or the Update Item/OrgAttributes forms. It can also be populated by performing item assignments whena category set is defined. The primary key is INVENTORY_ITEM_ID,ORGANIZATION_ID, CATEGORY_SET_ID.



Defining Item Categories


Defining Item Categories

You can define an unlimited number of categoriesand group subsets of your categories intocategory sets. A category can belong to multiplecategory sets.

Categories

(N) Inventory > Setup > Items > Categories > Category Codes



Oracle Inventory: Item Catalogs


Oracle Inventory: Item Catalogs

MTL_DESCRIPTIVE_ELEMENTS

MTL_DESCR_ELEMENT_VALUES

MTL_ITEM_CATALOG_GROUPS

MTL_SYSTEM_ITEMS_B

MTL_ITEM_CATALOG_GROUPSMTL_ITEM_CATALOG_GROUPS is the entity table for item catalog groups.An item catalog group consists of items that can be described by the same set ofdescriptive elements or item properties. The item catalog group assignment foran item is done at the item master organization level.The item catalog group is a key flexfield. The flexfield code is MICG. Theprimary key is ITEM_CATALOG_GROUP_ID.

MTL_DESCRIPTIVE_ELEMENTSMTL_DESCRIPTIVE_ELEMENTS stores the descriptive element definitionsfor an item catalog group. Descriptive elements are defining properties used todescribe the catalog group. The primary key isITEM_CATALOG_GROUP_ID, ELEMENT_NAME.

MTL_DESCR_ELEMENT_VALUESMTL_DESCR_ELEMENT_VALUES stores the descriptive element values fora specific item. An item can only be assigned to one item catalog group and willonly have descriptive elements for a single catalog group. The primary key isINVENTORY_ITEM_ID, ELEMENT_NAME.

MTL_SYSTEM_ITEMS_BMTL_SYSTEM_ITEMS_B is the definition table for items. This table holds thedefinitions for inventory items, engineering items, and purchasing items. Theflexfield code is MSTK. The primary key for an item is theINVENTORY_ITEM_ID and the ORGANIZATION_ID. The same item could



be defined in more than one organization. Each row represents an item in anorganization.



Defining Item Catalogs


Defining Item CatalogsWhen you define descriptive elements for an itemcatalog group, you specify whether the value of aparticular descriptive element can beconcatenated and used as an item's description.When you assign an item to a catalog group, youchoose descriptive elements that apply to theitem, and assign values to the descriptiveelements.

Item Catalog GroupsItem Catalog Groups

(N) Inventory > Setup > Items > Catalog Groups



Practice 1 Setup


Practice 1 Setup

1 Create seven items of the following variety:– Planning Item (Quantity 1)– Finished Goods (Quantity 2)– Purchased Items (Quantity 4)

2 Verify items for the correct template andorganization assignment.

Setup InstructionsCreate Seven Items1. Navigate to the Master Item form.(N) Inventory > Items > Master Items (note: select M1-Seattle Manufacturing asyour default)

• Name the item and fill in the description (note: item number is casesensitive).

• Apply the Item Template for each item as shown in the example tablebelow.[M]Tools > Copy From

• Select the correct template for each item from list of values, and Click theDone button.

• Assign Unit of Measure as shown in the example table below.• Select the Lead Time tab and enter 2 for processing lead time.• Save your work.

[M]Tools > Organization Assignment• Assign Item to the M1-Seattle Manufacturing organization.• Save your work.• Repeat step 1for the additional six items, substituting the appropriate

Template for each.Example:



Item Template Used UOM##-salsa Planning Item Each##-hot Finished Good Each##-mild Finished Good Each##-habanero Purchase Item Ounce##-jalapeno Purchase Item Ounce##-garlic Purchase Item Ounce##-tomato Purchase Item Ounce

Verify Items for Correct Template and Organization Assignment2. Navigate to the Find Organization Items form.(N) Inventory > Items > Organization Items (Ensure you are in the M1organization)

• Find your item numbers.• Select the Bill of Material tab.• Ensure each item has the BOM ALLOWED box checked.



Practice 1


Practice 1

Find your items, their descriptions, and determine thevalues of the eight Item Attributes that make up theItem Status Code.


• Tables: mtl_system_items, mtl_parameters• Keys: segmentl, organization_code, organization_id• Columns: purchasing_item_flag, internal_order_enabled_flag,

customer_order_enabled_flag, stock_enabled_flag, bom_enabled_flag,build_in_wip_flag, mtl_transactions_enabled_flag, invoiceable_item_flag



Practice 1 Solution


Practice 1 Solution

Find your items, their descriptions, and determine thevalues of the eight Item Attributes that make up theItem Status Code.


• substr(inv.segment1,1,15) “Item”,• substr(inv.description,1,20) “Description”,• inv.purchasing_item_flag,• inv.customer_order_enabled_flag,• inv.internal_order_enabled_flag,• inv.stock_enabled_flag,• inv.bom_enabled_flag,• inv.build_in_wip_flag,• inv.mtl_transactions_enabled_flag,• inv.invoiceable_item_flag

FROM• mtl_system_items inv,• mtl_parameters org

WHERE• inv.segment1 LIKE ‘&Item%’ AND• org.organization_code LIKE ‘&OrgCode%’ AND• org.organization_id = inv.organization_id



Agenda


Agenda




Oracle Inventory Transaction Flow


Oracle Inventory Transaction Flow

TXN processor

RCV processor

RCV_TRANSACTIONS_

INTERFACE

TXNworker

Cost processor

MTL_TRANSACTIONS_

INTERFACE

MTL_MATERIAL_TRANSACTIONS_

TEMP

MTL_MATERIAL_

TRANSACTIONS

MTL_TRANSACTION_

ACCOUNTS

Order entry Inventory,WIP Receiving

MTL_TRANSACTIONS_INTERFACEThis is the interface point between non-Inventory applications and the Inventorytransaction module.The Transaction Manager concurrent program polls this table at a user-specifiedprocess interval and submits the transaction workers to process them.Processing consists of data derivation, validation, and transfer of records fromMTL_TRANSACTIONS_INTERFACE,MTL_TRANSACTION_LOTS_INTERFACE, andMTL_SERIAL_NUMBERS_INTERFACE into their respective TEMP tables,from where they are processed by the transaction processor.MTL_MATERIAL_TRANSACTIONS_TEMPThis table is the gateway for all material transactions. Records are processedfrom this table into Inventory through the transaction processor. All Inventorytransaction forms write directly to this table. Outside applications must writetransaction records to MTL_TRANSACTSIONS_INTERFACE to be processedthrough MTL_MATERIAL_TRANSACTIONS_TEMP and the transactionprocessor by the Transaction Worker concurrent program.MTL_MATERIAL_TRANSACTIONSThis table stores a record of every material transaction or cost update performedin Inventory.Records are inserted into this table either through the transaction processor orby the standard cost program. The primary key is TRANSACTION_ID.MTL_TRANSACTION_ACCOUNTS



This table holds the accounting information for each material transaction inMTL_MATERIAL_TRANSACTIONS. Oracle Inventory uses this informationto track the financial impact of your quantity moves.Instructor NoteThere is no primary key for this table in the TRM.



Oracle Inventory: Inventory Transactions and ItemControls


Oracle Inventory:Inventory Transactions and Item Controls

MTL_UNIT_TRANSACTIONS


MTL_SYSTEM_ITEMS_B

MTL_TRANSACTION_LOT_NUMBERS

MTL_ITEM_REVISIONS

MTL_SERIAL_NUMBERS MTL_LOT_NUMBERS

MTL_UNIT_TRANSACTIONSMTL_UNIT_TRANSACTIONS stores a record of every material transaction ofa serialized unit in Oracle Inventory. Records are inserted into this table throughthe transaction processor. The primary key is TRANSACTION_ID,SERIAL_NUMBER.MTL_SERIAL_NUMBERSMTL_SERIAL_NUMBERS stores the definition and current status of all serialnumbers in Oracle Inventory. These serial numbers are also used in other areasof Oracle Manufacturing applications. The primary key isINVENTORY_ITEM_ID, SERIAL_NUMBER,CURRENT_ORGANIZATION_ID.MTL_TRANSACTION_LOT_NUMBERSMTL_TRANSACTION_LOT_NUMBERS stores lot number information fortransactions in the MTL_MATERIAL_TRANSACTIONS table. The primarykey is TRANSACTION_ID, LOT_NUMBER.MTL_LOT_NUMBERSMTL_LOT_NUMBERS stores the definition and expiration date of all lotnumbers in Oracle Inventory. The primary key is INVNETORY_ITEM_ID,ORGANIZATION_ID, LOT_NUMBER.MTL_ITEM_REVISIONS



MTL_ITEM_REVISIONS stores the revision levels for an inventory item.When an item is defined, a starting revision record is written to this table so thatevery item has at least one revision. The primary key isINVENTORY_ITEM_ID, ORGANIZATION_ID, REVISION.MTL_SYSTEM_ITEMS_BMTL_SYSTEM_ITEMS_B is the definition table for items. This table holds thedefinitions for inventory items, engineering items, and purchasing items. Theprimary key for an item is the INVENTORY_ITEM_ID and theORGANIZATION_ID.



Physical Inventory Process


Physical Inventory ProcessDefine physical inventory

Take snapshot of on-hand quantities

Generate tags

Count items

Void tags

Approve counts

Run adjustment program

Purge physical inventory

Define physical inventory

Overview of Physical InventoryA physical inventory is a periodic reconciliation of system on-hand balanceswith physical counts in inventory. You can perform a physical inventorywhenever you choose to verify the accuracy of your system on-quantities. Thiscount can be performed for the entire organization or for particularsubinventories within an organization.



Oracle Inventory: Physical Inventory


Oracle Inventory: Physical Inventory


MTL_PHYSICAL_

ADJUSTMENTS


MTL_PHYSICAL_SUBINVENTORIES

MTL_PHYSICAL_INVENTORIES

MTL_SYSTEM_ITEMS_B

MTL_PHYSICAL_

INVENTORY_TAGS

MTL_PHYSICAL_SUBINVENTORIESMTL_PHYSICAL_SUBINVENTORIES specifies which subinventories areinvolved in a physical inventory when the physical inventory does not includeall subinventories. The primary key is ORGANIZATION_ID,PHYSICAL_INVENTORY_ID, SUBINVENTORY.

MTL_SECONDARY_INVENTORIESMTL_SECONDARY_INVENTORIES is the definition table for thesubinventory. Subinventories are assigned to items, indicating a list of validplaces in which this item is located. The primary key isSECONDARY_INVENTORY_NAME, ORGANIZATION_ID.

MTL_PHYSICAL_INVENTORY_TAGSMTL_PHYSICAL_INVENTORY_TAGS stores information regarding physicalinventory tags, including tag number, SKU information, tag quantity, and apointer to the corresponding adjustment inMTL_PHYSICAL_ADJUSTMENTS. A change to this table can require achange to MTL_PHYSICAL_ADJUSTMENTS to ensure that the informationtherein remains consistent with its tags. The primary key is TAG_ID.

MTL_PHYSICAL_ADJUSTMENTSMTL_PHYSICAL_ADJUSTMENTS contains all information about theadjustment transactions, including the size of the necessary adjustment, theaccounts to which the adjustment transaction was posted, and the approvalstatus of each transaction. The primary key is ADJUSTMENT_ID.




MTL_MATERIAL_TRANSACTIONS stores a record of every materialtransaction or cost update performed in Inventory. Records are inserted into thistable either through the transaction processor or by the standard cost updateprogram. The primary key is TRANSACTION_ID.

MTL_SYSTEM_ITEMS_BMTL_SYSTEM_ITEMS_B is the definition table for items. This table holds thedefinitions for inventory items, engineering items, and purchasing items. Theprimary key for an item is the INVENTORY_ITEM_ID and theORGANIZATION_ID.



Defining Physical Inventory


Defining Physical Inventory

You can define and maintain an unlimited numberof physical inventories in Oracle Inventory. Aphysical inventory is identified by a unique nameyou assign. You use this name to identify anyactivity, such as adjustments, pertaining to thisphysical inventory.

Define Physical Inventory (M1)Define Physical Inventory (M1)

(N) Inventory > Counting > Physical Inventory > Physical Inventories



ABC Analysis Overview


ABC Analysis Overview

ComputerComputer

Item AItem A

PrinterPrinterItem BItem B

MouseMouseItem CItem C

Overview of ABC AnalysisABC Analysis is a method of determining the relative value of items in yourinventory sites. An ABC Analysis involves ranking your items according to acriterion and then grouping items into classes. ABC refers to the rankings youassign your items as a result of this analysis, where A items are more valuablethan B items, and so on.



Oracle Inventory: ABC Analysis


Oracle Inventory: ABC Analysis

MTL_ABC_ASSIGNMENTS

MTL_ABC_COMPILE_HEADERS

MTL_SYSTEM_ITEMS_B MTL_SECONDARY INVENTORIES

MTL_ABC_COMPILES

MTL_ABC_CLASSES

MTL_ABC_ASSGN_GROUP_CLASSES

MTL_ABC_ASSIGNMENT_

GROUPS

MTL_ABC_CLASSESMTL_ABC_CLASSES contains information about ABC classes. Each row inthis table defines an ABC class. An ABC class is a category under which itemswith similar metrics are put together. An ABC class can be used in more thanone ABC group, but only once within a given group. The primary key isABC_CLASS_ID.

MTL_ABC_ASSIGNMENT_GROUPSMTL_ABC_ASSIGNMENT_GROUPS contains information for ABC groups.Each row in this table defines an ABC group and is populated by the DefineABC Group table. Oracle Inventory uses this information as the basis for ABCclass assignment and item assignment. The primary key isASSIGNMENT_GROUP_ID.

MTL_ABC_ASSGN_GROUP_CLASSESMTL_ABC_ASSIGN_GROUP_CLASSES stores information about the ABCclasses assigned to an ABC group. An ABC class can be assigned to one ormore ABC groups, but can be used only once in each ABC group. The primarykey is ASSIGNMENT_GROUP_ID, ABC_CLASS_ID.

MTL_ABC_ASSIGNMENTSMTL_ABC_ASSIGNMENTS holds assignments of inventory items to ABCclasses and ABC groups. Oracle Inventory uses this information to load thecycle count process. The primary key is INVENTORY_ITEM_ID,ASSIGNMENT_GROUP_ID, ABC_CLASS_ID.

MTL_ABC_COMPILE_HEADERS



MTL_ABC_COMPILE_HEADERS contains information used for, and thatresults from, an ABC compile or an ABC analysis. It holds user-specifiedinformation, such as the current compile option and cost code chosen, theresults of an ABC analysis, the cumulative quantity, and the cumulative value.Oracle Inventory uses this information during the ABC compile process todetermine the compile criterion and attributes used for the compile. The primarykey is COMPILE_ID.

MTL_ABC_COMPILESMTL_ABC_COMPILES stores information about each item within an ABCcompiler. Each row includes an item's sequence number relative to other itemsin the given compiler, based on the criteria defined inMTL_ABC_COMPILE_HEADERS. The primary key isINVENTORY_ITEM_ID, COMPILE_ID.




Defining an ABC Compile


Defining an ABC Compile

You can define and compile an ABC analysis foryour entire organization or for a specificsubinventory within your organization.

ABC Compile (M1)

A 33

B 126

C 905

(N) Inventory > ABC Codes > ABC Compiles



Cycle Count Overview


Cycle Count OverviewDay 1 of Cycle CountDay 1 of Cycle Count

High-Value Item to CountHigh-Value Item to CountLow-Value Item to CountLow-Value Item to Count

Day 2 of Cycle CountDay 2 of Cycle Count


Day 3 of Cycle CountDay 3 of Cycle Count


Cycle CountingCycle counting is the periodic counting of individual items throughout the year.Count items of higher value more frequently than items of lower value. Performcycle counting instead of performing physical inventory. You can use bothtechniques to verify the accuracy of on-hand quantities and values.



Oracle Inventory: Cycle Count


Oracle Inventory: Cycle Count

MTL_CC_SCHED_COUNT

XREFS

MTL_CYCLE_COUNT_ENTRIES

MTL_MATERIAL_

TRANSACTIONS

MTL_CC_SCHEDULE_REQUESTS

MTL_SYSTEM_ITEMS_B

MTL_CYCLE_COUNT_ITEMS

MTL_CYCLE_COUNT_CLASSES

MTL_CYCLE_COUNT_HEADERS


MTL_CYCLE_COUNT_ITEMSMTL_CYCLE_COUNT_ITEMS stores information about all items eligible forcycle counting within the scope of a cycle count name. Oracle Inventory usesthis information to direct the cycle count scheduling process, and as a validationtable when entering manual schedule requests. The primary key isCYCLE_COUNT_HEADER_ID, INVENTORY_ITEM_ID.

MTL_CYCLE_COUNT_CLASSESMTL_CYCLE_COUNT_CLASSES stores information about cycle countclasses, such as associated cycle count name, approval tolerance limits, andminimum counting frequency. Oracle Inventory uses Cycle Count Classes as aunit for specifying and defaulting cycle count attributes. The primary key isABC_CLASS_ID, CYCLE_COUNT_HEADER_ID.

MTL_CYCLE_COUNT_HEADERSMTL_CYCLE_COUNT_HEADERS stores information about cycle countnames. Oracle Inventory uses this information to track defined cycle countnames, to indicate tolerance/approval limits, cycle count calendar and exceptionset, ABC initialization information, scheduling options, and recount options.The primary key is CYCLE_COUNT_HEADER_ID.



MTL_CC_SCHEDULE_REQUESTSMTL_CC_SCHEDULE_REQUESTS stores cycle count schedule requests.Oracle Inventory uses this information to feed the count generation process andgenerate Cycle Count Requests that show up in the Count List Reports. Theprimary key is CYCLE_COUNT_SCHEDULE_ID.

MTL_CC_SCHED_COUNT_XREFSMTL_CC_SCHED_COUNT_XREFS links cycle counts entered to the schedulerequest that generated it. Oracle Inventory uses this information to determinewhen a schedule request has been completed and to update its status. Theprimary key is CYCLE_COUNT_SCHEDULE_ID,CYCLE_COUNT_ENTRY_ID.

MTL_CYCLE_COUNT_ENTRIESMTL_CYCLE_COUNT_ENTRIES stores the actual counts of a cycle count. Arow in this table without a count is considered to be a count request. OracleInventory uses this information to determine and store cycle count adjustments,recounts, and approval requirements. The primary key isCYCLE_COUNT_ENTRY_ID.

MTL_MATERIAL_TRANSACTIONSMTL_MATERIAL_TRANSACTIONS stores a record of every materialtransaction or cost update performed in Inventory. Records are inserted into thistable either through the transaction processor or by the standard cost updateprogram. The primary key is TRANSACTION_ID.



Oracle Inventory: Demand and Reservation Information


Oracle Inventory:Demand and Reservation Information

MTL_DEMAND

MTL_SYSTEM_ITEMS_B

MTL_MATERIAL_

TRANSACTIONS

MTL_SALES_ORDERS


MTL_GENERIC_DISPOSITIONS

OE_ORDER_HEADERS_ALL

OE_ORDER_LINES_ALL

MTL_DEMAND_

INTERFACE

MTL_DEMANDMTL_DEMAND stores demand and reservation information used in Availableto Promise, Planning, and other manufacturing functions. Four row types arestored in this table:

• Summary Demand rows• Dependent Demand rows• Open Demand rows• Reservation rows

The primary key is INVENTORY_ITEM_ID, DEMAND_SOURCE_TYPE,DEMAND_SOURCE_HEADER_ID, DEMAND_SOURCE_LINE (o),DEMAND_SOURCE_DELIVERY (o), COMPONENT_SEQUENCE_ID (o).

MTL_SALES_ORDERSMTL_SALES_ORDERS stores the Oracle Inventory local definition of salesorders and maps sales orders between Oracle Inventory and other OracleManufacturing applications. The primary key is SALES_ORDER_ID.

OE_ORDER_HEADERS_ALLOE_ORDER_HEADERS_ALL stores header information for orders in OracleOrder Management. The primary key is HEADER_ID.

OE-ORDER_LINES_ALLOE_ORDER_LINES_ALL stores information for all order lines in OracleOrder Management. The primary key is LINE-ID.




This table stores valid Accounting Flexfield segment value combinations foreach accounting flexfield structure within your general ledger application.Available material can be reserved against a valid Accounting Flexfieldcombination. The primary key is CODE_COMBINATION_ID.

MTL_GENERIC_DISPOSITIONSMTL_GENERIC_DISPOSITIONS stores the user-defined account alias. Anaccount alias provides a method to use accounting numbers and makes it easierto transact account issues and receipts. Available inventory can be reservedagainst an account alias. The primary key is DISPOSITION_ID,ORGANIZATION_ID.

MTL_MATERIAL_TRANSACTIONSMTL_MATERIAL_TRANSACTIONS stores a record of every materialtransaction or cost update performed in Inventory. An issue transaction to anaccount number or account alias can relieve a reservation against the accountnumber or alias. The primary key is TRANSACTION_ID.

MTL_DEMAND_INTERFACEMTL_DEMAND_INTERFACE is the interface point between non-Inventoryapplications and the Oracle Inventory demand module. Records inserted intothis table are processed by the Demand Manager concurrent program.




Practice 2 Setup


Practice 2 Setup

1 Create several miscellaneous transactions for youritems.

2 Determine your on-hand quantities persubinventory.

Setup InstructionsCreate Miscellaneous Transactions1. Navigate to the Miscellaneous Transaction form.(N) Inventory > Transactions > Miscellaneous Transaction

• Select Miscellaneous Receipts from the list of values in the Type field.• Click Transaction Lines.• Enter your item numbers for your Purchased items (NOT Planning or

Fnished Good items).• Select a subinventory (Stores, RIP or Floor Stock) and reasonable quantity

for each item.• In the Account field, enter “%”, press the tab key and select an account

number.• Save your work.

Determine On-hand Quantities2. Navigate to the Find On-hand Quantities form.(N) Inventory > On-hand, Availability > On-hand Quantity

• Enter each item number you received and verify the on-hand quantity.



Practice 2


Practice 2

Determine your items’ on-hand quantities from thetables.


• Tables: mtl_system_items, mtl_onhand_quantities, mtl_parameters• Keys: segmentl, organization_code, organization_id, inventory_item_id• Columns: inventory_item_id, organization_id, subinventory_code, revision,

locator_id, transaction_quantity



Practice 2 Solution


Practice 2 Solution

Determine your items’ on-hand quantities from thetables.


• substr(inv.segment1,1,15) “Item Number”,• substr(onh.inventory_item_id,1,10) “Item ID”,• substr(onh.organization_id,1,6) “Org ID”,• substr(onh.subinventory_code,1,10) “SubInv”,• substr(onh.revision,1,5) “Rev”,• substr(onh.locator_id,1,8) “Locator”,• substr(onh.transaction_quantity,1,15) “Trans Quant”

FROM• mtl_system_items inv,• mtl_onhand_quantities onh,• mtl_parameters org

WHERE• inv.segment1 LIKE ‘&Item%’ AND• org.organization_code LIKE ‘&OrgCode%’ AND• org.organization_id = inv.organization_id AND• inv.inventory_item_id = onh.inventory_item_id AND• inv.organization_id = onh.organization_id



Agenda


Agenda




Oracle Applications Open Interfaces for Inventory


Oracle ApplicationsOpen Interfaces for Inventory

• Open Transaction Interface• Open Demand Interface• Open Replenishment Interface• Open Item Interface• Customer Item Interface

Oracle InventoryOpen Transaction InterfaceThis interface is used as an integration point with Oracle Order Management forshipment transactions. Oracle Order Management uses the Inventory interfaceprogram to populate the interface tables with transactions submitted through theConfirm Shipments window.Open Demand InterfaceThis interface program provides all the functions you need to interface anexternal order entry system with Oracle Inventory and Oracle Manufacturingapplications.Open Replenishment InterfaceThis allows you to load replenishment requests from external systems, such as abar-code application. Such requests may be in the form of stock-take counts orrequisition requests for subinventories in which you do not track quantities.Open Item InterfaceYou can import items from any source into Oracle Inventory and OracleEngineering using this interfaceCustomer Item InterfaceYou can import customer items and customer item cross-references into OracleInventory to achieve faster order processing and shipments.



Major Tables: Open Interfaces


Major Tables:Open Interfaces

• Transactions• Demand Interface• Replenishment

TransactionsYou can load transactions from external applications and feeder systems usingthis interface. These transactions could include sales order shipmenttransactions from an external order entry system, or they could be simplematerial issues, receipts, or transfers that are loaded from data collectiondevices.This is also used as an integration point with Oracle Order Management forshipment transactions. The Oracle Order Management Inventory Interfaceprogram populates the interface tables with transactions submitted through theShip Confirm window.

Open Demand InterfaceThis is a two-way interface that lets you have visibility as well as reservedemand that is created in external applications for forecasting, planning, andorder-promising purposes. This includes the option to automatically check ATPwhen adding demand to verify availability.

Open Replenishment InterfaceUsing this interface, you can load replenishment requests from external systemssuch as a bar-code application. Such requests may be in the form of stock-takecounts or requisition requests for subinventories in which you do not trackquantities.



Inventory Transactions Open Interface Tables


Inventory TransactionsOpen Interface Tables

Interface Data Flow Table, Table, View, or Module nameName Direction View, or Process

Transactions Inbound Table MTL_TRANSACTIONS_INTERFACE MTL_SERIAL_NUMBERS_INTERFACE MTL_TRANSACION_LOTS_INTERFACEDemand Inbound Table MTL_DEMAND_INTERFACEInterfaceReplenishment Inbound Table MTL_REPLENISH_HEADERS_INT MTL_REPLENISH_LINES_INT



Open Interfaces: Inventory Setups


Open Interfaces: Inventory Setups

• Open Item Interface• Customer Item and Customer Item Cross-Reference

Open Interface

Open Item InterfaceYou can import items from any source into Oracle Inventory and OracleEngineering using the Item Interface. This will convert inventory items fromanother inventory system, migrate assembly and component items from a legacymanufacturing system, convert purchase items from a custom purchasingsystem, and import new items from a Product Data Management package.

Customer Item and Customer Item Cross-Reference Open InterfaceToday’s manufacturing environment requires a close working relationshipbetween customers and suppliers. Suppliers must be able to react quickly totheir customer’s often-changing requirements. By cross-referencing your owninventory items with your suppliers, you can achieve faster order processing andshipments by placing orders using their internal item numbers.You can import customer items and customer item cross-references from anylegacy system into Oracle Inventory using this interface. The interface processwill ensure that the imported customer items and cross-references contain thesame detail as the items entered manually using the Customer Items andCustomer Item Cross- References windows.



Inventory Setups Open Interface Tables


Inventory Setups Open Interface Tables

Interface Name

Item

Customer Item

Customer ItemCross-Reference

Data FlowDirection

Table, View,or Process Table, View, or Module Name

Inbound

Inbound

Inbound

Table

Table

Table

MTL_SYSTEM_ITEMS_INTERFACEMTL_ITEMS_REVISIONS_INTERFACE

MTL_CI_INTERFACE

MTL_CI_XREFS_INTERFACE



Summary


Summary

In this lesson, you have learned how to relate themajor tables to inventory item definition,transactions, and open interfaces.• Organizations• Subinventories and locators• Item master• Item controls• Item status• Item category• Item catalog• ABC class• Interface tables


11i Manufacturing Functional Foundation: PurchasingChapter 8 - Page 1

11i Manufacturing FunctionalFoundation: PurchasingChapter 8



11i Manufacturing Functional Foundation: Purchasing


11i Manufacturing Functional Foundation:Purchasing



Objectives


Objectives

After completing this lesson, you should be able todo the following:• Discuss purchasing activity from requisition to

receipt of goods• Identify the major tables used in purchasing and

receiving• Run a query in SQL*Plus against the appropriate

database tables to review a purchase order andreceipt for a given item

• Discuss the open interfaces for purchasing

Lesson AimThe aim of this lesson is to provide the student an overview of the flow ofpurchasing activity from the requisition stage to the receipt stage and discuss thedatabase tables that are populated as a result of these activities.Instructor NoteThe primary key for each of the ERD tables is in each table definition in theNotes section of the slides. Example: ‘The primary key is INVENTORY_ID,ORGANIZATION_ID’, where there are two elements that make up the primarykey. Some _INTERFACE and _TEMP names may not have a primary keyassociated with it.An “(o)” following a primary key name indicates that element to be optional.Example: ‘WIP_ENTITY_ID, OPERATION_SEQ_NUM,REPETITIVE_SCHEDULE_ID (o)’. In this example it indicates that theREPETITIVE_SCHEDULE_ID is part of the primary key when you referencespecific Repetitive schedules tables and not part of the primary key when youreference Discrete job tables.



Agenda


Agenda

• Overview• Entity Relationship Diagrams (ERDs)• Open interfaces



Agenda


Agenda




Oracle Purchasing Overview


Oracle Purchasing Overview

RequisitionRequisitionpoolpool

Receive against POReceive against PO Match invoices in PayablesMatch invoices in Payables

AutoCreateAutoCreate

Maintain documentsMaintain documents

Accept Revise Control

POPO

ManuallyManuallycreatecreate

ApproveApprove

DescriptionOracle Purchasing is a comprehensive procurement solution, designed to reduceadministration costs while focusing on value analysis, strategic supply basemanagement, and contract negotiation.

Requisitioning• Replace paper processing with online requisition generation, purchase order

creation, and document approval.• Regulate document access, control or modification activity, and approval

based on organizational signature and security policies.• Minimize data entry time with time-saving templates, express processing

functions, and default infrastructures.Purchasing

• Control purchasing activity and enable accurate automatic pricing using anapproved supplier list.

• Consolidate purchase requirements from multiple warehouses, plants, orlocations.

ReceivingReceive production items, Maintenance, Receipt and Overhead (MRO) items,and services using a common flexible receiving process.

Business Communication• Facilitate communication between requesters, buyers, receiving staff, and

accounts payable staff using online inquiries and notes.



• Provide access to purchasing information to related functions (marketing,finance, legal, master scheduling, inventory management, production, costaccounting, or customer order entry) on an optional basis.

• Manage historical data.



Purchasing Process Flow


Purchasing Process Flow

Requisition

RFQ

QuoteBlanket

POContractPO

Blanket PORelease

StandardPO

Purchasing OverviewA requisition is generated either manually or by the system, which is ultimatelyturned into a purchase order by the buyer. Sometimes the buyer decides aRequest for Quotation (RFQ) is required by other suppliers to determine thebest price for the goods or services requested. Once the quote is received back,that information is used to finalize the purchase order.



Agenda


Agenda




Oracle Purchasing: Entity Relationships


Oracle Purchasing: Entity Relationships

RCV_SHIPMENT_HEADERS

PO_VENDOR_SITES_ALL

PO_HEADERS_ALL

PO-VENDORS

PO_LINES_ALL

RCV_SHIPMENT_LINES

RCV_TRANSACTIONS

PO_VENDORSThis table stores information about your suppliers. Oracle Purchasing uses thisinformation to determine active suppliers. The primary key is VENDOR_ID.

RCV_SHIPMENT_HEADERSThis table stores common information about the source of your receipts orexpected receipts. You group your receipts by the source type and the source ofthe receipt. Oracle Purchasing does not allow you to group receipts fromdifferent sources under one receipt header. The primary key isSHIPMENT_HEADER_ID.

PO_VENDOR_SITES_ALLThis table stores information about supplier sites. Oracle Purchasing uses thisinformation to store supplier address information. The primary key isVENDOR_SITE_ID.

RCV_SHIPMENT_LINESThis table stores information about items that have been shipped or receivedfrom a specific receipt source. This table also stores information about thedefault destination for in-transit shipments. The primary key isSHIPMENT_LINE_ID.

PO_HEADERS_ALLPO_HEADERS_ALL contains information for your purchasing documents.Each row contains buyer information, supplier information, notes, foreigncurrency information, terms and conditions information, and the document



status. Oracle Purchasing uses this information to record information related toa complete document. The primary key is PO-HEADER_ID.

RCV_TRANSACTIONSThis table stores historical information about receiving transactions that youhave performed. When you enter a receiving transaction and the receivingtransaction processor processes your transaction, the transaction is recorded inthis table.Once a row has been inserted into this table, it will never be updated. When youcorrect a transaction, the net transaction quantity is maintained inRCV_SUPPLY. The original transaction does not get updated. You can onlydelete rows from this table using the Purge feature of Oracle Purchasing. Theprimary key is TRANSACTION_ID.

PO_LINES_ALLPO_LINES_ALL stores current information about each purchase order line.You need one row for each line you attach to a document. Each row includesthe line number, item number and category unit, price, tax information, andquantity ordered for the line. Oracle Purchasing uses this information to recordand update item and price information for purchase orders, quotations, andRFQs. The primary key is PO_LINE_ID.



Suppliers


Suppliers

PO_VENDORS

PO_VENDOR_SITES_ALL

PO_VENDOR_CONTACTS

HR_EMPLOYEES

PO_VENDORSThis table stores information about your suppliers. Oracle Purchasing uses thisinformation to determine active suppliers. The primary key is VENDOR_ID.

HR_EMPLOYEESHR_EMPLOYEES is a view that contains information about employees. Youmust have a row for each requestor, requisition preparer, approver, buyer, orreceiver who uses Oracle Purchasing. The primary key is EMPLOYEE_ID (o).

PO_VENDOR_SITES_ALLThis table stores information about supplier sites. Oracle Purchasing uses thisinformation to store supplier address information. The primary key isVENDOR_SITE_ID.

PO_VENDOR_CONTACTSThis table stores information about supplier site contacts. The primary key isVENDOR_CONTACT_ID.



Suppliers Window


Suppliers Window

Suppliers (Vision Operations)Suppliers (Vision Operations)

You can set up suppliers in the Supplierswindow to record information about individualsand companies from whom you purchasegoods and services.

(N) Purchasing > Supply Base > Suppliers



Oracle Purchasing: Requisitions


Oracle Purchasing: Requisitions

PO_REQUISITION_HEADERS_ALL

PO_REQUISITION_LINES_ALL

PO_REQ_DISTRIBUTIONS_ALL

HR_EMPLOYEES

MTL_SYSTEM_ITEMS_B


PO_REQUISITION_HEADERS_ALLPO_REQUISITION_HEADERS_ALL stores information about requisitionheaders. Each row contains the requisition number, preparer status, anddescription. It is one of three tables that stores requisition information. Theprimary key is REQUISITION_HEADER_ID.

HR_EMPLOYEESHR_EMPLOYEES is a view that contains information about employees. Youmust have a row for each requestor, requisition preparer, approver, buyer, orreceiver who uses Oracle Purchasing. The primary key is EMPLOYEE_ID (o).

PO_REQUISITION_LINES_ALLThis table stores information about requisition lines. Each row contains the linenumber, item number, item category, item description, need-by date, deliver-tolocation, item quantities, units, prices, requestor, notes, and suggested supplierinformation for the requisition line. This table is one of three tables that storesrequisition information. The primary key is REQUISITION_LINE_ID.

MTL_SYSTEM_ITEMS_BMTL_SYSTEM_ITEMS_B is the definition table for items. This table holds thedefinitions for inventory items, engineering items, and purchasing items. Theprimary key is INVENTORY_ITEM_ID, ORGANIZATION_ID.

PO_REQ_DISTRIBUTIONS_ALLPO_REQ_DISTRIBUTIONS_ALL stores information about the accountingdistributions associated with each requisition line. Each requisition line musthave at least one accounting distribution. Each row includes the Accounting



Flexfield ID and requisition line quantity. This table is one of three tables thatstores requisition information. The primary key is DISTRIBUTION_ID.

GL_CODE_COMBINATIONSThis table stores valid Accounting Flexfield segment value combinations foreach accounting flexfield structure within your general ledger application.GL_CODE_COMBINATIONS is populated by the system when a newaccounting flexfield combination is used, either through dynamic insertion ormanually.This table references the CODE_COMBINATION_ID, which is the foreign keyused throughout Oracle Applications when tracking an accounting flexfieldcombination. The primary key is CODE_COMBINATION_ID.



Requisitions Window


Requisitions Window

With on-line requisitions, you can centralize yourpurchasing department, source your requisitionswith the best suppliers, and ensure that youobtain the appropriate management approvalbefore creating purchase orders from requisitions.

Requisitions (Vision Operations)

requisition

(N) Purchasing > Requisitions > Requisitions



Purchasing Documents


Purchasing Documents

• Standard purchase orders• Contract purchase orders• Blanket purchase orders• Planned purchase orders

Purchasing Documents OverviewStandard Purchase OrdersYou generally create standard purchase orders for one-time purchase of variousitems. You create standard purchase orders when you know the details of thegoods or services you require. Each standard purchase order line can havemultiple shipments, and you can distribute the quantity of each shipment acrossmultiple accounts.Contract Purchase OrdersA contract purchase agreement is an agreement between you and a supplier forunspecified goods or services. This agreement may include terms andconditions, committed amount, and effective and expiration dates.Blanket Purchase OrdersWith blanket purchase agreements and releases, you can negotiate a stable,long-term contract while maintaining flexible delivery schedules and orderquantity commitments. You create blanket purchase agreements when youknow the details of the goods or services you plan to buy from a specificsupplier in a period, but you do not yet know the detail of your deliveryschedules.Planned Purchase OrdersYou create a planned purchase order when you want to establish a long-termagreement with a single supplier to buy goods or services. Planned purchaseorders include tentative delivery schedules and accounting distributions. You



schedule releases against the planned purchase order to actually order the goodsor services.



Oracle Purchasing: Purchasing Documents


Oracle Purchasing: Purchasing Documents

PO_RELEASES_ALL

PO_LINE_LOCATIONS_ALL

PO_HEADERS_ALL

PO_LINES_ALL

PO_DISTRIBUTIONS_ALL


PO_HEADERS_ALLPO_HEADERS_ALL contains information for your purchasing documents.Each row contains buyer information, supplier information, notes, foreigncurrency information, terms and conditions information, and the documentstatus. Oracle Purchasing uses this information to record information related toa complete document. The primary key is PO-HEADER_ID.

PO_LINES_ALLPO_LINES_ALL stores current information about each purchase order line.You need one row for each line you attach to a document. Each row includesthe line number, item number and category unit, price, tax information, andquantity ordered for the line. Oracle Purchasing uses this information to recordand update item and price information for purchase orders, quotations, andRFQs. The primary key is PO_LINE_ID.

PO_LINE_LOCATIONS_ALLThis table contains information about purchase order shipment schedules andblanket agreement price breaks. You must have one row for each schedule orprice break you attach to a document line. Each row contains the location,quantity, and dates for each shipment schedule. Oracle Purchasing uses thisinformation to record delivery schedule information for purchase orders andprice break information for blanket purchase orders, quotations, and RFQs. Theprimary key is LINE_LOCATION_ID.




PO_DISTRIBUTIONS_ALL contains accounting information for a purchaseorder shipment line. Oracle Purchasing uses this information to recordaccounting and requisition information for purchase orders and releases. It isone of five tables that stores purchase orders and releases. The primary key isPO_DISTRIBUTION_ID.

PO_RELEASES_ALLThis table contains information about blanket and planned purchase orderreleases. You need one row for each release you issue for a blanket or plannedpurchase order. Each row includes the buyer, date, release status, and releasenumber. Each release must have at least one purchase order shipment(PO_LINE_LOCATIONS_ALL). The primary key is PO_RELEASE_ID.



Purchase Orders Window


Purchase Orders Window

Purchase Orders (Vision Operations)

purchase

order

Purchasing provides the Purchase Orders windowthat you can use to enter Standard and Plannedpurchase orders as well as to enter Blanket andContract purchase agreements.

(N) Purchasing > Purchase Orders > Purchase Orders



Receiving


Receiving


RCV_SHIPMENT_HEADERS

MTL_SYSTEM_ITEMS_B

RCV_SHIPMENT_LINES

RCV_TRANSACTIONS

RCV_SUPPLY


PO_LINE_LOCATIONS_ALL

RCV_SHIPMENT_HEADERSThis table stores common information about the source of your receipts orexpected receipts. You group your receipts by the source type and the source ofthe receipt. Oracle Purchasing does not allow you to group receipts fromdifferent sources under one receipt header. The primary key isSHIPMENT_HEADER_ID.

RCV_SHIPMENT_LINESThis table stores information about items that have been shipped or receivedfrom a specific receipt source. It also stores information about the defaultdestination for in-transit shipments. The primary key is SHIPMENT_LINE_ID.

PO_LINE_LOCATIONS_ALLThis table contains information about purchase order shipment schedules andblanket agreement price breaks. You must have one row for each schedule orprice break you attach to a document line. Each row contains the location,quantity, and dates for each shipment schedule. Oracle Purchasing uses thisinformation to record delivery schedule information for purchase orders, andprice break information for blanket purchase orders, quotations, and RFQs. Theprimary key is LINE_LOCATION_ID.

RCV_TRANSACTIONSThis table stores historical information about receiving transactions you haveperformed. Once a row is inserted into this table, it will never be updated. Whenyou correct a transaction, the net transaction quantity is maintained inRCV_SUPPLY. The original transaction quantity is not updated. You can delete



rows from this table using the purge feature of Oracle Purchasing. The primarycode is TRANSACTION_ID.

MTL_MATERIAL_TRANSACTIONSMTL_MATERIAL_TRANSACTIONS stores a record of every materialtransaction or cost update performed in Oracle Inventory. Records are insertedinto this table either through the transaction processor or by the standard costupdate program. The primary key is TRANSACTION_ID.


PO_DISTRIBUTIONS_ALLPO_DISTRIBUTIONS_ALL contains accounting information for a purchaseorder shipment line. Oracle Purchasing uses this information to recordaccounting and requisition information for purchase orders and releases. It isone of five tables that stores purchase orders and releases. The primary key isPO_DISTRIBUTION_ID.

RCV_SUPPLYThis table stores information about on-hand quantities in receiving andinspection. Oracle Purchasing uses the table to track item, quantity, location andsource information for each receiving transaction. The primary key isSUPPLY_TYPE_CODE, SUPPLY_SOURCE_ID.



Receiving Transactions


Receiving Transactions

One of the many receiving transactions is thereceipt. With the receipt you can display thesupplier shipments and inter-organizationshipments corresponding to your search criteria.You can receive goods into a receiving location orto their final destination.

Receipts (M1)

(N) Purchasing > Receiving > Receipts



Practice 1 Setup


Practice 1 Setup

1 Find your item purchase requisitions from theplanned orders you released from the Planner’sWorkbench.

2 Create a manual requisition if you do not find anyrequisitions in the summary form.

3 Create a purchase order from one of therequisitions.

Setup Instructions1 Navigate to the Requisition Summary Window(N) Purchasing > Requisitions > Requisitions Summary

– Enter the item number in the “Item, Rev” field for one of your releasedorders

– Note the requisition number, go to step 3– If you do not find your requisition, go to step 2

2 Create a manual requisition(N) Purchasing > Requisitions > Requisitions

– Click in the Item field and enter one of your purchased item numbers,Click the tab key

– Scroll or tab horizontally to fill in the Quantity, Price (less than $10.00)and Need-By date (use LOV) fields

– Save your work– Click the Approve button– Click OK to Submit for Approval– Click the OK button after the submitted window appears– Repeat step 1 above

3 Create a purchase order(N) > Purchasing > Autocreate



– Clear the form with the Clear button (if a field remains, click in it andselect the blank to clear it)

– Search for your requisition by requisition number “Ctrl-Click” the lineyou wish to create (it will highlight blue/green)

– Click the Automatic button– In the New Document form, select Advantage Corp from the LOV– If the Supplier Site field is blank, select the US site from the LOV– Click the Create button– Record your document number (the PO number) from the dialog box

that appears, then click OK– If a window for new search criteria opens, click OK– In the AutoCreate PO form, Click the “Approv…” button (if additional

information is needed, use LOV in that field to select it)– In the Approve Document form, Click “OK” (this will take a little while

so take a short stretch break)



Practice 1


Practice 1

For each purchase order line, find the quantity of theitems that you ordered.


• Tables: po_lines_all, po_line_locations_all, mtl_system_items_b• Keys: segment1, organization_id, item_id, po_line_id, inventory_item_id• Columns: segment1, item_description, quantity



Practice 1 Solution


Practice 1 Solution

For each purchase order line, find the quantity of theitems that you ordered.


• substr(inv.segment1,1,10) “Item”,• substr(po.item_description,1,30) “Description”,• substr(ln.quantity,1,10) “Quantity”

FROM• po_lines_all po,• po_line_locations_all ln,• mtl_system_items_b inv

WHERE• inv.segment1 LIKE ‘&Item%’ AND• inv.organization_id = 207 AND• po.item_id = inv.inventory_item_id AND• ln.po_line_id = po.po_line_id



Agenda


Agenda




Purchasing Open Interfaces


Purchasing Open Interfaces

• Open Requisitions Interface• Purchasing Documents Open Interface• Receiving Open Interface

Oracle PurchasingOpen Requisitions InterfaceYou can automatically import requisitions from other Oracle applications orother systems using this interface. This allows you to integrate your OraclePurchasing application with new or existing applications, such as materialrequirements planning, inventory management, and production control systems.Your Oracle Purchasing application automatically validates your data andimports your requisitions. You can import requisitions as often as you want.Then, you can review these requisitions, approve or reserve funds for them ifnecessary, and place them on purchase orders or internal sales orders.Purchasing Documents Open InterfaceYou can automatically import and update standard purchase orders, price/salescatalog information, and responses to request for quotations (RFQs) fromsuppliers through this interface. The Purchasing Documents Open Interface usesthe Applications Program Interfaces (APIs) to process document data in theOracle Applications interface table to ensure that it is valid before importing itinto Oracle Purchasing. After the data is validated, the program converts theinformation in the interface table into the into the appropriate document inPurchasing.Receiving Open InterfaceYou can automatically import receipt information from other Oracleapplications or other systems using the Receiving Open Interface. This interfacelets you integrate your Oracle Purchasing application with new or existing



applications. For example, you can load bar-coded and other receivinginformation from scanners and radio frequency devices, and the ReceivingOpen Interface validates the integrity of the new data before updatingPurchasing and Inventory. Advance shipment notices sent from suppliers arealso validated in the Receiving Open Interface.



Purchasing Open Interface Tables


Purchasing Open Interface Tables


Requisitions Inbound Table PO_REQUISITIONS_INTERFACE_ALL PO_REQ_DIST_INTERFACE_ALL

Purchasing Inbound Table PO_HEADERS_INTERFACEDocuments PO_LINES_INTERFACEReceiving Inbound Table RCV_HEADERS_INTERFACE RCV_TRANSACTIONS_INTERFACE



Summary


Summary

In this lesson, you have learned how to relate themajor tables to purchasing and receivingtransactions:• Suppliers• Requisitions• Purchasing documents• Delivery and receipt• Open interfaces


11i Manufacturing Functional Foundation: BOM and EngineeringChapter 9 - Page 1

11i Manufacturing FunctionalFoundation: BOM andEngineeringChapter 9



11i Manufacturing Functional Foundation: BOM andEngineering


11i Manufacturing Functional Foundation:BOM and Engineering



Objectives


Objectives

After completing this lesson, you should be able todo the following:• Discuss bill of material/engineering setup definition

activities• Identify the major tables used in a BOM definition• Run a query in SQL*Plus against the appropriate

database tables to find a particular bill of materialand its routing

Lesson AimThe aim of this lesson is to provide the student an overview of the setupdefinition process in Oracle Engineering and Bills of Material and discuss thedatabase tables that are populated as a result of the setup activity.Instructor NoteThe primary key for each of the ERD tables is in each table definition in theNotes section of the slides. Example: ‘The primary key is INVENTORY_ID,ORGANIZATION_ID’, where there are two elements that make up the primarykey. Some _INTERFACE and _TEMP names may not have a primary keyassociated with it.An “(o)” following a primary key name indicates that element to be optional.Example: ‘WIP_ENTITY_ID, OPERATION_SEQ_NUM,REPETITIVE_SCHEDULE_ID (o)’. In this example it indicates that theREPETITIVE_SCHEDULE_ID is part of the primary key when you referencespecific Repetitive schedules tables and not part of the primary key when youreference Discrete job tables.



Agenda


Agenda

• Oracle Bills of Material• Oracle Engineering• Open interfaces



Agenda


Agenda







• The Oracle engineering products areOracle Bills of Material and OracleEngineering.

• You use Oracle Bills of Material to:– Create and maintain production bills of

materials– Create and maintain production

resources, departments, routings, andlead times

– Perform mass changes– Delete product information– Maintain the workday calendar

DescriptionOracle Bills of Material develops and maintains manufacturing bills of material(BOMs) and routings to drive planning, costing, and work-in-process tracking.

Routings• Specify department and resources usage.• Define shop floor controls.• Maintain multiple revisions of routings.• Define dynamic, lot based flow routing for operation flexibility.

Bills of Material• Define component usage, yield, and material control.• Integrate with routings for point-of-use definition.• Maintain multiple revisions of bills of material.

Lead TimeCalculate manufacturing lead time to produce goods from routing standards.

Standard CostCalculate standard costs from bills of material and routings.

Views and Reports• Perform a single-level explosion of bills of material (or fully indented

explosions).• Choose to include or exclude costs in the explosion.



• Compare two bills of material or alternative versions of the same bill ofmaterial.



Oracle Bills of Material/Engineering Bills of MaterialStructures


Oracle Bills of Material/EngineeringBills of Material Structures

BOM_BILL_OF_BOM_BILL_OF_MATERIALSMATERIALS

MTL_SYSTEM_ITEMS_B

MTL_ITEM_

LOCATIONS

BOM_OPERATION_SEQUENCES

BOM_ALTERNATE_DESIGNATORS


PRIMARYBILL

ALTERNATEBILL

MTL_ITEM_

REVISIONS

BOM_INVENTORY_

COMPONENTS

MTL_SYSTEM_ITEMS_BMTL_SYSTEM_ITEMS_B is the definition table for items. This table holds thedefinitions for inventory items, engineering items, and purchasing items. Theitem attribute BOM_ENABLED allows an item to be used in bills of material.The primary key is INVENTORY_ITEM_ID, ORGANIZATION_ID.

BOM_BILL_OF_MATERIALSBOM_BILL_OF_MATERIALS stores information about manufacturing andengineering bills of material. Each row represents a unique manufacturing orengineering bill and is defined by its primary key, BILL_SEQUENCE_ID.

BOM_ALTERNATE_DESIGNATORSBOM_ALTERNATE_DESIGNATORS stores the alternate designators used todefine alternate bills of material and routings. The primary key isALTERNATE_DESIGNATOR_CODE (o), ORGANIZATION_ID

BOM_INVENTORY_COMPONENTSBOM_INVENTORY_COMPONENTS stores information about bill of materialcomponents. COMPONENT_SEQUENCE_ID uniquely identifies each row.There is one row per component on an operation within a given date range. Theprimary key is COMPONENT_SEQUENCE_ID.




BOM_OPERATION_SEQUENCES stores information about routingoperations. You can define multiple operations for a routing. You must specifythe department in which every operation must occur.The Routing Define form prevents overlapping effective dates for the sameoperation. The primary key is OPERATION_SEQUENCE_ID.

MTL_ITEM_LOCATIONSMTL_ITEM_LOCATIONS is the definition table for stock locators. Theassociated attributes describe which subinventory this locator belongs to, whatthe locator physical capacity is, and so on. The locator is a key flexfield; theflexfield code is MTLL. The primary key is INVENTORY_LOCATION_ID,ORGANIZATION_ID.

MTL_SECONDARY_INVENTORIESMTL_SECONDARY_INVENTORIES is the definition table for thesubinventory. A subinventory is a section of inventory such as raw material orfinished goods. Subinventories are assigned to items, indicating a list of validplaces where this item will physically exist in inventory. The primary key isSECONDARY_LOCATION_NAME, ORGANIZATION_ID.

MTL_ITEM_REVISIONSMTL_ITEM_REVISIONS stores revision levels for an inventory item. When anitem is defined, a starting revision record is written out to this table, so everyitem will at least have one starting revision. The presence of an engineeringchange notice code in this table indicates that the engineering system issued therevision through the implementation process. Along with the engineeringchange order, an implementation date and initiation date will be stored. Theprimary key is INVENTORY_ITEM_ID, ORGANIZATION_ID, REVISION.



Defining a Bill of Material


Defining a Bill of Material

You can create bills of material for your parent whenentering all your component information for that bill.You can create bills of material for your parent whenentering all your component information for that bill.

Bills of Material (M1) Bills of Material (M1)

(N) Bills of Materials > Bills > Bills



Item Revision Control


Item Revision Control

As part of creating your bill of material, you can enterthe revision and effective date for that bill.

Item Revisions (M1) Item Revisions (M1)

(N) Bills of Materials > Bills > Bills (B) Revision



Oracle Bills of Material/Engineering Resources andDepartments


Oracle Bills of Material/EngineeringResources and Departments

BOM_RESOURCES

BOM_DEPARTMENTS

BOM_DEPARTMENT_

RESOURCES

BOM_RESOURCESBOM_RESOURCES stores information about material and outside processingresources. It also stores overhead, material overheads, and materialsubelements. COST_ELEMENT_ID determines the resource type. The primarykey is RESOURCE_ID.

BOM_DEPARTMENTSBOM_DEPARTMENTS stores department information. DEPARTMENT_ID isthe primary key that uniquely identifies each row. You can assign a deliverylocation for each department used, which is used with outside processingresources. The primary key is DEPARTMENT_ID.

BOM_DEPARTMENT_RESOURCESBOM_DEPARTMENT_RESOURCES stores information about resources thatyou assign to a department. You can use these resources on routing operations.The primary key is DEPARTMENT_ID, RESOURCE_ID.



Outside Processing Example


Outside ProcessingExample

AA

BB CC

Part B is sent for outside processing, and then combinedPart B is sent for outside processing, and then combinedwith Part C to make Part A.with Part C to make Part A.

Routing Steps WIP completion of Part B Completion of Step 1 signals a requisition for a purchase order for an outsideservice Receive goods back into WIP for completion



Defining a Routing


Defining a Routing

Bills of material specify the operations and theirsequence.

Routings (M1)

(N) Bills of Materials > Routings > Routings



Oracle Bills of Material/Engineering Routings


Oracle Bills of Material/EngineeringRoutings

BOM_BOM_OPERATIONAL_OPERATIONAL_

ROUTINGSROUTINGS MTL_SYSTEM_ITEMS_B


MTL_RTG_ITEM_

REVISIONS

PRIMARYROUTING

ALTERNATEROUTING

BOM_ALTERNATE_DESIGNATIONS

BOM_RESOURCES

BOM_OPERATION_RESOURCES

MTL_SYSTEM_ITEMS_BMTL_SYSTEM_ITEMS_B is the definition table for items. This table holds thedefinitions for inventory items, engineering items, and purchasing items. Theprimary key is INVENTORY_ID, ORGANIZATION_ID.

BOM_OPERATIONAL_ROUTINGSBOM_OPERATIONAL_ROUTINGS stores information about manufacturingand engineering routings. The primary key is ROUTING_SEQUENCE_ID.

BOM_ALTERNATE_DESIGNATORSBOM_ALTERNATE_DESIGNATORS stores the alternate designators you useto define alternate bills of material and routings. The primary code isALTERNATE_DESIGNATOR_CODE (o), ORGANIZATION_ID.

MTL_RTG_ITEM_REVISIONSMTL_RTG_ITEM_REVISIONS stores revision levels for routings. A revisionmust be inserted into this table when a routing is defined; every routing has atleast one valid revision. The primary key is INVENTORY_ITEM_ID,ORGANIZATION_ID, PROCESS_REVISION.

BOM_OPERATION_SEQUENCESBOM_OPERATION_SEQUENCES stores information about routingoperations. You can define multiple operations for a routing. You must specifythe department in which every operation must occur. The primary key isOPERATION_SEQUENCE_ID.

BOM_OPERATION_RESOURCES



BOM_OPERATION_RESOURCES stores information about resources yourequire to complete operations on routings. You can assign multiple resourcesor assign the same resource multiple times at any operation. The primary key isOPERATION_SEQUENCE_ID, RESOURCE_SEQ_NUM.

BOM_RESOURCESBOM_RESOURCES stores information about material and outside processingresources. It also stores overhead, material overheads, and materialsubelements. COST_ELEMENT_ID determines the resource type. The primarykey is RESOURCE_ID.



Practice 1 Setup


Practice 1 Setup

1 Using the following structure, create Bill(s) ofMaterial in M1-Seattle, using the seven items youcreated.

2 Verify your BOM using the Indented BOM form.

FG 2FG 1

PP2 PP4PP2 PP3 PP1PP1

Plan Item

Setup Instructions• Assign Planning percentages for Finished Good 1 and Finished Good 2

when constructing the Plan Item BOM.• Vary your QPAs for Purchased Parts 1 through 4 as it suits you, when

building the two finished good BOMs.• Optionally, assign yields to the purchased parts (values must be between 0

and 1).Create Bills of Material1. Navigate to the Bills of Material window.(N) Bills of Materials > Bills > Bills

• Type in the Item Number for the parent item in the single BOM. Hit theTab key. The item description will fill in automatically.

• Place the cursor in the Component Region field.• Enter the appropriate Component Item Number and hit the Tab key.• For the two Standard bills, place cursor in “Quantity” field and change

quantity per assembly (QPA) as appropriate.• Select the Component Details tab. Change the Planning Percentage for the

planning bill and yield values for the Standard bills as appropriate.• Save your work.• Repeat step 1 for the remaining BOMs.

Verify Bills of Material



2. Navigate to the Find Indented Bills form.(N) Bills of Materials > Bills > Indented Bills

• Enter your planning item number in the item field and press the Tab key.• Click the Find button.• Expand your BOM using the ‘++’ button (functions exactly like the

Navigator window).• Inspect the various tabs available.• Return to the Indented Bills form, and enter a quantity greater than 1 in the

Quantity field, check the Use Planning percentage box and re-inspect yourBOM. Click on the Quantities tab and see your allocation by planningpercentage.



Practice 1


Practice 1

For each Bill of Material, find the items and determinetheir attached components and quantities.


• Tables: mtl_system_items, bom_bill_of_materials,bom_inventory_components, mtl_system_items

• Keys: segment1, organization_id, inventory_item_id, assembly_item_id,bill_sequence_id, component_item_id

• Columns: segment1, component_quantity, segmentl



Practice 1 Solution


Practice 1 Solution

For each Bill of Material, find the items and determinetheir attached components and quantities.


• substr(iasy.segment1,1,10) “Assembly”,• substr(icmp.segment1,1,15) “Component”,• substr(comp.component_quantity,1,5) “Quant”

FROM• mtl_system_items iasy,• bom_bill_of_materials bom,• bom_inventory_components comp,• mtl_system_items icmp

WHERE• iasy.segment1 LIKE ‘&Item%’ AND• iasy.organization_id = 207 AND• iasy.inventory_item_id = bom.assembly_item_id AND• iasy.organization_id = bom.organization_id AND• bom.bill_sequence_id = comp.bill_sequence_id AND• comp.component_item_id = icmp.inventory_item_id AND• icmp.organization_id = 207



Practice 2


Practice 2

Create resources, departments and routings, in M1-Seattle, for the assemblies in your Bills of Material.

Setup InstructionsCreate Resources1. Navigate to the Resources form.(N) Bills of Materials > Routings > Resources

• Enter ##-res as your resource.• Enter a description for your resource.• Select Machine as Type.• Select HR (hour) as UOM.• Select WIP Move Charge Type.• Save your work.

Create Departments2. Navigate to Departments form.(N) Bills of Materials > Routings > Departments

• Enter ##-dep as your Department.• Enter Description for your Department.• Click Resource button.• Enter your Resource in the Resource field.• Uncheck the Available 24 Hours box.• Enter 10 in the Units field.• Select the Shifts button.



• In the Shift Number field, enter a 1.• Save your work.

Create Routings3. Navigate to the Routings form.(N) Bills of Materials > Routings > Routings

• Enter the Item Number of one of your Finished Goods in the Item field.• Enter a 10 in the Seq field in the Operations Region.• Enter your department name in the Department field.• Click the Operation Resources button.• Enter a 1 in the Seq field.• Enter your resource in Resource field from list of values.• Enter a 4 in the Usage field.• Select the Scheduling tab, enter a 5 in the Assigned Units field.• Ensure that the Schedule field is set to yes.• Repeat step 3 for your second Finished Good.



Agenda


Agenda




Oracle Engineering


Oracle Engineering

• Create and maintain engineering items• Create and maintain engineering bills of materials• Create and maintain engineering resources,

departments, routings, and lead times• Transfer engineering product information to

production• Process engineering change orders• Perform mass changes• Delete product information

DescriptionOracle Engineering interacts with other Oracle manufacturing applications toprovide a cohesive integrated business solution. Oracle Engineering helps youdefine product and process specifications. It also provides the informationrequired for effective planning and execution.

Oracle Engineering• Define engineering and manufacturing bills of material.• Define engineering and manufacturing routings.• Manage product changes with engineering change orders (ECOs).• Create new design specifications using Oracle Engineering.• Determine resource availability.• Specify detailed resource use.

Introducing New Products• Define engineering items, BOMs, and routings to prototype new product

designs.• Calculate lead times and release engineering prototypes to manufacturing.

Defining Planning Bills• Define planning bills to assist with sales strategy.• Provide BOM maintenance.

Managing Engineering Changes



• Define and implement engineering changes to prototype and productionitems.

• Schedule ECOs manually with imbedded workflow, or to correspond to theplanned use-up of a specific item.

• Create ECOs across large organization structures at any given level in anorganization hierarchy.

Deleting Obsolete InformationDelete obsolete item and ECO information.



Oracle BOM/Engineering Change Control


Oracle BOM/Engineering Change Control

BOM_BILL_OF_BOM_BILL_OF_MATERIALSMATERIALS

BOM_INVENTORY_

COMPONENTS

PRIMARYBILL

ALTERNATEBILL

ENG_CURRENT_SCHEDULED_DATES

ENG_CHANGE_ORDER_

REVISIONS

ENG_REVISED_

COMPONENTS

ENG_ENGINEERING_CHANGES

ENG_REVISED_

ITEMS

MTL_SYSTEM_ITEMS_B

ENG_ENGINEERING_CHANGESENG_ENGINEERING_CHANGES stores information about engineeringchange order headers. Each row includes the unique identifier of the ECO, adescription, change order type, the reason and priority codes, the status and therequestor, approval list and approval status, implementation costs, andcancellation information. The primary key is CHANGE_NOTICE,ORGANIZATION_ID.

ENG_CHANGE_ORDER_REVISIONSENG_CHANGE_ORDER_REVISIONS stores information about the user-defined revisions of an engineering change order. It is a child table ofENG_ENGINEERING_CHANGES. The primary key is REVISION_ID.

ENG_REVISED_ITEMSENG_REVISED_ITEMS stores information about the revised items (usuallyassemblies) on an engineering change order. It is a child table ofENG_ENGINEERING_CHANGES. The primary key isREVISED_ITEM_SEQUENCE_ID.

ENG_CURRENT_SCHEDULED_DATESENG_CURRENT_SCHEDULED_DATES stores information about theeffective date for each revised item on an engineering change order. Each timethe effective date for a revised item on an ECO is changed, a new row isinserted into this table. The primary key is SCHEDULE_ID,REVISED_ITEM_SEQUENCE_ID (o).

BOM_BILL_OF_MATERIALS



BOM_BILL_OF_MATERIALS stores information about manufacturing andengineering bills of material. Each row represents a unique manufacturing orengineering bill and is defined by the BILL_SEQUENCE_ID primary key.

BOM_INVENTORY_COMPONENTSBOM_INVENTORY_COMPONENTS stores information about bill of materialcomponents. The primary key, COMPONENT_SEQUENCE_ID, uniquelyidentifies each row. There is one row per component on an operation within agiven date range.

ENG_REVISED_COMPONENTSENG_REVISED_COMPONENTS stores information about the implementedand canceled revised components on an engineering change order. The primarykey is COMPONENT_SEQUENCE_ID.




Practice 3 Setup


Practice 3 Setup

1 Create an ECO, substituting one item in one ofyour BOMs with another available item. Set theeffective date to a week from today.

2 Verify your indented BOM to view the impendingchange.

3 Implement your ECO, then re-verify your indentedBOM.

Setup InstructionsCreate an ECO1. Navigate to the Engineering Change Orders form.(N) Engineering > ECOs > ECOs

• Enter ##-eco in the first field on the header form. In the other header fields,enter any values you choose from the list of values (Caution: Do NOT usethe New Prod change type; it is set up for a Workflow process).

• Click the Revised Items button and enter the item number of the BOM youwish to change.

• Optionally, enter a new revision.• Enter an effective date of a week from today.• Click the Components button.• Go to the Action field and select Disable from the list of values.• Enter the item number of the component you wish to disable.• Return to the Action field, and select Add from the list of values.• Enter the item number of your new component.• Enter the new sequence for the component.• Return to the header form, and change the approval status to Approved, if

necessary.• Save your work.• Record your ECO number _____________.



Verify Indented BOM2. Navigate to the Find Indented Bills form.(N) Bills of Materials > Bills > Indented Bills

• Enter the top level item for the BOM you’re changing via ECO.• Set your Display Option drop down menu from Future and Current to All.• Clear the Implemented Only check box.• Click the Find button.• Expand your BOM and select the Effectivity tab to view pending date

changes.• Select the ECO tab to view the pending changes.

Implement Your ECO3. Navigate to the Engineering Change Orders form.(N) Engineering > ECOs > ECOs

• Query your ECO.• Fromthe Tools menu, select Implement.• Select Yes and OK.• Repeat step 2 (Verify Indented BOM) to view the change to the Bill of

Material.



Practice 3


Practice 3

Find the revised items included in your ECO.


• Tables: eng_engineering_changes, mtl_system_items, eng_revised_items• Keys: change_notice, revised_item_id, inventory_item_id,• Columns: change_notice, segmentl



Practice 3 Solution


Practice 3 Solution

Find the revised items included in your ECO.


• substr(eco.change_notice,1,10) “ECO #”,• substr(itm.segment1,1,5) “Item#”

FROM• eng_engineering_changes eco,• mtl_system_items itm,• eng_revised_items rev

WHERE• eco.change_notice LIKE ‘&ECO%’ AND• eco.change_notice = rev.change_notice AND• rev.revised_item_id = itm.inventory_item_id AND• rev.organization_id = itm.organization_id



Agenda


Agenda




Oracle Bills of Material/Engineering Open Interfaces


Oracle Bills of Material/EngineeringOpen Interfaces

• Open Bills of Material Interface• Open Routing Interface

Open Bills of Material InterfaceWith this interface, you can convert manufacturing bills of material from legacymanufacturing systems, migrate marketing bills of material from custom salesorder entry systems, import new engineering bills from Product DataManagement (PDM) systems, add members to product families, and exportBOM data for a particular assembly to all organizations, at any given levelunder an organization hierarchy.

Open Routing InterfaceThis interface allows you to convert manufacturing routings from legacymanufacturing systems, import new engineering routings from PDM systems, orupdate and delete existing routings.Instructor NoteIn the Open Bills of Material Interfaces definition, the export functionality hasbeen added. An Application Program Interface (API) is available to perform thisfunction. Its name, BOM_EXPORT_TAB, appears in the table on the nextpage.



Oracle BOM/Engineering Interface Tables


Oracle BOM/Engineering Interface TablesInterface Data Flow Table, View, Table, View, or Module nameName Direction or Process

MFG Outbound View BOM_CALANDAR_MONTHS_VIEWCalendarBill of Inbound/ Table BOM_BILL_OF_MTLS_INTERFACEMaterial Outbound BOM_INVENTORY_COMPS_INTERFACE BOM_REF_DESGS_INTERFACE BOM_SUB_COMPS_INTERFACE BOM_ITEMS_REVISIONS_INTERFACE BOM_EXPORT_TABRoutings Inbound Table BOM_OP_ROUTINGS_INTERFACE BOM_OP_SEQUENCES_INTERFACE BOM_OP_RESOURCES_INTERFACEECO Inbound Table ENG_ENG_CHANGES_INTERFACE ENG_ECO_REVISIONS_INTERFACE ENG_REVISED_ITEMS_INTERFACE ENG_INVENTORY_COMPS_INTERFACE ENG_REF_DESGS_INTERFACE ENG_SUB_COMPS_INTERFACE

Exporting BOM DataBOM_EXPORT_TAB is a PL/SQL table, which stores exploded billinformation for the specified assembly and for all subordinate organizations in aspecified organization hierarchy.



Summary


Summary

In this lesson, you have learned how to relate themajor tables to BOM/Engineering setup definition.• Bill of material structures• Resources and departments• Routings• Engineering change control• Interface tables


11i Manufacturing Functional Foundation: Work in ProcessChapter 10 - Page 1

11i Manufacturing FunctionalFoundation: Work in ProcessChapter 10



11i Manufacturing Functional Foundation: Work inProcess


11i Manufacturing Functional Foundation:Work in Process



Objectives


Objectives

After completing this lesson, you should be able todo the following:• Discuss the flow of inventory through a factory• Identify the major tables used in material move and

completion transactions• Run a query in SQL*Plus against the appropriate

database tables to review material transactionsagainst a particular inventory item

Lesson AimThe aim of this lesson is to provide the student an overview of the flow ofinventory through a factory and the resulting transactions that occur in OracleInventory, and discuss the database tables that are populated as a result of theseactivities.Instructor NoteThe primary key for each of the ERD tables is in each table definition in theNotes section of the slides. Example: ‘The primary key is INVENTORY_ID,ORGANIZATION_ID’, where there are two elements that make up the primarykey. Some _INTERFACE and _TEMP names may not have a primary keyassociated with it.An “(o)” following a primary key name indicates that element to be optional.Example: ‘WIP_ENTITY_ID, OPERATION_SEQ_NUM,REPETITIVE_SCHEDULE_ID (o)’. In this example it indicates that theREPETITIVE_SCHEDULE_ID is part of the primary key when you referencespecific Repetitive schedules tables and not part of the primary key when youreference Discrete job tables.



Agenda


Agenda

• Discrete jobs and repetitive schedules• Work in process transactions• Open interfaces



Agenda


Agenda




Discrete Versus Repetitive Manufacturing Process


Discrete Versus RepetitiveManufacturing Process

Discrete ManufacturingDiscrete Manufacturing Repetitive ManufacturingRepetitive Manufacturing

Making assemblies in batches orMaking assemblies in batches orgroupsgroups

Making assemblies continuously over aMaking assemblies continuously over apredefined amount of timepredefined amount of time

Defining jobs (work orders)Defining jobs (work orders) Defining repetitive schedulesDefining repetitive schedules

Detailed schedulingDetailed scheduling Repetit ive line schedulingRepetit ive line scheduling

Charging the jobCharging the job Charging the repetitive assembly or lineCharging the repetitive assembly or line

Job CostingJob Costing Period CostingPeriod Costing

Discrete Manufacturing Versus Repetitive ManufacturingA discrete job is a production order for the manufacture of a specific (discrete)quantity of an assembly, using specific materials and resources, within a limitedrange of time.In repetitive manufacturing, you produce on a continuous or semicontinuousbasis over a predefined length of time.



Oracle Work in Process Overview


Oracle Work in Process Overview

MTL_SYSTEM_ITEMS_B

WIP_ENTITIES

WIP_DISCRETE_JOBS

WIP_FLOW_SCHEDULES

WIP_REPETITIVE_SCHEDULES

WIP_REPETITIVE_ITEMS

WIP_OPERATIONS


WIP_ENTITIESWIP_ENTITIES stores information about each discrete job or repetitiveassembly. Each row includes a unique discrete job or repetitive assembly name,entity type, and the assembly built by the job or by the repetitive assembly. Theprimary key is WIP_ENTITY_ID.

WIP_REPETITIVE_ITEMSWIP_REPETITIVE_ITEMS stores your repetitive assemblies and theproduction lines on which you build each assembly. Each row represents aparticular assembly/line combination. The primary key is WIP_ENTITY_ID,LINE_ID.

WIP_REPETITIVE_SCHEDULESWIP_REPETITIVE_SCHEDULES stores repetitive schedule information.Oracle Work in Process uses this information to control repetitive production.The primary key is REPETITIVE_SCHEDULE_ID.

WIP_DISCRETE_JOBSWIP_DISCRETE_JOBS stores information about discrete jobs. Each rowrepresents a discrete job. Oracle Work in Process uses this information tocontrol discrete production. The primary key is WIP_ENTITY_ID.



WIP_OPERATIONSWIP_OPERATIONS stores information about the operations for your discretejobs and repetitive schedules. Oracle Work in Process uses this information tocontrol and monitor your assembly production on the shop floor. The primarykey is WIP_ENTITY_ID, OPERATION_SEQ_NUM,REPETITIVE_SCHEDULE_ID (o).

WIP_FLOW_SCHEDULESWIP_FLOW_SCHEDULES stores Work Order-less Flow scheduleinformation. Each row represents a Flow schedule and contains informationabout the assembly being built. The primary key is WIP_ENTITY_ID.Instructor NoteThe full definition and explanation of Flow Schedules will be available whenthat product has been added to this course.



Oracle Work in Process Operations


WIP_OPERATION_RESOURCES

Oracle Work in Process Operations

MTL_SYSTEM_ITEMS_B

WIP_REQUIREMENT_OPERATIONS

WIP_DISCRETE_JOBS

MTL_ITEM_

LOCATIONS


WIP_SHOP_FLOOR_

STATUSES

WIP_OPERATIONS

WIP_REQUIREMENT_OPERATIONSWIP_REQUIREMENT_OPERATIONS stores information about the materialrequirements for jobs or schedules. Oracle Work in Process uses thisinformation to track the material used in a job or schedule. The primary key isINVENTORY_ITEM_ID, WIP_ENTITY_ID, OPERATION_SEQ_NUM,REPETITIVE_SCHEDULE_ID (o).




MTL_ITEM_LOCATIONS



MTL_ITEM_LOCATIONS is the definition table for stock locators. Theassociated attributes describe which subinventory this locator belongs to, whatthe locator physical capacity is, etc. The primary key isINVENTORY_LOCATION_ID, ORGANIZATION_ID.

WIP_OPERATION_RESOURCESWIP_OPERATION_RESOURCES stores information about the resourcesassociated with an operation for a job or a repetitive schedule. Oracle Work inProcess uses this information to schedule jobs and repetitive schedules, and tocharge resources to jobs and schedules. The primary key is WIP_ENTITY_ID,OPERATION_SEQ_NUM, RESOURCE_SEQ_NUM,REPETITIVE_SCHEDULE_ID (o).


WIP_SHOP_FLOOR_STATUSESThis table stores the status codes that you assign to a discrete job or repetitiveschedule. Each row contains the operation sequence number and intraoperationstep to which you assign the status. The primary key is WIP_ENTITY_ID,OPERATION_SEQ_NUM, SHOP_FLOOR_STATUS_CODE, LINE_ID,INTRAOPERATION_STEP_TYPE.



Oracle Work in Process: Discrete Jobs



Oracle Work in Process: Discrete Jobs

WIP_DISCRETE_

JOBS


WIP_REQUIREMENT_

OPERATIONS

WIP_ACCOUNTING_

CLASSES

WIP_WORK_ORDER_

INTERFACE

WIP_OPERATIONS

MTL_SYSTEM_ITEMS_B

WIP_ENTITIES

WIP_DISCRETE_JOBSWIP_DISCRETE_JOBS stores information about discrete jobs. Each rowrepresents a discrete job. It also contains the information about the assemblybeing built, the revision of the assembly, the job quantity, the job status,accounting information, and job schedule dates. Oracle Work in Process usesthis information to control discrete production. The primary key isWIP_ENTITY_ID.



WIP_OPERATION_RESOURCESWIP_OPERATION_RESOURCES stores information about the resourcesassociated with an operation for a job or a repetitive schedule. Oracle Work inProcess uses this information to schedule jobs and repetitive schedules, and to



charge resources to jobs and schedules. The primary key is WIP_ENTITY_ID,OPERATION_SEQ_NUM, RESOURCE_SEQ_NUM,REPETITIVE_SCHEDULE_ID (o).

WIP_WORK_ORDER_INTERFACEWIP_WORK_ORDER_INTERFACE enables you to import Discrete job andRepetitive schedule header information, and Discrete job operations, material,resource, and scheduling information from any source, using a single process.There is no primary key associated with this interface.

WIP_ACCOUNTING_CLASSESThis table stores accounting flexfield information for standard discrete jobs,nonstandard asset jobs, nonstandard expense jobs, and repetitive assemblies.Oracle Work in Process stores a general ledger account for each cost elementassociated with a class. The CLASS_CODE column uniquely identifies eachclass. Oracle Work in Process uses this information to create the journal entriesthat post cost transactions. The primary key is CLASS_CODE,ORGANIZATION_ID.

MTL_SYSTEM_ITEMS_BThis is the definition table for items. This table holds the definitions forinventory items, engineering items, and purchasing items. Each item is initiallydefined in an item master organization. Then you assign the item to otherorganizations that need to recognize this item. A row is inserted for each neworganization to which the item is assigned. The primary key isINVENTORY_ITEM_ID, ORGANIZATION_ID.



Oracle Work in Process: Repetitive Schedules


Oracle Work in Process: Repetitive Schedules

WIP_REQUIREMENT_

OPERATIONS


WIP_ACCOUNTING_

CLASSES


WIP_OPERATIONS

WIP_REPETITIVE_ITEMS

MTL_SYSTEM_ITEMS_B


WIP_ENTITIES

WIP_WORK_ORDER_

INTERFACE

WIP_REPETITIVE_ITEMSWIP_REPETITIVE_ITEMS stores your repetitive assemblies and theproduction lines on which you build each assembly. Each row represents aparticular assembly/line combination and includes information such as the linepriority, the accounting class associated with the line, the line speed, the line’ssupply type, if the line is used in calculating the assembly’s lead time, thecompletion subinventory and locator for a line, and the alternate bill and routingyou use for a particular line. Oracle Work in Process uses this information whenyou define repetitive schedules. Oracle Master Schedule/MRP and OracleCapacity use this information when mass loading repetitive schedules andrunning capacity loads on repetitive schedules. The primary key isWIP_ENTITY_ID, LINE_ID.


WIP_OPERATIONSWIP_OPERATIONS stores information about the operations for your discretejobs and repetitive schedules. Each row represents a specific operation andincludes an operation sequence number to order the operations for a job orrepetitive schedule. Oracle Work in Process uses this information to control andmonitor your assembly production on the shop floor. The primary key is



WIP_ENTITY_ID, OPERATION_SEQ_NUM,REPETITIVE_SCHEDULE_ID (o).



WIP_ACCOUNTING_CLASSESThis table stores accounting flexfield information for standard discrete jobs,nonstandard asset jobs, nonstandard expense jobs, and repetitive assemblies.Oracle Work in Process stores a general ledger account for each cost elementassociated with a class. The CLASS_CODE column uniquely identifies eachclass. Oracle Work in Process uses this information to create the journal entriesthat post cost transactions. The primary key is CLASS_CODE,ORAGANIZATION_ID.

MTL_SYSTEM_ITEMS_BThis is the definition table for items. This table holds the definitions forinventory items, engineering items, and purchasing items. Each item is initiallydefined in an item master organization. Then you assign the item to otherorganizations that need to recognize this item. A row is inserted for each neworganization to which the item is assigned. The primary key isINVENTORY_ITEM_ID, ORGANIZATION_ID.



Repetitive Schedules Summary Report


Repetitive Schedules Summary Report

You can display the assemblies with their statuses fora repetitive line.You can display the assemblies with their statuses fora repetitive line.

Repetitive Schedules Summary (M1)Repetitive Schedules Summary (M1)

(N) WIP > Repetitive > Repetitive Schedules



Agenda


Agenda




Oracle WIP Transactions


Oracle WIP Transactions

InventoryInventory

Raw materialRaw materialinventoryinventory

Finished goodsFinished goodssubinventorysubinventory

Work in ProcessWork in Process

Jobs andJobs andschedulesschedules

Scrap rejectedassemblies

IssueIssuematerialmaterial

CompleteCompletefinishedfinished

assembliesassemblies Move assemblies onthe shop floor and charge resources

Work in Process TransactionsWork in Process supports discrete, project, repetitive, flow, assemble-to-order,work order-less, or a combination of these manufacturing methods.Manufacturing SupportBuild discrete jobs, both standard and nonstandard (prototype, rework,maintenance, and special projects).Production SchedulingLoad and sequence repetitive production by assembly and production line.Material ControlIssue and return components from and to inventory.Shop Floor ControlMove assemblies between and within operations.

Transaction FunctionalityOracle Work in Process tracks material and production activity on the shopfloor to facilitate inventory control, job scheduling, and costing.Material IssueRecord material issues to discrete jobs, repetitive schedules, nonstandard jobs,or flow schedules.Shop Floor MoveRecord production activity including operation moves, job completions andover-completions, and scrap transactions.



Resource Charging• Charge multiple resources option.• Charge resources automatically (based on shop floor moves) or manually, at

either standard or actual labor rates.Outside ProcessingEnables you to include supplier-sourced components and resources in yourmanufacturing processes.Integration with Oracle QualityYou can collect quality data as you complete and return assemblies.Workflow Alerts and Messages

• You can use workflow-based alerts and messaging to identify and eliminateinventory shortage situations within Oracle Work in Process.

• You can trigger alerts to key personnel when an item is moved intoinventory, when a shortage exists, or when it is completed.

Other Transactions• Cost material using standard cost.• Use repetitive schedules to simplify material and production reporting.• Use lot and serial number controlled parts in production moves.



Oracle WIP Material Transactions


Oracle WIP Material Transactions


MTL_MATERIAL_TXNALLOCATIONS

MTL_MATERIAL_

TRANSACTIONSWIP_DISCRETE_JOBS

WIP_REQUIREMENT_

OPERATIONS

WIP_OPERATIONS

MTL_TRANSACTION_

ACCOUNTS

MTL_MATERIAL_TXN_ALLOCATIONSThis table stores the repetitive schedules charged by a material transaction. Eachrow contains the quantity transacted to each schedule for a given transaction.Oracle Work in Process uses this information to report changes to individualschedules for multischedule material transactions. The primary key isTRANSACTION_ID, REPETITIVE_SCHEDULE_ID, ORGANIZATION_ID.

MTL_TRANSACTION_ACCOUNTSThis table holds the accounting information for each material transaction inMTL_MATERIAL_TRANSACTIONS. Oracle Inventory uses this informationto track the financial impact of quantity moves. (There is no primary key forthis table.)

MTL_MATERIAL_TRANSACTIONSThis table stores a record of every material transaction, including issues andreturns of component items in Work in Process. Records are inserted into thistable through the transaction processor. The primary key isTRANSACTION_ID.

WIP_REQUIREMENT_OPERATIONSThis table stores information about the material requirements for jobs orschedules. Oracle Work in Process uses this information to track the materialused in a job or schedule. The primary key is INVENTORY_ITEM_ID,WIP_ENTITY_ID, OPERATION_SEQ_NUM,REPETITIVE_SCHEDULE_ID (o).

WIP_OPERATIONS



WIP_OPERATIONS stores information about the operations of your discretejobs and repetitive schedules. Each row represents a specific operation andincludes an operation sequence number to order the operations for a job orrepetitive schedule. Oracle Work in Process uses this information to control andmonitor your assembly production on the shop floor. The primary key isWIP_ENTITY_ID, OPERATION_SEQ_NUM,REPETITIVE_SCHEDULE_ID (o).

WIP_REPETITIVE_SCHEDULESThis table stores repetitive schedule information. Oracle Work in Process usesthis information to control repetitive production. The primary key isREPETITIVE_SCHEDULE_ID.

WIP_DISCRETE_JOBSThis table stores information about discrete jobs. Each row represents a discretejob. Oracle Work in Process uses this information to control discreteproduction. The primary key is WIP_ENTITY_ID.



Material Transactions Window


Material Transactions Window

WIP Material Transactions (M1)WIP Material Transactions (M1)

You can issue components from inventory tojobs and return issued components from jobsto inventory.

(N) WIP > Material Transactions > WIP Material Transactions



Oracle WIP: Move Transactions


Oracle WIP: Move Transactions


WIP_MOVE_TXN_ALLOCATIONS


WIP_DISCRETE_JOBS

WIP_MOVE_TRANSACTIONS

WIP_OPERATIONS


WIP_TXN_ALLOCATIONS

WIP_TRANSACTIONS



MTL_MATERIAL_TRANSACTIONSThis table stores a record of every material transaction, including issues andreturns of component items in Work in Process. Records are inserted into thistable through the transaction processor. The primary key isTRANSACTION_ID.

WIP_OPERATIONSWIP_OPERATIONS stores information about the operations for your discretejobs and repetitive schedules. Each row represents a specific operation andincludes an operation sequence number to order the operations for a job orrepetitive schedule. Oracle Work in Process uses this information to control andmonitor your assembly production on the shop floor. The primary key isWIP_ENTITY_ID, OPERATION_SEQ_NUM,REPETITIVE_SCHEDULE_ID (o).




WIP_OPERATION_RESOURCES stores information about the resourcesassociated with an operation for a job or a repetitive schedule. Oracle Work inProcess uses this information to schedule jobs and repetitive schedules, and tocharge resources to jobs and schedules. The primary key is WIP_ENTITY_ID,OPERATION_SEQ_NUM, RESOURCE_SEQ_NUM,REPETITIVE_SCHEDULE_ID (o).

WIP_MOVE_TXN_ALLOCATIONSThis table stores Move quantity information for single shop floor Movetransactions that transcend multiple repetitive schedules. The primary key isTRANSACTION_ID, REPETITIVE_SCHEDULE_ID.

WIP_TXN_ALLOCATIONSWIP_TXN_ALLOCATIONS stores resource information for single resourcecost transactions that transcend multiple repetitive schedules. Oracle Work inProcess allocates resource charges to repetitive schedules based on a FIFOalgorithm. The primary key is TRANSACTION_ID,REPETITIVE_SCHEDULE_ID.

WIP_TRANSACTIONSThis table stores information about each resource transaction in Oracle Work inProcess. Oracle Work in Process uses this information to track resources and tocalculate values stored in WIP_TRANSACTION_ACCOUNTS. The primarykey is TRANSACTION_ID.

WIP_MOVE_TRANSACTIONSWIP_MOVE_TRANSACTIONS stores information about shop floor movetransactions. Each row represents a single move transaction and includes aunique transaction ID, a transaction date, the job or repetitive schedule in whichthe move occurs, the quantity moved, the from and to operation sequencenumbers, operation codes, and intraoperation steps. Oracle Work in Processuses this information to track move transactions. The primary key isTRANSACTION_ID.



Move Transactions Window


Move Transactions Window

Move Transactions (M1)Move Transactions (M1)

You can move the assemblies you are buildingfrom one operation step to another.

(N) WIP > Move Transactions > Move Transactions



Oracle WIP: Resource Transactions


Oracle WIP: Resource Transactions

WIP_TRANSACTION_

ACCOUNTS


WIP_TXN_ALLOCATIONS

WIP_TRANSACTIONS

WIP_DISCRETE_

JOBS

WIP_COST_TXN_INTERFACE


WIP_OPERATIONS

WIP_OPERATION_RESOURCE_

USAGE

WIP_OPERATION_OVERHEADS



WIP_OPERATIONSWIP_OPERATIONS stores information about the operations for your discretejobs and repetitive schedules. Each row represents a specific operation andincludes an operation sequence number to order the operations for a job orrepetitive schedule. Oracle Work in Process uses this information to control andmonitor your assembly production on the shop floor. The primary key isWIP_ENTITY_ID, OPERATION_SEQ_NUM,REPETITIVE_SCHEDULE_ID (o).




WIP_TRANSACTIONSWIP_TRANSACTIONS stores information about each resource transaction inOracle Work in Process. Oracle Work in Process uses this information to trackresources and to calculate values stored inWIP_TRANSACTION_ACCOUNTS. The primary key isTRANSACTION_ID.

WIP_COST_TXN_INTERFACEWIP_COST_TXN_INTERFACE contains information about cost transactionsthat Oracle Work in Process needs to process. Oracle Work in Process uses thistable to support all resource cost transactions, including transactions youprocess from other systems. The primary key is TRANSACTION_ID (o).

WIP_TRANSACTION_ACCOUNTSWIP_TRANSACTION_ACCOUNTS holds the accounting information foreach resource transaction in WIP_TRANSACTIONS. These tables are joinedby the TRANSACTION_ID column, and there are at least two rows (debit andcredit) for each transaction of a costed resource. Oracle Work in Process usesthis information to track the financial impact of resource transactions. There isno primary key.

WIP_TXN_ALLOCATIONSWIP_TXN_ALLOCATIONS stores resource information for single resourcecost transactions that transcend multiple repetitive schedules. Oracle Work inProcess allocates resource charges to repetitive schedules based on a FIFOalgorithm. The primary key is TRANSACTION_ID,REPETITIVE_SCHEDULE_ID.

WIP_OPERATION_RESOURCE_USAGEWIP_OPERATION_RESOURCE_USAGE stores information about the use ofresources associated with job and schedule operations. Each row represents aresource usage in a valid shift for that particular resource. There is no primarykey.

WIP_OPERATION_OVERHEADSWIP_OPERATION_OVERHEADS stores information about resource-basedand departmental overhead costs for jobs in an average costing organization.The primary key is WIP_ENTITY_ID, OPERATION_SEQ_NUM,OVERHEAD_ID, RESOURCE_SEQ_NUM, BASIS_TYPE.



Resource Transaction Window


Resource Transaction Window

You can use this form to charge resources.

Resource Transactions (M1)

(N) WIP > Resource Transactions > Resource Transactions



Oracle WIP: Completion Transactions


Oracle WIP: Completion Transactions

MTL_TRANSACTION

ACCOUNTS

WIP_DISCRETE_JOBS

WIP_FLOW_SCHEDULES




TEMP

MTL_MATERIAL_TXN_ALLOCATIONS



MTL_MATERIAL_TRANSACTIONS_TEMPMTL_MATERIAL_TRANSACTIONS_TEMP is the gateway for all materialtransactions. Transfer records are stored in this table as a single record. Theprimary key is TRANSACTION_HEADER_ID (o).


MTL_TRANSACTION_ACCOUNTSMTL_TRANSACTION_ACCOUNTS holds the accounting information foreach material transaction in MTL_MATERIAL_TRANSACTIONS. OracleInventory uses this information to track the financial impact of quantity moves.There is no primary key for this table.



MTL_MATERIAL_TXN_ALLOCATIONSMTL_MATERIAL_TXN_ALLOCATIONS stores the repetitive schedulescharged by a material transaction. Each row contains the quantity transacted toeach schedule for a given transaction. Oracle Work in Process uses thisinformation to report changes to individual schedules for multischedule materialtransactions. the Primary key is TRANSACTION_ID,REPETITIVE_SCHEDULE_ID, ORGANIZATION_ID.

WIP_FLOW_SCHEDULESWIP_FLOW_SCHEDULES stores Work Order-less Flow scheduleinformation. Each row represents a Flow schedule and contains informationabout the assembly being built. The primary key is WIP_ENTITY_IDInstructor NoteThe full definition and explanation of Flow Schedules will be available whenthat product has been added to this course.



Completion Transactions window


Completion Transactions window

You can complete assemblies from jobs intoinventory, and you can return completedassemblies from inventory to jobs.

Completion Transactions (M1)

(N) WIP . Material Transactions > Completion Transactions



Oracle WIP: Work Order-less Completions


Oracle WIP: Work Order-less Completions

WIP_PERIOD_BALANCES

WIP_TRANSACTIONS

WIP_FLOW_

SCHEDULES



TEMP

MTL_TRANSACTIONS_

INTERFACE

BOM_BILL_OF_

MATERIALS

BOM_OPERATIONAL_

ROUTINGS

WIP_ENTITIES

WIP_FLOW_SCHEDULESWIP_FLOW_SCHEDULES stores Work Order-less Flow scheduleinformation. Each row represents a Flow schedule. Oracle Work in Process usesthis information to control Flow schedule production. The primary key isWIP_ENTITY_ID.

MTL_TRANSACTIONS_INTERFACEMTL_TRANSACTION_INTERFACE is the interface point between nonOracle Inventory applications and the Oracle Inventory transaction module.Transaction Manager concurrent program polls this table at a user specifiedprocess interval, and submits the Transaction Workers to process them. There isno primary key for this table.


MTL_MATERIAL_TRANSACTIONS_TEMPMTL_MATERIAL_TRANSACTIONS_TEMP is the gateway for all materialtransactions. Transfer records are stored in this table as a single record. Theprimary key is TRANSACTION_HEADER_ID.

BOM_BILL_OF_MATERIAS



BOM_BILL_OF_MATERIALS stores information about manufacturing andengineering bills of material. Each row in this table represents a uniquemanufacturing or engineering bill. The primary key is BILL_SEQUENCE_ID.

BOM_OPERATIONAL_ROUTINGSBOM_OPERATIONAL_ROUTINGS stores information about manufacturingand engineering routings. The primary key is ROUTING_SEQUENCE_ID.

WIP_PERIOD_BALANCESWIP_PERIOD_BALANCES stores summary accounting information for jobs andschedules. Each row represents job or schedule charges within a given accountingperiod, and contains the summary values for each cost element. The primary keyis ACCT_PERIOD_ID, WIP_ENTITY_ID.WIP_TRANSACTIONS

WIP_TRANSACTIONS stores information about each resource transaction inOracle Work in Process. Oracle Work in Process uses this information to trackresources and to calculate values stored inWIP_TRANSACTION_ACCOUNTS. The primary key isTRANSACTION_ID.

WIP_ENTITIESWIP_ENTITIES stores information about jobs, repetitive assemblies, and flowschedules. Each row includes a unique entity name, the entity type, and theassembly being built. The primary key is WIP_ENTITY_ID.



Work Order-less Completions Window


Work Order-less Completions Window

You can complete or return assemblies to or frominventory. You can scrap assemblies from or returnscrapped assemblies to any operation.

Work Order-less Completions (M1)

(N) WIP > Material Transactions > Work Order-less Completions



Practice 1 Setup


Practice 1 Setup

Create and release a discrete job for one of yourassembly planned orders.

Setup InstructionsNavigate to the Discrete Jobs window.

. (N)WIP > Discrete > Discrete Jobs• Enter your assembly number in the Assembly field and choose Find.• In the Discrete Job Summary window, select one of your jobs and Open it• Record your job number• Change the status of your job to “Released” from the LOV• Click in the Bill box for a list of regions and select Routing• Enter a Completion Subinventory from the LOV• Save your work• Check the operation and component information for your assembly• Navigate to the Material Requirements window.

(N) WIP-> Job/Schedule Details->Material Requirements• Change some of your components to Push supply type.• Save your work.• Navigate to the WIP Material Transaction window.

(N) WIP > Material Transactions > WIP Material Transactions• Enter your job number and click Continue (you should see your Push

components in the window for issue); then select Done.• Navigate to the Move Transactions window.



(N) WIP > Move Transactions -> Move Transactions• Enter your job number.• Select Transaction Type of Complete (note default information in the

Operations region).• In the Operations region, click in From (Seq) box and perform LOV

(information is defaulted in).• In Transaction region, enter the full Quantity to complete all assemblies• Save your work.• Navigate to the following windows, enter your job number and review the

fields in the windows (note: only released jobs can be entered in thesewindows):

– Resource Transaction window which is used only for manual resourcetransactions can be accessed with the Resources button in the MoveTransaction window.

– Completion Transaction window is used for routine completiontransactions when assemblies are available to complete in the lastrouting operation in the To Move intra-operational step.



Practice 1


Practice 1



• Tables: wip_discret_jobs, mtl_system_items_b, mfg_lookups• Keys: segment1, organization_id, inventory_item_id, primary_item_id,

status_type• Columns: lookup_type, lookup_code, meaning, wip_entity_id, description,

start_quantity, quantity_completed, scheduled_completion_date



Practice 1 Solution


Practice 1 Solution


SQL Code Solution (to find the correct status type)SELECT

• substr(lookup_type,1,15) “Type”,• substr(lookup_code,1,5) “Code”,• substr(meaning,1,15) “Meaning”,

FROM• mfg_lookups

WHERE• lookup_type LIKE ‘WIP_JOB_STATUS’

SQL Code Solution (to find the job)SELECT

• substr(wip.wip_entity_id,1,10) “Job”,• substr(wip.description,1,10) “Desc”,• substr(wip.start_quantity,1,5) “Quant”,• substr(wip.quantity_completed,1,5) “Comp”,• substr(wip.scheduled_completion_date,1,10) “Date”,

FROM• wip_discrete_jobs wip,• mtl_system_item_b inv

WHERE



• inv.segment1 LIKE ‘&Item%’ AND• inv.organization_id = 207 AND• inv.inventory_item_id = wip.primary_item_id AND• wip.organization_id = inv.organization_id AND• wip.status_type = 4



Agenda


Agenda




Oracle WIP: Open Interfaces


Oracle WIP: Open Interfaces

• Work Order Interface• Open Move Transaction Interface• Open Resource Transaction Interface

Work Order InterfaceUsing this interface, you can import:

• planned orders for new Discrete jobs• Discrete job operations, components, resources, resource usage, and

scheduling details• update and reschedule recommendations for existing Discrete jobs, and

suggested Repetitive schedules.Oracle Work in Process uses this information to automatically create Discretejobs and pending Repetitive schedules, or to update existing Discrete jobs. Thisinterface consists of two tables: Open Job and Schedule Interface table and WIPJob Details Interface table.

Open Move Transaction InterfaceYou can use external data collection devices such as bar-code readers,automated test equipment, cell controllers, and other manufacturing executionsystems to collect move transactions or combined move and completion/returntransactions.

Open Resource Transaction InterfaceThis interface enables you to use external data collection devices such as bar-code readers, payroll systems, and time-card entry forms to collect resource andoverhead transactions.



Oracle WIP Transactions Open Interface Tables


Oracle WIP TransactionsOpen Interface Tables


Moves Inbound Table WIP_MOVE_TXN_INTERFACE

Resource Inbound Table WIP_COST_TXN_INTERFACEWork Order Inbound/ Process MTL_TRANACTIONS_INTERFACEInterface Outbound and MTL_SERIAL_NUMBERS_INTERFACE Table MTL_TRANSACTION_LOTS_INTERFACE Stored Procedures LOAD_INTERFACE and LOAD_WIP and WIP_SCHEDULING_INTERFACE



Summary


Summary

In this lesson, you have learned how to relate themajor tables to Work in Process inventorytransactions:• Discrete jobs• Repetitive schedules• Material transactions:

– Move– Resource– Completion– Work Order-less Completions

• Open interfaces


11i Manufacturing Functional Foundation: Cost ManagementChapter 11 - Page 1

11i Manufacturing FunctionalFoundation: CostManagementChapter 11



11i Manufacturing Functional Foundation: CostManagement


11i Manufacturing Functional Foundation:Cost Management



Objectives


Objectives

After completing this lesson, you should be able todo the following:• Discuss costing setup definition activities• Identify the major tables used in cost resources

and overhead definitions• Run a query in SQL*Plus against the appropriate

database tables to find the cost of a particular item

Lesson AimThe aim of this lesson is to provide the student an overview of the setupdefinition process in Oracle Cost and discuss the database tables that arepopulated as a result of the costing setup activity.Instructor NoteThe primary key for each of the ERD tables is in each table definition in theNotes section of the slides. Example: ‘The primary key is INVENTORY_ID,ORGANIZATION_ID’, where there are two elements that make up the primarykey. Some _INTERFACE and _TEMP names may not have a primary keyassociated with it.An “(o)” following a primary key name indicates that element to be optional.Example: ‘WIP_ENTITY_ID, OPERATION_SEQ_NUM,REPETITIVE_SCHEDULE_ID (o)’. In this example it indicates that theREPETITIVE_SCHEDULE_ID is part of the primary key when you referencespecific Repetitive schedules tables and not part of the primary key when youreference Discrete job tables.



Agenda


Agenda







ProductionProduction ProfitabilityProfitabilityInventoryInventory

AnalysisAnalysis Audit trailAudit trailItemItemcostscosts

DescriptionOracle Cost Management automatically performs the cost accounting for allyour Oracle Inventory, Work in Process, and Purchasing transactions. Yourinventory and work-in-process costs are up-to-date, and your inventory valuematches the cumulative total of your accounting transactions.

Standard Costing• Oracle Cost Management supports standard costing for inventory, bills of material, and work-in-process costing.• Organizations that use Oracle Work in Process must use standard costing. If you use Oracle Inventory without Oracle Work in Process, you can choose either standard or average costing.• You may use standard costing for one organization and average costing for another organization.

Average Costing• Oracle Cost Management supports average costing for inventory. Averagecosts are automatically updated as transactions are processed.• If you have Oracle Bills of Material installed and do not use Oracle Work in Process for your organization, you may transact your inventory at average, and use the standard cost features for product cost simulations and budgeting.

Extensive Cost Simulation Capability



• Create unlimited sets of product costs, called cost types. Each cost type has its own items and specific cost controls for the items.• Copy from one cost type to another, mass edit a cost type, run item cost and comparison reports, roll up costs, or update frozen standard costs by cost type. Each cost type may have its own activities and activity-based costs.

Simultaneous Open Periods• Set up and maintain simultaneous open periods.• Run transactions for the next period and still report inventory balances and quantities from the prior open period using historical inventory valuation reports. This gives you the flexibility to reconcile and analyze the period before you close it, while you continue to conduct business in the subsequent period.

Period Close and General Ledger Transfer• Close the earliest open period at any time. Closing a period automatically transfers summary or detailed information to the general ledger.• Perform interim general ledger transfers at any time, without closing a period. The general ledger transfer passes all accounting entries not transferred since the last period close.

Accruals Booked on ReceiptOracle Purchasing updates the accounts payable accrual accounts automaticallyand accrues your uninvoiced receipts.



Cost Information


Cost Information

Cost rollup

Cost update

Engineering information

Cost ProcessesThere are two main processes in defining costs: cost updates and cost rollups.Costs are defined at the item level and the cost rollup process will determinecosts at the higher levels as defined in the bill of material. Typically, a series ofcost rollups are performed in order to:

• determine appropriate cost information at the higher bill of material levels• perform a cost update to freeze costs for the next period, when final costs

seem appropriate.Each of these processes runs exclusively to avoid conflict in processing, sincethere is a general ledger impact. As items are sold, a cost variance for a gain orloss is recorded in the general ledger.



Agenda


Agenda




Cost Type: Standard


Cost Type: Standard

CST_ACTIVITIESBOM_

RESOURCES

CST_COST_ELEMENTS

CST_ITEM_COST_DETAILS

CST_ITEM_COSTS

MTL_SYSTEM_ITEMS_B

CST_COST_TYPES


CST_COST_TYPESCST_COST_TYPES stores the cost type definition. Cost types represent sets ofcosts, frozen cost, or next year’s cost. The table is seeded with the followingcosts types:

• Frozen: The organization uses the standard costing method.• Pending: For standard cost organizations, Pending charges to the frozen

cost.• Average: The organization uses the average costing method.• FIFO: The organization uses the FIFO costing method.• LIFO: The organization uses the LIFO costing method.

You can define as many additional cost types as you want. The primary key isCOST_TYPE_ID.

CST_ITEM_COSTSCST_ITEM_COSTS stores the cost control information. The Define Item Costwindow inserts information into this table. The primary key isINVENTORY_ITEM_ID, ORGANIZATION_ID, COST_TYPE_ID.

CST_COST_ELEMENTS



CST_COST_ELEMENTS stores the cost element information. It is seeded withfive cost elements: Material, Material Overhead, Resource, Outside Processing,and Overhead. The primary key is COST_ELEMENT_ID.

CST_ITEM_COST_DETAILSCST_ITEM_COST_DETAILS stores detailed cost information for an item for acost type. It is the child table of CST_ITEM_COSTS. The primary key isINVENTORY_ITEM_ID, ORGANIZATION_ID, COST_TYPE_ID.

CST_ACTIVITIESCST_ACTIVITIES stores activity definitions. An activity can be organization-specific or shared among all organizations. The primary key is ACTIVITY_ID.

BOM_RESOURCESBOM_RESOURCES stores information about all cost subelements, resources,overhead, material overheads, and material subelements. COST_ELEMENT_IDdetermines the resource type. The primary key is RESOURCE_ID.



Cost Types: Average, FIFO, LIFO


Cost Types: Average, FIFO, LIFO

CST_ACTIVITIESBOM_

RESOURCES

CST_COST_ELEMENTS

CST_QUANTITY_LAYERS

CST_ITEM_COSTS

MTL_SYSTEM_ITEMS_B

CST_COST_TYPES

CST_LAYER_COST_DETAILS


CST_COST_TYPESCST_COST_TYPES stores the cost type definition. Cost types represent sets ofcosts, frozen cost, or next year’s cost. The table is seeded with the followingcosts types:




CST_ITEM_COSTSCST_ITEM_COSTS stores the cost control information. The Define Item Costform inserts information into this table. The primary key isINVENTORY_ITEM_ID, ORGANIZATION_ID, COST_TYPE_ID.

CST_COST_ELEMENTS



CST_COST_ELEMENTS stores the cost element information. It is seeded withfive cost elements: Material, Material Overhead, Resource, Outside Processing,and Overhead. The primary key is COST_ELEMENT_ID.

CST_QUANTITY_LAYERSCST_QUANTITY_LAYERS stores item average cost, FIFO, and LIFOinformation by cost layer. This table is only used for average costing, FIFO, andLIFO organizations. The primary key is LAYER_ID.

CST_LAYER_COST_DETAILSCST_LAYER_COST_DETAILS stores detailed cost information by elementand level. It is a child table of CST_QUANTITY_LAYERS. The primary key isLAYER_ID, COST_ELEMENT_ID, LEVEL_TYPE.

CST_ACTIVITIESCST_ACTIVITIES stores activity definitions. An activity can be organization-specific or shared among all organizations. The primary key is ACTIVITY_ID.

BOM_RESOURCESBOM_RESOURCES stores information about all cost subelements, resources,overhead, material overheads, and material subelements. COST_ELEMENT_IDdetermines the resource type. The primary key is RESOURCE_ID.



Oracle Cost Management Resource and OverheadCosts


Oracle Cost ManagementResource and Overhead Costs

BOM_RESOURCESBOM_RESOURCES

MATERIAL OVERHEAD

MATERIALOVERHEAD

RESOURCE/OUTSIDE

PROCESSING

CST_RESOURCE_OVERHEADS

CST_DEPARTMENT_OVERHEADS

BOM_DEPARTMENTS

CST_COST_TYPES

CST_RESOURCE_

COSTS

BOM_DEPARTMENTSBOM_DEPARTMENTS stores department information. DEPARTMENT_ID isthe primary key and uniquely identifies each row.

CST_RESOURCE_COSTSCST_RESOURCE_COSTS stores resource and outside processing resource unitcosts by a cost type. The primary key is RESOURCE_ID, COST_TYPE_ID.

CST_COST_TYPESCST_COST_TYPES stores the cost type definition. Cost types represent sets ofcosts, frozen cost, and next year’s cost. The table is seeded with the followingcosts types:




CST_RESOURCE_OVERHEADS



CST_RESOURCE_OVERHEADS stores the list of resources to which anoverhead applies. The cost processor looks at this table to find the overheadsthat need to be absorbed. The primary key is COST_TYPE_ID,RESOURCE_ID, OVERHEAD_ID.

CST_DEPARTMENT_OVERHEADSCST_DEPARTMENT_OVERHEADS stores overhead rates for a cost type.You can define overhead rates in the Define Overhead window. The primarykey is DEPARTMENT_ID, COST_TYPE_ID, OVERHEAD_ID.

BOM_RESOURCESBOM_RESOURCES stores information about resources, overhead, materialoverheads, and material subelements. COST_ELEMENT_ID determines theresource type. The primary key is RESOURCE_ID.



Item Cost Summary and Details


Item Cost Summary and DetailsOracle Cost Management is a full absorption, perpetual andperiodic cost system for purchasing, inventory, and work inprocess transactions. Cost Management automatically costsand values all inventory, work in process, and purchasingtransactions.

Item Costs Summary (M1) Item Costs Summary (M1)

CurrentEngineeringFrozenPending

Item Costs Details (M1) Item Costs Details (M1)

Current

(N) Cost > Item Costs > Item Costs



Practice 1 Setup


Practice 1 Setup

1 Assign Material and Material Overhead costs to yourpurchased items.

2 Assign Resource costs.3 Perform an Assembly Cost Rollup on your two Finished

Goods.4 Perform a Standard Cost Update for your Items.

Setup Instructions1 Assign Material and Material Overhead costs.

(N) Cost > Item Costs > Item Costs (B) Newa Enter your Finished Good item numbers, enter a cost type of Pending.b Save your work.c Enter your a Purchased item number, enter a cost type of Pending.d Click the Costs button.e Enter Material as your Cost Element.f Select an Amount.g Go to the next row down and select Material Overhead as your Cost

Element.i Select Mat’l Mgmt as your SubElement.j Select Total Value as your Basis.k Enter any decimal percentage ( e.g. 5% = .05) in the Rate/Amount field.l Save your work.

Repeat steps c through i for the remainder of your purchased items.2 Assign Resource costs

(N) Bills of Materials > Routings > Resourcesa Query up your resource.b Click the Costed & Standard Rate check boxes.



c Select the Absorption Account field, enter % and press the tab key.d Select one of the account numbers.e Select the Variance Account field, enter % and press the tab key.f Select one of the account numbers.g Click the Rates button, and select Pending as the Cost Type.h Enter a rate.i Save your work.

3 Perform Assembly Cost RollupN) Cost > Item Costs > Assembly Cost Rollup

a Select Single Requestb Select Cost Rollup - Print Report GUI for Request Namec In the Parameters form, select: 1) Cost Type = Pending 2) Range = Range of Items 3) Item From = Your Lower Finished Good Item (##-hot) 4) Item To = Your Upper Finished Good Item (##-mild)d Submit you request.e View your request.f When your request is complete, place your cursor on your job, click the

View Output button and see the rollup result.g Return to the Item Costs screen, query up all of your items, and note the

difference between Frozen and Pending costs.4 Perform Standard Cost Update

(N) Cost > Item Costs > Standard Cost Update > Update Costsa Select Cost Type of Pending.b Adjustment Account Alias of Std Cost Varc Description: update ## cost.d Item Range: Range of Itemse Update Option: Overhead, resource, activity and item costf Item From: Your Lowest Item (##-garlic)g Item To: Your Upper Item (##-tomato)h Click the Submit Request button.i When your request is complete, return to the Item Costs screen, query

your items and note Cost Update by using the horizontal scroll barbelow the table of item records.



Practice 1


Practice 1

Find the material and material overhead costs associated withyour items.


• Tables: mtl_system_items_b, cst_item_costs, cst_cost_types• Keys: segment1, cost_type, organization_id, cost_type_id, ventory_item_id• Columns: segment1, material_cost, material_overhead_cost, cost_type_id



Practice 1 Solution


Practice 1 Solution

Find the material and material overhead costs associated withyour items.


• substr(inv.segment1,1,10) “Item”,• substr(cst.material_cost,1,10) “Cost”,• substr(cst.material_overhead_cost,1,10) “Overhead”,• substr(typ.cost_type,1,10) “Type”

FROM• mtl_system_items_b inv,• cst_item_costs cst,• cst_cost_types typ

WHERE• inv.segment1 LIKE ‘&Item%’ AND• typ.cost_type LIKE ‘&Type%’ AND• inv.organization_id = 207 AND• cst.organization_id = inv.organization_id AND• inv.inventory_item_id = cst.inventory_item_id AND• cst.cost_type_id = typ.cost_type_id



Agenda


Agenda




Oracle Cost Management Open Interfaces


Oracle Cost ManagementOpen Interfaces

• Item Cost Inquiry• MFG Cost Reporting

Item Cost Inquiry Open InterfaceYou can create user-defined inquiries by associating a template type for eachquery. The template type determines which columns are displayed in the ViewItem Costs Summary window. For more detailed information, refer to theOracle Bills of Material Technical Reference Manual.

MFG Cost Reporting Open InterfaceYou can set detail options for all relevant Item Cost Reports information byusing this interface. A detail option specifies how to summarize item costs andwhich template to use to display the item costs. For more detailed information,refer to the Oracle Bills of Material Technical Reference Manual.



Oracle Cost Management Interface Tables


Oracle Cost Management Interface Tables

Interface Data Flow Table, View, Table, View, or Module nameName Direction or Process

Item Cost Outbound View CST_INQUIRY_TYPESInquiry CSTFQVIC (View Item Cost Information)MFG Cost Outbound View CST_REPORT_TYPESReporting CSTRFICR (Inventory Valuation Report)



Summary


Summary

In this lesson, you have learned how to relate themajor tables to Cost Management setup definitions:• Cost Information• Resources and Overhead• Interface Tables