← All topicsENTRY POINTUnder review
F241ORD
ExecBlock("F241ORD", .F., .F., {aRecNosSE2, "SE2"})Call in F241IMPOST with two context elements and the return assigned to aRetOrd.
F241ORDFINA241F241IMPOSTaRecNosSE2aRetOrd
01 · OVERVIEWOverview
The official index lists F241Ord in FINA241, with documentation under construction. (TOTVS, n.d., ref. 1) The P12.2210 community listing shows F241ORD in F241IMPOST, receiving {aRecNosSE2, "SE2"} and assigning the result to aRetOrd. (Universo do Desenvolvedor, 2023, ref. 2) The excerpt provides neither an implementation nor subsequent return use. GitHub searches found no useful implementation.
02 · SYNTAXSyntax
ExecBlock("F241ORD", .F., .F., {aRecNosSE2, "SE2"})
Parameters
PARAMIXB[1] / aRecNosSE2Type and layout unconfirmedContext to confirm
First element of the array passed by the call: aRecNosSE2. The ExecBlock mechanism exposes it as PARAMIXB[1]. (Refs. 2–3) Its type, element layout and value meanings are unconfirmed; the name alone does not prove it is an array of RecNos.
PARAMIXB[2] / "SE2"CharacterContext to confirm
Second element: the literal string "SE2", available as PARAMIXB[2] through ExecBlock. (Refs. 2–3) The excerpt does not establish that this alias is open or positioned, nor authorize direct table operations.
Return value
The result is assigned to aRetOrd. Its variable prefix does not establish type, positions or expected layout. Do not recommend returning the context array, aRecNosSE2, NIL or a logical value without inspecting return consumption.
03 · PRACTICAL EXAMPLEDocumentary caller excerpt
// P12.2210 listing: FINA241.PRX / F241IMPOST() (ref. 2).
// The outer array has two elements; subsequent aRetOrd use is absent.
aRetOrd := ExecBlock("F241ORD", .F., .F., {aRecNosSE2, "SE2"})
Expected resultShows the two input values and return destination. It is a caller excerpt, not an F241ORD implementation or a standalone executable program.
BEST PRACTICES- Do not infer sorting, grouping or tax priority rules from the ORD name alone.
- Distinguish the outer array {aRecNosSE2, "SE2"} from the value in its first element; do not treat all of PARAMIXB as aRecNosSE2.
- Before implementing, inspect aRecNosSE2 preparation and every subsequent aRetOrd read in the target release and patch.
- Editorial test plan: record types and layout in a test environment and compare processing before and after customization once the contract is established. Do not modify data to discover the layout.
- The F241IMPOST association is observed in the listing; invocation frequency, active aliases and transaction position remain unconfirmed.
- Under review: not compiled or run in Protheus. Official index consulted through indexed evidence; community excerpt read directly.
Comments
There are no approved comments yet.
Sign in with Google or Microsoft to comment.