All articles

In the legacy Cloud Application Studio, the system connections are stored in the Windows Registry, path 
\HKEY_CURRENT_USER\SOFTWARE\SAP\SAPCloudApplicationsStudio\<release>\DialogPage\SAP.Copernicus.CopernicusOptionPage
Key: SystemConnections.

Upgrading the legacy Studio was tedious enough, having to manually copy that entry to the registry path of the new version.

In the new (pilot) release, they are stored in a different path and format.

I guess it was the first time that I've translated an SAP report after releasing the code changes to the Q system. But much to my surprise, I wasn't prompted for a transport request when I maintained the translations.

There's a very good article that explains how to transport the translations using transaction SLXT, however what I was really after was how to add those texts to the transport request manually.

Quick note to self - SAP provides the following reports to manage segmentation and target groups:

Wow, this is one for the history books ...

So we had this weird issue during replication from ERP that C4C would throw an error 

The BO 'CUSTOMER_QUOTE' supplied with the message does not match the BO of the current service call; within a service call, it is not allowed to raise messages for other BOs; application component 'LOD-LE-CQP

Nothing was showing in the Dump logs and the Incident Context was inconclusive.

If you're trying to find out in which transport a particular object was changed, you can go to SE03 and use the standard search transport request function. To do that, though, you need to know not only the object name but also the program type etc. - essentially, you need to specify what the entry looks like in the transport request, which may be a bit bothersome.

An easier solution is to look up the corresponding database tables correctly:

CRM Action processing conditions are evaluated in function module SWJ_EVALUATE_PARA_CONDITION

For the actual evaluation set breakpoint in CL_SWF_RLS_BINARY_COMPOP=>IF_SWF_RLS_COMPOP~EVALUATE

If you want to sort on your BPATH statement, the explanatory article by SAP provides an example that starts from the root node. So if you want to  sort a subnode (say to return the standard phone number (irrespective if it's mobile or landline), do it as follows:

BuilStandardAddressRel/BuilStandardAddressPhoneRel/~*[!STD_NO:DT,*]/@CALLER_NO

Explanation:

Attachments of a CRM order object cannot be retrieved via relation. You need to perform a separate BOL query.

This is how SAP ODATA converts the URL query string (e.g. $filter) into the nice select options that you can access in your ABAP code.

The flow is as follows:

Just a few random tricks how to work with the UI DEsigner scripts: