FAQs: Creating and Modifying Address Formats
| • | How do I change the entries I am prompted for when I type a user address? |
| • | What entry lists appear for vendor and user addresses when I am performing different tasks in SirsiDynix Symphony? |
| • | How do I create a Vendor EDI Address format? |
| • | What vendor EDI address information is available? |
How do I change the entries I am prompted for when I type a user address?
See the following procedure for changing entries that appear in user address formats.
| 1 | On the Configuration Module toolbar, click the User Configuration wizard group button. |
| 2 | Click the User Address Format wizard to be modified, either User Address 1, User Address 2, or User Address 3. For this example, the User Address 2 policy will be modified. |
| 3 | Click the Entries tab. From this tab, you can create new entries, modify entries, or remove entries from this format. For this example, the full, brief, and template synonym lists will be modified to display different entries. |
| 4 | Click the Entry ID Policy helper in the top left corner of the window. |
| 5 | Select the USERA2-FU entry ID, and click Modify. |
| 6 | Click the gadget in the Entries field and select entries that will be included in USERA2-FU. For this example, unselect LINE, and select ADDRESS. Click the Up Arrow to move ADDRESS to the top of the entries list. |
| 7 | The order of the entries is important. Click the Up and Down Arrows to rearrange the other entries as desired. |
| 8 | Click OK. |
| 9 | Click Save. |
| 10 | Repeat the preceding steps for the Brief Entries and Template Entries synonym lists. |
| 11 | Click Save and your changes to the User Address 2 format will appear after the next halt and run of the workstation server. |
What entry lists appear for vendor and user addresses when I am performing different tasks in SirsiDynix Symphony?
The following list indicates which entry lists appear for vendor and user addresses when performing different tasks in SirsiDynix Symphony:
| • | TEMPLATE entries for vendor and user addresses always appear when a user or vendor is created or modified. |
| • | FULL entries for vendor and user addresses always appear at the workstation or print in report lists. |
| • | BRIEF entries for vendor and user addresses are used in report notices, pipe-delimited output files, and labels. |
You should not have any entries in the BRIEF or FULL formats that are not also in your TEMPLATE format, or you will not be able to create user or vendor addresses which contain the entry missing from your TEMPLATE. Also, if you do not have all of the TEMPLATE entries in your FULL and BRIEF formats, they will not display or print in reports.
How do I create a Vendor EDI Address format?
The Vendor EDI Address Format policy includes the necessary field definitions for the formatting, sending, and receiving of X12 transactions. This format wizard can be accessed from either the Acquisitions Configuration wizard group or Serial Control Configuration wizard group.
Using EDI (X12) for ordering is different from using the SirsiDynix Symphony MARC Order Loader for 9XX ordering. For more information, see FAQs: Comparing X12 and 9XX Ordering.
The following is the default Vendor EDI Address Format policy.
Basic Tab
|
Name: |
VEDIADDR |
|
Description: |
Vendor EDI Address |
|
Record Type: |
OTHER |
|
Purpose: |
VENDOR_EDI |
Entries Tab
|
Full: |
VEDIADDR-F |
|
Brief: |
VEDIADDR-B |
|
Template: |
VEDIADDR-T |
|
Entry |
Value |
|
X12_ISA01 |
00 (X12 information) |
|
X12_ISA02 |
|
|
X12_ISA03 |
00 (X12 information) |
|
X12_ISA04 |
|
|
X12_ISA05 |
ZZ (X12 information) |
|
X12_ISA06 |
Your library name or number with the vendor (no longer than 15 characters); this may change per vendor |
|
X12_ISA07 |
ZZ (X12 information) |
|
X12_ISA08 |
Vendor SAN number or name or number both you and the vendor agree on |
|
X12_ISA11 |
U (X12 information) |
|
X12_ISA12 |
00302 (X12 information) |
|
X12_ISA14 |
1 (X12 information) |
|
X12_ISA15 |
P (X12 information) |
|
X12_ISA16 |
174 (X12 information) |
|
X12_GS02 |
Your library name or number with the vendor (no longer than 15 characters); this may change per vendor |
|
X12_GS03 |
Vendor SAN number or name or number you and the vendor agree on |
|
X12_GS07 |
X (X12 information) |
|
X12_GS08 |
003060 (X12 information) |
|
X12_DESEP |
052 (X12 data separator) |
|
X12_SEGTRM |
012 (X12 segment terminator) |
|
XFER_SCR |
ftpsend (or fptsendxpo, if .xpo file extension required by the vendor) (Transfer script) |
|
XFER_ADDR |
Vendor FTP transfer address; assigned to you by this vendor |
|
XFER_USER |
User ID (Transfer user ID assigned to you by this vendor) |
|
XFER_PASS |
Password (Transfer user password assigned to you by this vendor) |
|
XFER_MODE |
BINARY (Transfer mode assigned to you by this vendor) |
|
DOWNDIR |
Outgoing (Download directory the vendor supplies) |
|
DOWNFILE |
UNIQUE (Download file) |
|
UPDIR |
Upload to directory the vendor supplies |
|
UPFILE |
UNIQUE ( Upload file) |
|
RCPT_MTHD |
FTP (Retrieval method) |
|
SENDER_ID |
Sender ID supplied in segments ISA08 and GS03 |
|
REC_TRANS |
810:bookinv.rmap (Program for book invoices) |
|
REC_TRANS |
850:bookorder.map (Program for book purchase orders) |
|
TRANSTYPE |
BOOK or SERIAL (Indicates type of vendor, either a book vendor or serial vendor) |
|
FTP_PASS |
YES or NO (If YES, transfers are done in passive mode; if NO, transfers are done in active mode) |
|
RCPT_SCR |
ftpreceive (verify with vendor) |
Some vendors require the files received from libraries have an .xpo file extension. Ingram (a vendor that supports EDI transactions) requires the .xpo file extension. SirsiDynix Symphony will add this extension to exported files if the vendor’s EDI address entry for XFER_SCR contains the command: ftpsendxpo.
Blackwell North America (BNA) uses a unique file naming convention for uploading files to their file server. SirsiDynix Symphony will convert the exported file names if the vendor’s EDI address entry for XFER_SCR contains the command: ftpsendblackwell.
BNA puts all types of files in their directory for pickup. If the RCPT_SCR entry contains the command: ftpreceiveblackwell, then only those files that start with XI in the remote directory will be received.
Basic Tab for Entries
For each EDI entry, the Basic tab contains the following values.
|
Allow Create/Edit: |
YES |
|
Required: |
NO |
|
Data Type: |
ANY |
|
Minimum Size: |
0 |
|
Maximum Size: |
9999 |
|
Default Value At Record Creation: |
None |
Display Tab for Entries
For each EDI entry, the Label text boxes display the following corresponding values.
|
Entry ID |
Label |
|
X12_ISA01 |
X12_ISA01 |
|
X12_ISA02 |
X12_ISA02 |
|
X12_ISA03 |
X12_ISA03 |
|
X12_ISA04 |
X12_ISA04 |
|
X12_ISA05 |
X12_ISA05 |
|
X12_ISA06 |
X12_ISA06 |
|
X12_ISA07 |
X12_ISA07 |
|
X12_ISA08 |
X12_ISA08 |
|
X12_ISA11 |
X12_ISA11 |
|
X12_ISA12 |
X12_ISA12 |
|
X12_ISA14 |
X12_ISA14 |
|
X12_ISA15 |
X12_ISA15 |
|
X12_ISA16 |
X12_ISA16 |
|
X12_GS02 |
X12_GS02 |
|
X12_GS03 |
X12_GS03 |
|
X12_GS07 |
X12_GS07 |
|
X12_GS08 |
X12_GS08 |
|
X12_DESEP |
X12 Data Separator |
|
X12_SEGTRM |
X12 Segment Termintr |
|
XFER_SCR |
Transfer script |
|
XFER_ADDR |
Transfer address |
|
XFER_USER |
Transfer user ID |
|
XFER_PASS |
Transfer user passwd |
|
XFER_MODE |
Transfer mode |
|
DOWNDIR |
Download from dir |
|
DOWNFILE |
Download file |
|
UPDIR |
Upload to dir |
|
UPFILE |
Upload file |
|
RCPT_MTHD |
Retrieval method |
|
SENDER_ID |
Sender ID |
|
REC_TRANS |
Rec trans |
|
TRANSTYPE |
Transaction type |
|
FTP_PASSIVE |
FTP passive |
|
RCPT_SCR |
Receive script |
What vendor EDI address information is available?
The following vendor EDI addresses are defined.
| • | Baker & Taylor |
| • | Blackwell |
| • | Brodart |
| • | Ebsco |
| • | Harrassowitz |
| • | Ingram |
For the most up-to-date vendor EDI address information, search "EDI Address Information" on the SirsiDynix Customer Support website or see the EDI: Vendor Address Information link on the SirsiDynix Customer Support website (https://support.sirsidynix.com/kb/126171).
Related topics