Since the WebIDE is soon replaced by the Business Application Studio - BAS: where is the descriptor editor for the manifest.json ?
Well, I guess the answer is that it is nowhere. But when is it expected to be provided? Does anyone have any insights...
Earlier this year I wrote a Blog Post covering exactly this topic (find my original Blog Post here). Now - September 2020 - it is already time to provide an update as SAP is innovating quickly and made things more simple.
As Blog Posts can't be delet...
Important - this Blog Post is obsolete as of September 9 2020
see my updated Blog Post here
From that day forward the Cloud platform will support RFC calls to On-Premise systems for destinations maintained in the Cloud Foundry Subaccount. Speci...
Hi Dominik,you mention in the section local vs remote client copy:"Often the DDIC table definitions differ between the source and target systems due to different releases. Before each remote copy, the Client Copy Tool compares the DDIC table definiti...
of course - that is the classic (consuming RFC was a bit more complicated). You either consume the odata service via a public url:
DATA(lo_http_destination) = cl_http_destination_provider=>create_by_url( '...public url to your odata service ....'...
With the SAP Cloud Connector you can access as well RFCs in the cloud (I described the cloud to on-premise consumption. But the Cloud Connector works both ways). But the proper way - and state of the art - would be to consume/define an Odata service....
Hi Sagar,the reason to connect Cloud with on-premise is so that you can consume an on-premise service (OData or RFC) in a Cloud Foundry service. In my blog I described the consumption of an on-premise RFC in Cloud Foundry ABAP. The same applies if yo...
