Hierarchy
EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials⤷
SD-BIL-IV-SBI (Application Component) Self-Billing Proced.⤷
VASB (Package) Application Development R/3 Sales / Self-Billing Process
Basic Data
| Data Element | DEACT |
| Short Description | Deactivation Indicator |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | DEACT | |
| 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 | Deact. |
| Medium | 15 | Deactivated |
| Long | 20 | Deactivated |
| Heading | 7 | Deact. |
Documentation
Definition
Specifies whether the record is deactivated or not.
Use
Individual data records in a transmission can be deactivated, in order to exclude them from further processing.
You can use this function to give a transmission the status "successfully processed", even if some of the data records it contains cannot be processed.
Deactivated records are not included in the processing step and therefore have no influence on the processing status.
When deactivating a record, you have to set whether it has been through verification only, or if processing was already started.
Deactivation can be carried out manually, or by the system.
The deactivation indicator assigned to a record can have the following attributes:
- _ the record is active
The system includes the record in the processing step.
- A Manual deactivation after completion of verification step
The system does not include the record in the processing step. You use this option if the verification step resulted in errors that could not be solved. Either the data has to be transmitted again or the required postings, that would have been made automatically in the processing step, have to be made manually.
- B Automatic deactivation in verification step
The system deactivated the record in the verification step. This happens, for example, if the number 007 is contained in the header's ACTION code.
An automatically deactivated record cannot be manually set back to active.
- C Manual deactivation after start of processing step
The processing step was started for the record but could not be completed successfully.
You can always restart the processing step, causing the system to continue where it left off. If you cannot remove the cause of the error, your only option is to deactivate the record and terminate processing at this 'incomplete' stage. This is necessary firstly, so that any subsequent records can be processed, and secondly, so that the transmission as a whole can acheive the status "successfully processed".
When you deactivate a record in the processing step, the steps already carried out (such as automatically created request documents) are not undone. You must manually ensure that the suituation as a whole is successfully concluded. You might have to manually create missing documents or manually reverse created postings.
This option of manual deactivation after start of processing step should therefore be used only in rare, exceptional cases.
Take note that deactivating a record in the processing step also excludes all of the IDocs and items summarized and contained therein from further processing.
This becomes especially significant when several IDocs reference the same delivery and also contain several material items. Since a delivery grouping summarizes several IDocs, dependencies can result between IDocs in case of deactivation.
Dependencies
Example
History
| Last changed by/on | SAP | 20030411 |
| SAP Release Created in |
