Delta upload for total fisl extractor

Hello,
Its said that the BALANCE field in the transfer structure is not supplied with data during Delta upload .
Would you know the reason for this?
I assume this is for the totals extractor only since balance is not available otherwise.
Regards
Pascal

Because the change record updates the movements not the balance
And you can back post - ie post to a period already gone - so if yuu wanted balance to be provided you would then have to change every periods balance b/f in the extractor from the backposted period onwards
Easiest way to do it - do it in the cube (as per the OSS note) and let compression deal with getting rid of the extra records created

Similar Messages

Delta Upload for Flat File

Hello Everyone
i am srikanth. i would like to know wheather do we have a facility for Delta Upload for flat file. If yes can u please give me the steps.
thanks in advance
srikanth

Hi Sabrina...thank you for ur help...i did load the data from cube to ods
steps.
1. i generated export data source on the cube
2. i found the name of the cube with prefix 8<infocube name> in the infosource under DM application component.
3. there are already communication structure and transfer rules activated but when i am creating update rules for the ods..i am getting the message 0recordmode missing in the infosource.
4. so i went to infosource and added 0recordmode in communication structure and activated but the transfer rules in yellow colour..there was no object assigned to 0recordmode but still i activated.
5.again i went to ods and created update rules and activated (tis time i didnt get any message about 0recordmode).
6.i created infopackage and loaded.
a)Now my question is without green signal in the transfer rule how data populated into the ods and in your answer you mentioned to create communication structure and transfer rules where in i didnt do anything.
b) will i b facing any problem if i keep loading the data into the ods from cube (in yellow signal) ..is it a correct procedure..plz correct me..thanks in advance

Delta upload for generic data sources.

Hai All,
I tried as per SAP online document , but still i am not getting the result i.e delta upload from the BW side. Here i explained everything what i did.
In R/3
1. I have created a table with 3 fields SNO, SNAME, DOB
2. Then i created some entries in that table.
3. With Tr Code RSO2 i created one data source. Here i took Master Attribute Datasource
4. In generic delta i took the Generic field as DOB. and Time stamp and upper limit 10 sec.
In BW side
1. I have replicated the data sources under application compone in which i have creatred in R/3..
2. Then i activated that data source and created infopackage for that.
3. in the selection i have specified 01.01.1900 to 01.01.9999
4. First i made Full Update then i get all the records from R/3.
5. In R/3 i have created 2 more entries.
6. In Infopackage UPDATE Tab i have selected the Initilize Delta Process ( Initialization with Data Transfer).
For this i am getting the error message as follows.
Error message from the source system
Diagnosis
An error occurred in the source system.
System Response
Caller 09 contains an error message.
Further analysis:
The error occurred in Extractor .
Refer to the error message.
Procedure
How you remove the error depends on the error message.
Note
If the source system is a Client Workstation, then it is possible that the file that you wanted to load was being edited at the time of the data request. Make sure that the file is in the specified directory, that it is not being processed at the moment, and restart the request.
Here i closed the all things in R/3 as per the note mentioned above. Still it is giving the error message.
If i select the Intilization Delta Process( Intilization with out Data Transfer) then i am getting the option Delta Update . I selected this Delta update and scheduled but no data is coming.
Please help.
Regards
Prashanth K

Hai Sachin,
I am getting the problem at PSA only. Actually that is connected to ODS Object only. Until unless we don't get the delta data into PSA we can't proceed futher. So please help. I am working on NW 2004S.
Regards
Prashanth K

Delta upload for flat file extraction

Hello everyone,
Is it possible to initialize delta update for a flat file extraction, If yes please explain how to do that??

Hi Norton,
For a Flat file data source, the upload will be always FULL.
Please refer to following doc:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a0b3f0e2-832d-2c10-1ca9-d909ca40b54e?QuickLink=index&overridelayout=true&43581033152710 if you need to to extract delta records from Flat file. We can write routine at infopackage level.
Regards,
Harish.

Delta upload for DB connect.

hi all,
i have a small querry- i have to load data in a cube every month. my data source is a SQL table.
i will load data using DBCONNECT.
do we have delta update option for DBCONNECT, because in my info package i can see only "Full upload" option.
if delta upload is available, then how do i get this option in info package.
thanks a lot.
Regards,
Shruti

Hi Shruti,
In infopackage, in the tab for data selection, we can see some fields for selection. On those fields - we can write an abap code (routine) which will have some logic to find the last update date and then populate the selection field based upon this last update date + 1. So the info package will dynamically fetch the required records.
Regards,
Amit Mittal.

Delta Upload for Customized DataSource

Hello,
I created a Customized DataSource with Full Upload and replicated DS in BW ,now i want to creat Dalta Upload for the same Data Source is it possible can i do ,is there any method or settings to be done to get Delta upload update..
I hope my thread is understandable....
ifnot get back ....!
Thanks

Hi Bhanu,
What is the Safety Upper & Lower limits you have given for your Generic Delta(RSO2 trans). That also matters.
Give Safety Upper limit as 0 & Lower Limit as 1, Replicate the DS once in BW & then try to load Delta.
If possible Delete the Init--> Load the Init again & then try loading Delta after changing the Safety limits & loading INIT.
Hope it helps you!
Regards,
Pavan

Special Ledger-does delta datasource for totals table work at 4.7

Has anyone successfully used deltas on special ledger total tables at 4.7c ?
As the totals table doesnt have a timestamp I want to understand how this works?
heres the help line that appears to suggest it should work:
http://help.sap.com/saphelp_nw04/helpdata/en/f3/3a69377f2b8032e10000009b38f8cf/content.htm
Thank you in Advance.
Tony

Hi,
I hope you have written the codes in R/3 side.And whenever the Collection Specialist Master record is changed for a particular Customer, all the newly generated Accounting Document show the current Collection specialist but the already existing Accounting Document in BW will not converted to the current Collection Specialist since the data in BW is old data and no logic is written to convert the same.
Try to incorporate the logic to convert in BW also.
I could suggest is whenever there is change in Collection Specialist Master record , try to trigger a delat record generation that updates the old accounting doc withnew master in the delta load.
Ramesh

Missing delta records for the Z extractor

Hi,
I have created a Z extractor for the table BUT050 in CRM. I have created a function module and have included the delta logic on CRDAT which is the created date, CRTIM - created time, CHDAT - change date, CHTIM - Change time. I have initialed the delta and started doing the delta loads. I found that there are few missing records in the extractor when compared to the table. I'm attaching my code below.Can anyone please look into it and tell me what the issue is.
Text removed by moderator
Thanks
FUNCTION Z_BI_CC_BUT050.
*"*"Local Interface:
*" IMPORTING
*"     VALUE(I_REQUNR) TYPE SRSC_S_IF_SIMPLE-REQUNR
*"     VALUE(I_DSOURCE) TYPE SRSC_S_IF_SIMPLE-DSOURCE OPTIONAL
*"     VALUE(I_MAXSIZE) TYPE SRSC_S_IF_SIMPLE-MAXSIZE OPTIONAL
*"     VALUE(I_INITFLAG) TYPE SRSC_S_IF_SIMPLE-INITFLAG OPTIONAL
*"     VALUE(I_READ_ONLY) TYPE SRSC_S_IF_SIMPLE-READONLY OPTIONAL
*"     VALUE(I_REMOTE_CALL) TYPE SBIWA_FLAG DEFAULT SBIWA_C_FLAG_OFF
*" TABLES
*"      I_T_SELECT TYPE SRSC_S_IF_SIMPLE-T_SELECT OPTIONAL
*"      I_T_FIELDS TYPE SRSC_S_IF_SIMPLE-T_FIELDS OPTIONAL
*"      E_T_DATA STRUCTURE ZBI_BUT050 OPTIONAL
*" EXCEPTIONS
*"      NO_MORE_DATA
*"      ERROR_PASSED_TO_MESS_HANDLER
* Auxiliary Selection criteria structure
   DATA: l_s_select TYPE srsc_s_select.
* Maximum number of lines for DB table
   STATICS: s_s_if TYPE srsc_s_if_simple,
* counter
           s_counter_datapakid LIKE sy-tabix,
* cursor
           s_cursor TYPE cursor.
* Select ranges
   RANGES: l_r_RELNR FOR ZBI_BUT050-RELNR,
           l_r_PARTNER1 FOR ZBI_BUT050-PARTNER1,
           l_r_PARTNER2 FOR ZBI_BUT050-PARTNER2,
           l_r_DATE_TO FOR ZBI_BUT050-DATE_TO,
           l_r_ZZTMSTMP FOR ZBI_BUT050-ZZTMSTMP.
   DATA : startdate LIKE sy-datum,
          starttime LIKE sy-uzeit,
          enddate LIKE sy-datum,
          endtime LIKE sy-uzeit,
          tstamp LIKE tzonref-tstamps,
          timezone type TZONREF-TZONE.
   RANGES: l_r_CRDAT FOR ZBI_BUT050-CRDAT,
                   l_r_CRTIM FOR ZBI_BUT050-CRTIM.
* Initialization mode (first call by SAPI) or data transfer mode
* (following calls) ?
   IF i_initflag = sbiwa_c_flag_on.
* Initialization: check input parameters
*                 buffer input parameters
*                 prepare data selection
* Check DataSource validity
     CASE i_dsource.
       WHEN 'ZCC_MA_BUT050'.
       WHEN OTHERS.
         IF 1 = 2. MESSAGE e009(r3). ENDIF.
* this is a typical log call. Please write every error message like this
         log_write 'E'                  "message type
                   'R3'                 "message class
                   '009'                "message number
                   i_dsource   "message variable 1
                   ' '.                 "message variable 2
         RAISE error_passed_to_mess_handler.
     ENDCASE.
     APPEND LINES OF i_t_select TO s_s_if-t_select.
* Fill parameter buffer for data extraction calls
     s_s_if-requnr    = i_requnr.
     s_s_if-dsource = i_dsource.
     s_s_if-maxsize   = i_maxsize.
* Fill field list table for an optimized select statement
* (in case that there is no 1:1 relation between InfoSource fields
* and database table fields this may be far from beeing trivial)
     APPEND LINES OF i_t_fields TO s_s_if-t_fields.
   ELSE.                 "Initialization mode or data extraction ?
* Data transfer: First Call      OPEN CURSOR + FETCH
*                Following Calls FETCH only
* First data package -> OPEN CURSOR
     IF s_counter_datapakid = 0.
* Fill range tables BW will only pass down simple selection criteria
* of the type SIGN = 'I' and OPTION = 'EQ' or OPTION = 'BT'.
       LOOP AT s_s_if-t_select INTO l_s_select WHERE fieldnm = 'RELNR'.
         MOVE-CORRESPONDING l_s_select TO l_r_RELNR.
         APPEND l_r_RELNR.
       ENDLOOP.
      LOOP AT s_s_if-t_select INTO l_s_select WHERE fieldnm = 'PARTNER1'.
         MOVE-CORRESPONDING l_s_select TO l_r_PARTNER1.
         APPEND l_r_PARTNER1.
       ENDLOOP.
       LOOP AT s_s_if-t_select INTO l_s_select WHERE fieldnm = 'PARTNER2'.
         MOVE-CORRESPONDING l_s_select TO l_r_PARTNER2.
         APPEND l_r_PARTNER2.
       ENDLOOP.
       LOOP AT s_s_if-t_select INTO l_s_select WHERE fieldnm = 'DATE_TO'.
         MOVE-CORRESPONDING l_s_select TO l_r_DATE_TO.
         APPEND l_r_DATE_TO.
       ENDLOOP.
* Timestamp is delivered as a selection criterion.
* Split the timestamp into date and time
      LOOP AT s_s_if-t_select INTO l_s_select WHERE fieldnm = 'ZZTMSTMP'.
         tstamp = l_s_select-low.
         timezone = 'EST'.
         CONVERT TIME STAMP tstamp TIME ZONE timezone
          INTO DATE startdate TIME starttime.
         tstamp = l_s_select-high.
         CONVERT TIME STAMP tstamp TIME ZONE timezone
          INTO DATE enddate TIME endtime.
         l_r_CRDAT-low = startdate.
         l_r_CRDAT-sign = l_s_select-sign.
         l_r_CRDAT-option = l_s_select-option.
         l_r_CRDAT-high = enddate.
         APPEND l_r_CRDAT.
         l_r_CRTIM-low = starttime.
         l_r_CRTIM-sign = l_s_select-sign.
         l_r_CRTIM-option = l_s_select-option.
         l_r_CRTIM-high = endtime.
         APPEND l_r_CRTIM.
       ENDLOOP.
* Determine number of database records to be read per FETCH statement
* from input parameter I_MAXSIZE. If there is a one to one relation
* between DataSource table lines and database entries, this is trivial.
* In other cases, it may be impossible and some estimated value has to
* be determined.
       OPEN CURSOR WITH HOLD s_cursor FOR
* Use the l_r_erdat and l_r_erfzeit for both creation and change selections
* This way we can pick up both the creations and changes in a given time period.
       SELECT * FROM BUT050
              WHERE RELNR IN l_r_RELNR
               AND PARTNER1 IN l_r_PARTNER1
               AND PARTNER2 IN l_r_PARTNER2
               AND DATE_TO IN l_r_DATE_TO
               AND ( CRDAT >= startdate AND ( CRTIM >= starttime OR ( CRDAT <= enddate AND CRTIM <= endtime ) ) )
               OR ( CHDAT >= startdate AND ( CHTIM >= starttime OR ( CHDAT <= enddate AND CHTIM <= endtime ) ) ).
     ENDIF.
     "First data package ?
* Fetch records into interface table.
*   named E_T_'Name of extract structure'.
     FETCH NEXT CURSOR s_cursor
                APPENDING CORRESPONDING FIELDS
                OF TABLE e_t_data
                PACKAGE SIZE s_s_if-maxsize.
     IF sy-subrc <> 0.
       CLOSE CURSOR s_cursor.
       RAISE no_more_data.
     ENDIF.
     s_counter_datapakid = s_counter_datapakid + 1.
   ENDIF.              "Initialization mode or data extraction ?
ENDFUNCTION.
Message was edited by: Matthew Billingham

Hi,
As per my knowledge you want load particular period of data try repair request may issue solve.
Regards
Sivaraju

No Delta records for SRM Confirmations (Extractor - 0BBP_TD_CONF_1)

Hi,
We are getting zero records for delta update from 0BBP_TD_CONF_1 after successfull init w/data.
Delta queue is empty, and no records for delta extraction in RSA3 too in source system. Its sure that data ( changes/new confimations) is entered, but some how they are not updated to BW delta queue.
I saw couple of threads with same issue, but no solutions. If any one has any ideas/suggestions/solutions, please let me know.
Thanks,
S

Hi,
Did you checked the User exit wether you are doing any manupulations or selections.
since before populating the delta queue we can have our own code to populate the data.
So better check any such code is there in user exit.
Regards,
aanand

Failure in Delta Upload

friends,
       we have delta upload for our purchasing data to BW. from the infopackages the data is Updated to ODS- 0PUR_O01, which provides data to Infocubes - 0PUR_C08 and 0PUR_C07 and ODS 0PUR_O02 ( which in turn provides data to infocube - 0PUR_C09 ). 3 days back one request in ODS 0PUR_O01 went into error status. WAfter marking the request "RED" it was deleted from the ODS, but since the request had the same PSA_ID as that of an another successful (GREEN) request in the same ODS with data mart status ticked, this request also got deleted by mistake, as a result the datamart status for all the request in the ODS (0PUR_O01) is missing, from this time onwards the subsequent data updates to infocubes 0PUR_C08 and 0PUR_C07 and ODS 0PUR_O02 (also to Infocube 0PUR_C09 ) are finishing in Error status. we have deleted all the requests (after marking them "RED") for previous three days from the data targets ( infocubes 0PUR_C08, 0PUR_C07, and 0PUR_C09 and ODS 0PUR_O02). we also have deleted the correposnding requests from ODS 0PUR_O01 (after marking them "RED").Now when we are trying to reconstruct the requests at 0PUR_O01, it goes successful, but when we try to activate the requests into subsequent data targets ( back ground job BI_ODSA* ) the job fails with a short dump and the following error message.
Error Message:-
Check Load from InfoSource 80PUR_O01 , Packet Delta Package for Update by ODS 0PUR_O01
Please execute the mail for additional information.
Error message from the source system
Diagnosis
An error occurred in the source system.
System response
Caller 09 contains an error message.
Further analysis:
The error occurred in Extractor .
Refer to the error message.
Procedure
How you remove the error depends on the error message.
Note
If the source system is a Client Workstation, then it is possible that the file that you wanted to load was being edited at the time of the data request. Make sure that the file is in the specified directory, that it is not being processed at the moment, and restart the request.
Short Dump:-
What happened?
   The current application program detected a situation which really
   should not occur. Therefore, a termination with a short dump was
   triggered on purpose by the key word MESSAGE (type X).
What can you do?
   Print out the error message (using the "Print" function)
   and make a note of the actions and input that caused the
   error.
   To resolve the problem, contact your SAP system administrator.
   You can use transaction ST22 (ABAP Dump Analysis) to view and administer
    termination messages, especially those beyond their normal deletion
   date.
   is especially useful if you want to keep a particular message.
Error analysis
   Short text of error message:
   Request 0000017556 in ODS 0PUR_O02 must have QM status green before it i
   s activated
   Technical information about the message:
   Message classe...... "RSM1"
   Number.............. 110
   Variable 1.......... 0000017556
   Variable 2.......... "0PUR_O02"
   Variable 3.......... " "
   Variable 4.......... " "
   Variable 3.......... " "
   Variable 4.......... " "
How to correct the error
   Probably the only way to eliminate the error is to correct the program.
   You may able to find an interim solution to the problem
   in the SAP note system. If you have access to the note system yourself,
   use the following search criteria:
   "MESSAGE_TYPE_X" C
   "SAPLRSATREE" or "LRSATREEF28"
   "RSATREE_START_ACTIVATION"
   If you cannot solve the problem yourself and you wish to send
   an error message to SAP, include the following documents:
Please suggest a solution for this problem and to bring back the missing data mart statuses of the all the requests in ODS 0PUR_O01.

hi olivier,
   the said request is in ODS 0PUR_O02. will try to explain the scenario:
the data flow in this regard is:
PSA ->          Infopackages                       -
> *
          (2LIS_02_SGR, 2LIS_02_ITM etc.)
*-----> ODS (OPUR_O01) --> Infocube (OPUR_C07)
*-----> ODS (OPUR_O01) --> Infocube (OPUR_C08)
*-----> ODS (OPUR_O01) --> ODS (0PUR_O02) -
> ***
----> Infocube (OPUR_C09)
now when we try to reconstruct a request in ODS OPUR_O01, the a new request is created (Requid- 175429) with green status but without datamart icon. Now when this request is activated in 0PUR_O01 and since "Activate ODS object Data automatically and   Update Data Targets from ODS object automatically" is checked in 0PUR_O01, new requests are created in ODS 0PUR_O02 (Requid- 17566)and infocubes OPUR_C07(Requid- 17566) and OPUR_C08(Requid- 17566). All these requests are with 0 data and PSA_ID are also 0. and then the above short dump and error comes in.. one thing to note here is
"Activate ODS object Data automatically and   Update Data Targets from ODS object automatically" option is also checked in ODS 0PUR_O02.
Hope this clears up everything..
Edited by: Nivin Joseph Varkey on Jan 14, 2008 7:20 AM

Delta update for spend analysis fails

Hi,
I am using Spend Analysis in BI 7.0. The delta upload for this gives 0 records.
I have checked RSA7. The data source shows 0 records even though new records are available in the line item table. Delta field is <b>TIMESTAMP</b>.
The data source is delta enabled but still RSA3 does not allow Delta extraction test.
Can anybody tell me how delta is loaded for spend analysis data and why RSA7 is not showing any records.
This is a very urgent issue. Points will be rewarded for helpful answers.

hi venkat,
are you able to solve the problem? I got a similar problem like yours, not really familiar with delta updates with generic extractor.
If solved already can you share the solution? I am stuck after init delta, a little research indicate there's some V1/V2/V3 updates that i need to set in R/3 and also delta queue..
Thanks...
Heng Meng

Delta upload in different times and targets

Dear BW Gurus,
I have to fill a Master Data table with a delta (for performance reasons) from an ODS object, and later fill an InfoCube with the same delta from the same ODS Object. This two step approach is necessary because the Cube uses the Master Data filled in the first step - so I cannot do the two uploads within the same InfoPackage.
My approach was the following in a Process Chain:
1. Fill and activate "source ODS"
2. Load request from "source ODS" to PSA only
3. Update Material Master from PSA using "Read PSA and Update Data Target" process with the variant setting the PSA table and the Master Data InfoObject as Data Target.
4. Run "Attribute Change" process for the Master Data IO
5. Update InfoCube from the same PSA that was used for the Master Data InfoObject. This is also a "Read PSA and Update Data Target" process with the variant setting the same PSA table as before and now the InfoCube as the Data Target.
To me this seemed logical but when I run the Process Chain I got the following error message at point 3 (update Master Data from PSA): "No request for posting found in the variant".
This appears strange to me because if I specified the request, it would only work for the first upload and not for all the others.
Can anyone please help me how to overcome this issue of Delta upload in different times and targets?
Thanks in advance,
Attila

Gopi,
If I create two delta InfoPackages, the first one clears the delta queue, so the second InfoPackage won't find any data. This is unfortunately not the way to do...
Srini,
Your proposal is quite original - if I upload the same ODS with its data (amended by the date field) that would in fact generate a new delta for the same ODS.
However, in the meantime a more simple idea came up in our BW team, inspired by your proposal. For the uploading of the Master Data I now don't use the delta functionality of the ODS export Data Source, but instead I set up a full upload filtered for the actual date. This ensures the good performance of Master Data load (load time will not increase with time) and also we will have all recent Master Data uploaded from the ODS because that load is in the same Process Chain where the "Source ODS" is updated. Later in the same Process Chain I simply start the delta upload for the Cube.
Thanks a lot for all your help.
Attila
P.s. I will be out of office for until 24th July.

Is it possible to run delta upload in both servers simultaneously?

Dear SAP gurus,
We already have a running BW server version 3.0 B,Now we are planning to use another server having BI 7.0.Both thease servers needs to extract data from a single R/3 server.We have delta upload for some master info objects,Is it possible to run delta upload in both servers simultaneously?
If so,pls. let me know how to implement the same.
Regards,
Anuradha

HI
As said in the previous post u can run the delta in both the systems. Follow the same procedure how u do while u create a new infrastructure and do init without data transfer and do the delta loads.
correct me if i am wrong
Khaja

RSA7 shows zero records for delta upload of 2LIS_03_BF Datasource

Dear Professionals,
I am having constant issues with inventory management DataSource (2LIS_03_BF). I scheduled delta upload in r3 production using LBWE, keeping in mind that in LBWE there is no options for posting dates, ETC... In RSA3, there are records, but when i check RSA7, it is showing 0 records. What could be the problem. Do i need to do anything/activation anywhere in LBWE or RSA7 to see the records. Please advise.

Hi,
Normally there should be a collective run which transfers data from the application-specific queues to the BW delta queue (RSA7), just like this workflow:
MCEX03 queue==> RMBWV03 (Collective run job) ==> RSA7-Delta queue => BW
It is necessary to schedule the job control regularly - see point 3 of SAP Note 505700.
Check also these SAP Notes:
869628     Constant WAITUPDA in SMQ1 and performance optimization
728687     Delta queued: No data in RSA7
527481     tRFC or qRFC calls are not processed
739863    Repairing data in BW
Rgds,
Colum

Delta Upload Problem For 0PM_CO1 Cube

Hi Friends,
I got a problem for Delta Upload.In RSA3 data is O.K and In RSA7 also data is O.k.but the problem is with Delta Upload new records are not comming,i did First initialization,thst is o.k,but why Delta Upload is not comming.
please give me help about this .
Thanks in Advance.

Hi Praksh,
this is chava,can you send your mobile no. to my mail id.
Mail:[email protected]
Message was edited by: CHAVA CHAVA

Delta upload for total fisl extractor

Similar Messages

Maybe you are looking for