on 05-12-2015 12:46 PM
Hi Friends,
I would like to create dynamic actions that would pick up initial hire date from IT0000 and Date of birth from IT0002 to automatically update in IT0041.Can you please help me with logic.
Thank you
Babaiah
Hi Sruthi and Dimitiri,
Thanks for your suggestions.I have explored further and written dynamic actions to default Date of birth and Initial hire date in IT0041.I am able to default DOB in IT0041 but not the hire date.
Can you please help me out with the solution to default both DOB and initial hire date.
Please refer the screenshot and help me out with the solution.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Babaiah,
Please use the function code 06 instead of 04 when calling GBDAT. or You can combine both into single dynamic action.
04 404 W P0041-DAR01='16'
04 405 W P0041-DAT01=P0000-BEGDA
04 406 W P0041-DAR03='60'
04 407 W P0041-DAT03=P0002-GBDAT
The function code '04' is for create, so if same dynamic action is called twice the second execution will overwrite the first record.So you should use Function code "06(06 for Change and create)" .
Please try the same.
Thanks & Regards
JIm
Hi Jimson,
I have removed the config for IT0002 under T588Z.I have made changes as you said under IT0000 under t588z(combined dynamic action) but I didn't get the expected output.One by one all infotypes are triggered earlier and now,it is only triggering IT0001 followed by IT0041.
Please go through the screen shot for the configuration which I have done and help me out to fix this issue.
Thank you
Babaiah
Hi,
I'm more interested in the requirement than I am in the solution.
Can you explain why are you capturing DOB on IT0041 when it already exists on IT0002 and it is meant to be captured solely on IT0002? Points to consider:
1. Security/audit - From your screenshot (personnel area Alabama), it appears you are working for a US based client. If that is true, DOB is classified as personally identifiable information (PII) as per the guidelines defined by the National Institute of Standards and Technology (NIST). For that very reason, access to IT0002 is usually restricted. Access to IT0041 is much more open because it houses other dates that track important events such as hire, rehire, transfer, termination etc during an employee life cycle. To my knowledge, there is no standard way to restrict access based on fields within an infotype. It is all or nothing. With what you are trying to accomplish, you will not be making any friends with the folks from audit.
Refer: http://csrc.nist.gov/publications/nistpubs/800-122/sp800-122.pdf
2. Duplicate data entry in the database.
Hope this helps in evaluating the requirement.
Donnie
Jagan Gunja wrote:
In security profile, it is possible to restrict at field level within an infotype. Not sure about restricting in IT 41 - date value based on a particular date type value?
Are you are talking about auth. fields (PERSA, PERSG etc.) in auth. object such as P_ORGIN? If yes, that is not the same as restricting at field level within an infotype. For example, one cannot restrict the DOB field GBDAT within IT0002. If one has access to IT0002, they can see every field on it.
Donnie
I am not a Security expert. I have had feedback from several persons as above. Also see the links below:
1. Here it says you may be able to use include MPPAUTZZ.
3. Authorization Objects - Authorizations in mySAP HR - SAP Library
4. P_ORGINCON (HR: Master Data with Context) - Authorizations in mySAP HR - SAP Library
5. P_ORGXX (HR: Master Data – Extended Check) - Authorizations in mySAP HR - SAP Library
Hi All,
Thank you so much for your help.
I have removed dynamic actions under IT0000 and created under IT0002.Upon completion of hiring action,I could see DOB and Hire date is getting defaulted in IT0041.
Thank you Jimson
Babaiah
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Babaiah,
I agree with Shruti. You have not provided enough information on what exactly you want to achieve.
Also, in order to actually learn how dynamic actions work it is a great idea to try and make a dynamic action according to your requirement yourself and see where you're running into issues.
I'm sure all of us around here will gladly help you with these.
Good luck!
Dimitri.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Dimitri,
Thank you for the reply.I would like to build logic with screen fields like P0000-BEGDA and P0002-GBDAT for automatic updation of hiring date and date of birth in IT0041.
I would like to know the complete logic.Please help.
Thanks
Babaiah
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Babaiah
What logic are you expecting to know? Have you first made any attempt yourself to write the dynamic action? I would advise that you first do some reading on how to write dynamic actions and then try writing one yourself for your requirement. Then if you face any error post it here.
Hi Babaiah,
If you look into the dynamic actions view V_T588Z (select infotype 0000) , you will see some examples:
*-- US MODEL: DEFAULT U1/U2 DATES ON NEW HIRE --*
*** CREATE INFOTYPE 41 WHEN HIRING MEXICO ****
***** CREATE INFOTYPE 0041 **** (BRAZIL)
on how to create an IT41 record with dates from other infotypes. In the examples above, the initial hire date is used but it would be easy to add P0002-GBDAT as well.
Let us know how you get along with your dynamic action.
Good luck!
Dimitri.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.