Skip to Content
author's profile photo Former Member
Former Member

3FI_GL_XX_SI: Clearing date is not properly updated in delta mode.


we are using the new FI-GL extractors (3FI_GL_xx_SI) in delta process "ADDD like 'ADD' but via Delta Queue".

Records in delta mode ("D") are extraced:

So the delta mode works generally but we have the issue that we didn't get new records for cleared documents. That means within SAP the document was cleared (Clearing date was updated) but in BI the document it's still uncleared because no new updated delta record are extracted:


BI (still only two items with empty clearing date):

SAP Note "1598055" is implemented.

Have someone of you an idea? Any help are welcome!





The extractor checker (RSA3, FULL mode) shows the items with the correct clearing date:

1.png (14.9 kB)
2.png (59.5 kB)
3.png (10.5 kB)
1.png (16.1 kB)
Add a comment
10|10000 characters needed characters exceeded

Related questions

5 Answers

  • Posted on Nov 04, 2014 at 09:24 AM


    Did it work for you in the past ?

    We use 3FI_GL_xx_SI for N1 (IAS) data only, <-- no issues

    for 0L data we use standard 0figl_10/14. <-- no issues.

    May be there are some issues.

    Regards, Leszek

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Leslaw Piwowarski

      Hi Leslaw,

      I checked the steps you provide and for the example document number it seems that there are no changes:

      The following message is displayed:

      No changes selected for document 1800000107 1260 2014

      Message no. F4115

      I talked to our business and they told me that they use transaction "FEBAN" (or "F-28") for setting the clearing date. It seems that no "change" event is trickered within this transactions and therefore no changes are displayed within menu "Environment" -> "Document Changes". Could this be the problem? Should a change event trickered when using the given transactions?

  • Posted on Nov 04, 2014 at 01:03 PM


    That looks like this unfortunately there's no solution either.

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Nov 04, 2014 at 01:29 PM


    As of now , You can do repair full request with proper selections.

    Load those two records.Later do the reporting and see.

    if there is no issues no problem. if any key fig values are doubled then at cube level you can do selective deletion of old data.

    Regarding delta issue please raise to SAP.

    Seems like your delta loads will worked based on delta point settings.

    based on delta settings will pull the records. if clearing date was changed along with delta relevant fields then changed records will be pulled other wise it won't.


    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Nov 05, 2014 at 12:21 PM

    hi maybe you should still to assign the datasource to the general ledger with transaction

    RGUCBIW1_PI - Assign DataSource to a Ledger

    SAP procedure


    DataSources can be generated in the customer namespace (3FI*) only.

    An extract structure needs to have been generated in transaction FAGLBW01 for customer-defined totals tables of new General Ledger Accounting. Note: No extract structure needs to have been generated in transaction FAGLBW01 for totals record DataSources for table FAGLFLEXT and for line item DataSources of new General Ledger Accounting.

    An extract structure needs to have been generated in transaction BW01 for FI-SL totals tables or FI-SL line item tables.


    After starting the transaction, you receive a list of all selectable ledgers for which you can generate or maintain DataSources for the totals records and/or line items. If the ledger that you require does not appear, you may not have generated an extract structure yet for the underlying table. Call transaction FAGLBW01 or BW01 to do so.

    The list contains the following information (columns from left to right):

    • Ledger
    • Description of ledger
    • Table (totals table that the ledger is based on)
    • Totals record DataSource
    • Delta procedure of totals record DataSource
    • Status of totals record DataSource
    • Line item DataSource
    • Status of LI DataSource

    The status is shown by the status indicator on the right hand side, in the column next to the field of the DataSource in question. You can generate or maintain any DataSource by double-clicking the appropriate field in the corresponding column (totals record DataSource or line items DataSource).

    When a new DataSource is created, the system proposes a name in the subsequent dialog box. For totals record DataSources, the proposed name follows the convention 3FI_GL_xx_TT in new General Ledger Accounting (or 3FI_SL_xx_TT in FI-SL); for line item DataSources, it follows the convention 3FI_GL_xx_SI (or 3FI_SL_xx_SI), whereby "xx" serves as a placeholder for the ledger in question. You can change the proposed name (but the initial "3" must remain). Nevertheless, we strongly recommend that you retain the proposed convention.

    For totals record DataSources in new General Ledger Accounting, you can select a delta procedure. For more information, see the online documentation on the relevant radio button.

    We recommend using the delta queue.

    In processing mode, you can exclude individual fields of the ledger from the selection or from the data transfer to BI. When you choose "Save", the system generates the DataSource.

    In the transaction ASSIGN data source to general ledger select ADD method

    Hope it Helps

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Dec 16, 2014 at 04:05 PM


    it seems that the following SAP-Note fix the Problem:


    Please also implement SAP Note 1691854.

    Thanks a lot to the SAP Support! 😊

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.