LDB for infotypes 2001,2002 , 2003 ...04 ?

Is there any LDB for the infotypes 2001,2002,2003,2004 ...
Thanks,
JR.
Edited by: jeeva raj on Mar 13, 2009 12:00 PM

Hi,
I am not sure if I get your issue right, but from what I understand you can not do what you want. I do not think you are able to write a record in IT2001 or 2002 running RPTIME00, because it is absolutely the other way. RPTIME00 through the schema (TM00 in this case) gets the information for the infotype to be processed, but then to write back something in infotype I think is impossible.
Hope it helps.
Regards,
Edoardo

Similar Messages

Disable Delete Button for infotype 2001 subtype 0025

I want to Disable Delete Button for infotype 2001 subtype 0025 only in PA30/61.
Is there any EXIT available

Hi
Try it .
Somebody already given this type of answers.
Pls first use Search then post.
Well FYI,
<b>There is a standard User Exit for PA30 / 40 for PBO and PAI events.
ZXPADU01 for PBO and
ZXPADU02 for PAI events.
By writing proper code in here for the IT2001, you can write your rules.
PBAS0001 ( PA: Pers.Admin./Recruitment: Default values and checks ),</b>
Manoj Shakya.

How to extend IDOC type "HRMD_A" for infotype 2001?

Hi,
I'm trying to send infotype 2001 to another SAP system via ALE and since it is not part of message type "HRMD_A" I have tried to create an extension. I've already created a new segment(we31) and put this segment into the extension(we30). And I've assigned the extension to the message and basic type (we82) but it still doesn't work. Is there anything else I have to do?
Many thanks in advance
Christopher

Hello Christopher,
I don't think any coding is required in your case if I understand your issue correctly.
Just create a Z segment (say Z1P2001...make it same structure as P2001) then insert it as a child segment type of E1PITYP in your customer extension which should be attached to Basic Type HRMD_XX (as per your SAP release).
Make sure in the partner profile you have specified the name of your customer extension and in table T777D you have maintained the value of your Z segment (Z1P2001) in the field IDOC segment.
Now, as long as you have change pointers activated globally as well as for the message type you are using, change pointers will be auto triggered for infotype 2001 and when you run BD21 to process the change pointer, you'll see the system has automatically populated your customer segment Z1P2001.
Let me know if it solved your case.
Cheers,
Sougata.
Edited by: Sougata Chatterjee on May 23, 2008 1:41 PM

IT2001 error, no time constraint reachion for infotype 2001 with tm const00

Dear Seriors,
When I try to add any absence, it show the below given error message (red colour), but if I hit the enter button it allows me to mark absence.
no time constraint reachion for infotype 2001 with time constraint class 001
What might be the reason?
Regards
ET

The time constraint class is used to check for collisions between Time Management infotypes (2001 to 2012). It allows you to specify different regulations for checking for collisions between individual subtypes.
The views Time Constraint Reaction to Time Management Infotypes (V_554Y_B) and Global Time Constraint Reaction (V_T554Y) contain rules for the collision check.
Please explore on this.

PCL4 TABLE LOG FOR INFOTYPE 2001 IS NOT WORKING IN QUA 070 CLIENT

Heloo,
Could some one let me know the ways to capture the log of infotype 2001.
I have used PCL4 table to capture all the changes made to INFTY 2001.
This is working fine in DEV 070.
But not working in QUA 070.
Could someone let me know what is the problem and the solution.
Thanks a lot for your efforts.

Hi Lata!
I created the absences (T554S):
Ps grouping, Absence type text
04,0100 VACATION WORKIN DAYS (quota working fine)
34,0100 VACATION NATURAL DAYS
When I check your steps I have this information
1. Absence type screen no. should be 2001.
I have checked in table T554S.
Screen number quota working fine: 2001
Screen number quota working bad: 2001
2. Quota deduction should be selected in V_554S_Q table
Check quota deduction quota working fine: is checked
Check quota deduction quota working bad: is checked
3. Check that in counting rule you have assigned correct deduction rule.
Counting rule for quota working fine: is 010
Counting rule for quota working bad: is 030
The counting rule 030 is created for me, maybe this is the problem is a similar copy of the rule 010. It has different conditions because in Psgroup "04" the vacations are working days but in group "34" the vacations are natural days.
4. In deduction rule check whether correct quota no. you have maintained.
In deduction rule working fine the absence quota type is 10, standar leave, days
In deduction rule working bad the absence quota type is 30, ,days
I've checked the absence quota type and are similars:
In 10 absence quota type
ESG Time quota types: 1
PS Grpg tm Quota Typ: 01
Absence quota type: 10
Time/measurement unit: Days
Time constraint class: 02
In 30 absence quota type:
ESG Time quota types: 3
PS Grpg tm Quota Typ: 02
Absence quota type: 30
Time/measurement unit: Days
Time constraint class: 02
What's wrong?
Kind regards,
Julian

How to find the error message populating for infotype 2001 iN pa30

Hi ,
I got a requirement that one of our end user a a error message is populating when he tries to enter the data in 2001 absences infotype.
I check the documents ...it is written as a there is long back they modified the original T-code of 2001(report or userexit not sure) to allow only HR Department people , no one can enter the details apart from HR ,no-one else should be able to do that!!
Now i need to find where the error message is getting .............i dont know what is the best approach,
i debugged it(before savgin) but its too long to find......I put the break points for the user-exits available for the infotype(Total i found 16 Package PTIM) ......no user-exit is triggerring..i searching from morning....
The main problem is it is working fine for me.I am not getting error message...so unable to catch
Please help me how to search...or need to search with 'AUTH ' field? if so in how many programs?
or need to search using the 'MESSAGE' i just have the screen shot of the message..with the content how could i found that ??
waiting for your valuable inputs....
regards
sas

Hi Gautam,
Thanks for reverting back, but my problem is i am not getting error message!!
enduser is getting that!!
Rgars
sas

BAPI for infotype 2001

Hi All,
Please let me know any BAPI which can be use to apply leave through portal.
Thanks
Edited by: piyush mathur on Dec 30, 2008 7:34 AM

Hello ,
the BAPI is .....
BAPI_PTMGRATTABS_MNGCREATION
BAPI_PTMGRATTABS_MNGFROMWF
Rewards Points... if the solution is use full.

HR-ABAP-want user exit for pa30 for creation 2001 infotype for sick leave

Hi ALL,
         My requirement like, whenever I try to create a sick leave through PA30 Tcode for infotype 2001 then the has to be trigger like, if the personnel joing date will be from Feb-Dec any date of the year then, the SL will be valid for next year Jan.
Ex; Todya I am creating SL on 2001 infotype. then the condition will
        If joining date not Jan 2007 then,
         Leave will be valid for next year Jan 2008.
So, let me know is there any user exit for this.
Thanks In advance.
J.P

Find myself

How to retrieve time data from infotypes 2001 and 2002 when we use PNPCE

Hello Everyone,
   I am new in using PNPCE ldb.In the requirement i have to retrieve time data from infotypes 2001 and 2002 between the begda and endda.I tried using the macro RP-READ-ALL-TIME-ITY to retrieve data.But its not supporting.Can some body help me in doing this.
THanks in Advance..
Regards,
Chinni.

Hi
   Try the following code:
REPORT ZHRTM41.
nodes peras.
Tables: PERNR.
Infotypes: 2001.
start-of-selection.
get peras.
rp_read_all_time_ity pn-begda pn-endda.
end-of-selection.
loop at p2001.
write:/ p2001-abwtg,p2001-stdaz.
endloop.
    It worked for me when using PNPCE. let me know if you have any problem
Thanks,
V.Nagaraju

Change infotype 2003 when changing infotype 2001

Hi,
When changing some infotype 2001, I need to make a change for the same date in infotype 2003. So, I'm using BADI HRPAD00INFTY, method BEFORE_OUTPUT so I can change infotype 2003.
I already can change the infotype in that BADI, but after changing infotype 2001, which means on PAI, it seems that the old value of infotype 2003 is saved in memory, so it does not assume the new value there, and it gives me a warning message that I want to avoid with this development.
When I leave the transaction, infotype 2003 is updated, so that is working.
Do you have any idea how can I save the change in infotype 2003 in memory, so when changing 2001 it will recognize it?
Thanks in advance.
Best regards,
Sónia Gonçalves

You can try using the function call 'HR_INITIALIZE_BUFFER'.
Arya

INFOTYPE 2001 AND 2002

When i book absence in infotype 2001 or book an attendance in infotype 2002, if i put 6.51, the system automatically changes it to 6.52 hrs. I just want the system to take 6.51. How is this possible. Can this be done through configuration. Please help
Thanks

hi,
This Absence Hours is changing automatically to accomodate the absence start Time and End Time.
Say in your eg,
I assume Personal workshedule start Date - End date iis 8.00 - 17.00.
You are trying to input6.51,system will automatically change to 6.52 to get the correct start Time and End Time.(eg: 08:00 - 15:31)
Manoj.

User exit for infotype 2002

Hi ,
The requirement is making the WBS Element field mandatory ONLY for infotype 2002 cost assignment pop up in pa30.Is this any user exit check.
regards,
srinivas

Hi srinivasarao,
1. Enhancement name is PBAS0001.
2. Inside this FM is
EXIT_SAPFP50M_002
(for checking while saving)
regards,
amit m.

User-exits - Infotype 2001

Hi,
Can anyone tell me which user-exits exist when creating an infotype 2001?
I need to make a validation when saving one infotype 2001, so I need to know which user-exits can I use.
Thanks in advance for your help.
Best regards,
Sónia Gonçalves

Hi,
You must implements the function EXIT_SAPFP50M_002 (the include ZXPADU02) for After Input. In this Include you can check if the infotype is going to be saved (ex. sy-ucomm = UPD and somethings like this).
There is another possibility with an object of the interface method IF_EX_HRPAD00INFTY~IN_UPDATE. This method is called when you are going to save.
We make normaly these checks in 2001, 2002 and 2003 and all works properly.
Kind Regards
Jaime

Problem in updating infotype 2001

Hi Experts,
                 While i am updating infotype 2001 , using HR_INFOTYPE_operation FM it giving a error , because it calling a wrong sceen 2000 , instead of 2001 . can anybody can help on this ?
thanks and regards
Renjith MP

Hi Dude,
Go through the below code for 2002 infotype :
TYPES BEGIN OF text_version.
TYPES   nummer TYPE x.
TYPES END OF text_version.
DATA: PERSONALDATAKEY    LIKE BAPIPAKEY.
DATA: RETURN       LIKE BAPIRETURN1.
DATA: P2002       LIKE P2002.
DATA: PSKEY       TYPE PSKEY.
DATA: IT_TEXT       TYPE HRPAD_TEXT_TAB .
DATA: LINE       TYPE HRPAD_TEXT.
DATA: version       TYPE text_version.
DATA: pcl1       TYPE pcl1.Input Parameters:
PARAMETERS: PERNR LIKE PA2002-PERNR DEFAULT '1004511',
             AWART LIKE PA2002-AWART DEFAULT 'LW',
             BEGDA LIKE PA2002-BEGDA DEFAULT SY-DATUM,
             ENDDA LIKE PA2002-ENDDA DEFAULT SY-DATUM,
             BEGUZ LIKE PA2002-BEGUZ,
             ENDUZ LIKE PA2002-ENDUZ.
START-OF-SELECTION.
CALL FUNCTION 'HR_EMPLOYEE_ENQUEUE'
        EXPORTING
          number = PERNR
        IMPORTING
          RETURN = RETURN.
IF RETURN-NUMBER IS NOT INITIAL.
    EXIT.
ENDIF.
* ADD DATA
CLEAR: P2002.
P2002-PERNR = PERNR.
P2002-SUBTY = AWART.
P2002-ENDDA = BEGDA.
P2002-BEGDA = BEGDA.
P2002-BEGUZ = BEGUZ.
P2002-ENDUZ = ENDUZ.
P2002-AWART = AWART.
P2002-ITXEX = 'X'.
* WRITE DATA
CLEAR: RETURN, PERSONALDATAKEY.
CALL FUNCTION 'HR_INFOTYPE_OPERATION'
         EXPORTING
              INFTY          = '2002'
              NUMBER         = PERNR
              SUBTYPE        = AWART
              VALIDITYEND    = BEGDA
              VALIDITYBEGIN = BEGDA
              RECORD         = P2002
              OPERATION      = 'INS'
              NOCOMMIT       = ''
              TCLAS          = 'A'
         IMPORTING
              RETURN         = RETURN
              KEY            = PERSONALDATAKEY
         EXCEPTIONS
              OTHERS         = 0.
IF RETURN-NUMBER IS INITIAL.
    COMMIT WORK AND WAIT.
ELSE.
    ROLLBACK WORK.
    EXIT.
ENDIF.

HR_BLP_SAVE_TIMEDATA and how to load high volume records onto Infotype 2001

Because of high data volume (estimated 1 million records each run) and short SLA time requirement (runs every 2 hours), we chose to use functions that are called by CAT6 (Skipping the CATS to HR info types loading process) to load the time records directly into Infotype 2001 and Infotype 2002.
Now we discover that some records (sporadically and randomly) don't get loaded onto the infotype and they don't return from the error message table either. We are wondering whether anyone has used these functions before, and how they resolve the issues of missing records / error handling.
We are also wondering if there is any other feasible solution to meet our customer's need.
The two functions we use are: HR_BLP_MAINTAIN_TIMEDATA and HR_BLP_SAVE_TIMEDATA

Hi Curt,
No, they are 32 bit RGB. I have just made an 8 bit RGB and it gives me the option. Thank you for your help

LDB for infotypes 2001,2002 , 2003 ...04 ?

Similar Messages

Maybe you are looking for