Skip to main content

Global Agreements in iProcurement


Overview

Using global agreements, purchasing professionals are able to negotiate prices on behalf of multiple organizations within an enterprise and then enable the resulting agreement to be shared by those organizations for procuring products and services.

Global Agreements allow buying organizations to negotiate pricing and define agreements in a centralized shared services environment. Execution against the Global Agreement can be controlled and handled in more than one operating unit. Instead of creating multiple agreements in multiple operating units, you can create a single global agreement that can be viewed and used for sourcing by multiple operating units.

In addition to the Supplier/Supplier Site with whom the agreement was negotiated by the negotiating organization, it may not be the same supplier site which processes the purchase orders from the multiple buying organizations, where the agreement is enabled.

Creating and Using a Global Agreement

  • Create a Global Agreement in an Operating Unit (a Contract Purchase Agreement with the Global box and Enable All Sites box checked) - (N) Purchase Orders > Purchase Orders.
  • Enable the Agreement in multiple Operating Units. (N) Purchase Orders > Purchase Orders > Tools > Enable Organizations.
  • Optionally define local attributes for each of the Operating Units. This includes buyer, supplier site, freight carrier.
  • Local organizations can view and use the Global Agreement, however, they cannot make any changes to it. Only the local attributes can be changed by the buyers in the local organization.
  • Standard POs are created in the local organization using the local document sequence number for Purchase Orders that gets generated and stored by the system

Global Agreements in Oracle iProcurement

The following areas are impacted by the global agreements enhancements in Oracle iProcurement:
  • Catalogs can now refer to supplier sites that are not on the Contract Purchase Agreement.
  • You can bulk load content from a supplier site that is not on the Contract Purchase Agreement.
  • Re-defaulting of the contract site from the contract does not take place.
  • Non-catalog requests referencing a contract allow updates to supplier site.
  • For the Punch Out items referring to a global contract agreement, you can reference the contract. The punch out supplier return sites are valid for the supplier but do not necessarily match the site in the contract.

Comments

Post a Comment

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  
Post a Comment
Read more

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
Post a Comment
Read more

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
Post a Comment
Read more