What is a logical database

Hi All,
what is a logical database? what is the use of it.

Hi again,
1. To get a taste of it.
2. create a new z program.
3. while creating type PNP
   in logical database field.
4. paste this code and execute.
  REPORT ABC.
infotypes : 0001.
TABLES : PERNR.
GET PERNR.
WRITE :/ PERNR-PERNR.
5. The selection screen which u see
   is coming from logical database PNP program.
6. Execute
7. U will get a list of pernr.
SAPDBPNP
this is the main program of LDB PNP
which does the main work.
SAPDB + ldb name.
regards,
amit m.
Message was edited by: Amit Mittal

Similar Messages

  • What are the logical databases belongs to HR module.

    Hi experts,
    Please explain What are the logical databases belongs to HR module.
    Thanks,
    Rashmi

    Hi Rashmi,
    There are three LDBs in HR.
    1. PNPCE or PNP
    2. PCH
    3. PAP
    Good Luck
    Om

  • What exactly are Logical Database in Programs?

    Hi Experts,
       While digging deep into the programs, using the T-Code SE93/SE38, we come across Logical Database.
    what is the functionality and use of this Logical Database?
    Best Regards,

    Normally moderators reject unresearched questions, but this one has not been discussed much for it's security aspects.
    In the ABAP forums you will find a lot of discussions about LDB's ("LDB" is your search term).
    Please do a search and reconsider and focus your question more.
    What is it about LDB's that you would like to discuss?
    Cheers,
    Julius

  • What are the logical database source (SQVI) should i use for quick viewer

    Dear expert,
    Would like to seek for your help, how to use (SQVI) quick viewer/SAP query to generate the listing of   and can I use SQVI -quick viewer and select the data source as logical database source to generate in order to generate the listing of GL account number,GL account descrition , tax category,posting without tax allowed column in the query by company?
    Between, what are the data source should I use for logical database to generate the query with listing of GL account number,GL account descrition , tax category,posting without tax allowed column in the query by company?
    Please help.
    Many Thanks.
    Regards,
    Karen

    Hi,
    Thank you for the prompt reply, what I would like the query to generate is the master data GL listing for GL account,GL description,Tax category, posting without tax allowed column where i use BRF as the data source for logical database to generate the quick viewver but the BRF data source do not have the GL description.
    How I can join table/join query or what are the data source should i use so that i can able to generate the query with GL master data listing by company code by display GL account,GL description,Tax category, posting without tax allowed?
    Between,do you have any reference/link/document on the how to use the SQV1?
    Also, what the difference between SQV1 and SQ01 ?
    And also what are the sap query,inforset query,quick viewer mean for and what are the difference between them also when should i use sap query,inforset query,quick viewer  to generate the query?
    Please help.
    Many thanks.
    KH

  • What is a logical database diagram

    one of my class met joined a company as a freshear and says he was asked to draw a logical database diagram what does that mean.......he says i will be asked for the same if i join  a company ofcourse he wants me to find it myseld so some one help me pls........................
                                                                                    santo

    Hi
    A logical database is a special ABAP/4 program which combines the contents of certain database tables. You can link a logical database to an ABAP/4 report program as an attribute. The logical database then supplies the report program with a set of hierarchically structured table lines which can be taken from different database tables.
    LDB offers an easy-to-use selection screens. You can modify the pre-generated selection screen to your needs. It offers check functions to check whether user input is complete, correct, and plausible. It offers reasonable data selections. It contains central authorization checks for data base accesses. Enhancements such as improved performance immediately apply to all report programs that use the logical database.
    Less coding s required to retrieve data compared to normal internel tables.
    Tables used LDB are in hierarchial structure.
    Mainly we used LDBs in HR Abap Programming.
    Where all tables are highly inter related so LDBs can optimize the performance there.
    Check this Document. All abt LDB's
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.highlightedcontent?documenturi=%2flibrary%2fabap%2fabap-code-samples%2fldb+browser.doc
    GO THROUGH LINKS -
    http://www.sap-basis-abap.com/saptab.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/9f/db9bfa35c111d1829f0000e829fbfe/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/9f/db9b5e35c111d1829f0000e829fbfe/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/c6/8a15381b80436ce10000009b38f8cf/frameset.htm
    /people/srivijaya.gutala/blog/2007/03/05/why-not-logical-databases
    Re: **LDB**
    www.sapbrain.com/FAQs/TECHNICAL/SAP_ABAP_Logical_Database_FAQ.html
    www.sap-img.com/abap/abap-interview-question.htm
    www.sap-img.com/abap/quick-note-on-design-of-secondary-database-indexes-and-logical-databases.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/9f/db9b5e35c111d1829f0000e829fbfe/content.htm
    http://help.sap.com/saphelp_nw2004s/helpdata/en/9f/db9bb935c111d1829f0000e829fbfe/content.htm
    Gothru the blog which provides info on LDB's:
    /people/srivijaya.gutala/blog/2007/03/05/why-not-logical-databases
    <b>Reward points if useful</b>
    Regards
    Ashu

  • Logical database in adhoc query

    Hello All,
    Can anyone tell me what is the logical database in adhoc query?

    Hi
    When you create a query , you have to select an infoset. Infoset can be considered as a source from which data is populated in the Query Fields.
    Infosets are created from Transaction SQ02.
    There can be four methods through which an Infoset can become a source of data:
    1.  Table join ( By joining two or more tables from Data dictionary)
         example: Joining tables PA0001 and PA0006 on Pernr to get a one resultant dataset
    2. Direct read of Basis Table ( Like PA0001 as a source for data in Infoset )
    3. Logical Database ( A Pre-written Program by SAP that extract data from clusters, tables taking care of authorizations and validity periods)
    Example : Logical database PNP, PNPCE (Concurrent Employement),PCH ( LDB for Personnel Development Data)
    Custom Logical DBs can be created in T_Code SE-36.
    4. Data Retrieval by a Program ( Custom code written by ABAP developers which will collect and process data) . This program has a corresponding Structure in data dictionary and the fields of this structure will be used in query)
    Reward Points, if helpful.
    Regards
    Waseem Imran

  • Logical database of ABAP query

    Hi,
    Can anybody please let me know what is the Logical database for ETXDCI, ETXDCH & ETXDCJ (Tax tables) with any sales document tables? I need to develop one ABAP query for the users.
    I am a Functional person so I would like to know Can anybody please let me know how I can find out the Logical database?
    Your time and help will be really appreciate.
    Thanks & Regards,
    Niki Shah.

    Try the BRF logical database.
    I found it by searching in which programs the tables were used.
    It show program SAPDBBRF which is the program for logical database BRF.
    Kind regards,
    Arthur Parisius

  • Logical database for vendor cleared items

    Hi,
    What is the logical database for vendor cleared items.  KDF is giving me only open items. 
    Actually I am preparing a report which uses vendor cleared items and trying to get the list from BSAK table.  Which would be the better way (faster process for better performance)
    a) directly fetching data from database table like BSAK or
    b) by using logical database
    any ideas please.
    regards,
    mallik

    If  just display of all cleared items in a report,  then i would suggest you to go for Query development instead of a z report and use BSAK. Being Index table and query, we can reduce several errors in logic/easy to develop/less time.
    If you need Z report only, then also, you can go for BSAK. Where as BASK is secondary index table which helps to fetch data fast.
    In one way, BSEG - BSIK = BSAK for your case!
    Regards
    Sridevi

  • Re: logical database

    Hi,
        What is the logical database. I know how to create.
    I think it is useful for dynamic selections of parameters.
    This logical databases use by HR ABAP. Is it right?
    But i heard that these will increase performnace of ur coding. How can u justify these doubts.
    rgds
    p.kp

    Hi paluri,
    1. What is the logical database
       Logical database is nothing
       but a program only,
       which provides the facility of
       a)pre-defined seleciton secreen
       b) facility for GETting records
         (without knowint the databse tables)
    2.   logical databases use by HR ABAP. Is it right?
        Yes, absolutely right. Its mostly used
        in HR.
       But it is also used now a days in other modules
       like FI, SD.
    3. But i heard that these will increase performnace of ur coding
       Yes, it will increase the performanc,e
       in the sense, that,
       the SQL, FMs used for fetching from the database
       is already fine tuned and written
       into the already tested program of logical database.
    regards,
    amit m.

  • What is node and how to create a node in logical database in reports.

    What is the purpose of this nodes. Show me one example program using these nodes.Clearly show me an example with explanation. If this is taking any table means.Plz give me a clear example with my ztable.
    Tables : zptable1
    fields in this table are f1,
                                    f2,
                                    f3.

    hi,
    The sole effect of the NODES statement is to copy data from logical databases to executable programs. It defines an interface work area and is allowed only in the global declaration section of executable programs that are linked to a logical database, and in the database program of logical databases. node must be the name of a node of the logical database. NODES declares a table work area node for the respective node. The data type of the table work area is either predefined in the node of the logical database or can be chosen from a list using addition TYPE.
    The nodes of the structure of a logical database are maintained in transaction SE36
    for more go to transaction ABAPHELP and write Nodes you will get examples there and explanation
    thanks
    Sachin

  • What is a logical storage unit in a database can anyone help me in a better

    what is a logical storage unit in a database can anyone help me in a better
    Thank u

    Do you have something specific in your mind? Do you want to clarify something you did not understand in the documentation? If so please provide the document you are reading.
    For example, a tablespace is a logical storage unit where datafiles are physical files. Did you read the concepts manual?

  • What are structures of logical database.

    hi
    what are structures of logical database.

    Dear Chaitanya,
    The structure of LDB can be divided into three sections:
    >Structure
    >Selection
    >Database Program
    STRUCTURE:
    The structure defines the data view of the logical database. It adopts the hierarchy of the database tables defined by their foreign key relationships. This also controls the sequence in which the tables are accessed. It determines the structure of the other components and the behavior of the logical database at runtime.
    The structure of a logical database is usually based on the foreign key relationships between hierarchical tables in the SAP System. Logical databases have a tree-like structure, which can be defined as follows:
    · There is a single node at the highest level. This is known as the root node.
    · Each node can have one or several branches.
    · Each node is derived from one other node.
    The nodes must be structures defined in the ABAP Dictionary or data types from a type group. Normally, these are the structures of database tables which the logical database reads and passes to the user for further evaluation. However, it is also possible, and sometimes useful, to use ABAP Dictionary structures without an underlying database. For technical reasons, the maximum number of nodes allowed in the structure of a logical database is 300.
    Any executable ABAP program that has a logical database linked to it can contain a GET statement for each node of the structure. When you run the program, the corresponding event blocks are processed in the sequence prescribed by the hierarchical structure of the logical database. If a program does not contain a GET statement for every node of a logical database, the processing passes through all the nodes that lie in the path from the root to the nodes specified by GET statements.
    If you call a logical database using the function module LDB_PROCESS, the depth to which the system reads is controlled by an interface parameter.
    SELECTIONS:
    The selections define a selection screen, which forms the user interface of the executable programs that use the logical database. Its layout is usually determined by the structure. You can adapt the selections to your own requirements and also add new ones. When you link a logical database to an executable program, the selections of the logical database become part of the standard selection screen of the program (screen number 1000). If you call a logical database using the function module LDB_PROCESS, the selections are filled using interface parameters.
    The selections in a logical database are defined using the normal statements for defining selection screens, that is, PARAMETERS, SELECT-OPTIONS and SELECTION-SCREEN. In a logical database, you can also use the additions VALUE-REQUEST and HELP-REQUEST to define specific input and value help. You define the selection screen in a special include program known as the selection include.
    When you write programs using a logical database, you can also add your own program specific selections. The standard selection screen then contains the database-specific selections, followed by the program-specific selections that you have defined.
    When the system generates the selection screen for an executable program, database-specific selection criteria and parameters are only displayed if you have declared an interface work area for them in your program using the NODES or TABLES statement.
    Suppose you have a selection include containing the following lines:
    SELECT-OPTIONS slifnr FOR lfa1-lifnr.
    PARAMETERS pbukrs LIKE lfb1-bukrs FOR TABLE lfb1.
    The selection criterion SLIFNR is linked to table LFA1, the parameter PBUKRS to table LFB1. If the TABLES statement in an executable program (report) declares LFA1 but not LFB1, SLIFNR is displayed on the selection screen, but PBUKRS does not appear.
    The selection screen of a logical database can contain dynamic selections as well as static ones. Dynamic selections are extra, user-defined selections that the user can make as well as using the static selections defined in the selection include. To improve performance, you should always use this option instead of reading more data than you need and then sorting it out in the application program.
    To make dynamic selections available for the node nodeof a logical database, the selection include must contain the following statement:
    SELECTION-SCREEN DYNAMIC SELECTIONS FOR NODE|TABLE node.
    If the node node is requested by the user of the logical databases, the dynamic selections are included in the selection screen. A user can then choose Dynamic selections to enter extra selections for the corresponding fields. If you call the logical database using the function module LDB_PROCESS, you can pass a corresponding parameter. You can use these selections in dynamic statements in the logical database program to read data. The values of the program-specific selection criteria that you defined for a node for which dynamic selections were available are also passed to the logical database. The user can also define the fields for dynamic selections as a selection view for the logical database.
    The selection screen of a logical database is part of the standard selection screen (number 1000) of the executable program to which the logical database is attached. It has a standardized layout - the selection criteria and parameters appear on separate lines in the order in which they were declared. You can change the layout using the SELECTION-SCREENstatement.
    The runtime environment generates the selection screen with number 1000 for every program in which the attributes do not contain a different selection screen version. You can prevent certain input fields from the selection screen of a logical database from appearing on the selection screen by defining selection screen versions with a screen number lower than 1000 in the selection include, and entering this version number in the program attributes. By pressing F4 there, you can get an overview of the selection screen versions defined in the logical database concerned. To define a selection screen version, use the statements SELECTION-SCREEN BEGIN|END OF VERSION. Within these statements you can use SELECTION-SCREEN EXCLUDEto specify fields that you do not want to appear on the selection screen.
    If the attributes of an executable program contain the number of a selection screen version, the version is used in the standard selection screen. Although the input fields that you excluded from the selection screen are not displayed, the corresponding selections still exist, and you can still edit them in the program or by calling the function module LDB_PROCESS.
    DATABASE PROGRAM:
    The database program contains the ABAP statements used to read the data and pass it to the user of the logical database. There is a container for special subroutines into which, amongst other things, the data from the database tables is read. These subroutines are called by the reporting processor in the runtime environment in a sequence that has been predefined by the structure. The database program is determined by the structure and selections and can be adapted or expanded to meet your requirements.
    The name of the database program of a logical database ldbconforms to the naming convention SAPDBldb. It serves as a container for subroutines, which the ABAP runtime environment calls when a logical database is processed. The sequence of the calls and their interaction with the events in executable programs or the function module LDB_PROCESS depends on the structure of the logical database.
    A logical database program usually contains the following subroutines:
    · FORM LDB_PROCESS_INIT
    Called once only before the logical database is processed. It prepares it to be called more than once by the function module LDB_PROCESS.
    · FORM INIT
    Called once only before the selection screen is processed.
    · FORM PBO
    Called before the selection screen is displayed, each time it is displayed. Consequently, it is only called when you use the logical database with an executable program, not with the function module LDB_PROCESS.
    · FORM PAI
    Called when the user interacts with the selection screen. Consequently, it is only called when you use the logical database with an executable program, not with the function module LDB_PROCESS. The interface parameters FNAME and MARK are passed to the subroutine.
    FNAME contains the name of a selection criterion or parameter on the selection screen.
    MARK describes the selection made by the user: MARK = space means that the user has entered a simple single value or range selection. MARK = '*' means that the user has also made entries on the Multiple Selection screen.
    · FORM LDB_PROCESS_CHECK_SELECTIONS
    Called instead of the subroutine PAI if the logical database is called using the function module LDB_PROCESS without a selection screen. This subroutine can check the selections passed in the function module interface.
    · FORM PUT_node
    Called in the sequence defined in the structure. Reads the data from the node nodeand uses the
    PUT node.
    statement to trigger a corresponding GETevent in the ABAP runtime environment. The PUT statement is the central statement in this subroutine: It can only be used within a subroutine of a logical database. The logical database must contain the node node, and the subroutine name must begin with PUT_node. The PUT statement directs the program flow according to the structure of the logical database. The depth to which the logical database is read is determined by the GET statements in the application program or the interface parameter CALLBACK of the function module LDB_PROCESS.
    First, the subroutine PUT_root is executed for the root node. The PUT statement then directs the program flow as follows:
    i. If the database program contains the subroutine AUTHORITY_CHECK_node, the first thing the PUT_node statement does is to call it.
    ii. Next, the PUT statement triggers a GET event in the runtime environment. If there is a corresponding GET nodestatement in the executable program to which the logical database is linked, the associated event block is processed. If the CALLBACK parameter of the function module LDB_PROCESS is filled accordingly, the corresponding callback routine is called.
    iii. The PUT statement directs the program flow
    (a) To the next subroutine of a node that follows directly, if a lower-level node (not necessarily the very next) in the same subtree is requested by GET in the executable program or in the function module.
    (b) To the subroutine of a node at the same level, if the preceding node branches to such a node and if a GET statement exists for such a node in the executable program or the function module.
    The PUT statement in that subroutine starts again at step (i). In the subroutine of the lowest node in a subtree to be processed using GET, the program control does not branch further. Instead, the current subroutine is processed further. When a subroutine PUT_node has been executed in its entirety, the program flow returns to the PUTstatement from which it branched to the subroutine PUT_node.
    iv. When control has returned from a lower-level subroutine PUT_node, the PUTstatement triggers the event GET node LATEin the runtime environment.
    · FORM AUTHORITY_CHECK_node
    Called automatically by the PUT node statement. In this subroutine, you can specify authorization checks for the appropriate node node from the structure of the logical database.
    · FORM PUT_ldb_SP
    Called when the user makes a selection using a search help to process the key chosen in the search help. ldb is the name of the logical database. From this subroutine, you can use the entries in the search help tables to read the relevant entries from the root node root. The processing in the program can then be triggered using PUT root. The subroutine PUT_root is then not called automatically.
    · FORM BEFORE_EVENT
    Called before an event, the name of which is passed in the parameter EVENT. Currently, the EVENT field can only contain the value START-OF-SELECTION, to call a subroutine before this event.
    · FORM AFTER_EVENT
    Called after an event, the name of which is passed in the parameter EVENT. Currently, the EVENT field can only contain the value END-OF-SELECTION, to call a subroutine after this event.
    · FORM par_VAL, selop_VAL, selop-LOW_VAL, selop-HIGH_VAL
    Called when the user calls possible values help for the parameter par or the selection criterion selop. These must belong to the selections in the logical database.
    · FORM par_HLP, selop_HLP, selop-LOW_HLP, selop-HIGH_HLP
    Called when the user calls possible values help for the parameter par or the selection criterion selop. These must belong to the selections in the logical database.
    Example
    Suppose that in the logical database structure, LFB1 is a branch of LFA1.
    and that the following selection criteria are defined in the selection include:
    SELECT-OPTIONS: slifnr FOR lfa1-lifnr,
    sbukrs FOR lfb1-bukrs.
    A section of the database program would then read:
    FORM put_lfa1.
    SELECT * FROM lfa1
    WHERE lifnr IN slifnr.
    PUT lfa1.
    ENDSELECT.
    ENDFORM.
    FORM put_lfb1.
    SELECT * FROM lfb1
    WHERE lifnr = lfa1-lifnr.
    AND bukrs IN sbukrs.
    PUT lfb1.
    ENDSELECT.
    ENDFORM.
    An executable program (report) linked to the logical database could contain the lines:
    GET lfa1.
    WRITE lfa1-lifnr.
    GET lfb1.
    WRITE lfb1-bukrs.
    In this example, the runtime environment calls the routine put_lfa1 after the event START-OF-SELECTION. The event GET lfa1 is triggered by the statement PUT lfa1.
    Once the corresponding event block in the program is complete, PUT lfa1 branches to the subroutine put_lfb1.
    From this subroutine, the event GET lfb1 is triggered in the application program. If LFB1 is the last node to be read, processing resumes with the SELECTloop in put_lfb1. Otherwise, the program flow moves to the subroutine put_node of the next node. At the end of the SELECT loop of the last node, processing resumes in the SELECTloop of the node at the next level up. The example of programming using nested SELECT loops is only used to make the program flow clearer. In a real logical database, you would avoid doing this in order to minimize the number of database accesses.
    Regards,
    Rajesh K Soman
    Please reward points if helpful.

  • What is  logical database

    hi,
    what is logical databse  and its application.
    please tell ...
    thanks

    I have explained below the steps of how a LDB works in a report program.
    Logical database is a program which fetches data from the database and provides it to the other programs.
    It has its own selection screen. When we use a LDB in a report program, that selection screen automatically appears for this report program.
    In order to use it in a report program:
    1. We have to mention the LDB name in the attributes of report program… say for eg: we mention PNP (is one of the LDB).
    2. We have to mention a node in the report program. Node is nothing but a work area.
             This is done by declaring the TABLES statement in the report program.
              For eg:      TABLES : PERNR
              PERNR is a structure which contains the basic details of an employee (related to HR module)
    3. We have to mention the internal tables within which the relevant data is fetched.
              This is done by declaring the INFOTYPES statement in the report program.
              For eg:   INFOTYPES: 0000, 0001,0002, 0006, 0007.
              Infotypes are nothing but a table structure. Here we are declaring the internal tables PA0000, PA0001, PA0002.....which will have the same structure of corresponding database tables PA0000, PA0001, PA0002.. in the database.
    Now, how the data is actually fetched in to the program:
    1.     The fetching of the data is trigerrred by a ‘GET node’ event.
    Say, if we mention - GET PERNR. statement in the program. The data rows satisfying the parameters selected in selection screen are fetched from database, but filled into the PERNR work area row by row.
    2.     For each row fetched into the PERNR - relevant data is fetched into the internal tables PA0000, PA0001, PA0002 from database tables. For eg: PA0002 is a database table which holds the personal details of an employee and there may be many rows of data for  the same employee. So based on the personnel number (employee number) fetched into PERNR all data records of that employee are fetched in to our internal table pa0002 from the database table PA0002.
                 Like wise , the other internal tables - pa0003, pa0006 are filled with the corresponding data.
                Like data in PERNR work area acts like a primary key to fetch the data from data base to the internal tables.           
    3.     For these data fetched into internal tables - we can write our data processing statements or just display on the list report.
                 So what ever statements we write between GET PERNR. and END SELECTION. are executed repeatedly like within a loop until all data records satisfying the parameters entered in selection screen are fetched into the node(work area) PERNR.
                 GET PERNR.   * like LOOP.
                           write pa0002-name.   * This statement is executed for each data record fetched into the work area PERNR.
    other data processing statements.
                 END-SELECTION        * like END LOOP.
    Reward if useful.
    Regards,
    Pavithra

  • Alter database OR alter system?? what is the logic?

    Hi,
    this is just a general question not related to any particular issue. I seem to be missing the logic behind when we need to use the "alter system ... " statements and when we need to use the "alter database ..." statements. Is there a logic I can use to guess ? Or we only need to remember them (or look up for them)?
    Let's take an example.
    alter database archivelog; & alter system checkpoint;
    OR
    alter database add logfile; & alter system set undo_retention=800;
    If you have a key that can be generally applied please let me know as I am not able to find it. Thank you,
    enrico

    I am not sure if there is a general rule but this is what I use:
    alter database is about modifying the database architecture, like data files, archived log files etc.
    alter system is about modifying the instance. so, you are modifying the way oracle runs. Remember that all parameters should be done with alter system (like undo_retention)
    hope this will help you.

  • LOGICAL DATABASE IN HR ABAP PRPGRAMMING

    Hi Friends,
    what is use of LOGICAL DATABASE IN HR ABAP PROGRAMMING
    AND END-OF-SELECTION EVENT IN HR PROGRAMMING PROGRAMMING???
    regards,
    vijay.

    hi
    HR Logical Databases
    In Human Resources (HR), the following logical databases can be used as a data source for HR InfoSets:
    PNP (PNPCE)
    PAP
    PCH
    By selecting a logical database, you determine the HR data that can be reported on using an InfoSet.
    Logical Database PCH
    This logical database generally enables you to report on all HR infotypes. However, you are advised not to use this logical database unless you want to report on Personnel Planning data.
    Logical Database PNP (or PNPCE)
    Use logical database PNP to report on HR master data. It is possible to use logical database PCH to access this data, but PNP meets such reporting requirements more quickly because it is best suited to the task of selecting persons.
    Logical database PNP enables you to access HR master data and infotypes from Personnel Planning. For example, you have the following options:
    Reporting on the costs, number of attendees booked, and instructor for a business event on which an employee is booked
    Reporting on working time and planned compensation for a position that an employee occupies
    Reporting on the validity and proficiency of a qualification that an employee fulfils
    From a technical perspective, this means you can use PNP to report on all of the infotypes that exist for objects (infotype 1000) that have a direct relationship (infotype 1001) with the Person object.
    The ability to access infotypes from Personnel Planning using logical database PNP is a special feature that you can only use in the context of SAP Query and Ad Hoc Query. You cannot use this functionality for ABAP reports you programmed yourself.
    You can also use logical database PNP to report on data from Personnel Time Management (infotypes 2000 to 2999) and Payroll (special payroll infotypes for the USA and customer infotypes; for more information, access Customizing for the Human Resources Information System and see Payroll Results).
    Logical Database PAP
    Logical database PAP enables you to access data from Recruitment.
    regards
    navjot
    reward if helpfull

Maybe you are looking for

  • Where is the microphone button in iMessage?

    I am trying to dictate text. Does the iPhone 4 have this option? I read the 5.0 update and it said tap the microphone button. Can't seem to find it. Thx for any help.

  • OEM 10.1.0.4 (with 9.0.4.2) on WINDOWS ANYONE ??????

    Is anyone on the Windows platform using OEM Grid Control 10.1.0.4 with the iAS component patched up to 9.0.4.2 ? We currently have 10.1.0.4 with the 9.0.4.0 iAS component installed. If you look at the Oracle January 2006 Critical Patch Update, Oracle

  • How can I catch error in JheadStart lastest version

    Dear Forum I want to catch the errors in my Strut Action How can i do it, and then show in the in the component <messages> <messageBox id="messageBox" model="${data}"/> </messages> in my uix page. I want to Know how to use the model {data} Please hel

  • Download multiple reports in one hit

    I am just wondering if there anyway to have apex to download multiple reports with one button? The normal way I deal with reports is create the query within shared components, and then create a button on a page that links to the print URL of the repo

  • Goods Receipt to Production

    Hi Experts! I'm looking on the SAP documentation where its describe the Goods Issue to Production Process. Basically I want to know how the system determines when a receiving goods on a warehouse if the material that is receiving needs to be stored o