Central purchase contracts are global long-term agreements negotiated between an organization and a supplier. This helps in getting the best rates and conditions while bundling purchasing volume across multiple subsidiaries. These contracts are typically negotiated by the central purchasing organization, mostly at the headquarters, and used for globally driving operational efficiency, reduced cost while complying with regulations across multiple subsidiaries.
The central purchase contract, created at the headquarters, can be distributed to subsidiaries to generate local contracts or scheduling agreements. The splitting of distributions into outline agreements in the connected system is based on the split criteria which comprises of the following attributes:
- Purchasing Document Category (Contract or Scheduling agreement)
- Purchasing Document Type
- Purchasing Organization
- Connected Company Code
- Connected System
- Connected Plant
- Purchasing Group
- Document Currency
- Payment Terms
Once outline agreements are created in the connected systems, subsidiaries can then continue with the operational procurement in a seamless manner by leveraging this local contract or scheduling agreement. Central monitoring of contract consumption across subsidiaries and renewal of expiring contracts is easily managed by the headquarters.
This feature of creating central purchase contracts is available through the FIORI application Manage Central Purchase Contracts (link to documentation in help.sap.com) delivered as part of SAP S/4HANA for Central Procurement.
Check out the video accessible through the below link for a quick overview on central contracts, their distribution, follow on processes in the connected systems and subsequent consumption monitoring of the operational outline agreements at the hub system:
In this blog post, we will discuss in detail a new feature in the Manage Central Purchase Contracts FIORI application that enables the creation of Central Purchase Contract Hierarchy – central contracts with a level of hierarchy.
- As a configuration expert, it is possible to group company codes into groups such that each group represents a subsidiary/location/branch etc. This group configuration can then be used for creation of central purchase contract hierarchies in the Manage Central Purchase Contracts FIORI app.
- Distributions can be maintained for different company codes at the header and item level of the document. The company code groups are automatically populated on the distributions based on the above configuration.
- On approval of the central purchase contract hierarchy, subordinate central contracts are created for company code groups that have one or more distributions maintained in the hierarchy document. Subordinate Central Contracts section shows the central contracts that are created from the hierarchy document.
- Distribution Overview section lists the unique distributions maintained across the multiple connected systems based on the split criteria.
- The subordinate central contracts, after approval, get distributed resulting in creation of outline agreements in the connected systems.
- Let’s look at a hypothetical example to visualize how company codes across connected systems can be grouped to enable the creation of central purchase contract hierarchies:
|Connected System||Connected Company Code||Company Code Group||Distribution|
- Assume that a central purchase contract hierarchy is created with distributions for all the company codes CC1, CC2, CC3, CC4 and CC5. On approval of the hierarchy document, two subordinate central purchase contracts will be created, one each for GRP1 and and GRP2.
- The subordinate central contract created for GRP1 will have the distributions corresponding to GRP1 and similarly the distributions corresponding to GRP2 will be present on the subordinate central contract created for GRP2
|Company Code Group||Subordinate Central Contract|
- Assume that the distributions are maintained such that based on the split criteria, the distributions 1 and 2 can be grouped into a single outline agreement, while all other distribution are grouped into separate outline agreements as depicted below:
|Subordinate Central Contract||Distributions||Connected System||Outline Agreement|
- For the above example, the final view of the documents across systems would be as below:
- The outline agreements in the connected system can then be used for operational procurement
- The release information for the operational documents can be pulled to the hub system using the Schedule Import of Release Orders app
- The consumption details (release information) of the outline agreements can be seen in the subordinate central contracts
- The accumulated consumption percentages of the distributions and the items can be seen in the hierarchy document at the items and distribution levels.
This is a brief overview of the Central Purchase Contract Hierarchy feature available with SAP S/4HANA for Central Procurement from 2005 CE. You can go through the below video to get familiar with this feature.
Hope you found this blog post insightful. Share your feedback and thoughts in the comments section and in case of further questions, please post them in the Central Procurement community page using the link below:
For more information on SAP S/4HANA for Central Procurement, check out the below links: