Please click to proceed.

Understanding Customization Preservation Concepts in Oracle Workflows

In this presentation, you will learn How Oracle protects/discourages some key business critical Activities/Processes from being modified How you can preserve the customizations from patching Understand the internals of Workflow Preservation Concepts Different modes of Workflow Upload

Best practices in EBS From Anil Passi

Workflow Access/Protection Level Concepts

The access levels are defined as follows: 0-9: Reserved for Oracle Workflow 10-19: Reserved for Oracle Application Object Library 20-99: Reserved for Oracle E-Business Suite 100-999: Reserved for customer organizations 1000: Public How does the developer define their Access Level?

Best practices in EBS From Anil Passi

Example- How Oracle protects their Objects from Modifications

Developer in Oracle Corp
Via help Menu, developer in Oracle Corp will set Access Level to 20

Developer at EBS Customer Site

Oracle locks the access at level their level to discourage customers altering critical parts of the flow. To modify such items, you will have to change your access level to lower than 20, so that it fits into the range of 0..20. However altering key parts of the workflow process is not recommended.
Access[100] is not between range 0 and 20. Hence Customer Site can not modify this activity

Oracle developer locks the object at this access level

Best practices in EBS From Anil Passi

Next Scenario- How Oracle protects their Objects from Modifications

Developer in Oracle Corp
Via help Menu, developer in Oracle Corp will set Access Level to 20

Developer at EBS Customer Site

Oracle developer unchecks Lock at this access level, then Protection becomes 1000

Best practices in EBS From Anil Passi

Example- How Oracle protects their Objects from Modifications

Developer in Oracle Corp [Access Level 20]
20 is not between 100-100 or 100-1000. Hence Oracles patch can not modify/remove your customization. CUSTOMIZATION IS PRESERVED Developer at EBS Customer Site Modifies the Workflow at the Access Level 100

However by checking Allow Modifications to customized obj, Oracle will is able to modify the Customized objects

Best practices in EBS From Anil Passi

How Oracle delivers Workflow patches

Oracle delivers workflows via patches which use WFLOAD command to upload their definition to the Database
WFLOAD apps/$APPS_PWD 0 Y <UPLOAD_MODE> XX.wft

Different Upload Modes applicable to WFLOAD

UPGRADE Honours both protection and customization levels of data UPLOAD - Honours only protection level of data [No respect of Customization Level] FORCE - Force upload regardless of protection or customization level

Equivalent to

As a standard practice, Oracles upgrade patches mostly run in UPGRADE mode, hence your customizations can protected if best practices for development are followed.
Best practices in EBS From Anil Passi

Thanks
Anil Passi

Best practices in EBS From Anil Passi