Parameter file modifications
The M3 BE database structure and the PWB database structure are not identical. The modeling of data integration is defined in the parameter file, which defines which APIs are called and how the fields are mapped between APIs and the PWB database structure. The parameter file MI-PARAM.DAT contains the modeling and mapping.
The standard solution is to use internal configuration. If internal configuration is not enough, you can modify the parameter file.
To create parameter file modifications, follow these steps:
- Click .
- Right-click MI-PARAM.DAT and select to display the editor.
- Specify the modifications.
- Click to save the customer parameter file.
On your next server log on, the modified parameter file is used.
Modifications can have different scopes. These are some examples:
- You can map off fields in an already used API into free local fields and use the information in reports. This kind of modification is easy to migrate. There is less consequence of the modification being deleted because it is just nice-to-have information that you can easily migrate to the new parameter file.
- You can add logic in the parameter file. For example, a lead-time comes from (LEA1 purchase lead time) but if another field (PUIT=3 Acquisition code=distribution) is added, the lead-time is set to 1 day. This kind of modification is easy to migrate if they are well documented. There is a minor consequence of the modification being deleted because it affects the plan. A warning is displayed that you must migrate the modification to the new parameter file.
- You can use different APIs for data transfer. This kind of modification is complicated to migrate. There is a major consequence of the modification being deleted because it affects the data modeling and, therefore, the whole solution.
You must always analyze and report integration issues using a standard parameter file.