You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
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
Additional Information
see also eclipse-tractusx/sig-release#606
The text was updated successfully, but these errors were encountered: