Exploring SAP Fiori Applications for Project Control - Research and Development Projects

• 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 and edit project header details. You can also delete enterprise projects.

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

• 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.

• 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 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.

The processing status of a project indicates what part of the project lifecycle it is in. It controls which processing steps are allowed for projects during the individual lifecycle phases.

Based on where the project has reached from a business point of view, the project financial controller or project manager can decide when to change the processing status of the project.

Besides the project header, each work breakdown structure (WBS) element has a status which you can currently only display or set in the Project Builder app. The processing status of the project influences the status of the WBS elements and vice versa.

The available processing status values for projects are:

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.

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

• Assists in the creation, update, and display of operative projects and work breakdown structures.

• You can view the frequently accessed projects in the worklist area.

• In the context of the project financial control process, you can create projects such as overhead projects, investment projects, statistical projects, and projects with direct revenue posting. You can use the individual project profiles to create these projects. Upon creation of a project, the project profile cannot be changed.

• During the creation of a project, it is mandatory to provide the responsible cost center. The company code is subsequently derived from this input.

• You can assign the project manager who is responsible for the overall activities of the project.

• It facilitates the definition of work breakdown structures that serve as a template for creating operative work breakdown structures.

• You can change the status of the project and the underlying work breakdown structures.

• You can use templates to create new objects or objects within the current project.

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

• Overhead Project: You can plan and post costs for your project, monitor the project, and finally close the project. During period-end closing, you can apply actual overhead costs based on the costing sheet maintained in the WBS element, generate settlement rules to the responsible cost center and finally settle the costs, based on your requirement.

• Investment Project: You can plan and post costs, monitor costs and settle costs to asset accounting. By assigning an investment profile to the project or WBS element and upon releasing the WBS element, the asset under construction is generated. All or parts of the costs must be settled to the asset under construction. During the course of the project, the fixed asset is created in asset accounting and maintained in the settlement rules of the project. Once the WBS element is technically complete, then all subsequent cost postings, including the earlier postings done after it was released, are settled to the fixed asset.

• Statistical Project: A statistical project is used for planning and monitoring purposes. When you set the statistical flag for a project, this flag applies to the WBS elements present in the project hierarchy. After you save the project for the first time, you can no longer change the selection of this flag. At the WBS element level, you must set the cost center to which the costs are actually posted by default. Statistical WBS elements cannot be settled or carry overheads.

• Project with Revenue: You can plan and post costs / revenues for your project, monitor the project, and finally close the project. To allow revenue postings to your project, you must set the billing element flag for the corresponding accounting object. Presently, only the root node of the project can have the billing element set. The values associated with responsible cost center, company code, profit center, and functional area are identical across all objects in the project structure.

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

You can implement logic for the following Business Add-Ins (BAdIs) in the Custom Fields and Logic app:

The processing status of a project indicates what part of the project lifecycle it is in. It controls which processing steps are allowed for projects during the individual lifecycle phases.

Based on where the project has reached from a business point of view, the project financial controller or project manager can decide when to change the processing status of the project.

Besides the project header, each work breakdown structure (WBS) element has a status which you can currently only display or set in the Project Builder app. The processing status of the project influences the status of the WBS elements and vice versa.

The available processing status values for projects are as follows:

If the integration of projects with collaborations in SAP S/4HANA Cloud for intelligent product design has been set up for your solution, you can create and access a collaboration for a project directly from the project brief. Project managers and their teams can use these project-related collaborations to plan project-related work items, assign them to the responsible team members, and report and monitor their execution.

As project manager or as a project financial controller, you can create a collaboration for a project by adding a related object of type Collaboration in the project brief. You can only add one collaboration to a project. The system automatically uses the collaboration name <ProjectID>:<Project name>.When you save the project brief, the collaboration is created in intelligent product design and a link to the collaboration is created in the project brief.

Using the link in the Related Objects section of the project brief, you can open the collaboration in the My Collaborations app of intelligent product design. To be able to open the collaboration, you need to be assigned as a participant in the collaboration. When you create a collaboration, you are automatically assigned to it as a participant with Administrator permission. You can invite further participants and select their permissions when editing the collaboration. Make sure that the project manager is always assigned as a collaboration participant with Administrator permission. Each participant who is added to a collaboration automatically receives an e-mail with an invitation and a link to the collaboration. Participants who do not have access to the project brief can open the collaboration using this link.

When working with project-related collaborations, you can use the entire functionality of the collaboration capability in intelligent product design. You have the following options, for example:

• As project manager, you can create single work items or entire workflows to plan project-related tasks in the collaboration.

• You can assign work items to the responsible team members.

• The project manager and team members can share related documents and exchange comments in the collaboration.

• Team members can complete work items in the My Inbox app of intelligent product design.

• The project manager, financial controllers and steering committee members can monitor the completion of work items in the collaboration.

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

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

• Project Header

• Project Status Area

• Project Milestone

You can create custom fields in these business contexts, enable usage of these fields for the data source Project Brief Extensibility Model in the UI and Reports section of custom field maintenance, and publish your custom fields.

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

• Display the upcoming and overdue milestones that are defined for the active projects to which you are assigned as a project manager:

  • See the three most urgent milestones at a glance.

  • See the total number of upcoming and overdue milestones.

  • Drill down to the My Projects - Upcoming Milestones app to display all upcoming and overdue milestones.

  • Drill down to the Project Briefs app to display a specific project brief directly.

• Display the planned projects to which you are assigned as a project manager:

  • See the three planned projects with the earliest start date at a glance.

  • See the total number of your planned projects.

  • Drill down to the Project Briefs app to display all your projects or to display a specific project brief directly.

• Display the Overall Status values that are defined for the active projects to which you are assigned as a project manager:

  • See the five most severe Overall Status values at a glance.

  • See the total number of your active projects.

  • Drill down to the Project Briefs app to display all your projects or to display a specific project brief directly.

• Display all Status values (except for Overall Status) that are defined for the active projects to which you are assigned as a project manager:

  • See the five most severe Status values at a glance.

  • See the total number of all Status values.

  • Drill down to the My Projects - Detailed Status app to display all Status values.

  • Drill down to the Project Briefs app to display a specific project brief directly.

• Display the cost to date of all active projects to which you are assigned as a project manager:

  • See the five projects that have the highest variance between actual and planned cost (sorted by variance).

  • See the total number of your active projects.

  • Drill down to the Project Briefs app to display all your projects or to display a specific project brief directly.

• Display the development of cost to date over time, aggregated across all active projects to which you are assigned as a project manager:

  • See the aggregated actual cost that has been recorded up to the current date at a glance.

  • See the aggregated actual and planned cost-to-date values of the last three, six, or twelve months in a line chart.

  • Display the corresponding figures.

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.

• 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 predefined predictive scenario PROJCOSTFRCAST01 (Project Cost Forecast 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 predefined predictive scenario PREDICT_PROJECT_COST (Predictive scenario for project cost prediction) 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 predefined predictive scenario 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:

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.

• 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 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 theImport 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, the Company 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 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, please 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, please 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 in 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 column CO_BELKZ. If you did not specify a value in column CO_BELKZ, the system posts the data records as a debit (internal value S).

4. Check the imported data. Choose Check Financial Plan Data. The analytical app Financial Plan Data 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.

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.

• 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 work breakdown structure (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

  In case of projects that 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.

• 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:

• View aggregated and non-aggregated plan, actual, baseline, and commitment costs of a projector work breakdown structure (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 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 Business Role SAP_BR_PROJ_MANAGE_COMM.

• Save and view held journal entries before posting.

  Note

  Held journal entries expire 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.

You can extend the Create Purchase Requisition app according to your business needs.

Key users can extend the app in the Custom Fields and Logic app using the business context SSP Purchase Requisition Item. Key users can enable usage of their extension fields for the data source Purchase Requisition Item GUI  in the UIs and Reports  section of the extension field maintenance and publish their custom fields.

Key users can add fields to the following UI elements:

• Search for purchase requisitions based on different criteria such as purchase requisition ID, plant, purchasing group, purchasing organization, material group, and processing status.

• View or edit purchase requisition items.

• View the processing status of purchase requisition items.

• Depending on the status of a purchase requisition item, you can create follow-on documents, such as contracts, RFQs, or purchase orders.

• Preview and edit the follow-on documents that you have created. RFQs created from one or more purchase requisition items can now be previewed and edited directly in the Manage RFQs app.

• Assign sources of supply, such as info records, contracts, scheduling agreements, or suppliers, to the purchase requisition items. Additionally, based on the suppliers operational scores and the price per item offered by the suppliers, you can compare the available sources of supply and assign them to purchase requisition items.

• View the total purchasing spend of various sources of supply.

• View the business card of the supplier.

You can extend the Manage Purchase Requisitions app according to your business needs.

Key users can extend the app in the Manage Purchase Requisitions app using the business context SSP Purchase Requisition Item. You have the following options:

• Add additional fields to the table and pop-up.

• Change the order of fields.

• Save the current layout.

You can also make settings to exclude fields.

Key users can add fields to the following UI elements:

If you have the business role Employee Self Services (SAP_BR_EMPLOYEE), you can perform the following tasks:

• View the total number of missing hours in your timesheet.

• View all the tasks assigned to you.

  In the My Tasks side panel, you can view the list of tasks assigned to you for the selected week, view the list of tasks grouped by accounting objects (like Customer Projects: Billable, Non Project related Task Types, Internal Orders etc.), and the total number of hours recorded (for the selected week) for each task. You can also search a task from the My Tasks list. In addition to the accounting objects available for this app in SAP S/4HANA Professional Services Edition, the following accounting objects are also supported:

  • WBS Element

  • Internal Order

  • Cost Center

  Note

  Only four attributes are displayed for each task, irrespective of the number of attributes assigned to it.

• Change the calendar settings.

  You can change the calendar settings like the showing work week, setting the start day of the week and time format using the Calendar Settings.

• Navigate to the required week.

  You can navigate to the required week using the navigation arrows. You can navigate to the previous or next week. Each week displays days of the week depending on the calendar settings. You can log up to 24 hours of time per day. You can also navigate to any week, by choosing the calendar week link. It opens the calendar in a dialog box and then you can select the desired date from the dialog box. You can also navigate to the previous or next month in the dialog box using the arrow keys.

• Create, edit, and delete time entries for the selected week.

  You can update a time entry and if required, also add a note. You can either save the time entries using Save or send them for approval using Submit.

  Note

  Currently, both internal employees and contingent workers can submit their timesheet for approval. In case of contingent workers, the approved time entries cannot be edited, but can be deleted only if the corresponding Service Entry Sheet is deleted. By default, the approval process is enabled only for contingent workers. You can enable the approval process for internal employees using the configuration app Maintain Data Entry Profiles.

• View the approved and rejected time entries.

  The approved time entries are displayed with a green bar and the rejected entries are displayed with a red bar on the left of the entry. You can select a rejected entry to view the reject reason.

• View last approved time entry.

  You can view the last approved time entry's duration and note in the Time Entry's Details dialog box.

• Manage your tasks.

  You can manage your tasks by using this function. You can select Create Task to create a new task, update a task by selecting the task to be updated, or delete a task in Manage My Tasks. If a purchase order is created with account assignment category Cost Center (K) only then Activity Type is required to Create Task. This is required for inter and intra company sub contractor processes.

  Note

  By default, the task list does not have any tasks for contingent workers. You will have to add tasks manually using Manage My Tasks.

You can extend the Manage My Timesheet app according to your business needs.

Note

You have to select the <Extensibility Mode> field in the Maintain Data Entry Profile configuration app to enable the app extensibility.

Key users can extend the app in the Custom Fields and Logic app using the business context HCM_CATS_MANAGE.

• Add additional fields to forms and tables.

• Change the order of fields.

• Regroup and rename fields.

• Save the current layout.

Key users can use the Custom Fields and Logic app to extend the following business contexts:

• HCM: Timesheet Validations (HCM_CATS_V1_TS_VALIDATION)

  You can use this BAdI to perform the customer specific timesheet validations/checks when you save the timesheet entry.

• HCM: Timesheet Approver Determination (HCM_CATS_V1_APPROVER_DETRMN)

  You can use this BAdI to determine the approver for each timesheet entry and the BAdI also enables you to auto approve the timesheet entry.

You have to select the <Approval Required> field in the Maintain Data Entry Profile configuration app to enable the approver determination for timesheet entry.

• View 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.

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

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

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

• Navigate 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 Business Role SAP_BR_PROJ_MANAGE_COMM.

• 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. Go to the App Finder in your Me Area and search for the name of your app.

• Search for and display BOMs based on a range of filter criteria (such as material, plant, BOM usage, and alternative BOM).

• Create BOMs and alternative BOMs and delete BOMs.

• Copy a material BOM to a new material BOM.

• Hand over engineering bills of material (EBOMs) to manufacturing bills of material (MBOMs).

• Create BOMs for configurable materials and maintain object dependencies using the classic application.

• Take tentative decisions while working on a BOM and save your changes as a draft.

• Assign BOMs to a change record. You can configure the settings to make the assignment of change record mandatory while creating a BOM.

• Navigate to change instances using the change timeline.

• Create a change number and assign it to a material.

• Create a version BOM with validity changes for objects based on the parameter effectivity types for Manufacturing for production engineering and operations.

• Use the Attachment Service to attach documents or files to a material.

• Define software and its versions in a bill of material.

• Hand over bill of material components (spare parts and software) to the SAP Asset Intelligence Network.

• Calculate BOMs using international system of units.

• Use a range of functions on the Components tab when adding BOM items.

• Draft Enablement: Drafts are saved automatically in the background whenever you change information within a business entity (auto-save). This adds features like data-loss prevention, start-now continue-later, device-switch, locking mechanism, and collaborative editing.

• Requirement Assignments: Requirement Assignments reusable user interface component is adopted to assign requirements to PLM objects and manage them using the SAP Enterprise Architecture Designer, cloud edition.

• Data Profiling: You can control the changes made to fields Document Status and Document Desc in the Customizing Define Document Types to appear on the user interface.

• Search Document: You can search for a document using filter criteria such as document number, document type, document version, document part, document description, user, marked for deletion, and status. You can also search using a fuzzy search in the criteria.

• Create Document: You can create a document that stores all the data required to process and manage a document (original application file). Information related to document data, originals, object links, descriptions, and general information (document number, type, part) can be entered.

• Create a New Version: You create a new document version if the following conditions apply: Some of the data of the existing, original document version must be changed. The processing status of the existing, original document version must be saved and processed further.

• Copying a Document: You create a new document by copying from a document if the following prerequisites apply:

  • The document that you want to use as a template for copying must already exist.

  • The document that you copy from must have the same document type as the one you want to create.

• Edit Document: You can edit an active document by opening the document from the List Report page in edit mode and making changes. Click any document number to view information such as document data, originals, object links, document versions, descriptions, and general information.

• Marked for Deletion: You can use the deletion indicator to control that documents are deleted after the next archiving run. You can mark a document for deletion only in edit mode.

• Display Document: You can view document details such as document data, originals, object links, document versions, descriptions, and general information by clicking on a document in the Worklist page.

• Download Originals: You can download one or more original application files by selecting the check box in the Worklist page.

• Classification: The classification system allows you to use characteristics to describe documents according to criteria that you define, and to group similar documents together in classes. Integration of the classification system provides the following document search options:

  • Comprehensive search functions provide a powerful tool for finding documents.

  • Find document via class on the initial screen.

  • You can define extra fields for the basic data screen.

  • You can assign keywords to a document.

• Object Links: You can link documents to a large number of SAP objects (for example, materials, customer) in order to document the objects in more detail for various business processes.

• Create product master data records.

• Copy product master data records.

• Display master data records.

• Edit or change product master data records.

• Mark product master data records for deletion.

You can extend the Manage Product Master Data app according to your business needs.

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

• Product Master General

• Product Master Dimensions

• Product Master Distribution Chains

• Product Master Plant

• Product Master Valuation

• Product Storage Location

They enable usage of their extension fields for the app in the UIs and Reports section of the extension field maintenance and publish their custom fields.

Key users can add fields to the following UI elements:

• Add a software and create its constraints.

• Maintain software constraints and hardware constraints for an embedded software.

• View the available versions of an embedded software.

• Sort software according to the software material or the number of constraints.

• Search for a software.