Hi,

I'm trying to créate material master QM parameters for a semi-finished product but there's no some critical parametersat QM tab. The main problema is that i cannot see the inspection type parameters button. However for the same material in other plant, this button is displayed.

The QM plant dependent parameters are the same for both plants.

Thanks.

Regards.

OCS.

Hi,

I have one material which have Inspection Type 01 activated for the Inspection lot generate at GR Time.

we have done the GR for the Material and Batch combination and Inspection lot generate with qty 6240 Pcs on dated 04.02.2016 and Same day we have done 102 movement for this material and batch item.

Also i had checked in quality client, Normally for the GR Inspection lot, when we done 102 movement same time inspection lot is status changed from REL to LTCA But in this case Lot is available Open with REL status after 102 movement.

i had checked stock is not available in MMBE for this material and batch combination but inspection lot  showing open with Qty 6240 qty.

Inspection lot Showing in MD04 with Material & plant input with 6240 Pces qty and same issue facing.

Also, we are not able to cancel the inspection lot with QA02   function ---> cancel lot because it was in gray mode.

Also QM02 Special changes ---> Correct the actual qty from 6240 to 0 Pcsqty but error message "LO Stock in quality control doesn’t reached in 6240 PEç" 

we go to transaction MD04 is visible the quantity of 6240 PEÇ and the purchases area doesn’t buy this material because is visible the quantity in stock. What kind of procedure can we perform so that this stock appears in quantity 0 in MD04?

please provide your inputs

My current configuration for notification creation is one notification for one Lot . When ever the spec is out of the tolerance limit a defect needs to be logged an  auto notification for an inspection lot is created . When I went back to the same result and update the result to good  then defect needs to be removed and the notification needs to be marked and completed and Deleted (NOCO DLFL) .

In the same inspection point when ever there is a another Bad result then it should reopen the same notification and add the defects in to the same notification which is not happening now .

I looked into the configuration but I didn't find any clue.I am not sure is there any enhancement that is stopping this to happen. Can anyone help me where I need to start  looking at for this issue ? .

Thanks & Regards
Suman

Hi,

I want to change UD after long term inspection result recording.

But it will give status check error - LTIN.

Please guide in this.

Regards,

KA

Two questions here. Both of them aim to prevent shipments on a material with an open quality notification.

1. Is it possible to prevent a shipment in the system due to an open quality notification?

If so, details will on how to set it up will be greatly appreciated.

2. Is it possible to prevent a 101 and or a 261 movement type with an open QN.

Essentially, what is the best practice to ensure defective materials do not ship? All your input and responses will be greatly appreciated.

Thanks

Hi Experts,

I'm using QIRF_GET_DEFECT_ITEMS2  bapi to record defects. But when the bapi is executing it give below errors.

Below is the code.

LOOP AT it_defects_display into wa_defects_display.
             clear: wa_defects,wa_qmife,wa_location.

             read table it_location into wa_location with key kurztextcd = wa_defects_display-kurztextcd.

             if wa_inspection_points is not initial.
               wa_qmife-satzart = 'Q95'.
             else.
               wa_qmife-satzart = 'Q91'.
             endif.

             wa_qmife-prueflos = wa_yarn-prueflos.
             wa_qmife-vornr = zst_ny_qm_operations-inspoper.

             read table it_defects into wa_defects with key code = wa_defects_display-code.
             wa_qmife-fegrp = wa_defects-codegruppe.
             wa_qmife-fecod = wa_defects_display-code.
             wa_qmife-fekat = wa_defects-katalogart.
             wa_qmife-anzfehler = wa_defects_display-noofdefect.

             CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
               EXPORTING
                 INPUT  = v_posnr
               IMPORTING
                 OUTPUT = wa_qmife-posnr.

             wa_qmife-otkat = wa_location-katalogart.
             wa_qmife-otgrp = wa_location-codegruppe.
             wa_qmife-oteil = wa_location-code.

             APPEND wa_qmife to it_qmife.
             v_posnr = v_posnr + 1.
           ENDLOOP.

Is anything i'm doing wrong? Pls. help

Dear QM-experts!

I have issue with WMS-SAP integration. In our bussines process when stock is blocked in WMS, Q-notification have to be created in SAP, but I can't find suitable IDoc. Is there any IDoc for Q-notif. creation?

How to  default (tick mark) the "Documentation required indicator" in QM view of material master?  MARC-KZDKZ  (Documentation reqd)

Dear All,

I have inspection lot with inspection type 04 and user has to do RR.

Inspection lot have Operation 0010, 0020, 0030, 0040 and 0050.

for the Operation 0030 user has done changes 18 times RR for the Char and duplicate entries are found in table QASE with Combination Inspection lot number, Node, Char and Resultno screen shot attched.

When user run the TCode QE51N & QE03 for operation 0030 that ABAP Run time error come and not able to Lock the Results.

please help. also provide if any sap note available.

ABAP Run time error also attached.

thanks in advance.

Inspection lot is not transferred from SAP to LIMS

In table QIWL the transfer status is no transfer yet performed???

Can anyone tell where the error lies..and what are the t.codes we can use to find the error???

Dear QM experts,

Can we create inspection lot and assign reference operation set to this inspection lot.

The link between material and reference operation set is already maintained, but i'm not able to select inspection created through qp11 in my inspection lot (error message QA233)

Please advise.

Thanks

Hi

I could see there are Quality stock which generated in 2005.These stock generated from process order goods reciept -inspection type 04. I need to clear out these stock.But I am getting error in QA32 while Usage decision as Order xxxx doesnt exist. We archived this process order and system doesn't have process order information. How I can remove quality stock from the system in this situation?

I tried for below movement types but I am getting error as Change the inspection stock of material xxxx in QM only

555-Withdrawal for scrapping from blocked stock

551- Withdrawal for scrapping

321-TF quality to unrestricted

Please suggest is there any program or any transaction such that i can remove the quality stock from the system.

Regards,

Uday

Hi,Gurus,

I want to create one inspection lot for one material with serial number when create inspection lot manually? My question is I cant add the serial number ,can anyone tell me ?Many thanks!

Many thanks!

BR

Mishuang Zhao

Hi All,

Can you please explain me the difference between Inspection lot node and Inspection plan node. Also let me know where this value is maintained.

I can see those values in AFVC table.

Inspection lot node : AFVC-APLZL

Inspection plan node : AFVC-PLNKN

Thanks,

Deepak.N

Hi QM Experts,

While changing the Delivery date in PO, i received said error " Quality inspection is Required for this Material "

Purchase order created back dated  23.01.2016

Material Activated with QM ( mm02 ) 02.03.2016

Please advise how to overcome this issue.

Dear Friends ,

i am trying to configure for Quality Certificate. I have made all the neceesary master data and customization settings.

During testing at the tim eof delivery , i am able to see , LQCB in header output , but when i am trying to view the certificate ,

i am getting the message Certificate profile not found eventhough i have maintained.

. i have created certificate proflile via transaction QC01.

Certificate profile assignment   Via trannsaction QC15.

Output condition record via transaction  ..vv21

Please let me know what may be the issue.

Thnaks in advance for your solutions!!!!

Hi Everyone

We created a material document with movement type 101 and inspection lot is created . In first inspection lot item is rejected, so the item is return to the vendor with movement type 122. Again item is received and did subsequent delivery with movement type 101, so the inspection lot is created .This time item is approved.

So we created a MIRO invoice there payment is blocked because of Quality block. In material master QM control key is maintained with Z*** - Block Invoice.

Kindly let me know how to remove the block and also why there is a block even after accepting the item . If i use normal goods receipt second time, this error is not coming. This error occurs only when we use subsequent delivery

Regards

Raghu Prasad N

Hi Friends,

I have one critical issue, where in for particular Quality notification type (R3),the number sequence has not been following,

Eg ; Notification 300001179 was created manually through QM01 after 300001175, then notification 300001176 was created and similarly

...1177,...1178,but then again notification 300001179,hence the notification is overwritten and this should not happen.

could you please suggest how to rectify the issue ( i need to raise OSS note or any relevant SAP notes needs to be applied)

and this has been occurring in Production system only and in Development and Quality we are not finding any issues.

please guide me.

Thanks in advance.

Regards,

Srinika.

Dear experts,

Please i would like to auto select reference operation set for delivery inspection (category 10). In fact, as we know, the inspection lot generated for this type of inspection contains sales order number/item, delivery number/item.

Delivery inspection is performed based on reference operation set (qp11). SAP allows to assign material, sales document number and item in QP11.

After some customization, i've been able to select reference operation set (routing type S) in the inspection lot, but only without document sales assigned.

In the below example, we have the material LINGOT-QM-KS05S. This material had two assignment, 1st one without sales document, 2nd one (yellow) with sales document.

At the creation of inspection lot for delivery for sales order, SAP picks the 1st assigned, i.e without sales document. And when i delete this assignment, SAP can't find any reference operation set for this material.

Can you please help me to achieve auto selection of reference operation set based on sales document?

Thanks a lot.

ALE Settings for Quality Management

1 Basic ALE Settings

1.1 Define Logical System

Run Transaction SALE in Development environment.

Follow menu path IDoc Interface / Application Link Enabling (ALE) >> Basic Settings >> Logical Systems >> Define Logical System.

It is a cross client configuration.

Click on New Entry

Enter Logical System as following naming convention

SYSCLNTXXX

Here,

SYS – System name e.g. DEV- Development, QLT-Quality, PRD-Production

CLNT – Client (keep the text CLNT as it is)

XXX – Number of Client e.g. 101, 102, 103 etc.

Now, Save. It will ask for transport request. Create/assign the transport request and get this transport request transported to all the required environments. This is required activity because it will be used while creating Partner Profile. If don’t perform this activity, system will not allow you to create partner profile with logical system with this naming.

1.2 Create RFC Connection:

Run Transaction SM59 – Configuration of RFC connections

Or follow the menu path

Select ABAP Connections and click on Create

Enter the RFC Destination, Description, Target Host and instance number. System will pick the IP address automatically.

RFC destination as per following naming convention (as per logical system)

SYSCLNTXXX

Here,

SYS – System name e.g. DEV- Development, QLT-Quality, PRD-Production

CLNT – Client (keep the text CLNT as it is)

XXX – Number of Client e.g. 101, 102, 103 etc.

In Logon and Security Tab, Maintain the Logon Procedure, put destination client, User (ALEUser) and Password. And Save.

This is the procedure to create RFC Connection. You need to perform this activity in both the Sending and Receiving System. E.g. in Development Server you need to maintain Quality Server’s RFC and in Quality Server you need to maintain Development Server’s RFC.

1.3 Port Maintenance

Run the transaction WE21

Or follow the menu path

Select Port Type Transactional RFC and click on Create

Select the radio button for own port name and enter port as following naming convention (Same as logical system) on the pop up dialog box.

SYSCLNTXXX

Here,

SYS – System name e.g. DEV- Development, QLT-Quality, PRD-Production

CLNT – Client (keep the text CLNT as it is)

XXX – Number of Client e.g. 101, 102, 103 etc.

Enter the description and select the RFC destination

Now, Save.

1.4 Create Partner Profiles

Run the transaction code WE20

Or follow the menu path

Select the Partner type LS and Click on create

If you do not enter the logical system defined in step 1 then you will be facing following error

Enter the Partner number as per the logical system naming convention

SYSCLNTXXX

Here,

SYS – System name e.g. DEV- Development, QLT-Quality, PRD-Production

CLNT – Client (keep the text CLNT as it is)

XXX – Number of Client e.g. 101, 102, 103 etc.

Enter Type as US – User, Agent as user ID.

Now, Save.

The Partner profile is created. You can create Partner profile in each system as follows

2 Message Types Settings for Quality Management

There are following standard message types available in SAP for Quality Management Master Data.

2.1 Code Groups (Message Type QPGR)

We have to following to manage ALE for message type QPGR

Outbound parameter in development server for QLTCLNT201

Inbound parameter in Quality server for DEVCLNT101.

2.1.1 Set outbound parameter in development server for QLTCLNT201

Now, login to development server

In Transaction WE20 (Partner Profiles) select the required partner profile (e.g. QLTCLNT201 Quality Client 201) under the Logical system.

Click on create outbound parameter

In the next screen enter message type QPGR, Select Transfer IDOC immediately. Enter basic type QPGR01. And press enter.

After Enter

Now, Save. E.g. in development client you have set outbound parameter for QLTCLNT201.

2.1.2 Set inbound parameter in Quality server for DEVCLNT201

Now, login to Quality System to set inbound parameter.

Scroll down and click on create inbound parameter

Enter Message Type QPGR and Process Code BAPI and select Trigger immediately option.

Now, Save.

2.1.3 Send Code Group

Now, you can send the code groups using QL41 (Send Code Group) from Development server to Quality Server.

2.2 Master Inspection Characteristics (Message Type QPMK)

We have to following to manage ALE for message type QPMK

Outbound parameter in development server for QLTCLNT201

Inbound parameter in Quality server for DEVCLNT101.

2.2.1 Set outbound parameter in development server for QLTCLNT201

Maintain outbound parameter as below screenshot

2.2.2 Set inbound parameter in Quality server for DEVCLNT201

Maintain inbound parameter as below screenshot

2.2.3 Send Master Inspection Characteristics

Now, you can send the code groups using QL21 (Send Master Inspection Characteristics) from Development server to Quality Server.

2.3 Inspection Methods (Message Type QSMT)

We have to following to manage ALE for message type QSMT

Outbound parameter in development server for QLTCLNT201

Inbound parameter in Quality server for DEVCLNT101.

2.3.1 Set outbound parameter in development server for QLTCLNT201

Maintain outbound parameter as below screenshot

2.3.2 Set inbound parameter in Quality server for DEVCLNT201

Maintain inbound parameter as below screenshot

2.3.3 Send Inspection Methods

Now, you can send the code groups using QL31 (Send Inspection Methods) from Development server to Quality Server.

2.4 Material Inspection Setup (Message Type MATQM)

We have to following to manage ALE for message type MATQM

Outbound parameter in development server for QLTCLNT201

Inbound parameter in Quality server for DEVCLNT101.

2.4.1 Set outbound parameter in development server for QLTCLNT201

Maintain outbound parameter as below screenshot

2.4.2 Set inbound parameter in Quality server for DEVCLNT201

Maintain inbound parameter as below screenshot

2.4.3 Send Inspection Setup

Now, you can send the code groups using QL11 (Send Inspection Setup) from Development server to Quality Server.

2.5 Inspection Plan (Message Type INSPECTIONPLAN_CREATE)

We have to following to manage ALE for message type INSPECTIONPLAN_CREATE

Outbound parameter in development server for QLTCLNT201

Inbound parameter in Quality server for DEVCLNT101.

2.5.1 Set outbound parameter in development server for QLTCLNT201

Maintain outbound parameter as below screenshot

2.5.2 Set inbound parameter in Quality server for DEVCLNT201

Maintain inbound parameter as below screenshot

2.5.3 Send Inspection Plan

There is no transaction code available for sending inspection plan.

But, there is an executable Program (RQ_PLAN_CREATE_SAMPLE_FILE) available in SAP. You can execute it using transaction SE38.

The Program has a limitation. The parameter ‘receiver’ (logical system) in the program is set as no display. So, when the user run the program, the user will not be able to define the destination logical system and when you execute the program without destination, the IDoc will get failed. As the IDoc doesn’t have the destination address. (see the below screenshot)

If you run the program in debugging mode (by putting break point), you will be able to change the parameter ‘receiver’ and IDoc will get processed successfully.

There are few alternatives to achieve sending of inspection plan with the help of Developer.

Option 1: The developer can enhance (implicit enhancement spot available to have additional screen parameters) the program and put an additional screen parameter (logical system) and then pass the value of the parameter to ‘receiver’. This will allow the user to define destination.

Option 2: The Developer can create a custom program with additional parameter and then call the standard program within the same with passing all the parameter.

Option 3: The Developer can copy the standard program into a custom program and have this parameter ‘receiver’ as display.