An ERP program accesses these tables, to capture a job. Rules laid down in the ERP system for data collection, for example, that a job only in conjunction with a customer can be attached. This prevents inconsistent data is generated. At this level, complying with the rules is checked. Now, a user decides to go, so in the database, and create the order without customers, directly into the Excel spreadsheet that can’t be prevented at this level. The upper level business rules were abrogated. Such an approach with the abas business software is not possible through the consistent object-oriented encapsulation. In the overall design of the abas business software was ensured in General can be changed software core and database only by the development of abas in Karlsruhe. he matter.
This principle allows the abas customers of the first hours until today upgrades to make, without even Once the data is migrating to. Another special feature of the abas database: the clients relieve the database process, by they unpack the data records. This makes no other ERP system. This relieves abas ERP from the beginning of the database process. Traditional standard database perform this action in the database process. In the early 1990s – consideration to use mid-90s default database the abas developers tested the use of other database solutions.
It was influenced by the General discussion on the advantages of standard database, and the consideration was in the room, whether it was not clever, others to determine the development and to set up on their results. Checked the usage became a 1993 Informix of the eponymous company. The database objects were however otherwise required and the necessary standardisation was considered too expensive. The possibility of encapsulating application and database could not withstand the abas claims. FastObjects t7, at that time a product of the company was three years later POET, tested.