Implementation of Actions

Action type (CMS109) controls how and by which function an action must be implemented.

Currently these actions can be automatically implemented:

  • Reschedule macro order (RESCHDATEH)
  • Reschedule date operation (RESCHDATEO)
  • Split macro order (SPLITMACRO)
  • Move order to new macro order (MOVEORDER)
  • Seq/forced start - operation (OPRSTATUS)
  • Change work center type 1 (CHGWC1)

Re-schedule Macro Order (RESCHDATEH)

The definition of the fields sent with the action are as follows:
Origin MSP
Action type RESCHDATEH
Action group
Company CONO
Macro ord type MOTY
Macro ord no MONO
Planning date PLDT
Plan time std PLHM

The implementation will re-schedule all supply chains/orders connected to the macro order to the planning date and time included in the action.

The action is implemented in this way:

  1. Look-up orders and supply chains connected to the macro order through table MMAODE (information displayed in the function "Macro order Relations", RPS301).
  2. Re-schedule orders/supply chain to new date/time.
    • Planned orders: Finish date of the planned MO is set to the sent planning date. Re-schedule is performed by calling function "Manage planned MO" (PMS912). The content of the planned MO is re-generated according to the new date.
    • Released MO: Finish date/time of the MO is set to the sent planning date/time. Re-schedule done by calling function "Re-schedule MO" (PMS010BE).
    • Supply chain: Finish date/time of the highest supply level is set to the sent planning date/time. The re-schedule of the supply chain is performed through function "Manage supply chains" (RPS912). Note that the top level demand (CO or DO-line) is not affected by this change.
  3. Re-set the "next generation date/time on the macro order header to 0.
Note: 

This transaction overrules all other performed planning for affected orders/supply chains with the exception of Infor M3 SWB-planned operations (depending on setting in the planning policy, MMS037) and changes of work centers and facilities.

Re-schedule Macro Order Operation (RESCHDATEO)

The definition of the fields sent with the action are as follows:
Action type RESCHDATEO
Action group
Company CONO K
Macro ord type MOTY K
Macro ord no MONO K
Struct seq no SEOP K
Start date STDT R
Start time MSTI R
Finish date FIDT R
Finish time MFTI R
Resch downstrm RPOA R

The implementation will re-schedule the pin-pointed operation for all supply chains/orders aggregated into that operation to the planning date and time included in the action.

The action is implemented in this way:

  1. Look-up orders and supply chains aggregated into the selected operation through table MMAODR (information displayed in the function "Macro order detailed Relations", RPS304).
  2. Re-schedule operations to new start and finish date/time.
    • Planned and released orders: The dates of the operation are set to the sent start and finish dates. Re-schedule is performed by calling several functions (PMS910, MMS910, PMS940, PMMNGAPL etc). Connected materials are re-planned in the material plan to correspond with the new start date/time of the operation.

      The field RPOA (Re-schedule downstream) controls how to handle the other operations in the MO/Planned MO. These values are allowed:

      • 0 = Only the pin-pointed operations are changed. Surrounding operations remains on original date regardless of their dates
      • 1 = Surrounding operations are re-scheduled to the same date/time as the pin-pointed operation. All downstream operations up to the first critical operation are re-scheduled. All upstream operations are re-scheduled regardless if they are critical or not. 
    • Supply chain: There is no special handling for supply chains because it is only a specific planned/released MO that is affected.
  3. Re-set the "next generation date/time on the macro order header to 0.
Note: 

This change will update the setting "Planned by APP" on the operation. This setting will be set = 2. The fields Original start/finish date and time on the operations are not changed due to this action.

Note: 

This transaction do not support order initiated orders. An error message is generated for these types of orders.

Split Macro Order (SPLITMACRO)

The definition of the fields sent with the action are as follows:
Action type SPLITMACRO
Action group
Company CONO K
Macro ord type MOTY K
Macro ord no MONO K
Temp macro no TMON R
Planning date PLDT R

The implementation will copy a macro order header to create a new macro order. All fields on the new header except the bucket start and stop is equal to the "old" macro order.

The action is implemented in this way:

  1. Look-up and copy the macro order header.
  2. Retrieve bucket start and stop based on the planning date included in the action. The bucket start/stop is set to be same as on "old" macro order if no planning date is sent.
  3. Set the field Temp macro order number on the new macro order to the sent Temp macro order number in the action.
    Note: This field is used in other actions to be able to find the new macro order.

Move Order (MOVEORDER)

The definition of the fields sent with the action are as follows:
Action type MOVEORDER
Action group
Company CONO K
Macro ord type MOTY K
Macro ord no MONO K
Temp macro no TMON K
Supply chain no SCNB R
Order category ORCA R
Order no RIDN R
Order line RIDL R
Order op RIDO R

The implementation will move an order/supply chain from one macro order to another.

The action is implemented in this way:

  1. Look-up the sent order/supply chain in the Macro order relations (MMAODE).
  2. Remove it from the "old" macro order
  3. Retrieve the new macro order through the "Temp macro order number" (set through the action SPLITMACRO). Add the order/supply chain to this new macro order.
  4. Re-set the "next generation date/time on the "old" macro order header to 0.

Set Operation Status (OPRSTATUS)

The definition of the fields sent with the action are as follows:
Action type OPRSTATUS
Action group
Company CONO K
Macro ord type MOTY K
Macro ord no MONO K
Struct seq no SEOP K
Sequencing sts SEQS R
For start date FRCD R
For start date FRCT R

The implementation will set the status (Infor M3 SWB status) and the forced start/stop on the pin-pointed operation for all supply chains/orders aggregated into that operation. These fields are used in Infor M3 SWB for planning purposes.

The action is implemented in this way:

  1. Look-up orders and supply chains aggregated into the selected operation through table MMAODR (information displayed in the function "Macro order detailed Relations", RPS304).
  2. Set the fields Sequencing status, forced start and stop to the sent values.

Change Work Center Type 1 (CHGWC1)

The definition of the fields sent with the action are as follows:
Action type CHGWC1
Action group
Company CONO K
Macro ord type MOTY K
Macro ord no MONO K
Planning date SEOP K
Plan time std FACI R
WorkCenter PLGR R

The implementation will change the used work center (type 1) for the pin-pointed operation for all supply chains/orders aggregated into that operation to the planning date and time included in the action.

The action is implemented in this way:

Within same facility:

  1. Look-up orders and supply chains aggregated into the selected operation through table MMAODR (information displayed in the function "Macro order detailed Relations", RPS304).
  2. Change the work center (type 1) to the new work center sent in the transaction. The possible resource (Work center type 6) is set to the standard resource for the work center. Information like run time etc remains from old work center until a planned order is re-generated or released (same principle as when a work center is changed in the function "Work center schedule", PMS230). At that point all information is picked up for the new work center.  
    • Planned and released orders: The work center is changed and load etc is moved to new work center. Start/finish date, run time etc are not effected.
    • Supply chain: There is no special handling for supply chains because it is only a specific operation that is affected.
  3. Re-set the "next generation date/time on the macro order header to 0.

New facility

Note: 

Information about the new work center and facility is stored in a new table "Action log implemented action line" (MALIAL). This information is used to find the new work center and facility when a planned order is re-created or released. The fields "Original start/finish" date and time on the operations are not changed due to this action.

Important: 

This transaction do not support order initiated orders. An error message is generated for these types of orders.

API transactions

The connection between Infor M3 BE and M3 APS products are done through APIs. The API CMS050MI is used for all transactions related to action log.

The definition of the fields sent with the action are as follows:
Program CMS050MI
Description Action log
Transaction Description Sts
CloseAction CloseAction 20
CreateDetails CreateDetails 20
CreateHeader CreateHeader 20
CreateLine CreateLine 20
DeleteDetail DeleteDetail 20
DeleteHeader DeleteHeader 20
DeleteLine DeleteLine 20
Implement Implement 20
ListHeader ListHeader 20
ListLine ListLine 20
Related topics
Action Log Header
Actions
Activate the Implementation of Actions
Error Handling of Actions
Life Cycle of Actions