Protected by Copyscape Web Copyright Protection Software

Search This Blog

Tuesday, May 28, 2013

Profile Options in Oracle Apps Purchasing:

Some of Important Profile Options in Oracle Purchasing:
PO: AutoCreate GL Date Option
Indicates the date used on purchase orders generated by AutoCreate: The autocreate date is used as the purchase order date. The GL date on the requisition distribution is used as the
Purchase order date.
PO: Display the Autocreated Document
Yes or No indicates whether Purchasing opens the appropriate transaction window (Purchase
Orders window, RFQs window, or Sourcing negotiation page) and displays the created line(s) when you autocreate a document.
PO: Enable Sql Trace for Receiving Processor
Yes means that when you run the Receiving Transaction Processor to import data from another system using the Receiving Open Interface, the View Log screen displays the receiving transaction pre–processor’s actions, including errors, as it processed the receipt data from start to finish. (The profile option RCV: Processing Mode must also be set to Immediate or Batch for the Yes option to work.) Yes also generates a database trace file; if you need help with an error that occurs while the Receiving Transaction Processor runs, Oracle Support Services may ask you for this trace file.
This profile option should be set to Yes only while debugging the Receiving Open Interface or for generating a trace file.The Receiving Open Interface validates receipt transactions from other systems and uses the Receiving Transaction Processor to import the validated data into Purchasing.
PO: Release During ReqImport
Yes or No indicates whether Purchasing can automatically create releases during the
Requisition Import process.
PO: Restrict Requisition line modify to quantity split
Yes or No indicates whether Purchasing restricts requisition line modify in AutoCreate to only splitting the quantity of a line. No means that the standard AutoCreate requisition line modifies logic applies.
PO: Write Server Output to File
Yes or No indicates whether log details are written to a flat file rather than to the standard concurrent manager details log viewable through the View Log button in the Submit Request window when running the Purchasing Documents Open Interface program. Yes means log details are written to a flat file. No means log details are written to the concurrent manager log screen, which can cause overflow problems for large catalogs. Leaving this profile option blank means log details are not written at all, which improves performance.
RCV: Processing Mode
Indicates the processing mode used after you save your work for receiving transactions:
Batch
The transaction goes to the interface table, where it will be picked up the next time the Receiving Transaction Immediate
The Receiving Transaction Processor is called directly.
RCV: Allow routing override
Yes or No indicates whether the destination type assigned during requisition or purchase order entry can be overridden at receipt time.
RCV: Debug Mode
If set to Yes, and RCV: Processing Mode set to Immediate or Batch, debug messages will be printed to printed to the concurrent log file.
RCV: Default Include Closed PO Option
If it is set to yes, a search in the Enter Receipts window and the Receiving Transactions
Window automatically selects the Include Closed POs checkbox. Your search results will then include closed orders. The Receiving Open Interface (including ASN) will allow a receipt against orders with the status of Closed for Receiving if this profile is set to Yes. Any setting other than Yes prevents receiving against orders using the Receiving Open Interface with the status of Closed for Receiving.