PNP & PNPCE?

WHATS THE DIFF BETWEEN PNP & PNPCE?
WHY DO W E CANT ENHANCE FEW INFOTYPES?
THANKS & REGARDS
DEEPU R D

WHATS THE DIFF BETWEEN PNP & PNPCE?
PNP is for personnel administration
PNPCE is for personnel Admin with concurrent employment
WHY DO W E CANT ENHANCE FEW INFOTYPES?
As per my knowledge SAP given scope to enhance the field where it required.
Infotypes which can't be enhanced SAP doesn't given any provisioin.
Best Regards

Similar Messages

Hi this pandu can i know what is the diff between pnp &pnpce ldb

hi,
this pandu can i know what is the diff between pnp &pnpce logical database.
thanks and regards,
pandu.

pretty much the same.. except that PNPCE has additional functionality to deal with Concurrent Employment.. PL go through <a href="http://help.sap.com/saphelp_erp2005/helpdata/en/c6/8a15381b80436ce10000009b38f8cf/frameset.htm">SAP Help</a> for more info.
~Suresh

Support for Logical Databases PNP/PNPCE

On this topic I would like to know:
1. Will SAP will continue to support PNP or will support for PNP be eventually phased out?
2. Were can I find the official SAP document that covers the introduction of PNPCE?
3. Where is it stated officially by SAP the recommendation for all new development to use PNPCE?
Edited by: John McKee on Oct 14, 2009 11:17 AM

Hi John,
I can not make an official SAP statement here but given the fact that there are several thousand reports based on PNP from SAP and even more from Customers the answer is:
1. Will SAP will continue to support PNP
Yes
1. will support for PNP be eventually phased out?
No
2. Were can I find the official SAP document that covers the introduction of PNPCE?
3. Where is it stated officially by SAP the recommendation for all new development to use PNPCE?
Go to trasnaction SE36 enter PNPCE as LDB and read the thorough documentation.
PNPCE has simply a nicer Selection screen and much more options to predefine it in the report class.
If you have no CE you can simply use it in the old PNP-mode for details see the extensive documentation.
Hope that answers your qestions,
Michael
Edited by: Michael Fruechtl on Oct 14, 2009 11:47 AM

What is the diffrence betwen the pnp&pnpce

what is the diffrence betwen the pnp&pnpce

Hello,
Both are same, PNP is the Older one and PNPCE is the latest One.
Both are used for HR master data only.
Check this link for more information:
http://help.sap.com/saphelp_erp2004/helpdata/en/e1/e1f83f6e5a11d687620000e82158f1/frameset.htm
I hope it will help you.

Difference bwt PNP & PNPCE

Hello SAP Minds,
Can any one please focus on the difference between PNP and PNPCE with example.
Thanks a lot for your support.

Hi vamsi,
I think those are logical databases for creating infosets.I am giving link for you.There you can find the some information about those.
If you found helful reward me....
http://help.sap.com/saphelp_nw04/helpdata/en/d2/cb455f455611d189710000e8322d00/content.htm
Cheers
Srihari.

FM LDB_PROCESS with PNP or PNPCE does not work...

This is the code. This do nothing, no errors, no results.(The system have employees.)Please help with some advice.
José.
TABLES: PERNR.
TYPE-POOLS: RSDS, RSFS.
DATA: CALLBACK TYPE TABLE OF LDBCB,
      CALLBACK_WA LIKE LINE OF CALLBACK.
DATA: SELTAB TYPE TABLE OF RSPARAMS,
      SELTAB_WA LIKE LINE OF SELTAB.
DATA: TEXPR TYPE RSDS_TEXPR,
      FSEL TYPE RSFS_FIELDS.
Refresh: Callback.
Clear: Callback.
CALLBACK_WA-LDBNODE     = 'PERNR'.
CALLBACK_WA-GET         = 'X'.
*CALLBACK_WA-GET_LATE    = ' '.
CALLBACK_WA-CB_PROG     = SY-REPID.
CALLBACK_WA-CB_FORM     = 'PROG_PERNR'.
APPEND CALLBACK_WA TO CALLBACK.
Refresh: Seltab.
Clear: Seltab.
SELTAB_WA-SELNAME = 'PERNR'.
SELTAB_WA-SIGN    = 'I'.
SELTAB_WA-KIND    = 'P'.
SELTAB_WA-OPTION = 'EQ'.
CLEAR SELTAB_WA-LOW.
CLEAR SELTAB_WA-HIGH.
APPEND SELTAB_WA TO SELTAB.
Refresh: TEXPR, FSEL.
Clear: TEXPR, FSEL.
CALL FUNCTION 'LDB_PROCESS'
EXPORTING
    LDBNAME                     = 'PNP'
    EXPRESSIONS                 = TEXPR[]
    FIELD_SELECTION             = FSEL[]
TABLES
    CALLBACK                    = CALLBACK
    SELECTIONS                  = SELTAB
EXCEPTIONS
    LDB_NOT_REENTRANT           = 1
    LDB_INCORRECT               = 2
    LDB_ALREADY_RUNNING         = 3
    LDB_ERROR                   = 4
    LDB_SELECTIONS_ERROR        = 5
    LDB_SELECTIONS_NOT_ACCEPTED = 6
    VARIANT_NOT_EXISTENT        = 7
    VARIANT_OBSOLETE            = 8
    VARIANT_ERROR               = 9
    FREE_SELECTIONS_ERROR       = 10
    CALLBACK_NO_EVENT           = 11
    CALLBACK_NODE_DUPLICATE     = 12
    OTHERS                      = 13.
   case sy-subrc.
      when 1. raise ldb_not_reentrant.
      when 2. raise ldb_incorrect.
      when 3. raise ldb_already_running.
      when 4. raise ldb_error.
      when 5. raise ldb_selections_error.
      when 6. raise ldb_selections_not_accepted.
      when 7. raise variant_not_existent.
      when 8. raise variant_obsolete.
      when 9. raise variant_error.
      when 10. raise free_selections_error.
      when 11. raise callback_no_event.
      when 12. raise callback_node_duplicate.
    endcase.
if sy-subrc ne 0.
      message id sy-msgid type sy-msgty number sy-msgno
           with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
endif.
*&      Form PROG_PERNR
*       text
*      -->NAME       text
*      -->WA         text
*      -->EVT        text
*      -->CHECK      text
FORM PROG_PERNR USING NAME TYPE LDBN-LDBNODE
                      WA    TYPE PERNR
                      EVT   TYPE C
                      CHECK TYPE C.
    message id sy-msgid type sy-msgty number sy-msgno
           with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
CASE EVT.
    WHEN 'G'.
      WRITE: / WA-PERNR.
      ULINE.
    WHEN 'L'.
ENDCASE.
ENDFORM.                    "PROG_PERNR

Yes, this is the best way of fill out these tables. But my problem is different, I'm trying to get the infotypes info through a BADI or function module.
I received a response from SAP about how to resolve this issue. I need to use the old way:
SUBMIT...RETURN to call another report with the PNP/PNPCE Logical Database.
That's the reason for use the LDB_PROCESS function module. (SUBMIT...RETURN uses too many memory and processor resources) Now I know that this function module does not work with HR Logical Databases because the Infotypes structures.
Thank you by your quick reponse.
José

What is the main diff b/n ldb pnp and pnpce?

hi ,
what is the main diff b/n ldb pnp and pnpce?
thanks.

Hi Arun,
PNP/PNPCE - Both are Logical Databases for PA Module
In PNPCE - CE stands for Concurrent Employment.
The differnces are:
The PNPCE logical database supports the evaluation of HR master data. It includes the functions of the PNP logical database and offers additional evaluation options. Therefore, you should use the PNPCE logical database instead of the PNP logical database for all new developments.
The enhanced functionality of PNPCE in comparison to PNP essentially concerns the evaluation of Concurrent Employment, that is the possibility to group evaluate several assignments/personnel numbers of a person. The new events 'GET PERSON' and 'GET GROUP' as well as an enhanced syntax for the INFOTYPES statement (addition AS PERSON TABLE) for the procurement of infotype data enable you to use the new functionality. The use of these new functions is optional. You can run a PNPCE report that does not use the new events and the addition for the INFOTYPES statement in a PNP-compatible session. Since the PNPCE also has an improved selection screen, each report benefits from this even if the report does not use the functions for evaluating Concurrent Employment.
Hope this helps you.
Regards,
Chandra Sekhar

Change existence report LDB PNP to PNPCE

Hi HR experts !!!
We want to convert all the existence reports which are using PNP to PNPCE? Do you guys have idea how much time itll take? As we have around 1000 reports.
I need your input guys
Cheers
Usman

Usman,
I am also on HR project . Were also discussing the same thing !! but it looks like it need another project to change the LDB to PNPCE as reason being lots of reports are written using PNP logic in mind.
But PNPCE Behaves different . Well I must say its another project to change 1000 reports
FYI...
It is better to go in for PNPCE even if you do not have Concurrent Employment to take advantage of the new lDB. The one thing PNPCE does do is when the GET executes only the infotype records retrieved for the interval requested will be retrieved. Whereas PNP by default, will retrieve all infotype records for a given PERNR.
SAP recommends to use PNPCE for all new development. But all the features are not available as of now. The Time Management functions for concurrent employment have not been released for all customers. They are activated for selected pilot customers only. Can get some info in SAP Note : 518520 , 516489..
OSS Note # 561645 ( LDB PNPCE: compatibility with PNP )
Symptom
In some respects, logical database PNPCE responds differently from logical database PNP. This may cause errors in applications that do not know this difference.
Other terms
PNP, PNPCE, payroll period, PNPTIMR9, PNPTIMRA, error message, information message
Reason and Prerequisites
There are the following differences between logical databases PNP and PNPCE:
Unlike PNP, logical database PNPCE does not have two radio buttons you can use to set the payroll period (parameters PNPTIMR9 and PNPTIMRA). Instead, the payroll period is set via parameter PNPTIMED (displayed as a dropdown box on the selection screen). This difference must be taken into account when you call a PNPCE report from another program. Otherwise, in incorrect system response occurs in the PNPCE report called. Problems may also occur if you convert an existing PNP report to PNPCE and want to use an old (PNP) variant.
If you enter an invalid payroll arear or an invalid payroll period, PNP issues an error message whereas PNPCE only issues an information message. This causes problems if you run a PNPCE report in the background because in this case the program runs into an endless loop instead of terminating.
Solution
Implement the attached corrections or import the corresponding support package.
This changes PNPCE in such a way that it responds like PNP
Moreover, also look at OSS
PNPCE: Performance improvement ( OSS note # 687004)
Symptom
You use a report that is based on logical database PNPCE. Either the performance of the report is poor, or the program terminates due to a memory overflow.
Other terms
Performance, PNPCE, 0000, 0001, buffer, memory space, memory space consumption, partitioning, FILL_0000_0001_BUFFER, T77S0, LDB, PCEPS, PNP mode
Reason and Prerequisites
The PNPCE can be used in a PNP-compatible mode. The mode is 'PNP-compatible' if the report does not program on events GET PERSON and GET GROUP and does not use the 'AS PERSON TABLE' extension for the INFOTYPES statements (for more details refer to the documentation of logical database PNPCE in Transaction SE36).
In this mode the performance is worse, as if logical database PNP is used. After the implementation of the correction from this note, the performance is significantly improved.
Another problem is that all personnel numbers that meet the entered selection criteria are internally selected during the execution of the report. Then the system imports all data records of infotypes 0000 and 0001 for all these personnel numbers because they are needed for the internal processing for different reasons. If the amount of personnel numbers or the amount of data records per personnel number is very large, memory problems can occur. The attached correction solves the memory problems.
Solution
Implement the correction according to the correction instructions or import the corresponding Support Package. If you implement the correction manually, you first have to implement Note 705870.
A part of the correction causes the internal processing of the persons/personnel numbers in blocks. If logical database PNPCE runs in PNP mode, the block-by-block processing is executed based on personnel numbers. Otherwise (in CE mode) it is executed based on persons. In PNP mode, logical database PNPCE behaves exactly like logical database PNP concerning the block processing. The settings are also made along the lines of logical database PNP. For a more detailed description refer to Note 705870.
Standard setting of the block size
In CE mode the block size is set to 10,000 persons by default. That is, as long as the number of selected persons does not exceed this value, no block processing is executed at all. A memory space analyses showed that this does not cause problems with the memory space in a system with an average number of infotype 0000 and infotype 0001 data records. However, if the amount of data records (= splits) is very large in your system, you have to reduce the maximum block size manually.
Manual setting of the block size
There are two different options to set the block size manually: a) report-specific by means of a switch which you have to set in the source code of the report, and b) cross-system by means of a switch in switch table T77S0.
The report-specific switch is called PNP_MAX_PARTITION_SIZE. It has priority (if switch T77S0 is activated) and must be set in the source code of the report at event START-OF-SELECTION at the latest.
Example: Set the maximum block size (number of persons that can be processed together) to 250:
START-OF-SELECTION.
PNP_MAX_PARTITION_SIZE = 250.
The switch is recommended for customer-specific reports requiring a lot of memory and therefore need to minimize the additional memory space of logical database PNPCE. It is not suited for SAP standard reports because the report would have to be modified in that case.
The cross-system switch is maintained in table T77S0. It affects all reports that are based on logical database PNPCE and do not use the report-specific switch PNP_MAX_PARTITION_SIZE.
The switch belongs to the LDB group and is called PCEPS. The switch is maintained in Transaction SM30 (enter table 'T77S0' and choose 'Maintain'). The switch is delivered (for Release 4.70 in a Support Package) with initial value (0). An initial value causes the switch to be ignored and the standard setting to be used instead. If you want to set the switch, set it to a numeric value. This value specifies the maximum number of persons that are processed together in a block.
Example:
LDB PCEPS 250
For more information on the procedure of a system upgrade refer to Note 317722
Thanks
Saquib
Message was edited by: Saquib Khan

Logical DataBase PNP - Adding customised Field

How do everyone,
I have recently added a new field to the HR master infotype 0001.
How does one include this new field within the locgical database i.e. PNP, PNPCE
so that it is automatically included in the report selection screen??
Any help or suggestions would be much appreciated.
Andy

Hi,
Follow the link.
Re: Logical Database PNP. HR and Unicode
Regards
Rajesh Kumar

Authorization on PNP logical database

My limited understanding of authorization on reports that uses PNP/PNPCE logical database is that if a user who runs the report does not have authorization for any of the declared infotypes then the report stops with message 'no authorization for infotype ...'. And if the user has authorization for the infotypes but do not have authorizations for some of the PERNRS then it will only display those records that user have authorization for and shows message saying no. of skipped records (of those that user did not have authorization).
Programmers here say that the users who do not have authorization for some infotypes should still be able to see list for other infotypes that they do have authorization for.
-- Please shed some light on this and guide me if there is a cookbook/document out there about this.
Thanks a bunch.
Netra

Hi Neha,
Adding further.
Each report is different in its own way and there are various ways of controlling the access to the Reports based on ur scenario.
The first check happens at the P_ABAP level where in it checks the access to the program corresponding to that report and level of access (1,2).
If these are missing then it goes further to check for the explicit access
in objects like
P_ORGIN, P_PERNR etc.
Now in some of these reports the processing is designed in such a way that if the access to an IT is not available it throughs a error message and the processing of the report stops at that instance (this depends on the message type which has been defined at that instance to be displayed) so at this instance you need to have access to that IT to proceed further but in some other cases the check does happen but the processing continues without stopping at that check failure(example is P_PERNR, the check happens but is not required for processing the report).
This is one example but there could even more criterion based on which the processing of the report is terminated or allowed to continue depending on the reports utility
<a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/9f/dbaabc35c111d1829f0000e829fbfe/frameset.htm">The different message types and their significance is as follows</a>
So what you have been told by programmers is true in some cases but surely not accross all the HR reports and all auth objects.
Hope this helps
Manohar
Message was edited by:
Manohar Kappala

PNP authority check

Hi all,
I have a problem with authority check in a report.
I have to access to a field in an infotype and subtype.
I have all authorizations for this subtype and infotype.
I'm trying to retrieve this data from an employee, but this employee has informed another subtype in this infotype where I haven't permisions.
As in the source code there aren't access to this subtype where I haven't permisions, I found that the systems make it's authority check before the START-OF-SELECTION in class CL_HRPAD00AUTH_CHECK_STD, method IF_EX_HRPAD00AUTH_CHECK~CHECK_AUTHORIZATION.
The system takes the employee number, gets all its informed infotypes and subtypes and perform the authority check for my user, so I can't access to this employee information.
I think this authority check is made by the use of PNP logical database.
Is there any way to avoid this authority check?
Regards,
Angel Cepa

Hi Angel Cepa,
first of all: maybe you can use logical database PNPCE, because PNP is obsolet.
Anyway, please refer to the documentation of PNPCE (transaction SE36), that may solve your problem.
PNP/PNPCE knows two ways to check authority:
1. If no authorization exists for even one individual data record of one of the infotypes used, processing of the personnel numbers is terminated by default (switch "PNP_SW_SKIP_PERNR" = Y)
2. If you set this switch (at the INITIALIZATION or START-OF-SELECTION events) to N, no more personnel numbers (without authorization) are skipped. Only the data records for which no authorization exists are rejected (that is, not made available).
So, simply set the switch, mentioned above, to "N" and you will have access to this employee (except the infotype-records, you don't have authority for).
Regards
CHRIS

Difference between PNP and PCH logical database

WHats the difference between PNP nd PCH? When to use which??
Tx

Hi,
The Difference is only with in an SAP R/3 system in which Concurrent Employment is active, reports are executed by the PNPCE logical database. The general logic of the PNPCE logical database corresponds to the PNP logical database. The PNPCE logical database can also process the concept of Concurrent Employment.
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.
Check this link for more details
http://help.sap.com/saphelp_erp2004/helpdata/en/e1/e1f83f6e5a11d687620000e82158f1/frameset.htm
Reward points
Regards

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 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

Sort payroll simulation (payslips) by last name

Hello experts,
Is there any possibility to sort payslips TCode PC00_M01_CALC_SIMU by the last names of employees?
Thanks a lot in advance.
Regards,
Florian Heuer

Payslips displayed in payroll driver are in in the order of the employees processed through logical dbase PNP/ PNPCE .
You could try to copy the current report caetegory currently assigned to the country's payroll drirver you're using, set the 'Sort allowed' field for this custom report category, and config your payroll driver to use this custom report category through T599W. This way, when running your country's payroll driver, it will have a sort option for you use if needed.
Rgds.

PNP & PNPCE?

Similar Messages

Maybe you are looking for