SAP Sourcing

13 Posts authored by: Armin Fakouhi

2013 is coming to an end and our team wants to offer you another technical training with our technical experts and SCN Champions Vikram Shanmugasundaram in the SAP America HQ in Newtown Square, PA. There are still seats available, so sign-up. Here is what you need to know.

 

Where to sign-up

 

When are the dates?

  • Monday, December 2 - Friday, 6 2013

 

Where is the training?

 

What will be the content of the class?

 

If you have any questions, please feel free to reach out to me Armin Fakouhi

SAP Sourcing is currently developing version 10.0 of its product and as of today, the versions 7.0 and 9.0 are available for download and maintenance on the service marketplace. In many forum entries, our support team is handling similar requests and they often sound like:"Where can I find .... ?" In the light of these queries, the team thought it might be a good idea to guide the users around in the big SAP Service Marketplace.

 

How can I log on to SAP Service Marketplace?

Every SAP customer or partner is issued a S-User, in order to login to the SAP Service Marketplace, you have to hit the URL: www.service.sap.com
In order to login to the SAP Support Portal, you will need your login credentials i.e.:

  • S-User
  • Password

In case you are puzzled about how to get your S-User, do not worry because you are not alone. There is a forum post about it which can be found here.

Login.jpg

Where to go for software downloads on SAP Service Marketplace?

 

Typically there are three use cases for accessing the SMP for downloads for each, there are different shortcuts, you can choose to make your life easier. Generally the easiest way to access software downloads on the SAP Service Marketplace is the following URL: www.service.sap.com/swdc

 

1) Download SAP Sourcing

In order for you to download any available version of SAP Sourcing, you should follow the following path. First go to Software Downloads (in case that is not already your landing page). Afterwards perform the following path:
  • Installations and Upgrades --> A-Z Index --> S
  • Search for SAP Sourcing / CLM by hitting Ctrl+F and type SAP Sourcing / CLM

 

Right now you can choose between the currently supported version of SAP Sourcing/CLM (7.0 and 9.0). The upcoming 10.0 release will be posted on this page upon its release date. On this page, you can choose between the installation of SAP Sourcing as well its underlying Java WebApplication Server SAP NetWeaver 7.3 (check for a good link here). On the Installation link, SAP Sourcing will offer you the different versions which are available for download. You should ensure that the correct version for your appropriate Operating System is downloaded. You can check the supported DB/OS combinations on the product availability matrix (PAM) by going to www.service.sap.com/pam and searching for SAP Sourcing

 

SWDC1.jpg

 

2) Apply the latest support package (SP)

Now let's get back to start (www.service.sap.com) and instead of Installations and Upgrades, click on Support Packages and Patches. Follow the same procedure to get to the SAP Sourcing/CLM support packages and patches i.e.:
  • Support Packages and Patches --> A-Z Index --> S
  • Search for SAP Sourcing / CLM by hitting Ctrl+F and type SAP Sourcing / CLM

SP_patches.jpg

 

Both for SAP Sourcing 7.0 as well 9.0, the support packages are divided into different Software Component Versions:
  • SOURCING ENT. CONTR. GEN 9.0: This will be the component for fixes on the contract generation side and it is OS independent (i.e. can be applied on every operating system)
  • SOURCING SRM JSERVER OP 9.0: This will be the component containing the main fixes on SAP Sourcing/CLM product, make sure that  you download the appropriate file for your operating system
  • XI CONTENT SRMJSRV 9.0 This component is used for the mappings on the SAP Sourcing side when integrating to SAP ERP.
  • XI CONTENT ESO SRM INT 9.0: This component is used for the mappings on the SAP Sourcing side when integrating to SAP SRM.
Additionally, you have also access to the support packages of the underlying NetWeaver version.
SP-component.jpg

3) Download support packages for versions out of maintenance

In case you are on a release which is no longer in maintenance (i.e. E-Sourcing 5.0 / 5.1), there is still a way to access the available support packages for these versions. In the Support Packages and Patches section, you can click on Archive for Support Packages and Patches and follow the same procedure as described above:

  • Archive for Support Packages and Patches --> A-Z Index --> S
  • Search for SAP Sourcing / CLM by hitting Ctrl+F and type SAP Sourcing / CLM

In this section, you will find the available support packages for the versions 5.0 and 5.1

archive1.jpg

 

How to find the product documentation for SAP Sourcing/CLM?

The Service Marketplace is a big place and there is always the risk to get lost in big places. I was happy when I discovered that there is a shortcut for everything, also on the service marketplace. Particularly when looking for product documentation, there is one useful to access the documents in one-click: www.service.sap.com/eso

Docu.png

 

In this section you can find the different documents for SAP Sourcing (NOTE: Make sure to click on SAP Sourcing On-Premise). You will be able to click through the different available versions. In the respective you can find*:
  • Master Guide
  • Installation Guide
  • Configuration Guide
  • Upgrade Guide
  • Scripting and Workflow Guide
NOTE: The availability of different guides can vary from version to version. Also be aware that sometimes not all guides are displayed right away. In that case, you can click "Display all documents" as shown below in the screenshot.
display.jpg
Hopefully you will find this blog helpful to navigate your way around the SAP Service Marketplace.

In the past weeks our team has often received requests about best practices with regards to database installations for SAP Sourcing/CLM. The main questions which have been posted via customer support as well as SCN is: "Is SAP Sourcing/CLM required to be on the same or a separate database from the Application Server NW Java?". The short answer would to this question would be: "It is technically feasible to install on the same database instance, but it is strongly recommended to install on a separate database"

 

When purchasing a license to deploy SAP Sourcing/CLM on-Premise, the recommendation from a technical perspective is to use one database for the application server (NetWeaver Java) and one database for the application itself. There are several reasons why this is a good idea:

  • Potential performance improvements
  • Less constraints in planning and execution of upgrade strategy
  • Easier version control since NetWeaver and SAP Sourcing do not have to use the same DBMS version
  • Higher flexibility in backup and restore strategy
  • Pick a DBMS such as SQL Server or MAX DB for Netweaver but ONLY DB2 and Oracle are supported for Sourcing / CLM.

 

For further references on the installations procedures, please read the installations guides on the Service Marketplace (www.service.sap.com/eso). Our team has also contributed some more knowledge on best practices related to the database usage:

Rise and shine in 2013. The SAP Sourcing Team is offering another series of training covering the entire spectrum of functional, technical and integration training. Here are the details you need to know:

How can I sign-up ?

You can find the all training links by going to the SAP Training Website and search for desired training class (TSO100, TSO150 and/or TSO180):


When is it planned?

  • Newtown Square classes:
    • TSO100: May, 13 - May, 17
    • TSO150: June, 10 - June, 14

 

Where are these sessions?

 

What will be the content of these classes?

How can I learn more about SAP Sourcing/CLM 9.0?

Our Product Management Team has summarized the latest and greatest features of SAP Sourcing/CLM 9.0 in a blog series on:

 

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

WORKBOOKS

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

workbooks.png

 

Upgrade Workbooks

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

  • Enterprise Upgrade Workbook
  • Company Upgrade Workbook

 

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

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

workbooks-company.png

 

On Demand Workbooks

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

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

 

OD_workbook.png

MAIL TEMPLATE REFERENCE

 

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

mail-token.png

 

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

  • Username
  • Password
  • URL

specific-tokens.png

 

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

 

mail.png

This is a series of blogs about the Reference Guide of SAP Sourcing. In this first blog, the focus will be on the Class Reference and the different views in the Class reference. There will be upcoming blogs about the different workbooks and mail templates.

 

General overview

 

The Reference Guide, often referred to as the “RG”, provides very useful technical information particularly when you are planning to do any
type of configuration.  The Reference Guide is accessible from the top of right-hand side of the page.  It is important to note that the Reference Guide link is only visible to users that have the appropriate permissions.

 

The Reference Materials is a section of the Reference Guide which is most commonly used for different page and toolbar customizations, scripting, tokens and other things. It contains the:

 

  • Class Reference
  • IAPI JavaDoc
  • Mail Template Reference
  • Database ERD

SAP_Ref_Guide_1.png

The RG is typically not used by the Business User but more by System Administrators, Query Developers and Scripting and Workflow Developers. In order to make sure that not every user can do modifications via Reference Guide, the access is restricted through Security Profiles.

 

NOTE: The Reference Guide is context-sensitive which means you will get different data, tables, etc. depending on where the Reference Guide is started from e.g. when launching the “RG” from a Master Agreement the user will see information related to Master Agreement when starting it from a Project, the user will see information related to Project.

 

The Class Reference

 

The Class Reference is the single source of truth in the application to find the Class ID and the different class numbers for the different display names. As an example searching for “Projects” will give you all information on the Class “Project” on the header of the page:

  • ID:   1100
  • Name:   projects.projects.
  • Display Name:  Project
  • Display Name ID: projects$projects.projects.class_name
  • Description ID:  projects$projects.projects.class_desc
  • Scope: COMPANY

 

class-refernce.png

 

The most commonly used class references are listed below, these can be used for e.g. queries and other things, it is important to note however that Class Name is case-sensitive i.e. when using it for a custom query make sure to consider the spelling.

 

ObjectClass IDClass Name
Project1100projects.projects
RFx900rfx.RFXDoc
Auction800doc.auction.auctionevent
Master Agreement1004contracts.Contract
Sub Agreement1003contracts.Agreement
Supplier607masterdata.Vendor
Value List Value616masterdata.ValueListValue

 

The Different Views of Class Reference

The Class reference page offers the user different views which can be used for different purposes and will be described in more detail below:

  • Summary View: This view contains information about different class members (similar information as the UI-view). One key difference is the additional information about field length, required (yes/no), field type (String, Data, Reference, Boolean, Price, VLV Reference, etc.).
  • Schema View: The Schema view shows the user in which database tables the data is stored, in the case of e.g. writing custom queries, this view would tell you which database tables the query is touching. This view however only lists standard fields, extension fields are not listed and can be found in the Extension Schema from the Setup page.
  • UI View: The UI view shows you the layout of the screens. It is most commonly used for UI Page Customization e.g. in case you want to change the order of a field or make it required. (NOTE: since Sourcing 7.0, these fields are drop-down list in the Page Customization setup  area)
  • CSV View: This view is relevant for data imports. In reviewing the CSV view, the user will find information about specific import templates such as data types and which fields are required and have to be populated in order for the import to be successful e.g. importing Master Agreements or User Accounts.
  • IAPI View: This view will tell you which IAPIs are available for potential Scripting and other customizations e.g. for Project IAPIs the following Project iBean and HomeClass can be found under iAPI view.
  • Toolbar View: This view shows all buttons on a particular page and on which Toolbar Customizations can be performed e.g. hide “Create Auction” button. This can be done through toolbar customizations. The toolbar ID of Create Auction button can be found in the toolbar view.

 

NOTE: Navigation Alt+Left Arrow will take you to previous page. Alt+Right Arrow takes you forward to the next page. Depending on the browser in use, you can check the shortcuts online (same for Firefox, Chrome).

 

Stay tuned for upcoming blog posts....

SAP Sourcing/CLM Center of Excellence is offering another series of training sessions in the month of November/December. The training will be held in our SAP training facilty in Houston, TX. Both trainings will be based on our latest release of SAP Sourcing/CLM 9.0/Wave 9 which has just entered general availability.

 

Here are the relevant links for this training:

 

 

If you are interested to learn more about the new features in our latest release, please feel free to explore our blog posts on SCN about:

In our last blog post, I touched base on the business process of Sales Contract Management. With the help of our experienced SAP Consulting
group in particular Jagamohan Padhy, we will now expand our blog series with a lot of interesting topics around Sales Contracts deployment through CLM.

 

What is the process flow in SAP CLM ?

 

Following up on the more generic business process of sales contract management, the question of how the actual business process in SAP CLM would look like is coming to mind. Below is a diagram to explain (NOTE: bear in mind that the mappings through PI are non-standard and need to be custom created) 

business_process_CLM.jpg

What are the first steps ?

 

In order to guarantee that all the steps are in place, the following perquisites have to be taken into consideration:

 

  • Supplier Management & Customer Management Supplier management information has to be renamed considering that now the focus
    is on Customer Management information; this is typically done through changing all localized resources containing "supplier" in the system to "customer".

 

  • Master Agreement types: The Sales Master Agreement should have custom fields/tables enabled to support business process and integration scenario for Sales Contract Management. This can be achieved through Page customization in SAP CLM.

 

  • Global Search: To take advantage of the full capabilities in SAP CLM, all sales contracts and master agreements need to be searchable by types which are typically achieved via creation of queries.

 

  • Data replication to integrated systems: When publishing master agreements on the buy-side, the information is going to ECC-MM whereas in the sales side scenario, the published information needs to go to ECC-SD. There is some custom work which needs to happen in PI to enable publish to SD.

 

What are the different deployment options?

 

There are four different implementation options in SAP CLM

 

  1. Standalone implementation for both sales and procurement contract
  2. Standalone implementation for sales contract and integrated for procurement contract
  3. Integrated implementation for sales contract and standalone implementation for procurement contract
  4. Integrated implementation for both sales contract and procurement contract

 

In a standalone scenario and non-integrated case, SAP CLM can be used for both procurement and sales contracts (case 1). Different sets of master data needs to be replicated into SAP CLM from workbooks, in addition to the standard set for procurement contracts, there would be a need to add also customer master data needs to imported e.g. through workbooks.

 

In the integrated scenario, once the contract management needs to be also published into the transactional systems such as ECC-MM for procurement and ECC-SD for sales contracts, there is some additional mapping to be done (for ECC-MM integration, please see these blogs). For sales contracts integration to ECC-SD, there is some custom design required.

Benefits of Sales Contract Management

 

The business process “Quote-to-Cash” is the main focus for typical Sales Contract Management. Generally, the main motivations for customers to implement sales contracts in their business are similar to procurement contracts: 

  • Companywide Contract Visibility across the value chain
  • Risk and Compliance Management especially to ensure contract compliance post execution
  • Accelerate Quote-2-Cash Process – increased time-to-value through automated workflows
  • Optimize through Integration – Integrate sales contracts with other systems such as ERP-SD, CRM
  • Increase Collaboration – collaborate internally and externally with customers and stakeholders on quotes and contract drafts

 

Sales contracts business process


Typically the business process can be viewed as a reverse source-to-contract business process with the following steps.

 

Business_process.jpg

Sales Contracts in CLM

Mapping the high level business process to the capabilities of SAP CLM, the realization could be executed in the following way.

 

  • Quotation: The quotation which is sent out to a customer is done in a different system than CLM. Typically this would be done in a CRM-system. After an initial negotiation, there will be a first contract draft for the customer.
  • Create Contract: The first contract draft will be done in CLM by creating a Master Agreement and the first draft of the contract document.
  • Negotiate Contract: The contract negotiation can be done inside CLM by using the Check-in / Check-out functionality in SAP CLM.
  • Approve Contract: After the initial negotiation, the contract can be moved via approval workflow to the next phase.
  • Create Sales Order: Move contract execution phase e.g. via SAP ERP-SD to create sales order
  • Monitor Contract: Track the key dates (Expiration date, renewal date etc.) in SAP CLM

 

 

The implementation of Sales Contracts has many different aspects which have to be considered. In upcoming blog posts, we will cover other topics like:

 

  • Implementation approaches
  • Security concepts
  • Integration aspects

 

Stay tuned....

The SAP Sourcing/CLM Product Team is offering another series of training sessions during September (in Newtown Square, PA) and October (in Walldorf, Germany). Training sessions will be focused on:

  • Functions and Features (TSO100)
  • Technical aspects (TSO150)
  • Integration to ERP and SRM (TSO180)

 

In this post, I would like to address some questions we receive from participants before/during our training classes.

 

Which topics are offered in TSO100 and who should attend?

The TSO100 class goes through all the functional aspects and capabilities of the product with detailled exercises and hands-on sessions in the areas of:

  • User Experience and Navigation
  • Workbench
  • Project Management
  • RFx
  • Auction
  • Contract Management
  • Supplier Management

We normally recommend this class for SAP Sales and Pre-Sales as well as Functional Consultants. This class also serves the need for helping customers who are just getting started and/or are planning to start an implementation project with SAP Sourcing/CLM.

 

Which topics are offered in TSO150 and who should attend ?

TSO150 is a technical class, and the focus lies more around the different technical aspects of SAP Sourcing/CLM. This class in part covers some advanced configuration topics which do not neccessarly require deep technical knowledge, such as:

  • Page customization
  • Localized resources
  • Extensions
  • Business Rule Designer
  • User Defined Objects

The second half of the class requires a good understanding of Java and SQL in order to gain benefit from this class. There will be lessons and hands-on sessions on technical aspects of SAP Sourcing/CLM i.e.:

  • Creating Reports and Queries
  • Write Scripting
  • Design and write Workflows

 

Which topics are offered in TSO180 and who should attend ?

TSO180 is our latest training offering and puts emphasis on the increased need and focus for integration to other SAP backend systems. As of v7.0 / Wave 7, SAP Sourcing has been offering a standard integration into SAP ERP-MM which is being enabled through PI (more blogs on integration: SAP ERP RFQ integration with SAP Sourcing, ERP integration - Tips and Tricks, Using Price Conditions in SAP Sourcing, Extracting Master Data for SAP Sourcing). With our latest release SAP Sourcing/CLM 9.0 / Wave 9, the product is now also integrated with SAP SRM Central Contracts (see blog on SAP Sourcing/CLM integration with CLM), we saw the need to offer a class on how to configure this integration and benefit it.

As a pre-requisite for this class, it is recommended that the participants have already experience with either of these solution and in the optimal case with all of them:

  • SAP Sourcing/CLM
  • SAP ERP
  • SAP SRM
  • SAP NetWeaver PI

 

Do the participants get hands-on session with the product in these classes?

Yes, the main focus of all of these classes is to explain and expose the participants to the system as much as possible. All classes have exercises and solutions which will be handed out to the students afterwards for "home-study" sessions.

 

Does this class cover installation related questions?

No, none of these classes are covering installation related question. For any installation related queries, we recommend to study the Installation guide which is available to all SAP customers on www.service.sap.com/eso. Also does this class not cover any application server related issues; for all on-Premise customers, we recommend to study the NetWeaver installation guide which is also available on https://service.sap.com/netweaver

 

How do I sign up ?

All trainings onwards will be held in a SAP Sourcing/CLM 9.0 system. The classes can be booked via www.training.sap.com. The direct registration links for the trainings are listed below

 

Functional Training:

 

Technical Training

 

Integration Training

 

Stay tuned for more...

SAP Sourcing/CLM has numerous options to notify users of either upcoming events or personalized messages before the first usage of the product. This blog post should summarize all the possibilities of notifiying users in SAP Sourcing/CLM.

 

Global Message to all users

 

The purpose of this kind of message is to provide a message to all users that are logged into the application, in real time. This is referred to as the Global Message and it is configured at the system level and will apply to all users in the system (in a multi-tenant system, it is applied to all tenants).

 

The message is configured by logging in as the “system” user and choosing “Set up Global Message”. This message type is mostly recommended for system downtimes due to upgrades and/or maintenance. It is important to mention that with this option, usually the system user can set the start and end time until the message is not displayed in the UI any longer.

 

Global Message.jpg

 

Message at Login Page

Another way to provide messages to users would be via the login page prior to logging into the application. This can be accomplished
using 2 localized resources for both buyside and sellside. 
  • Usermgmt$login.securityWarning:
    This localized resource is used to provide a message on the “buy side” login page of SAP Sourcing / CLM. The message will appear just below the logon button.

 

  • Usermgmt$login.securityWarning.sellside:
    This localized resource is used to provide a message on the supplier portal login page of SAP Sourcing / CLM. The message will appear just below the
    logon button.

 

Change the localized resource with the message to the users, and save it.

Edit_localized_resource.jpg

 

Typically, these messages are used to alert users of pending down times or other things that may affect them once they login. There is no time limit to this option, in this case the user has to deactive the localized resource in order for this message to disappear.
login_page.jpg

 

Welcome Pages

 

In order to provide a longer detailed message to users announcing an upgrade configuration change, or more in-depth information about system use. These messages can be used for items such as scheduled system down time as well as more in depth descriptions of new functionality.

welcome page.jpg

Welcome Pages are a great way to provide information to the end users regarding changes to the system, either due to a system upgrade or perhaps a significant system change. Welcome pages are configured on the Company object, which means that each unique company may have a separate message. Users will see the message just once, the first time they login after the message is configured. The messages may later be inactivated when they are no longer applicable. The messages may be configured using Rich Text which allows for more advanced formatting.

 

welcome.jpg

 

 

As a follow up post to Paul Wagner's blog on Global Search, Product Development and Center of Excellence have created a new document on Global Search which focuses on:

  • How does Global Search work
  • How to operate Global Search
  • Global Search Adminstrative reports
  • Other daemons and reports
  • Troubleshooting

 

The document is available in the latest Operations Guide for SAP Sourcing/CLM on www.service.sap.com/eso --> Click Solution Operation Guide for SAP (Chapter 7)

This blog should explain the user how to setup and utilize User Defined Objects in SAP Sourcing/CLM.

 

Introduction

 

SAP Sourcing/CLM is known for its flexibility and configuration capabilities; some examples are the ease of adding new fields and the ability to configure the user interface with different field labels and layouts. Another feature which has been proven to be very helpful for our customers are User Defined Objects
(UDO).

 

UDOs allow system administrators to configure an entirely new business object. They include all of the major features of SAP Sourcing business documents including the document type / template creation model, configurable phase definitions, workflow, and user collaboration. The main use case for customers have been:

  • Custom forms (e.g. project requests or legal service requests)
  • Non-disclosure agreements (NDAs)
  • Surveys
  • Legal Service requests
  • Custom approvals for certain categories

 

Enable UDOs

 

A base installation and setup of SAP Sourcing does not come with UDOs enabled. UDOs are enabled via system properties that are set by the system user. There is a single property that turns them on and separate system properties that enable each of the five configurable UDOs. There are system properties for both purchaser side and supplier side enablement (UDOs are able to be seen by suppliers in addition to buyers if the requirements dictate such).

Enable UDO.jpg

Security Profiles

 

Once the system properties are enabled, UDOs are available for use in the system. However, SAP Sourcing does not come with any security profiles that provide access to the UDOs; as a result, adjustments to the relevant security profiles are required to provide the appropriate access to the UDOs and the associated setup objects (document types and configurable phase definitions).

Enable UDO_1.jpg.png

 

Upon establishing the system properties and security profile settings, a new navigation menu option will exist for UDOs. You can enable up to five UDOs with different settings, in the case above, only one UDO is enabled.

 

 

Enabled UDO BizDoc .jpg

Security Template

 

One important step in the setup of UDOs is to create a security template for the new object. Security_template.jpg

  

 

 

Localized Resources

 

 

 

Finally, SAP Sourcing provides a basic set of tabs and data that can be used on a UDO. Obviously, the real power is achieved by adjusting the layout through page customizations and adding new fields via extension definitions. Also, for UDOs, it is important to update the localized resources so that terms such as ”User Defined BizDoc” are changed to the appropriate term based on the configuration.

 

 

 

 

Before:Before.jpg

 

 

 

 

After

After.jpg

Wrap-Up

 

As you can see, the real power of UDOs is achieved through the inherent SAP Sourcing flexibility that enables custom fields and user interface adjustments using the extension definition and page customization capabilities in setup.

 

 

To review, the key things to do when adding UDO functionality to an implementation are:

 

  • Enable UDOs using system properties
  • Update the appropriate security profiles with the necessary access rights
  • Update the appropriate localized resources to reflect the true use of the UDO
  • Add the necessary extensions and page customizations for the business functionality required
  • Create the appropriate Document Types
  • Create the appropriate Phase Configurations
  • Add Workflow (if required)

 

 

 

 

 

Actions

Filter Blog

By author:
By date:
By tag: