Skip to main content

Flow Custom field to G/L Entry and other Posted tables : From Purchase Order to Posted Purchase invoice

Hi Readers,

In this blog we will see how we can transfer data from "Purchase Header" to "Purchase Invoice Header" & "G/L Entry" table in Business Central.

In this example, will create "Remarks" field on Purchase Header table and after posting, flow it to Purchase Invoice Header & G/L Entry tables:

Firsly, create required fields ("Remarks") in below mentioned tables by creating table extensions:

  • Purchase Header (38)
  • Purch. Inv. Header (122)
  • Gen. Journal Line (81) 
  • G/L Entry (17)
For the Purch. Inv. Header table, you can just create copy the field from purchase header and paste it in Purch. Inv. Header table. If the field ID No. is same for that field for both the tables then you don't have to code i.e, it automatically transfer that field data from Purch. Header to Purch. Inv. Header.

Step-(1) 
tableextension 50104 "Purchase Header Ext" extends "Purchase Header"
{
    fields
    {
        field(50000; "Remarks"; Text[100])
        {
            DataClassification = ToBeClassified;
        }
    }
}

Step-(2)
tableextension 50103 "Purchase Inv Header Ext" extends "Purch. Inv. Header"
{
    fields
    {
        field(50000; Remarks; Text[100])
        {
            DataClassification = ToBeClassified;
        }
    }
}

Step-(3)
tableextension 50102 "Gen. Journal Line Exn" extends "Gen. Journal Line"
{
    fields
    {
        field(50000; "Remarks"; Text[100])
        {
            DataClassification = ToBeClassified;
        }
    }
}

Step-(4)
tableextension 50105 "General Ledger Entry Ext" extends "G/L Entry"
{
    fields
    {
        field(50000; Remarks; Text[100])
        {
            DataClassification = ToBeClassified;
        }
    }
}

Step-(5) Now for flowing "Remarks" fields data to G/L Entry, we have to first transfer that field data to  Gen. Journal Line table based on required condition by using Event subscriber in Table Gen. Journal Line (81)  .
Then from that we can transfer it to G/L Entry. By using other Event Subscriber mentioned in CodeUnit "Gen. Jnl.-Post Line" - (12).

codeunit 50100 "Event Subscriber BackOffice"
{
    trigger OnRun()
    begin
    end;

    [EventSubscriber(ObjectType::Table, DataBase::"Gen. Journal Line", 
    'OnAfterCopyGenJnlLineFromPurchHeader', '', false, false)]
    Procedure OnAfterCopyGenJnlLineFromPurchHeader(PurchaseHeader: 
    Record "Purchase Header"; Var GenJournalLine: Record "Gen. Journal Line")
    begin
        GenJournalLine.Remarks := PurchaseHeader.Remarks;
    end;

    [EventSubscriber(ObjectType::Codeunit, Codeunit::"Gen. Jnl.-Post Line", 
    'OnAfterInitGLEntry', '', false, false)]
    Procedure OnAfterInitGLEntry(var GLEntry: Record "G/L Entry"; GenJournalLine: 
    Record "Gen. Journal Line")
    begin
        GLEntry.Remarks := GenJournalLine.Remarks;
    end;
}

Step-(6) Now add that field on Pages to Check wheather it's flowing or not:
  • Purchase Order (50)
pageextension 50103 "Purchase Order Ext" extends "Purchase Order"
{
    layout
    {
        addlast(General)
        {
            field(Remarks; Remarks)
            {
                ApplicationArea = All;
            }
        }
    }
}
  • Posted Purchase Invoice (138)
pageextension 50104 "Purchase Invoice Ext" extends "Posted Purchase Invoice"
{
    layout
    {
        addlast(General)
        {
            field(Remarks; Remarks)
            {
                ApplicationArea = All;
            }
        }
    }
}
  • General Ledger Entries (20)
pageextension 50105 "GL Entry Ext" extends "General Ledger Entries"
{
    layout
    {
        addafter(Description)
        {
            field(Remarks; Remarks)
            {
                ApplicationArea = All;
            }
        }
    }
}

Output-


I hope it helps!! Thanks for Reading!!!

Your valuable comment & feedback is Highly appreciated.

Labels:

Comments

  1. Anonymous9 February 2024 at 15:23

    Hello Kunal
    From Purchase Line to G/L Entry
    How Suggestion

    ReplyDelete

Post a Comment

Popular posts from this blog

Amount In Words in Navision / Business Central

Hi Guys, In this article, we will see how to display amount in words in Microsoft Dynamics Business Central. Here, I am taking an example of Report object  which is widely used in Navision for converting decimal amount field into words. Procedure :-  Step-1 Declare the following Global Variables :         RepCheck:  Report  "Check";         NoText:  array [ 2 ]  of   Text ;         AmountInWords:  Text ; where, (1) RepCheck is a variable of  Report DataType Named as " Check " which is 1401. (2) NoText is a variable of DataType " Text " with array Dimension value as 2 which is defined as shown above. (3) AmountInWords is a variable of DataType " Text " which will store final result of amount in words. Step-2 Now, add the following code in OnAfterGetRecord() trigger of DataItem containing that decimal field value. So in my custom Purchase Order Report, i am adding code in the Purchase Header (DataItem) - OnAfterGetRecord() trigger.   trigger  OnA
7 comments
Read more

Calculate Date : Using Date Formula and CalcDate Function in Navision/BC

 Hi Everyone, In this article we will see how we can Calculate Date by adding and subtracting No. of Days / Months based on CalcDate and DateFormula datatype. Here, I define three variables required for: (1) " No of Days " -  To define No. of Days / Months as required. You can also use these units denoted as: <Unit> = D | WD | W | M | Q | Y (D=day, WD=weekday, W=week, M=month, Q=quarter, Y=year). (2) " From Date " and " To Date "  Date type Variables to store calculated date in it. page   50103  "Date from Date Formula" {     PageType = Card;     ApplicationArea = All;     UsageCategory = Administration;     SourceTable =  Integer ;      layout     {          area( Content )         {              group( General )             {                  field( "No. of Days"; "No. of Days" )                 {                     ApplicationArea = All;                 }             }         }     }      actions     {          area
Post a Comment
Read more