FLEX FIELD

What is the difference between key flexfield and Descriptive flexfield?

Key Flexfield is used to describe unique identifiers that will have a better meaning than using number IDs. e.g a part
number, a cost centre etc
Desc Flex is used to just capture extra information.
Key Flexfields have qualifiers whereas Desc Flexfields do not.
Desc Flexfields can have context sensitive segments while Key flexfields cannot.
nd one more differenct that KFF displays li!e text item but DFF displays li!e [ ]
Which pr!ced"re sh!"ld be called t! enable a DFF in a f!rm?
F"D#D$%&'#F($).D$FI"$
*+(,&K -. /+(,&K#"0$/
,FI$(D -. /F,'0#FI$(D#"0$/
,11(#%2,'3#"0$ -. /11#"0$/
,D$%&#F($)#"0$ -. /DFF#"0$/
45
In +rief,
6e need to follow the following steps in your form7
a4 &reate a displayed field to hold your concatenated segment values *the 8 9 field4.
b4 &reate fields *normally hidden4 for each of the flexfield columns in your table *the
one used for your flex4.
c4 In the form:level 62$":"$6:F,'0:I"%3"&$,
call F"D#D$%&'#F($).D$FI"$,
setting +(,&K parameter to the name of the bloc! containing your 8 9 field,
the FI$(D parameter to the name of your 8 9 field,
the 11(#%2,'3#"0$ parameter to the short name of your application and the D$%&#F($)#"0$
parameter to the name of your descriptive flex.
In the form:level 62$":"$6:I3$0:I"%3"&$,
62$":;(ID3$:I3$0,
1'$:I"%$'3,
1'$:<1D3$,
1,%3:=<$'> and
1'$:=<$'> triggers place a call to F"D#F($).$;$"3 as follows7
F"D#F($).$;$"3 * /3'I??$'#"0$/45
where 3'I??$'#"0$ is the name of the trigger,
e.g. in the 1'$:=<$'> trigger .... F"D#F($).$;$"3*/1'$:=<$'>/45
Which pr!ced"re sh!"ld be "sed t! make the DFF read !nly at r"n time?
FND_DESCR_FLEX.UPDATE_DEFINITION()
What is the difference between flexfield #"alifier and se$ment #"alifier?
Flexfiled qualifier identifies segement in a flexfield and segment qualifier identifies value in a segment.
3here are four types of flexfiled qualifier
@4 +alancing segment qualifier
A4 cost center
B4 natural account and
C4 intercompnay
se$emtn #"alifier %&
@4 allow budgeting
A4 allow posting
B4 account type
C4 contral account and
D4 reconciliation flag
What are the c!mp!nents !f DFF 'like str"ct"re( se$ment)?
*!wmany +ey flexfiels are there in Invent!ry?
What is ,al"e -et?
;alue %ets define and store the valid items of data, which may be entered into a field. Key Flexfields,
Descriptive Flexfields and many standard fields use ;alue %ets. ,racle already comes with hundreds of
;alue %ets. 6e define additional ;alue %ets to support our own user:defined Key and Descriptive
Flexfields *although we may use any existing standard ;alue %ets if they suit our purpose4. In defining a
new ;alue %et, we are defining the physical format of valid data, which can reside in that ;alue %et. Data
in a ;alue %et can be of several types7
Independently loaded into a Vale Set (t!"o#! a $tanda"d %o"&).
Re$ident in a ta'le (to (!i)! (e di"e)t t!e Vale Set de%inition).
T!e"e )old 'e No Validation (any data )an #o into t!e %ield* 't $till $'+e)t to t!e %o"&attin#
"le$.)
Dependent on t!e ,ale o% data in a p"e)edin# Independent $e#&ent (loaded t!"o#! a
$tanda"d %o"&).
Ex% For %upplies E ccessories && in 31, we define ?$0%#?1,#%%I?"#%$3 value set for the
assignment set associated with that ,<.
Below are the setups need to be done before defining Items
Container Type:
Setp - Ite&$ - Containe" Type
Item Status:
Setp - Ite&$ - Ite& Stat$

Defining Picking Rule:
.o,e to Setp - Rle$ - Pi)/in#
Defining Item Types:
Setp - Ite&$ - Ite& type$

Item Templates:
Setp - Ite&$ - Te&plate$
T!en $ele)t Ne(

!er!iew of Item Categories:
Ite& Cate#o"ie$ de%ined to #"op ite&$ lo#i)ally a))o"din# to di%%e"ent )!a"a)te"$ and t!i$ i$ $ed %o"
di%%e"ent "epo"t$ and p"o#"a&$.
De%ine Ite& Fle0%ield$
De%ine Cate#o"ie$
De%ine Cate#o"y $et$
A$$i#n de%alt )ate#o"y $et$ to %n)tional a"ea$
A$$i#n ite&$ to )ate#o"ie$.
Define "le#field Structure for Categories:
Setp - Fle0%ield$ - 1ey - Se#&ent$
Define Categories:
Setp - Ite&$ - Cate#o"ie$ - Cate#o"y Code$
T!en $ele)t Ne(
Define Category Sets:
Setp - Ite&$ - Cate#o"ie$ - Cate#o"y Set$
Item Catalogs:
Ite& Catalo# i$ $ed to add de$)"ipti,e in%o"&ation to ite&$ and to pa"tition t!e ite& &a$te" into
di%%e"ent #"op$ o% ite&$ (!i)! $!a"e )o&&on )!a"a)te"i$ti)$.
On)e t!e p"o)e$$ o% de%inin# and )atalo#in# ite&$ i$ )o&plete* yo )an2
P"o,ide $tanda"d lan#a#e in "e%e""in# to ite&$* ena'lin# )o&panie$ in t!e $a&e ind$t"y to
)o&&ni)ate e%%e)ti,ely (it!ot needin# to na&e t!ei" ite&$ identi)ally.
Sto"e a detailed de$)"iption o% (!at an ite& i$ (it!ot !a,in# to e&'ed t!at &eanin# in t!e ite&
n&'e".
U$e de$)"ipti,e ele&ent$ a$ $ea")! )"ite"ia %o" ite&$.
Update t!e ite& de$)"iption (it! a )on)atenated ,ale o% t!e ite& )atalo# #"op in%o"&ation.
Find )o&&on e0i$tin# pa"t$ (!en de,elopin# an en#inee"in# p"ototype.
Setp - Ite&$ - Catalo# 3"op$
%ubinventory 3ransfer7
@. Does/nt 'equire pproval.
A. %uggested to use %I, when authoriFation of the
%ubinventories is same.
B. &an not be utomated.
0ove ,rder 3ransfer7
@. It is a request transfer.
A. 0, can be automated. $g. 0, *F?I to %tagging4 gets
generated when you perform 1ic! release in ,0.
B 'equires pproval.
C. 0, is suggested to use when authoriFation of
subinventories are different.
Q1. What is a Move Order transaction?
A1. Move Order is a request for a subinventory transfer or an account issue
also known as an account transfer. Move Orders allow planners and facility
managers to request the movement of material within the warehouse or facility
for replenishment, material storage relocations and quality handling, etc.
For all Move Orders the final result will be one of two supported transactions:
subinventory or account transfer. Subinventory transfer transactions may still
be initiated without utilizing the Move Order function if desired.
Q2. What Move Order source types are available?
A2. There are three Move Order source types:
A. Move Order Requisition
Generated by:
* Manually generated request inside Inventory
Navigation Inventory->Transactions->Move Orders
The requisition is a manually generated request for a Move Order.
May optionally utilize the approval processing - the requisition can
optionally go through an Oracle Workflow approval process before it becomes
a Move Order. If no approval process is used, the requisition becomes a move
order immediately.
B. Replenishment Move Order
Generated by:
* Kanban Cards when pull sequence calls for subinventory transfer
(intra-org Kanbans)
* Min Max Planning Report planned at the Subinventory Level
* Replenishment Counts
Replenishment Move Orders are pre-approved and ready to be transacted.
C. Wave Pick Move Order
Generated by:
* Sales Order picking
* Internal Sales Order picking
The Order Management pick release process generates move orders to bring
material from its source location in Inventory to a staging location, which is
defined as a subinventory. In other words, a subinventory transfer.
Wave Pick Move Orders are pre-approved and ready to transact. Pick slips can
also be generated for these Move Orders from Inventory with the release of the
Oracle Order Management module.
Q3. What are the components of a Move Order?
A3. The Move Order has three components:
*Move Order Header: Order Type Default Source
Order Number Default Destination
* Move Order Lines: Item Source
Project/Task Destination
Request Qty Completed Qty
* Move Order Line Detail: Item Destination Details
Lot/Serial/Locator
Quantity/UOM
Source Details
Move Order Header - Oracle inventory uses the Move Order header to store the
Move Order source type which refers to the entity that created the Move Order.
An Order could be a pick wave, sales order pick, a replenishment type (Kanban,
Min-Max, Replenishment Count) or a requisition. The Move Order header also
stores the default source and destination location in the event of a subinventory
transfer, or an account in the event of an account transfer. The header also
stores the Move Order number and the requested date.
Move Order Lines - Move Order Lines are the requests on a Move Order. They store
the item, requested quantity, completed quantity (for partially fulfilled Move
Order), a source and destination if known. The Move Order lines also include
any project and task references, if the organization is project manufacturing
enabled.
Move Order Lines Details - Move Order Lines Details contain the information
necessary to fulfill a particular request line. For instance, the material
locator, lot or serial control information will be contained at the line detail
level. These details are automatically populated by Oracle Inventory when
picking rules and item transaction defaults for destination locators have been
setup, or the user can manually fill in the details. It is highly recommended
that the item transaction defaults feature be set up in Release 11i:
Inventory->Setup->Transactions->Item Transaction Defaults
Q4. What is the basic process flow of a Move Order Requisiton?
A4. The Move Order process deploys the following steps:
* Create the Move Order for required material. You can manually create the
requisition or it may be automatically generated at Pick Release, Kanban
Replishment, Min-Max or Replishment Count reports.
* Approve the Move Order if required. There is a seeded Oracle Workflow for
Move Order Approvals. If approval is required then the Item Planner must
approve the Move Order Lines. All automatically generated Move Orders are
created with an automatic approval. If you do not desire to require
approvals in your Inventory Organization for manual Move Order Requisitions
then you must set your Time Out period parameter to '0' and the Time-Out
Action parameter to 'Approve'.
Navigation: Inventory->Setup->Organizations->Parameters
Choose the Inventory Parameters Tab.
* Detail the Move Order. Detailing is the process that uses Oracle Inventory
picking rules to determine where to source the material to fulfill a request
line. The detailing process fills in the Move Order Line Details with the
actual transactions to be performed and allocates the material to the Move
Order. You should not detail a Move Order too soon in the business process
because the detailing process for a Move Order creates pending transactions
and removes that quantity from an availability picture. Detailing should not
be done until you are ready to print a pick slip and actually move the
material.
* Print a pick slip if desired or push the Move Order Line Details to mobile
devices for transaction through the Move Order API - Move Orders
INV_Move_Order_PUB.
* You are now ready to transact the Move Order. You can transact all the order
lines at once or one detail line at a time as the items are moved. If you
transact less than the requested quantity, the Move Order will stay open
until the total quantity is transacted, or the Move Order is closed
or cancelled.
Q5. What new tables, forms or profile options are used with the Move Order
function?
A5.
TABLES
MTL_TXN_REQUEST_HEADERS
MTL_TXN_REQUEST_LINES
FORMS
Move Orders (INVTOMAI)
This form allows you to create and approve Move Orders by specifying
items, source and destination locations, quantities and other order
information.
This form includes the following windows:
Find Move Orders
Move Order Header Summary
Move Order Lines Summary
Transact Move Orders (INVTOTRX)
This form allows you to transact Move Orders and to view and update
sourcing information.
This form includes the following windows:
Find Move Order Lines
Transact Move Orders
Transact Move Order Line Details
PROFILE OPTION
TP:INV Move Order Transact Form
This profile option allows the Move Order transaction mode to be set as
either online, background or concurrent request.