Appendix A: Return Codes/Error codes

Content

For the detailed description of web service requests, please visit WEB-SERVICES documentation.

 

Appendix A: Return Codes/Error codes

 

TAF/TSI Code

PCS CodeName                                       Description                               Sample code helps you to detect the code part
 100SUCCESSThe response indicates that the request SUCCESSFULLY processed.<status>100</status>
 201UNKNOWN_AGENCY_ID Unknown AGENCY ID that can’t be resolved in the system. 
For a list of valid agency IDs, please run the getAllAgencies web service request.
<agency id="2600">
 202UNKNOWN_DOSSIER_TYPE_ID Unknow DOSSIER TYPE ID that can’t be resolved in the system. 
For a valid dossier type ID, please run the getDossier web service request.
 
<dossier_type_id>D</dossier_type_id>
The following Dossier_types are available in the system:
ID    DESCR
D    dossiertype.default
A    dossiertype.change
S    dossiertype.statusQuo
F    dossiertype.ausfall
T    dossiertype.pathAlteration
U    dossiertype.changeInYear
E    dossiertype.pathCancellation
H    dossiertype.partialHarmonization
P    dossiertype.flexPap
 203UNKNOWN_PROGRESS_STATUS_ID Unknown PROGRESS STATUS ID that can’t be resolved in the system. 
For a list of valid progress status IDs, please run the getAllProgressStatuses  web service request.
 <progress_status_id>U</progress_status_id>
 <progress_status_description>Not yet processed</progress_status_description>
5087204UNKNOWN_BRAKE_TYPE_ID Unknown BRAKE TYPE ID that can’t be resolved in the system. 
For a list of valid break type IDs, please run the getAllBrakeTypes web service request. 
<brake_type>
         <brake_type_id>1</brake_type_id>
         <brake_type_short_name>G</brake_type_short_name>
</brake_type>
5134205UNKNOWN_OPERATION_POINT_ID For a list of valid operation point IDs, please run one of the getOperationPointByXYZ web service request. <operation_point id="2084839"> (PCS ID)
 206NO_DOSSIER_FOUND_ERROR Unknown DOSSIER ID. 
For a valid dossier ID, please run the getDossier web service request.
<dossier_id>218260</dossier_id>
5127207UNKNOWN_CALENDAR_ITEM_ERRORUnknown CALENDAR ITEM.
For a valid calendar item ID, please run the getCalendarItemID web service request.
<calendar_item_id>3381325</calendar_item_id>
 208DOSSIER_VERSION_DOES_NOT_EXIST_ERRORUnknown DOSSIER VERSION.
For a valid dossier version number, please the getDossier web service request. 
<change_nr>10</change_nr>
 209DOSSIER_ID_MISSING_ERROR The request is trying to update a dossier, but the DOSSIER ID is missing. 
For a valid dossier ID, please run the getDossier web service request.
<dossier_id>217995</dossier_id>
 211UNKNOWN_PATH_ID Unknown PATH ID that can’t be resolved in the system.
For a valid path ID, please run the getDossier web service request.
 path_id>552758</path_id>
 212UNKNOWN_PATH_SECTION_ID Unknown PATH SECTION ID that can’t be resolved in the system.
For a valid path section ID, please run getDossier web service request. 
<path_section id="3704959">
 215UNKNOWN_COMPOSITION_IDUnknown COMPOSITION ID that can’t be resolved in the system. 
For a valid path composition relation ID, please run getDossier web service request. 
<composition id="69757">
 216UNKNOWN_COMPOSITION_ITEM_IDUnknown COMPOSITION ITEM ID that can’t be resolved in the system.
For a valid composition item ID, please run getDossier web service request. 
<composite_relations>
      <composite_relation id="2100">
            <type>FrequencyTrain</type>
             <name>TUE</name>
             <note>Composition Footnote id</note>
             <starting_dossier_id>218258</starting_dossier_id>
             <composite_relation_dossier id="2461">
                   <composite_relation_id>2100</composite_relation_id>
                           <dossier_id>218258</dossier_id>
                   </composite_relation_dossier>
                   <composite_relation_dossier id="2460">
                           <composite_relation_id>2100</composite_relation_id>
                           <dossier_id>218260</dossier_id>
               </composite_relation_dossier>
        </composite_relation>
  </composite_relations>
 217UNKNOWN_COMPOSITION_FOOTNOTE_IDUnknown COMPOSITION FOOTNOTE ID that can’t be resolved in the system.
For a valid composition footnote ID, please run getDossier web service request.
<note>Composition Footnote id</note>
 218UNKNOWN_CONNECTION_IDUnknown CONNECTION ID that can’t be resolved in the system.
For a valid connection ID, please run getDossier web service request. 
<connection id="122580">
5154221UNKNOWN_TRAIN_TYPE Unknown TRAIN TYPE that can’t be resolved in the system. 
For a list of valid train types, please run the getTrainTypes web service request.
The train type can either be Passenger or Cargo (as defined by <dossierdata>/<is_cargo> flag).
 <train_type_id>1000</train_type_id>
(<train_type_description>Passenger</train_type_description>)
5209222INVALID_IM_PARAMETER_VALUE_ERRORInvalid IM PARAMETER value.
For a list of valid IM parameter values, please run the getImParameters by IM Agency or run one of the getImParametersForXXX web service requests.
getImParameters request example:
<national_im_parameters id="4121" mandatory="true">
            <name>M-AMA Bestellung</name>
            <type>single choice list</type>
            <valid_values>Ja||Nein</valid_values>
            <scope>dossier-level</scope>
            <is_hidden>false</is_hidden>
            <description>National Path request alright made in M-AMA?</description>
 </national_im_parameters>
 223UNKNOWN_DOSSIER_STATUS_ID Unknown DOSSIER STATUS ID that can’t be resolved in the system. 
For a list of valid dossier status IDs, please run the getDossierProcessPhases web service request.
Please define the process_type_id and the dossier_type_id to generate the list.
<dossier_status_id>T</dossier_status_id>
 224INVALID_TIME_FORMATThe request contains path section arrival or departure time that can’t be interpreted in the system. The supported formats are: 
- HH:mm:ss, 
- HH:mm, 
- H:mm:ss, 
- H:mm, 
- HH.mm, 
- H.mm, 
- HH-mm, 
- H-mm, 
- HH mm, 
- H mm, 
- HHmm.
 
 225INVALID_AGENCY_TYPE The request contains AGENCY TYPE ID that can’t be resolved or the referenced AGENCY ID should not be used in that context (e.g. IM agency is set as responsible in the Applicant timetable). 
For a list of valid agency type IDs, please run the getAgencyTypes web service request.
<agency_type_id>EVU</agency_type_id>
 226UNKNOWN_GOODS_TYPE_IDUnknown GOODS TYPE ID that can’t be resolved in the system. 
For a list of valid good type IDs, please run the getGoodsTypesByXYZ web service request.
 
 228UNKNOWN_BAN_WAGGON_IDUnknown BAN WAGON ID that can’t be resolved in the system. 
For a list of valid ban wagon IDs, please run the getBanWaggonTypes web service request
<ban_waggon_type_id>R</ban_waggon_type_id>
 229UNKNOWN_CARGO_BRAKE_TYPE_IDUnknown CARGO BREAK ID that can’t be resolved in the system. 
 230INVALID_OP_VALIDITY_PERIODInvalid operation point's VALIDITY PERIOD (<valid_to> is before <valid_from>).
For a list of valid operation point validity period, please run one of the getOperationPointByXXX web service request.
 <valid_from>1990-01-01+01:00</valid_from>
 <valid_to>2099-12-31+01:00</valid_to>
 231DUPLICATE_REFERENCE_IDDuplicate REFERENCE ID. The reference ID is already defined on a national level (for the country) in the system. 
For a valid REFERENCE ID, please run  the  getOperationPointByReferenceId web service request.
<reference_id>01016</reference_id> (PLC code)
 232DUPLICATE_ENEE_IDDuplicate ENEE_ID  in the system.
For a valid enee ID, please run  the  getOperationPointByReferenceId web service request and check for duplication.
<enee_id>55010165</enee_id>
5134233INVALID_ENEE_ID Invalid ENEE ID in the system. 
For a list of valid enee_IDs, please run the getOperationPointByXYZ web service request.
The ENEE_ID should be 6 or 8-digit long.
<enee_id>55010165</enee_id>
 234INVALID_DATE_FORMATInvalid DATE FORMAT that can’t be resolved in the system. 
The supported formats are: 
- dd.MM.yyyy, 
- dd.MM.yyyy HH:mm:ss.
<first_date>13.12.2020 00:00:00</first_date>
 237UNKNOWN_TIMETABLE_PERIODFor a list of valid timetable period IDs, please run the getTimetablePeriods web service request. <timetable_period id="2021">
 238UNKNOWN_PROCESS_TYPE_IDUnknown PROCESS TYPE ID that can’t be resolved in the system. 
 239MANDATORY_LEADING_RU_ID_MISSING_ERRORThe request doesn't contain info about the leading Applicant and it cannot be extracted from the context (e.g. the system recognizes that the user belongs to an IM agency and she is trying to create a dossier which is not of Catalogue process type).
For a list of valid Applicant IDs in the dossier, please run the getRUIMPairsForDossier or getRUUserDataForDossier web service requests.
<leading_ru_id>
       <agency_id>323</agency_id>
 </leading_ru_id>
 240MINIMUM_NUMBER_OF_PATH_SECTIONS_ERRORSub-paths must contain at least two path sections. 
 241MANDATORY_RU_PATH_MISSING_ERRORAll process types except Catalogue must have a defined Applicant timetable.<tt_ru>
 242INVALID_CALENDAR_ITEM_BITFIELD_ERROR Invalid calendar bitfield

<bitfield>00100000010000001000000100000010000001

000000100000010000001000000100000010000001000

000100000010000001000000100000010000001000000

100000010000001000000100000010000001000000100

000010000001000000100000010000001000000100000

010000001000000100000010000001000000100000010

000001000000100000010000001000000100000010000

001000000100000010000001000000100000010000001

00000010000</bitfield>


The bitfields are representing the requested running days in

the calendar (365 days=365 bits) with the indication of

'0'=not running and with the value of '1'=running. 

 244 TRAFFIC_PERIOD_NAME_ALREADY_IN_USE_ERRORTRAFFIC PERIOD NAME is already in use in the system on the national level (in the country).<name>2021<name>
 245AGENCYGROUP_TRAFFIC_PERIOD_ALREADY_IN_USE_ERRORThe TRAFFIC PERIOD is already used in the system or it has been defined on the national level (in the country) for the given bitfield. 
For a list of valid traffic periods for the country, please run the getTrafficPeriodsForAgencyGroup web service request.
 
 246UNKNOWN_TRAFFIC_PERIOD_IDUnknown TRAFFIC PERIOD ID that can’t be resolved in the system. 
For a list of valid traffic period IDs, please run the getTrafficPeriodsForAgencyGroup web service request.
 
5136247UNKNOWN_OPERATIONPOINT_REFERENCE_IDUnknown OPERATIONPOINT REFERENCE ID that can’t be resolved in the system. 
For a list of valid operation point with reference IDs, please run the getOperationPointByRefrenceIds web service request.
 <reference_id>01016</reference_id> (PLC code)
 248UNKNOWN_AGENCY_UIC_IDUnknown agency UIC ID that can’t be resolved in the system. 
For a list of valid UIC IDs, please run the getAllAgencies web service request.
<agency id="2600">
5136252INVALID_REFERENCE_ID Invalid REFERENCE ID. It could be an empty value or it could be that mandatory value is missing. 
 253USED_AGENCY_IS_NOT_INVOLVED_IN_DOSSIER  The AGENCY is not involved in the dossier.
For a list of valid agencies, please run the getDossier or the getAllAgencies web service requests.
 
 262CURRENT_RU_IM_PAIR_MISSING_ERROR  The request represents an update of the dossier but there is no information which Applicant - IM pair should be used for the update. 
For a list of valid Applicant - IM pair, please run the getRUIMPairForDossier web service request.
<ru_im_pair_id>128586</ru_im_pair_id>
 263UNKNOWN_RU_IM_PAIR_ID Unknown APPLICANT - IM PAIR ID that can’t be resolved in the system. 
For a list of valid Applicant - IM pair ID, please run the getRUIMPairForDossier web service request.
<ru_im_pair_id>128586</ru_im_pair_id>
 264USER_NOT_PART_OF_CURRENT_RU_IM_PAIRThe user is not part of the Applicant - IM pair for which the update is performed.
For a list of valid Applicant - IM pair ID, please run the getRUIMPairForDossier web service request to find the correct pairs.
 
 <ru_im_pairs>
          <ru_im_pair id="128887">
                  <dossier_id>218260</dossier_id>
                  <ru_id>
                        <agency_id>323</agency_id>
                   </ru_id>
                   <im_id>
                         <agency_id>229</agency_id>
                   </im_id>
                   <ru_progress_status_id>P</ru_progress_status_id>
                   <im_progress_status_id>U</im_progress_status_id>
                   <dossier_status_id>D</dossier_status_id>
                   <process_type_id>L</process_type_id>
                   <national_im_parameters/>
         </ru_im_pair>
  </ru_im_pairs>
 265CURRENT_RU_IM_PAIR_NOT_INVOLVED_IN_DOSSIER The  APPLICANT - IM PAIR is not involved in the dossier. 
For a list of valid Applicant - IM pair ID, please run the getRUIMPairForDossier web service request to find the correct pairs.
 <ru_im_pairs>
          <ru_im_pair id="128887">
                  <dossier_id>218260</dossier_id>
                  <ru_id>
                        <agency_id>323</agency_id>
                   </ru_id>
                   <im_id>
                         <agency_id>229</agency_id>
                   </im_id>
                   <ru_progress_status_id>P</ru_progress_status_id>
                   <im_progress_status_id>U</im_progress_status_id>
                   <dossier_status_id>D</dossier_status_id>
                   <process_type_id>L</process_type_id>
                   <national_im_parameters/>
         </ru_im_pair>
  </ru_im_pairs>
 272MANDATORY_IM_PATH_MISSING_ERRORThe request represents a dossier transition but the mandatory IM path is missing.<tt_im>
5208273UNKNOWN_IM_PARAMETER_ERRORUnknown IM PARAMETER ID that can’t be resolved in the system. 
For a list of valid IM parameters, please run the getImParameters web service request.
 
5135274UNKNOWN_COUNTRY_CODEUnknown COUNTRY CODE that can’t be resolved in the system. 
For a list of valid COUNTRY CODEs, please run the getAllCountryCodes web service request. 
 <country_code>FR</country_code>
 <country_name>France</country_name>
5205275UNKNOWN_CORRIDOR_CATALOGUE_IDUnknown CORRIDOR CATALOGUE ID that can’t be resolved in the system.
For valid corridor catalog IDs, please run the getCatalog web service request.
 
 276UNKNOWN_PARAMETER_SET_CODEUnknown PARAMETER SET CODE that can’t be resolved in the system.
Please define a valid parameter set code.
<parameter_set_code>...</parameter_set_code>
5166277UNKNOWN_LOCO_IDENT Unknown LOCO IDENT ID that can’t be resolved in the system. 
For a valid loco type number, please run the getDossier web service request.
 
<loco_ident id="3853349">
5167278UNKNOWN_LOCO_TYPE_NUMBER Unknown LOCO TYPE number. 
For a valid loco type number, please run the getDossier web service or check the available loco types in the GUI by going to Loco Types submenu.
The planned implementation of the getLoco web service will be around  September this year.
<loco_type_number>1116</loco_type_number>
5169279UNKNOWN_TRAIN_CC_SYSTEM Unknown TRAIN CC system that can’t be resolved in the system. 
For a list of valid train CC system, please run the getTrainCCSystemCodes web service request.
<trainccsyst_id>1024</trainccsyst_id>
<trainccsyst_description>EVM</trainccsyst_description>
5170280UNKNOWN_TRAIN_RADIO_SYSTEMUnknown TRAIN RADIO system that can’t be resolved in the system. 
For a list of valid train radio system, please run the getTrainRadioSystemCodes web service request. 
 <train_radio_system_id>1000</train_radio_system_id>
 <train_radio_system_description>GSM-R</train_radio_system_description>
5168281UNKNOWN_TRACTION_MODEUnknown TRACTION MODE that can’t be resolved in the system. 
For a list of valid traction mode, please run the getTractionModes web service request. 
 <traction_mode_id>11</traction_mode_id>
 <traction_mode_description>Train traction-1st traction unit in the group</traction_mode_description>
 282UNKNOWN_PATH_SECTION_EXCEPTIONAL_GAUGING_IDENTUnknown path section's an EXCEPTIONAL GAUGING IDENT ID that can’t be resolved in the system. 
For a list of valid exceptional gauging indents IDs, please run the getDosssier web servcie request.
<exception_gauging_ident_id>1000</exception_gauging_ident_id>
 283UNKNOWN_EXCEPTIONAL_GAUGING_IDENT Unknown path section's an exceptional GAUGING IDENT ID that can’t be resolved in the system. 
For a list of valid exceptional gauging ident IDs, please run the get ExceptionalGaugingIdents web service request.
<exception_gauging_ident_id>1000</exception_gauging_ident_id>
 284UNKNOWN_DANGEROUS_GOODS_INDICATION The request contains the path section's DANGEROUS GOODS indication ID that can’t be resolved in the system.
For a list of valid dangerous goods indication, please run the getGoodsTypesByCargoTypeEneeId or run the getDossier web service requests.
<dangerous_goods_indication_id>70700</dangerous_goods_indication_id>
 285UNKNOWN_PACKAGE_GROUP Unknown PACKAGE GROUP ID that can’t be resolved in the system. 
For a valid package group ID, please run the getDossier web service request.
<package_group id="3080">
5154287UNKNOWN_TRAINTYPE_ID Unknown TRAIN TYPE that cannot be found in the system.
For a list of a valid train type system, please run the getTrainType web service request.
 
<train_type_id>1001</train_type_id>
 288MISSING_TIME_ON_REFERENCE_POINTThe request is missing mandatory arrival/departure times for the selected reference point. 
 293UNKNOWN_PATH_SECTION_ACTIVITY_TYPEUnknown path section's ACTIVITY TYPE ID that can’t be resolved in the system. 
For a valid path section's activity types, please run the getDossier web service request.
<activity_type id="3831607">
5202294UNKNOWN_ACTIVITY_TYPEUnknown ACTIVITY CODE that can’t be resolved in the system. 
Please consult getActivityTypes operation for a list of valid entries.
<activity_type_id>1000</activity_type_id>
 295UNKNOWN_TILTING_FUNCTION_IDUnknown TILTING FUNCTION that can’t be resolved in the system. 
For a list of valid tilting functions, please run the getAllTiltingFunctions web service request.
<tilting_function_id>1000</tilting_function_id>
<tilting_function_description>Active tilting</tilting_function_description>
 296TRAIN_PARAMETERS_NOT_IN_LINE_WITH_TRAIN_TYPE_ERRORThe request contains either: 
1.) passenger train parameters for cargo dossier or 
2.) cargo train parameters for passenger dossier.
 
 298MORE_THEN_ONE_AGENCY_FOR_UICID_ERRORInvalid AGENCY UIC ID that can't be resolved in the system.
For a list of valid UIC ID, please run the getAllAgencies web service request if it is registered for the agency.
<uic_id>0071</uic_id>
 300INVALID_TRAIN_PARAMETER_VALUEThe request contains a path section where either: 
1.) Train weight < Weight of set of carriages, 
2.) Train length < Length of a set of carriages, 
3.) Max speed < Highest planned speed.
 
 301UNAUTHORIZED_ERRORNo authentication information found for protected operation. ( eg.: the authentication header contains an old code value. When authentication is done for Test 1 system and trying to run the request in the Production environment.) 
5039302INSUFFICIENT_PRIVILEGES_ERRORThe request represents an operation for that the user does not have the privilege. Some examples would be the user trying to modify dossier segments (e.g. add comments, change leading agency…) when she has no sufficient access rights.  
 303STALE_DATA_ERRORThe request represents an update of a dossier but it contains stale data. Please use getDossier to retrieve the up-to-date dossier data. 
5030307INVALID_STATE_TRANSITION_ERROR The request represents an update of a dossier, but the transition is not a valid one. Please check the process type and dossier status in the request.  
 310ACCEPT_DOSSIER_NOT_ALLOWED_DUE_TO_MISSING_TRAIN_PARAMSThe dossier progress status cannot be changed to green because of missing mandatory train parameters. 
 500PING_FAILEDConstant for ping fail status. 
 501SYSTEM_ERRORA system error indicates a programming bug. 
 601UNKNOWN_PATH_SECTION_LOCATION_TYPE Unknown path section's LOCATION TYPE ID that can’t be resolved in the system.
For a  valid path section's location type ID, please run the getDossier web service request.
<location_type id="1711168">
 602UNKNOWN_LOCATION_TYPEUnknown LOCATION CODE that can’t be resolved in the system. 
For a list of valid location codes, please run the getLocationTypes web service request.
<location_type_id>1000</location_type_id>
 603UNKNOWN_PATH_ALTERATION_TYPEThe start of the Path Alteration process contains an unknown PA type. 
 604UNKNOWN_PATH_MODIFICATION_TYPEThe start of the Path Modification process contains an unknown PM type. 
 607TIMETABLE_PERIOD_IS_NOT_ACTIVE_FOR_DOSSIER_CREATIONThe request is a dossier creation for a timetable period that is still NOT open for editing. 
For a list of valid timetable periods, please run the getTimetablePeriods web service request.
 
 610UNKNOWN_DOSSIER_RUIMPAIR_PARAMETER_ID Unknown DOSSIER LEVEL PARAMETER that can’t be resolved in the system.
For a valid dossier-level parameter, please run the getDossier web service request.
It is declared in the <ru_im_pairs> section at following way:
 <national_im_parameter id="182346">
         <name>Type of freight train</name>
          <value>Ko - International corridor freight train (45)</value>
 </national_im_parameter>
 615INVALID_VALIDITY_PERIODInvalid VALIDITY PERIOD that could not be resolved in the system.
For a valid validity period, please run the getDossier web service request and search for the validity period.
<validity_period>13.12.2020-11.12.2021</validity_period>
 618UNKNOWN_PATH_ALTERATION_REJECTION_CAUSEUnknown REJECTION TYPE that could not be resolved by the system. 
For a list of valid rejection types, please run the getPathAlterationRejectionCause web service request.
 
 619UNKNOWN_PATH_MODIFICATION_REQUEST_REJECTION_CAUSEUnknown REJECTION TYPE that could not be resolved by the system. 
 For a list of valid rejetion type, please run the getPathModificationRequestRejectionCause web service request
 
 620UNKNOWN_PATH_MODIFICATION_OFFER_REJECTION_CAUSEUnknown REJECTION TYPE that could not be resolved by the system. 
For a list of valid rejection types, please run the getPathModificationOfferRejectionCause web service request.
 
 621UNKNOWN_PAP_REQUEST_IDUnknown PAP REQUEST ID that can't be resolved in the system.
For a valid PaP request ID, please run the getDossier web service request.
<pap_request_id>20544</pap_request_id>
5205622PAP_REQUESTS_NOT_RESERVED_ERRORNot all PaP REQUESTs inserted in the dossier are reserved.
To check the PaP request status, please run the getDossier web service request.
<status>RESERVED</status>
 623PARTIAL_OFFER_REQUEST_REASON_EMPTYThe reason for starting a partial offer is empty. 
 624PROGRESS_STATUS_DOWNGRADE_REASON_EMPTYThe reason for the progress status downgrade of the agency is empty. 
5205625INVALID_CORRIDOR_ID Invalid CORRIDOR ID that can't be resolved in the system.
For a list of valid corridor IDs, please run the getAllCorridors or the getDossier web services request.
<corridor id="1003">
 634DOSSIER_REJECTION_CAUSE_EMPTYMandatory rejection cause missing when IMs try to reject dossier from Path Request or Path Elaboration. 
 637ACCEPT_DOSSIER_NOT_ALLOWED_DUE_TO_MISSING_OPERATION_POINTSThe acceptance of the dossier is not allowed because not all locations are entered by the user. 
5205638UNKNOWN_CATALOG_DOSSIER_IDUnknown CATALOG DOSSIER ID that can’t be resolved in the system.
For valid catalog IDs, please run the getDossier or the getCatalogs web service requests.
 
 639MISSING_MANDATORY_TIMESThe CATALOG DOSSIER is missing mandatory times.
Please define the mandatory times in the catalog.
 
 640WRONG_PARENT_ID Incorrect parent ID. 
 641USED_PATH_ID_DOES_NOT_BELONG_TO_DOSSIERThe request contains a PATH ID that is not part of the dossier.
For valid path IDs, please run the getDossier web service request.
path_id>552758</path_id>
 642USED_OPERATION_POINT_ID_DOES_NOT_BELONG_TO_PATH_SECTION_IN_REFERENCED_PATHThe request contains the path section's OPERATION POINT ID that doesn’t belong to the path section in the referenced path.
For a valid path section's operation point ID, please run the getDossier web service request.
<from_op_id>117236</from_op_id>
 643UNKNOWN_OBSERVATION_TYPE_IDUnknown OBSERVATION TYPE ID that can’t be resolved in the system. 
For a list of valid observation type ID, please run the getObservationTypes web service request. 
 <observationType>
         <observation_type_id>1</observation_type_id>
         <observation_type_description>Route not correct</observation_type_description>
  </observationType>
 644GENERAL_TERMS_AND_CONDITIONS_NOT_ACCEPTEDIf the dossier contains a PaP request then ALL FREIGHT APPLICANTS must accept the CORRIDOR's GENERAL TERMS and CONDITIONS!
To read more about it please visit the document library:  https://cms.rne.eu/pcs/pcs-documentation-0/how-accept-general-terms-and-...
 
 645TRAIN_ID_IS_NOT_DEFINED The TSI TRAIN ID or PATH ID definitions are missing.
To check, please run the getDossier web service request.
<train_id> or  <tsi_path_id>
 646USED_PATH_SECTION_ID_DOES_NOT_BELONG_TO_DOSSIERThe request contains a PATH SECTION ID that is not part of the dossier.
For valid path section IDs, please run the getDossier web service request.
<path_section id="3704959">
 647PATH_ID_MISSING_ERROR The request contains a PATH ID that is not part of the dossier.
For valid path IDs, please run the getDossier web service request.
<path_id>?</path_id>
 648PATH_SECTION_ID_MISSING_ERRORThe request is trying to update path sections, but no path section id is provided. Please provide a valid path section ID.  
 650NO_CHANGES_FOUND No changes made to the dossier. The dossier version won't be saved. 
 651INVALID_TRAIN_PARAMETER_VALUE_AGAINST_CATALOGUE  Invalid TRAIN PARAMETERs value in the catalog.
To check the catalog train parameters, please run the getDossier or the getCatalog web service requests.
 
 654INVALID_PROCESS_INITIATOR Set Applicant-IM pair ID is not valid to process the initiator. 
 655INVALID_DOSSIER_RUIM_PAIR_ID_MARKED_AS_AFFECTED The dossier's Applicant - IM pair ID marked as affected is not valid (doesn't belong to dossier or it belongs to pair with COSS). 
 657INVALID_ACTION_PROCESSING_OFFER Action in processing PA/PM Offer is not valid. Should be 'A' or 'R'. 
 658UNSATISFIED_TRANSITION_CONDITIONS The transition cannot proceed, because there are conditions that are not satisfied. 
5148659INVALID_DWELL_TIME Invalid DWELL TIME. The dwell time is less than the difference between the departure and the arrival times. 
 660ONLY_RU_SHOULD_HAVE_COMMERCIAL_STATUS Only Applicants should have commercial status. 
 661ONLY_RU_IM_PAIR_BASED_DOSSIERS_HAVE_PROGRESS_STATUS Applicant - IM pair based dossiers should only have traffic lights on Applicant - IM pair based level only. 
 662ONLY_RU_SHOULD_HAVE_PRODUCTION_FLAGOnly Applicants should have production only flag set. 
 663RU_IM_PAIR_BASED_DOSSIERS_INVALID_DOSSIER_STATUSApplicant - IM pair based dossiers contain dossier status on Applicant - IM pair based level only.
For a list of valid phase description, please run the getDossierProcessPhases web service request.
 
 664RU_IM_PAIR_BASED_DOSSIERS_INVALID_PROCESS_TYPEApplicant - IM pair based dossiers should have process type set on Applicant - IM pair level only.<process_type_id>L</process_type_id>
The following Dossier_Process_types are available:
N    processtype.newPathRequest
L    processtype.latePathRequest
H    processtype.adhoc2PathRequest
Y    processtype.feasibilityStudy
A    processtype.adhocPartiallyHarmonized
E    processtype.pathAlteration
M    processtype.pathModification
R    processtype.adhocPreAccepted
O    processtype.rollingPlanning
 665PRODUCTION_AGENCY_ALREADY_INVOLVED_IN_DOSSIER_PAIRS Production related AGENCY already exists in the dossier. 
 666ONLY_ONE_USER_VARIANT_ALLOWED_FOR_DOSSIER_CREATIONOnly one USER VARIANT is supported during dossier creation. 
 667SUB_PATH_INCORRECT_TSI_VARIANT_ASSIGNEDIncorrect TSI VARIANT assigned.
For a valid TSI variant, please run the getDossier web service request.
<variant>00</variant>
 668PATH_SECTION_MISSING_RU_ID The request contains a path section without a responsible Applicant agency.
For a valid Applpicant ID, please run the getDossier or the getAllAgencies web service requests.
<responsible_ru_agency_id>
     <agency_id>3601</agency_id>
</responsible_ru_agency_id>
 669PATH_SECTION_MISSING_IM_IDThe request contains a path section without a responsible IM agency.
For a valid IM ID, please run the getDossier web service request.
 <responsible_im_agency_id>
      <agency_id>229</agency_id>
</responsible_im_agency_id>
 670INCONSISTENT_CALENDAR Inconsistent CALENDAR on the territory. 
The dossier cannot be accepted, please harmonize the calendar before proceeding further.
 
 671EMPTY_CALENDAR The dossier cannot be accepted because of an empty calendar on the territory.<calendar_item_id>?</calendar_item_id>
 672COMBINED_PAP_NOT_SUPPORTED  COMBINED PaPs are not supported via web service. The request contains a sub-path that is requesting capacity from PaP that is unavailable. 
 673ONLY FUTURE DAYS CAN BE CHANGED FOR SUB-PATHS IN PA/PM  
 674SUB_PATHS_FROM_ANOTHER_TERRITORYThe request contains subpath ids that do not belong to the provided RU-IM pair id. 
 675TERRITORY_WITHOUT_SUB_PATHIt is not allowed to exist territory without subpath. 
 676REFERENCE_ENTITY_ALREADY_EXISTSThe request contains an entity (entity refers to activity type & loco type) for the insert which is already defined in PCS 
 677REFERENCE_ENTITY_USED_IN_DOSSIERThe request contains update or remove the commands for the entity (entity refers to activity type & loco type), but the entity is already used in a dossier as reference data.