Inspection lot is not getting created in ECC

[venkatasasidhargupta_gada]

Hi All

Inspection document created in EWM is not able to create inspection lot in ECC. In the inspection document, it is identifiying external system and its business system properly. But seems to be communication is not happening properly. what should I check?

Thanks

Sasidhar Gupta

[venkatasasidhargupta_gada · Accepted solution]

Hi All

Sorry I have missed to put "not" in the title. However, finally I have achieved QIE and ERP QM integration. I can say configurations mentioned in SAP Help & EWM 100 and 120 helped me in this.

http://help.sap.com/saphelp_ewm91/helpdata/en/42/f9ebe8ed743ee3e10000000a1553f6/content.htm?frameset...

For the sake of community usage I wanted to put here, what I have missed and how I did trouble shooting.

Initially I thought that inspection lot is not getting created in ERP even after entering inspection type in inspection rule in EWM (/scwm/qrsetup). Since I was expecting a outbound qRFC message in SMQ1 or inspection lot# in inspection document or system log in EWM, I could not notice that inspection lot which was actually created in ECC. So, I had verified inspection document, HU contents and to me everything seems to be fine. In EWM monitor, inspection document displays external system and its business system name properly. In HU contents, inspection document# displayed correctly. Also, in EWM configs are fine. Later I have realized that inspection lot is getting created in ECC but it is not updated to EWM. So, I thought to go through all standard configurations to be done again. All seems to be fine except event type linkage in ERP and BADI "QPLEXT_COMM_TEC" implementation. After activating event type linkage I started noticing that a message sent from ERP to EWM QIE in system logs(SLG1 of ERP). But they are in error since BADI was failing to pick QRFC channel for EWM warehouse. After correcting the code, I could see next logs in green and now I can see inspection lot# in inspection document of EWM.

So, my understanding is, it is also worth to check system logs for further troubleshooting. In system logs, we will find logs in this sequence in both ERP and EWM put to-gether.

1. Created Inbound delivery - ERP

2. Distributed to EWM - ERP

3. Created/Activated IDN - EWM

4. Created/Activated ID - EWM (As per inspection rules, inspection doc will be created at this step)

5. Unloading completed - EWM

6. GR posted - EWM (inspection doc status will change from created to released at this step. Only at this stage QIE will inform ERP QM and releasing inspection document in EWM is required. Refer EWM 120.)

7. Inspection lot creation will be updated to EWM - ERP

8. Inspection lot creation confirmation in EWM - EWM

After this, I feel it could be better, if we have system log in EWM when QIE informs ERP QM with the inspection document#. So that we can at least understand EWM part is working fine.

Thanks

Sasidhar Gupta

[Former Member · Accepted solution]

Hi Sasi,

It's very useful posting, thanks for sharing.

Danny

[Former Member · Accepted solution]

Sasidhar,

Do you have any actual configuration document you can share with some examples. I have configured the system per your explanation in the forum.

My requirement is very basic. I want to implement basic incoming inspection with incoming quality certificates in procurement. So iam assuming I don't have to set up configuration for: samples and items, finding types and follow up actions?

Also if I want to create the equivalent to Inspection Plans in EWM , what am I supposed to consider. Iam thinking QGRP, PRODUCTID, UOM ?

Kindly let me know since I am new to this concept in QIE

Thanks

[venkatasasidhargupta_gada · Accepted solution]

Hi Anup

I have shared document in SCN. Please check.

Thanks

Sasidhar Gupta

[ankushkhatri8 · Accepted solution]

Hi Sasidhar,

As you have mentioned in your above comments "After correcting the code, I could see next logs in green and now I can see inspection lot# in inspection document of EWM."

I have integrated the ERP QM with EWM.

The inspection lots gets created in SAP ECC.

But after that the inspection lots are not getting transferred to EWM (may be bcoz of issues in the code for BADI).

Please find the application log in SAP ECC.

Could you please let me know the code for the BADI(changed code by you).

I have already copied the code from the sap note, but that is not working perfectly.

Regards,

Ankush

[Former Member · Accepted solution]

Hi Ankush,

From the screenshot I could see that you are using XI for QIE-QM integration, you need to set the communication technology to qRFC if warehouse is EWM. please make sure the BADI QPLEXT_COMM_TEC is implemented correctly in this case.

Regards

Danny

[ankushkhatri8 · Accepted solution]

Hi Danny,

Thanks for reply.

I have already implemented the BADI as shown below.

Yet, when the inspection lots are being transferred from ECC to EWM, the communication is taking place via XI.

It seems that code for the implementation need to be changed as it is not working.

Any idea what else would be missing?

Regards,

Ankush

[Former Member · Accepted solution]

Hi Anukush,

Without having a look at the codes, I cannot say anything missing in the BADI implementation.

Put a Break-point at the select statement and see if the correct value is passing.

Regards

Danny

[ankushkhatri8 · Accepted solution]

Hi Danny,

Please see the code below:-

method QPLEXT_COMM_TEC_IF~DETERMINE_TECHNOLOGY.

*Sets communication technology to qRFC in case of EWM

*Sample Implementation takes field LGNUM into account

*Further interesting fields e.g. LOG_SYSTEM

   type-pools ustyp.

   data lt_user_parameters    type ustyp_t_parameters.

   data ls_user_parameter     type ustyp_parameters.

   data: lv_decsy type /spe/decsy,

         lv_cust_typ type /spe/cust_typ,

         l_client_role type t000-cccategory,

         l_set_get type c,

         lv_lgnum type lgnum.

   constants: lc_ewm type /spe/decsy value 'E',

              lc_qrfc type qplext_comm_technology value 'Q'.

* Get Set/Get Parameter

   get parameter id '/SPE/CTRL_CUST_TYP' field lv_cust_typ.

   if sy-subrc = 0.

* Get the client role for the current system

     call function 'TR_SYS_PARAMS'

       importing

         system_client_role = l_client_role

       exceptions

         no_systemname      = 1

         no_systemtype      = 2

         others            = 3.

     if sy-subrc = 0 and l_client_role ne 'P'.

* exclude productive systems from Set/Get

       authority-check object 'S_DEVELOP'                    "#EC *

        id 'OBJTYPE' field 'DEBUG'

        id 'ACTVT' field '03'.

       if sy-subrc eq 0.

         l_set_get = 'X'.

       endif.

     endif.

   endif.

   if l_set_get is initial.

*CHeck SPM is active

     select single cust_typ from /spe/ctrl_sw into lv_cust_typ.

   endif.

   if lv_cust_typ na '13'.

     exit.

   endif.

*Check import parameter

   if ip_qals is initial.

     raise missing_import_parameter.

   endif.

   if ip_qals-lgnum is initial.

     select single lgnum from t320 into lv_lgnum

     where

         werks = ip_qals-werk

         and lgort = ip_qals-lagortvorg.

   else.

     lv_lgnum = ip_qals-lgnum.

   endif.

*CHECK warehouse number

   select single decsy from t340d into  lv_decsy

       where lgnum = lv_lgnum.

   if sy-subrc <> 0.

     raise invalid_import_parameter.

   endif.

*Check warehouse is EWM, set technology to qRFC in this case

   if lv_decsy eq lc_ewm.

     ep_comm_technology = lc_qrfc.

  endif.

   endmethod.

Regards,

Ankush

[Former Member · Accepted solution]

Hi Ankush,

Put a break point at the beginning of the following statements:

if ip_qals-lgnum is initial.

     select single lgnum from t320 into lv_lgnum

     where

         werks = ip_qals-werk

         and lgort = ip_qals-lagortvorg.

Check what value is passing to ip_qals-lgnum, if it is initial, ip_qals-lagortvorg will also be initial, in this case lv_lgnum will get nothing.

Regards

Danny

[ankushkhatri8 · Accepted solution]

Hi Danny,

Thanks for help.

There was not problem with code.

Actually "Enhancements for SPM" was not active.

Regards,

Ankush

[Former Member · Accepted solution]

Hello Sasidhar,

I have same issue : after inspection lot creation in ECC, the inspection lot is not updated in eWM inspection document. I activated event type linkage, but nothing happened.

Could you please share detailled actions done in event type linkage and QPLEXT_COMM_TEC ?

Thanks.

Dan BOURGEOIS

[former_member216529]

Many thanks !

BR

Miriam Zhao

[Former Member]

Thanks for sharing the information

Can you please suggest the details I need to mention in Even type linkage .

Cheers

Sam