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 | DEFAULT_ZUSATZBEW. | Assign Flow Types to Application Subfunctions |
| Transaction Code | S_ALR_87004397 | IMG Activity: DEFAULT_ZUSATZBEW. |
| Created on | 19981222 | |
| Customizing Attributes | DEFAULT_ZUSATZBEW. | Assign Other Flows |
| Customizing Activity | DEFAULT_ZUSATZBEW. | Assign Other Flows |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | DEFAULT_ZUSATZBEW |
In this step, you define the permitted flow types for the following application subfunctions in the securities area:
Application
subfunction Short name
001 Purchase
002 Sale
003 Other flows: Purchase
004 Other flows: Sale
021 Securities account transfer (outflow)
022 Securities account transfer (inflow)
026 Other flows: Give notice on bond
027 Other flows: Stock swap (old stock)
028 Other flows: Stock swap (new stock)
029 Other flows: Exercise warrant (warrant)
030 Other flows: Exercise warrant (underlying)
031 Other flows: Exercise convertible bond (bond)
032 Other flows: Exercise convertible bond (ref.sec.)
033 Other flows: Post subscription right (sub.right)
034 Other flows: Exercise subscription right
035 Other flows: Detach warrant (cum/ex)
036 Other flows: Detach warrant (warrant)
037 Other flows: Incoming payments
038 Manual posting
You can set up the permitted flow types in varying detail:
- Globally
To do this, you define the flow types per application function.
- Per company code / condition group
To do this, you define the flow types per company code, condition group and application function.
In this step, you define only the settings that apply globally for all the company codes. You define the settings for each company code and condition group by choosing 'Assign Flow Types to Application Subfunctions per Condition Group'.
Warning
If you have made entries for the current company code and the current condition group, only these entries are included. This means that if you make entries in the 'Assign Flow Types to Application Subfunctions per Condition Group' step, the settings you make here become inactive.
If, however, you have not maintained company code-dependent data, the data you enter here in the cross-company code table is permitted.
Example
As a rule, you want to allow only brokerage (flow type 3001) and commission (flow type 3002) as other flows for purchase transactions.
For stock purchases (condition group 010) in company code 1234, however, you also want to allow taxes (flow type 3005).
Make the following entries:
1. Choose Assign Flow Types to Application Subfunctions
AppFunc. FType
003 3001
003 3002
2. Choose Assign Flow Types to Application Subfunctions per condition group
CoCd CGrp. AppFunc. FType
1234 010 003 3001
1234 010 003 3002
1234 010 003 3005
Note
For information on maintaining data relating to the company codes and the condition groups, see Condition Types -> Assign Flow Types to Application Subfunctions per Condition Group.
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-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 | DEFAULT_ZUSATZBEW | 0 | HLA0100041 | Treasury Management |
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_TWB08A | V - View | SM30 | 0000000000 |
History
| Last changed by/on | SAP | 20000718 |
| SAP Release Created in |
