Delta Gap in LO

Hi Experts,
Can anybody tell me about what is Delta Gap in LO?
and also two more doubts, 1. Where to maintain currency conversations?
2. Where to create currency types?
Thanx in Advance,
Balaji Reddy

Hi dear,
better to open different threads when subjects are so different...
Anyway,
about currency conversion, look here:
http://help.sap.com/saphelp_nw2004s/helpdata/en/ec/076f3b6c980c3be10000000a11402f/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/80/1a6813e07211d2acb80000e829fbfe/content.htm
About "delta gap" I don't know what you exactly want to mean...could you please give us some more detail ?
Hope it helps!
Bye,
Roberto

Similar Messages

Get datetime delta gaps

Finding datetime gaps:
we have a table with cars working from to dates:
rec   car   DateFrom       DateTo
1   11   2008-10-28 00:00:00   2008-11-05 23:59:59
2   11   2008-11-06 00:00:00   2008-11-08 23:00:00
3   11   2008-11-09 00:00:00   2008-11-05 23:59:59
4   22   2008-10-28 00:00:00   2008-10-29 20:00:00
5   22   2008-10-31 00:00:00   2008-11-05 23:59:59
result I'm lookin for is finding dates and delta time a car is not working:
car   gapFrom        gapTo           gapDelta[h]
11   2008-11-08 23:00:00   2008-11-09 00:00:00   1    (in hours)
22   2008-10-29 20:00:00   2008-10-31 00:00:00   28

Hi b_blase,
Please see the below code to retrieve datetime delta gaps.
CREATE TABLE yourTable
rec INT,
car INT,
dateFrom DATETIME,
dateTo DATETIME
INSERT INTO yourTable VALUES(1,11,'2008-10-28 00:00:00','2008-11-06 00:00:00'),
(2,11,'2008-11-06 00:00:00','2008-11-08 23:00:00'),
(3,11,'2008-11-09 00:00:00','2008-11-10 00:00:00'),
(4,11,'2008-11-10 11:37:00','2008-11-11 00:00:00'),
(5,22,'2008-10-28 00:00:00','2008-10-29 20:00:00'),
(6,22,'2008-10-31 00:00:00','2008-11-05 00:00:00'),
(7,22,'2008-11-07 00:00:00','2008-11-11 00:00:00');
;WITH CTE AS
SELECT *,ROW_NUMBER() OVER(PARTITION BY car ORDER BY dateFrom) AS rn FROM yourTable
CTE2 AS
SELECT c1.car car,c2.dateTo gapFrom, c1.dateFrom gapTo
FROM CTE c1 LEFT JOIN CTE c2
ON c1.rn=c2.rn+1 AND c1.car=c2.car
WHERE c1.dateFrom <> c2.dateTo
SELECT *,CAST(ROUND(DATEDIFF(MINUTE,gapFrom,gapTo)/60.0,2) AS NUMERIC(20,1)) gapDelta FROM CTE2 ORDER BY car,gapTo;
DROP TABLE yourTable;
I just made a little modification on the dateTo column so that the
dateTo equaling to the dateFrom of next record can be identified as no gap. If you still prefer the dateTo valuing like ‘2008-11-06 23:59:59‘ as it was, you just modify the WHERE clause as below.
WHERE DATEDIFF(MINUTE,c2.dateTo,c1.dateFrom) <> 1
If you have any question, feel free to let me know.
Best regards,
Eric Zhang

Gaps while playing AC3 Sound through SPDIF on KT6-Delta FISR

Hi everybody,
I'm one of those lucky guys with a KT6-Delta FISR Board :D equipped with the C-Media 9739A OnBoard Soundchip and a S-Bracket from my old K7T266 Pro2 ( MS-6380 ) mainboard.
It works great. The only problem is, when I try to play
AC3-encoded Sound directly through SPDIF there are irregular gaps ( length = about half a second ) where no signal reaches my hifi system. Playing normal PCM-encoded Sound works fine, just AC3 is the problem.
I have the latest driver, the latest bios, the latest chipset driver from via & the latest Windows XP Prof. updates. :]
I also tried different AC3 Filters ( from WinFast DVD, PowerDVD and the free ac3filter ) and a fresh WinXP Prof. installation. But nothing worked.
Always these stupid gaps. ;(
The mysterious thing is: With my old MB and an extra pci soundcard with C-Media CMI8378 Chipset and optical SPDIF it works great.
Yeah, I know I could use the old one, but the KT6 OnBoard chip has some benefits :]
Some information about my system:
- Athlon XP1800@1800(133x11,5) ( Palomino Core )
- Cooling: Copper Silent 2 TC by Arctic Cooling
- Enermax power supply ( +3,3V/35A, +5V/44A, +12V/15A)
- NVidia GeForce TI4600 from Leadtek ( i forgot: latest driver )
- Western Digital WD1200JB HDD (120GB,7200 RPM,8MB Cache )
- RAM: 256 MB PC2100, CL2 by Apacer
- Home-theatre system: Sony STR-KSL5 ( dts,dolby digital/pro logic II, digital cinema sound, 2x optical digital input, 1x coaxial digital input )
- Connection between PC and hifi system: optical
Has anyone the same problem or maybe a solution or a suggestion ? Would be nice then, when he or she posts it here )

A little mistake: The S-Bracket is from the KT4 Ultra FISR - Board ( MS-6590 ), sorry for that
@osnavi:
I don't know whether it's okay or not. I just thought, the S-Bracket is just a cable extension of the onboard pin-connector ( means: there are no necessary parts in it - except the current-optical coverter for optical out - and the whole functionality is on the board ).
Have you any idea, whether there's another S-Bracket for the KT6 series ?
@maesus:
I've tested all latest available drivers ( both from www.cmedia.com.tw and from MSI via LiveUpdate3 ). All of them produced this gap.
Both drivers where tested with Coax out and Optical out.
I also tried to increase the PCI Latency in BIOS to give the sound chip more time for using the bus and therefore more time to transfer data. It didn't work, too.
I will now try the following:
- decreasing the FSB to 100 MHz ( just an idea , maybe it helps )
- installing a generic ac'97 audio driver (in case something like this exists )
- well, bang my head on my hifi system
Any suggestions are still welcomed )

Data transfer (Export & Import) of Delta Queue between two system.

We are planning to implement the following senario for a certain R/3 and BW system.
1. Implement storage snap shot copy solution for R/3 database and create replicated system of production R/3 every day in order to avoid load of production R/3 to BW directly. That is to say, we will extract business data from the replicated R/3 system and forward to BW.
2. We need to utilize Delta Queue function in order to feed the only gap data between production R/3 and BW. but as stated in 1. the source data will be replicated from the production R/3 every day and so we could not keep the Delta Queue data in R/3.
3. So, we are examining the following method in order to keep the Delta Data in the replicated R/3 system. i,e after feeding business data from the replicated R/3 to BW, we will extract the following Delta Queue table and keep it.
- TRFCQOUT (Client Dependent pointer table per queue name and destination.
- ARFCSSTATE: Likn between TRFCQOUT and ARFCSDARA
- ARFCSDATA: Compressed data for tRFC/qRFC
And then, next day, after replicating R/3 system, we will import those Delta data to the replicated R/3 system before stating extract business data and feed to BW.
Is the such method realistic? if not, is there any alternative?
Please advice!
Best regards,

I found the following document and this is one that I want to inplement.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5d51aa90-0201-0010-749e-d6b993c7a0d6
Additionaly, I want to execute this senario repeatedly. Does someone have experience such implementation?
Eguchi.

Talent Management - TM - Trex 7.1 - Delta Indexing

luke.....are you out there??
congrats on your blog being featured right on the SDN homepage... very nice...
http://scn.sap.com/community/erp/hcm/blog/2010/09/20/setting-up-netweaver-embedded-search-trex-for-sap-ehp4-talent-management
and congrats to Chris on his first two excellent blogs....
http://scn.sap.com/people/chris.mcnarney/blog/2010/08/26/whats-included-with-the-predefined-performance-management-process
http://scn.sap.com/people/chris.mcnarney/blog/2010/09/09/whats-included-with-the-predefined-performance-management-process--part-2
all 3 blogs are very helpful since there is little information available out there on these topics...
so we've been testing the delta indexing program very heavily - ESH_IX_PROCESS_CHANGE_POINTERS
we have found that it does not appear to be able to index new hires (new central_person index does not pick up the new CP). The only way this data can be indexed is by running a full re-index. That is problematic for us, b/c we were hoping to only do full re-indexing 1 a week or even 1 a month. our indexes take 2-3 hrs to complete and trex searching is pretty much inoperable during that time.
Have you tested new hires with delta indexing? it seems as a gap in the change_pointers program. We opened up OSS message to SAP.
some additional thoughts working with the program, relative to your blog. I would highly recommend that anyone testing this makes sure the following notes are implemented in your system. The first one is the most recent and we ourselves did not have that implemented.
1. 0.350 BC-EIM-ESH 1441190 Error in model assignments to logical system 24.02.2010
2. 0.230 BC-EIM-ESH 1408655 Alerts in syntax check due to unused indexes 18.11.2009
3. 0.260 PA-TM 1395703 Positions and termination are missing for indexing 30.10.2009
4. 0.330 BC-EIM-ESH 1249482 Functional corrections for Enterprise Search 7.01 SP03 26.01.2009
Another area which we found from testing: SAP by default does not delta index structural authority view. What this means is that if a new talent specialist is added with 741 relationship there access to see that structure will not be available in TREX search by default delta indexing. This would also impact existing organizations and positions shifted under existing 741 relationships.
The information in spro is actually quite helpful, you can find it in: talent management and talent development > basic settings > search > BAdI: Activate Delta Indexing for Authorization Data
Activtate the BADI, than the program to "create the change pointers" must run periodically in your system. This is done with RPTMC_CREATE_CHANGEPOINT_AUTH. Once that program creates the change pointers the next time your scheduled delta program runs (ESH_IX_PROCESS_CHANGE_POINTERS) all of the structural auths will be created and indexed correctly.
If we can just now get new hires to work with ESH_IX_PROCESS_CHANGE_POINTERS we will probably only run the full re-index once a week or once a month.
Let me know your thoughts,
Michael
Message was edited by: Luke Marson
Message was edited by: Luke Marson

so if anyone is interested, from my previous post I mentioned that new hires were not getting picked up by the change pointers program.
after further testing though, we found that when the authorization recon program identifies the new hires and appropriately creates a change pointer.
conclusion: to avoid full re-indexing of trex indexes, perform the following steps:
1. implement / activate the BADI - HRTMC_AUTHORITY_VIEW - talent management -> basic settings -> search
2. Schedule program RPTMC_CREATE_CHANGEPOINT_AUTH - every 30 mins, or 1 or 2 hr. This program will capture whenever anything changes from an authorization data perspective. This would include identifiying new central persons (new hires) or new TMC specialist being setup with 741 relationship. This program "creates change pointers" which than feeds the main delta program - ESH_IX_PROCESS_CHANGE_POINTERS.
3. Use Luke's blog on the instructions for the delta program - ESH_IX_PROCESS_CHANGE_POINTERS - this program you can have run every 5 mins, 10 mins, 15 mins, based on your needs. this processes all delta changes, the first time the program runs after the RPTMC_CREATE_CHANGEPOINT_AUTH program finishes it will also processes the data authorization changes, otherwise every other time the program is running it will catch non-data authorization for all the other indexes (employee name change, new performance rating, new potential, position name change, new profiiciency scale, new career profile data, etc).
hope this helps somebody!
michael
Edited by: Michael L Pappis on Oct 7, 2010 12:05 AM

Agentry Delta Mechanism - Detecting changes in nested objects?

Hi all,
I have some experience with the Agentry Delta mechanism directly on a SQL backend (Update / Exchange Tables, Triggers, etc.). Now I am trying to find the right documentation, examples and stuff for that mechanism in the "Work Manager for SAP 6.0".
Maybe, someone could outline a solution to the following "gap" in the Standard Work Managers exchange mechanism?
A notifications in the "Work Manager" is updated, when the description of the notification has been changed in SAP.
However, a notification is not updated, when the description of the functional locations of the notification has been changed in SAP. Now, the question is, how to extend the exchange mechanism to listen to the functional locations description?
Thanks in advance for any hints you might have.
Regards, Daniel

Note: I reposted this question in its own discussion. Please do reply there if you can contribute to this topic. Thank you!
Hi,
its me again. I did some reading and I found something called "Exchange Object Linkage Settings" that sounds like it should be used for the use case above. The problem is, that it does not seem to work as I would expect.
Here is some description from the smp_agentry_sap_framework.pdf, page 78:
Exchange Object - Linkage Settings The Linkage Settings tab allows the exchange objects that are linked together to communicate with each other. The communication is one-directional, with the exchange object sending information to the object(s) listed in the Linked Exchange Objects List. When there is a value change to the exchange object, that value change information is passed on to the linked exchange objects. The linked exchange objects then go through additional processes related to the value change.
In the Config Panel, one can see that in the Standard Work Manager, there is a linkage between Functional Location and Workorder:
(Note that I started this discussion with an example on Notifications and Functional Locations. This is still where I want to go, but I wanted to stay within the Standard Workmanager Setup to make the - hopefully - ongoing discussion easier to follow.)
According to the above description, I would expect that, when changing the Functional Locations description, that information is passed to all Workorders with that Functional Location.
BUT HOW? It is not entirely clear to me how and what information is passed where. I would expect, that in the end, all related entries in the workorder exchange table will be updated with a new time stamp. (How else could the client get the information that the workorder is to be updated?)
This is not what I can see! When changing the Functional Locations description in SAP, I see that the Functional Locations exchange table entry is updated, but the corresponding Work Orders exchange table entry is not changed.
Does anybody have an idea how this feature is supposed to work? Maybe, there are some configuration steps necessary? Any input on the would be highly appreciated.
Regards, Daniel

Delta extraction for a generic datasource

Hi BWers,
I want put in Delta the extraction of a generic datasource.
Currently this generic datasource is based on the table VBPA (Sales Document: Partner). Any time field exists.
We need a time field in order to converse to a Delta extraction. This time field exists in the table VBAP (Sales Document: Item data). In fact two time fields exist: one which is filled at the creation of the sales order (ERDAT), another at the change of the sales order (AEDAT).
The fields VBELN, POSNR and MANDT are keys in the tables VBAP and VBPA.
The table VBAP changes when partner functions is created or changed in a sales order (VBELN) :
- When it is a creation of a new sales order (with new partner functions), a new record is created in VBAP and the field ERDAT (Created on) is filled. The field AEDAT (Changed on) is empty.
- When is a change of an existing sales order, the corresponding record in VBAP changed, and the field AEDAT is filled. ERDAT stays unchanged.
In order to converse to the Delta extraction, i need a only one time-field (calendar day) in RSO2 / Generic Delta.
But there is 2 time-fields ERDAT and AEDAT. So i just need to get AEDAT if it is filled, else if AEDAT is empty I will get ERDAT.
I would base my datasource on a view between VBPA and VBAP with one field which will be filled by AEDAT or ERDAT (with the conditions below). But it seems it is not possible.
Can you give me other ideas ?
Thanks a lot.
Cheers,
Vince.

In order to create a generic delta from two source fields, ERDAT and AEDAT in this case, you're going to have to create your generic extractor from a Function Module. Otherwise you'll only have the standard functionality available to you for creating the generic delta, which allows you to base it on only one column.
Here's a sample you can use, that was created for VBFA, and change for your DataSource.
FUNCTION y_docu_flow.
*"*"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 YSDS_DOCU_FLOW OPTIONAL
*" EXCEPTIONS
*"      NO_MORE_DATA
*"      ERROR_PASSED_TO_MESS_HANDLER
*& Global Data Declarations
* Type for VBFA Data
TYPES : BEGIN OF ty_vbfa            ,
            mandt   TYPE vbfa-mandt   ,
            vbelv   TYPE vbfa-vbelv   ,
            posnv   TYPE vbfa-posnv   ,
            vbeln   TYPE vbfa-vbeln   ,
            posnn   TYPE vbfa-posnn   ,
            vbtyp_n TYPE vbfa-vbtyp_n ,
            rfmng   TYPE vbfa-rfmng   ,
            meins   TYPE vbfa-meins   ,
            rfwrt   TYPE vbfa-rfwrt   ,
            waers   TYPE vbfa-waers   ,
            vbtyp_v TYPE vbfa-vbtyp_v ,
            plmin   TYPE vbfa-plmin   ,
            erdat   TYPE vbfa-erdat   ,
            aedat   TYPE vbfa-aedat   ,
          END   OF ty_vbfa            .
* Internal Tables and Selection Criteria Structure
DATA : t_vbfa     TYPE STANDARD TABLE OF ty_vbfa ,
         l_s_select TYPE srsc_s_select             .
* Field Symbols
FIELD-SYMBOLS : <fs_fields> TYPE rsfieldsel.
* Constants
CONSTANTS : c_error_msgty TYPE rslogparms-msgty VALUE 'E'            ,
              c_error_msgid TYPE rslogparms-msgid VALUE 'YAERO_WTY_VSR',
              c_error_msgv1 TYPE rslogparms-msgv1 VALUE ' MESSAGE_V1 ' ,
              c_error_msgv2 TYPE rslogparms-msgv1 VALUE ' MESSAGE_V2 ' ,
              c_error_msgv3 TYPE rslogparms-msgv1 VALUE ' MESSAGE_V3 ' ,
              c_error_msgv4 TYPE rslogparms-msgv1 VALUE ' MESSAGE_V4 ' ,
              c_error_msgno TYPE rslogparms-msgno VALUE 999            ,
              c_alias(2)    TYPE c                VALUE 'A~'           ,
              c_vbfa        TYPE dntab-tabname    VALUE 'VBFA'         .
* Maximum Database Lines, Data Package Counter and Cursor
STATICS : s_s_if              TYPE srsc_s_if_simple ,
            s_counter_datapakid TYPE sy-tabix         ,
            s_cursor            TYPE cursor           .
* Select Ranges
RANGES : r_erdat FOR vbfa-erdat ,
           r_aedat FOR vbfa-aedat ,
           r_vbelv FOR vbfa-vbelv ,
           r_posnv FOR vbfa-posnv ,
           r_vbeln FOR vbfa-vbeln ,
           r_posnn FOR vbfa-posnn .
*& Processing Logic
* Refresh Internal Table and Clear work area
REFRESH: t_vbfa   ,
           e_t_data .
* Check the Extraction Mode (Delta Initialization Or Delta)
IF i_initflag EQ sbiwa_c_flag_on.
*   Determine DataSource Validity
    IF i_dsource NE 'YSDDS_DOCU_FLOW'.
*     Call Function to Write Log
      CALL FUNCTION 'RSAL_LOG_WRITE'
        EXPORTING
          i_msgty = c_error_msgty
          i_msgid = c_error_msgid
          i_msgno = c_error_msgno
          i_msgv1 = c_error_msgv1
          i_msgv2 = c_error_msgv2
          i_msgv3 = c_error_msgv3
          i_msgv4 = c_error_msgv4.
*     Raise Exception
      RAISE error_passed_to_mess_handler.
    ENDIF.                  " IF i_dsource NE 'YSDDS_DOCU_FLOW'.
*   Append the Selection Criteria
    APPEND LINES OF i_t_select TO s_s_if-t_select.
*   Fill parameter buffer for data extraction calls
    MOVE : i_requnr TO s_s_if-requnr ,
           i_dsource TO s_s_if-dsource ,
           i_maxsize TO s_s_if-maxsize .
*   Append Fields to be Selected
    APPEND LINES OF i_t_fields TO s_s_if-t_fields.
*   Add the Alias to Fields
    LOOP AT s_s_if-t_fields
      ASSIGNING <fs_fields>.
      CONCATENATE c_alias
                  <fs_fields>-fieldnm
             INTO <fs_fields>-fieldnm.
      CONDENSE <fs_fields>-fieldnm NO-GAPS.
    ENDLOOP.                " LOOP AT s_s_if-t_fields..
ELSE.                     " IF i_initflag EQ sbiwa_c_flag_on
*   For First Data Package, Open Cursor
    IF s_counter_datapakid EQ 0.
*     Clear Ranges
      CLEAR : r_erdat ,
              r_aedat ,
              r_vbelv ,
              r_posnv ,
              r_vbeln ,
              r_posnn .
*     Fill Selection Ranges
      LOOP AT s_s_if-t_select
        INTO l_s_select.
*       Determine Selection Range Field Name
        CASE l_s_select-fieldnm.
*         Created On Date
          WHEN 'ERDAT'.
            MOVE : l_s_select-sign   TO r_erdat-sign   ,
                   l_s_select-option TO r_erdat-option ,
                   l_s_select-low    TO r_erdat-low    ,
                   l_s_select-high   TO r_erdat-high   .
            APPEND r_erdat.
*           Fill the change date too
            MOVE r_erdat[] TO r_aedat[].
*         Predecessor Document Number
          WHEN 'VBELV'.
            MOVE : l_s_select-sign   TO r_vbelv-sign   ,
                   l_s_select-option TO r_vbelv-option ,
                   l_s_select-low    TO r_vbelv-low    ,
                   l_s_select-high   TO r_vbelv-high   .
            APPEND r_vbelv.
*         Predecessor Document Line Item
          WHEN 'POSNV'.
            MOVE : l_s_select-sign   TO r_posnv-sign   ,
                   l_s_select-option TO r_posnv-option ,
                   l_s_select-low    TO r_posnv-low    ,
                   l_s_select-high   TO r_posnv-high   .
            APPEND r_posnv.
*         Successor Document Number
          WHEN 'VBELN'.
            MOVE : l_s_select-sign   TO r_vbeln-sign   ,
                   l_s_select-option TO r_vbeln-option ,
                   l_s_select-low    TO r_vbeln-low    ,
                   l_s_select-high   TO r_vbeln-high   .
            APPEND r_vbeln.
*         Successor Document Line Item
          WHEN 'POSNN'.
            MOVE : l_s_select-sign   TO r_posnn-sign   ,
                   l_s_select-option TO r_posnn-option ,
                   l_s_select-low    TO r_posnn-low    ,
                   l_s_select-high   TO r_posnn-high   .
            APPEND r_posnn.
        ENDCASE.            " CASE l_s_select-fieldnm.
      ENDLOOP.              " LOOP AT s_s_if-t_select..
*     Open Cursor on View to Fetch data
*     If full load with Selection on Fiscal Year
      IF r_aedat[] IS INITIAL.
*       Full Extraction
        OPEN CURSOR
        WITH HOLD s_cursor FOR
      SELECT (s_s_if-t_fields)
        FROM vbfa      AS a
        JOIN pnwtyv    AS b
          ON a~vbelv   EQ b~sdvbeln
       WHERE a~vbelv   IN r_vbelv
         AND a~posnv   IN r_posnv
         AND a~vbeln   IN r_vbeln
         AND a~posnn   IN r_posnn
         AND a~rfmng   NE 0
         AND a~erdat   IN r_erdat
         AND b~sdvbeln NE space.
      ELSE.
*       Delta Extraction Using ERDAT and AEDAT
        OPEN   CURSOR
        WITH   HOLD s_cursor FOR
      SELECT   (s_s_if-t_fields)
        FROM   vbfa      AS a
        JOIN   pnwtyv    AS b
          ON   a~vbelv   EQ b~sdvbeln
       WHERE   a~vbelv   IN r_vbelv
         AND   a~posnv   IN r_posnv
         AND   a~vbeln   IN r_vbeln
         AND   a~posnn   IN r_posnn
         AND   a~rfmng   NE 0
         AND ( a~erdat   IN r_erdat
          OR   a~aedat   IN r_aedat )
         AND   b~sdvbeln NE space.
      ENDIF.                " IF r_aedat[] IS INITIAL
    ENDIF.                  " IF s_counter_datapakid..
*   Fetch Records into Interface Table
    FETCH NEXT CURSOR s_cursor
         APPENDING CORRESPONDING FIELDS
          OF TABLE t_vbfa
      PACKAGE SIZE s_s_if-maxsize.
*   No More Data, Raise Exception
    IF sy-subrc NE 0.
*     Close the Cursor
      CLOSE CURSOR s_cursor.
*     Raise Exception
      RAISE no_more_data.
    ELSE.
*     Move Extracted Data to Output Structure
      MOVE t_vbfa[] TO e_t_data[].
*     Release Memory
      FREE t_vbfa.
*     Sort Output Structure
      SORT e_t_data BY vbelv
                       posnv
                       vbeln
                       posnn
                       vbtyp_n.
*     Delete Duplicate Records from Output Structure
      DELETE ADJACENT DUPLICATES
        FROM e_t_data
   COMPARING vbelv
             posnv
             vbeln
             posnn
             vbtyp_n.
*     Increment Data Package Number
      s_counter_datapakid = s_counter_datapakid + 1.
    ENDIF.                  " IF sy-subrc NE 0
ENDIF.                    " IF i_initflag EQ sbiwa_c_flag_on
ENDFUNCTION.
Edited by: Dennis Scoville on Jul 16, 2009 8:29 AM
Edited by: Dennis Scoville on Jul 16, 2009 8:29 AM

CIF Delta transfer - PIR

Hi
I have included the fields LIFAB and LIFBI ( available from and available to dates of a Purchase info record) of EINA table in BD52 for delta transfer.
When i update the Purchase info record with the available from and available to dates and do a CFM3, the corresponding T-Lane in APO is not getting updated.
We want this transfer to take place thru delta transfer and not thru a intial transfer which is scheduled on a longer periodic gap.
Any thoughts on this pls..
Regards
Joe

the combination of Plant, material, P-Org in the Integration model decides the updates

Generic Data Source Delta on Time Stamp Issue

HI,
I had a Z datasource on a Z table with Time stamp
The Generic delta of the Data source is based on Time stamp with Upper Saftey Intreval 1Sec
When i extract delta consutively with 1 Hr gap i am getting an delta evn tough the table is updated with etries
How to investigate & resolve the issue
Thanks

Hi
please elaborate question is not clear.
Ashish

Setup tables - Deltas

Hi experts,
Suppose if we have filled the setup tables by 12:30 AM then at what time we need to schedule for deltas in lbwe job control i.e as soon as setup tables filling is over or at what time. What is the minimum time gap we can keep.
Regards,
Bhadri M.

Hi,
The setup tables are used for pullling the history. As soon as you initialize start the lbwe job control so that whatever transactions are recorded are pulled over to the delta queues.
As soon as your datasource is active any postings that the users are posting get recorded to the extractor queue.
Cheers,
Kedar

Finding gaps between dates in table

Is this following possible in sql...
Lets say I have a "sales" table with these fields
SalesMan, SaleDate, Amount.
and this data
John, 6/may/07,90
John, 4/may/07,330
John, 2/may/07,200
John, 9/apr/07,300
John, 5/apr/07,300
Dave, 9/jul/07,90
Dave, 8/jul/07,90
Dave, 4/jul/07,330
Dave, 2/jul/07,200
Dave, 4/jun/07,300
Dave, 2/jun/07,300
I want to ask the database "show me the third sale made by each sales man after any 2 week gap in sales"
Here's the same data again...
John, 6/may/07,90 --- I want this one
John, 4/may/07,330
John, 2/may/07,200
<2 week gap>
John, 9/apr/07,300
John, 5/apr/07,300
Dave, 9/jul/07,90
Dave, 8/jul/07,90 --- and this one
Dave, 4/jul/07,330
Dave, 2/jul/07,200
<2 week gap>
Dave, 4/jun/07,300
Dave, 2/jun/07,300
My actual problem is more complicated but this is it in its most basic form.
Any help is much appreciated.

That's easy enough using the LAG analytic funtion.
with testdata as (select 'John' name, to_date('6/may/07') sdate, 90 amount from dual
union all select 'John', to_date('4/may/07'), 330 from dual
union all select 'John', to_date('2/may/07'), 200 from dual
union all select 'John', to_date('9/apr/07'), 300 from dual
union all select 'John', to_date('5/apr/07'), 300 from dual
union all select 'Dave', to_date('9/jul/07'), 90 from dual
union all select 'Dave', to_date('8/jul/07'), 90 from dual
union all select 'Dave', to_date('4/jul/07'), 330 from dual
union all select 'Dave', to_date('2/jul/07'), 200 from dual
union all select 'Dave', to_date('4/jun/07'), 300 from dual
union all select 'Dave', to_date('2/jun/07'), 300 from dual
), sales_gaps AS (
select name, sdate, amount,
         lag(sdate,2) over (partition by name order by sdate, amount) -
         lag(sdate,3) over (partition by name order by sdate, amount) delta
from testdata
SELECT NAME, SDATE, AMOUNT FROM SALES_GAPS WHERE DELTA >= 14
NAME SDATE                     AMOUNT
Dave 08-JUL-2007 12:00:00      90
John 06-MAY-2007 12:00:00      90
2 rows selected

K7N2 Delta lock ups

Hi there,
I've got a MSI k7N2 Delta sitting in my PC atm. But with a nasty problem. I have to keep the cpu sitting in it (AMD Barton 3000) underclocked for me to use my PC for more then 40 mins at a time. After that time, it just freezes, and the sound card (not system speaker) emits a nasty high pitched sound. Using a more intensive game, i.e. planetside speeds up the process, somethimes running for a mere 5 mins. To use the pc atm, the cpu is clocked at 1.4Ghz, instead of the over 2ghz it should be at.
Any suggestions anyone?
Specs:
K7N2 Delta
AMD Barton 3000+
512Mb Kingston DDR (on compatibilty list)
ATI Radeon 7500
SB! 128
Antec 400Watt PSU

ok, after some more testing (man i love CS ) it still locks up, but it took longer initially. It now just freezes, with no beeeep from the sound card. It may be temperature related though, as after the intial freeze, it will now only take a few minutes before it does it again. Straight after it freezes I'm getting temperature of around 50 on all monitors.
Ill whip out that TV card and give it a whirl now
p.s. case fans, i think one is in the wrong way, is the spinny side supposed to facing in the case, or out the case? cheers

Error message -- "The gap...st have a duration of either a zero, or at least 0.4 seconds

timeline has 2 errors -- and this is what the error says. Of course I have no idea what the sentence says completely...
Have no idea where to look for the fix.
The menu used is cityscape modified HD and for main menu and then 2 submenus.
CS6
Anyone have any ideas?
Thanks

Zoom in on the junction between files. Is there a gap in the audio or video?
The usual problem here is that mpeg files often have small differences in the length of the audio and video streams. When you butt them together, this creates small gaps.
I have not experimented with this, and do not know whether using an mpg file (muxed) or m2v/wav/a3c (demuxed) makes a difference. I don't ever put multiple files on one timeline. If I need them on one timeline, I create one file.

Error while resetting the delta in ODS (BI 7.0)

Hi all,
I face a problem in delta resetting...need your help... Thanks..
I have an ODS-1 which has target cube1, cube2, cube3....One week back a new target has been added as ODS-2....All complete data from ODS1 has been piped into ODS 2..(Note.. ODS2 has many more inputs from other cubes/ODS too)
NO issues till now....
I found a data problem in ODS-1 which got loaded 15 days back..... I have removed all 15 requests from cube1, cube2 and cube3... Now I am trying to reset the delta in ODS1...
I am getting the following error....Infoprovide ODS2 still contains request... Delete this first....
Since ODS2 has many other data alongwith ODS1... If I try deleting request from ODS2,, I need to clean it totally and redo... I dont want to do this...
Is there any way to disconnect this delta link between ODS1 - ODS2..... So that I will reload the data in ODS1 and populate into all targets...
Let me know your suggestions.... Thanks!
Regards
Ayyappan.V

Is there any way to disconnect this delta link between ODS1 - ODS2..... So that I will reload the data in ODS1 and populate into all targets...
I dont think you can disconnect the link. just delete the requests originating from ODS1 in ODS2 and you can leave all other requests intact that are from other dataproviders and do a reinit.

Error while saving FYV : Gaps in financial year variant periods

Hello Experts,
We are getting an error while saving a new FYV as:
Gaps in financial year variant periods XY
Message no. FGV556
Diagnosis
The period specification has gaps. The periods must be sequentially numbered without any gaps.
System Response
Only a correctly defined period assignment can be saved.
Procedure
Define the periods with consecutive numbers.
Details: The new FYV has 52/53 weeks as posting periods depending on calendar year.
For example, we are trying to define Fisc 2009 as follows. (Fiscal year 2009 = Nov 01 2008 to Oct 31 2009).
Month-Day-Period-Yearshift
11     ---     7     ---     1     ---     +1
11     ---     14     ---     2     ---     +1
11     ---     21     ---     3     ---     +1
11     ---     28     ---     4     ---     +1
12     ---     5     ---     5     ---     +1
12     ---     12     ---     6     ---     +1
12     ---     19     ---     7     ---     +1
12     ---     26     ---     8     ---     +1
12     ---     31     ---     9     ---     +1
1     ---     3     ---     9     ---     0
1     ---     10     ---     10     ---     0
1     ---     17     ---     11     ---     0
1     ---     24     ---     12     ---     0
1     ---     31     ---     13     ---     0
2     ---     7     ---     14     ---     0
2     ---     14     ---     15     ---     0
2     ---     21     ---     16     ---     0
2     ---     28     ---     17     ---     0
3     ---     7     ---     18     ---     0
3     ---     14     ---     19     ---     0
3     ---     21     ---     20     ---     0
3     ---     28     ---     21     ---     0
4     ---     4     ---     22     ---     0
4     ---     11     ---     23     ---     0
4     ---     18     ---     24     ---     0
4     ---     25     ---     25     ---     0
4     ---     2     ---     26     ---     0
5     ---     9     ---     27     ---     0
5     ---     16     ---     28     ---     0
5     ---     23     ---     29     ---     0
5     ---     30     ---     30     ---     0
6     ---     6     ---     31     ---     0
6     ---     13     ---     32     ---     0
6     ---     20     ---     33     ---     0
6     ---     27     ---     34     ---     0
7     ---     4     ---     35     ---     0
7     ---     11     ---     36     ---     0
7     ---     18     ---     37     ---     0
7     ---     25     ---     38     ---     0
8     ---     1     ---     39     ---     0
8     ---     8     ---     40     ---     0
8     ---     15     ---     41     ---     0
8     ---     22     ---     42     ---     0
8     ---     29     ---     43     ---     0
9     ---     5     ---     44     ---     0
9     ---     12     ---     45     ---     0
9     ---     19     ---     46     ---     0
9     ---     26     ---     47     ---     0
10     ---     3     ---     48     ---     0
10     ---     10     ---     49     ---     0
10     ---     17     ---     50     ---     0
10     ---     24     ---     51     ---     0
10     ---     31     ---     52     ---     0
The above entries cover all the dates in calendar year 2009, that is, Jan 2009 to Oct 2009 is covered by periods 10 to 52 and Nov 01 2009 to Dec 31 2009 is covered by period 1 to 9 of the following fiscal year 2010.
Inspite of making sure that all the days of 2009 are covered by periods 1 to 52. We are still unable to save the FYV.
Please help!
Susan

Hello, I am getting this error while saving the FSV. My FSV is based on Weeks. Below is what I am inputting for this. Other details are Calender Year - 2017, No. of posting periods - 53, checked year dependent. Also, I have FSV for previous years also where weeks are 52 but configured as 53. So, hope that this is not creating this issue. Solicit your early response.
Month
Day
Period
Year Shift
1
7
1
0
1
14
2
0
1
21
3
0
1
28
4
0
2
4
5
0
2
11
6
0
2
18
7
0
2
25
8
0
3
4
9
0
3
11
10
0
3
18
11
0
3
25
12
0
4
1
13
0
4
8
14
0
4
15
15
0
4
22
16
0
4
29
17
0
5
6
18
0
5
13
19
0
5
20
20
0
5
27
21
0
6
3
22
0
6
10
23
0
6
17
24
0
6
24
25
0
7
1
26
0
7
8
27
0
7
15
28
0
7
22
29
0
7
29
30
0
8
5
31
0
8
12
32
0
8
19
33
0
8
26
34
0
9
2
35
0
9
9
36
0
9
16
37
0
9
23
38
0
9
30
39
0
10
7
40
0
10
14
41
0
10
21
42
0
10
28
43
0
11
4
44
0
11
11
45
0
11
18
46
0
11
25
47
0
12
2
48
0
12
9
49
0
12
16
50
0
12
23
51
0
12
30
52
0
12
31
1
+1
Thanks
Deepankar

Delta Gap in LO

Similar Messages

Maybe you are looking for