Business Unit Details' Business Centre field is a plain text field, not a combo
Table of Contents
This page is a capture in the inbox bucket of the product backlog — a pre-sprint idea, not yet pulled into a sprint as a story.
What
ores.refdata.business_unit.org's *** Detail fields table declares
business_centre_code as a plain line_edit
(businessCentreEdit), so the field is free-text in the generated
dialog. ores.refdata.party.org's equivalent field
(business_center_code) instead uses a flagged_combo widget
(businessCenterCombo, populated via fetch_business_centre_codes,
showing the country flag). Business unit should use the same
flagged_combo configuration.
Why
A free-text business centre field lets a business unit be saved with a code that doesn't correspond to any real business centre, whereas party/counterparty correctly constrain it to a valid, flagged choice. Inconsistent between the two entities that both carry this field.
References
projects/ores.refdata/modeling/ores.refdata.business_unit.orgline ~302 — theline_editrow to change.projects/ores.refdata/modeling/ores.refdata.party.orgline ~319 — theflagged_comboconfiguration to mirror.
See also
- Business Centre — the FpML business centre concept this field references.