Infotype 0008 BET01 Decimal Out of Place

I'm trying to write a custom ABAP program that reads infotype 0008 and works with the "Wage Type Amount" field (BET01), but I am having trouble getting an accurate value out of it. When I view the data in PA20 or SE16 (looking at table PA0008), the value comes up properly as a value going out to 5 decimal places. In this case, the value is 2,688.10667, which is correct.
When I try and read this value in my program, however, it comes as 2,688,106.67, with the decimal place shifted over 3 places! I have tried reading it using HR_READ_INFOTYPE, direct SELECT statement, and with the decoupled framework, but I get the same result. It seems to be shifting the number over to fill in just 2 decimal places no matter what record I go after.
If it matters, this value is in USD, but I am having the same problem with EUR or any other currency where the value is stretched out past 2 decimal places. It does not appear to be currency-specific.
It seems the displays in SE16 and PA20 can handle it, so I'm guessing there must be some conversion routine, but I don't see one attached to the datatype. How do I get it to return this value correctly?
Thanks in advance.

That's the weird thing. The database field is itself a CURRENCY type with only 2 decimal places. I am using the same datatype in my program as the infotype. How it renders with a different number of decimal places is what I don't understand.
I just found out that someone in my company did find a solution to this problem and created a class method for it. It appears there is a table, TCURX, that lists how many decimal places each currency type is supposed to allow. So using this table we are able to convert the number that comes out of PA0008-BET01 to use the correct number of decimal places. This method should serve my purposes well enough.
This is still confusing, though, as this is a custom solution and I doubt it is being referenced by SE16 or PA20 when those transactions display the value. It behaves as if there is a conversion routine attached to the datatype, but the Data Dictionary does not show any. How are SAP programs doing this conversion?

Similar Messages

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 .
Thanks

I solved this problem with:
if BET01 <> BET02.
message 'tekst' type 'S'.
LEAVE SCREEN.
endif.

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

How make display only the amount field in table control(infotype 0008)

Dear Freinds,
have to make display only the amount field (Q0008-bet01) on table control in infotype 0008 , could you tell me how to make it display only.
i have tried the below coding it is not working in PBO & PAI of the user exit
ZXPADU01 and ZXPADU02. For the table control is there any othe method??
       loop at screen.
           screen-name = 'WA_P0008-BET01'.
          screen-input = 0.
          screen-output = 1.
          modify screen.
      endloop.
i have tried like this as well
       loop at screen.
           screen-name = 'Q0008-BET01'.
          screen-input = 0.
          screen-output = 1.
          modify screen.
      endloop.
in the both the above methods it is not working. Could any one plese suggest me how to make display only the amount field in infotype 0008.
regards
syamla

Dear Freinds,
have to make display only the amount field (Q0008-bet01) on table control in infotype 0008 , could you tell me how to make it display only.
i have tried the below coding it is not working in PBO & PAI of the user exit
ZXPADU01 and ZXPADU02. For the table control is there any othe method??
       loop at screen.
           screen-name = 'WA_P0008-BET01'.
          screen-input = 0.
          screen-output = 1.
          modify screen.
      endloop.
i have tried like this as well
       loop at screen.
           screen-name = 'Q0008-BET01'.
          screen-input = 0.
          screen-output = 1.
          modify screen.
      endloop.
in the both the above methods it is not working. Could any one plese suggest me how to make display only the amount field in infotype 0008.
regards
syamla

Infotype 0008 in Recruitment

Hi Experts,
I have a problem with the Infotype 0008 in Recruitment.
When I try to create a new record through transactions PB30 or PB40, I meet the following error:
No entry in table T510 for the key 99    2B3
    Message no. RP100
I tried to customize the table t510, but I don't know how to customize it for applicants.
May you suggest me, please, the customizing step I have to perform?
Thank you very much!

Dear Ema,
                     I have such type of requirement in my client place. So to store data in infotype-8 I have made such type configuration.I think this will help you to solve the problem.
1. Maintain the payscale type & Area
2. Maintain the feature for PS Typae & Area In TARIF Feature as per your requirement
3.Maintain the table revise pay scle group & Level (t510) wher you have to insert the wage type which need to be auto defaulted in Infotype -8
5.Then create the wage type model in Revise Default Wage types.
6. Then maintain the feature LGMST as per the below instructions-
Under the specified country grouping go for creation of structure select the field for decision operation & select the node-TCLAS Transaction Class for Data Retention. Under this go for again creation & select- A -Master Data and Time Data &
B- Applicant Data., Then under Applicant data maintain the Wage type models as per your requirement.
Bleo is the configration I have made in my client Place.
40 India
TCLAS Transaction Class for Data Retention
A Master Data and Time Data
        B Applicant Data
WERKS Personnel Area
1000 Corporate
PERSG Employee Group
B Manager
PERSK Employee Subgroup
M1 Official
                                  M2 Monthly wage earner
                                  M3 14-day wage earner
                                  M4 Weekly wage earner
D Executive
8000 Novodigm Limited
otherwise
7. Then go to PB 30 & maintain Applicants Contract element -Infotype-16 wher you have to specify the EG & ESG.
8. Then select infotype -8 and go for creation & now you can able to create the infotype for the applicant.
I think this will solve the problem.If any query pl. contact me in this no-9702519630.
Snita.

Out-of-place upgrade to 11.2.0.4 (from 11.2.0.3); how does it affect certain items?

Hi All,
I've never done a db patch set update, and from what I've read today, I will need to do a full installation of 11.2.0.4 to have this patch set applied.
This sounds scary and being a rookie Oracle DBA, what does this mean to my existing Oracle Database installation (Oracle 11GR2 on Windows Server 2008R2)?
If I do an out-of-place upgrade (Oracle recommended), and create a new home, what will happen to the existing schemas/etc?
My application is configured to connect to SERVERA, SID=123 so when I install a new home, etc, does this change anything? I've read I need to modify the tnsnames files in my new home to be similar to my current tnsnames file..
Basically, I want to upgrade to patchset 11.2.0.4 b/c it's supposed to address a bug I have, but I want to be able to keep the 'settings' the same for the end users/applications (SERVERA, SID=123).
Thanks in advance

You have to remember that the database software/binaries are separate from the database itself. Typically, you first install the software (like you did for 11.2.0.3) and then create a database. Best practice states that the location of the database files should be outside/different then the location of the binaries.
When you install your new 11.2.0.4 in a new location, that is all that you are doing - the install does not affect the existing database. Once the 11.2.0.4 software is installed, you can upgrade the database by following the steps in the upgrade guide (the database files stay where they are, but the database gets upgraded from 11.2.0.3 to 11.2.0.4) and when the upgrade is completed successfully, the old (11.2.0.3) binaries can be de-installed at leisure.
HTH
Srini

HR ABAP infotype 0008

Hi All,
Please see my below requirement.
i got 2 periods in infotype 0008(in the datailed view)
1.03/31/2009-12/31/9999 and amount is 1500(Present period)
2.01/01/2007-03/30/2009 and amount 1000.(Previous Period)
I want to get the amount from the previous period.that is 1000.
Can you please let me know how to achive this and how to capture previous period.
Regards,
Phani.

Hi Phani,
i got 2 periods in infotype 0008(in the datailed view)
1.03/31/2009-12/31/9999 and amount is 1500(Present period)
2.01/01/2007-03/30/2009 and amount 1000.(Previous Period)
I want to get the amount from the previous period.that is 1000.
You can code something like below:
Select * from PA0008 INTO TABLE l_t_it0008 WHERE Pernr EQ l_pernr.
SORT l_t_pernr DESCENDING BY ENDDA.
READ TABLE l_t_it0008 sy-tabix EQ 2 INTO l_wa_it0008.
Regards
Shital

Infotype -0008 (Changes)

Hi,
The query was if any Change are made in Infotype 0008, by any users if he has authorization of PA30, to change or delete etc.
The client Wantu2019s an email should generate if any changes are made to Infotype 0008.and that mail has to go to the respective head
Any standard report or any customization step pls tell
Regards,

Try Dynamic Actions. Go to SM30 --> t588z --> Maintain.
Enter:
Itype : 0008
Fieldname : Any infotype field in IT0008 whose change has to trigget a mail
FC: Choose function code 2 digits as required (press F1 on the field for further information)
No: Enter a sequence number
S: Choose M(Send Mail)
Variable Function part : Trigger Feature name - Ex. M0001 (press F1 on the field for further information)

Audio out of place when transferring iMovie to iDVD

I've made a movie in iMovie 09 that runs just how I want it to in iMovie. However when I transfer it (via sharing with the media browser) to iDVD and preview it (or watch the film on a burnt DVD) towards the end of the movie the audio from the final 6 or 7 clips is played about 45 seconds before the clips themselves occur. The audio also then plays (correctly) with the clip. I have tried detaching the audio from these clips, as some forums seem to suggest but it still turns up in the incorrect place (before the clips themselves). I have tried deleting and reintroducing the offending clips but am wondering if I could have somehow copied and placed the audio to these clips at the wrong place on the project timeline - and for some reason can't see it?
It's a 23 minute movie that is now ruined by out of place audio right at the end so any help much appreciated.
I'm using: iMovie '09 version 8.0.6 and iDVD 7.1.2 on a Macbook Pro 2.4GHz Intel Core i5, OSX version 10.9.4
Thanks

Are you able to exert the movie to the Desktop and play it with Quicktime Player with all audio OK? What format are the audio clips. Some report best results with AIFF.
iDVD has a bug that if any of the video media is edited after having been added to the project the resulting DVD is compromised. Therefore try creating a new project entirely.
Follow this workflow to help assure the best qualty video DVD:
Once you have the project as you want it save it as a disk image via the File ➙ Save as Disk Image menu option. This will separate the encoding process from the burn process.
To check the encoding mount the disk image, launch DVD Player and play it. If it plays OK with DVD Player the encoding is good.
Then burn to disk with Disk Utility or Toast at the slowest speed available (2x-4x) to assure the best burn quality. Always use top quality media: Verbatim, Maxell or Taiyo Yuden DVD-R are the most recommended in these forums.

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 Rajam

you can try through fast entry screen and update the amount in infotype.

Default Pay scale group and Level in infotype-0008

Hi,
While hiring should display the default Pay scale group and Level in infotype-0008 or the pay scale group and level can default from the Job or position. Itu2019s possible? Thanks in advance.
Regards

No there is no standard Feature to default PSG and PSL. TARIFF is for PSA and PST.
Wait for some body may have some information.
Afrasyab

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 Portugal

Hello , 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ç

Authorization for Infotype 0008

Dear Experts,
I am new for SAP HR module, and I am facing one authorization issue.
It is about the PA30 authorization for Infotype 0008, I want to restrict user ( ext_test) who can change Infotype 0008 for person ID 44000156, Employee group 1, Employee subgroup EP(ETXAT).
And I create the role for T-code PA30.
In the P_ORGINCON object, I configure the activity as following :
Authorization level            E, R, S                                                                      AUTHC
Infotype                           0008                                                                          INFTY
Personnel Area                *                                                                               PERSA
Employee Group              1                                                                               PERSG
Employee Subgroup         EP                                                                            PERSK
Authorization Profile         *                                                                               PROFL
Subtype                          ' ', 0                                                                          SUBTY
Organizational Key          *                                                                               VDSK1
But when I execute PA30 with person ID 44000156, and want to change Infotype 0008, It shows that I miss the authorization.
The result of SU53 are
Authorization level            E
Infotype                           0008
Personnel Area                *
Employee Group              *
Employee Subgroup         *
Authorization Profile         *
Subtype                          0
Organizational Key          *
I don't know why it asks the * authorization for Employee group and subgroup even I want to chagne the data which are fit my created authorizations.
Could anyone give me some advice?

Dear Amamath,
Employee group is 1 (Direct), and subgroup is EP ( Expat).
I don't know if it is possible if I want to restrict the authority as following:
I have two person ID, one is 44000156, the other is 44000246.
44000156 has Employee group 1(Direct) and subgroup EP(Expat)
44000246 has Employee group 2(Indirect) and subgroup 3(Management)
I want to restrict the authority that end user can only change Infotype 0008 for the person which subgroup is EP ( No matter the Employee group is 1,2, or 3).That is , in this case, I can only change 44000156 basic pay but not 44000246.
So in the P_ORGINCON object, I restrict the Authorization level as "E,M,and R); Infotype as "0008"; and subgroup as "EP".
After that , I did the test with end user's accout. then SU53 shows that it need to have Employee subgroup = "*".
I don't know why it need the * authority for Employee subgroup. I should be able to change 44000156 since I granted the subgroup "EP" to end user account.

Create, but no changes in Infotype 0008

Hi all,
We have the following issue in HR authorization
There's one role with some transactions of HR, some of them is PA30 and PA40.
One of the rules at the company is, in transaction PA40, the person who made the admission of an employee, can register the salary data (IT 0008);
And later, the same person can consult this register of employee by transaction PA30, but cannot change the salary in Infotype 0008, only the manager could do this.
But, both transactions uses the same object (P_ORGIN).
The question is, this type of restriction (register salary in PA40, and only consult in PA30) can be made only in authorization profile (PFCG)?
How can we do this?
Thank you all!

Hi,
When you add both PA40 and PA30 tcodes into the same role. You can actually restrict the Infotype 0008 and its Subtype in the same role.
You can give restrict authorizations to only register salary and only consult via the field values in P_ORIGIN.
Regards,
Kiran Kandepalli.

Infotype operation on infotype 0008

Dear Freinds,
            While using the HR_INFOTYPE_OPERATION for the infotype 0008 , i have one specific problem being encountered .
the scenario is when iam having multiple Wage types for an employee..then i couldnt upload all the wages types . Only the
the wage type which is last one is being uploaded .
ex
pernr        wage type
1001          101
                 102
                 103
so when i see after uploading the data for the employee no
1001 only the wage type 103 being uploaded but not 101 & 102 at all.
could any one please let me know what i should do in order to get all the wages types.
Thanks & regards

In the record you have to fill diferent fields, if you have more then one wage you have to fill fields LGA01, LGA02, LGA03 and so on. I dont know what your input is (file or database) but i sugest creating the internal table with the same field names and then move-corresponding itab to it0008. If you specify a bit more i can give you an more exact example.

Infotype 0008 BET01 Decimal Out of Place

Similar Messages

Maybe you are looking for