0FI_AR_4 depencency on 0FI_GL_4

With ECC and BI7.0, does AR (0FI_AR_4) still have a load dependency on 0FI_GL_4?  Thanks

I believe GL is supposed to be extracted first in sequence than AR. I dont what plug in you are in - but this sequence is no more necesssary as of PlugIn2002.2. But still see if you have any dependecies that are resulting to this bhevior.
As soon as DataSource 0FI_GL_4 has been loaded, it is the leading DataSource with regard to accruals, such as the time and date (CPU date) by which extraction should be carried out.
From the transition of the data requirements in Delta-Init-Modus to Delta operation therefore, the data requirement in Delta mode 0FI_GL_4 should take place first.
http://help.sap.com/saphelp_erp2005vp/helpdata/en/55/02142e7bcffa43afa904f62d3e62ca/frameset.htm

Similar Messages

  • Decoupling of AR, AP, GL Datasources (i.e. 0FI_AR_4)

    I've checked out several posts regarding the topic of Decoupling 0fi_ar_4 0fi_ap_4 from 0fi_gl_4, but unfortunatly still don't see my specific issue.
    We have PI 2004_1_46c, BW 3.0b.  I found an OSS note 826023 that says it decouples the extractors.  Now, i thought this would remove the dependency, but we applied this and the dependency is still there.
    In R/3, using RSA3, if I try to view 0FI_AR_4 data, I cannot unless 0FL_GL_4 has been loaded into BW.  I have no use for GL at this time, so I really do want to remove this dependency.
    ALSO, I used CMOD to add logic in the customer exit to populate zz* fields I added to the structure append.  I read in another thread that I could do it this way instead of using the SAP suggested function module (from SAP documentation).  However, now that I have done that, when I try to run the delta init, it just sits there.  When I look at the job log (R/3), it is empty, save for some comments.  Any idea why?
    Any help would be appreciated!!
    Lisa

    Hi Guys!,
    I'm having the same problem, does anybody know if it possible to decoupling the FI extractors??
    Thanks!!.
    Mauricio.

  • Enhancing the extract structure for 0FI_GL_4,  0FI_AP_4,  0FI_AR_4

    Hi all,
          Does anyone know how to enhance the extraction structures with additional fields for datasources 0FI_GL_4 (General ledger: line item), 0FI_AP_4 (vendors: line item) and 0FI_AR_4 (customers: line item). 
    Thanks,
    Sabrina.

    Hi
        Here are the two scenario's described in the note:
    1. All the fields of the customer enhancement in the customer include are contained in the read structure (see the table above).  Then no additional action is required. The fields of the customer enhancement are filled automatically by the datasource from the assigned read structure via "move-corresponding".
    Example:   The extraction structure DTFIGL_4 for datasource 0FI_GL_4 (General ledger: line item) should be enhanced by the VALUT (value date) field.
               To do this, create structure CI_BSIS in the data dictionary of the R/3 source system and include the VALUT field in it. The data dictionary in the R/3 source system shows that the VALUT field is contained in the read structure of the datasource (table BSIS). For that reason the VALUT field is automatically filled by datasource 0FI_GL_4.
    2. Fields of the customer enhancement in the customer include are not contained in the read structure (see the table above).  In this case you have to program a function module to fill the field of the customer enhancement. To do this, there is a Business Transaction Event available (open FI interface for process 00005021). Create any function module you like and use function module SAMPLE_PROCESS_00005021 as a template for the interface (input parameter, changing parameter).
               Interface of function module SAMPLE_PROCESS_00005021:
                Input-parameter I_OLTPSOURCE: datasource that is currently extracting data from the R/3 source system.
                Changing-Parameter C_STRUCTURE: Extraction structure of the data source currently extracting including fields from the assigned customer include. When you call this customer defined function module, all the fields of the extract structure are transferred filled.
               Check whether the type pool SBIWA is declared in the TOP include of the function group.
    If not, add it with the statement TYPE-POOLS: SBIWA.
               Then maintain table TPS31 with Transaction SM30. Create the following entry:
               PROCS LAND APPLK FUNCT
               00005021 <fname>
               <fname> stands for the customer defined function module.
                By doing so, the function module you defined is called for each extracted record. Note that in this case the performance of the extraction may be reduced significantly regardless of the table read and the complexity of the programmed logic.
               Example:
               You want to enhance the extraction structure DTFIAR_3 for datasource 0FI_AR_4 (customers: line item) by the ORT01 (city) field from the customer master record.
                To do this, create structure CI_BSID in data dictionary of the R/3 source system and include the ORT01 field in that. The data dictionary in the R/3 source system displays that the ORT01 field is NOT contained in the read structure of datasource 0FI_AR_4 (Table BSID).
                Therefore you have to program a function module that reads the customer master in the R/3 system (table KANN1) and fills the ORT01 field of the customer enhancement. In the changing parameter C_STRUCTURE the filled fields of the extraction structure DTFIAR_3 are available to you. With the KUNNR field of extraction structure DTFIAR_3, you can select the respective master data record from table KNA1 and determine field ORT01 of the customer enhancement.
    1. All the fields of the customer enhancement in the customer include are contained in the read structure (see the table above).
               Then no additional action is required. The fields of the customer enhancement are filled automatically by the datasource from the assigned read structure via "move-corresponding".
               Example:
               The extraction structure DTFIGL_4 for datasource 0FI_GL_4 (General ledger: line item) should be enhanced by the VALUT (value date) field.
               To do this, create structure CI_BSIS in the data dictionary of the R/3 source system and include the VALUT field in it. The data dictionary in the R/3 source system shows that the VALUT field is contained in the read structure of the datasource (table BSIS). For that reason the VALUT field is automatically filled by datasource 0FI_GL_4.
               ATTENTION:
               By using Note 430303 you can enhance DataSource 0FI_GL_4 by all fields from table BSEG (instead of BSIS); then the fields are filled automatically in the extractor.
    1. Fields of the customer enhancement in the customer include are not contained in the read structure (see the table above).
                In this case you have to program a function module to fill the field of the customer enhancement. To do this, there is a Business Transaction Event available (open FI interface for process 00005021). Create any function module you like and use function module SAMPLE_PROCESS_00005021 as a template for the interface (input parameter, changing parameter).
               Interface of function module SAMPLE_PROCESS_00005021:
                Input-parameter I_OLTPSOURCE: datasource that is currently extracting data from the R/3 source system.
                Changing-Parameter C_STRUCTURE: Extraction structure of the data source currently extracting including fields from the assigned customer include. When you call this customer defined function module, all the fields of the extract structure are transferred filled.
               Check whether the type pool SBIWA is declared in the TOP include of the function group.
    If not, add it with the statement TYPE-POOLS: SBIWA.
               Then maintain table TPS31 with Transaction SM30. Create the following entry:
               PROCS LAND APPLK FUNCT
               00005021 <fname>
               <fname> stands for the customer defined function module.
                By doing so, the function module you defined is called for each extracted record. Note that in this case the performance of the extraction may be reduced significantly regardless of the table read and the complexity of the programmed logic.
               Example:
               You want to enhance the extraction structure DTFIAR_3 for datasource 0FI_AR_4 (customers: line item) by the ORT01 (city) field from the customer master record.
                To do this, create structure CI_BSID in data dictionary of the R/3 source system and include the ORT01 field in that. The data dictionary in the R/3 source system displays that the ORT01 field is NOT contained in the read structure of datasource 0FI_AR_4 (Table BSID).
                Therefore you have to program a function module that reads the customer master in the R/3 system (table KANN1) and fills the ORT01 field of the customer enhancement. In the changing parameter C_STRUCTURE the filled fields of the extraction structure DTFIAR_3 are available to you. With the KUNNR field of extraction structure DTFIAR_3, you can select the respective master data record from table KNA1 and determine field ORT01 of the customer enhancement.
    After you create the customer include in the R/3 source system you have to post process the accompanying datasource with Transaction RSA6. Select the application component according to the above table and change the datasource that fits the customer include. The "Hide fields" flag should be removed in the field list for the fields of the customer include. Then save the field list.
    If the fields of the customer include is not displayed in Transaction RSA6, refer to note 415530.
    1.  After you create the customer include in the R/3 source system you have to post process the accompanying datasource with Transaction RSA6. Select the application component according to the above table and change the datasource that fits the customer include. The "Hide fields" flag should be removed in the field list for the fields of the customer include. Then save the field list.
    If the fields of the customer include is not displayed in Transaction RSA6, refer to note 415530.
    Please let me know.
    Thanks,
    Sabrina.

  • 0FI_GL_4 failing due to enhancement for 0FI_AR_4

    Hi Gurus,
    I have enhanced the 0FI_AR_4 datasource with additional fields.  Create my function module and assigned it to 00005021 in table TPS31.  This works great for the AR extraction.  But now the GL extraction is failing on this function module.   This is the error message during the execution of extractor for 0FI_GL_4 ==>  'The data object "C_STRUCTURE" has no structure and therefore no component called "VBELN"..    Why would the 0FI_GL_4 extractor call the function module exit for the 0FI_AR_4?   Any help you can provide will be greatly appreciated. 
    Thank you in advance!!
    Andy

    hi
    0FI_GL_4 & 0FI_AR_4 are linked to gather.. hence when u enhance, u need to take care of this..
    read below SAP Note:
    410799

  • 0FI_AR_4 and 0FI_AP_4 Contents

    Hi Gurus!
    What kind of line items do 0FI_AR_4 and 0FI_AP_4 extract? When I check RSA3, it just lists the first line item in an accounting document data. Does it really work that way? Shouldn't it be extracting all the line items in a document? Or, I just missed configuring something?
    THanks for any help,
    Maan

    Maan,
    AR line items extract from BSID and BSAD (open and closed AR line items) and
    AP line items extract from BSIK and BSAK (open and closed AP line items)
    Depending on your plug-in level, these extractors may be coupled with GL line items extractors 0FI_GL_4 (from BKPF and BSEG) and that drives the selection for AR and AP extractors.
    Hope this helps,
    Mary

  • 0FI_AR_4 not fetching delta

    hi experts,
    i am having problem with 0fi_ar_4, i have run the init with data transfer for this datasource and it went successfully, But delta values are not able to fetch, delta infopackage brings 0 records with green status.
    In rsa7 there are no records for this datasource. I have checked in smq1 also no luws are stuck there
    I have 0fi_gl_4 data source which is working fine with full and as well as delta.
    I have checked in bwom2_timest which has last updated information for  0fi_ar_4 and delta also. But the values in delta run are not fetching.
    The same data source is working fine in development system. I can able to see delta records in rsa7 against this 0fi_ar_4 DS.
    please suggest me ..

    Hi..
    For FI datasources you will not be able to see any data in the delta queue..
    Data will get populated in the delta queue during extraction..
    After init...it writes the entries into the time stamp table BWOM2_TIMEST in the SAP R/3 System with a new upper limit for the time stamp selection...
    Depending on that data will get fetched from the table BKPF based on creation date (CPUDT)...
    For 0FI_AR_4 (AR- line items )Selections are made from tables BSID/BSAD (Accounts Receivable)
    This is for new entries.......
    For changed records data will get fetched from the table BWFI_AEDAT , depending on the time stamp table BWOM2_TIMEST....
    Check the following blog :
    /people/swapna.gollakota/blog/2008/01/14/one-stage-stop-to-know-all-about-bw-extractors-part1
    Regards,
    Debjani.........

  • 0FI_AR_4 extractor bringing zero records

    Hi,
    We are using extractor 0FI_AR_4 as delta. At times it is bringing zero records but the next time it brings data along with the daata missed the previous day.
    For ex
    Monday it brought records until previous week
    Tuesday it brought zero record
    Wednesday it brought more records i.e including records created on Monday and Tuesday
    We could not figure out a situation when can this happen. But our observation is that there is no entry for tuesday in the table BWOM2_TIMEST.
    BWOM_SETTINGS
    BWFILOWLIM     19910101
    BWFINSAF         3600
    BWFISAFETY     1
    BWFITIMBOR      020000
    DELTIMEST         60
    OBJCURTYPE    10
    Regards
    Vijay

    check http://help.sap.com/erp2005_ehp_04/helpdata/EN/af/16533bbb15b762e10000000a114084/content.htm
    it states :
    In delta mode, data requests with InfoSource 0FI_AR_4 and InfoSource 0FI_AP_4 do not provide any data if no new extraction has taken place with InfoSource 0FI_GL_4 since the last data transfer. This ensures that the data in BW for Accounts Receivable and Accounts Payable Accounting is exactly as up to date as the data for General Ledger Accounting.
    you can check this...de link gives details about the delta methods for FI extractors

  • 0FI_AR_4 delta problem

    We have recently implemented the 0FI_AR_4 extract of AR customer items into BW in conjunction with some of the Collections Management targets.  This appeared to be working well and was giving the data we expected.  However, after we started loading in Production, we realized that items that were being cleared after the initialization were still being reflected as Open in the BW datastore/cube.  In looking at the delta updates, we see the clearing document itself but no records affecting marking the old Open items with a Cleared status/date/etc.
    After reinitializing the targets, the affected data looks correct again and the items are marked as Cleared.  We get Delta updates nightly but it just doesn't appear to be everything we expect.  I have looked at some old notes in this area discussing 0FI_GL_4 and possible dependencies or need to decouple them.  We are on SAP ECC 6.0 - 7.0SP14 and BW 7.0 SP21.  Could anyone elaborate on if there would still be any need to also load 0FI_GL_4 to get 0FI_AR_4 deltas to work?  Or if there is anything I should specifically look for in this area before opening up a message with OSS?  For now, I was just going to have reinitialize it periodically to be safe.
    Thanks in advance for any assistance you can provide on this...

    Abby, we did some more research on exactly how the deltas worked with this extract in our environment.  Ultimately we didn't change anything -- I think it was more in just figuring out what timeframes were being pulled so we could understand differences in balances between R3 and BW at a given point.  There are other tables involved beyond just BSID and BSAD.  Such as BWFI_AEDAT that holds pointers to changed records in BSID/BSAD, since those tables don't have a 'change' date in all instances to work from with deltas.  There was also a table called BWOM2_TIMEST that holds delta upper limit timestamp info for each 0FI_AR_4 load and it behaves based on settings in BWOM_SETTINGS.  It controlled the time periods involved in each daily load (i.e. in our case, it went from 10 pm to 10 pm), so that was also part of the reason we were 'missing' records.  We didn't realize that a load running at 5 am one morning was only pulling records up to 10 pm the preceding night.  Once we felt better about the completeness of the records coming into BW, we no longer pursued it.
    This extract is by design a daily load.  But there are some notes out there about doing additional configuration to set up 'minute based' extraction and be able to run it multiple times in a day.  Fortunately we didn't have to look further into it.  Also, the 'coupling' between 0FI_GL_4 and 0FI_AR_4 were no longer a requirement in our version, so apparently that was never part of the issue either.
    Hope that helps you.  Good luck...

  • 0FI_AR_4 Delta not working like I think it should be

    I have the extractor/DataSource 0FI_AR_4 installed and I am on a 7.0 technical upgrade.  I have not yet migrated anything to the new 7.0 dataflow so I am still running 3.x data flow with this extractor.  My issue is that when I check RSA7 for this extractor I usually see 0 records.  Yesterday I saw 3 LUWs in RSA7 for this extractor but they were not AR records - it looked more like metadata.  Next I went to RSA3 and chose Update Mode u2018Du2019 and I got zero records back.  I ran the Delta InfoPackage 3 times yesterday and only got data once - the other two requests I got back 0 records.
    I read that since PlugIn 2002.2 that we no longer have to decouple GL from AR.  Is this true?  This was my first guess but we don't even have 0FI_GL_4 installed.
    Somehow the data is getting into our 0FIAR_O03 DSO, but I canu2019t identify how that data is being collected.  It looks like there is also a lag in the time that the data gets entered into ECC and when it finally gets extracted.  Any ideas?

    There are conflicting statements on help.sap.com
    1: In delta mode, data requests with InfoSource 0FI_AR_4 and InfoSource 0FI_AP_4 do not provide any data if no new extraction has taken place with InfoSource 0FI_GL_4 since the last data transfer. This ensures that the data in BW for Accounts Receivable and Accounts Payable Accounting is exactly as up to date as the data for General Ledger Accounting.
    2: As the strict connection of DataSources has been abolished as of PlugIn2002.2, you can now load 0FI_GL_4, 0FI_AR_4, 0FI_AP_4 and 0FI_TX_4 in any order you like. You can also use DataSources 0FI_AR_4, 0FI_AP_4 and 0FI_TX_4 separately without 0FI_GL_4. The DataSources can then be used independently of one another.
    Which is true?

  • 0FI_AR_4 extraction issue - actual fiscal year

    We are having problems with 0FI_AR_4 when extracting actual fiscal year data. For previous fiscal years, we run a full load, but when we tried to initialize the extractor for actual fiscal year there are no records. Cheked RSA3 and same problem. But with in RSA3 with 0FI_AR_3 there is plenty of records.
    PI_BASIS is 2005_1_700 level 13, so there shouldn't be any dependece with 0FI_GL_4.
    Any ideas on what might be happening ?
    Regards,
    SJR

    if you want you can try to manage the 0FI_AR with delta - launch a init for initialize the data loads and after this create a new infopackage delta to manage the new data
    alternatevely you can try with  a full repair load
    Hope it helps
    Andrea

  • 0FI_AR_4 Datasource, Delta

    Hi Experts,
    we are using 0FI_AR_4 datasource, this is delta enable, but the problem is we can run delta just once a day.
    Can any one please let me know how to change this so that i can run the delta more than once a day.
    Any document or a link would be of great help.
    Thanks in advance.
    Ananth

    hi Ananth,
    take a look Note 991429 - Minute Based extraction enhancement for 0FI_*_4 extractors
    https://websmp203.sap-ag.de/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=991429&_NLANG=E
    Symptom
    You would like to implement a 'minute based' extraction logic for the data sources 0FI_GL_4, 0FI_AR_4 and 0FI_AP_4.
    Currently the extraction logic allows only for an extraction once per day without overlap.
    Other terms
    general ledger  0FI_GL_4  0FI_AP_4  0FI_AR_4  extraction  performance
    Reason and Prerequisites
    1. There is huge volume of data to be extracted on a daily basis from FI to BW and this requires lot of time.
    2. You would like to extract the data at a more frequent intervals in a day like 3-4 times in a day - without extracting all the data that you have already extracted on that day.
    In situations where there is a huge volume of data to be extracted, a lot of time is taken up when extracting on a daily basis. Minute based extraction would enable the extraction to be split into convenient intervals and can be run multiple times during a day. By doing so, the amount of data in each extraction would be reduced and hence the extraction can be done more effectively. This should also reduce the risk of extractor failures caused because of huge data in the system.
    Solution
    Implement the relevant source code changes and follow the instructions in order to enable minute based extraction logic for the extraction of GL data. The applicable data sources are:
                            0FI_GL_4
                            0FI_AR_4
                            0FI_AP_4
    All changes below have to be implemented first in a standard test system. The new extractor logic must be tested very carefully before it can be used in a production environment. Test cases must include all relevant processes that would be used/carried in the normal course of extraction.
    Manual changes are to be carried out before the source code changes in the correction instructions of this note.
    1. Manual changes
    a) Add the following parameters to the table BWOM_SETTINGS
                             MANDT  OLTPSOURCE    PARAM_NAME          PARAM_VALUE
                             XXX                  BWFINEXT
                             XXX                  BWFINSAF            3600
                  Note: XXX refers to the specific client(like 300) under use/test.
                  This can be achieved using using transaction 'SE16' for table
                             'BWOM_SETTINGS'
                              Menue --> Table Entry --> Create
                              --> Add the above two parameters one after another
    b) To the views BKPF_BSAD, BKPF_BSAK, BKPF_BSID, BKPF_BSIK
                           under the view fields add the below field,
                           View Field  Table    Field      Data Element  DType  Length
                           CPUTM       BKPF    CPUTM          CPUTM      TIMS   6
                           This can be achieved using transaction 'SE11' for views
                           BKPF_BSAD, BKPF_BSAK , BKPF_BSID , BKPF_BSIK (one after another)
                               --> Change --> View Fields
                               --> Add the above mentioned field with exact details
    c) For the table BWFI_AEDAT index-1  for extractors
                           add the field AETIM (apart from the existing MANDT, BUKRS, and AEDAT)
                           and activate this Non Unique index on all database systems (or at least on the database under use).
                           This can achived using transaction 'SE11' for table 'BWFI_AEDAT'
                               --> Display --> Indexes --> Index-1 For extractors
                               --> Change
                               --> Add the field AETIM to the last position (after AEDAT field )
                               --> Activate the index on database
    2. Implement the source code changes as in the note correction instructions.
    3. After implementing the source code changes using SNOTE instruction ,add the following parameters to respective function modules and activate.
    a) Function Module: BWFIT_GET_TIMESTAMPS
                        1. Export Parameter
                        a. Parameter Name  : E_TIME_LOW
                        b. Type Spec       : LIKE
                        c. Associated Type : BKPF-CPUTM
                        d. Pass Value      : Ticked/checked (yes)
                        2. Export Parameter
                        a. Parameter Name  : E_TIME_HIGH
                        b. Type Spec       : LIKE
                        c. Associated Type : BKPF-CPUTM
                        d. Pass Value      : Ticked/checked (yes)
    b) Function Module: BWFIT_UPDATE_TIMESTAMPS
                        1. Import Parameter (add after I_DATE_HIGH)
                        a. Parameter Name  : I_TIME_LOW
                        b. Type Spec       : LIKE
                        c. Associated Type : BKPF-CPUTM
                        d. Optional        : Ticked/checked (yes)
                        e. Pass Value      : Ticked/checked (yes)
                        2. Import Parameter (add after I_TIME_LOW)
                        a. Parameter Name  : I_TIME_HIGH
                        b. Type Spec       : LIKE
                        c. Associated Type : BKPF-CPUTM
                        d. Optional        : Ticked/checked (yes)
                        e. Pass Value      : Ticked/checked (yes)
    4. Working of minute based extraction logic:
                  The minute based extraction works considering the time to select the data (apart from date of the document either changed or new as in the earlier logic).The modification to the code is made such that it will consider the new flags in the BWOM_SETTINGS table ( BWFINEXT and BWFINSAF ) and the code for the earlier extraction logic will remain as it was without these flags being set as per the instructions for new logic to be used(but are modified to include new logic).
    Safety interval will now depend on the flag BWFINSAF (in seconds ; default 3600) and has  a default value of 3600 (1 hour), which would try to ensure that the documents which are delayed in posting due to delay in update modules for any reason. Also there is a specific coding to post an entry to BWFI_AEDAT with the details of the document which have failed to post within the safety limit of 1 hour and hence those would be extracted as a changed documents at least if they were missed to be extracted as new documents. If the documents which fail to ensure to post within safety limit is a huge number then the volume of BWFI_AEDAT would increase correspondingly.
    The flag BWFINSAF could be set to particular value depending on specific requirements (in seconds , but at least 3600 = 1 hour)  like 24 hours / 1 day = 24 * 3600 => 86400.With the new logic switched ON with flag BWFINEXT = X the other flags  BWFIOVERLA , BWFISAFETY , BWFITIMBOR are ignored and BWFILOWLIM , DELTIMEST will work as before.
    As per the instructions above the index-1 for the extraction in table BWFI_AEDAT would include the field AETIM which would enable the new logic to extract faster as AETIM is also considered as per the new logic. This could be removed if the standard logic is restored back.
    With the new extractor logic implemented you can change back to the standard logic any day by switching off the flag BWFINEXT to ' ' from 'X' and extract as it was before. But ensure that there is no extraction running (for any of the extractors 0FI_*_4 extractors/datasources) while switching.
    As with the earlier logic to restore back to the previous timestamp in BWOM2_TIMEST table to get the data from previous extraction LAST_TS could be set to the previous extraction timestamp when there are no current extractions running for that particular extractor or datasouce.
    With the frequency of the extraction increased (say 3 times a day) the volume of the data being extracted with each extraction would decrease and hence extractor would take lesser time.
    You should optimize the interval of time for the extractor runs by testing the best suitable intervals for optimal performance. We would not be able to give a definite suggestion on this, as it would vary from system to system and would depend on the data volume in the system, number of postings done everyday and other variable factors.
    To turn on the New Logic BWFINEXT has to be set to 'X' and reset back to ' ' when reverting back. This change has to be done only when there no extractions are running considering all the points above.
                  With the new minute based extraction logic switched ON,
    a) Ensure BWFI_AEDAT index-1 is enhanced with addition of AETIM and is active on the database.
    b) Ensure BWFINSAF is atleast 3600 ( 1 hour) in BWOM_SETTINGS
    c) Optimum value of DELTIMEST is maintained as needed (recommended/default value is 60 )
    d) A proper testing (functional, performance) is performed in standard test system and the results are all positive before moving the changes to the production system with the test system being an identical with the production system with settings and data.
    http://help.sap.com/saphelp_bw33/helpdata/en/af/16533bbb15b762e10000000a114084/frameset.htm

  • 0FI_AR_4 Initilaization issues

    Hi All,
    I was going thru messages on and found quite a few messages on this
    the below was the the closest to our issue. We have around 5 million records to be pulled.
    0FI_AR_4 - Slow Sequential Read in ECC on Initial Load
    Also iIdid read that we have to load 0FI_GL_4 before we load 0FI_AR_4. We do not have FI GL implemented in BW nor in R/3.
    We are on R/3 4.7 Version & BW 7.0, we are in process of upgrade to ECC 6.0 which woudl happen by March 2010.
    So how does this condition satisfy of laoding GL before AR.
    Regards
    Lalan

    [OSS Note 641977 - Poor performance|https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=641977], which was listed in the post that you referenced, should resolve the issue, but when we deployed the indexes in that OSS Note via SE11 in R3/ECC, they weren't being invoked. We had to have our Basis DBA create the indexes at the RDBMS level and then they got invoked perfectly.
    What we've found is that any of the SAP recommended indexes related to FI-CO/PA tend to need to be created at the Oracle level instead of at the application level using SE11 in R3/ECC.

  • 0fi_gl_4 init is not pulling any data

    Hi All,
      We have ofi_gl_4 installed and running fine with deltas. We thought of reinitializing the delta because of some business reasons. I deleted the delta initialization and started delta initialization with data transfer with Fiscal Year/Period selection. It is not pulling any records and it is saying there is no new delta since last extraction. I'm sure there is data as this extractor pulled the data so far for this period.
      Then I thought of testing this using RSA3. Even RSA3 is not pulling any data. But there is data in BKPF/BSEG for this periods.
    The extractor is putting the correct time stamps in BWOM2_TIMEST and all other entries in tables like TPS31, BWOM_SETTINGS are all okay.
    Did any body faced this problem? Is there any change in the FI extractors recently?
    Your help is greatly appreciated.
    Thanks,
    Trinadha

    Hello Trinadha,
    You may want to have a look at OSS note 640633. Following is the text from note.
    Hope it helps.
    Regards,
    Praveen
    Symptom
    Deleting the Init 0FI_GL_4 deletes all BWFI_AEDAT data
    Other terms
    0fi_gl_4, 0fi_ar_4, 0fi_ap_4, 0fi_tx_4, BWFI_AEDAT, BWFI
    Reason and Prerequisites
    The system was intentionally programmed like this.
    Solution
    The error is corrected in the standard system with PI 2004.1.
    The reset logic is changed with this note so that during the reset, the DataSources 0FI_4 only delete their own entries in the initial selection table (ROOSPRMSF) and in the time stamp table (BWOM2TIMEST). The data of the table BWFI_AEDAT is, however, only deleted if no more 0FI__4 DataSources are active.
    Proceed as follows for the advance correction:
    1. Install the code in function module BWFIT_RESET_TIMESTAMPS or include LBWFITTOP.
    2. Create an executable program ZFCORR_BW_02 with transaction /NSE38.
    Program title:        Change 0FI_*_4 DataSources.
    Selection texts:      Name Text
                           OBJVERS Version
                            OLTPSOUR DataSource
    Implement the source code of program ZFCORR_BW_02.
    Execute the program for the DataSources 0FI_AR_4, 0FI_AP_4 and 0FI_TX_4. The program uses the BWFIT_RESET_TIMESTAMPS function module as a reset module for these DataSources.

  • 0fi_Gl_4 see data in R/3 side

    Hi ,
    I want to check the data 0fi_Gl_4 in R/3 side. Because some documents are missing... So need to check it out that is available in 0fi_Gl_4 or not

    Hi Naman,
    Use the extract checker txn code -RSA3 to check the data on the R/3 side.
    Hope this helps.
    Regards,
    Hima

  • Remote cube on Data Source 0FI_GL_4

    HI,
    I have a requirement of  reconciling  the Line Items from R/3 to BW.
    So i tried to create Remote cube with Direct access, but coudnt due to 0FI_GL_4 data source doesnt support Direct access and reconciliation.
    I can see that Data Source  0FI_GL_4  is being fetched by Function module BWFID_GET_FIGL_ITEM and the base table is DTFIGL_4.
    My question is can I create the Generic data source based on the function module by taking the copy of existing FM BWFID_GET_FIGL_ITEM  and change Direct access option to 2(Supports Preaggregation).
    Do i need to change any settings at table level and parameters to get the required solution.
    Please sugget me how to proceed the development to reconcile the Line Items from R3 to BW.
    Regards,
    Siva..
    Edited by: Siv Kishore on Apr 7, 2011 4:59 PM

    HI Banerjee,
    Thanks for the update.
    As you said i cant use the data source 0FI_GL_1, Because we need to reconcile many fields from R/3 to BW, but  those fields are not available in this data source and it will be complicated to enhance such fields.
    can I create View based generic data source on BSEK and BSEG tables, Will it work? if yes do i need to follow any criteria to get the Correct Line Items.
    Please suggest me is there any SAP suggested solution or if you worked on such kind of development.
    Regards,
    Siva Thottempudi..
    Edited by: Siv Kishore on Apr 12, 2011 4:06 PM

Maybe you are looking for