Table 6650 "Return Shipment Header"

Base Application · Microsoft.Purchases.History · BC23-30 · source at ea08af5e · facts from BC29

Learn documents this table through its pages: Page 6652 “Posted Return Shipments” (2 Learn pages), Page 6650 “Posted Return Shipment” (1).

Properties

Fields

Explanation: the field’s ToolTip in the code; without one, the ToolTip of a page control bound to the field (marked via the page); without that, its Caption (marked caption) when that differs from the name.

Keys

• Key1: No. (clustered)
• Key2: Return Order No.
• Key3: Buy-from Vendor No.
• Key4: Pay-to Vendor No.
• Key5: Posting Date

Events published

• OnBeforeSetSecurityFilterOnRespCenter(var ReturnShipmentHeader: Record "Return Shipment Header"; var IsHandled: Boolean) (integration)
• OnLookupAppliesToDocNoOnAfterSetFilters(var VendLedgEntry: Record "Vendor Ledger Entry"; ReturnShipmentHeader: Record "Return Shipment Header") (integration)
• OnBeforePrintRecords(var ReturnShipmentHeader: Record "Return Shipment Header"; ShowRequestForm: Boolean; var IsHandled: Boolean) + BC24 (integration)

Procedures

• PrintRecords(ShowRequestForm: Boolean)
• Navigate()
• ShowDimensions()
• SetSecurityFilterOnRespCenter()

Triggers

OnDelete

Relations

• drill-down page Page 6652 “Posted Return Shipments”
• lookup page Page 6652 “Posted Return Shipments”
• Shipment Method Code: TableRelation Table 10 “Shipment Method”
• Purchaser Code: TableRelation Table 13 “Salesperson/Purchaser”
• Location Code: TableRelation Table 14 “Location”
• Bal. Account No.: TableRelation Table 15 “G/L Account” (conditional)
• Sell-to Customer No.: TableRelation Table 18 “Customer”
• Ship-to Code: TableRelation Table 222 “Ship-to Address”
• Order Address Code: TableRelation Table 224 “Order Address”
• Buy-from City: TableRelation Table 225 “Post Code” (conditional)
• Buy-from Post Code: TableRelation Table 225 “Post Code” (conditional)
• Pay-to City: TableRelation Table 225 “Post Code” (conditional)
• Pay-to Post Code: TableRelation Table 225 “Post Code” (conditional)
• Ship-to City: TableRelation Table 225 “Post Code” (conditional)
• Ship-to Post Code: TableRelation Table 225 “Post Code” (conditional)
• Buy-from Vendor No.: TableRelation Table 23 “Vendor”
• Pay-to Vendor No.: TableRelation Table 23 “Vendor”
• Source Code: TableRelation Table 230 “Source Code”
• Reason Code: TableRelation Table 231 “Reason Code”
• Gen. Bus. Posting Group: TableRelation Table 250 “Gen. Business Posting Group”
• Transaction Type: TableRelation Table 258 “Transaction Type”
• Transport Method: TableRelation Table 259 “Transport Method”
• Bal. Account No.: TableRelation Table 270 “Bank Account” (conditional)
• Entry Point: TableRelation Table 282 “Entry/Exit Point”
• Area: TableRelation Table 284 “Area”
• Transaction Specification: TableRelation Table 285 “Transaction Specification”
• Payment Method Code: TableRelation Table 289 “Payment Method”
• Payment Terms Code: TableRelation Table 3 “Payment Terms”
• No. Series: TableRelation Table 308 “No. Series”
• Return Order No. Series: TableRelation Table 308 “No. Series”
• Tax Area Code: TableRelation Table 318 “Tax Area”
• VAT Bus. Posting Group: TableRelation Table 323 “VAT Business Posting Group”
• Shortcut Dimension 1 Code: TableRelation Table 349 “Dimension Value”
• Shortcut Dimension 2 Code: TableRelation Table 349 “Dimension Value”
• Currency Code: TableRelation Table 4 “Currency”
• Comment: CalcFormula Table 43 “Purch. Comment Line”
• Dimension Set ID: TableRelation Table 480 “Dimension Set Entry”
• Buy-from Contact No.: TableRelation Table 5050 “Contact”
• Pay-to Contact No.: TableRelation Table 5050 “Contact”
• Campaign No.: TableRelation Table 5071 “Campaign”
• Responsibility Center: TableRelation Table 5714 “Responsibility Center”
• Language Code: TableRelation Table 8 “Language”
• Buy-from Country/Region Code: TableRelation Table 9 “Country/Region”
• Pay-to Country/Region Code: TableRelation Table 9 “Country/Region”
• Ship-to Country/Region Code: TableRelation Table 9 “Country/Region”
• VAT Country/Region Code: TableRelation Table 9 “Country/Region”
• Vendor Posting Group: TableRelation Table 93 “Vendor Posting Group”

Referenced by

10 fields in 8 objects relate to this table (TableRelation or CalcFormula).

• Table 23 “Vendor”: No. of Pstd. Return Shipments, Pay-to No. of Pstd. Return S.
• Table 6651 “Return Shipment Line”: Currency Code, Document No.
• Table 38 “Purchase Header”: Last Return Shipment No.
• Table 5109 “Purchase Header Archive”: Last Return Shipment No.
• Table 7340 “Posted Invt. Put-away Header”: Source No.
• Table 7342 “Posted Invt. Pick Header”: Source No.
• Table 7344 “Registered Invt. Movement Hdr.”: Source No.
• Table 780 “Certificate of Supply”: Document No.

Pages and codeunits on this table

• Page 1352 “Posted Return Shpt. - Update” (source table)
• Page 30200 “APIV2 - Purch. Ret. Shpts.” (source table)
• Page 6650 “Posted Return Shipment” (source table)
• Page 6652 “Posted Return Shipments” (source table)
• Page 6655 “Return Shipment Statistics” (source table)
• Codeunit 1406 “Return Shipment Header - Edit” (codeunit runs on it)
• Codeunit 6651 “Return Shipment - Printed” (codeunit runs on it)

Extended by

• Table extension 6801 “WHT Return Shipment Header”

Calls

From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.

• Codeunit 364 “PostPurch-Delete” (2 calls: OnDelete → DeletePurchShptLines, OnDelete → IsDocumentDeletionAllowed)
• Codeunit 1535 “Approvals Mgmt.” (1 call: OnDelete → DeletePostedApprovalEntries)
• Codeunit 408 “DimensionManagement” (1 call: ShowDimensions → ShowDimensionSet)
• Codeunit 5700 “User Setup Management” (1 call: SetSecurityFilterOnRespCenter → GetPurchasesFilter)

Countries that replace it

AU, BE, IT, NZ, RU

Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).

Ask your agent

Procedure bodies are not stored here (D10). The call sections above are our own, per object, from the BC29 call graph. For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: bcatlas_resolve_node(object_type: "table", object_name: "Return Shipment Header"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.