SAP ABAP IMG Activity GART_DEFINITION_WP (Define Transaction Types)
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 | GART_DEFINITION_WP | Define Transaction Types |
Transaction Code | S_ALR_87009287 | Securities: Fin. Transaction Types |
Created on | 19990301 | |
Customizing Attributes | GART_DEFINITION_WP | Define Transaction Types |
Customizing Activity | GART_DEFINITION_WP | Define Transaction Types |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | GART_DEFINITION_WP |
In this section, you define your transaction types and assign these to the product types. You also define the important technical aspects of managing a transaction using the product types you have defined.
Requirements
- You have defined the product types you require in the IMG activity Define Product Types.
- You have created at least one number range interval in the IMG activity Define Number Ranges for Transaction.
Activities
- Use the New Entries function to create a new transaction type.
- Select a product type for which you want to define a transaction type. (Do not enter a long name since it is copied automatically from the product type).
- Enter a short key (three-character alphanumeric field) as the name of the transaction type.
- Enter the long name for your transaction type.
- Assign a transaction category to the transaction type. You can use transaction categories 100 (purchase) and 200 (sale) for each product category in the securities area.
- Assign a number range interval to the transaction type for the transactions and a number range for the underlying.
- Assign your transaction type to a processing category. The processing category determines which activity categories are intended for a transaction type and reflects the individual steps you must perform for a transaction. You can choose between the following two processing categories:
- 00001: Order - Contract
- 00002: Order - Contract - Settlement
A transaction can pass through different activity categories depending on which processing category you choose.
- If you set the Automatic posting release indicator, you can post the transaction flows generated without explicitly releasing them.
If you do not set this indicator, you must release a transaction before you can post it.
- In the Status management section you can specify a Status profile. You define the status profiles themselves in the IMG for the Transaction Manager by choosing General Settings -> Transaction Management -> Status Management -> Define Status Profiles.
- In the Automatic date determination section you can specify a date rule. This rule is used to determine the default proposals for the fields Position value date, Calculation date and Payment date in the screen for entering the transaction. You define the date rules in the IMG by choosing Securities -> Transaction Management -> Transaction Types -> Define Date Rules.
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 | GART_DEFINITION_WP | 0 | KFM0000009 | Transaction Management |
SIMG | GART_DEFINITION_WP | 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_GART2 | V - View | SM30 |
History
Last changed by/on | SAP | 20000718 |
SAP Release Created in |