Oracle ASCP collections and planning

how do you perform data pull from the source and load the data into the ASCP instance ? what are the steps that need to be performed.
and what is the AOL concurrent program that needs to be run to perform the Data collection.
and how do you load this data into a User Interface. i'm still in a basic understanding on oracle ascp. please do provide the steps in a simpler manner jus for the basic understanding.
thanks.
krishna

You can refer this link
http://docs.oracle.com/cd/E18727_01/doc.121/e13358/T309464T309468.htm
thanks

Similar Messages

ASCP collections not collecting the Items description from source Instance

Hi,
We have defined one item in source instance with item's description in Inventory. After the collection and planning, in workbench we could not able to see the Item's description. Can anyone advice me why the Item's description was not collected and shown in ASCP workbench?
Thanks & Regards,
Bharathram.N

Hi Kevin,
Thanks for your update. Now I can able to see Item's description in workbench.
Actually somebody have mistakenly deleted the decription field in the backend in the table MTL_SYSTEM_ITEMS_B but the same item's dscription was present in MTL_SYSTEM_ITEMS_TL and thats how we found somebody have done this deletion manually from backend and not through the ITEM API.
Now we have populated the description field in MTL_SYSTEM_ITEMS_B and ran the standard collection and the same being shown in ASCP Workbench.
Thanks for your inputs.
Thanks & Regards,
Bharathram.N

How Oracle ASCP and Inventory are integrated ,what are the Integration poin

Hi All Gurus,
Can any one tell me..
How Oracle ASCP and Inventory are integrated ,what are the Integration point of these modules ...?
Thanks,
Satyam

Here is a simplistic explanation on the the integration.
When you launch data collection from the ASCP side, Oracle launches a Refresh Snapshot process that gathers the latest inventory (and other modules) information into Snapshots. Snapshots are like materialized views. Then the Planning Data Pull is launched. That process pulls information from these snapshots into the ASCP side.
The following inventory information comes over to ASCP
Item master data (such as order modifiers, planning exception sets etc. )
item categories
Onhand quantities (including consigned invetory quantities) in nettable locations
subinventories
reservations
safety stocks
forecasts
item planners
Quantity in receiving or in transit
Hope this answers your question
Sandeep Gandhi
Independent Consultant
513-325-9026

How MS/MRP and Oracle ASCP will work for Manufracturing for a Item 'PEN' .

Hi All,
I am having oracle MS/MRP and Oracle ASCP.
I want to manufrature item as PEN. All items are buy items
Can any one tell here how MS/MRP & ASCP will work to manufrature a pen.
What will be the flow of these 2 modules?
Thanks,
Edited by: user11362919 on Jul 9, 2009 1:11 AM

Hi
If I understand your qn correctly you are asking about a writing pen ?
Lets say it has parts like pen body,refill,top and cap all these items will have ''buy souricng rules''.
Based on demand for the end item ''Pen'' AsCP will explode BOM for the Pen and suggest supplies as planned orders for the components , which can be converted to Std PO or BPA release automatically. All that MRP module could be of use to you is to define Forecast demand for the item.
Best Regards
Partha

Oracle 11i - Collection Plans (Discrete Manufacturing)

In Oracle Quality, Collection Elements can use SQL validation code to provide a LOV for data entry into a Collection Plan.
Collection Element values can also be determined using SQL code that includes using Token field values for data already entered into the current Collection Plan (e.g. JOB) as part of the query. However, the result of this query must be a unique value.
Can anyone tell me if its possible to use Token fields from Collection Elements already entered into a Collection Plan as part of the validation code to display a LOV?
I cannot see any way to do this.
Thanks
Edited by: user11340385 on Dec 17, 2012 11:29 AM

Thanks Peter,
I'm a newbie and it got posted there by accident.
I did notice this afterwards but then couldn't find somewhere for "EBS Discrete Manufacturing".
What's the best place for it and can it be moved there without me resending it?

Data extracted from Oracle ASCP and presented in OBI

Hello,
I work for a company using the Oracle APS suite and for demand management and supply planning. The ASCP (Advanced Supply Chain Planning) tool is the key tool for our end user planners.
What are the interfaces like between Oracle APS and OBI?
Are there any OBI users who have enjoyed success using OBI to present the detailed data out of ASCP? The users report that getting visibility to the data in ASCP using the out of the box ASCP functionality is very limited.
I am interested in general feedback and any suggestions on where to get more information or perhaps to read about how other companies are using APS/OBI together.
Thanks and Best Regards,
Jim Shaughnessy

One way of doing this is setup Heterogeneous Database connections
http://www.dba-oracle.com/t_heterogeneous_database_connections_sql_server.htm
I am sure there's other options out there.

Prerequisitions to be enabled/followed for the items that has to come in ASCP Collection Plan

Hi team,
I need to know what are all the prerequisitions to be enabled/followed for the items that has to come in ASCP Collection Plan (ie.,) the Item must be in Active status & Planning Method must be in MRP Planning like wise.
Anyone please give me the details.
Thanks in advance.
Suriya

Please check Support Note 1060245.1 Advanced Supply Chain Planning (ASCP) Item Collection Criteria
Regards,

Replacing Oracle OFA with Enterprise Planning and Budget or Hyperion

I'm looking at replacing OFA with EPB. Does this option still exist or has Oracle
phased it out?

Hi,
Oracle Hyperion Planning is the way forward and is the budgeting and planning tool of choice for Oracle.
So if you are going to make an investment I would go for Hyperion Planning.
Cheers
John
http://john-goodwin.blogspot.com/

Oracle Retail Merchandise Financial Planning and RPAS

Hi, i'm new with Oracle Retail and ORACLE RPAS. I would like ton know the best way to backup RPAS or if RPAS support Real Application Cluster or something like that.
We will install Oracle Retail Merchandise Financial Planning component and i would like the best architecture to do it.
Regards

Question:
What makes up the added value in OR MerchandiseAnalytics over ORDW?
Both offer extraction layer, staging layer, datamart layer, aggregate layer, OBIEE + prebuilt reports.
I want to know how the fact extraction layer on ORMS etc. is done using ODI. Unfortunately I see no CDC/Streams approach, that we have chosen to use for our extensions to the ORDW datamodel. Is the extraction logic more or less a rebuild of the good old Pro*C DWI programs?
Some points:
- More products have been connected to ORMA, additional to RMS: ReIM, ReSA, ORMFP, ORPM.
- ORMA has had an technology update for the ETL, from OR-only's custom RETL to the more general Oracle ODI (formerly Sunopsis).
- Is it the promised/future integration of one set of conformed dimension reused and shared over all other to-be OR analytics products? (Like Marketing, Planning, Supply Chain, Stores).
- ORMA offers 'Dashboards' - may be straightforward to make in RDW-OBIEE?
- ORMA offers multiple timeviews, where base RDW only offers AsWas (SCD2) - bsiness users may appreciate the AsIs view, and PIT.
Cherio,
Erik
Edited by: ErikYkema on May 25, 2011 10:38 PM
According to the RMS13.2 release notes (http://download.oracle.com/docs/cd/E12448_01/rms/pdf/rms_rfm_br/132/rms-132-rn.pdf), RETL and all RETL based interfaces to ORDW are desupported from 13.2!
“Discontinued Support for Oracle Retail Data Warehouse (RDW) Interfaces
A new analytical application is in development. Because of this strategic decision, support for interface between Oracle Retail applications and Oracle Retail Data Warehouse has been discontinued for Oracle Retail 13.2 releases. Oracle Retail Extract, Transform, and Load (RETL) extract scripts for RDW are not supported for use with Oracle Retail 13.2 applications and databases.”
That makes things a lot clearer!

Apex Collections and dates

Apex Collections and Dates
I made an earlier posting today on the forum titled “‘ORA-01861: literal does not match format string’ error after my hosting company upgraded to Apex 3.2.” The issue relates to Apex collections and dates. Prior to the hosting company upgrading Apex 3.2 from 3.1 all was working OK. It seemed a reasonable assumption that the issue relates to the upgrade to 3.2. Having tested the code against another Apex 3.2 installation I am satisfied that the issue is not with Apex 3.2. That said, I am still getting the issue on the hosting site.
To demonstrate the issue to my hosting company and this forum, I put together a simple one page application that demonstrates the issue using the least amount of code.
I created a page with an ‘On Load – Before header” process that sets up an Apex Collection with a single value of ’20-FEB-2009’ in the c001 element as follows:
if apex_collection.collection_exists(p_collection_name=>'THEISSUE') then
apex_collection.delete_collection(p_collection_name=>'THEISSUE');
end if;
apex_collection.create_collection(p_collection_name => 'THEISSUE');
APEX_COLLECTION.ADD_MEMBER(
p_collection_name => 'THEISSUE',
p_c001 => '20-FEB-2009');
I added an SQL REPORT region to the page which uses the Apex Collection as follows:
select to_date(c001,'DD-MON-YYYY') testdate
from apex_collections
where collection_name='THEISSUE'
and to_date('20-FEB-2009','DD-MON-YYYY')
= to_date(c001,'DD-MON-YYYY')
When the page is run I get the ‘ORA-01861: literal does not match format string’ error.
If I remove the following from the SQL Report Region:
and to_date('20-FEB-2009','DD-MON-YYYY')
= to_date(c001,'DD-MON-YYYY')
and run the page, the date is displayed OK, i.e., c001 is converted to a date OK. This made me wonder whether it does not like the line to_date('20-FEB-2009','DD-MON-YYYY')? So I changed the where code for the report to :
and to_date(c001,'DD-MON-YYYY')
= to_date(c001,'DD-MON-YYYY')
i.e., convert c001 to a date and compare it to itself. The rationale being that if the c001 converts to a date OK, then comparing c001 converted to a date with itself should not give an error. It did it gave the same error ‘ORA-01861’
It would seem on my hosting site since the upgrade, that Apex and Oracle have problems with Apex Collection elements being converted to dates as part of the where clause.
Now my understating of Oracle Apex collections in simple terms is that all Apex collections are held in a single Oracle table managed by a series of Apex functions. Given that all Apex collections are in the same table, could the issue be with the Oracle database when it is creating its execution plan for the query? Could Oracle be including the value of c001 from other collections (i.e., when c001 is not in a date format ) in the initial stages of its execution plan?
I hope the above make sense and thanks in advance.
Ian

Scott,
I believe I have found the answer the statistics on WWV_FLOW_COLLECTIONS$ and WWV_FLOW_COLLECTION_MEMBERS$. are out of date and Oracle is doing a full table scan instead of using the indices to select only the c001 columns that belong to the given collection_id. If I change my simple example to store the date value in c050 it works ok. (In all probability this will be the only collection on the hosted database to use c050).
I have asked the hosting company to gather stats on all the apex tables.
Thanks for your help
Ian

4 Problems in Oracle ASCP

Hi,
I have 4 problems with Oracle ASCP. 1) I have defined and saved unconstrained plan but the same is not seen in the Planner's workbench. 2) When I try to create and save simulated plan, it throws an error saying "the record already exists, you have entered duplicate values" 3) I am unable to define and save Profile Options as the corresponding fields are not activated. 4) i have created a query to retrieve information of a particular product and executed it successfully for the first time, but when I attempt to execute the same query again for the next time it asks for re-naming of the query i did it, after that when i clicked on OK button an error is displayed saying "the record already exists, you have entered duplicate values" I am a beginner and working for a live project. I request you to please help me in resolving the above errors.

hello,
regarding 1:
you need to put a group frame around the graph and make it collapsable. that way on the second page where there is nograph, the room is collapsed to 0 and your table can start from the top.
regarding 2:
you can not do summaries in the graph itself. the graph just visualizes the data of a query. so you need to have a query that returns you the data in the desired format.
regards,
philipp

ASCP Collections

I know ASCP gets the Items, BOM, Sales Orders. Sourcing Rules etc as part of the collections program.
Is there any way to restrict the level at which the BOM can be collected?
For example if the ATO has the
Item
|
Top Level Assembly (TLA)
|
Components
How to ensure only item and TLA gets collected and not the components?
Thanks

You can change the mrp planning code for the components to not planned.
Hope this helps,
Sandeep Gandhi
You can see Advanced Supply Chain Planning (ASCP) Item Collection Criteria [ID 1060245.1] for more details.

Datatype best practice and plan cardinality

Hi,
I have a scenario where I need to store the data in the format YYYYMM (e.g. 201001 which means January, 2010).
I am trying to evaluate what is the most appropriate datatype to store this kind of data. I am comparing 2 options, NUMBER and DATE.
As the data is essentially a component of oracle date datatype and experts like Tom Kyte have proved (with examples) that using right
datatype is better for optimizer. So I was expecting that using DATE datatype will yield (at least) similar (if not better) cardinality estimates
than using NUMBER datatype. However, my tests show that when using DATE the cardinality estimates are way off from actuals whereas
using NUMBER the cardinality estimates are much closer to actuals.
My questions are:
1) What should be the most appropriate datatype used to store YYYYMM data?
2) Why does using DATE datatype yield estimates that are way off from actuals than using NUMBER datatype?
SQL> select * from V$VERSION ;
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod
PL/SQL Release 10.2.0.1.0 - Production
CORE     10.2.0.1.0     Production
TNS for Linux: Version 10.2.0.1.0 - Production
NLSRTL Version 10.2.0.1.0 - Production
SQL> create table a nologging as select to_number(to_char(add_months(to_date('200101','YYYYMM'),level - 1), 'YYYYMM')) id from dual connect by level <= 289 ;
Table created.
SQL> create table b (id number) ;
Table created.
SQL> begin
2 for i in 1..8192
3 loop
4     insert into b select * from a ;
5 end loop;
6 commit;
7 end;
8 /
PL/SQL procedure successfully completed.
SQL> alter table a add dt date ;
Table altered.
SQL> alter table b add dt date ;
Table altered.
SQL> select to_date(200101, 'YYYYMM') from dual ;
TO_DATE(2
01-JAN-01
SQL> update a set dt = to_date(id, 'YYYYMM') ;
289 rows updated.
SQL> update b set dt = to_date(id, 'YYYYMM') ;
2367488 rows updated.
SQL> commit ;
Commit complete.
SQL> exec dbms_stats.gather_table_stats(user, 'A', estimate_percent=>NULL) ;
PL/SQL procedure successfully completed.
SQL> exec dbms_stats.gather_table_stats(user, 'B', estimate_percent=>NULL) ;
SQL> explain plan for select count(*) from b where id between 200810 and 200903 ;
Explained.
SQL> select * from table(dbms_xplan.display) ;
PLAN_TABLE_OUTPUT
Plan hash value: 749587668
| Id | Operation        | Name | Rows | Bytes | Cost (%CPU)| Time       |
|   0 | SELECT STATEMENT   |       |     1 |     5 |   824   (4)| 00:00:10 |
|   1 | SORT AGGREGATE    |       |     1 |     5 |            |       |
|* 2 |   TABLE ACCESS FULL| B       | 46604 |   227K|   824   (4)| 00:00:10 |
Predicate Information (identified by operation id):
PLAN_TABLE_OUTPUT
   2 - filter("ID"<=200903 AND "ID">=200810)
14 rows selected.
SQL> explain plan for select count(*) from b where dt between to_date(200810, 'YYYYMM') and to_date(200903, 'YYYYMM') ;
Explained.
SQL> select * from table(dbms_xplan.display) ;
PLAN_TABLE_OUTPUT
Plan hash value: 749587668
| Id | Operation        | Name | Rows | Bytes | Cost (%CPU)| Time       |
|   0 | SELECT STATEMENT   |       |     1 |     5 |   825   (4)| 00:00:10 |
|   1 | SORT AGGREGATE    |       |     1 |     5 |            |       |
|* 2 |   TABLE ACCESS FULL| B       | 5919 | 29595 |   825   (4)| 00:00:10 |
Predicate Information (identified by operation id):
PLAN_TABLE_OUTPUT
   2 - filter("DT">=TO_DATE('2008-10-01 00:00:00', 'yyyy-mm-dd
           hh24:mi:ss') AND "DT"<=TO_DATE('2009-03-01 00:00:00', 'yyyy-mm-dd
           hh24:mi:ss'))
16 rows selected.

Charles,
Thanks for your response.
I did not think of the possibilitty of histograms. When I ran the tests on 10.2.0.4, I could get the results as you have shown.
So I thought it might be due to some bug in 10.2.0.1. But interestingly, when I ran the test after collecting statistics using 'FOR ALL COLUMNS SIZE 1'
option, I got the cardinalities that match my 10.2.0.1 results (where METHOD_OPT was default i.e. 'FOR ALL COLUMNS SIZE AUTO').
So I carried out the tests again on 10.2.0.1 but the results did not look consistent to me. When there were no histograms on DATE column, the cardinality
was quite close to actuals but when I collected stats using 'FOR ALL COLUMNS SIZE SKEWONLY', it generated histograms on DATE column but
the cardinality was not quite close to actuals.
So I am bit confused about whether this is due to a bug or due to combined effect of optimizer's "intelligence" while collecting statistics using default option
values and the way table is queried (COL_USAGE$ data).
Here is my test:
SQL> select * from v$version ;
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod
PL/SQL Release 10.2.0.1.0 - Production
CORE     10.2.0.1.0     Production
TNS for Linux: Version 10.2.0.1.0 - Production
NLSRTL Version 10.2.0.1.0 - Production
SQL> exec dbms_stats.delete_table_stats(user, 'B') ;
PL/SQL procedure successfully completed.
SQL> select column_name, num_distinct, num_buckets, histogram from user_tab_col_statistics where table_name = 'B' ;
no rows selected
SQL> exec dbms_stats.gather_table_stats(user, 'B') ;
PL/SQL procedure successfully completed.
SQL> select column_name, num_distinct, num_buckets, histogram from user_tab_col_statistics where table_name = 'B' ;
COLUMN_NAME                    NUM_DISTINCT NUM_BUCKETS HISTOGRAM
ID                                      289         254 HEIGHT BALANCED
DT                                      289         254 HEIGHT BALANCED
SQL> explain plan for select count(*) from b where b.id between 200810 and 200903 ;
Explained.
SQL> select * from table(dbms_xplan.display) ;
PLAN_TABLE_OUTPUT
Plan hash value: 749587668
| Id | Operation          | Name | Rows | Bytes | Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT   |      |     1 |     5 | 3691   (1)| 00:00:45 |
|   1 | SORT AGGREGATE    |      |     1 |     5 |            |          |
|* 2 |   TABLE ACCESS FULL| B    | 38218 |   186K| 3691   (1)| 00:00:45 |
Predicate Information (identified by operation id):
   2 - filter("B"."ID"<=200903 AND "B"."ID">=200810)
14 rows selected.
SQL> explain plan for select count(*) from b where b.dt between to_date(200810, 'YYYYMM') and to_date(200903, 'YYYYMM') ;
Explained.
SQL> select * from table(dbms_xplan.display) ;
PLAN_TABLE_OUTPUT
Plan hash value: 749587668
| Id | Operation          | Name | Rows | Bytes | Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT   |      |     1 |     8 | 3693   (1)| 00:00:45 |
|   1 | SORT AGGREGATE    |      |     1 |     8 |            |          |
|* 2 |   TABLE ACCESS FULL| B    | 38218 |   298K| 3693   (1)| 00:00:45 |
Predicate Information (identified by operation id):
   2 - filter("B"."DT"<=TO_DATE('2009-03-01 00:00:00', 'yyyy-mm-dd
              hh24:mi:ss') AND "B"."DT">=TO_DATE('2008-10-01 00:00:00', 'yyyy-mm-dd
              hh24:mi:ss'))
16 rows selected.
SQL> connect sys as sysdba ;
Connected.
SQL> delete from sys.col_usage$ where obj# in (select object_id from all_objects where owner = 'HR' and object_name in ('A','B')) ;
4 rows deleted.
SQL> commit ;
Commit complete.
SQL> connect hr/hr ;
Connected.
SQL> set serveroutput on size 10000
SQL> exec dbms_stats.delete_table_stats(user, 'B') ;
PL/SQL procedure successfully completed.
SQL> exec dbms_stats.gather_table_stats(user, 'B') ;
PL/SQL procedure successfully completed.
SQL> select column_name, num_distinct, num_buckets, histogram from user_tab_col_statistics where table_name = 'B' ;
COLUMN_NAME                    NUM_DISTINCT NUM_BUCKETS HISTOGRAM
ID                                      289           1 NONE
DT                                      289           1 NONE
SQL> explain plan for select count(*) from b where b.id between 200810 and 200903 ;
Explained.
SQL> select * from table(dbms_xplan.display) ;
PLAN_TABLE_OUTPUT
Plan hash value: 749587668
| Id | Operation          | Name | Rows | Bytes | Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT   |      |     1 |     5 | 3691   (1)| 00:00:45 |
|   1 | SORT AGGREGATE    |      |     1 |     5 |            |          |
|* 2 |   TABLE ACCESS FULL| B    |   110K|   541K| 3691   (1)| 00:00:45 |
Predicate Information (identified by operation id):
   2 - filter("B"."ID"<=200903 AND "B"."ID">=200810)
14 rows selected.
SQL> explain plan for select count(*) from b where b.dt between to_date(200810, 'YYYYMM') and to_date(200903, 'YYYYMM') ;
Explained.
SQL> select * from table(dbms_xplan.display) ;
PLAN_TABLE_OUTPUT
Plan hash value: 749587668
| Id | Operation          | Name | Rows | Bytes | Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT   |      |     1 |     8 | 3693   (1)| 00:00:45 |
|   1 | SORT AGGREGATE    |      |     1 |     8 |            |          |
|* 2 |   TABLE ACCESS FULL| B    | 58680 |   458K| 3693   (1)| 00:00:45 |
Predicate Information (identified by operation id):
   2 - filter("B"."DT"<=TO_DATE('2009-03-01 00:00:00', 'yyyy-mm-dd
              hh24:mi:ss') AND "B"."DT">=TO_DATE('2008-10-01 00:00:00', 'yyyy-mm-dd
              hh24:mi:ss'))
16 rows selected.
SQL> exec dbms_stats.gather_table_stats(user, 'B') ;
PL/SQL procedure successfully completed.
SQL> select column_name, num_distinct, num_buckets, histogram from user_tab_col_statistics where table_name = 'B' ;
COLUMN_NAME                    NUM_DISTINCT NUM_BUCKETS HISTOGRAM
ID                                      289         254 HEIGHT BALANCED
DT                                      289           1 NONE
SQL> explain plan for select count(*) from b where b.id between 200810 and 200903 ;
Explained.
SQL> select * from table(dbms_xplan.display) ;
PLAN_TABLE_OUTPUT
Plan hash value: 749587668
| Id | Operation          | Name | Rows | Bytes | Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT   |      |     1 |     5 | 3690   (1)| 00:00:45 |
|   1 | SORT AGGREGATE    |      |     1 |     5 |            |          |
|* 2 |   TABLE ACCESS FULL| B    | 46303 |   226K| 3690   (1)| 00:00:45 |
Predicate Information (identified by operation id):
   2 - filter("B"."ID"<=200903 AND "B"."ID">=200810)
14 rows selected.
SQL> explain plan for select count(*) from b where b.dt between to_date(200810, 'YYYYMM') and to_date(200903, 'YYYYMM') ;
Explained.
SQL> select * from table(dbms_xplan.display) ;
PLAN_TABLE_OUTPUT
Plan hash value: 749587668
| Id | Operation          | Name | Rows | Bytes | Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT   |      |     1 |     8 | 3692   (1)| 00:00:45 |
|   1 | SORT AGGREGATE    |      |     1 |     8 |            |          |
|* 2 |   TABLE ACCESS FULL| B    | 56797 |   443K| 3692   (1)| 00:00:45 |
Predicate Information (identified by operation id):
   2 - filter("B"."DT"<=TO_DATE('2009-03-01 00:00:00', 'yyyy-mm-dd
              hh24:mi:ss') AND "B"."DT">=TO_DATE('2008-10-01 00:00:00', 'yyyy-mm-dd
              hh24:mi:ss'))
16 rows selected.
SQL> exec dbms_stats.gather_table_stats(user, 'B') ;
PL/SQL procedure successfully completed.
SQL> select column_name, num_distinct, num_buckets, histogram from user_tab_col_statistics where table_name = 'B' ;
COLUMN_NAME                    NUM_DISTINCT NUM_BUCKETS HISTOGRAM
ID                                      289         254 HEIGHT BALANCED
DT                                      289           1 NONE
SQL> exec dbms_stats.gather_table_stats(user, 'B', method_opt=>'FOR ALL COLUMNS SIZE SKEWONLY') ;
PL/SQL procedure successfully completed.
SQL> select column_name, num_distinct, num_buckets, histogram from user_tab_col_statistics where table_name = 'B' ;
COLUMN_NAME                 NUM_DISTINCT NUM_BUCKETS HISTOGRAM
ID                         289         254 HEIGHT BALANCED
DT                         289         254 HEIGHT BALANCED
SQL> explain plan for select count(*) from b where b.dt between to_date(200810, 'YYYYMM') and to_date(200903, 'YYYYMM') ;
Explained.
SQL> select * from table(dbms_xplan.display) ;
PLAN_TABLE_OUTPUT
Plan hash value: 749587668
| Id | Operation        | Name | Rows | Bytes | Cost (%CPU)| Time       |
|   0 | SELECT STATEMENT   |       |     1 |     8 | 3692   (1)| 00:00:45 |
|   1 | SORT AGGREGATE    |       |     1 |     8 |            |       |
|* 2 |   TABLE ACCESS FULL| B       | 27862 |   217K| 3692   (1)| 00:00:45 |
Predicate Information (identified by operation id):
   2 - filter("B"."DT"<=TO_DATE('2009-03-01 00:00:00', 'yyyy-mm-dd
           hh24:mi:ss') AND "B"."DT">=TO_DATE('2008-10-01 00:00:00', 'yyyy-mm-dd
           hh24:mi:ss'))
16 rows selected.
SQL> explain plan for select count(*) from b where id between 200810 and 200903 ;
Explained.
SQL> select * from table(dbms_xplan.display) ;
PLAN_TABLE_OUTPUT
Plan hash value: 749587668
| Id | Operation        | Name | Rows | Bytes | Cost (%CPU)| Time       |
|   0 | SELECT STATEMENT   |       |     1 |     5 | 3690   (1)| 00:00:45 |
|   1 | SORT AGGREGATE    |       |     1 |     5 |            |       |
|* 2 |   TABLE ACCESS FULL| B       | 32505 |   158K| 3690   (1)| 00:00:45 |
Predicate Information (identified by operation id):
   2 - filter("ID"<=200903 AND "ID">=200810)
14 rows selected.

Need to use production schedule in OPM without ASCP,APS and VCP.

Hi Folks,
Pls suggest me the options to work on PS for OPM in R12 without using ASCP,APS and VCP.Client is not interested to go for ASCP.I just need to run the schedule and show him how the alternate resource works.Kindly throw me the options which will be best to take it forward.
Regards,
Arul

Hi Partha,
My client does not want the ASCP,APS and value chain planning.The option which you provide also cannot pull the data to EBS which is currently in ER as per Oracle.
Any other functionality which can be used which will help my client.
Regards,
Arul

ASCP Collections spawned Refresh Collection Snapshot taking longer

Hello Experts,
In a decentralized deployment, Refresh Snapshots spawned by ASCP Collections takes longer than the refresh snapshot launched as standalone request.
It looks like the program runs for long on the following queries
SELECT bic.component_item_id,
bic.component_quantit y
FROM MRP_SN_BOMS bom,
MRP_SN_INV_COMPS bic,
MTL_SYSTEM_ITEMS msi1,
MTL_SYSTEM_ITEMS msi2
WHERE bom.assembly_item_id =
:inventory_item_id
AND bom.organiz ation_id = :organization_id
AND msi1.inventory_item_id = bo
m.assembly_item_id
AND msi1.organization_id =
bom.organizat ion_id
AND bom.alternate_bom_designator IS NULL
AND b ic.bill_sequence_id =
bom.common_bill_sequence_id
AND bic.e ffectivity_date <
:g_scheduled_completion_date
AND NVL(bic .disable_date, :g_scheduled_completion_date + 1) >
:g_scheduled_completion_date
AND bic.WIP_ SUPPLY_TYPE = 6
AND msi2.inventory_item_id =
bic.component_ item_id
AND msi2.organization_id =
msi1.organization_id A ND NOT (msi1.AUTO_CREATED_CONFIG_FLAG='Y'
AND msi1.base_item_id IS NOT NULL
AND (msi2.BOM_ITEM_TYPE = 1
OR msi2.BOM_ ITEM_TYPE = 2))
SELECT ORGANIZATION_ID,
PLANNED_QUANTITY,
PRIMARY_ITEM_ID,
QUANTITY_COMPLETED,
SCHEDULED_COMPLETION_DATE,
SCHEDULED_START_DATE,
WIP_ENTITY_ID,
RN
FROM MRP_SN_FLOW_SCHDS
WHERE RN >= -1
AND PLANNED_QUANTITY > QUANTITY_COMPLETED
And the data volume seems very small, we have 30K items , less than
250 resources, no BOM.
If we run the Refresh collection snapshot as a standalone request on
Source/EBS instance, it completes in less than 5 mins. Only when it is
launched vial collections/db link, we are seeing this performance
issue.
We are on 12.1.3.4.
DBAs are not willing to modify the init.ora parameter mvrefresh_use_stats unless this is very specific.
Any help on this would be very helpful.
Regards
Sudeep

Is this issue resolved? If not can you throw some more information along the below questions.
Is the planning manager up and running? What about the firm planned flag? Is there any open quantity on job to be completed? Does this job show up on the view supply/demand screen on the txn instance?
Thanks,
Karthik

Oracle ASCP collections and planning

Similar Messages

Maybe you are looking for