Variable Non-existent when running Stock Accounting Interface,Stock Periodic Processing Valuation

SUGGESTED

Variable Non-existent when running Stock Accounting Interface,Stock Periodic Processing Valuation

V12 Patch Level 27

When using Sigma on the Stock Accounting Interface, Stock->Periodic processing->Valuation

Error 1
Class non-existent (Variable Non-existent).

Error 2
CURAFF:Variable Non-existent

Error 3
F:GDE: Class Non- existence

Detailed steps to replicate error :
Run Stock Accounting Interface using Sigma.

Similar error on V12 Patch Level 29

When running the Stock accounting interface, Stock->Periodic processing->Valuation

"Error 6 :variable non existent CAL1"


Resolution Steps Attempted for both issues :

Validations of the screens, adding fields to screen and window and table validation
.

  • 0
    SUGGESTED

    Hi Tebogo,

    I just tried to replicate the issue in V12 P29 with sigma GTEST active and did not get the same error, I can not see if anyone has reported this issue. It will be best if you log it with your Sage support provider so it can be investigated fully. Are you able to log it to your support provider?

    Kind Regards

    Vish

  • 0 in reply to Vish Singh

    Hi Vish

    Thanks for the reply, I have tested the same on my side on Patch 29 & could not replicate. I was hoping there is anyone who might have an idea on what causes this issue on the client's environment as I have 2 clients who logged  similar issue on Patch 29 & one on Patch 27 but seems to be data related.

  • 0 in reply to Tebogo
    SUGGESTED

    Hi Tebogo,

    Yes, some of these jenkinsslave messages are environment related but can be investigated, if this issue continues please log it with your Sage Support team, such cases are being investigated case by case bases as they all are unique, it will require a debug log file from your customer's environment and Sage R&D can investigate further.

    Kind Regards

    Vish

  • 0 in reply to Vish Singh

    Thanks for your guidance Vish.

  • 0

    I have this issue for a Sage X3 v12p31 client coming from Sage X3 pu9.

    ```

    Repeat indefinitely, creating new empty newline records in the process:

    CURAFF : Variable Non-existent

    [F:GDE] : Class Non-existent

    STA : Variable Non-existent

    d:\jenkinsslave\workspace\runtime_release_release_r094.001\src\variable.c.2114. : Class Non-existent (Variable Non-existent)

    d:\jenkinsslave\workspace\runtime_release_release_r094.001\src\variable.c.2114. : Class Non-existent (Variable Non-existent)

    ```

    I need to restart server due to it keep creating multiple entries of empty lines.

    Would like to know if anyone have resolution for this.

  • 0 in reply to chunheng

    Hi  

    Please log this with your Sage Support team. As noted in the previous responses, issues of this nature are unique and require thorough investigation.

    Kind regards,

  • 0 in reply to Rowanne Pretorius

    Hi,

    My concern was treated as a legislation setup issue and has been closed as so.

    When I test on a longtime company, I will get error the moment I try to enter newline of a record that is shown by GTEST flag active.

    If I close the record, the record will be ingested by FUNSTKACC with no issue.

    If the record does have issue, I cannot change it in GTEST mode.

  • Looks like you're dealing with some pretty frustrating errors on V12 Patch Levels 27 and 29 when running the Stock Accounting Interface. The 'variable non-existent' errors seem to be tied to missing or unrecognized fields in the system. It’s good that you’ve already tried validating screens, adding fields, and table validation.

    One thing you might want to check is whether any customizations or missing updates to the patch might be causing these issues. Sometimes, upgrading to the latest patch can resolve system bugs like these. Also, try clearing cache or refreshing the schema, and see if that helps. If the errors persist, reaching out to the software vendor’s support team with detailed logs may be your best bet.

  • 0

    Make sure you also updated any stock journals that were on those patches, if there were any.