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.

Similar Messages

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

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

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

What is the difference bwt other spl. indicator and normal spl. indiactor

Hi
What is the difference bwt other spl. indicator(OBXT) and normal spl. indiactor(OBYR)?
As per my knowldege other spl ind. which is used for not to update books
and normal spl. ind. will updated the books?
it is right.
if that is right than in the both the cases i am able to see open items?
can any body guide me in this matter.
Thanks inadvance
satya

Hi Satya:
From my point of view, I think
OBYR is "Define Alternative Reconciliation Account for Down Payments";
OBXT is "Define Alternative Reconciliation Account for Vendors".
As long as your customizing is correct, specify the numbe of the alternative reconciliation account and make sure that the account is created, these two types of special G/L indicators will update the booking, you will find the open item under the correct account# as well.
Good luck
Z.T

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 Group and Rptcurrency dimension

Hi All
How to use GROUP dimentions in currency translation. what is the difference between rptcurrency and Group dimension.
I am not using Consolidation,But can i use the Group dimension in the currency translation
Can someone through light on this .

Yes got some idea Raghu. thanks
what i am tring to do is :
I want to test the currency translation in the Group mode. not in a rpt currency mode as mentioned in the note : 1254330. for my planning applicaiton.
1) I am able to do the currency translation from LC to Rpt currency in Rptcurrency mode.
2) How can i perform the same in the group mode. what steps do i need to maintian in the Group dimensioin.
3) Can i remove the Rptcurrency dimension and use the Group dimension in my planning application.
4) If i use the Group dimension does it work same as the Rpt currency dimesnion in my planning application.
I am bit confused with the properties invloved in the group dimension. how can they be used for my currency translation.
Thanks for response
Regards
AK

Difference bwt default and value

Hello frnds
what is the difference between below two statements:
data : f(5) value 'sap',
f(5) default 'sap'.
thnks,
SUnny

Hi,
data: name type char10 value 'Hello'.
*data: name type char10 default 'Hello'. "it throws syntax error
parameters: p_name type char10 default 'Hello'.

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.

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

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

What is the difference between ABAP and HR-ABAP?

Hi people,
Could u just tel me abt what is the difference between ABAP and HR-ABAP?
Thanks in advance,
Sanjeev K.V

Hi Sir ,
Please have a look below .Hope it is suitable and simpler solution for your question.
Please do reward if useful.
Thankx.
HR deals with the INFOTYPES which are similar to Tables in General ABAP.
There are different ways of fetching data from these infotypes.
There are different areas in HR LIKE Personal Admn, Orgn Management, Benefits, Time amangement, Event Management, Payroll etc
Infotypes for these areas are different from one another area.
storing of records data in each type of area is different
LDBS like PNP are used in HR programing.
Instead of Select.. we use some ROUTINES and PROVIDE..ENDPROVIDE.. etc
and in the case of Pay roll we use Clusters and we Import and Export them for data fetching.
On the whole Normal ABAP is different from HR abap.
Also,
HR:
HR deals with the INFOTYPES which are similar to Tables in General ABAP.
There are different ways of fetching data from these infotypes.
There are different areas in HR LIKE Personal Admn, Orgn Management, Benefits, Time amangement, Event Management, Payroll etc
Infotypes for these areas are different from one another area.
storing of records data in each type of area is different
LDBS like PNP are used in HR programing.
Instead of Select.. we use some ROUTINES and PROVIDE..ENDPROVIDE.. etc
and in the case of Pay roll we use Clusters and we Import and Export them for data fetching.
On the whole Normal ABAP is different from HR abap.
For Personal Admn the Infotypes start with PA0000 to PA1999
Time Related Infotypes start with PA2000 to PA2999.
Orgn related Infotypes start with HRP1000 to HRP1999.
All custom developed infotypes stsrat with PA9000 onwards.
In payroll processing we use Clusters like PCL1,2,3 and 4.
Instead of Select query we use PROVIDE and ENDPROVIDE..
You have to assign a Logical Database in the attributes PNP.
Go through the SAp doc for HR programming and start doing.
http://www.sapdevelopment.co.uk/hr/hrhome.htm
See:
http://help.sap.com/saphelp_46c/helpdata/en/4f/d5268a575e11d189270000e8322f96/content.htm
sites regarding hr-abap:
http://www.sapdevelopment.co.uk/hr/hrhome.htm
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PAPA/PAPA.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PAPD/PAPD.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PYINT/PYINT_BASICS.pdf
http://www.atomhr.com/training/Technical_Topics_in_HR.htm
http://www.planetsap.com/hr_abap_main_page.htm
You can see some Standard Program examples in this one ...
http://www.sapdevelopment.co.uk/programs/programshr.htm
http://searchsap.techtarget.com/originalContent/0,289142,sid21_gci1030179,00.html?Offer=SAlgwn12604#Certification
http://www.erpgenie.com/faq/hr.htm.
http://www.planetsap.com/hr_abap_main_page.htm
http://www.sapbrain.com/TUTORIALS/FUNCTIONAL/HR_tutorial.html
These are the FAQ's that might helps you as well.
http://www.sap-img.com/human/hr-faq.htm
http://www.sapgenie.com/faq/hr.htm
http://www.planetsap.com/hr_abap_main_page.htm
http://www.atomhr.com/library_full.htm
HR Long texts Upload
Look at the below link
And finally,
Few notes are below:
InfoSets in the HR Application
You can use SAP Query in HR to report on HR data. Queries are maintained as described in Creating Queries. The special features of queries created for HR are described in Maintaining Queries in the Human Resources Application. The maintenance procedure for HR InfoSets differs from the described procedure inasmuch as HR data fields are grouped together in infotypes.
InfoSet management in SAP Query is also used for InfoSet Query. For further information, see Functions for Managing InfoSets.
If you want to create InfoSets for HR, you can use logical databases PNP, PNPCE, PAP, and PCH (see HR Logical Databases). The database you must use to create your InfoSet depends on the component in which the data you want to report on is stored.
The reports you can execute using InfoSets based on logical databases PNP (or PNPCE) or PCH are similar, but differ in that they can select different objects. The following table describes the connection between the logical database, and the infotypes you can include in an InfoSet. It also provides you with one or two examples of reports that you can execute using the appropriate InfoSets.
Logical database PNP/PNPCE* PCH PAP
Selection of Persons Objects from Personnel Planning Applicants
Infotypes that can be included in the InfoSet Infotypes for· Personnel Administration (0000-0999) · Time Management (2000-2999) · Payroll infotypes · Infotypes for Personnel Planning objects that can be related to persons If the object type is specified:· Infotypes for the object type · Infotypes for objects that can be related to the specified object typeIf the object type is not specified:· All infotypes · Infotypes for Recruitment (4000-4999)· Some infotypes for Personnel Administration (such as 0001 and 0002)
· Customer infotypes
Reporting examples · Selection of all persons who participated in a specific business event, output of prices for reserved business events · Selection of all persons assigned to a specific personnel area, output of qualifications held by these persons · Selection of all business events held in London in March, output of all persons who participated in these business events · Selection of all positions assigned to a specific organizational unit, output of all persons assigned to the positions · Selection of all applicants hired last year to work on special projects, output of addresses for the applicants selected
Logical database PNPCE (PNP Concurrent Employment) functions just like logical database PNP. The procedure for creating InfoSets is also the same. It only becomes significant if you work with Concurrent Employment.
Creating InfoSets
The maintenance procedure for HR InfoSets differs from the procedure described so far in this section inasmuch as HR data fields are grouped together in infotypes. To set up an InfoSet for the HR application, proceed as follows:
1. On the initial screen for maintaining InfoSets, enter a name for the InfoSet and choose Create.
2. On the next screen, enter a name for the InfoSet and select one of the HR logical databases in accordance with your reporting requirements.
Customer infotypes can be created on all HR logical databases. In each individual case, therefore, you must decide which database to select so that you can report on customer infotypes.
This screen enables you to enter an authorization group. All of the queries that are subsequently created using this InfoSet can only be executed by persons who have this authorization group.
3. Choose .
This takes you to the Infotype Selection for InfoSet screen. You now have the option of creating field groups and assigning fields as required for non-HR InfoSets. Field groups that correspond to infotypes and already contain fields, however, are always created for HR InfoSets. The field groups are displayed in an overview tree in the top right section of the screen.
The infotypes that you included in the InfoSet are displayed in an overview tree on the left of the screen. The infotype fields that are already included in field groups are displayed in a different color, and the corresponding field group ID is displayed.
In the standard system, a field group is created automatically for each infotype that you included in the InfoSet (a field group corresponds to an infotype).
In the standard system, each field group contains the infotype-specific fields. To ensure that working with the InfoSet is as easy as possible, you are advised to restrict your use of fields in each field group to those you really require. This means you should remove fields that are not required.
An infotype's fields must only be assigned to the pertinent field group. Make sure this assignment is correct. If the assignment is incorrect, the InfoSet could be rendered unusable.
When an InfoSet is created, the following fields are transferred automatically to the first field group:
§ Logical database PNPCE or PNP Personnel number
§ Logical database PAP Applicant number
§ Logical database PCH Object ID, plan version, and object type
6. Determine the fields that must be included in the field groups of your InfoSet. If you require further information, see Assigning Fields to a Field Group.
If you want, you can change the default sequence of field groups and fields as required using Drag&Drop.
7. To save the InfoSet, choose .
8. To generate the InfoSet, choose .
On the Change InfoSet (InfoSet name) screen, you can choose Edit ® Change infotype selection to add more infotypes to the InfoSet, or to remove infotypes from the InfoSet. Remember to regenerate the InfoSet afterwards.
This screen also enables you to update InfoSets if, for example, the system contains new additional fields for specific key values. To do so, choose InfoSet ® Additional functions ® Update additional HR fields.
9. Go back to the initial screen for InfoSet maintenance.
10. Choose User group assignment.
11. Select a user group, and save your entry.
sample code
START-OF-SELECTION.
GET pernr.
rp_provide_from_frst p0000 space pn-begda pn-endda.
if pnp-sw-found EQ '1'.
READ TABLE p0001 WITH KEY pernr = p0000-pernr.
if sy-subrc = 0.
write : p0001-plans. " earliest.
endif.
endif.
rp_provide_from_last p0014 space pn-begda pn-endda.
if pnp-sw-found EQ '1'.
READ TABLE p0014 WITH KEY pernr = p0000-pernr.
if sy-subrc = 0.
write : p0014-LGART. .
endif.
endif.

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

Difference bwt PNP & PNPCE

Similar Messages

Maybe you are looking for