1 · D3_CODCaractereRequired
Source product. SB1->B1_COD in the example.
AUTOMATIC ROUTINEPublished
MATA261 — ExecAuto for warehouse transfer
MATA261 via MsExecAuto · estrutura posicional de aLinhaReference guide for developing the MATA261 ExecAuto call in AdvPL, with attention to the positional aLinha structure.
Overview
This page documents routine MATA261 from an AdvPL development perspective: how to prepare the structure sent to MsExecAuto, which positions compose aLinha and which cautions matter when validating the automatic routine contract. In versions later than the historical 11.8 sample, aLinha is positional: every value must remain in the exact position expected by the routine, including empty positions. The goal is to serve as a programming reference guide; functional Protheus process explanations may be linked from a dedicated site in the future.
Syntax
MATA261 via MsExecAuto · estrutura posicional de aLinhaParameters
2 · D3_DESCRICaractereRequired
Source product description.
3 · D3_UMCaractereRequired
Source unit of measure.
4 · D3_LOCALCaractereRequired
Source warehouse. 07 in the example.
5 · D3_LOCALIZCaractereOptional
Source location. Keep the position even when empty.
6 · D3_CODCaractereRequired
Destination product. The same code as the source in the example.
7 · D3_DESCRICaractereRequired
Destination product description.
8 · D3_UMCaractereRequired
Destination unit of measure.
9 · D3_LOCALCaractereRequired
Destination warehouse. 11 in the example.
10 · D3_LOCALIZCaractereOptional
Destination location. Keep the position even when empty.
11 · D3_NUMSERICaractereOptional
Serial number when applicable.
12 · D3_LOTECTLCaractereOptional
Source control lot.
13 · D3_NUMLOTECaractereOptional
Source lot/sub-lot according to the control used.
14 · D3_DTVALIDDataOptional
Source expiration date. Use CTOD("") when not applicable.
15 · D3_POTENCINuméricoOptional
Potency. Zero in the example.
16 · D3_QUANTNuméricoRequired
Transferred quantity. aDados[nX][2] in the example.
17 · D3_QTSEGUMNuméricoOptional
Second-unit quantity. Zero in the example.
18 · D3_ESTORNOCaractereOptional
Reversal indicator/information.
19 · D3_NUMSEQCaractereOptional
Sequence number related to the movement.
20 · D3_LOTECTLCaractereOptional
Control lot in the destination section. This repeated position is intentional.
21 · D3_DTVALIDDataOptional
Expiration date in the destination section. Use CTOD("") when not applicable.
22 · D3_ITEMGRDCaractereOptional
Grid item when applicable.
23 · D3_OBSERVACaractereOptional
Movement note. OVHL in the example.
Return value
This page documents the item-row structure; return values and error handling depend on the MsExecAuto flow used by the caller.
Positional structure for later versions
Local aLine := {}
AAdd(aLine, SB1->B1_COD) // D3_COD - source
AAdd(aLine, SB1->B1_DESC) // D3_DESCRI - source
AAdd(aLine, SB1->B1_UM) // D3_UM - source
AAdd(aLine, "07") // D3_LOCAL - source
AAdd(aLine, "") // D3_LOCALIZ - source
AAdd(aLine, SB1->B1_COD) // D3_COD - destination
AAdd(aLine, SB1->B1_DESC) // D3_DESCRI - destination
AAdd(aLine, SB1->B1_UM) // D3_UM - destination
AAdd(aLine, "11") // D3_LOCAL - destination
AAdd(aLine, "") // D3_LOCALIZ - destination
AAdd(aLine, "") // D3_NUMSERI
AAdd(aLine, "") // D3_LOTECTL - source
AAdd(aLine, "") // D3_NUMLOTE - source
AAdd(aLine, CTOD("")) // D3_DTVALID - source
AAdd(aLine, 0) // D3_POTENCI
AAdd(aLine, aData[nX][2]) // D3_QUANT
AAdd(aLine, 0) // D3_QTSEGUM
AAdd(aLine, "") // D3_ESTORNO
AAdd(aLine, "") // D3_NUMSEQ
AAdd(aLine, "") // D3_LOTECTL - destination
AAdd(aLine, CTOD("")) // D3_DTVALID - destination
AAdd(aLine, "") // D3_ITEMGRD
AAdd(aLine, "OVHL") // D3_OBSERVAExpected result
The row contains 23 positions and transfers the product from warehouse 07 to 11.
Why the 11.8 sample should not be copied literally
// Referência histórica: estrutura identificada por campo
// { "D3_COD", <valor>, Nil }
//
// Versões posteriores deste guia: estrutura posicional
// AAdd(aLinha, <valor-da-posicao-1>)
// AAdd(aLinha, <valor-da-posicao-2>)
// ...Expected result
The legacy field-identified format and the later positional format are different contracts.
- The TOTVS Support Center reference cited here is historical and targets Protheus 11.8; use it as a conceptual basis and validate the automatic routine contract in the release being used.
- In the later versions covered by this example, aLinha is positional. Do not remove a position because its field is empty.
- Keep the expected type in empty positions: empty strings for character fields, CTOD("") for dates and zero for numeric fields.
- Positions 1–5 represent the source product/warehouse and positions 6–10 represent the destination product/warehouse.
- D3_LOTECTL and D3_DTVALID appear again at positions 20 and 21; do not collapse these positions.
- Revalidate the array after release, patch or related package updates.
- Mixing the 11.8 format with the later positional format can cause execution errors or incorrect values.
- Moving one value shifts the interpretation of every following position.
- Field names in comments do not replace the positional contract.
- Scenarios with lot, serial, location or second-unit control require their corresponding positions to be filled according to the environment configuration and the routine contract.
Comments
There are no approved comments yet.
Sign in with Google or Microsoft to comment.