Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
AA (Package) Application Development R/3 Assets: Master Data
Basic Data
| Data Element | EINZEL |
| Short Description | List assets |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | XFELD | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Assets |
| Medium | 15 | Individual list |
| Long | 20 | List assets |
| Heading | 55 | List assets |
Documentation
Definition
If this indicator is set all posted assets will be listed with the respective posted depreciation.
Supplementary Documentation - EINZEL 0001
Definition
Set this indicator, if you want the system to lost all posted assets with their transactions.
Supplementary Documentation - EINZEL 0002
Definition
Set this indicator, if you want the system to list all posted assets with their posted depreciation.
Supplementary Documentation - EINZELPER 0001
Use
The individual period can indicate the sequence number of the weekday for daily newspapers.
Example for dailies:
<----------- Frequency rule ---------------------> <--Ind.per.-->
Repetition period Grid Grid divider Grid factor Indiv.periods
-----------------------------------------------------------------
1) Week Day 1 1 1 - 7
Explanation: This frequency rule is required for daily
publications (each other frequency rule defines
a non-daily publication)
The individual periods have the following meanings:
1 = Monday (= start of 1st individual period)
2 = Tuesday (= start of 2nd individual period)
3 = Wednesday (= start of 3rd individual period)
...
Examples
Examples for creating/interpreting a generation rule
1. Daily edition
The frequency rule for a daily is always defined as follows:
- Repetition period : Week
- Grid : Day
- Grid divider : 1
- Grid factor : 1
This results in 7 individual periods:
- Indiv.period 1 : Monday
- Indiv.period 2 : Tuesday
...
- Indiv.period 7 : Sunday
The individual periods are displayed in the generation rule as a table containing the following columns:
- Individual period
- Planned issue type
- Actual issue type if date is day before a public holiday
- Actual issue type if date is a public holiday
- Actual issue type if day is day after a public holiday
- Actual issue type if day is two days after a public holiday
You must now define the issue types for each individual period:
Example of a generation rule (daily):
-------------------------------------
Ind.per. StITy ITyBPH ITyPH ITy1PH ITy2PH
-----------------------------------------------------------
1 MO SA MO MO
2 TU SA TU TU
3 WE SA WE WE
4 TH SA TH TH
5 FR SA FR FR
6 SA SA SA SA
7
Interpretation of this generation rule:
---------------------------------------
Individual period 1 (Monday):
-StITy =MO: A Monday issue is published as standard on Mondays
-ITyBPH=SA: If the Monday is the day before a public holiday
(Tuesday being the public holiday), an issue is
generated on Monday with the actual issue type
'Saturday' (the planned issue type remains 'Monday').
-ITyPH = : If the Monday is a public holiday, no issues are
generated that day.
-ITy1PH=MO: If the Monday is the day after a public holiday
(the public holiday being Sunday), an issue is
generated on Monday with the actual issue type
'Monday' (the planned issue type remains 'Monday').
-ITy2PH=MO: If the Monday is two days after a public holiday
(the public holiday being on Saturday), an issue
is generated on Monday with the actual issue type
'Monday' (the planned issue type remains 'Monday').
Individual period 2 (Tuesday):
-StITy =TU: A Tuesday issue is published as standard on Tuesdays
-ITyBPH=SA: If the Tuesday is the day before a public holiday
(Wednesday being the public holiday), an issue is
generated on Tuesday with the actual issue type
'Saturday' (the planned issue type remains 'Tuesday').
-ITyPH = : If the Tuesday is a public holiday, no issues are
generated that day.
-ITy1PH=TU: If the Tuesday is the day after a public holiday
(the public holiday being Monday), an issue is
generated on Tuesday with the actual issue type
'Tuesday' (the planned issue type remains 'Tuesday').
-ITy2PH=TU: If the Tuesday is two days after a public holiday
(the public holiday being on Sunday), an issue
is generated on Tuesday with the actual issue type
'Tuesday' (the planned issue type remains 'Tuesday').
The other individual periods are interpreted in the same way.
Meaning of factory calendar specified for edition:
When processing dailies, the factory calendar is not taken into account but simply the assigned public holiday calendar. (The factory calendar is defined in terms of working days and non-working days, so that Saturday is generally a non-working day but not a public holiday. Public holidays are defined in the public holiday calendar.) If the generation rule is defined for Saturday (individual period 6), generation is based on whether or not the Saturday is defined as a public holiday in the public holiday calendar. It is irrelevant in issue generation whether or not the Saturday in the factory calendar is a non-working day.
Supplementary Documentation - EINZELPER 0002
Use
Example for non-dailies:
<----------- Frequency rule ---------------------> <--Ind.per.-->
Repetition period Grid Grid divider Grid factor Indiv.periods
-----------------------------------------------------------------
2) Year Month 1 1 1 - 12
3) 1 2 1 - 6
4) 2 1 1 - 24
The individual periods are numbered consecutively.
Explanation on example 2):
This frequency rule defines a monthly publication that is
repeated annually (individual periods 1-12):
The individual periods have the following meanings:
1 = January 1 (= start of 1st individual period)
2 = February 1 (= start of 2nd individual period)
3 = March 1 (= start of 3rd individual period)
Explanation on example 2):
This frequency rule defines a two-monthly publication that
is repeated annually (individual periods 1-6 ):
The individual periods have the following meanings:
1 = January 1 (= start of 1st individual period)
2 = March 1 (= start of 2nd individual period)
3 = May 1 (= start of 3rd individual period)
...
Explanation on example 3):
This frequency rule defines a publication that appears twice
a month and is repeated annually (individual periods 1-24):
The individual periods have the following meanings:
1 = January 1 (= start of 1st individual period)
2 = January 1 (= start of 1st individual period)
3 = February 1 (= start of 2nd individual period)
4 = February 1 (= start of 2nd individual period)
5 = March 1 (= start of 3rd individual period)
6 = March 1 (= start of 3rd individual period)
...
A frequency rule with a grid factor greater than 1
must separate publication dates by specifying time offsets
and absolute times, since generation could not otherwise
be performed for unique publication dates (for example,
the system would determine the publication date January 1
for individual periods 1 and 2 if no further data was
specified, so that the publication date would not be
unique and an error would occur in automatic generation).
Examples
Examples for creation and interpretation of a generation rule
Example for a non-daily edition
The frequency rule is explained here as it would be for publication:
- Repetition period : Year
- Grid divider : 1
- Grid factor : 1
This results in 12 individual periods:
- Individual period 1 : January
- Individual period 2 : February
...
- Individual period 12: December
In the generation rule, the individual periods are displayed in a tabular view containing the following columns:
- Individual period
- Planned variant type (StIVTy)
- Current day in individual period (DP)
- Current week in individual period (WP)
- Current month in individual period (MP)
- Public holiday collision (PHolKoll.)
The variant types must now be defined for each individual period:
Example of a generation rule (non-daily)
In the sequence MP/WP/DP, the FIRST entry is a time offset and all
others are absolute times.
Ind.period StIVTy DP WP MP PHolColl.
-----------------------------------------------------------
1 MZ 0 0 0 X
2 MZ 0 0 0 +
3 MZ 0 0 2 -
4 MZ 0 3 2 +
5 MZ 4 3 2 +
6 MZ 4 3 0 +
7 MZ 4 0 0 +
8 MZ 0 0 0 +
9 MZ 0 0 0 +
10 MZ 0 0 0 +
11 MZ 0 0 0 +
12 MZ 0 0 0 +
Interpretation of this generation rule
The individual period date is the start of the individual period irrespective of any additional time offset, absolute time and public holiday collisions that may have been specified.
Individual period 1 (= January):
-StIVTy=MZ: The January issue of the monthly magazine (MZ)
has the individual period date January 1st.
No time offset or absolute times are specified.
The provisional publication date remains January
1st. The system now checks whether this date is a
public holiday. January 1st is a public holiday.
The indicator for public holiday collision
defines that publication is still to take place on
a public holiday. This means that the publication
date for the January issue is January 1st.
tag für die Januarausgabe ist damit der 1.Januar.
(If a '+' was entered in this field, the issue
would be published on the workday following the
public holiday)
Individual period 2 (= February):
-StIVTy=MZ: The February issue of the monthly magazine (MZ)
has the individual period date February 1st.
No time offset or absolute times are specified.
The provisional publication date remains
February 1st. The system now checks whether this
date is a public holiday. February 1st is not a
public holiday. (The indicator for public holiday
&#
Supplementary Documentation - EINZELPER 0003
Use
For daily truck routes, the individual period might indicate the sequence number of the weekday.
Example for dailies:
<----------- Frequency rule ---------------------> <--Ind.per.-->
Repetition period Grid Grid divider Grid factor Indiv.periods
-----------------------------------------------------------------
1) Week Day 1 1 1 - 7
Explanation: This frequency rule is required for dailies: all
other frequency rules define non-dailies.
The individual periods have the following meanings:
1 = Monday (= start of 1st individual period)
2 = Tuesday (= start of 2nd individual period)
3 = Wednesday (= start of 3rd individual period)
...
Examples
Examples for creation and interpretation of a generation rule
Example for a daily truck route
The frequency rule for a daily is always defined as follows:
- Repetition period : Week
- Grid : Day
- Grid divider : 1
- Grid factor : 1
This results in 7 individual periods:
- Individual period 1 : Monday
- Individual period 2 : Tuesday
...
- Individual period 7 : Sunday
In the generation rule, the individual periods are displayed in a tabular view containing the following columns (truck route generation data):
- Individual period
- Truck route is generated on 1st day of individual period (GTRte)
- Truck route is generated if the date is the day before a public
holiday (BefPH)
- Truck route is generated if the date is a public holiday (OnPH)
- Truck route is generated if the date is the day after a public
holiday (1AftPH)
- Truck route is generated if the date is two days after a public
holiday (2AftPH)
The truck route generation data must now be defined for each individual period.
Example of a generation rule (daily)
Ind.period GTRte BefPH OnPH 1AftPH 2AftPH
-----------------------------------------------------------
1 X X X X
2 X X X X
3 X X X X
4 X X X X
5 X X X X
6 X X X X
7
Interpretation of this generation rule
Individual period 1 ( = Monday):
-GTRte=X : The truck route is run on Mondays.
-BefPH =X : If the Monday is the day before a public holiday
(i.e. the Tuesday is a public holiday), the truck route
is also run on the Monday.
-OnPH = : If the Monday is a public holiday, the truck route is not
run on the Monday.
-1AftPH=X : If the Monday is the day after a public holiday
(i.e. the Sunday is a public holiday), the truck route
is also run on the Monday.
-2AftPH=X : If the Monday is two days after a public holidy
(i.e. the Saturday is a public holiday), the truck route
is also run on the Monday.
Individual period 2 ( = Tuesday):
-GTRte=X : The truck route is run on Tuesdays.
-BefPH =X : If the Tuesday is the day before a public holiday
(i.e. the Wednesday is a public holiday), the truck route
is also run on the Tuesday.
-OnPH = : If the Tuesday is a public holiday, the truck route is not
run on the Tuesday.
-1AftPH=X : If the Tuesday is the day after a public holiday
(i.e. the Monday is a public holiday), the truck route is
also run on the Tuesday.
-2AftPH=X : If the Tuesday is two days after a public holiday
(i.e. the Sunday is a public holiday), the truck route is
also run on the Tuesday.
The other individual periods are interpreted in the same way.
Meaning of factory calendar specified for truck route
The factory calendar is ignored for dailies; only the public holiday calendar assigned to it is interpreted. (The factory calendar distinguishes between workdays and non-working days - for example, Saturday is generally a non-working day but not a public holiday. Public holidays are defined in the public holiday calendar.) If the generation rule is defined for Saturday (= individual period 6),y the only decisive factor for generation is whether or not the Saturday is a public holiday in the public holiday calendar. When generating daily publications, it is irrelevant whether or not the Saturday in the factory calendar is a non-working day.
Supplementary Documentation - EINZELPER 0004
Use
Example for non-dailies:
<----------- Frequency rule ---------------------> <--Ind.per.-->
Repetition period Grid Grid divider Grid factor Indiv.periods
-----------------------------------------------------------------
2) Year Month 1 1 1 - 12
3) 1 2 1 - 6
4) 2 1 1 - 24
The individual periods are numbered consecutively.
Explanation of example 2):
This frequency rule defines a monthly run frequency that is
repeated annually (individual periods 1-12 ):
The individual periods have the following meanings:
1 = January 1 (= start of 1st individual period)
2 = February 1 (= start of 2nd individual period)
3 = March 1 (= start of 3rd individual period)
Explanation of example 2):
This frequency rule defines a two-monthly run frequency that
is repeated annually (individual periods 1-6 ):
The individual periods have the following meanings:
1 = January 1 (= start of 1st individual period)
2 = March 1 (= start of 2nd individual period)
3 = May 1 (= start of 3rd individual period)
...
Explanation of example 3):
This frequency rule defines a run frequency twice a month
that is repeated annually (individual periods 1-24):
1 = January 1 (= start of 1st individual period)
2 = January 1 (= start of 1st individual period)
3 = February 1 (= start of 2nd individual period)
4 = February 1 (= start of 2nd individual period)
5 = March 1 (= start of 3rd individual period)
6 = March 1 (= start of 3rd individual period)
...
A frequency rule with a grid factor greater than 1
must separate publication dates by specifying time offsets
and absolute times, since generation could not otherwise
be performed for unique publication dates (for example,
the system would determine the publication date January 1
for individual periods 1 and 2 if no further data was
specified, so that the publication date would not be
unique and an error would occur in automatic generation).
Examples
Examples for creation and interpretation of a generation rule
1. Example of a non-daily truck route
The frequency rule is explained here as it would be for a truck route run monthly:
- Repetition period : Year
- Grid : Month
- Grid divider : 1
- Grid factor : 1
This results in 12 individual periods:
- Individual period 1 : January
- Individual period 2 : February
...
- Individual period 12: December
In the generation rule, the individual periods are displayed in a tabular view containing the following columns (truck route generation data):
- Individual period
- Generate truck route (GTRte)
- Current day in individual period (DP)
- Current week in individual period (WP)
- Current month in individual period (MP)
- Public holiday collision (PHColl.)
You must now define the truck route generation data for each individual period.
2. Example of a generation rule (non-daily)
In the sequence MP/WP/DP, the FIRST entry is a time offset and all others are absolute times.
Ind.period GTRte DP WP MP PHolColl.
-----------------------------------------------------------
1 X 0 0 0 X
2 X 0 0 0 +
3 X 0 0 2 -
4 X 0 3 2 +
5 X 4 3 2 +
6 X 4 3 0 +
7 X 4 0 0 +
8 X 0 0 0 +
9 X 0 0 0 +
10 X 0 0 0 +
11 X 0 0 0 +
12 X 0 0 0 +
Interpretation of this generation rule
The individual period date is the start of the individual period irrespective of any additional time offset, absolute time and public holiday collisions that may have been specified.
Individual period 1 ( = January):
-GTRte=X : The January truck route has the individual period date
January 1st. No time offset or absolute times are
specified. The provisional shipping date remains
January 1st. The system now checks if this date
is a public holiday. January 1st is a public
holiday. The indicator for public holiday collision
defines that the truck route is still to be run on a
public holiday. This means that the shipping date
for the January issue is January 1st.
(If a '+' was entered in this field, the truck route
would be run on the workday following the public
holiday.)
Individual period 2 ( = February):
-GTRte=X : The February truck route has the individual period date
February 1st. No time offset or absolute times are
specified. The provisional shipping date remains
February 1st. The system now checks if this date
is a public holiday. February 1st is not a public
holiday. (The indicator for public holiday collision
is therefore ignored.) This means that the shipping
date for the F
History
| Last changed by/on | SAP | 20020404 |
| SAP Release Created in |
