be-team services | Matthias Köper

Implementing Z_CTS_CROSS_REF manually


— English only —

If you experience trouble using ZSAPLINK, or are not able to use it for any other reason, you may follow these steps:
  1. Create empty report Z_CTS_CROSS_REF using transaction SE80 or SE38
  2. Upload Z_CTS_CROSS_REF source into the newly created report
  3. Add new GUI status MAIN, 
    1. use “Extras – Adjust Template”
    2. select “List template”.
    3. add buttons to application toolbar as shown in screenshot (ALLOBJECTS, TRANSPORT, VERSIO, SORTLIST, SORTASC, SORTDESC)

    image: https://www.be-team.org/wp-content/uploads/2011/10/0_Users_mkoeper_Desktop_Bildschirmfoto_2011-10-18_um_09_12_12.jpg

    Settings for function ALLOBJECTS:

    image: https://www.be-team.org/wp-content/uploads/2011/10/1_Users_mkoeper_Desktop_Bildschirmfoto_2011-10-18_um_09_13_27.png
  4. Add new GUI status STANDARD_FULLSCREEEN by copying it from function group SLVC_FULLSCREEN to Z_CTS_CROSS_REF 
    1. add the same buttons as for status MAIN
  5. Maintain texts 
    1. Paramters not named explicitly should be set as referring to data dictionary…
      Parameter
      Short text
      P_ALV
      Show as ALV table
      P_DEV
      Development SysID
      P_EXPHIS
      Export history
      P_GENKEY
      only req. with generic key(s)
      P_HASKEY
      only req. with key(s)
      P_IMPHIS
      Import history
      P_MISSON
      Misses on system XXX
      P_PRD
      Production SysID
      P_QUA
      Quality Assurance SysID
      P_TRA
      Training SysID
      P_TRFUNC
      Category of transport request
      P_XPRA
      only req. w. method execution

Beitrag veröffentlicht

in

,

von

mkoeper

Schlagwörter: