1 2 3 11 Previous Next

SAP Sourcing

152 Posts

Prerequisites:


 

  1. The database is set to support Unicode by having the correct character set specified during installation
  2. The application server’s JVM is set to UTF-8 encoding
  3. The used import files do support and are saved with UTF-8 encoding

 

 

Overview


 

In general multi-language support is very commonplace nowadays yet can pose some difficulty, depending on how the software has been setup and configured.

 

For SAP Sourcing this can happen if, for example, the import files are not properly prepared regarding file encoding.

 

Hence, after the setup that is performed by the System Administrator/Application Responsible, the end user solely has to pay attention to the typical import/export tasks he or she needs to perform.

 

 

Explanation of involved components


 

  • System property “system.csv.export.encoding.use_default_encoding” that can be set on System Manager level
    1.png
  • - User Account setting to switch from text (CSV/TXT) to Excel and vice versa
    2.png
  • - Document Type setting to switch from text (CSV/TXT) to Excel and vice versa
    3.png

 

Explanation and how to approach imports:


 

Once you`ve made sure that the DB supports Unicode (this should by default for a successful SAP Sourcing installation) you can continue to look at the application server. This seems like an area that`s somewhat overlooked as it`ll end up in a very different behaviour for the exact same workflow in the application.

 

Hence have a look at the below two tables depending on the application server`s OS character encoding (Cp1252 due to the fact that I was using a Windows based OS for this example)

 

File imports:

Application server JVM set to UTF-8 encoding:

Upload Preview

Trace content

Data in UI/DB

CSV

not OK

not OK

not OK

TXT

OK

OK

OK

Excel

OK

OK

OK

(all files UTF-8 encoded)


Application server JVM using default OS (Cp1252) encoding:

Upload Preview

Trace content

Data in UI/DB

CSV

not OK

not OK

not OK

TXT

OK

not OK

OK

Excel

not OK

not OK

not OK

(all files UTF-8 encoded)

 

It is important to note that that the Unicode “txt” might work if you are using the application server`s default encoding, but it will get confusing once you get to the trace. The preview and data will be correct, however, the trace might be confusing to users. Hence it is imperative to make sure that the application server is also set to use Unicode (UTF-8) encoding. From the start this will make it easier on the end user as they solely have to pay attention to the import file itself.

 

 

Explanation and how to approach exports:

 

 

If the data is already properly stored in Unicode in the database an export to e.g. an Excel file will be successful in its encoding.

 

To sum this up please have a look at the following table:

 

 

Application server JVM set to UTF-8 encoding:

Export file

CSV*

not OK

TXT**

OK

Excel

OK

* = Uncheck "Export to Excel" in the specific "User Account" settings

** = Set system property "system.csv.export.encoding.use_default_encoding" to "false"

Application server JVM using default OS (Cp1252) encoding:

Export file

CSV*

not OK

TXT**

OK

Excel

OK

* = Uncheck "Export to Excel" in the specific "User Account" settings

** = Set system property "system.csv.export.encoding.use_default_encoding" to "false"

 


Conclusion and recommendation


 

As a conclusion of this article it is highly recommended to make sure that the application server`s JVM is set to use UTF-8 encoding if you intend to use multiple languages.

 

 

On a NW AS this can be done  in the NW`s configtool by setting the Java JVM parameter “Dfile.encoding” with the value “UTF-8”.

 

If this is correctly set, the SAP Sourcing system will show in Setup – System Administration – System Information – Service Registration tab the “Character Set” which then would read UTF-8.

 

You may also read further in SAP KBA 2002598.

 

 

Let me know if you have any questions on this and/or also see my blog at: http://scn.sap.com/blogs/joerg.lippmann for more details on SAP Sourcing.

 

 

 

Regards,

 

Joerg Lippmann

 

 

 

 

FAQs

 

  1. Would you need a specific Sourcing language pack to be installed to support specific uploads?

    A: Actually no. The language pack mainly affects the SAP Sourcing standard page texts in the UI, not the user-entered data.


  2. Would you need to have the system property “system.csv.export.encoding.use_default_encoding” set to support Unicode imports?

    A: No. You can take a Unicode (UTF-8) tab separated txt file and can directly import this into a SAP Sourcing system that has this property set (by default) to “true”.


  3. Can I use Excel to save CSV files with Unicode character encoding?

    A: Not directly. In Excel, you can choose File à Save As… and save the file as type “Unicode Text (*.txt)”. Then rename the file extension from TXT to CSV. Excel will not save certain file types with Unicode encoding.


  4. Why do I get “txt” files everywhere after setting “system.csv.export.encoding.use_default_encoding” to “false”?

    A: This is to make sure that the encoding is properly stored and supported. Even if the SAP Sourcing UI might still in certain places refer to CSV, all files that used to be of type CSV will be exported as TXT.

Over the past 12 months I have received many calls from companies, consulting firms, staffing agencies and recruiters to find SAP Sourcing/CLM resources.  Unfortunately, the majority of these calls focus solely on finding the lowest cost per hour consultant.  The pitfall of this approach is that, for new implementations especially, staffing the cheapest consultant does not result in the lowest total implementation cost for three reasons:


First, rework takes time and money.  If the consultant is using either “trial and error” or “learning on the job” approaches for configuration, development and data loads, it does not take long to exceed the cost of an experienced consultant that will do it correctly the first time.  Experienced consultants are not starting from a blank page and will not waste time on non-valued-added activities. We have been called in to many situations in which an inexperienced consulting team had designed and started implementing a solution that violated several best practices, which led to a waterfall of issues and defects that we were asked to fix. This situation should have been prevented in the first place through the use of expert consultants who have been implementing SAP Sourcing/CLM for many years.


Second, bad design decisions cannot be mitigated easily.  The Blueprinting phase is typically less than 10% of the total cost, but it directly drives the other 90% of the implementation.   The consultant leading this phase must have a deep understanding of the system and have seen the application working in the “real world” to be able to guide the client to the best design, to analyze and mitigate the risk of custom development trade-offs, and to be able to incorporate best in class business processes and compliance.  We at SMA Enterprises (http://www.smaenterprises.us) have conducted over 70 SAP Sourcing / CLM implementations over the last 15 years and none of them have been implemented in exactly the same manner – however, all of them have been successful.  In order to execute these phases effectively, real-world implementation experience is critical from the Blueprinting phase all the way through post-go-live support. 


Lastly, missed go-lives are expensive and potentially embarrassing.  The two issues above can easily lead to extended implementation timelines, resulting in additional budget requests for existing resources,  additional resources, and/or overtime. 


While we all agree that cost is an important measure, it is the total cost, quality of the implementation, and adherence to the timeline that are the most important factors. It may seem counter-intuitive, but hiring the best qualified consultants with deep implementation experience will actually save time and money resulting in the lowest implementation cost.

There are many questions in SCN related to Mass update of Contract Documents fields. This blog will give the insight of how the Contract Document fields can be mass updated through workbook. Hope it will help.

 

Follow the following steps for updating Contract Document fields:


Step1. Download the Workbook Template from Contract Document and Importer

(Setup-->Document Setup-->Agreements-->Contract Data and Document Importer).

Step2. In the workbook Below 3 Fields are mandatory in order to mass update the CDs

 

     1.jpg

UNIQUE_DOC_NAME: Master Agreement’s Unique ID

DOC_DISPLAY_NAME: It is the Display Name of the CD which has to be updated

SKIP_PHASE_TRANSITIONS: This field should be TRUE

Apart from the above fields, other fields which have to be updated are added in the Workbook

For Example, CD phase and some custom fields have to be updated then below is the screenshot of the Workbook. Likewise any field in the Contract Document can be updated.

2.jpg

 

 

Note: If phase of CD is updated via workbook then it will not change the Status at the Master Agreement level.

Sample Workbook Attached.


Step4.Login into the System with Enterprise credentials

 

Step5. Click on Setup-->Document Setup-->Agreements-->Contract Data and Document Importer

3.jpg

Step6. Click on New

4.jpg

Step7. Select “Upload Master Agreement Data” option and click on next

          5.jpg

  • Upload the Workbook and click on next

     6.jpg

 

  • Click on Finish in order to complete the import.

 

 

Any feedback and suggestions are appreciated J

Introduction

 

 

Release 10.0 of SAP Sourcing/CLM – generally available (GA) since 7-Nov-2014 - provides support for additional ECC Item Categories in its SAP ERP Integration as well as new ECC Item Category configuration capabilities within SAP Sourcing/CLM.

 

Please note that ECC Item Categories are called Item Types in SAP Sourcing/CLM.

 

 

Prior Item Category Support in Release 9.0

 

In Release 9.0 of SAP Sourcing/CLM, standard support for Material (Standard <blank>) and Service (D) Item Categories were available.

 

For the Material Item Category, standard support was provided for Material Masters and Free Text Material line items.  For the Service Item Category, standard support was provided for Free Text line items (where the integration supports a single level ECC Service Specification for each SAP Sourcing/CLM Free Text Service line item).

 

 

No other Item Categories/Item Types were available in SAP Sourcing/CLM 9.0.

 

 

New Release 10.0 Item Category Support

 

 

New Item Categories Supported

 

Now the SAP Sourcing/CLM ERP Integration provides standard support for the ECC Item Categories/Sourcing CLM Item Types of Consignment (K), Subcontracting (L), Material Unknown (M), and Material Group (W).  In addition, SAP Sourcing/CLM provides the ability to integrate up to 3 “custom” ECC Item Categories (requires custom PI mappings). 

 

These new ECC Item Categories/Item Types are fully supported on SAP Sourcing/CLM Reports and Imports/Exports.

item1.png

 

Additional Item Category Configuration Capabilities

 

  • Automatic update of ECC Purchase Info Record for Consignment Item Type (Category) line items when published to SAP ERP.  Ref. SAP Note 1703392

 

  • New selected Item Types (Categories) can be activated on the RFx or Master Agreement Document Type level in ERP integrated documents

 

  • Control of Item Type (Category) visibility to Suppliers on Sourcing RFxs

 

  • Ability to change Item Type (Category) in RFx Award

 

 

If you are interested in learning more about these new capabilities, check out the related SAP Help for the new SAP Sourcing/CLM Release 10.0 ERP Integration features on Working with Item Types in SAP Sourcing on http://help.sap.com:

 

item2.png

item3.png

 

 

item4.png

 

item5.png

Introduction

 

 

Release 10.0 of SAP Sourcing/CLM – generally available (GA) since 7-Nov-2014 - provides a new Web Service Framework (WSF) for the development of custom RESTful style web services that leverage the existing SAP Sourcing/CLM Scripting and Query framework.

 

 

Now custom integrations can be more easily developed where SAP Sourcing/CLM can be a provider of RESTful style web services.

 

 

WSF Features

 

 

  • High-Level Summary

 

 

    • SAP Sourcing/CLM can now be a provider of custom inbound REST query/update web services using the existing SAP Sourcing/CLM Explicitly Called Script feature

 

 

    • SAP Sourcing/CLM can now be a provider of custom inbound REST query web services using the existing SAP Sourcing/CLM Report’s Query Definition feature (SAP delivered Query Definitions or custom Query Definitions)

 

 

    • Enablement of these new web services can be done through simple run-time configuration.  There is no requirement to deploy custom .jar files that require shutting down the SAP Sourcing/CLM application server.

 

    • Logging of these custom RESTful web service requests and responses is provided in a new Web Service Request object – that includes detail information about the request as well as both the request and response XML or JSON payload files.  These logging objects are available to view through a System Administration User Interface.  You do not need to get the actual SAP Sourcing/CLM logs to see this information

 

 

    • In addition, an SAP delivered standard RESTful web service is provided for SAP Sourcing/CLM User Account maintenance and queries.  This new web service can be used for User Account synchronization between Identity Management servers and/or NetWeaver servers

 

 

  • Authentication

 

    • Directory Configuration Settings provider authentication support:
      • Basic Authentication (User Name & Password)
        • Local (non-Production only), LDAP, and NetWeaver UME
      • SSO using SAP NetWeaver Assertion Tickets
        • NetWeaver UME

 

 

    • OAuth 1.0a (“3 legged”) RESTful provider authentication support
      • OAuth is an open standard protocol that is secure, flexible, and extensible
      • User Name & Password do not need to be provided to the client consuming application

 

 

  • Security

 

    • New Web Service Security Profiles
      • Web Service User & Web Service Admin standard Security Profiles delivered
      • User permission required to execute an inbound web service
      • Access Right permissions also required for new web service Configuration Objects

 

 

    • Script-based Web Service
      • Document Authorizer Framework IAPIs available for Scripts
      • The “Collaborator model” security is available and is based on the authenticated web service User Session context

 

 

    • Query-based Web Service
      • Report & Query Definition “Access List” security supported

 

 

    • The OAuth protocol is considered very secure

 

 

    • Configurable Throttling Model provided to protect server resources

 

 

  • Reference sample Scripts and Schema Files (.xsd files) provided to support custom development of Script-based web services:

 

    • Sample scripts provided to perform CRUD-like operations (e.g., Create Read, Update…) on CLM Master Agreements, and Souring RFxs and Projects
      • Sample scripts and XML Schema Files (.xsd files) can help “jump start” development of custom integrations
      • For example, custom SRM integration web services could be developed to create an SAP Sourcing Project or RFx from the SRM Sourcing Cockpit or to create an SAP CLM Agreement from an SRM Central Contract from the provided sample scripts and XML Schema Files

 

 

    • XML Schema Files (.xsd files) are used to automatically create XML Request and Response java proxy stub classes for the Explicitly Called Scripts used to provision a web service
      • After the XML Schema file is uploaded and saved via the new Web Service Definition UI, you can immediately view the JavaDocs that are automatically generated at run-time
      • The Request and Response java proxy stub classes are immediately available to the SAP Sourcing/CLM Script environment for Script BeanShell coding

 

 

    • New Scripting IAPIs provided to support Script-based web services development:
      • New “Adapter” IAPIs for unmarshalling/marshaling XML > Java > XML
        • Provided for the complex SAP Sourcing/CLM Data Types
      • New IAPIs to support CRUD (e.g., Create Read, Update…) operations – e.g., to handle checking document access rights on edit and find, clearing and setting document edit information on edit and release, and releasing memory appropriately.

 

 

 

The reference/sample scripts plus the new IAPIs plus the new Web Services Guide for SAP Sourcing 10.0 – now available on SAP Service Marketplace SAP Sourcing/CLM 10.0 On-Premise - can help illustrate a best practices and efficient approach to developing custom script-based web services.  In addition, please note that there is also a new Web Service Cookbook and Troubleshooting Guide 10.0 that should be read if you intend to use the new Web Service Framework script-based or query-based custom web services feature in SAP Sourcing/CLM Release 10.0.

 

You can get both of these documents now at SAP Service Marketplace:

 

 

 

 

samp 1.png

 

samp2.png

samp3.png

 

If you are interested in learning more detail about the above SAP Sourcing/CLM Release 10.0 Web Service Framework new features, please check out the recent SCN webinar presentation slides which have additional content and screen shots at the following link:

 

http://scn.sap.com/docs/DOC-55313

Scenario: - Master Agreements List Based on Status

 

DashBoard Report.jpg

 

When you click on any status in the report or the diagram, then the following report will be displayed


dash board results.jpg


In order to create above dashboard report, please follow as below


1)    Create a Simple query with result fields such as Master agreement ID and Master Agreement Status and with Status as filter since we are displaying the master agreements based on Status


Query Name: - Z_Master Agreement Status Detailed


SELECT <%RESULTS %> FROM <%SCHEMA %>.FCI_CONTRACT T1

WHERE T1.INACTIVE =0 AND T1.STATUS_OBJECT_NAME =?

 

Note: -   Make a note of the parameter name which you have given in the filter ex:-status

Filter.jpg

2)    Create a Report with the above Query Z_Master Agreement Status Detailed.

Report Name: - ZREP_ Master Agreement Status Detailed

3)    Create another Simple Query

                    Query Name: - Z_Master Agreement Status Dashboard

 

SELECT <%RESULTS %> FROM <%SCHEMA %>.FCI_CONTRACT T1

WHERE T1.INACTIVE =0

 

Create three result fields, of which first two are with unique (identical) name as below,

 

a) Master Agreement Status -->  T1.STATUS_OBJECT_NAME || ': (' || (COUNT (DISTINCT T1.UNIQUE_DOC_NAME)) || ')'    Column Type --- URL

The above SQL statement will show the results as below

dash board UI.jpg

When you click on above status then it will be navigated to the results i.e., first query results which can be achieved with below SQL statement


b) Master Agreement Status--> ('/analysis/report?queryGroupName=ZREP_Master Agreement Status Detailed Report&status='||T1.STATUS_OBJECT_NAME)   Column Type --- Internal Page


Blue color indicates --> Internal Name of the first Report (with first Query)

Brown color indicates --> parameter name of the Filter in the first Query


c) Count --> (COUNT (DISTINCT T1.UNIQUE_DOC_NAME))   Column Type --- Number (this has to be hidden for the users)

 

The above Number Type column has to be used in Query under Chart definition Tab as shown below

Chart Defination.jpg


4)    Create a Report with the above Query Z_Master Agreement Status Dashboard.

Report Name: - ZREP_ Master Agreement Status Dashboard

 

5)    Create a desktop channel under below path

      

                                    Setup --> System setup --> Workbench --> Desktop channel


         and add the above report under parameter definitions as shown below and choose the visibility internal or external or both.


Desktop Channel.jpg


6)    Add the desktop channel in your workbench and it will be displayed as below.


DashBoard Report.jpg


Any suggestions are welcome

 

Hope it Helps!

 

Regards,

Raj

Introduction

 

SAP Sourcing/CLM has introduced a feature that allows On-Premise SAP Sourcing/CLM System Administrators to set SAP NetWeaver “Debug Mode” and access the SAP NetWeaver logs directly from the SAP Sourcing/CLM application.  This feature was developed for SAP Sourcing/CLM Release 10.0 and back-ported to SAP Sourcing/CLM Release 9.0 Service Pack 17.

 

In the past, one of the challenges for On-Premise SAP Sourcing/CLM System Administrators has been the need for engaging SAP NetWeaver Basis Administrators when troubleshooting SAP Sourcing/CLM.   An SAP NetWeaver Basis Administrator was required in order to turn on SAP NetWeaver “Debug Mode” when reproducing an SAP Sourcing/CLM problem and also to retrieve the SAP Sourcing/CLM logs from the SAP NetWeaver server.  Retrieving the correct log files for the desired time period has also been a challenge.  Now these activities can be performed just by the On-Premise SAP Sourcing/CLM System Administrator.

 

Enabling this feature

 

 

On-Premise SAP Sourcing/CLM users who have been designated as application System Administrators typically already have the standard delivered “System Administrator” Security Profile assigned to them.  A new Security Profile Access Right has been introduced under the “Super User Rights” group.  Set the new Service Registration NetWeaver Logs View permission to Allow:

access permission.png

Log off and then log on again to refresh your Security Profiles cache.  You should now have access to this new feature.

 

Note: For SAP Sourcing/CLM “system” and “enterprise” administration users, this feature is automatically available and does not require the use of a Security Profile Access Right permission.  Also, if “multi-tenant” mode has been enabled for the SAP Sourcing/CLM implementation, only the “system” administration user will have access to this feature.

 

Setting SAP NetWeaver Debug Mode

 

 

Go to the Setup System Administration tab and click the System Information link:

sys info link.png

The Service Registration Logs tab should now be visible.  Click on the Logs tab and enter Edit mode.   You can now set the SAP NetWeaver Log Level to Debug Mode directly from within SAP Sourcing/CLM:

debug setting.png

Important Notes:

  • Normally ONLY Debug needs to be set for Log Level (Java). Do not set Debug for Log Level (SQL) and Log Level (Startup) unless instructed to do so by SAP Support.
  • Normal Log Level settings for running SAP Sourcing/CLM are:
    • Log Level (Java): Info
    • Log Level (SQL):  Error
    • Log Level (Startup): Error
  • Please don’t forget to turn off Debug Mode when you have completed reproducing a problem!

 

Retrieving SAP NetWeaver Sourcing/CLM Logs

 

 

From the same Service Registration Logs tab (you don’t need to be in Edit mode), set the Start Date and End Date date/time filters to only select log data for the desired time period when the problem occurred and then press the Get Logs button:

logs.png

By clicking the Download link for each file, your default text file editor will launch and you can immediately begin your troubleshooting or save the files so that they can be quickly provided to SAP Sourcing/CLM Support!

 

Important Notes:

  • Debug Mode does not need to be enabled to retrieve the logs.  Logs can be retrieved anytime and for time periods when Debug Mode is not enabled – as long as the log files for the time period are still on the SAP NetWeaver server file system.
  • If Log Level (Java): Debug has been set for the filter time period specified, then the SAP Sourcing/CLM “debug-specific” log entries will be found in the log file that is named with the prefix eso_trc_, e.g., ‘eso_trc_1195119837835452560.log’. Please make sure to also send this file to SAP Support if they have requested that you reproduce a problem in “Debug Mode”.

Ed Dunne and I are pleased to announce the General Availably of SAP Sourcing / CLM release 10.0 On Premise.

 

As of November 7th 2014 we have officially passed all required ramp-up milestones and the release is available for download.

 

We encourage all of our customers to start plans to upgrade to this new release.

 

Release 10.0 offers many exciting features for our customers.  Please refer to the following SCN blogs for more information on the contents of release 10.0.

 

Functional 10 Enhancements:

http://scn.sap.com/docs/DOC-53799

 

Technical 10 Enhancements:

http://scn.sap.com/docs/DOC-55313

 

 

 

Regards,

Anne McClelland and Ed Dunne Product Management

Definition

 

 

What happens if a potential SAP Sourcing user leaves the company? How will the ownership of their documents they worked on be reflected and tackled going forward?

 

Typically SAP Sourcing already does, built-in, provide possibilities to do this. I.e. typically you could either do an Ownership change of a business document via the UI (which certainly would only make sense if but a few documents were to be changed) or alternatively for large scale changes imports can be served with this purpose. SAP note 1092321 (Can you update collaborators on documents) does elaborate on this approach. While working however it may be time-consuming to perform the necessary steps to fill the import template and hence, should this be a recurring task, a more proper UI solution could be thought of.

 

This is where this implementation of a Succession Management Tool (in this context to be understood as a tool handy to change Ownership on business documents within SAP Sourcing) comes in. Note that this is based on this post here (Leavers and joiners policy ideas) if you wanted to investigate the original idea.

 

 

Installation


This implementation is delivered as follows in the attachment called (SMT with UDO - please rename the .txt extension again to .zip as this had to be done to be able to attach this here):

a) a system manager user workbook (as the SMT tool is using the User Defined Master Data 2 object by default)

b) an enterprise manager user workbook that contains the rest of the logic

c) the actual scripts that are being used and are referenced in the "script_definition" tab of the enterprise manager workbook

 

For the "script_definition" tab in the enterprise manager workbook make sure to check/adapt this to your local preferences/settings. Note the business context and the location of the scripts. The scripts need to be in a directory that the application server, where SAP Sourcing is deployed, can access.

 

 

Workflow

 

1) Log in as the Enterprise Manager user and find on the Master Data tab the SMT tool

1.jpg

2) Create new ownership change documents that are being used to trigger the ownership change. Here you can also see the customized columns.

2.jpg

3) The UI is split as follows - the actual logic is to be found under "Scripts" (once in "Edit" mode) whilst the from and to Ownership change is found below. The extension collections do show the Determined Documents for change(s) and also, once updated, will update their respective detail extension collection with the document/template ids that have been changed.

3.jpg

4) Determine the documents by using (in "Edit" mode) the respective "Determine..." scripts

4.jpg

5) This will then look like this

5.jpg

6) Then let`s update (aka change the owner to the from/to values) e.g. the Projects

6.jpg

7) Which yields the ID of the changed document

7.jpg

 

Note: In general if you have access to it I found it advisable to use the Enterprise Manager user for this task. If you do use a normal user (either of the affected / from the from/to fields) you a) may not get any notifications of the ownership change and b) if the security profile settings are not configured you may run into security issues upon ownership change attempt.

 

I hope this idea/implementation can help in managing this particular occurrence with the SAP Sourcing application. As always, with all posts, remember that this is provided "as is" and that as such no responsibility for any damages incurred can be taken. If you are in doubt please contact a SAP Sourcing consultant or similar resource.

 

 

Regards,

 

Joerg Lippmann

SAP currently supports SAP Sourcing/CLM Releases 7.0 and 9.0.  Release 10.0 is in the final stages of Ramp-Up and it is anticipated to be Generally Available within 4 to 6 weeks.

 

We have recently re-evaluated our end of maintenance dates for Release 7.0 and Release 9.0

 

  • The end of maintenance for SAP Sourcing Release 7.0 is and remains to be December 31st, 2017.
  • We have however, decided to extend the end of maintenance of Release 9.0 to December 31st, 2016.  With the timing of Release 10.0 GA, we have realized that our customers need more time to upgrade to it.
  • End of Maintenance for Release 10.0 remains to be December 31st, 2018.

 

SAP still strongly recommends that customers upgrade to the most recent version of SAP Sourcing/CLM regularly.  We hope that, for those customers on Release 9, this increased maintenance support time will help them plan for an upgrade to Release 10 before the end of 2016.   For those customers still on Release 7 we recommend skipping Release 9 and upgrading directly to Release 10.

 

SAP intends to continue providing customer-driven innovation to its On-Premise SAP Sourcing/CLM customers on a regular cadence of every 18-24 months. With that said, Release 11.0 is in the final stages of planning and design and its development cycle will begin soon.   Release 11.0 Ramp-up, GA and EOM dates will be formally announced soon.

 

If you have further questions on the SAP Sourcing/CLM release and maintenance plans please contact me at anne.mcclelland@sap.com.

 

Anne McClelland

Product Management - SAP Sourcing / CLM

Introduction

 

In SAP Sourcing, one common question comes up every now and then which is related to Document Links section (MA, project etc.). For convenience, in this blog I am explaining the technical script involved in solving this issue.

 

What is a Document Links Section?

 

Under Header Section of a Business Document, we can see the Document Links Sections where the user can add another Business Document in relation to the current one.

 

DocLinks.png

While adding another Business Document, the following data needs to be populated.

 

relation.png

 

Technical Scenario

 

Generally, based on some business requirement, we would require linking a previous Project (Business Document) to the current one. This can be achieved via scripting which is explained in this blog.

 

//Required imports

 

import com.sap.odp.api.doccommon.masterdata.DocumentLinkDefinitionIBeanHomeIfc;

import com.sap.odp.api.ibean.IBeanHomeLocator;

import com.sap.eso.api.projects.ProjectIBeanHomeIfc;

 

// Creating Document Links Home through DocumentLinkDefinitionIBeanHomeIfc

docLinkHome=IBeanHomeLocator.lookup(session,DocumentLinkDefinitionIBeanHomeIfc.sHOME_NAME);

 

// For instance, let us assume that the document is project

// Creating Project  Home

 

projHome=IBeanHomeLocator.lookup(session,ProjectIBeanHomeIfc.sHOME_NAME);

 

// Finding the Project which needs to be added in Document Links section

 

projBean = projHome.findByUniqueDocName("PROCAT-001--2014");

 

// Find the Relationship with which the Project  should get added. Refer FCI-DocLinkDefList query to view all the relations present in the system.

 

documentLinkDef = docLinkHome.findUnique("FCI-PROJECT PREVIOUS");

 

// A line is added with empty fields in Document Links section

newDocumentLink = doc. getDocumentLinkList().create();

 

// Setting the Type of document which needs to be added (project, RFx, Auction etc.)

 

newDocumentLink.linkDefinitionType = new DocLinkDefinitionTypeEnumType(1);

 

// Setting the Relationship of the document which needs to be added (Previous Project, Future Project etc.)

 

newDocumentLink.linkDefinitionObjRef = documentLinkDef.objectReference;

 

// Setting the Object Reference of the document which needs to be added

 

newDocumentLink.LinkDocObjRef = projBean.objectReference;

 

//A Document is added in the Document Links Section

 

doc. getDocumentLinkList().add(newDocumentLink);

 

This Script can be used with any Document Life cycle event or toolbar based on Business requirement.

 

Regards,

Vignesh

Introduction

 

SAP Sourcing/CLM can use either the Microsoft .NET-based WordService or the JAVA-based SAP Sourcing DOCX Generation Service to generate structured contract documents using clause documents, collection variable documents, and contract document templates.

 

SAP Sourcing DOCX Generation

 

The Microsoft .NET-based WordService requires setup of an additional Windows server. Due to this overhead and additional TCO, versions of SAP Sourcing 7.0 SP5/9.0 SP11/10.0 or higher now also support the SAP Sourcing DOCX Generation Service, which is WordService based on JAVA technology. The SAP Sourcing DOCX Generation Service does not require an additional Windows server. As this is lower TCO, we recommend switching to the SAP Sourcing DOCX Generation service. For more information on the JAVA-based generation service, see the following link:

 

The New SAP Sourcing & CLM DOCX Generation service

 

Microsoft .NET-based Word Service

 

The Microsoft .NET-based WordService requires setup of an additional Windows server. It uses MS Word on the Windows server to perform operations on the clause documents and generate a structured contract document.

 

Follow these steps to install the Microsoft .NET-based WordService:

 

1. Verify that you meet the prerequisites for the installation of .Net WordService. See the checklist of prerequisites:

Prerequisites to configure .Net based contract Generation service

 

2. Create an “Office Automation User” user account. This user should perform the operations in MS Word on the Windows machine for the generation of contract documents. We recommend not using this user for any other purpose, as that might disrupt the configuration, resulting in the failure of the contract generation service.

Create Office Automation User

 

3. Install the WordService. For details, see: Install WordService

 

4. Configure the WordService. For details, including screenshots, see:

Configure IIS for WordService

 

5. When the installation is complete, check the whether the WordService is working as desired by following these steps: Verify that Contract Generation WordService is working.

 

6. If the WordService is not working as desired, refer to the troubleshooting techniques here:

General Contract Generation Checklist for CLM Versions 9.x and Below

Please note that this topic is also covered by the available KBA 1996605 (then application level issues) (SAP Service Marketplace access required)

 

Prerequisite:

 

SAP Sourcing login URLs can be constructed as follows:

[protocol]://[hostname]:[port]/[context]/[login type]/[login path]

 

Process flow for buyside and sellside logins:

 

1. Install the Language Pack in question following the official SAP Sourcing documentation

 

2. Open the SAP Sourcing Login page in question (buyside, sellside)

 

3. Change the language in the dropdown ("Logon Screen Language") to the language in question and note the changing URL in the browser

 

4. Copy this URL and find the language pack ID for the selected langage pack at the end of said URL

 

5. Use this URL as a favorite or in any other manner to pre-default the SAP Sourcing Login Page language for the buyside and sellside logins

 

As such a buyside URL with a pre-defaulted language pack preference would look like:
[protocol]://[hostname]:[port]/[context]/fsbuyer/portal/login?languagepack=-2147481840:50


Buyside Login Page LP default.jpg

 

A sellside URL with a pre-defaulted language pack would look ike:
[protocol]://[hostname]:[port]/[context]/fsvendor/vendordesktop/login?languagepack=-2147481840:50

Sellside Login Page LP default.jpg

 

NOTE: This might not work in SSO scenarios as the login page might not stem from the actual SAP Sourcing application.

 

Process flow for the Supplier self-registration page:

 

1. Install the Language Pack in question following the official SAP Sourcing documentation


2. Note the "ISO Language" value of the language pack in question from the SAP Sourcing buyside (or enterprise user) login via Setup - System Setup - User Interface - Language Packs

Language Pack ISO.jpg


3. Open the SAP Sourcing Supplier self-registration page in question (if using multiple UI`s see also KBA 1995822 if in doubt how to call it)

 

4. Use the given URL and append the following: ?language=da&country=da whereas "da" is the ISO Language value of the language pack in question.

 

5. Use this URL as a favorite or in any other manner to pre-default the SAP Sourcing Supplier self-registration language

 

A Supplier self-registration page with a pre-defaulted language pack would look like:
[protocol]://[hostname]:[port]/[context]/fsguestvendor/vendordesktop/register?language=da&country=da

Supplier self reg UI default.jpg

 

If using an alternate Supplier UI with a pre-defaulted language pack this would then look like:
[protocol]://[hostname]:[port]/[context]/fsguestvendor/vendordesktop/register?language=da&country=da&ui=ui2

Supplier self reg UI2 default.jpg

The SAP Sourcing/CLM Customer Partner survey invitation was emailed out on Friday, June 6th.  This is your chance to influence the contents of the next release of SAP Sourcing/CLM.

 

The deadline for survey submissions has been extended to Friday, August 1st.

 

A separate survey invitation specifically for internal SAP Sourcing/CLM consultants/support network etc. was also sent out.

 

If you did not receive the survey email and would like to participate please notify me at anne.mcclelland@sap.com.

 

Anne McClelland

Product Management - SAP Sourcing/CLM

Please note that this topic is also covered by the available KBA 1997275 (then application level issues) (SAP Service Marketplace access required)

 

  1. Logging Categories (eso.<n>.log) – do not need be altered at any time

    1 Logging Categories.jpg
  2. Tracing Locations (eso.<n>.trc) – default settings (normal settings)

    2 Tracing Locations - default.jpg
  3. Tracing Locations (eso.<n>.trc) – SAP Sourcing (application) debug logs

    3 Tracing Locations - application debug.jpg
  4. Tracing Locations (eso.<n>.trc) – SAP Sourcing SQL debug logs

    4 Tracing Locations - SQL debug.jpg
  5. Tracing Locations (startup.<n>.trc) – SAP Sourcing startup debug logs

    5 Tracing Locations - startup debug.jpg

Actions

Filter Blog

By author:
By date:
By tag: