Thursday 28 June 2012

Inventory consists


Inventory consists of, mainly
1. Raw material 
2. Work In Process Inventory
 3. Finished Goods Functions of inventory
  •  Maintaining stock
  •   Planning 
  •  Forecasting 
  •  Physical control of inventory
  •   Receipt 
  •  Issues We will discuss these functions as regards with oracle applications


Inventory Flexfields
The flexfields which are used in inventory are:
• Account aliases • Item catalogs • Item categories • Sales orders • Stock locators • System items Depending on your setup inventory can use other modules flexfields like Accounting (General Ledger) & Sales tax location & territory from Accounts Receivables
Account Aliases
Table name : MTL_GENERIC_DISPOSITIONS
An account alias is an easily recognized name or label representing a general ledger account number. You can view, report, and reserve against an account alias. During a transaction, you can use the account alias instead of an account number to refer to the account.
Item catalogs
Table name: MTL_ITEM_CATALOG_GROUPS Unique ID column: ITEM_CATALOG_GROUP_ID
If you make entries for your items in a standard industry catalog or want to group your items according to certain descriptive elements, you need to configure your Item Catalog Group Flexfield.
Even if you do not use item cataloging, you must enable at least one segment and compile this flexfields before you can define items.
These flexfields supports only one structure and dynamic inserts is not allowed.
Item categories
Table name: MTL_CATEGORIES Unique ID Column: CATEGORY_ID
You must define & configure your item categories flexfields before you can start defining items since all items must be assigned to categories. You can define multiple structures fro different category groups. So that you can associate these structures with categories & category sets.
Sales order
Table name: MTL_SALES_ORDERS Unique ID Column: SALES_ORDER_ID Through this flexfield inventory will identify sales order transactions of OM with
inventory. This sales order flexfield should be defined as order number, order type and order source so that each transaction will be unique in inventory.
Stock locators
Table name: MTL_ITEM_LOCATIONS Unique ID Column: INVENTORY_LOCATION_ID
If you keep track of specific locators such as aisle, row, bin indicators for your items, you need to configure your Stock Locators Flexfield and implement locator control in your organization.
You can use stock locators field to capture more information about stock locators in inventory. If you do not have oracle inventory installed any none of items have locator control then it is not necessary to define this flexfield.
And this flexfield supports only one structure.
System items (item flexfield)
Table name: MTL_SYSTEM_ITEMS And unique id column is INVENTORY_ITEM_ID
You can use item flexfield for recording and reporting your item information, and you must define and configure your item flexfield before you can start defining items.
You must plan how Oracle Inventory represents your company’s inventory sites and business units. This includes defining organizations, locations, subinventories, and locators depending on your company structure.
Inventory is consisting of inventory – subinventory -locators as per your organization setup.
ITEM is defined in inventory that is generally first in master organization, so that later it can be assign to multiple organizations. Also item definition can be uploaded by item upload open interface.
ITEM definition
You define items in one organization. To distinguish it from others, we call it the Item Master organization. Other organizations (child organizations) refer to the Item Master for item definition. After you define an item in the Item Master, you can assign it to any number of other organizations.
Item attributes
• inventory attributes like lot control/ serial control
 
• Purchasing and costing information. 
• bill of material/ item category attributes 
• Physical attributes like weight, volume 
• Receiving attributes 
• General planning attributes like min-max qty, order qty. 
• Status of item Generally we will group the item attributes in these groups
Main Inventory Bill of material Asset management Costing Purchasing Receiving Physical attributes General planning MPS/MRP planning Lead times Work In Process Order Management Invoicing Service
Now we will discuss main attributes from major group.
Main attribute group
Primary Unit of Measure-
This is the stocking and selling unit of measure. Any necessary conversions are based on this unit of measure. This attribute is not updatable. The default primary unit of measure for new items is defined using the INV: Default Primary Unit of Measure profile option.
User Item Type-
Oracle provides several types by default at installation. These types correspond to the item templates also provided. Select one of these values, or one you defined with the Item Type window.
Different item types are ATO model/ Finished good/ Freight/ Inventory Type etc.
Item Status-
Item status codes set or default the values for attributes under status control. User–defined status codes control certain item attributes designated as status attributes. Item status can be active/engineer/inactive. The default item status for new items is defined using the INV:Default Item Status profile option.
Inventory Attribute Group
Inventory Item-Indicate whether to stock and transact this item in Oracle Inventory.
Stockable-Indicate whether to stock this item in Inventory. You can set this attribute only when you turn on the Inventory Item option.
Transactable – Indicate whether to allow Inventory transactions. You can set this attribute only when you turn on the Stockable option.
Reservable-Indicate whether you can create material reservations. You can reserve an item only when you have sufficient inventory.
Other attribute in this group are Lot control, serial control, locator control.
 
Bill of Material attribute group
BOM allowed-Allows you to define a bill of material for an item, or to assign the item as a component on a bill.
BOM item type-This attribute is controlled at the Master level only. Select a type to control bill functionality. You must enter a value here if BOM Allowed is turned on.
Asset management attribute group
These are the attributes you have to give for asset management.
Asset item type-This attribute identifies the asset item as an Asset Group, Asset Activity, or Rebuildable item.
Activity type-This is relevant when the Asset Item Type is set to Asset Activity. This indicates the type of maintenance for this asset activity.
Costing attribute group
You have to set these attributes while defining or updating items.
Costing enabled-
Indicate whether to report, value, and account for any item costs. Inventory asset value-Indicate whether to value an item as an asset in inventory. Turning this option off indicates an expense item.
Cost of goods sold account-
This attribute is controlled at the Organization level only. Enter a general ledger account to use as a source for the Cost of Goods Sold Account. The default cost of goods sold account is set when you define organization parameters.
Purchasing attribute group
Purchased-
Indicate whether to purchase and receive an item. Turning this option on allows you to set the Purchasable attribute. Purchasable-Indicate whether to order an item on a purchase order. You can set this only when Purchased is turned on.
Receipt required-
Indicate whether you must receive an item before you can pay the invoice. Leave this field blank if you want Inventory to use the value defined in the Purchasing Options window for transactions involving this item.
i.e. three way invoice matching Inspection required-
Indicate whether to inspect an item upon receipt from the supplier, before paying the corresponding invoice. Leave this field blank if you want Inventory to use the
value defined in the Purchasing Options window for transactions involving this item.
Encumbrance account-
This attribute is controlled at the Organization level only. Enter the default encumbrance account Oracle Purchasing uses when an item is received. If the item encumbrance account does not exist, Oracle Purchasing uses the sub inventory account.
Expense account-
This attribute is controlled at the Organization level only. Enter the default inventory account for expense items. This attribute is used only when Inventory Asset Value is turned off. Oracle Purchasing debits this account when you receive an item into inventory only if the item is being expensed. If you receive into an expense subinventory, Oracle Purchasing uses the expense account you assigned to the subinventory first; if you do not define the account here, Oracle Purchasing uses the expense account assigned to the item.
Receiving attribute group
In this group major attributes are receipt date controls, valid transactions and over-receipt quantity control.
Physical attribute group 
The main attributes like weight, volume, dimension are shown below,
General planning attributes 
Inventory planning method-Here you can select option for organizational level planning. Like not planned, min-max or recorder point.
For min-max quantity, order quantity and source. For source you can give inventory, subinventory or supplier.
Order Management attribute group 
Customer ordered-Indicate whether to allow an item to be ordered by external customers. You can add any customer orderable items to price lists in Oracle Order Management.
Shippable-Indicate whether to ship an item to a customer. Shippable items are released by Oracle Shipping Execution’s Pick Release program, creating confirmable shipping lines, and are printed on the pick slip.
Default shipping organization-Enter the Oracle Shipping Execution primary shipping organization.
Picking rule-Enter the picking rule that defines the order in which subinventories, locators, lots, and revisions are picked.
Invoicing attribute group 
Invoicable item-Indicate whether to include an item on an Oracle Receivables invoice.
Accounting rule-Enter an accounting rule to identify special revenue recognition rules for an item, such as recognizing revenue over time.
Invoicing rule-Enter an invoicing rule to determine the period in which you send an invoice when you recognize revenue over time (using accounting rules).
Sales account-This attribute is controlled at the Organization level only. Enter the general ledger account Oracle Receivables uses to record revenue when you bill the customer. If Auto-Accounting is based on items, accounting entries are created at that time.
Item templates
There are two types of templates. Predefined or custom template.
Predefined templates are planning item, purchased, outside processing item, lease item. So that once you assign any template, to new item then all default characters are assign to new item.
Category set & category
Categories are logical grouping of items that have similar characterizes, and a category set is a distinct category grouping scheme and consist of categories. Different category set accordingly to company need and reporting structure.
Use: For forecasting & summarizing history of that category. To keep easy track on that category.
Define category sets

Define categories

Specify default category sets
Assign categories to an item
Tables are related as, for item categories MTL_ITEM_CATEGORIES
MTL_SYSTEM_ITEMS_B
MTL_CATEGORY_SET_VALID_CATS
MTL_CATEGORY_SETS_B
MTL_CATEGORIES_B
Unit of Measure
Oracle Applications products provide powerful methods for defining and manipulating units of measure. You can easily convert between the units you define. This allows you to manufacture, order, or receive items in any unit of measure.
Table is related as:
MTL_UNITS_OF_MEASURE_TL
MTL_UOM_CONVERSIONS
MTL_SYSTEM_ITEMS_B
Item setup
The main tables that are involved in item master set up are with their relation,
MTL_SYSTEM_ITEMS_B
MTL_ITEM_STATUS
MTL_ITEM_TEMPLATES
MTL_PARAMETERS
MTL_ITEM_ATTRIBUTES
Item relationship
You can define item relationship between items. This allows you to search items through these relationships and for maintaining also.
• Item cross reference Use the Customer Item Cross References window to define and update cross references between your inventory items and the customer item numbers defined in the Customer Items Summary/Detail windows.
MTL_ITEM_TEMPL_ATTRIBUTES
• Substitute items In this relationship you can replace the outdated item, still keeping track on it.
• Related items You can relate different items according to your need.
• Manufacturer part no. You can define manufacturer part numbers for items. You can use this information for reporting purposes; and in catalog searches for particular items.
Inventory control
• Locator control You will track item as locator wise, it is a common method of inventory control. 
• Revision Control With different revision of items according to your need, revision control can be Implemented. 
• Lot Control You will define lot of your items so that you can track that item according to their lot numbers. 
• Serial no. Control For expensive or for which you want tight control you will give serial numbers to those items. Item catalog
Used to partition items that share some common characteristics.
Item Transaction
WIP Suppliers INV Inv customers
Inventory can interact or can have transactions with suppliers, customers, work in process and with other sub inventories.
A transaction type is the combination of a transaction source type and a transaction action. It is used to classify a particular transaction for reporting and querying purposes. Oracle Inventory also uses transaction types to identify certain transactions
For example, transaction type is purchase order receipt which is a combination of transaction action i.e. receipt into stores and transaction source type is purchase type.
Major transactions are,
Sub-Inventory transfer
Each subinventory transfer is carried out as two separate transactions, creating two records in MTL_MATERIAL_TRANSACTIONS. The first record represents an issue from the source subinventory and the second record is a receipt from the destination subinventory.
Inter- organization transfer
Use the Inter–Organization Shipping Network window to define accounting information and the relationships that exist between shipping and destination organizations. You can specify whether an organization is a shipping organization, a destination organization, or both.
In these transactions you will need bills, shipping bills and other accounting details.
ABC Analysis & cycle counting
ABC analysis is a method of determining relative value of items in your Inventory sites.
Automatically scheduled or manually scheduled cycle counts You can define your own ABC group like A class, B class, C class.
Now we will go through some of the set up steps, which you will need before setting up inventory.
Setup
• Define item flexfields
 
• Define item categories flexfields 
• Define catalog group flexfields 
 Define UOM 
• Define subinventories. 
• Define locators 
• Define organization parameters. 
• Define intercompany relationship. 
• Define picking rules. Some of the parameters we have to set defaults like item status as active, default primary unit of measure as Each or requisition approval status as approved or unapproved.
Organization parameters
You can define and update default inventory and costing parameters for your current organization in the following areas:
Default inventory parameters Costing information Revision, lot, serial parameters ATP, Pick, Item-sourcing parameters Inter-Organization Information Other account Parameters Define warehouse parameters
Default inventory parameters 
Provide organization code and item master organization
In the Move Order Timeout Period field, enter the number of days a move order requisition can wait for approval. For locator control option: Inventory transactions within this organization do not require locator information. Pre-specified only: Inventory transactions within this organization require a valid, predefined locator for each item. Dynamic entry allowed: Inventory transactions within this organization require a locator for each item. You can choose a valid, predefined locator, or define a locator dynamically at the time of transaction. Determined at subinventory level: Inventory transactions use locator control information that you define at the subinventory level.
Costing Information

You have to define costing organization and costing method.
Valuation Accounts:
You choose a default valuation account when you define organization parameters. Under standard costing, these accounts are defaulted when you define subinventories and can be overridden.
• Material An asset account that tracks material cost. For average costing, this account holds your inventory and in transit values. Once you perform transactions, you cannot change this account.
 
• Material Overhead An asset account that tracks material overhead cost. 
• Resource An asset account that tracks resource cost. 
• Overhead An asset account that tracks resource and outside processing overheads. 
• Outside processing An asset account that tracks outside processing cost. 
• Expense The expense account used when tracking a non-asset item. Other accounts
• Sales The profit and loss (income statement) account that tracks the default revenue account.
 
• Cost of Goods Sold The profit and loss (income statement) account that tracks the default cost of goods sold account. 
• Purchase Price Variance The variance account used to record differences between purchase order price and standard cost. This account is not used with the average cost method. 
• Inventory A/P Accrual The liability account that represents all inventory purchase order receipts not matched in Accounts Payable, such as the uninvoiced receipts account. 
• Invoice Price Variance The variance account used to record differences between purchase order price and invoice price. This account is used by Accounts Payable to record invoice price variance. 
• Encumbrance An expense account used to recognize the reservation of funds when a purchase order is approved. 
• Project Clearance Account When performing miscellaneous issues to capital projects, the project clearance account is used to post the distributions.
• Average Cost Variance Under average costing with negative quantity balances, this account represents the inventory valuation error caused by issuing your inventory before your receipts. Inter-Organization Transfer Accounts
You define default inter–organization transfer accounts in the Organization Parameters window. These accounts are defaulted when you set up shipping information in the Inter–Organization Shipping
Networks window.
• Transfer Credit The default general ledger account used to collect transfer charges when this organization is the shipping organization. This is usually an expense account. • Purchase Price Variance The default general ledger account used to collect the purchase price variance for inter–organization receipts into standard cost organizations. This is usually an expense account. • Payable The default general ledger account used as an inter–organization clearing account when this organization is the receiving organization. This is usually a liability account. • Receivable The default general ledger account used as an inter–organization clearing account when this organization is the shipping organization. This is usually an asset account. • In-transit Inventory The default general ledger account used to hold in-transit inventory value. This is usually an asset account. For average cost organizations, this account is the default material account. Other information you have to give is,
Revision, Serial and lot control information.
ATP, Pick, Item sourcing rules.
Inventory Planning and replenishment:
Oracle Inventory lets you manage your inventory levels using any combination of the system’s planning and replenishment features, including min–max planning, reorder point planning, kanban replenishment, and a replenishment system for generating orders.
Performing Recorder-Point planning
In this planning method you will take minimum order quantity and time to fulfill the order to decide the level of order. So record point is safety stock + forecast demand during lead time
Performing min-max planning
In this simple method you will decide maximum and minimum level of stock for that item, so that at min level order can be placed and the qty of that item can be full at max level.
Subinventory replishment planning
For some items you will have transactions with other subinventory so that optimum stock can be maintained.
Creating & executing Kanban cards
In this you will use kanban method by deciding some items as kanban cards.
And through requisition interface i.e. after running requisition import, Purchase requisition gets created that turns out to purchase orders. Then through purchase order u can receipt material in inventory.
And that is how purchasing comes into picture.
Before that we will take look at main tables in inventory modules like
Major Tables
• MTL_SYSTEM_ITEMS_B: Base table for item definition.
 
• MTL_PARAMETERS : This table is consist of ORGANIZATION_ID, PICKING_RULE_ID, RULE_ID for ATP 
• MTL_ITEM_CATEGORY_ SETS 
• MTL_ITEM_CATEGORIES : These tables will store information about different category sets and categories defined. 
• MTL_ITEM _SUB_INVENTORIES 
• MTL_ITEM_LOCATIONS 
• MTL_SYSTEM_ITEMS_INTERFACE 
• MTL_SUPPLY 
• MTL_ONHAND_QUANTITIES
• MTL_RESERVATIONS : These table stores information about reserved quantity and on hand quantity with available quantity for picking rules. 
• MTL_SALES_ORDERS : Order Management will interact with inventory for order details through this table. 
• MTL_ITEM_FLEXFIELDS 
• MTL_ITEM_TEMPLATES 
• MTL_ITEM_ATTRIBUTES
• MTL_ITEM_REVISIONS 
• MTL_MATERIAL TRANSACTION 
• MTL_TRANSACTIONS_REASONS Additional terms in inventory
• Accounting close cycle: General ledger transfer Inventory accounting periods
 

• Move orders: Move orders are requests for the movement of material within a single organization. They allow planners and facility managers to request the movement of material within a warehouse or facility for purposes like replenishment, material storage relocations and quality handling.
Move orders are restricted to transaction within tan organization
& if you are transferring material between organization, you must internal
requisitions.
Three types of move orders:
Move order requisition Replenishment move orders Pick wave move orders
Interfaces
Open Item Interface
You can import items from any source into Oracle Inventory and Oracle Engineering using the Item Interface. With this interface, you can convert inventory items from another inventory system, migrate assembly and component items from a legacy manufacturing system, convert purchased items from a custom purchasing system, and import new items from a Product Data Management package. The Item Interface validates your data, insuring that your imported items contain the same item detail as items you enter manually in the Master Item window.
The Item Interface reads data from three tables for importing items and item details.
MTL_SYSTEMS_ITEM_INTERFACE This table is used for your new item numbers and all item attributes. This is the main item interface table, and may be the only table you choose to use.
MTL_ITEM_REVISIONS_INTERFACE If you are importing revision details for your new items, you can use this table. Which is used only for revision information, and is not required.
MTL_ITEM_CATEGORIES_INTERFACE To import item category assignments, the table is used to store data about item assignments to category sets, and categories to be imported into the Oracle Inventory MTL_ITEM_CATEGORIES table.
MTL_INTERFACE_ERRORS is used for error tracking of all items that the Item Interface fails.
Before you use the Item Interface, you must write and run a custom program that extracts item information from your source system and inserts the records into the MTL_SYSTEM_ITEM_INTERFACE table. And if revision & category details are there upload into respective tables. After you load item, revision, and item category assignment records into these interface tables, you run the Item Interface to import the data. The Item Interface assigns defaults, validates data you include, and then imports the new items.
Customer Item and Customer Item Cross-Reference Open Interface
A number of manufacturing industries are characterized by a multi-tiered, just-intime supply chain structure. Today’s manufacturing environment requires a close working relationship between customers and suppliers along the entire supply chain. Suppliers must be able to react quickly to their customers’ often changing requirements. By cross-referencing customer items with their own inventory items, suppliers can achieve faster order processing and shipments by allowing customers to place orders using customer item numbers.
You can import customer items and customer item cross-references from any legacy system into oracle inventory.
In customer item interface you import customer items into inventory. For each customer item you must define related information such as customer and item definition level.
MTL_CI_INTERFACE
Using this table data is transferred MTL_CUSTOMER_ITEMS table.
In customer item cross reference, you can import cross-references between customer items and exiting inventory items into your master organization. You can create multiple cross-references between customer items and one Oracle Inventory item. You can also create multiple cross-references between Oracle Inventory items and one customer item.
MTL_CI_XREFS_INTERFACE Using this interface table data is uploaded into base table, MTL_CUSTOMER_ITEM_XREFS.
Reports In inventory
Oracle Inventory provides you with a wide variety of reports, intended for different users of the product.
We will have overlook on major reports that you will come across.
Inactive items report
You can use this report to print items that have not had an inventory transaction since the date you specify. You can use this report to isolate items that have become inactive and verify their status.
The parameters are display and break on sub inventory, category set, inactive since i.e. date from which no transactions were occurred for items.
Item categories report 
You will use this report to list items and their associated categories. Report can develop output as per category set and for given item range.
Item definition detail 
Use the Item Definition Detail report to view comprehensive information for items. Use this report to verify items have been classified in conformance with decisions you have made regarding how the parts are to be planned, coasted, and located.
The report prints the item definition for the organization in which you submit the report.
You can view item attributes as per the category and also depending on your choice which attributes you want to print. Like general item attributes, bill of material item attributes, costing item attributes, inventory item attributes or physical item attributes.
Item definition summary report 
Use the Item Definition Summary report to print a limited amount of information about items, such as description, status, and cost.
Item template listing 
Use the Item Template Listing to review the template definitions. A template is a way to define a set of attribute values.
Reports parameters are all template flag or item template.
 
Item statuses report 
Use the Item Statuses Report to view the item statuses. For example, You can use the report to review all pending statuses by making the effective date and the report date the same. You can have options like categories from-to, items from –to, and status effective date. And only for particular status.
 
ABC descending value report 
Use the ABC Descending Value Report to view the results of an ABC compile. The report is sorted by descending value or quantity, depending on the compile criterion. Use this report to evaluate the break points for assigning your ABC classes to items.
You can give cumulative display criteria i.e. cumulative by value of cumulative by quantity
.

AIM-METHODOLOGY




Before implementing apps, the functional consultants will study the existing system and then map the system with the oracle apps. They try to fit in the current processes into the apps processes.

For this they follow BR100 template from AIM methodology. These templates are developed by oracle and are licensed and doesnt come freely. the company that uses this has to pay money to oracle for using it.
BR030 - Solution Definition

 In this phase they define the solutions which means they complete the process cycles in oracle apps. With this the mapping of existing processes with apps will be complete.
After this phase they do CRP testing. CRP means conference room pilot. They take the solutions of oracle apps and see whether the existing processes fit in or not. This will be done by end user. In lay man terms, its like this.. In a bank the cashier is using one calculator for daily purpose.. and suddenly you go and give him a new one and ask him to use it.. after using it in for some time.. he will come up with the gaps that the new one cannot perform..since the cashier cannot change his process, we need to modify the new one . So after this CRP testing the gaps will be identified. Again the functional team will sit and try to fit into oracle processes.. This is a iterative process and hence there may be many rounds of CRP testing.. CRP 1, CRP 2 and all.. Finally the gaps will be identified and these will be taken as customizations..
and hence more gaps more money to consulting companies like tcs.
MD020 - Add on solution

 For each gap, a solution will be found. And each solution is recorded in this MD020 document. This will have a high level view of what the gap is and how it will be addressed in the customizations. Functional consultants will also prepare this.

MD050 - Functional design doc.
For each md020 there will be a MD050 doc..which is a functional design document. Its like an extension of the previous one with details like how the solution will be developed and all. which validations needs to be done and all.

MD070 - Technical design document
This is where you come into picture. you will be converting the functional doc to technical doc, like which API will be used, which tables will be used.. and all...based on this doc a developer will develop the code.

TE070 - Unit testing scripts and results. unit testing will be done by developer. you need to remember these terms and phases. in unit testing you will be testing components individually. like for instance in the interface development we tested the sqlloader scripts, table creation scripts, packages that call API's are tested seperately. the bugs that are found in this phase are fixed immediately then and there. The final results will be preserved and will be useful in future.

TE080 - Link test scripts and results
A separate testing team will do this. They will not look into the code but will be interested in input and out. This is like final testing. Any bugs found are notified to the development team for fixing.


Well your role will mostly be in MD050, MD070 and TE070 phases and these are usually carried out at offshore. While the other stuff are carried out at onsite.

Keep an idea of these as you will be mentioning about AIM methodology and they may ask some questions on these.

APPS TABLES(PO,APS,GL,OM,INV,AR,WIP)




Oracle Apps WIP KEY Tables 
WIP_LINES 
WIP_LINES stores production line information. Each row includes a line name, maximum and minimum rate information, throughput for rate based lines (lead time), and the start and stop time information that determines the amount of time per day that the line is available. Oracle Work in Process uses this information when you associate a line with a repetitive assembly and when you define a repetitive schedule on the line. Production line information is optional for discrete jobs.
 
WIP_OPERATIONS 
WIP_OPERATIONS stores information about job and repetitive schedule operations. Each row represents a specific operation and includes an operation sequence number, which orders the operations for the job or repetitive schedule. Each row also includes the assembly quantity completed at an operation, the quantity at each intraoperation step, the department associated with an operation, the scheduled start and completion dates for an operation, the operation’s count point andbackflush types and other operation attributes. In general, Oracle Work in Process uses this information to control and monitor assembly production on the shop floor.
WIP_ENTITIES 
WIP_ENTITIES stores information about jobs, repetitive assemblies, and flow schedules. Each row includes a unique entity name, the entity type,and the assembly being built. Oracle Work in Process uses this information to control production activities and to ensure that entities with duplicate names are not created.
 
WIP_DISCRETE_JOBS 
WIP_DISCRETE_JOBS stores discrete job information. Each row represents a discrete job, and contains information about the assembly being built, the revision of the assembly, the job quantity, the status of the job, the material control method, accounting information, and job schedule dates. Oracle Work in Process uses this information to control discrete production.
WIP_TRANSACTIONS 
WIP_TRANSACTIONS stores information about WIP resource transactions. Each row represents a single resource transaction and includes a unique transaction Identifier, a transaction date, the job or repetitive schedule charged, the WIP operation and resource charges, and the number of units of measure applied. Oracle Work in Process uses this information to track resource charges and to calculate the values stored in WIP_TRANSACTION_ACCOUNTS.
Oracle Work in Process (WIP) Tables
wip_move_transactions
wip_discrete_jobs
wip_repetitive_schedules
wip_move_txn_interface
wip_cost_txn_interface
wip_job_shedule_interface
wip_job_dtls_interface



Purchase Order(PO):
---------------------
1.po_requisition_headers_all   -- requisition header info
2.po_requisition_lines_all        -- Requisition Lines info
3.po_req_distributions_all      -- Requisition Distribution info
4.po_headers_all                   -- PO Header Info
5.po_lines_all                         -- PO Line Info
6.po_line_locations_all           -- PO Line Shipment info
7.po_distributions_all             -- PO Distribution info
8.rcv_shipment_headers         -- Receiving header info
9.rcv_shipment_lines              -- Receiving Lines info
10.rcv_transactions                -- Receiving transationd info
11.po_vendors                      -- Supplier Header info
12.po_vendor_sites_all          -- Supplier Site info
13.po_vendor_site_contacts  -- Supplier Site Contact info
14.hr_locations                      -- Supplier Site Address

Order Management (OM):
---------------------------
1.oe_order_headers_all             -- Order Header info
2.oe_order_lines_all                  -- Order line info
3.oe_transaction_types_tl          -- Order type info
4.oe_order_holds                      -- Order Hold info
4.oe_holds_all                           -- Order Hold info
5.oe_hold_sources                    -- Order Hold source info
6.oe_hold_releases                    -- Hold Release info
7.wsh_delivery_details               -- Delivery Detial Info
8.wsh_new_deliveries                -- Delivery Header info
9.wsh_delivery_Assignments      -- Delivery Assignments info
10.wsh_trip_stops                      -- Delivery trips info
11.hz_cust_accounts                  -- Customer info
12.hz_parties                              -- Party info
13.hz_cust_site_uses_all             -- Customer site use info
14.hz_cust_acct_sites_all           -- Customer Site Acct info
15.hz_party_sites                       -- Party site info
16.hz_locations                          -- Customer Site Adderess
17.wsh_lookups                        -- Shipping lookup info


Accounts Payable(AP):
-----------------------
1.ap_invoices_all                               -- Invoice Header info
2.ap_invoice_distributions_all            -- Invoice Line info
3.ap_checks_all                                -- Check info
4.ap_invoice_payments_all                -- Invoice Payment info
5.ap_payment_schedules_all             -- Payment Schedule info
6.ap_holds_all                                  -- Invoice Holds info
7.ap_lookup_codes                          -- Payable lookup info
8.po_vendors                                   -- Supplier Header info
9.po_vendor_sites_all                       -- Supplier Site info
10.po_vendor_site_contacts             -- Supplier Site Contact info
11.hr_locations                                -- Supplier Site Address
12.ap_banks                                   -- Bank Info
13.ap_bank_branches                     -- Bank Branch info
14.ap_ae_headers_all                     -- Accounitng header info
15.ap_ae_lines_all                          -- Accounting Lines info
16.ap_ae_accounting_evets            -- Accounting events info
17.ap_terms                                   -- Payment Terms

Accounts Receivables(AR):
---------------------------
1.ra_customer_trx_all                   -- Receivable transaction info
2.ra_customer_trx_lines_all          -- Transaction lines info
3.ra_cust_trx_line_gl_dist_all       -- Transaction distribution info
4.ar_receivable_applications_all   -- Receiving application info
5.ar_cash_Receipts_all                -- Cash Receipt info
6.ar_terms                                   -- Receivable Terms
7.hz_cust_accounts                     -- Customer info
8.hz_parties                                -- Party info
9.hz_cust_site_uses_all               -- Customer site use info
10.hz_cust_acct_sites_all            -- Customer Site Acct info
11.hz_party_sites                        -- Party site info
12.hz_locations                   -- Customer Site Adderess

InvenvtoryModule(INV):
-------------------------
1.mtl_System_items_b              -- Master item info
2.mtl_onhand_quanitties            -- Item onhand qty info
3.mtl_reservations                     -- Item Reservation info
4.mtl_material_transactions       -- Item Transaction info
5.mtl_item_locations                 -- Item location info
6,mtl_Categeries                      -- Item Category info
7.mtl_item_categories              -- Invemtry Categry
8.mtl_secondary_inventories    -- Subinventories info
9.org_organization_definitions  -- Organizaition info
10.mtl_transaction_Accounts   -- Item Transaction info
11.mtl_txn_source_types         -- Item Transaction sources
12.mtl_parameters                  -- Inventory Parameters

General Ledger(GL) :
--------------------

1.gl_je_headers               -- Journal Header info
2.gl_je_lines                    -- Journal Line info
3.gl_je_batches               -- Journal Batch info
4.gl_Sets_of_books        -- set of books info
5.gl_chart_of_accoutns   -- chart of accounts info
6.gl_code_combinations  -- Code combination info
7.gl_je_sources               -- Journal Source info
8.gl_je_categories           -- Journal Cateogiy info
9.fnd_currencies             -- Currency info
10.gl_balances               -- Journal Balances








Order management process


Order Management (OM)


1) What are the Base Tables and Interface Tables for Order Management?
Interface Tables : OE_HEADERS_IFACE_ALL, OE_LINES_IFACE_ALL
OE_PRICE_ADJS_IFACE_ALL, OE_ACTIONS_IFACE_ALL
OE_CREDITS_IFACE_ALL (Order holds like credit check holds etc)
Base Tables : OE_ORDER_HEADERS_ALL: Order Header Information
OE_ORDER_LINES_ALL: Items Information
OE_PRICE_ADJUSTMENTS: Discounts Information
OE_SALES_CREDITS: Sales Representative Credits.
Shipping Tables :WSH_NEW_DELIVERIES, WSH_DELIVERY_DETAILS, WSH_DELIVERY_ASSIGNMENTS, WSH_DELIVERIES.

2) What are the Base Tables and Interface Tables for Order Management?
Interface Tables : OE_HEADERS_IFACE_ALL, OE_LINES_IFACE_ALL
OE_PRICE_ADJS_IFACE_ALL, OE_ACTIONS_IFACE_ALL
OE_CREDITS_IFACE_ALL (Order holds like credit check holds etc)
Base Tables : OE_ORDER_HEADERS_ALL: Order Header Information
OE_ORDER_LINES_ALL: Items Information
OE_PRICE_ADJUSTMENTS: Discounts Information
OE_SALES_CREDITS: Sales Representative Credits.
Shipping Tables :WSH_NEW_DELIVERIES, WSH_DELIVERY_DETAILS, WSH_DELIVERY_ASSIGNMENTS, WSH_DELIVERIES.

3) What is Order Import and What are the Setup's involved in Order Import?
A) Order Import is an open interface that consists of open interface tables and a set of API’s. It imports New, updated, or changed sales orders from other applications such as Legacy systems. Order Import features include validations, Defaulting, Processing Constraints checks, Applying and releasing of order holds, scheduling of shipments, then ultimately inserting, updating or deleting orders from the OM base tables. Order management checks all the data during the import process to ensure its validity with OM. Valid Transactions are then converted into orders with lines, reservations ,price adjustments, and sales credits in the OM base tables.
B) Setups:
· Setup every aspect of order management that we want to use with imported orders, including customers, pricing, items, and bills.
· Define and enable the order import sources using the order import source window.

4) Explain the Order Cycle?
i) Enter the Sales Order
ii) Book the Sales Order(SO will not be processed until booked(Inventory confirmation))
iii) Release sales order(Pickslip Report is generated and Deliveries are created)
(Deliveries – details about the delivery. Belongs to shipping module (wsh_deliveries, wsh_new_deliveries, wsh_delivery_assignments etc) they explain how many items are being shipped and such details.
iv) Transaction Move Order (creates reservations determines the source and transfers the inventory into the staging areas)
v) Launch Pick Release (
vi) Ship Confirm (Shipping Documents(Pickslip report, Performa Invoice, Shipping Lables))
vii) Auto invoice and closed

5) Explain the Order to Cash Flow?
I. Enter the Sales Order
II. Book the Sales Order(SO will not be processed until booked(Inventory confirmation))
III. Release sales order(Pickslip Report is generated and Deliveries are created)
(Deliveries – details about the delivery. Belongs to shipping module (wsh_deliveries, wsh_new_deliveries, wsh_delivery_assignments etc) they explain how many items are being shipped and such details.
IV. Transaction Move Order (Selects the serial number of the product which has to be moved/ shipped)
V. Launch Pick Release
VI. Ship Confirm (Shipping Documents(Pickslip report, Performa Invoice, Shipping Lables))
VII. AutoInvoice (Creation of Invoice in Accounts Receivable Module)
VIII.Autolockbox ( Appling Receipts to Invoices In AR)
IX. Transfer to General Ledger ( Populates GL interface tables)
X. Journal Import ( Populates GL base tables)
XI. Posting ( Account Balances Updated).

5. What are the Process Constraints?
A. Process Constraints prevent users from adding updating, deleting, splitting lines and canceling order or return information beyond certain points in the order cycle. Oracle has provided certain process constraints which prevent data integrity violations.
Process constraints are defined for entities and attributes. Entities include regions on the sales order window such as order, line, order price adjustments, line price adjustments, order sales credits and line sales credits. Attributes include individual fields (of a particular entity) such as warehouse, shit to location, or agreement.

6. What are Validation Templates? 
A) Validation Templates are used to define the validation conditions in process constraints. A validation template names a conditions and defines the semantic of how to validate that condition. These are used in processing constraints framework to specify the constraining conditions for a given constraint. These conditions are based on
1 Where the entity is in its work flow.
2 The state of attributes on an entity.
3 Any other validation condition that cannot be modeled using the above condition.

7. What are different types of Holds?
1 GSA(General Services Administration) Violation Hold(Ensures that specific customers always get better pricing for example Govt. Customers)
2 Credit Checking Hold( Used for credit checking feature Ex: Credit Limit)
3 Configurator Validation Hold ( Cause: If we invalidate a configuration after booking)

8. What is Document Sequence?
A) Document sequence is defined to automatically generate numbers for your orders or returns as you enter them. Single / multiple document sequences can be defined for different order types.
Document sequences can be defined as three types Automatic (Does not ensure that the numbers are contiguous), Gapless (Ensures that the numbering is contiguous), Manual Numbering. Order Management validates that the number specified is unique for order type.

9. What are Defaulting Rules?
A) A defaulting rule is a value that OM automatically places in an order field of the sales order window. Defaulting rules reduce the amount of information one must enter. A defaulting rule is a collection of defaulting sources for objects and their attributes.
It involves the following steps
1 Defaulting Conditions - Conditions for Defaulting
2 Sequence – Priority for search
3 Source – Entity ,Attribute, Value
4 Defaulting source/Value

10. When an order cannot be cancelled?
A) An order cannot be cancelled if,
1 It has been closed
2 It has already been cancelled
3 A work order is open for an ATO line
4 Any part of the line has been shipped or invoiced
5 Any return line has been returned or credited.

11. When an order cannot be deleted?
A) you cannot delete an order line until there is a need for recording reason.

12. What is order type?
A) An order type is the classification of order. It controls the order work flow activity, order number sequence, credit check point and transaction type. Order Type is associated to a work flow process which drives the processing of the order.

13. What are primary and secondary price lists?
A) Every order is associated to a price list as each item on the order ought to have a price. A price list is contains basic list information and one or more pricing lines, pricing attributes, qualifiers, and secondary price lists. The price list that is primarily associated to an order is termed as Primary price list.
The pricing engine uses a Secondary Price list if it cannot determine the price of the item ordered in the Primary price list.

14. What is pick slip? Types?
A) It is an internal shipping document that pickers use to locate items to ship for an order.
1 Standard Pick Slip – Each order will have its own pick slip with in each picking batch.
2 Consolidated Pickslip – Pick slip will have all the orders released in the each picking batch.

15. What is packing slip?
A) It is an external shipping document that accompanies the shipment itemizing the contents of the shipment.

16. What are picking rules?
A) Picking rules define the sources and prioritization of sub inventories, lots, revisions and locators when the item is pick released by order management. They are user defined set of rules to define the priorities order management must use when picking items from finished goods inventory to ship to a customer.

17. Where do you find the order status column?
A) In the base tables, Order Status is maintained both at the header and line level. The field that maintains the Order status is FLOW_STATUS_CODE. This field is available in both the OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL.

18. When the order import program is run it validates and the errors occurred can be seen in?
A) Responsibility: Order Management Super User
Navigation: Order, Returns > Import Orders > 

 

 

 

Create XML Publisher report without RDF




First we have to create a data template for that. i have to give the sample data template..


-----> Create a data template on notepad like below

<?xml version = "1.0" encoding = "UTF-8"?>
<dataTemplate name="XXAR_CLIENT_DET_CASH_PYMT" version="1.0">
<properties>
<property name="debug_mode" value="on"/>
</properties>
 <parameters>
  <parameter name ="p_Workorder_From"          dataType="character"/>
   </parameters>
<dataQuery>
   <sqlStatement name="Q_CLNT_DET">
         select   distinct hca.account_number,account_name,
         hl.address4 Legacy_num,hca.attribute2 LOB,
         decode(hcsua.org_id,2,'US',22,'CAN') org_id,
         decode(hca.attribute12,'Y','CASH') Payment_Mode,
         trunc(TO_DATE(acrmv.start_date,'DD-MON-YY')) START_DATE,trunc(TO_DATE(acrmv.end_date,'DD-MON-YY')) END_DATE,
         acrm.name PAYMENT_METHOD,
         hcsua.site_use_code,
         hl.address1||','||hl.address2||','||hl.address3||','||hl.address4||','||hl.CITY||','||hl.state||','||hl.POSTAL_CODE||','||hl.country BILL_TO_ADDRESS
from
hz_locations hl,
HZ_PARTY_SITES hps,
hz_parties party,
HZ_CUST_ACCOUNTS hca,
HZ_CUST_ACCT_SITES_ALL hcasa,
HZ_CUST_SITE_USES_ALL hcsua,
HZ_CUSTOMER_PROFILES hcp,
ar_cust_receipt_methods_v acrmv,
ar_receipt_methods acrm
where
hps.location_id=hl.location_id
and party.party_id=hps.party_id
and party.party_id=hca.party_id
and hcasa.CUST_ACCOUNT_ID=hca.CUST_ACCOUNT_ID
and hcsua.CUST_ACCT_SITE_ID=hcasa.CUST_ACCT_SITE_ID
and hcp.SITE_USE_ID=hcsua.SITE_USE_ID
and hps.party_site_id=hcasa.party_site_id
and hca.cust_account_id = acrmv.customer_id
and acrmv.receipt_method_id = acrm.receipt_method_id
and hca.attribute12 = 'Y'
and hcsua.site_use_code = 'BILL_TO'
AND hcasa.BILL_TO_FLAG = 'P'
and rownum = 1
</sqlStatement>
  ---if we want one more sql query we add here......
</dataQuery>
<dataStructure>
    <group name="G_CLNT_DET" source="Q_CLNT_DET">
                    <element name ="ACCOUNT_NAME" value="ACCOUNT_NAME"/>
                    <element name ="ACCOUNT_NUMBER" value="ACCOUNT_NUMBER"/>
                    <element name ="LEGACY_NUM" value="LEGACY_NUM"/>         
                    <element name ="LOB" value="LOB"/>
                    <element name ="ORG_ID" value="ORG_ID"/>
                    <element name ="PAYMENT_MODE" value="PAYMENT_MODE"/>
                    <element name ="START_DATE" value="START_DATE"/>
                    <element name ="END_DATE" value="END_DATE"/>
                    <element name ="PAYMENT_METHOD" value="PAYMENT_METHOD"/>
                    <element name ="SITE_USE_CODE" value="SITE_USE_CODE"/>
                    <element name ="BILL_TO_ADDRESS" value="BILL_TO_ADDRESS"/>
-----if we have one more group we can add here.....
   </group>
</dataStructure>
<dataTrigger name="afterReport" source="xx.logic_func(:p_Workorder_From)"/>
</dataTemplate>
save it as .XML format



2. Once you create the Data definition, please create the respective concurrent program for this report if one does not already exists. Make sure the execute for this concurrent program should XDODTEXE no need to create executable,this is excises one. 

3. create concurrent program Make sure to enter the Token in the parameters screen. Also noted that this token should match to your parameters name in Data Template file.

4.Create request group and add to concurrent program.
5.attached the request group to responsibility.
6. go to srs window we will get the XML output.


Define the RTF Template using the Generated Data XML.

  .rtf File Regitration:
 =======================

1)Goto the XML Publisher Administrator Responsibility
2)Select Data Definations form
  Enter Data Defination Name = Enter Any Name 
  Code                          = Concurrent Program Short Name 
  Application                 = Any application
  startdate                         = Current Date
file                                = what ever ur create datatemplate file attached here

3)Copy the DataDefination name we have to add this to the Templete
4)Open the Templete Form
  Enter Templete Name : Any Name
  DataDefination      : enter data defination whatever we have created
  Code                : Concurrent Program Short Name
  Type                : rtf
  application         : any Application
  File                : Upload the .rtf file
  Laguage             : English
  Territory           : United States

5)Select Apply button

After register the .rtf file submit concurrent Program from SRS window system will 
automatically pick the .rtf file and generates  the Output.

If we want to customze the .rtf file we have to download by using templete , Customize then
upload the .rtf templete