FAGL_GINS FMGLFLEXT total table not showing all data

[Former Member]

Hi experts I need your help.

In total table we have added new field with FAGL_GINS.

This field is shown in reports for example FAGLB03 or in FGIR node 005.

Problem is that not all values which are posted are shown on reports just some postings.

Please can you help me how to populate total table with all data.

Also in transaction SE11 table FMGLFLEXT not all data is populated.

Another thing is if we call for example FAGLL03 and filter line items with added filed all documents are there.

We have also done checking with program RFFMRC04 all it also shows correct data.

Best regards

[joseluis_basalo]

Hi,

Please check these notes that belong to FI-GL-FL , maybe if these notes don´t help you. You could open a new message on FI-GL forum.

1385880 Error GH 071 for structure FAGL_DERIVE_VALIDITY_

1228772 Error GH 071 with transaction FAGL_GINS

Regards,

JLB

[Former Member]

Thank' s for quick replay, all notes have been imported but now system gives next error message when we do check in transaction FAGL_GINS :

All programs must be regenerated

Message no. GH064

Diagnosis

The system contains inconsistencies. The entries in the data dictionary do not correspond to the current existing program sources.

Procedure

You can bring the system back into a consistent state by choosing the "Activate" function.

[joseluis_basalo]

Hi,

Execute the report RGZZGLUX to regenerate all programs.

Regards,

JLB

[Former Member]

Thank you for replay but report RGZZGLUX end up with Runtime Errors ASSERTION_FAILED.

The ASSERT condition was violated.

Please if you have any idea how to solve this, we will be very appreciated.

Best regards

[joseluis_basalo]

Hi,

Firstly, I would like to tell you that this issue is a typical FI-GL-FL issue, so i´m not expert on this area. Nevertheless, i was checking similar issues and maybe this can help you to understand and solve dump.

Seems to be short dump could be caused by the modification in table FAGL_SCEN_FIELDS for scenario FIN_CONS.

Because these fields are NOT allowed, ASSERT condition is violated and the dump is issued. As it is not allowed to change the field assignment to the scenario, undo these changes.

If you require additional fields, you must create them with OXK3 and carry out FAGL_GINS to extend FAGLFLEXT. Then assign these fields to the ledger itself in customizing, not to the scenario.

However creating/adding additional fields could result in performance issue as described on note 820495.

I hope now, you can solve it

Regards, JLB

[Former Member]

Thank you very much, I need my abaper's to check structure.

I have gave you points.

Best Regards