Creation of a Custom Infotype in HR

2008-09-16T08:54:00.010+05:30

Lets assume that your company has decided to create a new dress code policy. This policy will be strictly enforced, so your company needs to ensure that everyone has read the new guidelines.

Printing the new policy and mailing this out to the employees in order to receive a signed signature back from them is far too costly and cumbersome. A decision has been made to create a custom infotype.

Here are the steps involved in creating a custom PA Infotype.

Go to transaction PM01 - Create Infotype. There are 6 tabs on the screen. Create Infotype, Copy Infotype, Enhance Infotype, Enhance List Screen, Delete Infotype and Action Menu.
Click on the Create Infotype Menu. Choose a no. for the Infotype between 9001 - 9999. This is the customer namespace. Select Employee Infotype. In this example, we will no. the infotype as 9990.
Start the create infotype process by defining the components of the infotype. Make sure the radio button for the PS Structure is selected.
Select the Create All button to have the system create the module pool (the program with the code to process the infotype), the interface screen, the customizing table entries, and the data dictionary objects for your infotype automatically. (NOTE: the sequence of these steps follows a slightly different path than in the standard SAP Help files)

Data Dictionary Entries

You will receive a notice stating that the PS9990 Data Dictionary Object does not exist and you will be asked if you wish to continue. Select Yes. R/3 will branch you to the data dictionary.
Define the PS9990 structure. A structure consists of a list of components and component types. The component is referred to in screens and programs. The component type determines the attributes of the component, such as whether it is a numeric or character field and the length of the field. Type in the name DRESS_CODE_POL for the component and XFELD as the component type. The short text name should be “Dress code policy” for the PS9990 structure.
Now save and activate the new PS9990 structure. Since you used the PM01 transaction instead of going directly to the data dictionary to create the PS9990 structure, the system builds the top level structure P9990, including both PSHDR and PS9990, for you. The database table PA9990 is automatically built using the definition of P9990.

Infotype Customizatin Settings

Carefully hit the green back arrow once (and only once). You will automatically be taken to a view of table T582A – Infotype attributes (Customizing). Here you will give your infotype characteristics that control the way the infotype is processed. If you need to access the customizing table later, you may go to transaction SM30, enter the view name V_T852A, and maintain the customizing settings there.

Select 'New Entries'
Enter your infotype number 9990 and the Short Text Name “Dress Code Policy”.
Make the Time Constraint a 2 since the employee is not required to have this infotype maintained, but if they do maintain this, they can only have one valid record at any given time. (See Time Constraint inset for an explanation of Time Constraints). The value you select here varies from requirement. Refer to a standard Infotype screen to compare the characterisitics.
You will not have subtypes for the infotype, so you may leave the fields relevant to subtypes blank. Check the Access Auth checkbox, which indicates to use the current date for authorization checks.
Check the Text checkbox, which allows text to be maintained on the infotype via the transaction PA30 – Maintain Text functionality, via transaction PA30 with the menu path – EDIT>Maintain Text.
Place a 3 in the Select with Start field, which indicates if a date is entered in PA30 in the “Period” section, records valid on the date specified are displayed.
Enter a 5 into the Select w/end field, which means that the records valid any time within the entered period are displayed.
For Select w/o date field, enter a 2, which means records valid for the system date are displayed when no dates have been entered in PA30.
The Create w/o start field should be a 3. This field controls what defaults into the start data field during a create process. A 3 indicates the system CPU date will be used.
Create w/o end should be a 1. This field controls what defaults into the end date field during a create. A 1 indicates 12/31/9999 will be used.
For Screen Header, you should enter the standard screen header 01. This determines the header style displayed on the infotype screen.
Do not enter anything into the Retroactive Accounting Trigger section as this infotype would not trigger any retroactivity functionality for payroll or time.
In the Technical Data section, place screen number 2000 in for the Single Screen field’s value and a List Screen value of 3000. These are the standard screens numbers that will be generated by PM01.
The Dialog Module will be RP_9990. The Structure will be P9990 and the Database table will be PA9990.

Screen Painter

You should now be on Transaction PM01
Select the Screen radio button and type in 2000 for the screen number.
Hit the Edit button. Now you will be taken to the Screen Painter: Initial Screen. PM01 builds a screen based on the fields in the infotype, but you will then refine the screen manually, if needed.
Select Layout Editor for the MP999000 Screen 2000 and then edit. Make all the necessary changes to the screen and you may add the validations based on your requirement in the PBO & PAI events.
Now test your screen by clicking on the Test icon or menu path Screen>Test. If you are happy with your screen, save the screen and activate it.

Program

PM01 uses P9990 to automatically generate MP999000, the module pool program for the infotype. For this example you will not need to change the module pool program to add edits or special processing.
You will not need to change the menu or toolbar. Use the SAP standard menu and toolbar from transaction PA30 – Maintain Master Data.

Testing

Go to transaction PA30 – Maintain Master Data.
Enter a personnel number of an employee and then type in the infotype 9990 into the direct selection of an infotype field.
Hit the create icon and the newly created screen appears.

The custom infotype is now ready and when the entries are saved, the data will be stored in the table PA9990.

If you have any questions, drop me a comment.

ABAP Vs HR ABAP

2008-09-13T19:04:00.014+05:30

ABAP is the proprietary language developed by SAP. SAP is developed on ABAP. Once SAP is implemented by the respective clients and if there is a need for any customisation, ABAP is the language needed. There are many things that can be done using ABAP. Generally, the following things are done in ABAP.

Table development
Data Processing
Report development
BAPIs / RFCs
Database updates
Screens development / enhancements
Scripts and Smart Forms
Function Building
Java Connectors etc
Communicating with different Applications

This is basically done through the programming in ABAP builder by using ABAP 4th generation language. This may be related to any module of my SAP ERP 2004 like HR, FICO, SD, MM, CRM Etc.,

Now, when it is said ABAP HR, it is the development of ABAP in the area of HR to meet the clients requirements according to the functional specifications. They may be in any area of HR like in the areas of time aspects, pay aspects, OM aspects and Self Services like E-recruitment, ESS, and MSS Etc.

SAP - ABAP HR

Creation of a Custom Infotype in HR

ABAP Vs HR ABAP