on 04-27-2010 2:25 PM
Hi Team,
Why 0FI_Gl_40 General Ledger Accounting: Line Items datasource is not delta supported? Full upload of FI-GL line item for any big industries is not a feasible solution. 0FI_GL_4/14 all prev extractors were delta enable but why SAP has made new 0FI_GL_40 delta disable? Quite strange step. Please share with me your suggestion or view.
Thanks & Regards,
Ashish
Hi
This is because your ECC environment has been upgraded to EHP3 or EHP4, doesn't mean that the New GL Reporting is automatically available and being used. It has to be configured. Therefore, if you're planning on using the New GL Reporting DataSources, make sure that it has been configured for use in your ECC environment. This can be easily done, if you don't have a communication line with your FI functional people, you can see if data is being populated to the newly introduced table FAGLFLEXA and/or FAGLFLEXT. If there's no data in those tables, you won't be able to use the New GL Reporting DataSources.
Now, having provided that caveat, if you do have the New GL Reporting configured in your ECC environment and want accounting document item data with delta, then you should take a look at the 0FI_GL_14 and 3FI_GL_XX_SI DataSources. You can use the 0FI_GL_14 DataSource for ledger 0L (leading ledger) and the 3FI_GL_XX_SI DataSource (XX would be the ledger designation) for the RS and LG ledgers. All 3 of these DataSources would then flow into DSO 0FIGL_O14.
Santosh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
check this Note 1290358 - DataSource 0FI_GL_40: Extraction of entry view
Reason and Prerequisites
The DataSource 0FI_GL_40 also returns data from the entry view. The selection is controlled and the data separated from the general ledger view using the ledger: The initial value is allowed as a valid restriction and an initial ledger in a returned data record is to be interpreted as an entry view. To assist the selection and the replication, the general ledger (G/L) fields DOCNR, DOCLN and RYEAR in these data records are not left empty but transferred from the corresponding fields in the entry view (BELNR, BUZEI, GJAHR).
Note also that no delta method can be supported for the entry view. With this in mind, check whether the replication of the data compared to the (leaner) direct access offers enough advantages in your business scenario.
Solution
To extract data in the entry view, the InfoPackage in BI must contain the initial value for the ledger selection.
The simplest variant is where no ledger selection takes place. In this case, the initial value automatically lies within the (empty) selection, and the entry view is requested together with all G/L ledgers. However, note that this option is only available as of ERP 6.0 Enhancement Package 4, according to related note 1270834.
One possibility is to restrict the document status: If you are only interested in non-posted documents from the entry view, then it is sufficient to restrict the document status accordingly (the value 1 cannot be contained for BSTAT_S in the selection).
To request the entry view specifically in the InfoPackage, store an ABAP routine (variable type 6) in the data selection area for the characteristic RLDNR. In the predefined source code, between the lines
"$$ begin of routine - insert your code only below this line" and
"$$ end of routine - insert your code only before this line",
insert the following lines (or similar source code with the same semantics):
data: l_idx like sy-tabix.
read table l_t_range with key fieldname = 'RLDNR'.
l_idx = sy-tabix.
l_t_range-fieldname = 'RLDNR'.
l_t_range-iobjnm = '0AC_LEDGER'.
l_t_range-sign = 'I'.
l_t_range-option = 'EQ'.
l_t_range-low = l_t_range-high = space.
modify l_t_range index l_idx.
p_subrc = 0.
In this case, only the initial ledger is requested with the InfoPackage. This corresponds exactly to the entry view.
Santosh
Edited by: Santhosh Nagaraj on May 12, 2010 12:37 PM
Hi,
Even today i have not cared or thought of making a delta load to my Infocube.
Follow this i have done the same in my system.
Step 1
Go to Info Package ---> Datatargets Tab
Step 2
Select the Datatarget that is Cube , there you have a small check box Delete entire content of datatarget.
now save the package and load the data. every time when you load the data to the Cube it delete all the previous request from the cube and load a fresh load with full update.
usuallly it takes time because of the large data , but this is what i am following and i am not missing a single record at the reporting level.
santosh
Thanks Santhosh,
But i can not go for full upload. because our R/3 system contains more then 1 billions of record in FI. You will face the same issue after couple of years when your volume of data increase beyond some limit. I need some method through which i can get delta from 40. else i have to be with the 14 and LIS datasource.
Thanks & Regards,
Ashish
ok... if that is the case... write a routine at the infopackage level to get delta enabled .
Go through this link and hope you could make it
Santosh
hi Ashish Lakdawala :
i had the same problem,
any help please?
Best®ards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi....this datasource is not delta capable because ist specifically created for the Remote Cube
Here you can see the documentation
http://help.sap.com/saphelp_nw70/helpdata/en/88/3c36861f874739a916df63ab6d7ca0/frameset.htm
For the remote cube you want to see always the actual information, theres no need for delta in this case....this is why the extractor is not delta capable.
Regards
Hi Team,
Any clue/Idea/suggestion?
Thanks & Regards,
Ashish
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
83 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.