Professional Documents
Culture Documents
Work Flow Key Points
Work Flow Key Points
Objectives
Understand Environment required to run Workflow in Oracle E-Business Suite Understand
steps required to setup Workflow
Gain familiarity with setup screens
Check Business Event System setup
Check Notification Mailer setup
Server Side
E-Business Suite 11.5.9 or 11.5.10
OAM Oracle Applications Manager
GSM Generic Services Manager
To View Notifications
Web browser that supports JavaScript and Frames
To View Monitor
Web browser that supports
JDK 1.1.8 or higher
Abstract Windowing Toolkit (AWT)
1
Add Notification Rules (user mode /admin mode) to responsibilities (11.5.9)
Customize company logo on Workflow web pages
Include additional icons for Builder
2
Required Directory Services
WF_USERS, WF_ROLES, WF_USER_ROLES views across WF_LOCAL_ROLES,
WF_LOCAL_USER_ROLES
WF_LOCAL_ROLES, WF_LOCAL_USER_ROLES populated by Directory sync programs or
(with added patches) directly as change is made
WF_LOCAL_USERS obsolete
Rows in WF_USERS w/o corresponding row in WF_ROLES
Invalid internal names in WF_ROLES Contain #, / or length > 30
Invalid user/role foreign key in WF_USER_ROLES
Missing user/role in WF_USER_ROLES (every user must participate in own role)
Duplicate rows in WF_USER_ROLES
3
Schedule Background Engines
Required Start Background Engine(s)
Required to have minimum of one
Can start Engines through concurrent manager (much easier) or through OAM
Enter parameters
Process Deferred, Process Timeout, and Process Stuck are Yes/No parameters
Schedule to repeat
How often depends on options specified
4
Clicking Advanced Schedule allows many more options
Summary page shows all options specified , Click Submit to start the process
5
Start Listeners
If status is Deactivated, click Start for Workflow Agent Listener Service and (if using mailer)
for Workflow Mailer Service
Starts concurrent managers (containers)
Verify Status
Workflow Components
Migrating Changes
Migrate using Workflow Builder
Open workflow using Workflow Builder from Source System
Save workflow using Workflow Builder to Destination System
Open Destination System using Workflow Builder to validate
Migrate using FND tool
On Source System Server
Set ORACLE_SID and environment to point to Source System
WFLOAD apps/<apps pwd> 0 Y DOWNLOAD <file.wft> <item type>
Transfer <file.wft> to Destination System Server
On Destination System Server
Set ORACLE_SID and environment to point to Desitnation System
WFLOAD apps/<apps pwd> 0 Y UPLOAD <file.wft> <item type>
Workflow Tables
Making Changes to WF
Only modify workflow objects with a protection level greater than 100
Always refer to the product-specific User Guide or Documentation Update
Do not change Oracles PL/SQL, copy it and create a custom procedure of your own
Research all the places a WF process is referenced, they are often nested
Have at least one Workflow Background process running under the concurrent manager without an
Item Type specified, with Process Deferred and Timeout set to Yes, and with a frequency of at least
once a day.
Watch out for objects which dont support versioning. Changes made to these objects may cause
existing Workflow processes to error out.
Attributes
Messages
Lookup Types
8
Use object versioning to see if an object has been modified by a patch.
The version increments by one each time the object is changed and saved to the database.
You can create a simple message body with the attributes of interest, link it to a notification, and
place it in your workflow to see what is happening at a particular place in the workflow process.
This is especially helpful in a complex workflow with Attributes states changing or in doubt.
9
Resend notifications.
This makes searching for customizations at the table level much easier.
Workflow Notifications
Notification Components
Notifications are comprised of:
- A Notification Activity
- A Message
- A Message Template
Optional Message Item Attribute(s)
Notification Activity
Think of this as a container to hold and call the message from.
This is what you will place on your workflow diagram.
When inserting a Notification Activity on a workflow diagram remember to provide a value for
the Performer. If you dont you will get a workflow runtime error about a NULL Performer.
11
Message
This is what contains the text you are going to send.
You can format messages at Text or HTML
Message Bodies can include Attributes (variables)
Message Attributes
Message Attributes allow you to modify features of a Workflow Notification, without having to
create separate Workflow Mailers.
There are dozens of Special Message Attributes. I am only showing two here.
#WFM_FROM Changes the From Email address
#WFM_REPLYTO Changes the Reply To Email
12
p_document := NL || '<P><B>';
p_document := p_document || 'Employee Table';
p_document := p_document || '</B>';
p_document := p_document || '<TABLE border=1 cellpadding=2 cellspacing=1>';
p_document := p_document || '<TR>' || NL;
p_document := p_document || '<TH>' || 'EMPNO' || '</TH>';
p_document := p_document || '<TH>' || 'ENAME' || '</TH>';
p_document := p_document || '<TH>' || 'JOB' || '</TH>';
p_document := p_document || '</TR>' || NL;
Access Level Level you use in the Workflow Builder or Workflow Definitions Loader
Protection Level Level assigned to objects created in the Workflow Builder
Customization Level Level that objects can only be further customized
All levels are represented by an integer from 0-1000
13
Preserve Customizations check box Locks customized object from being overwritten during
a workflow definition upgrade
Lock at this Level Protect the object at the current access level and do not allow the object
to be customized
Object Levels
Selected Check Box Object may be updated by
Saved
Customization = 0 Any access level (0-1000)
None Access = 100
Protection = 1000
Customization = 100 Access level (100-1000)
Allow modifications to customized object
Preserve Customizations Access = 100 check box, customized objects can be
changed by access levels (0-99)
Protection = 1000
Customization = 100 Access level (0-100)
Lock at this Access Level Access = 100
Protection = 100
Customization = 100 Access level (100)
Allow modifications to customized object
Both Access = 100 check box, customized objects can be
changed by access levels (0-99)
Protection = 100
14
Oracle uses access protection to allow or discourage customers to modify certain key Activities
All workflow objects except lookup codes, function attributes, and message attributes contain an
Access tab in their property pages. Lookup codes, function attributes, and message attributes
inherit their access settings from their parent lookup type, function, or message, respectively.
Protection Levels
Objects protected against customizations are considered seed data.
Only users operating at an access level equal to or lower than the protection level of the object
can modify the object.
Users operating at an access level greater than the protection level of the object will see a small
lock on the icon for the object in the navigator tree, indicating that the object is read-only.
Customization Levels
If you set an object to be customizable, its protection level is set to 1000.
A customized object is locked from further modification except from users with access levels
equal to the customization level of the object.
15
16
17