Feed

Hello @Mrinmoy Dam

  Integrating SAP Sales and Profitability Management (SPM) with Salesforce for real-time or near real-time territory assignment and data synchronization is an exciting opportunity. Based on my understanding, the approach involves Salesforce creating prospects and sales accounts, sending them to SAP SPM for territory and sales representative assignment, and then syncing the updated information back to Salesforce. I’ve been considering how to make this integration efficient, cost-effective, and scalable for future growth. Here are my thoughts.  

My Take on the Best Approach - 

I’m inclined toward an API-based integration using a lightweight middleware solution, such as MuleSoft Anypoint Platform or a similar iPaaS tool. Here’s why I believe this approach is a good fit and how it could work:

1. Real-Time/Near Real-Time Flow:
   • Both SAP SPM and Salesforce support robust APIs—such as Salesforce’s REST/SOAP APIs and SAP’s OData or RFC-enabled function modules. This enables smooth data exchange whenever a new prospect or account is created in Salesforce, allowing SAP SPM to handle territory assignment efficiently.
   • Event-driven triggers, like Salesforce Platform Events or SAP’s event system, can be used to send updated territory and rep details back to Salesforce almost immediately—bringing the process close to real-time.
2. Keeping Costs Manageable:
   • Developing a custom point-to-point integration from scratch may involve significant effort in terms of coding and ongoing maintenance. In contrast, an iPaaS like MuleSoft offers prebuilt connectors for both Salesforce and SAP, which can help reduce development time and associated costs.
   • MuleSoft’s SAP Connector is SAP-certified, ensuring strong compatibility with SPM, and its Salesforce Connector handles account and opportunity data with ease. Its usage-based pricing model also offers flexibility depending on data volume.
3. How to Put It Together:
   • Data Mapping: Map fields such as Account Name and OwnerId in Salesforce to territory codes and sales rep IDs in SAP SPM. The middleware can also transform data formats to ensure compatibility between systems.
   • Workflow: Design a process where a new account in Salesforce triggers an API call to SAP SPM. Once SAP determines the appropriate territory, it returns the information (either via callback or polling), and the middleware updates Salesforce accordingly.
   • Security: Implement OAuth 2.0 for secure authentication between systems.
4. Other Options Considered:
   • Batch Processing: This could be suitable for handling large volumes of data but may not meet the speed requirements for near real-time territory assignments.
   • Custom Middleware: Building a custom solution using Java or Apex offers flexibility but could require substantial effort for development and long-term support, especially given SAP SPM’s specialized functionality.
   • Other iPaaS Tools: Platforms like Jitterbit or Informatica are also strong options, though they may require additional configuration to match MuleSoft’s level of SAP integration and event-driven capabilities.

Hello @Dheerja Sharma

In the screenshot you provided, it shows that the agent is not deactivated. Please deactivate the agent first, and then try to remove the topic. 

Hi @Deepshikha .

I would suggest to check the setup once. 

like

Thanks

@Callum North

Here’s how you can set up a

1. Get Records
   • First, fetch all the records using Get Records.
   • Store them in a collection variable.
2. Initialize Variables
   • Create a counter and a temporary collection (to hold 250 records at a time).
   • Also, store the total record count.
3. Loop Through Records
   • Use a Loop to iterate through the full record collection.
   • Add each record to the temporary batch collection.
   • When the batch reaches 250 records OR it's the last record, then:
     • Call the “Convert Records to CSV” action.
     • Store the result (e.g., as a File or custom record).
     • Clear the temporary batch collection and continue.
4. Optional Enhancements
   • If you're working with very large datasets, consider Brian’s approach:
     • Use multiple "Get Records" calls with LIMIT 250 and conditional filters (e.g., based on CreatedDate or Id) to chunk the data from the start.

@Srinivasa Reddy Somu

  That is not quite correct.  The List Button type only renders the flow in Classic renderer, and therefore only appears on the "Custom Buttons" list in the List View Button Layout. 

Because of this limitation, the flow cannot use Lightning screen components, especially "Fields".  Once you understand this, and have experimented with the screen components that work, your suggestion will work!

upvote the idea to resolve this: https://ideas.salesforce.com/s/idea/a0B8W00000GddomUAB/configure-final-path-stages-for-a-custom-object

Potentially, but why not just use the standard functionality?