To start a concurrent program via the Self Service interface, add the function 'Schedule Requests' (FNDCPSRSSSWA) to your menu.

This function can be added in a pure Self Service menu, but also in a forms menu.

This function can be used as a template to start specific concurrent programs, by adding the parameters 'programApplName' and 'programName' to the html call.

Run balances are a new implemention of balance value retrieval, optimized for performance. The old style implementation is also known as run result balances.

To check if your legislation uses the run balances architecture, check the pay_legislation_rules table for the keys 'SAVE_ASG_RUN_BAL' and 'SAVE_RUN_BAL'.

Update recurring and reversal are not compatible. The reversal process inverses only run results, and does not modify the element entries (values, and the column updating_action_id).

A very old enhancement request exists on metalink...

Appraisals within the manager self service model work fine. But now I had to give the HR department read-only access to all published appraisals, excluding the appraisals of HR people.

This can be done through the creation of a security profile, that shows all employees, except the HR emps.

Next, create a new responsibility, based on the manager self service, that is linked to the security profile above. Set the profile option HR_DISPLAY_PERSON_SEARCH to Yes for the responsibility.

As such, Hr people can enter the application with the responsibility above, and they have now the possibility to search for people (and to create an individual people list) within their security profile. Once they found the employee needed, they can view the published appraisals.

The concurrent manager is working fine now. I had to recreate the network 8.0.6 environment (make -f ins_network.mk install), since the lsnrctl executable (amongst others) did not exist.

This recreation of executables gave a terrible list of link errors (undefined reference to `__ctype_b'). After a long search, I found out (www.puschitz.com) that I had to downgrade the glibc libraries to glibc-2.3.2-5.i686.rpm. Once this was done, the make finished well, and up was the concurrent manager.

I really need to control the execution order of concurrent requests. Incompatibility rules work fine, but I need further control. This could be realized through the priority of the request.

This priority can be set through the profile option "Concurrent: Request Priority" (system name: CONC_PRIORITY).

Programmatically, you can set this profile option value via a fnd_profile.put call.

Self Service Version 4 has still the old style appraisals (html generated by plsql). The good thing about it is that it is still very straightforward to tweek the output a little. A few lines of plsql code visualized also the people group in the appraisal html page.

Next problem is that the apps listener is not up. adalsctl exits with status 127. The lsnrctl executable does not exists in the 8.0.6 home.

I have to make them again. I guess something will be wrong with the gnu C compiler version.

The motif libraries were missing. This became a blocking problem when I launched the forms at client side. Frm-92050 was the very message we've got when launching a form.

Look for the missing libraries for the forms server:
ldd f60webmx | grep 'not found'

=> libXm.so.2 not found

Installing the motif libraries from the RH9 distributie. Since this version was too high, I created a symbolic link from the higer libXm to the lower one.

Installing 11.5.9 on Red Hat 9. When starting the Apache server, the libdb.so.3 library could not be found. And he is really not on the system. Extracting compat-db-3.3.11-4.i386.rpm into a tmp directory, and copying that very library into /lib overcame the issue.

For more details: http://www.linuxquestions.org/questions/showthread.php?threadid=129670

This snippet to rollback multiple payroll actions. Handy in a test environment.

for r in (
Select payroll_action_id from pay_payroll_actions
where
order by 1 desc
)
loop
py_rollback_pkg.rollback_payroll_action
(
p_payroll_action_id => r.payroll_action_id,
p_all_or_nothing => FALSE,
p_dml_mode => 'FULL'
);
end loop;

The API pay_balance_adjustment_api.create_adjustment is functionally the same as the Adjust Balance form. An element entry is created (creator type and entry type = B), non visible in the element entry screen. The creator id points to an assignment action. A payroll action (B) is created, with one assignment action, and one single run result.

Hrms FamilyPack G has been applied. From that moment on hrglobal is reporting problems on database items. Seems that there is now a new who-trigger on the ff_database_items table, but the code to decide whether to insert or to update the database item from the shadow tables uses therefore still the last_update_date. As such, every database_item is seen as a new one, so every time hrglobal tries to insert an extra row in ff_database_items, violating some constraints.

A quick fix in in the body of ff_data_dict resolved it. Now the tar.

The Formula functions (link between PlSql functions and Fast Formula) do now support output parameters. No idea since what release, but in 11 it was not working. This enhances the PlSql-FF integration significantly.

The output from hr_utility.set_location can be redirected to dbms_output. This has an upper limit of 1 Mb. Since the assignment api's generate tons of tracing ,the 1 Mb can not be enough.

In that case, you can redirect your tracing to Oracle trace files.

Hr_Utility.set_trace_options(UPPER( 'trace_dest:trace_file'));
Hr_Utility.trace_on;

We encountered some problems with the pre-payment process for third party payment methods.

By adding some trace code into the package HR_PRE_PAY, we could knock down the issue.

fnd_file.put_line( 1, 'your message');

The line above adds some lines to the log file of the concurrent request.

When you change or create a balance route, you have to recompile all fast formulas, since the route text is part of the fast formula package code.

Bulk compile of fast formulas: $FF_TOP/bin/FFXBCP apps/apps 0 Y %% %%

Oops, deleted data, and 2 hours later my report was not working anymore. And the dba was not in to restore the table.

Flashback queries saved me.

SELECT * FROM xxrs_pay_balance_redefinitions
AS OF TIMESTAMP TO_TIMESTAMP ('07012004 00:00:01','DDMMRRRR HH24: MI: SS')

The API for assignment extra information types requires that there is a line for your session in the Fnd_sessions table, since some of the queries rely on that datetrack information.

In a lot of cases you need to make your pure plsql session application aware. Standard software needs to know the application user, responsibility or application to find the right profile option values.

This can be established through the following procedure call:

Fnd_global.apps_initialize
(
my_user_id,
my_responsibility_id,
800 -- application_id HR.
);