SAP ABAP Data Element NORMD (Standardize Release Creation Date in Release Creation Report)

Hierarchy

☛ ECC-DIMP (Software Component) DIMP
   ⤷ IS-A-EMM (Application Component) Enhancements to scheduling agreements MM (Outbound)
     ⤷ ISAUTO_ME (Package) ISAUTO: Purchasing

Basic Data

Data Element	NORMD
Short Description	Standardize Release Creation Date in Release Creation Report

Data Type

Category of Dictionary Type	D	Domain
Type of Object Referenced		No Information
Domain / Name of Reference Type	NORMD
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	Standard.
Medium	19	Standardize Date
Long	26	Standardize Release Date
Heading	53	Standardize Creation Date in Release Creation Report

Documentation

Definition

Determines how the release creation date is standardized at the time of release creation.

Use

• No standardization
  With this setting, the release creation date is calculated per SA release at the time of its creation.
  If, for example, the release creation program runs from 11 pm until 1 am, a date change occurs during this period. That is to say, some of the SA releases contain the date on which the program was started and others contain the date of the following day.
• Standardization to start date of SA release creation program
  All SA releases are assigned a common (i.e. standardized) creation date. At the start of the release creation program run, the current date is determined and assigned as their creation date to all SA releases created during the run.
  If you have chosen Standardization to start date of SA release creation program, all SA releases created through a release creation program run are assigned a uniform date.
  In contrast, if you have chosen No standardization, SA releases may be assigned different dates if a there is a change of date during the program run.
• Standardization to planned job date
  A prerequisite for this setting is that the release creation program is scheduled and started via the job management facility.
  At the start of the release creation process, the planned start date of the job is determined and assigned as the creation date to all SA releases created.
  The planned release creation date is thus used even if the release creation program cannot be started on the originally desired date.
  Example
  The release creation program usually starts at 23.00 hrs daily. Due to a technical delay, however, the program cannot be started until 00.30 hrs the following day. Standardization to the planned job date results in the desired release creation date being determined from the planned job date.
  In contrast, if Standardization to start date of SA release creation program were chosen, the following day would be determined as the release creation date.

Dependencies

If necessary, you can shift the release creation date by one workday by making an entry in the Move Release Creation Date field.

Example

You plan to run the release creation program for plant 0001 on Sunday 01.30.2000 at 23.00 hrs.

• To standardize the the release creation date, you choose Standardization to planned job date.
• You wish to move the release creation date one day into the future (Move creation date by + 1 workday) because you want all SA releases created by the release creation program for your vendors to have Monday (01.31.2000) as their reference date.
• The job does not start until 23.15 hrs on Sunday and runs until 00.30 hrs on Monday.

Result

• All SA releases have 01.31.2000 as their creation date.
  Initially, the planned job date (Sunday, 01.30) was determined as the release creation date. The latter was then moved one day into the future (i.e. to Monday 01.31).
• Backlog and immediate requirements relate to 01.31.2000, unless otherwise determined via the creation profile.
• The schedule line dates start with 02.01.2000 at the earliest (1st day after the release creation date).

Supplementary Documentation - NORMDA 0001

Procedure

Select this field if you want to edit or display data on this screen.

Supplementary Documentation - NORMDAT 0001

Procedure

Enter the identifying numbers of the characteristic data records in the DIN file which you want to copy.

Separate the numbers with commas. Enter intervals in the format (<lower limit>,<upper limit>).

History

Last changed by/on	SAP	20050301
SAP Release Created in