tableWarehouseofficial - Microsoftderived - from the source, no model text

Table 7340 "Posted Invt. Put-away Header"

Base Application · Microsoft.Warehouse.InventoryDocument

Across versions

  1. BC23present
  2. BC241 fields changed
  3. BC25unchanged
  4. BC261 fields changed
  5. BC27unchanged
  6. BC2810 fields changed
  7. BC29-30unchanged

Neighbourhood 15 connected objects and pages

Table 14 "Location" (relates to, 2 links)LocationTable 110 "Sales Shipment Header" (relates to)Sales Shipment HeaderTable 120 "Purch. Rcpt. Header" (relates to)Table 18 "Customer" (relates to)CustomerTable 23 "Vendor" (relates to)VendorTable 27 "Item" (relates to)ItemTable 308 "No. Series" (relates to)No. SeriesTable 36 "Sales Header" (relates to)Sales HeaderTable 5770 "Warehouse Comment Line" (relates to)Warehouse Comment LineTable 6650 "Return Shipment Header" (relates to)Return Shipment HeaderTable 7301 "Warehouse Employee" (relates to)Page 7394 "Posted Invt. Put-away List" (pages and codeunits on it, 2 links)Posted Invt. Put-away ListPage 7390 "Posted Invt. Put-away" (pages and codeunits on it)Posted Invt. Put-awayTable extension 99000775 "Mfg. Posted InvtPutaway Header" (extended by)Mfg. Posted InvtPutaway HeaderPage 456 "No. Series" (calls)No. Series

Open in the neighbourhood explorer

One hop out, from the extracted relations and call graph. Up to 40 shown; the sections below list them all.

Base Application · Microsoft.Warehouse.InventoryDocument · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Posted Invt. Put-away Header
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
2 No. Δ BC28 Code[20] Specifies the number of the involved entry or record, according to the specified number series.
3 Location Code Δ BC28 Code[10] Specifies the code of the location in which the posted inventory put-away occurred. TableRelation Table 14 “Location”; NotBlank
4 Assigned User ID Code[50] — TableRelation Table 7301 “Warehouse Employee” (“Warehouse Employee” where(“Location Code” = field(“Location Code”))); DataClassification EndUserIdentifiableInformation
5 Assignment Date Date —
6 Assignment Time Time —
8 Registering Date Date —
9 No. Series Δ BC28 Code[20] Specifies the number series from which entry or record numbers are assigned to new entries or records. TableRelation Table 308 “No. Series” (No. Series); not editable
10 Comment Δ BC24 Boolean — FlowField: exist(“Warehouse Comment Line” where(“Table Name” = const(“Posted Invt. Put-Away”), Type = const(” “), “No.” = field(“No.”))); not editable
11 Invt. Put-away No. Δ BC28 Code[20] Specifies the inventory put-away number from which the put-away was posted.
12 No. Printed Integer — not editable
20 Posting Date Δ BC28 Date Specifies the posting date from the inventory put-away.
7306 Source No. Δ BC28 Code[20] Specifies the number of the source document that the entry originates from. TableRelation Table 110 “Sales Shipment Header”, Table 120 “Purch. Rcpt. Header”, Table 6650 “Return Shipment Header” (if (“Source Type” = const(120)) “Purch. Rcpt. Header” where(“No.” = field(“Source No.”)) else if (“Source Type” = const(110)) “Sales Shipment Header” where(“No.” = field(“Source No.”)) else if (“Source Type” = const(6650)) “Return Shipment Header” where(“No.” = field(“Source No.”)) else if (“Source …)
7307 Source Document Enum “Warehouse Activity Source Document” — enum Enum 5768 “Warehouse Activity Source Document”
7308 Source Type Integer —
7309 Source Subtype Option — OptionCaption: 0,1,2,3,4,5,6,7,8,9,10; not editable
7310 Destination Type enum “Warehouse Destination Type” — enum Enum 7310 “Warehouse Destination Type”
7311 Destination No. Δ BC26 Δ BC28 Code[20] Specifies the number or the code of the customer, vendor, location, item, family, or sales order linked to the posted inventory put-away. TableRelation Table 14 “Location”, Table 18 “Customer”, Table 23 “Vendor” (if (“Destination Type” = const(Vendor)) Vendor else if (“Destination Type” = const(Customer)) Customer else if (“Destination Type” = const(Location)) Location else if (“Destination Type” = const(Item)) Item else if (“Destination Type” = const(“Sales Order”)) “Sales Header”.“No.” where(“Document Type…)
7312 External Document No. Δ BC28 Code[35] Specifies a document number that refers to the customer’s or vendor’s numbering system.
7313 Expected Receipt Date Δ BC28 Date Specifies the date on which the receipt of the items on the posted inventory put-away was expected.
7315 External Document No.2 Δ BC28 Code[35] Specifies an additional part of the document number that refers to the customer’s or vendor’s numbering system.

Keys

  • Key1: No. (clustered)
  • Key2: Invt. Put-away No.
  • Key3: Location Code
  • Key4: Posting Date

Procedures

  • Navigate()

Plus 3 local procedures.

Triggers

OnDelete, OnInsert

Relations

Pages and codeunits on this table

Extended by

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.

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

Evidence 1 sources