Use this event to
| Excerpt |
|---|
Handle collected values from Header Steps for a Transfer Order or set arguments in standard posting routine. |
If your code is not specific for Transfer Lines consider using the OnPostReceiveOrder_OnBeforePostAnyOrder event.
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 OnPostReceiveOrder_OnHandleRegistrationFor...
...
- -events.
| Note | ||
|---|---|---|
| ||
Database transactions in [...]OnBeforePostTransferOrderthis event is committed to database prior to calling standard "TransferOrder-Post Receipt" functionBC posting routines. Your customized code must be structured accordingly. You may Nearly always you must subscribe to standard BC posting events to do your actual processing to ensure rollback of your database transactions or trigger events on-after posting, if this is required for your code. |
See also:
How-to: Subscribe to standard events in BC base app
on error. |
Template
[EventSubscriber(ObjectType::Codeunit, Codeunit::"MOB WMS Receive", 'OnPostReceiveOrder_OnBeforePostTransferOrder', '', true, true)]
local procedure OnPostReceiveOrder_OnBeforePostTransferOrder(var _OrderValues: Record "MOB Common Element"; var _TransferHeader: Record "Transfer Header")
begin
end;
| Filter by label (Content by label) | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...