| Indicators | Description |
|---|
Contract Screen
Main information | Tool | ARIBA : Contract Management |
Process
Sub-Process | SPP : Solvay Purchasing Process Process: 3 Negotiate and Contract Sub-Process: 3.2 Contract |
| Definition | Measuring the number of Purchasing contract and the annual amount. Contracts which have the status "Closed" are excluded. |
Zone
| Worldwide |
| Scope | All Contracts store in ARIBA (according to ARIBA process*), excluding: - contracts Domain "Energy".
All corporate functions are gathered in "CBS function". |
| Loading data Frequency | Monthly |
| Referring | Purchasing and Supply Chain Excellence Solutions |
| Expected Evolution | Decreasing "Expired Contract" number and amount. |
Useful Tips Caution | Getting the portfolio according to the Buyers name. Through Bookmark functionality, you can keep it! ARIBA is based on hierarchical data, it raises the high level but not the low level except if it was selected by buyer. |
Screen (click on the screenshot to enlarge it) |   |
| Main Dimensions | - Currency (EUR/USD) : the exchange rates is based on the exchange rates set in ARIBA.
- Month/Year : month/year of the extraction from ARIBA, by default is the previous month (M-1).
- Zone : this is the zone of the contract. This zone is set according to the input of the buye.r
- PUR Contract Scope : see above the scope definition.
- Country : this is the country of the contract, if the contract is set on the level Zone, the item "No country" will be dispalyed.
- Site: this is the site of the contract, if the contract is set on the level Zone or Country, the item "No site" will be dispalyed.
- GBU (ARIBA) : this is the GBU/Corporate function which is impact by the contract (GBU/Function internal client). There is not link between ARIBA GBU/Function and BW.
- Domain : GPS domain.
- Segment : GPS segment.
- Group PUR : in ARIBA the group PUR is going to be implemented in replacement of DUNS Ultimate code.
- Supplier PRS : supplier database is based on PRS code. A cleansing is on-going.
- Owner : this is the buyer who is in charge of the contract
|
Number of Contracts
| Features
| - Lifecycle contract in ARIBA is related to Status, in contract screen we keep 2 main status:
| Status in QlikView | Status in ARIBA | Expiration date | Description |
|---|
| Draft | Draft | "Y": expiration date of the contract has been exceeded "N": expiration date of the contract has not been exceeded | The contract has not Published it means: - The systems does not take into account the expiration date to change the status to "Expired";
- The buyer in charge of the contract will not receive notifications related to the notice period or the expiration date.
| | Draft Amendment | | On Hold | | Published | Pending | "Y": expiration date of the contract has been exceeded "N": expiration date of the contract has not been exceeded | The contract has Published it means: - The systems takes into account the expiration date to change the status to "Expired";
- The buyer in charge of the contract receives notifications related to the notice period or the expiration date.
| | Published | | Expired | | Closed | Closed | The contract is closed by buyer in charge of the contract regardless of the expiration date. | Closed contracts are not raised by QlikView. Closed contracts mean that the commitment with the supplier about a subject has been ceased. |
|
Annual Contract Amount | Features | A contract in ARIBA can affect several GBU, Zone/Country and site and Domain/Segment.
 The contract amount is a global amount it means that there are not split according to GBU, Zone/Country/Site and Domain/Segment. The Annual Contract Amount is equal to: Contract amount / (Expiration date in Year- Effective date in Year) If a renewal period has been sent in the contract, the expiration date will include the extended period.
If the contract has not expiration date ("perpetual" term type), the annual amount will be equal to 0 (case for the contract created before July 2013). |
The best way to get IT support is to use the new
Service One Platform.