PNP and PNPCE databases in ESS

HI,
As all you know standard ESS works on PNP logical database.but we have a situation in our project that we should use PNPCE database instead of PNP.
So i would like to get your inputs on the usage of PNPCE in ESS .will there be any bad impact of using that database
helpful inputs will be rewarded
Bala

Hi Bala,
It's very interesting question.
In case of PNP we are using the employee number as the base and using the sap logon name of this user pernr.
But if we are able to do the same with Person ID of the employee then I think we will be able to use the ESS with PNPCE.
I am not sure that is this possible but just giving a thought.
Regards,
Umesh Chaudhari.

Similar Messages

PNP and PNPCE databases in ESS portal

HI,
As all you know standard ESS works on PNP logical database.but we have a situation in our project that we should use PNPCE database instead of PNP.
So i would like to get your inputs on the usage of PNPCE in ESS .will there be any bad impact of using that database
helpful inputs will be rewarded
Bala

Hi Bala,
It's very interesting question.
In case of PNP we are using the employee number as the base and using the sap logon name of this user pernr.
But if we are able to do the same with Person ID of the employee then I think we will be able to use the ESS with PNPCE.
I am not sure that is this possible but just giving a thought.
Regards,
Umesh Chaudhari.

Tell me about PCH , PAP and PNPCE database using in HR reports

Hi SAP-HR Experts .
May anybody tell me about PCH , PAP and PNPCE database using in HR reports .
Does anybody have any ABAP report code about using thses LDB's .
I always used PNP database in my reports , i never come across in which i should use PCH , PAP and PNPCE database .
may some body tell me the practical use these LDB's .
My Best Regards to ALL : Rajneesh .

     minimize the amount of programming required, it often makes sense to use logical databases when generating reports. Reports are special programs that provide selection screens and access databases. The logical database PNP consists of the database driver SAPDBPNP and is activated using the report attributes. It fulfils three main functions:
     Data retrieval:
HR data is written for each employee to the main memory, where it can be processed.
     Screening: A selection screen enables you to select employees in accordance with organizational criteria. For example, you can select all of the hourly wage earners of a particular personnel subarea.
     Authorization check: The implicit authorization check is another advantage of the logical database. Personnel data is frequently confidential and it does not make sense to allow all programs carry out the authorization check.

PNP and PNPCE

What is the difference between PNP and PNPCE. why we are using PNP instead of PNPCE. In what situation we use PNPCE..
Please focus on this issue.
Regards
vamsi.

0712 is used in Concurrent Employment, it is for Main Assignment of a person.
I think he wanted to mention 709 Infotype that is used to determine pernrs for a person.
Every person in Concurrent Employment (CE) environment can hold multiple positions, each position will have one pernr, so one person can have many pernrs. (one for each job/position). These infotypes are useful while fetching data for all pernrs of a person. PNPCE is the logical database that facilitates all this process.

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

How to add table Z to infoset that is using PNP or PNPCE

hello my friends... i thing that the subject explains my situation... i want to add a Z table to infoset that is using PNP or PNPCE database, then i want to use the fields of Z table to selection criteria
regards and thanks in advance
Mário

Hi Mario,
As you go to GOTO - Global Properties while maintaining the infoset, you will realize that an infoset can either have a logical database or table join-not both at the same time-.
However, in your case, you can use References - Text field for respective fields in field group.
If it is a custom infotype, you can directly relate the text table to the domain of the data element of the infotype field.
-Please check IT0002 Country of birth as reference-
Regards,
Dilek

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

Management Global Employee Vs C.E + PNP or PNPCE

All,
We are moving towards implementing u201CManagement Global Employeeu201D. I am new to u201CManagement Global Employeeu201D and I found some good documentation at www.saphelpbykevin.com . Kevin you did great job there like you did with us in Boise, Idaho. Any way first I wanted to understand the key differences between C.E and MGE?
After that what effort we need to do in order to change our ABAP program. Can we use PNP with MGE ?
Iu2019ve worked on Concurrent Employment in 2006 and I remember we had a hard time changing all our HR ABAP program and LDB to PNPCE . Are we talking about the same effort here? If any body of you has any suggestion , key point please share with me .
Thanks,
Saquib Khan

Lol!
I didn't see post until now...Not sure if you received the response yet...
MGE is a subset or submodule of CE.
CE concept is more align with and more import if you use SAP Payroll and Time. CE is concurrent employment where a person holds more than one position at a time in the same country.
MGE is management global employee. Where a person move from one position to another during a duration to do an assignment. Upon completing the assignment, the person could localize there or return home.
PNP and PNPCE. PNP is being discontinued and is replaced by PNPCE. The main difference between the two is PNPCE support the PERSON ID concept. Which is the unique identifier for an employee. It would be best to use PNPCE with MGE as you need that PERSON ID in the HR Report Category.
Kevin T. Nguyen-Tu
www.saphelpbykevin.com

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 - PNP, PCH, PNPCE

Hi Experts,
Im New to ABAP HR,
I would like to know about the logical databases we are using .
Logical Database - PNP, PCH, PNPCE, basic principles
If any body cud let me know about the differences , requiremnts , associated with these Logical databses will be much helpful for me.
Thanks
Rohini Devi
[email protected]

Hi Rohini...
Global Employee Programming
Thanks
Message was edited by:
Aslam Riaz

Selection screen and logical database PNP

hi all,
I am having a requirement to produce a HR Report where i need to use logical database PNP. Now the issue is i need to supress some of the elements of standard selection screen of PNP and add a couple of fields of mine.
i have been looking all around and i got few of the below methods.
its good to use a report category.
somewhere it says include it in ur program using selection screen block..
can you please guide me which is the best way and what would be a perfect solution?
thanks in advance,
Reena

In the Program Attributes, click on the pushbutton 'HR Report Category'.Click on the 'Create' icon in the pop-up window that comes up. You will get a list of all the available Report Categories. Go through the list & if you don't find one that suits you, select one that is closest & click on the 'Copy As' icon in the menu bar..
Now, you can remove the unwanted fields & add yours for selection. save it & and attach it to report in the attributes.
~Suresh

Change of LDB from PNP to PNPCE

HI All,
I have a HR program where LDB PNP is used. Now I need to change the LDB from PNP to PNPCE. Can any one please tell me what are the mandatory change I need to do in the program after changing the LDB.
Thanks & Regards,
Arnab

Hi,
Purpose
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.
Prerequisites
A report that wants to use the PNPCE must enter this in its report attributes under Logical database.
In addition, the PERNR structure must be declared in the report using the 'TABLES PERNR' statement. You can only use the PERNR structure again in certain circumstances. The use of the 'GET PERNR' event is therefore forbidden. Instead, use the 'GET PERAS' event. Except for the PERNR-PERNR component, all other components of the PERNR structure are no longer filled and have initial values. This kind of programming (with the exception of PERNR-PERNR) therefore not permitted.
In addition to the 'GET PERAS' event, you can also use the GET PERSON' and 'GET GROUP' events. To be able to use these events, you must declare them using the NODES statement (NODES PERSON', 'NODES GROUP', or. NODES PERAS').
Explanation of Terms
If the 'GET PERSON' and 'GET GROUP events and the 'AS PERSON TABLE' addition for the INFOTYPES statement are not used, the report indicates that it does not require the functionality for evaluating Concurrent Employment. In this case, the report runs in a PNP-compatible session. This is referred to as PNP mode in the following documentation. On the other hand, if the report uses the functionality for evaluating Concurrent Employment we refer to CE mode.
Features
Process of an Evaluation
The PNPCE selection screen offers you as standard a range of functions that you can use to restrict the personnel number and person selection. These are discussed in more detail in the following sections. The process is initially as follows regardless of whether the report runs in CE or PNP mode. All available functions and selection conditions leads to the selection of personnel numbers. If you use the sorting function, this set of personnel numbers is then sorted according to the sort criteria you selected. In PNP mode, the GET PERAS event is triggered as a result for each personnel number.
In CE mode, the persons belonging to the personnel numbers are determined first for all personnel numbers selected. The GET PERSON event is then triggered for each person. The person ID is specified in the OBJID component of the PERSON structure. PERNR_NUM contains the total number of personnel assignments (= personnel numbers) that this person has and the ALL_PERNRS table, which contains a list of these personnel numbers regardless of whether they were actually selected or not. The SELECTED flag is set to X for the personnel numbers selected. The flag is initial for all personnel numbers that are not selected. The PROCESS flag specifies whether the personnel number should be processed in the rest of the process. This flag is set to X by default for the personnel numbers selected. However, the report can set or delete this flag at the GET PERSON event for all personnel numbers. In this way, report and logical database communicate with each other which enables the report to control the rest of the process.
In the next step, the logical database groups all personnel numbers of a person that are to be processed (that is, all personnel numbers that have the PROCESS flag set). The report can control the type of grouping using the PNPCE_GROUPING_FROM_PAYROLL flag (normal or payroll grouping) and using the PNPGPRSN (grouping reason) and PNPGPVAL (grouping value) parameters of the selection screen. The GET GROUP event is triggered for each group of personnel numbers determined. The GROUPING_REASON and GROUPING_VALUE components contain the grouping reason and grouping value of this group. The number of personnel numbers that belong to this group and that are processed subsequently is in PERNR_NUM. The included ALL_PERNR table contains a list of these personnel numbers with additional information. The SELECTED flag specifies whether the current personnel number was originally selected (flag is set) or was marked by the report as to be processed. GROUPING_BEGDA and GROUPING_ENDDA contain the validity period that the personnel number has for this grouping. The NO_AUTHORITY flag is set if there is insufficient authorization for a personnel number. This personnel number is not processed further. The SORT component defines a standard sort order for the personnel numbers of a group. The report can change this by overwriting the values. In this way, report and logical database communicate with each other, which controls the further processing sequence of the personnel numbers.
The GET PERAS event is then triggered for all personnel numbers of the group (with the exception of the personnel numbers for which no authorization exists) in the sequence defined by the SORT component (see above). The SELECTED, GROUPING_BEGDA, and GROUPING_ENDDA components have the same meaning here as with the GET GROUP event. The PROCESSED_BEFORE flag specifies whether the personnel number has already been processed once before (it is possible that the personnel number belongs to several groupings and has been therefore been processed several times).
Thanks and Regards
Ravi

Difference PNP and PNPCH

Hi Experts,
What are major differences between logical database PNP and PNPCH.
Thanks,
Ankur

Hi,
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.

HR LDB PNP and customer infotypes in 640

Hello,
I encountered the following problem during an upgrade from 4.6C to SAP ERP Central Component 5.0. When using logical database PNP and customer infotypes the syntax check produces the following syntax error:
- INCLUDE report "%_HR9731" not found
I have added an example program below. Prerequisite for this program is that the cutomer infotype 9731 exists in the system.
Has anyone experienced this problem before? And if so, is there a solution? I can program some workarounds, but I prefer a solution, which does not involve changing my code.
Regards,
Marcel
REPORT ZTESTINFOTYPES.
tables: pernr.
infotypes: 0000,
0001,
0002,
9731 mode n.
start-of-selection.
get pernr.
write / p0002-pernr.
end-of-selection.

Hi all,
"You will have to run report RPUMS40CCI (XPRA for generation of
infotype include) for existing customer-defined infotypes.
If you have not run this report then please do so.
The report RPU40CCI creates the infotype include %_HRnnnn (nnnn =
infotype number) and the additional data structure Pnnnn_AF (nnnn =
infotype number) for the given infotype, provided that the correspondin parameter ("generate infotype include" or "generate additional data
structure") are set on the selection screen. If the parameter "maintain only T77ID" is set, no infotype include or additional data structure is maintained, only those entered in table T77ID."
Best Regards
Silvio Galery

ABAP-HR, using two LDB ie, PNP and PCH

Hi friends,
How can i use two logical database regarding to master data and organization managemnt. if i use PNP in Attributes LDB, how can i get tables regarding to organization mangent in reports, so that i can retrieve data from PNP and PCH.
Effecient answer will be rewarded points....
Thanks&Regards
Shiva Prasad

Hi Amit,
Thanks for yor valuable answer, i have tried it using 1st mentioned method, but i couldn't get. can u give me sample code.
i didn't try for the 2nd method.
i will try.

PNP and PNPCE databases in ESS

Similar Messages

Maybe you are looking for