A P P E N D I X A UNIVERSAL BRIDGE EXTERNAL FILE FORMATS This Appendix outlines the requirements for the external files.
Download ReportTranscript A P P E N D I X A UNIVERSAL BRIDGE EXTERNAL FILE FORMATS This Appendix outlines the requirements for the external files.
Slide 1
A P P E N D I X
A
UNIVERSAL BRIDGE EXTERNAL FILE FORMATS
This Appendix outlines the requirements for the external files that are used for
the Cougar Mountain Universal Bridge feature. This feature imports
transactions into several of the Cougar Mountain Accounting core and AddOn modules: General Ledger, Accounts Receivable, Accounts Payable,
Inventory, Order Entry, Payroll, and Bank Reconciliation.
Slide 2
Import External Transaction File
Import External Transaction File
The External File option allows you to import unposted transactions from an
external data file. The option to import is accessed from different menus
within these modules, as shown in the table below. The following pages
contain the external file requirements for each module.
Table 2:1
Module
752
Menu Option
General Ledger
Journal / Generate Journal Entries From /
External File
Bank Reconciliation
Enter Activity / Generate Activity From /
External File
Accounts Payable
Enter Bills / Generate Bills From / External
File
Payroll
Enter Payroll / Track Daily Units / Generate
Transactions From / External File
Accounts Receivable
Transaction / Generate Transactions From /
External File
Inventory
Adjustments / Generate Adjustments From /
External File
Order Entry
Manager / Generate Orders From / External
File
Cougar Mountain Accounting
Slide 3
Requirements for Importing Transactions from an External File
To import transactions from an external file in the above modules, do the
following:
1. Select the import option from the appropriate menu (see previous table in
this section).
"N
2. Create a new batch into which to import or generate transactions.
ote Transactions can only be imported into or generated in an empty batch. If you
are in single batch mode, you must post or clear any unposted transactions
that are currently in the batch before you can import.
Requirements for Importing Transactions from
an External File
Transactions can only be imported into or generated in an empty batch. If you
are in single batch mode, you must post or clear any unposted transactions
that are currently in the batch before you can import.
The following window appears:
3. Select one of the following file types that describes the file you want to
import:
Column Position File (fixed length): Each field in the file to be
imported starts at a specific position and contains a fixed number of
characters. This file type is sometimes referred to as “fixed length.”
Tab Delimited File: The fields in the file to be imported are separated
by tabs.
Universal Bridge - External File Formats
753
Slide 4
Requirements for Importing Transactions from an External File
Semi-Colon Delimited File: The fields in the file to be imported are
separated by semi-colons.
4. Select Begin Import to start importing the transactions, or Cancel to exit
without importing.
Import Transaction Validation
When transactions are imported, each piece of information is checked to make
sure it is in an acceptable format, required fields are not empty, etc. See the
following pages for the field definitions for each module.
Printing the Import Error Report
If errors were detected during the import process, an error report is generated,
and a message appears. To print the error report, do the following.
1. When the error report message appears, click OK.
Depending on the defaults you set for print options in your Module
Preferences, the Print Options window may appear.
2.
If the Print Options window appears, select the report destination:
Printer, Screen, or File.
If you select Printer or Screen, specify Laser or Dot Matrix. If you
select File, type the output file name. The default is REPORT.TXT. If you
regularly save to a file, the new file will append to the end of the existing
file, so you will not lose previously saved information.
3. Enter the number of copies to print.
By default, one copy will print, unless you enter a different default
number in your Module Preferences, or unless you select File or Screen
as the report output destination.
4. Select OK to print the report or Cancel to exit without printing.
754
Cougar Mountain Accounting
Slide 5
Requirements for Importing Transactions from an External File
Correcting Errors
While it may be possible to correct some of the errors on the error report in
the Cougar Mountain batch file, we recommend clearing the batch, correcting
the errors in the external file, and then importing again.
"N
ote Certain information, such as dates, will be required at posting, but will not be
required at the time of import. Be sure to print an Edit Report and review it
carefully prior to posting. If errors are detected at posting, an error report will
be generated. Use this to correct your entries.
Using the following instructions, correct any errors prior to posting the batch.
Correcting Errors in the External File
1. Edit the transactions in the external file, as necessary.
2. Clear the transactions you previously imported. The menu option used
will vary depending on the module.
3. Import the file again. For more information, see “Import External
Transaction File” on page 752.
Correcting Errors in the Imported Batch
1. Select the option that allows you to enter transactions from the main menu
of the module with which you are working. For example, in Accounts
Payable, select the Enter Bills option on the Enter Bills menu.
2. Use the Find button to locate and select the transaction(s) you want to
change.
3. Select Edit to change the transaction, and update it as needed.
4. Save the corrected transaction.
Universal Bridge - External File Formats
755
Slide 6
Requirements for Importing Transactions from an External File
Requirements for Importing Transactions from
an External File
When you import transactions from an external file using one of the Universal
Bridge options, the information in the file being imported must be in the
correct format to be written to the Cougar Mountain files. For example, fields
must be of the correct lengths and be delimited as expected.
Date Formats
The import will accept the following date formats:
YYYYMMDD__ ...
.If the import is based on column position,
then two spaces will be required on the
end of this format to accept the dates
correctly. Without the two spaces, the
record size will be incorrect.
MM/DD/YYYY ...
..When using this date format, be sure to use
all 4 digits of the year. If all four digits are
not used, the date may not be imported
correctly.
"N
ote Certain information, such as dates, will be required at posting, but will not be
required at the time of import. Be sure to print an Edit Report and review it
carefully prior to posting. If errors are detected at posting, an error report will
be generated. Use this to correct your entries.
756
Cougar Mountain Accounting
Slide 7
Requirements for Importing Transactions from an External File
External Files
The external files must be named as follows, where xxx is your company’s
three-character company code. These files must be located in the CMSWIN
directory (or wherever your Cougar Mountain software is installed).
General Ledger: ...
..GLEXT.xxx
Accounts Receivable: ... ...AREXT.xxx
Order Entry: ...
.OEEXT.xxx
Inventory: ...
...INEXT.xxx
Accounts Payable: ...
..APEXT.xxx
Payroll: ...
..PREXT.xxx
Bank Reconciliation:...
.BREXT.xxx
The external file must be in one of the following file formats: column position
(sometimes referred to as “fixed length”), semicolon delimited, or tab
delimited. The user must indicate which of these formats will be used when
they start the import process.
When information is imported from the external file, it will be imported into
one or two files (see the information contained later in this section) in the
batch selected by the user. The selected batch must be empty or an error
message will display.
Depending on the module you are using, the following files in the selected
batch are updated, where xxx is your company’s three-character company
code, and aaa represents your batch identity.
General Ledger: ...
..xxxGDaaa.DBF and xxxGJaaa.DBF
Bank Reconciliation:...
.xxxBTaaa.DBF and xxxBLaaa.DBF
Accounts Payable: ...
..xxxAIaaa.DBF and xxxAEaaa.DBF
Order Entry: ...
.xxxOTaaa.DBF and xxxOLaaa.DBF
Payroll: ...
..xxxPRDLY.DBF
Accounts Receivable: ... ...xxxATaaa.DBF and xxxALaaa.DBF
Inventory: ...
Universal Bridge - External File Formats
...xxxIHaaa.DBF
757
Slide 8
General Ledger File Format
Transaction numbers will be generated automatically based on the next
available number in the batch.
The file will contain multiple records, each having a CR/LF at the end and an
“H” or “D” as the first character. Records with an “H” at the beginning are
header or master records, and subsequent records with a “D” at the beginning
are the detail lines (sometimes referred to as “child lines”) for that header
record. The remaining pages in this section describe the external file formats
for each of the above modules.
"N
ote In the tables on the following pages, the Field Len column shows the
maximum length of the field; any characters over the specified length will be
truncated. Fields in column position files must be the exact length specified,
whereas fields in semicolon or tab delimited files may be shorter.
General Ledger File Format
The following tables show the requirements for the external file that is used to
import General Ledger journal transactions. The first table shows the file
definitions for the header record, and the second table shows the file
definitions for the detail records.
Table 3: General Ledger Header Record (xxxGJaaa.dbf)
Field Description
Field
Len
Pos
Data Type
Req
Header Identifier
1
01
Char-Caps
Type = “H”
Yes
Transaction Date
10
02
Date
Yes1
Posting Reference
15
12
Char-Caps
Yes
Trans Description
50
27
Character
No
End of Record
02
77
Yes
Maps To
Use to identify Header
Row
GLJHDATE
GLJHREF
GLJHTDES
Nowhere/used as record
separator
Record Length is 78 characters
758
Cougar Mountain Accounting
Slide 9
Accounts Receivable File Format
Table 4: General Ledger Detail Record (xxxGDaaa.dbf)
Field Description
Field
Len
Pos
Data Type
Req
Maps To
Detail Identifier
1
01
Char-Caps
Type = “D”
Yes
Used to identify Detail
Row
Account Number
30
02
Char-Caps
Yes
GLJDACCT
Detail Description
50
32
Character
No
Debit/Credit Flag
1
82
Character
Yes1 GLJDCREDIT
Transaction Amount
14
(11.2)
83
Numeric
No 2 GLJDAMOUNT
End of Record
02
97
Yes
GLJDTDES
Nowhere/used as record
separator
Record Length is 98 characters
"N
otes The Debit/Credit Flag must either be blank or contain a “D” for debit or a “C”
for credit. If left blank, the field defaults to “D.” The “C” must be in the field
for credit transactions to process correctly.
If the Transaction Amount is a negative number, then the import process
reverses the debit/credit flag and makes the transaction amount positive.
Accounts Receivable File Format
The following tables show the requirements for the external file that is used to
import Accounts Receivable transactions. The first table shows the file
760
Cougar Mountain Accounting
Slide 10
Accounts Receivable File Format
definitions for the header record, and the second table shows the file
definitions for the detail records.
Table 5: Accounts Receivable Header Record (xxxATaaa.dbf)
Field Description
Field
Len
Pos
Data Type
Req
Maps To
Header Identifier
1
01
Char-Caps
Type = “H”
Yes
Use to identify Header
Row
Customer Number
20
02
Char-Caps
Yes
ARTHCUST
Source Document
15
22
Char-Caps
Yes
ARTHDOC
Transaction Date
10
37
Date
Yes1
ARTHDATE
Transaction Code
(2,3,4,5,6,7,9)
4
47
Char-Caps
Yes
ARTHTCODE
Description
30
51
Character
No
ARTHTDES
Terms Code
2
81
Char-Caps
No
ARTHTCODE
Transaction Amount
14
(11.2)
83
Numeric
No
ARTHAMOUNT
Electronic? Flag
1
97
Char-Caps
No
ARATEFT (“Y” or “N”)
Bank Account Code
03
98
Char-Caps
No
ARTHBANK
Discount Amount
14
101
Numeric
No
ARTHDISC
CC Payment
1
115
Numeric
No
ARTHCCPMT
CC Code
4
116
Character
No
ARTHCRCD
CC Number
20
120
Character
No
ARTHCRNO
CC Exp Date
5
140
Character
No
ARTHCREX
CC Authorization
Code
15
145
Character
No
ARTHCRAU
CC Processed Flag
1
160
Numeric No
CC Authorization
Flag
1
161
Numeric
No
ARTHCRFL (1=Yes,
0=No)
CC PCCharge
TransNum
10
162
Character
No.
ARTHCCPCTN
Universal Bridge - External File Formats
ARTHCPROC (1=Yes,
0=No)
761
Slide 11
Accounts Receivable File Format
Table 5: Accounts Receivable Header Record (xxxATaaa.dbf)
Field Description
Field
Len
Pos
Data Type
Req
Maps To
CC Address
20
172
Character
No
ARTHCRADDR
CC Zip
9
192
Character
No
ARTHCRZIP
CC Clerk
6
201
Character
No
ARTHCLERK
End of Record
02
207
Yes
Nowhere/used as record
separator
Record Length is 208 characters
"N
otes If the Transaction Date is invalid, an error will be printed on the Import Error
Report. If the Transaction Date is blank, it will be imported as is.
A blank entry in the Electronic (EFT) field will be treated the same as a “0”
(No). If AR is not integrated to BR then the Bank Account Code field in the
Import File will instead be the 3-character EFT Account Code.
Table 6: Accounts Receivable Detail Record (xxxALaaa.dbf)
Field Description
Field
Len
Pos Data Type
Req
Maps To
Detail Identifier
1
01
Char-Caps
Type = “D”
Yes
Used to identify Detail
Row
Document to Pay
15
02
Char-Caps
No
ARTLDOC
Discount Override
1
17
Numeric R:
{0-9}
No1
ARTLDISC
Discount Amount
14(11.2)
18
Numeric
No
ARTLDISAMT
Apply Amount
14(11.2)
32
Numeric
Yes
ARTLAMOUNT
End of Record
02
46
Yes
Nowhere/used as record
separator
Record Length is 47 characters
762
Cougar Mountain Accounting
Slide 12
Order Entry File Format
"N
otes If the Discount Override has a value of 8, then the discount used will be the
amount in the Discount Amount field. (0-No Discount; 1-Discount #1; 2Discount #2; 3-Discount #3; 4-Discount #4; 5-Discount #5; 8-Special
Discount; 9-Normal Discount).
Order Entry File Format
The following tables show the requirements for the external file that is used to
import Order Entry transactions. The first table shows the file definitions for
the header record, and the second table shows the file definitions for the detail
records.
Table 7: Order Entry Header Record (xxxOTaaa.dbf)
Field Description
Field
Length
Pos
Data Type
Req
Maps To
Header Identifier
1
01
Char-Caps
Type = “H”
Yes
Used to identify
Header Row
Shipping Customer
20
02
Char-Caps
Yes
OETHNUM
Shipping Address
35
22
Character
No
OETHADD1
Shipping Address
35
57
Character
No
OETHADD2
Shipping Address
35
92
Character
No
OETHADD3
Shipping Address
35
127
Character
No
OETHADD4
Cash/Check/CC/Chg 1
(0-Cash; 1-Check; 2CCard; 3-AR Charge)
162
Numeric
Yes
OETHPAY
Transaction Type
1
(0-Normal; 1-Hold; 2Quote; 3-Work Order)
163
Numeric
Yes
OETHTYPE
Invoice Number
15
164
Char-Caps
Yes
OETHINVNO
PO Number
20
179
Char-Caps
No
OETHPONUM
Ship Via Code
6
199
Char-Caps
No
OETHSHIP
Universal Bridge - External File Formats
763
A P P E N D I X
A
UNIVERSAL BRIDGE EXTERNAL FILE FORMATS
This Appendix outlines the requirements for the external files that are used for
the Cougar Mountain Universal Bridge feature. This feature imports
transactions into several of the Cougar Mountain Accounting core and AddOn modules: General Ledger, Accounts Receivable, Accounts Payable,
Inventory, Order Entry, Payroll, and Bank Reconciliation.
Slide 2
Import External Transaction File
Import External Transaction File
The External File option allows you to import unposted transactions from an
external data file. The option to import is accessed from different menus
within these modules, as shown in the table below. The following pages
contain the external file requirements for each module.
Table 2:1
Module
752
Menu Option
General Ledger
Journal / Generate Journal Entries From /
External File
Bank Reconciliation
Enter Activity / Generate Activity From /
External File
Accounts Payable
Enter Bills / Generate Bills From / External
File
Payroll
Enter Payroll / Track Daily Units / Generate
Transactions From / External File
Accounts Receivable
Transaction / Generate Transactions From /
External File
Inventory
Adjustments / Generate Adjustments From /
External File
Order Entry
Manager / Generate Orders From / External
File
Cougar Mountain Accounting
Slide 3
Requirements for Importing Transactions from an External File
To import transactions from an external file in the above modules, do the
following:
1. Select the import option from the appropriate menu (see previous table in
this section).
"N
2. Create a new batch into which to import or generate transactions.
ote Transactions can only be imported into or generated in an empty batch. If you
are in single batch mode, you must post or clear any unposted transactions
that are currently in the batch before you can import.
Requirements for Importing Transactions from
an External File
Transactions can only be imported into or generated in an empty batch. If you
are in single batch mode, you must post or clear any unposted transactions
that are currently in the batch before you can import.
The following window appears:
3. Select one of the following file types that describes the file you want to
import:
Column Position File (fixed length): Each field in the file to be
imported starts at a specific position and contains a fixed number of
characters. This file type is sometimes referred to as “fixed length.”
Tab Delimited File: The fields in the file to be imported are separated
by tabs.
Universal Bridge - External File Formats
753
Slide 4
Requirements for Importing Transactions from an External File
Semi-Colon Delimited File: The fields in the file to be imported are
separated by semi-colons.
4. Select Begin Import to start importing the transactions, or Cancel to exit
without importing.
Import Transaction Validation
When transactions are imported, each piece of information is checked to make
sure it is in an acceptable format, required fields are not empty, etc. See the
following pages for the field definitions for each module.
Printing the Import Error Report
If errors were detected during the import process, an error report is generated,
and a message appears. To print the error report, do the following.
1. When the error report message appears, click OK.
Depending on the defaults you set for print options in your Module
Preferences, the Print Options window may appear.
2.
If the Print Options window appears, select the report destination:
Printer, Screen, or File.
If you select Printer or Screen, specify Laser or Dot Matrix. If you
select File, type the output file name. The default is REPORT.TXT. If you
regularly save to a file, the new file will append to the end of the existing
file, so you will not lose previously saved information.
3. Enter the number of copies to print.
By default, one copy will print, unless you enter a different default
number in your Module Preferences, or unless you select File or Screen
as the report output destination.
4. Select OK to print the report or Cancel to exit without printing.
754
Cougar Mountain Accounting
Slide 5
Requirements for Importing Transactions from an External File
Correcting Errors
While it may be possible to correct some of the errors on the error report in
the Cougar Mountain batch file, we recommend clearing the batch, correcting
the errors in the external file, and then importing again.
"N
ote Certain information, such as dates, will be required at posting, but will not be
required at the time of import. Be sure to print an Edit Report and review it
carefully prior to posting. If errors are detected at posting, an error report will
be generated. Use this to correct your entries.
Using the following instructions, correct any errors prior to posting the batch.
Correcting Errors in the External File
1. Edit the transactions in the external file, as necessary.
2. Clear the transactions you previously imported. The menu option used
will vary depending on the module.
3. Import the file again. For more information, see “Import External
Transaction File” on page 752.
Correcting Errors in the Imported Batch
1. Select the option that allows you to enter transactions from the main menu
of the module with which you are working. For example, in Accounts
Payable, select the Enter Bills option on the Enter Bills menu.
2. Use the Find button to locate and select the transaction(s) you want to
change.
3. Select Edit to change the transaction, and update it as needed.
4. Save the corrected transaction.
Universal Bridge - External File Formats
755
Slide 6
Requirements for Importing Transactions from an External File
Requirements for Importing Transactions from
an External File
When you import transactions from an external file using one of the Universal
Bridge options, the information in the file being imported must be in the
correct format to be written to the Cougar Mountain files. For example, fields
must be of the correct lengths and be delimited as expected.
Date Formats
The import will accept the following date formats:
YYYYMMDD__ ...
.If the import is based on column position,
then two spaces will be required on the
end of this format to accept the dates
correctly. Without the two spaces, the
record size will be incorrect.
MM/DD/YYYY ...
..When using this date format, be sure to use
all 4 digits of the year. If all four digits are
not used, the date may not be imported
correctly.
"N
ote Certain information, such as dates, will be required at posting, but will not be
required at the time of import. Be sure to print an Edit Report and review it
carefully prior to posting. If errors are detected at posting, an error report will
be generated. Use this to correct your entries.
756
Cougar Mountain Accounting
Slide 7
Requirements for Importing Transactions from an External File
External Files
The external files must be named as follows, where xxx is your company’s
three-character company code. These files must be located in the CMSWIN
directory (or wherever your Cougar Mountain software is installed).
General Ledger: ...
..GLEXT.xxx
Accounts Receivable: ... ...AREXT.xxx
Order Entry: ...
.OEEXT.xxx
Inventory: ...
...INEXT.xxx
Accounts Payable: ...
..APEXT.xxx
Payroll: ...
..PREXT.xxx
Bank Reconciliation:...
.BREXT.xxx
The external file must be in one of the following file formats: column position
(sometimes referred to as “fixed length”), semicolon delimited, or tab
delimited. The user must indicate which of these formats will be used when
they start the import process.
When information is imported from the external file, it will be imported into
one or two files (see the information contained later in this section) in the
batch selected by the user. The selected batch must be empty or an error
message will display.
Depending on the module you are using, the following files in the selected
batch are updated, where xxx is your company’s three-character company
code, and aaa represents your batch identity.
General Ledger: ...
..xxxGDaaa.DBF and xxxGJaaa.DBF
Bank Reconciliation:...
.xxxBTaaa.DBF and xxxBLaaa.DBF
Accounts Payable: ...
..xxxAIaaa.DBF and xxxAEaaa.DBF
Order Entry: ...
.xxxOTaaa.DBF and xxxOLaaa.DBF
Payroll: ...
..xxxPRDLY.DBF
Accounts Receivable: ... ...xxxATaaa.DBF and xxxALaaa.DBF
Inventory: ...
Universal Bridge - External File Formats
...xxxIHaaa.DBF
757
Slide 8
General Ledger File Format
Transaction numbers will be generated automatically based on the next
available number in the batch.
The file will contain multiple records, each having a CR/LF at the end and an
“H” or “D” as the first character. Records with an “H” at the beginning are
header or master records, and subsequent records with a “D” at the beginning
are the detail lines (sometimes referred to as “child lines”) for that header
record. The remaining pages in this section describe the external file formats
for each of the above modules.
"N
ote In the tables on the following pages, the Field Len column shows the
maximum length of the field; any characters over the specified length will be
truncated. Fields in column position files must be the exact length specified,
whereas fields in semicolon or tab delimited files may be shorter.
General Ledger File Format
The following tables show the requirements for the external file that is used to
import General Ledger journal transactions. The first table shows the file
definitions for the header record, and the second table shows the file
definitions for the detail records.
Table 3: General Ledger Header Record (xxxGJaaa.dbf)
Field Description
Field
Len
Pos
Data Type
Req
Header Identifier
1
01
Char-Caps
Type = “H”
Yes
Transaction Date
10
02
Date
Yes1
Posting Reference
15
12
Char-Caps
Yes
Trans Description
50
27
Character
No
End of Record
02
77
Yes
Maps To
Use to identify Header
Row
GLJHDATE
GLJHREF
GLJHTDES
Nowhere/used as record
separator
Record Length is 78 characters
758
Cougar Mountain Accounting
Slide 9
Accounts Receivable File Format
Table 4: General Ledger Detail Record (xxxGDaaa.dbf)
Field Description
Field
Len
Pos
Data Type
Req
Maps To
Detail Identifier
1
01
Char-Caps
Type = “D”
Yes
Used to identify Detail
Row
Account Number
30
02
Char-Caps
Yes
GLJDACCT
Detail Description
50
32
Character
No
Debit/Credit Flag
1
82
Character
Yes1 GLJDCREDIT
Transaction Amount
14
(11.2)
83
Numeric
No 2 GLJDAMOUNT
End of Record
02
97
Yes
GLJDTDES
Nowhere/used as record
separator
Record Length is 98 characters
"N
otes The Debit/Credit Flag must either be blank or contain a “D” for debit or a “C”
for credit. If left blank, the field defaults to “D.” The “C” must be in the field
for credit transactions to process correctly.
If the Transaction Amount is a negative number, then the import process
reverses the debit/credit flag and makes the transaction amount positive.
Accounts Receivable File Format
The following tables show the requirements for the external file that is used to
import Accounts Receivable transactions. The first table shows the file
760
Cougar Mountain Accounting
Slide 10
Accounts Receivable File Format
definitions for the header record, and the second table shows the file
definitions for the detail records.
Table 5: Accounts Receivable Header Record (xxxATaaa.dbf)
Field Description
Field
Len
Pos
Data Type
Req
Maps To
Header Identifier
1
01
Char-Caps
Type = “H”
Yes
Use to identify Header
Row
Customer Number
20
02
Char-Caps
Yes
ARTHCUST
Source Document
15
22
Char-Caps
Yes
ARTHDOC
Transaction Date
10
37
Date
Yes1
ARTHDATE
Transaction Code
(2,3,4,5,6,7,9)
4
47
Char-Caps
Yes
ARTHTCODE
Description
30
51
Character
No
ARTHTDES
Terms Code
2
81
Char-Caps
No
ARTHTCODE
Transaction Amount
14
(11.2)
83
Numeric
No
ARTHAMOUNT
Electronic? Flag
1
97
Char-Caps
No
ARATEFT (“Y” or “N”)
Bank Account Code
03
98
Char-Caps
No
ARTHBANK
Discount Amount
14
101
Numeric
No
ARTHDISC
CC Payment
1
115
Numeric
No
ARTHCCPMT
CC Code
4
116
Character
No
ARTHCRCD
CC Number
20
120
Character
No
ARTHCRNO
CC Exp Date
5
140
Character
No
ARTHCREX
CC Authorization
Code
15
145
Character
No
ARTHCRAU
CC Processed Flag
1
160
Numeric No
CC Authorization
Flag
1
161
Numeric
No
ARTHCRFL (1=Yes,
0=No)
CC PCCharge
TransNum
10
162
Character
No.
ARTHCCPCTN
Universal Bridge - External File Formats
ARTHCPROC (1=Yes,
0=No)
761
Slide 11
Accounts Receivable File Format
Table 5: Accounts Receivable Header Record (xxxATaaa.dbf)
Field Description
Field
Len
Pos
Data Type
Req
Maps To
CC Address
20
172
Character
No
ARTHCRADDR
CC Zip
9
192
Character
No
ARTHCRZIP
CC Clerk
6
201
Character
No
ARTHCLERK
End of Record
02
207
Yes
Nowhere/used as record
separator
Record Length is 208 characters
"N
otes If the Transaction Date is invalid, an error will be printed on the Import Error
Report. If the Transaction Date is blank, it will be imported as is.
A blank entry in the Electronic (EFT) field will be treated the same as a “0”
(No). If AR is not integrated to BR then the Bank Account Code field in the
Import File will instead be the 3-character EFT Account Code.
Table 6: Accounts Receivable Detail Record (xxxALaaa.dbf)
Field Description
Field
Len
Pos Data Type
Req
Maps To
Detail Identifier
1
01
Char-Caps
Type = “D”
Yes
Used to identify Detail
Row
Document to Pay
15
02
Char-Caps
No
ARTLDOC
Discount Override
1
17
Numeric R:
{0-9}
No1
ARTLDISC
Discount Amount
14(11.2)
18
Numeric
No
ARTLDISAMT
Apply Amount
14(11.2)
32
Numeric
Yes
ARTLAMOUNT
End of Record
02
46
Yes
Nowhere/used as record
separator
Record Length is 47 characters
762
Cougar Mountain Accounting
Slide 12
Order Entry File Format
"N
otes If the Discount Override has a value of 8, then the discount used will be the
amount in the Discount Amount field. (0-No Discount; 1-Discount #1; 2Discount #2; 3-Discount #3; 4-Discount #4; 5-Discount #5; 8-Special
Discount; 9-Normal Discount).
Order Entry File Format
The following tables show the requirements for the external file that is used to
import Order Entry transactions. The first table shows the file definitions for
the header record, and the second table shows the file definitions for the detail
records.
Table 7: Order Entry Header Record (xxxOTaaa.dbf)
Field Description
Field
Length
Pos
Data Type
Req
Maps To
Header Identifier
1
01
Char-Caps
Type = “H”
Yes
Used to identify
Header Row
Shipping Customer
20
02
Char-Caps
Yes
OETHNUM
Shipping Address
35
22
Character
No
OETHADD1
Shipping Address
35
57
Character
No
OETHADD2
Shipping Address
35
92
Character
No
OETHADD3
Shipping Address
35
127
Character
No
OETHADD4
Cash/Check/CC/Chg 1
(0-Cash; 1-Check; 2CCard; 3-AR Charge)
162
Numeric
Yes
OETHPAY
Transaction Type
1
(0-Normal; 1-Hold; 2Quote; 3-Work Order)
163
Numeric
Yes
OETHTYPE
Invoice Number
15
164
Char-Caps
Yes
OETHINVNO
PO Number
20
179
Char-Caps
No
OETHPONUM
Ship Via Code
6
199
Char-Caps
No
OETHSHIP
Universal Bridge - External File Formats
763