Related links
Homepage
User documentation
Uživatelská dokumentaceFI - Finance Management
Framework Core functionality
- AyMINE Framework Server
- frmFrm – provided functionality
- System Rights
- System messaging
- AyMINE Business – Price calculation
- Strings and translations
- Export collection of objects
- AyMINE Framework management FAQ
- The AyMINE licence model
- AyMINE On-premise
- System events
- Mutli-client architecture
- Import collection of objects
- User sessions
- Default server methods
- Client-defined object attributes
- Common Libraries
Module - support for management
Libraries & Lincences
Mobile & Web Application
- Runtime debugging
- System console
- AyMINE Application
- In-line table edit support
- Object scripting API – object lang
- Application object structure
- Multilingual support
- View of a single object – detail
- Is using EVAL / feval method risky?
- Included library – String operations
- Cliplink
- Object API – object <g>
- API – Data object
- Object scripting API – object User
- Object view definition
- Framework support for Drag & Drop
- Common libraries
- Multiple-object update implementation
- fClip & fCliplist
- Offline persistent objects
- Mobile application
HR - Human Resources
System Management (part of framework)
Task, Project, Quality
Task & Task pattern
CMS - Content Management & Web API services
Acquisition and purchase support
- Acquisition business view
- Acquisition business data model
- Pruchase – technical implementation
- Acquisition data view
Delivery supports evidence and process steps related with the asset order and delivery. During the delivery process user can also create the delivery evaluation as a part of the supplier quality evaluation and qualification.
Acquisition business view
The delivery business view presents the following view:
Acquisition business data model
Business objects of the acquisition support:
Pruchase – technical implementation
Acquisition object
Acquisition encapsulates the whole acquisition and delivery process. It contains data necessary to manage the acquisition process as well as links order and delivery data.
Acquisition could be a multilayer object where super-layer encapsulates the subordinated. Super-layer is used only in case that single acquisition requires acquisition from several suppliers. The decision process is then linked with the super-object and all parts of the acquisition is approved at once
At the lowest level, single acquisition
- Can be linked with several suppliers requested to make a bid
- Is linked with single supplier with offer
If acquisition is split between two or more suppliers during the offer evaluation, the acquisition is split to two or more sub-acquisitions single for each supplier.
Purchase Delivery object
Note: Purchase delivery is internally managed as the same object as the selling-deliery object. It supports both processes.
Changes from abstract ancestor
- Delivery defines its own user types
Delivery record
Records are object implemented in the task module. They are reused here. Delivery record is one of the supported types for records and so extension is not necessary.
Acquisition data view
Appropriate part of the data model:
Other modules extensions
Decision
Delivery object extends list of objects that can be linked with the decision