Join the OracleApps88 Telegram group @OracleApps88to get more information on Oracle EBS R12/Oracle Fusion applications.

If you are facing any issues while copying the Code/Script or any issues with Posts, Please send a mail to OracleApp88@Yahoo.com or message me at @apps88 or +91 905 957 4321 in telegram.

Monday, September 9, 2013

Oracle Applications Interview Questions (FAQS)



Q1. Does autocreate copies descriptive flexfields from the requisition to the document you create? 

A: Yes, but it does not validate the information. For example: If in the requisition desc flex is not mandatory and in the purchase order it is mandatory, autocreate will not error out. It will just copy as is.

  
Q2. Does autocreate copy Notes from the requisition to the document you are creating?

A: Yes, Notes are copied from the requisition lines and the corresponding requisition header. 
  
Q3. What are the columns on which autocreate combines the requisition lines into a single document lines?

A: For purchase order, Purchasing combines the quantities of all requisition lines that have the same item, item revision, line type, transaction reason, and unit of measure onto a single document line. For RFQ�s, quantities of all requisition lines that have the same item, revision, and line type are combined.

  
Q4. What price becomes the actual price in case multiple requisition lines with different prices are combined to single PO line?

A: The lowest unit price from the combined requisition lines becomes the actual price of the purchase order line. 

  
Q5. What are the columns based on which Shipping information is combined in case of autocreate? 

A: For purchase orders and releases, Purchasing combines shipment information only if the requisition lines have the same need�by date, ship�to location, organization, Accrual type (period�end or on�line), and shipment type 

  
Q6. Does autocreate add to an existing PO shipment that has been encumbered? 

A: Purchasing does not add to an existing purchase order shipment if that shipment has been encumbered even though all the grouping columns necessary to combine shipping information are there. 

  
Q7. What can be done to open the created document directly once autocreate is done successfully?

A: Set the profile option PO: Display the autocreated Document to Yes, Purchasing displays the Purchase Orders, Releases, or RFQ window, as appropriate, after creating your document lines. 

  
Q8. Can requisition line with item number and without item number [one time item] be combined to single document line in autocreate?

A: If you want to combine two requisition lines for the same item, one with an item number and one without, you have to manually autocreate the document and use Modify on the Tools menu to add the predefined item to the requisition line for the one�time item. 
Note: You cannot use Modify with outside processing items or if you are using encumbrance or budgetary control.
 

  
Q9. Can you autocreate a release if the description of the requisition created in PO is different of the description of the Blanket? 

A: No, If we do not choose an item, that is if the requisition and blanket are created with one time/expense items the autocreate process tries to match the descriptions as item id's are null. The only differentiating factor in one time items (item id null) is the description. 

  
Q10. How do you prevent autocreate from seeing requisitions from another organization? 

A: Requisitions and Purchase Orders are not organization specific. If you do not want to be able to see or access requisitions across different organizations, then you need to set up different operating units with different responsibilities tied to each one. 

  
Q11. Can you autocreate from a quotation and tie the PO to the associated quotation and requisition?

A: Yes, you can autocreate from a Quotation.
Navigation:
 
1. Create and approve a requisition.
 
2. Go to the AutoCreate Screen, chose the requisition form the pool of approved requisitions.
3. Change the Document Type field to RFQ and click the automatic button.
 
4. The RFQ is created and appears on the screen.
5. Enter the required fields on the RFQ (quote affectivity), click on the Supplier button and choose the list of suppliers.
 
Change status to active and save.
 
6. To enter the vendor responses a Quote must be created.
 
Go to the RFQ screen and query up the RFQ you just created.
 
Click Special on the Tool bar and choose Copy Document.
 
This will create your quotation.
 
7. Go to the Quotation screen and query up the new quotation and enter
 
the price break information. Change the description (if PO attribute is set to allow the description to be changed).
 
8. Approve the quotation.
 
9. AutoCreate the PO from the requisition.
 
Delete the description if the quote has a description different than the requisition
 
Click on the catalog button - Receive message
 
Your can update only the price for the saved record.
 
Open the Catalog to select price only
 
Click YES
 
10. Select the quote.
 
11. You will now have both the requisition and quote tied to the PO.
 

  
Q12. Where does the note to buyer show on an autocreated PO? 

A: On the AutoCreate form, go to the Folder menu and choose Show Field. Select Note to Buyer and click OK. The field will now be displayed. 
If you would like this field to be displayed every time you use autocreate, go to Folder -> Save As... Give the folder a name and check the Open as Default box.
 

  
Q13. Does the supplier name from a requisition get carried over to an autocreated purchase order? 

A: The standard functionality is that if the requisition has a the "suggested supplier name" field populated, it would carry over to the autocreated PO. The "suggested supplier name" field will only carry to the autocreated PO if it was selected from the list of values on the requisition. If it is typed in manually, it will not carry over. 

  
Q14. What causes the app-14090 error when autocreating a requisition?

A: There are several things that must be performed to address this issue: 
* Profile Option in MRP must be set as follows:
 
- MRP: Sourcing Rule Category Set value must be set to Purchasing in the Purchasing application.
* AutoCreate Blanket PO 
- Revisions do not default for Items when autocreating Blanket PO and the Item Revision # must be entered.
 
- The Item Revision number on the requisition must match the Item Revision number on the PO.
* Navigate: Setup -->Organization -->Financial Options; and in the Alternate Region ENCUMBRANCE, verify if the REQUISITION ENCUMBRANCE checkbox is checked.
* In the Sys Admin Responsibility navigate to: 
Profiles=> query for the Profile Option PO: AUTOCREATE GL DATE.
If using the Encumbrance for Requisitions, then this Profile Option can be set to either AUTOCREATE DATE or REQUISITION GL DATE. If not using Encumbrance, then you may set it to NULL. This will solve the problem. 
The Profile Option PO: AUTOCREATE GL DATE is applicable only if you are using Encumbrance for Requisitions.
 

  
Q15. How do you autocreate a requisition with a document type as blanket release when requisitions were imported from a 3rd party system?

A: Ensure the line types selected for Requisitions are appropriate. 
You need to have Requisition Line types and PO Line types correctly associated.
 
Rerun the process and verify that the system does not error out.
 
Submit the request for requisition import and use the AutoCreate window to create document with type as Blanket Release against the requisition. Navigation:
 
Purchasing -> Reports -> Submit a request for Requisition Import
 
Purchasing -> AutoCreate

  
Q16. How do you autocreate mrp generated requisitions to a blanket purchase order? 

A: First initiate the Release Purchase Requisitions from the Planners Workbench. 
Navigation:
 
Material Planning -> MRP -> Workbench
 
Second, in the Purchasing Responsibility, AutoCreate the requisition to a Blanket PO.
 
Navigation: AutoCreate
 
For Autocreate to find these requisition lines from MRP, the Blanket PO line type must be set to Goods because the MRP Purchase Requisition is always created with a line type of Goods. The reason that MRP uses the line type of Goods is because Goods is seeded data and because the MRP Planner Workbench uses MRPPRELB.pls to insert a record into the PO_REQUISITION_INTERFACE table.
 

  
Q17. Can you autocreate more than one standard PO in one autocreate session? 

A: Yes, 
1) Find the requisition lines to be autocreated.
 
2) Choose a line.
 
3) Autocreate the purchases order using the automatic button.
 
4) Do not leave the requisition lines screen.
 
5) Choose a different line.
 
6) Try to autocreate another standard purchase order by clicking the automatic button.
 
7) The system gives the message: app-14090: no requisition lines were autocreated.
 

  
Q18. Try to autocreate, but the system hangs, how to cancel the requisition that are locked? 

A: Check if there is a lock on the PO related tables. 
Select object_id, session_id, oracle_username, os_user_name,
 
Process, locked_mode
 
From sys.v_$locked_object;
Select a.object_name, b.oracle_username 
From all_objects a, v$locked_object b
 
Where a.object_id = b.object_id
 
And a.object_name like 'po%';
If you have any records returned, you have a lock. To disable the lock, kill the session. Regenerating the form and bouncing the database will unlock all the objects. 

  
Q19. What is the package or procedure that stores the autocreate process?

A: Poxbwp1b.pls - autocreate po package body. 
Description: this package contains all the functions to create purchase orders, releases and rfq's from data stored in the po_headers_interface, po_lines_interface and po_distributions_interface tables. When a user selects a line to be autocreated, it loads the above interface tables. At that point the functions which are part of this package are called and move to create the req line into a release or purchase order.

  
Q20. What does the grouping method 'default' indicate in the autocreate form?

A: With the grouping method 'default' requisition lines for the same item, revision, line type, unit of measure, and transaction reason are combined into individual purchase order lines; and requisition lines for the same item, revision, and line type are combined into individual rfq lines.

  
Q21. I autocreated a PO with two lines. When I go to the purchase order entry screen and query the PO, instead of showing the lines created, it only shows a new line with number 3. Why? 

A: Make sure Inventory organization field is populated in Financial Options.
FAQ Details
Q1. What do I do if I am unable to Approve a Requisition?

A: 1. Check that the Document Manager is up.
2. Check and resolve the Document Manager error.
3. Run wfstat.sql and check its output.
 
4. If the above have been performed, check if you have set up approval assignments correctly.
 
To set up approval assignments navigate to:
 
Purchasing>Setup>Approvals>Approval Assignments
 
On the find job approval assignments form, search and select the appropriate position (e.g. VPM200 Vice President of Materials) which will display the "Assign Approval Groups" window. On this window, make sure you have an approval group selected for each document type you work with.
 

  
Q2. How do I check the Status of Deferred Activities?

A: 1. Run wfbkgchk.sql available at $FND_TOP/sql 
2. For example, log on to the database by doing sqlplus username/password@database
 
3. Then run the sql file, wfbkgchk.sql, by doing @wfbkgchk.sql
 
  
Q3. What do I do if I get the 'PO_ALL_EXIT_ERROR' error?

A: Have you performed the following? 
1. Check if the message file is <lang.msb> is present. If not regenerate messages using adadmin utility.
 
2. Set the Profile Option 'PO: Document Approval Mode' correctly.
Set the profile for one of the following options:
 
- Standard User Exit
 
- Document Approval Manager ( Which occurs twice in the List of values for the Profile option. The correct profile option is the one which occurs the second time)
 
Explanation:
 
As the System Administrator responsibility, the list of values for the system profile option 'PO: Document Approval Mode' should contain 3 entries:
 
1. Document Approval Manager
 
2. Standard User Exit
 
3. Document Approval Manager
 
Note that the option 'Document Approval Manager' appears twice in the list.
 
The first one listed was actually obsoleted in 10.7 . Development will not be providing a script which will remove or inactivate the old profile option. The application does not offer the ability to inactivate or remove profile option values.
 
To resolve the issue, either of the other two values (the second and third as mentioned above) in the list of values can be used for the profile option and users should then be able to approve a purchase order.
 

  
Q4. How do I identify Document Manager failures while Approving a Document? 

A: To identify the document manager error number, please look at the attribute DOC_MGR_ERROR_NUM in the wfstat log provided. 

DOC_MGR_ERROR_NUM VALUE - MEANING:
1 Document Manager Timed Out (It is taking more than 180 sec to complete the activity). Bounce the Database and Restart the PO Approval Document Manager.
 
2 Document Manager is Down. Please restart the PO Approval Document Manager.
3 Exception in the Code. In this case look at SYSADMIN_ERROR_MSG attribute for more details.
 
  
Q5. What do I do when I get a Document Manager Failure Notification? 

A: For customers on Family Pack and above: 
1. A new item type POERROR is created for handling the error process in case of any document manager related issues.
 
2. The following workflow attributes are defined with implementation specific values. (These need to be set in POERROR wf) DOC_MGR_WAIT_RELATIVE_TIME - amount of time processes will have to wait before getting picked again. (default 0) RETRY_COUNT - number of attempts to get document manager for approval (default 0) TIMEOUT_VALUE - amount of time for notification to automatically close itself. (default 0) SYSADMIN_USER_NAME - application user (typically system administrator) who can receive notifications for document manager related errors in status 1 and 2. (MUST BE SET BY CUSTOMER TO A VALID USERNAME)
 
3. The workflow background engine always needs to be running for the POERROR item type.
 
The interval between document manager retries is dependent on the following factors
 
- attribute DOC_MGR_WAIT_RELATIVE_TIME
 
- work flow background engine wait period
 
Irrespective of the approval mode, there has to be separate workflow background process for the POERROR item type which will "poll" those processes to complete their "wait" periods and get picked for processing again. Once the background engine is started, it will try to approve the document again. Users are not sent any notifications for status 1 and 2 errors. Status 3 errors are reported to the user and not to the system administrator.
 

  
Q6. What is the title of the executable file that represents the Document Approval Manager, and where is it located on the server?

A: The executable file that contains the code for 'PO: Document Approval Manager' is POXCON. This file can be found on the database server in the $PO_TOP/bin directory. For a Windows NT environment, the file will be named POXCON.EXE and the FIND FILE tool should be utilized to locate it. 

  
Q7. Is it necessary to have the Document Approval Manager running, and how many target processes should be available?

A: Yes, it necessary for the PO Document Approval Manager to be running in order for the approval process to complete. The number of target processes should be greater than or equal to the number of processors in the database server (actual processes). Number of Target Processes => Number of Processors on Server (actual process) 

  
Q8. How does the Document Approval Manager get restarted?

A: The Document Approval Manager gets restarted on the Administer Concurrent Managers form, using the following steps: 

Responsibility: System Administrator
 
Navigation: Concurrent -> Manager -> Administer
 
- Locate the PO Document Approval Manager.
 
- In the Status column, you should see something saying the manager is not running.
 

To reactivate the PO Document Approval Manager:
 
- Click on the line containing the PO Document Approval Manager
 
- Click the Deactivate button.
 
- Close and reopen the form.
 
- Locate the PO Document Approval Manager and click on the line
 
- Click on the Activate button.
 
The PO Document Approval Manager should now be restarted.
 

NOTE:
 The Internal Manager must be running for this process to work. If it is not running, the DBA or System Administrator must restart the Internal Manager first.

No comments:

Post a Comment

If you are facing any issues while copying the Code/Script or any issues with Posts, Please send a mail to OracleApp88@Yahoo.com or message me at @apps88 or +91 905 957 4321 in telegram.
Best Blogger TipsGet Flower Effect