OPM Administration Technical

Oracle ProcessManufacturing SystemAdministration TechnicalReference Manual

RELEASE 11i

December 1999

OPM System Administration Technical Reference Manual

Release 11i

To order this book, ask for Part No. A80885-01

Copyright © 1994, 1999. Oracle Corporation. All rights reserved.

Major Contributor: Michele-Andrea Fields

Contributors: Bill Stearns

This Technical Reference Manual (TRM) in any form, software or printed matter, contains proprietaryinformation of Oracle Corporation; it is provided under an Oracle Corporation agreement containingrestrictions on use and disclosure and is also protected by copyright, patent, and other intellectualproperty law. Restrictions applicable to this TRM include, but are not limited to: (a) exercising either thesame degree of care to safeguard the confidentiality of this TRM as you exercise to safeguard theconfidentiality of your own most important Confidential Information or a reasonable degree of care,whichever is greater; (b) maintaining agreements with your employees and agents that protect theConfidential Information of third parties such as Oracle Corporation and instructing such employees andagents of these requirements for this TRM; (c) restricting disclosure of this TRM to those of youremployees who have a ”need to know” consistent with the purposes for which this TRM was disclosedto you; (d) maintaining this TRM at all times on your premises; (e) not removing or destroying anyproprietary or confidential legends or markings placed upon this TRM in whatever form, software orprinted matter; and (f) not reproducing or transmitting this TRM in any form or by any means, electronicor mechanical, for any purpose, without the express written permission of Oracle Corporation. Youshould not use this TRM in any form, software or printed matter, to create software that performs thesame or similar functions as any Oracle Corporation products.

Program Documentation is licensed for use solely to support the deployment of the Programs and not forany other purpose.

The information in this TRM is subject to change without notice. If you find any problems in the TRM inany form, software or printed matter, please report them to us in writing. Oracle Corporation does notwarrant that this TRM is error-free. This TRM is provided to customer ”as-is” with no warranty of anykind. This TRM does not constitute Documentation as that term is defined in Oracle’s agreements.

Reverse engineering of the Programs (software and documentation) associated with this TRM areprohibited. The Programs associated with this TRM are not intended for use in any nuclear, aviation,mass transit, medical, or other inherently dangerous applications. It shall be licensee’s responsibility totake all appropriate fail-safe, back-up, redundancy and other measures to ensure the safe use of suchapplications if the Programs are used for such purposes, and Oracle disclaims liability for any damagescaused by such use of the Programs.

Restricted Rights LegendThis TRM and the Programs associated with this TRM delivered subject to the DOD FAR Supplement are’commercial computer software’ and use, duplication and disclosure of the TRM and the Programsassociated with this TRM shall be subject to the licensing restrictions set forth in the applicable Oraclelicense agreement. Otherwise, this TRM and the Programs associated with this TRM delivered subject tothe Federal Acquisition Regulations are ’restricted computer software’ and use, duplication anddisclosure of the TRM and the Programs associated with this TRM shall be subject to the restrictions inFAR 52.227-14, Rights in Data -- General, including Alternate III (June 1987). Oracle Corporation, 500Oracle Parkway, Redwood City, CA 94065.

Oracle is a registered trademark, and CASE*Exchange, Enabling the Information Age, Hyper*SQL,NLS*Workbench, Oracle7, Oracle8, Oracle 8i, Oracle Access, Oracle Application Object Library, OracleDiscoverer, Oracle Financials, Oracle Quality, Oracle Web Customers, Oracle Web Employees, OracleWork in Process, Oracle Workflow, PL/SQL, Pro*Ada, Pro*C, Pro*COBOL, Pro*FORTRAN, Pro*Pascal,Pro*PL/I, SmartClient, SQL*Connect, SQL*Forms, SQL*Loader, SQL*Menu, SQL*Net, SQL*Plus, andSQL*Report are trademarks or registered trademarks of Oracle Corporation. Other names may betrademarks of their respective owners.

CAUTIONThis Technical Reference Manual in any form -- software orprinted matter -- contains proprietary, confidentialinformation that is the exclusive property of OracleCorporation. If you do not have a valid contract withOracle for the use of this Technical Reference Manual orhave not signed a non-disclosure agreement with Oraclecovering this Technical Reference Manual, then youreceived this document in an unauthorized manner and arenot legally entitled to possess or read it.

Use, duplication, and disclosure are subject to restrictionsstated in your contract with Oracle Corporation.

Contents

1 Introduction

Overview .............................................................................................................................................. 1-2Finding the Latest Information ........................................................................................................ 1-2Audience............................................................................................................................................... 1-3How This Manual is Organized....................................................................................................... 1-3How to Use This Manual................................................................................................................... 1-3How Not To Use This Manual.......................................................................................................... 1-4About Oracle Application Object Library ..................................................................................... 1-5A Few Words About Terminology ................................................................................................... 1-5Other Information Sources ............................................................................................................... 1-7About Oracle...................................................................................................................................... 1-11Thank You .......................................................................................................................................... 1-11

2 High-Level Design

Overview of High-Level Design...................................................................................................... 2-2Summary Database Diagram...................................................................................................... 2-2Database Diagrams....................................................................................................................... 2-2Table Lists ...................................................................................................................................... 2-2View Lists ...................................................................................................................................... 2-3Module List.................................................................................................................................... 2-4

Summary Database Diagram ........................................................................................................... 2-5Database Diagramming Conventions ...................................................................................... 2-6

Database Diagrams............................................................................................................................. 2-7How to Use These Database Diagrams ..................................................................................... 2-8

v

Oracle Proprietary, Confidential Information--Use Restricted by Contract

Documents............................................................................................................................... ............. 2-9Language and Text ............................................................................................................................ 2-10Lookups ............................................................................................................................... ............... 2-11Organizations .................................................................................................................................... 2-12Purge and Archive ............................................................................................................................ 2-13Unit of Measure................................................................................................................................. 2-14Public Table List ................................................................................................................................ 2-15Public View List ................................................................................................................................ 2-17Module List ............................................................................................................................... ......... 2-17

Forms ............................................................................................................................................ 2-18Concurrent Programs................................................................................................................. 2-18

3 Detailed Design

Overview of Detailed Design ........................................................................................................... 3-2Table and View Definitions......................................................................................................... 3-2

Table and View Definitions ........................................................................................................... 3-2Foreign Keys.................................................................................................................................. 3-3QuickCodes Columns .................................................................................................................. 3-3Column Descriptions.................................................................................................................... 3-3Indexes............................................................................................................................................ 3-5Sequences ....................................................................................................................................... 3-6Database Triggers ......................................................................................................................... 3-6View Derivation ............................................................................................................................ 3-6GEM_LOOKUP_TYPES............................................................................................................... 3-7GEM_LOOKUP_VALUES........................................................................................................... 3-8GMA_ACTCOL_WF_B................................................................................................................ 3-9GMA_ACTCOL_WF_TL ........................................................................................................... 3-10GMA_ACTDATA_WF............................................................................................................... 3-11GMA_ACTDEF_WF................................................................................................................... 3-12IC_WHSE_MST........................................................................................................................... 3-13PS_PLNG_CLS ............................................................................................................................ 3-15SY_ADDR_MST .......................................................................................................................... 3-17SY_CMPY_MST .......................................................................................................................... 3-18SY_DOCS_MST........................................................................................................................... 3-19SY_DOCS_SEQ............................................................................................................................ 3-20

vi


SY_GEOG_MST .................................................................................................................... ...... 3-21SY_ORGN_MST.......................................................................................................................... 3-22SY_ORGN_USR .......................................................................................................................... 3-23SY_PARA_CDS_TL .................................................................................................................... 3-24SY_PURG_DEF ........................................................................................................................... 3-25SY_PURG_DEF_ACT................................................................................................................. 3-26SY_PURG_DEF_CRIT ................................................................................................................ 3-27SY_PURG_ERR ........................................................................................................................... 3-28SY_PURG_LOG .......................................................................................................................... 3-29SY_PURG_MST........................................................................................................................... 3-30SY_PURG_MST_CRIT ............................................................................................................... 3-32SY_REAS_CDS............................................................................................................................ 3-33SY_TEXT_HDR ........................................................................................................................... 3-34SY_TEXT_TBL_TL ...................................................................................................................... 3-35SY_TEXT_TKN_TL..................................................................................................................... 3-36SY_TRIGGER_ACTIVATION_WF .......................................................................................... 3-37SY_UOMS_MST.......................................................................................................................... 3-38SY_UOMS_STD........................................................................................................................... 3-39SY_UOMS_TYP........................................................................................................................... 3-40TX_TLOC_CDS ........................................................................................................................... 3-41

vii


viii


Send Us Your Comments

Oracle Process Manufacturing System Administration Technical ReferenceManualPart No. A80885-01

Oracle Corporation welcomes your comments and suggestions on the quality and usefulness of thispublication. Your input is an important part of the information used for revision.

� Did you find any errors?� Is the information clearly presented?� Do you need more information? If so, where?� Are the examples correct? Do you need more examples?� What features did you like most about this manual?

If you find any errors or have any other suggestions for improvement, please indicate the chapter,section, and page number (if available). You can send comments to us in the following ways:

� FAX: 650-506-7200 Attn: Oracle Process Manufacturing� Postal service:

Oracle CorporationOracle Process Manufacturing500 Oracle ParkwayRedwood City, CA 94065U.S.A.

If you would like a reply, please give your name, address, and telephone number below.

If you have problems with the software, please contact your local Oracle Support Services.

ix

x

Introd


1
Introduction
The Oracle Process Manufacturing System Administration Technical Reference Manualprovides the information you need to understand the underlying structure of OracleProcess Manufacturing (OPM). After reading this manual, you should be able toconvert your existing applications data, integrate your existing applications withOPM, and write custom reports for OPM, as well as read data that you need toperform other tasks.

This chapter introduces you to the Oracle Process Manufacturing SystemAdministration Technical Reference Manual, and explains how to use it.

uction 1-1

Overview

OverviewAt Oracle, we design and build applications using Oracle Designer, our systemsdesign technology that provides a complete environment to support developersthrough all stages of a systems life cycle. Because we use a repository-based designtoolset, all the information regarding the underlying structure and processing of ourapplications is available to us online. Using Oracle Designer, we can present thisinformation to you in the form of a technical reference manual.

This Oracle Process Manufacturing System Administration Technical Reference Manualcontains detailed, up-to-date information about the underlying structure of OPM.As we design and build new releases of OPM, we update our Oracle Designerrepository to reflect our enhancements. As a result, we can always provide youwith an Oracle Process Manufacturing System Administration Technical ReferenceManual that contains the latest technical information as of the publication date.Note that after the publication date we may have added new indexes to OPM toimprove performance.

About this ManualThis manual describes the Oracle Applications Release 11i data model, as used byOPM; it discusses the database we include with a fresh install of OracleApplications Release 11i. If you have not yet upgraded to Release 11, your databasemay differ from the database we document in this book.

If you have upgraded from a previous release, you might find it helpful to use thismanual with the appropriate Oracle Applications Product Update Notes manual. Theproduct update notes list database changes and seed data changes in OPM betweenreleases. The Oracle Applications Product Update Notes Release 11 manual describesthe changes between release 10.7 and release 11, and the Oracle Applications ProductUpdate Notes Release 11i manual describes the changes between release 11 andrelease 11i.

You can contact your Oracle representative to confirm that you have the latesttechnical information for OPM. You can also use OracleMetaLink which is accessiblethrough Oracle’s Support Web Center ( http://www.oracle.com/support/elec_sup ).

Finding the Latest InformationThe Oracle Process Manufacturing System Administration Technical Reference Manualcontains the latest information as of the publication date. For the latest informationwe encourage you to use OracleMetaLink which is accessible through Oracle’sSupport Web Center ( http://www.oracle.com/support/elec_sup ).

1-2 OPM System Administration Technical Reference Manual


How to Use This Manual

AudienceThe Oracle Process Manufacturing System Administration Technical Reference Manualprovides useful guidance and assistance to:

� Technical End Users

� Consultants

� Systems Analysts

� System Administrators

� Other MIS professionals

This manual assumes that you have a basic understanding of structured analysisand design, and of relational databases. It also assumes that you are familiar withOracle Application Object Library and OPM. If you are not familiar with the aboveproducts, we suggest that you attend one or more of the training classes availablethrough Oracle Education (see: Other Information Sources).

How This Manual is OrganizedThis manual contains two major sections, High-Level Design and Detailed Design.

High-Level DesignThis section, Chapter 2, contains database diagrams, and lists each database tableand view that OPM uses. This chapter also has a list of modules.

Detailed DesignThis section, Chapter 3, contains a detailed description of the OPM database design,including information about each database table and view you might need for yourcustom reporting or other data requirements.

How to Use This ManualThe Oracle Process Manufacturing System Administration Technical Reference Manual isa single, centralized source for all the information you need to know about theunderlying structure and processing of OPM. For example, you can use thismanual when you need to:

� Convert existing application data

� Integrate OPM with your other applications systems

Introduction 1-3


How Not To Use This Manual

� Write custom reports

� Define alerts against Oracle Applications tables

� Configure your Oracle Self-Service Web Applications

� Create views for decision support queries using query tools

� Create business views for Oracle Discoverer

You need not read this manual cover to cover. Use the table of contents and indexto quickly locate the information you need.

How Not To Use This Manual

Do not use this manual to plan modificationsYou should not use this manual to plan modifications to OPM. Modifying OPMlimits your ability to upgrade to future releases of OPM. In addition, it interfereswith our ability to give you the high-quality support you deserve.

We have constructed OPM so that you can customize it to fit your needs withoutprogramming, and you can integrate it with your existing applications throughinterface tables. However, should you require program modifications, you shouldcontact our support team (see: Other Information Sources). They can put you intouch with Oracle Services, the professional consulting organization of Oracle.Their team of experienced applications professionals can make the modificationsyou need while ensuring upward compatibility with future product releases.

Do not write data into non-interface tablesOracle reserves the right to change the structure of Oracle Applications tables, andto change the meaning of, add, or delete lookup codes and data in future releases.Do not write data directly into or change data in non-interface tables usingSQL*Plus or other programming tools because you risk corrupting your databaseand interfering with our ability to support you.

Moreover, this version of the Oracle Process Manufacturing System AdministrationTechnical Reference Manual does not contain complete information about thedependencies between OPM tables. Therefore, you should write data into onlythose tables we identify as interface tables. If you write data into othernon-interface tables, you risk violating your data integrity since you might notfulfill all the data dependencies in OPM.



A Few Words About Terminology

You are responsible for the support and upgrade of the logic within the proceduresthat you write, which may be affected by changes between releases of OracleApplications.

Do not rely on upward compatibility of the data modelOracle reserves the right to change the structure of OPM tables, and to change themeaning of, add, or delete lookup codes and other data in future releases. We donot guarantee the upward compatibility of the OPM data model. For example, ifyou write a report that identifies concurrent requests that end in Error status byselecting directly from Oracle Application Object Library tables, we do notguarantee that your report will work properly after an upgrade.

About Oracle Application Object LibraryThe Oracle Process Manufacturing System Administration Technical Reference Manualmay contain references to tables that belong to Oracle Application Object Library.Oracle Application Object Library is a collection of pre-built applicationcomponents and facilities for building Oracle Applications and extensions to OracleApplications. Oracle Application Coding Standards use the Oracle ApplicationObject Library and contains shared components including but not limited to --forms, subroutines, concurrent programs and reports, database tables and objects,messages, menus, responsibilities, flexfield definitions and online help.

A Few Words About TerminologyThe following list provides you with definitions for terms that we use throughoutthis manual:

RelationshipA relationship describes any significant way in which two tables may be associated.For example, rows in the Journal Headers table may have a one-to-manyrelationship with rows in the Journal Lines table.

Attention: Oracle does not support any customization of OracleApplication Object Library tables or modules, not even by Oracleconsultants. (Oracle Application Object Library tables generallyhave names beginning with FND_%.)

Accordingly, this manual does not contain detailed informationabout most Oracle Application Object Library tables used by OPM.

Introduction 1-5


A Few Words About Terminology

Database DiagramA database diagram is a graphic representation of application tables and therelationships between them.

Summary Database DiagramA summary database diagram shows the most important application tables and therelationships between them. It omits tables and relationships that contribute littleto the understanding of the application data model. Typically, a summary databasediagram shows tables that contain key reference and transaction data.

ModuleA module is a program or procedure that implements one or more businessfunctions, or parts of a business function, within an application. Modules includeforms, concurrent programs and reports, and subroutines.

Application Building BlockAn application building block is a set of tables and modules (forms, reports, andconcurrent programs) that implement closely-related database objects and theirassociated processing. Said another way, an application building block is a logicalunit of an application.

QuickCodesQuickCodes let you define general purpose, static lists of values for window fields.QuickCodes allow you to base your program logic on lookup codes whiledisplaying user-friendly names in a list of values window. QuickCodes simplifyname and language changes by letting you change the names your end users see,while the codes in your underlying programs remain the same.

FormA form is a module comprised of closely related windows that are used together toperform a task. For example, the Enter Journals form in Oracle General Ledgerincludes the Enter Journals window, the Batch window, and the More Actionswindow among others. The Enter Journals window is the main window, and fromit, you can use buttons to navigate to other windows in the form. The form nameusually corresponds to the main window in the form, and is frequently a windowyou open directly from the Navigator.



Other Information Sources

Other Information SourcesThere are additional information sources, including other documentation, trainingand support services, that you can use to increase your knowledge andunderstanding of Oracle Designer, Oracle Application Object Library, and OPM.We want to make these products easy for you and your staff to understand and use.

Oracle Designer Online DocumentationThe online help for Oracle Designer describes how you can use Oracle Designer foryour development needs.

Oracle Applications Developer’s GuideThis guide contains the coding standards followed by the Oracle Applicationsdevelopment staff. It describes the Oracle Application Object Library componentsneeded to implement the Oracle Applications user interface described in the OracleApplications User Interface Standards. It also provides information to help you buildyour custom Developer forms so that they integrate with Oracle Applications.

Oracle Applications User Interface StandardsThis manual contains the user interface (UI) standards followed by the OracleApplications development staff. It describes the UI for the Oracle Applicationsproducts and how to apply this UI to the design of an application built using OracleForms 6.

Oracle Process Manufacturing System Administration User’s GuideYour user guide provides you with all the information you need to use your Release11i OPM application. Each user guide is organized for fast, easy access to detailedinformation in a function- and task-oriented organization.

Oracle Self-Service Web Applications Online DocumentationThis documentation describes how Oracle Self-Service Web Applications enablecompanies to provide a self-service and secure Web interface for employees,customers, and suppliers. Employees can change their personal status, submitexpense reports, or request supplies. Customers can check on their orders, andsuppliers can share production schedules with their trading partners. Thisdocumentation is available in HTML only.

Introduction 1-7



Oracle Applications Flexfields GuideThis guide provides flexfields planning, setup and reference information for theOPM implementation team, as well as for users responsible for the ongoingmaintenance of Oracle Applications product data. This manual also providesinformation on creating custom reports on flexfields data.

Oracle Workflow GuideThis manual explains how to define new workflow business processes as well ascustomize existing Oracle Applications-embedded workflow processes. You alsouse this guide to complete the setup steps necessary for any Oracle Applicationsproduct that includes workflow-enabled processes.

Oracle Alert User GuideThis manual explains how to define periodic and event alerts to monitor the statusof your Oracle Applications data.

Multiple Reporting Currencies in Oracle ApplicationsIf you use the Multiple Reporting Currencies feature to report and maintainaccounting records in more than one currency, use this manual before implementingOPM. This manual details additional steps and setup considerations forimplementing OPM with this feature.

Multiple Organizations in Oracle ApplicationsIf you use the Oracle Applications Multiple Organization Support feature to usemultiple sets of books for one OPM installation, use this guide to learn about settingup and using OPM with this feature. This book describes the Oracle Applicationsorganization model, which defines business units and the relationships betweenthem in an arbitrarily complex enterprise. Functional and technical overviews ofmultiple organizations are presented, as well as information about how to set upand implement this feature set in the relevant Oracle Applications products.

Oracle Applications Messages ManualThe Oracle Applications Messages Manual contains the text of numbered errormessages in Oracle Applications. (Oracle Applications messages begin with theprefix ”APP-”.) It also provides information on the actions you take if you get amessage. Note: This manual is available only in HTML format.




Installation and System Administration

Oracle Applications Installation Release NotesThis manual contains a road map to the components of the release, includinginstructions about where to access the Release 11i documentation set.

Oracle Applications ConceptsDesigned to be the first book the user reads to prepare for an installation of OracleApplications. It explains the technology stack, architecture, features andterminology for Oracle Applications Release 11i. This book also introduces theconcepts behind and major uses of Applications-wide features such as MRC, BIS,languages and character sets (NLS, MLS), BIS, Self-Service Web Applications and soon.

Installing Oracle ApplicationsDescribes the One-Hour Install process, the method by which Release 11i will beinstalled. This manual includes all how-to steps, screen shots and informationabout Applications-wide post-install tasks.

Using the AD UtilitiesThis manual contains how-to steps, screen shots and other information required torun the various AD utilities such as AutoInstall, AutoPatch, AD Administration,AD Controller, Relink and so on. It also contains information about when and whyyou should use these utilities.

Upgrading Oracle ApplicationsThis manual contains all the product specific pre and post-upgrade steps that arerequired to upgrade products from Release 10.7 (NCA, SC and character-mode) orRelease 11 of Oracle Applications. This manual also contains an overview chapterthat describes all the tasks necessary to prepare and complete a upgrade of OracleApplications.

Oracle Applications System Administrator’s GuideThis manual provides planning and reference information for the OracleApplications System Administrator. It contains information on how to definesecurity, customize menus and manage concurrent processing.

Introduction 1-9



Oracle Applications Product Update NotesThis book contains a summary of each new feature we added since Release 11, aswell as information about database changes and seed data changes that may affectyour operations or any custom reports you have written. If you are upgrading fromRelease 10.7 you also need to read Oracle Applications Product Update Notes Release11.

Oracle Self-Service Web Applications Implementation ManualThis manual describes the setup steps for Oracle Self-Service Web Applications andthe Web Applications Dictionary.

Oracle Applications Implementation Wizard User GuideIf you are implementing more than one Oracle product, you can use the OracleApplications Implementation Wizard to coordinate your setup activities. Thisguide describes how to use the wizard.

Other Information

TrainingOracle Education offers a complete set of training courses to help you and your staffmaster Oracle Applications. We can help you develop a training plan that providesthorough training for both your project team and your end users. We will workwith you to organize courses appropriate to your job or area of responsibility.

Training professionals can show you how to plan your training throughout theimplementation process so that the right amount of information is delivered to keypeople when they need it the most. You can attend courses at any one of our manyEducational Centers, or you can arrange for our trainers to teach at your facility. Inaddition, we can tailor standard courses or develop custom courses to meet yourneeds.

SupportFrom on-site support to central support, our team of experienced professionalsprovides the help and information you need to keep OPM working for you. Thisteam includes your Technical Representative, Account Manager, and Oracle’s largestaff of consultants and support specialists with expertise in your business area,managing an Oracle server, and your hardware and software environment.



Thank You

About OracleOracle Corporation develops and markets an integrated line of software productsfor database management, applications development, decision support, and officeautomation, as well as Oracle Applications, an integrated suite of more than 75software modules for financial management, supply chain management,manufacturing, project systems, human resources, and sales and servicemanagement.

Oracle products are available for mainframes, minicomputers, personal computers,network computers, and personal digital assistants, allowing organizations tointegrate different computers, different operating systems, different networks, andeven different database management systems, into a single, unified computing andinformation resource.

Oracle is the world’s leading supplier of software for information management, andthe world’s second largest software company. Oracle offers its database, tools, andapplications products, along with related consulting, education, and supportservices, in over 145 countries around the world.

Thank YouThanks for using OPM and this technical reference manual!

We appreciate your comments and feedback. At the back of this manual is aReader’s Comment Form that you can use to explain what you like or dislike aboutOPM or this technical reference manual. Mail your comments to the followingaddress or call us directly at (650) 506-7000.

Oracle Applications Documentation Manager

Oracle Corporation

500 Oracle Parkway

Redwood Shores, California 94065

U.S.A.

Or, send electronic mail to [email protected].

Introduction 1-11


Thank You



High-Level D


2
High-Level Design
This chapter presents a high-level design for Oracle Process Manufacturing (OPM)that satisfies the business needs we specify during Strategy and Analysis. Itcontains database diagrams for OPM System Administration building blocks, listsof database tables and views, and a list of modules.

esign 2-1

Overview of High-Level Design

Overview of High-Level DesignDuring High-Level Design, we define the application components (tables, views,and modules) we need to build our application. We specify what applicationcomponents should do without specifying the details of how they should do it.

You can refer to this High-Level Design chapter to quickly acquaint yourself withthe tables, views, and modules that comprise OPM System Administration. And,you can prepare yourself to understand the detailed design and implementation ofOPM.

Summary Database DiagramThe Summary Database Diagram section graphically represents the most importantapplication tables and the relationships between them. It omits tables andrelationships that contribute little to the understanding of the application datamodel. Typically, a summary database diagram shows tables that contain keyreference and transaction data.

We prepare a summary database diagram to describe, at a conceptual level, the keyinformation on which our business depends. Later, we refine this summarydatabase diagram, breaking it into multiple database diagrams (generally, one perapplication building block) to represent all the tables and relationships we need toimplement our application in the database.

Review the Summary Database Diagram section to see at a glance the major tablesand relationships on which your application depends.

Database DiagramsThe Database Diagrams section graphically represents all OPM SystemAdministration tables and the relationships between them, organized by buildingblock.

Use this section to quickly learn what tables each OPM System Administrationbuilding block uses, and how those tables interrelate. Then, you can refer to theTable and View Definitions sections of Chapter 2 for more detailed informationabout each of those tables.

Table ListsThe Table List sections list the OPM System Administration tables. Because aproduct might not include at least one table for each type, this Technical ReferenceManualmight not include each of the following sections.




Public TablesUse the Public Table List section to quickly identify the tables you are mostinterested in. Then, you can refer to the Table and View Definitions sections ofChapter 2 for more detailed information about those tables.

In addition, this manual may contain full documentation for one or more of thefollowing Application Object Library tables: FND_DUAL, FND_CURRENCIES, andFND_COMMON_LOOKUPS.

Internal TablesThis section includes a list of private, internal tables used by OPM SystemAdministration; we do not provide additional documentation for these tables.

View ListsThe View List sections list the OPM System Administration views, with one sectionfor each type of view. Because a product might not include at least one view foreach type, this Technical Reference Manual might not include each of the followingsections.

Use this section to quickly identify the views you are most interested in. Then, youcan refer to the Table and View Definitions sections of Chapter 2 for more detailedinformation about those views.

Public ViewsThis section lists views that may be useful for your custom reporting or other datarequirements. The list includes a description of the view, and the page in Chapter 3that gives detailed information about the public view.

Web ViewsThis section lists views that you may need to configure your Self-Service Webapplications. The list includes a description of the view, and the page in Chapter 3that gives detailed information about the web view.

Forms and Table ViewsThis section lists supplementary views that are not essential to the Release 11i datamodel, but simplify coding or improve performance for Oracle Developer.

High-Level Design 2-3



Internal ViewsThis section includes each private, internal view that OPM System Administrationuses.

Single-Organization ViewsThis section lists the views that we added to take the place of various tables that arenow partitioned by operating unit, to support multiple sets of books within a singleinstallation of OPM.

Multiple Reporting Currency ViewsThis list includes views that were created to support the Multiple ReportingCurrencies feature.

MultiLingual ViewsThis section lists views that were created to allow certain seed data to be availablein multiple national languages simultaneously.

Module ListThe Module List section briefly describes each of the OPM System Administrationmodules. This section lists forms, reports, and concurrent programs.

A form is a module comprised of closely related windows that are used together toperform a task. For example, the Enter Journals form in Oracle General Ledgerincludes the Enter Journals window, the Batch window, and the More Actionswindow. The Enter Journals window is the main window, and from it, you can usebuttons to navigate to other windows in the form. The form name usuallycorresponds to the main window in the form, and is frequently a window you canopen directly from the Navigator.

The Reports and Concurrent Programs lists include processes you can submit fromthe Submit Requests window or other windows, as well as processes that aresubmitted automatically by OPM System Administration. Use your user’s guide tolearn more about reports and concurrent processes.



Summary Database Diagram

Summary Database DiagramThis Summary Database Diagram graphically represents the most important OPMSystem Administration tables and the relationships between them. It describes, at aconceptual level, the key information on which OPM depends.

This diagram does not represent the complete database implementation of OPMSystem Administration tables. It shows tables that contain key reference andtransaction data, and omits tables and relationships that contribute little to theunderstanding of the OPM data model. For example, a foreign key relationshipshown between two tables may actually be implemented by an intervening table,not shown in this diagram.

For more detailed graphical representations of OPM System Administration tablesand the relationships between them, see the Database DIagrams section in thischapter.



Summary Database Diagram

Database Diagramming ConventionsWe use the following notational conventions in our database diagrams:

Mandatory and Optional Foreign Keys

A Value entered in the column in the foreign keymust match a value in the primary key column.

��

��

��

��

��

��

� ��

��

��

�� !

��

"��#��$

%� ��

�� %��

&�� !��

'�� (�� !�� (� (��)��!� �!

��!� �!��"�$

��%� ��!��"�$

Server Model Diagram Elements and Notation

A Value entered in the column in the foreign keymust match either a value in the primary key column,or else it must be null.



Database Diagrams

Tables - are the basic unit of storage in the database. A hand symbol preceding thetitle in the table’s title bar indicates that the table is not owned by this applicationbut shared with another.

Foreign key constraint - is a type of referential integrity constraint for checking theintegrity of data entered in a specific column or set of columns. This specifiedcolumn or set of columns is known as the foreign key.

Delete rule indicator - determines the action to be taken when an attempt is made todelete a related row in a join table. A line through the foreign key constraint, asshown on the above diagram, indicates that this action is restricted.

Arcs - specify that, for any given row in a table, a value must be entered in one ofthe arc columns. The remaining columns within the arc must be null.

Database DiagramsThis section graphically represents all OPM System Administration tables and therelationships between them, organized by building block. Use this section toquickly learn what tables each OPM System Administration building block uses,and how these tables interrelate. Then, you can refer to the Table and ViewDefinitions sections of Chapter 2 for more detailed information about each of thosetables.

This section contains a database diagram for each of the following OPM SystemAdministration building blocks:

� Diagram 1:Documents

� Diagram 2:Language and Text

� Diagram 3:Lookups

� Diagram 4:Organizations

� Diagram 5:Purge and Archive

� Diagram 6:Unit of Measure

Some tables, especially important reference tables, appear in more than onedatabase diagram. When several building blocks use a table, we show that table ineach appropriate database diagram.



Database Diagrams

How to Use These Database DiagramsHere is an example of how you might use these database diagrams:

Suppose you want to write a custom application to interface your Oracle Payablesapplication with your non-Oracle purchasing system. You want to see how yourOracle Payables application matches an invoice to a purchase order. You turn toDiagram 3 to see the table structure for the Matching Invoices to Purchase Ordersbuilding block. You learn that each purchase order distribution line in PO_DISTRIBUTIONS may be used to create one or more invoice distribution lines inAP_INVOICE_DISTRIBUTIONS when you match an invoice to a purchase order.You can also see that your Oracle Payables application associates a matching holdon an invoice with a purchase order shipment through the PO_LINE_LOCATIONStable. Finally, you know that your Oracle Payables application matches invoices topurchase orders at the purchase order shipment level.

Next, you turn to the Table and View Definitions section in Chapter 2 to learn aboutthe columns in each of these tables and determine which columns are required formatching. Using this information, you write an application that allows your OraclePayables application to match invoices to purchase orders from your purchasingsystem.



Documents

Documents



Language and Text

Language and Text

ÿþýüûúüýùø÷

üûúüý��øû

ÿþýüûúüýü��ýü�

üûúüý�ûþ

��ý��øû

��û

ÿþýüûúüýü��ýü�

üûúüý��øû

��ý��øû

��÷��÷��ùý��øû

ÿ��ý��÷��øû

��ûý��

��û

ÿþý��÷�ý�øÿýü�

ü��ûý��û

��÷��÷��ùý��øû

ÿ��ý��÷��øû

��û



Lookups

Lookups

ÿþýüûúúù��ü��þ�

ûúúù��ü��þ

ÿþýüûúúù��ü��û�þ�

ûúúù��ü��þ

ûúúù��ü�ú�þ



Organizations

Organizations

ÿþýÿ

üûúýú

ùø

ÿ�þüû

úýú

ûù�

ø�ýû��ý�ø

�

�ø��ý�ù

û��ýú

ûù�

ø�ýû��ý�ø

ÿ

û��ýú

ûù�

ø�ýú��ý�ø

ÿ

úûýú

ûù�

ø�ý�ùù�ý�ø

ÿ

�ùù�ý�ù



Purge and Archive

Purge and Archive

ÿþýüûúùýøÿ÷ýöúõ÷

üûúù�ýõ�

öúõ÷ý÷�ù

ÿþýüûúùýøÿ÷

üûúù�ýõ�

ÿþýüûúùý��ù

üûúù�ýõ�

÷��ý��ø�

ÿþýüûúùý��ýöúõ÷

üûúù�ý÷þü�

öúõ÷ý÷�ù

ÿþýüûúùý��ý�ö÷


÷��ý��ø�

ÿþýüûúùý��


ÿþýüûúùý�úú

üûúù�ýõ�

�õ��ý��



Unit of Measure

Unit of Measure

ÿþýüûúÿýùþ�

üúýùþ��

ÿþýüûúÿýÿù�

üúýùþ��

ÿþýüûúÿýúÿù

üúý�û��



Public Table List

Public Table ListThis section lists each public database table that OPM System Administration usesand provides a brief description of each of those tables.

Note that ”public” tables are not necessarily intended for write access by customcode; Oracle Corporation supports write access using only standard OracleApplications forms, reports, and programs, or any SQL write access to tablesexplicitly documented as API tables. For more information, see the How Not To UseThis Manual section of this book’s Introduction.

OPM System Administration uses the following Public tables:

Table Name Description

FND_NEW_MESSAGES Application messages for Oracle Applications in GUI mode

FND_TABLES Tables registered in applications

FND_USER Application users

GEM_LOOKUP_TYPES OPM Lookups, formerly known as System Types.

GEM_LOOKUP_VALUES Stores the List of Values associated with Lookup Types.

GMA_ACTCOL_WF_B This table, will contain information associating a role definitiontothe corresponding table and fields to which the role will beassociated. Also Defines the hierarchy of the role .This serversas aseed data for the form where theactual data is associated toa specificrole.

GMA_ACTCOL_WF_TL Checks the availability of Activity Identification in GMA_ACTDEF_WF before inserting a row in GMA_ACTCOL_WF.

GMA_ACTDATA_WF This table will contain the actual data of the role association.User Role association with specific set of data is stored in thistable.

GMA_ACTDEF_WF This table is used to define the activity where a role has to be.

IC_WHSE_MST Warehouse master.This table contains warehouse definitioninformation.

PS_PLNG_CLS Planning class definitions.

SY_ADDR_MST Address master.

SY_CMPY_MST Stores Organization Definitions at a single level

SY_DOCS_MST Document master.

SY_DOCS_SEQ Document sequencing by organization.



Public Table List

SY_GEOG_MST Geographic regions.

SY_ORGN_MST Organization code master.

SY_ORGN_USR Associates OPM Organizations with FND users.

SY_PARA_CDS_TL Stores paragraph codes.

SY_PURG_DEF OPM Purge and Archive definitions are stored in this table.

SY_PURG_DEF_ACT Designates the Action to be performed by OPM Purge andArchive on a table by table basis

SY_PURG_DEF_CRIT Stores the Purge Criteria tags. These criteria are used todetermine what rows will be archived and purged.

SY_PURG_ERR Stores the database output from the GMA_PURGE_ENGINEpackage.

SY_PURG_LOG Stores OPM Purge and Archive statistics table by table based onPurge ID.

SY_PURG_MST Table storing data of all OPM Archives/Purges that have beenrun.

SY_PURG_MST_CRIT OPM Purge and Archive table used to store the criteria enteredspecific to a Purge ID.

SY_REAS_CDS The Reason Code table is used to store Reason Code definitionswhich provide information on the increase or decrease ininventory. Reason codes are used to flag transactions and attachreasons to them.

SY_TEXT_HDR Master table for creation and storage of OPM text codesassociated with GMA tables.

SY_TEXT_TBL_TL GMA product Text Lines (OPM System Administration).Descriptive text for all tables in this module. Also stores TextToken text.

SY_TEXT_TKN_TL Stores OPM Text Token definitions

SY_TRIGGER_ACTIVATION_WF

Used to store the detail information about theTriggersresponsible for Starting the Workflows and their Status (Enabled, Disabled ) of the individual triggers.

SY_UOMS_MST Unit of measure master for Oracle Process Manufacturing.Synchronized with MTL_UNITS_OF_MEASURE and associatedtables when Oracle Financials is used.

SY_UOMS_STD Table for associating Units of Measure and UOM Types. Not yetused.




Module List

Public View ListThis section lists each public database view that OPM System Administration usesand provides a brief description of each of those views. These views may be usefulfor your custom reporting or other data requirements.

OPM System Administration uses the following public views:

Module ListThis section lists each form, report and concurrent program comprising OPMSystem Administration.

SY_UOMS_TYP Unit of measure type master for Oracle Process Manufacturingproducts. Define unit of measure types here, which categorizeUnits of Measure. Synchronized with MTL_UOM_CLASSES.

TX_TLOC_CDS Tax Location Codes.

View Name Description

GEMMS_TABLES View of all tables owned by OPM

GEM_LOOKUPS View of all OPM lookups

GMA_ACTCOL_WF_VL This View will be the Used to fetch the data for Columnprompt.

SY_ADDR_MST_VW1 View of ADDR_ID + first two lines of the address

SY_PARA_CDS_VL

SY_TEXT_TBL_VL

SY_TEXT_TKN_VL




Module List

Forms

Concurrent Programs

SYADDED Address Edit

SYDOCED Document Type

SYDOCORD Document Ordering

SYGEOGED Geography Codes

SYLNGED Languages

SYLVMLU OPM Lookups

SYOPORGN User Organizations

SYOPRCLS Operator Planning Classes Form

SYORGED Organization Codes

SYPAAED2 Purge and Archive

SYPAASED Purge Setup

SYPAAVW1 Purge Inquiry

SYPARAED Paragraphs

SYREASED Reason Code

SYSESPAR Session Parameters

SYTKNED Text Tokens

SYTXTSEL Edit Text

SYUMTED UOM Type

SYUOMED Unit of Measure

SYPRGENG OPM Purge and Archive Process



Detailed D


3
Detailed Design
This chapter presents a detailed design for implementing Oracle ProcessManufacturing (OPM). It contains detailed definitions of tables and views that youmay need to reference to write custom reports or use for other data extraction.

esign 3-1

Overview of Detailed Design

Overview of Detailed DesignDuring Detailed Design, we specify in detail how each applications componentshould work. We prepare detailed definitions of tables and views.

You can refer to this Detailed Design chapter to gain a detailed understanding of theunderlying structure and processing of OPM that enables you to:

� Convert existing application data

� Integrate OPM with your other applications systems

� Write custom reports

� Define alerts against Oracle Applications tables

� Create views for decision support queries using query tools

� Configure your Oracle Self-Service Web Applications

Table and View DefinitionsThe Table and View Definitions section contains a detailed definition of OPM tables.For each table, it provides information about primary keys, foreign keys,QuickCodes, indexes, triggers, and sequences. It also gives you a detaileddescription of each column and its characteristics. In addition, it provides the SQLstatement that defines each view. Review this section to get a detailedunderstanding of what tables OPM System Administration contains, and how ituses them to hold and access the information it needs.

Table and View DefinitionsThis section contains a detailed description of each OPM System Administrationtable and view that you may need to reference. For each table, it presents detailedinformation about:

� Primary keys

� Foreign keys

� Column descriptions

� Indexes

� Oracle sequences

� Triggers



Table and View Definitions

� View derivations

Because Oracle does not support customization of Oracle Application ObjectLibrary tables, we do not provide you with detailed information about them.Consequently, this section does not document all the FND_% tables OPM uses.

The following sections appear in each table or view description:

Foreign KeysTo help you understand the relationships between tables, we list each foreign keycontained in a table. For each foreign key in a table, we list the primary key tablename (the table to which a foreign key refers), its corresponding primary keycolumns, and the foreign key columns that refer to those primary key columns.

When the primary key table has a composite primary key, we list each column ofthe composite key sequentially.

If a table contains two or more distinct foreign keys that refer to the same primarykey table, we repeat the primary key table name and list each of the distinct foreignkeys separately.

QuickCodes ColumnsWhen a database column contains a QuickCodes value, which we implement usinga foreign key to FND_LOOKUPS, MFG_LOOKUPS, or to some other lookup table,we list the QuickCodes type (lookup type) to which the QuickCodes value mustbelong and a complete list of QuickCodes values and meanings. Some QuickCodescan be defined by you in the application. These values are designated asUser-defined.

Column DescriptionsWe list the important characteristics of each column in a table or view. Thesecharacteristics include whether the column is part of the table’s primary key,whether Oracle8i requires a value for this column, and the data type of the column.We also give you a brief description of how OPM System Administration uses thecolumn.

When a column is part of a table’s primary key, we append the notation (PK) to thename of that column.

Detailed Design 3-3



To help you understand which columns OPM uses and which columns it does notuse, we alert you to any unused column. When no module uses a database column,we show one of the following legends in the Description column:

Standard Who ColumnsMost ORACLE PRODUCT applications tables contain standard columns to support\ Row Who. When your program or SQL*Plus command selects a row from atable, use these columns to determine who last updated the row. If your program orSQL*Plus command updates or inserts a row in an interface table, you mustpopulate each of the five standard Who columns:

Since every table containing Who columns has several foreign keys to the tablesFND_USER and FND_LOGINS, we do not include the foReign key columns LAST_UPDATED_BY, CREATED_BY, or LAST_UPDATE_LOGIN in a table’s list of foreignkeys.

Not currently used OPMdoes not use this column, although the columnmight be used in a future release.

No longer used OPMno longer uses this column. AutoInstall installs thiscolumn. Subsequent versions of OPM might not includethis column.

No longer installed OPMno longer uses this column. If you upgraded yoursoftware from an earlier version, you may still have thiscolumn, depending upon whether you chose to delete itduring an upgrade process. If you install OPM, you donot have this column.

LAST_UPDATE_DATE Date when a user last updated this row.

LAST_UPDATED_BY User who last updated this row (foreign key to FND_USER.USER_ID).

CREATION_DATE Date when this row was created.

CREATED_BY User who created this row (foreign key to FND_USER.USER_ID).

LAST_UPDATE_LOGIN Operating system login of user who last updated this row(foreign key to FND_LOGINS.LOGIN_ID). You shouldset this to NULL, or to 0 if NULL is not allowed.




Additional Who Columns for Concurrent ProgramsSome OPM tables also contain several additional Who columns to distinguishbetween changes a user makes with a form and changes a concurrent programmakes. When a concurrent program updates or inserts a row in a table, theconcurrent program populates the following additional Who columns:

Since every table containing these additional Who columns has severalforeign keys to the tables FND_CONCURRENT_REQUESTS, FND_APPLICATION, and FND_CONCURRENT_PROGRAM, we do notinclude the foreign key columns REQUEST_ID, PROGRAM_APPLICATION_ID, or PROGRAM_ID in a table’s list of foreign keys.

IndexesIf an OPM table uses an Oracle8i index, we list the database columns that comprisethat index, in sequential order.

REQUEST_ID Concurrent request ID of program that last updated thisrow (foreign key to FND_CONCURRENT_REQUESTS.REQUEST_ID).

PROGRAM_APPLICATION_ID Application ID of program that last updated this row(foreign key to FND_APPLICATION.APPLICATION_ID).

PROGRAM_ID Program ID of program that last updated this row(foreign key to FND_CONCURRENT_PROGRAM.CONCURRENT_PROGRAM_ID).

PROGRAM_UPDATE_DATE Date when a program last updated this row.

Note: The indexes we document in this manual correspond tounique keys we specified during product development and test-ing. In some cases, we may add additional indexes during theporting process to fine-tune performance on specific platforms;therefore, there may be minor differences between the indexesdocumented in this book and the indexes for production versions ofOPM.

Detailed Design 3-5



SequencesOPM uses Oracle8i sequence generators to generate unique integers. If any tablecolumn gets its value from an Oracle8i sequence generator, we list the name of thecorresponding sequence generator and the name of the column that stores theunique integer.

Database TriggersIf a table has one or more active database triggers, we provide a brief explanation ofeach database trigger and when it fires.

View DerivationFor each OPM view you may need to reference, we include important elementsfrom the SQL statement that defines or creates a view. By studying this viewdefinition, you can understand exactly how a view derives its contents.




GEM_LOOKUP_TYPESGEM_LOOKUP_TYPES stores Oracle Process Manufacturing Lookup types. Eachrow includes the lookup type and the application the lookup type belongs to. Eachrow also includes the customization level for the lookup type, the security groupthe lookup type belongs to, and the application view through with the lookup typewill be exposed. You need one row for each lookup type. This table is used todisplay LOVs on forms.

Column DescriptionsName Null Type Description

LOOKUP_TYPE_MEANING NULL VARCHAR2(80) Lookup Type meaningCUSTOMIZATION_LEVEL NOT NULL VARCHAR2(1) Customization level allowed by user: U: User, S:

System, E: ExtensibleAPPLICATION_ID NOT NULL NUMBER(15) Application ID of the product owning the Lookup

TypeLOOKUP_TYPE (PK) NOT NULL VARCHAR2(30) Name of the Lookup TypeSHARED_FLAG NOT NULL VARCHAR2(1) Indicator as to whether this Lookup Type is

shared among different productsCREATED_BY NOT NULL NUMBER(15) Standard Who columnCREATION_DATE NOT NULL DATE Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER(15) Standard Who columnLAST_UPDATE_LOGIN NULL NUMBER(15) Standard Who columnLAST_UPDATE_DATE NOT NULL DATE Standard Who column

Indexes

Index Name Index Type Sequence Column Name

GEM_LOOKUP_TYPES_PK UNIQUE 10 LOOKUP_TYPE

Detailed Design 3-7



GEM_LOOKUP_VALUESGEM_LOOKUP_VALUES stores Oracle Process Manufacturing lookup codes andvalues. Each row includes the lookup type, the lookup code, its meaning, andadditional description. Each row also includes a language code that indicates whatlanguage the information is in. You need one row for each lookup code in each ofthe languages installed at your site. OPM uses this information to display LOVs onforms.

Foreign Keys

Primary Key Table Primary Key Column Foreign Key Column

GEM_LOOKUP_TYPES LOOKUP_TYPE LOOKUP_TYPE


LOOKUP_TYPE (PK) NOT NULL VARCHAR2(30) Name of the Lookup TypeLOOKUP_CODE (PK) NOT NULL VARCHAR2(30) The Lookup Code associated with this lookupMEANING NOT NULL VARCHAR2(80) The meaning of the LookupDESCRIPTION NULL VARCHAR2(80) A description of the Lookup.ENABLED_FLAG NOT NULL VARCHAR2(1) Indicates whether or not this Lookup can be usedSTART_DATE_ACTIVE NULL DATE Date from when this record is active or useableEND_DATE_ACTIVE NULL DATE End date to when this record is active or useableCREATION_DATE NOT NULL DATE Standard Who columnCREATED_BY NOT NULL NUMBER(15) Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER(15) Standard Who columnLAST_UPDATE_DATE NOT NULL DATE Standard Who columnLAST_UPDATE_LOGIN NULL NUMBER(15) Standard Who column

Indexes


GEM_LOOKUP_VALUES_I1 NOT UNIQUE 1 LOOKUP_TYPE 3MEANING

GEM_LOOKUP_VALUES_PK UNIQUE 1 LOOKUP_TYPE 2LOOKUP_CODE




GMA_ACTCOL_WF_BThis table will contain information associating a role definition to thecorresponding table and fields to which the role will be associated. Also defines thehierarchy of the role. This serves as seed data for the form where the actual data isassociated to a specific role.


ACTIVITY_ID (PK) NOT NULL NUMBER(10) Activity Identification numberCOLUMN_HIERARCHY NULL NUMBER(3) Hierarchy of the fieldTABLE_NAME (PK) NOT NULL VARCHAR2(100) Table associated to the columnCOLUMN_NAME (PK) NOT NULL VARCHAR2(32) Column name to which the role name is associatedLOV_TABLE NOT NULL VARCHAR2(100) Table from where the values are validatedLOV_COLUMN NOT NULL VARCHAR2(200) List of columns to be appearing on LOVLAST_UPDATE_LOGIN NULL NUMBER(15) Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER(15) Standard Who columnCREATED_BY NOT NULL NUMBER(15) Standard Who columnCREATION_DATE NOT NULL DATE Standard Who columnLAST_UPDATE_DATE NOT NULL DATE Standard Who column

Indexes


GMA_ACTCOL_WF_B_PK NOT UNIQUE 1 ACTIVITY_ID 2TABLE_NAME 3 COLUMN_NAME

GMA_ACTCOL_WF_B_UK NOT UNIQUE 1 ACTIVITY_ID 2COLUMN_HIERARCHY

Detailed Design 3-9



GMA_ACTCOL_WF_TLChecks the availability of Activity Identification in GMA_ACTDEF_WF beforeinserting a row in GMA_ACTCOL_WF


ACTIVITY_ID NOT NULL NUMBER(10) Activity Identification NumberCOLUMN_HIERARCHY NULL NUMBER(5) Hierarchy of the fieldTABLE_NAME NOT NULL VARCHAR2(100) Table associated to the columnCOLUMN_NAME NOT NULL VARCHAR2(32) Column name to which the role name is associatedCOLUMN_PROMPT NOT NULL VARCHAR2(40) Column prompt to be displayedSOURCE_LANG NOT NULL VARCHAR2(4) MLS Support - source languageLANGUAGE NOT NULL VARCHAR2(4) MLS Suport - Current LanguageLAST_UPDATE_LOGIN NULL NUMBER(15) Standard Who columnLAST_UPDATE_DATE NOT NULL DATE Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER(15) Standard Who columnCREATED_BY NOT NULL NUMBER(15) Standard Who columnCREATION_DATE NOT NULL DATE Standard Who column

Indexes


GMA_ACTCOL_WF_TL_UK NOT UNIQUE 1 ACTIVITY_ID 3TABLE_NAME 5 COLUMN_NAME 10 LANGUAGE




GMA_ACTDATA_WFThis table will contain the actual data of the role association .User Role associationwith specific set of data is stored in this table.


ACTIVITY_ID NOT NULL NUMBER(10) Role Identfication numberCOLUMN_NAME1 NULL VARCHAR2(32) Column name1 to which the role name is associatedCOLUMN_VALUE1 NULL VARCHAR2(240) Column value 1 for the roleCOLUMN_NAME2 NULL VARCHAR2(32) Column name2 to which the role name is associatedCOLUMN_VALUE2 NULL VARCHAR2(240) Column value 2 for the roleCOLUMN_NAME3 NULL VARCHAR2(32) Column name3 to which the role name is associatedCOLUMN_VALUE3 NULL VARCHAR2(240) Column value 3 for the roleCOLUMN_NAME4 NULL VARCHAR2(32) Column name4 to which the role name is associatedCOLUMN_VALUE4 NULL VARCHAR2(240) Column value 4 for the roleCOLUMN_NAME5 NULL VARCHAR2(32) Column name5 to which the role name is associatedCOLUMN_VALUE5 NULL VARCHAR2(240) Column value 5 for the roleCOLUMN_NAME6 NULL VARCHAR2(32) Column name6 to which the role name is associatedCOLUMN_VALUE6 NULL VARCHAR2(240) Column value 6 for the roleCOLUMN_NAME7 NULL VARCHAR2(32) Column name7 to which the role name is associatedCOLUMN_VALUE7 NULL VARCHAR2(240) Column value 7 for the roleCOLUMN_NAME8 NULL VARCHAR2(32) Column name8 to which the role name is associatedCOLUMN_VALUE8 NULL VARCHAR2(240) Column value 8 for the roleCOLUMN_NAME9 NULL VARCHAR2(32) Column name9 to which the role name is associatedCOLUMN_VALUE9 NULL VARCHAR2(240) Column value 9 for the roleCOLUMN_NAME10 NULL VARCHAR2(32) Column name10 to which the role name is associ-

atedCOLUMN_VALUE10 NULL VARCHAR2(240) Column value 10 for the roleROLE NULL VARCHAR2(30) Column role value associatedLAST_UPDATE_LOGIN NULL NUMBER(15) Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER(15) Standard Who columnCREATED_BY NOT NULL NUMBER(15) Standard Who columnCREATION_DATE NOT NULL DATE Standard Who columnLAST_UPDATE_DATE NOT NULL DATE Standard Who column

Detailed Design 3-11



GMA_ACTDEF_WFThis table is used to define the activity where a role has to beresolved which will beused by a workflow and is to be resolved duringthe process of the workflow.


ACTIVITY_ID (PK) NOT NULL NUMBER(10) Activity Identification NumberWF_ITEM_TYPE NOT NULL VARCHAR2(8) Item Type of the WorkflowPROCESS_NAME NOT NULL VARCHAR2(100) Process name in the workflowACTIVITY_NAME NOT NULL VARCHAR2(100) Activity name to where the role is resolvedDESCRIPTION NULL VARCHAR2(240) Description of the processLAST_UPDATE_LOGIN NULL NUMBER(15) Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER(15) Standard Who columnLAST_UPDATE_DATE NOT NULL DATE Standard Who columnCREATED_BY NOT NULL NUMBER(15) Standard Who columnCREATION_DATE NOT NULL DATE Standard Who column

Indexes


GMA_ACTDEF_WF_PK NOT UNIQUE 1 ACTIVITY_ID

GMA_ACTDEF_WF_UK NOT UNIQUE 1 WF_ITEM_TYPE 2PROCESS_NAME 3ACTIVITY_NAME




IC_WHSE_MSTWarehouse master.This table contains warehouse definition information.

Foreign Keys


IC_TEXT_HDR TEXT_CODE TEXT_CODE

SY_ADDR_MST ADDR_ID ADDR_ID

SY_ORGN_MST ORGN_CODE ORGN_CODE

TX_TLOC_CDS TAXLOC_CODE TAXLOC_CODE


WHSE_CODE (PK) NOT NULL VARCHAR2(4) Code for the warehouse.WHSE_NAME NOT NULL VARCHAR2(40) Name of the warehouse.ORGN_CODE NOT NULL VARCHAR2(4) Organization that owns the warehouse.LOCT_CTL NOT NULL NUMBER(5) Location control indicator. 0=Warehouse is not

location controlled, 1=Validated location con-trol, 2=Non-validated location control.

ADDR_ID NULL NUMBER(10) Surrogate key to the address of the warehouse.CONSIGN_IND NOT NULL NUMBER(5) Consignment indicator. 0=Not a consigment ware-

house, 1=Consignment warehouse.NONNET_IND NOT NULL NUMBER(5) Not currently used.REGION_CODE NULL VARCHAR2(8) Region code.WHSE_CLASS NULL VARCHAR2(8) Warehouse class. Not currently validated.WHSE_CONTACT NULL VARCHAR2(40) Contact person at the warehouse.WHSE_PHONE NULL VARCHAR2(20) Phone number.TAXLOC_CODE NULL VARCHAR2(10) Tax location of warehouse.LAST_UPDATE_DATE NOT NULL DATE Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER(15) Standard Who columnCREATION_DATE NOT NULL DATE Standard Who columnCREATED_BY NOT NULL NUMBER(15) Standard Who columnTRANS_CNT NULL NUMBER(10) Not currently usedDELETE_MARK NOT NULL NUMBER(5) Standard: 0=Active record (default); 1=Marked

for (logical) deletion.TEXT_CODE NULL NUMBER(10) ID which joins any rows of text in this table to

the Text Table for this ModuleLAST_UPDATE_LOGIN NULL NUMBER(15) Standard Who columnINGREDIENT_STAGE NULL VARCHAR2(16) Staging location for ingredients.PRODUCT_STAGE NULL VARCHAR2(16) Staging location for products.RECV_STAGE NULL VARCHAR2(16) Staging location for receiving. Acts as default

location for receiving allocations.SHIP_STAGE NULL VARCHAR2(16) Staging location for shipping. Acts as default

location for shipment allocations.ATTRIBUTE1 NULL VARCHAR2(240) Descriptive flexfield segmentATTRIBUTE2 NULL VARCHAR2(240) Descriptive flexfield segmentATTRIBUTE3 NULL VARCHAR2(240) Descriptive flexfield segmentATTRIBUTE4 NULL VARCHAR2(240) Descriptive flexfield segmentATTRIBUTE5 NULL VARCHAR2(240) Descriptive flexfield segmentATTRIBUTE6 NULL VARCHAR2(240) Descriptive flexfield segmentATTRIBUTE7 NULL VARCHAR2(240) Descriptive flexfield segmentATTRIBUTE8 NULL VARCHAR2(240) Descriptive flexfield segmentATTRIBUTE9 NULL VARCHAR2(240) Descriptive flexfield segmentATTRIBUTE10 NULL VARCHAR2(240) Descriptive flexfield segmentATTRIBUTE11 NULL VARCHAR2(240) Descriptive flexfield segmentATTRIBUTE12 NULL VARCHAR2(240) Descriptive flexfield segment




ATTRIBUTE13 NULL VARCHAR2(240) Descriptive flexfield segmentATTRIBUTE14 NULL VARCHAR2(240) Descriptive flexfield segmentATTRIBUTE15 NULL VARCHAR2(240) Descriptive flexfield segmentATTRIBUTE16 NULL VARCHAR2(240) Descriptive flexfield segmentATTRIBUTE17 NULL VARCHAR2(240) Descriptive flexfield segmentATTRIBUTE18 NULL VARCHAR2(240) Descriptive flexfield segmentATTRIBUTE19 NULL VARCHAR2(240) Descriptive flexfield segmentATTRIBUTE20 NULL VARCHAR2(240) Descriptive flexfield segmentATTRIBUTE21 NULL VARCHAR2(240) Descriptive flexfield segmentATTRIBUTE22 NULL VARCHAR2(240) Descriptive flexfield segmentATTRIBUTE23 NULL VARCHAR2(240) Descriptive flexfield segmentATTRIBUTE24 NULL VARCHAR2(240) Descriptive flexfield segmentATTRIBUTE25 NULL VARCHAR2(240) Descriptive flexfield segmentATTRIBUTE26 NULL VARCHAR2(240) Descriptive flexfield segmentATTRIBUTE27 NULL VARCHAR2(240) Descriptive flexfield segmentATTRIBUTE28 NULL VARCHAR2(240) Descriptive flexfield segmentATTRIBUTE29 NULL VARCHAR2(240) Descriptive flexfield segmentATTRIBUTE30 NULL VARCHAR2(240) Descriptive flexfield segmentATTRIBUTE_CATEGORY NULL VARCHAR2(30) Descriptive flexfield segment

Indexes


IC_WHSE_MST_PK UNIQUE 10 WHSE_CODE




PS_PLNG_CLSPlanning class definitions. Items and operators can be associated to these tosupport report groupings for item activity by planning class.

Foreign Keys


IC_TEXT_HDR TEXT_CODE TEXT_CODE


PLANNING_CLASS (PK) NOT NULL VARCHAR2(8) Code for the planning class.PLANNING_CLASS_DESC NULL VARCHAR2(40) Description of the planning class.TEXT_CODE NULL NUMBER(10) ID which joins any rows of text in this table to

the Text Table for this ModuleTRANS_CNT NULL NUMBER(10) Not currently usedDELETE_MARK NOT NULL NUMBER(5)CREATED_BY NOT NULL NUMBER(15) Standard Who columnCREATION_DATE NOT NULL DATE Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER(15) Standard Who columnLAST_UPDATE_DATE NOT NULL DATE Standard Who columnLAST_UPDATE_LOGIN NULL NUMBER(15) Standard Who columnATTRIBUTE1 NULL VARCHAR2(240) Descriptive FlexfieldATTRIBUTE2 NULL VARCHAR2(240) Descriptive FlexfieldATTRIBUTE3 NULL VARCHAR2(240) Descriptive FlexfieldATTRIBUTE4 NULL VARCHAR2(240) Descriptive FlexfieldATTRIBUTE5 NULL VARCHAR2(240)ATTRIBUTE6 NULL VARCHAR2(240) Descriptive FlexfieldATTRIBUTE7 NULL VARCHAR2(240) Descriptive FlexfieldATTRIBUTE8 NULL VARCHAR2(240) Descriptive FlexfieldATTRIBUTE9 NULL VARCHAR2(240) Descriptive FlexfieldATTRIBUTE10 NULL VARCHAR2(240) Descriptive FlexfieldATTRIBUTE11 NULL VARCHAR2(240) Descriptive FlexfieldATTRIBUTE12 NULL VARCHAR2(240) Descriptive FlexfieldATTRIBUTE13 NULL VARCHAR2(240) Descriptive FlexfieldATTRIBUTE14 NULL VARCHAR2(240) Descriptive FlexfieldATTRIBUTE15 NULL VARCHAR2(240) Descriptive FlexfieldATTRIBUTE16 NULL VARCHAR2(240) Descriptive FlexfieldATTRIBUTE17 NULL VARCHAR2(240) Descriptive FlexfieldATTRIBUTE18 NULL VARCHAR2(240) Descriptive FlexfieldATTRIBUTE19 NULL VARCHAR2(240) Descriptive FlexfieldATTRIBUTE20 NULL VARCHAR2(240) Descriptive FlexfieldATTRIBUTE21 NULL VARCHAR2(240) Descriptive FlexfieldATTRIBUTE22 NULL VARCHAR2(240) Descriptive FlexfieldATTRIBUTE23 NULL VARCHAR2(240) Descriptive FlexfieldATTRIBUTE24 NULL VARCHAR2(240) Descriptive FlexfieldATTRIBUTE25 NULL VARCHAR2(240) Descriptive FlexfieldATTRIBUTE26 NULL VARCHAR2(240) Descriptive FlexfieldATTRIBUTE27 NULL VARCHAR2(240) Descriptive FlexfieldATTRIBUTE28 NULL VARCHAR2(240) Descriptive FlexfieldATTRIBUTE29 NULL VARCHAR2(240) Descriptive FlexfieldATTRIBUTE30 NULL VARCHAR2(240) Descriptive FlexfieldATTRIBUTE_CATEGORY NULL VARCHAR2(30) Descriptive Flexfield




Indexes


PS_PLNG_CLS_PK UNIQUE 1 PLANNING_CLASS




SY_ADDR_MSTOPM Address master. Table which stores addresses for all OracleProcessManufacturing applications entities.


ADDR_ID NOT NULL NUMBER(10) Surrogate id uniquely identifying an address.ADDR1 NULL VARCHAR2(70) First line of the address.ADDR2 NULL VARCHAR2(70) Second line of the address.ADDR3 NULL VARCHAR2(70) Third line of the address.ADDR4 NULL VARCHAR2(70) Fourth line of the address.STATE_CODE NULL VARCHAR2(4) State code of the address.COUNTRY_CODE NULL VARCHAR2(4) Country code of the address.POSTAL_CODE NULL VARCHAR2(16) Postal code of the address.PSEUDO_KEY NOT NULL VARCHAR2(70) Allows recreation of link to originating record

in case of table corruption.LAST_UPDATE_DATE NOT NULL DATE Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER(15) Standard Who columnCREATION_DATE NOT NULL DATE Standard Who columnCREATED_BY NOT NULL NUMBER(15) Standard Who columnCOMMENTS NULL VARCHAR2(40) Comment Field - unusedDELETE_MARK NOT NULL NUMBER(5) Standard: 0=Active record (default); 1=Marked for

(logical) deletion.TRANS_CNT NULL NUMBER(10) Not currently usedORA_ADDR4 NULL VARCHAR2(70) Address Line used for Oracle Financials Integra-

tionPROVINCE NULL VARCHAR2(70) Province codeCOUNTY NULL VARCHAR2(70) County codeLAST_UPDATE_LOGIN NULL NUMBER(15) Standard Who columnPROGRAM_APPLICATION_ID NULL NUMBER(15) Concurrent who columnPROGRAM_ID NULL NUMBER(15) Concurrent who columnPROGRAM_UPDATE_DATE NULL DATE Concurrent who columnREQUEST_ID NULL NUMBER(15) Concurrent who column

Indexes


SY_ADDR_MST_PK UNIQUE 10 ADDR_ID

Sequences

Sequence Derived Column

GEM5_ADDRESS_ID_S ADDR_ID




SY_CMPY_MSTStores Organization Definitions at a single level

Foreign Keys


SY_ORGN_MST ORGN_CODE CO_CODE


CO_CODE (PK) NOT NULL VARCHAR2(4) Company CodeCREATED_BY NOT NULL NUMBER(15) Standard Who columnCREATION_DATE NOT NULL DATE Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER(15) Standard Who columnLAST_UPDATE_DATE NOT NULL DATE Standard Who columnLAST_UPDATE_LOGIN NULL NUMBER(15) Standard Who column

Indexes


SY_CMPY_MST_PK UNIQUE 10 CO_CODE




SY_DOCS_MSTOracle Process Manufacturing Document master. This table stores documentdefinitionsused by inventory, resource and costing transactions in OPM.

Foreign Keys


SY_TEXT_HDR TEXT_CODE TEXT_CODE


DOC_TYPE (PK) NOT NULL VARCHAR2(4) Document type.DOC_DESC NOT NULL VARCHAR2(40) Description of the document in the default lan-

guage.DESC_ENGLISH NOT NULL VARCHAR2(40) Description of the document in english.DELETE_MARK NOT NULL NUMBER(5) Standard: 0=Active record (default); 1=Marked


the Text Table for this ModuleTRANS_CNT NULL NUMBER(10) Not currently usedCREATION_DATE NOT NULL DATE Standard Who columnCREATED_BY NOT NULL NUMBER(15) Standard Who columnLAST_UPDATE_DATE NOT NULL DATE Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER(15) Standard Who columnLAST_UPDATE_LOGIN NULL NUMBER(15) Standard Who column

Indexes


SY_DOCS_MST_PK UNIQUE 10 DOC_TYPE




SY_DOCS_SEQDocument sequencing by OPM organization. Maintains document numberassignment rules including auto assignment. Does not support blankpaddingcharacters.

Foreign Keys


SY_DOCS_MST DOC_TYPE DOC_TYPE


SY_ORGN_MST ORGN_CODE SY_DOCS_SEQ_ORGN_CODE

SY_ORGN_MST ORGN_CODE SY_DOCS_SEQ_ORGN_CODE2

SY_ORGN_MST ORGN_CODE SY_DOCS_SEQ_ORGN_CODE3



DOC_TYPE (PK) NOT NULL VARCHAR2(4) Document type for which the document sequencingrules are defined.

ORGN_CODE (PK) NOT NULL VARCHAR2(4) Organization for which document sequencing rulesare defined.

ASSIGNMENT_TYPE NOT NULL NUMBER(5) 1= manual assignment; 2=auto integer sequencing.LAST_ASSIGNED NULL NUMBER(10) Last integer assigned to the document inthe orga-

nization.FORMAT_SIZE NULL NUMBER(5) Size of the document number. Must be greater than

0, less than 11.PAD_CHAR NULL VARCHAR2(1) Padding character used for padding leading spaces

in the document number. Either blank or zero.DELETE_MARK NOT NULL NUMBER(5) Standard: 0=Active record (default); 1=Marked for

(logical) deletion.CREATION_DATE NOT NULL DATE Standard Who columnCREATED_BY NOT NULL NUMBER(15) Standard Who columnLAST_UPDATE_DATE NOT NULL DATE Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER(15) Standard Who columnTEXT_CODE NULL NUMBER(10) ID which joins any rows of text in this table to

the Text Table for this ModuleTRANS_CNT NULL NUMBER(10) Not currently usedDUMMY_FILL NULL VARCHAR2(255) Used to enlarge record so it fills more of a

logical database page.LAST_UPDATE_LOGIN NULL NUMBER(15) Standard Who columnSY_DOCS_SEQ_ORGN_CODE NULL VARCHAR2(4)SY_DOCS_SEQ_ORGN_CODE2 NULL VARCHAR2(4)SY_DOCS_SEQ_ORGN_CODE3 NOT NULL VARCHAR2(4)

Indexes


SY_DOCS_SEQ_PK UNIQUE 10 DOC_TYPE 20ORGN_CODE




SY_GEOG_MSTStores geographic regions used by Oracle Process Manufacturing entities. Theseregionsare classified by Country, State, Province and County.

Foreign Keys




GEOG_TYPE (PK) NOT NULL NUMBER(2) Type of Geographical Region. 1=Country, 2=State,3=Province, 4=County.

GEOG_ID NULL NUMBER Surrogate ID for composite PK - GEOG_TYPE + GEOG_CODE

GEOG_CODE (PK) NOT NULL VARCHAR2(4) Geography code such as state or country abbrevia-tions.

GEOG_DESC NOT NULL VARCHAR2(40) Description of geography code.DELETE_MARK NOT NULL NUMBER(5) Standard: 0=Active record (default); 1=Marked for

(logical) deletion.TEXT_CODE NULL NUMBER(10) ID which joins any rows of text in this table to


Indexes


SY_GEOG_MST_PK UNIQUE 10 GEOG_TYPE 20GEOG_CODE




SY_

SY_ORGN_MSTOrganization code (business unit) master for Oracle Process Manufacturing.Defineorganization codes and addresses here. This table is linked to HR_ORGANIZATION_UNITS by ORGANIZATION_ID, where a one to onerelationship exists.It also stores Resource Warehouse as used in the APS integration.

Foreign Keys


SY_ADDR_MST ADDR_ID ADDR_ID

SY_DOCS_SEQ ORGN_CODE SY_ORGN_MST_ORGN_CODE DOC_TYPEORGN_MST_DOC_TYPE

SY_ORGN_MST ORGN_CODE CO_CODE

SY_ORGN_MST ORGN_CODE PARENT_ORGN_CODE


TX_TLOC_CDS TAXLOC_CODE TAXLOC_CODE


ORGN_CODE (PK) NOT NULL VARCHAR2(4) Organization code.ORGN_NAME NOT NULL VARCHAR2(40) Organization name.PARENT_ORGN_CODE NOT NULL VARCHAR2(4) Orgn to which orgn_code reports. Must already

exist in the table.CO_CODE NOT NULL VARCHAR2(4) Company code of the organization.PLANT_IND NOT NULL NUMBER(5) 0=no the organization is not a plant; 1=yes the

organization is a plant.ADDR_ID NULL NUMBER(10) Surrogate of the organization address.ORGANIZATION_ID NOT NULL NUMBER(15) Foreign reference to HR_ORGANIZATION_UNITSTAXLOC_CODE NULL VARCHAR2(10) Tax Location Code for this organization (FK to

TX_TLOC_CDS)TEXT_CODE NULL NUMBER(10) ID which joins any rows of text in this table to

the Text Table for this ModuleDELETE_MARK NOT NULL NUMBER(5) Standard: 0=Active record (default); 1=Marked

for (logical) deletion.TRANS_CNT NOT NULL NUMBER(10) Not currently usedPOC_IND NOT NULL NUMBER(5) 0=Do not generate POC transactions for organiza-

tion; 1=Generate POC transactions for organiza-tion

CREATION_DATE NOT NULL DATE Standard Who columnCREATED_BY NOT NULL NUMBER(15) Standard Who columnLAST_UPDATE_DATE NOT NULL DATE Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER(15) Standard Who columnLAST_UPDATE_LOGIN NULL NUMBER(15) Standard Who columnRESOURCE_WHSE_CODE NULL VARCHAR2(4) Resource warehouse code associated to PlantsSY_ORGN_MST_ORGN_CODE NOT NULL VARCHAR2(4)SY_ORGN_MST_DOC_TYPE NOT NULL VARCHAR2(4)

Indexes


SY_ORGN_MST_PK UNIQUE 10 ORGN_CODE

SY_ORGN_MST_U1 UNIQUE 10 ORGANIZATION_ID




SY_ORGN_USRAssociates OPM Organizations with FND users. This dictates what OrganizationaUser has access to, limiting the ability to process transactions and vieworganizationspecific data where necessary.

Foreign Keys




USER_ID (PK) NOT NULL NUMBER(15) Foreign Key to FND_USERORGN_CODE (PK) NOT NULL VARCHAR2(4) Organization Code (Foreign key to SY_ORGN_MST)LAST_UPDATE_DATE NOT NULL DATE Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER(15) Standard Who columnCREATION_DATE NOT NULL DATE Standard Who columnCREATED_BY NOT NULL NUMBER(15) Standard Who columnLAST_UPDATE_LOGIN NULL NUMBER(15) Standard Who column

Indexes


SY_ORGN_USR_PK UNIQUE 10 USER_ID 20ORGN_CODE




_

SY_PARA_CDS_TLStores Oracle Process Manufacturing Paragraph Codes, which are used tocategorizetext entered against any row in any OPM table. Paragraphs can bedefined atmultiple levels, including by language and sub-paragraph code.

Foreign Keys


SY_TEXT_TBL_TL PARAGRAPH_CODE PARAGRAPH_CODE SUB_PARACODESUBPARACODE


TABLE_NAME (PK) NOT NULL VARCHAR2(32) Table nameLANG_CODE NOT NULL VARCHAR2(4) Indicates language used in text.PARAGRAPH_CODE (PK) NOT NULL VARCHAR2(4) Paragraph codeSUB_PARACODE (PK) NOT NULL NUMBER(5) Sub Paragraph codePARA_DESC NOT NULL VARCHAR2(70) Description of the Paragraph codeNONPRINTABLE_IND NOT NULL NUMBER(5) Indicates whether the paragraph is printableCREATION_DATE NOT NULL DATE Standard Who columnCREATED_BY NOT NULL NUMBER(15) Standard Who columnLAST_UPDATE_DATE NOT NULL DATE Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER(15) Standard Who columnLAST_UPDATE_LOGIN NULL NUMBER(15) Standard Who columnLANGUAGE (PK) NOT NULL VARCHAR2(4) The value stored in this column represents the

Language in which the data will be displayed.SOURCE_LANG NOT NULL VARCHAR2(4) The Language the text will mirror. If text is not

yet translated into LANGUAGE then any changes tothe text in the source language row will bereflected here as well.

SY_PARA_CDS_TL_TEXT_CODE NULL NUMBER(10)SY_PARA_CDS_TL_LANG_CODE NULL VARCHAR2(4)SY_PARA_CDS_TL_PARAGRAPH_CODE NULL VARCHAR2(4)SY_PARA_CDS_TL_SUB_PARACODE NULL NUMBER(5)SY_PARA_CDS_TL_LINE_NO NULL NUMBER(5)SY_PARA_CDS_TL_LANGUAGE NULL VARCHAR2(4)

Indexes


SY_PARA_CDS_TL_PK UNIQUE 10 TABLE_NAME 20PARAGRAPH_CODE 30SUB_PARACODE 40 LANGUAGE




SY_PURG_DEFOPM Purge and Archive definitions are stored in this table.

Foreign Keys




PURGE_TYPE (PK) NOT NULL VARCHAR2(4) Purge Type - the name of the Purge and Archiveroutine (eg, PROD).

SQLSTATEMENT NOT NULL LONG The sql statement used to select the rows to bearchived or purged.

PURGE_CLASS NOT NULL VARCHAR2(1) Differentiates standard, pre-defined purges fromuser-defined purges. S = Standard Purge, Blankor Other = User Defined purge

PURGE_DESC NOT NULL VARCHAR2(255) Description of the Purge TypeCREATION_DATE NOT NULL DATE Standard Who columnCREATED_BY NOT NULL NUMBER(15) Standard Who columnLAST_UPDATE_DATE NOT NULL DATE Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER(15) Standard Who columnTRANS_CNT NULL NUMBER(10) Not currently usedDELETE_MARK NOT NULL NUMBER(5) Standard: 0=Active record (default); 1=Marked for


the Text Table for this ModuleLAST_UPDATE_LOGIN NULL NUMBER(15) Standard Who columnWORK_TABLESPACE NULL VARCHAR2(30) Tablespace to use for P/A temporary tables

(defaults to user’s default tablespace if null).DEFAULT_TARGET_TABLESPACE NULL VARCHAR2(30) Tablespace to use for P/A target tables (defaults

to user’s default tablespace if null). Can beoverridden at the table level through sy_purg_def_act.

Indexes


SY_PURG_DEF_PK UNIQUE 10 PURGE_TYPE




SY_PURG_DEF_ACTDesignates the Action to be performed by OPM Purge and Archive on a table bytable basis.

Foreign Keys


SY_PURG_DEF PURGE_TYPE PURGE_TYPE




TABLE_NAME (PK) NOT NULL VARCHAR2(32) Table to be archived or purgedACTION NULL VARCHAR2(1) Not UsedCREATION_DATE NOT NULL DATE Standard Who columnCREATED_BY NOT NULL NUMBER(15) Standard Who columnLAST_UPDATE_DATE NOT NULL DATE Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER(15) Standard Who columnARCHIVE_ACTION NOT NULL VARCHAR2(1) D = Delete rows after they are archived. K =

Keep rows after they are archivedTRANS_CNT NULL NUMBER(10) Not currently usedDELETE_MARK NOT NULL NUMBER(5)TEXT_CODE NULL NUMBER(10) ID which joins any rows of text in this table to

the Text Table for this ModuleLAST_UPDATE_LOGIN NULL NUMBER(15) Standard Who columnTARGET_TABLESPACE NULL VARCHAR2(30) Tablespace to use for *this* table. If null,

defaults to sy_purg_def.default_target_tablespace, then user’s default tablespace.

Indexes


SY_PURG_DEF_ACT_PK UNIQUE 10 PURGE_TYPE 20TABLE_NAME




SY_PURG_DEF_CRITStores the Purge Criteria tags. These criteria are used to determinewhat rows willbe archived and purged.

Foreign Keys






CRIT_TAG (PK) NOT NULL VARCHAR2(32) Criteria tag. Serves as a placeholder whereselection criteria will be entered

DEFAULT_VALUE NULL VARCHAR2(32) Default value for the Criteria Tag. DefaultValue is Blank, but can be updated by the enduser.

MASK NULL VARCHAR2(120) Not UsedDESCRIPTION NULL VARCHAR2(80) Description of what criteria should be entered

for a field on the form (eg, Enter OperatorCode). This will be displayed at the time of cri-teria entry.

CREATION_DATE NOT NULL DATE Standard Who columnCREATED_BY NOT NULL NUMBER(15) Standard Who columnLAST_UPDATE_DATE NOT NULL DATE Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER(15) Standard Who columnTRANS_CNT NULL NUMBER(10) Not currently usedDELETE_MARK NOT NULL NUMBER(5) Standard: 0=Active record (default); 1=Marked for


the Text Table for this ModuleLAST_UPDATE_LOGIN NULL NUMBER(15) Standard Who columnVALUE_MASK NOT NULL VARCHAR2(120) Will handle masking of data in order to feed Cri-

teria to SQL statement during execution (eg,CHAR, DATE, NUMBER).

Indexes


SY_PURG_DEF_CRIT_PK UNIQUE 10 PURGE_TYPE

20 CRIT_TAG




SY_PURG_ERRStores the database output from the OPM Purge and Archive utility, specifically theGMA_PURGE_ENGINE package.

Foreign Keys


SY_PURG_MST PURGE_ID PURGE_ID


PURGE_ID (PK) NOT NULL NUMBER(5) Unique identifier for each purge.LINE_NO (PK) NOT NULL NUMBER Line number of error message.CREATED_BY NOT NULL NUMBER(15) Standard Who columnLAST_UPDATE_DATE NOT NULL DATE Standard Who columnCREATION_DATE NOT NULL DATE Standard Who columnLAST_UPDATE_LOGIN NULL NUMBER(15) Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER(15) Standard Who columnTEXT NULL VARCHAR2(80) Error text associated with the purge ID.

Indexes


SY_PURGE_ERR_PK UNIQUE 1 PURGE_ID

2 LINE_NO

Sequences


GEM5_SY_PURG_ERR_LINE_S LINE_NO




SY_PURG_LOGStores OPM Purge and Archive statistics table by table based on Purge ID.

Foreign Keys




PURGE_ID (PK) NOT NULL NUMBER(5) Unique identifier for each purge.TABLE_NAME (PK) NOT NULL VARCHAR2(32) Table that was archived or purged.ROWS_ARCHIVED NOT NULL NUMBER(10) Number of rows archived for this purge_id/table.ROWS_DELETED NOT NULL NUMBER(10) Number of rows deleted for this purge_id/table.CREATION_DATE NOT NULL DATE Standard Who columnCREATED_BY NOT NULL NUMBER(15) Standard Who columnLAST_UPDATE_LOGIN NULL NUMBER(15) Standard Who columnLAST_UPDATE_DATE NOT NULL DATE Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER(15) Standard Who column

Indexes


SY_PURGE_LOG_PK NOT UNIQUE 1 PURGE_ID

2 TABLE_NAME




SY_PURG_MSTTable storing data of all OPM Archives/Purges that have been run

Foreign Keys





PURGE_ID (PK) NOT NULL NUMBER(5) Unique identifier for each purge.PURGE_TYPE NOT NULL VARCHAR2(4) Purge Type - the name of the Purge and Archive

routine (eg, PROD).STATUS NOT NULL NUMBER(5) No longer used. Purge Status used instead.PURGE_COMMENT NULL VARCHAR2(256) User entered purge comment.ROWS_ARCHIVED NULL NUMBER(10) Number of rows archived for this purge_id.ROWS_DELETED NULL NUMBER(10) Number of rows deleted for this purge_id.ARCHIVE_START_TIME NULL DATE Date and Time Archive process began.ARCHIVE_ELAPSED_TIME NULL NUMBER(38) Elapsed time ONLY FOR ARCHIVE (in seconds).CREATION_DATE NOT NULL DATE Standard Who columnCREATED_BY NOT NULL NUMBER(15) Standard Who columnLAST_UPDATE_DATE NOT NULL DATE Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER(15) Standard Who columnORA_STATUS NULL NUMBER Oracle Error message numberPURGE_START_TIME NULL DATE Date and Time Purge process began.PURGE_ELAPSED_TIME NULL NUMBER(38) Elapsed time ONLY FOR PURGE (in seconds).TRANS_CNT NULL NUMBER(10) Not currently usedDELETE_MARK NOT NULL NUMBER(5) Standard: 0=Active record (default); 1=Marked for


the Text Table for this ModuleLAST_UPDATE_LOGIN NULL NUMBER(15) Standard Who columnSELECTION_ELAPSED_TIME NULL NUMBER(38) Time in seconds for P/A row selectionCOPY_ELAPSED_TIME NULL NUMBER(38) Time in seconds for copy functionROWS_PER_SECOND NULL NUMBER(38) Rows per second using end to end P/A execution

time (includes selection time).COPY_ROWS_PER_SECOND NULL NUMBER(38) Rows per second * just* usin copy time. Probably

represents a platform dependent constant. Per-formance increases as rows_per_second approachescopy_rows_per_second.

DEBUG_FLAG NULL VARCHAR2(1) If set to ’T’, adds debuggin information tologged output. Basically, this means that thegenerated SQL is output for analysis.

DISABLE_CONSTRAINTS_FLAG NULL VARCHAR2(1) If set to ’T’, disables constraints as appropri-ate before the copy function starts and restoresthem after the end of the ocpy function. ’Asappropriate’, means that if a table is marked fordelete, constraints are disabled.This greatlyspedd performance. This requires that the purgedefinition respects data integrity constraints(as it should be).

CALCULATE_STORAGE_FLAG NULL VARCHAR2(1) If set to ’T’, calcuates the size of targettables before the copy function and attempts toallocate the entire space. Failure to do so will*not* stop archiver; archiver will then just use’standard’ method.




COMMIT_FREQUENCY NULL NUMBER Store value that designates how often to commit.Advanced users may find that this settin affectscopy_rows_per_second. Defaults to 1000 if notspecified.

PURGE_STATUS NOT NULL NUMBER(5) 0= Defined, not yet run. 1= Archive in progress.2= Archived Successfully. 3= Purge in progress.4= Purge Completed Successfully. -1= Archiveprocess failed. -3=Purge process failed.

OBJECT_OWNER NULL VARCHAR2(30)ARCHIVE_TABLE_COUNT NULL NUMBER

Indexes


SY_PURG_MST_PK UNIQUE 10 PURGE_ID

Sequences


GEM5_SY_PURGE_ID_S PURGE_ID




SY_PURG_MST_CRITOPM Purge and Archive table used to store the criteria entered specific to a PurgeID.

Foreign Keys





PURGE_ID (PK) NOT NULL NUMBER(5) Unique identifier for each purge.CRIT_TAG (PK) NOT NULL VARCHAR2(32) Criteria tag. Serves as a placeholder where

selection criteria will be entered.CRIT_VALUE NOT NULL VARCHAR2(32) User entered value against criteria tag for this

purge_id.CREATION_DATE NOT NULL DATE Standard Who columnCREATED_BY NOT NULL NUMBER(15) Standard Who columnLAST_UPDATE_DATE NOT NULL DATE Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER(15) Standard Who columnTRANS_CNT NULL NUMBER(10) Not currently usedDELETE_MARK NOT NULL NUMBER(5) Standard: 0=Active record (default); 1=Marked for


the Text Table for this ModuleLAST_UPDATE_LOGIN NULL NUMBER(15) Standard Who column

Indexes


SY_PURG_MST_CRIT_PK UNIQUE 10 PURGE_ID

20 CRIT_TAG




SY_REAS_CDSThe Reason Code table is used to store Reason Code definitions which provideinformation on the increase or decrease in inventory. Reason codes are used to flagtransactions and attach reasons to them.

Foreign Keys




REASON_CODE (PK) NOT NULL VARCHAR2(4) Reason code.REASON_DESC1 NOT NULL VARCHAR2(40) Description of the reason code.REASON_DESC2 NULL VARCHAR2(70) Description of the reason code (not used).REASON_TYPE NOT NULL NUMBER(5) Indicates change type for the reason.FLOW_TYPE NOT NULL NUMBER(5) Indicates inventory flow. -1=inflow; 1=outflow;

0=usage; 2=exclude.AUTH_STRING NULL VARCHAR2(90) Unused.DELETE_MARK NOT NULL NUMBER(5) Standard: 0=Active record (default); 1=Marked



Indexes


SY_REAS_CDS_PK UNIQUE 10 REASON_CODE




SY_TEXT_HDRMaster table for creation and storage of OPM text codes associated with GMAtables.


TEXT_CODE (PK) NOT NULL NUMBER(10) Surrogate key for this record. ID which joinsany rows of text in this table to the Text Tablefor this Module

LAST_UPDATED_BY NOT NULL NUMBER(15) Standard Who columnCREATED_BY NOT NULL NUMBER(15) Standard Who columnLAST_UPDATE_DATE NOT NULL DATE Standard Who columnCREATION_DATE NOT NULL DATE Standard Who columnLAST_UPDATE_LOGIN NULL NUMBER(15) Standard Who column

Indexes


SY_TEXT_HDR_PK UNIQUE 10 TEXT_CODE




SY_TEXT_TBL_TLGMA product Text Lines (OPM System Administration). Descriptive text for alltables in this module. Also storesText Token text.


TEXT_CODE (PK) NOT NULL NUMBER(10) ID which joins any rows of text in this table tothe Text Table for this Module

LANG_CODE (PK) NOT NULL VARCHAR2(4) Indicates language used in text.PARAGRAPH_CODE (PK) NOT NULL VARCHAR2(4) Defined in sy_para_cds.SUB_PARACODE (PK) NOT NULL NUMBER(5) Defined in sy_para_cds.LINE_NO (PK) NOT NULL NUMBER(5) Line number which allows multiple lines of

descripitive text for underlying record. -1 =line is used to recreate key of underlyingrecord; 1

TEXT NULL VARCHAR2(70) Descriptive text.LANGUAGE (PK) NOT NULL VARCHAR2(4) The value stored in this column represents the


yet translated into LANGUAGE thenany changes tothe text in the source language row will bereflected here as well.

LAST_UPDATED_BY NOT NULL NUMBER(15) Standard Who columnCREATED_BY NOT NULL NUMBER(15) Standard Who columnLAST_UPDATE_DATE NOT NULL DATE Standard Who columnCREATION_DATE NOT NULL DATE Standard Who columnLAST_UPDATE_LOGIN NULL NUMBER(15) Standard Who column

Indexes


SY_TEXT_TBL_TL_PK UNIQUE 10 TEXT_CODE

20 LANG_CODE

30 PARAGRAPH_CODE

40 SUB_PARACODE

50 LINE_NO

60 LANGUAGE




SY_TEXT_TKN_TLStores OPM Text Token definitions


TEXT_KEY (PK) NOT NULL VARCHAR2(32) Text Token NameLANG_CODE (PK) NOT NULL VARCHAR2(4) Indicates language used in text.TEXT_CODE NULL NUMBER(10) ID which joins any rows of text in this table to

the Text Table for this ModuleTOKEN_DESC NOT NULL VARCHAR2(70)CREATION_DATE NOT NULL DATE Standard Who columnCREATED_BY NOT NULL NUMBER(15) Standard Who columnLAST_UPDATE_DATE NOT NULL DATE Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER(15) Standard Who columnLAST_UPDATE_LOGIN NULL NUMBER(15) Standard Who columnLANGUAGE (PK) NOT NULL VARCHAR2(4) The value stored in this column represents the


yet translated into LANGUAGE then any changes tothe text in the source language row will bereflected here as well.

Indexes


SY_TEXT_TKN_TL_PK UNIQUE 10 TEXT_KEY

20 LANG_CODE

30 LANGUAGE




SY_TRIGGER_ACTIVATION_WFUsed to store the detail information about theTriggers responsible for Starting theWorkflows and their Status ( Enabled, Disabled ) of the individual triggers.


WF_ITEM_TYPE (PK) NOT NULL VARCHAR2(8) Workflow Item TypeWF_DESCRIPTION NOT NULL VARCHAR2(80) Workflow descriptionTRIGGER_NAME (PK) NOT NULL VARCHAR2(30) Trigger responsible for the workflowTRIGGER_DESCRIPTION NOT NULL VARCHAR2(40) Trigger descriptionENABLE_FLAG NOT NULL NUMBER(5) Indicates whether the trigger is enabled or not.LAST_UPDATED_BY NOT NULL NUMBER(15) Standard Who columnCREATED_BY NOT NULL NUMBER(15) Standard Who columnLAST_UPDATE_LOGIN NULL NUMBER(15) Standard Who columnCREATION_DATE NOT NULL DATE Standard Who columnLAST_UPDATE_DATE NOT NULL DATE Standard Who column

Indexes


SY_TRIGGER_ACTIVATION_WF_PK NOT UNIQUE 5 WF_ITEM_TYPE

7 TRIGGER_NAME




SY_UOMS_MSTUnit of measure master for Oracle Process Manufacturing. Synchronized withMTL_UNITS_OF_MEASURE and associated tables when Oracle Financials is used.

Foreign Keys



SY_UOMS_TYP UM_TYPE UM_TYPE


UM_CODE (PK) NOT NULL VARCHAR2(4) Unit of Measure code for which the conversion isdefined.

UM_DESC NOT NULL VARCHAR2(40) Description of the Unit of MeasureUM_TYPE NOT NULL VARCHAR2(10) The Unit of Measure Type associated with each

Unit of MeasureSTD_FACTOR NOT NULL NUMBER Conversion factor to the reference UOM of the

same Type.RND_FACTOR NOT NULL NUMBER Unused, defaulted to 0.REF_UM NULL VARCHAR2(4) Reference Unit of Measure for the same Unit of

Measure Type.LAST_UPDATE_DATE NOT NULL DATE Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER(15) Standard Who columnCREATION_DATE NOT NULL DATE Standard Who columnCREATED_BY NOT NULL NUMBER(15) Standard Who columnTEXT_CODE NULL NUMBER(10) ID which joins any rows of text in this table to


for (logical) deletion.TRANS_CNT NULL NUMBER(10) Not currently usedLAST_UPDATE_LOGIN NULL NUMBER(15) Standard Who column

Indexes


SY_UOMS_MST_PK UNIQUE 10 UM_CODE




SY_UOMS_STDTable for associating Units of Measure and UOM Types. Not yet used.

Foreign Keys


SY_UOMS_MST UM_CODE UM_CODE

SY_UOMS_TYP UM_TYPE UM_TYPE


UM_TYPE (PK) NOT NULL VARCHAR2(4) The Unit of Measure Type associated with eachUnit of Measure

UM_CODE NOT NULL VARCHAR2(4) Unit of Measure code for which the conversion isdefined.

CREATED_BY NOT NULL NUMBER(15) Standard Who columnCREATION_DATE NOT NULL DATE Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER(15) Standard Who columnLAST_UPDATE_DATE NOT NULL DATE Standard Who columnLAST_UPDATE_LOGIN NULL NUMBER(15) Standard Who column

Indexes


SY_UOMS_STD_PK UNIQUE 10 UM_TYPE




SY_UOMS_TYPUnit of measure type master for Oracle Process Manufacturing products. Defineunit of measure types here, which categorize Units of Measure. Synchronized withMTL_UOM_CLASSES when Oracle Financials is used.

Foreign Keys




UM_TYPE (PK) NOT NULL VARCHAR2(10) Unit of Measure TypeTYPE_DESC NOT NULL VARCHAR2(40) Unit of Measure Type description.LAST_UPDATE_DATE NOT NULL DATE Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER(15) Standard Who columnCREATION_DATE NOT NULL DATE Standard Who columnCREATED_BY NOT NULL NUMBER(15) Standard Who columnTEXT_CODE NULL NUMBER(10) ID which joins any rows of text in this table to


for (logical) deletion.TRANS_CNT NULL NUMBER(10) Not currently usedLAST_UPDATE_LOGIN NULL NUMBER(15) Standard Who columnSTD_UM NULL VARCHAR2(4) The Standard, or reference, UOM for this UOM Type

Indexes


SY_UOMS_TYP_PK UNIQUE 10 UM_TYPE




TX_TLOC_CDSThis table holds the definition of Tax Locations. A Tax Location is assigned to acustomer and warehouse to determine which tax authorities pertain to theship-from warehouse/customer combination. The pairing of Tax Locations is donein the table TX_TOFR_ASC.

Foreign Keys


TX_TEXT_HDR TEXT_CODE TEXT_CODE


TAXLOC_CODE (PK) NOT NULL VARCHAR2(10) Tax location code. Indicates tax jurisdic-tion/geographic location.

TAXLOC_DESC NOT NULL VARCHAR2(70) User entered description for the tax locationCREATION_DATE NOT NULL DATE Standard Who columnLAST_UPDATE_DATE NOT NULL DATE Standard Who columnCREATED_BY NOT NULL NUMBER(15) Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER(15) Standard Who columnTRANS_CNT NULL NUMBER(10) Not currently usedDELETE_MARK NOT NULL NUMBER(5) Standard: 0=Active record (default); 1=Marked


the Text Table for this ModuleLAST_UPDATE_LOGIN NULL NUMBER(15) Standard Who column

Indexes


TX_TLOC_CDS_PK UNIQUE 1 TAXLOC_CODE






Index
AApplication Building Block, 1-6
CColumn descriptions, 3-3Columns

Who, 3-4Concurrent Program List, 2-18Concurrent Program List See Concurrent Program

Definitions, 2-4

DDatabase Diagram, 1-6

Summary Database Diagram, 1-6database diagrams

conventions, 2-6summary, 2-5

Database triggers, 3-6

FForeign keys, 3-3Form, 1-6Form List, 2-18Form List See Form Definitions, 2-4

IIndexes, 3-5

important note about, 3-5

LLookup types See QuickCodes, 3-3

MModule List, 2-17Module List See Module Definitions, 2-4Modules, 1-6

OOracle8 sequences See Sequences, 3-6

PPublic Table List, 2-15Public View List, 2-17

QQuickCodes, 1-6

Columns that contain, 3-3

RRelationship, 1-5Report List See Report Definitions, 2-4

SSequences, 3-6summary database diagram See database

diagrams, 2-5

Index-1

TTable and View Definitions

GEM_LOOKUP_TYPES, 3-7GEM_LOOKUP_VALUES, 3-8GMA_ACTCOL_WF_B, 3-9GMA_ACTCOL_WF_TL, 3-10GMA_ACTDATA_WF, 3-11GMA_ACTDEF_WF, 3-12IC_WHSE_MST, 3-13PS_PLNG_CLS, 3-15SY_ADDR_MST, 3-17SY_CMPY_MST, 3-18SY_DOCS_MST, 3-19SY_DOCS_SEQ, 3-20SY_GEOG_MST, 3-21SY_ORGN_MST, 3-22SY_ORGN_USR, 3-23SY_PARA_CDS_TL, 3-24SY_PURG_DEF, 3-25SY_PURG_DEF_ACT, 3-26SY_PURG_DEF_CRIT, 3-27SY_PURG_ERR, 3-28SY_PURG_LOG, 3-29SY_PURG_MST, 3-30SY_PURG_MST_CRIT, 3-32SY_REAS_CDS, 3-33SY_TEXT_HDR, 3-34SY_TEXT_TBL_TL, 3-35SY_TEXT_TKN_TL, 3-36SY_TRIGGER_ACTIVATION_WF, 3-37SY_UOMS_MST, 3-38SY_UOMS_STD, 3-39SY_UOMS_TYP, 3-40TX_TLOC_CDS, 3-41

TablesColumn descriptions, 3-3Foreign keys, 3-3Indexes See Indexes, 3-5Primary Keys, 3-3QuickCodes Columns, 3-3Who columns, 3-4, 3-5

Tables See Table and View Definitions, 3-2

VView Definitions See Table and View

Definitions, 3-6Views

Derivation, 3-6Views See Table and View Definitions, 3-6Views See View List, 3-6

Index-2

CAUTION!This document contains proprietary,

If you are an Oracle customer, thisnumbered copy is registered in your site’s

name. Use, duplication, and disclosure areseverely restricted and subject to

restrictions stated in your contract withOracle Corporation.

If you are an Oracle employee, thisnumbered copy is registered in your name

and must be returned if you leave thecompany. It is your responsibility not to

disclose this information to anyone outsideof Oracle who is not licensed to use this

product. If you have a prospect whoneeds to see this information, contactmailid APPSAPP to obtain a special

nondisclosure agreement.

If you are neither an Oracle customer with avalid contract for the use of this document

nor an Oracle employee, then you receivedthis document in an unauthorized manner

and are not legally entitled to possessor read it. Please return it immediatelyto Oracle. You may call collect to theoffice of the Executive Vice President

Applications Division, to arrange its return.

confidential information that is the exclusiveproperty of Oracle Corporation.

Copy #

��

��

A8

08

45

–0

1

Date post:	24-Oct-2014
Category:	Documents
Upload:	jayanta
View:	60 times
Download:	5 times