Dear Community members,
We have implemented an open channel campaign action in yMkt cloud, to interface with another system. We have defined certain custom header attributes (via BADI), which are rendered in the Campaign UI for this OC action. ...
For those interested in linking custom tables to the BOL model BT(Business Transactions), here's an update. This is a follow up of the already published wiki Extend BOL model BT with custom tabe type relationship . As of now, the steps involved in th...
Some time ago, I had to develop a custom BOL object for maintaining some custom tables. These were a set of tables linked by relationships. The model implementation came out ok. Since these tables were to be used in the sales environments and t...
BOL programmers will, no doubt, be familiar with the GET_PARENT method. This method will return the parent entity of the current BOL entity. It is very convenient and used often. But, are you aware of the potential pitfall in using this method? ...
I for one, hate to see direct API calls in the UI layer. We tend to follow the "standard" style of coding and it's for the best. But is this applicable in all scenarios? Well, it depends. Having used both the API function modules and BOL for...
I left a similar comment under that blog at the beginning of this year. From a design perspective, what is perplexing is that SAP allows us to define the structure of the CBO, define its semantic keys and yet, it feels the need to impose its own tech...
I'm also interested in this topic. A MERGE is still an update (specific fields) and therefore needs the technical key of the object. Technically, the ODATA PUT request can accommodate UPSERT scenarios, if the keys are known.Where this is thwarted is ...
Hi Saurabh,
Thanks for the answer. But, like I said, forcing the campaign into error is as good as discarding it. You cannot change the campaign design anyway. I understand the reasoning behind disallowing the option to edit the campaign once it is...
I'm still waiting for the day, where this whole "enrichening with SAP UUID" step can be dropped. When doing a post (full data for a Origin ID), the system should be able to determine all that it has to update, delete and insert.
Excellent guide, thanks! But the lack of an upsert function is aggravating. Why is the backend not smart enough to decide if it has to create or update, based on the semantic keys in the supplied data? After all, when we create the custom business ob...
