R12.2.X – Materialized Views Migration/Implementation in R12.2.X

 

1. Drop the existing Materialized view and underlying table of the materialized view

DROP MATERIALIZED VIEW XXCUST.XXCUST_TEST_MV;

 

 

2. Create the Logical View in your development database.

The Logical View name must be the desired materialized view name with a '#' character appended to it.

A materialized view name must be unique within the first 29 bytes.

A materialized view definition must be stored in an ordinary view called MV_NAME||'#'.

A materialized view definition must specify a column alias for each item in the select list.[minimal]

• Failure to specify a column alias may cause the error ORA-00998 "must name this expression with a column alias".
• Example:

SELECT SUM (EMP.SALARY) AS SUM_EMP_SALARY,

       MIN (EMP.empno) AS MIN_EMP_NUM,

       'XX' || 'YY' AS XXYY

  FROM TEST_EMP EMP

 

 

Logical View Creation Example:

                CREATE OR REPLACE VIEW XXCUST.XXCUST_TEST_MV#

AS

   SELECT UPPER (oracle_username) USERNAME,

          DECODE (read_only_flag,'C','pub','E','applsys','U','apps') USERTYPE

     FROM fnd_oracle_userid

    WHERE read_only_flag IN ('C','E','U');

 

Test the materialized view definition for accuracy before generating the materialized view implementation

SELECT * FROM XXCUST.XXCUST_TEST_MV#;

 

 

3. Generate the Materialized View.

On an editioned database, materialized views are generated from their corresponding logical views using the AD_ZD_MVIEW.UPGRADE procedure.

• Do not attempt to directly create or replace the materialized view implementation. To recreate a materialized view implementation, call the AD_ZD_MVIEW.UPGRADE procedure.

BEGIN

      AD_ZD_MVIEW.UPGRADE('XXCUST', 'XXCUST_TEST_MV');

      COMMIT;

END;

 

 

In this example, the UPGRADE procedure detects that materialized view is missing and generates it from the Logical View. The Materialized View definition is generated by transforming the Logical View query into an equivalent implementation query that directly references the underlying tables and columns.

 

These 4 Rows get created in the process for

·         Logical View (Ending with '#') in Custom Schema

·         Materialized View in Custom Schema

·         Table in Custom Schema

·         Synonym in APPS

 

SELECT object_type, object_name

FROM dba_objects

WHERE object_name like 'XXCUST_TEST_MV%';

4.       Use the ALTER MATERIALIZED VIEW statement to modify an existing materialized view in one or more of the following ways:

·         To change its storage characteristics

·         To change its refresh method, mode, or time

·         To alter its structure so that it is a different type of materialized view

·         To enable or disable query rewrite

 

ALTER MATERIALIZED VIEW XXCUST.XXCUST_TEST_MV REFRESH FORCE ON DEMAND USING TRUSTED CONSTRAINTS DISABLE QUERY REWRITE;

/

 

5.       If the referenced objects are be placed in a non editioned schema that is different from the schema where the mview is to be created, then grant execute permission on the package to the mview owner.References:
12.2 E-Business Suite Upgrade Of Custom Materialized Views Fails Due To Changes Required For 12.2 ADOP Editioned Objects (Doc ID 2205375.1)
ORA-38818: Illegal Reference To Editioned Object When Creating Materialized View (Doc ID 1556379.1)

 

A materialized view should use 'REFRESH FORCE' instead of 'REFRESH FAST'. The 'FORCE' option allows the materialized view to fall back to using a complete refresh in situations where the fast refresh is not possible.

 

If the materialized view implementation content must be automatically refreshed after patching, then you must include the '/*AUTOREFRESH*/' comment tag in the materialized view definition query.

o    Do not specify the /*AUTOREFRESH*/ tag for large materialized views that will take a long time to refresh. For these cases use a concurrent program to refresh the materialized view after patching cutover.

• Example: create or replace view XXCUST_TEST_MV# as select /*AUTOREFRESH*/ ... ;

 

BEGIN 

      DBMS_MVIEW.REFRESH('XXCUST.XXCUST_TEST_MV','C',ATOMIC_REFRESH=>TRUE);

END;

/

 

Parameters in detail:

Refresh Method	Parameter	Description
COMPLETE	C	Refreshes by recalculating the defining query of the materialized view.
FAST	F	Refreshes by incrementally applying changes to the materialized view.
		For local materialized views, it chooses the refresh method which is estimated by optimizer to be most efficient. The refresh methods considered are log-based FAST and FAST_PCT.
FAST_PCT	P	Refreshes by recomputing the rows in the materialized view affected by changed partitions in the detail tables.
FORCE	?	Attempts a fast refresh. If that is not possible, it does a complete refresh. For local materialized views, it chooses the refresh method which is estimated by optimizer to be most efficient. The refresh methods considered are log based FAST, FAST_PCT, and COMPLETE.

 

 

6.       Create a comment to an oracle Materialized view

COMMENT ON MATERIALIZED VIEW XXCUST.XXCUST_TEST_MV IS 'snapshot table for snapshot XXCUST.XXCUST_TEST_MV ';

Oracle Reimplement vs Upgrade?

Reimplement vs. Upgrade?

The first and ultimate business decision for companies considering an upgrade is the decision whether to upgrade or reimplement. An upgrade would involve taking the current EBS environment and upgrading it and all the data in it to the newer versions. A reimplementation involves installing the new version of EBS and performing setups and data conversions in the new version, leaving the old version to die a natural death. Every major release (10.7 to 11.0 or 11i, 11.0.x to 11i, and now any prior version to R12) has companies wondering which the better option is.

A good starting point is to understand what Oracle’s plans are for your current release as well as for future releases. The current statement is that for 11.5.10, Oracle will provide all support except integration with new non-Oracle products, through November 2012. Accordingly, the more stable, older release, 11.5.10, may be a viable option for your organization when you are upgrading from an older version and the functionality in R12 will not benefit your business processes.

Some key changes in the core modules to R12 may make the more expensive upgrade to R12 worth the extra time and expense. Access to multiple Ledgers in the General Ledger is one of them, and the need to account for transactions in different ways is another. If your business processes are complicated and global enough that two representations are required for government and corporate reporting, this is a strong feature in R12 that is not as comprehensive in 11i.

Another major area for consideration is centralized and decentralized processes. R12 has done a nice job of allowing for both in the same organization and module. Prior to R12, EBS segregated all transactions for subledgers such as Receivables and Payables into separate organizations, requiring users to access each organization separately, making truly centralized processing cumbersome. Now, entries can be done into multiple operating units from the same responsibility without the segregation. Payment process also has a new centralized hub allowing payment processing and bank accounts to be combined for multiple organizations. Once you’ve decided on a version, consider a few significant points that can help make the decision whether to upgrade or reimplement a little clearer.

Differences between R12 & 11i.5.10 New R12 Features Upgrade Assessment

1. Differences between R12 & 11i.5.10 New R12 Features Upgrade Assessment

2. Upgrade to R12 – Pros and Cons Pros:

o Sub-ledger Accounting – The new Oracle Sub-ledger Accounting (SLA) architecture allows users to customize the standard Oracle accounting entries. As a result of Cost Management's uptake of this new architecture, users can customize their accounting for Receiving, Inventory and Manufacturing transactions.

o Enhanced Reporting Currency (MRC) Functionality – Multiple Reporting

Currencies functionality is enhanced to support all journal sources.

Reporting sets of books in R12 are now simply reporting currencies. Every journal that is posted in the primary currency of a ledger can be automatically converted into one or more reporting currencies.

o Deferred COGS and Revenue Matching – R12 provides the ability to automatically maintain the same recognition rules for COGS and revenue for each sales order line for each period. Deferred COGS and Deferred Revenue are thus kept in synch.

Cons:

o Resources – Availability of knowledgeable resources

o Maturity – Though R12 is around since 2007, not all the modules are mature enough meaning modules like E-B Tax have many bugs being fixed by Oracle development.

o Integration with customized applications – In a customized environment, all the extensions & interfaces need to be analyzed because of the architectural changes in R12.

3. R12 Features and differences with 11.5.10 – Inventory / Cost Management

o Multi-Organization Access Control (MOAC) - Multi-Org Access Control enables uses to access multiple operating units data from single responsibility. Users can access reports , Concurrent programs , all setup screens of multiple operating units from single responsibility without switching responsibilities.

o Unified Inventory - R12 merges Oracle Process Manufacturing OPM

Inventory and Oracle Inventory applications into a single version . So

OPM users can leverage the functionalities such as consigned & VMI and center led procurement which were available only to discrete inventory in 11i.5.10.

o Inventory valuation Reports -There are a significant number of reports which have been enhanced in the area of Inventory Value Reporting

o Inventory Genealogy - Enhanced genealogy tracking with simplified, complete access at the component level to critical lot and serial information for material throughout production.

o Fixed Component Usage Materials Enhancement – Enhanced BOM setup screen and WIP Material Requirement screen that support materials having a fixed usage irrespective of the job size for WIP Jobs, OSFM lotbased jobs, or Flow Manufacturing

o Component Yield Enhancements - New functionality that provides flexibility to control the value of component yield factors at WIP job level.

This feature allows the user to include or exclude yield factor while calculating back flush transactions.

o Periodic Average Cost Absorption Enhancements – Enhanced functionality for WIP Final Completion, WIP Scrap Absorption, PAC WIP Value Report, Material Overhead Absorption Rule, EAM work order, and PAC EAM Work Order Cost Estimate Processor Report.

o Component Yield benefits - Component yield functionality user have the flexibility to control the value of component yield factors and use those factors for back flush transactions. Of course if the yield factor is not used, yield losses can be accounted for using the manual component issue transaction.

New Features:

4. R12 Features and differences with 11.5.10 – Advanced Procurement Suite

o Professional Buyer’s Work Center – To speed up buyers’ daily purchasing tasks – view & act upon requisition demand, create & manage orders and agreements, run negotiation events, manage supplier information.

o Freight and Miscellaneous Charges – New page for viewing acquisition

cost to track freight & miscellaneous delivery cost components while

receiving. Actual delivery costs are tracked during invoice matching.

o Complex Contract Payments – Support for payments for services related procurement including progress payments, recoupment of advances, and retainage.

o Unified Inventory – Support for the converged inventory between Oracle Process Manufacturing – OPM Inventory & Oracle Inventory.

o Document Publishing Enhancements – Support for RTF & PDF layouts and publish contracts using user specified layouts

o Support for Contractor Purchasing Users – Support for contingent workers to create & maintain requisitions, conduct negotiations, and purchase orders.

New Features:

5. R12 Features and differences with 11.5.10 – Order Management

o Multi-Organization Access Control (MOAC) - Multi-Org Access Control enables uses to access multiple operating units data from single responsibility. Users can access reports , Concurrent programs , all setup screens of multiple operating units from single responsibility without switching responsibilities. They can also use Order Import to bring in orders for different Operating Units from within a single responsibility.

The same applies to the Oracle Order Management Public Application Program Interfaces (APIs).

o Post Booking Item Substitution - Item Substitution functionality support has been extended to post-Booking through Scheduling/re-scheduling in Sales Order, Quick Sales Order, and Scheduling Order Organizer forms. Item Substitution functionality is also supported from Planner’s Workbench (loop-back functionality) till the line is pick-released.

o Item Orderability - Businesses need the ability to define which customers are allowed to order which products, and the ability to apply the business logic when the order is created.

o Mass Scheduling Enhancements – Mass Scheduling can now schedule lines that never been scheduled or those that have failed manual scheduling. Mass Scheduling also supports unscheduling and rescheduling

o Exception Management Enhancements – Improved visibility to workflow errors and eases the process of retrying workflows that have experienced processing errors

o Sales Order Reservation for Lot-Based Jobs – Lot-Based Jobs as a Source of Supply to Reserve Against Sales Order(s). OSFM Displays Sales Order Information on Reserved Jobs

o Cascading Attributes – Cascading means that if the Order header attributes change, the corresponding line attributes change

o Customer Credit Check Hold Source Support across Operating Units - Order Management honors credit holds placed on customers from AR across operating Units. When Receivables places a customer on credit hold a hold source will be created in all operating units which have:

 A site defined for that customer

 An order placed against that customer.

New Features:

6. R12 Features and differences with 11.5.10 – Shipping

o Pick Release/Confirm Features

 Pick Release enhancements - Enhancements will be made to the Release Sales Order Form and the Release Rules Form to support planned crossdocking and task priority for Oracle Warehouse Management (WMS) organizations. Pick release will allow a user to specify location methods and if crossdocking is required, a cross-dock rule. The task priority will be able to be set for each task in a sales order picking wave when that wave is pick released.

The priority indicated at pick release will be defaulted to every Oracle WMS task created

 Parallel Pick Release Submission - This new feature will allow users to run multiple pick release processes in parallel to improve overall performance. By distributing the workload across multiple processors, users can reduce the overall time required for a single pick release run.

o Workflow Shipping Transaction Enhancement – Oracle has enabled Workflow in the Shipping process for: workflow, process workflow, activity and notification workflow, and business event

o Support for Miscellaneous Shipping Transactions - Oracle Shipping Execution users will now be able to create a delivery for a shipment that is not tied to a sales order via XML (XML-equivalent of EDI 940 IN). Once this delivery has been created, users will be able to print shipping documents, plan, rate, tender, audit and record the issuance out of inventory. Additionally, an XML Shipment Advice (XML- equivalent of EDI 945 OUT) will be supported to record the outbound transactions.

o Flexible Documents: With this new feature ,Shipping Execution users will be able to create template-based, easy-to-use formats to quickly produce and easily maintain shipping documents unique to their business. Additional attributes will be added to the XML templates for each report for added flexibility

o Enhanced LPN Support - Oracle Shipping Execution users will now have improved visibility to the Oracle WMS packing hierarchy at Pick Confirmation. The packing hierarchy, including the License Plate Number (LPN), will be visible in the Shipping Transactions form as well as in the Quick Ship user interface.

New Features:

7. R12 Features and differences with 11.5.10 – Warehouse Management

o Crossdock Execution – WMS allow you to determine final staging lane, merge with existing delivery or create a new delivery, synchronize inbound operation plan with outbound consolidation plan, enhance outbound consolidation plans and manage crossdock tasks.

o Labor Management – WMS provides labor analysis. It gives the warehouse manager increased visibility to resource requirements. Detailed information for the productivity of individual employees and warehouses is provided

o Warehouse Control Board Additions - Additional Task selection criteria

o User Extensible Label Fields – WMS, users are now able to add their own variables without customizing the application, by simply defining in SQL the way to get to that data element

o Material Consolidation across deliveries – WMS allows you to consolidate material across deliveries in a staging lane

New Features:

8. R12 Features and differences with 11.5.10 – OSFM

o Lot and Serial Controlled Assembly– Lot controlled job can now be associated with serial numbers to track and trace serialized lot/item during shop floor transactions as well as post manufacturing and beyond

o Fixed Component Usage Support for Lot Based Jobs – OSFM now supports fixed component usage defined in the Bill of Material of an end it.

o Support for Partial Move Transactions – Users are able to execute movement of a partial job quantity interoperation

o Enhanced BOM to Capture Inverse Usage – Users can now capture the inverse component usage through the new inverse usage field in BOM UI

o Support for Rosetta Net Transaction - comprising of 7B1 (work in process) and 7B5 (manufacturing work order).

New Features:

9. R12 – Further Info…

o The latest RCD (Release Content Documents) can be accessed from the metalink note 404152.1 (requires user name & password).

o The TOI (Transfer Of Information) sessions released by Oracle Learning can be accessed from its portal at http://www.oracle.com/education/oukc/ebs.html

o Oracle White papers – Extending the value of Your Oracle E-Business Suite 11i.10 Investment & Application Upgrades and Service Oriented Architecture

R12 Further Info – RCD & TOI