Check before an infotype operation (PA) / HR_INFOTYPE_OPERATION

Question

Hi,
In my latest project there is a requirement to simulate the HR_INFOTYPE_OPERATION (or other possibilities to update the PA* infotypes). The main meaning of the project is in robust customer customization, which translates to dynamic abap webdynpro views with data from the infotypes. Person fills those forms and sends the "personal document" for processing (creating entries in customer Z* namespace). Just after that a different user can pick the "personal document" and can process it - that is the part where it comes to the infotypes filling (HR_INFOTYPE_OPERATION, batch-inputs, direct updates etc.).
Now requirement is to implement checks also in the creating of the "personal document" itself, before saving it into customer (Z*) tables. How could that be achieved? One way would be using HR_INFOTYPE_OPERATION with nocommit = 'X' and after all operations call of ROLLBACK WORK, initializing buffers etc. However whole concept of using HR_INFOTYPE_OPERATION is in locking the personal number before the call. User which only creates the "personal document" should not lock the personal number - as this part should be independent on other processes, taken in SAP standard HR tables / transactions themselfs.
I did not find any kind of checking mechanism ignoring the person-locking concept, but with full logic that the corresponding infotype expects. There should be are all kind of operations supported (insert, copy, delimit...).
I underline that the customer is at a low support package (< EH5) and the decoupling infotypes concept is useless here.
Thanks for any advice.

Answer 1

Hi Surya,
Enhancement project PBAS0001which contains those includes is obsolete in terms of detached infotype framework.
The following enhancements will work for a decoupled infotype:
BAdIs:
HRPAD00INFTYBL Enhancement of Business Logic of Standard Infotypes (this is the direct replacement for the enhancement project PBAS0001)
HRPAD00INFTYDB Performing actions after updating (this is the direct replacement for the BAdI HRPAD00INFTY)
HRPAD00INFTYUI BAdI: UI Logic Enhancement
More information you may find here:
IMG Personnel Management->Personnel Administration->Customizing Procedures->Infotypes->Infotypes in Detached Infotype Framework
Under the following IMG nodes:
Enhancements to Business Logic and Updating
Enhancements to UI Logic
Regarding to your questions:
1. If the infotype is decoupled, even the HR_INFOTYPE_OPERATION will call these business checks and time constraint checks. Right ? So, what is the major advantage of moving to HR_ECM_INSERT_INFOTYPE ?
I suppose it has been done to follow the same logic as SAP does in PA-EC component
For example to adjust a salary in ECM SAP uses FM HR_ECM_ACTIVATE_SAL_ADJUSTMENT meanwhile it uses FM HR_ECM_INSERT_INFOTYPE to update IT0008
2. Is there some trick to enable HR_ECM_INSERT_INFOTYPE call the user exits of the Infotype ?
I think there is no standard way to do so...
It is a good idea to follow the standard enhancement concept for decoupled infotypes, at least I see no problems in moving the old enhancement to a new one.
Kind regards,
Sergey