Infotype 002 - Marital Status - Married - Infotype 0021 - Subtype 1

[Former Member]

Experts,

The below dynamic actions for Infotype 0002 works fine when the marital status is changed (from Single to Married) via PA30. IT0021 (subtype 1) Infotype pops up with Family Member as 'Spouse'

But when we create IT0002 record with marital status as 'Married' while hiring the employee (PA40) IT0021 doesn't pop up with subtype 1. Can someone help here on how to achieve this.

Guess we cant add Infotype 0021 subtype 1 in the Infogroup for Hiring Action as we need to check the condition for Marital Status as 'Married' and only then we need to populate IT0021 (Subtype 1).

INFTY	FNAME	OPERA	SEQNO	KENNZ	VINFO
2	FAMST	6	150	P	PSPAR-TCLAS='A'
2	FAMST	6	151	P	T001P-MOLGA='01'
2	FAMST	6	152	P	P0002-FAMST='1'/X
2	FAMST	6	153	P	PSAVE-FAMST='0'
2	FAMST	6	154	I	INS,0021,1,,(P0002-FAMDT),(P0002-ENDDA)
2	FAMST	6	160	P	PSPAR-TCLAS='A'
2	FAMST	6	161	P	T001P-MOLGA='01'
2	FAMST	6	162	P	P0002-FAMST='3'/X
2	FAMST	6	163	P	PSAVE-FAMST='1'
2	FAMST	6	164	I	INS,0021,10,,(P0002-FAMDT),(P0002-ENDDA)
2	FAMST	6	165	I	LIS9,0021,1,,(P0002-FAMDT),(P0002-ENDDA)
2	FAMST	6	170	P	PSPAR-TCLAS='A'
2	FAMST	6	171	P	T001P-MOLGA='01'
2	FAMST	6	172	P	P0002-FAMST='2'/X
2	FAMST	6	173	P	PSAVE-FAMST='1'
2	FAMST	6	175	I	LIS9,0021,1,,(P0002-FAMDT),(P0002-ENDDA)
2	FAMST	6	180	P	PSPAR-TCLAS='A'
2	FAMST	6	181	P	T001P-MOLGA='01'
2	FAMST	6	182	P	P0002-FAMST='0'/X
2	FAMST	6	183	P	PSAVE-FAMST='1'
2	FAMST	6	185	I	LIS9,0021,1,,(P0002-FAMDT),(P0002-ENDDA)
2	FAMST	6	190	P	PSPAR-TCLAS='A'
2	FAMST	6	191	P	T001P-MOLGA='01'
2	FAMST	6	192	P	P0002-FAMST='1'/X
2	FAMST	6	193	P	PSAVE-FAMST='3'
2	FAMST	6	195	I	INS,0021,1,,(P0002-FAMDT),(P0002-ENDDA)
2	FAMST	6	200	P	PSPAR-TCLAS='A'
2	FAMST	6	201	P	T001P-MOLGA='01'
2	FAMST	6	202	P	P0002-FAMST='1'/X
2	FAMST	6	203	P	PSAVE-FAMST='2'
2	FAMST	6	204	I	INS,0021,1,,(P0002-FAMDT),(P0002-ENDDA)

Thanks,

Sriram

[jagan_gunja]

Further, when there are several records of IT 2, the module part which processes dynamic actions, may not be positioning IT 2 at the right record (i.e, with the right validity period) corresponding to the pers.action date.

Hence I 'd suggest a call to a routine where the plausibility checks can be made, as well as the insert/maintain of IT 21. 

[jimso101]

Hi Sriram,

From the above dynamic action sequence  i don't think you will get the expected output.The code will only work if there is a change in Marital status. Because you are comparing two values

P0002-FAMST='2' against PSAVE-FAMST='0'.

For eg: During hiring action you are entering Married- Status 1 , while saving the infotype PSAVE - Status is still married which is '1'. I don't think your code has similar scenarios covered. So to list out all scenarios is difficult via dynamic action, so will suggest to go via routine route(creation of routine) which gives more flexibility.

Hopefully this helps.

Thanks & Regards

JIm

[Former Member]

Hi Sriram,

I assume you process IT0002 before 0001 in your action.

Even though you'll have captured the personnel area on the start screen or in the IT0000 screen, IT0001 data will not have been saved yet at that point.

I assume that's why the rule can't fugure out the MOLGA yet and therefore the rule doesn't proceed.

Not 100% sure where it's talking the data from, but seems a logocal explanation. Does it work, if you remove the MOLGA check rule?

SO, you may have to develop some custom routine to achieve this.

best wishes

Sven