GL Initialization & Validation Process (Oracle General Ledger Users' Guide)


	Previous	Next		Contents	Index	Navigation	Glossary	Library

GL Initialization & Validation Process

The GL Initialization & Validation Process performs initialization, then validates the journal batch. If the journal batch is valid, the subprocess also determines whether the batch requires approval.

The process has a result type of GL Initialization & Validation Process Result that gives one of three results:

Approval Not Required: The journal batch does not need approval.

Approval Required: The journal batch needs to be approved before further action can be taken by the preparer.

Validation Failed: The journal batch failed the validation process and was never submitted to the approver.

The process consists of 12 unique activities, some of which are reused, to comprise the 14 activity nodes that appear in the workflow diagram:

Start (Node 1)

This is a Standard function activity that simply marks the start of the process.

Function WF_STANDARD.NOOP

Result Type None

Retrieve Set of Books Attributes (Node 2)

This function activity retrieves your set of books attributes.

Function GL_WF_JE_APPROVAL_PKG. GET_SOB_ATTRIBUTES

Result Type None

Retrieve Journal Batch Attributes (Node 3)

This function activity retrieves your journal batch attributes, which are then used to determine if the journal batch is valid.

Function GL_WF_JE_APPROVAL_PKG. GET_JEB_ATTRIBUTES

Result Type None

Is Journal Batch Valid (Node 4)

This function activity determines if the journal batch is valid. If the batch is valid, the procedure returns a value of 'Yes'. If the batch is not valid, the procedure returns a value of 'No'.

Function GL_WF_JE_APPROVAL_PKG.IS_JE_VALID

Result Type Yes/No

Customizable: Is Journal Batch Valid (Node 5)

With this function activity you can customize the journal batch validation process. If the batch is valid, the procedure returns a value of 'Yes'. If the batch is not valid, the procedure returns a value of 'No'.

Function GL_WF_CUSTOMIZATION_PKG.IS_JE_VALID

Result Type Yes/No

Does Journal Batch Need Approval (Node 6)

This function activity determines whether the journal batch needs approval. If so, the procedure returns a value of 'Yes'. If not, the procedure returns a value of 'No'.

Function GL_WF_JE_APPROVAL_PKG. DOES_JE_NEED_APPROVAL

Result Type Yes/No

Customizable: Does Journal Batch Need Approval (Node 7)

With this function activity you can customize the process of determining whether a journal batch needs approval. If the batch does need approval, the procedure returns a value of 'Yes'. If not, the procedure returns a value of 'No'.

Function GL_WF_CUSTOMIZATION_PKG. DOES_JE_NEED_APPROVAL

Result Type Yes/No

Update Journal Batch Status to Invalid (Node 8)

This function activity updates the journal batch approval status to Invalid.

Function GL_WF_JE_APPROVAL_PKG.SET_JE_INVALID

Result Type None

Update Journal Batch Status to Approval Not Required (Node 9)

This function activity updates the journal batch approval status to Approval Not Required.

Function GL_WF_JE_APPROVAL_PKG. SET_APPROVAL_NOT_REQUIRED

Result Type None

Notify Preparer of Invalid Journal Batch (Node 10)

This activity notifies the preparer that the journal batch was invalid. The message includes 'Send' or 'Respond' attributes that display the batch name, invalid journal entry error message, the monitor URL, and the Enter Journals window.

Message Notify Preparer of Invalid Journal Batch

Result Type None

Notify Preparer of No Approval Required (Node 11)

This activity notifies the journal batch preparer that no approval is required. The message includes 'Send' or 'Respond' attributes that display the batch name, the monitor URL, and the Enter Journals window.

Message Notify Preparer of No Approval Required

Result Type None

End (Nodes 12 through 14)

This function activity marks the end of the process. Although the activity itself does not have a result type, each node of this activity in the process must have a process result assigned to it. The process result is assigned in the property page of the activity node. Since the GL Initialization & Journal Validation process activity has a result type of GL Initialization & Journal Validation Process Result, each End activity node must have a process result matching one of the lookup codes in the GL Initialization & Journal Validation Process Result lookup type.