Use this event to
Add steps to be displayed at the mobile device when collecting values for each individual Consumption Line (component).
Description
Steps at line level (collected for each individual line) requires a collectorConfiguration-Key to be declared in Reference Data.
This is unlike steps at header level, that allows steps to be declared directly in the OnGetProdConsumptionLines_OnAddStepsToProdOrderLine event.
Line-level steps are:
- ...declared as part of a collectorConfiguration-Key in Reference Data.
- ...added by calling the Create_StepsByReferenceDataKey-function (Currently only once)
- ...sorted by Id. Sorting can be changed using the
<orderLineConfiguration><extraInformationConfiguration stepSorting="ById"/><orderLineConfiguration/>
in mobile configuration.
Currently Mobile WMS supports only one (custom) referenced key per Order Line, meaning only one customization may subscribe to this event at any time. This single one subscriber must set a Key that includes all steps for all other intended subscribers as well. This can only be done by knowing other customizations are in place and manually create a new RegistrationCollectorConfigurationKey that includes all steps (this will improve in a future version).
Template
[EventSubscriber(ObjectType::Codeunit, Codeunit::"MOB WMS Production Consumption", 'OnGetProdConsumptionLines_OnAddStepsToProdOrderComponent', '', true, true)]
local procedure OnGetProdConsumptionLines_OnAddStepsToProdOrderComponent(_ProdOrderComponent: Record "Prod. Order Component"; _TrackingSpecification: Record "Tracking Specification"; var _BaseOrderLineElement: Record "MOB Ns BaseDataModel Element")
begin
end;
Example
// [Example]: Add steps referenced by new RegistrationCollectorConfiguration-Key to line steps collectors
[EventSubscriber(ObjectType::Codeunit, Codeunit::"MOB WMS Production Consumption", 'OnGetProdConsumptionLines_OnAddStepsToProdOrderComponent', '', true, true)]
local procedure MyOnGetProdConsumptionLines_OnAddStepsToProdOrderComponent(_ProdOrderComponent: Record "Prod. Order Component"; _TrackingSpecification: Record "Tracking Specification"; var _BaseOrderLineElement: Record "MOB Ns BaseDataModel Element")
begin
_BaseOrderLineElement.Create_StepsByReferenceDataKey('CustomConsumptionSteps', true);
end;
[EventSubscriber(ObjectType::Codeunit, Codeunit::"MOB WMS Reference Data", 'OnGetReferenceData_OnAddRegistrationCollectorConfigurations', '', true, true)]
local procedure MyOnGetReferenceData_OnAddRegistrationCollectorConfigurations(var _Steps: Record "MOB Steps Element")
begin
_Steps.InitConfigurationKey('CustomConsumptionSteps');
_Steps.Create_DecimalStep(10000, 'CustomNetWeightGrams');
_Steps.Set_header('Net Weight (Grams)');
_Steps.Set_label('Net Weight (Grams):');
_Steps.Set_helpLabel('Net Weight in Grams per Base Unit of Measure');
_Steps.Set_minValue(0);
_Steps.Set_maxValue(100000);
_Steps.Set_performCalculation(true);
end;
More examples
-
Case: Add Posting Date step to Production Consumption and Output — A customer wishes to allow mobile users to specify the posting date when posting Production Consumption and Output from the mobile device.
-
Case: Scan ExpirationDate in custom format — Scan ExpirationDate as custom format YYYYMM when goods is received from any Vendor.
-
How-to: Production Output - Implement a Unit of Measure step — For Items with multiple Unit of Measure codes
Version History
Version | Changes |
---|---|
MOB5.22 | Introduced |