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 BPDM architect,
I want that the identifier types used in the Catena-X Portal are in line with the identifier types used in BPDM,
so that identifiers can be correctly assigned to the respective identifier type
when handing them over to the Portal BPDM Gate while onboarding to create BPNs and while managing own company data in the respective Portal UI
when handing them over to GXDCH while onboarding
when they are returned from the BPDM Pool and displayed in the Portal Partner Network
Acceptance Criteria
[criteria 1] Existing identifier types stay for backward compatibility; new company registrations will use the corresponding new identifier types -> old identifier types will need to be removed in the next breaking release (see table below)
[criteria 2] New migration is written to fill bpdm_identifiers and country_assigned_identifiers with the new BPDM identifier types and corresponding GXDCH identifier types
[criteria 3] Where there is no corresponding GXDCH identifier type (see table below) it must be left empty -> registration will not be possible with the corresponding identifier type until GXDCH includes a corresponding source
[criteria 4] Tests are adapted to include the new BPDM identifier types
Existing BPDM Identifier Type Code
New BPDM Identifier Type Code
Corresponding New GXDCH Identifier Type Code
(Local) Name (just for information - is part of BPDM data model)
EU_VAT_ID_AT
AT_EU_VAT_ID
vatID (VIES)
European Union Value-added Tax Identification Number
BE_ENT_NO
BE_ON
local (OpenCorporates)
Ondernemingsnummer
EU_VAT_ID_BE
BE_EU_VAT_ID
vatID (VIES)
European Union Value-added Tax Identification Number
Description
As a BPDM architect,
I want that the identifier types used in the Catena-X Portal are in line with the identifier types used in BPDM,
so that identifiers can be correctly assigned to the respective identifier type
Acceptance Criteria
Additional Information
Feature is planned here: eclipse-tractusx/sig-release#605
The text was updated successfully, but these errors were encountered: