ebs r12 interview questions
DESCRIPTION
EBS R12 Interview QuestionsTRANSCRIPT
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 etcDesc 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.And one more differenct that KFF displays like text item but DFF displays like [ ] .
Which procedure should be called to enable a DFF in a form?FND_DESCR_FLEX.DEFINE (BLOCK => 'BLOCK_NAME' ,FIELD => 'FORM_FIELD_NAME' ,APPL_SHORT_NAME => 'APP_NAME' ,DESC_FLEX_NAME => 'DFF_NAME' );
In Brief, We need to follow the following steps in your form: a) Create a displayed field to hold your concatenated segment values (the [ ] field).b) Create fields (normally hidden) for each of the flexfield columns in your table (the
one used for your flex).c) In the form-level WHEN-NEW-FORM-INSTANCE, call FND_DESCR_FLEX.DEFINE, setting BLOCK parameter to the name of the block containing your [ ] field, the FIELD parameter to the name of your [ ] field, the APPL_SHORT_NAME parameter to the short name of your application and the DESC_FLEX_NAME parameter to the name of your descriptive flex.
In the form-level WHEN-NEW-ITEM-INSTANCE, WHEN-VALIDATE-ITEM, PRE-INSERT, PRE-UPDATE, POST-QUERY and PRE-QUERY triggers place a call to FND_FLEX.EVENT as follows:
FND_FLEX.EVENT ( 'TRIGGER_NAME');where TRIGGER_NAME is the name of the trigger, e.g. in the PRE-QUERY trigger .... FND_FLEX.EVENT('PRE-QUERY');Which procedure should be used to make the DFF read only at run time?FND_DESCR_FLEX.UPDATE_DEFINITION()
What is the difference between flexfield qualifier and segment qualifier?Flexfiled qualifier identifies segement in a flexfield and segment qualifier identifies value in a segment. There are four types of flexfiled qualifier
1) Balancing segment qualifier 2) cost center 3) natural account and 4) intercompnay
segemtn qualifier :-
1) allow budgeting 2) allow posting 3) account type 4) contral account and 5) reconciliation flag
What are the components of DFF (like structure, segment)?Howmany Key flexfiels are there in Inventory?What is Value Set?Value Sets define and store the valid items of data, which may be entered into a field. Key Flexfields, Descriptive Flexfields and many standard fields use Value Sets. Oracle already comes with hundreds of Value Sets. We define additional Value Sets to support our own user-defined Key and Descriptive Flexfields (although we may use any existing standard Value Sets if they suit our purpose). In defining a new Value Set, we are defining the physical format of valid data, which can reside in that Value Set. Data in a Value Set can be of several types:
Independently loaded into a Value Set (through a standard form). Resident in a table (to which we direct the Value Set definition). There could be No Validation (any data can go into the field, but still subject to the formatting
rules.) Dependent on the value of data in a preceding Independent segment (loaded through a standard
form).
Ex: For Supplies & Accessories CC in ATP, we define GEMS_GPO_ASSIGN_SET value set for the assignment set associated with that OU.
Below are the setups need to be done before defining Items
Container Type: Setup Items Container Type
Item Status:
Setup Items Item Status
Defining Picking Rule:Move to Setup Rules Picking
Defining Item Types:Setup Items Item types
Item Templates:Setup Items Templates
Then select New
Overview of Item Categories: Item Categories defined to group items logically according to different characters and this is used for
different reports and programs. Define Item Flexfields Define Categories Define Category sets Assign default category sets to functional areas Assign items to categories.
Define Flexfield Structure for Categories:Setup Flexfields Key Segments
Define Categories:Setup Items Categories Category Codes
Then select New
Define Category Sets:Setup Items Categories Category Sets
Item Catalogs:
Item Catalog is used to add descriptive information to items and to partition the item master into different groups of items which share common characteristics.
Once the process of defining and cataloging items is complete, you can:
Provide standard language in referring to items, enabling companies in the same industry to communicate effectively without needing to name their items identically.
Store a detailed description of what an item is without having to embed that meaning in the item number. Use descriptive elements as search criteria for items. Update the item description with a concatenated value of the item catalog group information. Find common existing parts when developing an engineering prototype.
Setup Items Catalog Groups
Subinventory Transfer:1. Does'nt Require Approval.2. Suggested to use SI, when authorization of the Subinventories is same.3. Can not be Automated.
Move Order Transfer:1. It is a request transfer.2. MO can be automated. Eg. MO (FGI to Stagging) gets generated when you perform Pick release in OM.3 Requires Approval.4. MO is suggested to use when authorization 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.