fix(Generic): naming of BPN fields in generic business partner #596
Conversation
This file contains 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
nicoprow
changed the title
SujitMBRDI
approved these changes
Nov 3, 2023
fabiodmota
approved these changes
Nov 3, 2023
nicoprow
force-pushed
the
feat/generic-bpn-field-names
branch
from
9427403 to
f296fe7
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
This pull request aligns with the specification of the Generic Business Partner model for BPN fields: #382. I renamed the generic business partner's BPN fields in order to better represent their meaning, as explained in the linked issue.
I changed the code of the API but left entities unchanged.
Fixes #594
Pre-review checks
Please ensure to do as many of the following checks as possible, before asking for committer review: