Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
SD-SLS (Application Component) Sales⤷
ERP_SALES_LORD (Package) ERP Sales Lean Order
Basic Data
| Data Element | TDV_INPUT_BEHAVIOR |
| Short Description | Input Behavior |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | DOM_LORD_INPUT_BEHAVIOR | |
| 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 | Input |
| Medium | 15 | Input Behavior |
| Long | 20 | Input Behavior |
| Heading | 20 | Input Behavior |
Documentation
Definition
This indicator controls the input behavior of the current field on the user interface or programming interface.
Use
- Editable in create/change mode, read-only in display mode
If you choose this field, the field is ready for input in edit mode and otherwise read-only.In most cases, you can use this option to achieve the desired standard input behavior.
- Mandatory in create/change mode, read-only in display mode
If you choose this field, the field is a required field in edit mode and otherwise read-only.You should only use this option if the field is definitely mandatory in all business cases.
- Read-only in create/change/display mode
If you choose this field, the field is always read-only.You should only use this option if the field should not be changeable on the user interface or programming interface.
- Editable in create/change/display mode
If you choose this field, the field is always ready for input.Note that the field is not saved to the database if it is changed in display mode. You should only use this option if the field controls dependent fields, such as the Variant field, which controls if other fields are displayed or hidden.
- Determine input behavior via reference screen
If you choose this field, the input behavior of the field is determined by the system via PBO simulation of the specified reference screen of the given main program. - You need this option if the input behavior depends on the business semantics of the current surrounding data and you already implemented this business logic in the field selection source code of the relevant reference screen. You should choose this setting if such an appropriate reference screen already exists.
- If you do not specify an appropriate screen number (or do not specifiy a screen number at all), the field is always invisible.
- Determine input behavior via BAdI implementation
If you choose this field, the input behavior of the field is not automatically determined by the system. Instead, you must implement BADI_LORD_GET_INPUT_MODE BAdI, method GET_INPUT_MODE and use appropriate program code to control the input behavior. - You need this option if the input behavior depends on the business semantics of the current surrounding data and you have to cover this situation programmatically within the LO API layer. You should choose this setting if the input behavior varies according to the current business data situation.
- If you choose this option but do not implement the BAdI accordingly, the field is always flagged as invisible by sales backend processing. This means that it does not appear on a user interface, for example.
Dependencies
Example
Note
None of these settings triggers a check of the actual content of the field. You can implement this type of check using the BADI_LORD_DO_PAI BAdI, method FILL_SUPPLY_LIST.
History
| Last changed by/on | SAP | 20100310 |
| SAP Release Created in | 605 |
