on 06-13-2018 11:45 AM
This can be handled using standard SAP functionality. It does require the creation of an FM.
Quality Management-->Quality Certificates-->Certificate Profile-->Define Data Origin
Select "Origin of characteristic specifications"
If you double click on an item you'll see the values and a FM behind each choice.
I'd copy SpecOrign 10 to say Z1. Change the text as appropriate. Copy the FM QC02_CHAR_SPECS_DUMMY to a new Z FM. In the FM you should get the QCVME structure imported in. In that structure is the MIC number (QMERKNR) and the characteristic internal number (ATINN). You can then put in your own logic in to get the value you want to return as the specification to the COA profile. Here are some design choices:
1) using the MIC number get the spec text value from the info field 1, 2 or 3 field in the MIC. This works if the same text can be used for all customers and profiles.
2) classify your mic. In the MIC class add a characteristic called "COA_SPEC_TEXT" and insert the text here. Have the FM retrieve that,. You can add multiple characteristics in case you have specific customer or material COA profiles. COA_SPEC_XXXXXXXXXXXX where xxxxxxxxxxxx is the COA 12 character profile name. In this case, the FM looks for a characteristic specific to the COA profile. If none is found, it uses the value for COA_SPEC_TEXT. This give you the most flexibility.
3) Same as #2 but classify the general characteristic and use the ATINN to retrieve the values.
4) Add a method the characteristic and using QMERKNR look up the method and in the method header get the spec text from info field 1, 2 or 3. This works where the same spec description can be used for all customers and profiles.
5) Methods can also be classified. You can use the same concept as in #2 but get the spec text from the classification data of the method.
6) If you don't use the column "Char. description" for electronic distribution of your COA, you can put in the characteristic spec text into this field. The function module then simply returns the value for field QCHARACT_ID1 from structure QCVME. This is easy, but has to be in every COA profile. The other options are less maintenance as those values are held at a characteristic level can be used in multiple COA profiles.
7) create a custom Z table indexed by characteristic (QMERKNR or ATINN) and the cert profile and maintain the spec value there. I hate using custom tables though. They then usually require a custom Z transaction for maintenance, updating security roles, etc.. And in most cases there are other options as shown in 1-6 above.
Once you've done all that, you maintain the master data. Then in the COA profile for the attributive characteristics you select Z1 for the column "insp.spec.origin".
Craig
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is brilliant thanks Craig
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
91 | |
11 | |
10 | |
6 | |
5 | |
5 | |
5 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.