Infotype 0008 Not Updated
Hi Gurus,
We have created a dynamic action running in background in order to
update infotype 0008 with the new Grades and Levels of the
employee,when an Organizational Reassignment is executed. However, the
user who executes the action doesn't have sufficient authorization to
display infotype 0008 and this prevents the dynamic action to be
executed,although in background. The customer, cannot give
authorization to the user and the action cannot be executed from users
with appropriate authorization due to business processes. We need to
overcome this, as infotype 0008 contains wrong data.
Steps for Reconstruction
The user executes the action Organizational Reassignment (transaction
pa40)but he has no authorization for infotype 0008. After he saves
infotype 0001, a dynamic action is triggered and checks whether the
employee's job has changed. If yes, the system should execute the
dynamic action in background, in order to update infotype 0008 (both
subtypes 0,9000) with the grades and levels of the new job.
Thanks in advance for help
A mail is sent through dynamic action to the responsible of payroll and he enters the data manually.
Similar Messages
-
Infotype is not updating through 'HR_INFOTYPE_OPERATION'
Hi Frds,
I am trying to update the infotype 2006 leave quota for casual leave. After execution of all code the screen automatically closing itself. Its not modifying the record . I am writing this code in include of exit PBAS0001. Can anybody help regarding this.
CALL FUNCTION 'HR_READ_INFOTYPE'
EXPORTING
TCLAS = 'A'
PERNR = lw_pa0000-PERNR
INFTY = '2006'
BEGDA = '18000101'
ENDDA = '99991231'
BYPASS_BUFFER = ' '
LEGACY_MODE = ' '
IMPORTING
SUBRC =
TABLES
INFTY_TAB = lt_2006
EXCEPTIONS
INFTY_NOT_FOUND = 1
OTHERS = 2
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
read table lt_2006 into lw_2006 with key pernr = innnn-PERNR.
LW_2006-AEDTM = sy-datum.
lw_2006-ANZHL = v_cs_quota.
First Enqueue
CALL FUNCTION 'BAPI_EMPLOYEE_ENQUEUE'
EXPORTING
NUMBER = LW_2006-PERNR
IMPORTING
RETURN = RETURNE.
------------- Update
CALL FUNCTION 'HR_INFOTYPE_OPERATION'
EXPORTING
INFTY = '2006'
NUMBER = LW_2006-PERNR
SUBTYPE = LW_2006-SUBTY
OBJECTID = LW_2006-OBJPS
LOCKINDICATOR = LW_2006-SPRPS
VALIDITYEND = LW_2006-ENDDA
VALIDITYBEGIN = LW_2006-BEGDA
RECORDNUMBER = LW_2006-SEQNR
RECORD = LW_2006
OPERATION = 'MOD'
TCLAS = 'A'
DIALOG_MODE = '0'
IMPORTING
RETURN = RETURN
KEY = KEY.
--------- Dequeue
CALL FUNCTION 'BAPI_EMPLOYEE_DEQUEUE'
EXPORTING
NUMBER = LW_P2006-PERNR.
ENDIF.Thank you, Yes Its updating in 2006....but only sy-datum and username are updating .....Leave quota i am changing from 4 to 3 . its not updating, but showing in screen when i used dialog = 2. Also the same screen appearing 3 times and when i am trying to click on save button its ending with an error 'internal maximum number of sessions reached' , then screen automatically closing by itself.
-
Infotype 0105 not updated via HRUSER
Hi there
I'm currently implementing ESS for SAP R/3 4.7 and running into issues running the HRUSER transaction. I can see a specific employee who has no user account setup but a personnel record in the system. When I select to setup the User ID the program successfully runs in the background but the User ID isn't created and the Personnel Record isn't updated with the Infotype 0105 record. I've ran an authority check and there aren't any failure messages so I'm struggling to see why the Infotype isn't being updated. If anyone could point me in the right direction it would be very much appreciated.
Regards
NathanCheck for the hiring dates of the personnel record. i.e. The employee record is valid on the ID creation date.
-
PPOME - infotype 0000 not update
hello.
is there any way when I change an employee from one position to another using the PPOME it generate a record in infotype 0000? He throws in infotype 0001. ThanksHi Braulio,
Unfortunately no, not in the standard system. When a reassignment is made via PPOME, it is not an action so no IT0000 is created. Since you have intergration between OM and PA, the IT0001 is created to reflect the move, but not an IT0000.
You may be able to create a program or Workflow to create the IT0000 when using PPOME, but there is nothing standard.
Paul -
IDOC_INPUT_HRMD, it posts the document but does not update the Infotypes
Hi,
I am trying to trigger the IDoc Type 'HRMD_A06'. This Idoc was posted successfully, with the status as '53' (inbound IDoc). The Processing Function Module is IDOC_INPUT_HRMD for the IDoc "HRMD_A06". However the infotypes are not updated. The infotypes I am trying to update are 0000,0001,0002,0006, & 0008.
If someone has a solution for this issue. Kindly let me know.
Regards,
NarunHi Srinu,
Again....
Whats happening in Debug ???
Just clone the FM as it is and use the FM HR_INFOTYPE_OPERATION instead of other.
Parameters:
The following code is for infotype 15 inside custom FM which i have done. u can use for ref.
CALL FUNCTION 'ENQUEUE_EPPRELE'
EXPORTING
pernr = l_wa_p0015-pernr
EXCEPTIONS
foreign_lock = 1
system_failure = 2
OTHERS = 3.
IF sy-subrc = 0.
CALL FUNCTION 'HR_INFOTYPE_OPERATION'
EXPORTING
INFTY = c_0015
NUMBER = l_wa_p0015-pernr
SUBTYPE = l_wa_p0015-subty
OBJECTID =
LOCKINDICATOR =
VALIDITYEND = l_wa_p0015-begda
VALIDITYBEGIN = l_wa_p0015-endda
RECORDNUMBER =
RECORD = l_wa_p0015
OPERATION = c_ins1
TCLAS = c_a
DIALOG_MODE = '0'
NOCOMMIT =
VIEW_IDENTIFIER =
SECONDARY_RECORD =
IMPORTING
RETURN = l_i_return .
KEY =
To dequeue the selected employee
CALL FUNCTION 'DEQUEUE_EPPRELE'
EXPORTING
pernr = l_wa_p0015-pernr. -
Not able to modify the data for infotype 0008 using FM
Hi All ,
I have got a requirement for updating the infotype 0008 data using FM : HR_MAINTAIN_MASTER_DATA.
While trying to modify the wagetypes data which is of blank ..unable to upload the amount for that partcular field ..
For this am herewith the link of o/p :
http://i55.tinypic.com/28jfw2c.jpg for this am also posting the code...
Please suggest me furthur in what way i can upload..
SELECT * FROM pa0008 INTO TABLE itab_pa0008
FOR ALL ENTRIES IN itab
WHERE pernr = wa_data-pernr
AND begda = wa_data-begda_out
AND endda = wa_data-endda_out.
DESCRIBE TABLE itab_pa0008 LINES lin.
IF lin EQ 0.
c_action = 'INS'.
ELSE.
c_action = 'MOD'.
ENDIF.
LOOP AT itab INTO wa_itab WHERE pernr = wa_data-pernr.
CLEAR: wa_bapireturn, wa_bapireturn1, wa_hr_return.
REFRESH: it_pprop[],it_modified_keys[].
it_pprop-infty = '0008'.
it_pprop-fname = 'P0008-TRFAR'. "1
it_pprop-fval = wa_itab-trfar.
APPEND it_pprop.
CLEAR it_pprop.
it_pprop-infty = '0008'.
it_pprop-fname = 'P0008-TRFGB'. "2
it_pprop-fval = wa_itab-trfgb.
APPEND it_pprop.
CLEAR it_pprop.
it_pprop-infty = '0008'.
it_pprop-fname = 'P0008-TRFGR'. "3
it_pprop-fval = wa_itab-trfgr.
APPEND it_pprop.
CLEAR it_pprop.
it_pprop-infty = '0008'.
it_pprop-fname = 'P0008-TRFST'. "4
it_pprop-fval = wa_itab-trfst.
APPEND it_pprop.
CLEAR it_pprop.
flag = flag + 1.
*****************************************************************************************************5
BREAK-POINT.
IF NOT wa_itab-lga1 IS INITIAL.
it_pprop-infty = '0008'.
it_pprop-fname = 'P0008-LGA01'.
it_pprop-fval = wa_itab-lga1.
APPEND it_pprop.
CLEAR it_pprop.
bet1 = wa_itab-bet1.
ENDIF.
IF NOT wa_itab-bet1 IS INITIAL.
it_pprop-infty = '0008'.
it_pprop-fname = 'P0008-BET01'.
it_pprop-fval = wa_itab-bet1.
APPEND it_pprop.
CLEAR it_pprop.
ENDIF.
*******************************************************************************************************6
IF NOT wa_itab-lga2 IS INITIAL.
it_pprop-infty = '0008'.
it_pprop-fname = 'P0008-LGA02'.
it_pprop-fval = wa_itab-lga2.
APPEND it_pprop.
CLEAR it_pprop.
bet1 = wa_itab-bet2.
ENDIF.
IF NOT wa_itab-bet2 IS INITIAL.
it_pprop-infty = '0008'.
it_pprop-fname = 'P0008-BET02'.
it_pprop-fval = wa_itab-bet2.
APPEND it_pprop.
CLEAR it_pprop.
ENDIF.
*******************************************************************************************************7
IF NOT wa_itab-lga3 IS INITIAL.
it_pprop-infty = '0008'.
it_pprop-fname = 'P0008-LGA03'.
it_pprop-fval = wa_itab-lga3.
APPEND it_pprop.
CLEAR it_pprop.
bet1 = wa_itab-bet2.
ENDIF.
IF NOT wa_itab-bet3 IS INITIAL.
it_pprop-infty = '0008'.
it_pprop-fname = 'P0008-BET03'.
it_pprop-fval = wa_itab-bet3.
APPEND it_pprop.
CLEAR it_pprop.
ENDIF.
*******************************************************************************************************8
IF NOT wa_itab-lga4 IS INITIAL.
it_pprop-infty = '0008'.
it_pprop-fname = 'P0008-LGA04'.
it_pprop-fval = wa_itab-lga4.
APPEND it_pprop.
CLEAR it_pprop.
bet1 = wa_itab-bet2.
ENDIF.
IF NOT wa_itab-bet4 IS INITIAL.
it_pprop-infty = '0008'.
it_pprop-fname = 'P0008-BET04'.
it_pprop-fval = wa_itab-bet4.
APPEND it_pprop.
CLEAR it_pprop.
ENDIF.
*******************************************************************************************************9
IF NOT wa_itab-lga5 IS INITIAL.
it_pprop-infty = '0008'.
it_pprop-fname = 'P0008-LGA05'.
it_pprop-fval = wa_itab-lga5.
APPEND it_pprop.
CLEAR it_pprop.
bet1 = wa_itab-bet2.
ENDIF.
IF NOT wa_itab-bet5 IS INITIAL.
it_pprop-infty = '0008'.
it_pprop-fname = 'P0008-BET05'.
it_pprop-fval = wa_itab-bet5.
APPEND it_pprop.
CLEAR it_pprop.
ENDIF.
*******************************************************************************************************10
IF NOT wa_itab-lga6 IS INITIAL.
it_pprop-infty = '0008'.
it_pprop-fname = 'P0008-LGA06'.
it_pprop-fval = wa_itab-lga6.
APPEND it_pprop.
CLEAR it_pprop.
bet1 = wa_itab-bet2.
ENDIF.
IF NOT wa_itab-bet6 IS INITIAL.
it_pprop-infty = '0008'.
it_pprop-fname = 'P0008-BET06'.
it_pprop-fval = wa_itab-bet6.
APPEND it_pprop.
CLEAR it_pprop.
ENDIF.
*******************************************************************************************************11
IF NOT wa_itab-lga7 IS INITIAL.
it_pprop-infty = '0008'.
it_pprop-fname = 'P0008-LGA07'.
it_pprop-fval = wa_itab-lga7.
APPEND it_pprop.
CLEAR it_pprop.
bet1 = wa_itab-bet2.
ENDIF.
IF NOT wa_itab-bet7 IS INITIAL.
it_pprop-infty = '0008'.
it_pprop-fname = 'P0008-BET07'.
it_pprop-fval = wa_itab-bet7.
APPEND it_pprop.
CLEAR it_pprop.
ENDIF.
*******************************************************************************************************12
IF NOT wa_itab-lga8 IS INITIAL.
it_pprop-infty = '0008'.
it_pprop-fname = 'P0008-LGA08'.
it_pprop-fval = wa_itab-lga8.
APPEND it_pprop.
CLEAR it_pprop.
bet1 = wa_itab-bet2.
ENDIF.
IF NOT wa_itab-bet8 IS INITIAL.
it_pprop-infty = '0008'.
it_pprop-fname = 'P0008-BET08'.
it_pprop-fval = wa_itab-bet8.
APPEND it_pprop.
CLEAR it_pprop.
ENDIF.
*******************************************************************************************************13
IF NOT wa_itab-lga9 IS INITIAL.
it_pprop-infty = '0008'.
it_pprop-fname = 'P0008-LGA09'.
it_pprop-fval = wa_itab-lga9.
APPEND it_pprop.
CLEAR it_pprop.
bet1 = wa_itab-bet2.
ENDIF.
IF NOT wa_itab-bet9 IS INITIAL.
it_pprop-infty = '0008'.
it_pprop-fname = 'P0008-BET09'.
it_pprop-fval = wa_itab-bet9.
APPEND it_pprop.
CLEAR it_pprop.
ENDIF.
*******************************************************************************************************14
IF NOT wa_itab-lga10 IS INITIAL.
it_pprop-infty = '0008'.
it_pprop-fname = 'P0008-LGA010'.
it_pprop-fval = wa_itab-lga10.
APPEND it_pprop.
CLEAR it_pprop.
bet1 = wa_itab-bet2.
ENDIF.
IF NOT wa_itab-bet10 IS INITIAL.
it_pprop-infty = '0008'.
it_pprop-fname = 'P0008-BET010'.
it_pprop-fval = wa_itab-bet10.
APPEND it_pprop.
CLEAR it_pprop.
ENDIF.
*******************************************************************************************************15
it_pprop-infty = '0008'.
it_pprop-fname = 'P0008-LGA11'.
it_pprop-fval = wa_itab-lga11.
APPEND it_pprop.
CLEAR it_pprop.
bet1 = wa_itab-bet2.
it_pprop-infty = '0008'.
it_pprop-fname = 'P0008-BET11'.
it_pprop-fval = wa_itab-bet11.
APPEND it_pprop.
CLEAR it_pprop.
********************************************************************************************************16
it_pprop-infty = '0008'.
it_pprop-fname = 'P0008-LGA12'.
it_pprop-fval = wa_itab-lga12.
APPEND it_pprop.
CLEAR it_pprop.
bet1 = wa_itab-bet2.
it_pprop-infty = '0008'.
it_pprop-fname = 'P0008-BET12'.
it_pprop-fval = wa_itab-bet12.
APPEND it_pprop.
CLEAR it_pprop.
********************************************************************************************************17
it_pprop-infty = '0008'.
it_pprop-fname = 'P0008-LGA13'.
it_pprop-fval = wa_itab-lga13.
APPEND it_pprop.
CLEAR it_pprop.
bet1 = wa_itab-bet2.
it_pprop-infty = '0008'.
it_pprop-fname = 'P0008-BET13'.
it_pprop-fval = wa_itab-bet13.
APPEND it_pprop.
CLEAR it_pprop.
********************************************************************************************************18
it_pprop-infty = '0008'.
it_pprop-fname = 'P0008-LGA14'.
it_pprop-fval = wa_itab-lga14.
APPEND it_pprop.
CLEAR it_pprop.
bet1 = wa_itab-bet2.
it_pprop-infty = '0008'.
it_pprop-fname = 'P0008-BET14'.
it_pprop-fval = wa_itab-bet14.
APPEND it_pprop.
CLEAR it_pprop.
BREAK-POINT.
CALL FUNCTION 'BAPI_EMPLOYEE_ENQUEUE'
EXPORTING
number = wa_itab-pernr
IMPORTING
return = wa_bapireturn1.
BREAK-POINT.
IF c_action = 'INS'.
CALL FUNCTION 'HR_MAINTAIN_MASTERDATA'
EXPORTING
pernr = wa_itab-pernr
actio = 'INS'
tclas = 'A'
begda = wa_data-begda_out "'20110401'
endda = wa_data-endda_out "'99991231'
dialog_mode = '2'
luw_mode = '1'
IMPORTING
return = wa_bapireturn
return1 = wa_bapireturn1
hr_return = wa_hr_return
TABLES
proposed_values = it_pprop
modified_keys = it_modified_keys.
IF NOT wa_bapireturn IS INITIAL.
WRITE : / wa_bapireturn.
CLEAR : wa_itab , wa_bapireturn.
ENDIF.
ELSEIF c_action = 'MOD'.
CALL FUNCTION 'HR_MAINTAIN_MASTERDATA'
EXPORTING
infty = '0008'
pernr = wa_itab-pernr
actio = 'MOD'
begda = wa_data-begda_out "'20110401'
endda = wa_data-endda_out "'99991231'
record = p_record
recordnumber = wa_itab-SEQNR
operation = change
nocommit = nocommit
dialog_mode = '0'
IMPORTING
return = wa_bapireturn
return1 = wa_bapireturn1
hr_return = wa_hr_return
TABLES
proposed_values = it_pprop
modified_keys = it_modified_keys.
IF NOT wa_bapireturn IS INITIAL.
WRITE : / wa_bapireturn.
CLEAR : wa_itab , wa_bapireturn.
ENDIF.
ENDIF.
CALL FUNCTION 'BAPI_EMPLOYEE_DEQUEUE'
EXPORTING
number = wa_itab-pernr
IMPORTING
return = wa_bapireturn1.
ENDLOOP.
ENDLOOP.Here is a sampe, and the logic you are using for wages goes in the internal table for wages (you already have the enqueue & dequeue so you don't have to worry about that, so you only have to add the BAPI_TRANSACTION_COMMIT):
CALL FUNCTION 'BAPI_BASICPAY_CHANGE'
EXPORTING
employeenumber = pa0008-pernr
subtype = pa0008-subty
objectid = pa0008-objps
lockindicator = pa0008-sprps
validitybegin = pa0008-begda
validityend = pa0008-endda
recordnumber = pa0008-seqnr
payscaletype = pa0008-trfar
payscalearea = pa0008-trfgb
payscalegroup = pa0008-trfgr
payscalelevel = pa0008-trfst
* NEXTINCREASE =
* LOCALALLOWLEVEL =
* PARTNERSHIP =
* CURRENCY =
* COMPARISONPAYSCLTYPE =
* COMPARISONPAYSCLAREA =
* COMPARISONPAYSCLGRP =
* COMPARISONPAYSCLLVL =
* COMPNEXTINCREASE =
* CAPACITYUTILLEVEL =
* HOURSWORKEDPERPERIOD =
* ANNUALSALARY =
* CASEGROUPCATALOG =
* CASEGROUP =
* CURRENCYANNUALSALARY =
* REASON =
* NOCOMMIT =
* importing
* return =
TABLES
wagetypes = wages.
Regards,
Ryan Crosby -
Automatic updation of amount of wage type in infotype 0008 for all live emp
Hi,
Please note that I want to upadate one wage type (9001 - bonus) amount from Rs.2000 to Rs.1950 in infotype 0008 for all the live employees.
If I do the following way -
Payroll: India -- > Reimbursements, Allowances and Perks --> Maintain Pay Scale Groups and Levels
then the new value appears only for new entry in Infotype 0008.
Please advice
Warm Regards
S J Rajamyou can try through fast entry screen and update the amount in infotype.
-
Changes are not updating in infotype 588
Hi,
In 0001 subtype of infotype 0588 , when i try to copy the record into another or change the record,
i am changing the ESI Number ,but this new number is not updating. It is updating with same old number.
What may be the problem?
This problem is coming when i try to create the new record by copying the existing one.
If i create new record normally then it is working fine.
Thanks,
Mamathahi,
I am not copying the infotype. I am copying the record of 588 infotype to create the new one.
thanks and regards
mamatha -
Infotype 0008 wage types are not considered while payroll
Hi Experts,
When i am running the payroll, all the wage types of infotype 0008 is not considered. Neither it is being stored in RT. But all the wage types of infotype 0014 and 0015 are correctly being considered in the payroll. Plz help
Regards
TarunHi,
Plz see the XVAL log that i am getting while running payroll. Do let me know if you need any other information. I can call you now if you say.
PIT XVAL P10 Valuate pay elements
Input
IT
Table IT
PCRlGr Wage salary type WC C1 C2 C3 Assign: AltPa CA BT Abs.
Var s. Unit Rate Number Amount
3 /806 Partial period factor 6 01
100,000.00
3 2000 BASIC SALARY-NEW 01
8,000.00
3 3000 BUS DEDUCTION-HPL 01
1,000.00-
Processing
/806 Partial period factor 6
/806 Partial period factor 6
Rule ESGPCR VaKey Operation
XVAL 3 VWTCL 10
XVAL 3 0 ADDWT *
2000 BASIC SALARY-NEW
2000 BASIC SALARY-NEW
Rule ESGPCR VaKey Operation
XVAL 3 VWTCL 10
XVAL 3 1 ELIMI *
XVAL 3 1 RESET RA
XVAL 3 1 RTE= /801
XVAL 3 1 RESET *
XVAL 3 1 MULTI RAA
XVAL 3 1 AMT/KGENAU
XVAL 3 1 ZERO= R
XVAL 3 1 ADDWT *
3000 BUS DEDUCTION-HPL
3000 BUS DEDUCTION-HPL
Rule ESGPCR VaKey Operation
XVAL 3 VWTCL 10
XVAL 3 0 ADDWT *
Output
IT
Table IT
PCRlGr Wage salary type WC C1 C2 C3 Assign: AltPa CA BT Abs.
Var s. Unit Rate Number Amount
3 /806 Partial period factor 6 01
100,000.00
3 3000 BUS DEDUCTION-HPL 01
1,000.00- -
OM infotypes not updated with relatioship.
Hi Experts,
I made one LSMW to upload info types 0000 (Actions) and 0001 (Org Assignment) using batch input recording method and successfully updated PA infotypes and verified OM info types 1001 (Relationships) for those positions (S) which I assigned new holders (P).
But OM not got updated and is not showing the holder in those positions which I executed action.
Can any tell me why it has not updated OM.
With regards,
Chandrasekhar
Edited by: chandra sekhar on Mar 7, 2009 12:22 PMmeans
run the RHINTE Reports once
before check all the records exists or not
u2022 RHINTE00 - Transfer PA Records To PD Positions. In another world, it creates the HRP1001 between P to S in the OM side of the world. When you view a record via IT0001, you see this person holds the position, however via HRP1001, that relationship isnu2019t so.
u2022 RHINTE10 - Generates the required relevant tables. (T513 - Jobs, T513S - Jobs, T528B - Positions, T528T - Work Center, T527X - Org Unit
u2022 RHINTE20 - checks for all objects for integration between PA and OM. This is a big one and will take awhile to run. What it does is look at table T513/T513T - Jobs, T528/T528T - Position, and T528X - Org Unit. It will then compare it against the HRPxxxx table to find missing objects. If there are any missing objects, it will create the record.
u2022 RHINTE30 - Transfer OM to PA. This will create infotype 0001. If the conversion strategy is to have SAP auto inherit factor to kick in for IT0001, often time jobs and org unit are missing via IT0001 during the inital conversion load. RHINTE30 will find the relationship and push it through IT0001.
Edited by: Sikindar on Mar 7, 2009 12:34 PM -
Problems in updating infotype 0008
Hello,
I' am trying to insert a record into infotype 8. But not all wage type amounts should get reflected in the total salary. How is it possible? Is it through OPKXX field, if so how?
Thanks,
AravindI think that you need to check the section in the IMG under
Personnel Management - Personnel Administration - Payroll Data - Basic Pay - Define annual salary
Under this you can check the "Relevant wage types for annual salary valuation" to check that all of the wage types you created on infotype 0008 are included in the annual salary. -
Impact of NOT UPDATING infotype(Additional Action IT0302)
Hi,
I wanted to know the functional and technical impacts if IT302 is not updated and maintained ?
Regards,
JyotiHi Jyothi shankar,
IT0302- Additional Actions are maintained, if more than one action need to be updated/maintained on the same calendar date!!
Functional: In any organization different actions (say hiring & termination & Promotion & change of Org unit & etc...) can not be done on the same day
Ex: you can not hire and terminate any employee on the same date, isn't it?
that is the reason we have additional actions for any updations required on the personnel action on the same calendar date.
Technical: It will update your records as per the personnel action you run!!
Cheers,
TG -
Infotype 0008 - User Exit Validation
Hi Gurus,
I have to validate infotype 0008 amount fields in PAI user exit ZXPADU02 .
For a scenario, if the amounts are not equal ( BET01 <> BET02) then I have to geneate error message.
Then the user is supposed to correct / re-enter the amounts .
The problem is , when I generate error message , the amount fields are grayed out.
I think this is happeneing cause of standard SAP code ( in flow logic for program MP000800 ) .
Is there any way to generate error message in the user exit and
Give the users an option to update the amount correctly ??
Core mod is the last option.
Appreciate your inputs .
ThanksI solved this problem with:
if BET01 <> BET02.
message 'tekst' type 'S'.
LEAVE SCREEN.
endif. -
Create Wage Type in Infotype 0008 for Myanmar
Dear Experts,
I am trying to create wage types in Infotype 0008 for Myanmar, which is not one of the countries where SAP payroll is being delivered. I am not trying to run payroll, but only to create the wage type so that I can maintain the salary information in Infotype 0008. I have done much searches prior to doing this post and found that there are several other posts which are similar to mine. However, as I could not get the answer that I needed, I am posting again here.
I have gathered that for ECC 6.0, it is not possible to copy wage types between country groupings. The advice that I had seen from other posts are:
1. There are many countries where the wage types are not delivered.
2. For country groupings where there are no SAP-defined wage type models, you have to create wage types from scratch in T512W using MOLGA 99 wage types as reference.
3. The wage type groups should then be created for the country grouping in T52D5.
4. Wage types are then assigned to these wage type groups in V_T52D7 of T52D7.
5. You may also need to update the wage types in tables T511B, T512Z, T512J.
My questions are:
a. How should I perform Step 2 as mentioned above? Specifically, how to I maintain table T512W?
What I had done was to go to t-code OH11, select "Copy", select country grouping as "99" and selected wage type M020. Then I typed the customer wage type number as 1000 and also entered the wage type long text (as shown below). M020 was successfully copied to wage type 1000 in country grouping 99. However, how should I continue from here to copy this wage type 1000 to country grouping Myanmar?
b. How can I maintain T52D5 as mentioned in Step 3?
c. I have not been able to try for Steps 4 and 5 since I was not able to start with Steps 2 & 3. I will ask again when I have managed to do Steps 2 & 3.
Very much appreciate all advice and suggestions to the above.....you can try through fast entry screen and update the amount in infotype.
-
V_T510 and infotype 0008
When updating V_T510 how can i have delimited (automatically) the infotype 0008 for the begin date i have in V_T510 ?
Thanks
MColaço - Somincor PortugalHello , from the sud of Portugal best regards and thanks for your help.
It was very helpful
Even my 510D and 510E are empty ?
Thanks
MColaç
Maybe you are looking for
-
Strugging with exporting data out from an Unicode database
Background information Server: Sun Solaris 5.10; 10g Client: Windows 2000; 10g, TOAD, Oracle ODBC 10.2.0.1 select * from v$NLS_PARAMETERS NLS_LANGUAGE AMERICAN NLS_TERRITORY AMERICA NLS_CURRENCY $ NLS_ISO_CURRENCY AMERICA NLS_NUMERIC_CHARACTERS ., NL
-
Someone used upload files into blob in JDeveloper 10.1.3.2 ?
Someone used upload files into blob in JDeveloper 10.1.3.2 ? I used Steve Muech example 85, but after downloading , downloaded files doesn't work ? I prepared test case http://www.sttb.pl/jakub/UploadAndDownloadBlob.zip - meybe someone resolve it. Re
-
An error occurred downloading iOS 7.0. why ???
please feed back me. thanks!
-
I want to display computer contents (email videos, YouTube videos) on my Panasonic HDTV. Can a model from Jan. 2010 do this? Thanks.
-
How to divide the Prompts window in sections?
Hello, I'm a beginner in Web Intelligence and BO, I have a report with a lot of prompt filters, I want to divide the Prompts window in sections, Is that possible? I'm using web intelligence to generate my reports. Thank you, Marcela