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

How To Enable / Disable Forms Personalization Option

Forms Personalization gives great flexibility to execute custom business logic without performing so much of technical work. To start forms personalization navigate to Help -> Diagnostics -> Custom Code -> Personalize But many time when we click on personalize it give below error  " Function is not available for this respnosibility. Change responsibilities or contact your System Administrator " To Enable access to forms personalization function we need to set below profile option.  -  Utilities:Diagnostics -> Yes / No It determines the diagnostics option is enabled for a user / responsibility or site, depending on the level profile option is set. Navigate to System Administrator -> Profile -> System Query for your user / responsibility for which you want to provide access. Set the value to 'Yes' , If you want allow access to forms personalization Since we change the profile option please change the respons...
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 ,               ...
Post a Comment
Read more

Oracle Purchasing – Receipt Accounting

Oracle Purchasing – Receipt Accounting (Accrue On Receipt and Accrue at Period End) Inventory Accruals: Inventory and Purchasing provides visibility and control of accrued liabilities for inventory items. Purchasing automatically records the accrued liability for the inventory items at the time of receipt. This transaction is automatically recorded in the general ledger at the time of receipt. The inventory expense is recorded at delivery if Standard Delivery is used and at receipt if Direct Delivery used. Expense Accruals: Purchasing optionally accrues un-invoiced receipts of non-inventory items when a period is closed. Purchasing automatically creates a balanced journal entry for each receipt un-invoiced at period end which can be reversed at the beginning of the next period. Navigation: India Local Purchasing > Oracle Purchasing > Setup > Organizations > Purchasing Options Difference between 'Accrue On Receipt' and 'Accrue at Per...
Post a Comment
Read more