oracle apps ebs-- flexfields

Flexfields:

1. Configure applications to support your own accounting, product and other codes.
2. Enable the construction of intelligent keys.
3. Configure application to capture additional data.
4. Use the application to validate values and value combinations entered by the user.
5. Support multiple flexfield structures depending on data context.

there are two Types Of Flexfields

• Key flexfield
• Descriptive flexfield

KEY FLEXFIELD
we do have 39 KFF's

• KFF Owned by one application; used by many
• Required to set up not always required to use
• Intelligent keys
• Identifies entities

DESCRIPTIVE FLEXFIELD
we do have around 3000+ DFF's

• DFF Associated with tables in a specific application
• Setup is optional
• No intelligence; only stores additional information
• Captures additional information only

key flexifield qualifier

A qualifier is a label attached to a particular key flexfield segment so it can be located by the application requiring its information. 

A key flexfield qualifier can be of 2 types:

• Flexfield qualifiers
• Segment qualifiers

Flexfield qualifiers: identify a segment in a flexfield.
Segment qualifiers: identify a value set in a segment.

allow dynamic insert: 
Dynamic Insertion is a feature which controls whether the user can enter new account code combinations from any form/window. 
If this feature is disabled, then the user cannot input new account code combinations from any window/form.

cross validation: 
key flexfields with multiple segments, we can define rules to cross check value combinations entered with in the key flexfield segments. This option is referred as Cross Validation rules.

Value Set

A value set is a definition of the values approved for entry or display by a particular flexfield segment. A value set may also contain a list of actual approved values although this is not required.

Some value sets permit a limited range of values others permit only certain values others have minimal restrictions.
Different flexfields can share the same value set. For example, a value set containing the names of regional offices could be used by many different flexfields.
Different segments of the same flexfield can use the same value set, for example a date value set. Segments defined to different structures of the same flexfield can share value set. Many of the report parameters used with Standard Request Submission (SRS) forms are tied to shared value sets.
Value sets do not have to have the same actual values defined for them.

Value Set Security Type

No Security:
All security is disabled for this value set.
Hierarchical Security: 
With Hierarchical security, the features of the value security and value hierarchies are combined. With this feature any security that applies to a parent value also applies to its child values.
Non-Hierarchical Security: 
Security is enabled, but the rules of the hierarchical security do not apply. That is, a security rule that applies to a parent value does not “cascade down” to its child values.


NONE: 
A value set of the type None has no list of approved values associated with it. A None value set performs only minimal checking of, for example, data type and length.
INDEPENDENT: 
Independent type value sets perform basic checking but also check a value entered against the list of approved values you define.
DEPENDENT:
A dependent value set is associated with an independent value set. Dependent value sets ensure that all dependent value are associated with a value in the related independent value set.
TABLE:
Table value sets obtain their lists of approved values from existing applications tables. When defining your table value set, you specify a SQL query to retrieve all the approved values from the table.
SPECIAL: This specialized value set provides another flexfield as a value set for a single segment.
PAIR: This specialized value set provides a range flexfield as a value set for a pair of segments.
TRANSLATED INDEPENDENT: 
This works similar to Independent type. However, a Translated Independent value set can contain display values that are translated into different languages.
TRANSLATED DEPENDENT: 
This works similar to Dependent type. However, a Translated Dependent value set can contain display values that are translated into different languages.

inventory interview question

Question:

How Many Key Flex Fields Are There In Inventory?
Answer :
Seven KFF are there in Inventory:
Account Alias
Item
Item Category
Item Catalogues
Stock Locators
Sales Order : This is used during material transaction when source is Sales Order.
Segments are Sales order Number. Sales Order Type. Sales Order Source.
Service Items

Question:

What Is The Difference Between Purchased And Purchasable Flag For An Item?
Answer :
purchased flag decides whether item is able to purchasable and receivable or not
purchased is enabled: item can be received
purchasable flag decides whether the item is orderable or not in PO
If purchasable is enabled:item can be ordered in a purchase order
if not:new purchase orders can’t be created and approved for the items.

Question:

 What Is The Valuation Accounts Used In Inventory?
Answer :
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.
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.

Question:

What Is The Different In Mo Issue And Mo Transfer?
Answer : (MO-move order)
MO Issue will move out the stock from inventory against an account.
MO transfer will move the stock from one sub inventory to other Sub inventory.

Question

How A Mo Is Diff From Subinv Transfer?
Answer :
Move order is generally request of movement of items in one organization.
there we have involved steps like create MO, Approved Mo, Allocated MO,Transact MO
We have different types of move orders
requisition move order
replenishment move order
pick wave move order
possible to perform MO issues also. there we will get transaction number.
Subinventory transfer there you haven't get any transaction number/id
purpose of move order/ subinventory is moving the material from one sub inventory to another sub inventory within the organization.

Question:

What Is Net Table In Sub Inventory and non-nettable sub inventory ?
Answer :
nettable sub inventory:
To consider the onhand of the sub inventory as available for planning tasks.
non-nettable sub inventory:
we cant able to make future plans by using non-nettable sub inventory.

Question

When Can You See Such Scenario,
Item Available To Qty Is 0 But Available To Transact More Than 0?
Answer :
If item is not resolvable
If Sub inventory Allow reservation is not allowed
If Item is lot controlled and lot is expired

Question:

What Is A Transaction Type?
Answer :
Transaction Source Type
Transaction Action
Transaction Type
A transaction type is a combination of a transaction source type and a transaction action. It is used to classify a particular transaction for reporting purposes.
Ex: Sales order issue (txn type) + issue from stores (txn action) = sales order (txn source type).
Move order transfer (txn type) + sub inventory transfer (txn action) = move order (txn source type).
transaction types:
transaction source types come seeded with Oracle Inventory:
Purchase Order
Account Alias
Move Order
Internal Order
Standard Cost Update
Internal Requisition
Sales Order
Cycle Count
Periodic Cost Update
Physical Inventory
Account
RMA (Return Material Authorization)
Inventory
Job or Schedule
we have 6 transaction actions in oracle inventory.
issue from stores
receipt into stores
direct transfer
intransit
subinventory transfer

Question:

Describe Various Inventory Transaction Types?
Answer :
Miscellaneous transaction:
transaction is used to do adjust the the quantity through miscellaneous transaction we can increase/ decrease the quantity
Sub inventory transfer: used to transfer goods from one sub inventory to another within the same inventory organization.
InterORG transfer: This transaction is used to transfer goods from one inventory organization to another inventory organization with in the operating unit.
Receiving transaction: This transaction is used to move goods from receiving dock to specified sub inventory and locator.

Question:

Which Tables Are The Transcriptional Details Are Stored?
Answer :
MTL_MATERIAL_TRANSACTIONS
after completion of the transaction those records will be stored in the MMT table.
MTL_TRANSACTIONS_INTERFACE
when we perform interface trip stop program where the data moved from interface table to MMT table
MTL_MATERIAL_TRANSACTIONS_TEMP
where the pending transactions stored in the table
MTL_TRANSACTION_ACCOUNTS
where transaction related accounts stored in the table

Oracle Inventory Period Closure - Inventory Accounting period

 

 

 Inventory Periods:

 
Accounting Close Cycle > Inventory Accounting Periods

 

Inventory period closure we have 3 main tabs where we should have to maintain records as Null

 

Resolution Required:    

 

Here we have to provide solution for closure the inventory periods. If any data exist in these fields. Inventory will not allow for closing the periods.

 

• Unprocessed material

There are transactions on Unprocessed material transactions that can be stored in MTL_MATERIAL_TRANSACTIONS_TEMP table

View Transactions->Pending transactions

• Uncosted material/WSM

There are transactions in the MTL_MATERIAL_TRANSACTIONS table with unprocessed accounting entries

Check Cost managers are running properly and also validate the cost flag for processed transactions.

MTL_MATERIAL_ TRANSACTIONS where the costed_flag = ‘N’ or ‘E’ (N-NO E-ERROR)

to see those information in front end use the navigation
 View Transactions> Material Transactions

• Pending WIP Costing

Transactions that are unprocessed resource and overhead accounting transactions in the WIP_COST_TXN_INTERFACE table

• Pending WSM interface

There are pending transactions in the WSM_SPLIT_MERGE_TXN_INTERFACE table. 

• Pending LCM Interface transactions 

There are pending transactions in the CST_LC_ADJ_INTERFACE table. 

 

Unprocessed Shipping Transactions:

Here we have to provide solution for closure the inventory periods. If any data exist in these fields. Inventory will not allow for closing the periods.

 

If delivery does not get interfaced and struck in “shipped” there we could see the data in unprocessed shipping transactions

 
OM module > Shipping > Transactions

table name:
WSH_DELIVERY_ DETAILS
Shipping or OM> Interface > Run > Trip Stop SRS to run the Trip Stop interface

Resolution Recommended:

Here, if we have any records exist system still allow for closure the period for the month. Whatever the data exist and we are closing inventory periods, those transaction would be carryforward to next month.

• Pending Receiving:

PO Receipt Transactions that are error out.
Receiving transactions are always using interface table. Sometimes random transaction will be error out some unexplained reasons.

table name:
RCV_TRANSACTIONS_ INTERFACE
table used to populated external receiving transactions

We could see data in “Transaction Status Summary” form.

• Pending Material:

If transaction data gets errored or pending it will get struck in transaction Open interface. There might be the cases of negative transactions and Wip issues, ship confirmation issues.

table name: 
MTL_TRANSACTIONS_INTERFACE

To see that information in front end use the navigation
Transactions> Transaction Open Interface

 

• Pending Shop Floor Move:

If any data get struck in pending move transactions, then it will have record exist in here, it will have WIP completion related issues.

 

VENKATESH MITTIKAYALA