Ansicht
Dokumentation
FSH_CTFC - Maintain Field Catalog
rdisp/max_wprun_time - Maximum work process run time General Material DataThis documentation is copyright by SAP AG.
In this Customizing activity, you determine the fields you want to use for the creation of your value-added service (VAS) condition tables.
The field catalog contains the fields permitted for defining condition tables.
Field catalog maintenance can be divided into three screen areas:
- Field catalog area
- Detail area for field and data element (hidden or not hidden)
- Detail area for the log (hidden or not hidden)
Field catalog area
The field catalog area is the main component of field catalog maintenance. Fields can be processed or created. The following fields should be maintained in change mode:
- Subcommunication structure category (This field is merely used to select All fields, otherwise a specific category is predefined):
- Field: You enter the field name here. You should make sure that the name areas Y* and Z* are reserved as customer namespace. The remaining name areas are reserved for SAP.
- Virtual: The virtual attribute for the field determines how often the field occurs.
- Selection type: This attribute determines the type of selection of condition records in general condition maintenance.
- Data element: The data element determines the business significance as well as the data category of a field. In principal, all of the data elements contained in the system can be selected. When you enter the data element, the description, data category as well as field lengths are displayed in the other columns in table control (the columns that are not available for input). You should make sure that the name areas Y* and Z* are reserved as customer namespace. The remaining name areas are reserved for SAP.
Note
A data element can only be available once in the field catalog.
Detail area for field and data element
The detail area can be maintained exclusively for a selected field in the field catalog area for which the function detail (Icon: magnifying glass) has been selected.
- Relationships
- In this area, relationships to other fields can be maintained for the selected field. Relationships make sense, if internal and external usages of a field are different.
- The selected field should always be a field with internal usage (virtual column in field catalog area). Relationships to fields with external usage can then be maintained. If the field usages do not fit together, a corresponding error message appears.
- Only relationships to fields from the global field catalog (table/SAPCND/T681FF) can be maintained.
- Dependencies
- In this area, you maintain dependencies for a data element of a selected field to another data element. These dependencies are checked during condition record processing.
- In the dependencies, you can only select data elements for the global field catalog.
- Detail area for the log
- In the log area, the application log is displayed as part of the last transaction call when saving and/or generating written application logs.
The standard functions for the application log are available.
The logs are saved under the following application log object: COND_TECHNIQUE (sub object FIELD_CATALOGUE).
You can use transaction SLG1 (evaluate Application Log) to display all logs. Logs that are no longer required can be deleted using transaction SLG2 (Delete obsolete application logs).
The following functions are available globally for all screen areas.
- Generate
- The generate function is required when a new field has been inserted. When you execute the Generate function, the system generates the work structures and possibly communication structures from the field catalog.
- Transport
- In general, a manual transport of the field catalog is not necessary due to the automatic transport connection to field catalog maintenance.
- It is, however, possible to trigger a manual transport of the entire field catalog for an application.
Vendor Master (General Section) ABAP Short Reference
This documentation is copyright by SAP AG.
Length: 4981 Date: 20240523 Time: 200209 sap01-206 ( 75 ms )