Showcasing Changes and New Features

Here are the changes in Cloud Integration capability of SAP Integration Suite since version November 2011:

• IDoc Receiver Adapter Has New Parameter to Set Message ID: The adapter provides a parameter to configure the message ID. You can use this feature to implement scenarios that guarantee end-to-end Exactly Once delivery.
• Integration Artifact Filter Improved: When you navigate from the message monitor to the integration content monitor, instead of a pre-filtered list, the currently deployed active artifact will be opened.
• Message Monitoring Performance Improved: The search logic for messages has been improved so that it also performs efficiently under high load conditions.
• Disable Attachments for Message Processing Failures: In the latest versions of the HTTP, OData V2, and OData V4 receiver adapters, you have an option to disable the creation of attachments when the message processing fails.
• Integration Flow Design Guidelines Changes. The following integration flow design guidelines have been changed:

  • Decouple Sender and Flows Using Data Store now uses a data store based on Data Store sender adapter instead of a Timer event.

  • Decouple Sender and Flows Using Data Store and Polling Consumer now uses a data store and polling consumer based on new data store sender adapter instead of timer event.

  • The integration flow design guideline (and integration flow Pattern Quality Of Service - Scenario 08) has been replaced by the new guideline Resequencer (see Resequencer).

These changes aim to enhance functionality, performance, and usability within the Cloud Integration feature of SAP Integration Suite, providing users with more flexibility and control over integration processes.

These are the new, major enhancements releasedin the Cloud Integration feature of SAP Integration Suite:

• Newer Version of Exception Subprocess Available: A newer version of Exception Subprocess pool – version 1.1 – is now available. You can move to the newer version in a single click. See: Migrate an Integration Flow Component to a New Version.
• Search Existing Flow Steps in an Integration Flow: You can now search for an existing flow step in an integration flow by different parameters.
• Usability Improvement After Creating An Integration Flow: You can now open an integration flow directly in the integration flow editor from the creation screen. Earlier, you had to create the integration flow, go the Artifacts list view of the package, and then navigate to the editor.
• Message Mapping: New standard functions added – getHeader and getProperty – so that you can fetch the headers and properties from the message exchange without having to write custom scripts.
• Integration Flow Design Guidelines Changes: The following new integration flow design guidelines (including integration flows) have been newly added:

  • Create Attachments

  • Read Multiple Attachments Based on Filter Criteria

These enhancements aim to improve user experience, streamline processes, and provide additional functionality within the Cloud Integration feature of SAP Integration Suite, empowering users to efficiently manage integration flows and processes.

Here are the new features introducedin the Integrations area since version 2111 (Nov 2011):

• Odata Service for Code List Mapping is a new service for querying code list mapping from Cloud for Customer.
• Create Copy of CPQ Quotes: You can create a copy of CPQ quotes and use it as a template.
• Owner in SAP CPQ Quote allows you to select in a sales quote an owner that is different to the user.
• Replication of Historical Account Team Information in your integration with SAP CRM: Historical account team information can now be replicated to SAP Cloud for Customer.
• Replicate Contingent Workforce from SuccessFactors to SAP Cloud for Customer: You can now replicate contingent workforce along with regular employees from SAP SuccessFactors.
• Improvements to SAP Master Data Integration: For business partner integration, you can copy the ID mapping for your sales organization.

These updates encompass various aspects of Common Features of Integration, Integration with SAP CPQ, Integration with SAP CRM, Integration with SAP SucessFactors Employee Central, Integration with SAP Master Data Integration and other enhancements aimed at providing administrators and integration developers with more flexibility, control, and functionality within SAP Sales and Service Cloud.

Here are the integration features from the major enhancements released in the SAP S/4HANA and SAP S/4HANA Cloud areas:

• Create a follow-up S/4HANA Service Order from a Service Ticket: You can create a follow-up S/4HANA service order from within a service ticket.
• SAP S/4HANA Sales Order ID in Cloud for Customer Quote documents: You can see the sales order ID in the corresponding preceding sales quote in Cloud for Customer.
• End to End Document Flow Integration for SAP S/4HANA Sales Orders: The new enhanced document flow shows the end to end SAP S/4HANA sales orders process.
• Sales Office and Sales Group in Contract Pricing: The fields Sales Office and Sales Group are now available in the pricing call request from SAP Cloud for Customer to SAP ERP and SAP S/4HANA.

These major enhancements in the SAP S/4HANA and SAP S/4HANA Cloud areas streamline processes, improve visibility, and enhance integration between SAP Cloud for Customer and SAP S/4HANA systems, facilitating smoother operations and better customer service.

The following list goes over the new features and enhancementsintroduced for Machine Learning Scenarios since version 2111 (Nov 2011).:

• Text Summarization: You can use the Text Summarization model to summarize English texts in Interactions and the Subject field of tickets.
• Search Opportunities by Machine Learning Score: Using advanced filters, search for opportunities based on the score deviations featured by machine learning in the work list. This will enable you to focus and act on opportunities more effectively.
• Preprocess Ticket Text for Machine Translation: Preprocess ticket text data for better detection results from Machine Translation. You can use a BAdI exit and the Cloud Applications Studio SDK to preprocess ticket text for better results from your Machine Translation model​.
• Business Text Intelligence: You can use Natural Language Understanding (NLU) to get actionable insights, such as appointment recommendations based on notes from text analysis, using business text intelligence.
• Product Recommendation: Use the Product Recommendation model to get actionable insights on recommended products.
• Opportunity Closing Prediction Date: You can use machine learning to predict the expected close date of an opportunity that is open or in process.

All these enhancements offer improved functionality and insights, empowering users to make informed decisions and streamlining SAP Sales and Service Cloud processes within Machine Learning Scenarios.