Bank File Definitions can be very boring to create because each bank has different configuration setup. We spend most of our time in designing the configuration setup and testing it in the test environment. Once we have finished with the testing in the test environment, how can we configure the same bank file definition in the live folder?
We have the option of manually entering the definitions in the live folder which could be very time consuming and prone to types with all those formulas with multiple commas, semicolons, brackets, etc and there is a chance of doing mistakes in the setup.
To overcome that we could use the copy option. We need to navigate to Setup >> A/P-A/R accounting >>Bank file definitions.
However, copy of objects are only allows duplicating one definition at a time. If we wish to copy it on a different server, there isn’t a way to copy the bank file definition from here.
We can also take patch of the configured bank file definition. For that we need to navigate to Development >> Utilities >> Patches >> Patch creation
As shown in above figure we will select the destination type as ‘Client’. We will select the folder from which we have created bank file definition as we have created it in ‘SEED’ folder. We will select type as ‘AAA’. Click on action button on object name field and select the ‘Data models’
Setup template screen will be displayed as shown in below figure 4. Select data model as ‘TABFILBAN’ and click on the ‘OK’ button. After that we will return to the patch creation screen and an Object name formula is generated.
A patch of AAA type corresponds to a line coming from a setup model. It uses a specific format for the element code. This format is one of the two following:
MODELE~CODE_LEG~CODE_TRS~=’FORMULE_SELECTION’
MODELE~CODE_LEG~CODE_TRS~CLE~SOUS_CLE~SOUS_SOUS_CLE…
MODELE corresponds to the data model used to describe the tables to extractt
CODE_LEG corresponds to the legislation code, which can be empty (in this case, two ~ are placed one after the other)
CODE_TRS corresponds to the transaction code, which can also be empty
FORMULE_SELECTION is a filter condition. Any text chain must be put ‘in double quotes’ since the formula is put in ‘simple quotes’.
CLE~SOUS_CLE~SOUS_SOUS_CLE (the number of sub-keys being variable) corresponds to the specific case when it is required to select a key value corresponding to the model main table. It is only possible when calling up a model (AAA code) from the patch creation and then opening the window making it possible to select the model and enter the key by direct search.
We are using the first format. We will change the Object name from TABFILBAN~~~=” to TABFILBAN~USA~~=” which will filter our patch to include only Bank file definitions for the USA legislation.
For Type of patch, we will select Standard. Then, click OK to generate the patch.
The file is generated to our desktop’s Downloads directory and the file name will start with the letter “F.” We are ready to apply the patch. The file can be copied to the server of our choice for Patch Integration. Please note, The Patch integration process will copy over existing records if their identities are the same. Make sure to generate a patch from the same version and patch level as your intended target because the table structures may have changed.
Hence by doing above process in Sage X3, we can copy or take patch of the bank file definitions configuration.