PPOME: Error in Infotype Tabpage

Hello Experts,
I had a requirement to add CUSTOMER infotype "9610" as a tabpage in PPOME , i was did all
required updations to get it in PPOME. Now i can view "9610" infotype in PPOME.
Problem : In this tabpage iam getting " Record 1 of 1 " (which we can normally able to see at PP01
                at infotype records view). Normally this field "PPHDX-RECORD_NR" exist at 2000 screen but
                its getting in the tabpage of PPOME. I was created a subscreen-7000 for getting tabpage at
                PPOME.
Please suggest !
~Scogni

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.

Similar Messages

Iam getting any error in infotype 0002 while doing enhancement ...

Dear all
could any one let me know why iam getting this error ,
" TABL HRTIM00WS_PWS_INFTIES was adjusted
Check table HRTIM00WS_PWS_INFTIES (SFCD07/13.06.07/11:34)
Enhancement category for table missing
Enhancement category for include or subtype missing
Field name TIME is reserved (Do not use structure as include in DB table)
Table HRTIM00WS_PWS_INFTIES was checked with warningsif iam doing
enhancement for infotype 0002 ....
i have just added an one custom field ...(zzname , data element is zzname type char 20)as per the business requirement.
regards
vamsi

Iam getting any error in infotype 0002 while doing enhancement .
" TABL HRTIM00WS_PWS_INFTIES was adjusted
Check table HRTIM00WS_PWS_INFTIES (SFCD07/13.06.07/11:34)
Enhancement category for table missing
Enhancement category for include or subtype missing
Field name TIME is reserved (Do not use structure as include in DB table)
Table HRTIM00WS_PWS_INFTIES was checked with warningsif iam doing
enhancement for infotype 0002 ....
when iam activating .................the structure i got the above error...........please urgent i have just added only one field

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.

Error PG008 - Infotype does not exist message

I created a custom HR infotype in our development client and tested it via PA30 and it works fine. Once transported over to the Test client I am getting a 'Infotype does not exist' message in PA30. I checked all of the transports and config and the only table where I can see a difference is in the T591A table. This infotype does not contain any subtypes and when I access this table in the Development client I get a 'no data for IT9013' message. When I try to access this table in the Test client I get the 'Infotype does not exist' message. Does anyone know what I may have missed or how I can correct this? Thanks!!

Please check your transport log in SE09 for any warnings or errors.
thanks.
JB

Error in infotype 0021 - Entry 14 1 04 does not exist

Hi experts,
I have one problem during key-in infotype 0021. When I choose fields relation, this message appear, '14 1 04 does not exist'.
Actually I have add data in table V_T577.Is that any config I should do besides this table. Thanks in advance

HI,
Please elaborate, do you mean that you are getting this error while selecting subtype for IT0021?
Regards.

PPOME - New Tab & Infotype - How to find "start date" of preview period

Hi all,
I have successfully created own Infotype and add as new tab in PPOME.
But now I need in my modulpool program to read field "start date" of preview period (from heading of screen in PPOME). I can't find right field. Has anybody any idea?
Thanks a lot.
Dusan
Message was edited by:
Dusan Skokanek

Hi ramprasad74,
According to your description, you are using Analysis Services as a data source for the report, the cube has hierarchy: Fyear, FQuarter, FPeriod, fweek, Fdate. You want to add a date parameter to the report, after you changed value of the parameter, the
report will return the first day of FPeriod.
To achieve your goal, we need to add a parameter to the report, then use the parameter in mdx query. For detail information, please refer to the following steps:
In the Report Data pane, right-click on a dataset created from a SQL Server Analysis Services data source type, and then click Query. The MDX query designer opens in Design mode.
On the toolbar, click Design to toggle to Query mode.
On the MDX query designer toolbar, click Query Parameters symbol. The Query Parameters dialog box opens.
In the Parameter column, click <Enter Parameter>, and then type the name of a parameter.
In the Dimension column, choose a value from the drop-down list.
In the Hierarchy column, choose a value from the drop-down list.
In the Default column, from the drop-down list, select a single value.
Click OK.
In query designer dialog box, type the mdx query like below:
with member [Measures].[FirstChild]
as
[Date].[Fiscal].currentmember.parent.firstchild.name
select {[Measures].[FirstChild]} on 0,
[Date].[Fiscal].[Date].members on 1
from
( SELECT ( STRTOSET(@ParameterName, CONSTRAINED) ) on 0
from
[Cube]
Here are relevant threads you can reference:
https://social.msdn.microsoft.com/forums/sqlserver/en-US/c7146ac3-40ea-4d53-b321-c707aebbd405/how-to-pass-date-parameter-to-mdx-query
https://social.msdn.microsoft.com/forums/sqlserver/en-US/fd12a865-bc90-4a65-af42-ce38a8cfa29b/pass-date-time-parameter-to-mdx-query-ssrs
If you have any more questions, please feel free to ask.
Thanks,
Wendy Fu
If you have any feedback on our support, please click
here.

Error message while copying a position in PPOME

Hi,
I get the following error message when trying to copy a position in PPOME
Error during copying. The action has been interrupted.
Message no. 5A505
Any ideas what might cause this?
Regards,
Francois

Hi Francois,
I have found a note that might help solve your issue
1037901 Error during copying in transaction PPOME
1104954 PPOME: Error 5A 505 when copying objects
other customers had similar issue in their user exit, check if you have set up one.
Hope this help
Sarah

Error coming while modifying data in infotype through HR_INFOTYPE_OPERATION

I have created a report which reads a excel file fom the system and then upload data in infotype 0077 through HR_INFOTYPE_OPERATION. In this report first I check if the record exists in IT0077 for a particular employee , if not then creates a new record with the input file data and if the records exists then I need to modify that record.
But the problem is that on updation the function module HR_INFOTYPE_OPERATION always return an error that "Infotype doesnot exist", although its exists in the system.
Why this error comes when once I excuted the report with a pernr number for creation and then I execute with teh same data to modify it, it gives an error in modification.

iam not sure
When we create we have to use INS in the code and when we modify we have to use Operation MOD
Since Dilek our Techinical consultant is there hope your issue is solved

HCM process & Forms - Need logic to handle the Error's when Infotype Update

Hi Experts,
Currently im working with HCM process and forms workflow's. I have ten HCM workflow's and everything is working fine.
Now the issue is, at the time of save, if there is any error like infotype lock or any other Master data error's, then the standard task responsible for save the data, returns the Status as Error.
Already the approval process for the request is carried out, and it can not be make it again. So I need to save the data without re execution of the process or without re-approval.
I searched in standard workflow also. There is no option to handle the Infotype update Error's.
So can any one give me some hint about this? Without the re-initiation i need to save the data's.
Thanks for your time and Suggestions.

If you are using the framework to update specific infotypes and they are locked for "no apparent" reason you'll want to open an SAP message. I would highly discourage you from going down the path of calling that FM, from within workflow no less. Workflow in the framework was not intended to do such operations, this is supposed to be handled in the decoupled infotype framework (through configuration)... not to mention you won't be using the dec. infty framework by calling that function.
While I've had to do this before, it was because of a limitation in the framework not something as trivial as a locked infotype. Who knows, it might actually be locked for a legitimate reason?
Andy

Copy infotypes organization unit ppome

Hi.
We are with an upgrade and we are copying infotypes from organization unit in PPOME and the infotypes copied aren't the same in both systems. Are there any database table where you indicate the infotypes to be copied.
Thanks.
Regards.
Jose

Hi,
You could find a list of infotypes off the IMG. Are you looking for PA or PD infotypes?
Try RPUAUD00 Infotype Log Documents
OR
T512Z Permitted Wage Types for HR.
Regards,
Amit Lal

INfotype not found error

Hi expert.
When i try to create a new employee in PA30.
I got error that infotype is not found in below function:
CALL FUNCTION 'HR_INFOTYPE_DATABASETABLE_GET'
      EXPORTING
        infty           = infty
        tclas           = tclas
      IMPORTING
        dbname          = dbtab
      EXCEPTIONS
        entry_not_found = 1
        OTHERS          = 2.
    IF sy-subrc <> 0 OR dbtab = 'TEVEN' OR dbtab IS INITIAL.
      RAISE infty_not_found.
    ENDIF.
Thanks & REgards
Anwar

When i am trying to change any dataof any user who is hired and have entry in 0000,through pa30,as soon as i click on save button,dumb error comes..upto 1 hr earlier it was working fine,,is thier any error for country grouping???
A RAISE statement in the program "SAPLHRAC" raised the exception                              |
condition "INFTY_NOT_FOUND".
Since the exception was not intercepted by a superior
program, processing was terminated.
Short description of exception condition:
For detailed documentation of the exception condition, use
Transaction SE37 (Function Library). You can take the called
|    function module from the display of active calls.

Error while using copy function for position in IT 1001

Hi All,
I am getting the following error " For infotype 1001 in status 1, function COP is not allowed" when I am changing the Org unit relationship (A003) in IT 1001 for a position
Steps followed:
po13 -> choose position -> select relationship IT-> click overview -> select A003 -> click on copy button
then I get the above error.
Analysis I have done till now :
1. In IDES everything is working fine.
2. I checked the Time constraint for IT 1001 and it was 3
Thanks for the help in advance
Ram Prakash

Hi Ram,
please check, if the note 1396300 is implemented in your system?
If so, check the table T777F.
It should have the following entries:
MANDT ISTAT INFTY FCODE
002   1     ****   AEND
002   1     ****   COP
002   1     ****   CUTI
002   1     ****   DEL
002   1     ****   DISP
002   1     ****   INSE
002   1     ****   LISD
002   1     ****   PLVO
In case these entries are missing, please do an adjustment with your 000-client.
Hope this help
Sarah

Error in PA10

Dear Experts
We have upgraded from Ecc4.6c to Ecc6.0.
After the upgrade during the testing phase when we execute the PA10 transaction
Error description is below-
When we execute after entering the personnel number the error is --
Infotype 0122 does not exist
Message no. PG008
Diagnosis
Infotype 0122 is not available in the system.
System Response
This action cannot be executed.
Procedure
Please check and correct your entry.
Regards
Iyer

Hi Some of the details of your personnel records links with 0122 please check if you customize something of this IT.
or you can go to SPRO check this IT there might changes and differences between the two system.

Create InfoType with decimal field

Hi,
I would like to create an InfoType with some numeric, char and currency type in the structure
Then I run PM01, create the structure
http://img119.imageshack.us/my.php?image=ps9080ze4.jpg
activate it and go back to PM01 but when I click on GENERATE button, il get the following message :
msg type error : The infotype must not include an integer type or floating point no.field
I dont realy understand why this error occurs and why an IT couldn't have integer type in his structure...
Any idea ?
Thanks,
Ant.

Instead of INT use DEC or NUMC data types.
To know why INT cannot be used try searching with Hardware Restriction in terms of general computing.

How to maintian Infotype 0302?

Dear All,
How to maintian Infotype 0302, Additional Actions.
Direct selection shows error- This Infotype cannot be maintianed directly.
Is it maintained directly when we do two actions on the same day, if yes how to view both the actions?
Regards,
Saureb

Hi
Please see SPRO node "Set up personnel actions"
You can use personnel actions to carry out complex personnel administration procedures. A personnel action displays, in the correct sequence, the infotypes that have to be maintained for a specific action.
In this step
you determine whether you want to use the Additional Actions infotype (0302).
The Additional Actions infotype (0302) enables the automatic logging of all personnel actions types that you carry out for an employee on a key date.
Note that in the Actions infoytype (0000), only one personnel action type is saved per day. In this infotype, you only store the personnel action types that change the status of the employee, such as the personnel action type Leaving.
you define the personnel action types that represent the personnel processes in your enterprise. This means that within the personnel action Hiring, all the infotypes that must be maintained when hiring a new employee are displayed automatically to the personnel administrator for processing.
define a priority list for the personnel action types that do not change status, and must therefore not be stored in the Actions infotype (0000), but which should nonetheless be logged in this infotype.
If the personnel administrator performs no personnel action types that change status, but instead several that do change status on one day, the priority list controls which of these personnel action types is to be stored in the Actions infotype (000).
Note that personnel action types that are only used to process several infotypes in an infogroup should not be stored in the Actions infotype (0000). SAP recommends that you log personnel action types such as these automatically using the Additional Actions infotype (0302).
You only have to carry out this activity if you want to use the Additional Actions infotype (0302), and have activated this infotype.
If you want to perform simplified employee organizational changes, you can also set up a 'Country reassignment' action type in this step, for which you set the Country reassignment indicator. For more information on country reassignments, refer to Personnel Administration documentation under Business Processes in Personnel Administration -> Country Reassignment.
Requirements
Familiarize yourself with the personnel processes that occur in your enterprise, such as entry or leaving.
Standard settings
In the standard system, the Additional Actions infotype (0302) is not activated. Furthermore, the SAP standard system contains several personnel action types.
Recommendation
Refer to the SAP sample entries for guidance when you are defining your own personnel actions.
Activities
1. If you want to use the Additional Actions infotype (0302), call up view Activate 'Additional Actions' for all existing personnel numbers.
2. Call up the view Personnel Action Types.
3. Check the SAP sample entries.
4. Delete the entries you do not require.
5. If required, define several personnel action types.
a) Choose New entries.
b) In the Action type field, enter a number, and in the Name of action type field, enter a name for the personnel action type.
c) In the FC field, enter the function character for the personnel action type.
You can distinguish the first entry actions from all the others. Choose the function character 1 for first entries, 7 for first entries with data transfer from recruitment and 0 for all other personnel action types.
d) If required, define the status indicator STAT1 (customer specific).
This status indicator is not used in the standard system. You can use this indicator individually.
e) Define the status indicator STAT2 (recruitment) and STAT3 (Special payment).
f) Decide whether you require standard decision rules to define plausibility rules for the sequence of personnel action types (check feature).
Note: Never change the standard decision rules.
g) Decide whether organizational assignment data may be changed whilst personnel actions are being carried out. When you set the indicator P, the position field in the Actions infotype (0000) is ready for entry.
You can process the fields Personnel area, Employee group and Employee subgroup with the indicators PA, EG and ES.
h) Assign an infotype group number to the IG field in the personnel action type.
You can then process the the individual infotypes from the selected group in the personnel action type in the appropriate sequence.
You defined the infotype groups in the " Define Infogroups" step.
i) Specify whether the date entered on the initial screen of the Actions infotype (0000) is the start date for new infotype records or the end date for old infotype records. This is especially important in the case of leaving actions.
j) Use the indicator U0000 to determine whether your personnel action type should create a new record for the Actions infotype (0000).
k) Use the Country change indicator to determine whether the personnel action type is a country change.
6. If you have activated the Additional Actions infotype (0302), determine whether your personnel action type should be logged in the Additional Actions infotype (0302) using the U0302 indicator. Call up the view Priority list for personnel action types.
Specify a priority list for the personnel actions which do not change the status, and for which you have set the indicator to U0000.
In the Priority field assign sequential numbers with a maximum of two digits to each of the personnel action types. The smaller the number, the higher the priority of the accompanying personnel action type.
Further notes
Do not define any new personnel action types if only the infotype group should be different for the personnel administrator. To achieve this, you can define the infogroups as user group dependent.
The keys for personnel action types, which you carry out for an employee, for example, hiring, organizational change, leaving, are stored in the infotype Actions (0000).
The existence of a personnel number is ruled out by the existence of a record in this infotype. Only one record can exist for this infotype on the database at any one time.
When an employee has left, there is also a record in the system for the personnel action Leaving. The most important information in this infotype is the employee's employment status: active, leave of absence, retired, left.
Personnel actions that are only used to process several infotypes in an infogroup should not be saved in the infotpye Actions (0000). SAP recommends that you log personnel actions of this kind automatically using the Additional actions infotype (0302).
Notes on the creation of batch-input sessions:
If you want to carry out a batch-input for a personnel action, do not call up transaction PA40 (Actions menu). Instead, call up transaction PA30 (infotyp menu). In the actions menu place your cursor on the line containing the relevant action; this assumes you know the exact setup of the menu.
Proceed as follows:
1. Call up transaction PA30.
2. Choose the Actions infotype (0000).
3. Enter the personnel action type in the Type field.
4. When processing entry actions, enter the function code '=INS', for other actions, enter the function code '=COP'.
regards
Pravin

PPOME: Error in Infotype Tabpage

Similar Messages

Maybe you are looking for