Design predecessor/successor relation for constellation: Legal name change

[zygokaktus]

Description

As CX-member company ... ,
I want to be able to get (provide) predecessor/successor data in case of a re-naming of a company (without any further changes like address or legal form, registration,...) ... ,
so that I can see this information in the CX Pool and have it available in the GATE (and other GATES who have/had business relations with this VP.
-->

Acceptance Criteria

• Relation between predecessor and successor level can be establishd/maintained
• Corresponding BP of all levels (BPNA/BPNS/BPNL) are taken into consideration for this business case
• Provide additional data why such relation has been established ("reason", e.g., Legal name change, ,...)
• Foresee validity intervals and status information of relation (to be ignored?)
• Data model is extended (if necessary) for this relation / business case in both GATE and POOL

Additional Information

Detailed business case for the scope of this task:

• Pure re-naming of a company, e.g., Maier GmbH becomes Maier Solarthermie Gmbh as the field of business acitivity may have changed and shall be expressed in a name adjustment
• Change is maintained in respective business register(s)
• No change of the legal form
• No legal address change
• No change of the responsible courtyard (Handelregister)
• Corresponding, existing BPNA and BPNS (if applicable) are also affected by the changed name
  - Consider site scenario in this feature???

Concept work

Expected results
BPNA level

• Relation between 2 BPNA (predecessor BPNA1 (source) and successor BPNA2 (target) is set up
• Valid from - valid to for BPNA1 dates are filled
• Valid from for BPNA2 is filled --> valid to is empty, BPNA2 status is set to active
• BPNA2 has inheritated the address type for "isLegalAddress" from BPNA1 (may interfere/collide with last bullet point)
• BPNA1 technically remains (number will not be re-used or archived or similar) and is still in the CX-Pool and the linked Gates of the Companies who also have/had a business relation with (subscribed) this BP
• BPNA2 is created through the GR-process (with a corresponding BPNL2 and classified as legal address)

BPNL level

• BPNL remains the same
• The formerly set up relation between BPNL and BPNA1 remains but become inactive due to the status change (inactive) on BPNA-level

Reason codes:
to be discussed:

• Is it useful to have reason codes on different levels or is it better to have it as general/generic information

• Decision after alignment during working session on 08.10.2025:

  • start with overall reason codes, not dedicated/restricted to a respective level of a BP.
  • Further break down of reasons to L/S/A in future for achieving more granularity is in principle technically possible though may cause some efforts.

• Who can provide the information about name change of LE:

[zygokaktus]

@SujitMBRDI @nicoprow @MG2023-RB: Created this feature as next iteration step of predecessor/successor scenarios as discussed yesterday, based on #1381. Will be detailed/sharpened further...