Using ldb PCH in HR
hi ,
can somebody give me sample code for using PCH logical database. and the events used in it
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.
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.
The InfoSet is based on logical database PCH
Provided that object selection is switched on, InfoSets based on this database enable you to use InfoSet Query to select objects of one object type, such as business events, qualifications, and positions. You can use all of the fields of infotypes allowed for the object in question, and all of the object types and their allowed infotypes that can be related with the selected object type, as selection criteria and for output.
When you create an InfoSet, you determine the object type that you can select using an InfoSet. The generated InfoSet can only be used to select this particular object type. If you want to create reports for business events, qualifications, or positions, for example, you must create three separate InfoSets. This means the reports can only be executed separately.
If you do not select an object type when you create the InfoSet, you can only use the InfoSet for InfoSet Query if object selection has been switched off.
Kanagaraja L
Similar Messages
-
Regarding ldb pch (include DBPCHSEL for selection screen)
hi experts,
i am developing report for training and event mgmt details for this i m using ldb pch and include DBPCHSEL for standard selection screen what i want that in this include extra parameters & select-options/selection fields for input are already declared but i dnt want all of these plz help me how to remove extra selection fields which i dnt want on my customized report i want only one to two selection fields.
plz help me how to remove these extra fieldsdear amit,
ven ever u use ldb "pch" it is not asking for report category means it wnt allow u create a report category.then plz gve another solutions. -
Changes in Standard RHBUCH00_LSO with LDB PCH
Hi All,
Greetings!!
I have to make changes in RHBUCH00_LSO which uses LDB PCH . The changes are to display Applicanr also with Participant also . The Standard report at selection screen take only one object type (P Participant ) or (AP Applicnat) .
As it uses LDB making changes in it is difficult .
I am trying yo use FM LDB_PROCESS to call again LDB for AP .
Please throw some light on the use of FM LDB_PROCESS or is some other alternative is available .
Thank YouHi rhaul,
1. I don't we can directly do as per ur requirement.
2. Bcos No-Intervals cannot be modified using Loop at screen.
3. Another option is to copy the standard Ldb and use it.
regards,
amit m. -
Can I use LDB in a WDA !?
Can I use LDB in a WDA !?
Just like we do in a HR ABAP program with PNP or PCH .
and get the infotype data with Get PERNR .
If the LDB doesn't work in WDA again,
Is there any other special tools in WDA for HR develop !?!?!?
Thanks a lot.Hi Wang,
Here in my project what we are doing to read the infotype is see the code whcih will give clear idea.
Here in my example i am reading the infortype 221.
<b>Code:</b>
method GET_221_DATA .
This method gets the 0221 data by calling the model component.
The dataset retrieved is then mapped to the Do_Not_Change node.
DATA:
lt_infotype_datasets TYPE /kyk/s_paitf_dataset_tab,
lv_temp TYPE string. " to hold the fieldname in a string type
DATA lo_nd_node_it0221structure TYPE REF TO if_wd_context_node.
DATA lo_el_node_it0221structure TYPE REF TO if_wd_context_element.
DATA ls_node_it0221structure TYPE wd_this->element_node_it0221structure.
declarations for 0221 data
DATA:
ls_infotype_dataset TYPE /kyk/s_paitf_dataset,
it_ui_structure TYPE /kyk/t_dataset_uistructure,
wa_ui_structure TYPE /kyk/s_dataset_uistructure,
wa_field_structure TYPE /kyk/s_value_of_field,
wa_field_structure1 TYPE /kyk/s_value_of_field,
it_field_structure TYPE /kyk/t_value_of_field.
DATA:
l_ref_interfacecontroller TYPE REF TO /kyk/iwci_c_pa_model,
l_componentinterface TYPE REF TO if_wd_component_usage.
l_componentinterface = wd_this->wd_cpuse_model( ).
IF l_componentinterface->has_active_component( ) IS INITIAL.
l_componentinterface->create_component( ).
ENDIF.
l_ref_interfacecontroller = wd_this->wd_cpifc_model( ).
ls_node_it0221structure-begda = '18000101'.
ls_node_it0221structure-endda = '99991231'.
ls_node_it0221structure-pernr = PERNR.
l_ref_interfacecontroller->readinfty(
EXPORTING
begda = ls_node_it0221structure-begda " Begda
endda = ls_node_it0221structure-endda " Endda
infty = '0221' " Infty
pernr = ls_node_it0221structure-pernr " Persno
subty = '*' " Subty
IMPORTING
patif_dataout = lt_infotype_datasets " /kyk/s_Paitf_Dataset_Tab
delete lt_infotype_datasets where subty ne 'YAWA' and subty ne 'YANA'.
navigate from <CONTEXT> to <NODE_IT0221STRUCTURE> via lead selection
lo_nd_node_it0221structure = wd_context->get_child_node( name = wd_this->wdctx_node_it0221structure ).
*--- first loop at infotype dataset
LOOP AT lt_infotype_datasets INTO ls_infotype_dataset.
it_ui_structure = ls_infotype_dataset-uifields.
lo_el_node_it0221structure = lo_nd_node_it0221structure->create_element( ).
lo_nd_node_it0221structure->bind_element( new_item = lo_el_node_it0221structure set_initial_elements
= abap_false ).
*---set lead selection
lo_nd_node_it0221structure->set_lead_selection( lo_el_node_it0221structure ).
**---second loop at uifieldstructure
LOOP AT it_ui_structure INTO wa_ui_structure where structurename eq 'HCMT_BSP_PA_CA_R0221'.
it_field_structure = wa_ui_structure-fieldvalues.
*--- Do not read if STATUS is not 'X'
READ TABLE it_field_structure WITH KEY fieldname = 'ADJRN' INTO wa_field_structure1.
IF wa_field_structure1-fieldvalue <> 'X'.
lo_nd_node_it0221structure->remove_element( lo_el_node_it0221structure ).
ELSE.
*---third loop at fieldstructure
LOOP AT it_field_structure INTO wa_field_structure.
Set all the general attribute values
lv_temp = wa_field_structure-fieldname.
CALL METHOD lo_el_node_it0221structure->set_attribute
EXPORTING
value = wa_field_structure-fieldvalue
name = lv_temp.
ENDLOOP.
ENDIF.
ENDLOOP.
ENDLOOP.
endmethod.
Warm Regards,
Vijay -
Renaming the Selection Text of LDB PCH
Hi -
Can anyone suggest a way to Rename the Standard Selection Screen Variable Name ( Selection Text in a Standard Selection Screen ) of a LDB ( PCH )to a custom one ?
Eg. There is a need to change the Object ID ( PCHOBJID - Selection Text ) to " Org. Unit " .
Thanks,
MullaiHi,
You can do that, suppress that field whatever you are getting from the standard LDB and define a selection field in your custom program witht he same name and use your own selection text and check,
This should work for you.
Thanks,
Mahesh. -
How to use LDB PNP with ABAP objects in a program
Hello,
I am wondering if anybody has used the HR logical database(LDB) PNP with user defined ABAP objects in a program? I am using the FM- <b>LDB_PROCESS</b> but its not working. Also assigning PNP in the attributes section of the program -- so that I can use predefined fields from the LDB and then invoking the FM doesn't work -- throwing 'Logical database already active' error.
I suppose even with the ABAP objects and the new FM -- I should still be able to utilize the pre-defined fields of the PNP database -- and also the built in authorizations. I cannot use GET PERNR and REJECT as they give errors. I understand that the use of HR-macros (RP-PROVIDE-FROM-LAST and et al.) are not allowed as they use the table work area -- which is not allowed in ABAP-OOPS.
I would really appreciate if anyone could show me some insight regarding this. Thank you.
Kshitij R. DevreHi Kshitij
It would be really good if we could use both together. But as I know, it is not possible. "GET pernr." is an event-like loop statement and so cannot be used in OO context. And I guess, the same restriction holds for the "LDB_PROCESS" since it uses LDB-specific processing.
What I suggest you is to use standard and BAPI functions.
Sorry for giving bad news...
*--Serdar -
Facing Problem while Debugging a custom report using LDB
Hi Gurus,
I have requirement to modify a custom report program related to FI. This program used Logical database ZDF ( Copied original DDF) for data fetching.
when i am trying to see the data in debugging mode, its not allowing to check in start-of-selection event. only in the initialization & end-of-selection i could able to debug.
when i put breakpoint in initialization, it is allowing to see the flow till a Get Event occurs in the code, once a Get event occur the debugger is coming out and displaying the report.
If anybody faced this kind of problem when debugging a report using LDB, please share how you resolved it. If there are any other ways to debug a program of this kind please help me.
Thanks,
NandaHi Amith,
I checked that way also, i put break point in database program of the copied LDB, but its not allowing to check the flow in that program also.
Please suggest any other ways.
Thanks,
Nanda -
How to Create and Use ldb in reports?
Give examples that uses ldb.
Hi Albert
You can create and maintain logical databases via the transaction <b>SE36</b>.
You can relate a LDB to your program using the 'Attributes' window by entering the LDB name to the relevant field.
Additional to what Andreas told, many HR programs use LDB. Check programs with 'RH*'.
Regards
*--Serdar <a href="https://www.sdn.sap.com:443http://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.sdn.businesscard.sdnbusinesscard?u=qbk%2bsag%2bjiw%3d">[ BC ]</a> -
How to get a default variant screen using LDB.(HR-ABAP)
Hello,
I have created a report using LDB PNP.Used HRBEN000 as a hr report category.
Got a default selection screen, I want to add one more field, for this I have selected the field from further
selection button, and displayed on the screen. Now i saved as a variant.
how to get this default screen using the variant in the report/program when executed?
Please help me.
Thanks&Regards,
Archana.Hi ,you camn always make your Z report category...if the field is present in further selection tab..
if not you can create your own paramerter or select option.....
but you have to handle it in your code ....as get pernr wont filter on its basis(parameter select optyin created by you)
but why loop at screen is not working?
let me know how you are doing...
have to do it in at selection-screen output -
Want to have own selection screen in HR-ABAP report using LDB
Hi experts,
I am working on HR-ABAP report using LDB pnp and infotypes..But, here we get the built in selection criterion..but I want my own selection screen to be displayed..whats the solution for this??? Is it possible to create my own selection screen instead of default one..and how???
Please help me..its very urgent..Hi,
chk this out:
Create Report Categories
In this step, you define the report categories and determine the layout
of the standard selection screen for these report categories. You can
create report categories for programs or queries that are based on the
PNP or PNPCE logical databases.
The definition of report categories is divided into two sections:
o In the Change Report Category view, you define general attributes
such as sort order, input fields for date, and so on.
o In the Change Selection Criteria view, you define which selection
fields of the logical database should be avaliable on the selection
screen.
Example
You want to set up your system so that your employees can only start
evaluation reports for Payroll if they use a payroll area. Within a
payroll area, you should be able to select according to personnel
number. Additional selection criteria should not be possible and you
should not be allowed to enter a sort sequence.
Standard settings
The standard system already contains report categories. You can find the
attributes of the report categories in the table.
Note the following five report categories in particular:
o Report category ' ' is the SAP default report category for
programs that are based on the PNP logical database.
o Report category PNPCE is the SAP default category for programs that
are based on the PNPCE logical database.
o Report category '00000000' is the customer-specific default category
for programs that are based on the PNP logical database.
o Report category '0PNPCE' is the customer-specific default category
for programs that are based on the PNPCE logical database.
o Report category __X2001 is the default category for Queries that
are based on an InfoSet of the PNP LDB.
o Report category QUEPNPCE is the default category for queries that
are based on an InfoSet of the PNPCE LDB.
The default report categories are used when a report is called if
the report has not been assigned a report category.
Parameters and Options for Report Categories of the LDB PNP and PNPCE
Parameters and Options in Screen Area General Data
If you activate this parameter, you can only enter data on the data
selection period if you use reports that have been assigned. The
same date entries are then used for the person selection as for the
date selection.
o Matchcode allowed
If you activate this parameter, you have use of a Matchcode
pushbutton (search help) if you use reports that have been assigned.
This pushbutton enables you to perform the person selection.
o Sort allowed
If you activate this parameter, you have use of a Sort pushbutton if
you use report that have been assigned. This pushbutton enables you
to define a sort order before you execute the report.
o Organizational structure allowed
If you activate this parameter, you have use of an Org.Structure
pushbutton if you use reports that have been assigned. This
pushbutton enables you to perform the person selection.
Note:
For more information about these options, see the online
documentation under this path:
SAP Library -> Human Resources -> Reporting in Human Resources
Management -> Standard HR Reports -> Report Selection Screen in
Human Resources Management.
Parameters and Options in Screen Areas Data Selection Period/Person
Selection Period/Payroll Area/Period/Year
o Options for data selection period and person selection period (key
date and so on)
Here you define which options for date and person selection are
available for reports that have been assigned.
o Options for payroll area/period/year
Here you define which options for selection using payroll
area/period/year are available for reports that have been assigned.
Parameters and Options in Screen Area Selection View
o Type/Name
This parameter enables you to use selection views to define report
categories. You use the selection view selected here to determine
which fields are available in the Dynamic Selectionsy.
Note:
You create selection views for the PNP and PNPCE logical databases
in the Object Navigator (SE80):
1. Start the Object Navigator (SE80)
2. Choose Workbench -> Edit Object.
3. Choose the More... tab page and the Selection view on this tab
page.
4. Choose Create.
5. In the Create Selection View dialog box, choose the For any
tables option.
6. In the Name of view field, enter a name for your selection view.
7. In the Tables dialog box, enter the name of the table from which
you want to use fields.
Note:
When you enter the table name, observe the naming convention in
Personnel Administration:
Infotype number: nnnn -> table name: PAnnnn
8. Choose Continue.
9. In the Functional groups area, define functional groups by
assigning a name and a number.
10. Assign fields from the selected tables to the functional groups
by entering the number of the desired functional group in front of
each field.
11. Save your entries.
For more information about adjusting the dynamic selections using
your own selection views, see the online documentation under the
following menu path:
SAP Library -> Human Resources -> Reporting in Human Resources
Management -> HR Standard Reports -> Report Selection Screen in
Human Resources Management -> Enhancing the Selection Screen -
Dynamic Selections.
If you do not want to offer dynamic selections, make the following
settings:
- LDB PNP: In the Selection view field, enter PNP_NO_FREE_SEL.
- LDB PNPCE: Leave the Selection view field empty.
Parameters and Options in Screen Area Data Selection Period/Person
Selection Period/Payroll Area/Period/Year
o Available input parameters, date or period entry (today, key date,
all, and so on), and standard value.
Using the Standard value option, you define which of the selected
options is shown.
Parameters and Options in Screen Area CE Selection Fields
o CE selection fields (external person ID, grouping reason, grouping
value)
Using the options in this area, you define whether the external
person Id, grouping reason, or grouping value are available on the
selection screen.
Note:
These parameters are only relevant for you if you implement
Concurrent Employment (see also note 517071).
Parameters and Options in Screen Area Selection view
o Dynamic selections as dialog box
If this switch is set, you can call the dynamic selections as a
dialog box.
o Dynamic selections active
If this switch is set, the dynamic selections of the logical
database are active at the start of the report.
Note that the following combinations are possible for the last two
options mentioned:
Dyn.Sel. as dialog box/Dyn.Sel. active: inactive/inactive
Dyn.Sel. as dialog box/Dyn.Sel. active: inactive/active
Dyn.Sel. as dialog box/Dyn.Sel. active: active/inactive
Activities
1. Choose Edit -> New entries.
2. Enter an abbreviation and a long text for the report category.
The customer name range for report categories is 0-9.
3. Select the For the PNPCE logical database checkbox, if you want to
create a report category for a program or for queries of the PNPCE
logical database.
4. In the General Data screen area, choose the desired options.
If you want to use selection IDs, you must have first created and
grouped selection Ids. The IMG path to do this is given in the
parameter description section.
5. In the Data selection period/person selection period or Selection
period screen area, choose the desired options.
6. In the Selection view screen area, choose the desired options.
7. In the CE selection fields screen area, choose the desired (only
possible for report categories of the LDB PNPCE).
8. Save your entries.
9. Choose the subactivity Permitted selection criteria.
10. Choose Edit -> New entries.
11. In the Select option field, use the input help to select each field
that should be available on the selection screen.
12. Select the checkbox in the 1.page column, if you want this selection
field to be available directly when you call the selection screen.
Further notes
13. If you want to copy entries, you still have to enter the selection
parameters again in the subsequent screen.
o If you create the report category '000000000', a selection screen is
generated according to report category '00000000'for all reports for
which a report category has not explicitly been assigned.
Assign Report Categories
In this step, you assign a report category to your reports.
Example
You have created your own report, for example ZPCTEST1, and would like
it to have the selection screen that corresponds to that of the
evaluation report for Payroll, which is assigned to report category
'__M00001'.
Assign report category '__M00001' to the report.
Requirements
You must have defined the Report Categories.
Standard settings
SAP Standard Reports:
In the standard system, reports are assigned a report category. If you
want to override these assignments, perform the activities described
here. If you want to assign report categories to standard reports using
SE38, this represents a modification.
Customer-Specific Reports:
For reports you have developed yourself, you can either assign report
categories by performing the activities described here or directly in SE38.
Recommendation
Only assign a report category if you have created your own reports or if
the selection screens in the standard system do not meet your
requirements.
Activities
1. Choose Edit -> New entries.
2. Perform the required assignment using the Program name and Report
category fields.
3. Save your entries.
reward if helpful
regards,
madhumitha -
Reading Locked records from HR table using LDB PNP
Hi,
I am trying to read the table pa0168 using LDB PNP.
But the problem is that get pernr staement does not retrieve locked records i.e where PA0168-sprps eq "X'.
Can anybody help me with this.
I have to use LDB so i don't want a solution of writing a select * for the pa0168 table.
hence i have to use get pernr statement but it should also retrieve locked records.
how can i achieve that.? please help
Thanks
GT
Message was edited by: GTHi GT,
In the START-OF-SELECTION event, set the parameter value
pnp-sw-ignorelockedrecords = 'N'.
Good Luck,
Suresh Datti
( Pl award points if the answer helps you ) -
How to use ldb PNPCE with FM u0091HR_INFOTYPE_OPERATIONu0092
Hi all,
Im creating a report with LDB PNPCE, this report has to create/modify infotypes of an ID person. Im trying to use de FM HR_INFOTYPE_OPERATION, but its not working A DUMP is generated, with this description:
An exception that could not be caught occurred.CX_HRPA_VIOLATED_PRECONDITION
I think that the problem is due to logical database PNPCE, because if I use PNP, its working Does anybody know anything about using the FM HR_INFOTYPE_OPERATION with the LDB PNPCE?
Thanks!!This piece of code it's working with ldb PNP
CALL FUNCTION 'ENQUEUE_EPPRELE'
EXPORTING
MODE_PREL = 'E'
MANDT = SY-MANDT
pernr = wa_p9961-pernr
infty = '9961'
SUBTY =
OBJPS =
SPRPS =
endda = wa_p9961-endda "'99991231'
begda = wa_p9961-begda "'20071201'
SEQNR =
X_PERNR = ' '
X_INFTY = ' '
X_SUBTY = ' '
X_OBJPS = ' '
X_SPRPS = ' '
X_ENDDA = ' '
X_BEGDA = ' '
X_SEQNR = ' '
_SCOPE = '2'
_WAIT = ' '
_COLLECT = ' '
EXCEPTIONS
foreign_lock = 1
system_failure = 2
OTHERS = 3
CALL FUNCTION 'HR_INFOTYPE_OPERATION'
EXPORTING
infty = '9961'
number = wa_p9961-pernr
subtype = wa_p9961-subty
OBJECTID =
lockindicator = 'X'
validityend = wa_p9961-endda
validitybegin = wa_p9961-begda
recordnumber = lwa_pa9961-seqnr
record = wa_p9961
operation = 'INS'
tclas = 'A'
dialog_mode = '0'
nocommit = ' '
VIEW_IDENTIFIER =
SECONDARY_RECORD =
IMPORTING
return = l_return
KEY =
CALL FUNCTION 'DEQUEUE_EPPRELE'
EXPORTING
MODE_PREL = 'E'
MANDT = SY-MANDT
pernr = wa_p9961-pernr
infty = '9961'
SUBTY =
OBJPS =
SPRPS =
endda = wa_p9961-endda "'99991231'
begda = wa_p9961-begda "'20071201'
SEQNR =
X_PERNR = ' '
X_INFTY = ' '
X_SUBTY = ' '
X_OBJPS = ' '
X_SPRPS = ' '
X_ENDDA = ' '
X_BEGDA = ' '
X_SEQNR = ' '
_SCOPE = '3'
_SYNCHRON = ' '
_COLLECT = ' '
But if I use ldb PNPCE instead PNP, with the events:
GET person.
GET group.
GET peras.
ths dump is generated...
Thank u!! -
FM's used in report program using ldb pnpce
hii all,
will anybody provide me function modules that are used to populate data in report program using ldb pnpce.
<REMOVED BY MODERATOR>
thanks in advance
regards
Ashweeni.
Edited by: Alvaro Tejada Galindo on Mar 18, 2008 6:01 PMU can use all the FM's which were used for LDB PNP ..
For ex : Use the below to get the payroll results ..
To get the results directory
call function 'CU_READ_RGDIR'
exporting
persnr = peras-pernr
tables
in_rgdir = pc261_tab
exceptions
no_record_found = 1
others = 2.
to get evaluation periods ...
call function 'CD_EVALUATION_PERIODS'
There are no particular FM's that will populate data in report
program .. please let me know what is the requirement ... -
Want to use ldb selection screen with select queries
I want to use ldb selection screen with select queries since ldb having performance issue .How can I use the fields of the dynamic selection of LDB in the select queries
Hi,
Check the code snippet below: Here 'XXXX' is the table for your select query.
DATA L_DS_CLAUSES TYPE RSDS_WHERE.
MOVE 'XXXX' TO L_DS_CLAUSES-TABLENAME.
READ TABLE DYN_SEL-CLAUSES WITH KEY L_DS_CLAUSES-TABLENAME
INTO L_DS_CLAUSES.
SELECT * FROM XXXX
WHERE field1 IN ...
AND field2 ....
AND (L_DS_CLAUSES-WHERE_TAB).
PUT XXXX.
ENDSELECT.
You can also try using the FM 'RS_REFRESH_FROM_DYNAMICAL_SEL' passing SY-CPROG in curr_report and 'M' for mode to get the dynamic selection screen values.
Regards,
Munesh. -
Display an extra column in the standrad report using LDB
my requirement is like this
1) to add one more parameter region in the selection screen of VI98
2) Display the region column in the output in the 3rd position
is there any way to add one more parameter in the selection screen of transaction VI98 and based on the region entered the output should be filterd(ie the records of given region only should come)
this program is using ldb VXV
and selection screen 600
is there any way to achieve this ?hi first check the report catagory of the LDB report and check whether is there any field available there...other wise create a new report catagory..
Maybe you are looking for
-
Reading values from ServletRequst in Filter
I have a filter that captures some basic info (request method and uri) from request. But whenever I read parameters contained in http request for "POST" method, I can't figure out how to repost parameters to request. I think that after I read paramet
-
How to specify "Layout Grid" or "Margin/Column" for a new doc in the Japanese version
I am using the Japanese version of InDesign CS2. When you open a new document in the Japanese version, you can specify what kind of layout grid to use "Layout Grid" (traditional Japanese layout) or "Margin/Column" (normal English layout). How do you
-
HT201317 Help with photo stream?
I have photo stream turned on at my mac and at my Iphone. In Iphoto, I clicked on an album to share to my photo stream, but it won't show up on my phone. Help?
-
Problems with sockets and hex code
When i try to send 0x9d on socket, it send 0x3f. Why? conexion = new Socket("server", 0000); escritura = new PrintWriter( conexion.getOutputStream(),true); escritura.write(0x9d); escritura.print("\u009d"); It always send 0x3f.
-
I've just started having a few problems when I try to bounce mixes internally in Logic. I set my locators, set the start and end points etc etc...Everything is fine. Start the bounce, still everything is fine. The status bar starts scrolling, passes