Designing New Processes - Process Flow or Custom MO?

From time to time implementation/project teams will need to support business processes that are not provided by the base product. PSRM provides 2 main options for implementing custom business processes, Process Flows and custom Maintenance Objects (MOs).

Process flow provides some functionality out of the box to make configuration of new processes easy, such as logs, monitor batch processes, and query and maintenance portals.  As Process Flow is generic, it will behave generically in some ways, including:

  • Design Approach:  Characteristics and CLOB fields will be used for things that otherwise may be captured in distinct fields and/or tables.  This is true for what is implemented initially, and any enhancements needed in the future.
  • Performance:  Indexes for all instances of an object will be defined on the same table, possibly affecting insert/update/delete performance.
  • Maintenance:  Different objects would have different lifecycles and should be handled differently for Information Lifecycle Management (ILM) or other maintenance processes.

Maintenance objects will require more effort to implement but allow built-for-purpose lifecycles and user interface (UI) hints for simplified UI map development effort. Using a maintenance object will give implementation teams control over how tables and fields are defined in the database. A custom MO is recommended for high volume entities that justify the additional effort while Process Flow is preferred for lower volume, lower complexity functions.

  • Design Approach:  Distinct fields and/ or tables will be used for specific data elements. 
  • Performance:  Indexes can be designed for the specific uses of the MO. 
  • Maintenance:  The BO’s lifecycle can be used Information Lifecycle Management (ILM) or other maintenance processes.

The effort required to implement business objects including schema definitions, UI maps, and processing logic is the same whether using Process Flow or custom Maintenance Objects to implement custom business processes. Implementation teams should consider the time they have available to design and implement the business process, the complexity of the requirements and propensity for future changes or similar requirements when deciding to use Process Flow or custom Maintenance Objects.

Comments:

Post a Comment:
  • HTML Syntax: NOT allowed
About

This blog is for our Oracle Public Sector Revenue Management customers, delivery partners, and even our fellow Oracle professionals, and is dedicated to all things Oracle Tax and Revenue Management. We will focus on support and implementation tips, announcements, and FAQs (frequently asked questions) for all of our Oracle Public Sector Revenue Management products. This include Oracle Public Sector Revenue Management (PSRM), Oracle Tax Analytics, and our Oracle PSRM Self Service and integration products.

Search

Categories
Archives
« April 2014
SunMonTueWedThuFriSat
  
1
3
4
5
6
7
9
11
12
13
14
15
16
17
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today