Pin Code File Format - Avaya S6200 Administration And Maintenance

Managing Files
The data contained in these two files needs to adhere to the formats specified in the following
sections. Both files require the use of the pipe to delimit fields.
Note:
When the files do not meet the specific file formats, then the batch load may fail.
Note:
Note: Optional fields must contain a space to separate the field delimiters. For example: 8975| |

PIN Code File Format

The pins.txt file format is defined in
a first row identifying the fields. All lines of the file contain data. For example
:
||||ACBRIDGE Test1|AnyCo, Inc.|||||99999999901|197865551212||||||1077123541|PINRaw
Batch Load|||
||||ACBRIDGE Test2|AnyCo, Inc.|||||99999999902|197865551212||||||1077123541|PINRaw
Batch Load|||
Table 41: PINs.txt File Format
Field
CompanyRef
ClientImportID
ClientFirstName
ClientLastName
ClientFullName
ClientCompanyName
ClientAddrLine1
ClientAddrLine2
ClientAddrLine3
ClientAddrLine4
ClientMainPINCode
ClientMainPhone
ClientMainFax
206 Administration and Maintenance of the S6200/S6800 Servers
Table 41. Unlike the pre-33 file, this format does not require
Type Required
Integer N
Char(50) N
Char(30) PINRaw requires either:
ClientFirstName and ClientLastName
Char(30)
—or—
ClientFullName
Char(80) Y, —or— ClientFirstName and
ClientLastName
Char(60) N
Char(40) N. Reserved for future use.
Char(40) N. Reserved for future use.
Char(40) N. Reserved for future use.
Char(40) N. Reserved for future use.
Char(16) Y. Must be unique for non-NULL values.
Char(40) N
Char(40) N. Reserved for future use.
1 of 2