Action log in QM02 does not record changes

[Former Member]

Hi,

I have a requirement to link the QNs. Let's say there are 2 QNs, a child QN and a parent one. When completing the child QN, changes in the child QN will be updated in the parent QN.

I've used some BAPIs and FMs to update the data from the child QN to its parent, and the data in parent QN of QM02 has been updated sucessfully. But the action log in the parent does not show the updated data. I think I may miss some flags or data so that the changes can be displayed in the ALV of the aciton log.

Do you have any suggestions ?

Thanks,

Paul

[Former Member]

Hi,

I have a requirement to link the QNs. Let's say there are 2 QNs, a child QN and a parent one. When completing the child QN, changes in the child QN will be updated in the parent QN.

I've used some BAPIs and FMs to update the data from the child QN to its parent, and the data in parent QN of QM02 has been updated sucessfully. But the action log in the parent does not show the updated data. I think I may miss some flags or data so that the changes can be displayed in the ALV of the aciton log.

Do you have any suggestions ?

Thanks,

Paul

[RaymondGiuseppi]

I've used some BAPIs and FMs to update the data from the child QN to its parent,

I am confident enough to BAPIs, but what FM did you use?

Regards,

Raymond

[Former Member]

Hi Raymond,

I use the FM 'IQS4_ADD_DATA_NOTIFICATION'. This works well. It updates data from the child QN to its parent. I have not tried all the parameters of this FM, hence I wonder whether that is the cause for the issue that changes are not recorded in the action log of the parent QN.

Thanks,

Paul

[RaymondGiuseppi]

Did you call in sequence

- ENQUEUE_EIQMEL

- IQS4_GET_NOTIFICATION

- IQS4_ADD_DATA_NOTIFICATION

- IQS4_CHECK_ERROR_SEVERE (or loop at RETURN)

- DEQUEUE_EIQMEL (if error)

Regards,

Raymond

[Former Member]

Hi Raymond,

I've tried to lock and unlock the QN before and after calling the FM 'IQS4_ADD_DATA_NOTIFICATION', but the changes are still not recorded in the action log.

There are dozens of parameters that I may miss during the FM calling, hence that's why the changes are not recorded. But I could not find the right way to 'inform' the system to record the changes.

I'm thinking of a way to use BDC. By this way, surely the changes willl be recorded like the way we enter QM02, making changes and saving the QN. But with this way, I also have to deal with dozen of BDC's parameters.

Thanks,

Paul

[nabheetscn]

Put a break point in add notification function module and perform the step directly on SAP standard screen. It stop at this point if SAP standard is using this FM and you can note down the parameters

Nabheet

[Former Member]

Hi Nabheet,

Thanks for your suggestion. However, I don't have an opportunity to 'watch' the way the standard code uses the FM 'IQS4_ADD_DATA_NOTIFICATION' or the BAPI 'BAPI_QUALNOT_ADD_DATA', simply because standard SAP does not call these FM and BAPI when we are completing a QN.

After looking at the standard codes for a while, I think that only changes in the screens will be recorded and kept in the action log. The system compares the current status of the fields in the screens with those in the buffer, which are buffered after the very first time users get in. Those changes will be recorded and shown in the action log. In my case, when completing a child QN, we have to implement an enhancement to update the data for the parent QN, update it with the child QN's cause code, activity, task etc.. There are no changes in the screens of the parent QN in our case, that's why I think the FMs and BAPIs I've tried do not help.

The last way seems to be the usage of BDC, but I will have to rebuild the enhancement to update data for the parent QN from the first step (OMG).

Thank you a lot for your suggestions.

paul

[Former Member]

Problem solved