Invalid or Processing status records - Generate Run Balances

There can be following reasons for processing status

1) Generate run balances process is still running

2) You had PROCESS_TIMEOUT for this process and that limit is reached so process was gracefully terminated.

3) Generate run balances process has been terminated or killed due to some reason

so you can wait till process complete sucessfully in case of process still running.

You can find what are all balances which are in invalid or processing status with following SQL

SELECT * FROM PAY_BALANCE_VALIDATION;

Now you have two options in case of PROCESS_TIMEOUT or termination/killed

OPTION 1: Retry the GRB (Preferred Solution as it starts back up where it left off)

Resp: Responsibility Generate Run Balance was Submitted Under

Nav: Process & Reports > Submit Process & Reports > Single Request

Name: Retry US Payroll Process (US Legislation)

Parameters:

- Process Year: 4712

- Process Type: Magnetic Report

- Process: LOV

The LOV should show the Generate Run Balance process that have executed.

Select the process to retry.

OPTION 2: Start the process over (Note: All previous will be lost)

In order to get the status to change from Processing - you must manually switch the status flag (Contact Support for information concerning how to perform this) from P (Process) to I (Invalid).

Then the process can be submitted again with the MODE parameter set to ALL INVALIDS.

NOTE: That running the ALL BALANCES or ALL INVALIDS (if there is a large quantity) for ASSIGNMENT Level will process for a long time.

Please note that it is recommended that when ever executing the GRB or ARDB for ALL BALANCES or ALL INVALID (if a large amount exist) that the PROCESS_TIMEOUT parameter should be set on the Pay_Action_Parameters table to control the execution time of the process.

Future Dated balance Adjustment

You can't run payroll or quickPay for employees if a future dated balance adjustment exists for this employee.

Does Transfer to GL Process rollback remove rows from GL_INTERFACE table

Yes. If you rollback Transfer to GL Process, it will remove records from GL_INTERFACE table unless they have been imported.

Check Oracle Application version for Specific Module

Following query can be used to find module version

select to_number(substr(product_version,1,2))

from fnd_product_installations

where APPLICATION_ID = 800

reference column details :GL_INTERFACE

reference21 :payroll_action_id -- payroll action ID for Transfer to GL process

reference22 :cost_allocation_keyflex_id

reference23 :run_date -- payroll run check date

reference24 :run_date_earned -- payroll run date earned

reference25 :run_action_id -- payroll action ID for payroll run process

The package called by Transfer to GL process : pay_trgl_pkg.trans_pay_costs

Transfer to GL Process transfer on date earned

If you want to set the accounting date for the transfer to date earned, then change the TGL_DATE_USED pay action parameter to "E".

If you do not do this then the accounting date of the transfer defaults to the check/cheque date of the originating payroll

Due to the fact that employees need to have distributed labor costs as per the time period derived from date earned , instead of the time period that payroll populates in payroll tables. Utilizing the parameter TGL_DATE_USED set to the value of ‘E’, will send transactions to GL based on date earned (when switch is enabled), Labor Distribution will also pick up only on the basis of date earned. The get_payroll_assig actions was modified to pick on the basis of date earned for regular run, quick pay and reversals.

Not Set - Normal costing will be transferred with an Accounting Date of the payroll run's effective date. Reversal of Estimate Costing will be transferred with an Accounting Date of the payroll periods Pay Advice Date + Payroll Offset Days.

'E' - Normal costing will be transferred with an Accounting Date of the payroll run's Date Earned. Reversal of Estimate Costing will be transferred with an Accounting Date of the payroll period's end date.

'EVE' - Normal costing will be transferred with an Accounting Date of the payroll run's effective date. Reversal of Estimate Costing will be transferred with an Accounting Date of the payroll period's end date.

Values Null, E or EVE

Default Value Null

Parameter Type Costing

Processes Used In TRANSFER TO GL

Modules Used In PACKAGES

PAY_TRGL_PKG (pytrangl.pkb)

Running Select statement from diagnostics in Oracle Apps

You can see value of any profile using diagnostics in Oracle applications as shown in screenshot here

Delete An Assignment Change

Find what record you want to delete e.g. for following assignment I want to delete this record which is start from 01-Mar-2010

Change the effective date to one day before above record i.e. 28-mar-2010 by click on below shown icon in toolbar

After changing your effective date assignment form will show you previous record as shown here where your effective date to will be 28-Feb-2010

Click on delete icon in toolbar as shown in below screenshot

After click the delete icon it will show below message where click on OK button

Next screen will ask what delete you want to do. Depending on requirement you can

a) Next – It will delete next change only so if you have multiple future changes, it will delete only next one leaving other changes untouched

b) All – It will delete all the future changes done on assignment

c) Purge – It will completely delete this assignment

After selecting your option, press save icon in toolbar