Quantcast
Channel: SCN: Message List
Viewing all articles
Browse latest Browse all 8581

Re: Dinamic notification type determination

$
0
0

Hello Manuel,

 

  • Amol 's  Z-table proposal in his first post may not be very relevant to your requirement, but the exit figured in the same post can help your issue resolved. His second post takes you to the nearsolution.
  • You have to use user-exit IWO10009 (alternatively BAdi WORKORDER_UPDATE)., where you will write Notification creating code according to your Plant and Type conditions.
  • You need not have a Ztable for Plant and Notification type if they are few. Hard-coding would suffice.
  • Better opt for Batch input lines (BDC method) for Notification creating in the exit using  CALL TRANSACTION 'IW21'.  in the end.
  • Alternatively you can use these FMs in sequence for Notification creation.
    • BAPI_ALM_NOTIF_CREATE
    • BAPI_ALM_NOTIF_SAVE
    • BAPI_TRANSACTION_COMMIT
  • Yours is not a difficult task.
  • My providing code will not be relevant because of the several Notification fields involved which you only know.
  • Please note that this proposal needs removal of all Notification Order integration settings in customization.
  • So, show this to your ABAPer who might then be able to start coding for you in the include ZXWOCU07 of the exit mentioned above.
  • Last but not the least, it is important to know the end result. When Order is created ( Coding should start based on IF condition for tcode IW31), a Notification of type depending upon the plant would be created at the SAVE event of the Order. MEans both Order and Notification will be created together.
  • Whether you use this exit or a BAdi mentioned above, the coding guidelines and efforts will be same.
  • You'd come to know other things which I could not list while testing the code.

 

 

Good luck

KJogeswaraRao


Viewing all articles
Browse latest Browse all 8581

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>