Mandatory fields: MovementOrder

As movement orders can be tailored to suit customer needs, there are no fields that are always mandatory. The minimum amount of data required for entering movement orders is very small. However, you should bear in mind that the actual amount needed to create meaningful orders and to progress those orders is much larger. This is wholly dependant on how your system is configured.

As a guide, you will probably find that the following need to be supplied:

• Movement Order Definition Code - payload element <MovementOrderDefinitionCode>
• Movement Order Reference - payload element <MovementOrderReference>
• Either User Line Number - payload element <UserLineNumber> or Line Number - payload element <LineNumber>.

See individual methods for specific field requirements.

Standard Text

When creating or attaching standard text associated with a Movement Order, values for the following must be supplied:

• Standard Text Class Code - payload element <StdTextMo_StdTextClassCode>
• Standard Text Code - payload element <StdTextMo_StdTextCode>.

When creating or attaching standard text associated with a Movement Order Line, values for the following must be supplied:

• Standard Text Class Code - payload element <StdTextMo1_StdTextClassCode>
• Standard Text Code - payload element <StdTextMo1_StdTextCode>.
  注意：At runtime the component validates the payload contents to ensure that the values supplied are correct. Various combinations of values may require other elements in the payload to be specified before the payload can be processed successfully.

Example Payload using CreateOrAmendWithSerialNumbers

Receipt:

For an example payload, two items codes are used - ITMAUTO, with automated serial numbers, and ITMUSER, with user generated serial numbers. A payload for a three line movement order is given below:

<MovementOrder>

...

<MovementOrderLine>

<DemandQuantity>2</DemandQuantity>

<ItemCode>ITMAUTO</ItemCode>

<LineNumber>1</LineNumber>

...

</MovementOrderLine>

<MovementOrderLine>

<DemandQuantity>4</DemandQuantity>

<ItemCode>ITMAUTO</ItemCode>

<LineNumber>2</LineNumber>

...

</MovementOrderLine>

<MovementOrderLine>

<DemandQuantity>3</DemandQuantity>

<ItemCode>ITMUSER</ItemCode>

<LineNumber>3</LineNumber>

….

</MovementOrderLine>

<SerialNumbersForLine>

<SerialNumbers></SerialNumbers>

</SerialNumbersForLine>

<SerialNumbersForLine>

<SerialNumbers>

<SerialNumber>USERENTERED1</SerialNumber>

</SerialNumbers>

<SerialNumbers>

<SerialNumber>USERENTERED2</SerialNumber>

</SerialNumbers>

<SerialNumbers>

<SerialNumber>USERENTERED3</SerialNumber>

</SerialNumbers>

</SerialNumbersForLine>

</MovementOrder>

Issue:

The example payload here uses the same two items codes as the Receipts example - ITMAUTO, with automated serial numbers, and ITMUSER, with user generated serial numbers. However, for Issues the serial number format used does not make any difference – the requirement is for the correct number of valid serial numbers for the item code. The example below assumes that Value Label 1 is used for Quantity (i.e. 3 of ITMAUTO and 2 of ITMUSER)

<MovementOrder>

...

<MovementOrderLine>

<ItemCode>ITMAUTO</ItemCode>

<LineNumber>1</LineNumber>

...

<VLAB1>

<Base>

<VMolVlabEntry_Val>3.00000</VMolVlabEntry_Val>

</Base>

</VLAB1>

<IssueSerialNumbers>

<IssueSerialNumber>

<SerialNumber>A000004</SerialNumber>

</IssueSerialNumber>

<IssueSerialNumber>

<SerialNumber>A000123</SerialNumber>

</IssueSerialNumber>

<IssueSerialNumber>

<SerialNumber>A000041</SerialNumber>

</IssueSerialNumber>

</IssueSerialNumbers>

</MovementOrderLine>

<MovementOrderLine>

<ItemCode>ITMUSER</ItemCode>

<LineNumber>2</LineNumber>

….

<VLAB1>

<Base>

<VMolVlabEntry_Val>2.00000</VMolVlabEntry_Val>

</Base>

</VLAB1>

<IssueSerialNumbers>

<IssueSerialNumber>

<SerialNumber>USERENTERED5</SerialNumber>

</IssueSerialNumber>

<IssueSerialNumber>

<SerialNumber>USERENTERED4</SerialNumber>

</IssueSerialNumber>

</IssueSerialNumbers>

</MovementOrderLine>

</MovementOrder>