Do not rely on openFDA to make decisions regarding medical care. Always speak to your health provider about the risks and benefits of FDA-regulated products.
We may limit or otherwise restrict your access to the API in line with our openFDAOpenFDA provides APIs and full sets of downloadable files to a number of high-value, high priority and scalable structured datasets, including adverse events, drug product labeling, and recall enforcement reports.Where to StartThe best place to start is on the
page. It provides a great introduction to openFDA and some good pointers on how you can begin developing using the platform.The OpenFDA Developer CommunityOpenFDA features an open user community for sharing open source code, examples, and ideas. Share your feedback, questions, and ideas with the community on ,, and. Take a look at some of the built by members of the community.Access denied | www.webmd.com used Cloudflare to restrict access
Please enable cookies.
What happened?
The owner of this website (www.webmd.com) has banned your access based on your browser's signature (3fc5eea-ua98).Oracle iProcurement Implementation and Administration Guide
Browser version scriptRequisitions Setup
Requisitions Setup Checklist
Use the following checklist for all setup related to requisition creation and management. The steps are organized by functional area. For example, all steps that concern setting up delivery information on requisitions appear together. This is a checklist of all setup steps in this chapter. These steps appear in a suggested, but not required, order.
Requisitions Setup Checklist
Functional Area
Required or Optional
Information Source
Foreign Currency Support
Information Templates
Suggested Buyer
One-Time Address
Purchase Order Grouping for Requisition Lines with One-Time Addresses
Hazard Information
Global Requester
Charge Account Displays
Expense Charge Account Rules
Employee P-Cards
Supplier P-Cards
PO Extract for P-Card Reconciliation
Project Accounting
Grants Accounting
Favorite Charge Accounts
Required if you have not implemented Oracle Purchasing
Global Approver
Requisition Changes
Requisitions
Requester-Initiated Changes to Purchase Orders
Requisitions
Requisition Cancellations
Requisitions
Life Cycle Tracking
Requisitions
Internal Requisitions
Requisitions
Oracle Services Procurement
Requisitions
Foreign Currency Support
Each time a requester searches for an item in a catalog, the search can display the currency associated with that item. This currency can be any valid currency defined in the application, including the functional currency. Similarly, users can make a non-catalog request in any valid currency. When these items are added to the shopping cart, the application converts the price for that item into the functional currency using the relevant exchange rate, and then displays the functional currency throughout the application.
The foreign currency feature displays the foreign currency price along with the functional currency price on key windows in the application.
The foreign currency can appear on the following pages:
Shopping Cart
Approver Shopping Cart
Edit Single Account
Edit Multiple Accounts
Review Charge Accounts
Edit Lines - Delivery information
Edit Lines - Billing information
Review and Submit - expand line details
Printer-friendly
Approval Notification
Approval Notification Reminders
Requisitions: click requisition - click Details icon - expand line details
Setup Steps
Decide whether to display the transaction currency price to requesters during checkout. Use Oracle Applications Framework personalization to display or hide the field.
The following table shows the default settings of transaction and functional prices and amounts in the shopping cart:
Price and Amount Fields by Default
Field Name
Personalization Name
Displayed or Hidden by Default?
Transaction Currency Price
Displayed by default
Functional Currency Price
Hidden by default
Transaction Amount
TxnAmountFlow
This field cannot be personalized
Functional Amount
FuncAmount and TxnAsFuncAmount
This field cannot be personalized
If you do not want to accept the defaults for Transaction Currency Price and Functional Currency Price, then use Oracle Applications Framework personalization to change them. For more information, see .
To apply your changes to the Review and Submit page of the checkout process, apply your personalizations to that page.
Note: The Transaction Amount is hidden if the transaction currency is the same as the functional currency for all lines in the cart. It is visible if there is at least one foreign currency line. The Functional Amount always appears. Personalization does not control these fields.
Information Templates
You can set up information templates to gather additional information in Oracle iProcurement to pass necessary order processing information to suppliers. When an information template is assigned to a category or item, the application prompts requesters to provide the information specified in the template when the item is added to the shopping cart. This information becomes a line-level attachment to the requisition.
For example, you can implement information templates for items such as business cards that require additional information (name, address, e-mail address, phone) from the requester. Oracle iProcurement prompts for name, address, e-mail address, and phone number when you order business cards. Each information template must be associated with an Oracle Purchasing item or item category. If an information template is associated with an item category, all items belonging to that category are also associated with the template.
Setup Steps
Create an information template
Navigate to the Define Information Template window in Oracle Purchasing.
Give your Template a name.
This name appears as a heading during checkout.
Select Available in All Organizations to make the template available to requesters in all operating units. Deselect this option to make the template available only to requesters in the same operating unit in which you are creating the information template.
For example, you are logged in with a responsibility that is tied to the Vision France operating unit. If you leave this option deselected, then your information template is available only to users in your French operating unit.
Select an Attachment Category of To Supplier or To Buyer.
To Buyer means that the requisition, when turned into a purchase order, displays the information template as an attachment to the buyer. To Supplier means that the information template also is available as an attachment to the supplier.
Enter an Attribute Name and Description. The Attribute Description is the actual field prompt that appears in Oracle iProcurement.
Define Information Template Window
If you use Multilingual Support (MLS), you can enter translations for the following fields: Template, Attribute Name, Attribute Description, and Default Value. To enter the translations, select Translations from the View menu. For more information, see the Oracle E-Business Suite User's Guide.
Optionally, enter a default value to automatically appear in the field.
For example, for an Attribute Name of Body Color, the default value could be Black.
To make the template field to be a list of values from which the requester selects, see the steps for creating lists.
Indicate whether the field is mandatory for Oracle iProcurement requesters. If the field is mandatory, requesters must enter a value in the field before proceeding to complete the requisition.
Indicate whether to activate the attribute to actually appear in Oracle iProcurement. In certain circumstances, you can define an attribute, but delay enabling it for display.
Choose Associate Template to associate the template with an item or item category.
Information Template Association Window
In the Information Template Association window select the type of association (Item Number or Item Category) to associate with the template.
If you selected Item Number, enter the number. If you selected Item Category, enter the category.
Save your work.
Create pop-lists
Complete these steps to make your template fields a menu of valid values. For example, you create a Country of Origin field. Instead of letting the requester enter any value, you provide a menu that contains only the values Canada, US, and Mexico.
For more information about the following steps, see the Oracle E-Business Suite Flexfields Guide.
Log in to Oracle Purchasing.
Use the following navigation: Setup & Flexfields & Validation & Sets.
Create a flexfields validation set that satisfies the following criteria:
Format Type is Char, and Maximum Size is less than or equal to 240.
Validation Type is either Independent or Translatable Independent.
List Type is any of the provided options.
Use the following navigation: Setup & Flexfields & Validation & Values.
Search for the validation set name that you created and add values to it.
For example, your validation set is Country of Origin, and the values are Canada, US, or Mexico.
Access the Information Templates window the preceding instructions for defining information templates describe
In the LOV field, select your validation set name.
Save your work.
Implementation Considerations
If information templates are created for both the item and a category that it belongs to, then both templates apply to that item.
The information template is also accessible through a Special Information link in the cart, if the requester wishes to update the fields after initially adding the items to the cart.
The preceding figure shows how information templates are associated with multiple lines in a cart, through the Special Information column. (The Special Information column appears by default.)
Suggested Buyer
As requisitions are created in Oracle iProcurement, it is possible to indicate the suggested buyer for each requisition and requisition line. You can define a buyer for any of the following:
Blanket purchase agreement or quotation
Requisition template
If a buyer is found on any of the preceding items, then it becomes the default buyer in the corresponding purchase requisition based on its position in the document hierarchy. The Oracle iProcurement requester can accept this default or override it based on the list of buyers in the Suggested Buyer field on the requisition. This suggested buyer information is then passed to the resulting purchasing document and may be overridden during the document creation process.
Profile Options
The profile option HR: Cross Business Groups lets buyers be the default buyers from other business groups. See .
The Get Buyer process of the PO Create Documents workflow retrieves buyer information for the purchase order when it is being created. For standard purchase orders, this process retrieves the buyer from the requisition line (through the Get Buyer From Req Line function). If no buyer is defined at the requisition level, then the item master, category, source document, and contract are subsequently examined. When a blanket release is created, the process retrieves the buyer from the blanket agreement, regardless of the buyer defined on the associated requisition.
Implementation Considerations
When the profile HR: Cross Business Groups is set to Yes:
When using the Category to determine the default buyer, Oracle iProcurement spans business group boundaries when selecting the default buyer.
The list of values for the Suggested Buyer field crosses business groups, enabling the user to select an employee from another business group as the suggested buyer.
One-Time Address
Requesters can specify alternate delivery locations, such as a home address, that are not an office location or other location from the database. This is a one-time address. This feature lets requesters specify the one-time address on a requisition line during the checkout process. The requester can associate the one-time address with specific requisition lines or with all requisition lines on a given requisition. One-time locations appear as line-level attachments on the resulting purchase order.
Setup Steps
To set up a default one-time address:
Set up a dummy HR location to use as the deliver-to location on the requisition line whenever the requester specifies a one-time location. When defining this location, it might or might not be associated with an organization. If it is associated with an organization, then you must define a distinct location for every organization. You can set up this location on the Location window, which you can access from the Setup & Organizations & Locations...Purchasing menu.
Set the value of the POR: One Time Location profile option to be equal to the name of the location that you created in the preceding step. You can set this profile value at the site, responsibility, or user level.
By default, enter the address details. Use Oracle Applications Framework personalization to configure the address so that individual address lines are available. For more information, see .
Profile Options
POR: One Time Location must be set to a location that has been previously defined in the Location window.
Function Security
You can restrict access to this functionality using menu function security. Under Menu Exclusions, exclude the function One Time Location. For information about function security setup, see .
Implementation Considerations
No additional considerations.
Purchase Order Grouping for Requisition Lines with One-Time Addresses
As requisitions are created in Oracle iProcurement, it is possible to assign one-time addresses as the deliver-to locations for each line. Requesters specify one-time locations (delivery addresses) when they want to have heir ordered items delivered to a location that has not been previously defined (and most likely not used again). Delivery of items on individual requisition lines can be to distinct one-time locations. Each one-time location appears on the resulting purchase order line as an attachment.
In the case where the same item is found on two or more requisition lines, each with a separate one-time delivery address, the buyer or requester may not want these two (or more) requisition lines to be grouped onto the same purchase order line since there could be some confusion as to the quantity to be delivered to each location. The following figure details the requisition-to-purchase order process when one-time locations are employed:
As requisition lines are converted into purchase order lines, multiple requisition lines are grouped onto one purchase order line if certain characteristics, such as item and unit of measure, are the same. If one-time locations are associated with the requisition lines, each one-time location is represented on the resulting purchase order line as an attachment. Details of the main functional elements of the one-time location grouping functionality follow.
Grouping Options
Attributes in the PO Create Documents Workflow control the grouping feature and provide the requester the ability to not group requisition lines that contain one-time locations. The workflow looks at the available requisition lines to be converted into purchase order lines and first determines the value of these attributes to determine whether to group requisition lines with the same data.
The workflow attributes are:
Is Grouping of Requisition Line Allowed?
Is Grouping of One Time Address Line Allowed?
Each of these attributes can have a value of Yes or No. Depending on the value selected, the workflow PO Create Documents behaves differently:
If the attribute Is Grouping of Requisition Line Allowed? is set to No, then no requisition lines are consolidated into a single purchase order line.
If grouping is set to occur, but Is Grouping of One Time Address Line Allowed? is set to No, then requisitions with one-time locations are not grouped.
If both attributes are set to Yes, then all similar requisition lines, even those with one-time locations are consolidated onto a single purchase order line. The default values for both attributes are Yes.
Note: When the attribute Is Grouping of One Time Address Line Allowed? is set to No, then no grouping of requisition lines with one-time locations occurs, even if the one-time addresses are the same.
The internal names of the preceding attributes are GROUPING_ALLOWED_FLAG and GROUP_ONE_ADDR_LINE_FLAG, respectively.
Append Quantity and UOM to Attachment
As one-time locations are converted and become attachments for the purchase order lines, these text attachments include the following information (for one-time location text attachments only):
Unit of Measure (UOM)
Quantity Ordered
The following is an example of the text of an attachment:
Please ship 30 (Each) to:
100 Mason St.
Palo Alto, CA
Setup Steps
Access the PO Create Documents Workflow. For more information, see .
Find the workflow attributes Is Grouping of Requisition Line Allowed? and Is Grouping of One Time Address Line Allowed?
To modify the grouping logic, change the values of these attributes from Yes to No. Yes is the default value for both attributes. The following table details the results of the various attribute setting combinations:
One-Time Location Grouping Attributes
Is Grouping of Requisition Line Allowed?
Is Grouping of One Time Address Line Allowed?
Groups all similar requisition lines regardless of the existence of one-time locations.
Groups similar requisition lines unless a one-time location is found on the requisition line.
No grouping of requisition lines ever occurs.
No grouping of requisition lines ever occurs.
Profile Options
POR: One Time Location must be set. For profile setup instructions, see .
The PO Create Documents workflow looks at the following attributes--Is Grouping of Requisition Line Allowed? and Is Grouping of One Time Address Line Allowed?--when determining if requisition lines should be grouped onto a single purchase order line.
Implementation Considerations
The automatic grouping logic only applies to the workflow PO Create Documents. When creating purchase documents through the Autocreate window, the buyer always has the ability to control the grouping function.
The POR: One Time Location profile option must be properly set for one-time locations to use within Oracle iProcurement.
If the first workflow attribute Is Grouping of Requisition Line Allowed? is set to No, then no grouping occurs, regardless of the setting of Is Grouping of One Time Address Line Allowed?
Hazard Information
Requesters can indicate hazard information for each line item of a requisition. As requesters create requisitions in Oracle iProcurement, they can associate both a hazard identification number and a hazard class with a requisition line. In addition, if an item already has a hazard identification number or a hazard class linked to it, either from a source document or the item master, then this default information is copied to the resulting requisition line.
Setup Steps
By default, the hazard fields are hidden. To display them, use Oracle Applications Framework. For more information, see .
Global Requester
Oracle iProcurement lets requesters create requisitions on behalf of another requester, even if that requester is in a different operating unit or business group. For example, a manager in the United Kingdom can order office supplies for a newly hired employee in the United States, even though the UK and the US represent different business groups. Possible scenarios include:
Global preparer. The manager in the UK logs on using the US responsibility. Even though the manager is not part of the US business group, the manager can create a requisition for a US employee.
Global requester. The manager in the UK logs on using the US responsibility and picks himself as the requester, even though the manager is not an employee in the US business group. For example, the manager is traveling to the US and needs to order supplies while in the US.
The process flow routes the resulting requisition for approval based on the preparer's approval path, when using an employee-supervisor hierarchy. When using a position hierarchy and the preparer or approver belongs to a different business group than the requester, then the preparer or approver must manually select an approver for the requisition. (The workflow cannot generate an approval list in this scenario.)
During Checkout, iProcurement shows the Requester field on the requisitiont. When global requester functionality is enabled, then clicking the Search icon next to this field lets you select requesters in other business groups.
Note: When you click the Flashlight icon, the list of available requesters includes all employees in the business group associated with the login responsibility, plus the preparer. For example, a manager in the UK logs on using the US responsibility. This manager sees everyone in the US business group, plus himeself.
If the global requester functionality is enabled while searching for requisitions on the Requisitions tab, then you can select the option Include employees from other organizations to expand the search to preparers or requesters in other business groups. The list of available preparers and requesters includes all employees in the business group associated with the login responsibility, plus the preparer.
Note: You can monitor only those requisitions that were created in the operating unit associated with your login responsibility. For example, a manager in the UK logged on using the US responsibility and created a requisition. When the manager logs on using the UK responsibility, the manager does not find the requisition. The manager finds it only when logging in using the US responsibility.
Setup Steps
Set HR: Cross Business Group to Yes to allow the selection of requesters in other business groups.
If this profile option is set to No, then preparers can select requesters in other operating units, but not in other business groups.
Set the profile option ICX: Override Requestor to either By All or Within Organization.
When ICX: Override Requestor is set to No, then the Requester field on the requisition defaults to the preparer and cannot be changed.
Profile Options
Set the following profile options as described in the preceding setup steps:
HR: Cross Business Group
ICX: Override Requestor
The following table show how Oracle iProcurement behaves depending on the setting of these profile options:
HR: Cross Business Group and ICX: Override Requestor
HR: Cross Business Group
ICX: Override Requestor
Preparer's Actions
Preparer can select any employee in or outside one's business group.
Within Organization
Preparer can select any employee in or outside one's business group.
Function Security
The functions for viewing or performing actions on My Group's Requisitions, My Requisitions, All Requisitions, Requisitions I Approved, and Orders to Approve behave the same regardless of how HR: Cross Business Group is set. For example, if the requester is given access to View My Group's Requisitions (and the security level access for the requisition document type in Oracle Purchasing is set to Public), then the requester can view all requisitions created in the operating unit that the requester is logged in to, regardless of whether the preparer belongs to the same business group.
Implementation Considerations
The accounting for the global requester functionality behaves no differently than it normally does:
If the item is an expense item and no account information is defined for the item, then the system verifies whether an account is associated with the requester (in the People window in Oracle Applications). As always, this account must share the same set of books as the operating unit in which the requisition is created.
If the account is not valid for the set of books of the operating unit in which the requisition is being created, then the system verifies the favorite accounts that the preparer has defined in the iProcurement Preferences. If a valid account does not exist in the preferences, then the system still tries to build the account using the expense charge account rules, if set up.
If the system cannot build the account information, then the preparer receives a prompt to enter the appropriate accounting information manually during checkout.
Displaying Charge Accounts
The following profile option determines how or whether to display charge account information at certain points during the checkout process:
The POR: Generate and Display Account at Checkout profile option affects the first step of the checkout.
The default setting for the POR: Generate and Display Account at Checkout profile option is No. When set to No, no charge account information appears during the first step of the checkout. (Charge account information always appears when you edit lines and on the last, review-and-submit page of the checkout.)
When POR: Generate and Display Account at Checkout is set to Yes, the charge account appears during the first step of the checkout, in the Billing section of the Checkout: Requisition Information page. (If the charge account varies by line, then the Charge Account field displays a Multiple link.)
The POR: Display Legacy Accounting Flex UI profile option affects the optional edit lines step of the checkout.
For example, the charge account, 01-510-0, appears in a single field if POR: Display Legacy Accounting Flex UI profile option is set to No (its default value). The requester can edit this field.
The same charge account, 01-510-0, would display each segment in a separate field if the POR: Display Legacy Accounting Flex UI profile option is set to Yes. In this example, the segments appear in separate columns: Company (01), Department (510), Account (7530), and Sub-Account (0000).
Whether the account appears in a single or separate field, the names of each segment still appear, and the requester can click a search icon to search for the valid accounts for each segment. Only the method of displaying and searching the segments changes.
Profile Options
Set the following profile options to implement this feature:
POR: Generate and Display Account at Checkout
POR: Display Legacy Accounting Flex UI
Expense Charge Account Rules
When determining the default charge account, the account generator may reference the charge account defined on the employee record. Expense Charge Account Rules enable you to override one or multiple segments of that default account based on the item category. This ability to override does not interfere with the action of the account generator, but replaces those segments you configure after the account generator has created a charge account.
Setup Steps
Log in to Oracle Applications and choose the Procure to Pay Administrator responsibility.
Navigate to Purchasing Setup & Financials & Accounting & Expense Account Rules.
Define the rules (for each item category) in the window. Duplicate rules for the same category or account segment are not permitted.
Save your work.
Profile Options
Set POR: Apply Expense Account Rules to Favorite Charge Accounts to Yes. See .
Employee P-Cards
Employee P-Cards let companies incorporate electronic payment and settlement procedures to streamline their procure-to-pay processes. Employers assign each requester his or her own employee P-Card to make purchases using Oracle iProcurement.
Setup Steps
For more information about setting up procurement cards, see the sections on Setting Up Credit Card Programs and Procurement Card Management in the Oracle Payables User's Guide.
In addition to the setup steps provided in the Oracle Payables User's Guide, you must enable supplier sites to accept procurement cards.
Log in to Oracle Applications. From the Oracle Purchasing menu, choose Supply Base & Suppliers.
Query the supplier associated with the supplier site that you want to set up.
Choose Sites. Query the supplier site for which you want to enable procurement cards.
Select the Procurement Card check box to indicate that the supplier site is P-Card enabled.
Save the changes.
Profile Options
POR: Override Supplier P-card must be evaluated when implementing this feature. For profile setup instructions, see .
Supplier P-Cards
Supplier P-Cards (or Ghost Cards) let companies incorporate electronic payment and settlement procedures to streamline their procure-to-pay processes. Instead of having to maintain a separate employee P-Card for each requester in the company and each requester having to use his or her own employee P-Card to make purchases, companies can maintain a single supplier P-Card for each supplier or supplier site in the system, and consolidate all purchases from that supplier or supplier site on the single P-Card. The feature lets all requisitions in Oracle iProcurement (across requesters) created against the respective supplier or supplier site be automatically charged to the single supplier P-Card. To enable the feature, the supplier P-Card must be set up and tied to the supplier or supplier site in advance. This arrangement improves control on the purchasing process and reduces maverick spending.
The following are the major business flows involved in the supplier P-Card functionality used in Oracle iProcurement:
Supplier P-Card Setup
Supplier P-Card Assignment For Requisitions
Supplier P-Card Setup
To enable the supplier P-Cards feature, enable supplier or supplier sites to accept procurement cards.
Log in to Oracle Applications. From the Oracle Purchasing menu, select Supply Base & Suppliers.
Query the supplier associated with the supplier site.
Choose Sites. Query the supplier site for which you want to enable procurement cards.
Select the Procurement Card check box to indicate that the supplier site is P-Card enabled.
Save the changes.
After the supplier or supplier sites have been enabled for P-Cards, set up supplier P-Cards in Oracle Payables using a process similar to the setup for employee P-Cards. The following diagram shows the windows that you use to set up supplier P-Cards in Oracle Payables.
Setup for Supplier P-Card
Card Programs: On this page, set up the following information for a P-Card: See the Oracle Payables User Guide for details.
Card Brand: Card brand name (American Express, Diners, Visa, Mastercard, and so forth).
Card Type: Select whether the card is of type Procurement, Travel, or Supplier. You can use only P-Cards of type Supplier and Employee in Oracle iProcurement. To set up a supplier P-Card, you would select a card type of Supplier.
Card Issuer/Issuer Site: Select a card issuer or issuer site for the card program. The card issuer or issuer site needs to be an active supplier or supplier site in the system.
Card Profiles: On this page, associate card profiles to the card program. You can associate multiple credit card profiles with each card program. The profile records any transaction amount limits that are associated with a P-Card. These transaction limits are passed to the P-Cards (both employee and supplier) that you create using the profile. See the Oracle Payables User Guide for details.
Note: When using the P-Card (employee or supplier) associated with the card profile for a requisition checkout in Oracle iProcurement, the transaction limit enforcement is::
If the aggregate amount (in functional currency for the operating unit) for all lines in the requisition checkout that can be charged to the P-Card is equal to or smaller than the transaction limit defined on the card profile, then the P-Card is assigned to all the lines.
If the aggregate amount (in functional currency for the operating unit) for all lenses) in the requisition checkout that can be charged to the P-Card is greater than the transaction limit defined on the card profile, then the P-Card is not assigned to any of the lines.
Credit Cards: On this page, define the P-Card and associate it with a card program and card profile. See the Oracle Payables User Guide for details.
In the Credit Cards window:
Enter Information for the P-Card, such as the card number and expiration date.
Associate the card with the card program and card profile.
If the card program is of type Procurement, then enter additional information about the employee who would own the P-Card.
If the card program selected is of type Supplier, then enter the supplier or supplier sites, which are to be associated with the supplier P-Card. The business rules for associating the P-Card to a supplier or supplier site when the card program selected is of type Supplier are:
You cannot complete the fields in the window that apply for a card program of type Procurement (such as Card Member Name, Employee Name, and Employee Number).
The supplier and supplier site fields on the window are mandatory. That is, each supplier P-Card must have at least one supplier or supplier site associated with it.
You can associate each supplier site only with a single supplier P-Card.
You can associate a single supplier P-Card with (shared by) multiple supplier sites as long as the supplier sites belong to the same supplier.
You can associate supplier sites within a supplier with different supplier P-Cards.
The Select All Eligible Sites button provides the requester the ability to enter the multiple supplier sites. Clicking this button automatically completes the supplier site fields for the selected supplier with valid but unassigned (that is, the site is not assigned to another supplier P-Card) supplier sites for the selected supplier.
For additional information about setting up supplier P-Cards, see the Oracle Payables User's Guide.
Supplier P-Card Assignment for Requisitions
When the requester creates a requisition in Oracle iProcurement, one of the following payment methods can be assigned to each line on the requisition:
Employee P-Card
Supplier P-Card
No P-Card (payment method on invoice)
As the requester is checking out a requisition in Oracle iProcurement, the application verifies and determines which payment method to assign to each line on the requisition. The first payment method (employee P-Card) is an option which the requester can explicitly select during the requisition checkout.
When certain conditions are met (the requester does not have to explicitly select them), the application automatically assigns the other payment methods (supplier P-Card and no P-Card) to the requisition line.
Note: A requisition in Oracle iProcurement can contain multiple lines. Depending on the source of the item or service on the line (internal or from external supplier or supplier site), the type of the item (expense or inventory) and other setup, different payment methods could apply to each line. Hence, the assignment of the payment method is done at the requisition line level, and not at the requisition header level.
The following business rules apply for the assignment of payment methods to a requisition line during checkout:
No P-Card (neither employee P-Card nor supplier P-Card) can be assigned to a requisition line in the following cases:
No supplier or supplier site is available or selected for the requisition line.
The item or service on the requisition line is sourced internally.
The supplier or supplier site available or selected for the requisition line is not P-Card enabled.
No employee P-Card has been set up for the requester and no supplier P-Card has been set up for the supplier or supplier site that is available or selected for the requisition line.
The requisition line is associated with a project, in which case a P-Card (employee or supplier) cannot be assigned to the line.
For an inventory item being delivered to a subinventory, a P-Card (employee or supplier) cannot be assigned to the line. On the other hand, if the inventory item is not delivered to a subinventory, then a P-Card (employee or supplier) can be assigned to the line.
If none of the preceding cases is met, then P-Cards (employee or supplier), if set up, are eligible to be assigned to the requisition line. Only one of them can be applied, and Oracle iProcurement determines which one to apply during the requisition checkout process.
To provide maximum flexibility, a system profile controls which P-Card (employee or supplier) gets precedence when both P-Card types are eligible to be applied to the requisition line. The profile option is POR: Override Supplier P-Card. This profile option applies to the Supplier P-Card Assignment for Requisitions business flow.
The following figure shows the business logic for assignment of P-Cards to a requisition line during a checkout if none of the cases mentioned in Rule #1 applies, and if the POR: Override Supplier P-Card profile option is set to No.
Supplier P-Card Assignment for Profile Set to No
The following figure shows the business logic for assignment of P-Cards to a requisition line during a checkout if none of the cases mentioned in Rule #1 applies and if the POR: Override Supplier P-Card profile option is set to Yes.
Supplier P-Card Assignment for Profile Set to Yes
After the application has determined the payment method for the requisition lines during checkout, the information is visible to the requester. Access to this information is available on the Review and Submit page during checkout, and also on the Requisition Details page after the requisition has been submitted. If an employee P-Card has been assigned to at least one line on the requisition, then the partially masked employee P-Card number appears in the P-Card Number field at the requisition header level. At the requisition line level, the P-Card Used field indicates which payment method is assigned to that particular line. The possible values for this field are:
Yes, when employee P-Card is assigned to the line
Supplier P-Card, when supplier P-Card is assigned to the line
No, when no P-Card is assigned to the line
Only one employee P-Card can be used for each requisition, and it might or might not apply to all the lines on the requisition. The P-Card Number field at the requisition header level contains either a single partially masked employee P-Card number or a blank value.
The requester does not see the actual supplier P-Card number (neither in the P-Card Number field at the requisition header level nor in the P-Card Used field at the requisition line level). The value of the P-Card Used field at the requisition line level (when it is Supplier P-Card) is the only indication to the requester that a supplier P-Card has been assigned to the line.
Common P-Card Logic
The requisition that is created in Oracle iProcurement is converted into a purchasing document in Oracle Purchasing. When all the necessary conditions are met, the resulting purchase order document contains the supplier P-Card number that was associated with the requisition line. The processes in Oracle Purchasing to convert a requisition into a purchase order include:
PO Create Documents workflow: Workflow process to automatically create standard purchase orders and blanket releases from approved requisitions.
Autocreate: Utility to manually create standard purchase orders and blanket releases from approved requisitions.
Create Releases: Concurrent program to generate releases for existing blanket purchase agreements from approved requisitions.
Requisition-to-Purchase Order Conversion Processes
The P-Card Used flag for the requisition lines coming from Oracle iProcurement holds the possible values: Yes, No, or Supplier P-Card. This flag determines whether and which P-Card number (employee or supplier or none) should apply to the purchase order, which Oracle Purchasing generates.
A P-Card (employee or supplier) can be assigned to purchase order documents of type Standard Purchase Order and Blanket Purchase Release only. Only one P-Card number (employee or supplier) can be assigned for each purchase order and is applied at the header level of the purchase order only, and, unlike a requisition in Oracle iProcurement, applies to all the lines on the purchase order.
Note: If purchase orders are created directly or are created from requisitions submitted in Oracle Purchasing (that is, there is no associated requisition in Oracle iProcurement), then no P-Card can be assigned to the purchase order, even if the particular supplier or supplier site accepts P-Cards.
The logic to determine how and which P-Card number (employee or supplier or none) should be applied to the purchase order works as indicated in the following table. This logic applies to all the requisition-to-purchase order conversion processes.
Common P-Card Logic
Value of P-Card Number for Requisition Header
Value of P-Card Used Flag for Requisition Lines
Requisition-to-Purchase Order Conversion Logic in Oracle Purchasing
Scenario is NOT possible. If no P-Card number is at requisition header level, all values for P-Card Used flag should be either No or Supplier.
No employee P-Card can apply to purchase orders. For such requisition lines:
If requisition lines have same supplier or supplier site and other purchase order header level information, then requisition lines can appear on a single purchase order. Else, requisition lines appear on different purchase orders.
No employee P-Card can be applied to purchase order. Derive supplier P-Card defined for supplier or supplier site: If supplier P-Card is valid (see ), maintain supplier P-Card for requisition lines. If supplier P-Card is invalid, delete supplier P-Card for requisition lines. For such requisition lines: If requisition lines have same supplier or supplier site and other purchase order header level information, then requisition lines can be put on a single purchase order. Else, requisition lines appear on different purchase orders.
Employee P-Card Number
Employee P-Card from requisition header can be applied to purchase order: If employee P-Card is valid (see ), maintain employee P-Card for requisition lines. If employee P-Card is invalid, delete employee P-Card for requisition lines. For such requisition lines: If requisition lines have same supplier or supplier site and other purchase order header level information, then requisition lines can be put on a single purchase order. Else, requisition lines appear on different purchase orders.
Employee P-Card Number
Do not apply employee P-Card from header level to lines. For such requisition lines: If requisition lines have same supplier or supplier site and other purchase order header level information, then requisition lines can be put on a single purchase order. Else, requisition lines appear on different purchase orders.
Note: Validity verification for employee and supplier P-Cards includes:
Is card active?, AND
Is card not expired?, AND
Is supplier or supplier Site P-Card enabled?
P-Cards In The Purchase Order Autocreate Window
In addition to the logic discussed in the preceding table, when a buyer in Oracle Purchasing converts a requisition into a purchase order using the Purchase Order Autocreate window, the buyer can resolve or change the supplier or supplier site at that time. Even if the buyer selects a supplier or supplier site that accepts supplier P-Cards, the P-Card information is not applied at that time. In other words, only the requisition lines that have P-Card information assigned to them during the requisition checkout in Oracle iProcurement can have P-Cards assigned to them in the resulting purchase order.
Changing Supplier Or Supplier Site On A P-Card Purchase Order
Even if a P-Card is assigned to the purchase order, the buyer has the ability to change the supplier or supplier site on the purchase order. The new supplier or supplier site might not accept P-Cards (employee or supplier) and it could lead to an error condition. Hence, if a P-Card (employee or supplier) exists on a purchase order, and, if the buyer changes the supplier or supplier site on the purchase order, the application automatically deletes the P-Card number on the purchase order. Before doing so, the application generates an appropriate warning message for the buyer.
Purchase Order Communication to Supplier
When the purchase order with the assigned supplier P-Card has been created and approved, the supplier P-Card information is sent as a part of the purchase order when it is communicated to the supplier. The information sent is adequate for the supplier to charge the amount on the purchase order to the assigned supplier P-Card. Similar to the existing support for the employee P-Card, the following information for the supplier P-Card is sent as a part of the purchase order:
P-Card Number
Card Member Name
Expiration Date for P-Card
Credit Card Brand
Also, similar to existing support for employee P-Cards, the supplier P-Card information is included as a part of the purchase order only when the purchase order is communicated to the supplier through EDI delivery and XML delivery.
For information about purchase order communication to the supplier using EDI delivery, see the Oracle e-Commerce Gateway User's Guide. For more information about purchase order communication to the supplier through XML delivery, see the Oracle Purchasing XML Transaction Delivery Guide and the Oracle XML Gateway User's Guide.
Profile Options
POR: Override Supplier P-Card must be set. For profile setup instructions, see .
Purchase Order (PO) Extract for P-Card Reconciliation
The P-Card reconciliation process electronically reconciles the P-Card statements and the corresponding purchase orders in the buyer's purchasing application for both employee and supplier P-Card transactions. The card issuer typically provides the reconciliation engine, which resides in the buyer's purchasing system. To accommodate the reconciliation process, the engine needs a couple of information feeds:
Transaction feed from the P-Card issuer containing charges for the billing cycle.
Purchase order history feed from the buyer's purchasing system for the billing cycle.
This reconciliation is necessary so that the buyer is able to electronically verify that only valid supplier purchase orders are included in the invoices that are paid to the card issuer. After a successful reconciliation between the PO history feed and the transaction feed, the reconciliation engine sends the reconciled data files to Oracle Payables (using the Oracle Payables Open Interface). The following figure shows the flow for the P-Card reconciliation process:
For more information about this part of the process, see the documentation provided with the reconciliation engine and the Oracle Payables User's Guide.
At the end of the P-Card billing cycle, the buying company receives a transaction feed containing an electronic statement for all P-Card purchases that the buying company made. The Purchase Order Extract for P-Card Reconciliation feature:
Extracts the corresponding purchase order information for the P-Card billing cycle
Provides the capability to prepare the purchase order history feed for the reconciliation engine. You can run the PO History Feed concurrent report or request in Oracle Purchasing to generate the feed. For more information, see the following topic, About the PO History Feed Concurrent Report.
Major Features
PO History Feed Concurrent Report
The concurrent report accumulates and compiles the necessary PO history data in a specific format. Upon its completion, the output file is stored in a specified directory location. The following business rules apply to the concurrent request:
Name for the concurrent program:
Title: Purchase Order History Feed for P-Card Reconciliation
Description: Purchase Order History Feed for reconciling P-Card payments
The concurrent program is a part of Oracle Purchasing.
You can run the program at any time, but typically you run it before the end of the monthly billing cycle for the P-Card. You can also set it to run at a specified frequency through standard report submission (SRS).
The output of the concurrent program appears in a specific directory. The directory is derived from the UTL_FILE_DIR parameter in the INIT.ORA file of the Oracle Purchasing installation. The application administrator should set up the output directory location prior to running the concurrent program.
Specify the following parameters on the PO History Feed Report Request window before running the report:
Card Brand Name: List of values containing all available card brand names.
Card Issuer/Card Issuer Site: List of values containing all valid card issuer and issuer Sites.
From Date/From Time: From Date and Time. The last_update_date for a purchase order should be on or later than the selected date and time.
After the requester has entered a valid Card Brand Name, Card Issuer and Card Issuer Site, the From Date/From Time field on the window gets automatically filled with the To Date and To Time information from the last successfully run report (report with Completed Phase with Normal status or Complete Phase with Warning status) for the selected card brand name and card issuer or card issuer site combination. Using this logic reduces the chances of sending duplicate PO History Feeds by running reports with overlapping dates and missing PO records by skipping intermediate dates.
Note: If the last run report for a particular card brand name and card issuer or card issuer site combination is not completed successfully (the request is in any phase or status other than Completed Phase with Normal Status or Complete Phase with Warning Status), then no tracking of the To Date/Time information for that request occurs.
To Date/To Time: To Date and Time. The last_update_date for a purchase order should be earlier than the selected date and time for it to be selected.
Output Filename: The name of the file in which the PO History feed file that the report generated should be stored in the output directory location. If a file with the same filename as the one selected in the Output Filename field already exists in the output directory, then the new file overwrites the existing file in the output directory.
Criteria Selection of Purchasing Records
Only purchase orders that satisfy certain selection criteria are included in the PO history feed. Some of the selection criteria for the purchase records are entered on the PO History Feed Report Request window (as described in the preceding section), while the application automatically and internally applies the rest of the selection criteria. The internal selection criteria are:
Only purchase orders of type Standard Purchase Order and Blanket Release are available for selection.
Only purchase orders created against supplier or supplier sites that belong to the same operating unit as the requester's responsibility are selected.
The different values for the Approval Status, Control Status, and On Hold Status for the purchase order in Oracle Purchasing determine whether the purchase orders should be sent as a part of the PO History Feed. The following business rules apply:
Only purchase orders with an approval status of Approved and Requires Reapproval are eligible for selection. Purchase orders with any other approval status do not get extracted.
Purchase orders with an approval status of Requires Reapproval get selected only if they have been approved at least one time before they were put in the current approval status of Requires Reapproval.
Based on a combination of the Approval status, Control status, and On Hold status for the purchase order, the program generates possible statuses for the Order Status field for the purchase order included in the PO History Feed:
ON: Purchase order is open and should be reconciled with the corresponding transaction feed from the card issuer.
HL: Purchase order is temporarily put on hold, but the hold may get released at a later time. It should not be reconciled with the corresponding transaction feed from the card issuer while it remains in the HL status.
CN: Purchase order is permanently canceled and should not be reconciled with the corresponding transaction feed from the card issuer.
The following figure indicates the selection logic based on the Approval, Control, and On Hold statuses of the purchase order in Oracle Purchasing and the appropriate output status for the purchase order in the PO History Feed.
Status and Selection Logic
Approval Status
Control Status
On Hold Status
Selection and Status of Purchase Order in PO History Feed
All except Canceled and Finally Closed
Not On Hold
PO is sent with Order Status = ON
All except Canceled and Finally Closed
PO is sent with Order Status = HL
Canceled OR Finally Closed
Does Not Matter
PO is sent with Order Status = CN
In Process
Does Not Matter
Does Not Matter
PO is not sent
Incomplete
Does Not Matter
Does Not Matter
PO is not sent
Pre-approved
Does Not Matter
Does Not Matter
PO is not sent
Does Not Matter
Does Not Matter
PO is not sent
Requires Reapproval1.
All except Canceled and Finally Closed
Does Not Matter
If (PO APPROVED_DATE ¹ NULL), PO is sent with Order Status = HL If (PO APPROVED_DATE = NULL), PO is not sent
Requires Reapproval3.
Canceled or Finally Closed
Does Not Matter
If (PO APPROVED_DATE ¹ NULL), PO is sent with Order Status = CN If (PO APPROVED_DATE = NULL), PO is not sent
For information about the format and data elements of PO History Feed, see .
Setup Steps
The output of the concurrent program is stored in a specific directory. The directory is derived from the UTL_FILE_DIR parameter in the INIT.ORA file of the Oracle Purchasing installation. For more information about setting the output directory location, see the Oracle e-Commerce Gateway Implementation Manual.
Project Accounting
Integration with Oracle Projects enables requesters to optionally reference project and task information on requisition lines. Cost distribution of a single requisition line can span one or more projects.
Setup Steps
You must license and implement Oracle Projects. For more information, see the Oracle Projects Implementation Guide.
When you are implementing Oracle Projects, decide whether to expose the project and task fields to requesters:
By default, the following fields appear if Oracle Projects is installed and the destination type is Expense: Project, Task, Expenditure Type, Expenditure Organization, and Expenditure Item Date.
If the destination type is Inventory or Shop Floor, then the Project and Task fields require you to enable Project Manufacturing.
To hide any of the project-related fields, then use Oracle Applications Framework. For more information, see .
Note: If you have installed Oracle Projects, then the project-related fields appear in the Billing section of the requisition, even if you do not implement or use Oracle Projects. You can hide these fields if you do not use them.
Grants Accounting
Oracle Grants Accounting integrates with Oracle iProcurement to support the charging of requisitions and resulting purchase orders to projects that grants (awards) funded. The integration introduces the concept of an award number, which represents additional information about the source of funding associated with projects and tasks.
In addition to the standard project and task information, the Award dimension from Oracle Grants Accounting can specify the source of funding associated with projects and tasks. This helps organizations manage all aspects of the grant funding they receive. In higher education institutions, other public sector agencies, and project-intensive commercial enterprises, it is often necessary to distribute the cost of a purchase request line across multiple projects. To support this need, you can enter multiple projects and awards for each requisition line.
You must enable the Award number field if you have implemented Oracle Grants Accounting for the associated operating unit. The Award number field is only required for projects that awards in Oracle Grants Accounting fund.
Setup Steps
You must license and implement Oracle Projects and Oracle Grants Accounting. For more information, see the Oracle Grants Accounting User's Guide.
By default, the Award field appears if you have implemented Oracle Grants Accounting for the associated operating unit. To hide this field, use Oracle Applications Framework. For more information, see .
Favorite Charge Accounts
The favorite charge accounts functionality provides the requester the capability to maintain a list of up to 50 frequently used charge accounts on the iProcurement Preferences page. During the checkout process, the requester can access the favorite charge accounts list and use it to automatically complete the charge account information for the items, rather than having to manually enter the charge account information.
Setup Steps
Log in to Oracle iProcurement.
On the Home page, click Preferences in the upper-right corner.
In the Preferences area, click iProcurement Preferences.
Enter Favorite Charge Accounts and a nickname for each account. To add another row, click Add Another Row.
Select a default favorite charge account.
Save the changes.
Function Security
Function Security exists to disable the Favorite Charge Account List functionality. The function is called Favorite Charge Accounts. For information about function security setup, see .
Implementation Considerations
The favorite charge account list is the last resort to generate the charge account information for the item. If the Account Generator workflow engine, which includes Employee Default Charge Account and the Commodity-based Accounting Rules, has already been set up, then the favorite charge accounts functionality does not affect it.
The requester can add, delete, or modify accounts in the list. A nickname for an account is mandatory, and it must be unique by list. One of the accounts in the list must be selected as the default.
The requester can have one favorite charge account list for each responsibility. If the requester has multiple responsibilities, they can choose a favorite charge account list by responsibility. The accounts maintained in one responsibility are not available in the other responsibilities. If the requester has responsibilities that roll up to multiple sets of books with different accounting structures, then the favorite charge accounts list conforms to the respective accounting structures.
The favorite charge account functionality does not affect the system profile for Dynamic Insertion of Charge Accounts. If the profile has been turned on, requesters still can create new charge accounts simultaneously in the preferences as well as during the edit lines step of the checkout.
A requester can store only valid charge accounts in the favorite charge account list. If a charge account is deactivated in Oracle General Ledger after the requester has already stored it in the favorite charge accounts list, then an error appears when the requester resubmits the iProcurement Preferences page (by clicking Apply Changes). The requester then has the opportunity to edit or delete the charge account in the favorite charge account list. Until the deactivated account is changed, it displays an error if it is used during checkout.
You can conduct requisition approvals in Oracle iProcurement in the following ways:
Use the approval setup from Oracle Purchasing. For more information, see the Oracle Purchasing User's Guide.
Use Oracle Approvals Management, also known as the Approvals Management Engine (AME). AME lets you define approval rules one time and leverage them across multiple applications.
The following figure shows that an employee and supervisor approval setup in Oracle Purchasing consists of:
Define jobs
Define document types
Define approval groups
Assign approval groups
Assign employees
Approval Setup in Oracle Purchasing
The following figure shows how the approvals setup appears using AME. For descriptions of each of these steps, see the .
Approval Setup Using AME
Whether you set up approvals in Oracle Purchasing or AME, the Requisition approval workflow in Oracle Purchasing handles the approval. For example, the Approval List Routing Using AME process in the Requisition approval workflow is initiated if AME approvals have been set up. (See the .) This process uses your approval setup in AME to perform the approval, send notifications, and complete other approval tasks in Oracle iProcurement.
Implementing Oracle Purchasing Approvals
For instructions, see the approval setup information in the Oracle Purchasing User's Guide. See also information about requisition approval workflow attributes, whose defaults you can change, in the Oracle Purchasing User's Guide.
Implementing AME Approvals
Offline, analyze your approval structure. Determine the approval structure to use in iProcurement
An example of Employee/Supervisor approval structure:
Meredith Walton, Buyer, reports to
Pat Stock, Manager, reports to
Casey Brown, Executive
An example of Position Hierarchy approval structure:
Shop Floor Manager reports to
Production Manager who reports to
Plant Manager
If you are going to use the Employee/Supervisor structure you must perform the following tasks:
In the Human Resources responsibility, navigate to the Job Window.
Create a job.
Assign approval authority to the job.
Create employees and assign appropriate jobs and supervisors.
Create users.
Add appropriate responsibilities to the users.
For complete details on performing these steps, see: Oracle HRMS Enterprise and Workforce Management Guide.
If you are going to use the Position Hierarchy structure you must perform the following tasks:
In the Human Resources responsibility, navigate to the Positions Window.
Create all of your organization's positions.
Use the Position Hierarchy window to build and administer your position hierarchies.
Create employees and assign them to the referenced positions with the Enter Person window.
Use the Submit Requests window to run the Fill Employee Hierarchy process.
Create users.
Add appropriate responsibilities to the users.
For complete details on performing these steps, see: Oracle HRMS Enterprise and Workforce Management Guide.
In Oracle Purchasing, navigate to the Document Types window.
Select a Document Type:
Purchase Requisition
Internal Requisitions
Change Order Request: Requisition
For the selected document type, select one of the provided Approval Transaction Types, or one that you created in AME:
PURCHASE_REQ
INTERNAL_REQ
Document Types Window
Note: Use the Approval Transaction Types field to enable or disable AME. If a transaction type is selected in this field, then Oracle iProcurement uses AME to conduct approvals. If you leave the Approval Transaction Types field blank, then AME approvals are not used. Instead, the approval setup in Oracle Purchasing are used.
Use the Oracle Approvals Management Implementation Guide, available on My Oracle Support forum to complete the following steps:
Create attributes. See the following list of attributes that Oracle iProcurement provides. For example:
ITEM_CATEGORY (line level)
REQUISITION_TOTAL (header level)
Create conditions using the attributes. Conditions are the "if" clause in an action rule. They are similar to approval groups in Oracle Purchasing. For the rule to apply to a transaction, all of its conditions must be true.
For example, to enforce a rule about a requisition's total amount, you could have the following condition, where REQUISITION_AMOUNT is an attribute: USD1000 &= REQUISITION_AMOUNT & USD5000. In this example, a requisition initiates this approval rule when the requisition total amount is greater than or equal to 1000 USD and under 5000 USD.
Create approval groups. An approval group is an ordered set or list of one or more approvers. For example, an approval rule can add an approval group's members, in order, to a transaction's approval list. Typically, approval groups represent functional approvers outside a transaction's chain of authority, such as finance or internal legal counsel, who must approve a transaction before or after management has done so. You can also insert an approval group into the chain of authority.
Define actions. Actions generate the approval list for a transaction. If a transaction satisfies all conditions in an action rule, then the associated actions are processed to generate the approval list.
The Action Types page is where you would define approval groups with the same order number to enable parallel approval.
It is also the page where you define voting methods. This provides you with the ability to model group approvals more closely to the business rules that your organization uses. For example, you might choose First Responder Wins.
Create action rules.
Define rules based on the conditions that result in an action. For example:
If the condition USD1000 &= REQUISITION_AMOUNT & USD5000 is met, then require approvals up to at least level 1 approval authority.
If the condition USD5000 &= REQUISITION_AMOUNT & USD9000 is met, then require approvals up to at least level 2 approval authority.
In the following example:
If the condition 0 USD &= REQUISITION_TOTAL &= 100 USD, then require approvals up to at least level 1.
If the condition 1000 USD & REQUISITION_TOTAL &= 25000 USD, then require approvals up to at least level 2.
If the condition ITEM_CATEGORY in {IT.EQUIPMENT...}, then require post-approval from IT approval group.
Approval Authority
Meredith Walton
Casey Brown
Connie Horton (in the IT approval group)
IT Manager
Provided AME Attributes
Oracle iProcurement provides the following types of AME attributes:
AME mandatory attributes}