Table 282 "Entry/Exit Point"
Base Application · Microsoft.Inventory.Intrastat
Across versions
- BC23present
- BC24declaration changed
- BC25-27unchanged
- BC282 fields changed
- BC29-30unchanged
Neighbourhood 45 connected objects and pages
Base Application · Microsoft.Inventory.Intrastat · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Entry/Exit Point |
| DataClassification | CustomerContent |
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.
| No. | Name | Type | Explanation | Notes |
|---|---|---|---|---|
| 1 | Code Δ BC28 | Code[10] | Specifies the code for the shipping location (Entry/Exit Point). | NotBlank |
| 2 | Description Δ BC28 | Text[100] | Specifies a description of the shipping location (Entry/Exit Point). |
Keys
- Key1: Code (clustered)
Relations
- drill-down page Page 394 “Entry/Exit Points”
- lookup page Page 394 “Entry/Exit Points”
Referenced by
44 fields in 44 objects relate to this table (TableRelation or CalcFormula).
- Table 110 “Sales Shipment Header”: Exit Point
- Table 111 “Sales Shipment Line”: Exit Point
- Table 112 “Sales Invoice Header”: Exit Point
- Table 113 “Sales Invoice Line”: Exit Point
- Table 114 “Sales Cr.Memo Header”: Exit Point
- Table 115 “Sales Cr.Memo Line”: Exit Point
- Table 120 “Purch. Rcpt. Header”: Entry Point
- Table 121 “Purch. Rcpt. Line”: Entry Point
- Table 122 “Purch. Inv. Header”: Entry Point
- Table 123 “Purch. Inv. Line”: Entry Point
- Table 124 “Purch. Cr. Memo Hdr.”: Entry Point
- Table 125 “Purch. Cr. Memo Line”: Entry Point
- Table 169 “Job Ledger Entry”: Entry/Exit Point
- Table 210 “Job Journal Line”: Entry/Exit Point
- Table 263 “Intrastat Jnl. Line”: Entry/Exit Point
- Table 32 “Item Ledger Entry”: Entry/Exit Point
- Table 36 “Sales Header”: Exit Point
- Table 37 “Sales Line”: Exit Point
- Table 38 “Purchase Header”: Entry Point
- Table 39 “Purchase Line”: Entry Point
- Table 4812 “Intrastat Report Line”: Entry/Exit Point
- Table 5107 “Sales Header Archive”: Exit Point
- Table 5108 “Sales Line Archive”: Exit Point
- Table 5109 “Purchase Header Archive”: Entry Point
- Table 5110 “Purchase Line Archive”: Entry Point
- Table 5740 “Transfer Header”: Entry/Exit Point
- Table 5744 “Transfer Shipment Header”: Entry/Exit Point
- Table 5746 “Transfer Receipt Header”: Entry/Exit Point
- Table 5900 “Service Header”: Exit Point
- Table 5902 “Service Line”: Exit Point
- Table 5990 “Service Shipment Header”: Exit Point
- Table 5991 “Service Shipment Line”: Exit Point
- Table 5992 “Service Invoice Header”: Exit Point
- Table 5993 “Service Invoice Line”: Exit Point
- Table 5994 “Service Cr.Memo Header”: Exit Point
- Table 5995 “Service Cr.Memo Line”: Exit Point
- Table 6010 “Service Header Archive”: Exit Point
- Table 6012 “Service Line Archive”: Exit Point
- Table 6650 “Return Shipment Header”: Entry Point
- Table 6651 “Return Shipment Line”: Entry Point
- Table 6660 “Return Receipt Header”: Exit Point
- Table 6661 “Return Receipt Line”: Exit Point
- Table 753 “Standard Item Journal Line”: Entry/Exit Point
- Table 83 “Item Journal Line”: Entry/Exit Point
Pages and codeunits on this table
- Page 394 “Entry/Exit Points” (source table)
Countries that replace it
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). 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: "Entry/Exit Point"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.