1 2 3 10 Previous Next

SAP Sourcing

138 Posts

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

Please note that this topic is also covered by the available KBA 1997890 (SAP Service Marketplace access required)

 

Environment

 

 

SAP Sourcing 7.0 and SAP Contract Lifecycle Management 7.0
SAP Sourcing and SAP Contract Lifecycle Management 9.0

 

and WordService Installation performed on a supported Windows OS

 

 

Reproducing the Issue

  1. Set Log Severity
  2. Reproduce Issue
  3. Reset Log Severity
  4. Acquire Logs
  5. Validate Logs
  6. Provide validated Logs to Support

 

SAP Sourcing Contract Generation issues.jpg

 

Resolution

 

PREREQUISITES:

Make sure to have the appropriate access rights to the involved applications/functions:

 

  • OS level access / contact your local IT and/or system administrator

 

ESSENTIAL FILES to be provided to SAP Sourcing Support:

 

  • log_<date>.log and log_<date>.trc files contained within the directory given during the installation of the WordService

 

INSTRUCTIONS:

  1. Set Log Severity

    This step is only necessary if you are being asked to provide the Contract Generation Logs in "debug" severity. If this is the case then:

    a) Find the file located at: [www root]\WordService\Web.config and open it in a text editor

    b) Find the section "<appSettings>" and look for the string "<add key = “logLevel” value=”info”/>"

    NOTE: If you did not revert previous settings it might not read "info" for the value

    c) Change the value to "debug" and save.

    d) Restart the WordService.

    Example of a debug configured Web.config:

    Untitled 3.jpg
  2. Reproduce Issue
  3. Reset Log Severity

    Revert the changes made in step 1 by modifying the Web.config to its previous original value.
  4. Acquire Logs

    Navigate to the directory defined during the installation of the WordService.

    Example at
    c:\fci:

    Untitled 1.jpg

    and copy those files which are needed (see next step).
  5. Validate Logs

    NOTE: DEBUG entries will only be found in the respective log_<date>.log files. Nonetheless the log_<date>.trc files of the same timeframe are required.

    a) Open the files to see if the desired severity logging is there (you would see DEBUG, the screenshot only shows INFO and ERROR entries).
    Contract Generation log example.jpg

    b) Make sure that the timeframe is matching with the reproduction.
  6. Provide validated Logs to Support

    Once you have identified the relevant log files do provide them to SAP Sourcing Support

Calling all workflow gurus for SAP Sourcing / SAP CLM !We have some good news for you. The news is also good for the folks who were a bit gun-shy with creating and maintaining workflows in SAP Sourcing / SAP CLM.

 

With SAP Sourcing / SAP CLM version 9 SP 16+ (and, of course, with our upcoming release SAP Sourcing / SAP CLM 10.0), we will be introducing a brand new and extremely intuitive, easy to use, highly functional, wizard driven visual workflow editor. Ah OK! I will lay off the adjectives and get down to brass tacks. But yes, we are excited about this long-standing request from a number of our customers, and consultants.

 

I will not go into the capabilities and functionality of the Workflow in SAP Sourcing / SAP CLM, which has been covered extensively and synopsized wonderfully in this webcast (recording, and presentation), but focus more on the creation of the Workflow, and the features being introduced.

 

Throw away those old 3rd-party workflow editors

 

Let’s step back a little and understand our decision to bring this capability into the application. Well,

  • The 3rd-party tools and editors (visual or text based), which can construct the workflow process definition in a format as supported by SAP Sourcing / SAP CLM, are becoming difficult to find. Additional licensing issues (LGPL, GPL, etc.) associated with these tools which complicate the matter further.
  • Using 3rd-party tools meant that after creating the workflow process, a file needed to be saved and then imported into the SAP Sourcing / SAP CLM Workflow definition interface
  • The visual tools our customers and consultants were using were pretty clunky and required a number of extension attributes to be added, and/or had some attributes that were not mandatory and just plain confusing
  • For the type of functionality that a solution like SAP Sourcing / SAP CLM provides, adhering to the open industry standard XPDL or BPMN is a bit more cumbersome than necessary

 

So is it as easy as you claim?


You can be the judge.

Setting up a workflow process, is as easy as 1, 2, 3, and you are done.


Step 1 - Define the Workflow Process

 

The Workflow definition task has not changed, except for one very important and useful addition, allowing the associated workflow process to be created and saved in Draft status before publishing.

 

Figure 1.png

 

Once the details for the workflow have been defined, and the option to "Add New Version" has been selected, you will now be presented with 4 options to help give your workflow process definition a great starting point, and doing most of the initial heavy lifting for you. The 4 choices are:

  1. Use our automated workflow process generator. All you have to do is provide the number of approval steps you would like, and we will do the rest. One limitation: you cannot define more than 20 approval steps, but if you need more than 20 approval steps, then get in touch with us so that we can look at the use case, and maybe provide some useful alternatives. This is the best option for starting a new workflow process definition.As a bonus, with this option, you can now also define a default Prescript and a default Postscript to be used in the entire workflow process. The scripts defined as default, will be associated with the generated appropriate steps in the workflow process
  2. Use the last published workflow process definition. If you have created versions, and have perhaps used a version of the workflow process, and then realized that a small tweak needs to be made to make the process compliant with the expectations of the users of the system, then this is the option for you.
  3. Use the last published version of another workflow. Well, you have done it before, and now it’s time to create a new workflow, but, why reinvent the wheel? Use the working published workflow process that exists and works perfectly.
  4. Use an existing workflow schema file. We would like you to use our new visual workflow process flow editor, but of course there is always a need to support and allow workflow process schema files (.xpdl or .sswp) to be imported and used.

 

Figure 2.png

Step 2 - Build the Workflow Process

Here you define all the details of the workflow process in one screen, by populating an optimized and necessary list of fields only, with most fields already populated with default values. We have also ensured that all the approval steps are given default names, and if you have used the default script population option, then hey, presto, you are well on your way, and can finish the whole definition really very quickly.

 

Of course, all the names and labels can be easily changed, and additionally, the visual workflow works almost like any other visual tool, with clickable approval steps and icons.

 

 

 

Defining additional approval steps or deleting approval steps is easy with the clear buttons, and of course you select where the additional approval steps should be placed.

Figure 3.png

 

Step 3 - Add the Scripts please

 

Now that the stage has been set, all that is required is to start adding the scripts to suit your specific scenarios and processes for each of the approval steps. Simply click on the icons that are provided for defining Prescripts, Precancel, and Postscripts for each approval step and you will be able to enter your script or copy and paste from your favorite editor. The icons are also colored differently depending on whether a script has been defined for an approval step or not.

 

A capability to define a Global Precancel script is also provided

 

And that’s it .......

Figure 4.png

 

SSWP!?! What is this SSWP?

 

One new aspect that we are introducing is a file format that is truly SAP Sourcing. All the workflow processes defined or modified will now be available in the .sswp format. SSWP stands for SAP Sourcing Workflow Process, is still an XML file, and just like the user experience is optimized for the SAP Sourcing / SAP CLM workflow capabilities.

 

Voila! Workflow process definition in a box.

 

There you have it

 

But wait, there's more "Help" on the way. The Help section for workflow definition has been comprehensively updated to include details on all the features and functionality for our upcoming Release 10 (for all the features of Release 10, please refer to this blog). For Release 9, we will be updating our Scripting and Workflow guide, which will be available on Service Marketplace.

 

If there is any more information that you need, please feel free to get in touch.

Integration of SAP Sourcing with SAP ERP allows for seamless transactions with replication of master data and transfer of  Business Document's between the two systems. The following document outlines the Good Business Practices that can be employed while considering the integration during the planning phase of the Implementation cycle.

 

Standard Solution –Publishing Process (ES/PI/ERP):

     The standard solution is designed to allow the publishing of Awards or Master Agreements as Purchase Orders and Outline Agreements to the ERP system. This is a synchronous process; meaning that the end user will have to wait after clicking the ‘Publish to ERP’ for a valid response before initiating any other action in the User Interface.  Following is the sequence of events that occur during the Publish process:

  • Validate the Business Document in SAP Sourcing
  • Generate the XML payload that will be sent to the SAP PI system
    1. The Integrated Document Configuration is considered to determine the content of the XML payload
  • Connect to the SAP PI system and submit the XML payload
  • In SAP PI, the XML payload is mapped to the Function ‘BBP_ES_UPDATE’
  • SAP PI then invokes the call to SAP ERP system with the transformed Payload
  • In the SAP ERP system, the Business Document is validated for completeness and consistency and then created
    1. At this step, the SAP ERP configuration is read and interpreted
  • The SAP ERP system, upon successfully creating the document, will return the Document Number that was generated as well as any success and other messages (warning and error)
  • The return call from SAP ERP is mapped back in SAP PI to the SAP Sourcing call and the values returned to SAP Sourcing
  • In SAP Sourcing, the process completes upon the following occurring:
    1. Updating the document number from SAP ERP on the header and line item
    2. In the case of an error – a pop-up message displaying the reason for the error

NOTE: In the case of success, a pop-up window is not displayed.  You can reference the document number on the Header of the Business Document in SAP Sourcing as confirmation of a successful publish.

As can be seen above, the entire process is ‘Synchronous‘ by design to provide immediate feedback to the end user with regards to the completeness of the transaction.

It has been found that for most business needs this standard behavior will enable good end user response times and user interaction.

 

Implications due to Extending/enhancing the standard process:

When the standard solution does not support the required Business demands, it is necessary to extend the standard functionality which procedurally involves:

  • Extension fields or elements on the business documents
  • Scripts to support the validations or other business needs
  • SAP PI Mapping related changes (to message types and mapping) to support the new fields
  • Enhancements  to the ‘receiving’ function modules (BBP_ES_OA_UPDATE, BBP_ES_PO_CREATE) to support these new fields

Depending on the complexity of such enhancements, the behavior of the standard solution will be impacted and will result in a differing end user experience. The effect will be more pronounced if enhancements or extensive scripting is used for validations etc. at the line item level or a sub-Object level that has collections.

 

 

Performance of the standard system under normal designed loads:

With Integration and also as an outcome of the synchronous nature of the calls to SAP ERP, the end user experience and thereby the performance of the system will be determined by several parameters:

  • Sizing of the system to support the concurrent users and the business use cases
  • Number of users currently logged in and actions being performed
  • Batch jobs that may be running
  • Current SAP Sourcing system load in terms of the memory consumption
  • If detailed Logging or Tracing is enabled
  • Network latency (since data needs to be sent to SAP PI and SAP ERP systems)
  • SAP PI system load
  • SAP ERP system load
  • Size of the Business Document – not necessarily limited to the number of line items but including all collections and sub collections
  • .. several others

 

The performance could be different under differing conditions since it will not always  be able to predict what the load on the SAP PI and SAP ERP systems are even though SAP Sourcing could have been sized and managed well.

As an example, under standard behavior and in the SAP test landscape with few users or just the performance test user logged in and with nothing but a very basic document containing the bare line items, the following metrics have been observed relating to the publishing of Business Documents from SAP Sourcing to SAP ERP.

 

1. Publish Master Agreements to SAP ERP

Number of Line ItemsMA Publish to ERP:  (secs) *time as derived from log files
502.446
10024.821
25062.201
500138.56
1000322.725

 

 

2. Publish RFX Award to SAP ERP

Number of Line ItemsPublish RFX Award to ERP:  (secs) *time as derived from log files
507.944
10014.651
25037.951
50083.428
1000218.768

 

As is observed from the times above, the publish times will increase with the number of line items (considering this alone and no other variations). As can be noticed,the end user will experience lengthy wait times as we reach the 1000 line item mark. This not only impacts the user trying to publish the document to SAP ERP but all other users logged into the system.

 

Best Business Practice suggestion:

     Because the Sourcing to ERP integration scenario uses synchronous HTTP calls to transfer data, and all HTTP requests are expected to respond within reasonable network limits (i.e. ~ 5 minutes) to ensure a real-time, responsive user experience for all users on that network – it is not recommended to attempt publishing more than ~1000 line items at any one time. We expect that significantly raising or removing such limits as a long-term solution will have a negative impact on the behavior of the network as a whole - including the applications and users within it.

 

Alternative ideas to publish large number of line items:

     There have been various approaches suggested depending on the business needs but a common approach proposed and used by many customers at this time is to split the business document into multiple documents with fewer line items. This way the end user experience while navigating the document in sourcing or even while publishing will be within acceptable norms.

     One approach might be to publish a “parent” agreement with no line items that serves as the “umbrella” agreement with “child” agreements for all of the line items ensuring that each child agreement included no more than ~1000 line items.  This would enable you to manage the “child” agreements together under the “parent” but ensure that no “child” has more than ~1000 line items.  There may be some logical groupings that would allow you to group the line items onto a “child” agreement by, for example:

  • Product
  • Category
  • Organizational Unit
  • Geography
  • Plant

 

In the case that the need arises to publish documents larger than the suggested line items (~1000), some of the symptoms the system will exhibit are:

  • Frequent and inconsistent timeouts experienced by the user publishing the document to ERP.
  • In some situations inconsistent transaction states due to the timeout (meaning the document may have been created in ERP but due to the timeout occurring in SAP Sourcing, the document references will not be updated in SAP Sourcing)

Both of the above issues can be addressed by changing the timeout parameters (on some but most likely) on all systems (SAP Netweaver, SAP Sourcing, SAP PI, SAP ERP).

 

Timeout parameters of interest:

SAP Netweaver: (Refer to NW documentation)

  • icm/conn_timeout
  • icm/keep_alive_timeout
  • icm/server_port<_n>/PROCTIMEOUT

 

SAP Sourcing:  (Refer to the SAP sourcing configuration guide for additional details)

  • upp.metering.login_inactivity_timeout
  • upp.metering.cleanup_interval
  • transactionTimeout.millis

SAP PI System: ( Refer to the PI documentation for the details)

  • HTTP_TIMEOUT
  • xiadapter.inbound.timeout.default

SAP ERP:

  • rdisp/mas_wprun_time


Note:  Increasing the timeouts will lead to successful publish of documents to ERP but will not guarantee good end user experience for all the users logged into SAPSourcing (i.e.,the users may experience slow response times as much of the system resources would be locked up processing the Publish event).

How to configure a new Master Agreement Type in SAP Sourcing/CLM 7.0?

Hi,

 

In this blog, I would like to show how to configure numbering table and master agreement type.

 

Configure Numbering table:

Menu path: Set Up ->Master Data (tab) ->Numbering Table Definition.

1.JPG

Click on ‘Numbering Table Definition’, and then click ‘New’ .Then below screen will appear.

2.JPG

 

 

I entered in the above screen as below.

*Name:  Numbering for DLMA (Distribution Logistics Master Agreement)

Table ID: ‘MA-DL’.

Prefix:  DLMA-

Prefix:  -<%YYYY%>

*Sequence Number Width: 6

Ticked Sequence Number Padded

*Start Number: 1

*Number incremented by: 1

Finally click ‘Save’ button and ‘Done’ button.

Now we have configured numbering table for DLMA (Distribution Logistics Master Agreement type).

************************************************************************************

Configure Master Agreement Types:

Here I am going to create a new type for DLMA (Distribution Logistics Master Agreement type)

Menu Path: Set up->Document Set up

3.JPG

Just click ‘Master Agreement Types’, and then click ‘New’ button.

Now I entered data as blow in the below screen (Type Tab).

4.JPG

If you tick ‘Integrated Type, then Integration Details tab you see as in the above screen. Otherwise you cannot see ‘Integration Details Tab’.

*Name        : D and L Master Agreement

Description: Give your description (I gave Master Agreement type for Distribution and Logistics)

*Order : 400(system gives this number)

Numbering table: select ‘Numbering for DLMA’ as below screen.

 

5.JPG

Tick in the below screen (Features,Rules,Defaults and Notification )  according to your requirements:

 

6.JPG

7.JPG

8.JPG

Finally click ‘Save’ button and ‘Done’ button.

Now we have configured Distribution Logistics Master Agreement type.

Now check you master agreement type just now you created (D and L Master Agreement).

Go to  this  path : Set up->Document Set up->Master Agreement types.

9.JPG

 

With Regards,

Jaheer,Cristal

Introduction

In “Master Agreement Types Explained – Part 1”, an overview of Master Agreement Types was provided.  In this blog, each configuration item on a Master Agreement Type is explained.

 

Configuration of Master Agreement Types

As discussed in Part 1, there are five (5) sections that need to be reviewed and configured when defining a Master Agreement Type.  The following paragraphs provide an explanation of each field in each of the five sections.

 

General Section - The General section is used to establish some key information about the Master Agreement Type such as the Name and Description as well as the Order in which it will be displayed to the user.  The following items should be reviewed and setup according to your requirements:

 

Item

Item Description

Inactive

This is a checkbox that, if checked, indicates that a Master Agreement Type is no longer available for use.  When this checkbox is checked, the Master Agreement Type will not show up in the list of Master Agreement Types to pick from when the user does a “Create Master Agreement” or “Create Master Agreement Template”.

Integrated System Type

This field will only be displayed if the integration to SAP ERP or SRM is enabled.  If you are using the integration, you can select the type of integration that is related to the Master Agreement Type.  When you choose a particular type of integration (SAP ERP or SRM), a new tab – Integration Details - on the Master Agreement Type will be displayed.

Name

This is the name of the Master Agreement Type – for example, Master Services Agreement.  This is the name that is displayed when the user does a Create Master Agreement” or “Create Master Agreement Template”.  This field is required and has a maximum length of 40 characters.

Description

This field is used to describe the Master Agreement Type.  It is not a required field.  It has a maximum length of 256 characters.

Order

The number value used in this field determines in which order a particular Master Agreement Type will be displayed to the user.  For example, if there are five Master Agreement Types defined and the values used in this field are 10, 20, 30, 40, and 50, the Master Agreement Type with an Order value of 10 will be the first in the list as it is displayed to the user.  It is recommended that you leave some spaces between the numbers used for the Order value.  By leaving some spaces, if you need to create a new Master Agreement Type, you will be able to insert it in the order in which you want it displayed.  This is a required field. 

Numbering Table

If you want to use a specific Numbering Table for a particular Master Agreement Type, you must associate the desired Numbering Table with the Master Agreement Type.  The Numbering Table must first be defined in the Master Data section of Setup.  The Numbering Table is used to create a unique id for each agreement of that type. 

If you do not associate a specific Numbering Table with a Master Agreement Type, the system will automatically use the default Numbering Table for Master Agreement Types.

 

 

Features Section - The Features Section is used to determine which tabs - such as Audits and Schedules - will be used as well as which features - such as Discussions and Attachments - will be enabled.  The following tables discusses each of the configuration items in this section:

 

Item

Item Description

Discussions

The Discussions feature allows you to have discussions related to each Master Agreement with both your internal stakeholders and your suppliers.  The Discussions are stored with Master Agreement. Depending upon other configuration options available to you, users can find their Discussion messages in the Discussion channel on their Workbench page or they can receive email notifications that a Discussion message has been sent to them.  By checking this box, the Discussions feature will be available to users in the toolbar of any Master Agreements of that type.  Most often, this feature is enabled.

Chat

Chat allows you to “instant message” with another user that is logged into the system at the same time you are and reviewing the same Master Agreement.  Chat messages are also stored with the Master Agreement and are accessible from the Chat feature in the toolbar if it is enabled.  Most often, this feature is not used on Master Agreements.

Attachments

By checking the Attachments box, you will enable the Attachments button to be displayed to users in the toolbar of Master Agreements of that type.  This feature allows you to upload file attachments that are related to a particular Master Agreement.  This allows you to store all related documentation with the Master Agreement in a single place.  This feature is almost always enabled.

Accounting

By checking this box, you will enable the Accounting tab on Master Agreements of this type.  The Accounting tab allows you to associate predefined accounting entities (such as cost centers and general ledger accounts) at the header level of the Master Agreement and estimate benefit related to those accounting entities. The Accounting tab is most often not used.  It can be repurposed; however, with the additional tabs that can be configured to meet specific needs, it is easier to use one of the additional tabs for custom requirements that you might have.  

Require Product Category

The Product Category (often relabeled as “Material Group”) can be made a required field on all Master Agreements of that type by checking this box.  This is a that is commonly used in the standard reports and is one that organizations use to report on frequently to determine how much activity they have for a particular Product Category.  This field is often enabled for that reason.

Allow Duplication

 

Savings Metrics

 

Formulas

 

Line Item Specifications

 

Supplier-Entered Attributes

 

Master Agreement

Agreements

 

Audits

 

Schedules

 

Terms

 

Line Items

 

Performance Metrics

 

Tab 1

 

Tab 2

 

Tab 3

 

Tab 4

 

Tab 5

 

Hierarchy

 

Enforce Date Range

 

Subagreement

Audits

 

Schedules

 

Terms

 

Line Items

 

Performance Metrics

 

Tab 1

 

Tab 2

 

Tab 3

 

Tab 4

 

Tab 5

 

Introduction

 

Master Agreement Types are a foundational structure in Contract Lifecycle Management which:

  • Determine the features and functions that will be available on an actual Master Agreement or a Master Agreement Template
  • Give you the ability to define a Numbering Table to be used with a particular Master Agreement Type
  • Enable you to do Page Customizations to determine how the pages will be configured for a specific Master Agreement Type
  • Allow you to write Scripts to drive specific logic that applies to a particular Master Agreement Type
  • Enable you to query agreements in the system by Master Agreement Type

 

Before you can create a Master Agreement or a Master Agreement Template, you must define at least one Master Agreement Type in Setup.

 

Generally, Master Agreement Types will be defined in the system according to your current business usage and the types of agreements that you intend to store in the system.  Examples of Master Agreements Types that are commonly defined include:

  • Master Goods Agreement
  • Master Services Agreement
  • Lease Agreement
  • Statement of Work

Although you must have at least one Master Agreement Type defined in the system, the number of actual Master Agreement Types that are defined should reflect your business needs.

 

Who can Define Master Agreement Types in the System?

 

Generally, Master Agreement Types are a business concept and should be defined according to the business needs.  In order to define Master Agreement Types, a user must have the appropriate Security Profile.  There are different approaches that organizations take in assigning the necessary permissions to users.

 

For example, permissions might be assigned to:

  • A “Super User” who both understands the business needs and the necessary system configuration
  • A team including an IT System Administrator and a knowledgeable Business User

Because Master Agreement Types should reflect the needs of the business, key business users should always be involved in their definition.

 

Configuration of Master Agreement Types

 

When defining a new Master Agreement Type, there are five (5) sections that need to be reviewed and configured:

 

MATYPEIMAGE1.png

 

There is also a sixth section on the Master Agreement Type that does not require configuration:

MATYPEIMAGE3.png

 

The Change History section also captures the user’s name that created the specific Master Agreement Type as well as the date and time when they created it.  It also captures the user’s name that last changed the Master Agreement Type and, again, the date and time when they changed it.

 

In another blog, Master Agreement Types Explained – Part 2, each configuration item in a Master Agreement Type will be further explained.

When a Master agreement is published to create an Outline agreement or an Rfx/Award to create a Purchase Order from SAP Sourcing, there is a simple way to search and identify such documents in ECC. The following guide points to the way of searching for the documents.

 

In the ECC system, invoke the transaction "BBP_ES_SEARCH", here we have the option to either search by the Master Agreements or the RFx Number from SAP Sourcing.

 

Step 1. Identify the Master agreement or the RFx ID. in SAP Sourcing

ESMA.jpg

Step 2.  In the ECC system invoke the transaction BPP_ES_SEARCH. Enter the Master Agreement /Rfx ID identified in the previous step.

BBP_SEARCH.jpg

 

Step 3. When the transaction is executed with the Master agreement Id specified it will list the Outline agreeement and line items associated with the Master   agreeement.

SRCH_RES.jpg

 

As seen from the output the search, we notice that it not only pulls up the Master agreement data (header) but also the line items.

 

The procedure is the same for the Rfx document.

Overvew.png

 

Technical detials:

The references to the Master agreements coming from SAP sourcing are saved in the configured TextId's at header and Item level. The configuration needs to be performed both on the SAP sourcing and the ECC system to actvate this and make this possible. The transaction BBP_ES_SEARCH will then use this saved references in the text elements to list the referenced contracts or Purchase orders.

Introduction

 

The Expected Value Column that is returned in the results set of some of the Master Agreement List Queries is a calculated field based on metrics that are defined in the Savings Metrics tab of either a Master Agreement or Sub-Agreement.  The metrics are designed to track the expected value and the savings that will be realized as a result of a particular Agreement.  The Expected Value is entered for each of the metrics defined on an Agreement.  The value that is returned in the Expected Value Column is a total of all of the Expected Values that have been entered for each of the metrics defined in the Savings tab.

 

Note:  The Savings tab will only appear in either the Master Agreement or the Sub-Agreement but not in both if the Savings Metrics flag is enabled.  If Sub-Agreements are enabled, then the Savings tab will appear only on Sub-Agreements and not on Master Agreements.  This is defined on the Master Agreement Type in Setup.  

 

Savings Metrics Tab

You will find the Savings Metrics feature In the Features section of the Master Agreement Type definition as seen below:

 

Image 1.png

 

 

If you enable this feature on the type, the Savings tab will be displayed in the Agreement – in the example below, it is displayed in the Sub-Agreement:

 

Savings Tab

 

Image 2.png

 

In order to begin tracking Expected Value and related savings, the Savings Metrics for a specific time period must be defined as seen in the example above.  In this case, there are three time periods for which savings metrics have been defined.

 

Time Period 1

 

Image 3.png

 

Time Period 2

 

Image 4.png

 

Time Period 3

 

Image 5.png

 

Expected Value – Sub-Agreements

 

The total Expected Value that is displayed for this single Sub-Agreement in the results set of the query is the sum of the Expected Values entered for the three time periods in the Savings tab:

 

Image 6.png

 

Expected Value – Master Agreements

 

The total Expected Value that is displayed for this Master Agreement in the results set of the query is the sum of the Expected Values entered for all the time periods for all of the Sub-Agreements in the Savings tab:

 

Image 7.png

 

Summary

 

In summary, this column is only one component of measuring value and savings related to Agreements; however, it does rely on the enabling the Savings Metrics feature in the Master Agreement Type definition and populating relevant metrics on the Agreements themselves.

In Sourcing 7.0 SAP introduced an useful feature that allows a supplier registration to route through an approval workflow.  When a new supplier registers via the supplier registration page, the registration request can be routed to one or more approvers or approver groups before the supplier is added to the supplier master in Sourcing.

 

Supplier workflow is very similar to project and contract approval workflow. When a supplier registration is submitted the approver will receive an email notifying them about the current approval. Upon logging into the system, the approver can either use the “My Supplier Workflow Activities” channel to access the current approvals or go to the supplier record to approve. In this short blog I will cover the configurations needed to enable this. It is assumed that the readers are somewhat familiar with the general workflow configurations.

 

Step 1 – Supplier Registration Workflow Definition

 

The first step is to create a Workflow Definition for the supplier workflow. This step is similar to creating a Workflow Definition for Project or Contract workflow. It includes creating an XPDL file that contains the logic for the approval workflow including the details on how many approvals and the order of approval. For more information on creating a Workflow Definition, please refer to the Scripting and Workflow Configuration guide on the SAP Service Market Place.

 

Step 2 – Define Supplier Field Access Definition

 

In project and contract workflow when the workflow is trigged the document is locked so all the fields are read-only. In supplier workflow, with Supplier Field Access Definition it is possible to control what fields can remain editable on the supplier record in a specific phase. Supplier Field Access Definition can be accessed from Setup > Document Setup > Suppliers. Note this is an optional step depending on the requirement of your supplier workflow. Create a new Supplier Field Access Definition and select the fields you want to allow edit access to. The screenshot below shows the edit access allowed for Order Address 1 through 3 fields. Both the standard fields and custom fields will be listed on this page. Note that this does not apply to collections (both standard and custom).

 

8-9-2012 3-25-12 PM.png


Step 3 – Define Supplier Phase Configuration

 

Supplier Phase Configuration is where the phases for the supplier registration/modification are defined. There are four system phases – Created, Modified, Approved and Rejected. These system phases cannot be modified or removed. Let’s take a look at each one of these phases:

Created phase - Created phase is automatically set when the supplier registration/modification is created.

Modified phase – This phase is set when the data is updated

Approved phase - When this phase is reached, the vendor registration/modification request has been processed by the approver

Rejected phase – Indicates a request that is denied

 

Note that both Approved and Rejected phases are configured as “next” phase in the Supplier Configurable Phase Definition. New custom phases can be added but should be added between the Modified and Approved phase.

 

Now that the phases are configured let’s take a look at the configurations for each custom phase.

Next and Previous Phase: For each custom phase the valid next and previous phases should be configured.

 

Add Workflow Definition: For each workflow phase a Workflow Definition should be added

 

Add Supplier Field Access Definition: Each phase can be associated with a Supplier Field Access Definition. It allows you to control what fields can be editable on the supplier record for a particular phase. By default all the fields on the supplier record are not editable. In most cases, Supplier Field Access Definition will be added to a workflow phase; however, it is also possible to add it to a non-workflow phase.

 

8-13-2012 9-34-55 AM.png

Step 4 – Define Supplier Type

 

This is the last configuration step. In this step, Configurable Phase Definition created in step 3 is added to a Supplier Type. In addition, the Supplier Type should be associated with a supplier self-registration UI mapping. Note that the changes made to the Supplier Type do not affect the current supplier registration requests / modifications.

 

As a last step, ensure the Document Security Templates for supplier registration and supplier modification are configured so that the approvers are properly added when the registration or modification approvals are triggered.

 

Hope you found this blog useful.

Introduction

In order for an organization to extract the expected value from implementing a new system or business process, it’s critical for users to adopt the system and drive the change throughout the organization.  We often get questions about how to drive organizational change and encourage user adoption – these questions most often come from our customers and their implementation teams.  Change is hard.  This is especially true when implementing new systems that affect strategic processes such as sourcing and contract management.  These processes are typically not rote in nature as is typically the case with operational transactions.  Sourcing and contract management often require planning, strategy, and sufficient time to achieve the end results that you are looking for.  There’s an expectation that there will be collaboration both internally and externally (with an organization’s business partners) to achieve those results.  In the following paragraphs, you’ll find some tactics that customers and their implementation teams have used to successfully enable change and encourage user adoption.

 

End User Adoption

1.  Visible executive sponsorship is critical to encouraging users in adopting new systems and doing things differently.  If users are left to make their own decisions about using a new system, very often they will continue doing what they are used to doing.  Users need to know that what they are doing matters to their management.

2.  Communication is another key aspect of driving adoption.  Employees need to understand why things are changing and the importance of the change to the organization.  They need to understand that they have a role in helping to make the change successful.  Build momentum by recognizing successes. 

3.  Appoint a champion to lead the program and identify early adopters that are willing to be change agents.  Publicly acknowledge and reward change agents.  Leverage change agents to provide a support system for end users to resolve issues and answer questions. 

4.  Don’t skimp on training.  Be sure that users have the tools and training necessary to be successful.  Ensure that users understand both the use of the system and how it applies to the business processes that are affected.  Help them to understand the benefits and efficiencies to be gained.  Don’t make training a “one-time” event.  Offer training periodically on key topics.  Survey the users to understand where they are having problems and to identify what training will help them.

5.  Establish metrics and reporting.  Help users understand what is expected of them and how they will be measured.  Monitor activity and what users are doing on a monthly or quarterly basis. 

 

Supplier Adoption

1.  Ensure that qualifying suppliers have a real opportunity to win business.  It’s important that suppliers have confidence that when they are taking the time to learn a new system to respond to requests that they also have the opportunity to win the business. 

2.  Assure suppliers that the system provides a more level playing field.  We often hear that suppliers are reluctant to use a system to submit bids and proposals because they fear that they are losing the personal contact.  Help them to understand that using a system actually opens up more opportunities and makes the evaluation process more objective.

3.  Let your suppliers know that you are committed to the process and technology – and it’s not going away.  Help them understand that the use of technology in the business process enables collaboration, communication, and visibility – and it is important to your business goals and objectives.

4.  Provide training opportunities for your suppliers.  Web conferences, where the suppliers can remain anonymous (if desired), provide an inexpensive means of providing training and enabling suppliers to use new technologies.  This will go a long way in eliminating fears and concerns.

5.  Establish a support system for suppliers.  Give suppliers a way to ask questions and get support when they are responding to requests.  Encourage them to respond early in the process to avoid last minute problems. 

 

Technology doesn’t eliminate the communication and collaboration that should occur as part of the business process.  In many ways, the role of the sourcing or category manager changes from one of managing and consolidating spreadsheets to one of managing the process, communicating with internal and external stakeholders, and driving results for the organization. 

It’s that time again!! We are almost ready with SAP Sourcing/SAP CLM Release 10.0 !!! SAP is looking at you, existing SAP Sourcing or SAP CLM customers, to help gauge the demand and timing of SAP Sourcing / SAP CLM 10.0. Based on your feedback, SAP will set the Ramp-Up start date accordingly.

 

But first, let's address the basic question.

 

What does SAP Sourcing Ramp-Up give you?  It provides:

  • ·Accelerated head start on achieving business value with new leading-edge solutions

o Getting the software up to 6 months before general availability

o Support for installation and configuration

  • Benefits from intensive monitoring and support by the back office of the SAP Ramp-Up organization

o Direct channel into SAP Development Organization (via the Ramp-Up Back Office)

o Prioritized and expedited solution of your questions and error messages

  • A smooth implementation and reduced project risk

o Coaching and support for scoping and project execution

  • An opportunity to give feedback and thereby influence right where the decisions for tomorrow’s solutions are made
  • Early Training for your Key-Users and consultants
  • Access for 10 users in your company to e-learning at no additional cost
  • Project Staffing with trained consultants
  • Certified Ramp-Up Coach from SAP Consulting
  • Board attention on your project (regular reporting)
  • Provides software which was already rigorously tested

 

The organization and roles during ramp-up are summarized below:

 

RampUP figure 1.png

 

What about you, our customer? What is your commitment?

    • Assist in Project Scoping during enrollment
    • Commitment to:

o Install the new software within 2-3 weeks of receipt

o Go Live

o Apply support packages as soon as available

    • Projects must have direct involvement of SAP Consulting (Ramp-Up Coach)
    • Implementation of current default release of SAP Solution Manager
    • Regular feedback provision (via project manager to regional Ramp-Up owners)
    • Partner consultants must be trained on the new solution through Ramp-Up Knowledge Transfer
    • Act as a reference before and after going live

 

In addition to the above benefits of a ramp-up program, what about the release itself?  What is in release 10.0 that would compel you to upgrade from releases 5.1, 7.0, or 9.0?  Here is a summary of the key Enhancements by release:

Release 10 - Slide 1.png

Release 10 - Slide 2.png

Release 10 - Slide 3.png

*Denotes features will be available in certain Service Packs in Release 7/9

 

 

Please also look for a blog from me that will provide more details of the SAP Sourcing / SAP CLM 10.0 enhancements.

 

If you are interested in becoming an SAP Sourcing / SAP CLM 10.0 Ramp-Up customer, or would like more information, please contact Kevin Mulligan at kevin.mulligan@sap.com, or please feel free to send me an email.

We, the SAP Sourcing team is very pleased to announce, that we are now ready with the new and upcoming SAP Sourcing/CLM 10.0 release for our On Premise customers. As noted in the previous blog by Anne McClelland, Release 10 is almost ready for release to customer, with Ramp Up (another blog with further details on Ramp Up is also upcoming) planned for very early in Q2 of 2014, and general availability set for Q4 of 2014. Release 10 will also have a full maintenance cycle, with end maintenance slated for December 31, 2018.

 

To stay within our legal guidelines, I should also point out that all of this blog’s content is subject to the disclaimer at the bottom of this blog.

 

Ok, now that we have gone over the release schedule, let’s dive into the main course, and the exciting world of SAP Sourcing/CLM Release 10.

 

SAP Sourcing / SAP CLM 10.0 Theme

 

SAP Sourcing / SAP CLM 10.0 is based on the strong SAP philosophy of Customer-Driven Innovation and Enhancements, and this will remain our guiding principle moving forward for all our upcoming releases. The other major themes our 10.0 release is predicated on are:

 

  • Improved User Experience
  • Open Connectivity
  • Reduced Total Cost of Ownership (TCO)

 

Let’s now look at each area that has been enhanced and improved for this release:

 

 

Cross-Solution Enhancements (Usability)

 

Recents and Favorites feature on the Supplier Side. Beginning with Wave 8 (Release 9.0 for On-Premise), SAP Sourcing / SAP CLM introduced Recents and Favorites on the buyer side. This feature provides a clean, quick way to pull up key documents, while removing clicks and providing a more intuitive navigation. This proved to be such a success for the end users that SAP has now added this ability for the supplier-side users.

"Add" button dropdown selector. When adding an RFx Question or an Agreement Performance, the user must first pick a type, e.g., a yes-no question type ("Type" first, "Add" second). But picking the type first and then clicking Add is counter-intuitive; the user typically wants to add, and then indicate what he wants to add ("Add" first, "Type" second). The "Add" UI now has a dropdown to make it easier and more intuitive.

New Edit button on the Attachments window and Discussion window.  One source of user confusion is when a user clicks down into a window, and then cannot perform his desired action because he is not in Edit mode. Instead of forcing the user to close up the window and navigate back out, click Edit, and navigate back down, the Edit button is now available in the lower-level  Attachments window and Discussions window. This goes across all documents that have this capability, namely Projects, RFx documents, Auctions, Master Agreements, and User-Defined Objects.

Image file in My Settings. The system allows you to include a picture of yourself in My Settings. This enhancement was made in preparation for potential mobile applications that will be integrated with SAP Sourcing / SAP CLM.

Access the Discussion report from documents. Having the Discussion report available from within documents makes it easier for users with access rights to see and export all of the topics and messages associated with one document. Filter capabilities make it even more useful to find specific messages, dates, and authors.

Provide number of records returned and displayed per page.  Providing the number of records being displayed helps the users manage their search results records. This is available in all List pages, Collection pages, Query lists, Reports, and pickers.

Back button positioned more intuitively. Users have previously missed the application "Back" button because of its position at the extreme far right side. The application "Back" button is now positioned at a location that is more likely to be seen by the user, is more consistent with other "Back" button locations, and is alongside the breadcrumbs to visually group the navigation actions together.

iPad Compatibility. While it is not expected that users will use the iPad exclusively, there are many advantages to being able to review approvals, run reports or refer to specific documents via the iPad.  A new workbench has been introduced specifically designed for the iPad to make it easy for users to navigate to those tasks that will be most likely done on an iPad. But be aware that there are some limitations with the iPad, namely: Flash is not supported (dashboards and Attach File requires Flash, and therefore cannot be run on the iPad), tooltips are not available, and Excel downloads cannot be edited.

Print Supplier Registration Page. Once suppliers have registered with SAP Sourcing/SAP CLM, they wanted a way to print and have a record of their supplier registration for auditing and verification purposes, and a print functionality is now provided to get a clean printed document.

Increased availability of Auto-Complete functionality. Auto-complete functionality enables users to have fields populated in with significantly fewer clicks. Auto complete or type-ahead functionality is available in various areas of the application, and the availability of this functionality within the application has been expanded even more.

Expanded Browser Support. Internet Explorer version 10 is also now inherently supported along with various versions of Firefox, Chrome, and Safari, as explained in this blog.

 

Strategic Sourcing Enhancements

 

Save Auctions without Commencing. Buyers cannot make interim saves while creating an Auction, so they have no other option but to completely define the auction. Save functionality has been added to Auctions so that auctions can be created carefully, without the fear of kicking off a half-completed auction, or having to start fresh each time.

RFx line item Offers Report for export. A new report is now available to show RFx line item Offers, which can be exported to Excel.  This is helpful for offline analysis.

Buyer option to hide currency exchange rates from suppliers. The enhancement controls whether the currency exchange rate information is exposed to the supplier in order to better maximize response efficiency.

Buyer option to import currency exchange rates. Buyers now have the ability to import exchange rates when creating an RFx. This allows users can now use Exchange index rates from common sources easily to provide consistency.

Enhanced information for suppliers of existence of line item groups. When line item groups are used in an RFx, it is sometimes easy for the supplier to miss seeing all the line items across all line item groups. The system has been enhanced to improve user experience by ensuring that the supplier is aware of line items that may be "hidden" in other line item groups.

Display descriptions for attributes in Formula Editor. Descriptions for the Line Item Specifications, Supplier Entered Attributes, and Formula descriptions will now be displayed in the Formula Editor to provide a clearer view of the attributes in use.

Notifications to all the supplier contacts for RFx and Auctions. Notifications for RFx, or Supplier which were restricted to the primary supplier contact, can now be sent to all the supplier contacts, based on a simple setting to ensure notifications are not missed in case of primary contact unavailability


Contract Management Enhancements

 

New Contract Generation Service.Contract Authoring (also known as Contract Generation) is a key SAP CLM functionality to automatically create legal contract documents in the CLM repository through the use of pre-created clauses, sections, and templates. This process has been streamlined to reduce TCO and support the DOCX format introduced with Microsoft Office 2007 and higher. A separate server is no longer required to perform contract generation. Note that while this is a 10.0 enhancement (possibly to be released in a support pack), this feature is also being implemented into service packs for releases 7.0 and 9.0.

Clause Section Break flag. Clauses that have the section break feature turned on will enforce a MS Word Section break immediately before it. The new section within the contract document can then have its own unique header and footer format as it was defined within that clause.

Perpetual Terms Checkbox enabled. Previously, ERP integrated Master Agreement Document Types were prevented from turning on the Perpetual Term checkbox. Now, if you use the Master Agreement/Sub-Agreement structure, you can define the MA as perpetual and still setup your Sub-Agreements with start and end dates.
Integrated and Non-Integrated in Same Hierarchical Family. Previously, Master Agreements that were part of the same n-level hierarchy family had to all be from doc_types that had Integration System Type enabled (SRM or ERP) or all had Integration System Type disabled (None). Now, Master Agreement hierarchy families can have Integrated and Non-Integrated Master Agreement documents within the same hierarchy family. When creating a child agreement from a parent MA, users can select doc_types with any of the 3 Integration System Types:  None, ERP or SRM. Similarly, when linking an existing Master Agreement with another Master Agreement into a parent/child relationship, the pick-list of Master Agreements will include MAs that were created using doc_types with Integrated System Types of None, ERP or SRM.


Cross-Solution Enhancements (Platform)

 

Ability to Share a Saved Search with other colleagues, and globally. The Save Search capability was introduced in release 7.0. The enhancement to this is the ability to share the Saved Search with other selected (or all) users.

Wizard Driven Visual Workflow Editor. An extremely functional visual workflow editor is now available as part of the SAP Sourcing/ SAP CLM application will now be made available. This functionality would allow the entire workflow process to be easily defined with in the application and thus eliminating the need to use any 3rd party tool, thus reducing TCO.

Implementation of SAP Virus Scan Interface (VSI).  Provides integration with McAfee, Clam AV, Bowbridge, and other antivirus products.

Support for Symantec Protection Engine for Cloud Services version 7, and ICAP Protocol. Support for the new version of Symantec Protection Engine (version 7) is now available, and along with it SAP Sourcing/ SAP CLM will now also support the ICAP protocol, and thus reducing the TCO for our customers.

Web Services Framework .  With 10.0, SAP Sourcing will deliver the first set of the new Web Services Framework features. This will support RESTful architectural style of web services, allow runtime enablement of web services, support OAuth authentication and authorization protocol, and allow custom script and query-based web services. This means that customers, partners, and consultants can design and develop their own specific custom web services using custom scripts and standard or custom queries.

Scripting Supportability Tools. New Standard Logging Information is now available in INFO mode. There will be no need to turn on DEBUG to get all the pertinent script execution information, such as start/end time, execution duration, etc. in the logs. Additionally, a new report is also being made available to display document-related active scripts for easy determination of the classes and hooks (contexts) that are in play. The report will provide details of the sequence of script execution relative to document lifecycle, and also navigate through related subordinate objects and scripts associated with them.

System-Oriented Application Authorization Report. A report is now available to view all the authorizations and access privileges that a user or a group has been provided. All this authorization information can now be easily accessed and exported by an Administrator from one neat report rather than navigating through multiple security settings.

Database support. SAP Sourcing/SAP CLM will now also support DB2 version 10.5 to ensure our customers can use newer versions of the database to take advantage of better features and also to ensure landscape harmonization.


Integration Enhancements

 

Support set of ERP item categories (Item Type) in integrated documents. New standard item types that are supported in the RFx include Consignment, Subcontracting, and Material Unknown. New standard item types that are supported in Agreements include Consignment, Subcontracting, Material Unknown, and Material Group.  Custom item types are also supported.


That provides a very high-level description of the features that will be available with SAP Sourcing/SAP CLM Release 10. This probably is not going to satisfy your appetite and so we in Product Management, will be providing detailed blogs, and other content which should amplify this functionality and offer you a much deeper look. So please keep your antennae up and watch this space for more on Release 10 features!


Please don’t hesitate to get in touch if you have any further questions.

 

 

Legal Disclaimer:


The information in this document is confidential and proprietary to SAP and may not be disclosed without the permission of SAP. This presentation is not subject to your license agreement or any other service or subscription agreement with SAP.  SAP has no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation and SAP's strategy and possible future developments, products and or platforms directions and functionality are all subject to change and may be changed by SAP at any time for any reason without notice. The information on this document is not a commitment, promise or legal obligation to deliver any material, code or functionality.  This document is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.  This document is for informational purposes and may not be incorporated into a contract. SAP assumes no responsibility for errors or omissions in this document, except if such damages were caused by SAP intentionally or grossly negligent.


All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations.  Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions

Introduction

 

Master Data integration is a pre-requisite to successful business process integration.  This document is intended to provide you with a simplified view of the steps required to implement this integration.


Adequate preparation for integrating SAP ERP Master Data with the SAP Sourcing/CLM application will help you get a jump start on a successful integration of these two major SAP applications.


The following checklist should help you prepare for and then be successful with this important integration activity.  Please note that the following Configuration Guide References are based on the Configuration Guide available on the SAP Service Marketplace.


If you would like a copy, you can download it from Service Marketplace by clicking this link:
Configuration Guide for Integrating SAP ERP and SAP Sourcing

 

StepDescriptionConfig Guide Reference
1.First perform the “Basic Configuration of Integrated Systems” as described in Chapter 3 of the Configuration Guide.3
2.Extract the Unit Category Text and Unit Category  customizing data from ERP using program BBP_ES_CUSTOMIZINGDATA_EXT_CSV4.1.1
3.

Extract the following customizing data from SAP ERP:

  • Currency ISO codes
  • Currencies
  • UOM ISO codes
  • Units of measure
  • Company codes
  • Purchasing organizations
  • Regions
  • Plants
  • Purchasing groups
  • Material groups
  • Payment terms
  • Condition types (price conditions)
  • Incoterms
  • Vendor account groups

using program BBP_ES_CUSTOMIZINGDATA_EXTRACT

4.1.2
4.

Import the customizing master data into SAP Sourcing in the specific order given below since dependencies exist between certain customizing master data objects:

1) Currency ISO Codes

2) Currencies

3) Unit Category Text

4) Unit Category

5) UOM ISO Codes

6) Unit of Measure

7) Company codes

8) Purchasing organizations

9) Regions

10) Plants

11) Purchasing groups

12) Material groups

13) Payment terms

14) Condition types (price conditions)

15) Incoterms

16) Vendor Account Groups

4.1.3
5.For the initial load, extract Material Masters from ERP using report program BBP_ES_MASTERDATA_EXTRACT 4.2.1
6.For the initial load, import the Material Masters extracted above into SAP Sourcing.4.2.1
7.Configure ERP, Netweaver PI, and SAP Sourcing as described in Configuration Guide section 4.2.2 to automatically create and pass MATMAS05 IDocs from ERP, through PI, and into SAP Sourcing so that all Material Master changes (“deltas”) are replicated into SAP Sourcing.  Note that this configuration step should be coordinated with the Material Masters initial load extract above so that any changes to the Material Master data after the initial load extract are not lost.4.2.2
8.For the initial load, extract Vendor Masters from ERP using report program BBP_ES_MASTERDATA_EXTRACT 4.3.1.1
9.For the initial load, import the Vendor Masters extracted above into SAP Sourcing.4.3.1.1
10.Configure ERP, Netweaver PI, and SAP Sourcing as described in Configuration Guide section 4.3.1.2 to automatically create and pass CREMAS05 IDocs from ERP, through PI, and into SAP Sourcing so that all Vendor Master changes (“deltas”) are replicated into SAP Sourcing.  Note that this configuration step should be coordinated with the Vendor Masters initial load extract above so that any changes to the Vendor Master data after the initial load extract are not lost.4.3.1.2

 

  • If you plan on publishing Suppliers from SAP Sourcing to SAP ERP, follow the additional instructions in Configuration Guide section 4.3.2.
  • If you plan on integrating to multiple SAP ERPs – to take advantage of the ability to distribute SRM Central Contracts to multiple ERPs via the SAP Sourcing/CLM SRM integration - follow the additional instructions in Configuration Guide section 4.3.4.

 

Additional Information

 

There are a number of blogs which have been written on the topic of Sourcing/CLM Integration with ERP.  The following are additional blogs that you might find useful:

 

The following blog documents the mechanism by which one can debug the Outline agreement or the PO creation process in SAP ERP system as a result of the publish event triggered from SAP Sourcing.


Pre-requisites: In the ECC system, activate Logging of the publish events originating from SAP Sourcing. In order to do so,

  1. In transaction SPRO navigate to "Integration with other mySAP.com Components - SAP Sourcing - Make settings for Integration with SAP Sourcing"SIMG.png
  2. Check the box 'Activate Log' in the section Technical settings (as shown below)

     SIMG2.png

Once the above configuration settings are enabled, whenever a publish event is triggered in SAP Sourcing, the paylod or data that is sent from SAP sourcing is captured and saved before an Outline agreement or a Purchase order actually gets creates in ERP. One can then re-use the data to check for the reasons of failure or debug the process.

 

Debug the Publish of Master agreement to ERP

In the ERP system use the transaction BBP_ES_ANALYZE and on the selection screen using the value help and filter criteria of "OA*" representing an outline agreement.

ANA1.png

Determine the payload by filtering on the date and time during which the Publish action occured in SAP Sourcing. It can also be searched by Master agreement number represeting the ID from sourcing as 'External Reference number'.

ANA2.png

After selecting the appropriate entry, the paylod for the specific publish event will be displayed, the data can then be verified and subsequently the Payload can be tested by choosing the 'Execute' or 'Debug' options.

ANA3.png

In order to start debugging the process, just click on the 'Debug' icon presented on the application toolbar and this will allow for the detailed analysis of hte payload as it gets executed.

ANA4.png

The outcome of both the Execute and Debug actions will result in an outline agreement either being created or updated. This can be verified using transaction ME33K.

 

The same procedure can be repeated for Purchase Orders, except that in the initial screen of BBP_ES_ANALYZE we will start by looking for the Purchase order related payloads published from SAP Sourcing (as shown below)

ANA5.png

 

If at the end of the 'Execute' or 'Debug' step data related errors are noticed, the same need to be fixed in SAP sourcing and the document can be republished.

PS: not all errors necessarily can be fixed from SAP Sourcing, some need to be addressed in ECC and some in the PI mappings depending on the particular case.

 

Cleanup of the Payloads:

   If the 'Activate Log' setting is left turned ON, there will be an accumulation of considerable payload data over time. It is always a good practise to

  1. Eanble Log during implementation or testing and if there are unexplained errors
  2. Deactivate the Logging when not needed and
  3. Clean-up payloads periodically

The clean-up of logs can be triggered by the transaction 'BBP_ES_RFC_DELETE'. This will allow for selective deleate of the saved Payloads.

 

Summary:

     BBP_ES_ANALYZE is a helpful transaction and can be very helpful in tricky situations when the publsh events fail without much information.

Actions

Filter Blog

By author:
By date:
By tag: