BC Observatoryunofficial, made by waldo
tableextensionFinanceofficial - Microsoftderived - from the source, no model text

Table extension 1694 "SalesReceivablesSetupExtension"

BankDeposits · Microsoft.Bank.Deposit

Open in Claude1694.mdSource on GitHub

Across versions

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

Neighbourhood 1 connected objects and pages

Table 311 "Sales & Receivables Setup" (relates to)Sales & Receivables Setup

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.

BankDeposits · Microsoft.Bank.Deposit · BC29-30 · source at ea08af5e · facts from BC29

Extends Sales & Receivables Setup.

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
1690 Bank Deposit Nos. Code[20] Specifies the code for the number series that will be used to assign numbers to bank deposits. via Page extension 1700 “SalesReceivablesSetupExt” TableRelation No. Series; DataClassification SystemMetadata
1691 Post Bank Deposits as Lump Sum Boolean Specifies if bank deposits should be posted as a single bank account ledger entry with the total amount. You can change this setting on the bank deposit card. via Page extension 1700 “SalesReceivablesSetupExt” DataClassification SystemMetadata

Relations

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

Evidence 1 sources