11i Vs R12

Being currrently there is a good acceptance for the R12 implementation,the general question in the mind of Client and the implementor are as follows:

11i really needs to be updated?
wats new in r12?
Implementation strategy for r12?
Organization architecture in R12?

To answer all the question and go ahead with r12 the Client should be clear in his requirement and the Implemantors should be aware of the new product(r12) in depth.

The major fear in R12 is due to various reasons as such the main factor is lack of exposure.

The R12 has various development comparatively in the areas of organization architecture,modulewise enhancement and shift of various Form into HTML based pages.

The Legal entity is given more importance to address multidimensional requirements.

The Set of Books 3 c concept is added with a additional parameter.

OU has its ease link from the Accounting environment.

The Suppliers and Customers are given a new look from form to pages.
The centralized parties are introduced.

In short the R12 is stepping to new face, hope to sink it in Fusion.

Hail to Oracle application Continous Improvement!!!!!!!!!!!!!!!!!!!!!

Oracle Apps Key Flex Field (a) KFF

As the name explains in Oracle KFF is a field which is flexible to be structured as per the requirement of the Business.One has to know well abt the KFF before building the system. KFF is a critical setup and many of them are irreversible.There are totally 38 KFF available acroos all Modules.

Key points to be noted in the KFF are as follows

Which application doesit belong to?

How many structure allowed?

Possibility of Dynamic insert

To be More clear about the Basic KFF for a functional consultant, lets move into some of the specific KFF and its application.

Application: Inventory

1) System Item flexfield
2) Item Categories
3) Item Catalogs
4) Sales Orders
5) Stock Locators
5) Account Aliases

Application: General Ledger

1) Accounting Flexfield
2) GL Ledger Flexfield ---> This is a additional KFF in R12
3) Reporting Attributes:Accountin

Application: Assets

1) Asset Key Flexfield
2) Category Flexfield
3) Location Flexfield

Application: Human Resources

1) Competence Flexfield
2) Grade Flexfield
3) Job Flexfield
4) Position Flexfield

Application: Payroll

1) Cost Allocation Flexfield
2) People Group Flexfield


Hint For INV implementation: System Item KFF is a critical thing to be taken care and the number of segment will decide the entire Item transaction across all modules.
Adviceable is to restrict the number of Segment inSystem Item KFF

Attribute Determines the Item

Defining a Item is not just naming a physical or logical object, but inturn assigning various properties to it.In oracle its termed as Attributes, the attibute is the one which determines the nature of a Item.So every consultant should now the significance of the item, item category and organization assignment.Let me share the key attributes in each functional areas for now.

Main

1. Primary Unit of Measure
2. User Item Type
3. Item Status
4. Conversions

Inventory

1. Inventory Item
2. Stockable
3. Transactable
4. Revision Control
5. Reservable
6. Check Material Shortage
7. Lot Expiration (Shelf Life) Control
8. Shelf Life Days
9. Lot Control
10. Starting Lot Prefix
11. Starting Lot Number
12. Cycle Count Enabled
13. Negative Measurement Error
14. Positive Measurement Error
15. Serial Generation
16. Starting Serial Prefix
17. Starting Serial Number
18. Locator Control
19. Restrict Subinventories
20. Restrict Locators

Bills of Material

1. BOM Allowed
2. BOM Item Type
3. Base Model
4. Engineering Item (Oracle Engineering only)
5. Effectivity Control

Costing

1. Costing Enabled
2. Inventory Asset Value
3. Include in Rollup
4. Cost of Goods Sold Account
5. Standard Lot Size

Purchasing

1. Purchased
2. Purchasable
3. Use Approved Supplier
4. Allow Description Update
5. RFQ Required
6. Outside Processing Item
7. Outside Processing Unit Type
8. Taxable
9. Receipt Required (Three-Way Invoice Matching)
10. Inspection Required (Four-Way Invoice Matching)
11. Default Buyer
12. Unit of Issue
13. Receipt Close Tolerance
14. Invoice Close Tolerance
15. UN Number
16. Hazard Class
17. List Price
18. Market Price
19. Price Tolerance
20. Rounding Factor
21. Encumbrance Account
22. Expense Account
23. Asset Category

Receiving

1. Receipt Date Action
2. Receipt Days Early
3. Receipt Days Late
4. Overreceipt Quantity Control Action
5. Overreceipt Quantity Control Tolerance
6. Allow Substitute Receipts
7. Allow Unordered Receipts
8. Allow Express Transactions
9. Receipt Routing
10. Enforce Ship-To

Physical Attributes

1. Weight Unit of Measure
2. Unit Weight
3. Volume Unit of Measure
4. Unit Volume
5. Container
6. Vehicle
7. Container Type
8. Internal Volume
9. Maximum Load Weight
10. Minimum Fill Percentage
11. Collateral Item
12. OM Indivisible

General Planning

1. Inventory Planning Method
2. Planner
3. Make or Buy
4. Min-Max Minimum Quantity
5. Min-Max Maximum Quantity
6. Minimum Order Quantity
7. Maximum Order Quantity
8. Order Cost
9. Carrying Cost Percent
10. Source Type (Replenishment)
11. Source Organization
12. Source Subinventory
13. Safety Stock Method
14. Safety Stock Bucket Days
15. Safety Stock Percent
16. Fixed Order Quantity
17. Fixed Days Supply
18. Fixed Lot Multiplier

MPS/MRP Planning

1. Planning Method
2. Forecast Control
3. Exception Set
4. Pegging
5. Shrinkage Rate
6. Round Order Quantities
7. Acceptable Early Days
8. Repetitive Planning
9. Overrun Percentage
10. Acceptable Rate Increase
11. Acceptable Rate Decrease
12. Calculate ATP
13. Reduce MPS
14. Planning Time Fence
15. Planning Time Fence Days
16. Demand Time Fence
17. Demand Time Fence Days
18. Release Time Fence
19. Release Time Fence Days

Lead Times

1. Preprocessing
2. Processing
3. Postprocessing
4. Fixed
5. Variable
6. Cumulative Manufacturing
7. Cumulative Total
8. Lead Time Lot Size

Work in Process

1. Build in WIP
2. Supply Type
3. Supply Subinventory
4. Supply Locator
5. Overcompletion Tolerance Type
6. Overcompletion Tolerance Value
Order Management
1. Customer Ordered
2. Customer Orders Enabled
3. Shippable
4. Internal Ordered
5. Internal Orders Enabled
6. OE Transactable
7. Pick Components
8. Assemble to Order
9. ATP Components
10. Ship Model Complete
11. Check ATP
12. ATP Rule
13. Picking Rule
14. Default Shipping Organization
15. Returnable
16. RMA Inspection Required
17. Over Shipment Tolerance
18. Under Shipment Tolerance
19. Over Return Tolerance
20. Under Return Tolerance

Invoicing

1. Invoiceable Item
2. Invoice Enabled
3. Accounting Rule
4. Invoicing Rule
5. Tax Code
6. Sales Account
7. Payment Terms

Service

1. Support Service
2. Warranty
3. Coverage
4. Service Duration
5. Billing Type
6. Serviceable Product
7. Service Starting Delay

Do Not Confuse Re engineering and ERP Implementation

Companies should separate reengineering modifications from ERP implementations

If a single word has dominated the world of business in the 1990's it is "reengineering" - a process that reforms business practices for optimum performance, customer service, and financial return. Teams are organized, studies are made, money is spent, and dreams are hatched, but for most companies, not that much changes. "Can-identify-the-problem" people far outnumber "can-solve-the-problem" people, so that problems are found but left unresolved, adding to workforce cynicism. In all this team problem-solving and supposed reforming, too many forget that changing business procedures is a complex activity. Some companies have implemented reengineering in a continually impoving environment, but most have abandoned reengineering as just another fad.

The theory behind reengineering is a good one - modifying procedures and behavior to the needs of the business. Most companies were implementing these type changes long before the term "reengineering" came into existence. Yet, a complete company overhaul is often beyond what companies are willing to tackle - the effort is too much and the impact too large. For this reason, companies should separate reengineering modifications from ERP implementations. Installing a broad-based ERP system is a complicated job involving a high level of risk, especially as it relates to cost and timing. Adding other factors that are complex in their own right, such as reengineering, can often doom a project.

IF the work processes to be used in an ERP system have not been established prior to trying to install one, "reengineering" should take place to establish the work processes to be used in such systems (i.e., Oraclle ,SAP R/3, etc.). It should take place "prior to and in preparation for" an ERP implementation - not in conjunction with, and should be in a state of continually updating as the dynamic enterprise must continually change to meet changing market demands.

Steps for Successful Implementation

Eight Steps for Success implementation

Whether the implementation involves a stand-alone software solution or is part of a larger project, one methodology that has proven successful includes eight distinct phases. Each phase has defined deliverables that must have executive sponsor and steering committee buy-in before the next phase can begin. These eight phases are;

1. Scoping.

This phase takes place immediately after the contractual agreement. The implementation team defines the scope and parameters of the project, establishes the metrics to measure progress, and sets up the communication and reporting process. Deliverables for this phase include a general outline of the implementation schedule and basic project milestones. An initial meeting engages all participants and builds enthusiasm, and concept education introduces the software's capabilities and expected benefits (the Kick-Off Meeting).

2. Analysis.

In this crucial phase, which typically takes about a month, the business environment and processes are examined and evaluated, and defined business and production goals are prioritized. Next, a definitive implementation timeline can be established. Deliverables for this phase include a formal vision statement of detailed objectives, and the implementation's Technical and Social Design.
The Technical Design. - details how the product and processes will be aligned to achieve the desired objectives.
The Social Design - considers the "people issues:" how workers perform their jobs, and how the implementation may change business practices, workflow, and reporting relationships.

3. Prototyping.

The goal of this phase is to build, test, assess, and refine the initial prototype. In most cases, the team identifies a portion of the plant or a product line on which to build this first iteration, which - depending on the business goals - may or may not include all of the application's functionality. When the prototype has been built, tested, and run, results are charted for performance and logic, and refinements are ongoing. The deliverable for this phase is a "project notebook" and prototype demonstrations for the executive sponsor, steering committee and key users. Additionally, the company's core team receives a greater degree of training in the software's architecture and technology, capabilities, maintenance, and usage.

4. Deployment.

Once the prototype has been refined and accepted, it's expanded and built to full production scale. This phase includes data gathering, process modeling, and adding the specified "bells and whistles" to the basic prototype. At this stage, supervisors and operators receive additional training regarding product performance and capabilities, and any business process changes that will affect them or their work groups.

5. Interface/Integration.

Occurring simultaneously with deployment, all necessary interfaces are designed and integration issues are resolved to ensure the software works in concert with other systems. Key deliverables include handing all files, specifications, upload/download and maintenance procedures over to the company's IS team, and ensuring that effective knowledge transfer took place.

6. Parallel Testing.

This phase involves complete simulation testing of the live system to validate its performance and the effectiveness of interfaces/integration. Its key deliverable is acceptance of test results.

7. Cutover.

Before cutover actually occurs, a strategy is devised to execute timely and effective rollout. The rollout itself may either be phased or performed all at once; the choice depends on which approach will disrupt business and production the least.

8. Continuous Improvement.

This is more of a philosophy than an actual phase. To ensure continuous improvement, a post-implementation audit should be performed after the system has been up and running for three to six months to test whether or not the anticipated ROI and business benefits are being realized. Comparing actual numbers with previously established benchmarks will reveal if the software tool does what it is intended to do - add value to the enterprise. This first audit should be performed by the implementation partner to give the business's IT team a "snapshot" of the company's post-implementation progress. After that, it is important to periodically review the system's performance to ensure continuous improvement for maximum ROI

Basic Elements in Form

Oracle Anniversary

Oracle's 30th Anniversary

Three Decades of Innovation:

Three decades ago, Larry Ellison, while routinely scanning the IBM Journal of Research and Development, discovered a research paper that described a working prototype for a relational database management system (RDBMS). Today, Oracle is the gold standard for database technology and applications in enterprises throughout the world, from the largest multinational corporations to the corner coffee shop. In honor of the company's anniversary, Profit spoke with a range of executives at Oracle's top ranks to get a snapshot of the company's culture and plans.

Get Ready For Fusion

Be aware of Release

To summarize what this Releases in E-Business Suite:

Oracle E-Business Suite Release 12 is the next major release after Release 11i

Release 12 has its own stream of updates, such as 12.1 and 12.x

Oracle Fusion is our next-generation enterprise applications suite, bringing together the best functionality and technology from of all Oracle applications.

How ERP Integrates?

Oracle Apps Product Line

Oracle E-Business SuiteThe E-Business Suite's Global Single Database (GSD) computing model leverages Oracle's world-class database technology to provide unparalled embedded analytic access, with Daily Business Intelligence (DBI), to a comprehensive business view of your enterprise across all geographic regions.
PeopleSoft Enterprise Tools and TechnologyPeopleSoft Enterprise tools and technology transform the way organizations implement, use, and maintain enterprise software. We offer an automated, highly flexible development environment; integration and business modeling tools; world-class usability; and predictive, customer system-specific diagnostic and support tools.
JD Edwards EnterpriseOne Tools and TechnologyThe JD Edwards EnterpriseOne Tools offer you a complete technology solution for running EnterpriseOne applications. Built around the concepts of flexibility and adaptability, EnterpriseOne Tools enable your business to adjust to changing business conditions.
JD Edwards WorldBuilt for the IBM iSeries platform, Oracle's JD Edwards World offers small businesses a reliable, functionality-rich, web-enabled environment for world-class management of plants, inventories, equipment, finances, and people. The applications function as a synchronized, integrated whole and are tightly integrated and pre-bundled on a single database.
SiebelOracle's Siebel CRM Technology provides the server framework to support Siebel Applications. It covers development, deployment, diagnostic and integration. In addition, productivity tools such as Outlook/Sharepoint Integration and Mobile Solutions allow you to drive your business processes from Outlook and mobilize your CRM application.

Wats ERP?

ERP stands for Enterprise Resource Planning. ERP is a way to integrate the data and processes of an organization into one single system. Usually ERP systems will have many components including hardware and software, in order to achieve integration, most ERP systems use a unified database to store data for various functions found throughout the organization.
The term ERP originally referred to how a large organization planned to use organizational wide resources. In the past, ERP systems were used in larger more industrial types of companies. However, the use of ERP has changed and is extremely comprehensive, today the term can refer to any type of company, no matter what industry it falls in. In fact, ERP systems are used in almost any type of organization - large or small.
In order for a software system to be considered ERP, it must provide an organization with functionality for two or more systems. While some ERP packages exist that only cover two functions for an organization (QuickBooks: Payroll & Accounting), most ERP systems cover several functions.
Today's ERP systems can cover a wide range of functions and integrate them into one unified database. For instance, functions such as Human Resources, Supply Chain Management, Customer Relations Management, Financials, Manufacturing functions and Warehouse Management functions were all once stand alone software applications, usually housed with their own database and network, today, they can all fit under one umbrella - the ERP system