Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
WBON (Package) WWS: Bonus
Basic Data
| Data Element | KALSM_KRUST |
| Short Description | Schema "Account key for provisions for accrued income" |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | KALSM | |
| Data Type | CHAR | Character String |
| Length | 6 | |
| Decimal Places | 0 | |
| Output Length | 6 | |
| Value Table | T683 |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | PROCEDURE | |
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Schema |
| Medium | 15 | Schema |
| Long | 20 | Schema |
| Heading | 6 | Schema |
Documentation
Definition
Schema that defines a different account key for posting provisions for accrued income if settlement accounting has already been performed for the arrangement.
Example
If a goods receipt is posted after settlement accounting has been performed, Subsequent Settlement can no longer manage any provisions for accrued income. Data should not be posted to the account normally used for provisions for accrued income.
- You can no longer post the provisions for accrued income.
This may be useful for arrangements with one-time settlement. The material stock is valuated differently.
- Alternatively, you can post the provisions for accrued income to a separate account using a different account key.
This procedure is to be used for arrangements that are to be extended periodically. The material stock is not valuated differently here.
Enter the condition types in the schema and maintain the different account key for provisions for accrued income.
History
| Last changed by/on | SAP | 19990318 |
| SAP Release Created in |
