The table below shows the data relationship between PMI data elements/fields (target) and corresponding source data elements/fields (source).
You will find the transformation/load rules meant to explain any programmatic manipulation and calculation applied in the adapter to get the desired data format and/or result in the PMI staging table where such have been applicable.
An example of the source file data, format and structure is also attached below the table.
This table will be updated whenever the source file or the interface in question are changed throughout the interface life-cycle.
Te file name pattern is like CJ*.txt
| # | Interface name incl. version | PMI data element (target) |
|---|---|---|
| 1 | Vsp_Revenue_V001 | Retrieving actual data |
| Columns | PMI data element (target) |
|---|---|
| 1 | Date |
| 2 | Not used |
| 3 | Not used |
| 4 | Account |
| 5 | Revenue |
| 6 | Not used |
| 7 | Not used |
| 8 | Not used |
| 9 | Not used (inconsistent) |
| # | PMI data element (target) | Description | Mandatory / Optional | Data transformation/load rules | Data element (source) | Comment |
|---|---|---|---|---|---|---|
| 1 | Date | Transaction date | Mandatory | Directly mapped from source file | Date | |
| 2 | Department | ID or name of the department | Optional | Not available in source file | ||
| 3 | Account | ID or name of the account | Mandatory | Directly mapped from source file | Account | |
| 4 | Description | Account description | Optional | Not available in source file | ||
| 5 | Revenue | Revenue without authority charge rates | Mandatory | Directly mapped from source file | Revenue | Revenue is including VAT |