TLE Operations Center User Guide

TrustedLink® Enterprise

Operations Center User Guide July 2007

TrustedLink Enterprise Operations Center User Guide Document Release Date: 13 July 2007 Software Release: 6.1.1 Product Support: U.S.—1.877.446.6847 (1.877.4INOVIS); EMEA—1+44 (0)1483 569388 For International support outside EMEA, call +1 404.467.3806 © 2007 Inovis, Inc. All rights reserved.

InovisTM, the Inovis logo, Inovis CatalogueTM, Retail Web FormsTM, BizManagerTM, and InovisworksTM are all trademarks of Inovis, Inc. TrustedLink®, TrustedLink® Enterprise, TrustedLink®iSeries, and TrustedLink® Windows are registered trademarks of Inovis, Inc. All other trademarks and registered trademarks are the property of their respective owners. The names of companies and individuals used in any sample database or as examples in the documentation are fictitious and illustrate the use of the software, only. Any resemblance to actual companies or individuals, whether past or present, is purely coincidental. This document and the related software described in this manual are supplied under license or nondisclosure agreement and may be used or copied only in accordance with the terms of the agreement. The information in this document is subject to change without notice and does not represent a commitment on the part of Inovis This document may contain examples of data screens or reports or other descriptions or examples which use the names of individuals, companies, brands, categories, products and/or product codes. All of these names and codes are fictitious, and any similarity to the names and codes used by an actual person or entity is entirely coincidental. U.S. Government Users: This documentation and any software it describes are "commercial items" as that term is defined in 48 C.F.R. 2.101 and successor regulations, consisting of "commercial computer software documentation", "documentation related to commercial computer software" or "commercial computer software" as such terms are used in 48 C.F.R. 12.212 and 48 C.F.R. 252.227-7014(a)(1) and their successor regulations. Consistent with 48 C.F.R. 12.212 and 48 C.F.R. 252.227-7202-1 through 227.7202-4 and their successor regulations, all U.S. Government users, agencies and contractors acquire this documentation and the software to which it relates with only those rights described in this paragraph.

Inovis 11720 AmberPark Drive Alpharetta, Georgia 30004 tel +1 877.446.6847 www.inovis.com

ii

TrustedLink Enterprise Operations Center User Guide

Contents Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About This Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Conventions Used In This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TrustedLink Enterprise Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Contacting Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Contact Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Product Training Assistance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

15 15 16 16 16 16 17

1 Overview TrustedLink Enterprise Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operation Center Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Translation Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scheduling Translations for Windows and UNIX Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . Translation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logging and Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Administrator Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Translation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Supported Translation Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Inbound Process Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Outbound Translation Process Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

19 19 20 20 21 21 22 22 23 23 23 25

2 Accessing and Navigating Opening the Operations Center Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Select Data Source Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Database Logon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Secured User Logon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Navigating the Operations Center Client Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operations Center Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operations Center Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

29 30 30 32 33 33 34

3 Contact Management Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . More About EDI Representatives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . More About Contacts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Email Notifications and History Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . More About Email Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the Contact Management Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding a New Contact. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Assigning EDI Representatives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Assigning Contacts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing the EDI Representative for a Trading Partner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Unassigning Contacts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Unassigning EDI Representatives for Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

37 38 38 39 40 40 44 45 45 46 46 47

iii

CONTENTS

Setting Contact Notification Preferences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing EDI Rep and Contact Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing Trading Partners or Events for an EDI Rep . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing Contacts for a Trading Partner or Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Editing Contact Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting a Contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

48 49 50 50 50 51

4 Trading Partners Opening the Trading Partners/Events Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a New Trading Partner. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining the General Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining the Alphanumeric Control Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining the Contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining the Alias Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining Interchange Reference Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining the FG Control Number Maintenance Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Searching for a Trading Partner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Searching by Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Searching by Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Searching by Communication Provider . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying Trading Partner Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting Trading Partners and Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting a Trading Partner. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting an Interchange Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reassigning Trading Partners to Interchanges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

53 54 55 56 58 59 60 65 67 68 69 70 71 72 72 72 73

5 Applications Application Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Internal Cross-References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Defining External Cross-References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Opening an Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Creating an Inbound Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Defining the Inbound Application General Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Defining the Inbound Application Contacts Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Defining the Inbound Application Production File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Defining the Inbound Application Test File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Defining the Inbound Application Internal Cross Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Viewing the Trading Partner Associated to the Inbound Application . . . . . . . . . . . . . . . . . . . . . . . . 84 Creating an Outbound Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Defining the Outbound Application General Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Defining the Outbound Application Contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Defining the Outbound Application Production File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Defining the Outbound Application Test File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Defining the Outbound Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 Defining the Outbound Application Internal Cross Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Defining the Outbound Application External Cross-Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Viewing the Outbound Trading Partners Associated to the Application . . . . . . . . . . . . . . . . . . . . . . 97 Sending Multiple Documents to the Same Trading Partner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Maintaining Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

iv


CONTENTS

Copying an Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying an Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting an Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting an Internal Cross-Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting an External Cross-Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

102 102 102 103 103

6 Event Wizard Creating an Inbound Event Using the Event Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EDI Document Details—Inbound . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . XML Document Details—Inbound . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating an Outbound Event Using the Event Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EDI Document Details—Outbound . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . XML Document Details—Outbound . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying an Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event Properties—EDI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event Properties—XML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Copying Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

105 109 112 113 117 120 120 121 123 125 126

7 Data Export Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exporting Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Opening the Trading Partners/Events Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Opening the Communications Mailbox Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Opening the Contact Management Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Opening the Applications Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Selecting a Data Source for Applications Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Opening the Interchange List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exporting Map Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

129 130 130 131 131 132 133 134 134

8 Scheduling Tasks Overview Event-Scheduled Transfers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event-Scheduled Transfer Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Batch-Scheduled Transfers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Batch-Scheduled Transfer Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Manual Mailbox Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Queuing a File from Command Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transferring a File Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

137 137 138 138 138 138 139

9 UNIX Task Schedule Setting Up the Schedule Type on the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Batch Scheduling on the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Batch Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Up the Server—UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

141 141 142 142

10 Windows Task Scheduling TrustedLink Scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143


v

CONTENTS

Scheduler Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scheduler Service Logging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gateway Scheduling Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up the Scheduler Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining the Scheduler Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting the Scheduler Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operations Center Task Scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Schedule List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding a New Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updating or Disabling a Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Schedule Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying a Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting a Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

143 144 144 144 144 145 145 146 146 146 149 152 152

11 Translations Command Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Opening the Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting the Browser Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Translation Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Submitting a Translation Request from the Operations Center. . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting a Translation Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking TL Services Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Queuing a File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transferring a File From a Mailbox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Request Log List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Refreshing the Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying the Request Log List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command Line Translation Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

154 154 154 155 155 156 158 158 158 159 160 160 160 161

12 Map Versioning Map Versioning TLE Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TLE Client Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Access Manager Version Control Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TL Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Map Repository Version Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operations Center Version Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Workbench Version Control Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Workbench and TLE Map Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up Access Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Up Map Versioning In TL Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using Map Versioning In the Operations Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing Map Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the Repository Administration window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating Map Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting Map Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the Map Repository in Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the Repository Manager Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Importing Maps into the Workbench Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

vi

163 164 164 164 164 165 166 166 166 167 168 168 169 171 172 172 173 174


CONTENTS

Modifying Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 Importing Third Party Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 Checking Maps Into the Map Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

13 TL Services Submitting Requests to TL Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 Command Line Formats. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

14 Message Configuration Message Configuration Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of Messages to EDI Administrators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of Messages to Contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Inbound EDI Recovery Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Inbound EDI Reject Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Inbound EDI Test Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mail Function Setup Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing Contact Email Addresses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

179 179 180 180 184 184 185 185 185

15 Error Recovery and Logging Inbound Error Recovery (IER) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Translation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Interchange Rejection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recovery File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Abnormal Termination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recovery Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Inbound Extended Error Logging (IEL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IEL Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting IEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Outbound Error Recovery (OER) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OER Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Open Error Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RECOVERY Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Outbound Extended Error Logging (OEL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting OEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OEL Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backwards Compatibility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . In Conjunction with IER Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

187 187 187 188 188 188 189 189 189 189 190 190 190 190 191 191 191 191 192 192

16 Reports and Statistics History Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transaction Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Document Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Opening the History Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


193 193 193 194 194

vii

CONTENTS

Viewing History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reconciling a Transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing Manual Reconciliation Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing Delinquent Real-time FA Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Banking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Selecting Data Banking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing Banked Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Purging Banked Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing Data Banking from the History Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Specifying Search Criteria for Business Document Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Specifying Search Criteria for Event Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

194 195 196 197 198 198 198 200 201 201 202 202 204

17 System Administrator Accessing the System Administrator Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mailbox and Inbound Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . View Mailbox Passwords. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Set Mailbox Password and Inbound Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Administrator Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Optional Compliance Checking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Error Code Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating Optional Compliance Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Implementing Optional Compliance Checking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TL Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OnRamp Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . User Profiles and Browser Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding a User Profile and Assigning Browser Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

207 208 209 209 210 211 211 211 213 214 215 215 215

18 Miscellaneous Functions Setting the Mapping Tools Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting the Mapping Workbench Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting the Mapper Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Translation Table Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uploading Translation Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Downloading Translation Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

217 217 217 218 218 219

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221

viii


List of Procedures To open the Operations Center Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 To use the Select Data Source dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 To access Contact Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 To add a new contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 To assign EDI Representatives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 To assign a Contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 To change the EDI Representative for a trading partner . . . . . . . . . . . . . . . . . . 46 To unassign a Contact from an application or trading partner . . . . . . . . . . . . . 47 To unassign all Contacts from an application or trading partner . . . . . . . . . . . 47 To unassign an EDI Representative from one event . . . . . . . . . . . . . . . . . . . . . . 47 To unassign an EDI Representative from all events . . . . . . . . . . . . . . . . . . . . . . 47 To set the notification preference for a trading partner Contact . . . . . . . . . . . 48 To set the notification preference for an application Contact . . . . . . . . . . . . . . 48 To set the notification preference for a trading partner. . . . . . . . . . . . . . . . . . . 49 To set the notification preference for an application . . . . . . . . . . . . . . . . . . . . . 49 To view existing contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 To view trading partners or events associated with an EDI Rep . . . . . . . . . . . . 50 To view Contacts for a trading partner or application . . . . . . . . . . . . . . . . . . . . 50 To modify contact information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 To delete a contact. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 To open the Trading Partners/Events window . . . . . . . . . . . . . . . . . . . . . . . . . . 53 To create a new trading partner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 To define trading partner properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 To define the alphanumeric control definitions. . . . . . . . . . . . . . . . . . . . . . . . . . 57 To access the Contacts tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 To unassign a trading partner Contact in Trading Partner Properties . . . . . . . 59 To define the alias properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 To define the interchange reference properties . . . . . . . . . . . . . . . . . . . . . . . . . 61 To add an interchange reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 To define the Functional Group control number maintenance properties . . . 66 To search for a trading partner by event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

ix

LIST OF PROCEDURES

To search for a trading partner by associated applications . . . . . . . . . . . . . . . . 69 To search for a trading partner by communications information . . . . . . . . . . . 70 To modify a trading partner’s properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 To delete a trading partner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 To delete an interchange reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 To reassign an interchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 To open the Application List window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 To create an inbound application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 To define inbound application general properties . . . . . . . . . . . . . . . . . . . . . . . . 78 To access the Contacts tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 To unassign an application Contact in Application Properties . . . . . . . . . . . . . 80 To define inbound application production file properties. . . . . . . . . . . . . . . . . . 81 To define inbound application test file properties . . . . . . . . . . . . . . . . . . . . . . . . 82 To define inbound application internal cross-reference properties . . . . . . . . . . 83 To add an internal cross-reference to an inbound application . . . . . . . . . . . . . . 83 To view the trading partner associated to the inbound application . . . . . . . . . 84 To create an outbound application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 To define outbound application general properties . . . . . . . . . . . . . . . . . . . . . . 86 To access the Contacts tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 To add a new application contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 To assign an existing contact to an application . . . . . . . . . . . . . . . . . . . . . . . . . . 87 To unassign an application contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 To define outbound application production file properties . . . . . . . . . . . . . . . . 88 To define the outbound application test file properties . . . . . . . . . . . . . . . . . . . 89 To define ASCII or EBCDIC Flat File Outbound Layout properties . . . . . . . . . 91 To define XML Outbound Layout properties . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 To define outbound application internal cross-reference properties . . . . . . . . 95 To add an internal cross-reference to an outbound application . . . . . . . . . . . . 96 To define outbound application external cross-reference properties . . . . . . . . 96 To add an external cross-reference to an outbound application . . . . . . . . . . . . 97 To define outbound application trading partner properties. . . . . . . . . . . . . . . . 97 To send multiple documents to the same trading partner. . . . . . . . . . . . . . . . . 99

x


LIST OF PROCEDURES

To create a new application from an existing one. . . . . . . . . . . . . . . . . . . . . . . 102 To modify an application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 To delete an application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 To delete an internal cross-reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 To delete an external cross-reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 To create an event using the Event Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 To create an event using the Event Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 To modify an event. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 To copy an event. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 To delete an Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 To export the data to another database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 To open the Trading Partners window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 To open the Communications Mailbox window . . . . . . . . . . . . . . . . . . . . . . . . 131 To copy contact data associated to another database . . . . . . . . . . . . . . . . . . . 131 To copy application data associated with a particular event to another database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 To select a data source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 To view or copy an interchange list window . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 To copy a map to another database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 To queue a file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 To manually transfer a file using the Command Manager . . . . . . . . . . . . . . . . 139 To set up the Scheduler Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 To set up the Scheduler Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 To manually start the Scheduler Service to enable the Automatic function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 To add a new schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 To update or disable a schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 To create a schedule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 To modify a schedule with the Schedules tool. . . . . . . . . . . . . . . . . . . . . . . . . . 152 To delete a schedule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 To open the browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 To set the browser path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155


xi

LIST OF PROCEDURES

To translate an event manually from the Command Manager . . . . . . . . . . . . 155 To submit a translation request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 To remove a translation request. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 To check the status of TL Services using the browser . . . . . . . . . . . . . . . . . . . 158 To send a file to a mailbox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 To transfer a file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 To refresh the data in the Request Log List window. . . . . . . . . . . . . . . . . . . . . 160 To display the Request Log List window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 To set up Map Versioning through TL Configuration . . . . . . . . . . . . . . . . . . . . 167 To use Map Versioning in the Operations Center . . . . . . . . . . . . . . . . . . . . . . . 168 To view map versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 To use the Repository Administration window . . . . . . . . . . . . . . . . . . . . . . . . . 169 To create a map release. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 To delete a map release. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 To import maps into Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 To modify events in Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 To import a new map. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 To import a third-party map keeping the name of an existing map . . . . . . . . 175 To check maps into the Map Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 To set up the TrustedLink mail function on your server . . . . . . . . . . . . . . . . . 185 To view a contact email address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 To open the History window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 To view history about a trading partner, transmission, or transaction . . . . . . 194 To manually reconcile a transmission. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 To view a transmission message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 To view real-time delinquent FA information . . . . . . . . . . . . . . . . . . . . . . . . . . 197 To set the viewing criteria for Data Banking . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 To set purge criteria. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200 To view banked data from the History window. . . . . . . . . . . . . . . . . . . . . . . . . 201 To view statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202 To specify search criteria for business document statistics . . . . . . . . . . . . . . . 202 To specify search criteria for Event statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . 204

xii


LIST OF PROCEDURES

To access the System Administrator menu function . . . . . . . . . . . . . . . . . . . . 207 To set or modify mailbox passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 To view the password for a specific mailbox . . . . . . . . . . . . . . . . . . . . . . . . . . . 209 To set or change the mailbox or inbound passwords . . . . . . . . . . . . . . . . . . . . 209 To set the system administrator password . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210 To create an optional compliance profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211 To implement optional compliance checking . . . . . . . . . . . . . . . . . . . . . . . . . . 213 To change the timeout setting for the TL Services connection. . . . . . . . . . . . 214 To add a user profile and assign browser access . . . . . . . . . . . . . . . . . . . . . . . . 215 To set the TrustedLink Mapping Workbench path . . . . . . . . . . . . . . . . . . . . . . 217 To set the Mapper path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217 To upload translation tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 To download translation tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219


xiii

LIST OF PROCEDURES

xiv


Introduction

T

his TrustedLink® Enterprise document Introduction is organized as follows:

■

“Audience” on page 15

■

“About This Guide” on page 15

■

“Conventions Used In This Guide” on page 16

■

“TrustedLink Enterprise Documentation” on page 16

■

“Contacting Customer Support” on page 16

Audience This guide is intended for individuals working on the TrustedLink Enterprise tasks discussed in this guide.

About This Guide This guide is organized as follows. Chapter

Chapter 1

“Overview”

Chapter 2

“Accessing and Navigating”

Chapter 3

“Contact Management”

Chapter 4

“Trading Partners”

Chapter 5

“Applications”

Chapter 6

“Event Wizard”

Chapter 7

“Data Export”

Chapter 8

“Scheduling Tasks Overview”

Chapter 9

“UNIX Task Schedule”

Chapter 10

“Windows Task Scheduling”

Chapter 11

“Translations”

Chapter 12

“Map Versioning”

Chapter 13

“TL Services”

Chapter 14

“Message Configuration”

Chapter 15

“Error Recovery and Logging”

Chapter 16

“Reports and Statistics”

15

Conventions Used In This Guide

Chapter (Continued)

Chapter 17

“System Administrator”

Chapter 18

“Miscellaneous Functions”

Conventions Used In This Guide This guide uses the following conventions to call attention to names, screen output, and program code. . This convention

Indicates

Example

bold text

Button names, keys, menu options, hyperlinks, values entered in fields or selected in dropdowns, and names of dropdowns, radio buttons, and fields when the names are phrases, not one or two words.

Save

Title Case

Names of pages, dialogs, forms, tabs, reports, and names of dropdowns, radio buttons, and fields when they are one or two words.

Trading Partner List

Lucida Console font

Indicates a URL, application code, command name, file name, directory path, or DOS or UNIX screen output.

filename

Italics indicate variables. Angle brackets <> indicate the enclosed material is optional. Italic |

Name of book or guide, name of a variable, or a new term the first time that it appears.

TrustedLink Enterprise Installation Guide

In a syntax line, a pipe within square brackets separate a choice between parameters.

[Warning | Violation]

TrustedLink Enterprise Documentation This guide is part of a documentation set that describes TrustedLink Enterprise product information management software. These documents are available online from Inovisworks.

Contacting Customer Support If support for your TrustedLink Enterprise product is provided by an Inovis Business Partner, contact that business partner directly. If support is provided by Inovis, log on to Inovisworks for your support needs. After you register, you will have access to a rich database of problem resolutions, release notes, known issues, and announcements. If the answer to your question is not in the database, you can log a problem ticket on the Customer Support site. Contact Information

Inovis Customer Support can be reached as follows: ■

Primary point of contact for support: http://www.inovisworks.net You can log a problem ticket and documentation comments at Inovisworks.

16


Contacting Customer Support

■

Telephone support: ■

In North America, call 877.4INOVIS (877.446.6847)

■

In Europe, call +44 (0)1483 569388

■

For international support outside EMEA, call +1 404.467.3806

Note:

For support hours, go to http://www.inovis.com/support/.

Important: If you should experience a production-down issue, call one of the support telephone numbers above.

Product Training Assistance

Inovis offers training on many of its electronic commerce products, including TrustedLink. To view the current schedule and pricing, or to sign up for a training class, click http://www.inovis.com/training


17

Contacting Customer Support

18


1

Overview

T

his chapter introduces you to the Operations Center Client and describes how it works with the other components in TrustedLink Enterprise. Topics include:

■

“TrustedLink Enterprise Overview” on page 19

■

“Operation Center Components” on page 19

■

“Translation Process” on page 23

TrustedLink Enterprise Overview TrustedLink Enterprise uses these functions to exchange data:

See also the TrustedLink Enterprise Mapper User Guide and Mapping Workbench User Guide. The Operations Center, which includes the Gateway, Translation Set Up and the Translation Process features, are explained in these sections.

Operation Center Components The Operations Center Client is a Windows®-based application you use to enter and maintain event information. The information identifies your trading partners, documents, applications and communication providers, mailboxes, and is stored on the database. The information is used by the Translator and Gateway components to process your inbound and outbound data. History, error and statistical information are also stored on the database and can be viewed using the Operations Center.

19

OVER VIEW

Operation Center Components

For the purposes of this manual, the Operations Center components are grouped by the functions required to exchange documents and based on how you use and view the Operations Center user interface. Functions include: ■

“Gateway” on page 20

■

“Translation Setup” on page 20

■

“Scheduling Translations for Windows and UNIX Environments” on page 21

■

“Translation Process” on page 21

■

“Logging and Reporting” on page 22

■

“System Administrator Functions” on page 22

Gateway

The Gateway is a communications software enabling you to send and receive data/files with trading partners, or VANs. You can also transfer files internally from one server to another on your own network. To use the Gateway, set up the following information:

Important: The functions in this graphic include all possible set ups required to use the Gateway. Individual set ups can vary based on your operating systems and the types of translation.

See the TrustedLink Enterprise Gateway Communications User Guide for more information. Translation Setup

Four parts must be defined within the Operations Center to perform inbound and outbound translations:

20

■

EDI Representative

■

Trading Partner

■

Application


1

OVER VIEW


■

Event

In addition, two more parts must be defined within the Operations Center to perform outbound translation: ■

Interchange

■

Communication provider/mailbox

This graphic outlines the parts needed to create an Operations Center event:

Important: The functions in this graphic include all possible set ups required to perform a translation. Individual set ups can vary based on your operating systems and the types of documents you are translating.

Scheduling Translations for Windows and UNIX Environments

Scheduling translations allows TrustedLink to perform translations and connections without manual intervention. There are different set up procedures for Windows and UNIX. See “UNIX Task Schedule” on page 141 and “Windows Task Scheduling” on page 143 for more information. Translation Process

TL Services includes all translation services. TL Services use the data defined in the Operations Center Client to translate inbound and outbound EDI and XML transmissions.


21

OVER VIEW


TL Services translations employ transaction tracking, load leveling, and recovery. When an installation contains concurrent translations, multiple translators run in this mode.

See the TrustedLink Enterprise TL Services User Guide for more information. Logging and Reporting

Logging and Report functions are grouped in the Operations Center and are typically used after translation occurs to monitor the translation results. You can: ■

View translation results

■

Check translation errors

■

Recover from errors

See “Logging and Reporting” on page 22 for more information. System Administrator Functions

In the Operations Center, you can perform many tasks from the System Administrator function: ■

Mailbox Password maintenance

■

System Administer Password maintenance

■

Optional Compliance Checking

■

TL Services

■

OnRamp Profile maintenance

■

User Profiles and Browser Access

See “System Administrator” on page 207 and “Miscellaneous Functions” on page 217 for more information. Miscellaneous functions include setting the mapping tool paths and uploading and downloading translation tables.

22


1

OVER VIEW

Translation Process

Translation Process To transmit inbound and outbound documents from your company to a trading partner, TrustedLink Enterprise converts documents into a standard Electronic Data Interchange (EDI) or Extensible Markup Language (XML) format. The translation process for inbound and outbound documents is described in these sections. Supported Translation Types

TrustedLink Enterprise supports these types of inbound and outbound translations: Inbound

Outbound

EDI to Flat File

Flat File to EDI

EDI to XML

XML to EDI

XML to Flat File

Flat File to XML Application to Application

Inbound Process Flow Inbound Translation Process 1 If the source document is in: This format...

And the target document is...

The map is defined using...

EDI

Flat file

Mapping Workbench

EDI

XML

Mapping Workbench

XML

Flat file

Mapper

2 If the document is EDI, export the event with the Mapping Workbench. The export

process creates the translation tables associated with the event. If the document is an incoming XML document, save the map with Mapper. The save process creates the transaction tables associated with the event.

Note:

Important: After saving the map, it is important you upload the Mapper to the TrustedLink Enterprise server in the Operations Center. When you save a Mapper map, it is saved as XML files in the c:\program files\client34\data\bdd and bdt directories on the local drive. Use the Operations Center upload function to copy the files to the TrustedLink Enterprise server. 3 Create an inbound event using the Operations Center Client. 4 Upload the translation tables to the server using Operations Center Client.

Make sure you have already defined the path for the Workbench and/or Mapper before attempting to upload. See “Setting the Mapping Tools Paths” on page 217 in “Miscellaneous Functions” on page 217 for instructions for this one time setting.

Note:

5 The Gateway receives the files from a value added network (VAN) or directly from your

trading partner. 6 TL Services reads the documents from the gateway mailbox, determines the appropriate

translation table to use, and then routes the data to the appropriate translator. 7 TL Services writes the translated documents into the application file associated with the

event.


23

OVER VIEW

Translation Process

MAPPING WORKBENCH INBOUND PROCESS

24


1

OVER VIEW

Translation Process

MAPPER INBOUND PROCESS

Outbound Translation Process Flow Outbound Translation Process 1 If the target document is: This format...

And the target document is...

The map is defined using...

Flat file

EDI

Mapping Workbench

Flat file

XML

Mapping Workbench

XML

XML

Mapper

2 If the document is EDI, using mapping workbench, export the event. The export process

creates the translation tables associated with the event. If the target is an outgoing XML document, save the map with Mapper. The save process creates the transaction tables associated with the event.

Note:

Important: After saving the map, it is important you upload the Mapper to the TrustedLink Enterprise server in the Operations Center. When you save a Mapper map, it is saved as XML files in the c:\program files\client34\data\bdd and bdt directories on the local drive. Use the Operations Center upload function to copy the files to the TrustedLink Enterprise server. 3 Create an outbound event using the Operations Center Client.


25

OVER VIEW

Translation Process

4 Upload the translation tables to the server using Operations Center Client.

Make sure you have already defined the path for the Workbench and/or Mapper before attempting to upload. See “Setting the Mapping Tools Paths” on page 217 in “Miscellaneous Functions” on page 217 for instructions for this one time setting.

Note:

5 TL Services determines the translation tables to use for the application file and routes the

data to the appropriate translator. 6 TL Services writes the translated documents into the Gateway mailbox associated with the

event.

26


OVER VIEW

Translation Process

1

MAPPING WORKBENCH OUTBOUND PROCESS


27

OVER VIEW

Translation Process

MAPPER OUTBOUND PROCESS

28


Accessing and Navigating

T

2

his chapter explains how to open and navigate through the Operations Center Client. Topics include:

■

“Opening the Operations Center Client” on page 29

■

“Navigating the Operations Center Client Interface” on page 33

Opening the Operations Center Client Before you can log on to the Operations Center Client, your system administrator must setup an ODBC Data Source Name (DSN) on the client to connect to the TrustedLink Enterprise server database. To open the Operations Center Client 1 Select Start > Programs > Inovis TrustedLink Enterprise > Operations Center Client.

Depending on your system configuration, one of these windows will display when you open the Operations Center Client: For this dialog...

Go to...

Select Data Source

“Select Data Source Window” on page 30

Database Logon: Use the appropriate instructions below for your database type: Informix Logon

“Informix Logon” on page 30

Oracle Logon

“Oracle Logon” on page 31

Sybase Logon

“Sybase Logon” on page 31

SQL Server Login

“SQL Server Login—Windows” on page 32

Secured User Logon

“Secured User Logon” on page 32

2 See the appropriate following section to proceed.

29

A C C E S S I N G A N D N AV I G A T I N G

Opening the Operations Center Client

Select Data Source Window To use the Select Data Source dialog 1 Select the Machine Data Source tab.

2 Select the data source name from the list and click OK.

The Operations Center Client dialog opens. 3 Enter the information required for the database logon.

Database Logon

This information describes the fields available on the logon dialogs, based on the database you use: ■

“Informix Logon” on page 30

■

“Oracle Logon” on page 31

■

“Sybase Logon” on page 31

■

“SQL Server Login—Windows” on page 32

■

“Navigating the Operations Center Client Interface” on page 33

Informix Logon

Here is the Informix logon dialog:

30




Field

Description

Host Name

Name of the machine on which the Informix server resides

Port Number

Port number for the server listener

Server Name

Name of the Informix server as it appears in the sqlhosts file.

Database Name

Name of the database you want to connect to.

User Name

Identifies the user who has an account on the host machine where the Informix database server resides.

Password

Password to confirm the user name.

2

Oracle Logon

Here is the Oracle logon dialog:

Field

Description

Host

Name or the IP address of the server to which you want to connect.

Port Number

Number of your Oracle listener.

SID

Oracle System Identifier that refers to the instance of Oracle running on the server

User Name

Oracle user name.

Password

Oracle password.

Sybase Logon

Here is the Sybase logon dialog:


31



Field

Definition

Network Library

Name of the network library. This specifies which network protocol to use.

Network Address

Network address: , for Winsock

Login ID

Sybase login ID

Password

Sybase password

Database

Sybase password

SQL Server Login—Windows

Here is the SQL Server Login dialog:

Field

Definition

Login ID

User identification on the SQL Server database server for the database specified.

Password

Password used to confirm the user name.

Secured User Logon

You are required to enter a user name and password in the Logon to Operations Center Client dialog, if: ■

You are a secured user by the TrustedLink Enterprise system administrator. If the user account is disabled, you cannot use this account to log into the Operations Center Client. If there is an active account, the login screen displays. If there is not an enabled user account, the login screen is skipped. For more information, see “User Profiles and Browser Access” on page 215 in “System Administrator” on page 207.

■

You have purchased the Access Manager feature. The Operations Center Client detects the Access Manager feature by checking the serial number on the TrustedLink Enterprise server database instance where it just connected. In this case, you cannot login as the System Administrator as the Logon as System Administrator is disabled. At least one user account must exist and cannot be disabled.

32



Navigating the Operations Center Client Interface

2

Navigating the Operations Center Client Interface When you access the Operations Center Client, a dialog opens.

The Operations Center Client toolbar contains buttons for frequently used functions and tools. To select an option, click the button you want to activate. Operations Center Toolbar

The table shows the icons (also called buttons) on the toolbar. Icon

Icon Name

Menu Access, click...

Translation Set Up Icons

Event Wizard.

View

Contacts

View

Trading Partners/Events

View

Applications

View

Interchange

View

Communications

View

Ports

View

Gateway

Miscellaneous Functions

Trading Partner Search


View

33



Icon

Icon Name

Menu Access, click...

Browser

View > Command Manager > Browser

Logging and Reporting

Request Log

View > Command Manager > Request Log

Error Log

View > Error Log

History

View > Error Resolution History

Statistics

View > Statistics > and select... Business Document or Event

Mapping Tools and Translation Table Maintenance

Download Translation Table

View > Command Manager > Download Translation Tables...

Upload Translation Tables

View > Command Manager > Upload Translation Tables...

Upload Repository Tables

View > Command Manager > Upload Repository Tables... Available only if you use Map Versioning

Shortcut to Mapping Workbench

No menu option available

Shortcut to Mapper


See “Setting the Mapping Workbench Path” on page 217. See “Setting the Mapper Path” on page 217.

Windows Translation Scheduler and Other Functions

Schedules

View > Schedules Enabled only when connected to a TrustedLink Enterprise server on Windows.

Schedule Wizard

View > Scheduler Wizard Enabled only when connected to a TrustedLink Enterprise server on Windows.

Special Application Interface (SAP)


System Administrator

View > System Administrator

Available only if you have SAP installed

Operations Center Menu Options

These menus are available in the Operations Center Client:

34

■

“Options Menu” on page 35

■

“View Menu” on page 35


2



Options Menu

You can access options functions using the Options menu. Most of these functions are accessible using the navigation buttons.

View Menu

You can access view functions using the View menu. Most of these functions are accessible using the navigation buttons.


35



36


Contact Management

3

U

se Contact Management to create and manage your contacts, including EDI Representatives. The two sections of this chapter explains contacts, provides an overview of Contact Management, and describes notifications. Subsequent sections describe procedures for working with contacts in TLE. This chapter is organized as follows: ■

“Overview” on page 37

■

“Email Notifications and History Updates” on page 39

■

“About the Contact Management Window” on page 40

■

“Adding a New Contact” on page 44

■

“Assigning EDI Representatives” on page 45

■

“Assigning Contacts” on page 45

■

“Changing the EDI Representative for a Trading Partner” on page 46

■

“Unassigning Contacts” on page 46

■

“Unassigning EDI Representatives for Events” on page 47

■

“Setting Contact Notification Preferences” on page 48

■

“Viewing EDI Rep and Contact Details” on page 49

■

“Viewing Trading Partners or Events for an EDI Rep” on page 50

■

“Viewing Contacts for a Trading Partner or Application” on page 50

■

“Editing Contact Information” on page 50

■

“Deleting a Contact” on page 51

For information about actions that full permission allows when working in Contact Management, see the TrustedLink Enterprise Access Manager User Guide. To migrate your contact data as part of a TLE upgrade, see “Migrating Contact Information” in the “Installing the Operations Center Client” section of the “TrustedLink Enterprise Client Installation“ chapter of the TrustedLink Enterprise Installation Guide.

Overview Contact Management enables you to establish contact people for trading partners, events, and applications, and to route TLE notification messages about translations or delinquent FAs, for example, to the appropriate people. There are two kinds of contacts in TrustedLink Enterprise:

37

CONTACT MANAGEMENT

Overview

■

EDI Representatives: ■

Work in EDI departments and use TrustedLink Enterprise to create maps and setups, troubleshoot problems, and so on.

■

Assigned to trading partners and events.

■

Receive a variety of message types, including all messages that concern trading partners or events to which they are assigned. Notification cannot be suspended.

See “More About EDI Representatives” on page 38. ■

Contacts ■

Work at the same company as EDI Representatives, or at a trading partner company.

■

Assigned to trading partners (as internal or external Contacts) or applications (as internal Contacts only).

■

Receive only delinquent FA notifications, and only if configured to do so.

See “More About Contacts” on page 38. Note that this guide refers to EDI Representative contacts as “EDI Representatives,” and contacts that are not EDI Representatives as “Contacts.” When “contacts” appears with a small “c” in this guide, it refers to both kinds of contacts. For example: When an event is copied from one TLE database instance to another, all associated contacts will also be copied. More About EDI Representatives

Note the following about EDI Representatives: ■

You must assign an EDI Representative to a trading partner to create the trading partner. You can change the EDI Representative later.

■

You do not have to assign an EDI Representative to an event when you create the event. You can add one later, if you wish. Assign different EDI Representatives to different events for a trading partner to more efficiently manage trading relationships that have a high volume of transactions.

Note:

■

A trading partner or an event can have only one EDI Representative, but you can assign an EDI Representative to multiple trading partners or events.

■

A person can be a Contact for some trading partners and an EDI Representative for others.

■

You can make a contact an EDI Representative when you create the contact or when you edit it later.

■

You cannot delete an EDI Representative for a trading partner. You must first change (that is, “reassign”) the trading partner’s EDI Representative, then delete the original.

More About Contacts

Note the following about Contacts:

38

■

You must assign a Contact for an application when you create the application.

■

You must assign a Contact for a trading partner when you create the trading partner.

■

You can assign multiple Contacts to a trading partner or application.


3

CONTACT MANAGEMENT

Email Notifications and History Updates

Email Notifications and History Updates The following tables show for various FA scenarios which contacts receive email notifications and whether or not TLE updates the History-Transactions window. All email notifications regarding batch FAs have a text file attached that includes details. All email notifications regarding real-time FAs have an XML file attached that includes details. For descriptions and examples of FA and other types of messages that TLE sends to contacts, see “Types of Messages to Contacts” on page 180. Abbreviations used in the tables below are as follows: ■

TP—Trading Partner

■

App—Application

■

Y—Email recipient will receive notifications. TLE will update History window. A TP Contact or App Contact will receive notifications only if configured to do so. See “Setting Contact Notification Preferences” on page 48

Note:

■

N—Email recipient will not receive notifications. TLE will not update History window.

EMAIL NOTIFICATIONS AND HISTORY UPDATES FOR BATCH FAS Email Recipients Batch FA Scenarios

FA Status

EDI Rep TP

EDI Rep Event

Contact TP

Contact App

History Update*

Inbound EDI / Outbound FA

Not Expected

N

N

N

N

N

Delinquent FA

Y

N

N

N

N

Outbound EDI / Inbound FA

Acknowledged

N

N

N

N

Y

Duplicate FA

Y

N

N

N

N

Rejected

Y

N

N

N

Y

Not Expected

N

N

N

N

N

Delinquent FA

Y

N

N

N

N

Acknowledged

N

N

N

N

Y

Duplicate FA

Y

N

N

N

N

Rejected

Y

N

N

N

Y

FA Not Expected**

Y

N

N

N

Y

Overridden

N

N

N

N

Y

*History Update refers to whether or not TLE updates the Ack Status column in the HistoryTransactions window after the batch delinquent FA program edidr997 runs. **TLE sends an FA Not Expected message when an FA that is not expected arrives. The status on the History-Transactions window changes from Not Expected to Acknowledged. An FA status of Not Expected means an FA is not expected for the transmission.


39

CONTACT MANAGEMENT

About the Contact Management Window

EMAIL NOTIFICATIONS AND HISTORY UPDATES FOR REAL-TIME FAS Email Recipients Real-time FA Scenarios

Inbound EDI / Outbound FA

Outbound EDI / Inbound FA

FA Status

EDI Rep TP

EDI Rep Event

Contact TP

Contact App

History Update*

Delinquent FA

Y

Y

Y

Y

Y**

Acknowledged

N

N

N

N

Y

Rejected

Y

Y

N

N

Y

Delinquent FA

Y

Y

Y

Y

Y***

Acknowledged

N

N

N

N

Y

Duplicate FA

Y

Y

N

N

N

Rejected

Y

Y

N

N

Y

*History Update refers to whether or not TLE updates the Ack Status, FA Delinq Date, and FA Delinq Notified columns in the History-Transactions window after the real-time delinquent FA program tldr997 runs. (The latter two fields are used only for real-time FAs.) See also “Viewing Delinquent Real-time FA Information” on page 197. **TLE adds a notification timestamp to FA Delinq Notified. In batch FA processing, this field is not used and the History window is not updated. ***TLE adds a delinquency timestamp to FA Delinq Date and a notification timestamp to FA Delinq Notified. In batch FA processing, these fields are not used and the History window is not updated. More About Email Notifications

For details and examples of FA reconciliation and delinquency notification emails and attachments, see the “FA Reconciliation” and “Delinquent FA Processing” sections of the “FA Reconciliation and Delinquency Processing” chapter of the TrustedLink Enterprise Translation Setup Guide. For a complete list of automatic email messages in TLE, see the “Automatic Email Messages” chapter in the TrustedLink Enterprise System Messages Guide. For example, the “MEK Failure” message in that list refers to email notification of the designated contact if a problem occurs in the MEK process when translating an outbound XML file into EDI. For information about the email message you can configure ALE to send when the SAP server is unavailable, see the “ALE Interface Operations” chapter of the TrustedLink Enterprise SAP/R3 Setup and User Guide. (Applies only to customers using SAP with TLE.)

About the Contact Management Window Use the Contact Management window to add, update, assign, and delete contacts. To access Contact Management

Click Contacts.

The Contact Management window opens to the Contact List tab.

40


3

CONTACT MANAGEMENT


The window is divided into four tabs. The data in some panels in the tabs are organized into columns. Wherever columns appears, you can sort the list by clicking the column headers. The procedures in this chapter describe how use Contact Management. A brief overview and screen shots of the four tabs follows and provides a sense of the many actions you can perform. After making changes on any of the tabs, click OK or Apply to save your changes. The difference is that clicking OK will close Contact Management after saving, and clicking Apply leaves Contact Management open after saving. To not save changes, click Cancel. The four tabs are as follows: ■

■

Contact List—Note the following (for graphic see preceding screen shot): ■

The tab displays on the left a list of existing contacts and on the right details of the selected contact.

■

Actions include the following: ■

Use the horizontal scroll bar to display more information for contacts.

■

Add new contacts.

■

Edit details for existing contacts.

■

Delete existing contacts.

■

Define contacts as EDI Representatives.

EDI Rep Associations—Note the following:


41

CONTACT MANAGEMENT


■

The tab’s three sections lists EDI Representatives, all trading partners (which must have an EDI Representative to be created), and all events for the selected trading partner. An event may or may not have an EDI Representative. Note: This tab does not list trading partner Contacts, which are not EDI Representatives. The Trading Partner Associations tab lists them.

■

■

42


View an EDI Representative trading partner or event associations.

■

Assign an EDI Representative to a trading partner or event.

■

Change a trading partner’s EDI Representative.

■

Unassign events for EDI Representatives.

Application Associations—Note the following: ■

The tab displays lists of applications and Contacts.

■


View Contact(s) assigned to an application.

■

Assign Contact(s) to an application.

■

Set notification preferences for Contact(s) assigned to an application.


CONTACT MANAGEMENT


■

■

3

Unassign Contact(s) from an application.

Trading Partner Associations—Note the following: ■

The tab displays lists of trading partners and Contacts. Trading partner EDI Representatives are listed on the EDI Rep Associations tab.

■


View Contact(s) assigned to a trading partner.

■

Assign Contact(s) to a trading partner.

■

Set notification preferences for Contact(s) assigned to a trading partner.


43

CONTACT MANAGEMENT

Adding a New Contact

■

Unassign Contact(s) for a trading partner.

Adding a New Contact Use this procedure to add a new contact or to create a new contact using data from an existing contact. The latter can save you time. To add a new contact 1 Click Contacts.

The Contact Management window opens. 2 In the Contact List tab, perform the appropriate action: To create a new...

Do this:

Contact

Click New, or right-click in the Contact List panel and select New.

Contact from an existing contact

Right-click in the Contact List panel the contact you want to copy, then select Create from Current.

To cancel the action at any time, click Contacts > Cancel Add, or right-click in the list and click Cancel Add in the popup menu. To undo typing in the current field, right-click anywhere except in another field and click Undo in the popup menu, or click Contacts > Undo. Note:

3 Type or modify these fields on the right side of the Contact List tab:

44

Field

Description

First Name

Contact’s first name. Maximum 20 characters.

Last Name

Contact’s last name. Maximum 20 characters.

Title

Contact’s title. Maximum 20 characters.


3

CONTACT MANAGEMENT

Assigning EDI Representatives

Field

Description

Company

Name of contact’s company.

Address

Address of contact’s company.

Contact Type

Description of the contact.

Phone

Contact’s phone number. Maximum 25 characters.

Fax

Contact’s fax number. Maximum 25 characters.

Mobile

Contact’s mobile phone number. Maximum 25 characters.

Email Address

Contact’s email address.

Email Note

Write an email note to be contained in any email notification to the contact. Leave the field blank to not add an email note to notifications to this contact.

Comments

Add descriptive comments to this contact entry (for example, hours of telephone availability). The comments are for the user and are not used in notifications. Maximum 140 characters.

EDI Representative

Select this check box to designate this contact as an EDI Representative.

4 To assign the contact, see “Assigning EDI Representatives” on page 45 and “Assigning

Contacts” on page 45. 5 Click OK or Apply to save your changes.

Assigning EDI Representatives This procedure applies only to EDI Representatives. To assign a Contact, see “Assigning Contacts” on page 45. You can assign EDI Representatives to trading partners or events. You can also assign an EDI Representative to a new event in the Event Wizard, or for an existing event use the Event Properties-EDI dialog. To assign EDI Representatives 1 Click Contacts.

The Contact Management window opens. 2 Click the EDI Rep Associations tab.

The tab opens. 3 In the Trading Partners panel or the Events panel, click a trading partner or event name,

and drag it onto the name of the EDI Rep in the EDI Representatives panel. If the trading partner or event already has an EDI Rep assigned to it, a message will ask you if you want to unassign the EDI Rep. If you do, click Yes. 4 Click OK or Apply to save your changes.

Assigning Contacts This procedure applies to Contacts only. To assign an EDI Representative contact, see “Assigning EDI Representatives” on page 45.


45

CONTACT MANAGEMENT

Changing the EDI Representative for a Trading Partner

To assign a Contact 1 Click Contacts.

The Contact Management window opens. 2 Click the Application Associations or Trading Partner Associations tab, depending on

which kind of assignment you want to make. The tab opens. 3 Select the Contact in the list in the panel on the right, and drag it onto the name of the

application or trading partner in the left panel. To view existing Contacts for the application or trading partner, click the application or trading partner’s plus icon (+) to display the Contacts. No plus sign means that no Contacts have been assigned.

Note:

4 Click OK or Apply to save your changes.

Changing the EDI Representative for a Trading Partner Use this procedure to change the EDI Representative assigned to a trading partner. If you want to delete an EDI Representative from TLE, you can use this procedure to assign a new EDI Representative to the trading partner or event, which is necessary before you can delete the former EDI Representative. See also “Unassigning EDI Representatives for Events” on page 47. To change the EDI Representative for a trading partner 1 Click Contacts.


The tab opens. 3 In the EDI Representatives panel, find the current contact that you want to change. Click

its plus sign (+), then click the plus sign next to Trading Partners. A list of trading partners displays for which the contact is the EDI Representative. 4 In the EDI Representatives panel, right-click the trading partner that you want to assign a

different EDI Representative, and choose Reassign TP in the popup menu. Note:

You can also double-click the trading partner in the Trading Partners panel.

The Trading Partner Properties dialog opens. 5 Select a different contact in the EDI Rep dropdown, then click OK or Apply to save your

changes. The assignment is updated in the Contact Management window, EDI Rep Associations tab.

Unassigning Contacts Use the following procedures to unassign Contacts from trading partners or applications. The first applies to a specific Contact for the trading partner or application. The second applies to all Contacts for the trading partner or application.

46


3

CONTACT MANAGEMENT

Unassigning EDI Representatives for Events

For EDI Representatives, see “Unassigning EDI Representatives for Events” on page 47 To unassign a Contact from an application or trading partner 1 Click Contacts.

The Contact Management window opens. 2 Click the Applications Associations or Trading Partner Associations tab.

The tab opens. 3 In the left panel, click the plus sign (+) next to an application or trading partner to

display the Contact(s) assigned to it. No plus sign means that no Contacts have been assigned. 4 Right-click on the Contact and choose Unassign. 5 Click OK or Apply to save your changes.

To unassign all Contacts from an application or trading partner 1 Click Contacts.

The Contact Management window opens. 2 Click the Application Associations or Trading Partner Associations tab.

The tab displays a list of applications or trading partners. 3 In the left panel, right-click the application or trading partner for which you want to

unassign all Contacts. 4 Choose Unassign All Contacts in the popup menu. 5 Click OK or Apply to save your changes.

Unassigning EDI Representatives for Events Note: You cannot unassign EDI Representatives for trading partners. You can change them,

however. See “Changing the EDI Representative for a Trading Partner” on page 46. Use following procedures to unassign EDI Representatives from events. The first procedure applies to one event. The second applies to all events for which the EDI Representative is assigned. For Contacts, see “Unassigning Contacts” on page 46. To unassign an EDI Representative from one event 1 Click Contacts.


The tab opens. 3 Right-click the event in the Events panel (requires its trading partner to be selected) or in

the expanded Events tree under the contact in the EDI Representatives panel, then choose Unassign Event in the popup menu. 4 Click OK or Apply to save your changes.

To unassign an EDI Representative from all events 1 Click Contacts.


47

CONTACT MANAGEMENT

Setting Contact Notification Preferences


The tab opens. 3 In the left panel, right-click the EDI Representative, then choose Unassign All Events in

the popup menu. 4 Click OK or Apply to save your changes.

Setting Contact Notification Preferences Note: You do not set notification preferences for EDI Representatives because EDI Reps receive notifications automatically.

Use the following procedures to have Contacts receive (or not receive) automatic email notifications when their associated trading partners or applications have delinquent real-time FAs. Set notification preferences by individual Contact or by trading partner or application. When you activate notification, the names of impacted Contacts appear in bold text in Contact Management. To set the notification preference for a trading partner Contact 1 Click Contacts.

The Contact Management window opens. 2 Click the Trading Partner Associations tab. 3 In the left panel, click the plus sign (+) for the trading partner to display the assigned

Contacts. 4 Right-click on the Contact, then select a notification option: ■

Notify for TP—Notify the Contact about delinquent FAs for this trading partner.

■

Notify for All TPs—Notify the Contact about delinquent FAs for all trading partners.

■

Unnotify for All TPs—Do not notify this Contact about delinquent FAs for any trading partners.

A check mark next to the option indicates the option is selected. Click the option to unselect it. 5 Click OK or Apply to save your changes.

If you activated notification, the Contact name changes to bold text. To set the notification preference for an application Contact 1 Click Contacts.

The Contact Management window opens. 2 Click the Application Associations tab. 3 In the left panel, click the plus sign (+) for the application to display the assigned

Contacts. 4 Right-click on the Contact, then select a notification option: ■

48

Notify for App—Notify the Contact about delinquent FAs for this application.


3

CONTACT MANAGEMENT

Viewing EDI Rep and Contact Details

■

Notify for All Apps—Notify the Contact about delinquent FAs for all applications.

■

Unnotify for All Apps—Do not notify this Contact about delinquent FAs for any applications.

In the popup menu, a check mark indicates the option is selected. Click the option to unselect it. 5 Click OK or Apply to save your changes.

If you activated notification, the contact name changes to bold text. To set the notification preference for a trading partner 1 Click Contacts.

The Contact Management window opens. 2 Click the Trading Partner Associations tab. 3 In the left panel, right-click on the trading partner name, then select a notification

option: ■

Notify All Contacts—Send delinquent FA notifications to all Contacts assigned to the trading partner.

■

Unnotify All Contacts—Do not send delinquent FA notifications to any Contacts assigned to the trading partner.


If you activated notification, all Contact names for the trading partner change to bold text. To set the notification preference for an application 1 Click Contacts.

The Contact Management window opens. 2 Click the Application Associations tab. 3 In the left panel, right-click on the application name, then select a notification option: ■

Notify All Contacts—Send delinquent FA notifications to all Contacts assigned to the application.

■

Unnotify All Contacts—Do not send delinquent FA notifications to any Contacts assigned to the application.


If you activated notification, all Contact names for the application change to bold text.

Viewing EDI Rep and Contact Details Use the Contact Management window to view details of your existing contacts. To view existing contacts 1 Click Contacts.

The Contact Management window opens. 2 In the Contact List tab, peruse the list of contacts. Details appear in the fields on the right.


49

CONTACT MANAGEMENT

Viewing Trading Partners or Events for an EDI Rep

Viewing Trading Partners or Events for an EDI Rep Use the following procedure to view a list of trading partners or events associated with an EDI Representative. For Contacts, see “Viewing Contacts for a Trading Partner or Application” on page 50. To view trading partners or events associated with an EDI Rep 1 Click Contacts.


The tab opens. 3 Click the plus sign (+) next to the EDI Rep that you want to view, then click the plus sign

(+) next to Trading Partners or Events. A list of trading partners or events associated with the selected EDI Representative displays. No plus sign next to Trading Partners or Events means the EDI Representative has not been assigned a trading partner or event, depending on the list heading.

Note:

Viewing Contacts for a Trading Partner or Application Use the following procedure to view a list of Contacts for a trading partner or application. To view Contacts for a trading partner or application 1 Click Contacts.

The Contact Management window opens. 2 Click the Application Associations or Trading Partner Associations tab.

The tab displays a list of applications or trading partners. 3 In the left panel, click the plus sign (+) next to the application or trading partner for

which you want to view a list of Contacts. The list displays. No plus sign next to an application or trading partner means that it has not been assigned a Contact.

Note:

Editing Contact Information Use the following procedure to change contact information. To modify contact information 1 Click Contacts.

The Contact Management window opens. 2 In the Contact List tab, select the contact to modify, then edit the fields on the right side

as needed. To cancel the action at any time, click Contacts > Cancel Add, or right-click in the list and click Cancel Add in the popup menu. To undo an edit, right-click anywhere except in another field and click Undo in the popup menu, or click Contacts > Undo. Note:

50


3

CONTACT MANAGEMENT

Deleting a Contact


Deleting a Contact Use the following procedure to delete a contact from TLE. Important: You cannot reverse a deletion.

To delete a contact 1 Click Contacts.

The Contact Management window opens. 2 Select the contact to delete, and click Delete, or right-click and choose Delete in the

popup menu. If the contact is assigned to a trading partner or application, TLE asks if you want it to unassign the contact and then delete it. Important: You cannot delete a contact that is EDI Representative for a trading partner.

First, assign a new EDI Representative contact to the trading partner, then delete the original EDI Representative. 3 Click Yes to delete, No to not delete.


51

CONTACT MANAGEMENT

Deleting a Contact

52


Trading Partners

I

4

nformation about the trading partner must be added to the database before you create an event. You can add a trading partner or modify information about a trading partner using the procedures in this chapter.

For instructions about how to create and maintain Events, see “Event Wizard” on page 105. Topics include: ■

“Opening the Trading Partners/Events Window” on page 53

■

“Creating a New Trading Partner” on page 54

■

“Searching for a Trading Partner” on page 67

■

“Modifying Trading Partner Properties” on page 71

■

“Deleting Trading Partners and Properties” on page 72

Opening the Trading Partners/Events Window The Trading Partners/Events window, is divided into two sections. The left section displays trading partners; the right section displays events associated with the selected trading partner. To open the Trading Partners/Events window 1 Click Trading Partners/Events.

53

TR A D I N G P A R T N E R S

Creating a New Trading Partner

The Trading Partners/Events dialog opens.

2 Perform the appropriate action: To

See

Create a new Trading Partner

“Creating a New Trading Partner” on page 54

Search for a Trading Partner

“Searching for a Trading Partner” on page 67

Change a Trading Partner

“Modifying Trading Partner Properties” on page 71

Delete a Trading Partner or some trading partner properties

“Deleting Trading Partners and Properties” on page 72

Creating a New Trading Partner Use the procedures in this section to create a new trading partner. This section is organized by the tabs and procedures used to create a trading partner: Tab

See

General

“Defining the General Properties” on page 55.

Alphanumeric Control Def “Defining the Alphanumeric Control Definitions” on page 56 Contacts

“Defining the Contacts” on page 58 Note: Before you can save the new trading partner, you must assign an EDI Representative to the trading partner.

Alias

“Defining the Alias Properties” on page 59

Interchange Reference

“Defining Interchange Reference Properties” on page 60

FG Control No. Maint.

“Defining the FG Control Number Maintenance Properties” on page 65

To create a new trading partner 1 From the Trading Partners/Events dialog, click

54

New in Trading Partners section.


4



The Trading Partner Properties dialog opens to the General tab.

2 Use property tabs as described in the procedures that follow to configure the trading

partner. Defining the General Properties

Use the Trading Partner Properties window to define the Trading Partner General properties: To define trading partner properties 1 Type the following information: Field

Description

Company

Company name of the trading partner. Maximum 30 characters.

Business Unit

Division name or plant location. Maximum 30 characters.

Key

Unique ID for this trading partner. Maximum 35 characters. One possible usage of this field is to identify a department or division in your company. For example: ■

ANSI—GS02 (Sender ID) on an inbound document; GS03 (Receiver ID) on an outbound document

■

EDIFACT—UNB02:01 or UNB02:03

If you are using the UNG envelope, we look at UNG02:01. Address Information

Trading partner’s address. Including: Address 1, Address 2, City, State, Postal Code and Country (code).


55



Field

Description

Validation Type

Select one of the types from the dropdown:

Classification FG Uniqueness

■

Interchanges and FG Validation: Validates both the interchange and functional group (FG) control numbers for a unique number.

■

No Duplicate Validation: Does not validate control numbers.

■

No FG Level Validation: Validates only the interchange control number.

■

No Interchange Level Validation: Validates only functional group control numbers.

■

Sequential Validation: Validates all control numbers. Each number received = one plus the last number received.

Your trading partner’s type of business. Select from the dropdown. Select Yes or No from the dropdown. If validating (FG) control numbers, this entry indicates whether the FG type indicator (such as PO, IN, ORDERS, etc.) should be included as part of the validation criteria.

EDI Rep

The EDI Representative is your internal person responsible for managing EDI or XML documents for this trading partner. You must select an EDI Rep. Select from the dropdown.

Comments

Type your comments here. Maximum 240 characters.

2 Perform the appropriate action: ■

Go to the next section, “Defining the Alphanumeric Control Definitions” on page 56.

■

Make other changes to the Trading Partner. Click the appropriate tab:

Defining the Alphanumeric Control Definitions

This section applies to EDIFACT and TRADACOM only.

56


4



To define the alphanumeric control definitions 1 From the Trading Partner Properties window, click the Alphanumeric Control Def. tab:.

2 Type the following information: Field

Description

Interchange Control Number

Inbound:

Interchange Control Number

Functional Group Control Number


■

Number of Constant Prefix Characters: Number of alphanumeric characters that make up the constant prefix. The constant prefix occurs before the sequence digits in the inbound interchange control number.

■

Number of Sequence Digits: Number of digits that indicates the length of the numeric sequence. The sequence digits follow the constant prefix in the inbound interchange control number. Valid values are 0 to 14. The default is 14.

Outbound: ■

Constant Prefix: Constant prefix appears before the sequence digits in the outbound interchange control number. You can enter up to 13 characters. Do not use spaces.

■

Number of Sequence Digits: Number of digits that indicates the length of the numeric sequence. The sequence digits follow the constant prefix in the outbound interchange control number. Valid values are 0 to 14. The default is 14.

Inbound: ■

Number of Constant Prefix Characters: Number of alphanumeric characters that make up the constant prefix. The constant prefix appears before the sequence digits in the inbound functional group (FG) control number.

■

.Number of Sequence Digits: Number of digits that indicates the length of the numeric sequence. The sequence digits follow the constant prefix in the functional group control number. Valid values are 0-14. The default is 14.

57



Field

Description

Functional Group Control Number

Outbound:

Accept inbound transmissions on error?

■

Constant Prefix: Constant prefix appears before the sequence digits in the outbound functional group (FG) control number. You can enter up to 13 alphanumeric characters with no empty spaces.

■

Number of Sequence Digits: Number of digits that indicates the length of the numeric sequence. The sequence digits follow the constant prefix in the outbound functional group (FG) control number. Valid values are 0 to 14. The default is 14.

If you select this check box, a warning message is written to the inbound translation log if the transmission violates the alphanumeric control number. The transmission will be translated.


If you are finished editing an existing Trading Partner, click OK. The Trading Partner Properties dialog closes and your entries are saved.

■

Continue with the next section, “Defining the Contacts” on page 58.

■


Defining the Contacts

For more information about contacts, which includes EDI Representatives, see“Contact Management” on page 37. Note that the capitalized “Contacts” in this guide refers to Contacts that are not EDI Representatives. Use the Trading Partner Properties, Contacts tab, to manage your internal and external Contacts for this trading partner. These are people who you may wish to ask questions or who you wish to receive automatic delinquent FA notifications. To create a trading partner, you must assign a Contact. You can assign more than one. The Contacts tab links to the Contact Management window, where you will perform the following tasks: ■

To add a new trading partner Contact, click Add New Contact. See “Adding a New Contact” on page 44.

■

To assign a Contact for the trading partner, click Assign Contact. See “Assigning Contacts” on page 45.

■

To set a delinquent FA notification preference for a Contact for this trading partner, double-click the Trading Partner Properties window. See “Setting Contact Notification Preferences” on page 48.

To unassign a Contact for the trading partner, you can use the Trading Partner Properties window, Contacts tab, as described below. Note: You can also unassign Contacts in the Contact Management window, Trading Partner Associations tab. See “Unassigning Contacts” on page 46.

To access the Contacts tab 1 From the Trading Partner Properties window, click the Contacts tab.

58


4



The tab opens and displays Contacts assigned to the trading partner. Use the appropriate procedure that follows.

To unassign a trading partner Contact in Trading Partner Properties 1 From the Trading Partner Properties window, click the Contacts tab. 2 Select the Contact in the list to unassign from the trading partner. 3 Click Unassign Contact. 4 Click OK or Apply to save your changes.

The Contact is no longer assigned to the trading partner. Defining the Alias Properties

Use the alias properties when the trading partner’s functional group ID is not unique. For example, type a combination of the interchange and functional group IDs.


59



To define the alias properties 1 From the Trading Partner Properties window, click the Alias tab.

2 Type this information: Field

Description

Primary ID

Associated with the interchange ID. Maximum 35 characters.

Secondary ID

Associated with the functional group ID. You can enter up to 35 characters.


If you are finished creating or editing the Trading Partner, click OK. The Trading Partner Properties dialog closes and your entries are saved.

■

Continue with the next section, “Defining Interchange Reference Properties” on page 60.

■

Make other changes to the Trading Partner, click the appropriate tab.

Defining Interchange Reference Properties

An interchange is the entire collection of documents and envelope information that makes up a transmitted EDI or XML document. For EDI, an interchange consists of one or more documents or functional groups preceded by an interchange header segment (ISA or UNB) and followed by an interchange trailer segment (IEA or UNZ). The outbound Translator builds the interchange level header segment. For XML, the interchange is specified by data within the XML document with tags that are defined by the user. The user needs to include this as part of the mapping exercise. These rules apply to interchanges: ■

60

For EDI documents, an interchange must be set up only for outbound events.


4



■

For XML documents, an interchange is required for inbound events and is optional for outbound events. If the document is sent through Inovisworks then the interchange is required for the outbound event.

If you use the Event Wizard to set up an outbound Event, you associate an interchange with your trading partner in the final window. You can either create a new interchange or select an existing one for your trading partner. You can set up a new interchange or modify existing ones using the Interchange window. You can create a new interchange by: ■

Using the properties of an existing interchange.

■

Creating a new one without existing information.

Important: When you send outbound EDI documents to the trading partner, an Interchange is required. When you send or receive XML documents, an interchange is required.

To define the interchange reference properties 1 From the Trading Partner Properties window, click the Interchange Reference tab.

2 Click New to add a new Interchange Reference.


61



The Interchange Reference dialog opens.

3 Select an Internal Division ID from the dropdown.

This value must match the Internal Division ID as defined in the Event properties. 4 For Interchange, either: ■

Select an existing interchange from the list and click OK.

■

Click New to create a new interchange, and continue with “Adding an Interchange Reference” on page 62.

5 Click OK.

The Trading Partner Properties tab reopens to the Interchange Reference tab. 6 Perform the appropriate action: ■

If you are finished creating or editing the Trading Partner, click OK.

The Trading Partner Properties dialog closes and your entries are saved. ■

Continue with “Defining the FG Control Number Maintenance Properties” on page 65.

■


Adding an Interchange Reference To add an interchange reference 1 From the Trading Partners Interchange Reference tab, select the trading partner for whom

you want to add an interchange reference. 2 Click Properties, then the Interchange Reference tab. 3 Click New.

The Interchange Type dialog opens.

4 Select one of the following interchange types and click OK.

62


4



■

EDI and continue with step 5.

■

XML and continue with step 6.

The dialog that opens depends on your selection. 5 The EDI Interchange Properties dialog opens.

Type this information and continue with step 7. Field

Description

Trading Partner

Qualifier—Defines the trading partner’s receiver ID qualifier. Values for this field should come from the definitions of the EDI standard used. Maximum 4 characters. Identifier—Trading partner receiver ID. This is a corporate level ID for the trading partner. Maximum 35 characters.

Internal

Qualifier—Value that defines the internal sender’s ID qualifier. Values for this field come from the definitions of the EDI standard used. Maximum 4 characters). Identifier—Internal sender ID. This is a corporate level ID sender for the sender. In the U.S., this is usually the DUNS number. Maximum 35 characters.

Standards ID

EDI standard to be used with this interchange. For X12 Standards 4020 and above, you can use this for the repeating element delimiter. Example: For ANSI X12 Standards 4010 or earlier, the X12 standard is U.

Version

Interchange version of the EDI standard to be used with this interchange. Maximum 5 characters. This value can range from 00200 - 00501 and is usually the same as the EDI document version. Example: For a 4010 ANSI ASC X12 standard, type 0401.

Delimiter Characters

Select from the dropdown. The hex value of the character separator to be used in transmission displays in the field along with the character or control character shown in parentheses. Important: Be sure to choose character values that are not found in the data content of the EDI document.


63



6 The XML Interchange Properties dialog opens.

Type this information: Field

Description

Trading Partner

Identifier—Trading partner ID. This is a corporate level ID for the trading partner. Maximum 35 characters. XML Tag Name—The XML element tag name or XPATH location of the trading partner.

Internal

Identifier—Internal ID. This is a corporate level ID for the receiver. In the U.S., this is usually the DUNS number. Maximum 35 characters. This must match the internal division ID on the document properties. XML Tag Name—The XML element tag name or XPATH location of the internal sender ID.

7 Click OK.

The Interchange Reference dialog opens.

8 Select an Internal Division ID, and select the interchange envelope from the Interchange

list box. 9 Click OK.

The interchange reference you added appears in the list on the Interchange Reference tab of the Trading Partner Properties window. 10 Select the new interchange from the list and click OK. 11 Click OK.

The Trading Partner Properties tab reopens to the Interchange Reference tab.

64


4




If you are finished creating or editing the Trading Partner, click OK. The Trading Partner Properties dialog closes and your entries are saved.

■

Continue with the next section, “Defining the FG Control Number Maintenance Properties” on page 65.

■


Defining the FG Control Number Maintenance Properties

Before defining the Function Group control number information, review the rules that apply to: ■

■

Internal Division ID: ■

When adding a new FG Control Number, enter the functional group sender ID. Maximum nine alphanumeric characters.

■

When viewing properties, this field cannot be updated.

■

For the ANSI ASC X12 and TDCC standards, this key is in element two of the GS segment.

■

For the UN/EDIFACT standard, this key is in element two, sub one of the UNB segment, unless the transmission includes a UNG segment. In which case it looks at the UNG element three, sub one.

■

In the TRADACOM standard, the key is in element 2, sub 1 of the STX segment.

FG Type: ■

For the ANSI ASC X12 and TDCC standards, this code appears in the first element of the GS segment.

■

In the EDIFACT and TRADACOM standards, this code is identical to the document ID (message ID).


65



To define the Functional Group control number maintenance properties 1 From the Trading Partner Events window, click the FG Control No. Maint. tab.

2 Add a new control number, click New.

The FG Control Number Maintenance Properties dialog opens.

3 Type this information:

66

Field

Description

Company

Company name displayed on the Document tab. To update this value, see “Defining the General Properties” on page 55.

Bus. Unit

Business unit displayed on the Document tab. To update this value, see “Defining the General Properties” on page 55.

Key

Key displayed on the Document tab. To update this value, see “Defining the General Properties” on page 55.

Internal Div. ID

Value that represents the business group sending the transmission. Maximum 9 alphanumeric characters.

FG Type

Code that identifies the document’s functional group (FG) type. Maximum 6 alphanumeric characters.


4


Searching for a Trading Partner

Field

Description

Control No.

Unique number to validate the transmission level of the EDI translation. Maximum 14 numeric characters. The control number is the starting number for the Trading Partner and IntDivID combination. The next EDI group generated has a control number one higher than the entered number. Important: X12 allows only nine characters. If you enter a number greater than 999,999,999 TrustedLink Enterprise cannot generate group control numbers. This cannot be reset resulting in a fatal error.

Status

Document Type

Indicates whether the documents in the functional group are sent as test or production. ■

Start-up—indicates the Event is set up, but not ready for transmission.

■

Test—Translator translates the document as a test document.

■

Production— Translator translates the document as a production document.

■

Hold— temporarily places the Event on hold and prevents the documents from being translated.

■

Release—disengages the Hold status and translates the documents as test documents.

■

Inactive— indicates the Event is no longer being used and documents will not be translated.

Select one of the following depending on type of document you are trading: ■

EDI

■

XML

4 Click OK.

The Trading Partner Properties dialog reopens displaying your entries on the FG Control Maint. tab. 5 Perform the appropriate action. If you are finished creating or editing the Trading Partner,

click OK. The Trading Partner Properties dialog closes and your entries are saved. 6 To continue making changes to the Trading Partner, click the appropriate tab:

Searching for a Trading Partner This section describes the options available for performing a trading partner search. You can search for a trading partner using any of the procedures in this section. To search by: ■

Event, see “Searching by Event” on page 68.

■

Application, see “Searching by Application” on page 69.

■

Communication provider, see “Searching by Communication Provider” on page 70.

Perform the search by selecting different options within each type of criteria.


67



Searching by Event To search for a trading partner by event 1 Click Trading Partner Search.

The Trading Partner Search dialog opens to the Event tab.

2 Select the search options from these fields: Field

Description

Document ID

Select the document ID from the dropdown for the trading partner that is defined when associated Events are created. Required.

Direction

Select the direction inbound or outbound events to help narrow the search.

Standard

Perform the appropriate action:

Version

Business Group

■

To search by all standards, leave blank.

■

Select to search by a specific EDI standard.

Perform the appropriate action: ■

To search by all versions, leave blank.

■

Select to search by an EDI standard version you select from the dropdown.


To search by all business groups, leave blank.

■

Select to search by a specific application business group. You select from the dropdown.

3 Click Search.

68




4

The Trading Partners Referencing Document ID dialog opens displaying a list of documents.

4 Click X in the right corner of the screen

to close the window.

Searching by Application To search for a trading partner by associated applications 1 Click Trading Partner Search.

The Trading Partner Search dialog opens to the Event tab 2 Click the Application tab.

The Trading Partner Search dialog opens to the Application tab.


69



3 Select from these search options: Field

Description

Business Group


Name

Subsystem

Release

■

To search by all business groups, leave the box unchecked.

■

Select to narrow the search by business group. Type the first few letters or numbers to sort the list, or select the business group from the dropdown.


To search by all application names, leave the box unchecked.

■

Select to narrow the search by the application name. Type the first few letters or numbers to sort the list, or select the business group from the dropdown.


To search by all subsystems, leave the box unchecked.

■

Select to narrow the search by subsystem. Type the first few letters or numbers to sort the list, or select the business group from the dropdown.


To search by all subsystems, leave the box unchecked.

■

Select to narrow the search by release. Type the first few letters or numbers to sort the list, or select the release from the dropdown.

4 Click Search.

The Application Trading Partners List dialog opens displaying the results of the search. 5 Click X in the right corner of the screen to close the window.

Searching by Communication Provider To search for a trading partner by communications information 1 Click Trading Partner Search.

The Trading Partner Search dialog opens to the Event tab. 2 Click the Communication tab.

70


4


Modifying Trading Partner Properties

The Trading Partner Search dialog opens to the Communication tab.

3 Type these search options: Field

Description

Provider

Option is always active when doing a communication search. Required.

Mailbox


Internal Division ID

■

To search by all mailboxes, leave the box unchecked.

■

Check box to narrow the search by mailbox and type the first few letters or numbers to sort the list, or select the mailbox from the dropdown.


To search by all internal division IDs, leave the box unchecked.

■

Select to narrow the search by internal division ID. Type the first few letters or numbers to sort the list, or select from the dropdown.

4 Click Search.

The Trading Partner Using Provider dialog opens with the search results. 5 Click Close.

The Trading Partner Using Provider dialog opens with the search results. 6 Click Close.

Modifying Trading Partner Properties You can change the information in any of the active fields on the Trading Partner Properties window. To change an inactive field, you must create a new trading partner. To modify a trading partner’s properties 1 Click Trading Partners/Events.

The Trading Partners/Events dialog opens. 2 Select the trading partner you want to modify and click Properties.


71


Deleting Trading Partners and Properties

The Trading Partner Properties dialog opens to the General tab. 3 Use the property tabs to modify or configure the trading partner as it applies to your

configuration: Tab

See

General

“Defining the General Properties” on page 55.

Alphanumeric Control Def

“Defining the Alphanumeric Control Definitions” on page 56

Contacts

“Defining the Contacts” on page 58

Alias

“Defining the Alias Properties” on page 59

Interchange Reference

“Defining Interchange Reference Properties” on page 60

FG Control No. Maint.

“Defining the FG Control Number Maintenance Properties” on page 65

4 Click Apply. 5 Click OK.

The Trading Partner Properties window closes and your entries are saved.

Deleting Trading Partners and Properties You cannot delete a trading partner if events are associated with the trading partner. Some properties must be deleted before you can make a change. This section describes how to delete a trading partner and some trading partner properties. Topics include: ■

“Deleting a Trading Partner” on page 72

■

“Deleting an Interchange Reference” on page 72

■

“Reassigning Trading Partners to Interchanges” on page 73

To delete a contact, see “Deleting a Contact” on page 51. Deleting a Trading Partner

All events associated to a trading partner, must be deleted before you can delete a trading partner. To delete a trading partner 1 Click Trading Partners/Events.

The Trading Partners/Events dialog opens. 2 Select the trading partner you want to delete from the Trading Partners list and click

Delete. 3 Click Yes to confirm the delete trading partner request.

The trading partner is deleted. Deleting an Interchange Reference To delete an interchange reference 1 Click Trading Partners/Events.


72




4

2 Select the trading partner with the interchange reference you want to delete and click

Properties. The Trading Partner Properties dialog opens to the General tab. 3 Click the Interchange Reference tab. 4 Select an interchange reference in the list and click Delete.

Reassigning Trading Partners to Interchanges

When an interchange is deleted, the trading partners associated is disabled. If you want to continue to use a given trading partner, it must be reassigned to another interchange. To reassign an interchange 1 Create a new interchange, if one does not exist that you want to use.

See “Adding an Interchange Reference” on page 62. 2 Reassign the trading partner to the new/existing interchange by doing the following: a Open the Trading Partner Properties window and click the Interchange Reference

tab. b Select the new/existing and click OK.


73



74


5

Applications

T

his chapter provides information about the following topics:

■

“Application Overview” on page 75

■

“Opening an Application” on page 76

■

“Creating an Inbound Application” on page 77

■

“Creating an Outbound Application” on page 84

■

“Maintaining Applications” on page 101

Application Overview TrustedLink Enterprise uses Application/Document architecture for all translation types. The task of identifying the application and the document is completed in advance. The direction, inbound or outbound, is indicated by the identification of the application and document. TrustedLink can accommodate the translation requirements for many different business units inside a company. The business units are defined in TrustedLink Enterprise through the application portion of the Application/Document architecture. The document portion of the architecture is the common format you use to convey your business data to the outside world. If you are required to receive EDI data (document) and translate it to an application format, this is an inbound translation event. If you are required to produce EDI (document) from an application format, this is an outbound translation event. TrustedLink Enterprise can also translate from one application format to a different application format, commonly referred to as application-to application mapping. With TrustedLink Enterprise, an application serves as either a target or a source for test or translated production documents. There are four types of applications: Application Type

Description

Inbound Flat File

A set of defined records populated from the mapped portion of an EDI or XML transmission.

Inbound XML

An XML document populated from the mapped portion of an EDI transmission.

Outbound Flat File

Used to populate either XML or EDI documents.

Outbound XML

Used to populate an EDI document.

You can define an application by: ■

Creating an inbound or outbound application

75

APPLICATIONS

Opening an Application

■

Creating a new application from an existing application

■

Modifying an application

■

Deleting an application. You cannot delete an application if it has an event associated with it.

■

Adding a path/file for test data to your application.

■

Adding or modifying an internal cross-reference

■

Viewing an application’s trading partners

Internal Cross-References

Internal cross-references are defined in the Application properties. Internal cross-references perform different functions, depending on the direction of the event associated with them. For Events with this Direction...

Internal Cross-References...

Inbound

Outbound

■

Used only in conjunction with the ID Cross-reference command in TrustedLink Workbench.

■

Look up values and return a corresponding value.

■

Optional. Used only when a trading partner has two or more outbound events of the same document, such as two purchase orders with different internal IDs.

■

Match the ID value in the document header record with the Internal Division ID of an outbound event.

■

Structure the EDI envelope by specifying the functional group sender ID.

Defining External Cross-References

External cross-references are required for an outbound application. An external crossreference must be added to the application to cross-reference the application data to the trading partner key. You can add or delete an external cross-reference on the Cross Ref. tab of the Application Properties window in Operations Center Client.

Opening an Application The Application List window, available through the Operations Center Client, displays all applications currently in the system. To open the Application List window 1 Click Applications.

76


5

APPLICATIONS

Creating an Inbound Application

The Applications List dialog opens.

2 Continue with the appropriate set of instructions: ■

“Creating an Inbound Application” on page 77

■

“Creating an Outbound Application” on page 84

■

“Maintaining Applications” on page 101

Creating an Inbound Application When you create an application you define the path of the application. This section is organized by the Application Properties tabs and procedures used to create an inbound application: Tab

See

General

“Defining the Inbound Application General Properties” on page 78

Contacts

“Defining the Inbound Application Contacts Properties” on page 79

Production File

“Defining the Inbound Application Production File” on page 81

Test File

“Defining the Inbound Application Test File” on page 82

Internal Cross Ref.

“Defining the Inbound Application Internal Cross Reference” on page 82

Trading Partner

“Viewing the Trading Partner Associated to the Inbound Application” on page 84

To create an inbound application 1 From the Application List window, right-click and select New.

The Provide information about the intended use of this application dialog opens.

2 Select Inbound. 3 Select a Transformation Type: ■

EDI to ASCII

■

EDI to EBCDIC

■

EDI to XML


77

APPLICATIONS


■

XML to ASCII

4 Click OK.

The Application Properties dialog opens to the General tab. Defining the Inbound Application General Properties

Use the Application Properties General tab to define the general application properties.

To define inbound application general properties 1 Type this information as it applies to your transformation type: Section

Description

Direction

The direction, Inbound, is already selected for the application and is based on your selection when defining the event.

Process Type

Specifies a particular action the translator performs following the creation of the application file.

Business Group

78

■

Batch—Translator writes the translated data to the production or test path name indicated on the Production and Test File tabs.

■

Queue—Translator places translated data in the Gateway mailbox identified by the value in the Key field. Gateway mailboxes will be covered later. The data is not written to the Production path. Accomplished only in production mode.

■

Database API—The translator writes the translated production data to a relational database table named EDI_STAGING_IN. Inbound only.

■

Event Driven—Only available if the Event Driven option was purchased. The translator writes the translated data to the path: $EDIH\STGIN\\\\

■

Script—After the translator has completed translating a file and writes it to the Production path, it executes the script or program named here. The script or program must be in the $EDIH/xlate/bin directory. Maximum seven characters.

Specific application business group.


5

APPLICATIONS


Section

Description

Name

Application name.

Subsystem

Subsystem name.

Release

Release name or number.

Application Type

Will already be selected based on your selection when defining the event. This value can be one of the following:

Delimited

■

ASCII (Flat File)

■

EBCDIC

■

Flat File

■

XML

Select if the application is delimited. By checking this box, the Field Separator and Field Delimiter are enabled.

Field Separator

Field separator for the delimited file.

Field Delimiter

Field delimiter for the delimited file

Defining the Inbound Application Contacts Properties

For more information about contacts, see“Contact Management” on page 37. Note that the capitalized “Contacts” in this guide refers to Contacts that are not EDI Representatives. Use the Application Properties, Contacts tab, to manage application Contacts. These are individuals who you may wish to ask questions or who you may wish to receive automatic notifications of delinquent FAs for the associated application. To create an application, you must assign a Contact. You can assign more than one. The Contacts tab links to the Contact Management window, Application Associations tab, where you will perform the following tasks: ■

To add a new application Contact, click Add New Contact. See “Adding a New Contact” on page 44.

■

To assign a Contact to an application, click Assign Contact. See “Assigning Contacts” on page 45.

To unassign a Contact for an application, you can use the Application Properties window, Contacts tab, as described below. Note: You can also unassign Contacts in the Contact Management window, Application Associations tab. See “Unassigning Contacts” on page 46.

To choose whether or not you want an application Contact to receive automatic email notifications of delinquent FAs for the application, See “Setting Contact Notification Preferences” on page 48. To access the Contacts tab 1 From the Applications Properties window, click the Contacts tab.


79

APPLICATIONS


The tab opens and displays Contacts assigned to the application. Use the appropriate procedure that follows.

To unassign an application Contact in Application Properties 1 From the Application Properties window, click the Contacts tab. 2 Select the Contact in the list to unassign from the application. 3 Click Unassign Contact. 4 The Contact is no longer assigned to the application.

80


5

APPLICATIONS


Defining the Inbound Application Production File To define inbound application production file properties 1 Select the Production File tab.

2 Type this information: Section

Description

Production Path/File

Unique pathname on your server where the target file is to be written. Maximum of 255 characters. You can enter a pathname for a: ■

Directory—New target file names are system generated. TL Services places the new file in the directory each time it executes. Required for inbound translations.

■

File—TL Services writes the data to the file and appends it to any data that exist when a directory and file are defined.

Directory

Directory name where the application file definitions are stored. For information only.

Filename

File name of the file definition for the application production and test files. For information only.


81

APPLICATIONS


Defining the Inbound Application Test File To define inbound application test file properties 1 Select the Test File tab.


Description

Test Path/File

Unique pathname on your server where the target file test data is to be written. Maximum of 255 characters. You can enter a pathname for a: ■

Directory—New target file names are system generated. TL Services places the new file in the directory each time it executes.

■

File—TL Services writes the data to the file and appends it to any data that exist when a directory and file are defined.

Defining the Inbound Application Internal Cross Reference

The lookup and replace list are used in conjunction with the ID cross command in the Workbench.

82


5

APPLICATIONS


To define inbound application internal cross-reference properties 1 Select the Internal Cross Ref tab.

2 Do one of the following: ■

Select an internal cross reference.

■

Add a new internal cross-reference. Click New and see “Adding an Inbound Internal Cross-Reference” on page 83.

Adding an Inbound Internal Cross-Reference To add an internal cross-reference to an inbound application 1 Click the Internal Cross Reference tab and select New.

The Application Internal Cross-Reference dialog opens.

2 Provide cross-reference information for these fields: Field

Description

Lookup Value

The value you want to convert the incoming value to. Maximum 30 characters.

Return Value

Incoming code you want to convert. For example, the vender ID or UPC code. Maximum 35 characters.

3 Click OK.


83

APPLICATIONS

Creating an Outbound Application

The new internal cross-reference displays in the list on the Internal Cross-Ref. tab. Viewing the Trading Partner Associated to the Inbound Application To view the trading partner associated to the inbound application 1 Select the Trading Partners tab.

The table appears with a list of the Trading Partners associated with the application. This information is read-only.

You can view the following information: ■

Document ID

■

Trading Partner

■

Business Unit

■

Key

Creating an Outbound Application When you create an application you define the source document that is opened and read at the beginning of the translation process. This section is organized by the Application Properties tabs and procedures used to create an outbound application:

84

Tab

See

General

“Defining the Outbound Application General Properties” on page 86

Contacts

“Defining the Outbound Application Contacts” on page 87

Production File

“Defining the Outbound Application Production File” on page 88

Test File

“Defining the Outbound Application Test File” on page 89

Outbound Layout

“Defining the Outbound Layout” on page 90


APPLICATIONS


Tab

See

Internal Cross Ref.

“Defining the Outbound Application Internal Cross Reference” on page 95

External Cross Ref.

“Defining the Outbound Application External Cross-Reference” on page 96

Trading Partner

“Viewing the Trading Partner Associated to the Inbound Application” on page 84

5

See also “Sending Multiple Documents to the Same Trading Partner” on page 98 To create an outbound application 1 From the Application List window, right-click and select New.

The Provide information about the intended use of this application dialog opens.

2 Select Outbound. 3 Select a Transformation Type: ■

App to App

■

ASCII to EDI

■

ASCII to XML

■

EBCDIC to EDI

■

XML to EDI

4 Click OK.

The Application Properties dialog opens to the General tab.


85

APPLICATIONS


Defining the Outbound Application General Properties

Use the Application Properties General tab to define the general application properties.

To define outbound application general properties 1 Type this information as it applies to your transformation type: Section

Description

Direction

The direction, Outbound, is already selected for the application and is based on your selection when defining the event.

Process Type

Specifies a particular action the Translator performs following the creation of the application file. Select Batch. The translator writes the translated data to the production or test path name indicated on the Production and Test File tabs. Note: If you select Batch, the Script field is not available.

Business Group

Specific application business group.

Name

Application name.

Subsystem

Subsystem name.

Release

Release name or number.

Application Type

Will already be selected based on your selection when defining the event. This value can be one of the following:

Delimited

86

■

ASCII Flat File

■

EBCDIC

■

Flat File

■

XML

Select if the application is delimited.


5

APPLICATIONS


Section

Description

Field Separator

Field separator for the delimited file. Note: Does not apply to XML type Applications.

Field Delimiter

Field delimiter for the delimited file. Note: Does not apply to XML type Applications.

Defining the Outbound Application Contacts

Use the Application Properties, Contacts tab, to manage application contacts. The Contacts tab links to the Contact Management window, where you will perform the following tasks: ■

Add a new application contact.

■

Assign an existing contact to an application.

You can unassign a contact for the application in the Contacts tab. To access the Contacts tab 1 From the Applications Properties window, click the Contacts tab.

The tab opens and displays contacts assigned to the application. Use the appropriate procedure that follows.

To add a new application contact 1 From the Application Properties window, click the Contacts tab. 2 Click Add New Contact.

The Contact Management window, Contact List tab, opens. See “Adding a New Contact” on page 44. After clicking OK or Apply, the contact is associated with the application. To assign an existing contact to an application 1 From the Application Properties window, click the Contacts tab.


87

APPLICATIONS


2 Click Assign Contact.

The Contact Management window, Application Associations tab, opens. The left panel displays the applications, with the selected application expanded to show its contact assignments. The right panel displays contacts. 3 To assign a contact, drag a contact name from the right panel into the left panel and onto

the name of an application. The contact name is assigned to the application and displays under the application name. To unassign an application contact 1 From the Application Properties window, click the Contacts tab. 2 Select the contact in the list to unassign from the application. 3 Click Unassign Contact.

The contact is no longer assigned to the application. Defining the Outbound Application Production File To define outbound application production file properties 1 Select the Production File tab.

88


5

APPLICATIONS


2 Type this information:r Section

Description

Production Path/File

Unique pathname on your server for the source documents which will be open and read. Maximum of 255 characters. You can enter a pathname for a: ■

Directory—When a directory is specified, the entire directory is read.

■

File—When a directory and file is specified, only that file is read.

Important: Outbound translations performed in production mode delete the source file contents (leaving a zero byte file) after reading it into the translation. Directory

Directory name where the application file definitions are stored. For information only.

Filename

File name of the file definition for the application production and test files. For information only.

Defining the Outbound Application Test File To define the outbound application test file properties 1 Select the Test File tab.


89

APPLICATIONS



Description

Test Path/File

Unique pathname on your server for the source documents which will be open and read. Maximum of 255 characters. You can enter a pathname for a: ■

Directory—When a directory is specified, the entire directory is read.

■

File—When a directory and file is specified, only that file is read.

Important: Outbound translations performed in production mode delete the source file contents (leaving a zero byte file) after reading it into the translation.

Defining the Outbound Layout

This tab displays for outbound applications only. Use the Outbound Layout tab to define the location of the Header record, the Trading Partner ID data, the Internal Division ID and the Document Type data within the source document. The outbound layout page varies based on these application types: ■

“ASCII or EBCDIC Flat File Outbound Layout” on page 90

■

“XML Outbound Layout” on page 94

ASCII or EBCDIC Flat File Outbound Layout

If you are creating an outbound ASCII or EBCDIC application, the Outbound Layout tab will be available:

90


5

APPLICATIONS


To define ASCII or EBCDIC Flat File Outbound Layout properties 1 Provide information for these fields: Field

Description

Layout for

Select Production/Recover or Test. Information displayed in the next fields differ based on the layout selected. Note: If no test path is entered in the Test tab, then Test File is not available to select.

Header ID ASCII and EBCDIC

Values that uniquely identify the header record for each document within the application path name. ■

Offset—Used for fixed field lengths files. Offset is one less than the position Number (range of 0 to 9999).

Example: The column 1 offset would be 0 and column 2 would be 1. For a delimited file format, the offset is the field number (usually 0). ■

Length—Field not used for delimited file formats. Length of the header constant field (1 to 9 bytes).

Example: If the header constant is ABC, the length is 3. The default is blank. ■

Constant—Header constant the Application sends in a record to specify the first record of a document. Enter up to eight alphanumeric characters. This constant must be the same for all documents within the Application. Translator uses the Offset and Length fields to locate and identify a header record.

■

Number—Field number in the record.

If the Delimited check box is selected on the Application Properties window, General tab, an entry in this field is required. For delimited file formats, define only the field number of the header constant within the Application record (starting at one). Field size is determined by the field separators.


91

APPLICATIONS


Field

Description

External Cross Reference

Links the Trading Partner ID data in the source document to the Trading Partner key. Offset, Length and data Type within the document header record where the trading partner identifier is located. This number must be cross-referenced to the Trading Partner Key field. ■

Offset—Number of bytes that Translator should skip in the header record before it finds the field specifying an Application Trading Partner code. Example: A customer or vendor number. This optional field has a range of 0 to 9999. If you enter the offset in this field, Translator takes the data at that offset location and attempts to find a match for this field on the External Cross-reference tab. The offset is not used for delimited files, only number.

Document Constant

■

Length—Length of the Application Trading Partner code, from 1 to 9999 bytes. The default is blank. This field is not used for the delimited file format.

■

Type—Select the data type from the dropdown. When Translator uses the offsets and lengths specified on an Application header record, Translator needs to know the type of data to test it appropriately. The default is Alphanumeric.

■

Number—If the Delimited check box is selected on the Application Properties window, General tab, an entry in this field is required. For delimited file formats, define only the field number of the external crossreference within the Application record (starting at one). Field size is determined by the field separators.

Optional. If you enter values in these fields, you must enter a Document Constant cross-reference with both a Document Constant and document name. ■

Offset—Number of bytes that Translator should skip in the header record before it finds the field specifying an Application Document Constant that defines the document being sent. This is important if the Application sends multiple document types in the same Application dataset/file. This field has a range of 0 to 9999.

Example: If the Document Constant begins at column 30, the offset is 29. The default is blank. The offset is not used for delimited files, only number. ■

Length—Length of the Document Constant, 1 to 9999.

Example: If the constant is ABC, the length is 3. The default is blank. This field is not used for delimited file format. ■

Number—If the Delimited check box is selected on the General tab of the Application Properties window, an entry in this field is required.

For delimited file formats, define only the field number of the Document Constant within the Application record (starting at one). Field size is determined by the field separators.

92


5

APPLICATIONS


Field

Description

Internal Cross Reference

Links the Internal Division ID data in the source document to the Internal Division ID used in the event and target document. Offset and Length within the document header record where the internal identifier is located. The internal identifier must be cross-referenced to an Internal Division ID on the Internal Cross Reference tab. Optional. Complete these fields only when a trading partner has two or more outbound events of the same document type (such as two purchase orders) having different internal IDs. ■

Offset—Number of bytes that Translator should skip in each record before it finds the field specified as the Application sender code, with a range of 0 to 9999.

Example: If the offset for column 1 is 0, and column 2 would be 1 byte. Use the Offset field only if one Application holds data from two different internal divisions that use more than one functional group sender ID. If you enter the offset in this field, Translator takes the data at that offset location and attempts to find a match for this field on the Internal Cross-reference tab. The default is blank. The offset is not used for delimited files, only number. ■

Length—Use the Length field only if the Offset field is used. The default is blank. This field is not used for delimited file format. Field size is determined by the field separators.

■

Number—If the Delimited check box is selected on the Application Properties window, General tab, an entry in this field is required.

For delimited file formats, define only the field number of the internal crossreference within the Application record (starting at one). Field size is determined by the field separators. Document Constant Cross References

At least one Document Constant Cross-reference must exist. You can add or delete a Document Constant by clicking New or Delete. ■

Document Constant—Document Constant sent by the Application in the header record that specifies the type of document being sent. The constant should represent one of the valid EDI document names. If an Application sends more than one document, you should specify multiple lines of constants.

This is an optional field; however, if values are present in the Offset and/or Length fields of the Document Constant area, this field becomes mandatory. ■


Document Name—Name of the outbound document associated with the unique document constant. This is a required field. Should match the document name of an event.

93

APPLICATIONS


XML Outbound Layout

You can enter an XML element tag name or XPATH expression to specify the XML element tag name. If you are creating an outbound XML to EDI application, the Outbound Layout tab will be available.

To define XML Outbound Layout properties 1 Provide information for these fields: Field

Description

Header ID

Value that uniquely identifies the header for each XML document within the application path name.

Document Constant

94

■

Attribute Name - Header ID is an XML attribute. The attribute tag name needs to be provided.

■

Element Name - Header ID is contained within an XML Element. The element tag name needs to be provided.

■

Element Tag - Header ID is the actual tag name for the XML element.

■

Constant - Header constant for the document.

Optional. If you enter values in these fields, you must enter a Document Constant cross-reference with both a Document Constant and document name. ■

Attribute Name - Document constant is an XML attribute. The attribute tag name needs to be provided.

■

Element Name -Document constant is contained within an XML Element or XPATH expression for the XML element tag name. The element tag name needs to be provided.

■

None - Not used in XML document.


5

APPLICATIONS


Field

Description

External Cross Reference

Location within the XML document where the trading partner identifier is located. The number must be cross-referenced to the Trading Partner Key field. Required.

Internal Cross Reference

■

Attribute Name—External cross reference is an XML attribute. The attribute tag name needs to be provided.

■

Element Name—External Cross Reference is contained within an XML Element or XPATH expression for the XML element tag name. The element tag name needs to be provided.

■

Type—Data type for external cross reference.

Internal Cross Reference—Location within the XML document where the internal identifier is located. The number must be cross-referenced to the Internal Division ID field. Optional. ■

Attribute Name—Internal cross reference is an XML attribute. The attribute tag name needs to be provided.

■

Element Name—Internal Cross Reference is contained within an XML Element or XPATH expression for the XML element tag name. The element tag name needs to be provided.

■

None—Not used in XML document.

Defining the Outbound Application Internal Cross Reference To define outbound application internal cross-reference properties 1 Select the Internal Cross Ref tab.

2 Continue with the next section, “Adding an Outbound Internal Cross-Reference” on

page 95. Adding an Outbound Internal Cross-Reference

Before setting up an internal cross-reference for an outbound event, the Internal Crossreference fields must be specified on the Application Properties Window - Outbound Layout tab. TrustedLink Enterprise Operations Center User Guide

95

APPLICATIONS


To add an internal cross-reference to an outbound application 1 From the Application Properties Internal Cross Ref tab and click New.

The Application Internal Cross Reference dialog opens.

2 Provide information for these fields. Field

Description

Application Division ID

Data in the source file that refers to your internal division ID. Maximum 30 characters.


Internal functional group identification code for the division in your company. Maximum 35 characters.

3 Click OK to save the internal cross-reference.

Defining the Outbound Application External Cross-Reference To define outbound application external cross-reference properties 1 From the Application Properties dialog, select the External Cross Ref tab.

2 Continue with the next section, “Adding an Outbound External Cross-Reference” on

page 97.

96


5

APPLICATIONS


Adding an Outbound External Cross-Reference To add an external cross-reference to an outbound application 1 From the Application Properties External Cross Ref tab and click New.

The Application External Cross Reference dialog opens.

2 Provide this information: Field

Description

Application Reference ID

Data that is in the source document used to reference the Trading Partner to be used in the event. This number appears in the header. Multiple reference IDs can point to one trading partner. Type the Application Reference ID the application uses to identify the trading partner. Maximum 30 numeric characters.

Type Name or Select from List

Key

Select a trading partner using one of three methods: ■

Select the name from the list.

■

Type the trading partner name in the Type Name or Select from List field.

■

Type the trading partner key in the Key field and click Search. Maximum 35 characters.

Trading partner key in the trading partner set up. This is the functional group sender ID (X12) or the UNB sender ID (EDIFACT).

Ledger Code

Optional value assigned by the application to the trading partner. Maximum three characters.

3 Click OK.

The new External Cross-Reference is added and appears in the list box on the External Cross-Reference tab. 4 Click OK to return to the Application Properties dialog.

Viewing the Outbound Trading Partners Associated to the Application To define outbound application trading partner properties 1 Select the Trading Partners tab.


97

APPLICATIONS


The table appears with a list of the Trading Partners associated with the application. This information is read-only.

Sending Multiple Documents to the Same Trading Partner

The section describes how to send multiple EDI documents to a single trading partner using unique Internal Division IDs, which are specified in GS02. This procedure therefore requires the GS segment. The example used in the procedure below involves three documents and requires the following three events: ■

Send an invoice to trading partner TP101. Document includes GS02=01.

■

Send a second invoice to trading partner TP101. Document includes GS02=02.

■

Send a purchase order to trading partner TP101. Document includes GS02=01.

Note: The multiple documents can be configured to use the same ISA. For example, HDRTP101MYCO01810IN12345 ... HDRTP101MYCO02810PO67890 ... HDRTP101MYCO01850PO67890 ...

See the note that follows Step 2 below for more about this part of the ISA.

98


5

APPLICATIONS


To send multiple documents to the same trading partner 1 In the Trading Partner Properties window, define the above three events for the trading

partner with Trading Partner Key TP101.

2 In the Application Properties window, Application Outbound Layout tab, define the

values in the source application document. The example requires three event setups, each associated with its own application definition. In the graphic below, the sections of the tab are associated with the information at the top of the ISA. For example:

Note:

HDRTP101MYCO01810IN12345

Header ID


External CrossReference

Internal CrossReference

Document Constant

99

APPLICATIONS


3 In the Application Properties window, External Cross-Ref. tab, cross-reference the value in

the source document that will point to the Trading Partner Key used in the trading partner setup.

100


5

APPLICATIONS

Maintaining Applications

4 In the Application Properties window, Internal Cross-Ref. tab, cross-reference the value in

the source document to the Internal Division ID value that will be placed in the GS02 element. This cross-reference determines the identifier used for the sender company.

The Internal Division ID also determines the ISA envelope definition to use in an outbound event. You can view the Internal Division ID relationships in the Trading Partner Properties window, Interchange Reference tab, as seen below.

Note:

The final outbound EDI document would look something like the following: ISA*00* *00* *ZZ*TP105 *ZZ*TP200 *040430*1225*U*00200*000000187*1*P*> GS*IN*01*TP101*20060101*0845*200*X*004030 ST*810*0001 … … SE*7*0001 GE*1*200 GS*IN*02*TP101*20060101*0845*201*X*004030 ST*810*0001 … … SE*5*0001 GE*1*201 GS*PO*01*TP101*20060101*0845*202*X*004030 ST*850*0001 … … SE*6*0001 GE*1*202 IEA*3*000000187

Maintaining Applications Use the following instructions to maintain applications: ■

“Copying an Application” on page 102

■

“Modifying an Application” on page 102

■

“Deleting an Application” on page 102


101

APPLICATIONS


■

“Deleting an Internal Cross-Reference” on page 103

■

“Deleting an External Cross-Reference” on page 103

Copying an Application

The Create from Current option lets you create a new application based an existing one. When you use this option you can use all of the existing Application properties, or overwrite existing properties to fit your needs. To create a new application from an existing one 1 Open the Application List window. 2 Right-click the application to copy from and select Create from Current.

The Application Properties dialog opens. 3 Select a tab and enter information as needed. 4 Click OK.

Modifying an Application

After you have created an application, you can change the information in the application, except for these fields: ■

Direction

■

Business Group

■

Name

■

Subsystem

■

Release

To modify an application 1 Click Applications.

The Application List dialog opens. 2 Double-click an application from the list.

The Application Properties window displays information about the application you selected. 3 Select a tab and enter information as needed. 4 Click OK.

Deleting an Application To delete an application 1 Open the Application List window. 2 Right-click on the application you want to delete and select Delete. A confirmation

message appears. 3 Click OK. Important: If the application is associated with one or more events, the delete will fail and an error message displays: “Associated event(s) exist, unable to delete.” The associated event(s) must be modified to use a different application before this application can be deleted.

102


5

APPLICATIONS


Deleting an Internal Cross-Reference To delete an internal cross-reference 1 Click Applications.

The Application List dialog opens. 2 Double-click the inbound application you want.

The Application Properties dialog opens to the General tab. 3 Select the Internal Cross Ref tab. 4 Select the internal cross-reference you want to delete and click Delete.

The internal cross-reference is deleted from the application. Deleting an External Cross-Reference To delete an external cross-reference 1 Click Applications.

The Application List dialog opens. 2 Double-click the outbound Application you want to delete an external cross reference

from. The Application Properties dialog opens displaying the General tab. 3 Select the External Cross Ref tab.

4 Select the external cross-reference you want to delete and click Delete.

The external cross-reference is deleted.


103

APPLICATIONS


104


Event Wizard

T

6

his chapter describes how to use the Event Wizard to create an inbound or outbound event.

Topics include: ■

“Creating an Inbound Event Using the Event Wizard” on page 105

■

“Creating an Outbound Event Using the Event Wizard” on page 113

■

“Modifying an Event” on page 120

■

“Copying Events” on page 125

■

“Deleting Events” on page 126

Creating an Inbound Event Using the Event Wizard Use the Event Wizard to create inbound event. Before you can create an event, you must have previously defined: ■

A trading partner

■

An application

■

An interchange for outbound EDI events and all XML events

■

A communication provider/mailbox (only outbound events)

An inbound event can use the same EDI representative, trading partner, and application as an outbound event. Note: You do have the option to define or modify all components when creating the event.

To create an event using the Event Wizard 1 Click Event Wizard.

105

EVENT WIZARD

Creating an Inbound Event Using the Event Wizard

The Provide information about the Event dialog opens.


Description

Event Name

A unique Name for the event. Required. The Event name is assumed by TrustedLink Enterprise to be the map name. However, because the same map can be used in more than one event setup in the Operations Center Client you need to enter the Map name in the Event Alias field. If you enter any value in the Event Alias name field, TrustedLink Enterprise assumes that this is the map name. If a map by this name is not found, an error results.

Event Alias

Alternative name for the event when using one map for more than one event. Optional. See “Event Name” on page 106 for details.

Direction

Select Inbound.

Transformation Type

For Inbound, these options are available: ■

EDI to EBCDIC

■

EDI to ASCII

■

EDI to XML

■

XML to ASCII

3 Click Start Wizard.

106


6

EVENT WIZARD


The Event Wizard - Trading Partner dialog opens.


Select the trading partner from the Provider Name list and click Next. Continue with step 5.

■

Click New to add a trading partner. See “Creating a New Trading Partner” on page 54 for instructions. After creating the trading partner, select the trading partner and click Next.

The Event Wizard-Communications Provider dialog opens.

5 Perform the appropriate action:

If you are creating an inbound event, choose any existing communications provider. ■

Select the communications provider from the Provider List and click Next.


107

EVENT WIZARD


■

Click New to add a communications provider and see the TrustedLink Enterprise Gateway Communications User Guide for instruction to create a communications provider.

After creating the communications provider, select the provider and click Next. The Event Wizard - Application dialog opens.


Select an application and click Next to advance to the Event Wizard - Event Details dialog.

■

Click New to add an application. See “Creating an Inbound Application” on page 77.

After creating the application, select the application and click Next. The Event Wizard - Document Details dialog opens. The event details dialog vary based on the document type you selected. 7 Follow the appropriate set of instructions for defining the properties, then continue with

step 9: ■

“EDI Document Details—Inbound” on page 109

■

“XML Document Details—Inbound” on page 112

8 After defining the EDI or XML details, click Next.

108


6

EVENT WIZARD


The Event Wizard-Billing Information dialog opens.

Note:

Billing information is not required to complete your event.

9 Enter the billing information, if required, and click Finish.

EDI Document Details—Inbound

For inbound EDI documents, enter the detail information for these fields (red fields in the graphic are required):


109

EVENT WIZARD


Enter the following information, then continue with step 8 on page 108. Field

Description

Event Name

Name of the event. Required. This field points to the mapping tables used by the EDI translators to translate the event. Maximum eight characters. Can be overwritten by the Event Alias field.

Envelope Name

Applies to Outbound events only.

Event Alias

Enter the map name. Use when the set of translation tables are used for more than one trading partner. This field overrides the Event Name.

Notify Level

EDI representative is notified when an error has this severity level. TL Services lists the error in the Error Log. Select one of these options:

ID

■

Only Abnormal Termination

■

Reject and Abnormal Termination

■

All Errors and Warnings

EDI Transaction Set ID (document ID) that identifies the document used for the event. Element ID ANSI ST01. 850 (X12 purchase order) or UNH02:01 (EDIFACT).

Standard

Type or select the Standard to be used when this document is translated. The available list of Standards are based on your installation and can include:

Committee

■

ANSI

■

CTX

■

EDIFACT

■

NACHA

■

PROP

■

TDCC

■

TRADA (TRADACOM)

Committee code that corresponds to the EDI standard. Required for ANSI; optional for EDIFACT. X = EDI (Element ID GS07 in ANSI envelopes)

Version

Version number of the EDI standard. Element ID ANSI GS08. Note: You can type the version if it is not available for selection from the dropdown.

Status

Available options vary on the type of event you are creating and the direction. Select from the dropdown:

110

■

Test—Translator translates the document as a test document.

■

Production— Translator translates the document as a production document.

■

Hold— temporarily places the Event on hold and prevents the documents from being translated.

■

Release—disengages the Hold status and translates the documents as test documents.

■

Inactive— indicates the Event is no longer being used and documents will not be translated.


6

EVENT WIZARD


Field

Description

Accept Level

When an error occurs during translation, this portion of the EDI file is placed in recovery:

Name

■

Interchange: The entire interchange is rejected.

■

Functional Group: Functional group is rejected.

■

Document: Transaction set containing the error is rejected.

Name of the document that corresponds to the ID.


Value used to identify your receiver ID. Maximum 35 characters.

FG Type

Code that identifies the document’s functional group type. Element ID ANSI GS01.

Write To

Applies to outbound only.

Functional Ack

If you expect a Functional Acknowledgement for this event, select the following as needed: ■

Expected—Indicates an inbound functional acknowledgment is expected. Enables the Process Real Time check box for real-time FAs, and the Count field in the Reconciliation section for batch FAs. See below.

■

Process Real Time—Requires Expected to be selected. Select this box for a real-time FA. Enables the Duration field in the Reconciliation section, and the Duration and Calendar sections. Disables the Count field. See below.

Note: Real-time FA is enabled only if your serial number supports it. Count

If the expected FA will be processed by batch, in this field type the number of times the FA reconciler will run before TLE considers the transmission FAdelinquent if the FA has not arrived.

Duration (field)

If the expected FA will be reconciled in real-time after being translated, in this field type the number of minutes, hours, or days that can pass before TLE considers the transmission FA-delinquent if the FA has not arrived. Requires making selections in the Duration and Calendar sections.

Duration (options)

Calendar

Additional Options


If you typed a value in the Duration field, select what that number represents: ■

Days (default)

■

Hours

■

Minutes

If you typed a value in the Duration field, select which calendar to use: ■

Business (default)—Uses only work days.

■

Standard—Uses all days.

Click to use data banking and/or specify an EDI Representative for this event. When the Additional Document Properties dialog opens, do either or both of the following, then click OK: ■

In the Data Banking tab, select the Enable Data Banking check box to use data banking for this event.

■

In the EDI Representative tab, select the Associate an EDI Representative... check box, then choose a contact from the dropdown.

111

EVENT WIZARD


XML Document Details—Inbound

For inbound XML events, provide information for these fields (red fields in the graphic are required):

Enter the following information, then continue with step 8 on page 108. Field

Description

Event Name


Event Alias


Notify Level


112

■


■


■


Document Name

User-defined name describing document type. Optional for inbound events. Required for outbound events

Document Version

User-defined name describing document version. Inbound only. Optional.


Identifies your receiver ID. Maximum 35 characters. This is used to link to the appropriate XML interchange defined for this event

XML Tagname/XPath

Required if you supplied a document name and version.


6

EVENT WIZARD

Creating an Outbound Event Using the Event Wizard

Field

Description

Make Priority Key Unique

Used in conjunction with the Tracking Priority feature within Mapper. The tracking field with the highest priority will be checked for duplicates, and a reject will occur if a duplicate is detected.

Status

These options or fields are available:

Functional Acknowledgement

■

Test or Production

■

Value

■

XML Tagname/XPath

These options and fields are available: ■

Expected—Inbound Events only. There are no predefined maps for Functional Acknowledgements of XML documents. You will need to create a map and an event.

■

FA Event— Provide event name. Activated when the FA is selected.

Creating an Outbound Event Using the Event Wizard Use the Event Wizard to create an outbound event. Before you can create an event, you must have previously defined: ■

An EDI representative

■

A trading partner

■

An application

■

An interchange for outbound EDI events and all XML events

■

A communication provider/mailbox (only outbound events)

An outbound event can use the same EDI representative, trading partner, and application as an inbound event. Note: You do have the option to define or modify all components when creating the event.

To create an event using the Event Wizard 1 Click Event Wizard.

The Provide information about the Event dialog opens.


113

EVENT WIZARD



Description

Event Name


Event Alias


Direction

Select Outbound.

Transformation Type

For Outbound events, these options are available: ■

App to App

■

ASCII to EDI

■

ASCII to XML

■

EBCDIC to EDI

■

XML to EDI

3 Click Start Wizard.

The Event Wizard - Trading Partner dialog opens.


114

■

Select the trading partner from the Provider Name list and click Next. Continue with step 5.

■

Click New to add a trading partner. See “Creating a New Trading Partner” on page 54 for instructions. After creating the trading partner, select the trading partner and click next.


6

EVENT WIZARD


The Event Wizard-Communications Provider dialog opens.


You must choose an XML mailbox for outbound XML documents and an EDI mailbox for all other types. An XML mailbox allows XML documents to be sent to Inovisworks as binary documents

Note:

■

Select the communications provider from the Provider List and click Next.

■

Click New to add a communications provider and see the TrustedLink Enterprise Gateway Communications User Guide for instructions to create a communications provider.

After creating the communications provider, select the provider and click Next. The Event Wizard - Application dialog opens.



115

EVENT WIZARD


■

Select an application and click Next to advance to the Event Wizard - Event Details dialog.

■

Click New to add an application. See “Creating an Inbound Application” on page 77.

After creating the application, select the application and click Next. The Event Wizard - Document Details dialog opens. 7 Follow the appropriate set of instructions for defining the properties, then continue with

step 9. The Event Wizard - Document Details dialog opens. The event details dialog vary based on the document type you selected. 8 To define the details, use the appropriate set of instructions: ■

“EDI Document Details—Outbound” on page 117

■

“XML Document Details—Outbound” on page 120

9 After defining the EDI or XML details, click Next.

The Event Wizard-Billing Information dialog opens.

Note:

Billing information is not required to complete your event.

10 Enter the billing information, if required, and do one of the following: ■

Click Next if the event is an outbound event or an inbound XML event, the Event Wizard - Interchange dialog opens.

■

Click Finish.


Select an interchange from the list and go to step 12.

■

Click New and go to “Adding an Interchange Reference” on page 62, then continue with step 12.

12 Click Finish.

116


6

EVENT WIZARD


EDI Document Details—Outbound

For EDI documents, enter the detail information for these fields (red fields in the graphic are required):

Field

Description

Event Name


Envelope Name

Envelope tables used for translation. Outbound events only. See “Outbound EDI Envelopes” on page 119.

Event Alias


Notify Level


ID

■


■


■


EDI Transaction Set ID (document ID) that identifies the document used for the event. Element ID ANSI ST01. 850 (X12 purchase order)


117

EVENT WIZARD


Field

Description

Standard

Standard used when this document is translated. Select from the dropdown. This list can include (varies depending on your installation):

Committee

■

ANSI

■

CTX

■

EDIFACT

■

NACHA

■

PROP

■

TDCC

■

TRADA (TRADACOM)

Committee code that corresponds to the EDI standard. Required for ANSI; optional for EDIFACT. X = EDI (Element ID GS07 in ANSI envelopes)

Version

Version number of the EDI standard. Element ID ANSI GS08. Note: You can type the version if it is not available for selection from the dropdown.

Status

Accept Level

Select from the dropdown: ■

Test

■

Start-Up

■

Production

When an error occurs during translation, this portion of the EDI file is placed in recovery: ■


■


■


Name

Name of the document that corresponds to the ID. Identifies the division that uses the application defined by this document.



FG Type


Write To

Select one of these options:

Functional Ack

■

Mailbox—select if you use the auto email feature.

■

Database—select if you write to a the staging database.



■


Note: Real-time FA is enabled only if your serial number supports it. Count

118



6

EVENT WIZARD


Field

Description

Duration (field)


Duration (options)

If you typed a value in the Duration field, select what that number represents:

Calendar

■

Days (default)

■

Hours

■

Minutes

If you typed a value in the Duration field, select which calendar to use:

Additional Options

■


■


Click to use data banking and/or specify an EDI Representative for this event. When the Additional Document Properties dialog opens, do either or both of the following, then click OK: ■


■


Outbound EDI Envelopes

The table lists the EDI envelopes available for outbound EDI events: Envelope

Direction

Standard

Comments

ANSIOUT1

O

X12

Up through 3070

ANSIOUT2

O

X12

4010 only

ANSIOUT3

O

X12

4020+

ANSIUCS0

O

UCS

Up through 3070

ANSIUCS2

O

UCS

4010

EDIFACTO

O

EDIFACT

No routing address logic, ISO 9375 v2

EDIFOV4

O

EDIFACT

Same as EDIFACTO, but supports v4

EDIFOUTD

O

EDIFACT

Supports reverse and forward routing address, and TP document interchange numbering

EDIFODV4

O

EDIFACT

Same as EDIFOUTD, but supports v4

EDIFOUTT

O

EDIFACT

Supports reverse and forward routing address, and TP interchange numbering

EDIFOTV4

O

EDIFACT

Same as EDIFOUTT, but supports v4

EDIFUNG

O

EDIFACT

Support for UNG/UNE

EDIFUNG4

O

EDIFACT

Same as EDIFUNG, but supports v4


119

EVENT WIZARD

Modifying an Event

XML Document Details—Outbound

For outbound XML events, provide the information for these fields (red fields in the graphic are required):

Field

Event Name

Description

Name of the event. Required. This field points to a set of translation tables used to translate the event. Each event you create must have a unique name. Maximum eight characters. Can be overwritten by the Alias field.

Event Alias

Used when the set of translation tables are used for more than one trading partner. This field overrides the event name.

Notify Level


Document Name

■


■


■


This value must match the Document Constant Cross Reference in the Outbound Layout tab of the Application.


Used to link to the appropriate XML interchange defined for this event. Maximum 35 characters.

Status

Select one of these options from the dropdown:

Functional Acknowledgement

■

Test

■

Production

Applies to inbound only.

Modifying an Event When you modify an EDI event, you can change all information except:

120


6

EVENT WIZARD

Modifying an Event

■

Document ID

■

Committee

■

Trading Partner Key

■


■

Version Number

To modify an event 1 Open the Trading Partners window. See “Opening the Trading Partners/Events Window”

on page 53 for details. 2 Select an event and click Properties.

The Event Properties dialog opens to the General tab. The window that opens depends on the document type: 3 Provide information for either: ■

“Event Properties—EDI” on page 121

■

“Event Properties—XML” on page 123

Event Properties—EDI

Field

Description

Event Alias

Use when the set of translation tables are used for more than one trading partner. This field overrides the Event Name.

Envelope Name

Envelope tables used for translation. For outbound events only.

Committee

Committee code that corresponds to the EDI standard. Required for ANSI; optional for EDIFACT. Element ID ANSI GS07.

Accept Level

When an error occurs during translation, this portion of the EDI file is placed in recovery:


■


■


■


121

EVENT WIZARD

Modifying an Event

Field

Status

Description

Select from the dropdown: ■

Test

■

Start-Up

■

Production

■

Hold, Release

■

Inactive

Notify Level

EDI representative is notified when an error has this severity level. TL Services lists the error in the Error Log.



FG Type


Name

Name of the document that corresponds to the ID. Identifies the division that uses the application defined by this document.

Write To

Select one of these options:

Functional Ack

■

Mailbox —select if you use the auto email feature.

■

Database—select if you write to a the staging database.



■


Note: Real-time FA is available only if your serial number supports it. Count


Duration (field)


Duration (options)

122

If you typed a value in the Duration field, select what that number represents: ■

Days (default)

■

Hours

■

Minutes


6

EVENT WIZARD

Modifying an Event

Field

Description

Calendar

If you typed a value in the Duration field, select which calendar to use:

Additional Options

■


■


Click to view or modify billing information, use data banking, and/or specify an EDI Representative for this event. When the Additional Document Properties dialog opens, do any of the following, then click OK: ■

Modify the Billing tab as needed.

■


■


Event Properties—XML

1 Enter the following information: Field

Description

Event Alias

Overrides the event name and uses another set of translation tables when translating the event. Used for translating two or more of the same type documents, with the same document mapping. Requires creating and maintaining one set of tables. Optional.

Name

User-defined name describing document type.

Document Version

User-defined name describing document version.


Used to link to the appropriate XML interchange defined for this event. Maximum 35 characters.

XML Tag/XPath

Required if you supplied a document name and version.

Notify Level

Level of error severity at which you want the EDI Representative notified.

Status

These options or fields are available:


■

Test, Production, Hold, Release, Inactive and Startup

■

Value

■

Date

■

XML Tag/XPath

123

EVENT WIZARD

Modifying an Event

Field

Description

Write To

Choose one of these options:

Functional Ack(nowledgement)

Additional Options

■

Mailbox

■

Database

Applies to inbound only. These options and fields are available: ■

Expected—For inbound events, indicates whether to send an outbound functional acknowledgment. For outbound events, indicates whether you expect to receive an inbound functional acknowledgment from the trading partner.

■

FA Event— Provide event name. Activated when FA selected.

Click to view or modify billing information, use data banking, and/or specify an EDI Representative for this event. When the Additional Document Properties dialog opens, do any of the following, then click OK: ■

Modify the Billing tab as needed.

■


■


2 Click the Communications tab.

3 Select a new communications provider for this event, if needed.

124


6

EVENT WIZARD

Copying Events

4 Click the Application tab.

5 Select a new application for this event, if needed. 6 Click OK.

All information up to the last Apply has been saved. The event displays in the Events list with the updated information.

Copying Events You can create a new event by copying information from an existing one. Use this feature to copy an event exactly as it exists, or when an existing event closely resembles the requirements of a new event. Note: Copying an event does not copy contacts from the original event to the new event.

To copy an event 1 Click Trading Partners/Events.

The Trading Partners/Events dialog opens. See “Opening the Trading Partners/Events Window” on page 53 for details. 2 Select the trading partner associated with the event you want to copy.


125

EVENT WIZARD

Deleting Events

The events associated with the trading partner appear in the events list.

3 Click the event that you want to copy, then click Copy To.

The Copy Event To dialog opens.

4 Select the trading partner you want to copy the event to or type the trading partner key

and click Search. 5 Type a new name for the event and click OK.

The Trading Partners/Event dialog opens. 6 Select the trading partner to view the changes. 7 Click Close.

Deleting Events To delete an Event 1 Click Trading Partners/Events.

The Trading Partners/Events dialog opens. 2 Select the trading partner associated with the event you want to delete. 3 Select the event from the list.

126


EVENT WIZARD

Deleting Events

6

4 Click Delete. A confirmation message displays. 5 Click Yes to delete the selected event.

The event is deleted from the list


127

EVENT WIZARD

Deleting Events

128


7

Data Export

T

his chapter provides information about exporting data. The chapter is organized as follows:

■

“Overview” on page 129

■

“Exporting Data” on page 130

Overview You can export data from one database to another database. This means you can move events and maps from a test environment to a production environment. You can export these components to another database: Component

Use this option.

Trading partner

If you want to copy all data (except maps) associated with the trading partner.

Event

If you need one event for a trading partner instead of all the events associated with the trading partner.

Communications mailbox

To copy mailbox data associated with an event.

Contacts

To copy contact data associated with an event.

Application

To copy application data associated with an event.

Interchange

To copy Interchange data associated with an event.

Map

To copy map data associated with an event.

Port

To copy port data associated with an event.

When you export data, any required foreign key values are automatically moved.

129

DATA EXPORT

Exporting Data

Exporting Data To export the data to another database To Export this data...

Go to...

Trading Partners and Events

“Opening the Trading Partners/Events Window” on page 130

Communications Mailbox

“Opening the Communications Mailbox Window” on page 131

Contact

“Opening the Contact Management Window” on page 131

Application

“Opening the Applications Window” on page 132

Maps

“Exporting Map Data” on page 134

Interchange

See the TrustedLink Enterprise Gateway Communications User Guide for instructions to define the Interchange Reference Properties.

Opening the Trading Partners/Events Window To open the Trading Partners window 1 Click Trading Partners/Event or select View > Trading Partners/Events.


2 In the Trading Partners box, select the trading partner you want to export. 3 Perform the appropriate action: ■

Select Trading Partner > Copy to Database. The Select Data Source dialog opens. Continue with step 4.

■

From the Trading Partner / Events window in the Events box, select a corresponding Event and click Copy to Database. The Copy To Event dialog opens.

The Select Data Source dialog opens displaying the File Data Source tab. 4 Select the applicable data source. For instructions, see “Selecting a Data Source for

Applications Setup” on page 133.

130


DATA EXPORT

Exporting Data

7

Opening the Communications Mailbox Window To open the Communications Mailbox window 1 Click Communications, or select View > Communications.

The Communications dialog opens.

2 Click the mailbox to copy. 3 Select Communications > Copy to Database.

The Select Data Source dialog opens displaying the File Data Source tab. 4 Go to “Selecting a Data Source for Applications Setup” on page 133.

Opening the Contact Management Window To copy contact data associated to another database 1 Click Contacts, or select View > Contacts.


131

DATA EXPORT

Exporting Data

The Contact Management window opens.

2 Select the contact whose information you want to copy. 3 Click Contacts > Copy to Database.


Opening the Applications Window To copy application data associated with a particular event to another database 1 Click Applications, or select View > Applications.

The Application List dialog opens.

2 Click the application you want to copy. 3 Select Applications > Copy to Database.


132


7

DATA EXPORT

Exporting Data

Selecting a Data Source for Applications Setup

Choose your target TrustedLink Enterprise installation to copy the data to. This step requires an ODBC setup for the target TrustedLink Enterprise installation. To select a data source 1 From the Select Data Source window, select the data source.

2 Click the Machine Data Source tab.

3 Select a data source name and click OK.

The Logon dialog opens.

4 Type your user name and password. 5 Click OK.

The Copy To Database window displays a record of the copy you have just completed. If the file you copied already exists on the destination database, the record indicates the file is already in the destination database.


133

DATA EXPORT

Exporting Data

Important: You cannot copy event data between database instances that use different versions of TrustedLink Enterprise. With TrustedLink Enterprise 6.1, you can only copy from and to TrustedLink Enterprise 6.1 databases. 6 Click OK.

Opening the Interchange List Window To view or copy an interchange list window 1 Click Interchanges, or select View > Interchanges.

The Interchange List window opens.

2 Click the Interchange you want to copy. 3 Select Interchange > Copy to Database.


Exporting Map Data To copy a map to another database 1 Click Trading Partners/Events, or select View > Trading Partners/Events.


2 Select the event that has the map you want to copy. 3 Select the event you want to copy. 4 Select Event > Copy Map.

134


7

DATA EXPORT

Exporting Data

The Copy Map dialog opens.

5 Provide this information:. From Server

To Server

Server Name: Hostname 1

Server Name: Hostname 2

TL Services Port Number: set in TL Configuration Tool

TL Services Port Number: set in TL Configuration Tool.

EDI Home Directory: /edi/tlehome1

EDI Home Directory: /edi/tlehome2

6 Click OK.

A box opens indicating your copy was successfully completed. Important: If the map already exists in the destination database, you will be asked

whether you want to overwrite the existing map. 7 Perform the appropriate action: Click

Description

Yes

Copies all map files. This option overwrites any files that exist on the target system.

No

No map files are copied.

8 Click OK.


135

DATA EXPORT

Exporting Data

136


Scheduling Tasks Overview

W

8

hen you added a mailbox, you indicated if it should use an event or batch schedule to process solicited transactions.

When you send data to...

This happens...

An event-scheduled mailbox

Gateway sends the data to the trading partner as soon as a port is available.

A batch-scheduled mailbox

Data stays in the mailbox until either: ■

Batch scheduler sends a request to Gateway to schedule mailbox files.

■

You submit a manual request to Gateway.

■

A trading partner dials in to receive the data.

Topics include: ■

“Event-Scheduled Transfers” on page 137

■

“Batch-Scheduled Transfers” on page 138

■

“Manual Mailbox Commands” on page 138

Event-Scheduled Transfers For an event-scheduled transfer (always a solicited transaction), the EDI or XML file is scheduled immediately for Gateway processing. Other Gateway actions may push back the immediate transfer. When you set up Gateway for event-scheduled transfers, you must first add the mailboxes for these transfers as event-scheduled. You may also need to set up other EDI software components to handle the event-scheduled exchanges. Event-Scheduled Transfer Process

In an event-scheduled transfer, Gateway requests a full exchange—a send and receive. When it receives data, Gateway might send a request to TL Services to activate Translator, telling it to pull data from your trading partner’s mailbox and translate it into your business software application format. A translation request is an option within the API script for asynchronous, bisynchronous, and FTP protocols. An OnRamp mailbox does not require an API script to process events. Event-Scheduled Transfer Process Flow

After all system components are set up to handle solicited, event-scheduled transfers, the transfers are made automatically:

137

S C H E D U L I N G TA S K S O V E R V I E W

Batch-Scheduled Transfers

1 Translator places translated data in an event-scheduled mailbox to be sent to a trading

partner, and sends a request to Gateway to schedule the file in the mailbox to be sent out. 2 Gateway checks the trading partner’s communications profile for protocol and mailbox

information, then transfers the data to your trading partner or Value-Added Network (VAN) over a phone line or network. 3 After Gateway transfers the files, it sends a request to your trading partner’s system or

VAN to receive any data waiting for you. 4 The other party’s system checks for data based on the user ID and password that Gateway

submits, and transfers any files waiting for you back to that trading partner’s mailbox on your Gateway.

Batch-Scheduled Transfers For a batch-scheduled transfer, the EDI file is queued for the next scheduled Gateway transaction. Other Gateway actions may postpone the immediate transfer. When you set up the Gateway for batch-scheduled transfers, you add the mailboxes for these transfers as batch-scheduled. You may also need to set up other EDI software components to handle the batch-scheduled exchanges. Batch-Scheduled Transfer Process

You can use Operations Center to schedule batch processing by using one of these options: ■

For Windows—cgw command in the Schedule Wizard

■

For UNIX—cron job, which you can set up via communications Mailbox Schedules and edi-batch unsolicited.

You can also set up a mailbox for batch scheduling and then not schedule it. You must then either run the cgw command manually or allow your trading partner to pick up the files. Batch-Scheduled Transfer Process Flow

The stages of batch-scheduled transfers are as follows: 1 After you run the cgw or cron command, either manually or as a scheduled event,

Gateway checks the trading partner’s communications profile for protocol and mailbox information. 2 Gateway transfers the data to your trading partner or VAN over a phone line or network. 3 After Gateway transfers the files, it sends a request to your trading partner’s system or

VAN to receive any data waiting for you. 4 The other party’s system checks for data based on the user ID and password that Gateway

submits, and transfers any files waiting for you back to that trading partner’s mailbox on your the Gateway.

Manual Mailbox Commands You can manually queue and transfer files in a mailbox. Queuing a File from Command Manager

When you submit a manual command to queue a file in a mailbox, the file remains in the mailbox until either Gateway or Translator, depending on the direction of the file, receives a

138


8


Manual Mailbox Commands

command to process the data. You can queue a mailbox file from the command line or by using the Operations Center Command Manager. You can use the Browser window in Command Manager to send a file to a mailbox. To queue a file 1 Click Command Manager and select Browser. Select the file you want to queue. 2 Right-click and select Gateway then Queue.

The Mailbox Queue Options dialog opens.

3 Provide information for these fields: Field

Description

Direction

Outbound indicates that you want to place the selected file in a mailbox for Gateway to send. Inbound indicates you are placing a file in a mailbox for the Inbound Translator to process.

QKey (optional)

Select the QKey of the mailbox from the dropdown. You can click Browse to locate the QKey.

Contains Binary Segment

Use this option when a file must be transferred as binary rather than EDI. Transmits the document through Inovisworks

Filename

Path to the selected file displays in this field. If this is not the correct path or you wish to queue a different file, type the path to the correct file.

X.400 Attachment

Not currently supported.

4 Click OK.

Transferring a File Manually

This section provides information about submitting a transfer command to transfer batchscheduled files before the scheduled time. You can use the Browser window in the Operations Center Client Command Manager to manually transfer a file. To manually transfer a file using the Command Manager 1 Select the file to be transferred in the Browser window. 2 Right-click and select Manual Transfer.


139


Manual Mailbox Commands

The Manual Transfer Option dialog opens.

3 Provide information in these fields: Field

Direction

QKey

Required. Select QKey from the dropdown.

Mode

Required. Click the dropdown to select the type of manual transfer desired: ■

Send

■

Receive

■

Exchange

4 Click OK.

140


UNIX Task Schedule

T

9

his chapter explains the following topics:

■

“Setting Up the Schedule Type on the Database” on page 141

■

“Batch Scheduling on the Server” on page 141

■

“Setting Up the Server—UNIX” on page 142

Setting Up the Schedule Type on the Database When you configure the database with the Operations Center Client for Batch scheduling, you use the General tab and the Activity Schedule tab on the Communications Mailbox window. The Schedule Type field can be either Event or Batch. ■

Event—TrustedLink software automatically processes the files the outbound translator sends to that mailbox with the cgw command.

■

Batch—TrustedLink software processes the files the outbound translator sends to that mailbox according to a schedule. You can have an unscheduled, or scheduled batch mailbox. ■

Unscheduled Batch Mailbox—When you set up a mailbox via the Communications Mailbox window of the Operations Center Client with a Batch Schedule Type, you can either schedule the mailbox on the Activity Schedule tab or not schedule the mailbox. If you choose Batch but you do not schedule the files in the mailbox to be sent, then you can either send the files manually (cgw -q qkey -m exch) or allow your trading partner to retrieve them.

■

Scheduled Batch Mailbox—Batch scheduling is useful for performing data exchanges that occur on a regular basis; for example, at a specific time each day or on a particular day of each month.

Batch Scheduling on the Server Batch scheduling on the UNIX server requires three things: ■

The cron daemon is running

■

You have permission to use crontab to set up and save a cron file

141

U N I X TA S K S C H E D U L E

Setting Up the Server—UNIX

■

Before you run edi_batch to add the information specified on the database via the Operations Center Client, you can manually configure your $EDIH/etc/edi_cron.base file to run TrustedLink and other commands.

Batch Processing

When you run the edi_batch program, this processing occurs: ■

The edi_batch program pulls information from the database for the entries you specified, via the Activity Schedule tab on the Communication window in Operations Center Client, to configure the $EDIH/temp/edi_cron.base file.

■

After it configures this file, edi_batch calls the UNIX crontab program to save that file to the appropriate directory.

■

The cron daemon then processes your cron file and runs the cgw commands you designated according to schedule.

Setting Up the Server—UNIX Before you attempt to set up the Gateway Batch Scheduler, verify:

142

■

You have a Gateway install.

■

The cron setup on your system.

■

The $EDIH/etc/edi_cron.base file is configured to meet your specifications.

■

The edi_cron.base file with $EDIH/bin/edi_batch is loaded and configured

■

Your general setup.


Windows Task Scheduling

T

10

he Operations Center Client offers a Scheduler program and the Schedule Wizard, which let you configure the TrustedLink database.

With the Operations Center Client, you can schedule entries using the Schedule Wizard. You can create or delete entries with schedules, view the schedule list, or temporarily disable the scheduler. Note: Scheduler features are available only if you are running the TrustedLink server software on a Windows host.

Topics include: ■

“TrustedLink Scheduler” on page 143

■

“Gateway Scheduling Process” on page 144

■

“Operations Center Task Scheduling” on page 145

■

“Schedule List” on page 146

■

“Schedule Wizard” on page 149

TrustedLink Scheduler The Scheduler has three main components: ■

Schedule Wizard and Schedules programs in Operations Center

■

TrustedLink database

■

Scheduler Service on the server

Both the Schedule Wizard and the Schedules programs allow you to configure the TrustedLink database. The Scheduler Service on the server polls the TrustedLink database every minute, scanning the entries and executing those schedules ready to run. The Scheduler Service is installed with the Translator and has no user interface on the server side. Scheduler Process

The stages of the Scheduler between the server and the client workstation are as follows: 1 The schedule you submit in the Schedule Wizard is entered into the TrustedLink

database. 2 The Scheduler Service scans the database for application entries that are ready to run. 3 When it finds an applicable entry, the Scheduler Service executes it.

143

W I N D O W S TA S K S C H E D U L I N G

Gateway Scheduling Process

The server side of the Scheduler uses the Translator System Service for translation requests and the Gateway System Service for Gateway requests. For all requests other than Translator and Gateway, the Scheduler scans the database and executes those applications ready to run. Scheduler Service Logging

The TrustedLink Scheduler is a service used to schedule an EDI task such as outbound translation or a user-defined task, such as execute a custom program or script. It polls the TrustedLink Scheduler database every minute, scanning the entries and executing those schedules ready to run. The Scheduler is installed on the server with TL Services and has no user interface. The Scheduler logs its activity to the schedlog.txt file. When the Scheduler is installed, a registry value (SCHEDULER_LOG) is placed in the registry for the TrustedLink instance. This value is set to 0 (zero). To enable diagnostic logging, set this value to 1 (one) using the TrustedLink registry tool (C:\TLEServer60\Prod60\xlate\Bin\regtool.exe). Important: Scheduler features are available only if you are running the TrustedLink server software on an host and have specified the Windows server in the configuration tool.

Gateway Scheduling Process The schedule you create in the Operations Center is entered into the TrustedLink database. The Scheduler on the server scans the database for application entries that are ready to run. When it finds an applicable entry, the Scheduler executes it. The Scheduler uses TL Services System Service for translation requests and the Gateway System Service for gateway requests. For all other requests, the Scheduler scans the database and executes those applications ready to run. Before you set up the Scheduler Service, you must set up an EDI Administrator account on the server that corresponds to the TrustedLink server. Setting up the Scheduler Service To set up the Scheduler Service 1 Check the EDI_ADM registry setting. This is the setting that controls who receives

notifications for Translator production problems. 2 Set up the Scheduler Service.

See “Defining the Scheduler Service” on page 144 for details. 3 Start the Scheduler Service.

See “Starting the Scheduler Service” on page 145 for details. Defining the Scheduler Service

After you check the EDI_ADM registry, you can set up the Scheduler Service. To set up the Scheduler Service 1 From the Start menu, select Settings > Control Panel > Administrative Tools. 2 Double-click Services.

The Services window opens. 3 Scroll to the Scheduler System Service you want to check and double-click that entry.

144



Operations Center Task Scheduling

10

The Inovis Scheduler (604) Properties (Local Computer) dialog opens. 4 Select the Automatic option for the Startup Type. 5 Click the Log On tab. 6 For Log on as: select This Account 7 To set or change This Account field, click Browse.

The Select User dialog opens. 8 Use this dialog to specify the login account the scheduler service is to use. This is the user

who has authority to run scripts that may be added to the Windows Scheduler. Programs and scripts run by the scheduler use this user account. 9 Leave the Services window open, and continue with “Starting the Scheduler Service” on

page 145 Starting the Scheduler Service

You must manually start the Scheduler Service for the first time after you set the Startup Type to Automatic. It runs automatically thereafter. To manually start the Scheduler Service to enable the Automatic function 1 From the Services window, click Start.

The Service Control Startup Timer opens. After the Service Control completes its action, the Status column lists Started for the Schedule Service.

2 Click Close, then close the Control Panel.

The Scheduler Service runs automatically.

Operations Center Task Scheduling With the Operations Center Client, you can schedule entries using the Schedule List window or Schedule Wizard. You can create or delete entries with Schedules as well as view the schedule list to see when each schedule will be started or schedules temporarily disable. You can schedule EDI or non-EDI tasks in the Operations Center. You can also view the schedule list to see when each schedule is started, and see temporarily disable schedules. There are two ways to schedule tasks or update existing schedules: ■

“Schedule List” on page 146


145


Schedule List

■

“Schedule Wizard” on page 149 This is the easiest method for creating a new schedule.

Schedule List The Schedule List window displays all schedules currently in the system. From this window, you can add, update, disable, or delete a scheduled task. To add a schedule, you can copy an existing scheduled task or create a new one. Click Schedules to open the schedule list window.

From the Schedule list window, you can: ■

“Adding a New Schedule” on page 146

■

“Updating or Disabling a Schedule” on page 146

■

“Modifying a Schedule” on page 152

■

“Deleting a Schedule” on page 152.

Adding a New Schedule To add a new schedule

From the Schedule List window, perform the appropriate action: ■

In the Schedule List window, right-click and select New to create a unique schedule. Use the instructions in the next section, “Updating or Disabling a Schedule” on page 146 to define the properties for the schedule.

■

Select an existing schedule from the list, right-click and select Create from Current to copy the existing schedule. You can then modify the properties. See “Updating or Disabling a Schedule” on page 146.

Updating or Disabling a Schedule To update or disable a schedule 1 From the Schedule List window, select the schedule to update, right-click and select

Properties.

146



Schedule List

10

You can update this schedule with a different task or a new time by typing over existing information. The name of the schedule you are updating appears in the title bar. The Schedule Properties dialog opens to the General tab. The General Tab displays basic information about the schedule, including the schedule name, the type of task and any command line options to be executed.

2 Complete or update these fields. Field

Description

Name (required)

Name for this schedule. If you are updating properties, this field is disabled and cannot be updated

Disabled

Click on this check box to disable the schedule.

Program Name (required)

Select the program you want this schedule to run;

Command Line Options

■

For EDI tasks, the program file name appears in the Program Name field.

■

For a user-defined program, enter the path name for the program in the Program Name field.

Enter command line options you want to run when the program is executed.

3 Click the When tab.


147


Schedule List

This tab displays information about when and for how long the program is scheduled to run.

4 Complete or update these fields: Field

Description

Frequency

Select the option that determines how often you want this schedule to run: ■

Once—Runs once based on the date selection in the Only Once area. Click Once, then click on the drop down list box to select the day.

■

Daily—Runs daily based on the delay selection in the Daily area. Click Daily, then select the increment of days from 1 to 6.

Tip: If today is Monday and you select 2 days, the task will be scheduled for Monday (the first instance) every two days after that: Wednesday, Friday, Sunday and Tuesday.

When

Duration

■

Weekly—Runs on a specified day every week based on the day selection in the Weekly area. Click Weekly; select the frequency of weeks from 1 to 4 and the day you want the task to be scheduled.

■

Monthly—Runs on a specified day of a specified week based on the selections in the Monthly area. Click Monthly; select the day and month, or select a day modifier, such as first, and the day of the week.

■

Yearly—Runs on a specified day based on the selection in the Yearly area. Click Yearly; select a day of the year by choosing the month and day, or by selecting a day modifier, such as first, and the day of the week. Click the End Date check box to select an end date, or leave the end date disabled if you want this schedule to always run.

You can select a time or block of time you want the schedule to run. ■

At—Enter the time you want the schedule to run.

■

Every—For every Frequency except Once, you can select the blocks of time the schedule will run between.

For every Frequency except Once, select a Start Date. You can click the End Date check box to select an end date, or leave the end date disabled if you want this schedule to always run.

148



Schedule Wizard

10

5 Click OK.

Adds, updates or disables the schedule.

Schedule Wizard You can create a schedule in the Operations Center Client using the Schedule Wizard and modify a schedule in the Schedules List. To create a schedule 1 Click Schedule Wizard.

The Schedule Wizard dialog opens.

2 In the Schedule Name field, enter a name for the schedule.

This must be a unique name. Maximum 30 alphanumeric characters. 3 Click Next.

The Schedule Wizard - Task dialog opens. 4 Select Gateway Request in the list, and click Next.

The Schedule Wizard - Task Options dialog open with Program Name field populated by cgw. 5 Type this command in the Command Line field: -m mode -q qkey Parameter

Description

-m

A literal. This switch indicates that the transmission mode follows.

mode

A variable. MODE represents the four-character transmission code. The three codes available are xmit, exch, and recv.

-q

A literal. This switch indicates that the qkey follows.

qkey

A variable. QKEY represents the name of the mailbox, up to four characters.


149


Schedule Wizard

6 Click Next.

The Schedule Wizard - Frequency dialog opens. 7 Select how often you want the task scheduled: Option

Description

Once

Task runs on one day based on the date selection in the next window. Click Next. Click the dropdown to select the day on the Once window.

Daily

Task runs daily unless you specify otherwise in the delay selection in the next window. Click Next. Select the increment of days from 1 to 6 on the Daily window. If today is Monday and you select two days, the task runs every two days. It is scheduled for Monday (the first instance), then every two days after that: Wednesday, Friday, Sunday, Tuesday, and so on.

Weekly

Task runs on a specified day every week based on the day selection in the next window. Click Next. Select the frequency of weeks from 1 to 4 and the day you want the task scheduled to run on the Weekly window.

Monthly

Task runs on a specified day of one or more months based on the selections in the next window. Click Next to display the Monthly window. Select the day and increment of month, or select a day modifier, such as first, second, third, and the day of the week, week day, weekend day, and so on.

Yearly

Task runs on a specified day of the year based on the selection in the next window. Click Next. Select a day of the year on the Yearly window.

8 Click Next.

Depending on the selection you made, one of these windows opens: Once, Daily, Weekly, Monthly, or Yearly. 9 If you run the Gateway every week on specific days, the best selection is weekly, as shown

in the graphic.

10 Click Next.

150



Schedule Wizard

10

The Schedule Wizard - When dialog opens if you did not select Once on the Frequency dialog.


Enter a specific time

■

Select an interval (for example, every 30 minutes) between 5:00 AM and 11:00 PM.

■

If you selected Once on the Frequency window, enter a specific time. Skip to step 14.

12 Click Next.

The Schedule Wizard - Duration dialog opens.

13 Provide a date in the Start Date field. 14 Select the End Date check box and specify an end date, if necessary. 15 Click Finish.

A message box opens indicating the schedule has been added.


151


Schedule Wizard

Modifying a Schedule To modify a schedule with the Schedules tool 1 Click

Schedules.

The Schedule List opens. 2 From the Schedule List window, select the schedule to update, right-click and select

Properties. The name of the schedule you are updating appears in the title bar. The Schedule Properties dialog opens to the General tab. The General Tab displays basic information about the schedule, including the schedule name, the type of task and any command line options to be executed. The Schedule Properties dialog opens displaying the General tab.

3 Make the modifications as needed. 4 Select the When tab. 5 Make modifications, as needed. 6 Click OK.

Deleting a Schedule To delete a schedule 1 Click Schedules.

The Schedules List opens. 2 Select the schedule, right-click and select Delete. 3 Click Yes to confirm the deletion.

152


Translations

T

11

he next several chapters describe the translation process. The following graphic is an overview of the material.

See “Scheduling Tasks Overview” on page 137.

See “Translations” on page 153.

See the “Logging and Reporting” on page 22.

There are two methods to start event translations: ■

Method 1—EDI documents are received through the Gateway and deposited into a Gateway mailbox. Gateway then sends a request to TL Services to begin the translation.

■

Method 2—TL Services can be run manually from the Command Manager of the Operations Center, scheduled via cron, or run from the command line.

This chapter discusses Method 2, translating an event manually from the Operations Center using the Command Manager. Topics include: ■

“Command Manager” on page 154

■

“Using the Browser” on page 154

■

“The User Profile dialog opens.” on page 155

■

“Deleting a Translation Request” on page 158

153

TR A N S L A T I O N S

Command Manager

■

“Checking TL Services Status” on page 158

■

“Queuing a File” on page 158

■

“Transferring a File From a Mailbox” on page 159

■

“Request Log List” on page 160

Command Manager Command Manager consists of these features: ■

■

■

Browser: ■

Reads files

■

Determines TL Services status

■

Performs Translator and Gateway actions

Request Log List: ■

Monitors activity of translation requests on the server

■

Removes completed requests from the list

Upload Translation Tables ■

■

Copies translation tables for an event from the client machine running Workbench and Mapper.

Download Translation Tables ■

Copies translation tables for an event to the Workbench.

Using the Browser You can use the Browser to perform these tasks: ■

Initiate translation

■

View files on the server

■

Perform Gateway commands such as queuing and manual transfer

■

Check the status of TL Services.

To activate the Browser button, the Operations Center must be connected to TL Services and the browser path must be specified. Opening the Browser To open the browser 1 Click Browser.

154



Setting the Browser Path

11

The Browser dialog opens.

Setting the Browser Path If your user login was set up by the system administrator, contact the system administrator to change the Initial Browser Path field. If your user login has not been set up with security, you can set the browser path. To set the browser path 1 Select Options > User Profile.

The User Profile dialog opens.

2 In the Initial Browser Path field, type a path name where the files you want to display are

located. 3 In the Viewer field, specify an application to view files. The default application is write.exe.

Translation Requests To translate an event manually from the Command Manager 1 Create the event in the Operations Center. See “Event Wizard” on page 105. 2 Map the event in the Workbench or Mapper mapping tools. 3 Upload the map to the server. See “Translation Table Transfer” on page 218.


155


Translation Requests

Submitting a Translation Request from the Operations Center To submit a translation request 1 Click Browser.

The Browser dialog opens. 2 Select the file or directory you want to translate. 3 Right-click and select Translate.

The Translate Options dialog opens.

4 Provide information for these fields: Field

Direction Mode

Description ■

Inbound

■

Outbound

■

Production

■

Test

■

Recover

Optional Parameters

156

History Logging

Select to log the interchange, functional group, and transaction set control numbers to the database tables.

Partial Accept

With this option enabled, the translators reject documents at the accept level specified on the Event Properties (interchange, functional group, document). Otherwise the inbound translator rejects all documents at the interchange level, and the outbound translator rejects all documents at the document level, regardless of what is specified on the Event Properties.




11

Field

Description

Special Application Interface

Select to execute the translation job with Special Application Interface processing. Refer to your Special Application Interface manual for details.

Split Documents

Select to create a separate application file for each EDI document. If not selected, TrustedLink will create one application file for multiple EDI documents. Inbound only.

Compliance Override Profile

Select an option from the dropdown: ■

Default_in contains a list of selected standardized error types that TrustedLink regularly rejects for inbound documents.

■

Default_out contains a list of selected standardized error types that TrustedLink regularly rejects for outbound documents.

For information about Optional Compliance Checking. Input Override Filename

Outbound translations only. Enter the path name or fully qualified file name of a source file. This field defines the source data location for the outbound translation. A file specified here will also override a data source specified in a control file, if used.

Output Override Filename

Type the path name or fully qualified file name of a destination file for translation output. A file specified here overrides the production data path destination. On outbound, it overrides the mailbox path. Data output from Translator will be written to the Output Override file instead of the mailbox path. On inbound, it overrides the application path.

Delete Input

If selected, the input file or directory is deleted. Available only for production mode, inbound and outbound.

Recov Mem Threshold (MB)

If selected, type a value in megabytes to set the upper limit of memory on the server to allocate for recovery processing.

Error Logging

Select check box to log errors to the database tables.

Error Detection

If selected, Translator continues validation after the first error has been encountered. If not selected, Translator stops on the first error it finds. Test mode only.

Sequential Control Numbering

Normal setting is to turn on sequential control number generation (checked). Outbound translations only.

Priority

Choose the priority of the translation request. The lower the value, the greater the urgency. The default value of 0 is the highest urgency. See “Priority Processing” in the “Inbound Translation Requests” chapter of the TrustedLink Enterprise System Reference Guide.

Trace Options

Command Tracing

Select to trace mapping commands during translation. Creates a file called cmdtrace.txt (cmdtrace in UNIX) in the working directory. Note: You can program a map to turn command trace on and off by using the Command Trace On and Command Trace Off commands described in the TrustedLink Enterprise Mapping Workbench User Guide.

Maximum Trace File Size

Use in conjunction with the Command Trace option. Enter a maximum size (in megabytes) for the cmdtrace file.

ODBC Tracing

Select to create an ODBC trace file in the working directory. Information contained in the ODBC trace file can be used to troubleshoot databaserelated errors.

Translate Item

Path/File


Type the path name to the file or directory you want to translate.

157



Field

Description

Inbound QKey

For inbound translation, select the QKey for the Gateway mailbox which contains data to be translated.

Outbound Control File

For outbound translation, type the path name for the control file.

Outbound Staging Database

Directs the translator to obtain input data from the outbound staging database. Outbound translations only.

5 Click OK.

A message box displays indicating the request has been made to the Translator. The Request Log List windows opens allowing you to monitor the status of your translation request. Deleting a Translation Request

Two rules apply to deleting translation requests: ■

To delete a translation request, you must be its owner.

■

You cannot remove translation requests while they are in process.

To remove a translation request 1 Click Request Log.

2 Press the

F5 key to refresh the screen.

The Request Log List window displays all translation requests. 3 Right-click and select Remove Request.

The selected translation request is removed. Checking TL Services Status To check the status of TL Services using the browser 1 Click Browser. 2 Right-click on the file and select Translator Server Status.

A message box indicating the status of TL Services opens. If you receive a message that TL Services is not running, verify the server name and port number are correct. See “Setting the Browser Path” on page 155 for information about locating the information.

Note:

Queuing a File

You can use the Browser to send a file to a mailbox. To send a file to a mailbox 1 From the Operations Center, click Browser. 2 Select the file you want to queue. 3 Right-click and select Gateway, then Queue.

158




11

The Mailbox Queue Options dialog opens.

4 Provide this information: Field

Description

Direction

Select the direction: ■

Outbound indicates you want to place the selected file in a mailbox.

■

Inbound indicates you are receiving a file.

QKey

Select the QKey of the mailbox from the dropdown. You can click Browse to locate the QKey.

Contains Binary Segment

Select to transmit through Inovisworks a document that contains: ■

binary data

■

an ANSI x12 document with BIN or BDS data

Filename

The path to the selected file displays in this field. If this is not the correct path, or you want to queue a different file, enter the path to the file you want to queue.

X.400 Attachment

Not yet available.

5 Click OK.

A message displays indicating the file has been queued. Transferring a File From a Mailbox

You can submit a request to the Gateway to transfer files in a mailbox to a VAN or trading partner using the Browser. To transfer a file 1 Click Browser. 2 Right-click and select Gateway, then Manual Transfer.


159


Request Log List

The Manual Transfer Option dialog opens.

3 Complete the fields or make selections: Field

Description

QKey

Click the dropdown to select the QKey.

Mode

Click the dropdown to select the type of manual transfer.

4 Click OK.

A message displays indicating the request has been scheduled.

Request Log List This section describes how to use the Request Log List window. This window displays automatically after a translation request. Use this feature to perform these functions: ■

Determine the status of your translation requests

■

Search for requests based on specific criteria

■

Remove a translation request.

Refreshing the Window To refresh the data in the Request Log List window

Do one of the following: ■

Press the F5 key

■

Select Window, then Refresh.

Displaying the Request Log List To display the Request Log List window 1 Click Request Log.

The Request Log List dialog opens. This information is provided in the Request Log List window: Column

Description

Status

Status of the translation: Completed, Failed, Started, or Submitted.

Message Text

Displays each phase of translation. Each message is delimited by a semicolon. Example: Start EDICNVRT; edixlato Completed.

Activity

160

Translation activity requested: Inbound or Outbound.



Command Line Translation Requests

11

Column

Description

Input Location

Location on the server where the file resided.

Output Location

Location of the working directory. The working directory is also the job name.

Submitted

Date and time the file was submitted.

Started

Date and time the file began translation.

Completed

Date and time translation was completed.

Owner

Logon name of the person requesting the translation.

Request ID

Unique value assigned to the request by the system.

2 Right-click the Request Log List window and select Search Criteria.

The Search Criteria dialog displays:

3 Provide the search criteria: Field

Description

Owner

User initiating the translation request. Select the user from the dropdown or type the first few letters of the user’s name, or select All to search for all owners.

Activity

Type of translation to search for: inbound, outbound, or all.

Status

Types of status to search for: Submitted, Started, Completed, or Failed. Click All to select every status. To clear all check boxes, click Clear.

4 Click OK.

The Request Log List window displays translation requests based on the search criteria.

Command Line Translation Requests Using the command line or the Operations Center, you can create a request for translation. This information is provided if you encounter errors: ■

edixlati, edixlato, editd (UNIX), and Operations Center requests for translation will fail if TL Services are not running.

■

Command line parameters are case-sensitive. Also, no default value is taken for parameters that accept additional parameter data (‘d’, ‘h’, ‘P’). Values for the parameters ‘d’, ‘h’, and ‘P’ must have parameter data explicitly set on the command line.

■

The S command line option allows EDI document splitting for all inbound EDI translations. The result will be a different application file produced for each EDI document. This option requires the inbound application point to a directory.


161


Command Line Translation Requests

■

162

A Java program is available to facilitate submission of translation requests across heterogeneous operating systems. If the operating system can run a Java Virtual Machine then a request for translation can be submitted to the TL Services server.


Map Versioning

12

T

rustedLink Enterprise offers an automatic versioning control component called the Map Repository that monitors changes to Workbench maps. Map Repository can stand alone or, coupled with Audit Manager, can be part of a comprehensive TLE change management monitoring system TLE's Version Control is done through the licensing of a third-party Version Control System called Subversion. More information about this integration tool can be found at http://subversion.tigris.org. This chapter is organized as follows: ■

“Map Versioning TLE Components” on page 163

■

“TLE Client Installer” on page 164

■

“Access Manager Version Control Function” on page 164

■

“TL Configuration” on page 164

■

“Map Repository Version Control” on page 164

■

“Operations Center Version Control” on page 165

■

“Workbench Version Control Functions” on page 166

■

“Setting Up Map Versioning In TL Configuration” on page 167

■

“Using Map Versioning In the Operations Center” on page 168

■

“Using the Map Repository in Workbench” on page 172

Map Versioning TLE Components The Map Repository server must be installed on a Windows Server. It can be installed on the TLE client machine or separately, and needs regular back up. Major TLE Components involved in the Map Versioning process include: ■

Serial Number

■

TLE Client Installer

■

Access Manager

■

TLConfig

■

TLE Map Repository

■

Operations Center

■

Workbench

163

M A P VE R S I O N I N G

TLE Client Installer

When Map Versioning is purchased, the TLE Serial Number includes a Map Versioning flag used by Workbench and the Operations Center.

TLE Client Installer The Map Versioning installation is an option selected during the Client Installation process. More than one Map Repository can be installed using the same serial number; therefore, administrators, using the TL Configuration Tool, can connect different databases to different Repositories. For example: One database server instance can be assigned to testing with no specific map Repository requirements; another server instance can be assigned to the production environment requiring uploading maps from a specific Repository; and yet another for a different production environment. See the “TrustedLink Enterprise Client Installation” chapter of the TrustedLink Enterprise Installation Guide for more information.

Access Manager Version Control Function Access Manager controls which Operations Center users have permission to access which map versioning features.

TL Configuration The TL Configuration Tool is where the choice is made to use the Map Repository, and, if chosen, the database instance must be configured and the Map Repository path identified. When the Map Repository is selected, only maps from the Repository can be uploaded to the server. Workbench maps cannot be directly uploaded. Note: Mapper maps are not currently supported in Map Versioning.

Map Repository Version Control The Map Repository is a networked version control system. Remote Map Repository operations use a network connection from the Client to the Repository Server. The TLE Map Repository follows the standard Subversion directory hierarchy conventions for Trunk development and Tagged releases.

164



Operations Center Version Control

12

TLE - Subversion Directory Hierarchy

Workbench Trunk Development

Root

FA997I.ans FA997I.dsc FA997I.cnt FA997I.cnd FA997I.id FA997I.evt

Trunk FA997I

ANSIFCT Tags

Release1 Operations Center Tagged Releases

FA9971

ANSIFCT Trunk and Tags folders are created in a TLE Repository when it’s first installed: ■

Tags directory (Operations Center)—Stores releases.

■

Trunk directory (Mapping Workbench)—Stores map development.

For Map Repository maintenance beyond the scope of actions described within Workbench and the Operations Center, see http://subversion.tigris.org.

Operations Center Version Control When the Map Repository option is activated in TL Configuration the Operations Center may group maps into Releases. ■

Releases are map sets grouped by date, map type (POs), etc. Releases are created by the Repository Administrator.

■

Releases can be uploaded in their entirety, or an individual map within the Release can be uploaded.

■

Releases are snapshots of individual revised maps intended for promotion into production.

■

Releases can be used to roll back maps that are failing in production.


165


Workbench Version Control Functions

The Operations Center supports these Map Repository functions and Administrative tasks: ■

Downloading either individual maps or the entire Map Repository to create a local working copy.

■

Uploading either individual maps, or entire sets of map files from the local working copy to the TLE Server production area.

■

Creating and managing Map Repository releases.

■

Locking map files.

■

Unlocking maps.

■

Checking in existing TLE maps not yet in the Map Repository.

Workbench Version Control Functions When the Map Repository is enabled, these functions are supported in Workbench: ■

Importing maps from the Map Repository

■

Locking map files from the Map Repository for editing

■

Checking maps back into the Map Repository.

■

Promoting maps to production using Command Manager > Upload Repository in the Operations Center Client.

■

Developing Workbench Maps in the Trunk directory and saving them to the Workbench database. When a saved file is checked back into the Repository, new map tables are added to \WB\Repository\Trunk and sent to the Repository Server.

Note: Exporting maps is not required. If you do export a map event, exported map tables are written to \WB\xlate directory.

Workbench and TLE Map Repository

Maps are checked out of the Map Repository into Workbench using the "lock-modifyunlock" system. ■

Only locked maps can be modified and saved with the same name. Note:

Unlocked maps can be modified but must be saved by another name.

■

Until an imported map is locked it is Read Only.

■

Only the person who locks a map has modification ability.

Only the latest version of the map can be locked and modified, all prior map versions are Read Only in the Map Repository. For Map Repository maintenance beyond the scope of actions described within Workbench and the Operations Center, see http://subversion.tigris.org. Setting up Access Manager

See TrustedLink Enterprise Access Manager User Guide.

166



Setting Up Map Versioning In TL Configuration

12

Setting Up Map Versioning In TL Configuration TL Configuration is where the choice is made to use the Map Repository. If selected: ■

The database instance must be configured, and the Map Repository path identified.

■

Only maps from the Repository can be uploaded to the server. Workbench maps cannot be uploaded directly from \WB\xlate directory.

■

Upload Translation Tables only lists Mapper XML maps.

To set up Map Versioning through TL Configuration 1 From the TL Configuration General window, in the Map Versioning area, select Use

Repository for maps.

Select Use Repository for Maps Type the Repository URL for a specific database instance

2 Type the URL path for the Map Repository database instance. file is a Subversion communication naming convention. Subversion has other types of communication naming conventions but TLE only supports the file communications type. ■

If the repository is located on a separate Windows server or PC: file:///path/path

■

If the repository is on a TLE Windows server local drive: file:///C:/TrustedLink/MapVersioning/TLE_MAP_REPOS

Note:

Pathnames are case-sensitive.

3 Click OK.

TLE verifies the URL.


167


Using Map Versioning In the Operations Center

Using Map Versioning In the Operations Center To use Map Versioning in the Operations Center

From the Operations Center Client window, select View > Command Manager > Upload Repository Tables…

With the Repository option selected in TL Configuration, Upload Translation Tables lists only Mapper XML map files. With the TL Configuration Repository option selected, Upload Repository Tables is active. Workbench Maps must be uploaded using the Map Repository.

With the TL Configuration Repository option selected: ■

Upload Repository Tables is available

■

The Map Repository must be used to upload Workbench maps.

■

Upload Translation Tables lists only Mapper XML map files.

TL Configuration Repository option must be selected for the Upload Repository Tables selection to be available. Viewing Map Versions To view map versions 1 From the Operations Center Client window, select View > Command Manager >

Upload Repository Tables…

168




12

The Upload Repository Maps screen shows a listing of Repository Maps available for uploading to the Server. The Server panel lists all maps in production. Lists all available Repository Maps. < > indicates a Map Release set.

Lists all available production maps on the Server.

Click to view the Map Revision screen for map selection.

2 Select a or an individual map > Upload.

The Map Revisions screen lists all revisions of your selection...

Important: Revision numbers are based on the number of revisions made to the entire Map Repository, not the number of revisions made to an individual map.

Using the Repository Administration window To use the Repository Administration window 1 From the Operations Center Client window, select View > Command Manager >

Repository Administration...


169



2 The Repository Administration window shows all Repository, Working, and Server maps. Lists all maps in the Map Repository trunk - individual map selection only.

Lists all maps uploaded to the TLE Server.

Lists local maps downloaded from the TLE Server.

Delete...Any Deletion requires a comment in the confirmation dialog box.

Unlock - Unlocks a selected locked map regardless of who has it locked.

Download Downloads selected maps are not listed in the Map Repository to the Working Maps.

CheckIn...Enabled if map selection includes a map not already listed in the Repository.

Refresh selected or all working maps. Refreshes the Working copy with the most recent revision from the Map Repository.

Delete...Deletes the map(s) from the Working list but does not remove the map from the Map Repository.

Repository Administration Fields This button:

Does this...

Repository Maps Panel Delete

Marks the selected map as deleted in the Map Repository. Displays a confirmation dialog box and requires a description/comment. Note: This does not delete the map from the TLE Server.

Lock

Locks the selected map. Note: Only the current version of the map can be locked. The lock owner is TLE Server or PC logon user, not the TLE user or the Access Manager User.

Unlock

The Repository Administrator can unlock maps, if need be.

Checkout

Opens the Map Revisions screen for selection of either the most recent revision or a prior revision of the selected map. The map is moved to local Working Maps. Important: Revision numbers are based on the number of revisions made to the entire Map Repository, not the number of revisions made to the selected map(s). Selecting checks out the entire repository and specifies a Repository revision.

Working Maps Panel Check In

170

Active when at least one of the selected maps does not already exist in the repository. Opens a Map Checkin dialog box requiring a comment.




12

This button:

Does this...

Refresh

When selected, a Refresh Working Maps dialog box opens where you choose to select All Working Maps or Selected Working Maps. Updates the local working copy with the most recent version from the Map Repository.

Delete

When one or more map is selected, deletes the map from the local working copy. Note: Will not delete the map from the Map Repository.

Server Maps Panel Download

Enabled when one or more Server Maps selected maps do not exist in the Repository. Selected maps are downloaded (copied) from the TLE Server to Working Maps. Multiple maps may be imported in a single operation.

Repository Administration Window Release...

When selected, displays the Map Release dialog box to create and delete Map Releases.

Creating Map Releases To create a map release 1 From the Operations Center Client window, select View > Command Manager >

Repository Administration... 2 From the Repository Administration window, click Release.

The Map Releases screen opens.

Active when a specific map revision is selected. The Map Revisions screen opens listing the Revision log.

Click to Add a Release.


Active when a release is selected. A single revision cannot be deleted.

171


Using the Map Repository in Workbench

3 From the Map Release dialog box, click Add. Both Name: and Comment: are required fields. Choose the source for your new release.

4 Type the release Name and a descriptive Comment. Note: Both fields are required. 5 Select whether your Release source is the Map Repository trunk or Working Maps, and

click OK. Your release will either contain a list of maps from the Map Repository maps, or the Working Maps. Deleting Map Releases

Map releases can only be deleted from the map releases dialog. To delete a map release 1 From whichever window or panel you choose to delete the map release, select the

Release you need to delete. 2 Click Delete. 3 In the Confirm Delete dialog box, verify the map name and type a required Comment >

OK. Note:

The map is marked as Deleted in the Map Repository, but it is not deleted.

Using the Map Repository in Workbench When the Map Repository is selected, only maps from the Repository can be uploaded to the server. Workbench maps cannot be uploaded directly from the \WB\xlate directory using the Upload Translation Tables icon in the Operation Center Client. When TLE detects the Repository license key, the Map Versioning box on the Workbench Options screen is activated. Select this option to use the Repository Manager to import events. Type the Repository URL. File is a Subversion communication naming convention. While Subversion has other types of communication naming conventions, TLE only supports file.

172




12

1 On the Options screen, select Use Repository for Maps in the Map Versioning box.

This selection means that all existing events must be imported from the Map Repository using the Repository Manager menu.

Note:

2 Type the Repository URL path for the Map Repository database instance, and click OK.

TLE verifies the URL. Note:

This is the same URL used in the TL Configuration General screen.

file is a Subversion communication naming convention. Subversion has other types of communication naming conventions but TLE only supports the file communications type. ■

If the repository is located on a separate Windows server or PC: file:///path/path

■

If the repository is on a TLE Windows server local drive: file:///C:/TrustedLink/MapVersioning/TLE_MAP_REPOS

3 From the Mapping Workbench window, select Event > Repository Manager. Note: Because Use Repository for Maps was selected on the Workbench Options screen, the Import selection is not available on the Event menu. Events must be imported from the Map Repository using the Repository Manager menu. Since Access Manager is not a component of Workbench, there is no user ID checking in the Workbench.

Using the Repository Manager Window

The Repository Manager window lists all Repository Maps available in the Repository trunk. These maps can be imported individually, or the entire Repository imported into the Workbench database. Listing of all Maps in the Map Repository

Select All to import the entire Map Repository.

Lists all available Events

Click to Unlock selected map(s) from the Event list.

Click to import selected map(s).


Click to check in one or more locked events into the Map Repository.

Click to lock selected map(s) from the Event list.

173



Importing Maps into the Workbench Database

Only the most recent version of each map should be imported. To import maps into Workbench 1 Select either an individual map for import, or select All, and import the entire Map

Repository > Import. The Map Revisions screen lists all revisions of the selected map, or the entire Map Repository. 2 Select the current map revision you need to import, and click OK.

The selection is imported into the Workbench database, and is listed as an Event in the Workbench Events panel. Modifying Events

When you lock an event, that event is replaced with the latest revision from the Map Repository, assuring that you are modifying the most recent version of the selected map. To modify events in Workbench 1 Select the Event(s) you need to modify and click Lock

Only when the selected Event(s) are locked can modifications be made. Click OK, a message confirms the lock. Note:

2 Close the Map Repository window. 3 From the Workbench Event menu, select Open and make your event revisions.

If you select an event from the Open Event screen that has not been locked, you will receive a message that the map must be locked before any modifications can be made. Either return to the Event list on the Map Repository window and lock the map, or continue. If you choose to continue, you must rename the event before you can save any changes.

Note:

Importing Third Party Maps

The procedure for importing third party maps depends upon whether the map is new or existing. See: ■

“To import a new map”

■

“To import a third-party map keeping the name of an existing map”

To import a new map

If a new map is sent from a third party, for example a map created by Inovis Professional Services, it is imported by the regular Workbench new map import process. 1 Copy the map table files in the \WB\xlate directory. 2 From Workbench select Event > New. 3 Select the Import A Map checkbox. 4 Select the new map from the dropdown > click OK.

Once the map is imported into Workbench, it must be checked in (Check-in) to Map Versioning Repository (Event > Repository Manager). For more information about importing maps in Workbench, see the Workbench Mapping Guide.

174




12

To import a third-party map keeping the name of an existing map

If a map from a third party has the same name as an existing map. For example, if Inovis Professional Services modified an existing map and you need to retain the map name even though it is the name of an existing map, follow this process: 1 With the Repository active, lock the existing map. 2 From the Workbench Options screen, deactivate the Use Repository for Maps selection. 3 Import the map event using the regular Workbench import process. 4 From the Workbench Options screen, reactivate the Use Repository for Maps selection. 5 Check in the latest version of the map.

See “Checking Maps Into the Map Repository” on page 175. Checking Maps Into the Map Repository

From the Event menu select Repository Manager and find your map listed in the Events panel. Note: Keeping the map locked retains any map changes.

To check maps into the Map Repository 1 Select the map(s) you need to check into the Map Repository and click Check In. Type a brief description of any modifications. This field is mandatory. Select to use the same comment for all events you are checking into the Map Repository. Select to keep the event locked after check in to the Map Repository.

2 On the Event Check In screen, the Comment field is mandatory. Type a brief description

of any modifications. 3 If you are checking in more than one event, select whether you want to use this

description for all of them. 4 If you need to keep the event locked after check in, select Retain Lock after check in. 5 Click OK, and the event is checked in the Map Repository.


175



176


13

TL Services

T


■

“Submitting Requests to TL Services” on page 177

■

“Command Line Formats” on page 177

Submitting Requests to TL Services Two programs can be used to submit requests to TL Services from the command line: tlreqc and jtlreqc. can be used from any supported TrustedLink Enterprise platform.

■

tlreqc

■

is a Java version of tlreqc that can be used on unsupported TrustedLink Enterprise platforms. It requires Java 1.4. jtlreqc.jar

Note: For TrustedLink Enterprise UNIX, any programs that submit translation requests need to be modified to submit them through TL services. (See section on tlreqc for the syntax).

Command Line Formats To request a translation use this command syntax: tlreqc or java -jar jtlreqc.jar

The table lists the options that can be included in the command: Note: If you are going to have multiple jtlreqc running simultaneously, the TL Service

client name must be unique. Option

Description

-r

TL Services request

-u

TL Service Client Name

-h

TL Services host name

-p

TL Services port number

The possible service requests are: ■

Tlstat—get

system status

■

Xlati—submit

an inbound translation

■

Xlato—submit

an outbound translation

177

TL SERVICES

Command Line Formats

For more information see the TrustedLink Enterprise TL Services User Guide.

178


Message Configuration

T

14

his chapter describes message information for TrustedLink Enterprise:

■

“Message Configuration Overview” on page 179

■

“Prerequisites” on page 179

■

“Types of Messages to EDI Administrators” on page 180

■

“Types of Messages to Contacts” on page 180

■

“Mail Function Setup Process” on page 185

■

“Viewing Contact Email Addresses” on page 185

Message Configuration Overview TrustedLink Enterprise produces error messages for the EDI Administrator and the EDI Representative. The edidr997, edixssti and edixu997 programs, and the tldr997 service create message files for the EDI Representative. The edidbhpg, edieprg, inbound, and outbound translation services send messages to the EDI Administrator. On a TrustedLink server in Windows, registry values define the address of the EDI Administrator. On a TrustedLink server on UNIX, the edi_env_sh file defines the address of the EDI Administrator. The file defines the working environment on the server, and the TrustedLink scripts load the edi_env_sh file to define their environment variables. Set the EDI Administrator email address in the TL Configuration Tool. See that chapter of the TrustedLink Enterprise Installation Guide.

Prerequisites The accounts used to start TL Services must have access to the SMTP server. The email addresses used for the EDI Administrator, Gateway Administrator, contacts (which includes EDI Representatives) must also be available to the SMTP server.

179

MESSAGE CONFIGURATION

Types of Messages to EDI Administrators

Types of Messages to EDI Administrators The EDI Administrator receives the following message types: Message Type

Description

Translation reject

Sent by the inbound and outbound translation services when a document is rejected. For example: There are rejected documents in job I23400. The working directory was \Training\ediclass\xlate\i\23400.

EDI Representative unknown

Sent by the inbound translation service program when the edixssti program does not find a setup that matches the error field specified.

No records from the edicnvrt program

Sent by the outbound translation service when the edicnvrt program does not write records to the xlate file.

Non-zero return code

Sent when the TLE programs terminate with a non-zero return code.

Abnormal termination (abend)

Generated by all TLE programs when they self-abend because of a critical problem. For example: EDIXLATI did not complete successfully. The return code was 201 and the working directory was \Training\ediclass\xlate\i\26800.

Types of Messages to Contacts For more about contacts, including EDI Representatives, see “Contact Management” on page 37. For more about FA reconciliation and delinquency emails, their attachments, and the file naming conventions of the those attachments, see the “FA Reconciliation and Delinquency Processing“ chapter of the TrustedLink Enterprise Translation Setup Guide. Note: In this guide the capitalized “Contacts” refers to Contacts that are not EDI Representatives. The small-case “contacts” refers to both EDI Representatives and Contacts.

The table below includes the types of messages TLE sends to contacts, the names the programs that generate the messages, and message examples. Note the following:

180

■

If the message involves a batch FA, TLE sends the message only to the EDI Representative for the trading partner. If the message involves a real-time FA, TLE sends a message to the EDI Representatives for the trading partner and the event (if assigned).

■

TLE sends Recover, Reject, and Test messages to EDI Representatives for both the trading partner and the event (if assigned).

■

Contacts that are not EDI Representatives receive only one type of message—delinquent FA notifications for real-time FAs.



Types of Messages to Contacts

14

The message types information is as follows: Message Type

Description

Delinquent FA

For batch FAs, the edidr997 program sends this message to the EDI Rep for the trading partner after it decrements a transmission’s Reconcile Count to below zero. For real-time FAs, if the tldr997 service finds a transmission that has an expired FA Delinquent Date, it sends this message to all of the following that exist—EDI Rep for the trading partner, EDI Rep for the event, and notification Contacts for the trading partner and application (of original transmission). For example: DELINQUENT FA NOTICE COMPANY = ACME INC. DIV-A INT SND ID = TEACHER-ISA-ID INT RCV ID = ACME-ISA-ID FG SND ID = TEACHER-GS-ID FG RCV ID = ACME-GS-ID INT CNTL # = 00000000000001 FG CNTL # = 00000000000001 GS TYPE = PO DIRECTION = O DATE SENT = 2006-06-19 STATUS: T PLEASE CONTACT : NAME = John Doe PHONE = 555-1234

Recover

Sent by the edixssti program to EDI Reps for the trading partner and the event when it writes documents to the recover file. The message tells the EDI Rep(s) which trading partner needs to have data recovered. Edixssti creates this message when it cannot access an application file and has to write the inbound documents to the recover file in the working directory. The problem may be that a directory doesn’t exist on the server or permissions are set incorrectly. See also “Inbound EDI Recovery Messages” on page 184. For example: Cannot access path name AAEX\EDI\820DOC EDI-REP MUST RECOVER 820 FEED FROM HES THE TRANSLATED FEED IS LOCATED IN AAEX\RECOV GS SENDER ID IS HES GS RECEIVER ID IS INOVIS


181



Message Type

Description

Reject

Sent by the edixssti program to the EDI Reps for the trading partner and the event when it writes documents to the reject file. Edixssti creates this message when it cannot locate the inbound application on the TLE database and has to write the inbound documents to the reject file in the working directory. The reason why the edixssti program would not be able to locate the inbound application on the TLE database would most likely be related to a mapping error. Go back to the Workbench and check to make you are writing your application records correctly, paying special attention to the Staging Key (WS_Input) record. When the application specified in the Staging Key is not set up in the Operations Center Application Properties, Event Properties, and Trading Partner Properties windows, TLE sends a reject message to the EDI Representative(s). See also “Inbound EDI Reject Messages” on page 184. For example: A 850 FEED FROM ACME INC. DIV-A HAS BEEN REJECTED. THE TRANSLATED FEED IS LOCATED IN C:\training\ediclass\xlate\i\31700\reject

FG SENDER ID IS ACME-GS-ID FG RECEIVER ID IS TEACHER-GS-ID FG SENDER ID IS ACME-GS-ID FG RECEIVER ID IS TEACHER-GS-ID Bad SQL code while getting application info. SQLCODE = 100 GROUP = SC APPL = MKT SUBSYSTEM = 820 RELEASE = 1.0 Test

Sent by the edixssti program to the EDI Reps for the trading partner and the event when it successfully processes a test file from a trading partner. Edixssti creates this message when it successfully processes inbound test EDI-toFlat-File or EDI-to-XML documents and writes them to an application file. See also “Inbound EDI Test Messages” on page 185. For example: ACME INC. DIV-A HAS SENT A TEST 850 THE TRANSLATED FEED IS LOCATED IN \Training\teacher\tapplin\appfile

FG SENDER ID IS ACME-GS-ID FG RECEIVER ID IS TEACHER-GS-ID

182




14

Message Type

Description

Duplicate FA

Sent by the edixu997 program (batch FA) to the EDI Rep for the trading partner, or by the tlxlpost postprocessor (real-time FA) to the EDI Reps for the trading partner and the event, upon reconciling a duplicate functional acknowledgment. For example: W PROC.500 ACME-GS-ID has sent a duplicate 997 to: TEACHER-GS-ID 1st 997 for O PO FG # 00000000000001 Was received on 2006-06-03 The ACME INC. DIV-A Transaction contact is: John Doe They can be reached at 555-1234

No original document

Sent by the edixu997 program (batch FA) to the EDI Rep for the trading partner, or by the tlxlpost postprocessor (real-time FA) to the EDI Reps for the trading partner and the event, when no original document exists for an FA it attempts to reconcile. For example: W PROC.502 ACME-GS-ID has sent a 997 to: TEACHER-GS-ID Original feed was not logged Unable to find transmission info Looking for Dir: O Stat: T FG Type: PO FG # 00000000000001 The ACME INC. DIV-A Transaction contact is: John Doe They can be reached at 555-1234

FA Not Expected

Sent by the edixu997 program (batch FA) to the EDI Rep for the trading partner when it reconciles an FA and the event properties of the original document indicate that the FA was not expected. Not applicable to real-time FAs. For example: W PROC.500 ACME-GS-ID has sent an unexpected 997 to: TEACHER-GS-ID EDI_rep should update FA expected flag The ACME INC. DIV-A Transaction contact is: John Doe They can be reached at 555-1234


183



Message Type

Description

FA Rejects Document(s)

Sent by the edixu997 program (batch FA) to the EDI Rep for the trading partner, or by the tlxlpost postprocessor (real-time FA) to the EDI Reps for the trading partner and the event, when it reconciles an FA that indicates the receiver rejects the original document(s). For example: W PROC.512 ACME-GS-ID has sent a(n) Rejected 997 to TEACHER-GS-ID The rejected O 850 was sent on 1998-12-03 and is: FG # 00000000000072 All 2 document(s) sent in the FA were rejected The TEACHER INC. DIV-A Transaction contact is: John Doe They can be reached at 555-1234

Inbound EDI Recovery Messages

Edixssti sends out recovery messages when it cannot allocate the inbound application file. Edixssti accesses information specified on the Trading Partner Properties window to get the name of the EDI Representative assigned to the trading partner. It then sends a message to the contact specified in the Error EV field on the EDI Representatives window. The message identifies the trading partner that needs to have data recovered. Here is a sample recovery message: Cannot access path name AAEX/EDI/820DOC EDI-REP MUST RECOVER 820 FEED FROM HES THE translator FEED IS LOCATED IN AAEX/RECOV GS SENDER ID IS HES GS RECEIVER ID IS HES1

When you receive a Recovery Message, use the edixssti program to recover the data. The table describes inbound EDI recovery message lines: Message Line Example

Explanation

CANNOT ACCESS path name: AAEX\EDI\820DOC

Application file.

EDI-REP MUST RECOVER 820

Doc ID.

FEED FROM HES DEV

HES is the Trading Partner name and DEV is the Trading Partner business unit.

THE translator FEED IS LOCATED IN AAEX\RECOV

Recovery path name specified in the program.

GS SENDER ID IS HES

The functional group ID of the sender.

GS RECEIVER IS INOVIS

The internal functional group ID.

Inbound EDI Reject Messages

Edixssti sends an EDI representative a message similar to the example when the application specified in the Staging Key (WS-INPUT) is not set up on the Ops Center Application Properties, Event Properties, and Trading Partner Properties windows. A 820 THE GS GS

184

FEED FROM HES DEV HAS BEEN REJECTED. TRANSLATED FEED IS LOCATED IN AAEX/RECOV SENDER ID IS HES RECEIVER ID IS PEREGRINE



Mail Function Setup Process

14

Bad SQL code while getting application info. SQLCODE = 100 GROUP = SC APPL = MKT SUBSYSTEM = 820 RELEASE = 1.0

The table describes inbound EDI reject message lines: Message Line Example

Explanation

A 820 FEED FROM HES DEV HAS BEEN REJECTED

820 is the document ID. HES is the sender. DEV is the sender division.

THE TRANSLATED FEED IS LOCATED IN AAEX\RECOV

Reject file name.

GS SENDER ID IS HES

Functional group ID of the sender.

GS RECEIVER ID IS INOVIS

Internal ID.

Inbound EDI Test Messages

EDI Representatives receive a test message notification similar to this example when a trading partner sends a test transmission. HES HAS SENT A TEST 820 THE TRANSLATED FEED IS LOCATED INAAEX/TEST/820 GS SENDER ID IS HES GS RECEIVER ID IS INOVIS

The table describes inbound EDI test message lines: Message Line Example

Explanation

HES has sent a test 820

HES is the sender name and 820 is the doc ID.

TRANSLATED FEED IS LOCATED IN AAEX\TEST.820

Name of the file.

GS SENDER ID IS HES

Functional Group ID of the sender.

GS RECEIVER ID IS INOVIS

Internal ID.

Mail Function Setup Process To set up the TrustedLink mail function on your server 1 Confirm that you have access to an SMTP server and that you can send email to the server. 2 Set up a login/mail account on your SMTP server for your EDI Administrator. 3 Set the translation system administrator email ID using the TL Configuration Tool.

Viewing Contact Email Addresses This section describes how to view email addresses of your contacts, including EDI Representatives. The Contact Management, Contact List tab, specifies the email address for contacts and enables email to be sent from the translators to reach the contacts. See also “Inbound EDI Recovery Messages” on page 184.


185


Viewing Contact Email Addresses

To view a contact email address 1 Click Contacts or select View > Contacts.

The Contacts Management window, Contact List tab, opens. 2 Select the contact name in the list, then see the Email Address field. This value must be a

valid email address. For example, [email protected].

186


Error Recovery and Logging

T

15


■

“Inbound Error Recovery (IER)” on page 187

■

“Inbound Extended Error Logging (IEL)” on page 189

■

“Outbound Error Recovery (OER)” on page 190

■

“Outbound Extended Error Logging (OEL)” on page 191

Inbound Error Recovery (IER) This section explains how the inbound error recovery program functions. The inbound error recovery program recovers rejected data from the inbound translator program; it does not recover rejected data from the edixssti program. The inbound translator program places rejected files in the recovery directory and the edixssti program places rejected files in the reject file of the working directory. During inbound translation, the inbound translator program may reject an interchange. The EDI Representative can view the error message in the Operations Center Client Error Log List window. Translation Process

During inbound translation, the translator saves all the segments of an interchange. If a rejection occurs, the translator can obtain the segments to write a recovery file. The translator uses memory to store the interchange segments. If the memory usage goes beyond a specific amount (default memory threshold (8 MB) or the value indicated in the RECOV_MEM_THRESHOLD parameter), the translator copies all the data to a temporary storage file called tprecov. The translator continues to store the data on the disk until it completes the translation of one interchange. The translator then determines if rejections have occurred, and creates the recovery file, if rejections are indicated. Interchange Rejection

The PARTIAL_ACCEPTS parameter controls the translator’s level of interchange rejection. Interchange can be entirely or partially rejected. The PARTIAL_ACCEPTS registry value can be set to: ■

NO

■

YES

If the partial accept parameter is turned off (PARTIAL_ACCEPTS=NO) in the inbound translator program, the entire interchange is rejected and written to a recovery file.

187

E RRO R R E C OVE R Y A N D L OG G I N G

Inbound Error Recovery (IER)

If partial accept processing is turned on (PARTIAL_ACCEPTS=YES) in the inbound translator program, the translator looks for information that indicates the level at which it can reject an interchange. The levels available are listed in the table: If the partial accept level is...

Then the entire...

Interchange

Interchange is written to one recovery file.

Functional Group

Rejected functional group is written to one recovery file.

Document

Rejected transaction set is written to one recovery file.

If part of an interchange is rejected, the translator creates a recovery file containing partial data. Since partial data can be confused with a trading partner’s entire transmission feed, the translator separates them by putting the partial data into specially created interchange and FG header and trailer segments. The actual document to be recovered is located between the FG header and FG trailer segments. Important: If a rejection occurs for a TRADACOMS or EIAJ Standard, the translator writes the entire interchange to the recovery file including the original envelope segments.

Recovery File

The inbound translator writes the rejected data to the recovery file you set up in the RECOV_HIQ parameter. The recovery file is recov_hiq\xlate.key.date.time Parameter

Description

recov_hiq

Path name you indicated in the RECOV_HIQ parameter. Maximum 60 characters

xlate_key

Translator Event Name

date

Date the rejection occurred

time

Time the rejection occurred

Abnormal Termination

If the translator initiates abnormal termination, all errors logged prior to the error are discarded. Only the error causing the termination is logged so the translator does not log incomplete control numbers. Additionally, no recovery file is available in a translator-initiated abnormal termination. Recovery Mode

The inbound translator gets the OK to attempt recovery of inbound translator rejects when the EDI Rep selects the Marked for Recover check box on the Operations Center Error Properties window, General tab. When the translator runs in recovery mode (MODE=RECOVERY), it collects all the files for the error entries that have the Marked for Recover check box selected on the Operations Center Error Properties window, General tab. The translator then looks for errors that have an Open status and have been marked for recovery.

188

■

If another reject occurs, the translator does not log a new error entry to the Error Log. Instead, it adds the new errors to the same error entry.

■

The translator does not log control numbers on a recovery run.

■

The translator inserts specific values into fields in the Operations Center Error Log List window. When an interchange is successfully recovered, the translator changes the Recover field to Completed and the Status field to Resolved in the Operations Center Error Log List


ERRO R RECOVER Y AN D LOGG IN G

Inbound Extended Error Logging (IEL)

15

window. In addition, if the Status field is Open when the recovery began, the translator inserts a line in the Operations Center Error Properties window, Resolution Text tab to indicate the job name, number, date, and time of the recovery job. ■

The translator uses envelope tables RANSI to retranslate ANSI X12 or TDCC documents or REDIFACT to retranslate EDIFACT documents. All other standards use the same envelope tables as normal processing.

Inbound Extended Error Logging (IEL) The inbound extended error logging routine writes translation errors to the database. The Operations Center Client has access to this database and displays this error message information in its Error Log List window. This setup makes it easy for EDI Representatives to use the error list to review error messages for their documents. IEL Process

If an Abend, Reject, or Warning message is generated during translation, the generated message and all corresponding fields found in the Error Log reports are inserted into their own fields in the database. Only the error messages and their associated report fields; such as Translator Key, Standard, Sender ID, are logged. Previously recorded informational messages are not written to the database. By having the data elements stored in a database, EDI Reps may sort and filter the errors they see on the Operations Center Error Log List window by using many different viewing criteria. Starting IEL

To start the inbound extended error logging routine, make sure the error logging registry value is set to yes. You can set this registry value in one of the following ways: ■

Run the inbound translator program with option -e.

■

If you run the translator from the Translate window of the Operations Center Client, specify Error Logging before you run it.

Compatibility

Regardless of whether error logging is implemented, the format and content of the ERRLOG file remains the same, which ensures compatibility with any report parsing routines our customer base writes. In addition, this approach allows EDI Reps to have the same standard reports available if and when they want them. Implementing inbound extended error logging decreases throughput by roughly 10%. Actual results may vary site by site. Inbound extended error logging can only be implemented in conjunction with inbound error recovery (IER). The marriage of these two functions allows the IER architecture to have access to error information accessibility in a relational database. IEL is compatible with any mode of partial accept processing or history logging. When operating the translator in inbound error recovery mode, Inbound extended error logging does not try to insert the same errors into the database if recovery is unsuccessful. Instead, IEL appends the new error message to the existing error message text on the Error Log database.


189


Outbound Error Recovery (OER)

You can maintain the inbound extended error logging database via the error log database purge program.

Outbound Error Recovery (OER) The outbound error recovery program recovers rejects from the outbound translator program. It does not recover rejects from the edicnvrt program. Note: The outbound translator program produces its rejects to the recovery directory.

When the translator rejects outbound transmission information for a trading partner, it looks at the outbound translator program for specific instructions about what to do with the reject information. OER Process

After outbound error recovery records all errors to the database, the EDI Rep who is responsible for the trading partner’s outbound documents can view the errors, mark them for recovery, and comment on them. The EDI Rep uses the Error Management screens to perform these tasks. The Outbound Error Recovery routine is available for Batch or Event Driven processing. When the translator runs in Batch mode (MODE=BATCH), all invalid documents are rejected and written to a file under the path name specified by the RECOV_HIQ parameter. The frontend of the OER process, called extended error recovery, logs available errors into the error_log and error_text tables and leaves the record Open for recovery. When this part of the OER process is running, it updates errors with the appropriate rejected file name that was written to the file specified by the HIQ_RECOV registry value during processing. When the translator runs in DB API Mode (input from the outbound staging (OSD) database), the rejected data is not written to the recovery files. DB API data can be recovered by changing the W in STO_DELETE_BYTE of the OSD to B and resubmitting the outbound translation. Open Error Messages

When the outbound error recovery routine creates open error records, the Error Management database makes them available for viewing on the Operations Center Error Log List window. EDI Reps, using the error log list, can look at open errors involving the trading partner documents. An EDI Rep can mark the error for recovery by selecting the Marked for Recover check box on the Operations Center Error Properties window, General tab. RECOVERY Mode

When the translator runs in recovery mode (MODE=RECOVERY), the edicnvrt portion of the TL Services process locates the recovery data an EDI Rep has marked for recovery. The TL Services

190


ERRO R RECOVER Y AN D LOGG IN G

Outbound Extended Error Logging (OEL)

15

process sends the data to the outbound translator program. The program uses one of these methods for reprocessing: If the output is...

Then the translator...

Valid

Converts all outgoing data into EDI documents. It changes the value from Open to Resolved in the Status field in the Operations Center Error Log List window. It then adds resolution text in the Error Properties window, Resolution Text tab edit field, indicating the successful recovery of the data.

Invalid

Rejects the data again. An invalid response can reoccur when the rejection actually occurs before the correction. If the translator is running in recovery mode, it adds the new error to the original entry rather than create a new entry.

After rejecting the data, the translator increments the recovery attempt count of the error record in the Operations Center. The EDI Rep gets a second error message about the rejected data, indicating another error has occurred. The translator then adds new error information to the Operations Center Error Log List window. The EDI Rep corrects the new error and marks it for recovery on the Error Properties window, General tab. The translator can now reprocess the errors in recovery mode as valid input.

Outbound Extended Error Logging (OEL) The outbound extended error logging routine writes translation errors to a database. The Operations Center Client has access to this database and displays error message information in its Error Log List window. This setup makes it easy for EDI Reps to use the error list to review error messages for their documents. Starting OEL

Make sure you set the error logging registry value is set to yes, in one of the following ways to start the outbound extended error logging routine. ■

Run outbound translator program with option -e.

■

If you run the translator from the Translate window of the Operations Center Client, specify Error Logging before you run it.

OEL Process

If an Abend, Reject or Warning message is generated during translation, the generated message and all corresponding fields found in the ERRLOG file are inserted into their own fields in the database. Only the error messages and their associated report fields, such as Translator Key, Standard, Sender ID, are logged. Previously recorded informational messages are not written to the database. By having the data elements stored in a database, EDI Reps may sort and filter the errors they see on the Error Management screens by using many different viewing criteria. Backwards Compatibility

Regardless of whether or not Extended Error Logging is implemented, the format and content of the ERRLOG file remains the same, which ensures compatibility with any report parsing routines written by our customer base. In addition, this approach allows EDI Reps to still have the same standard reports available if and when they want them.


191


Outbound Extended Error Logging (OEL)

We have estimated that implementing Outbound Extended Error Logging decreases throughput by roughly 10%. Actual results may vary site by site. Outbound extended error logging may be implemented only in conjunction with outbound error recovery (OER). The marriage of these two functions allows OER’s architecture to have error information accessibility in a relational database. OEL is compatible with any mode of partial accept processing or history logging. In Conjunction with IER Operation

When operating the translator in outbound error recovery mode, outbound extended error logging does not try to insert the new errors into the Error Log database if recovery is unsuccessful. Instead, OEL appends the new error message to the existing error message text on the Error Log database. See the section: “Outbound Error Recovery (OER)” on page 190, for more information about Outbound Error Recovery. Maintenance

Maintain the outbound extended error logging database via the database error log purge program.

192


Reports and Statistics

T

16


■

“History Feature” on page 193

■

“Reconciling a Transmission” on page 195

■

“Viewing Manual Reconciliation Messages” on page 196

■

“Viewing Delinquent Real-time FA Information” on page 197

■

“Data Banking” on page 198

■

“Statistics” on page 201

■

“Specifying Search Criteria for Business Document Statistics” on page 202

■

“Specifying Search Criteria for Event Statistics” on page 204

History Feature This section describes the History feature in the Operations Center Client. The Operations Center Client tracks the history of all transmissions and transaction documents exchanged between your company and your trading partners. Transmissions are the exchange of data between your company and a trading partner and can include any number of uniquely numbered transactions. History features available include: ■

“Transaction Numbers” on page 193

■

“Document Numbers” on page 193

■

“Viewing History” on page 194

Transaction Numbers

Documents are sent as transactions; each transaction is assigned a transaction number representing the sequential order of the documents sent within that transmission. Example: If you send 10 purchase orders in a transmission, the transaction numbers are 1 through 10. The document number is the actual number of each purchase order. Document Numbers

The document number is the number of the document exchanged. This could be the invoice number or the purchase order number, for example. A transaction can have a second document number. The secondary document number references a prior, related document number.

193

REPORTS AND STATISTICS

Opening the History Window

Example: The primary document number for an invoice is the invoice number, and the secondary document number might be the purchase order number. When searching by document number, you should always search by the primary document number. Viewing History

You can specify criteria to search for history data in the History window. You can perform different searches by completing information in the three tabs: ■

Transmissions

■

Transactions

■

Document Number

Opening the History Window To open the History window 1 Click History.

The History dialog opens displaying the Transmissions tab.

Viewing History To view history about a trading partner, transmission, or transaction 1 Click History. 2 Select a trading partner by:

194

■

Typing the name

■

Selecting a name from the list



Reconciling a Transmission

■

16

Typing the Trading Partner Key and then clicking Search

3 Define your search criteria on any of the three tabs: Transmissions, Transactions, or

Document Number. Important: For Transmission search only: If you perform a Transmission search and select All Trading Partners, the search only looks for items on a single day. Specify the day in the Date Range Starting field. You cannot perform this search for a date range. 4 Click Search.

A dialog opens the search results. 5 If you performed a transmissions search, you can also search for the associated

transactions or document numbers: ■

To search for transactions, right-click the transmission and select Transaction.

■

To search for document numbers, right-click the transmission and select Primary Document History or Secondary Document History. The options available will depend on the transmission.

6 If you performed a transactions search, you can also view EDI standards data for the

transaction if the event is set up for data banking: a Select a transaction result displaying Y in the Banked column. b Right-click the transaction and select Transaction Data.

Reconciling a Transmission This section describes the procedure for reconciling a transmission. You can reconcile a transmission from the Transmissions search results window. To manually reconcile a transmission 1 Click History.

The History dialog opens displaying the Transmissions tab.

2 Select the search criteria and click Search.


195


Viewing Manual Reconciliation Messages

Search results appear in the History-Transmissions window. Each row contains a transmission, and the transmission date which lists transmissions in rows and transmission in numerous columns across the page. 3 Select the transmission you want to reconcile. If the Ack Status is listed as Waiting, the

transmission can be reconciled. 4 Right-click the transmission and select Reconcile, or select History > Reconcile.

The Message dialog opens.

5 Enter reconcile information in the lines on the Message dialog. These rules apply: ■

Lines 1 and 2 accept up to 40 characters.

■

Line 3 accepts 30 characters.

6 Click OK.

The Ack Status column displays Reconciled and the Message column indicates Yes for the transmission.

Viewing Manual Reconciliation Messages To view a transmission message 1 Click History.

The History dialog opens displaying the Transmissions tab. 2 Select the search criteria and click Search.

Search results display in the History-Transmissions window. 3 Select a message to view. You can select transmissions that display Reconciled or Waiting

in the Ack Status column. 4 Right-click the transmission and select Message, or select History > Message.

196



Viewing Delinquent Real-time FA Information

16

The Message dialog opens.

Viewing Delinquent Real-time FA Information Use the following procedure to view a transaction’s real-time delinquent FA date and whether or not a delinquent FA notification has been sent. To view real-time delinquent FA information 1 Click History.

The History dialog opens displaying the Transmissions tab. 2 Select a trading partner from the list. 3 Click the Transactions tab. 4 Make selections to search by transaction. 5 Click Search in the Transactions tab.

The History-Transactions window displays search results. 6 Click the transaction row to highlight it, then use the horizontal scroll bar to find the

following column headers: ■

FA Delinq Date—Date and time that TLE will consider the FA delinquent.

■

FA Delinq Notified—Date and time that TLE sent a delinquent FA notification to appropriate EDI Reps and Contacts. Blank means no notification has been sent.

Note:

These two columns apply only to real-time FAs. They are not used for batch FAs.

See the graphic below for an example of a delinquent inbound real-time FA:


197


Data Banking

Data Banking Data Banking lets you store the entire EDI form of a document translated by TrustedLink. Note that using this feature can quickly consume database resources, so you might wish to purge the data bank on a different schedule than you purge the transmission history. See “Purging Banked Data” on page 200 to enable or disable Data Banking for an event. For an inbound translation, the pre-translation document is banked; for an outbound translation, the post-translation document is banked. You can also view groups of data based on specific criteria. Before you can bank a document, you must have the history logging feature enabled. Data banking can be applied in either Test or Production mode. Selecting Data Banking

You can select data banking in the Event Wizard-Event Details window or the Data Banking/Select Events window. To enable data banking from the Event Wizard, click Additional Options, then select Data Banking from the Event Wizard-Event Details window when you are adding or updating an event associated with an EDI document.

Click Additional Options, then select Data Banking

You can also select data banking for Event in the Data Banking/Select Events window. See “Viewing Banked Data” on page 198. Viewing Banked Data

You can use the Data Banking/Select Events window to set the Data Banking criteria for groups of Events associated with EDI documents. For example, you might want to enable Data Banking on all Events for a new trading partner, or all purchase order response documents. You can then view your grouped data on the Events log that opens alongside the Select Event window.

198



Data Banking

16

To set the viewing criteria for Data Banking 1 Select Options, Data Banking and then Events.

The Select Events dialog appears along with the Events log.

2 Use the Select Events window to set display criteria for the Events window: Criterion

Description

All Data Banking-Enabled Events

Select this check box to show only events that have data banking turned on. Enabling this check box disables all other search options on this dialog, except direction.

By Trading Partner

Select the trading partner key. The Events window displays only events for the selected trading partner.

By Internal ID

Select the Internal ID. The Events window displays only events for the selected internal ID.

By Document ID

Select the document ID. The Events window displays only events for the selected document ID.

Direction

Select the direction for Events you want to view in the Events window. Both is the default.

3 Click OK.


199


Data Banking

The Events log displays events that match the criteria you selected..

4 To enable or disable data banking, right-click an event and select Toggle Databanking.

Purging Banked Data

Inovis recommends that most users purge data banks more frequently than transmission histories because data banking quickly consumes a large amount of database space. If you do not use the Purging Banked Data procedure below, the data bank will be purged on the same schedule as the transmission history. Use the procedure below to set the default amount of time to retain banked data. To override that value, use the -b dbnk_count option when running the History Purge (edidbhpg) program. See edidbhpg in the “Maintenance Routines” chapter of the TrustedLink Enterprise System Reference Guide. To set purge criteria 1 Select Options > Data Banking > Retention.

The Data Banking Retention dialog opens. 2 Type a value in the Duration field.

This value defines the default amount of time to retain banked data. The time is measured in either cycles (batch processing runs of the History Purge program edidbhpg) or days (real-time processing). The default setting is cycles. You must use days for real-time processing (see step 3). For example, 5 specifies that banked data will be purged five cycles or days after the transmission date. 3 (Real-time processing) To use days as the Duration setting, you must use the -d option

when running the History Purge program (edidbhpg). See edidbhpg in the “Maintenance Routines” chapter of the TrustedLink Enterprise System Reference Guide. 4 Click OK.

The data banking purge criteria has been set.

200



Statistics

16

Viewing Data Banking from the History Window To view banked data from the History window 1 From the Operations Center Client, click History. 2 Select a trading partner from the list. 3 Select the Transactions tab. 4 Make selections to search by transaction. 5 Click Search in the Transactions tab.

The History-Transactions window displays search results. 6 Click the transaction you want to view. 7 Right-click the transaction and select Transaction Data, or double-click the transaction.

The Transaction Data dialog opens.

Statistics The Statistics feature uses Microsoft Excel to create a bar chart of your EDI data. After your data is incorporated into an Excel spreadsheet, you can change the display criteria. For example, you can change the graph from a bar chart to a pie chart. Additionally, you can perform any Excel function using the data TrustedLink Enterprise generated. Here are some basic rules about statistics. ■

If you do not have Microsoft Excel 5.0 or higher installed on your computer, the statistics feature will not operate. You will receive an error message when you try to access the feature.

■

You will need at least 30 days of data to create useful representations of your EDI transactions.

■

Once you specify the data that you want to use for your graph, it may take a few minutes to display. The length of time depends on the size of your database and the computer environment Operations Center is running on.


201


Specifying Search Criteria for Business Document Statistics

Viewing Statistics To view statistics 1 Click Statistics.

The Select Statistics dialog opens.

2 Select the type of statistics you want to view. Field

Description

Business Document

Use this graph to see information about one or more trading partners’ business document activity by months, quarters, or years.

Event

Use this graph to see information about all event activity by months, quarters, or years.

3 Perform the appropriate action: If you selected...

Then...

Business Document

Proceed to “Specifying Search Criteria for Business Document Statistics” on page 202.

Event

Proceed to “Specifying Search Criteria for Event Statistics” on page 204.

Specifying Search Criteria for Business Document Statistics To specify search criteria for business document statistics 1 Click Statistics.


2 Select Business Document. 3 Click OK.

202



Specifying Search Criteria for Business Document Statistics

16

The Business Document Statistics Selection dialog opens.

4 Define your selection criteria: Option

Description

Monthly

Shows data on a month-to-month basis for the past 36 months.

Quarterly

Shows data in quarterly columns for the past 12 quarters.

Yearly

Shows data in yearly columns for the past three years.

Trading Partner

Select All trading partners (default) or Selected to choose from list.

Selected

Select specific trading partners in the list.

Application Business Group

Select the business group for the application(s). Select All to search all Business Groups.

Document ID

Select the code that uniquely identifies the transaction set or document. Select All to search all Document IDs.

Direction

Select the direction(s) you want to include in the statistics information. You can select one or both directions:

Status

■

Inbound—Indicates events sent by a trading partner.

■

Outbound—Indicates events sent to a trading partner.

Status of the event, either Production or Test.

5 Click OK.


203


Specifying Search Criteria for Event Statistics

If information matching the criteria is found, a Microsoft Excel spreadsheet opens and displays a bar chart with the statistics information generated.

Specifying Search Criteria for Event Statistics To specify search criteria for Event statistics 1 Click Statistics.


2 Select Event and click OK.

The EDI Event Statistics Selection dialog opens.

204




16

3 Define your selection criteria: Field

Description

Monthly

Shows data on a month-to-month basis for the past 36 months.

Quarterly

Shows data in quarterly columns for the past 12 quarters.

Yearly

Shows data in yearly columns for the past three years.

Application Business Group

Select the business group for the application(s). Select All to search all Business Groups.

Document Standard

Select the EDI standard. Select All to search by all standards.

Document ID

Select the code that uniquely identifies the transaction set or document. Select All to search all Document IDs.

Direction

Select the direction(s) you want to include in the statistics information. You can select one or both directions:

Status

■

Inbound—Indicates Events sent by a trading partner.

■

Outbound—Indicates Events sent to a trading partner.

Status of the Event, either Production or Test.

4 Click OK.

If information matching the criteria is found, a Microsoft Excel spreadsheet opens and displays a bar chart with the statistics information generated.


205



206


System Administrator

T

17

he System Administrator menu in the Operations Center provides access to the following functions:

■

“Accessing the System Administrator Menu” on page 207

■

“Mailbox and Inbound Passwords” on page 208

■

“System Administrator Password” on page 210

■

“Optional Compliance Checking” on page 211

■

“TL Services” on page 214

■

“OnRamp Profile” on page 215

■

“User Profiles and Browser Access” on page 215

Accessing the System Administrator Menu To access the System Administrator menu function 1 Click System Administrator or click View > System Administrator.

The System Administrator Password dialog opens. 2 Type your System Administrator password and click OK.

The System Administrator menu dialog opens.

3 Click a function option and continue working:

207

SYSTEM ADMINISTRATOR

Mailbox and Inbound Passwords

■

“Mailbox and Inbound Passwords” on page 208

■

“System Administrator Password” on page 210

■

“Optional Compliance Checking” on page 211

■

“TL Services” on page 214

■

“OnRamp Profile” on page 215

■

“User Profiles and Browser Access” on page 215

Mailbox and Inbound Passwords You can set your password and password expiration options by using either the command line interface or the Operations Center Client. This section describes the procedure using the Operations Center. Operations Center controls password reuse. For security measures, Operations Center does not reuse the last three passwords. To set or modify mailbox passwords 1 From the System Administrator menu, click Mailbox / Inbound Passwords.

The Set Passwords dialog opens. The Set Passwords dialog displays a list of communications providers and their respective mailboxes, user IDs, and inbound user IDs.


To view passwords, select a provider and click View Passwords.

See “View Mailbox Passwords” on page 209. ■

To define a password, select a provider and click either Set Mailbox Password or Set Inbound Password.

See “Set Mailbox Password and Inbound Password” on page 209.

208



Mailbox and Inbound Passwords

17

View Mailbox Passwords To view the password for a specific mailbox 1 From the System Administrator menu, click Mailbox / Inbound Passwords.

The Set Passwords dialog opens. 2 Select the provider and click View Password.

The Mailbox Passwords dialog opens.

3 Click Close when finished.

Set Mailbox Password and Inbound Password To set or change the mailbox or inbound passwords 1 From the System Administrator menu, click Mailbox / Inbound Passwords

The Set Passwords dialog opens. 2 Select the provider and click one of these options: ■

Set Mailbox Password

■

Set Inbound Password

The Set Mailbox Password dialog opens.

3 Type information in these fields: Field

Description

Old Password

Type the previous password, up to nine characters (System Adm. determines minimum length). If you are setting a new password, this field does not display.

New Password

Type the new password up to nine characters (System Adm. determines the minimum length).

Confirm New Password

Type the password again to confirm.


209


System Administrator Password

Field

Description

Password Expiration

Select Yes if you want the password to expire in a specified number of days. If you do not want the password to expire, select No.

Days until Password Expires

Type the number of days you want the new password to be valid, up to 19 characters. If you selected No for Password Expiration, this field is disabled.

4 Click OK.

System Administrator Password The following rules apply to System Administrator passwords: ■

This password is required to access the System Administrator and Set Mailbox Password dialogs.

■

The password remains in effect until the Administrator modifies it.

■

The initial default value is 12345678.

■

Operations Center controls password reuse. For security measures, Operations Center does not reuse the last three passwords used.

To set the system administrator password 1 From the System Administrator menu, click Mailbox / Inbound Passwords

The Set System Administrator Password dialog opens.

2 Type information in these fields: In this field…

Do this…

New Password

Type a new password. Maximum 11 alphanumeric characters.

Confirm New Password

Type the new password again to verify it.

Minimum Password Length

Type the minimum number of alphanumeric characters (1 to 11) required for a password.

Password Expiration

Specify whether you want password expiration on (Yes) or off (No).

Days Until Password Expires

If you selected Yes to turn on password expiration, designate how many days can lapse before the password expires.

3 Click OK, then click Close.

210




17

Optional Compliance Checking The following section describes the Optional Compliance Checking (OCCHECK) feature. This feature is useful when you need to temporarily override validation when performing testing. TrustedLink performs standards compliance checks before translating: ■

Outbound data into EDI format

■

Inbound data into application formats

When a standards error is detected, Translator issues a reject message and terminates the process. When compliance checking locates non-compliant data, it discontinues document processing. You can override the process in some cases with the Optional Compliance Checking feature. You receive warnings when certain errors occur, but the translation process continues. Error Code Profiles

You can use the default error code profile or create a new one. There are two default error profiles: ■

Default_in—Error types that TrustedLink regularly rejects for incoming documents.

■

Default_out—Error types that TrustedLink regularly rejects for outgoing documents.

If you do not want to include all of the default errors within your optional compliance check, the Administrator can create new profiles do so. A new profile must specify error types to be included in the Default_in or Default_out profiles. Creating Optional Compliance Profiles To create an optional compliance profile 1 From the System Administrator menu, click Optional Compliance Checking.

The Compliance Profile dialog opens.

2 Click New.


211



The New Profile dialog opens.

3 Enter your optional profile name. Important: Do not type a path name. TrustedLink sends this profile name to the

Operations Center database, not to a file. 4 Select either Inbound or Outbound for this new profile, and click OK.

The Compliance Profile dialog opens displaying your new profile in the pull-down menu. 5 Move either the inbound or outbound error types that you do not want to use from the

Selected list to the Available list. See “Inbound Error Codes” on page 212 for error descriptions. 6 Click OK to return to the System Administrator dialog, then click Close.

The new profile appears on the Translate Options dialog when you initiate a translation. Inbound Error Codes

212

Inbound Error Number

Type of Error

149, 150, 151, 152, 153, 154

Duplicate Control Number

161, 162, 163, 164, 165, 166, 566, 567, 568, 569, 570, 571, 572

Control Number not consecutive or does not match format

231

Missing first segment of new loop

328, 329, 339, 341, 533

Missing beginning ending segment of LS/LE Loop

352, 353, 354, 357

Invalid date for DATE element

355, 356, 358, 359, 360

Invalid time for DATE/TIME element

500, 501

Invalid ID Code

502, 506, 507

Missing mandatory sub field/element

503

Missing mandatory field/element

504, 505, 506, 507, 508

MIN/MAX field length error

505, 555

Missing conditionally mandatory field/element

509, 511, 514

Segment exceeded maximum number of repetitions

510

Missing mandatory segment

512, 513, 524-527

Segment Hierarchy error

528, 573

Unexpected element(s)




17

Outbound Error Codes Outbound Error Number

Error Type

208

Missing conditionally mandatory field/element

209, 210, 215

Missing mandatory segment

211

File identifier not found

212, 213

Segment hierarchy error

214

Loop repeated beyond the limit defined in the standards table

216, 217

Missing mandatory element/sub-element

226

Partial feed

228, 229

Error in writing functional acknowledgment

230

Loop level of the segment is not greater than the previous loop level

Implementing Optional Compliance Checking To implement optional compliance checking 1 Click Browser.

The browser you selected in the Operations Center for viewing files opens.

2 Select a file, right-click, and select Translate....


213


TL Services

The Translation Options dialog opens.

3 Select Compliance Override Profile in the Optional Parameters area.

A list of profile names appear in the dropdown. 4 Select the profile name to use for Optional Compliance Checking. 5 Complete the selections on the Translate Options dialog and click OK.

TL Services In the TrustedLink TL Services Connection Information window you can adjust the connection timeout setting. To change the timeout setting for the TL Services connection 1 From the System Administrator menu, click System Administrator.

214



OnRamp Profile

17

The TL Services dialog opens.

2 For Timeout, type the number of seconds or use the up/down arrows to the appropriate

value. 3 Click OK.

OnRamp Profile TrustedLink OnRamp is a feature you can use to exchange data with Inovisworks, TrustedLink’s electronic commerce portal. You also use OnRamp to request TL Services. Settings can be changed using the System Administrator dialog. Changing TL Services Settings—OnRamp was enabled when TrustedLink version 6.1 was installed on your system. During installation, you were prompted for a server name and a port number to enable the TL Service feature. For more information about creating or maintaining an OnRamp profile, see the TrustedLink Enterprise Gateway Communications User Guide for the OnRamp Configuration instructions.

User Profiles and Browser Access You can add a new user profile or modify the properties of an existing profile. If you modify an existing profile, you cannot modify the User Login name. If you need to modify the User Login name, add a new user profile and delete the existing account. Adding a User Profile and Assigning Browser Access To add a user profile and assign browser access 1 From the System Administrator menu, click User Profiles and Browser Access.


215


User Profiles and Browser Access

The User Properties dialog opens.

2 Select a User or type a new User Login name and provide or modify this information: In this field…

Type or select:

User Login

The secure user login ID. This is the only field that cannot be modified later.

Full Name

A description of the user account.

Password

A password for the user account.

Confirm Password

A confirmation of the password.

Status

Select to enable or disable the user account. Disabled users cannot log into the Operations Center.

Allow user to change password

Select to allow the user to change the account password. The General Configuration window sets the default for this check box.

Force password change on next login

Select to require the user to change the account password on initial login. The General Configuration window sets the default for this check box. The Allow user to change password option must be selected with this option.

Days until password expires

Decide how long a password is effective.

3 Click OK, then click OK on the User Properties window.

216


Miscellaneous Functions

A

18

dditional functions that can be performed in the Operations Center include the following:

■

“Setting the Mapping Tools Paths” on page 217

■

“Translation Table Transfer” on page 218

Setting the Mapping Tools Paths To launch the Mapping Workbench and Mapper from Operations Center using the toolbar, you must set the path. After setting the path, the Upload and Download Translation Tables buttons becomes active. Use these instructions to set the mapping tools paths: ■

“Setting the Mapping Workbench Path” on page 217

■

“Setting the Mapper Path” on page 217

Setting the Mapping Workbench Path To set the TrustedLink Mapping Workbench path 1 Select Options > Set Workbench Path.

The Set Workbench Path dialog opens.


Click Browse and navigate to the Mapping Workbench installation directory and select the Workbench executable file, WB.exe.

■

Type the path for your installed version of TrustedLink Mapping Workbench.

3 Click OK.

Setting the Mapper Path To set the Mapper path 1 Select Options > Set Mapper Path.

217

MISCELLANEOUS FUNCTIONS

Translation Table Transfer

The Set Mapper Path dialog opens.

2 Type the path for your installed version of Mapper or click Browse to select the path. 3 Click OK.

Translation Table Transfer Before you upload or download translation tables, the path to your installed version of the Workbench or Mapper must be set in the Operations Center. See “Setting the Mapping Tools Paths” on page 217. These conditions must be met before you upload your translation tables from Mapping Workbench: ■

Only a map that has been exported can be uploaded. Translation tables are created during the export process in the Workbench.

■

The path to your installed version of TrustedLink Workbench must be set. be set on the Operations Center. Talk to your system administrator if you are unsure of this.

Mapper maps do not need to be uploaded to be saved. They are saved in Mapper in the proper name format. They are then eligible to be uploaded to the server. To upload or download translation tables, see: ■

“Uploading Translation Tables” on page 218

■

“Downloading Translation Tables” on page 219

Uploading Translation Tables

The last task to complete before translation is transferring the translation tables to your host EDI platform where the translation tables are stored and accessed by Translator to translate the inbound or outbound document. To upload translation tables 1 Click Upload Translation Tables.

218




18

The Upload TrustedLink Workbench Tables dialog opens.

Exported Workbench maps and saved Mapper maps (matching the proper naming format) are displayed for upload. 2 Select the event. 3 Click OK.

The tables for the selected event are uploaded to the server. Downloading Translation Tables

During map download, maps are downloaded from the TrustedLink Enterprise server to the Mapping Workbench xlate directory. If the exported maps exist in Mapping Workbench or Mapper, they are overwritten by the downloaded maps. To download translation tables 1 Click Download Translation Tables.

The Download Mapping Tables dialog opens.

The dialog shows maps on the TrustedLink Enterprise server instance where the Operations Center Client is connected. 2 Select the event. 3 Click OK.

The tables for the selected event are downloaded from the server.


219



220


Index A abnormal termination, 188 adding external cross-reference, 103 inbound internal cross-reference, 83 interchange references, 62 outbound internal cross-reference, 95, 97 applications copying, 102 cross-references, external, 76–103 cross-references, internal, 76–103 deleting, 102 viewing Contacts for, 50 viewing contacts for, 50 applications, copying, 132, 134 assigning Contacts, 45 assigning EDI Representatives, 45 automatic map versioning, 163

B backwards compatibility, error log, 189 batch scheduling setting up on server, 141 setting up schedule type, 141 batch-scheduled transfers, 138 buttons, 33

C can, 129 checking status, 158 command manager, 154 translation requests, 155 command tracing, 157 commands manually submitting mailbox queue, 138 submitting mailbox queue manually, 138 communications manual file transfer, 159 compliance checking for testing, 211 contact copying, 131 Contact Management window, 40 contacting Inovis Technical Support, 16 Contacts about, 38 assigning, 45 unassigning specific, 46 viewing for application or trading partner, 50 contacts about EDI Representatives, 38

creating from existing, 44 deleting, 51 EDI Representatives, reassigning, 46 editing, 50 email addresses, 185 messages to, 180 notification assignments, 48 viewing, 49 viewing for application or trading partner, 50 Contacts tab, 58 contacts, trading partner, 58 copying applications, 102 applications data, 132, 134 contact, 131 Event Maps, 134 Events, 125 mailbox data, 131 cross-references, external, 76–103 adding, 103 deleting, 103 cross-references, internal, 76–103 deleting, 103 inbound, adding, 83 outbound, adding, 95, 97 customer support, 16

D data banking, 198–201 disabling, 200 enabling, 200 purging banked data, 200 delete input, 157 deleting applications, 102 contacts, 51 Events, 126 external cross-references, 103 interchange references, 72 internal cross-references, 103 trading partners, 72 disabling data banking, 200 schedules, 147 document partial accept level, 188 documentation, 16 documentation, TLE, 16 duration, of scheduled task, 148

E EDI

221

INDEX

envelopes, 119 event details, 109, 117 EDI Administrators message types, 180 EDI Representatives about, 38 assigning, 45 lists of assignments, 50 messages to, 180 unassigning for events, 47 edidbhpg, 179 edidr997, 179 edieprg, 179 editing contact information, 50 edixssti, 179 edixu997, 179 email addresses, viewing, 185 email notifications,FAs, 39 enabling data banking, 200 envelope tables, 189 envelopes, outbound EDI, 119 error logging inbound extended, 189–190 process, 189 starting, 189 setting for, 157 error management outbound error recovery, 190 error recovery inbound, 187 outbound, 190 outbound (OER), 190 errors detection, setting for, 157 rejection, setting for, 156 Event Maps, copying, 134 Events copying, 125 deleting, 126 modifying, 120 Events window, opening, 53 event-scheduled transfers, 137 extended error logging outbound (OEL), 191–192

F FA Delinq Date, 197 FA Delinq Notified, 197 FAs, History updates, 39 filename, 139 files manually transferring, 159 queueing, 158 frequency of scheduled task, 149

222

functional group, partial accept level, 188

H history logging, setting for, 156 History updates, 39 History, updating for FAs, 39 History-Transactions delinquent real-time FAs, 197 FA Delinq Date, 197 FA Delinq Notified, 197

I icons, 33 inbound error recovery, 187 abnormal termination, 188 automatic, 188 error recovery, automatic, 188 extended error logging (IEL), 189–190 backwards compatibility, 189 maintenance, 190 process, 189 starting, 189 recovery file, 188 Inovis Technical Support, contacting, 16 input override file, 157 interchange partial accept setting, 188 interchanges deletion requirement, 73 references, adding, 62 references, deleting, 72 translation rejection and, 187

M mailboxes copying data, 131 scheduled batch, 141 sending files to, 158 submitting queue commands manually, 138 unscheduled batch, 141 maintaining inbound error log, 190 manually submitting commands mailbox queue, 138 manually transferring files, 139 map repository access manager, 164 admin fields, 170 admin tasks, 166 admin window, 170 checking in maps, 175 deleting map releases, 172 dreating map releases, 171 importing third party maps, 174–175


INDEX

installation, 164 op center dir, 165 releases, 165 tl config, 164 tl config setting up through, 167 tl config setup, 167 using in workbench, 172 using manager window, 173 using ops center, 168 version control, 164 viewing ops ctr maps, 168 workbench functions, 166 workbench modify repository events, 174 workbench trunk dir, 165 map versioning, 163 Mapper set path from ops center, 217 setting path for, 217 mapping workbench set path from ops center, 217 messages recovery, 184 reject, 184 test, 185 to contacts, 180 to EDI Administrators, 180 mode, 140 modifying Events, 120 trading partner properties, 71 multiple documents, sending, 98

N navigation, 33 notifications contacts, 48 delinquent real-time FAs, 197

O operations center creating map releases, 171 version control, 165 versioning admin tasks, 166 ops center client components, 19 opening, 29 shortcut to Workbench, 34 translation set up description, 20 ops center command manager queue a file, 138 outbound error recovery, 190 extended error logging (OEL), 191–192 output override filename, 157


P partial accept (error rejection), setting for, 156 partial accept processing, 187 procedures manual transfer commands to the Gateway, 138 queue a file in a mailbox, 138 purging banked data, 200

Q QKey, 139–140 queue file using Ops Center Command Manager, 138 submitting mailbox queue commands manually, 138 queueing files, 158 files using Command Manager, 138

R real-time FAs, delinquent information, 197 reassigning EDI Representatives, 46 trading partner to interchange, 73 recovery file, 188 recovery memory threshhold, 157 recovery message, 184 recovery mode, inbound, 188 recovery, outbound errors, 190 reject message, 184 reject, recovery file, 188 request log, 34

S SAP (special application interface) button for, 34 setting for, 157 schedule creating, 149 deleting, 152 modifying, 152 Schedule Wizard - Duration window, 151 Schedule Wizard - Task Options window, 149–150 Schedule Wizard - When window, 151 Schedule Wizard window, 149 scheduled batch mailbox, 141 Scheduler Wizard button, 34 schedules, 149 Schedules button, 34 scheduling, 143 disabling schedule, 147 duration setting, 148 frequency settings, 149 logging, diagnostic, 144 setting up Scheduler, 144 setup in Ops Center, 145 searching

223

IND E X

by application, 69 by communications, 70 by event, 68 sending files from mailbox, 159 files to a mailbox, 158 multiple documents to a trading partner, 98 setting path, 217 setting up batch scheduling, 141 shortcut to Workbench, 34 solicited transaction, 137 standards compliance check for testing, 211 submitting mailbox queue commands manually, 138 manual commands at command line, 138 Subversion, 163 subversion tag files, 165 trunk files, 165 subversion directory structure, 165

transfers, event-scheduled, 137 Translation, 23 translation process, 187 recovery file, 188 requests, 155 translation services inbound, 179 outbound, 179 translation set up description, 20 translation tables download, 219 upload, 218 Translator envelope tables, 189 error management outbound error recovery, 190 TrustedLink Mapper button, setting, 217 Workbench button, setting, 217 TrustedLink Mapping Workbench, setting path, 217 typographical conventions, 16

T Technical Support, contacting, 16 test message, 185 testing compliance checking, changing, 211 the, 158 third party versioning control, 163 TL Services status, 158 TLE documentation, 16 tle overview gateway, 19 mapping tools, 19 translation process, 19 translation set up, 19 toolbar, 33 trading partners deleting, 72 interchanges adding, 62 deleting, 72 properties, modifying, 71 reassigning to interchange, 73 searching for, 67 viewing Contacts for, 50 viewing contacts for, 50 Trading Partners/Events window, 54 transferring files from mailbox, 159 manually, 139

224

U unassigning EDI Representatives, 47 specific Contacts, 46 unscheduled batch mailbox, 141 updating Events, 120 uploading translation tables, 34

V versioning checking in maps, 175 control, 163 deleting map releases, 172 importing exisiting third party maps, 175 importing new workbench maps, 174 importing third party maps, 174 map, 163 operations center, 165 ops ctr admin tasks, 166 third party components, 163 tl config setup, 167 TLE components, 163 using admin window, 169 using in ops ctr, 168 workbench functions, 166 viewing history, 194 viewing contacts, 49


INDEX

W Window Schedule Wizard, 149 Schedule Wizard - Duration, 151 Schedule Wizard - Task Options, 149–150 Schedule Wizard - When, 151 Workbench setting path for, 217 shortcut to, 34 workbench importing existing maps into repository, 175 importing new maps for repository, 174 importing repository maps into db, 174 importing third party maps to repository, 174 lock-modify-unlock, 166 map repository, 166 modifying repository events, 174 using map repository, 172

X XML, document details, 112


225

INDEX

226


TLE Operations Center User Guide

Recommend Documents