SAP ABAP Data Element TS65MUSS (Postprocessing of Empty Required Entry Fields)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷
CRM-MD-PCT (Application Component) Product Catalog
⤷
FF (Package) Cash Management
BBPCRM (Software Component) BBPCRM⤷
CRM-MD-PCT (Application Component) Product Catalog⤷
FF (Package) Cash Management
Basic Data
| Data Element | TS65MUSS |
| Short Description | Postprocessing of Empty Required Entry Fields |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | YESNO | |
| 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 | 0 | |
| Medium | 0 | |
| Long | 30 | Postprocessing Required Fields |
| Heading | 0 |
Documentation
Definition
If this has been highlighted, only individual records are selected for which at least one required field is empty.
Use
Individual records (payment advice and planned items) may for example have empty required entry fields,
- If field control was subsequently changed for a planning type
- If individual records were read in from a file with report RFTS6510. Report RFTS6510 is unable to verify required entry fields because an error message causes the report to terminate.This is why RFTS6510 only checks the fields that are absolutely necessary in order to create an individual record, e.g. the value or planning date.
Empty required entry fields can subsequently be processed.
Dependencies
Example
History
| Last changed by/on | SAP | 20030714 |
| SAP Release Created in | 470 |
