D365 Finance & Operations and Dynamics AX Forum

Expand all | Collapse all

AX 2009 Orphan payment journal lines

  • 1.  AX 2009 Orphan payment journal lines

    SILVER CONTRIBUTOR
    Posted 16 days ago
    We have a case where somehow the journalNum was changed and the old lines are now without a header record.  When I look at the database log it shows that the previous value was 21820 and the new value is 21842.  This field is set to not allow edits so I am not sure how it happened but we have an issue with journal lines with cheques printed but cannot be completed and transactions that are still marked.  It doesn't seem that there are any transactions on the ledger.
    If I go to open transaction editing it shows the record as marked and when I go to the specification form I see the record but there is no journal number.  If I click open journal form, nothing shows.
    I have seen weird things in the past where a number sequence from a different company gets copied over but that was at journal creation.  I have not see a record of journal num changed after creation before.  Any ideas would be helpful.

    ------------------------------
    Randy Delmore
    Business Applications Technical Architect
    Septodont Inc.
    Cambridge ON
    ------------------------------
    Conference-AXUG_200x200


  • 2.  RE: AX 2009 Orphan payment journal lines

    Posted 16 days ago
    This sounds like it could be orphans in the SPECTRANS table - see the link below for details on how to fix:

    https://support.microsoft.com/en-gb/help/894412/a-red-hand-symbol-appears-next-to-an-invoice-in-the-open-transaction-e

    ------------------------------
    Nik Lawrence
    ERP Co-ordinator
    Hill and Smith Limited
    Wolverhampton
    ------------------------------

    Conference-AXUG_200x200


  • 3.  RE: AX 2009 Orphan payment journal lines

    TOP CONTRIBUTOR
    Posted 16 days ago
    ​Changes made via sql directly on the database skip the validation checks in the AOT, and are likely how the record got changed.
    Who has SQL access to your prod db? :)

    (It can be unintentional - if they thought they were testing on a different connection)

    ------------------------------
    Tony Zeigler
    Senior Consultant
    Strategic Solutions NW, LLC
    Beaverton OR
    ------------------------------

    Conference-AXUG_200x200


  • 4.  RE: AX 2009 Orphan payment journal lines

    SILVER CONTRIBUTOR
    Posted 15 days ago
    It is true that changes made directly to sql skip the AOT validation checks, but it is also true that direct sql changes are not logged in the AX database log.  Therefore it must have been a system bug.
    SQL access to the database is limited to a very select number of admins who are trained not to run any sql code against the database.  Reading in the article that the solution from Microsoft is to delete records from the AOT is very concerning.

    ------------------------------
    Randy Delmore
    Business Applications Technical Architect
    Septodont Inc.
    Cambridge ON
    ------------------------------

    Conference-AXUG_200x200


  • 5.  RE: AX 2009 Orphan payment journal lines

    TOP CONTRIBUTOR
    Posted 14 days ago
    Edited by Mark Prouty 14 days ago
    This is disconcerting. You may need to spend some time on how this happened. An AOT job that used a doUpdate() instead of update()?

    It sounds like the journal id was changed​ on the journal table but not journal lines. If the journal Ids are distinct, you should be able to right click on the journal table record 21842 and choose Record Info, then Rename. Rename to 21820. The orphans should "magically" show up.

    Was a table relationship changed? Is the journalId number sequence pre-allocated? Sequential?
    I've seen very peculiar things (including record deletion) when client application version != kernel version in AX 2009.

    ------------------------------
    Mark Prouty
    Programmer / Analyst
    ANGI Energy Systems
    Janesville WI
    ------------------------------

    Conference-AXUG_200x200


If you've found this thread useful, dive deeper into User Group community content by role