Question:
... this seems to be more a PM issue than a QM issue. Hope somebody here can help me
Hi all,
During results recording (QE17) defects are recorded, and automatically a PM notification is generated (IW21).
In this PM notification, the short text is not filled, and neither is the start date and time.
Is it possible to have values from the result recording taken over in these fields. Is this customising or is there a user-exit to perform this (it seems that enhancements QQMA0007 and QQMA0025 are not called in the QM-PM link).
I'm an ABAP guy with minor QM-PM knowledge, but all the consultants who configured this, are gone since the project is live
I hope somebody here can help. We are on 46C
Txs!
Answer:
Frank,
Have a look at user-exit QQMA0025 (Default values when adding a notification) via TCode SMOD
You could also consider automatic task determination
_________________
Sponsored partner: www.arch.co.uk
PM/CS FAQ
Search SAPFans
Answer:
Hi PJA,
Thanks a lot for your tips.
As I mentionned in my first posting, I already tried enhancements QQMA0007 and QQMA0025. Are you sure that QQMA0025, which you suggest, normally is called during the QM-PM link. If so, I must try to find out why my coding isn't working.
The automatic task determination. Is that something I must search for in QM, or in PM.
THX, Frank
Answer:
Hi PJA,
Thanks a lot for your tips.
As I mentionned in my first posting, I already tried enhancements QQMA0007 and QQMA0025. Are you sure that QQMA0025, which you suggest, normally is called during the QM-PM link. If so, I must try to find out why my coding isn't working.
The automatic task determination. Is that something I must search for in QM, or in PM.
THX, Frank
Answer:
Hi PJA,
Thanks a lot for your tips.
As I mentionned in my first posting, I already tried enhancements QQMA0007 and QQMA0025. Are you sure that QQMA0025, which you suggest, normally is called during the QM-PM link. If so, I must try to find out why my coding isn't working.
The automatic task determination. Is that something I must search for in QM, or in PM.
THX, Frank
Answer:
Frank,
QQMA0025 will work if you use PM/CS Notifications (not QM Notificatios)
The equivilent QM user-exit is QQMA0007 (QM: Default Values when Creating a Notification)
_________________
Sponsored partner: www.arch.co.uk
PM/CS FAQ
Search SAPFans
Answer:
Hi PeteA,
I believe that I am generation PM notifications, but from within a QM transaction.
But as mentioned, both enhancements (QQMA0007 and QQMA0025) seems not to be working when I automatically generate this notification through defect reporting in a calibration in QM (transaction QE17).
If I create a PM notification with the same notification type (NA - deviation) through transaction IW21, I indeed come in this enhancement, but I need it specifically for the QM-PM scenario described above.
But in your opinion, the enhancement should work also for this scenario? Could it have something to do with configuration that this is not the case in our system?
Thanks for your time.
Regards, Frank
Answer:
Frank,
If you read the documentation for QQMA0025 (TCode SMOD), you will see that the user-exit is not shown displayed if the notification is created in the background (which is the case for QM-PM integration).
However, it should still work.
Can you cut-and-paste your ABAP code into this message
_________________
Sponsored partner: www.arch.co.uk
PM/CS FAQ
Search SAPFans
Answer:
EXIT_SAPLIQS0_017
*--- Move VIQMEL to exporting parameter E_VIQMEL
MOVE I_VIQMEL TO E_VIQMEL.
INCLUDE ZXWOCU21.
... and ZXWOCU21
*----------------------------------------------------------------------*
* INCLUDE ZXWOCU21 *
*----------------------------------------------------------------------*
E_VIQMEL-QMTXT = 'Test user exit'.
E_VIQMEL-STRMN = syst-datum.
E_VIQMEL-STRUR = syst-uzeit.
This works when generating a PM notification with IW21, but not when the notification is generated automatically from within QE17.
Regards, Frank
Answer:
Hi PeteA,
Does the code did ring any bell?
I debugged the transaction, and did not encouter this user-exit.
Could it be that there is some customising related with this?
Txs, Frank
Answer:
Frank,
Without testing it myself, I don't know....
Try opening an OSS Message to SAP and see what they have to say.
_________________
Sponsored partner: www.arch.co.uk
PM/CS FAQ
Search SAPFans
Answer:
We have the same issues as you have and we did not find any solution at all with the user exits mentioned up till now.
Our conclusion is that this part of the PM/QM interface is not developed at all.
What we did in the end is creating a job triggered program that selected al notifications resulting from Result recording and then using the user exits available to put in the data we required.
This is not a very nice solution but the best we could think of. In general, this integration area PM/QM is not calling upon any of the user exits at all.
We also found problems with the catalog type for problems which need to be 9 when you generate notifcations from results recording. This is hard coded in SAP QM and no user exits to help you out here. Eventually we migrated all of our codes within our old PM problem catalog type to the standard QM defect type 9.
Summarised : SAP has still some development to do in this area
Answer:
Hi QMMM.
Txs for the confirmation.
I am also consulting SAP OSS, but besides a sommation of inadequate QM and PM enhancement, nothing came out so far.
The reason why we want to avoid the change of the PM notification after creation is that some workflows are running on the notification create event. This would mean that I also have to alter the triggering events for these
Our main problem is with the field "required start date" VIQMEL-STRMN, which (in our system) is a mandatory field which is not filled by the QM-PM link. If there should be a way to have this field filled, or set to optional, this would also be a major step forward.
I must say that in customising, in "Set Field Selection for Notifications / Field Selection for Maintenance Notifications", the Required start date is a input field, not a required field, so I am wondering why it is required in IW21 .
Regards, Frank
Answer:
Regarding my comment: "... "Set Field Selection for Notifications / Field Selection for Maintenance Notifications", the Required start date is a input field, not a required field... " I overlooked that the influencing factor for notification type putted this field to mandatory. My mistake.