Account Generator Process Diagram
A basic Account Generator process contains the following function activities, in the order:
- Functions to generate the code combination, for example, Assign Value to Segment, as well as functions to check if the code combination is complete. Some of these functions may be product-specific
- Validate Code Combination function
Oracle provides standard Account Generator process function activities that are described later in this chapter, in addition to standard Workflow activities described in the Oracle Workflow Guide. Each product's Account Generator process may also include additional product-specific functions. See your Oracle [Product] User's Guide for details on a particular process.
In addition, a process may contain process activities (subprocesses). For example, the following Account Generator top-level process contains three process activities: Generate Book Level Accounts, Generate Category Level Accounts, and Generate Asset Level Accounts.
Each of the three subprocesses has its own diagram. For example, the Generate Category Accounts process diagram is shown below:
Here, the main process contains the activities Start Generating Code Combination, Validate Code Combination, and End Generating Code Combination. The subprocess contains the activities that actually build the combination. The activities of the subprocess are as follows:
- Start: every process has to have a Start activity.
- Check Category Account: this activity checks to see if the combination is a Category account combination.
- Copy Segment Value from Code Combination: this activity copies a segment value from a given code combination to a segment of the combination being built.
- Copy Segment Value from Code Combination: this activity copies a different segment value from a given code combination to another segment of the new combination.
- Assign Value to Segment: this activity assigns a specified value to another segment of the new combination.
- Copy Values from Code Combination: this activity copies values from a default code combination to any remaining segments of the new combination. This activity has the attribute 'Replace Existing Value' set to "False" to prevent values assigned elsewhere from being overwritten.
- End: every process has to have an End activity.
Note that after the code combination is created within the subprocess, the flow returns to the main process where the combination is validated by the function Validate Code Combination.
Note: A top-level runnable Account Generator process is represented by an icon called "flexproc.ico", which has the image of two gears on a yellow background with a representation of a flexfield combination at the bottom. A subprocess is shown by the "process.ico" icon, which has two gears in a yellow background. You can differentiate between the two types of processes using these icons.
Attention: These process diagrams are examples only. To learn about your particular product's processes, see your Oracle [Product] User's Guide.
See Also
Standard Flexfield Workflow: page - 53
Overview of the Oracle Workflow Builder: page
Oracle Workflow Guide
