Ansicht
Dokumentation

SIMG_CFMENUFNMCFZCS - Define Flow Types

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Note:

• Calculation Category NOOP (No Operation)

No flow records are generated from conditions that have been assigned a flow type with a calculation category NOOP. You use this setting if conditions are assigned to a contract for information purposes.

• Calculation Category ' ' (Empty Field)

If you leave the field Calculation Category empty then only fixed amounts can be allocated to those conditions that have been assigned this type of calculation category. The system does not calculate amounts using financial mathemetics (for example, 5% of the disbursement amounts). Instead, the fixed amounts are caluclated pro rata temporis if necessary.(For example, an annual account management charge is calculated proportionately if the contract is repaid or paid off within half a year.) The pro rata temporis calculation is based on the value date for the flow. The previously used calculation category TF* is no longer to be used.

If you use calculation category NOOP or leave the field empty, the flows for this flow type can always be reversed with no prerequisite settings, that is, a reversal sequence does not need to be observed.

• Financial Mathematical Calculation

To enable flows to be included in the financial mathematical calculation, you need to define the following activity indicators:

• For loans managed according to the planned principle, you need to enter the indicator '1 Receivables' or '2 Payables' for the required flows.

• For loans managed according to the actual principle, you need to define the indicators '1 Receivables', '2 Outgoing Payment', '3 Payables', or '4 Incoming Payment' for the required flows.

For loans according to the actual principle, the flow categories 'EABS Write-Down', 'SABS Repayment Write-Down', 'VERZ Waiver', or 'SVER Repayment Waiver' are comparable to flows for incoming /outgoing payments. Moreover, the flows for write-downs and waivers must each receive the same calculation category as the corrresponding flows for receivables and payables.

• Activity Category

1. Posting control

This flag controls whether planned records for a flow are to be generated manually or automatically.

1. Incoming pmnt

Controls whether an incoming payment is to be generated immediately for a debit position (an example of this might be a salary deduction).

1. Third party pmt

Subdivides flow types into two groups. This flag is only relevant for postings to customer accounts.

1. IP clearg

This flag is used for updating loan data in the loans subledger. This only affects advance payments, overpayments and prepayments.

WARNING: You should not set this flag for any other flows, since this would result in a dual update.

1. Withhold.disb.

Flag for withholding amounts from disbursements.

1. Payment details:

• Direction:

If no direction is specified for the flow, the payment details for the loan are not transferred (for example, rate gain, accrual/deferral). Otherwise, the system uses the relevant payment details for the direction specified.

• Payment request permitted:

You can use this field to prevent the generation of payment requests for a particular flow type.

• Individual payment required:

You can use this field to make individual payment mandatory for a flow type.

PERFORM Short Reference   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.

Length: 4937 Date: 20240523 Time: 152700     sap01-206 ( 83 ms )