Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
FVV (Package) R/3 application development for Financial Assets Management
Basic Data
| Data Element | SZEGEN |
| Short Description | Generate incoming payment immediately |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | SZEGEN | |
| Data Type | NUMC | Character string with only digits |
| Length | 2 | |
| Decimal Places | 0 | |
| Output Length | 2 | |
| Value Table | TD21 |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Inc.pmnt |
| Medium | 15 | Incoming pmnt |
| Long | 20 | Incoming payment |
| Heading | 3 | IP |
Documentation
Definition
The indicator controls the immediate generation of an incoming payment together with the debit position.
Use
Can be used if the payment is guaranteed but carried out in another system.
Examples
The payment is withheld from wage/salary.
Supplementary Documentation - SZEGEN 0000
Incoming payments field settings
You can use the incoming payments field to manage how incoming payment flows are generated.
Background
You need incoming payment flows if you want to post incoming payments from income (e.g. interest), repayments or refunds of overpaid taxes via a receivables account. You first post a flow which creates a receivable (account determination: receivable to income or receivable to position). When you actually receive the incoming payment, you then post an incoming payment flow which clears this receivable again (account determination: bank clearing to receivable).
Receivables flows are usually posted via the automatic posting function. At the same time the system generates the incoming payments flows, which you then post via the incoming payments function.
The incoming payments field manages whether and how the first receivables flow automatically generates a second flow during posting.
Procedure
- Enter 01 or 02 for the flow type you want to set up as the receivables flow (account determination: receivable to income or receivable to position). This generates an incoming payment flow for this flow type when you post the flow. Leave the field empty for all other flow types.
- Enter 01 or 02 in the incoming payments field for the flow types and company codes in which you want to use these receivables flows. 01 means the incoming payment flows are generated as planned records. 02 means they are generated as actual records. It is not usually meaningful to use setting 02.
Example
You want to post the interest received via a receivables account in company code 0001 for product type 04I (fixed-interest securities). However, for stocks you have in the same company code, you want to post the dividends not via a receivables account, but directly in a bank clearing account.
To do this, you have to make the following settings:
- Set the incoming payments field to 01 for flow type 5000 (nominal interest). This flow type is set up as a receivables flow in the account determination.
- Leave the incoming payments field blank for flow type 6000 (nominal interest IP). You set up this flow type as an incoming payments flow for the receivable in the account determination.
- Leave the incoming payments field blank for flow type 5013 (dividends) since no IP flows are generated for this.
- Set the IP field to 01 for product type 04I (fixed-interest securities) in company code 0001, since IP flows are generated as planned records for this flow type in this company code.
- Leave the incoming payments field blank for product type 01A (stocks) in company code 0001, since no IP flows are generated for this.
Note
Only the incoming payments field is relevant for the flow type for refundable taxes (flow category KTR). The product type settings in a company code are not taken into account. If you therefore set the incoming payments to 01 or 02 for a flow type with flow category KTR, the system generates IP flows for all product types and all company codes when you post this flow.
Requirements
You have set up the incoming payments flow type (6000 in the example) as an offsetting flow for the receivables flow type (5000 in the example) with offsetting flow type 01 (incoming payments).
History
| Last changed by/on | SAP | 19980617 |
| SAP Release Created in |
