Time calculation class

hello there i was wondering is there any class which will change the hour into minutes and back to hours.

No, but it wouldn't take more than three minutes to write one.

Similar Messages

Time evaluation classes

Hi Gurus,
Can any one help by giving some data on time evaluation classes. what exactly it means? what r they? my mail id is [email protected]
reward points will be given for all the helpful replies.
Thanks in advance
Regards
Swarup

hi,
check, this.
Time evaluation classes
In this IMG activity you assign the time evaluation class to the attendance types, in which you calculate payment for worked Sundays, leaves and public holidays.
Standard settings
The SAP standard system provides you with the following calculation class values:
10 Worked Sundays
11 Worked Leaves
12 Worked holidays
Activities
Determine the user wage types that are registered through the Attendance infotype (2001) and that apply in these cases.
Further notes
The time evaluation class defines the concept type to process (Sundays, leave or holidays). For that reason you already have values 10, 11 and 12 fixed, which are read from the MXPR rule, that processes the payments before mentioned.
thanks,
Time evaluation classes
In this IMG activity you assign the time evaluation class to the attendance types, in which you calculate payment for worked Sundays, leaves and public holidays.
Standard settings
The SAP standard system provides you with the following calculation class values:
10 Worked Sundays
11 Worked Leaves
12 Worked holidays
Activities
Determine the user wage types that are registered through the Attendance infotype (2001) and that apply in these cases.
Further notes
The time evaluation class defines the concept type to process (Sundays, leave or holidays). For that reason you already have values 10, 11 and 12 fixed, which are read from the MXPR rule, that processes the payments before mentioned.
Vasu.

Execution time calculation issue

Hi,
I have a proceudre which update the tables data and it will capture the execution time for each and every table.
For that i am using below procedure and its giving incorrect values. i.e., its giving end_time<start_time
PFB code(Line nos 25,26,33,73,7679,80 code for exeution time calculation) and output.
1 CREATE OR REPLACE PROCEDURE my_proc
2 IS
3 CURSOR c
4 IS
5 SELECT tablename, TYPE
6 FROM table_list;
7
8 TYPE emp_record IS RECORD (
9 empkey tab1.pkey%TYPE,
10 rid ROWID,
11 ID tab_join.ID%TYPE,
12 dt tab_join.dt%TYPE
13 );
14
15 TYPE emp_type IS TABLE OF emp_record
16 INDEX BY BINARY_INTEGER;
17
18 v_emp emp_type;
19
20 TYPE emp_type_rowid IS TABLE OF ROWID
21 INDEX BY BINARY_INTEGER;
22 tab_no Number:=0;
23 emp_rowid emp_type_rowid;
24 r_cur sys_refcursor;
25 v_start_time TIMESTAMP; /** Added for time calculation*/
26 v_end_time TIMESTAMP; /** Added for time calculation*/
27 string1 VARCHAR2 (1000) := 'SELECT b.empkey, b.ROWID rid, a.id id, a.dt dt FROM emp_base a,';
28 string2 VARCHAR2 (1000) := ' b WHERE a.empkey = b.empkey';
29 rowcnt Number;
30BEGIN
31 FOR c1 IN c
32 LOOP
33 tab_no:=tab_no+1;
34 v_start_time := SYSTIMESTAMP; /** Added for time calculation*/
35 BEGIN
36 string_d := string1 || c1.tablename || string2;
37
38 OPEN r_cur FOR string_d;
39
40 LOOP
41 FETCH r_cur
42 BULK COLLECT INTO v_emp LIMIT 50000;
43
44 IF v_emp.COUNT > 0
45 THEN
46 FOR j IN v_emp.FIRST .. v_emp.LAST
47 LOOP
48 emp_rowid (j) := v_emp (j).rid;
49 END LOOP;
50
51 upd_string := ' UPDATE ' || c1.tablename || ' SET id = ' || v_emp (1).ID || 'WHERE ROWID = :emp_rowid';
52 FORALL i IN emp_rowid.FIRST .. emp_rowid.LAST
53 EXECUTE IMMEDIATE upd_string
54 USING emp_rowid (i);
55 rowcnt := rowcnt + emp_rowid.COUNT;
56 END IF;
57
58 EXIT WHEN v_emp.COUNT < 50000;
59 v_emp.DELETE;
60 emp_rowid.DELETE;
61 END LOOP;
62
63 v_emp.DELETE;
64 emp_rowid.DELETE;
65
66 CLOSE r_cur;
67 EXCEPTION
68 WHEN OTHERS
69 THEN
70 DBMS_OUTPUT.put_line (SQLERRM);
71 END;
72
73 v_end_time := SYSTIMESTAMP; /** Added for time calculation*/
74
75 INSERT INTO exec_time
76 VALUES (tab_no||' '||c1.tablename, v_start_time, v_end_time, v_end_time - v_start_time, rowcnt); /** Added for time calculation*/
77
78 COMMIT;
79 v_start_time := NULL; /** Added for time calculation*/
80 v_end_time := NULL; /** Added for time calculation*/
81 rowcnt := 0;
82 END LOOP;
83END;
Output :
TableName: exec_time
"TABLE_NAME"      "START_TIME"     "END_TIME"      "EXCUTION_TIME"      "NO_OF_RECORDS_PROCESSED"
TAB7      5/29/2013 10:52:23.000000 AM      5/29/2013 10:52:24.000000 AM      +00 00:00:00.521707      773
TAB5      5/29/2013 10:52:18.000000 AM      5/29/2013 10:52:15.000000 AM      -00 00:00:03.381468      56525
TAB6      5/29/2013 10:52:15.000000 AM      5/29/2013 10:52:23.000000 AM      +00 00:00:08.624420      49078
TAB2      5/29/2013 10:51:54.000000 AM      5/29/2013 10:51:42.000000 AM      -00 00:00:11.932558      529
TAB4      5/29/2013 10:51:47.000000 AM      5/29/2013 10:52:18.000000 AM      +00 00:00:31.208966      308670
TAB1      5/29/2013 10:51:45.000000 AM      5/29/2013 10:51:54.000000 AM      +00 00:00:09.124238      65921
TAB3      5/29/2013 10:51:42.000000 AM      5/29/2013 10:51:47.000000 AM      +00 00:00:04.502432      12118
Issue: I am getting execution time in negitive values because end_time<start_time coming.
Please suggest me how to resolve this.
Thanks.

Welcome to the forum!!
Please read {message:id=9360002} from the FAQ to know the list of details (WHAT and HOW) you need to specify when asking a question.
I primarily hate 3 things in your code
1. The way you have used BULK update which is totally unnecessary
2. COMMIT inside LOOP
3. The use of WHEN OTHERS exception.
Your code can be simplified like this
create or replace procedure my_proc
is
   v_start_time timestamp;
   v_end_time   timestamp;
   v_rowcnt     integer;
begin
   for c1 in (
                 select rownum tab_no
                      , tablename
                      , type
                   from table_list
   loop
      sql_string := q'[
                              merge into #tablename# a
                              using (
                                      select id, dt
                                        from emp_base
                                    ) b
                                 on (
                                      a.empkey = b.empkey
                                when matched then
                                    update set a.id = b.id;
      sql_string := replace(sql_string, '#tablename#', c1.tablename);
      v_start_time := systimestamp;
      execute immediate sql_string;
      v_end_time   := systimestamp;
      v_rowcnt     := sql%rowcount;
      insert into exec_time
           values
                c1.tab_no || ' ' || c1.tablename
              , v_start_time
              , v_end_time
              , v_end_time - v_start_time
              , v_rowcnt
   end loop;
   commit;
end; In the INSERT statement on the table EXEC_TIME try to include the column list.
NOTE: The above code is untested.

How is Processing time calculated in Simulation

Hi,
How is processing time calculated for every simulation-relevant object?
say for example,
i have 2 objects of person type (p1 and p1)
4 human tasks (T1, T2, T3, T4)
T1 assigned to p1, processing time 2hrs
T2 assigned to p1, processing time 2hrs
T3 assigned to p2, processing time 2hrs
T4 assigned to p2, processing time 2hrs
start --> T1(p1) --> T2(p1) --> T3(p2) --> T4(p2) --> end
Have not set any other simualtion parameters. now,
* Duration for simulation is set to 6hrs,
T1, T2, and T3 are getting processes once, but start event is getting processed twice
# Why is start event getting processed second time?
# Will this take any processing time..
* Duration for simulation set to 7hrs,
start event and T1 gets processed 2 times, T2 and T3 once..
and the total processing time becomes *8hrs*..
# At wht point of time does the second processing of T1 start.
# If it is not after after the completion of one full process cycle, in this case, why not the second processing start at the end # of 2nd hour, or 4th hour.
Thanks,
Vishnupriya

Hi Vishnupriya,
"Why is start event getting processed second time?"Can you check the "Frequency" attribute of your start event? There you can specify how often the process will be triggered.
"At wht point of time does the second processing of T1 start."You should be able to check it in the Processes (det.). It provides an overview regarding the process instances started during the simulation run. Furthermore you can check the Events (det.) category.
Best regards,
Danilo

Processing type/time type class

Hi All,
I have 10 attendance type of which 5 productive hrs and 5 non productive hrs and 5 absence type.
I have assigned all these in V_554S_E, but i dont know what we have to assign in (Processing type/time type class)
and one more thing T555Y wht is the (Processing type/time type class) number i have to assign
Please suggest.
Thanks
Veer

I solved this issue my self.
I have assigned att/ ab to time type sucessfully.
Thanks
Veer

Ess Leave Request -Change in Time calculation without changing work schedu

Hi All,
We are implementing a ESS Leave Request in EP6 with backend HR ECC5.0.
The time calculation is taken from the Work schedule rule in
HR backend which is 24*7.
For example if the leave taken is for 2 days-systems calculates as 24*2=48 hrs
but in actual the requirement is to calculate 2*8 =16 hrs without changing
the Work Schedule in 2001 infotype in HR Backend.
Can we do this change through
1.Validation in portal itself
2.Changing the RFC PT_ARQ_REQUEST_CHECK
3.Changing the Absence Types
Regards
Anand.

Hello,
Please use:
programming
but without the spaces before and after } and {
Testing:
programming
regards
Rick Bakker
Hanabi Technology

Time Constraint Classes.

Hi All,
Pls let me know the concepts for Time Constraints classes.
Regards
Rajesh

A time constraint indicates whether more than one infotype record may be
available at one time. The following time constraint indicators are
permissible:
     -   1: An infotype record must be available at all times. This
         record may have no time gaps. You may not delete the record last
         stored on the database because all records of this infotype
         would otherwise be deleted.
     -   2: Only one record may be available at one time, but time gaps
         are permitted.
     -   3: Any number of records may be valid at one time, and time gaps
         are permitted.
Other possible time constraint indicators are as follows:
     -   A: Only one record may ever exist for this infotype. It is valid
         from 01/01/1800 to 12/31/9999. Splitting is not permissible.
         View V_T582B Infotypes Which are Created Automically controls
         whether the system automatically creates the infotype record for
         an employee hiring or an applicant data entry action.
         Infotypes with time constraint A may not be deleted.
     -   B: Only one record may ever exist for this infotype. It is valid
         from 01/01/1800 to 12/31/9999. Splitting is not permissible.
         Infotypes with time constraint B may be deleted.
     -   T: The time constraint varies depending on the subtype.
     -   Z: Refers to time management infotypes. The time constraint for
         these infotypes depends on the time constraint class defined in
         view V_T554S_I Absence: General Control. Collision checks are
         defined in view V_T554Y Time Constraint Reaction.
Regards
...Sadhu

Time Constraint Class

What is the number (0 to 7) stands for time constraint class in absence for the screen number 2001. I have a leave type CL (causual leave). What time constraint class shall i assign to it.
Regards,
Chinmay

for ur info alreadt raghu has given the answer any way check this tooo
A: Only one record may ever exist for the infotype (from 01/01/1800 - to 31/12/9999). Infotypes with time constraint A may not be deleted.
B: Only one record may ever exist for the infotype (from 01/01/1800 - to 31/12/9999). Infotypes with time constraint B may be deleted.
T: Time constraint varies depending on subtype.
Z : Refers to time management infotypes.Time constraint for these ITs depend on time constraint class in table V_T554S_I. Collision checks : V_T554Y
Apart from 1, 2, 3 there are some other types of Time Constraints: A, B, T, Z.
The Infotypes with TC type A must exist, must have only one record in its lifetime, and these ITs cannot be deleted.
Example: IT0003 (Payroll Status)
The Infotypes with TC type B must have only one record in its lifetime.
Example: IT0031 (Reference Personnel numbers)
The Infotypes with TC type T will have subtypes, and the TC is based on the subtype.
Example: IT0009 (Bank Details)
The Time Mnagegement Infotypes will have TC type Z .
Example: IT2001 (Absences)
rule that determines whether collisions in time data are allowed, and if so, specifies how the system reacts to such collisions.
Time contraints comprise the following:
Time constraint classes that determine which collisions in time data records are allowed
Time constraint table that contains the time-based collisions allowed in the time data records
Time constraint indicator that displays whether a new data record that collides with an existing time data record can be transferred to the system or whether the transfer is prohibited
When you update an infotype, old data is not lost but archived for historical evaluation. The system records a specific period of validity for each infotype, This enables the system to store more than one infotype record at the same time, even if their validity periods overlap. This means that the time relationships between infotype records must be defined. The concept of time constraints enables you to do this.
HR master data uses the following three time constraints:
Time Constraint 1
For the entire time that the employee works at the enterprise, exactly one valid infotype record must exist. The validity periods of the individual records must not overlap. If a new record is created, the system automatically uses the start date of the new record as the delimitation date of the old record. Gaps are only allowed between the employeeu2019s entry date and the start date of the first record.
Time constraint 1 must be used for all of the infotypes containing information that must be available at all times. This is particularly true of personal and organizational assignment data.
If a record is delimited because of time constraint 1, the system displays an appropriate message.
Time Constraint 2
No more than one valid record can exist at any one time. Records with constraint 2 must not overlap. Their existence is not obligatory. If a new record is created, the system automatically delimits the previous record, if one exists.
If a record is delimited because of time constraint 2, the system displays an appropriate message.
Time Constraint 3
Any number of valid records can exist at any one time. The individual records do not conflict with each other.
Time Constraints:
When an info type is updated, the old data is not lost. Instead, it remains in the system so that you can perform historical evaluations. Each info type is stored with a specific validity period. This means that the system can contain more than one record of the same info type at the sometime, even if their validity periods coincide.
If you enter and save new information in an info type, the system checks whether the record already exists for this info type. If this is the case, the system reacts based on rules or TIME CONSTRAINTS set up for that particular info type or subtype.
Time Constraint 1: This is mandatory information that must be uniquely available, gaps are not allowed
Time Constraint 2: This is optional information that, if available, must be unique, gaps allowed.
Time Constraint 3: This is optional information that, if available, can exist more than once.

Time constraint classes and screen number for absence type

Hi all,
What should be the Time constraint classes and screen number for absence type.
The different absence types are annual leave, sick leave , study leave , personal leave, maternity leave , juryduty leave nad leave without pay etc
Kindly help.
Regards,

The time constaint class depends on the client requirement.
eg.if they want that a error needs to be generated while overlapping absences or warning message is required.
Time contraints comprise the following:
Time constraint classes that determine which collisions in time data records are allowed
Time constraint table that contains the time-based collisions allowed in the time data records
Time constraint indicator that displays whether a new data record that collides with an existing time data record can be transferred to the system or whether the transfer is prohibited
For screen number you will have to see if the is quota based deduction or just an absence. Here is the documentation of screen number from SAP
In the standard system, the following numbers are allocated to the screens:
1. 2000 - General absence
This screen is used for all absences which do not require special processing (such as paid leave of absence for getting married).
2. 2001 - Quota deduction
This screen is used for entering data on leave or time in lieu of overtime.
3. 2002 - Work incapacity
Use this screen for all absence types where continued pay should be taken into account automatically by the system.
4. Special screens have been developed for the following absence types:
2003 - maternity protection, parental leave
2004 - military and non-military service
2005 - work incapacity (Netherlands)
Please go through the documentation of the configuration.
Shrikant Basarkar

Time constraint class for Time infotype

Hi all,
Where is the table to create a new time constraint class? I know how to link the reaction rules, but not how to create a new digit?
Thanks

Hi,
Please maintain table V_554Y_B for 2005 TC class 00 and 2004 infotype.
Regards,
Dilek

Scout: Too much time calculating dirty regions

Hi All,
Frist of all, sorry for my English.
I have a problem with my AIR App, I'm developing for Android and iOS. In iOS works perfectly but on Android the performance is poor.
I checked with Scout and this is what i see:
I don't understand why it spends so much time calculating dirty regions but I didn't change anything on the DisplayList.
Edit: AS you can see in the screen the frames are 13 but in the next frames is over 200 frames and that repeats.
Can someone tell me how to interpret this results?
Thanks a lot.
Goratz
Mensaje editado por: goratz

The feature you are referring to exists in Logic but not in GarageBand (yet?). It is called the Marquee Tool that lets you drag a selection, and when hitting the delete key, that section of the Region(s) will be deleted, and the remaining part of the Region on the right will be moved to the left to close the gap (if you you have set the Drag Mode to "Shuffle L").
Hope that helps
Edgar Rothermich
http://DingDingMusic.com/Manuals/
'I may receive some form of compensation, financial or otherwise, from my recommendation or link.'

Using java.time.LocalDate class

Hello,
I am using the latest JDK8 build b87 and JDeveloper 11.1.2.1. In the editor, the code insight does not show the java.time.LocalDate class. When I use the LocalDate class, it is highlighted in red. However, I can compile and run the application fine. Other classes in the java.time package, for example, the Clock class is fine. I can use classes from the java.time subpackages fine. How can I fix this issue?
Thanks
Kishori

JDeveloper does not support JDK 8 as indicated by the certification matrix.
http://www.oracle.com/technetwork/developer-tools/jdev/index-091111.html
java.time.LocalDate being a new class, code insight does not support the class.

Warning Time calculation "Before Aggregation" is obsolete

Hi,
Recently in our project we have upgraded BW 3.0B to BI7.
After upgrade to BI7, when we run some of the reports we are getting a warning message as below -
Warning Time calculation "Before Aggregation" is obsolete.
Pls refer to the attachment.
Any of our satyam colleagues encounter this warning, if so what was the solution you applied.
Note : I found some notes in Forum like saying use ' Exception Aggregation' for the Before Aggregation.. etc etc., but my problem is in our project thre are many CKFs are there which are using 'Before Aggregation'.
Please let me know if you have any other alternatives.
Thanks !!!!!!!!!

Hi,
Try SAP notes 935903.
Symptom
Calculated Key Figures "Existance Indicator" with aggregation behaviour "Before Aggregation" will get now with NW 2004s warning popup "Time of calculation 'Before Aggregation' is obsolete" during execution.
this may be helpful.
thanks,
JituK

No time constraint reaction for infotype 2005 with time contraint class 00u2019

Hi,
We have a incident wherein employee is trying to put overtime, IT 2005 for the period when he is on standby IT 2004. It gives error u2018No time constraint reaction for infotype 2005 with time contraint class 00u2019.
Can anybody help?

Hi,
Please maintain table V_554Y_B for 2005 TC class 00 and 2004 infotype.
Regards,
Dilek

Entry screen for Time constraint class

Hi All,
What should be the "Entry screen and Time constraint class" in Determine Entry screen number for Time constraint class.
Please do help me.
Regards
Jagadeesh Reddy

Hai..
It depends on the requirement...
The following screens are currently available:
Absences: - 2000 Absences (general)   - 2001 Quota deduction
- Attendances:   - 2050 Quota deduction   - 2051 No quota deduction
And abt Time constraint ..
A: The old record is delimited.
E: It is not possible to create a new record.
W: It is possible to create a new record, but the old record
     remains unchanged.
N: As for indicator W, but no display.
Time Constraint Class is basically how u want the system to treat when u try to create a new record during a period where a record already exists..
Ram Manohar

Time calculation class

Similar Messages

Maybe you are looking for