{"id":3397,"date":"2016-02-29T16:12:06","date_gmt":"2016-02-29T15:12:06","guid":{"rendered":"https:\/\/compera.vanvlerken.nl\/central-contracts-vanaf-srm-7-0\/"},"modified":"2018-03-26T14:46:06","modified_gmt":"2018-03-26T13:46:06","slug":"central-contracts-srm-70","status":"publish","type":"post","link":"https:\/\/compera.vanvlerken.nl\/en\/central-contracts-srm-70\/","title":{"rendered":"Central Contracts in SRM 7.0"},"content":{"rendered":"

[et_pb_section bb_built=”1″ admin_label=”section”][et_pb_row admin_label=”row” background_position=”top_left” background_repeat=”repeat” background_size=”initial”][et_pb_column type=”4_4″][et_pb_text background_layout=”light” text_orientation=”left” use_border_color=”off” border_color=”#ffffff” border_style=”solid” background_position=”top_left” background_repeat=”repeat” background_size=”initial”]<\/p>\n

SAP has introduced a renewed concept for contract management in SRM 7.0: Central Contract Management. At first sight there doesn’t seem to have changed too much. For instance, just like in SRM 5 contracts can be distributed to the desired backend(s). Also contracts can be created to be called off upon in SRM purchase orders in the Extended Classic scenario. However, there definitively are some subjects that are worth taking a closer look at.<\/p>\n

What does Central Contract Management deliver more than Global Outline Agreements?<\/strong><\/p>\n

By far the most important enhancement compared to Global Outline Agreements is the ability to use an aggregated contract for procurment in you entire landscape in the form of a Central Contract. This means that one single Central Contract can be distributed to multiple backends and can be used as a source of supply in SRM itself. It offers the ideal functionality to directly get a full overview of the global usage of the Central Contract. That’s because all call-offs are confirmed back to the Central Contract, regardless the origin of the call-off.<\/p>\n

<\/p>\n

Distribution, call-off confirmation and real time checks via SOA Enterprise Services.<\/strong><\/p>\n

Central Contract Management uses standard SOA Enterprise Services for communication from and toward the different backends. SAP PI is actually not mandatory here, because the set of services can also be used via Web Services Reliable Messaging (WSRM). For all maintenance tasks standard SAP webservice tools are available.\u00a0Even though Central Contracts can still be distributed via iDocs, in that case classic Out,ine Agreements are created in the backend. The real time SRM Pricing Check also only works via webservices. With the use of a Badi implementation an older bakcend system can easily be connected to SRM Central Contract Management. Therefor a diverse landscape does not have to be a limitation.<\/span><\/p>\n

<\/p>\n

Central Contract in SAP ECC Ehp4 and up.<\/strong><\/p>\n

The distribution of an SRM Central Contract results in a Central Contract in ECC. The biggest difference with an Outline Agreement is the extra “layer” of the Central Contract. Still Outline Agreements are created, but they are now bundled in one Central Contract (if it originates from one SRM Central Contract). In standard configuration the contract number is identical of that of SRM. For the call-off creation for a Central Contract there are new fields added to directly link the call-off to the SRM Central Contract and the Contract item. Also a new search help is delivered to search based on the Outline Agreement number and\/or the Central Contract number.<\/p>\n

Migration from Global Outline Agreement to Central Contracts.<\/strong><\/p>\n

During an upgrade of SRM 7\/ECC6 Ehp4 it is necessary to convert already created and distributed Global Outline Agreements in SRM and ECC to Central Contracts. This can easily be done by using a conversion report in ECC and an ugrade report in ECC and SRM. That way all Outline Agreements in ECC will be converted to Central Contracts, without the loss of aggregated data. Thanks to these programs you are a lot more flexible while implementing Central Contracts, especially in heterogeneous landscapes.<\/p>\n

Display\u00a0Global Outline Agreement<\/strong> in SAP ECC:<\/em><\/p>\n

<\/p>\n

Display\u00a0Central Contract<\/strong> in SAP ECC:<\/em><\/p>\n

<\/p>\n

[\/et_pb_text][\/et_pb_column][\/et_pb_row][\/et_pb_section]<\/p>\n","protected":false},"excerpt":{"rendered":"

SAP has introduced a renewed concept for contract management in SRM 7.0: Central Contract Management. At first sight there doesn’t seem to have changed too much. For instance, just like in SRM 5 contracts can be distributed to the desired backend(s). Also contracts can be created to be called off upon in SRM purchase orders […]<\/p>\n","protected":false},"author":6,"featured_media":3035,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"on","_et_pb_old_content":"

SAP heeft in SRM 7.0 een vernieuwd concept voor contract management ge\u00efntroduceerd: Central Contract Management. Op het eerste zicht lijkt er niet zo veel veranderd. Zo kunnen contracten net als in SRM 5 gedistribueerd worden naar de gewenste backend(s). Ook kunnen contracten aangelegd worden om op af te roepen in SRM bestellingen in het Extended Classic scenario. Toch zijn er wel degelijk wat onderwerpen die de moeite waard zijn om wat nader toe te lichten.<\/p>

Wat biedt Central Contract Management meer dan Global Outline Agreements?<\/strong><\/p>

Veruit de belangrijkste vooruitgang ten opzichte van Global Outline Agreements is het kunnen gebruiken van een geaggregeerd contract voor inkoop in je gehele landschap in de vorm van een Central Contract. Dit betekent dat \u00e9\u00e9n enkel Central Contract kan worden gedistribueerd naar meerdere backends \u00e9n gebruikt kan worden als source of supply in SRM zelf. Het biedt de ideale kapstok om in \u00e9\u00e9n oogopslag een volledig overzicht te krijgen van de globale uitnutting van het Central Contract. Alle afroepen worden immers teruggemeld naar het Central Contract, ongeacht de oorsprong van de afroep.<\/p>

\"Compera\"<\/p>

Distributie, afroepbevestigingen en real time checks via SOA Enterprise Services.<\/strong><\/p>

Central Contract Management maakt gebruik van standaard SOA Enterprise Services voor de communicatie van en naar de verschillende backends. Hiervoor hoeft men overigens geen gebruik te maken van SAP PI, omdat de set services ook via Web Services Reliable Messaging (WSRM) kunnen worden gebruikt. Voor alle beheertaken kunnen de standaard SAP webservice tools gebruikt worden.\u00a0Central Contracts kunnen weliswaar nog steeds via iDoc's worden gedistribueerd, maar dan worden in de backend nog steeds de klassieke Outline Agreements aangelegd. De real-time SRM Pricing Check werkt ook alleen met web services. Met behulp van een Badi-implementatie kan een ouder backend echter prima aangesloten worden aan SRM Central Contract Management, zodat een divers systeemlandschap geen beperking hoeft te zijn.<\/p>

\"Compera\"<\/p>

Central Contract in SAP ECC Ehp4 en hoger.<\/strong><\/p>

Het distribueren van een SRM Central Contract resulteert in een Central Contract in ECC. Het grootste verschil met een Outline Agreement is de extra \"schil\" van het Central Contract. Nog steeds worden er Outline Agreements aangelegd, maar deze zijn wel gebundeld in \u00e9\u00e9n Central Contract (mits het \u00e9\u00e9n SRM Central Contract betreft). Standaard is ook het contractnummer identiek aan die van SRM. Bij het afroepen op een Central Contract zijn er nieuwe velden toegevoegd om direct te kunnen koppelen aan het SRM Central Contract en Contract item. Ook kan een contract gezocht worden op basis van het Outline Agreement nummer en\/of het Central Contract nummer.<\/p>

Migratie van Global Outline Agreement naar Central Contracts.<\/strong><\/p>

Bij een upgrade naar SRM 7\/ECC Ehp4 is het noodzakelijk om reeds eerder aangelegde \u00a0en gedistribueerde Global Outline Agreements in SRM en ECC te converteren naar Central Contracts. Dit kan eenvoudig met behulp van een conversierapport in ECC en een upgraderapport in ECC en SRM. Zo worden alle Outline Agreements in ECC omgevormd tot Central Contracts, zonder verlies van geaggregeerde data. Dankzij deze programmatuur ben je dus een stuk flexibeler bij de implementatie van Central Contracts, met name in heterogene landschappen.<\/p>

Weergave Global Outline Agreement<\/strong> in SAP ECC:<\/em><\/p>

\"Compera\"<\/p>

Weergave Central Contract<\/strong> in SAP ECC:<\/em><\/p>

\"Compera\"<\/p>","_et_gb_content_width":"","footnotes":""},"categories":[119],"tags":[],"class_list":["post-3397","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-srm-en"],"_links":{"self":[{"href":"https:\/\/compera.vanvlerken.nl\/en\/wp-json\/wp\/v2\/posts\/3397","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/compera.vanvlerken.nl\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/compera.vanvlerken.nl\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/compera.vanvlerken.nl\/en\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/compera.vanvlerken.nl\/en\/wp-json\/wp\/v2\/comments?post=3397"}],"version-history":[{"count":0,"href":"https:\/\/compera.vanvlerken.nl\/en\/wp-json\/wp\/v2\/posts\/3397\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/compera.vanvlerken.nl\/en\/wp-json\/wp\/v2\/media\/3035"}],"wp:attachment":[{"href":"https:\/\/compera.vanvlerken.nl\/en\/wp-json\/wp\/v2\/media?parent=3397"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/compera.vanvlerken.nl\/en\/wp-json\/wp\/v2\/categories?post=3397"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/compera.vanvlerken.nl\/en\/wp-json\/wp\/v2\/tags?post=3397"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}