SAP ABAP Data Element ADDI_DATE (Execution date for follow-up action)

Hierarchy

☛ BBPCRM (Software Component) BBPCRM
   ⤷ LO-ADM (Application Component) Additionals Management
     ⤷ WTAD (Package) IS-R: Additionals

Basic Data

Data Element	ADDI_DATE
Short Description	Execution date for follow-up action

Data Type

Category of Dictionary Type	D	Domain
Type of Object Referenced		No Information
Domain / Name of Reference Type	DATS
Data Type	DATS	Date field (YYYYMMDD) stored as char(8)
Length	8
Decimal Places	0
Output Length	10
Value Table

Further Characteristics

Search Help: Name
Search Help: Parameters
Parameter ID
Default Component name	EXECUTION_DATE
Change document	☐
No Input History	☐
Basic direction is set to LTR	☐
No BIDI Filtering	☐

Field Label

	Length	Field Label
Short	10	Date
Medium	17	Subs. action date
Long	20	Subseq. action date
Heading	10	Date

Documentation

Definition

Date on which a follow-up action for additionals is to be performed.

Use

The date for a follow-up action is determined on the basis of the data in the triggering application.

Example

The date for ordering sew-in labels for a T-shirt is dependent on the T-shirt's delivery date.

Notes

The system suggests default values which you can change as follows:

• Online in the additionals monitor
• Using user exit EXIT_SAPLWTIP_001 during generation of an additionals IDoc.
• Using user exit EXIT_ADDI_ORDER_FORMS_001 during generation of an additionals purchase order.

The date of use is filled for each application as follows:

Application     Reference field     Database field

Sales     schedule line delivery date     VBEP-EDATU

Purchasing     delivery date of item     EKET-EINDT

Goods movement     posting date in document     MKPF-BUDAT

Delivery     planned goods issue date     LIKP-WADAT

History

Last changed by/on	SAP	20110901
SAP Release Created in