What is Flexfield?
A flexfield is a field made up of segments. A flex field is a flexible data field that your organization can customize to your business needs without programming. Oracle Applications uses two types of flexfields, key flexfields and descriptive flexfields.
What is a Set of Books (SOB)?
Set of Books is a financial entity that shares a common Chart of Accounts, Functional Currency and Accounting Calendar (3Cs).
What is Segment?
A segment is a single sub–field within a flexfield. You define the appearance and meaning of individual segments when customizing a flexfield. A segment is represented in your database as a single table column.
What is a Value Set?
The flexfield validates each segment against a set of valid values that are usually predefined are called Value Sets.
What is Cross Validation?
A cross-validation rule defines whether a value of a particular segment can be combined with specific values of other segments
What are the different types of tables in Oracle 11i Apps?
B – The Main base tables
_ALL – Contains multi-org data
_V – View created on base table
_TL – Table that supports multi language
_VL – View created on multi language tables
_F – Data tracking tables. Used in HRMS
_S – Sequence related table
_DFV / _KFV – The DFF/KFF table created on the base table
What is the difference between Request Group and Request Set?
A request group is a collection of reports or concurrent programs.  A System Administrator defines report groups in order to control user access to reports and concurrent programs.  Only a System Administrator can create a request group.
Request sets define run and print options, and possibly, parameter values, for a collection of reports or concurrent program. End users and System Administrators can define request sets. A System Administrator has request set privileges beyond those of an end user. 
What are different types of validations of Value Sets?
None (not validated at all)
Independent
Dependent
Table
Special (advanced)
Pair (advanced)
Can you change the validation type of the existing Value set?
No.
What are the validation types supported by Accounting Flexfield?
Dependent, Independent, Table

What is the difference between Discrete Manufacturing and Process Manufacturing?
Discrete manufacturing is a manufacturing process where distinct products are built or manufactured in discrete batches on manufacturing floor. The resulting product is what you can count. It uses Bills of Materials (BOMs) and assembles along a routing.
Eg: Computer Manufacturing, Machinery Manufacturing, Automobiles, etc
Process manufacturing is a manufacturing process in which the end product manufactured are undifferentiated. It uses formulations or recipes and blends in a batch.
Eg: Pharmaceutical, Food and beverages, Refineries, etc
What are Shared Entities in Oracle 11i Apps?
Shared entities enable one-time definition of object and are accessed by several products/Modules.
Few shared entities and the owned applications are
Set of Books – General Ledger
Items – Inventory
Unit of Measure – Inventory
Suppliers – Purchasing
Customers – Receivables
Locations – Human Resource
Employee – Human Resource
Organization – Human Resource
How data are secured (partitioned) in Oracle 11i Applications?
General Ledger and Fixed Assets – Set of Books
Human Resource – Business Group
Order Management, Accounts Receivables, Accounts Payables, Purchasing, Cash Management, Projects, Service, Sales Compensation, Sales and Marketing – Operating Unit
Inventory, Manufacturing – Inventory Unit
There are 34 KFF’s available in Oracle 11i. They are as follows
S.No.
Flex Field
Owning Application
Maximum Segments
1
AHL Operation
Advanced Service Online
15
2
AHL Route
Advanced Service Online
15
3
Asset Key Flexfield
Assets
10
4
Category Flexfield
Assets
7
5
Location Flexfield
Assets
7
6
Group Asset
CRL Financials Assets
7
7
Super Group
CRL Financials Assets
7
8
Management Flexfield
Financials Intelligence
9
Accounting Flexfield
General Ledger
30
10
Reporting Attributes: Accounting
General Ledger
11
CAGR Flexfield
Human Resources
20
12
Competence Flexfield
Human Resources
30
13
Grade Flexfield
Human Resources
30
14
Item Contexts Key Flex
Human Resources
30
15
Job Flexfield
Human Resources
30
16
Personal Analysis Flexfield
Human Resources
30
17
Position Flexfield
Human Resources
30
18
Soft Coded Key Flexfield
Human Resources
30
19
Account Aliases
Inventory
20
20
Item Catalogs
Inventory
20
21
Item Categories
Inventory
20
22
ORACLE_SERVICE_ITEM_FLEXFIELD
Inventory
20
23
Sales Orders
Inventory
20
24
Stock Locators
Inventory
20
25
System Items
Inventory
20
26
Bank Details Key Flexfield
Payroll
30
27
Cost Allocation Flexfield
Payroll
30
28
People Group Flexfield
Payroll
30
29
PSB Position Flexfield
Public Sector Budgeting
30
30
ARTA-Receipt Prof Ident
Receivables
15
31
Sales Tax Location Flexfield
Receivables
10
32
Territory Flexfield
Receivables
20
33
Oracle Service Item Flexfield
Service
20
34
Training Resources
Training Administration
20
Lets take a case Food industry:

FG Foods Ltd. sell variety of Chicken which can have different weight. The superior quality of a chicken weighs to 4 Pound (on an average) but the deviation can be ±10%. This chicken is purchased on number basis and later it is sold on Number (Each) basis as well as on weight (Pound-Lbs) basis. So here Chicken is getting transacted based on two UOM and FG Foods want to track Qty on both UoM basis.
To satisfy this requirement we need to define an item which can be tracked on two UoM, define converser rate between these UoMs.

Item Definition:
UoM Conversion:
Also define Inter-class conversion that too item specific.
1 Unit = 4 Pound

Transactions:
Lets look at the transaction below, 100 Lbs comes to 25 chickens (as per tolerance), but if it goes beyond the tolerance then Oracle will not accept it.


In this case, based on tolerance defined it will accept values for secondary UoM ±2.5 (10% of 25).
So in below transactions one line is on –ve tolerance and other is on +ve tolerance.

On-hand and Availability:

Miscellaneous Issue:
Lets try doing issue transaction based on only Secondary UoM (Each). Oracle will automatically calculate quantity in other UoM based on the conversion rate.


On-hand Qty:
In above transaction, even though we did not give value in Lbs, Oracle deducted one chicken and 4 Pounds (refer the conversion).
51-1   = 50 Each
200-4 = 196 Lbs


Price List View:
Oracle accepts different price values for different UoM as shown below, and you can sell the product on any UoM.


Sales Order Lines 68097 :
Lets sell this product based on different UoM..
Oracle will pull the price based on UoM you mentioned on the Order line, also it asks to feed the secondary qty as well. But remember the final transaction will happen based on UoM added on Order line and then other qty will be calculated.


Now Process the Order: Book > Pick Release > Pick Confirm > Ship Confirm.

Observe the above shipping transactions,
Line 1.1: even though its showing Secondary Req Qty as 12 actual Secondary Shipped Qty is 11.5 (as per the conversion), as 46Lbs of chicken comes to 11.5 (46/4)
Line 1.2: Here we did not give qty in Lbs, so oracle calculated it based on conversion and populated.
At the end of this transaction the final On-Hand shall as below:
50 – (11.5+12) =  26.5
196 – (46+48)  = 102
Item Orderability – This is new feature introduced in Oracle R12.1.1.This is the rule that user can define to restrict the items/group of item (Category) that can be ordered from the Sales Order form.

Because of the complex business scenario in the Modern time organization want to control which customer are allowed to order which product.

Consider below scenarios:
• If a company is developing customer specific items, then specific item shall be sold to specific customer only.
• Few products may be banned in specific region.
• Few items may be sold thru specific channel only. Example: Online, Distributors, franchises, Sales Executive etc.

Now Order management Provide a new utility in R12.1.1 to define the rule to restrict the Item to be sold, based on rules, this utility is name as
Item Orderability Rules. It allows user to Order the Item based on the Rules. Item Orderability rules are defined at Operating Unit (OU) Level.


Now let’s have a deeper look at Item Orderability:

Level at which rule can be built:
As of Now Oracle has provided rules to control only at 11 attributes  


01. Customer

02. Customer Class
03. Customer Category
04. Region
05. Order Type
06. Ship To
07. Bill To
08. Deliver To
09. Sales Channel
10. Sales Representative
11. End Customer
Rule can be defined based on any combination of above attributes:
Example:


 
 Suppose one rule is built based on multiple attributes as done in above example:
The OR condition is applicable when evaluating multiple conditions. In the example above, either the ‘Customer Category’ OR ‘Customer’ OR ‘Sales Channel’ is taken into consideration.

Criteria for the rule:
Criteria can be ‘Item’ or ‘Item Category’


If you select Category as a criterion then you will see “Item Categories
Codes” from the Category Set which is assigned as ‘Default Category Set’
for Order Entry functional area for that OU.

Example:
In our case ‘Order Entry’ has ‘Inv.Item’ category set assigned so we
will be able see category codes from ‘Inv.Item’ Category set only.



Item Validation Organization is referred to validate ‘Item + Category’ combination

Generally Available Flag:
We can set up rules to define when an item or item category is generally not available (the Generally Available box is unselected)
with the conditions available for that rule. For example, Item X is
generally not available, however, since you have set up conditions at
the Rule Level, it is available for a particular customer, or region or
customer class.

Conclusion:
Generally Available box is unselected: Oracle will allow putting order for Criteria + ruling combination
Generally Available box is Selected:      Oracle will not allow putting order for Criteria + Rule combination

This is illustrated in the example below:

Case 1: Unselect Generally Available

This means, Item ‘AS54999’ is generally not available for all, but you want to sell it to Customer ‘A. C. Networks’ only.

So this rule allows putting order for Customer + Item combination.

Case 2: Select Generally Available


This means, Item ‘AS54999’ is generally available but you do not want Customer ‘A. C. Networks’ to order it.
So this rule does not allow putting order for Customer + Item combination



Effect of “OM: Use Materialized View for Items LOV (Honors Item Orderability Rules)”

If the value of the profile option OM: Use Materialized View for Items LOV
(Honors Item Orderability Rules) is set to Yes, then the Ordered Item
LOV displays only those items which are based on the rules defined. The
Ordered Item LOV is then dynamically populated based on Item
Orderability Rules and the current attribute values on the line.


If the value of the profile option OM: Use Materialized View for Items LOV
(Honors Item Orderability Rules) is set to No, then the Ordered Items
LOV lists all the items of the item validation organization of the
current operating unit. This doesn’t consider the defined item
orderability rules, however if there is a defined rule that prevents the
item from being ordered, then an error message is displayed while
saving the order. You will not be able to save the order. Below is
Simple test case for Item Orderability feature.


Steps to Define the Item Orderability Rule- 

  1. Select the Criteria  (Item or Category. And Generally Available or not)
  2. Select criteria values (Item Number / Category Code)
  3. Select the Rules Level/s (by selecting any combinations of above 11 attributes)
  4. Select Rules Level value.
If you find a case where Shipped Quantity more than Ordered Quantity, then you may control it using the shipment tolerance setup given below.
Over or under shipment tolerance can be setup at at three levels.

1. Item Level (Highest precedence)

2. Customer Level

3. Profile Option (Lowest precedence): This can be setup at Site level.