Table 6114 "E-Doc. Purchase Line PO Match"

EDocument · Microsoft.eServices.EDocument.Processing.Import.Purchase · BC29-30 · source at ea08af5e · facts from BC29

Properties

Property	Value
Access	Internal

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	E-Doc. Purchase Line SystemId	Guid	—	TableRelation Table 6101 “E-Document Purchase Line” (“E-Document Purchase Line”.SystemId); not editable; DataClassification SystemMetadata
2	Purchase Line SystemId	Guid	—	TableRelation Table 39 “Purchase Line” (“Purchase Line”.SystemId); not editable; DataClassification SystemMetadata
3	Receipt Line SystemId	Guid	—	TableRelation Table 121 “Purch. Rcpt. Line” (“Purch. Rcpt. Line”.SystemId); not editable; DataClassification SystemMetadata

Keys

Key1: E-Doc. Purchase Line SystemId, Purchase Line SystemId, Receipt Line SystemId (clustered)

Relations

Receipt Line SystemId: TableRelation Table 121 “Purch. Rcpt. Line”
Purchase Line SystemId: TableRelation Table 39 “Purchase Line”
E-Doc. Purchase Line SystemId: TableRelation Table 6101 “E-Document Purchase Line”

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: "E-Doc. Purchase Line PO Match"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.