Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tax Jurisdiction Code Attribute for Physical Postal Address of Business Partner Data Management Gate and Pool APIs #955

Closed
Sebastian-Wurm opened this issue May 29, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@Sebastian-Wurm
Copy link

Sebastian-Wurm commented May 29, 2024

Description

As a data steward and indirect consumer of the BPDM Gate and Pool APIs, I want to include and manage the tax jurisdiction code for the physical postal address of each business partner record, so that I can ensure precise tax calculation, compliance with tax regulations, and accurate reporting based on the tax jurisdiction of each business partner's location in my business processes.

Acceptance Criteria

  • the Gate API (and its documentation) must be updated to include the "taxJurisdictionCode" attribute for the physical postal address of a business partner in the request and response payloads for create, update, and retrieve operations.
  • the Pool API (and its documentation) must be updated to include the "taxJurisdictionCode" attribute for the physical postal address of a legal entity, site and address in the request and response payloads for retrieve operations.
  • the "taxJurisdictionCode" must be an alphanumeric string with no special length restriction (256 chars are OK) to accommodate various jurisdiction coding schemes.
  • the "taxJurisdictionCode" is non-mandatory in both APIs (later in an operating environment it is ensured that the attribute will always be returned in the Gate output and Pool APIs for countries, where the tax jurisdiction code is legally mandatory)

Additional Information

see also eclipse-tractusx/sig-release#606

@Sebastian-Wurm Sebastian-Wurm added the enhancement New feature or request label May 29, 2024
@nicoprow nicoprow self-assigned this Jun 20, 2024
nicoprow added a commit that referenced this issue Jun 20, 2024
…dress

- changed API models
- added database column
- adapted the mappings
- enhanced the test data
- updated the api documentation

implements to #955
nicoprow added a commit that referenced this issue Jun 20, 2024
…dress

- changed API models
- added database column
- adapted the mappings
- enhanced the test data
- updated the api documentation

implements to #955
nicoprow added a commit that referenced this issue Jun 25, 2024
…dress

- changed API models
- added database column
- adapted the mappings
- enhanced the test data
- updated the api documentation

implements to #955
@nicoprow nicoprow closed this as completed Jul 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Archived in project
Development

No branches or pull requests

2 participants