6 Configuration of the SWSHORE Template
The SWSHORE Template synchronizes cruise, group, guest, and special request information from External DB to SilverWhere.
This section describes how to configure the different areas within the SWSHORE Template to meet operational needs.
Note:
To connect successfully to the databases, you must configure the credentials to the External DB as well as the BKSTG_DINING schema:
-
The BKSTG_DINING user must be the default connection to SilverWhere.
-
The External user must be created to connect to the External DB, and ‘External’ must be case-sensitive.
General Functionalities
The table below describes the available settings.
Table 6-1 General
| Function | Description |
|---|---|
|
Ship Code |
Enter the ship code (SHIP.SHIP_CODE) |
|
Group Not Together |
Enter the list of group types where the SEAT_TOGETHER column should be set to N. |
|
Default Product Code |
Enter the default Product that should be used for Dining Reservations if the requested product is not found. Example: DINNER |
|
Default Location Code |
Enter the default Location that should be used for Dining Reservations if the requested location is not found. Example: STEAK |
|
Reservations from External DB to SW |
Enter the excursion codes that should be retrieved from the External DB as Dining Reservations, separated with a semicolon. |
|
Don’t Seat |
Enter the guest type codes that should be used to set the PASSENGER.DONT_SEAT column to ‘Y’. |
|
Suite |
Enter the cabin category codes that should be used to set the PASSENGER.VIP column to ‘Y’. |
|
Special Request Types |
Enter the special request codes that should be imported to SilverWhere. Each value must contain Code, Value and Description, and each setis separated by a semicolon. Code: The External DB code for the special request. Value: The special request provider. Description: The Special Request description. Example: S_SPOCC, F/B, SPECIAL OCCASION;S_VM, DIET, VEGETARIAN MEAL; |
|
Special Request Table Types |
Enter the special request codes that can be converted into SilverWhere dining reservations. The below columns will be updated: WHEELCHAIR, TABLE SIZE, IN_A_SUITE, REQUESTED_SEATING, BACKTOBACK_CRUISE_ID, TABLE Each value must contain Code, Value and Description, and each set will be separated by a semicolon. Example: WLTS_MAIN,REQUESTED_SEATING,1;E_WH,WHEELCHAIR,Y; |
|
Special Request Convert |
Enter the special request codes of the External DB that are longer than the codes maintained in SilverWhere. The values are a combination of External DB code and SilverWhere Code. Example: S_MAIN_5:30PM,S_M5:30PM;S_MAIN_5:45PM,S_M5:45PM; |
|
Seat and Show |
Enter the seat, assigned show, and seating value from the External DB to be used as the SilverWhere passenger information, separated by a semicolon. Example: MAIN,1,1;SECOND,2,2; |
|
Alternate Type |
Enter the value for the External Type, SilverWhere Type, Location, and Product. Example: Sea, Silver, BIST, DINNER |
|
Loyalty Status |
Enter the repeat cruiser value based on the passenger type. Example: GOLD SILVER PLATINUM. |
|
Excluded Cruise Group Status |
Enter the RES STATUS (e.g., CX, WL) to be excluded from getting external cruise group data, separated by a semicolon. |
|
Included Palo records [External DB] with reservation status |
Enter the status of the dining reservations which should be imported, separated by a semicolon. with reservation status Example: BK;CL;TM; |
|
Include Cruise records [External DB] with Event Types |
Enter the event types (e.g., ARRIVAL; AT SEA;) that should be included when retrieving the cruise itinerary data from External DB, separated by semi colon. |
|
Exclude Special Request Status Code [External DB] |
Enter the special request status that should be excluded from the import, separated by a semicolon. Example: Cancel |
|
Include Passenger records [External DB] with Res Status |
Enter the PASSENGER RES STATUS that should be imported, separated by a semicolon. Example: CX;BK;OF;CL;TM; |
|
Log Error into Database |
Enable for writing errors to the BKSTG_DINING.LOG table. |
Importing Cruise Information from External DB to SilverWhere Functionalities
Table 6-2 Importing Cruise Information from External DB to SilverWhere
| Function | Description |
|---|---|
|
1.0 Import Cruise Info from External DB to SW |
Enable to import cruise information from External DB to SilverWhere |
|
1.0.1 Cruise Days Out |
Enter the number of cruise days to import to SilverWhere, current day plus x days. |
|
1.0.2 Group Days Out |
Currently not in use |
|
1.0.3 Guest Days Out |
Enter the number of cruise days to import cruise group data to SilverWhere, current day plus x days. |
|
1.0.4 Delete Old Cruises |
Enter the number of past cruises that should be deleted, current day – x days. |
|
1.0.5 Seat Time |
Enter the restaurant and seat time for Traditional Dining. Each value must contain room, and seat time, separated by a semicolon. |
|
1.0.6 Cruise Show |
Enter the show information that should be imported to SilverWhere. Each value must contain show code, show time, seating, and capacity, separated by a semicolon. |
Table 6-3 Import Cruise Group and Guest Info from External DB to SilverWhere Functionalities
| Function | Description |
|---|---|
|
Import Cruise Group and Guest Info from External DB to SW |
Enable to import group and passenger information. |
|
Log Error into Database . |
Enable for writing to the BKSTG_DINING.LOG table |