How to undertake SAP and Salesforce Integration

How to undertake SAP and Salesforce Integration

The rapid adoption of Cloud Computing is impacting how enterprise applications are developed, distributed, and implemented. This development has implications for both the IT industry as well as enterprises.

The typical characteristics of enterprise software are complexity, data dependency and security and they focus on three areas: the platform, collaboration, and co-evolution.

The original idea for SAP was to provide customers with the ability to interact with a common corporate database for a comprehensive range of applications this has undergone a significant change over a period. Salesforce started off as a cloud-based customer management company though it has also expanded its solution stack significantly.

SAP S/4HANA- SAP S/4 HANA has a Cloud-based ERP offering that transforms SAP from an on-premise platform into a Cloud-based solution. This solution can be deployed either as a public Cloud or as an on-premise deployment.

Public Cloud designed for companies that have less restrictive data security and segregation policy and need integration that addresses the core business processes.

Salesforce – Salesforce revolutionized the CRM software market by developing a SAAS based CRM. Salesforce CRM has features that address most of the customers’ requirements. Force.com is a recent PaaS offering from Salesforce and offers developer several tools to develop and deploy their applications. The advanced apps distributed through the market platform AppExchange. AppExchange applications are web-based applications that interoperate with the Force.com platform and quite often Salesforce CRM. With both Salesforce and SAP entrenched within the enterprise there seamless integration has been an area of focus for corporations.

SAP Integration methods are Netweaver and Non-Netweaver based like BAPI/ ABAP/ IDOC ALE Inbound/Outbound Web services Netweaver XI/PI SAP BW/BI (ODBO, OLAP BAPI, XML for Analysis/XMLA) ABAP Connector & Batch-Input Connector.

Integrating with Salesforce Integration Platform provides third-party platforms capabilities for automated integration with the Salesforce API including objects, CRM metadata, bulk jobs, replication and lead conversion.

A business process integration solution allows corporations to perform all the required functions with objects. When working with Salesforce.com metadata, an organization needs to validate the status of any metadata operation at any time.

For corporations which have both SAP and Salesforce implemented the benefit of Integration are many, this combination is utilized to synchronize information between the two frameworks. For example, when data integrated into Salesforce, it is essential that this information is accessible in a synchronized way for finance, administration, and other business functions managed by SAP. Whenever SAP and

Salesforce is well integrated, and organizations can streamline and automate their business processes.

A significant advantage of this integration is reduction of manual data entry, fewer information redundancies, and mistakes caused by manual information

Undertaking data-integration predominantly did through either Extract-Transform-Load or Enterprise Application Integration tools. ETL approach involves data uploads in batches into Salesforce, or from Salesforce into data warehouses.  Batch uploads happen at regular intervals which can be hourly, daily or some other frequency. EAI is a complex event-based approach, where data ingestion occurs very frequently from external systems into Salesforce.

Conventional integration scenarios have been resource intensive and complex. Collaborative, point-to-point integration, for example, has been used at times as a rapid solution for SAP and Salesforce integration.

Service Oriented Architecture is an approach that can be leveraged to incorporate SAP and Salesforce. While SOA stacks enable free integration between applications and give corporations flexibility to address changes. Developing a full SOA stack for a large enterprise application requires high expenses and significant time to prepare.

Undertaking SAP and Salesforce integration require addressing of several issues which include aspects like identifying connectors and interfaces security, and the center approach you’ll take. There are multiple options to undertake integration. Designed and delivered right all solutions can work, but every opportunity has its scenario of risks, expenses, and tradeoffs. The idea should be to use the approach best suited to a corporation’s requirements.

When integrating SAP with Salesforce.com, a corporation needs to consider factors like network infrastructure, information flow, and data exchanges.

One of the ways to integrate SAP with Salesforce is by using the Sales Lightning component to undertake this integration.

Another viral mechanism leveraged by corporations is to undertake integration leveraging Informatica ETL functionality which enables an organization to set up a client synchronization with a wizard-based interface.

A new approach that is increasing in popularity is that of API driven integration and a leading solution in this domain is Mulesoft, the advantages of undertaking integration using this method is that building a scalable solution is easy in comparison to other approaches. With APIs, developers can integrate with endpoints and make connections without needing to have a deep understanding of disparate systems.

To wrap up

Remember, integrating Saleforce.com to SAP is essential since there is a central need to bring these frameworks together to meet the prerequisites of the business. Integration projects have been very specialized, challenging and costly to execute, a reason corporation frequently stayed away from this leading it to it hamper business. Once this integration initiates successfully, it becomes easy for organizations to exchange data seamlessly.

Salesforce Google Map Integration

Salesforce Google Map Integration

We are Salesforce™ Experts and we channelize our energy by documenting all the industry-specific technical problems we solve in Salesforce™ CRM world. Here I am about to explain one of the Google Map API with Saleforce.com custom development projects I was closely involved as a Salesforce™ Developer. At, below I will provide you the brief description of the project what basically it is and how we helped our end client.

Requirements:-

In, this Project Client basically need a system viewer where he can calculate a distance between the source and the other records. The basic agenda of this project to help our end client where they will help their customer and they can identify all the machine from the source of Account.

The original idea of the project is that from a single Account record Source we need the ability to produce a list of other accounts. Account records that fall within a certain proximity radius to that account is a list of accounts that result from the search ‘Proximity’ accounts.

The account in the system could potentially be a source account. The user initiating the search from the Source account would first need to populate a screen showing various criteria information. Such criteria would include a ‘Radius’ setting we will provide the initial default value but we will need the ability to override.

Additional criteria would include two or three custom fields these currently exist on the Account record. It will provide default values for each but we will need the ability to override.

It is not mandatory that the list of Proximity accounts display in map form. If the Proximity accounts are displayed in a list, and not on a map, it is important that we can see the distance in miles from each Proximity account to the Source account.

We came with the solution:-

In,this what we acknowledge that from the list of account we can identify certain set of machines from the source to the estimate miles and can find out the list of machines from the source with different cost and it would ease to identify the certain machine from the list of miles and also it can be identified from the last sale day ago which we can filter from all the above source and then click on search. From this, it provides two option 

1-Generate pdf
2-View Map

Generate Pdf:- From this Option Customer after selecting their choices they will click on this option and they will get the detailed report within the Pdf.

View Map:- It provides the viewer to identify all the destination location of the products and analyze the certain destination via this map.

 

 

Now, with the following screenshots its methodology can be understood as follows:-

1) Search Filter with the various criteria

 

It can be understood with the following Code Snippets as follows. These are the few components which we deployed to the production.

1. Show All Account on Filter Controller:-

From below code, we are able to distinguish how to multi-select the option which is available on the filter-

public with sharing class ShowAllAccountOnFilterController {

public String recordID{get;set;}

public Account Sourceaccount{get;set;}

public double Last_Sale_Days_Ago{get;set;}

public list<Account> accountList{get;set;}

public list<Account> accountlistSearched{get;set;}

public list<Account> accountlistSearched1{get;set;} // list will show on map

public list<wrpclass> SearchAccountListWithMiles{get;set;}

public list<String> accountpicklistvalue;

public list<String> seletectedaccountpicklistvalue;

public boolean listisempty{get;set;}

public boolean showiflistfilled{get;set;}

public  String headerdata{get;set;}

At below there is a description of the above model with the ER Diagram

 

 

 

 

Salesforce Winter ’18 Top Features For Platform

Salesforce Winter ’18 Top Features For Platform

Salesforce presents 54th release this year; we feel enchanted to try-out our hands upon incredible new features from winter ’18 version. Subsequently, playing with the latest version directly on the platform brings out our favorite top 6 highlights from the winter ’18 release. Let’s check them out here!!

Salesforce Service Salesforce DX: Salesforce DX is a whole new and innovative way to regulate and flourish Salesforce applications. Whether you’re an individual developer or functioning as part of an organization, Salesforce DX contributes an integrated end-to-end lifecycle design for high-performance agile development, and above all, Salesforce creates it the approachable and flexible for you to develop with coexisting tools.

Salesforce DX is a compilation of products and services that transport source drive development. Now you can get gain from modern collaboration technologies such as:

  • Get to version control everything across your team
  • Your code
  • Your org configuration
  • Metadata

It provides more excellent ability to test out features with determination. Also, Salesforce DX CLI’s is a powerful command-line interface that facilitates development and builds automation while working with your Salesforce org and much more.

Salesforce IoT Explorer: Salesforce IOT Explorer is inherent to the core Salesforce platform; you can launch precisely from the setup. Salesforce is accessing device data in real time and monitoring the energy output of a connected product. The orchestrations interface allows you to see various states with associated declarative rules that automatically generates a service case when IOT Explorer detects a fault. Here the case details are directly set up within service console that has been notifying by reading the device data. A service technician can now escalate and route that case accordingly based on the device data. With Salesforce IOT Explorer the user experience and processing engine are all built into the core Salesforce platform and is fully integrated across all your business processes. All this benefits you to connect with customers across any connected device and revolutionize the way you service to sell and market.

Einstein Analytics New Story Recommendations and Visualizations: The latest Einstein analytics enhancement included exciting new features for Einstein discovery drive, smarter insights and impressed with new story visualizations. Salesforce has taken care of all the work while it recommends improvement to your data. It will automatically detect any duplicates and outliers so that you can create the best version of your analytical report. With the addition of story timelines, you can tap back and forth between your story and what’s going to change over time is the ability to discover these consistent patterns in your data without the use of any data scientist, it allows your team to work smarter and faster.

Einstein Analytics SDK with Encryption at Rest: In winter 18, there’s an opening up the foundation of our analytics platform to everyone with the Einstein analytics SDK. Whether your app is built in lightning visualforce or even outside of Salesforce, you can now have your apps interact with any analytics dashboard.  Salesforce has now introduced both the analytics web SDK which allows you to quickly connect with custom applications as well as the analytics effects SDK where you can put up queries of your analytics data from any apex class encryption at rest. It might built-in natively, you’ll never have to worry about the security and protection of your analytics data.

Lightening Experience Enhancements: In the winter release, you’ll undoubtedly notice a drastically changed Lightning experience. These enhancements are results of incredible research feedback from Salesforce community and a strong desire to see customers succeed.

First comes first, This feature has an all-new option which is Scanning information.  You’ll soon notice the more compelling contrast between the content and the background. Salesforce has improvised legibility with enhanced font sizes and with explicit hierarchies between the textbox, headers, body content, and buttons. You will also observe more compact design with increased content density and less white space on the page. Now you can view more data in the same area and spend less time scrolling, but that’s not all. We’ve infused the lightning experience with some Salesforce fun. Trailhead branding built right in; these new enhancements help make every user attain the most out of their lightning experience and be more productively efficient.

New Lightning Components: It is the moment of joy to share that; Salesforce has added even more based lightning components for Salesforce developer community. Based lightning components are the building blocks that make up the modern lightning experience, Lightning apps, and lightning communities user interfaces.

New and Changed Lightning Components are as follows:

  • Added information about new components, lightning:outputField and lightning:recordViewForm, and changes to lightning:datatable and lightning:verticalNavigation
  • New and Changed Lightning Components
  • Added information about changes to lightning:button and lightning:buttonStateful.
  • New and Changed Lightning Interfaces
  • Added support for the force:hasRecordId interface for Lightning components used in the Utility Bar.

Hope this has helped you with the all new winter 18 release, for more information you can check us out at www.cloudanalogy.com

Challenges Of Undertaking Salesforce Integration

Challenges Of Undertaking Salesforce Integration

A modern organization tends to utilize various sets of application to enhance its operational efficiency. For example, Salesforce for Sales, Workday for HR & Finance, Service Now for Operations, Atlassian for Engineering and so on. Most of these applications serve different functions. Some of them are not programmed to work with one another yet they have many things in common, i.e working out similar business complications and issues. When we integrate related yet separate applications within an organization it helps the business to increase their operational consistency, efficiency, and quality. CRM systems incline to serve a consolidated location for all the data related to the customer, so, it makes more sense for a company to enable the connection with such platforms.

Salesforce with a market share of around 22% in the CRM domain and customers ranging from startups to Fortune 500, has a well-deserved reputation in the market. Salesforce offers a range of features like multi-channel marketing, customer segregation, support service, collaboration and forecasting, reporting, workflow etc. Salesforce APIs are smooth and allows integration but then there are still some areas which need to look after.

According to an article published in First Post, a survey of 200 active Salesforce users and professionals disclosed their top issues like future planning and usage patterns with the implementation of Salesforce. Around 54 percent of the Salesforce user pointed out that data source integration with the application is the most critical issue.

With solution ranging from Biztalk to Informatica, Integration technology has existed for many years but cloud computing has changed the scenario and brought upon an entirely new set of challenges. In the initial years of integration technology, it was categorized around terminologies like Enterprise Application Integration, Enterprise Information Integration  Extraction, Transformation, and Loading. For simpler usage custom coding was also an option.

In the hybrid environment that spans on-premise and cloud-based data centers, the integration scenario has changed and have become more complex in several ways. To start with, the computing infrastructure for the foreseeable future will now be spread across the following locations:

The Salesforce integration issues erupt from the necessity to share data between Salesforce and various platforms.

The main integration challenges are:

1. Extensive coding and application installation required

In certain integration scenarios, extensive coding is required and multiple appliances need to be installed to ensure successful integration. These solutions require the management to update the software and similar infrastructure. With frequent platform update, it becomes important that regular distribution of these updates for all instances should be ensured at the same time.

2. Control

Undertaking integration development, management and monitoring in the cloud for centralized control is a complex task. Developing a runtime the engine that can be deployed either in the cloud or on-prem for installation and integration execution that can be a cumbersome task especially if we are looking at sharing of data among disparate applications. This is also dependant on a corporation’s security and latency considerations.

3.  Flexibility

At complex environments where several SaaS and on-premise application needs to be to integrated, which includes a combination of legacy at a  house hosted applications to cloud-based applications. In case there is a requirement to move data from on-premises application to cloud-based applications at migration scenario. It is important that any integration effort should support any combine premise and cloud application integration. This should be possible even across core information systems, subsidiaries, regions, and partners.

Possible Solutions

There are two main ways which can help to deal with the above or other Salesforce integration issues. It can be either building on your own solution which is customized or to use an existing tool for the job.

Evaluating the main pros of building one’s software for integration is being presented with extensive customization options along with enormous flexibility. It will allow satisfying all the needs of a business and CRM integration. However, it involves lofty investment and considerable time to process and develop such a tool. Thus, it becomes an unreasonable option for businesses. The second way is to use existing services which is easy to afford and at the same time faster to deploy. By having a single access to one of these services, it allows integration with multiple systems at the same time. There is practically no requirement to write individual integration modules for different CRM platform nor there is a requirement to hire developers.

Can Force.com (From Salesforce.com) Be Considered A PaaS

Can Force.com (From Salesforce.com) Be Considered A PaaS

INTRODUCTION TO CLOUD COMPUTING AND FORCE.COM

“Cloud Computing” has dramatically changed how business applications are built and run. Deploying another application is presented as fast as opening your Internet program. Platform as a Service — or PaaS — is today an established model for running applications without the challenge of maintaining the hardware and software infrastructure at your company. An advantage of PaaS solutions is their ability to upgrade themselves to latest without manual intervention.

PaaS services are deployed in the cloud and accessed by clients essentially via their web program. Software designers, web engineers, and organizations can make all profit by PaaS: Software designers can take advantage of a PaaS solution to assemble an application which they are planning to offer over the web or software to sell out of the box. Web designers can utilize individual PaaS situations at each stage of the procedure to create, test and host their sites. Organizations can build up their internal software, mainly to develop unmistakable ring-fenced advancement and testing conditions. Platform as a service (PaaS) is a distributed computing model in which an outsider supplier conveys hardware and software instruments – usually those required for application improvement – to clients over the web. A PaaS supplier has the hardware and software all alone infrastructure.

PaaS liberates clients from having to install in-house hardware and software to create or run another application. The original aim of PaaS was to improve the code-composing process for designers, with the infrastructure and operations handled by the PaaS supplier. Initially, all PaaS platforms were in the public cloud. Over a period because many companies did not want to have everything, in public cloud, private and hybrid PaaS platforms built.

Force.com Platform enables corporations to build and deploy apps in the cloud, faster than much on-premise application platform, hybrid platforms, and many cloud platforms that are not as evolved.

PaaS gives a situation to engineers and companies to create, have and convey applications, saving designers from the complexities of the infrastructure side (setting up, arranging and managing components, for example, servers and databases). PaaS can accelerate the application development by ensuring that developers and other stakeholders can concentrate on the application itself without having to address issues around managing runtime, middleware, operating framework, virtualization, servers, storage, and networking.

 What makes Force.com PaaS?

 

Just like Salesforce.com is an out of the box solution with their products around, Sales Cloud, Service Cloud and Marketing Cloud. An organization could go out and buy the Sales Cloud today and start logging leads, opportunities, running reports, etc.In contrast, by buying some Force.com licenses, you would not have an out of the box solution, no access to leads, accounts or opportunities. You would have to build Apps, Tabs, Custom Objects, Workflow Rules yourself all to design the kind of system that you want to use.

Force.com as PaaS

Force.com has some significant difference from other PaaS providers as it underpins a programming interface and is specifically intended for creating multi-tenant cloud-based applications. It has a unique programming model based on the Java-like Apex programming language. It also has a native UI and UI programming language. Applications built on Force.com platform can be expansions of CRM capabilities gave by Salesforce CRM, or they can be work process-based business applications, for example, approval work processes. The platform also provides integration APIs to CRM integration or outsider services.

In Force.com a developer can merely declare data objects are utilizing visual configuration tools and compose trigger handlers in the Apex programming language. Support for multi-tenancy, including tenant data isolation and configuration, is given out of the case with no specific programming required. One of the practical, abnormal state aspects of this sort of platform.

However, the tradeoff is that the programming model is one of a kind and does not translate to traditional enterprise architecture. Additionally, with a specific end goal to help multi-tenancy, the platform has runtime cut-off points in place which limit the amount of data, some transactions, and transaction latency.

The Force.com platform offers other features, including security and integration with external APIs

Force.com accelerates development velocity for cloud-based applications that tap into the center Salesforce.com application and facilitate seamless deployment. Many ISVs are reluctant to adopt Force.com because of its being proprietary and does not have the maturity or market acceptance as compared to more mainstream development platforms, for example, Microsoft .NET or Java/J2EE. Also, as the Force.com does not offer extreme cloud portability some programmers are are hesitant in leveraging this platform

Salesforce.com is proceeding with its PaaS push. For example, the company acquired Heroku—a Ruby-based PaaS that backings a global improvement group and pushes many social and versatile cloud applications. The company also presented database.com—a language-autonomous facilitated database apparently on the path to contend with Microsoft SQL Azure. How these forms strategically complement Force.com and will be accepted by the market has yet to be completely caught on.

A right PaaS platform drives innovation, enabling corporations to deploy applications faster. An exact PaaS application is open, lets IT collaboration helps in multi-cloud deployment.

Despite Force.com’s focus on productivity, the platform still needs to address factors like development support for a range of application from simple to the most complex, visual development of application logic and source control out of the box.

Pin It on Pinterest