Exploring SAP Fiori Applications for Project Control - Finance

The following is a list of key features:

• You can view the list of projects based on the filter criteria you have specified. You have the option to create variants based on your needs.

• You can get an overview of project header and control details, such as, the assigned project manager, project profile, responsible cost center, profit center, and relevant dates.

• You can create new projects, copy existing projects, and edit project header details. You can also delete enterprise projects. When you create a new project in the Project Control app by copying basic project data including the project structure, work packages, milestones, and project team from an existing project

• You can change the processing status of the project. The processing status defines the stage of the overall lifecycle the project is in.

• You can block functions, such as, time recording, other expense and service postings based on the requirement at project level. You can block one or more functions mentioned below for the selected project or work packages:

  • Time Recording - Time posting from the Manage My Timesheet app.
  • Activity Allocation - Manual activity allocation from the Enter Direct Activity Allocation and Manage Direct Activity Allocation apps.
  • Concur Expense Posting - Expense posting from SAP Concur.
  • Other Expense Posting - Manual cost posting to a G/L account from the Enter Manual Cost Allocations, Reassign Costs and Revenues, Post General Journal Entries, and Create Supplier Invoice apps.

• For reporting purposes, you can choose the priority and type of your project.

• On creation of a project, you can maintain the project currency. Modifications to the project currency are not permitted upon saving the project for the first time.

• You can maintain the joint venture accounting attributes if joint venture accounting is active for your project.

• You can maintain the accounting attributes associated with Public Sector Management (PSM), if PSM is active for your project.

• You can include the tax jurisdiction code for your project. This helps to determine how the tax amount is determined for your project.

• Project budgeting and budget availability control can be used to monitor the consumption of assigned budgets to projects and prohibit budget overruns in time. You can assign an availability control profile to a project and choose to activate the budget availability control as per your need.

• Receive information of situations when the budget consumption for the project exceeds the thresholds defined in the availability control profile of the project.

• You can navigate to the Project Planning app to create or maintain the project structure.

• You have the option to navigate to related apps that are used in the project financial controlling process.

Note

If the Project Review (1YF) process is enabled, you have the option to navigate to related apps of this process.

You can extend the Project Control app according to your business needs.

Key users can extend the app in the Custom Fields and Logic app using the business context Project Header. You can create custom fields in this business context, enable usage of these fields for the data source Project Control Extensibility Model in the UIs and Reports section of custom field maintenance, and publish your custom fields.

With the BAdI Project Validation, you can validate values for project header properties.

With the BAdI Project Determination, you can determine values for project header properties.

The key features of the Manage Cost Rates - Professional Services App (F3161) include:

• Search for activity types.

• Display a list of activity types filtered according to your specific criteria.

• Display activity type master data.

• Edit activity type master data.

• Create activity types from scratch or based on existing activity types.

• Refine the displayed list by searching for keywords or figures.

• In addition, the app supports the following technical features and options.

• Integration with MS Outlook allows you to generate an email with a link to a specific worklist without leaving the app.

• A share option allows you to initiate collaboration with colleagues by posting a worklist to SAP Jam without leaving the app.

Note

This app contains in-app help for key fields and concepts. To display the help while working in the app, press F1 or choose the question mark displayed in the app header.

A financial statement version is a hierarchical arrangement of G/L accounts. Semantic tags are a new kind of financial infrastructure tool that you can use to simplify your work. You can use semantic tags to set standard key figure definitions that can be used in any report.

A key user has to define a financial statement version and configure a cost-related semantic tag. A semantic tag has to be then assigned to the financial statement version. This combination of semantic tag and financial statement version enables the system to determine project costs.

Note

Only costs related to G/L accounts that are assigned to a financial statement item (that in turn belongs to the financial statement version of your controlling area) are displayed in the app.

Budget Availability Control allows you to control budget consumption in your projects. To control budgets in your projects, you first maintain the Budget Availability Control Profile for projects. Then, you activate budget availability control for projects.

The key features of the Monitor Projects (F3088) app include:

• View plan costs, actual costs, and commitments of a project based on filter criteria, such as, company code, cost component, posting date, and so on.

  Note

  This card does not support budget relevant costs, that is, costs derived from semantic tags assigned to budget availability control profiles.

• Choose a cost planning category and use it for calculation of variance.

• Visualize costs by category and costs by cost component in the form of micro charts.

• Select one or more projects and navigate to view costs and budget associated with projects (desktop only).

• Select one or more projects and navigate to view project progress.

• Choose a project to view possible actions that can be performed on that project by navigating to related apps.

• Select a project and predict its cost.

  Note

  To predict the total cost of a project, this app uses the PROJCOSTFRCAST01 (Project Cost Forecast Predictive Scenario) predefined predictive scenario.

• Choose a predicted cost for prediction overview and then navigate to prediction details view cumulative costs, cost component details, and similar projects (desktop only) used for prediction.

  Note

  In the cumulative costs chart, actual costs, and commitments are plotted only for the current fiscal year. Also, prediction details are not plotted if the project is in the final month of its total duration.

The PREDICT_PROJECT_COST (Predictive scenario for project cost prediction) predefined predictive scenario allows you as a data scientist or machine learning expert, to enable your users to predict the overall project cost for new or running projects based on historical project data and using a K-Nearest Neighbors (KNN) algorithm.

Note

The PREDICT_PROJECT_COST (predictive scenario for project cost prediction) has replaced the predefined predictive scenario PROJCOSTFRCAST01 (project cost forecast). If the old predefined predictive scenario is still in use by your predictive model, you have to retrain it using this new predefined predictive scenario.

You enable this predictive functionality by using an active version of the default model in this predictive scenario. To do so, you create versions by training the model with different sets of data using the Predictive Models app. Then you apply the version that you prefer by setting it as the active version. If this predictive functionality has not been enabled, consuming apps cannot display predicted results.

Note

Recommendation

• To ensure the quality of your model version, we recommend that you train the model with data that corresponds to your business case. To do so, you can add filters to your training dataset to refine the predictions.

• To achieve reliable predictions of total cost of projects, train the model with data of completed projects. Set the filter accordingly to exclude data of uncompleted projects.

If you use the model to predict the costs of a particular project, its current or planned costs are not included in the calculation. However, the dates of the earliest and latest cost postings (PLANNEDCOSTERLSTTOLTSTDURN and ACTUALCOSTERLSTTOLTSTDURN) may influence the prediction.

As a key user, you can extend the Monitor Projects app according to your business needs.

Key users can extend the app in the Custom Fields and Logic app using the following business contexts:

Project Header:

You can create custom fields in this business context, enable usage of these fields for the data source Project Financial Summary Extensibility Model in the UIs and Reports section of custom field maintenance, and publish your custom fields.

The Import Financial Plan Data (F1711) app has the following key features:

• Import plan data records stored in a CSV file.

• Include nearly every field from the ACDOCP table in the import.

• Automatically validate all values from the CSV file before the import.

The prerequisites for the Import Financial Plan Data (F1711) app include:

• The source files must be available as CSV files. The source files must have the correct structure and format and contain the plan data records as data rows.

• All organizational units and all master data for which you want to plan exist in the system.

• For time-dependent organizational units or master data, the following applies:

  • It must exist in the period specified in the same data row.

  • If period 0 is specified, the master data must exist in period 1.

  • If a special period is specified, the master data must exist in the last normal period of the fiscal year.

  • If only the fiscal year is provided, the master data must exist at some time during the fiscal year.

1. You receive the plan data files from the planners responsible and store them within your local network.

2. Open the Import Financial Plan Data app and select a source file. The app performs the following checks and determinations:

   1. Validity: The app checks whether the values in the source file are valid. If required, it returns a list of error messages. Correct the values in the source file until they are all valid before you can proceed.

   2. Mandatory fields: If the following fields are not included in the source file, the app automatically determines their values from the system settings:

      • If you did not enter the Company Code (RBUKRS) directly, the Plant (WERKS) determines the Company Code (RBUKRS).

      • If you did not enter the Controlling Area directly, theCompany Code (RBUKRS) determines the Controlling Area (KOKRS).

      • The Controlling Area (KOKRS) determines the following characteristics:

        • Ledger (RLDNR)

        • Fiscal Year Variant (PERIV)

        • Chart of Accounts (KTOPL)

      • The app sets the CO Debit/Credit Indicator (CO_BELKZ) to the default value S.

   3. Optional fields that are not included in the source file: If the following fields are not included in the source file, the app automatically determines their values from the system settings:

      • Periods: The Period/Year (FISCYEARPER) field is determined by the Period (POPER) and the General Ledger Fiscal Year (RYEAR) field or the other way round.

      • Posting Date (BUDAT): The app sets the posting date to either the first day of the period or the first day of the first year.

      • Account Assignment Type (ACCASTY): The account assignment type is the type of the true account assignment object.

        • Cost Center (RCNTR) leads to ACCASTY = KS.

        • Sales Order (KDAUF) and Sales Order Item (KDPOS) lead to ACCASTY = VB.

        • WBS Element (PS_POSID) leads to ACCASTY = PR.

      • Cost centers usually are true account assignment objects. For an important exception, see below.

        WBS elements can be marked as true or statistical in their master record.

        If there is more than one true account assignment object, the ACCASTY field remains empty. Subsequent derivations based on the ACCASTY field are not possible. Exception: If there are two true account assignment objects and one of them is a cost center, the cost center becomes statistical. The import fills the ACCASTY field with the type of the remaining true account assignment object.

        Cost centers usually are true account assignment objects. For an important exception, see below.

        WBS elements can be marked as true or statistical in their master record.

        If there is more than one true account assignment object, the ACCASTY field remains empty. Subsequent derivations based on the ACCASTY field are not possible. Exception: If there are two true account assignment objects and one of them is a cost center, the cost center becomes statistical. The import fills the ACCASTY field with the type of the remaining true account assignment object.

      • These organizational units are derived from the account assignment object specified by the account assignment type (ACCASTY).

        • Profit Center (PRCTR)

        • Company Code (RBUKRS)

        • Plant (WERKS)

        If the app cannot determine the profit center, the app sets it to the dummy profit center of the controlling area.

      • Functional Area: The Functional Area (RFAREA) is determined by the G/L account (RACCT). If this is not successful, the true account assignment object determines the functional area.

      • Segment: The Segment (SEGMENT) is determined by the Profit Center (PRCTR).

      • Project: The Project Definition (PS_PSPID) is determined by the WBS Element (PS_POSID).

      • CO-PA Characteristics: The CO-PA Characteristics are determined from a profitability segment that is referred to 100 percent by the settlement rule of the true account assignment object. If this is not successful, the app processes the CO-PA derivation.

      • Currencies: The system behavior depends on the currency you have used in your source file.

        • If you entered the plan amounts as amounts (HSL) in Company Code Currency (RHCUR) or as amounts (KSL) in Controlling Area Currency (RKCUR), the app copies one of these amounts to amounts (WSL) in Transaction Currency (RWCUR):

          1. Priority: the amounts (CO_OSL) in Company Code Currency (RCO_OCUR)

          2. Priority: the amounts (HSL) in Company Code Currency (RHCUR)

          3. Priority: the amounts (KSL) in Controlling Area Currency (RKCUR)

        • If you entered or derived the plan amounts as amounts (WSL) in Transaction Currency (RWCUR), the app converts these amounts into amounts (HSL) in Company Code Currency (RHCUR) and amounts (KSL) in Controlling Area Currency (RKCUR).

   4. Optional fields included in the source file: If you include optional fields in the source file, the app accepts their values and doesn't overwrite them with derived values. The app also accepts an empty field as unassigned.

   5. Plan Data Scope: If all values are valid, the app selects the distinct values for all characteristics of the plan data scope (as defined the third row of the source file):

      • If no plan data exists in the system for any combination of these characteristic values, you can directly import the plan data.

      • If plan data exists in the system for any combination of these characteristic values, the app displays the affected values. It assumes that you want to completely replace the existing plan data by the new plan data import.

3. Choose Import Source File. The app performs the following steps:

   1. It reverses the plan data records existing in the system for all combinations of the displayed values (the plan data scope).

   2. It posts the imported plan data records with the CO Debit/Credit Indicator you entered in the CO_BELKZ column. If you did not specify a value in the CO_BELKZ column, the system posts the data records as a debit (internal value S).

4. Check the imported data. Choose Check Financial Plan Data. The Financial Plan Data analytical app opens in a separate window. It only displays the plan data which you have just imported. You can use this analytical app to check the completeness of your import.

Key features of the Manage Direct Activity Allocation (F3697) app include:

• Navigating directly to the Allocation Flow app using Display Allocation Flow to visualize the links between documents.

• Filtering for direct activity allocations by various criteria, such as, reference document, status, or posting type.

• Viewing the details of a direct activity allocation, including the relevant journal entries.

• Copying the attributes of one allocation to create a new allocation.

• Downloading templates to use for uploading allocation items.

The key features of the Post General Journal Entries (F0718) app include:

• Save and view held journal entries before posting.

  Note

  Held journal entries expire in 180 days after creation for data protection. Check the creation time and renew the held journal entries if needed.

• Make manual postings to G/L accounts.

• Upload a CSV or XLSX file to post an entry to G/L accounts.

• Assign postings to additional objects, such as, cost centers, profit centers, and orders.

• Calculate taxes automatically.

• Add attachments and enter notes to explain the reason for a posting.

• Mass delete held journal entries.

The Project Financial Controller Overview (F3078) app has the following key features:

• You can customize the overview page by rearranging cards and by hiding or showing them. You can drag and drop cards to rearrange them.

• To hide a card, proceed as follows:

  • In the header bar, choose the User icon and choose Manage Cards. Use the switch control to hide or show the relevant card. Choose OK.

  • To reset the view to the default settings, choose Restore in the Manage Cards window.

• You can also apply a filter to the displayed information, which will affect all relevant cards. For example, you can filter the content of all cards per project or planning category.

• A standard filter variant is delivered that can be used immediately. It contains some predefined values for the filter bar. You can make your own variant by selecting the Select Variant drop-down arrow. You can also customize the filter by choosing Adapt Filter.

• This app includes SAP CoPilot, a contextual collaboration tool that allows you to create, collect, and share artifacts (such as, notes, objects, messages, and screenshots) based on the context of the screen you are currently working in.

This table describes the various cards that appear on the Project Financial Controller Overview (F3078) app:

The key features of the Project Cost Report - Line Items (F2538) app allow us to:

• View aggregated and non-aggregated plan, actual, baseline costs, and commitments of a project or WBS element based on filter criteria, such as, company code, G/L account, posting date, and so on.

• View cost details of multiple projects or WBS elements from different projects and hierarchies.

• Configure two cost planning categories and use one category for calculation of variance.

• Enter the level to which a project tree must be expanded.

• Navigate to view costs at the line item level.

• Switch between visual filter and compact filter for costs at the line item level.

• Drill down to view line item costs by fiscal year, fiscal period, company code, controlling area, and so on.

• Select or click data points on the line chart to get more information.

• Navigate to view the details of a project or a WBS element.

• Navigate to view journal entries of a document.

  Note

  You can only view the costs of PBS projects and WBS elements. If you wish to see the details of PBS projects and WBS elements, you require the SAP_BR_PROJ_MANAGE_COMM Business Role.

The key features of the Project Cost Report – Overview (F2513) app allow you to:

• View aggregated and non-aggregated plan, actual, baseline, and commitment costs of a projector WBS element based on filter criteria, such as, company code, G/L account, posting date, and so on.

• View cost details of multiple projects or WBS elements from different projects and hierarchies.

  Costs in project currency will be blank for a project if a project currency is not defined for that project.

• Configure two cost planning categories and use one category for calculation of variance.

• Enter the level to which a project tree must be expanded.

• Navigate to view costs at the line item level.

• Switch between visual filter and compact filter for costs at the line item level.

• Drill down to view line item costs by fiscal year, fiscal period, company code, controlling area, and so on.

• Select or click data points on the line chart to get more information.

• Navigate to view journal entries of a document.

Note

You can only view the costs of PBS projects and WBS elements. If you wish to see the details of PBS projects and WBS elements, you require the SAP_BR_PROJ_MANAGE_COMM Business Role.

The key features of the Manage Project Procurement (F2930) app are:

• Viewing purchase orders and purchase requisitions associated with a project or WBS element based on filter criteria, such as, material, supplier, project manager, delivery date, and so on.

• Viewing the quantity that is delivered as against the quantity that is ordered for purchase orders in the form of a micro chart.

• Viewing the quantity that is ordered as against the total quantity for purchase requisitions in the form of a micro chart.

• Choosing a project to view all possible actions that can be performed on that project by navigating to related apps.

• Navigating to view contextual information related to WBS element, material, supplier, purchase order item, and purchase requisition item.

Note

You can only view the costs of PBS projects and WBS elements. If you wish to see the details of PBS projects and WBS elements, you require the SAP_BR_PROJ_MANAGE_COMM Business Role.

The key features of the P&L - Plan/Actual (Cloud) (F1710A) app allow you to:

• Specify the search criteria using variables or filters.

• Display the query results in grid format.

• Export the query results to Microsoft Excel.

• Manipulate the query results grid by moving available characteristics to and from the grid axes.

• Display read-only information about the underlying query, such as, its technical name and when it was last updated.

• If your app does not work with a screen reader, you can add a separate, accessible version of this app to your SAP Fiori launchpad. Navigate to the App Finder in your My Area and search for the name of your app.

You can use this app to:

• Maintain the project structure by creating and deleting work packages and by changing their position in the project structure.

• View the most important data of each structure element.

• Change the processing status of the project and its work packages.

• Edit the planned and actual dates of the project and its work packages.

• Edit important organizational assignments of the project or work packages, such as, the responsible cost center or plant.

• View the number of material and service demands assigned to the project or work packages and navigate to the Manage Project Demand app.

• Specify which work packages of a project with revenue are to be used as billing elements for planning revenue and posting actual revenue.

• View the planned project timeline including all work packages in a Gantt chart.

• Change the planned project and work package dates in the Gantt chart.

• Zoom in and out of the Gantt chart to view the project timeline on a scale of days, months, or years.

• Drill down to display or edit detailed project data in the Project Control app.

• Drill down to display or edit detailed work package data in the Work Package app.

• Navigate to related apps to analyze project data, for example, in the Monitor Projects app or the Project Cost Report app.

• Use the drag-and-drop function in the Project Planning app to change the position of a WBS element in the work breakdown structure of the project. This enables you to move a WBS element across several structure levels or up and down several steps in the sequence of WBS elements at once.
• Three new table columns have been added to the Project Planning app that indicate the number of maintenance orders, purchase orders, and sales orders assigned to a project and its WBS elements and that enable you to open the assigned orders in the Maintenance Orders, Manage Purchase Orders, and Sales Order apps respectively.

You can extend the Project Planning app according to your business needs.

Key users can extend the app in the Custom Fields and Logic app using the business context Project Header and Project Element. You can create custom fields in this business context, enable usage of these fields for the Project Planning Model data source in the UIs and Reports section of custom field maintenance, and publish your custom fields.

Business users can display fields that you have enabled in the Custom Fields and Logic app by personalizing certain UI elements. The fields that you enable for the Project Planning app are included in the personalization options for business users for the following UI elements:

With the BAdIs Project Validation and Project Element Validation, you can validate values for properties of the project header and properties of project elements, such as, work packages.

With the BAdIs Project Determination and Project Element Determination, you can determine values for properties of the project header and properties of project elements, such as, work packages.

Key features of the Project Work Package (F3799) app include:

• Viewing the header data of a work package, such as, its planned dates, processing status, and the associated project.

• Editing the organizational assignments of the work package, such as, the responsible cost center, profit center, and plant, the functional location for plant maintenance, and the tax jurisdiction.

• Editing account assignments for Public Sector Management, such as, fund and grant, if Public Sector Management is active in your company.

• Editing the planned start and finish of the work package.

• Editing parameters that control subsequent process steps. Depending on the project profile, you can, for example, define the costing sheet used for overhead calculation, specify whether the work package is to be used as a billing element, or assign the default cost center for statistical postings.

• Editing joint venture accounting attributes if joint venture accounting is active in your company and the work package is to be used as a cost object for a joint venture.

• Blocking functions for the work package, such as, time recording, other expense and service postings, or purchasing activities like the creation of purchase requisitions and purchase orders.

• Uploading or link documents as attachments to the work package and open attached documents from the work package.

• Receiving information if budget consumption for the work package exceeds the thresholds defined in the availability control profile of the project.

• Opening the Maintain Settlement Rule app to create and edit settlement rules for work packages of overhead projects and investment projects.

You can extend the Work Package app according to your business needs.

Key users can extend the app in the Custom Fields and Logic app using the business context Project Element. You can create custom fields in this business context, enable usage of these fields for the data source Work Package Extensibility Model in the UIs and Reports section of custom field maintenance, and publish your custom fields.

You can add published custom fields to the following UI elements using key user adaptation at runtime:

With the BAdI Project Element Validation, you can validate values for properties of project elements, such as, work packages.

With the BAdI Project Element Determination, you can determine values for properties of project elements, such as, work packages.

The Mass Changes to Projects (F3891) app allows you to:

• Display a list of projects and work packages on separate tabs based on a range of filter criteria.

• Select the items that you want to change.

• Specify whether you want to clear, replace, or keep values in the fields.

• View the status of mass change jobs that you have scheduled in the Application Log.

• Define new fields to be involved in mass changes via key user extensibility.

You can extend the Mass Changes to Projects app according to your business needs.

Key users can extend the app in the Custom Fields and Logic app using the business context Project Header andProject Element. You can create custom fields in this business context, enable usage of these fields for the data source Mass Changes to Projects Extensibility Model in the UIs and Reports section of custom field maintenance, and publish your custom fields.

You can add published custom fields to the following UI elements using key user adaptation at runtime:

With the BAdIs Project Validation and Project Element Validation, you can validate values for properties of the project header and properties of project elements, such as, work packages.

With the BAdIs Project Determination and Project Element Determination, you can determine values for properties of the project header and properties of project elements, such as, work packages.

Key features include:

• Getting an overview of the already existing projects rankings.

• Creating new project rankings.

  • Assigning the projects that will be part of your rankings.

  • Analyzing a selected project by navigating to another app, for example to the Project Briefs app.

• Defining the review date for each project ranking.

• Defining a cost threshold for each project ranking to visualize automatically which projects would exceed the targeted cost limit for the upcoming period.

• Prioritizing your projects within each project ranking:

  • Project Priority/Mandatory: The project priority has been directly defined for the project and cannot be changed here. However, by marking a project as mandatory, you can reprioritize the project during the review process, if necessary (without changing the project priority itself).

  • In Scope: Based on the project data and in particular the prioritization information, you define for the upcoming period which projects shall be in scope. Within the list, you can rank a selected project by including it in the scope or excluding it from the scope. You can also move a project up or down.

    All projects you have set to In Scope: Yes are considered as part of your scope.

• Perform status changes for each project ranking to go through an approval process and to make the final version of a ranking available for the corresponding review.

• Delete project rankings if needed.

A Financial Statement Version is a hierarchical arrangement of G/L accounts. Semantic tags are a new kind of financial infrastructure tool that you can use to simplify your work. You can use semantic tags to set standard key figure definitions that can be used in any report.

A key user has to define a financial statement version and configure a cost-related semantic tag. A semantic tag has to be then assigned to the financial statement version. This combination of semantic tag and financial statement version enables the system to determine project costs.

Note

Only costs related to G/L accounts that are assigned to a financial statement item (that in turn belongs to the financial statement version of your controlling area) are displayed in the app.

Budget Availability Control allows you to control budget consumption in your projects. To control budgets in your projects, you first maintain the Budget Availability Control Profile for projects. Then, you activate budget availability control for projects.

To ensure budget relevant costs are displayed by default in the app, you first configure a cost-related semantic tag and associate it with budget relevant financial statement version items. You then assign this semantic tag to a budget availability control profile. Finally, you associate this budget availability control profile with your projects in the Project Control app.

Key features for the Project Budget Report (F3377) include:

• View aggregated and non-aggregated budget relevant (derived using budget availability control profile) planning category and actual costs, budget, and commitments of a project or WBS element based on filter criteria, such as, company code, fiscal year and so on.

  Note

  Only budget relevant costs in global currency are displayed by default. You can choose to display other costs from settings.

• View cost and budget details of multiple projects or WBS elements from different projects and hierarchies in global as well as project currency.

  Note

  Costs and budget in project currency will be blank for a project if a project currency is not defined for that project.

• Configure a planning category and use it for calculation of available budget.

• Enter the level to which a project tree must be expanded.

• Choose a project to view its budget availability control details along with all possible actions that can be performed on the project.

• Select one or more projects or WBS elements and choose View Details to navigate to view budget and costs at the line item level.

  Note

  Where projects do not have an active budget availability control profile, the Only Budget Relevant Values filter has no influence on the table. All costs related to such projects are displayed in the table. Due to this, even when you set the Only Budget Relevant Values filter to Yes, you will still see line items of these projects in the table. Such line items will have No as the value in the Budget Relevant Values column.

• Switch between visual filter and compact filter for budget and costs at the line item level.

• Drill down to view line item costs by fiscal year, fiscal period, company code, controlling area, and so on.

• Select or click data points on the line chart to get more information.

• Navigate to view the details of a project or a WBS element.

• Navigate to view journal entries of a document.

In addition, the app supports the following technical features and options:

This app includes SAP CoPilot, a contextual collaboration tool that allows you to create, collect, and share artifacts (such as, notes, objects, messages, and screenshots) based on the context of the screen you are currently working in.

As a key user, you can extend the Line Items page of the Project Budget Report app according to your business needs.

Key users can extend the app in the Custom Fields and Logic app using the following business contexts:

You can create custom fields in this business context, enable usage of these fields for the data source Extensibility Model for Project Budget Report Line Items in the UIs and Reports section of custom field maintenance, and publish your custom fields.

You can add fields to the following UI elements:

As a prerequisite for these budget processes, a budget availability control profile must be assigned to the projects to which the involved WBS elements are related. You must be authorized to change all WBS elements that are involved in a certain budget process.

You can use this app to do the following:

• Get an overview of all already existing budget documents.

• Create new budget documents to post budget transfers, budget supplements, or budget returns.

• Copy an existing budget document to create a new one.

• Delete a budget documents that has not yet been posted.

• Reverse a budget document that has already been posted. Specify the reason for the reversal.

You can use this app to:

• View the details of a direct activity allocation, including the relevant journal entries.

• Filter for direct activity allocations by various criteria, such as, reference document, status, or posting type.

• Navigate directly to theAllocation Flow app using the Display Allocation Flow button to visualize the links between documents.

• Create, repost, or reverse direct activity allocations.

• Copy the attributes of one allocation to create a new allocation.

• Download templates to use for uploading allocation items.

Post activity allocations using cost rates that you have calculated per ledger with the Actual Cost Rate Calculation app or maintained manually per ledger with the Manage Cost Rates - Actual app. Different values will then be posted in different ledgers.

Note

Activity allocations always post to all ledgers. The posted activity quantity remains the same in all ledgers. However, the values posted can differ between ledgers. The system will use ledger-specific cost rates, if these are available. If there are no ledger-specific cost rates, the system uses the ledger-independent cost rate.

The transaction currencies of cost rates can be different for each ledger. When you post activity allocations, the amount in the transaction currency will be converted to the transaction currency of the cost rate in the leading ledger. As a result, activity allocation uses one currency as transaction currency in the posting document.

Note

There are limits on the number of lines you can upload for some document types. For more information, see 483817 Information published on SAP site.