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

Tags in C4C

$
0
0

Whenever a blog is written, or a picture is clicked and shared on a social media, you get an option to tag it. For example, you would tag different pictures based on the location it was clicked at, or the name of person or the event. Similarly blogs are also tagged based on the topic, author, etc. - this blog has been tagged under Cloud for Customer, SAP C4C, tags etc.  So what is tagging exactly ?

 

I would say tagging is like giving a 'nick name'. You remember the nick name and so it makes the search for the object very easy.

 

SAP Cloud for Customer provides the tags feature wherein you can assign a 'nick name'. You can tag a customer, a contact person, an employee, an opportunity or even a feed can be tagged. Any object record can be tagged in C4C. Tags are assigned to describe, and organize your object records.

 

There are two types of tag, you can use - Public tag and Private tag.

 

Public tags are shown to all the users. They can use the tag to search for objects. However, search result will show only the objects authorized to users.

 

Private tags can be used only by you. It's not shown to others user who might have access to that objects. You can create private tag by prefixing the tag by a '*'. For example, you want to tag a customer a strategic customer which cannot be seen by other employees who might have access to customer. You can do that by assigning a tag like *strategic_customer.

 

Points to Note:

  1. Tags cannot contain spaces
  2. Tags are not case sensitive and always appear in the Tags pane as lowercase. For examples, system considers a tag like Strategic_Customer or strategic_Customer or Strategic_CusTOMER as strategic_customer.
  3. You can assign multiple tags to the same object

    

Why should you use tags?

  1. Tags help you organize your data. Say your company sells different types of sensors and you are responsible for a only a certain set of sensors which fit into a mobile phone. You can tag the products, customer who purchase sensors and opportunities for sensors with a tag like - 'mobile_sensor'. This makes it easier for you to search for all the objects.
  2. Tags can also eliminate requirement of creating new fields.

 

You can view the video on how to use tags here.

 

More to Continue….


SAP Hybris Cloud for Customer - August 2016 Release - Planned Timeline

$
0
0

Dear Community,

Please find a visual of the planned timeline of solution release for the planned August 2016 release of the SAP Hybris Cloud for Customer solution. We will keep updating this space with additional information as we get closer to the planned solution release based on the timeline outlined below.

 

1608 Release Timeline.jpg

 

Thank you for your time and attention to this matter.

Use HCP OData Provisioning To Create Fiori Apps.

$
0
0

About this Blog:

 

Currently a lot of customers use their SAP Gateway system in On-Premise mode to expose OData services and host Fiori like applications.
The OData services which are available in their respective Business Suite system are registered on the SAP Gateway system which acts as a hub.

Below is a simple system landscape which is common in recent days.

 

AS – IS System:

1.jpg

 

  Targeted user for this blog:

 

  • Fiori Consultant.
  • Gateway developer.
  • SAP UI5 Developers.

 

     The Problem statement:

 

  • Investment on the infra for the gateway server.
  • Maintenance and upgrade of the gateway software and its associated libraries.
  • Maintenance of security system like DMZ setup.
  • With more IOT devices getting connected and the need of cloud based system is imperative.

 

     Solution (TO – BE System): 

 

  • In order to strengthen and harmonize the cloud-based integration solutions for 'SAP HANA Cloud Integration' and 'Gateway as a Service' we plan to bring these two offerings closer together.
  • 'Gateway as a Service' is now called 'HCP OData Provisioning'.
  • Don’t need an infrastructure on your On-premise to host the gateway related components.
  • Easily integrate your backend services with other Cloud based services like Fiori Cloud Edition, API Management etc.
  • Enhanced security mechanism

 

2.jpg

 

     Pre- Requisites for develop the sample application development:

 

  • SAP Cloud Connector basics.
  • SAP Hana and SAP Hana Cloud Integration Trial
    account.
  • WebIDE basics.

 

     Topics to Cover:

  • Hana Cloud Connector configuration.
  • Getting started with WebIDE.
  • HCP configuration to connect ECC
  • Sample Application development and deployment in HCP
  • Configuration of Fiori FLP on cloud

 

     1. Hana Cloud Connector Installation:

 

      To Download and configure the HANA Cloud Connector use the below link.

      Use the latest version (2.7.2) of HCC to verify the connection status.

 

     https://help.hana.ondemand.com/help/frameset.htm?db9170a7d97610148537d5a84bf79ba2.html


     The Cloud connector runs as on-premise agent in a secured network and acts as a reverse invoke proxy between the on-premise network and
     SAP HANA Cloud Platform

      HCC acts as the bridge between the On-premise systems and the HANA Cloud Platform.

 

     It combines an easy setup with a clear configuration of the
     systems that are exposed to SAP HANA Cloud Platform.

 

    2.Create the virtual system for the business suite system in HCC:

 

     To avoid direct access of the business suite system from  cloud, we need to create the virtual system in HCC- access control.

     The port should be same for internal and virtual host.   All the resource and sub paths of the business suite system Needs to be added.

 

3.jpg

      Note: To Find the Port, execute the sicf TCode in your business suite system àenter the service name as IWBEP and test it A pop-up
     window will be displayed, make a note of the host and port name from it.

 

4.jpg

 

     3.Register the account at SAP HCP:

 

     If you are a new user, Then register for a new trial account using the below link.

     https://account.hanatrial.ondemand.com/

     Once registered --> logon with your credentials.

 

5.jpg

 

 

     4.WebIDE subscription

 

      After the successful registration / Login, please click on the subscription link to subscribe the WebIDE.

6.jpg

 

     Click on the new HTML5 subscription --> enter the WebIDE and save it.

7.jpg

 

  Open the Web IDE by clicking on the application URL link.

8.jpg

 

    This will take you to the WebIDE Tool.

9.jpg

 

 

    5. Configure OData Provisioning

 

       To Enable the ODataProvisioning in HCP Cockpit, Navigate to services and enable the oData provisioning.


10.jpg


     Click on OData Provisioning.

     To Configure the OData Provisioning, click on configure oData Provisioning.

11.jpg

 

 

 

     5.1 Create the Business suite Destination System in HCP Cockpit:


     Click on New Destination and enter the business suite virtual details as per below screen shot.  Then click on Check connection button .You will get the      connection      status as successful.  Don’t confuse this OData provisioning destination with global destination.

 

12.jpg

   Note: If the connection is not successful, then verify the HCC paths & sub paths.

 


    5.2 Role Assignment for the HCP oData Provisioning :

 

     Click on the Roles in the menu and assign your user (without  the word trial) to both the roles (GW_Admin & GW_User) listed in this page.


13.png

 


  6. Launch the HCI – ODP service:

 

  After the successful destination creation and role assignment, you can register the service which is available in your business suite system.

  Navigate to main section of the OData Provisioning and click on Go to Service Link.


14.png

 

     Select the destination system from the Dropdown menu and click on the search icon. You will get all the OData services available in the business
     suite system.  Select the service and register it. In our exercise we have registered the “EPM_RETAIL_SCENARIO_SRV” to list out Product details.

15.png

 

   Once the service has been registered, click on the open service document link, to verify the working status of the registered service.

16.png


   Click on the “Service Name” link to explore the service. This URL will be used when you are building applications using WebIDE
17.png

 


   7. Create a destination for HCI-ODP in HANA Cloud Cockpit

 

     Create a global destination in the HANA Cloud Cockpit for consume the registered services in the HCP.

     Note: The URL points to our HCI-ODP service.


18.png

 

 

 

   8.Create Fiori Application from the registered service:

 

  •      Open the WebIDE from the subscribed application.
  •      Create the project from the Template.


19.png

 

   Select the Template --> project Name -->Select the Cloud system which we have created from the previous step.

20.png

 

 

      Enter the service name and press the load metadata service link.

     You can find all the entity sets for the loaded service will be displayed on the RHS of the screen.

     Click on Next Button.

21.png

 

    Enter the required data binding details.

22.png

 

     Provide values for the remaining section of the wizard and click on the finish button.

23.png

 

     Once you created the project, you can find the App entry in the WebIDE.

     Open the project and adjust your code if required.

     Right click on the component.js / index.html in the application,

     Select Run --> Run As --> WebApp Preview.

     The preview of the app will open it in the new window.

24.png

 

 

 

     9.Deploy the application to Hana Cloud Platform:

 

     Open the WebIDE --> Select the Project -->Right Click -->deploy  --> Deploy to SAP HANA Cloud Platform.

 

     Once application has successfully deployed, you will get the success message.

 

    26.png

 

    10. Register the application in Fiori Launchpad:


      Once the application has been deployed, click on the Register to SAP Fiori Launch Pad button.

     ( or )

      From the WebIDE -->Deploy --> Register to SAP Fiori Launchpad.

      Enter below details like Application Name, Tile Details, Group  --> Next  --> Finish.

 

 

     11.Configure the Fiori Launchpad:

 

         Subscribe the "flpportal" (Fiori Launchpad Portal) in your HTML5 application for create your own sites.

         Click on the Application link

       31.jpg

          This is place where the application tiles / Catalog / Group will be placed.

    32.png

 

      Create the required Fiori catalogs, Tiles, Roles, Groups and assign the deployed application.

 

 

     12. Access the Fiori Launchpad :

 

      Click on the site settings URL to access the Fiori Launchpad.

    33.png

 

 

         You can find all the configured application in the FLP.

     34.png

 

          Click on the respective Tile to navigate to the application.

  

          35.png

 

        About The Authors:

 

          Julian Bellarmin & Arun Santhanam working as SAP Mobility Consultant in TechMahindra and involved in Fiori implementation for various region                customers. Have experience in SAP UI5 ,SAP Fiori , SAP HCP & IOT related applications.

Reporting @ C4C

$
0
0

Welcome back! This is the second blog in our Analytics Series.

 

Refer the link below for previous blog

 

http://scn.sap.com/community/cloud-for-customer/blog/2016/05/20/derive-business-insights-using-c4c-analytics

 

In this blog we will cover the features that area available to a Key user while he/she is working on reports in C4C.

 

Below is the list of actions available to key user:

  • Create an assign reports to work centers and roles
  • Create views and selections
  • Mark selections as default for report or view
  • Enable hierarchy on reports
  • Structure tables for hierarchical view
  • Create report to report navigation and thus pass filters and navigate between reports
  • Exception and Condition based reporting
  • Maintain field specific settings e.g. Sorting, Scaling, ID/Description display, Result rows (sub-totals and totals) etc.
  • Send report via e-mail or Export to Excel
  • Create excel based reports
  • Publish reports on home page

 

Most of the features listed above are also available to end user. Below are some features that are exclusively available to the Key user.

 

Enable Fiscal Year based reporting

 

System provides you a lot of flexibility to choose from standard available fiscal years or create your own fiscal year for reporting.

You can also configure different settings for each year. E.g. If your Fiscal Year ends on 3rd Sat of Dec then the date would be different for each year. The system provides you flexibility to choose different start and end dates for each year.

   

You can specify period details and give your own description to these periods.

 

Blog 2 image 1.jpg

 

You need to enable Fiscal year based reporting in scoping and then make these settings in fine tuning.

 

Configure Actions


As an Admin you can control what actions user can perform while working with reports. E.g. if you do not want your users to download reports to excel you can control that.

 

Blog 2 image 2.png

 

 

You can configure following actions:

  • Download
  • Send
  • Open in excel
  • Add fields or attributes

 

Buffer Hierarchy


If your end users work a lot with hierarchy, you can buffer hierarchy to make these reports more performant. This feature pre-calculates hierarchy and ensures data is ready before end users execute report.

 

blog 2 image 3.jpg

You can schedule the buffering job based on your business requirements.

 

Broadcasting


Broadcasting can used to email regular reports to your users. Broadcasting is available for both reports as well as dashboards.

 

 

Blog 2 image 4.jpg.png

 

 

You can choose from HTML, CSV, URL or XML formats available for broadcasting.

 

System provides you flexibility to schedule these broadcasts or execute them on ad-hoc bases. Logs are available for you to analyze the job execution.

Blog 2 image 5.png

 

 

 

Maintain translation

You can use language translation tool to maintain translation of report names.

 

Embed report in business object

For contextual analysis you can embed reports on BO facet. This can be done using KUT tool.

 

blog 2 image 6.png

 

Please note this blog only talks about report specific features. A key user can do a lot more using Business Analytics workcenter.

 

See you again next week when we will talk about dashboard creation.

SAP Cloud for Customer: How-to identify cold browser scenario

$
0
0

Browser caching is a common technique used to optimize performance of web applications. In SAP Cloud for Customer, we cache the following at the browser level: HTTP statistic assets - like images, CSS files, Java Scripts, etc. and screen designs aka. Floor Plan metadata. Floor Plan metadata is the heaviest asset. This cached data is persisted for 14 days within the browser cache to improve performance and reduce network traffic. When browser cache is cleared all static assets are removed and the browser has to retrieve them from the server increasing network round trips and possible impact by poor network conditions, etc. which at the end represent higher response time and poor user experience.

 

Using HTTPWatch’s Basic Edition (free version - Download | HttpWatch), it is very easy to identify cold browser scenarios (with empty browser cache). Basically most of the GET requests in SAP Cloud for Customer should normally be cached at the browser and if we see GET requests that get sent to the server rather taken than from the cache - this will indicate a cold browser scenario.

 

Screenshot below shows an example of cleared cache. We can observe GET request, or several GET requests (Method column=GET) that went all the way to the server (Result column =  ‘200’). In this specific case we are requesting screen design from the server (floor plan metadata).

 

5-9-2016 7-07-13 PM_2.jpg

 

The following screenshot shows the same step executed with static content cached (GET request has result column = ‘Cache’). We can see that request taken from the cache is very fast and took just 44 ms compared to 2.5 seconds before.

5-9-2016 7-07-54 PM_new2.jpg

 

As you can see performance impact is very significant just for one GET request for floor plan metadata. The data received over the network is also significant - 232913 bytes compared to 0 when it is taken from cache.

 

In case you see cold browser behavior all the time (after the first time use) then, there could be a problem with the cache settings in your browser or IT maybe deleting the same via an Active Directory rule.

 

Verify that the browser cache is not deleted when it is closed. The following Internet Explorer configuration controls this behavior.

5-19-2016 9-38-51 AM.jpg


Verify with your IT department that there are no active directory policy rules, which clears browser cache.

 

Example: Microsoft Internet Explorer settings

 

Please navigate to:

User Configuration> 'Administrative Templates'> 'Windows Components'> 'Internet Explorer'> 'Internet Control Panel'> 'Advanced Page' - 'Empty Temporary Internet Files Folder when browser is closed'

 

Verify that browser cache settings are optimal.

5-19-2016 9-44-30 AM.jpg

 

 

For more details of recommended browser settings, refer to the following link:

https://cp.hana.ondemand.com/dps/d/preview/4343596dbae042569562d267650aa3da/1605/en-US/frameset.html?13cdb6d0cc1b456389fedb7ad186c192.html



SAP Cloud for Customer: How to troubleshoot sub-optimal reports performance

$
0
0

SAP Cloud for Customer comes with its own analytical reporting features, capabilities and strengths. These capabilities should not be compared with other primary (independent) reporting / analytical tool, proper evaluation should be done to design and implement each business reporting use case optimally.

Inefficient report or data source modeling may result in extremely slow report performance.

 

Here is a simple example of how report design can affect performance.

 

Using HTTPWatch’s Basic Edition (free version - Download | HttpWatch), it is easy to see hints for sub-optimal report design.


HTTP Watch trace for custom built, non-optimal report:


The Red part in Time Chart column for POST request is Wait time. Wait time is the idle time spent waiting for a response message from the server. This value includes delays introduced due to network latency and the time required to process the request on the web server. We can see high server response time (~47 seconds) as well as high number of GET requests (which is status check requests).

 

5-18-2016 3-21-21 PM.jpg



First we have to check based on which data source report is built. In BUSINESS ANALYTICS work center we search for report name and in search results we get data source name.


5-18-2016 10-30-45 PM.jpg

Now we can review specific data source to see how it is built. In BUSINESS ANALYTICS work center we search for data source and go into EDIT mode.

5-18-2016 10-38-20 PM.jpg

In EDIT mode we see which fields and data sources are used.

5-18-2016 10-40-19 PM.jpg

Anchor data source is Opportunity Funnel (standard), joined via Inner Join with data source Opportunity Header and Item (standard).

In this example customer has built report based on customer designed Join Data Source. Join Data Source was based on two SAP standard Data Sources - Opportunity Funnel and Opportunity Header and Item. After reviewing the report results and available data sources, we have identified that the same data can be retrieved using just one SAP standard Data Source (Opportunity Funnel), and performance got improved.


HTTP Watch trace for re-designed report to improve performance:

5-18-2016 3-22-46 PM.jpg

 

We can see that performance has improved from ~47 seconds to ~2.5 seconds with adjusting the report design. This is basic and simple example of how inefficient design can impact end user experience. Of course there will be more difficult cases to analyse and optimize.

 

Before building custom reports or data sources always investigate possibilities of using SAP standard data sources or reports. If using SAP standard reports is not an option model and design reports based on the following best practices.


Join Data Source modeling best practices:


Inner Joins are a preferred approach.

Avoid joining multiple Data Source (DS). If unavoidable, for inner join, use them together in one DS

Left Outer Join should be avoided, if unavoidable can be joined separately, after Inner Joins.

The leftmost data source (Anchor):

  • Should be the one that returns least number of unique records
  • Should ideally be the source of report’s mandatory selection conditions

For generic requirements please provide SAP a feedback for evaluation if it can be delivered as standard DS in future releases.


Report modeling best practices:


If a field is available in DS directly add it through report wizard instead of using ‘Add Fields’.

If a field is not directly available in a DS consider using ‘Add Fields’ before joining.

If possible, reports on join DS should have selections from all data sources used in join.

It is recommended to use not more than one hierarchy in a report.

Avoid using negative selection conditions.

For detailed level reports add mandatory selections. Consider using relative selects.

Reduce report drill down to required fields only. End user has an ability to add fields to drill down and save their own views based on their requirements.

Avoid using column drill down.


Testing best practices:


Testing should always be done in  a smaller parts

Test data should be set up for all individual data sources (part providers)

Testing for the complete scenario with multiple and complex join should be done as last step

First, each part provider should first be tested with a respective test reports and right selection conditions

Once the lower level part providers are tested, the overlying hierarchy of joins can be tested in step by step manner

  • This helps to identify the missing records early in the chain
  • It gives clues if the joins are incorrect
  • Data setup is not as expected

Once the lower level part providers are tested, the overlying hierarchy of joins can be tested in step by step manner

 

Additional information:

 

Anant Ahuja talks about and demonstrates Best practices for SAP Cloud for Customer Join Data Source Creation and Usage in the following video. Conversation transcript for best practices session is attached to this blog.

 

Business Analytics Guide is available here:

https://cp.hana.ondemand.com/dps/d/preview/cab8d3fba22647dea4f6f162f38bd519/1605/en-US/frameset.html

Use this guide to find more details about how to apply the rich analytic capabilities of SAP Cloud for Customer. You will find information about designing reports, KPIs, interactive dashboards, and more.

How to identify potential network problems in C4C using HTTP Watch

$
0
0

It is possible to identify some type of network problems and information that could be very useful for further network analysis using HTTP Watch which will help, by example:

 

  • Long Send times. “Send is the time required to send the HTTP request message to the server and will depend on the amount of data that is sent. For example, long Send times will result from uploading files using an HTTP POST” (ref. http://help.httpwatch.com/time_chart.html)

 

This is an example of a trace that showed high send time and this was observed during the refresh of the ticket list.

                

                    HTTPWatchTrace1.png

 

 

On the previous example, it is observed that the first trace took 22 seconds, the upload bandwidth was 0.001Mbps compared to the second trace that only took 0.004 seconds where the bandwidth was 8.1Mbps.

 

  • Long Receive times. “In the same way that we could have long send times we can also have long receive times. Receive is the time taken to read the response message from the server. This value will be depend on the size of the content, network bandwidth and whether HTTP compression was used” (ref. http://help.httpwatch.com/time_chart.html).

 

 

                         HTTPWatchTrace2.png

 

 

The example above shows a very poor bandwidth of only 0.0003 Mbps for download.

 

  • Long TCP connections. “Connect is the time required to create a TCP connection to the web server (or proxy). If a secure HTTPS connection is, being used this time includes the SSL handshake process. Keep-Alive connections are often used to avoid the overhead of repeatedly connecting to the web server” (ref. http://help.httpwatch.com/time_chart.html).

 

This is another indicator of a potential problem in the network which will impact the user experience.

 

                         HTTPWatchTrace3.png

 

 

The previous example shows a very bad case where the connect time was 7.8 seconds.

 

 

This could happen between the browser and the proxy, the browser and Akamai or the browser and the SAP load balancing depending on the network configuration.

 

This is another indicator of a potential problem in the network, which will influence the user experience.

 

                         HTTPWatchTrace4.png

 

 

The previous example shows a SSL Handshake of 2.8 seconds, which at the end will impact the end user experience.

 

  • Long blocked times. “The Blocked time includes any pre-processing time (such as cache lookup) and the time spent waiting for a network connection to become available. IE 7 and Firefox 2 will only create a maximum of two concurrent network connections per host name (i.e. www.microsoft.com and will queue up requests until a network connection is available. Often the Blocked time is the most significant factor in the download time of images embedded in a web page” (ref. http://help.httpwatch.com/time_chart.html).

 

Newer browsers support more concurrent connections but all have limits.

 

It is important to mention that this could be caused by a network problem but also by a computer problem, in order to try to reduce the variables is recommended to use another browser and see if it behaves the same or start the browser in safe mode to remove the noise cause by add-on (long block times could also mean a slow computer or device).

 

                         HTTPWatchTrace5.png

 

 

The example above we can see block times of over 500 milliseconds with apparently no other parallel HTTP request happening, which could be a good indication that something is not correct in the PC or the network.

 

  • IP of host to where PC/browser is connecting. Following the same scenario from the send time example showed before and after realizing that browser took almost 23 seconds to send only 3.9 KB of data what is important is to know to who the browser was sending the data

 

Within the HTTP Watch Studio selecting the request that has the long send time under the “Stream” tab we can see the IP of the host to where the browser send the data, in this case is 10.3.0.228

 

Normally this will either be the IP of the Akamai server, SAP load balancing (when Akamai is not active) or the forward proxy.

 

                         HTTPWatchTrace6.png

 

            

As it was identified before the IP which is receiving the data from the browser is 10.3.0.228, which means it is private IP and for that reason it can be deduct that there is a on premise proxy being used and the long send time is within the customer network, from the PC where the browser is running to the forward proxy

 

  • Other Scenarios. Long DNS Lookup, browser exceptions, or others could be catch and it will depend if the browser detects a network error like ERROR_INTERNET CONNECTION_ABORTED, ERROR_INTERNET_NAME_NOT_RESOLVED, ERROR_INTERNET_CONNECTION_RESET, etc.

 

                              HTTPWatchTrace7.png

How to idetify high network latency and bandwidth within SAP Cloud for Customers

$
0
0

Perform network testing using the SAP Cloud for Customers network diagnostic tool. Within SAP Cloud for Customer we have we have a small tool which measure the HTTP latency and bandwidth from the browser all the way to the tenant at the application layer level. This tool can be access using the following URL:

 

https://myXXXXXX.crm.ondemand.com/sap/public/ap/ui/repository/BYD_COD/Common/Diagnostics/diagnostic_tests.html

 

This tool offers two test options:


  • Start Latency Test. This option executes 10 HTTP latency tests and then offers the average latency for the 10 tests. This type of test should be executed multiple times during the day to get multiple samples and capture multiple readings throughout the day for the network latency

 

               Latency1.png

 

 

  • Start Download Test. This option test the download bandwidth and the latency giving samples for five executions. This type of test should be executed multiple times during the day to get multiple samples and capture multiple readings throughout the day for the network bandwidth

 

               Latency2.png

 

 

How to interpret the information from these two tests:

 

  • HTTP Latency Test. In general the average latency should be less than 250 ms, the bigger this number is, the bigger the overhead in performance and impact on end user experience. Also if we see sporadic increase, this could mean a high jitter and with this a symptom of some other kind of problem like bandwidth congestion, overhead in forward proxy, overhead in some network component within the path used to connect to the SAP Cloud System. The following example shows a sudden increase in latency, which if we see this happens constantly this for sure will present a problem

 

               Latency3.png

 

                    The previous example clear shows a problem where the average latency shows 1.1 seconds with even one reading which was over 6.4 seconds.

 

  • Bandwidth Test (Download Test). As it was mentioned before, bandwidth is a factor relevant to the type of applications, number of user and type of activities, which make use of this share connection. In general bandwidth of 1Mbps could be enough for a small trial implementation as a minimal recommendation, in some cases if not other activities are done at least 0.5Mbps (should be enough but it will not provide the best performance). By example the screenshot below shows a download bandwidth of less than 0.5 Mbps which could start causing degradation of performance

 

                   Latency4.png


How SAP Cloud for Customers could be affected by network problems

$
0
0

SAP Cloud for Customer as a Software as a Service solution is accessible over the Internet from anywhere over the world by either browser, mobile applications, web services, and others,

 

The user requests from the browser or others have to travel through multiple networks including the user private network, ISP public network, Internet public network and SAP Datacenter network to get to the Cloud for Customer servers to be process.

 

As the number of components, networks and geographies increase, the probability of network failures increase as well and with this the end user experience or performance of the SaaS solution could be affected.

 

Different network conditions could influence the performance of Cloud for Customers, they could be consolidated in the following two areas:

 

  • Overhead caused by network conditions. In this case multiple factors either cause by hardware or software problems, or actual overload or even operator errors could present different type of symptoms, by example but not limited to:

 

    • High Network Latency. First lets define network latency, it is the time that it takes to send one network package to get to the receiver, which also in some case is the time that it takes for the package to return to the sender and in this case is called round trip time or RTT.

 


Main1.jpg

In SAP Cloud for Customers we have in-tenant embedded tools which helps to measure latency, details on how to use this could be found here. There could be multiple reasons because high network latency and some of those are:

 

      • Inefficient path. In the Internet, routing policies and protocols are based in number of factors, which sometimes are not related with performance. The protocol, which makes the Internet works, is called BGP (Border Gateway Protocol), but it is not the only one. BGP is a protocol that exchange routing information between gateways as known host that can be reached, the exchanged information could contain cost associated the path and some other attributes that are used to determine the best available route. This protocol like some others, allow high level of configuration which could cause inefficiencies in the routing, which finally could cause the network packages to travel longer or through busier networks which finally will cause high network latency

 

      • Distance. Network packages have to travel from one location to another and they could travel at the speed of ~124000 miles per seconds, around 62 miles in millisecond for a RTT, the more the package has to travel the longer it will take and the higher the network latency will be, pure physics

 

 

      • Busy networks. Queuing effects could be observed during the travel of the package over the network, usually over the Internet the package has to travel over several public and shared network components, which are interconnected, one busy link could be the main factor determine the increase in network latency. When a package arrives to a network component (router, switch, etc.), the package has to be process and re-transmitted, because the network component has a limit of package(s) that can be process and if the packages arrive faster that they can be process, they will be put into a queue and the processing time will increase. Sometimes when those queues get over flooded, network packages get discarded which means “package loss” and within the TCP protocol, the packages will need to be retransmitted, this behavior could cause a domino effect since now multiple devices will have to process and queue more packages. In general, high latency and high package loss together could cause severe slowdowns in network communications. There is another factor called jitter, when there is too much variation in network latency the jitter will increase and this will be a sign of problematic network connections (jitters is defined as the difference between network latency from package to package)

 

  • Low Network Bandwidth. Bandwidth refers to how much data can be transfer from one point to another in a set amount of time. The bigger the bandwidth the more amount of data can be transfer in less time. The same becomes a factor where multiple applications or users use the “pipe”, here concurrency, the type of application and amount of data that is uploaded or downloaded from the Internet will be the factors that determines how big this bandwidth has to be. If the bandwidth becomes a bottleneck, it will slow down the throughput and with this the response time, think in a highway during rush hour, at that time we might be in a bumper to bumper situation we will be driving at 30 mph, while on the same highway in another moment we could probable drive at 70 mph.

 

 

          Main2.jpg

 

Bandwidth will always has limitation and it is also important to understand that the upload and download available bandwidth could be different. SAP Cloud for Customers has an in-tenant tool which can be used to calculate the bandwidth, more details are here.

 

  • Configuration issues that cause overhead. There are different configurations factors that could cause overhead to the response time, some of those could be but not limited to:

 

    • DNS Configuration. Cloud for Customers uses product from our partner company Akamai to accelerate the traffic over the Internet. This product relies of Geolocation of the DNS server, which resolves the Cloud for Customer DNS tenant name to an IP of an Akamai server geographically close to the DNS server. This is to provide the best routing from that region where the user is connecting to the SAP datacenter. For the user to take full advantage of this feature, it requires to have the DNS server and the user in the same geographical area. A common problem is where the user is using a DNS server which is located in a different geographical region to resolve DNS queries, in those cases the DNS server will resolve the Cloud for Customer tenant DNS name to IP close to the DNS server but not necessarily to the user, examples are where a user from Europe is trying to access a SAP Cloud for Customer tenant in Europe and is using a DNS server in America, in this case the user from Europe will receive an IP from a Akamai server in America forcing the user to connect from Europe to the Akamai server in America to then connect to the SAP Cloud for Customers tenant in Europe, causing considerable network overhead. One method on how to identify if the DNS resolution and TCP routing is happening under the same region is explained in this blog:

 

    • Overhead cause by forward proxies. Some forward proxies either OnPremise or in the Cloud have showed to cause overhead while using SAP Cloud for Customers, in most cases we have observed high TCP times, SSL handshake times and sometime even high send or receive times. Some ideas on how to identify these type of issues with a HTTP tracing tool like HTTP Watch is explained here

 

 

    • Overhead caused by last mile routing. In some cases IP routing is not correct in the last mile, either within the customer private network or from the customer network to the Akamai sever (the last mile), or if Akamai is not enabled to the SAP Data Center. Some ideas on how to identify this problems is explained in this blog.

 

 

Main3.jpg

How to validate routing of last mile in the context of SAP Cloud for Customer

$
0
0

It is possible to validate routing of last mile, using the command “tracert” to identify the route that is used to connect to the Akamai server and with this understand if the network packages are traveling to other regions or countries which could be adding overhead and might require closer look of the network administrators or ISP. By example:

 

  • Use the tracert command to get IP for each of the hoops or routers involved in the routing

 

LastMile1.png

 

 

 

  • Once we have the IPs we can use  any of the IP geolocation services mentioned here to get the location and use information from the tracert to look into the latency

 

IP

Locations

Latency (ms)

  1. 192.168.1.1

Private

2

  1. 10.0.0.1

Private

6

Unknown

 

 

  1. 68.85.251.1

Houston

18

  1. 68.85.244.173

Houston

15

  1. 68.85.87.197

Houston

27

  1. 68.86.92.61

Dallas

36

  1. 68.86.89.250

Stemmons

23

  1. 50.242.150.138

Chicago

25

  1. 23.203.61.191

Cambridge

27

 

It is important to mention that different tools use different geo database and results could be different due to outdated database, it is recommended to get geo location information from different sources.

How to check proper DNS resolution based in gelocation for SAP Cloud for Customer

$
0
0

Check of proper DNS resolution is important since SAP Cloud for Customer take advantage Akamai network acceleration solutions to improve the path of the middle mile, but still the first mile could be a problem if the DNS configuration is not set correctly. To verify this, we need to follow these steps:

 

  • Identify IP of Akamai server. Commands like “nslookup” or “dig” can be used to query the DNS server and get IP of the Akamai Edge Server, by example

DNS1.png

 

  • Identify geolocation of Akamai server. There are multiple web sites that offers geo location information for IPs from different databases, some of these tools are free, and maybe some might have outdated information. The recommendations will be to retrieve the information from multiple of these web sites to validate the accuracy. The following is a list of web site which offer geolocation information for IP:

 

https://www.iplocation.net/

https://www.ultratools.com/tools/geoIpResult

https://www.maxmind.com/en/geoip-demo

https://geoiptool.com/

 

DNS2.png

 

  • If require, identify IP used to access Internet. There are different methods to identify the IP used to connect to Internet, one simple way is by searching in Google, searching the following term “what is my ip” this method will show you the public IP used to connect to the InternetDNS3.png

 

  • If require, identify geolocation of public IP. The same steps follow before to get the geolocation of the Akamai server can be follow to get the geolocation of the IP used to connect to the Internet
  • If require, identify IP of DNS server. Using commands like ipconfig /all, nslookup, or dig is possible to identify the IP of the DNS server, sometimes it might be required to ask the network administrator for this information
  • If required, identify geolocation of DNS server base in IP. The same steps follow before to get the geolocation of the Akamai server can be follow to get the geolocation of the DNS server based in the IP

 

Once we have the IP and geolocation of the Akamai server, DNS server and from where we are connecting to the Internet, it will possible to determine if all of them are located in the same region and further more validate that the end user is located in same region as well.

How To Analyze Customization Impact On Server Time

$
0
0

Tools like HTTPWatch and In-Tenant Performance Reporting provide a limited breakdown of the overall processing time into client, network and server. There are however no further details about the server processing, how customizations and integrations impact the performance.

 

Till standard reports are available, this can be accomplished via a custom report based on the same data source that powers the In-Tenant Performance Reporting. That data source provides details about times spent in web service calls, workflow execution and SDK code (custom code developed in the SAP Cloud Developer Studio, also referred to as PDI).

 

Use the BUSINESS ANALYTICS work center to create a new report based on data source “(Beta) Response Time Analysis”:

NewReport.jpg

 

Use the default selection which already includes workflow execution, PDI as well as Web Service processing times:

NewReportSelectKeyFigures.jpg

 

Complete the report creation and start the analysis:

ReportAnalysis.jpg

 

The report allows you to analyze processing times based on date/time, work centers and other characteristics. Processing time spent in SDK (PDI) code, web services and workflow rules is part of the overall Server Time.

 

If there are for example problems with the execution of web service calls to due long processing times in a remote system, the report would show high “Web Service Processing Times”:

WebService.jpg

 

In similar fashion, SDK (PDI) code and workflow processing will also show up in the report:

PDI.jpg

 

Workflow.jpg

 

In case the total server time is above acceptable levels, the individual components contributing to it need to be analyzed in detail.

Task Distribution in C4C

$
0
0

In this blog I am focusing on the unassigned approvals,

 

As we all know approval process gets triggered on the back of a transaction based on the condition set in the steps.

Normally all the assigned approvals can be seen on the approval tab page in the transaction.

Lets say by some reason the approval has been created and approver hasn't been determined due to missing employee manager details,

 

In this case we can see all the unassigned approvals as unassigned items in  Task Distribution

 

 

Got to Application user management =>Task Distribution

Task distribution.png

 

 

Select Unassigned Items in the filter

Unassignment item.png

 

 

Click on Go

Go.png

 

If you want to assign you can click on Action =>Assign items

assignitem.png

 

 

 

If you want to approve directly you can by clicking on Open Details

open detail.png

And click on approve

 

approve.png

E2E connectivity test for ERP and C4C using HCI

$
0
0

There are many documents and posts on how to setup up and configurate the communication between ERP and SAP Cloud for Customers using HANA Cloud Integration, but there is a lack of documentation on how to test it.

 

For that reason i created two documents on how the communication can be tested:

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

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

 

The incoming connection from SAP Cloud for Customers to ERP is more complex than the outgoing connection from ERP to C4C, as there is the Reverse Proxy (SAP Webdispatcher) as an additional component involved.

 

The connection tests can be really helpful to find and identify problems. So the communication can be tested until it finally works.

 

For configuration purposes these documents have been a good help:

How to Configure Integration between SAP ERP and SAP Cloud for Customer using SAP HCI : https://websmp102.sap-ag.de/~sapidp/012002523100014621522014E/SAP_BP/RDS_CFC_ERP_CFC1411V3_XX/Documentation/How-To-Guide-ERP-HCI-C4C-1411.pdf

Technical Connectivity Guide for OnDemand - OnPremise Hybrid Applications : https://websmp107.sap-ag.de/~sapidb/012002523100002936972016E/TechConnGuide_1602.pdf

How to Configure SAP Web Dispatcher as Reverse Proxy for SAP CRM or SAP ECC  using HANA Cloud Integration :https://scn.sap.com/docs/DOC-51947

Interactive Dashboards

$
0
0

Welcome back!

 

This is the third blog in our Analytics Enablement series. Please refer to the link below for previous blogs:

 

Derive Business Insights using C4C Analytics

http://scn.sap.com/community/cloud-for-customer/blog/2016/05/20/derive-business-insights-using-c4c-analytics


Reporting @ C4C


http://scn.sap.com/community/cloud-for-customer/blog/2016/05/27/reporting-c4c


In this blog we will talk about Interactive dashboards.


Interactive dashboards allow you to club related reports together and view them side by side. You can also establish connection between reports which can be used to pass filters during analysis. Key features of interactive dashboards are as below:

  • Easy to consume and configure
  • Guided wizard to create and publish dashboards
  • Define connections and pass filters between reports
  • Flexibility to define layouts
  • In-place interactivity and drilldown
  • Transactions quick view
  • Launch transactions from dashboard
  • View data in the form of chart and tables
  • Open reports on web/excel for further analysis from dashboard


As a key user you can work in design mode. This will help you edit the dashboards without waiting for it to launch.

 

Blog 3 image 1.jpg

 

SAP provides guided wizard for easy creation of dashboard. In case you have enabled Role Based Analytics you can assign dashboard to the various roles.

 

Blog 3 image 2.jpg


System provides you a flexibility to define the layout. 3x3 grid gives you option to add upto 9 reports in a dashboard. You may also choose to expand reports to multiple columns or rows. This can come very handy when you are adding a tabular report to dashboard.


To define layout drag and drop reports from available list to the left pane.


Blog3 image 3.jpg

 

You can define connections in step 5. These connections will be used to pass filters between reports. Make use of Auto-Mapping to allow system to propose possible connections.

 

blog 3 image 4.jpg

Dashboard Analysis


Execute Mode can be used to analyze data using dashboard.


Please Note - End users can only work on Execute Mode.


In-place drill down allows you to slice and dice data for further analysis. Dashboard allows you to view data in different visualizations e.g. if you see a particular month is not performing well you can add Employee responsible, Account and Opportunity detail and change char to table to get further details.



Blog 3 Image 5.jpg

 

 

Quick view of transactions help you analyze details without leaving dashboard.


blog 3 image 6.jpg


 

Interactive dashboard is a very powerful feature. It helps you to get complete picture of your business.


Our customers love it. Have you tried this feature yet!


Now I leave you here to explore dashboard further. We will meet next week again for our last blog in this series.


SAP RTC by Genband Available for Productive Use

$
0
0

A C4C User can now communicate real time with another C4C user through Genband SAP RTC.  This is available for productive use since 16.02.


Following Use Cases supported -

  1. Launch - As a C4C user, I can click on on a tool-bar icon to open a real-time Genband RTC window
  2. Presence - As a C4C user, I can see who is available/present in Genband RTC window
  3. Communicate - As a C4C user, I can select available user and initiate text chat, video call, and audio call in Genband RTC window

Setup -

  1. As a C4C Admin, I can automatically provision a Genband user. This happens automatically when user is assigned Genband workcenter view
  2. As a C4C Admin, I can provision two types of Genband Users - Basis and Advanced. Basic gets chat and presence. Advanced user get chat, presence, phone and video. 
  3. As a C4C Admin, I can review/accept user agreement terms. This is part of the configuration.
  4. As a C4C Admin, I can select Genband's data center location. This is part of the configuration.


Admin Guide - What's New in SAP Cloud for Customer


More to Come - Mobile functionality.

 

Related Article -

 

Customer Engagement in Real-Time, Every Time

"Call Me" Now! - New SAP RTC feature

$
0
0

Anybody can initiate real time communication with C4C user.  On one side its anybody with browser access and another side its C4C user.  Anybody could be customer, prospect, partner etc.


'Call Me' sample scenarios -


1. Omni-Channel - As an Agent, while I am interacting with customer through emails. I sense that I can be more effective with RTC. I trigger this with 'Call Me' feature.

2. Embedded in Portals - A a customer/partner, I can initiate RTC with C4C user. I can do so be click on 'Call Me" link.

3. More...

 


Here is how it works -


1. Open Genband RTC within C4C. Go to Options settings and copy the URL.

2. Share URL through email or embed this URL in the portal

3. Anybody with access to this URL can initiate RTC with C4C user.


See attached screen shots -


Copy 'Call Me' Link -

Call Me Settings.jpg



User opens the link in a browser -

AnyUser Login.jpg

User initiates phone, video communication -

AnyUser Side.jpg

C4C User Accepts RTC request -

C4C User Side.jpg

Related Articles -


SAP RTC by Genband Available for Productive Use

Customer Engagement in Real-Time, Every Time

business partner Integration C4C-R/3 - account team

$
0
0

Starting with release 1602 the account team members can be synchronized from C4C to R/3.

 

 

In R/3 the partner functions are always sales area dependent, therefore the main prerequisite for this feature to work is:

 

-> you have to maintain your account team members sales area dependent.

 

This is only possible if your party role is flagged as 'sales Data dependent' in the fine tuning for party roles

AND once you have included the sales Area fields in the sales team tab via adaption mode.

 

d1.JPG

d2.JPG

 

please make sure you have the latest PI /HCI content in place in order to get the data correctly mapped into the IDOC segment E1KNVPM

 

d3.JPG

How to configure dynamic target groups in SAP Hybris Cloud for Customer

$
0
0

Target groups, simply put, is a group/list of customers within a pre-defined broader market, identified based on certain criterion and is created with a focus to send out a focused marketing content or activity.

For example, all customers in the state of California which are A – classified or all account in Germany which belong to the industry segment manufacturing.


Prior to 1605 of SAP Hybris Cloud for Customer, it is was possible to create only static target groups, which meant that  marketing administrator created target groups manually either using excel upload or selecting members in the target groups .


With SAP Hybris Cloud for Customer 1605 release, the marketing administrator can now define dynamic target groups. This feature enables the marketing administrator to define conditions based on which the members are determined automatically in the target groups.


For example, let us take the use case shared above, ‘all accounts in Germany which belong to the industry segment manufacturing’.

The user can create a dynamic target group defining these conditions and leave it to the system to do the heavy lifting. 

The system will automatically query the customer data base and add alls account which have country as Germany and industry segment as manufacturing to the target group.


The user have full control to schedule this determination, which means, he/she can define if this automatically determination needs to be done daily, weekly or monthly. This scheduling capability makes sure that the target group periodically updates the member list and adds/deletes members solely based on the conditions defined .

 

This capability reduces manual error in adding new accounts which might have been added to customer database and also deleting members which do not satisfy the conditions defined in the target group.

 

The user has to decide whether the target group is dynamic or not at the time of creation of the target group.

This is done by ticking the checkbox provided on the creation screen.

Once done, the type of the target group (static or dynamic) cannot be changed.

At present, conditions can be maintained for the following business partner types.

  • Account
  • Contact (with an account assignment)
  • Individual Customer

 

This blog explains in detail, the creation, configuration and scheduling of dynamic Target Groups.

 

Creation of a dynamic target group

 

  1. Go to the Marketing WorkCentre, Target Group WorkCentre view.
  2. Click on button New.
  3. You can create a dynamic target group by ticking the checkbox Member Determination on the target group creation screen. The target group will be in status In Preparation.

Fig 1.png

Fig. 1


Note: Once saved, then you cannot change the type of target group (static or dynamic).

 

Automatic Member Determination Configuration


I. Maintenance of conditions

 

1. Open a dynamic target group from the target group worklist.

The dynamic target group can be identified by referring to the column Member Determination on the worklist table. If checked, then the record is a dynamic target group

 

2. Go to the Member Determination tab.

In this tab, you will see three tables where you can maintain the conditions; each table holds the selection conditions for one type of business partner.

Currently the automatic member determination is supported only for 3 types of business partners.

    • Account
    • Contact (with account assignment)
    • Individual Customers


3.Maintain the appropriate conditions for each business partner type.

For example, if you would like to add all 'A' classified Accounts in US as members to the target group, maintain the conditions as shown in figure Fig. 2.

 

Fig 2.png

Fig. 2


II. Maintain the determination schedule

 

Once the conditions are maintained, you have to schedule the member determination process.

The system provides you the option of scheduling immediately or at a particular date and time as shown in figure Fig. 3.

You can also specify a recurrence for the process. This is particularly helpful if you have a large and dynamic customer base.

 

Fig 3.png

Fig. 3


III. Activate the member determination process

 

Once you have maintained the conditions and the schedule, you can start the member determination process by clicking on the Activate button under the Actions button group.

The activation triggers the member determination process in the background. The progress of this progress is captured in the Execution Status field.

Upon successful activation, the target group status becomes Active and the execution status becomes Scheduled.

Note: The Activate button performs two actions, viz. activating the target group and scheduling the member determination process.

Activation of the target group is a onetime activity. Hence the Activate button remains enabled only when the target group status is In Preparation.

Once the member determination process is completed, the execution status of the target group becomes Finished Successfully.

The members that satisfy the conditions are also added to the target group as shown in figure Fig. 4.

 

 

Fig 4.png 

Fig. 4


At any time during the member determination process, if you need to adjust the conditions or the schedule, you can click on the Deactivate Schedule button.

This will stop the determination process and set the execution status to Not Started.

To resume the process, click on the button Activate Schedule.

Please note that the process cannot be stopped if the execution status is Running.


IV. Maintain Conditions for Extension fields

 

The dynamic target group is designed in such a way that it also allows the user to maintain conditions for extension fields.

However in order to maintain business consistency, the selection criteria for the member determination should be the same in case of both dynamic target group and manual target group.

  1. i.e. The set of attributes for which conditions can be maintained on the dynamic target group and the set of search fields on the static target group are same.

This is true in case of extension fields as well.

Here’s a step by step explanation on how to maintain conditions for extension fields.

The example considers the member type Account.


Note:In order to add extension fields, the user should have access to the Key User Tool


1. Create an extension field on the Customer Screen

Create an extension field on the customer screen as shown in figure Fig. 5.


Fig 5.png

Fig. 5


2. Select the appropriate extension scenario

In order to maintain the conditions for extension fields on the target group, the field needs to be extended in the appropriate extension scenario.

In order to do this, please follow the steps mentioned below.

  1. Create an extension field, save and open the edit screen.
  2. Navigate to the Extension Scenarios tab.
  3. Select the scenario Account - General Information to Target Group - Account Selection and add the field to this scenario as shown in figure Fig. 6.

Fig 6.png

Fig. 6


3. Add the extension field to the Customer Screen

Once the extension field is created, it is not visible by default on the customer screen.

You have to add the field as shown in figure Fig. 7. Add the extension field and maintain appropriate values.

Fig 7.png

Fig. 7


4. Add the above added extension field(s) to the search screen of static target group

Open a target group where the member determination is NOT configured, i.e. a manual/static target group.

Go to the members tab and click on the Add Accounts button under the Add button control.

On this pop-up screen, add the extension field that you created for the Account (as shown in figure Fig. 8).


Note:This is an important step. If the extension field is not added to the search pop-up, then the member determination for the extension fields will not work.

Fig 8.png

Fig. 8


5. Add the extension field to the conditions table.

Now open the dynamic target group where you want to maintain conditions for the extension fields.

In the Account Condition table, add the extension field as shown in figure Fig. 9.


Fig 9.png

Fig. 9

 

This completes the configuration process for maintaining the condition for extension fields.

 

The process is similar for other member types (Contact and Individual Customer).

The extension scenario which correspond to each member is listed below.


Account                               - Account - General Information to Target Group - Account Selection

Contact                                - Contact - General Information to Target Group - Contact Selection

Individual Customer            - Indivudual Customer - General Information to Target Group - Indivudual Customer Selection


Automatic transfer of open leads/opportunity to Manager when sales employee leaves

$
0
0

Hello,

 

We have a business requirement if any sales employee leaves and we want to re-assign the open leads and opportunities to either his manager/new hire. Is there way we can re-assign them without having to do like mass change? More like an automatic by entering this data one time to update in leads and opportunity..

 

If assigning to manager for short period and then when new employee join these leads/opportunities are transferred to him/her once again.

 

Is there a way to custom build to achieve this or any existing process already exist?

 

Your quick response is highly appreciated.

Many thanks in advance for your help.

Thank you,

Shashi

Viewing all 262 articles
Browse latest View live


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