Ansicht
Dokumentation
DFS_FLGHTORDAREA - Adjust Terminology for the "Flight Order"
Addresses (Business Address Services) CPI1466 during BackupThis documentation is copyright by SAP AG.
In this customizing activity, you define new terminology for areas according to your business requirements. You can adjust the flight-specific terminology on the flight order screens, to make the application more generic or to make it relevant for specific order types in some cases. This can be done to make the application more suitable for land or sea-based equipment.
While you may want to make the higher-level screen areas in the application (such as menu paths, search help, and so on) more generic, you can define and adjust the terminology so that it is suitable for specific order types for the screen fields in the “flight order”.
The different locations for which the terminology can be defined and where the changes apply are known as areas.
The areas for which text modification is supported are shown below:
Area | Initial Screen (For All Order Types) | Detail Screen (For a Specific Order Type) |
Application Title | Yes | Yes |
Initial Screen - Flight | Yes | No |
Application - Data Loss PopUp - Title | No | Yes |
Application - Controlled Usage - Flight | No | Yes |
Menu Bar - Flight | Yes | Yes |
Menu Bar - Flight - Other Flight | Yes | Yes |
Menu Bar - Edit - Settings - Flight | Yes | Yes |
Menu Bar - Environment. - Change Document - Flight | No | Yes |
Settings - Title | Yes | Yes |
Settings - Flight Data | Yes | Yes |
Header Area - Flight | No | Yes |
Flight Data - Title | No | Yes |
Flight Data - Flight Status | No | Yes |
Date/Target - Takeoff Date/Time | No | Yes |
Date/Target - Latest Takeoff Time | No | Yes |
Date/Target - Landing Date/Time | No | Yes |
Date/Target - Planned Flight Time | No | Yes |
Date/Target - Landing Site | No | Yes |
Date/Target - Runaway | No | Yes |
Note: Certain areas are applicable for initial screen and are not dependent on order type whereas certain areas are applicable for details screen which are order type dependent. Also, an area can also be applicable for both initial as well as details screen.
- You must define the area that needs to be modified.
- You must check whether that area is applicable for Flight Order’s Initial or Details Screen.
- In case of generic adjustments, such as those for menu paths or initial screens, the order type field must be left blank. But in case of specific areas you can enter the order type.
- You can give supporting texts according to your needs.
Example 1:
In case of an area such as “Initial Screen – Flight” which is generic, you can define a generic term which are order type independent (such as “Task Order”).
Area | Text |
Initial Screen – Flight | Task Order |
The initial screen for the display “flight” changes and shows “Create Task Order”.
Example 2:
In case of an area such as “Application Title”, which can be defined either for a generic term or a specific term, you can either define a generic term (such as “Task Order”) or a term specific to any air based vehicle such as “Flight Task Order.
Area | Text |
Application Title | Task Order |
The application title of initial screen will show “Create Task Order” instead of “Create Flight”.
Type | Area | Text |
FL01 | Application Title | Flight Task Order |
The application title of main screen will show “Create Flight Task Order” instead of “Create Flight”.
Example 3:
In case of an area for which the terms can be defined for order type (such as “Date/Target - Take Off Date/Time”), you can define different terms for specific order types used for land vehicles (“Departure”), compared to those used for ships (“Departure”) or aircraft (“Take Off”).
Type | Area | Text |
FL01 | Date/Target - Take Off Date/Time | Take Off Date/Time |
A001 | Date/Target - Take Off Date/Time | Departure Date/Time |
N001 | Date/Target - Take Off Date/Time | Departure Date/Time |
Note: Generic term can be used for all vehicles or equipment which can be land, air or sea based.
TXBHW - Original Tax Base Amount in Local Currency General Data in Customer Master
This documentation is copyright by SAP AG.
Length: 7832 Date: 20240523 Time: 183309 sap01-206 ( 71 ms )