SAP E40A Fiori Application to Display Schedule Records

Search SAP Objects

E40A is a standard SAP S/4HANA Fiori application available in both on-premise and cloud environments, depending on your system version and release level. . It is delivered as a SAP GUI for HTML transaction, presented in the SAP Fiori theme to provide a consistent and seamless user experience. Classic transactions like E40A are accessible through the SAP Fiori launchpad, which serves as the unified entry point for both modern Fiori applications (SAPUI5/Fiori Elements) and classic transaction-based applications (ALV, Dynpro, Web Dynpro) in SAP S/4HANA and SAP S/4HANA Cloud, private edition.

Fiori App ID: E40A
App Name: Display Schedule Records
App Launcher: Display Schedule Records
Type(UI): SAP GUI(SAP GUI)
Fiori Apps Library: E40A
Device: Desktop
T-Code: E40A
ODATA (V4):
Database: HANA DB exclusive
Business Role: ()

Once configured, Fiori Apps are accessible as tiles on the SAP Fiori Launchpad. You can access the Launchpad either through the traditional SAP GUI using transaction code /UI2/FLP, or directly via a web browser by entering your system URL followed by the path /sap/bc/ui2/flp. Additionally, the SAP Web GUI can be accessed using transaction code WEBGUI, or through a web browser using the URL path /sap/bc/gui/sap/its/webgui/.

Application Configuration

• WebDynpro Application(Config):
• SAPUI5 / BSP:
• ICF Path:
• SAP UI5 Component:

Target Mapping

• Semantic Object: UtilitiesScheduling
• Semantic Action: displayScheduleRecords

Technical Catalog

• Name: SAP_TC_ISU_BF_BE_APPS:S4ISU
• Description: SAP Utilities Industry Basic Functions: Classic Apps

Business Catalog

• Name:
• Description:

Business Group

• Name:
• Description:

Pages/Spaces

• Page Name:
• Page Title:
• Space Name:
• Space Title:

Business Area / Roles

• Line Of Business:
• Scope:
• Relevant role: Other
• Component: IS-U-BF-PS
• Leading business role: -
• Additional role: -

Font End Components

• Component Version: UIS4HOP1 900 - SP 0003
• Min SP:
• Product Version: SAP FIORI FOR SAP S/4HANA 2023
• Support Package Stack: 03 (02/2025) FPS

Back End ABAP Components

• Component Version: S4CORE 108 - SP 0000
• Min SP:
• Product Version: SAP S/4HANA PRIVATE CLOUD 2023
• Support Package Stack: 03 (02/2025) FPS

HANA Components

• Component Version:
• Min SP:
• Product Version:
• Support Package Stack:

OData

Additional Details:

Lighthouse App: No
A “Lighthouse App” refers to a Fiori application that exemplifies the best of SAP Fiori design principles with high user adoption, optimized UX, business value, and performance. These apps are often redesigned from classic SAP GUI transactions and built natively with Fiori/UI5 to fully leverage the capabilities of the SAP Fiori design system.

Note Collection:

Industry Relevance:


Description:
When a portion and meter reading units are created, these schedule records can be used to generate schedule records for the following year. The base dates of the master schedule records are used to generate the appropriate periodic schedule records. Once you have entered the necessary budget billing data in the portion, budget billing dates are also generated for the portion. The dates of the generated schedule records are used to schedule the meter reading for the next period (years, months). The scheduled meter reading date for the schedule records is the date when extrapolation for consumption during the next period expires. Similarly, the data of the schedule records for billing (that is, the gas date and allocation date) is used for scheduling billing and for the statistical allocation of billings. Schedule records can be created in advance for a period that you define. You should create schedule records for at least one year in advance. This because a predecessor is always required, for example, for post processing a move-in or a move-out. Example Generating schedule records from 03/01/03 to 12/31/03 If the customer wants to execute an action for the schedule record in March, he or she will not be successful because they cannot access the schedule record for February. Schedule records were generated starting from 03/01/03. This means that there is no previous record available. Schedule Record for a Portion The schedule records of the portion are used for scheduling billing and allocating budget billing due dates to the portion schedule records. The budget billing period is directly linked to the end of the billing period. The following dates for the schedule records are transferred into the billing order: Scheduled billing date Billing transaction Scheduled meter reading date You cannot change meter reading schedule records for which meter reading order creation has already been executed. Period key The period key enables you to create a text for each budget billing cycle in each budget billing period. If you want to allocate a period key to all schedule records of a portion, you must first of all create a single schedule record (transactions EA43, E43A). You must then adjust this manually (transaction: Change Schedule Record; E40B). In the change mode, you can use the budget billing dates to allocate an individual period key to every date within every budget billing cycle. You can then generate other schedule records after this change (transactions EA43, E43A). Note You cannot regenerate a schedule record that you created with a period key. Schedule Records for a Meter Reading Unit. The schedule records for the meter reading unit regulate the due meter readings. This includes creating meter reading orders, meter reading announcements, and customer meter reading orders, and printing or downloading meter reading orders. The following dates for the schedule records are transferred into the meter reading order: Scheduled meter reading date Scheduled meter reading type Allocation date Gas date

BEX Query:


Search for further information about these or an SAP related objects