Oracle Applications Interview Questions (FAQS)

Q1. What are Reminder notifications?

A: Once an approver doesn?t respond to approval notification for quite sometime, then a reminder notification can be sent out to the approver. You can send up to two reminders to an approver using the Timeout feature. You can also specify that after a certain period of time, the document be forwarded automatically to the next approver in the hierarchy. This feature has to be setup by you by changing the PO and/or Requisition approval workflow in Oracle Workflow Builder.

  

Q2. How do you setup the timeout feature?

A: In Oracle Workflow Builder, open the ?PO Approval? workflow (for purchase orders) or the ?PO Requisition Approval? workflow for requisitions. To enable the Timeout feature in the PO Approval workflow, modify the following activities in the Notify Approver sub process by entering a Timeout period in their Properties windows: 
Approve PO Notification, PO Approval Reminder 1, and PO Approval Reminder 2. 
To enable the Timeout feature in the PO Requisition Approval workflow, modify the following activities in the Notify Approver sub process by entering a Timeout period in their Properties windows: Approve Requisition Notification, Requisition Approval Reminder1, and Requisition Approval Reminder2. 

  

Q3. Any prerequisite for timeout to work?

A: Workflow Background Process must be running for the reminder notifications to be generated. Background process must be set to run periodically if you want the reminders to be regularly generated. Run this program with parameter ?Timeout? set as ?Yes?, and ?Item Type? parameter as ?PO Approval Process? or ?PO Requisition Approval Process? whichever appropriate. 

  

Q4. How do you generate the notifications for the documents that need to be started up in approval yet?

A: You can run ?Send Notifications For Purchasing Documents? program to search the documents that are incomplete, rejected, or in need of re-approval and send notifications to the appropriate people informing them about the document?s status. 

  

Q5. What are the different types of reminders that the notifications can be sent for?

A: When ?Send Notifications For Purchasing Documents? program is run, Notifications are generated regarding the following situations:
- POs and requisitions are Incomplete, Rejected or may require re-approval.
- POs and Releases require acceptance and acceptance is not yet received. ?Acceptance past due? notifications is sent if the acceptance required date is over and no acceptance is entered by this date. 
- RFQ's and Quotations are in status of In Process. 
- Active RFQ approaching expiration i.e. current date is between Due Date and Close Date. 
- Active Quotation approaching expiration.

General Information
Q: What are the Oracle Applications patch types?
A: All Applications patches are organized by aggregation level.

·                     Stand-alone (one-off) Patch: Addresses a single fix or enhancement. Stand-alone patches are released only when there is an immediate need for a fix or enhancement that cannot wait until an aggregate bundling is available. Although stand-alone patches are intended to be as small as possible, they usually include any dependent files that have changed since the base release in order to form a complete patch that can be applied by any customer. The actual number of files changed will depend on the current code level on the system to which the patch is being applied.

·                     Rollup Patch (RUP): An aggregation of patches that may be at the functional level, or at a specific product/family release level. For example, a Flexfields rollup patch contains all the latest patches related to Flexfields at the time the patch was created. A Marketing Family 11.5.9 rollup patch contains all the latest Marketing patches released since, and applicable to, 11.5.9.

·                     Mini-pack: An aggregation of patches at the product level. For example, Inventory Mini-pack G (11i.INV.G) contains all the latest patches for the Inventory product at the time the mini-pack was created. Mini-packs are named in alphabetical sequence such as 11i.INV.E, 11i.INV.F, 11i.INV.G, and so on. Mini-packs are cumulative. In other words, 11i.INV.G contains everything in 11i.INV.F, which contains everything in 11i.INV.E, and so on. The terms patchset and mini-pack are often used interchangeably. <

·                     Family Pack: An aggregation of patches at the product family level. For example, Financials Family Pack C (11i.FIN_PF.C) contains all the latest patches for products in the Financials family at the time the family pack was created. Family product codes always end in "_PF" and family packs are given alphabetical sequence such as 11i.HR_PF.B, 11i.HR_PF.C, and 11i.HR_PF.D. Family packs are cumulative. In other words, Discrete Manufacturing Family Pack G (11i.DMF_PF.G) contains everything in 11i.DMF_PF.F, which contains everything in 11i.DMF_PF.E, and so on.

·                     Maintenance Pack: An aggregation of patches for all products in the E-Business Suite. For example, Release 11.5.9 Maintenance Pack contains all the latest code level for all products at the time 11.5.9 was created. Maintenance packs are numbered sequentially such as 11.5.7, 11.5.8, 11.5.9, and are cumulative. In other words, 11.5.9 contains everything in 11.5.8, which contains everything in 11.5.7, and so on.

In addition to releasing a maintenance pack, Oracle also packages a new Rapid Install at each maintenance pack release level. So Applications Release 11.5.9 Rapid Install contains the same applications code level that a customer would get if they applied the Release 11.5.9 Maintenance Pack on an earlier 11i release level. Note that the technology stack could still be different since Rapid Install includes the latest certified technology stack, but the maintenance pack includes only Applications code.

Patches can also be organized by purpose.

·                     Diagnostic Patch: Used to gather additional information when a product failure cannot be reproduced by Oracle. The additional information will assist Oracle Support Services and Oracle Development in resolving the failure.

·                     Interoperability Patch: Allows Oracle Applications to function properly with a newer version of the technology stack. Interoperability patches are typically required with new version of the database or Applications technology stack.

·                     Translated Patch: A non-English version of a patch. Release 11i supports 30 non-English languages. Customers who are using languages other than English, need to apply the corresponding translated patch(es) for the languages they are using in addition to any base US patch(es).

·                     Merged Translation Patch: Provided in real time (without requiring a translator) in the event a translated patch is not available when a customer needs it. A merged translation patch is applied just like a fully translated patch. The fully translated patch is escalated and is usually available within 24 hours. It can be applied safely on  of a merged translation patch.

·                     Translation Fix: Provided in the event a translation word choice is inappropriate. A translation fix is applied just like a translated patch, except there is no corresponding base US patch.

·                     New Feature Patch: Introduces new functionality and/or products. It is applied using standard patching utilities.

·                     Consolidated Update: Improves and streamlines the upgrade and maintenance processes by consolidating certain post-release patches. Most recommended patches and rollups for a particular maintenance release are consolidated into a single patch that is installed immediately following the Maintenance Pack or the Rapid Install.

·                     Family Consolidated Upgrade Patch: All upgrade-related patches consolidated from all the products within a product family. Family consolidated upgrade patches are released as needed and are only available for upgrading to Release 11i from Release 10.7 or 11.0. TheOracle Applications Release Notes lists the most recent patches.

·                     Documentation Patch: Updates online help.

Q1. Why does the create releases process not create a Release when we have run the CREATE RELEASES program against a Blanket Purchase Order whose EFFECTIVE DATES are in the future with a valid Sourcing Rule?

A: The CREATE RELEASE program must be run within the EFFECTIVE DATES of the Blanket Purchase Order. This is because the program verifies whether the SYSTEM DATE falls within the EFFECTIVE DATES, when looking for the Releases to be created. This is a standard functionality.

  

Q2. Why can�t we create a release of a blanket purchase order, When there exists a valid BPA and in the release form we pick the blanket PO from the list of values (LOV). Once selected, we cannot tab past that field and does not get any error messages.

A: Check for the invalid objects in the database. Invalid objects can prevent improper screen field action. There are numerous packages and library handling code that the form utilizes.

  

Q3. When we try to run Requisition import after running a Min-Max planning request why is it that requisitions are created from Requisition import but no releases are created against blanket POs.

A: For Releases to get created automatically in the Requisition Import process: 
- Check for the profile option PO: Release During Requisition Import which should be set to 'Yes� to create releases during requisition import. 
- 'Sourcing Rule' must have current date between 'effective date' and 'to date'. 
- Check that the requisition is sourced with the blanket, and the requisitions are approved as part of the Requisition Import process. 
- If the Encumbrance is ON, then the requisition will not get approved and will be in pre approved status and hence release will not get created. 
- Check the profile option MRP: Purchasing By Revision (If requisitions are coming from MRP) and INV: Purchasing By Revision (If requisitions are coming from INV). This must be set according and should not be null. This profile option must be set to 'Yes' or 'No' according to the customer�s requirement. 
- Verify the table PO_REQUISITIONS_INTERFACE, column AUTOSOURCE_FLAG is �Y�. 
- Verify if this item has a blanket purchase agreement approved and it is not closed or cancelled. 

  

Q4. Why are we able to create releases against a Blanket Purchase Order even though the sum of amount of all the releases that have been created is equal to the amount on the Blanket Purchase Order?

A: Oracle Purchasing does not do any validation on the agreed amount limit on the Blanket until approval of the release.

  

Q5. Why is it so that even though the Release is not approved, the amount against this release is on the blanket gets updated?

A: This is standard functionality. As soon as a release is created, the amount released on the blanket gets updated. In fact the amount released is not stored anywhere, system always calculates It whenever the blanket is queried.

 

Q6. Why are the releases not getting generated automatically after the requisition import is run successfully for those requisitions, which are created from MRP?

A: Check that the Release Time Fence on the item in setup is defined. Creating a Release Time Fence on the item in setup solves the problem. The Release Time Fence on the item must fall within the established schedule in MRP. The Release method should be set to Automatic Release.

 

Q7. Why is the Reqimport Automatically Creating Releases Although Profile PO: Release During ReqImport is set to No?

A: This might be because of the Incorrect WorkFlow attribute setting. Check the attribute "Is Automatic Creation Allowed" in the work flow process. This should set to N. Then the release is not created automatically

 

Q8. Why is the amount released on the blanket PO is not updated and still includes the amount of the cancelled release after a release is cancelled?

A: Released amount of the blanket PO is not automatically updated if an invoice was previously matched and not cancelled before the release was cancelled.

 

Q9. Why is the Create Releases program, PORELGEN is not creating any releases for requisitions, which are sourced to blanket agreements and have been generated from a template?

A: The Source details on the requisition line have not been populated. The Create Releases program will only create a releases if the Source Document Number has been populated on the requisition line. When creating a requisition template, if you manually enter the item line there is no where to enter the blanket information. When the requisition is created from the template, the Source details on the requisition line are left blank so the Create Release program does not select the requisition. Instead of entering the lines manually while creating the template, use the Copy button, enter the type as Purchase Order and enter the blanket agreement number. The Source details will be correctly populated with the blanket agreement number and the requisition will be picked up by the Create Release program.

 

Q10. Is the user allowed to modify quantity on distribution zone of an approved and reserved release?

A: Oracle Purchasing does not allow the user to modify the quantity on the distribution of an encumbered shipment nor does it allow creation of new distributions against encumbered shipments.

 

Q11. Is the user allowed to delete an Incomplete Release?

A: Yes, The users are allowed to delete the incomplete releases in the application.

 

Q12. Can we save and approve blanket PO releases without entering promised and need-by date?

A: If the item is either MRP/DRP, MPS/DRP or DRP planned item the promised date or need by date is mandatory and the user has to enter the date. If the item is not planned, then it is not mandatory.

 

Q13. Can the users enter the P-Card number in the Enter Releases Form?

A: No. The users can not enter the P-Card number the core apps. A P-card may be specified in iProcurement, but is only a display only in Core Apps. We can see the P-Card data if the profile option PO: Use P-card in Purchasing is set to YES.

 

Q14. Can we cancel the releases if they are in 'incomplete' status?

A: Cancellation is an authorization provides to revert back the approved status. If we cancel the 'Incomplete' release we will loose the traceability of the document actions. Hence we will not be able to cancel an incomplete release.

  

Q15. Does the Blanket Purchase Orders get Automatically closed After the Release is Fully Received and Invoiced?

A: The Blanket Purchase Orders will not automatically close after the Release is fully received and invoiced. The roll-up of closed status for the Blanket Release Shipment happens to the Blanket Release Header and not to Blanket Purchase Order. This is the Standard Functionality.

  

Q16. What is the significance of "PO: Convert Requisition UOM to Source Document UOM" profile option?

A: Earlier in Autocreate if the requisition UOM is different from the BPA UOM the user would not be allowed to create a release. But in Create releases program this was possible. To make the behavior consistent we have introduced this profile option. If this profile is set to yes we allow the autocreation of the release with the quantity and UOM converted to that of the BPA. If the profile is set to yes we do not allow the creation of the req both in autocreate as well as the create releases program.

  

Q17. Doesn't the Create Releases report support one time items? Is this a bug?

A: Create Releases report does not support one time items. This is the intended functionality. This is not a Bug.

  

Q18. Is it correct functionality that the enter req form will not raise a warning when the item is tied to a BPA when the selection is made from the catalog via a Requisition Template?

A: Yes this is the correct functionality. We do not raise a warning when the item is tied to a BPA when the selection is made from the catalog via a Requisition Template. There is already an ER 690225, which is logged for this issue.

FAQ Details

Q1. Why doesn't cancel PO automatically cancel assigned requisition, even when the checkbox 'Cancel requisition' is checked?

A: The intended functionality is that when a PO is canceled and the cancel requisition option is selected, it only cancels the backing requisition lines not the header. So only requisition lines will get canceled not the header.

  

Q2. Why do I get an APP-14056 error when canceling a PO shipment that has been matched?

A: Please check to see if the shipment being canceled is not Over Billed [billed more than received]. In that case it cannot be canceled.
  

Q3. Why doesn't 'Canceling of Standard PO' change the status of the document? The Status stays in value 'Approved'.

A: The authorization status remains Approved. Even if PO is canceled, only the canceled flag is set to 'Y'. It is intended functionality.

  

Q4. Can I automatically 'Close' the Purchase order without receiving the full quantity?

A: The Receipt Close Tolerance lets you specify a quantity percentage within which Purchasing closes a partially received shipment. For example, if your Receipt Close Tolerance is 5% and you receive 96% of an expected shipment, Purchasing automatically closes this shipment for receiving.

  

Q5. When does a Purchase Order line get Closure Status 'Closed for Receiving'?

A: Purchasing automatically closes shipments for receiving and invoicing based on Tolerances that you specify in the Purchasing Options window. Once all shipments for a given line are received and invoiced within these tolerances, Purchasing automatically closes the line. 

  

Q6. When does a Purchase order get Closure Status 'Closed'?

A: When all lines for a given header are closed, Purchasing automatically closes the document.

  

Q7. What is the difference between the control actions 'On Hold' and 'Freeze' for a Purchase order?

A: You can place a Purchase order 'On hold' only at the header level. This unapproves the purchase order while preventing printing, receiving, invoicing, and future approval until you remove the hold. You can 'Freeze' only at the header and release level. You freeze a Purchase order when you want to prevent any future modifications to the Purchase order. When you freeze a Purchase order, you can still receive and pay for goods you already ordered. If you use a Requisition template or AutoSource to source requisition lines from a Purchase order line, Purchasing does not automatically update the corresponding sourcing information when you freeze a purchase order with which you source requisition lines. If you freeze a purchase order, you have to update the corresponding information in the Requisition Templates or the AutoSource Rules window.

  

Q8. What are the different document statuses/actions used in Oracle Purchasing?

A: This discusses mainly the statuses/actions of a purchase order:
Delete
Before documents are approved, you can delete them or their components from the document entry window. If you use online requisitions, Purchasing returns all requisitions associated with your delete action to the requisition pool. You can reassign these unfilled requisitions to other purchase orders or releases using the AutoCreate Documents window.

Cancel
Purchasing lets you terminate an existing commitment to buy from a supplier by canceling document headers, lines, shipments, or releases. When you cancel a purchase order entity, you are unable to receive or pay for cancelled items and services, however, you can pay for all previously received orders. You also cannot modify a cancelled entity or its components.

Final Close 
Prevent modifications to or actions against completed documents, lines, and shipments by final closing them. Final-closed documents are not accessible in the corresponding entry forms, and you cannot perform the following actions against final-closed entities: Receive, Transfer, Inspect, Deliver, Correct receipt quantities, Invoice, Return to supplier, or Return to receiving.
You can approve documents that include final-closed entities, but you cannot approve documents that are final closed at the header level. You can print final-closed documents. Finally, you can Purge documents that were final closed at the header level before the Last Activity Date that you specify when you submit Purge.

Freeze
Freeze your purchase orders and releases to prevent changes or additions while maintaining the ability to receive and match invoices against received shipments. You cannot access frozen documents in the entry forms.

Hold
Place documents on hold to un-approve them while preventing printing, receiving, invoicing, and future approval until you remove the hold.

Firm
When you firm an order, Master Scheduling/MRP uses the firm date to create a time fence within which it will not suggest new planned purchase orders, cancellations, or reschedule�in actions. It continues to suggest reschedule�out actions for orders within the time fence. If several shipments with different promised or need�by dates reference the same item, Master Scheduling/MRP sets the time fence at the latest of all scheduled dates.
You can firm orders at the document header or shipment level. If you firm at the header level, Purchasing applies this control to every shipment on the document.

Close
Purchasing automatically closes shipments for receiving and invoicing based on controls that you specify in the Purchasing Options window. Once all shipments for a given line are closed, Purchasing automatically closes the line. When all lines for a given header are closed, Purchasing automatically closes the document.

Close for Receiving
The Receipt Close Tolerance lets you specify a quantity percentage within which Purchasing closes a partially received shipment. For example, if your Receipt Close Tolerance is 5% and you receive 96% of an expected shipment, Purchasing automatically closes this shipment for receiving.
The Receipt Close Point lets you choose which receiving action (Received, Accepted, or Delivered) you want to use as the point when Purchasing closes a shipment for receiving based on the Receipt Close Tolerance. For example, if you set a Receipt Close Tolerance of 5% and choose Delivered as your Receipt Close Point, Purchasing closes shipments for receiving when you have delivered 95% or more of the ordered quantity.

Close for Invoicing
The Invoice Close Tolerance lets you specify a similar quantity percentage within which Purchasing automatically closes partially invoiced shipments for invoicing.

Open
You can open at the header, line, and shipment levels.

Open for Receiving
You can reopen for receiving at the header, line, and shipment level.

Open for Invoicing 
You can reopen for invoicing at the header, line, and shipment level.

Unfreeze
You can unfreeze only at the header and release levels.

  

Q9. Will shipment of a PO be cancelled if these conditions are met?

A: Shipment Checks:
Quantity received >= quantity ordered -> Fully received
Quantity billed >= quantity ordered -> fully billed
Distribution Checks:
Quantity billed > quantity ordered -> over billed
Quantity delivered > quantity ordered -> over delivered

If you partially received a shipment corresponding to multiple distributions, Purchasing cannot always cancel the shipment. To make sure Purchasing can cancel a shipment, enter the delivery transactions for the receipts you entered against that shipment. You can use express delivery to facilitate this process.
No records in receiving interface for this entity being cancelled. The ASN for this entity being cancelled should be completely received.

  

Q10. What are need to be tried If USER_EXIT error is raised when 'Canceling'?

A: Regenerate the message file. 
Disable all the custom triggers.
Check the quantities whether they are matching with the conditions.

  

Q11. Why Closed Code is set to 'I' when Cancellation failed with user exit error?

A: When using encumbrance, the funds checker will be called before canceling the document. Fund checker will change the cancel flag to �I�. Now the cancellation code will process the record and change the cancel flag to �Y�. In our case the fund checker went through fine. But it failed in the cancellation code.

  

Q12. Is there anyway I can revert back the document if a Purchase Order/Requisition is cancelled accidentally?

A: No. The cancellation is a non-reversible process. Once the document is cancelled we cannot revert it back.

  

Q13. Can I Receive a shipment even when it is "Closed for Receiving"?

A: Yes, it does not prevent you from receiving.

  

Q14. Can a Closed / Finally Closed Purchase Order be reopened?

A: You can Open a Closed purchase order but you cannot take any control action on Finally Closed PO.

  

Q15. Can I match an Invoice against a line even when it is 'Closed for Invoicing'?

A: The Close for Invoicing status does not prevent you from matching an invoice to a purchase order or to a receipt.

  

Q16. What are the valid Statuses/Actions for Requisitions?

A: For requisitions, the only available actions are Cancel and Finally Close.