Train ID

Submitted by Anna Géczi on 15 October, 2019 - 09:07
Basic
Description
Summary

Description

  • Train ID consists the following elements:
    • Object type: 2 characters (TR)
    • Company code: 4 digits (RICS or UIC code - user can choose from RU agencies that have UIC ID)
    • Core element: 12 characters
    • Variant: 2 digits (value: '00')
    • Timetable Year: 4 digits (ttp of the dossier)
    • Start-date (optional) <xs:minInclusive value="2012-01-01"/> <xs:maxInclusive value="2097-12-31"/>
  • Train ID should be mandatory element, in order to be compatible with master it's better to be defined as optional element in WS schema, and to return ERROR code if Train ID is not defined
  • This identifier should be stored on the dossier level in the Basic Data (under the international train number field) (should be shown on GUI)
  • Should be defined during the process of dossier creation in dossier wizard
  • Modification of the Train ID is possible only in Open phase (by Leading RU), after releasing the dossier to Harmonization the editing of the Train ID should be disabled
  • Core elementCompany codeVariant and Start date are the fields that should be entered by the user, the rest will be resolved by the system
  • Code list for Object Types:
    • Train: TR
    • Case Reference: CR
    • Path Request: PR
    • Path: PA

Implementation

  • add new columns in dossier table:
    • TSI_CORE_ELEMENT (rename already existing INT_TRAIN_NR_VARIANT to TSI_CORE_ELEMENT)
    • TSI_VARIANT (rename already existing TSI_VARIANT_COUNTER to TSI_VARIANT)
    • TSI_COMPANY_CODE
    • TSI_START_DATE
  • Object type - we know that for TRAIN_ID is 'TR'
  • Timetable period is the same as dossier timetable period
JIRA nr.
https://extranet.netcetera.biz/jira/browse/RNE014-1606
Issue type
Story
Priority
Critical
Details
Taken in Patch Release
Friday, 5 May, 2017