Oracle Apps – SCM Functional Interview Questions & Answers

Oracle Apps – SCM Functional Interview Questions & Answers

What is a DFF?
Descriptive Flexfield (DFF) is a tool that lets to create new fields in the forms.

Is the DFF’s are flexible?
DFF are flexible.

Example: Depending upon the value in a field, it can made as either Field1 or Field2 to appear in DFF. 

Can these new fields be added without modifying / customization of the screen?

Yes. Only some setup is needed to setup the DFF.

Can these new fields that get created as a result of DFF free text that is whether end user can enter any junk into the new fields that are added via DFF?
If user attach a value set to the field (at time of setup of dff), then field will no longer be free text. The entered value in the field will be validated, also a list of valid values will be provided in LOV. 

Will the values that entered by the user in DFF fields be updated to database?
Yes, this happens because for each field that you create using DFF will be mapped to a column in Oracle Applications.

Can user create a DFF on any database column?
Not really. Oracle delivers a predefined list of columns for each table that are meant for DFF usage. Only those columns can be mapped to DFF segments. These columns are named similar to ATTRIBUTE1, ATTRIBUTE2 and ATTRIBUTE3 etc... Usually Oracle provides upto 15 columns, but this number may vary. 

Can user add hundreds of fields to a given screen?
This depends on the number of attribute columns in the table that screen uses. Also, those columns must be flagged as DFF enabled in DFF Registration screen. Don’t need to worry much about this because all the ATTRIBUTE columns are by default flagged for their DFF usage.

Is DFFs are related to table and columns?
Yes, each DFF is mapped to one table. And also each segment (or call it field) is mapped to one of the attribute columns in that table.

Is it possible to appear these fields in screen only when certain conditions are met?
Yes, based on Context Sensitive Descriptive Flexfields

Oracle Apps - Query to list the responsibility to which the concurrent program is assigned

Oracle Apps - Query to list the responsibility to which the concurrent program is assigned

Query to find the responsibilities to which the concurrent program is assigned.

select    frt.responsibility_name, 

frg.request_group_name, 

frgu.request_unit_type, 

frgu.request_unit_id, 

fcpt.user_concurrent_program_name 

from      fnd_Responsibility fr, 

fnd_responsibility_tl frt, 

fnd_request_groups frg, 

fnd_request_group_units frgu, 

fnd_concurrent_programs_tl fcpt 

where   frt.responsibility_id = fr.responsibility_id 

and        frg.request_group_id = fr.request_group_id 

and        frgu.request_group_id = frg.request_group_id 

and        fcpt.concurrent_program_id = frgu.request_unit_id 

and        fcpt.user_concurrent_program_name = :P_CONCURRENT_PROGRAM_NAME

order by 1,2,3,4

Oracle SCM Functional Interview Questions & Answers - Inventory Module – Part XI

Oracle SCM Functional Interview Questions & Answers - Inventory Module – Part XI

What is the “mtl_transactions_interface” table used for?
This table is an Interface table used between non-Inventory applications and the Oracle Inventory Transactions module.
In other words any other module other than Inventory that needs to update the Inventory is processed through this table.

Modules such as Work In Progress (WIP) and Order Entry (OE) first inserts the records to the mtl_transactions_interface (MTI) for validation.

The Interface Manager called the Transactions Manager (INCTCM) which reads records from this table, validates them and moves the successful transactions into mtl_material_transactions_temp, and submits Transaction workers (sub-processes - INCTCW) which then processes these records through inventory. This process consists of data derivation, validation and transfer of records from mtl_transctions_interface, mtl_transactions_lots_interface and mtl_serial_numbers_interface into their respective temporary (temp) tables from where the transactions processor processes them.

What is the “mtl_material_transactions_temp” table used for?
“mtl_material_transactions_temp” is a temporary table, once the transactions have been passed to this table after initial validation by the Transactions Manager (INCTCM) from the “mtl_transactions_interface” table a job id is attached and Transactions Worker (INCTCW) is submitted by the INCTCM process in order to the get the records processed and moved to the “mtl_material_transactons” table.

This table is also used by Inventory Module and Purchasing module which inserts / updates directly into this table for any transactions entered within itself and each transaction in turn through a process of strict validation.    

What type of issues can been seen in the “mtl_transactions_interface” and “mtl_material_transactions_temp” tables?
The issues can be related to stuck transactions in these tables.
Below list of errors may be seen in the mentioned tables:

What type of issues can been seen in the “mtl_material_transactions” table?
“mtl_material_transactions” table is a transactional historical table.

Transaction is valued (unit cost*quantity = amount), once the data inserted into this table the transaction is almost complete except for the fact that it needs to have the costing details finally updated and inserted into the Transaction Accounts table for transfer to General Ledger.

However, it is the holding point for transactions to be cost.

What is purpose of “mtl_transaction_accounts” table?
The details of the transactions are usually inserted into this table as Debits and Credits and from here it is transferred to GL

What are the major tables involved in Material Movement for Inventory and WIP Material, Move, and Resource Transactions?
Major tables involved in material movement for inventory, WIP Material, Move & Resource Transactions are:
mtl_transactions_interface
mtl_material_transactions_temp
mtl_material_transactions
wip_move_txn_interface
wip_move_transactions
wip_cost_txn_interface

How to resolve the Pending Material Transactions?
Resolving Pending Material Transactions is a process of determining and fixing what is preventing a record from being processed through the “mtl_transactions_interface” table.

Details of pending transactions can be viewed through the application by navigating to the Transaction Open Interface form.
Using the Transaction Open Interface window, user can view, edit, correct and resubmit transactions received through the open interface.
There are five selections in the alternate region list of values: Error, Location, Source, Intransit & Other.

These provide detailed information to help the user to resolve the pending transactions.

In the Error alternate region:
a. The error code describes the error on the last attempt to process the line item.
b. The error explanation gives a reason for the error.
c. The process flag indicates whether the row has been processed by the concurrent manager.
The process flag status codes are:
1 = Pending
2 = Running
3 = Error

Resubmitting Transactions for Processing:
In the Transaction Open Interface window, check the Resubmit box next to the transaction that user wants to resubmit or choose Resubmit All from the Special menu. If user have many transactions to resubmit, use the Resubmit All button to select all transactions for processing and then selectively deselect individual transactions user don’t need to resubmit.

Save the work to submit the transactions for processing.

How to resolve Pending WIP Cost Transactions?
Resolving Pending WIP Cost transactions is a process of determining and fixing what is preventing a record from being processed through the “wip_cost_txn_interface” table Pending transactions can be viewed through the application by navigating to the WIP Responsibility > Pending resource transaction form.
In the Pending Resource Transaction window you can view, update, delete, and resubmit resource transactions that have failed validation and remain in the “wip_cost_txn_interface” table.

User can also resubmit transactions whose concurrent process has failed and have a processing phase of Complete and process status of Error. There are eight selections in the alternative region list of values: Processing, Source, Concurrent Request, Job or Schedule Name, Operation, Resource,
Transaction and Comments.

Error transactions will have the Transaction ID and Group ID populated and the Status will be error. Pending transactions will have the Transaction Id and Group ID fields blank and the Status will be pending.
To view error details for failed resource transactions, select the errored transaction and click on the Error button. The Pending Resource Transaction error window appears. Column indicates the name of the column in the resource transaction interface table “wip_cost_txn_interface” that failed validation. Message indicates why the transaction failed.

To resubmit failed resource transactions:
In the Pending Resource Transactions widow either check the transaction's Resubmit check box to resubmit one record or choose select All for Resubmit from the Special Menu then save the work.

In which column the PO number is inserted, when attempting to load legacy data into the “mtl_transactions_interface” table?
There is not a direct column for PO number. In the Oracle Manufacturing Implementation Manual, locate the section on Open Transactions Interfaces.  This section describes the transaction type id's and there is not a PO number. Refer to the column of transaction_reference and this column will allow the po number. The column is optional and shows up on reports and transaction displays. Since a column for the PO number does not directly exist, a transaction_reference field can be used to input this information.

Why is the distribution account ID required in “mtl_transactions_interface” table?
All issues and receipts of asset items to an asset subinventory and sales order shipments require the distribution account id that originates from GL code combinations. This account id is required to create a complete audit trail of the transaction.

Reference: Collected from various web sources.

Please do refer below links for Oracle SCM Functional interview questions & Answers on inventory module.

http://learnoraclecsbscm.blogspot.in/2015/05/oracle-inventory-scm-functional.html

http://learnoraclecsbscm.blogspot.in/2015/08/oracle-scm-functional-interview.html

http://learnoraclecsbscm.blogspot.in/2015/08/oracle-scm-functional-interview_9.html

http://learnoraclecsbscm.blogspot.in/2015/09/oracle-scm-functional-interview_28.html

http://learnoraclecsbscm.blogspot.in/2015/10/oracle-scm-functional-interview_10.html

http://learnoraclecsbscm.blogspot.in/2015/10/oracle-scm-functional-interview_12.html

http://learnoraclecsbscm.blogspot.in/2015/10/oracle-scm-functional-interview_13.html

http://learnoraclecsbscm.blogspot.in/2015/10/oracle-scm-functional-interview_16.html

http://learnoraclecsbscm.blogspot.in/2015/10/oracle-scm-functional-interview_19.html

http://learnoraclecsbscm.blogspot.in/2015/10/oracle-scm-functional-interview_24.html

Oracle Apps – Workflow Background Process Program

Oracle Apps – Workflow Background Process Program

Workflow Background Program:

Workflow background program is a concurrent program which is used to run for processing the deferred activities, notifications activities, wait activities, timeout activities & stuck processes using the specified input parameters. Based on the parameters the background engine executes all the activities & stuck processes. Any activities that are newly deferred or timed out or processes that become stuck after the current background engine starts are processed by the next background engine that is invoked by the concurrent program.

Workflow Background Process runs with the help of Workflow Background Engine which is PL/SQL Procedure which runs this concurrent program with specified parameters.

Workflow background process concurrent is available in both 11i & R12.

Navigation:

System Administrator Responsibility > View Requests > Submit a New Request

Parameters:

Item Type:

Specify an item type to restrict this engine to activities associated with that item type. If item type is not specified, the engine processes any activity regardless of its item type.

Minimum Threshold:

Specify the minimum cost that an activity must have for this background engine to execute it, in hundredths of a second.

Maximum Threshold:

Specify the maximum cost that an activity can have for this background engine to execute it, in hundredths of a second. By using Minimum Threshold and Maximum Threshold can create multiple background engines to handle very specific types of activities. The default values for these arguments are null so that the background engine runs activities regardless of cost.

Process Deferred:

Specify whether this background engine checks for deferred activities. Setting this parameter to Yes allows the engine to check for deferred activities.

Process Timeout:

Specify whether this background engine checks for activities that have timed out. Setting this parameter to Yes allows the engine to check for timed out activities.

Process Stuck:

Specify whether this background engine checks for stuck processes. Setting this parameter to Yes allows the engine to check for stuck processes.

Oracle R12 Purchasing – Track Requisition Number using Purchase Order Number:

Oracle R12 Purchasing – Track Requisition Number using Purchase Order Number:

The below query provides the related requisition number against the purchase order number:

Query to track Requisition number against Standard Purchase Order:

select prha.segment1 from po_requisition_headers_all prha, po_requisition_lines_all prla,po_distributions_all pda,  po_req_distributions_all prda, po_headers_all pha

where prha.requisition_header_id = prla.requisition_header_id

and prla.requisition_line_id = prda.requisition_line_id

and prda.distribution_id = pda.req_distribution_id

and pda.po_header_id = pha.po_header_id

and pha.type_lookup_code = 'STANDARD'

and pha.segment1 = :p_po_number

Query to track Requisition number against Blanket Purchase Agreement & Release:

select prha.segment1 from po_requisition_headers_all prha, po_requisition_lines_all prla, po_req_distributions_all prda, po_headers_all pha , po_releases_all pra, po_line_locations_all plla, po_distributions_all pda

where prha.requisition_header_id = prla.requisition_header_id

and prla.requisition_line_id = prda.requisition_line_id

and prda.distribution_id = pda.req_distribution_id

and pda.po_header_id = pha.po_header_id

and pha.type_lookup_code = 'BLANKET'

and pha.po_header_id = pra.po_header_id

and pra.po_release_id = plla.po_release_id

and prla.line_location_id = plla.line_location_id

and pha.segment1 = :p_po_number

and pra.release_num = :p_po_release_number

Types of Natural Accounts:

Types of Natural Accounts:

Accounting Definition:

A Systematic process of identifying, registering, measuring, classifying, verifying, summarizing, interpreting and reporting the financial information is called as Accounting.

It provides the profit or loss for a given period and the value and nature of a firm's assets, liabilities and owners' equity.

Accounting Equation:

Assets - What it owns

Liabilities - What it owes to others

Owner's Equity - Difference between assets and liabilities

In other words, the Accounting Equation can be rewritten as:

Balance Sheet:

Organizations which are registered under Government is obliged to disclose the above mentioned balance in a document which is called as Balance Sheet.

Types of Natural Accounts:

The types of natural accounts are:

1. Assets Account

2. Expense Account

3. Liability Account

4. Owner’s Equity Account

5. Revenue Account

In Oracle General Ledger, when we attach the “Natural Account” Flexfield Qualifier to a segment. System attaches the 5 nature on the Value form.

When we add the Natural Account Value, we have to define the nature of the account as well.

 

1. Assets Account:

An asset which is belongs to an organization used for future operations.

Example: Cash On Hand, Notes Receivable, Accounts Receivable, Other Receivable, Pre-paid Expense, Land, Equipment, Building, Bank Account, Purchase Area, etc…

Asset Account increases when it is debited and decreases when credited.

2. Expense / Cost Account:

Expenditure is incurred by the enterprise or organization to earn revenue.

Example: Salary, Wages, Repair Suppliers, Services, Rent.

Expense Account increases when it is debited and decreases when credited.

3. Liability Account:

Amounts owed by the organization to the outsiders except the owner of the organization.

Example: Bank Overdraft, Creditors, Accounts Payable, Notes Payable and Interest.

Liability Account increases when it is credited and decreases when debited.

4. Owner's Equity Account:

Owner's Equity is the total Claim by the owner against the organization.

Example: Capital.

Equity Account increases when it is credited and decreases when debited.

5. Revenue Account:

Revenue is the Monetary earning through the organization's primary business.

Example: Sale of Products, Services, etc.

Revenue Account increases when it is credited and decreases when debited.

The below table summarize the nature account credit & debit:

 

Oracle SCM Functional Interview Questions & Answers - Order Management Module - Part VI

Oracle SCM Functional Interview Questions & Answers - Order Management Module - Part VI

Question & Answers on Shipping & Execution

Define Release Rules:

Release Rules is defined as the criteria to be used during Pick Release. Only sales orders which meet the criteria and are eligible will be released. A Sales Order line is eligible if it has completed the prerequisite workflow activities, such as Schedule - Line or Create Supply.

Define Release Sequence Rules:

Release Sequence Rules determines the order in which inventory is allocated to sales orders. Users can choose to allocate by order, outstanding Invoice value, Scheduled Date, Departure Date & Shipment Priority.

The Sequence in which sales orders are filled could be very important. If a company has a problem of running out of material before all of their orders have been filled it is very important that they have filled their most important orders first.

Define Picking Rules:

Picking Rules which are created and maintained in Inventory, suggests which material to use, based on inventory controls such as Revision control, Lot control, FIFO (first in first out) or subinventory / locator picking numbers.

Picking Rule is an Item Attribute. Create a variety of picking rules and associate them with the appropriate items. If there isn’t a Picking Rule associated with the item, the system will use the Organization’s default Picking Rule which is defined in the Shipping Organization’s Parameters.

Define Pick Slip Grouping Rules:

Pick Slip Grouping Rules organize how released order lines are grouped on Pick Slips for ease of picking.

Example: By using the Pick Slip Grouping Rule "Sub-Inventory" the user can reduce the number of trips to a particular sub-inventory by grouping all lines for that sub-inventory on to one Pick Slip.

What Happens during Pick Release?

1. A pre-approved Move Order is automatically created in Inventory.

2. A Move order is a request for a subinventory transfer from the source subinventory to the destination (staging) subinventory.

3. A Move order is created for every Sales Order Line that has the status of “Awaiting Shipping” and passes the picking criteria.

4. The Destination subinventory is the Staging subinventory entered on the Release Sales Orders form or defaulted from the Shipping Parameters. Only one staging subinventory is allowed per Picking Batch.

Note: A Picking Batch is the total number of Order Lines that were released at one time.

Inventory uses the move order to manage material requisitions within an Organization.

Other options during Pick Release:

Allocate Inventory to the move order:

Allocating can be done automatically after the move order is created by setting “Auto Allocate” to yes on the Release Sales Order form or postponed until later, then manually allocated from the Transaction Move Orders form.

The Release Sequence Rule, that was entered on the Release Sales Orders form, or defaulted from the Shipping Parameters, will be used to determine in what sequence to fill the move orders.

Pick Confirm the move order:

Pick Confirm can be done automatically during the picking process by setting “Pick Confirm” to yes on the Release Sales Orders form or by unchecking the Pick Confirm Required checkbox in the Organization Parameters form. If it is not done automatically during pick release it can be done manually from the Transaction Move Orders form by selecting the Transact button.

The Pick Confirm transaction executes the subinventory transfer, moving the material from it’s source location to it’s destination staging location. Only 1 staging subinventory is supported per picking batch.

Auto Create Deliveries – Optional:

A delivery is required in order to Ship Confirm. User can select to have the Picking process automatically group the delivery lines into deliveries to expedite this process.

Reference: Collected from various web sources

Please do refer:

http://learnoraclecsbscm.blogspot.in/2015/05/oracle-scm-functional-interview.html

http://learnoraclecsbscm.blogspot.in/2015/05/oracle-scm-functional-interview_14.html

http://learnoraclecsbscm.blogspot.in/2015/08/oracle-scm-functional-interview_22.html

http://learnoraclecsbscm.blogspot.in/2015/08/oracle-scm-functional-interview_23.html

http://learnoraclecsbscm.blogspot.in/2015/09/oracle-scm-functional-interview.html