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
.

Parents
  • 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,

Reply Children
  • 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.