Quantcast
Channel: SAP Cloud for Customer
Viewing all 262 articles
Browse latest View live

Opportunity External Pricing (Integration with ERP through PO)

$
0
0

Introduction

Pricing can be maintained in C4C although, most common scenario is to have them stored on ERP system. Having real-time pricing on the Opportunities, recovered from ERP, is a typical scenario. This is performed by doing a synchronous call to recover pricing from pricing conditions stored on ERP side.

 

1.jpg

 

 

Purpose

I am currently working on an Integration project where we are connecting C4C with ERP through PO and, it is being difficult to gather the required information for setting the complete process. There are plenty of great documents for pricing related to Sales Quotes but, the way it is customized is different to Opportunity pricing.

In case you have access to C4C50 flipbook through Learning Hub, you will learn how to setup these External Pricing but through HCI and not through PI/PO so, hope this blog will fill this missing scenario; that's the reason why I have decided to write it. (This document is being written based on version 1505.)

 

 

 

STEP 1: C4C Configuration

It is required to configure a few things on Cloud for Customer (C4C) side:

 

a) When doing Scoping, adjust the required elements in order to activate this function; include in your scope the questions “Do you want to use your SAP ERP solution to calculate prices for opportunity items in your cloud solution?”. You will find it under:

    1. Communication and Information Exchange
    2. Integration with External Applications and Solutions
    3. Integration with SAP ERP

 

2.png

 

b) In C4C, Create the communication arrangement for the real-time opportunity pricing.  The communication arrangement is called Opportunity with Sales Order Pricing in ERP.

 

c) Check C4C Price Lists under Products >> Price Lists. Create a new price list and assign desired products. Also, it is possible not to have prices on C4C side and directly handle them from ERP. (this is my current Business Scenario)

 

 

 

STEP 2: ERP Configuration

Here it is required to configure the Pricing web service through SOAMANAGER transaction:

 

WebService name is “SalesOrderPricingInformationQu”. This should have been leveraged automatically when following standard Integration Guide provided by SAP on its Marketplace so no steps to be done here.

 

3.jpg

Also, it is required to check that Pricing Conditions exist in ERP.

 

 

 

STEP 3: PI/PO Configuration

Ideally, this task should be handled by someone with understanding on PI/PO. Starting from a template, communication channels should be created (or added) and then, SOAP adapter should be configured.

In our case, it happened that templates had an older version of adapters so communication channels were created manually in order to point to latest adapter version.

 

4.png

 

 

 

STEP 4: Quick test!

Once previous Steps are done, we are ready to conduct a quick test:

1. Once in C4C, navigate to “Sales” workcenter and then, into “Opportunities”:

 

5.jpg

 

2. Create a new Opportunity. It is important to know that, before doing so, it is required to personalize the screen in order to add Sales Organization, Distribution Channel, Division and, Sales Unit as Materials should be assigned to them.

 

6.jpg

 

3. After having added the requested fields, proceed to create a new Opportunity and also, complete the organizational data (on the previously added fields). Let me highlight once again, if you do not enter Sales Organization, Distribution Channel, Division and, Sales Unit, you won’t get the “Request Pricing” action enabled.

 

4. Click into Products section and Add a new Product. Once added, you will be shown with the list of all the added Products so, there, you should click on actions (grey wheel) and select “Request Pricing”.

 

7.jpg

 

Hope this blog helps you avoid several headaches!

Regards.

Alejandro.


Apple Watch Charting using SAP Digital for Customer Engagement API

$
0
0

Disclaimer

Public access to the SAP Digital for Customer Engagement OData API is not supported currently. Customers/developers/partners should reach out to SAP for any such requests. For this sample your own login credentials will be used to access the OData API's


Who is this blog post aimed at?

This blog post is aimed at developers & partners. The sample code demonstrates how to connect an iOS & Apple Watch app to the SAP Digital for Customer Engagement OData API’s for both Accounts & Opportunities and render the Opportunity data in an animated dynamic bar chart.


What topics does this blog post cover?

  • Setting up a SAP Digital for Customer Engagement trial account
  • Connecting an iOS app to the OData API & displaying Accounts & Opportunities in a list view
  • Connecting an Apple Watch to the OData API & displaying a list of Accounts and a dynamic chart showing Opportunities and their sizes

 

Sample Code Architecture

C4CAppleWatch.png

Apple Watch.png

What is SAP Digital for Customer Engagement?


SAP Digital for Customer Engagement is a simple, yet powerful CRM solution that’s designed to help smaller sales teams get up and running in minutes, but that delivers many of the same powerful capabilities as our enterprise offering. It can help your team close more deals by enabling them to sell smarter, work more efficiently, and collaborate more effectively.


For more info see: Introducing SAP Digital for Customer Engagement


How to get started?


It is super simple to sign up & free for 30 days!


Sign up for a 30 day free trial


Once you are signed up lets create some sample data!


Step 1

setup-1.png

Step 2

setup-3.png

Step 3

setup-4.png

Step 4

setup-5.png

 

 

Lets take a look at the sample code?

 

The sample code for this tutorial can be found here: https://github.com/SAP/c4c-apple-watch-chart-example

 


Running the sample project

 

    1. Clone the Github repo

 

          git clone git@github.com:SAP/c4c-apple-watch-chart-example.git

 

 

     clone_repo.png

 

 

     2. Open the Xcode project file called "ODataExample.xcodeproj"

 

          xcode_project_file.png

 

     3. Run the iPhone Xcode Scheme

          scheme.png

 

     4. Login with your credentials and click save & test them

 

 

          Enter the e-mail address & password you used to sign up for your 30 day trial account.

 

          Note: You must see “Credentials Valid” in the iPhone app's Log Viewer in order to confirm everything is connecting correctly.

 

 

         Once you see "Credentials Valid" in the log viewer click "View Accounts"

 

        iPhone.pngaccounts.pngopportunities.png

 

     5. Running the WatchKit App Scheme

 

     scheme2.png

 

What inspired this SCN Blog Post?


Watch the SAP Cloud for Customer: The Perfect Meeting - YouTube video we showcased the Perfect Meeting Apple Watch app at Sapphire 2015 in Orlando!

 

 

Thank You

 

That's it! Stay tuned for an update for WatchOS 2.0!!

Mandatory Fields

$
0
0

Hello Guys,

 

The other day I received some questions regarding what can be made mandatory and what cannot in the C4C system.
Based on this questions I thought that a blog post would be good to clarify things.

 

Important thing to remember when trying to make fields mandatory is that not all fields are can be made mandatory.

One example is:

 

When adding a Product to an Opportunity, on the QV (Quick View) you have the Product Category field, however, you will not be able to make it mandatory. This happens because on Quick Views, you are not creating any data, you are just adding existing data to another screen. Assuming that you know what you are adding, you do not need any mandatory fields on this part of the system.

 

Another thing is, only fields that you can "fill" are available to make mandatory. For example: on Customers Workcenter, inside an Account you have the Contact tab, there you have some Columns that filter the Contacts list and those cannot be made mandatory as well. However, you can make that specfic field mandatory on the Contact QC and it would achieve the same resutls.

 

So, in summary:

 

- Only fields that you can fill can be made mandatory;

- But even then, they might not in case they are in QV's (Quick Views).

 

I hope you guys enjoy it.

Please provide your feedback!

 

Thank you and best regards,

Felipe Fraga

Support Consultant

SAP Cloud Product Support

Are you a C4C partner looking for detailed information related to the C4C public cloud SaaS...Look No Further!

$
0
0

Welcome to the SAP Cloud for Customer Engagement Partner Community on SAP Jam!


You will find detailed broadcast videos, documents and other descriptive collateral related to the SAP Cloud for Customer service portfolio.

 

 

What is the purpose of this community?

This community has been setup to keep you up to date with the latest information related to the SAP Cloud for Customer solution offering. SAP will broadcast videos, documents and related information content regarding the SAP Cloud for Customer solution via this community to educate and inform our partners about the Cloud for Customer solution offering.

 

We will also be sharing event information that is relevant for this community of partners working with the SAP Cloud for Customer, public cloud software-as-a-service powered by the SAP HANA Cloud Platform.

 

Check out the video below for more details…


 

 

How do I undertake discussions about SAP Cloud for Customer?

Please join us on the SCN Cloud for Customer community at (http://scn.sap.com/community/cloud-for-customer) to create discussion threads at (http://scn.sap.com/community/cloud-for-customer/content?filterID=contentstatus%5Bpublished%5D~objecttype~objecttype%5Bthread%5D~thread%5Bdisc%5D) and access to a community of experts to help you further your understanding of SAP Cloud for Customer.

 

How do I undertake Q&A about SAP Cloud for Customer?

Please join us on the SCN Cloud for Customer community at (http://scn.sap.com/community/cloud-for-customer) to create questions at (http://scn.sap.com/community/cloud-for-customer/content?filterID=contentstatus%5Bpublished%5D~objecttype~objecttype%5Bthread%5D~thread%5Bopen%5D) and access to a community of experts to help you further your understanding of SAP Cloud for Customer. You can view answered questions at (http://scn.sap.com/community/cloud-for-customer/content?filterID=contentstatus%5Bpublished%5D~objecttype~objecttype%5Bthread%5D~thread%5Banswered%5D)

 

Where can I publish blogs about SAP Cloud for Customer?

Please join us on the SCN Cloud for Customer community at (http://scn.sap.com/community/cloud-for-customer) to create blogs at (http://scn.sap.com/community/cloud-for-customer/content?filterID=contentstatus%5Bpublished%5D~objecttype~objecttype%5Bblogpost%5D) and engage the community of experts to help you further their understanding of SAP Cloud for Customer.

 

Where can I publish documents about SAP Cloud for Customer?

Please join us on the SCN Cloud for Customer community at (http://scn.sap.com/community/cloud-for-customer) to create documents at (http://scn.sap.com/community/cloud-for-customer/content?filterID=contentstatus%5Bpublished%5D~objecttype~objecttype%5Bdocument%5D) and engage the community of experts to help you further their understanding of SAP Cloud for Customer.



Where can I document strategic ideas about improving SAP Cloud for Customer?

We have a formal idea management solution deployed to cater to SAP Cloud for Customer at the link https://ideas.sap.com/SAPCloudforCustomer. Please engage with the product management team of SAP Cloud for Customer via the idea management space to provide ideas to SAP to improve SAP Cloud for Customer.

 

What are some other sources of information and engagement that I should be aware of as regards SAP Cloud for Customer?

Some other useful sources of information about, and engagement around, the SAP Cloud for Customer solution portfolio are highlighted below:

SAP Cloud for Customer on SAP Service Marketplace: http://service.sap.com/cloud4customer

SAP Cloud for Customer on SAP Community Network: http://scn.sap.com/community/cloud-for-customer

SAP Cloud for Customer on YouTube: www.youtube.com/SAPCustomerOD

SAP Cloud for Customer on SAP Help Portal: http://help.sap.com/cloud4customer

SAP Cloud for Customer on SAP Idea Place: https://ideas.sap.com/sapcloudforcustomer

SAP Cloud for Customer on SAP Store: https://store.sap.com/sap/cp/ui/resources/store/html/Search.html?pcntry=US&sap-language=EN&catID=&searchText=sap%20cloud…



Please send us a note via this link if you would like to access this valuable content and broadcast information resource.

SAP Cloud for Customer Tenant Landscapes: Determine how many tenants you need

$
0
0

This blog series discusses C4C tenants from the aspect of how many you need and examples of recommended tenant landscapes.    The blog series includes the following topics:

 

1. Determine how many tenants you need - this blog

2. Tenant landscape use case examples

3. Considerations for tenant copies

4. Tenant landscape recommendations with SDK

5. Deployment recommendations with SDK

 

Before we get started, there is a full landscape deck available at business center sme.sap.com site (primarily for partners).

 

 

Determine how many tenants you need

 

When a production subscription of SAP Cloud for Customer is purchased, the subscription includes a production tenant and a test tenant.  Each tenant has a unique URL. Additional test tenants may be purchased as well.

 

tenantMgmt_standardTenants.PNG

 

 

The following summarizes what is delivered with C4C tenants.


Productive Tenant subscription for C4C

  • Provides a single productive tenant
  • Provides a test tenant to support the initial implementation and post go-live application lifecycle management using change projects.  This tenant is often referred to as the 'sandbox' tenant.
  • If you require a fresh tenant, you need to decommission the older one first

Test Tenants

  • You can purchase additional test tenants
  • SAP recommends buying an additional test tenant for every additional tenant you want to have available in your permanent landscape

Considerations

  • If planning integration or SDK work, you should purchase a minimum of one (1) additional test tenant, often referred to as the permanent test tenant.

 

 

Questions to ask when deciding how many tenants you need

  1. Do you know what tenants you purchased?   Default for each production subscription includes production and 1 test tenant.  Any other tenants must be purchased. 
  2. Do have you custom development? Purchase an additional test tenant.
  3. Do you have integration?  Purchase an additional test tenant.
  4. Do you have a phased project with functional changes going on while other end user training and testing is going on?  A second test tenant may be required (4 tenant landscape).
  5. Is there anything specific in business-as-usual to consider additional tenants (for example, complex on-premise landscape where tenants should always connected to DEV/PRE-PROD, etc)?  Additional test tenants may be required. This is an exception scenario and a specific tenant design should be created with the customer and the SAP account team or partner account team so that the financial impact of the required tenants is understood.
  6. Are there organizational reasons for separate tenants for different lines of business with separate projects that require more tenants?  Additional test tenants may be required. This is an exception scenario and a specific tenant design should be created with the customer and the SAP account team or partner account team so that the financial impact of the required tenants is understood.

 

 

In the next blog we will discuss example tenant landscapes.

SAP Cloud for Customer Tenant Landscapes: Tenant Landscape Use Case Examples

$
0
0

This blog series discusses C4C tenants from the aspect of how many you need and examples of recommended tenant landscapes.    The blog series includes the following topics:

 

1. Determine how many tenants you need

2. Tenant landscape use case examples - this blog

3. Considerations for tenant copies

4. Tenant landscape recommendations with SDK

5. Deployment recommendations with SDK

 

 

 

Tenant Landscape Use Case Examples

In this blog we will look at several examples of tenant landscapes.   All of the examples below are actual customer examples, following SAP’s recommendations.


Example 1:  Basic Production Landscape 


This example shows a basic production system.  This subscription includes no SDK and no integration.

 

tenant_example1.PNG

 

The test tenant normally referred to as the sandbox tenant,  can be kept constant, or it can be decommissioned once you are live and you can create a new one as needed.   


Example 2:  Integration to SAP On-Premise


This example covers the scenario with integration to On-Premise.  There is a tenant connected to quality assurance and a tenant connected to production.

tenant_example2.PNG


In this scenario two test tenants are required:  the subscription-booked test tenant and a purchased test tenant.  This enables one tenant to be used to configure, decommission, re-create. The other test tenant keeps a permanent connection to QAS on-premise.  


An important note is that all test tenants are the same.  Meaning, the test tenant received when the subscription was booked could be used for the permanent integration to QAS.  The additional test tenant that was purchased can be used as a sandbox  - the one that can be decommissioned and a new one created at will.  The important point is that for integration, an additional test tenant is purchased which ensures you always have a permanent connection to QAS and you always have a tenant to support configuration changes, test, lifecycle changes, that can be decommissioned and a new one created as needed.  


Example 3:  Integration to SAP On-Premise and SDK


In this scenario there is integration to QAS and PROD on premise, as well as SDK usage.


tenant_example3.PNG

One tenant is reserved for SDK.  This tenant should only have developers.  No business users test or are active on this tenant.  There is a test tenant integrated with quality and a production tenant.   This scenario requires an additional test test. 

 

Example 4:  Integration and DEV test tenant


This example includes a development tenant used only by developers, another development tenant that is connected to SAP ERP OP DEV.  In this example the SDK work is integrated with SAP OP, so extensive testing of this integration is required.  


tenant_example5.PNG

 

Two additional test tenants should be purchased to support this scenario.  This is to support integration to quality and development OP systems.

 

 

In all of these scenarios you notice a separation of the development tenant.  This is very important for consistency of the solution. Anytime SDK or integration is in scope, at least one additional test tenant should be purchased.  Depending on the scenario, you may need two additional test tenants.

 

We have had customers take their test tenant, connect it to DEV on-premise, and then later switch all the connections to QAS on-premise.  This is considered a high-risk approach and is not recommended. The cost of an additional test tenant is less than the risk of changing all the connections and managing the data inconsistencies.

 

 

When doing SDK work, it is recommended the tenants be separated by usage and the usage guidelines should be followed.   The graphic below depicts the recommendation.  This will be discussed again in a later blog on SDK deployment recommendations.    The important point is that all SDK work is done on a separate development tenant that is used exclusively by developers and has only the required scoping and basic setup needed for the development work.

 

tenant_recommendedlandscapewithSDK.PNG

 

In the next blog we will discuss considerations for tenant copies.

SAP Cloud for Customer Tenant Landscapes: Considerations for Tenant Copies

$
0
0

This blog series discusses C4C tenants from the aspect of how many you need and examples of recommended tenant landscapes.    The blog series includes the following topics:

 

1. Determine how many tenants you need

2. Tenant landscape use case examples

3. Considerations for tenant copies - this blog

4. Tenant landscape recommendations with SDK

5. Deployment recommendations with SDK - coming soon

 

 

Considerations for Tenant Copies

 

When creating a tenant, various tenant copy options are available.   The options available will vary on where the tenant is being copied from and where it is being copied to.  For example, the copy could  for a production tenant from test, a new test tenant from production, a new test tenant from test, etc.     All tenant options are outlined in detail in the business center.   The landscape deck in the business center sme.sap.com has details on the topic. 

 

The most common option to select when performing a tenant copy is to copy the solution profile.  The solution profile includes scoping and fine tuning. When a solution profile is copied to create a new tenant, the scope is copied and all fine-tuning settings that have a Repetition Required setting of “No” are copied.

tenantblog_1.png

 

When a solution profile is copied to a new production tenant, the following additional activities automatically occur.  It is NOT possible to trigger these activities when copying a solution profile to a new test tenant.

  • Extension fields and screen layout adaptations made via key user tools are copied as long as there are no extension fields and/or screen layout adaptations already made in the new production tenant
    • Note:  Language Adaptations and Custom Business Objects are not included
  • .Form adaptations are copied
  • Level 0 master data (bank directory, org structure, locations, jobs, product categories, transport zones and transport lanes) is copied to a staging area where the user can choose to import the pre-populated data migration templates or ignore them.

 

 

After a solution profile is copied, all subsequent changes are required to be performed manually in each tenant.

In addition to Solution Profile settings, other objects will need to be moved via Content Transfer, Upload/Download, or recreated manually. 

The Content Transfer feature is used to move adaptations.  Examples include, but are not limited to:  page layouts, code restrictions, key user adaptations such as custom fields.  With the extension fields metadata is also moved.  This includes metadata related to Web Services, Enterprise Search, MDAV, Business Context, External Usage. 

Objects that can be downloaded and uploaded include code list mapping, ID mapping, reports, forms, custom objects, language adaptations, OData service.

Some settings must be manually redone.  This includes business roles, workflow rules, SLA's, mashup others, and other process configuration.

Keep in mind:

  • When requesting a tenant, review in detail the options outlined at sme.sap.com.  Ensure you know where are copying from and to. 
  • The solution profile will not bring everything. 
  • You will need to use the content transfer or downloads to move other configuration.  Some settings must be manually redone.  


SAP Cloud for Customer Tenant Landscapes: Tenant Landscape Recommendations with SDK

$
0
0

This blog series discusses C4C tenants from the aspect of how many you need and examples of recommended tenant landscapes.    The blog series includes the following topics:

 

1. Determine how many tenants you need

2. Tenant landscape use case examples

3. Considerations for tenant copies

4. Tenant landscape recommendations with SDK - this blog

5. Deployment recommendations with SDK - coming soon

 

Tenant Landscape Recommendations with SDK

Early in the project you should determine if you will use the SDK or not.   Keep in mind, if you are using the Adaptation tools to add custom fields, if those fields require business logic, the SDK is required.   For example, if you add a field called "bonus plan" and you need to calculate the field value, or base the field value based on a comparison of other fields, then you need the SDK.

 

When you need the SDK, the recommended landscape is described below.   As mentioned in the previous blogs, an additional tenant is highly recommended.  For SDK, you need a tenant designated as the Development tenant.  Only development work is done on this tenant.

 

 

 

pdi1.png

 

One of the test tenants is designated TEST, the other DEV.   In the TEST tenant you do the main configuration and all testing.    From this tenant the development tenant is created. The DEV tenant is done by requested a solution profile with full copy.    The DEV tenant has only developers an only has basic scoping and whatever is required for the development.  Unit tests are performed in the DEV tenant.  The solution is then deployed to TEST where it is scoped and tested.   This is an iterative process until the solution is accepted and is ready to move to production.     Once deployed to production, the SDK solution is scoped, configured, with cut over to production.

 

The next blog goes into the details of the deployment process with the SDK.


Access Control Management: Basics of access control and business roles

$
0
0

Welcome to the blog series on access control management.  The series discusses access control and business roles.  It provides typical examples of roles and access management.  The following are the blogs in this series:

 

  1. Basics of access control and business roles – this blog
  2. Access Control Management: Access restrictions explained (coming soon)
  3. Access Control Management Example: Global versus local admin (coming soon)
  4. Access Control Management Example: Access forwarding (coming soon)
  5. Access Control Management Example:  Access to transaction or master data access (coming soon)
  6. How to analyse access control issues (coming soon)

 

Basics of access control and business roles

User management, business roles and access rights are maintained in the Administrator work center.  Authorization access can be maintained individually per business user or with the use of business roles. Access rights can be granted by global and/or local administrators.  Business users can only be created for employees or service agents.    It is highly recommended to use business roles for all access controls.  Assigning access controls directly to employees is a higher risk and much more complex to maintain and it does not provide all functionality which is available for roles.

 

 

Access controls within SAP Cloud for Customer has two levels:

 

  1. Assignment of work center and work center views
  2. Instance access restriction based on access context

 

This entire blog series focused on point 2 – access restriction based on access context. It is very important to understand that access context is by business object.  It is not changeable or extensible.  
For example, if the access context for a particular object is employee, then you cannot enhance the access context by adding additional criteria such as sales organization. Access context is explained in more detail in the following blog.

 

 

Business roles can be created for different access restrictions such as sales employees, administrator, manager etc.  Access restrictions can also be maintained for business roles.   An example would be a business role for sales manager, with an access restriction to their territory.

The business role is assigned to business user.  Multiple business roles can be assigned to one business user.  The business role must be in status active. In this case the business user will inherit the access control of both roles (Example: Role1: read; Role2: read&write --> Business User has read&write access)


Changes of the business role trigger an update for all assigned users.  Within a single role you can have various access capabilities.

Business roles are a central part of your security strategy, they can be key for all access.  Many capabilities can be linked to business roles.

 

 

Roles.JPG

 

The preceding graphic shows the most common linkages to the business roles (additional capabilities will follow).  By linking reports, code list restrictions, page layouts, work center assignments, and access and field restrictions to the business role, the business role becomes the key driver to all access permissions for your business users.

 

The next blog descriptions access restrictions in more detail.

Setting up communication system using XML Gateway to C4C

$
0
0

This blog gives you an idea on how to set up a communication system  from ECC to C4C via PI and XML gateway. I worked on the following landscape and though about sharing the experience to make life easy.

 

 

       landscape.JPG

    In this use case data is flowing from on premise ECC system to C4C system via PI and XML gateway.

 

 

To call C4C web service from Client network you need to create one pass-thru service in XML Gateway which will accept the requests from SAP PI system and forwards the HTTPs request to C4C web service using SSL certificates of C4C.

 

To enable mutual SSL handshake between XML Gateway and C4C system, following activities need to be done:

 

  • C4C shared their private key for authenticating clients (This is applicable only when mutual SSL handshake is required, in this case C4C provided private key with a password (C4C private key.pfx and password  ***)
  • C4C shared its server certificate along with root and intermediate certificates, which has to be trusted by XML gateway

 

SAP PI, in turn, also establishes secure HTTPs connection with XML gateway, by adding the gateway’s certificate in its trusted server list and using user/password authentication as shared by gateway.

 

 

Server certificates-For validating the clients we used below 3 certificates of C4C in XML gateway.

 

 

certificate.JPG

SAP Cloud for Customer Tenant Landscapes: SDK deployment recommendations

$
0
0

This blog series discusses C4C tenants from the aspect of how many you need and examples of recommended tenant landscapes. The blog series includes the following topics:

 

  1. Determine how many tenants you need
  2. Tenant landscape use case examples
  3. Considerations for tenant copies
  4. Tenant landscape recommendation with SDK
  5. SDK deployment recommendations - this blog

 

When using the SDK it is important to plan the landscape and how the solution will move through the tenant landscape. This blog highlights key topics discussed in the Deployment Recommendations with SDK presentation.

 

The presentation provides details on the following topics:

  • Recommended Standard Landscape for SDK Development
  • Advanced Options with more than 3 Tenants
  • Solution Template Option
  • Solution and Patch Process in Detail

 

This blog highlights the major points from the presentation.

 

Recommended Standard Landscape for SDK Development

 

 

 

As stated in the previous blogs, the recommended landscape is a separate DEV tenant that is used only for development.   When setting up the development tenant, there are some very important considerations:

  • Development tenant is a normal test tenant which is used solely for SDK developments.
  • Create the development tenant from the (main) test tenant. Usually full copy, to copy the solution profile and test data.
  • The test tenant remains the leading tenant for implementation configuration.

 

Use these tips to avoid obstacles:

  • Do not assign the PDI work center to business users.
  • Do not use the SDK development user for tests in frontend.
  • Do not use the development tenant for integration, data migration preparation, report adoption and master/page Layouts, because of namespace switch in patch process.


Advanced Options with More than 3 Tenants

Whenever a test tenant is purchased, by default it is on the same system as your other test tenant.   With multiple test tenants on the same system, both tenants must have the same version of the SDK  solution.  This may not be what you need.

 

Example: 
In your company you have developers working on a DEV tenant.  There are administration/key users testing on the TEST tenant.  Additionally, you have user acceptance testing going on regionally. The user acceptance testing is done by a group of business users. It could be that while user acceptance test is going on, the key users are testing an updated version of the solution that has not yet been rolled out to the user acceptance testing.  In this situation, the user acceptance testing may be on version 2.0 of a SDK solution, while the developers and key users are testing version 2.5 of the custom solution. 

 

In order to support the previous example, the user acceptance testing needs to be on a different version of the SDK solution.  This requires that the user acceptance tenant be located on a different system.

 

When test tenants are purchased and created, by default the system where they are located will not be known to you.   You need to create an incident when requesting the test tenant and request it be on a different system in order to support multiple versions of the SDK solution.

 

Solution Template Option

 

Some consultants prefer to develop using solution template. This enables you to start coding when the design is not ready. There are disadvantages as well, for example business configuration content cannot be created.  The presentation describes the pros and cons to help you make your decisions.

 

Solution and Patch Process in Detail

 

In order to deploy the solution to the (main) test tenant and production tenant, you need to assemble the solution in the development tenant and upload and activate it in the target tenant. Once the solution is assembled, all further developments and enhancements are done via a patch and must be compatible to previous versions. This means that deletion of objects (BOs, fields, BCOs, etc.) as well as change of data types is not allowed in a patch. However you can add new fields and objects and change the business logic in a patch. When the patch is then deployed to production, the entire solution is deployed to production.  There are no ‘delta’ deployments. The actual deployment is a manual step, consisting of uploading a locally stored solution file to the target tenant and activation of the solution in that tenant. There is no transport mechanism between the tenants.

SAP Cloud for Customer Browser Support Update

$
0
0

sapcloud.jpg

 

Dear SAP Cloud Customer,

 

SAP SE would like to keep you updated about upcoming changes in browser support related to the SAP Cloud for Customer (C4C) public cloud service offering.


Google has announcedtheir plan to remove NPAPI support from Chrome, a change that will improve Chrome’s security, speed, and stability as well as reduce complexity. In September 2015 NPAPI support will be permanently removed from Chrome. Installed extensions that require NPAPI plugins will no longer be able to load those plugins.


Read all about the impact of this announcement by Google, SAP recommendations and how you can engage with SAP regarding this matter to get further clarification at this link

 

Best Regards

SAP Cloud Customer Engagement

FAQs for Installed Base Management in SAP Cloud for Service

$
0
0


Disclaimer: The aim of this document is to provide a better understanding of the installed base management feature in SAP Cloud for Service.
This is not the product documentation and the content
included here may get updated over time.

 

Question 1: What is Installed Base? What is Installed Base Item?

 

Answer: Installed Base is a hierarchical arrangement of items installed at your customer’s location. For example: You can maintain an installed base for Company ABC where your servers are installed. Certain information can be maintained at the installed base header level, for example, Involved Parties, Attachments, Notes and Competitor Products.

 

The following can be added as items in an installed base:

  • Registered Product
  • Product
  • Text

 

Registered Product: It is a unique instance of a Product with a serial ID. It is possible to maintain a warranty for a Registered Product. One registered product can exist only in one Installed Base at a time.

 

Product : An instance of a Product. Same product can be added in multiple installed bases.

 

Text : A flexible category which can represent, for example, a location or a grouping.

 

On the UI, the “Category” field differentiates the types of items. (Technically, an Installed Base item is an installation point of the specific category).

 

An example of Installed Base set up:

 

Installed Base Hierarchy.png

 

Question 2: Is there any limit to the number of levels when creating the installed base hierarchy?

 

Answer: There is no limit to the number of levels that can be created in an installed base hierarchy. However, too many levels may become incomprehensible or difficult to maintain. Decide on an optimal number based on your scenario.

 

Question 3: How is installed base used in the service process?

 

Answer: Installed Base Management provides the ability to create a Ticket from an Installed Base at the header level or at the item level. Certain information (if) maintained in the Installed Base (header or item level) is automatically copied over to the Ticket, for example the customer, contact, service
technician, service technician team and location.

 

The list of all tickets where an installed base or installed base item is included is seen in the TICKETS facet on installed base.

 

Question 4: I see multiple views - Registered Products, Installed Base, and Installation Points. How are they different? When to use what?

 

Answer: Registered Products view was available (under Products work center) prior to Installed Base. Registered Products can be used standalone if you need to track serialized products as individual items.

 

Use Installed Base if you need a hierarchical representation and a consolidated view of installed items.

 

When you enable Installed Base feature, the Registered Products view is automatically enabled and is shown under Installed Base Work Center as well (since Registered Product can be an item in Installed Base).

 

Installation Points has been built to enable replication of ERP Functional Locations to C4C. But it can be used standalone also without ERP integration. Currently this view shows Installation Points of category “Functional Location”. In future, installation points of other categories (product and
text) will also be shown here.

When you enable Installed Base feature, the Installation Points view is automatically enabled.

 

Question 5: Is there any integration with SAP ERP available for Installed Base management?

 

Answer: Replication from SAP ERP is available for the following:

Equipments in SAP ERPare replicated as Registered Products in SAP Cloud for Service.

Functional Locations in SAP ERP are replicated as Installation Points of category ‘Functional Location’.

Information such as Party Information, Notes, Address etc. maintained for both Equipment and Functional Location gets replicated to SAP Cloud for Service.

Please note that only uni-directional replication, from SAP ERP to Cloud for Service is available.

 

Question 6: Can I migrate installed base related data from another system into C4C?

 

Answer: Installed Base and Installation Points (installed base items) migration templates are available that can be used to migrate installed base related data to SAP Cloud for Service.

 

Question 7: Is functional location equivalent to installed Base?


Answer: No. In SAP Cloud for Service, a Functional Location is an Installation Point of category/type “Functional Location” and is shown in the Installation
Point UI.

 

Question 8: I see ITEMS in Registered Product and Installation Point as well, what are these?

 

Answer: The Items in Registered Product and Installation Point show the structure (child items). This is a flat list (no hierarchy) so one level of items is
shown.

In SAP ERP, a functional location can have equipments and other functional locations under it. Similarly, an equipment can have other equipments under it. This is supported in SAP Cloud for Service as well. The registered product can have other registered products as Items.

The Installation point (Functional Location) can have other functional locations or registered products as Items.

 

In SAP Cloud for Service: For a pure registered product scenario (if installed base is not scoped in):

These items can only be registered products.

For installed base scenario:

These are all items (can be registered products, products or text) added directly under this registered product in the Installed base hierarchy.

 

Question 9: What is the “Belongs to Installation Point ID” field ?

 

Answer: The “Belongs to Installation Point ID” field (if filled) indicates that the Installation Point is part of the structure (is a child) of another Installation Point (registered product or functional location)

This field is a hyperlink and will open the parent Installation Point.

 

For example: Belongs to Installation Point ID for registered product Coffee Machine “CM01” shows “21”. When you click on 21, the UI for Installation Point
21 is launched which is a functional location “Floor 1”. The ITEMS facet of Floor 1 shows CM01. This means that coffee machine CM01 is under Floor 1.

 

Question 10: Can Registered Products or Installed Base be added to contracts?

 

Answer: Currently, you can add a registered product as a covered object in a Contract. In future, you will be able to add installed base as well into a contract.

SAP Cloud for Customer (C4C) - My first experience

$
0
0

Recently I have taken part on a C4C Project, one of the first ones in South America region and I have been going through different status that I’d like to share with you as well as some advices that would have saved me a lot of time and, that I hope will help you to speed up your ramp-up into C4C when working as a consultant.

 

Let me first share with you a brief description of my SAP related background; I have been working with SAP CRM for over 10 years as techno-functional consultant, technical leader and, CRM Trainer. Over a year ago, as I was seeing that SAP CRM consulting demands where decreasing in some regions of the world, I had to decide whether to pivot and change (by moving to another area) or to persevere (by keeping my eyes on CRM related areas and learning new technologies). Today I am sure I have chosen the right path! And even better, I am seeing that SAP CRM demand has risen again!

 

In my personal experience, I have had the chance of taking C4C trainings but, as we all know, participating on courses is not the same as having hands on experience and facing specific issues but, it is a very good starting point.

 

In comparison to the moment where I started working with SAP CRM technical side in 2005, there was not much public information being shared by SAP. Nowadays, SAP seems to have changed its strategy as we have several places from where we can gain a lot of knowledge. I personally first started with SAP Cloud for Customer YouTube channel (https://www.youtube.com/user/SAPCustomerOD/videos) and then, jumped into SDN C4C Space (http://scn.sap.com/community/cloud-for-customer). Afterwards, I also took advantage of Marketplace documentation (http://service.sap.com/cloud4customer).

 

For those who want technical insights, it also has very valuable documentation the SAP Cloud Application Studio site (http://help.sap.com/studio_cloud). Also, there is an openSAP course for SAP ByDesign (https://open.sap.com/courses/byd1).

 

However, the most relevant knowledge was provided by the networking generated through SDN C4C Space where I had the chance of meeting new consultants around the globe who have really helped me when I was under complex situations and when I was not facing further alternatives.

 

Some of the biggest challenges I faced where when trying to leverage connection from ERP to C4C through PO as the guide had some inconsistencies which were taken care by SAP colleagues (after raising an Incident). These issues forced me to deeply research and learn to use new C4C and ERP tools. Also, they made me learn things which are not written (and that I am trying to share on several SDN documents). As a friend of mine says, “the best knowledge is gained while suffering”. I am trying to change this phrase by “the best knowledge is gained by accessing SDN C4C space”, hope I can help with it!

 

From my personal and humble point of view, there are some things that seem to be “still a bit green” but SAP is demonstrating, day after day, that their commitment for improving tis is huge and that they are already adding existing OnPremise (traditional SAP CRM) tools and processes into OnDemand (C4C) system. I have personally seen this, after having worked with several C4C releases, after having been in touch with SAP Product responsible and, after having received help from several SAP SMEs while solving open incidents. Also, you can understand this by checking the news for future releases where they improve existing functionalities and, also, add some others which were still not present. I strongly believe that this is going straight forward and that this is the right path!  Meanwhile, while not getting specific functionalities on the standard, this is good for us as where are being forced to explode our creativity in order to solve issues on alternative ways; always adjusting system to customer needs and not the other way!

 

Finally, feel free to mention me on your SDN queries so I can try helping you. I received plenty of help while ramping up and, for sure, I am open to provide the same (and more) to others!

Cloud for Customer (C4C) - Summarizing some experiences

$
0
0

After having written a few documents, I started getting some requests to unify all my documents so colleagues could follow them in a quicker way in addition to the fact that helped me to find my own documents in a quicker manner so, I decided to create this new blog! During my next experiences, I will continue updating it.


1) SAP Cloud for Customer (C4C) - My first experience

This document is about my first project experience working with functional and integration side of C4C. Here I share some feelings and advices in order to help others to speed up their ramp-ups into it.


2) Creating a default port in SOA Management for a Consumer Proxy

This document explains how to create the Logical Port required when leveraging ERP-C4C integration.


3) C4C - Mapping ERP Account Group into C4C

This document explains a complete development for being able to syncronize standard Acount Group from ERP within custom field on C4C; covering development, mapping in PO, customizing, etc.


4) C4C Integration - Filtering Products and Accounts from ERP to C4C

This document explains how to filter Products and Accounts when flowing from C4C into ERP. Also, it gives some insights on how to filter other objects. Finally, it explains how to filter objects on the opposite flow (ERP into C4C).

 

5) Opportunity External Pricing  (Integration with ERP through PO)

This document explains how to setup external pricing between C4C and ERP, going through all the configuration of the 3 systems (ERP, C4C and PO) and, also, explaining how to test it.

 

6) C4C Integration – Debugging remote calls into ERP / CRM

This document explains how to debug on ERP/CRM when doing remote calls from C4C side. It is really helpful when having integration issues and troubleshooting.

 

7) Cloud for Customer (C4C) - Lock Concept

This document explains how is Lock concept applied to C4C, as well as it explains parallel processing..

 

8) Cloud for Customer (C4C) – Organizational Management

This document explains several concepts related to Organizational Management which were making me some trouble and that, after writing them all down, things got a bit more clear as I started understanding differences. Some parts of this blog are copy-pasted from help.

 

Hopefully, I will be updating this blog soon with new experiences!

 

Cheers.

 

Alejandro.


Access Control Management: Access restrictions explained - Access Context

$
0
0
  1. Basics of access control and business roles
  2. Access Control Management: Access restrictions explained  - Access Context (this blog)
  3. Access Control Management: Access restrictions explained  - Restriction Rules (coming soon)
  4. Access Control Management Example: Global versus local admin (coming soon)
  5. Access Control Management Example: Access forwarding (coming soon)
  6. How to analyze access control issues (coming soon)

 

 

The previous blog mentioned that each object is controlled by the access context. This access context is a characteristic of the work center view/business object. In the following screenshot, you can see that the work center view Account has the access context 1015 – Employee or Territory or Sales Data.  

 

0200_AccessContext.png


The access context 1015 is also relevant for Opportunities, Sales Quotes and other business objects. Other business objects such as the product may have different access contexts assigned. The access context is a characteristic bound to the work center view/business object. It is defined by the standard set up of the business object and cannot be changed or enhanced. Hence the access control capabilities for a certain business object works in the defined structure of the access context. That also implies – if there is no access context defined for a work center view/business object a distinct instance base access control setup is not possible for that particular entity.


For custom BOs created with the SAP cloud development studio access control can be inherited from a standard business object through association. In addition it is also possible to define a custom BO specific access control context related to employees or territories.


Example for Access Context:

The work center view “Accounts” has the access context 1015 assigned (Employee or Territory or Sales Data). This implies that the access to an account can (only) be controlled based on the following criteria:


EMPLOYEES directly assigned in the account team --> I have access to all accounts where I am member of the account team (independent of the role assigned); or my manager has access to all accounts of EMPLOYEES of the functional unit (organization) for which he is assigned as a manager.

 

0201_AccountTeam.png


TERRITORY team --> I have access to all accounts which are assigned to a territory I am a member of. Accounts assigned to territories which are sub territories of my territory are also accessible. Please note that the work center territories where the territories can be maintained works with a different access context - 1010 Employee!

0202_TerritoryTeam.png


SALES DATA - This is a new capability introduced with 1508 --> I have access to all accounts which are assigned to a sales area I am eligible for. The assignment of my relevant sales areas can be maintained in the employee master independent of my actual organizational assignment.


0203_SalesData.png

0204_EmployeeSalesArea.png


Read/Write access can be restricted on Work Center View (Business Object) level. 

 

Question:


Consider the following scenario for account Widgets Inc.:

For Widgets, Inc, Violet is assigned as the owner of the account. She is the designated employee responsible. Violet’s business role provides access context to accounts by employee. Violet’s business role provides her only access to accounts that are owned by Peter.

The question is: Can Violet see the account Widgets, Inc? 


The answer is no: Violet cannot see it because access context outweighs the role employee responsible. Even though she is the employee responsible, her access restriction settings in the role assigned to her only provides access to accounts that are owned by Peter. 



Cloud for Customer (C4C) – Organizational Management

$
0
0

Introduction

Organizational Management (OM) is the central source of organizational information in the C4C solution. It is used for modelling the organizational structure and it provides a graphical representation through an organizational chart. In addition, it reflects entities and aspects (legal, operational and functional) of the company. SAP C4C accesses OM whenever business processes require information related to company’s organization.

 

01.png

 

For ensuring an appropriate OM, the following guiding principles exist:

 

- Time dependency: all information stored is time dependent.

 

- Active version vs. Planning version: the system has the ability to differentiate between the planning version and the active version of the organizational information.

 

- Consistency checks: there are some checks which help maintaining OM consistent all the time.

 

- Partial activation: it is possible to activate smaller parts of the organizational structure, while continuing to work with other parts.

 

 

Purpose

The aim of this document is to help consultants to clarify what does each function of the Organizational Management means as they are not detailed.

 

 

Organizational Units

These are the functional units of a company and form the basis of an organizational plan. Depending on how a company is organized, the organizational units may be departments, groups or, project teams.

 

 

Organizational Unit detail in C4C

When working with an organizational unit in C4C, there are several tabs which give meaning and sense to each unit. I will give a deeper detail for: General, Definitions and Functions.

 

 

Tab: General

Following, I will list the meaning of some of the relevant fields:

 

- Org. Unit ID: this is the unique identifier, once the OM has been activated, it is no longer editable.

 

- Org. Unit Name: the value contained on this field is the one that will appear on reports and business documents.

 

- Valid From/To: validity period for organizational unit.

 

- Working day calendar: specifically used for time management and payment optimization.

 

- Org. Unit. Manager: defines the service agent or employee with managerial responsibility over this organizational unit.

 

02.png

 

Tab: Definitions

The following properties are used for defining the organizational unit:

 

- Company: it represents an org. unit that is financially and legally independent, that is not tied to a geographical location, and is registered under business law. It includes all legally registered entities, such as associations, cooperatives, or any other legal persons that release annual financial statements. Each company has an official country of registration and a default currency. Each org. structure must contain at least one org unit that is defined as a company.

 

- Business Residence: it represents a part of your company within a geographic area. The business activity of this business residence is subject to uniform tax processing, its registration with public authorities is unique, and there is only one valuated stock per material for this business residence. A business residence can be, for example, a city or region, even if your company has several locations with different addresses within this city or region.

 

- Reporting Line Unit: it represents an org. unit that has personnel responsibility within the reporting line. If a manager is assigned to the reporting line unit, all employees on the org. unit and below it report to that manager.

 

- Program:  it represents a group of related projects managed collectively to achieve a common goal. The assignment of projects to a program is optional.

 

- Segment: it represents a company area whose business activities result in revenue and expenditure, and whose operating income is regularly monitored for the purpose of assigning resources and evaluating performance. The segment collects the balances of all lower-level profit centers and offers additional financial reports to those provided at profit center level.

 

- Profit Center: it represents a company area for which a separate period-based profit is determined. It is used for evaluating and regulating the activities of the company area in a profit-oriented manner. The profit center provides visibility on profit and loss via reports.

 

- Cost Center: it represents a defined location of cost incurrence, for which costs are recorded separately. A cost center is used in cost center management accounting to collect and allocate overhead costs.

 

03.png

 

 

Tab: Functions

On this tab, customer defined the functions that correspond to a specific organizational unit such as:

 

- Sales Organization: it indicates that the org. unit to which it is assigned represents the head org unit of a sales hierarchy. An example of a sales organization is the head organization in a country, such as domestic sales. The sales organization is also the relevant org unit for defining sales-relevant master data. Sales data in the product and account master can be defined in relation to the sales organization in combination with the distribution channel - this combination is known as the distribution chain. Price lists can be defined based on the distribution chain. In a sales document, such as a sales order or service order, the combination of the sales organization and the distribution channel appears.

 

- Sales: it indicates that the org. unit to which it is assigned is responsible for the processing of sales quotes and sales orders. In sales reporting, sales data is aggregated at the level of sales units. The sales organization is a specific type of sales unit, which is used to head complete areas, regions, or countries.

 

- Marketing: it indicates that the org. unit to which it is assigned is responsible for target group and campaign management, capturing of responses to campaigns, market and competitor information, and leads generation.

 

- Service Organization: it indicates that the org. unit to which it is assigned represents the organization that provides customer service. Below the service organization, customer service units can be defined to represent sub-entities of the service organization. If the services provided are sold to your customers,

you will also require a sales organization.

 

- Customer Service: it indicates that the org. unit to which it is assigned is responsible for the management, monitoring, and execution of services, such as the handling of product inquiries, providing recommendations, and pre- and after sales support. Customer service can be provided by a service desk or by field and in-house service teams.

 

- Strategic Purchasing: it indicates that the org. unit to which it is assigned is responsible for procuring products, identifying and managing sources of supply, and establishing long-term relationships with suppliers. Responsibilities include the creation of requests for quotation, and the negotiation and management of contracts with suppliers.

 

- Operational Purchasing: it indicates that the org. unit to which it is assigned is responsible for the procurement of materials and services from external suppliers. This includes the automation of the procurement process and the handling of purchase requests, purchase orders, purchase order acknowledgments, non-stock materials, and goods and services receipts.

 

- Cash Flow Management: it indicates that the org. unit to which it is assigned is responsible for: Cash and liquidity management, Payment management, Expense and reimburse management and, tax management.

 

- Financial and Management Accounting: it indicates that the org. unit to which it is assigned is responsible for: General ledger, Fixed assets, Cost management and, Inventory valuation.

 

- Customer Invoicing: it indicates that the org. unit to which it is assigned is responsible for: Receivables and Invoicing of customers for the supply of products and services

 

- Supplier Invoicing: it indicates that the org. unit to which it is assigned is responsible for: Payables and Supplier invoicing.

 

- Human Resources: it indicates that the org. unit to which it is assigned is responsible for: Personnel administration, Time administration, Compensation, Payroll, Expense and reimburse management.

 

04.png

Get up to speed with the latest information and news on SAP Cloud for Customer

$
0
0

6th July 2015

Due to the global announcement of SHA-1 certificate deprecation plans and migration to SHA-2 for better security, our current SSL server certificates will be re-issued against SHA-2 Signature Hash Algorithm from a new certificate authority (Baltimore Cybertrust Root).

 

Read More at http://scn.sap.com/docs/DOC-65089

 

 

29th June 2015

We had the distinct pleasure of talking to our customers and partners informing them about the planned functionality that will be available with the August 2015 release of the SAP Cloud for Customer, public cloud software as a service offering, powered by the SAP HANA Cloud.

 

Find all the details at http://scn.sap.com/docs/DOC-63524

 

 

22nd June 2015

Earlier this year we announced SAP Cloud for Customer certification.  SAP just announced a discount available for C4C certification.  The promotion is available now thru  August - so check it out and get certified!

 

Find all the details at Promotional offer for SAP Cloud for Customer certification! 

 


5th May 2015

On May 5, 2015SAPintroduceda new service called “SAPDigitalforCustomer Engagement”...D4C is designed for “your way” - easy to buy, simple to use, robust and scale-able, all for the best price you can get.Buy D4C atThe SAP Store...

FAQ - C4C Tagging and Text Analysis - Hana Text Analysis

$
0
0

This document captures common questions on this topic. These are valid as of C4C 15.05 version.

 

Q1. What is the engine behind text analysis.

Answer - Hana Text Analysis v1.85 (part of SPS 08). Used for  both Tagging(auto-tagging) and Sentiment Analysis(automatic sentiment determination)

 

Q2 - Where is Auto-Tagging used ?

Answer - Used in analyzing incoming Service/Social interactions - Eg social media mentions "Chris Rock is a big fan of iPhone" - Name "Chris Rock" and "iPhone" are tagged for that message. C4C user (agent) can manually change and update these.

 

Q3 - Where is Sentiment Analysis used?

Answer - Used in analyzing incoming Service/Social interactions. Systems detects sentiment and marks these interactions with positive/negative/neutral sentiments.  C4C user (agent) can manually change these.


Q4 - Does engine use dictionaries?

Answer -  Yes engine uses different dictionaries for different languages. These are standard predefined dictionaries.


Q5 - Can customer tweak the standard dictionary or define custom dictionaries? Can customer influence this process?

Answer - At this point, no.  Engine uses standard dictionaries for both sentiment analysis and tagging.

 

Q6 - What languages are supported?

Answer - English, German, Spanish, French, Italian, Norwegian, Portuguese  and Traditional Chinese.

 

 

Related blog - http://scn.sap.com/thread/3761609

Work Distribution Rules for defaulting Owner in Opportunities

$
0
0

This blog aims to discuss how we could use the Work Distribution Rules to default an Owner in the transactions -

Using the Involved Parties of the Opportunities-> Rule "Employee Responsible for Sales" along with a Work Distribution Rule defined for this Rule, this can be achieved

 

Eg: If the Rules for Party Determination in an Opportunity specify that the owner can be determined by the following:

     - Employee Responsible of the Account Team

     - Employee Responsible of the Territory Team

 

 

But, while creating the Account, the data specified in the Account meets none of the above.. say neither an Account Team has been defined with an Owner, nor is there a Territory Team. We still don't want the Opportunity to have no Owner determined. In such a case, using the Work Distribution Rules, one can specify a default Employee here.. Here is how you could do this:

 

1. To ensure that the Work Distribution Rule gets evaluated, you have to enable the associated rulel in Maintain Distributions of the Involved Parties for the Opportunities (Business Configuration -> Fine Tuning -> Opportunities -> Involved Parties)

wd5.gif

 

 

2. Next, ensure that there is a rule that is defined for the "Employee Responsible for Sales".

Go to Administrator -> General settings and locate Work Distribution Rules

WD1.gif

3. Define a Rule specifying the Owner who should get defaulted - Eg: Ulrike

wd2.gif

 

4. Next, to test, create an Account for which no Account Team / Owner / Territory has been defined - so that there is no Owner that can be determined in the transaction

wd3.gif

 

5. Finally, create an Opportunity for this customer - and check if Ulrike gets defaulted as the Owner

wd4.gif

 

Cheers !

Vinita

Viewing all 262 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>