tableIntegration & APIsofficial - Microsoftderived - from the source, no model text

Table 6140 "E-Doc. Purchase Line History"

EDocument · Microsoft.EServices.EDocument.Processing.Import.Purchase

Across versions

  1. BC23-28not present
  2. BC29-30present

Neighbourhood 4 connected objects and pages

Table 123 "Purch. Inv. Line" (relates to)Purch. Inv. LineTable 23 "Vendor" (relates to)VendorTable 6101 "E-Document Purchase Line" (referenced by)E-Document Purchase LineTable 6105 "E-Document Line Mapping" (referenced by)E-Document Line Mapping

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.

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

Properties

Property Value
Caption E-Doc. Purchase Line History
Access Internal
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 Entry No. Integer — not editable; AutoIncrement; DataClassification SystemMetadata
2 Vendor No. Code[20] Specifies the vendor number. TableRelation Table 23 “Vendor”
3 Product Code Text[100] Specifies the product code. not editable
4 Description Text[100] Specifies the description. not editable
20 Purch. Inv. Line SystemId Guid Purchase Inv. Line SystemId caption TableRelation Table 123 “Purch. Inv. Line” (“Purch. Inv. Line”.SystemId); not editable; DataClassification SystemMetadata

Keys

  • PK: Entry No. (clustered)
  • K1: Vendor No., Product Code, Description
  • K2: Product Code, Description
  • K3: Vendor No., Product Code
  • K4: Vendor No., Description

Relations

Referenced by

2 fields in 2 objects relate to this table (TableRelation or CalcFormula).

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

Evidence 1 sources