SAP ABAP Data Element PRVRG (Business transaction for validations)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ KABR (Package) Appl. development: R/3 Cost Accounting order settlement
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ KABR (Package) Appl. development: R/3 Cost Accounting order settlement
Basic Data
Data Element | PRVRG |
Short Description | Business transaction for validations |
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 | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | ValidTrans |
Medium | 15 | ValidationTrans |
Long | 20 | Validation trans. |
Heading | 0 |
Documentation
Definition
Consistency checks on data entered depend partly on the commercial transaction carried out. If this is not specified precisely enough for, among other things, the activity used in FI-GL, (COBL field VORGN), you can set a different checking procedure here.
Use
Within the program, for communication between function modules.
Examples
VORGN = 'Financial account posting', PRVRG = 'Down payment'
For updates in FI-GL, you need enter only the "Financial acccounting document", but more detailed information is needed to create AM line items. You need not fill the PRVRG field, but, if you do not, components accessed have to take the activity from the VORGN field.
History
Last changed by/on | SAP | 19981111 |
SAP Release Created in |