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 5 Next »



Code to be executed prior to posting via standard posting routines. When migrating code from older MOB versions, this event is the most direct 1:1 comparison to existing in-line customizations.

Template:

    [EventSubscriber(ObjectType::CodeunitCodeunit::"MOB WMS Receive", 'OnPostReceiveOrder_OnBeforePostTransferOrder''', true, true)]
    procedure OnPostReceiveOrder_OnBeforePostTransferOrder(var _OrderValues: Record "MOB Common Element"; _TransferHeader: Record "Transfer Header")
    begin
    end;


Desccription:

The event is mostly used to validate collected "header" level steps (added from OnGetReceiveOrderLines_OnAddStepsToAnyHeader) and to write collected header level steps values to fields in the database that subsequently can be accessed from standard posting function events.

Steps added at "line" level via OnGetReceiveOrderLines_OnAfterAddStepsAnyLine (Q4 2019) is generally handled via OnHandleRegistrationFor[...]-events.


Commit

Database transactions in [...]OnBeforePostTransferOrder is committed to database prior to calling standard "TransferOrder-Post Receipt" function. Your customized code must be structured accordingly.

You may subscribe to standard posting events to ensure rollback of your database transactions or trigger events on-after posting, if this is required for your code.


See also: 
OnGetReceiveOrderLines_OnAddStepsToAnyHeader

OnPostReceiveOrder_OnBeforePostAnyOrder

OnGetReceiveOrderLines_OnHandleRegistrationFor[...] TODO

How-to: Subscribe to standard events in BC base app

Example:

See:
Case: Add a new text collector step on headers for inbound goods documents (BC)


Version History:

Version

Changes

MOB5.11Introduced
  • No labels