on 09-18-2014 9:44 AM
HI Experts,
I have a requirement wheras the particular WT 6000 is valid till 31.5.2014.Now from 1.6.2014 new WT will get generated as 6005 in place of 6000.THere is already an existing PCR for generation of amount of Wt 6000.So how the new Wt 6005 can be made applicable from 1.6.2014.
Note:We need to keep in mind that old WT 6000 should get generated with existing logic till 31.5.2014 if retro is triggered.
So request you to provide logic to handle this scenario. Is operation CMPER will be useful in this case. If yes then what may be the steps.
Regards
Suman
Can you use this view V_512W_B for your WT6000 and by delimiting the entries give other WT6005 with effective from respective dates in the field of 'Statement WT'.
Please check this in DEV.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Do you want to use CMPER only or else any other ways will it
go.
You can use constant in T511K with validity date and set the validation check
based on the dates
Or else you can use
NUM=YCURYY
NUM=2014
*
<
NUM=YCURPP
NUM=06 (pay
Period)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sikinder,
We have presently implemented the constant date check logic. Please see below logic.Not sure it is correctly working or not. However what happened is, in sept retro entries of WT 8000 has been made for Feb and Jan month. The WT /304 amount and Wt 8000 is used in the calculation of WT 6000.Now from 1.6.2014 WT 6005 is applicable. Now in Sept payroll the retro amounts are incorrect or lets say its equal to WT 8000 value entered in IT0014.But it should not be.Or there is no issues with below PCR logic as per requirement?
Please explain more on your 2nd method more if applicable and where I should put those in the below PCR.
ZAZX
*
****
ADDWT * OT Output table
/304
OUTWPPERSG EE group in v.key
*
ADDWT * OT Output table
4
OUTWPPLANT P.area in v.key
****
ADDWT * OT Output table
AZ00
ADDWT * OT Output table
AMT=KZZAZX Set <------------------- Constant used.
AMT?0 Comparison
=
GCY ZAZXA With exact w.types
>
GCY ZAZXB With exact w.types
A
/304
AMT=* Set
ADDWT&/304 VAR Variable table
ZERO= A AmtNumRteTime = 0
AMT=E 8000 Set
AMT?0 Comparison
=
>
AMT=& /304 Set
AMT+E 8000 Addition
AMT*-1 Multiplication
SETIN R=3 Set Pcalc.rule split
SETIN A=01 Set wrk.center split
ADDWTE6000 RT Results table
ADDWT /110 OT Output table
B
/304
AMT=* Set
ADDWT&/304 VAR Variable table
ZERO= A AmtNumRteTime = 0
AMT=E 8000 Set
AMT?0 Comparison
=
>
AMT=& /304 Set
AMT+E 8000 Addition
AMT*-1 Multiplication
SETIN R=3 Set Pcalc.rule split
SETIN A=01 Set wrk.center split
ADDWTE6005 RT Results table
ADDWT /110 OT Output table
In V_T511K table constant amount given as 1 valid from 1.6.2014 and 0 for till 31.5.2014.
Regards
Suman
Message was edited by: suman das
Hi Suman,
You can go with same pcr with the replace of wage type. Use this two pcr one after another. Then what happend since you told from 01.06.2014 WT6005 will start working and i think it will be handle by maintaining some master data change if i am wrong rectify me.
If it's correct then it would not be effective on the retro case and will work correctly.
Regards,
Sankarsan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
HI Sankarsan,
I think its not going to work.How system will understand that the effective date of WT 6005 is from 1.6.2014.And the retro active accounting from previous month will have to be taken into account. let say they input values for the april month and WT 6000 gets generated. Then there will be a problem.
Regards
Suman
User | Count |
---|---|
85 | |
7 | |
6 | |
4 | |
3 | |
3 | |
3 | |
3 | |
3 | |
2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.