If you have assigned components to different phases or operations you may want to get an overview of all components regardless of their phase assignment at the start of the PI Sheet or Electronic Work Instruction. Here is the way how to do it.
If you are using process instructions (not XSteps) you need to have a process instruction with all the characteristics and output elements which I don’t explain further. When assigning that process instruction in your control recipe destination setup (O10C) you need to use the position ’01’ (At the start of the control recipe) and of course the generation scope ’01’ (all reservations). This will generate that instruction for all reservation items regardless of their assignment to a specific phase.
If you are using XSteps you need to setup the parameters which are valuated with the material data and use some output elements to display them. In the XStep you need to choose any material-related generation scope. When you use that XStep in your recipe you need to make sure that no phase context is assigned to it (if you do you will get the phase-specific material list(s)). This will put the material table at the beginning of the PI Sheet (assigned to the virtual phase 0000)
Quick Tip: Complete Material List,| Please rate the article: |
Hello, I have been trying to do something similar to this so I attempted to do what is described here in order to test. No matter what scope of generation I choose I do not get a table containing a list of materials, the end result is always a set of tables, with one material per table. This is because the scope of generation causes the XStep to be repeated for each material.
Looking through the databases I can see that the generated XStep tree would not have room for a list of values in a table parameter, only room for a single fixed value or the valuation symbol itself, but hopefully I am missing something.
I see what my issue was now, I had the process instruction set to be a “repeated data request” instead of a “simple data request”. I will continue my testing to see if this will fix my other issue.