Document Tracking with Time Constraint

Hi All
We have a requirment to track the statuses of Documents.
1) Documents have different statuses like Create, Checked, Send for Review, Approved etc
2) Each statuses have definite time period. For eg, after Create, the user responsible has 3 days to change it to "Checked" status
3) If the user responsible does not change to "Checked" a reminder mail should be triggered.
4) ie, the system should check whether the status has been changed to "Checked" after 3 days and if not , the mail should get triggered.
Please let me know whether we can have this in Std. DMS?
Also can we give time constraint to the status..? Like as I mentioned. give 5 days to change the status to "Checked" for a pariticular user responsible?
If not how can we do this?
Regards
Aby
Edited by: Aby Thomas on Nov 23, 2008 11:28 AM

Aby,
I think your case is a classic example for using the functionality of ECM ( Engineering Change Management) for document status management purposes.
ECM is a module created by SAP for enabling changes through coordinated change management procedures. Essentially there is a change master and ECR/ECO related to the process.
ECR is an engineering change request and ECO is an engineering change order. If I visualise in your case, an ECR can be created for changing the statuses of a document. Once the ECR go through various statuses you can decide to finally release the ECR which creates an ECO and executes it.
Also you can configure Messaging under DMS customisation to trigger messages for document status change.
You can also trigger a workflow event based on each status change as has been suggested by some colleagues here.
My advise would be to use as much as system functionality possible for each of these custom requests.
Sojan
Note : ECM can be used to trigger any coordinated changes in the sap system. It can be material, BOM,
DMS, you name it.

Similar Messages

IT0009 with Time Constraint 1

Hi Experts,
We have defined IT0009 with a subtype whcih has Time Constraint value as 1. Ideally we shouldn't be able to delete the IT0009 with Time Constraint 1. But still we are able to delete all records for It0009. Could anybody tell why this is happening?
Regards
Niharika

Hi,
Time constraint Class for infotype 0009 is T that means it will depend upon the subtype
If you change this time constraint class to one in table V_512W_D you will not be able to delete the recods for 0009.
Warm Regards,
Kapil Kaushal

Shipments/ Delivery Document tracking with Purchase Order

Dear all,
Please help me in finding all the shipments accessed against Purchase order or Delivery document information with the help of Purchase order.
Is it possible to track either of them using PO?
Please help....
Thanks & Regards,
Deepthi.

This is the sales forum, not purchasing forum.
You might be able to find something in EKBE table for PO. Also check the reference document field LIPS-VGBEL on the delivery. In sales it usually contains the sales order number, not sure if it will have the PO number for the inbound delivery. If not, check other fields in LIPS.
There is no direct link between shipments and orders. You'll need to find the delivery first and then the shipments for it. Delivery numbers will be in VTTP-VBELN, VTTP-TKNUM is the shipment number.

Position to Cost Center Relationship with time constraint 1

Hi,
I have a situation wherein:
1. There exists 2 records in PP01 with S-K relationship e.g. 01.01.2013 to 28.02.2013 and 01.03.2013 to 31.12.9999
2. There is a requirement to create another S-K record with dates; 01.02.2013-28.02.2013 automatically delimiting the first record.
Hence in all three records should exist
But when i try creating the 3rd record with end date 28.03.2013, it gives an information message stating End Date corrected to maximum end date of 31.12.9999. Thereby over writing the previous record(2nd one)
Do I need to change time constraint? Time constraint 1 should ideally allow this, as my records do not have gaps and exist at all times.
Please guide me through.

Hi Rohan,
Please check the table V_T777ZVK and the time constraint between S and A011 it must be 02 as per the standard system.
Then time constraint 2 means a maximum of one infotype record of the same type for the same object at the same time.
So if you change then end date must be 31.12.9999.
Regards,
Mithun K

Deleting an Infotype with Time Constraint 1 - programatically

Hi there,
We have a few records (IT0008), that need to be deleted. Unfortunately, when we use PA30 to delete, it won't delete the record(s). (Displays the error msg. "Record has time constraint 1" ) But, when we use the Utilities option in PA30 and go thru', it appears to successfully delete the same.
Now, could somebody pl. let us know how to go abt. doing the same programatically in ABAP ? I've tried looking at the FM's HR_MAINTAIN_MASTERDATA and HR_INFOTYPE_OPERATION (without much luck though....Although, SAP claims to have a documentation of these FM's, there is actually no proper docmn. at the Field level of these FMs)
Moreover, the FM HR_MAINTAIN_MASTERDATA returns exactly the same error "Record has time constraint 1".
Am a bit baffled as it is...
Any help would be gratefully acknowledged and appreciated.
Many thanks in anticipation,
Kind Regards,
RVS

there is no function module to do forbidden actions.
you only can do it with DELETE statement.
select single dbtab from t777d into gv_dbtab where infty = p_infty.
delete from (gv_dbtab) where pernr in p_pernr.
But you will have to be very carefully. There are "blind" infotypes behind some "normal" infotypes you will have to care about (i.e. 0000 -> 0302).

How can I prevent my mouse from erratic tracking with time machine on?, How can I rpevent my mouse from errtic tracking with time machine on?

I am running 10.8.5 on my MBP, and external monitor, keyboard and Magic Mouse. When I have Time Machine on the mouse is a pain to use use as it does not track properly. Is there anyway to have Time MAchine come on after 30 minutes of inactivity or something? I have yet to find that prference.
Thanks,
Jim

4 MB
I was doing that and I wanted something on Sept 18 and I shut it off on 8/20 and never turned it back on. So that will work but you have to remember to turn it it. There should almmost be an option somewhere to check that when the system goes to sleep, turn on Time Machine. All my PC back-up stuff has that option. Surprised TM doesn't. If raising the memory will do it it seems to cheap enough. Will that help you think. And I did just reboot my machine yesrday so it is pretty clean:).

IT2001 error, no time constraint reachion for infotype 2001 with tm const00

Dear Seriors,
When I try to add any absence, it show the below given error message (red colour), but if I hit the enter button it allows me to mark absence.
no time constraint reachion for infotype 2001 with time constraint class 001
What might be the reason?
Regards
ET

The time constraint class is used to check for collisions between Time Management infotypes (2001 to 2012). It allows you to specify different regulations for checking for collisions between individual subtypes.
The views Time Constraint Reaction to Time Management Infotypes (V_554Y_B) and Global Time Constraint Reaction (V_T554Y) contain rules for the collision check.
Please explore on this.

Time Constraints - Hr ABAP

Hi Everyone
Can anybody throw some light on the various time constraints used in the HR-ABAP and their relation to the infotypes.
Also specify if their some Transaction code from where we can get to know about the value's of the time constraints.
And also if their's any Table associated with them.
<REMOVED BY MODERATOR>
Thanks & Regards
Gaurav
Edited by: Alvaro Tejada Galindo on Feb 22, 2008 10:24 AM

Hi,
Please refer to the document below:
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 employees 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.
The system also contains the following time constraint indicators:
Time Constraint A
Infotypes with time constraint A must have no more than one record. The system automatically assigns the record a validity period from January 01, 1800 through December 31, 9999. This validity period cannot be subdivided.
Infotype records with time constraint A cannot be deleted.
Time Constraint B
Infotypes with time constraint B must have no more than one record. The system automatically assigns the record a validity period from January 01, 1800 through December 31, 9999. This validity period cannot be subdivided.
Infotype records with time constraint B can be deleted.
Time Constraint T
Infotype records with time constraint T depend on the subtype.
The principles of data entry and time constraints that apply to infotypes ensure that data is consistent and accurate. They also constitute the basis of time recording, payroll accounting, and reporting.
Thanks,
Sriram Ponna.

Any report to identify Time Constraint issues?

Hello,
Is there a report that I can run to get the employees and Infotype records with time constraint issues? So until last week, we had not turned on the PC-UI switch in T77S0 table. So the way it worked was, if in history there were 2 records with time gaps for Infotype with time constraint = 1, then it still allowed us to create new records. Now with the switch turned on, it gives an error. Once the historic records are corrected, it allows us to proceed. This is freaking out a lot of data specialists, and we were wondering if we can proactively identify the employees with these historic data inconsistencies and be able to correct them. Please let me know.
Thanks,
Nakul

Found it: RPUSCNTC
Thanks,
Nakul

How to make a custom infotype field the time constraint 1?????

Hello everyone I have this challenging question for gurus to answer it.
In custom created infotype for OM Ii have that field called ZZJOBID. When infotype was created I assigned the time constraint 1 for that infotype. That time constraint was base on OBJID not on ZZJOBID. Now the problem I am encountering is when I assign the 2nd ZZJOBID with time span 01011800-12319999 it overwrite the 1st assign ZZJOBID.
for the requirement reason I have to use PO10( not po03). If I change the time constraint to 3 which let me have the multiple records but I am losing the delimit and other functionality which comes with time constraint 1.

Suresh,
you are wright when you say that ' Time Constraint is for the Infotype/Subtype record and cannot be based off a field.' The OM infotype runs on bases of Object such as Organizational Unit, Job, etc... The point I was trying to draw is I am looking for a way that allow me to work via TC PO10 which run on Organizational Unit along with different ZZJOBID (with same begda and endda, if needed).

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 in 0008 infotype - any report for this siituation?

Hi,
I need some help to solution a big problem with time constraint and 0008 infotype.
Resume:
when I put the "2" time constraint, all the history of 0008 entries are changed...
For exemple:
Old (before "2" time constraint):
0 - 01.11.2007 - 31.12.9999 - 1000,00
0 - 01.10.2007 - 31.10.2007 - 900,00
NEW (after "2" time constraint):
0 - 01.11.2007 - 31.12.9999 - 1000,00
0 - 01.10.2007 - 01.10.2007 - 900,00
BR - 01.10.2007 - 01.10.2007 - 900,00
OR
0 - 01.11.2007 - 31.12.9999 - 1000,00
BR - 01.10.2005 - 01.10.2005 - 900,00
there aren't logical situation, all the records have a lot of errors...
Are there any report that corrects this situation????
Regards!!!!
Sandra

Daniel,
thanks for your response, and here's some more info:
- I've use the time contraint in multiple playlists, that have worked just fine before adding the time constraint;
- initially, after adding a time constraint (usually something like "time" "is less than" "10:00") everything seemed fine;
- only a few days later I noticed that my playlist hadn't been updated correctly. For example, one of my playlists consists of songs rated 4 and I limit to 50 songs by least recently played; with over 900 songs rated 4, after a song was played it should disappear from that playlist for a while but some songs didn't; also, sometimes I would see less than 50 songs in that playlist;
- after removing the time constraint the playlist updated correctly again
I know that the fact this only appears after a few days (or that I've only noticed it a few days later) makes it pretty tough to narrow down but that's all I've got so far.
Thanks again,
Heiko.

Time Constraints in HR Master Data

Hi
Can you please explain scenarios where Time Constraint 0 is used.
thanks
AP

Actually time constraint 0 exists.
It is "may only exist once".
Example:
IT0008 with time constraint 0.
The results will be a permanent record. Because it can exist only one and once. So, you cannot delimit, you cannot gap, you cannot duplicate.
Hope that explains.
Márcio Leoni
Edited by: Márcio Leoni on May 7, 2008 10:28 AM

Time constraints and Dialog module

1.What is the difference between the time constraints A(IT exists just once from 01 Jan 1800 to 12 Dec 9999) and B(IT exists for maximum of once from 01 Jan 1800 to 12 Dec 9999)?
2.What is the necessity of dialog module for a Infotype?

Time Constraint A and B
Infotypes with time constraint A & B must have no more than one record. The system automatically assigns the record a validity period from January 01, 1800 through December 31, 9999. This validity period cannot be subdivided.
Infotype records with time constraint A CANNOT be deleted.
Infotype records with time constraint B CAN be deleted.
The difference is check the BOLD TEXT.
As for ur second question, Function modules/dialog modules helps calling infotypes when called from any custom program ,and allows you to perform similar actions/tasks that you would perform on them from direct maintainance. ex: create,change, delete etc. also performing the same on multiple infotypes in a single go using a them is easier than writing a code to manipulate each single infotype.
SAP exposed these functions to be exploited as there will come many situations in business scenarios where you require to work with them by writing custom code.
hope its helpful

Document Tracking with Time Constraint

Similar Messages

Maybe you are looking for