Create MO using M3 Action Logs

It is now possible to export new production orders to M3 using asynchronous APIs implemented using M3's Action Log. This includes retrieving a new action log number by calling CMS050MI-CreateHeader, sending create MO and update operation commands using the new action log number and in the order of order 1 - operation 1, order 2 - operation 2, …, order n - operation n. Finally, the listed "actions" with the new action log number are implemented. M3 starts creating MOs and updating the operation only after the implement command is executed.

Currently this new method is only available to export new orders, that is, for records in SO_PRODUCTION_PLAN table where scp_order_status = "New". For all other status (Open, Planned and Firm Planned), existing outbound flows are used. This new method is available as a replacement to the replace the existing three-step method: Create MO + Reschedule + Update Operation. However, the new method is turned off by default. The m3_use_batch_create_mo new application variable must be set to 1 to turn on the new outbound method.

The new method is available when Business Plans are used. The Business Plan-based generic outbound flow in SCV remains unchanged. All changes to the M3 outbound flow for this feature are between Outbox and M3 staging tables.

This new application variable has been added:

  • m3_use_batch_create_mo: Default = 0 (batch creation of MOs disabled)

This existing macro has been updated:

  • SCV_M3_Outbound_Supply_Plan_Full

These new entities have been added:

  • CMS050MI_Implement
  • CMS050MI_CreateLine
  • CMS050MI_CreateHeader
  • CMS050MI_CreateHeader_ReturnValue

These new SCV tables have been registered together with all related configuration (such as datasheets, etc.):

  • ST_M3_OUT_CMS050MI_CreateHeader
  • ST_M3_OUT_CMS050MI_CreateHeader_ReturnValue
  • ST_M3_OUT_CMS050MI_CreateLine
  • ST_M3_OUT_CMS050MI_Implement

These new views have been added:

  • ST_V_M3_CMS050MI_CreateHeader
  • ST_V_M3_CMS050MI_CreateLine
  • ST_V_M3_CMS050MI_Implement

These new mappings have been added:

  • BASE_ST_V_M3_CMS050MI_CreateHeader-ST_M3_OUT_CMS050MI_CreateHeader
  • BASE_ST_V_M3_CMS050MI_CreateLine-ST_M3_OUT_CMS050MI_CreateLine
  • BASE_ST_V_M3_CMS050MI_Implement-ST_M3_OUT_CMS050MI_Implement

These new BOIs have been added:

  • CMS050MI_CreateHeader_ST_M3_OUT_CMS050MI_CreateHeader
  • CMS050MI_CreateLine_ST_M3_OUT_CMS050MI_CreateLine
  • CMS050MI_Implement_ST_M3_OUT_CMS050MI_Implement

CreateLine command for updating operations requires the default resource unit to be passed as parameter. This information available now is imported from M3 using PDS010MI-Select. The PLGD field has been added to this API to hold the default resource unit.

These existing entities have been updated together with all related configuration (such as datasheets):

  • PDS010MI_Select_Resource
  • PDS010MI_Select_ResourceUnit

This existing view has been updated:

  • ST_V_M3_RESOURCE

This existing mapping has been updated:

  • BASE_ST_V_M3_RESOURCE-SI_RESOURCE
Note: This feature is enabled after appending the M3 template (base for M3.zip) for this version. You do not require to do anything to enable this feature.

Action required after the activation:

The export through M3 Action Logs require the default resource unit in a resource to be set. Before executing the new export using M3 Action Logs, master data must be imported from M3 to populate the new column.