Issue in Query Restriction

Hi all,
I have a query in which customer is a input variable, which is optional.  My requirement is, if the user does not input any value for the customer in the report, then the report is to be restricted with a particular fixed range for  ex: 1000 - 3000.
If the user enters some value, then the report has to be restricted for the entered selection.
How to achieve this?
Thanks in advance.

HI,
Have two variables one  Var1 with user input which is restricted inside a local keygifure ie to get input from customer.
Create another variable Var2 of customer exit  which is restricted in Filter. Populate this by reading Var1 in the customer exit.
If user entry available populate them with user input value.
Else populate the value you need
Hope this helps for you.
Thanks,
Arun

Similar Messages

  • Issue In query output

    Hello Gurus,
    I am having an issue with query output.Please find below the details of it
    Unsold claims: Total---> 200
    Dispatch: Total--->118,086
    Unsold claims/dispatch--->0.001694
    This should be the output but its coming --.0033120 because itu2019s dividing with max value in dispatch which is 60,386.
    Reason: The aggregation property of Dispatch is max value. I am not supposed to do any changes in Modeling. So can we do any thing at reporting level to get the desired output?
    Desired output---->0.001694
    Output coming---->.0033120
    Please help me in getting the desired output at query level.
    Regards,

    solved with the help of nested exception aggregation

  • View Link Editor Issue - empty query clause if based on association

    JDeveloper 10.1.2
    Setup:
    - entities A and B
    - a 1 to * association from entity A to entity B (A_B_association)
    - a view of A based on entity A (AView)
    - a view of B based on entity B (BView)
    - BView has an expert mode query
    Create a view link from table A to table B:
    - choose the A_B_association under AView for the source attribute
    - choose the A_B_association under BView for the destination attribute
    - click add
    - click next
    issue: the query clause is empty
    - click next:
    info dialog pops up;
    title = "Business Components"
    message = "Restoring the default where clause."
    Note, however, that creating a view link based on the attributes works. That is, if I choose the primary key attribute under AView for the source attribute, and the corresponding foreign key attribute under BView for the destination attribute, then the wizard generates the expected query clause.
    If I create a new project and recreate the entities, the views, and the association, then I can successfully create a view link based on the association. The foreignKey value on the association end was different in the new association XML file.  I modifed the old XML file so that it used the same foreignKey element, but that did not seem to work.
    I am guessing that this is some sort of user error on my part or that we have otherwise managed to squat up our XML files.
    Any tips, hints, or ideas appreciated.
    Thanks,
    Steve

    The problem is in AView.
    We had modified the AView at one point, then reverted it to a default view of entity A. Here, "a default view" means that we undid our custom changes (apparently not thoroughly enough); that is, we did not delete it and create a default view from scratch using the contextual menu on the A entity.
    The bottom line is that the AView attributes were not being mapped to the entity -- they were showing up as calculated attributes.
    We created a "New Default View Object..." from the contextual menu of entity A, then manually corrected the AView.xml file to solve the problem.

  • Adhoc Query Issue - How to restrict /SAPQUERY/H2 access

    Hi Experts,
    I have created two User Groups HR_1 (assigned to infosets for Time data) and HR_2 (assigned to Infosets for Payroll data). Also, I want to assign the HR_1 to a user Time_admin and HR_2 to Payroll_Admin, so that Payroll admin do not have access to Time data and vice versa.
    Now I can restrict the access but when I execute the Adhoc query for the user, I can see the User group that I have assigned with a default user
    group /SAPQUERY/H2, which has access to all data.
    My question is, how can I restrict the access for the /SAPQUERY/H2 for the users so that the users have only access to their user groups i.e.,
    Time_admin to HR_1 only and Payroll_admin to HR_2 only.
    Regards
    Vikrant

    I was expecting some Answer but was unfortunate enough.
    I have found a solution and will mention it for those who face this issue in future.
    Configuration in “The Global Area (Cross Client)”, has some limitations
    1)      1) Restricting the access via T-Code S_PH0_48000510 (Ad-hoc Query) is difficult as this t-code S_PH0_48000510 uses the user group /SAPQUERY/H2 to which an Infoset is assigned /SAPQUERY/HR_ADM. This infoset has access to all the master data and is standard one (default).
    2)      Also, this is available in “The Global Area (Cross Client)”, due to which there will be access to all HR master data.
    Configuration in “Standard Area, i.e., Client Specific”
    1)      With this approach, we will do the same configurations in “Standard Area (Client Specific)” i.e.,
    I.            Create User groups (ZHR_1 and ZHR_2)
    II.            Create Infosets (X1 for time management Infotypes and X2 for PM and PA Infotypes)
    III.            Assign User Groups to Infosets (X1 to ZHR_1 and X2 to ZHR_2)
    IV.            Assign Users to User Groups (As per the requirement)
    2)      Additionally, Admin need to do two things
    I.            For the Users Set Parameters via SU3 as:
    Parameters for Users for Time Data
    Parameter ID
    Parameter Value
    Description
    AQB
    ZHR_1
    ABAP Query: User group
    AQS
    X1
    SAP Query: Infoset
    AQW
    Standard
    ABAP Query: Query area
    Parameters for Users for OM/PA data
    Parameter ID
    Parameter Value
    Description
    AQB
    ZHR_2
    ABAP Query: User group
    AQS
    X2
    SAP Query: Infoset
    AQW
    Standard
    ABAP Query: Query area
    II.            Provide access to T-Code S_PH0_48000513 (also calls Adhoc Query but this t-code will respect the parameters set by us in SU3).
    III.            As a result of this approach, the Users on executing the T-Code S_PH0_48000513 will be directly moved to the Adhoc query screen with their authorized access.
    NOTE:
    these changes cannot be transported via Transport.
    Regards,
    Vikrant

  • Issue while query execution on web analyser.

    Hi,
    I am getting an error message while query execution on web ie Record set too large , data retrieval restricted by configuration .I am able to run the same query in bex analyser without any issue .Any idea what could be the reason and solution for this issue .
    Regards,
    Neetika.

    Hi Neetika,
    The Query is exceeding the set limits,i suggest you to Reduce the time LIne for the Query, as it may be having more number of Cells in terms of Rows and Columns.
    Execute the Query for Less number of Days,if u r executing it for 1 Month then execute it for 10 Days.
    Rgds
    SVU123

  • Performance Issue-;How to restrict the total output of the report.

    Hi Experts
    I need your advise to resolve one performance issue in my BI Publisher report.
    My report query is extracting more than 80000 records at once. To load these records into the report template it is taking all most 14 to 15 hours. Unfortunately i cannot change my logic to put some more filter to restrict the query output, as this is the requirement from the client.
    Is there any way i can restrict my report so that it will extract the first 1000 record and on the event of pressing next it will extract the next 1000 record and so on from the point when it left in last time.
    Kindly let me know if you have any solution for this.
    Thanks in advance.
    Regards
    Srikant

    Hi experts...
    Any update on this...

  • MSS custom query restrictions (table/view/join)

    Dear all,
    We are currently trying to integrate a sap query which also gathers data from event management. This query is based on an infoset and a table view and not on a logical database.
    When executing the query within the portal (generictableview iview) we get the error message "No data records found". While debugging the function module HR_INFO_GET_USING_QUERY which is called here we found out that the error message is generated because no logical database is retrieved.
    Therefore my question is: are mss queries in portal restricted to queries which are based on logical databases only or can we create and use queries in portal which are based on table/views/joins?
    Any help on this issue is greatly appreciated!
    Thanks already very much in advance,
    Helga

    Hello MIG,
    I am still searching and I have not found a solution yet.
    Interestingly enough the query can be executed without any problems in R/3 but not from the portal iView. Therefore I am wondering if it is only a restriction on the MSS side.
    @forum users: did anyone of you face this problem and has a solution to it?
    Thanks very much for any input on this!
    Kind regards,
    Helga

  • Navigational attribute issue in query

    Hi gurus,
    Here is a very tricky issue that I am facing. If anyone could please help me with a workaround for the same.
    I have an infoObject called ZDIV_CUS which is basically 0CUSTOMER with 0DIVISION compounded to it. Hence, when I load data into ZDIV_CUS, I would have one record for a unique combination of customer and division. In functional words, I would have one customer maintained for multiple divisions. ZDIV_CUS also has other navigational attributes as 0SALES_OFF, 0SALES_DIST & 0SALES_GRP. Also, I have 0MATERIAL, which has 0DIVISION as a navigational attribute in my cube.
    Hence the master data for ZDIV_CUS looks as follows -
    0DIVISION    0CUSTOMER    0SALES_OFF    0SALES_GRP    0SALES_DIST
    01           100000       L001          L01           L010100
    02           100000       L005          L08           L020150
    01           100001       L001          L01           L050150
    03           100001       L005          L02           L052542
    The transactional data in my cube is as follows -
    0MATERIAL    0CUSTOMER    0DIVISION    0SALES_OFF   0NET_SALES   0MATERIAL_DIVISION (Material master div)
    102152          100000       01           L002         110000       02
    102545          100001       02           L002         12000000     02
    The above data is all transactional except for 0MATERIAL_DIVISION which comes from material division.
    My query is built in such a way that the division comes from 0MATERIAL (restricted to variable in the selection screen). ZDIV_CUS and its navigational attributes are being used in my query. The initial display is shown as per ZDIV_CUS_0SALES_OFF (i.e. sales office from ZDIV_CUS)
    The problem is that say for eg for the above mentioned scenario, the user executes the query for division 01 and the below mentioned output comes up -
    0MATERIAL_DIVISION     ZDIV_CUS    0MATERIAL    ZDIV_CUS_0SALES_OFF     0NET_SALES
    02                     100000      102152       L001                    110000
    If we take a closer look, we would know that ZDIV_CUS_0SALES_OFF should pick up value L005 and not L001 since the division for which the query is run is 0MATERIAL_DIVISION and not 0DIVISION.
    Request help to resolve the abovementioned issue.
    Thank you,
    Sree

    Can any one answer for Issue-2. Even I am also facing the same.
    Thanks in Advance.

  • How to solve this issue in query definition

    Hi Experts,
    I need to solve an issue existed in a query.
    This query is built on a infocube which main char and key figures as follow:
    sales doc., item, material, fiscal year/period, ordered qty, billed qty.
    The query has to show opened qty for specific sales doc / item level. the formula for  opened qty = ordered qty - billed qty. But some of the sales doc /item are partial delivered i.e. there are several deliveries' entries for same sales doc/itm. for example the entries as follow:
    sales doc---- item--materailfiscal year/periodordered qty-- billed qty
    20001------ --    30--- m1 2009/002  200--
      25
    20001--    30 -m1 2009/002 -  200--
    100
    Then after the execution of the query we got the opened qty: (200 - 25) + (200 - 100) = 175. This is totally wrong because the correct opened qty should be 200 - 25 - 100 = 75.
    Could any body provide a solution to get the correct result ?
    Thanks a lot
    Edited by: Leon Ouyang on Dec 15, 2008 4:12 PM
    Edited by: Leon Ouyang on Dec 15, 2008 4:13 PM
    Edited by: Leon Ouyang on Dec 15, 2008 4:43 PM

    Hi Leon,
    Somewhere in your infocube there must be an indicator whether it is the first delivery or not.
    Change ordered quantity into a resctricted keyfigure using the restriction of the indicator first delivery.
    Your overview will be:
    sales doc---- item--materailfiscal year/periodordered qty-- billed qty
    20001------ -- 30--- m1 2009/002 200--
    25
    20001-- 30 -m1 2009/002--
    100
    And your total will be correct.
    Success,
    Udo.

  • Issues with Admissions Restricted flag on Programs of Study

    Hi,
    We have had issues recently with students booking when they should not be allowed to book.  (example: admission approved for fall, but the student was able to book for the previous summer)  One suggestion from SAP was to use the Admissions Restricted checkbox located in the Program Data section of the SC "Program of Study"
    Testing went well, however, we found a couple of instances where this option did not work.
    1.  If the student had 2 admissions with the same program of study and one of them was in Rejected status, they would not be able to book.  So the scenario is...a student applied last year and was rejected as an Undeclar UG.  They applied again this year also as an Undeclar UG and were approved for Fall.  When they book for fall...the error message returns that they do not have a valid admission.
    2.  It appears that if we can no longer use the Change of Program button on the Registration tab.  If we try to change the program, we get the message that the "Student has no valid admission" for the program we are switching too.  Which they don't have an admission for the change...that's why we do the Change of Program functionality.
    I may have to file an OSS note for this, but I was wondering if anyone else used this feature and ran into the same problems.
    Thanks!
    Mike

    Hi Mike,
        If look into documentation of BADI it says "the system calls this BAdI when you process the following activities:
    RA01 - Initial registration
    RA02 - Extend study segment
    RQ01 - Change of program
    The logic you suppose to code is if you are getting value CV_ADMISSION_OK as space. Look for does that student have any approved admission for that level (UG/GR/DR). If he finds any records in Hrp1001(relat 530) with same level just set this flag to 'X'. It will allow you to change the program.
       Let's say if SAP allows you to change of program without going through this validation. Again you will get caught when student will not be able to book course because it will not find any admission for new program. This badi is allowing you override admission check.
    Thanks,
    Prabhat Singh

  • Performance issues with query input variable selection in ODS

    Hi everyone
    We've upgraded from BW 3.0B to NW04s BI using SP12.
    There is a problem encountered with input variable selection. This happens regardless of using BEx (new or old 3.x) or using RSRT. When using the F4 search help (or "Select from list" in BEx context) to list possible values, this takes forever for large ODS (containing millions of records).
    Using ST01 and SM50 to trace the code in the same query, we see a difference here:
    <u>NW04s BI SQL command</u>
    SELECT                                                                               
    "P0000"."COMP_CODE" AS "0000000032" ,"T0000"."TXTMD" AS "0000000032_TXTMD"                             
    FROM                                                                               
    ( "/BI0/PCOMP_CODE" "P0000" ) LEFT OUTER JOIN "/BI0/TCOMP_CODE" "T0000" ON  "P0000"."COMP_CODE" = "T0000
      "."COMP_CODE"                                                                               
    WHERE                                                                               
    "P0000"."OBJVERS" = 'A' AND "P0000"."COMP_CODE" IN ( SELECT "O"."COMP_CODE" AS "KEY" FROM              
      "/BI0/APY_PP_C100" "O" )                                                                               
    ORDER BY                                                                               
    "P0000"."COMP_CODE" ASC#                                                                               
    <u>BW 3.0B SQL command:</u>
    SELECT ROWNUM < 500 ....
    In 3.0B, rownum is limited to 500 and this results in a speedy, though limited query. In the new NW04s BI, this renders the selection screen unusable as ABAP dumps for timing out will occur first due to the large data volume searched using sequential read.
    It will not be feasible to create indexes for every single query selection parameter (issues with oerformance when loading, space required etc.). Is there a reason why SAP seems have fallen back on a less effective code for this?
    I have tried to change the number of selected rows to <500 in BEx settings but one must reach a responsive screen in order to get to that setting and it is not always possible or saved for the next run.
    Anyone with similar experience or can provide help on this?

    here is a reason why the F4 help on ODS was faster in BW 3.x.
    In BW 3.x the ODS did not support the read mode "Only values in
    InfoProvider". So If I compare the different SQL statements I propose
    to change the F4 mode in the InfoProvider specific properties to
    "About master data". This is the fastest F4 mode.
    As an alternative you can define indexes on your ODS to speed up F4.
    So would need a non-unique index on InfoObject 0COMP_CODE in your ODS
    Check below for insights
    https://forums.sdn.sap.com/click.jspa?searchID=6224682&messageID=2841493
    Hope it Helps
    Chetan
    @CP..

  • Performance issue on query. Help needed.

    This is mainly a performance issue. I hope someone can help me on this.
    Basically I have four tables Master (150000 records), Child1 (100000+ records), Child2 (50 million records !), Child 3 (10000+ records)
    (please pardon the aliases).
    Now every record in master has more than one corresponding record in each of the child tables (one to many).
    Also there may not be any record in any or all of the tables for a particular master record.
    Now, I need to fetch the max of last_updated_date for every master record in each of the 3 child tables and then find the maximum of
    the three last_active_dates obtained from the 3 tables.
    eg: for Master ID 100, I need to query Child1 for all the records of Master ID 100 and get the max last_updated_date.
    Same for the other 2 tables and then get the maximum of these three values.
    (I also need to take care of cases where no record may be found in a child table for a Master ID)
    Writing a procedure that uses cursors that fetches the value from each of the child table hits performance
    badly. And thing is I need to find out the last_updated_date for every Master record (all 150000 of them). It'll probably take days to do this.
    SELECT MAX (C1.LAST_UPDATED_DATE)
    ,MAX (C2.LAST_UPDATED_DATE)
    ,MAX (C3.LAST_UPDATED_DATE)
    FROM CHILD1 C1
    ,CHILD2 C2
    ,CHILD3 C3
    WHERE C1.MASTER_ID = 100
    OR C2.MASTER_ID = 100
    OR C3.MASTER_ID = 100
    I tried the above but I got a temp tablespace error. I don't think the query is good enough at all.
    (The OR clause is to take care of no records in any child table. If there's an AND, then the join and hence select will
    fail even if there is no record in one child table but valid values in the other 2 tables).
    Thanks a lot.
    Edited by: user773489 on Dec 16, 2008 11:49 AM

    Not sure I understand the problem. The max you are getting from the above is already the greatest out of the three - that's why we do the UNION ALL.
    Here's sample code without output, maybe this will clear it up:
    with a as (
    select 10 MASTER_ID, to_date('12/15/2008', 'MM/DD/YYYY') LAST_DTE from dual UNION ALL
    select 20 MASTER_ID, to_date('12/01/2008', 'MM/DD/YYYY') LAST_DTE from dual UNION ALL
    select 30 MASTER_ID, to_date('12/02/2008', 'MM/DD/YYYY') LAST_DTE from dual
    b as (
    select 10 MASTER_ID, to_date('12/14/2008', 'MM/DD/YYYY') LAST_DTE from dual UNION ALL
    select 20 MASTER_ID, to_date('12/02/2008', 'MM/DD/YYYY') LAST_DTE from dual UNION ALL
    select 40 MASTER_ID, to_date('11/15/2008', 'MM/DD/YYYY') LAST_DTE from dual
    c as (
    select 10 MASTER_ID, to_date('12/07/2008', 'MM/DD/YYYY') LAST_DTE from dual UNION ALL
    select 30 MASTER_ID, to_date('11/29/2008', 'MM/DD/YYYY') LAST_DTE from dual UNION ALL
    select 40 MASTER_ID, to_date('12/13/2008', 'MM/DD/YYYY') LAST_DTE from dual
    select MASTER_ID, MAX(LAST_DTE)
    FROM
    (select MASTER_ID, LAST_DTE from a UNION ALL
    select MASTER_ID, LAST_DTE from b UNION ALL
    select MASTER_ID, LAST_DTE from c)
    group by MASTER_ID;
    MASTER_ID              MAX(LAST_DTE)            
    30                     02-DEC-08                
    40                     13-DEC-08                
    20                     02-DEC-08                
    10                     15-DEC-08                
    4 rows selectedEdited by: tk-7381344 on Dec 16, 2008 12:38 PM

  • Issue with Query on a virtual infoprovider

    Hello,
    I am getting the following error message while executing a query on a virtual infoprovider. We have recently gone through upgrade from BI 3.5 to BI 7.0 EHP1 (SP5) and from SEM BCS 4.0 to BCS 6.0.
    EVersion not specified or not unique                                                             UCR0                006                   
    EError reading the data of InfoProvider ZBCS_CV11                                    DBMAN             305ZBCS_CV11          
    EError while reading data; navigation is possible                                          BRAIN               289                   
    I>> Row: 11 Inc: RAISE_READ_ERROR Prog: CL_RSDRV_VPROV_BASE   RS_EXCEPTION        301CL_RSDRV_VPROV_BASE
    this query has been running fine before the upgrade. In the selection screen there are two fields - version1 and version2, if I am specifying same value in both the fields then the query runs fine and if I am providing different values then the above stated error message appears.
    I have tried different settings with properties - Read mode: H,A,X and also different combination from the properties of the virtual infoprovider - with and w/o hierarchies; with and w/o navigation attributes but it did not workout.
    the only thing which has changed on this virtual provider is that I had enabled delta caching as this was supposed to be used in a multiprovider.
    Has anyone experienced similar issue or have an idea as to what is going wrong here. Please advice.
    Regards,
    Manish

    Hi Manish,
    I have exactly the same issue with a query on a virtual infoprovider after upgrading from BI 3.5 to BI 7.0 EHP1 (SP5) and from SEM BCS 4.0 to BCS 6.0.
    Would you be so kind to tell me how you fixed this. (other queries seem to be working)
    Kind regards,
    Jamie Flaxman

  • Issue with query for AR transactions posted to GL

    Hi all,
    I'm using Oracle R12.1.3.
    I have a report similar to Account Analysis Report which displays Transactions posted to GL.
    I have the following issue:
    In the result of the report if an AR transaction has 2 lines or more I get multiplication of them. So my question is how can I identify which AR transaction line is linked to GL line number?
    Here is my query:
    SELECT DISTINCT GJH.JE_HEADER_ID,
      GJL.JE_LINE_NUM,
      PARTY.PARTY_NAME CUSTOMER_VENDOR,
      RCT.TRX_NUMBER TRANS_NUMBER,
      SUBSTR(REPLACE(REPLACE(REPLACE(REPLACE(REPLACE(SUBSTR(CTL.DESCRIPTION, 1, 2000), CHR(13), ''), CHR(10), ''), CHR(9), ''), CHR(11), ''), CHR(12), ''), 1, 100) DESCRIPTION,
      NVL(xal.entered_dr, 0) - NVL(xal.entered_cr, 0) amount,
      CTL.*
    FROM GL.GL_JE_HEADERS GJH,
      GL.GL_JE_LINES GJL,
      GL.GL_CODE_COMBINATIONS GCC,
      GL.GL_PERIODS GLP,
      GL.GL_IMPORT_REFERENCES IMP,
      XLA.XLA_AE_LINES XAL,
      XLA.XLA_AE_HEADERS XAH,
      XLA.XLA_EVENTS XE,
      XLA.XLA_TRANSACTION_ENTITIES XTE,
      RA_CUSTOMER_TRX_ALL RCT,
      HZ_PARTIES PARTY,
      AR.HZ_CUST_ACCOUNTS CA,
      GL_CODE_COMBINATIONS_KFV CC,
      AR.RA_CUSTOMER_TRX_LINES_ALL CTL,
      AR.RA_CUST_TRX_LINE_GL_DIST_ALL CTLD
    WHERE 1              = 1
    AND GJH.JE_HEADER_ID = GJL.JE_HEADER_ID
      --      AND GJL.STATUS || '' = 'P'
    AND GCC.CODE_COMBINATION_ID   = CTLD.CODE_COMBINATION_ID
    AND GJH.PERIOD_NAME           = GLP.PERIOD_NAME
    AND RCT.CUSTOMER_TRX_ID       = CTLD.CUSTOMER_TRX_ID
    AND CTLD.CUSTOMER_TRX_LINE_ID = CTL.CUSTOMER_TRX_LINE_ID
    AND ctld.customer_trx_id      = RCT.CUSTOMER_TRX_ID
      --       AND GLP.ADJUSTMENT_PERIOD_FLAG <> 'Y'
    AND GJH.JE_SOURCE           = 'Receivables'
    AND GJL.JE_HEADER_ID        = IMP.JE_HEADER_ID
    AND GJL.JE_LINE_NUM         = IMP.JE_LINE_NUM
    AND IMP.GL_SL_LINK_ID       = XAL.GL_SL_LINK_ID
    AND IMP.GL_SL_LINK_TABLE    = XAL.GL_SL_LINK_TABLE
    AND XAL.APPLICATION_ID      = XAH.APPLICATION_ID
    AND XAL.AE_HEADER_ID        = XAH.AE_HEADER_ID
    AND XAH.APPLICATION_ID      = XE.APPLICATION_ID
    AND XAH.EVENT_ID            = XE.EVENT_ID
    AND XE.APPLICATION_ID       = XTE.APPLICATION_ID
    AND XTE.APPLICATION_ID      = 222
    AND XE.ENTITY_ID            = XTE.ENTITY_ID
    AND XTE.ENTITY_CODE         = 'TRANSACTIONS'
    AND XTE.SOURCE_ID_INT_1     = RCT.CUSTOMER_TRX_ID
    AND RCT.BILL_TO_CUSTOMER_ID = CA.CUST_ACCOUNT_ID
    AND CA.PARTY_ID             = PARTY.PARTY_ID
    AND rcT.CUSTOMER_TRX_ID     = ctl.CUSTOMER_TRX_Id
    AND CTL.LINE_TYPE           = 'LINE'
    AND XAL.CODE_COMBINATION_ID = CC.CODE_COMBINATION_ID
    AND RCT.CUSTOMER_TRX_ID                              = 8857929
    AND GJL.JE_LINE_NUM                                  = 8866
    Any ideas?
    Thanks in advance,
    Stoyanov.

    Hi Stoyanov,
    Please try using the table xla_distribution_links to join with ra_cust_trx_line_gl_dist_all by using
    xla_distribution_links.source_distribution_id_num_1 = ra_cust_trx_line_gl_dist_all.cust_trx_line_gl_dist_id
    The below link gives the join conditions for various sub ledger types :
    Techincal: R12 SLA Tables connection to AP, AR, INV,Payments, Receiving
    Hope this helps.
    Regards,
    Manjusha.

  • Issue in query panel LOV order by

    Hi All,
    I am using Jdev 11.1.1.6 version and Weblogic 10.3.6 version. I am facing an issue which is explained below. I have a screen with query panel and results table.
    For Ex. Say i have Name in the results table and search paramater as well. Created Name with the help of a view object with search parameter as view criteria with Order by Name. Name search paramater is created as SelectOneChoice(LOV) . Also from my first page Add button can be clicked. On clicking the button new Name value can be added. On successfully saving the New value it is getting refreshed in the table results and displaying in the correct order. But in LOV the latest value is getting added at the Last. Rest of the values are Ordered by Name.
    Is it possible to display the values in the correct order in LOV after new values are getting added?
    I have tried the following.
         1. Refreshing the View Object with Search Criteria.
         2. Refreshing the LOV View Object.
         3. Refreshing the Whole Page.
    4. Order by in View Accessor.
    5. Refreshing the View Accessor.
    Note: When i totally reload the page again then it is getting refelected correctly.
    Thanks.
    Regards,
    Deena.

    Maybe you can try to reset QueryModel, something like this:
    QueryModel queryModel = queryComponent.getModel(); 
    QueryDescriptor queryDescriptor = queryComponent.getValue(); 
    queryModel.reset(queryDescriptor); 
    queryComponent.refresh(FacesContext.getCurrentInstance());
    AdfFacesContext.getCurrentInstance().addPartialTarget(queryComponent);Sorry, I don't have any more ideas :(
    Dario

Maybe you are looking for