Page Comparison

Use this event to

...

...

If your code is not specific for to Sales Order Lines consider Lines consider using the the OnPostReceiveOrder_OnHandleRegistrationForAnyLine event.

Description

This event is used to handle collected "line" level steps and is executed once for each individual Mobile WMS Registration.

...

• Write collected values to new or existing fields in the database that 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.
• But notNot to process "header" level steps.  Steps added via OnAddStepsToAnyHeader[...] is better handled via OnPostReceiveOrder_OnBeforePost...-events.
  
  

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.

Item Tracking

For Sales Return orders it is assumed that the item tracking details have been entered on the line when the return order was created.
So reservation entries are not created.

Template

    [EventSubscriber(ObjectType::Codeunit, Codeunit::"MOB WMS Receive", 'OnPostReceiveOrder_OnHandleRegistrationForSalesReturnLine', '', true, true)]
    local procedure OnPostReceiveOrder_OnHandleRegistrationForSalesReturnLine(var _Registration: Record "MOB WMS Registration"; var _SalesReturnLine: Record "Sales Line")
    begin
    end;

...