Regarding the Delta Logic in the Report

Hi Abap gurus,
i have selection screen for 3 fields in one block called material, plant and extract date. if the user selects the extract date as todays date then data has to fetch the as per todays date.
i have two radio buttons on the selection screen for the second block. one is change material and second is all materials.
if user clicks on first radio button then only change material and aslo newly posted records for that date has to come.
how to build the logic for this? i have developed upto first part. data is coming fine. how to build the delta logic? i am working for the site receipts. guide me in this issue. if possible post the code.

Hi,
[here you find lots of sample reports, |http://help.sap.com/abapdocu_702/en/index.htm]
Hope it solves your question.
Regards,
Clemens

Similar Messages

Question about Note 886102 - Empty the delta queue of the connected SAP source systems

Dear expert
I'm doing the system refresh from ECC PRD to QAS using the hot backup of PRD
Before i start the database restore i was told to do the following step since this ECC has connection with one BW system
-----------------------Step -----------------------------
2.17 SAP note 886102 scenario C3
Empty the delta queue for all of the connected BW systems.
Execute all delta info packages two times on BW side, to clean up the delta queue in the source system. This is needed, because BDLS cannot rename the still available LUW-s in the qRFC queue.
----------------------Step-----------------------
But unfortunately i missed to execute this step
And the Q11 is now retoreing the backup of the database
My quesion
1. what will be bad consequence due to not execute this step? any way to makeup this error?
Best regards,

Hi Kate,
The probably issue which I could forsee is data getting wrongly updated into production if RFC connection from ECC to BW is not stopped.
Solution here could be to disable or deletethe RFC connections between ECC and BW before starting the SAP system at database level.
delete from sapr3.rfcdes where rfcdest = '<name>';
Once the system is up and running you can recreate them if required.
Also before starting SAP set the number of batch processes to 0 on the profile at OS level so that any released jobs don't start as soon as SAP is up.
Once the SAP system is up execute BDLS and change the logical system name.
Hope this helps.
Regards,
Deepak Kori

About the rules (logic) between the fan speed and the temperatures?

Hello All,
Well, I've had a bad experience with my MBP last week: my motherboard busted and had to replace it... Expensive part to replace!
After thinking about the reasons why it failed, my attention has been directed toward a possible motherboard overheating, which might have damaged the motherboard.
I've installed the iStat Pro widget and regularly monitor temperatures displayed vs. fan speed. I do get a bit nervous when I see a 84 oC CPU temperature and idle (2000 rpm) fan speeds. My GPU temperature is also sometimes in that range.
My questions are:
1) does anybody know the rules (logic) between the various temperatures (CPU, CPU heatsink, GPU, GPU heatsink, enclosure, HD, etc.) and the fan speeds?
2) other than with the fews apps out there, is there a way to customize the rules? Is there a text file or a plist file somewhere where I can change the rules?
Thanks!

If your idle speeds are 2000 rpm, you have one of the original Core Duo MBPs. For me, I see fans on my 17" CD MBP speeding up once temps get into the upper 70s °C.
Apps like smcFanControl allow you to alter the setpoints. Note that some users who installed smcFanControl, then uninstalled it, report symptoms like yours - namely, the fans remain at idle no matter how hight the temps get, until a thermal shutdown is triggered (somewhere close to 100 °C).

How to delete the delta queue in the ECC

Hi everyone!
After I tryed to save a new Infopackage and I have the error :
(Deltas already loaded for request REQU_41Q82WJLR9AZCE9ZMKQLVG3RG init. selection; no 2. init
Message no. RSM1071
Diagnosis
Deltas have already been loaded for the init. selection of request REQU_41Q82WJLR9AZCE9ZMKQLVG3RG. A second initialization is therefore not possible with these selection conditions.
Procedure
If you want to carry out a new initialization, you have to choose selections that do not overlap.
If you want to repeat the init. for the same selection, you have to delete the delta queue in the source system, and restart the delta process.
As the error says - Deltas have already been loaded for the init. selection.
Can you please give me some links/guids which describes how to delete the delta queue in the source system, and restart the delta process.
thank you, Ron

Hi,
Assuming as you need to the reinit for same selections.
in such case you need to delete old init.
how to delete init:
Go to your info pack screen, menu Scheduler--> initialization options for source system--> here you can see the existing init, select init(green) and delete it.
Later you can trigger your init info pack with selections.
Thanks

Why editing iview id break the delta link in the portal page?

For some reason, everytime I edit the iview id, the delta link in the page will be broken.
After I changed the iview id, the iview id that I added as delta link in portal page remain same, and seems like become a separate copy , rather than the original delta link.
This frustracted me as I have to remove the old iview , and add the new edited iview into the page again.
Why is this happen? (I am very sure I didn't accidentally add the iview as copy, instead of delta link)
By the way, I am in NW04s SP9.
Thanks for help.
Kent

Hi Kent,
> (I am very sure I didn't accidentally
> add the iview as copy, instead of delta link)
The wording "I am very sure" points to the fact that you didn't really check and re-try it?!
I just checked it on NW04 / SPS18 (which corresponds to SP09 on NW2004s) - and it works like a charme. The delta-link on the test page points to the new ID (as the ID-Change-Wizard announces it).
As I have no 2004s installation at hand, I would suggest really to re-check if you are really talking of a delta-link. If it really doesn't work on SP09 while it works on SP18 in parallel, you would have to open an OSS message. Anyhow, this really should behave analogously...
Hope it helps
Detlev

The delta update for the InfoCube ZCUBE is invalidated

Hi BI Experts,
I am working on BW 3.5.
For the datasource 2LIS_13_VDITM there were some requests(deltas) missing for 3 days. So I got all the documents there were missing or not updated in BW. I deleted the setup tables and filled them with the new document numbers.
I did a full repair request from the Infopackage level and the data got updated in ODS.
But the DM Status is missing for all the requests in the ODS.
And the data for the full repair request didnt get updated in the Cube and I got the following error:-
The delta update for the InfoCube ZCUBE is invalidated. The can be due to one of the following:
1. A request, which was already retrieved from the target system, was deleted from the InfoCube.
2. A request, which was not yet retrieved from the target system, was compressed in the InfoCube.
And the following delta was also not successfull.. How can I clear up this mess and ensure smooth flow of deltas. How can I set the DM status.
Thanks
Kumar

Thanks for your reply.
When I did a Full Repair Request on the ODS the data is in the New table and the DM status got reset(vanished). And the following day delta got failed( data for that request did not get updated in ODS and Cube)
How can we bring back the DM Status and make the deltas successfull.
Thanks
Kumar

How to view the code/logic for the built-in oracle functions

Hi,
How can we view the logic behind the oracle supplied built-in functions like LAST_DAY , MONTHS_BETWEEN etc.,
I tried to view the same using the sys.STANDARD package , the observations are given below
function LAST_DAY(RIGHT DATE) return DATE;
pragma BUILTIN('LAST_DAY',38, 12, 12); -- PEMS_DATE, DATE_LAST_DAY
pragma FIPSFLAG('LAST_DAY', 1450);
Regards
Lok

How can we view the logic behind the oracle supplied built-in functions like LAST_DAY , MONTHS_BETWEEN etc., You cannot. These built-ins, are 'built-in'.... As far as I know they are implemented in Oracle's kernel, as C code.

I placed a track of mine on the Global Chord track and when I remove the chords, Logic changes the pitch of all the notes in my project. How can I fix this?

I dragged and dropped an organ part onto the Chord Global Track in hopes of reading the chord symbols later. However, I continued recording and now that I want to replace a portion of that original track, I can't record over it because Logic keeps transposing every note I play based on the chords in the Global Track. Deleting these chords from the global track ruins every other track I've recorded since then. What can I do to get control back? Thanks so much.
I'm also seeing big translucent white lines all over the track I imported- those might be sustain pedal cues but I think they have to do with each new chord from the Global track...

9 hours is a lot of footage for a single Event. That is probably the hangup. Is there a way you could logically divide the event into multiple events? For example, if Martin Scorcese was filming the Woodstock concert, he could divide into Friday, Saturday, Sunday.
IMovie can use multiple events in a single project, and an event can be used in multiple projects.

The math/ logic of the Tachometer

I am find the rotations per second (rps) of a tachometer, but I am having trouble figuring out the logic behind it/ how to calculate it. I am using a pulley with 10 spokes, and all that I can think of right now is have the tachometer count every 0.25 seconds then divide it by 10 to make it a full rotation. I tried simply dividing the count found by the tachometer by the total time to find rps, but it doesn't seem correct because with that logic the program won't be giving me the current rps. I don't really need a full vi, but any help with the logic behind would be appreciated. I am using a daq assistant that is detecing the voltage of the tachometer and using a threshold to detect the spokes to count the rotations.
Thanks.

Sounds like you have an incremental optical rotational encoder and are trying to make the system of the encoder + your software act as a tachometer. A tachometer is a device that measures rotational speed, so the encoder on its own isn't actually a tachometer, although they are sometimes marketed that way if they are often used along with measurement hardware/software that makes the system behave as a tachometer.
Anyways, an encoder can only tell you the rotational position, not the rotational speed. An incremental encoder can only be watched to see when it changes position. Therefore, you won't ever be able to get a true current speed from it, but you can numerically differentiate the position with respect to time in order to get an estimation of the speed over the sampling period. Most commonly one does what you have described - count each spoke over a sampling period, such as 0.25 s, and then divide the number of counts by the sampling period to get speed. Shorter sampling times mean that you can sample much faster and have an estimated speed much closer to current speed; however, longer sampling allows better resolution.

ABAP Routine code for the below logic

Hello BW Experts ,
I need to write a complex ABAP routine in BW .
Following is the detail explaination .
Can anyone tell me the ABAP code for the below logic?
It would be a greate help as I am unable to do this
since last two days.
WBS Elements are maintained at IOS and Warranty levels in R/3 side.
The IOS WBS is a top level of WBS element and below that the Warranty WBS level.
The IOS and Warranty WBS elements can be differentiated by means of priority field.
When priority = i   , WBS Element is known as IOS Level WBS Element and
When priority = Y the WBS element is known as Warranty WBS element.
The Equipment Number is maintained compulsorily at IOS Level WBS elements only.
It is not maintained at Warranty WBS Element.
But the Cost is maintained at Warranty WBS Elements.
In BW I need all Warranty WBS ( priority = Y) along with their cost figures and Equipment Numbers.
But as the Equipment Number is not maintained compulsorily at Warranty WBS level we have asked to
Copy it from IOS WBS ( priority = i ) and assign it to Warranty WBS level ( priority = Y ).
So I have included the Equipment Number in the ODS and in update rules I need to write the routine for it as
per the above logic.
The Equipment Number is coming from Master data of WBS Element.
The WBS element master data we are loading in BW .
Also the same WBS Element transaction data is coming from the transaction data data source in BW.
Following fields / infoobjects and the table names in BW :
1. Equipment Number : /BIC/ZEQUIPMNT and table name /BIC/MZWBS_ELEM.
2. WBS Element       : ZWBS_ELEM is coming from transaction data data source as well as master data.
                                 In ODS update rules it is coming from transaction data data source Comm_structure-ZWBS_ELEM.
                                 Also we are loading separetly the master data for ZWBS_ELEM.
                                 The ZEQUIPMNT is an attribute of ZWBS_ELEM.
3. Priority                : PRIORITY     and table name /BIC/MZWBS_ELEM.
                                  The info object name for Priority is 0Priority but in master data table /BIC/MZWBS_ELEM
                                  the field name is    PRIORITY.
                                 When PRIORITY = ' i ' then    ZWBS_ELEM is at IOS Level
                                 When PRIORITY = ' y ' then ZWBS_ELEM is at Warranty Level.
4. ODS name : /BIC/AZCOST00 and same is table name active data table .
So please tell me the routine Code .
Best Regards ,
Amol.

Hi Dinaker,
Did you find any solution for this issue. I too have a similar requirement of pulling all the service orders for a specific Purchase Order in the BW report.
Thanks,
SAPBWI

Role upload does not change the delta links

Hi,
We are using the Role upload functionality in the portal to upload BW roles by selecting the "Convert roles to worksets" and "Overwrite existing content" options.
The newly created workset (corresponding to the uploaded role) is then copied and pasted as a delta link in another folder.
We upload the BW role again whenever some changes are made to the original BW role (such as addition/deletion of reports).
However, these changes are not getting reflected in the delta link (although the delta link dependency still exists).
Does delta link work only for manual deletion/addition of portal content and the changes do not filter through using a role upload with overwrite?
It is definitely not working for us using the role upload functionality and It seems that overwriting content using role upload does not impact the associated delta links.
Any solution/workaround to this issue would be greatly appreciated.
Regards,
Vibhu

Hi Vibhu,
> Good to hear from you after such a long time
Yeah, I didn't had that much time the last months, but at the moment, I'm trying to be back a bit
> We investigated the problem further and found that it is only the deletions to a
> BW role in the backend that do not get reflected in the delta link.
>
> The additions work fine.
> It is defintely a bug.
So it's up to SAP to fix it - and you could mark the thread as closed?!
Best regards
Detlev

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

Domain logic in the database

Hi.
Don't know if this fits the topic, but I need some feedback.
My company is relativly new to J2EE. We are currently moving our existing application portfolio to J2EE from a two tier client-server architecture developed on Centura and Oracle. Our data model is pretty strong, and much of the domain logic of the application has been moved to the database over the course of the last few years, so there is quite a bit of PL/SQL code in there.
Now there is a heated discussion internally about the validity of making the transition to J2EE with the databases intact and reusing this PL/SQL based domain logic. We have individual proclaiming that every operation on data is domain logic and all domain logic should reside on the application server with J2EE.
I personally feel that J2EE fully allows for keeping domain logic in the database, and that one should always apply the principle of the "best technology for the job" in each case. For instance data intensive transformations and calculations belong on the database.
Please provide me with some support to use in our internal discussions as I feel overpowered by the "darker forces", and would very much like to know how the industry at large feels about this issue.
Regards,
Jorn Olmheim
Senior Java Developer

Hey Jorn.
Sorry, but I would have to side with the dark forces you mention. In moving to an 'n' tier architecture, the Business logic should be contained in server side components, not the database. This will allow re-use of componenents across other applications(think Enterprise here), as well as providing a layer of abstraction for accessing the database.
Also, What if you change db vendors? All your pl/sql code will need to be ported. Very messy.

What are the steps we follow while customizing the Deltas in Bw side

Hi All,
I had a query regarding the customization of deltas in BW side after replicating from R/3.
thanks and regards
kabir

Hi,
In order to customize the deltas for the different DS are depends upon the type of the DS you are using for ex. if it is from LO cockpit then you need to take care of
the delta setups but you can do the setting for Jobs.
In case if you have any generic DS you can customize the delta at RSO2 transaction by selecting the one of the delta feild from the DS..
Hope this helps..
assign points if useful.
Cheers,
Pattan.

Delta support for the Generic extracter

Hello Roberto,
I have created the generic extractor (view-VBRK,VBRP) and it is working fine now i want to create the delta support for the extractor at R/3 side , please guide for the same .
Regards,
Milind

Hi Milind,
Under R/3, go to TCODE <b>RSO2</b>, you are presented with 3 options "Transaction Data", "Master Data", "Text". You choose which is the type of Generic Extractor you want.
There is a button labeled "<b>DELTA</b>" on the upper left corner of the screen. You indicate there which of the fields in your Extract Structure will be used as DELTA indicator or reference point.
You can choose either via Numeric Pointer, Timestamp, Calendar Day.
Hope that helps...
Do award some points if helpful...
--Jkyle

Regarding the Delta Logic in the Report

Similar Messages

Maybe you are looking for