SAP Sourcing/CLM Reference Guide Part 2

[Former Member]

In my previous post, I focused on Class References and the different views in the RG. In this post, there will be a more explanations on Workbooks and Mail Template Reference.

WORKBOOKS

There are 2 different sets of workbooks (On-Premise and On-Demand) which can be found in the Reference Guide.

Upgrade Workbooks

In the list of Upgrade Workbooks, the user will find two sets of workbooks for each release:

• Enterprise Upgrade Workbook
• Company Upgrade Workbook

The difference here is that the Enterprise Workbook makes changes on the Enterprise level whereas the Company Workbook only applies changes on the company level (which is one hierarchy level lower). When using these upgrade workbooks, the procedure is to apply the workbook X SP Y patch Z depending on the version the user is coming from e.g. the current release you have upgraded to is SAP Sourcing 9.0 SP 02 and your previous release level was SAP Sourcing 7.0 SP02, then you would choose the following workbooks:

• Enterprise Upgrade Workbook - 7.0.02
• Company Upgrade Workbook - 7.0.02

 

On Demand Workbooks

When deploying your application On-Demand, you would use these workbooks. Depending on which deployment you have licensed you can use the appropriate set of Workbooks e.g.:

• Strategic Sourcing (Sourcing Enterprise and Company)
• Contract Management (CLM Enterprise and Company)
• Strategic Sourcing and Contract Management  (Sourcing and CLM Enterprise and Company)
• Supplier Management (Supplier Management Enterprise and Company)

MAIL TEMPLATE REFERENCE

The mail template reference contains a high degree of details on mail tokens for the different mail types which are being sent to users of SAP Sourcing/CLM. The different mail types is a list of the different mails sorted by Module and Descriptions.

Looking into the different mail types, the user can see the Tokens which are being used for that specific email, as an example every user receives an activation email which typically looks like this. The tokens in this email are:

• Username
• Password
• URL

Based on these specific tokens, this email would be generated to users: