User Tools
en:app:020cor:140mis:0300migdia
Book Creator
Add this page to your book
Add this page to your book Book Creator
Remove this page from your book
Remove this page from your book 
Manage book (
Help Migration of Diaries
Transaction MIGDIA
This transaction can be used to transfer diary events from a legacy system.
For each diary event, a file containing data such as the date and the diary reason is expected.
The individual lines must conform to a certain structure. Each line begins with a tag bracketed by ':'. The actual content follows after the second ':'.
The following tags are processed:
| Tag | Content | Transfer |
|---|---|---|
| C001 | Reference number of the contract | for mapping to contract |
| D001 | Reference number of the contract, with preceding business sector abbreviation | for mapping to contract |
| D002 | Diary event type “DIA” | check only |
| D003 | Coded reason | Reason and name of diary event |
| D008 | Diary event date (format YYMMDD or YYYYMMDD) | Date (first diary) |
| D010 | Diary event date (format YYMMDD or YYYYMMDD) | Date (if second diary is needed) |
| D018 | Text | Diary Description |
| D019 | Text | Diary Description |
The transaction remains empty; the user is filled using the responsible user in the contract.
The implementation usually calls for project-specific adaptation.
More information on migration can be found under Migration.
Transaction Panels
Import
Datafields
| Datafield | Description |
|---|---|
| Encoding of Import File | Possible encodings are “CP437” MS-DOS US “CP850” MS-DOS Central Europe “UTF-8” UTF-8 |
en/app/020cor/140mis/0300migdia.txt · Last modified: 2022/09/02 12:49 (external edit)
