Versions Compared

Old Version 1

changes.mady.by.user SNP

Saved on

compared with

New Version Current

changes.mady.by.user Marian Vidra

Saved on

Key

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

...

  1. Directly via SNP Validate report test variant: Type the name of the mapping (use F4 search help to display existing mapping) in the report test variant and double-click on the name. A new popup window with the mapping editor will be displayed.

    Image RemovedImage Added

  2. Call transaction /DVD/VAL_REP_MAP: Choose a mapping on the selection screen (use F4 search help to display existing mapping) and execute. The mapping editor will be displayed.

...

  • Mapping ID [MAP_ID(integer)]: Unique key of each mapping statement. The Mapping ID also represents an order of applying the mapping on the report output. The order can be changed by drag&drop within the report name, image type, variant ID, Test case, and test plan names. The ID is automatically re-calculated after saving any performed changes.

  • Report Name [REPORTNM(40)]: Used to set dependency of mapping statement on the report name. If it is empty then the mapping statement can be applied to any report output.

  • Image Type [IMG_TYPE(1)]: Used to set dependency of mapping statement on image type. If it is empty then the mapping statement is applied to the before and after image.

  • Mapping Function [MAP_FUNC(10)]: Name of mapping specific function which will be applied on each line of report output. The application depends also on function parameters in the mapping statement.

  • 1st Parameter of Mapping Function [FUNC_PARAM1(string)]: The meaning of the first parameter is function-specific.

  • 2nd Parameter of Mapping Function [FUNC_PARAM2(string)]: The meaning of the second parameter is function-specific.

...

  • Changed At [CHANGED_AT(timestamp)]: Contains the date and time when the mapping statement was changed.

  • Changed By User [CHANGED_BY(12)]: Contains the user name who changed the mapping statement.

  • Created At [CREATED_AT(timestamp)]: Contains the date and time when the mapping statement was created.

  • Created By User [CREATED_BY(12)]: Contains the user name who created the mapping statement.

...

  • Report Test Variant ID [VARIANT_ID(13)]: Used to set dependency of mapping statement on SNP Validate report test variant ID.

  • Report Test Run ID [RUNID(10)]: Used to set dependency of mapping statement on SNP Validate test Run ID.

  • Test Plan Technical Name [PL_TECHNAME(20)]: Used to set dependency of mapping statement on SNP Validate test plan name.

  • Report Test Case Technical Name [TC_TECHNAME(20)]: Used to set dependency of mapping statement on SNP Validate test case name.

Reserved columns (internal usage):

  • Software Component [COMPONENT(30)]: Used to set dependency of mapping statement on SAP software component. The mapping statement is only applied if a software component exists on the system.

  • Software Component Release [COMP_RELEASE(10)]: Used to set dependency of mapping statement on SAP software component release. The mapping statement is only applied if a software component exists on the system in this release. If the value in the software component is not set then this dependency is ignored.

  • Software Component Support Package Level [COMP_SP_LEVEL(4)]: Used to set dependency of mapping statement on SAP software component SP level. The mapping statement is only applied if a software component exists on the system with this SP level. If the value in the software component is not set then this dependency is ignored.

...