Subject: ECO Workflow Approval Process Setup and Use

Doc ID: Note:104421.1 Type: WHITE PAPER

Last Revision Date: 12-JUN-2006 Status: PUBLISHED

PURPOSE
-------
This document is intended as a technical paper on ECO Workflow setup and use.

SCOPE & APPLICATION

-------------------
This paper covers the basics of using and modifying the ECO Workflow Approval
Process and assumes a basic understanding of the same.

ORACLE ENGINEERING ECO NOTIFICATION APPROVAL PROCESS SETUPS AND REQUIREMENTS

----------------------------------------------------------------------------
I. Table of Contents.

1. Section 1 Introduction
2. Section 2 Setting Up Workflow
3. Section 3 Setting Up the ECO
4. Section 4 Standard Approval Process Flow
5. Section 5 ECO Voting Activity Setup
6. Section 6 ECO Multiple Approval List Setup
7. Section 7 Alerts
8. Section 8 Release 11i(11.5.0) Notes

II. Section 1 - Introduction.

Engineering has an embedded standard Workflow process for ECO approvals that
does not require the installation of the full Oracle Workflow product. Workflow
Builder is required, however, because there is NO seeded default performer for
the ECO standard approval process. The standard Workflow process for ECO
approvals also allows the use of the [Submit] button on the Define ECO Form and
the use of the ECO Notifications "Inbox" Form. This Workflow process allows the
ECO to be sent to an approval list. The approvers have the option to approve or
reject the ECO before implementation.

III. Section 2 - Setting Up Workflow.

Please reference the Workflow 2.0.3 User's Guide Part No: A56104-01 for
more detailed instructions.

1. Update Embedded Workflow to Version 2.0.3.

a. Order the CD, Oracle Workflow Embedded Version 2.0.3 for Oracle
Applications, for Windows 95/Windows NT (Part No. A60742-01 or A34760).
b. You can order this through support on a shipping tar.
c. The Workflow development team will ONLY support version 2.0.3 for
Rel.11.0. and Rel.10.7.16.1
d. Workflow 2.5 is used for Release 11i(11.5.0)
e. The installation instructions are included on the CD readme file.
f. Follow all the installation instructions provided for Workflow.
g. Patch 1036678 is a complete synchronization patch of all Workflow 'C'
code for embedded applications workflow.
2. Setup an e-mail account for the user "Workflow". You can do this in
Unix Sendmail, Oracle Messaging, Oracle InterOffice or a Mapi-compliant
e-mail system. Use the documentation provided with the email system you
are using.

3. Edit the wfmail.cfg file located in the $FND_TOP/resource directory.

Include the following important required fields:

a. CONNECT username/password@<database_connect_string>
b. ACCOUNT - use the following:
1) For MAPI system: username/password
2) For Oracle InterOffice: username/password@<database_connect_string>
3) For Unix Sendmail full path to the OUTGOING mail spool file usually
located in <root> var/mail directory
� Account corresponds to the account from which the Notification Mailer
is started.
� If using Embedded version, this is the account from which you start
the concurrent manager (program).
c. NODE - The computer name from which the Notification Mailer is started.
� If you intend to use the Web part of Notifications, you must also
configure the following in the wfmail.cfg file.

# HTML Web Agent path: (required for mailed html support)

# CHANGE THIS!
HTMLAGENT=http://<your_agent>:<port>/sid/owa

# HTML Attachment file: used as the filename when attachment is saved

HTMLFILE=attach.html

# HTML Attachment desc: description of attachment type

HTMLDESC=HTML

# HTML Attachment type: numeric attachment code (oracle office)

# HTMLTYPE=10003

4. Types of Notification Mailer Programs. The Notification Mailer is a program

that performs e-mail send and response processing for the Oracle Workflow
Notification System.

a. Embedded Workflow.

� WFMAIL
� Is used on Unix platforms.
� Is used for the Embedded versions
� Is submitted using the Concurrent Request Submit Form in Sysadmin.
� Command line syntax: WFMAIL apps/pwd 0 Y <config_file> &

� wfmlr20.exe
� This program is for WINDOWS NT Server Platforms.
� It can be installed from the CD above.
� You can register this program in Oracle Apps.
� This Program must be installed and started from the MAPI
E-mail server.
� Command line syntax: wfmlr20.exe -f <config_file>
� You can start this from an icon with properties set to find the
right wfmail.cfg file.

b. Standalone Workflow.
 � wfmail.snd
� This program is for standalone version using Unix Sendmail

� wfmail.ofc
� This program is for standalone version of Workflow using Oracle
InterOffice.

� The syntax for submitting the programs from the command line is:
� <xxx> where xxx is snd or ofc respectively
� wfmail.<xxx> -f <config_file>

5. Setup the concurrent programs if you are NOT using the MAPI version.

a. Navigate to System Administrator/Security/Responsibility/Requests.

b. In the Group field, query up System Administrator Reports.
c. Scroll down to the bottom and add the following:

� type name application

� Program Notification Mailer Application Object Library
� Program Workflow Resource Generator Application Object Library
� Program Workflow Definitions Loader Application Object Library
� Program Workflow Background Process Application Object Library

d. Save the screen.

6. Create or Edit the resource file wfcfg.msg as follows:

� The wfcfg.msg file is located in the $FND_TOP/resource/<language>

directory for Embedded Workflow.
� This file is needed for two reasons in Embedded Workflow.
� It defines the Workflow Web Agent to use.
� It defines the Workflow Administrator Role.
� Once the file is edited with a. and b. below, it
is necessary to upload the file to the database.

Before installing Workflow, Oracle WebServer must be properly installed

and configured. Once the WebServer is configured, the Oracle Web Agent
that Workflow uses must be identified so workflow can access its Web
Components. Enter that web agent in the wfcfg.msg file as follows:

a. To add the Oracle Web Agent to the wfcfg.msg file:

WFTKN WF_WEB_AGENT 0 <your_web_agent_here>

� <your_web_agent_here> is your base URL of the Oracle Web Agent

defined for Oracle Workflow in Oracle WebServer. The URL should
look something like this:

http://<server.com:port_id/<plsql_agent_virtual_path>

b. To add the Oracle Workflow Administrator Role to the wfcfg.msg file:

WFTKN WF_ADMIN_ROLE 0 <role_name>

� Any user associated with the Admin Role will have Workflow Admin
Privileges.
� If you want all users to have Administrator Privileges, the '*' can be
used as a wildcard to enable all users.
 � Edit the file as follows:

WFTKN WF_ADMIN_ROLE 0 *

c. To generate a binary resource file from a source(.msg) file:

� Run the Resource Generator concurrent program with FILE as the

Destination Type. The Resource Generator program creates a
resource file.
� Command line syntax:

WFRESGEN apps/pwd 0 Y FILE <res_file> <source_file>

d. To upload seed data to the database:

� Run the Resource Generator with DATABASE as the Destination Type.

The Resource Generator Program uploads the seeded data to the
WF_RESOURCE table from the source(.msg) file.
� Command line syntax:

WFRESGEN apps/pwd 0 Y DATABASE <source_file>

� <source_file> should be replaced with:

@<application_short_name:[<dir>/.../]file.ext

7. Submit the concurrent programs only if NOT using the MAPI e-mail system.

a. Navigate to System Administrator/Requests.

b. Click on Run.
c. On the Submit Requests form click the LOV for Name.
d. Notification Mailer should now be in the list, select it.
e. In the Parameters form, enter the directory name where the
wfmail.cfg is located (i.e., c:\wfmail.cfg).
f. Set the resubmit interval to a least every hour or more.
g. Do the same for Workflow background process.
h. Set the ITEM TYPE to ECO Approvals.
k. The book says you should have one background engine for deferred
processing and one background engine for timeout processing.
However, you can, at a minimum, setup one with both.
l. Minimum and maximum thresholds default to 0(zero) and 100 to
include all.

8. Useful Workflow Scripts.

� All scripts below are in the $FND_TOP/sql directory

a. wfstatus.sql -- WorkFlow item STATUS report

� Displays a status report on the indicated item
� Note 1011380.102

b. wfver.sql -- WorkFlow Version display

� Displays version information for all WF source
� Note 1011379.102

c. wfbkgchk.sql -- WorkFlow Background Check

� Displays a status report on background work waiting to be processed
� Note 1011382.102
 d. wfrun.sql -- WorkFlow RUN a process
� Creates and starts the specified process
� Note 1011378.102

e. wfdirchk.sql -- WorkFlow Directory Services Data Model Check

� check directory services data model for all known problems
� Note 1011377.102

f. wfbkg.sql -- WorkFlow Background engine

� starts the background engine, running for the indicated number of
minutes.
� Note 1011381.102

IV. Section 3 - Setting Up Oracle Engineering And The ECO.

1. Create ECO priorities.

2. Create the APPROVAL LIST to include the people in the list or roles for
the standard approval process. This can be any name but must also be
set as the default perfomer in the Workflow Process using Workflow Builder.
If notifications are not sent to the people in the approval lists, you need
Patch 676283 or Patch 866202, both are available for 10.7 and 11.0.
Patch 1036678 (for Release 11) is newer and contains the changes in both
676283 and 866202.

This updates wfmlr.lc and wfntf.lc.

3. Create an ECO TYPE that includes the Standard Approval Process as its process.
Attach the Standard Approval Process for each priority you want to use.

4. When creating the ECO:

a. Pick the ECO TYPE that includes the Standard Approval Process.
b. Pick the Priority attached to the Standard Approval Process when ECO TYPE
was defined.

5. Save the ECO.

6. If all the tables include at least one user and role, the ECO Type is setup
correctly and the ECO uses the ECO Type above, the SUBMIT button will be
"Active".

7. Click the SUBMIT button to submit the ECO to the Standard Approval Process.

a. Once submitted, you cannot change the ECO.

b. You can ABORT the APPROVAL by selecting the SPECIAL Menu option and ABORT
APPROVAL.
c. When you abort, you can then make changes and resubmit.

8. If, after submitting, no one receives a notification, navigate to

Engineering/ECOs/ECOs to see if there is an error.

� Query the ECO.

� Click on the Approvals Button.
� Select the current approval process.
� Click the status button for the current status.
� In the Approvals window, are the following four (4) steps performed
by the Approval Process?
 � Step 1 Approval Process
� Step 2 Start
� Step 3 Get ECO Attributes
� Step 4 Standard Approval Notification

� If the fourth step is in an ERROR status, it will provide the error

message. The messages differ slighltly for 10.7, 11.0, or 11.5
For example, the below error means it tries to submit to no performer
or an invalid performer and fails.

3120: Activity 'ECO_APP/39779' has no performer.

[Error Process Error:3116: Activity 'WFERROR/ENG_ERROR_PROCESS'
is not a runnable process.]

� It could also be that the process is actually "Not Runnable", but this
typically is not the case.

� To resolve the 'No Performer' error, do the following:

� Load Workflow Builder.

� Login to the Database where Workflow is loaded.
� Ignore Effectivity.
� Effectivity defines the Revision Date of the Saved Process in the
Database.
� Workflow Builder does not overwrite older or newer revisions of the
processes stored in the Database.
� You can load versions of the process in to workflow builder that were

effective at particular point in time from the database based on

effectivity.
� Open ECO Approval.
� File/Load Roles from database and select your performer (approval list).
� Click on the + for your database connect string.
� Click on the + for ECO Approval.
� Click on Processes.
� To check if the process is runnable,
� Right click on the Standard Approval Process Icon.
� Select Properties.
� Ensure that the Runnable checkbox is checked.
� Double click on Standard Approval Process.
� In the Process Window, right click on the icon for standard approval
(i.e., the one in the middle that shoots off into two different
directions).
� Click on Properties.
� At the bottom of the form, view what is in the Performer Area (zone).
� Set the Default Performer to your approval list.
� If no roles appear in the List Box, Load/Create the Roles as per above.
� A Role/Performer is a:
� Responsibility.
� Valid person in HR/Engineering/Inventory.
� Approval List.
� Save the change back to the database that you connected to.
� Run the ECO Approval Process again.

V. Section 4 - The Standard Approval Process Flow.

The package ENG_WORKFLOW_API_PKG contains the procedures and functions for the
ECO Approval Workflow and is created by file engwkfwb.pls. The ECO Approval
Workflow Notification Process that is seeded in Release 11 Embedded Oracle
Applications does the following:

Function Description
--------------------------------------------------------------------------
Start * Mark start of process.

Get ECO Attributes * This activity sets pre-defined ECO attributes that
can be used by this item type. This activity is
seeded by the Oracle Engineering product.
* Gets the data from Eng_Engineering_Changes for the
ECO Number(Change_Notice), Organization Id(Org_id).

Standard Approval * This is the standard ECO Approval Notification

seeded for the Oracle Engineering product.
* Sends the Notification with the ECO Attributes
collected above to the individuals in the Approval
List using Workflow Notification Mailer.
If Approved,
* Set MRP to Active * This function sets MRP Active to "Yes" for all
"Open" or "Scheduled" revised items belonging to
the ECO.
* Updates Mrp_Active to 1 (Yes) in Eng_Revised_Items
for Change_Notice, Org_Id and having a Status_Type
of 1 (Open) or 4 (Scheduled).
* Approve ECO * This function sets the ECO's Approval Status to
"Approved", sets the Approval Date to the current
date and sets all "Open" revised items belonging to
this ECO to "Scheduled".
* Updates Approval_Status_Type to 5 (Approved) and
Approve_Date to Sysdate in Eng_Engineering Changes
table for Change_Notice, Org_Id.
* Updates Status_Type = 4(Scheduled)
Eng_Revised_Items table for Change_Notice, Org_Id.
End * Marks the end of the process.

If Rejected,
* Set MRP to Inactive * This function sets MRP Active to "No" for all "Open"
or "Scheduled" revised items belonging to the ECO.
* Updates Mrp_Active to 2 (No) in Eng_Revised_Items
for Change_Notice, Org_Id and having a status_type
of 1 (Open) or 4 (Scheduled).
* Reject ECO * This function sets the ECO's Approval Status
to "Rejected" and clears out the Approval Date.
* Updates Approval_Status_Type to 4 (Rejected) and
Approval_Date to NULL in Eng_Engineering_Changes
for Change_Notice, Org_Id.
End * Marks the end of the process.

VI. Section 5 - Setting Up the ECO Approval Voting Activity.

1. The default setup of the ECO Notification and Approval Process, when
setup properly, allows the first of the approvers who sends a response
to approve or reject the ECO. All other responses are ignored.

2. To allow all approvers to approve the ECO before it is implemented, the

Embedded Workflow Process "ECO Approval" must be altered using Workflow
 Builder. The ECO Standard Approval Process must be copied, renamed and
edited to replace the Notification Standard Approval Notification Activity
with a Notification Voting Activity. The creation of the ECO Vote
Approve/Reject
Notification Process is described below.

3. The voting activity can be setup using any of six different or customized
voting methods as described in the On-Line Help in Workflow Builder. Search

on Voting Activity. These are some of the various methods described:

a. Simple Majority:
Vote Approve: 50%
Vote Reject: 50%
� If either Approve or Reject get more than 50% of the vote,
then it is the result.

b. Simple Majority with Default:

Vote Approve: 50%
Vote Reject: <blank>
� If Approve does not get more than 50% of the vote,
then Reject is the result.

c. Popularity:
Both Vote Approve and Vote Reject are NULL<blank>.
� The response with the most votes is the result.

d. Black Ball:
Vote Approve: 100%
Vote Reject: <blank>
� Any Vote for Reject is a result of Reject.

e. Jury:
Vote Approve: 100%
Vote Reject: 100%
� All must vote the same to get that result.

4. Setup the above voting methods as described below in No.5 step d.

5. The Vote Approve/Reject Voting Activity requires the following setup:

a. Lookup Types
b. Messages
c. Notification
d. Workflow Process

When you connect and load your ECO Approval Process in Workflow Builder,
save that definition to a file on your PC before you start to edit the
process. You then have a backup if it is ruined in testing. It can be
reloaded from a CD but why go to that trouble.

a) Lookup Types.
1) Create or review Lookup Types.
2) Review Seeded Approvals Lookup Types.
� ECO Approval (This is the seeded lookup type)
� Internal Name: ECO_Approval
� Add the following attributes.
� Percent Approve
� Internal Name: 5
 � Percent Reject
� Internal Name: 4
3) Create New Voting Options Lookup Type.
� ECO Voting Options (Create New)
� Internal Name: WFECO_VOTING_OPTION
� Add the following Lookup Codes.
� Require All Votes
� Internal Name: REQUIRE_ALL_VOTES
� Tally On Every Vote
� Internal Name: TALLY_ON_EVERY_VOTE
� Wait For All Votes
� Internal Name: WAIT_FOR_ALL_VOTES

b) Messages.
1) Use the Seeded Default STANDARD_APPROVAL_MESSAGE
� Do not create a new message
� Use the seeded message
� It works with the Voting Activity.

c) Notification.
1) Create a New Notification.
� Voting Approval Notification
� Internal Name: VOTEFORRESULTTYPE
� Display Name: Vote Approve/Reject
� Description: Vote for Approve/Reject Result Type

� Function: WF_STANDARD.VOTEFORRESULTTYPE

� Note: The Function field only shows when Expand Roles is

checked.
� After Expand Roles is checked, you can enter the Function Name.
� Result Type: ECO Approval
� Message: Default Voting Message Approval/Reject
� Expand Roles: Checked
� Icon: MEET.ico
� Attributes:
* Percent Approve: The Internal Name here must match the
internal
name of the Seeded ECO Approval Lookup Types
Attributes: Approve or Reject
� Internal Name: 5
� Type: Number

* Voting Option
� Internal Name: VOTING_OPTION
� Type: Lookup
� Lookup Type: ECO Voting Options
� Default Value: Constant - Require All Votes

* Percent Reject: The Internal Name here must match the

internal
name of the Seeded ECO Approval Lookup Types
Attributes: Approve or Reject
� Internal Name: 4
� Type: Number

After completing testing with the above setup, if you get the
errors listed below, then you have incorrectly specified the
lookup codes and the voting activity attributes' internal names.
 3109: Attribute '4' does not exist for activity '119' in
item 'ECO_APP/EC68044-511-1'.
[Error Process Error: 3116: Activity 'WFERROR/
ENG_ERROR_PROCESS' is not a runnable process.]

Note: The Internal Names *MUST* match the internal names of

the Seeded ECO Approval Lookup Types Attributes: Approve and
Reject respectively.

d) Workflow Process.
1) Copy the Standard Approval Process and name it Voting Approval
Process.
2) In the Voting Approval Process Graphics Window:
� Replace the Standard Approval Notification with the newly
created Vote Approve/Reject Notification.
� Navigate to ECO Approval Processes in the Navigator.
� Double click on Voting Approval Process. This should pop up
the Workflow Process Graphic Display window. In that window:
� Delete the ICON in the middle with the 2 arrows Marked
Approve and Reject (it looks like an envelope).
� Navigate back to the ECO Approval- Notifications.
� Expand the Notifications icon.
� Drag and drop the Vote Approve/Reject Notification icon into
the graphic window where the old one used to be: CONSTANT
� Constant as "Performer" resolves to WF_ROLES.DISPLAY_NAME
� Performer: <Your Approval List or Role> (i.e., XX-ECOList1
or Standard, etc.).
� To setup the Black Ball Voting Method mentioned above, on the
Attribute Values Tab:
� Select Vote Approve
� Enter: 100
� Select Voting Option
� Select Require All Votes in the Drop-down List
� Select Vote Reject
� leave <blank>
� Right Click and drag from the starting icon to the Vote
Approve/Reject icon. This creates the transition link.
� Right Click and drag from the Vote Approve/Reject icon to the
top right icon (the set MRP to Active function).
� When you release the mouse button, it allows you to select
Approve or
Reject.
� Select Approve.
� Right Click and drag from the Vote Approve/Reject icon to the
bottom right icon (the set MRP to inactive function).
� Select Reject.
� Save your changes to a File on your Client PC.
� Save your changes to the Database.
� Start Your new ECO Approval Process from the applications.

VII. Section 6 - ECO Multiple Approval List Setup.

A user asked how to use more than one approval list for the ECO Approval
Standard Approval Process Embedded for use with Oracle Engineering if they seed
the default performer to the ONE performer (i.e., go to Workflow builder, open
the process, and set the default performer to your approval list name).
This only allows that ECO Approval Standard Approval Process to send
Notifications to ONE list as described earlier in this document. The basics of
that
process are documented below.

1. Open the Workflow Builder.

a. Log in to the database where Workflow is loaded. Ignore effectivity.

� Effectivity defines the revision date of the saved process in the
database.
� Workflow Builder does not overwrite older or newer revisions of the
processes stored in the database.
� You can load versions of the process in to workflow builder that were
effective at a particular point in time from the database based on
Effectivity.
b. Open ECO Approval.
c. File/Load Roles from database.
d. Click on the + for your database connect string.
e. Click on the + for ECO Approval.
f. Click on Processes.
g. Click on Standard Approval Process.
h. In the Process window, right click on the icon for Standard Approval
(i.e., the one in the middle that shoots off into two different
directions).
i. Click on Properties.
j. At the bottom of the form, view what is in the Performer zone.
k. Set the Type to Item Attribute.
� Item Attribute as a "Performer" resolves to WF_ROLES.NAME
l. Set the Default Performer to Attribute1 (or 2-15 if already using
Attribute1).
� The Attributes 1-15 are the respective Descriptive Flexfield Columns
in the ENGFDECN form and ENG_ENGINEERING_CHANGES table.
� The performer is the Approval List Name. A Performer is a:
� Responsibility
� Valid person in HR/Engineering/Inventory
� Approval List
� Role
m. Save the change back to the database that you connected to.
n. Setup a Descriptive Flexfield in the Form to enter the Approval List
Name into the column "Attribute1" in the ENG_ENGINEERING_CHANGES table
when we save the ECO.

2. Navigate to Flexfields/Descriptive/Segments from any responsibility that

has it, usually System Administrator.

a. Click the Find (flashlight) on the Menu Bar.

b. Enter %Engineer% in the Find Field.
c. Click the [Find] button.
d. Select Change Order Information from the List.
e. Uncheck the Freeze Flexfield Definition checkbox.
f. Click in the Global Data Elements field.
g. Click on the [Segments] button at the bottom of the screen.
� Number: 1
� Name: Anything you like(i.e. Approval List)
� Window Prompt: Defaults to data entered in Name field.
� Column: Select ATTRIBUTE1 from LOV.
� Value Set: <any name you like> (ie. ECO_MULTI_APRPROVAL_
LISTS)
h. Create a new value set as follows:
� Value Set Name: EE_Multi_Approval_Lists
 � Format Type: Char
� Max Length: 100
� Validation Type: Table
� Click on the [Edit Information] button.
� Table Application: Applications Objects Library
� Table Name: WF_ROLES
� Ensure the check box for Allow Parent Values is UNchecked
� Value: NAME Type: Varchar2 Size: 40
� Meaning: DISPLAY_NAME Type: Varchar2 Size: 40
� ID: Leave Blank
� Where/Order by Clause: enter the following:

Where wf_roles.orig_system='ENG_LIST'

i. SAVE.
j. Close all windows back to the first flexfield window.
k. Check the checkbox for Freeze Flexfield Definition
l. Click the Compile Button.
m. Close the Form.
n. Create an ECO selecting all necessary data to submit to ECO approval
as described earlier.
o. Select the descriptive flexfield.
p. Select the Approval List you want to use and save your ECO.
q. Submit. The Workflow process should find the value in the column
ATTRIBUTE1, resolve the value to what is in the WF_ROLES.NAME field, and
use it for the default Performer.

The above Multi-Approval List flexfield setup works. There is at least one
other method available to use multiple approval list.

1. Copy the Standard Approval Process as many times as you have lists to use.
a. Seed the Approval lists, one to each copy.
b. Save the ECO Approval back to the database.
c. Create an ECO Change Type for each of those newly added processes and
attach the new process using the [Process] button.
d. When you create an ECO and want to use a different approval process,
select that ECO Change Type that is using the process in which you
seeded the Performers.

2. This method is currently untested and requires more maintenance when list
names change.

VIII. Section 7 - Setting Up ECO Alerts.

Alerts can be used as an alternate form of notification and are setup as shown
below. Alternately, the following Alerts can be setup in Alert Manager to
receive e-mail notifications:

� ECO Approval Alert

� ECO Implementation Alert
� Both need to be set as EVENT ALERT
� Application: Oracle Engineering
� Table: ENG_ENGINEERING_CHANGES
� Before Insert: Checked
� After Insert: Checked
� Verify that ALECTC is setup properly in the Sysadmin/Concurrent/Program/
Executable. This is the Check Event Alert Program.
� If the Event Alerts do not work in a Multi Org Environment, apply
 Patch #439908 for 10.7.
� OR
� If set up as PERIODIC ALERTS, the Periodic Alert Scheduler concurrent
program must be running.
� There is a bug for Periodic Alerts in a multi-organizational environment.

IX. Section 8 - Release 11i (11.5.0) notes.

� Release 11i uses Workflow 2.5
� Please download appropriate Workflow version 2.5 for use with
all Release 11i Workflows.
� ECO Approval may have different error messages for the same errors, as
in previous releases.
� The Voting Activity is seeded with Release 11i Eco Approval Item Type.
� The Multiple Approval Lists functionality is still a customization as
documented above.
� Otherwise, it should function the same as previous releases.

1. Current Engineering Workflow related patches/bugs for Release 11i.

a. If you receive the following error, apply the latest Engineering

patchset 11.5.2 to update the files listed below:

� Upon pressing the [Submit] button, you get:

ERROR: The approval status type 3 is invalid for ECO (the ECO you
created)since it has a workflow process associated with it.

b. Patch 1337625 corrects the issue. It updates files:

eng 11.5 forms/US ENGFDECN.fmb 115.104

resource ENGFMECO.pld 115.19
patch/115/sql ENGLECOB.pls 115.34
patch/115/sql ENGDECOB.pls 115.19
patch/115/sql ENGVECOB.pls 115.66

@ Reference Bugs 1337625 and 1325563.

2. Ensure Workflow Monitor is correctly setup and functional.

� To get the Approval status, the Workflow Monitor is called when the [Status]
button
is pressed.

RELATED DOCUMENTS
-----------------
� Reference Article-ID: Note 62094.1 Workflow Description, Installation, and
Configuration.
� This article has very good information related to Workflow Specific
Setup issues. It is specific