Versions Compared

Version Old Version 2 New Version 3
Changes made by

ProNovia

ProNovia

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Class /PCH/CL_OBJ_NAV_HANDLER_TX
The handler allows navigation to a freely definable SAP transaction, where appropriate user parameters can be defined for calling the transaction. It is possible to set parameters before calling the transaction and retrieve parameters after calling the transaction.

Parameter

Description

TRANSACTION_CODE

Transaction code of the transaction to be called

SKIP_FIRST_SCREEN

Skip initial screen (for transactions with initial screen).

NEW_WINDOW

Open the transaction in a new window.

WAIT

Wait for the end of the update program after the transaction has ended.

KEY_TYPE_NAME

Technical type of the key. May be required for structured keys.

<SET/GET Parameter ID>

Specification of the parameter ID to be set (e.g. MAT for material). Short form for E:<SET/GET Parameter ID>.

E:<SET/GET Parameter ID>

Specification of a parameter ID to be set. Can be used to make the parameter flow clearer or to set a parameter with a reserved name.
Supported placeholders:

  • <OBJECT_KEY> or <OBJECT_KEY>-[field name] - Passed object key or, if created, the newly created object key for the return transport.

  • <VALID_FROM> - Valid from (if passed in the call).

  • <VALID_TO> - Valid until (if passed in the call)

  • <CHANGE_NUMBER> - Change number(if passed in the call).

  • <KEY_DATA> or <KEY_DATA>-[field name] - specify key data for the asset (e.g. document type or material number). Only for plant.

  • <REF_OBJECT_KEY> or <REF_OBJECT_KEY>-[field name] - key of the reference or template object. Only when creating with template and if passed when calling.

I:<SET/GET Parameter ID>

Specification of a parameter ID which is to be transported back after the transaction call. Only supported for action "Create" and for the new object key.

Image Removed
Note

The KEY_TYPE_NAME information can or must be specified if no object type is known at runtime or if a key structure different from the object type is to be used.

...

Note

With the retrieval (import) of user parameters the key data of a just created object can be retrieved if necessary. Whether this is possible in principle depends on the type and structure of the called transaction, may be release-dependent and cannot be influenced. In addition it is to be considered that parallel transactions (several windows) can affect the condition of the user parameters unpredictably. The use of importing parameters should only be used if it can be ensured that the parameters always have the expected state.

...

Note

Calling in a new window and retrieving parameters or waiting for the end of the updater are not compatible and may lead to an error.

Examples:

Navigation to the CV03N for a document to be displayed.

Parameter

Value

TRANSACTION_CODE

CV03N

SKIP_FIRST_SCREEN

X

KEY_TYPE_NAME

DMS_DOC_KEY

CV1

<OBJECT_KEY>-DOKNR

CV2

<OBJECT_KEY>-DOKAR

CV3

<OBJECT_KEY>-DOKVR

CV4

<OBJECT_KEY>-DOKTL


Navigation to document creation with template into CV01N

Parameter

Wert

TRANSACTION_CODE

CV01N

SKIP_FIRST_SCREEN

X

KEY_TYPE_NAME

DMS_DOC_KEY

E:CV1

<KEY_DATA>-DOKNR

E:CV2

<REF_OBJECT_KEY>-DOKAR

E:CV3

<KEY_DATA>-DOKVR

E:CV4

<REF_OBJECT_KEY>-DOKTL

E:CV7

<REF_OBJECT_KEY>-DOKNR

E:CV8

<REF_OBJECT_KEY>-DOKTL

E:CV9

<REF_OBJECT_KEY>-DOKVR

I:CV1

<OBJECT_KEY>-DOKNR

I:CV2

<OBJECT_KEY>-DOKAR

I:CV3

<OBJECT_KEY>-DOKVR

I:CV4

<OBJECT_KEY>-DOKTL