Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-BMT-OM (Application Component) Organizational Management⤷
SP00_ITF (Package) Infotype Framework
IMG Activity
| ID | PD_ITF_003 | SAP: Define Field Properties |
| Transaction Code | S_Y7A_80000013 | (empty) |
| Created on | 20070801 | |
| Customizing Attributes | PD_ITF_ATTR | Attribute for IMG Activities for Decoupled Infotype Framework |
| Customizing Activity | PD_ITF_003 | SAP: Define Field Properties |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | PD_ITF_003 |
Note
This IMG activity serves to illustrate to you the settings made by SAP. You create customer settings in the Customer: Define Field Properties IMG activity.
Use
In this IMG activity, you define the properties for infotype fields. You can define for each field whether it is a required entry field, whether it is an input field or an output field, and whether it is relevant at all. You can make these settings dependent on the values for the subtype and object type.
At runtime, the decoupled infotype framework evaluates for each infotype field these SAP settings and the customer settings in the Customer: Define Field Properties IMG activity. The system then compares the values for the object type and subtype processed at runtime with the existing settings for the object type and subtype. The system performs the comparison in the following sequence:
- If an entry exists for the field for the object type and subtype values being processed at runtime, the field properties are read and taken into account during further processing.
- If no entry exists for the field for the object type or subtype values being processed at runtime, the infotype framework looks for an item with the specified object type but without the subtype (subtype = SPACE (initial)). The field properties for the field are read and taken into account during the rest of the processing.
- If no entry for the object type exists for the field for the object type or subtype values being processed at runtime, the infotype framework reads with the specified subtype but without the object type (object type = SPACE (initial)). The field properties for the field are read and taken into account during the rest of the processing.
- If no entry for the object type or subtype exists for the field for the object type or subtype values being processed at runtime, the infotype framework reads without an object type or subtype (object type and subtype = SPACE (initial)). The field properties for the field are read and taken into account during the rest of the processing.
Note
In all cases, the infotype framework first evaluates the customer settings. If a customer setting does not exist, then the system reads the SAP setting. The customer settings therefore always have higher relevance than the SAP settings. However, SAP has the option of prohibiting customer settings. If the Fixed indicator is set for a field, customer settings are not permitted for this field. If you still make an entry for this field, the system ignores this entry.
Standard settings
Activities
- Specify the work area. Enter the number of the infotype for which you want to maintain the field attributes.
- Choose New Entries.
- Enter the subtype, or leave it initial if the following specifications apply to all subtypes of the infotype.
- Enter the obect type, or leave it initial if the following specifications apply to all object types.
- Under Structure, enter the name of the P structure (in the Pnnnn form) that contains the infotype field, with nnnn representing the number of the infotype If you want to create the entry for a field in the table section, enter then name of the HRT structure (in the HRTnnnn form).
- Enter the name of the field. The field must be part of the previously specified structure.
- Specify whether the field is a Required Entry field. If you set the indicator, the infotype framework checks at runtime whether an entry was made for the field (that is, whether a value exists that is not equal to the initial value). If this is not the case, the system outputs an error message that the data record containing errors cannot be written to the database.
- Specify whether the field is an Output Field. If you set this indicator, the infotype framework does not permit any changes to the field value. If the infotype framework determines at runtime that the field value was changed, the field is reset to the old value and a warning message is output. Processing is then continued.
- Specify whether the field is Not in Use. A field can be not in use if it exists in principle but is not used for the specific object type or subtype. If you set this indicator, the infotype framework does not permit any entries for this field. However, if the infotype framework determines a field value at runtime, this field value is deleted and a warning is output. Processing is then continued.
- Specify whether the SAP setting is Fixed or if it can be overwritten by customers. If this indicator is set, the customer cannot then override the field properties for this field in the Customer: Define Field Properties IMG activity. Customer settings for fields with this indicator set are ignored.
Example
Example 1:
Work area infotype: 1000
Subtype: -
Object type: -
Structure: P1000
Field name: SHORT
Required entry: X
Output: -
Not in use: -
Fixed: -
Example 2:
Work area infotype: 1016
Subtype:
Object type:
Structure: HRT1016
Field name: GENERATED
Required entry: -
Output: -
Not in use: X
Fixed: -
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 1 | Critical |
| Country-Dependency | A | Valid for all countries |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| V_T777IFPROPS | V - View | SM30 |
History
| Last changed by/on | SAP | 20070801 |
| SAP Release Created in | 700 |
