1. health and fitness
2. disease
3. aids and hiv

www.sksoft.com
eBanking Suite
for
Microsoft Dynamics AX 2012
Updated: December 24, 2014
Page 1
Table of Contents
Contents
Table of Contents.......................................................................................................................................... 2
A. Overview ................................................................................................................................................... 5
Outline ...................................................................................................................................................... 5
Pre-Requisites ........................................................................................................................................... 5
Note on Custom Positive Pay formats ...................................................................................................... 6
Note on Custom APEFT Plus! And AREFT Plus! formats ........................................................................... 6
B. Installation/Setup ..................................................................................................................................... 6
Overview ................................................................................................................................................... 6
Copy Files to your System ......................................................................................................................... 7
Server Install ............................................................................................................................................. 7
Upgrading from an AX2009 installation of eBanking ............................................................................ 7
Install the SKS eBanking Module on a New AX 2012 Install (eBanking is being installed at the same
time as AX 2012 is first being installed) ................................................................................................ 7
Adding the SKS eBanking Module to an Existing AX 2012 Install (AX2012 was previously installed –
this is used for both a new install of eBanking and/or an eBanking Upgrade)..................................... 8
Upgrading AX from one version to another when eBanking was already installed at the pre-upgrade
level (e.g. RTM to FP or FP to FP-CU3 or to R2, R3 etc.) ..................................................................... 14
Client Install (must be done on EACH client workstation, in Citrix/TermServer environments each of
those machines is acting as an AX client and therefore needs this client install) .................................. 15
Install the client assembly ................................................................................................................... 15
Help Install .............................................................................................................................................. 15
Import Positive Pay File Formats (only if using Positive Pay) ................................................................. 16
Import EFT Plus! Formats (only if using APEFT or AREFT Plus!) .............................................................. 16
Import EFT Plus! EDI820 Layouts (only if using APEFT Plus! with CTX) .................................................. 16
Setup Security/Permissions .................................................................................................................... 16
Organization Hierarchies ........................................................................................................................ 16
Virtual Companies ................................................................................................................................... 16
C. Unlocking Keys ........................................................................................................................................ 17
Updated: December 24, 2014
Page 2
eBanking Suite parameters ..................................................................................................................... 17
AX License Information ........................................................................................................................... 18
E. Un-Install ................................................................................................................................................. 19
Introduction ............................................................................................................................................ 19
Remove the eBanking Suite AX Objects (SKS eBanking Model) ............................................................. 19
Uninstall the eBanking Help files ............................................................................................................ 19
Remove the Client Assembly .................................................................................................................. 19
Remove the EFT+ email templates (v5 and later) ................................................................................... 19
F. Backup & Restore .................................................................................................................................... 20
G. Revision/Enhancement History .............................................................................................................. 20
Appendix A – Setting up eBanking Security ................................................................................................ 47
Security layers ......................................................................................................................................... 47
System tools ............................................................................................................................................ 47
Setting up eBanking security................................................................................................................... 47
Duties ...................................................................................................................................................... 47
Duties by module: ............................................................................................................................... 47
Roles and duties: ..................................................................................................................................... 48
The duties and roles assigned by eBanking: ....................................................................................... 48
Positive Pay ......................................................................................................................................... 48
Electronic Bank Reconciliation ............................................................................................................ 48
Lockbox (AR eSettlement w/Lockbox) ................................................................................................ 49
APEFT Plus!.......................................................................................................................................... 49
AREFT Plus! ......................................................................................................................................... 50
Privileges ................................................................................................................................................. 50
Appendix B – Organization hierarchies in eBanking ................................................................................... 51
Overview ................................................................................................................................................. 51
eBanking support .................................................................................................................................... 51
Positive Pay ......................................................................................................................................... 52
Electronic Bank Reconciliation ............................................................................................................ 52
AR eSettlement w/Lockbox, APEFT Plus!, AREFT Plus! ....................................................................... 52
Setting up organizations ......................................................................................................................... 52
Security ................................................................................................................................................... 53
Updated: December 24, 2014
Page 3
Setup data ............................................................................................................................................... 53
Appendix C – Virtual Company Setup ......................................................................................................... 54
Positive Pay ......................................................................................................................................... 54
Electronic Bank Reconciliation ............................................................................................................ 54
AR eSettlement w/Lockbox ................................................................................................................. 55
APEFT Plus! & AREFT Plus! .................................................................................................................. 55
Notes to existing customers – switching to virtual companies .......................................................... 55
Updated: December 24, 2014
Page 4
A. Overview
Outline
This guide outlines how to install the features of the eBanking Suite into the Microsoft Dynamics
AX 2012 application. Models are included for RTM, FP, R2 and R3 (see details below).
The eBanking Suite consists of five modules:
 Positive Pay
 Electronic Bank Reconciliation
 AR eSettlement w/Lockbox
 AP EFT Plus!
 AR EFT Plus! (v6 or greater only)
Contact information for SK Global Software, LLC
Main Number: (301)963-7300 (North Bethesda, MD)
AX Tech Support:
x114 [email protected]
Registration Keys:
x115 [email protected]
Sales:
x117 [email protected]
Pre-Requisites
The following lists the pre-requisites required to successfully install the eBanking Suite:
 Microsoft Dynamics AX 2012 RTM, FP-CU3, FP-CU4, FP-CU5, R2, R2-CU6, R2-CU7, R3 and R3CU8.
 Windows MorphX Development Suite license to allow synchronization of the AOT objects.
 For hardware or system requirements, please refer to the Microsoft Dynamics AX


requirements.
Developer/Implementer resource - Since the eBanking Suite is tightly integrated with the
GL, A/P, A/R and Bank modules of AX our code requires merging with AX and other
ISV/customized code. This needs to be done by an experienced developer/implementer
that is familiar with the AOT, Project developer workspaces and compare, compile
features. SK has staff available to provide this install/merge service when required (at our
standard billing rate).
AX Module Requirements
eBanking module
AX module(s) required
Positive Pay
Bank, Accounts Payable or Payroll
eBank Reconciliation
Bank, General Ledger
AR eSettlement w/Lockbox
Bank, Accounts Receivable
AP EFT Plus!
Bank, Accounts Payable
AR EFT Plus!
Bank, Accounts Receivable
Updated: December 24, 2014
Page 5
* If you are using Business Ready Licensing, the required Bank, Accounts Payable, Accounts
Receivable and General Ledger modules are included in Business Essentials as part of the
Financials I license.
Note on Custom Positive Pay formats
The formats we provide (at no charge) are designed per the bank’s specification. Our goal is to build
up a library that can be shared with the whole AX community. When a format request is site or
implementation specific we can provide a quote to create that customized format.
Note on Custom APEFT Plus! And AREFT Plus! formats
Unlike Positive Pay, EFT+ formats are much more complex to develop. If a particular format is
required and does not exist in our library we will develop it for a fixed amount. This should have
been identified in the sales process. If not please contact SK sales ([email protected]) to start the
process of reviewing the file specification and determining pricing. We generally can deliver a new
format within 30 days of obtaining the file specification.
B. Installation/Setup
Overview
The eBanking Suite installation includes both a client and server install. For the server install,
the instructions vary based on whether this is an initial install, adding on to an existing install or
upgrading from an AX 2009 installation with the eBanking Suite already installed.
Install Overview
 Copy files to your system
 Server Install
o Install the server assembly
o Install pre-upgrade code on source system (if upgrading from an AX 2009
install of eBanking)
o Install the SKS eBanking Model (RTM, FP-CU3, FP-CU4, FP-CU5, R2, R2-CU6,
R2-CU7, R3 or R3-CU8)
o Import File Formats (for Positive Pay and APEFT/AREFT Plus!)
 Client Install (each client installation)
o Install the client assembly
 Help Install
o Install the AX 2012 help
 Setup Security/Permissions
 Enter unlocking keys
If adding a New Positive Pay format – see the section at the bottom of this document
Updated: December 24, 2014
Page 6
Copy Files to your System
1. Double click the installation file AXeBanking-7-x-x-6x.exe.
2. Unzip to folder C:\SKS_eBankingInstall (or any other folder of your choice)
3. Click Unzip – the following files will be copied to your system:
File
Folder
Installation Docs
C:\SKS_eBankingInstall
Client Files
C:\SKS_eBankingInstall\Client
Server Files
C:\SKS_eBankingInstall\Server
Formats
C:\SKS_eBankingInstall\Formats
EDI820Layouts
EFT Addenda (US federal tax payments)
Holidays (banking holidays)
EFT+ formats
Positive Pay formats
Lockbox formats
Help Files
C:\SKS_eBankingInstall\Help
Sample Files
C:\SKS_eBankingInstall\Sample Files
eBankRec
Lockbox
Utilities (ftp scripts, batch files)
Server Install
Note: All eBanking Suite AOT objects are prefixed with SKS_ and then a module prefix followed by an
underscore (ex: SKS_PP_ or SKS_BR_. Some of the original Positive Pay objects were leveraged by other
eBanking modules and the objects were not renamed. Since objects were not renamed, some objects
that are used by multiple eBanking modules are prefixed with SKS_PP_ (ex: SKS_PP_Setup is used by all
modules).
Upgrading from an AX2009 installation of eBanking
Please contact AX support ([email protected]) before proceeding.
Install the SKS eBanking Module on a New AX 2012 Install (eBanking is being installed at the
same time as AX 2012 is first being installed)
NOTE: The order of these steps is CRITICAL!
1. Client files - Copy SKS.Common.dll, SKS.Common.R2.dll or SKS.Common.R3.dll from the
Client folder of your SKS_eBanking install to this folder on your server: C:\Program Files
(x86)\Microsoft Dynamics AX\60\Client\Bin directory. SKS.Common.dll is used with AX
2012 RTM, FP-CUx. SKS.Common.R2.dll is used with AX 2012 R2, R2-CUx.
SKS.Commond.R3.dll is used with AX 2012 R3-CUx.
Updated: December 24, 2014
Page 7
2. Server files - Copy SKS.Common.dll, SKS.Common.R2.dll or SKS.Common.R3.dll from the
Server folder of your SKS_eBanking install to this folder on your server: C:\Program
Files\Microsoft Dynamics AX\60\Server\<AXServerName>\Bin directory.
3. Follow the instructions in the Microsoft Dynamics AX 2012 Installation Guide in the section
titled “Create a shared directory for installation”.
4. Make a new subdirectory named "SKS_EB" in the model subdirectory of your installation
folders and copy the SKS eBanking Models to that directory (the model files are found in the
C:\SKS_eBankingInstall\Server folder).
5. Continue with the remaining steps in the install guide, making sure to select the SKS model
and additionally select either the SKSAXRTM, SKSAXFPCU3, SKSAXFPCU4, SKSAXFPCU5,
SKSAXR2, SKSAXR2CU6, SKSAXR2CU7, SKAXR3 or SKAXR3CU8 model on the "Select
additional models page" of the installation. Select the appropriate additional model:
a.
b.
c.
d.
e.
f.
g.
h.
i.
SKSAXRTM - if you are installing on Microsoft Dynamics AX 2012 RTM
SKSAXFPCU3 - if you are installing on Microsoft Dynamics AX 2012 FP-CU3
SKSAXFPCU4 - if you are installing on Microsoft Dynamics AX 2012 FP-CU4
SKSAXFPCU5 - if you are installing on Microsoft Dynamics AX 2012 FP-CU5
SKSAXR2 – if you are installing on Microsoft Dynamics AX 2012 R2
SKSAXR2CU6 – if you are installing on Microsoft Dynamics AX 2012 R2-CU6
SKSAXR2CU7 – if you are installing on Microsoft Dynamics AX 2012 R2-CU7
SKSAXR3 – if you are installing on Microsoft Dynamics AX 2012 R3
SKSAXR3CU8 – if you are installing on Microsoft Dynamics AX 2012 R3-CU8
Also, it is important to complete the "Compile Application" and "Generate CIL" steps.
These are labeled optional in the checklist but will cause failures if not completed.
6. At the point where the AX 2012 client is launched for the first time, the instructions in the
Client Install section of this guide must first be executed on the machine launching the
client.
Compile errors will occur if this step is not performed!
Adding the SKS eBanking Module to an Existing AX 2012 Install (AX2012 was previously
installed – this is used for both a new install of eBanking and/or an eBanking Upgrade)
NOTE: The order of these steps is CRITICAL!
If upgrading from a prior version of eBanking and upgrading to a different Microsoft Dynamics AX
version:
1.
2.
3.
4.
5.
6.
Before you install the new SKS eBanking models, open the AOT.
In the AOT go to Data Dictionary > Base Enums
Locate HierarchyPurpose
Right click SKS_PPControl and choose properties
Note the EnumValue.
Right click SKS_BRControl and choose properties.
Updated: December 24, 2014
Page 8
7. Note the EnumValue.
8. These values will be used later.
Now, for all installation cases:
1. Client files - Copy SKS.Common.dll (for RTM, FP-CUx) or SKS.Common.R2.dll (for R2, R2-CUx) or
SKS.Common.R3.dll (for R3, R3-CUx) from the Client folder of your SKS_eBanking install to this
folder on your server: C:\Program Files (x86)\Microsoft Dynamics AX\60\Client\Bin directory.
2. Server files - Copy SKS.Common.dll, SKS.Common.R2.dll or SKS.Common.R3.dll from the Server
folder of your SKS_eBanking install to this folder on your server: C:\Program Files\Microsoft
Dynamics AX\60\Server\<AXServerName>\Bin directory.
3. Open a command prompt as Administrator.
4. AXUtil - Change Directory: CD to C:\Program Files\Microsoft Dynamics
AX\60\ManagementUtilities.
5. Run the following commands (your path to the .AXModel file may be different – depending on
where the SK files were installed). Enter “Y” to the prompt “Are you sure you want to overwrite
this or these model(s)?” if you are upgrading eBanking. This process imports the eBanking Suite
code.
Note: There are multiple models that get installed. Each model must be separated by a
comma without spaces before or after.
New eBanking Installation (if upgrading eBanking, see below)
a. If you are on AX 2012 RTM (and any updates before Feature Pack) run this command.
This installs the AX RTM objects that eBanking modifies.
Axutil import
/file:C:\SKS_eBankingInstall\Server\SKS.AXModel,C:\SKS_eBankingInstall\Server\SKSAX
RTM.AXModel /conflict:push
b. If you are on AX 2012 FP-CU3 (and any updates prior to R2) run this command. This
installs the AX Feature Pack objects that eBanking modifies.
Axutil import
/file:C:\SKS_eBankingInstall\Server\SKS.AXModel,C:\SKS_eBankingInstall\Server\SKSAXF
PCU3.AXModel /conflict:push
c. If you are on AX 2012 FP-CU4 (and any updates prior to R2) run this command. This
installs the AX Feature Pack objects that eBanking modifies.
Axutil import
/file:C:\SKS_eBankingInstall\Server\SKS.AXModel,C:\SKS_eBankingInstall\Server\SKSAXF
PCU4.AXModel /conflict:push
Updated: December 24, 2014
Page 9
d. If you are on AX 2012 FP-CU5 (and any updates prior to R2) run this command. This
installs the AX Feature Pack objects that eBanking modifies.
Axutil import
/file:C:\SKS_eBankingInstall\Server\SKS.AXModel,C:\SKS_eBankingInstall\Server\SKSAXF
PCU5.AXModel /conflict:push
e. If you are on AX 2012 R2 run this command. This installs the AX R2 objects that
eBanking modifies.
Axutil import
/file:C:\SKS_eBankingInstall\Server\SKS.AXModel,C:\SKS_eBankingInstall\Server\SKSAX
R2.AXModel /conflict:push
f.
If you are on AX 2012 R2-CU6 run this command. This installs the AX R2 objects that
eBanking modifies.
Axutil import
/file:C:\SKS_eBankingInstall\Server\SKS.AXModel,C:\SKS_eBankingInstall\Server\SKSAX
R2CU6.AXModel /conflict:push
g. If you are on AX 2012 R2-CU7 run this command. This installs the AX R2 objects that
eBanking modifies.
Axutil import
/file:C:\SKS_eBankingInstall\Server\SKS.AXModel,C:\SKS_eBankingInstall\Server\SKSAX
R2CU7.AXModel /conflict:push
h. If you are on AX 2012 R3 run this command. This installs the AX R3 objects that
eBanking modifies.
Axutil import
/file:C:\SKS_eBankingInstall\Server\SKS.AXModel,C:\SKS_eBankingInstall\Server\SKSAX
R3.AXModel /conflict:push
i.
If you are on AX 2012 R3-CU8 run this command. This installs the AX R3 objects that
eBanking modifies.
Axutil import
/file:C:\SKS_eBankingInstall\Server\SKS.AXModel,C:\SKS_eBankingInstall\Server\SKSAX
R3CU8.AXModel /conflict:push
Updated: December 24, 2014
Page 10
Upgrading an eBanking Installation
Before beginning the upgrade, go to eBanking Suite > eBanking Parameters >
Registration tab and note the eBanking version. It may be used below.
First determine the SKS models installed. Run the following command:
Axutil list
Add any SKS models returned from the axutil list command to the commands below
using the /replace switch in Axutil. (E.g. if Axutl list shows SKS and SKSAXRTM models
installed, add /replace:SKS,SKSAXRTM)
a. If you are on AX 2012 RTM (and any updates before Feature Pack) and you are
upgrading an existing eBanking installation run this command after updating the
/replace switch. This installs the AX RTM objects that eBanking modifies.
Axutil import
/file:C:\SKS_eBankingInstall\Server\SKS.AXModel,C:\SKS_eBankingInstall\Server\SKSAX
RTM.AXModel /conflict:push /replace:[comma separated list of SKS models installed]
b. If you are on AX 2012 FP-CU3 (and any updates prior to R2) and you are upgrading an
existing eBanking installation import this additional model. This installs the AX Feature
Pack objects that eBanking modifies.
Axutil import
/file:C:\SKS_eBankingInstall\Server\SKS.AXModel,C:\SKS_eBankingInstall\Server\SKSAXF
PCU3.AXModel /conflict:push /replace:[comma separated list of SKS models installed]
c. If you are on AX 2012 FP-CU4 (and any updates prior to R2) and you are upgrading an
existing eBanking installation import this additional model. This installs the AX Feature
Pack objects that eBanking modifies.
Axutil import
/file:C:\SKS_eBankingInstall\Server\SKS.AXModel,C:\SKS_eBankingInstall\Server\SKSAXF
PCU4.AXModel /conflict:push /replace:[comma separated list of SKS models installed]
d. If you are on AX 2012 FP-CU5 (and any updates prior to R2) and you are upgrading an
existing eBanking installation import this additional model. This installs the AX Feature
Pack objects that eBanking modifies.
Axutil import
/file:C:\SKS_eBankingInstall\Server\SKS.AXModel,C:\SKS_eBankingInstall\Server\SKSAXF
PCU5.AXModel /conflict:push /replace:[comma separated list of SKS models installed]
Updated: December 24, 2014
Page 11
e. If you are on AX 2012 R2 and you are upgrading an existing eBanking installation import
this additional model. This installs the AX R2 objects that eBanking modifies.
Axutil import
/file:C:\SKS_eBankingInstall\Server\SKS.AXModel,C:\SKS_eBankingInstall\Server\SKSAX
R2.AXModel /conflict:push /replace:[comma separated list of SKS models installed]
f.
If you are on AX 2012 R2-CU6 and you are upgrading an existing eBanking installation
import this additional model. This installs the AX R2 objects that eBanking modifies.
Axutil import
/file:C:\SKS_eBankingInstall\Server\SKS.AXModel,C:\SKS_eBankingInstall\Server\SKSAX
R2CU6.AXModel /conflict:push /replace:[comma separated list of SKS models installed]
g. If you are on AX 2012 R2-CU7 and you are upgrading an existing eBanking installation
import this additional model. This installs the AX R2 objects that eBanking modifies.
Axutil import
/file:C:\SKS_eBankingInstall\Server\SKS.AXModel,C:\SKS_eBankingInstall\Server\SKSAX
R2CU7.AXModel /conflict:push /replace:[comma separated list of SKS models installed]
h. If you are on AX 2012 R3 and you are upgrading an existing eBanking installation import
this additional model. This installs the AX R3 objects that eBanking modifies.
Axutil import
/file:C:\SKS_eBankingInstall\Server\SKS.AXModel,C:\SKS_eBankingInstall\Server\SKSAX
R3.AXModel /conflict:push /replace:[comma separated list of SKS models installed]
i.
If you are on AX 2012 R3-CU8 and you are upgrading an existing eBanking installation
import this additional model. This installs the AX R3 objects that eBanking modifies.
Axutil import
/file:C:\SKS_eBankingInstall\Server\SKS.AXModel,C:\SKS_eBankingInstall\Server\SKSAX
R3CU8.AXModel /conflict:push /replace:[comma separated list of SKS models installed]
6. Enter “Y” to the prompt “Are you sure you want to overwrite this or these model(s)?” if you are
upgrading eBanking. This process imports the eBanking Suite code.
7. You will receive the message “Because of the changes made to the model store, it is highly
recommended to restart the AOS, run appropriate scripts, and compile and synchronize the
application. Not doing that may cause runtime errors and loss of data.” when the Axutil process
completes. You will be returned to the command prompt.
8. Enter “Exit” to close the command prompt.
Updated: December 24, 2014
Page 12
9. Re-start the AOS (this allows AX to recognize the model update).
10. Open AX 2012.
11. You will be prompted that the model store has been modified. Choose the Skip option and click
the OK button.
12. Open the SKS_eBanking_Suite project. Review the objects in the AX node and determine if
merging is necessary on your system due to Cumulative updates or customizations.
a) Right-click each object in the AX node and choose Compare.
b) eBanking is installed on the ISV layer. You’ll need to compare the isv layer object to the
other layers of your installation. These layers are typically sys, syp or fpk depending on
what version of AX you are running.
c) Click the Compare button.
d) The lower part of the screen displays differences between the two layers. Click each
node on the left side and review the code that displays on the right side. Use the left
and right arrows to add or remove changes.
e) After changes are made close the compare window.
f) Right-click the object and choose Compile.
13. Starting with eBanking v7.3, the SKS Advanced Bank Reconciliation Server is no longer used (an
AX batch job is now used to import Bank statement files). The service can be uninstalled from
Programs and Features (SKS Advanced Bank Reconciliation Service for Microsoft Dynamics AX)
14. If upgrading from an eBanking build prior to version 5.3.0.6x:
Method changes to table objects were moved to event handlers. If eBanking was
previously installed and a merge was performed on a layer above the ISV layer, some
merged code may need to be removed. eBanking specific code was removed from the
table methods and replaced with event handlers. Please review the following table
objects and remove previously merged code if necessary: BankChequeTable, CustTrans,
LedgerJournalTable, LedgerJournalTrans and WMSBillOfLadingOrder.
15. If upgrading from a prior version of eBanking and upgrading to a different Microsoft Dynamics
AX version:
a)
b)
c)
d)
In the AOT go to Data Dictionary > Base Enums
Locate HierarchyPurpose
Right click SKS_PPControl and choose properties
If the EnumValue is different than the EnumValue noted prior to installation, you will
need to follow the directions below to modify the code. The code will upgrade any data
associated with the prior EnumValue to the new EnumValue.
e) Right click SKS_BRControl and choose properties.
f) If the EnumValue is different than the EnumValue noted prior to installation, you will
need to follow the directions below to modify the code. The code will upgrade any data
associated with the prior EnumValue to the new EnumValue.
Updated: December 24, 2014
Page 13
To modify the code:
a) In the AOT go to Classes > OMHierarchyPurposeTableClass.
b) Open the addSKS_PPControlPurpose class and change the 9 to the value you noted
previously.
c) Open the addSKS_BRControlPurpose class and change the 10 to the value you noted
previously.
d) After the eBanking installation is completed, open the Organization administration >
Setup > Organization > Organization hierarchy purpose screen. Review the eBanking
Positive Pay and eBanking Bank Reconciliation purposes and verify the correct
hierarchies are still assigned.
16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
Click the Windows icon on the AX 2012 toolbar and then click New Development Workspace.
Compile - Right-click the AOT and choose Compile.
Close the Compiler output window.
Click Build from the Microsoft Dynamics AX toolbar in the development workspace.
Full CIL - Click Generate Full CIL.
Click Yes to message “Would you like to generate CIL from all X++ code? Full CIL generate can
take a long time to complete.” (this can be many hours) An Infolog window appears with the
message “The full CIL generation from X++ is done.” when the Generate Full CIL process
completes.
Close the Infolog window.
Synchronize - Right-click the Data Dictionary and choose Synchronize.
Close the AOT.
Close the Compiler output and the development workspace windows.
Upgrading AX from one version to another when eBanking was already installed at the preupgrade level (e.g. RTM to FP or FP to FP-CU3 or to R2, R3 etc.)
If you encounter merge issues during the AX upgrade process (that involve eBanking objects) you can
either resolve those issues manually or use the above procedures to install the correct eBanking model
for the new AX version.
Updated: December 24, 2014
Page 14
Client Install (must be done on EACH client workstation, in Citrix/TermServer
environments each of those machines is acting as an AX client and therefore
needs this client install)
Install the client assembly
From your installation folder (Client) copy the file as below:
(your folder path might be slightly different depending on the install location)
File
Folder
SKS.Common.dll or
SKS.Common.R2.dll C:\Program Files (x86)\Microsoft Dynamics AX\60\Client\Bin
SKS.Common.R3.dll
* SKS.Common.dll is used with AX 2012 RTM or AX 2012 FP-xx. SKS.Common.R2.dll is used
with AX 2012 R2, R2-CUx. SKS.Common.R3.dll is used with AX 2012 R3, R3-CUx.
Help Install
The help install file (.msi) is located in the C:\SKS_eBankingInstall\Help folder. To install the help
files to the AX Help Server, run the SKSeBanking-AX2012Help-x-x-x.msi on the IIS server where
the AX help has been installed.
By default, it will be installed to the following folder (please modify this in the .msi process if it
does not match your Help Server install location):
C:\inetpub\wwwroot\DynamicsAX6HelpServer\Content
These folders will have been created/updated beneath the "Content" folder:
SKSoft
\EN-US
\UserDocResources
has the TableOfContents.xml & readme.txt
\UserDocumentation
has all the help topics
Note that these new updates need to refresh the Windows Indexing system Indexing progress
can been noted via the Control Panel > Indexing Options. The "Content" folder (and its child
folders - see above) should already be setup as an indexing location.
For the eBanking Suite help topics to appear the AX Help Server web.config file needs to be
updated – it is located in the C:\inetpub\wwwroot\DynamicsAX6HelpServer folder.
Find the <publishers> tag section... and add the SKSoft publisherId entry (exactly per below) if
not already there (the "Microsoft" tag should already be there)
<publishers>
<add publisherId="Microsoft" name="Microsoft" />
<add publisherId="SKSoft" name="Sandler-Kahne Software" />
</publishers>
Updated: December 24, 2014
Page 15
Once this is updated and the Windows indexing process has completed, the eBanking Suite help
should be available.
Import Positive Pay File Formats (only if using Positive Pay)
1.
2.
3.
4.
5.
6.
Open Microsoft Dynamics AX 2012.
Go to eBanking Suite -> Setup -> eBanking Suite parameters -> Modules tab.
In the Positive Pay group, click the Import File Formats button.
Enter or browse to C:\SKS_eBankingInstall\Formats\SKS_PP_FileFormats.csv.
Click OK.
The data will be imported. An Infolog message will display showing the number of records
Added, Updated and Deleted.
7. Click Close on the message.
Import EFT Plus! Formats (only if using APEFT or AREFT Plus!)
1.
2.
3.
4.
5.
6.
Open Microsoft Dynamics AX 2012.
Go to eBanking Suite -> Setup -> eBanking Suite parameters -> Modules tab.
In the EFT+ group, click the Import EFT+ File Formats… button.
Enter or browse to C:\SKS_eBankingInstall\Formats\SKS_EFT_FileFormats.csv.
Click OK.
The data will be imported. An Infolog message will display showing the number of records
added, updated and deleted.
7. Click Close on the message.
Import EFT Plus! EDI820 Layouts (only if using APEFT Plus! with CTX)
1.
2.
3.
4.
5.
6.
7.
Open Microsoft Dynamics AX 2012.
Go to eBanking Suite -> File formats -> EFT+ file formats -> Setup EDI 820.
Click the Import layout button.
Enter or browse to the C:\SKS_eBankingInstall\Formats\EDI820Layouts folder.
Select the EDI 820 layout that you need. e.g. EDI820_US_ACH_CTX_STP.csv
Click OK.
The data will be imported. An Infolog message will display showing the number of records
added.
8. Click Close on the message.
9. Repeat for other EDI layouts that you need.
Setup Security/Permissions
1. See Appendix A – Setting up eBanking Security
Organization Hierarchies
1. See Appendix B - Organization hierarchies in eBanking
Virtual Companies
1. See Appendix C - Virtual Companies
Updated: December 24, 2014
Page 16
C. Unlocking Keys
Your AX reseller will provide you with an unlocking key for the eBanking Suite (or you can call or email
the registration department as shown on the eBanking Suite parameters screen). The software is in
“demo” mode without an unlocking key. When in demo mode, files are restricted to 3 records (Pos Pay/
APEFT+/AREFT+ – 3 records in the output file, eBank Rec /Lockbox – 3 records processed from the input
file).
The unlocking key is based on the AX License Serial number (red arrows), total number of AX Users
(Functional + Enterprise + Server) (green arrows) and the eBanking Suite Product version (blue arrow) as
well as the combination of eBanking modules and EFT+ formats that have been licensed. Below you can
see where the Serial Number and AX Authorized Users are displayed in eBanking Setup parameters and
in the AX License Information screen.
Be sure to ONLY check the eBanking modules that you are licensing.
eBanking Suite parameters
NOTE: If any of the above bolded values change a new unlocking key may be required. The eBanking
Suite is licensed based on tiers of the Enterprise + Functional + Server user counts (1-25, 26-75, 76-299
and 300+). If the user count changes and moves to another tier a new unlocking key is required – and
this will require a license upgrade.
Updated: December 24, 2014
Page 17
NOTE: You can use unlicensed modules in “demo” mode by simply checking the “Active” option on the
modules tab.
AX License Information
The AX Serial number and Users count are also found on the License Information screen. They are found
under the AX Administration Module | Setup | Licensing | License Information screen (once the license
file has been loaded, the Access Licenses tab shows the counts by types of users):
Updated: December 24, 2014
Page 18
E. Un-Install
Introduction
This section discusses how to un-install the Dynamics AOT objects that belong to the eBanking Suite
feature.
1. Remove the SKS eBanking Model.
2. Remove the Help files.
3. Remove the client assembly.
Remove the eBanking Suite AX Objects (SKS eBanking Model)
1. Warning! Performing these steps will remove all eBanking Suite data.
2. Open a command prompt as Administrator.
3. CD to C:\Program Files\Microsoft Dynamics AX\60\ManagementUtilities.
4. Run the following command (your path to the model file may be slightly different):
Axutil list
Delete each SKS model listed using the following command:
Axutil delete /model:SKS.xxxxx
5. This removes the eBanking suite code.
6. Re-start the AOS (this allows AX to recognize the model removal).
7. Start AX 2012.
8. You will be prompted that the model store has been modified. Choose Compile and
synchronize.
Uninstall the eBanking Help files
1. Use Control Panel | Add/Remove Programs to uninstall “eBanking – AX2012 Help – x.x.x”
Remove the Client Assembly
1. Perform the following steps on each Client workstation where the eBanking Suite was originally
installed.
2. Go to the path where the client assembly was installed. It should be something similar to
C:\Program Files (x86)\Microsoft Dynamics AX\60\Client\Bin.
3. Locate SKS.Common.dll (used with RTM or FPCUxx) or SKS.Common.R2.dll (used with R2 or R2CUx) or SKS.Common.R3.dll (used with R3) and delete it.
4. Repeat steps 1-3 above on the Server.
Remove the EFT+ email templates (v5 and later)
1. Go to Basic > Setup > E-mail templates.
2. Delete the four templates that have an E-mail ID that starts with SKS_EFT.
Updated: December 24, 2014
Page 19
F. Backup & Restore
The SKS-eBanking Suite is written as a Microsoft Dynamics AX–based application. The eBanking Suite
fields and tables will be treated the same as any other data and will be backed up as part of the core
Microsoft Dynamics AX backup process.
G. Revision/Enhancement History
Note: v6 and greater includes AREFT+, v5 does not
Revision 7.3.1 – 12/24/2014 (NOTE: an EB pre-6.7 to 6.7 or greater upgrade requires a new
unlocking key)

eBankRec
o AB Service is discontinued and bank statement file import is now done via an AX
batch server (#3301)
o File import - MT940 file format imports debits as deposits and credits as disbursements
when the credit/debit flag was set to "CR"/"DR" (#3326)
o Click-n-Match – added Select All option (#1182)

AR eSettlement w/Lockbox
o Automation features added – files imported, matched in the workbench and the A/R
payment journal is created (unattended) (#3194)
o Workbench – make full screen when maximized (#3204)
o
Workbench – message when moving payments displayed incorrect customer (#3218)
o
Workbench - Reassign payments allows you to assign payment amounts to
different check numbers (#3310)
o File Import – enhanced matching – Matching Rules Groups (#3291)
Updated: December 24, 2014
Page 20

AP EFT+
o Create and Send - Addenda file not printing vendor name in the file (#3175)
o Addenda Configuration - YYYYMMDD format for dates in addenda switches back
to YYMMDD on save (#3309)
o Create and Send – ACH – block fill not working correctly when over 10 payments
(#3322)
o Bank Account – AP EFT+ - block fill field disappears from screen if “Use defaults” button
is checked or unchecked (#3320)

AR EFT+
o AX Payment Journal – Added Change EFT+ state – send file now option (#3318)

General
o Registration/unlocking key code moved to server side (#3292)
o Support for R3/CU8 (#3324)
Revision 7.2.0 – 11/17/2014 (NOTE: an EB pre-6.7 to 6.7 or greater upgrade requires a new
unlocking key)

eBankRec
o GL mapping rules – allow matching for txn types when the mapping rule fails to find a
value in the lookup screen (#2638)
o File Import – when the bank file includes time in a date field, remove the time value and
retain the date(#2952)

AR eSettlement w/Lockbox
o Workbench – Support ability to have unmatched negative settlements break into a
separate negative payment record in good payments grid (#3255)
Updated: December 24, 2014
Page 21

AP EFT+
o Code Lookup - format group should be validated against valid format groups (#2987)
o Create and Send – under certain circumstances the Next Action combobox is disabled
and set to Select (#3062)
o Character Replacement groups added (#3169)
o Create and Send – ACH file format used incorrect service class code when a change was
made to the vendor bank account. (#3179)
o Create and Send - Paying a vender into two different vendor bank accounts, results in
the beneficiary information from the first account appearing on subsequent transaction
lines (#3231)
o Vendor eBanking Details/Additional Data - 'A field requires additional data' warning
occurring when trying to close Additional Data (#3241)
Revision 7.1.1 – 10/21/2014 (NOTE: an EB pre-6.7 to 6.7 or greater upgrade requires a new
unlocking key)

eBankRec
o Imported Statement History - UI cleanup - grid width, grid row shading, multi-select,
status bar (#3100)
o File Formats – support for MT940 (#3107)
o Click-n-Match - not showing transactions in the top or bottom grid when the bank
account id contains a comma (#3160)
o Matching - eBankRec not auto matching when bank account id contains a comma
(#3187)
o Parse rules - added ability to trim leading zero from parsed values (#3208)

AR eSettlement w/Lockbox
o Process Files – Added a column for the physical file name associated with a particular
lockbox journal. (#2464)
o Workbench - LB Batch total doubles when records for check paying +1 INV appear in
payments and payments with errors (non-BAI2) (#2961)
o Workbench - Posting date not defaulting correctly in Create Payment Journal dialog
(#3014)
o Workbench - Receive error when attempting to insert a record across companies into
the errors grid (#3092)
o File import - Settlement amount is incorrect in BAI2 files with multiple 4 records settling
the same invoice within the same check (#3104)
o Formats – Symcor added (Canada) (#3131)
o Workbench - Import a description from a lockbox file and enable it for edit within the
workbench form (#3159)
o File Formats - Added credit settlement and negative payment indicators to configure
layouts more precisely (#3162
Updated: December 24, 2014
Page 22
o
o
o

Process Files - added option to filter lockbox journals – completed, not completed
(#103)
Setup – Bank Account – added option to create individual payment lines for each invoice
being settled (#3192)
File Import - AutoCredit fails when a credit invoice reference is the same as the invoice
number (#3212)
AP EFT+
o Communications - form allows Inbound direction for modules that don’t support it
(#3093)
o Inbound File - Add status action has incorrect label on form (#3095)
o Inbound File Groups - Change error message that displays when changing Action (#3098)
o eBanking Parameters – AP EFT+ Setup – options are cut off (#3099)
o Communications – after selecting a Batch Job ID, the communications ID changes
(#3120)
o Create and Send File - Path and file name fields too short and not scrollable on EFT+
create/send form. Can't see all data (#3127)
o AP Payment Journal - Able to delete the AP Payment Journal that contains payments
sent to EFT that haven't been processed - AX 2012 R3 (#3137)
Revision 7.0.0 – 9/16/2014 (NOTE: an EB pre-6.7 to 6.7 or greater upgrade requires a new
unlocking key)

eBankRec
o Automation features – auto-create statements, auto-post GL journal, auto-reconcile
statement (#3040)

AR eSettlement w/Lockbox
o File Formats – correct spelling on EDI column (#3010)

AP EFT+
o Inbound (return) file support (#3039)
o Automation features – auto-create/send, auto-post journal, delayed payment rejection
reversal (#3041)

General
o eBanking setup parameters – change default purge months from 2 to 24 (#3037)
Revision 6.11.2 – 8/19/2014 (NOTE: an EB pre-6.7 to 6.10 upgrade requires a new unlocking
key)
Updated: December 24, 2014
Page 23

Positive Pay
o Formats - ARP Register field 7 optional description field data no comma allowed (#2846)
o Audit report - Positive pay audit report doesn't include the positive pay file number and
Grand Total label is on the left side of the page but its ':' is on the right side of the page
(#1883)
o Create/Send - Checks From option in Select/View Checks does not filter records in the
grid when deselecting a check with a date that is less than 60 days ago (#1244)

eBankRec
o Service – AB.Service shows running but is not processing folders after loss of access to a
remote folder (#2822)

AR eSettlement w/Lockbox
o Import - Lockbox CSV files assign values from files out of order (#3005)
o Workbench - Reassigning a payment causes the invoice number to be added to the
newly created payment record in the AR journal (#3004)
o Support added to process fees (#2960)
o Support for EDI820, EDI823 file formats (#2959)
o Support for multiple lockbox file formats per bank account (#2958)
o Support for multiple bank accounts within the same lockbox file (#2576)
o Workbench – Cannot move invoice to good grid because of incorrect "invoice found for
wrong customer" error (#2953)

AP EFT+
o Formats – Wells Fargo PMS – Receiving party bank ID type was not recognized (#2955)
o Formats - US-Chase-SUA-28 field 7 vendor bank account pulling from Chase Bank
account and not vendor (#2832)
o Formats - US-CITI-CDFF FT – writing file - payment spec requires field 4 (Value date) and
field settings for vendors with SWIFT codes are not correct (#2831)
o Create/Send – MAL - Contact name / e-mail is defaulting fax and phone number as well
as email (#2829)
o Vendor eBanking Details – Right-click on vendor address or MAL email - could not
process the lookup table value on the Args instance. The table 'LogisticsLocation' does
not exist as a root FormDataSource for the form 'DirPartyTable' (#2828)
o Vendor eBanking Details – more descriptive messages for required fields (#529)
o Create/Send – failed emails will now retry 3 times instead of 1. (#2751)
Revision 6.10.303 – 7/25/2014 (NOTE: an EB pre-6.7 to 6.10 upgrade requires a new unlocking
key)

AP EFT+
o Setup – EFT+ - code lookups (#2885)
o Vendors – account approval changes (#2886)
Updated: December 24, 2014
Page 24
o
o
o
Bank Accounts – account approval changes (#2886)
Setup – EFT+ Formats - Citibank – Ecuador format added (#2887)
Setup – EFT+ Formats – format grouping feature (#2888)
Revision 6.10.1 – 5/30/2014 (NOTE: an EB pre-6.7 to 6.10 upgrade requires a new unlocking
key)

Positive Pay
o File Formats - positive pay format able to be deselected while in use by Bank Account
and defaulted in parameters (#2249)
o Bank Accounts – added support for archive option and path (#2391)

eBankRec
o Imported file details – cannot filter the grid on description field (#2725)

AR eSettlement w/Lockbox
o Workbench – error grid invoice lookup taking too long to retrieve invoice list (#2416)
o Bank Accounts – added support for archive option and path (#2391)
o Workbench – creating/updating journals – error when number sequence is longer than
journal ID length (#2683)
o Lockbox File Formats - receive erroneous message "Are you sure you want to delete this
payment line..." message when delete a Lockbox file format (#2687)
o Lockbox File Formats - end positions are forced to be greater than start position in BAI2
lockbox formats/ last indicator default error (#2715)
o Workbench - payments are automatically settled against the oldest invoice for a
customer set to "No settlement (#2734)
o Workbench – creating/updating journals – Ledgerjournaltrans.MarkedInvoiceRecID for
an AR Payment Journal created from Workbench contains CustTrans.Recid instead of
CustTransOpen.Recid (#2772)

AP EFT+
o AX > AP > All Vendors - Error executing code: SKS_EFT_Addenda (object), method
validateAddenda called with invalid parameters in AP All vendors > Invoice tab > Settle
open transactions (#2707)
o Create and Send - EFT + File Details form should not show data on the MAL tab if it is not
an MAL payment (#2708)
o EFT+ File Formats - EFT file format form should check to make sure the MAL class exists
for the format when the MAL option is selected (#2711)
o Bank Accounts – added support for archive option and path (#2391)

AR EFT+
o Create and Send - Change column order of File details and make form re-sizable. Hide email fields if e-mail is not being used (#2360)
o Bank Accounts – added support for archive option and path (#2391)

General
Updated: December 24, 2014
Page 25
o
Support added for R3 (#2739)
Revision 6.9.1 – 5/2/2014 (NOTE: an EB pre-6.7 to 6.9 upgrade requires a new unlocking key)

Positive Pay
o Create/Send Files - Positive pay file name not created properly when the file name ends
with a period (#527)

eBankRec
o Rule Groups - Prevent deletion of an eBankRec Matching, GL mapping, or Parse rule if it
is in use (#2330)
o Posting GL ledger created by eBankRec - Error when posting GL if cross company ledger
account used in GL mapping rules on R2 and newer builds (#2685)
o SKS Adv Bank Rec Service - Application log error message ABRFolderNames would like
message to reflect error in partition name (#2582)

AR eSettlement w/Lockbox
o Workbench - When using a BAI2 Lockbox format that maps to the Bai2_CITI formatID,
moving more than one record from the errors grid to the payment grid will blank out
the payment journal posting date (#2526)
o Workbench - Attempting to perform a select all on the errors grid causes an "Invoice not
found" warning to appear for each record in the grid (#2527)
o Setup/Workbench – Add option to allow duplicate check numbers in Workbench
(#2624)
o Workbench - Receive "Access denied to method validateLedgerAccount in class
FinancialDimensionValidationService." when user attempts to create an AR payment
journal and the user has the Accounts receivable payments clerk roles assigned (#2668)

AP EFT+
o Copy Addenda Form - The word “form” should be removed from the caption (#2623)
o Bank Holiday Copy Group Form - Caption reads Bank holidays instead of Copy bank
holiday group (#2622)
o General - Add support for EFT Master Account List (MAL). This is used with Virtual Pay
card systems (e.g. Chase-SUA) (#2645)
o Paymode-X (BoA-CPPX format) - Populate Disbursing Paymode-X Account ID for the CHK
payspec and populate Vendor Number for the for the PMX and CHK payspecs for the USBOA-CPPX AP EFT file format (#2636)
o WF PMS XML format – Added additional field for a separate wire routing number
(#2654)

General
o Upgrade message - Change message box "An upgrade is required, click OK to proceed
with this normal process of upgrading The word “form” should be removed from the
caption (#2623)
o eBanking Parameters/Registration tab - Add licensing notes to registration form to
clarify pricing policy (#2136)
Updated: December 24, 2014
Page 26
o
Date fields - Date fields in eBanking should have a date lookup button. This is common
in AX for date fields (#2542)
Revision 6.8.2 – 4/8/2014 (NOTE: pre-6.7 to 6.8 upgrade requires a new unlocking key)

eBankRec
o Import files - Imported transaction for .19 (no leading zero) imports as 0.00 (#2546)
o Reconciliation/Click-n-Match - Unreconciled transactions selected total shows USD
currency Imported transactions selected total shows CAD currency unable to match
transaction (#2601)

AR eSettlement w/ Lockbox
o File formats – Field layout cuts off end of word for the format id (#2137)
o Import files – support for file with one line that doesn't have carriage returns (#1240)
o Import files – Get “record already exists’ when creating new customer eBanking details
– under rare cases (#2497)
o eBanking Suite Parameters - typo in Auto-credit account parameters message when
exiting eBanking Suite parameters (#2500)

AP EFT+
o Vendor eBanking Details - optional EFT+ Account information fields only displaying
when set to required, not used (#2417)
o Vendor eBanking Details - E-mail notification check box not automatically checked when
vendor has an e-mail address, the vendor is auto-added in Vendor eBanking details, and
AP EFT is setup for e-mail notifications (#2579)
o Communications – add support for communication IDs (#2407)
o Banking Holidays – add calendar support for prenotes & effective dates (#2283)
o Addenda Configuration – add support for tax and child support ACH addenda (#2046)

AP EFT+
o Communications – add support for communication IDs (#2407)
o Banking Holidays – add calendar support for prenotes & effective dates (#2283)
Revision 6.7.2 – 3/7/2014 – (NOTE: pre-6.7 to 6.7+ upgrade requires a new unlocking key)

Positive Pay
o Communications – automation features added (Upon Journal Posting, Fixed Time
(#2406)

eBankRec
o File Formats – added support for the Australian NAI format (#2135)

AR eSettlement w/ Lockbox
Updated: December 24, 2014
Page 27
o
o
o
o

Import files – when using any of the optional lookup methods – all those methods will
now be checked before using the default settlement method – was using default
settlement method if there was no invoice number (#2418)
Workbench – wrong information in message when creating A/R payment journal
(#2423)
Workbench – error grid select all option did not work with alternate lookup such as
customer requisition number (#2460)
Import files – auto-credits being created, but not matched and placed in the error grid
(#2461)
General
o Now include label files for all English locales - AXSKSen-au, -ca, -gb, -ie, -my, -nz, -sg, -us,
-za (#1079)
o New unlocking key required for v6.7 (#2462)
Revision 6.6.2 – 1/24/2014

Positive Pay
o Format – check rejected in a payment journal (now marked as void) was not appearing
correctly in the original pos pay file (#1245)
o Create/Send Files - Select/View Checks displays checks included in a file plus any check
that can be included in a PP file, fixed so only checks included in the original file are
shown (#2394)
o Create/Send Files - Positive Pay file when complete a file then later void a check the
selected checks number is incorrect (#1247)
o Audit Report - The Company Id field in the Positive Pay audit report displays the
sks_pp_filedetail.dataareaid instead of the company the check was created in (#1376)
o Create/Send Files - The Positive pay file number label is missing in the Positive Pay Select/View Checks form (#1460)
o Create/Send Files - Amount field in Select/View Checks for Positive Pay is enabled to be
edited, now fixed to remain disabled. (#2058)

eBankRec
o Import files - In BAI2 files eBankRec treats a space in the field as the end of the line.
(#2387)
o Matching/Mapping - Enhance eBankRec to enable Parsing, Matching and GL Mapping
rules to be shared across all companies (#2394)

AR EFT+
o Create/Send Files - The header and trailer records are showing in the AP/AR Create and
send File Details form as transmitted records (#1673)
Revision 6.6.1 – 1/6/2014

eBankRec
Updated: December 24, 2014
Page 28
o
Import files - BAI2 file with line feeds and no carriage return does not import (#2351)

AR eSettlement w/ Lockbox
o Workbench - able to select multiple payments for same invoice from error grid and send
them both to payments grid as settled (#2355)
o Workbench – added lookup type/reference fields to support AX transactions that don’t
have invoice numbers (#2337)
o Workbench - records with the same check number that appear in both the payment grid
and the payments with errors grid should not be able to be added to a payment journal
(#2339)
o Processing files - formatting/layout consistency issues (#2338)
o Processing files/Workbench - bank totals should not show on Journal summary and
Process esettlement/lockbox files forms if BAI2 formats are not in use (#2347)
o General - support for payment reference processing (in addition to invoice number, BOL,
Cust. Req., Sales Order) (#2342)

AR EFT Plus!
o Create and Send files – the Adv. Email, Adv. e-mail sent and Adv. e-mail failure counts
are missing from the File Details form (#1672)
Revision 6.5.2 – 12/9/2013

eBankRec
o Import file - Import BAI2 file into bank reconciliation with $ does not bring in the
amount of check (#2098)
o Import file - detail lines for accounts with a leading zero in the "Bank Accounts" screen,
will not import. (#2231)
o AP Vendor transactions/checks - add clear date field (#2296)
o Major enhancement – new architecture for matching and mapping. Matching Rule
Groups, GL Mapping Rule Groups, Parsing Rules. Click for details on these
enhancements. (#2299)
o Click-n-Match screen - when selecting a prematched transaction, the unmatching of the
existing prematch would not update the totals and not allow exiting the screen. (#2311)
o Reconciliation – Import bank file - correction amount is not set if a match was found
with an amount tolerance (#2324)

AR eSettlement w/ Lockbox
o Documentation – User Guide - added Hints/Tips topic covering cross-company
settlements
o Documentation – Reference - added document for Workbench – Create Payment
Journal
o Workbench - over/under payment tolerance is not used for credit payments (#862)
o Workbench - give users options to handle duplicate settlements more effectively than
current "settlement marked by another user" functionality (#1677)
Updated: December 24, 2014
Page 29
o
o



Workbench - show the unsettled payment amount visible in the grid (#1681)
Workbench - show payment (BAI2 "6" records) and settlements (BAI2 "4" records) all
together in the esettlement/lockbox file pop-up screens (#1683)
o eSettlement/Lockbox journals - display counts and amount totals from BAI2 import file
to be used to balance to actual counts/amounts (#1678)
o Create AR Payment Journal - improve date defaulting for check date and posting date
(#1680)
AP EFT Plus!
o Create and Send files - receive "Only 1 EFT+ file (at a time) can be selected for
processing." message when click the Selected checkbox on the Create and send AP EFT+
files screen and only one line is selected (#1106)
o Create and Send files - email attachment for a vendor bank debit doesn't report
information properly (#1220)
o Create and Send files - EFT offset date multiplied when more than one journal is
selected (#2282)
o AP Payment Journal - message generated when Validate EFT+ for a credit amount and
“Allow vendor bank debit” is not selected “Vendor eBanking details” should indicate
where to turn the option on (#1221)
o AP Payment Journal - cannot post payment journal with delete lines checked, message
"Cannot edit record in ledger journal table, update conflict due to another user
process.” (#2132)
o AP Payment Journal - able to change Payment status in AP Payment Journal after
Payment status is set to “Sent by AP EFT” and then manually changing Payment status
to “Rejected” (#2147)
o Vendor eBanking details - automatically populate Beneficiary and Beneficiary bank
information for vendors when vendors are added to eBanking using bulk load, auto
create or manually in vendor payment spec (#1962)
AR EFT Plus!
o Create and Send files - receive "Only 1 EFT+ file (at a time) can be selected for
processing." message when click the Selected checkbox on the Create and send AR EFT+
files screen and only one line is selected (#1106)
o Create and Send files - overdue by xx Days - same as the "Send in xx days" message but
should be issued when the Business Date is PAST the Transmit/Effective Date. (#1756)
o Create and Send files - AR ACH with Prenotes turned on is not using bank account in the
ebanking bank account screen but the default for internet explorer (#2091)
o Customer eBanking details – “Allow customer bank credit” check box is missing from
payment spec details (#2126)
o Bulk load customer eBanking details - allows the selected checkbox to be checked even
if there is no bank account (#1110)
General
o Added R2-CU7 model, removed R2-CU1 model (#2216)
Revision 6.2.6 – 10/7/2013
Updated: December 24, 2014
Page 30


AR eSettlement w/ Lockbox
o File Formats - Cannot change field start or end on Batch Sequence and Batch number
and Last indicator fields for BAI2 formats (#2072)
o Workbench - Cannot edit a record in eSettlement/lockbox journal AR
(SKS_LB_JournalAR). If the Invoice was for a different company from the payment
company, error would occur if trying to edit the settle amount in the settlements
subform (#2085)
o Workbench - Cannot reassign unassigned amounts to same customer account with
different dimension (#2048)
o eBanking Parameters – Warning should be given if Auto-credit account parameters grid
is empty but auto-credit is checked. (#1573)
o Workbench Errors grid - Invoice lookup in Errors grid of Workbench should use Lookup
Options setting in eBanking Suite Setup instead of displaying all open documents for the
customer (#1892)
o Workbench Errors grid - Multiple matches found error should not be received in
Workbench for duplicate invoices that are simply installments of the same base invoice.
(#2102)
o Workbench Errors grid - Nothing happens when select to move a payment to top grid
when the payment is settled against an invoice installment that is also selected in a
different AR Payment Journal. Should receive a message why the payment can't be
moved. (#2031)
o eSettlement w/Lockbox batches - Process eSettlement/lockbox files form does not order
the journal number in descending order (highest to lowest, most recent on top) (#1481)
o Workbench - Unable to settle multiple installments with one payment in Workbench. AR
Payment Journal allows multiple installments to be settled by one payment. (#2029)
o Workbench Errors grid – Stack trace: company does not exist. Error displays in lockbox
workbench when clicking in an empty grid for invoice for a record in Payment with
errors section. (#2013)
AP EFT Plus!
o Template Setup - Add invoice description to EFT email (#2064)
o eBanking Parameters – Test email - AP and AR EFT files to choose from were
erroneously displayed (AR files for AP and vice versa) (#1282)
o Create and Send - AP EFT file not in APEFT folder or in Archive folder when Archiving is
on and Delete file after sending is on (#1123)
o Payment Journal - EFT+ state for an AP Payment Journal is Ready even though payments
have been transferred to eBanking and the file for the payments has been completed
(#1787)
o Template Setup - Email templates add format for dollar sign, comma and period for
cents. (#1280)
o Template Setup - Email templates wants ability to send date format using regional date
on computer (#1271)
o Create and Send - File journal and prenote option does not display in Create and send
AP EFT+ files or Create and send AR EFT+ files when prenotes are not turned on (#1277)
Updated: December 24, 2014
Page 31
o

Create and Send - Incorrect EFT file when using the same vendor id from different
companies in the same payment (#2115)
o Vendor Bank Accounts - Receive "Warning - One EFT+ vendor payment specification
uses this bank account and requires prenotes." in Vendor bank accounts when specify
Bank Group and a bank account setup for AP EFT is attached to the group but vendor
doesn't exist in eBanking (#1212)
o Create and Send – Selected payment journals in EFT+ Select/view payments is incorrect
when Filter into separate files option is turned on for a payment spec (#1794)
o Create and Send – Payment spec is blank in EFT+ Select/view payments for ACH-CCD
payment spec in the USBOAEDI820 file format (#1793)
AR EFT Plus!
o Create and Send - One of the selected payment specification requires that payment
dates must be the same (#1062)
o Create and Send - The Payment details grid is empty in Create and Send AR EFT+ files. If
Filter into separate grid or Select by payment date settings were not consistent for all
specs within a format, could intermittently get issues selecting records together for
payment within EFT. (#1068)
o Create and Send - The Transaction Code for the company's 6 record is showing as 23
instead of 28 in an EFT+ file that is for Prenotes (#1790)
Revision 6.2.4 – 8/30/2013



Positive Pay
o All formats are now in classes (#1345)
o Formats – JPMChase-PWS report does not include the vendor name (#1995)
AR eSettlement w/ Lockbox
o File Formats – Change Lockbox BAI2 format to have mappable Check and Invoice lines
(#1344)
o File Formats - Add ability to store front and back image for checks identifiers for checks
(#1397)
o Workbench - LB payment that doesn't settle an invoice disappears from Errors grid after
moving the payment to the Payments grid then moving to the Errors grid (#1947)
o Workbench – Manage dimensions on payments (#1330)
o Workbench - Incorrect payment amount when moving a record from good grid to error
grid (#2014)
o eBanking Parameters - Path does not exist message displays when typing in the Path to
eSettlement/lockbox files field (#1710)
AP EFT Plus!
o File Formats – Add support for US-ACH – CTX, .csv import (#1374/#1560)
o File Formats - BFX and SWIFT payments to Australian companies must use a BSB (BankState-Branch) code instead of a SWIFT code (#1996)
o File Formats – US-BOA-EDI820 format - Debit entries and negative credit entries in an AP
Invoice Journal appear as positive amounts in the Remittance Advice Accounts
Receivable Open Item (RMR) record (#1997)
Updated: December 24, 2014
Page 32

General
o Registration – Correct license counts for EA and Hosted license types (#1375)
o Registration – Key for licensed key now is valid for any user count <= licensed count
(#1373)
o Registration/All apps - Unlocking key changes to allow modules that are not unlocked to
be in demo mode (#1958)
Revision 6.1.14 – 8/5/2013




eBankRec
o Add/Remove Programs - Advanced bank reconciliation service when install 6.1.5.6 and
go to add remove programs version shows 6.1.2 (#1424)
o Click-n-Match - Click and match showing difference amount when using foreign currency
(#1806)
AR eSettlement w/ Lockbox
o Workbench – Lockbox imports two credit notes for the same items to good grid. One by
requisition number and one by the invoice number (#1818)
o Workbench - Missing labels (#1483)
o Workbench - Remove LB customer account number from top grid of Workbench. It is
causing confusion when records are moved between grids and should only contain data
if a customer account number is in the file. (#1633)
o AX Sales Order – Error (from eBanking code) when entering order - cannot create a
record in Invoice secondary match (SKS_LB_InvoiceMatch). Match type: Invoice number,
xxxx the record already exists (#1410)
o Workbench – Creating A/R Payment Journal - Journal lines cannot be created as no
attached journal exists (#1828)
o Workbench - Reversing entry should use the date of the payment for transaction date.
(#1854)
o Workbench - When a change is made to a settlement amount the settled amount at top
of the workbench grid doesn't change if using F5 to refresh the screen (#1894)
APEFT Plus!
o Bank Account – Originating DFI name in APEFT+ defaults from eBanking Suite
parameters > EFT+ Defaults > Immediate Origin Name instead of Originating DFI name
(#1800)
o A/P Payment Journal – EFT+ validation - AP payment journal if create partial payment
the ap eft file not getting created successfully. Validation code enhanced to verify
payment/settlement records (#1586)
o Vendor eBanking details - A vendor address with multiple lines is placed in Address 1 on
the Wire Transfer/IAT - 1 tab of Vendor eBanking payment spec details (#1936)
General
o Model support for R2, CU6 (#1898)
Updated: December 24, 2014
Page 33
Revision 6.1.12 – 6/25/2013





eBankRec
o Bank Accounts - Add Alternate Bank ID field for resolving bank accounts during bank rec
import. (#1552)
o File Import - Bank Rec records are not being imported properly when "Use Setup
Defaults" is checked in the eBanking's Bank Accounts screen when used with multiple
companies (#1775)
AR eSettlement w/ Lockbox
o Workbench – General Journal button should automatically open under the customer
company of the Good grid line that is in focus, not open in the current company (#1320)
o Workbench - the payment total for both good and errors grid together doesn't equal
the batch total for the bank file for BAI2 formats (#1333)
o Workbench - Reassign payment amount can't find customer if in a different company
(#1492)
o Workbench - Lockbox not putting payment to the correct company when customers
shared and invoices in two different companies (#1637)
o Workbench - Auto-credits when created should use the date in the check record of the
bank file and not todays date (#1721)
APEFT Plus!
o Vendor eBanking Details – AP Payment Specifications – buttons enabled when accounts
list was empty. Using buttons - Stack trace: The company does not exist.
c:\forms\sks_eft_appaymetnspecdefaults\designs\designlist\bankaccounts\method\clic
ked (#1594)
o US-BOA-EDI820 format - only the first outsourced check payment (CHK-PBC-US) within
an AP Payment Journal is assigned a check number when the journal's new voucher field
is set to one voucher number only (#1743)
o US-BOA-EDI820 format - Recipient name (BankChequeTable.BankNegInstRecipient
Name) in cash and bank management > checks is not updated for CHK-PBC-xx payment
specification (#1786)
AREFT Plus!
o Customer eBanking Details – AR Payment Specifications – buttons enabled when
accounts list was empty. Using buttons - Stack trace: The company does not exist.
c:\forms\sks_eft_appaymetnspecdefaults\designs\designlist\bankaccounts\method\clic
ked (#1594
o AR Methods of Payment - the "EFT+ format" section label is missing above Format Id in
the File formats area (#1276)
o AR Methods of Payment - Unable to View details, no form exists for table
'SKS_EFT_FileFormat' infolog displays when right clicking the AR EFT+ format id (#1458)
General
o eBanking Parameters – Registration - handled exceptions are not popping up in 6.x.x.6
builds. (#1138)
Updated: December 24, 2014
Page 34
Revision 6.1.10 – 6/7/2013


eBankRec
o Import process – change to accommodate RBC BAI2 – extra characters (#1589)
o Import process - Bank Rec Service fails if BankAccountTable is virtualized (#1695)
AR eSettlement w/ Lockbox
o Workbench – invoice number could not be found error when manually entering invoice
number that is in a different company (#1659)
o Workbench - error grid invoice look up taking too long to retrieve invoice list (#1662)
Revision 6.1.9 – 6/4/2013




Positive Pay
o Audit report - prints the same name at top of report no matter what company logged
into (#1626)
eBankRec
o Imported bank files - users are able to delete imported files after the related bank rec
statement is reconciled and this causes unreconciled balances (#1619)
AR eSettlement w/ Lockbox
o Import – auto-credit fails if it occurs after a split invoice check. (#1618)
o Import - lockbox does not create auto-credit if invoice is same number as existing debit
invoice (#1561)
o Workbench - auto credit button says it will use default values even though customer
auto-credit info is available. (#1562)
o Workbench - Incorrect records are put into the error grid when moving a record from
the good grid to the error grid in LockBox (#1382)
APEFT Plus!
o Payment Journal – dimensions were not defaulting correctly when executing Functions >
Generate payment (#1495)
o Create and Send - a payment made to an AP EFT vendor is included in an ACH file even
though the vendor's Inactive Date has passed (#1283)
o Create and Send – some file formats – file creation date is the effective date and should
be current date (#1588)
o Create and Send – US-ACH - Incorrect company bank account specified when two
payments are for different bank accounts but the same company (#1620)
o Create and Send – US-ACH - The BatchHash (“8”) and FileHash (“9”) in the file can
display a negative number - fixed (#1577)
o Create and Send - two buttons with the same label exist in Create and send AP EFT+ files
and Create and send AR EFT+ files (#1275)
o Create and Send - unable to change file name and path (#1450)
o Vendor eBanking Details - Stack trace error: “the company does not exist” Error displays
when clicking on the Vendor Bank Accounts button when there is no record in the grid
on the payment specification details form (#1416)
Updated: December 24, 2014
Page 35
o


Vendor eBanking Details – AP Payment Specifications - displays prenote and account
approval as being turned on even though now they are turned off (#1417)
o Vendor eBanking Details – add vendor name to grid (#1241)
o eBanking Parameters – EFT+ Defaults – AP EFT+ Setup - the Auto create vendor
eBanking record checkbox should be checked by default for a new eBanking installation
(#1508)
o US-BOA-EDI820 – bank unique payment specification company ID and name are not
working (#1636)
AREFT Plus!
o Create and Send - a .SKTest file is getting created, but not deleted. Fixed (#1053)
o Create and Send - two buttons with the same label exist in Create and send AP EFT+ files
and Create and send AR EFT+ files (#1275)
o Customer eBanking Details - Stack trace error: “the company does not exist” Error
displays when clicking on the Customer Bank Accounts button when there is no record
in the grid on the payment specification details form (#1279)
o Customer eBanking Details – add customer name to grid (#1241)
o eBanking Parameters – EFT+ Defaults – AR EFT+ Setup - the Auto create customer
eBanking record checkbox should be checked by default for a new eBanking installation
(#1510)
General
o Create and update model for AX 2012 FP-CU5 (#1512)
o AX 2012 help files are now provided
Revision 6.1.7 – 5/13/2013


eBankRec
o AX Account Recon - Unable to clear the cleared check box on Account reconciliation due
to error message “This transaction has been matched with an imported transaction. Use
Import bank file to remove the match” (#1309)
o BAI2 Format support enhanced – support “+” throughout, wrapped “88” records now
handled (#1364)
o Able to uncheck items in Account Reconciliation (Forms/BankReconciliation) that have
been matched manually in the Import Bank File screen(forms/SKS_BR_BANKTRAN)
(#1505)
o Import - Changes to support RBC BAI2 file bank account number (#1551)
o Import Log - users are able to delete imported bank files after the related bank rec
statement is reconciled and this causes an unreconciled balance (#1462)
AR eSettlement w/ Lockbox
o eSettlement/lockbox file formats – field layout – change “Invoice number” to “Invoice
reference” (#665)
o Free Text invoice if input a customer requisition number lockbox did not use the PO#
field in custinvoicejour table to find a match (#975)
Updated: December 24, 2014
Page 36
o

Corrected error when opening eBanking Parameters after an upgrade. Received
message: “Cannot insert multiple records invoice secondary match sks_lb_invoice match
customer requisition mxn080911a” (#998)
o Customer bulk load – loading customers - incorrect customer name (#1117)
o Import - Auto-credit does not work if the customer/invoice is in a different company
than the processing/payment company (#1144)
o Workbench – add "Select All" button (#1190)
o Payment Journal post gets error - Cannot edit a record on open customer transactions
(CustTransOpen). An update conflict occurred due to another user process deleting the
record or changing one or more fields in the record (#1193)
o Workbench - Auto Credit created for wrong customer if Account and Account suggestion
are both present in errors grid (#1261)
o Workbench - "Create free text invoice" button in the error grid should open in the
Customer Company of error grid record (#1268)
o Workbench - when moving payments to errors gird, settlement information is lost if
settlement amount was first zeroed out on settlement screen before move (#1288)
o Workbench - Settle amount taken for larger than amount that document balance
(#1300)
o Workbench - LB requires full settlements if rounding parameters are set to zero in AX
setup (#1312)
o Import - Invoices created thru Auto-credit do not have tax, language and address field
filled in properly (#1316)
o Workbench - Cannot move unsettled payment to good grid without an invoice number if
a bad invoice number was imported from lockbox file (#1369)
o Import - Auto-credit and auto-debit GL entries in lockbox to support multiple companies
with multiple chart of accounts (#1429)
o Workbench - auto reversing checkbox (payments grid) is not checked when a credit note
that was auto created is applied to a payment record (#1464)
o Workbench - LB Invoice field is incorrect in errors grid when record is moved from top
grid to error grid (#1484)
o Workbench - customer company field is blank in the errors grid when the Invoice
error/note is "Found, for wrong customer" (#1517)
APEFT Plus!
o Create and Send - Set vendor to inactive for AP EFT+ yet allows txn to pass validation in
AP Payment Journal (#893)
o eBanking Parameters - Message "EFT+ e-mail cannot be enabled until Administration>Setup->E-mail parameters are set up." should refer to System administration, not
Administration (#1042)
o Vendor Bulk Load - vendor name is incorrect in grid (#1049)
o Create and Send - records in grid should be sorted from highest to lowest EFT+ file
number instead of lowest to highest (#1066)
o Create and Send - Change the behavior that occurs when using bank debits (aka credit
memos) in APEFT+ and using bank credits for AREFT+ (#1257)
Updated: December 24, 2014
Page 37
o
o
o
o


AP Payment Journal - Stack trace error: the company does not exist message when
select to delete all lines in AP Payment Journal and AP EFT+ is not licensed (#1259)
Create and Send - when vendor address is on two lines in vendor screen a carriage
return to APEFT+ file (#1342)
Create and Send - Receive Error message: Stopped (error): Cannot edit a record in
Ledger journal table (LedgerJournalTable). The record has never been selected." Occurs
when running GL workflows (#1363)
Vendor Bulk Load - name field is enabled in grid (#1514)
AREFT Plus!
o Customer Bulk Load - name field is enabled in grid (#1515)
General
o Create and update model for AX 2012 R2 CU1 (#1332)
Revision 6.1.5 – 3/15/2013


eBankRec
o An unhandled exception ('System.IO.FileNotFoundException') occurred in
SKS.ABService.exe [11612] and the ABR service stops (#1171)
o Account reconciliation screen not showing checks cleared that were cleared in click and
match (#1184)
APEFT Plus!
o AP EFT format for Bank of America CashPro (#1167)
o US-BOA-EDI820 format issues fixed (#1198)
Revision 6.1.4 – 2/28/2013

AR eSettlement w/ Lockbox
o Lockbox payment imports with Customer Company set to the virtual company ID
(#1034)
Revision 6.1.3 – 2/22/2013

Positive Pay
o Void checks (tran code 430) should have zero dollar amounts for multiple
WELLSFARGO_NNN positive pay formats (#1095, #948, #1011)
o Positive pay file not in PP folder or in Archive folder when indicated that the file was not
transmitted successfully (#759)
o Positive Pay URL required for a bank account even though PP not used for this bank
account (#761)
o Clicking the Default positive pay format ID drop down box on the Modules tab of
eBanking Suite parameters takes you to the Registration tab when an unlocking key has
not been entered (#919)
o Print Report check box was updating the setup checkbox in the PP create and send
screen. (#1077)
Updated: December 24, 2014
Page 38



eBankRec
o Click n match - if sorting by check number and picking 3 checks on top of grid and 3 on
bottom of grid it only saves the last check as cleared. (#639)
AR eSettlement w/ Lockbox
o LB - credits not creating credit for previous invoices found on this same check and those
invoices all pointed to the same company customer, use that customer (#699)
o Create credit is not creating a credit but an invoice (#700)
o Credit note assigned as a transaction that is already marked. Should allow the credit
note to process successfully. (#707)
o Credit notes are not being tagged as credit notes if the lockbox file cannot find an
invoice or customer for the record being imported (#762)
o LB payments without a check number import each “4” record as individual payments
(#805)
o Unable to select a credit note in the Errors grid when the credit note's number is the
same as another open credit note for the customer (#806)
o LB ability to create a credit payment in the workbench and leave it unapplied (#809)
o AR Payment Journal created from Lockbox doesn't appear in AR Payment Journal when
journal name as Private for user group set to an AX user group (#1022)
o Create an Invoice from a Sales Order, the Invoice does not appear in the
sks_lb_InvoiceMatch table (#954)
o R2: AR payments created for LB payments do not have the Offset account specified
(#999)
o Label in Lockbox setup is incorrect (#1072)
o Customer company in Customer eBanking Details is not set when a record is created for
a customer that was processed in Lockbox (#1043)
APEFT Plus!
o PNC bank spec needs space filled after payment set 641-1057 (#720)
o PNC vendor eBanking details requires bank account and routing number. They need
SWIFT and IBAN (#871)
o Vendor bank account fields required when they shouldn't be for the EU-SEB-INT, PLSEB-0511, SE-BGC-0711, and US-PNC-FX-R2 APEFT file formats (#853)
o Poland for the vendor side is pulling the bank account and routing number. Need to pull
the SWIFT code and bank account number. (#908)
o Poland file field 15 the transaction classification need quotes around the field. (#922)
o Poland bank spec in the 4 record needs the SWIFT (#869)
o Vendor bulk load vendor creates vendor eBanking with no vendor bank account yet that
is required field (#949)
o Load all vendors and click on bulk load bank accounts and do not get a list of all vendor
bank accounts (#965)
o Cannot edit a record in Vendor bank accounts (VendBankAccount). The record has never
been selected. (#967)
Updated: December 24, 2014
Page 39
o


When VendTable is virtualized the Vendor Bank Accounts show for both companies but
only saved for one which makes the vendor bank account drop down list blank in
Vendor eBanking details (#1008)
o You are not able to change the path or filename when "Can change filename and path in
create and send" is checked (#972)
o Vendor Details email template resets to the eBanking Setup values on save (#1021)
o Email templates not defaulting correctly in Customer eBanking details and Vendor
eBanking Details (#1024)
o Can't edit a record in EFT + file (SKS_EFTAP_FILE) the operation can't be completed since
the records were not selected for update (#1046)
o Discount amount was incorrect if past discount date (#903)
o Segment count in SE record of US-BOA-CHK-EDI820 is incorrect (#920)
o The vendor bank account drop down list is empty in the Vendor eBanking details form
when the VendTable and the… (#993)
o CLRObject static method innovaction error when trying to create and send AP EFT with
email turned on (#1010)
o eBanking Vendor detail and Customer detail records get created even if Auto create not
set in eBanking (#1088)
o In the AP create and send screen, the print audit report check box does not default the
value from setup screen (#1078)
AREFT Plus!
o ACH file issues - offset and total amounts (#1023)
o Processing both AP EFT and AR EFT could incorrectly select the file record from the
other module (#1025)
o Check AR test file do not receive message box (#1064)
o Payment journal has transactions that are selected in EFT+ file: 000001. Message box
does not give actual file number (#1067)
o Incorrect label when the Can change file name and path in create and send is checked
with Server Side processing turned on. The AP module is displayed in the label instead
of AR (#1050)
o Can't edit a record in EFT + file (SKS_EFTAP_FILE) the operation can't be completed since
the records were not selected for update (#1046)
o The Complete message box does not appear for AR EFT+ if the Separate user
submits/uploads the file to the bank (2-step) checkbox is checked in AP EFT+ (#1051)
o Block Fill is being ignored if only AR EFT+ is active (#1098)
o Numeric File ID Modifier is never used in a US-ACH file (#1096)
o Error can't locate email template. Check template name and language in setup (#1044)
General
o Registration screen – when authorized users is 600000 - Arithmetic operation resulted in
an overflow. at SKS.Common.EBCommon. RegistrationCheck(STring Checkkey, String
moduelString, Int32EFTLicFormatsNbr, Boolean isUserInteractiveMode) (#1115)
o Auto create customer and vendor are missing from eBanking setup in 2012 (#1087)
o Issue with unlocking keys – including Task users (#885)
Updated: December 24, 2014
Page 40
o
Add support for AX 2012 FP CU3 and AX 2012 FP CU4 (#955)
Revision 5.4.2 – 2/6/2013



eBankRec
o Click and Match - items in click and match selected, Imported bank file shows
reconciled, Account reconciliation checks not cleared. Fixed (#822)
o Dimension used when creating the GL journal entry for transaction type was not
creating dimension for right side of entry (#850)
APEFT Plus!
o Discount amount was incorrect if past discount date (#903)
o Vendor custom fields do not show (#928)
o Creating EFT+ file taking too long (over an hour). Fixed (#1039)
o Issue showing prenotes on Create and Send fixed.
General
o Issue with unlocking keys – including Task users (#885)
Revision 6.0.2 – 1/7/2013




eSettlement/Lockbox
o LB payments without a check number import each 4 record as individual payments
(#805)
o Unable to select a credit note in the Errors grid when the credit note's number is the
same as another open credit note for the customer (#806)
o Ability to create a credit payment in the workbench and leave it unapplied (#809)
APEFT Plus!
o Poland – modify to use SWIFT code (#908)
o eBanking Parameters – setup – multiple issues (#910)
o Create and Send – initial record not getting created (#912)
AREFT Plus!
o First release
General
o File paths are now controlled by server side accounts – for security (#767)
Revision 5.4.0 – 12/17/2012


APEFT Plus!
o Finland EU-SEB-1211 need routing number and IBAN in file (#749)
o Change for US-PNC-FX-R2 (#697
General
o Add support for AX 2012 R2 (#828)
Revision 5.3.0 – 11/28/2012


Positive Pay
o Payee name issues with comma would like quotes in payee name field (#748)
eBank Rec
Updated: December 24, 2014
Page 41
o


Error executing code: Wrong argument types for addition received when importing BAI2
BR file (#656)
o A line 16 record that ends with a "/" followed by spaces includes the "/" in the last field
instead of ignoring it since it means the line is continued with the following 88 record
(#763)
o The ability to take one deposit and apply it to several deposits on the imported bank
reconciliation file (CLICK-N-MATCH) (#260)
APEFT Plus!
o Bulk load design issue: Vendor eBanking Details form should have button to directly
launch bulk load. (#753)
o Finland EU-SEB-1211 need routing number and IBAN in file (#749)
General
o Registration change for user counts (#756)
o Installation support for AX 2012 Feature Pack (#752)
Revision 5.1.7 – 11/1/2012




Positive Pay
o Check status option for positive pay includes Void status checks but not able to get a
void (bankchequetable.chequestatus = 3) status check (#557)
eBank Rec
o Advanced bank rec service should display a better error message when the ABR svc
version differs from the eBanking version (#660)
o Electronic Bank Reconciliation File Format has not been setup for this bank account
received in Event log. (#634)
eSettlement/Lockbox
o Database upgrade should initialize the lockbox alternate lookup options to only search
on invoice by default. (#636)
o The Payment total in the error grid section does not display the proper value when the
Payment amount = Sum of check amounts is checked for the file format (#521)
o Label on create payment dialog in LB Workbench should be Posting date vs. Transaction
date (#684)
o Cannot edit a record in eSettlement/lockbox Journal AR (SKS_LB_JournalAR) error
displays when importing a settlement file with tolerance (#649)
APEFT Plus!
o Vendor eBanking details is creating vendor but not payment specification when change
method of payment and spec for Vendor in AX. (#708)
o Cannot edit a record in Vendor bank accounts (VendBankAccount). “The record has
never been selected." message received when have Auto create vendor record turned
on and edit existing vendor to have AP EFT+ method of payment (#711)
o Name PNC should be included in description for format US-PNC-FX-R2 (#653)
o PL-SEB-0511 format is incorrectly zero padding amount (#671)
o Setting up to use virtual companies, vendor eBanking details screen does not work.
Fixed (#648)
Updated: December 24, 2014
Page 42
o
Vendor eBanking details add button that would allow users to bring in list of mass
vendor that are setup for ACH method of payment and/or payment specification (#424)
Revision 5.1.4 – 9/28/2012
















PP –Description of HUNTINGTON_ARP positive pay format displays as Hunting Bank – ARP
(#536)
PP – The description of the positive pay Wells Fargo Bank - Customer Refunds and Wells Fargo
Bank - Payee Match formats are not meaningful (#553)
PP - AX 2012 R2 Tap beta testing AX bank records the check using dummy vendor and not
employee the check was issued for (#611)
PP – Positive Pay format request for Bank of America (#630)
PP – Positive Pay format request for Canadia (#628)
eBankRec –Electronic Bank Reconciliation File Format has not been setup for this bank account
in Event log received. (#634)
APEFT – Weekends are included when calculating Effective Date (#620)
APEFT – ACH record 1 - Immediate Destination and Immediate Origin need to be left padded
instead of right padded (#621)
APEFT – EDI payment spec doesn't restrict to format (#623)
APEFT – IBAN number on Vendor payment spec screen is enabled (#638)
PP – Need to make sure that new Positive Pay reports are in both AX 2009 and AX 2012
branches (#591)
APEFT – AP EFT format request US-PNC-FX-R2 for txn types Wire 103, Multi-CurrencyVOS (#449)
APEFT – ACH 6 record trace number should be Originating DFI Id (#643)
System - Need to standardize the way changes are made to AX objects (#586)
System – Files in the Formats and Sample Files folders are Read-only (#570)
System –Version of the eBanking model displays as 1.0.0.0 when import the model (#540)
Revision 5.1.3 – 9/16/2012









Bank Accounts - Receive "This field is required" in Bank account referencing the PP, BR, and LB
paths when PP, BR, LB, and EFT are registered but only want AP EFT defined for the bank
account (#569)
APEFT - AP EFT File format for Domestic Kroner file name madeoswedenBG4009en.pdf (#450)
APEFT - Include vendor's email address in the Infolog when email fails (#571)
APEFT - Truncation in SKS_PP_HeaderTrailer FormatID field. File formats greater than 30
characters long in when they are added to DB's predating 8/1/2012 build. (#604)
APEFT - Email format/data (#576)
APEFT - Add option to file format payment spec to use bank check number (#599)
Install - Missing Lockbox file formats (#601)
Method 'send' in COM object of class 'CDO.message" returned error code 0x8004020f (#598)
APEFT - Add Infolog message after running Validate EFT+ when validation passes. on the main
Payment journal screen (#564)
Updated: December 24, 2014
Page 43
















APEFT - The Active checkbox and the Enable method of payment/payment spec in journal
checkbox in the Vendor eBanking details screen do not default as checked like they do in AX
2009. (#471)
APEFT - Issues with the AP EFT+ audit report (#558)
APEFT - Payment amount on AP EFT+ file details displays as negative amount but the Payment
total on Create and send AP EFT+ files shows positive amount (#573)
APEFT - The Selected payment journals field count can go negative in the AP EFT+ select/view
payments screen (#544)
APEFT - If the Create and send AP EFT+ files grid is empty and the Select/view payments grid is
empty when the user clicks on the Select/view payments button the message "Form cannot be
called directly." Displays (#543)
APEFT - When checking the box Company ids are unique by payment specification, the fields for
PPD, CCD and IAT that were disabled disappear from the screen. (#606)
APEFT - When File id modifier is set to Numeric (1-9) and more than 9 files are created in the
same day, the file id modifier is incremented to 10, 11, 12, etc. instead of reset at 1 which
causes the field placement in the ACH file to be incorrect. (#609)
APEFT - The RDFI ID that is displayed in the ACH file for an IATB transaction type in record 714,
field 41-74 is incorrect. (#614)
APEFT - Show payments already selected check box is enabled for a Transmitted status EFT line
(#560)
APEFT - Unable to include an EFT payment previously included in a different EFT file (result of
bug 537) (#554)
APEFT - Format request Bank of America - Outsourced check printing (#457)
eBankRec - Unable to maximize Imported electronic bank reconciliation file details (#547)
Lockbox - Create payment journal you can change the document date would like the transaction
date changed to the document date as well. (#280
Lockbox - External settlement file dialog does not default to the directory set up for that
customer. (#617)
Lockbox - Multiple issues with Invoice lookup for lockbox want the column "Invoice reference"
renamed to "lookup type" (#594)
Lockbox - Lookup options for Lockbox allows having 2 lookup types that are the same not sure
how it will decide which one to use (#595)
Revision 5.1.2 – 8/16/2012










GA release for AP EFT Plus!
Lockbox – when importing BAI2 files, split into separate LB journals by batch
Lockbox – manage “in use” when multiple users are editing LB journals
Lockbox – record routing and account numbers to use in matching customers
Lockbox – add “None” as a settlement method, by customer (settlement is done manually)
Lockbox – capability to import settlement data independently of main lockbox file (separate files
provided by customers) - External Settlement.
Lockbox - External settlements can be for multiple customers
Lockbox - Credit note support
Lockbox - Secondary invoice match support
Lockbox - Payment reassign button added to Workbench screen
Updated: December 24, 2014
Page 44






Lockbox - Ability to specify Journal name by Bank Account
Lockbox - Multiple BAI2 formats supported
Lockbox - RTN/Acct will only save off now if workbench is pushed to a payment journal
Lockbox – Provide option to match by multiple criteria (Invoice, Bill of Lading, Customer
Purchase Req number, SO number)
eBankRec - Click-n-Match allows flexible matching (1 AX txn to Multiple bank txns, Multiple AX
txns to 1 bank txn, Multiple AX txns to Multiple bank txns)
Compiled with AX2012 RTM
Revision 4.4.4 – 3/29/2012



Compiled with AX2012 RTM
Lockbox – Added image identifiers
Registration – removed Task users from licensing key
Revision 4.3.34 – 3/5/2012





AX 2012 RTM build
AX 2012 samples files need to be updated for advanced bank reconciliation (#122)
AX 2012 sample files need to be updated for lockbox (#123)
When two companies with the same bank account id and eBanking is virtualized multiple errors
are occurring in Positive Pay (#138)
The SKS.Common.dll file is pulling the Vendor Name from the Checks Recipient name when it
should be pulling from the Vendor master address name field (#112)
Revision 4.3.32 – 1/16/2012


Installation revised to always install SKS.Common.dll on the server
Bug 80 – Issue with using more than 100 companies with virtual companies or organizational
model. Fixed.
Revision 4.3.3 – 12/22/2011








eBanking Setup parameters - enhanced user count licensing based on Task + Functional +
Enterprise users. HTML help not yet included
eBankRec Adv– added journal level matching (AX journal total matching to bank entry)
eBankRec Adv– imported transaction that creates a GL tran doesn’t get a bank tran type – fixed
eBankRec Adv– enhanced to support GL journal level matching in addition to AP and AR
eBankRec Adv–AR payment with a payment fee was not matched – fixed
eBankRec Adv–unable to clear an imported txn using Check/Deposit slip number – fixed
eBankRec Adv–unable to match an imported txn when Check/Deposit slip number included a
special character – fixed
eBankRecAdv – transactions do not import when followed by txns set to “Do Not Import” - fixed
Revision 4.3.0 – 8/17/2011
Updated: December 24, 2014
Page 45

eBankRec Adv – enhancement to match payment journal total to a bank statement entry (beta).
Revision 4.2.2 – 11/29/2011

eBanking Setup parameters - enhanced user count licensing based on Task + Functional +
Enterprise users. HTML help not yet included
Revision 4.2.1 – 8/24/2011

Beta release of eBanking for AX 2012. HTML help not yet included
Updated: December 24, 2014
Page 46
Appendix A – Setting up eBanking Security
Security layers
The eBanking Suite uses the AX 2012 security layer model. An understanding of Roles, Duties, Privileges,
Entry Points and Permissions is required to implement eBanking Security. Please review the AX
documentation for details on these topics.
System tools
AX provides screens that allow Administrators to assign users to role and assign duties to roles and view
privileges.
The Application Object Tree (AOT) can be used to review details related to security. A new Security
grouping is in the AOT. Roles, Duties and Privileges for the eBanking Suite can be viewed here. All
eBanking Suite security objects are prefixed with SKS_. On any security object you can right-click and
choose Add-Ins -> Security tools. From there the selecting will change based on which security object
you are on. The choice will either be View related security objects or View related security roles.
On each form, you can look at the permissions in the AOT. Read, Update, Create and Delete each have
their own set of permissions. The majority of the permissions are auto-generated. You can use the area
to view or override permissions. The most common scenarios are adding table permissions to a form,
excluding specific controls or adding associated forms.
Setting up eBanking security
The eBanking Suite ships with pre-defined Privileges and Duties. The Duties are added to pre-defined AX
Roles. The Privileges and Duties are separated by module – Positive Pay, eBank Reconciliation and AR
Settlement w/Lockbox (Lockbox). They are also separated into security tied to Read permissions and
security tied to CRUD (Create, Read, Update Delete) permissions.
Duties
For eBanking, the duties are separated between Policies (Setup) and Process. All screens needed to
perform Setup are in the duties with the AOT name of Policies. All screens needed to perform
processing are in the duties with the AOT name of Process.
Duties by module:
Duty (AOT name)
Positive Pay
SKS_PP_PoliciesEnable
SKS_PP_PoliciesInquire
SKS_PP_ProcessEnable
SKS_PP_SelectionOverride
SKS_PP_ProcessInquire
Duty description
Maintain eBanking Positive Pay policies
Inquire into eBanking Positive Pay policies
Enable eBanking Positive Pay processing
Enable eBanking Positive Pay check selection override
Inquire into eBanking Positive Pay processing
Electronic Bank Reconciliation
Updated: December 24, 2014
Page 47
SKS_BR_ProcessEnable
SKS_BR_ProcessInquire
SKS_BR_PoliciesEnable
SKS_BR_PoliciesInquire
Enable eBanking Reconciliation import
Inquire into eBanking Reconciliation import
Maintain eBanking Reconciliation policies
Inquire into eBanking Reconciliation policies
Lockbox (AR eSettlement w/Lockbox)
SKS_LB_PoliciesEnable
SKS_LB_PoliciesInquire
SKS_LB_ProcessEnable
SKS_LB_ProcessInquire
Maintain eBanking Lockbox policies
Inquire into eBanking Lockbox policies
Enable eBanking Lockbox processing
Inquire into eBanking Lockbox processing
APEFT Plus!
SKS_EFT_AutoCreateEFT_ProcessEnable
SKS_EFT_ProcessEnable
SKS_EFT_ProcessInquire
SKS_EFT_PoliciesEnable
SKS_EFT_PoliciesInquire
Enable AP EFT+ create now processing
Enable eBanking AP EFT+ processing
Inquire into eBanking AP EFT+ processing
Maintain eBanking AP EFT+ policies
Inquire into eBanking AP EFT+ policies
AREFT Plus!
SKS_EFTAR_ProcessEnable
SKS_EFTAR_ProcessInquire
SKS_EFTAR_PoliciesEnable
SKS_EFTAR_PoliciesInquire
Enable eBanking AR EFT+ processing
Inquire into eBanking AR EFT+ processing
Maintain eBanking AR EFT+ policies
Inquire into eBanking AR EFT+ policies
Roles and duties:
The eBanking suite does not add any pre-defined roles. It uses the existing AX roles related to the
functions that are extended by the eBanking Suite.
The duties and roles assigned by eBanking:
Duty name
Positive Pay
Maintain eBanking Positive Pay policies
Enable eBanking Positive Pay processing
Enable eBanking Positive Pay check selection override
Inquire into eBanking Positive Pay policies
Inquire into eBanking Positive Pay processing
Electronic Bank Reconciliation
Maintain eBanking Reconciliation policies
Updated: December 24, 2014
Role name
Treasurer
Treasurer
Treasurer
Accounting manager
Financial controller
Accounting manager
Financial controller
Treasurer
Page 48
Enable eBanking Reconciliation import
Inquire into eBanking Reconciliation policies
Inquire into eBanking Reconciliation import
Lockbox (AR eSettlement w/Lockbox)
Maintain eBanking Lockbox policies
Enable eBanking Lockbox processing
Inquire into eBanking Lockbox policies
Inquire into eBanking Lockbox processing
APEFT Plus!
Maintain eBanking AP EFT+ policies
Inquire into eBanking AP EFT+ policies
Updated: December 24, 2014
Treasurer
Chief financial officer
Accountant
Accounting manager
Accounting supervisor
Financial controller
Chief financial officer
Accountant
Accounting manager
Accounting supervisor
Financial controller
Accounts receivable payments clerk
Accounts receivable payments clerk
Collections agent
Collections manager
Chief financial officer
Accounts receivable clerk
Accounts receivable manager
Accountant
Accounting manager
Accounting supervisor
Financial controller
Accounts receivable centralized payments clerk
Collections agent
Collections manager
Chief financial officer
Accounts receivable clerk
Accounts receivable manager
Accountant
Accounting manager
Accounting supervisor
Financial controller
Accounts receivable centralized payments clerk
Accounts payable payments clerk
Chief financial officer
Accountant
Accounting manager
Accounting supervisor
Financial controller
Accounts payable centralized payments clerk
Page 49
Enable eBanking AP EFT+ processing
Inquire into eBanking AP EFT+ processing
AREFT Plus!
Maintain eBanking AR EFT+ policies
Inquire into eBanking AR EFT+ policies
Enable eBanking AR EFT+ processing
Inquire into eBanking AR EFT+ processing
Treasurer
Accounts payable clerk
Accounts payable manager
Accounts payable payments clerk
Chief financial officer
Accountant
Accounting manager
Accounting supervisor
Financial controller
Accounts payable centralized payments clerk
Treasurer
Accounts payable clerk
Accounts payable manager
Accounts receivable payments clerk
Collections agent
Collections manager
Chief financial officer
Accounts receivable clerk
Accounts receivable manager
Accountant
Accounting manager
Accounting supervisor
Financial controller
Accounts receivable centralized payments clerk
Accounts receivable payments clerk
Collections agent
Collections manager
Chief financial officer
Accounts receivable clerk
Accounts receivable manager
Accountant
Accounting manager
Accounting supervisor
Financial controller
Accounts receivable centralized payments clerk
Privileges
Privileges and entry points can be reviewed in the AOT using the methods described in the System tools
section above. The eBanking Suite uses menu items as the entry points defined in the privileges.
Updated: December 24, 2014
Page 50
Appendix B – Organization hierarchies in eBanking
Overview
In AX 2012, a new concept was introduced for managing organization hierarchies. The changes help
support scenarios for viewing data across multiple organizations including but not limited to companies
(called legal entities in AX 2012). This is the eventual replacement to virtual companies. In AX 2012
virtual companies are still supported.
Here is a link to an article on Organization hierarchies:
http://technet.microsoft.com/en-us/library/hh242144.aspx
eBanking support
eBanking needs to support the new organization hierarchy and provide backward compatibility support
for virtual companies. The organizational hierarchy is used to determine which companies will be
included in eBanking. Positive Pay and Bank Rec have new “Organization hierarchy purposes” defined
and Lockbox uses the out of the box “Centralized purpose”. The Organizational hierarchy is added to
the organization hierarchy purpose.
Below are two different Organization hierarchies (CEC and CEE). In each example, all of the companies
(legal entities) shown in the hierarchy would be available.
Updated: December 24, 2014
Page 51
Positive Pay
Checks from any companies in the organization hierarchy attached to the eBanking Positive Pay purpose
and that the user has access will be available to include in the Positive Pay file. If no companies are in
the organization hierarchy, virtual company setup will be used. If no virtual companies are found, the
current company will be used.
Electronic Bank Reconciliation
Bank accounts from any companies in the organization hierarchy attached to the eBanking Bank
Reconciliation purpose and that the user has access will be imported. If no companies are in the
organization hierarchy, virtual company setup will be used. If no virtual companies are found, the
current company will be used.
AR eSettlement w/Lockbox, APEFT Plus!, AREFT Plus!
Lockbox and AP/AR EFT+ use the out of the box organization hierarchy purpose called “Centralized
payments” to determine which companies should be used when finding Invoices.
Setting up organizations
Use the Organization administration menu to setup organizations. Under Setup -> Organizations, there
are multiple screens. Organization hierarchies is used to layout the organization structure. Organization
hierarchy purposes lists the purposes and allows you to attach hierarchies to the purpose.
Updated: December 24, 2014
Page 52
Security
Security in the organization hierarchy is controlled by the organizations assigned to the roles in the User
form. For each role listed for the user, you can click Assign organizations and grant rights to all
organizations or specific organizations. This security restricts the companies that you can see in an
organization hierarchy.
Setup data
In AX 2009, setup data like File formats could be shared using virtual companies. In AX 2012, this is done
differently if you are not using virtual companies. To share data in AX 2012, you need to change the
table property “SaveDataPerCompany” to false. This will allow the data to be saved once in AX and used
by all companies.
Appendix C (below) lists the tables that should be placed in a table collection to support virtual
companies. This same list can be used to share data across all of the companies. If using virtual
companies in AX 2012, the setup in Appendix C (the same as documented in AX 2009) should be used.
It is not mandatory to share the setup data if using Organization hierarchies. The companies will be
determined based on the Organization hierarchy purpose. Sharing setup data is a convenience to allow
users to not have to repeat the setup in each company.
Updated: December 24, 2014
Page 53
Appendix C – Virtual Company Setup
The eBanking Suite supports the use of virtual companies to centralize processing. eBanking does not
require the use of virtual companies but can be configured to take advantage of any virtual company
setup you may have.
To set up virtualization you need to create or update a table collection. This is done via the AOT
(Application Object Tree) -> Data Dictionary -> Table Collections.
If you need to create a new table collection it will need to be added to a virtual company:
1. Go to Administration -> Setup -> Virtual company accounts
2. Choose a Virtual company or create a new one.
3. Add Company accounts if necessary
4. Add the new Table collection to the selected table collections.
Positive Pay
Using virtual companies allows selecting checks and processing files for multiple bank accounts across
multiple companies.
The following eBanking tables must be placed in the table collection:
 SKS_PP_File
 SKS_PP_FileDetail
 SKS_PP_FileFormat
 SKS_PP_HeaderTrailer
The following table is optional as to being placed in the table collection (it would only be done if also
using eBank Rec Advanced and/or Lockbox Processing):
 SKS_PP_Setup - this table links to the LedgerJournalName table. If this table is virtualized or if
the journal name that you are using in all companies is the same, the SKS_PP_Setup table can be
virtualized.
Electronic Bank Reconciliation
Using virtual companies allows for processing a single file that contains transactions for multiple bank
accounts across multiple companies.
The following eBanking tables must be placed in the table collection:
 SKS_BR_BankHeader
 SKS_BR_ErrorLog
 SKS_BR_FileFormat
 SKS_BR_FileFormatDetail
Updated: December 24, 2014
Page 54
The following tables are optional as to being placed in the table collection:
 SKS_BR_FileFormatTranMapping - this table links to BankTransType, LedgerTable and Dimension
tables. If those tables are already virtualized, the SKS_BR_FileFormatTranMapping table can be
virtualized.
 SKS_PP_Setup - this table links to the LedgerJournalName table. If this table is virtualized or if
the journal name that you are using in all companies is the same, the SKS_PP_Setup table can be
virtualized.
AR eSettlement w/Lockbox
Lockbox allows processing payments against invoices within any company when AX is configured to
allow for centralized processing. It uses the same rules as the AX Payment Journal as to centralized
processing.
The following tables are optional as to being placed in the table collection:
 SKS_PP_Setup - this table links to the LedgerJournalName, CustPaymMode and
NumberSequence tables. If these table are virtualized or if the journal name that you are using
in all companies is the same, the SKS_PP_Setup table can be virtualized.
 SKS_LB_FileFormat
 SKS_LB_FileFormatDet
APEFT Plus! & AREFT Plus!
APEFT Plus! allows processing payments against invoices within any company when AX is configured to
allow for centralized processing. It uses the same rules as the AX Payment Journal as to centralized
processing.
The following tables are optional as to being placed in the table collection:






SKS_PP_Setup - this table links to the LedgerJournalName, CustPaymMode and
NumberSequence tables. If these table are virtualized or if the journal name that you are using
in all companies is the same, the SKS_PP_Setup table can be virtualized.
SKS_EFT_FileDetail
SKS_EFT_FileFormat
SKS_EFT_FileFormatLookups
SKS_EFT_FileFormatNotes
SKS_EFT_Setup – this table is linked to other tables that also may need to be virtualized
Notes to existing customers – switching to virtual companies
If a table is setup for individual companies and then later, the table is virtualized, all of the existing data
will no longer display in the screens. It is still in the database, it just won't be displayed.
An example: File format in company CEU and company CEE. Create a virtual company CCC and place
the file format table in the virtual company. Now if in CEU or CEE, it will only display record for CCC.
The dataAreaId field in the file format table contains the company id. If the dataAreaId was changed to
Updated: December 24, 2014
Page 55
CCC on an existing CEU or CEE record, it would start displaying in the virtual company. So a user would
need to decide if they wanted to change an existing record or create a new record. If they change
existing records, they will most likely need to also eliminate a record. So CEU would become CCC and
CEE would get eliminated.
Here’s a blog post that gives more information on this process: http://blog.colesys.com/?p=15
Updated: December 24, 2014
Page 56