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.
);

The bank details keyflexfield that defines personal payments methods has in a lot of legislations a hidden segment to validate the account number.

The segment is defaulted from a sql statement, using the account number as an input. A cross validation rule checks the content of that hidden segment.

When loading personal payment methods through the api's, one has to fill that hidden segment too.

To create yourself extra information types, you still have to insert some metadata yourself. Familypack G promises that this will be the last time.

Insert into Pay_element_type_info_types
(
information_type,
active_inactive_flag,
multiple_occurences_flag,
description,
legislation_code,
object_version_number
)
Values
(
'XX$your type$',
'Y',
'Y',
'$your meaningfull description$',
'BF',
1
);

The element_type_id is not available in the screen before saving, so you can not use it as a context for valuesets.