Hierarchy
⤷ PPM-PRO-EXT-OBL (Application Component) Object Links
⤷ DPR_OBJECTLINK_R3 (Package) Project Management - R/3 Core Object Link
Basic Data
Data Element | OLR3_TV_PVALUE |
Short Description | Parameter Value in a Start URL |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | OLR3_PVALUE | |
Data Type | CHAR | Character String |
Length | 132 | |
Decimal Places | 0 | |
Output Length | 132 | |
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 | Value |
Medium | 15 | Value |
Long | 20 | Parameter Value |
Heading | 25 | Parameter Value |
Documentation
Definition
Used to generate a start URL for the SAP GUI for HTML. The system then uses this URL to call an SAP transaction using the ITS (Internet Transaction Server). You can instruct the system to automatically fill the initial screen with the required data, so that the user lands directly in the corresponding transaction.
The start URL for calling an SAP transaction must be set up in the following way:
<Web Server Address>?<Transaction>& <Ok-Code>& <Screen-Field>
Use
Enter the following values for the parameters:
- Screen field:
A component of the DDIC structure, which describes the external identification or the internal key of each Project Management object type for object links. If both structures exist, use a component from the identification structure. The corresponding names of the DDIC structures are defined in Customizing for Project Management in the activity Define Object Types for Objects Links. You can determine the components for these data types in the ABAP dictionary using the transaction SE12.
The name of the screen field must exist in the initial screen of the SAP transaction.
- ~TRANSACTION:
The name of the SAP transaction to be called.
- ~OKCODE:
The OK code for the initial screen of the SAP transaction to be called.
The OK code is required for skipping the initial screen.
- ~CLIENT:
The name of the client in which the SAP transaction should be started.
The client must exist in the target system. If you do not enter a client the system determines the client from the RFC destination defined in the object type for object links.
- ~LANGUAGE:
The language abbreviation for the language in which the SAP transaction should be started.
If you do not enter a language abbreviation, the system uses the current language settings in the Project Management system to call the SAP transaction.
Dependencies
You must define the Web server address of the Internet Transaction Server in Customizing for Project Management in the activity Define Object Types for Object Links. The SAP system of the transaction to be called should be assigned to this Internet Transaction Server. If the Web server address you define does not contain the service "WebGui", the system generates the string "scripts/wgate/webgui/!?" with it in the start URL.
For more information about the syntax of a start URL for calling an ITS service from the Web browser, see the SAP@Web Installation Guide, Release 6.10 Compilation 1:
- <protocol> ://<webserver>:<port>/<execdir>/<wgateexec>/<service>/!
- <protocol>: Specify HTTP or HTTPS. If you do not specify a protocol the system uses HTTP.
- <webserver>: Specify the Web server URL (hostname.domain:port) of your Internet Transaction Server.
- <execdir><wgateexec><service>: For calling SAP transactions using the Plug-In "WebGui", you require the string "scripts/wgate/webgui/!?" in the start URL, for example.
Example
Parameter name Parameter value
*PROJ-PSPID PSPID
~TRANSACTION CJ08
~OKCODE MDTB
~CLIENT 100
~LANGUAGE EN
History
Last changed by/on | SAP | 20141109 |
SAP Release Created in | 200 |