Use this event to
| Excerpt |
|---|
Handle collected values from Header Steps for a Sales Return Order or set arguments in standard posting routine. |
If your code is not specific for to Sales Lines consider Lines consider using the the OnPostReceiveOrder_OnBeforePostAnyOrder event.
...
Examples of use could be:
- Write 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 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 "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. |
Template
[EventSubscriber(ObjectType::Codeunit, Codeunit::"MOB WMS Receive", 'OnPostReceiveOrder_OnBeforePostSalesReturnOrder', '', true, true)]
local procedure OnPostReceiveOrder_OnBeforePostSalesReturnOrder(var _OrderValues: Record "MOB Common Element"; var _SalesReturnHeader: Record "Sales Header")
begin
end;
| Filter by label (Content by label) | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Version History
| Version | Changes |
|---|---|
| MOB5.11 | Introduced |