Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
FVVW (Package) Treasury Management: Securities
IMG Activity
| ID | SIMG_CFMENUFWMCFZBE | Assign Flow Types to Flow Category |
| Transaction Code | S_ALR_87004407 | IMG Activity: SIMG_CFMENUFWMCFZBE |
| Created on | 19981222 | |
| Customizing Attributes | SIMG_CFMENUFWMCFZBE | Assign Flow Types to Flow Category |
| Customizing Activity | SIMG_CFMENUFWMCFZBE | Assign flow types to flow category |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CFMENUFWMCFZBE |
Flows are generated automatically for certain business transactions. In such cases, the transaction and flow category are linked (hard-coded). Flow categories control how flows are processed technically for accounting purposes (also refer to the section on "Flow types"). In most cases, the same flow categories are used for inflows and outflows. Inflows are then distinguished from outflows using the debit/credit indicator in the flow type. Since more than one flow type with a debit or credit indicator can be assigned to a flow category, you must define in this step which of the permitted flow types should be used for a condition group (and as such for a product type).
You must make this assignment for all flow categories for which you generate flows, regardless of whether the combination of flow category and debit/credit indicator is relevant for only one or for several flow types.
In the standard Customizing settings delivered with the system, default flow types are defined for all flow categories that require such an assignment.
Examples
- When you exercise a subscription right, the system generates an outflow of subscription rights and an inflow of corresponding stocks. In order to post the respective in- and outflows, the system requires flow types, which in turn have to be assigned to the flow category.
- The user must be able to distinguish between flows that have the same combination of flow category and debit/credit indicator. For example, you may want to distinguish between inflows from legacy data transfers and inflows from purchases. To do this, you create two flow types:
Flow type Flow category Debit/Credit
a) 1000 purchase A D
b) 1001 legacy data transfer A D
When the postings result from a legacy data transfer, flow type 1001 is assigned to flow category A. When normal processing is resumed, flow type 1000 is assigned to flow type 1000.
Requirements
You have already defined the flow types.
Activities
Assign flow debit flow types and credit flow types to the flow categories line by line. It does not matter which side you enter the debit or credit flow type on.
Note:
In some cases, the flow category itself is classified as a debit or credit flow. You then only assign one flow type to the flow category.
Further notes
If you have changed and inserted flow types, check whether the changes affect this table and make any necessary adjustments.
New entries should normally not be made by the user, since the relationship between flow categories and system programs or transactions is hard-coded in the system.
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 1 | Critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | SIMG_CFMENUFWMCFZBE | 0 | KFM0000011 | Transfer to Financial Accounting |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| V_TWBBBN | V - View | SM30 | 0000000000 | Call view maintenance |
History
| Last changed by/on | SAP | 20000718 |
| SAP Release Created in |
