Quantcast
Channel: SCN: Message List
Viewing all articles
Browse latest Browse all 8468

Re: notification origin

$
0
0

Check if you can use defect location code groups for this. If you refer to QM15 report following texts and codes are visible.

 

  1. Code group of Defect Location
  2. Code Group description of Defect Location
  3. Code of Defect Location
  4. Code description of Defect Location

 

Above set will be common (for logic) for catalogs of defects, causes, tasks, activities at item level and coding at header level.

 

What I can suggest is to explore whether all these have been properly utilized or not and try to set the logic of codes so that the individual code or code group will make some sense for reporting.

 

I doubt at the last instance of notification closure it will be possible or not but I can give 1 example by which this can be mapped. Create 2 code groups- One for Internal Origin and another for External Origin  under defect location catalog. The agencies responsible for externals factors would be the codes of External Origin code group. Same way for internal.

 

Else you need to go with custome screen mapping and new Z table creations to store the information. When you click on internal or external radio button at the time of notification closure it will take you to different screen say vendor code screen from where you can choose required entry. Earlier option is more advisable, I would say!

 

Anand


Viewing all articles
Browse latest Browse all 8468

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>