Table 436 "IC Inbox Purchase Header"
Base Application · Microsoft.Intercompany.Inbox
Across versions
- BC23present
- BC24declaration changed
- BC251 fields added
- BC26-27unchanged
- BC281 fields changed
- BC29-30unchanged
Neighbourhood 7 connected objects and pages
Base Application · Microsoft.Intercompany.Inbox · BC23-30 · source at ea08af5e · facts from BC29
Learn documents this table through its pages: Page 646 “IC Inbox Purchase Doc.” (1 Learn page).
Properties
| Property | Value |
|---|---|
| Caption | IC Inbox Purchase Header |
| 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 | Document Type | Enum “IC Purchase Document Type” | Specifies the type of the related document. via Page 646 “IC Inbox Purchase Doc.” | enum Enum 436 “IC Purchase Document Type”; not editable |
| 2 | Buy-from Vendor No. | Code[20] | Specifies the name of the vendor who delivered the items. via Page 646 “IC Inbox Purchase Doc.” | TableRelation Table 23 “Vendor”; not editable |
| 3 | No. | Code[20] | Specifies the number of the involved entry or record, according to the specified number series. via Page 646 “IC Inbox Purchase Doc.” | not editable |
| 4 | Pay-to Vendor No. | Code[20] | Specifies the number of the vendor that you received the invoice from. via Page 646 “IC Inbox Purchase Doc.” | TableRelation Table 23 “Vendor”; not editable |
| 11 | Your Reference | Text[35] | — | |
| 13 | Ship-to Name | Text[100] | Specifies the name of the customer at the address that the items are shipped to. via Page 646 “IC Inbox Purchase Doc.” | not editable |
| 15 | Ship-to Address | Text[100] | Specifies the address that the items are shipped to. via Page 646 “IC Inbox Purchase Doc.” | not editable |
| 16 | Ship-to Address 2 | Text[50] | — | not editable |
| 17 | Ship-to City | Text[30] | Specifies the city of the address that the items are shipped to. via Page 646 “IC Inbox Purchase Doc.” | not editable |
| 20 | Posting Date | Date | Specifies the entry’s posting date. via Page 646 “IC Inbox Purchase Doc.” | |
| 21 | Expected Receipt Date | Date | — | not editable |
| 24 | Due Date | Date | Specifies when the related invoice must be paid. via Page 646 “IC Inbox Purchase Doc.” | |
| 25 | Payment Discount % Δ BC28 | Decimal | Specifies the payment discount percentage that is granted if you pay on or before the date entered in the Pmt. Discount Date field. The discount percentage is specified in the Payment Terms Code field. via Page 646 “IC Inbox Purchase Doc.” | not editable |
| 26 | Pmt. Discount Date | Date | Specifies the date on which the amount in the entry must be paid for a payment discount to be granted. via Page 646 “IC Inbox Purchase Doc.” | not editable |
| 32 | Currency Code | Code[10] | Specifies the currency that is used on the entry. via Page 646 “IC Inbox Purchase Doc.” | TableRelation Table 4 “Currency”; not editable |
| 35 | Prices Including VAT | Boolean | — | |
| 66 | Vendor Order No. | Code[35] | — | |
| 68 | Vendor Invoice No. | Code[35] | — | not editable |
| 69 | Vendor Cr. Memo No. | Code[35] | — | not editable |
| 72 | Sell-to Customer No. | Code[20] | — | not editable |
| 91 | Ship-to Post Code | Code[20] | — | not editable |
| 92 | Ship-to County | Text[30] | — | |
| 93 | Ship-to Country/Region Code | Code[10] | — | TableRelation Table 9 “Country/Region” (Country/Region) |
| 99 | Document Date | Date | Specifies the date when the related document was created. via Page 646 “IC Inbox Purchase Doc.” | |
| 125 | IC Partner Code | Code[20] | Specifies the code of the intercompany partner that the transaction is related to if the entry was created from an intercompany transaction. via Page 646 “IC Inbox Purchase Doc.” | TableRelation Table 413 “IC Partner” (IC Partner); not editable |
| 201 | IC Transaction No. | Integer | Specifies the number of the intercompany transaction. The transaction number indicates which line in the IC Outbox Transaction table the document is related to. via Page 646 “IC Inbox Purchase Doc.” | not editable |
| 202 | Transaction Source | Option | Specifies which company created the transaction. via Page 646 “IC Inbox Purchase Doc.” | OptionCaption: Returned by Partner,Created by Partner; not editable |
| 210 | Ship-to Phone No. + BC25 | Text[30] | — | |
| 5790 | Requested Receipt Date | Date | Specifies the date that you want the vendor to deliver your order. The field is used to calculate the latest date you can order, as follows: requested receipt date - lead time calculation = order date. If you do not need delivery on a specific date, you can leave the field blank. via Page 646 “IC Inbox Purchase Doc.” | not editable |
| 5791 | Promised Receipt Date | Date | — | not editable |
Keys
- Key1: IC Transaction No., IC Partner Code, Transaction Source (clustered)
Triggers
OnDelete
Relations
- Buy-from Vendor No.: TableRelation Table 23 “Vendor”
- Pay-to Vendor No.: TableRelation Table 23 “Vendor”
- Currency Code: TableRelation Table 4 “Currency”
- IC Partner Code: TableRelation Table 413 “IC Partner”
- Ship-to Country/Region Code: TableRelation Table 9 “Country/Region”
Pages and codeunits on this table
- Page 646 “IC Inbox Purchase Doc.” (source table)
Calls
From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.
- Codeunit 408 “DimensionManagement” (1 call:
OnDelete → DeleteICDocDim)
Ask your agent
Procedure bodies are not stored here (D10). The call sections above are our own, per object, from the BC29 call graph. 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 Inbox Purchase Header"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.