Table 611 "Buffer IC InOut Jnl. Line Dim."
Base Application · Microsoft.Intercompany.DataExchange
Across versions
- BC23-30present
Neighbourhood 1 connected objects and pages
Base Application · Microsoft.Intercompany.DataExchange · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| 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 | Table ID | Integer | — | |
| 2 | IC Partner Code | Code[20] | — | |
| 3 | Transaction No. | Integer | — | |
| 4 | Line No. | Integer | — | |
| 5 | Dimension Code | Code[20] | — | |
| 6 | Dimension Value Code | Code[20] | — | |
| 7 | Transaction Source | Option | — | OptionCaption: Rejected,Created |
| 8100 | Operation ID | Guid | — | not editable |
Keys
- Key1: Table ID, Transaction No., IC Partner Code, Transaction Source, Line No., Dimension Code (clustered)
Pages and codeunits on this table
- Page 30424 “API Buf IC InOut Jnl Line Dim” (source table)
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: "Buffer IC InOut Jnl. Line Dim."), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.