Hierarchy
⤷ BC-SRV-COM (Application Component) Communication Services: Mail, Fax, SMS, Telephony
⤷ SO (Package) SAPoffice
Basic Data
Data Element | SO_PARTYPE |
Short Description | SAPoffice: Parameter type |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | SO_PARTYPE | |
Data Type | CHAR | Character String |
Length | 2 | |
Decimal Places | 0 | |
Output Length | 2 | |
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 | 10 | Param.type |
Medium | 15 | Parameter type |
Long | 15 | Parameter type |
Heading | 15 | Parameter type |
Documentation
Definition
Type of the respective parameter. 'RT' for runtime, 'US' for user master, and 'PC' for PC connection are supported. However, 'PC' is the only type under which you should encrypt new parameters in the customer system.
Use
When PC applications are connected in SAPoffice, it is better for performance if the path for common applications is held in parameters.
There are a few parameters in SAPoffice which are not to be set via the Office user.
These parameters are therefore encrypted in table TSOPA and not in TPARA.
Example
You know that a specific PC application is used frequently for which a parameter has not yet been encrypted in the standard version (e.g. for the file extension 'CRD').
It would therefore be better for your system if the register was not read each time a CRD document was called but if the path for the appropriate application was available in a SET/GET parameter after the first call. This would reduce runtime.
Proceed as follows:
- Find a parameter name which does not yet exist in table TSOPA and is not used by another application via TPARA.
- Reserve this name in TRESN so that it is not possible for someone else to encrypt the name later in TPARA. (Important!)
- Enter your parameter in TSOPA. Enter pc for the parameter type and crd for the function.
Dependencies
From now on, the path for the application belonging to 'CRD' is only read in the register once per screen session.
The path is taken from your parameter for the second and all subsequent calls of a CRD document.
History
Last changed by/on | SAP | 19970214 |
SAP Release Created in |