tableWarehouseofficial - Microsoftderived - from the source, no model text

Table 5765 "Warehouse Request"

Base Application · Microsoft.Warehouse.Request

Across versions

  1. BC23present
  2. BC241 fields changed
  3. BC25unchanged
  4. BC262 procedures added, 2 events removed
  5. BC27unchanged
  6. BC2812 fields changed
  7. BC292 procedures removed, 1 events removed
  8. BC30unchanged

Neighbourhood 17 connected objects and pages

Table 14 "Location" (relates to, 2 links)LocationTable 36 "Sales Header" (relates to, 2 links)Sales HeaderTable 10 "Shipment Method" (relates to)Table 18 "Customer" (relates to)CustomerTable 23 "Vendor" (relates to)VendorTable 27 "Item" (relates to)ItemTable 291 "Shipping Agent" (relates to)Shipping AgentTable 5767 "Warehouse Activity Line" (relates to)Table 5790 "Shipping Agent Services" (relates to)Shipping Agent ServicesPage 5793 "Source Documents" (pages and codeunits on it, 2 links)Source DocumentsTable extension 903 "Asm. Warehouse Request" (extended by)Asm. Warehouse RequestTable extension 99000780 "Mfg. Warehouse Request" (extended by)Mfg. Warehouse RequestCodeunit 5991 "Sales Warehouse Mgt." (event subscribers)Sales Warehouse Mgt.Codeunit 5992 "Purchases Warehouse Mgt." (event subscribers)Purchases Warehouse Mgt.Codeunit 5993 "Transfer Warehouse Mgt." (event subscribers)Transfer Warehouse Mgt.Codeunit 5995 "Service Warehouse Mgt." (event subscribers)Service Warehouse Mgt.Codeunit 5996 "Prod. Order Warehouse Mgt." (event subscribers)

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.Request · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Warehouse Request
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 Source Type Integer — not editable
2 Source Subtype Option — OptionCaption: 0,1,2,3,4,5,6,7,8,9,10; not editable
3 Source No. Δ BC28 Code[20] Specifies the number of the source document that the entry originates from. TableRelation Table 36 “Sales Header” (if (“Source Document” = const(“Sales Order”)) “Sales Header”.“No.” where(“Document Type” = const(Order), “No.” = field(“Source No.”)) else if (“Source Document” = const(“Sales Return Order”)) “Sales Header”.“No.” where(“Document Type” = const(“Return Order”), “No.” = field(“Source No.”)) else if (“S…); not editable
4 Source Document Δ BC28 Enum “Warehouse Request Source Document” Specifies the type of document that the line relates to. enum Enum 5770 “Warehouse Request Source Document”; not editable
5 Document Status Option — OptionCaption: Open,Released; not editable
6 Location Code Δ BC28 Code[10] Specifies the location code to which the request line is linked. TableRelation Table 14 “Location”; not editable
7 Shipment Method Code Δ BC28 Code[10] Specifies the delivery conditions of the related shipment, such as free on board (FOB). TableRelation Table 10 “Shipment Method” (Shipment Method); not editable
8 Shipping Agent Code Δ BC28 Code[10] Specifies the code for the shipping agent who is transporting the items. TableRelation Table 291 “Shipping Agent” (Shipping Agent); not editable
9 Shipping Agent Service Code Code[10] — TableRelation Table 5790 “Shipping Agent Services” (Shipping Agent Services); not editable
10 Shipping Advice Δ BC28 Enum “Sales Header Shipping Advice” Specifies the shipping advice, which informs whether partial deliveries are acceptable. enum Enum 3657 “Sales Header Shipping Advice”; not editable
11 Destination Type Δ BC28 enum “Warehouse Destination Type” Specifies whether the type of destination associated with the warehouse request is a customer or a vendor. enum Enum 7310 “Warehouse Destination Type”
12 Destination No. Δ BC26 Δ BC28 Code[20] Specifies the number or code of the customer or vendor related to the warehouse request. 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…)
13 External Document No. Δ BC28 Code[35] Specifies a document number that refers to the customer’s or vendor’s numbering system.
14 Expected Receipt Date Δ BC28 Date Specifies the date when receipt of the items is expected.
15 Shipment Date Δ BC28 Date Specifies when items on the document are shipped or were shipped. A shipment date is usually calculated from a requested delivery date plus lead time.
19 Type Enum “Warehouse Request Type” — enum Enum 5771 “Warehouse Request Type”; not editable
20 Put-away / Pick No. Δ BC24 Δ BC28 Code[20] Specifies the number of the inventory put-away or pick that was created from this warehouse request. FlowField: lookup(“Warehouse Activity Line”.“No.” where(“Source Type” = field(“Source Type”), “Source Subtype” = field(“Source Subtype”), “Source No.” = field(“Source No.”), “Location Code” = field(“Location Code”))); not editable
41 Completely Handled Boolean —

Keys

  • Key1: Type, Location Code, Source Type, Source Subtype, Source No. (clustered)
  • Key2: Source Type, Source Subtype, Source No.
  • Key3: Source Type, Source No.
  • Key4: Source Document, Source No.
  • Key5: Type, Location Code, Completely Handled, Document Status, Expected Receipt Date, Shipment Date, Source Document, Source No.
  • Key6: Source No., Source Subtype, Source Type, Type, Document Status

Events published

Procedures

  • DeleteRequest(SourceType: Integer; SourceSubtype: Integer; SourceNo: Code[20])
  • SetSourceFilter(SourceType: Integer; SourceSubtype: Integer; SourceNo: Code[20])
  • ShowSourceDocumentCard()

Relations

Pages and codeunits on this table

Extended by

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: "Warehouse Request"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources