|
|
|
Scala Back Office Interface Setup
The Back Office Interface is designed to transfer your revenue information and city ledger to the Scala Back Office System.
Select Configuration>External>Back Office>Interface. Right mouse button click on the interface name to display the Change Interface button. Selecting it displays a pop-up box with all available interfaces. Select the Scala Interface and click OK.
Select Configuration>External>Back Office>Translate. Select Transaction Codes from the selection menu on the screen and the translation code table for the Scala Interface will display on screen.
Code |
Text |
Data Type |
Width |
BOF_CODE1 |
Cost Center |
CHAR |
6 |
BOF_CODE4 |
Project |
CHAR |
6 |
BOF_CODE5 |
Product |
CHAR |
6 |
Therefore, all transaction codes whose revenue will be exported to the Scala Back Office system have appropriate translation for these analysis codes.
Select Configuration>External>Back Office>Configuration>Transaction Codes. After setting the translation codes, the Transaction Codes entry in the configuration menu can be selected from the selection menu on the screen. An overview of all transaction codes is now displayed on the screen. By double clicking the transaction code a Cost Center, Project or a Product can de entered, which are appropriate for that particular transaction code.
Select Configuration>External>Back Office>Define Records>Revenue Records. As part of SID data the revenue record configuration is already set up for the user. The record definitions on the screen define the different records in the export. A double click on one of the entries will display a pop up box with the record details.
Select Configuration>External>Back Office>Define Records>City Ledger Records. As part of SID data the city ledger record configuration is already set up for the user. The record definitions on the screen define the different records in the export. A double click on one of the entries will display a pop-up box with the record details.
Following is the export setup for the Scala Back Office Interface.
Main |
File |
Record |
Export |
Export |
Always Append to File? |
Table Definition |
Group |
General |
1 |
DTL |
Revenue Records |
c:\temp |
'RV'||to_char(rev_trns_date,'rrmmdd')||'.txt' |
N |
BOF_REVENUE_RECORDS |
|
net_amount <>0 |
Order |
Seq. |
Column Name |
Length |
Data Type |
Format |
Align L/R |
1 |
1 |
TRX_DATE |
8 |
DATE |
RRRRMMDD |
R |
2 |
1 |
TRX_DESC |
30 |
CHAR |
|
R |
3 |
1 |
BOF_CODE3 |
10 |
CHAR |
|
R |
4 |
1 |
BOF_CODE2 |
10 |
CHAR |
|
R |
5 |
1 |
NVL(GROSS_AMOUNT,0) |
20 |
NUMBER |
FM999G999G999G999D00 |
R |
6 |
1 |
BOF_CODE1 |
10 |
CHAR |
|
R |
7 |
1 |
BOF_CODE5 |
10 |
CHAR |
|
R |
8 |
1 |
BOF_CODE4 |
10 |
CHAR |
|
R |
Main |
File |
Record |
Export |
Export File Name |
Always Append to File? |
Table Definition |
Group |
General Condition |
1 |
DTL |
City Ledger Transfer |
c:\temp |
'CL'||to_char(city_trns_date,'RRMMDD')||'.txt' |
N |
BOF_CITYLED_RECORDS |
|
|
Order |
Seq. |
Column Name |
Length |
Data Type |
Format |
Align L/R |
|---|---|---|---|---|---|---|
1 |
1 |
ACCOUNT_NO |
30 |
CHAR |
|
R |
2 |
1 |
TRX_DATE |
8 |
DATE |
RRRRMMDD |
R |
3 |
1 |
GUEST_NAME |
30 |
CHAR |
|
R |
4 |
1 |
ADDRESS1 |
30 |
CHAR |
|
R |
5 |
1 |
ADDRESS2 |
30 |
CHAR |
|
R |
6 |
1 |
PHONE |
15 |
CHAR |
|
R |
7 |
1 |
FAX |
15 |
CHAR |
|
R |
8 |
1 |
ZIP |
6 |
CHAR |
|
R |
9 |
1 |
CITY |
30 |
CHAR |
|
R |
10 |
1 |
COUNTRY |
30 |
CHAR |
|
R |
11 |
1 |
INVOICE_NO |
20 |
NUMBER |
|
R |
12 |
1 |
TRX_AMOUNT |
20 |
NUMBER |
FM999G999G999G999D00 |
R |
