Defining AutoAccounting Rules (Oracle Projects Help)


	Previous	Next		Contents	Index	Navigation	Glossary	Library

Defining AutoAccounting Rules

Each AutoAccounting rule you define supplies one Accounting Flexfield segment value at a time. Thus, you need to specify one AutoAccounting rule for each segment in your Accounting Flexfield for each AutoAccounting transaction you want to use.

Some of the AutoAccounting rules you define can be quite simple, such as always supplying a constant company code or natural account. Others can draw upon context information (parameters), such as the revenue category for a particular posting or the organization that owns a particular asset. You can even use multiple parameters to provide a segment value.

You can reuse the same AutoAccounting rules for many different functions and their transactions.

You define rules based on project information that you enter. You can use these AutoAccounting parameters as input values to your rules.

Note: AutoAccounting does not use Flexfield security rules when determining a valid account combination. You must define your AutoAccounting rules to determine the appropriate account based on the rules required by your company.

Defining AutoAccounting Rules

See Also