Hierarchy
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ CU (Package) Variant Configuration
Basic Data
Data Element | PAR |
Short Description | Name of settings for configurator |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | CHAR55 | |
Data Type | CHAR | Character String |
Length | 55 | |
Decimal Places | 0 | |
Output Length | 55 | |
Value Table |
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 | 9 | Parameter |
Medium | 9 | Parameter |
Long | 9 | Parameter |
Heading | 9 | Parameter |
Documentation
The user settings, profile settings, and current settings that you have defined are listed here.
Supplementary Documentation - PARAFB 0001
Use
You can only display takeover areas in this screen. You can maintain the rules for takeover in the Customizing definition of the depreciation area (Valuation -> Areas).
Procedure
Examples
Dependencies
Supplementary Documentation - PARAMID 0001
Use
At this point just use the parameter IDs with the origin 4 (user field from operation).
Dependencies
The parameter IDs are saved in Customizing under Set formula parameters.
Supplementary Documentation - PARGB 0001
Use
The clearing business area is transferred automatically from the account assignment object (for example cost center) if it is defined there.
Supplementary Documentation - PARGB 0002
Use
A business area entered here is set as the default value in all non-automatic G/L account items and can be overwritten during entry.
Supplementary Documentation - PARGR 0001
You define partner determination schemas and partner roles in Customizing for the Project System, under
Structures -> Operative Structures -> Project Structure Plan
Supplementary Documentation - PARM1 0001
Use
T52C0
Procedure
Examples
Dependencies
Supplementary Documentation - PARM1 0002
Use
T52C1
Procedure
Examples
Dependencies
Supplementary Documentation - PARM2 0001
Use
T52C0
Procedure
Examples
Dependencies
Supplementary Documentation - PARM2 0002
Use
T52C1
Procedure
Examples
Dependencies
Supplementary Documentation - PARM3 0001
Use
T52C0
Procedure
Examples
Dependencies
Supplementary Documentation - PARM3 0002
Use
T52C1
Procedure
Examples
Dependencies
Supplementary Documentation - PARM4 0001
Use
T52C0
Procedure
Examples
Dependencies
Supplementary Documentation - PARM4 0002
Use
T52C1
Procedure
Examples
Dependencies
Supplementary Documentation - PARNR 0100
Use
When using the interface for upload sales activities, you must note that this contact partner will be checked in the partner table with function 'AP' and counter '0'.
Otherwise, the 'usual' partner processing rules apply.
Supplementary Documentation - PARVW 0001
Procedure
Enter the partner function that you want the system to check for during this access.
Supplementary Documentation - PARVW 0002
Procedure
Enter the partner function with which you want to determine the language for this access.
Supplementary Documentation - PARVW 1964
Use
In this field, you define the partner function for appropriation requests, for which the function holder is to be written to the summarization database.
Supplementary Documentation - PARVW_VERA0001
Use
Enter a partner function in this field, if you want to be able to enter a partner for this partner function on the header data screen of the order.
Procedure
Examples
Dependencies
- If you enter a partner function in this field, a field appears on the order header data screen, in which you can enter the name of the person responsible for the order.
- If the partner function in this field is of the type "Person" and the Debit field is selected (marked), the system checks whether the person entered in the Partner field has been assigned to the work center responsible.
- If you want the system to create split records automatically for all operations in the order, you must:
- Ensure that the work center performing the operations corresponds to the work center entered as responsible in the order header.
- Mark the Debit field in this table for this order type
The created split records are also immediately planned.
Supplementary Documentation - PARWE 0001
Use
This field enables you to define the different specifications for
a function parameter.
Procedure
Examples
Dependencies
Supplementary Documentation - PARWE 0002
Use
This field enables you to define the different specifications
for a function parameter.
Procedure
Examples
Dependencies
History
Last changed by/on | SAP | 19990520 |
SAP Release Created in |