During an implementation, you can set a value for each Oracle Purchasing profile option to specify how Purchasing controls access to and processes data.
See: User Profiles and Profile Options in Oracle Application Object Library, Oracle E-Business Suite Setup Guide.
Profile options are grouped into one or more categories, which enables you to view only those profile options applicable to your application or function.
PO: Override Approved Supplier List Status - OBSOLETE
PO: Supplier Pricing Method - OBSOLETE
PO: Use Requisition Line Numbers on Autocreated Purchase Order Lines
This section describes profile options by category.
The tables in this section provide profile option information as follows:
The Default column displays either the default profile option value in italics, or No Default if none exists.
The User Access column indicates whether you can view or update the profile option.
The System Administration: Site, Application, Responsibility, and User columns indicate at which levels the system administrator can update these profile options.
The key for each table is:
Update: You can update the profile option.
View Only: You can view the profile option but cannot change it.
No Access: You cannot view or change the profile option.
The table below lists the profile options that impact document approvals.
| Profile Option | Default | User Access | System Administration: Site | System Administration: Application | System Administration: Responsibility | System Administration: User |
|---|---|---|---|---|---|---|
| PO: Allow PO Approval Forward Action | Yes | View Only | Update | View Only | View Only | View Only |
| PO: Allow Requisition Approval Forward Action | Yes | View Only | Update | View Only | View Only | View Only |
| PO: Archive Catalog on Approval | No | Update | Update | Update | Update | Update |
The profile option PO: Allow PO Approval Forward Action enables users to display or hide the Forward, and Approve and Forward buttons in the approval notification. When the value of the profile option is Yes, these two buttons are displayed. When the value of the profile option is No, these two buttons are not visible in the notification. Thus you see the following buttons: Approve, Reject, Reassign, and Request Information.
Yes indicates that the Forward and the Approve and Forward actions are active in a requisition approval notification.
Yes or No indicates whether Purchasing archives blanket purchase agreements in a price/sales catalog submission upon approval. You need to consider this profile option only if you receive price/sales catalog submissions from your suppliers through the Purchasing Documents Open Interface. This profile option comes into effect only if Archive on Approval is chosen in the Document Types window in Purchasing and you import the documents with a status of Approved; if you then choose No for this profile option, Purchasing does not archive the price/sales catalog agreements.
Note: If a document update is pending review in the Exceeded Price Tolerances window, the revision of that document is not updated until you accept all line updates.
For more information, see the Oracle Manufacturing, Distribution, Sales and Service Open Interfaces Manual.
The table below lists the profile options that control AutoCreate functionality options.
| Profile Option | Default | User Access | System Administration: Site | System Administration: Application | System Administration: Responsibility | System Administration: User |
|---|---|---|---|---|---|---|
| PO: AutoCreate GL Date Option | AutoCreate Date | Update | Update | Update | Update | Update |
| PO: Convert Requisition UOM to Source Document UOM | No Default | Update | Update | Update | Update | Update |
| PO: Default PO Promise Date from Need By Date | No Default | Update | Update | Update | Update | Update |
| PO: Use Need-by Date for Default Autocreate Grouping | No Default | Update | Update | Update | Update | Update |
| PO: Use Requisition Line Numbers on Autocreated Purchase Order Lines | No Default | Update | Update | Update | Update | Update |
| PO: Use Ship-to for Default Autocreate grouping | No Default | Update | Update | Update | Update | Update |
| PO: Warn if RFQ Required before Autocreate | No | Update | Update | Update | Update | Update |
Indicates the date used on purchase orders generated by AutoCreate:
AutoCreate Date: The autocreate date is used as the purchase order date.
Requisition GL Date:The GL date on the requisition distribution is used as the purchase order date.
A Null setting (default value) indicates that the functionality continues as in the past (AutoCreate of releases from a requisition will fail with different UOMs, but the Create Releases concurrent program will convert UOMs and create a release). If set to Yes, users can create requisitions in a different UOM from the UOM on the blanket agreement line and the conversion will be done by Purchasing when the release is created. No means the UOM on the requisition must match the UOM on the blanket purchase agreement for a release to be created by any process.
Yes indicates that the promise date is defaulted from the requisition need-by date when a purchase order or release is automatically created.
Yes indicates that the need-by date on the requisition is included with the defaults to group requisition lines.
Yes indicates that the requisition line numbers are used on autocreated purchase order lines. Note that this only applies when creating a new purchase order.
Yes indicates that the ship-to organization and location on the requisition is included with the defaults to group requisition lines.
The table below lists the profile options that control security for AutoCreate functionality.
| Profile Option | Default | User Access | System Administration: Site | System Administration: Application | System Administration: Responsibility | System Administration: User |
|---|---|---|---|---|---|---|
| PO: Allow Autocreation of Oracle Sourcing Documents | No | View Only | Update | View Only | View Only | View Only |
| PO: Allow Buyer Override in Autocreate Find | Yes | Update | Update | Update | Update | Update |
| PO: Allow Category Override in Autocreate Find | Yes | Update | Update | Update | Update | Update |
| PO: Restrict Requisition line modify to quantity split | No | View Only | Update | Update | Update | View Only |
Yes or No indicates whether the buyer can create Oracle Sourcing documents from the AutoCreate window. The default is No.
Yes or No indicates whether the suggested buyer (from the Enter Person window) defaulted into the Find Requisition Lines window can be cleared or overridden. The default is Yes.
Yes or No indicates whether the category (from the Buyers window) defaulted into the Find Requisition Lines window can be cleared or overridden.
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 modify logic applies.
The table below lists the profile options that control the UI (user interface) aspects of AutoCreate.
| Profile Option | Default | User Access | System Administration: Site | System Administration: Application | System Administration: Responsibility | System Administration: User |
|---|---|---|---|---|---|---|
| PO: Auto Apply Default Contract Template | No Default | Update | Update | Update | Update | Update |
| PO: Display the Autocreated Document | Yes | Update | Update | Update | Update | Update |
| PO: Display the Autocreated Quotation | Yes | Update | Update | Update | Update | Update |
| PO: Warn if RFQ Required before Autocreate | No | Update | Update | Update | Update | Update |
Oracle Procurement Contracts: Yes indicates to use the default defined for the document type contract template in Contract Terms Library.
Yes or No indicates whether Purchasing should automatically display the AutoCreated purchase order.
Yes or No indicates whether Purchasing should automatically display the AutoCreated quotation.
Yes or No indicates whether you are given a warning message and an opportunity to cancel autocreate if one or more of the requisition lines selected for inclusion requires an RFQ and has not been placed on an RFQ.
If you use the PO Create Documents workflow to create purchase orders automatically from approved requisition lines, note that setting this profile option to Yes can affect the workflow. If it is set to Yes and the requisition line is not on an RFQ (but RFQ Required is checked for the requisition line), the workflow stops automatic document creation because it is unable to issue the warning. (The requisition line will still be available in the AutoCreate Documents window.) Even if an RFQ is required for the requisition line, as long as this profile option is set to No, the workflow will continue creating the document.
The table below lists the profile options that control automatic sourcing.
| Profile Option | Default | User Access | System Administration: Site | System Administration: Application | System Administration: Responsibility | System Administration: User |
|---|---|---|---|---|---|---|
| PO: Automatic Document Sourcing | No | View Only | Update | Update | No Access | No Access |
Yes means that Oracle Purchasing automatically defaults source document and pricing information for an item from the most recently created purchase agreement or quotation. No means that this source document information comes from the Approved Supplier List window, where you must specify which source documents to use.
Note: If an item on a requisition is associated with both a blanket purchase agreement and a quotation, Oracle Purchasing may use the blanket purchase agreement even if the quotation was created more recently (depending on your sourcing settings).
See: Setting Up Automatic Sourcing.
The table below lists the profile options that control catalog import functionality.
| Profile Option | Default | User Access | System Administration: Site | System Administration: Application | System Administration: Responsibility | System Administration: User |
|---|---|---|---|---|---|---|
| PO: Archive Catalog on Approval | No | Update | Update | Update | Update | Update |
| PO: Price Tolerance (%) for Catalog Updates | No Default | Update | Update | Update | Update | Update |
A value in this profile option specifies the maximum percentage increase allowed to an item's price when your supplier sends updated price/sales catalog information through the Purchasing Documents Open Interface. This profile option affects only blanket purchase agreements and catalog quotations imported through the Purchasing Documents Open Interface. If the tolerance is exceeded, the buyer receives a notification and can accept or reject the price increase in the Exceeded Price Tolerances window.
This profile option is used only if price tolerances are not already defined at lower levels, in the purchase agreement Terms and Conditions window or the Supplier-Item Attributes window.
See: Receiving Price/Sales Catalog Information Electronically.
The table below lists the profile options that control consigned inventory and VMI functionality.
| Profile Option | Default | User Access | System Administration: Site | System Administration: Application | System Administration: Responsibility | System Administration: User |
|---|---|---|---|---|---|---|
| PO: Display VMI Warning | Yes | No Access | Update | No Access | No Access | No Access |
| PO: Supplier Consigned Enabled | No | No Access | Update | No Access | No Access | No Access |
| PO: Update VMI flag for ASL-enabled manual requisitions | No | Update | Update | Update | Update | Update |
| PO: VMI Enabled | No | No Access | Update | No Access | No Access | No Access |
Yes or No indicates whether inventory consignment from supplier features are enabled in Oracle Purchasing
Oracle Vendor Managed Inventory: Yes or No indicates whether Vendor Managed Inventory (VMI) is enabled in Oracle Purchasing.
Set the profile option to Yes, to view the demand from Vendor and Planner pages in Oracle Collaborative Planning, when you create purchase orders from manually created VMI requisitions. The default value is No. For more information, see Defining the Supplier-Item Attributes.
The table below lists the profile options that control Purchasing create releases functionality.
| Profile Option | Default | User Access | System Administration: Site | System Administration: Application | System Administration: Responsibility | System Administration: User |
|---|---|---|---|---|---|---|
| PO: Convert Requisition UOM to Source Document UOM | No Default | Update | Update | Update | Update | Update |
| PO: Default PO Promise Date from Need By Date | No Default | Update | Update | Update | Update | Update |
| PO: Release During ReqImport | No | Update | Update | Update | Update | Update |
The table below lists the profile options that control debug features usually used by technical support staff.
| Profile Option | Default | User Access | System Administration: Site | System Administration: Application | System Administration: Responsibility | System Administration: User |
|---|---|---|---|---|---|---|
| PO:Enable Sql Trace for Receiving Processor | No | Update | Update | Update | Update | Update |
| PO: Set Debug Concurrent ON | No | Update | Update | Update | Update | Update |
| PO: Set Debug Workflow ON | No | Update | Update | Update | Update | Update |
| PO: Write Server Output to File | No Default | Update | Update | Update | Update | Update |
| RCV: Debug Mode | No | Update | Update | Update | Update | Update |
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. See the Oracle Manufacturing, Distribution, Sales and Service Open Interfaces Manual, Release 11i.
This profile option is used, usually by technical support staff only, for finding problems with Requisition Import.
Caution: For performance reasons, it is very important that this profile option always be set to No, unless you are instructed otherwise by Oracle for debugging purposes.
This profile option is used, usually by technical support staff only, for finding problems with Purchasing workflow processes.
Caution: For performance reasons, it is very important that this profile option always be set to No, unless you are instructed otherwise by Oracle for debugging purposes.
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.
You need to consider a value for this profile option only when debugging a price/sales catalog submission from your supplier through the Purchasing Documents Open Interface.
See the Oracle Manufacturing APIs and Open Interfaces Manual, Release 11i.
If set to Yes, and RCV: Processing Mode set to Immediate or Batch, debug messages will be printed to the concurrent log file.
The table below lists the profile options that control Deployment.
| Profile Option | Default | User Access | System Administration: Site | System Administration: Application | System Administration: Responsibility | System Administration: User |
|---|---|---|---|---|---|---|
| PO: Approval Timeout Value | No Default | No Access | Update | No Access | No Access | No Access |
| PO: Cache Time To Live | No Default | Update | Update | No Access | No Access | No Access |
| PO: Contracts Enabled | No Default | No Access | Update | No Access | No Access | No Access |
| PO: Enable Services Procurement | No | Update | Update | Update | Update | Update |
| PO: MFG Organization ID | No Default | No Access | Update | No Access | No Access | No Access |
| PO: View receipt mode | No Default | No Access | No Access | No Access | No Access | No Access |
| PO:Workflow Processing Mode | Background | Update | Update | Update | Update | Update |
| RCV: Processing Mode | Online | Update | Update | Update | Update | Update |
Indicates Approval Timeout to wait for the Doc Manager to return. Value is in seconds.
Specifies the duration that data is cached in memory. A value of 0 disables caching. Value is in minutes.
Oracle Procurement Contracts: Yes indicates that Oracle Procurement Contracts is installed, implemented, and active in Oracle Purchasing.
Oracle Services Procurement: Yes indicates that Services Procurement is installed, implemented, and active in Oracle Purchasing.
Latin America Localization: Indicates Inventory Organization used for Ledger.
Affects the performance of the Purchasing approval workflow processes:
Online: Completes an entire approval workflow process before letting you proceed to the next activity, but provides you with an updated Status (for purchase orders) as soon as it finishes.
Background: Enables you to proceed to the next activity while the approval process completes in the background.
Whichever option you choose, you can always view the current status of a requisition or purchase order through the Requisitions Summary or Purchase Orders Summary windows.
The default value is Background.
Note: When this profile option is set to Background, you must start the Workflow Background Engine, which you access through the System Administrator responsibility. It is recommended that you set this process to run frequently, if you are using it for Background mode approvals. See: To Schedule Background Engines, Oracle Workflow Guide.
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 Processor runs.
Immediate: The transaction goes to the interface table, and the Receiving Transaction Processor is called for the group of transactions that you entered since you last saved your work.
On-line: The Receiving Transaction Processor is called directly.
The table below lists the Document Builder Security profile options.
| Profile Option | Default | User Access | System Administration: Site | System Administration: Application | System Administration: Responsibility | System Administration: User |
|---|---|---|---|---|---|---|
| PO: Allow Autocreation of Oracle Sourcing Documents | No | View Only | Update | View Only | View Only | View Only |
| PO: Allow Buyer Override in Autocreate Find | Yes | Update | Update | Update | Update | Update |
| PO: Allow Category Override in Autocreate Find | Yes | Update | Update | Update | Update | Update |
The table below lists the Document Builder UI profile options.
| Profile Option | Default | User Access | System Administration: Site | System Administration: Application | System Administration: Responsibility | System Administration: User |
|---|---|---|---|---|---|---|
| PO: Auto Apply Default Contract Template | No Default | Update | Update | Update | Update | Update |
| PO: Default Requisition Grouping | No Default | Update | Update | Update | Update | Update |
| PO: Display the Autocreated Document | Yes | Update | Update | Update | Update | Update |
| PO: Document Builder Default Document Type | No Default | Update | Update | Update | Update | Update |
Indicates the default grouping method used when aggregating requisition demand to create a new document. Values are Default or Requisition.
Default - combine lines from multiple requisitions to create a single line if possible.
Requisition - create a separate line for each requisition line.
This profile option specifies the default target document type that is defaulted into the document builder region within the demand workbench. Values are: Add to PO, New Auction, New PO, New RFQ.
The table below lists the profile options that control Purchasing Document Security.
| Profile Option | Default | User Access | System Administration: Site | System Administration: Application | System Administration: Responsibility | System Administration: User |
|---|---|---|---|---|---|---|
| PO: Allow Auto-generate Sourcing Rules | No | View Only | Update | View Only | View Only | View Only |
| PO: Allow Rate Override For User Rate Type | No | View Only | Update | Update | Update | Update |
| PO: Allow Retroactive Pricing of POs | No Default | View Only | Update | Update | Update | View Only |
| PO: Change Supplier Site | No Default | View Only | Update | Update | Update | View Only |
| PO: Enable Direct Delivery To Shop Floor | No | Update | Update | Update | Update | Update |
| PO: Legal Requisition Type | Both | View Only | Update | Update | Update | View Only |
| RCV: Allow routing override | No | Update | Update | Update | Update | Update |
Create Only indicates whether the buyer can create new sourcing rules, sourcing assignments, and approved supplier list entries while approving a blanket purchase agreement. Create and Update enables the buyer to update sourcing rules and assignments as well as create new sourcing rules. The default is None.
Yes or No indicates whether the Rate in the Currency tabbed region of the Receipts window can be changed. Even if the Rate Type is User, you cannot change the Rate if this profile option is set to No. This profile option affects the Rate on the receipt only, not in the Currency window of a purchase order, RFQ, or quotation. (In the Currency window, you can modify the Rate if the Rate Type is User.)
Used to determine if blanket releases and standard purchase orders can be mass updated with retroactive price change(s) entered on their corresponding blanket agreement.
Never: If this profile is not set or is set to Never, the Apply Retroactive Price Update to Existing PO/Releases checkbox will be disabled in the Blanket Agreement Approval window and the Mass Update Price on Open Releases concurrent program will not update any blanket releases or global agreement sourced standard purchase orders.
Open Releases Only:The Mass Update Price on Open Releases concurrent program will only process releases which have no receipts (if accruing at time of receipt) or invoices matched to them.
All Releases:Perform retroactive pricing on all releases (including those which have accrued receipts or invoices), if the archive mode for that operating unit is set to Approve.
Yes or No indicates whether users can change the supplier site on approved purchase orders.
If Enterprise Asset Management has been implemented and this profile is set to Yes, Outside Services items can be delivered directly to the shop floor. See the Oracle Enterprise Asset Management User's Guide.
Indicates whether users can enter internal requisitions sourced from stock by means of an internal sales order, purchase requisitions sourced from a purchase order, or both types. Available values are Both, Internal, and Purchase.
Yes or No indicates whether the destination type assigned during requisition or purchase order entry can be overridden at receipt time.
The table below lists the Encumbrance profile options for Oracle Purchasing.
| Profile Option | Default | User Access | System Administration: Site | System Administration: Application | System Administration: Responsibility | System Administration: User |
|---|---|---|---|---|---|---|
| PO: AutoCreate GL Date Option | AutoCreate Date | Update | Update | Update | Update | Update |
| PO:Override Funds Reservation | No Default | Update | Update | Update | Update | Update |
| PO:Use Document GL Date to Unreserve | No | View Only | Update | Update | Update | No Access |
| PO:Validate GL Period | Yes | Update | Update | Update | Update | Update |
Indicates whether the GL Funds Override capability should be utilized. If set to Yes and the Oracle General Ledger (GL) setup allows it, absolute funds checking will succeed even if funds are exceeded, up to the amount limit defined for a given account.
This profile determines the default value for funds reservation in the Approval window and the behavior for funds reservation in Oracle Purchasing workflows.
Yes or No indicates whether the GL date of the document is used for encumbrance reversal actions that do not support entry of a GL date (Reject/Return) and as a default for actions that do allow entry of a date (Cancel/Final Close/Unreserve).
Controls the validation of the GL Date in purchase order distributions and requisition distributions.
Select any one of the following values:
Yes: The application verifies the GL date and displays an error message if the date is invalid, for example, the date is in a closed GL period or in a period that is not yet open. Buyers must modify the date to reflect a valid date. Yes is the default value.
No: The application does not validate the GL date.
Redefault: The application verifies the GL date. If the date is found invalid, for example, the date is in a closed GL period, or in a period that is not yet open, then the application automatically corrects the GL date to reflect the current system date. A message displays on the page, informing you that the GL date has been adjusted automatically. However, you can still opt to change the GL date to any other valid date, if required.
The table below lists the Oracle Purchasing profile options for Enterprise Asset Management (EAM) setup.
| Profile Option | Default | User Access | System Administration: Site | System Administration: Application | System Administration: Responsibility | System Administration: User |
|---|---|---|---|---|---|---|
| PO: Enable Direct Delivery To Shop Floor | No | Update | Update | Update | Update | Update |
The table below lists the iProcurement Setup profile options in Oracle Purchasing.
| Profile Option | Default | User Access | System Administration: Site | System Administration: Application | System Administration: Responsibility | System Administration: User |
|---|---|---|---|---|---|---|
| PO: Use P-Cards in Purchasing | No | View Only | Update | Update | Update | Update |
The table below lists the profile options that control Oracle Purchasing Notifications.
| Profile Option | Default | User Access | System Administration: Site | System Administration: Application | System Administration: Responsibility | System Administration: User |
|---|---|---|---|---|---|---|
| PO: Amount Billed Threshold Percentage | No Default | View Only | Update | View Only | View Only | View Only |
| PO: Contractor Assignment Completion Warning Delay | No Default | View Only | Update | View Only | View Only | View Only |
| PO: Notify Requester on Order Approval | No | Yes | Yes | Yes | Yes | Yes |
| PO: Notify Requester on Order Creation | No | Yes | Yes | Yes | Yes | Yes |
| PO: Notify Buyers when Purchase Requisition is Assigned | No | Yes | Yes | Yes | Yes | Yes |
Oracle Services Procurement: Indicates the amount above which the amount billed exceeded threshold notification will be sent to the requester.
Oracle Services Procurement: Yes indicates that the contractor assignment completion notification is sent to the requester when the assignment is complete.
If this profile option is set to Yes, the requester is notified when the order created referring to the requester's requisition is approved.
If this profile option is set to Yes, requesters are notified when their requisitions are converted into purchase order documents.
If this profile option is set to Yes, a notification is sent to the buyers when the purchase requisitions are assigned to them
The table below lists the profile options that control the Notifications UI.
| Profile Option | Default | User Access | System Administration: Site | System Administration: Application | System Administration: Responsibility | System Administration: User |
|---|---|---|---|---|---|---|
| PO: Notification Lines Display Limit | No Default | Update | Update | Update | Update | Update |
Indicates the number of purchase order or release lines to be displayed in approval notifications. Oracle recommends a maximum of 30 lines.
The table below lists the profile options that controls communication of purchasing documents with suppliers.
| Profile Option | Default | User Access | System Administration: Site | System Administration: Application | System Administration: Responsibility | System Administration: User |
|---|---|---|---|---|---|---|
| PO: Communication Email Default | No Default | Update | Update | Update | Update | Update |
| PO: cXML From Domain | No Default | View Only | Update | View Only | View Only | View Only |
| PO: cXML From Identity | No Default | View Only | Update | View Only | View Only | View Only |
| PO: Default Communication method from Order document | No Default | Update | Update | Update | Update | Update |
| PO:Fax Output Directory for the PO Document | No Default | Update | Update | Update | Update | Update |
| PO: Generate Amendment Documents | No | Update | Update | Update | Update | Update |
| PO: In File Path | No Default | View Only | Update | No Access | Update | Update |
| PO: Secondary Email address | No Default | Update | Update | No Access | No Access | Update |
| PO: Terms and Conditions filename | No Default | View Only | Update | No Access | Update | No Access |
If this profile option value is set to Contact, the email address will be defaulted from the supplier contact; and if set to Site, the email address will be defaulted from the supplier site.
Indicates buyer's identity on the cXML From Domain.
If this profile option value is set to Yes, the communication method will be defaulted from the latest approved purchase order document. If the value is set to No, the communication method will be defaulted from supplier site or from the supplier contact.
The operating system directory name where the document publisher will store the generated purchase order PDF file for faxing.
Oracle Procurement Contracts: Yes displays the amendments made to the contract terms and conditions in a separate section in the purchase order PDF. The purchase order PDF cover page then displays summary of changes entered by the user at the time of submitting the purchase order for approval.
For e-mailed purchase orders this indicates the absolute path of the directory where the optional terms and conditions file is stored. This directory must be a database directory defined for PL/SQL file I/O. See My Oracle Support Knowledge Document 2525754.1, Using UTL_FILE_DIR or Database Directories for PL/SQL File I/O in Oracle E-Business Suite Releases 12.1 and 12.2.
When using e-mail purchase orders (PO), enter an e-mail address to send a copy of the e-mail PO to someone in your company. If it is necessary to resend the e-mail, you could log into this secondary e-mail account and resend it from there.
For e-mailed purchase orders this profile identifies the name of the optional terms and conditions file. This text file needs to be placed in one of the database directories defined for PL/SQL file I/O and the file path indicated by the profile PO: In File Path. See My Oracle Support Knowledge Document 2525754.1, Using UTL_FILE_DIR or Database Directories for PL/SQL File I/O in Oracle E-Business Suite Releases 12.1 and 12.2.
The table below lists the profile options that control the PO/Releases/Requisitions UI.
| Profile Option | Default | User Access | System Administration: Site | System Administration: Application | System Administration: Responsibility | System Administration: User |
|---|---|---|---|---|---|---|
| FND: Enable List Search | No Default | No Access | Update | - | Update | - |
| PO: Auto Apply Default Contract Template | No Default | Update | Update | Update | Update | Update |
| PO: Check open periods | No Default | Update | Update | Update | Update | Update |
| PO: Default Need-By Time | No Default | Update | Update | Update | Update | Update |
| PO: Display VMI Warning | Yes | No Access | Update | No Access | No Access | No Access |
| PO: Use P-Cards in Purchasing | No | View Only | Update | Update | Update | Update |
| PO: Default Line Type for Orders and Requisitions | No Default | Update | Update | Update | Update | Update |
| PO: Allow Organization and Location Update on Schedules | No | Update | Update | Update | Update | Update |
This profile option enables users to view list search in the application pages. If you set the value of this profile option to True, list search is visible. If the value of this profile option is False, list search is not displayed in the application pages. List Search is a search tool that helps users quickly and easily retrieve information. Oracle Application Framework implements List Search on top of an existing Query Bean component. For more information on List Search, see: Oracle E-Business Suite Setup Guide.
Yes indicates that the need by date and the promise by date must be in an open Purchasing period when entering purchase orders. Any other setting provides no validation against Purchasing periods.
Indicates the time used to default for the entry of need-by date when a requisition, purchase order, or release is created.
Yes or No indicates whether a warning will be displayed when Vendor Managed Inventory (VMI) item is being placed on a Purchasing document. Default is Yes, the warning will be displayed.
Set this profile option to Yes if you use procurement card-also known as P-Card or corporate credit card-numbers on requisitions in Oracle iProcurement. Set this profile option to Yes to display the procurement card number in the Purchase Orders, Releases, and Purchase Order Headers summary windows.
Set this profile option to No if you do not have Oracle iProcurement installed or do not want to display the procurement card field to buyers. Purchasing windows can physically display the procurement card field even if Oracle iProcurement is not installed and procurement cards aren't used. Therefore, set this profile option to No if you are not using procurement cards.
Determines the defaulting line type behavior for purchase orders and requisitions in Forms. This profile option is not applicable to Buyer Work Center purchasing documents.
There is no any default value for this profile.
If a line type is set as a value for this profile option, then the line type defined at the profile level takes precedence over the line type defined in the Purchasing Options window.
If no value is set for this profile option, then the Line Type defined in the Purchasing Options window is used.
If no default value is set at both the profile level and Purchasing Options window, then there is no line type defaulting in purchase orders or requisitions in forms.
This profile option determines whether a buyer can update the ship to organization, and allows requisition reference when the schedules are split on an approved or draft purchase order. The default is No.
The table below lists the Procurement Contracts Setup profile options in Oracle Purchasing.
| Profile Option | Default | User Access | System Administration: Site | System Administration: Application | System Administration: Responsibility | System Administration: User |
|---|---|---|---|---|---|---|
| PO: Allow Referencing CPA Under Amendment | No | Update | User | |||
| PO: Auto Apply Default Contract Template | No Default | Update | Update | Update | Update | Update |
| PO: Contracts Enabled | No Default | No Access | Update | No Access | No Access | No Access |
| PO: Generate Amendment Documents | No | Update | Update | Update | Update | Update |
If this profile option is set to Yes, then GCPA reference on Requisitions or Standard Purchase Orders (both in Oracle iProcurement and Oracle Purchasing) is allowed during GCPA amendment, provided the GCPA has been approved once referencing the CPAs in Amendment state.
The table below lists the profile options that controls Receiving functionality in Oracle Purchasing.
| Profile Option | Default | User Access | System Administration: Site | System Administration: Application | System Administration: Responsibility | System Administration: User |
|---|---|---|---|---|---|---|
| PO: Automatically Deliver Drop Ship ASNs | No Default | Update | Update | Update | Update | Update |
| RCV: Default Include Closed PO Option | No | Update | Update | Update | Update | Update |
| RCV: Fail All ASN Lines if One Line Fails | No | View Only | Update | Update | Update | No Access |
| RCV: Print Receipt Traveler | No | Update | Update | Update | Update | Update |
| RCV: Return Order Type for Internal RMA | No Default | No Access | No Access | No Access | No Access | No Access |
| RCV: Support Intransit Return for Internal Requisitions | No Default | No Access | No Access | No Access | No Access | No Access |
| RCV: Track Shipments for Return To Vendors | No | Update | Update | No Acces | Update | No Access |
Yes indicates that you want Oracle Purchasing to automatically perform a receipt and deliver action for drop ship ASNs. See: Advance Shipment Notices (ASNs).
If it is set to Yes, a search in the Enter Receipts window and the Receiving Transactions window automatically select 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.
If you choose Yes, you can reject an entire Advance Shipment Notice (ASN) if any ASN line fails validation or processing. If you choose No, then you can accept an ASN if at least one ASN line is successful.
Yes or No indicates whether Purchasing automatically prints the receipt traveler when you perform a receipt or a receiving transaction, and when you match unordered receipts. You can always print receipt travelers from the Submit Requests window.
This profile option identifies the transaction type that Oracle Order Management uses to create an internal RMA for a return order. You can set this profile only at the Organization level using the System Profiles Values window. Set the profile for an organization to receive material through return ASN.
Create this profile option and set the profile value to Yes to enable in transit support for IR returns.
This profile option enables customers to enable the return to vendor feature. Select from the following values:
No: This is the default value. When No is selected, then the advanced return feature cannot be used.
Yes: Enables advanced return features associated with returns to suppliers.
Important: If you select Yes, then this profile option cannot be updated if any return transactions have been created.
The table below lists the profile options that control Requisition Import.
| Profile Option | Default | User Access | System Administration: Site | System Administration: Application | System Administration: Responsibility | System Administration: User |
|---|---|---|---|---|---|---|
| PO: Archive Catalog on Approval | No | Update | Update | Update | Update | Update |
| PO: Release During ReqImport | No | Update | Update | Update | Update | Update |
Yes or No indicates whether Purchasing can automatically create releases during the Requisition Import process.
The table below lists the Self-Billing profile options.
| Profile Option | Default | User Access | System Administration: Site | System Administration: Application | System Administration: Responsibility | System Administration: User |
|---|---|---|---|---|---|---|
| PO: ERS Aging Period | 0 | View Only | Update | Update | Update | No Access |
| PO: ERS Invoice Number Prefix | ERS- | View Only | Update | Update | Update | No Access |
The value in this profile option indicates the number of days between the receipt date and the Payment on Receipt automatic invoice creation date. For example, a value of 2 means that Payment on Receipt creates invoices only for receipts that are 2 or more days old. Any corrections or returns you make against a receipt during that 2-day period are included on the Payment on Receipt invoice.
'ERS-' is the prefix that appears before all invoices that you create automatically using Payment on Receipt. This profile option allows you to change this prefix. For example, shortening this prefix allows extra spaces for longer packing slip or receipt numbers.
The table below lists the Services Procurement Setup profile options in Oracle Purchasing.
| Profile Option | Default | User Access | System Administration: Site | System Administration: Application | System Administration: Responsibility | System Administration: User |
|---|---|---|---|---|---|---|
| PO: Amount Billed Threshold Percentage | No Default | View Only | Update | View Only | View Only | View Only |
| PO: Contractor Assignment Completion Warning Delay | No Default | View Only | Update | View Only | View Only | View Only |
| PO: Enable Services Procurement | No | Update | Update | Update | Update | Update |
| PO: UOM Class for Temp Labor Services | No Default | Update | Update | Update | Update | Update |
Oracle Services Procurement: For a rate based temp labor line type, entry of unit of measure (UOM) is restricted to those in this UOM class.
The table below lists the profile options in Oracle Purchasing used to control document sourcing features.
| Profile Option | Default | User Access | System Administration: Site | System Administration: Application | System Administration: Responsibility | System Administration: User |
|---|---|---|---|---|---|---|
| PO: Allow Autocreation of Oracle Sourcing Documents | No | View Only | Update | View Only | View Only | No Access |
| PO: Display the Autocreated Document | Yes | Update | Update | Update | Update | Update |
The following table lists the Supplier profile options in Oracle Purchasing :
| Profile Option | Default | User Access | System Administration: Site | System Administration: Application | System Administration: Responsibility | System Administration: User |
|---|---|---|---|---|---|---|
| PO: Allow Supplier Merge for Multiple Operating Units | No Default | No Access | Update | No Access | No Access | No Access |
This profile option enables suppliers to merge supplier sites from an open global agreement that refers to multiple operating units. Set this profile option to Yes to merge the supplier sites. Run the concurrent program Supplier Merge Program, to obtain a list of all the operating units that are referred to in the global agreement. After the supplier sites for all the operating units are merged, reset this profile option to No.
Note: Only the system administrator can setup this profile option.
The table below lists the profile options that controls the Oracle Purchasing Supplier Item Catalog Forms UI.
| Profile Option | Default | User Access | System Administration: Site | System Administration: Application | System Administration: Responsibility | System Administration: User |
|---|---|---|---|---|---|---|
| PO: Default Supplier Item Catalog Option | Negotiated Sources | Update | Update | Update | Update | Update |
| PO: Item Cross Reference Warning | Disposition | View Only | Update | Update | Update | No Access |
Indicates the default source tabbed region in the supplier item catalog: Negotiated Sources, Prior Purchases, Sourcing Rules, or Requisition Templates.
Indicates the Item Cross Reference Type that you want to use as a disposition warning message for requisitions.
The following are profile options are required for Pricing Transparency:
Application level:
QP: Licensed for Product --Purchasing
QP: Pricing Perspective Request Type-- Purchase Order
QP: QP: Pricing Transaction Entity --Procurement
QP: Source System Code -- Oracle Purchasing
PO: Price Enhancement --Yes
Note: You need to enable Pricing Enhanced checkbox for the Document style using the PO: Price Enhancement profile option.
System / Responsibility Level:
QP: Item validation Organization
System Level:
QP: Security Control
Note: Refer to the Oracle Advanced Pricing User's Guide for more information on the aforementioned profile options.
The table below lists the profile options in Oracle Purchasing used to control the setup for Supplier Scheduling.
| Profile Option | Default | User Access | System Administration: Site | System Administration: Application | System Administration: Responsibility | System Administration: User |
|---|---|---|---|---|---|---|
| MRP: Default Sourcing Assignment Set | - | - | Yes | No Access | No Access | Yes |
| MRP: Sourcing Rule Category Set | - | - | Yes | No Access | No Access | No Access |
| MSC: Source Setup Required | - | - | - | - | - | - |
| PO: Use Enhanced Sourcing Rules | Obsolete | Obsolete | Obsolete | Obsolete | Obsolete | Obsolete |
| PO: Allow Auto-generate Sourcing Rules | No Access | No Access | Yes | No Access | No Access | No Access |
This profile option indicates which sourcing rules assignment set will be used in Purchasing and Supplier Scheduling. Planning allows the user to use multiple Assignment Sets, however, Purchasing looks at only a single Assignment Set. The value of this profile option should be the name of the Assignment Set used in Purchasing. This profile option must be set if the user is using sourcing rules in Purchasing.
This profile needs to be set to display Category and Category–Organization assignments in the Sourcing Rule/Bill of Distribution Assignments window.
Internal profile used by the software during collections configuration. Do not manually update.
This profile option is obsolete.
Create Only indicates whether the buyer can create new sourcing rules, sourcing assignments, and approved supplier list entries while approving a blanket purchase agreement. Create and Update enables the buyer to update sourcing rules and assignments as well as create new sourcing rules. The default is None.