Api Gateway code generation #7678
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Changed the call to ask_sentiment and fixed class declaration issues in unit test
github-actions
bot
added
the
SAP ABAP
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Weird timestamp bug?
Log below:
**Error:**CX_SY_CONVERSION_NO_NUMBER: 'The argument '2025-12-13T03:24:31Z' cannot be interpreted as a number'`Root Cause: The API Gateway service returns timestamps in ISO 8601 format (
2025-12-13T03:24:31Z), but the ABAP SDK cannot convert this format to ABAP timestamp format.`
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.