period meaning of time profile

[Former Member]

Dear PP experts,

I would like to change time profile configuration on t-cd:OPD2.

But I am not clear about each period meaning.

Can you please tell me the difference between database read period, evaluation period, planning period and dispatching of backlog ?

Thanks in advance.

[marianoc · Accepted solution]

Hi,

This profile is used in the overal profile for Capacity Leveling profiles.

You can read the help of the customizing point here:

Define time profile
In this step you define time profiles for capacity leveling and the extended evaluation.
With the time profile, you specify various important time periods:

Database read period
The database read period specifies the period in which capacity requirements are read from the database. All requirements are accessed which are partially or completely within the database read period.



Evaluation period
The evaluation period specifies the period over which data is formatted and displayed. The evaluation period must lie within the database read period.



Planning period
The planning period defines the period in which the SAP system can carry out planning. The planning period is smaller than or equal to the evaluation period.
You cannot move operations outside the planning period. Equally, when automatic finite scheduling is carried out for an operation the system only searches for a new date within the planning period.



Date for dispatching backlog
The date for dispatching the backlog is of importance in period-related planning.
You use the date for dispatching the backlog to determine the date backlogs are to be allocated.
The following types of entry are available:
Actual date specifications
These date specifications (for example, calendar day, calendar year) are only useful in the profiles in exceptional cases.

Relative date specifications
These date specifications (for example, number of calendar days, number of calendar years) are always calculated from the current day.
For every period, you can specify in what form you want to enter the date by using the respective field "Type of entry".

Example
Evaluation period

Type of entry J (calendar month)
Start date    0
Finish date   2
Current date: 06/09/1994

In this case, the evaluation is carried out for the period from 6/1/1994 until 8/31/1994.

Note

Specifications in posting periods and factory calendar days are not possible since a plant would have to be specified in this case.
You cannot delete the time profiles that are contained in the standard system.


Standard settings
Time profiles are predefined in the SAP standard package.

Actions
Define time profiles according to your requirements.

Kind Regards,

Mariano

[kiran_kumar179]

Ostu,

The database read period specifies the period in which capacity requirements are read from the database. All requirements are accessed which are partially or completely within the database read period.

The evaluation period specifies the period over which data is formatted and displayed. 

The evaluation period must lie within the database read period.

The planning period defines the period in which the SAP system can carry out planning. 

The planning period is smaller than or equal to the evaluation period. You cannot move operations outside the planning period. Equally, when automatic finite scheduling is carried out for an operation the system only searches for a new date within the planning 

period.

The date for dispatching the backlog is of importance in period-related planning.

We use the date for dispatching the backlog to determine the date backlogs are to be 

allocated.

Let us see an example for database period In above if you enter Entry type as G which is number of calender days and current date is 17th Sep and You have start date as -10 and Finish date as 30 then this generates database read period from  7th Sep to 7th Oct it means during capacity levelling with above setting all requirements which are falling in between above dates are only read from database.

BR
KK