FSG Error (Account (3))

Customer January 4, 2025 at 3:03 pm

On our CRP1 system, recently licensed for analysis purposes, in our
R12 project, we want to use the Blitz FSG. Some accounts give an error
message after loading, instead of a balance it shows ” Error (Account
(3)) “.
Where can we find an explanation of the error codes? Or a FSG manual
in general (although the UI is rather self explaining)?

Viewing 2 reply threads

Author
Replies
- Support January 5, 2025 at 11:48 am
  Hi,
  This error indicates that the value provided to the balance function parameter ‘Account’ (Segment 3) either doesn’t exist or is incorrectly configured for the selected ledger.
  We are currently in the process of developing a comprehensive user guide, which is not yet published. In the meantime, I would be happy to schedule a call with you to walk you through the functionalities and address any specific issues you are encountering.
  
  Thanks & Regards,
  Mrugesh
- Support January 6, 2025 at 11:44 pm
  Hi,
  Adding to Mrugesh’s comment about the Error (Account(3)) message:
  This appeared so far in two scenarios:
  1. The account segment value passed to the function is invalid as there is no matching flex value found
  2. The passed account segment value is set up as a parent, but it does not have any child account values (either no child ranges are defined or no accounts are matching the defined ranges)
  As we saw that customers often have flex values incorrectly set up as parents without defining any ranges, we are changing our code now to ignore such cases, or to show a more descriptive message.
  Regards,
  Andy
- Customer January 8, 2025 at 12:56 pm
  Hi Andy,
  Thank you for the explanation. First I thought the “3” was an error number, but as Mrugesh stated it’s the 3rd segment, I could have guessed that having setup the segments .
  The issue on our CRP1 environment is indeed end-dated segment values, or parents without children. Both situations might appear in EBS in PROD as well, but of course we will not list the parents without children in the FSG.
  But disabled or end-dated segment values may still have data in older periods so should be listed. Did I see these disabled values in grey in the FSG report? Think that is a good feature!
  Once our consultant/finance lead start looking into the FSG report, we’ll raise questions or suggestions when needed.
  In the meantime I’m trying to match reports and uploads to our CEMLI-List items, I will list the ones that I miss and/or could expect and revert, likely in 1-2 weeks from now.
Author
Replies

Viewing 2 reply threads

You must be logged in to reply to this post.