Baan / ERP LN Freight Management Freelance Trainer Required


We currently require a Freight Management Freelance Trainer for Baan / ERPLN.

Training needs to be provided remotely through Skype (Voice Call & Screen Sharing).

Candidates who are having over 2 years of experience in Frieght Management of Baan/LN ERP,kindly send across your updated CV and contact details to fullonbaan@gmail.com

 

Advertisements

ERP LN Technical Requirement in UAE


There is a requirement for LN Technical Consultant for UAE location.
Requirement is candidate should have 4-5 years of total experience out of which 3-4 years
of LN technical experience.

Exposure to Customization,Development and AFS.

Additional Benefits:
Medical + Ticket , Annual Bonus subject to individual and company performance.

If interested, please mail your updated resume asap to fullonbaan@gmail.com.

Financial Limitations in Older version of Baan


Financial Limitations

Accounts Receivable:

Cashbook enhances the cash application functionality in BAAN. BAAN limitations in the ACR space include:

  • No ability to apply cash to multiple customers at the same time.
  • Deductions/Debit Notes/Credit Notes are a separate function to cash application.
  • ACR is not flexible and automatically posts transactions rather than leaving the user with discretion as to when to post journals.
  • ACR batches need to be closed the finalization posts the amounts to financials. Cashbook can post all auto matched transactions while creating a separate batch for unallocated to be processed by the AR clerks.
  • Limited access to additional information.
  • No integration with bank statements.
  • No bank lockbox integration.
  • No ability to apply cash across multiple BAAN companies.

AR Credit & Deduction Management:

The limitations with BAAN financials for credit collections & deductions include:

  • No ability to put notes on customer accounts.
  • No ability to re-print invoices quickly & easily.
  • No facility to rapidly send fax/pdf/email to customers detailing invoices outstanding and cash required for collection.
  • Not a user-friendly order-hold process.
  • No method of tracking collection agent’s accounts & DSO achievements.

Accounts Payable:

Cashbook has added to BAAN payment functionality by providing Electronic Payment & Email Remittance functionality in BAAN.
BAAN limitations in the ACP space include:

  • Selection and de-selection of vendors and invoices is done in non-intuitive fashion.
  • Difficult process to manipulate the total payment amount.
  • Bank reconciliation process is non-existant.
  • Ability to make payments in one process for multiple finance companies not in the same group company.
  • Ability to make payments in multiple currencies.
  • Email/Fax to Supplier with payment details for all companies invoices.

Bank Reconciliation:

Cashbook has given BAAN bank reconciliation functionality by downloading AR & AP cash receipt and payment information directly from the ACP200 and ACR200 tables as well as the GLD 106 table into one central location. These cash transactions can then be dynamically compared to incoming bank statements from any global location.

Transaction Handling in Baan


With respect to database actions, a transaction is a sequence of related actions that are treated as a unit. The actions that make up a transaction are processed in their entirety, or not at all. 


A transaction ends with the function commit.transaction() (all changes made during the transaction are stored in the database) or with the function abort.transaction() (no changes are stored in the database). A transaction starts either at the beginning of a process, with the function set.transaction.readonly(), with the function db.lock.table(), or after the preceding transaction has ended. A transaction is automatically rolled back (that is, it is undone) when a process is canceled and if a program ends without a commit.transaction() or abort.transaction() after the last database call. Undoing a transaction is only possible if the underlying database system supports this. 


Certain database actions cannot be placed within a transaction, because they can not be rolled back. These actions are: db.create.table(), db.drop.table(), and set.transaction.readonly(). These functions can be called only at the start of a program or after the end of the preceding transaction. 


You can set a retry point immediately before a transaction. In case of an error, the system returns to this point and re-executes the transaction from there.


A read-only transaction is a transaction in which you are permitted only to read records (without lock) from the database. You retain read consistency during the entire transaction. This means that during the transaction your view of the database does not change, even if other users update the records. A read-only transaction starts with the function set.transaction.readonly() (this must be called after ending the preceding transaction or at the beginning of the program) and ends with a commit.transaction() or abort.transaction(). A consistent view consumes a large amount of memory, so a read-only transaction must be as short as possible; user interaction during the transaction is not recommended

Data Flow through the Baan ERP Architecture


Note that the database driver provides an interface between the Baan ERP application server and the specifi c RDBMS server being used. The flow of data through the system is described below. 

When a user performs an operation at a GUI workstation, the user interface server interprets the input and sends the information to the Baan ERP application virtual ma- chine. Based on the information it receives, the application server causes the appropriate application object to be executed. 


When a running application object requires information that is stored in the database, the application server sends the request to the database driver. Data requests from the client applications are RDBMS independent and are made using BaanERP SQL, an RDBMS independent SQL language.


When the application server executes a database query from an application program, it first determines whether or not there is a running database driver available to process the query. If there is no database driver running,or if the running database driver instances are communicating with a database server other than the one storing the needed data, the application server starts a new instance of the database driver. The application server parses the BaanERP SQL database query it receives from the application object and sends an internal representation of the query to the database driver. The internal representation of the query that the database driver receives is still RDBMS independent. 


The database driver translates the database query into an appropriate query using SQL statements compatible with the specific RDBMS being used. Each database driver takes advantage of the design of the particular RDBMS that it supports so that the resulting SQL statements are valid for the RDBMS and provide the best possible performance. The RDBMS specific SQL statements are then submitted to the RDBMS server,which processes the data request. When the RDBMS has processed the query, it returns the data to the database driver. Any error conditions are caught and handled by the database driver. The database driver then returns the data and status information to the application server, where it provides the information to the application that requested it. The application server may also send a message to the user interface server, which displays an appropriate message on the users workstation.