Previous  Next          Contents  Index  Navigation  Glossary  Library

The Default Account Generator Process for Oracle Receivables

Evaluate whether the default Account Generator process meets your accounting requirements. No setup steps are required to use the default. The default process can also be updated later as your needs change. You can make minor changes to the default process without changing the name.

Note: If you used FlexBuilder in Release 10 but did not customize the default configuration, you can use the default Account Generator process in Release 11, which gives you the same result as the default assignments in FlexBuilder.

Each Account Generator workflow is called an item type. Oracle Receivables comes with the following Account Generator item type:

The AR Substitute Balancing Segment contains the following workflow processes:

Replace Balancing Segment Process

This process updates the balancing segment whenever you create finance charges for a transaction or post transactions to the general ledger by running the GL Interface.

Following are the attributes of this item type:

The Replace Balancing Segment process consists of three unique activities that comprise the five activity nodes that appear in the workflow diagram.

In the workflow diagram shown below, the process activity nodes are numbered for reference in the descriptions that follow. (The numbered circles are not part of the process diagram.)

Sample Invoice Account Generation Activities

Following is a description of each activity in the sample process for Replace Balancing Segment Account Generation, listed by function name. You can create all the components for an activity in the graphical Oracle Workflow Builder except for the PL/SQL stored procedures that the function activities call.

Start Generating Code Combination (Node 1)

This is a standard activity that marks the start of the process.

Copy Segment Value from Code Combination (Node 2)

Node 2 copies the new balancing segment value from the substitution code combination ID (CCID). This is the segment that will contain the value of the exchange gain or loss for this transaction.

Copy Values from Code Combination (Node 3)

This activity copies the remaining segment values from the original code combination into the new code combination for this transaction.

Validate Code Combination (Node 4)

Node 4 contains the standard Flexfield function for validating a code combination. For this function to work, the attribute value New code combinations must be set to True.

End Generating Code Combination (Node 5)

This standard activity ends the code combination generation process.

Generate Account Using FlexBuilder Rules Process

If you used FlexBuilder in a previous release to generate account combinations, you can use the Generate Account Using FlexBuilder Rules process to replicate your FlexBuilder setup automatically, without changing any of your predefined FlexBuilder Rules, and without customizing the Account Generator. The Generate Account Using FlexBuilder Rules process includes a function generated during your upgrade from Release 10 to Release 11.

If you are upgrading from Release 10, follow the guidelines in the FlexBuilder chapter of the Oracle Applications Upgrade Preparation Manual.

See Also

Customizing the Account Generator for Oracle Receivables


         Previous  Next          Contents  Index  Navigation  Glossary  Library