1) Segmented Item Codes
If you want to use segmented item codes, use the Segmented Domains
(ttgfd4122m000) session to define the segments of the Item (item) domain in the
iBaan ERP packages. Each segment represents a certain type of information. The
data that you define in this session is copied to the Item Segmentation
You can use segmented item codes to support:
Clusters for distribution-requirements planning, in Baan Enterprise Planning.
Projects, in iBaan ERP Project.
Bills of materials, in iBaan ERP Manufacturing.
Before you start the Segmented Domains (ttgfd4122m000) session, you must
decide how you want to structure the item codes. After you have created items
and saved the item data, you can no longer change the item-code segmentation.
If you want to define segments for other types of domains, you can also use the
Segmented Domains (ttgfd4122m000) session to do this.
2) Segmented Domains
3) Enterprise Modeler
– Editor has to be installed on the client PC
– User Authorisation by specific role or status
– Default Authorisations for version use
– Workflow is part of the Enterprise Modeling
Major differences exist between DEM IV and DEM ERP. In a bullet point list, the most important would be:
– a total of 6 model views: (the Function/Process/Organization Models found in DEM IV plus the Enterprise Structure Model (ESM – displaying the geographical breakdown of the company), the Business Control Model (BCM – top level decomposition of the functional areas of the business), and last, the Entity Relationships Diagrams (ERD – representing the graphical structure of the data dictionnary of Baan tables)
– in DEM IV, the user was using 3 different editors to handle the 3 different views. In DEM ERP, one single editor, more generic, is used to handle the editing of all 6 views (see above)
– the editors in DEM IV are coded in Baan Tools. In DEM ERP, the editor has been re-writing using OO components to be portable and use XML diagrams definition. The resulting editor is called the EME (Enterprise Modeler Editor) and needs to be installed on the Client PC of the Baan user. Although all editing tasks will be performed on the Client PC and not on the Baan server, the EME is not fully Stand-Alone and still require the diagrams to be saved in the BRG tables on the server.
– the handling of DEM Versions, Reference Models, Project Models are similar from DEM IV to DEM ERP, making the import-export from one to the other possible. It is also possible to back-port from ERP to IV.
– although the diagrams migration from IV to ERP is possible and faily easy to do, an important difficulty reside in the fact that the session codes have been modified in Baan ERP. While a Process Activity (BPA) can be linked to a session in DEM IV (Ex. tiitm0101m000), and that this diagram can be ported to DEM ERP, a disconnect can happen is that session code no longer exits in ERP (because of being replaced by other session codes). In a nutshell, the graphical structure of DEM IV and ERP are compatible but the defined relationships to the underlining applications can see some disconnects.
– on a Business Reference Models side (supplied by Baan), DEM IV saw a extensive list of industry specific models and extentions (Ex. ETO, ATO, MBI, BPM, A&D, etc…). In DEM V, one extensive model (the Hybrid Manufacturing Model HBL renamed to the Enterprise Business Model EBM) is available, and incorporate many of the smaller DEM IV models content. A “Business Profile” configurator enables organization to select the relevant part of the HBL/EBM model related to their industry segment)