Pete

Author Archives

  • How To Change And Create SAP HR Infotype Screens

    In SAP HR, infotypes are used to group employee data. SAP provides many standard infotypes for different information group. Many times, based on the business requirements, we have to modify the standard infotypes.

    We can modify the infotypes either by showing/hiding the standard infotypes fields based on certain criteria or by adding additional custom fields in the infotype structure.

    This is a 2 part tutorial. In Part – 1 you will learn how to configure infotype screens. In Part – 2 you will learn how to add additional custom fields to your screens.

    Show/Hide fields in infotype screen

    The infotype screen can be configured based on the values of the following fields:

    Field Field Name Field Length
    Screen number DYNNR 4 characters
    Subtype SUBTY Up to 4 characters, but always  the same length for one feature
    Company code BUKRS 4 characters
    Personnel area WERKS 4 characters
    Employee group PERSG 1 character
    Employee subgroup PERSK 2 characters
    Payroll area ABKRS 2 characters
    Country grouping MOLGA 2 characters

    Based on the relevant employee data in the above fields the infotype screen can be customized. The fields which are used to decide the screen layout are maintained in a ‘Feature’ through transaction code PE04.

    Features return the value in the Variable key, which is then maintained against the infotype screen numbers in table T588M.

    Let us take an example of infotype 0185 (Personal IDs).The standard screen is:

    Example Of infotype 0185 (Personal IDs)


    Our requirement is to show only two fields, ID Type and ID no. for subtype Resident Status.

  • How To create SAP PA-HR Infotype In 5 Easy Steps

    In SAP HR/HCM, employee data is grouped in Infotypes. This employee data is saved in infotypes based on his/her personal number (PERNR).

    For example in infotype PA0006 (Addresses) you will find employee’s address details. Similarly, in infotype PA0021 you will find the employee’s family details.

    SAP provides hundreds of standard infotypes, but many times there are business/client requirements where we have to create new infotypes. In this tutorial we will see how to create a custom PA (Personal Administration) infotype in just five easy steps.

    Step 1. Creating the PSnnnn Structure

    Each infotype requires a PS structure which contains all the data fields.

    To create the ‘PS structure’, go to transaction code PM01.

    To create The ‘PS Structure’, Go To Transaction Code PM01

    Give a four digit number between 9000 – 9999 in the ‘Infotype no.’ field. Select the radio button ‘Employee infotype’. Select the radio button ‘PS Structure’ and then click on the ‘Edit’ button.

  • How To Create A Chart Of Accounts In SAP

    Concept Of Chart Of Accounts

    The chart of accounts is the list of all the general ledger accounts that can be used by one or more company codes. As a good SAP business practice, the chart of accounts should be one of the first organizational elements which a company implementing SAP should finalize. This is because the chart of accounts decides which G/L accounts will be available for general as well as tax related postings.

    Assigning Company Code To Chart Of Accounts


    The chart of accounts is defined at the client level i.e. above the company code level. This allows the same chart of accounts to be used by multiple company codes. This is helpful in case of sister companies which are defined as separate legal entities but require more or less identical general ledger accounts.

    Types Of Chart Of Accounts

    A single company code can have three types of charts of accounts. This is required in case the same company needs to prepare financial statements in more than one format. The different types of chart of accounts are:

  • How To Use The SAP ABAP Debugger Efficiently

    The ABAP Debugger is used tool to execute and analyze programs line by line. Using it we can check the flow logic of a program and display runtime values of the variables. Currently, SAP offers two types of Debuggers:

    • The Classic ABAP Debugger
    • The New ABAP Debugger

    The Classic ABAP Debugger, with its old user interface and its limitations to debug certain types of ABAP program is now not in use by many new and old ABAP developers.

    Learn How To Use The ABAP Debugger In This Training Course

    The New ABAP Debugger, with its state of the art and flexible user interface, can be used to debug all types of ABAP programs. It provides many new features which improve our efficiency of debugging, both in ABAP support and development.

    In this article, we will learn how to use these new features and discover some tips and tricks to efficiently use ABAP debugger.

    Switching between the ‘Classic Debugger’ and ‘New Debugger’

    You can switch between both the debugger and make any one your default debugger. To do this, go to ABAP Editor (SE38)→ Utilities → Settings.

    SAP ABAP Editor - SE38


    Now in the user-specific settings pop up box click on ABAP Editor tab and then click on Debugging.

  • Analysis Of SAP FBL3N Report And It’s Significance

    The Purpose Of The FBL3N Report

    The FBL3N report is used to list line items for multiple accounts across multiple company codes. This functionality is provided by the selection screen of the report. It is also possible to display items from more than one General Ledger account in a customized layout. This report allows changes to individual documents or to carry out mass changes to posted line items displayed in the report.

    Search help is available to enable a detailed selection of General Ledger accounts which allows access to various possible entries. The search help screen is shown in figure 1 below.

    Search Help To Select General Ledger Accounts
    Search Help To Select General Ledger Accounts

  • How To Create A Vendor Master In SAP

    Concept Of A Vendor Master

    The vendor master stores all the data pertaining to a particular vendor in SAP. This data is made available to other transactions and modules as and when required by SAP via the inter-module integration. The vendor master contains the following data sets:

    • GENERAL DATA: The general data consists of the vendor address, country, contact person, bank account, etc.
    • COMPANY CODE DATA: The company code data contains the data specific to a company code like the payment terms, payment methods, dunning procedures, tax details, etc.
    • PURCHASING ORGANIZATION DATA: The purchasing organization data contains information like the sales purchasing organization, partner functions, pricing, etc.

    The vendor master is extremely important for the materials management, logistics as well as the Financial Accounting module. The details of the vendor such as the payment terms, address, purchasing organization, purchasing group, payment methods, etc. are picked up from the vendor master and provided to the other modules as and when necessary.

    The total data for a vendor master is stored in multiple tables. The General data pertaining to a vendor is stored in the LFA1 table while the company code data is stored in the LFB1 table. The purchasing organization data for a vendor is stored in the LFM1 table. All these tables are accessed for information about the vendor by the FI and the MM module.

    Vendor Master Data Tables
    Vendor Master Data Tables