MHS850MI Transaction AddMOReqIssue

The transaction MHS850MI AddMOReqIssue is used to report issue of material on a manufacturing order. It is applicable for issue on material line with issue method 2 (requisition) or 3,4,5 and 6 (back flush).

The transaction MHS850MI AddMOReqIssue requires the following information in order to proceed correctly:

Which balance ID to issue from (ITNO, WHSL, BANO, CAMU). Existence and sufficiency of stock to issue is controlled by the parameter 'Prevent negative on-hand balance' in 'Settings - MO Reporting' (PMS490).
Which material line to report. The manufacturing order number and material sequence number must be provided (MFNO and MSEQ). Alternatively, the reporting number (WOSQ) identifying the material line must be provided. Note that in both cases, the reference saved in the interface file MHILIN in 'Internal Stock Trans Msg. Manage' (MHS852) is always the manufacturing order number (RIDN) and material sequence number (RIDL). The reporting number (WOSQ) is never saved, but converted to the corresponding order and line number.
The reported quantity and catch weight.

Note: Even if the Product Engineering U/M (PEUN) is provided, the quantity is always considered to be expressed in the unit on the material line, or the engineering unit, depending on the item setup in 'Item. Connect Alternate U/M' (MMS015).

To delete or reverse part of a quantity that was issued, the transaction MHS850MI AddMOReqIssue can be run with a negative quantity.

This transaction is compatible with issue of sublots. Example of workflow:

Run MHS850MI AddMOReqIssue with a blank process flag.
Use MHS850MI AddSubLine as many times as there are sublots to issue.
MHS850MI ChgWhsLine to update the delivered quantity (DLQT) to match the number of sublots.
Run MHS850MI PrcWhsTran to execute the transaction.

For sublot items: catch weight adjustment is not permitted when performing a requisition order issue, therefore an individual sublot's catch weight is always retrieved from the sublot master to prevent inconsistencies.

This transaction can be run with UTC mode activated, which means that all date and time provided are considered being UTC time and will be converted to local warehouse time.