Events
Description
This module is used for the overview and processing of all transactions for a business object. For example, a business object can be a partner, a user or a part. The window title shows who the displayed transactions originate from.
If the transactions are listed from a contact person, the window title shows not only the associated company, but also whether and from which company role the contact person was called. When creating transaction documents, this information controls whether the transaction folder of the company or the company role is placed in the transaction document in addition to the transaction folder of the contact person.
Transactions primarily include transactions that are automatically posted to the transaction folder of the corresponding business object. This is done according to the transaction description of the individual document types, such as invoices, orders, etc.. Subfolders (period, status, etc.) are also automatically created in which the documents are filed. In this way, a structure is created, as can be seen on the right-hand side, for example. (The number in brackets indicates how many receipts are in the corresponding folder.)
Furthermore, there are so-called transaction documents that are manually posted in transaction folders. These include letters, faxes and e-mails, but also simple notes or visit logs. To categorise these documents in transaction fold ers, a folder structure can also be created manually.
The transaction folder is for master data what the document history is for documents. Thus, in addition to the transactions, documents and cost objects can also be displayed and partially maintained here.
Functionality
General functionality of the Tasks folder
The folder is divided into two parts. On the left side the tasks/task folders are shown in the tree structure. The task documents can be displayed or not displayed here in the tree structure by option. Independently of the options the tasks of the selected folder are displayed on the right side.
Also on the left side there is the possibility to view or change attributes, documents or cost units assigned to this object. The right mouse button opens context menus, which can be used to insert or remove object references.
System folder/"normal" folders
The colour of the folder shows whether it was created automatically or manually. The folders shown in red are the automatically created system folders that were created by posting a transaction based on a transaction description. Transaction documents in these folders can neither be moved nor removed and it is also not possible to insert other transaction documents or "simple" folders here. Folders shown in yellow are manually created folders. The user is free to edit these folders.
Display of the transaction documents in the list
The presentation of the transaction documents in the list can vary from folder to folder. For example, there is a standard format for the list if there are only transaction documents (letter, fax, etc.) in a folder. If a folder consists of subfolders (and transactions), the system switches to a general format.
If a system folder has no subfolders but only transactions, the system tries to determine the list format automatically from the status monitor or workflow of the corresponding document type.
General process window
The task folders have a uniform layout with a general functionality. However, there are slight differences, for example between the task folder of the part and that of the user, customer, etc. Therefore it can happen that the described fields or menu items are not applicable or available for all task folders.
| Menu item | Description |
|---|---|
| Edit | - |
| new | - |
| : : Note | Create transaction document for a note |
| : : Letter | Create transaction document for a letter |
| : : Fax | Create a transaction document for a fax |
| - | |
| : : : Writing | Create a transaction document for an email |
| : : : Import from Outlook | Create transaction document for an email imported from Outlook This creates a new e-mail transaction document (as with the menu item "Write"), but the e-mail currently selected in Outlook is additionally attached as an external document in .msg format. The subject as well as the date and time of the e-mail are read out and inserted into the transaction document accordingly. In addition, the direction ("active"/"passive") is set automatically. If the e-mail is in the "Sent" folder of Outlook, the transaction document is marked as "active", if the e-mail comes from any other folder as "passive". |
| : : Phone call | Create a transaction document for a telephone call |
| : : Meeting | Create a transaction document for a meeting |
| : : folder | Create activity folder |
| Open | Edit a process folder or process. |
| Remove | Remove a task folder or task. |
| : Document chaining | This selection is only active when transaction documents are displayed in the right part of the window |
| : : Release | The predecessor/successor links of the transaction documents selected in the list are removed |
| : : Create again | The predecessor/successor links of the transaction documents selected in the list are first disconnected and then rebuilt according to the selected sequence |
| Close | Close window |
| Options | - |
| Display documents in the tree | Documents are displayed in the tree view |
| Symbol | Description |
|---|---|
 | Create task folder or tasks. |
 | Edit task folder or task. |
 | The selected object is removed from the task folder. If the object is a task note that is not referenced in any other task folder (monitor), it is also deleted. |
 | Print the current view. |
 | Update list |
 | Copy to the clipboard. |
 | Display document history. |
| Open first document |
 | Display a list of all operations. |
  | Switch between the view with all tasks / task folders and the simple view. |
 | Show bookings |
 | This button is enabled if the transaction folder of a variant part or an article role of a variant part has been opened. In the activity folder of a variant part, all documents of the variant part are accumulated. (Exceptions are the predecessors of the subparts, but these can be displayed in the activity folder of the variant part via the option "Incl. activities of subparts"). If you now want to display the predecessors of a very specific variant or group of variants, you can filter the activities according to their characteristics. The filter can refer to concrete attribute values or to value ranges. If an attribute filter is active, this is indicated by a red text in the task folder. |
| Field | Description | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Including operations of the lower parts (Only for variant parts) | This option is only displayed in the operation folder of parts and part roles and it can only be selected when the operations of a variant part are displayed. If this option is set, all operation folders (variant part + subparts) are combined into a folder structure and displayed. | ||||||||||
| Activity folder | Folder structure of the operation folders. The number of documents posted in a folder is shown in brackets. | ||||||||||
| Folder/task list | The subfolders and operations of the folder selected in the folder structure are displayed. The columns of the folders can be defined individually via the status or the business process
| ||||||||||
| Attributes | The attributes of the business object (company, person, part, etc.) | ||||||||||
| Documents | The documents of the business object. | ||||||||||
| Cost unit | The cost units of the business object. |
Option window
Used to set the option when using the operations folder
| button | Description |
|---|---|
| Display documents in the tree | This option enables you to display the documents of a folder in both the list and the tree. |
| Display documents without folders in the list | This option can be used to activate that only documents are displayed in the list and the folders are ignored. This has the advantage, among other things, that if a folder has subfolders, these are not displayed but their documents are. Example: |
List window
Used to list the transaction account objects.
| button | Description |
|---|---|
| Edit | The current transaction account object is displayed in the input window. |
| New | An empty input window opens. |
| Delete | The selected transaction account object is deleted. |
| Close | The window is closed. |
Selection window
This window is for selecting a transaction folder or transaction account.
| Symbol | Description |
|---|---|
 | Unfold all elements. |
 | Fold all elements together. |
  | Show/hide descriptions of the operation folders. |
 | Edit operations. |
| Switch between the view with all tasks / task folders and the simple view. |
| button | Description |
|---|---|
| OK | The selected transaction account is transferred. |
Related topics
Technical Documentation
Overview
Transaction account basic module
Module name
Proceedings.mod
Classes
Transaction account selection module
Module name
ProceedingsSelect.mod
Classes
Security
In addition to restricting access rights via the class and its data fields, the module can be restricted in its use via some of the received messages.
| Message | Parameters | Function | Security |
|---|---|---|---|
| SELECT_PROCEEDINGS | Transaction account object, recipient of the response | Call up selection window for transaction account |
| Message | Parameters | Function | Receiver module |
|---|---|---|---|
| EDIT_PROCEEDINGS | NULL or transaction account object | Call up the input window for transaction account | Transaction Account Editing Module |
| PROCEEDINGS_SELECTED | Transaction account object, recipient | Transaction account was selected |
Transaction account editing module
Module name
ProceedingsEdit.mod
Classes
Security
In addition to restricting access rights via the class and its data fields, the module can be restricted in its use via some of the received messages.
| Message | Parameters | Function | Security |
|---|---|---|---|
| PROCEEDINGS_CHANGED | Transaction account object | Transaction account was changed | |
| PROCEEDINGS_CREATED | Transaction account object | Transaction account was created | |
| PROCEEDINGS_DELETED | Transaction account object | Transaction account was deleted | |
| PROCEEDINGS_FOLDER_CHANGED | Activity folder object | Activity folder has been changed | |
| PROCEEDINGS_FOLDER_CREATED | Activity folder object | Task folder was created | |
| PROCEEDINGS_FOLDER_DELETED | Activity folder object | Activity folder was deleted | |
| TXN_NOTE_CHANGED | Activity note object | Transaction note has been amended | |
| TXN_NOTE_CREATED | Activity note object | Activity note was created | |
| TXN_NOTE_DELETED | Activity note object | Activity note was deleted |
| Message | Parameters | Function | Receiver module |
|---|---|---|---|
| EDIT_MAIL | Create e-mail. | ||
| EDIT_PROCEEDINGS | NULL or transaction account object | Call up the input window for transaction account | Transaction Account Editing Module |
| SHOW_TXN_HISTORY | Event object. | Display operation sequence. | |
| SHOW_PREVIEW | Print Preview | Print Preview |
Transaction Account Editing Module General
Module name
ProceedingsEditMain.mod
Classes
Security
In addition to restricting access rights via the class and its data fields, the module can be restricted in its use via some of the received messages.
| Message | Parameters | Function | Security |
|---|---|---|---|
| EDIT_PROCEEDINGS | NULL or transaction account object | Call up the input window for transaction account | |
| LIST_PROCEEDINGS | Collection transaction account objects or NULL | Call up the list window for transaction account |
| Message | Parameters | Function | Receiver module |
|---|---|---|---|
| CREATE_LETTER | NULL or letter object | Open the input window for operation notesCall upinput window for transaction notes | |
| EDIT_PROCEEDINGS_OF_ITEM | Transaction account object | Open the input window for operations. | Procedure Editing module for objects and items |
| EDIT_PROCEEDINGS_OF_TXN_NOTE | Transaction account object | Open the input window for operations. | Process Editing module for letters, notes etc. |
Transaction account editing module for items (CX_ITEM)
Module name
ProceedingsEditItem.mod
Classes
Security
In addition to restricting access rights via the class and its data fields, the module can be restricted in its use via some of the received messages.
| Message | Parameters | Function | Security |
|---|---|---|---|
| LIST_PROCEEDINGS_OF_ITEM | |||
| LOAD_PROCEEDINGS_OF_ITEM | |||
| EDIT_PROCEEDINGS_OF_ITEM | Transaction account object | The input window for object operations opens. |
| Message | Parameters | Function | Receiver module |
|---|
Transaction account editing module for partners (CX_PARTNER)
Module name
ProceedingsEditTxn.mod
Classes
Security
In addition to restricting access rights via the class and its data fields, the module can be restricted in its use via some of the received messages.
| Message | Parameters | Function | Security |
|---|---|---|---|
| LOAD_PROCEEDINGS_OF_TXN_NOTE | Import operations | ||
| LIST_PROCEEDINGS_OF_TXN_NOTE | Collection transaction account objects or NULL | Call up the list window for transaction account | |
| EDIT_PROCEEDINGS_OF_TXN_NOTE | Activity note object | Activity note was deleted |
| Message | Parameters | Function | Receiver module |
|---|---|---|---|
| EDIT_OBJECT | Object | Open input window for object | Object Editing Module |
| EDIT_PROCEEDINGS_FOLDER | Higher-level monitor | Open the input window for the operation folder | Folder Editing Module |
| EDIT_TXN_NOTE | Note or NULL | Edit or create an ink note. | Process Editing ModuleTransaction editing module |
| CREATE_LETTER | Operation object or NULL | Edit or create an operation. (For letters, faxes, e-mails) | Process Editing ModuleTask editing module |
| LIST_TXN_NOTE | Transaction account | Display the list of operations. | Procedure list moduleTask list module |
| DELETE_PROCEEDINGS_FOLDER | Activity folder | Delete an operation folder. |
;){kind=link}
;){kind=link}
;){kind=link}