Hierarchy
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ ML (Package) R/3 services management
Basic Data
Data Element | DEL |
Short Description | Deletion Indicator |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | CHAR01 | |
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 | DELETE_IND | |
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Del. Ind. |
Medium | 15 | Deletion Ind. |
Long | 20 | Deletion Indicator |
Heading | 1 | D |
Documentation
Definition
Shows whether the object is earmarked for deletion.
Procedure
Set this indicator if you wish the object to be deleted when the reorganization program is next run.
Supplementary Documentation - DELFZ 0001
Use
Probable end of term of a loan contract.
Procedure
Examples
Date when the contract is or will be paid back.
Dependencies
Supplementary Documentation - DELFZ 0002
Use
Probable end of validity period of a loan contract.
Procedure
Examples
Dependencies
Supplementary Documentation - DELKZ 0001
Use
Procedure
By entering the corresponding indicator, you determine which MRP elements are allocated to the element hierarchy.
By pressing F2 on this field, you can maintain additional detailed data for this MRP element.
Examples
Dependencies
Supplementary Documentation - DELRKURS 0001
Use
If you make an entry in this field, you can override the settings you made in Customizing in the step Follow-up processing that are generally valid for all business event types.
Procedure
Check the settings in Customizing. If you want to specify a different setting for this business event type, mark the checkbox or leave it blank.
If you want to take over the remaining procedure settings from Customizing for this event type, transfer these to the infotype.
Examples
Example 1:
In Customizing, you defined the following settings for all business event types:
You defined the following check procedure for the attendee type H in Customizing in the step Attendee checks:
Attendee type H:
BookSameET: E (Check for booking on the same business event type)
PreBSameET: W (Check for prebooking for the same business event type)
Prereq.: W (Check for prerequisite attendance at business events)
CheckQual I (Check attendee's qualifications)
(E = Error, W = Warning, I = Information)
You made the following settings for follow-up processing in Customizing in the step Follow-up processing:
Attendee type H:
TransfQual: x (Transfer qualifications)
DelRel.E/A.: x (Delete relationship business event / attendee)
CreateE/A: x (Create relationship business event type / attendee)
Now you want to change the settings referring to deletion of the relationship between the business event type and the attendee on completion of the event. You do not want the relationship deleted. You want to transfer the other settings as defined in Customizing.
You leave this field empty and transfer the remaining values and settings from Customizing to infotype 1030.
Example 2:
You want warnings issued for attendees of type P for checks on a specific event type. No actions should be performed in follow-up processing. You enter the following:
Attendee type P:
BookT: W (Check for booking on the same business event type)
PrebT: W (Check for prebooking on the same business event type)
ChPreq: W (Check for prerequisite attendance at business events)
CheckQual W (Check attendee's qualifications)
TransfQual: (No transfer of qualifications)
DelRel.E/A.: (No deletion of relationship business event / attendee)
Rel.E/A: (No creation of relationship business event type/attendee)
Dependencies
Infotype 1030 overrides all the entries made in Customizing for Training and Event Management in the steps Attendee checks and Follow-up processing.
Supplementary Documentation - DELTX 0001
Use
Procedure
Enter a text which describes the element to be dispalyed in more detail.
Examples
Dependencies
History
Last changed by/on | SAP | 20130604 |
SAP Release Created in |