Page 2584 "Dim Correct Posted Ledg Entr"
Base Application · Microsoft.Finance.Dimension.Correction
Across versions
- BC23-30present
Neighbourhood 3 connected objects and pages
Base Application · Microsoft.Finance.Dimension.Correction · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| SourceTable | G/L Entry |
| PageType | ListPart |
Fields on this page
Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).
| Group | Control | Shows | ToolTip |
|---|---|---|---|
| Control1 | Entry No. | Entry No. | Specifies the identifier for the entry. The number series for entries assigned the identifier. |
| Posting Date | Posting Date | Specifies the entry’s posting date. from the table field | |
| Document Type | Document Type | Specifies the Document Type that the entry belongs to. from the table field | |
| Document No. | Document No. | Specifies the entry’s Document No. from the table field | |
| G/L Account No. | G/L Account No. | Specifies the number of the account that the entry has been posted to. from the table field | |
| G/L Account Name | G/L Account Name | Specifies the name of the account that the entry has been posted to. from the table field | |
| Description | Description | Specifies a description of the entry. from the table field | |
| Job No. | Job No. | Specifies the number of the related project. from the table field | |
| Global Dimension 1 Code | Global Dimension 1 Code | Specifies the code for the global dimension that is linked to the record or entry for analysis purposes. Two global dimensions, typically for the company’s most important activities, are available on all cards, documents, reports, and lists. from the table field | |
| Global Dimension 2 Code | Global Dimension 2 Code | Specifies the code for the global dimension that is linked to the record or entry for analysis purposes. Two global dimensions, typically for the company’s most important activities, are available on all cards, documents, reports, and lists. from the table field | |
| IC Partner Code | IC Partner Code | Specifies the code of the intercompany partner that the transaction is related to if the entry was created from an intercompany transaction. from the table field | |
| Gen. Posting Type | Gen. Posting Type | Specifies the type of transaction. from the table field | |
| Gen. Bus. Posting Group | Gen. Bus. Posting Group | Specifies the vendor’s or customer’s trade type to link transactions made for this business partner with the appropriate ledger account according to the general posting setup. | |
| Gen. Prod. Posting Group | Gen. Prod. Posting Group | Specifies the item’s product type to link transactions made for this item with the appropriate ledger account according to the general posting setup. | |
| Quantity | Quantity | Specifies the quantity that was posted on the entry. from the table field | |
| Additional-Currency Amount | Additional-Currency Amount | Specifies the ledger entry that is posted if you post in an additional reporting currency. | |
| VAT Amount | VAT Amount | Specifies the amount of VAT that is included in the total amount. from the table field | |
| Bal. Account Type | Bal. Account Type | Specifies the type of account that a balancing entry is posted to, such as BANK for a cash account. from the table field | |
| Bal. Account No. | Bal. Account No. | Specifies the number of the ledger, customer, vendor, or bank account that the balancing entry is posted to, such as a cash account for cash purchases. | |
| User ID | User ID | Specifies the ID of the user who posted the entry, to be used, for example, in the change log. from the table field | |
| Source Code | Source Code | Specifies the source code that specifies where the entry was created. from the table field | |
| Reason Code | Reason Code | Specifies the reason code, a supplementary source code that enables you to trace the entry. from the table field | |
| Reversed | Reversed | Specifies if the entry has been part of a reverse transaction (correction) made by the Reverse function. from the table field | |
| Reversed by Entry No. | Reversed by Entry No. | Specifies the number of the correcting entry. If the field Specifies a number, the entry cannot be reversed again. from the table field | |
| Reversed Entry No. | Reversed Entry No. | Specifies the number of the original entry that was undone by the reverse transaction. from the table field | |
| FA Entry Type | FA Entry Type | Specifies the number of the fixed asset entry. from the table field | |
| FA Entry No. | FA Entry No. | Specifies the number of the fixed asset entry. from the table field | |
| Dimension Set ID | Dimension Set ID | Specifies a reference to a combination of dimension values. The actual values are stored in the Dimension Set Entry table. from the table field | |
| External Document No. | External Document No. | Specifies the entry’s external document number, such as a vendor’s invoice number. from the table field |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Processing | Show Selection Criteria | View the filter criteria that was used to select the entries to correct. |
Procedures
SetDimensionCorrectionEntryNo(NewDimensionCorrectionEntryNo: Integer): Sets the dimension correction entry number for displaying posted G/L entries with corrected dimensions.
Plus 2 local procedures.
Triggers
OnFindRecord
Relations
- source table Table 17 “G/L Entry”
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 2580 “Dimension Correction Mgt” (2 calls:
LoadRecords → GetFilterConditionsLimit,LoadRecords → GetPreviewGLEntriesLimit)
Documented on Microsoft Learn
Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).
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: "page", object_name: "Dim Correct Posted Ledg Entr"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.