...
Movement type | Define which movement types are relevant to be sent to FSM | ||||||
Plant | Define for which plant movement type should be sent to FSM | ||||||
Storage location | Limit send online good movements only to chosen storage location (advisable to leave this empty) and has to be relevant to plant | ||||||
Special stock indicator | Choose If movement type is combined with special stock indicator | ||||||
Send stock level | Stock level will be sent to the cloud (after each stock relevant booking in SAP)
| ||||||
Send MatDoc | Material document for specified movement type should be sent to the cloud | ||||||
Send RMAT | Sending goods movement to the cloud for Reserved Material should be triggered immediately after using movement type on material | ||||||
| A given movement type triggers deletion of serial numbers from FSM. Applicable e.g. for scrapping/inventory movements. ExampleDelete old serial number from FSM after cancelling goods issue 261. This field must be activated if reversed serial numbers should be able to be consumed again (applicable for goods issues on non-FSM-relevant warehouses). The ‘Delete SERNR’ field is enabled for goods movement 262:  Consume a serialized material on the mobile app. Revert the goods movement 261 by movement 262 in transaction MIGO:  A deletion request is sent for the serial number first. Then the serial number is sent again (with a new GUID) as active:  The serial number is available on the mobile app again:  | ||||||
| Delete the original material movement document after cancelling goods issue (deletion request idoc sent to FSM). See also the field above. |
...