Restrict responsibility with one value set

Hi,
We have created a responsibility and we want that to have only one value set. When we add "Flexfield Value" menu to the responsibility it shows the query screen where users can access any value set.
Other than custom.pll or forms personalization, is there any other simple way?
Thanks.

No, There is no simpler way to have only one value set.

Similar Messages

Fnd_request.submit_request issue with PA_SRS_DATES2 value set.

Hi,
We are applications 12.0.6 with 10.2.0.3.0 database. I'm trying to submit the "PRC: Generate Draft Revenue for a Single Project" through fnd_request.submit_request and is erroring out with "PA: Error - Entered Accrue through date is not within open/future PA period". I'm able to run the same program from the application with the same parameters. I'm passing Accue date of 2009/08/31 00:00:00 from the program and I can see the same value when submitted frm the applications also.
Value set for this Accrue date parameter is "PA_SRS_DATES2". It is setup as format type "Standard Date" and maximum size is 11.
Thanks for your help,
Shree.
Here is the script
SELECT TO_CHAR (rec1.per_end_date, 'RRRR/MM/DD HH24:MI:SS')
INTO v_rev_accrue
FROM DUAL;
fnd_file.put_line (fnd_file.LOG,
'Revenue Accrue Date is :' || v_rev_accrue
fnd_file.put_line (fnd_file.LOG, 'Parameters for GDR :');
fnd_file.put_line (fnd_file.LOG,
'Argument1 is :' || TO_CHAR (rec1.project_id)
fnd_file.put_line (fnd_file.LOG, 'Argument4 is :' || v_rev_accrue);
v_fc_req_id :=
fnd_request.submit_request (application => 'PA',
program => 'PARGDR_SINGLE',
sub_request => FALSE,
start_time => NULL,
argument1 => rec1.project_id,
argument2 => 'N',
argument3 => 'Y',
argument4 => v_rev_accrue,
argument5 => NULL,
argument6 => NULL,
argument7 => NULL,
argument8 => NULL,
argument9 => NULL,
argument10 => NULL,
argument11 => 'Y',
argument12 => 'N',
argument13 => NULL,
argument14 => NULL,
argument15 => NULL,
argument16 => NULL,
argument17 => NULL,
argument18 => 'N',
argument19 => 'N',
argument20 => 'N'
IF NVL (v_fc_req_id, 0) = 0
THEN
gv_debug_name :=
'Error in Submitting the draft revenue program program. ';
fnd_file.put_line (fnd_file.LOG, gv_debug_name);
RAISE general_error;
ELSE
COMMIT;
fnd_file.put_line (fnd_file.LOG,
'draft revenue program. Request Id:'
|| TO_CHAR (v_fc_req_id)
END IF;
Here is the log for the request submitted via fnd_request.submit_request.
Projects: Version : 12.0.0
Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
PARGDR_SINGLE module: PRC: Generate Draft Revenue for a Single Project
Current system time is 13-AUG-2009 18:59:19
Entering parmai()
...Connected to Oracle
Accrue Thru date from Command line is : 2009/08/31 00:00:00
Start of log messages from FND_FILE
End of log messages from FND_FILE
Executing request completion options...
Finished executing request completion options.
PA: Error - Entered Accrue through date is not within open/future PA period
Exceptions posted by this request:
Concurrent Request for "PRC: Generate Draft Revenue for a Single Project" has completed with error.
Concurrent request completed
Current system time is 13-AUG-2009 18:59:20
Here is the log for the request submitted via the application
Projects: Version : 12.0.0
Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
PARGDR_SINGLE module: PRC: Generate Draft Revenue for a Single Project
Current system time is 10-AUG-2009 17:12:11
Entering parmai()
...Connected to Oracle
Accrue Thru date from Command line is : 2009/08/31 00:00:00
project:196 delete:N regenerate:Y acc_thru_dt:2009/08/31
start project: end project:
Operating unit is 153Revenue is running in Normal revenue mode
Revenue is not based on specific project type...
Revenue is not based on specific organization...
Revenue is not based on specific customer...
Revenue is not based on specific Agreement...
Revenue is running for MCB/Non MCB projects...
Revenue is running for Unrelease revenue mode...
Revenue is not creating the detail report ...
Revenue Processing Parameter List
=================================
-------------- < parameter list > -----------------------
Accru Through Date ----------------------------------------> 2009/08/31
Project ID ------------------------------------------------> 196
From Project Number --------------------------------------->
To Project Number ----------------------------------------->
Adjusting Revenue Run -------------------------------------> No
Project Type ID -----------------------------------------> 0
Organization ID ------------------------------------------> 0
Customer ID ----------------------------------------------> 0
Agreement ID ----------------------------------------------> 0
Multi Currency Projects -----------------------------------> No
Release Draft Revenue -------------------------------------> No
Include Detail Report -------------------------------------> No
-------------- < End of parameter list > -----------------------
...Request ID = 714111
This concurrent request is not being rescheduled
Current system time is 10-AUG-2009 17:12:11
...about to delete revenue for project id 196
...0 draft revenues deleted
Current system time is 10-AUG-2009 17:12:11
...about to process adjustments
SELECT p.project_id, p.segment1,
p.distribution_rule, p.project_level_funding_flag,p.project_currency_code,
p.project_bil_rate_date_code,
p.project_bil_rate_type,
to_char(p.project_bil_rate_date,'YYYY/MM/DD'),
p.project_bil_exchange_rate,
p.projfunc_currency_code,
p.projfunc_bil_rate_date_code,
p.projfunc_bil_rate_type,
to_char(p.projfunc_bil_rate_date,'YYYY/MM/DD'),
p.projfunc_bil_exchange_rate,
p.revproc_currency_code,
p.funding_rate_date_code,
p.funding_rate_type,
to_char(p.funding_rate_date,'YYYY/MM/DD'),
p.funding_exchange_rate,
p.multi_currency_billing_flag,
p.assign_precedes_task,
p.enable_top_task_customer_flag,
p.enable_top_task_inv_mth_flag,
nvl(p.inv_by_bill_trans_curr_flag, 'N'),
nvl(p.revtrans_currency_type, 'PROJ_FUNC_CURR_ONLY')
FROM pa_projects p, pa_project_types t
WHERE p.project_id = :project_id
AND pa_project_utils.check_prj_stus_action_allowed(p.project_status_code,'GENERATE_REV') = 'Y'
AND :start_project_number||'x' != :end_project_number||'y'
AND p.project_type = t.project_type
AND t.project_type_class_code = 'CONTRACT'
AND EXISTS (SELECT /*+ INDEX(pf pa_summary_project_fundings_u1)*/ NULL
FROM pa_summary_project_fundings pf
WHERE pf.project_id = p.project_id
AND nvl(pf.revproc_baselined_amount, 0) != 0)
AND NOT EXISTS
(SELECT NULL
FROM pa_draft_revenues r2
WHERE r2.project_id = p.project_id
AND r2.released_date||'' is null
AND r2.generation_error_flag||'' = decode(:mass_gen,
1, 'Y', r2.generation_error_flag)
AND (EXISTS (SELECT NULL
FROM pa_expenditure_items_all i
WHERE i.project_id = p.project_id
AND i.cost_distributed_flag ||''= 'Y'
AND i.revenue_distributed_flag = 'N'
AND i.expenditure_item_date
<= NVL(TO_DATE(:acc_thru_dt,'YYYY/MM/DD'),sysdate)
AND (EXISTS (SELECT /*+ LEADING(l)*/ NULL
FROM pa_draft_revenues r, pa_cust_rev_dist_lines l
WHERE r.project_id = i.project_id
AND ((l.expenditure_item_id = i.adjusted_expenditure_item_id AND i.adjusted_expenditure_item_id is not null )
OR (l.expenditure_item_id = i.expenditure_item_id))
AND NVL(l.reversed_flag,'N') = 'N'
AND l.line_num_reversed IS NULL
AND r.project_id = l.project_id
AND r.draft_revenue_num = l.draft_revenue_num
AND (r.released_date||'' is not null
OR r.generation_error_flag||'' = decode(:mass_gen,
1, 'N', 'E')))
or exists (
select 1 from pa_expenditure_items ei2
where ei2.project_id = i.project_id
and ei2.expenditure_item_id=i.adjusted_expenditure_item_id
and ei2.revenue_distributed_flag='Y'
and ei2.raw_revenue=0))
union all
SELECT /*+ LEADING(v)*/NULL
FROM pa_events v
WHERE v.project_id = p.project_id
AND ((v.revenue_distributed_flag = 'N'
AND v.completion_date
<= NVL(TO_DATE(:acc_thru_dt,'YYYY/MM/DD'),sysdate))
OR (substr(p.distribution_rule,1,4) = 'COST'
AND v.revenue_distributed_flag = 'Y'
AND v.completion_date
> NVL(TO_DATE('2009/08/31','YYYY/MM/DD'), sysdate)))
AND (DECODE(NVL(v.bill_trans_rev_amount, 0), 0 ,
DECODE(NVL(v.zero_revenue_amount_flag, 'N'), 'Y', 1, 0),1) = 1)
AND NVL(revenue_hold_flag, 'N') = 'N'
AND EXISTS (
SELECT NULL
FROM pa_tasks t
WHERE v.task_id is not NULL
AND t.ready_to_distribute_flag = 'Y'
AND v.task_id = t.task_id
UNION ALL
SELECT NULL
FROM pa_tasks t1
WHERE v.task_id is NULL
AND t1.ready_to_distribute_flag = 'Y'
AND v.project_id = t1.project_id )
AND Exists (select null from pa_draft_revenues r,pa_cust_event_rev_dist_lines l
where l.project_id = v.project_id
AND ( l.task_id = v.task_id OR v.task_id is NULL )
AND l.event_num = v.event_num
AND NVL(l.reversed_flag,'N') = 'N'
AND l.line_num_reversed IS NULL
AND r.project_id = v.project_id
AND r.draft_revenue_num = l.draft_revenue_num
AND (r.released_date||'' is not null
OR r.generation_error_flag||'' = decode(:mass_gen,
1, 'N', 'E')))
union all
SELECT /*+ USE_CONCAT */ NULL
FROM PA_Billing_Extensions be, PA_Billing_Assignments bea
WHERE bea.active_flag = 'Y'
AND bea.billing_extension_id = be.billing_extension_id
AND (bea.project_id = p.project_id
OR bea.project_type = p.project_type
OR bea.distribution_rule = p.distribution_rule)
AND be.calling_process in ('Revenue','Both')
AND nvl(be.call_after_adj_flag, 'N') = 'Y'
AND be.trx_independent_flag = 'Y'))
Current system time is 10-AUG-2009 17:12:11
...0 projects processed for adjustments
Current system time is 10-AUG-2009 17:12:11
...about to generate revenue for project id 196
...Fetching next project
Current system time is 10-AUG-2009 17:12:11
...about to call pa_billing.bill_ext_driver( 196, 'Revenue', 'PRE', '2009/08/31', 714111 )
Current system time is 10-AUG-2009 17:12:11
...exiting pa_billing.bill_ext_driver( 196, 'Revenue', 'PRE', '2009/08/31', 714111 )
Current system time is 10-AUG-2009 17:12:11
Leaving pauoarchn()
...no rows to process for this project.
Current system time is 10-AUG-2009 17:12:11
...generated revenue for project id 196, number 72DM000001
...about to call pa_billing.bill_ext_driver( 196, 'Revenue', 'REG', '2009/08/31', 714111 )
Current system time is 10-AUG-2009 17:12:11
...exiting pa_billing.bill_ext_driver( 196, 'Revenue', 'REG', '2009/08/31', 714111 )
Current system time is 10-AUG-2009 17:12:11
Leaving pauoarchn()
Leaving pauoarchn()
Leaving pauoarchn()
Leaving pauoarchn()
Leaving pauoarchn()
Leaving pauoarchn()
Leaving pauoarchn()
Leaving pauoarchn()
Leaving pauoarchn()
Leaving pauoarchn()
Leaving pauoarchn()
Leaving pauoarchn()
Leaving pauoarchn()
Leaving pauoarchn()
Leaving pauoarchn()
Leaving pauoarchn()
Leaving pauoarchn()
Leaving pauoarchn()
Leaving pauoarchn()
l_inv_by_btc_flag is ...N
l_mcb_flag is ...Y
l_rpc_code is ...GBP
Leaving pauoarchn()
Leaving pauoarchn()
Leaving pauoarchn()
Leaving pauoarchn()
...Else loop 1
...else loop 2
...else loop 4
...else loop 5
...non_zero_amount
Leaving pauoarchn()
Leaving pauoarchn()
Leaving pauoarchn()
Leaving pauoarchn()
Leaving pauoarchn()
Leaving pauoarchn()
...Else loop 1
...else loop 2
...else loop 4
...else loop 5
...non_zero_amount
Leaving pauoarchn()
Leaving pauoarchn()
Leaving pauoarchn()
Current system time is 10-AUG-2009 17:12:11
...generated revenue for automatic events for project id 196, number 72DM000001 calling loc REG
...about to call pa_billing.bill_ext_driver( 196, 'Revenue', 'POST-REG', '2009/08/31', 714111 )
Current system time is 10-AUG-2009 17:12:11
...exiting pa_billing.bill_ext_driver( 196, 'Revenue', 'POST-REG', '2009/08/31', 714111 )
Current system time is 10-AUG-2009 17:12:11
Current system time is 10-AUG-2009 17:12:11
...generated revenue for automatic events for project id 196, number 72DM000001 calling loc POST-REG
...about to call pa_billing.bill_ext_driver( 196, 'Revenue', 'POST', '2009/08/31', 714111 )
Current system time is 10-AUG-2009 17:12:11
...exiting pa_billing.bill_ext_driver( 196, 'Revenue', 'POST', '2009/08/31', 714111 )
Current system time is 10-AUG-2009 17:12:11
...Fetching next project
Current system time is 10-AUG-2009 17:12:11
Current system time is 10-AUG-2009 17:12:11
...about to call AutoAccounting
Current system time is 10-AUG-2009 17:12:11
Current system time is 10-AUG-2009 17:12:11
Current system time is 10-AUG-2009 17:12:11
Current system time is 10-AUG-2009 17:12:11
Entering pafvsu
Allocating pafvcs structure
Allocating memory for structure, fdfkai
Allocating memory for structure, fdfkao
Allocating flex input and output structure
Assigning ptype
Calling pagtfn
Nullig out
Setting everything that does not need to be allocated
Allocating optional arrays
Checking a_line_id
Checking a_trans_ind
Checking a_param_lst
Checking a_extra_atr
Allocating required array
Allocating auto accounting elements
Describing kff and control processing options
Tune flex validation system options
Allocate main cache
Allocate additional memory for main cache
Allocate ksv if needed
Store pointer to text strings in last ksv element so we can free later
val [¿], segval [00000000]
val [00000000], segval [000000]
val [000000], segval [7210OCOA01]
val [7210OCOA01], segval [0000]
val [0000], segval [72OXLFTG]
val [72OXLFTG], segval [66101010]
val [66101010], segval [7210]
Current system time is 10-AUG-2009 17:12:11
Current system time is 10-AUG-2009 17:12:11
Current system time is 10-AUG-2009 17:12:11
Current system time is 10-AUG-2009 17:12:11
Current system time is 10-AUG-2009 17:12:11
Current system time is 10-AUG-2009 17:12:11
Current system time is 10-AUG-2009 17:12:11
Current system time is 10-AUG-2009 17:12:11
...returned from AutoAccounting
...about to update pe_expenditures_all for intercompany processing
Current system time is 10-AUG-2009 17:12:11
Entering parddl()
...setting error codes and bad code combination id to null
... Update draft revenues for marking autoaccounting error if any
Current system time is 10-AUG-2009 17:12:11
0 rows updated.
... Update draft revenues without generation error to normal state
Current system time is 10-AUG-2009 17:12:11
1 rows updated.
... Update pa_cust_event_rev_dist_lines for setting bad CCID to null
Current system time is 10-AUG-2009 17:12:11
0 rows updated.
... Update pa_events for marking AutoAccounting error if any
Current system time is 10-AUG-2009 17:12:11
0 rows updated.
... Update pa_events for setting revenue_distributed_flag to 'N'
Current system time is 10-AUG-2009 17:12:11
0 rows updated.
... Update pa_cust_rev_dist_lines for setting bad CCID to null
Current system time is 10-AUG-2009 17:12:11
0 rows updated.
... Update pa_expenditure_items_all for marking AutoAccounting error if any
Current system time is 10-AUG-2009 17:12:11
0 rows updated.
... Update pa_expenditure_items_all for setting revenue_distributed_flag to 'N'
Current system time is 10-AUG-2009 17:12:11
0 rows updated.
Leaving parddl()
Current system time is 10-AUG-2009 17:12:11
Current system time is 10-AUG-2009 17:12:11
0 rows updated with Generation error due to ccid=-1
Current system time is 10-AUG-2009 17:12:11
0 rows updated with Generation error PA_REV_GEN_ERROR
Current system time is 10-AUG-2009 17:12:11
...1 projects processed for revenue generation
Deleting automatic event for which revenue has generation error
Current system time is 10-AUG-2009 17:12:11
...about to update proj summary funding amounts
executing pa_billing.check_spf_amounts('B',196, , ) Calling check_spf_amounts...Inside the Single projects If
Current system time is 10-AUG-2009 17:12:11
...about to generate reports
SEL-SUC:72DM000001 4 1048 AP Exploration Operating DML 101 31-AUG-09 121659.83
Current system time is 10-AUG-2009 17:12:12
...completed generating reports
Process completed.
0 rows deleted from distribution_warnings table.
Start of log messages from FND_FILE
Request id is :714111
Before calling the insert event for top task_id :19839
Parameters to the insert event API :
Revenue amount is :12106.73
Bill amount is :12106.73
Project id is :196
Event Type is :BILLING
Top Task id is :19839
organization id is :239
completion date is :31-AUG-2009
event description is :Financing Fee
Return status after calling insert event is :0
error message after calling insert event is :
Before calling the insert event for top task_id :14612
Parameters to the insert event API :
Revenue amount is :109553.1
Bill amount is :109553.1
Project id is :196
Event Type is :BILLING
Top Task id is :14612
organization id is :239
completion date is :31-AUG-2009
event description is :Expenditure
Return status after calling insert event is :0
error message after calling insert event is :
End of log messages from FND_FILE
Executing request completion options...
------------- 1) PRINT -------------
Printing output file.
Request ID : 714111
Number of copies : 0
Printer : noprint
Finished executing request completion options.
Concurrent request completed successfully
Current system time is 10-AUG-2009 17:12:12
---------------------------------------------------------------------------

Duplicate thread.
fnd_request.submit_request error with PA_SRS_DATES2 value set
fnd_request.submit_request error with PA_SRS_DATES2 value set

Fnd_request.submit_request error with PA_SRS_DATES2 value set

Hi,
We are applications 12.0.6 with 10.2.0.3.0 database. I'm trying to submit the "PRC: Generate Draft Revenue for a Single Project" through fnd_request.submit_request and is erroring out with "PA: Error - Entered Accrue through date is not within open/future PA period". I'm able to run the same program from the application with the same parameters. I'm passing Accue date of 2009/08/31 00:00:00 from the program and I can see the same value when submitted frm the applications also.
Value set for this Accrue date parameter is "PA_SRS_DATES2". It is setup as format type "Standard Date" and maximum size is 11.
Thanks for your help,
Shree.
Here is the script
SELECT TO_CHAR (rec1.per_end_date, 'RRRR/MM/DD HH24:MI:SS')
INTO v_rev_accrue
FROM DUAL;
v_fc_req_id :=
fnd_request.submit_request (application => 'PA',
program => 'PARGDR_SINGLE',
sub_request => FALSE,
start_time => NULL,
argument1 => rec1.project_id,
argument2 => 'N',
argument3 => 'Y',
argument4 => v_rev_accrue,
argument5 => NULL,
argument6 => NULL,
argument7 => NULL,
argument8 => NULL,
argument9 => NULL,
argument10 => NULL,
argument11 => 'Y',
argument12 => 'N',
argument13 => NULL,
argument14 => NULL,
argument15 => NULL,
argument16 => NULL,
argument17 => NULL,
argument18 => 'N',
argument19 => 'N',
argument20 => 'N'
IF NVL (v_fc_req_id, 0) = 0
THEN
gv_debug_name :=
'Error in Submitting the draft revenue program program. ';
fnd_file.put_line (fnd_file.LOG, gv_debug_name);
RAISE general_error;
ELSE
COMMIT;
fnd_file.put_line (fnd_file.LOG,
'draft revenue program. Request Id:'
|| TO_CHAR (v_fc_req_id)
END IF;
Here is the log for the request submitted via fnd_request.submit_request.
Projects: Version : 12.0.0
Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
PARGDR_SINGLE module: PRC: Generate Draft Revenue for a Single Project
Current system time is 13-AUG-2009 18:59:19
Entering parmai()
...Connected to Oracle
Accrue Thru date from Command line is : 2009/08/31 00:00:00
Start of log messages from FND_FILE
End of log messages from FND_FILE
Executing request completion options...
Finished executing request completion options.
PA: Error - Entered Accrue through date is not within open/future PA period
Exceptions posted by this request:
Concurrent Request for "PRC: Generate Draft Revenue for a Single Project" has completed with error.
Concurrent request completed
Current system time is 13-AUG-2009 18:59:20
Here is the log for the request submitted via the application
Projects: Version : 12.0.0
Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
PARGDR_SINGLE module: PRC: Generate Draft Revenue for a Single Project
Current system time is 10-AUG-2009 17:12:11
Entering parmai()
...Connected to Oracle
Accrue Thru date from Command line is : 2009/08/31 00:00:00
project:196 delete:N regenerate:Y acc_thru_dt:2009/08/31
start project: end project:
Operating unit is 153Revenue is running in Normal revenue mode
Revenue is not based on specific project type...
Revenue is not based on specific organization...
Revenue is not based on specific customer...
Revenue is not based on specific Agreement...
Revenue is running for MCB/Non MCB projects...
Revenue is running for Unrelease revenue mode...
Revenue is not creating the detail report ...
Revenue Processing Parameter List
=================================
-------------- < parameter list > -----------------------
Accru Through Date ----------------------------------------> 2009/08/31
Project ID ------------------------------------------------> 196
From Project Number --------------------------------------->
To Project Number ----------------------------------------->
Adjusting Revenue Run -------------------------------------> No
Project Type ID -----------------------------------------> 0
Organization ID ------------------------------------------> 0
Customer ID ----------------------------------------------> 0
Agreement ID ----------------------------------------------> 0
Multi Currency Projects -----------------------------------> No
Release Draft Revenue -------------------------------------> No
Include Detail Report -------------------------------------> No
-------------- < End of parameter list > -----------------------
...Request ID = 714111
This concurrent request is not being rescheduled
Current system time is 10-AUG-2009 17:12:11
...about to delete revenue for project id 196
...0 draft revenues deleted
Current system time is 10-AUG-2009 17:12:11
...about to process adjustments
SELECT p.project_id, p.segment1,
p.distribution_rule, p.project_level_funding_flag,p.project_currency_code,
p.project_bil_rate_date_code,
p.project_bil_rate_type,
to_char(p.project_bil_rate_date,'YYYY/MM/DD'),
p.project_bil_exchange_rate,
p.projfunc_currency_code,
p.projfunc_bil_rate_date_code,
p.projfunc_bil_rate_type,
to_char(p.projfunc_bil_rate_date,'YYYY/MM/DD'),
p.projfunc_bil_exchange_rate,
p.revproc_currency_code,
p.funding_rate_date_code,
p.funding_rate_type,
to_char(p.funding_rate_date,'YYYY/MM/DD'),
p.funding_exchange_rate,
p.multi_currency_billing_flag,
p.assign_precedes_task,
p.enable_top_task_customer_flag,
p.enable_top_task_inv_mth_flag,
nvl(p.inv_by_bill_trans_curr_flag, 'N'),
nvl(p.revtrans_currency_type, 'PROJ_FUNC_CURR_ONLY')
FROM pa_projects p, pa_project_types t
WHERE p.project_id = :project_id
AND pa_project_utils.check_prj_stus_action_allowed(p.project_status_code,'GENERATE_REV') = 'Y'
AND :start_project_number||'x' != :end_project_number||'y'
AND p.project_type = t.project_type
AND t.project_type_class_code = 'CONTRACT'
AND EXISTS (SELECT /*+ INDEX(pf pa_summary_project_fundings_u1)*/ NULL
FROM pa_summary_project_fundings pf
WHERE pf.project_id = p.project_id
AND nvl(pf.revproc_baselined_amount, 0) != 0)
AND NOT EXISTS
(SELECT NULL
FROM pa_draft_revenues r2
WHERE r2.project_id = p.project_id
AND r2.released_date||'' is null
AND r2.generation_error_flag||'' = decode(:mass_gen,
1, 'Y', r2.generation_error_flag)
AND (EXISTS (SELECT NULL
FROM pa_expenditure_items_all i
WHERE i.project_id = p.project_id
AND i.cost_distributed_flag ||''= 'Y'
AND i.revenue_distributed_flag = 'N'
AND i.expenditure_item_date
<= NVL(TO_DATE(:acc_thru_dt,'YYYY/MM/DD'),sysdate)
AND (EXISTS (SELECT /*+ LEADING(l)*/ NULL
FROM pa_draft_revenues r, pa_cust_rev_dist_lines l
WHERE r.project_id = i.project_id
AND ((l.expenditure_item_id = i.adjusted_expenditure_item_id AND i.adjusted_expenditure_item_id is not null )
OR (l.expenditure_item_id = i.expenditure_item_id))
AND NVL(l.reversed_flag,'N') = 'N'
AND l.line_num_reversed IS NULL
AND r.project_id = l.project_id
AND r.draft_revenue_num = l.draft_revenue_num
AND (r.released_date||'' is not null
OR r.generation_error_flag||'' = decode(:mass_gen,
1, 'N', 'E')))
or exists (
select 1 from pa_expenditure_items ei2
where ei2.project_id = i.project_id
and ei2.expenditure_item_id=i.adjusted_expenditure_item_id
and ei2.revenue_distributed_flag='Y'
and ei2.raw_revenue=0))
union all
SELECT /*+ LEADING(v)*/NULL
FROM pa_events v
WHERE v.project_id = p.project_id
AND ((v.revenue_distributed_flag = 'N'
AND v.completion_date
<= NVL(TO_DATE(:acc_thru_dt,'YYYY/MM/DD'),sysdate))
OR (substr(p.distribution_rule,1,4) = 'COST'
AND v.revenue_distributed_flag = 'Y'
AND v.completion_date
> NVL(TO_DATE('2009/08/31','YYYY/MM/DD'), sysdate)))
AND (DECODE(NVL(v.bill_trans_rev_amount, 0), 0 ,
DECODE(NVL(v.zero_revenue_amount_flag, 'N'), 'Y', 1, 0),1) = 1)
AND NVL(revenue_hold_flag, 'N') = 'N'
AND EXISTS (
SELECT NULL
FROM pa_tasks t
WHERE v.task_id is not NULL
AND t.ready_to_distribute_flag = 'Y'
AND v.task_id = t.task_id
UNION ALL
SELECT NULL
FROM pa_tasks t1
WHERE v.task_id is NULL
AND t1.ready_to_distribute_flag = 'Y'
AND v.project_id = t1.project_id )
AND Exists (select null from pa_draft_revenues r,pa_cust_event_rev_dist_lines l
where l.project_id = v.project_id
AND ( l.task_id = v.task_id OR v.task_id is NULL )
AND l.event_num = v.event_num
AND NVL(l.reversed_flag,'N') = 'N'
AND l.line_num_reversed IS NULL
AND r.project_id = v.project_id
AND r.draft_revenue_num = l.draft_revenue_num
AND (r.released_date||'' is not null
OR r.generation_error_flag||'' = decode(:mass_gen,
1, 'N', 'E')))
union all
SELECT /*+ USE_CONCAT */ NULL
FROM PA_Billing_Extensions be, PA_Billing_Assignments bea
WHERE bea.active_flag = 'Y'
AND bea.billing_extension_id = be.billing_extension_id
AND (bea.project_id = p.project_id
OR bea.project_type = p.project_type
OR bea.distribution_rule = p.distribution_rule)
AND be.calling_process in ('Revenue','Both')
AND nvl(be.call_after_adj_flag, 'N') = 'Y'
AND be.trx_independent_flag = 'Y'))
Current system time is 10-AUG-2009 17:12:11
...0 projects processed for adjustments
Current system time is 10-AUG-2009 17:12:11
...about to generate revenue for project id 196
...Fetching next project
Current system time is 10-AUG-2009 17:12:11
...about to call pa_billing.bill_ext_driver( 196, 'Revenue', 'PRE', '2009/08/31', 714111 )
Current system time is 10-AUG-2009 17:12:11
...exiting pa_billing.bill_ext_driver( 196, 'Revenue', 'PRE', '2009/08/31', 714111 )
Current system time is 10-AUG-2009 17:12:11
Leaving pauoarchn()
...no rows to process for this project.
Current system time is 10-AUG-2009 17:12:11
...generated revenue for project id 196, number 72DM000001
...about to call pa_billing.bill_ext_driver( 196, 'Revenue', 'REG', '2009/08/31', 714111 )
Current system time is 10-AUG-2009 17:12:11
...exiting pa_billing.bill_ext_driver( 196, 'Revenue', 'REG', '2009/08/31', 714111 )
Current system time is 10-AUG-2009 17:12:11
Leaving pauoarchn()
Leaving pauoarchn()
Leaving pauoarchn()
Leaving pauoarchn()
Leaving pauoarchn()
Leaving pauoarchn()
Leaving pauoarchn()
Leaving pauoarchn()
Leaving pauoarchn()
Leaving pauoarchn()
Leaving pauoarchn()
Leaving pauoarchn()
Leaving pauoarchn()
Leaving pauoarchn()
Leaving pauoarchn()
Leaving pauoarchn()
Leaving pauoarchn()
Leaving pauoarchn()
Leaving pauoarchn()
l_inv_by_btc_flag is ...N
l_mcb_flag is ...Y
l_rpc_code is ...GBP
Leaving pauoarchn()
Leaving pauoarchn()
Leaving pauoarchn()
Leaving pauoarchn()
...Else loop 1
...else loop 2
...else loop 4
...else loop 5
...non_zero_amount
Leaving pauoarchn()
Leaving pauoarchn()
Leaving pauoarchn()
Leaving pauoarchn()
Leaving pauoarchn()
Leaving pauoarchn()
...Else loop 1
...else loop 2
...else loop 4
...else loop 5
...non_zero_amount
Leaving pauoarchn()
Leaving pauoarchn()
Leaving pauoarchn()
Current system time is 10-AUG-2009 17:12:11
...generated revenue for automatic events for project id 196, number 72DM000001 calling loc REG
...about to call pa_billing.bill_ext_driver( 196, 'Revenue', 'POST-REG', '2009/08/31', 714111 )
Current system time is 10-AUG-2009 17:12:11
...exiting pa_billing.bill_ext_driver( 196, 'Revenue', 'POST-REG', '2009/08/31', 714111 )
Current system time is 10-AUG-2009 17:12:11
Current system time is 10-AUG-2009 17:12:11
...generated revenue for automatic events for project id 196, number 72DM000001 calling loc POST-REG
...about to call pa_billing.bill_ext_driver( 196, 'Revenue', 'POST', '2009/08/31', 714111 )
Current system time is 10-AUG-2009 17:12:11
...exiting pa_billing.bill_ext_driver( 196, 'Revenue', 'POST', '2009/08/31', 714111 )
Current system time is 10-AUG-2009 17:12:11
...Fetching next project
Current system time is 10-AUG-2009 17:12:11
Current system time is 10-AUG-2009 17:12:11
...about to call AutoAccounting
Current system time is 10-AUG-2009 17:12:11
Current system time is 10-AUG-2009 17:12:11
Current system time is 10-AUG-2009 17:12:11
Current system time is 10-AUG-2009 17:12:11
Entering pafvsu
Allocating pafvcs structure
Allocating memory for structure, fdfkai
Allocating memory for structure, fdfkao
Allocating flex input and output structure
Assigning ptype
Calling pagtfn
Nullig out
Setting everything that does not need to be allocated
Allocating optional arrays
Checking a_line_id
Checking a_trans_ind
Checking a_param_lst
Checking a_extra_atr
Allocating required array
Allocating auto accounting elements
Describing kff and control processing options
Tune flex validation system options
Allocate main cache
Allocate additional memory for main cache
Allocate ksv if needed
Store pointer to text strings in last ksv element so we can free later
val [¿], segval [00000000]
val [00000000], segval [000000]
val [000000], segval [7210OCOA01]
val [7210OCOA01], segval [0000]
val [0000], segval [72OXLFTG]
val [72OXLFTG], segval [66101010]
val [66101010], segval [7210]
Current system time is 10-AUG-2009 17:12:11
Current system time is 10-AUG-2009 17:12:11
Current system time is 10-AUG-2009 17:12:11
Current system time is 10-AUG-2009 17:12:11
Current system time is 10-AUG-2009 17:12:11
Current system time is 10-AUG-2009 17:12:11
Current system time is 10-AUG-2009 17:12:11
Current system time is 10-AUG-2009 17:12:11
...returned from AutoAccounting
...about to update pe_expenditures_all for intercompany processing
Current system time is 10-AUG-2009 17:12:11
Entering parddl()
...setting error codes and bad code combination id to null
... Update draft revenues for marking autoaccounting error if any
Current system time is 10-AUG-2009 17:12:11
0 rows updated.
... Update draft revenues without generation error to normal state
Current system time is 10-AUG-2009 17:12:11
1 rows updated.
... Update pa_cust_event_rev_dist_lines for setting bad CCID to null
Current system time is 10-AUG-2009 17:12:11
0 rows updated.
... Update pa_events for marking AutoAccounting error if any
Current system time is 10-AUG-2009 17:12:11
0 rows updated.
... Update pa_events for setting revenue_distributed_flag to 'N'
Current system time is 10-AUG-2009 17:12:11
0 rows updated.
... Update pa_cust_rev_dist_lines for setting bad CCID to null
Current system time is 10-AUG-2009 17:12:11
0 rows updated.
... Update pa_expenditure_items_all for marking AutoAccounting error if any
Current system time is 10-AUG-2009 17:12:11
0 rows updated.
... Update pa_expenditure_items_all for setting revenue_distributed_flag to 'N'
Current system time is 10-AUG-2009 17:12:11
0 rows updated.
Leaving parddl()
Current system time is 10-AUG-2009 17:12:11
Current system time is 10-AUG-2009 17:12:11
0 rows updated with Generation error due to ccid=-1
Current system time is 10-AUG-2009 17:12:11
0 rows updated with Generation error PA_REV_GEN_ERROR
Current system time is 10-AUG-2009 17:12:11
...1 projects processed for revenue generation
Deleting automatic event for which revenue has generation error
Current system time is 10-AUG-2009 17:12:11
...about to update proj summary funding amounts
executing pa_billing.check_spf_amounts('B',196, , ) Calling check_spf_amounts...Inside the Single projects If
Current system time is 10-AUG-2009 17:12:11
...about to generate reports
SEL-SUC:72DM000001 4 1048 BP Exploration Operating DML 101 31-AUG-09 121659.83
Current system time is 10-AUG-2009 17:12:12
...completed generating reports
Process completed.
0 rows deleted from distribution_warnings table.
Start of log messages from FND_FILE
Request id is :714111
Before calling the insert event for top task_id :19839
Parameters to the insert event API :
Revenue amount is :12106.73
Bill amount is :12106.73
Project id is :196
Event Type is :BILLING
Top Task id is :19839
organization id is :239
completion date is :31-AUG-2009
event description is :Financing Fee
Return status after calling insert event is :0
error message after calling insert event is :
Before calling the insert event for top task_id :14612
Parameters to the insert event API :
Revenue amount is :109553.1
Bill amount is :109553.1
Project id is :196
Event Type is :BILLING
Top Task id is :14612
organization id is :239
completion date is :31-AUG-2009
event description is :Expenditure
Return status after calling insert event is :0
error message after calling insert event is :
End of log messages from FND_FILE
Executing request completion options...
------------- 1) PRINT -------------
Printing output file.
Request ID : 714111
Number of copies : 0
Printer : noprint
Finished executing request completion options.
Concurrent request completed successfully
Current system time is 10-AUG-2009 17:12:12
---------------------------------------------------------------------------

Hi srini,
For the request submitted via the application and for the request submitted by fnd_request.submit_request, argument4 has the same value 2009/08/31 00:00:00
Thanks

Issue with the value set

Hi friends,
am trying to do a percentage calculation from two value sets
like
select round((to_number(:$FLEX$.PROP_BONUS)*100)/(12*to_number(:$FLEX$.XX_SAL)),2) FROM DUAL
this is giving me error ...
those two are number data type value sets.. and am using this in self service pages
the error says like this
oracle.apps.fnd.framework.OAException: oracle.jbo.SQLStmtException: JBO-27122: SQL error during statement preparation. Statement: select fnd_number.number_to_canonical(round((to_number(:$FLEX$.PROP_BONUS)*100)/(12*to_number(:$FLEX$.XX_SAL)),2)) FLEX_VALUE
, to_char(round((to_number(:$FLEX$.PROP_BONUS)*100)/(12*to_number(:$FLEX$.XX_SAL)),2)) FLEX_DISPLAY
from DUAL
where (1 = 1)
and 'Y' = 'Y'
and nvl(fnd_date.canonical_to_date(:1), trunc(SysDate))
between nvl(trunc(to_date(null)), nvl(fnd_date.canonical_to_date(:2), trunc(SysDate)))
and nvl(trunc(to_date(null)), nvl(fnd_date.canonical_to_date(:3), trunc(SysDate)))
and to_char(round((to_number(:$FLEX$.PROP_BONUS)*100)/(12*to_number(:$FLEX$.XX_SAL)),2)) like :L1
order by FLEX_DISPLAY
java.sql.SQLException: ORA-00911: invalid character
can some one suggest me a solution please

Please see if (Unable To Use $FLEX$ In Table Name Field While Creating Value Set [ID 1071197.1]) and (Compilation Error ORA-00911 Occurred After Adding To Descriptive Flexfield [ID 445246.1]) help.
Thanks,
Hussein

Pie chart With one value

Hello Experts,
I am new to apex.
I want to plot a pie chart with only one value.
that one value should look like a one slice in the pie chart.
I tried it, but it showing as entire pie chart as one value.
So Please help me in this regard.
Its very urgent.
Please.

Hi,
Try creating the entire chart using custom XML and PL-SQL, it will give you full control over the sql and xml . Take look at this thread Re: Help Needed : Changing the Color of Bar Graph Dynamically , Change the data_plot_settings to line and you can refer to the http://www.anychart.com/products/anychart/docs/xmlReference/index.html for more detail on the tags and syntax. Thanks.
Regards,
Manish

Problem with Table Value Set

Hi,
i have created a Table value Set for showing Vendor_site_code in DFF
XXXX_VENDOR_NAME
Table Application :Purchasing
Table Name:PO_VENDORS
Value:VENDOR_NAME
ID:VENDOR_ID
XXXX_VENDOR_SITECODE
Table Application :Purchasing
Table Name:PO_VENDORS PV, PO_VENDOR_SITES_ALL PVS
Value:PVS.VENDOR_SITE_CODE
ID:PVS.VENDOR_SITE_ID
where/order by: where PV.VENDOR_ID=PVS.VENDOR_ID
XXX_ITEM
Table Application :IVENTORY
Table Name:MTL_SYSTEM_ITEMS_B
Value:PVSSEGMENT1||'-'||SEGMENT2||SEGMENT3
ID:PVS.INVENTORY_ITEM_ID
where/order by:WHERE ORGANIZATION_ID = cs_std.get_item_valdn_orgzn_id
i am facing the below error when opening the Form related to that DFF
APP-FND-01564: ORACLE error 1722 in FDFGVD
Cause: FDFGVD failed due to ORA-01722: invalid number.
The SQL statement being executed at the time of the error was: SELECT PVS.VENDOR_SITE_ID,PVS.VENDOR_SITE_CODE VALUE, PVS.VENDOR_SITE_CODE DESCRIPTION, NVL('N', 'N'), NVL(TO_NUMBER(NULL), -1), NULL, NVL('Y', 'Y'), NVL(TO_CHAR(TO_DATE(NULL), 'J'), 0), NVL(TO_CHAR(TO_DATE(NULL), 'J'), 0) FROM PO_VENDORS PV, PO_VENDOR_SITES_ALL PVS WHERE ( PV.VENDOR_ID=PVS.VENDOR_ID) AND PVS.VENDOR_SITE_ID = :X and was executed from the file &ERRFILE.

Can you say where have you placed this valueset - which DFF, in which form?

Cost Allocation Flexfield with Table Value Sets

Hi
I am setting up Costing for Payroll. I have a requirement where I want to use Table Validated value sets for Cost Allocation Flexfield. In the Administrator Guide it is written that we should not use Table validated value sets for any KFFs.
I still tried the same (defining Table validated value sets) and my process errored out. It was giving following error
Value 381 for the flexfield segment Cost Center does not exist in the value set
SJR_COST_CENTER_LIST.
invalid code combination:
381SJR_COST_CENTER_LIST is name of the value set.
Then I changed the value set and keep the code and meaning in the value set table as same and my process worked fine.
Now I want to know that should I use Table validated value set or not. As Oracle does not support these in KFFs

Hi Thierry
Thanks for the reply
have you used cross validation rules?I am not sure about cross validation rules and how we can use in my case.
An other thought: there is an action parameter available parameter_name=COST_API_IMODE
Set the parameter_value = 'Y'In my case my costing process is working fine, even when I define my table validated value sets. My question is should we define table validated values sets or not as Oracle does not support it now? Oracle use to support this for KFFs some time back but now they are saying they does not support.
Are there any known issues if we use Table validated value sets? Why Oracle does not support it for KFFs?

[8i] Best way to replace "similar" values with one value...?

Below is some sample data:
Sorry for the large set / complex set of sample data, but there should be no need to go through it in detail =).
2 things to keep in mind:
1) This is an 8i db
2) I cannot create any new tables within this db, though I can create views
CREATE TABLE     ord_master
(     part_nbr          CHAR(25)
,     ord_nbr          CHAR(10)
,     sub_ord_nbr     CHAR(3)
,     ord_type          CHAR(2)
,     ord_stat          CHAR(2)
,     date_closed     DATE
-- please note, though none of the columns in ord_master are explicitly defined as NOT NULL,
-- none of them are NULL in the db, and given how things are input into the table, I don't
-- even think it's possible
-- a unique order is described by ord_nbr, sub_ord_nbr. there should only be one record in
-- this table for a given unique combination of those columns, though they are not the p.k.
-- NOTE: dates default to 12/31/1900, so in the table above, if an order is still open (thus,
-- not closed), it's date_closed will be 12/31/1900. It will only change once the order closes.
INSERT INTO     ord_master
VALUES     ('ABC-123','1','1','AA','CL',TO_DATE('05/01/2009','mm/dd/yyyy'));
INSERT INTO     ord_master
VALUES     ('ABC-123','1','2','AA','CL',TO_DATE('9/14/2009','mm/dd/yyyy'));
INSERT INTO     ord_master
VALUES     ('ABC-123','2','1','AA','CL',TO_DATE('12/03/2009','mm/dd/yyyy'));
INSERT INTO     ord_master
VALUES     ('ABC-123','3','1','AA','OP',TO_DATE('12/31/1900','mm/dd/yyyy'));
INSERT INTO     ord_master
VALUES     ('ABC-123','4','1','AA','CL',TO_DATE('03/12/2004','mm/dd/yyyy'));
INSERT INTO     ord_master
VALUES     ('XYZ-123','5','1','AA','CL',TO_DATE('03/12/2004','mm/dd/yyyy'));
CREATE TABLE     op_detail
(     ord_nbr          CHAR(10)
,     sub_ord_nbr     CHAR(3)
,     major_seq_nbr     CHAR(4)
,     wctr_id          CHAR(5)
,     oper_stat          CHAR(2)
,     plan_su_rsrc     NUMBER(5,2)
,     plan_run_rsrc     NUMBER(11,8)
,     plan_subc_amt     NUMBER(15,5)
,     act_su_rsrc     NUMBER(5,2)
,     act_run_rsrc     NUMBER(7,2)
,     act_subc_amt     NUMBER(15,2)
,     act_start_dt     DATE
,     dt_completed     DATE
,     qty_planned     NUMBER(13,4)
,     qty_recvd          NUMBER(13,4)
,     qty_complete     NUMBER(13,4)
,     qty_scrap          NUMBER(13,4)
,     qty_on_hold     NUMBER(13,4)
-- similar to ord_master, thought none of the columns are explicitly defined as NOT NULL,
-- none of the records have NULL values for any of these columns, and I don't think it's
-- really possible with the way the system is
INSERT INTO     op_detail
VALUES     ('1', '1', '0081', 'X516 ', 'CP', 0, 0, 0, 0, .2, 0, TO_DATE('02/03/2010', 'mm/dd/yyyy'), TO_DATE('02/03/2010', 'mm/dd/yyyy'), 3, 3, 3, 0, 0);
INSERT INTO     op_detail
VALUES     ('1', '1', '0324', 'Y000 ', 'CP', .1, .2, 0, 0, .87, 0, TO_DATE('04/06/2010', 'mm/dd/yyyy'), TO_DATE('04/06/2010', 'mm/dd/yyyy'), 3, 3, 3, 0, 0);
INSERT INTO     op_detail
VALUES     ('1', '1', '0170', 'X928 ', 'CP', 0, 0, 9.6, 0, 0, 159, TO_DATE('03/05/2010', 'mm/dd/yyyy'), TO_DATE('03/05/2010', 'mm/dd/yyyy'), 3, 3, 3, 0, 0);
INSERT INTO     op_detail
VALUES     ('1', '1', '0130', 'H211 ', 'CP', .5, .1, 0, .08, .63, 0, TO_DATE('02/10/2010', 'mm/dd/yyyy'), TO_DATE('02/10/2010', 'mm/dd/yyyy'), 3, 3, 3, 0, 0);
INSERT INTO     op_detail
VALUES     ('1', '2', '0120', 'H214 ', 'CP', .3, .05, 0, 0, .68, 0, TO_DATE('05/22/2009', 'mm/dd/yyyy'), TO_DATE('05/22/2009', 'mm/dd/yyyy'), 3, 3, 3, 0, 0);
INSERT INTO     op_detail
VALUES     ('1', '2', '0122', 'T203 ', 'CP', 2.5, 1, 0, .67, .3, 0, TO_DATE('05/28/2009', 'mm/dd/yyyy'), TO_DATE('05/28/2009', 'mm/dd/yyyy'), 3, 3, 3, 0, 0);
INSERT INTO     op_detail
VALUES     ('1', '2', '0130', 'H211 ', 'CL', .5, .1, 0, .67, .3, 0, TO_DATE('05/28/2009', 'mm/dd/yyyy'), TO_DATE('05/28/2009', 'mm/dd/yyyy'), 3, 3, 3, 0, 0);
INSERT INTO     op_detail
VALUES     ('1', '2', '0170', 'X928 ', 'CP', 0, 0, 9.6, 0, 0, 153.12, TO_DATE('06/10/2009', 'mm/dd/yyyy'), TO_DATE('06/10/2009', 'mm/dd/yyyy'), 3, 3, 3, 0, 0);
INSERT INTO     op_detail
VALUES     ('1', '2', '0324', 'Y000 ', 'CP', .1, .2, 0, 0, .08, 0, TO_DATE('06/17/2009', 'mm/dd/yyyy'), TO_DATE('06/17/2009', 'mm/dd/yyyy'), 3, 3, 3, 0, 0);
INSERT INTO     op_detail
VALUES     ('2', '1', '0081', 'X516 ', 'CL', 0, 0, 0, 0, 0, 0, TO_DATE('07/20/2009', 'mm/dd/yyyy'), TO_DATE('07/20/2009', 'mm/dd/yyyy'), 4, 4, 4, 0, 0);
INSERT INTO     op_detail
VALUES     ('2', '1', '0324', 'Y000 ', 'CL', .1, .2, 0, 0, 3.03, 0, TO_DATE('09/11/2009', 'mm/dd/yyyy'), TO_DATE('09/11/2009', 'mm/dd/yyyy'), 4, 4, 4, 0, 0);
INSERT INTO     op_detail
VALUES     ('2', '1', '0170', 'X928 ', 'CP', 0, 0, 9.6, 0, 0, 204.16, TO_DATE('08/11/2009', 'mm/dd/yyyy'), TO_DATE('08/11/2009', 'mm/dd/yyyy'), 4, 4, 4, 0, 0);
INSERT INTO     op_detail
VALUES     ('2', '1', '0130', 'H211 ','CP', .5, .1, 0, 1.97, 2.67, 0, TO_DATE('07/28/2009', 'mm/dd/yyyy'), TO_DATE('07/29/2009', 'mm/dd/yyyy'), 4, 4, 4, 0, 0);
INSERT INTO     op_detail
VALUES     ('3', '1', '0170', 'X928 ', 'CP', 0, 0, 9.6, 0, 0, 255.2, TO_DATE('11/06/2009', 'mm/dd/yyyy'), TO_DATE('11/06/2009', 'mm/dd/yyyy'), 5, 5, 5, 0, 0);
INSERT INTO     op_detail
VALUES     ('3', '1', '0130', 'H212 ', 'CP', .5, .1, 0, .6, .03, 0, TO_DATE('10/21/2009', 'mm/dd/yyyy'), TO_DATE('10/21/2009', 'mm/dd/yyyy'), 5, 5, 5, 0, 0);
INSERT INTO     op_detail
VALUES     ('3', '1', '0550', 'R501 ', 'WK', 1, 16, 0, 2.2, 12.4, 0, TO_DATE('05/19/2010', 'mm/dd/yyyy'), TO_DATE('12/31/1900', 'mm/dd/yyyy'), 5, 5, 5, 0, 0);
INSERT INTO     op_detail
VALUES     ('3', '1', '0324', 'Y000 ', 'CL', .1, .2, 0, 0, .07, 0, TO_DATE('02/04/2010', 'mm/dd/yyyy'), TO_DATE('02/04/2010', 'mm/dd/yyyy'), 5, 5, 5, 0, 0);
INSERT INTO     op_detail
VALUES     ('4', '1', '0324', 'Y000 ', 'CP', .1, .2, 0, 0, .59, 0, TO_DATE('02/06/2004', 'mm/dd/yyyy'), TO_DATE('02/06/2004', 'mm/dd/yyyy'), 4, 4, 4, 0, 0);This is the query I'm working with right now:
SELECT     o.part_nbr
,          s.major_seq_nbr          AS op_nbr
,          CASE          -- CASE statement to replace similar-to wctr_id's with a single new wctr_id, so we can treat them as the same
               WHEN     s.wctr_id     IN ('H211','H212')
               THEN     'Z211'
               ELSE     s.wctr_id
          END                         AS wctr
,          MIN(s.plan_su_rsrc)          AS min_plan_setup
,          AVG(s.plan_su_rsrc)          AS avg_plan_setup
,          MAX(s.plan_su_rsrc)          AS max_plan_setup
,          STDDEV(s.plan_su_rsrc)     AS sdev_plan_setup
,          MIN(s.plan_run_rsrc)     AS min_plan_run
,          AVG(s.plan_run_rsrc)     AS avg_plan_run
,          MAX(s.plan_run_rsrc)     AS max_plan_run
,          STDDEV(s.plan_run_rsrc)     AS sdev_plan_run
,          MIN(s.plan_subc_amt)     AS min_plan_subc
,          AVG(s.plan_subc_amt)     AS avg_plan_subc
,          MAX(s.plan_subc_amt)     AS max_plan_subc
,          STDDEV(s.plan_subc_amt)     AS sdev_plan_subc
,          MIN(s.act_su_rsrc)          AS min_act_setup
,          AVG(s.act_su_rsrc)          AS avg_act_setup
,          MAX(s.act_su_rsrc)          AS max_act_setup
,          STDDEV(s.act_su_rsrc)     AS sdev_act_setup
,          MIN(s.act_run_rsrc)          AS min_act_run
,          AVG(s.act_run_rsrc)          AS avg_act_run
,          MAX(s.act_run_rsrc)          AS max_act_run
,          STDDEV(s.act_run_rsrc)     AS sdev_act_run
,          MIN(s.act_subc_amt)          AS min_act_subc
,          AVG(s.act_subc_amt)          AS avg_act_subc
,          MAX(s.act_subc_amt)          AS max_act_subc
,          STDDEV(s.act_subc_amt)     AS sdev_act_subc
,          MIN(s.act_start_dt)          AS min_start
,          MAX(s.act_start_dt)          AS max_start
,          MIN(s.dt_completed)          AS min_comp
,          MAX(s.dt_completed)          AS max_comp
,          MIN(s.qty_planned)          AS min_qty_plan
,          AVG(s.qty_planned)          AS avg_qty_plan
,          MAX(s.qty_planned)          AS max_qty_plan
,          STDDEV(s.qty_planned)     AS sdev_qty_plan
,          MIN(s.qty_recvd)          AS min_qty_recvd
,          AVG(s.qty_recvd)          AS avg_qty_recvd
,          MAX(s.qty_recvd)          AS max_qty_recvd
,          STDDEV(s.qty_recvd)          AS sdev_qty_recvd
,          MIN(s.qty_complete)          AS min_qty_comp
,          AVG(s.qty_complete)          AS avg_qty_comp
,          MAX(s.qty_complete)          AS max_qty_comp
,          STDDEV(s.qty_complete)     AS sdev_qty_comp
,          MIN(s.qty_scrap)          AS min_qty_scrap
,          AVG(s.qty_scrap)          AS avg_qty_scrap
,          MAX(s.qty_scrap)          AS max_qty_scrap
,          STDDEV(s.qty_scrap)          AS sdev_qty_scrap
,          MIN(s.qty_on_hold)          AS min_qty_hold
,          AVG(s.qty_on_hold)          AS avg_qty_hold
,          MAX(s.qty_on_hold)          AS max_qty_hold
,          STDDEV(s.qty_on_hold)     AS sdev_qty_hold
,          COUNT(*)                    AS rec_cnt
,          CASE
               WHEN a.ord_min_start     >     ADD_MONTHS(SYSDATE,-12)
               THEN     '12 mos. back'
               WHEN a.ord_min_start     >     ADD_MONTHS(SYSDATE,-24)
               THEN     '24 mos. back'
               WHEN a.ord_min_start     >     ADD_MONTHS(SYSDATE,-36)
               THEN     '36 mos. back'
               ELSE '37 mos. back +'
          END                         AS time_period
FROM          ord_master o
,          op_detail     s
,          (     -- begin in-line view a, to get the min act_start_dt for each order
          SELECT     s1.ord_nbr
          ,          s1.sub_ord_nbr
          ,          MIN     (
                         CASE
                              WHEN     s1.act_start_dt     > TO_DATE('01/01/2000','mm/dd/yyyy')
                              THEN     s1.act_start_dt
                         END
                         )          AS ord_min_start
          FROM          op_detail s1
          GROUP BY     s1.ord_nbr
          ,          s1.sub_ord_nbr
          ) a     -- end in-line view a
WHERE     o.ord_nbr          = s.ord_nbr
AND          o.sub_ord_nbr     = s.sub_ord_nbr
AND          o.ord_nbr          = a.ord_nbr
AND          o.sub_ord_nbr     = a.sub_ord_nbr
AND          o.ord_type     = 'AA'
AND          o.ord_stat     IN ('CL','OP')
AND          s.oper_stat     IN ('CL','CP')
GROUP BY     o.part_nbr
,          s.major_seq_nbr
,          CASE          -- CASE statement to replace similar-to wctr_id's with a single new wctr_id, so we can treat them as the same
               WHEN     s.wctr_id     IN ('H211','H212')
               THEN     'Z211'
               ELSE     s.wctr_id
          END
,          CASE
               WHEN a.ord_min_start     >     ADD_MONTHS(SYSDATE,-12)
               THEN     '12 mos. back'
               WHEN a.ord_min_start     >     ADD_MONTHS(SYSDATE,-24)
               THEN     '24 mos. back'
               WHEN a.ord_min_start     >     ADD_MONTHS(SYSDATE,-36)
               THEN     '36 mos. back'
               ELSE '37 mos. back +'
          END
ORDER BY     o.part_nbr
,          CASE
               WHEN a.ord_min_start     >     ADD_MONTHS(SYSDATE,-12)
               THEN     '12 mos. back'
               WHEN a.ord_min_start     >     ADD_MONTHS(SYSDATE,-24)
               THEN     '24 mos. back'
               WHEN a.ord_min_start     >     ADD_MONTHS(SYSDATE,-36)
               THEN     '36 mos. back'
               ELSE '37 mos. back +'
          END
,          s.major_seq_nbrThis gives me a bunch of descriptive statistics on some data stored in the database, broken into groups by the time period.
I have 7 sets of possible values for the column wctr_id that are groups of similar/same work centers, and should be treated as the same, assuming the ord_nbr, sub_ord_nbr, and major_seq_nbr are the same. In my example case statement above, anytime I find 'H211' or 'H212', I am replacing it with 'Z211', which is my new, unique identifier for any wctr in the group ('H211', 'H212'). I have 7 of these sorts of groups that need to be replaced by a new, unique identifier. Is my CASE statement (noted above) the best way to do this, or is there a better way? These groups of similar-to wctr_id's are not listed in a table anywhere.

Hi,
As always, thanks for posting the CREATE TABLE and INSERT statements; that's very helpful, and leads to faster, better solutions.
Another thing that is helpful, and promotes faster, better solutions, is to simplify your problem.
For example, you have to compute a lot of aggregates, but it looks like you already know how to do that. This problem only involves the CASE expressions, and how they interact with the GROUP BY clause. So just cut out most of the aggregate functions.
Also, it looks like the intricacies of in-line view a have nothing to do with your current problem. For purposes of posting this problem, pretend that a is a regular view, so it doesn't clutter up the main query.
I think your problem could be restated like this:
You already have a query like this:
CREATE OR REPLACE VIEW a
AS
          SELECT     s1.ord_nbr
          ,          s1.sub_ord_nbr
          ,          MIN     (
                         CASE
                              WHEN     s1.act_start_dt     > TO_DATE('01/01/2000','mm/dd/yyyy')
                              THEN     s1.act_start_dt
                         END
                         )          AS ord_min_start
          FROM          op_detail s1
          GROUP BY     s1.ord_nbr
          ,          s1.sub_ord_nbr
SELECT     o.part_nbr
,          s.major_seq_nbr          AS op_nbr
,          CASE          -- CASE statement to replace similar-to wctr_id's with a single new wctr_id, so we can treat them as the same
               WHEN     s.wctr_id     IN ('H211','H212')
               THEN     'Z211'
               ELSE     s.wctr_id
          END                         AS wctr
,          MIN(s.plan_su_rsrc)          AS min_plan_setup
          -- lots of other agtgregates go here in real query
,          CASE
               WHEN a.ord_min_start     >     ADD_MONTHS(SYSDATE,-12)
               THEN     '12 mos. back'
               WHEN a.ord_min_start     >     ADD_MONTHS(SYSDATE,-24)
               THEN     '24 mos. back'
               WHEN a.ord_min_start     >     ADD_MONTHS(SYSDATE,-36)
               THEN     '36 mos. back'
               ELSE '37 mos. back +'
          END                         AS time_period
FROM          ord_master o
,          op_detail     s
,          a          -- in real query, a is an in-line view
WHERE     o.ord_nbr          = s.ord_nbr
AND          o.sub_ord_nbr     = s.sub_ord_nbr
AND          o.ord_nbr          = a.ord_nbr
AND          o.sub_ord_nbr     = a.sub_ord_nbr
AND          o.ord_type     = 'AA'
AND          o.ord_stat     IN ('CL','OP')
AND          s.oper_stat     IN ('CL','CP')
GROUP BY     o.part_nbr
,          s.major_seq_nbr
,          CASE          -- CASE statement to replace similar-to wctr_id's with a single new wctr_id, so we can treat them as the same
               WHEN     s.wctr_id     IN ('H211','H212')
               THEN     'Z211'
               ELSE     s.wctr_id
          END
,          CASE
               WHEN a.ord_min_start     >     ADD_MONTHS(SYSDATE,-12)
               THEN     '12 mos. back'
               WHEN a.ord_min_start     >     ADD_MONTHS(SYSDATE,-24)
               THEN     '24 mos. back'
               WHEN a.ord_min_start     >     ADD_MONTHS(SYSDATE,-36)
               THEN     '36 mos. back'
               ELSE '37 mos. back +'
          END
ORDER BY     o.part_nbr
,          CASE
               WHEN a.ord_min_start     >     ADD_MONTHS(SYSDATE,-12)
               THEN     '12 mos. back'
               WHEN a.ord_min_start     >     ADD_MONTHS(SYSDATE,-24)
               THEN     '24 mos. back'
               WHEN a.ord_min_start     >     ADD_MONTHS(SYSDATE,-36)
               THEN     '36 mos. back'
               ELSE '37 mos. back +'
          END
,          s.major_seq_nbr
;that produces this output:
`                       MIN_
                       PLAN_
PART_NBR   OP_N WCTR   SETUP TIME_PERIOD
ABC-123    0081 X516      .0 12 mos. back
ABC-123    0130 Z211      .5 12 mos. back
ABC-123    0170 X928      .0 12 mos. back
ABC-123    0324 Y000      .1 12 mos. back
ABC-123    0120 H214      .3 24 mos. back
ABC-123    0122 T203     2.5 24 mos. back
ABC-123    0130 Z211      .5 24 mos. back
ABC-123    0170 X928      .0 24 mos. back
ABC-123    0324 Y000      .1 24 mos. back
ABC-123    0324 Y000      .1 37 mos. back +The output is correct; the problem is, can we get the same results without 2 copies of the wctr CASE expression, and 3 copies of the time_period CASE expression?
Is that a fair description of the problem?
For starters, you can use column aliases in the ORDER BY clause. Unfortunately, that's the only place where you can use column aliases in the same query where they are defined . You can compute them in a sib-query, and then use them in super-queries.
In other words, wouldn't it be nice if we had a table just like op_detail, but with an additional column called wctr? Make a view: either a regular view (especially if wctr, computed the same way, will be used in several different queries) or an in-line view, as shown below.
Wouldn't it be great if there was a table that was just like a, except that it had time_period alreay computed? Make a view: either a regular view or an in-line view, as shown below.
SELECT     o.part_nbr
,     s.major_seq_nbr          AS op_nbr
,     s.wctr
,     MIN(s.plan_su_rsrc)          AS min_plan_setup
     -- lots of other agtgregates go here in real query
,     a2.time_period
FROM     ord_master      o
,     (          -- Begin in-line view s, with data from op_detail
             SELECT op_detail.*      -- or list all columns needed in main query
          ,     CASE          -- replace similar-to wctr_id's with a single new wctr_id, so we can treat them as the same
                   WHEN     wctr_id        IN ('H211','H212')
                   THEN     'Z211'
                   ELSE     wctr_id
               END                    AS wctr
          FROM     op_detail
     ) s          -- End in-line view s, with data from op_detail
,     (           -- Begin in-line view a2, to compute time_period
          SELECT a.*
          ,     CASE
                   WHEN ord_min_start     >     ADD_MONTHS(SYSDATE,-12)
                       THEN     '12 mos. back'
                       WHEN ord_min_start     >     ADD_MONTHS(SYSDATE,-24)
                       THEN     '24 mos. back'
                       WHEN ord_min_start     >     ADD_MONTHS(SYSDATE,-36)
                       THEN     '36 mos. back'
                       ELSE '37 mos. back +'
               END                         AS time_period
          FROM     a          -- in real query, a is an in-line view
     ) a2          -- End in-line view a2, to compute time_period
WHERE     o.ord_nbr     = s.ord_nbr
AND     o.sub_ord_nbr     = s.sub_ord_nbr
AND     o.ord_nbr     = a2.ord_nbr
AND     o.sub_ord_nbr     = a2.sub_ord_nbr
AND     o.ord_type     = 'AA'
AND     o.ord_stat     IN ('CL','OP')
AND     s.oper_stat     IN ('CL','CP')
GROUP BY     o.part_nbr
,          s.major_seq_nbr
,          s.wctr
,          a2.time_period
ORDER BY     o.part_nbr
,          a2.time_period
,          s.major_seq_nbr
;In your example, wctr is the same as wctr_id except for two values. If it was more complicated (e.g., if there were not just 2 values that need to be mapped to 'Z211', but also 3 values to were equivalent to 'Z987', and 1 that was to be treated like 'A012', and 5 that should appear as 'A666', and ...), then you could code all that in a humongeous CASE expression (a nested CASE expression, if it involves more that 128 branches), but it really belongs in a table, where you have the raw wctr_id (like 'H211') in one column, and its corresponding equivalent (such as 'Z211') in another. I know you said you can't create new tables; I'm just pointing this out so you can tell the people who won't let you create new tables that it's a bad idea, likely to cause errors and certain to waste time in the future.

Dimension with one value not returned

Hi all,
I have a question related with the dimensions returned by the Endeca search results.
There is one dimension, which has only one single value for all records, that is not returned with the Endeca search results.
Do you know why can this happen?
Many thanks,
Alejandra

Alejandra,
Yes. Guided navigation only returns "valid refinements" for a given navigation state. In other words, after each refinement is made, the Endeca Server recalculates which refinements are now valid. Valid refinements are those that, if selected, will filter the result set further. If every record in a result set carries the same dimension with the same value, the Endeca Server will not return it since it is not valid as a refinement. If every record has it, selecting it would not refine the results further -- rather, it would return the same collection of records that is already displayed effectively accomplishing nothing.
I suspect that EVERY record in your Endeca Server has the same value for a dimension and, by design, the Endeca Server is not returning it in guided navigation.
HTH,
Dan
http://branchbird.com

Comparing database table with one value

hi,
i need to compare a value with table record.
how can i compare?
please help me.
Thank you

I guess your question doesn't fully present your
doubt.. JDBC is the obvious answer for accessing the
database and taking the result set.. Post back if
this is not what you wanted..It's too obvious and like many others the OP might not ever visit this thread.

How do I remove Restriction Passcode if one is set up accidentally?

If I have restrictions set "On" under General Settings and can not remember my password, how do I remove the restrictions? I tried restoring it but the Restrictions still show 'On'.

You have to restore the iPod to factory defaults/new iPod.

Can't write to strict typedef with Control Value:Set [Variant]

Hey everyone,
I inherited a project that uses stacked strict typedefs for the front panel, and I need to programmatically change one control, and it is within an event. However, the control is a strict typedef in a strict typedef, and Control Valueet [Variant] has no effect on the specific control. I have gotten the method to work in small test vi's without typedefs, so I'm pretty sure that is the problem.
The only thing I can think of is that there is a unique way of referencing the control name through typedefs, and I don't know it.
Any ideas?
Thanks in advance,
Jeff
=============
XP SP2, LV 8.2
CLAD

Lynn,
Thanks for the reply. It turns out that to programmatically Control Valueet [Variant] bundled controls, you can only pass in the top level bundle control name. It took some tricky placement around my structures, but I eventually unbundled and bundled by name from the top level down to the bottom and back up to make it work.
Thanks again
- Jeff
=============
XP SP2, LV 8.2
CLAD

How to restrict value set to a certain responsibility

A group of users need access to add values to a value set. We dont want them to access all available value sets. So how can I restrict the responsiblity to access only one value set? can we create a function or something and pass the value set name? or does it need form personalization?
Thanks.

I don't think it's possible adding parameters to the form function. So, you would need to use form personalizations or add some code to the CUSTOM.pll. Another possibility would be to use lookups instead of value sets. Lookups can be restricted using form function parameters.
Hope it helps.

WAD - Exclude more than one value with filter button

Hi guys
I have been working on a web template with a button to set a filter to exclude two values. E.g. I want to exclude both the values '28' and '30' from the dataprovider.
What I have done is insert a button group item, create a button with the command SET_SELECTION_STATE_SIMPLE to exclude '28' as command 1 and SET_SELECTION_STATE_SIMPLE to exclude '30' as command 2. This does however not give me the correct result, as it only excludes '30' as set in command 2. So the conclusion must be that SET_SELECTION_STATE_SIMPLE can not be used, as it will only work with one value.
So I went on and tried with SET_SELECTION_STATE which gives the possibility to choose more than one filter value. However it does not seem possible to exclude values with this command?
Is it not possible to exclude two filter values with a button in a BI 7.x web template?
BR
Stefan.

Dear Frank
I did it as like as the following link lead me:
http://www.oracle.com/technology/obe/obe11jdev/11/adfbc_new_features/adfbc.html
The problem has been appeared when I attached the "Create" button and when press on it to create new record, then the "LOV" couldn't work correctly.
Thanks for your reply

DropdownByKey inside ALV Table - Problem with Value set

Hi,
I have Component A which has a custom controller that uses the interface controller of the ALV Component.
Custom controller has node ITAB.. that has certain attributes...
I want DropdownByKey inside the ALV Table column. I am populating the corresponding attribute of ITAB node with the value set that I want the drop down to have.
However when I execute the application..I get error
" Key XXX not present in Value Set and is not initial"
XXX is present in the Value Set table of the attribute.
Following is my code in the methods of CUSTOM CONTROLLER
Generate Value Set
nodeinfo_context = wd_context->get_node_info( ).
nodeinfo_ITAB= nodeinfo_context->get_child_node( wd_this->wdctx_ITAB ).
 Populate the Value Set
data ls_valueset type wdy_key_value.
data it_valueset type wdy_key_value_table.
ls_valueset-key = 'FRA'.
ls_valueset-value = 'FRANCE'.
Append ls_valueset to it_valueset.
ls_valueset-key = 'SFO'.
ls_valueset-value = 'SAN FRANCISCO'.
Append ls_valueset to it_valueset.
Set the Value Set for the Attribute
call method nodeinfo_ITAB->SET_ATTRIBUTE_VALUE_SET
 EXPORTING
 NAME = 'ATTR1'
 VALUE_SET = it_valueset.
Changing ALV Column
Get the ALV Configuration Model
ifc_alv2 = wd_this->wd_cpifc_alv2( ).
itab_alv2_config = ifc_alv2->get_model( ).
itab_alv2_config->IF_SALV_WD_TABLE_SETTINGS~SET_READ_ONLY( abap_false ).
Get the Column reference for ATTR1
ref_alv2_colset = itab_alv2_config->if_salv_wd_column_settings~get_column( 'ATTR1' ).
Create the DropDownByKey Object
CREATE OBJECT ref_dropdownkey
 exporting SELECTED_KEY_FIELDNAME = ref_alv2_colset->id.
ref_dropdownkey->SET_SELECTED_KEY_FIELDNAME( ref_alv2_colset->id ).
ref_alv2_colset->SET_CELL_EDITOR( ref_dropdownkey ).
Check the value set
ref_attr_info = nodeinfo_flight_details2->get_attribute( ref_alv2_colset->id ).
I do get back the value set if I see ref_attr_info->value_set.
SO the Value Set is getting set for attribute ATTR1, but still I get Error
"The value selectedKey = "SFO" in DropDownByKey "_8C" does not exist in the value list and is not initial either "
SAP User

You have forgotten to set a cell variant. I had the same with setting a ProgressIndicator cell-editor to a table column as default editor. This causes the column to be hidden on the table while it did show up in the settings dialog. I removed the set_editor( lr_progressindicator) and created a cell variant instead with this lr_progressindicator. You then need to add this cell variant to your column. By default it will select the standard viewtext-cell-editor (which can only be textview and inputfield, like when you create a table yourself in a view), but if you use a cell variant, it will display the required cell editor if you set it (last line of the code).
In your case, replace lr_progressindicator by your ref_dropdownkey.
DATA: lr_column_settings TYPE REF TO if_salv_wd_column_settings,
 lr_column TYPE REF TO cl_salv_wd_column,
 lr_column_header TYPE REF TO cl_salv_wd_column_header,
 lr_cellvar TYPE REF TO cl_salv_wd_cv_standard,
 l_cellvar TYPE string,
 lr_progress_indicator TYPE REF TO cl_salv_wd_uie_progr_indicator.
lr_column_settings ?= wd_this->mr_table.
lr_column = lr_column_settings->get_column( 'STATUSBAR' ).
lr_column_header = lr_column->get_header( ).
lr_column_header->set_text( 'Completed' ).
CREATE OBJECT lr_cellvar.
l_cellvar = 'CV_SB'.
lr_cellvar->set_key( l_cellvar ).
CREATE OBJECT lr_progress_indicator.
lr_progress_indicator->set_percent_value_fieldname( 'STATUSBAR' ).
lr_progress_indicator->set_tooltip( 'completed' ).
lr_cellvar->set_editor( lr_progress_indicator ).
lr_column->add_cell_variant( lr_cellvar ).
lr_column->set_selected_cell_variant( l_cellvar ).
I hope this will solve your issues.

Restrict responsibility with one value set

Similar Messages

Maybe you are looking for