Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Current »

Use this event to

Handle collected values from Header Steps for a Shipment.

Description

This event is used to handle collected "header" level steps and is executed only once per order posting from the mobile device.

Examples of use could be:

  • 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 OnAddStepsToAnyLine[...] is better handled via OnPostShipOrder_OnHandleRegistrationFor...-events.


Commit

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.-Activity-Post" and "Whse.-Activity-Register" codeunits includes several unconditional commits in standard code, including for every source document posted. When you rely on standard code rollback for your custom code , 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 Ship", 'OnPostShipOrder_OnBeforePostWarehouseShipment''', true, true)]
    procedure OnPostShipOrder_OnBeforePostWarehouseShipment(var _OrderValues: Record "MOB Common Element"; var _WhseShipmentHeader: Record "Warehouse Shipment Header")
    begin
    end;


Examples



Version History

Version

Changes

MOB5.11Introduced
  • No labels