I had a conversation with SAP folks recently and brought up the future of C4C. My current impression in dealing with SAP Support is that it's "maintenance only" and their logic regarding bugs seems to be: SAP standard always "works as designed", so if the reported behaviour is part of SAP it - naturally - can't be a bug. I also noted that there are hardly any new features in C4C, all attention is on v2.
I recently wrote a reuse function that handled all kinds of scenarios and returned different values. However, I forgot to handle the negative case, i.e. where none of these scenarios apply and no (or an empty) value should be returned.
C4C does something funny in this case: It doesn't just return a "blank" value, it returns the value of the last successful "return".
As we all know, SAP has changed the way exchange rates are replicated with the transition to S/4. In ERP, C4C would pull the exchange rates using a background job. In S/4, the exchange rates are pushed to C4C using a new interface.
Historically, many users preferred the simplicity of "set-and-forget" basic authentication over the hassle of expiring certificates. However, rising security scrutiny has shifted this mindset.
In SAP Cloud for Customer (C4C), switching to inbound certificate-based integration seems straightforward:
C4C has an interesting quirk (I wouldn't go so far and classify it as a bug):
Assume you have a reuse function that returns a value.
In this case, you need to make sure that your script always (i.e. in all scenarios) explicitly (i.e. using the return statement) returns a value.
If you don't, it will return the same value it returned when it was previously called.
When you maintain a communication system in SAP C4C for integration with an SAP backend system (ERP, S/4), you flag the "SAP Business Suite" field and then maintain the "Business Instances".
The terminology has always confused me, but I just came across a pretty old blog by SAP that explains these fields under a somewhat unintuitive title: Communication System Setup and Message Header Hand... - SAP Community.
For a few months now, whenever I've opened a solution in the new Visual Studio 2022 SDK plugin, I've been receiving the annoying warning that my project targets an unsupported version of .NET, asking me whether I want to upgrade the target to .NET 4.8.
It was a mere nuisance, usually clicked okay and could continue to work.
In the new Visual Studio 2022 plugin, it is not possible to create script files (or perform other BO operations) without first checking out and making a dummy edit to any custom BO.
I had created a custom BO yesterday and wanted to proceed with the script files today, when I noticed that I couldn't create them:
The following is the process for installing SAP Cloud Application Studio via the "Visual Studio 2022 plugin" avenue:
According to SAP note 3053335, workflow rule actions that are scheduled “OnSave” are executed BEFORE the BeforeSave. Accordingly, the BeforeSave cannot influence the OnSave action.
However, SAP can enable a backend flag, called “Late Condition Evaluation”.
With that enabled, OnSave actions are executed AFTER the BeforeSave and therefore the BeforeSave suddenly has an influence on the OnSave action.