Question { IBM, 11258 }

Can anybody tell me, What is the Implementation Process?

Answer

Implementations process as follows:
1.Definitions phase
in this phase the project team plan the implementations
project and the project team oraganised.kick of meeting
between superuser,key user and Imp team.it is just
introductions phase.
2.Operations and Analysis Phase
AS IS STUDY AND TO BE STUDY DO DONE and GAP is defined
BP40,BP80,RD10,RD20,RD50 AIM's Docs prepare.
3.Solutions design.
High Gap level find out and full fill the GAP to done
Workround and Customaizations.Business Requirements Map to
Applications.
BR10,BR30,MD50,MD70 to be prepared.
4.Build Phase
Develop the development instance and Test instance
such as BR100,TE20,TE50 to be prepared
5.Transitions
Testing done in test Instance
CRP will done.
UAT will done.
6.productions.
sucessfull done in UAT,it goes to LIVE
Find data migrations.
support to Post Productions for particular period.(as per
customer discussion)

Question { eicc, 30146 }

What are Lexical Parameters.How They are used in Reports 6i

Answer

1.Lexical Parameters are placeholders for text that you
embed in a SELECT statement. You can use lexical
references to replace the clauses appearing after SELECT,
FROM, WHERE, GROUP BY, ORDER BY, HAVING, CONNECT BY, and
START WITH.

You cannot make lexical references in a PL/SQL statement.
You can, however, use a bind reference in PL/SQL to set the
value of a parameter that is then referenced lexically in
SQL.

example:
we can use (&)lexical parameter in where cluse and inside
from clause and group by clause i enclose the query used in
reports 6i.

select
decode (UPPER(:p_order_by),'CUSTOMER',NULL,
types.cust_trx_type_id ) dummy_id_inv,
decode (UPPER
(:p_order_by),'CUSTOMER',NULL,types.name)
dummy_type_inv,


ps.trx_number
invnum ,

types.name
invoice_type_inv,

ps.amount_adjusted
amount_adjusted_inv,

ps.amount_applied
amount_applied_inv,

ps.amount_credited
amount_credited_inv,

ps.gl_date
gl_date_inv,

&lp_bal_segment
bal_segment_value_inv,
&lp_query_show_bill cons_billing_number,
from ra_cust_trx_types_all types,
hz_cust_accounts cust_acct,
hz_parties party,
&lp_ar_payment_schedules_all ps,
&lp_table_show_bill
&lp_ra_customer_trx_all trx,
hz_cust_site_uses_all site,
hz_cust_acct_sites_all addr,
hz_party_sites party_site,
hz_locations loc,
&lp_ra_cust_trx_gl_dist_all gld,

where TRUNC(ps.gl_date) <= :p_as_of_date
and ps.customer_trx_id+0 = trx.customer_trx_id
and ps.customer_id = cust_acct.cust_account_id
and cust_acct.party_id = party.party_id
&lp_customer_name_low1
&lp_customer_name_high1
&lp_customer_number_low1
&lp_customer_number_high1
and ps.cust_trx_type_id = types.cust_trx_type_id
and nvl(ps.org_id,-99) = nvl(types.org_id,-99)
&lp_invoice_type_low
&lp_invoice_type_high
and ps.customer_site_use_id+0 = site.site_use_id+)
and site.cust_acct_site_id = addr.cust_acct_site_id(+)
and addr.party_site_id = party_site.party_site_id(+)
and loc.location_id (+) = party_site.location_id
and ps.gl_date_closed > :P_AS_OF_DATE
&lp_curr_code
and ps.customer_trx_id+0 = gld.customer_trx_id
and gld.account_class = 'REC'
and gld.latest_rec_flag = 'Y'
and gld.code_combination_id = cc.code_combination_id
&lp_bal_segment_low
&lp_bal_segment_high
&lp_where_show_bill
&P_ORG_WHERE_CTT
&P_ORG_WHERE_PS
&P_ORG_WHERE_ADDR
&P_ORG_WHERE_GLD