Configure SAP Commissions in Salesforce(SFDC)

Hi All,

The purpose of this article is to demonstrate and explain how to Add SAP Commissions Web tab inside Salesforce allows Sales reps/Admin to quickly access their Dashboard/Reports/Disputes, content, and more within Salesforce.

This allows for increased access and adoption of Commissions tab as a sales incentive tool, as reps can use it without ever having to leave their CRM.

Sales Rep can get an view of Performance earnings for their opportunities/deals completed and if their is any credits/incentive is missing or not calculated in earnings , disputes can be created within the current tab and can receive/respond messages from his/her Manager for the dispute.


Salesforce Admin will start login & setup

Let’s Start to Configure (follow the numbers in order)

  1. In the top right corner of Salesforce, find and click Setup.
  2. On left side-bar find Build, and click Create.
  3. Once Create opens, click Tabs.
  4. Scroll down the page to Web Tabs and click New.
  5. Update the view details for Web tab to display
  6. Update the SAP Commissions API link in textbox ( tenant-id)


Choose tab type
=          URL,
Label =                          <your custom name>
Tab Name =                  <your custom name>
Tab Style                      can be any of the default styles, or you can create a custom style.
Frame height should be    600 pixels.

Click Next

Enter the SAP Commissions URL (Provided below)

Just copy and paste below line – change only <tenantid>

https://<tenantid>.callidusondemand.com/CallidusPortal?sforceSessionId={!API.Session_ID}&sforceServerUrl={!API.Partner_Server_URL_90}

Click Save

Sample Screenshot below after you saved


Select your Salesforce Experience

Let’s see how Sales Rep login through Salesforce Classic

Note ⚠️ : After the setup is completed, every first time login screen will be prompted and from next login, it won’t be displaying.

Let’s see how Sales Rep login through Salesforce Lightning

Note ⚠️: After the setup is completed, every first time login screen will be prompted and from next login, it won’t be displaying.

📌 Thank you for reading!. I feel much better. It’s good to be liked. (Hit Like Button). you can also share this blog through LinkedIn or twitter.

4th Generation Release of SAP Best Practices for SAP SuccessFactors Learning

About three years back Adobe talked about Flash & The Future of Interactive Content. And announced Flash’s end-of-life (EOL), i.e. their plan to stop updating and distributing the Flash Player at the end of 2020. For all the SAP SuccessFactors Learning customers, partners and consultants out there this of course raised the question about what this means for SAP’s learning solution.

And now, with the latest release of SAP SuccessFactors Learning, we –the SAP SuccessFactors learning community – can experience hands-on what this means: a delightful newly reworked SAP SuccessFactors Learning solution, that went way beyond a pure technical replacement effort! This great blog Flash-Based Learning Administration Interface Deprecated Within Second Half 2020 Release – Innovation Alert has all the details.

Also, this has been the call for us in the SAP Best Practices teams to lift all our available 3rd generation assets to the new HTML5-based configurations. And here they are. The 4th Generation of SAP Best Practices for SAP SuccessFactors.

This new version addresses all available scope items in the package:

Learning Management

This process supports the creation of different learning items such as classes and online items. It supports the creation of curricula and programs to structure learning content. Through various assignment methods, such as automatic, mass and self-assignments, learning items can be assigned to employees. Learners search and browse learning catalogs for learning items. Learning items with online content in iContent and through Open Content Network (OCN) are supported.

Learning Evaluations

Learning evaluations based on surveys facilitate the evaluation of user satisfaction with a course (Course Feedback Survey) and the evaluation of the learner’s ability to apply knowledge (Follow-up Survey)

Learning Assessments

An assessment is an approach for measuring users’ understanding or mastery of content. Learning assessments come in two flavors: quiz assessments and exam assessments. Quizzes are designed with simplicity in mind and are a set of questions and rules. Exams have been designed to take care of more complex assessments and are supported by a question library which allows to share questions among exams.

Learning Groups with Jam

SAP Jam integration allow to bring together the world of more formal learning with the more informal social learning. Learning groups within SAP Jam can be either associated with learning items or with complete programs (in the Learning Program Jam tile) so that learners and users can share content and ideas.

Learning Competencies

In an integrated scenario with Career Development Planning, learning activities can be added to the development plan and refer to learning items in SAP SuccessFactors Learning that support the development of certain assigned competencies (competency-based catalog search).

Mobile and Offline Learning

Mobile and Offline Learning empowers learners with the flexibility to learn at their convenience, anywhere anytime – even when they are offline. On iPad® as well as on Windows® laptops, learners can easily access their learning assignments or search for courses in learning catalogs. When they find a course they’d like to take, they can simply assign it.

Training Planner

With the Training Planner organizations have the ability to manage training budgets. The training planner allows companies and learning departments to run training planning cycles for a specific planning period where employees can raise training requests for courses they would like to take in the future.

Over the last quarters we have seen such a strong continuous demand and consumption of the SAP Best Practices for SAP SuccessFactors Learning, that we are deeply grateful to contribute to safeguarding and supporting our customer’s journey to this new technology.

Please visit SAP Best Practices for SAP SuccessFactors Learning on the Best Practices Explorer and let us know if this helps you making the transition to a new technology a ‘flashy’ and smooth one.

Discover SAP S/4HANA Cloud Extensibility Service in SCP

In this Blog  I would be covering about basics of SAP S/4HANA Cloud Extensibility Service which I came to know while configuring Enterprise Messaging for Cloud 2005 . SCP Services for at least me is like deep ocean; more you explore it – more you find about it. So, this service is available in Cloud Foundry account and its only for integrations with SAP S/4HANA Cloud, SAP SuccessFactors, SAP Cloud for Customer, SAP Commerce Cloud, and SAP Field Service Management. Probably recently added since few months back I remember it wasn’t there. But what can this service help me with, you would be thinking right? 

Now you have automated Configurations option using this service: You can automatically create Communication Arrangements in SAP S/4HANA Cloud and Destinations in SCP. Isn’t it cool? So while building extension applications, you can leverage this service for automation of the integration between the cloud platform and SAP S/4HANA Cloud .

This SCP Service available is Cloud Foundry account as shown below:

Pre-requisite to use this service:

  1. S/4HANA Cloud system is registered in SCP 
  2. As SCP admin you must configure Entitlement for Sub account for the SAP S/4HANA Cloud Extensibility Service
  3. Go to SCP Global Account 
    1. Choose Entitlements->Sub Account Assignments and select the sub account from the drop-down menu and click on Go
    2. Choose Configure Entitlements and Select the SAP S/4HANA Cloud Extensibility as shown below. In the right side select available plans either or both as shown below.

       So, we have 2 types of plan as shown below:

api-access: For applications running on SAP Cloud Platform to consume SAP S/4HANA Cloud APIs, we need to create a service instance of the SAP S/4HANA Cloud Extensibility service using the api-access service plan.

messaging: Enables the Enterprise Eventing Integration (SAP_COM_0092) communication scenario which allows you to consume SAP S/4HANA Cloud events and create event-based extensions.

Let’s quickly look into one example – I need to access Business Partner API in my application; so, I need to have the Communication arrangement created in SAP S/4HANA Cloud and Destination created in SCP to use the API. Let’s do this with the help of SAP S/4HANA Extensibility Service

  •  In SAP Cloud Platform Cockpit, go to your subaccount and navigate to space in which you want to create a service instance
  • In navigation area, choose Services ->Service Marketplace and select S/4HANA Cloud Extensibility Service in right side of pane. Below screen will show up – that shows the Service Plans that we selected earlier

  •   On left side select Instances and click on New Instance 

  • Here select the plan as api-access since you are creating it to access Business Partner API and in system name select the name of your S/4HANA Cloud system (that you used while registering S/4HANA Cloud system)

  • In next, either provide the JSON file / give the json format directly. Refer here for sample JSON file for Business partners . Change the system name to your S/4HANA Cloud system name as in drop down selected and provide username and password for basic authentication
  • Enter the name of your instance and click on Finish – it will create the service instance.
  • After you have created the service instance: The newly created instance appears in the list of instances in the Instance panel and An HTTP destination on a subaccount level with the same name as the service instance name is automatically generated in this subaccount.

And if I check SAP S/4HANA Cloud system Communication arrangement has been created automatically based on our json file given in service instance.

Similarly, you will find the destinations created in SCP CF Sub account. During the creation of the service instance, destination on a subaccount level with the same name as the service instance name is automatically created in the subaccount. It contains all instance binding properties which are required to establish connection to the SAP S/4HANA Cloud system.

Summary: I thought to share with you guys about S/4HANA Cloud Extensibility service since I am sure someone like me wouldn’t be knowing that Communication arrangements and Destinations can be creating automatically too and there is service with name S/4HANA Cloud Extensibility . I am not covering Enterprise Messaging activation using this automated process in my blog since when I checked with SAP – they did mention that they are in process of updating their blogs . So, hoping that soon SAP blogs will cover the same 🙂

Regards

Taranam

Role of Integration Switches in Replication from SuccessFactors to SAP ERP

Introduction:

Integration is one of the most vital factor in SAP HR system. The Integration moves the data from Organization Management Tables to PA tables. It is required to keep the data consistent between the OM and PA modules of SAP HR. The Integration is maintained through a Switch which is accessed through the table T77S0, the role of this switch can be utilized in Replication from SuccessFactors to SAP ERP also when we need to allow only certain Objects of Organization Chart alone needs to be Replicated.

Role of Integration Switches in Replication from SuccessFactors to SAP ERP

Firstly, Implications PA/PD integration to integration Employee Central to SAP ERP HCM, and how can we find out whether it’s active or not.

In SAP ERP HCM system, there will be an active integration between Organizational Management (OM) and Personnel Administration (PA), called PA/PD integration. PA/PD integration synchronizes the Organizational Management data, such as position, job, organizational unit, or cost center between Organizational Management and Personnel Administration. We can use PA/PD integration if we are going for replicating the employee master data and organizational assignment data from Employee Central to SAP ERP HCM to synchronize organizational data (position, job, org unit, cost center) between the Relationships (1001) infotype in Organizational Management and the Organizational Assignment (0001) infotype in Personnel Administration.

What PA/PD integration means for integration between Employee Central and SAP ERP HCM

In Personnel Administration, a person (object type P) can be assigned to a cost center and to organizational plan data: position, job, organizational unit. The assignments are stored in the Organizational Assignment (0001) infotype.

  • If we are using the employee master data replication message only, the message updates cost center from Employee Central and fills the default position from SAP ERP HCM Customizing (using the PLOGI PRELIentry in the T77S0 table).
  • If we are using the organizational assignment replication message, the message creates relationships in infotype 1001 between:
    • person and position (P –S)
    • position and cost center (S – K)
    • position and organizational unit (S – O)
    • position and job (S – C)
  • If PA/PD integration is not active, the person (object type P) is the only link between the data stored for Personnel Administration and for Organizational Management. The objects and the relationships aren’t synchronized across the two components.
  • If PA/PD integration is active, infotype 1001 of Organizational Management and infotype 0001 of Personnel Administration are kept in sync. This means the Organizational Management fields position, job, org unit, and cost center are synchronized with the corresponding fields in infotype 0001 of Personnel Administration.
  • If the employee is a new hire, the organizational unit and the job are left empty once the employee is created. The Positionfield is filled with the default position from SAP ERP HCM Customizing. After the organizational assignment message is processed in Organizational Management, the Organizational Management fields are replicated to the fields: position, job, organizational unit and cost center in infotype 0001 in Personnel Administration by PA/PD integration.

The employee master data replication message updates fields in infotype 0001 apart from Organizational Management fields for position, job and organizational unit. These fields are updated by the organizational assignment message in Organizational Management and then synchronized by PA/PD integration.

Keep in mind!

To have organizational assignment replication requests processed, we need to schedule the database update program as a regular background job. Processing of org assignments on its part triggers PA/PD integration

If PA/PD integration is not active, the organizational data fields of infotype 0001 (such as Cost Center) are updated by employee master data replication if a corresponding field mapping is defined in Customizing, in the template group we use for employee master data replication.

If PA/PD integration is active in wer system, organizational assignment replication updates the organizational data fields in infotype 0001. 

How PA/PD integration is enabled in SAP ERP HCM Customizing

Integration between Organizational Management and Personnel Administration is active if the value of the PLOGI ORGA switch in table T77S0 is set to X. Integration can be restricted for subsets of employees using the Control: Integration of Personnel Planning and Master Data Management (PLOGI) feature.

We can find these settings in SAP Customizing for Personnel Management, under Organizational Management   Integration Iwith Personnel Administration    Set up Integration with Personnel Administration. Choose Basic Settings to set the switch or Participate in Integration to maintain the PLOGI feature.

Restrict Relations Created When Replicating Organizational Assignment

Through Configuration we can decide which relations we want to create in the Enterprise Resource Planning (ERP) system when replicating organizational assignments from SAP SuccessFactors Employee Central.

The employee’s (object type P) relation to a position (object type S) is always created, independent of the settings we make here.

By default, also the following relations are created for the employee’s position:

  • Position to organizational unit (object type O)
  • Position to job (object type C)
  • Position to manager’s position (object type S)
  • Position to cost center (object type K)

If we want to create these default relations for the employee’s position, we don’t need to make any settings here.

If we need to replicate a reduced organizational assignment, however. For example, if we use generic object replication and replicate the organizational objects together with their associations from Employee Central. In this case, we can prevent creation of some or all of the relations of the employee’s position to other objects in the ERP system.

Note:We cannot prevent the employee-position relation from being created. If we switch off creation of all relations of the employee’s position to other objects, the relation of the employee to the employee’s position is still created in ERP.

Prevent creation of relations of the employee’s position to other objects by setting the value of these switches to X:

  • SFSFI OANSO- Don’t Create Position to Org. Unit Relation

Using this switch we can prevent the relation of an employee’s position to an organizational unit from being created in the Enterprise Resource Planning (ERP) system when replicating employee organizational assignments from SAP SuccessFactors Employee Central.

If we want to have the relation of the employee’s position (object type S) to the organizational unit (object type O) created by default, leave the switch value blank.

If we don’t want to have this relation created, set the switch value to X. Make sure to do so if we use generic object replication to replicate the position together with its association to the department, division, or business unit from Employee Central. Departments, divisions, and business units from Employee Central all correspond to organizational units in ERP. That’s why in this case we should prevent the relation of the employee’s Position to the organizational unit from being created by organizational assignment replication in the ERP system.

  • SFSFI OANSC -Don’t Create Position to Job Relation

Using this switch we can prevent the relation of an employee’s position to a job from being created in the Enterprise Resource Planning (ERP) system when replicating employee organizational assignments from SAPSuccessFactors Employee Central.

If we want to have the relation of the employee’s position (object type S) to the job (object type C) created by default, leave the switch value blank.

If we don’t want to have this relation created, set the switch value to X. Make sure to do so if we use generic object replication to replicate the position together with its association to the job classification from Employee Central. In this case, we should prevent the relation of the employee’s position to the job from being created by organizational assignment replication in the ERP system.

  • SFSFI OANSS -Don’t Create Position to Manager Position Relation

Using this switch we can prevent the relation of an employee’s position to the position of the employee’s manager from being created in the Enterprise Resource Planning (ERP) system when replicating employee      organizational assignments from SAP SuccessFactors Employee Central.

If we want to have the relation of the employee’s position (object type S) to the manager’s position (object type S) created by default, leave the switch value blank.

If we don’t want to have this relation created, set the switch value to X. Make sure to do so if we use generic object replication to replicate the position together with its association to the manager’s position from Employee Central. In this case, we should prevent the relation of the employee’s position to the manager’s position from being created by organizational assignment replication in the ERP system.

  • SFSFI OANSK -Don’t Create Position to Cost Center Relation

Using this switch we can prevent the relation of an employee’s position to a cost center from being created in the Enterprise Resource Planning (ERP) system when replicating employee organizational assignments from    SAP SuccessFactors Employee Central.

If we want to have the relation of the employee’s position (object type S) to the cost center (object type K) created by default, leave the switch value blank.

If we don’t want to have this relation created, set the switch value to X. Make sure to do so if we use generic object replication to replicate the position together with its association to the cost center from Employee Central. In this case, we should prevent the relation of the employee’s position to the cost center from being created by organizational assignment replication in the ERP system.