Diverse connections (collaborations) among separate instances (objects) of classes
of the business model can display a
wide range of possible business scenarios or use cases.
The basic InstantView®
business model consists out of around 200 classes and splits into 5 categories:
Here, business objects equate to master data
and transaction objects equate to dynamic data. Data types as well as
information objects can be used for a stronger forming of master data and dynamic data.
Transaction object bookings makes it possible to evaluate master
data statistically via monitor objects (OLAP).
For faster recognition, InstantView® ' 5 categories are displayed in the following colors:

Business patterns for the following domains are described below:
| Business Pattern | Description | Preview |
|---|---|---|
| Companies | ||
| Company CX_CORPORATION |
Company mapping should come as close to reality as
possible (e.g. directly based on trade register and additional
data, such as branches, connected companies, etc....). Related topics: |
|
| Branches CX_BRANCH |
... Related topics: |
|
| Connected Companies CX_CORPORATE_GROUP |
... Related topics: |
|
| Chart CX_COST_CENTER_CHART |
|
|
| Persons | ||
| Persons CX_PERSON |
|
|
| Staff Members CX_STAFF_MEMBER |
... Related topics: |
|
| Partner Data | ||
| Locale Data CX_LOCALE |
|
|
| Access Data CX_ACCESS |
|
|
| Communication Person CX_ACCESS |
|
|
| Bank Account CX_BANK_ACCOUNT |
Own bank details and bank details that belong to a partner can be saved in different complexity. |
|
| Business Pattern | Description | Preview |
|---|---|---|
| Items | ||
| Items CX_ITEM |
|
|
| (Servicing) Unit CX_SERVICE |
|
|
| Other Real Things | ||
| Industrial Plant CX_INDUSTRIAL_PLANT |
|
|
| Item accounts | ||
| Item accounts |
|
|
| Item Casts | ||
| Component Set CX_CONSTRUCTION_SET |
|
|
| PID CX_SALES_BOM |
|
|
| Sales Set and Attributes CX_SALES_SET |
|
|
| Item Data | ||
| Price Chain CX_PRICE_DISCOUNT |
|
|
| Supplier Agreement CX_SUPPLY_BOM |
|
|
| Serial Number CX_SERIAL_NUMBER |
|
|
| BOM Modeling | ||
| Allocations CX_SINGLE_ALLOCATION |
Eine Einzel-Allokation beschreibt je nach Sichtweise eine Verwendung oder eine Ressource eines Geschäftsobjekts. |
|
| CX_CONDITIONED_ALLOCATION | Mit dieser Klasse werden bedingte Allokationen beschrieben. Im Normalfall werden in die bedingte Tabelle Einzel-Allokationen gesetzt, um verschiedene Szenarien abzubilden. |
|
| CX_SET_ALLOCATION | Eine Allokationstabelle ist eine Liste von Allokationen. Im Normalfall besteht die Liste aus Einzel- oder bedingten Allokationen. |
|
| Special Values CX_PRODUCT_AMOUNT |
|
|
| CX_INDUSTRIAL_PLANT_PlantGroup |
|
| Business Pattern | Description | Preview |
|---|---|---|
| Business Operation CX_WORK_FLOW |
In ClassiX®,
business operations are mapped via CX_WORK_FLOW objects as a business
operation identifier and - for possible transaction states within this
business operation - CX_STATE_MONITOR objects. Related topics: |
|
| Business Operation CX_WORK_FLOW_Delivery |
In ClassiX®,
business operations are mapped via CX_WORK_FLOW objects as a business
operation identifier and - for possible transaction states within this
business operation - CX_STATE_MONITOR objects. Related topics: |
|
| (Electronic) Float Files CX_FLOAT_FILE |
In CyberEnterprise®
you can take use of electronic float files with associations to dokuments, Excel-, Word- or
.pdf file, which can be sent among any users of the system. Each user will get its due activities in concern with float files in his proceedings account. |
|
|
Controlling |
||
| Accounting Area CX_ACCOUNTING_AREA |
Um auch für z.B. Fremdlager, unabhängig vom lokalen
Lagerbestand, termingerecht disponieren zu können, sind Buchungskreise
notwendig. Es werden alle logistischen und dispositiven Bewegungen und Mengen nach Buchungskreisen getrennt in Untermonitoren mitgeführt. Eine Betrachtung der gesamten Prozesse ist also so pro Buchungskreis möglich. |
|
| KPI Auditor CX_KPI_AUDITOR |
Im folgendem Pattern werden die Zusammenhänge für die Ermittlungen von Kennzahlen zur Lieferantenbewertung beschrieben. Der KPI Auditor (CX_KPI_AUDITOR) dient der Definition von Kennzahlen, welche als Attribute angelegt werden. Der KPI Auditor ist mit dem Workflow (CX_WORK_FLOW) der Bestellpositionen (in diesem Beispiel CX_TRANSACTION statt CX_LINK_TXN) verbunden. Über die Transaktionsbeschreibung wird ein Logcube (CX_LOG_CUBE) zwischen dem KPI Auditor und dem Lieferanten beim Buchen der Bestellposition erzeugt. Beide Objekte können von der Transaktionsbeschreibung über die Bestellposition erreicht werden. Die Transaktionsbeschreibung schreibt die Kennzahlen in die jeweiligen Logcubes (Alle, Jahr, Monat) und verbucht die Transaktion. |
|
| Overview Quantity Booking |
|
| Business Pattern | Description | Preview |
|---|---|---|
| Financial Booking | ||
| Open Item Debitors CX_DEBIT_OPEN_ITEM_TXN |
|
|
| Sales | ||
| Verkaufsauftrag CX_SALES_ORDER |
|
|
|
Coupling
Offer/Order with Project,
Industrial
Plant etc. |
|
|
| Structure
Offer/Order CX_SALES_ORDER_Structure |
|
|
| Advance Demand CX_ADVANCE_DEMAND |
|
|
| Job Group CX_JOB_GROUP |
|
|
| Sales Order Costing CX_SALES_ORDER_Costs |
|
|
| Purchase | ||
| Order Item Supplier
Agreement CX_PURCHASE_ACCOUNT |
|
|
| Approved
Demand Requisition Status CX_WORK_FLOW_PurchaseRequisition |
|
|
| Production | ||
| Disposition Component CX_DISPOSITION_BOM |
To be able to control the disposition use of parts within an Item Demand, it is possible to keep information in the according master BOMs |
|
| Resolved Production BOM CX_ALLOCATION_TXN |
Resolving a BOM generates a tree structure with CX_ALLOCATION_TXN objects. This object hierarchy also defines at first the Disposition Item use; this can be overwritten with additional indications. |
|
| Item Demand CX_ITEM_DEMAND |
Item demands are transactions, which are automatically generated from an item disposition according to the Gozinto Method. Starting point is a Product Item E1 consisting of the items B2 and B3, etc. |
|
| Business Pattern | Description | Preview |
|---|---|---|
| Customer - Sales Statistics CX_SALES_ACCOUNT |
|
| Business Pattern | Description | Preview |
|---|---|---|
| MS Office Integration Outlook Synchronization |
|
|
| Vocabulary CX_PHRASE |
CX_PHRASE and CX_SIGNIFICATION objects are connected via "clearingObjects". A CX_PHRASE object can reference more CX_SIGNIFICATION objects. |
|
| Business Pattern | Description | Preview |
|---|---|---|
| Saved Lists CX_LIST_VIEW_COLLECTION |
|
|
| Partner Search Items
CX_INDEX_CI |
|
|
| Transaction Description CX_TXN_DESCRIPTOR |
In ClassiX® , transaction descriptions control the processing (transactions) of all transactions (CX_TRANSACTION objects). |
|
| Wrapper CX_OVERWRITING_REF |
|
|
| Access Rights CX_SECURITY_SET |
|