on 2023 Feb 20 12:34 AM
Hey Guy,
we have a "simple" question: Should fields using alpha conversion been transformed to the representation/outbound format before sending them via an bgRFC call?
Our situation:
We develop a cloud application that should retrieve data from e.g. OnPremise S4/Hana systems.
The data we retrieve includes fields which use a domain with alpha conversion, like order numbers etc.
Since the current OnPremise logic has some problems with an automatic conversion, we started discussing if the alpha conversion (to the representation format) needs to be done before sending it to our Cloud Product or not.
My Opinion:
The data should use the representation/outbound format when send to an external system (our cloud product).
Since the data leaves the system that uses and knows the alpha conversion setting, so the external system has hardly any way to handle it. And our user also expect that our ui works with the outbound format for displaying and filtering our entities.
We could include some code that could handle the removal of, e.g. leading zeros. But we can't just apply the logic to some specific fields, since we allow our data to include customer individual fields/data.
If we take a look at how we retrieve data with the default way of pulling it over the odata api, we get it with the outbound format too.
What experiences have you made with the topic?
Or how do you see the issue, maybe I misunderstood a few things?
Regards,
Florian
Request clarification before answering.
User | Count |
---|---|
98 | |
39 | |
8 | |
5 | |
3 | |
3 | |
3 | |
3 | |
2 | |
2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.