Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Use this event to

...

  • Stage collected values to new or existing fields in the database that can subsequently can be accessed from standard posting function events.
  • Validate collected values against live data since registration at the mobile device is mostly conducted offline.
  • Set arguments in standard BC posting routines prior to posting.
  • But not to process "line" level steps. Steps added via OnAddStepsToProdOrderComponent is better handled via OnPostReceiveOrder_OnHandleRegistrationFor...-eventsOnPostProdConsumption_OnHandleRegistrationForProductionJnlLine-event.


Note
titleCommit

Database transactions in this event is committed to database prior to calling standard BC posting routines. Your customized code must be structured accordingly.

Nearly always you must subscribe to standard BC posting events to do your actual processing to ensure rollback of database transactions on error.Note: The "Whse.-Post Receipt" codeunit includes several unconditional commits in standard code, including for every source document posted. When you rely on standard code rollback for your custom code for Warehouse Receipts, this needs to be taken into account and the standard integration event you are subscribing to must be selected carefully.


Template

    [EventSubscriber(ObjectType::CodeunitCodeunit::"MOB WMS Production Consumption", 'OnPostProdConsumption_OnBeforePostProdOrderLine''', true, true)]
    local procedure OnPostProdConsumption_OnBeforePostProdOrderLine(var _OrderValues: Record "MOB Common Element"; var _ProdOrderLine: Record "Prod. Order Line")
    begin
        // Add your custom code here...
        // Note: OnBeforePost-events is committed to the database prior to posting. Your custom code must be structured accordingly (or use standard BC events).
    end;

Example

    See: Case: Add Header Signature step for inbound goods documents

...