ADVLink for Flat File. Lab Exercises

Transcription

1 ADVLink for Flat File Lab Exercises Version 11.6 May, 2014

2

3 2012 HighJump Software Inc. All Rights Reserved. This document and the software it describes are copyrighted properties of HighJump Software Inc. with all rights reserved. Neither this information nor the software may be copied in whole or in part without the prior written consent of the copyright owner. This document was created in the United States of America. HighJump is a trademark of HighJump Software Inc. All other marks are the property of their respective owners. HighJump Software Inc. warrants the software covered by this document only as stated in a legally binding End User Agreement between a customer and HighJump Software Inc. or one of its current or historic subsidiaries or affiliates. This document is subject to change at the sole discretion of HighJump Software Inc. If this document and the software it describes are being acquired by or for the Federal Government, or by any prime contractor or subcontractor (at any tier) under any prime contract, grant, cooperative agreement, or other transaction agreement with the Federal Government, the following provisions apply: By accepting delivery of this software and information, the Federal Government, prime contractor or subcontractor hereby agrees that this software qualifies as "commercial computer software" within the meaning of the applicable Federal Government procurement or financial assistance regulations. The terms and conditions set forth above shall apply to the Federal Government's use, duplication and disclosure of this document and the software it describes, and shall supersede any conflicting terms and conditions. If these terms and conditions fail to meet the Federal Government's needs or are inconsistent in any respect with Federal law, the Federal Government agrees to return this document and the software it describes, unused, to HighJump Software Inc. Advantage System Administration Table of Contents i

4 Table of Contents Exercise 1: Installation of ADVLink for Flat File... 3 Introduction... 3 Background Information... 3 Activity 1: Installation and activation of the ADVLink for Flat File Application... 4 Exercise 2: Explore the components that make up ADVLink for Flat File.. 12 Introduction Background Information Activity 1: Component 1 The Platform input device Activity 2: Component 2 The Process objects Activity 3: Import a sample file Modify Import Mapping Introduction Background Information Activity 1: Define File Mapping Activity 2: Alter the Database Activity 3: Advantage Link for Flat File Activity 4: Configure Subscribing Application Activity 5: Process Test File Advantage System Administration Table of Contents ii

5 Exercise 1: Installation of ADVLink for Flat File Introduction This exercise consists of the following activities: 1. Installation and activation of the ADVLink for Flat File module Background Information The ADVLink for Flat File application install will setup the necessary components (directories, Process Objects, etc.) to enable the Warehouse Advantage system to import data in the form of flat files from a host system. Exercise 1: Installation of ADVLink for Flat File 3

6 Activity 1: Installation and activation of the ADVLink for Flat File Application From the VLab desktop, use Windows Explorer to locate the installation files. They are found at C: / V11.6 / CD2 / Advantage Link Apps / Flatfile Open the Base Application folder and double-click on FlatFileBaseAppInstall.msi to install the application. Exercise 1: Installation of ADVLink for Flat File 4

7 The destination folder should default to the location shown below. Click Next. Select SQL Server as the database type. Click Next. The Database Server Name should be the machine name of the VLab and the Advantage Application Database name should be AAD. Click Next. Click Install to begin the installation. Click Finish. Prior to running the application, you must import, compile, and activate the application as described in the next steps. Open HighJump Advantage Architect by selecting Start > All Programs > HighJump Software > Advantage Platform > Advantage Architect Unicode. Connect to the Application Repository. Exercise 1: Installation of ADVLink for Flat File 5

8 Enter (local) in the Server Name edit box. Enter REPOS in the Database Name edit box. Select the Use SQL Server Authentication radio button. Open the Training folder on the VLab desktop. Open the Misc folder. Double-click the login.txt file. Use the Architect section of the login.txt file to populate the User Name and Password edit boxes of the Connection dialog. Click the OK button. Type your name in the User Name field and click OK. In Architect, select File > Import > Application. Click the ellipsis ( ) button and browse to the Flat File application folder shown in the following illustration: Exercise 1: Installation of ADVLink for Flat File 6

9 Click OK. Architect displays the import process results in the Output Window. Once the import is successful, click OK. FlatFileADVLink appears in the Repository. Now the application must be compiled and activated. In Architect, select Run > Compile Application. Select FlatFileADVLink from the application drop down list and click Compile. If the compile was successful, the following dialog appears. Click Yes. Exercise 1: Installation of ADVLink for Flat File 7

10 In the dialog box that appears, Uncheck the Use Current Connection checkbox and click OK Change the Database Name to ADV. Use the same login credentials as before and click OK. Exercise 1: Installation of ADVLink for Flat File 8

11 Select AdvLinkFlatFile from the drop down box and click OK. If all went well, the following dialog should indicate that the activation was successful. Click OK. After you import, compile, and activate Advantage Link for Flat File, you must recompile and activate previously activated applications that subscribe to messages published by Advantage Link for Flat File. Perform the following steps to re-compile and activate Warehouse Advantage (WA). In Architect, select Run > Compile Application In the Compile Application dialog box, Click the ellipsis ( ) button and browse to the WA application. Exercise 1: Installation of ADVLink for Flat File 9

12 Click Compile. Once the Compile is complete, click Yes to activate the application. In the Activate Application dialog box, click OK. Change the Database Name to ADV. Use the same login credentials as before and click OK. Exercise 1: Installation of ADVLink for Flat File 10

13 From the drop down list, select WA as the solution name and click OK. If all went well, the following dialog should indicate that the activation was successful. Click OK. Leave Architect open and go on to the next Exercise when you are ready. Exercise 1: Installation of ADVLink for Flat File 11

14 Exercise 2: Explore the components that make up ADVLink for Flat File Introduction Now that you have installed the ADVLink application, use the following procedures to examine its components. This is an important step in helping you understand how the application works as well as for possible troubleshooting. This exercise consists of the following activities: 1. Exploring and configuring the Platform input device 2. Exploring the process objects involved with ADVLink 3. Importing a Sample file. Background Information You will be working with the Vendor Import ADVLink files. It is a simple import involving the import of host data into one table. More complex imports such as items would involve multiple tables. Exercise 2: Explore the components that make up ADVLink for Flat File 12

15 Activity 1: Component 1 The Platform input device. The first step in the process is configuring a device (in this case, a file) to locate the host data file and trigger a process object to perform the import work. Open Windows Explorer (open it within the VLab, NOT from your host computer) Locate the IMPORTS folder within the HighJump Software Directory (HJS). The IMPORTS folder was created when you installed ADVLink for FF. It contains several subfolders that were also installed as part of the HighJump base system. This is the starting point for interfacing a host system using flat files with the HighJump System. Open the VENDOR subfolder. Exercise 2: Explore the components that make up ADVLink for Flat File 13

16 The file called SCAVEND.BASE is a sample file of host data. Nothing will happen to this file until it is renamed SCAVEND.DAT. The HighJump System is configured to look for this.dat file and start the import process. Once that action is taken, the ROLLVEND.BAT file rolls over the.dat file and renames it with a numbered sequence (for example: SCAVEND.001). This creates a backup of the import file as well as prevents the system from continually importing the same file over and over. The VENDOR.ERR file is used to log any errors that may have occurred during the process. So where do you configure the system device to act on these files? Open Advantage Commander a. Login as Administrator / HJSPASS. Spill down File Devices and click on Select Solution Environment. Click on Select a Solution Environment on Server. Exercise 2: Explore the components that make up ADVLink for Flat File 14

17 From the Options that appear, click on Work with Solution Environment [AdvLinkFlatFile]. Once the Solution Environment is selected, click Files under the File Devices menu. Go to page 2 of the list of File Devices and locate Start Vendor Host>Msg-FF. Make note that the ID is FF-VEN. This will be a useful identifier that is visible in the status consoles. Click on the Edit Link for Start Vendor Host>Msg-FF. Here is where you configure the file device to pick up the host file from the IMPORTS folder. Look at the File/Path Name field. This tells the device where to look and the name of the file to import. Notice it is the exact path and file name as the sample file in the IMPORTS folder you looked at earlier. Also notice the Process Object field. This is the name of the process object that is triggered when the SCAVEND.DAT file is detected. This is what does the work of importing the data from the host. Exercise 2: Explore the components that make up ADVLink for Flat File 15

18 In Review: The first step in the process is using Commander to configure a device (in this case, a file) to locate the host data file and trigger a process object to perform the import work. In the next activity, you will locate and analyze the triggered process object called from the device. Exercise 2: Explore the components that make up ADVLink for Flat File 16

19 Activity 2: Component 2 The Process objects. The second step in the import process is the triggered process object used to perform the import work. Open Advantage Architect (REPOS database). Open the FlatFileAdvLink application. And perform a search for the triggered process object configured in the previous exercise (Host>Msg Vendor). Locate and open the Call action that calls the Process Vendor Record PO (line16). This PO processes each vendor record one by one. It parses the record string and populates the vendor fields (line1 and 2). Once the vendor fields are populated, another PO (line 3) is called to insert the data into the GHI tables. Exercise 2: Explore the components that make up ADVLink for Flat File 17

20 Open the field action in line1 of the Process Vendor Record PO (IMP_VND Record). Here is where the detailed mapping of vendor file occurs. The string is parsed into IMP_VND fields. Use Notepad to open the SCAVEND.BASE file that resides in the VENDOR subfolder. The parsing in the field action must match the incoming data string. Note that the first 10 character spaces match the Vendor Code followed by the next 50 spaces for the Vendor name, etc. As a developer, you may have to modify this action to properly parse a host file that contains additional columns of data. Close the field IMP_VND Record. Open line 2 of the Process Vendor Record PO. This process object uses a series of calculate and compare actions to map the IMP fields over to the AL_VND fields (AL stands for Advantage Link). Exercise 2: Explore the components that make up ADVLink for Flat File 18

21 These fields are then used by the PO in line 3 to populate the GHI tables. Open the database action in line 3 of the Process Vendor Record PO (DB!Ins AL_VND). Open the database action in line 3 of the Ins AL_VND PO. Here you can see the query used to insert only the AL fields into the GHI table (t_al_host_vendor_master). Again, as a developer, you may have to modify this query to accommodate a host file that contains additional columns of data. Exercise 2: Explore the components that make up ADVLink for Flat File 19

22 Close all the objects except for the original Host>Msg Vendor process object. For every line (record) in the host data file, the Host>Msg Vendor process object will assign a host group ID (line 13) and perform one import. Once all the records from the host file are parsed and populated in the GHI tables, the process object publishes a message (see lines 23-28). Warehouse Advantage will detect this message (see Message Bus) and trigger a process object to import the data (with similar host group IDs) residing in the GHI tables into the working tables of AAD. In the next activity, you will import a sample file using ADVLink for Flat File. Exercise 2: Explore the components that make up ADVLink for Flat File 20

23 Activity 3: Import a sample file With the Advantage Workflow Engine running, open the Application Status Console. Open Windows Explorer (open it within the VLab, NOT from your host computer) Locate the IMPORTS folder within the HighJump Software Directory (HJS). The IMPORTS folder was created when you installed ADVLink for FF. It contains several subfolders that were also installed as part of the HighJump base system. This is the starting point for interfacing a host system using flat files with the HighJump System. Exercise 2: Explore the components that make up ADVLink for Flat File 21

24 Open the VENDOR subfolder. Right-click on the file called SCAVEND.BASE and select Rename from the menu. Change the name of the file to SCAVEND.dat. The HighJump System is configured to look for this.dat file and start the import process. After a few seconds, the ROLLVEND.BAT file rolls over the.dat file and renames it with a numbered sequence (for example: SCAVEND.001). This creates a backup of the import file as well as prevents the system from continually importing the same file over and over. You should be able to see the activity in the Application Status Console. It is a good idea to leave this open during imports since it is a useful tool to use for troubleshooting. Notice the following in the console screen: a. ADVLINKFLATFILE (process object) started, processed records, and ended. b. WA picked it up and began its import vendors process If any errors occurred, they would show up in yellow or red in the status console. Exercise 2: Explore the components that make up ADVLink for Flat File 22

25 Finally, take a look in the AAD database and take a look at the records you just imported. Open Microsoft SQL Server Management Studio. Execute the following query to look at the GHI table: SELECT * FROM t_al_host_vendor_master Notice the host_group_id column. This same GUID was assigned for each record on the imported file. Execute the following query to look at the GHI table: SELECT * FROM t_vendor Here is the final destination. These are the working tables containing the data that WA will be using. Exercise 2: Explore the components that make up ADVLink for Flat File 23

26 This concludes the import of a sample file. In the next Exercise, you will be given a more complex import to tackle. Leave Advantage Architect open. Exercise 2: Explore the components that make up ADVLink for Flat File 24

27 Modify Import Mapping Introduction The basic understanding of the Advantage Link for Flat File application you established in the prior exercise will now be applied to change the mappings of an import file. This exercise consists of the following activities: 1. Define File Mapping 2. Altering the Database 3. Configure Advantage Link for Flat File Application 4. Configure Supply Chain Advantage (SCA) Application 5. Process Test File Background Information This exercise will use a simulated project scenario to guide you through Advantage Link for Flat File modifications. In this scenario, the workshop phase of your project has established the requirement for the Warehouse Management System (WMS) to hold and report on additional Vendor attributes. The Host system needs to provide the WMS with three new pieces of information: Contact Name Phone This additional information will grant WMS users direct access to vendor contact information and eliminate a lengthy walk to the front office. Vendor discrepancies will now be managed while the truck is unloading at the door. Modify Import Mapping 25

28 Activity 1: Define File Mapping Data mapping is a fundamental step with integrating multiple systems and creating data element interpretations between two distinct data models. During the definition-phase of a project, team members representing the Host and WMS system establish the protocol for importing data into the WMS. Through a full system review, the project team outlines important definitions about data flow. At this time, the system-wide impact of each data element is reviewed. In the end, file field positions, formats, and default values are determined. This important undertaking ensures the accurate flow of data into the WMS system. The resulting file layouts determine specific data mappings for each import (i.e. Purchase Order, Sales Order, Vendor, etc.). In this activity, you will first build an understanding of file layouts and how they are typically documented in the HighJump Advantage Link for Flat File Definitions. Next, you will apply this understanding to the updated Vendor Flat File Definition. Finally, you will review a sample file to ensure the mappings are correct. Understanding File Layouts In the Advantage Link for Flat File Guide the file layout for each supported import includes specific information about fields in the import file. The file layout includes the information presented in the table below. Note that this document in its entirety can be found on the HighJump Document Library site. Review the descriptions of each column name in the following table to establish an understanding of the typical HighJump Advantage Link for Flat File Import File Definitions format used in the for the following section. Column Name Field Name Field Description Required by WA? Updated Field? Default Value Notes Start End Length Format Description The application field name used with HighJump Advantage Link for Flat File. The description of the field. Indicates whether a value is required in this field for a HighJump Warehouse Advantage implementation. Valid values are Required, Optional, Not Used, or N/A. Indicates whether the field value is updated when files with a processing code of Update are processed. If the field is considered an updated field but a value is not provided, the default is used. If a default does not exist, the field is updated with blanks. Indicates the value assumed by the field if no other value is provided. Information about how the field is used by the HighJump application, including valid values. The starting position for the field in the file. The ending position for the field in the file. The length of the field in the file. The data type represented by the field. Modify Import Mapping 26

29 Advantage Link for Flat File Definition An excerpt of the Vendor Import file layout from the HighJump Advantage Link for Flat File Import File Definitions is provided below. Recall that in this exercise your project has established the requirement for the WMS to store additional Vendor attributes. Receivers on the inbound dock need to contact Vendors and storing new contact information in the WMS will allow for more rapid issue resolution. These changes have been appended to the Import File Definitions below in bold red. Use the understanding of the file layout (from the previous section) to review the Vendor Import file definition in the following chart. Review the Vendor Import Flat File Definition and note the new IMP_VND Contact Name field stores the name of the vendor contact. The mapping allocates 40 characters to the new attribute giving it a start position 123 and end position of 162 in the file. Review the Vendor Import Flat File Definition and note the new IMP_VND Phone field stores the phone of the vendor contact. The mapping allocates 30 characters to the new attribute giving it a start position 163 and end position of 192 in the file. Review the Vendor Import Flat File Definition and note the new IMP_VND field stores the of the vendor contact. The mapping allocates 50 characters to the new attribute giving it a start position 193 and end position of 242 in the file. Vendor Import (HighJump Advantage Link for Flat File Import File Definitions) The Vendor Import interface populates vendor information in HighJump Warehouse Advantage. The interface requirements are presented below. If the information contained in a file is for an existing vendor, the information processes as an update. For updates the import must contain values for each field that can be updated. If the field is considered an updated field but a value is not provided, the default is used. If a default does not exist, the field is updated with blanks. See the Updated Field? column in the file layout section to determine the fields that will be updated. Field Name Field Description Required by WA? Updated Field? Default Value Notes Start End Length Format IMP_VND Vendor Code Vendor Code assigned to vendor Required Unique vendor code character IMP_VND Vendor Name Vendor Name Required Y character IMP_VND Inspection Flag Inspection Flag Optional Y NO Information al only. Suggested values are character Modify Import Mapping 27

30 Field Name Field Description Required by WA? Updated Field? Default Value Notes Start End Length Format YES, NO. IMP_VND Ownership Control Ownership Control Optional Y NO Information al only. Suggested values are YES, NO character IMP_VND Audit Percent Str Audit Percentage Optional Y 0 Information al only number IMP_VND VQM Profile Vendor Quality Management Profile Optional Y Information al only character IMP_VND Contact Name Name of Vendor Contact Optional Y New custom attribute character IMP_VND Phone Phone Number Optional Y New custom attribute character IMP_VND Address Optional Y New custom attribute character Review Test File Start and end position in a flat file definition allow for the program to map the data values from the string in the file to processing variables. Reviewing the start and end positions of fields in customer provided test files before processing can save time. If the file has been validated, you can focus troubleshooting effort on the program changes. (Note that methods similar to those outlined in this section can also be used to generate a test file when one is not yet available from the customer.) For this exercise your customer has already updated the Host system and generated a test file. You will review the file to ensure it reflects the agreed upon mappings (that you just reviewed in the prior section). Notepad++ is a text editor and source code editor for Windows. While it can be used for a variety of programming and scripting languages, we will simply use it to confirm the positions presented in the prior section on Advantage Link for Flat File Definition. (Notepad++ is distributed as free software.) Open Notepad++ by selecting Start > All Programs > Notepad++ > Notepad++. In Notepad++ choose the File Open menu. Click the Desktop button on the left pane. Navigate to the Training\AdvLink Flat File\VENDOR folder. Modify Import Mapping 28

31 Click the SCAVEND.CUSTOM file. Click the Open button. Notice the Notepad++ status bar at the bottom of the opened file. The circled section in the graphic below displays the current line ( Ln ), current column ( Col ), and selected number of characters ( Sel ). Manually scrolling through the file with the keyboard arrow keys will change the current line ( Ln ) and column ( Col ) values. (In addition, selecting text within the file by holding the keyboard <Shift> key while using a keyboard arrow key will change the selected text ( Sel ) values. A combination of these actions can be used to validate the positions in the file match the File Definition.) Press <Ctrl Key> + G to launch the Go To dialog. Choosing the Offset radio button and entering the position ( You want to go to ) will navigate the cursor to that position in the current row of the opened file. Close the Go To dialog by selecting the I m going nowhere button. With this basic understanding of the Go To dialog in Notepad++ you can now review the customer provided file and make sure the align with the vendor file definition. Modify Import Mapping 29

32 The first column in the Vendor Import File Definition is the IMP_VND Vendor Code. An excerpt of the mapping is listed below. Field Name Field Description Required by WA? Updated Field? Default Value Notes Start End Length Format IMP_VND Vendor Code Vendor Code assigned to vendor Required Unique vendor code character From Notepad++ in the SCAVEND.CUSTOM file, press the <Ctrl Key> + G to launch the Go To dialog. Confirm the cursor is in the first row of the opened file. Click the Offset radio button. Enter a Go To value of 0 to navigate to the start of position of this file. Click the Go button. The graphic below displays the expect results: current line ( Ln ) 1, current column ( Col ) 1. To the right of this position is the character value of WILLIAMS. This string has with a total length of 8 and is within the allocated length of 10 in the mapping. The next column in the Vendor Import File Definition is the IMP_VND Vendor Name. An excerpt of the mapping is listed below. Field Name IMP_VND Vendor Name Field Description Vendor Name Required by WA? Updated Field? Default Value Notes Start End Length Format Required Y character From Notepad++ in the SCAVEND.CUSTOM file, press the <Ctrl Key> + G to launch the Go To dialog. Modify Import Mapping 30

33 Click the Offset radio button. Enter a Go To value of 10 to navigate end of position of the previous field in the file. Click the Go button. The graphic below displays the expect results: current line ( Ln ) 1, current column ( Col ) 11. To the right of this position is the character value of WILLIAMS INC. This string has with a total length of 12 and is within the allocated length of 50 in the mapping. The next column in the Vendor Import File Definition is the IMP_VND Inspection Flag. An excerpt of the mapping is listed below. Field Name IMP_VND Inspection Flag Field Description Inspection Flag Required by WA? Updated Field? Default Value Optional Y NO Information al only. Suggested values are YES, NO. Notes Start End Length Format character From Notepad++ in the SCAVEND.CUSTOM file, press the <Ctrl Key> + G to launch the Go To dialog. Click the Offset radio button. Enter a Go To value of 60 to navigate to the end of position of the previous field in the file. Click the Go button. The graphic below displays the expect results: current line ( Ln ) 1, current column ( Col ) 61. To the right of this position is the character value of YES. This string has with a total length of 3 and is within the allocated length of 10 in the mapping. Modify Import Mapping 31

34 The next column in the Vendor Import File Definition is the IMP_VND Ownership Control. An excerpt of the mapping is listed below. Field Name IMP_VND Ownership Control Field Description Ownership Control Required by WA? Updated Field? Default Value Optional Y NO Information al only. Suggested values are YES, NO. Notes Start End Length Format character From Notepad++ in the SCAVEND.CUSTOM file, press the <Ctrl Key> + G to launch the Go To dialog. Click the Offset radio button. Enter a Go To value of 70 to navigate to the end of position of the previous field in the file. Click the Go button. The graphic below displays the expect results: current line ( Ln ) 1, current column ( Col ) 71. To the right of this position is the character value of YES. This string has with a total length of 3 and is within the allocated length of 10 in the mapping. Modify Import Mapping 32

35 The next column in the Vendor Import File Definition is the IMP_VND Audit Percent Str. An excerpt of the mapping is listed below. Field Name IMP_VND Audit Percent Str Field Description Audit Percentage Required by WA? Updated Field? Default Value Optional Y 0 Information al only. Notes Start End Length Format number From Notepad++ in the SCAVEND.CUSTOM file, press the <Ctrl Key> + G to launch the Go To dialog. Click the Offset radio button. Enter a Go To value of 80 to navigate to the end of position of the previous field in the file. Click the Go button. The graphic below displays the expect results: current line ( Ln ) 1, current column ( Col ) 81. To the right of this position is the numeric value of 95. This string has with a total length of 2 and is within the allocated length of 12 in the mapping. The next column in the Vendor Import File Definition is the IMP_VND VQM Profile. An excerpt of the mapping is listed below. Field Name IMP_VND VQM Profile Field Description Vendor Quality Management Profile Required by WA? Updated Field? Default Value Optional Y Information al only. Notes Start End Length Format character From Notepad++ in the SCAVEND.CUSTOM file, press the <Ctrl Key> + G to launch the Go To dialog. Click the Offset radio button. Modify Import Mapping 33

36 Enter a Go To value of 92 to navigate to the end of position of the previous field in the file. Click the Go button. The graphic below displays the expect results: current line ( Ln ) 1, current column ( Col ) 93. To the right of this position is the numeric value of PROFILE1. This string has with a total length of 8 and is within the allocated length of 30 in the mapping. The next column in the Vendor Import File Definition is the new IMP_VND Contact Name. An excerpt of the mapping is listed below. Field Name IMP_VND Contact Name Field Description Name of Vendor Contact Required by WA? Updated Field? Default Value Optional Y New custom attribute. Notes Start End Length Format character From Notepad++ in the SCAVEND.CUSTOM file, press the <Ctrl Key> + G to launch the Go To dialog. Click the Offset radio button. Enter a Go To value of 122 to navigate to the end of position of the previous field in the file. Click the Go button. The graphic below displays the expect results: current line ( Ln ) 1, current column ( Col ) 123. To the right of this position is the numeric value of Walter White. This string has with a total length of 8 and is within the allocated length of 40 in the mapping. Modify Import Mapping 34

37 The next column in the Vendor Import File Definition is the new IMP_VND Phone. An excerpt of the mapping is listed below. Field Name IMP_VND Phone Field Description Phone Number Required by WA? Updated Field? Default Value Optional Y New custom attribute. Notes Start End Length Format character From Notepad++ in the SCAVEND.CUSTOM file, press the <Ctrl Key> + G to launch the Go To dialog. Click the Offset radio button. Enter a Go To value of 162 to navigate to the end of position of the previous field in the file. Click the Go button. The graphic below displays the expect results: current line ( Ln ) 1, current column ( Col ) 163. To the right of this position is the numeric value of This string has with a total length of 8 and is within the allocated length of 30 in the mapping. The next column in the Vendor Import File Definition is the new IMP_VND . An excerpt of the mapping is listed below. Modify Import Mapping 35

38 Field Name IMP_VND Field Description Address Required by WA? Updated Field? Default Value Optional Y New custom attribute. Notes Start End Length Format character From Notepad++ in the SCAVEND.CUSTOM file, press the <Ctrl Key> + G to launch the Go To dialog. Click the Offset radio button. Enter a Go To value of 192 to navigate to the end of position of the previous field in the file. Click the Go button. The graphic below displays the expect results: current line ( Ln ) 1, current column ( Col ) 193. To the right of this position is the numeric value of wwhite@williams-inc.com. This string has with a total length of 8 and is within the allocated length of 50 in the mapping. Your preliminary review of the file mapping is complete. When performing the steps outlined in the review you focused on the first line in the file. It is normal to visually confirm alignment of all data for each mapped position across all lines at the same time. The start positions and lengths of the reviewed fields align with the vendor file definition. At this point, no changes need to be made to the file. Note that later testing of the file will verify your visual check is correct. Close the open SCAVEND.CUSTOM file in Notepad++. Modify Import Mapping 36

39 Activity 2: Alter the Database After the file definition activities have been completed, the database tables supporting the specific import in the Warehouse Management System (WMS) need be updated to allow data to flow through the entire import process. Both the Generic Host Interface (GHI) table(s) and Supply Chain Advantage (SCA) working objects must be altered to support the new attributes added to the Vendor import (e.g. Contact Name; Phone; ). The chart below lists the database objects impacted by the changes. Object Name Type Description t_al_host_vendor_master Table Generic Host Interface (GHI) table t_vendor Table Supply Chain Advantage (SCA) working table holding master data v_al_host_vendor_master View Supporting view for interface Note the GHI table names typically start with a t_al_host_ prefix. More information on these tables can be found in the Advantage Application Database (AAD) Data Dictionary on the HighJump Document Library site. The determination of the above objects is normally established through supporting documentation found on the HighJump Document Library site (e.g. HighJump Advantage Link for Flat File Guide; Import File Definitions; Export File Definitions). Additional information can also be obtained through a code read of the application processes and its database objects. Database scripts have been provided to alter the tables for this activity. Completion of this exercise will provide a basis for doing such activities in the future. Perform the following steps to access the scripts and alter these tables. Choose the Start All Programs Microsoft SQL Server 2005 SQL Server Management Studio menu. Type the machine name (HJU-VLAB) of the database server in the Server Name drop-down box. Choose SQL Server Authentication in the Authentication drop down box. Use the SQL Server section of the login.txt file in the folder on the desktop to log in. Click the Connect button. Modify Import Mapping 37

40 Choose the File Open File menu. Click the Desktop button on the left pane. Navigate to the Training\AdvLink Flat File\SQL folder. Click the alter_t_al_host_vendor_master.sql file. Click the Open button. Enter the Password and click the Connect button. Modify Import Mapping 38

41 The system opens the file in a new tab. Choose the Query Execute from the menu. The system alters the t_al_host_vendor_master table definition adding new contact_name, phone, and columns. Choose the File Close menu. Choose the File Open File menu. Click the Desktop button on the left pane. Navigate to the Training\AdvLink Flat File\SQL folder. Click the alter_t_vendor.sql file. Click the Open button. Enter the Password and click the Connect button. The system opens the file in a new tab. Choose the Query Execute menu. The system alters the t_vendor table definition adding new contact_name, phone, and columns. Choose the File Close menu. Modify Import Mapping 39

42 Choose the File Open File menu. Click the Desktop button on the left pane. Navigate to the Training\AdvLink Flat File\SQL folder. Click the alter_v_al_host_vendor_master.sql file. Click the Open button. Enter the Password and click the Connect button. Choose the Query Execute menu. Modify Import Mapping 40

43 The system alters the v_al_host_vendor_master view definition adding new contact_name, phone, and columns. Use the provided script to confirm the database changes have been made to your environment. Choose the File Open File menu. Click the Desktop button on the left pane. Navigate to the Training\AdvLink Flat File\SQL folder. Click the run_confirm_changes.sql file. Click the Open button. Enter the Password and click the Connect button. Choose Query Execute menu. The script results should resemble the following graphic. If the script results differ, revisit the related steps provided in this activity. You have updated the database to support the new file definition. The new contact_name, phone, and columns have been added to the t_al_host_vendor_master, t_vendor, and v_al_host_vendor_master tables. The related applications can now be updated to provide the appropriate values. Choose the File Close menu. Modify Import Mapping 41

44 Activity 3: Advantage Link for Flat File Now that the database has been updated to support the new file definition, your focus can turn to the Vendor triggered process object in the Advantage Link for Flat File solution. This process object transforms the data file, populates the related Generic Host Interface (GHI) tables in the HighJump Advantage Application Database (AAD), and publishes a message so subscribing solutions can process the data into the final destination working tables. In this activity you will complete the following tasks: 1. Identify the Process Object 2. Review the Process Object 3. Configure Advantage Link for Flat File Identify the Process Object Advantage Commander is an administrator's tool used to add and configure devices on HighJump Software solutions. In this case, you are looking up the installed Advantage Link for Flat File solution s triggered file device that imports vendors from the host system. The following steps will assist you in identifying the triggered process object specified in the file device definition. Configuration to account for the new vendor attributes can performed on the triggered process object after this object is determined. Choose the Start All Programs HighJump Software Advantage Platform Advantage Commander. Enter the Username (Administrator) and Password (HJSPASS) to login. Expand Advantage Commander from the main menu. The system displays the menu options for Advantage Commander. The menu options should look like the following graphic. Expand the File Devices node. Click the Select Solution Environment menu. Modify Import Mapping 42

45 Click the Select a Solution Environment on Server [HJU-VLAB] link. (Note that HJU-VLAB is the server name of your training environment.) Click the Work with Solution Environment [AdvLinkFlatFile] link. (This will set a system variable for the session allowing Advantage Commander to return only devices defined within the AdvLinkFlatFile solution.) Click the Files menu in the File Devices node. Advantage Commander lists of all installed file definitions for the AdvLinkFlatFile solution. These configured files will input and output records to and from the HighJump Advantage solution. Find the definition with a Name of Start Vendor Host>Msg-FF and Sub Type is TRIGGER. There are several pages of AdvLinkFlatFile File Devices so you may need to page forward to find this specific definition. Modify Import Mapping 43

46 Click the edit link. The screen should look like the following graphic. The triggered process file definition specifies several attributes to determine how the HighJump Advantage system runs: Process Object; Log Level; File/Path Name; File Format; Poll Rate. (For more information on these triggered process object attributes see HighJump Advantage Commander Help.) In this case, the HighJump Advantage system uses a triggered process file to start a process object to import data into the HighJump Advantage Application Database. When the system polls and finds the file indicated, it runs the corresponding triggered process object. This same process object needs to be updated to handle the new vendor attributes defined in the file mapping and added to the database in the prior activities for this exercise. The Edit/Add Device [Start Vendor Host>Msg-FF] page show us that the Start Vendor Host>Msg-FF triggered file runs the Host>Msg Vendor process object. Your upcoming configuration efforts for this activity will focus on this process object. Close the triggered file by clicking the Cancel button. Modify Import Mapping 44

47 Review the Process Object It is important to have an understanding of the current process before making changes. As you found in the Advantage Commander triggered file definition from the previous task, the Host>Msg Vendor process object imports data from a host file into the Advantage Application Database. When the data is delivered to the system in the form of a flat text file called SCAVEND.DAT, this triggered process reads the %HJSDIR%\imports\VENDOR directory file/path based on a poll rate to see if the VEDNOR.DAT file has been placed in the directory. If this file exists, the process object is triggered to start. Unfamiliarity with the Advantage Link for Flat File application triggered process object can result in missed requirements and the loss of information during the import process. The steps that follow will guide you through the review of the Host>Msg Vendor process object. In Advantage Architect, double-click the FlatFileAdvLink application from the Repository tab. Click the plus sign to expand the Triggered Process Object node. Double-click Host>Msg Vendor to open the definition of the triggered process object. Use the Host>Msg Vendor: Line by Line chart below to review the triggered process object in Advantage Architect. Host>Msg Vendor: Line by Line All of the descriptions below list the line numbers, which refer to the opened Host>Msg Vendor process object. To see any of the following steps in more detail, double-click the line in the process object in your HighJump Advantage Architect. Line(s) Description 1-2 This calculate action sets a log message to say the import has started. Whether these steps passes or fail, it moves to line 3. 3 This action connects to the database. In the database definition, there is information regarding the database name and type of database. If the connection is successful (Pass), the process moves to step number 4. If it is not successful (Fail), the process moves to FAILURE, which in this case is line 29. Modify Import Mapping 45

48 Line(s) Description 4 This calls a process object that queries the t_control table to find and set the corresponding GROUP MAX system parameter. If the record is not found, one is inserted with the specified default value. In this case the maximum number of records to process in a Generic Host Interface group is 10,000. This value gets assigned to the Group Max variable. Whether this step passes or fails, it moves to line 6. 6 The Counter variable to capture the number of records processed per Group is initialized to zero. Whether this step passes or fails, it moves to line 8. 8 The Error Count variable to capture the number of errors processed per Group is initialized to zero. Whether this step passes or fails, it moves to line The Records in Group ID variable to capture the number of inserted records per Group is initialized to zero. Whether this step passes or fails, it moves to line This action executes a function to generate a unique 32 character GUID and stores the value in the Actual Host Group ID variable. Whether this step passes or fails, it moves to line The Msg Host Group ID variable is assign the value of the Actual Host Group ID variable. Whether this step passes or fails, it moves to line This Record action assigns the Msg Host Group ID variable value to the associated SYS_RECORD Text Field. Whether this step passes or fails, it moves to line This action receives one row of data from the flat file and places it into the Record Str variable. If the step passes (fails), the process moves to line 16 (26). 16 This calls a process object that processes the imported vendor records and inserts them into the t_al_host_vendor_master table. If the step passes (fails), the process moves to line 23 (18) Increment the Error Counter variable and send the failed record to the SCAVEND.ERR file. Whether this step passes or fails, it moves to line If the current Records in Group ID variable is less than the systems Group Max variable, this step passes and moves to line 15 and find the next vendor record to process. If the system Group Max variable has been met, this step fails and moves to the next line (24) These lines set the appropriate Message Name and publish the Vendor Msg FFADVLink message. The message includes the current value of the unique Msg Host Group ID field. Whether this step passes or fails, it moves to line If the current Records in Group ID variable is zero, there is nothing to process and this compare action passes and moves to line 32. If the current Records in Group ID variable is not zero, there are records in the last group to publish so the next two lines set the appropriate Message Name, publish the Vendor Msg FFADVLink message, and move to line The LOG FAIL label first disconnects from the database and then sends failed database connection message to the log table in the HighJump Advantage Platform database. Whether these steps passes or fails, it moves to line The DISCONNECT label first disconnects from the database and then runs a rollover execute action for the Vendor import file. If the rollover is successful, it moves to line 36. If the rollover it is unsuccessful, it sends a message to the log table in the HighJump Advantage Platform database and then moves to line 36. Modify Import Mapping 46

49 Line(s) Description The NEXT LOGS label sends the processed/failed record count and import completed messages to the log table in the HighJump Advantage Platform database and then moves to line This return line exits the process object with a PASS. Your review of the code should establish some important details. Advantage Link for Flat File scans the directory folder to see if a SCAVEND.DAT file is present. If a file is found, the Host>Msg Vendor processes the records and inserts them into the corresponding Generic Host Interface (GHI) tables in the HighJump Advantage Application Database (AAD) with a Group ID. The Vendor Msg FFADVLink message with the Group ID gets published for each record group. Once all the records have been processed, an external batch file is called that renames the SCAVEND.DAT file to SCAVEND.001. This rename is performed so the next SCAVEND.DAT file can be placed in that directory without the need for user intervention and to keep a record of the past files for reference. Most of your Advantage Link for Flat File configuration efforts in the next task will focus on the Process Vendor Record (line 16). Configure Advantage Link for Flat File Using your understanding of the requirements and current process from prior tasks, development can now begin. The following steps direct you through the configuration of the vendor import Advantage Link for Flat File triggered process object. Completion of this activity will allow data to be processed from the data file to staging GHI tables. Open the Host>Msg Vendor triggered process object in the FlatFileAdvLink application. Right-mouse-click on the Host>Msg Vendor tab header and select Close All But This. Click once on the Action Name of line 16 (Call Process Vendor Record). Double-click the Action Name column of line 16 (Call Process Vendor Record) to drill into this object. The system opens the definition of the process object as in the graphic below. Modify Import Mapping 47

50 Unfamiliarity with the Process Vendor Record process object can result in missed requirements and the mishandling of information during the import process. Use the Process Vendor Record: Line by Line chart below to review the opened process object in Advantage Architect. Process Vendor Record: Line by Line The following chart provides description of the process. All of the descriptions below list the line numbers, which refer to the opened Process Vendor Record process object in your HighJump Advantage Architect. To see any of the following actions in more detail, double-click the Action Name in the in the process object. Line(s) Description 1 The IMP_VND Record field parses out the Record Str variable and assigns the IMP_VND Record fields values based on the fixed positions in the record. If the step passes (fails), the process moves to line 2 (7). 2 The AL_VND Field Values are assigned the values from the IMP_VND Record field values (determined in the prior step). If the step passes (fails), the process moves to line 3 (7). 3 The AL_VND field values are inserted into the t_al_host_vendor_master table. 4-5 The Records in Group ID and Counter variables are incremented for each successfully processed record. Whether these steps pass or fail, the process moves to line 6. 6 This return line exits the process object with a PASS. 7-8 A data error message is posted to the log table in the HighJump Advantage Platform database. Whether these steps passes or fails, it moves to line 9. Modify Import Mapping 48

51 Line(s) Description 9 This return line exits the process object with a FAIL. Recall that the vendor data file mapping has been updated to store three new attributes in the WMS. Contact Name, , and Phone must be accounted for in lines 1 3 of the Process Vendor Record process object. (See Activity 1: Define File Mapping for more details.) Click once on the Action Name of line 1 (Field IMP_VND Record). Double-click the Action Name column of line 1 (Field IMP_VND Record) to open this object. The IMP_VND Record field parses out the Record Str variable and assigns the IMP_VND Record fields values based on the fixed positions in the record. The new Import Vendor record fields must first be created and then they can be added to the IMP_VND Record definition. The chart below lists the new field and non-defaulted attributes that will be used to create them. Field Name Type Length IMP_VND Contact Name Text 40 IMP_VND Phone Text 30 IMP_VND Text 50 Modify Import Mapping 49

52 Perform the following steps to create new record fields. Choose the Define Field menu option to establish the active object type. Choose the File New menu option. Select field Type of Text. Enter Name of IMP_VND Contact Name, and Length of 40. All other attributes for this field require no input and should use their defaulted values. Choose the File Save menu option. Close the field by clicking the X on the tab. Choose the File New menu option. Modify Import Mapping 50

53 Select field Type of Text. Enter Name of IMP_VND Phone, and Length of 30. All other attributes for this field require no input and should use their defaulted values. Choose the File Save menu option. Close the field by clicking the X on the tab. Choose the File New menu option. Select field Type of Text. Enter Name of IMP_VND , and Length of 50. All other attributes for this field require no input and should use their defaulted values. Modify Import Mapping 51

54 Choose the File Save menu option. Close the field by clicking the X on the tab. The new IMP_VND record fields that you just created now need to be added to the IMP_VND Record definition. Completing these steps will allow the Record Str variable that was populated with data from the import file to be properly parsed out according to this definition. Return to the previously opened IMP_VND Record. Choose the Version Control Check Out menu option. Modify Import Mapping 52

55 Click anywhere on row 6 (IMP_VND VQM Profile) to highlight the line. Click the Insert After button. In the Record Field dialog box, select the IMP_VND Contact Name from the Field Name drop-down list. No other fields require input. Click the OK button. Click the Insert After button. In the Record Field dialog box, select the IMP_VND Phone from the Field Name drop-down list. No other fields require input. Click the OK button. Click the Insert After button. In the Record Field dialog box, select the IMP_VND from the Field Name drop-down list. No other fields require input. Click the OK button. Modify Import Mapping 53

56 Click the Update Length button for the IMP_VND Record to update the position and length for every field in the grid. Notice that the Start and End positions have been modified to reflect the length of each field and the total length of the record is now 242 characters. The finished Record Field should look like the following graphic. Choose the File Save menu option. You have updated IMP_VND Record according to the new data mapping the record. The Record Str variable read from the import file will now be parsed out according to this definition. IMP_VND Contact Name, Phone, and fields will be populated with the provided data. Right-mouse-click on the IMP_VND Record tab header and select Close. Return to the Process Vendor Record process object to continue with your configuration efforts. Click once on the Action Name column of line 2 (Call Set AL_VND Field Values). Double-click the Action Name column of line 2 (Call Set AL_VND Field Values) to open this object. Modify Import Mapping 54

57 The currently open Set AL_VND Fields Values process object uses a series of calculate actions to assign the collection of AL_VND fields the values from the already established IMP_VND Record fields. (Recall that you earlier modified the IMP_VND Record to include the new vendor attributes. This effort allowed the data string from the file to be properly parsed out into the IMP_VND Record fields.) Now in this next segment of configuration, new fields and calculate actions must be created to support the data flow of the new vendor attributes in the Set AL_VND Fields Values process object. The chart below lists attributes that will be used to create the new fields. Name Type Length AL_VND Contact Name Text 40 AL_VND Phone Text 30 AL_VND Text 50 Perform the following steps to create new AL_VND fields. Choose the Define Field menu option to establish the active object type. Choose the File New menu option. Select field Type of Text. Enter Name of AL_VND Contact Name, and Length of 40. All other attributes for this field require no input and should use their defaulted values. Modify Import Mapping 55

58 Choose the File Save menu option. Close the field by clicking the X on the tab. Choose the File New menu option. Select field Type of Text. Enter Name of AL_VND Phone, and Length of 30. All other attributes for this field require no input and should use their defaulted values. Modify Import Mapping 56

59 Choose the File Save menu option. Close the field by clicking the X on the tab. Choose the File New menu option. Select field Type of Text. Enter Name of AL_VND , and Length of 50. All other attributes for this field require no input and should use their defaulted values. Modify Import Mapping 57

60 Choose the File Save menu option. Close the field by clicking the X on the tab. At this point, you have just created the new vendor attribute AL_VND fields. Having these fields in place allows for the supporting calculate actions to be added to the Set AL_VND Fields Values process object. Creating these new calculate objects will allow for the previously parsed out data string values from the flat file (that are stored in the IMP_VND Record fields) to be stored in the AL_VND field collection and continue to flow through the process. Perform the following steps to create the new calculate actions. Return to the previously opened Set AL_VND Field Values process object. Choose the Version Control Check Out menu option. Click once on row 24 and use the Insert After button to add row. Modify Import Mapping 58

61 Right-mouse-click on the newly added line 25 and choose Comment Line. Add the following comment text: Vendor Contact Info Click on row 25 and use the Insert After button to add row. Enter CONTACT in the Label edit box. Choose Calculate in the Type drop-down box. Select the Action Name for the new row and click the asterisk button to the right of the drop down box. Choose the Calculate Action menu option. Enter AL_VND Contact Name = IMP_VND Contact Name in the Action Name edit box. Modify Import Mapping 59

62 Click the Checkmark button on the right side of the Action Name drop down box. Use the Insert After button to add row. Choose Calculate in the Type drop-down box. Click the asterisk button to the right of the Action Name drop down box. Choose the Calculate Action menu option. Enter AL_VND Phone = IMP_VND Phone in the Action Name edit box. Click the Checkmark button on the right side of the Action Name drop down box. Use the Insert After button to add row. Choose Calculate in the Type drop-down box. Click the asterisk button to the right of the Action Name drop down box. Choose the Calculate Action menu option. Enter AL_VND = IMP_VND in the Action Name edit box. Click the Checkmark button on the right side of the Action Name drop down box. Choose the File Save menu option. The process object looks like the following graphic. The previous steps created the calculate actions. Now the details within each of these actions need to be specified. Modify Import Mapping 60

63 The following steps will complete the Contact Name calculation. From the Set AL_VND Fields Values process object, double-click the AL_VND Contact Name = IMP_VND Contact Name Calculate Action Name (line 26) to navigate to the object. Click the Insert After button. Select Equals from the Operator list. Select AL_VND Contact Name from the Result drop-down list. Select IMP_VND Contact Name from the Operand1 drop-down list. Select DEFAULT from the Output Format drop-down list. Click OK. Right-mouse-click on the object tab and select Save. Close the object. The following steps complete the Phone calculation. From the Set AL_VND Fields Values process object, double-click the AL_VND Phone = IMP_VND Phone Calculate Action Name (line 27) to navigate to the object. Click the Insert After button. Select Equals from the Operator list. Select AL_VND Phone from the Result drop-down list. Select IMP_VND Phone from the Operand1 drop-down list. Modify Import Mapping 61

64 Select DEFAULT from the Output Format drop-down list. Click OK. Right-mouse-click on the object tab and select Save. Close the object. The following steps complete the calculation. From the Set AL_VND Fields Values process object, double-click the AL_VND = IMP_VND Calculate Action Name (line 28) to navigate to the object. Click the Insert After button Select Equals from the Operator list. Select AL_VND from the Result drop-down list. Select IMP_VND from the Operand1 drop-down list. Select DEFAULT from the Output Format drop-down list. Click OK. Right-mouse-click on the object tab and select Save. Close the object. Modify Import Mapping 62

65 You have just updated the Set AL_VND Fields Values process object. The new calculate actions now assign the AL_VND Contact Name, Phone, and fields the values that were earlier parsed out from the data file and stored in the IMP_VND fields. This was an import step to ensure the data flows through the process. Close the Set AL_VND Fields Values process object. Now that the new AL_VND fields are assigned the values from the data file, the specific database action that inserts the imported vendor records and into the t_al_host_vendor_master table needs to be updated. Completing these steps will allow for the new attributes to be stored in the Generic Host Interface (GHI) table making it available to applications subscribing to vendor imports. Return to the Process Vendor Record process object. Click once on the Action Name column of line 3 (Call DB!Ins AL_VND). Double-click the Action Name column of line 3 (Call DB!Ins AL_VND) to open this object. The system opens the definition of the DB!Ins AL_VND process object. Click the Action Name column of line 3 (Call Ins AL_VND) to open this object. Double-click the Action Name column of line 3 (Call Ins AL_VND). The system opens the definition of the Ins AL_VND database action. Modify Import Mapping 63

66 In the graphic above you can see the AL_VND field values are inserted into the t_al_host_vendor_master table. (Recall from Activity 2: Alter the Database that you added the contact_name, phone, and columns to this table.) Perform the following steps to modify the database action to accommodate the new columns. Choose the Version Control Check Out menu. First, add the new t_al_host_vendor_master columns to the database action. string added to this section is presented below in bold text. The new columns text vqm_profile, contact_name, phone, ) The steps that follow direct you through each step to add the new columns string. Note that the new text is in bold and [ENTER] indicates use of the enter key. Click immediately after the vqm_profile column and add the following text:, [ENTER] Add the following text on the new line: contact_name, [ENTER] Add the following text on the new line: phone, [ENTER] Add the following text on the new line: Modify Import Mapping 64

67 Next, add the new AL vendor fields to the VALUES section the database action. The new text string added to this section is presented below in bold text. :AL_VND VQM Profile:, :AL_VND Contact Name:, :AL_VND Phone:, :AL_VND ) The steps that follow direct you through each step to add the new field string. Note the new text is in bold and [ENTER] indicates use of the enter key. Click immediately after the :AL_VND VQM Profile: column and add the following text:, [ENTER] Add the following text on the new line: :AL_VND Contact Name:, [ENTER] Add the following text on the new line: :AL_VND Phone:, [ENTER] Add the following text on the new line: :AL_VND The completed database action should look like the following graphic. The changes are highlighted. Note that spaces should be added to maintain the readability of the code. Modify Import Mapping 65

68 Choose the File Save menu. Right-mouse-click on the database action object tab and choose Close All. Compile/Activate Application Follow the steps below to Compile and Activate the Advantage Link for Flat File application. During this process the Advantage Architect compiler audits your application for errors. If the application has no errors, Advantage Architect compiles the application to the directory that you specify. Activating your compiled application overwrites the existing application by moving the compiled files into the runtime folder for your Solution Environment. Completion of these steps will allow for your changes to be tested in a later activity after all the change are complete. In Architect, select Run > Compile Application. Select FlatFileADVLink from the application drop down list, un-check Production compile and click Compile. If the compile was successful, the following dialog appears. Click Yes. Modify Import Mapping 66

69 In the dialog box that appears, Uncheck the Use Current Connection checkbox and click OK Change the Database Name to ADV. Use the same login credentials as before and click OK. Select AdvLinkFlatFile from the drop down box and click OK. Modify Import Mapping 67

70 Click Yes to stop the Solution Environment. If all went well, the following dialog should indicate that the activation was successful. Click OK. Note that after you compile and activate Advantage Link for Flat File, you would normally compile and activate previously activated applications that subscribe to messages published by Advantage Link for Flat File. The next activity will guide you through this process for the WA application after the necessary changes are completed. If you encountered errors during your compile and activate process, scroll through the Output Window in Advantage Architect to find additional information about the error and revisit the related steps provided in this activity. Modify Import Mapping 68

71 At this point you have completed configuration of the Advantage Link for Flat File application. The Advantage Link for Flat File solution will now processes the data file records, parse out the revised data mappings, and insert them into the corresponding Generic Host Interface (GHI) tables in the HighJump Advantage Application Database (AAD) with a Group ID. Upon completion of the fore mentioned events, a message will be published for subscribing applications to process. Your next phase of configuration will focus on the subscribing application. Modify Import Mapping 69

72 Activity 4: Configure Subscribing Application Now that the Advantage Link for Flat File application has been updated to support the new vendor file definition, your focus can turn to the subscribing Supply Chain Advantage (SCA) application. This subscribing solution receives the published message from Advantage Link for Flat File and processes the related Generic Host Interface (GHI) moving data into the final destination master data tables in the HighJump Advantage Application Database (AAD). In this activity you complete the following tasks: 1. Identify the Subscribing Object 2. Review the Existing Functionality 3. Configure the Subscribing Application Identify Subscribing Object Advantage Architect includes messages definitions that allow the Advantage Platform to control the publication and subscription of these messages. In order to begin configuration on the subscribing SCA application, the supporting objects must first be identified. Knowledge of the application and naming standards can significantly shorten this first step. However, we will follow the formal code path in this activity to demonstrate the link between the publishing and subscribing applications. In Advantage Architect, double-click the FlatFileAdvLink application from the Repository tab. Click the plus sign to expand the Triggered Process Object node. Double-click Host>Msg Vendor to open the definition of the triggered process object. The system opens the definition of the Host>Msg Vendor triggered process object that first imports vendors from the SCAVEND.DAT flat file into Generic Host Interface (GHI) tables and then publishes a message so subscribed applications can process the data. Focus on the publish message logic (lines 23-28) in the following graphic. Notice that line 24 (Calculate Msg Name=Vendor Msg FFADVLink) sets the Message Name variable to Vendor Msg FFADVLink. Modify Import Mapping 70

73 Click once on the Action Name column of line 25 (Call PB! Publish Action All Message). Double-click the Action Name column of line 25 (Call PB! Publish Action All Message) to open object. A review of the PB! Publish Action All Message process object will identify the specific Publish Action that is being used. Keeping in mind the fore mentioned Message Name value of Vendor Msg FFADVLink, you should see that the code will go through the first 10 lines failing each compare action until it passes line 11 (Msg Name=Vendor Msg FFADVLink?). The process then goes to the VENDOR MSG label in Line 23 where the Vendor Msg FFADVLink publish action is called. Modify Import Mapping 71

74 Click once on the Action Name column of line 23 (Publish Vendor Msg FFADVLink). Double-click the Action Name column of line 23 (Publish Vendor Msg FFADVLink) to open object. Publish actions are used to publish messages designed to notify an application of an event. In this case, the FlatFileAdvLink application has processed the Vendor Import SCAVEND.DAT flat file and is publishing the message called Vendor Msg FFADVLink to which another application subscribes. Continue with the following steps to identify the subscribing application and objects that need updates for the new vendor file definition. Double-click the contents of the Message Name attribute (Vendor Msg FFADVLink) to open the object. The following graphic shows that the Vendor Msg FFADVLink message includes the Msg Vendor Record and has subscribers. (Note that this record contains the Msg Host Group ID that is the unique identifier for the import generated by the Host>Msg Vendor triggered process.) Modify Import Mapping 72

75 Messages are vehicles for SCA modules to communicate with other SCA modules. They consist of a record or a list and are published by one module and subscribed to by other modules. (Multiple applications can subscribe to the same message and each receives a copy of the message.) Messages are also called Message Bus Messages because messages are published to the "message bus" (a table in the ADV database called t_message_bus). Right-click on the Vendor Msg FFADVLink object and select Where Used. This option helps you determine where certain objects are being used by the application. Modify Import Mapping 73

76 The results display on the Search tab as in the graphic below. In this case, we are interested in the message subscriptions. Double-click the contents of the Vendor Msg FFADVLink to open the object. Notice that the active application in Advantage Architect has changed from FlatFileADVLink to WA (see the graphic below). The steps completed up to this point have established that the WA solution s Vendor Msg FFADVLink message subscribes to the FlatFileADVLink message. Further review of the current object shows that the message subscription in the WA solution runs the Msg>App Vendor business process object. Double-click the Business Object Name to open Msg>App Vendor in the WA solution. This object will be the focal point of your configuring the subscribing application activities. Modify Import Mapping 74

77 Review the Process Object In the previous task, you determined that the Advantage Link for Flat File solution Host>Msg Vendor process object publishes the Vendor Msg FFADVLink message to which the Msg>App Vendor process object in the Warehouse Advantage solution subscribes. The steps that follow will guide you through the review of the Msg>App Vendor process object. (It is always important to have an understanding of the current process before making changes. Unfamiliarity with the application can result in missed requirements and the loss of information during the import process.) In Advantage Architect, double-click the WA application from the Repository tab. Click the plus sign to expand the Business Process Object node. Double-click Msg>App Vendor to open the definition of the business process object. Use the Msg>App Vendor: Line by Line chart below to review the business process object in Advantage Architect. Msg>App Vendor: Line by Line All of the descriptions below list the line numbers which refer to the opened Msg>App Vendor process object. To see any of the following steps in more detail, double-click the line in the process object in your HighJump Advantage Architect. Line(s) Description 1-2 This calculate action sets a log message to say the import has started. Whether these steps passes or fail, it moves to line 3. 3 This action connects to the database. In the database definition, there is information regarding the database name and type of database. If the step passes (fails), the process moves to line 4 (39). 4 This compare statement check if the database action from the previous line (3) encounters a deadlock error. If the step passes (fails), the process moves to line 3 (6). 6 This calls a process object that gets all system parameters. This process establishes a default value for each system parameter, but then queries the control table to get the configured value. After querying the control table it sets the corresponding system parameter. If the step passes (fails), the process moves to line 8 (39). Modify Import Mapping 75

78 Line(s) Description 8 This calls a process object that gets the first record in the vendor GHI table (t_al_host_vendor_master). Values are stored in the AL_VND fields. Note that this done through a query on the supporting database view (v_al_host_vendor_master) that uses the GHI table. If the step passes (fails), the process moves to line 9 (32). 9 This calculate action transforms the vendor message data. VND Record fields are assigned the AL_VND field values that were set in the prior line (8). Whether this step passes or fails, it moves to line This calls a process object that gets the next record in the vendor GHI table (t_al_host_vendor_master). Values are stored in the AL_VND fields. Note that this done through a query on the supporting database view (v_al_host_vendor_master) that uses the GHI table. If the step passes (fails), the process moves to line 11 (32). 11 This compare statement checks that at least one row was found in the last SQL statement from the previous line (10). If the step passes (fails), the process moves to line 12 (39). 12 This calculate action transforms the vendor message data. VND Record fields are assigned the AL_VND field values that were set in the prior line (8). Whether this step passes or fails, it moves to the next line (13) If the VND Vendor Code variable does not have a value, the log message is set to indicate this key variable is missing and it moves to line 36. If the VND Vendor Code variable has a value, it moves to line If the VND Vendor Name variable does not have a value, the log message is set to indicate this key variable is missing and it moves to line 36. If the VND Vendor Name variable has a value, it moves to line This calls a process object that sets the default values for the VND Record fields. Whether this step passes or fails, it moves to the next line (18) These three lines check to determine the Transaction Code. The Transaction Code was parsed out to data HighJump Advantage Architect can evaluate in Line 12. In this process object, the record type can have a value of N, U or D. These codes tell the application whether the record being process is record is marked as new (line 21), update (line 21), or delete (line 23). If the record type is none of the three, it fails at line 20, which directs the process to line This calls a process object that does an existences check on the t_vendor (final destination vendor working table) for the current Vendor Code. If a record already exist for the vendor, it moves to UPDATE label (line 24), otherwise, it moves to the INS VND label (line 25). 23 This calls a process object to delete the vendor record from the final destination working table. If the step passes (fails), the process moves to line 10 (49). 24 This calls a process object to update the vendor record in the t_vendor table. If the step passes (fails), the process moves to line 31 (49). 25 This calls a process object to insert the vendor record in the t_vendor table. If the step passes (fails), the process moves to line 26 (32) If Event Advantage is being used, send a new vendor event and proceed to line 31. If Event Advantage is not being used, proceed directly to line 31. Modify Import Mapping 76

79 Line(s) Description 31 Increment the Counter variable to capture the number of records processed. Whether this step passes or fails, it moves to line Increment the Error Counter variable to track the number of records that failed. If Event Advantage is being used, send a vendor import error event. Send the import error message to the log table in the HighJump Advantage Platform database. Whether these steps passes or fails, it moves to line Send the missing data message to the log table in the HighJump Advantage Platform database. If Event Advantage is being used, send a missing data event. Whether these steps passes or fails, it moves to line The DISCONNECT label first disconnects from the database and sends the processed/failed record count and import completed messages to the log table in the HighJump Advantage Platform database and then moves to line This return line exits the process object with a PASS. 49 This return line exits the process object with a FAIL. Your review of the code should establish some important details. The Msg>App Vendor business process retrieves data from the Generic Host Interface (GHI) tables in the HighJump Advantage Application Database (AAD) using Group ID sent in the message from Advantage Link for Flat File. After the data is transformed, a Transaction Code is used to determine how to act on the master vendor table in the database (e.g. insert, update, delete). Your configuration efforts in the next task will focus on these areas. Configure Warehouse Advantage Development can now begin using your understanding of the requirements and current process prior tasks. The following steps direct you through the configuration of the vendor import Warehouse Advantage (WA) business process object. Completion of this activity will allow data to be processed from staging GHI table into the primary vendor table (t_vendor). If not already accessible in Advantage Architect, open the Msg>App Vendor business process object in the WA application. Close any other opened objects. To begin, the WA application database action that fills the AL_VND fields must be updated to account for the new fields. Click once on the Action Name column of line 8 (Call DB!Get AL_VND w/group ID). Modify Import Mapping 77

80 Double-click the Action Name column of line 8 (Call DB!Get AL_VND w/group ID) to open the object. Click once on the Action Name column of line 3 (Call Find AL_VND w/group ID). Double-click the Action Name column of line 3 (Call Find AL_VND w/group ID) to open the object. The system opens the definition of the database action. Note that this query utilizes a database view (v_al_host_vendor_master) that uses the GHI table (t_al_host_vendor_master). Recall that you already modified these database objects in Activity 2: Alter the Database of this exercise. The Find AL_VND w/group ID database action uses the Group ID passed in the in the message published by the Advantage Link for Flat File solution to get the first record in the vendor Generic Host Interface (GHI) table and assign the values to the AL_VND fields. First the new AL_VND fields must be created and then these fields can then be added to the database action. The chart below lists the new field attributes that will be used. Modify Import Mapping 78

81 Name Type Length AL_VND Contact Name Text 40 AL_VND Phone Text 30 AL_VND Text 50 Perform the following steps to create new record fields. Choose the Define Field menu option to establish the active object type. Choose the File New menu option. Select field Type of Text. Enter Name of AL_VND Contact Name and Length of 40. All other attributes for this field require no input and should use their defaulted values. Modify Import Mapping 79

82 Choose the File Save menu option. Close the field by clicking the X on the tab. Choose the File New menu option. Select field Type of Text. Enter Name of AL_VND Phone and Length of 30. All other attributes for this field require no input and should use their defaulted values. Choose the File Save menu option. Close the field by clicking the X on the tab. Choose the File New menu option. Select field Type of Text. Enter Name of AL_VND , and Length of 50. All other attributes for this field require no input and should use their defaulted values. Modify Import Mapping 80

83 Choose the File Save menu option. Close the field by clicking the X on the tab. Now that the AL_VND fields have been created, you can update the Find AL_VND w/group ID database action. Return to the previously opened Find AL_VND w/group ID database action. Choose the Version Control Check Out menu. First, add the new v_al_host_vendor_master columns to the database action. The new columns text string added to this section is presented below in bold text. vqm_profile, contact_name, phone, ) Modify Import Mapping 81

84 The steps that follow will guide you through the addition of the new columns string. Note the new text is in bold and [ENTER] indicates use of the enter key. Click immediately after the vqm_profile column and add the following text:, [ENTER] Add the following text on the new line: Add the following text on the new line: Add the following text on the new line: contact_name, [ENTER] phone, [ENTER] Next, add the new AL vendor fields to the RETURNS(..) section of the database action. For reference, the new text string added to this section is presented below in bold text. :AL_VND VQM Profile:, :AL_VND Contact Name:, :AL_VND Phone:, :AL_VND ) The steps that follow direct you through each step to add the new field string. Note the new text is in bold and [ENTER] indicates use of the enter key. Click immediately after the :AL_VND VQM Profile: field and add the following text:, [ENTER] Add the following text on the new line: Add the following text on the new line: Add the following text on the new line: :AL_VND Contact Name:, [ENTER] :AL_VND Phone:, [ENTER] :AL_VND [ENTER] Choose the File Save menu. The completed database action should look like the following graphic. The changes are highlighted. Modify Import Mapping 82

85 Choose the File Save menu. Return to the Msg>App Vendor process object. Right-mouse-click and choose Close All But This. Click once on the Action Name column of line 9 (Calculate Transform Vendor Msg Data). Double-click the Action Name column of line 9 (Calculate Transform Vendor Msg Data) to open the object. The system opens the calculate action that transforms the vendor message data by assigning AL_VND Field values to the VND Record fields. To continue the new VND fields must first be created and then they can be added to the Transform Vendor Msg Data calculate action. Modify Import Mapping 83

86 The chart below lists the new field attributes that will be used to create them. Name Type Length VND Contact Name Text 40 VND Phone Text 30 VND Text 50 Perform the following steps to create the new VND fields. Choose the Define Field menu option to establish the active object type. Choose the File New menu option. Modify Import Mapping 84

87 Select field Type of Text. Enter Name of VND Contact Name, and Length of 40. All other attributes for this field require no input and should use their defaulted values. Choose the File Save menu option. Close the field by clicking the X on the tab. Choose the File New menu option. Select field Type of Text. Enter Name of VND Phone, and Length of 30. All other attributes for this field require no input and should use their defaulted values. Modify Import Mapping 85

88 Choose the File Save menu option. Close the field by clicking the X on the tab. Choose the File New menu option. Select field Type of Text. Enter Name of VND , and Length of 50. All other attributes for this field require no input and should use their defaulted values. Modify Import Mapping 86

89 Choose the File Save menu option. Close the field by clicking the X on the tab. Recall from your earlier changes that the AL_VND fields were assigned the database values of the vendor Generic Host Interface (GHI) table using the Group ID passed to the subscribing WA message and the Find AL_VND w/group ID database action. Now that you have created VND fields for the new attributes, the Transform Vendor Msg Data calculate action can be modified to assign the VND fields the corresponding AL_VND field values. Perform the following steps to modify the calculate action. Return to the Transform Vendor Msg Data calculate action. Choose the Version Control Check Out menu option. Click on the last row and use the Insert After button to add row. Modify Import Mapping 87

90 Select the Equals Operator, Result of VND Contact Name, Operand1 of AL_VND Contact Name, and Output Format of DEFAULT. Click OK to return to the Transform Vendor Msg Data calculate action. Click on the last row and use the Insert After button to add row. Select the Equals Operator, Result of VND Phone, Operand1 of AL_VND Phone, and Output Format of DEFAULT. Modify Import Mapping 88

91 Click OK to return to the Transform Vendor Msg Data calculate action. Click on the last row and use the Insert After button to add row. Select the Equals Operator, Result of VND , Operand1 of AL_VND , and Output Format of DEFAULT. Click OK to return to the calculate action. The finished Transform Vendor Msg Data Calculate Action should look like the following graphic. Modify Import Mapping 89

92 Right-mouse-click on the object tab and select Save. Close the object. Return to the Msg>App Vendor process object. Right-mouse-click and choose Close All But This. Click once on the Action Name column of line 10 (Call DB!FN AL_VND w/grp ID by Uniqu). Double-click the Action Name column of line 10 (Call DB!FN AL_VND w/grp ID by Uniqu) to open the object. Click once on the Action Name column of line 3 (Database FN AL_VND w/grp ID by Uniq). Double-click the Action Name column of line 3 (Database FN AL_VND w/grp ID by Uniq). Modify Import Mapping 90

93 The system opens the definition of the object. The FN AL_VND w/grp ID by Uniq database action uses the Group ID passed in the in the message published by the Advantage Link for Flat File solution to get the next record in the vendor GHI table and assign the values to the AL_VND fields. Note that this is done through a query on the supporting database view (v_al_host_vendor_master) that uses the GHI table (t_al_host_vendor_master). Recall that you already modified these database objects in Activity 2: Alter the Database of this exercise. Choose the Version Control Check Out menu option. First, the new v_al_host_vendor_master columns must be added to the database action. The new columns text string added to this section is presented below in bold text. vqm_profile, contact_name, phone, FROM v_al_host_vendor_master The steps that follow will guide you through the addition of the new columns string. Note the new text is in bold and [ENTER] indicates use of the enter key. Modify Import Mapping 91

94 Click immediately after the vqm_profile column and add the following text:, [ENTER] Add the following text on the new line: Add the following text on the new line: Add the following text on the new line: contact_name, [ENTER] phone, [ENTER] [ENTER] Next, add the new AL vendor fields to the RETURNS( ) section of the database action. The new text string added to this section is presented below in bold text. :AL_VND VQM Profile:, :AL_VND Contact Name:, :AL_VND Phone:, :AL_VND ) The steps that follow direct you through each step to add the new field string. Note the new text is in bold and [ENTER] indicates use of the enter key. Click immediately after the :AL_VND VQM Profile: field and add the following text:, [ENTER] Add the following text on the new line: Add the following text on the new line: Add the following text on the new line: :AL_VND Contact Name:, [ENTER] :AL_VND Phone:, [ENTER] :AL_VND [ENTER] Choose the File Save menu. The completed database action should look like the following graphic. The changes are highlighted. Modify Import Mapping 92

95 Choose the File Save menu. Return to the Msg>App Vendor process object. Right-mouse-click and choose Close All But This. Click once on the Action Name column of line 24 (Call DB!Upd Vendor w/vendor Code). Double-click the Action Name column of line 24 (Call DB!Upd Vendor w/vendor Code) to open the object. Click once on the Action Name column of line 2 (Database Upd VND w/ Vendor Code). Modify Import Mapping 93

96 Double-click the Action Name column of line 2 (Database Upd VND w/ Vendor Code) to open the object. Choose the Version Control Check Out menu option. The Upd VND w/ Vendor Code database action updates the t_vendor table setting the record to the columns equal to their respective VND field values. As with the earlier database actions, this object needs to be updated to reflect the new columns in the t_vendor table. The new text added to this object is presented below in bold text. vqm_profile = :VND VQM Profile:, contact_name = :VND Contact Name:, phone = :VND Phone:, = :VND WHERE vendor_code = :Vendor Code: ) The steps that follow will guide you through the changes. Note the new text is in bold and [ENTER] indicates use of the enter key. Click immediately after the vqm_profile column and add the following text:, [ENTER] Add the following text on the new line: Add the following text on the new line: Add the following text on the new line: contact_name = :VND Contact Name:, [ENTER] phone = :VND Phone:, [ENTER] = :VND The completed database action should look like the following graphic. The changes are highlighted. Modify Import Mapping 94

97 Choose the File Save menu. Return to the Msg>App Vendor process object. Right-mouse-click and choose Close All But This. Click the Action Name column of line 25 (Call DB!Ins VND) to bring focus. Double-click the Action Name column of line 25 (Call DB!Ins VND). Click the Action Name column of line 2 (Call Ins VND) to bring focus. Double-click the Action Name column of line 2 (Call Ins VND). The Ins VND database action inserts the new record into the t_vendor table. In this statement the column names of the statement are not specified in the column list because values for all t_vendor columns are supplied in the VND Insert Record. (Note that the records fields are also listed in the same order as the columns in the table.) Therefore, you do not need to make changes to Ins VND. (If the Modify Import Mapping 95

98 INSERT statement explicitly mapped columns and values, the new fields would need to be added.) The VND Insert Record, however, does need to be updated to reflect the new t_vendor table definition. Close the Ins VND database action. Perform the following steps to modify the record definition. Choose the Define Record menu option. Search for the VND Insert Record. Open the VND Insert Record. Modify Import Mapping 96

99 Choose the Version Control Check Out menu option. Click anywhere on row 6 (IMP_VND VQM Profile) to highlight the line. Click the Insert After button. Choose the VND Contact Name for Record Field and accept the defaulted values for all other attributes. Click the OK button. Click the Insert After button. Choose the VND Phone for Record Field and accept the defaulted values for all other attributes. Click the OK button. Click the Insert After button. Choose the VND for Record Field and accept the defaulted values for all other attributes. Click the OK button. Modify Import Mapping 97

100 Click the Update Length button for the IMP_VND Record. Note this is an important step to ensure the Start and End positions are correct. The WA application could lose data values that map beyond the total length if the length is not updated. Choose the File Save menu option. The finished Record Field should look like the following graphic. As you can now see above, adding the new attributes to the VND Insert Record definition has extended the end position of the last field in the record. The length of the VND Record Str field associated with the record now needs to be at least of 242 to ensure data is fully mapped and not lost. Perform the following steps to ensure the VND Insert Record has enough room in the VND Record Str for the new definition. From the VND Insert Record double-click the VND Record Str Text Field to open the object definition Modify Import Mapping 98

101 Choose the Version Control Check Out menu option. Update the Length to be the total length of the record (242). Choose the File Save menu option. Return to the Msg>App Vendor process object. Right-mouse-click and choose Close All But This. Recall that the Ins VND database action assumes that data stored in the VND Insert Record is in the same order as the table columns defined in the database. (This is apparent because the column list for the t_vendor table is not explicitly part of the statement.) Earlier you alter the table within the SQL Server Advantage Application Database (AAD). In this next section you will modify the Advantage Architect Database Definition within WA. In Advantage Architect, select Database Definition as the object type and double-click on AAD to open. Database Definition allows you to set up table definitions in HighJump Advantage Architect that contain column names and other data characteristics that are necessary to create and access rows and columns from a database table. Modify Import Mapping 99

102 Check out the object using the appropriate menu icon. In the AAD Database Definition, scroll through the Table List to locate the t_vendor table and click the record to highlight it. Move down to the Column List for the t_vendor table and select the last column record for the table (vqm_profile). Click the Insert After button. Define the contact_name column by entering the information below and clicking the OK button. Modify Import Mapping 100

103 Click the Insert After button. Define the phone column by entering the information below and clicking the OK button. Click the Insert After button. Define the column by entering the information below and clicking the OK button. The Database Definition for the t_vendor table should resemble the graphic provided below. Modify Import Mapping 101

104 Save and close the AAD Database Definition. Compile/Activate Application Perform the following steps to Compile and Activate the Warehouse Advantage (WA) application. During this process the Advantage Architect compiler audits your application for errors. If the application has no errors, Advantage Architect compiles the application to the directory that you specify. Activating your compiled application overwrites the existing application by moving the compiled files into the runtime folder for your Solution Environment. Completion of these steps will allow for your changes to be tested in a later activity after all the change are complete. In Architect, select Run > Compile Application. Select WA from the application drop down list, un-check Production compile and click Compile. Modify Import Mapping 102

105 If the compile was successful, the following dialog appears (be patient, it may take a few minutes). Click Yes. In the dialog box that appears, Uncheck the Use Current Connection checkbox and click OK Change the Database Name to ADV. Use the same login credentials as before and click OK. Modify Import Mapping 103

106 Select WA from the drop down box and click OK. Select Yes to stop the Solution Environment. Select Yes to restart the Solution Environment. Modify Import Mapping 104

107 If all went well, the following dialog should indicate that the activation was successful. Click OK. After compile, and activate Warehouse Advantage, you must recompile and activate previously activated applications that subscribe to messages published by Advantage Link for Flat File. Note if errors occurred during the compile and activate process, scroll through the Output Window in Advantage Architect for additional information and revisit the related steps provide in this activity. Upon successful compile and activation, you have completed configuration of the Warehouse Advantage (WA) application. After receiving the Group ID in message published from the Advantage Link for Flat File (AdvLinkFlatFile) solution. The subscribing WA application will now retrieve the new vendor attributes from the Generic Host Interface (GHI) tables. These new vendor attributes will be stored and transformed before the WA application either creates or updates vendor information in the master data table (t_vendor) tables in the HighJump Advantage Application Database (AAD). In the next activity you will use the customer provided file (SCAVEND.CUSTOM) to verify that new file mappings, database changes, and application (WA and AdvLinkFlatFile) changes converge to correctly populate the vender master data table in the Advantage Application Database (AAD). Modify Import Mapping 105

108 Activity 5: Process Test File Now that configuration of both the Advantage Link for Flat File and the subscribing Supply Chain Advantage (SCA) application (Warehouse Advantage) are complete, you are ready to test the customer provided file that was reviewed in the Define File Mapping activity for this exercise. When the test file is dropped to the Advantage Commander triggered file path, Advantage Link for Flat File will run the associated process object (Host>Msg Vendor) transforming the data file populating the related Generic Host Interface (GHI) tables. Each completed group publishes a message. The subscribing application (Warehouse Advantage) receives the published message and processes (Msg>App Vendor) the related GHI data into the final destination working tables (t_vendor) in the HighJump Advantage Application Database (AAD). The following steps direct you through the processing of the test and validation of data. Open the Advantage Workflow Engine Service Manager and confirm that the necessary solutions are running. Open the Application Status Console (All Programs HighJump Software Advantage Platform Application Status Console). Modify Import Mapping 106

109 The Application Status Console displays in chronological order application events and errors that occur within HighJump Advantage applications and HighJump WebWise. In addition to displaying informational log messages on the current state of the file during the import process, this window also provides visibility to exceptions and application errors. Open Windows Explorer. Click the Desktop button on the left pane. Navigate to the Training\AdvLink Flat File\VENDOR folder and copy the SCAVEND.CUSTOM file. Navigate to the C:\HJS\IMPORTS\VENDOR folder and paste the SCAVEND.CUSTOM file. Confirm that no other *.DAT file is present in this folder. Click on the SCAVEND.CUSTOM file and Copy-Paste to the current folder. A Copy of SCAVEND.CUSTOM file will be created. Click on the Copy of SCAVEND.CUSTOM file and rename the file to SCAVEND.DAT Click Yes on the Rename warning message below. For a moment, the contents of the vendor import directory should resemble the graphic below. Modify Import Mapping 107

110 The import process will then begin within the Advantage Commander triggered process defined poll rate (10 seconds). At that time the Advantage Link for Flat File application then reads the SCAVEND.DAT file, populates the t_al_host_vendor_master GHI table, and publishes a message. After receiving the message, Warehouse Advantage processes and populate the t_vendor table. The processed SCAVEND.DAT is rolled over becoming SCAVEND.001 and earlier processed files are incremented (e.g. SCAVEN.002 ). The Application Status Console you opened earlier will include log information import for both the Advantage Link for Flat File (ADVLINKFLATFILE) and Warehouse Advantage (WA) solutions. Below is a text extra of log information from the above Application Status Console information. Application Status Console Modify Import Mapping 108

111 [ :46:47.734] [ADVLINKFLATFILE] [P_FF-VEN] [Beginning execution of Process Object [ADVLINKFLATFILE.Host>Msg Vendor].][ :46:47.734] [ADVLINKFLATFILE] [P_FF-VEN] [Host>Msg Vendor started at 14:46:47 on 01/10/14.] [ :46:53.453] [ADVLINKFLATFILE] [P_FF-VEN] [Host>Msg Vendor Processed [6] Records.] [ :46:53.453] [ADVLINKFLATFILE] [P_FF-VEN] [Host>Msg Vendor Encountered [0] Error Records.] [ :46:53.453] [ADVLINKFLATFILE] [P_FF-VEN] [Host>Msg Vendor ended at 14:46:53 on 01/10/14.] [ :46:53.453] [ADVLINKFLATFILE] [P_FF-VEN] [Ending execution of Process Object [ADVLINKFLATFILE.Host>Msg Vendor]. Time to execute was 5719 milliseconds.] [ :46:53.921] [WA] [M_03] [Beginning execution of Process Object [WA.Msg>App Vendor].] [ :46:53.921] [WA] [M_03] [Import Vendors started at 14:46:53 on 01/10/14. ] [ :46:54.234] [WA] [M_03] [Msg>App Vendor Processed [6] Records.] [ :46:54.234] [WA] [M_03] [Msg>App Vendor Encountered [0] Error Records.] [ :46:54.234] [WA] [M_03] [Msg>App Vendor ended at 14:46:54 on 01/10/14.] [ :46:54.234] [WA] [M_03] [Ending execution of Process Object[WA.Msg>App Vendor]. Time to execute was 312 milliseconds.] This output in the Application Status Console tells you that the ADVLINKFLATFILE application started at 14:46:47, processed 6 records with 0 error records, and stopped at 14:46:53. Then the WA application started at 14:46:53, processed 6 records with 0 error records, and stopped at 14:46:53. No application or database errors were posted. In Microsoft SQL Server Management Studio choose the File Open menu. Click the Desktop button on the left pane. Navigate to the Training\AdvLink Flat File\SQL folder. Click the run_confirm_import.sql file. Click the Open button. Choose Query Execute menu. Modify Import Mapping 109