Actual Path of BW Config Files

I always found issue while creating or copying config file for BAAN as Path showed on BECS is fake and misleading.

Actual Path of these files is located to c:\User\Public\Public Documents\BaanIVorERPLN\Config

Export SQL Queries

How to Export SQL Queries from BAAN.

Simple Answer : Export Data Dictionary(ttiex1284m000).

        When we try this option we found no SQL Query listed in dump.l and no letter for SQL Queries in dump.l. We give one try and imported same dump to other server and found all component imported without any error.

   So we notice that Export DD session exports SQL queries but you will not get query list in dump.l file. Also no attached reports will be exported with SQL Query. We need to export it separately.

Scan Bar Code Data into ERP LN

   We had requirement to scan 2D Bar Code and add records to ERP LN. We got Data Logic GD4400 scanner to scan Bar Codes. We find two way by which we can read Bar Code in ERP LN
1) Reading RS 232 Port and adding records to ERP LN.
2) By putting Data at the point of Cursor(in field)

   In our requirement, user will scan multiple items at a time and then he will confirm the scanned items and then after confirmation data will be sent to respective tables. Bar Code contains comma separated data, that we separated in when.field.change Event of field.
   When we scan Item, scanner put comma separated string in respective field but we need to tab to hit event. We try every single event but nothing works. We tried adding tab at the end of Bar Code Data but in vain.
   In User Manual of Scanner we found programming of scanner. By which we can program scanner. There is List of Bar Code which require to program scanner. First we need to scan Start Mode code so that scanner goes into programming mode after that we can add suffix character by scanning respective character. We set Tab as suffix character and it works. Now user scan Items one by one and item get enter in LN with out tab.

 We are not aware of how to read RS232 port so skip that option.

update.status and update.occ()

When we create session with form field and need to update form field data to table using standard save functionality as "Choice Update.DB". Normally when we use table fields and if we made some changes then system understand the record is modified and update.db will get hit. But whenever we use form fields we need to tell system this field has changed by using following code.

field.:

when.field.changes:

update.status = modify.set

update.occ()

This will force LN to call choice.update.db section.

Suppress Standard Message After Save

This is common requirement while creating update session and updating same by form command. Once we update by using form command function while closing session system display error message "Do you want to save record?".

Now to avoid this we have to tick check box in form command as "Save before Execute" on second form.

Migrate Session from Baan IV to ERP LN

This is regarding migration of session from BAAN IV to ERP LN. Following is the procedure to migrate session from Baan 4 to ERP LN.

1) Copy all session and forms and dump it in to respective package VRC.
2) Copied form are still static form.
3) First go to the GTM and Modify table ttadv200( Session) of 000 company. Update Dynamic Form and Integrated Field to "no".
4) Prior to this make sure your session contains static forms.
5) Then run session Convert Session to Dynamic(ttadv2900m000). Enter session code and hit convert and its done, your session converted to dynamic.

User Exits In ERP LN

             "Wrapper" is very familier word for ERP developer. If you are working in Baan ERP software you will come to situation where you need to modify functionality of Standard session. In those situation you need source code of that session which is usually not available at Client Place. Then you need to have something which do something prior to actual events.

             ERP LN has concept of User Exists which execute before Dal hooks. For this you need to create one program script with extension ".ue". In this script define extern functions such as "before.before.display.object()" for "before.display.object()" in DAL. This "before.before.display.object()" function will get called prior to actual Dal hook.

            Similarly we can define before and after event of every DAL Hook in User Exists. There is no provision for field level checks. It is only works for DAL Hook.

             I will explain it with example..........................