There are two alternatives:

1. Define the pathname to the executable (e.g. Winword.exe) in your environment variables. In the session 'Helper Applications', you've to enter only the filename (without the path), e.g. Winword.exe
2. Use the ~ (tilde) to abbreviate the folder name. E.g. C:\Progra~1\Micros~2\Office\Winword.exe

DEM in Baan ERP does include much more powerful functions. Main differences are:

• New model types: Enterprise Structure Model & Business Control Model
• Changed authorization scheme and changed relation with Baan Tools authorizations
• Introduction of Application Components Concept, allowing other application to be included into the DEM model more naturally

More information can be found in the difference studies available in the Download Center.

No, this is no longer possible. Business function can only be created by using session 'Business Functions' (tgbrg2500m000). Note that navigation from a parent business function to his child is still possible in the editor, by using the context (right-mouse button) menu, Activate - Child.

This is possible indeed, with some limitations. Find below the preferred scenario.

• Define in Baan ERP 5.0c environment, the Baan ERP 5.0c component as the running Baan component.
• Import the applications from this running Baan environment.
• Define in Baan ERP 5.0a environment, the Baan ERP 5.0a component as the running Baan component.
• Export the component application data in Baan ERP 5.0a
• Import this component application data in Baan ERP 5.0c
• Define for the Baan ERP 5.0a component the executable as follows: .bwc”.
• For each Baan ERP 5.0a component appli­ca­tion, define in the argument field the session code.

The limitations are:

• For each session in Baan ERP 5.0a, a sepa­rate Bshell will be started
• Subsession authorization doesn’t work for the Baan ERP 5.0a sessions.

Sharing DEM tables is not necessary. In Baan ERP there is the central modeling company (defined in session 'Enterprise Modeler Parameters', tgbrg0100s000) where a DEM company can be defined. Below some reasons, why the central company is implemented the way it is.

1. Both in BaanIV and BaanERP all texts (not helptext) is stored in the current company.
2. Both in BaanIV and BaanERP all helptexts are stored in company 000 (The difference between BaanIV and BaanERP is that in DEM BaanIV created helptexts first were stored in the current company, and afterwards converted to helptext in company 000 (session: 'Convert Text to Helptext'). In BaanERP, helptext is immediately written into company 000.
3. Linking DEM tables (logical table linking), the side-effect is that ALL texts (not only DEM, but also from Distribution, Manufacturing and all other packages) are shared too. That will be in most cases not the intention.
4. That's the reason why the central modeling company is implemented, using a 'company switch', instead of logical table linking. Invoking a DEM session (tgbrg), the company will automatically switch to the central modeling company. The text problem, as stated in point 3 doesn't exist in that case.

To deal with the fact that you often do not want to share the texts of the logistical tables but you do want to share the DEM tables, the following can be done. The minus side of this solution is that you should have already finished creating your DEM-texts, and in case of DEM-text adjustments, you must remove temporarily the table sharing links. If you can deal with this then do the following: Suppose you have your DEM models in company 100, and you have two logistical companies 200 and 201. In 200 and 201 you want to use the DEM models, and store texts of manufacturing/distribution in the companies themselves (200 and 201)

• Do not share any texts tables.
• In company 100 finish up your DEM texts
• Export Version Dump
• Create link from 200 to 100 for tgbrg tables
• Create link from 201 to 100 for tgbrg tables
• Import Version dump in 200 (into a new version (just to be safe), this will place the DEM models in 100, and the texts in 200)
• Import Version dump in 201 (into the same new version, with overwrite = Yes, which will (re)place the DEM models in 100 and put the texts in 201)

If you have to update DEM texts, you must first remove the logical table links, then modify the texts and repeat above mentioned steps. If your people need to keep on using the DEM models during the modification of the texts, make a version dump of the version before you remove the links, then remove the links, import dump in 200 and 201, and delete the versions before you are ready to start above mentioned steps again.

Note: in Baan IVc it is not possible to import into a different version so if you want to be extra safe, before you import, copy the components to a backup version, and when you import, specify also in 200 Overwrite = Yes

Help texts are in BaanERP presented in standard Windows format. The message indicates that the Windows help file is not available on the client. Two steps must be done:
1. The help file must be created (compiled) on the server (once)
2. The help file must be downloaded from the server to each client.
Those actions can be executed from the menu browser using the sessions "Create DEM Help Files on the Server" and "Download DEM Windows help files on the Client". Customers are often using the shared directories to store the helpfiles, to prevent that each Client PC need to download the help files.

In the enterprise structure model, information about where logistical and financial data must be stored (in which logistical and financial company, defined by enterprise unit). Out of each company, the system must know where to find this information. That's why the company must be defined, where the system can find the enterprise structure diagram with the enterprise units.

The link with the logistical company is implicitly created, based on the logistical company, the entities are created in. The entities are linked to enterprise units, so then the system know which logistical company belongs to which enterprise unit.

Schematically:
Entity exist in company - EU linked to entity

Only entities created in the same logistical company can belong to one EU. An EU is always linked to one logistical (implicitly) and one financial company.

The Enterprise Modeler Editor will only work in direct connection with Baan ERP (database). Although Baan doesn't provide a stand-alone editor to their customers, there is a stand-alone DEM compliant editor available, EZ-Modeler. Find more information about this product at EZ-Process Website

These checks are explained in a document, available in the Download Center of this Website.

Minumum requirements:

• Pentium 2
• Internal memory 64Mb
• Windows 98/2000/XP
• Free disk space at least 15Mb

Recommended:

• Pentium 3+
• Internal memory 128Mb

Responsibility codes are linked to a role/activity combination, and indicates the type of responsibility for that combination. Responsibility Codes can be defined in session 'Responsibility Codes' (tgbrg8130m000). If no responsibility codes are linked to a role/activity combination, it will not influence the authorization. But if there are responsibility codes linked, at least one responsibility code (out of the rc's linked to the role/activity) must have the 'execute' parameter on 'yes'

The cause of this message is that the version you're working in, doesn't have the proper license code. This license code is linked to a version and contains encrypted some specific data. If this license code is corrupt, this message pops-up and it's no longer possible to use that version.
One cause of a corrupt license field is a copy of DEM tables from one company to another. For copying DEM data, always the 'Export/Import Version Dump' must be used.
To resolve this, the license code must get the correct value. Due to the fact that this is a secret algorithm, the most simple way is to make a dump of DEM data, instead of the copy of tables.

The enterprise unit is directly linked to a financial company. The logistic company of the EU is determined by the logistic company of the entities within the enterprise unit as defined in tcemm. An enterprise unit is always linked to one (1) financial and one (1) logistic company.

Just to escape from the problem to use a logistic company for each country. Currencies are stored by financial company, so it's now possible to have one logistic company for more countries.

The communication between the editor and BAAN goes through the following steps:
1.When a user saves a diagram, the diagram is written in XML (sort of HTML) format and stored to the local drive in the [DATA] subdirectory.
2.The file is exported to the BAAN database tables. After conformation of the BAAN database that the diagram is correctly stored, the XML-file is transferred to the recycler subdirectory. The recycler subdirectory is created because the diagrams should be only started out of BAAN. Starting the editor by double-clicking on the diagram file in the Windows Explorer can cause communication problems (because the editor can't check if the default started BAAN shell (with a certain company) is the right one where the diagram should be stored).

All bitmaps are stored on the Baan server. During the installation of the editor, all bitmaps will be copied to the local directory on the client. During each startup of the editor, the bitmap directory on the client will be compared with the on the server. If the directories are different, synchronization will take place (from server to client). To add new bitmaps, ftp (UNIX) or copy (NT) the bitmap to the server directory and start up your editor.
NOTE: in the user settings, you can switch of the automatic synchronization. Verify that synchronization is enabled! The synchronization can be disabled to improve performance in case of slow network or telephone connection.

See the document "Model Migration Scenario's" in Download Center for different model migration scenario's in a specific company situation.

For translation purposes, you can create a file with all language dependent descriptions of a DEM Model with session "Export Enterprise Modeler Language Dependent Model data (tgbrg1237m000)". This translation file has the same format as BaanERP software translation files, and can be imported with session "Import Language Dependent Software Components (ttadv6231m000)". The file should always be imported in the same company as where the Export Enterprise Modeler Language Dependent Model data was done. This is different for import/export version data. A version dump can be imported in any company, system or DEM software version.

Consistency and syntax checks are only implemented in the process diagrams, not for the business control model