FUNSTKACC

SOLVED

Hi all 

Could you help meATRACE (2).pdf with the problem  faced while we run FUNSTKACC (Account. Interface), the system is not able to create a journal but updated stock qty and cost.
The error attached herewith.
Best Regards,
Shemsu Heiru
  • 0

    Hi Shemsu

    The FUNSTKACC does not update stock qty & costs - this is done by the stock transactions. 

    If you can go into X3 Stock> Inquiries>Movements> Transactions & search for one of the affected transactions, you can use the log to get the transaction. Enter the Site, Product & identify the transaction, check if there is a value on the account document field. If there is a value then a journal was already created & posted. 

    You can also run SQL query basing it on the table STOJOU, for the Site, product  where VCRNUM is your stock transaction. Check if there a value on the ENTCODE field.

  • 0 in reply to AndrewV

    Hi Andrew,

    I have checked the STOJOU there is a value at ENTCODE, on the transaction movement of the item also, it shows the delivery return both in qty and cost, but  on the action button of movement menu, doesn't show accounting document  like other transaction movements ie why I suspect the journal did not created.

    Please help me on how can I remove delivery return transaction that stops me from year end closing

    Thank you for your response. 

  • 0 in reply to Afrosage

    I think this requires more data investigation. Is it possible to log this with your local support? 

    Why would the delivery return block yearend?

  • 0 in reply to AndrewV

    Hi Andrew

    The year end is not yet run, but the FUNSTKACC and CLOPPER generate the error, I thought the closings not run unless clopper is free of error.

    Is there any possible risk if I delete row of delivery return transactions table and STOJOU from SQL DB as the transaction not create journal entry?

  • +1 in reply to Afrosage
    verified answer

    Hi Andrew,

    The problem solved by deleting the transaction using Development, Utilities, Maintenance, In lines (GMAINT)

    Thank you so much for your response.