Hierarchy
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ MB (Package) Application development R/3 inventory management
Basic Data
Data Element | J_VORGANG_S |
Short Description | Business transaction/event (debit) |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | J_VORGANG | |
Data Type | CHAR | Character String |
Length | 4 | |
Decimal Places | 0 | |
Output Length | 4 | |
Value Table | TJ01 |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | TRANS | |
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Trans._D |
Medium | 15 | Bus. trans_D |
Long | 20 | Business trans._D |
Heading | 7 | Trans_D |
Documentation
Definition
Specifies the action the user is carrying out on the screen (for example, a transaction or a function).
Use
The system distinguishes between debit and credit postings according to the following procedure:
When you enter a goods receipt, for example with movement type 101 or 102, the system determines the posting string reference in the table T156 via the field BUSTR. The posting string reference with 101 is at first identical for both movement types. The system then determines via the debit/credit indicator whether the movement is a goods receipt (debit) or an issue (credit).
Depending on the debit/credit indicator, the field for either debit or credit is used.
Objects that use general status management can decide at transaction/event level which functions are allowed or forbidden.
Examples
You carry out a business transaction when you:
- Post a G/L account
- Release an order or project
- Post a goods receipt
- Enter a confirmation
History
Last changed by/on | SAP | 19990125 |
SAP Release Created in |