Saturday, October 17, 2009

Setup Steps – Order Mangement


Setup Steps – Order Mangement

Step 1: Multiple Organizations
Step 2: Multi-Org Access Control
Step 3: Flexfields
Step 4: Inventory Organizations
Step 5: Profile Options
Step 6: Parameters
Step 7: Invoicing
Step 8: Salespersons
Step 9: Tax
Step 10: QuickCodes
Step 11: Workflow
Step 12: Document Sequences (Order Numbering)
Step 13: Order Import Sources
Step 14: Units of Measure
Step 15: Item Information
Step 16: Items
Step 17: Configurations
Step 18: Pricing
Step 19: Customer Classes
Step 20: Customers
Step 21: Item Cross References
Step 22: Sourcing
Step 23: Order Management Transaction Types (Sales Documents)
Step 24: Cost of Goods Sold (COGS)
Step 25: Processing Constraints
Step 26: Defaulting Rules
Step 27: Credit Checking
Step 28: Holds
Step 29: Attachments
Step 30: Freight Charges and Carriers
Step 31: Shipping

Monday, June 15, 2009

How does one setup Multi Org Access Control (MOAC) in Order Management for R12?

General MOAC Setup:

1. Define the Security Profile in HRMS:

a. Using HRMS Management responsibility

b. Navigate to: HRMS Manager > Security > Profile

c. Verify that the Security Profile is defined (for the OM responsibility or site level)

d. If it is not yet setup, enter it and attach the Operating Units

e. SAVE

NOTE: If you created a new security profile in 'd' above, you MUST run the concurrent program 'Security List Maintenance' or the multiple operating units will not appear in the LOV in the OM forms. This program populates a table that is used for validating multi-org access.

Navigation: HRMS Management > HRMS Manager > Processes & Reports > Submit Process & Report > Security List Maintenance
2. Setup MO Profile Options:

a. MO: Security Profile - Setting this profile enables MOAC functionality

b. MO: Default Operating Unit - This Operating Unit will default into OM forms and reports. You can use the LOV to clear it or change it.

Keep the MO profiles in sync:

MO: Security Profile is settable at both the site and responsibility level.

MO: Default Operating Unit is settable at the site, responsibility and user level.Verify the settings of these profiles if you find the application not behaving as expected.

3. OM Setup:

Review new OM System Parameters migrated from OM Profiles with R12 upgrade: Order Management Super User > Setup > System Parameters > Values


4. Enable hidden field 'Operating Unit' in forms and save as default folder:
Sales Order and Order Organizer forms

Quick Sales order and Organizer forms

Sales Agreement forms

Pricing and Availability form

Other forms

How Can One Use The Same Price List For Order Management And Purchasing?

How Can One Use The Same Price List For Order Management And Purchasing?

Yes, this is possible if one associates Advanced Pricing with Purchasing as follows:

1. Responsiblity: Oracle Pricing Manager

2. Navigate to: Setup > Attribute Management > Pricing Transaction Entity Association.

3. Do a FIND on: Name = PO It will show one line for code = PO.

4. Add a line as follows: Code = QP (defaults description = Advanced Pricing) Ensure that "enabled" is checked. Save.

5. Switch to the purchasing responsibility.

6. Navigate to Price List > Price List Setup Query the price list created and uncheck the 'active' checkbox. Save.

7. Please retest and the price is now returned from the price list created in Order Management.

Order Import Interface Tables

OE_HEADERS_IFACE_ALL

OE_LINES_IFACE_ALL

OE_PRICE_ADJS_IFACE_ALL

OE_PRICE_ATTS_IFACE_ALL

OE_CREDITS_IFACE_ALL

OE_LOTSERIALS_IFACE_ALL

OE_RESERVTNS_IFACE_ALL

OE_ACTIONS_IFACE_ALL

OE_CUSTOMER_INFO_IFACE_ALL

OE_PAYMENTS_IFACE_ALL

Order Management tables

Order Management related tables
Entity Related Table Name
----------------------------- ------------------------
Order Header OE_ORDER_HEADERS_ALL
Order Price Adjustments OE_PRICE_ADJUSTMENTS
Order Sales Credits OE_SALES_CREDITS
Order Line OE_ORDER_LINES_ALL
Order Pricing Attributes OE_ORDER_PRICE_ATTRIBS
Order Adjustment Attributes OE_PRICE_ADJ_ATTRIBS
Order Adjustment Associations OE_PRICE_ADJ_ASSOCS
Line Sales Credits OE_SALES_CREDITS
Line Price Adjustments OE_PRICE_ADJUSTMENTS
Line Pricing Attributes OE_ORDER_PRICE_ATTRIBS
Line Adjustment Attributes OE_PRICE_ADJ_ATTRIBS
Line Adjustment Associations OE_PRICE_ADJ_ASSOCS
Lot Serial Numbers OE_LOT_SERIAL_NUMBERS

Thursday, June 11, 2009

Oracle Pricing

Oracle Pricing engine determines the selling prices for products and services. It provides answers to the following questions:
1) Who qualifies for prices and benefits?
2) What is the item or service, which is being priced or modified?
3) How do we adjust the order price or the order line price?
How it works?Oracle Advanced Pricing prices any transaction by first identifying a list price which contains the list price. The pricing engine (Qualifiers) then determines whether the price found on the price list have to be adjusted or not. Modifiers control the amount of these adjustments, and can modify a price by either giving a discount or adding a surcharge. Once the pricing engine has selected one or more modifiers that adjust the price, it computes the final selling price.
"Price List" contains price for items and/ or services. You could have multiple price list for the same items/service. For example: Standard Price List, Summer Promotion Price List, Festival price list.
"Qualifiers" determine who is eligible for a price or modifier list. For example: Order Type, Customer Class, Customer Site and Customer Name.
"Pricing Attribute" determines what is being priced or modified on a price or modifier list. For example: Item Category, Product Brand, Location, Distance, Age and Volume.
"Modifiers" determines how the eligible item/service is priced. For example, Discounts, Surcharges, Coupon Issue, Item Upgrade, Terms Substitution, Freight Charge, Promotional Goods.
With all the above inputs, Pricing Engine calculates the final Price which is equal to the original price on the price list minus any eligible discounts, plus any other applicable surcharges or promotionsOracle Pricing is flexible to occupy various combinations to suit the business needs.
For example:
-Price List A is for Product X and applicable for Customer ABC.
- Price List B is for All Products and applicable for All Customer.
- Price List C is for all products belonging to Item Category A and B and applicable for All Customers

Supply types in Oracle WIP?

Supply types decides the method of supplying component materials to discrete jobs and repetitive schedules in WIP module. It also controls how materials are planned in MS/MRP module and how materials are costed in Cost Management module.You can assign supply types to the items when you define in Inventory module. You can also assign supply types to components when you create bills of material in Bills of Material and Engineering modules. The following is a list of the WIP supply types and the way they work:

a) Push

Push components can be manually issued directly to discrete jobs and repetitive schedule as per requirements. You can specify the subinventory for items in Item definition form or in Bills or define default subinventory in WIP parameters form. Work in Process defaults the supply subinventory associated with the component.

b) Operation Pull:

Operation pull components that are assigned to backflush operations, are automatically backflushed (pulled) from inventory and issued to discrete jobs and repetitive schedules when assemblies are moved and completed at that operation i.e. when you complete backflush operations. Also, operation pull component that have not been backflushed because they are assigned to non-backflush operations prior to the backflush operation are also backflushed. The Components are pulled from the supply subinventory assigned to the component. You cannot assign this supply type to an assenbly without a routing or a non-standard discrete job without a routing. You can assign this supply type to assemblies that have routings with no operations or when the routing has disabled operations. However, all components with a supply type of operation pull are automatically changed to assembly pull.

c) Assembly pull:

Assembly Pull components are issued (backflushed) to discrete jobs and repetitive schedules when you complete all operations on assemblies in Work in Process. They are pulled from the supply subinventory assigned to the component requirement.If you want to assign pull components to a bill of material or job that is not associated with a routing, you must assign an Assembly Pull supply type, rather than operation pull supply type. You cannot assign this supply type to a non-standard discrete job if you have not specified an assembly or bill of material reference for that non standard discrete job.

d) Based on Bill:

When you define a discrete job or a repetitive line/assembly association in WIP, the supply type for the assembly defaults to Based on Bill and assembly components are supplied based upon their bill of material supply types. You can change the defaulted Based on Bill supply type that is assigned to jobs and schedules as you define them. The Based on Bill supply type is WIP specific.If the supply type for a job or line/assembly association is changed, the new supply type is applied to all component material requirements. For example, if you change the supply type of a job assembly from Based on Bill to Assembly Pull, the supply types of all assembly components are changed to Assembly pull. You can update the supply types of individual material requirements using the Material Requirements window in WIPThe system automatically changes components with a supply type of Operation Pull to Assembly Pull, when the Based on Bill supply type is applied to a job or repetitive job/ schedule that has a bill of material but has no a routing or operations.

e) Bulk:

Bulk component requirements can be viewed and are displayed on reports and inquiry forms (that display components requirements) when you include Bulk components on a bill of material. They can be used to communicate to the shop floor that bulk components must be used but need not be transacted. You can choose specific components in the type field of WIP material transaction form for issuing bulk components.Bulk components are not backflushed nor do they default when issuing all components for an assembly. You can, however, manually issue specific bulk components to a discrete job or repetitive schedule. This supply type is selected for components like screws,nuts,bolts,nails,etc where it is difficult and may not be necessary to transact the exact quantity used.

f) Supplier/Vendor:

Supplier component requirements can be included on bills of material. Requirements for supplier components are created when you define discrete jobs and repetitive schedules in Work in Process. Supplier component requirements can be viewed and are displayed on reports. They provide information on the component materials that your suppliers provide but need not be transacted. Supplier components are not backflushed nor do they default when issuing all components for an assembly. You can, however, manually issue specific supplier components to discrete jobs and repetitive schedules/job.

g) Phantoms:

Phantom components can be assigned to bill of material component subassemblies and subassembly items in BOM and Engineering. Components of phantom subassemblies are used as if they were tied directly to the parent assembly. Phantom supply types cannot be assigned to jobs and repetitive lines/assembly associations in Work in Process. When model or option class bills are components to another bill of material, that component supply type is phantom.

Phantoms behave normally when they are top level assemblies, such as when master scheduled or manufactured on a discrete job. As subassemblies, they lose their distinct identity and become a collection of their components. Phantom components (not the phantom itself) are included on discrete jobs and repetitive job/schedules and are listed on the Discrete Job and Repetitive Schedule Pick List Reports.