Business Patterns
By means of different connections (collaborations) between the instances (objects) of individual classes of the enterprise model, a wide variety of scenarios (use cases) can be represented in an enterprise.
InstantView's basic enterprise model comprises around 200 model classes and is essentially divided into 5 categories:
- Data types (simple and intelligent)
- Information objects
- Business properties
- Monitor objects
- Transaction objects
The business objects correspond to the master data and the transaction objects to the transaction data, whereby the data types as well as the information objects are used to define master and transaction data more precisely.
Through the rule-based posting of transaction objects, master data can be statistically evaluated by means of monitor objects (OLAP).
The 5 categories of the enterprise model in InstantView are colour-coded in the business patterns for better differentiation according to the following legend:
Business patterns of the following areas are documented here:
- Partner
- Products
- Business Process Modelling
- Activities
- Evaluations
- Office functionality
- Technical Patterns
Partner
| Business Pattern | Description |
|---|---|
| Companies | |
Companies
| The representation of a company should correspond as far as possible to the real circumstances, e.g. directly to the details of an extract from the commercial register and e.g. additional data such as branches, affiliated companies, etc.. Related topics: |
Subsidiaries
| ... Related topics: |
Affiliated companies
| ... Related topics: |
Organization Chart
| |
| People | |
People
| |
Employees
| ... Related topics: |
| Partner data | |
Location specific data
| |
Access data
| |
Communication People
| |
Bank details
| Own bank details and bank details of partners can be stored in different complexity |
Products
| Business Pattern | Description |
|---|---|
| Parts | |
Parts
| |
(Service) performance units
| |
| Phantom parts CX_ITEM_PATTERN_PHANTOM | |
| Other real things | |
Industrial plants
| |
Resources
| |
| Part Rolls | |
Sub-assembly set
| |
PID
| |
Sales sets and features
| |
Storage aids
| |
| Part data | |
Price chains
| |
Supplier Agreements
| |
Serial numbers
| |
| Bill of material modelling | |
Allocations
| A single allocation describes a use or a resource of a business object, depending on the point of view. |
| This class is used to describe conditional allocations. Normally, individual allocations are placed in the conditional table to represent different scenarios. |
| An allocation table is a list of allocations. Normally, the list consists of single or conditional allocations. |
Special stocks
| |
CX_INDUSTRIAL_PLANT_PlantGroup
|
Business Process Modelling
| Business Pattern | Description |
|---|---|
Business processes
| A business process is mapped in ClassiX using the class CX_WORK_FLOW as business process identifier and - for the possible states of the documents within this business process - with objects of the class CX_STATE_MONITOR. Related topics: |
Business processes
| A business process is mapped in ClassiX using the class CX_WORK_FLOW as business process identifier and - for the possible states of the documents within this business process - with objects of the class CX_STATE_MONITOR. Related topics: |
(Digital) floating folders
| In CyberEnterprise, (digital) circulation folders can be created for all receipts, but also for any associations to e.g. documents, Excel, Word or pdf files, etc. and passed on electronically between users. Each user recognises in the folder "My Floating Folders" the operations to be processed by him. |
Controlling | |
Company codes
| Company codes are necessary to be able to plan on time, for example, for external warehouses, independent of local stock levels. |
KPI Auditor
| The following pattern describes the interrelationships for the determination of key figures for supplier evaluation. The KPI Auditor (CX_KPI_AUDITOR) is used to define key figures that are created as attributes. The KPI Auditor is connected to the workflow (CX_WORK_FLOW) of the order items (in this example CX_TRANSACTION instead of CX_LINK_TXN). A logcube (CX_LOG_CUBE) is created between the KPI Auditor and the supplier via the transaction description when the order item is posted. Both objects can be accessed from the transaction description via the order item. The transaction description writes the key figures in the respective logcubes (all, year, month) and posts the transaction. |
|
Activities
| Business Pattern | Description |
|---|---|
| Financial Accounting | |
Open items debtors
| |
| Sale | |
Sales order
| |
Coupling offer/order
| |
Structure of offer/order
| |
Advance requirements
| |
Service provider group
| |
Order item with sales set type 1 and purchase set
| |
Order item with sales set type 3 and purchasing set
| |
| Purchasing | |
Delivery agreements for ordered articles
| |
Approved
| |
Self-provision
| Self-provision to a supplier, these can be specified in a parts request or a purchase order |
| Manufacturing | |
Disposable assembly
| In order to be able to control the dispositive use of parts within a parts request, you can store corresponding information in the master parts lists |
Exploded production parts list
| Exploding a BOM creates a tree structure with objects of the class CX_ALLOCATION_TXN. The hierarchy of these objects initially also determines the dispositional use of the parts, but can be overwritten by additional specifications. |
Parts request
| Part requests are documents which are automatically generated from a parts planning according to the Gozinto method. The starting point is again a production part E1, which consists of parts B2 and B3, etc. |
Evaluations
| Business Pattern | Description |
|---|---|
Customer sales statistics
| |
| |
Order-accompanying final costing
| |
Parts accounts
|
Office functionality
| Business Pattern | Description |
|---|---|
MS Office integration
| |
Vocabulary
| CX_PHRASE and CX_SIGNIFICATION objects are linked via "clearingObjects". A CX_PHRASE object of a language can reference several CX_SIGNIFICATION objects. |
Technical Patterns
| Business Pattern | Description |
|---|---|
Saved lists
| |
| Reports and report presentation CX_REPORT | |
Search terms
| |
Transaction Descriptions
| Transaction descriptions control the processing (posting) of all documents in ClassiX (the objects of class CX_TRANSACTION) |
Wrapper
| |
Access rights
|
;){kind=link}