×

[PR]この広告は3ヶ月以上更新がないため表示されています。
ホームページを更新後24時間以内に表示されなくなります。




Sapass

 Simplify SAP R/3 development with Excel VBA/VB RFC  
Home> UserExit>QQMA0010



Index

QQMA0010

Customer Exits QM/PM Notifications
Use

With this customer enhancement, you can include additional data on the CAUSE detail screen for notification cause (screen SAPMLIQS0 7116).
For this purpose, the data for the notification header, item and cause data are transferred to the function group via the user exit. You can then include this data on the customer-specific subscreen.

It is possible to change the data. Make sure the structure VIQMUR is transferred to the export structure E_VIQMUR before you leave the user exit. Only then will the unchanged fields be transferred back properly.

Note

If field TQ80-USERSCR3 (maintained in Customizing) contains a screen number, this screen is called up as a subscreen. Otherwise, screen 0100 is used.
It is important that the screens for program SAPLXQQM are defined.

If you want to add your own fields to the view VIQMUR, you must include them in table QMUR as an APPEND structure. In this way, the additional fields are automatically copied into view VIQMUR.


Function/Program:
  • EXIT_SAPMIWO0_013: Customer Exit: Transfer Cause to User Screen
  • EXIT_SAPMIWO0_014: Customer Exit: Transfer Cause from User Screen
  • SAPLIQS07116_USER0003_SAPLXQQM0100: Cause Detail
  • SAPLIQS07116_USER0003_SAPLXQQM0310: Cause Detail
  • SAPLIQS07116_USER0003_SAPLXQQM0311: Cause Detail
  • SAPLIQS07116_USER0003_SAPLXQQM0312: Cause Detail
  • SAPLIQS07116_USER0003_SAPLXQQM0313: Cause Detail
  • SAPLIQS07116_USER0003_SAPLXQQM0314: Cause Detail
  • SAPLIQS07116_USER0003_SAPLXQQM0315: Cause Detail
  • SAPLIQS07116_USER0003_SAPLXQQM0320: Cause Detail
  • SAPLIQS07116_USER0003_SAPLXQQM0321: Cause Detail
  • SAPLIQS07116_USER0003_SAPLXQQM0322: Cause Detail
  • SAPLIQS07116_USER0003_SAPLXQQM0323: Cause Detail
  • SAPLIQS07116_USER0003_SAPLXQQM0324: Cause Detail
  • SAPLIQS07116_USER0003_SAPLXQQM0325: Cause Detail
  • SAPLIQS07116_USER0003_SAPLXQQM0330: Cause Detail
  • SAPLIQS07116_USER0003_SAPLXQQM0331: Cause Detail
  • SAPLIQS07116_USER0003_SAPLXQQM0332: Cause Detail
  • SAPLIQS07116_USER0003_SAPLXQQM0333: Cause Detail
  • SAPLIQS07116_USER0003_SAPLXQQM0334: Cause Detail
  • SAPLIQS07116_USER0003_SAPLXQQM0335: Cause Detail

02-Oct-2005