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

Use this event to

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 Sales Order 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:

  • 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.


Commit

Error rendering macro 'excerpt-include' : No link could be created for 'Shared text - Commit'.

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::CodeunitCodeunit::"MOB WMS Receive", 'OnPostReceiveOrder_OnBeforePostSalesReturnOrder''', true, true)]
    procedure OnPostReceiveOrder_OnBeforePostSalesReturnOrder(var _OrderValues: Record "MOB Common Element"; var _SalesReturnHeader: Record "Sales Header")
    begin
    end;



Examples


Version History

VersionChanges
MOB5.11Introduced
  • No labels