Hierarchy
EA-FINSERV (Software Component) SAP Enterprise Extension Financial Services⤷
FIN-FSCM-TRM (Application Component) Treasury and Risk Management⤷
FTPC (Package) Customizing Treasury: Portfolio management
IMG Activity
| ID | BEWARTENGESCHAEFTWP | Define Flow Types |
| Transaction Code | S_ALR_87009293 | Securities: Flow Types |
| Created on | 19990301 | |
| Customizing Attributes | BEWARTENGESCHAEFTWP | Define Flow Types for Transaction |
| Customizing Activity | BEWARTENGESCHAEFTWP | Define Flow Types for Transaction |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | BEWARTENGESCHAEFTWP |
In this step, you define all the flow types which you require in the transaction management functions.
You assign a flow category to each flow type. The system uses the flow category to determine the calculation category. The classification, which divides the flow types according to business criteria, is always 'structure' for transaction flow types, and is therefore predefined in the system.
For each flow type, you define whether you want the flows to be updated to Cash Management and Financial Accounting, in other words, whether they are relevant to Cash Management and to posting.
Using the 'net payment amount' indicator, you can determine whether the flow is included in the net payment amount calculation.
In the payment management area, indicate whether payment requests, which are executed using the 'payment program for payment requests', can be generated for this flow type. To do this, enter the corresponding payment details in the transaction. You can choose from the following payment requests for each flow type:
- None
- For outgoing payments
- For incoming payments
- For outgoing and incoming payments
Use the 'individual payment' field to control if the flow with this flow type must be paid together with other flows, or if a single payment is necessary.
Note here that the payment requests function is an optional condition, but that the individual payment function is a required condition. In other words, if the indicator is set for payment requests, a payment request CAN be generated. If, however, the individual payments indicator is set, payments MUST be made individually.
Recommendation
Use the settings in the sample Customizing when you define the flow types for the transaction.
Activities
- Choose new entries. The 'New Entries: Details of Added Entries' screen appears.
- Enter an alphanumeric key and a name for the flow type.
- The classification is preset to structure. Choose a flow category from the permitted categories. The system assigns the calculation category automatically.
- Set the 'relevant to CM' indicator if you want the flows to be updated to Cash Management, and set the 'relevant to posting' indicator, if you want the flows to be transferred to Financial Accounting.
Business Attributes
| ASAP Roadmap ID | 203 | Establish Master Data |
| Mandatory / Optional | 1 | Mandatory 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 | BEWARTENGESCHAEFTWP | 0 | KFM0000009 | Transaction Management |
| SIMG | BEWARTENGESCHAEFTWP | 1 | O I070004705 |
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_BWGART2 | V - View | SM30 |
History
| Last changed by/on | SAP | 20030220 |
| SAP Release Created in |
