Quota is displayed twice in 2006 for the same date

When iam entering Leave Quota Through PA30 , PA61 ,PT_QTA00
for a particular Employee it will display the Quota Twice
Is there any way we can stop this ?
is there any way we can Put cap that double Entry for the same date ?
Quota is deducting Normally but it is Displaying Twice
Plz Help Experts

Thank You So much
i changed in the info type
SPRO>> Time Management>> Time Data Recording and Administration>> Specify System Reaction to Overlapping Time Infotypes
Infotype 2006
Time Cstr. Class 01
Reaction Indicator   : select according to The Requirement
Right now Reaction Indicator is set to W
Make the Reaction Indicator to E and save the Entry
It worked for now
one thing iam not sure how does V_T554Y table work
Plz let me know
Reaction I ndicator
This indicator determines how the system reacts when you enter new infotype records which overlap with existing ones.
The specifications are as follows:
A - The old record is delimited, all collisions are displayed.
E - The system does not allow you to create the new record, and
    displays all collisions.
W - You can create the new record, but the old record   remains unchanged. All collisions are displayed.
N - As for W, but collisions are not displayed.
Edited by: jkhose on Jan 25, 2012 1:23 AM

Similar Messages

Display discounts and surcharges for the same vbeln in the same row

hi experts
i have to display one discount and surcharges for one vbeln, posnr and one material,
i have used konv-kschl for condition type and konv-kwert for condition value.
in my output the conditions what i have given for discounts and surcharges its matching and displaying in different lines for the same vbeln and posnr. usually i should get one line of outputfor one vbeln, but iam getting 3 times repeated
(one without discounts, surcharges,
second : same vblen, posnr with discounts,
third : same vblen, posnr for surcharges )
please modify the internal table and conditions below what i have given in my object.
DATA : BEGIN OF it_konv OCCURS 0,
knumv LIKE konv-knumv, "Number of the document condition
kschl LIKE konv-kschl, "Condition type
kwert LIKE konv-kwert, "Condition value
kbetr LIKE konv-kbetr,
kposn LIKE konv-kposn,
discounts LIKE konv-kwert,
surcharges LIKE konv-kwert,
hkunnr LIKE knvh-hkunnr,
kunnr LIKE knvh-kunnr,
END OF it_konv.
LOOP AT it_konv INTO wa_konv.
CASE wa_konv-kschl.
WHEN 'ZD01' OR 'ZD02' OR 'ZD03'.
wa_konv-discounts = wa_konv-kwert.
WHEN 'ZEXP' OR 'ZEXW' OR 'ZCAF' OR 'ZCAP' OR 'ZCAQ'
OR 'ZS01' OR 'ZS02' OR 'ZS03'.
wa_konv-surcharges = wa_konv-kwert.
WHEN OTHERS.
DELETE it_konv WHERE kschl = wa_konv-kschl.
ENDCASE.
MODIFY it_konv FROM wa_konv TRANSPORTING discounts surcharges.
CLEAR wa_konv.
REFRESH wa_konv.
ENDLOOP.
As per one of the abap expert who responded to my query is the following.
DATA : BEGIN OF it_konv OCCURS 0,
knumv LIKE konv-knumv, "Number of the document condition
kschl LIKE konv-kschl, "Condition type
kwert LIKE konv-kwert, "Condition value
kbetr LIKE konv-kbetr,
kposn LIKE konv-kposn,
discounts LIKE konv-kwert,
surcharges LIKE konv-kwert,
hkunnr LIKE knvh-hkunnr,
kunnr LIKE knvh-kunnr,
END OF it_konv.
DATA : BEGIN OF wa_konv OCCURS 0,
kposn LIKE konv-kposn,
discounts LIKE konv-kwert,
surcharges LIKE konv-kwert,
hkunnr LIKE knvh-hkunnr,
kunnr LIKE knvh-kunnr,
END OF wa_konv.
move '1' to it_konv-knumv.
move 'ZD01' to it_konv-kschl.
move '1200' to it_konv-kwert.
move '0010' to it_konv-kposn.
append it_konv.
move '2' to it_konv-knumv.
move 'ZEXP' to it_konv-kschl.
move '1300' to it_konv-kwert.
move '0010' to it_konv-kposn.
append it_konv.
move '3' to it_konv-knumv.
move 'ZEXP' to it_konv-kschl.
move '1400' to it_konv-kwert.
move '0010' to it_konv-kposn.
append it_konv.
LOOP AT it_konv.
MOVE-CORRESPONDING it_konv to wa_konv.
CASE IT_konv-kschl.
WHEN 'ZD01' OR 'ZD02' OR 'ZD03'.
wa_konv-discounts = IT_konv-kwert.
WHEN 'ZEXP' OR 'ZEXW' OR 'ZCAF' OR 'ZCAP' OR 'ZCAQ'
OR 'ZS01' OR 'ZS02' OR 'ZS03'.
wa_konv-surcharges = IT_konv-kwert.
ENDCASE.
COLLECT WA_KONV.
CLEAR wa_konv.
ENDLOOP.
But to try according to the above, i dont have the values for kwert, i know only the condition type (KSCHL). based on this how can i solve my problem
please clarify
thanks in advance

Refer to the suggestion given by Naimesh here Can we modify a sub-total in ALV making use of function GET_GLOBALS_FROM_SLVC_FULLSCR and the method GET_SUBTOTALS. You can see the parameter ep_collect01 refered in case of subtotals. Can you please check ep_collect00 for grand total in your case.
As said about EP_COLLECT00,here goes a classic example Modify grand total in ALV GRID
BR
Keshav
Edited by: Keshav.T on Sep 21, 2011 9:39 AM

Multiple MM schedule lines for the same date

Hello All Gurus,
I am facing a problem where the MM schedule lines are divided into various quantites for the same date. For example on 02/11/2010 the total quantity is 120, it is appearing in the below form in ME38:
02/11/2010 - 40
02/11/2010 - 40
02/11/2010 - 40
Although this is not an error, but my client is not happy with this. Can someone tell me why I am getting this error? Is it because of the rounding value that we maintain in MRP 1 view of material master record? Or is there any other setting that I am missing?
Please let me know. I would be very much thankful to you.
Thanks and Regards,
Umakanth

Hi,
Before changing the setup, note that sometimes it is beneficial to split one demand into multiple delivery schedules. Especially if the demand is bigger than equipment type (container/truck etc.). If you want to manage inbound transportation for such delivery schedules, it is much simpler to do this when each delivery schedule is not bigger than one equipment.
Regards,
Dominik Modrzejewski

Events cannot have multiple exceptions for the same date

I just starting getting this message and could not sync to one of my Google calendars. I'm posting this for others who might get the same problem.
I didn't find the answer on these forums but did find it on this thread on Google:
http://www.google.com/support/forum/p/Calendar/thread?tid=241155f758d9e2a4&hl=en
Here's the important excerpt:
"I had a client, who just had this same issue, nothing to do with Google cals.
It was apparently, in my best guess, a corruption of the subscribed cal.
*I did a get info on the cal, copied the URL, deleted the cal, then re-subscribed to it by pasting in the URL, and now it's working fine*."

I've been having the same problem with my iCal calendars and the "Events cannot have multiple exceptions for the same date" error. Once it gets going, it uses up a lot of the CPU and resources. After reinstalling iCal, all my calendars were missing and I could not even resubscribe to them.
I took my MacBook Pro to the Apple Store, and they were able to solve the problem by moving some of the iCal files from their existing folders out to the desktop, and reopening the program. That got it working, however, now I'm having the same problem again. So back to square one. Anyone else having this issue and know the cause?
My setup is my MacBook Pro uses Entourage, use that calendar in my iCal. And I subscribe to two calendars my wife publishes on her Macbook. We're both using Snow Leopard.

How does iCal, or Calendar, order the display of multiple events for the same time?

I can't for the life of me figure out how iCal orders the display of multiple items at the same time. Does anyone have a clue? It's not alphabetical. It's not according the the order of the calendars in the left pane. Is it just random? Any help would be greatly appreciated.

In the focus lost eventhandling start a thread which does
the actual handling.
the new thread waits for a little time (0.1 seconds)
the click event of the button checks for a thread like the one above and tells it not to execute
This way you execute the for the lost focus event only if
the ok button isn't clicked in the same process ... not
realy good, because it kind of relies on the ordering of threads ... but maybe it still works for you?

Can create twice billing document for the same delivery in STO

Hi experts,
I donot have problems in Standard Sales order when I create billing doc via VF01. When I try to create another billing doc in VF01 for the same delivery it says error, as the item is already invoiced.
This is correct.
But while creating invoice for STO order, system allows me to create more than 1 billing document for the same delivery. If we accidentally or purposefully create it allows to create many.
Could you let me know where in SPRO (IMG) I can control this?
Thanks,
Pri

Hi
STO billing if it is intercompany STO followed by IV billing type you can create only once
No special settings reqd to achieve this as you bill (IV billing type) the delivery the first time, the delivery status gets completed
If Intracompany, the billing type is proforma invoice F8 and this can be created as many times as you wish as proforma doesnot update accounting
if your issue is this
Even this also if you want to restrict only once then try with copying requirenments 311 at item level (i hope standard item category NLN is used) in VTFL between header NL to F8
Regards
Raja

BAM Combo Chart showing data in 2 graphics for the same data object

Hi all,
I’m trying to show 2 views of the same data object in a Combo Chart (e.g. orders created today as a bar chart and orders created yesterday as line chart grouping by hour of day). It was pretty easy adding the same data object twice but the data type of the horizontal axis seems to be lost and it gets sorted as a simple string, leading to strange grouping of the hours with 05:00 representing 5 AM sided with 05:00 representing 5 PM. Also, I’m not able to format such fields using the format values tab.
Is using the same data object two times in the same report an unsupported scenario?
Thanks,
Daniel

why you want to add the same data object twice? Your use case can be achieved with single data object only.
1) Create combo chart and select the data object.
2) On "Choose data fields" page group by datetime field.
3) You will see UI changed to 3 sections - left one with "Group by" section, middle with "Chart values" and right one with "Time Groups".
4) In the right "Time Group" section, uncheck checkbox for continuous time series. Time Unit as hour, quantity as 1.
5) In middle "Chart values" section ,select the fields that you want to display as chart values and respective chart types , in your case orders created today as a bar chart and orders created yesterday as line chart.
5) Click Next and Finish.
6) Then you can go to Value format tab, and change the format for the datetime field as timeunit and required format.

CBO generating different plans for the same data in similar Environments

Hi All
I have been trying to compare an SQL from 2 different but similar environments build of the same hardware specs .The issue I am facing is environment A, the query executes in less than 2 minutes with plan mostly showing full table scans and hash join whereas in environment B(problematic), it times out after 2 hours with an error of unable to extend table space . The statistics are up to date in both environments for both tables and indexes . System parameters are exactly similar(default oracle for except for multiblock_read_count ).
Both Environment have same db parameter for db_file_multiblock_read_count(16), optimizer(refer below),hash_area_size (131072),pga_aggregate_target(1G),db_block_size(8192) etc . SREADTIM, MREADTIM, CPUSPEED, MBRC are all null in aux_stats in both environment because workload was never collected i believe.
Attached is details about the SQL with table stats, SQL and index stats my main concern is CBO generating different plans for the similar data and statistics and same hardware and software specs. Is there any thing else I should consider .I generally see environment B being very slow and always plans tend to nested loops and index scan whereas what we really need is a sensible FTS in many cases. One of the very surprising thing is METER_CONFIG_HEADER below which has just 80 blocks of data is being asked for index scan.
show parameter optimizer
optimizer_dynamic_sampling integer 2
optimizer_features_enable string 10.2.0.4
optimizer_index_caching integer 0
optimizer_index_cost_adj integer 100
optimizer_mode string ALL_ROWS
optimizer_secure_view_merging boolean TRUE
**Environment**
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
PL/SQL Release 10.2.0.4.0 - Production
CORE     10.2.0.4.0     Production
TNS for Solaris: Version 10.2.0.4.0 - Production
NLSRTL Version 10.2.0.4.0 - Production
Note: : There are slight difference in the no of records in the attached sheet.However, I wanted to tell that i have tested with exact same data and was getting similar results but I couldn't retain the data untill collecting the details in the attachment
TEST1     COMPARE TABLE LEVE STATS used by CBO
ENVIRONMENT A
TABLE_NAME     NUM_ROWS     BLOCKS     LAST_ANALYZED
ASSET     3607425     167760     5/02/2013 22:11
METER_CONFIG_HEADER     3658     80     5/01/2013 0:07
METER_CONFIG_ITEM     32310     496     5/01/2013 0:07
NMI     1899024     33557     18/02/2013 10:55
REGISTER     4830153     101504     18/02/2013 9:57
SDP_LOGICAL_ASSET     1607456     19137     18/02/2013 15:48
SDP_LOGICAL_REGISTER     5110781     78691     18/02/2013 9:56
SERVICE_DELIVERY_POINT     1425890     42468     18/02/2013 13:54
ENVIRONMENT B
TABLE_NAME     NUM_ROWS     BLOCKS     LAST_ANALYZED
ASSET     4133939     198570     16/02/2013 10:02
METER_CONFIG_HEADER     3779     80     16/02/2013 10:55
METER_CONFIG_ITEM     33720     510     16/02/2013 10:55
NMI     1969000     33113     16/02/2013 10:58
REGISTER     5837874     120104     16/02/2013 11:05
SDP_LOGICAL_ASSET     1788152     22325     16/02/2013 11:06
SDP_LOGICAL_REGISTER     6101934     91088     16/02/2013 11:07
SERVICE_DELIVERY_POINT     1447589     43804     16/02/2013 11:11
TEST ITEM 2     COMPARE INDEX STATS used by CBO
ENVIRONMENT A
TABLE_NAME     INDEX_NAME     UNIQUENESS     BLEVEL     LEAF_BLOCKS     DISTINCT_KEYS     AVG_LEAF_BLOCKS_PER_KEY     AVG_DATA_BLOCKS_PER_KEY     CLUSTERING_FACTOR     NUM_ROWS
ASSET     IDX_AST_DEVICE_CATEGORY_SK     NONUNIQUE     2     9878     67     147     12982     869801     3553095
ASSET     IDX_A_SAPINTLOGDEV_SK     NONUNIQUE     2     7291     2747     2     639     1755977     3597916
ASSET     SYS_C00102592     UNIQUE     2     12488     3733831     1     1     3726639     3733831
METER_CONFIG_HEADER     SYS_C0092052     UNIQUE     1     12     3670     1     1     3590     3670
METER_CONFIG_ITEM     SYS_C0092074     UNIQUE     1     104     32310     1     1     32132     32310
NMI     IDX_NMI_ID     NONUNIQUE     2     6298     844853     1     2     1964769     1965029
NMI     IDX_NMI_ID_NK     NONUNIQUE     2     6701     1923072     1     1     1922831     1923084
NMI     IDX_NMI_STATS     NONUNIQUE     1     106     4     26     52     211     211
REGISTER     REG_EFFECTIVE_DTM     NONUNIQUE     2     12498     795     15     2899     2304831     4711808
REGISTER     SYS_C00102653     UNIQUE     2     16942     5065660     1     1     5056855     5065660
SDP_LOGICAL_ASSET     IDX_SLA_SAPINTLOGDEV_SK     NONUNIQUE     2     3667     1607968     1     1     1607689     1607982
SDP_LOGICAL_ASSET     IDX_SLA_SDP_SK     NONUNIQUE     2     3811     668727     1     2     1606204     1607982
SDP_LOGICAL_ASSET     SYS_C00102665     UNIQUE     2     5116     1529606     1     1     1528136     1529606
SDP_LOGICAL_REGISTER     SYS_C00102677     UNIQUE     2     17370     5193638     1     1     5193623     5193638
SERVICE_DELIVERY_POINT     IDX_SDP_NMI_SK     NONUNIQUE     2     4406     676523     1     2     1423247     1425890
SERVICE_DELIVERY_POINT     IDX_SDP_SAP_INT_NMI_SK     NONUNIQUE     2     7374     676523     1     2     1458238     1461108
SERVICE_DELIVERY_POINT     SYS_C00102687     UNIQUE     2     4737     1416207     1     1     1415022     1416207
ENVIRONMENT B
TABLE_NAME     INDEX_NAME     UNIQUENESS     BLEVEL     LEAF_BLOCKS     DISTINCT_KEYS     AVG_LEAF_BLOCKS_PER_KEY     AVG_DATA_BLOCKS_PER_KEY     CLUSTERING_FACTOR     NUM_ROWS
ASSET     IDX_AST_DEVICE_CATEGORY_SK     NONUNIQUE     2     8606     121     71     16428     1987833     4162257
ASSET     IDX_A_SAPINTLOGDEV_SK     NONUNIQUE     2     8432     1780146     1     1     2048170     4162257
ASSET     SYS_C00116157     UNIQUE     2     13597     4162263     1     1     4158759     4162263
METER_CONFIG_HEADER     SYS_C00116570     UNIQUE     1     12     3779     1     1     3734     3779
METER_CONFIG_ITEM     SYS_C00116592     UNIQUE     1     107     33720     1     1     33459     33720
NMI     IDX_NMI_ID     NONUNIQUE     2     6319     683370     1     2     1970460     1971313
NMI     IDX_NMI_ID_NK     NONUNIQUE     2     6597     1971293     1     1     1970771     1971313
NMI     IDX_NMI_STATS     NONUNIQUE     1     98     48     2     4     196     196
REGISTER     REG_EFFECTIVE_DTM     NONUNIQUE     2     15615     1273     12     2109     2685924     5886582
REGISTER     SYS_C00116748     UNIQUE     2     19533     5886582     1     1     5845565     5886582
SDP_LOGICAL_ASSET     IDX_SLA_SAPINTLOGDEV_SK     NONUNIQUE     2     4111     1795084     1     1     1758441     1795130
SDP_LOGICAL_ASSET     IDX_SLA_SDP_SK     NONUNIQUE     2     4003     674249     1     2     1787987     1795130
SDP_LOGICAL_ASSET     SYS_C004520     UNIQUE     2     5864     1795130     1     1     1782147     1795130
SDP_LOGICAL_REGISTER     SYS_C004539     UNIQUE     2     20413     6152850     1     1     6073059     6152850
SERVICE_DELIVERY_POINT     IDX_SDP_NMI_SK     NONUNIQUE     2     3227     660649     1     2     1422572     1447803
SERVICE_DELIVERY_POINT     IDX_SDP_SAP_INT_NMI_SK     NONUNIQUE     2     6399     646257     1     2     1346948     1349993
SERVICE_DELIVERY_POINT     SYS_C00128706     UNIQUE     2     4643     1447946     1     1     1442796     1447946
TEST ITEM 3     COMPARE PLANS
ENVIRONMENT A
Plan hash value: 4109575732
| Id | Operation                       | Name                   | Rows | Bytes |TempSpc| Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT                |                        |    13 | 2067 |       |   135K (2)| 00:27:05 |
|   1 | HASH UNIQUE                    |                        |    13 | 2067 |       |   135K (2)| 00:27:05 |
|* 2 |   HASH JOIN                     |                        |    13 | 2067 |       |   135K (2)| 00:27:05 |
|* 3 |    HASH JOIN                    |                        |     6 |   900 |       |   135K (2)| 00:27:04 |
|* 4 |     HASH JOIN ANTI              |                        |     1 |   137 |       |   135K (2)| 00:27:03 |
|* 5 |      TABLE ACCESS BY INDEX ROWID| NMI                    |     1 |    22 |       |     5   (0)| 00:00:01 |
|   6 |       NESTED LOOPS              |                        |     1 |   131 |       | 95137   (2)| 00:19:02 |
|* 7 |        HASH JOIN                |                        |     1 |   109 |       | 95132   (2)| 00:19:02 |
|* 8 |         TABLE ACCESS FULL       | ASSET                  | 36074 | 1021K|       | 38553   (2)| 00:07:43 |
|* 9 |         HASH JOIN               |                        | 90361 | 7059K| 4040K| 56578   (2)| 00:11:19 |
|* 10 |          HASH JOIN              |                        | 52977 | 3414K| 2248K| 50654   (2)| 00:10:08 |
|* 11 |           HASH JOIN             |                        | 39674 | 1782K|       | 40101   (2)| 00:08:02 |
|* 12 |            TABLE ACCESS FULL    | REGISTER               | 39439 | 1232K|       | 22584   (2)| 00:04:32 |
|* 13 |            TABLE ACCESS FULL    | SDP_LOGICAL_REGISTER   | 4206K|    56M|       | 17490   (2)| 00:03:30 |
|* 14 |           TABLE ACCESS FULL     | SERVICE_DELIVERY_POINT |   675K|    12M|       | 9412   (2)| 00:01:53 |
|* 15 |          TABLE ACCESS FULL      | SDP_LOGICAL_ASSET      | 1178K|    15M|       | 4262   (2)| 00:00:52 |
|* 16 |        INDEX RANGE SCAN         | IDX_NMI_ID_NK          |     2 |       |       |     2   (0)| 00:00:01 |
| 17 |      VIEW                       |                        | 39674 |   232K|       | 40101   (2)| 00:08:02 |
|* 18 |       HASH JOIN                 |                        | 39674 | 1046K|       | 40101   (2)| 00:08:02 |
|* 19 |        TABLE ACCESS FULL        | REGISTER               | 39439 |   500K|       | 22584   (2)| 00:04:32 |
|* 20 |        TABLE ACCESS FULL        | SDP_LOGICAL_REGISTER   | 4206K|    56M|       | 17490   (2)| 00:03:30 |
|* 21 |     TABLE ACCESS FULL           | METER_CONFIG_HEADER    | 3658 | 47554 |       |    19   (0)| 00:00:01 |
|* 22 |    TABLE ACCESS FULL            | METER_CONFIG_ITEM      | 7590 | 68310 |       |   112   (2)| 00:00:02 |
Predicate Information (identified by operation id):
   2 - access("METER_CONFIG_HEADER_SK"="METER_CONFIG_HEADER_SK")
   3 - access("NETWORK_TARIFF_CD"="NETWORK_TARIFF_CD")
   4 - access("SERVICE_DELIVERY_POINT_SK"="TMP"."SERVICE_DELIVERY_POINT_SK")
   5 - filter("ROW_CURRENT_IND"='Y' AND ("NMI_STATUS_CD"='A' OR "NMI_STATUS_CD"='D'))
   7 - access("ASSET_CD"="EQUIP_CD" AND "SAP_INT_LOG_DEVICE_SK"="SAP_INT_LOG_DEVICE_SK")
   8 - filter("ROW_CURRENT_IND"='Y')
   9 - access("SERVICE_DELIVERY_POINT_SK"="SERVICE_DELIVERY_POINT_SK")
10 - access("SERVICE_DELIVERY_POINT_SK"="SERVICE_DELIVERY_POINT_SK")
11 - access("SAP_INT_LOGICAL_REGISTER_SK"="SAP_INT_LOGICAL_REGISTER_SK")
12 - filter("REGISTER_TYPE_CD"='C' AND (SUBSTR("REGISTER_ID_CD",1,1)='4' OR
              SUBSTR("REGISTER_ID_CD",1,1)='5' OR SUBSTR("REGISTER_ID_CD",1,1)='6') AND "ROW_CURRENT_IND"='Y')
13 - filter("ROW_CURRENT_IND"='Y')
14 - filter("ROW_CURRENT_IND"='Y')
15 - filter("ROW_CURRENT_IND"='Y')
16 - access("NMI_SK"="NMI_SK")
18 - access("SAP_INT_LOGICAL_REGISTER_SK"="SAP_INT_LOGICAL_REGISTER_SK")
19 - filter("REGISTER_TYPE_CD"='C' AND (SUBSTR("REGISTER_ID_CD",1,1)='1' OR
              SUBSTR("REGISTER_ID_CD",1,1)='2' OR SUBSTR("REGISTER_ID_CD",1,1)='3') AND "ROW_CURRENT_IND"='Y')
20 - filter("ROW_CURRENT_IND"='Y')
21 - filter("ROW_CURRENT_IND"='Y')
22 - filter("ROW_CURRENT_IND"='Y' AND "CONROL_REGISTER"='X')
ENVIRONMENT B
Plan hash value: 2826260434
| Id | Operation                            | Name                   | Rows | Bytes | Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT                     |                        |     1 |   181 |   103K (2)| 00:20:47 |
|   1 | HASH UNIQUE                         |                        |     1 |   181 |   103K (2)| 00:20:47 |
|* 2 |   HASH JOIN ANTI                     |                        |     1 |   181 |   103K (2)| 00:20:47 |
|* 3 |    HASH JOIN                         |                        |     1 |   176 | 56855   (2)| 00:11:23 |
|* 4 |     HASH JOIN                        |                        |     1 |   163 | 36577   (2)| 00:07:19 |
|* 5 |      TABLE ACCESS BY INDEX ROWID     | ASSET                  |     1 |    44 |     4   (0)| 00:00:01 |
|   6 |       NESTED LOOPS                   |                        |     1 |   131 | 9834   (2)| 00:01:59 |
|   7 |        NESTED LOOPS                  |                        |     1 |    87 | 9830   (2)| 00:01:58 |
|   8 |         NESTED LOOPS                 |                        |     1 |    74 | 9825   (2)| 00:01:58 |
|* 9 |          HASH JOIN                   |                        |     1 |    52 | 9820   (2)| 00:01:58 |
|* 10 |           TABLE ACCESS BY INDEX ROWID| METER_CONFIG_HEADER    |     1 |    14 |     1   (0)| 00:00:01 |
| 11 |            NESTED LOOPS              |                        |     1 |    33 |   116   (2)| 00:00:02 |
|* 12 |             TABLE ACCESS FULL        | METER_CONFIG_ITEM      |     1 |    19 |   115   (2)| 00:00:02 |
|* 13 |             INDEX RANGE SCAN         | SYS_C00116570          |     1 |       |     1   (0)| 00:00:01 |
|* 14 |           TABLE ACCESS FULL          | SERVICE_DELIVERY_POINT |   723K|    13M| 9699   (2)| 00:01:57 |
|* 15 |          TABLE ACCESS BY INDEX ROWID | NMI                    |     1 |    22 |     5   (0)| 00:00:01 |
|* 16 |           INDEX RANGE SCAN           | IDX_NMI_ID_NK          |     2 |       |     2   (0)| 00:00:01 |
|* 17 |         TABLE ACCESS BY INDEX ROWID | SDP_LOGICAL_ASSET      |     1 |    13 |     5   (0)| 00:00:01 |
|* 18 |          INDEX RANGE SCAN            | IDX_SLA_SDP_SK         |     2 |       |     2   (0)| 00:00:01 |
|* 19 |        INDEX RANGE SCAN              | IDX_A_SAPINTLOGDEV_SK |     2 |       |     2   (0)| 00:00:01 |
|* 20 |      TABLE ACCESS FULL               | REGISTER               | 76113 | 2378K| 26743   (2)| 00:05:21 |
|* 21 |     TABLE ACCESS FULL                | SDP_LOGICAL_REGISTER   | 5095K|    63M| 20245   (2)| 00:04:03 |
| 22 |    VIEW                              |                        | 90889 |   443K| 47021   (2)| 00:09:25 |
|* 23 |     HASH JOIN                        |                        | 90889 | 2307K| 47021   (2)| 00:09:25 |
|* 24 |      TABLE ACCESS FULL               | REGISTER               | 76113 |   966K| 26743   (2)| 00:05:21 |
|* 25 |      TABLE ACCESS FULL               | SDP_LOGICAL_REGISTER   | 5095K|    63M| 20245   (2)| 00:04:03 |
Predicate Information (identified by operation id):
   2 - access("SERVICE_DELIVERY_POINT_SK"="TMP"."SERVICE_DELIVERY_POINT_SK")
   3 - access("SERVICE_DELIVERY_POINT_SK"="SERVICE_DELIVERY_POINT_SK" AND
              "SAP_INT_LOGICAL_REGISTER_SK"="SAP_INT_LOGICAL_REGISTER_SK")
   4 - access("ASSET_CD"="EQUIP_CD")
   5 - filter("ROW_CURRENT_IND"='Y')
   9 - access("NETWORK_TARIFF_CD"="NETWORK_TARIFF_CD")
10 - filter("ROW_CURRENT_IND"='Y')
12 - filter("ROW_CURRENT_IND"='Y' AND "CONROL_REGISTER"='X')
13 - access("METER_CONFIG_HEADER_SK"="METER_CONFIG_HEADER_SK")
14 - filter("ROW_CURRENT_IND"='Y')
15 - filter("ROW_CURRENT_IND"='Y' AND ("NMI_STATUS_CD"='A' OR "NMI_STATUS_CD"='D'))
16 - access("NMI_SK"="NMI_SK")
17 - filter("ROW_CURRENT_IND"='Y')
18 - access("SERVICE_DELIVERY_POINT_SK"="SERVICE_DELIVERY_POINT_SK")
19 - access("SAP_INT_LOG_DEVICE_SK"="SAP_INT_LOG_DEVICE_SK")
20 - filter((SUBSTR("REGISTER_ID_CD",1,1)='4' OR SUBSTR("REGISTER_ID_CD",1,1)='5' OR
              SUBSTR("REGISTER_ID_CD",1,1)='6') AND "REGISTER_TYPE_CD"='C' AND "ROW_CURRENT_IND"='Y')
21 - filter("ROW_CURRENT_IND"='Y')
23 - access("SAP_INT_LOGICAL_REGISTER_SK"="SAP_INT_LOGICAL_REGISTER_SK")
24 - filter((SUBSTR("REGISTER_ID_CD",1,1)='1' OR SUBSTR("REGISTER_ID_CD",1,1)='2' OR
              SUBSTR("REGISTER_ID_CD",1,1)='3') AND "REGISTER_TYPE_CD"='C' AND "ROW_CURRENT_IND"='Y')
25 - filter("ROW_CURRENT_IND"='Y')Edited by: abhilash173 on Feb 24, 2013 9:16 PM
Edited by: abhilash173 on Feb 24, 2013 9:18 PM

Hi Paul,
I misread your question initially .The system stats are outdated in both ( same result as seen from aux_stats) .I am not a DBA and do not have access to gather system stats fresh.
select * from sys.aux_stats$
SNAME     PNAME     PVAL1     PVAL2
SYSSTATS_INFO     STATUS     NULL     COMPLETED
SYSSTATS_INFO     DSTART     NULL     02-16-2011 15:24
SYSSTATS_INFO     DSTOP     NULL     02-16-2011 15:24
SYSSTATS_INFO     FLAGS     1     NULL
SYSSTATS_MAIN     CPUSPEEDNW     1321.20523     NULL
SYSSTATS_MAIN     IOSEEKTIM     10     NULL
SYSSTATS_MAIN     IOTFRSPEED     4096     NULL
SYSSTATS_MAIN     SREADTIM     NULL     NULL
SYSSTATS_MAIN     MREADTIM     NULL     NULL
SYSSTATS_MAIN     CPUSPEED     NULL     NULL
SYSSTATS_MAIN     MBRC     NULL     NULL
SYSSTATS_MAIN     MAXTHR     NULL     NULL
SYSSTATS_MAIN     SLAVETHR     NULL     NULL

Different Info Packages for the same data source.

Hi Team,
I have a question, which i asked before that but i ended up with different solution.
I want to load 02.2002 to till date into ODS. Data source is 0FI_AR_10.
My boss wants in this way .
1) one infopackage for 02.2002 to 02.2005 with init.
2) one infopack for 03.2005 to 07.2008 with init for the same datasource.
3) one info pack with no selection criteira.
What will be the result ?
My guess is, Once we do init for the time period 02.2002 to 02.2005 ,
the system with note the timepreiod for the Datasource.
When i try to do Init for the second, the system will say init already exits for the data source. And it will not allow me to do init for the second selection.
Correct me if i am wrong.
Regards,
-Sonti-

Your planned InfoPackages:
- 1) one infopackage for 02.2002 to 02.2005 with init.
- 2) one infopack for 03.2005 to 07.2008 with init for the same datasource.
- 3) one info pack with no selection criteira.
As the selection criteria of package 1) & 2) do not overlap, is it possible.
For package 3), you need to do it as delta update instead of initialisation. Package 3) with no selection criteria overlaps with package 1) & 2).
Refer to the Help Documentation, which explains this quite clearly.
Link: [Maintaining InfoPackage - Tab Page: Updating|http://help.sap.com/saphelp_nw70/helpdata/en/e3/e60138fede083de10000009b38f8cf/frameset.htm]
>For selection criteria that do not overlap, several initialization criteria are possible for initializing the delta process when scheduling InfoPackages for data from an SAP system. This gives you the option of loading the relevant data for the delta process, step by step into the Business Information Warehouse. For example, you can load the data into BI for cost center 1000 in the first step, and the data for cost center 2000 in the second step.
>A delta requested after several initializations, contains the super set of all the successful initial selections as a selection condition. This selection condition can then no longer be changed for the delta.
Hope this help.

How to handle Multiple date formats for the same date field in SQL*Loader

Dear All,
I got a requirement where I need to get data from a text file and insert the same into oracle table.
I am using SQL*Loader to populate the data from the text file into my table.
The file has one field where I am expecting date date data in multiple formats, like dd/mon/yyyy, yyyy/dd/mon, yyyy/mon/dd, ,mm/dd/yyyy, mon/dd/yyyy.
While using SQL*Loader, I can see Loading is failing for records where we have formats like yyyy/dd/mon, yyyy/mon/dd, mon/dd/yyyy.
Is there any way in SQL*Loader where we can mention all these date formats so that this date data should go smoothly into the underlying date column in the table.
Appreciate your response on this.
Thanks,
Madhu K.

The point being made was, are you sure that you can uniquely identify a date format from the value you receieve? Are you sure that the data stored is only of a particular limited set of formats?
e.g. if you had a value of '07/08/03' how do you know what format that is?
It could be...
7th August 2003 (thus assuming it's DD/MM/RR format)
or
8th July 2003 (thus assuming it's MM/DD/RR format)
or
3rd August 2007 (thus assuming it's RR/MM/DD format)
or
8th March 2007 (thus assuming it's RR/DD/MM format)
or even more obscurely...
3rd July 2008 (MM/RR/DD)
or
7th March 2008 (DD/RR/MM)
Do you have any information to tell you what formats are valid that would allow you to be specific and know what date format is meant?
This is a classic example of why dates should be stored on the database using DATE datatype and not VARCHAR2. It can lead to corruption of data, especially if the date can be entered in any format a user wishes.

Distribution working differently for the same report

Hello all,
I created a template with 3 reports, each of which opens for 4 plants.
Then, when I schedule the offline distribution process, 2 of the reports are generated correctly for all plants, while the 3rd has a strange behavior. This 3rd report has 2 sheets and opens correctly for 2 of the plants, while for the other 2:
- in one sheet, the formulas are not converted to offline mode (like _epmOfflineCondition_ ) giving an "#Error, no current connection." message and the sheet is not protected; however, the report data is correct.
- in the other sheet, everything works ok and the sheet is protected;
Any thoughts? Thanks,
Ana-Maria

Thanks Ashok,
but unfortunately the above points are not applicable to the issue indicated:
1. Log off&log on has no effect since this problem appears on all PCs and always for the same data group.
2. The data group is available in the model cube and master data.
3. We are using the ADMIN user to execute the process so we have all authorizations (also, these are defined at Country level and only one Plant from a Country is not working).
4. The formula is correct.
5. Since the report executes correctly as a standalone report and works for other plants, I don't believe there is an issue with it.
The issue still persists.
Ana-Maria

OBIEE 11g - Current year date and the same date in Previous year

Hi Experts,
I have an attribute say RECEIPT NO, i want to display the "No of Receipts" i.e(count(receipt no)) for any given date in the current year as well as for the same date in previous year.
Please suggest me how to achieve this in 11g.
Thanks

Hi Veeravalli,
Thanks for your prompt help.
Could you please ellobarate this. I have to display the count(receipt_no) for the last year same date.
Thanks

Multiple reads of the same data from Multiprovider by Query (Bex)

Hello, guys!
We're having issue with performance of a query built on Multiprivider. During our investigation, we've found out that within one run of a Query, it several times refers to InfoProvider for the same data (see image attached).
Do you have ideas what can be a reason for multiply reads of the same data from Multipvovider?

Hello Nikita,
By "copy of a query" i meant something like this as shown below :
*Kindly click on the screenshot for a better view.
1) See the highlighted portions below in the screenshot . See Query 2 highlighted and name of the BEx query highlighted.
2) See the highlighted portions . See Query 3 highlighted and name of the BEx query highlighted.
As you can see from the above screenshots i have used the same BEx query 2 times by the name of Query 2 & Query 3 . Infact i have not attached the complete screenhsot . In that i have used it 6 times.
I have to analyze this a bit in detail but what i am guessing is that when this WEBi is called the single BEx is also called multiple times. And hence it hits the Info Provider multiple times resulting in a decreased performance.
But this does not mean that this is wrong approach. There are various areas where you can improve for example :
1) Either improve your BEx query if possible or use aggregates or something like that .
2) Use the Query stripping setting in WEBi so that unused dimensions and measures are not pulled resulting in an improved performance. It's switched on by default.
Thanks!!
Regards,
Ashutosh Singh

How to load member for "sales same date last year"?

I need to load a member in Measures named "PriorYrSales" with "Sales" for the same date last year as today's date. Thus, retrieving "PriorYrSales" for 2/10/2002 would return the sales amount for 2/10/2001. Since days roll-up to months, quarters, years, it would be easy to determine how we're doing compared to the same time last year.Data is loaded each day for a date range from the current date and the preceding x days. Substitution variables are available for the beginning and ending date and the same dates for last year.For example: Data is loaded from beginning date of 2/01/2002 through ending date of 2/10/2002.The prior year date variables contain 2/01/2001 and 2/10/2001.The time period dimension is as follows:FY01->Jan2001-->01012001 (Alias: 1/01/2001)-->01022001 (Alias: 1/02/2001)-->all the dates in Jan->Feb2001-->02012001 (Alias: 2/01/2001)-->02022001 (Alias: 2/02/2001)-->all the dates in Febetc.FY02->Jan2002-->01012002 (Alias: 1/01/2002)-->01022002 (Alias: 1/02/2002)-->all the dates in Jan->Feb2002-->02012002 (Alias: 2/01/2002) -->02022002 (Alias: 2/01/2002)-->all the dates in Febetc.Thanks your any and all suggestions.Phil

Perhaps I wasn't clear in the first post. The intent is to easily compare sales for a current date/period to the same date/period last year. Neither Excel nor Analyzer provide a method that I'm aware of to retrieve data as follows:-------------------------------------Period Sales PriorYrSales Diff4/15/2002 1,000 900 100-------------------------------------(900 is sales for 4/15/2001)(100 is the calculated difference.)Nor can I do this:-------------------------------------Period Sales Period Sales Diff4/15/2002 1,000 4/15/2001 900 100-------------------------------------What Excel and Analyzer do allow is:-------------------------------------Period Sales 4/15/2002 1,0004/15/2001 900-------------------------------------I readily acknowledge that the data is redundant but I can't think of another option that will allow Excel and Analyzer to easily retrieve the values for comparison. If the PriorYrSales member can be loaded then the users can compare years, quarters, months and days quite easily.My challenge is knowing how use a calc script to derive prior year dates that correspond to current year dates. Something like:PriorYrSales->04152002 = Sales->04152001I've considered arrays but I've never used them and the documentation is not helpful enough for me.Thanks for your response.Phil

Multiple Purchase Requisition generate in the same date WHY ?

Hi All,
In MD04 Tcode for one Material No , I can see multiple PR getting generated for the same Date !! I would like to know based on what settings same date is appearing ?? and also please tell how to combine all this PR into one PR !!! Please guide me
Thanks & Regards,
Vinoth.

Hi,
Che on it:-
Re: Third party Drop Ship
Re: Single PO for Multiple PR
Re: MD04 + Auto PR generation
pherasath

Quota is displayed twice in 2006 for the same date

Similar Messages

Maybe you are looking for