Table 443 "IC Setup"
Base Application · Microsoft.Intercompany.Setup
Across versions
- BC23present
- BC24declaration changed
- BC25unchanged
- BC261 fields changed
- BC27-28unchanged
- BC291 fields added
- BC30unchanged
Neighbourhood 8 connected objects and pages
Base Application · Microsoft.Intercompany.Setup · BC23-30 · source at ea08af5e · facts from BC29
Learn documents this table through its pages: Page 653 “Intercompany Setup” (1 Learn page).
Properties
| Property | Value |
|---|---|
| Caption | IC Setup |
| 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 | Primary Key Δ BC26 | Code[10] | — | |
| 2 | IC Partner Code | Code[20] | Specifies your company’s intercompany partner code. via Page 653 “Intercompany Setup” | |
| 3 | IC Inbox Type | Option | Specifies what type of intercompany inbox you have, either File Location or Database. via Page 653 “Intercompany Setup” | OptionCaption: File Location,Database |
| 4 | IC Inbox Details | Text[250] | Specifies details about the location of your intercompany inbox, which can transfer intercompany transactions into your company. via Page 653 “Intercompany Setup” | |
| 5 | Auto. Send Transactions | Boolean | Specifies that as soon as transactions arrive in the intercompany outbox, they will be sent to the intercompany partner. via Page 653 “Intercompany Setup” | |
| 6 | Default IC Gen. Jnl. Template | Code[10] | Specifies the journal template name that will be used to create journal lines as soon as transactions arrive in the intercompany inbox. via Page 653 “Intercompany Setup” | TableRelation Table 80 “Gen. Journal Template” (Gen. Journal Template) |
| 7 | Default IC Gen. Jnl. Batch | Code[10] | Specifies the journal batch that will be used to create journal lines as soon as transactions arrive in the intercompany inbox. via Page 653 “Intercompany Setup” | TableRelation Table 232 “Gen. Journal Batch” (“Gen. Journal Batch”.Name where(“Journal Template Name” = field(“Default IC Gen. Jnl. Template”))) |
| 8 | Partner Code for Acc. Syn. | Code[20] | Specifies the partner you want to synchronise with. The selected partner will be used during the synchronisation of your Intercompany Chart of Account and Intercompany Dimensions. via Page 653 “Intercompany Setup” | TableRelation Table 413 “IC Partner” (“IC Partner”.Code where(“Inbox Type” = filter(“IC Partner Inbox Type”::Database))) |
| 9 | Transaction Notifications | Boolean | Specifies whether the system should send you notifications when a new transaction is sent to the intercompany outbox. via Page 653 “Intercompany Setup” | |
| 10 | Log API Requests + BC29 | Boolean | Specifies whether to log outgoing and incoming intercompany API requests for troubleshooting. via Page 653 “Intercompany Setup” | DataClassification SystemMetadata |
Keys
- Key1: Primary Key (clustered)
Relations
- Default IC Gen. Jnl. Batch: TableRelation Table 232 “Gen. Journal Batch”
- Partner Code for Acc. Syn.: TableRelation Table 413 “IC Partner”
- Default IC Gen. Jnl. Template: TableRelation Table 80 “Gen. Journal Template”
Pages and codeunits on this table
- Page 30414 “API - IC Setup” (source table)
- Page 629 “IC Chart of Accounts Setup” (source table)
- Page 653 “Intercompany Setup” (source table)
- Page 678 “IC Dimensions Setup” (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: "IC Setup"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.