Infotype 0008 using SEQNR?

Hi,
Anyone here have gone down the path of using SEQNR on infotype 0008? Is it possible to do so?
For example, a person transfering from LA to London received a position promotion increase, cost of living adjustment, and internal equity adjustment.
True, you can do it via infotype 759 w/ ECM module, but there are situation where things shouldn't be in 759 ECM module and goes directly on IT0008.
In situation as described and SEQNR is not the method to go down, what have everyone done in this situation?
Thanks!
KN

Yea you could..
But what if you have more than one type of pay changes and want to capture the differences
for example promotion increase is 1000, relocation is 500, etc..which makes up a new basic pay...So we know which is which...
w/o going down the route of recording everything in infotype 0759...

Similar Messages

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

Modify Infotype 0008 using BADI or EXIT - How to?

Hi,
How to modify the values for infotype '0008' in save moment, using a EXIT or BADI????
What EXIT or BADI to use for this?
Thanks,
Daniel

Use Exit FM: EXIT_SAPFP50M_001 for setting default values and Exit FM: EXIT_SAPFP50M_002 validations for various infotypes(including IT0008) by enhancing PBO and PAI includes respectively.
for Example.
When copying an infotype 0008 record, the reason code *should be cleared.
INCLUDE y_zxpadu01_08.
Data declaration.
DATA: BEGIN OF wa_am7912_0008.
        INCLUDE STRUCTURE p0008.
DATA:   filler(1500) TYPE c,
      END OF wa_am7912_0008.
Only perform for 0008 infotypes....
IF innnn-infty = '0008'.
...that are being copied only....
    IF ipsyst-ioper = 'COP'.
    .....and that are being called manually.
      IF ipsyst-inpst = '0'.
      Parse the data.
        CLEAR wa_am7912_0008.
        wa_am7912_0008 = innnn.
      Clear the reason code.
        clear wa_am7912_0008-preas.
        clear innnn.
        innnn = wa_am7912_0008.
      endif.
    endif.
endif.
Regards,
MM

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?

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.

Updating infotype 0041 using HR_INFOTYPE_OPERATION?

Hi All:
How do we update the dates in infotype 0041 using HR_INFOTYPE_OPERATION? lets say we have 6 dates populated in 41 and we another employee has 9 dates populated. We are reading these records and need to update the dates for all the employee records.
Thanks
Venkata

Hi Venkata,
What you can do is use the HR_INFOTYPE_OPERATION in Change or MOD(Modify) mode i.e.
pass 'MOD' in operation parameter.
Your recordnumber parameter should have the sequence number from infotype record you are updating (field SEQNR). All other parameters should be as it is had been for INS or insert operation.
Regards.

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 reecord creation in a BAdI - Issue

I am implementing the method 'CALC_SAL_ADJUSTMENT' of the BAdI definition 'HRECM00_ACTIVATION'. As per the requirement, I have to copy the record in the importing parameter IT0008_OLD, make some modifications to the record and then pass it on to the exporting parameter IT0008. Simultaneously, a new infotype 0008 record has also to be created based on the data in the new record IT0008. I tried using the FM 'BAPI_BASICPAY_CREATESUCCESSOR', since this will also delimit the previous record.
**Create a new Infotype 0008 record, delimiting the previous record
CALL FUNCTION 'BAPI_BASICPAY_CREATESUCCESSOR'
EXPORTING
employeenumber = pernr
subtype = it0008_old-subty
validitybegin = effdt
validityend = c_endda
payscaletype = it0008_old-trfar
payscalearea = it0008_old-trfgb
payscalegroup = it0008_old-trfgr
payscalelevel = it0008_old-trfst
nextincrease = it0008_old-stvor
localallowlevel = it0008_old-orzst
partnership = it0008_old-partn
currency = it0008_old-waers
comparisonpayscltype = it0008_old-vglta
comparisonpaysclarea = it0008_old-vglgb
comparisonpaysclgrp = it0008_old-vglgr
comparisonpayscllvl = it0008_old-vglst
compnextincrease = it0008_old-vglsv
capacityutillevel = it0008_old-bsgrd
hoursworkedperperiod = it0008_old-divgv
annualsalary = v_annsal
casegroupcatalog = it0008_old-falgk
casegroup = it0008_old-falgr
currencyannualsalary = it0008_old-ancur
reason = it0008_old-preas
nocommit = space
IMPORTING
return = wa_return
employeenumber = v_empno
subtype = v_subty
objectid = v_objectid
lockindicator = v_lockind
validitybegin = v_valbegin
validityend = v_valend
recordnumber = v_recordno
TABLES
wagetypes = it_bwagetype.
However, it is raising an exception 'cx_hrpa_violated_precondition', which is not caught and hence a run-time error.
I tried using the above function module in a report program and it worked fine.
Can anybody please let me know, whether it is possible to create an infotype 0008 record inside the above BAdI implementation? and if yes, where am I going wrong?
Thanks in advance.
Sujit.

put the BAPI call as a BACKGROUND TASK & try it..
~Suresh

Infotype 0008 check to Job code

Hi All !
I need to check the employee Grade with the Job code. For Example if the employee Job Is Assistant Manager / Manager / Senior Manager his Grade in infotype 0008 should not less than 32 or in range some where between 32 to 35. Any suggestion by standard as Dynamic Action not working .
Thanks in Advance
Regards
SBA

You can use IT 1005 in OM for this. Refer http://help.sap.com/saphelp_46c/helpdata/en/66/9bb8923aff11d189370000e829fbbd/content.htm

Infotype 0008 wage-type issue.

Hi all,
An hiring action was run for a new employee and subsequent information was input in PA30.Along with other information wage-type was filled in Infotype 0008.
Problem: When we check the corresponding transparent table PA0008 we are unable to find wage type or amount entry there. But when we retrieve the same in PA30 we get all the information along with wage-type and amount.
Can someone please tell as to where the data is getting retrieved from if it is not saved in PA0008.
Thanks and Regards,
Ribhu

Hi Ribhu,
You have to retrieve data through the Reports only because data of IT8 is stored in the infotype only and we cannot check the data from the database table .
It is suggested to get the Report or use standard report.
Manoj Shakya.
Technical-Fuctional Consultant
SAP-HR
******(Useful answers should be rewarded)

Infotype 0008 master data with no salary and no wage types.

I am an abapper so I apologise whole heartedly in advance for what may be a silly question.
I want to use infotype 0008 only to hold master data values. The only fields I want filled are:
Pay Scale Type,
Pay Scale Area,
Pay Scale Group,
Pay Scale Level,
Capacity utilization level.
Is it possible to configure infotype 0008 just to enter these values and nothing else. I don't any values in Annual Salary, Wage types, etc.

Dear Gemini,
You can hide some of the fields if you donu2019t want to display or you can make them Output fields (table name T588M, and select the module pool, MP000800).
Thanks
Haji

Infotype 0008 and Wage Type Amount

Hi ,
I can see the Wage type in infotype 0008 , but when I input an amount in "Annual salary" , the Wage type Amount is not calulated ( stay blank ) .
The Wage type Amount should be = Annual salary / PFREQ .
What did I miss ? Feature PFREQ and LGMST are setup . Can see the Wage Type , but no calculation is done ?
Help will be rewarded
Thank you.

Hello there!
There are 3 important things to note in ANSAL.
1. Period Parameters - Table T549R
2. Annual Salary Wage Type - When you are defining the characteristics you will have to use ANSAL as Indirect evaluation module
3. Monthly/Period Wage types - the wages which will make the sum for Annual Salary.
Try to complete all the steps present in PA-> Payroll Data -> Basic Pay -> Define annual salary.
Thanks
Yash

MSS approval application without infotype 0008 ?

The MSS webdynpro application, which is calling functionmodule HRMSS_CAT_WD_APPROVAL, crashed with error "IT0008_NOT_FOUND".
I added the infotype in PA30 to the manager, and now the application is working fine.
However, we are not using SAP as payroll system, and really do not want infotype 0008, Basic pay, in our master data, since we have to put a value 1, into basic pay for all employees.
It does not make sense to store garbage data in the system.
How to solve this issue ?

Hi Henrik,
We are facing similar error message in the MSS team calendar. Wonder if you can let me know how the issue got resolved.
Many thanks,
Terence
P.S: issue resolved by applying SAP note 1131910 hence, no response requested
Edited by: Terence Bosco on Sep 9, 2009 5:54 PM

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.

How to retrive data from infotype 0008 &0021 and dispaly as alv output

hi all,
i have to read data from infotype 0008 and infotype 0021 and display as alv grid..
can any one help me..
<removed by moderator>
regards,
viswanath
Moderator message: please search for information and try yourself before posting here.
Edited by: Thomas Zloch on Jan 12, 2012

Hello Sourabh,
If I am not wrong, there are two parts two your query...
a) Data or Content Retrieval
b) Displaying Retrieved content
Here is my feedback
a) The Content can be Retrieved using the FM ARCHIV_GET_TABLE.
Pass the Archive Object, SAP Object and the SAP Object ID and based on the Connection table entries (TOA*), the underlying Content Repository (T-code OAC0) is determined and a request for synchronous retrieval is made to the Content Server.
b) Display of Retrieved content is normally done through dedicated viewers (Ex: Livelink Viewer) or front-end applications (Excel, Word) based on the Protocol (OAA3/OAA4) specified in the Content Reository Configuration. Hence, to my knowledge, you cannot display the content directly in the Smartform.
With Regards
Vijay Gajavalli

Infotype 0008 using SEQNR?

Similar Messages

Maybe you are looking for