Use this event to
...
- Write 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 this event |
...
is committed to database prior to |
...
calling standard BC posting routines. Your customized code must be structured accordingly. Nearly always you |
...
...
to do your actual processing to ensure rollback of database transactions on error. Note: The "Sales-Post"-codeunit includes commits in standard code that is not always correctly suppressed for Sales Return Orders, even if SalesPost.SetSuppressCommit(true); is set. This needs to be taken into account and tested carefully before relying on SalesPost rollback for your custom code for Sales Return Orders. |
If your code is not specific for Sales Return Transfer Orders consider using the OnPostPickOrder_OnBeforePostAnyOrder event.
...
Template
[EventSubscriber(ObjectType::Codeunit, Codeunit::"MOB WMS Receive", 'OnPostReceiveOrder_OnBeforePostTransferOrder', '', true, true)]
procedure OnPostReceiveOrder_OnBeforePostTransferOrder(var _OrderValues: Record "MOB Common Element"; _TransferHeader: Record "Transfer Header")
begin
end;
| Filter by label (Content by label) | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...