Basic form
INFOTYPES nnnn.
nnnn between 0000 and 0999: HR master data info types
nnnn between 1000 and 1999: HR planning data info types
nnnn between 2000 and 2999: HR time data info types
nnnn between 3000 and 8999: Not yet used
nnnn between 9000 and 9999: Customer-specific info types
Additions
1. ... NAME c
2. ... OCCURS occ
3. ... MODE N
4. ... VALID FROM begin TO end
Effect
Declares the HR info type nnnn . Creates an internal table as follows:
DATA BEGIN OF Pnnnn OCCURS 10.
INCLUDE STRUCTURE Pnnnn.
DATA END OF Pnnnn VALID BETWEEN BEGDA AND
ENDDA.
Example
INFOTYPES: 0000, 0001, 0002.
Addition 1
... NAME c
Effect
c is a name
c is a name up to 20 characters long. Creates an internal table as follows:
DATA BEGIN OF c OCCURS 10.
INCLUDE STRUCTURE Pnnnn.
DATA END OF c VALID BETWEEN BEGDA AND ENDDA.
Example
INFOTYPES: 0005 NAME VACATION, 0006 NAME ADDRESS.
Addition 2
... OCCURS occ
Effect
occ is a number for the OCCURS value. Creates an internal table as follows:
DATA BEGIN OF c OCCURS m.
INCLUDE STRUCTURE Pnnnn.
DATA END OF c VALID BETWEEN BEGDA AND ENDDA.
Example
INFOTYPES 0003 OCCURS 1.
Addition 3
... MODE N
Applies only to the HR logical databases PNP and PCH .
Effect
The info type tables are not filled by GET PERNR (logical database PNP ) or GET OBJEC (logical database PCH ). The effect of the INFOTYPES statement is then the same as the data declaration of an internal table .
Example
INFOTYPES: 2001 MODE N, 2002 MODE N, 2003 MODE N.
Addition 4
... VALID FROM begin TO end.
... VALID FROM begin TO end.
Effect
This addition should only be used with the logical database PNP .
GET PERNR retrieves only those info type records which are valid within the time range ( begin and end ) specified. begin and end are dates with the format YYYYMMDD.
Example
INFOTYPES: 0007 VALID FROM 19910101 TO 19911231.
Note
Each info type has a formal description in the ABAP/4 Dictionary as table Pnnnn .
If you enter SHOW INFOTYPES nnnn in the editor command line, the system displays information about the info type nnnn .
If you enter SHOW INFOTYPES * , you see a list of all info types.
You can go through entire syntax check here.
Check SAP SCRIPTS AND SMART FORMS BDC HERE COMPLETELY.
Learn object oriented approach of SAP ABAP HERE COMPLETELY.
ABAP ALE CONFIGURATION
SAP CRM Technology Overview
CRM Data Exchange with SAP R/3 CRM Data Exchange via AdapterCRM E commerce Introduction
CRM Interaction Center System ArchitectureCRM Field Sales
People Centric SAP CRM
Analytical SAP CRm Overview
SAP CRM Solution MonitoringCRM Backup Restoring System
Thank you for visiting SAP ABAP.If you liked the post, please subscribe to RSS FEED or get the updates directly into your mail box through EMAIL SUBSCRIPTION.If you want to contact me click here.
Request you to share this page on your favorite book mark site.
INFOTYPES nnnn.
nnnn between 0000 and 0999: HR master data info types
nnnn between 1000 and 1999: HR planning data info types
nnnn between 2000 and 2999: HR time data info types
nnnn between 3000 and 8999: Not yet used
nnnn between 9000 and 9999: Customer-specific info types
Additions
1. ... NAME c
2. ... OCCURS occ
3. ... MODE N
4. ... VALID FROM begin TO end
Effect
Declares the HR info type nnnn . Creates an internal table as follows:
DATA BEGIN OF Pnnnn OCCURS 10.
INCLUDE STRUCTURE Pnnnn.
DATA END OF Pnnnn VALID BETWEEN BEGDA AND
ENDDA.
Example
INFOTYPES: 0000, 0001, 0002.
Addition 1
... NAME c
Effect
c is a name
c is a name up to 20 characters long. Creates an internal table as follows:
DATA BEGIN OF c OCCURS 10.
INCLUDE STRUCTURE Pnnnn.
DATA END OF c VALID BETWEEN BEGDA AND ENDDA.
Example
INFOTYPES: 0005 NAME VACATION, 0006 NAME ADDRESS.
Addition 2
... OCCURS occ
Effect
occ is a number for the OCCURS value. Creates an internal table as follows:
DATA BEGIN OF c OCCURS m.
INCLUDE STRUCTURE Pnnnn.
DATA END OF c VALID BETWEEN BEGDA AND ENDDA.
Example
INFOTYPES 0003 OCCURS 1.
Addition 3
... MODE N
Applies only to the HR logical databases PNP and PCH .
Effect
The info type tables are not filled by GET PERNR (logical database PNP ) or GET OBJEC (logical database PCH ). The effect of the INFOTYPES statement is then the same as the data declaration of an internal table .
Example
INFOTYPES: 2001 MODE N, 2002 MODE N, 2003 MODE N.
Addition 4
... VALID FROM begin TO end.
... VALID FROM begin TO end.
Effect
This addition should only be used with the logical database PNP .
GET PERNR retrieves only those info type records which are valid within the time range ( begin and end ) specified. begin and end are dates with the format YYYYMMDD.
Example
INFOTYPES: 0007 VALID FROM 19910101 TO 19911231.
Note
Each info type has a formal description in the ABAP/4 Dictionary as table Pnnnn .
If you enter SHOW INFOTYPES nnnn in the editor command line, the system displays information about the info type nnnn .
If you enter SHOW INFOTYPES * , you see a list of all info types.
You can go through entire syntax check here.
Check SAP SCRIPTS AND SMART FORMS BDC HERE COMPLETELY.
Learn object oriented approach of SAP ABAP HERE COMPLETELY.
ABAP ALE CONFIGURATION
SAP CRM Technology Overview
CRM Data Exchange with SAP R/3 CRM Data Exchange via AdapterCRM E commerce Introduction
CRM Interaction Center System ArchitectureCRM Field Sales
People Centric SAP CRM
Analytical SAP CRm Overview
SAP CRM Solution MonitoringCRM Backup Restoring System
Thank you for visiting SAP ABAP.If you liked the post, please subscribe to RSS FEED or get the updates directly into your mail box through EMAIL SUBSCRIPTION.If you want to contact me click here.
Request you to share this page on your favorite book mark site.
How to update data to HR infotype tables in database?
ReplyDeleteGood post !! What blog platform do you use on your site ?
ReplyDeletewhat is the alternative to Infotypes ( now obsolete statement ) in Unicode program?
ReplyDelete