LDB-Queries

Hi ALL,
I need to access logical database PSJ and tables are PROJ and PRPS_R.
The queries are
1. I need to fetch PROFIT CENTER (PRCTR) from PROJ
2. I need to fetch COST CENTER (FKSTL) from PRPS_R.
Based on this PROJ-PRCTR from selection screen , I need to fetch some more fields.
In the beginning , I will mention in the ATTRIBUTES : PSJ
In the program,I will give GET PROJ.
After this , I need to select some fields from PRPS_R.
I dont know how to proceed.
Points will be awards in advance

hi,
look sample report <b>RPSISPE000</b>
and use dynamic (free) selections
hope that helps
Andreas

Similar Messages

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.

Infoset Query- How do I clear the in-built selection screen in LDB

Dear Experts,
When LDB is used in queries unwanted selection screen blocks appear.
Please help in getting rid of the same.
Kind Regards
Jogeswara Rao

Hello Jogeswara,
1. In the Infoset push button Extras and then select Code tab.
2. Select AT SELECTION-SCREEN OUTPUT for Code Section.
Suppose your query is based on logical database KDF and you went to hide the SELECT-OPTIONS for Company Code.
loop at screen.
if SCREEN-NAME = '%_KD_BUKRS_%_APP_%-TEXT' OR
     SCREEN-NAME = '%_KD_BUKRS_%_APP_%-OPTI_PUSH' OR
     SCREEN-NAME = '%_KD_BUKRS_%_APP_%-TO_TEXT' OR
     SCREEN-NAME = '%_KD_BUKRS_%_APP_%-VALU_PUSH' OR
     SCREEN-NAME = 'KD_BUKRS-LOW' OR
     SCREEN-NAME = 'KD_BUKRS-HIGH'.
    screen-invisible = '1'.
    screen-active = '0'.
    modify screen.
endif.
endloop.
Kind Regards,
Rae Ellen Woytowiez

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

Reg : SAP Query in LDB

Hello ,
I would like to know more about how infosets are used in LDB's.
I was recently testing a LDB of Hedge Mgmt. i selected seveal param's and found that the order of fields in the query really makes a diff. LDB's are very senstive to ordering ?? Can any one give me more info on how Infosets and SAP queries work ?
Regards,
Sri

Hi,
look here:
http://help.sap.com/saphelp_47x200/helpdata/en/d2/cb4138455611d189710000e8322d00/frameset.htm
http://help.sap.com/saphelp_47x200/helpdata/en/d2/cb43b2455611d189710000e8322d00/frameset.htm
A.
Message was edited by:
Andreas Mann

ABAP Query Using LDB

Hello Frn's
I need to develop a abap Query using LDB , for this a Infoset is allready created , which uses PNPCE LDB .
Below i am Descrbing the scenerio , for which we need to develop the query ....
Dept/Div Transfer
Employees who transferred dept or division within specified date range:
EmpID
Last Name, First Name
Date of transfer
New department
New division
Current supervisor
Old department
Old division
How can i fitler out the data of our requirment ... because i want to use same infoset in diffrent query .
Please provide some solution
Thanks and Regards..
Priyank Dixit

Hi Priyank,
First you need to check whether all the required fields are available there in the LDB PNPCE(I guess you are using the same).
I think old department, old division must not be available there. Then you need to add it in your Infoset and write custom code for these fields. Once you are done with custom coding, you can use this infoset for creating queries.
Use trnx SQ02 to create queries, either SAP or Infoset.
Hope it helps. Let me know if you need some more help.
Raveesh

Using PCH LDB

Hi Experts......
Here is my requirement...............
We have a report which retrieves the data basing on Company Code. i.e., when u give Comp. Code and Date in selection screen... it retrieves the Org. Units assigned to that comp. code and then the positions assigned to those Org. units and then the employees who are assigned to those positions.
Present we are retrieving the data using Select queries.. Can we retrieve the same using LDB PCH?
Thanking you in advance...
Regards,
Sree.

Hi Seenu,
There are some infotypes which are shared by some other logical database.
You need a report like infotype 0024 is shared by PAP and PNPCE so as there are some infotypes which are shared by other infotypes as well.
Infotype 0001 Organizational Assignment will fullfill your purpose
When you create the Infoset with logical database PNPCE you have the option to select all the personnel administration infotype as well as infotype of the related Objects Thats why you can access the data from HRP tables as well.
Warm REgards,
Warm Regards,

Added posting date period in LDB SDF!!

Hi,
i have a kinda req where i have to modify the SDF and add posting date period on the selection screen n modify the select queries accordingly therin.so i hav copied the LDB , which all places shall i make the changes to accomodate posting period ( so that it works fine)!!
Thx
Gunjan

1) add to selections
2) modify select of bsis / bsas
in put_bsis / put_bsas
SELECT (bsis_fields) FROM bsis "/ bsas
WHERE bukrs EQ save_bukrs
... and monat = sd_monat
Andreas

Could I have CASE or IF statement in FMS queries?

Is it possible to have case statements in FMS queries:
For example:
SELECT T0.[U_DepoistfeeON] case
when T0.[U_DepoistfeeON] is NOT BLANK then $[$38.111.160]='Deposit Fee'
when T0.[U_DepoistfeeON] is BLANK then then $[$38.111.160]=BLANK
end FROM OITM T0
What is wrong with above query please? Thank you very much.
I do not mind even if above query is doable with an IF statement in it.

Hi Rahul, this is what I want -
I have a user defined field attached to item master OITM. The field is called : U_DepoistfeeON
The above field contains additional depositFee taxes for selling beer bottles.
I have also created a new tax as part of Freight handling. While on Sales Order screen, the Freight (unhide first through forms field) drop down can have the new tax type selected automatically "Deposit Fee".
Thus, if the line item is of beer type that has U_DepositfeeON, then Freight field should automaticlally pick the type "Deposit Fee".
If U_DepositfeeON is zero then I would like the Freight field on Sales Order screen ($38.111.160) set to blank.
I tried to achieve this through following using case statement.
select T0.U_DepoistfeeON
from oitm t0
case
when T0.U_DepoistfeeON 0
then $http://$38.111.160='Deposit Fee'
when T0.U_DepoistfeeON = 0
then $http://$38.111.160=''
else
$http://$38.111.160=''
end;
Of course it doesn't work. Note: I know I typed in DepoistfeeON, the error is not due to that.
Thanks.

How to Dene a Data Link Between Queries: Bind Variables

This is an interesting topic and I cannot get it to work using Bind Variables.
I have 2 queries: Q1 and Q2. Q2 needs c_id, account_code and account_type from Q1.
Whe I run the data template below, I get only the data for Q1.
Now people may argue that there is no data in Q2 for the relevant clause. So if I even remove the where clause in Q2 I still get no joy i.e Data appears for Q1 but not for Q2
<dataTemplate name="FLCMR519_DATA_SET" description="Termination Quote Report">
     <parameters>
          <parameter name="cid" dataType="number" defaultValue="1"/>
          <parameter name="p_cln_id" dataType="number" defaultValue="62412"/>
     </parameters>
     <dataQuery>
          <sqlStatement name="Q1">
               <![CDATA[SELECT qm.qmd_id,
qm.contract_period,
qm.quo_quo_id||'/'||qm.quote_no||'/'||qm.revision_no reference_no,
qm.contract_distance,
qm.mdl_mdl_id,
q.qpr_qpr_id,
q.quo_id,
q.drv_drv_id,
qm.revision_user username,
pb.first_name||' '||pb.last_name op_name,
pb.telephone_no,
pb.facsimile_no,
pb.email,
q.c_id c_id,
q.account_type account_type,
q.account_code account_code,
m.model_desc,
ph.payment_description payment_head_desc,
cl.fms_fms_id,
cl.start_date,
cl.end_date,
cl.actual_end_date,
cl.con_con_id,
cl.cln_id,
cl.term_qmd_id term_qmd_id,
qm2.contract_period term_period,
qm2.contract_distance term_distance
FROM quotations q,
           quotation_models qm,
           contract_lines cl,
           personnel_base pb,
           models m,
           model_types mt,
           payment_headers ph,
           quotation_models qm2
WHERE q.quo_id = qm.quo_quo_id
       AND cl.cln_id = :p_cln_id
       AND qm.qmd_id = cl.qmd_qmd_id
       AND qm2.revision_user = pb.employee_no (+)
       AND qm.mdl_mdl_id = m.mdl_id
       AND m.mtp_mtp_id = mt.mtp_id
       AND qm.payment_id = ph.payment_header_id
       AND qm2.qmd_id (+) = cl.term_qmd_id
]]>
          </sqlStatement>
          <sqlStatement name="Q2">
               <![CDATA[SELECT ea.c_id,                  ea.account_type,ea.account_code,ea.account_name
FROM external_accounts ea
             WHERE ea.c_id = :c_id
               AND ea.account_type = :account_type
               AND ea.account_code = :account_code
]]>
          </sqlStatement>
     </dataQuery>
</dataTemplate>

Defining dataStructure section is mandatory for multiple queries.

How to use one WAD template for all the available queries

Hi,
I have created a WAD template... Now we have close to 25 queries which will use that template for displaying their output at Portal...
Is there any way that i don`t have to create multiple copies of my WAD template...
I.e. all queries would call that same template through portal...

Hi,
The Bex report uses the Standard Template 0ANALYSIS_PATTERN while it is executed.
So if your sure that the look and feel of all the Reports is going to remain same, you don't need to even attach all these Queries to Templates in WAD.
When you execute the BEx query, it would pick up the standard template and run it in portal.
But if you want to customize the Report Template:
1) You can change this standard template 0ANALYSIS_PATTERN and customize it according to ur requrement in WAD.
2) Or you can create a copy of this standard template and change it as required. Then change the template in spro (transaction RSCUSTV27) to point to this Z template.
Let me know if you need more details.
Regards,
Forum

Error while Activating / running Bex queries/reports

Hello
I have following ERRORs while activating / running BEx reports/queries.
1. While Activating BEx reports, I keel getting following ERRORS
Object directory entry R3TR ELEM E341OIR6G715GUMGN0MRXP3MA does not exist
Error when activating element BX7FOOKQB4588RROCBTC2YVZN
BEx transport request 'BIDK901352' is not available or not suitable
2. While running the BEx report/query in Bex Analyzer, I'm getting ERROR in entering the parameters, its NOT allowing / giving me option to select the parameters, for example for 0COSTCENTER, it is NOT displaying list costcenters to select before I can RUN that particular report.
3. How can I trouble shoot ERRORs related to BEx and Portal connectivity.
4. How would I setup the Variants for a Bex query/report ? Are these Variants for per user basis / per report basis. Can I have each variant for particular users OR all users must select their own variant each time when they RUN the report ?
Thanks, Sorry I have asked multiple questions, in jst one thread.
BI

Goto SE03 -->Search for Objects in Requests/Tasks option , select the object type and execute it will give all the transports it has collected before ..
Also you can use transport connection in RSA1 and select the query and find out all the objects in query locked by what request etc ..
Thanks,
Ravi

Error while transporting Queries

Hi,
I am getting this error while transporting queries!!
Object '!ZTIC_UKA' (ELEM) of type 'Query' is not available in version 'A'
Message no. RSO252
Diagnosis
You wanted to generate an object with the name '!ZTIC_UKA' (in transport request ELEM) of type 'Query' (TLOGO). This is, however, not available in the BW Repository database. It does not exist in the requested version A. If the version is 'D' then it is possible that an error arose during the delivery or installation. If the version is 'A' then the Object was either not created or not activated.
System Response
The object was not taken into account in the next stage of processing
Thanks

Hi Murali,
YOu are trying to transport the element ZTIC_UKA' of the query,may be an variable which is not colelcted in the request.
Try to transport the query through RSA1> Transport connection->Query-->give you query name -->Drag and Drop to Right hand side and Click on collect all dependent objects and check whetehr they have collected in the same request.Make sure ur variables are collected.
Tranport it now and Check.
Rgds
SVU123
Edited by: svu123 on Mar 4, 2010 7:41 AM

Need procedure for creation of BW Roles, Assigning Queries,Publishing Roles

Hi Experts,
Could you please let me know the procedure for creation of BW Roles, Assigning Queries,Publishing Roles in Business Explorer (BEx - BW 3.5)
Thanks in advance,
Andy

Hi,
Creating BW Roles
http://help.sap.com/saphelp_nw04/helpdata/en/52/6714b6439b11d1896f0000e8322d00/frameset.htm
Assigning Queries
After creating the query, save the query to a role from the query designer.
Publishing Roles in Business Explorer
https://websmp101.sap-ag.de/~sapdownload/011000358700002894802003E/HowToBIPortal1.pdf
Hope this helps you..!
-Pradnya

Problem using DECODE() function with a Query of Queries

I
posted
on my blog about an issue I was having trying to use the PL/SQL
DECODE() function with a Coldfusion Query of Queries. This function
works fine when you query a database for information. However, when
you query another query, it seems that CF doesn't recognize it. I
got errors stating that it found a left parenthesis where it
expected a FROM key word. Here is a simplified version of what I am
trying to do:
quote:

<cfscript>
qOriginal = queryNew("Name,Email,CountryCode",
"VarChar,VarChar,VarChar");
newRow = queryAddRow(qOriginal, 5);
querySetCell(qOriginal, "Name", "Joe", 1);
querySetCell(qOriginal, "Email", "[email protected]", 1);
querySetCell(qOriginal, "CountryCode", "AMER", 1);
querySetCell(qOriginal, "Name", "Sally", 2);
querySetCell(qOriginal, "Email", "[email protected]", 2);
querySetCell(qOriginal, "CountryCode", "AMER", 2);
querySetCell(qOriginal, "Name", "Bob", 3);
querySetCell(qOriginal, "Email", "[email protected]", 3);
querySetCell(qOriginal, "CountryCode", "ASIA", 3);
querySetCell(qOriginal, "Name", "Mary", 4);
querySetCell(qOriginal, "Email", "[email protected]", 4);
querySetCell(qOriginal, "CountryCode", "EURO", 4);
querySetCell(qOriginal, "Name", "John", 5);
querySetCell(qOriginal, "Email", "[email protected]", 5);
querySetCell(qOriginal, "CountryCode", "EURO", 5);
</cfscript>
<cfquery name="qCountries" dbtype="query">
SELECT DISTINCT(CountryCode) AS CountryCode,
DECODE(states, "AMER", "North America & Canada",
"EURO", "Europe & Africa", "ASIA", "Japan &
Asia","") CountryName
FROM qOriginal
ORDER BY CountryCode
</cfquery>
<cfdump var="#qCountries#">

So running this returned the following error:
Query Of Queries syntax error.
Encountered "(. Incorrect Select Statement, Expecting a
'FROM', but encountered '(' instead, A select statement should have
a 'FROM' construct.
Does anybody know why this doesn't work? Is it just not
supported? Please note that I have also tried to use the CASE()
function instead of DECODE() and that resulted in basically the
same error. For now I an looping over my distinct query with a
switch statement and manually loading a new query with the data how
I want it. But it would be a lot cleaner and less code to have the
DECODE() to work. Thx!

DECODE() is an Oracle function, not generic SQL. Q-of-Q is a
very limited subset of SQL and lacks many functions and clauses
available in standard SQL, especially what you may be used to using
in your particular RDBMS.
See
Query
of Queries user guide
Phil

LDB-Queries

Similar Messages

Maybe you are looking for