X hits on this document

590 views

0 shares

0 downloads

0 comments

68 / 190

  • Student data as from

  • Program data from

  • Module data from

.

.

.

You can use this function to calculate the fee based on a user-specified period key. A new

field

has been added to the

screen (transaction PQ FEE CALC).

_

_

You can use this function when there is more than one period key for the defined calculation date. If you do not specify the period key, the fee is calculated for all the period keys that are derived from the calculation date.

The period key is added as one of the source key fields for determining the fee calculation procedure. You can use this function when you want to have different rules for every period key.

Prerequisites

This function is available if you have activated the business function SAP Student Lifecycle Management: Implementation Accelerator (ISHERCM_604_EXIAP_M).

Use When the system has calculated the fees, you can make the required manual corrections.

Manual corrections can only be made for individual calculations and only before they are posted. Manual corrections cannot be made for mass fee calculation runs.

Procedure To make manual corrections after an individual calculation, proceed as follows:

1.

You have run fee calculation for an individual student and are on screen.

2.

In the

field, enter the revised amount.

When you confirm your entry, the system displays the result of the fee calculation and the previous

and new manual correction in the

field.

3. 4.

Enter an explanatory

for the new manual correction.

Choose

in the column to display the distribution. You also can change the

distribution manually.

5.

To post the fee calculation result and the manual correction, choose

with the quick info text

.

Example The following diagram shows the consequences of two manual corrections for the same account key.

© 2009 SAP AG

| sdn.sap.com

| bpx.sap.com 68

Document info
Document views590
Page views612
Page last viewedTue Jan 17 23:52:58 UTC 2017
Pages190
Paragraphs8353
Words64781

Comments