Hierarchy

⤷

⤷

⤷

IMG Activity
ID | WP-ZUSATZBEW. | Assign Flow Types to Application Subfunctions per Condition Group |
Transaction Code | S_ALR_87003835 | IMG Activity: WP-ZUSATZBEW. |
Created on | 19981222 | |
Customizing Attributes | WP-ZUSATZBEW. | Assign Other Flows per Condition Group |
Customizing Activity | WP-ZUSATZBEW. | Assign Other Flows per Condition Group |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | WP-ZUSATZBEW. |
In this step you define the permitted flow types specifically for each condition group 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)
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 subscrip. right (underlying)
035 Other flows: Detach warrant (ex/cum)
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 company code-dependent settings. You define the global settings that apply to all company codes by choosing Assign Flow Types to the Application Subfunctions.
Warning
If you have made entries for the current company code and the current condition group, only these entries are taken into account. This means that if you maintain entries in this step, the global settings become inactive.
If you do not maintain company code-dependent entries here, the settings in the cross-company code table you make by choosing "Assign Other Flows" will be valid.
Example
For purchase transactions you only want to allow brokerage (flow type 3001) and commission (flow type 3002). 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 Other Flows
App FType
003 3001
003 3002
2. Choose Assign Other Flows per Condition Group
CoCd CGrp AppFunc FType
1234 010 003 3001
1234 010 003 3002
1234 010 003 3005
Note
For information on maintaining cross-company code data, see Flow Types -> Assign Other Flows.
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 | WP-ZUSATZBEW. | 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_TWB08 | V - View | SM30 | WERTPAPIER |
History
Last changed by/on | SAP | 20000718 |
SAP Release Created in |