cancel
Showing results for 
Search instead for 
Did you mean: 

QM- IDI download data QIRF_SEND_INSP_DATA_FOR_WL2

antonio_rodriguez9
Participant
0 Kudos

Hello.

we use this function QIRF_SEND_INSP_DATA_FOR_WL2 to download data from sap to external system. And it seems to works fine, output table are filled, but we don't see  table qiwl update status and also status from inspection lot doesn't change, in this case, i think that i will see how change status from MSUB to SUB, but i don't anythin.

i call functionQIRF_SEND_INSP_DATA_FOR_WL2  with this values...  and also i call ( from external system) QIRF_SEND_COMMIT_TO_QM

I_IND_EVALUATE_CHARACTERISTIC   X

I_IND_MULTI_TRANSFER_POSSIBLE   X

I_IND_ONLY_OBLIGATORY_CHARACT

I_IND_READ_PURCHASING_INFO

I_IND_READ_SALES_INFO

I_IND_READ_VENDOR_AND_PRODUCER

I_IND_READ_WORK_CENTER          X

I_IND_SEND_PROTOCOL_MAIL

I_IND_SET_BLOCK_INDICATORS          X

I_IND_SORT_ASCENDING_TO_DATE    X

I_IND_SORT_DESCENDING_TO_DATE

I_IND_TRANSFER_CHAR_CODES           X

I_IND_TRANSFER_USAGE_DEC_CODES X

I_QAILS

SATZART

LOSNR_VON                      040000012101

LOSNR_BIS                      000000000000

PLNFL                          0

VORNR_VON                      0020

VORNR_BIS

VORGWERK

SUBSYS                         Y00001

regards.

antonio

Accepted Solutions (0)

Answers (2)

Answers (2)

former_member42743
Active Contributor
0 Kudos

It's been years since I worked with the QIWL table but if I remember correctly, it is your responsibility to update the table via your interface programs.

Maybe using QIRF_NOTIFY_FUNCTION?  

Check this page.

http://help.sap.com/saphelp_470/helpdata/en/26/b439e4506511d182c20000e829fbfe/content.htm

FF

Former Member
0 Kudos

Yes, you are right.

It is the responsibility of the subsystem to send this commit. SAP provides the function module QIRF_SEND_COMMIT_TO_QM for this activity.

This function module is called by the subsystem after having downloaded the relevant data (inspection lots, operations, characteristics), as described in the documentation from SAP.

But: This commit does not work.

The update of the QIWL is not done.

The function module you mentioned above (QIRF_NOTIFY_FUNCTION) is somthing else but does not help here, as far as I can see it.

regards

Roland

former_member42743
Active Contributor
0 Kudos

Does this help at all?

http://www.sapfans.com/forums/viewtopic.php?f=27&t=365703

This is an older PDF on the interface. I don't know if it will shed any light or not.

http://www.winlims.info/images/2/26/Qm_idi_30.pdf

Have you done an OSS note search yet on the commit RFC?

Note 327635 is an older note that might apply but not knowing the version you're working with I don't know.

FF

antonio_rodriguez9
Participant
0 Kudos

Hello.

you have to call function tow function

1.- QIRF_SEND_INSP_DATA_FOR_WL2

2.-QIRF_SEND_COMMIT_TO_QM

from external systemm in the same saplogon conection..

Regards

Former Member
0 Kudos

Hi Guys,

it works!

Essential was to call the 2 functions within one session. This was not so easy to find out (SAP .net is used)

In SE37 this can be simulated by creating a test sequence.

Roland

former_member42743
Active Contributor
0 Kudos

Thanks Roland for the update.  Since you tagged onto an old unclosed note, and since their are obvious nuances associated with doing this, maybe you would consider writing up the steps for this along with some example coding into a document and posting it to the QM space.

Thanks,

Craig

Former Member
0 Kudos

Hi Antonio,

sorry - but I have no answer - I have exactly the same issue.

I use the QIRF_SEND_INSP_DATA_FOR_WL2, the download works. Then I run the QIRF_SEND_COMMIT_TO_QM but nothing happens. The QIWL is not updated and also not the status in the lot and in the charcteristics.

Do you now have a solution for this issue? (You posted it almost 1 year ago)

regards

Roland