Day: December 5, 2017

Whether we’re developing statistical models, training machine learning recognizers, or developing AI systems, we start with data. And while the suitability of that data set is, lamentably, sometimes…

… https://goo.gl/Dhg8hm #BigData #Analytics

Java Messaging Service (JMS) is an API that is capable of creating, sending, and reading messages. JMS provides loosely coupled, reliable, and asynchronous communication functionality. Hence, JMS is used in enterprise applications to integrate multiple systems together.

When it comes to integration, it is paramount to guarantee the reliability of the overall solution as to not lose any message passing through the solution. This is where the JMS transactionality comes in handy, where you can read a message transactionally from a JMS queue and after performing all the required logic on the message, you can either commit or rollback the message. In the case of committing the message, it will be removed from the source queue, and in the case of a rollback, the message will remain in the JMS queue for a successive re-try attempt. https://goo.gl/2TCi9G #DataIntegration #ML

Direct navigation in CRM WebUI

Use this url for example: https://:44354/sap(bD1lbiZjPTAwMSZkPW1pbg==)/bc/bsp/sap/crm_ui_start/default.htm?crm-object-type=BPFS&crm-object-action=B&crm-object-value=120&crm-object-keyname=PARTNER the overview page of business partner with id 120 in current application server could directly be opened: How does CRM WebUI framework know which target UI view should be used for rendering? In the url the CRM object type BPFS and action B ( display ) is specified, both of which are used for target UI view resolvation. In my example, the determined target ID is TBPFSOV. This mapping is configured in customizing below: This target ID will further be used to determine the target WebClient UI component view. The mapping between a target ID and corresponding UI component is maintained in customizing below:

Direct navigation in CRM Fiori

Sample url: http://:50033/sap/bc/ui5_ui5/ui2/ushell/shells/abap/FioriLaunchpad.html?sap-client=001&sap-language=EN#Lead-manageLead&/detail1/Leads(guid’40F2E963-AFAA-1EE5-88AD-D6FD7FB9D1CE’) Semantic object Lead and action “manageLead” are specified in the url. How Fiori knows which UI5 view is used as target UI for rendering? Open the Catalog page in Fiori catalog designer: The combination of semantic object plus action used in my example leads to the target Fiori application with alias “MyLeads” in LPD_CUST. Open transaction code LPD_CUST, locate the UI5 application by application alias “MyLeads”. Open the Component.js of this application and the target view, S3, is configured for route pattern “detail1/{contextPath}”. This explains why S3.view.xml and S3.controller.js are loaded in the runtime when the direct url is accessed.

Direct navigation in C4C

Example: https://.c4c.saphybriscloud.cn/sap/public/byd/runtime?bo=COD_OPPORTUNITY_THINGTYPE&nav_mode=TI&param. Key=00163E217B181EE6AFB52FAEC14878E2 And the TI page of given opportunity is displayed. The supported type for corresponding TI page are listed in SAP help. If you monitor network request in Chrome development tool, it is easy to find out that the navigation target, Opportunity TI page, is resolved by a ABAP backend function module OBERON_OBN_TARGET_RESOLVE, which is not visible to C4C customer & partner. http://bit.ly/2iVaKmT #SAP #SAPCloud #AI