Table 18606 "Posted Gate Entry Header" (IN)

IN country layer · Microsoft.Warehouse.GateEntry · BC29-30 · source at ea08af5e · facts from BC29

An object of the IN localization, not part of W1.

Properties

Property	Value
Caption	Posted Gate Entry Header

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	Entry Type	Enum “Gate Entry Type”	—	enum Gate Entry Type; DataClassification EndUserIdentifiableInformation
2	No.	Code[20]	—	DataClassification EndUserIdentifiableInformation
3	No. Series	Code[20]	—	TableRelation No. Series; DataClassification EndUserIdentifiableInformation
4	Document Date	Date	—	DataClassification EndUserIdentifiableInformation
5	Document Time	Time	—	DataClassification EndUserIdentifiableInformation
7	Location Code	Code[10]	—	TableRelation Location; DataClassification EndUserIdentifiableInformation
8	Description	Text[120]	—	DataClassification EndUserIdentifiableInformation
9	Item Description	Text[120]	—	DataClassification EndUserIdentifiableInformation
10	LR/RR No.	Code[20]	—	DataClassification EndUserIdentifiableInformation
11	LR/RR Date	Date	—	DataClassification EndUserIdentifiableInformation
12	Vehicle No.	Code[20]	—	DataClassification EndUserIdentifiableInformation
13	Station From/To	Code[20]	—	DataClassification EndUserIdentifiableInformation
15	Comment	Boolean	—	FlowField: Exist(“Gate Entry Comment Line” where(“Gate Entry Type” = field(“Entry Type”), “No.” = field(“No.”)))
17	Posting Date	Date	—	DataClassification EndUserIdentifiableInformation
18	Posting Time	Time	—	DataClassification EndUserIdentifiableInformation
19	Gate Entry No.	Code[20]	—	DataClassification EndUserIdentifiableInformation
20	User ID	Code[50]	—	TableRelation User.“User Name”; DataClassification EndUserIdentifiableInformation

Keys

Key1: Entry Type, No. (clustered)
Key2: Location Code, Posting Date, No.

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: "Posted Gate Entry Header"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

A IN country object, not part of W1: the default corpus does not have it; bcatlas_list_countries shows which countries the atlas has.