docs(0074): add business partner script variants#326
Draft
nicoprow wants to merge 1 commit into
Draft
Conversation
Sebastian-Wurm
suggested changes
Jun 18, 2026
Comment on lines
+270
to
+274
| 1. A sharing member **MAY** supply script variants on input when source data is available in multiple scripts. | ||
| 2. Script variants are passed to the enrichment process as part of the business partner data and are processed like any other attribute. | ||
| 3. The enrichment process **MAY** add or normalise script variants on output, for example by adding a Latin transliteration for a record submitted in a non-Latin script. | ||
| 4. The set of available script codes is operator-defined and published in the Business Partner Data Pool (see CX-0012 Business Partner Data Pool API). The Gate accepts any string value for the script code without validation; unknown codes are resolved by the enrichment process. | ||
| 5. The Gate accepts a script variants list containing duplicate script code entries; deduplication is the responsibility of the enrichment process. |
There was a problem hiding this comment.
If these shall be CACs, they must be in the normative part of the document. As these are suggestions anyway, I'd rather remove the MAY.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
Applies the script variants contribution to the CX-0074 Business Partner Gate API standard, standardising the
scriptVariantsattribute already present in the reference implementation.Script Variants(List of Business Partner Script Variant) to the Business Partner entity in §1.5.2.1BusinessPartnerScriptVariantwith nestedLegalEntityScriptVariant,SiteScriptVariant, andAddressScriptVariant(each with a physical and, where applicable, alternative address variant)Fields standardised in physical address script variant: postal code, city, district, street name/prefix/suffix fields, building, floor, door, company postal code, industrial zone. Fields present in the reference implementation but not meaningful to vary by script (
taxJurisdictionCode, house number, milestone, direction) are intentionally excluded from the standard.Diagrams
business-partner.puml/.svg: removes obsolete commented-out script variant draft and addsBusinessPartnerScriptVariantclass withScriptCode/NamePartsand a composition relation fromBusinessPartnerbusiness-partner-script-variant.puml/.svg: dedicated diagram for §1.5.2.1.2 showing the full script variant hierarchyChange Request
https://github.com/catenax-eV/product-standardization-prod/issues/667