Skip to main content

iProcurement Information Templates

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
  1. Navigate to the Define Information Template window in Oracle Purchasing.

  2. Give your Template a name.This name appears as a heading during checkout.
  3. 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.

  4. 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.

  5. Enter an Attribute Name and Description. The Attribute Description is the actual field prompt that appears in Oracle iProcurement.

    Define Information Template Window
    the picture is described in the document text

    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.

  6. 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.

  7. To make the template field to be a list of values from which the requester selects, see the steps for creating lists.

  8. 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.

  9. 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.

  10. Choose Associate Template to associate the template with an item or item category.

    Information Template Association Window

    the picture is described in the document text
  11. In the Information Template Association window select the type of association (Item Number or Item Category) to associate with the template.

  12. If you selected Item Number, enter the number. If you selected Item Category, enter the category.

  13. 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.
  1. Log in to Oracle Purchasing.
  2. Use the following navigation: Setup > Flexfields > Validation > Sets.
  3. 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.
  4. Use the following navigation: Setup > Flexfields > Validation > Values.
  5. 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.
  6. Access the Information Templates window the preceding instructions for defining information templates describe
  7. In the LOV field, select your validation set name.
  8. 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 picture is described in the document text

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.)


Popular posts from this blog

SQL Query to extract Oracle Purchase Order Information

SELECT   poh.po_header_id,    poh.type_lookup_code PO_TYPE,   poh.authorization_status PO_STATUS,   poh.segment1 PO_NUMBER,   pov.vendor_name SUPPLIER_NAME,   povs.vendor_site_code Location,   hrls.location_code Ship_To,   hrlb.location_code Bill_to,   pol.line_num ,   msib.segment1 Item,   pol.unit_price,   pol.quantity,   pod.amount_billed Amount,   pod.destination_subinventory,   ppf.full_name Buyer_Name,   poh.closed_Code  FROM   PO_HEADERS_ALL poh,   PO_LINES_ALL pol,   mtl_system_items_b msib,   PO_LINE_LOCATIONS_ALL poll,   PO_DISTRIBUTIONS_ALL pod,   po_vendors pov,   po_vendor_sites_All povs,   hr_locations_all hrls,   hr_locations_all hrlb,   per_all_people_f ppf,   po_line_types polt WHERE   1                         =1 AND polt.line_type_id    = pol.line_type_id AND povs.vendor_site_id     = poh.vendor_site_id AND pov.vendor_id           = poh.vendor_id AND pol.item_id             = msib.inventory_item_id AND msib.organization_id  

Query to find Operating Unit, Business Group and Legal Entity Information

SELECT   DISTINCT   hrl . country ,                  hroutl_bg . name              bg ,                  hroutl_bg . organization_id ,                  lep . legal_entity_id ,                  lep . name                    legal_entity ,                  hroutl_ou . name              ou_name ,                  hroutl_ou . organization_id   org_id ,                  hrl . location_id ,                  hrl . location_code ,                  glev . flex_segment_value FROM     apps . xle_entity_profiles   lep ,         apps . xle_registrations   reg ,         apps . hr_locations_all   hrl ,         apps . hz_parties   hzp ,         apps . fnd_territories_vl   ter ,         apps . hr_operating_units   hro ,         apps . hr_all_organization_units_tl   hroutl_bg ,         apps . hr_all_organization_units_tl   hroutl_ou ,         hr_organization_units   gloperatingunitseo ,         apps . gl_legal_entities_bsvs   glev WHERE    lep . transacting_entity_flag   =   'Y'         AND   l

List of iExpenses Tables

List of iExpenses Tables  Table Name Description AP_EXPENSE_REPORT_HEADERS_ALL Expense report header information AP_EXPENSE_REPORT_LINES_ALL Expense report lines information AP_EXP_REPORT_DISTS_ALL Expense report distribution information. It contains the accounts against each expense report line. AP_CREDIT_CARD_TRXNS_ALL Table to store the corporate credit card transactions that are sent by the banks. These lines are saved as expense lines when the user creates the expense lines for credit cards AP_NOTES Table to store the comments entered by approvers and auditors     Setup tables   AP_EXPENSE_REPORTS_ALL This table contains the header level information about the expense templates AP_EXPENSE_REPORT_PARAMS_ALL This table contains the detail level information about the expense templates AP_POL_CAT_OPTIONS_ALL Table to store the policy options AP_POL_CONTEXT Table to store the policy context     AP_POL_LOCATIONS_TL Table