Reviewing and Processing the Allocation Packages

Reviewing/Processing the Allocation Packages

Click the hyperlinked “Run #” field in the “Select Packages” screen.

The “Review/Process allocation Packages” page appears.

The system displays the following fields in the ‘Allocation Run Info.’ section:

Company/FB	The login OU company for which the allocation Package is reviewed. The finance book in which the allocation Package is reviewed.
Fin. Year	The financial year for which the review of allocation packages is to be done.
Fin. Period	The financial period for which the review of allocation packages is to be done.
Package #	The unique number identifying the package.
Run #	The unique number identifying the run number of the allocation package.
Status	The run status of the allocation package.

Enter the following fields in the “Process Run” section:

Rule #	Use the drop-down list box to specify the Rule Id. The system lists all the Rules of the Package along with the value 'All'
Rule Line #	Use the drop-down list box to specify the Rule Line #. The system lists all the Rule Line #s along with the value ‘All’.

The system displays the following fields in the ‘Detail’ multiline:

Company	The login OU company for which the allocation Package is reviewed
Finance Book	The finance book in which the allocation Package is reviewed.
Rule #	The unique number identifying the rule
Rule Line #	The line number of the rule.
Rule Seq. #	The sequence number of the Rule Line #.
Account Code	The code identifying the account to which the accounting entries will be posted
Cost Center	The cost center to which the amount must be posted.
Analysis Code	The analysis code to which the selected account is mapped in the "Assign Analysis Code" activity of the "Account Based Budgeting" business component
Sub Analysis Code	The sub analysis code, which is mapped to the analysis code in the "Assign Sub Analysis Code" activity of the "Account Based Budgeting" business component.
Contra Account Code	The code identifying the account which will be credited while allocating costs out.
Exp. Cls.	The classification of the expense/income incurred by the journal voucher.
Currency	The currency in which the transaction has taken place.

Enter the following field:

Allocated Amt.

This represents the amount allocated to the destination combination of account code and/or Cost Center and/or Analysis and/or Sub Analysis Code and/or Expense Classification from the source combination. This can be modified by the user.

The system displays the following fields in the ‘Detail’ multiline:

Original Allocated Amt.	This represents the amount allocated to the destination combination of account code and/or Cost Center and/or Analysis and/or Sub Analysis Code and/or Expense Classification from the source combination. This is a display only field and displays the original allocated amount even if the user modifies the allocated amount.
Available Balance	Available Balance in Account ledger for the given source combination.

Enter the following field in the multiline:

Remarks

Any textual description. This field is mandatory when Allocated Amount is modified.

The system displays the following fields in the ‘Detail’ multiline:

Current Allocation	The current allocation from the source combination.
Flag	Flag displays whether it is a Source line or a destination line.
Run #/Package #	The number identifying the run. The number identifying the package.
Account Desc.	The textual description of the account code.
Cost Center Desc.	The textual description of the Cost Center.
Analysis Code Desc.	The textual description of the Analysis Code.
Sub Analysis Code Desc.	The textual description of the Sub Analysis Code.
Journal Voucher No	The number identifying the journal voucher. JV # gets generated on click of Post JV.

Click the “Save” pushbutton to save the entered details.
Click the “Post JV #” pushbutton to generate JV.

Journal Vouchers will get generated specifically to each Rule # and Source FB combination either as a Inter FB JV or a regular JV if FB is same in the destination also.

Note: For a Recurring Package, each time when the scheduler runs, if the Package is not yet Initiated for that period, the system generates a Run # and updates the status as Initiated (post an entry for processing) the package after the stipulated number of Days mentioned in the package. (This no. of days will be checked dynamically - if 4 days are edited and modified as 2 days when it is 3rd day when the scheduler runs, the package will be picked immediately and initiated (posted with an entry for processing).