Force delete of existing planned orders in M3
Planned orders have been exported to M3 in batch mode where all existing planned orders
in M3 are deleted and the new planned orders are loaded. However, the M3 APIs deleted existing
planned orders only if the new batch has new planned orders. Now existing planned orders are
explicitly deleted even if there are no new planned orders to be exported.
The M3 API SPS101MI-TriggerUpdatJob is extended with additional flags to force deletion of existing planned orders:
- DLPD=1 for explicit deletion of planned distribution/transfer orders
- DLPM=1 for explicit deletion of planned manufacturing/production orders
- DLPP=1 for explicit deletion of planned purchase orders
This SCV entity has been extended to include the three new fields:
- SUPPLY_POST_TRIGGER
These SCV views have been updated to include the new fields:
- ST_V_M3_SUPPLY_POST_TRIGGER
- ST_V_M3_SUPPLY_PLANNED_POST_TRIGGER
These SCV mappings have been updated to include the new fields:
- BASE_ST_V_M3_SUPPLY_POST_TRIGGER-ST_M3_OUT_SUPPLY_POST_TRIGGER
- BASE_ST_V_M3_SUPPLY_PLANNED_POST_TRIGGER-ST_M3_OUT_SUPPLY_POST_TRIGGER
Note: This feature is enabled after appending the M3 base integration template (base for m3.zip)
for this version. No additional role or privilege is required to access this feature.