HR userexit for changes to employee infotype

I would like to add a function module to a few infotypes to invoke a bapi on the save to that info type. Which user exits should I put my function mod in when say infotypes pa0001,0002,0006,0105 are changed.

Example code from ZXPADU01/02 for ECC6.0
when '0001'.
    if i0001-begda ge '20060401'.
    MOVE innnn TO i0001.
      call method cl_hr_pnnnn_type_cast=>prelp_to_pnnnn
        exporting
          prelp = innnn
        importing
          pnnnn = i0001.
    do what ever you want to here.........
case P0001-BUKRS.
when 10.
do condition 10
when 20
do condition 20
when others.
endcase
    MOVE i0001 TO innnn.
      call method cl_hr_pnnnn_type_cast=>pnnnn_to_prelp
        exporting
          pnnnn = i0001
        importing
          prelp = innnn.

Similar Messages

BAdI or USEREXIT for changing data of purchase order header - ME21N

hello all,
I would like to ask you any way to change the field "reason for change" of the Purchase Order header.
I tried implementing the method PROCESS_HEADER of IF_EX_ME_PROCESS_PO_CUST
or changing reason_code of structure ekko in user exits EXIT_SAPMM06E_006 and EXIT_SAPMM06E_006
but it seems not to work.
How can i do?..
sap. v. ecc 6.0

>
Shiva Kumar wrote:
> Use the user exit : EXIT_SAPMM06E_012: This is triggered on saving of a PO...and user can add validations etc in the exit...
> Cheers
It doesn't work...
>
Martin Voros wrote:
> you get reference to object IM_HEADER in method PROCESS_HEADER of BADI ME_PROCESS_PO_CUST. On this object you can call two methods - GET_DATA and SET_DATA. GET_DATA returns structure with type MEPOHEADER. You can change your field here and then call method SET_DATA with your modified structure. This should work.
> Cheers
..same thing for this solution...
the field that i want to change is RSCOD inside structure EREVGRID...it seems to have also get_data and set_data methods ( IF_REVISION_ITEM_DCM ),
but I don't know which BAdI to implement that has a object type ref to EREVGRID...
Edited by: E_M on May 13, 2008 11:08 AM

MIRO USEREXIT for change GL account

I have the requirement
when i post the invoicement for good receipt
I need change the GL account by purchase group
anyone can give me some suggestion about use which userexit?

Hi,
You can use user exit ZXMBCU02 in enhancement -
MBCF0002 ( EXIT_SAPMM07M_001 ).
However you cannot directly chnage as MSEG is available as importing parameter and whatever you change here will have no impact on main prog. Instead you can use following code -
FIELD-SYMBOLS <F2> TYPE ANY,"Field Symbol for the GL ACCOUNT
DATA : W_KONTO_NAME(50) VALUE '(SAPMM07M)DM07M-KONTO'.
ASSIGN (W_KONTO_NAME) TO <F2>.
MOVE "GLACCOUNT" TO <F2>.
"GLACCOUNT" is the new GL account you want to change.
or try field exit:
report RSMODPRF
Regards,

Approval process for changes in BAsic infotype

Dear Gurus,
The customer wants approval process whenever hr changes BASIC infotype, a mail shpuld go to his superior, who will approve the request in the system.
- We are not implementing Workflow, ESS.
- Enqueue / Dequeue concept does not work with Time constraint 1.
- We are not in favour of changing time constraint of BASIC infotype
How can we handle this situation thru GUI client ?
Regards,
Vijay Badgeri

Hi Kapil/Sikandar,
Thank you for the reply.
As per my understanding, the steps involved would be:
1. The dynamic action will be triggered during "Change in Pay" action.
2. HR executive will make necessary changes in IT0001, IT0008, IT0014.
3. Dynamic action is triggered when IT0008 is updated.
4 Current values & new values of IT0008 & IT0014 are moved to workflow container and create workflow request to the HR Manager.
5. On approval of workflow request by HR Manager, the IT0008, IT0014 get updated.
my doubts are :
1. What would be the status of action till manager approves?
2. Will HR Admin be able to see the entries made by him ?
(In Finance we have PARK option, is there any such option in HR?)
3. Would the dynamic action triggered if bulk "Change in Pay" actions are generated thru BDC/LSMW ?
Pl let me know...
Warm Regards,
Vijay Badgeri

Userexit for changing line item from header, tcode VA42, VA41

Hi All,
I have a Zfield (VBAK) for the sales document (contract) at the header level in Additional tab.
Also the same zfield is present in VBAP table for all line items.
When this field is maintained by the user using Tcode VA41 or VA42 the line item zfield should also get updated.
I am trying to find out if User Exits
1. USEREXIT_MOVE_FIELD_TO_VBAK
2. USEREXIT_SAVE_DOCUMENT_PREPARE
might work. Can anyone tell me if there is access to line items in the above 2 user exits which I can modify.
Thanks,
Kajal

Hi Breakpoint,
Yes I did use table XVBAP in uesr exit SAVE_DOCUMENT_PREPARE.
But somehow my changed values in XVBAP table is not reflected in the table VBAP.
Am I missing something here.
My piece od code in the user exit :
FORM XVBAP_ZZREBREL_CHANGE TABLES t_xvbap STRUCTURE vbapvb
                           USING P_VBAK_ZZREBREL TYPE vbak-zzrebrel.
data wa_xvbap type vbapvb.
IF p_vbak_zzrebrel = 'X'.
    LOOP AT t_xvbap into wa_xvbap.
      wa_xvbap-zzrebrel = 'X'.
      MODIFY t_xvbap from wa_xvbap INDEX sy-tabix TRANSPORTING zzrebrel.
      clear wa_xvbap.
    ENDLOOP.
ENDIF.
ENDFORM.

Userexit for changing financial period(MONAT)

Hello.
We need to change financial period(BKPF-MONAT) on FI document which is created by Other Goods Receipts(Trcd:MB1C).
In additoion, we also need to do it following documents.
-Profit center document
-FI-SL document
Does anyone know how to handle this situation ?
Thanks and Regards,
S.Hirai

Hello,
Can I know how you have changed the monat field in bkpf table while creation of fi document.
Regards
Srinivas

Userexit to change PO Line items

Hi All,
We are looking for a userexit for changing the PO line items (EKPO-SPINF)......searched the entire forum but not working.....
we were trying to implement MM06E005........however none of the function modules in it are triggered......
Any help.....

Hi Faheem,
Thanks for the reply.
We are on 4.6c system...hence we do not have this BADI available...
What i am trying to understand is whether we can use exit MM06E005 to modify standard fields.....though we do not have any customer fields...
What i feel is no since....the BADi will not be triggered from those custom screens.........
Please correct, if i am wrong....
But its hard to believe that we cannot modify standard fields of PO when creating purchase order......in 4.6c

Error: while configuring logs for changes in infotype data

Hi All,
I am configuring the following Tables for maintain logs for changes in infotype data.
V_T585A, V_T585B and V_T585C
While configuring V_T585B, when i input * in 'field name' column it gives me an warning message " All data fields in **** infotype 31 will be deleted.
Please let me know, what does this warning message means?
Also, How is the report RPUAUD00 read?
Regards
Simran

Hi Simran,
you are not suppose to give the IT 0031-Reference Personnel Numbers in these tables. why because this will done at the time of Employee hiring only and we don't change this. if you change you will lost the old data in the IT.
Normally we assign only the IT which we change frequently for the master data. example like 0 1 2 7 8 9 27 582 - 589 2001 2006.
if you are configuring today means from today on-wards any changes had made to these IT's you can see in the report. before changes will not be seen. in the report you have to choose either long-term document / short-term document and remaining fields as per the requirement.
Regards,
Praneeth kumar

Change Pointers not being created for HR-PA Custom Infotype

Problem Description:
We have a custom Infotype in SAP to store the data for contingent employee - Infotype 9001. Change pointers is
turned on. We are running the program RBDMIDOC to send changes to Oracle IDM using message HRMD_A. The change
detected for all infotypes except 9001. For 9001, the change pointer is not created.
The following are the current configuration details:
IDOC Extension Created to Idoc type HRMD_A07 (ZHR_EXT)
custom segment zhr_seg
Change pointers are switched on.
Change pointers switched on for message Type HRMD_A.
IDOC configuration created for Port / Process code etc.
Maintenance of view T777D - Added ZHR_SEG.
If I add the segment ZHR_SEG as a 2nd segment to Infotype 0000, I dont get a syntax error. But the changes for Infotype 9001 are not picked up.
If I add the segment ZHR_SEG as a segment to Infotype 9001, I get a syntax error - check EDI: Syntax error in IDoc (mandatory segment missing) below.
EDI: Syntax error in IDoc (mandatory segment missing)
Message no. E0072
Diagnosis
The segment ZHR9001 has the attribute 'Mandatory' in the syntax description of the basic type HRMD_A07 (customer enhancement ZHR_EXT). However, the segment is missing in the IDoc. The segment number logged in the status record identifies the item before which the segment is missing.
This error may have been triggered by an unidentifiable segment before the expected mandatory segment.
Procedure
Please check the IDoc or the syntax description of the basic type HRMD_A07 (customer enhancement ZHR_EXT).

Were you able to resolve the issue?
If yes, could you please share what was done to resolve it.
Your help will be greatly appreciated.

Reason for change of Infotype Based on Company Code

Hi Experts,
I have a requirement where I need to restrict the F4 HELP in
PA30 Transaction for the infotype 15 based on company code for the field reason for chagne.
I know that reason for change of infotype are maintained in the table T530E.
But can this be restricited through SPRO configuration.
Thanks in Advance.
Regards,
IFF

Hi.
It's possible to change the search helps with a search help exit.
Take a look in SE11 for search help H_T530E.
Search help exit
A search help exit is a function module for making the input help process described by the search help more flexible than possible with the standard version.
This function module must have the same interface as function module F4IF_SHLP_EXIT_EXAMPLE. The search help exit may also have further optional parameters (in particular any EXPORTING parameters).
A search help exit is called at certain timepoints in the input help process.
Note: The source text and long documentation of the above-specified function module (including the long documentation about the parameters) contain information about using search help exits.
Function modules are provided in the function library for operations that are frequently executed in search help exits. The names of these function modules begin with the prefix F4UT_. These function modules can either be used directly as search help exits or used within other search help exits. You can find precise instructions for use in the long documentation for the corresponding function module.
Regards.

Userexit for partner function changed

What is the userexit for partner function changes in VA01 or VA02.

Hi,
Please check this:
EXIT_SAPLEINM_002
Thanks and best Regards,
Suresh

Userexit for SO Create/Change.

Hi,
Please tell me the userexit for the Sales Order Create/Chagne

Hi,
You can find the user exits in the include MV45AFZZ....
Details are given below   :
<b>User exits in the program MV45AFZZ</b>
The user exits which you can use for modifications in sales document processing are listed below.
     USEREXIT_DELETE_DOCUMENT
This user exit can be used for deleting data which was stored in a separate table during sales document creation, for example, if the sales document is deleted.
For example, if an additional table is filled with the name of the person in charge (ERNAM) during order entry, this data can also be deleted after the sales order has been deleted.
The user exit is called up at the end of the FORM routine BELEG_LOESCHEN shortly before the routine BELEG_SICHERN.
     USEREXIT_FIELD_MODIFICATION
This user exit can be used to modify the attributes of the screen fields.
To do this, the screen fields are allocated to so-called modification groups 1 - 4 and can be edited together during a modification in ABAP. If a field has no field name, it cannot be allocated to a group.
The usage of the field groups (modification group 1-4) is as follows:
     Modification group 1: Automatic modification with transaction MFAW
     Modification group 2: It contains 'LOO' for step loop fields
     Modification group 3: For modifications which depend on check tables or on other fixed information
     Modification group 4: is not used
The FORM routine is called up for every field of a screen. If you require changes to be made, you must make them in this user exit.
This FORM routine is called up by the module FELDAUSWAHL.
See the Screen Painter manual for further information on structuring the interface.
     USEREXIT_MOVE_FIELD_TO_VBAK
Use this user exit to assign values to new fields at sales document header level. It is described in the section strong> "Transfer of the customer master fields into the sales document".
The user exit is called up at the end of the FORM routine VBAK_FUELLEN.
     USEREXIT_MOVE_FIELD_TO_VBAP
Use this user exit to assign values to new fields at sales document item level. It is described in the section strong> "Copy customer master fields into the sales document".
The user exit is called up at the end of the FORM routine VBAP_FUELLEN.
     USEREXIT_MOVE_FIELD_TO_VBEP
Use this user exit to assign values to new fields at the level of the sales document schedule lines.
The user exit is called up at the end of the FORM routine VBEP_FUELLEN.
     USEREXIT_MOVE_FIELD_TO_VBKD
Use this user exit to assign values to new fields for business data of the sales document. It is described in the section strong> "Copy customer master fields into sales document" .
The user exit is called up at the end of the FORM routine VBKD_FUELLEN.
     USEREXIT_NUMBER_RANGE
Use this user exit to define the number ranges for internal document number assignment depending on the required fields. For example, if you want to define the number range depending on the sales organization (VKORG) or on the selling company (VKBUR), use this user exit.
The user exit is called up in the FORM routine BELEG_SICHERN.
     USEREXIT_PRICING_PREPARE_TKOMK
Use this user exit if you want to include and assign a value to an additional header field in the communication structure KOMK taken as a basis for pricing.
     USEREXIT_PRICING_PREPARE_TKOMP
Use this user exit if you want to include or assign a value to an additional item field in the communication structure KOMP taken as a basis for pricing.
     USEREXIT_READ_DOCUMENT
You use this user exit if further additional tables are to be read when importing TA01 or TA02.
The user exit is called up at the end of the FORM routine BELEG_LESEN.
     USEREXIT_SAVE_DOCUMENT
Use this user exit to fill user-specific statistics update tables.
The user exit is called up by the FORM routine BELEG-SICHERN before the COMMIT command.
Note
If a standard field is changed, the field r185d-dataloss is set to X. The system queries this indicator at the beginning of the safety routine. This is why this indicator must also be set during the maintenance of user-specific tables that are also to be saved.
     USEREXIT_SAVE_DOCUMENT_PREPARE
Use this user exit to make certain changes or checks immediately before saving a document. It is the last possibility for changing or checking a document before posting.
The user exit is carried out at the beginning of the FORM routine BELEG_SICHERN.
Working with User Exits
Updating the document flow
The total quantity to be billed is transferred to the sequential data record. Quantities which have already been billed are managed within the SAP system. This process is influenced by user exits. User exits directly influence the update of compressed document flow VBAPF in the system. This document flow accumulates quantities which have already been billed and compares them to new billing quantities. A new billing document is then created with the following quantity:
Quantity to be billed = New quantity - quantity already billed
Using user exits, you can specify the keys to which records of the compressed document flow are to be stored.
santhosh

Change sales employee authorization for sales opportunities

"Change sales employee" in general authorizations is working only for documents, but not for sales opportunities.
There should be an authorization alos for sales employee on sales opportunities.
Not only for itself but also to make a sense to authorization of sales employee on documents, because having full rights to sales employee on sales opportunities make easy to set sales employees on documents even if not authorized, just by adding the document from a sales opportunity from where it will inherit any sales employee.

Hi Sean,
Your request is very reasonable. I am supporting this DRQ. It would be better to be include in the new release soon.
What is your B1 version? Have you checked the latest version?
Thanks,
Gordon

Function Module to change start of infotypes when hire date changed in HCM

Hello Guys,
I have a scenarion where in i need to change the start of the infotypes(Ex IT0001,2,7,41.105 etc) for an employee in the program with new hire date. For this already one BDC is there with PA41 recording but for some scenarios it is not working. I am searching for a FM to overcome the issue. Coudl any one pls help me if you have the same problem eralier.
Early help appreciated......
Thanks,
Preetham

This way we need to change all the infotypes with this FM in the program which are there in PA41 to change the date, I am looking a direct FM whicn can do the functionality of PA41 in instead of BDC.
Thanks ...

RHINTE30 for updation of PA infotype

Hi All,
I am trying to update the personnel area(PA) and personnel sub area(PSA) for an employee in IT000,1 if PA or PSA of its Organizational unit is changed in which employee lies.
I execute the report with PERNR as a parameter but the report executed without making any changes to the Infotype 0001.
I have checked the integration settings between PA and OM. PLOG feature settings are also done.
Could any one please let me know what could be reason for this.
Thanks & best regards, Amit

Hi,
As far as I know, RHINTE10 is used to create the objects in PA which are already created in OM to make the data synchronized. Keep my updated if I am wrong!!
But my problem is related to an existing Organizational Unit or Position which is already present in both OM and PA. I changed the Personnel area and PSA for an Org Unit but it's not reflecting for the employee associated to this Org Unit.
Thanks & Best regards,
Amit

HR userexit for changes to employee infotype

Similar Messages

Maybe you are looking for