Infotype 0008 error for Brazil

I am trying to run the confirmation ation for brazil employee, in the middle of the month.
but then infotype 8 is throwing error saying " Accorning to Law salary increase should begin on the 1st day of month."
the problem did not occur for other countries, though the confirguration is same. and Infotype 8 is in COP mode for CN- confirmation action
maybe someone might be having some idea about it.
Please do let me know.

Hi,
seems that local law prohibits mid-month salary changes.
I would ask local (brazilian) experts whether such a law indeed exists....
Wilfred.

Similar Messages

Infotype 0008 error

While creating reason for change in IT 0008 , showing abap runtime error when trying to save the description.

Good to see you after a long time
Can u let us know wht is the error you are getting........
and check with your ABAPER also ......
hope everything is fine from your side

Deletion of infotype 0008

Dear Team,
One of our client wants to delete the infotype 0008.
Kindly suggest how can we delite.
Thank you,
Regards,
Rakesh

Hi Rakesh,
In case payroll is executed for the particular employee / group please delete the results before you delete the infotype 0008. PU01 is the T-code to delete the payroll results. Once the results are deleted and then delete the infotype 0008 through tool bar -> Utilities-> delete personnel no -> Infotype 0008. For your reference find the screen shot below
PU01 ->
Deletion of Infotype 0008
Regards,
Basanthi

Error in Infotype 0008 Basic Pay

Hi,
I got an error in Infotype 0008 Basic Pay : as below
"Basic salary is not part of the pay components
Message no. HRPADIN01135"
I've copied the below 4 wage types and configured in IMG Activity, but when I tried to enter in Infotype 0008 Basic Pay, got the above message as Basic Salary is not part of the pay Components.
1000-Basic Pay
1001-HRA
1002-Convance allowance
1003-Fixed DA
Kindly inform me where might be the problem, in which configuration.
Awaiting your suggestions.
Regards,
Sree.

Hi Prashanth,
Firstly thank you for your reply.
After entering i get another error message with regard to Retroactive Accounting period, as below:
"Enter data for payroll past (retroactive accounting)
Message no. PG131
Diagnosis
The current entry begins on 15.03.2009. Either this date is before the 'accounted to' date, or payroll has not been run for the employee.
System Response
The recalculation date in infotype 0003, Payroll Status, is set to the begin date of the current entry.
A recalculation will be triggered for this employee in the next payroll run."
And if I still go for saving the same, ABAP Runtime Error will come and it shows as below:
Runtime Errors : WRITE_TO_OFFSET_TOOLARGE
Date and Time : 20.03.2011 17:53:56
Program error: Offset in WRITE TO in program "SAPFP500" is too large.
Kindly suggest me, awaiting your reply,
Regards,
Sree.

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

Error while posting GR with MvT 835 for Brazil Plant using transaction MBSU

Hi,
While posting GR with MvT 835 through transaction MBSU with reference to GI document, we are receiving below error :-
Balance not zero: **** - debit: ****
credit: ****
Message No.: M7050.
We are using TAXBRA procedure for Brazil.
We request you to please let us know what all configuration do we need to check.
Regards,
Kiran

Answered.

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.

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.

Personal Profile service for Brazil - Type Conflict for infotype 0002

Hello All,
We are enabling personal profile service for Brazil. And we did all the required configuration for that.
When I access the personal info service I can see the overview page with personal data. But when I click on display link, I get the error message saying -
Type conflict with ASSIGN in program CL_HRPA_UI_CONVERT_0002_BR
Is there any configuration missing?
Thanks,
Bhushan

Short text
    Type conflict with ASSIGN in program "CL_HRPA_UI_CONVERT_0002_BR====CP".
What happened?
    Error in the ABAP Application Program
    The current ABAP program "CL_HRPA_UI_CONVERT_0002_BR====CP" had to be
     terminated because it has
    come across a statement that unfortunately cannot be executed.
What can you do?
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
Error analysis
    You attempted to assign a field to a typed field symbol,
    but the field does not have the required type.
How to correct the error
    Adapt the type of the field symbol to the type of the field or use an
    untyped field symbol or use the "CASTING" addition.
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "ASSIGN_TYPE_CONFLICT" " "
    "CL_HRPA_UI_CONVERT_0002_BR====CP" or "CL_HRPA_UI_CONVERT_0002_BR====CM003"
    "IF_HRPA_UI_CONVERT_STANDARD~OUTPUT_CONVERSION"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
       To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
       Display the system log by calling transaction SM21.
       Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
       In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
Line SourceCde
    6   DATA: attributes           TYPE hrpad_field_attribute_tab.
    7   DATA: l_object_key         TYPE hcm_object_key.
    8   DATA: l_subrc              TYPE sysubrc.
    9
   10   FIELD-SYMBOLS <r0002_br>   TYPE hcmt_bsp_pa_br_r0002.
   11   FIELD-SYMBOLS <p0002_br>   TYPE p0002.
   12   FIELD-SYMBOLS <p0625>      TYPE p0625.
   13
   14   is_ok = if_hrpa_ui_convert_standard~true.
   15   ASSIGN screen_structure    TO <r0002_br>.
   16   l_object_key = <r0002_br>-object_key.
   17   MOVE-CORRESPONDING pnnnn TO super_screen_ref.
   18
   19   CALL METHOD super->if_hrpa_ui_convert_standard~output_conversion
   20     EXPORTING
   21       screen_structure_name = a_super_screen_structure_main
   22       pnnnn                 = pnnnn
   23       message_handler       = message_handler
   24       field_metadatas       = field_metadatas
   25     IMPORTING
   26       screen_structure      = super_screen_ref
   27       is_ok                 = is_ok
   28       field_attributes      = field_attributes.
   29
   30   MOVE-CORRESPONDING super_screen_ref TO screen_structure.
   31
   32   CASE a_super_screen_structure_main.
   33     WHEN 'HCMT_BSP_PA_XX_R0002'.
   34       ASSIGN pnnnn                  TO <p0002_br>.
   35       ASSIGN screen_structure       TO <r0002_br>.
>>>>>       ASSIGN pnnnn2                 TO <p0625>.
   37       MOVE-CORRESPONDING <p0002_br> TO <r0002_br>.
   38       MOVE-CORRESPONDING <p0625>    TO <r0002_br>.

Country specific infotypes for brazil and argentina

Dear All,
We are going for implementation of our client for brazil and argentina........can any body guide with country specific infotypes for the same

Hi,
Brazil:
Infotype 0398: Agreement Components: Further Information
Infotype 0397: Information about Dependents
Infotype 0410: Transportation Allowance
Infotype 0437: Simultaneous Jobs
Infotype 0661: Employment Contract Termination
Infotype 0598: Dismissal Protection
Infotype 0185: Personal IDs
http://help.sap.com/saphelp_erp60_sp/helpdata/en/0f/1605350928385ee10000009b38f844/frameset.htm
Argentina:
Family Data Infotype: Special Schooling Assistance
Termination of Contract Infotype (0551)
Infotype Social Insurance (0392)
Income Tax Infotype (0389)
Income Tax: Deductions Infotype (0390)
Income Tax: Other Employer Infotype (0391)
Infotype Life Events for My Simplification (0875)
http://help.sap.com/saphelp_erp60_sp/helpdata/en/ee/28fd346f0f4661e10000009b38f844/frameset.htm
Cheers

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.

HR_INFOTYPE_OPERATION 0008 Error

hi guys,
i am using HR_INFOTYPE_OPERATION FM to upload data at infotype 0008 (basic pay).
i get a short dump error with the following message:
Error analysis
    You cannot call a COMMIT WORK in a FORM not executed by the variants
    PERFORM ... ON COMMIT or PERFORM ... ON ROLLBACK until the commit of the
     calling program.
i did the nocommit = 'X' parameter for the FM, then COMMIT WORK later at the program.
dump still appears.
if i remove that parameter, and the COMMIT WORK as well, i still get the same dump.
if i assign nocommit = space or remove it at all, no dump happens, but IT0008 is not updated as well.
i tried my same code with other infotypes, with nocommit = 'X' and COMMIT WORK later in the program.
it works fine. no dumps.
it seems that i only get the dump at infotype 0008.
any ideas what is happening?
anyone had the same problem at infotype 0008?

Hi,
R u adopting the parameters in the following way.
CALL FUNCTION 'HR_INFOTYPE_OPERATION'
    EXPORTING
         INFTY            = '0008'
         NUMBER           = OLD_P0008-PERNR
         SUBTYPE          = OLD_P0008-SUBTY
         OBJECTID         = OLD_P0008-OBJPS
         LOCKINDICATOR    = OLD_P0008-SPRPS
         VALIDITYEND      = OLD_P0008-ENDDA
         VALIDITYBEGIN    = OLD_P0008-BEGDA
VALIDITYEND      = I0573-endda*
VALIDITYBEGIN    = I0573-begda*
         RECORDNUMBER     = OLD_P0008-SEQNR
         RECORD           = I0008
         OPERATION        = OPERN
         TCLAS            = 'A'
         DIALOG_MODE      = DIALOG_MODE
NOCOMMIT         =*
VIEW_IDENTIFIER =*
SECONDARY_RECORD =                             IMPORTING*
        RETURN           = BAPISUBRC
        KEY              = INFTY_KEY.
Thanks
Pavan

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.

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.

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

Infotype 0008 error for Brazil

Similar Messages

Maybe you are looking for