During implementation, set a value for each Oracle
Purchasing profile option to specify how Purchasing controls access to and
processes data.
Profile options are grouped into one
or more profile option categories enabling you to view only the profile options
that pertain to your application or function.
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.
Approvals Category
PO: Allow Requisition Approval Forward Action
Yes indicates that the Forward and the Approve
and Forward actions are active in a requisition approval notification.
PO: Archive Catalog on Approval
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.
AutoCreate Category
PO: AutoCreate GL Date Option
- 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.
PO: Convert Requisition UOM to Source Doc UOM During Release
Creation
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.
PO: Default PO Promise Date from Need By date
Yes indicates that the promise date is defaulted from the
requisition need-by date when a purchase order or release is automatically
created.
PO: Use Need-by Date for Default Autocreate grouping
Yes indicates that the need-by date on the requisition is
included with the defaults to group requisition lines.
PO: Use Requisition Line Numbers on Autocreated Purchase Order
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.
PO: Use Ship-to for Default Autocreate grouping
Yes indicates that the ship-to organization and location on the
requisition is included with the defaults to group requisition lines.
AutoCreate Security Category
PO: Allow Autocreation of Oracle Sourcing Documents
Yes or No indicates whether the buyer can create Oracle Sourcing
documents from the AutoCreate window. The default is No.
PO: Allow Buyer Override in AutoCreate Find
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.
PO: Allow Category Override in AutoCreate Find
Yes or No indicates whether the category (from the Buyers
window) defaulted into the Find Requisition Lines window can be cleared or
overridden.
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 modify logic applies.
AutoCreate UI Category
The table below lists the profile options that control
the UI (user interface) aspects of AutoCreate.
PO: Auto Apply Default Contract Template
Oracle Procurement Contracts: Yes indicates to use the default
defined for the document type contract template in Contract Terms Library.
PO: Display the Autocreated Document
PO: Display AutoCreated Quotation
PO: Warn if RFQ Required before AutoCreate
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.
Automatic Sourcing Category
PO: Automatic Document Sourcing
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).
Catalog Import Category
PO: Price Tolerance (%) for Catalog Updates
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.
Consigned and VMI Category
PO: Supplier Consigned Enabled
Yes or No indicates whether inventory consignment from supplier
features are enabled in Oracle Purchasing
PO: VMI Enabled
Oracle Vendor Managed Inventory: Yes or No indicates whether
Vendor Managed Inventory (VMI) is enabled in Oracle Purchasing.
Debug Category
The table below lists the profile options that control
debug features usually used by technical support staff.
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: Set Debug Concurrent ON
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.
PO: Set Debug Workflow ON
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.
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.
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.
RCV: Debug Mode
If set to Yes, and RCV: Processing Mode set to Immediate or
Batch, debug messages will be printed to the concurrent log file.
Deployment Category
PO: Approval Timeout Value
PO: Cache Time To Live
Specifies the duration that data is cached in memory. A value of
0 disables caching. Value is in minutes.
PO: Contracts Enabled
Oracle Procurement Contracts: Yes indicates that Oracle
Procurement Contracts is installed, implemented, and active in Oracle
Purchasing.
PO: Custom Measure Precedence
This profile is used by Oracle Purchasing Intelligence. It
determines the survey matching precedence.
PO: Enable Services Procurement
Oracle Services Procurement: Yes indicates that Services
Procurement is installed, implemented, and active in Oracle Purchasing.
PO: MFG Organization ID
PO: View receipt mode
PO: Workflow Processing Mode
- 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.
RCV: Processing Mode
- 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.
Document Builder UI Category
PO: Default Requisition Grouping
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.
PO: Document Builder Default Document Type
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.
Document Security Category
PO: Allow Auto-generate Sourcing Rules
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.
PO: Allow Rate Override for User Rate Type
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.)
PO: Allow Retroactive Pricing of POs
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.
PO: Change Supplier Site
PO: Enable Direct Delivery to Shop Floor
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.
PO: Legal Requisition Type
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.
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.
Encumbrance Category
PO: Override Funds Reservation
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.
PO: Use Document GL date to Unreserve
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).
Enterprise Asset Management Setup Category
The table below lists the Oracle Purchasing profile
options for Enterprise Asset Management (EAM) setup.
iProcurement Setup Category
Notifications Category
PO: Amount Billed Threshold Percentage
Oracle Services Procurement: Indicates the amount above which
the amount billed exceeded threshold notification will be sent to the
requester.
PO: Contractor Assignment Completion Warning Delay
Oracle Services Procurement: Yes indicates that the contractor
assignment completion notification is sent to the requester when the assignment
is complete.
Notifications UI Category
PO: Notification Lines Display Limit
Indicates the number of purchase order or release lines to be
displayed in approval notifications. Oracle recommends a maximum of 30 lines.
PO Communication Category
The table below lists the profile options that controls
communication of purchasing documents with suppliers.
PO: cXML From Domain
PO: cXML From Identity
PO: Fax Output Directory for the PO Document
The operating system directory name where the document publisher
will store the generated purchase order PDF file for faxing.
PO: Generate Amendment Documents
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.
PO: In File Path
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 also be specified in the UTL_FILE parameter in the INIT.ORA file.
PO: Secondary E-mail Address
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.
PO: Terms and Conditions File Name
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 directories specified in the UTL_FILE parameter in the INIT.ORA file
and the file path indicated by the profile PO: In File Path.
PO/Releases/Requisitions UI Category
PO: Check Open Periods
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.
PO: Default Need-By Time
Indicates the time used to default for the entry of need-by date
when a requisition, purchase order, or release is created.
PO: Display VMI Warning
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.
PO: Use P-Cards in Purchasing
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.
Procurement Contracts Setup Category
Allow Referencing CPA Under Amendment
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.
Receiving Category
The table below lists the profile options that controls
Receiving functionality in Oracle Purchasing.
PO: Automatically Deliver Drop Ship ASNs
Yes indicates that you want Oracle Purchasing to automatically
perform a receipt and deliver action for drop ship ASNs.
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 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.
RCV: Fail All ASN Lines if One Line Fails
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.
RCV: Print Receipt Traveler
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.
Requisition Import Category
PO: Release During ReqImport
Yes or No indicates whether Purchasing can automatically create
releases during the Requisition Import process.
Self-Billing Category
PO: ERS Aging Period
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.
PO: ERS Invoice Number Prefix
'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.
Services Procurement Setup Category
PO: UOM Class for Temp Labor Services
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.
Sourcing Setup Category
The table below lists the profile options in Oracle
Purchasing used to control document sourcing features.
Supplier Item Catalog Forms UI Category
The table below lists the profile options that controls
the Oracle Purchasing Supplier Item Catalog Forms UI.
PO: Default Supplier Item Catalog Option
Indicates the default source tabbed region in
the supplier item catalog: Negotiated Sources, Prior Purchases, Sourcing Rules,
or Requisition Templates.
PO: Item Cross Reference Warning
Indicates the Item Cross Reference Type that you want to use as
a disposition warning message for requisitions.
Pricing Transparency Profile Options
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.
No comments:
Post a Comment