User Tools
Add this page to your book 
Remove this page from your book 
Manage book (
Help Table of Contents
Naming Transactions
In DOKA-NG, transaction names are assigned according to a specific system of abbreviations (mnemonics, or mnemos for short). Naming is based on mnemos made up of the English names of the transactions/business sectors.
This is described below using the Import L/C (LI/BR) business sector as an example. 'LI' is the abbreviation for 'Import Letter of Credit' and 'BR' is a document set under an import L/C (Bills Received).
In principle, transaction mnemos follow a straightforward pattern:
xxTyyy = Business transactions (e.g. LITAME)
xxByyy = Batch transactions (automated functions, such as LIBCOM)
xxRyyy = Report transactions for creating reports in the business sectors
The first two characters identify the business sector. The third letter indicates whether the transaction is a business transaction, a batch transaction or a report. The last three characters identify the type/nature of the transaction.
Business Sector / Subsector Transactions
| Transaction Mnemo | Description |
|---|---|
| xxTPOP | Transactions for preadvising contracts |
| xxTOPN | Transactions to open new contracts |
| xxTRAM | Transactions used for amendment requests |
| xxTAME | Transactions used for amendments |
| xxTADD | Transactions to add or amend parties' reference numbers |
| xxTATT | Transactions to allocate an incoming message to a contract |
| xxTFRE | Transactions for sending common messages |
| xxTFEE | Transactions for settling fees and charges |
| xxTTEN | Transactions for changing tenors |
| xxTTRF | Transactions to exchange contract parties |
| xxTCOM | Transactions for automatic commissioning |
| xxTAOP | Transactions for assignments |
| xxTCAN | Cancelation transactions |
| xxTROP | Transactions for re-opening contracts |
| Subsector Import Documents (Examples) | |
| BRTSND | Transaction to send documents |
| BRTPAY | Transaction to send and settle documents |
| BRTSUS | Transaction to settle usance documents |
| BRTLAT | Transaction to handle late payments |
General Comprehensive Transaction Mnemos
| Transaction Mnemo | Description |
|---|---|
| xxxSEL | Display transactions which are available in each business sector, for example, and which show the status of a selected contract (e.g. LETSEL). |
| xxxREL | Release transactions that display items waiting for release and which can possibly be released. |
| xxxGEN | General report generators are used to define and/or generate reports for the respective sector. |
| INFxxx | Info System transactions are available for business sectors as well as for the static data system. . Structure: INFxxx, whereas xxx is replaced by the static data sector (e.g. 'CTY' for country or a business or subsector (z.B. INFLED for Export L/Cs or INFBED for document sets under an Export L/C). |
| GENyyy | These transactions are used to handle all kinds of developer tasks in the system. Structure: GENyyy, whereas yyy is replaced by a mnemo for the respective function / task (e.g. GENUPD for generating updates). |
| SYSyyy | System transactions are used to handle a wide range of system administration tasks. They are mainly used by system administrators. Structure: SYSyyy, whereas yyy is replaced by a mnemo for the respective function / task (e.g. SYSCLN for cleaning up historical data). |
| REOyyy | These transactions are used for Reorganization, checking or re-structuring of data . Structure: REOyyy, whereas yyy is replaced by a mnemo for the respective type of data (e.g. REOCBS for reorganizing the CBS entries). |
| yyyTSK | Managers are used for controlling different types of services in the workflow, messages or for controlling jobs (JOBTSK) within the system. Structure: yyyTSK, whereas yyy is replaced by the respective mnemo (e.g. SWITSK for controlling incoming messages). |
| yyyCFG | Transactions for creating and modifying different menus and profiles in the system. Structure: yyyCFG, whereas yyy is replaced by the respective mnemo (e.g. FILCFG for the Sub Menu Editor). |
Static Data Transactions
Static data transactions begin with the characters DB (for database). The third character identifies the type of transaction (e.g. 'E' for editing/modifying). With 'Parties', for example, DBxPTY → PTY = party. 'yyy' is replaced by the mnemo for the respective static data type (e.g. 'ADR' for addresses').
| Transaction Mnemo | Description |
|---|---|
| DBAyyy | DBAyyy transactions are used for adding new records (A for Add) |
| DBDyyy | DBDyyy transactions are used for deleting records (D for Delete) |
| DBEyyy | DBEyyy transactions are used for editing records (E for Edit) |
| DBIyyy | DBIyyy - Overview/Display transactions for the respective type of static data (I for Information) |
| DBLyyy | DBLyyy - Creating reports of static data (L for Listing) |
| DBZyyy | Special transactions in the static data system (M for Manage, R for Release, S for Split, etc.) |
