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

Table 6116 "E-Doc. PO Matching Setup"

EDocument · Microsoft.eServices.EDocument.Processing.Import.Purchase

Across versions

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

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 Id Integer — AutoIncrement; DataClassification SystemMetadata
2 PO Matching Config. Receipt Enum “E-Doc. PO M. Config. Receipt” — enum Enum 6112 “E-Doc. PO M. Config. Receipt”; DataClassification CustomerContent
3 Vendor No. Code[20] — TableRelation Vendor.“No.”; DataClassification CustomerContent
4 Receive G/L Account Lines Boolean — DataClassification CustomerContent

Keys

  • PK: Id (clustered)

Procedures

  • GetSetup(VendorNo: Code[20]): Sets the current record to the setup applicable to the provided vendor
  • GetSetup(): Sets the current record to the setup applicable if there is no specific override

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

Evidence 1 sources