Oracle Apps System Admin Student Guide2

Volume 2 - Student Guide
D49195GC10
Edition 1.0
July 2007
D51750
THESE eKIT MATERIALS ARE FOR YOUR USE IN THIS CLASSROOM ONLY. COPYING eKIT MATERIALS FROM THIS
COMPUTER IS STRICTLY PROHIBITED
Oracle University and Egabi Solutions use only
R12 Oracle Applications System

Administrator Fundamentals
Copyright 1996, 2007, Oracle. All rights reserved.

This document contains proprietary information and is protected by copyright and other intellectual property laws. You may copy and
print this document solely for your own use in an Oracle training course. The document may not be modified or altered in any way.
Except where your use constitutes "fair use" under copyright law, you may not use, share, download, upload, copy, print, display,
perform, reproduce, publish, license, post, transmit, or distribute this document in whole or in part without the express authorization
of Oracle.
The information contained in this document is subject to change without notice. If you find any problems in the document, please
report them in writing to: Oracle University, 500 Oracle Parkway, Redwood Shores, California 94065 USA. This document is not
warranted to be error-free.
If this documentation is delivered to the United States Government or anyone using the documentation on behalf of the United
States Government, the following notice is applicable:
Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation and/or its affiliates. Other names may
be trademarks of their respective owners.
Author
Mildred Wang, Robert Farrington, Clara Jaeckel, Melody Yang
Technical Contributors and Reviewers
Donna Johnson, Leta Davis, Barbara Waddoups, Gary Lemmons, Roman Kratochvil, Roger
Wigenstam, Venkata Vengala, Biju Mohan, Gursat Olgun, Maxine Zasowski, Sunil Ghosh
This book was published using:
oracletutor
U.S. GOVERNMENT RIGHTS

The U.S. Governments rights to use, modify, reproduce, release, perform, display, or disclose these training materials are restricted
by the terms of the applicable Oracle license agreement and/or the applicable U.S. Government contract.
Table of Contents
Introduction to Oracle Applications Security ...............................................................................................2-1

Introduction to Oracle Applications Security ................................................................................................2-3
Objectives ......................................................................................................................................................2-4
Successive Layers of Access Control ............................................................................................................2-5
Increasing Flexibility and Scalability ............................................................................................................2-6
Function Security...........................................................................................................................................2-8
Data Security .................................................................................................................................................2-9
Oracle User Management Layers of Access Control.....................................................................................2-11
Role Based Access Control (RBAC) .............................................................................................................2-12
Delegated Administration..............................................................................................................................2-14
Registration Processes ...................................................................................................................................2-16
Self Service and Approvals ...........................................................................................................................2-18
Summary........................................................................................................................................................2-19
Function Security.............................................................................................................................................3-1
Objectives ......................................................................................................................................................3-4
Overview of Function Security......................................................................................................................3-5
Defining a New Application User .................................................................................................................3-7
Custom Applications .....................................................................................................................................3-8
Defining an Application ................................................................................................................................3-9
Registering an Oracle ID ...............................................................................................................................3-10
Data Groups...................................................................................................................................................3-11
Securing Functions ........................................................................................................................................3-13
Defining a Menu............................................................................................................................................3-14
Identifying Existing Menu Structures...........................................................................................................3-16
Menu Guidelines ...........................................................................................................................................3-17
Creating a Menu ............................................................................................................................................3-18
Modifying an Existing Menu Definition ......................................................................................................3-20
Navigator Menus ...........................................................................................................................................3-21
The Menu Viewer..........................................................................................................................................3-22
Viewing Node Properties in the Menu Viewer..............................................................................................3-23
Adding a Custom Form Function ..................................................................................................................3-24
Using Responsibilities ...................................................................................................................................3-25
Responsibility Components ...........................................................................................................................3-27
Defining a New Responsibility......................................................................................................................3-28
Responsibility Creation Process ....................................................................................................................3-29
Defining a New Responsibility......................................................................................................................3-30
Excluding Functions and Menus ...................................................................................................................3-31
Summary........................................................................................................................................................3-32
Introduction to Data Security.........................................................................................................................4-1
Objectives ......................................................................................................................................................4-4
Copyright Oracle Corporation, 2006. All rights reserved.
R12 System Administrator Fundamentals Table of Contents

i
THESE eKIT MATERIALS ARE FOR YOUR USE IN THIS CLASSROOM
ONLY. COPYING eKIT MATERIALS FROM THIS
Introduction .....................................................................................................................................................1-1
Introduction ...................................................................................................................................................1-3
Course Objectives..........................................................................................................................................1-4
Overview .......................................................................................................................................................1-5
Oracle Applications System Administration .................................................................................................1-6
Oracle Workflow Component........................................................................................................................1-7
Oracle Applications Flexfields Component...................................................................................................1-8
Additional Material........................................................................................................................................1-9
Introduction to Oracle User Management ....................................................................................................5-1

Introduction to Oracle User Management .....................................................................................................5-3
Objectives ......................................................................................................................................................5-4
What Is Oracle User Management? ...............................................................................................................5-5
Access Control Model ...................................................................................................................................5-6
Successive Layers of Access Control ............................................................................................................5-7
Increased Flexibility and Scalability..............................................................................................................5-8
Responsibilities..............................................................................................................................................5-10
Data Security .................................................................................................................................................5-11
Role Based Access Control (RBAC) .............................................................................................................5-12
Delegating to Proxy Users .............................................................................................................................5-15
Provisioning Services ....................................................................................................................................5-16
Self-Service and Approvals ...........................................................................................................................5-18
Login Assistance ...........................................................................................................................................5-19
Summary........................................................................................................................................................5-20
Implementing Oracle User Management.......................................................................................................6-1
Objectives ......................................................................................................................................................6-4
Steps for Implementing Oracle User Management........................................................................................6-6
Configuring and Testing Oracle User Management ......................................................................................6-9
Introduction to Roles .....................................................................................................................................6-10
Examples of Roles .........................................................................................................................................6-11
Defining Roles: Data Security Policies .........................................................................................................6-12
Defining Roles: Assigning a Single Responsibility and All Its Functions to a Role .....................................6-13
Assigning a Single Responsibility to a Role and Granting Specific Functions to a Role ..............................6-14
Defining Roles: Assigning Multiple Responsibilities to a Role ....................................................................6-15
Role Inheritance Hierarchies .........................................................................................................................6-16
Role Categories .............................................................................................................................................6-17
Assigning Permissions to Roles.....................................................................................................................6-18
Advantages of Roles Over Responsibilities...................................................................................................6-20
Phase II: Define Roles ...................................................................................................................................6-22
Steps for Creating Roles: Define a Role Category ........................................................................................6-23
Steps for Creating Roles: Create a Role within the Role Category ...............................................................6-24
Steps for Creating Roles: Place Role in Role Inheritance Hierarchy.............................................................6-25
Steps for Creating Roles: Assign Permissions to Roles.................................................................................6-26
Steps for Creating Roles: Assign Role to a New Person ...............................................................................6-27
Steps for Creating Roles: Test Role as Customer Administrator...................................................................6-28
What Is Delegated Administration?...............................................................................................................6-30
User Administration Privileges......................................................................................................................6-31
User Administration Privileges (cont.) ..........................................................................................................6-32
Role Administration Privileges......................................................................................................................6-33
Seeded Permissions for User Administration ................................................................................................6-34
Managing Roles with Role Administration ...................................................................................................6-35
Seeded Permissions for Role Administration ................................................................................................6-36
Organization Administration Privileges ........................................................................................................6-37
Seeded Permissions for Organization Administration ...................................................................................6-38

ii
Data Security Components - Objects.............................................................................................................4-7

Grants ............................................................................................................................................................4-8
Permissions and Permission Sets...................................................................................................................4-9
Data Security Policies....................................................................................................................................4-10
Example of a Data Security Policy ................................................................................................................4-11
Summary........................................................................................................................................................4-12
Profile Options .................................................................................................................................................7-1

Managing Profile Options..............................................................................................................................7-3
Objectives ......................................................................................................................................................7-4
Personal Profile Values .................................................................................................................................7-5
System Profile Options - Profile Hierarchy Types ........................................................................................7-6
Profile Hierarchy Levels - Security ...............................................................................................................7-7
Profile Hierarchy Levels Organization .......................................................................................................7-8
Profile Hierarchy Levels - Server ..................................................................................................................7-9
System Profile Options..................................................................................................................................7-10
Using User Profile Values as Defaults .........................................................................................................7-11
Profile Categories ..........................................................................................................................................7-12
Auditing Related Profile Options ..................................................................................................................7-13
Currency-Related Options .............................................................................................................................7-15
Flexfield-Related Options..............................................................................................................................7-16
Online Reporting-Related Options ................................................................................................................7-18
Personal Output Viewer Options ...................................................................................................................7-19
User-Related Concurrent Request Profile Options ........................................................................................7-20
Security Signon Profile Options ....................................................................................................................7-22
Summary........................................................................................................................................................7-24
Auditing System Resources.............................................................................................................................8-1
Auditing System Resources...........................................................................................................................8-3
Objectives ......................................................................................................................................................8-4
Auditing Oracle Applications ........................................................................................................................8-5
Auditing User Activity ..................................................................................................................................8-6
Signon Audit Profile Option..........................................................................................................................8-7
Signon Audit Reports ....................................................................................................................................8-8
Signon Audit Forms Report...........................................................................................................................8-9
Signon Audit Concurrent Requests Report....................................................................................................8-10
Signon Audit Responsibilities Report............................................................................................................8-11
Signon Audit Unsuccessful Logins Report....................................................................................................8-12
Signon Audit Users Report............................................................................................................................8-13
Purge Audit Records......................................................................................................................................8-14
Monitor Users Window .................................................................................................................................8-15
Auditing Database Changes...........................................................................................................................8-16
Steps for Setting Up AuditTrail.....................................................................................................................8-17

iii
Delegated Administration vs. Traditional System Administration ................................................................6-39

Phase III: Setting Up Delegated Administration ...........................................................................................6-40
Steps for Implementing Delegated Administration: Set Up User Administration for a Role ........................6-41
Steps for Implementing Delegated Administration .......................................................................................6-42
Registration Processes ...................................................................................................................................6-45
Registration Processes: Core Components ....................................................................................................6-47
Self-Service Account Requests......................................................................................................................6-48
Requests for Additional Access.....................................................................................................................6-49
Account Creation by Administrators .............................................................................................................6-50
Phase IV: Creating Registration Processes ....................................................................................................6-51
Steps for Creating Registration Processes: Provide Required Description Information................................6-52
Steps for Creating Registration Processes: Enter Runtime Execution Information.......................................6-54
Steps for Creating Registration Processes: Enter Eligibility Information......................................................6-55
Steps for Creating Registration Processes: Register Subscriptions to Business Events ................................6-56
Steps for Creating Registration Processes: Optionally Set Profile Options...................................................6-57
Steps for Creating Registration Processes: Optionally Set Login Page UI Attributes...................................6-59
Steps for Creating Registration Processes: Test as Customer Administrator ................................................6-61
Managing Proxy Users ..................................................................................................................................6-62
Self-Service Features.....................................................................................................................................6-64
Login Assistance ...........................................................................................................................................6-66
Summary........................................................................................................................................................6-67
Managing Printers...........................................................................................................................................9-1
Managing Printers..........................................................................................................................................9-3
Objectives ......................................................................................................................................................9-4
Oracle Print Definition Components .............................................................................................................9-5
Relationships of the Printer Components ......................................................................................................9-7
Formatting Information .................................................................................................................................9-8
Defining Printers............................................................................................................................................9-10
Finding Existing Printer Types......................................................................................................................9-11
Registering a New Printer..............................................................................................................................9-12
Defining a New Printer Type.........................................................................................................................9-13
Printing with Pasta.........................................................................................................................................9-14
Setup for Basic Printing with Pasta ...............................................................................................................9-15
The pasta.cfg file ...........................................................................................................................................9-16
Modifying an Existing Printer Type to Use Pasta .........................................................................................9-17
Generating Other Formats using the Preprocessing Option...........................................................................9-19
Using Pasta with XML Publisher ..................................................................................................................9-20
Other Customization Materials for Oracle Applications Printing..................................................................9-22
Summary........................................................................................................................................................9-23
Introduction to Oracle Applications Manager..............................................................................................10-1
Introduction to Oracle Applications Manager (OAM) ..................................................................................10-3
Objectives ......................................................................................................................................................10-4
What is Oracle Applications Manager? .........................................................................................................10-5
Benefits of Oracle Applications Manager......................................................................................................10-6
Oracle Applications Manager Integrates with ..........................................................................................10-7
Application Management Pack for Oracle E-Business Suite.........................................................................10-9
Navigation in OAM .......................................................................................................................................10-10
Applications Dashboard ................................................................................................................................10-11
Site Map.........................................................................................................................................................10-13
Administration...............................................................................................................................................10-14
Monitoring.....................................................................................................................................................10-15
Maintenance ..................................................................................................................................................10-16
Diagnostics and Troubleshooting ..................................................................................................................10-17
Setting Up Oracle Applications Manager......................................................................................................10-18
Summary........................................................................................................................................................10-19
System Monitoring in Oracle Applications Manager...................................................................................11-1
System Monitoring in Oracle Applications Manager ....................................................................................11-3
Objectives ......................................................................................................................................................11-4
System Status Overview................................................................................................................................11-5
System Status Configuration Changes........................................................................................................11-7
System Status Web Components Status .....................................................................................................11-8
System Status System Alerts ......................................................................................................................11-10
System Status User Initiated Alerts ............................................................................................................11-12
Performance...................................................................................................................................................11-13
Critical Activities...........................................................................................................................................11-15
Critical Activities Setup.................................................................................................................................11-16
System Alerts, Metrics, Logs.........................................................................................................................11-17
Database Initialization (init.ora) Parameters..................................................................................................11-19

iv
Identify Tables and Columns to Audit...........................................................................................................8-18

Create an Audit Group...................................................................................................................................8-19
Audit Tables Window....................................................................................................................................8-20
Identifying the Schema to be Audited ...........................................................................................................8-21
Enabling Audit Processing ............................................................................................................................8-22
Audit Shadow Tables.....................................................................................................................................8-23
Shadow Table Views .....................................................................................................................................8-24
Summary........................................................................................................................................................8-25
Diagnostics and Troubleshooting with Oracle Applications Manager .......................................................12-1

Oracle Applications Manager - Diagnostics and Troubleshooting ................................................................12-3
Objectives ......................................................................................................................................................12-4
Diagnostics and Troubleshooting in Oracle Applications Manager ..............................................................12-5
Applications Dashboard - Diagnostics ..........................................................................................................12-7
Troubleshooting Wizards...............................................................................................................................12-9
Concurrent Manager Recovery Wizard .........................................................................................................12-11
Service Infrastructure Wizard........................................................................................................................12-13
Generic Collection Service (GCS) and Forms Monitoring Wizard ...............................................................12-14
CP Signature..................................................................................................................................................12-15
Dashboard Collection Wizard........................................................................................................................12-17
Support Cart...................................................................................................................................................12-18
Summary........................................................................................................................................................12-20
Managing Concurrent Programs and Reports .............................................................................................13-1
Managing Concurrent Requests.....................................................................................................................13-3
Objectives ......................................................................................................................................................13-4
Concurrent Requests, Programs, and Managers ............................................................................................13-6
Business Needs for Concurrent Processing ...................................................................................................13-7
Business Needs for Standard Request Submission........................................................................................13-8
Definitions .....................................................................................................................................................13-9
Submit Request Flow.....................................................................................................................................13-11
Submit a New Request ..................................................................................................................................13-12
Using the Parameters Window ......................................................................................................................13-13
Defining a Submission Schedule ...................................................................................................................13-14
Defining Completion Options........................................................................................................................13-16
Request ID .....................................................................................................................................................13-17
Reprinting a Report .......................................................................................................................................13-18
Use the Requests Window to View and Change Requests ............................................................................13-19
How to Use the Requests Window ................................................................................................................13-20
Using the Requests Window..........................................................................................................................13-21
Viewer Options Window ...............................................................................................................................13-23
Canceling a Request ......................................................................................................................................13-24
Holding a Request .........................................................................................................................................13-25
Changing Request Options ............................................................................................................................13-26
Four Phases of a Concurrent Request ............................................................................................................13-27

v
Business Flows ..............................................................................................................................................11-20

Monitoring Oracle E-Business Suite Security ...............................................................................................11-22
Monitoring E-Business Suite Security Setup - Diagnostic Tests...................................................................11-24
Applications Dashboard - Security ................................................................................................................11-25
Database Status Details .................................................................................................................................11-26
Application Services......................................................................................................................................11-27
Monitoring Forms..........................................................................................................................................11-28
Forms Runaway Processes ............................................................................................................................11-29
Forms Sessions ..............................................................................................................................................11-31
Forms Runtime Processes..............................................................................................................................11-33
Host Management..........................................................................................................................................11-35
Host Management - Status.............................................................................................................................11-37
Host Management - Configuration ................................................................................................................11-38
Setting Up Oracle Applications Manager......................................................................................................11-39
Dashboard Configuration and Alerting Setup................................................................................................11-40
Setting Up Dashboard Configuration and Alerting .......................................................................................11-41
OracleMetaLink Credentials Setup................................................................................................................11-43
Knowledge Base Setup..................................................................................................................................11-44
Concurrent Requests Setup............................................................................................................................11-45
Signon Audit Setup........................................................................................................................................11-46
Summary........................................................................................................................................................11-47
Administering Concurrent Managers............................................................................................................14-1

Administering Concurrent Managers.............................................................................................................14-3
Objectives ......................................................................................................................................................14-4
Concurrent Requests, Programs, and Processes ............................................................................................14-5
Overview of Concurrent Processing ..............................................................................................................14-6
Generic Service Management (GSM)............................................................................................................14-7
Defining a Concurrent Manager ....................................................................................................................14-8
Defining Work Shifts.....................................................................................................................................14-10
Balancing Process Workload Over Time.......................................................................................................14-11
Work Shift Hierarchy ....................................................................................................................................14-12
Concurrent Managers Window: Program Libraries.......................................................................................14-13
Assigning Workshifts to a Manager ..............................................................................................................14-14
Specializing a Concurrent Manager...............................................................................................................14-15
Specializing a Concurrent Manager: Combined Rules ..................................................................................14-16
Specialization Rules ......................................................................................................................................14-17
Action Types .................................................................................................................................................14-18
Combining Multiple Actions Within Rules ...................................................................................................14-19
Concurrent Request Types.............................................................................................................................14-20
Using Request Types .....................................................................................................................................14-21
Conflicts Domains .........................................................................................................................................14-22
Processing Conflicts Domains.......................................................................................................................14-24
Control Functions of Concurrent Managers ..................................................................................................14-25
Internal Monitor and ICM .............................................................................................................................14-27
Defining a Transaction Manager ...................................................................................................................14-28
Viewing Log and Output Files ......................................................................................................................14-29
Managing Parallel Concurrent Processing.....................................................................................................14-30

vi
Pending Phase................................................................................................................................................13-28
Running Phase ...............................................................................................................................................13-29
Completed Phase ...........................................................................................................................................13-30
Inactive Phase................................................................................................................................................13-31
System Administrator Monitoring Privileges ................................................................................................13-32
Review Log Files...........................................................................................................................................13-33
Managing Log Files and Tables ....................................................................................................................13-34
Purge Request Results ...................................................................................................................................13-35
Grouping Concurrent Programs and Requests...............................................................................................13-36
Creating a Request Group..............................................................................................................................13-38
Using a Request Group with a Code..............................................................................................................13-39
Submitting Requests: Form Compared with Responsibility..........................................................................13-40
Implementing a Coded Request Group..........................................................................................................13-41
Customization Example.................................................................................................................................13-42
Creating the New Form Function ..................................................................................................................13-43
Passable Request Parameters.........................................................................................................................13-44
Adding the Function to the Menu..................................................................................................................13-45
Defining a Request Set ..................................................................................................................................13-46
Request Set Stages.........................................................................................................................................13-47
Stage Status ...................................................................................................................................................13-48
Linking of Stages...........................................................................................................................................13-50
Defining Request Sets Step 1: Enter Request Set Name ...............................................................................13-51
Defining Request Sets Step 2: Define a Stage ...............................................................................................13-53
Defining Request Sets Step 3: Enter Requests for Stage ...............................................................................13-54
Defining Request Sets Step 4: Enter Request Parameter...............................................................................13-55
Defining Request Sets Step 5: Link Stages ...................................................................................................13-56
Submitting a Request Set...............................................................................................................................13-57
User Request Set Privileges...........................................................................................................................13-58
System Administrator Request Set Privileges ...............................................................................................13-59
Summary........................................................................................................................................................13-60
Introduction to Oracle Workflow ..................................................................................................................15-1

Introduction to Oracle Workflow ..................................................................................................................15-3
Objectives ......................................................................................................................................................15-4
Enabling E-Business......................................................................................................................................15-5
Inter-Enterprise Business Processes ..............................................................................................................15-6
Traditional Workflow ....................................................................................................................................15-7
Workflow-Driven Business Processes...........................................................................................................15-8
Sample Workflow Process.............................................................................................................................15-10
Event-Based Workflow .................................................................................................................................15-11
Subscription-Based Processing......................................................................................................................15-12
System Integration with Oracle Workflow ....................................................................................................15-13
Business Process-Based Integration ..............................................................................................................15-14
Supported System Integration Types.............................................................................................................15-15
Designing Applications for Change...............................................................................................................15-16
Designing Applications for Integration .........................................................................................................15-19
Oracle Workflow in Oracle E-Business Suite ...............................................................................................15-21
Summary........................................................................................................................................................15-22
Oracle Workflow Components.......................................................................................................................16-1
Oracle Workflow Components ......................................................................................................................16-3
Objectives ......................................................................................................................................................16-4
Oracle Workflow Architecture ......................................................................................................................16-5
Oracle Workflow Components ......................................................................................................................16-9
Workflow Engine ..........................................................................................................................................16-10
Workflow Processes ......................................................................................................................................16-11
Supported Process Constructs........................................................................................................................16-13
Oracle Workflow Builder ..............................................................................................................................16-17
Business Event System Architecture .............................................................................................................16-18
Business Event System Components.............................................................................................................16-19
Advanced Queuing, an Enabling Technology ...............................................................................................16-20
Oracle Database Communication Alternatives..............................................................................................16-21
Accessing Oracle Workflow Web Pages .......................................................................................................16-23
Oracle Workflow Home Pages ......................................................................................................................16-24
Notification System .......................................................................................................................................16-25
Worklist Web Pages ......................................................................................................................................16-26
E-Mail Notifications ......................................................................................................................................16-27
Directory Services .........................................................................................................................................16-28
Status Monitor Web Pages.............................................................................................................................16-29
Workflow Definitions Loader........................................................................................................................16-30
Workflow XML Loader.................................................................................................................................16-31
Workflow Manager........................................................................................................................................16-32
Service Components ......................................................................................................................................16-33
Oracle Workflow Documentation..................................................................................................................16-34
Review Questions ..........................................................................................................................................16-36
Summary........................................................................................................................................................16-37
Setting Up Oracle Workflow ..........................................................................................................................17-1
Setting Up Oracle Workflow .........................................................................................................................17-3
Objectives ......................................................................................................................................................17-4
Required Setup Steps.....................................................................................................................................17-5
Step 1 Setting Global Workflow Preferences ................................................................................................17-6
Step 2 Setting Up an Oracle Workflow Directory Service ............................................................................17-9
Step 3 Running Background Engines ............................................................................................................17-13
Step 4 Configuring the Business Event System.............................................................................................17-16
Step 4 Event Message Communication .........................................................................................................17-17
Step 4 Setting Up Database Links and Queues..............................................................................................17-18

vii
Summary........................................................................................................................................................14-32
Overview of Flexfields .....................................................................................................................................18-1

Overview of Flexfields ..................................................................................................................................18-3
Objectives ......................................................................................................................................................18-4
Overview .......................................................................................................................................................18-5
Customizing Oracle Applications..................................................................................................................18-6
Flexfield Structures and Flexfield Segments .................................................................................................18-7
Segment Prompts and Value Descriptions.....................................................................................................18-8
Validating Input Using Value Sets ................................................................................................................18-9
Key and Descriptive Flexfields .....................................................................................................................18-10
Key Flexfields ...............................................................................................................................................18-11
Intelligent Keys .............................................................................................................................................18-12
Key Flexfield Example: Accounting Flexfield ..............................................................................................18-14
Oracle Applications Key Flexfields...............................................................................................................18-15
Descriptive Flexfields....................................................................................................................................18-16
Using Reference Fields..................................................................................................................................18-17
Using Different Contexts: Asset Category Flexfield .....................................................................................18-18
Oracle Applications Descriptive Flexfields (Partial) .....................................................................................18-19
Standard Request Submission (SRS) and Flexfields .....................................................................................18-20
Benefits of Flexfields.....................................................................................................................................18-21
Storing Flexfield Data Internally ...................................................................................................................18-22
Implementing a Flexfield Steps ....................................................................................................................18-23
Summary........................................................................................................................................................18-24
Using Value Sets...............................................................................................................................................19-1
Using Value Sets ...........................................................................................................................................19-3
Objectives ......................................................................................................................................................19-4
Overview .......................................................................................................................................................19-5
Validating Input Using Value Sets ................................................................................................................19-6
Planning a Value Set......................................................................................................................................19-7
Types of Value Sets.......................................................................................................................................19-8
Validation Type None ...................................................................................................................................19-10
Independent Value Sets .................................................................................................................................19-11
Dependent Value Sets....................................................................................................................................19-12
Table-Validated Value Sets ...........................................................................................................................19-13
Specialized Validation Types ........................................................................................................................19-14
Translatable Independent Value Sets.............................................................................................................19-15

viii
Step 4 Checking Database Parameters...........................................................................................................17-19

Step 4 Scheduling Agent Listeners................................................................................................................17-20
Step 4 Scheduling Propagation......................................................................................................................17-23
Step 4 Synchronizing License Statuses .........................................................................................................17-27
Step 4 Cleaning Up the WF_CONTROL Queue...........................................................................................17-28
Step 4 Tuning Performance ...........................................................................................................................17-29
Step 4 Specifying the BPEL Server...............................................................................................................17-31
Optional Setup Steps .....................................................................................................................................17-32
Optional Step 1 Partitioning Workflow Tables .............................................................................................17-34
Optional Step 2 Setting Up Additional Languages........................................................................................17-36
Optional Step 3 Implementing Notification Mailers .....................................................................................17-38
Optional Step 4 Customizing Message Templates ........................................................................................17-41
Optional Step 5 Adding Worklist Functions to User Responsibilities...........................................................17-44
Optional Step 6 Setting the Notification Reassign Mode ..............................................................................17-46
Optional Step 7 Setting Up Notification Handling Options ..........................................................................17-47
Optional Step 8 Setting Up for Electronic Signatures ...................................................................................17-49
Optional Step 9 Customizing the Workflow Web Page Logo .......................................................................17-51
Optional Step 10 Adding Custom Icons ........................................................................................................17-52
Version Compatibility ...................................................................................................................................17-53
Review Questions ..........................................................................................................................................17-54
Summary........................................................................................................................................................17-56
Defining Descriptive Flexfields .......................................................................................................................20-1

Defining Descriptive Flexfields.....................................................................................................................20-3
Objectives ......................................................................................................................................................20-4
Overview .......................................................................................................................................................20-5
Planning a Descriptive Flexfield ...................................................................................................................20-6
Using Descriptive Flexfields .........................................................................................................................20-8
Typical Descriptive Flexfield Information ....................................................................................................20-9
Some Oracle Applications Descriptive Flexfields.........................................................................................20-10
Identifying a Descriptive Flexfield ................................................................................................................20-11
Determining the Descriptive Flexfield Name ................................................................................................20-12
Determining Available Resources .................................................................................................................20-14
Planning Questions ........................................................................................................................................20-15
Identifying Your Information ........................................................................................................................20-16
Grouping Information By Usage ...................................................................................................................20-17
Isolate Common Information.........................................................................................................................20-18
Determine Different Contexts........................................................................................................................20-19
Descriptive Flexfield Components ................................................................................................................20-20
Global Segments............................................................................................................................................20-21
Context-Sensitive Segments ..........................................................................................................................20-22
Distinguishing Between Contexts..................................................................................................................20-23
Reference and Context Fields........................................................................................................................20-24
Using Reference Fields..................................................................................................................................20-25
Identifying Referenceable Columns ..............................................................................................................20-26
Using Context Fields .....................................................................................................................................20-27
Synchronizing the Context Field Value with the Reference Field Value ......................................................20-28
Planning Flexfields: Global Segments Only..................................................................................................20-30
Planning Flexfields: Context Segments Only ...............................................................................................20-31
Planning Flexfields: Global and Context Fields ............................................................................................20-32
Specifying the Flexfield Attributes................................................................................................................20-33

ix
Translatable Dependent Value Sets ...............................................................................................................19-16

Validation Types: Summary ..........................................................................................................................19-17
Planning Value Sets.......................................................................................................................................19-18
Value Set Attributes.......................................................................................................................................19-19
Planning Format Validation...........................................................................................................................19-20
Format Types and Options.............................................................................................................................19-21
Char and Number Format Editing .................................................................................................................19-22
Time, Standard Date, and Standard DateTime Format Editing .....................................................................19-23
Format Interaction .........................................................................................................................................19-24
Formatting Requirements for Translatable Value Sets .................................................................................19-25
Planning Validation Strategy.........................................................................................................................19-26
Planning Value Sets and Their Values ..........................................................................................................19-28
Planning Dependent Value Sets.....................................................................................................................19-29
Defining Value Sets.......................................................................................................................................19-30
Predefined Value Sets....................................................................................................................................19-31
Using Existing Value Sets .............................................................................................................................19-32
Value Set Usage by Key Flexfields ...............................................................................................................19-33
Value Set Usage by Descriptive Flexfields ...................................................................................................19-35
Defining a New Value Set .............................................................................................................................19-36
Defining a Dependent or Translatable Dependent Value Set ........................................................................19-37
Selecting a Value Set for Value Definition ...................................................................................................19-38
Defining Values for a Dependent or Translatable Dependent Value Set.......................................................19-39
Defining Values for a Value Set....................................................................................................................19-40
Modifying Value Definitions.........................................................................................................................19-41
Value Hierarchies ..........................................................................................................................................19-42
Defining Value Hierarchies and Qualifiers....................................................................................................19-44
Summary........................................................................................................................................................19-45
Defining Key Flexfields ...................................................................................................................................21-1

Defining Key Flexfields ................................................................................................................................21-3
Objectives ......................................................................................................................................................21-4
Overview .......................................................................................................................................................21-6
Intelligent Keys .............................................................................................................................................21-8
Key Flexfields' Dual Purpose ........................................................................................................................21-9
Oracle Applications Key Flexfields...............................................................................................................21-10
Implementing Key Flexfields ........................................................................................................................21-11
Key Flexfield Structures................................................................................................................................21-12
Code Combinations .......................................................................................................................................21-13
Storing Code Combinations...........................................................................................................................21-14
Key Flexfield Application Tables..................................................................................................................21-15
Key Flexfield Qualifiers ................................................................................................................................21-16
Types of Qualifiers ........................................................................................................................................21-17
Flexfield Qualifiers........................................................................................................................................21-18
Segment Qualifiers ........................................................................................................................................21-20
Other Key Flexfield Options .........................................................................................................................21-21
Allowing Dynamic Insertion .........................................................................................................................21-22
Cross-Validating Values................................................................................................................................21-23
Using Shorthand Aliases ...............................................................................................................................21-24
Securing Value Set Access ............................................................................................................................21-25
Designing the Key Flexfield Layout..............................................................................................................21-26
Designing Segments ......................................................................................................................................21-27
Specifying Default Values.............................................................................................................................21-28
Planning Decisions ........................................................................................................................................21-30
Planning Key Flexfield Values......................................................................................................................21-32
Definition Procedure......................................................................................................................................21-33
Accessing the Key Flexfield Definition.........................................................................................................21-35
Specifying Flexfield Behavior.......................................................................................................................21-36
Defining Segment Attributes .........................................................................................................................21-37
Defining Validation and Size Attributes........................................................................................................21-38
Defining Flexfield Qualifiers.........................................................................................................................21-39
Freezing and Compiling the Definition .........................................................................................................21-40
Defining Value Set Values ............................................................................................................................21-41
Defining Segment Qualifiers .........................................................................................................................21-42
Cross-Validating Values................................................................................................................................21-43
Cross-Validation Rule Syntax .......................................................................................................................21-44
Data Type Specifications and Cross-Validation Rules ..................................................................................21-45

x
Specifying the Context Field Information .....................................................................................................20-34

Specifying the Segment Attributes ................................................................................................................20-36
Storing Descriptive Flexfield Segments ........................................................................................................20-37
Descriptive Flexfield Application Tables ......................................................................................................20-38
Specifying the Segment Detail Attributes .....................................................................................................20-40
Specifying Default Values.............................................................................................................................20-43
Defining a Descriptive Flexfield ...................................................................................................................20-45
Locating the Flexfield Definition ..................................................................................................................20-47
Defining the Flexfield Header Attributes ......................................................................................................20-48
Defining Segment Attributes .........................................................................................................................20-49
Specifying Validation and Field Sizes...........................................................................................................20-50
Freezing and Compiling the Definition .........................................................................................................20-51
Defining Context Field Information ..............................................................................................................20-52
Defining Context-Sensitive Segments ...........................................................................................................20-54
Defining Values for a Value Set....................................................................................................................20-55
Summary........................................................................................................................................................20-56
Using Advanced Validation Capabilities .......................................................................................................22-1

Using Advanced Validation Capabilities.......................................................................................................22-3
Objectives ......................................................................................................................................................22-4
Overview .......................................................................................................................................................22-5
Advanced Validation Options........................................................................................................................22-6
Table-Validated Value Sets ...........................................................................................................................22-7
Defining a Table-Validated Value Set...........................................................................................................22-8
Restricting Values Retrieved from a Table....................................................................................................22-9
Limitations on Using SQL WHERE Clauses ................................................................................................22-10
Using Multiple Tables for Validation............................................................................................................22-11
Other Advanced Validation Options..............................................................................................................22-12
Using $PROFILES$ ......................................................................................................................................22-13
Using :block.field ..........................................................................................................................................22-14
Using $FLEX$...............................................................................................................................................22-15
Cascading Dependencies Using $FLEX$......................................................................................................22-16
Using Special Value Sets...............................................................................................................................22-17
Using Pair Value Sets ....................................................................................................................................22-18
Summary........................................................................................................................................................22-19
Appendix - Administering Folders.................................................................................................................23-1
Appendix - Administering Folders ................................................................................................................23-3
Objectives ......................................................................................................................................................23-4
Folders: Definition.........................................................................................................................................23-5
Administering Folders: Topics ......................................................................................................................23-6
Assigning a Default Folder to a Responsibility .............................................................................................23-7
Assigning a Default Folder to a User.............................................................................................................23-8
Assigning Ownership of a Folder ..................................................................................................................23-9
Deleting a Folder Definition..........................................................................................................................23-10
Summary........................................................................................................................................................23-11

xi
Preparing for Cross-Validation......................................................................................................................21-46

Defining Cross-Validation Rules...................................................................................................................21-47
Cross-Validation Reports ..............................................................................................................................21-48
Comparing Cross-Validation and Security Rules ..........................................................................................21-49
Using Shorthand Aliases ...............................................................................................................................21-50
Using Full and Partial Aliases .......................................................................................................................21-51
Typical Key Flexfields Using Aliases ...........................................................................................................21-52
Defining an Alias...........................................................................................................................................21-53
Defining an Alias Template...........................................................................................................................21-54
Recompiling the Flexfield Definition ............................................................................................................21-55
Flexfields: Shorthand Entry Profile Option ...................................................................................................21-56
Flexfields: Show Full Value Profile Option ..................................................................................................21-57
Modifying Existing Alias Definitions............................................................................................................21-58
Securing Value Set Access ............................................................................................................................21-59
Security and Value Sets.................................................................................................................................21-60
Constructing Security Rules ..........................................................................................................................21-61
Specifying Acceptable Values.......................................................................................................................21-62
Using Multiple Clauses .................................................................................................................................21-63
Rules with Overlapping Values .....................................................................................................................21-64
Rules Without Overlapping Values ...............................................................................................................21-65
Implementing Flexfield Security ...................................................................................................................21-66
Enabling Security for a Value Set .................................................................................................................21-67
Enabling Security for a Segment ...................................................................................................................21-68
Enabling Security for a Program Parameter ..................................................................................................21-70
Defining Security Rules.................................................................................................................................21-71
Assigning Security Rules...............................................................................................................................21-72
Defining Key Flexfields Summary ...............................................................................................................21-74
Appendix - Incorporating Custom Help Files ...............................................................................................25-1

Appendix - Incorporating Custom Help Files................................................................................................25-3
Objectives ......................................................................................................................................................25-4
Customizing Help ..........................................................................................................................................25-5
Oracle Applications Help System Utility ......................................................................................................25-6
Help System Utility Setup: Define Directory Paths.......................................................................................25-7
Downloading Help Files ................................................................................................................................25-8
Identify Help Files for Customization ...........................................................................................................25-9
Identify the Language and Product of the Files ............................................................................................25-10
Downloading Help Files for Editing..............................................................................................................25-11
Linking Help Files .........................................................................................................................................25-12
Special Syntax versus Conventional HTML..................................................................................................25-13
Cross-Application Links................................................................................................................................25-14
Related Topics Links .....................................................................................................................................25-15
Related Topics Links Syntax .........................................................................................................................25-16
Uploading Your New or Changed Help Files................................................................................................25-17
File Upload Steps...........................................................................................................................................25-18
Updating the Search Index.............................................................................................................................25-20
Creating Reports ............................................................................................................................................25-21
Running Reports ............................................................................................................................................25-22
Customizing Help Navigation Trees..............................................................................................................25-23
Help Builder Functions..................................................................................................................................25-24
The Help Builder ...........................................................................................................................................25-25
Opening a Tree for Editing ............................................................................................................................25-26
Adding New Help Files to a Tree ..................................................................................................................25-27
Adding New Nodes to a Tree ........................................................................................................................25-28
For Further Information.................................................................................................................................25-29
Summary........................................................................................................................................................25-30
Guided Demonstrations and Practices...........................................................................................................26-1
Guided Demonstrations and Practices ...........................................................................................................26-3
Practice - Users..........................................................................................................................................26-4
Solution - Users .........................................................................................................................................26-5
Practice - Data Groups...............................................................................................................................26-9
Solution Data Groups .............................................................................................................................26-11
Practice - Menus ........................................................................................................................................26-13
Solution - Menus .......................................................................................................................................26-16
Practice - Query-Only Forms.....................................................................................................................26-24
Solution - Query-Only Forms ....................................................................................................................26-25
Practice - Responsibilities..........................................................................................................................26-30
Solution - Responsibilities .........................................................................................................................26-32
Guided Demonstration - Data Security Policy Example............................................................................26-36
Guided Demonstration - Creating Role Categories ...................................................................................26-37
Practice - Creating a Role and Placing it in a Role Inheritance Hierarchy ................................................26-38

xii
Appendix - Incorporating a Custom Program..............................................................................................24-1

Appendix - Incorporating a Custom Program................................................................................................24-3
Objectives ......................................................................................................................................................24-4
Using Custom Programs in Oracle Applications ...........................................................................................24-5
Assumptions for Incorporating a New Program ...........................................................................................24-6
Components of a Concurrent Program ..........................................................................................................24-7
Adding a Custom Program to Oracle Applications ......................................................................................24-8
Identifying the Executable.............................................................................................................................24-9
Creating the Concurrent Program ..................................................................................................................24-11
Concurrent Program Parameters Window .....................................................................................................24-13
Associating a Program with a Request Group ...............................................................................................24-15
Submitting the Concurrent Program ..............................................................................................................24-16
Summary........................................................................................................................................................24-17

xiii
Solution Creating a Role and Placing it in a Role Inheritance Hierarchy...............................................26-40

Practice - Assigning Permission Sets to the Role ......................................................................................26-42
Solution Assigning Permission Sets to the Role.....................................................................................26-44
Guided Demonstration - Setting Up Delegated Administration ................................................................26-45
Practice - Testing Delegated Administration.............................................................................................26-47
Solution Testing Delegated Administration............................................................................................26-49
Practice - Creating a Registration Process for the Role .............................................................................26-51
Solution Creating a Registration Process for the Role............................................................................26-53
Practice - Testing the Registration Process for the Role............................................................................26-54
Solution Testing the Registration Process for the Role ..........................................................................26-56
Practice - Profile Options...........................................................................................................................26-58
Solution - Profile Options..........................................................................................................................26-59
Practice - Auditing Resources....................................................................................................................26-61
Solution - Auditing Resources...................................................................................................................26-62
Guided Demonstration - Support Cart .......................................................................................................26-64
Practice - Scheduling Requests..................................................................................................................26-65
Solution - Scheduling Requests .................................................................................................................26-66
Practice - Request Groups .........................................................................................................................26-72
Solution - Request Groups.........................................................................................................................26-74
Practice - Coded Request Groups ..............................................................................................................26-76
Solution - Coded Request Groups .............................................................................................................26-78
Practice - Request Sets Using Wizard .......................................................................................................26-84
Solution - Request Sets Using Wizard.......................................................................................................26-85
Practice - Administering Concurrent Managers.........................................................................................26-87
Solution - Administering Concurrent Managers........................................................................................26-90
Guided Demonstration - Loading and Running a Workflow Process........................................................26-97
Practice - Define a Descriptive Flexfield...................................................................................................26-99
Solution Define a Descriptive Flexfield .................................................................................................26-104
Practice - Define a Descriptive Flexfield with None Validation ...............................................................26-109
Solution Define a Descriptive Flexfield with None Validation ..............................................................26-111
Practice - Define a Descriptive Flexfield with Context-Sensitive Segment ..............................................26-115
Solution Define a Descriptive Flexfield with a Context-Sensitive Segment ..........................................26-118
Practice - Define a Descriptive Flexfield with a Dependent Segment.......................................................26-124
Solution Define a Descriptive Flexfield with a Dependent Segment......................................................26-127
Practice - Define a Key Flexfield ..............................................................................................................26-131
Solution - Define a Key Flexfield..............................................................................................................26-135
Practice - Security Rules............................................................................................................................26-144
Solution Security Rules ..........................................................................................................................26-146
Practice - Cross-Validation Rules..............................................................................................................26-148
Solution - Cross-Validations......................................................................................................................26-150
Practice - Shorthand Aliases ......................................................................................................................26-152
Solution Shorthand Aliases.....................................................................................................................26-153
Practice - Table Validation ........................................................................................................................26-154
Solution Table Validation.......................................................................................................................26-155
Practice - Cascading Dependencies with $FLEX$ ....................................................................................26-157
Solution Cascading Dependencies with $FLEX$...................................................................................26-161
Guided Demonstration - Folders................................................................................................................26-166
Practice - Incorporating Custom Programs................................................................................................26-173
Solution - Incorporating Custom Programs ...............................................................................................26-174

Preface
Profile
Before You Begin This Course
Thorough knowledge of R12 Oracle Applications Navigation
Prerequisites
There are no prerequisites for this course.
How This Course Is Organized

This is an instructor-led course featuring lecture and hands-on exercises. Online demonstrations
and written practice sessions reinforce the concepts and skills introduced.

xv
Related Publications
Oracle Publications
Part Number
Oracle Applications System Administrators Guide Security
B31451
Oracle Applications System Administrators Guide Configuration
B31453
Oracle Applications System Administrators Guide Maintenance
B31454
Oracle Workflow Administrators Guide
B31431
Additional Publications
System release bulletins
Installation and users guides
Read-me files
International Oracle Users Group (IOUG) articles
Oracle Magazine

xvi
Title
Typographic Conventions
Typographic Conventions in Text
Caps and
lowercase
Courier new,
case sensitive
(default is
lowercase)
Initial cap
Element
Glossary term (if
there is a glossary)
Buttons,
check boxes,
triggers,
windows
Code output,
directory names,
filenames,
passwords,
pathnames,
URLs,
user input,
usernames
Arrow
Brackets
Commas
Graphics labels
(unless the term is a
proper noun)
Emphasized words
and phrases,
titles of books and
courses,
variables
Interface elements
with long names
that have only
initial caps;
lesson and chapter
titles in crossreferences
SQL column
names, commands,
functions, schemas,
table names
Menu paths
Key names
Key sequences
Plus signs
Key combinations
Italic
Quotation
marks
Uppercase
Example
The algorithm inserts the new key.
Click the Executable button.
Select the Cant Delete Card check box.
Assign a When-Validate-Item trigger to the ORD block.
Open the Master Schedule window.
Code output: debug.set (I, 300);
Directory: bin (DOS), $FMHOME (UNIX)
Filename: Locate the init.ora file.
Password: User tiger as your password.
Pathname: Open c:\my_docs\projects
URL: Go to http://www.oracle.com
User input: Enter 300
Username: Log on as scott
Customer address (but Oracle Payables)
Do not save changes to the database.

For further information, see Oracle7 Server SQL Language
Reference Manual.
Enter user_id@us.oracle.com, where user_id is the
name of the user.
Select Include a reusable module component and click Finish.
This subject is covered in Unit II, Lesson 3, Working with
Objects.
Use the SELECT command to view information stored in the

LAST_NAME
column of the EMP table.
Select File > Save.
Press [Enter].
Press and release keys one at a time:
[Alternate], [F], [D]
Press and hold these keys simultaneously: [Ctrl]+[Alt]+[Del]

xvii
Convention
Bold italic
Typographic Conventions in Code

Element
Oracle Forms
triggers
Column names,
table names
Example
When-Validate-Item
Passwords
DROP USER scott

IDENTIFIED BY tiger;
OG_ACTIVATE_LAYER
(OG_GET_LAYER (prod_pie_layer))
SELECT last_name
FROM s_emp;
PL/SQL objects
Lowercase
italic
Uppercase
CREATE ROLE role
Syntax variables
SQL commands and SELECT userid

FROM emp;
functions
Typographic Conventions in Oracle Application Navigation Paths

This course uses simplified navigation paths, such as the following example, to direct you
through Oracle Applications.
(N) Invoice > Entry > Invoice Batches Summary (M) Query > Find (B) Approve
This simplified path translates to the following:
1.
(N) From the Navigator window, select Invoice then Entry then Invoice Batches
Summary.
2.
(M) From the menu, select Query then Find.
3.
(B) Click the Approve button.
Notations:
(N) = Navigator
(M) = Menu
(T) = Tab
(B) = Button
(I) = Icon
(H) = Hyperlink
(ST) = Sub Tab

xviii
Convention
Caps and
lowercase
Lowercase
Typographical Conventions in Oracle Application Help System Paths

This course uses a navigation path convention to represent actions you perform to find
pertinent information in the Oracle Applications Help System.
The following help navigation path, for example
(Help) General Ledger > Journals > Enter Journals
1.
In the navigation frame of the help system window, expand the General Ledger entry.
2.
Under the General Ledger entry, expand Journals.
3.
Under Journals, select Enter Journals.
4.
Review the Enter Journals topic that appears in the document frame of the help system
window.

xix
represents the following sequence of actions:


xx
Chapter 15
Introduction to Oracle Workflow

Chapter
15 - Page 1 ONLY. COPYING eKIT MATERIALS FROM THIS
THESE eKIT MATERIALS ARE FOR YOUR USE IN THIS
CLASSROOM
Introduction to Oracle
Workflow


Chapter
CLASSROOM

Chapter
CLASSROOM
Objectives

Chapter
CLASSROOM
Enabling E-Business

Chapter
CLASSROOM
Inter-Enterprise Business Processes

In e-business, different enterprises need to communicate with each other over the Internet.
Oracle Workflow with the Business Event System can be used as part of an integration hub,
modeling business processes that span all of the enterprises involved in an end-to-end process.

Chapter
CLASSROOM
Inter-Enterprise Business Processes
Traditional Workflow
Traditional applications-based workflow processes are launched from a business application
through APIs hard-coded within the application. These processes model the business rules in
the individual local application and are made up of activities executed by the Workflow Engine
only in that applications system. For example, the modeling of an approval hierarchy is a
common use of Oracle Workflow in this scenario.

Chapter
CLASSROOM
Traditional Workflow
Workflow-Driven Business Processes

Oracle Workflow can help save time by:
Reducing repetitive data entry tasks
Automating approval hierarchies
Automatically delivering notifications and reminders of work to be done
Providing self-service monitoring capabilities

Chapter
CLASSROOM

Chapter
CLASSROOM
Sample Workflow Process

A workflow process consists of a sequence of activities that together make up a business flow,
expressing your organizations policies and rules. The activities can include significant
business events, automated functions, notifications to users, or subprocesses.
This example shows a sample order processing workflow process that includes business events.

Chapter
CLASSROOM
Sample Workflow Process
Event-Based Workflow
With the Business Event System, Oracle Workflow supports both traditional applicationsbased workflows and event-based integration workflows.
For e-business, there is a requirement to integrate with external systems, such as sending a
document to a business-to-business exchange, or other systems external to the local
application. Oracle Workflow supports e-business integration workflows by allowing business
analysts and developers to model business processes spanning different systems using a
graphical drag-and-drop designerthe Workflow Builderand run those processes using the
Workflow Engine and the Business Event System. This support enables Oracle Workflow
customers to deal with business objects in comprehensive e-business integration flows with
minimal intrusion into the core application.
The Business Event System and the Workflow Engine can function independently of each
other. However, you can achieve the most powerful and flexible processing by using the
Business Event System and the Workflow Engine together to execute cross-system processes
for e-business integration.

Chapter
CLASSROOM
Event-Based Workflow
Subscription-Based Processing
The Business Event System provides increased flexibility through subscription-based
processing: you raise a business event from an application, but specify the processing to
perform for that event as a subscription in Oracle Workflow. For example, you can launch a
workflow process when an event is raised by specifying that process in a subscription to the
event. You can also define multiple subscriptions to the same event to perform additional
processing for different purposes without intruding any further on the core application.

Chapter
CLASSROOM
Subscription-Based Processing
System Integration with Oracle Workflow

Chapter
CLASSROOM
Business Process-Based Integration

Business process-based integration is model-driven.
Business rules are expressed in a process model.
These rules define the policy for each end-to-end process.
The process model can encompass applications both within and beyond the enterprise.
Business process-based integration provides:
A global, enterprise-level view of business objects
Business process automation
Oracle Workflow supports business process-based integration through the Business Event
System.

Chapter
CLASSROOM
Business Process-Based Integration
Supported System Integration Types

The types of system integration supported by Oracle Workflow are message-based. By
supporting the communication of messages between systems, Oracle Workflow lets you define
processing across different systems encompassing both your own enterprise and your business
partners. The power of this cross-system processing, together with the flexibility provided by
subscription-based processing, enables you to use Oracle Workflow for e-business integration.

Chapter
CLASSROOM
Supported System Integration Types
Designing Applications for Change

The benefits of good design include:
Reduced cost of ownership through diminished development costs
Ease of management and maintenance
Visual documentation of business processes

Chapter
CLASSROOM
Designing Business Processes for Change

Complete process representation:
A workflow process can cross organizational and company boundaries to represent an
end-to-end flow.
You can provide alternatives within a process to accommodate different situations.
You can build management metrics and performance goals into a process.
Graphical development tool:
The Oracle Workflow Builder separates business process definition and modeling from
code development.
Workflow diagrams provide a visual overview of your processes.
You can easily modify a process definition.
Ease of management and maintenance:
Oracle Workflow lets you analyze time and costs for entire business processes.
You can refine your process definitions according to your analysis to streamline them and
reduce time and costs.
You can easily implement a modified process.

Chapter
CLASSROOM
Oracle Workflow empowers process participants by giving them access to review the
progress and current status of their processes.
Users can find the answers to many common questions themselves using these monitoring
capabilities.

Chapter
CLASSROOM
Designing Applications for Integration

Chapter
CLASSROOM

Business events as integration points:
Applications can raise business events at any point where further processing or integration
might be required.
You can define the processing to be triggered by an event immediately after defining the
event or at any later time.
Subscription-based processing:
Use subscriptions to specify the processing you want to perform for a business event.
You can define multiple subscriptions to the same event to perform additional processing
for different purposes.
Web-based business event and subscription management tool:
The Event Manager separates event subscription definition from code development.
You can use the Event Manager web pages to define, update, or delete event subscriptions
without intruding on the core application.

Chapter
CLASSROOM
Oracle Workflow in Oracle E-Business Suite

In Oracle E-Business Suite, Oracle Workflow is incorporated in applications including
Enterprise Resource Planning (ERP), Customer Relationship Management (CRM), and Human
Resources Management Systems (HRMS). Oracle Workflow is leveraged by both professional
applications, which are typically Forms-based applications for power users, and self-service
applications, which are typically HTML-based applications for more casual users.

Chapter
CLASSROOM
Oracle Workflow in Oracle E-Business Suite
Summary

Chapter
CLASSROOM
Chapter 16
Oracle Workflow Components

Chapter
CLASSROOM
Oracle Workflow
Components


Chapter
CLASSROOM

Chapter
CLASSROOM
Objectives

Chapter
CLASSROOM
Oracle Workflow Architecture

Development Client
The development client is a Windows PC. This tier is used to create and modify Oracle
Workflow process definitions, and to save and load flat files containing Oracle Workflow
process definitions and XML definitions for Business Event System objects.

Chapter
CLASSROOM

Oracle Database
The server tier is the Oracle Database that hosts the business application integrated with Oracle
Workflow, the Workflow Engine, Business Event System, Notification System, and directory
service. The Business Event System leverages the Advanced Queuing feature within the Oracle
Database.

Chapter
CLASSROOM

Application Server
The application server is the middle tier environment outside of the database. This environment
includes ancillary services such as Oracle HTTP Server as the Web server, and Oracle
Workflow service components that run in the middle tier, such as agent listeners and
notification mailers.

Chapter
CLASSROOM

End-User Client
The end-user client is the workstation or PC that an end user uses to perform daily tasks. This
client includes browser support for accessing Oracle Workflow Web pages, as well as for
accessing the Oracle Workflow Manager component available through Oracle Applications
Manager (OAM). The end-user client also includes a mail client application for reviewing and
responding to notifications by e-mail.

Chapter
CLASSROOM

Chapter
CLASSROOM
Workflow Engine

Chapter
CLASSROOM
Workflow Processes
A workflow process definition must be saved to the same database as the Workflow Engine. A
process definition is composed of activities and the transitions between them.
A completed application transaction or event can initiate a workflow process by raising an
event or by calling a series of Workflow Engine APIs.
The Workflow Engine locates the Start activity in the process definition.
The Workflow Engine drives through the process, performing all automated steps such as
function activities and Raise and Send event activities, until an asynchronous activity such
as a notification, Receive event activity, or blocking activity occurs.
- The Workflow Engine calls the Notification System to deliver a notification message
to an appropriate role. Once a user of that role completes the notification response,
the Workflow Engine continues to drive through the remaining activities in the
process.
- If a blocking activity is encountered, the Workflow Engine waits for an external
program to complete and call the appropriate Workflow Engine API before
proceeding to the next activity.

Chapter
CLASSROOM
Workflow Processes
- If a Receive event activity is encountered, the Workflow Engine waits to receive the
event from the Business Event System before proceeding to the next activity.
The process completes when the Workflow Engine encounters an End activity.
Example: Order Processing
This example shows a workflow process that includes business events.

Chapter
CLASSROOM
Supported Process Constructs

The Workflow Engine supports sophisticated workflow rules to model your business logic.

Chapter
CLASSROOM

Chapter
CLASSROOM

Chapter
CLASSROOM

Chapter
CLASSROOM
Oracle Workflow Builder

Saving workflow definitions as flat files on the local file system enables designers to back up
their work and use source control.
Navigator Tree
The navigator provides a tree structure for the workflow definition, with the highest level being
the data store. Next is the item type, which is a grouping of workflow objects into a high-level
category. The lower levels are the workflow objects themselves, such as attributes, processes,
notifications, functions, events, messages, and lookup types. All these objects are organized
into their respective categories within the tree.
Process Diagram
The diagram is made up of icons representing workflow objects. A diagram is built by
dragging the objects from the navigator window and dropping them into the process diagram
window. This method is called bottom-up design. You can also create new objects as you
design the diagram and complete the definitions of those objects later. This method is called
top-down design.

Chapter
CLASSROOM
Oracle Workflow Builder
Business Event System Architecture

The Business Event System is an application service that communicates business events
between systems. Oracle Workflow with the Business Event System can act as a system
integration messaging hub that relays business event messages among systems.
The Business Event System leverages Oracle Advanced Queuing to send messages from one
system to another.
For the greatest flexibility in routing and processing business events, you can model your
business process logic in powerful cross-system workflow processes that are executed by the
Workflow Engine. However, the Business Event System can also function independently of the
Workflow Engine.

Chapter
CLASSROOM
Business Event System Architecture
Business Event System Components

Chapter
CLASSROOM
Advanced Queuing, an Enabling Technology

Oracle Advanced Queuing allows queue-to-queue propagation across machine boundaries.
Oracle Advanced Queuing is a feature of the Oracle Database that provides database-integrated
message queuing functionality, leveraging the functions of the Oracle Database to store
messages persistently and transmit them using various transport protocols.
Java Message Service (JMS) is a messaging standard defined by Sun Microsystems, Oracle,
IBM, and other vendors. Oracle Java Message Service (OJMS) provides a Java API for Oracle
Advanced Queuing based on the JMS standard. Oracle Workflow supports communication of
JMS Text messages through Oracle Advanced Queuing in a format called
SYS.AQ$_JMS_TEXT_MESSAGE.
Oracle Workflow also supports business event messages in a standard Workflow format called
WF_EVENT_T. You can additionally define custom message formats.
For more information, refer to the Oracle Streams Advanced Queuing Users Guide and
Reference.

Chapter
CLASSROOM
Advanced Queuing, an Enabling Technology
Oracle Database Communication Alternatives

You can use Oracle Advanced Queuing for communication by SQLNET, HTTP, and HTTPS
protocols, and for integration with third-party messaging solutions.
You can use Oracle Net Services (formerly Net8) to propagate messages by the SQLNET
protocol. Oracle Workflow supports JMS Text messages for SQLNET propagation, as well as
business event messages in a standard Workflow format called WF_EVENT_T. You can also
define custom message formats.
The Oracle Streams Advanced Queuing Internet access functionality lets you perform Oracle
Advanced Queuing operations over the Internet by using the Oracle Advanced Queuing
Internet Data Access Presentation (IDAP) for messages and transmitting the messages over the
Internet using transport protocols such as HTTP or HTTPS.
Messaging Gateway is a feature of Oracle Advanced Queuing that enables communication
between applications based on non-Oracle messaging systems and Oracle Advanced Queuing.
Standard Oracle Advanced Queuing functionality provides propagation between two Oracle
Advanced Queuing queues; Messaging Gateway extends that propagation to legacy
applications based on non-Oracle messaging systems.

Chapter
CLASSROOM
Oracle Database Communication Alternatives
For more information, refer to the Oracle Streams Advanced Queuing Users Guide and
Reference.

Chapter
CLASSROOM
Accessing Oracle Workflow Web Pages

Chapter
CLASSROOM
Oracle Workflow Home Pages

Administrator home page: Lists your five highest priority notifications. Also provides tabs
to the Developer Studio, Event Manager (Business Events), administrator Status Monitor,
Advanced Worklist, and Administration pages.
Self-service home page: Lists your five highest priority notifications as well as the five
most recent workflows that you own that were started in the last two weeks. Also provides
tabs to the Advanced Worklist and self-service Status Monitor.

Chapter
CLASSROOM
Oracle Workflow Home Pages
Notification System
The Notification System:
Routes notifications to a role, which can be a single user or group of users
Enables users to receive and respond to notifications using an e-mail application or Web
browser of choice
Sends e-mail notifications and processes e-mail responses using the JavaMail API
Allows any users with access to the Internet to be included in a workflow process
Provides access to the Worklist from Oracle E-Business Suite through the Worklist web
pages
Enables users to drill down from a notification in the Worklist web pages to any URL or
Oracle E-Business Suite form to respond to the notification

Chapter
CLASSROOM
Notification System
Worklist Web Pages

Oracle Workflow includes two different versions of the Worklist in the Oracle Application
Framework user interface format:
Advanced Worklist: Provides full notification information as well as additional options for
displaying and administering notifications
Personal Worklist: Provides additional search and filtering options for displaying
notifications

Chapter
CLASSROOM
Worklist Web Pages
E-Mail Notifications

Chapter
CLASSROOM
Directory Services
Users can be associated with more than one role, and a role may contain more than one user.
The Workflow Engine and Notification System use the directory service to determine who
should receive notifications and in what format. Notifications can be delivered to an individual
user or to all members of a particular role.
Note: Oracle Workflow uses a directory service model in which denormalized information is
maintained in the Workflow local tables for performance gain. You should maintain
synchronization between the user and role information stored in application tables by the
source modules and the information stored in the Workflow local tables.

Chapter
CLASSROOM
Directory Services
Workflow Monitor
Oracle Workflow includes both administrator and self-service versions of the Status Monitor in
the Oracle Application Framework user interface format.

Chapter
CLASSROOM
Status Monitor Web Pages
Loading Workflow Definitions

The Workflow Definitions Loader is a utility program that lets you transfer process definitions
between a database and a flat file. The Workflow Definitions Loader:
Runs on the server machine.
Lets you upgrade a database with new versions of process definitions or upload existing
process definitions after a database upgrade.
Is also integrated into Oracle Workflow Builder.
Allows process definitions to be source-controlled as flat files.

Chapter
CLASSROOM
Workflow Definitions Loader
Workflow XML Loader

The Workflow XML Loader is a utility program that lets you transfer XML definitions for
Business Event System objects between a database and a flat file.
When you download Business Event System object definitions from a database, Oracle
Workflow saves the definitions as an XML file.
When you upload object definitions to a database, Oracle Workflow loads the definitions
from the source XML file into the Business Event System tables in the database, creating
new definitions or updating existing definitions as necessary.

Chapter
CLASSROOM
Workflow XML Loader
Workflow Manager
Administrators can use Workflow Manager to perform the following tasks:
Run Workflow service components, such as notification mailers and agent listeners.
Control other Workflow system services, including background engines, purging obsolete
Workflow data, and cleanup of the Workflow control queue.
Monitor work item processing by viewing the distribution of all work items by status and
drilling down to additional information.
Monitor event message processing for local Business Event System agents by viewing the
distribution of event messages by status and drilling down to additional agent information
and individual event messages, as well as by viewing queue propagation details.
With this ability to monitor work items and event messages, a system administrator can
identify possible bottlenecks easily.

Chapter
CLASSROOM
Workflow Manager
Service Components
Oracle Workflow uses the Generic Service Component Framework (GSCF) to simplify and
automate the management of background Java services. A service component is an instance of
a Java program that has been defined according to the GSCF standards so that it can be
managed through this framework.
Use Oracle Workflow Manager to configure and run service components.
Note: Oracle Workflow Manager also lets you manage Web services outbound components,
which process outbound Web service messages for Oracle XML Gateway. For more
information, see the Oracle XML Gateway Users Guide.

Chapter
CLASSROOM
Service Components
Oracle Workflow Documentation

The main Oracle Workflow documentation set includes the following:
Oracle Workflow Administrators Guide: Explains how to complete the setup steps
necessary for any product that includes Workflow-enabled processes, as well as how to
monitor the progress of run-time workflow processes.
Oracle Workflow Developers Guide: Explains how to define new workflow business
processes and customize existing Oracle E-Business Suite-embedded workflow processes.
It also describes how to define and customize business events and event subscriptions.
Oracle Workflow Users Guide: Describes how users can view and respond to workflow
notifications and monitor the progress of their workflow processes.
Oracle Workflow API Reference: Describes the APIs provided for developers and
administrators to access Oracle Workflow.
You can also consult the following:
Installation documentation for your release and platform, usually available within the
installation software bundle.

Chapter
CLASSROOM
Oracle Workflow Documentation
Oracle Workflow Documentation Resources, Release 12, (note 396314.1), available on

OracleMetaLink.

Chapter
CLASSROOM
Review Questions and Solutions

Which component of Oracle Workflow:
Communicates business events among systems? Business Event System
Executes workflow processes? Workflow Engine
Lets you develop workflow process definitions? Oracle Workflow Builder
Delivers process-related messages to users? Notification System
Lets you review and administer a run-time process? Status Monitor

Chapter
CLASSROOM
Review Questions
Summary

Chapter
CLASSROOM


Chapter
CLASSROOM
Chapter 17
Setting Up Oracle Workflow

Chapter
CLASSROOM


Chapter
CLASSROOM

Chapter
CLASSROOM
Objectives

Chapter
CLASSROOM
Required Setup Steps

1. Set system-wide preferences and default user preferences for your installation of Oracle
Workflow using the Workflow Configuration page.
2. Ensure that a directory service is set up to provide information about the individuals and
roles in your organization who may utilize Oracle Workflow functionality and receive
workflow notifications.
3. Set up background Workflow engines to manage the load on the primary Workflow
Engine by processing deferred and timed out activities and stuck processes.
4. Configure the Business Event System for event communication.
For more information, refer to the Setting Up Oracle Workflow chapter in the Oracle
Workflow Administrators Guide.

Chapter
CLASSROOM
Required Setup Steps
Setting Global Workflow Preferences

Use a Web browser to navigate to the Workflow Configuration page, using a responsibility and
navigation path specified by your system administrator. Some possible navigation paths in the
seeded Workflow responsibilities are:
Workflow Administrator Web Applications: Administration > Workflow Preferences
Workflow Administrator Web (New): Administration > Workflow Preferences
Workflow Administrator Event Manager: Administration > Workflow Preferences
You can also navigate to the Workflow Configuration page from other Oracle Workflow
administrator Web pages by choosing the Administration tab or selecting the Administration
link at the end of the page.
You must have workflow administrator privileges to set global workflow preferences on the
Workflow Configuration page. If you do not have administrator privileges, you can view
global workflow preferences, but you cannot modify them.
Workflow System Administrator

Chapter
CLASSROOM
Step 1 Setting Global Workflow Preferences

Chapter
CLASSROOM
Select the role to which you want to assign workflow administrator privileges. If you want all
users and roles to have workflow administrator privileges, such as in a development
environment, enter an asterisk (*).
LDAP
If you are integrating with Oracle Internet Directory, specify the Lightweight Directory Access
Protocol (LDAP) server information for the LDAP directory to which you will connect. If you
already configured these parameters while installing Oracle Application Server with Oracle EBusiness Suite, Oracle Workflow displays those values here. For more information, see:
Installing Oracle Application Server 10g with Oracle E-Business Suite Release 12
(OracleMetaLink note 376811.1) and Oracle Single Sign-On Integration, Oracle Applications
System Administrator's Guide - Security.
Host: The host on which the LDAP directory resides.
Port: The port on the host.
Username: The LDAP user account used to connect to the LDAP server. This user name
must have write privileges and is required to bind to the LDAP directory.
Old Password: Enter your current LDAP password. Oracle Workflow validates this
password before letting you change it.
New Password: Enter the new LDAP password you want to use. The password must be at
least five characters long.
Repeat Password: Enter your new LDAP password again in this field to confirm it.
Change Log Base Directory: The LDAP node under which change logs are located.
User Base Directory: The LDAP node under which user records can be found.
Business Event Local System
Specify the system name for the database where this installation of Oracle Workflow is
located, to identify it in the Business Event System. Oracle Workflow automatically creates the
system definition for this database in the Event Manager during installation.
Select the execution status for the local system.
Enabled: Subscriptions are executed on all events. Oracle Workflow sets the system status
to Enabled by default.
Local Only: Subscriptions are executed only on events raised on the local system.
External Only: Subscriptions are executed only on events received by inbound agents on
the local system.
Disabled: No subscriptions are executed on any events.
Notification Style
Specify whether Oracle Workflow should send e-mail notifications to users, and if so, in what
format. A user can override this default setting by specifying a different notification style in his
or her individual Oracle EBusiness Suite preferences.
HTML mail with attachments
Plain text mail with HTML attachments
Plain text mail
Plain text summary mail
Do not send me mail

Chapter
CLASSROOM
HTML mail
HTML summary mail
Browser Signing DLL Location
Specify the location of the Capicom.dll file that is used for Web page operations with
encryption in the Microsoft Internet Explorer browser. This preference is required only if you
plan to use certificate-based digital signatures to confirm notification responses, and your users
access Oracle Applications with Microsoft Internet Explorer. By default, this preference is set
to a URL at which the Capicom.dll file can be downloaded from Microsofts Web site. In most
cases, you do not need to change this setting. However, you can update this preference if the
location of the Capicom.dll file changes, or if you choose to store a copy of the file on your
local network and point to that location instead.
JInitiator
Review details about the JInitiator plugin in your Oracle E-Business Suite installation. Oracle
Workflow uses JInitiator to launch Oracle Applications forms linked to notifications.
Class ID: The class identifier for this version of JInitiator.
Download Location: The location where the JInitiator executable is staged for download
to users client machines.
Version: The JInitiator version number.
Setting Up an Oracle Workflow Directory Service

In the predefined directory service implementation, Oracle Workflow automatically creates
directory service views to integrate with the appropriate source tables.
You can also create your own directory service by defining custom views with the required
columns. However, note that only the predefined directory service provided by Oracle
Workflow is supported by Oracle.

Chapter
CLASSROOM
Step 2 Setting Up an Oracle Workflow Directory Service

Chapter
CLASSROOM
Setting Up an Oracle Workflow Directory Service

You only need to run the bulk synchronization program for products that are not successfully
performing incremental synchronization.
The Synchronize Workflow LOCAL Tables request set contains ten instances of the
Synchronize WF Local Tables program, one for each originating system. You can use this
request set to submit requests for all the originating systems at once.
Use the Submit Requests form to submit the request set or concurrent program. Enter the
following parameters:
Orig System (single concurrent program only): Select the name of the originating system
whose user and role information you want to synchronize with the WF_LOCAL tables.
Parallel Processes: Enter the number of parallel processes to run. The default value for this
parameter is 1. However, if your hardware resources allow, you can optionally set this
parameter to a higher value in order to parallelize the queries during execution of the
program.
Logging: Select the logging mode you want. This mode determines whether redo log data
is generated for database operations performed by the bulk synchronization process. The
default value for this parameter is LOGGING, which generates redo log data normally.

Chapter
CLASSROOM
You can optionally set the logging mode to NOLOGGING to suppress redo log data,
obtaining a performance gain. Without this redo log data, however, no media recovery is
possible for the Workflow directory tables and indexes.
Temporary Tablespace: Select the temporary tablespace the program should use.
Raise Errors: Select Yes or No to indicate whether the program should raise an exception
if it encounters an error. Usually you can leave this parameter set to the default value,
which is Yes.
Note: Products that use role hierarchies do not participate in bulk synchronization. These
products must perform incremental synchronization.

Chapter
CLASSROOM
Running Background Engines

Ensure that you have at least one background engine that can check for timed out activities,
one that can process deferred activities, and one that can handle stuck processes. At a
minimum, you need to set up one background engine that can handle all three types of issues.
However, for performance reasons we recommend that you run three separate background
engines at different intervals.
Run a background engine to handle only deferred activities every 5 to 60 minutes.
Run a background engine to handle only timed out activities every 1 to 24 hours as
needed.
Run a background engine to handle only stuck processes once a week to once a month,
when the load on the system is low.

Chapter
CLASSROOM
Step 3 Running Background Engines

Chapter
CLASSROOM
Running Background Engines

The Background Engine API parameters are:
itemtype: Optional item type to restrict this engine to activities associated with that item
type.
minthreshold: Optional minimum cost that an activity must have for this background
engine to execute it, in hundredths of a second.
maxthreshold: Optional maximum cost an activity can have for this background engine to
execute it, in hundredths of a second.
process_deferred: Specify TRUE or FALSE to indicate whether the engine should check
for deferred activities.
process_timeout: Specify TRUE or FALSE to indicate whether the engine should check
for timed out activities.
process_stuck: Specify TRUE or FALSE to indicate whether the engine should check for
stuck processes.

Chapter
CLASSROOM
Configuring the Business Event System

You can also optionally perform these steps:
To enhance performance, you can change the maximum cache size used in Business Event
System subscription processing and enable static function calls for custom PL/SQL
functions.
If you want to invoke business process execution language (BPEL) processes through
event subscriptions, you can optionally specify the BPEL server.

Chapter
CLASSROOM
Step 4 Configuring the Business Event System
Event Message Communication

To send an event message, Oracle Workflow places the event message on a local outbound
agents queue. You must schedule propagation to deliver the message from there to the
designated inbound agents queue.
To receive an event message in Oracle Workflow, you must run an agent listener to dequeue
the message from the inbound agents queue for Oracle Workflow to process. A component of
the Event Manager called the Event Dispatcher then searches for and executes subscriptions to
the event.

Chapter
CLASSROOM
Step 4 Event Message Communication
Setting Up Database Links and Queues

Database Links
When you set up database links for use by the Business Event System, you should fully qualify
each database link name with the domain name.
Queues
In addition to the standard queues provide by Oracle Workflow, you can also set up your own
queues for event message propagation. To set up a queue, you must create the queue table,
create the queue, and start the queue.
Oracle Workflow provides a sample script called wfevquc2.sql, which you can modify to set
up your queues, as well as a sample script called wfevqued.sql, which you can modify to drop
queues. These scripts are located on your server in the $FND_TOP/sql directory.
If you define a queue with a payload type other than the standard WF_EVENT_T Workflow
format or the JMS Text message format, you must create a queue handler to translate between
the standard Workflow format and the format required by the queue.

Chapter
CLASSROOM
Step 4 Setting Up Database Links and Queues
Checking Database Parameters

The JOB_QUEUE_PROCESSES parameter defines the number of SNP job queue processes
for your instance. You must start at least one job queue process to enable message propagation.
The minimum recommended number of processes for Oracle Workflow is ten.
You can either modify the parameter in the init.ora file and restart the database, or you can use
the ALTER SYSTEM statement to dynamically modify the parameter for the duration of the
instance.
Note: If you want to review more detailed information about Oracle Advanced Queuing
processing, you can optionally use another initialization parameter, EVENT, for detailed
database level tracing of issues related to Oracle Advanced Queuing. Add the following line to
your init.ora file:
event = "24040 trace name context forever, level 10"
Then restart your database to make this change effective. Be aware that using this parameter
may generate large trace files.

Chapter
CLASSROOM
Step 4 Checking Database Parameters
Scheduling Agent Listeners

The Generic Service Component Framework is a facility that helps to simplify and automate
the management of background Java services.
Agent listener service components, managed through Oracle Workflow Manager, are the most
automated and robust way to run agent listeners. However, Oracle Workflow also provides an
administrative script named wfagtlst.sql that you can use to run an agent listener, or you can
run the WF_EVENT.Listen API directly in SQL*Plus. These methods are intended primarily
for testing and debugging purposes.

Chapter
CLASSROOM
Step 4 Scheduling Agent Listeners
Scheduling Agent Listeners

Seeded PL/SQL agent listeners:
Workflow Deferred Agent Listener: Handles messages on WF_DEFERRED to support
deferred subscription processing.
Workflow Deferred Notification Agent Listener: Handles notification messages on
WF_DEFERRED to support outbound notification processing.
Workflow Error Agent Listener: Handles messages on WF_ERROR to support error
handling for the Business Event System.
Workflow Inbound Notifications Agent Listener: Handles messages on
WF_NOTIFICATION_IN to support inbound e-mail notification processing.
Seeded Java agent listeners:
Workflow Java Deferred Agent Listener: Handles messages on WF_JAVA_DEFERRED
to support deferred subscription processing in the middle tier.
Workflow Java Error Agent Listener: Handles messages on WF_JAVA_ERROR to
support error handling for the Business Event System in the middle tier.

Chapter
CLASSROOM
Step 4 Scheduling Agent Listeners
Oracle XML Gateway also provides PL/SQL agent listeners named ECX Inbound Agent
Listener and ECX Transaction Agent Listener, and a Java agent listener named Web Services
IN Agent. See: Oracle XML Gateway User's Guide.
You can optionally create additional agent listener service components. For example, you can
configure agent listeners for other inbound agents that you want to use for event message
propagation, such as the standard WF_IN and WF_JMS_IN agents, or any custom agents. You
can also configure an agent listener service component that only processes messages on a
particular agent that are instances of a specific event.

Chapter
CLASSROOM
Scheduling Propagation
If you want to use the standard WF_OUT and WF_JMS_OUT agents or custom agents for
event message propagation, ensure that you schedule propagation for those agents.

Chapter
CLASSROOM
Step 4 Scheduling Propagation
For information about using Oracle Enterprise Manager to schedule Oracle Advanced Queuing
propagation, refer to Oracle Enterprise Manager Support, Oracle Streams Advanced Queuing
User's Guide and Reference and the Oracle Enterprise Manager online help.

Chapter
CLASSROOM
The Schedule_Propagation API parameters are:
queue_name: The queue associated with the local outbound agent for which you want to
schedule propagation. Specify the queue name prefaced by the schema that owns the
queue, in the following format: <schema>.<queue>
The standard Workflow queues are usually owned by the APPLSYS schema.
destination: The database link to the remote system to which you want to propagate
messages. To propagate messages to another queue on the local system, enter the
destination NULL. The default value is NULL.
start_time: The initial start time for the propagation window.
duration: The duration of the propagation window, in seconds
next_time: A date function to compute the start of the next propagation window from the
end of the current window. For example, to start the window at the same time every day,
next_time should be specified as 'SYSDATE + 1 - duration/86400'. If this value is NULL,
then propagation is stopped at the end of the current window and is not run repeatedly.
The default value is NULL.

Chapter
CLASSROOM
latency: A latency time in seconds to specify how long you want to wait, after all
messages have been propagated, before rechecking the queue for new messages to the
destination. The latency represents the maximum wait time during the propagation
window for a message to be propagated after it is enqueued. To propagate messages as
soon as possible after they are enqueued, enter a latency of zero. The default latency is 60
seconds.

Chapter
CLASSROOM
Synchronizing License Statuses

You can use the License Manager utility to review which products you currently have licensed.
See: License Manager, Oracle Applications System Administrators Guide - Maintenance.
Use the Submit Requests form to submit the Synchronize Product License and Workflow BES
License concurrent program (FNDWFLIC). This program does not require any parameters.
If you upgrade from an Oracle E-Business Suite release earlier than Release 11.5.9, you should
run the Synchronize Product License and Workflow BES License concurrent program once
after the upgrade to update the license status of the existing events and subscriptions in your
Event Manager. Otherwise, subscriptions may not be correctly processed after the upgrade.
Subsequently, when you license a product, Oracle Workflow automatically updates the license
status for all the events and subscriptions owned by that product.
Note: Any events and subscriptions that you define with a customization level of User are
always treated as being licensed.

Chapter
CLASSROOM
Step 4 Synchronizing License Statuses
Cleaning Up the WF_CONTROL Queue

The WF_CONTROL agent is used for internal processing only. You should not place custom
event messages on this queue.You do not need to schedule propagation for the
WF_CONTROL agent, because the middle tier processes that use WF_CONTROL dequeue
messages directly from its queue. However, this queue should be cleaned up periodically.
When a middle tier process for Oracle E-Business Suite starts up, it creates a JMS subscriber to
the WF_CONTROL queue. If a middle tier process dies, however, the corresponding
subscriber remains in the database. For more efficient processing, you should ensure that
WF_CONTROL is periodically cleaned up by removing the subscribers for any middle tier
processes that are no longer active. The recommended frequency for performing cleanup is
every 12 hours.
Use Oracle Workflow Manager to manage the Workflow Control Queue Cleanup
(FNDWFBES_CONTROL_QUEUE_CLEANUP) concurrent program, which uses the
WF_BES_CLEANUP.Cleanup_Subscribers() API to perform the necessary cleanup. This
concurrent program is scheduled to run every 12 hours by default. The program does not
require any parameters.

Chapter
CLASSROOM
Step 4 Cleaning Up the WF_CONTROL Queue
Tuning Performance
Changing the Maximum Cache Size for the Business Event System
The Business Event System caches event, subscription, and agent definitions to enhance
performance during subscription processing. The default maximum size of the cache is 50
records. You can optionally increase the maximum cache size to reduce the database queries
performed by the Business Event System, or decrease the maximum cache size to reduce the
amount of memory used by the cache.
The maximum cache size is determined by the value for the WFBES_MAX_CACHE_SIZE
resource token. To change this value, you must first create a .msg source file specifying the
new size as the value for the WFBES_MAX_CACHE_SIZE resource token. Then use the
Workflow Resource Generator program to upload the new seed data from the source file to the
database table WF_RESOURCES. See: To Run the Workflow Resource Generator, Oracle
Workflow API Reference.
Enabling Static Function Calls for Custom PL/SQL Functions
If you use custom PL/SQL functions within the Business Event System, including event data
generate functions, event subscription rule functions, and queue handler enqueue and dequeue

Chapter
CLASSROOM
Step 4 Tuning Performance

Chapter
CLASSROOM
APIs, Oracle Workflow calls those functions using dynamic SQL by default. However, you
can enable Oracle Workflow to call your custom functions statically to enhance performance.
Oracle Workflow provides two PL/SQL packages with procedures that contain lists of static
function calls. The Business Event System internally calls these procedures during subscription
processing to check whether static function calls are available for the procedures being
executed.
WF_BES_DYN_FUNCS package - Contains static function calls for generate functions
and rule functions.
WF_AGT_DYN_FUNCS package - Contains static function calls for queue handler
enqueue and dequeue APIs.
The initial seeded versions of these packages include static function calls only for seeded Oracle
Workflow functions, such as the rule function WF_RULE.Default_Rule and the queue handler
APIs WF_EVENT_QH.Enqueue and WF_EVENT_QH.Dequeue. You can use the
wfbesfngen.sql script to add functions from other Oracle Applications products or your own
custom functions to these packages.
Specifying the BPEL Server

The WF: BPEL Server profile option lets you quickly change the BPEL server setup for all
subscriptions that invoke BPEL processes, such as if you move these subscription definitions
from a test instance to a production instance. See: Invoking a Web Service, Oracle Workflow
Developer's Guide.

Chapter
CLASSROOM
Step 4 Specifying the BPEL Server
Optional Setup Steps

1. Partition certain Workflow tables for performance gain.
2. Set up additional languages if you want to use Oracle Workflow in languages other than
English.
3. Set up one or more notification mailers if you want to allow your users to receive
notifications by e-mail.
4. Customize the templates for your e-mail notifications.
5. Give users access to the Advanced Worklist, Personal Worklist, and and Notifications
administrator search Web pages from any responsibility you choose.
6. Use the WF: Notification Reassign Mode profile option to control which reassign modes
are available to users from the Notification Details page.
7. Control the item types for which users can define vacation rules and grant worklist
access, using the WF: Vacation Rule Item Types lookup type and the WF: Vacation
Rules - Allow All profile option.
8. Set up users to enable electronic signatures in notification responses.
9. Customize the company logo that appears in Oracle Workflow Web pages.

Chapter
CLASSROOM
Optional Setup Steps
10. Include additional icons in your Oracle Workflow icons subdirectory to customize the
diagrammatic representation of your workflow processes.
For more information, refer to the Setting Up Oracle Workflow chapter in the Oracle
Workflow Administrators Guide.

Chapter
CLASSROOM
Partitioning Workflow Tables

The wfupartb.sql script partitions the following tables:
WF_ITEM_ACTIVITY_STATUSES
WF_ITEM_ACTIVITY_STATUSES_H
WF_ITEM_ATTRIBUTE_VALUES
WF_ITEMS
The script recreates the following indexes:
WF_ITEM_ACTIVITY_STATUSES_PK
WF_ITEM_ACTIVITY_STATUSES_N1
WF_ITEM_ACTIVITY_STATUSES_N2
WF_ITEM_ACTIVITY_STATUSES_H_N1
WF_ITEM_ACTIVITY_STATUSES_H_N2
WF_ITEM_ATTRIBUTE_VALUES_PK
WF_ITEMS_PK
WF_ITEMS_N1

Chapter
CLASSROOM
Optional Step 1 Partitioning Workflow Tables
WF_ITEMS_N2
WF_ITEMS_N3

Chapter
CLASSROOM
Setting Up Additional Languages

Note: You can display languages that require a multibyte character set only if your database
uses a character set that supports these languages, such as UTF8.
Displaying Oracle Workflow Web Pages in Other Languages
You select and install additional languages as part of the Oracle E-Business Suite installation.
Users can set their language preference to an installed language through the Personal
Homepage.
Creating and Viewing Workflow Definitions in Other Languages using Oracle Workflow
Builder
Set the NLS_LANG environment variable for the new language, territory, and encoded
character set that you want to use for the workflow definition. Specify the value for
NLS_LANG in the following format: LANGUAGE_TERRITORY.CHARSET Use the
Registry Editor on your PC to set the NLS_LANG environment variable:
- Select Run from the Start menu on your PC.
- Enter the command to run the Registry Editor and click OK. The command depends
on your version of Windows; for example, it may be regedit or regedit32.

Chapter
CLASSROOM
Optional Step 2 Setting Up Additional Languages

Chapter
CLASSROOM
- Drill down to My Computer > HKEY_LOCAL_MACHINE > Software > Oracle, and
then to the Oracle home where the Workflow Builder is installed.
- Select the NLS_LANG variable and select Modify from the Edit menu.
- Enter the value you want and click OK.
- Exit the Registry Editor.
Start Oracle Workflow Builder. Create a translated version of your workflow definition
and save it as a flat file (.wft), or open and view a workflow definition that is already
translated.
Loading Workflow Definitions in Other Languages to a Database
Ensure that the language you want is set up in the database. You select and install
additional languages as part of the Oracle E-Business Suite installation.
Before running the Workflow Definitions Loader program to load a translated workflow
definition to your database, you must set the NLS_LANG environment variable to the
appropriate territory and character set for the workflow definition you want to load. The
character set must match the character set encoding used to create the workflow definition
file, which is determined by the NLS_LANG value that was set on the client PC before the
.wft file was created in the Workflow Builder. To set NLS_LANG before running the
Workflow Definitions Loader, use the following format: _TERRITORY.CHARSET
Note that it is important to include the underscore (_) before the territory name and the
period (.) between the territory name and the character set name in the NLS_LANG value.
You do not need to include the language in this NLS_LANG value because the Workflow
Definitions Loader uses the language specified within the .wft file to determine the
language to load.
Before using the Workflow Builder to save a translated workflow definition to your
database, you must set the NLS_LANG environment variable to the appropriate language,
territory, and character set. If you are saving several workflow definitions in different
languages, you must reset NLS_LANG for each language.
Sending E-mail Notifications in Other Languages
Determine whether Oracle has translated the e-mail notification templates to the language
you want to set by checking for the file containing the templates in the appropriate
language subdirectory, $FND_TOP/import/<lang>. The standard templates are delivered
in a file called wfmail.wft.
If the e-mail templates are available for the desired language, Oracle Workflow uses the
language preference for the notification recipient to determine the language for an e-mail
notification.
Optional Step 3 Implementing Notification Mailers

Chapter
CLASSROOM

Chapter
CLASSROOM
Implementing Notification Mailers

Users can receive e-mail notifications using various e-mail clients, although notifications may
be displayed differently in different clients, depending on the features each client supports.
Oracle Workflow fully supports Multipurpose Internet Mail Extensions (MIME) encoded
messages. This means that a notification mailer can exchange messages with workflow users
containing languages with different character sets and multimedia encoded content.

Chapter
CLASSROOM
Customizing Message Templates

Message templates are defined in the System: Mailer item type, stored in a file named
wfmail.wft. It is not recommended to modify the standard templates. However, you can choose
to use the alternative templates provided by Oracle Workflow instead of the default templates,
or you can also create your own custom templates in the System: Mailer item type. For more
information, refer to the Setting Up Oracle Workflow chapter in the Oracle Workflow
Administrators Guide.
You can implement alternative standard or custom templates in the following ways:
Assign the templates that you want to a particular notification mailer service component in
the mailer configuration parameters. The templates assigned to a mailer override the
default System: Mailer templates.
Assign the templates that you want to a particular notification in a workflow process by
defining special message attributes. In this case the templates assigned to the notification
override both the templates assigned to a mailer and the default System: Mailer templates.

Chapter
CLASSROOM
Optional Step 4 Customizing Message Templates
Customizing Message Templates

The following standard message templates are used by default. An asterisk (*) marks the
templates for which Oracle Workflow also provides an alternative version.
* Open Mail (Templated): For notifications that require a response when you are using the
templated response method
* Open Mail (Direct): For notifications that require a response when you are using the
direct response method
* Open Mail (Outlook Express): For notifications that require a response, if you use an email application such as Microsoft Outlook Express as your e-mail client
* Open FYI Mail: For notifications that do not require a response
View From UI: For response-required notifications whose content you do not want to send
in e-mail
View FYI From UI: For notifications that do not require a response, whose content you do
not want to send in e-mail
URL Attachment: Creates the Notification References attachment for HTML-formatted
notification messages that include URL attributes with Attach Content checked

Chapter
CLASSROOM
Optional Step 4 Customizing Message Templates
* Canceled Mail: Informs the recipient that a notification is canceled

* Invalid Mail: Informs the recipient that the response to the notification is invalid
* Closed Mail: Informs the recipient that a previously sent notification is now closed
Summary Mail (HTML): For notification summaries
Warning Mail: Informs the recipient of unsolicited mail that he or she sent
Signature Required Mail: For notifications that require an electronic signature in the users
response; users must respond to such notifications through the Notification Details Web
page rather than by e-mail
Signature Warning Mail: Informs the recipient that an e-mail notification response was not
valid because the notification required an electronic signature to be entered through the
Notification Details Web page
Secure Mail Content: For notifications that include sensitive content that cannot be sent in
e-mail for security reasons; users must view and respond to such notifications through the
Notification Details Web page rather than by e-mail
* Open Mail (More Information Request): For requests for more information about a
notification from one user to another user
More Information Request (Outlook Express): For requests for more information about a
notification from one user to another user, if you use an e-mail application such as
Microsoft Outlook Express as your e-mail client
Invalid Open Mail (More Information Request): Informs the recipient that the response to
a request for more information is invalid
User Notification Preference Update Report: Informs the administrator that an e-mail
notification could not be sent to one or more recipients, that the notification preference for
those recipients has been set to DISABLED, and that those recipients' original notification
preferences, which are listed, should be reset after the issues that caused the failures are
corrected

Chapter
CLASSROOM
Adding Worklist Functions to User Responsibilities

Add the following functions to the responsibilities from which you want users to access the
corresponding pages:
Advanced Worklist: WF_WORKLIST
Personal Worklist: WF_WORKLIST_CUSTOM
Notifications administrator search page: WF_WORKLIST_SEARCH
The Advanced Worklist is seeded on the menu for the Workflow User Web Applications
responsibility by default. You can also add its function to other responsibilities from which you
want users to access notifications.
The Personal Worklist is an optional feature that is not seeded on any Oracle E-Business Suite
menu. If you want users to access this version of the Worklist, you must first add its function to
the menu for a responsibility assigned to those users.
If you add the Personal Worklist, you can use worklist flexfields to define specialized worklist
views that display information specific to particular types of notifications. If you define a
securing function for a view, add the securing function to the same menu as the Personal

Chapter
CLASSROOM
Optional Step 5 Adding Worklist Functions to User

Responsibilities
Worklist function. Your specialized worklist view will appear in the list of views only when
users access the Personal Worklist from that responsibility.
The Notifications administrator search page is seeded on the menu for the Workflow
Administrator Web Applications responsibility by default. You can also add its function to
other responsibilities from which you want users to be able to search for notifications. For
example, if you want users with the Workflow User Web Applications responsibility to have
access to the Notifications administrator search page, you can add this function to the
FND_WFUSER (Workflow User) menu with a prompt such as Notification Search.
A user must have workflow administrator privileges to access other users' notifications on the
Notifications administrator search page. If a user does not have administrator privileges, that
user can only search for and access his or her own notifications.

Chapter
CLASSROOM
Setting the Notification Reassign Mode

The WF: Notification Reassign Mode profile option controls the reassign modes available to
users from the Advanced Worklist, the Personal Worklist, and the Response section of the
Notification Details page.
Delegate: This mode lets users give another user authority to respond to a notification on
their behalf, while still retaining ownership of the notification themselves. For example, a
manager might delegate all vacation scheduling approvals to an assistant.
Transfer: This mode lets users give another user complete ownership of and responsibility
for a notification. For example, users might select this option if they should not have
received a certain notification and they want to send it to the correct recipient or to another
recipient for resolution. A transfer may have the effect of changing the approval hierarchy
for the notification. For example, a manager might transfer a notification about a certain
project to another manager who now owns that project.
Reassign: This setting provides users access to both the Delegate and Transfer reassign
modes. The Reassign setting is the default value for the WF: Notification Reassign Mode
profile option.

Chapter
CLASSROOM
Optional Step 6 Setting the Notification Reassign Mode
Setting Up Notification Handling Options

Adding Item Types for Vacation Rules and Worklist Access
By default, the list of item types a user can select when creating a vacation rule or when
granting worklist access displays those item types for which the user has previously received at
least one notification. You can also choose to add item types that you want to appear in the lists
for all users. In this way you can allow users to create rules or grant worklist access to handle
any notifications they may receive from those item types in the future.
To add an item type to the list, define the internal name of the item type as a lookup code for
the WF: Vacation Rule Item Types lookup type.
Navigate to the Application Object Library Lookups window in the Application Developer
responsibility.
Query the WF_RR_ITEM_TYPES lookup type with the meaning WF: Vacation Rule Item
Types in the Application Object Library application.
Define the item type you want as a new lookup code for this lookup type. Ensure that you
enter the item type internal name in the Code field exactly as the name is defined in your
database.
Allowing Vacation Rules That Apply to All Item Types

Chapter
CLASSROOM
Optional Step 7 Setting Up Notification Handling Options
Use the WF: Vacation Rules - Allow All profile option to determine whether the list of item
types for vacation rules includes the All option. The All option lets users create a generic
rule that applies to notifications associated with any item type.
Enabled: The All option appears in the list of item types for vacation rules. This is the
default value.
Disabled: Users must always specify the item type to which a vacation rule applies.
After changing the value of this profile option, you must stop and restart Oracle HTTP Server
for the change to take effect.

Chapter
CLASSROOM
Setting Up for Electronic Signatures

Implementing Password-based Signatures with Single Sign-On
Oracle Workflow supports password-based signatures for notifications based on Oracle
Application Object Library (FND) passwords. If you maintain your directory service based on
Oracle Application Object Library users and passwords, no additional setup is required.
However, if you implement single sign-on for your site through Oracle Internet Directory, you
must perform the following steps.
Set the Applications SSO Login Types profile option to either Local or Both at user level
for all users who need to enter password-based signatures.
Ensure that these users have valid passwords defined in Oracle Application Object
Library.
For more information, see: Oracle Single Sign-On Integration, Oracle Applications System
Administrator's Guide - Security.
Loading Certificates for Digital Signatures
Before users can sign responses with their X.509 certificates, you must load these certificates
into your Oracle E-Business Suite database using the Workflow Certificate Loader. When you
load a certificate, you must also specify the Oracle Applications user to whom that certificate is

Chapter
CLASSROOM
Optional Step 8 Setting Up for Electronic Signatures

Chapter
CLASSROOM
assigned. Oracle Workflow uses this information to validate that the user attempting to sign
with a certain certificate is the same user to whom that certificate is assigned.
A user can have more than one certificate assigned to him or her. However, each certificate can
only be assigned to one user. Additionally, after you have loaded a certificate for a user, you
cannot delete it from the database or assign it to a different user. If a certificate is incorrectly
assigned, the user to whom it belongs must revoke it and obtain a new certificate instead.
You must load a users personal certificate, the root certificate of the certificate authority that
issued the personal certificate, and any intermediate certificates required for this type of
personal certificate.
Run the loader by running Java against
oracle.apps.fnd.wf.DigitalSignature.loader.CertificateLoader. You can load several certificates
at once by listing the information for all the certificates in a data file for the loader. You can
also load a single certificate by specifying the certificate information in the command line for
the loader.
Note: Oracle Workflow does not provide a framework for certificate provisioning. Oracle
Workflows digital signature support assumes that certificate provisioning is already part of
your infrastructure.
Customizing the Workflow Web Page Logo

Note: /OA_MEDIA/ is a virtual directory mapping defined in your Web server when Oracle
Workflow is installed.

Chapter
CLASSROOM
Optional Step 9 Customizing the Workflow Web Page Logo
Adding Custom Icons

If you create custom icons to include in your Oracle Workflow Builder process definition, and
you want the custom icons to appear in the Status Monitor when you view the process, you
must do the following:
1. Convert the custom icon files (.ico) to GIF format (.gif).
2. Copy the .gif files to the physical directory associated with your Web servers
/OA_MEDIA/ virtual directory, so that the Status Monitor can access them.
Note: /OA_MEDIA/ is a virtual directory mapping defined in your Web server when Oracle
Workflow is installed.

Chapter
CLASSROOM
Optional Step 10 Adding Custom Icons
Version Compatibility

Chapter
CLASSROOM
Review Questions and Solutions

1. What are the required setup steps for Oracle Workflow?
- Set your global workflow preferences.
- Ensure that your directory service is set up.
- Set up background engines.
- Configure the Business Event System for event communication.
2. What are the optional setup steps for Oracle Workflow?
- Partition Workflow tables for performance gain.
- Set up additional languages.
- Set up notification mailers.
- Customize the templates for your e-mail notifications.
- Add Worklist web pages to users responsibilities.
- Set the WF: Notification Reassign Mode profile option.
- Control the item types for which users can define vacation rules and grant worklist
access.

Chapter
CLASSROOM
Review Questions
- Set up users to enable electronic signatures in notification responses.

- Customize the company logo that appears in Oracle Workflow Web pages.
- Include custom icons in your Oracle Workflow icons subdirectory.

Chapter
CLASSROOM
Summary

Chapter
CLASSROOM
Chapter 18
Overview of Flexfields
Chapter
CLASSROOM

Chapter
CLASSROOM
Chapter
CLASSROOM
Lesson Topics
This lesson describes how to use modifiable fields called flexfields to tailor Oracle
Applications to reflect your business needs and practices.
You can use flexfields to define the structure of certain data identifiers required by Oracle
Applications. You can also gather, store and process additional data that may be required by
your business.
After completing this lesson, you should be able to:
Explain flexfields and how they are used by Oracle Applications
Distinguish between key and descriptive flexfields
Identify key and descriptive flexfields used by Oracle Applications
List the benefits provided by flexfields
Chapter
CLASSROOM
Objectives
Lesson Overview
This lesson describes how Oracle Applications uses customizable fields called flexfields to
modify and expand processing. Specifically it covers:
How flexfields operate
The two types of flexfields
Flexfield terminology
Flexfield benefits
Chapter
CLASSROOM
Overview
Using Flexfields to Customize Applications

A flexfield is a customizable field that opens in a window from a regular Oracle Applications
window. Defining flexfields enables you to tailor Oracle Applications to your own business
environment. You can easily define flexfields to modify or extend Oracle Applications without
programming. By using flexfields within Oracle Applications, you can:
Structure certain identifiers required by Oracle Applications according to your own
business environment
Collect and display additional information for your business as needed
Flexfields are important because they are used throughout Oracle Applications. Flexfields
provide many opportunities for easy modification and customization of standard Oracle
Applications processing. Members of the system implementation team as well as system
administration personnel should be familiar with the concepts and procedures of flexfields to
design and support an Oracle Applications environment that meets the needs of all its users.
Chapter
CLASSROOM
Customizing Oracle Applications
Flexfield Components
A flexfield is composed of segments. The segments of a flexfield contain the flexfield values.
Flexfield segments are combined in a grouping called a structure. The segments that make up a
particular structure are logically or functionally related. A single flexfield can have more than
one structure.
When you implement a flexfield, you decide how many segments you need for a particular
structure and whether you need multiple structures. Being able to define different structures for
the same flexfield allows you to tailor the same flexfield to the needs of different end users.
The example on the slide shows three segments:
Category
Item
Color
These three segments together form a structure.
Chapter
CLASSROOM
Flexfield Structures and Flexfield Segments
Customizing the Flexfield Appearance

In addition to defining the segments and structures that make up the flexfield, you can define
the appearance of the flexfield. You can specify names and descriptions for the segments
appearing on the window, as well as specify the display size for each field.
Chapter
CLASSROOM
Segment Prompts and Value Descriptions
Using Value Sets with Flexfields

Value sets allow you to control the values for a segment or a report parameter. A value set is a
definition of the values approved for entry or display by a particular flexfield segment. A value
set may also contain a list of actual approved values although this is not required. You may be
able to define the appropriate values after you define the value set.
Value Sets Limit Acceptable Types of Values
Some value sets permit a limited range of values; others permit only certain values; others
have minimal restrictions.
Different flexfields can share the same value set. For example, a value set containing the
names of regional offices could be used by many different flexfields.
Different segments of the same flexfield can use the same value set, for example a date
value set. Segments defined to different structures of the same flexfield can share value
set. Many of the report parameters used with SRS forms are tied to shared value sets.
Value sets do not have to have the actual values defined.
Chapter
CLASSROOM
Validating Input Using Value Sets
Different Types of Flexfields

There are two types of flexfields, key and descriptive flexfields. Each type is discussed in more
detail on the following slides. The main differences are:
You use key flexfields to define your own structure for many of the identifiers required by
Oracle Applications.
You use descriptive flexfields to gather additional information about your business entities
beyond the information required by Oracle Applications.
Chapter
CLASSROOM
Key and Descriptive Flexfields
Key Flexfields
In Oracle Applications you use key flexfields as identifiers for entities. Generally, the identifier
you create using a key flexfield is required by the application (for example, the Accounting
Flexfield builds the account number used by Oracle General Ledger).
A key flexfield appears as a normal field on a form. Any existing value for the key appears in
the field as a concatenated value having segment separators.
You can use the Flexfields: Open Key Window profile option to specify whether you want the
key flexfield window to be opened automatically when you navigate to the key flexfield on the
base form. This profile option is visible and updatable at the user level.
A key flexfield structure usually consists of multiple segments, each of which contains
meaningful information. The resulting combinations of values from these segments therefore
function as intelligent keys.
Chapter
CLASSROOM
Key Flexfields
Using Key Flexfields to Build Intelligent Keys

Intelligent keys are multipart codes where the value in each individual part contains
meaningful information. Each combination of values can therefore identify a particular
business entity or class of entities. Such intelligent key structures are used throughout Oracle
Applications. Because you define your key flexfield structure yourself, it reflects the
organization of your business.
Accounting Flexfield Example
One important key flexfield is the Accounting Flexfield. The example on the slide shows how
two hypothetical businesses could define Accounting Flexfield structures that reflected their
different accounting structures. Business As accounting structure has five segments, while
business Bs accounting structure has four segments.
Additional Key Flexfield Features
You can define value sets to control the allowable values for each segment of the key. You can
also define cross-validation rules to control the allowable combinations of segment values
within the key.
Chapter
CLASSROOM
Intelligent Keys
Intelligent Key Examples

There are many areas in business where you can use intelligent keys. Some examples are
displayed above. Many such intelligent keys are used in Oracle Applications to represent such
entities.
Chapter
CLASSROOM
Intelligent Keys
The Accounting Flexfield

The Accounting Flexfield is used to create and display account numbers. The Accounting
Flexfield is owned by Oracle General Ledger, but Accounting Flexfield values are used by
many of the applications. For example, an Accounting Flexfield structure can consist of five
segments:
Company
Department
Account
Sub-Account
Product
Chapter
CLASSROOM
Key Flexfield Example: Accounting Flexfield
Key Flexfields Within Oracle Applications

Many Oracle applications have key flexfields. The slide displays some of the applications and
their associated key flexfields. In many cases, you must implement the key flexfield to
implement the application. Many key flexfields are used by multiple applications. For example,
the Accounting Flexfield is used by both Oracle General Ledger and Oracle Payables.
Chapter
CLASSROOM
Oracle Applications Key Flexfields
Descriptive Flexfields
You use descriptive flexfields to collect information beyond what is collected by Oracle
Applications. Using descriptive flexfields allows you to gather additional specialized
information required by your business. The use of descriptive flexfields is optional.
A descriptive flexfield appears on a form as a double-character field enclosed by brackets. You
can use the Flexfields: Open Descr Window profile option to specify whether you want the
descriptive flexfield window to be opened automatically when you navigate to the bracketed
field, if the flexfield is enabled. This profile option is visible and updatable at the user level.
A descriptive flexfield typically uses multiple structures. You can:
Define a basic structure that gathers additional information for all entities.
Define several different structures that gather specialized information for different types of
the same general entity.
Define a combination of the preceding two. This structure can gather general information
about all entities and then optionally gather certain information about certain types of
entities.
The example shows a descriptive flexfield that gathers different payment information based on
the type of payment: check (CK) or credit card (CC).
Chapter
CLASSROOM
Descriptive Flexfields
Using Context and Reference Fields to Control Descriptive Flexfields

The same descriptive flexfield often uses multiple structures. Each of these structures can have
different segments and gather different data. When you define multiple structures for a
descriptive flexfield, you can make the choice of structure either dependent on the value of
another field or selectable by the user:
If the value in a preceding field elsewhere on the form determines which structure is used,
the preceding field is known as a reference field. However, if the descriptive flexfield is
used in another form, then the two forms must have the same name for the reference field.
If the value in a field within the flexfield itself determines which structure is used, that
field is called a context field.
The example on the slide shows a hypothetical window containing sales information. One of
the fields on this window, Payment Type, is used as a reference field for a descriptive flexfield
that contains information about how the customer will pay.
In this example, the buyer is using a credit card so the credit card information is gathered by
using the descriptive flexfield structure shown on the right. If payment is by check, you could
gather check-related information by using the descriptive flexfield structure shown on the left.
Chapter
CLASSROOM
Using Reference Fields
The Asset Category Flexfield

The example on the slide shows the Asset Category descriptive flexfield. The descriptive
flexfield is gathering further information about an office building asset. You can see this both
by the value in the reference field, and by the type of information being requested on the
flexfield.
Note: In this example, the reference field is itself a key flexfield.
Chapter
CLASSROOM
Using Different Contexts: Asset Category Flexfield
Partial List of Oracle Applications Descriptive Flexfields

Numerous descriptive flexfields are available throughout Oracle Applications. The slide shows
only a partial list. In contrast to key flexfields, descriptive flexfields are not shared between
applications.
Chapter
CLASSROOM
Oracle Applications Descriptive Flexfields (Partial)
Using Flexfields as Parameters Within Standard Request Submission

Reports and concurrent programs submitted with Standard Request Submission often have
parameter windows that pop up. These parameter windows behave similarly to descriptive
flexfields.
Parameter Windows Are Context Sensitive
The window that appears and the segments contained in it depend on which request is
being run.
The request name acts as a reference field.
Many request parameters have associated value sets to control the allowable values for
that parameter. Such value sets are often shared by many other flexfields. You should
always be careful when modifying any value sets used by SRS processing.
Chapter
CLASSROOM
Standard Request Submission (SRS) and Flexfields
Benefits of Flexfields
You should now have a basic understanding of how flexfields are used by Oracle Applications.
The ease of configuring flexfields provides many benefits to users. The main benefits are listed
on the slide.
Chapter
CLASSROOM
Benefits of Flexfields
Storing Flexfield Values in Database Tables

The values entered through an applications flexfields are stored internally in that applications
database tables:
Each segments value is stored in a column in one of the base tables.
The column name reflects the type of flexfield data it holds. In general, key flexfields
store their data in columns called SEGMENTn, where n is a number. In general,
descriptive flexfields store their data in columns called ATTRIBUTEn, where n is a
number.
The number of SEGMENT and ATTRIBUTE columns available for use by a flexfield
varies between flexfields. Not all flexfields have the same number of fields defined. When
implementing a flexfield, determining the number of fields available for use is an
important planning step.
Chapter
CLASSROOM
Storing Flexfield Data Internally
Implementing a Flexfield: General Procedure

Use the following steps when defining flexfields, both key and descriptive:
Plan your flexfield structure and layout. Remember that many flexfields use more than
one structure, and that each structure can consist of different segments. Also plan any
value sets and their values.
Define flexfield value sets. Value sets limit the allowable values for the flexfield segment.
If you create your value sets first, you can refer to them while your are defining your
flexfield segments in the following step.
Define flexfield segments and structures. Use the plan you designed earlier.
Define values for your value sets.
For key flexfields, define security and cross-validation rules as necessary.
Test your flexfield.
Chapter
CLASSROOM
Implementing a Flexfield Steps
Summary
Flexfields are Oracle Applications fields that you can configure. You can define the content
and layout of the flexfield to reflect your own business needs.
There are two types of flexfields:
Key flexfields are used to create entity identifiers required by Oracle Applications. You
can use key flexfields to structure these identifiers according to your business
environment. The definition of many key flexfields is required by the application.
You use descriptive flexfields to gather additional information for storage or processing.
You can define descriptive flexfields in multiple ways to accommodate the needs of many
different groups of users. The use of descriptive flexfields is optional.
Chapter
CLASSROOM
Summary
Chapter 19
Using Value Sets

Chapter
CLASSROOM
Using Value Sets

Using Value Sets

Chapter
CLASSROOM
Using Value Sets
Using Value Sets

Chapter
CLASSROOM
Lesson Topics
This lesson describes planning and using value sets to control input with flexfields. At the end
of this lesson, you should be able to:
List options for validating flexfield segment values and report parameters
Choose the appropriate validation option to use with a particular segment
Identify issues for consideration when planning a validation strategy
Define new value sets
Define allowable values for a value set
Using Value Sets

Chapter
CLASSROOM
Objectives
Lesson Overview
Value sets are definitions of allowable values for use with a flexfield segment or report
parameter. This lesson covers the different types of value sets and how each is used. It also
describes how to plan the value set as well as the actual values for those sets that require a list
of values. Finally, it covers the definition process itself.
Using Value Sets

Chapter
CLASSROOM
Overview
Value Sets Define Allowable Values

You can create a value set and assign it to a flexfield segment or report parameter to control the
valid values for the segment.
Value Sets Check User Input
Define a value set for each flexfield segment. A value set is a general definition of the values
acceptable for a particular flexfield segment or report parameter. A value set can also have a
list of actual values available to the segment, although this is not required.
Other Advantages of Value Sets
Value sets control which segments can use special features such as Longlist, value security,
and segment value combination checking.
The example in the slide shows two value sets:
The Category value set specifies the allowable values for the Category segment.
The Item value set specifies the allowable entries for the Item segment.
Using Value Sets

Chapter
CLASSROOM
Validating Input Using Value Sets
Planning Your Value Set

There are several steps to planning your value set:
1. Determine the basic attributes for the set. Choose what conditions all values must fit to be
considered valid values. Such criteria include data type (Character, Numeric), value
length, and minimum and maximum values, if appropriate.
2. Select the appropriate validation strategy. Choose the type of validation most appropriate
for the data. Validation types are discussed in the following pages.
3. Identify approved values, if appropriate. For some value sets, you know ahead of time the
acceptable values. In these cases, in addition to defining the value set, you can also specify
the values that appear when the user enters the flexfield segment. The segment accepts
only values explicitly defined for that value set.
For some value sets, it does not make sense to try to provide a complete list of all the approved
values. For example, a segment containing customer telephone numbers probably does not
need a list of values, because each new customer will have a new telephone number which you
do not know at design time.
Using Value Sets

Chapter
CLASSROOM
Planning a Value Set
Types of Value Sets

You can define several types of value sets depending on how you need your values to be
checked. All value sets perform minimal checking; some value sets also check against the
actual values, if you have provided any.
None - A value set of the type None has no list of approved values associated with it. A None
value set performs only minimal checking of, for example, data type and length.
Independent - Independent type value sets perform basic checking but also check a value
entered against the list of approved values you define.
Dependent - A Dependent value set is associated with an Independent value set. Dependent
value sets ensure that all dependent values are associated with a value in the related
Independent value set.
Table - Table value sets obtain their lists of approved values from existing application tables.
When defining your table value set, you specify a SQL query to retrieve all the approved
values from the table.
Special - This specialized value set provides another flexfield as a value set for a single
segment.
Using Value Sets

Chapter
CLASSROOM
Types of Value Sets
Types of Value Sets (continued)

Pair - This specialized value set provides a range flexfield as a value set for a pair of segments.
Translatable Independent - A Translatable Independent value set is similar to an Independent
value set in that it provides a predefined list of values for a segment. However, a Translatable
Independent value set can contain display values that are translated into different languages.
Translatable Dependent - A Translatable Dependent value set is similar to a Dependent value
set in that the available values in the list and the meaning of a given value depend on which
independent value was selected in a prior segment of the flexfield structure. However, a
Translatable Dependent value set can contain display values that are translated into different
languages.
Using Value Sets

Chapter
CLASSROOM
Types of Value Sets
Validation Type None

A validation of type None performs only minimal checking of the data input through this
flexfield segment. Use the validation type None when the actual values to be input cannot be
anticipated in advance but the data entered must conform to a particular data type, length, or
any other formatting criteria. Examples of such values include credit card numbers, street
addresses, and phone numbers.
Using Value Sets

Chapter
CLASSROOM
Validation Type None
Validation Type Independent

Use the validation type Independent when you know the allowable values ahead of time. With
an Independent validation type, you typically also define a list of the actual values approved
for use. The user selects these values from a pop-up list.
In the example in the slide, the Category value set contains only three allowable values for the
Category segment of a hypothetical Item Information flexfield. The category segment value
must indicate a computer item, an appliance item, or an item of furniture.
Using Value Sets

Chapter
CLASSROOM
Independent Value Sets
Validation Type Dependent

A Dependent value set is also associated with a list of approved values. In this case however,
the values on the list can be grouped into subsets of values. Each subset of values is then
associated with a value from an Independent value set. Once a value from the Independent
value set has been specified, the list of values for the Dependent value set displays only the
values that are approved for the value selected from the Independent value set.
In the example in the slide, once a value from the Category value set has been specified, only
the appropriate values from the Item value set are displayed.
The segment or parameter using the dependent value set must appear after the segment or
parameter using the independent value set.
Using Value Sets

Chapter
CLASSROOM
Dependent Value Sets
Validation Type Table

If an application table already contains all the allowable values, you can define a tablevalidated value set to retrieve values from the table. You can specify selection criteria in the
form of an SQL WHERE clause if you need to restrict the values.
Table-validated value sets are useful when the set of approved values is large, changes
frequently, and is maintained by the application.
Using Value Sets

Chapter
CLASSROOM
Table-Validated Value Sets
Specialized Validation Types

Two additional validation types are used for more specialized validation needs:
Special value sets can accept an entire key flexfield as a segment value in a descriptive
flexfield or report parameter.
Pair value sets are a specialized form of Special value sets.
Using Value Sets

Chapter
CLASSROOM
Specialized Validation Types
Validation Type Translatable Independent

Translatable Independent value sets are similar to Independent value sets except that translated
values can be displayed to the user. Translatable Independent value sets enable you to use
hidden values and displayed (translated) values in your value sets. In this way your users can
see a value in their preferred languages, yet the values will be validated against a hidden value
that is not translated.
A Translatable Independent value set can have only Translatable Dependent value sets
dependent on it.
Using Value Sets

Chapter
CLASSROOM
Translatable Independent Value Sets
Validation Type Translatable Dependent

Translatable Dependent value sets are similar to Dependent value sets except that translated
values can be displayed to the user. Translatable Dependent value sets enable you to use
hidden values and displayed (translated) values in your value sets. In this way your users can
see a value in their preferred languages, yet the values will be validated against a hidden value
that is not translated.
Translatable Dependent value sets must be dependent on a Translatable Independent value set.
Using Value Sets

Chapter
CLASSROOM
Translatable Dependent Value Sets
Summary of Validation Types

The chart in the slide displays a comparison of the various validation types. It also shows
where the lists of acceptable values are stored.
Using Value Sets

Chapter
CLASSROOM
Validation Types: Summary
Planning Your Value Set

There are three major areas you should consider when planning your value sets.
Planning the value set attributes, including the value set name, description, and other
attributes
Planning the format validation to determine how all input must be formatted to be
accepted
Planning the value validation, including specifying the validation type and any additional
validation information, if required by the validation type
Using Value Sets

Chapter
CLASSROOM
Planning Value Sets
Value Set Level Attributes

Value Set Name - If an Oracle applications predefined value set has the same name as a userdefined value set within the same application, the user-defined value set is overridden during
an upgrade. Therefore, follow these naming guidelines:
Do not use the patterns of either two or three characters followed immediately by a
hyphen or an underscore. These patterns are reserved by Oracle Applications.
Do not use spaces in your value set name.
Include a custom or site prefix in the value set name to make it unique.
Oracle always provides a list of reserved value set names before an upgrade. Be sure to check
this list against your existing value sets.
Description - You can give your value sets descriptive text information.
Security - You can define security rules that further control the values available from this
value set.
Longlist Option - You can enable the user to interrupt the display of very long lists of values.
Using Value Sets

Chapter
CLASSROOM
Value Set Attributes
Planning Data Format Validation

Format Type - Select the available data types from the list of values.
Maximum Size - Specify the maximum size of the value. The maximum size must be less than
or equal to the size of the underlying column in the base application.
Precision - For numeric data, specify the number of decimal places.
Numbers Only - Select Numbers Only to accept only digits.
Uppercase Only - Select Uppercase Only to force any lowercase input to uppercase.
Right-Justify and Zero-Fill - Select these options to shift number to the right and then pad
from the left with zeros. This is an alternate format for alphanumeric numbers.
Maximum/Minimum Value - To define a range of values for this value set, specify a
beginning value and an ending value.
Using Value Sets

Chapter
CLASSROOM
Planning Format Validation
Formatting Types
You can require one of several types of data formatting. When you declare a value set a
particular format type, all data entered in the segment that uses this value set must match the
requirements of the format.
For some format types, there are additional options.
The various format types and options are discussed on the following pages.
Using Value Sets

Chapter
CLASSROOM
Format Types and Options
Char and Number Formatting Rules and Their Results

You have several choices about the type of data you can allow in a value set and the editing
done to that data. Two of the choices are shown in the slide.
Char Format - Plain character format type accepts uppercase, lowercase, and special
characters.
Numbers Only - This format type allows only the digits 09 to be input into a field. You will
receive an error message if you attempt to enter anything else.
Uppercase Only - This format type converts any lowercase letters entered to uppercase.
Right-Justify and Zero-Fill Numbers - Alphanumeric data is ordinarily left-justified. This
option enables you to right-justify numeric values and pad with zeros. Any number entered is
converted to the full width of the field size.
Precision - For data, this numeric format type enables you to specify the number of decimal
positions available. If the data entered has more decimals than there are precision positions, the
data will be rounded.
Using Value Sets

Chapter
CLASSROOM
Char and Number Format Editing
Date and Time Format Results

The Max Size attribute controls the display of the output for the Time format as shown in the
slide. The Standard Date and Standard DateTime formats enforce the users preferred format.
There are two additional format types: Date and DateTime. However, these exist for backward
compatibility only. Any new value sets you create should use Standard Date and Standard
DateTime.
Using Value Sets

Chapter
CLASSROOM
Time, Standard Date, and Standard DateTime Format Editing
Considering the Interaction of Formatting

When planning your value set, consider the interaction between the value set and the segment
that will eventually use it. Optionally, try to keep identical the maximum size defined for the
value set and the display size defined for the flexfield segment. Otherwise, the user may have
to scroll to see the full value. This is especially important with values formatted with RightJustify and Zero-Fill.
Using Value Sets

Chapter
CLASSROOM
Format Interaction
Formatting Requirements for Translatable Value Sets
Using Value Sets

Chapter
CLASSROOM
Planning How to Validate Your Values

Which type of validation you use depends on the variability of the data and how the list of
acceptable values is processed.
Using Value Sets

Chapter
CLASSROOM
Planning Validation Strategy
Planning Validation Strategy
Using Value Sets

Chapter
CLASSROOM
Planning Your Values When Planning Value Sets

For validation types that provide lists of values, plan the values they will process when you are
planning the value set itself:
Consider how the actual values should be formatted. For example, if the values are 01, 02,
instead of 1,2, define the value set with Right-Justify Zero-Fill set to Yes.
Consider the segment size and the display sizes you define.
When using existing value sets, disable values that have become obsolete (values cannot
be deleted), or change the description and reuse the value if possible.
Using Range Features
Group related values in ranges to simplify implementing range-based features such as
cross-validation and security rules.
Allow for future expansion by using large values. For example, use three digits instead of
two for a segment.
Using Value Sets

Chapter
CLASSROOM
Planning Value Sets and Their Values
Planning Values for Dependent Value Sets

Because the values for a dependent value set interact with the values from an independent
value set, use the procedure outlined on the slide when planning your dependent value set.
Notice that you must define a default value for each group of dependent values.
Translatable dependent value sets behave like dependent value sets except that they must be
dependent on a translatable independent value set. A translatable independent value set can
have only translatable dependent value sets dependent on it.
Using Value Sets

Chapter
CLASSROOM
Planning Dependent Value Sets
Defining Your Value Sets

The procedure for defining value sets is shown in the slide. You should always check the
existing value sets to see if there is an existing value set that you can use.
Using Value Sets

Chapter
CLASSROOM
Defining Value Sets
Predefined Value Sets
Using Value Sets

Chapter
CLASSROOM
Using Existing Value Sets
Using Value Sets

Chapter
CLASSROOM
Value Set Usage by Key Flexfields

col 'value set' for a40
col flexfield for a40
col structure for a30
col column for a32
select
from
where
d.flex_value_set_name "Value Set",

a.id_flex_name "Flexfield",
e.id_flex_structure_name "Structure",
c.segment_name "Segment"
fnd_id_flexs a,
fnd_id_flex_structures b,
fnd_id_flex_segments c,
fnd_flex_value_sets d,
fnd_id_flex_structures_tl e
a.application_id = b.application_id
and a.id_flex_code = b.id_flex_code
Using Value Sets

Chapter
CLASSROOM
Value Set Usage by Key Flexfields
order by
and b.application_id = c.application_id

and b.id_flex_code = c.id_flex_code
and b.id_flex_num = c.id_flex_num
and c.flex_value_set_id = d.flex_value_set_id
and c.application_id = e.application_id
and c.id_flex_code = e.id_flex_code
d.flex_value_set_name, a.id_flex_name,
e.id_flex_structure_name;
Using Value Sets

Chapter
CLASSROOM
Value Set Usage by Descriptive Flexfields

select
flex_value_set_name "Value Set",
descriptive_flexfield_name "Flexfield",
descriptive_flex_context_code "Structure",
end_user_column_name "Column"
from
fnd_descr_flex_column_usages a,
fnd_flex_value_sets b
where
a.flex_value_set_id = b.flex_value_set_id
and descriptive_flexfield_name not like '$SRS$%'
order by
flex_value_set_name,
descriptive_flexfield_name,
descriptive_flex_context_code;
Using Value Sets

Chapter
CLASSROOM
Value Set Usage by Descriptive Flexfields
Defining a New Value Set
Using Value Sets

Chapter
CLASSROOM
Defining a Dependent or Translatable Dependent Value Set
Using Value Sets

Chapter
CLASSROOM
Selecting a Value Set for Value Definition
Using Value Sets

Chapter
CLASSROOM
Defining Values for a Dependent or Translatable Dependent

Value Set
Using Value Sets

Chapter
CLASSROOM
Defining Values for a Value Set
Using Value Sets

Chapter
CLASSROOM
Modifying Value Definitions
Using Value Sets

Chapter
CLASSROOM
Value Hierarchies
Using Value Sets

Chapter
CLASSROOM
Value Hierarchies
Using Value Sets

Chapter
CLASSROOM
Defining Value Hierarchies and Qualifiers

Parent - Select this check box for parent values. Clear this check box for values that are not
parents of any other value.
Group - For parent values, select the rollup group to which you want to assign the value.
Level - Enter a description of this values relative level in your hierarchy structure. This level
description is for your purposes only.
Qualifiers - Navigate to the Qualifiers field to display the Segment Qualifiers window and
assign segment qualifiers to your values as appropriate. Examples of segment qualifiers for the
Accounting Flexfield include:
Allow Budgeting
Allow Posting
Account Type
Using Value Sets

Chapter
CLASSROOM
Defining Value Hierarchies and Qualifiers
Using Value Sets: Summary

Use value sets to control the data entered and displayed through flexfield segments. A value set
is a definition of allowable values. There are several types of value sets. Each type differs in
the amount and type of validation processing it performs. Some types of value sets present the
user with a list of actual values from which to choose. You can define this list yourself or
retrieve it from an application table.
Using Value Sets

Chapter
CLASSROOM
Summary

Using Value Sets

Chapter
CLASSROOM
Chapter 20
Defining Descriptive Flexfields

Chapter
CLASSROOM
Defining Descriptive
Flexfields


Chapter
CLASSROOM

Chapter
CLASSROOM
Lesson Topics
This lesson describes the process required to plan a descriptive flexfield.
At the end of this lesson, you should be able to:
Identify the descriptive flexfield to be used and the information to be gathered
Organize the information according to usage
Plan the layout of the descriptive flexfield
Plan the behavior of the descriptive flexfield
Define the descriptive flexfield structure
Define global segments
Define context-sensitive segments as appropriate

Chapter
CLASSROOM
Objectives
Lesson Overview
Descriptive flexfields allow the user to gather additional information beyond that gathered by
Oracle Applications. The information gathered by a descriptive flexfield and the structure of
that information can vary between different users. This lesson covers analyzing and organizing
the additional data, designing the different flexfields layouts, and specifying how the
descriptive flexfield will behave.
This lesson also covers the mechanics of defining a descriptive flexfield. Flexfields consisting
of only global segments as well as both global and context-sensitive segments are covered.

Chapter
CLASSROOM
Overview
Implementing a Descriptive Flexfield

Descriptive flexfields provide an easy and powerful way to extend the processing of Oracle
Applications. However, since descriptive flexfield structures can be organized in many ways,
you should spend some time in planning the new flexfield to ensure a successful result. Follow
these steps to implement your descriptive flexfield:
1. Identify the flexfield to implement. Descriptive flexfields do not exist in a vacuum. They
are logically related to the form on which they appear. Once you decide to implement the
descriptive flexfield on a form, you must identify which descriptive flexfield it is.
2. Determine the system resources available to you. The number of segments available for
use on your flexfield depends on the number of underlying columns in the base table.
Since this will control the number of segments you have available for use, you must find
this information before you can plan your design.
3. Identify the items of information you wish to gather. The information you gather should
be logically related to the other information on the form.
4. Design the flexfield layout. Determine the number of segments and how they will be
combined into structures.

Chapter
CLASSROOM
Planning a Descriptive Flexfield
5. Design the flexfield behavior. If you have multiple structures, determine how to process
the different contexts.
6. Define the actual flexfield. Use the descriptive flexfield definition windows to enter your
definition. Freeze and compile the definition to make the flexfield available to other users.

Chapter
CLASSROOM
Using Descriptive Flexfields

Descriptive flexfields have many uses in Oracle Applications:
Flexfields expand Oracle Applications processing without programming.
- Descriptive flexfields provide user-customizable expansion space in forms by
enabling built-in blank fields to store extra data.
- Each installation of Oracle Applications may use descriptive flexfields differently.
You can use different structures for different contexts.
- Use different segments depending on other information in the form or the descriptive
flexfield.
- Allow only the appropriate context-sensitive segments to appear.
Flexfields save space.
- Non-essential information resides in a descriptive flexfield that pops up only when
the information becomes necessary.
- If no extra fields are needed, the descriptive flexfield occupies little additional space
on the form.

Chapter
CLASSROOM
Using Descriptive Flexfields
Typical Information Collected by Descriptive Flexfields

The slide shows typical business areas in which you may need to track additional or specialized
information. You can easily define a descriptive flexfield to gather and store as much extra
data as is required for your business needs.

Chapter
CLASSROOM
Typical Descriptive Flexfield Information
Oracle Applications Descriptive Flexfields (Partial)

There are many descriptive flexfields available for use within Oracle Applications. The slide
shows only some of the flexfields available.

Chapter
CLASSROOM
Some Oracle Applications Descriptive Flexfields
Identifying a Descriptive Flexfield

Chapter
CLASSROOM
Determining the Descriptive Flexfield Name

Chapter
CLASSROOM
Determining the Descriptive Flexfield Name

Chapter
CLASSROOM
Determining the Available Resources

Once you have identified the descriptive flexfield you want to implement, you need to
determine how many segments you can plan for. To do this, you need to know the number of
ATTRIBUTE columns in the underlying table.
Find the flexfield definition and navigate to the Segments Summary window for that flexfield.
Use the list of values on the Column field to display a list of the attribute columns. You will
use this list of values again later to assign a segment to an underlying column, but you can also
use it for planning now. The columns are numbered sequentially, so the highest numbered
column tells you how many segments you can use.

Chapter
CLASSROOM
Determining Available Resources
Identifying Your Information Needs

Once you know what resources you have available, you can begin to plan the layout of the
flexfield.
First determine your information needs. Some of the questions to ask are shown on the slide.
Before you can start designing the flexfield structure, you should know what information needs
to be gathered by this flexfield, and how the information will be used.

Chapter
CLASSROOM
Planning Questions
Identifying Needed Information

Assume you are planning a descriptive flexfield that will gather additional sales payment
information. Some of the possible items of data in which you might be interested appear on the
slide.

Chapter
CLASSROOM
Identifying Your Information
Organizing Information by Usage

After you have identified all the items of information you want to gather, organize them by
usage. Are all the items used all the time? Are all the items used in the same way?
The slide shows three different payment situations and the items of information appropriate for
each situation.

Chapter
CLASSROOM
Grouping Information By Usage
Isolate Common Information

After you have organized the items of information by usage, isolate any items that occur in all
situations. You define the information used by all tasks in one structure and the information
that varies by task in another, task-specific structure.

Chapter
CLASSROOM
Isolate Common Information
Determine Your Contexts

After you have removed the commonly occurring information, you can organize the remaining
information into groups according to the type of information being gathered or the way the
information is being used. These different groups of information are called contexts.
Once you have determined the items of information that are always appropriate and the
different contexts with each of their pieces of information, you are ready to begin defining your
flexfield.

Chapter
CLASSROOM
Determine Different Contexts
Descriptive Flexfield Components

Descriptive flexfields are constructed from segments. Each segment contains one item of
information. Since the same flexfield can be used by different contexts, and each context needs
different items of information, you need to design different layouts for the same flexfield to
support the different contexts.
Specify your layout in terms of global segments and context-sensitive segments.

Chapter
CLASSROOM
Descriptive Flexfield Components
Using Global Segments

Global segments are segments that appear regardless of context. Always plan your global
segments first. Some descriptive flexfields use only global segments.
Continuing the payment information example, the slide shows that the store number is
appropriate for all contexts. Thus it is an obvious global segment.
Global segments are the easiest to define. However, they may use up the allotted columns.
Columns used for global segments cannot hold an context-sensitive segments.
You can add context-sensitive segments later if columns are available, but enabled global
segments always appear.

Chapter
CLASSROOM
Global Segments
Context-Sensitive Segments
Context sensitive segments occur depending on the context.
The slide shows sample contexts and the segments that are unique to each of them.

Chapter
CLASSROOM
Context-Sensitive Segments
Distinguishing Between Contexts

If your descriptive flexfield uses different contexts, you must decide how to distinguish
between them. You must identify a field whose value can distinguish between contexts. This
field is called the context field.
In some cases, you can use an existing field as the context field, in other cases, you must create
a segment on the descriptive flexfield.

Chapter
CLASSROOM
Distinguishing Between Contexts
Using Reference and Context Fields

There are two design options for distinguishing between contexts:
If there is an existing field on the base window or an existing profile option whose value
can be used to distinguish between contexts, it can be used as a reference field.
If there is no existing field or profile option that can be used to automatically select the
context, you may choose to allow users to manually select the context.

Chapter
CLASSROOM
Reference and Context Fields

Reference fields are fields on the existing window whose values can determine which context a
descriptive flexfield uses under the following conditions:
The field must be defined to be referenceable. Not all fields on a window can be used as a
reference field.
The values appearing in the reference field should be known and predictable.
Since the same descriptive flexfield can appear on different windows, any field used as a
reference field for that descriptive flexfield must appear on the same windows. Also, the
reference field must have the same internal name in all the forms where the flexfield is
used.

Chapter
CLASSROOM
Identifying Referenceable Columns

Chapter
CLASSROOM
Using a Context Field

Sometimes there is no field on the existing window that is appropriate for use as a reference
field. In this case, you need to create a column on the descriptive flexfield itself to hold and
display the different possible context values.
A context field is an additional field appearing on the descriptive flexfield.
The user can display the appropriate context by selecting a value from the pop-up list for
the context field.
A context field is not a segment.
The context field has a context field prompt.
The response, called a context field value, determines which group of context-sensitive
segments appears next.
Each value for the context field can correspond to a separate context-sensitive structure.
Context fields do not always display. Non-displayed context fields derive values from a
default or from a reference field, and the user cannot change the context field value.

Chapter
CLASSROOM
Using Context Fields
Synchronizing the Context Field Value with the Reference Field Value
You can optionally set up your flexfield so that the context field value is synchronized with the
reference field value. You may have instances where, when querying existing records, you
want the context field value to match the original reference field value, but with new records,
you want the context field value to be derived from the current reference field value.
For example, say the context field is Country Code (IN for India, AU for Australia, and so on).
This information should be constant for the lifetime of a given record, such as an Expense
Report; that is, it remains constant from the original data entry (and saving of the record) to
subsequent queries on the record.
In this example, the Country Code value could be captured as a profile option value specific to
the user (the reference field). The desired behavior of which Country Code value is used by the
descriptive flexfield may depend on the action at runtime. For example, say an expense report
is created by an employee in India, with a Country Code of IN. If payment processing is done
in Australia and the Australian (Country Code: AU) Payables Approver queries the Indian
employee's expense report, the expected default Country Code context field value is IN; it is
not derived from the Australian Payables Approver's profile option value of AU. However, if

Chapter
CLASSROOM
Synchronizing the Context Field Value with the Reference Field

Value

Chapter
CLASSROOM
the Australian Payables Approver enters in his/her own expense report, then the expected
default Country Code context field value is AU.
The context field value defaulting behavior is configurable for each descriptive flexfield. How
you configure each descriptive flexfield determines whether the old context field value is
retained or whether the new context information is accepted.
Here are the possible configurations:
Context Field Synchronized and Displayed -The context value is always derived from the
reference field value. Users can see but not update the context field value, because they
should not be allowed to break the synchronization.
Context Field Synchronized but Not Displayed - The context value is always derived from
the reference field value. The context field is hidden from the user.
Context Field Not Synchronized and Not Displayed The context field value is derived
from the reference field value the first time the descriptive flexfield value is touched.
Thereafter it is never synchronized with a new reference field value. Because the context
field is not displayed, users will not be able to update its value.
Context Field Not Synchronized but is Displayed The context field value is derived from
the reference field value the first time the descriptive flexfield value is touched. Thereafter
the context field value is not automatically synchronized with a new reference field value,
but users are allowed to update its value.
Using Global Segments Only

Some descriptive flexfields use global segments only. The information gathered by that
flexfield is valid for all users of the flexfield. All global segments display when the user enters
the flexfield, and each segment prompts the user for one item of information.

Chapter
CLASSROOM
Planning Flexfields: Global Segments Only
Using Context-Sensitive Segments Only

Some descriptive flexfields use only context-sensitive segments. They have no global
segments. The flexfield contains only the context field prompt until a context is chosen. The
context field value that is chosen determines which context is displayed in a second window.

Chapter
CLASSROOM
Planning Flexfields: Context Segments Only
Using a Combination of Global and Context-Sensitive Segments

Most descriptive flexfields use a combination of global and context-sensitive segments. With a
combination of global and context-sensitive segments, the processing is as follows:
When the user opens the flexfield, all the global segments and a context prompt appear.
Once the user chooses a context, the appropriate context-sensitive segments are added to
the already visible global segments.

Chapter
CLASSROOM
Planning Flexfields: Global and Context Fields
Specifying the Flexfield Attributes

Once you have the structure designed and the context behavior determined, you can plan the
flexfield cosmetics. These include:
The context prompt
All the segment prompts
The segment separator
Specifying the Flexfield Structures
All of the segments contained on the flexfield will be defined to a structure. There is a default
structure, Global Data Elements, to which you define all global segments. In addition to the
Global Data Elements structure, you create a separate structure for each context. Use
meaningful context names since they show up in the list of values for the contexts. Clear the
enabled box if you ever need to mark this structure as unavailable. When you have specified
your structure information, click the Segments button to define your structure segments.

Chapter
CLASSROOM
Specifying the Flexfield Attributes
Specify How the Context Is Determined

Prompt - This is the prompt context displayed on the flexfield. If you choose to display the
context field, you must supply a value for this field.
Value Set You can optionally associate a value set to specify valid values for the context
value.
Default Value - Specify a default context structure to use. Always define a value here if you
are not using a reference field and not displaying the context field.
Reference Field - If you use a reference field, enter the name here in the format Block.field.
Use the pop-up list on this field to display a list of the fields on the base window that are most
likely to be referenced.
Required - Indicate whether a context field value is required.
Displayed - Clear this check box if you want to restrict the user from choosing different
contexts. If you use a reference field, you do not have to display the context field unless you
want to allow the user to select a context different from the reference field value. If you do not
display the context field and are not using a reference field, you should define a default context
value as discussed above.

Chapter
CLASSROOM
Specifying the Context Field Information
Synchronize with Reference Field - Check this box if you want the context field value to be
always synchronized with the reference field value for this descriptive flexfield.

Chapter
CLASSROOM
Specifying Segment Attributes

Specify the following attributes for each segment in the structure:
Number - The placement of the field on the window, from top to bottom.
Name - The internal name for this segment.
Window Prompt - The prompt to be displayed for this segment on the flexfield.
Column - The ATTRIBUTE column stores the data from this segment. Available columns are
selectable from a pop-up list for this field. See the following page for an explanation of how
ATTRIBUTE columns store descriptive flexfield data.
Value Set - If you wish the validate the data entered through this segment, specify a value set
to perform validation checking.
Displayed - Clear this check box if you need to prevent the display of this field.
Enabled - Select this check box to mark this segment ready for processing.

Chapter
CLASSROOM
Specifying the Segment Attributes
Storing Descriptive Flexfield Segments

As mentioned previously, the segments that make up a descriptive flexfield are stored in
columns in the underlying tables. Each segment stores its data in one of the ATTRIBUTE
columns. This does not mean, however, that every segment on the flexfield needs its own
column. As shown on the slide, context-sensitive columns from different contexts can share the
same column. The value in the CONTEXT column distinguishes between context segments.

Chapter
CLASSROOM
Storing Descriptive Flexfield Segments
Descriptive Flexfield Application Tables

This SQL*Plus query can be used to determine the application base table where a descriptive
flexfield stores its data. This is a partial report for one application (General Ledger application ID 101) and does not show any information for flexfields used with SRS.
TITLE
-----------------------------Accounting Calendar: Calendar
Accounting Calendar: Periods
AutoAccounting Rules
AutoAllocation Batch
AutoPost Criteria
GL_AUTOMATIC_POSTING_OPTIONS
AutoReversal Criteria
Automatic Posting Sets
Budget Types
Budget Versions
Budgetary Control Group: Group
Budgetary Control Group: Rules
APPLICATION_TABLE_NAME
--------------------------GL_PERIOD_SETS
GL_PERIODS
GL_IEA_AUTOGEN_MAP
GL_AUTO_ALLOC_BATCHES
GL_AUTOREVERSE_OPTIONS
GL_AUTOMATIC_POSTING_SETS
GL_BUDGET_TYPES
GL_BUDGET_VERSIONS
GL_BC_OPTIONS
GL_BC_OPTION_DETAILS

Chapter
CLASSROOM
Descriptive Flexfield Application Tables
GL_SHARES_ACTIVITY
GL_DAILY_CONVERSION_TYPES
Common Stocks: Share Activity

Conversion Rate Types

Chapter
CLASSROOM
Specifying the Segment Detail Attributes

You can use this window to specify any additional attributes for the segment.
Validation Block Entries
Value Set - The name of the value set used to validate data entered through this segment.
Description - The description of this value set.
Default Type - If you wish to define a default value for this segment, select the data type here.
Default Value - Define the actual default here.
Required - Select this checkbox if a value for this segment is mandatory.
Security Enabled - Select this checkbox to turn on any security rules for this value set.

Chapter
CLASSROOM
Specifying the Segment Detail Attributes (continued)

Sizes
These sizes determine the width of the field on the flexfield that is used to display this
segment. Especially consider the interaction between Display Size and the Maximum Size
value defined to the value set used with this segment.

Chapter
CLASSROOM
Specifying the Segment Detail Attributes (continued)

Prompts
List of Values - By default, this will be the same as the segment name. It should not be larger
than the Display Size.
Window - Specify the label that will appear to the left of this segment on the flexfield.

Chapter
CLASSROOM
Specifying Segment Defaults - Examples

Default Type: Constant
Default Value: The constant specified.
Example: USA
Result: USA
Default Type: Current Date
Default Value: The date at the time of entry.
Example:
Result: AUGUST 01, 2007
Default Type: Current Time
Default Value: The Date/Time at the time of entry.
Example:
Result: 14:30:00 AUGUST 01, 2007

Chapter
CLASSROOM
Specifying Default Values
Default Type: Profile

Default Value: The value of the specified profile option. Use the application name of the
profile option.
Example: GL_SET_OF_BOOKS_ID
Result: 101
Default Type: Segment
Default Value: The value returned by the specified previous segment.
Example: Company
Result: 01
Default Type: SQL Statement
Default Value: The value returned by the specified SQL statement. The statement must return
a single value. $PROFILES$ and $FLEX$ can be used in the statement.
Example: SELECT NAME FROM EMP WHERE JOB=CEO
Result: Jones

Chapter
CLASSROOM
Default Type: Field

Default Value: The value in the specified field. Use the format block:field
Example: ORDER:LINE
Result: 3
Defining a Descriptive Flexfield

Chapter
CLASSROOM
Defining Value Sets

Chapter
CLASSROOM
Locating the Flexfield Definition

Chapter
CLASSROOM
Defining the Header Attributes

The header attributes you specify include:
Application - The application that owns the flexfield.
Title - The title displayed at the top of the flexfield.
Freeze Flexfield Definition - Select this box when you have finished defining your flexfield.
Freezing the definition enables the Compile button so you can compile your definition.
Segment Separator - Specify a separator to be used when displaying concatenated segment
values.
Global Data Elements - If your structure has no context-sensitive structures, select Global
Data Elements and click the Segments button to define the global segments.
Define the segments that always appear regardless of the context value. Define global
segments first to facilitate efficient column use.

Chapter
CLASSROOM
Defining the Flexfield Header Attributes
Defining Segment Attributes

Number - Specify the sequence number (from top to bottom) of this segment within the
flexfield structure. The segments defined for Global Data Elements always appear first. They
are the followed by the segments defined for whatever other context-sensitive structure is
selected.
Name - Enter the name for this segment.
Window Prompt - Enter a prompt to show up on the flexfield window. The default is to use
the Name.
Column - Select the ATTRIBUTE column in the base table to hold this segments data. A popup list for this field displays the columns available to you for definition.
Value Set - Specify an existing value set to validate the data for this segment.
Click the Open button to define additional attributes for your segment.

Chapter
CLASSROOM
Specifying Validation and Field Sizes

Use this window to specify additional attributes for the segment.
If you are using a value set to validate the input in this segment, enter the name of the value
set. You can also enter a default for the segment and enable security.
Use the Sizes fields to control the display of the segment in the flexfield window.
Specify the Display Size of the flexfield segment to be the same as the Maximum Size of the
value set used by this segment to avoid scrolling.
Index Flag (Accounting Flexfield Only) - This is used with the General Ledger Optimizer
feature.

Chapter
CLASSROOM
Specifying Validation and Field Sizes
Freezing and Compiling the Definition

Freeze the flexfield information to notify the application to begin using the flexfield.
Compiling the flexfield stores the information efficiently. If the compile detects any problems,
a message window displays a warning.
Flexfields automatically compile the flexfield definition at every commit on this form. The
request for view generation automatically follows compilation.
You see your own changes immediately. Other users must exit or change responsibilities to see
the new definitions take effect.

Chapter
CLASSROOM
Defining Context Information

Define context information to determine how context-sensitive structures are chosen.
If not using a reference field to obtain the context value, enter a context field prompt. This
is the prompt that instructs the user to select a context.
Optionally enter a value set to specify valid values.
Optionally enter a default value. This should be the name of the most common contextsensitive structure. If you use a reference field, ensure that the default value can be
obtained from the reference field.
If you are using a reference field, specify the field name in the Reference Field field. Not
all fields on the window can be used as a reference field. Use the list of values for this
field to set the possible reference fields for the window.
Specify whether the context field is required. Without a required response in the context
field, users can avoid entering any information in any of the context-sensitive structures. If
you are requiring a context value and not displaying a context prompt, either provide a
default or ensure that a value can be obtained from a reference field value.
Specify whether the context field is displayed. If you want to restrict the user from
choosing different contexts, you should not display the context field. If you use a

Chapter
CLASSROOM
Defining Context Field Information
reference field, you do not have to display the context field unless you want to allow the
user to select a context different from the reference field value. If you do not display the
context field and are not using a reference field, you should define a default context value
as discussed above.
Specify whether the context field value should be synchronized with the reference field
value, if applicable.
Enter the context values in the Context Field Values region. The names of these structures
must exactly match the values you expect to see in the context field.

Chapter
CLASSROOM
Defining Context-Sensitive Segments

Chapter
CLASSROOM
Defining Values for a Value Set

Chapter
CLASSROOM
Summary
This lesson discussed how to plan a descriptive flexfield. Descriptive flexfields gather
additional information beyond that gathered by Oracle Applications. Not all users of the same
descriptive flexfield need the same information. Descriptive flexfields can be customized so
that each user sees only the information needed.
Once you have planned the structure of your descriptive flexfield, the actual definition process
is straightforward. If this flexfield uses any new value sets, plan those first. Define the flexfield
header attributes. Define all global segments for the Global Data Elements structure.
If you are using multiple contexts, define either a reference field on the base window, or a
context field on the flexfield itself to control which context structure appears. For each context,
define a structure containing the segments appropriate for that context.
When you have finished defining all your structures and segments, freeze your definition and
compile the flexfield. This makes the flexfield available for others to use.

Chapter
CLASSROOM
Summary
Chapter 21
Defining Key Flexfields

Chapter
CLASSROOM


Chapter
CLASSROOM

Chapter
CLASSROOM
Lesson Topics
Explain intelligent keys and provide examples
Identify key flexfields that are required by Oracle Applications
Explain the purpose of flexfield qualifiers and optional key flexfield features
Design a key flexfield structure
Define the key flexfield structure and segment attributes
Define flexfield qualifiers and segment qualifiers

Chapter
CLASSROOM
Objectives
Lesson Topics
Explain the purpose for cross-validation
Define cross-validation rules and control the interaction between multiple rules
Identify candidates for shorthand entry
Plan and define useful shorthand aliases
Enable shorthand entry
Explain how flexfield security is accomplished
Identify which flexfields are candidates for security
Design a security plan
Control interactions between security rules
Define and assign security rules
Enable security

Chapter
CLASSROOM
Objectives
Overview
Key flexfields create unique identifiers for use internally by Oracle Applications. The
combinations of values for the segments of a key flexfield identify entities. These code
combinations are used throughout Oracle Applications.
Depending on which key flexfield you are defining, you might need to specify flexfield
qualifiers and segment qualifiers. There are also several optional features of key flexfields you
may wish to implement.
This lesson covers the mechanics of the definition process.

Chapter
CLASSROOM
Overview
Overview, continued
This lesson describes additional flexfield options, including:
Cross-validation - Cross-validation rules let you control the combination of values
entered for a key flexfield.
Shorthand aliases - Shorthand aliases let you label certain groupings of values for a
multi-segment flexfield. Whenever you need one of these groupings of values, you can use
the alias for that grouping to enter the entire group.
Security rules - Security rules let you control flexfield access to data. You create and tie
security rules to a value set to specify which entries in a list of values are available to a
user of a specific responsibility. This allows you to control that users access to data. You
create security rules by defining inclusion or exclusion statements. You combine these
statements to create a security rule. You must carefully consider the interaction of multiple
rules when planning your security.

Chapter
CLASSROOM
Overview
Building Intelligent Keys for Oracle Applications

Intelligent keys are multipart key values in which each part of the key contains meaningful
information. You use key flexfields to build the intelligent keys required by Oracle
Applications.
Because key flexfields are integrated with the internal processing of Oracle Applications, there
are more requirements for the structure and content of key flexfields than was the case with
descriptive flexfields.

Chapter
CLASSROOM
Intelligent Keys
Requirements for Key Flexfields

Key flexfields have a dual purpose. They must collect information required by Oracle
Applications and still allow for user configuration.
Provide Required Information
Provide information needed for reports and processing. For some applications, particular
items of information must be identified within the flexfield. For example, Oracle General
Ledger requires the balancing segment of the Accounting Flexfield.
Build unique IDs for use by the applications while giving users meaningful codes.
Provide Configuration Capability
Tailor the flexfield to the companys business practice instead of changing the practice to
fit the flexfield.
Retain the information the company already keeps.

Chapter
CLASSROOM
Key Flexfields' Dual Purpose
Key Flexfields Used by Oracle Applications (Partial List)

The above slide displays some of the key flexfields used by Oracle Applications. The number
of key flexfields is significantly smaller than the number of descriptive flexfields.

Chapter
CLASSROOM
Oracle Applications Key Flexfields
Implementing Key Flexfields: Procedure

The above slide displays the steps involved in implementing a key flexfield. The first two steps
are covered in this lesson. The remaining steps are covered in the remainder of the course.

Chapter
CLASSROOM
Implementing Key Flexfields
Key Flexfield Structures

Although it is possible for a key flexfield to use multiple structures, it is much less typical than
with descriptive flexfields. Most key flexfields use only one structure. However, key flexfields
still allow the user to control the structure of the flexfield. For example, the slide shows two
different accounting flexfield structures defined by two different businesses. Each business
defines an accounting flexfield that reflects its operating structure
While in many cases the user has control over which descriptive flexfield structure is used,
with key flexfields the application usually determines the correct structure with which to
function. For example, Oracle General Ledger determines which accounting flexfield structure
to use from the profile option Set of Books.

Chapter
CLASSROOM
Key Flexfield Structures
Key Flexfield Code Combinations

Key flexfields typically consist of several segments. The values provided by these segments
make up the code combinations that function as intelligent keys for use by Oracle Applications.

Chapter
CLASSROOM
Code Combinations
Storing Code Combinations

Each flexfield stores its code combinations in a database table. These database tables are called
code combinations tables. In the combinations table, there is one column for every key
flexfield segment. These columns are usually named SEGMENTn, where n is a number. There
is a set number of SEGMENT columns available for each key flexfield. You assign a key
flexfield segment to a particular SEGMENT column when you define the key flexfield.
Each row in the combinations table (that is, each unique combination of segment values) is
identified by a unique ID value stored in a unique ID column. This column functions as the
primary key for the combinations table. For key flexfields that have multiple structures, there is
also a structure ID column.

Chapter
CLASSROOM
Storing Code Combinations
Key Flexfield Application Tables

This SQL*Plus query can be used to show Oracle Applications key flexfields and the tables in
which they store their code combinations.

Chapter
CLASSROOM
Key Flexfield Application Tables
Key Flexfield Qualifiers

Both descriptive flexfields and key flexfields allow the user to design the flexfield structures
and their segments. With descriptive flexfields, neither the information gathered nor the way
the information is structured is used internally by Oracle Applications. Key flexfields,
however, are different.
Oracle Applications use certain pieces of information collected by some key flexfield segments
internally. For example, Oracle General Ledger needs to know which segment in the
Accounting flexfield to use for balancing operations. But since the location of the balancing
segment in the accounting flexfield can be configured, the application must have a way of
locating the segment it needs within any accounting flexfield structure.
Being able to locate particular segments in a key flexfield structure is the purpose for
qualifiers. A qualifier is a label attached to a particular key flexfield segment so it can be
located by the application requiring its information.

Chapter
CLASSROOM
Key Flexfield Qualifiers
Types of Key Flexfield Qualifiers

Qualifiers allow the user to retain the ability to configure the structure of the flexfield while
still allowing the Oracle Application to find the information it needs to process.
There are two types of qualifiers:
Flexfield qualifiers identify a segment in a flexfield.
Segment qualifiers identify a value in a segment.
The slide shows both types of qualifiers assigned to an accounting flexfield combination.

Chapter
CLASSROOM
Types of Qualifiers
Flexfield Qualifiers Identify Key Flexfield Segments

The flexfield asks each segment a yes/no question.
Flexfield qualifiers may be unique, global, and required:
Unique: Is this the segment that this flexfield can have only one of?
Required: Is this the segment this flexfield must have to do its work?
Global: Is this a segment? Global qualifiers exist as carriers for segment qualifiers.
Assigning Flexfield Qualifiers to Segments
Global qualifiers need not be assigned since they apply automatically to every segment in
the flexfield.
Assign flexfield qualifiers while defining segments.
Key Flexfields that Use Qualifiers
Here are some of the key flexfields that user qualifiers with their owning application:
Accounting Flexfield (Oracle General Ledger)
Location Flexfield, Asset Category Flexfield (Oracle Assets)
SoftCoded Key Flexfield (Oracle Human Resources)

Chapter
CLASSROOM
Flexfield Qualifiers
Cost Allocation Flexfield (Oracle Payroll)

Sales Territory Flexfield (Oracle Receivables)

Chapter
CLASSROOM
Identifying Values in Flexfield Segments with Segment Qualifiers

A segment qualifier is similar to the segment asking each value the question, What type of
value are you?
For example, the account number 300 may be used within a company as a revenue account.
Use the following segment qualifiers with the accounting flexfield:
Allow Budgeting
Allow Posting
Account Type: Asset, Expense, Liability, Ownership/Stockholders Equity, or Revenue

Chapter
CLASSROOM
Segment Qualifiers
Other Key Flexfield Features

Some other capabilities of key flexfields are available for use. You should consider using these
capabilities where appropriate:
Dynamic insertion of new values Dynamic insertion allows users to enter new values in
display windows in addition to the typical code combination entry window.
Cross-validation - Cross-validation rules let you control the combination of values
Security rules - Security rules let you control flexfield access to data. You create and tie
security rules to a value set to specify which entries in a list of values are available to a
user of a specific responsibility. This allows you to control that users access to data.
Shorthand aliases - Shorthand aliases let you label certain groupings of values for a multisegment flexfield. Whenever you need one of these groupings of values, you can use the
alias for that grouping to enter the entire group.

Chapter
CLASSROOM
Other Key Flexfield Options
Allowing Dynamic Insertion of New Code Combinations

Key flexfield code combinations appear on many types of windows. Typically, Oracle
Applications use a particular form (called a combination form) for directly entering the new
code combinations. These same code combinations can be displayed by many other windows.
On these related windows, however, the fields are typically read-only and not updateable.
Therefore new code combinations cannot be entered from these forms.
If you allow dynamic insertion, you can enter new code combinations from such display
windows as well as from regular entry windows.

Chapter
CLASSROOM
Allowing Dynamic Insertion
Validating the Combinations of Segment Values to Control Data Integrity

For key flexfields with multiple segments, you can define rules to cross-check value
combinations entered. Thus you can prevent combinations of segment values that are illogical
or should not be allowed from being entered.
The slide shows an illogical combination of values for the Asset key flexfield being
disallowed.
Cross-validation is discussed in more detail later in this lesson.

Chapter
CLASSROOM
Cross-Validating Values
Using Shorthand Aliases to Speed Data Entry

If the same combination is frequently being entered into a multi-segment flexfield, you should
consider defining an alias for that value combination. You can then use the alias to generate the
complete set of values for the flexfield.
Entering a shorthand alias automatically inserts the values for that alias into the key flexfield.
Shorthand aliases are discussed in more detail later in this lesson.

Chapter
CLASSROOM
Using Shorthand Aliases
Securing Values
You may want to allow users to only enter or view specific values for flexfields.
You can create a security rule to restrict values available to a given responsibility. Once you
associate that rule to the appropriate responsibility, all users of that responsibility are restricted
to the values allowed by that security rule.
For example, a company has assigned its sales force to different responsibilities according to
the type of items they sell. Two of these responsibilities are Electronic Sales and Household
Sales. A value set called Item Type lists all the types of items the company sells. In this case,
you can define a security rule to restrict the users of a particular responsibility to only access
item types appropriate for their responsibility. For example, the Household Goods Only
security rule allows access only to the FURN and APPL item types.
Security rules are discussed in more detail later in this lesson.

Chapter
CLASSROOM
Securing Value Set Access
Designing Key Flexfield Layout

Design the structures needed and the segments for each structure:
Identify the structure titles.
Plan the number and order of segments.
Identify the segment separator.
Determine the value sets and values to be used.
Plan the window prompts.

Chapter
CLASSROOM
Designing the Key Flexfield Layout
Designing Key Flexfield Segments

Decide how each segment of the key flexfield should behave and what values to allow in each
segment.
Enabled or Displayed - Can users see this segment? Disabled segments are not displayed. If
the segment does not display, use a default value to populate it.
Required - Can users leave the segment without entering a value? Most key flexfield segments
require a value.
Validation - Most key flexfield segments provide a list of values. Use a predefined value set,
or design a new one for this segment. Not using a value set is equivalent to using a validation
type of None, character format, width same as underlying segment column, uppercase allowed,
and no right justification or zero fill.
Value Security - Should security rules for the value set apply to this segment?
Related Segments - Link segments with ranges of Low and High to enforce a relationship
between them.

Chapter
CLASSROOM
Designing Segments
Specifying Segment Defaults - Examples

Default Type: Constant
Default Value: The constant specified.
Example: USA
Result: USA
Default Type: Current Date
Default Value: The date at the time of entry.
Example:
Result: August 1, 2007
Default Type: Current Time
Default Value: The Date/Time at the time of entry.
Example:
Result: 14:30:00 AUGUST 01, 2007

Chapter
CLASSROOM
Specifying Default Values
Default Type: Profile

Default Value: The value of the specified profile option. Use the application name of the
profile option.
Example: GL_SET_OF_BOOKS_ID
Result: 101
Default Type: Segment
Default Value: The value returned by the specified previous segment.
Example: Company
Result: 01
Default Type: SQL Statement
Default Value: The value returned by the specified SQL statement. The statement must return
a single value. $PROFILES$ and $FLEX$ can be used in the statement.
Example: SELECT NAME FROM EMP WHERE JOB=CEO
Result: Jones

Chapter
CLASSROOM
Default Type: Field

Default Value: The value in the specified field. Use the format block:field
Example: ORDER:LINE
Result: 3
Planning Decisions
Application Question: Does the application support different segment structures?
Related Question: How many structures are needed?
Application Question: How many segment columns are available?
Related Question: What segments are needed?
Application Question: What flexfield qualifiers does this flexfield use or need?
Related Question: Do segments correspond to each needed qualifier?
Application Question: Are dynamic inserts feasible?
Related Question: Who can create new combinations?
Application Question: Should cross-validation be enabled?
Related Question: Is protection from invalid combinations needed?

Chapter
CLASSROOM
Planning Decisions
Application Question: Should shorthand flexfield entry be enabled?

Related Question: Are many combinations used repeatedly?
Application Question: Which value sets are available?
Related Question: How should the segments be validated?
Application Question: Which segments should use flexfield value security?

Related Question: Are some segment values privileged or applicable only for some users?

Chapter
CLASSROOM
Planning Values for Use with Key Flexfields

Plan the values for the independent and dependent value sets created for this key flexfield.
Choose values logically and systematically. Grouping values together logically makes defining
security and validation rules much easier.

Chapter
CLASSROOM
Planning Key Flexfield Values
Defining Key Flexfields: Procedure

Use the following procedure to define a key flexfield:
Plan the key flexfield structure.
Define new value sets if needed.
Define key flexfield structure.
Define the structure segments, including qualifiers.
Freeze and compile the flexfield definition.
Define value set values, including any qualifiers.
Test the key flexfield.

Chapter
CLASSROOM
Definition Procedure
Defining Value Sets

Chapter
CLASSROOM
Accessing the Key Flexfield Definition

Chapter
CLASSROOM
Specifying the Key Flexfield Behavior

Enabled - This enables shorthand entry of frequently used value combinations.
Segment Separator - Specify a segment separator character. Segment separators are especially
important for key flexfields since their values are often displayed concatenated.
Cross-Validate Segments - This enables cross-checking of segment value combinations.
Allow Dynamic Inserts - This allows new key value combinations to be dynamically created
and inserted into the table.
When you have defined the flexfield level attributes, click the Segments button to continue
defining individual segments for this structure.
Note: some key flexfields may require additional features to be defined.

Chapter
CLASSROOM
Specifying Flexfield Behavior

Use the Segments Summary window to define most of the segment attributes.
Number - This specifies the sequence in which the fields will appear on the window.
Name - The name by which this segment is known within Oracle Applications. Name the
segment intuitively. Other segments may refer to this one for validation information. Also, the
view generated uses the segment names for its column names.
Window Prompt - The prompt that will appear on the window. The segment name is the
default.
Column - Specify the SEGMENT column in the underlying base table that contains this
segments data. A pop-up list shows the SEGMENT columns available for use.
Displayed - If you choose not to display a segment, specify a default to populate it.
Enabled - This flags the segment as available for use.

Chapter
CLASSROOM
Defining Validation and Size Attributes

Validation Information
Use the Validation block fields to specify value set information.
Choose a predefined value set with a list of values or design one for this particular
segment with the Value Sets window.
Specify default information if you need to populate the segment with a default value.
Determine whether security rules should apply to this value set for this segment.
Size Specifications
Display Size determines the field size on the flexfield. Specify a display size the same as
the maximum segment size to avoid scrolling.
Keep prompts small for neater reports.
Click the Flexfield Qualifiers button to determine whether this flexfield has any qualifiers to be
assigned.

Chapter
CLASSROOM
Defining Validation and Size Attributes
Defining Flexfield Qualifiers

Chapter
CLASSROOM

Chapter
CLASSROOM
Defining Value Set Values

Chapter
CLASSROOM
Defining Segment Qualifiers

Specify additional qualifiers at the value level when appropriate. For example, Allow
Budgeting is an Accounting Flexfield segment qualifier.
Whenever possible do not change a value, change its description. If reuse is not possible,
disable unused values. You cannot delete them.

Chapter
CLASSROOM
Defining Segment Qualifiers
Using Cross-Validation to Enforce Data Integrity

You can create rules specifying the allowable value combinations for multiple segment key
flexfields. In this way you can avoid the generation of illogical or inappropriate key values.
Cross-validation rules apply only to key flexfields.
The above slide displays an Asset Location flexfield with three fields for country, state, and
city information. Since Asset Location is a key flexfield, you could define a cross-validation
rule to ensure no one tries to specify a US state value for the UK. Note that you could also
specify cross-validation rules to ensure that each city value was placed in the correct state.

Chapter
CLASSROOM
Cross-Validating Values
Designing Rule Elements

Cross-validation rules consist of an Include element that includes all possible combinations,
and one or more Exclude elements that restrict various segment value combinations. To make
maintenance easier, use many simple rules rather than a few complex rules. To pass validation,
a value combination must be included and not be excluded by any of the Exclude elements.
Rules are not retroactive, they apply only to segment value combinations entered after they are
defined and enabled.

Chapter
CLASSROOM
Cross-Validation Rule Syntax
Specifying Data Type and Format in Cross-Validation Rules

Cross-validation rules recognize any value characteristics specified for the value sets the
segments use, such as Format Type, Right-Justify and Zero-Fill, Numbers Only, and
Uppercase Only. Note that the Accounting flexfield does not use NULL values.
The Cross-Validation Rules window enforces the correct collating order for the platform.
For most platforms (ASCII) 0 < 000 < Z < ZZZ
For some platforms (EBCDIC) A < AAA < 9 < 999

Chapter
CLASSROOM
Data Type Specifications and Cross-Validation Rules
Preparing for Cross-Validation

Chapter
CLASSROOM
Defining Cross-Validation Rules and Error Messages

Define an Error Message and an Error Segment - Enter a rule name and description for
each cross-validation rule. Specify the error message to display and the segment where the
cursor should move when a user enters an invalid combination. Use the segment where the
error probably occurred. Enter optional start and end dates for your rule. You can also use
these fields to disable a rule.
Specify at Least One INCLUDE Element - Unspecified values are always excluded, so every
rule needs at least one Include statement. Otherwise no combinations will ever pass validation.
As shown in the example, you can use the pop-up window to define which combinations to
exclude. Exclude statements override Include statements. There can be multiple statements and
each statement can specify values for multiple flexfield segments.
Change the Flexfield Definition - You must exit and sign on again or change responsibilities
to see any changes.

Chapter
CLASSROOM
Defining Cross-Validation Rules
Maintaining Cross-Validation Rules

To minimize maintenance, plan cross-validation rules when first setting up the key flexfield. If
later changes are necessary, review existing rules to ensure accurate and consistent validation.
Disable previously existing combinations that are no longer valid according to the new rules.
Using Reports to Maintain Cross-Validation Rules
The Cross-Validation Rule Violation Report offers a listing of all the previously created
flexfield combinations that violate the cross-validation rules for a given structure. The
report program can also disable the existing combinations that violate the new rules.
The Cross-Validation Rules Listing report lists all the cross-validation rules that exist for a
particular flexfield structure.

Chapter
CLASSROOM
Cross-Validation Reports
Interaction of Cross-Validation and Value Security Rules

Both cross-validation and value security control the data a user can enter. The above slide
displays a comparison of the scope and action of each.
Cross-Validation
Applies to all users regardless of responsibility
Affects only key flexfields
Applies across an entire key flexfield structure
Value Security Rules
Apply only to users of the chosen responsibility
Can affect key and descriptive flexfields as well as program parameters
Apply only to the value set used by a flexfield segment or program parameter

Chapter
CLASSROOM
Comparing Cross-Validation and Security Rules
Using Shorthand Aliases to Speed Data Entry

Whenever you notice that you are frequently entering the same combination of values into a
multi-segment flexfield, you should consider defining an alias for that value combination. You
can then use the alias to generate the complete set of values for the flexfield.
Select an alias from a pop-up list of possible aliases for the flexfield. You can also enter the
alias name directly in the alias window.
Entering a shorthand alias automatically inserts the values for that alias into the key flexfield.

Chapter
CLASSROOM
Using Shorthand Aliases
Using Full and Partial Aliases

An alias can represent a complete flexfield combination or a set of partial segment values:
If most combinations vary only in a single segment, create an alias with that segment
blank and values specified for the remaining segments.
If the alias represents a complete combination, once the alias name has been selected or
entered, the shorthand window closes and the cursor moves to the next field.
If the alias represents a partial flexfield value, the full flexfield window pops up with the
cursor on the first empty segment.
Pressing [Return] in a blank shorthand entry window also pops up the full flexfield
window.
Users can override values generated by aliases as appropriate.

Chapter
CLASSROOM
Using Full and Partial Aliases
Typical Key Flexfields Using Aliases

Because aliases are used to speed up the entry of often-used value combinations, certain key
flexfields in Oracle Applications are especially suited for alias entry.

Chapter
CLASSROOM
Typical Key Flexfields Using Aliases
Defining an Alias

Chapter
CLASSROOM
Defining an Alias Template

Chapter
CLASSROOM
Recompiling the Flexfield Definition

Chapter
CLASSROOM
Flexfields: Shorthand Entry Values

The Flexfields: Shorthand Entry profile option controls the behavior of aliases at the user level.
The user has the ability to update this option as appropriate.

Chapter
CLASSROOM
Flexfields: Shorthand Entry Profile Option
Flexfields: Show Full Value Profile Option

The Flexfields: Show Full Value Profile Option allows the user to turn off the full display of a
key flexfield whenever the user specifies an alias with values for all segments of the flexfield.

Chapter
CLASSROOM
Flexfields: Show Full Value Profile Option
Modifying Alias Definitions

Since aliases are tied to the structure of the flexfield, any change to the flexfield structure
during setup must be reflected in any aliases providing values for that flexfield. Some of the
typical modifications that also require changes to aliases are shown in the slide.

Chapter
CLASSROOM
Modifying Existing Alias Definitions
Controlling Access to Flexfield Values by Specifying Value Security Rules

Responsibilities are used within Oracle Applications to specify what operations a user can
perform. Responsibilities limit the forms and reports a user can access. Responsibilities are
equivalent to job descriptions and therefore usually map to data access privileges as well. Users
of the same responsibility generally need to see the same data.
You can define security rules to restrict users from using flexfields to enter or display certain
data. Once you associate these rules with the appropriate responsibility, all users of that
responsibility are restricted to the values allowed by that responsibilitys security rule.
Example
In the example on the slide, a company has assigned its sales force to different responsibilities
according to the type of items they sell. Two of these responsibilities are Electronic Sales and
Household Sales. A value set called Item Type lists all the types of items the company sells. In
this case, you can easily define a security rule to restrict the users of a particular responsibility
from accessing item types not appropriate for their responsibility. For example the
Hshld_Goods_Only security rule allows access only to the FURN and APPL item types.

Chapter
CLASSROOM
Securing Value Set Access
How Value Security Works

You can apply security to the value sets used by key flexfield segments, descriptive flexfields
segments, and request parameters.
Security rules have no effect for segments or parameters that use value sets with a
validation type of None, Special, Pair, Translatable Independent, or Translatable
Dependent, or for segments without a value set.
Security rules provide data entry and querying control. Once the security rule is associated
with a responsibility, a list of values displays only the values appropriate to that
responsibility.
Some forms permit querying of restricted values but do not permit updating of restricted
values.
Security rules apply only to data entered through the forms on which the flexfield appears.
They do not apply to data created or copied automatically by the applications themselves.
Therefore, be careful when loading data without using Oracle Application forms.
If you are using a parent and child value hierarchy with the Accounting Flexfield, you can
enable hierarchical value security on your value sets. With hierarchical value security,
any security rule that applies to a parent value also applies to its child values.

Chapter
CLASSROOM
Security and Value Sets
Security Rule Elements

Security rules are defined in terms of the values in the value set.
Certain values or value ranges are either included or excluded by a rule.
The same rule can specify both values to be included as well as different values to be
excluded.
By default all values are excluded unless explicitly included, and exclusion tests override
inclusion tests.

Chapter
CLASSROOM
Constructing Security Rules
Specifying Security Rules

Whenever possible, restrict access to ranges of values. Plan values carefully to make security
rules easy to define.
Example
Assume you have a value set ACCOUNT TYPE. Since the accounts are distinguished by the
account type number, you can define a rule including all account types in the 1100 account
type number series. This rule can later be assigned to an appropriate responsibility to restrict
users from accessing anything but cash account types.

Chapter
CLASSROOM
Specifying Acceptable Values
Using Multiple Elements

As shown on the previous slides, you define security rules in terms of exclude or include
clauses. You can combine these clauses as necessary to effect the restrictions you need. A
security rule can therefore consist of one clause or many.
You can apply security rules to more than one responsibility, and a single responsibility can
have more than one security rule associated with it. It is not unusual for several responsibilities
to share a broadly defined security rule with some of the responsibilities also having more
restrictive security rules.
Example
The examples on the slide show two rules: one containing multiple clauses and one consisting
of only one clause.

Chapter
CLASSROOM
Using Multiple Clauses
Interaction of Security Rules and Elements

Since a responsibility can have multiple security rules for the same value set, it is important to
consider the interaction of security rules.
In a single security rule:
Everything is excluded unless explicitly included.
The clauses have a logical OR relationship to one another so that the result is a union of
all included values.
If a value satisfies the criteria for both an include and an exclude, it is excluded.
In multiple security rules:
More rules restrict more not less. All values must pass all security rules to be acceptable.
The different rules have a logical AND relationship to one another so that the intersection
of the rules included values applies.
If a value satisfies the criteria for both an include and an exclude, it is excluded.
Example
The slide shows two examples of security rules operating on a value set. The values approved
by the different rules are shown in italics.

Chapter
CLASSROOM
Rules with Overlapping Values
Rule Results Without Overlapping Ranges

If the values specified by the clauses do not overlap, the result sets are different:
The result set for a responsibility with a single security rule with multiple clauses contains
all values that satisfy any of the include clauses. Any excluded values are removed.
The result set for a responsibility with multiple rules contains no members if there are not
any values that satisfy all the rules.

Chapter
CLASSROOM
Rules Without Overlapping Values
Implementing Flexfield Security

Chapter
CLASSROOM
Enable Security for a Value Set

Specify either Non-Hierarchical Security or Hierarchical Security for the Security Type for the
value set.
Hierarchical security is only used with parent and child values with the Accounting Flexfield.
With hierarchical security, a security rule that applies to a parent value also applies to its child
values.

Chapter
CLASSROOM
Enabling Security for a Value Set
Enabling Security for a Segment

Chapter
CLASSROOM
Enabling Security for a Segment

Chapter
CLASSROOM
Enabling Security for a Program Parameter

Chapter
CLASSROOM
Defining Security Rules

To define security information for an existing value set, search for that value sets
definition by its value set name, or by any flexfield segment or concurrent program
parameter that uses that value set. Specify how you wish to search by selecting the
appropriate option. Security must be enabled for the value set, or it will not appear.
Specify include and exclude ranges for values.
An automatic exclude rule excludes all values not explicitly included. Rules without
elements therefore exclude everything.
Without any rules, anyone can see and use any segment value.
On most computers, 0 < Z.

Chapter
CLASSROOM
Defining Security Rules
Assigning Security Rules

Chapter
CLASSROOM
Assigning Security Rules

Chapter
CLASSROOM
Summary
Key flexfields are used to build identifiers required by Oracle Applications. Key flexfields
allow the user to provide information needed by Oracle Applications while still structuring that
information to reflect a particular business environment.
The procedure for defining a key flexfield is similar to that for defining a descriptive flexfield.
However, there are additional attributes for key flexfields that may also need to be defined.
Additionally, key flexfields have several optional features that should be implemented where
appropriate.
The additional requirements and options for key flexfields include:
By using qualifiers in key flexfields you can require that certain segments and certain
values be identified for processing.
You can allow security checking and integrity checking.
You can define aliases to speed data entry.
You can enter key flexfield value combinations from different windows, if allowed.

Chapter
CLASSROOM
Defining Key Flexfields Summary
Summary, continued
Cross-validation rules are used to restrict invalid combinations of segment values. Rules are
defined by specifying the value combinations that are either allowed (included) or disallowed
(excluded). Cross-validation rules are not tied to a responsibility like security rules. You can
combine cross-validation rules as needed.
Short aliases provide a way to speed entry of frequently used value combinations. Any key
flexfield is a candidate for shorthand alias entry.
You can control the access to data by defining value security rules. These rules list the
allowable values for display or selection through a flexfield segment. The rules are applied to
the value set defined for that flexfield segment. Once you have defined the rules, you assign
them to a responsibility. All users of that responsibility are then restricted to the approved
values when using the flexfields segment.

Chapter
CLASSROOM
Defining Key Flexfields Summary


Chapter
CLASSROOM
Chapter 22
Using Advanced Validation Capabilities

Chapter
CLASSROOM
Using Advanced Validation

Capabilities


Chapter
CLASSROOM

Chapter
CLASSROOM
Lesson Topics
A previous lesson discussed creating and using value sets to check user input. You performed
practices in which you defined value sets of the validation types None, Independent, and
Dependent.
In this lesson, you learn how to use values stored in applications tables for validation. You also
learn how to restrict the set of values returned from the table.
Use values retrieved from application tables for validating input
Reference profile option values when validating input
Use a value from another field on the same form for validation
Use the value from a previously used value set for validation

Chapter
CLASSROOM
Objectives
Overview
There are several advanced techniques you can use when defining value sets for validating
input. These techniques use values obtained from a location other than a list specifically
defined for the value set. These locations include:
Values retrieved from an application table
The current value for a particular profile option
A value used earlier in a field on the form
A value used earlier in another value set

Chapter
CLASSROOM
Overview

Besides obtaining values from an application table, you can obtain other values for validation
from:
Current profile options
A prior field on the same form
A prior value set used by a segment on the same form

Chapter
CLASSROOM
Advanced Validation Options
Using Existing Values in Application Tables for Validation

Use the values stored in application tables to provide values to flexfield segments and
report parameters.
You can use a SQL WHERE clause to restrict the set of values returned.
Remember the Longlist feature for large tables.
Dependent value sets cannot use a table-validated value set as their Independent value set.
Avoiding Double Maintenance
Values stored in application tables are maintained by the application.
Table validation is especially useful when values already exist in feeder systems.

Chapter
CLASSROOM
Table-Validated Value Sets
Defining a Table-Validated Value Set

Match the format options to the values stored in the table when defining table-validated value
sets. Specify which table and which columns to use for this value set in the Validation Table
Information window.
Value Column - Specifies the name, type, and size of the column containing the values to be
used for validating. The list of values limits itself to columns matching the format choices
made in the Value Sets window.
Meaning Column Contains the descriptions for the values in the Value column.
Hidden ID Column - Contains non-displayed values. For example, an application ID number
corresponding to the displayed application name. Many Oracle Applications key flexfields do
not allow the use of the hidden ID column.
Additional Columns - Any additional columns to display. You can use a column alias to
provide a title for the column. Include a width indicator for the column. For example:
user_formname Form Title(30), application_name Application Name(35)

Chapter
CLASSROOM
Defining a Table-Validated Value Set
Restricting Values Retrieved from a Table

Chapter
CLASSROOM
Limitations on Using SQL WHERE Clauses

Chapter
CLASSROOM
Using Multiple Tables for Validation

Chapter
CLASSROOM
Other Advanced Validation Options

Using $PROFILES$
You can reference the current value of a profile option in a WHERE clause by prefixing the
name of the profile option with $PROFILES$.
:$PROFILES$.profile_option_name
Using :Block.field
You can test against the value of a prior field on the same form in a WHERE clause by
referring to the field using the format Block_name.field_name. To find out the block and field
names, click in the field and then select Help>Tool>Examine from the menu bar. This
displays the block name and the field name for the selected field.
Using $FLEX$
You can refer to the current value of a previously used value set on the same form by using
$FLEX$.value_set_name.

Chapter
CLASSROOM
Other Advanced Validation Options
Using $PROFILES$

Chapter
CLASSROOM
Using :block.field to Refer to a Field on the Base Window

Use this value set only with flexfields on windows that have the same block.field
available. If the list of values cannot find the correct field, the segment cannot accept any
value as valid. Do not use this value set with flexfields appearing on other windows or
with report parameters.
This argument requires the same :block.field on every window where a value set based on
this validation table could be used. For example, if the flexfield whose segment uses
block.field validation appears on seven different windows, the same block.field must also
be present on those seven forms.
If sharing value sets among multiple descriptive flexfields, all windows that use any of
those flexfields must have this block.field.
Use only with Oracle Forms. OA Framework (HTML-based) pages do not support
:block.field.

Chapter
CLASSROOM
Using :block.field
Using $FLEX$ to Refer to a Value Used in a Previous Value Set

The flexfield segment or report parameter always uses the value from the Value column
(not the Meaning or Hidden columns).
Because Value_set_name is case-sensitive, you must ensure that the name in the WHERE
clause exactly matches the value set name defined.
Use only letters, numbers, and underscores in value set names if you want to use them
with $FLEX$.
Do not use quotes, spaces, or other special characters in these value set names.
The value set must point to a previous segment in the same flexfield structure. For
descriptive flexfield context-sensitive segments, the value set must point to the previous
segment in the same context-sensitive structure.
Multiple $FLEX$.value_set_name statements can be used in the same WHERE clause.

Chapter
CLASSROOM
Using $FLEX$
Using Cascading Dependencies

You can use the $FLEX$ keyword to create chains of validation checks called cascading
dependencies.

Chapter
CLASSROOM
Cascading Dependencies Using $FLEX$
Using Special Value Sets

Chapter
CLASSROOM
Using Pair Value Sets

Chapter
CLASSROOM
Summary
Some value sets (for example, Independent and Dependent) have lists of approved values
explicitly defined. Other types of value sets, however, can use values from other locations for
validation. Using values from an application table is one example of these alternate locations.
Also, the current value of a profile option can be used. The value from a previously appearing
field on a form can be referenced as well. Finally, the value from a previously used value set
can be used by all subsequent value sets.

Chapter
CLASSROOM
Summary


Chapter
CLASSROOM
Chapter 23
Appendix - Administering Folders

Chapter
CLASSROOM
Appendix - Administering
Folders


Chapter
CLASSROOM

Chapter
CLASSROOM
Objectives

Chapter
CLASSROOM
Folders: Definition

Chapter
CLASSROOM
Administering Folders: Topics

Chapter
CLASSROOM
Assign a Default Folder to a Responsibility

(N) System Administrator responsibility > Application > Administer Folders
Note: You must create default folders before you can perform the following functions. For
information on creating default folders see
(Help) Users Guide > Forms-Based Applications > Customizing the Presentation of Data in a
Folder.
Note: After you save a default folder definition for a folder set, that folder set no longer
appears in the list of values.
Form Fields
Folder Set: Every folder set is associated with a particular folder block, and a user or
responsibility can have one default folder within each folder set. The folder set name
generally describes the records shown in the block; some blocks may have multiple sets of
folders associated with them.

Chapter
CLASSROOM
Assigning a Default Folder to a Responsibility
Assign a Default Folder to a User

(N) Application > Administer Folders
Note: After you save a default folder definition for a folder set, that folder set no longer
appears in the list of values.
Form Fields
Source Type: Enter either User or Responsibility. Records entered in this window use the
source type of User. If one of the current users responsibilities has default folders
defined, the default folders are listed with a source type of Responsibility.
User defaults override Responsibility defaults. You cannot delete Responsibility default
folders in this window.
Responsibility: The Responsibility that uses this default folder definition.

Chapter
CLASSROOM
Assigning a Default Folder to a User
Form Fields
Public: This check box governs the availability of the folder to all users.
Anyones Default: Indicates whether this folder definition is used as a default by a user or
a responsibility. If it is a default definition, use Default Assignments to view the users and
responsibilities for which it is the default folder definition.
Default Assignments: The users and responsibilities that use this folder definition as a
default.

Chapter
CLASSROOM
Assigning Ownership of a Folder

Chapter
CLASSROOM
Deleting a Folder Definition
Summary

Chapter
CLASSROOM


Chapter
CLASSROOM
Chapter 24
Appendix - Incorporating a Custom Program

Chapter
CLASSROOM
Appendix - Incorporating a
Custom Program


Chapter
CLASSROOM

Chapter
CLASSROOM
Lesson Aim
Oracle Applications uses concurrent programs to process and report on data stored in Oracle
Applications tables. These programs are secured, processed, and managed within the Oracle
Applications environment, using the operations that you have seen in other lessons. However,
you can take your custom applications and programs and integrate them into the Oracle
Applications environment as well. In that environment they can be secured and managed the
same way as regular Oracle Applications programs.
This lesson covers how to integrate user-developed programs into Oracle Applications.

Chapter
CLASSROOM
Objectives
Integrating Custom Programs with Oracle Applications

Although Oracle Applications provides you with a complete range of functionality, you may
need to develop and implement your own custom programs to perform specialized processing.
You can integrate such custom applications into the Oracle Applications environment so that
they are processed like all your other Oracle Applications programs and reports.
For example, a sales table used by Oracle Receivables can also be accessed by a user program
for special reporting needs. Such a user reporting program can be added to the Oracle
Applications environment.

Chapter
CLASSROOM
Using Custom Programs in Oracle Applications
Assumptions for Incorporating a New Program

Chapter
CLASSROOM
Components of a Concurrent Program

You need to define several components of a concurrent program when adding your custom
program to the Oracle Applications environment. A concurrent program consists of an
executable modulefor example, an Oracle Reports program or a PL/ SQL procedureand
the input parameters required by the program or procedure. A concurrent program must be
associated with either an existing Oracle application or a custom application. In most cases,
you will associate any custom concurrent programs with a registered custom application. This
protects your concurrent programs during an upgrade.

Chapter
CLASSROOM
Components of a Concurrent Program
Adding a Custom Program to Oracle Applications

Chapter
CLASSROOM
Identifying the Executable

(N) Concurrent > Program > Executable (Forms interface, using the System Administrator
responsibility)
The Concurrent Program Executable window prompts for the following information:
Executable The name for your concurrent program executable. In the Concurrent
Programs window you assign this name to a concurrent program to associate your
concurrent program with your executable logic.
Short Name The short name for your concurrent program executable.
Application The concurrent managers use the specified application to determine in
which directory structure to look for your execution file.
Execution Method Specifies the type of program, such as a PL/SQL procedure or an
Oracle Reports program. The execution method cannot be changed once the concurrent
program executable has been assigned to one or more concurrent programs in the
Concurrent Programs window.
Execution File Name The operating system name of your execution file.

Chapter
CLASSROOM
Identifying the Executable
Subroutine Name The name of your C or Pro*C program subroutine. Only immediate
programs or spawned programs using the Unified C API use this field.
Note: Defining new immediate concurrent programs is not recommended. Use either a
PL/SQL stored procedure or a spawned C program instead.
Execution File Path
Stage Function Parameters button Opens a window that allows you to enter
parameters for the Request set Stage Function. This button is only enabled when you
select Request Set Stage Function as you Execution Method.
For more information see:
(Help) Applied Technology > Oracle Applications System Administration > Configuration >
Overview of Concurrent Programs and Requests > Concurrent Program Executable Window

Chapter
CLASSROOM
Concurrent Programs Window Fields

(N) Concurrent > Program > Define (Forms interface, using the System Administrator
responsibility)
The Concurrent Program window prompts for the following information:
Program A descriptive name for your concurrent program. This is the name you see
when you view your requests in the Requests window. If this concurrent program runs
through Standard Request Submission, you see this name in the Submit Requests window.
Short Name A short name that Oracle Applications can use to associate your program
with a concurrent program executable.
Application The programs application determines what ORACLE username your
program runs in and where to place the log and output files.
Enabled Indicate whether users will be able to submit requests to run this program and
the concurrent managers will be able to run your program. Disabled programs do not
display in users lists, and do not appear in any concurrent manager queues.
Executable: Name The concurrent program executable for your program. The
executable is defined using the Concurrent Program Executable window.

Chapter
CLASSROOM
Creating the Concurrent Program

Chapter
CLASSROOM
Executable: Method The execution method used by your concurrent program displays
in this field.
Executable: Options Contains options for SQL*Report programs.
Executable: Priority Priority for this program. If you do not assign a priority, the users
profile option Concurrent:Priority sets the requests priority at submission time.
Request: Type Certain concurrent managers are specialized to run only certain request
types.
Incrementor For use by Oracle Applications internal developers only.
MLS Function The MLS function used by the program (if applicable). The Multilingual
Concurrent Request feature allows a user to submit a request once to be run multiple
tomes, each time in a different language. If this program utilizes this feature the MLS
function determines which installed languages are needed for the request.
Use in SRS Indicates whether this program can be run using Standard Request
Submission. If this box is checked, you must register the parameters of this program.
Allow Disabled Values For a program authorized for SRS submission, check this box to
allow a user to enter disabled or outdated parameter values.
Run Alone Check this box if your program is incompatible with other programs in its
logical database and should therefore be run alone.
Restart on System Failure Check this box if you want this program to be restarted
automatically when the concurrent manager is restored after a system failure.
Enable Trace turns on SQL tracing when program runs.
NLS Compliant Check this box if the program allows a request to reflect a language
and territory that are different from the language and territory that the user is operating in.
This option should be set only by the developer of the program. The program must be
NLS Compliant to utilize this feature. See: Oracle Applications Developers Guide.
Output Fields Specify the handling or output from executions of this program.
Concurrent Programs Window Buttons
Copy to - Choose this button to create another concurrent program using the same
executable, request, and report information.
Session Control Specify options for the database session of the concurrent program
when it is executed. These options are used to optimize system performance.
Incompatibilities Opens the Incompatible Programs window to define which
programs should not be run when this program is running.
Parameters Opens the Program Parameters window.
For more information see:
Overview of Concurrent Programs and Requests > Concurrent Programs Window
Note: You can also define concurrent programs in the Oracle Applications Framework
interface; using the System Administration responsibility, navigate to Concurrent (heading) >
Programs.
Concurrent Programs Parameters Window Fields

(N) Concurrent > Program > Define > (B) Parameters
The Concurrent Program Parameters Window prompts you for the following information:
Conflicts Domain - The parameter that holds the conflicts domain used by incompatible
programs. Incompatible programs may be incompatible because they run on the same
data; for example, a Set of Books. The Set of Books parameter would be the Conflicts
Domain.
Security Group - Used in HRMS only.
Sequence - The sequence number for the parameter that you are defining.
Parameter - The parameter name.
Enabled - Disabled parameters are not displayed at request submission time and are not
passed to your program.
Validation Information: Value Set - Specify an independent, table, or non-validated
value set for use in checking values passed for this parameter.
Validation Information: Default Type - If you intend to specify a default for this
parameter, declare the default type.

Chapter
CLASSROOM
Concurrent Program Parameters Window

Chapter
CLASSROOM
Validation Information: Default Value - For certain types of default, you can specify a
default value to use. This default value appears automatically when you enter the
parameter fields in the Validation region.
Validation Information: Required - Choose this box if a value for this parameter is
required by your program.
Validation Information: Enable Security - If the value set for this parameter does not
allow security rules, this field is display only. Otherwise, you can choose to apply any
security rules defined for this value set to affect your parameter list also.
Validation Information: Range - Choose either Low or High if you want to validate
your parameter value against the value of another parameter in this structure.
Display - Indicates whether to display this parameter in the Parameters window when a
user submits a request to run this program form the Submit Requests window.
Display: Display Size The field length in characters for this parameter. The user sees
and and fills in the field in the Parameters window launched from the Submit Request
window.
Display: Description Size The display length in characters for the parameter value
description.
Display: Prompt The prompt to appear in the Parameter window of the Submit Request
window.
Display: Concatenated Description Size - The length for the parameter value description
field. This field displays all the parameter values as a concatenated string.
Token Refers to the name of a keyword or parameter for an Oracle Reports program.
Entries in this field are case-sensitive. Any values entered in this field must exactly match
the value expected by the Oracle Reports program.
For a complete description of the fields in this window see:
Overview of Concurrent Programs and Requests > Concurrent Programs Window >
Concurrent Program Parameters Window
Associate a Program with a Request Group

(N) Security > Responsibility > Request
Request Group Window Fields
For the definition of the fields in this window see:
Overview of Concurrent Programs and Requests > Request Group Window

Chapter
CLASSROOM
Associating a Program with a Request Group
Submitting the Concurrent Program
(N) Requests > Run

Chapter
CLASSROOM
Summary

Chapter
CLASSROOM


Chapter
CLASSROOM
Chapter 25
Appendix - Incorporating Custom Help Files

Chapter
CLASSROOM
Appendix - Incorporating
Custom Help Files


Chapter
CLASSROOM

Chapter
CLASSROOM
Lesson Aim
Oracle Applications uses an extensive network of help files to give users immediate online
assistance. You can customize these help files by manipulating the files supplied by Oracle, or
by adding your own to the system. This lesson covers how to integrate customized help files
into Oracle Applications.

Chapter
CLASSROOM
Objectives
Overview of Customizing Help Files

In order to customize help files you first must download them into an area for manipulation.
Oracle Applications provides the Help System Utility to download files. Oracle Applications
help files are in HTML format, making them easy to modify using a commercial web
browser/editor such as Netscape Navigator. You can also add HTML and GIF files of your
own.
Oracle Applications help files use a special link syntax that points the links to anchors within
files rather than to the files themselves. This method ensures that hypertext links will not be
broken if files are renamed or split. This lesson explains how to use this syntax, although it is
not required for your custom help files.
When your changes are complete, use the Help System Utility to upload the files back to the
appropriate Oracle Applications directory.
Rebuild the Search Index and use the Help Builder applet to update the navigation tree with
your new files.

Chapter
CLASSROOM
Customizing Help
Oracle Applications Help System Utility

Chapter
CLASSROOM
Set Profile Options

Before using the Help System Utility you must define the upload and download directory
paths. Oracle Applications provides profile options for you to set these paths.
Use the profile option Help Utility Download Path to define the directory location to which
the Help System Utility will download files.
Use the Help Utility Upload Path to define the directory location from which your
customized files will be transferred back into the Oracle Applications Help System.

Chapter
CLASSROOM
Help System Utility Setup: Define Directory Paths
Downloading Help Files

Chapter
CLASSROOM
Identify Help Files

Help files are downloaded by file name. To identify the specific file that you want to
customize, open the document in the Oracle Applications Help System. Use the view source
function of your browser to view the HTML source code. The source information will include
the file name.
For example, the topic Downloading and Uploading Help Files in the help system is found
by navigating from the Help Library Tree to Applied Technology > Oracle Applications
System Administration > Configuration > Customizing Help > Downloading and Uploading.
View the source of this file and you will see the following header comments:

As you can see in the example, the file name is SYS00032663.htm.

Chapter
CLASSROOM
Identify Help Files for Customization
Identify the Language and Product of the Help Files

To identify the language and product of the help file, use the source document URL. The
source document URL contains the language, the product name, and the anchor or target name.
Using this help file as an example again, the URL contains the string
OA_HTML/help/topics/iHelp/HelpServlet/US/FND/@ht_updown.
The nodes in the above string identify the language as US, the product name as FND, and the
target name as ht_updown.

Chapter
CLASSROOM
Identify the Language and Product of the Files
Downloading Help Files for Editing

To download files, use the Oracle Applications Help Administration page for the Help System
Utility. You can access it from the System Administration responsibility: Select Help
Download under Help Administration. The File Download page appears.
Follow these steps to download a single help file:
1. Select Single File Download.
2. Enter search criteria for the file you want.
3. Select the file you want from the search results, and select Download.
Follow these steps to download multiple help files:
1. Select Bulk Files Download.
2. Enter in the Target Directory and Filter Options as appropriate.
3. Select Download.

Chapter
CLASSROOM
Downloading Help Files for Editing
Oracle Applications Special Link Syntax: Overview

The Oracle Applications help system supports a special syntax for hypertext links that keeps
them working even when files are renamed or split into parts.
Links in Oracle Applications help files point at a named anchor contained in the file rather than
the filename itself. The help system resolves the anchorname to file link dynamically, every
time a link is negotiated.
Information on which files contain which anchornames is put into the help system
automatically on upload. Authors must ensure that anchornames are unique across an
applications help files to prevent duplicate links.
It is not required that you use Oracles special syntax for your custom help files. If you prefer,
you can always use conventional hypertext links based on filename.

Chapter
CLASSROOM
Linking Help Files
Using the Special Syntax

The conventional HTML example would allow the user to jump forward to a section with the
anchorname widgets.
Oracle Applications help files extend this HTML syntax to create links not only within, but
also between help files.
To link to a file that contains a particular named anchor, you simply place an @ before the
anchorname. To link to the precise spot within the file where the anchor appears, you append a
pound sign followed by the anchorname, just as you would in conventional HTML.

Chapter
CLASSROOM
Special Syntax versus Conventional HTML
Using the Special Links Syntax Across Applications

In the Oracle Applications help system, all help files associated with a particular application
exist in the same directory, as far as their URL is concerned. Help files associated with other
applications exist in directories named after the applications short name. All these application
directories are at the same level in the help system.
To create a link that goes to a help file associated with a different application, you create a
relative link that goes up a level to the parent of all help application directories, and then back
down through the other applications directory, before concluding with Oracle Applications
special link syntax.

Chapter
CLASSROOM
Cross-Application Links
Related Topics Links

Links are not limited to a single target in the Oracle Applications help system. You can point
your links at multiple topics and files by using Related Topics links.
When a user negotiates a Related Topics link, a page headed Related Topics appears
containing a list of the related page links.

Chapter
CLASSROOM
Related Topics Links
Related Topics Links Syntax

Chapter
CLASSROOM
Note
If you have created a new application with new help files that you are uploading for the first
time, you must use the Generic File Manager Access Utility (FNDGFU) to upload these files.
See (Help) Applied Technology > Oracle Applications System Administration > Configuration
> Loaders > Generic File Manage Access Utility for additional information.

Chapter
CLASSROOM
Uploading Your New or Changed Help Files
File Upload Steps

There are four types of files that you would generally upload to the help system. These are:
HTML files (all HTML files must have a .htm extension)
GIF graphics files (must have a .gif extension)
Adobe Acrobat Files (must have a .pdf extension)
Cascading Style Sheets (must have a .css extension)
Follow these steps to upload a single customized help file:
1. Place the customized file in a location accessible from your desktop.
2. Navigate to the Help Upload page of the Help System Utility. From the System
Administration responsibility, select Help Upload under Help Administration. The File
Upload page appears.
3. Specify the file to upload.
4. Specify the application to which it belongs, and its customization level (typically 100 or
above, indicating it is a customized file).
5. Select Upload.
Follow these steps to upload multiple help files (bulk upload):

Chapter
CLASSROOM
File Upload Steps

Chapter
CLASSROOM
1. Copy the customized files to the appropriate product folder in the upload directory.
For example, if you customized six help files for Accounts Receivable, copy the six files
to the <server location><Help Utility Upload Path>\US\AR directory. You must
copy the files to the correct product folder for the Oracle Applications Help System
Utility to place the files in the correct location within the Oracle Applications Help
System.
2. Navigate to the Help Upload page of the Help System Utility. From the System
Administration responsibility, select Help Upload under Help Administration. The File
Upload page appears.
3. Specify the Source Directory for the files.
4. Specify the application and the customization level (typically 100 or above, indicating
these are customized files).
5. Select Upload.
The Help Utility uploads the help files for the application you selected. All files located in
the directory for the selected language and application will be uploaded.
Updating the Search Index

Chapter
CLASSROOM
Creating Reports

Chapter
CLASSROOM
Running Reports

Chapter
CLASSROOM
Customizing Help Navigation Trees

Chapter
CLASSROOM
Help Builder
To access the Help Builder, you can use the System Administration responsibility and select
Help Builder under Help Administration.

Chapter
CLASSROOM
Help Builder Functions
The Help Builder User Interface

The Help Builder window default view consists of three panes. The left pane displays the tree
that is currently selected. Use this area to manipulate your tree by adding nodes, deleting
nodes, and dragging nodes into the positions desired.
The top right pane displays items matching the searches you have performed using the Find
Documents or Find Trees functions. Switch from the Trees to the Documents display by
clicking on the tabs.
The bottom right pane is the Properties Pane. This area displays the properties of the item
(root, node, or document) currently selected. Those properties displaying enabled fields can be
updated.

Chapter
CLASSROOM
The Help Builder
Opening a Tree for Editing

Chapter
CLASSROOM
Adding New Help Files to a Tree

Documents are listed by target name. Therefore if a file contains multiple targets the file will
be listed multiple times. Be sure to choose the target or anchorname that corresponds to the
topic you want to add.
If the topic you want to add is not the header target of the file, but a target within the
document, you must supply the special link syntax in the Data field of the Properties Pane.
For example, the target name might appear in the Data field as @ht_updown. To link directly
to this anchor from the tree you will add #ht_updown to the end of the anchorname. The
resulting entry in the Data filed will be @ht_updown#ht_updown.

Chapter
CLASSROOM
Adding New Help Files to a Tree
Adding New Nodes to a Tree

Chapter
CLASSROOM
For Further Information

Chapter
CLASSROOM
Summary

Chapter
CLASSROOM

Oracle Apps System Admin Student Guide2

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Oracle Apps System Admin Student Guide2

Hochgeladen von

Copyright:

Verfügbare Formate

Volume 2 - Student Guide

Oracle University and Egabi Solutions use only

R12 Oracle Applications System

Copyright 1996, 2007, Oracle. All rights reserved.

Oracle University and Egabi Solutions use only

U.S. GOVERNMENT RIGHTS

Introduction to Oracle Applications Security ...............................................................................................2-1

R12 System Administrator Fundamentals Table of Contents

Oracle University and Egabi Solutions use only

Introduction to Oracle User Management ....................................................................................................5-1

R12 System Administrator Fundamentals Table of Contents

Oracle University and Egabi Solutions use only

Data Security Components - Objects.............................................................................................................4-7

Profile Options .................................................................................................................................................7-1

R12 System Administrator Fundamentals Table of Contents

Oracle University and Egabi Solutions use only

Delegated Administration vs. Traditional System Administration ................................................................6-39

R12 System Administrator Fundamentals Table of Contents

Oracle University and Egabi Solutions use only

Identify Tables and Columns to Audit...........................................................................................................8-18

Diagnostics and Troubleshooting with Oracle Applications Manager .......................................................12-1

R12 System Administrator Fundamentals Table of Contents

Oracle University and Egabi Solutions use only

Business Flows ..............................................................................................................................................11-20

Administering Concurrent Managers............................................................................................................14-1

R12 System Administrator Fundamentals Table of Contents

Oracle University and Egabi Solutions use only

Introduction to Oracle Workflow ..................................................................................................................15-1

R12 System Administrator Fundamentals Table of Contents

Oracle University and Egabi Solutions use only

Overview of Flexfields .....................................................................................................................................18-1

R12 System Administrator Fundamentals Table of Contents

Oracle University and Egabi Solutions use only

Step 4 Checking Database Parameters...........................................................................................................17-19

Defining Descriptive Flexfields .......................................................................................................................20-1

R12 System Administrator Fundamentals Table of Contents

Oracle University and Egabi Solutions use only

Translatable Dependent Value Sets ...............................................................................................................19-16

Defining Key Flexfields ...................................................................................................................................21-1

R12 System Administrator Fundamentals Table of Contents

Oracle University and Egabi Solutions use only

Specifying the Context Field Information .....................................................................................................20-34

Using Advanced Validation Capabilities .......................................................................................................22-1

Copyright Oracle Corporation, 2006. All rights reserved.

R12 System Administrator Fundamentals Table of Contents

Oracle University and Egabi Solutions use only

Preparing for Cross-Validation......................................................................................................................21-46

Appendix - Incorporating Custom Help Files ...............................................................................................25-1

R12 System Administrator Fundamentals Table of Contents

Oracle University and Egabi Solutions use only

Appendix - Incorporating a Custom Program..............................................................................................24-1

Copyright Oracle Corporation, 2006. All rights reserved.

R12 System Administrator Fundamentals Table of Contents

Oracle University and Egabi Solutions use only

Solution Creating a Role and Placing it in a Role Inheritance Hierarchy...............................................26-40

Oracle University and Egabi Solutions use only

Thorough knowledge of R12 Oracle Applications Navigation

How This Course Is Organized

Copyright Oracle Corporation, 2006. All rights reserved.

R12 System Administrator Fundamentals Table of Contents

Oracle University and Egabi Solutions use only

Oracle Applications System Administrators Guide Security

Oracle Applications System Administrators Guide Configuration