# |
Title |
Description |
SAP Comments |
3 | CO report enhancements | Standard CO reports should include the following:
|
Selection requirements feasible. Will
be discussed with CO
Display of FM data in CO is not SAP’s philosophy |
6 | CC Group movement enhancement | Ability to move Cost Centre Groups without the requirement that the group be empty. | SAP effort is not low! Will be discussed with CO |
10 | Historical information retention | Point-in-time info - e.g. the value of FM commitments at a specific historical point in time - yes, we can work it out but it's a lot of trouble (so we store it in our own tables); or inventory values - if we don't run a report and download it immediately after a physical inventory count, then the value of the inventory at that point in time is lost. | Accounting view on open items might solve that with 4.6C (to be verified) |
11 | FM account assignment history / multiple display option | Allocation of Cost Centre to FM Account Assignment: Provide a change history for this function and provide a display screen that lets the user look at more than one cost centre at a time. | Change history: Huge volume of data
Display: Will be discussed with FM development.
|
12 | Sales & Distribution integration with FM in sales order processing | We would like to enter multiple funds when processing a sales order with many line items. We don't want to split one sales order line but would like an easy way to enter the different funds for every line item. When the user selects the Account Assignment screen, the "Objects Allocation: Funds Management" dialog box appears displaying the line item number and FUND field. We would like the dialog box or a fast entry screen to display all line items so that multiple funds can be entered. (For example in MM when processing a PO with many line items, you click on the "Repeat Account Assignment" button) | Requires change of transaction logic in SD. SD operates that way, since applications other than FM derive the account assignments. Requires SAP Public Sector to convince SD development. |
13 | Sales & Distribution sales order processing - billing plan type | When creating a sales order with
a" Milestone" billing plan attached to it, the user must be able to enter
the values to be billed on the date specified in the billing plan
Or enter the percentage of value to be invoiced on the date specified in the billing plan. Currently the user enters the billing values and cannot enter the percentage of value to be billed. Only 100% can be entered. Transaction VA01 and order type ZRS1 is used. |
Requires discussion with SD development. |
14 | HR information to be held against the fund and fund centre master | The ability to enter either a staff number, position number or org number against a fund centre or fund. This would involve entering the HR object type and object number against the fund or fund centre master | To exchange the user name in the funds center
for a position or personnel number is an interesting request.
If such a development ocurred it would no longer be possible to apply the user name of the funds center as the recipient of a warning e-mail from the FM availability control. Thus, a change in the funds center would also require to rethink the appropriate recipient of warning e-mails from availability control. To apply an org. number, position or personnel number against the fund would be a totally new development since currently neither one of the above nor a user name is assigned to a fund. |
15 | Structural funds centre authorisations | A facility to be able to enter a funds centre and hierachy indicator in authorisation profiles, so that authorisations to a fund centre and all funds centres below it are automatically included. Similar to structural authorisations in HR. | Requires substantial SAP development, since the authorization object would need to be changed in master data, budgeting, reporting. |
24A | Maintenance of authorisations | The profile generator and the principle of structural
authorisations help a lot to create the correct profiles, but there is
still a need to have more tools to maintain the authorisations and to assign
them to users.
Case 1: HR By using structural authorisations it is possible to restrict the authorisations in HR-PD for a user to a part of the organisational structure. It is typically used for managers to see or maintain only the information related to the organisational units he is responsible for. Although in setting up the profiles the starting object for the authorisation
is derived by using the defined relationship(s) for managers, these relationship(s)
aren't used in the assignment of the authorisation profiles to users. There
it is still necessary to explicitly enter the users for whom the structural
authorisation profile must be checked. This is what we want to avoid.
The financial budgets are managed via Funds centres and Funds in FM. Although there is a 'person responsible' assigned to every Funds centre (in master data), there is no authorization object that makes use of this information. Every new funds centre has to be put in the correct profile, and assigned to the correct responsible. Further more these responsibles delegate the administrative work for their funds centres (create purchase orders, approve invoices, reporting, ...) |
This is an extension of the structural authorization
in HR and requires development to recognize customer relationships for
structural authorisations.: The request requires a new function module
to be developed by SAP HR core. The critical point is that SAP’s philosophy
in HR is against assigning a person directly to a organizational unit,
as conducted at K.U. Leuven.
Requires SAP Public Sector to convince HR development. |
24B | Maintenance of authorisations 2 | The financial budgets are managed via Funds
centres and Funds in FM.
Although there is a 'person responsible' assigned to every Funds centre (in master data), there is no authorization object that makes use of this information. Every new funds centre has to be put in the correct profile, and assigned to the correct responsible. Further more these responsibles delegate the administrative work for their funds centres (create purchase orders, approve invoices, reporting, …) |
This relates to FM and seems like an extension
of the UCT request to maintain the personnel number, or position or org.
number at the fund center / fund. SAP requests more information on the
rules / business cases of case 2.
Action Item: To provide the business cases / rules that K.U. Leuven applies. |
25 | Integration of HR-FPM (funds and position management) and PS (project system). | The required functionality is exactly the same
as what is offered for FM (funds management) from release 4.6, but for
PS-budgets instead of FM-budgets.
In the module FPM you will be able to assign directly a funds center - fund -combination to a position, which leads in FM to the necessary pre-commitments, commitments and actual postings. In the same way it should be possible to assign a WBS-element to a position, with the same effects on the PS-budgets as stated above for the FM-budgets |
No short or medium term development goal. Any development into that area is tied to a new budget processor, and new dimensions in FM. |
28 | Teaching assignments | The required functionality should allow to recruit academic staff starting from vacant courses or parts of courses (tasks, event types, modules,...), rather than from vacant positions. | The development request would be subject to new development by SAP HR. Requires SAP Public Sector to convince HR development. |