Delta Mechanism for BPC to BI

Hello Guru,
I have below scenario configured for BPC. Do please let me know your thoughts.
I have 0FIGL_C10 infocube configured in BW where i have data for Entity 1000, 2000& 3000. Data is available from the year Jan 2006 till Nov 2011. 0FIGL_C10 infocube gives data in 3 currencies (00, 10 & 20)
My requirement is below.
1. Entity 1000 is discontinued but data still comes in 0FIGL_C10 infocube. How should i restrict this entity in BPC ? Data manager package doesn't have any selection criteria option like Transformation file has..
2. I have 2 reports. P&L and Balance Sheet. for Balance Sheet , I want to select 100000 to 200000 G/L Account with Currency Type 30 & for P&L, I want to select 300000 to 400000 G/L Account with Currency Type 10. Do let me know how this can be done ?
3. I have data from Jan 2006 till Nov 2011 in my BI Infocube but i want to load only 2011 data into my BPC. So, with that said when i do initialization from BI to BPC, i should be able to extract data from Jan 2011 till Nov 2011 and from December onwards i should be able to extract data for December and then onwards month. How should i manage this because in BI i have data for last 4 years.
Do let me know your valuable thoughts.
Regards,
Komik Shah

Hi,
The set selection feature should serve your puprose.
Have you considered an integration layer with in BW from where you can do the data loads into BPC? You can check the pros and cons of having a new layer.
If you have then, you could use DTP filters when loading to the infocube in the integration layer from FIGL. You need to have other criteria as well to have the staging layer. Just check.
- Restricting Entity 1000....Do you have the conversion file for Entity. You could do *SKIP in a conversion file for this entity.
You could have a routine in BW integration cube to force a particular currency type for PL accounts & GL accounts. Try also looking at using an IF condition in transformation file for currency type selection
RPTCURRENCY=*IF(0CURTYPE=*STR(10) then *STR(LC); TC)
RPTCURRENCY is a currency type dimension in your application. LC and TC are members of this dimension in BPC.
Thanks,
Sreeni

Similar Messages

Delta Mechanism for LO Extraction.... urgent plz

hi experts,
Could you plz.. give me the details below for LO EXTRACTION DELTA MECHANISM.
for the first time load i have done initialize with data transfer. what should i do if i want to extract the new data(Changed Records) from r/3. what are all the settings i need to give. i am using BI7.
plz provide me the documentation for LO EXTRACTION DELTA MECHANISM.
regards
vadlamudi

Hi,
After initialization you need to check the deltas in RSA7 after the load.
For further explanation check these blogs by Roberto Negro:
Episode one:
/people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146
Episode two:
LOGISTIC COCKPIT DELTA MECHANISM - Episode two: V3 Update, when some problems can occur...
Episode three:
LOGISTIC COCKPIT DELTA MECHANISM - Episode three: the new update methods
Also check
Gist of LO Cockpit Delta
Assign points if this helps........
Rgs,
I.R.K

Delta mechanism for 0fi_gl_14

Hi,
We are using 0fi_gl_14 DS for extracting leading ledger's line item data.
But when I checked table BWOM2_TIMEST, there is no entry for the above data source.
Could someone help me understand delta mechanism for 0fi_gl_14?
Is it not similar to 0fi_gl_4 delta?
What is the difference between 0fi_gl_4 and 0fi_gl_14?
Regards,
Shravani

Hi,
Most of the extractors (specially one in question 0FI_GL_14) in FI related extractors work on pull mechanism via Extraction method: F1 (function module (complete interface))
Extractor: FAGL_GET_SI_DATA
1. 0FI_GL_14 extractor, considers all data from the tables FAGLFLEXA (or similar customer tables), BKPF, BSEG, and BSEG_ADD. we use this extractor if New GL configuration done in ECC or otherwise 0FI_GL_4 still holds good.
2.Coming to Delta are picked from BWFI_AEDAT table where all the changed documents/new are maintained as part of changed status.
Hope i have addressed your question!
Regds,
Karunakar P

Delta Mechanism for LO Cockpit

Hi All,
Currently I am having an issue with an implementation on Sales Order. As understood from Generic DataSource that is available in transaction code SBIW. We are able to create a datasource with the ability to trace the changes that is occuring in a particular transaction by using either addtive delta or new status for changed record.
In Data Source, 2LIS_11_VAITM, which is only available in LO Cockpit, is it possible to have the same tracing too? As I know in LO Cockpit, we have the queued delta, direct delta and the unserialized v3 update, but this is not the delta that we would want.
Really need help urgently on this matter.
Thanks.

It works with the Business content datasource (because it is built in the extractor logic), eg 2LIS_11_VAITM.
This is what is confusing to many people. And it is same as file source system. In the file based DS, you do have an option of specifying whether it is a additive delta (in the datasource editor screen, at least it was till 3.5). This doesn't mean that the file will be read and system will compare from ? PSA or earlier load of the file and determine the delta to be pushed to BW. It means that we are saying that the file already contains delta.
Same here. When we specify additive delta, we are saying that the table/view already contains additive delta (and not that the generic extractor will apply the logic to derive the delta values for the KF).
Let us take an example, say you are storing stock market quotes in a spreadsheet or a table, and you want to move it to BW using generic extractor which loads the current prices to an ODS/Cube.
Let us say the data is like this
STOCK-ID--CLOSING_PRICE--
Movement_since_last_price
NYDE -
60 - -
3.5
HWP -
125 -
-1.25
and so on.
Now, if from this table (or file), you push STOCK_ID, and CLOSING_PRICE using your generic extractor, it is a 'new image' and that is what you should specify.
But, you can also instead push STOCK_ID and 'MOVEMENT' in which case it is an 'additive delta' and you should specify your DS as such.
If you only had STOCK_ID and MOVEMENT data in your table, your DS would have to be 'additive delta'.
I hope you understand it now. Your table data determines what delta type the generic DS is, you can not just specify it as you wish.
Why this setting is there - it tells BW what type of DS it is, so it can warn you if you are trying to load it to incompatible target. For example, if you had a 'new image' type DS, and you tried to load it directly to a cube, the system will give you a warning/error about it being incompatible.

Repeat Delta mechanism for FI-CO & Generic extractor.

Hello Guys,
Can any one please let me know whether there is repeat delta is possible for FI/CO data sources if we miss any daily dela loads.
If its there, how it works.
thanks in advance
peter.

Hi,
Yes, it is possible to repeat the failed delta for FICO extractors. One thing you need to note is that you need to request the delta second time only then you will get records to BW. First time repeat will fetch 0 records.
Hope this helps
Regards.,
Srni

Delta mechanism for LO Cockpit and COPA datasources

What is the trigger for creating a delta for LO cockpit datasources. Is it a result of calling the LIS exit or the actual creation/change to the transaction?
I have this same question for the COPA datasource.
Thanks
Jim Goodwine

The trigger that you are talking about must be running of a infopackage in BW that extracts data from R/3. When transactions are posted in R/3 (both LIS and COPA), they start accumulating in the delta queue of that datsource in R/3.
A infopackage is scheduled to execute at regular intervals that pull the data from this delta queue into BW.

Delta mechanism setting on R/3 side for a datasource from the FI area

Hi,
How to activate delta data transfer on the R/3 side for a FI related datasource?
For sales and logistics related datasources, there's LBWE where you can activate the delta mechanism.
I have a datasource called 'Committment line items for Funds Management' that comes under FI Management. What is the procedure to activate the delta mechanism for this datasource?
Thanks
Edited by: Sanjeev Koganti on Mar 21, 2008 2:07 PM

Hi,
Financial Accounting line items are read by extractors directly from the tables in SAP R/3.
A time stamp on the line items serves to identify the status of the delta data.
Time stamp intervals that have already been read are stored in a time stamp table.
The delta dataset is transferred to BW directly, without records being transferred to the delta queue in SAP R/3 (extractor delta method).
The FI Extractors are typically function module extractors. The function module for the extractors are as follows:
0FI_TX_4 - BWFID_GET_FITAX_ITEM
0FI_GL_4 - BWFID_GET_FIGL_ITEM
0FI_GL_2 - FBIW_DATA_TRANSFER_GL_2
0FI_GL_1 - FBIW_DATA_TRANSFER_GL_1
0FI_AR_3 - FBW4_DATA_TRANSFER_AR_3
0FI_AP_4 - BWFID_GET_FIAP_ITEM
0FI_AP_3 - FBW4_DATA_TRANSFER_AP_3
Refer.
FI-SL Extraction
http://www.jt77.com/business-warehouse/work-flow-13393.html
http://www.saptutorials.com/list/1/,B,BW,xhtml
Steps to move data from SAP r3 into BW
http://www.jt77.com/business-warehouse-q/index20.html
http://jt77.com/business-warehouse/work-flow-15111.html
http://help.sap.com/saphelp_sm32/helpdata/en/f9/eb7641b61b5858e10000000a1550b0/RN_353_e.pdf
CO-PA and FI-SL EXTRACTIONs
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/FISL/FISL.pdf
http://help.sap.com/saphelp_47x200/helpdata/en/66/bc7d2543c211d182b30000e829fbfe/frameset.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/a7f2f294-0501-0010-11bb-80e0d67c3e4a
Re: Which tables for LO and FI...
http://help.sap.com/saphelp_nw04/helpdata/en/af/16533bbb15b762e10000000a114084/frameset.htm
Difference between FI and LO extraction
Extraction Steps for FI Data Sources
FI-GL Extraction steps
Re: FI Extraction Steps
http://help.sap.com/saphelp_bw32/helpdata/en/af/16533bbb15b762e10000000a114084/frameset.htm
Thanks,
JituK

Is Delta possible for the below mentioned data sources in your systems?

Hi All,
I am strongly belive that these below datasources are not having delta.
By any change recently is there any ECC systme new plugins may having these datasources also delta's?
0FUNCT_LOC_ATTR
0EQUIPMENT_ATTR
0NOTIFICATN_ATTR
0ASSET_ATTR
0CS_ORDER_ATTR
0EMPLOYEE_ATTR
Please confirm me if any of your case having delta's for these datasources?
Regards
Srini
Edited by: Srinivas Gogineni on Feb 27, 2010 10:38 PM

Hi,
SAP Note #1619612 will be released in a few days to enable deltas on 0CS_ORDER_ATTR.
[1619612 - Delta mechanism for 0CS_ORDER_ATTR.|https://websmp107.sap-ag.de/sap/support/notes/1619612 ]
Kind Regards,
Paulo Jr.

How to make added custom field Delta mechanism work for LO Cookpit?

We appended a new custome field into extraction structure of the LO Cookpit datasource 2LIS_02_ITM through RSA6. And then run CMOD to write the exit code to populate the value and it works fine. But after we read Roberto's Weblog:
/people/sap.user72/blog/2005/02/14/logistic-cockpit--when-you-need-more--first-option-enhance-it , find the enhancement we did can't make the Delta mechanism works if only this new field gets changed in a record, and the change cannot be reflected on BW.
In order to make the Delta mechansim works, one option is to append the custom field into one of the LIS Communication Structure MCEKKO of 2LIS_02_ITM extraction structure and then write the enhancement code to this LIS Communication Structure. In this way, the custom field can be treated like standard field that whenever it gets changed, the Delta mechanism or the user exit will be triggered. The enhancement for this LIS Communication Struture is LEINS001.
Now we've got two problems when doing the above enhancements of the LIS Communication structure:
1. Maintain extraction structure problem in LBWE:
We added a custom field, e.g., called ZZZ in LIS Communication structure MCEKKO (Purchasing Document Header) by creating a new custom append structure and add the field ZZZ into it, then activate the new append structure, but get warning msg like "Field name DUMMY is reserved (Do not use structure as include in DB table)".
We do find a field called DUMMY in the structure MCEKKO. How to get rid of the warning msg and successfully activate the new custom append structure with the new field ZZZ?
You could say that we can ignore the warning msg, but why the new custom field appended can not be seen from the right side pool of the Maintain Extract Structure in LBWE? We need to make the new custom field shows up in the right side pool and then drag it over to the left side frame and to activate the extraction structure to change it. But now it doesn't show up in the right frame pool!
2. Refer to Sanyam's weblog
/people/sanyam.kapur/blog/2005/04/30/custom-fields-and-bw-extractors-making-a-mixed-marriage-work-part-ii, there is a sample code inside this article which tells us how the sample code looks like to write this LIS Communicaton structure enhancement to make the Delta mechanism works, below is the code we modified to suit our needs, but don't know if it would work?
DATA: i_t_ekko LIKE ekko   OCCURS 1 WITH HEADER LINE.
DATA: ebeln LIKE ekpo-ebeln,
      it_ekko TYPE TABLE OF ekko WITH HEADER LINE,
      old_val(50) TYPE c. "For storing the value from the Field Symbol
FIELD-SYMBOLS <fs> TYPE ANY TABLE.
CASE zeitp.
WHEN 'MA'.                            "When creating a purchase order
    MOVE '(SAPLEINS)T_EKKO[]' TO old_val.
    ASSIGN (old_val) TO <fs>.
    i_t_ekko[] = <fs>.
    LOOP AT xmcekko.
      ebeln = xmcekko-ebeln.
      IF xmcekko-supkz = '1'.            "Old Value ?
        SELECT SINGLE * FROM ekko INTO it_ekko WHERE ebeln = ebeln.
        xmcekko-ZZZ = it_ekko-ZZZ.
      ELSE.                              "New Value ?
        READ TABLE i_t_ekko WITH KEY ebeln = ebeln.
        xmcekko-ZZZ = i_t_ekko-ZZZ.
      ENDIF.
      MODIFY xmcekko.
    ENDLOOP.
EndCase.
Share your ideas and we will give you reward points!

Hello Kevin
We have exactly the same problem. Did you solve it? If you did, could you please tell us how you did it? We neither see our field in LBWE. Our field is a Z field from a Z table.
I hope you could help us. We just have this issue to finish our project.
Thanks a lot in advanced

Is there a way to enable delta for BPC transaction loads ?

Hi,
I am using Data Management package methodology to load data from BI to BPC.
Created Transformation file, created Data management package to download the data from Infoprovider and run the package to load the data from BI cube to BPC application.
everytime i run the package all the data from Infoprovider is read and will feed the application.So is there a way to delta enable the load from BI cube ?
does this method work for volumes ? what is the best practice for BPC NW to load the transaction data from BI to BPC.
thoughts appreciated.
Regards

Hi,
Thanks for the information.Your blog is really a savior.
I have followed the steps for automating the DM package.I have created prompt file based on the log file generated from the successful run of the package and i have entered all the required fields in UJD_TEST_PACKAGE programe along with Answer prompt file and i ran the package then some of the records were rejected with error "No authorization for members()on dimension()" and in the detaile log i saw "Cannot access the member (ACTUAL) of dimension (C_CATEGORY)" as the rejected records.
Other hand if i run the package directly in excel client > Run Data management package then the package runs succesfully without any errors.
I have checked the authorizations in Admin Client and i have full Member Access profile.Also checked C_Category is not a secured dimension.
what it has to do with C_CATEGORY dimension??
do we need any special authorisations while we run through the program? even in BI i have sap_all profile.
Pls help.

BPC 10.0 - Delta- Message for Prakash Darji

Hello,
Where can I get the delta featurs of BPC 10.0. I got some from the help portal but not the full list of delta features.
Also please elt me know when the OKP for BPC 10 will be available and any delta couses?
Thanks much.
Ravi THothadri

Hi Mathias,
Were you able to resolve the above issue. I have a similar requirement too.
Thanks
Rakesh

How Delta mechanism works for the datasource 0CRM_SALES_ACT_1 in CRM .

Hi all,
How Delta mechanism works for the datasource 0CRM_SALES_ACT_1 in CRM .
I mean timestamp, date etc? And how I can check that
Appreciate u r response.
Thanks
Pramod

Hi,
in your system, goto rsa1->tools->assign source system id....
regards
Siggi
PS: I strongly recommend to use the search functionality. This has been asked already a few times.

0FC_BP_ITEMS: ERP customizing and delta mechanism

Hi BI fans
I have two questions:
1.) The following link describes how to make the settings for delta enabling of datasource 0FC_BP_ITEMS:
http://help.sap.com/saphelp_nw70/helpdata/en/27/42073e774a4329b6dd6bab21eef613/frameset.htm
Prerequisites-
"...If you want to use the delta method, you first have to activate it in the Implementation Guide for Contract Accounts Receivable and Payable -> Integration Business Intelligence -> Maintain Central Settings in the clients of the OLTP system..."
But I cannot find the setting for "Maintain Centrall Settings" in the implementation guide!
Any idea from your side?
What I see are entries for:
Define Fields for the Extraction of Items
Define Grid for Grouping of Items
2.) What is the exact delta logic of this extractor (working through function module)?
Which fields are relevant for the delta logic?
Thanks
BEOplanet

Hi Andrea
First of all I activated the whole content (datasource, BW content, etc.).
Regarding the pseudo-delta on CPUDT I have designed a BEx variable on a DATS 8 time characteristic, e.g. 0NETDUEDATE. It is a BEx variable feeded by a customer exit, you will find a sample coding below. Furthermore an interval variable, mandatory input.
Screen for BEx variable properties:
Assign this BEx variable into your infopackage for intended use of pseudo-deltas, type OLAP-variable:
The sample coding below gives you an idea about our pseudo-delta mechanism, from 1st. of last month until sy-datum.
Data wa1 like line of e_t_range.
data d1 type d.
data fdate type d.
data fyear type d.
data ldate type d.
data fmonth type d.
case i_vnam.
when 'ZL2MTDY'. "BEx variable on 0NETDUEDATE or any other DATS 8 time characteristic
d1 = sy-datum.
fdate = d1 - 31.
fdate+6(2) = '01'.
ldate = sy-datum.
wa1-opt = 'BT'.
wa1-sign = 'I'.
wa1-low = fdate.
wa1-high = ldate.
append wa1 to e_t_range.
ENDCASE.

How to delete the data in update queue and delta queue for Queued delta?

Dear BWers,
How do i delete the delta queue and update queue data before i fill the setup tables for a extraction based on Queued delta. Please help.
Thanks
Raj

Hi Raj,
I think you need some ground work for the LO extraction same as others here. Please read the 3 blogs expliciltly created for LIS by Robert Negro.
/people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146
/people/sap.user72/blog/2004/12/23/logistic-cockpit-delta-mechanism--episode-two-v3-update-when-some-problems-can-occur
/people/sap.user72/blog/2005/01/19/logistic-cockpit-delta-mechanism--episode-three-the-new-update-methods
As well, the OSS 380078 would clear your doubts reagrding the the BW QUEUE mainatinance.
Please let me know if these material has been suffecient enough.
regarda,
raj

Episode 1: Weblog: Logistic Cockpit Delta Mechanism

Hi,
I just completed reading this document (Logistic Cockpit Delta Mechanism Episode 1) by Roberto and I will appreciate if you can clarify these for me:
1. The entire document(Episode 1) is about V3 Update, the Serializer but if the superior Update mode Unserialzed V3 discussed Episode 3 replaces the Serializer in earlier version, why the need to even learn about the Serializer? Any reaction to this comment?
2. On page 2 of this document, Roberto had a Fig and 2 paragraphs beneath it.
The para 2 discusses that V3 collective run is transferred to the BW delta queue from which data is retrieved by means of (delta) requests from BW.
But the para 1 suggests that with V3 Updates (the technology for collective update) is first collected in R3 Update table before it is transferred to the interface.
What interface was he referring to?
3. The two paragraphs appear to be explanations to the figure which shows a flow: Application Document to LIS Comm. Structure to Extract Structure to Central Delta Mgmt and to DataSource
Strangely, in the Fig, BW System Delta Queue did not appear. Where does this BW System Delta Queue come in the figure?
Also, is this entire flow obsolete because of the new Unserialized V3 Update discussed in Episode 3?
4. If I get it right, V1 Update, V2 Update and V3 Update are processes(or technologies?) being used in the Update Modes: Direct Delta, Queued Delta and Unseriazed V3 Update. Right?
So, regardless of the Update Mode(Direct Delta, Queued Delta and Unseriazed V3 Update) that we are discussing, one of the processes V1 Update, V2 Update and V3 Update will be in the underlining process.
Is this statement valid? Please correct me.
Thanks

Not getting any help yet ... I will review some old documents and if it is still not helpful, I will break the question up and re-post.

Delta Mechanism for BPC to BI

Similar Messages

Maybe you are looking for