This section describes the available Parameters for the ENOAD module and they are accessible in Administration module, System Setup, Parameter.
Table 1-1 PAR Group ENOAD UK
PAR Name | PAR Value | Description |
---|---|---|
PAR Name |
PAR Value |
Description |
Allow Blank Date |
1 |
1 – Enable to allow blank date for expected guests/crew handling 0 – Disable |
Allow Reuse of Departure-Notice-ID During Arrival |
1 |
1 – Enable to allow reuse of departure-notice-ID during arrival 0 - If Set To FALSE, Use INITIAL Notification When Returning To Port |
CARICOM Countries |
|
Specify the These countries listed will have the country name populated in State element as required for CARICOM submissions to NVMC. For example, |
Default to FNU on Blank UXP_A_FSTN or FIRST_NAME |
1 |
1 – Enable. If the guest first name is null, it defaults the First Name field as “FNU” 0 – Disable. If disabled, the First Name field cannot be null |
ENOAD Web Service SOAPAction |
Obtain from NVMC website the relevant NVMC Web Service SOAP Action for the ENOAD System. |
|
ENOAD Web Service SOAPHeader |
Obtain from NVMC website the NVMC Web Service SOAP Header for the ENOAD System. |
|
ENOAD Web Service URL |
Obtain from NVMC website the NVMC Web Service URL for the ENOAD System. |
|
FIELD TO STRIP |
|
Comma Separated XML Field Name(s) These field(s) will be stripped of invalid characters according to Parameter setting “STRIP INVAL CHAR” For example, |
File Output Folder |
|
Allows output file to be saved to a user-defined local or network path folder. For example, |
Foreign Voyage Type |
|
Specify the Foreign Voyage Type options to be displayed in OHC ENOAD from the Voyage Type drop-down. Uses Comma Delimited values. These values must not be edited unless advised to do so by Oracle Cruise Support as the changes may cause the ENOAD manifest submissions to fail. For example, Foreign To US,Foreign To CARICOM,US To CARICOM,US To Foreign,CARICOM To Foreign,CARICOM To US,Foreign To Saint Lawrence Seaway,Saint Lawrence Seaway To Foreign |
Include VOYAGE_NUMBER During submission |
Voyage Number: 1 - Time Stamp, 2 - Cruise external system identifier 0 – NULL/ or <blank> |
|
Mandatory Birthdate Field |
1 |
1 – Enable the birthdate field as mandatory 0 – Disable birthdate field for guests/crew handling |
Mandatory Field For <ARRIVE> |
|
Specify the mandatory XML fields for These values must not be edited unless advised to do so by Oracle Cruise Support as the changes may cause the ENOAD manifest submissions to fail. For example, |
Mandatory Fields For <CARGO> |
|
Specify the mandatory XML fields for These values must not be edited unless advised to do so by Oracle Cruise Support as the changes may cause the ENOAD manifest submissions to fail. For example,
|
Mandatory Fields For <COMP_CERT> |
|
Specify the mandatory XML fields for These values must not be edited unless advised to do so by Oracle Cruise Support as the changes may cause the ENOAD manifest submissions to fail. For example, |
Mandatory Fields For <CONTACT> |
|
Specify the mandatory XML fields for These values must not be edited unless advised to do so by Oracle Cruise Support as the changes may cause the ENOAD manifest submissions to fail. For example, |
Mandatory Fields For <CREW> |
|
Specify the mandatory XML fields for These values must not be edited unless advised to do so by Oracle Cruise Support as the changes may cause the ENOAD manifest submissions to fail. For example, |
Mandatory Fields For <DEPART> |
|
Specify the mandatory XML fields for These values must not be edited unless advised to do so by Oracle Cruise Support as the changes may cause the ENOAD manifest submissions to fail. For example, |
Mandatory Fields For <ISSC> |
|
Specify the mandatory XML fields for These values must not be edited unless advised to do so by Oracle Cruise Support as the changes may cause the ENOAD manifest submissions to fail. For example, |
Mandatory Fields For <LAST_PORT> |
|
Specify the mandatory XML fields for These values must not be edited unless advised to do so by Oracle Cruise Support as the changes may cause the ENOAD manifest submissions to fail. For example, |
Mandatory Fields For <NEXT_PORT> |
|
Specify the mandatory XML fields for These values must not be edited unless advised to do so by Oracle Cruise Support as the changes may cause the ENOAD manifest submissions to fail. For example, |
Mandatory Fields For <NONCREW> |
|
Specify the mandatory XML fields for These values must not be edited unless advised to do so by Oracle Cruise Support as the changes may cause the ENOAD manifest submissions to fail. For example, |
Mandatory Fields For <NONCREW> 1 |
|
Specify the mandatory XML fields for These values must not be edited unless advised to do so by Oracle Cruise Support as the changes may cause the ENOAD manifest submissions to fail. For example, |
Mandatory Fields For <NOTICE_DETAILS> |
|
Specify the mandatory XML fields for These values must not be edited unless advised to do so by Oracle Cruise Support as the changes may cause the ENOAD manifest submissions to fail. For example, |
Mandatory Fields For <PREVIOUS_FOREIGN_PORT_LIST> |
|
Specify the mandatory XML fields for These values must not be edited unless advised to do so by Oracle Cruise Support as the changes may cause the ENOAD manifest submissions to fail. For example, |
Mandatory Fields For <REPORTING_PARTY> |
|
Specify the mandatory XML fields for These values must not be edited unless advised to do so by Oracle Cruise Support as the changes may cause the ENOAD manifest submissions to fail. For example, |
Mandatory Fields For <SFTYMGMT_CERT> |
|
Specify the mandatory XML fields for <SFTYMGMT_CERT> element that eNOAD program checks during file creation. Use Comma Delimited Values. These values must not be edited unless advised to do so by Oracle Cruise Support as the changes may cause the ENOAD manifest submissions to fail. For example, ISSUED_DT,EXPIRATION_DT,AGENCY |
Mandatory Fields For <VESSEL> |
|
Specify the mandatory XML fields for These values must not be edited unless advised to do so by Oracle Cruise Support as the changes may cause the ENOAD manifest submissions to fail. For example, |
Mandatory Fields For <VESSEL_LOC> |
|
Specify the mandatory XML fields for These values must not be edited unless advised to do so by Oracle Cruise Support as the changes may cause the ENOAD manifest submissions to fail. For example, |
Mandatory Fields For <VOYAGE> |
|
Specify the mandatory XML fields for These values must not be edited unless advised to do so by Oracle Cruise Support as the changes may cause the ENOAD manifest submissions to fail. For example, |
Mandatory First Name Field |
1 |
1 - First Name Mandatory for expected crew or passengers 0 – Not mandatory for First Name Only crew/passenger records that contain this information is included in ENOAD Manifest submission when expected crew/passenger is chosen during file creation. |
Mandatory Gender Field |
1 |
1 - Gender is mandatory for expected crew or passengers 0 – Not mandatory for gender Only crew/passenger records that contain this information is included in ENOAD Manifest submission when expected crew/passenger is chosen during file creation. |
Mandatory ID Field |
1 |
1 - Passport (or other form of identification) is mandatory for expected crew or passengers. 0 – Not mandatory for passport Only crew/passenger records that contain this information is included in ENOAD Manifest submission when expected crew/passenger is chosen during file creation. |
Mandatory Last Name Field |
1 |
1 - Last Name is mandatory for expected crew or passengers 0 – Not mandatory for last name Only crew/passenger records that contain this information is included in ENOAD Manifest submission when expected crew/passenger is chosen during file creation. |
Mandatory Nationality Field |
1 |
1 - Nationality is mandatory for expected crew or passengers 0 – Not mandatory for nationality Only crew/passenger records that contain this information is included in ENOAD Manifest submission when expected crew/passenger is chosen during file creation. |
Manifest Submission Tracker |
|
If specified, a Tracker File is created with matching XML File Name; for example, |
STRIP INVAL CHAR |
|
Comma Separated ASCII Code(s) Specify the non-alphanumeric characters (in ASCII Code) that will be stripped from the passenger/crew records section in the ENOAD Manifest. Specify the fields to which this handling needs to be applied in FIELDS TO STRIP parameter. For example, 33,35,36,37,38,42,61,91,93,94,123,125 |
Source Column For Record Locator |
|
Specifies the Database Column Used for For example, |
UNSUBMITTED NONCREW FIELDS |
|
Comma Separated XML Field Name(s) Specify the XML elements that should have their value left empty even if the information exists. This should only be done for non-mandatory fields that are known to contain data not formatted to NVMC specifications. For example, |
Gender Description List |
<Gender_Desc> |
To specify XML fields for <GENDER> element which ENOAD will check for upon file creation. Use <> Delimited Values. For example, <Male><Female><Other> |