Advancement Data Load 8.8 Handbook

Banner AdvancementData Load/Extract Handbook Release 8.8December 2015/nWithout limitation: Ellucian®, Banner®, Coll eague®, and Luminis® are trademarks of the Ellucian group of companies that are reg istered in the U.S. and certain other countries; and Ellucian AdvanceŽ, Ellucian Course SignalsŽ, Ellucian Degree WorksŽ, Ellucian PowerCampus Ž, Ellucian RecruiterŽ, Ellucian SmartCallŽ, are also trademarks of the Ellucian group of companies. Other names may be trademarks of their respective owners. © 2005, 2015 Ellucian. Contains confidential and proprietary information of Ellucian and its subsidiaries. Use of these materials is limited to Elluci an licensees, and is subject to the terms and conditions of one or more written li cense agreements between Ellucian and the licensee in question. In preparing and providing this publicati on, Ellucian is not rendering legal, accounti ng, or other similar professional service s. Ellucian makes no claims that an institution's use of this publication or the soft ware for which it is provided will guarantee compliance with ap plicable federal or state laws, rules, or regulations. Each organiza tion should seek legal, accounting, and other similar professional services from comp etent providers of the organization's own choosing. Ellucian 4375 Fair Lakes Court Fairfax, VA 22033 United States of America Revision History Publication DateSummary December 2015 New version that supports Banner Advancement 8.8 software. /n 3Banner Advancement Data Load/Extract Handbook |Contents Contents Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7 Data files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Advancement Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Data Transfers Using Data Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8 Set up a data load or a data extract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Extract directory data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Data that can be extracted. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Steps to extract data from Banner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Load matching gift data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Data that can be loaded. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Load external ratings and directory information . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Data that can be loaded. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Address information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Incoming fitofl date before other addresses begin . . . . . . . . . . . . . . . . . . . . . . . . . . 83 Incoming fifromfl date after other addresses ends . . . . . . . . . . . . . . . . . . . . . . . . . . 83 Incoming fifromfl date between existing fifromfl and fitofl dates . . . . . . . . . . . . . . . . . 84 Incoming fitofl date between existing fifromfl and fit ofl dates . . . . . . . . . . . . . . . . . . . 84 Incoming fifromfl and fitofl dates between existi ng fifromfl and fitofl dates . . . . . . . . . 85 Incoming fifromfl and fitofl dates come before and after existing fifromfl and fitofl dates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Incoming fifromfl and fitofl dates cross over date s on two other records. . . . . . . . . . 87 Incoming date range includes existing date range . . . . . . . . . . . . . . . . . . . . . . . . . 88 Existing address with some null fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Technical considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Loading data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Header record. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Dates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 /n 4Banner Advancement Data Load/Extract Handbook |Contents Load third-party gifts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 Record types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 Base record (record number 01). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 Detail record (record number 02) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Format of the data load file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Character delimited data load file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Fixed length data load file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Data that can be loaded. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Technical considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Loading data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Header record. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Dates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 4Data Transfers Using the Advancement Conn ector . . . . . . . . . . . . . . . .105 Integration with iModules Encompass . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Processing overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Data that can be synchronized. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Push processing flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Pull processing flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 Set up the Advancement Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 Manage data mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Create a local data mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Inactivate a data mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Manage profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Local profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 Related data elements in pull profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 Selection values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 Selection value for Primary Donor Code data elemen t. . . . . . . . . . . . . . . . . . . . . . 117 Selection value for Deceased data element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 Create a profile without copying. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 Create a profile by copying. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 Modify a profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 20Delete a profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 21/n 5Banner Advancement Data Load/Extract Handbook |Contents Push data from Banner to Encompass . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 Load initial data to Encompass. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 Initiate a push process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 CSV file creation processing and lo gic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 Best practice recommendations for Web Service pushes and CSV file creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 View the status of a push process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 Correct a push process that processed with errors . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Special Handling when the Primary Donor Code has Changed in Banner. . . . . . . . . . 127 Pull biographic data from Encompass to Banner . . . . . . . . . . . . . . . . . . . . . . . . . . 128 Initiate a pull process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 View the status of a pull process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 Review and post data changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 Banner updates for pulled data changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 Primary e-mail. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 Business e-mail. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 Preferred phone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 Business phone. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 Preferred address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 Business address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 Business addresses and primary employment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 Home fax phone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 Business fax phone. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 Cell phone. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 Pull one-time, perpetual, and scheduled gifts from Encompass to Banner . . . . . 149 Supported transaction types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 Unsupported transaction types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 Scheduled payments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 Process overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 Initial scheduled payment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 Pledge installments out of balance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 Subsequent pledge payments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 Gift setup in Banner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 AGACTRL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 AUACMAP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 AUACDEF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 Payment frequency. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 Pledge duration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 Adjustments required for scheduled payments entered before 8.6.1 . . . . . . . . . . . 170 Setting up Designations in Encompass . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 Setting up instance fields In Encomp ass . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 /n 6Banner Advancement Data Load/Extract Handbook |Contents Gift pull initiation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 AUAINIT Œ Initiation tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 AUAINIT Œ Scheduler tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 AUAINIT Œ Run History tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 Error Identification Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 Merge Gift Pull Timeline Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 Gift Review functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 Viewing Processing Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 Modifying the Gift Type value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 Handling gifts with no Designation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 Viewing Processing Instructions fo r Billing Phone. . . . . . . . . . . . . . . . . . . . . . . . . . 178 Display of Encompass Data on AGAWGIF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 Schedule the transfer of data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 Scheduler tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 8Adding a new scheduler record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 Modifying an existing scheduler record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 Deleting an existing scheduler record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 E-mail notification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 9Appendix A - Advancement Connector Data Mappings. . . . . . . . . . . . .191 Biographic information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 Preferred contact information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 Education information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202 Other education information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 Spouse and family information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 Business information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231 Business contact information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 Activities and honors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 Admin only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 /n 7Banner Advancement Data Load/Extract Handbook |Introduction IntroductionYou can load data from third-party products to Banner® Advancement. You can also extract data from Banner for use by third-party products. There are two ways to transfer data between Banner and third-party products: ŁData files ŁAdvancement Connector Data files The following Banner Advancement processes use data files to transfer data between Banner and third-party products: fiData Transfers Using Data Filesfl on page8 provides detailed instructions for setting up a data extract or data load process and running each process. Advancement ConnectorThe Advancement Connector is a Banner Advancement module that uses Web services to transfer data between Banner and third-party products. fiData Transfers Using the Advancement Connectorfl on page105 provides detailed instructions for using the Advancement Connector to load data between Banner Advancement and Encompass, a Web-based social networking tool available from iModules. APPDEXTDirectory Data Extract ProcessAGPMATCMatching Gift Data Load Report APPCUPDExternal Ratings an d Directory Load Process AGPEXGFExternal Gi ft Load Process /n 8Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files Data Transfers Using Data Files The following processes in Banner® Advancement use data files to transfer data between Banner and third-party products. This chapter provides detailed instructions for setting up a data extract or data load process and running each process. Set up a data load or a data extract You must set up the data load or data extrac t before you load or extract data. Setup for a data extract and setup for a data load are similar. Use the following steps to set up a data load or a data extract: ŁfiStep 1 - Define the third-party vendors or external systemsfl on page9 (data load only) ŁfiStep 2 - Define the data filefl on page9 ŁfiStep 3 - Review the fields that are available for data load or data extractfl on page10 ŁfiStep 4 - Map external values to Banner valuesfl on page10 (data load only) ŁfiStep 5 - Review available Banner data fieldsfl on page11 ŁfiStep 6 - Define the format of the data filefl on page12 ŁfiStep 7 - Set up name type codesfl on page13 ŁfiStep 8 - Set up cross reference codesfl on page14 ŁfiStep 9 - Set up e-mail address type codesfl on page14 ProcessProcess Name Description APPDEXTDirectory Data Extrac t ProcessExtracts alumni information from Banner for third-party vendors that produce directories AGPMATCMatching Gift Data Load ReportLoads employer matching gift policies and procedures into Banner APPCUPDExternal Ratings and Directory Load Process Loads alumni information from third-party vendors that produce directories into Banner Loads external ratings data into Banner AGPEXGFExternal Gift Load Pr ocessLoads gift and pled ge payment details from third-party vendors into Banner /n 9Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files Step 1 - Define the third-party vendors or external systemsNote: This step applies to data loads only . Skip this step if you are setting up a data extract. Use the Data Source Identifier Validation Form (ATVDSRC) to define the third parties that provide data to be loaded. You only need to define vendors and external systems that send data that differs from existing Banner values. You do not need to define vendors and external systems that send data that matches Banner values. Step 2 - Define the data file Use the Data File Validation Form (ATVTAPE) to define the basic characteristics of each data extract or data load file that you use. The file can be character delimited or fixed length: ŁCharacter delimited - A special character (such as a comma) separates each field in a record. This special char acter is defined in the Delimiter field. The following figure shows a sample ATVAPE definition for a character delimited file: ŁFixed length - Each field (for example, last name or e-mail address) is a predetermined, constant number of characters. (The length of each field is de fined in a later step.) A file is fixed length if the Delimiter field is blank. The following figure shows a sample definition for a fixed length file: You can define an unlimited number of extr act and load files. Because you can add a new file code every time you want to create a different layout, there is no need to remove or change an existing definition. Banner allows you to track and save the history of previous file definitions, if you wish, by pr oviding the ability to do the following: ŁDefine a new name. ŁUse the copy feature to duplic ate the existing definition. ŁMake changes, as necessary, to the new record. Example - fixed length matching gift data load file ŁFile Code field: MG_L_2008 ŁDescription field: Matching Gift load-2008 ŁProcess field: AGPMATCŁDelimiter field: blank ŁMarker field: blank Because the Delimiter and Marker fields are blank, Banner expects you to define the length of each field on the Data Field Position Rules Form (AGATPFD) (step 6). /n 10Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files Example - character delimited directory load fileŁFile Code field: D_L_ABC_08 ŁDescription field: Directory load-ABC vendor-2008 ŁProcess field: APPCUPDŁDelimiter field: , (comma) ŁMarker field: blank The Delimiter field tells Banner that a comma separates each data field for each record in the file being loaded. Example - character delimited directory data extr act file with a marker requiredŁFile Code field: D_E_ABC_08 ŁDescription field: Directory extract-ABC-2008 ŁProcess field: APPDEXTŁDelimiter field: , (comma) ŁMarker field: fi (quotation mark) Banner creates a file where every field is in quotation marks and is separated by a comma (for example, fiJamesfl,fiArnoldfl,fiSmithfl,fiApt. 2, Building Afl). The comma between Apt. 2 and Building A is not a problem for Banner because markers are used. Banner treats Apt. 2, Building A as a single item. Step 3 - Review the fields that are available for data load or data extract Use the Data Field Names Validation Form (ATV TPFD) to review the fields that can be included in your data load or extract based on the selected process. The displayed values are delivered as part of the baseline product and cannot be changed. Not all values listed are available for all processes. Step 4 - Map external va lues to Banner values Note: This step applies to data loads only . Skip this step if you are setting up a data extract. Vendors and external systems might use some codes that are different from the corresponding Banner codes. If this occurs, you must tell Banner what codes to look for and how the codes should be translated. 1.Review the code values on incoming data file s to determine if any values differ from those in your Banner tables. 2.Use the Data Translation Field Value Rules Form (APATRAN) to map a vendor™s values to the appropriate Banner values. /n 11Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files Each vendor requires its own mapping becaus e different vendors use different values. When data is loaded, Banner translates the vendor™s values to the appropriate Banner values.If a vendor™s file contains all Banner values, you do not need to create translations on APATRAN. You only need to set up the translations when the vendor™s values do not match the Banner values. Consider an example for ADDR_COUNTRY. The vendor might use the code USA for United States of America while Banner uses the code 157. APATRAN would specify, for this vendor (data source) and ADDR_COUNTRY (field name), that Banner should look for occurrences of USA and translate each one to 157 when loading data. Note: The values in Banner tables are uppercase. If the vendor™s values are mixed case or lowercase, you must use APATRAN to map the vendor™s values to the Banner values. Key blockFields in this block are used to query data in the Details block. All fields in the key block are optional. If you want to see all records for all data sources and all field names, leave all fields blank and perform a Next Block. Details block This block shows the translations between the vendor™s values and Banner values. You can enter new translations or changes entries. Some fields have a pull-down arrow that allows you to select from a list of values. Step 5 - Review avail able Banner data fields Use the Data Field Process Rules Form (APATPFD) to review the processes that can extract or load each data field. Values for the supported data fields and processes are delivered as part of the baseline product. If you want to load or extract additional da ta fields to accommodate local modifications, you must add the data fields on the Data Field Names Validation Form (ATVTPFD) and APATPFD. Add data fields on ATVTPFD The Data Field Names Validation Form (ATVTPFD) lists all fields that can be extracted from and loaded into Banner. The displayed values are delivered as part of the baseline product and cannot be changed or deleted. If you want to load or extract additional data fields to accommodate local modifications, add the data fields to ATVTPFD. Note: Not all values are available for all processes. /n 12Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files Add Data Fields on APATPFD The Data Field Process Rules Form (APATPFD) displays all processes that can extract or load a specific field. The displayed values are delivered as part of the baseline product and cannot be changed or deleted. If you want to load or extract additional data fields to accommodate local modifications, add the data fields to APATPFD. Step 6 - Define the form at of the data file Use the Data Field Position Rules Form (AGATP FD) to define the format of the data file. This file definition specifies the order of fields on the extract file that Banner creates or on the load file that Banner receives. There are two types of data file formats. Each type has a separate window for defining the file format.ŁCharacter delimited - A special character (such as a comma) separates each field in a record. This special char acter is defined in the Delimiter field on ATVTAPE. ŁFixed length - Each field (for example, last name or e-mail address) is a predetermined, constant number of characters. A file is fixed length if the Delimiter field on ATVTAPE is blank. For data loads, the third-party vendor provides the data file layout to use as the basis for defining the format on AGATPFD. Note: The External Gift Load Process (AGPEXGF) has additional file layout requirements. See fiLoad third-party giftsfl on page90 for more details. Delimited File Details window This window is displayed if the file code entered in the key block is defined on ATVTAPE as character delimited . This window allows you to s pecify the order in which the fields appear on the extract or load and any occurrence information. Note: The Copy Definition option is enable d if you are defining a new file code that has no existing format details. Fixed Length File Details window This window is displayed if the file code in the key block was defined on ATVTAPE as fixed length . This window allows you to specify t he order of fields in the data extract or data load, the length of each field, and any occurrence information. Note: The Copy Definition option is enable d if you are defining a new file code that has no existing format details. /n 13Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files Using occurrencesThe Occurrence field is used to manage repeating groups of information such as multiple children or multiple types of addresses. For example, a data load can include home, business, and cell phone information. Each reco rd would consist of the same information: ŁType code ŁArea code ŁTelephone number ŁExtensionFor a fixed format data file layout, you would specify the start and end position for each field, but use a different occurrence for each type of telephone information: Step 7 - Set up name type codes Name type codes are used for the following: ŁNames of parent comp anies and subsidiaries ŁCross-references ŁAliasesŁFund names ŁOrganization names Field NameStartEndOccurrenceDescription PHONE_CODE27301 Type code - home phone PHONE_AREA31331 Area code - home phone PHONE34401 Telephone number - home phone PHONE_EXT41451 Telephone extension - home phone PHONE_CODE46492 Type code - business phone PHONE_AREA50522 Area code - business phone PHONE53592 Telephone number - business phone PHONE_EXT60632 Telephone extension - business phone PHONE_CODE64673 Type code - cell phone PHONE_AREA68703 Area code - cell phone PHONE71773 Telephone number - cell phone PHONE_EXT78813 Telephone extension - cell phone /n 14Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files They are used in many different places in B anner, including the Alternate Identification window on the Advancement Identification Form (APAIDEN). Name type codes are shared with all Banner systems. You should work with the other Banner users at your institution to determi ne which values to add. Use the Name Type Validation Form (GTVNTYP) to set up name type codes if they have not already been created. Step 8 - Set up cross reference codes Cross reference codes identify the cross reference relationships tracked by Banner. These codes must be defined before you can set up cross references between parent companies and subsidiaries. Use the Cross Reference Code Validation Form (ATVXREF) to set up cross reference codes if they have not already been created. Step 9 - Set up e-mail address type codes Examples of e-mail address types include bu siness, personal, and school. They are used in many different places in Banner. Becaus e they are shared with other Banner systems, you should work with the other Banner users at your institution to determine which values to add. Use the E-mail Address Type Validation Form (GTVEMAL) to add e-mail address type codes.Extract directory data The Directory Data Extract Pr ocess (APPDEXT) extracts alum ni information from Banner for third-party vendors that produce directories. The vendors can send surveys to your alumni, receive the results, and send you a file with the updated data. You can then use the External Ratings and Directo ry Load Process (APPCUPD) (see fiLoad external ratings and directory informationfl on page60 ) to load this file into Banner. Before extracting data, you must perform the setup steps described in fiSet up a data load or a data extractfl on page8 .Data that can be extracted APPDEXT can extract the following data from Banner. The ATVTPFD field names are used to define the file layout on the Data Field Position Rules Form (AGATPFD). ATVTPFD Field NameBanner Data Field Description ADDR_ACTIVITY_DATESPRADDR_ACTIVITY_ DATEDate of last address update /n 15Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files ADDR_CITY SPRADDR_CITY City for specified address type code. Address must be active. ADDR_CODE SPRADDR_ATYP_CODE Address type code ADDR_HOUSE_NUMBERSPRADDR_HOUSE_NUM BERUnique number assigned to each building on a street or in an area and used as part of the postal address in some countries ADDR_PHONE SPRTELE_PHONE_NUMBERPhone number for telephone type code specified as a parameter. Telephone number must be active. ADDR_PHONE_ALLSPRTELE_PHONE_ALL Phone area code, number, and extension for telephone type code specified as a parameter. Telephone number must be active. ADDR_PHONE_AREASPRTELE_PHONE_ AREAPhone area code for telephone type code specified as a parameter. Telephone number must be active. ADDR_PHONE_COUNTRY_ CODE SPRTELE_CTRY_CODE_PHONECo de that designates the region and country of the telephone number ADDR_PHONE_EXTSPRTELE_PHONE_EXT Phone number extension for telephone type code specified as a parameter. Telephone number must be active. ADDR_STATE SPRADDR_STAT_CODE State for specified address type code. Address must be active. ADDR_STREET1SPRADDR_STR EET_LINE1First address line for specified address type code. Address must be active. ADDR_STREET2SPRADDR STREET_LINE2Second address line for specified address type code. Address must be active. ADDR_STREET3SPRADDR_STREET_L INE3Third address line for specified address type code. Address must be active. ATVTPFD Field NameBanner Data Field Description /n 16Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files ADDR_STREET4SPRADDR _STREET_LINE4Fourth address line for specified address type code. Address must be active. ADDR_ZIPSPRADDR_ZIP ZIP/postal code for the specified address type code. The address must be active. These are the first five digits of SPRADDR_ZIP. ADDR_ZIP4 SPRADDR_ZIP ZIP/postal code for specified address type code. Address must be active. These are the last four digits of SPRADDR_ZIP. ADDR_ZIPC SPRADDR_ZIP ZIP/postal code for specified address type code. Address must be active. This is the complete value in SPRADDR_ZIP. BAN_ID SPRIDEN_ID Banner ID (unique identifier) BAN_PIDM SPRIDEN_PIDM Banner PIDM (unique identifier) BIRTH_DATE SPBPERS_BIRTH_DATE Birth dateCHILD_NAME_FIRSTAPRCHLD_FIRST_NAME Child™s first name (repeating value if a person has more than one child) CHILD_NAME_LASTAPRCHLD_LAST_NAME Ch ild™s last name (repeating value if a person has more than one child) CHILD_NAME_MIDDLEAPRCHLD_MI Child™s middle name (repeating value if a person has more than one child) CHILD_SURNAME_PREFIXAPRCHLD_SURNAME PREFIXChild™s last name prefix (repeating value if a person has more than one child) DECEASED_INDSPBPERS_DEAD_I NDDeceased indicatorDEGREE APRADEG_DEGC_CODE Degree code (repeating value if a person has more than one degree code) DEGREE_YEAR APRADEG_ACYR_CODE Award year (repeating value if a person has more than one award year) ATVTPFD Field NameBanner Data Field Description /n 17Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files DONOR_CODE APRCATG_DONR_CODE Donor category (identifies non-alumni, etc.) EMAILGOREMAL_EMAIL_ADDRESSE-mail address for e-mail address type code specified as a parameter. E-mail address must be the primary one (primary indicator must be selected).EMAIL_CODEGOREMAL_EMAL_CO DEE-mail type code that corresponds to the e-mail address. EMPR_NAME APREHIS_EMPR_NAME Employer™s name where the primary indicator is selected and the to date (APREHIS_TO_DATE) is null. If a selected record has a Banner PIDM, the name is selected from the SPRIDEN table. Otherwise, the name is selected from the APREHIS table. EMPR_PIDMAPREHIS_EMPR_PIDM Employer™s PIDM where the primary indicator is selected and the to date (APREHIS_TO_DATE) is null. The following employer address and phone informat ion is selected by comparing these values: ŁAddress type and sequence number on APREHIS associated with the record selected ŁAddress type and sequence number on SPRADDR and SPRTELE for the employee The primary employer indicator must be sele cted. The telephone number must be active. EMPR_ADDR_ACT_DATESPRADDR_ACTIVITY_D ATEDate of last employer address update EMPR_ADDR_CODESPRADDR_ATYP_CO DEEmployer™s address type codeEMPR_HOUSE_NUMBERSPRADDR_HOUSE_NUM BERUnique number assigned to employer™s building on a street or in an area and used as part of the postal address in some countries EMPR_STREET1 SPRADDR_STREET_LINE1First line of employer™s mailing address EMPR_STREET2 SPRADDR_STREET_LINE2Second line of employer™s mailing address ATVTPFD Field NameBanner Data Field Description /n 18Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files EMPR_STREET3 SPRADDR_STREET_LINE3Third line of employer™s mailing address EMPR_STREET4 SPRADDR_STREET_LINE4Fourth line of employer™s mailing address EMPR_CITYSPRADDR_C ITYEmployer™s city EMPR_STATE SPRADDR_STAT_CODE Employer™s state EMPR_ZIP SPRADDR_ZIP Employer™s ZIP/postal code. These are the first five digits of SPRADDR_ZIP. EMPR_ZIP4SPRADDR_ZIP Additional four digits for ZIP/ postal code. These are the last four digits of SPRADDR_ZIP. EMPR_AREA_CODESPRTELE_PHONE_AREA Employer™s phone area code for the telephone type code specified as a parameter EMPR_PHONE SPRTELE_PHONE_NUMBEREmployer™s phone number for the telephone type code specified as a parameter EMPR_PHONE_EXTSPRTELE_PHONE_EXT Employer™s phone extension for the telephone type code specified as a parameter EMPR_PHONE_ALL SPRTELE_PHONE_ ALLEmployer™s area code, number, and extension for the telephone type code specified as a parameter EMPR_PHONE_COUNTRY_ CODE SPRTELE_CTRY_CODE_PHONECo de that designates the region and country of the employer™s telephone number EMPR_EMAIL GOREMAL_EMAIL_ADDRESSEmployer™s e-mail address for the e-mail address type code specified as a parameter. E-mail address must be the primary one (primary indicator must be selected). EMPR_EMAIL_CODEGOREMAL_EMAL_CO DEEmployer™s e-mail type code EXCL_CODE APREXCL_EXCL_CODE Exclusions (including do not mail/phone, do not include, do not solicit)EXCL_END_DATE APREXCL_END_DATE Date when the exclusion ends ATVTPFD Field NameBanner Data Field Description /n 19Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files EXCL_REASON APREXCL_REASON Reason that the exclusion applies to the IDEXCL_START_DATEAPREXCL_DATE Date when the exclusion starts INST_CODEAPRADEG_SBGI_CODE In stitutions attended code (including current institution) INST_DESCSTVSBGI_DESC Institutions attended description (including current institution)JOB_CATEGORY APREHIS_JOBC_CODE Occupation/career code (job category) JOB_SICC_CODEAPREHIS_SICC_CODE Occupation/career code (SIC code) JOB_TITLE APREHIS_EMPL_POSITIONEmployee™s job title LOST_INDICATOR LOST_INDICATOR Indicator that all mailing address records are inactive MAIDEN_NAME_FIRSTSPRIDEN_FIRST_N AME Maiden first name (where the name type on GTVNTYP has the value MAIDEN )MAIDEN_NAME_LASTSPRIDEN_LAST_NAME or APBCONS_MAIDEN_LAST_NAME Maiden last name (where the name type on the Name Type Validation Form (GTVNTYP) has the value MAIDEN ) or the maiden name information from the APBCONS table if a record exists MAIDEN_NAME_MIDDLESPRIDEN_MIMaiden middle name (where the name type on GTVNTYP has the value MAIDEN )MAIDEN_NAME_SUFFIXSPBPERS_NAME_SU FFIXMaiden suffix (where the name type on GTVNTYP has the value MAIDEN )MAJORAPRAMAJ_MAJR_CODEMajor code (repeating value if a person has more than one major code) NAME_FIRSTSPRIDEN_FIRST_NAMEFirst name NAME_LASTSPRIDEN_LAST_NAMELast name NAME_MIDDLESPRIDEN_MIMiddle name NAME_PREFIXSPBPERS_NAME_PREFIXName prefix ATVTPFD Field NameBanner Data Field Description /n 20Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files Steps to extract data from Banner Use the following steps to extract data from Banner: ŁfiStep 1 -Identify the IDs to be extractedfl on page20 ŁfiStep 2 - Run the Directory Data Ex tract Process (APPDEXT)fl on page21 ŁfiStep 3 - Review the outputfl on page22 The following sections provide deta iled instructions for each step. Step 1 -Identify the ID s to be extractedYou must create a population selection or a manual data file to identify the IDs to be extracted: ŁYou can build a population selection to identify the IDs that you want to extract from the Banner database. You can also copy and c hange an existing population selection. A population selection is a set of rules used to select IDs from the Banner database for reports, processes, and letters. A populati on selection is uniquely identified by an application, selection ID, and creator ID. For more information, refer to the fiProcessingfl chapter of the Banner General User Guide .ŁYou can create a manual data file of IDs that you want to extract from the Banner database. The Banner IDs to use for the record selection must be stor ed in the first field of the data file. NAME_SUFFIXSPBPERS_NAME_SUFFIXName suffix NAME_SURNAME_PREFIXSPRIDEN_SURNAME_PREFIXLast name prefix PREF_ADDRESS_CODEAPBCONS_ATYP_CO DE_PREFPreferred address code PREFERRED_CLASSAPBCONS_PREF_CLA SPreferred class (repeating value if a person has more than one preferred class) SCHOOL_CODEAPRADEG_COLL_CO DESchool/college code (repeating value if a person has more than one school/ college code) SP_NAME_FIRSTAPRCSPS_FIRST_NAMESpouse™s first name SP_NAME_LASTAPRCSPS_LAST_N AMESpouse™s last name SP_NAME_MIDDLEAPRCSPS_MI_N AMESpouse™s middle name SP_SURNAME_PREFIXAPRCSPS_SURNAME_P REFIXSpouse™s last name prefix ATVTPFD Field NameBanner Data Field Description /n 21Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files Step 2 - Run the Directory Da ta Extract Process (APPDEXT) The Directory Data Extract Pr ocess (APPDEXT) extracts in formation from Banner. The Data Field Position Rules Form (AGATPFD) defines which fields are extracted and the order in which the data elements appear on the output file. The output file can be fixed length or character delimited. APPDEXT is run from the Process Submissi on Controls Form (GJAPCTL) with the following parameters: Parameter Description 01File Code File code for the appropriate data source. Select List or the Values pull-down arrow to see valid values from the Data File Validation Form (ATVTAPE). Required. 02Data File NameName of the file you are creating. Optional. 03Application CodeApplication associat ed with a population selection. (A population selection is a set of rules used to select Banner IDs from the database. A population selection is uniquely identified by an application code, selection ID, and creator ID combination.) Required if you are using a population selection to identify the Banner IDs to be extracted. 04Selection ID Population selection ID. The population selection must already exist. Required if you entered an application code.05Creator ID User ID of the person who created the population selection. Required if you entered an application code. 06User ID User ID of the person who is running the population selection. Required if you entered an application code. 07Path of Manual Data FileComplete file location of the manual data file that contains the Banner IDs to be extracted. Required if you are using a data file, rather than a population selection, to identify the IDs to be extracted. 08Manual ID File Name of the manual data file that contains the Banner IDs to be extracted. A unique identifier must be the first nine digits. Required if you are using a data file, rather than a population select ion, to identify the IDs to be extracted. APPDEXT only runs pr operly if this f ile contains valid Banner IDs. /n 22Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files For more in formation about APPDEXT, refer to the Banner Advancement User Guide .Step 3 - Review the output Review the file produced by APPDEXT and see if it appears to be correct. You can also look at the output report. Contents of the report depend on whether the file is fixed length or character delimited: 09Address TypeType of address (f or example, billi ng, mailing) for record selection of address information, if you included address in the extract definition. Select List or the Values pull-down arrow to see valid values from the Address Type Validation Form (STVATYP). Optional. This is a repeating parameter. You can specify more than one type of address. Be sure to define each occurrence. For more inform ation about occurrences, refer to fiUsing occurrencesfl on page13 .10Phone TypeType of telephone number (for example, business) for record selection of telephone information, if you included telephone in the extract definition. Select List or the Values pull-down arrow to see valid values from the Telephone Type Validation Form (STVTELE). Optional. This is a repeating parameter. You can specify more than one type of telephone number. Be sure to define each occurrence. For more information about occurrences, refer to fiUsing occurrencesfl on page13 .11E-mail TypeType of e-mail address (for example, home) for record selection of e-mail informat ion, if you included e-mail address in the extract definition. Select List or the Values pull-down arrow to see valid values from the E-mail Address Type Validation Form (GTVEMAL). Optional. This is a repeating parameter. You can specify more than one type of e-mail address. Be sure to define each occurrence. For more information about occurrences, refer to fiUsing occurrencesfl on page13 .12Maiden CodeCode that represents the maiden name (as defined on the Name Type Validation Form (GTVNTYP), or on ABPCONS_MAIDEN_LAST_NAME if your institution doesn™t use GTVNTYP), if you included maiden names in the extract definition. Optional. Parameter Description /n 23Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files If there are problems with the file, ma ke your changes and run APPDEXT again, as described in step 2. Many problems can be traced to an incorrect f ile definition. Check the file definition on the Data Field Position Rules Form (AGATPFD). Make sure all fields are defined and that you are using occurrences correctly. For more information, refer to fiSet up a data load or a data extractfl on page8 . Make sure that the job submission parameters are provided as needed, and that multiple occurrences are noted and included if repeat ing data is included in the file definition. Load matching gift data Employers can agree to match certain gifts under certain circumstances up to certain amounts. This information can be stored in Banner. You should load the matching gift policies and procedures of various employers into Banner on a regular basis so you can determine how much money your institution can expect to receive from these employers. Your institution can subscribe to one or both of the following databases that provide the policies and procedures: ŁHigher Education Publications Company (HEP) GiftPlus database ŁCouncil for Advancement and Support of Education (CASE) National Clearinghouse for Matching Gift Information database Third-party vendors also provide matching gift information. The file returned by a vendor includes the special matching gi ft ID that will be loaded into Banner with th e rest of the data. The vendor should also send you information from the GiftPlus or National Clearinghouse for Matching Gift Information database. Fixed Length File AGRTPFD_TFPD_CODEData file field name ATVTPFD_DESCData field names description AGRTPFD_START_POSStart posi tion of data file field AGRTPFD_END_POSEnd position of data file field Character Delimited File AGRFPFD_TPFD_CODEData file field name ATVTPFD_DESCData field names description AGRTPFD_START_POSField number AGRTPFD_OCCNumber of times the data repeats (occurrence) /n 24Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files Before loading data, you must perform the setup steps described in fiSet up a data load or a data extractfl on page8 .The Matching Gift Data Load Report (AGPMATC) lo ads matching gift data to Banner. After the data is loaded into Banner, you can see the matching gift data on Banner forms: ŁIf a company matches gifts, it is noted on the Matching Gifts window of the Advancement Organization Header Form (AOAORGN). ŁIf a percentage is included in the Organization ID Matching Gift Percentage field on AOAORGN, the matching gift company ID an d name are displayed on the Employment History Form (APAEHIS) for the employee ( ŁMatching gift information is displayed on the Matching Gift Information Form (AOAMTCH).Data that can be loaded AGPMATC can load the following data into Banner. The various third-party vendors work with a subset of these data fields. These fields are delivered as part of the base line product and are the only fields that can be inserted into the database. The ATVTPFD fiel d names are used to define the file layout on the Data Field Position Rules Form (AGATPFD). ATVTPFD Field Name Description ADD_LINE1Address street line 1 ADD_LINE2Address street line 2 ALIASAlias or abbreviation of name from GTVNTYP ANN_EMPTotal annual maximum matching gift amount per employee ATITLE Administrative title BAN_NAMEBanner organization name (this does not replace the key block version of the name) BAN_PIDMBanner PIDM CITYCityCOMMENT_BLOCK1 Comments block 1, displayed on the Comments window on AOAMTCH COMMENT_BLOCK2 Comments block 2, displayed on the Comments window on AOAMTCH COMMENT_BLOCK3 Comments block 3, displayed on the Comments window on AOAMTCH /n 25Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files COMMENT_BLOCK4 Comments block 4, displayed on the Comments window on AOAMTCH COUNTRY CountryEMAILE-mail address on APAEMAL EXTExtension for telephone FISCALYR Fiscal yearFNAMEFirst name of contact on AOAORGN FUNDNAME Matching gift or foundation name from AGPMATC parameter 04 (Name Type for Fund). AGPMATC creates a SPRIDEN record with an alternate name of the type specified in the parameter. HOMEPAGE URL of the home page on APAEMAL HOUSE_NUMBERUnique number assigned to each building on a street or in an area and used as part of the postal address in some countries LNAME Last name of contact on AOAORGN MAXIMUMMaximum matching gift amount on AOAORGN MG_ACKNOWLEDGE_GIFT_RECEIP TIndicator that a gift receipt acknowledgement is required for every matching gift on AOAORGN MG_ACKNOWLEDGE_LETTER Indicator that an acknowledgement letter is required for every matching gift on AOAORGN MG_AFFILIATION_ALUMNI Code that specif ies if the employee must be an alumnus for the advancement organization to match gifts. This must be a valid code on ATVMAST, and it is displayed on the Alumni Status block under the Eligibility Requirements window on AOAMTCH. MG_AFFILIATION_ATTEND Code that specif ies if the employee™s spouse or children must attend the institution for the advancement organization to match gifts to that institution. This must be a valid code on ATVMPUR, and it is displayed on the Related Purpose block under the Eligibility Requirements window on AOAMTCH. MG_AFFILIATION_GRADUATE Code that spec ifies if the employee must be a graduate of an institution for the advancement organization to match gifts to that institution. This must be a valid code on ATVMAST, and it is displayed on the Alumni Status block under the Eligibility Requirements window on AOAMTCH. ATVTPFD Field Name Description /n 26Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files MG_AFFILIATION_MEMBER Code that spec ifies if the employee must be a member for the advancement organization to match gifts to that institut ion. This must be a valid code on ATVMAST, and it is displayed on the Alumni Status block under the Eligibility Requirements win dow on AOAMTCH.MG_AFFILIATION_PATIENT Code that spec ifies if the employee must have received patient care for the advancement organization to match gifts to that institution. This must be a valid code on ATVMAST, and it is displayed on the Alumni Status block under the Eligibility Requirements window on AOAMTCH. MG_ATHLETICS_BUILDING Code that specifies if the advancement organization matches gifts made to building funds for an athletics program. This must be a valid code on ATVMPUR, and it is displayed on the Related Purpose block under the Eligibility Requirements win dow on AOAMTCH.MG_ATHLETICS_PROGRAM Code that specifies if the advancement organization matches gifts made to an athletics program. This must be a valid code on ATVMPUR, and it is displayed on the Related Purpose block under the Eligibility Requirements window on AOAMTCH. MG_ATHLETICS_SCHOLAR Code that specifies if the advancement organization matches gifts made to scholarships for an athletics program. This must be a valid code on ATVMPUR, and it is displayed on the Related Purpose block under the Eligibility Requirements win dow on AOAMTCH.MG_DIST_ANNUALLY Total annual di stribution, displayed in the Organization Maximum Per Institution Per Year field on the Matching Gifts window on AOAORGN. MG_DIST_CONTINUOUS Indicator that specifies if the advancement organization continually distributes funds when a form is provided. Displayed on the Matching Gifts window on AOAORGN MG_DIST_MONTHLY Total monthly di stribution, displayed on the Matching Gifts window on AOAORGN MG_DIST_QUARTERLY Total quarterly distribution, displayed on the Matching Gifts window on AOAORGN MG_DIST_SEMI_ANNUALLY Total semi-annual distribution, displayed on the Matching Gifts window on AOAORGN ATVTPFD Field Name Description /n 27Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files MG_ELIGIBILITY_FLAG_ALL Code that specif ies if gifts from all employees are matched. This must be a valid code on ATVMERQ, and it is displayed on the Employment Status block under the Eligibility Requirements win dow on AOAMTCH.MG_ELIGIBILITY_FLAG_ALL_FT Code that specifies if gifts from full-time employees are matched. This must be a valid code on ATVMERQ, and it is displayed on the Employment Status block under the Eligibility Requirements win dow on AOAMTCH.MG_ELIGIBILITY_FLAG_ALL_FT_ SALARIEDCode that specifies if gifts from salaried employees are matched. This must be a valid code on ATVMERQ, and it is displayed on the Employment Status block under the Eligibility Requirements win dow on AOAMTCH.MG_ELIGIBILITY_FLAG_ALL_PT Code that specifies if gifts from part-time employees are matched. This must be a valid code on ATVMERQ, and it is displayed on the Employment Status block under the Eligibility Requirements win dow on AOAMTCH.MG_ELIGIBILITY_FLAG_ELIG_SPO USECode that specifies if gifts from the spouses of employees are matched. This must be a valid code on ATVMERQ, and it is displayed on the Employment Status block under the Eligibility Requirements win dow on AOAMTCH.MG_ELIGIBILITY_FLAG_RETIREDC ode that specifies if gift s from retired employees are matched. This must be a valid code on ATVMERQ, and it is displayed on the Employment Status block under the Eligibility Requirements win dow on AOAMTCH.MG_ELIGIBILITY_INST_4YR Code that specifie s if gifts to four-year institutions are matched. This must be a valid code on ATVMEDU, and it is displayed on the Levels block under the Eligibility Requirements window on AOAMTCH.MG_ELIGIBILITY_INST_COMM_JRC ode that specifies if gifts to community colleges or junior colleges are matched. This must be a valid code on ATVMEDU, and it is displayed on the Levels block under the Eligibility Requirements win dow on AOAMTCH.MG_ELIGIBILITY_INST_ELEM_SCHOO LCode that specifies if gifts to elementary schools are matched. This must be a valid code on ATVMEDU, and it is displayed on the Levels block under the Eligibility Requirements window on AOAMTCH.ATVTPFD Field Name Description /n 28Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files MG_ELIGIBILITY_INST_GRADPROFCode that specifies if gifts to graduate or professional schools are ma tched. This must be a valid code on ATVMEDU, and it is displayed on the Levels block under the Eligibility Requirements win dow on AOAMTCH.MG_ELIGIBILITY_INST_SEC_SCHOOLCode that specifies if gi fts to secondary schools are matched. This must be a valid code on ATVMEDU, and it is displayed on the Levels block under the Eligibility Requirements window on AOAMTCH.MG_ELIGIBILITY_INST_SEMINARYCode that sp ecifies if gifts to seminaries are matched. This must be a valid code on ATVMEDU, and it is displayed on the Levels block under the Eligibility Requirements window on AOAMTCH.MG_ELIGIBILITY_INST_TECH_SCHOOLCode that specifies if gifts to technical schools are matched. This must be a valid code on ATVMEDU, and it is displayed on the Levels block under the Eligibility Requirements window on AOAMTCH.MG_IDHEP-CASE ID on AOAORGN MG_NONPROFIT_CHARITIES Code that sp ecifies if gifts to charities are matched. This must be a valid code on ATVMNED, and it is displayed on the Non- Educational Institutions block under the Associations and Institutions window on AOAMTCH. MG_NONPROFIT_CULTURAL Code that specifie s if gifts to cultural institutions are matched. This must be a valid code on ATVMNED, and it is displayed on the Non- Educational Institutions block under the Associations and Institutions window on AOAMTCH. MG_NONPROFIT_ENV_CONSERVCode that spec ifies if gifts to environmental or conservation organizations are matched. This must be a valid code on ATVMNED, and it is displayed on the Non-Educational Institutions block under the Associations and Institutions window on AOAMTCH. MG_NONPROFIT_FRAT_SOR Code that specifies if gifts to fraternity or sorority educational foundations ar e matched. This must be a valid code on ATVMNED, and it is displayed on the Non-Educational Institutions block under the Associations and In stitutions window on AOAMTCH. ATVTPFD Field Name Description /n 29Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files MG_NONPROFIT_HEALTHCARECode that specif ies if gifts to non-profit health care organizations are matched. This must be a valid code on ATVMNED, and it is displayed on the Non-Educational Instit utions block under the Associations and Institutions window on AOAMTCH. MG_NONPROFIT_MUSEUMCode that spec ifies if gifts to museums are matched. This must be a valid code on ATVMNED, and it is displayed on the Non- Educational Institutions block under the Associations and Institutions window on AOAMTCH. MG_NONPROFIT_PERF_ARTSCode that spec ifies if gifts to performing arts organizations are matched. This must be a valid code on ATVMNED, and it is displayed on the Non-Educational Institutions block under the Associations and Institutions window on AOAMTCH. MG_NONPROFIT_RADIO_TVCode that specifies if gifts to public radio and TV stations are matched. This must be a valid code on ATVMNED, and it is displayed on the Non- Educational Institutions block under the Associations and Institutions window on AOAMTCH. MG_NONPROFIT_RELIGIOUSCode that specifies if gifts to religious organizations are matched. This must be a valid code on ATVMNED, and it is displayed on the Non-Educational Institutions block under the Associations and Institutions window on AOAMTCH. MG_NONPROFIT_SOCIALSERVICECode that sp ecifies if gifts to social service organizations are matched. This must be a valid code on ATVMNED, and it is displayed on the Non-Educational Institutions block under the Associations and Institutions window on AOAMTCH. MG_PROCEDURE_DONOR_CHECKCode that in dicates if the donor must provide a check and a form to the advancement organization for it to match the donor™s gifts. This must be a valid code on ATVMPRO, and it is displayed on the Procedures window on AOAMTCH. ATVTPFD Field Name Description /n 30Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files MG_PROCEDURE_DONOR_PHONECode that indi cates if the donor must contact the advancement organization by telephone for it to match the donor™s gifts. This must be a valid code on ATVMPRO, and it is displayed on the Procedures window on AOAMTCH. MG_PROCEDURE_INST_FORMCode that indica tes if the institution receiving the matching gift must file a form with the advancement organization after the institution receives the gift. This must be a valid code on ATVMPRO, and it is displayed on the Procedures window on AOAMTCH. MIMiddle initial of the contact person at the company MINIMUMMinimum matching gift amount on AOAORGN ORGNAMEHEP-CASE parent company name on AOAORGNPHONETelephone number of t he contact person at the company PHONE_COUNTRY_CODECode that design ates the region and country of the telephone number of the contact person at the company PTITLEPersonal title of the contact person at the company RATIOMatching gift ratio on AOAORGN SNAME_PREFIXPrefix that preced es last name of the contact person at the company STATEState of the contact person at the company SUFFIXName suffix of the contact person at the company ZIP4Last four digits of th e ZIP/postal code of the contact person at the company ZIP5First five digits of the ZIP/postal code of the contact person at the company ZIPCComplete ZIP/postal code of the contact person at the company ATVTPFD Field Name Description /n 31Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files The following layout for the HEP data file is pr ovided for your convenience. It contains all of the fields listed above, except for COUNTRY, EMAIL, and PHONE_COUNTRY_CODE. HEP Field NameBanner Field Name ALUMIDBAN_PIDMCONAMEBAN_NAMEIDMG_IDORGNAME ORGNAME AKAALIASFUNDNAME FUNDNAME PTITLEPTITLEFNAMEFNAME MIMILNAME LNAME SUFFIXSUFFIXATITLE ATITLE ADLINE1 ADD_LINE1 ADLINE2 ADD_LINE2 CITYCITYSTATE STATE ZIP5ZIP5ZIP4ZIP4PHONEPHONEEXTEXTMINIMUMMINIMUM MAXIMUMMAXIMUM ANNEMP ANN_EMPRATIO RATIO FISCALYR FISCALYR EL01 MG_ELIGIBILITY_FLAG_ALL EL02 MG_ELIGIBILITY_FLAG_ALL_FT EL03MG_ELIGIBILTY_FLAG_ALL_FT_SALARIED EL04 MG_ELIGIBILITY_FLAG_ALL_PT /n 32Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files EL05 MG_ELIGIBILITY_FLAG_RETIRED EL06 MG_ELIGIBILITY_FLAG_ELIG_SPOUSE EE01MG_ELIGIBILITY_INST_4YR EE02MG_ELIGIBILITY_INST_GRADPROF EE03MG_ELIGIBILITY_INST_COMM_JR EE04MG_ELIGIBILIT Y_INST_SEMINARY EE05MG_ELIGIBILITY_ INST_SEC_SCHOOLEE06MG_ELIGIBILITY_INST_ELEM_SCHOOL EE07MG_ELIGIBILITY_INST_TECH_SCHOOL PR01MG_PR0CEDURE_DONOR_CHECK PR02MG_PR0CEDURE_INST_FORM PR03MG_ACKNOWLEDGE_GIFT_RECEIPT PR04MG_ACKNOWLEDGE_LETTER PR05MG_PR0CEDURE_DONOR_PHONE AT01 MG_ATHLETICS_PROGRAM AT02 MG_ATHLETICS_SCHOLAR AT03 MG_ATHLETICS_BUILDING AF01 MG_AFFILIATION_ALUMNI AF02 MG_AFFILIAT ION_GRADUATE AF03 MG_AFFILIATION_ATTEND AF04 MG_AFFILIATION_MEMBER AF05 MG_AFFILIATION_PATIENT OT01MG_NONPROFIT_HEALTHCARE OT02MG_NONPROFIT_MUSEUM OT03MG_NONPROFIT_SOCIALSERVICE OT04MG_NONPROFIT_PERF_ARTS OT05MG_NONPROFIT_RADIO_TV OT06MG_NONPROFIT_RELIGIOUS OT07MG_NONPROFIT_ENV_CONSERV OT08MG_NONPROFIT_CULTURAL OT09MG_NONPROFIT_CHARITIESHEP Field NameBanner Field Name /n 33Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files Steps Use the following steps to load matching gift data to Banner: ŁfiStep 1 - Create the extract filefl on page33 ŁfiStep 2 - Review contact type codesfl on page34 ŁfiStep 3 - Copy the returned data file to an appropriate directoryfl on page34 ŁfiStep 4 - Verify the file definitions and input datafl on page35 ŁfiStep 5 - Run the MG Data Load Report (AGPMATC) in report modefl on page39 ŁfiStep 6 - Review the output reportsfl on page42 ŁfiStep 7 - Run the MG Data Load Report (AGPMATC) in update modefl on page51 ŁfiStep 8 - (Optional) Load and link subsidiary organizationsfl on page51 ŁfiStep 9 - (Optional) Review employee reco rds for potential matching giftsfl on page55 The following sections provide deta iled instructions for each step. Step 1 - Create the extract file Run the MG Data Extract Process ( agpexmg.sql ) to extract organization records and create a fixed length output file of the advancement or ganizations with which your institution interacts. The first data element in the output file is a unique number (PIDM) that identifies each organization to Banner. The organization name is the second data element. It also extracts any alternate names, nick names, acronyms, or previous names (the change indicator on the SPRIDEN table is null or N).OT10MG_NONPROFIT_FRAT_SOR DS01MG_DIST_CONTINUOUS DS02MG_DIST_MONTHLY DS03MG_DIST_QUARTERLY DS04MG_DIST_ANNUALLY DS05MG_DIST_SEMI_ANNUALLY COMMENT1COMM ENT_BLOCK1 COMMENT2COMM ENT_BLOCK2 COMMENT3COMM ENT_BLOCK3 COMMENT4COMM ENT_BLOCK4 HEP Field NameBanner Field Name /n 34Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files If there is no PIDM for an employer record, the field is blank in the data file. This record requires special processing when the file is re turned. It cannot be loaded into Banner via the automatic load process without a PIDM. Assign a name to the output file when you run the script. You can name the file MGEXTxxxxxx.dat , where xxxxxx is the date when the script is run in MMDDYY format (for example, MGEXT071308.dat ). This enables you to maintain historical records, if necessary. Data on the extract file comes from the SPRIDEN and APREHIS tables: ŁThe process looks for SPRIDEN_PIDM and SPRIDEN_LAST_NAME (where the non- person indicator is Y, indicating that the PIDM belongs to an organization). It includes all those records on the file. ŁIf the process does not find SPRIDEN_PIDM, it looks for APREHIS_PIDM and APREHIS_EMPR_NAME. It checks to see if there are any duplicates (where APREHIS_EMPR_NAME is the same as SPRI DEN_LAST_NAME); it does not include those records on the file. This is the file format: This is an example of data on the file: 11111 Test Corporation After the file is created, se nd it to HEP, CASE, or anot her vendor. The vendor adds matching gift data for each organization to the file and returns it to you. The PIDM must remain on this file so Banner can load the correct data for each organization. Step 2 - Review contact type codes The Advancement Organization Contact Type Validation Form (ATVOCON) contains the valid Banner contact type codes. Make sure that any codes inclu ded on the file you receive from the vendor exist on this form. These codes are assigned to secondary cont acts for an organization on the Advancement Organization Header Form (AOAORGN). Step 3 - Copy the returned data fi le to an appropriate directoryCopy the returned file to a directory where Banner can access it. Later, when you run the Matching Gift Company Data Load Proce ss (AGPMATC), you must specify both the location and the filename as parameters. PIDMNUMBER(8) NAMECHARACTER(60) /n 35Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files Step 4 - Verify the file definitions and input data The Data Definition File List Process (APPDFLS) show s the data on the incoming data file with the corresponding information from the Da ta Field Position Rules Form (AGATPFD). The format of the report produced by APPDFLS is similar to that of AGATPFD but includes the actual data values for each field. Use APPDFL S to see if your file definition is set up correctly on AGATPFD, and to check the incoming data on the file. The input file can be fixed length or character delimited. APPDFLS is run from the Process Submission Controls Form (GJAPCTL) with the following parameters: Parameter Description 01File Code File code for the appropriate data source. Select List or the Values pull-down arrow to see valid values from the Data File Validation Form (ATVTAPE). Required. 02Path of Data File - Part 1Directory where the data load file is located (up to 30 characters). If the data file path is longer than 30 characters, parameters 08 and 09 are available to provide additional data file path details. Required. 03Data File NameExact name of t he file, including the extension. Required.04Data Source IdentifierCode that represents the data source. Select List or the Values pull-down arrow to see valid values from the Data Source Identi fier Validation Form (ATVDSRC). Required. 05Start Record NumberNumber of the firs t record you want to process in the data file. This allows you to check a large data file in sections, rather than look at the whole file at one time. Optional. 06End Record NumberNumber of the last record you want to process in the data file. Use this with the Start Record Number to look at part of a large incoming file. Optional. 07Header Record ExistsCode that indicate s if the input file has a header record that Banner should not process as data. Y - Input file has a header record that should not be processed as data. N - First record on the file is actual data. This information is found on the incoming data file documentation from the vendor. Optional. /n 36Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files Output from the process shows each field name and the data in that field. If the file is fixed length, it also shows the start position, end po sition, and occurrence. If the file is character delimited, it shows the field number and th e occurrence. For more information about occurrences, refer to fiUsing occurrencesfl on page13 .If the data does not look correct (for example, some characters that should appear in the first field actually appear in the second), t hen go back to AGATPFD and change the file definition for the incoming data file. If everything is correct, you can proceed. For more in formation about APPDFLS, refer to the Banner Advancement User Guide .08Path of Data File - Part 2Additional details (up to 30 characters) for the directory where the data load file is located. Used with the Path of Data File - Part 1 parameter when the data file path is longer than 30 characters. This entry is concatenated to the end of the details entered in part 1. Optional. 09Path of Data File - Part 3Additional details (up to 30 characters) for the directory where the data file is located. Used with the Path of Data File - Part 1 and Part 2 parameters when the data file path is longer than 60 characters but less than 91 characters. This entry is concatenated to the end of the details entered in part 2. Optional. Parameter Description /n 37Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files 02-JUN-2009 BANNER University PAGE 1 Rel 8.2 File Definition Verification APPDFLS Harris Publishing Column Name Value Start End Occurs BAN_PIDM 7 1 9 1 NAME_PREFIX 11 30 1 NAME_FIRST Matthew All 31 59 1 NICKNAME 61 75 1 NAME_LAST en 76 104 1 NAME_MIDDLE R 105 111 1 EMAIL mallenb@test.com 112 127 1 ADDR_STREET1 11111111 Long Street 128 150 1 ADDR_CITY Masonlong 151 181 1 ADDR_STATE OH 182 183 1 ADDR_COUNTRY 184 216 1 ADDR_ZIPC 45040 217 221 1 ADDR_PHONE_ALL 5131223345 222 231 1 CHILD_NAME_FIRST Amanda 233 254 1 CHILD_DECEASED_IND 255 255 1 CHILD_NAME_LAST Walker 256 274 1 INSTITUTION Rhodes College 275 296 1 DEGREE BA 297 298 1 Total Number of Records Reviewed: 1 End of Listing /n 38Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files 02-JUN-2009 BANNER University PAGE 2 Rel 8.2 File Definition Verification APPDFLS Harris Publishing * * REPORT CONTROL INFORMATION * * parameter Message USER:........................ CSMITH Parameter Name Value Message _____ ___ ________ Parameter Seq No File Code FIXLOAD Path of Data File - Part 1 /export/home/cnorris/ Data File Name /fixlong.dat Data Source Identifier HARRIS Start Record Number 1 End Record Number 9999999 Header Record Exists N Path of Data File - Part 2 Path of Data File - Part 3 Line Count 45 /n 39Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files Step 5 - Run the MG Data Load Repor t (AGPMATC) in report modeBefore loading the matching gift information in to Banner, you should test to make sure the data will load cleanly. Run the lo ad process in repo rt mode and review the various reports. AGPMATC is run from the Process Submi ssion Controls Form (GJAPCTL) with the following parameters: Parameter Description 01File Code File code for the appropriate data source. Select List or the Values pull-down arrow to see valid values from the Data File Validation Form (ATVTAPE). Required. 02Name Type for Organization Organization name type code to be used in the data load. Select List or the Values pull-down arrow to see valid values from the Na me Type Validation Form (GTVNTYP). It is possible for a matching gift organization to have multiple names. This parame ter allows you to handle situations where a PIDM appears on the returned file with a different name than any of those currently in Banner for that PIDM. If you enter a value for this parameter, AGPMATC adds a SPRIDEN record for the PIDM with the name type you specify here. Optional. 03Name Type for AliasAlias name type code to be used in the data load. Select List or the Values pull-down arrow to see valid values from the Name Type Validation Form (GTVNTYP).It is possible for a matching gift organization to have multiple names. This parame ter allows you to handle situations where a PIDM appears on the returned file with an alias that does not currently exist in Banner for that PIDM. If you enter a value for this parameter, AGPMATC adds a SPRIDEN re cord for the PIDM with the name type you specify here. Optional. 04Name Type for FundFund name type code to be used in the data load. Select List or the Values pull-down arrow to see valid values from the Name Type Validation Form (GTVNTYP).It is possible for a matching gift organization to have multiple names. This parame ter allows you to handle situations where a PIDM appears on the returned file with a fund name that does not currently exist in Banner for that PIDM. If you enter a value for this parameter, AGPMATC adds a SPRIDEN record for the PIDM with the name type you specify here. Optional. /n 40Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files 05Secondary Contact CodeSecondary contact type code to be used in the data load. Select List or the Values pull-down arrow to see valid values from the Organization Contact Type Validation Form (ATVOCON). Optional. Banner lets you choose which subsets of matching gift rules you want to load via parameters 06 through 09. 06Eligible EmployeeIndicator that det ermines whether to load rules that determine, at runtime, which employees are eligible to participate in the matching gift program. These rules appear on the Eligibility Requirements window on AOAMTCH. Required.Y - Load rules. N - Do not load rules (default). 07AthleticsIndicator that determi nes whether to load rules that determine, at runtime, how the organization handles donations for athletics. These rules appear on the Eligibility Requirements window on AOAMTCH. Required.Y - Load rules. N - Do not load rules (default). 08Affiliation Indicator that determi nes whether to lo ad rules that determine, at runtime, whic h affiliations are required for matching gifts. These rules appear on the Eligibility Requirements window on AOAMTCH. Required. Y - Load rules. N - Do not load rules (default). 09Non eligibilityIndicator that dete rmines whether to load rules that determine, at runtime, which employees are ineligible for the matching gift program. These rules appear on the Eligibility Requiremen ts window on AOAMTCH. Required.Y - Load rules. N - Do not load rules (default). 10Report/UpdateCode that determines whether the database is updated when the process is run. R - Print report; do not update database (default). U - Print report; update database. Parameter Description /n 41Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files For more information about AGPMATC, refer to the Banner Advancement User Guide .11Source - HEP/CASESource of the returned file: H - HEP (default) C - CASE12HEP/CASE in File NameLocation to which you copied the source file. It must be the name of the file and the path to it. Required. 13Address TypeAddress type (for the matching gift organization) of the records to be loaded into the database. It must be a valid type code from the Address Type Code Validation Form (STVATYP). If the incoming data file contains an address type that matches this parameter value, and it does not already exist in Banner, AGPMATC adds the new address. If the incoming data file contains an address that matches this value and it already exists but the information is different, Banner makes the existing address inactive and creates a new record with the new information. Required. 14Email TypeE-mail address type (for the matching gift organization) of the records to be loaded. It must be a valid type code from the E-mail Address Type Validation Form (GTVEMAL). If the incoming data file contains an e-mail address that matches an existing Banner record with this e- mail type, the details are not loaded. (It looks for a match on e-mail address and type.) If the incoming data file contains an e-mail address that does not match an existing Banner record with this e-mail type, a new e- mail address record is inserted. Required. 15URL TypeURL type (for the matching gift organization) of the records to be loaded. It must be a valid type code from the E-mail Address Type Validation Form (GTVEMAL). If the incoming data file contains a URL that matches an existing Banner record with this type code, the details are not loaded. (It looks for a match on URL and type.) If the incoming data file contains a URL that does not match an existing Banner record with this type, a new URL record is inserted. Required. Parameter Description /n 42Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files Step 6 - Review the output reports Review the following AGPMATC output reports for any errors: Make any changes necessary, based on what th e reports indicate. If everything is correct, then you can proceed. agpmatcXXXX.lisThis report displays the matching gift inform ation that was loaded from a parent company file into the Banner tables. agpmatc_XXXX.lis agpmatc_XXXX.lis2 agpmatc_XXXX.lis3 agpmatc_XXXX.lis4 agpmatc_XXXX.lis5 /n 43Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files 23-FEB-2009 Watermark University PAGE 1 MG Data Load Report AGPMATC Update Mode Source ID Banner ID Company Name Contact Name and Title A00022438 AMD Mr Fundname #124 00003 P.O. Box 7586 Street Line 3 Official Name Street Line 4 AMD Princeton, NJ 08543 8005008199 Alias Distribution Procedure A C Min. Match Month Max. Match Amount Ratio Max Tot. Emp. Ann Employee Status Other Non-Profit $ 25.00 $ 1500.00 100% $ 0.00 R 3 5 6 4 2 Fiscal Year Eligible Ed. Inst Athletics Employee Affiliation Acknowledgements G C S D E T G Y- Receipt required. Email Address: Homepage URL: Comments: Source ID Banner ID Company Name Contact Name and Title A00022440 Ms. Ma Swope Matching Gift Coordinator Fundname #124 00003 4333 Edgewood Rd. NE AEGON USA Charitable Foundation Street Line 3 Official Name USA Cedar Rapids, ID 52499 3193988935 Alias Distribution Procedure M Min. Match Month Max. Match Amount Ratio Max Tot. Emp. Ann Employee Status Other Non-Profit $ 25.00 $ 1500.00 100% $ 0.00 F P R Fiscal Year Eligible Ed. Inst Athletics Employee Affiliation Acknowledgements G C S D E G Y- Receipt required. Email Address: Homepage URL: Comments: /n 44Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files 23-FEB-2009 Watermark University PAGE 2 MG Data Load Report AGPMATC Report Mode * * Report Control Information * * REPORT NAME: AGPMATC CURRENT RELEASE: 8.2 PARAMETER SEQUENCE NUMBER: FILE CODE: CNMATCTEST NAME TYPE FOR ORG: ORGA NAME TYPE FOR ALIAS: NICK NAME TYPE FOR FUND: FUND CONTACT CODE: MG UPDATE ELIGIBLE PERSONNEL/EMPLOYEE STATUS INFORMATION: Y UPDATE ATHLETICES ELIGIBILITY PERSONNEL/EMPLOYEE STATUS INFORMATION: Y UPDATE EMPLOYEE AFFILIATION REQUIREMENTS ELIGIBILITY INFORMATION: Y UPDATE NON ELIGIBILITY INFORMATION: Y ADDRESS TYPE: BU EMAIL TYPE: WORK URL TYPE: URL REPORT[R]/UPDATE(U): R SOURCE FOR INFORMATION - CASE(C)/HEP[H]: H INPUT FILE: /export/home/cnorris/htest.dat LINE COUNT: 55 /n 45Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files agpmatc_XXXX.lis2This report lists all the companies for which the matching ratios are non-standard. For example, if a company™s policy is to gi ve $3 for each $1 that an employee gives, that company would be list ed on this report (a 1:1 or 2:1 ratio is standard). Note: This report is only produc ed when you load CASE data. 23-FEB-2009 12:31:43PM Development Page 1 Non-Standard Ratio Report AGPMATC ID Company Name 00000240 American National Can Co. Ratio: 2:1 up to $100 annual total matched per employee (cumulative), then 1:1. 00000841 Ameritech Corp. Ratio: 2:1 up to $500 annual total matched per employee (cumulative), then 1:1. Accreditation: State registration accepted for K-12 schools also. Maximum: $5,500b for education; $5,500 for culture/arts. Distribution: Three times a year: April, August, or December. 00000855 A. E. Staley Manufacturing Co. Ratio: 2:1 up to $100 annual total matched per employee (cumulative), then 1:1. Associations: National associations or funds soliciting support for education eligible only if connected with an eligible institution or fund. Maximum: $2,500b for noneducational. Ratio: 1:1 for noneducational. End of Listing /n 46Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files apgmatc_XXXX.lis3This report lists all the companie s for which the secondary contact is not located in the United States. Note: This report is only produc ed when you load CASE data. 23-FEB-2009 12:31:43PM Development Pa ge 1 Non-USA Country Report AGPMATC ID Company Name Country 00000973 Acuson SWEDEN 00001006 Addison Wesley Longman ENGLAND End of Listing /n 47Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files apgmatc_XXXX.lis4This report lists all the records that could not be loaded into the Banner tables automatically because they did not have a PID M. These records must be entered into Banner manually, and this report cont ains the information you need to enter them. Be sure to check for the existing record using different spe llings and acronyms for the name. 23-FEB-2009 Development Page 1 Organizations without a Banner ID Report AGPMATC Source ID Banner ID Company Name Contact Name and Title 5940000 Ms. Jackie Meara Supervisor Fundname One Kroc Drive McDonald™s Employee Matching Gifts Oak Brook, IL 60523 Official Name (630) 623-7048 McDonald™s Corporation Alias Distribution Procedure Q A Min. Match Month Max. Match Amount Ratio Max Tot. Emp. Ann Employee Status Other Non-Profit $ 10 $ 10000 100% $ 10000 A R S Fiscal Year Eligible Ed. Inst Athletics Employee Affiliation Acknowledgements 01/01 - 12/31 F G C T N Y- Receipt required. Email Address: Homepage URL: Comments: ID Number and Name of Constituents with this employer 510000001 Matthew Andrew Allen 311115555 Sarah R Norris @00002674 Amanda Norris End of Listing /n 48Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files Organizations without a Banner ID Report AGPMATC * * Report Control Information * * REPORT NAME: AGPMATC CURRENT RELEASE: 5.3 PARAMETER SEQUENCE NUMBER: FILE CODE: HEP2001 NAME TYPE FOR ORG: ORGA NAME TYPE FOR ALIAS: NICK NAME TYPE FOR FUND: FUND CONTACT CODE: MG UPDATE ELIGIBLE PERSONNEL/EMPLOYEE STATUS INFORMATION: Y UPDATE ATHLETICES ELIGIBILITY PERSONNEL/EMPLOYEE STATUS INFORMATION: Y UPDATE EMPLOYEE AFFILIATION REQUIREMENTS ELIGIBILITY INFORMATION: Y UPDATE NON ELIGIBILITY INFORMATION: Y ADDRESS TYPE: MA EMAIL TYPE: BUSI URL TYPE: HPAG REPORT[R]/UPDATE(U): U SOURCE FOR INFORMATION - CASE(C)/HEP[H]: H INPUT FILE: /u/designer/cnorris/hep2.dat LINE COUNT: 55 /n 49Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files apgmatc_XXXX.lis5For all address types, this report lists all new addresses and changed addresses that had a problem with information (for examp le, required information is missing). These records cannot be loaded into Banner. After research, you might be able to enter the data into B anner manually. 23-FEB-2009 Development Page 1 Organizations with Address Updates Report AGPMATC Source ID Banner ID Company Name Previous Address Incoming Address 220000 220000 Aid Association for Lutherans 4321 North Ballard Road Appleton, WI 54919 225000 225000 Air Products and Chemicals, Inc. 17201 Hamilton Boulevard 7201 Hamilton Boulevard Allentown, PA 18195 PA 18195 Incoming Address Update bypassed due to missing data. 22110000 000000369 20th Century Industries 111 Emp Employee Relations Department 6301 Owensmouth Avenue 6301 Owensmouth Avenue Woodland Hills, CA 91367 Woodland Hills, CA 91367 End of Listing /n 50Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files 23-FEB-2009 Development Page 2 Organizations with Address Updates Report AGPMATC * * Report Control Information * * REPORT NAME: AGPMATC CURRENT RELEASE: 5.3 PARAMETER SEQUENCE NUMBER: FILE CODE: HEP2001 NAME TYPE FOR ORG: ORGA NAME TYPE FOR ALIAS: NICK NAME TYPE FOR FUND: FUND CONTACT CODE: MG UPDATE ELIGIBLE PERSONNEL/EMPLOYEE STATUS INFORMATION: Y UPDATE ATHLETICES ELIGIBILITY PERSONNEL/EMPLOYEE STATUS INFORMATION: Y UPDATE EMPLOYEE AFFILIATION REQUIREMENTS ELIGIBILITY INFORMATION: Y UPDATE NON ELIGIBILITY INFORMATION: Y ADDRESS TYPE: MG EMAIL TYPE: BUSI URL TYPE: HPAG REPORT[R]/UPDATE(U): U SOURCE FOR INFORMATION - CASE(C)/HEP[H]: H INPUT FILE: hep2e.dat LINE COUNT: 55 /n 51Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files Step 7 - Run the MG Data Load Repor t (AGPMATC) in update mode Run AGPMATC as described in step 5, except enter U (update) as parameter 10 rather than R (report). In update mode, AGPMATC loads data into permanent Banner tables. The following data is always updated on AOAORGN when you run the process in update mode: ŁMinimum gift amount ŁMaximum gift amount ŁRatioŁMaximum total annual match for an employee ŁFiscal yearŁLast load source ŁLast load ID ŁLast load date The following data can also be updated, depending on the parameters you select on GJAPCTL:ŁOrganization name related information (APAIDEN) (updates addresses only) ŁMatching gift program administrator info rmation (AOAORGN se condary contacts) ŁAthletic matching gift purpose eligibility information (AOA MTCH Matching Gift Purpose) ŁMatching gift eligible employee status information (AOAORGN Employee Requirement) ŁMatching gift eligible educational instit ution information (A OAMTCH Educational Institution)ŁEmployee attendance information (AOAMTCH Alumni Status) Step 8 - (Optional) Load and link subsidiary organizationsRun the Matching Gift Subsid iary Data Load Report (AGP MATS) to load subsidiary company name information into the SPRIDEN table and link subsidiary organizations to their parent companies. The process creates cr oss-references that can be viewed on the Cross Reference Form (APAXREF). Similar to AGPMATC, this report uses the name type to determine which record should be updated if there are multiple names or acronyms for the same PIDM. AGPMATS has the following prerequisites: ŁThe parent organization must exist in Banner. ŁIf you want to set up a cross reference to i ndicate a parent/subsidiary relationship, the cross reference codes must exist on the Cross Reference Validation Form (ATVXREF). ŁThe name type code you use for the name of the parent company or subsidiary must exist in the Name Type Validation Form (GTVNTYP). /n 52Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files Run this process in report mode to verify the changes. AGPMATS is run from the Process Submission Controls Form (GJAPCTL ) with the following parameters: Review the report that is produced to verify the changes. Once the data is verified, run AGPMATS in update mode to create the actual cross-reference links. For more information about AGPMATS, refer to the Banner Advancement User Guide .Parameter Description 01Name Type Name type of the parent company. Required. 02Name Type for Subsidiary Name type of the subsidiary. Optional. 03Xref Code for ParentCross-reference code that represents the relationship between the parent and the subsidiary. If you enter this code, a cross-reference record is added for both IDs. The records can be displayed and reviewed on APAXREF. Optional. 04Report Mode Code that determines whether the database is updated when the process is run. R - Print report; do not update database (default). U - Print report; update database. 05Source - HEP/CASESour ce of the data file: H - HEP (default) C - CASE06HEP/CASE Input File NamePath and file name of the input file. Required. /n 53Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files 18-APR-2000 02:59:57PM Development PAGE 1 MG Subsidiary Data Load Report AGPMATS Report Mode Parent Company Information Source ID Banner ID Company Name 6320000 6320000 AEGON USA, Inc. Subsidiary Company Information Source ID Banner ID Company Name 6320010 Subsidiary Name Advanced Financial Services Division NO UPDATE Cross Reference: Parent Company Information Source ID Banner ID Company Name NO UPDATE Subsidiary Company Information Source ID Banner ID Company Name 6320010 Subsidiary Name Advanced Financial Services Division NO UPDATE Cross Reference: /n 54Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files 18-APR-2000 02:59:57PM Development PAGE 530 MG Subsidiary Data Load Report AGPMATS Report Mode * * Report Control Information * * REPORT NAME: AGPMATS CURRENT RELEASE: 4.3 PARAMETER SEQUENCE NUMBER: NAME TYPE: HEP NAME TYPE FOR SUBSIDIARY: HEP XREF CODE: COR REPORT[R]/UPDATE(U): R LINE COUNT: 55 SOURCE FOR INFORMATION - CASE(C)/HEP[H]: H INPUT FILE: /u/designer/cnorris/hepsub.dat /n 55Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files Step 9 - (Optional) Review employee records for potential matching gifts Run the Expected Matching Gift Allocation s Report (AXPMATG) or the Matching Gift Allocations Report (AGPMATG) to identify other potential matching gifts to which your institution might be entitled. These processes create the waiting matching gift payment records that are displayed on the Employer Matching Gift Payment Form (AGAMATG). Note: AXPMATG and AGPMATG are simila r. AXPMATG, however, has more functionality because it uses the same processing logic that the online gift and pledge entry forms use to evaluate matching gifts. AXPMATG also updates the re asons why a pledge or gi ft is not eligible to be matched. You should use AXPMATG instead of AGPMATG. If the ID whose gift was matched is th e spouse of an eligible employee, ( SPS ) appears after the ID™s name. Only gifts that are in a finalized cashiering session and have not already been processed by this report are selected. AXPMATG and AGPMATG are run from the Process Submission Controls Form (GJAPCTL). AXPMATG is run with the following parameters: AGPMATG is run with the following parameter: For more information about AXPMAT G and AGPMATG, refer to the Banner Advancement User Guide.Parameter Description 01Pledge, Gift, or BothCode that indicates what records are processed: P - Pledges only G - Gifts only B - Both pledges and gifts 02Beginning DateBeginning date to process matching gifts. 03Ending DateEnding date to process matching gifts. Parameter Description 01Report or Report/ UpdateCode that determines whether the database is updated when the process is run. R - Print report; do not update database (default). U - Print report; update database. /n 56Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files This is a sample of th e AGPMATG report output: 09-DEC-1998 15:11:12 Watermark University PAGE 1 Matching Gift Allocations AGPMATG Report Only MG ORG ID MG ORG NAME DUPLICATE - Y MATCH % MINIMUM PERSON MAX ORG MAX 510000035 Maryland Broadcasting Corp. 150.00 RATIO % BEGIN END 50.00 1.00 500.00 25.00 500.01 10,000.00 25.00 10,000.01 9,999,999.99 MATCHING ID MATCHING NAME DUPLICATE - Y MATCH % MINIMUM PERSON MAX ORG MAX 510000035 Maryland Broadcasting Corp. 150.00 RATIO % BEGIN END 50.00 1.00 500.00 25.00 500.01 10,000.00 25.00 10,000.01 9,999,999.99 CONSTITUENT ID CONSTITUENT NAME GIFT DATE GIFT NO QUALIFY AMT MATCH AMOUNT 990000019 (SPS) Holly T. Alison 09-DEC-1998 0004042 25.00 12.50 TOTALS: $25.00 $12.50 995000005 George Richard Black 24-NOV-1998 0003907 25.00 12.50 TOTALS: $25.00 $12.50 990000003 Kevin D. Rolfe 09-DEC-1998 0004040 50.00 25.00 TOTALS: $50.00 $25.00 990000004 Margaret C. Rolfe 09-DEC-1998 0004041 50.00 25.00 TOTALS: $50.00 $25.00 MG ORG TOTALS: $150.00 $75.00 /n 57Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files 09-DEC-1998 15:11:12 Watermark University PAGE 3 Matching Gift Allocations AGPMATG Report Only * * REPORT CONTROL INFORMATION * * RPTNAME: AGPMATG PARAMETER SEQUENCE NUMBER: REPORT OR REPORT/UPDATE: R LINE COUNT: 55 RECORD COUNT: 5 /n 58Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files This is a sample of the AXPMATG report output. 26-JUL-1996 14:57:02 Banner Development Environment PAGE 3 Expected MG Allocations AXPMATG CONSTITUENT GIFT GIFT ID CONSTITUENT NAME DATE NUMBER GIFT AMT QUALIFY AMT MATCH AMT MATCHING GIFT COMPANY 990000001 Allen, Matthew A. 09-MAY-1996 0000410 $100.00 $100.00 $100.00 510000035 Maryland Broadcasting Corporation, Inc 09-MAY-1996 0000412 $100.00 $100.00 $100.00 510000035 Maryland Broadcasting Corporation, Inc 10-JUL-1996 0000494 $50.00 $50.00 $50.00 510000035 Maryland Broadcasting Corporation, Inc TOTAL: $250.00 $250.00 $250.00 990000002 (S) Allen, Roberta Evans 09-MAY-1996 0000406 $1,500.00 $1,500.00 $1,500.00 510000035 Maryland Broadcasting Corporation, Inc 990000139 Chaves, Tom Andrew 09-MAY-1996 0000421 $100.00 $100.00 $250.00 @00000140 Chaves, Inc 10-JUL-1996 0000472 $100.00 $100.00 $250.00 @00000140 Chaves, Inc 10-JUL-1996 0000487 $25.00 $25.00 $62.50 @00000140 Chaves, Inc 10-JUL-1996 0000492 $111.00 $111.00 $111.00 @00000140 Chaves, Inc 10-JUL-1996 0000493 $122.00 $122.00 $122.00 @00000140 Chaves, Inc 10-JUL-1996 0000500 $65.00 $65.00 $162.50 @00000140 Chaves, Inc 10-JUL-1996 0000503 $81.00 $81.00 $202.50 @00000140 Chaves, Inc 10-JUL-1996 0000507 $50.00 $50.00 $125.00 @00000140 Chaves, Inc 10-JUL-1996 0000508 $500.00 $500.00 $500.00 @00000140 Chaves, Inc GRAND TOTALS: $2,904.00 $2,904.00 $3,535.50 /n 59Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files 26-JUL-1996 14:57:02 Banner Development Environment PAGE 4 Expected MG Allocations AXPMATG * * REPORT CONTROL INFORMATION * * REPORT NAME: AXPMATG PARAMETER SEQUENCE NUMBER: PLEDGE, GIFT OR BOTH: B STARTING DATE: 01-MAY-1996 ENDING DATE: 19-JUL-1996 LINE COUNT: 55 RECORD COUNT: 21 /n 60Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files Load external ratings and directory informationThe External Ratings and Directory Load Process (APPCUPD) loads the following information from third-party products to Banner: ŁExternal ratings data ŁUpdated alumni information from a vendor th at produces alumni directories. You can use this process with the Directory Data Extract Process (APPDEXT). APPDEXT extracts information to share with the vendor, the results are returned to your institution, and APPCUPD loads the updates into th e Banner database. Before loading data, you must perform the setup steps described in fiSet up a data load or a data extractfl on page8 .Data that can be loaded APPCUPD can load the following da ta into Banner. The ATVTPFD field names are used to define the file layout on the Data Fi eld Position Rules Form (AGATPFD). ATVTPFD Field NameBanner Data FieldDescription ACTIVITYAPRACTY_ACTC_CODEActivity code ADDR_ACTIVITY_DATESPRADDR_ACTI VITY_DATEAdvancement indi vidual address activity date ADDR_CITY SPRADDR_CITY Advancement individual city (repeating) The selection is based on STVATYP = parameter value where the occurrence determines the sequence selection. For example, if the first parameter value = MA, the first occurrence of the address is loaded as MA. If t he second parameter value = BU, the second occurrence of the address is loaded as BU. ADDR_CODE SPRADDR_ATYP_CODEAdvancement individual address type code ADDR_COUNTRY SPRADDR_NATN_CODEAdv ancement individual country (repeating) The selection is based on STVATYP = parameter value where the occurrence determines the sequence selection. For example, if the first parameter value = MA, the first occurrence of the address is loaded as MA. If t he second parameter value = BU, the second occurrence of the address is loaded as BU. /n 61Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files ADDR_FAX_AREA SPRTELE_PHONE_AREAAdvancement individual fax area code ADDR_FAX_NUM SPRTELE_PHONE_ NUMBERAdvancement individual fax number ADDR_HOUSE_NUM BERSPRADDR_HOUSE_ NUMBERAdvancement individual house number, a unique number assigned to each building on a street or in an area and used as part of the postal address in some countries ADDR_PHONE_ALL SPRTELE_PHONE_ NUMBERAdvancement individual phone number with area code and extension (repeating) The selection is based on STVTELE = parameter value where occurrence determines the sequence selection. For example, if the first parameter value = MA, the first occurrence of phone is loaded as MA. If the second parameter value = BU, the second occurrence of phone is loaded as BU.The first six characters of ADDR_PHONE_ALL are processed as the area code; the next 12 characters are processed as the phone number; the next 10 characters are processed as the extension. For example, a typical incoming U.S. phone number would be formatted as 610 5551212 1234. To better control your data load, it is recommended that you use ADDR_AREA_CODE, ADDR_PHONE, and ADDR_PHONE_EXT instead of ADDR_PHONE_ALL. ADDR_PHONE_AREASPRTELE_PHONE_ NUMBERAdvancement individual phone area code (repeating) The selection is based on STVTELE = parameter value where the occurrence determines the sequence selection. For example, if the first parameter value = MA, the first occurrence of phone is loaded as MA. If the second parameter value = BU, the second occurrence of phone is loaded as BU.ADDR_PHONE_COUNTRY_ CODESPRTELE_CTRY_CODE_ PHONECode that designates the region and country of the telephone number of the advancement individual ATVTPFD Field NameBanner Data FieldDescription /n 62Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files ADDR_PHONE_EXTSPRTELE_PHONE_ NUMBERAdvancement individual phone number extension (repeating) The selection is based on STVTELE = parameter value where the occurrence determines the sequence selection. For example, if the first parameter value = MA, the first occurrence of phone is loaded as MA. If the second parameter value = BU, the second occurrence of phone is loaded as BU.ADDR_PHONE_NUMSPRTELE_PHONE_ NUMBERAdvancement individual phone number (repeating) The selection is based on STVTELE = parameter value where the occurrence determines the sequence selection. For example, if the first parameter value = MA, the first occurrence of phone is loaded as MA. If the second parameter value = BU, the second occurrence of phone is loaded as BU.ADDR_STATESPRADDR_STAT_CODEAdvancement individual state (repeating) The selection is based on STVATYP = parameter value where the occurrence determines the sequence selection. For example, if the first parameter value = MA, the first occurrence of the address is loaded as MA. If t he second parameter value = BU, the second occurrence of the address is loaded as BU. ADDR_STREET1SPRADDR_STREET LINE1Advancement individual street address 1 (repeating) The selection is based on STVATYP = parameter value where the occurrence determines the sequence selection. For example, if the first parameter value = MA, the first occurrence of the address is loaded as MA. If t he second parameter value = BU, the second occurrence of the address is loaded as BU. ATVTPFD Field NameBanner Data FieldDescription /n 63Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files ADDR_STREET2SPRADDR_STREET_LINE2Advancement individual street address 2 (repeating) The selection is based on STVATYP = parameter value where the occurrence determines the sequence selection. For example, if the first parameter value = MA, the first occurrence of the address is loaded as MA. If t he second parameter value = BU, the second occurrence of the address is loaded as BU. ADDR_STREET3SPRADDR_STREET_LINE3Advancement individual street address 3 (repeating) The selection is based on STVATYP = parameter value where the occurrence determines the sequence selection. For example, if the first parameter value = MA, the first occurrence of the address is loaded as MA. If t he second parameter value = BU, the second occurrence of the address is loaded as BU. ADDR_STREET4SPRADDR_STREET_LINE4Advancement individual street address 4 (repeating) The selection is based on STVATYP = parameter value where the occurrence determines the sequence selection. For example, if the first parameter value = MA, the first occurrence of the address is loaded as MA. If t he second parameter value = BU, the second occurrence of the address is loaded as BU. ADDR_ZIPSPRADDR_ZIPAdvancement individual ZIP (repeating) The selection is based on STVATYP = parameter value where the occurrence determines the sequence selection. For example, if the first parameter value = MA, the first occurrence of the address is loaded as MA. If t he second parameter value = BU, the second occurrence of the address is loaded as BU. ATVTPFD Field NameBanner Data FieldDescription /n 64Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files ADDR_ZIP4 SPRADDR_ZIPAdvancement individual ZIP - last four digits (repeating) The selection is based on STVATYP = parameter value where the occurrence determines the sequence selection. For example, if the first parameter value = MA, the first occurrence of the address is loaded as MA. If t he second parameter value = BU, the second occurrence of the address is loaded as BU. ADDR_ZIPC SPRADDR_ZIPAdvancement individual ZIP complete (repeating) The selection is based on STVATYP = parameter value where the occurrence determines the sequence selection. For example, if the first parameter value = MA, the first occurrence of the address is loaded as MA. If t he second parameter value = BU, the second occurrence of the address is loaded as BU. BAN_PIDMSPRIDEN_PIDMBanner PIDM (unique identifier) CHILD_BIRTHDATE APRCRVW_BIRTH_DATEChild™s date of birth CHILD_DECEASED_DATEAPRCRVW_DECEASED DATE Child™s deceased date CHILD_DECEASED_INDAPRCRVW_DECEASED_ INDChild™s deceased indicator CHILD_GENDER APRCRVW_SEX Child™s gender CHILD_NAME_FIRSTAPRCRVW_FIR ST_NAMEChild™s first name CHILD_NAME_LASTAPRCRVW_LAST NAMEChild™s last name CHILD_NAME_MIDDLEAPRCRVW_MI Child™s middle name CHILD_PIDM APRCRVW_CHLD_PIDMChild™s Banner PIDM CHILD_SURNAME PREFIXAPRCHLD_SURNAME_ PREFIXChild™s last name prefix DEGREEAPRDRVW_DEGC_CODENew degree DEGREE_NAMEAPRDRVW_DEG_NAMENew degree name (when no code is returned) DEGREE_YEARAPRDRVW_ACY R_CODEDegree year ATVTPFD Field NameBanner Data FieldDescription /n 65Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files EMAILGOREMAL_EMAIL_ ADDRESSAdvancement individual e-mail (repeating) The selection is based on GTVEMAL = parameter value where the occurrence determines the sequence selection. For example, if the first parameter value = HOME, the first occurrence of e-mail is loaded as HOME. If the second parameter value = HPAG the second occurrence of e- mail is loaded as HPAG. EMAIL_CODE GOREMAL_EMAL_CODEE-mail type code EMPR_ADDR_CODEAPRERVW_ATYP_CODEEmployer address type code (STVATYP = Employer Address Type parameter value) EMPR_AREA_CODEAPRERVW_PHONE_AREA Employer phone area code EMPR_CITYAPRERVW_CITYEmployer address city EMPR_COUNTRYAPRERVW_NATN_CODEEmployer country EMPR_COUNTYAPRERVW_CNT Y_CODEEmployer county EMPR_EMAILAPRERVW_EMAIL_ ADDRESSEmployer e-mail EMPR_EMAIL_CODEAPRERVW_EMAIL_C ODEEmployer e-mail type code EMPR_FAXAPRERVW_FAX_NUMBEREmployer fax number EMPR_FAX_ALLAPRERVW_FAX_AREA and APRERVW_FAX_NUMBER Employer fax with area code EMPR_FAX_AREAAPRERVW_FAX_AREAEmployer fax area code EMPR_FROM_DATEAPRERVW_ADDR_FROM_ DATE Employer address start date EMPR_HOUSE_NUMBERSPRADDR_HOUSE_ NUMBEREmployer house number, a unique number assigned to each building on a street or in an area and used as part of the postal address in some countries EMPR_MATCH_GIFTAPRERVW_MG_INDEmplo yer matching gift indicator (Y/N) EMPR_NAMEAPRERVW_EMPR_NAMEEmployer name EMPR_PHONEAPRERVW_PHONE_ NUMBEREmployer phone ATVTPFD Field NameBanner Data FieldDescription /n 66Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files EMPR_PHONE_ALLAPRERVW_PHONE_AREA, APRERVW_PHONE_ NUMBER, and APRERVW_PHONE_EXT Employer phone with area code and extension The first six characters of are processed as the area code; the next 12 characters are processed as the phone number; the next 10 characters are processed as the extension. For example, a typical incoming U.S. phone number would be formatted as 610 5551212 1234. To better control your data load, it is recommended that you use EMPR_AREA_CODE, EMPR_PHONE, and EMPR_PHONE_EXT instead of EMPR_PHONE_ALL. EMPR_PHONE_COUNTRY_ CODESPRTELE_CTRY_CODE_ PHONECode that designates the region and country of the employer telephone number EMPR_PHONE_EXTAPRERVW_PHONE_EXTEmployer phone extension EMPR_PIDMAPRERVW_EMPR_IDEmpl oyer PIDM (from Banner) EMPR_STATE APRERVW_STAT_CODEEmployer address state EMPR_STREET1APRERVW_STREET_LINE1 Employer address street 1 EMPR_STREET2APRERVW_STREET_LINE2 Employer address street 2 EMPR_STREET3APRERVW_STREET_LINE3 Employer address street 3 EMPR_STREET4APRERVW_STREET_LINE4 Employer address street 4 EMPR_TO_DATE APRERVW_ADDR_TO_ DATE Employer address end date EMPR_ZIPAPRERVW_ZIPC Employer address ZIP - first five digits EMPR_ZIP4APRERVW_ZIPC Employer address ZIP - last four digits EMPR_ZIPCAPRERVW_ZIPC Employer address complete ZIPEXCL_CODEAPREXCL_EXCL_CODE Exclusions (including do not mail/phone, do not include, do not solicit) EXCL_END_DATE APREXCL_END_DATEDate when the exclusion ends EXCL_REASONAPREXCL_REASONReason that the exclusion applies to the ID EXCL_START_DATEAPREXCL_DATE Date when the exclusion starts EXT_ACTIVITY_DATEAMREXRT_AC TIVITY_DATEActivity date EXT_RATE_SOURCEAMREXRT_EXRS_CO DEExternal rating source EXTERNAL_LEVEL AMREXRT_EXT_LEVELLevel EXTERNAL_SCORE AMREXRT_EXT_SCOREScore ATVTPFD Field NameBanner Data FieldDescription /n 67Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files EXTERNAL_VALUE AMREXRT_EXT_VALUEValue INCOMEAPBCONS_INCM_CODEAdvanceme nt individual income detail INST_CODEAPRDRVW_SBGI_CODE Banner institution attended code INSTITUTIONAPRDRVW_INST_NA MENew degree institution JOB_CATEGORY APRERVW_JOBC_CODEJob category JOB_CATEGORY2 APRERVW_JOBC_CODE2Job category 2 JOB_CATEGORY3 APRERVW_JOBC_CODE3Job category 3 JOB_CATEGORY4 APRERVW_JOBC_CODE4Job category 4 JOB_EMP_STATUS APRERVW_EMPS_CODEJob status JOB_FROM_DATE APRERVW_FROM_DA TEEmployee™s job start date JOB_PRIMARY_IND APRERVW_PRIMARY_IND Primary employer indicator (Y/N) JOB_SICC_CODE APRERVW_SICC_CODEOccu pation/career code (SIC code) JOB_TITLEAPRERVW_EMPL_ POSITIONEmployee™s job title JOB_TO_DATE APRERVW_TO_DATEEmployee™s job end date JOB_WKLY_HOURSAPRERVW_WKLY_ HOURSWeekly hours worked MAIDEN_NAME_LASTAPBCONS_MAIDEN_LAST_ NAMEMaiden last name MAJORAPRDRVW_MAJR_CO DEBanner major code MAJOR2APRDRVW_MAJR_CODE 2Banner major code 2 MAJOR3APRDRVW_MAJR_CODE 3Banner major code 3 MAJOR_NAME APRDRVW_MAJOR_NAMENew major name (when no code is returned) MAJOR_NAME2 APRDRVW_MAJOR_NAME2New major name 2 (when no code is returned) MAJOR_NAME3 APRDRVW_MAJOR_NAME3New major name 3 (when no code is returned) MARITAL_STATUS SPBPERS_MRTL_CODEMarital status ATVTPFD Field NameBanner Data FieldDescription /n 68Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files NAME_FIRST SPRIDEN_FIRST_NAMEFirst name (repeating) The selection is based on GTVNTYP = parameter value where the occurrence determines the sequence selection. For example, if the first parameter value = MAID, the first occurrence of first name is loaded as MAID. If the second parameter value = CASL, the se cond occurrence of first name is loaded as CASL. NAME_LAST SPRIDEN_LAST_NAM ELast name (repeating) The selection is based on GTVNTYP = parameter value where the occurrence determines the sequence selection. For example, if the first parameter value = MAID, the first occurrence of last name is loaded as MAID. If the second parameter value = CASL, the se cond occurrence of last name is loaded as CASL. NAME_MIDDLE SPRIDEN_MIMiddle name (repeating) The selection is based on GTVNTYP = parameter value where the occurrence determines the sequence selection. For example, if the first parameter value = MAID, the first occurrence of middle name is loaded as MAID. If the second parameter value = CASL, the second occurrence of middle name is loaded as CASL.NAME_PREFIXSPBPERS_NAME_PREFIXName prefix NAME_SUFFIXSPBPERS_NAME_SUFFIXName suffix NAME_SURNAME_PREFIXSPRIDEN_SURNAME_ PREFIXLast name prefix NICKNAMEAPBCONS_NICKNAMENicknam e for advancement individual OCCUPATION_TITLEAPBCONS_DOTT_ CODE Occupation title PHONE_COUNTRY_CODESPRTELE_CTRY_CODE_ PHONECode that designates the region and country of the telephone number PREF_ADDRESS_CODEAPBCONS_ATYP_CODE_ PREFPreferred address code PREFERRED_CLASSAPBCONS_PREF CLASPreferred class RESEARCH_COMMENTSAMRPUSR_VALU EResearch da ta comments RESEARCH_SOURCEAMRPSRC_SORC_CODESource ATVTPFD Field NameBanner Data FieldDescription /n 69Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files RESEARCH_USER AMRPUSR_USRC_CO DEResearch data user RESEARCHER AMRPRSC_IDEN_CODE RSCH ResearcherSCHOOL_CODE APRDRVW_COL L_CODESchool/college SOURCE_ACT_DATEAPRCRVW_ACTIVITY_ DATE, APRDRVW_ACTIVITY_ DATE, APRSRVW_ACTIVITY_ DATE, and APRERVW_ACTIVITY_ DATE Third-party source activity date SP_AREA_CODEAPRSRVW_PHONE_AREA Spouse™s phone area code SP_BIRTHDATE APRSRVW_BIRTH_DATESpouse™s birth date SP_CITYAPRSRVW_CITY Spouse™s address city SP_COUNTRY APRSRVW_NATN_CODESpouse™s country SP_COUNTYAPRSRVW_CNTY_ CODESpouse™s county SP_DECEASED_DATEAPRSRVW_DEAD_DATESpouse™s deceased date SP_DECEASED_INDAPRSRVW_DEAD_IND Spouse™s deceased indicator SP_EMAILAPRSRVW_EMAIL_ ADDRESSSpouse™s e-mail SP_FAX APRSRVW_FAX_NUMBERSpouse™s fax number SP_FAX_AREA APRSRVW_FAX_ARE ASpouse™s fax area code SP_FROM_DATE APRSRVW_ADDR_FROM_~ DATE Spouse™s address start date SP_HOUSE_NUMBERSPRADDR_HOUSE_ NUMBERSpouse™s house number, a unique number assigned to each building on a street or in an area and used as part of the postal address in some countries SP_MAIDEN_NAME_LASTAPRSRVW_MAIDEN_ NAMESpouse™s maiden last name SP_MAR_END_DATEAPRSRVW_MRTL_END_ DATE Marriage end date SP_MAR_START_DATEAPRSRVW_MRTL_START_ DATE Marriage start date SP_MARITAL_CODEAPRSRVW_M RTL_CODEMarital code SP_MARITAL_IND APRSRVW_MARS_IN DCurrent spouse indicator SP_NAME_FIRSTAPRSRVW_FIRST NAMESpouse™s first name ATVTPFD Field NameBanner Data FieldDescription /n 70Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files SP_NAME_LASTAPRSRVW_LAST_NAMESpouse™s last name SP_NAME_MIDDLE APRSRVW_MI Spouse™s middle name SP_NAME_PREFIXAPRSRVW_NAME_PREFIXSpouse™s prefix SP_NAME_SUFFIXAPRSRVW_NAME_SUFFIXSpouse™s suffix SP_PHONEAPRSRVW_PHONE NUMBERSpouse™s phone SP_PHONE_ALLAPRSRVW_PHONE_AREA, APRSRVW_PHONE_ NUMBER, and APRSRVW_PHONE_EXT Spouse™s phone with area code and extension The first six characters are processed as the area code; the next 12 characters are processed as the phone number; the next 10 characters are processed as the extension. For example, a typical incoming U.S. phone number would be formatted as 610 5551212 1234. To better control your data load, it is recommended that you use SP_AREA_CODE, SP_PHONE, and SP_PHONE_EXT instead of SP_PHONE_ALL.SP_PHONE_COUNTRY_ CODESPRTELE_CTRY_CODE_ PHONECode that designates the region and country of the spouse™s telephone number SP_PHONE_EXTAPRSRVW_PHONE_EXT Spouse™s phone extension SP_STATE APRSRVW_STAT_CODESpouse™s address state SP_STREET1APRSRVW_STREET_LINE1 Spouse™s address street 1 SP_STREET2APRSRVW_STREET_LINE2 Spouse™s address street 2 SP_STREET3APRSRVW_STREET_LINE3 Spouse™s address street 3 SP_STREET4APRSRVW_STREET_LINE4 Spouse™s address street 4 SP_SURNAME_PREFIX APRCSPS_SURNAME_ PREFIXSpouse™s last name prefix SP_TO_DATE APRSRVW_ADDR_TO_ DATE Spouse™s address end date SP_ZIPAPRSRVW_ZIP Spouse™s address ZIP - first five digits SP_ZIP4APRSRVW_ZIP Spouse™s addre ss ZIP - last four digits SP_ZIPCAPRSRVW_ZIP Spouse™s address ZIP - complete SPS_PIDMAPRSRVW_SPS_PIDMSpouse™s Banner PIDM SS_NUMBERSPBPERS_SSN Social security numberATVTPFD Field NameBanner Data FieldDescription /n 71Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files Steps Use the following steps to load external ratings and directory information to Banner: ŁfiStep 1 - Verify the file definitions and input datafl on page71 ŁfiStep 2 - Run the External Ra tings and Directory Load Pr ocess (APPCUPD) in report modefl on page75 ŁfiStep 3 - Review the output reportsfl on page79 ŁfiStep 4 - Run the External Ratings and Directory Load Process (APPCUPD) in update modefl on page80 ŁfiStep 5 - Display all records in the temporary tablesfl on page81 ŁfiStep 6 - Review and update records in the temporary tablesfl on page81 ŁfiStep 7 - Load the verified records into the Banner permanent tablesfl on page82 The following sections provide deta iled instructions for each step. Step 1 - Verify the file definitions and input data The Data Definition File List Process (APPDFLS) show s the data on the incoming data file with the corresponding information from the Da ta Field Position Rules Form (AGATPFD). The format of the report pr oduced by APPDFLS is similar to the format of AGATPFD but includes the actual data value for each field. Use APPD FLS to see if your file definition is set up correctly on AGATPFD, and to check the incoming data on the file. The input file can be fixed length or character delimited. APPDFLS is run from the Process Submission Controls Form (GJAPCTL) with the following parameters: Parameter Description 01File Code File code for the appropriate data source. Select List or the Values pull-down arrow to see valid values from the Data File Validation Form (ATVTAPE). Required. 02Path of Data File - Part 1Directory where the data load file is located (up to 30 characters). If the data file path is longer than 30 characters, parameters 08 and 09 are available to provide additional data file path details. Required. 03Data File NameExact name of t he file, including the extension. Required.04Data Source IdentifierCode that represents the data source. Select List or the Values pull-down arrow to see valid values from the Data Source Identi fier Validation Form (ATVDSRC). Required. /n 72Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files Output from the process shows each field name and the data in that field. If the file is fixed length, it also shows the start position, end po sition, and occurrence. If the file is character delimited, it shows the field number and th e occurrence. For more information about occurrences, refer to fiUsing occurrencesfl on page13 .If the data does not look correct (for example, some characters that should appear in the first field actually appear in the second), t hen go back to AGATPFD and change the file definition for the incoming data file. If everything is correct, you can proceed. For more in formation about APPDFLS, refer to the Banner Advancement User Guide .05Start Record NumberNumber of the firs t record you want to process in the data file. This allows you to check a large data file in sections, rather than look at the whole file at one time. Optional. 06End Record NumberNumber of the last record you want to process in the data file. Use this with the Start Record Number to look at part of a large incoming file. Optional. 07Header Record ExistsCode that indicate s if the input file has a header record that Banner should not process as data. Y - Input file has a header record that should not be processed as data. N - First record on the file is actual data. This information is found on the incoming data file documentation from the vendor. Optional. 08Path of Data File - Part 2Additional details (up to 30 characters) for the directory where the data load file is located. Used with the Path of Data File - Part 1 parameter when the data file path is longer than 30 characters. This entry is concatenated to the end of the details entered in part 1. Optional. 09Path of Data File - Part 3Additional details (up to 30 characters) for the directory where the data file is located. Used with the Path of Data File - Part 1 and Part 2 parameters when the data file path is longer than 60 characters but less than 91 characters. This entry is concatenated to the end of the details entered in part 2. Optional. Parameter Description /n 73Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files 23-FEB-2009 Watermark University PAGE 1 Rel 8.2 File Definition Verification APPDFLS Testing Load Inc Column Name Value Position Occurs BAN_PIDM 45278 1 1 ADDR_HOUSE_NUMBER AAAA 2 1 ADDR_STREET1 1Street1 3 1 ADDR_STREET2 1Street2 4 1 ADDR_STREET3 1Street3 5 1 ADDR_STREET4 1Street4 6 1 ADDR_CITY Mason 7 1 ADDR_STATE OH 8 1 ADDR_ZIP 11111 9 1 ADDR_HOUSE_NUMBER BBBB 10 2 ADDR_STREET1 2Street1 11 2 ADDR_STREET2 2Street2 12 2 ADDR_STREET3 2Street3 13 2 ADDR_STREET4 2Street4 14 2 ADDR_CITY Mason 15 2 ADDR_STATE OH 16 2 ADDR_ZIP 22222 17 2 ADDR_HOUSE_NUMBER CCCC 18 3 ADDR_STREET1 3Street1 19 3 ADDR_STREET2 3Street2 20 3 ADDR_STREET3 3Street3 21 3 ADDR_STREET4 3Street4 22 3 ADDR_CITY Mason 23 3 ADDR_STATE OH 24 3 ADDR_ZIP 33333 25 3 EMAIL one@test 26 1 EMAIL two@test 27 2 EMAIL three@test 28 3 ADDR_PHONE_COUNTRY_CODE 9999 29 1 ADDR_PHONE_ALL 5131111111 30 1 ADDR_PHONE_COUNTRY_CODE 8888 31 2 ADDR_PHONE_ALL 5132222222 32 2 ADDR_PHONE_COUNTRY_CODE 7777 33 3 ADDR_PHONE_ALL 5133333333 34 3 EMPR_NAME Martin Car Detailing Incorporated 35 1 SP_NAME_FIRST Margaret 36 1 SP_SURNAME_PREFIX Von 37 1 SP_NAME_LAST Norristestoffieldlength 38 1 INSTITUTION University of Duluth 39 1 INSTITUTION Specialty Arts Academy 40 2 ADDR_FAX_COUNTRY_CODE 6666 41 1 ADDR_FAX_ALL 7777777777 42 1 CHILD_NAME_FIRST Thomas 43 1 CHILD_SURNAME_PREFIX Von 44 1 /n 74Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files 23-FEB-2009 Watermark University PAGE 3 Rel 8.2 File Definition Verification APPDFLS Testing Load Inc * * REPORT CONTROL INFORMATION * * USER:........................ CNORRIS Parameter Name Value Message _____ _____ ________ ILD_DECEASED_IND 213137 File Code NEWDATA Path of Data File - Part 1 /export/home/cnorris/ Data File Name newdata.dat Data Source Identifier TEST Start Record Number 1 End Record Number 9999999 Header Record Exists Y Path of Data File - Part 2 dataload/ Path of Data File - Part 3 Line Count 45 /n 75Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files Step 2 - Run the External Ratings and Directory Load Process (APPCUPD) in report modeBefore loading the ratings and directory information into Banner, you should test to make sure the data will load cleanly. Run the load process in report mode and review the various reports. APPCUPD is run from the Process Submis sion Controls Form (GJAPCTL) with the following parameters: Parameter Description 01File Code File code for the appropriate data source. Select List or the Values pull-down arrow to see valid values from the Data File Validation Form (ATVTAPE). Required. 02Path of Data File - Part 1Directory where the file to be loaded currently exists. This must be a location where Banner can access it. If the data file path is longer than 30 characters, parameters 23 and 24 are available to provide additional data file path details. Required. 03Data File NameExact name of the file sent by the vendor. Required. 04Data Source IdentifierCode that represents the data source. Select List or the Values pull-down arrow to see valid values from the Data Source Identi fier Validation Form (ATVDSRC). Required. 05Address Type Code that represents the address type to be loaded. This parameter accepts multiple values and should be defined for every occurrence of address data. Add a sequence number before each address type to indicate the order of the address records on the data file (for example, 1BU). If an address in the incoming data file includes an address type, the address is loaded with that address type. If the address does not have an address type, it is loaded with address type 1 defined in this parameter. If the address does not have an address type and no address type is defined in this parameter, the address is not loaded. Select List or the Values pull-down arrow to see valid values from the Address Type Code Validation Form (STVATYP). Optional. /n 76Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files 06Phone Type Code that represents the telephone type to be loaded. If you leave this parameter blank, no telephone details are loaded. This parameter accepts multiple values and should be defined for every occurrence of phone data. Add a sequence number before each phone type to indicate the order of the phone records on the data file (for example, 1BU). Select List or the Values pull-down arrow to see valid values from the Telephone Type Validation Form (STVTELE). Optional. 07Fax Number TypeCode that represents the fax type to be loaded. If you leave this parameter blank, no fax details are loaded. This parameter accepts multiple values and should be defined for every occurrence of fax number data. Add a sequence number before each fax number type to indicate the order of the fax number records on the data file (for example, 1BU). Select List or the Values pull-down arrow to see valid values from the Telephone Type Validation Form (STVTELE). Optional. 08E-mail Type Code that represents the e-mail address type to be loaded. If you leave this parameter blank, no e-mail address details are loaded. This parameter accepts multiple values and should be defined for every occurrence of e-mail data. Add a sequence number before each e-mail type to indicate the order of the e-mail records on the data file (for example, 1BU). Select List or the Values pull-down arrow to see valid values from the E-mail Address Type Validation Form (GTVEMAL). Optional.09Employer Address Type Code that represents the employer address type to be loaded. If you leave this blank, no employer address details are loaded. Select List or the Values pull-down arrow to see valid values from the Address Type Code Validation Form (STVATYP). Optional. Parameter Description /n 77Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files 10Employer Phone TypeCode that represents the employer phone type to be loaded. If you leave this blank, no employer telephone details are loaded. Select List or the Values pull-down arrow to see valid values from the Telephone Type Validation Form (STVTELE). Optional. 11Employer Fax TypeCode that represents the employer fax type to be loaded. If you leave this blank, no employer fax details are loaded. Select List or the Values pull-down arrow to see valid values from the Telephone Type Validation Form (STVTELE). Optional. 12Employer E-mail TypeCode that represents the employer e-mail address type to be loaded. If you leave this blank, no employer e-mail address details are loaded. Select List or the Values pull-down arrow to see valid values from the E-mail Address Type Validation Form (GTVEMAL). Optional.13Spouse Address TypeCode that represents the spouse address type to be loaded. If you leave this blank, no spouse address details are loaded. Select List or the Values pull-down arrow to see valid values from the Address Type Code Validation Form (STVATYP). Optional. 14Spouse Phone TypeCode that represents the spouse phone type to be loaded. If you leave this blank, no spouse telephone details are loaded. Select List or the Values pull-down arrow to see valid values from the Telephone Type Validation Form (STVTELE). Optional. 15Spouse Fax TypeCode that represents the spouse fax type to be loaded. If you leave this blank, no spouse fax details are loaded. Select List or the Values pull-down arrow to see valid values from the Telephone Type Validation Form (STVTELE). Optional. 16Spouse E-mail TypeCode that represents the spouse e-mail address type to be loaded. If you leave this blank, no spouse e-mail address details are loaded. Select List or the Values pull-down arrow to see valid values from the E-mail Address Type Validation Form (GTVEMAL). Optional.Parameter Description /n 78Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files 17Name Type Code that represents the name type to be loaded. If you leave this blank, no name details are loaded. This parameter accepts multiple values. Add a sequence number before each name type to indicate the order of the name records on the data file (for example, 1LEGL). Select List or the Values pull-down arrow to see valid values from the Name Type Validation Form (GTVNTYP). Optional. 18Preferred E-mailCode that represents the preferred e-mail address if you want to change an incoming e-mail address with a certain type code to be the preferred e-mail address. If you don™t want to change it, leave this blank. Select List or the Values pull-down arrow to see valid values from the E-mail Address Type Validation Form (GTVEMAL). Optional.19Report/Update Mode Mode in which you want to run the report. Enter R to produce reports without changing anything in Banner; enter U to update the Banner tables. Required. 20Line CountNumber of lines per page for the output report. Defaults to 55. Optional. 21Date FormatDate format that ov errides the system-defined date format for this execution of APPCUPD. Must be a valid Oracle date format. Used solely to evaluate incoming dates and load details to Banner. Optional. 22File Source DateDate us ed for file source details if the incoming data file does not have this detail. If the mapping on the Data Field Position Rules Form (AGATPFD) contains a reference to the SOURCE_ACT_DATE field, that value is used for the file source date. If AGAT PFD does not contain this reference, the value in the File Source Date parameter is used. If neither is defined , the current system date is used as the file source date. If a date format is entered in parameter 21, then this same date format must be used when entering a value for parameter 22. 23Path of Data File - Part 2Additional details (up to 30 characters) for the directory where the data file is located. Used with parameter 02 when the data file path is longer than 30 characters. This entry is concatenated to the end of the details entered in parameter 01. Optional. Parameter Description /n 79Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files For more in formation about APPCUPD, refer to the Banner Advancement User Guide .Step 3 - Review the output reports Review the details on the APPDFLS and APPCUPD output reports for any errors. ExampleIf the file definition create d on the Data Position Rules Form (AGATPFD) includes three different address sequences (by using occurrences), you must define three different address type parameter values (parameter 05) to specify how the data will be loaded. If the corresponding parameter details are missing, the process displays only those address records that w ill be loaded (those with appropriate ma pping details on AGATPFD where the parameter value is identified when the process is executed). Address records are not loaded if either the mapping is not defined or the corresponding parameters are missing. For more information about occurrences, refer to fiUsing occurrencesfl on page13 . Make any needed adjustments to the file defi nition on AGATPFD. If bad data details are identified, correct the issues in the data file as needed. You might need technical 24Path of Data File - Part 3Additional details (up to 30 characters) for the directory where the data file is located. Used with the parameters 02 and 23 when the data file path is longer than 60 characters but less than 91 characters. This entry is concatenated to the end of the details entered in parameter 23. Optional. 25Address Phone TypePhone type assigned to phone numbers that are associated with addresses in the data file. Select List or the Values pull-down arrow to see valid values from the Telephone Type Validation Form (STVTELE). Optional. 26Maintain Pref Email SettingSetting that determines how preferred e-mail addresses are maintained when the process is run. This parameter is used wit h Parameter 18. Required. Y - Insert an incoming e-mail address as the fipreferredfl e-mail address if it has the same address type as the original preferred e-mail address. Insert all other incoming e-mail addresses without the fipreferredfl indicator. N - Insert an incoming e-mail address as the fipreferredfl e-mail address only if it has the address type that is specified in Pa rameter 18. Insert all other incoming e-mail addresses without the fipreferredfl indicator, thereby retaining the fipreferredfl indicators on the original e-mail addresses. Parameter Description /n 80Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files assistance at your institution if the data file needs changes and you are not familiar with the change process. Step 4 - Run the External Ratings and Directory Load Process (APPCUPD) in update modeRun APPCUPD as described in step 2, except enter U (update) as parameter 19 rather than R (report). In update mode, APPCUPD loads some incoming data into permanent Banner tables and some data into temporary tables. Data loaded into permanent tables When executed in update mode, APPCUPD au tomatically loads some of the incoming data into the following Banner tables. ŁSPRIDENŁSPRTELE ŁSPRADDRŁGOREMAL ŁSPBPERS ŁAPBCONSŁAMRPRSCŁAMRPUSRŁAMREXRT (The remaining data is loa ded into temporary tables.) APPCUPD loads informatio n based on the Banner PIDM. This internal identifier must exist to load data for an advancement individuals or advancement organization. If the PIDM is missing, the record is listed on the output re port and the information is not loaded into any Banner tables. In general, data is loaded as follows: ŁIf information on the incoming data file is the same as existing data in the Banner tables, the new data is ignored. ŁIf the new data is different from the existing data, the way data is loaded depends on whether the data is repeating. For repeating da ta, the new data is inserted in Banner as a new record. For non-repeating data, the new da ta is noted on the report but existing Banner details are not updated. Note: Because fifromfl and fitofl dates are used with addresses, the preceding rule always applies to addresses. See fiAddress informationfl on page82 for more information. ŁIf the new data does not already exist, it is loaded into the Banner tables. /n 81Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files When name information is loaded into the Banner tables, the prefix and suffix information is added to the name automatically if that information is provided by the third-party vendor and the values are missing in the existing Banner data. Data details provided for the prefix are loaded to SPBPERS_NAME_PREFIX. Data deta ils provided for the suffix are loaded to SPBPERS_NAME_SUFFIX. Data loaded into temporary tables APPCUPD loads some incoming data into temporary tables. Th e remaining steps describe the process for displaying a list of records in the temporary tables, reviewing these records, and loading data to permanent Banner tables. Step 5 - Display all record s in the temporary tables Access the Data Load ID List Inquiry Form (APILRVW) to display a list of all records loaded into the temporary tables. The default sort order is alphabetical. The secondary sort order is by source. This form is used in the following steps to review and load data to permanent Banner tables. The Name, ID, Source, Source Date, Date Loaded , and load indicators are displayed for each record. The load indicators show the lo ad status of employer, degree, spouse, and child records:ŁP (pending review) - Data in the associated hold table has not been reviewed for loading. ŁL (ready to load) - Data in the associated hold table has been reviewed and the load check box is checked. ŁN (no data) - No data exists in the associated hold table for this ID. Step 6 - Review and update record s in the temporary tables The following forms can be used to review and update records in the temporary tables: 1.Access the desired review form. There are two ways to access a review form: ŁUse Direct Access to query an ID from the key block. ŁAccess a review form from APILRVW by highlighting a record and selecting Employer Review, Degree Review, Spouse Review, or Child Review from the Options menu. Menu options are available only if the corresponding load indicator is P (pending review). Type of InformationReview Form Children informationChild Review Form (APACRVW) Degree information Degree Review Form (APADRVW) Employer informationEmplo yer Review Form (APAERVW) Spouse informationSpouse Review Form (APASRVW) /n 82Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files 2.Make any necessary changes on the review form. 3.Select the OK to Load check box to indicate that data is ready to load to permanent Banner tables. 4.Save your changes. Note: If you return to APILRVW, the load i ndicator for that type of data is now L (ready to load). For more information about the review forms, refer to online help. Step 7 - Load the verified records into the Banner permanent tables After you review the data and select the OK to Load check box on the review form, a record can be loaded into the permanent Banner tables. There are two ways to load records: ŁIndividually from the review form ŁIn a group from APILRVW To load an individual record from the review form, select Load Record from the Options menu. To load multiple records from APILRVW: 1.Access APILRVW. The load indicator is L (ready to load) for those records ready to load. 2.(Optional) Review and change additional records. 3.Select Load Records from the Options menu to load all records where the load indicator is L.Once records are loaded to the permanent tables, Banner refreshes the list on APILRVW. If all data for a record was loaded, the record is no longer listed on APILRVW. If at least one temporary table reco rd still exists, the record remains on APILRVW. Note: An incoming data record might have details on more than one review form (for example, degree information and child information). When this occurs, each review form must be reviewed separately, the OK to Load check box must be selected on each review form, and each record must be loaded into the permanent tables before the record is removed from APILRVW. Address informationAddresses are handled differently than other types of data.The fifromfl and fitofl dates determine how APPCUPD treats th e new record. Be sure to review addresses carefully. The following examples show how addresses are loaded. /n 83Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files Note: When evaluating dates, APPCUPD uses the value in SOURCE_ACT_DATE as the current date when comparing it to SPRADDR_FROM_DATE. Incoming fitofl date before other addresses begin If the fitofl date on the new record is before any other address begins for the same address type selected, then APPCUPD inserts the new re cord as an inactive address. It does not make the existing address inactive. ExampleResult:Incoming fifromfl date after other addresses ends If the fifromfl date on the new record begins after any other address ends for the same address type selected, then APPCUPD inserts the new record. ExampleIncoming record: From date=01-MAY-2007 To date=12-DEC-2007 Existing record:From date=01-JAN-2008 To date=end of time New, inactive record: From date=01-MAY-2007 To date=31-DEC-2007 Unchanged existing record: From date=01-JAN-2008 To date=end of time Incoming record: From date=04-APR-2007 To date=12-DEC-2009 Existing record:From date=01-JAN-1980 To date=31-DEC-2006 /n 84Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files Result:Incoming fifromfl date between existing fifromfl and fitofl dates If the fifromfl date on the new record starts be tween the fifromfl and fitofl dates of an existing record for the same address type selected, then APPCUPD inserts the new record and updates the fitofl date for the existing record to be one less than the incoming fifromfl date. ExampleResult:Incoming fitofl date between existing fifromfl and fitofl datesIf the fitofl date on the new record is between the fifromfl and fitofl dates of an existing record for the same address type selected, then APPCUPD inserts the new record and changes the fifromfl date on the existing record to be one more than the fitofl date on the incoming record. New record: From date=04-APR-2007 To date=12-DEC-2009 Unchanged existing record: From date=01-JAN-1980 To date=31-DEC-2006 Incoming record: From date=01-MAY-1981 To date=01-MAY-1982 Existing record:From date=01-JAN-1980 To date=30-DEC-1981 New record: From date=01-MAY-1981 To date=01-MAY-1982 Updated existing record: From date=01-JAN-1980 To date=30-APR-1981 /n 85Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files ExampleResult:Incoming fifromfl and fitofl dates between existing fifromfl and fitofl datesIf the fifromfl and fitofl dates on the incoming record come between the fifromfl and fitofl dates on the existing record for the same address type selected, then APPCUPD does the following: ŁChanges the fitofl date on the existing record to be one day before the fifromfl date on the incoming record ŁInserts the incoming record without changing anything ŁInserts a copy of the existing address record where the fifromfl date is one day after the incoming record™s fitofl date ExampleIncoming record: From date=01-MAY-1979 To date=01-MAY-1982 Existing record:From date=01-JAN-1980 To date=31-DEC-1982 New record: From date=01-MAY-1979 To date=01-MAY-1982 Updated existing record: From date=02-MAY-1982 To date=31-DEC-1982 Incoming record: From date=01-MAY-1981 To date=01-MAY-1982 Existing record:From date=01-JAN-1980 To date=End of time /n 86Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files Result:Incoming fifromfl and fitofl dates come before and after existing fifromfl and fitofl datesIf the fifromfl and fitofl dates on the incoming record come before and after the fifromfl and fitofl dates on the existing record for the same address type selected, then APPCUPD makes the existing record inacti ve and inserts the incoming record into the Banner tables. ExampleResult:Updated existing record: From date=01-JAN-1980 To date=30-APR-1981 New record: From date=01-MAY-1981 To date=01-MAY-1982 New record: From date=02-MAY-1982 To date=End of time Incoming record: From date=01-MAY-1979 To date=01-MAY-1982 Existing record:From date=01-JAN-1980 To date=01-JUN-1981 New record: From date=01-MAY-1979 To date=01-MAY-1982 Inactive existing record: From date=01-JAN-1980 To date=01-JUN-1981 /n 87Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files Incoming fifromfl and fitofl dates cross over dates on two other recordsIf the fifromfl date on the incoming record comes between the fifromfl and fitofl dates of an existing record of the same address type, and the fitofl date comes between the fifromfl and fitofl dates of a different existing record with the same address type selected, then APPCUPD does the following: ŁChanges the fitofl date on the first existing record to be one day before the fifromfl date on the incoming record ŁInserts the incoming reco rd without changing it ŁChanges the fifromfl date on the second existing record to be one day after the incoming record™s fitofl date ExampleResult:Incoming record: From date=01-MAY-1980 To date=01-MAY-1982 Existing record 1:From date=01-JAN-1980 To date=01-JUN-1981 Existing record 2:From date=02-JUN-1981 To date=End of time Updated existing record 1: From date=01-JAN-1980 To date=30-APR-1980 New record: From date=01-MAY-1980 To date=01-MAY-1982 Updated existing record 2: From date=02-MAY-1982 To date=End of time /n 88Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files Incoming date range incl udes existing date rangeIf the incoming record contains the entire date range of the existing record for the same address type selected, then APPCUPD inserts a new record for the incoming address and changes the fitofl date on the incoming address. ExampleResult:Existing address with some null fields If an existing address record has some fields that are null and an incoming record has information that would update those fiel ds, where both have the same address type selected, then APPCUPD updates the exis ting record with th e new information. ExampleThe existing record includes street line 1, city, state, and ZIP code. The incoming record includes the same information plus street line 2 and country. The existing record is updated to include street lines 1 and 2, city, state, ZIP code, and country. Incoming record: From date=01-FEB-2000 To date=End of time Existing record:From date=01-APR-2000 To date=End of time New record: From date=01-FEB-2000 To date=31-MAR-2000 Existing record:From date=01-APR-2000 To date=End of time /n 89Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files Technical considerations The following processing tips apply to APPCUPD. Loading data You must do the following when yo u load information with APPCUPD: ŁVerify that the input file is in ASCII or .csv format. ŁUse the File Transfer Process (FTP) to transf er the file in ASCII mode via a Secure File Transfer to a directory that Banner can read from and write to. This directory depends on your operating system. This location is entered as one or more APPCUPD parameters (depending on the length of the data file path). ŁSave your file as a .dat file. Enter the new name as a parameter for APPCUPD. Header recordThe file might begin with a header record cont aining information provided by the vendor: ŁIf your file is charac ter delimited, APPCUPD igno res the header record. ŁIf your file is fixed length, APPCUPD tries to load the firs t line in the file. You should manually delete the header record before running APPCUPD. DatesAPPCUPD recognizes all potentia l Oracle date formats for the date on the input file. APPCUPD uses the following logic to determine the file source date: ŁAPPCUPD first checks the Data Field Positi on Rules Form (AGATPFD) for the file definition selected. If the mapping contains a reference to SOURCE_ACT_DATE, this value is used for the file source date. ŁIf AGATPFD does not contain a referenc e to SOURCE_ACT_DATE, APPCUPD checks the value in the File Source Da te parameter for a date entry. If defined, this value is used for the file source date. ŁIf neither of the previous checks provides a value, the system date when the run is executed is used as the file source date. /n 90Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files Load third-party gifts The External Gift Load Process (AGPEXGF) lo ads gift and pledge payment details from third-party processors into Banner, ensuring the safe handling of payment card and ACH transactions that are received from PCI- compliant payment card processing services. Before loading data, you must perform the setup steps described in fiSet up a data load or a data extractfl on page8 . Record typesThe data load files used with AGPEXGF must have at least two records for each gift that is being loaded. The first record includes base information for the gift. The other records include details for each campaign/designation co mbination in the gift. You must define the format of the base and detail record types on the Data Field Position Rules Form (AGATPFD). Base record (record number 01)The base record type is identified on AGATPFD by entering 01 in the Record Number field. The following fields must be included in the file definition: ŁBAN_ID (for authenticated gifts) ŁEXT_GIFT_EXT_GIFT_IDŁEXT_GIFT_REC_NUMŁEXT_GIFT_AMT_TOT ŁEXT_GIFT_GIFT_CODE Optional fields can also be included in the file definition. See fiData that can be loadedfl on page93 for additional fields that can be loaded. Note the following: ŁIf EXT_GIFT_GIFT_DATE (gift da te) is not included in the base record, AGPEXGF uses the current system date when gifts are loaded. ŁIf EXT_GIFT_ENTRY_DATE (gift entry date) is not included in the base record, AGPEXGF uses the current system date when gifts are loaded. ŁIf the EXT_GIFT_CASHIER (cashier) field is not included in the base record, AGPEXGF uses the ID of the person who runs AGPEXGF. /n 91Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files Detail record (record number 02) The detail record type is identified on AGATPFD by entering 02 in the Record Number field. The following fields must be included in the file definition: ŁBAN_IDŁEXT_GIFT_EXT_GIFT_IDŁEXT_GIFT_REC_NUMŁEXT_GIFT_CAMPAIGN ŁEXT_GIFT_DESGŁEXT_GIFT_DESG_AMTFormat of the data load file The following sections provide mo re details on the format of the data load files used with AGPEXGF. A data load file ca n be character delimited or fixed length, depending on how the file is defined on the Data File Validation Form (ATVTAPE). Character delimited data load file A character delimited file uses a special character (for example, a comma) to separate each field in a record. The following illustration shows a sample character delimited data load file. Each gift must have one base record (01) and one or more detail records (02). /n 92Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files The following figure shows a sample AGATPFD definition for the base record (record number 01) for a character delimited data load file: The following figure shows a sample AGATPFD definition for the detail record (record number 02) for a character delimited data load file: Fixed length data load file A fixed length file uses a predetermined, co nstant size for each field in a record. The following illustration shows a samp le fixed length data load f ile. Each gift must have one base record (01) and one or more detail records (02). /n 93Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files The following figure shows a sample AGATPFD definition for the base record (record number 01) for a fixed length data load file. The following figure shows a sample AGATPFD definition for the detail record (record number 02) for a fixed length data load file. Data that can be loaded AGPEXGF can load the following data into Ba nner. The ATVTPFD field names are used to define the file layout on the Data Field Position Rules Form (AGATPFD). The following fields can be loaded in the base record (01): ATVTPFD Field Name Description RequiredBAN_IDBanner ID PEXT_GIFT_AMT_TOT External gift amount P/n 94Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files The following fields can be loaded in the detail record (02): EXT_GIFT_CARD_AUTH_CODEExternal gift payment card transaction authorization code EXT_GIFT_CARD_REFR_ NUMBERExternal gift payment card transaction reference number EXT_GIFT_CASHIERExternal gift cashier EXT_GIFT_COMMENTExternal gift comment EXT_GIFT_ENTRY_DATEExte rnal gift entry date EXT_GIFT_EXT_GIFT_IDExternal gift identifierP EXT_GIFT_GCLS_CODE_1External gift class 1 EXT_GIFT_GCLS_CODE_2External gift class 2 EXT_GIFT_GCLS_CODE_3External gift class 3 EXT_GIFT_GIFT_CODEExternal gift typeP EXT_GIFT_GIFT_DATEExternal gift date EXT_GIFT_GIFT_DESCExtern al gift description EXT_GIFT_MATCH_RECEIVEDExtern al gift match form received EXT_GIFT_PGVE_CODEExternal gift giving vehicle code EXT_GIFT_REC_NUMExternal gift record number ( 01 for base record) PEXT_GIFT_SOLC_CODEExternal gift solicitation code EXT_GIFT_SOL_IDExternal gift solicitor Banner ID EXT_GIFT_SOL_ORGExternal gift solicitor organization ATVTPFD Field Name Description RequiredBAN_IDBanner ID PEXT_GIFT_CAMPAIGN External gift campaign (at least one) EXT_GIFT_DESGExternal gift designation (at least one) EXT_GIFT_DESG_AMTExternal gift designation amount (at least one) EXT_GIFT_EXT_GIFT_IDExternal gift identifierP EXT_GIFT_PLEDGE_NOExternal gift pledge number EXT_GIFT_REC_NUMExternal gift record number ( 02 for detail record) PATVTPFD Field Name Description Required/n 95Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files The following fields are available in order to load unauthenticated gifts. Values in these fields, if supplied, are populated in the APBWIDN table for temporary storage until the data is posted to the proper Banner Advancement tables. Using the following chart to add the fields to your file definition. These values can be added using the drop-down list on AGATPFD, which validates against ATVTPFD. These values can be added in any order. APBWIDN Name Required or optionalCommentATVTPFD Name APBWIDN_IDRequiredWeb ID created by a user not found in Banner. BAN_IDAPBWIDN_LAST_NAMEConditionally required Last Name of donor with no Banner PIDM. This field is used to determine if an unauthenticated gift is being processed. If not found (either because an invalid PIDM was supplied or no PIDM was supplied and this field is blank) an error will be received. This field is only required for gifts coming in without a valid Banner PIDM (APBWIDN_ID value), thus is conditionally required. NAME_LASTAPBWIDN_FIRST_NAMEOptional, but highly recommended First Name of donor with no Banner PIDM.Optional, but highly recommended if incoming gift is for a constituent not in Banner Advancement. NAME_FIRSTAPBWIDN_MIOptionalMiddle Name of donor with no Banner PIDM.NAME_MIDDLE APBWIDN_ATYP_CODEOptional Address Type of donor with no Banner PIDM. A parameter has been added to AGPEXGF so this field can be defaulted in if an unauthenticated gift record contains no value in this field. Logic was added to make sure the value coming in is a valid type code in Banner. Validates against ATVATYP. ADDR_CODE/n 96Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files APBWIDN_STREET_LINE1Optional, but highly recommended if incoming gift is for a constituent not in Banner Advancement. Street Line 1 of donor with no Banner PIDM.ADDR_STREET1APBWIDN_STREET_LINE2OptionalStree t Line 2 of donor with no Banner PIDM.ADDR_STREET2APBWIDN_STREET_LINE3OptionalStree t Line 3 of donor with no Banner PIDM.ADDR_STREET3APBWIDN_CITYOptional, but highly recommended if incoming gift is for a constituent not in Banner Advancement. Address City of donor with no Banner PIDM.ADDR_CITYAPBWIDN_STAT_CODEOptional. However, it is required on AGAWGIF for addresses in the U.S.A. Address State of donor with no Banner PIDM. Logic was added to make sure the value coming in is a valid state code in Banner. Validates against STVSTAT. ADDR_STATE APBWIDN_ZIPOptional. However, it is required on AGAWGIF for addresses in the U.S.A. Address Zip/Postal Code of donor with no Banner PIDM. ADDR_ZIP, ADDR_ZIP4, ADDR_ZIPCAPBWIDN_NATN_CODEOptional. However, it is required on AGAWGIF for addresses outside the U.S.A.Address Nation of donor with no Banner PIDM. Logic was added to make sure the value coming in is a valid nation code in Banner. Validates against STVNATN. ADDR_COUNTRY APBWIDN Name Required or optionalCommentATVTPFD Name /n 97Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files APBWIDN_TELE_CODEOptional Tele phone Type of donor with no Banner PIDM. A parameter has been added to AGPEXGF so this field can be defaulted in if an unauthenticated gift record contains no value in this field. Logic was added to make sure the value coming in is a valid type code in Banner. Validates against STVTELE.PHONE_CODEAPBWIDN_PHONE_AREAOptional Phone Number Area Code of donor with no Banner PIDM. PHONE_ALL, PHONE_AREA APBWIDN_PHONE_ NUMBEROptional Phone Number of donor with no Banner PIDM.PHONE_ALL, PHONEAPBWIDN_PHONE_EXTOptional Phone Number Extension of donor with no Banner PIDM. PHONE_EXTAPBWIDN_INTL_ACCESSOptional Inter national Access Code of Phone Number of donor with no Banner PIDM.PHONE_INTL_ACCESS APBWIDN_EMAIL_ ADDRESSOptional Email Address of donor with no Banner PIDM.EMAIL APBWIDN_EMAL_CODEOptional Ema il Code of donor with no Banner PIDM. A parameter has been added to AGPEXGF so this field can be defaulted in if an unauthenticated gift record contains no value in this field. Logic was added to make sure the value coming in is a valid type code in Banner. Validates against GTVEMAL.EMAIL_CODEAPBWIDN_DONR_CODEOptional on the input file, but required to add a new constituent in Banner Advancement. Donor Code of donor with no Banner PIDM. A parameter has been added to AGPEXGF so this field can be defaulted in if an unauthenticated gift record contains no value in this field. Logic was added to make sure the value coming in is a valid type code in Banner. Validates against ATVDONR. DONOR_CODEAPBWIDN_CTRY_CODE_ PHONEOptional Code designating the region or country. PHONE_COUNTRY_ CODEAPBWIDN Name Required or optionalCommentATVTPFD Name /n 98Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files Optionally, the following four parameters can be added before running the process via GJAPCTL.Steps Use the following steps to load gift details from third-party processors into Banner: ŁfiStep 1 - Run the External Gift Load Process (AGPEXGF) in report modefl on page99 ŁfiStep 2 - Review the output reportfl on page100 ŁfiStep 3 - Run the External Gift Load Process (AGPEXGF) in update modefl on page103 ŁfiStep 4 - Review and load the records into permanent Banner tablesfl on page103 APBWIDN NameComment ATVTPFD Name APBWIDN_ATYP_CODEAddress Type of donor with no Banner PIDM. A parameter has been added to AGPEXGF so this field can be defaulted in if an unauthenticated gift record contains no value in this field. Logic was added to make sure the value coming in is a valid type code in Banner. Validates against ATVATYP. ADDR_CODEAPBWIDN_TELE_CODETelephone Type of donor with no Banner PIDM. A parameter has been added to AGPEXGF so this field can be defaulted in if an unauthenticated gift record contains no value in this field. Logic was added to make sure the value coming in is a valid type code in Banner. Validates against STVTELE. PHONE_CODEAPBWIDN_EMAL_CODEEmail Code of donor with no Banner PIDM. A parameter has been added to AGPEXGF so this field can be defaulted in if an unauthenticated gift record contains no value in this field. Logic was added to make sure the value coming in is a valid type code in Banner. Validates against GTVEMAL. EMAIL_CODEAPBWIDN_DONR_CODEDonor Code of donor with no Banner PIDM. A parameter has been added to AGPEXGF so this field can be defaulted in if an unauthenticated gift record contains no value in this field. Logic was added to make sure the value coming in is a valid type code in Banner. Validates against ATVDONR. DONOR_CODE/n 99Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files Step 1 - Run the External Gift Loa d Process (AGPEXGF) in report modeRun the External Gift Load Process (AGPEXGF) in report mode. This allows you to test the data load without changing any data in Banner. AGPEXGF is run from the Process Submissi on Controls Form (GJAPCTL) with the following parameters: Parameter Description 01File Code File code for the appropriate data source. Select List or the Values pull-down arrow to see valid values from the Data File Validation Form (ATVTAPE). Required. 02Data Source IdentifierCode that identi fies the third-party processor. Select List or the Values pull-down arrow to see valid values from the Data Source I dentifier Validation Form (ATVDSRC). Required. 03Data File NameExact name of the file sent by the vendor. Required. 04Path of Data File - Part 1Directory where the data file is located. This must be a location where Banner can access it. If the data file path is longer than 30 char acters, parameters 05 and 06 are available for additional data file path details. Required.05Path of Data File - Part 2Additional details (up to 30 characters) for the directory where the data file is located. Used with parameter 04 when the data file path is longer than 30 characters. This entry is concatenated to the end of the details entered in parameter 04. Optional. 06Path of Data File - Part 3Additional details (up to 30 characters) for the directory where the data file is located. Used with the parameters 04 and 05 when the data file path is longer than 60 characters but less than 91 characters. This entry is concatenated to the end of the details entered in parameter 05. Optional. 07Report/Update ModeCode that determines whether the database is updated when the process is run: R - Print report; do not update database (default). U - Print report; update database. 08Date FormatDate format that ov errides the system-defined date format for this execution of AGPEXGF. Must be a valid Oracle date format. Used solely to evaluate incoming dates and load details to Banner. Optional. /n 100 Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files For more in formation about AGPEXGF, refer to the Banner Advancement User Guide .Step 2 - Review the output report Review the details on the AGPEXGF output re port. The report heading identifies the third- party processor and the sort order. The report body includes two sections for each gift: ŁThe base section includes information such as the donor™s Banner ID, Banner gift ID, external gift ID, gift type, giving vehi cle, gift date, and total gift amount. ŁThe detail section includes each campaign/designation combination in the gift and the associated amount. If an error occurs, an error message is displayed below the record where the error occurred. The following conditions result in an error message: ŁInformation is missing or invalid. ŁTotal gift amount does not equal the sum of detail gift amounts. Records with errors are not loaded to Banner. These records must be corrected in the data load file or manually loaded into Banner. 09Header Record ExistsCode that indica tes whether the data load file includes a header record: Y - Header exists (default). N - Header does not exist. 10Sort OrderReport sort order: 1 - ID (default) 2 - Name (last, first, middle) 3 - External gift ID Parameter Description /n 101Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files 13-OCT-2008 Watermark University PAGE 1 Release 8.1 External Gift Load Process AGPEXGF Gifts from All, Inc Report Only - Banner ID Order Banner ID Name 999744444 Geiser, Donald Banner Gift Number: REPORT External Gift ID: THREE Gift Type: CC - Credit Card Giving Vehicle: WWW - Web Credit Card Gift Date: 02-OCT-2008 Gift Classes: Total Gift Amount: $450.00 Gift Entry Date: 01-OCT-2008 Authorization Code: ABC123 Reference Number: REF1234567890 Solicitation: ABUS - Area Business Appeal Match Form Received: N Solicitor Organization: AFS - Annual Fund Solicitors Cashier: GSMITH Solicitor: 999743383 Comment: Errors: Solicitor ID does not exist in Banner. Pledge Number Campaign Designation Detail Amount 0000000 NOR - Norton Building Campaign ATHLS - Athletic Scholarships with a $200.00 really, really, really long 0000000 NOR - Norton Building Campaign BIMED - Biomedical Research Center $150.00 0000000 NOR - Norton Building Campaign BLCHR - Bleachers Restoration Fund $100.00 999745555 Geiser, George Banner Gift Number: REPORT External Gift ID: TWO Gift Type: CC - Credit Card Giving Vehicle: WWW - Web Credit Card Gift Date: 24-SEP-2008 Gift Classes: HONR - In Honor of Total Gift Amount: $300.00 MEMY - Memorial Gift Entry Date: 36-SEP-2008 ANON - Anonymous Authorization Code: ABC123 Reference Number: REF1234567890 Solicitation: ABUS - Area Business Appeal Match Form Received: N Solicitor Organization: AFS - Annual Fund Solicitors Cashier: GSMITH Solicitor: 999743333 - Geiser, S Craig Comment: In Memory of Mary Errors: Invalid Gift Entry Date. Pledge Number Campaign Designation Detail Amount 0000000 EXCEL - Campaign for Excellence & A BLCHR - Bleachers Restoration Fund $150.00 Errors: Invalid Campaign and Designation Combination. 0000000 NOR - Norton Building Campaign ATHLS - Athletic Scholarships with a $250.00 really, really, really long Errors: Detail amounts do not equal the Total Gift Amount. /n 102Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files 13-OCT-2008 Watermark University PAGE 3 Release 8.1 External Gift Load Process AGPEXGF Gifts from All, Inc Report Only - Banner ID Order Banner ID Name * * REPORT CONTROL INFORMATION * * parameter Message USER:........................ SGEISER Parameter Name Value Message _____ _____ ____________ 203421 File Code EXT_GIFTS Data Source Identifier GIFTCO Data File Name external_gifts.csv Path of Data File - Part 1 /export/home/sgeiser/ Path of Data File - Part 2 rel81/xsd/ Path of Data File - Part 3 [R]eport/(U)pdate Mode R Date Format DD-MON-YYYY Header Record Exists N Sort Order 1 Line Count 55 /n 103 Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files Step 3 - Run the External Gift Loa d Process (AGPEXGF) in update modeRun AGPEXGF as described in step 1, except enter U (update) as parameter 07 rather than R (report). In update mode, AGPEXGF loads the gift data into temporary tables. Step 4 - Review and load the reco rds into permanent Banner tables Use the following steps to review the third-pa rty gifts and move them from the temporary tables into permanent Banner tables. 1.Access the Review External Gifts Form (AGAWGIF). 2.Enter the ID whose external gifts you want to review. 3.Go to the Gift Details block. 4.Review the gift details and ma ke any changes, if necessary. 5.Select the OK to Load check box to approve the record. 6.Select Save. 7.Select Create Gift from t he Options menu to remove the record from the temporary table, load the approved record into the permanent Banner tables, and refresh AGAWGIF. Optionally, the Gift List Tab allows you to view a list of th e gifts along with a count of the gifts, specify which gifts should be loaded and reviewed and subsequently load all gifts, thereby bypassing the individual review process. In addition to displaying attributes that can also be viewed on the Gift Details tab , the Gift List tab contains options that allow you to control the display of the list and determine what action should be performed. These options include the following: OptionDescription Create Gifts Selecting this option allows you to load gifts for all gift transactions that have the Load check box checked. Check All / Uncheck All When the Check All check box is checked, the Load check box will be checked for all transactions, except those that have the Review check box checked. Any transaction that has the Review check box checked must have the Load check box checked manually. When the Check All check box is checked, the list will re-sort and all transactions with the Load check box checked will ap pear at the top of the list. Any transactions that have the Review check box checked will sort to the bottom of the list. The Check All an Uncheck All check boxes only dictate how transactions that appear on the Gift List will behave. These options do not apply to the Oracle query function. /n 104 Banner Advancement Data Load/Extract Handbook |Data Transfers Using Data Files Technical considerations The following processing tips apply to AGPEXGF. Loading data You must do the following when you load third-party gifts with AGPEXGF: ŁVerify that the input file is in ASCII format. ŁMake sure there are no blank lines in the data load file. The file cannot be loaded if it contains blank lines. ŁUse the File Transfer Process (FTP) to transf er the file in ASCII mode via a Secure File Transfer to a directory that Banner can read from and write to. This directory depends on your operating system . This location is entere d as one or more AGPEXGF parameters (depending on the length of the data file path). ŁEnter the file name as an AGPEXGF parameter. Header recordIf the file begins with a header record that contains information provided by the third-party processor, set parameter 09 (Header Record Exists) to Y. With this setting, AGPEXGF ignores the first record. DatesAGPEXGF recognizes all potentia l Oracle date formats for dates on the data load file. If parameter 08 (Date Format) is defined, this format is used for dates. If the parameter is not defined, the format of the curr ent system date is used for dates. LoadIf this check box is checked, t he gift transaction will be loaded when the Create Gifts option is selected. Transactions that do not have this check box checked will not be loaded. This check box is unchecked by default. This check box can be populated manually or via the Check All or Uncheck All options. ReviewWhen the batch posting routine occurs, any transactions that could not be posted will have a status of Revi ew Required. This is indicated by a check in this column and serves as an indication something needs to be fixed prior to being posted successfully. When this occurs, depending on the rules at your institution, you could either view this gift on the Gift Detail tab , fix the changes and attempt to post it there, or fix the issues on the Gift Detail tab and defer the posting of this gift until the next run on the Gift List tab. OptionDescription /n 105 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector Data Transfers Using the Advancement ConnectorThe Advancement Connector is a Banner® Advancement module that uses Web services to transfer data between Banner and partner products. This chapter provides instructions for loading data between Banner Advancem ent and Encompass, a Web-based social networking tool available from iModules. Note: Although this chapter targets integration between Banner Advancement and iModules Encompass, the Advancement Connector has a flexible design that can be used to integrate Banner Advancement with other partner products. Refer to the Advancement Connector Developer™s Guide for details on how to integrate Banner Advancement with other partner products. Integration with iModules Encompass The Advancement Connector uses Web services to share constituent data between your Banner database and the Encompass database. Shared data can include member, contact, education, spouse, family, business, activity, and honors information. Specific Banner database fields are mapped to specif ic Encompass database fields to ensure the integrity of both databases. See fiAppendix A - Advancement Connector Data Mappingsfl on page191 for a list of the supported data mappings. Data transfer between Banner and Encompass keeps both databases up-to-date and accurate. There are two ways to transfer data: ŁPush - You can collect changes in your Banner database and push them to the Encompass database. ŁPull - You can collect changes in the partner database and pull them to the Encompass database. Processing overviewBanner is the master repository for constituent data. Pushing Banner data changes to Encompass allows constituents to view their data in Encompass. Pulling Encompass data changes to Banner keeps the master repository current. This two-way transfer ensures the integrity of both databases. Information in Banner and Encompass might never be identical. For example, a constituent might change an address in Enco mpass immediately after changes are pulled /n 106 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector to Banner. The constituent change would not be reflected in Banner until the next pull was performed. Your synchronizat ion schedule determines the level of accuracy in each database. You should choose a frequency that is appropriate for your institution. The following sections provide an overview of the synchronization of data between Banner and Encompass. Data that can be synchronized Specific Banner database fields can be synchronized with specific Encompass database fields. The Advancement Connector Data Mapp ing Form (AUACMAP) is delivered with all data mappings that baseline Banner Advancement supports. Each mapping indicates whether the data can be pushed to Encompass and/or pulled from Encompass. You can create additional data mappings on AUACMAP if you want to synchronize other database fields. The baseline code, however , cannot process these additional data mappings. Your institution must make all codi ng changes (tables, forms, packages, and so on) needed to support the synchronizati on of additional database fields. ProfilesProfiles identify the specific Banner databas e fields that your institution wishes to synchronize with Encompass database fields. You need separate profiles for push and pull processing. Banner Advancement delivers profiles as seed data. You can also copy, create, modify, and delete profiles. Push processing flowThe following processing flow occurs when you push information from Banner to Encompass. 1.A Banner administrative user initiates push processing on the Advancement Connector Initiation Form (AUAINIT). This fo rm identifies the profile and the date/time parameters that are used to select the data that will be pushed. Optionally, the Scheduler Tab allows your institution to set predefined schedul es for the automatic running of push and pull profiles. 2.Banner Advancement performs the following processing: 2.1. Evaluates advancement constituents in the Banner database and selects data changes that were made to the profile data elements and have an activity date in the specified date range. If an activity date contains a date only (no time), only the date parameter on AUAINIT is used to determine whether the data change is pushed. For repeating data elements (such as degree majors, interest codes, and activity codes), the six newest records, based on activity date, are selected. For /n 107 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector example, if an interest code is added or changed, the six newest interest codes are selected for the push. 2.2. Collects the data changes into the AUBTROT table and organizes them into batches. A push transaction can have more than one batch. 2.3. Calls the iModules Web service for each batch in the push transaction. 3.The iModules Web service performs the following processing for each batch in the push transaction: 3.1. Updates the Encompass database with the changes extracted from Banner. 3.2. Sends a response to Banner that indicates whether the push was successful or had errors on the Encompass side. 4.The Banner administrative user views the push status and any messages from Encompass on the Run History tab of the Advancement Connecto r Initiation Form (AUAINIT). For additional information on push processing, please refer to fiPush data from Banner to Encompassfl on page122 .Pull processing flowThe following processing flow occurs when you pull information from Encompass to Banner. 1.A Banner administrative user initiates pu ll processing on the Advancement Connector Initiation Form (AUAINIT). This form identifies the profile and the date/time parameters that are used to pull data. Op tionally, the Scheduler Tab allows your institution to set predefined schedules for the automatic running of push and pull profiles. 2.Banner Advancement calls the iModules Web service for each batch. 3.The iModules Web service performs the following processing: 3.1. Evaluates the Encompass database to determine the appropriate updates to include in the Web service response, based on the data elements in the pull profile.3.2. Returns the data to Banner with a response message that indicates whether the pull was successful or had errors on the Encompass side. 4.For BIOGRAPHIC PULLS ONLY, Banner Adva ncement collects the constituents™ pulled data elements in the AUBTRIN table. Both changed data elements and context data elements are stored in the table. Changed data elements are flagged with an asterisk. A Banner administrative user performs the following tasks: 4.1. Views the pull status and any messages from Encompass on the Run History tab of the Advancement Connecto r Initiation Form (AUAINIT). 4.1. Uses the Advancement Connector Re view Form (AUACRVW) to compare Encompass data changes with existing Banner data, accept or reject the data changes, and post the approved changes to Banner. /n 108 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector 5.For GIFT PULLS ONLY, Banner Advancement collects the appropriate gift-related data. Any errors associated with the pull can be viewed on the Run History tab of AUAINIT. The actual review and posting of pulled gifts is performed in AGAWGIF. For additional information on biographic pull processing, please refer to fiPull biographic data from Encompass to Bannerfl on page128 .For additional information on gift pull processing, please refer to fiPull one-time, perpetual, and scheduled gifts from Encompass to Bannerfl on page149 .Set up the Advancement ConnectorIntegration between Banner and Encompass requires the following setups. Establish a relation ship with iModulesThe Advancement Connector for Encompass is included in the Banner Advancement baseline license. In order to use this functionality, an Encompass account must be established with Encompass. A client must contract with Encompass for the implementation of the Encompass Connector and access to the iModules web services. Please contact your iModules Account Manager for the necessary work order agreement. Install and configure t he Advancement ConnectorEnsure that your system administrator has installed the Advancement Connector. Instructions are contained in the Banner Advancement Connector Installation and Administration Guide. Once the Advancement Connector is installed, review the following configuration properties. These properties are configured with initia l values that facilitate immediate data exchange with Encompass. In most cases, you do not need to change these values. PropertyDescription Initial Value connector. delimiter Delimiter character used to separate elements in data transfer files, when flat files are used for data upload , (comma) (Required value for Banner/Encompass integration) connector. entityidlabel Column label for the entity identifier property when written to a delimited file format such as CSV SPRIDEN_PIDM (Required value for Banner/Encompass integration) /n 109 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector Configure Encompass properties Review the following Encompass pr operties, which were configur ed during the installation process. The initial values provide a reason able working environment for data exchange with Encompass. In most cases, you do not need to change these values. connector. implementationc lass ConnectorService implementation loaded by the Factory The initial value should be changed only if you customize the Encompass connection or connect with a different partner system. com.sungardhe. banner.advance ment.utility.connec tor. encompass. EncompassServi ceconnector. writefilepath File directory or path on the application server where data transfer files are written when a flat file is used to transmit data Your institution™s system administrator sets the value for this property and optionally makes this location available to the Banner Advancement administrative user who transfers data files to Encompass for upload. C:/advconnector/ (Assumes a Windows operating system) PropertyDescription Initial Value encompass.debug Flag that determines whether the Encompass service operations are in debug or operational mode: true - Debug mode false - Operational mode Keep the initial value unless your institution created a different implementation of an operation. falsePropertyDescription Initial Value /n 110 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector encompass. allowaddconstitu ents Flag that determines whether new Banner constituent records can be pushed to Encompass: true - Push new constituents to Encompass. Use this se tting if you create new constituent records in Banner and you want to transfer these new constituents to Encompass. false - Do not push new constituents to Encompass. This property applies only to push and update transactions. trueencompass. batchsize Maximum number of constituent records in a transfer batch. A constituent record can have any number of individual data changes. A transfer is divided into one or more batches, based on this property. The initial value is 1000, which iModules determined to be a reasonable starting value that balances data transfer size with performance of the Web service. You can change this value if the data transfer situation at your inst itution warrants it. 1000encompass. ignoremessages List of Encompass message codes that the Advancement Connector should ignore and not capture in the transfer status records or logs. If the list is empty, all messages are captured and recorded. This list does not apply to Encompass error codes, which are those elements found in the nodes of a response. You can comment out this property to temporarily enable messages without deleting the list. 2207PropertyDescription Initial Value /n 111 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector Encrypt credentialsEnsure that your system administrator has en crypted your login and password credentials for the iModules Web service. Instructions are contained in the Banner Advancement Connector Installation and Administration Guide . This document also describes alternative configurations that provide different ways to protect the Encompass login and password credentials, depending on your instit ution™s needs and security practices. encompass. includeblankids Flag that determines whether constituent records are pulled if they do not have a constituent ID: true - Pull records without a constituent ID. false - Do not pull records without a constituent ID. This property applies only to pull and get member transactions. The Advancement Connector does not support the processing of constituents that do not have a Banner PIDM. Therefore, this property value should remain false, unless you customize the behavior of Banner Advancement and the Advancement Connector. falseencompass. includenonmembers Flag that determines whether constituent records are pulled if they are not members of the community in Encompass: true - Pull non-members. false - Do not pull non-members. This property applies only to pull and get member transactions. trueencompass. timeoutMaximum number of seconds the service client waits for a resp onse from the iModules Web service. This property is used with the batch size to provide optimum performance. The initial value is 90, which iModules determined to be a reasonable starting value.90PropertyDescription Initial Value /n 112 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector Set the Advancement Connector URL in BannerUse the following steps to set the URL that Banner uses to call the Advancement Connector. 1.Access the Advancement Control Form (AGACTRL).2.Select the Institution tab 3.Select the Connector Defaults sub-tab. 4.Enter the base URL in the Connector URL field using this format: http(s)://:/advconnector/init 5.Select values from the applicable drop-downs. 6.Save.Establish your push/pull schedule Develop a push/pull schedule that is appropri ate for your institutio n. Follow the schedule rigorously to ensure data integrity. Your schedule might be daily, weekly, or some place between. The more frequently t he transfers occur, the smaller each data transfer will be. Optionally, use the scheduler to set predefined schedules for the automatic running of push and pull profiles. Manage data mappings Data mappings identify which Banner da tabase fields are synchronized with which Encompass database fields. The Advancement Connector Data Mapping Form (AUACMAP) is delivered with all data mappings that baseline Banner Advancement supports. Refer to fiAppendix A - Advancement Connector Data Mappingsfl on page191 for a list of the supported data mappings. Create a local data mapping You can create additional data mappings if you want to synchronize other database fields. Baseline Banner, however, cannot process these additional data mappings. You must make all coding changes to support the sy nchronization of additional database fields. Use the following steps to cr eate a local data mapping. 1.Access the Advancement Connector Data Mapping Form (AUACMAP). 2.Insert a new record. 3.Enter values in the following required fields: ŁConnector Name ŁFriendly Name /n 113 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector ŁReview Category ŁBanner Table Name ŁBanner Column Name 4.If this is an active da ta mapping, select the Active check box. You can have multiple data mappings for a data element, but only one mapping can be active at any time. Only active data mappings can be included in profiles on the Advancement Connector Pr ofile Form (AUACDEF). 5.Select the Push Allowed and/or Pull Allowed check box. At least one of the check boxes must be selected. 6.Save.7.Enter information as necessary in the Valid Profile Categor ies data block. This data block allows you to associate each data element in the Data Elements data block to the appropriate Profile Categories. As you navigate between Data Elements, the values in the Profile Categories data block ch ange in order to reflect the associations to the Data Element in context. For additional information, please refer to fiAUACMAPfl on page159 .8.Make all necessary coding changes to support the new data mapping (tables, forms, packages, and so on). Inactivate a data mapping Data mappings delivered in baseline Banner cannot be deleted. You can, however, inactivate a baseline data mapping to prevent it s use at your institution. Use the following steps to inactivate a data mapping. 1.Access the Advancement Connector Data Mapping Form (AUACMAP). 2.Select the record that you wish to inactivate. 3.Clear the Active check box. 4.Save.Manage profilesProfiles identify the specific Banner databas e fields that your institution wishes to synchronize with Encompass database fields. When you initiate a push or pull, you must specify the profile to be used. Banner Advancement delivers baseline profiles as seed data on the Advancement Connector Profile Form (AUACDEF). These baseline profiles are meant to serve as a starting point for each supported type of push and pull. As you create your institution- specific profiles, the recommendation is to reta in the original seed data profiles so you can refer back to them as necessary. Your institution should make copies of the seed data /n 114 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector profiles and rename and customize them as applicable in order to expedite the profile creation process. Note: BANNER PULL profile is the only seed data profile that can be used without modification. All other profiles must be configured by each institution prior to use. Local profilesIf you want to push or pull selected data elements, you can create local profiles on AUACDEF for your institution. You can create brand new profiles, or you can copy existing profiles and add, modify, and delete data elements as desired. The following general guidelines apply to local profiles: ŁPush processing and pull processing require separate profiles. ŁOnly active data elements mapped on the Advancement Connector Data Mapping Form (AUACMAP) can be included in a profile. ŁOnly those data elements flagged for push processing can be included in push profiles. Similarly, only those data elements flagged for pull processing can be included in pull profiles. Related data elements in pull profiles When you create a local pull profile, you should include all data elements that are related to the data changes you want to pull. By pulling related data elements, you can see the context of the changes during the review proce ss. You should also define a display order that groups related data elements together on the review form. For example, a profile that pulls preferred address changes should include all preferred address data elements and should specify a display order that groups these data elements together. The following table identifies the related data elements for each type of data that can be pulled from Encompass: Type of Pulled DataRelated Data Elements Primary e-mail Primary Email Primary Email Code Business e-mail Business E-mail Business E-mail Code /n 115 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector Preferred phone Preferred Phone Type Preferred Phone Address Type (hidden) (optional) Preferred Phone Address Sequence Number (hidden) (optional) Phone Country Code (optional) Phone Area Code (optional) Phone Number Phone Extension (optional) Business phone Business Phone Type Business Phone Address Type (hidden) (optional) Business Phone Address Sequence Number (hidden) (optional) Business Phone Country Code (optional) Business Phone Area Code (optional) Business Phone Number Business Phone Extension (optional) Preferred address Address Status (hidden) Preferred Address Type Preferred Address 1 Preferred Address 2 Preferred Address 3 Preferred Address 4 House Number CityState Zip CountryType of Pulled DataRelated Data Elements /n 116 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector Business address Business Address Status (hidden) (optional) Business Address Type Business Address 1 Business Address 2 Business Address 3 Business Address 4 Business House Number Business City Business State Business Zip Business Country Home fax phone Fax Phone Type (hidden) Fax Phone Address Type (hidden) (optional) Fax Phone Address Sequence Number (hidden) (optional) Fax Country Code (optional) Fax Area Code (optional) Fax Number Fax Extension (optional) Business fax phone Business Fax Phone Type (hidden) Business Fax Phone Address Type (hidden) (optional) Business Fax Phone Address Sequence Number (hidden) (optional)Business Fax Country Code (optional) Business Fax Area Code (optional) Business Fax Number Business Fax Extension (optional) EmploymentEmployer Name (optional) Job Title (optional) Job Category (optional) Type of Pulled DataRelated Data Elements /n 117 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector Selection valuesSome data elements, when used in push profiles, use a selection value to ensure that the correct data is extracted and pushed to Encompass. The following table indicates whether a selection value is required or optional for these data elements: For example, if you create a profile that us es the Business Email Code data element, you must enter a selection value to identify which e-mail type should be extracted and pushed to Encompass as the business e-mail address. A selection value can be entered for any data element in a push profile. However, selection values are supported only for those data elements that use a data element in baseline Banner. If your institution wants to use selection values for other data elements, you must make all coding changes to support this functionality. Selection value for Primary Donor Code data element By default, the baseline push profile updates da ta for all donor categories. If you want to limit updates to selected donor types, you can include the Primary Donor Code data element in the profile. Use the Selection Value field to identify the donor codes that should be included in the push. Multiple donor codes can be entered, each separated by a comma with no spaces. Push processing selects only those constituents whose primary donor code matches one of the codes in the Selection Value field. If the Selection Value field is left blank, all donor codes are sele cted. The primary donor code for each selected constituent is pushed to Encompass. Data Element Selection Value RequiredSelection Value OptionalSalutation Code PPrimary Donor Code PPreferred Address Type PPreferred Phone Type PFax Phone Type PJoint Salutation Code PMaiden Name Type PBusiness Email Code PBusiness Address Type PBusiness Phone Type PBusiness Fax Phone Type PDeceased P /n 118 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector ExampleTo push updates for alumni and non-degreed alumni only, include the following data element in the profile: ŁConnector Database Name : Primary Donor Code ŁSelection Value : ALND,ALUM Only alumni and non-degreed alumni are se lected for the push. For each selected ID, the primary donor code is pushed to Encompass Selection value for Deceased data element By default, the baseline push profile up dates data for both living and deceased constituents. If you wa nt to limit updates to deceased constituents or living constituents, you can include the Deceased data element in the profile. Enter one of the following values in the Selection Value field to indicate which constituents should be included in the push:Create a profile without copyingUse the following steps to create a new profile without copying an existing profile. 1.Access the Advancement Connector Profile Form (AUACDEF). 2.Enter a new profile code in the Profile Code field. Maximum length is 30 characters. 3.Press Tab. A popup window alerts you that your are creating a new profile. 4.Click OK in the popup window. 5.Enter a description of the profile in the Profile Description field. Maximum length is 60 characters. 6.Select a value ( PUSH or PULL) from the Transaction Type drop-down list. 7.Go to the next block. 8.Use the following steps to add each data element to the profile: 8.1. Select the name of an Encompass database field from the Connector Name drop-down list. The drop-down list for this field shows th e active data elements that can be used in the profile. The list also indicates whether the database field requires a selection value. blankInclude all living and deceased constituents in the push (default). NInclude living constituents only in the push. YInclude deceased constituents only in the push. /n 119 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector 8.2. If this is a push profile and the data elem ent requires a selection value, enter the value in the Selection Value field. This field is not validated, so enter the value carefully. A selection value is used by some data elements to extract and push the correct data to Encompass. Refer to fiSelection valuesfl on page117 for a list of data elements that require a selection value and a list of data elements that optionally use a selection value. 8.3. Enter a value in the Display Order field. The order must be unique for each data element. Maximum value is 9999. This value determines the order in which data elements are displayed on AUACDEF when the form is refreshed. For a pull profile, this value also determines the order in which data elements are displayed on the Advancement Connector Review Form (AUACRVW). 9.When all data elements are entered, save. Create a profile by copyingUse the following steps to create a new profile by copying an existing profile. Once you copy a profile, you can add, modify, and delete data elements as desired. 1.Access the Advancement Connector Profile Form (AUACDEF). 2.Enter a new profile code in the Profile Code field. Maximum length is 30 characters. 3.Press Tab. A popup window alerts you that your are creating a new profile. 4.Click OK in the popup window. 5.Enter a description of the profile in the Profile Description field. Maximum length is 60 characters. 6.Select a value ( PUSH or PULL) from the Transaction Type drop-down list. 7.Select a profile code from the Copy Profile Code drop-down list. This is the profile that you want to copy. The drop-down list displays the existing profiles that you can copy. For a new push profile, the drop-down list displays existing push profiles. For a new pull profile, the drop-down list displays existing pull profiles. 8.Go to the next block. A popup window asks if you want to create a profile. 9.Click Yes in the popup window. A popup window confirms the copy. 10. Click OK in the popup window. Data elements for the copied profile are displayed in the Profile Details block. /n 120 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector 11. To add a data element: 11.1. Go to a blank row or insert a new record. 11.2. Select the name of an Encompass database field from the Connector Database Name drop-down list. The drop-down list for this field shows th e active data elements that can be used in the profile. The list also indicates whether the database field requires a selection value. 11.3. If this is a push profile and the data elem ent requires a selection value, enter the value in the Selection Value field. This field is not validated, so enter the value carefully. A selection value is used by some data elements to extract and push the correct data to Encompass. Refer to fiSelection valuesfl on page117 for a list of data elements that require a selection value and a list of data elements that optionally use a selection value. 11.4. Enter a value in the Display Order field. The order must be unique for each data element. Maximum value is 9999. This value determines the order in which data elements are displayed on AUACDEF when the form is refreshed. For a pull profile, this value also determines the order in which data elements are displayed on the Advancement Connector Review Form (AUACRVW). 12. To modify a data element, change the value in the Connector Database Name , Selection Value , or Display Order field as desired. 13. To delete a data element: 13.1. Select the record to be deleted. 13.2. Remove the record. 14. When you are done, save. Modify a profileUse the following steps to modify a profile. 1.Access the Advancement Connector Profile Form (AUACDEF). 2.Select the profile code from the Profile Code drop-down list. 3.(Optional) Modify the profile description in the Profile Description field. Maximum length is 60 characters. 4.Go to the next block. Existing data elements are displayed. You can use the following steps to add, modify, and delete data elements, as desired. /n 121 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector 5.To add a data element: 5.1. Go to a blank row or insert a new record. 5.2. Select the name of an Encompass database field from the Connector Database Name drop-down list. The list of values for this field shows the active data elements that can be used in the profile. The list also indicates whether the database field requires a selection value. 5.3. If this is a push profile and the data elem ent requires a selection value, enter the value in the Selection Value field. This field is not validated, so enter the value carefully. A selection value is used by some data elements to extract and push the correct data to Encompass. Refer to fiSelection valuesfl on page117 for a list of data elements that require a selection value and a list of data elements that optionally use a selection value. 5.4. Enter a value in the Display Order field. The order must be unique for each data element. Maximum value is 9999. This value determines the order in which data elements are displayed on AUACDEF when the form is refreshed. For a pull profile, this value also determines the order in which data elements are displayed on the Advancement Connector Review Form (AUACRVW). 6.To modify a data element, change the value in the Connector Database Name , Selection Value , or Display Order field as desired. 7.To delete a data element: 7.1. Select the record to be deleted. 7.2. Remove the record. 8.When you are done, save. Delete a profileUse the following steps to delete a profile.1.Access the Advancement Connector Profile Form (AUACDEF). 2.Select the profile code from the Profile Code drop-down list. 3.Go to the next block. 4.Remove each data element. 5.Save. 6.Roll back to the key block. A popup window alerts you that detail records do not exist. 7.Click Yes to delete the profile. /n 122 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector Push data from Banner to Encompass The following tasks can be used to push data from Banner to Encompass. Note: To maintain data integrity, you must develop a push/pull schedule that is appropriate for your institution and follow the schedule rigorously. Load initial data to Encompass A lot of data must be loaded from Banner to Encompass when the integration is first implemented. To minimize network traffic and po ssible timeout, you s hould save the initial data load to a flat file. Th e Advancement Connector propertie s file identifies the file directory or path on the application server where this file is located. Note: You should always use a flat file, rather than the iModules Web service, to load la rge volumes of data. If you previously used local processes to integrate Banner with Encompass, you do not need to load data to Encompass. The only exception is if you plan to synchronize additional types of data. In this case, you shou ld create a flat file that contains the new types of data only. Use the following steps to create a fl at file for the initial data load. 1.Access the Advancement Connecto r Initiation Form (AUAINIT). 2.Select Push from the Initiation Selection drop-down list. 3.Select a category code from the Category Code drop-down list. This code identifies the ca tegory of data elements (Bio grapic or Gift) that will be extracted from Banner and pushed to Encompass. 4.Select a profile code from the Profile Code drop-down list. This code identifies the set of data elem ents that will be extr acted from Banner and pushed to Encompass. 5.Enter a date in the Begin Date field. Data changes with an activity date on or after this date will be selected. This date cannot be a future date. 6.(Optional) Select a time from the Begin Time drop-down list. Data changes with a timestamp on or after this time will be selected. 7.Select the CSV file radio button in the Output Format field.8.Enter the name of the output file in the File Name field. Maximum length is 30 characters. An extension in the file name is optional. If no extension is entered, the default is .csv. /n 123 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector Do not include the path in the file name. The path is specified in the Advancement Connector properties file. 9.Click Run. When processing is completed, a popup window confirms that the request was initiated.10. Click OK in the popup window. The assigned ID is displayed in the Request ID field. The output file is written to the location specified in the Advancement Connector properties file. 11. Select the Run History tab to check the status of the push process. Initiate a push processUse the following steps to initiate a push process. 1.Access the Advancement Connecto r Initiation Form (AUAINIT). 2.Select Push from the Initiation Selection drop-down list. 3.Select a category code from the Category Code drop-down list. This code identifies the ca tegory of data elements (Bio grapic or Gift) that will be extracted from Banner and pushed to Encompass. 4.Select a profile code from the Profile Code drop-down list. This code identifies the set of data elem ents that will be extr acted from Banner and pushed to Encompass. 5.Enter a date in the Begin Date field.Data changes with an activity date on or after this date will be selected. This date cannot be a future date. 6.(Optional) Select a time from the Begin Time drop-down list. Data changes with a timestamp on or after this time will be selected. 7.Choose one of the following values in the Output Format field: ŁWeb Service - Use the iModules Web service to push data ŁCSV file - Create a flat file of data changes 8.If you selected the CSV file format, ente r the name of the output file in the File Name field.An extension in the file name is optional. If no extension is entered, the default is .csv. Do not include the path in the file name. The path is specified in the Advancement Connector properties file. 9.Click Run. When processing is completed, a popup window confirms that the request was initiated.10. Click OK in the popup window. The assigned ID is displayed in the Request ID field./n 124 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector 11. Select the Run History tab to check the status of the push process. Each initiation request generates one or more batches of data to be synchronized. The number of batches depends on the numb er of transactions being processed and the batch size set in the Encompass properties file. Note: The best practice recommendation is to leave the Begin Time and End Time parameters blank. This will help ensure the desi red results are selected. CSV file creation processing and logic When deciding which Output Format (CSV file or Web Service) you wish to utilize, please note the following:ŁIn order to achieve efficiency for incremental data changes and efficiency for large data sets, the processing logic employs two different strategies for finding data for the different output formats. Using two different strategies means that each output format performs efficiently for its intended purpose. ŁThe logic for a push with an Output Format = Web Service expects smaller amounts of data, typically updates that would occur over a day or over a week. It has been designed to select incremental data changes throughout the collection of advancement individuals efficiently. ŁThe logic for a push with an Output Format = CSV file expects significantly larger amounts of data, especially given the primary usage of creating the initial files for iModules for data conversions and loads to Encompass. The logic for this scenario is designed to select data from the entire collection of advancement individuals efficiently. ŁOnce the qualifying profile data elements are selected to be included in the push, one processing step is to write these profile data elements to the transfer out table (AUBTROT). Profile data elements are writte n to the AUBTROT table only if the element contains data changes for an advancement individual. This substantially reduces the number of rows added to the table for each request. The reduced number of rows in the table improves the performance of the process and reduces the overall database resources required by the process. When the data in AUBTROT will be written to a CSV file, the CSV file writing proce ss ensures that all of the data elements in the profile have a column in the CSV file, and that all records have appropriate empty values for profile data elements where there were no data chan ges. This ensures that the CSV file retains the correct format. ŁSometimes, data values in the Advancement database can contain characters that are reserved characters in the CSV format, primarily the comma(','), double quote ('"'), and return/newline characters. In the CSV format, commas sepa rate values, double quotes enclose values that may contain commas, an d return/newline characters signal the end of a row in the file. The processing logic checks the data values coming from the Advancement database for these reserved c haracters. If a comma is present in the data value, the data value is enclosed in double quotes. Double quote characters in the data value are converted to single quote characters ('). Return/newline characters in the data values are removed, as are any leading or trailing spaces or tab characters. If a Push request receives a status of 'No Changes', this means that there are no updates that qualify to be included in the push. If the Output Format is CSV File, no .csv file will be /n 125 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector created. In this scenario, the 'No Changes' status communicates to the user that there were no updates to provide. Best practice recommendations for Web Service pushes and CSV file creationUse Web Service for incremental changes For incremental data changes, the push to Encompass using the web service is efficient for relatively small amounts of data, representing the collection of changes to advancement individuals' data over periods of a day or a week. Accepting incremental data changes the design and purpose of th e web service offered for the Encompass product. Most incremental pushes using the web service should complete in under a minute. While the selection process for web service pushes is very efficient at collecting incremental data changes throughout the collect ion of advancement individuals, it is NOT efficient at collecting all of the data elements in a profile for every advancement individual in the collection. Therefore, your institutio n should not attempt to do a web service push with a profile containing many data elements where the date range selected would cause some or most of the data elements for every advancement individual in Banner Advancement to be selected for transf er to Encompass. Use CSV file for large data sets For initial data loads to Encompass, the push o peration to create a CSV file is efficient for large amounts of data, representing all de sired data elements for every advancement individual that will be transferred to Encompass. The total time to create a f ile with data for a large number of advancement individuals (51,00 0 individuals in Ellucian's tests) ranges from 1 to 2 hours. Larger num bers of advancement individ uals will take proportionally longer, and smaller numbers will ta ke proportionally less time. The logic of the file creation operation is to check every single advancement individual in Advancement for data changes. Therefore, the to tal time to complete this operation is proportional to the number of advancement i ndividuals in your institution's Advancement system, regardless of the number of data elements in a profile, and regardless of the expected number of data changes the selecti on would pick up. This means that for push requests where you expect only a small number of data changes to be collected into the file, the operation using the file creation will take subst antially longer than the same operation done using the web service. In Elluci an's tests, finding a few data changes in a collection of 51,000 advancement individuals takes a few seconds when done using the web service option, but takes 10-12 minutes when done using the output to file option. Therefore, your institution should expect t hat writing incremental data changes to a CSV file will take much longer than the web service operation, and the time it takes will be proportional to the number of advancement indi viduals your institutio n has, and will not be proportional to the ex pected amount of data that will be collected. /n 126 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector Break up large data sets into multiple filesBased on the iModules' recommended CSV file size limit of 20MB, your institution may want to initiate multiple push requests, generating mu ltiple CSV files for the initial data load. If this is necessary, two possible options are: ŁUse the same push profile and initiate it multiple times, varying the Begin and End Date ranges to break the request into separate time periods. ŁUse different push profiles that each addre ss a certain set of data elements - bio, degrees, activities, spouse and children, etc. , and collect this data for all advancement individuals. Allocate sufficient memory to Java when writing large files When writing CSV files, the Advancement Connector uses a form of memory on the connector server called heap space. It is an a llocation of the server's memory to the Java virtual machine that is executing the code th at creates the CSV file from the data in the transfer out table. The more records the process writes out, the more heap space the Java virtual machine needs. If, during the file writing operation, the virtual machine runs out of heap space, the file wr iting process will terminate, without wr iting some of the records to the file, and the Java virtual machine will log an out of memory except ion. Therefore it is important to configure the connector OC4J cont ainer in the Oracle Application Server to allocate sufficient memory to the Java virtual machine. The installation instructions for this release increase the heap size for the connector's Java Virtual Machine (JVM) to 1536 Megabytes or 1.5 Gigabytes. In Ellucian's test s, this memory allocation was sufficient to allow the connector to write out 51,000 advanc ement individual records to a CSV file, with some room for writing a larger number than that. For more information on adjusting the JVM he ap size, refer to the Step 6 Increase the JVM heap size section in the p1-jg5hsb_alu8040001in.pdf .However, if your Advancement system has a su bstantially larger number of advancement individuals in it, you may need to allocate even more memory to the Java virtual machine, to get a successful file writ e, if you are writing the records out into one file. Once the large initial data lo ad files have been generated, yo u can reduce the amount of memory allocated to the Java virtual machine. For normal incremental data change operations, a heap size between 512 and 1024 Megabytes should be more that sufficient. View the status of a push process Use the following steps to view the status of a push process. 1.Access the Advancement Connecto r Initiation Form (AUAINIT). 2.Select the Run History tab. Each push request in the Initiation Requests block has one of the following statuses: ŁINITIATED : Transfer was initiate d and is in process. ŁCOMPLETED : Data was successfully pushed from Banner to Encompass. /n 127 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector ŁCOMPLETE WITH ERROR : Some data was pushed, but at least one data element had an error. ŁNO CHANGES : Push was initiated but there were no data changes in the requested date range.ŁFAILED : Transfer failed due to system or service issues. 3.In the Initiation Requests block, select the push process that you want to view. 4.Review the associated batch details in the Associated Batches block. 5.(Optional) Use the following steps to disp lay the iModules Web service response message for a batch: 5.1. Select a batch in the Associated Batches block. 5.2. Click Response Summary .5.3. Review the response message. 5.4. Click Close.Correct a push process that processed with errorsIf the status of a push process is COMPLETE WITH ERROR , some of the data elements were not pushed successfully. Use the following steps to correct the errors. 1.Access the Advancement Connecto r Initiation Form (AUAINIT). 2.Select the Run History tab. 3.In the Initiation Requests block, select t he push process that processed with errors. 4.Select the batch in the Associated Batches block that has the status COMPLETE WITH ERROR .5.Click Response Summary .6.Review the response summary. 7.Click Close.8.Use the appropriate Banner forms to correct the Banner data. 9.Re-run the push process. Special Handling when the Primary Donor Code has Changed in BannerEnhanced logic determines if the primary donor code is part of the information that has been updated for an advancement individual incl uded in a biographic push. If so, for these individuals only, all biographic data identified in the push profile and populated for this individual will be included in the push, regardle ss of the activity date associated with these records. This logic help s ensure that all relevant data is pushed to iModules Encompass when someone first becomes an advancement indi vidual. In these cases, it is likely that /n 128 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector much of their Banner biographic data was entered while they were a student and has older activity dates. Without this logic, the othe r types of data would not be included in the biographic push to iModules Encompass because these older activity dates are prior to the Biographic Push Begin Date value. Please note that this will result in a larger volume of data being included in the push for these particular scenarios. If the primary Donor Category code hasn't chan ged, only the biographic changes that falls within the specified date range for the push will be sent from Banner to iModules Encompass. This functionality applies to biographic data being pushed manually and by the scheduler. In addition to changes to the primary Donor Category code via students becoming advancement individuals, it is possible for the primary Donor Category code to change for other reasons, which would also trigger this new logic. While the Base Information tab on the APACONS form displays the primary Donor Category code, the Donor Categories tab on APACONS allows you to specify additional Donor Category codes. An individual may have multiple codes if they are, for exampl e, an Alumna/us, parent, and staff member. When multiple Donor Category codes exist, Banner uses the hierarchy specified on the Donor Category Co de Validation form (ATVDONR) to determine which is the primary Donor Category code. If an individual has a new record added to their list of Donor Category records on the Donor Categories tab on APACONS, and the new code has a higher priority (lower sequence number) than any of the existing Donor Category records, this will trigger a change in th eir primary Donor Category code and thus trigger this new logic that looks for changes to the primary Donor Category code. Warning! The push profile must include Donor Category as one of the elements. If it is not included, this logic that results in a full refresh of biographic data will not function. Pl ease refer to the Advancement Connector Data Mappings for a complete description of required mappings. Pull biographic data from Encompass to Banner The following tasks can be used to pull biographic data from Encompass to Banner. Note: To maintain data integrity, you must develop a push/pull schedule that is appropriate for your institution and follow the schedule rigorously. Initiate a pull processUse the following steps to initiate a pull process. 1.Access the Advancement Connecto r Initiation Form (AUAINIT). 2.Select the Initiation tab. 3.Select Pull from the Initiation Selection drop-down list. /n 129 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector 4.Select a category code from the Category Code drop-down list. This code identifies the category of da ta elements that will be extracted from Encompass. 5.Select a profile code from the Profile Code drop-down list. This code identifies the set of data elem ents that will be extr acted from Encompass. 6.Use the following steps to specify the date ra nge of the data changes that you want to pull:6.1. Enter a date in the Begin Date field.Data changes with an activity date on or after this date will be selected. This date cannot be a future date nor can this date be after the end date. 6.2. (Optional) Select a time from the Begin Time drop-down list. Data changes with a timestamp on or after this time will be selected. 6.3. (Optional) Enter a date in the End Date field. Data changes with an activity date on or before this da te will be selected. 6.4. (Optional) Select a time from the End Time drop-down list. Data changes with a timestamp on or before this time will be selected. 7.Click Run. When processing is completed, a popup window confirms that the request was initiated.8.Click OK in the popup window. The assigned ID is displayed in the Request ID field.9.Select the Run History tab to check the status of the pull process. Each initiation request generates one or more batches of data to be synchronized. The number of batches depends on the numb er of transactions being processed and the batch size set in the Encompass properties file. Batches initially include all constituents that had Encompass data changes during the requested date range. The paging limit determines the size of these batches. Constituents are then dropped from the batches if their changes do not match any data elements in the pull profile. For this reason, the final count of constituents in a batch may be smaller than the batch size set in the Encompass properties file. View the status of a pull process Use the following steps to view the status of a pull process. 1.Access the Advancement Connecto r Initiation Form (AUAINIT). 2.Select the Run History tab. Each pull request in the Init iation Requests block has one of the following statuses: ŁINITIATED : Transfer was initiate d and is in process. ŁREVIEW : Data was successfully pulled from Encompass and is ready for review. /n 130 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector ŁCOMPLETED : All data was successfully pulled from Encompass, reviewed, and posted to Banner. ŁNO CHANGES: Pull was initiated but there were no data changes in the requested date range.ŁFAILED : Transfer failed due to system or service issues. 3.In the Initiation Requests block, select the pull process that you want to view. 4.Review the associated batch details in the Associated Batches block. 5.(Optional) Use the following steps to disp lay the iModules Web service response message for a batch: 5.1. Select a batch in the Associated Batches block. 5.2. Click Response Summary .5.3. Review the response message. 5.4. Click Close.6.(Optional) To access pulled data that needs to be reviewed: 6.1. Select the pull process in the Initiation Requests block ( Type must be PULL and Status must be REVIEW ).6.2. Click Review . The Advancement Connector Review Form (AUACRVW) is displayed. 6.3. Use AUACRVW to review pulled data, take action, and post data changes. Review and post data changes The Advancement Connector Review Form (AUACRVW) is used to review and take action on a constituent™s data changes. You c an choose to insert the data changes into Banner, modify existing Banner data, or reject the changes. Once you take action on all data changes for a constituent, you can post the constituent™s data changes to Banner. AUACRVW displays unposted data changes only. When all data changes for a constituent are reviewed and successfully posted to Banner, AUACRVW no longer displays the constituent. When all constituents in a pull process are reviewed and posted, AUACRVW no longer displays the pull process. The profile used to pull data from Encompass determines which data elements are displayed for review on AUACRVW. If at least one data change is pulled for a constituent, then all data elements in the profile are pulled and displayed on AUACRVW in the order defined in the pull profile. To facilitate the review process, a pull profile should include all data elements related to the data that you want to pull. The profile should also define the display order so that related data elements are displayed together on AUACRVW. For example, a profile intended to pull preferred address changes should include all preferred address data elements and should specify a display order that groups these data elements together on AUACRVW. /n 131 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector You should review related data elements as a group so you can see the context of the data changes. Two flags on AUACRVW are used during the review process: ŁA number sign (#) flags the fimasterfl data element in each group of related data elements. For example, the Preferred Address Type data element is flagged to indicate that it is the fimasterfl data element fo r the preferred address data elements. ŁAn asterisk () flags those data elements that have different values in Banner and Encompass. The following table lists the fimasterfl data element for each type of data: If any data element in a group has a data chan ge flagged with an asterisk (), the fimasterfl data element requires an action. The selected action applies to all data elements in the group. If a group has no data changes, the fimasterfl data element does not require an action. Normally you can select an action for fimasterfl data elements only. The only exception is the ability to select the reject action for any data element. This action does not affect other data elements in the group. ExampleA constituent updates his preferred addres s in Encompass. All components of the preferred address are pulled from Encompass and displayed on AUACRVW. You want to accept all parts of the address except st reet line 2. Preferred Address Type is the fimasterfl data element for preferred addr ess information. The following actions allow you to insert a new Banner record with all of the updates except street line 2: Type of Data fiMasterfl Data Element Primary e-mail Primary Email Code Business e-mail Business Email Code Preferred address Preferred Address Type Business address Business Address Type Preferred phone Preferred Phone Type Business phone Business Phone Type Home fax phone Fax Phone Type Business fax phone Business Fax Phone Type Cell phone Cell Phone Type Employment Employer Data Element ActionPreferred Address TypeInsert /n 132 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector It is important to understand the differenc e between the insert and modify actions: ŁThe insert action inserts a new Banner record with the pulled data changes. Use this action if there is no existing Banner record or if you need to keep the existing Banner record as an audit trail. (An audit trail record is created where it is supported for repeating fields in Banner.) ŁThe modify action modifies an existing Banner record with the pulled data changes. This action overwrites existing values and can be used if you do not need to keep an audit trail of the existing Banner record. ExampleA constituent updates his primary e-mail address in Encompass. All components of the e-mail address are pulled and displayed on AUACRVW. Primary Email Code is the fimasterfl data element for the pulled data. You want to keep an audit trail of the existing primary e-mail address, so you select the Insert action for the Primary Email Code data element. This action inse rts a new e-mail record into Banner without overwriting the exis ting e-mail record. ExampleA constituent changes the suite number (address line 2) in her Encompass business address. All components of the business address are pulled and displayed on AUACRVW. Business Address Type is the fimasterfl data element for the pulled data. You do not want to keep an audit trail of the change, so you select the Modify action for the Business Address Type data element. This action updates the business address in Banner, overwriting the previous address line 2. Use the following steps to review and post data changes to Banner. 1.Access the Advancement Connector Review Form (AUACRVW). 2.Select a pull process from the Request ID drop-down list. This is the ID that was assigned to the pull process when it was initiated on the Advancement Connector Initiation Form (AUAINIT). The list of values displays IDs for pull processes that have unreviewed data changes. Preferred Address 1null (no action) Preferred Address 2Reject Preferred Address 3null (no action) Preferred Address 4null (no action) Citynull (no action) Statenull (no action) Zipnull (no action) Data Element Action/n 133 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector 3.Select the Encompass data source code from the Data Origin drop-down list. This code identifies Encompass as the sour ce of the data changes. This source code is assigned to all Encompass data changes that are posted to Banner. 4.Choose one of the following: 4.1. If your institution tracks the address source for pulled data changes, select the Encompass address source code from the Address Source drop-down list. When address changes are posted to Banner, this source code is assigned to pertinent address records in Banner. 4.2. If your institution does not track the address source for ulled data changes, leave the Address Source field blank. 5.Go to the Unreviewed Constituents bloc k to view the consti tuents that have unreviewed data changes. 6.Select the constituent that you want to review. The Constituents Updates block displays the data elements that were pulled for the constituent. The profile used to pull data from Encompass determines which data elements are displayed.. If at least one data change is pulled for a constituent, then all data elements in the profile are pulled and displayed in the order defined in the pull profile.7.Go to the next block. 8.(Optional) If you want to review a specific type of data, select the review category from the Review Category drop-down list. Note: Although you can review and take action on data changes for a specific review category, you mu st review and take action on all data changes before you can post any changes to Banner. If you select a review category and then want to remove the filter, clear the Review Category field and select Next Item or Next Block to display the entire list of data changes. 9.Use the following steps to review each group of related data elements that were pulled for the constituent. If the pull profile is defined properly, related data elements are displayed together on AUACRVW. Each group of related data elements has a fimasterfl data element that is flagged with a number sign (#). If any data element in the group has a data change flagged with an asterisk (), the fimaste rfl data element requires an action. The selected action applies to all data elements in the group. If a group has no data changes, the fimasterfl data element does not require an action. 9.1. Review the Connector value for each data element in the group. These are the values that were pu lled from Encompass. 9.2. (Optional) If you need to change a Connector value before it is posted to Banner, enter the change in the appropriate Connector Value field and select Save. (This is how you can cleanse pulled addresses to meet your institution™s format standards.) /n 134 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector You can change any Connector value, w hether it matches the Banner value or not. If the Connector and Banner values originally matched and your change causes the values to no longer match, an asterisk is automatically assigned to the data element when you save the change. 9.3. (Optional) If you want to reject the Conn ector value for a specific data element without affecting other data elements in the group, select Reject from the Action drop-down list for the data element. Th is is the only action allowed for a data element that is not a fimasterfl data element. 9.4. Choose one of the following values from the Action drop-down list for the group™s fimasterfl data element (the data element flagged with a number sign): ŒInsert : This action inserts a new Banner record with the Connector values. Select this action if either of the following conditions exists: * The Current Banner Value fields are blank. * The Current Banner Value fields have values that you want to keep as an audit trail. (An audit trail record is cr eated where it is supported for repeating fields in Banner.) ŒModify : This action modifies an existing Banner record wi th the Connector values. Select this action if you do not need to keep an audit trail of the existing Banner record. This action overwrites existing values, so make sure this is the desired result. ŒReject : This action rejects all Connector values in the group of related data elements. Note: If you select an invalid action, the Action field does not accept your selection and an error message is disp layed in the auto hint at the bottom of the form. Be alert to any error messages when you select an action. 10. Ensure that an action is selected for each group of related data elements. You must take action on all groups that have data changes before you can post the constituent™s data changes to Banner. If yo u take action on some but not all changes for a constituent, the actions are saved but not posted to Banner. 11. Select Save. 12. Click Post Updates to validate and post the constituent™s changes to Banner. Note: If you change a Connector value or action to correct an error or warning message, you must save the change and then click Post Updates again. 13. Repeat steps 6 through 12 for each constituent in the pull process. The specific Banner updates for each type of pulled data changes are described in fiBanner updates for pulled data changesfl on page135 ./n 135 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector Banner updates for pulled data changes When you review data changes on AUACRVW, you can choose to insert a new Banner record, modify an existing Banner record, or reject the changes. It is important to understand the difference between the Insert and Modify actions: ŁThe Insert action inserts a new Banner record with the pulled data changes. This action should be used if there is no existing Banner record or if you need to keep the existing Banner record as an audit trail. (An audit trail record is created where it is supported for repeating fields in Banner.) ŁThe Modify action modifies an existing Banner record with the pulled data changes. This action overwrites existing values and can be used if you do not need to keep an audit trail of the existing Banner record. Some situations may require more sophisti cated handling than AUACRVW provides. In these cases, you should reject the changes on AUACRVW and update Banner manually. The following sections describe th e result of each action for the various types of data that can be pulled from Encompass. Primary e-mailThe following data elements can be pulled from Encompass: ŁPrimary EmailŁPrimary Email Code If an existing Banner e-mail record is flagged as fipreferred,fl the Current Banner Value fields on AUACRVW display information for that e-mail record. If no existing Banner e-mail record is flagged as fipreferred,fl the Current Banner Value fields are blank. You must take one of the following actions if the pulled values are different from the existing Banner values: ActionResult InsertThis action inserts a new e-mail record into Banner. The record is flagged as fiactivefl and fipreferred.fl The fipreferredfl flag on the existing preferred e-mail record, if there is one, is removed. If the pulled values match the values in an existing Banner e-mail record, the insert action is not allowed. ModifyThis action updates the existing fip referredfl e-mail record in Banner with the pulled information. The e-mail types of the old and new records do not have to match. This action overwrites existing Banner values, so use it carefully. If there is no existing fipreferredfl e-mail re cord in Banner, the modify action is not allowed.RejectAll data changes are rejected. Banner is not updated. /n 136 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector Business e-mail The following data elements can be pulled from Encompass: ŁBusiness E-mail ŁBusiness E-mail Code Push processing and pull processing assume that one e-mail type is used to indicate business e-mail addresses. The push profile specifies the e-mail type that is used to push and pull business e-mail addresses for all consti tuents. If your institution has other policies related to business e-mail addresses, you may need to update business e-mail addresses manually rather than use AUACRVW. The Current Banner Value fields on AUACRVW display information for the business e-mail record as follows: ŁIf Banner has one active business e-mail record with the same e-mail type that was pulled from Encompass, then AUACRVW displays that record. ŁIf Banner has multiple active business e-mail records with the same e-mail type that was pulled from Encompass, then AUACRVW displays the e-mail record with the most recent activity date. ŁIf Banner has no active business e-mail records with the same e-mail type that was pulled from Encompass, then the Current Banner Value fields are blank. You must take one of the following actions if the pulled values are different from the existing Banner values: ActionResult InsertThis action inserts a new business e-mail record into Banner. The record is flagged as fiactive.fl If the pulled values match the values in an existing Banner e-mail record, the insert action is not allowed. ModifyThis action updates the business e-ma il address in the existing active Banner record that has the same e-mail type code that was pulled from Encompass. If multiple Banner records have the same e-mail type code, the record with the most recent activity date is updated. This action overwrites existing Banner values, so use it carefully. If there is no existing active e-mail record in Banner that has the same e-mail type code that was pulled from Encompass, the modify action is not allowed. RejectAll data changes are rejected. Banner is not updated. /n 137 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector Preferred phoneThe following data elements can be pulled from Encompass: ŁPreferred Phone Type ŁPreferred Phone Address Type (hidden) (optional) ŁPreferred Phone Address Sequence Number (hidden) (optional) ŁPhone Country Code (optional) ŁPhone Area Code (optional) ŁPhone Number ŁPhone Extension (optional) The profile that is used to push preferred phone numbers to Encompass affects the preferred phone numbers that are pulled from Encompass: ŁIf the push profile specifies a preferred phone type, then that phone type is used to push and pull preferred phone numbers for all constituents. For each constituent, the fiprimaryfl phone number that has this phone type is synchronized between Banner and Encompass. ŁIf the push profile does not specify a pref erred phone type, then the fiprimaryfl phone number that is associated with the most cu rrent preferred address is pushed and pulled for each constituent. The pref erred address is determined by the preferred address type on the Advancement Individual Information Form (APACONS). Preferred telephone is first searched for using the Telephone Type, Address Type and Address Sequence number returned from Encompass. If an exact match of the three fields is found on an active SPRTELE record, the data for this record is displayed in the Current Banner Value column for the preferred telephone data elements. If an exact match is not found on the above three fields, the SPRTELE table is searched for an active telephone record that matches th e Telephone type only. If only one record is found, the data from that record is displayed in the Current Banner Value column. If more than one record is found, the records are sorted by the Primary Indicator first and then the Activity Date. The re cord having the most recent Activity Date and having the Primary indicator checked would be selected for display. If there are no matching phone records that have the Primary checkbox checke d, then the matching one having the most recent Activity Date value would be disp layed in the Current Banner Value column /n 138 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector You must take one of the following actions if the pulled values are different from the existing Banner values: ActionResult InsertThis action inserts a new phone record into Banner. The record is flagged as fiprimaryfl and this phone record is autom atically linked to the preferred address record. Insert is not allowed if an existing Banner phone record has the same phone type, phone number, address type, and sequence number as Encompass. If the new phone record is tied to an add ress, only one phone record with that phone type, address type, and sequence number can be flagged as fiprimary.fl The fiprimaryfl flag is removed from any existing phone records that have the same phone type, address type, and seque nce number as the new record. If it is not tied to an address, multiple phone records can be flagged as fiprimary.fl If the pull request also included changes to preferred address information for this constituent, this is recognized in the enhanced logic. Therefore, the inserted phone record would be associated with the preferred address record that would exist after all updates are pos ted for this constituent for this pull. ModifyThis action updates the existing fipri maryfl phone record in Banner that has the same phone type, address type, and sequence number that were pulled from Encompass. This action overwrites existi ng Banner values, so use it carefully. If there is an existing primary active phone record linked to the current preferred address record, the primar y checkbox will be unchecked on this phone record. This is because the alumnus has provided an updated preferred phone # that should now be associated with the preferred address record. Since an address record cannot have more than one primary phone record associated with it, this update is required. The existing phone record will not be inacti vated as it is not certain that this phone number is invalid. If this Encompass pull also included a preferred address type change for this constituent and Insert was selected fo r handling this update, any existing phone records associated with the ‚old ™ preferred address are marked as inactive. This reflects the standard handling that would occur in Banner Advancement when the same transactions are entered online. If no matching phone record is found, when the user tries to select the Modify action on the review form, they'll see that it is not accepted by the system (it is blanked out) as it is not a valid action if an existing address record for this address type does not exist. RejectAll data changes are rejected. Banner is not updated. /n 139 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector Business phone The following data elements can be pulled from Encompass: ŁBusiness Phone Type ŁBusiness Phone Address Type (hidden) (optional) ŁBusiness Phone Address Sequence Number (hidden) (optional) ŁBusiness Phone Country Code (optional) ŁBusiness Phone Area Code (optional) ŁBusiness Phone Number ŁBusiness Phone Extension (optional) The profile that is used to push business phone numbers to Encompass affects the business phone numbers that are pulled from Encompass: ŁIf the push profile specifies a business phone type, then that phone type is used to push and pull business phone numbers for all constituents. For each constituent, the fiprimaryfl phone number that has this phone type is synchronized between Banner and Encompass. ŁIf the push profile does not specify a business phone type, then the fiprimaryfl phone number that is tied to a constituent™s business address is pushed and pulled for each constituent. The Current Banner Value fields on AUACRVW display information for the fiprimaryfl Banner phone record that matches the phon e type, address type, and sequence number that were pulled from Encompass. If no Banner phone record meets these criteria, the Current Banner Value fields are blank. Note: In some cases, the address type and sequence number are blank for the business phone. For example, a cell phone might be the business phone without being tied to an address. /n 140 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector You must take one of the following actions if the pulled values are different from the existing Banner values: Preferred addressThe following data elements can be pulled from Encompass: ŁAddress Status (hidden) ŁPreferred Address Type ŁPreferred Address 1-4 ŁHouse Number ŁCityŁState ŁZipŁCountryActionResult InsertThis action inserts a new phone record into Banner. The record is flagged as fiprimary.fl If the new phone record is tied to an address, then only one phone record with that phone type, address type, and sequence number can be flagged as fiprimary.fl The fiprimaryfl flag is removed from any existing phone records that have the same phone type, address type, and sequence number as the new record. If the new phone record is not tied to an address, then multiple phone records with that phone type, address type, and sequence number can be flagged as fiprimary.fl If an existing Banner phone record has the same phone type, phone number, address type, and sequence number that were pulled from Encompass, the insert action is not allowed. ModifyThis action updates the existing fipri maryfl phone record in Banner that has the same phone type, address type, and sequence number that were pulled from Encompass. This action overwrites existi ng Banner values, so use it carefully. If there is no existing fiprimaryfl phone re cord in Banner that matches the phone type, address type, and sequence number that were pulled from Encompass, the modify action is not allowed. RejectAll data changes are rejected. Banner is not updated. /n 141 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector The profile that is used to push preferred addresses to Encompass also affects the preferred addresses that are pulled from Encompass to Banner: ŁIf the push profile specifies a preferred address type, then that address type is used to push and pull preferred addresses for all constituents. For each constituent, the address that has this address type is synchronized between Banner and Encompass. ŁIf the push profile does not specify a prefer red address type, then the preferred address type that is defined for a c onstituent on the Advancement Individual Information Form (APACONS) is used to synchronize the constituent™s preferred address between Banner and Encompass. If no address type is returned from Encompass, the current preferred address type in Banner (APBCONS_ATYPE_CODE_PREF) is us ed to display the preferred address information in the Current Banner Value column. If an address type is returned from Encompass, that address type is used to locate a current address record with the matching add ress type. If no curr ent address record matches the address type returned from Encompass, no data is displayed in the Current Banner Value column. /n 142 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector You must take one of the following actions if the pulled values are different from the existing Banner values: ActionResult InsertThis action inserts a new address re cord into Banner. The current date is stored as the start date. If the existing preferred address in Banner has the same address type that was pulled from Encompass but the address details are different, yesterday™s date is stored as the end date for the existi ng address. This allows you to keep the existing record for audit purposes. If the preferred address type value pulled from Encompass is different than the current preferred address type in Banner Advancement (per APACONS), the preferred address type (APBCONS_ ATYPE_CODE_PREF) is updated automatically in Banner Advancement to reflect the address type retrieved from Encompass. If an address record currently exists in Banner that matches the address type retrieved from Encompass, this address record is inactivated. This is done automatically via population of the To Date field with yesterday™s date, which results in the Inactivate Ad dress check box being checked. If a change to the Encompass preferred phone information is also provided as part of this Encompass update AND the Insert action is the selected for handling this updated phone information, a new phone record is inserted and is associated with this new address record after appropriate processing on the review form. In this case, no phone records currently associated with the existing preferred address record need to be re-associated with this new address record. If this Encompass update does not include any new preferred phone update, the connector logic automatically re-asso ciates the primary phone record tied to the current preferred address record in Banner to the newly inserted preferred address record. In both scenarios above for phone records, there would be no updates to existing non-primary phone numbers associated with the old preferred address record. If the existing preferred address record in Banner has the same address details that were pulled from Encompass, the insert action is not allowed. /n 143 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector Business address The following data elements can be pulled from Encompass: ŁBusiness Address Status (hidden) (optional) ŁBusiness Address Type ŁBusiness Address 1 ŁBusiness Address 2 ŁBusiness Address 3 ŁBusiness Address 4 ŁBusiness House Number ŁBusiness City ŁBusiness State ŁBusiness Zip ŁBusiness Country ModifyIf the preferred address type value pulled from Encompass is different than the current preferred address type in Banner Advancement (per APACONS), the preferred address type (APBCONS_ ATYPE_CODE_PREF) is updated automatically in Banner Advancement to reflect the address type value retrieved from Encompass. If there is, a matching active address found in Banner with a the same address type, the sane matching address record is updated to reflect the changes pulled over from Encompass and displayed on the Review form when the user saves and posts this constituent™s updates. If no matching address record is found, when the user tries to select the Modify action on the review form, they™ll see that it is not accepted by the system (it is blanked out) as it is not a valid action if an existing address record for this address type does not exist. The user can tell if a matching existing record has been found as it would have its values displayed in the Current Banner Value column on the review form. In this scenario, since the user is choosing to ‚Modify™ the existing address record, no updates are performed to ex isting phone records as part of this address update. However, if there were actual preferred phone updates included from Encompass for this constituent, the rules for handling Preferred Phone Updates would be used. Please see the rules for handling Preferred Phone Inserts and Modifies found later in subsequent pages of this document. RejectAll data changes are rejected. Banner is not updated. ActionResult /n 144 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector The profile that is used to push business addresses to Encompass also affects the business addresses that are pulled from Encompass to Banner: ŁIf the push profile specifies a business addr ess type, then that address type is used to synchronize all business addresses between Banner and Encompass. ŁIf the push profile does not specify a business address type, then the business address that is associated with a constituent™s curren t active employment record is synchronized between Banner and Encompass. The Current Banner Value fields on AUACRVW display information for the Banner address record that matches the address type pulled from Encompass and is active in Banner when the data changes are being reviewed on AUACRVW. If no Banner address record meets these criteria, the Current Banner Value fields are blank. You must take one of the following actions if the pulled values are different from the existing Banner values: Business addresses and primary employment When appropriate, institutions may associ ate the primary employment record to an address record on the APAEHI S form. To accommodate this and streamline the process, logic allows you to maintain or establish links between the appropriate business address and primary employment records when pulling updates from Encompass to employment or business address information. ActionResult InsertThis action inserts a new address re cord into Banner. The current date is stored as the start date. If the existing business address in Ban ner has the same address type that was pulled from Encompass but the address details are different, yesterday™s date is stored as the end date for the existi ng address. This allows you to keep the existing record for audit purposes. If the existing business address record in Banner has the same address details that were pulled from Encompass, the insert action is not allowed. ModifyThis action updates the business address record in Banner with the pulled information. This action overwrites existi ng Banner values, so use it carefully. If no active business address record in Banner matches the pulled address type, the modify action is not allowed. RejectAll data changes are rejected. Banner is not updated. /n 145 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector If any of the new three employment fields ha ve changes that are pulled from Encompass, the following actions are available on AUACRVW: ActionDescription Employment Updates - Insert Insert new employment record A new employment record is inse rted and marked as the primary employment record. It will contain the updated values pulled from Encompass for the Employer Name, Job Title and Job Category fields. Update existing employment record that does not include updates to Business Address If there is an existing primary employment record, the primary indicator will be unchecked. If the update from Encompass does NOT include any updates to the Business Address information, the new primary employment record will NOT be linked to an a ddress automatically. Any linking needs to be performed manually by institutional personnel. This automatic linking does not occur because it is assumed if there is a new business address for the new employer, the alumni would have provided the updates in Encompass, in which case the employment and address records would be linked automatically, as described below. Update existing employment record that does includes updates to Business Address If there is an existing primary employment record, the primary indicator will be unchecked. If the update from Encompass also includes a change to any of the Business Address data elements and the INSERT or MODIFY action is selected for posting the business address updates, the new primary employment record will be tied to the new or modified business address record. This may occur when an alumni changes jobs and provides that information along with an updated business address, in which case the employer and business address should be associated to each other. Update a Business Address update when there are no updates to the Employer- related fields If the current primary employment record is NOT associated with an address record, no address link changes will be made to the primary employment record. If the current primary employment record is associated to an address record, the system will de termine if the address record linked to the primary employer record has the same address type as the business address record for which the updates were pulled. If it does, in addition to the standard business address update logic, the prim ary employer record will be updated to point to this new business address record. If it doesn't, no additional processing is performed for employment record purposes. /n 146 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector Home fax phoneThe following data elements can be pulled from Encompass: ŁFax Phone Type (hidden) ŁFax Phone Address Type (hidden) (optional) ŁFax Phone Address Sequence Number (hidden) (optional) ŁFax Country Code (optional) ŁFax Area Code (optional) ŁFax Number ŁFax Extension (optional) The profile that is used to push home fax phone numbers to Encompass affects the home fax phone numbers that are pulled from Enco mpass. The profile specifies the home fax phone type. For each constituent, the fiprimaryfl fax number that has this phone type is synchronized between Banner and Encompass. The Current Banner Value fields on AUACRVW display information for the fiprimaryfl Banner phone record that matches the phon e type, address type, and sequence number that were pulled from Encompass. If no Banner phone record meets these criteria, the Current Banner Value fields are blank. Employment Updates - Modify Update employment record without Employer Name If the update does not include an update to the Employer Name, the existing primary employer record will be updated with the new Job Title and/or Job Category an d all other values will remain as- is.Update employment record with Employer Name that does not include an Employer IDIf the update includes a change to the Employer Name and the current primary employment record does NOT have the employer ID populated (i.e. the employer name is entered in the employer text field), standard modification logic will occur. Update employment record with Employer Name that does include an Employer ID If the update includes a change to the Employer Name and the current primary employment record has the employee ID populated, the word 'ID' will disp lay in the Notes column on the review form and the Modify action will not be allowed. In this scenario, you must select Insert or Reject. This is required because a modification to the em ployer name on an existing employer record, where the Employer ID is populated, is not allowed. Updated employment record when there is no primary employment record If there is no primary employer record, the Modify option is not allowed since there is no record to Modify. In this scenario, you must select Insert or Reject. ActionDescription /n 147 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector Note: If the fax phone is not tied to an address, the address type and sequence number are blank. You must take one of the following actions if the pulled values are different from the existing Banner values: Business fax phone The following data elements can be pulled from Encompass: ŁBusiness Fax Phone Type (hidden) ŁBusiness Fax Phone Address Type (hidden) (optional) ŁBusiness Fax Phone Address Sequence Number (hidden) (optional) ŁBusiness Fax Country Code (optional) ŁBusiness Fax Area Code (optional) ŁBusiness Fax Number ŁBusiness Fax Extension (optional) ActionResult InsertThis action inserts a new phone record into Banner. The record is flagged as fiprimary.fl If the new phone record is tied to an address, then only one phone record with that phone type, address type, and sequence number can be flagged as fiprimary.fl The fiprimaryfl flag is removed from any existing phone records that have the same phone type, address type, and sequence number as the new record. If the new phone record is not tied to an address, then multiple phone records with that phone type, address type, and sequence number can be flagged as fiprimary.fl If an existing Banner phone record has the same phone type, phone number, address type, and sequence number that were pulled from Encompass, the insert action is not allowed. ModifyThis action updates the existing fipri maryfl phone record in Banner that has the same phone type, address type, and sequence number that were pulled from Encompass. This action overwrites existi ng Banner values, so use it carefully. If there is no existing fiprimaryfl phone re cord in Banner that matches the phone type, address type, and sequence number that were pulled from Encompass, the modify action is not allowed. RejectAll data changes are rejected. Banner is not updated. /n 148 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector The profile that is used to push business fax phone numbers to Encompass affects the business fax phone numbers that are pulled from Encompass. The profile specifies the business fax phone type. For each constituent, the fiprimaryfl fax number that has this phone type is synchronized between Banner and Encompass. The Current Banner Value fields on AUACRVW display information for the fiprimaryfl Banner phone record that matches the phon e type, address type, and sequence number that were pulled from Encompass. If no Banner phone record meets these criteria, the Current Banner Value fields are blank. Note: If the fax phone is not tied to an address, the address type and sequence number are blank. You must take one of the following actions if the pulled values are different from the existing Banner values: Cell phone Once cell phone information is pushed to Encompass via the connector, the data is available to alumni and constituents in Encompass for maintenance purposes. After information is maintained in Encompass, the connector can be used to pull the updated information back to Banner Advancement. ActionResult InsertThis action inserts a new phone record into Banner. The record is flagged as fiprimary.fl If the new phone record is tied to an address, then only one phone record with that phone type, address type, and sequence number can be flagged as fiprimary.fl The fiprimaryfl flag is removed from any existing phone records that have the same phone type, address type, and sequence number as the new record. If the new phone record is not tied to an address, then multiple phone records with that phone type, address type, and sequence number can be flagged as fiprimary.fl If an existing Banner phone record has the same phone type, phone number, address type, and sequence number that were pulled from Encompass, the insert action is not allowed. ModifyThis action updates the existing fipri maryfl phone record in Banner that has the same phone type, address type, and sequence number that were pulled from Encompass. This action overwrites existi ng Banner values, so use it carefully. If there is no existing fiprimaryfl phone re cord in Banner that matches the phone type, address type, and sequence number that were pulled from Encompass, the modify action is not allowed. RejectAll data changes are rejected. Banner is not updated. /n 149 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector The following data elements can be pulled from Encompass: ŁCell Phone Country Code ŁCell Phone Area Code ŁCell Phone NumberThe # sign, which indicates the user must sele ct a desired action fo r the record, displays to the right of the Cell Phone Number field in the Constituents Updates data block. This information appears as the third piece of ce ll phone information in the list within the data block. Failure to select an Action from the Cell Phone Number row will prevent the cell phone number and country and area codes (if present) from loading properly. Pull one-time, perpetual, and scheduled gifts from Encompass to Banner The Encompass connector supports pulling one-time, perpetual, and scheduled gift transactions from Encompass to Banner Advancement. One-time gifts and perpetual gifts are handled by Banner in an almost identical manner. A one-time gift is a single, one-time-only gift made by a donor. The perpetual gift option allows the donor to indicate a gift amount they would like to give at a predetermined frequency with no identified end date. You can identify a different gift type to be assigned to perpetual gifts through the Perpetual Gift Type field on the Advancement Control Form (AGACTRL). Otherwise, the value on the Gift Type field is applied to both one-time gifts and perpetual gifts. A scheduled payment is a pledge made by a donor, with a pledge amount, a particular installment schedule, and corresponding ple dge payments. Both a Banner pledge and a pledge payment can be created when the init ial scheduled payment transaction is pulled over from Encompass. The gift reviewer w ill need to review both the pledge and pledge payment (gift) portions on the enhanced Review External Gifts Form (AGAWGIF). When both are approved and posted through AGAWGIF, all expected updates occur for the creation of a pledge, a pledge installment schedule, and a pledge payment. ActionResult InsertInsert a new ac tive cell phone record with this cell phone type. If there is an existing matching cell phone record, the In active check box is checked, thereby indicating it is inactive ModifyWhen a matching active record for the consti tuent is found, the existing record is updated with the change from Encompa ss. This action is not allowed when no matching active record is found. If you try to select the Modify action, you will notice the system does not retain this action (it is blanked out. RejectAll data changes are rejected. Banner is not updated. /n 150 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector Supported transaction typesBanner Advancement supports pulling the following types of one-time, perpetual, and scheduled gifts: Type Descriptions Authenticated GiftsAuthenticated gifts are gifts made by a donor whose Encompass member record has a valid Banner PIDM value in the field labeled Constituent PIDM, typically found on the Admin Only tab of the member's Encompass profile. The standard mechanism for populating the Encompass Constituent_ID is with the PIDM value, which is provided by the Banner Advancement push to Encompass. Thus, if populated in this manner, it should always be a valid Banner PIDM. Each complete and valid authenticated gi ft is considered a candidate for mass posting via the Gift List tab of the AGAWGIF form. /n 151 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector Unauthenticated Gifts Unauthenticated gifts are gifts made by a donor whose Encompass member record does not have a valid Banner PIDM value in the field labeled Constituent PIDM, typically found on the Admin Only tab of the member™s Encompass profile. This can occur for various reasons including the gift being made by a new donor who doesn™t yet have a record in Banner or when the donor doesn™t sign-on when making the gift and the gift is not associated with a member record having a valid PIDM in the Constituent PIDM field. For unauthenticated gifts, the billing info rmation provided by the donor when making the gift (and listed below) is pulled from Encompass to Banner and can be viewed on the APAWPRS fo rm. For these transactions, the external gift review process needs to include reviewin g the external person data to either tie the incoming donor to an existing Banner ID or create a new Banner ID to which the incoming gift would be tied. The following are the specific biographic-related elements pulled from Encompass and displayed on the APAWPRS form: Person Information tab: ŁLast Name (required in Encompass ŁFirst Name (required in Encompass) Address Information tab: ŁPhone (required in Encompass, shown in Processing Instructions field, user needs to cut & paste into appropriate phone fields) ŁStreet Line 1 (required in Encompass ŁStreet Line 2 ŁCity (required in Encompass) ŁState (required in Encompass) ŁZip (required in Encompass) ŁNation (required in Encompass) If there are multiple unauthenticated Encompass gifts in the temporary gift tables and more than one of these unau thenticated gifts is associated with the same Encompass member ID, when the fi rst of these gifts is reviewed and associated with a Banner ID (regardless of whether this is done through the creation of a new Banner constituent or the association of this gift to an existing Banner constituent), all other unauthenticated gifts for this same Encompass member id in the temporary gift tables will be associat ed with this same Banner ID. The assumption is that if the first gi ft from this member is associated to a particular Banner ID, all other unauthent icated gifts from this same Encompass member ID sitting in the temporary gift tables should be associated with that same Banner ID. This saves the reviewer time in having to associate each of these unauthenticated gifts from this same member to the Banner ID. This will save the reviewer look-up and data entry time since the association will occur automatically. Type Descriptions /n 152 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector Gifts with Multiple Designations Gift transactions entered in Encompass can be allocated to multiple designations. Banner will allow you to retrieve, review and process these transactions, per standard workflow. Gifts with a Single Designation For single-designation gifts, there are two Encompass scenarios supported for Gift Integration: ŁThe designation is set-up as an actual designation in Encompass and is passed in the normal designation node via the iModules web service. ŁThe campaign is set-up so that the user does not have to select a designation, thus saving data entry as t here is only one designation option for this campaign. Therefore, the actual designation value MUST be set-up in a particular manner in Encompass so that the Banner gift integration logic can obtain the designation value. If it is not set-up in exactly this manner, the designation will not successfully be pulled from Encompass. When this campaign is created in Enco mpass, the set-up for this campaign must also include a Commerce Identifier = Banner Designation Code. If this Commerce Identifier is not available as a choice to your institution (using the Advance Mode when setting up the campaign), you must work with iModules to have a Commerce Identifier of ‚Banner Designation Code™ created and available. When available for selection, the ‚Value™ that you should assign for this Commerce Identifier should be the actual Banner designation code. The value of the Banner De signation Code Commerce Identifier will only be interrogated for a designation value if a designation value(s) is not found in the designation node when the iModules web service is called. Gifts without a Designation It is technically possible for gifts to be entered in Encompass without a designation value being entered or defaul ted. These gifts are supported by gift integration. You can set-up a designation default (on AGACTRL) for any Encompass gifts pulled and are missing a designation. If this default is not set, the requirement of a valid designation value will be enforced when the us er is positioned on the Gift Details tab of AGAWGIF when reviewing the pulled gift. Type Descriptions /n 153 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector Unsupported transaction typesBanner Advancement does not support pulling the following types of transactions: Scheduled payments From a Banner perspective, a scheduled paym ent is a pledge made by a donor, with a pledge amount, a particular installment schedule, and corresponding pledge payments. You can create a Banner pledge and a pledge payment when the initial scheduled payment transaction is pulled ov er from Encompass. The gift reviewer will need to review both the pledge and pledge payment (gift) portions on the enhanced Review External Gifts Form (AGAWGIF). When both are approved and posted through AGAWGIF, all expected updates occur for the creation of a pledge, a pledge installment schedule, and a pledge payment. The following sections provide detailed information about the support of scheduled payments. Type Description Skip Billing Transactions Encompass allows an Admin user to enter a gift on behalf of a donor. While this follows the normal donation workflow, the Admin has an additional option to "Skip" the collection of Billing information. This is occasionally done when charging the credit card is not appropriat e, such as registering for an event for which payment was provided separately. When these gift transactions are pulled from Encompass to Banner, these transactions are identified as errors as part of the Gift Processing error handling logic. Any error that meets this condition will not be ac cepted into Banner, thus these types of transactions should not be entered in Encompass. Adjustment Transactions While Encompass does allow the entry of adjustment transactions, Banner is considered the system of record. Therefore, all adjustments should be done directly in Banner, not through the Adjustment function in Encompass. The handling of Encompass Adjustment records is not supported by the Advancement Connector. Unfortunately, there is no me thod available to identify and exclude the pulling of these adjustment transactions in Gift In tegration. Therefore, the only method of controlling this is for institutions to enforce the policy of no entry of Encompass Gift Adjustments. All other Transactions Gift Integration currently only supports one-time, perpetual, or scheduled gift transactions that are successful (com plete) transactions. All other gift transactions are excluded, including the two noted in this table. /n 154 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector Process overviewThis section provides a high-level summary of the steps required to pull over scheduled payment transactions and process them to the permanent Banner tables: 1.A donor enters the Scheduled Payment transaction into Encompass. This can be authenticated or unauthenticated. 2.A gift pull is performed for this campaign so that the gifts are pulled over via the AUAINIT form or through a pull scheduled via AUAINIT. 3.After the manual pull is initiated, view the Run History tab of AUAINIT to ensure that the status of the Request ID indicates succ essful completion. If it was a scheduled pull, the recipients of the e-mail noti fication review the notification. 4.Errors that are encountered display, per existing functionality, in the Response Summary shown on the Run History tab on AUAI NIT. This informati on is also reflected in the e-mail text for anyone who receives e-mail notifications when a scheduled gift pull has been completed. 5.Navigate to AGAWGIF to review and process the pulled gifts (and attached pledges, if applicable).6.If the New Pledge check box is checked on t he Gift List tab for a transaction, the Pledge Details tab will be acti ve. The majority of the fields on this tab are editable. 7.If this is an unauthenticated gift, navigate to the External Person Form (APAWPRS). Complete the normal steps to review the exte rnal person data to associate it with an existing or new Banner ID. You can then "x" out of APAWPRS. 8.Navigate to the Pledge Details tab to review the pledge and ensure the details are correct. When you are satisfied with the pledge information, check the Accepted check box. Any time the Accepted check box is checked or unchecked, the form will complete an automatic save. If any errors are dete cted, an attempt to mark the Accepted check box will fail and error messages will display. Fix the errors and try to check the Accepted check box again. Repeat until you can successful mark the Accepted check box. This indicates that the pledge has been reviewed and accepted. 9.Complete one of the following options: 9.1. To post a single gift, navigate to the Gift Details tab. 9.2. To post a batch, navigate to the Gift List tab and use the Check All function or mark the Load check box to select this and any other desired qualifying gifts. 10. Select the appropriate Create Gifts option to initiate the posting of the selected gifts to Banner. 11. If errors are detected on gifts with attached pledges when the Create Gifts option is checked, the gift transactions should have the Review check box marked, per existing standard functionality. Fix the errors and pos t the gift from the Gift Details form per existing standards. 12. Subsequent pledge payments are pulled over in subsequent pull requests. These transactions do not contain an attached pledge record, so they should be reviewed and posted on AGAWGIF per normal gift handling. /n 155 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector Initial scheduled payment The scheduled payment option provided in Encompass allows the user to specify the total donation (pledged) amount along with informat ion regarding the frequency and duration of the payments. When the scheduled payment option is selected, the first payment is always taken at that time. There is no option to defer the initial pledge payment. All subsequent payments on this pledge are taken automatically, with no data entry required on the donor's part, based on the payment sche dule identified by the donor when the initial scheduled payment transaction is entered. Scheduled payments can be authenticated or unauthenticated. When the donor enters the scheduled payment, Encompass provides the donor the option to change the day of the month on which all subsequent payments are made. There are three options provided in a drop-down labeled 'Make payments based on'. The three options are as follows: ŁCurrent Date (Default) Ł1st Day of Month Ł15th Day of Month. If the donor chooses the 1st or the 15th of the mo nth and their original donation date is not the 1st or the 15th, an additional step is required by the Banner gift processor to help ensure that the Banner pledge installment schedule matches the schedule created in Encompass. For example, a donor makes a donation of $1200 paid monthly over a 12 month period. The original scheduled payment is made by the donor in Encompass on May 13, 2013. ŁScenario 1: The donor leaves the 'Current Date' as the date of t he month on which all subsequent pledge payments should be charged against their credit card. In this case, no manual adjustment to the pledge installment schedule is required in Banner as both the first installment and all subsequent inst allments will be scheduled to occur on the 13th of the month, regardless of frequency. ŁScenario 2: The donor changes the 'Current Date' value to the 1st Day of month or the 15th Day of Month. However, the date the pledge is made is NOT the 1st or 15th of the month. Banner does not support this scenario without the user having to manually adjust the pledge installment schedule in some way. If this scenario occu rs, the Banner user will be made aware of this situation when re viewing the pledge on AGAWGIF through two different methods. The first method to notify the user of a change of payment date is the display of a new field labeled External Next Paymen t Date on the Pledge Details tab of AGAWGIF, in the Installment Information datablock. This view -only field displays the Next Payment Date that is pulled from Encompass. The user can compare the First Bill Date value which indicates the date the initial payment was made, to the External Next Payment Date value. If they occur on a different day of the month, the user should understand that the pledge installment data will require adjustment.In the graphic below, the user has selected the 1st of the month for the subsequent scheduled payments even though the initial payment was taken on May 13th. Therefore, the External Next Payment Date provided by iModules is July 1st. When the payment frequency is monthly, it appears that the iM odules Next Payment Date calculation ensures /n 156 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector that a full month has transpired between the initial and next payment. Therefore, iModules calculates July 1st as the External Next Payment Date instead of June 1st. Additionally, when the user successfully ch ecks the Accepted check box on the Pledge Details tab, a warning will display in a pop- up. The warning message indicates: "Please note that the installment schedule requires manual adjustment based on the External Next Payment Date value. See online help for additional details." The user should then click OK to acknowledge the message. The best practice recommendation is for the reviewer to modify the First Bill Date on the Pledge Details form of AGAWGIF to be in line with the External Next Payment Date value provided by iModules. Given that the above scenario has a frequency of monthly, the reviewer would modify the First Bill Date and change the value from May 13 201 3 to June 1, 2013. Note: This date modification does not im pact the gift date. It indicates the First Bill Date value that should be us ed by the pledge installment logic for the creation of the pledge installments. With this modification, the user has address ed the issue of all subsequent payments being taken on the first day of the month by adjust ing the first payment date to match. When the installment schedule is created, the system will show the first installment as paid, as the initial pledge payment always accompanies a scheduled payment from Encompass. Modifying this First Bill Date has no negative implications and is the easiest method to ensure the pledge installment dates for all remaining scheduled payments have the same dates in Banner as exist in Encompass. /n 157 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector In the figure above, the user would have entered June 1st as the new First Bill Date. As this is a monthly payment, the June 1st date would line up with the next payment date value provided by Encompass, which was July 1st. The actual first pledge payment has already been paid so that amount display in the Amount Paid column for the first installment. The actual Gift Record will corr ectly record the date of the gi ft and is not impacted by this change to the First Bill Date va lue on AGAWGIF. If the user forgets to make this change on AGAWGIF, they can make the change on th e AGAPINS form after the pledge is posted either by removing and creating the installment schedule again with a new value in the First Billing Date, or modifying each of the Date Due values as desired on the Schedule tab. The frequency selected by th e donor and the Next Payment Date value will help the user determine the appropriate date to enter into the First Bill Date. The user should always verify any schedule adjustments on AGAPINS after posting the transaction. If further modifications are required to the Date Due values for the remaining installments, those can be made on the AGAPINS form. Pledge installments out of balance The pledge installment schedule that is created when you post a pledge from AGAWGIF pledge installment schedule may run into rounding issues that result in Expected Amounts on the installment schedule and installment detail records that do not match. If this were to occur, a warning message would display on AGAWGIF when you attempt to post the gift and pledge. The message is as follows: All installment schedule amounts could not be evenly distributed to the associated installment detail record s for ID XXXXXXXXX, Pledge 9999999. Please adjust Expected Amounts on Installment Detail records accordingly. The logic used to post gifts/pledges and create the installment schedule handles one pledge/gift record at a time, even if the user performs batch-level post ing of multiple gifts/ pledges on AGAWGIF. As a part of all of th e existing messaging that occurs when gifts and pledges are posted, this new warning would also display for each pledge that is posted where the out-of-balance condition has resulted from the pledge installment creation process. If a batch of multiple pledg es were posted on AGAWGIF and there were two out of six pledges with out-of-balance installment schedules, the user would see two separate pop-up messages on AGAWGIF with the above warning message. This would /n 158 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector provide the user with the appropriate informati on to navigate to AGAPINS and review the installment schedule for the identified Banner ID and Pledge number. Subsequent pledge payments For scheduled payment transactions, institut ions must always pull over the initial scheduled payment transaction prior to pulling over any subsequent payments. This is required to ensure that the duration of th e pledge payment schedule can be calculated correctly. One of the data elements provided to Banner through the iModules Web services is a count of the remaining payments for a scheduled payment transaction. This value changes as subsequent payments are taken. If the initial scheduled payment was set-up for 11 remaining payments after the initial payment, 11 would be provided to Banner in the Web services. If the initial scheduled paym ent was not included in a pull prior to the institution pulling over the next payment, and th ey all ended up in the same pull, iModules would have decreased the amount of remaining payments from 11 to 10. This would be an incorrect value for the Duration calculation performed by Banner. Warning! The initial scheduled payment transaction must ALWAYS be included in a pull completed prior to pulling any of the subsequent payment transactions over to Banner. When a pledge is pulled over from Encompas s, the Web service response provides the external pledge number, which is Encompass's unique pledge #. When a pledge is processed and posted through AGAWGIF, this Encompass pledge value is stored in the AGBPLDG_EXT_PLEDGE_ID field on the pledge. This value can be viewed at the bottom of the AGAWPLG form. When subsequent pledge payments are pulled in a gift pull, the external pledge number is provided for these transactions. The Banner logic uses the external pledge ID to look for an existing pledge record wit h this eternal pledge # on the AGBEPLG (temporary pledge) or AGBPLDG (permanent pledge) tables. If one is found for the identified Banner ID, the system automatically associates the subsequent pledge payment to the correct Banner ID and Pledge number. This is true whether the incoming subsequent payment is authenticated or unauthenticated. Gift setup in Banner This section describes the set-up steps necessary for pulling gifts from Encompass to Banner Advancement. As part of this process, the following forms in Banner need to be examined: ŁAGACTRLŁAUACMAP ŁAUACDEF /n 159 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector Note: The 'Allow Web Pledges' and 'Allow Web Gifts' check boxes on the Base Information tab on the AFACAMP Form (Campaign Detail), are not used, as it's assumed each instit ution will only set up campaigns in Encompass for which it makes sense to allow the donor to make online gifts. AGACTRL Each gift transaction in Banner must contain a valid gift type code. As the entry of this value is not supported in Encompass, a Gift Type default must be set-up in Banner for Encompass gift transactions to successfully be pulled over to Banner. There are additional default fields that potentially require populat ion by your institution to enable the Gift Integration to successfully func tion. All of these default val ues are now available for entry on the Connector Defaults sub-tab on the Institution tab of the AGACTRL form. These defaults only need to be populated by institutions using the Encompass Gift Integration. AUACMAPThe following components on the Advancement Connector Data Mapping Form (AUACMAP) allow you to se t up gift integration: ŁValid Profile Categories Data block ŁData Mappings to support Gift Integration ŁGift Integration Review Category ŁGift Integration Profile Category Valid Profile Categories Data block The AUACMAP form contains a data block ca lled Valid Profile Categories, which allows you to associate each data element in the Data Elements data block to the appropriate Profile Categories. As you navigate between Data Elements, the values in the Profile Categories data block change in order to reflect the associations to the Data Element in context. Note: Prior to Banner Advancement 8.5, duplicate Data Elements with the same Connector Name were not allo wed. With the introduction of the Profile Categories data block in 8.5 and the ability to indicate the profile category to which the Data Element applies, duplicate Connector Name values are allowed, as long as they have different Profile Categories. For example, you can have two Data Elements named SPRIDEN_FIRST_NAME, one with a Prof ile Category of Biographic that maps to the SPRIDEN table for Biogra phic updates and one with a Profile Category of Gift that maps to t he APBWIDN table for Gift Pulls. You may not have two Data Elements that have the same Profile Category. /n 160 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector Add, Modify and Delete RulesThe following rules apply to the new Profile Categories data block Additional business logic checksThe following information is meant to assist in the additi on or modification to existing records. ŁEach Profile Category record must have, at the minimum, the Push Allowed or Pull Allowed check box checked. You will receive an error and will not be able to save any profile records if this condition is not met. ŁIf the Data Element in the top data block has the Active indicator un-checked, a new Profile Category record cannot be associated with that data element. If this is attempted and you try to save this re cord, you will receive an error. This is because that data element is not considered active so it shoul d not allow or require any new associations to Profile Categories. ŁIf a Data Element is active, it can be assigne d a new Profile Category (via an Add in the Valid Profile Categories data block). However, this Profile Catego ry record is only allowed to have the Push or Pull check box checked if the corresponding check box is checked for the Data Element in the top data block. If you attempt to check one of these Push or Pull check boxes for a Profile Category Record when the associated data element does not have the same check box checked, an error will appear and indicate 'Push or Pull can only be allowed if it is allowed for the associated Data Element'. ŁIf your institution inactivates a data element in the top data block of AUACMAP, please be aware that this does not have an impact on any existing profiles that already contain this data element. It only prevents that 'inact ive' data element from being assigned to a ActionRuleAddYou can add a new Profile Category record at your discretion. However, it must have a unique Profile Category value; duplicates category values are not allowed. If the baseline indicator is not checked on the Valid Profile Category record for a data element, this is not an integration type that is supported by the Banner Advancement Connector. Therefore, any desire you have to extend the Advancement Connector to support this data element for the indicated Profile Category type would be a customization you own and maintain. Modify You can modify a record. However, the record after the changes must not violate any cons traints, such as creating a duplicate profile category value, and must be a valid value. Delete Baseline records can not be deleted. If desired, you can inactivate a Profile Category by unchecking the Active check box." Non-baseline records can be deleted. However, performing this action will not im pact any existing profiles of this Profile Category that contain this data element. /n 161 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector profile moving forward. You can, at your discretion, manually delete the data element from any existing profiles if the data elem ent is considered no longer valid from an institutional perspective. Seed Data Seed data is provided for each data element in the base product. ŁFor each data element supported for the existing BIOGRAPHIC integration, a BIOGRAPHIC Profile Category record is automatically inst alled when you install Banner Advancement, and these records will ha ve the Baseline check box checked. ŁFor each data element supported for the new GIFT integration, a GIFT Profile Category record is automatically installed when you install Banner Advancement, and these records will have the Baseline, Active and Pull Allowed check boxes checked. ŁIf your institution had defined any non-baseline data elements prior to your update to this release, the upgrade routine will automatically assign a BIOGRAPHIC Profile Category record to that data element. Data mappings for gift integration The master list of Data Elements includes Gi ft-Related data elements that are supported for Gift Integration. These Data Elements are all included as seed data and installed for you during the Banner Advancement installation process. By default, all Data Elements listed below will have the Active, Baseline and Pull Allowed check boxes checked, and the Pu sh Allowed chec k box unchecked. Connector Name Friendly NameReview CategoryBanner Table NameBanner Column Name (for temporary gift tables) spriden_first_nameFirst Name GIFTAPBWIDNAPBWIDN_FIRST_NAME spriden_last_nameLast NameGI FTAPBWIDNAPBWIDN_LAST_NAME goremal_email_address _pref EmailGIFTAPBWIDNAPBWIDN_EMAIL_ADDR ESSClass Code 1 - CUSTOMIZATION REQUIRED Code 1GIFTAGBGHLDAGBGHLD_GCLS_CODE Class Code 2- CUSTOMIZATION REQUIRED Code 2GIFTAGBGHLDAGBGHLD_GCLS_CODE _2Class Code 3- CUSTOMIZATION REQUIRED Code 3GIFTAGBGHLDAGBGHLD_GCLS_CODE _3/n 162 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector Gift integration review category A Review Category is available on the Advancement Connector Review Category Validation Form (ATVRCAT). This seed data record contains a Code = GIFT and a Description = Gift Integration. When you access the AUACMAP form, this value appears in the Review Category field when you select a Data Element to which the ca tegory applies. Gift Integration Profile Category A Profile Category is available on the Adva ncement Connector Profile Category Validation Form (ATVPFTP). This seed data record contains a Profile Category = GIFT and a Description = Gift Integration. When you access the AUACMAP form, this value appears in the Category field in the Valid Profile Categories datablock when you select a Data Element to which the category applies. AUACDEFThe following components of the Advanc ement Connector Profile Form (AUACDEF) support gift integration: ŁProfile Categories Code Field ŁCampaign Code and Control ID Fields ŁGift Integration Pull Profile Profile Categories CodeThe AUACDEF form includes a Category Code field, which allows you to associate a connector profile with a Category Code (GIF T, BIOGRAPHIC). This field is required. Values in this drop-down are validated against the Connector Profile Category Validation Form (ATVPFTP). Comment- CUSTOMIZATION REQUIRED CommentGIFTAGBGHLDAGBGHLD_COMMENT Processing Instructions- CUSTOMIZATION REQUIRED Processing InstructionsGIFTAGBGHLDAGBGHLD_PROC_INST RMatching Gift Company- CUSTOMIZATION REQUIRED Matching Gift Company GIFTAGBGHLDAGBGHLD_PROC_INST RConnector Name Friendly NameReview CategoryBanner Table NameBanner Column Name (for temporary gift tables) /n 163 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector When you indicate you want to copy an exis ting profile via the Copy Profile Code drop- down, the list of profile s from which you can copy will be lim ited to those that have both a matching Transaction Type (pull/push) and a matching Category Code (bio, gift). Only those profiles with matching values for both fields are displayed as options in the Copy Profile Code drop-down. Campaign Code and Control ID Fi elds for Gift Category CodeThe AUACDEF form includes two fields that are required if the Category Code is GIFT. They are Campaign Code (Banner Code) and Control ID. These fields are maintainable on a Gift Integr ation Profile. This allows you to modify the Control ID or Campaign of an existing prof ile, if necessary. Other key fields cannot be modified. If other values are incorrect, dele te the profile and add it with the appropriate values. This form does support the establishing of multiple campaigns in Encompass and mapping them to the same Banner Advancement campaign. The set-up for this would include multiple Campaign (g ift) Profiles in Banner Advancement, which have the same Campaign value and different Control ID values. Gift Integration Pull Profile Gift Integration requires a Pull Profile. Ther efore a BANNER GIFT PULL profile is provided as seed data. However, it is important to not e that the profile needed to support the Gift Pulls has a few key differences from the Biographic profiles and cannot be used successfully without some modification. The first difference is that there are addit ional data elements in the keyblock on the Advancement Connector Profile form (AUACDEF) t hat are required for Gift profiles. This is spoken to in the section above. The second difference is the functional purp ose of the BANNER GIFT PULL profile. Since a Gift transaction has a more rigid set of fields returned from Encompass, the BANNER GIFT PULL profile only needs to include fields that are not included in the standard Gift Transaction. Key block data values The following key block values are associated with the new BANNER GIFT PULL profile: ŁProfile Code = BANNER GIFT PULL ŁProfile Description = Baseline Gift Pull Profile ŁCategory Code = GIFT ŁTransaction Type = PULL ŁCampaign = Update Me ŁControl ID = 99999 Warning! The default Campaign code, UPDATE ME, must be configured to represent a Campaign code unique to your institution. Failure to do so /n 164 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector will result in an error on AUAINIT that indicates th e value must be updated here on AUACDEF. To change this value, make a copy of the BANNER GIFT PULL profile and then modify the UPDATE ME value while current on the copied BANNER GIFT PULL profile. Copying the profile before modifying it preserves the original BANNER GIFT PULL seed data and allows you to refer back to it, if necessary. Data block values The fields that are required for a valid Gift Pull profile, and are included in the BANNER GIFT PULL PROFILE include: Optional Data block values Optionally, Gift Integration will support the pulling of six addit ional ‚instance™ fields for a campaign. These are optional fields and are not required to be used by institutions. In fact, these mappings are invalid and will not work as delivered. This is because the value entered in the ‚Connector Name ™ column does not map to an actual instance field in Encompass as instance field names (Connector Name) are unique to each institution and to each of their campaigns. These seed dat a values are provided as placeholders to remind institutions that these particular instance fields are supported for the BANNER GIFT PULL profile if desired. When configuring a Gift Pull Profile for use at your institution, copy the provided BANNER GIFT PULL profile and name it something more meaningful to your institution. You should then delete these pre-delivered six instance fields and add any unique instance names that you have set-up and are associating with this campaign/Gift Pull profile. NameConnector Name Display Order First NameSPRIDEN_FIRST_NAME1Last NameSPRIDEN_LAST_NAME 2Email AddressGOREMAL_EMAIL_ADDRESS_PREF3 NameConnector Name Display Order Matching Gift Company MATCHING GIFT COMPANY - CUSTOMIZATION REQUIRED 4Class 1, Class 2, Class 3CLASS CODE 1 - CUSTOMIZATION REQUIRED CLASS CODE 2 - CUSTOMIZATION REQUIRED CLASS CODE 3 - CUSTOMIZATION REQUIRED 567CommentCOMMENT - CUSTOMIZATION REQUIRED 8/n 165 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector The following provides additional information regarding the optional instance fields: Processing Instructions PROCESSING INSTRUCTIONS - CUSTOMIZATION REQUIRED 9NameEncompass SourceBanner Target Matching Gift Company Encompass provides a field called Matching Gift Company. This field allows the donor to provide the name of a company that will match the gift. If a donor provides this information, the pull process will include this information in the Processing Instructions field along with a label that indicates it is the Matching Gift Company Name.As with other gifts that include Processing Information, the Ma tching Gift Company information will display on the Gift Details tab of AGAWGIF so that the reviewer can see this additional information and use it to accurately update and post the gift. Class Code 1Configured as an instance field with a drop-down list on the appropriate Campaign(s) in Encompass. The valid codes should correspond to the valid Class Codes identified in Banner. Gift Integration supports the same fields that are available for In-Honor and In-Memory, which are supported by Banner Advancement and Banner Advancement Self-Service. These include Class 1, Class 2 and Class 3. Class Code 2Configured as an instance field with a drop-down list on the appropriate Campaign(s) in Encompass. The valid codes should correspond to the valid Class Codes identified in Banner. See above comments. NameConnector Name Display Order /n 166 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector Class Code 3Configured as an instance field with a drop-down list on the appropriate Campaign(s) in Encompass. The valid codes should correspond to the valid Class Codes identified in Banner. See above comments. CommentConfigured as an instance field (text) on the appropriate Campaign(s) in Encompass. This is a general Comment field that is mapped to the Comment field on the AGAWGIF form. This is similar to the general comment field provided in Banner Advancement Self-Service. Depending on the method you use to add this instance field to your Encompass environment, the value inserted in this field might exceed 300 characters in length. However, when this val ue is pulled to Banner, the maximum limit is 300 characters. Thus, any Comment value that exceeds 300 characters will be truncated when the value is inserted into Banner for viewing on the Gift Details tab of AGAWGIF or on the standard forms used to view post ed gifts. No error or warning will be displayed in Banner indicating the value was truncated. If Comments are truncated as part of this process, and you wish to determine what info rmation was truncated, the balance of the information can be ascertained via Campaign Reporting in Encompass. NameEncompass SourceBanner Target /n 167 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector Payment frequency In Encompass (the iModules system), the standard frequency values available for use by institutions are listed below. The values on th e left are the values shown in the Frequency drop-down in the Encompass user interface. The values on the right are the Frequency values that are provided in the iModules Web se rvices to indicate the frequency selected by the donor. You can choose not to display all of the options to your donors. However, you cannot add additional frequency options. Processing Instructions Configured as an instance field (text) on the appropriate Campaign(s) in Encompass. This field is designed to allow the donor to provide guidance regarding the intended use of their donation or additional processing instructions. This may be, for example, instructions indication the gift is an In-Honor or In-Memory gift. This field is available on the Details Tab of the Banner external gift review form (AGAWGIF) to help the gift reviewer ensure the gift is posted appropriately. The Processing Instructions information is stored in a temporary table, not in a permanent Banner table. These are simply temporary instructions that aim to help ensure the gift itself is processed correctly in Banner. If a gift pulled from Encompass has a value in the Processing Instructions field, the gift will automatically have the Review check box checked, indicating it requires review. This will prevent the gift from being mass posted. When this occurs, the gift will need to be posted from the Gift Details Tab on the AGAWGIF form. This method ensures the gift entry operator has viewed the Donor Instructions text prior to processing the gift. Depending on the method you use to add this instance field to your Encompass environment, the value inserted in this field might exceed 2000 characters in length. However, when this val ue is pulled to Banner, the maximum limit is 2000 characters. Thus, any Processing Instructions value that exceeds 2000 characters will be truncated when the value is inse rted into Banner for viewing on the Gift Details tab of AGAWGIF or on the standard forms used to view posted gifts. No error or warn ing will be displayed in Banner indicating the value was truncated. If Processing Instructions are truncated as part of this process, and you wish to determine what information was truncated, the balance of the information can be ascertained via Campaign Reporting in Encompass. NameEncompass SourceBanner Target /n 168 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector In Banner, there is a frequency validation tabl e that is maintained on the Frequency Code Validation List (ATVFREQ). Banner has no co ntrol over the values that users populate within the ATVFREQ table. Therefore, your inst itution must set up translation rules for the incoming iModules Frequency codes (1, 2, 4 and 12) to indicate the values from the Banner Frequency Code Validation table that correspond to the four iModules frequency codes. The your institution sets up translatio n rules using the PAYMENT_FREQUENCY Field Name on the Data Translation Field Value Ru les Form (APATRAN). You must populate the appropriate values on APATRAN to create the necessary mapping so that the incoming iModules frequency codes can be converted to the correct Banner frequency code. An example of these new values is shown in the figure below. As there are other Advancement Connector fields that use APATRAN translation, there is an existing Translation Data Source parameter on the Connector Defaults tab on AGACTRL. This value will also be used to identify the Data Source for frequency translation for the Advancement connector gift integration. When you use the APATRAN translation functi on and the values entered below on this form, the incoming iMod ules frequency code of 1 should be converted to YR for Banner purposes. An incoming frequency code of 12 should be converted to MO for Banner purposes and so forth. If the Advancement Connector logic is unable to successfully translate the incoming Frequency value to a valid Bann er Frequency value, an error will be reported when the gift pull is performed and the erring gift(s) will not be loaded into Banner. The error message will read as follows: Missing Pledge Frequency Code - Translation not found on APATRAN . Frequency Description in Encompass Frequency Code passed by the iModules Web service Monthly 12 Quarterly 4Twice a year 2Yearly 1/n 169 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector Pledge durationThe concept of pledge duration is handled differently in iModules than in Banner. Advancement Connector logic has been added to calculate the duration so that it can be written to the Duration field on t he Pledge Details tab of AGAWGIF. For example, a donor has entered a $6,000 pledge that is to be paid quarterly with a total of 24 payments, the first payment included with the initial transaction along with 23 remaining payments. When this donation is made in Encompass as a scheduled payment, Encompass indicates that the remaining payments will be placed between July 18, 2013 - Jan 18, 2019. This is provided in small text below the frequency information. Because the scheduled payment transaction is entered on April 18, this date will be used in Banner for the creation of the pledge as well as the initial pledge payment. In this example, the connector completes the following logic to calculate the pledge duration: ŁNumber of months between payments The logic first calculates the number of mont hs between payments. It uses the current payment date, April 18, and date of the next payment. The latte r is the first date of the payment range which is July 18, 2013. Using date math, it is determined there are 3 months between each payment. ŁTotal months of pledge duration The logic then multiples this fiNumber of months between paymentsfl (number of remaining payments + 1) The result is as follows: 3 months between payments * (23+1 payments) = 72-month pledge duration The value of the pledge duration in months (72 in the above example) is then used to perform a look-up in the Banner Duration Code Validation table viewed on the ATVPDUR form. The table uses this amount to look for a record with a matching value within the Months column, as shown in the figure below. In this case, as there is no matching record with a Months value of 72, this gift would be identified as being in error and the gift would not be loaded into the temporary gift tables for review. The response summary information on the Run History tab of the AUAINIT form would indicate the error and provide the following error description: Missing Pledge Duration Code - Number of months not found on ATVPDUR To address this error, the appropriate Banner user would need to insert a record on the ATVPDUR form that had the matching months va lue. The user could then run another pull with selection criterion that woul d include this gift. This pull should result in the gift being successfully pulled, unless there are other errors associated with the gift. /n 170 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector Adjustments required for scheduled payments entered before 8.6.1 If your institution allowed donors to make scheduled payments in Encompass prior to your upgrade, the 8.6.1 release prov ides a method to link the unique Encompass pledge ID to the corresponding Banner Pledge. Any subsequent pledge payments pulled from iModules are automatically associated with the correct Banner ID and pledge #. Banner pledge and the external pledge ID # assigned to that same pledge by iModules. When an adjustment is made to a pledge on the AGAADJS form, a new External Pledge field displays on the bottom of the Pledge Adju stment form. In this field, enter the unique pledge id assigned to the scheduled payment transaction by iModules. You should make these adjustments as part of the set-up prior to your institution's go-live for this upgrade. When this adjustment is made and saved, this Banner pledge is now associated to the corresponding Encompass pledge. Therefore, when a pledge payment (gift) is pulled over from Encompass, Banner logic searches through the various Banner pledges in both the permanent pledge table (AGBPLDG_EXT_PLE DGE_ID) and the temporary pledge table (AGBEPLG_EXT_PLEDGE_ID), looking for one that contains the valu e that matches the external pledge id provided by iModules. When found, the Banner logic automatically associates this incoming pledge payment to the Banner ID and pledge number. This pledge payment displays as an authentica ted gift (pledge payment) on AGAWGIF. Warning! It is critical that the institution assign the correct external pledge ID to the correct Banner ID and Banner pledge. If this association is not set up correctly when performing the above adjustments, then subsequent pledge payments pulled from Encompass will be associated, automatically, with the incorrect Banner ID and Pledge. Setting up Designations in Encompass When defining a Designation in Encompass, t he Designation IDs func tionality is used to tie an Encompass Designation to a Banner Designation code. To facilitate this, there must be a value of ‚Banner Designation Code™ that can be selected from the Designation IDs drop-down option. For any designa tions that can potentially be on a one-time or perpetual gift that is pulled over to Banner, institutio nal personnel must then select that ‚Banner Designation Code™ drop-down for the Designation IDs field, enter the actual Banner designation code as the Value for that Designation ID and Save. If this is not done or there is a type-o in either the Designation ID or the Value, gift integration will not be able to successful id entify the appropriate designation code. Instead, an error will display when this gift is reviewed on the AGAWGIF form and the user will be required to enter the appropriate valid Banner designation code. /n 171 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector Setting up instance fields In Encompass If you want to include any of the six supported instance fields for any of your campaigns, certain set-up steps are required. The following describes these steps. 1.Identification of instance fields in Encompass for appropriate campaigns. When adding a new field to a campaign form in Encompass, the check box labeled ‚Make this an instance field™ must be checke d. If this is not checked, then the gift integration for this field will not function properly and is not supporte d. The value that is entered in the ‚E xport Column Header™ field in Encompass will also be the unique Connector Name that you will be using in St ep 2.1 below. Please make note of this value. Please work with iM odules directly if you re quire any assistance in understanding how to setup an instance field on a campaign. For example: For your Annual Fund campaign, you would like to include the Processing Instructions field. Therefore, you add it as an instance field for that campaign with an ‚Export Column Header™ name of ‚2012 Annual Fund:Processing Instructions™. 2.Identification of these instance fields on the AUACMAP form. Since instance names in Encompass are unique by institution and by campaign, your institution must identify th is unique name to Banner so it will understand the appropriate column to interrogate when trying to pull over this value for a particular Gift Pull Profile (and campaign). The following two steps are required: 2.1. Insert a new Data Elements record in the top data block on the AUACMAP form. Since your institution has a new ‚instance™ field that isn™t yet known to Banner, the first step is to identify this data el ement to the master list of data elements supported for the Advancement Connector. This is done on the AUACMAP form using the Record Insert action. To make this easier, the BANNER GIFT PULL profile has a seed data record for each of the six instance fields supported for Gift Integration. All of these can easily be found by filtering the view on AUACMAP to include only those that have a Connector Name containing the word ‚Customization.™ If you view these existing seed data records, it provides the majority of the values you would need for your ‚instance™ record. The only piece of information that will vary by institution is the Connect or Name value. This should be equal to the value you have for this instance fi eld in Encompass in the ‚Export Column Header™ attribute. For example: To identify the Processing Instructions instance field that I added to my Annual Fund campaign in Encompass, I would insert a new record that had the same data as the seed data record with the Connector Name ‚PROCESSING INSTRUCTIONS - CUSTOMIZATION REQUIRED™. Instead of the above connector name, for my new record, the value would instead be ‚2012 Annual Fund: Processing Instructions™ which is the exact value from the ‚Export Column Header™ attribute of the Encompass instance field. Both the Processing Instructions and the Matching Gift Data are mapped to the AGBGHLD_PROC_INSTR table and column . Therefore, a label will display in front of each value so the user can easily understand the data they are viewing in that one field. The label that will be displayed in the Processing Instructions field on AGAWGIF (Gift Details tab) is de fined by the value in the Friendly Name /n 172 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector field on AUACMAP for thes e two records. Institutio ns have the option of modifying the text in the Friendly Name field for these records to customize those labels if desired. The order in which these two fields display in the Processing Instructions field (assuming both values are being populated and pulled over with Gifts) is dictated by the Display Order value for the data element on AUACMAP and can be modified by the institution of a different order is desired. 2.2. Associate this new data element to the Gift Category on the bottom data block entitled ‚Valid Profile Categories™. Once you have added the mapping for this instance field for this particular campaign, you then need to assign it the Gift Category in the Valid Profile Categories data block at the bottom of this form. It should be marked as active and have the ‚Pull Allowed™ check box checked. This now makes this data element available to be added to any Gift Pull profile. 3.Add this data element to the appropriate Gift Pull Profile on the AUACDEF form. You can add this campaign-specific instance field to the appropriate Gift Profile being used for that campaign. Given that the ‚Export Column Header™ value is required by Encompass to be unique across all campaigns, you will need to do the above steps for every one of these supported instance fields you choose to include on every campaign. So, as an example, if you only wanted to add the Processing Instructi ons form to your campaigns and pull that one ‚instance™ field over to Banner but you had six campaigns, you™d need to add six unique data element records to AUACMAP and then add them to the appropriate six Gift Pull Profiles per the instructions above. Gift pull initiation This section describes initiating the pu lling of gifts from Encompass to Banner Advancement after the initial se tup is performed. As part of this process, the AUAINIT form (Initiation tab, Scheduler tab and Run History tab) in Banner needs to be examined. AUAINIT Œ Initiation tab Since there are two kinds of integration (Bio graphic and Gift), a Category Code field is available on the initiation tab on the Advancement Connector Initiation Form (AUAINIT). When you select a Category from this drop-down, values in the Profile Code list below will be filtered and will only display profiles associated with the sele cted category in this field. ŁIf Initiation Selection = Push, and Category Code = Biographic, only the Biographic push profiles display. ŁIf Initiation Selection = Push and Category Code = Gift, no profiles display as none are supported at this time. However, if your institution has customized the Advancement Connector and has, for some reason created Gift Push profile(s), they would display. ŁIf Initiation Selection = Pull and Category Code = Biographic, only the Biographic Pull profiles display. ŁIf Initiation Selection = Pull and Category Code = Gift, only the Gift Pull profiles display. /n 173 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector AUAINIT Œ Scheduler tab Since there are two kinds of integration (Bio graphic and Gift), a Category Code field is available on the Scheduler tab on the Advancem ent Connector Initiati on Form (AUAINIT). When you select a Category from this drop-down, values in the Profile Code list below will be filtered and will only display profiles associated with the sele cted category in this field. ŁIf Initiation Selection = Push, and Category Code = Biographic, only the Biographic push profiles display. ŁIf Initiation Selection = Push and Category Code = Gift, no profiles display as none are supported at this time. However, if your institution has customized the Advancement Connector and has, for some reason created Gift Push profile(s), they would display. ŁIf Initiation Selection = Pull and Category Code = Biographic, only the Biographic Pull profiles display. ŁIf Initiation Selection = Pull and Category Code = Gift, only the Gift Pull profiles display. AUAINIT Œ Run History tab Since there are two kinds of integration (Bio graphic and Gift), the Run History tab on the Advancement Connector Initiation Form (AUAIN IT) includes the followin g items in order to support gift integration. Profile CategoryA new Category Code field was added to help th e user understand the type of profile that was run (Gift, Biographic). CountThe Count in both the Initiation Requests and the Associated Batches data blocks represents the number of gifts pulled back as part of that Request ID. This would include all gift transactions returned by Encompass for that Gift pull request, regardless of whether the Banner gift integration logic subsequently i dentified error conditions and reports any of these gifts as errors. Status values for Gift Pulls When a gift pull is requested and the pull is executed successfully, the status on the Run History form will be one of the following:ŁCompleted : All gift records included in the pu ll were successfully loaded into the external gift tables (APBW IDN, AGBGHLD and AGRGHDE). ŁCompleted with Errors : There was at least one gift record that could not be loaded because it did not pass the validation logic. This may be due to an error identified by Encompass or the Banner pull logic. See the section below entitled ‚Gift error display™ for additional information. ŁInitiated : The pull request is in process. /n 174 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector ŁNo Changes: There were no new gifts that qualified for inclusion in the pull. ŁFailed : There was a larger system or service failure that caused the entire pull request to fail. As a result, no gift records were pulled over. In most cases the status will be Completed or Completed with Errors .Note: You might momentarily notice a gift pull contains a status of 'Review'. If this occurs, this temporary status can be ignored as it simply indicates the request is being processed. Warning! Since the review of pulled gifts does not occur on the Connector review form, the updating of the status from Review to Completed does not apply. Once the pull is completed successfully, you must use the Review External Gift s Form (AGAWGIF) to review these pulled gifts. Gift error display When a pull results in a stat us of Complete with Errors, additional information can be viewed in order to understand the gifts that were identified as having errors. This error information can be viewed by selecting t he Response Summary icon on the Run History tab in the Associated Batches data block where the batch level information is displayed. When the Response Summary is displayed, you will see four counts at the top, followed by any error information. The four counts at the top include the number of Total Constituents, Total Pledges, Authenti cated Gifts and Unauthenticated Gifts. Email notification for successful gift pulls When a scheduled gift inte gration pull is successful, an email will be sent to the designated recipient. As wit h the Bio push/pull process, the message will contain a standard set of information (Request ID, Type, Date Run, Status, Profile Code and Frequency). Additionally, the message will incl ude the following gift-s pecific information.Email notification for Gift Pulls with a Complete with Error Status When a pull results in a status of Complete with Errors, additio nal information will be included in the email notificati on. This information is meant to assist in identifying which gifts had errors and were not pulled over to Banner. The additional information that displays in th e email includes a count of gift transaction errors along with the same information that displays on the Response Summary, as described earlier. /n 175 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector Error Identification Logic When pulling gifts from Encompass, Banner Advancement performs certain checks prior to loading the gift transactions for review. If certain error conditions exist, the gift transactions are not loaded into the gift temporary tables (APBWIDN, AGBGHLD and AGRGHDE). Instead, the transactions appear on the gift error display. If a transaction has more than o ne error, each individual error will be a part of the error count shown on the Response Summary on the Run History tab and the error information for each particular error will be re ported separately. For example, if the gift pull contained 1 gift that was authenticated and the gift cont ained 3 errors, the Total Number of Errors would be 3 and all errors will have the same gift number. The following errors were added in order to support gift transactions: Error MessageDescription ID does not exist in Banner or Name information is missingThe gift transaction has neither a valid PIDM nor a Last Name value. To be loaded into the temporary gift tables, either: ŁA valid PIDM must exist, which indicates an authenticated gift. ORŁLast Name must be populated to provide enough information for an unauthenticated gift. Gift has already been processed The gift transaction has already been posted to Banner. As part of this process, the following fields are examined to determine if the gift has been posted from this source, for this Banner ID. These fields are checked for both gifts posted into Banner as well as the other gifts currently in the temporary gift tables: ŁExternal Gift Number ŁBanner ID ŁData Origin ŁGift Date Missing Total Gift Amount The gift transaction is missing a value for the total gift amount. Missing Detail Amount The gift is missing an amount value for a designation. Missing Gift Type CodeŒ Please set- up default on AGACTRLThe gift type code is missing. For gifts from Encompass, this is a reminder to the institution to fill in the Gift Type code on AGACTRL. If this error is enc ountered, the appropriate Gift Type Code should be entered on AGACTRL. Once the value is specified and the us er tries the Gift pull again, this error will no longer appear. /n 176 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector Invalid Gift Type Code Œ Please check default value on AGACTRLThis error would only occur if the default gift type value set- up on AGACTRL has become invalid for some reason. Skip Billing Transactions Not Supported The transaction does not incl ude Billing Information and represents a ‚Skip B illing™ transaction entered by an Admin in Encompass, which is not supported. Invalid Gift Class Code 1Indicates that the value pulled from Encompass for the Gift Class Code 1 does not have a corresponding valid value in Banner. To resolve this issue, re view the valid values for this field in both Encompass and Banner to make sure they are in sync. Once the issue is resolve, pull this gift again and the error should not appear. Invalid Gift Class Code 2Same description as Invalid Gift Class Code 1, but for Class Code 2.Invalid Gift Class Code 3Same description as Invalid Gift Class Code 1, but for Class Code 3.State Code does not exist Indicates the value pulled from Encompass for the State Code for an unauthenticated gift does not have a corresponding valid value in Ba nner. To resolve this issue, review the valid valu es for this field in both Encompass and Banner to make sure they ar e in-synch. Once the issue is resolved, pull this gift again and the error should not appear. Nation Code does not exist Indicates the value pulled from Encompass for the Nation Code for an unauthenticated gift does not have a corresponding valid value in Ba nner. To resolve this issue, review the valid valu es for this field in both Encompass and Banner to make sure they were in-synch. Once the issue is resolved, pull this gift again and the error should not appear. Pledge has already been processed Indicates the gift pull included initial scheduled payment transactions that you hav e already pulled, whether authenticated or u nauthenticated. This will typically occur when you are running a scheduled or manual pull that is for a timeline - or includes a time line - that was included in a previous pull.Missing Pledge Frequency Code - Translation not found on APATRAN Indicates the Advancement Connector logic was unable to successfully translate the incoming Frequency value to a valid Banner Frequency value. See Payment frequency for details on how to resolve this issue.Error MessageDescription /n 177 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector Merge Gift Pull Time line Considerations The iModules gift-related web services are structured so they only provide gifts to Banner after any necessary review has been performed on a gift transaction (primarily for member-merge types of functionality). iModules has worked out a method to ensure this is transparent to those using the gift-related we b services so the user does not have to do any special processing other than performing th eir normal hourly, daily or weekly gift pulls. However, please be aware that this potentially will result in a delay before certain gifts may be available to be pulled over to Banner. Pl ease be sure your institution works with iModules personnel to understand any impact this may have on the delay of gifts being available for the Banner Advancem ent Connector Gift Integration. Gift Review functionality As with other external gifts that are loaded into Banner Advancement, the Gifts pulled from Encompass will be reviewed & processed usin g the Review External Gifts forms Œ AGAWGIF and APAWPRS. The following speaks onl y to these forms to allow reviewing of the Encompass gifts. Missing Pledge Duration code - Number of months not found on ATVPDUR Indicates there is no matching pledge duration value in the Banner Duration Code Validation table viewed on the ATVPDUR form. See Pledge duration for details on how to resolve this issue. Missing Banner Pledge # Indicates one of the following two scenarios: ŁThe institution is trying to pull over a subsequent pledge payment but they have not yet pulled over the original scheduled payment transaction th at is used to create the corresponding pledge in Banner. Therefore, the pledge does not yet exist in Banner. ŁThe institution used Encompass and allowed entry of scheduled payment transactions prior to upgrading to this release. Additionally, the institution has not yet performed the set-up step that allows them to link the unique encompass pledge # to an existing Banner pledge number so that subsequent pledge payments on a scheduled payment transaction can be handled by Banner. To correct this error, you must link the unique Encompass pledge ID to the correct corresponding Banner Pledge. See Adjustments required for scheduled payments entered before 8.6.1 for details on how to resolve this issue. Error MessageDescription /n 178 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector Viewing Processing Instructions Any processing instructions that the donor provides in Encompas s will display in a new Processing instructions field, which is vi sible on the Gift Details tab in AGAWGIF. Information in this field is inquiry-only. When you access this field, instructions appea r in the lower-left indicating this field contains fiAdditional Processing Instructions fr om the donor to help ensure this gift is posted per the donor's wishes.fl Modifying the Gift Type value When you access the Gift Type field to modify the value, the field will display a new drop- down, which validates against ATVGIFT. This is the same fashion in which the Gift Type field appears on the AGAGIFT form. Handling gifts with no Designation If a gift is pulled from Enco mpass and contains no designation, Banner will not allow you to save or post the gift. When this situatio n occurs, you must enter a Designation and it must be one that is valid for the Campaign. Note: If you attempt to check the 'OK to Load' check box and the Designation value is missing, you will receive an error that indicates the Designation value is required to create gifts. Under these circumstances you will be allowed to save any changes on the Gift Details tab. However, you will not be allowed to check the 'OK to Load' check box while this error condition exists. Viewing Processing Instruc tions for Billing PhoneWhen billing information is pulled for unauthenticated gifts, the billing phone information from Encompass is passed to Banner as a text field. This information can be viewed on the APAWPRS form in a new inquiry-only field named Processing Instructions. The telephone number that appears in this field will contain a prefix of Billing Phone: and will be followed by the actual number. Note: This data is only stored in APBWID N. It is not stored in any of the permanent bio or gift tables since it is used to facilitate the communication of this data from Encompass to inform the user of the need to transcribe the number into the appropriate phone fields. Warning! If you choose the Create Constituent option and there is data in the Processing Instructions field, but there is no data in the apbwidn_phone_number field, a warning message will indicate the Processing Instructions contains data but no phone number value has /n 179 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector been entered. This message aims to help ensure you don't inadvertently miss the opportunity to transcribe phone information into the phone fields. Display of Encompass Data on AGAWGIF The following provides a listing of the various data elements that can be seen on the AGAWGIF and APAWPRS forms and indicates how and if they are supported for the Advancement Connector Gift Integration. AGAWGIF Œ Gift Details tab Anywhere that it says ‚Not Supported™ is simply an indication the data element is not pulled over from Encompass via the Gift Integration. Any exiting functionality tied to that data element on the External Gift forms continues to apply. Field LabelGift Integration Support Configuration Requirements External IDProvided by iModul es in the gift web service response.Represents the unique id of the member in Encompass (member id). NoneBanner IDProvided by iModules in the gift web service response if available. If provided and the Banner ID is valid, this indicates an authenticated gift. This field will be blank for unauthenticated gifts. NoneOK to LoadThis is used by standard external gift review functionality and its purpose or use has not changed. NoneGift NumberThis unique Banner Gift Number value is assigned by Banner, per standard external gift processing. NoneGift TypeThis is not provi ded by Encompass. Instead this value is populated based on the default Gift Type identified on AGACTRL. AGACTRLDateProvided by iModules in the web service response.Represents the date the gift was made by the donor. NoneAmountProvided by iModules in the web service response.Represents the total gift amount. None/n 180 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector Fiscal YearThis gets populated with the ATVFISC_CODE where the gift_date is between the atvfisc_start_date and the atvfisc_end_date. NoneEntry DateThis is populated by Banner with the sysdate (system date). NoneVehicleNot supportedNone Match FormNot supportedNone CategoryŁFor an authenticated gift, this value is the Donot Category value associated with the Banner ID. ŁFor an unauthenticated gift, if a default value for Donor Category has been entered on AGACTRL, that value will default when the gift is loaded into the temporary gift tables. ŁDonor Category will get updated on the AGAWGIF form (agbghld table) if a change is made on the APAWPRS form (apbwidn table). AGACTRLClass 1Supported for Gift Integration via specific use and configuration of an Encompass instance field.Instance field Class 2Supported for Gift Integration via specific use and configuration of an Encompass instance field.Instance field Class 3Supported for Gift Integration via specific use and configuration of an Encompass instance field.Instance field AuthorizationProvided by iModules in the web service response.NoneReferenceNot supportedNone CommentSupported for Gift Integration via specific use and configuration of an Encompass instance field.Instance field Processing Instructions Supported for Gift Integration via specific use and configuration of an Encompass instance field.This field will potentially contain information for two Encompass fields Œ Processing Instructions and Matching Gift Company. Instance field Field LabelGift Integration Support Configuration Requirements /n 181 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector External Gift IDProvided by iModules in the web service response.Represents the unique external gift ID assigned by Encompass. NoneUserThe user responsible for pulling this gift over to the Banner temporary gift tables for review. If done manually, this will reflect the user initiating the pull. If done by the scheduler, this will have the value ADVCONN. NoneOrigin For gifts pulled from Encompass through the Advancement Connector, the Origin value will always equal AUKEXGF. This is set by Banner logic. NoneActivity DateThe date this reco rd was last updated. This is initially set to the date and time the temporary gift records are created in Banner. NoneSolicitor InformationiModules Gift Integration does not support the pulling of the Solicitation, Organization or ID fields from Encompass. However, per current functionality, when reviewing a gift the user is able to make modifications to these fields on the Gift Details tab if desired. N/ACampaign and Designation Details Gift AmountProvided by iModules in the web service response.Represents the individual amounts for each designation. NonePledgeNot supportedN/A CampaignThis is set to the Campaign value on the Gift Pull Profile used to pull over this gift. Gift Pull Profile set-up on the AUACDEF the form.DesignationProvided by iModules in the web service response.Represent the individual designation(s) for the gift. Instance field Field LabelGift Integration Support Configuration Requirements /n 182 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector AGAWGIF Œ Pledge Details tab Field LabelGift Integration Support Configuration Requirements AcceptedNot supported N/ASpouse SplitNot supported N/APledge Not supported N/AIndividual RulesNot supported N/AAmount Provided by iModules in the web service response.Represents the total pledge amount. NoneInstitution RulesNot supported N/ADateProvided by iModules in the web service response. Represents the date the pledge was made by the donor. NoneFiscal YearThis gets populated with the ATVFISC_CODE where the pledge_date is between the atvfisc_start_date and the atvfisc_end_date ATVFISC Status This is not provided by Encompass. Status codes are defined on the Membership Status Code Validation Form (ATVAMST) None. Type This is not provided by Encompass. Instead this value is populated based on the default Pledge Type identified on AGACTRL. If the default is not defined on AGACTRL, you must enter the pledge type on AGAWPLG before the pledge can be accepted and stored in Banner. AGACTRLPledge Class 1This is not prov ided by Encompass. Instead this value is populated based on the default pledge classification specified on ATVPCLS. ATVPCLS Pledge Class 2This is not prov ided by Encompass. Instead this value is populated based on the default pledge classification specified on ATVPCLS. ATVPCLS Pledge Class 3This is not prov ided by Encompass. Instead this value is populated based on the default pledge classification specified on ATVPCLS. ATVPCLS Vehicle Not supported. None /n 183 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector CommentsSupported for Gift Integration via specific use and configuration of an Encompass instance field.Instance field ReminderProvided by iModules in the web service response.Represents the reminder code for the installment. NoneFirst Bill Date This is populated by Banner with the sysdate(system date). NoneExternal Next Payment DateProvided by iModules in the web service response.Represents the date th at the next payment will be taken by the external party providing this pledge information. NoneFrequencyProvided by iModules in the web service response.Represents the frequency of the installments. ATVFREQ Last Bill Date This is populated by Banner with the sysdate(system date). Represents the frequency of the installments. NoneDurationProvided by iModules in the web service response.Represents the duration of the installments. NoneCampaign 1This is set to the Campaign value on the Gift Pull Profile used to pull over this gift. Gift Pull Profile set-up on the AUACDEF the form.Campaign 2This is set to the Campaign value on the Gift Pull Profile used to pull over this gift. Gift Pull Profile set-up on the AUACDEF the form.Campaign 3This is set to the Campaign value on the Gift Pull Profile used to pull over this gift. Gift Pull Profile set-up on the AUACDEF the form.Designation 1This is set to the Campaign value on the Gift Pull Profile used to pull over this gift. Gift Pull Profile set-up on the AUACDEF the form.Field LabelGift Integration Support Configuration Requirements /n 184 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector APAWPRS Œ Person Information tab Designation 2This is set to the Campaign value on the Gift Pull Profile used to pull over this gift. Gift Pull Profile set-up on the AUACDEF the form.Designation 3This is set to the Campaign value on the Gift Pull Profile used to pull over this gift. Gift Pull Profile set-up on the AUACDEF the form.Amount 1Provided by iModules in the web service response.Represents the pledge amount for the campaign/designation combination. NoneAmount 2Provided by iModules in the web service response.Represents the pledge amount for the campaign/designation combination. NoneAmount 3Provided by iModules in the web service response.Represents the pledge amount for the campaign/designation combination. NoneField LabelGift Integration Support Configuration Requirements External IDProvided by iModul es in the gift web service response.Represents the unique id of the member in Encompass (member id). NoneProcessedStandard Banner functionality.N/A Generate IDStandard Banner functionality.N/A Field LabelGift Integration Support Configuration Requirements /n 185 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector Banner IDProvided by iModules in the gift web service response if available. If provided and the Banner ID is valid, this indicates an authenticated gift. This field will be blank for unauthenticated gifts. To ensure you do not add a new Banner ID for someone who already exists in your Banner database, use the ‚Common Matching Entry™ from the Options menu on APAWPRS to perform a lookup on the donor name to determine if the unauthenticated donor already exists in Banner. If so, simply associate this unauthenticated gift to that existing Banner individual. NoneLast Name PrefixNot supportedN/A Last NameProvided by iModules in the gift web service response.NoneFirst NameProvided by iModules in the gift web service response.NoneMiddle NameNot supportedN/A PrefixNot supportedN/A SuffixNot supportedN/A Date of BirthNot supportedN/A GenderNot supportedN/A Maiden NameNot supportedN/A Donor CategoryIf this is an unauthenticated gift, if a default value for Donor Category has been entered on AGACTRL, that value will default when the gift is loaded into the temporary gift tables. AGACTRLPreferred ClassNot supported N/APreferred CollegeNot supported N/ALast Login DateNot supported N/ASpouse Information (four name-related fields) Not supported N/AField LabelGift Integration Support Configuration Requirements /n 186 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector APAWPRS Œ Address Information tab The below biographic and address information is only pulled over from Encompass for unauthenticated gifts. If it is an unauthentica ted gifts, the Billing address information entered by the donor will be di splayed to at least provide th e one known address for this unauthenticated donor. UserThe user responsible for pulling this gift over to the Banner temporary gift tables for review. If done manually, this will reflect the user initiating the pull. If done by the scheduler, this will have the value ADVCONN. NoneActivity DateThe date this reco rd was last updated. This is initially set to the date and time the temporary gift records are created in Banner. NoneGifts ExistsStandard functionality. This gets checked on the form if a re cord is found in AGBGHLD for the APBWIDN_IDNoneAddress Information Exists Standard functionality. If any of the APBWIDN address fields are populated then this will be checked. NoneField LabelGift Integration Support Configuration Requirements Address TypeThis is not provided by Encompass. Instead this value is populated based on the default Address Type identified on AGACTRL. AGACTRLHouse NumberNot supportedN/A Street Line 1Provided by iModules in the gift web service response.NoneStreet Line 2Provided by iModules in the gift web service response.NoneStreet Line 3Not supportedN/A Street Line 4Not supportedN/A CityProvided by iModules in the gift web service response.NoneState or ProvinceProvided by iModules in the gift web service response.Ensure codes in both systems match so no errors occur when pulling to Banner. Field LabelGift Integration Support Configuration Requirements /n 187 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector Zip or Postal CodeProvided by iModules in the gift web service response.NoneCountyNot supportedN/A NationProvided by iModules in the gift web service response.Ensure codes in both systems match so no errors occur when pulling to Banner. Processing Instructions Provided by iModules in the gift web service response.Instance field Telephone TypeThis is not prov ided by Encompass. Instead this value is populated based on the default Address Type identified on AGACTRL. AGACTRLPhone Number Components The billing phone number entered by the unauthenticated donor will display in the Processing Instructions field on the Address Information tab of APAWPRS. This information can be reviewed and then copied and pasted into the appropriate phone number components. The format of this field in Encompass does not allow direct mapping into the Banner Phone number fields. Require cut & paste by reviewer into the appropriate phone number component fields. Fax Type and Phone Number Components Not supportedN/A Email TypeThis is not provided by Encompass. Instead this value is populated based on the default Email Type identified on AGACTRL. AGACTRLEmail AddressProvided by iModules in the web service response.This represents the email address provided by the unauthenticated don or with their billing information when making the gift. NoneField LabelGift Integration Support Configuration Requirements /n 188 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector Schedule the transfer of data Banner Advancement provides optional functionality for scheduling the transfer of data between Banner and iModules™s Encompass pr oduct. This functionality allows your institution to set predefined sc hedules for the automatic running of push and pull profiles. These Scheduler records then automatically initiate these runs at the requested dates and times, relieving your staff of having to initiate them manually. Scheduler tab The Scheduler tab is used to add, modify, and delete Scheduler records. Adding a new scheduler recordYou can add one Scheduler record per profile. Th is Scheduler record is either active or inactive. You are not allowed to add another Sc heduler record for the same profile. If you try this, you get the following error message: ERROR Only one scheduler record for a profile is allowed .Use the following steps to add a new Scheduler re cord for a profile and initiate it from the Scheduler tab. 1.Access the Advancement Connecto r Initiation Form (AUAINIT). 2.Select the Scheduler tab. 3.Select Insert from the Record menu. 4.Indicate whether the Scheduler record is active or inactive. 5.Select a profile type from the Profile Type drop-down list. 6.Select the profile code from the Profile Code drop-down list. 7.Select the frequency from the Frequency drop-down list. 8.Enter the time you want to init iate the push or pull in the Start Time field. Note: Please be sure that you refer to the published guidelines provided by iModules regarding the use of Web services. These will help your institution better understand iModules recommendations regarding record volume, time of day recommendations for larger transactions sets, configuration settings, etc. 9.Enter the date when you want the selection to begin in the Selection Begin Date field.10. Enter the time when you want the selection to begin in the Selection Begin Time field.11. If you want an e-mail notification about the status of the scheduled job, enter an e-mail id in one of the four e-mail notification fields, as required. /n 189 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector 12. Save the changes. When the Scheduler record initiates a push request, the request selects the changes that occurred since the last time this process wa s successfully initiate d by this Scheduler record. If there is no prior run for this Sch eduler record that was successful, the entered Selection Begin Date and Time are used for selection purposes. Modifying an existing scheduler recordYou can modify a Scheduler record by modi fying the information you entered on the Scheduler tab fields. However, you are not allowed to make any modifications for the profile code. If you need to change the profile code, delete the existing record and add a new one with the new profile code. Deleting an existing scheduler recordUse the following steps to delete an existing Scheduler record. 1.Select the Scheduler record you want to delete. 2.Select Remove from the Record menu. You get the following message: Do you really want to delete this scheduler reco rd? It is possible to inactivate this record instead of deleting it. 3.Click Yes .The selected record is deleted. E-mail notificationThe Scheduler provides automated e-mail notificat ions to the institutio ns to automatically communicate whether the scheduled jobs were run successfully or not. If there were any issues with the job running, the e-mail would pr ompt the appropriate personnel to look into and address the issue. The institutions can identify as many as fo ur different e-mail addresses to which this notification should be sent for each scheduler record. The use of these four fields is optional. Certain format checks are performed when an e-mail address is entered. These include a warning message and automatic removal of spaces as well as an error if there is not at least one character before the @ and before the . in the e-mail address. A sample e-mail notification looks like the following: To: Email 1, 2, 3, 4 From: Banner Advancement Scheduler /n 190 Banner Advancement Data Load/Extract Handbook |Data Transfers Using the Advancement Connector Subject: Scheduler Request Initiated ST ATUS: Completed PROFILE: Banner Push Email text:Request ID: 9999 Type: Push Date Run: 2/24/2011 Status: Completed Profile: Banner Push Frequency: Daily Error Info: only populated if error information was returned in the web service response Note: If a Gift Push or Pull is completed, a Total Pledges count displays in the summary counts. When a push or pull request is submitted, that request id first moves to INITIATED status. When the request is fully processed, the status will then change to refl ect whether or not it was completed successfully. This is the point at which e-mail notifications are generated. Therefore, if for some reason a request does not move from the INTITIATED status, e-mail notifications will not be generate d. Any of these requests shoul d be investigated as this most likely means something is wrong with the Connector installation or configuration. /n 191 Banner Advancement Data Load/Extract Handbook |Appendix A - Advancement Connector Data Mappings Appendix A - Advancement Connector Data Mappings Specific Banner® database fields are mapped to specific iModules Encompass database fields to ensure the integrity of both database s. This appendix provides details about the data mappings that are supp orted by baseline Banner Advancement and delivered on the Advancement Connector Data Mapping Form (AUACMAP). The tables in this appendix are organized by the following tabs that are displayed in Encompass: ŁBiographic information ŁPreferred contact information ŁEducation information ŁOther education information ŁSpouse and family information ŁBusiness information ŁBusiness contact information ŁActivities and honors information ŁAdmin only The tables in this appendix provide the following details for each data mapping: Table Heading Description Encompass Database NameName of the data element in the Encompass database Friendly NameLabel used in the En compass user interface to identify the data element TypeType of data field (drop-down list, text box, date box, e- mail text box confirm, or label) Maximum Field SizeMaximum size of the data element PullFlag that indicates whether the data element can be pulled from Encompass to Banner PushFlag that indicates whether the data element can be pushed from Banner to Encompass Banner Database NameName of the data element in the Banner database /n 192 Banner Advancement Data Load/Extract Handbook |Appendix A - Advancement Connector Data Mappings Selection Code RequiredFlag that indi cates whether a selection code must be entered on the Advancement Connector Profile Form (AUACDEF) when a push profile uses this data element Table Heading Description /n 193Banner Advancement Data Load/Extract Handbook |Appendix A - Advancement Connector Data Mappings Biographic informationEncompass Database NameFriendly NameType Max Field SizePullPushBanner Database Name Selection Code RequiredComments SPBPERS_NAME_PREFIXPrefixText box20 PSPBPERS_NAME_PREFIX SPRIDEN_FIRST_NAMEFirst NameText box60 PSPRIDEN_FIRST_NAME SPRIDEN_MIMiddle NameText box60 PSPRIDEN_MI SPRIDEN_LAST_NAMELast NameText box60 PSPR IDEN_LAST_NAMESPRIDEN_SURNAME_PREFIXLast Name PrefixText box60 PSPRIDEN_SURNAME_ PREFIX SPBPERS_NAME_SUFFIX SuffixText box20 PSPBPERS_NAME_SUFFIX SPBPERS_SEX GenderDrop- down list 1PSPBPERS_SEX SPBPERS_BIRTH_DATEBirth DateDa te box8 PSPBPERS_BIRTH_DATE APRSALU_SALU_CODESalutation Code (hidden) Drop- down list 4PAPRSALU_SALU_CODERequired - Indicates which salutation code is pushed to Encompass APRSALU_SALUTATIONSalutationT ext box120 PAPRSALU_SALUTATION /n 194Banner Advancement Data Load/Extract Handbook |Appendix A - Advancement Connector Data Mappings SPBPERS_ETHN_CDEEthnicityDrop- down list 1PSPBPERS_ETHN_CDE SPRIDEN_LAST_NAME_ ORG Organizati on Name Text box60PSPR IDEN_LAST_NAMEAPRCATG_DONR_CODEPrimary Donor CodeText box4P APRCATG_DONR_CODERequired - Indicates which donor category(s) are pushed to Encompass. If blank, all constituents are included in the push. If one or more selection codes are entered (each separated by a comma with no spaces), only those constituents that match one of the entered selection codes are included in the push. If primary Donor Category code in Banner changes, all biographic data for the constituent is pushed regardless of whether the bio changes fall within the specified date range and regardless of whether the push was initiated manually or by the scheduler. For additional information, please refer to fiSpecial Handling when the Primary Donor Code has Changed in Bannerfl on page127 .Encompass Database NameFriendly NameType Max Field SizePullPushBanner Database Name Selection Code RequiredComments /n 195Banner Advancement Data Load/Extract Handbook |Appendix A - Advancement Connector Data Mappings Preferred contact information Encompass Database NameFriendly NameType Max Field SizePullPushBanner Database Name Selection Code RequiredComments SPRADDR_STATUS_IND_ PREFAddress Status (hidden) Drop- down list 1PPSPRADDR_STATUS_IND GOREMAL_EMAIL_ ADDRESS_PREFPrimary EmailE-mail text box confirm 128PPGOREMAL_EMAIL_ ADDRESSGOREMAL_EMAL_CODE_ PREFPrimary Email CodeDrop- down list 4PPGOREMAL_EMAL_CODE /n 196Banner Advancement Data Load/Extract Handbook |Appendix A - Advancement Connector Data Mappings SPRADDR_ATYP_CODE_ PREFPreferred Address Type Drop- down list 2PPSPRADDR_ATYP_CODEOptional If blank, the following address fields are retrieved from the preferred address in Banner Advancement. If a selection code is entered, the following address fields are retrieved from the active address record that has this address type and is effective on the date of the push. SPRADDR_STREET_ LINE1_PREFPreferred Address 1 Text Box75PPSPRADDR_STREET_ LINE1 SPRADDR_STREET_ LINE2_PREFPreferred Address 2 Text Box75PPSPRADDR_STREET_ LINE2 SPRADDR_STREET_ LINE3_PREFPreferred Address 3 Text Box75PPSPRADDR_STREET_ LINE3 SPRADDR_STREET_ LINE4_PREFPreferred Address 4 Text Box75PPSPRADDR_STREET_ LINE4 Encompass Database NameFriendly NameType Max Field SizePullPushBanner Database Name Selection Code RequiredComments /n 197Banner Advancement Data Load/Extract Handbook |Appendix A - Advancement Connector Data Mappings SPRADDR_HOUSE_NUMBER_PREF House NumberText Box10PPSPRADDR_HOUSE_ NUMBER SPRADDR_CITY_PREFCityText Box50PPSPRADDR_CITY SPRADDR_STAT_CODE_ PREFStateDrop- down list 3PPSPRADDR_STAT_CODE SPRADDR_ZIP_PREFZipText Box30PPSPRADDR_ZIP SPRADDR_NATN_CODE_ PREFCountryDrop- down list 5PPSPRADDR_NATN_CODE Encompass Database NameFriendly NameType Max Field SizePullPushBanner Database Name Selection Code RequiredComments /n 198Banner Advancement Data Load/Extract Handbook |Appendix A - Advancement Connector Data Mappings SPRTELE_TELE_CODEPreferred Phone Type Drop- down list 4PPSPRTELE_TELE_CODEOptional If blank, the fiprimaryfl phone number is the phone number that is associated with the most current preferred address (defined on APACONS). The phone type on this phone record is used to transfer preferred phone numbers between Encompass and Banner. If the preferred address does not have a phone number, preferred phone numbers are not transferred between Encompass and Banner. If the selection code specifies a phone type, that phone type is used to transfer preferred phone numbers between Banner and Encompass. Encompass Database NameFriendly NameType Max Field SizePullPushBanner Database Name Selection Code RequiredComments /n 199Banner Advancement Data Load/Extract Handbook |Appendix A - Advancement Connector Data Mappings SPRTELE_ATYP_CODE_ PREFPreferred Phone Address Type (hidden) Text Box2PPSPRTELE_ATYP_CODE SPRTELE_ADDR_ SEQNO_PREF Preferred Phone Address Sequence Number (hidden) Text Box2PPSPRTELE_ADDR_SEQNO SPRTELE_CTRY_CODE_ PHONE_PREFPhone Country Code Text Box4PPSPRTELE_CTRY_CODE_ PHONE SPRTELE_PHONE_AREA_ PREFPhone Area CodeText Box6PPSPRTELE_PHONE_AREA SPRTELE_PHONE_ NUMBER_PREF Phone NumberText Box12PPSPRTELE_PHONE_ NUMBER SPRTELE_PHONE_EXT_ PREFPhone ExtensionText Box10PPSPRTELE_PHONE_EXT Encompass Database NameFriendly NameType Max Field SizePullPushBanner Database Name Selection Code RequiredComments /n 200Banner Advancement Data Load/Extract Handbook |Appendix A - Advancement Connector Data Mappings SPRTELE_TELE_CODE_ FAX_PREF Fax Phone Type (hidden) Drop- down list 4PPSPRTELE_TELE_CODERequired - Indicates which phone type represents the fax The following fax fields are retrieved from the active record that has this phone type and is effective on the date of the push. SPRTELE_ATYP_CODE_ FAX_PREF Fax Phone Address Type (hidden) Text Box2PPSPRTELE_ATYP_CODE SPRTELE_ADDR_ SEQNO_FAX_PREF Fax Phone Address Sequence Number (hidden) Text Box2PPSPRTELE_ADDR_SEQNO SPRTELE_CTRY_CODE_ FAX_PREF Fax Country Code Text Box4PPSPRTELE_CTRY_CODE_ PHONESPRTELE_FAX_AREA_ PREFFax Area CodeText Box6PPSPRTELE_PHONE_AREA Encompass Database NameFriendly NameType Max Field SizePullPushBanner Database Name Selection Code RequiredComments /n 201Banner Advancement Data Load/Extract Handbook |Appendix A - Advancement Connector Data Mappings SPRTELE_FAX_NUMBER_ PREFFax NumberText Box12PPSPRTELE_PHONE_ NUMBER SPRTELE_FAX_EXT_ PREFFax ExtensionText Box10PPSPRTELE_PHONE_EXT SPRTELE_CTRY_CODE_ PHONE_CELLCell Phone Country CodeText Box4PPSPRTELE_CTRY_CODE_ PHONESPRTELE_PHONE_AREA_ CELLCell Phone Area CodeText Box6PPSPRTELE_PHONE_AREA SPRTELE_PHONE_ NUMBER_CELL Cell Phone NumberText Box12PPSPRTELE_PHONE_ NUMBER Encompass Database NameFriendly NameType Max Field SizePullPushBanner Database Name Selection Code RequiredComments /n 202Banner Advancement Data Load/Extract Handbook |Appendix A - Advancement Connector Data Mappings Education informationEncompass Database NameFriendly NameType Max Field SizePullPushBanner Database Name Selection Code RequiredComments APBCONS_COLL_CODE_PREFPreferred School Drop- down list 2PAPBCONS_COLL_CODE_ PREF APBCONS_PREF_CLASPreferred Class Year Drop- down list 4PAPBCONS_PREF_CLAS APRADEG_SEQ_NO_ PRIM_1Degree 1 sequence number (hidden) LabelInteger (5) PAPRADEG_SEQ_NO APRADEG_DEGC_CODE_ PRIM_11st Degree Label / Drop- down list 6PAPRADEG_DEGC_CODEFo ur most recent degrees are extracted, based on activity date. APRADEG_ACYR_CODE_ PRIM_11st Degree Year Label / Drop- down list 4PAPRADEG_ACYR_CODE APRADEG_SBGI_CODE_ PRIM_11st Degree Institution CodeDrop- down list 6PAPRADEG_SBGI_CODE APRADEG_COLL_CODE_ PRIM_11st Degree School Drop- down list 2PAPRADEG_COLL_CODE /n 203Banner Advancement Data Load/Extract Handbook |Appendix A - Advancement Connector Data Mappings APRADEG_CAMP_CODE_PRIM_11st Degree CampusDrop- down list 3PAPRADEG_CAMP_CODE APRAMAJ_MAJR_CODE_ 1_PRIM_1 1st Degree Major 1 Label / Drop- down list 4PAPRAMAJ_MAJR_CODE Six most recent majors for the degree are extracted, based on activity date. APRAMAJ_MAJR_CODE_ 2_PRIM_1 1st Degree Major 2 Label / Drop- down list 4PAPRAMAJ_MAJR_CODE APRAMAJ_MAJR_CODE_ 3_PRIM_1 1st Degree Major 3 Label / Drop- down list 4PAPRAMAJ_MAJR_CODE APRAMAJ_MAJR_CODE_ 4_PRIM_1 1st Degree Major 4 Label / Drop- down list 4PAPRAMAJ_MAJR_CODE APRAMAJ_MAJR_CODE_5_PRIM_1 1st Degree Major 5 Label / Drop-down list 4PAPRAMAJ_MAJR_CODE APRAMAJ_MAJR_CODE_ 6_PRIM_1 1st Degree Major 6 Label / Drop- down list 4PAPRAMAJ_MAJR_CODE Encompass Database NameFriendly NameType Max Field SizePullPushBanner Database Name Selection Code RequiredComments /n 204Banner Advancement Data Load/Extract Handbook |Appendix A - Advancement Connector Data Mappings APRADEG_MAJR_CODE_CONC_1_PRIM_11st Degree Major Concentr ation 1 Label / Drop- down list 4PAPRADEG_MAJR_CODE_ CONC_1APRADEG_MAJR_CODE_ CONC_2_PRIM_11st Degree Major Concentr ation 2 Label / Drop- down list 4PAPRADEG_MAJR_CODE_ CONC_2APRADEG_MAJR_CODE_ CONC_3_PRIM_11st Degree Major Concentr ation 3 Label / Drop- down list 4PAPRADEG_MAJR_CODE_ CONC_3APRADEG_MAJR_CODE_ CONC_4_PRIM_11st Degree Major Concentr ation 4 Label / Drop- down list 4PAPRADEG_MAJR_CODE_ CONC_4APRADEG_MAJR_CODE_ CONC_5_PRIM_11st Degree Major Concentr ation 5 Label / Drop- down list 4PAPRADEG_MAJR_CODE_ CONC_5Encompass Database NameFriendly NameType Max Field SizePullPushBanner Database Name Selection Code RequiredComments /n 205Banner Advancement Data Load/Extract Handbook |Appendix A - Advancement Connector Data Mappings APRADEG_MAJR_CODE_CONC_6_PRIM_11st Degree Major Concentr ation 6 Label / Drop- down list 4PAPRADEG_MAJR_CODE_ CONC_6APRADEG_MAJR_CODE_ MINR_1_PRIM_1 1st Degree Minor Label / Drop- down list 4PAPRADEG_MAJR_CODE_ MINR_1 APRADEG_MAJR_CODE_ MINR_2_PRIM_1 1st Degree Minor 2 Label / Drop- down list 4PAPRADEG_MAJR_CODE_ MINR_2 APRADEG_SEQ_NO_ PRIM_2Degree 2 sequence number (hidden) LabelInteger (5) PAPRADEG_SEQ_NO APRADEG_DEGC_CODE_ PRIM_22nd Degree Label / Drop- down list 6PAPRADEG_DEGC_CODEFo ur most recent degrees are extracted, based on activity date. APRADEG_ACYR_CODE_ PRIM_22nd Degree Year Label / Drop- down list 4PAPRADEG_ACYR_CODE APRADEG_SBGI_CODE_ PRIM_22nd Degree Institution CodeDrop- down list 6PAPRADEG_SBGI_CODE Encompass Database NameFriendly NameType Max Field SizePullPushBanner Database Name Selection Code RequiredComments /n 206Banner Advancement Data Load/Extract Handbook |Appendix A - Advancement Connector Data Mappings APRADEG_COLL_CODE_PRIM_22nd Degree School Drop- down list 2PAPRADEG_COLL_CODE APRADEG_CAMP_CODE_ PRIM_22nd Degree CampusDrop- down list 3PAPRADEG_CAMP_CODE APRAMAJ_MAJR_CODE_ 1_PRIM_2 2nd Degree Major 1 Label / Drop- down list 4PAPRAMAJ_MAJR_CODE Six most recent majors for the degree are extracted, based on activity date. APRAMAJ_MAJR_CODE_ 2_PRIM_2 2nd Degree Major 2 Label / Drop- down list 4PAPRAMAJ_MAJR_CODE APRAMAJ_MAJR_CODE_ 3_PRIM_2 2nd Degree Major 3 Label / Drop- down list 4PAPRAMAJ_MAJR_CODE APRAMAJ_MAJR_CODE_4_PRIM_2 2nd Degree Major 4 Label / Drop-down list 4PAPRAMAJ_MAJR_CODE APRAMAJ_MAJR_CODE_ 5_PRIM_2 2nd Degree Major 5 Label / Drop- down list 4PAPRAMAJ_MAJR_CODE APRAMAJ_MAJR_CODE_ 6_PRIM_2 2nd Degree Major 6 Label / Drop- down list 4PAPRAMAJ_MAJR_CODE Encompass Database NameFriendly NameType Max Field SizePullPushBanner Database Name Selection Code RequiredComments /n 207Banner Advancement Data Load/Extract Handbook |Appendix A - Advancement Connector Data Mappings APRADEG_MAJR_CODE_CONC_1_PRIM_22nd Degree Major Concentr ation 1 Label / Drop- down list 4PAPRADEG_MAJR_CODE_ CONC_1APRADEG_MAJR_CODE_ CONC_2_PRIM_22nd Degree Major Concentr ation 2 Label / Drop- down list 4PAPRADEG_MAJR_CODE_ CONC_2APRADEG_MAJR_CODE_ CONC_3_PRIM_22nd Degree Major Concentr ation 3 Label / Drop- down list 4PAPRADEG_MAJR_CODE_ CONC_3APRADEG_MAJR_CODE_ CONC_4_PRIM_22nd Degree Major Concentr ation 4 Label / Drop- down list 4PAPRADEG_MAJR_CODE_ CONC_4APRADEG_MAJR_CODE_ CONC_5_PRIM_22nd Degree Major Concentr ation 5 Label / Drop- down list 4PAPRADEG_MAJR_CODE_ CONC_5Encompass Database NameFriendly NameType Max Field SizePullPushBanner Database Name Selection Code RequiredComments /n 208Banner Advancement Data Load/Extract Handbook |Appendix A - Advancement Connector Data Mappings APRADEG_MAJR_CODE_CONC_6_PRIM_22nd Degree Major Concentr ation 6 Label / Drop- down list 4PAPRADEG_MAJR_CODE_ CONC_6APRADEG_MAJR_CODE_ MINR_1_PRIM_2 2nd Degree Minor Label / Drop- down list 4PAPRADEG_MAJR_CODE_ MINR_1 APRADEG_MAJR_CODE_ MINR_2_PRIM_2 2nd Degree Minor 2 Label / Drop- down list 4PAPRADEG_MAJR_CODE_ MINR_2 APRADEG_SEQ_NO_ PRIM_3Degree 3 sequence number (hidden) LabelInteger (5) PAPRADEG_SEQ_NO APRADEG_DEGC_CODE_ PRIM_33rd Degree Label / Drop- down list 6PAPRADEG_DEGC_CODEFo ur most recent degrees are extracted, based on activity date. APRADEG_ACYR_CODE_ PRIM_33rd Degree Year Label / Drop- down list 4PAPRADEG_ACYR_CODE APRADEG_SBGI_CODE_ PRIM_33rd Degree Institution CodeLabel / Drop- down list 6PAPRADEG_SBGI_CODE Encompass Database NameFriendly NameType Max Field SizePullPushBanner Database Name Selection Code RequiredComments /n 209Banner Advancement Data Load/Extract Handbook |Appendix A - Advancement Connector Data Mappings APRADEG_COLL_CODE_PRIM_33rd Degree School Drop- down list 2PAPRADEG_COLL_CODE APRADEG_CAMP_CODE_ PRIM_33rd Degree CampusDrop- down list 3PAPRADEG_CAMP_CODE APRAMAJ_MAJR_CODE_ 1_PRIM_3 3rd Degree Major 1 Label / Drop- down list 4PAPRAMAJ_MAJR_CODE Six most recent majors for the degree are extracted, based on activity date. APRAMAJ_MAJR_CODE_ 2_PRIM_3 3rd Degree Major 2 Label / Drop- down list 4PAPRAMAJ_MAJR_CODE APRAMAJ_MAJR_CODE_ 3_PRIM_3 3rd Degree Major 3 Label / Drop- down list 4PAPRAMAJ_MAJR_CODE APRAMAJ_MAJR_CODE_4_PRIM_3 3rd Degree Major 4 Label / Drop-down list 4PAPRAMAJ_MAJR_CODE APRAMAJ_MAJR_CODE_ 5_PRIM_3 3rd Degree Major 5 Label / Drop- down list 4PAPRAMAJ_MAJR_CODE APRAMAJ_MAJR_CODE_ 6_PRIM_3 3rd Degree Major 6 Label / Drop- down list 4PAPRAMAJ_MAJR_CODE Encompass Database NameFriendly NameType Max Field SizePullPushBanner Database Name Selection Code RequiredComments /n 210Banner Advancement Data Load/Extract Handbook |Appendix A - Advancement Connector Data Mappings APRADEG_MAJR_CODE_CONC_1_PRIM_33rd Degree Major Concentr ation 1 Label / Drop- down list 4PAPRADEG_MAJR_CODE_ CONC_1APRADEG_MAJR_CODE_ CONC_2_PRIM_33rd Degree Major Concentr ation 2 Label / Drop- down list 4PAPRADEG_MAJR_CODE_ CONC_2APRADEG_MAJR_CODE_ CONC_3_PRIM_33rd Degree Major Concentr ation 3 Label / Drop- down list 4PAPRADEG_MAJR_CODE_ CONC_3APRADEG_MAJR_CODE_ CONC_4_PRIM_33rd Degree Major Concentr ation 4 Label / Drop- down list 4PAPRADEG_MAJR_CODE_ CONC_4APRADEG_MAJR_CODE_ CONC_5_PRIM_33rd Degree Major Concentr ation 5 Label / Drop- down list 4PAPRADEG_MAJR_CODE_ CONC_5Encompass Database NameFriendly NameType Max Field SizePullPushBanner Database Name Selection Code RequiredComments /n 211Banner Advancement Data Load/Extract Handbook |Appendix A - Advancement Connector Data Mappings APRADEG_MAJR_CODE_CONC_6_PRIM_33rd Degree Major Concentr ation 6 Label / Drop- down list 4PAPRADEG_MAJR_CODE_ CONC_6APRADEG_MAJR_CODE_ MINR_1_PRIM_3 3rd Degree Minor Label / Drop- down list 4PAPRADEG_MAJR_CODE_ MINR_1 APRADEG_MAJR_CODE_ MINR_2_PRIM_3 3rd Degree Minor 2 Label / Drop- down list 4PAPRADEG_MAJR_CODE_ MINR_2 APRADEG_SEQ_NO_ PRIM_4Degree 4 sequence number (hidden) LabelInteger (5) PAPRADEG_SEQ_NO APRADEG_DEGC_CODE_ PRIM_44th Degree Label / Drop- down list 6PAPRADEG_DEGC_CODEFo ur most recent degrees are extracted, based on activity date. APRADEG_ACYR_CODE_ PRIM_44th Degree Year Label / Drop- down list 4PAPRADEG_ACYR_CODE APRADEG_SBGI_CODE_ PRIM_44th Degree Institution Code Label / Drop- down list 6PAPRADEG_SBGI_CODE Encompass Database NameFriendly NameType Max Field SizePullPushBanner Database Name Selection Code RequiredComments /n 212Banner Advancement Data Load/Extract Handbook |Appendix A - Advancement Connector Data Mappings APRADEG_COLL_CODE_PRIM_44th Degree School Drop- down list 2PAPRADEG_COLL_CODE APRADEG_CAMP_CODE_ PRIM_44th Degree CampusDrop- down list 3PAPRADEG_CAMP_CODE APRAMAJ_MAJR_CODE_ 1_PRIM_4 4th Degree Major 1 Label / Drop- down list 4PAPRAMAJ_MAJR_CODE Six most recent majors for the degree are extracted, based on activity date. APRAMAJ_MAJR_CODE_ 2_PRIM_4 4th Degree Major 2 Label / Drop- down list 4PAPRAMAJ_MAJR_CODE APRAMAJ_MAJR_CODE_ 3_PRIM_4 4th Degree Major 3 Label / Drop- down list 4PAPRAMAJ_MAJR_CODE APRAMAJ_MAJR_CODE_4_PRIM_4 4th Degree Major 4 Label / Drop-down list 4PAPRAMAJ_MAJR_CODE APRAMAJ_MAJR_CODE_ 5_PRIM_4 4th Degree Major 5 Label / Drop- down list 4PAPRAMAJ_MAJR_CODE APRAMAJ_MAJR_CODE_ 6_PRIM_4 4th Degree Major 6 Label / Drop- down list 4PAPRAMAJ_MAJR_CODE Encompass Database NameFriendly NameType Max Field SizePullPushBanner Database Name Selection Code RequiredComments /n 213Banner Advancement Data Load/Extract Handbook |Appendix A - Advancement Connector Data Mappings APRADEG_MAJR_CODE_CONC_1_PRIM_44th Degree Major Concentr ation 1 Label / Drop- down list 4PAPRADEG_MAJR_CODE_ CONC_1APRADEG_MAJR_CODE_ CONC_2_PRIM_44th Degree Major Concentr ation 2 Label / Drop- down list 4PAPRADEG_MAJR_CODE_ CONC_2APRADEG_MAJR_CODE_ CONC_3_PRIM_44th Degree Major Concentr ation 3 Label / Drop- down list 4PAPRADEG_MAJR_CODE_ CONC_3APRADEG_MAJR_CODE_ CONC_4_PRIM_44th Degree Major Concentr ation 4 Label / Drop- down list 4PAPRADEG_MAJR_CODE_ CONC_4APRADEG_MAJR_CODE_ CONC_5_PRIM_44th Degree Major Concentr ation 5 Label / Drop- down list 4PAPRADEG_MAJR_CODE_ CONC_5Encompass Database NameFriendly NameType Max Field SizePullPushBanner Database Name Selection Code RequiredComments /n 214Banner Advancement Data Load/Extract Handbook |Appendix A - Advancement Connector Data Mappings Other education informationAPRADEG_MAJR_CODE_CONC_6_PRIM_44th Degree Major Concentr ation 6 Label / Drop- down list 4PAPRADEG_MAJR_CODE_ CONC_6APRADEG_MAJR_CODE_ MINR_1_PRIM_4 4th Degree Minor Label / Drop- down list 4PAPRADEG_MAJR_CODE_ MINR_1 APRADEG_MAJR_CODE_ MINR_2_PRIM_4 4th Degree Minor 2 Label / Drop- down list 4PAPRADEG_MAJR_CODE_ MINR_2 Encompass Database NameFriendly NameType Max Field SizePullPushBanner Database Name Selection Code RequiredComments APRADEG_SEQ_NO_OTHER_1 Other Degree 1 sequence number (hidden) LabelInteger (5) PAPRADEG_SEQ_NO Encompass Database NameFriendly NameType Max Field SizePullPushBanner Database Name Selection Code RequiredComments /n 215Banner Advancement Data Load/Extract Handbook |Appendix A - Advancement Connector Data Mappings APRADEG_DEGC_CODE_OTHER_1 Other 1st Degree Drop- down list 6PAPRADEG_DEGC_CODEFo ur most recent other degrees are extracted, based on activity date. APRADEG_ACYR_CODE_ OTHER_1 Other 1st Degree Year Drop- down list 4PAPRADEG_ACYR_CODE APRADEG_SBGI_CODE_ OTHER_1 Other 1st Degree Institution CodeDrop- down list 6PAPRADEG_SBGI_CODE APRADEG_COLL_CODE_ OTHER_1 Other 1st Degree School Drop- down list 2PAPRADEG_COLL_CODE APRADEG_CAMP_CODE_ OTHER_1 Other 1st Degree CampusDrop- down list 3PAPRADEG_CAMP_CODE APRAMAJ_MAJR_CODE_1_OTHER_1 Other 1st Degree Major 1 Label / Drop-down list 4PAPRAMAJ_MAJR_CODE Six most recent majors for the other degree are extracted, based on activity date. APRAMAJ_MAJR_CODE_ 2_OTHER_1 Other 1st Degree Major 2 Label / Drop- down list 4PAPRAMAJ_MAJR_CODE Encompass Database NameFriendly NameType Max Field SizePullPushBanner Database Name Selection Code RequiredComments /n 216Banner Advancement Data Load/Extract Handbook |Appendix A - Advancement Connector Data Mappings APRAMAJ_MAJR_CODE_3_OTHER_1 Other 1st Degree Major 3 Label / Drop- down list 4PAPRAMAJ_MAJR_CODE APRAMAJ_MAJR_CODE_ 4_OTHER_1 Other 1st Degree Major 4 Label / Drop- down list 4PAPRAMAJ_MAJR_CODE APRAMAJ_MAJR_CODE_ 5_OTHER_1 Other 1st Degree Major 5 Label / Drop- down list 4PAPRAMAJ_MAJR_CODE APRAMAJ_MAJR_CODE_ 6_OTHER_1 Other 1st Degree Major 6 Label / Drop- down list 4PAPRAMAJ_MAJR_CODE APRADEG_MAJR_CODE_ CONC_1_OTHER_1 Other 1st Degree Major Concentr ation 1 Label / Drop- down list 4PAPRADEG_MAJR_CODE_ CONC_1APRADEG_MAJR_CODE_CONC_2_OTHER_1 Other 1st Degree Major Concentr ation 2 Label / Drop-down list 4PAPRADEG_MAJR_CODE_ CONC_2APRADEG_MAJR_CODE_ CONC_3_OTHER_1 Other 1st Degree Major Concentr ation 3 Label / Drop- down list 4PAPRADEG_MAJR_CODE_ CONC_3Encompass Database NameFriendly NameType Max Field SizePullPushBanner Database Name Selection Code RequiredComments /n 217Banner Advancement Data Load/Extract Handbook |Appendix A - Advancement Connector Data Mappings APRADEG_MAJR_CODE_CONC_4_OTHER_1 Other 1st Degree Major Concentr ation 4 Label / Drop- down list 4PAPRADEG_MAJR_CODE_ CONC_4APRADEG_MAJR_CODE_ CONC_5_OTHER_1 Other 1st Degree Major Concentr ation 5 Label / Drop- down list 4PAPRADEG_MAJR_CODE_ CONC_5APRADEG_MAJR_CODE_ CONC_6_OTHER_1 Other 1st Degree Major Concentr ation 6 Label / Drop- down list 4PAPRADEG_MAJR_CODE_ CONC_6APRADEG_MAJR_CODE_ MINR_1_OTHER_1Other 1st Degree Minor Label / Drop- down list 4PAPRADEG_MAJR_CODE_ MINR_1 APRADEG_MAJR_CODE_ MINR_2_OTHER_1Other 1st Degree Minor 2 Label / Drop- down list 4PAPRADEG_MAJR_CODE_ MINR_2 APRADEG_SEQ_NO_ OTHER_2 Other Degree 2 sequence number (hidden) LabelInteger (5) PAPRADEG_SEQ_NO Encompass Database NameFriendly NameType Max Field SizePullPushBanner Database Name Selection Code RequiredComments /n 218Banner Advancement Data Load/Extract Handbook |Appendix A - Advancement Connector Data Mappings APRADEG_DEGC_CODE_OTHER_2 Other 2nd Degree Drop- down list 6PAPRADEG_DEGC_CODEFo ur most recent other degrees are extracted, based on activity date. APRADEG_ACYR_CODE_ OTHER_2 Other 2nd Degree Year Drop- down list 4PAPRADEG_ACYR_CODE APRADEG_SBGI_CODE_ OTHER_2 Other 2nd Degree Institution CodeDrop- down list 6PAPRADEG_SBGI_CODE APRADEG_COLL_CODE_ OTHER_2 Other 2nd Degree School Drop- down list 2PAPRADEG_COLL_CODE APRADEG_CAMP_CODE_ OTHER_2 Other 2nd Degree CampusDrop- down list 3PAPRADEG_CAMP_CODE APRAMAJ_MAJR_CODE_1_OTHER_2 Other 2nd Degree Major 1 Label / Drop-down list 4PAPRAMAJ_MAJR_CODE Six most recent majors for the other degree are extracted, based on activity date. APRAMAJ_MAJR_CODE_ 2_OTHER_2 Other 2nd Degree Major 2 Label / Drop- down list 4PAPRAMAJ_MAJR_CODE Encompass Database NameFriendly NameType Max Field SizePullPushBanner Database Name Selection Code RequiredComments /n 219Banner Advancement Data Load/Extract Handbook |Appendix A - Advancement Connector Data Mappings APRAMAJ_MAJR_CODE_3_OTHER_2 Other 2nd Degree Major 3 Label / Drop- down list 4PAPRAMAJ_MAJR_CODE APRAMAJ_MAJR_CODE_ 4_OTHER_2 Other 2nd Degree Major 4 Label / Drop- down list 4PAPRAMAJ_MAJR_CODE APRAMAJ_MAJR_CODE_ 5_OTHER_2 Other 2nd Degree Major 5 Label / Drop- down list 4PAPRAMAJ_MAJR_CODE APRAMAJ_MAJR_CODE_ 6_OTHER_2 Other 2nd Degree Major 6 Label / Drop- down list 4PAPRAMAJ_MAJR_CODE APRADEG_MAJR_CODE_ CONC_1_OTHER_2 Other 2nd Degree Major Concentr ation 1 Label / Drop- down list 4PAPRADEG_MAJR_CODE_ CONC_1APRADEG_MAJR_CODE_CONC_2_OTHER_2 Other 2nd Degree Major Concentr ation 2 Label / Drop-down list 4PAPRADEG_MAJR_CODE_ CONC_2APRADEG_MAJR_CODE_ CONC_3_OTHER_2 Other 2nd Degree Major Concentr ation 3 Label / Drop- down list 4PAPRADEG_MAJR_CODE_ CONC_3Encompass Database NameFriendly NameType Max Field SizePullPushBanner Database Name Selection Code RequiredComments /n 220Banner Advancement Data Load/Extract Handbook |Appendix A - Advancement Connector Data Mappings APRADEG_MAJR_CODE_CONC_4_OTHER_2 Other 2nd Degree Major Concentr ation 4 Label / Drop- down list 4PAPRADEG_MAJR_CODE_ CONC_4APRADEG_MAJR_CODE_ CONC_5_OTHER_2 Other 2nd Degree Major Concentr ation 5 Label / Drop- down list 4PAPRADEG_MAJR_CODE_ CONC_5APRADEG_MAJR_CODE_ CONC_6_OTHER_2 Other 2nd Degree Major Concentr ation 6 Label / Drop- down list 4PAPRADEG_MAJR_CODE_ CONC_6APRADEG_MAJR_CODE_ MINR_1_OTHER_2Other 2nd Degree Minor Label / Drop- down list 4PAPRADEG_MAJR_CODE_ MINR_1 APRADEG_MAJR_CODE_ MINR_2_OTHER_2Other 2nd Degree Minor 2 Label / Drop- down list 4PAPRADEG_MAJR_CODE_ MINR_2 APRADEG_SEQ_NO_ OTHER_3 Other Degree 3 sequence number (hidden) LabelInteger (5) PAPRADEG_SEQ_NO Encompass Database NameFriendly NameType Max Field SizePullPushBanner Database Name Selection Code RequiredComments /n 221Banner Advancement Data Load/Extract Handbook |Appendix A - Advancement Connector Data Mappings APRADEG_DEGC_CODE_OTHER_3 Other 3rd Degree Drop- down list 6PAPRADEG_DEGC_CODEFo ur most recent other degrees are extracted, based on activity date. APRADEG_ACYR_CODE_ OTHER_3 Other 3rd Degree Year Drop- down list 4PAPRADEG_ACYR_CODE APRADEG_SBGI_CODE_ OTHER_3 Other 3rd Degree Institution CodeDrop- down list 6PAPRADEG_SBGI_CODE APRADEG_COLL_CODE_ OTHER_3 Other 3rd Degree School Drop- down list 2PAPRADEG_COLL_CODE APRADEG_CAMP_CODE_ OTHER_3 Other 3rd Degree CampusDrop- down list 3PAPRADEG_CAMP_CODE APRAMAJ_MAJR_CODE_1_OTHER_3 Other 3rd Degree Major 1 Label / Drop-down list 4PAPRAMAJ_MAJR_CODE Six most recent majors for the other degree are extracted, based on activity date. APRAMAJ_MAJR_CODE_ 2_OTHER_3 Other 3rd Degree Major 2 Label / Drop- down list 4PAPRAMAJ_MAJR_CODE Encompass Database NameFriendly NameType Max Field SizePullPushBanner Database Name Selection Code RequiredComments /n 222Banner Advancement Data Load/Extract Handbook |Appendix A - Advancement Connector Data Mappings APRAMAJ_MAJR_CODE_3_OTHER_3 Other 3rd Degree Major 3 Label / Drop- down list 4PAPRAMAJ_MAJR_CODE APRAMAJ_MAJR_CODE_ 4_OTHER_3 Other 3rd Degree Major 4 Label / Drop- down list 4PAPRAMAJ_MAJR_CODE APRAMAJ_MAJR_CODE_ 5_OTHER_3 Other 3rd Degree Major 5 Label / Drop- down list 4PAPRAMAJ_MAJR_CODE APRAMAJ_MAJR_CODE_ 6_OTHER_3 Other 3rd Degree Major 6 Label / Drop- down list 4PAPRAMAJ_MAJR_CODE APRADEG_MAJR_CODE_ CONC_1_OTHER_3 Other 3rd Degree Major Concentr ation 1 Label / Drop- down list 4PAPRADEG_MAJR_CODE_ CONC_1APRADEG_MAJR_CODE_CONC_2_OTHER_3 Other 3rd Degree Major Concentr ation 2 Label / Drop-down list 4PAPRADEG_MAJR_CODE_ CONC_2APRADEG_MAJR_CODE_ CONC_3_OTHER_3 Other 3rd Degree Major Concentr ation 3 Label / Drop- down list 4PAPRADEG_MAJR_CODE_ CONC_3Encompass Database NameFriendly NameType Max Field SizePullPushBanner Database Name Selection Code RequiredComments /n 223Banner Advancement Data Load/Extract Handbook |Appendix A - Advancement Connector Data Mappings APRADEG_MAJR_CODE_CONC_4_OTHER_3 Other 3rd Degree Major Concentr ation 4 Label / Drop- down list 4PAPRADEG_MAJR_CODE_ CONC_4APRADEG_MAJR_CODE_ CONC_5_OTHER_3 Other 3rd Degree Major Concentr ation 5 Label / Drop- down list 4PAPRADEG_MAJR_CODE_ CONC_5APRADEG_MAJR_CODE_ CONC_6_OTHER_3 Other 3rd Degree Major Concentr ation 6 Label / Drop- down list 4PAPRADEG_MAJR_CODE_ CONC_6APRADEG_MAJR_CODE_ MINR_1_OTHER_3Other 3rd Degree Minor Label / Drop- down list 4PAPRADEG_MAJR_CODE_ MINR_1 APRADEG_MAJR_CODE_ MINR_2_OTHER_3Other 3rd Degree Minor 2 Label / Drop- down list 4PAPRADEG_MAJR_CODE_ MINR_2 APRADEG_SEQ_NO_ OTHER_4 Other Degree 4 sequence number (hidden) LabelInteger (5) PAPRADEG_SEQ_NO Encompass Database NameFriendly NameType Max Field SizePullPushBanner Database Name Selection Code RequiredComments /n 224Banner Advancement Data Load/Extract Handbook |Appendix A - Advancement Connector Data Mappings APRADEG_DEGC_CODE_OTHER_4 Other 4th Degree Drop- down list 6PAPRADEG_DEGC_CODEFo ur most recent other degrees are extracted, based on activity date. APRADEG_ACYR_CODE_ OTHER_4 Other 4th Degree Year Drop- down list 4PAPRADEG_ACYR_CODE APRADEG_SBGI_CODE_ OTHER_4 Other 4th Degree Institution CodeDrop- down list 6PAPRADEG_SBGI_CODE APRADEG_COLL_CODE_ OTHER_4 Other 4th Degree School Drop- down list 2PAPRADEG_COLL_CODE APRADEG_CAMP_CODE_ OTHER_4 Other 4th Degree CampusDrop- down list 3PAPRADEG_CAMP_CODE APRAMAJ_MAJR_CODE_1_OTHER_4 Other 4th Degree Major 1 Label / Drop-down list 4PAPRAMAJ_MAJR_CODE Six most recent majors for the other degree are extracted, based on activity date. APRAMAJ_MAJR_CODE_ 2_OTHER_4 Other 4th Degree Major 2 Label / Drop- down list 4PAPRAMAJ_MAJR_CODE Encompass Database NameFriendly NameType Max Field SizePullPushBanner Database Name Selection Code RequiredComments /n 225Banner Advancement Data Load/Extract Handbook |Appendix A - Advancement Connector Data Mappings APRAMAJ_MAJR_CODE_3_OTHER_4 Other 4th Degree Major 3 Label / Drop- down list 4PAPRAMAJ_MAJR_CODE APRAMAJ_MAJR_CODE_ 4_OTHER_4 Other 4th Degree Major 4 Label / Drop- down list 4PAPRAMAJ_MAJR_CODE APRAMAJ_MAJR_CODE_ 5_OTHER_4 Other 4th Degree Major 5 Label / Drop- down list 4PAPRAMAJ_MAJR_CODE APRAMAJ_MAJR_CODE_ 6_OTHER_4 Other 4th Degree Major 6 Label / Drop- down list 4PAPRAMAJ_MAJR_CODE APRADEG_MAJR_CODE_ CONC_1_OTHER_4 Other 4th Degree Major Concentr ation 1 Label / Drop- down list 4PAPRADEG_MAJR_CODE_ CONC_1APRADEG_MAJR_CODE_CONC_2_OTHER_4 Other 4th Degree Major Concentr ation 2 Label / Drop-down list 4PAPRADEG_MAJR_CODE_ CONC_2APRADEG_MAJR_CODE_ CONC_3_OTHER_4 Other 4th Degree Major Concentr ation 3 Label / Drop- down list 4PAPRADEG_MAJR_CODE_ CONC_3Encompass Database NameFriendly NameType Max Field SizePullPushBanner Database Name Selection Code RequiredComments /n 226Banner Advancement Data Load/Extract Handbook |Appendix A - Advancement Connector Data Mappings APRADEG_MAJR_CODE_CONC_4_OTHER_4 Other 4th Degree Major Concentr ation 4 Label / Drop- down list 4PAPRADEG_MAJR_CODE_ CONC_4APRADEG_MAJR_CODE_ CONC_5_OTHER_4 Other 4th Degree Major Concentr ation 5 Label / Drop- down list 4PAPRADEG_MAJR_CODE_ CONC_5APRADEG_MAJR_CODE_ CONC_6_OTHER_4 Other 4th Degree Major Concentr ation 6 Label / Drop- down list 4PAPRADEG_MAJR_CODE_ CONC_6APRADEG_MAJR_CODE_ MINR_1_OTHER_4Other 4th Degree Minor Label / Drop- down list 4PAPRADEG_MAJR_CODE_ MINR_1 APRADEG_MAJR_CODE_ MINR_2_OTHER_4Other 4th Degree Minor 2 Label / Drop- down list 4PAPRADEG_MAJR_CODE_ MINR_2 Encompass Database NameFriendly NameType Max Field SizePullPushBanner Database Name Selection Code RequiredComments /n 227Banner Advancement Data Load/Extract Handbook |Appendix A - Advancement Connector Data Mappings Spouse and family information Encompass Database NameFriendly NameType Max Field SizePullPushBanner Database Name Selection Code RequiredComments SPBPERS_MRTL_CODEMarital Status Drop-down list 1PSPBPERS_MRTL_CODE APRSALU_SALU_CODE_ JOINT Joint Salutation Code (hidden) Label4PAPRSALU_SALU_CODERequired - Indicates which joint salutation code is pushed to Encompass APRSALU_SALUTATION_ JOINT Joint Salutation Text box120PAPRSALU_SALUTATION APRCSPS_MRTL_START_ DATE Date of Marriage Date box8PAPRCSPS_MRTL_START_ DATE SPRIDEN_NTYP_CODE_ MAIDENMaiden Name Type (hidden) Drop- down list 4PSPRIDEN_NTYP_CO DERequired - Indicates which name type code is used to push maiden name information to Encompass SPRIDEN_FIRST_NAME_ MAIDENMaiden First Text box60PSPRIDEN_FIRST_NAME SPRIDEN_MI_MAIDENMaiden Middle Text box60PSPRIDEN_MI /n 228Banner Advancement Data Load/Extract Handbook |Appendix A - Advancement Connector Data Mappings SPRIDEN_LAST_NAME_ MAIDENMaiden Last Text box60PSPR IDEN_LAST_NAME APRCSPS_FIRST_NAMESpouse First Text box60PSPRIDEN_FIRST_NAME APRCSPS_FIRST_NAMEAPRCSPS_MISpouse Middle Text box60PSPRIDEN_MI APRCSPS_MIAPRCSPS_LAST_NAMESpouse Last Text box60PSPR IDEN_LAST_NAMEAPRCSPS_LAST_NAME APRCSPS_SURNAME_ PREFIXSpouse Surname PrefixText box60PSPRIDEN_SURNAME_ PREFIX APRCSPS_SURNAME_PREFIX APRCHLD_FIRST_NAME_ 11st Child First Text box60PSPRIDEN_FIRST_NAME APRCHLD_FIRST_NAME APRCHLD_MI_11st Child Middle Text box60PSPRIDEN_MI APRCHLD_MI APRCHLD_LAST_NAME_11st Child Last Text box60PSPR IDEN_LAST_NAMEAPRCHLD_LAST_NAMEEncompass Database NameFriendly NameType Max Field SizePullPushBanner Database Name Selection Code RequiredComments /n 229Banner Advancement Data Load/Extract Handbook |Appendix A - Advancement Connector Data Mappings APRCHLD_SURNAME_ PREFIX_11st Child Surname PrefixText box60PSPRIDEN_SURNAME_ PREFIX APRCHLD_SURNAME_ PREFIX APRCHLD_FIRST_NAME_ 22nd Child First Text box60PSPRIDEN_FIRST_NAME APRCHLD_FIRST_NAME APRCHLD_MI_22nd Child Middle Text box60PSPRIDEN_MI APRCHLD_MI APRCHLD_LAST_NAME_22nd Child Last Text box60PSPR IDEN_LAST_NAMEAPRCHLD_LAST_NAMEAPRCHLD_SURNAME_ PREFIX_22nd Child Surname PrefixText box60PSPRIDEN_SURNAME_ PREFIX APRCHLD_SURNAME_ PREFIX APRCHLD_FIRST_NAME_ 33rd Child First Text box60PSPRIDEN_FIRST_NAME APRCHLD_FIRST_NAME APRCHLD_MI_33rd Child Middle Text box60PSPRIDEN_MI APRCHLD_MI APRCHLD_LAST_NAME_33rd Child Last Text box60PSPR IDEN_LAST_NAMEAPRCHLD_LAST_NAMEEncompass Database NameFriendly NameType Max Field SizePullPushBanner Database Name Selection Code RequiredComments /n 230Banner Advancement Data Load/Extract Handbook |Appendix A - Advancement Connector Data Mappings APRCHLD_SURNAME_ PREFIX_33rd Child Surname PrefixText box60PSPRIDEN_SURNAME_ PREFIX APRCHLD_SURNAME_ PREFIX APRCHLD_FIRST_NAME_ 44th Child First Text box60PSPRIDEN_FIRST_NAME APRCHLD_FIRST_NAME APRCHLD_MI_44th Child Middle Text box60PSPRIDEN_MI APRCHLD_MI APRCHLD_LAST_NAME_44th Child Last Text box60PSPR IDEN_LAST_NAMEAPRCHLD_LAST_NAMEAPRCHLD_SURNAME_ PREFIX_44th Child Surname PrefixText box60PSPRIDEN_SURNAME_ PREFIX APRCHLD_SURNAME_ PREFIX APRCHLD_FIRST_NAME_ 55th Child First Text box60PSPRIDEN_FIRST_NAME APRCHLD_FIRST_NAME APRCHLD_MI_55th Child Middle Text box60PSPRIDEN_MI APRCHLD_MI APRCHLD_LAST_NAME_55th Child Last Text box60PSPR IDEN_LAST_NAMEAPRCHLD_LAST_NAMEEncompass Database NameFriendly NameType Max Field SizePullPushBanner Database Name Selection Code RequiredComments /n 231Banner Advancement Data Load/Extract Handbook |Appendix A - Advancement Connector Data Mappings Business informationAPRCHLD_SURNAME_ PREFIX_55th Child Surname PrefixText box60PSPRIDEN_SURNAME_ PREFIX APRCHLD_SURNAME_ PREFIX Encompass Database NameFriendly NameType Max Field SizePullPushBanner Database Name Selection Code RequiredComments APREHIS_EMPL_POSITIONJob TitleText box60PPAPREHIS_EMPL_ POSITIONAPREHIS_EMPR_NAMEEmployerText box60PPSPRIDEN_LAST_NAME APREHIS_EMPR_NAMEAPBCONS_DOTT_CODEOccupatio nDrop- down list 4PPAPBCONS_DOTT_CODE APREHIS_JOBC_CODEJob CategoryDrop- down list 3PPAPREHIS_JOBC_CODE Encompass Database NameFriendly NameType Max Field SizePullPushBanner Database Name Selection Code RequiredComments /n 232Banner Advancement Data Load/Extract Handbook |Appendix A - Advancement Connector Data Mappings Business contact information Encompass Database NameFriendly NameType Max Field SizePullPushBanner Database Name Selection Code RequiredComments SPRADDR_STATUS_IND_ BUSBusiness Address Status (hidden) Drop- down list 1PPSPRADDR_STATUS_IND GOREMAL_EMAL_CODE_ BUSBusiness E-mail CodeDrop- down list 4PPGOREMAL_EMAL_CODERequired - Indicates which e- mail type is used to push business e- mail addresses to Encompass GOREMAL_EMAIL_ ADDRESS_BUSBusiness E-mailText box128PPGOREMAL_EMAIL_ ADDRESS/n 233Banner Advancement Data Load/Extract Handbook |Appendix A - Advancement Connector Data Mappings SPRADDR_ATYP_CODE_ BUSBusiness Address Type Drop- down list 2PPSPRADDR_ATYP_CODEOptional If blank, the business address information associated with the current active primary employment record is used for the push to Encompass. If a selection code is entered, the current, active. address type is used for the push to Encompass. SPRADDR_STREET_ LINE1_BUS Business Address 1 Text box75PPSPRADDR_STREET_ LINE1SPRADDR_STREET_ LINE2_BUS Business Address 2 Text box75PPSPRADDR_STREET_ LINE2SPRADDR_STREET_ LINE3_BUS Business Address 3 Text box75PPSPRADDR_STREET_ LINE3SPRADDR_STREET_ LINE4_BUS Business Address 4 Text box75PPSPRADDR_STREET_ LINE4Encompass Database NameFriendly NameType Max Field SizePullPushBanner Database Name Selection Code RequiredComments /n 234Banner Advancement Data Load/Extract Handbook |Appendix A - Advancement Connector Data Mappings SPRADDR_HOUSE_NUMBER_BUS Business House NumberText box10PPSPRADDR_HOUSE_ NUMBER SPRADDR_CITY_BUSBusiness CityText box50PPSPRADDR_CITY SPRADDR_STAT_CODE_ BUSBusiness State Drop- down list 3PPSPRADDR_STAT_CODE SPRADDR_ZIP_BUSBusiness ZipText box30PPSPRADDR_ZIP SPRADDR_NATN_CODE_ BUSBusiness CountryDrop- down list 5PPSPRADDR_NATN_CODE SPRTELE_TELE_CODE_ BUSBusiness Phone Type Drop- down list 4PPSPRTELE_TELE_CODEOptional If blank, the phone information is tied to the phone number associated with the business address, if there is one. SPRTELE_ATYP_CODE_ BUSBusiness Phone Address Type (hidden) Text box2PPSPRTELE_ATYP_CODE Encompass Database NameFriendly NameType Max Field SizePullPushBanner Database Name Selection Code RequiredComments /n 235Banner Advancement Data Load/Extract Handbook |Appendix A - Advancement Connector Data Mappings SPRTELE_ADDR_ SEQNO_BUSBusiness Phone Address Sequence Number (hidden) Text box2PPSPRTELE_ADDR_SEQNO SPRTELE_CTRY_CODE_ PHONE_ BUSBusiness Phone Country CodeText box4PPSPRTELE_CTRY_CODE_ PHONE SPRTELE_PHONE_AREA_ BUSBusiness Phone Area CodeText box6PPSPRTELE_PHONE_AREA SPRTELE_PHONE_ NUMBER_BUS Business Phone NumberText box12PPSPRTELE_PHONE_ NUMBER SPRTELE_PHONE_EXT_ BUSBusiness Phone ExtensionText box10PPSPRTELE_PHONE_EXT SPRTELE_TELE_CODE_ FAX_BUS Business Fax Phone Type (hidden) Drop- down list 4PPSPRTELE_TELE_CODERequired - Indicates which phone type is used to push business fax information to Encompass Encompass Database NameFriendly NameType Max Field SizePullPushBanner Database Name Selection Code RequiredComments /n 236Banner Advancement Data Load/Extract Handbook |Appendix A - Advancement Connector Data Mappings SPRTELE_ATYP_CODE_ FAX_BUS Business Fax Phone Address Type (hidden) Text box2PPSPRTELE_ATYP_CODE SPRTELE_ADDR_ SEQNO_FAX_BUS Business Fax Phone Address Sequence Number (hidden) Text box2PPSPRTELE_ADDR_SEQNO SPRTELE_CTRY_CODE_ FAX_BUS Business Fax Country CodeText box4PPSPRTELE_CTRY_CODE_ PHONE SPRTELE_FAX_AREA_ BUSBusiness Fax Area CodeText box6PPSPRTELE_PHONE_AREA SPRTELE_FAX_NUMBER_ BUSBusiness Fax NumberText box12PPSPRTELE_PHONE_ NUMBER SPRTELE_FAX_EXT_BUSBusiness Fax ExtensionText box10PPSPRTELE_PHONE_EXT Encompass Database NameFriendly NameType Max Field SizePullPushBanner Database Name Selection Code RequiredComments /n 237Banner Advancement Data Load/Extract Handbook |Appendix A - Advancement Connector Data Mappings Activities and honorsEncompass Database NameFriendly NameType Max Field SizePullPushBanner Database Name Selection Code RequiredComments APRIGRP_IGRP_CODE_1Interests Code 1Drop-down list 10PAPRIGRP_IGRP_CODESix most recent interest codes are extracted, based on activity date. APRIGRP_IGRP_CODE_2Interests Code 2Drop- down list 10PAPRIGRP_IGRP_CODE APRIGRP_IGRP_CODE_3Interests Code 3Drop- down list 10PAPRIGRP_IGRP_CODE APRIGRP_IGRP_CODE_4Interests Code 4Drop- down list 10PAPRIGRP_IGRP_CODE APRIGRP_IGRP_CODE_5Interests Code 5Drop- down list 10PAPRIGRP_IGRP_CODE APRIGRP_IGRP_CODE_6Interests Code 6Drop-down list 10PAPRIGRP_IGRP_CODE APRACTY_ACTC_CODE_ 1Activity Code 1Drop- down list 8PAPRACTY_ACTC_CODE Six most recent activity codes are extracted, based on activity date. APRACLD_LEAD_CODE_1Activity Participati on Code 1 Drop- down list 5PAPRACLD_LEAD_CODE /n 238Banner Advancement Data Load/Extract Handbook |Appendix A - Advancement Connector Data Mappings APRACTY_ACTC_CODE_ 2Activity Code 2Drop- down list 8PAPRACTY_ACTC_CODE APRACLD_LEAD_CODE_2Activity Participati on Code 2 Drop- down list 5PAPRACLD_LEAD_CODE APRACTY_ACTC_CODE_ 3Activity Code 3Drop- down list 8PAPRACTY_ACTC_CODE APRACLD_LEAD_CODE_3Activity Participati on Code 3 Drop- down list 5PAPRACLD_LEAD_CODE APRACTY_ACTC_CODE_ 4Activity Code 4Drop- down list 8PAPRACTY_ACTC_CODE APRACLD_LEAD_CODE_4Activity Participati on Code 4 Drop- down list 5PAPRACLD_LEAD_CODE APRACTY_ACTC_CODE_ 5Activity Code 5Drop- down list 8PAPRACTY_ACTC_CODE APRACLD_LEAD_CODE_5Activity Participati on Code 5 Drop- down list 5PAPRACLD_LEAD_CODE APRACTY_ACTC_CODE_ 6Activity Code 6Drop- down list 8PAPRACTY_ACTC_CODE APRACLD_LEAD_CODE_6Activity Participati on Code 6 Drop- down list 5PAPRACLD_LEAD_CODE Encompass Database NameFriendly NameType Max Field SizePullPushBanner Database Name Selection Code RequiredComments /n 239Banner Advancement Data Load/Extract Handbook |Appendix A - Advancement Connector Data Mappings Admin onlyThe following data elements can be viewed by administrators only. These data elements are hidden for other users. .Encompass Database NameFriendly NameType Max Field SizePullPushBanner Database Name Selection Code RequiredComments SPRIDEN_PIDMConstituent PIDMText box8PPSPRIDEN_PIDM SPRIDEN_IDBanner IDText box8 PSPRIDEN_ID Process checks SPRIDEN_ACTIVITY_DATE in active SPRIDEN record. If there are changes to the active SPRIDEN record, which fall within the time frame specified in the push, those changes are sent to Encompass. SPRIDEN_ID is not supported by the pull process. Allows institutions to query data in Encompass, in lieu of the PIDM. If a constituent has multiple SPRIDEN record changes, only the changes to the active SPRIDEN record are pushed to Encompass. /n 240Banner Advancement Data Load/Extract Handbook |Appendix A - Advancement Connector Data Mappings SPBPERS_DEAD_INDDeceasedDrop- down list1PSPBPERS_DEAD_INDOptional If blank, all living and deceased constituents are included in the push. If set to N, only living constituents are included. If set to Y, only deceased constituents are included. Encompass Database NameFriendly NameType Max Field SizePullPushBanner Database Name Selection Code RequiredComments /n

Banner_Advancement_Data_Load_Extract_Handbook_8.8.pdf (1.7 MB)
Helpful?

Related Articles: