Saturday, March 29, 2014
Infotypes 2000 to 2999 are time infotypes.We should not load all time infotype records from the earliest to most recent system dates into main memory. If you use negative time management(front end time recording system is connected to your system), this will quickly lead memory overload.
If you use GET PERNR event, all records for the employee would be loaded, when you use INFOTYPES 20001. Use the infotype declaration MODE N to define the internal table for infotype so internal table is not populated when GET PERNR is triggered.
Use RP_READ_ALL_TIME_ITY to read time data.
Read all Infotypes between 2000 and 2999 into the corresponding infotype tables only allowed after GET PERNR event.Parameters:
- BEGDA - Requested Interval-Begin
- ENDDA - Requested Interval-End
REPORT ztest_ldb_program. NODES: pernr. "&------------------------------------------------------------------------* * If the MODE N addition is specified, the table is not connected with * the logical databases and is not filled with the GET events. "&------------------------------------------------------------------------* INFOTYPES:2001 MODE N. START-OF-SELECTION. GET pernr. RP_READ_ALL_TIME_ITY pn-begda pn-endda. LOOP AT P2001. WRITE: / P2001-PERNR,P2001-ABWTG. ENDLOOP. END-OF-SELECTION.
SAP ABAP online training in hyderabad
ReplyDeleteSAP ABAP online training hyderabad