Difference between After parameter Form Trigger and before Report Trigger

hi,
Can some one tell me difference between After parameter form Trigger and Before parameter trigger.
Why do we need both these trigger , why can't we use any one of them because after parameter trigger will obviously fire before report trigger and similarly before report trigger will fire after parameter form.
Thanks
Ram

Hi,
i will make it clear..!
Actually, we have four type of triggers in reports..!
Before Parameter -- fires before params are suppied to the calling report..
After Parameter -- fires after params are suppied to the calling report..
Before Report -- fires before report is generated..
After Report. -- fires after report is generated..
Before Report and After Report triggers are used for formatting the report design..
like u can specify a report to be displayed based on a condition in the Before
Report trigger and u can specify some backend updations in the after report trigger
which fires after report is generated..

Similar Messages

  • Difference between AFTER PARAMETER FORM and BEFORE REPORT in Reports 6i

    Hi Aii,
    What is the difference between AFTER PARAMETER FORM and BEFORE REPORT in Reports 6i.
    Thanks in Advance,
    Balu

    Hi Balu.,
    As per my findings the After Parameter is fired after the Parameters are given to the report and Before Report fires when the queries are parsed and data is fetched.
    Regards.,
    Vijay G

  • Difference between After parameter Trigger and befor report Trigger

    hi,
    Can anyone tell me Functional difference between After parameter Trigger and Before Report Trigger. with some practical example or scenario.
    I did try few things but I couldn't make out any difference.
    thanks
    ram

    Probably none at this point.
    We pass parameters from a form (and do not use the report param selection screen), but always run code in the afterpform.
    put your parameter form code processing in the afterpform. I rarely ever use before report.
    The order is as expected:
    before pform
    param form
    after pform
    before report
    report
    --between pages during report run
    after report

  • Calling report from form and after parameter form trigger

    Hi, I've also posted to this to the reports forum but because it works from Reports Builder it may be a forms issue which is why I'm x-posting. Apologies.
    I have a report that creates a file, desname is set in the after parameter form trigger (it uses one of the parameter values).
    The problem is file is not created using the path and filename set in the trigger, the file is created in the bin folder with the name account_by_service_type.txt (account_by_service_type.rdf is the report definition).
    If the desname is set in the before parameter form AND a field with the source=desname is added to the parameter form then the file will be created with the correct path and name however it won't have the relevant parameter incorporated into the file name obviously.
    I've noticed in other reports that where the desname is being set in the after parameter form that I've had to pass the desname from the form but obviously I cannot do that here either.
    Am I missing something obvious?
    Regards
    Sean

    Hi Frank,
    It's WebForms. Below is the code:
    -- call from menu item
    run_report_object_proc(TRUE,'accounts_by_service_type.RDF',null,FILE,'delimited','paramform=yes');
    -- run_report_0bject procedure
    PROCEDURE run_report_object_proc (p_screen IN BOOLEAN,
                        p_report_filename IN VARCHAR2,
                        p_desname IN VARCHAR2,
                        p_destype IN NUMBER,
                        p_desformat IN VARCHAR2,
                        p_paramform IN VARCHAR2)IS
    v_report_id     report_object;
    v_report     varchar2(100);
    v_job_id     varchar2(100);
    v_url          varchar2(1000);
    rep_status     varchar2(20);
    hidden_action     VARCHAR2(2000)     :='';
    BEGIN
    v_report_id := find_report_object( 'report2');
    SET_REPORT_OBJECT_PROPERTY(v_report_id,REPORT_FILENAME,p_report_filename);
    SET_REPORT_OBJECT_PROPERTY(v_report_id,REPORT_DESNAME,p_desname);
    SET_REPORT_OBJECT_PROPERTY(v_report_id,REPORT_DESTYPE,p_destype);
    SET_REPORT_OBJECT_PROPERTY(v_report_id,REPORT_DESFORMAT,p_desformat);
    hidden_action := hidden_action||'&report='||GET_REPORT_OBJECT_PROPERTY(v_report_id, REPORT_FILENAME);
    hidden_action := hidden_action||'&destype='||GET_REPORT_OBJECT_PROPERTY(v_report_id, REPORT_DESTYPE);
    hidden_action := hidden_action||'&desformat='||GET_REPORT_OBJECT_PROPERTY(v_report_id, REPORT_DESFORMAT);
    hidden_action := hidden_action||'&userid='||GET_APPLICATION_PROPERTY(username)||'/'||GET_APPLICATION_PROPERTY(password)||'@'||GET_APPLICATION_PROPERTY(connect_string);
    if p_desname is not null then
    hidden_action := hidden_action||'&'||p_paramform||'&desname='||p_desname;
    else
    hidden_action := hidden_action||'&'||p_paramform;
    end if;
    hidden_action := '/reports/rwservlet?_hidden_server=rserv1'||hidden_action;
    SET_REPORT_OBJECT_PROPERTY(v_report_id, REPORT_OTHER, 'pfaction='||hidden_action||' '||p_paramform);
    -- SET_REPORT_OBJECT_PROPERTY(v_report_id, REPORT_OTHER, 'paramform=no');
    v_report := run_report_object( v_report_id);
    IF p_screen THEN
         v_job_id := substr(v_report,instr(v_report,'_',-1)+1);
    rep_status:=report_object_status(v_report);
    while rep_status in ('RUNNING', 'OPENING_REPORT', 'ENQUEUED')
    loop
         rep_status:=report_object_status(v_report);
    end loop;
    if rep_status='FINISHED' THEN
         v_url := '/reports/rwservlet/getjobid'||v_job_id||'?server=rserv1';
              web.show_document(v_url,'_blank');
    else
         message(rep_status||' error running report');
    end if;     
    end if;
    END;
    -- report after parameter form trigger
    function AfterPForm return boolean is
    begin
    :desname := 'c:\service_type_'||:p_service_type||'_'||to_char(sysdate,'DDMMYYYY')||'.xls';
    return (TRUE);
    end;

  • Report Builder 6i returns ORA-01483 in after parameter form trigger ?

    Can anybody help me ?
    I've been working on a report with report builder 6.0.8.11.3,
    and whenever i run the report the after parameter form trigger
    returns REP-1401 and following ORA-01483.
    I've been trying to change the values of some user parameters
    from within the trigger code, none of them is a date or a number
    parameter, these are character variables who would be referenced
    lexically to change a table name dynamically when the trigger
    fires. Aditionally I'm using a cursor to obtain data and then
    modify the parameters.
    How can i get this thing to work ?
    Thanks in advance for your reply...

    hello,
    this might be related to the usage of number(1) as type/length
    of your parameter. this is a known problem. it should be solved
    by using e.g. number(2) as the type/length of your parameter.
    regards,
    the oracle reports team --pw                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

  • Difference between F.35 Receivables amount and FBL5N report open items

    Hi All,
    There is an amount difference between f.35 receivables amount and fbl5n open items amount, I have observed that there are some changes to credit master like risk category and credit representative group, so I thought if we run f.28 it will be right but still difference exits.
    If anybody has come across similar issue or if you have any idea on this on how to analyze, please let me know.
    Regards,
    RK.

    Hi ,
    Please check the time horizon in credit check used. then compare it with FBL5n.
    May be there will be difference in comparison period.
    Program RFDKLI20 or F.28 is to run when there is changes in Assignment from company code, entry in customer master data, entry in sales area data, user exit., currency of credit control area , Assignment of customers to credit accounts.
    And
    Program RVKRED09.--> only the risk class was changed it is sufficient to run
    Regards
    Atul

  • After Parameter Form trigger failed

    REP-0771. I have the trigger returning to false on a condition, however, this is when I get the error. All I want to do is return to the parameter form, and it's giving me an error. Is there any way to suppress this error?

    Hi Maggie
    To validate a parameter value at runtime:
    1. In the Object Navigator, expand the Data Model node, then the System Parameters or User Parameters node.
    2. Double-click the PL/SQL icon for the parameter for which you want to add a PL/SQL validation trigger.
    3. In the PL/SQL Editor, define the PL/SQL to be triggered at runtime
    Validation triggers are used to validate the Initial Value property of the parameter. Depending on whether the function returns TRUE or FALSE, the user is returned to the Runtime Parameter Form.
    Thanks
    Rohit

  • Parameter not being set in before parameter form trigger

    I am running 10g reports over the web and have a problem with some parameters. I have a User parameter which I set in the BEFORE-PARAMETER-FORM trigger. This parameter is not displayed on the parameter form because it shouldn't ever be changed by a user. It is supposed to be displayed on the report output to show who ran the report, but it is appearing blank.
    I've found that if I physically display the parameter on the parameter form it works, but this isn't a realistic option. It looks like it gets cleared out if it isnt displayed on the parameter form. Can anyone explain why and offer any help?

    Assign value to the parameter in the After Parameter Form Trigger, not Before.

  • After Parameter Form issue - Oracle Reports 10g

    Hi All,
    I have compiled an .rdf report to an .rep file and when
    I run this file I get the "REP-1247: Report contains uncompiled PL/SQL" message.
    The issue is I have built the report with dynamic XML customizations in the after parameter form trigger. When I remove this piece of code from the trigger both files .rdf and .rep works fine.
    Notice that the .rdf file works fine with the after parameter form XML customization.
    Please, can enyone advice me how can I have a .rep file that contains dynamic XML customization (using the srw.add_definition).
    Thank you in advance.

    In Your code there is a line:
    add_parameter(pl_id,'PARAMFORM',text_PARAMETER,'NO');
    which actually disables the report parameter form.
    The line:
    WEB.SHOW_DOCUMENT ('/reports/rwservlet/getjobid'|| vjob_id||
    '?server=rep_mohahubkpcomp_ORaHOme_IAS'||'&userid=
    bedman/bedman@bedman'||'&paramform=yes','_blank');
    displays the report to which vjob_id refers. At this point the report is competed so the parameters userid and paramform are useless.
    Hope this helps.
    Regards
    Bekcic Aleksandar

  • Differences between Hyperion Workspace, Web Analysis and Financial Reportin

    Hello,
    Can anybody explain me the differences between Hyperion Workspace, Web Analysis and Financial Reporting?
    Thank you

    In real simple terms....
    Financial reporting - Perfect for producing standardised monthly reporting such as P&L, balance sheets etc. Highly formatted, print well in PDF format.
    Web Analysis - Highly graphical, web based analysis tool more suited to dashboards, pinboards etc with slice and dice capability.
    Workspace - Common environment where reporting content in deployed. Users can access web anlysis, fin reports, Interactive reports plus other content through the workspace. It was the start of the 'log on to one place for all reporting' concept instead og logging on to multiple products.
    Hope that helps
    Regards
    CD

  • Problem in Insertion into table through After Report Parameter form trigger

    Hi All,
    I am getting problem in inserting some data into temp table through Report.
    My requirement is like that, I have to do a calculation based on user parameters, and then insert the data into the temp table. I wanted to do this into After Report Parameter form trigger function. I have done all the calculation and wrote all the insert statement in that function. There is no problem in compilation. then I am taking value from this temp table in my formula columns.
    When I run this report, it hangs, don't understand what is the problem.Can anybody help me out in this.
    Thanks,
    Nidhi

    The code is as follows:
    function AfterPForm return boolean is
    CURSOR CUR_RECEIPT(RECEIPT_NUM_FROM NUMBER, RECEIPT_NUM_TO NUMBER) IS
    SELECT DISTINCT receipt, item_no FROM xxeeg.xxeeg_1229_sp_putaway WHERE RECEIPT BETWEEN
    RECEIPT_NUM_FROM AND RECEIPT_NUM_TO ;
    V_CUR_RECEIPT CUR_RECEIPT%ROWTYPE;
    begin
    OPEN CUR_RECEIPT(:RECEIPT_NUM_FROM, :RECEIPT_NUM_TO);
    FETCH CUR_RECEIPT
    INTO V_CUR_RECEIPT;
    LOOP
    EXIT WHEN CUR_RECEIPT%NOTFOUND;
    IF V_CUR_RECEIPT.ITEM_NO = 'TEST1' AND V_CUR_RECEIPT.RECEIPT = '12' THEN
    INSERT INTO SP_TEMP
    (RECEIPT, ITEM_NO, LOCATION1)
    VALUES
    (V_CUR_RECEIPT.RECEIPT, V_CUR_RECEIPT.ITEM_NO, 10);
    UPDATE SP_TEMP
    SET LOCATION2 = 12
    WHERE RECEIPT = V_CUR_RECEIPT.RECEIPT AND ITEM_NO = V_CUR_RECEIPT.ITEM_NO;
    UPDATE SP_TEMP
    SET LOCATION3 = 13
    WHERE RECEIPT = V_CUR_RECEIPT.RECEIPT AND ITEM_NO = V_CUR_RECEIPT.ITEM_NO;
    UPDATE SP_TEMP
    SET LOCATION4 = 14
    WHERE RECEIPT = V_CUR_RECEIPT.RECEIPT AND ITEM_NO = V_CUR_RECEIPT.ITEM_NO;
    ELSE
    IF V_CUR_RECEIPT.ITEM_NO = 'TEST2' AND V_CUR_RECEIPT.RECEIPT = '12' THEN
    INSERT INTO SP_TEMP
    (RECEIPT, ITEM_NO, LOCATION1)
    VALUES
    (V_CUR_RECEIPT.RECEIPT, V_CUR_RECEIPT.ITEM_NO, 10);
    UPDATE SP_TEMP
    SET LOCATION2 = 16
    WHERE RECEIPT = V_CUR_RECEIPT.RECEIPT AND ITEM_NO = V_CUR_RECEIPT.ITEM_NO;
    UPDATE SP_TEMP
    SET LOCATION3 = 17
    WHERE RECEIPT = V_CUR_RECEIPT.RECEIPT AND ITEM_NO =V_CUR_RECEIPT.ITEM_NO;
    UPDATE SP_TEMP
    SET LOCATION4 = 18
    WHERE RECEIPT = V_CUR_RECEIPT.RECEIPT AND ITEM_NO = V_CUR_RECEIPT.ITEM_NO;
    ELSE
    INSERT INTO SP_TEMP
    (RECEIPT, ITEM_NO, LOCATION1)
    VALUES
    (V_CUR_RECEIPT.RECEIPT, V_CUR_RECEIPT.ITEM_NO, 10);
    UPDATE SP_TEMP
    SET LOCATION2 = 19
    WHERE RECEIPT = V_CUR_RECEIPT.RECEIPT AND ITEM_NO = V_CUR_RECEIPT.ITEM_NO;
    UPDATE SP_TEMP
    SET LOCATION3 = 20
    WHERE RECEIPT = V_CUR_RECEIPT.RECEIPT AND ITEM_NO =V_CUR_RECEIPT.ITEM_NO;
    UPDATE SP_TEMP
    SET LOCATION4 = 21
    WHERE RECEIPT = V_CUR_RECEIPT.RECEIPT AND ITEM_NO = V_CUR_RECEIPT.ITEM_NO;
    END IF;
    END IF;
    END LOOP;
    COMMIT;
    CLOSE CUR_RECEIPT;
    return(TRUE);
    end;
    .....................................................................................................................

  • Want to Create View as per Condition Fires After Parameter Form.

    Hi ..
    I want to create a report from a view,and that view would create after parameter form of that
    report.
    Example..
    I want to select max(sal) of each Dept.where employee hired between 1-jan-2007 and 31-jul-2007'
    I want when i Passes dates in Parameter FOrm
    a view i.e select empno,deptno,sal, from emp created.
    that means that view contains only data about that certain period
    SO in Report Query i can write
    select deptno,max(sal) from vw_employee
    group by deptno.
    This is just an example....my real problem is very hard and only can be done by doing create a view as per given dates in Report Parameter Form.
    Waiting for Reply
    Regards
    Danish Hayder

    Wrong ideea.
    You should have the parameters in the report's query:
    select empno,deptno,sal, from emp where hired between :p_start_date and :p_end_date
    Why do you want to create a view in the report, seeing that it's best to use parameters.
    Moreover, think that the oracle user running the report would have to have the priviledges to create views, which may not be good security policy.
    Still, if you insist on creating the view when running the report, then you'd better create the view from a stored procedure, that would receive as parameter the SQL select for creating the view.
    So, you'd have the stored procedure:
    proc_view(p_select in varchar2, p_view_name in varchar2) is
    begin
    execute immediate 'create or replace view '||p)view_name||' as '||p_select;
    end;
    You then would compose the select in the afterpform trigger and call the proc_view procedure.
    Note that I did not allow proc_view to execute immediate any SQL one would pass, for that would be really dangerous. What if one would pass to the procedure executing dynamic SQL the following: 'drop table my_table cascade constraints'?

  • Calling a report from another report in after parameter form

    hi,
    I'm calling Emp.rdf report with deptno as parameter and if the parameter is '10' then i have to call dept.rdf
    function AfterPForm return boolean is
    begin
    if :p_deptno =10 then
         srw.run_report('report=c:\reports\dept.rdf destype=screen p_deptno='||:p_deptno);
         end if;
    return (TRUE);
    end;
    But, now i'm getting an error as
    REP-1428: afterpform': Error while running SRW.RUN_REPORT
    Could you please help on this. thanks Bcj

    Hi , I have tried destype=file , didn't work for me. same time i tried with background=yes , that time report crashed.
    Actualy what i'm trying to do is,
    whenever the main report received an incorrect user input , i have to run a different report based on that particular input value and to show the users the actual input values.
    so the coding would be like this in the after parameter form,
    BEGIN
    IF :P_ID between 1000 and 5000 then
    --here i'm only changing the paramter value ,
    ELSE
    --here i'm calling the new report
    srw.run_report('report=c:\reports\emp.rdf batch=yes destype=file desname c:\reports\id.txt background=yes p_new_id='|| :p_id);
    return(true);
    END;
    Any help....

  • Difference between General Ledger Accounting (New) and Old

    Hello All,
    Please help me with the below:
    1)Could any one please explain the difference between General Ledger Accounting (New) and General Ledger Accounting (Old).
    After going through the help document I understood that the BI 7 version came up with General Ledger Accounting (New), If this is true then can we still use 0FI_GL_04 in Ecc and BI7.0?
    2)what is the difference between 0FI_GL_04 and 0FI_GL_14?
    3) Is there any material or link or pdf that explains more clearly about FI - GL implementation in BI.
    Thanks in advance.Your help will be much appreciated.

    Hi Kiran,
    Pl check SDN before Posting
    Diff. Between old and New GL :
    Using new oEhP3 FI or old FI datasources
    Extraction and Reporting of FI-CA: Open Items Data In SAP-BI:
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a9996115-0b01-0010-b2b2-d9de0170a425?QuickLink=index&overridelayout=true
    Financial Accounting: Procedure for Delta Extraction of Transaction Figures:
    http://help.sap.com/saphelp_sm32/helpdata/en/41/4b73415fb9157de10000000a155106/content.htm
    Complete FI-GL Information :
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/FigL/FigL.pdf
    Regards
    Ram
    Edited by: Ramakanth Deepak Gandepalli on Jan 29, 2010 5:14 AM

  • Differences between operational systems data modeling and data warehouse da

    Hello Everyone,
    Can anybody help me understand the differences between operational systems data modeling and data warehouse data modeling>
    Thanks

    Hello A S!
    What you mean is the difference between modelling after normal form like in operational systems (OLTP) e. g. 3NF and modelling a InfoCube in a data warehouse (OLAP)?
    While in a OLTP you want to have data tables free of redundance and ready for transactions meaning writing and reading few records often, in an OLAP-system you need to read a lot of data for every query you do on a database. Often in an OLAP-system you aggregate these amounts of data.
    Therefore you use another principle for these database scheme. This is called star schema. This means that you have one central table (called fact table) which holds the key figures and have keys to another tables with characteristics. These other tables are called dimension tables. They hold combinations of the characteristics. Normally you design it that your dimensions are small, so the access  on the data is more efficent.
    the star scheme in SAP BI is a little more complex than explained here but it follows the same concept.
    Best regards,
    Peter

Maybe you are looking for