Page 6561 "Invt. Receipt"

Base Application · Microsoft.Inventory.Document · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property	Value
Caption	Invt. Receipt
SourceTable	Invt. Document Header
PageType	Document

Fields on this page

Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).

Group	Control	Shows	ToolTip
General	No.	No.	Specifies the number of the involved entry or record, according to the specified number series. from the table field
	Posting Description	Posting Description	Specifies any text that is entered to accompany the posting, for example for information to auditors. from the table field
	Location Code	Location Code	Specifies the warehouse or other place where the involved items are handled or stored. from the table field
	Gen. Bus. Posting Group	Gen. Bus. Posting Group	Specifies the vendor’s or customer’s trade type to link transactions made for this business partner with the appropriate general ledger account according to the general posting setup. from the table field
	Posting Date	Posting Date	Specifies the entry’s posting date. from the table field
	Document Date	Document Date	Specifies the date when the related document was created. from the table field
	External Document No.	External Document No.	Specifies a document number that refers to the customer’s or vendor’s numbering system. from the table field
	Salesperson/Purchaser Code	Salesperson/Purchaser Code	Specifies the employee purchaser code or salesperson code associated with this document. from the table field
	Correction	Correction	Specifies the entry as a corrective entry. You can use the field if you need to post a corrective entry to an account. from the table field
	Status	Status	Specifies the status of the item document. from the table field
Content	ReceiptLines	part Page 6562 “Invt. Receipt Subform”	—
Dimensions	Shortcut Dimension 1 Code	Shortcut Dimension 1 Code	Specifies the code for Shortcut Dimension 1, which is one of two global dimension codes that you set up in the General Ledger Setup window. from the table field
	Shortcut Dimension 2 Code	Shortcut Dimension 2 Code	Specifies the code for Shortcut Dimension 2, which is one of two global dimension codes that you set up in the General Ledger Setup window. from the table field

Actions

Group	Action	ToolTip	Runs
Receipt	Statistics	View statistical information, such as the value of posted entries, for the record.	Page 6776 “Invt. Document Statistics”
	Comments	View or edit comments.	Page 5750 “Inventory Comment Sheet”
	Dimensions	View or edit dimensions, such as area, project, or department.
Functions	Copy Document…	Copy document.
	Release	Enable the record for the next stage of processing.
	Reopen	Open the closed or released record.
Posting	Post	Record the related transaction in your books.
	Preview Posting	Review the different types of entries that will be created when you post the document or journal.
	Post and Print	Finalize and prepare to print the document or journal. The values and quantities are posted to the related accounts. A report request window where you can specify what to include on the print-out.
Processing	Print	Print document.

Procedures

4 local procedures, no public ones.

Relations

source table Table 5850 “Invt. Document Header”

Pages and codeunits on this table

Page 6563 “Invt. Receipts” (card page)
Page 6775 “Invt. Document List” (card page)

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 5853 “Invt. Doc.-Post (Yes/No)” (1 call: ShowPreview → Preview)

Called by

Codeunit 5854 “Invt. Doc. Line-Reserve” (1 call: OnLookupDocument → (object))

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: "page", object_name: "Invt. Receipt"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Across versions

Neighbourhood 5 connected objects and pages