Hierarchy
EA-FINSERV (Software Component) SAP Enterprise Extension Financial Services⤷
FIN-FSCM-TRM-TM-IS (Application Component) Information System⤷
FTI (Package) Application development R/3 Treasury information system
IMG Activity
| ID | SIMG_VORSCHLAGSGEN | Proposal Gereration for the Payment Relevance of Update Types |
| Transaction Code | S_PLN_62000762 | (empty) |
| Created on | 20040526 | |
| Customizing Attributes | SIMG_VORSCHLAGSGEN | Proposal Gereration for the Payment Relevance of Update Types |
| Customizing Activity | SIMG_VORSCHLAGSGEN | Proposal Gereration for the Payment Relevance of Update Types |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | VORSCHLAGSGENERIER |
Example
Use
Removing the operative valuation area and the integration of its position data into the architecture of parallel position management has made it necessary to reorganize payment reporting. This is done by introducing the FTI_TR_CASH_FLOWS logical database. Payments can thus be made without being dependent on the valuation area.
Payment reporting is based on independent Customizing where payment relevance is assigned to each update type. This assignment is only valid for reporting, not for operative purposes.
Since this is secondary Customizing, sample Customizing is not delivered. Instead, this report enables default proposals to be generated for Customizing. This is carried out in two steps:
- The selected update types that you processed in Customizing up to now are first transferred to the Customizing table regardless of their relevance for payment. All update types are closed and ready for manual postprocessing.
- For OTCs (Money Market, Foreign Exchange and OTC Derivatives), the old Customizing for the area is read and transferred based on the assignment of update types to flow types. For the Securities product group on the other hand, defaults are generated on the basis of the assigned flow types.
Requirements
Standard settings
Activities
Following the generation of defaults you must postprocess them manually in order to check and complete them.
Example
Business Attributes
| ASAP Roadmap ID | 103 | Set up development systems |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
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 |
| TRISB | T - Individual transaction object | TPM_PAY_ASSIGN |
History
| Last changed by/on | SAP | 20040601 |
| SAP Release Created in | 500 |
