Specifications dependent upon value against the characteristic in variant

[Former Member]

Hello All,

I need your help to map the below mentioned scenario.

We deal in materials which we manufacture based upon customer demand.

Customer specifies the requirement. For this we have opt variant configuration with pure MTO scenario.

We have created class characteristics against class type 'Variant'.

Now while punching the sales order, we are going to maintain the values against these characteristics for ex. flange width 20 mm.

I need these values to flow to inspection lot (inspection type 04) with lower and upper limit (based upon the tolerance limit agreed by customer). I have configured this but I am unable to get the limits as the values in the variant class are unique and not in range, I get the nique value only. Moreover the the tolerance limit is different for different customers.How to map this?

Mimiri

[tanuj_parikh · Accepted solution]

Hi,

Hope indicator 'Insp. By Configuration' in Inspection Type: 04 is activated.

Try Function Exit: EXIT_SAPLQMCF_001.

Regards,

[Former Member · Accepted solution]

Yep, it's marked.

May I know the purpose of this user exit also?

Mimiri

[tanuj_parikh · Accepted solution]

Hi,

It is for Loading values from material specification/ configuration.

What SAP information says is as follows:

Use

From Release 4.0A, you can use the enhancement EXIT_SAPLQMCF_001 to

adapt inspection specifications or configurations in the material

specification to your needs.

Calling the function module

The function module listed in this enhancement EXIT_SAPLQMCF_001

(customer function "001") is called from within the function module

QMCF_SPECIFICATION_CONFIG_READ.

The module QMSP_SPECIFICATION_CONFIG_READ is called when an inspection

lot is created (either manually or automatically), if in the QM

inspection data for the inspection type at least one of the indicators

"Inspect with spec." or "Inspect according to config." is set.

In this module, entries are made for the following tables before the

customer exit is called.

o L_QMSPTAB_SPEC

In the standard system, this contains the characteristics with

specifications (such as tolerances, units of measure) that are

defined in the material specification. If the SAP enhancement

QMSP0001 is active, these characteristics may have changed in

comparison to the material specification. The table structure is

similar to that of the table in the material specification (QMSP).

o L_QMSPTAB_CONF

This contains the characteristics and specifications that are

defined in the configuration. The table structure is similar to that

of the table in the material specification (QMSP).

o T_RQMCFTAB

This table contains a combination of tables L_QMSPTAB_SPEC and

L_QMSPTAB_CONF. The table contains the specifications from the

configuration for characteristics that are defined in both the

specification (L_QMSPTAB_SPEC) and the configuration

(L_QMSPTAB_CONF). The structure of this table is similar to the

table in the material specification. It also contains the field

HERKUNFT that records the origin of the specifications for each

characteristic. If this indicator has the initial value (blank), the

specifications are taken from the specification. If the indicator

has the value 'X', the specifications come from the configuration.

Result

tables in the parameters T_QMSP_SPECTAB (specification),

SP_CONFTAB (configuration) and T_RQMCFTAB (combination of both these

es) are available to the customer exit, in addition to the

ection lot record I_QALS.

Note for the table T_RQMCFTAB

Since the subsequent program only uses this table for processing, it

is advisable to adapt this table only.

The origin of the inspection specifications is recorded using the

field HERKUNFT.

The field can have two settings:

- Blank:

The data comes from the specification

- 'X':

The data comes from the configuration

>> You can take help of ABAPer to meet your requirement and to flow specification from SO Chars to MIC in RR.

Regards,

[Former Member · Accepted solution]

Tanuj,

Thanks for this solution.

Let me work on this and I shall get back to you.

Mimiri

[former_member42743]

Have you ticked on "additional values" in the class and characteristic?

FF

[Former Member]

Hello FF,

I haven't yet.

But what does it signifiy?

Also can you tell me how to derive the range(upper & lower limit) from the input value against the class characteristcis if the input value is single value and not the range?

Mimiri

[former_member42743]

Additional values allows values outside the specified values to be allowed.

You should specify the range and not just a target. i.e. if the customer wants 22.0 you would ener 21.9 - 22.1. I fyou enter 22.0 it would have to be 22.0 exactly.

FF

[Former Member]

That is what I am asking.

From variant attributes I will be getting the target value only.

Depending upon the tolerance limit agreed by customer I need lower and upper limits in inspection lot.

Hoe to map this?

Mimiri

[former_member42743]

I'm not sure you can.

You can specify a tolerance in the MIC. This than looks at the target value and calculates the upper and lower spec. But I don't hink you can specify the target value from variant config and if you could, I'm not sure it could triger a new spec calculation.

The only way I can think of doing this would be to maybe do it with a custom valuation rule. You create a new valuation rule that takes the spec passed from varinat config, say for instance 21.0 - 21.0 and uses the toleranc key for the MIC, + or - .2 and valuates the result against the calculated specs that it would figure out within the FM, i.e 20.8 - 21.2. Then it passes back either A or R.

FF

[Former Member]

Good one.

With this I can tackle requirement of MICs where the tolerance limit is fixed.

But in some cases the limit is customer specific.

Let me work on this and I shall come back to you with the results.

Mimiri

[vineeth_varghese]

FF,

Could you please tell my understanding is correct on this,

Step 1- MIC with class characteristic created, characteristic comes from variant configutation.

Step 2- Tolerence Key created and assigned to above MIC.

Step 3- Valuation Rule cretaed with new Function Module

Step 4- Valuation Mode created and assigned new Valuation rule

Step 5- Sampling procedure created with above valuation mode.

Step 6- Above created MIC is assigned to insp plan or mat spec

Valuation happens appropraitely at time of RR valuation, Please correct me, if am wrong.

Also Is it possible to explore calculated characteristic possibilities for this requirement?

Thanks

Vineeth

[former_member42743]

It looks like your steps are correct.

Using a calculated characteristic is difficult becasue the issue she has is that a target value is specified by the customer. This than has to be transalated to a spec using a tolerance key. But SAP doesn't have a way of doing that.

One thing I had forgotten about however. I wonder if she can use some general characteristics for this? General chracteristic A would be the target value for characteristic B. Characteristic B would use a procedure to calculate the spec range of Characteristics B using the target range in characteristic A. The tolerance range would have to be stored somewhere else. Possibly as a defautl value in a third characteristic.

So it would be something like this:

Characteristic Diameter Tolerance (defautl value of tolerance.. like 2)

Characteristic Diameter Customer Target: (inputted by sales at time of order creation, 34mm)

Characteristics DIiameter: (Spec range value calculate by a variant procedure) Would be 32 - 36 using above examples. It would be linked to a MIC and transferred to the lot.

FF

[former_member188029]

This message was moderated.