Newbie how to approach customize Histogram, Sigma Capability, and Process Summary

[#1]

Hi.  I am very new.  Before I jump into learning Scripting, I would like to get a confirmation I am approaching this correctly.  We want an easy way to create the below simple Distribution report that can be created for a user selected column, typically 30 data points, that looks like the below pic and we are hoping to remove the items with red lines:

An example of a data table is: 

Below is the script the system created when I used: Save Script/To Data Table:

Distribution(
Continuous Distribution(
Column( :OD ),
Horizontal Layout( 1 ),
Histogram( 0 ),
Vertical( 0 ),
Process Capability(
Use Column Property Specs,
Process Capability Analysis( Nonconformance( 0 ) )
)
),
Histograms Only,
SendToReport(
Dispatch( {"OD", "Process Capability", "OD Capability", "Histogram"}, "1",
ScaleBox,
{Min( 2.1388234375 ), Max( 2.1636765625 ), Inc( 0.005 ),
Minor Ticks( 5 )}
)
)
);

I am assuming this cannot be done without scripting.  If that is not true, please let me know.

What I am planning on doing is trying to learn how to script so the user can select the Column to use, where the above script only uses column "OD".  This would, hopefully, give the basic report above by running the script.

Then start looking for script changes to remove the entries that we have crossed out in red.

Is this approach naive?  Is there a better way to approach it?

Thank you for any input,

Grant

[#2]

I used

Filter Where(Portion == "Total Outside");

but you can still use Contains if you want to (in your script the problem wasn't contains but using wrong column Expected Overall PPM instead of Portion to do the comparison from)

Report(dist)[Outline Box("Nonconformance"), Table Box(1)] << Filter Where(Contains({"Total Outside"}, Portion));

I used equal comparison because you wish to only show single line of the table. Contains can be used for multiple items and when you just have single item (like in this case) it is unnecessary. 

Reason I changed it was something like this:

You might think that "but does it matter if it works?". Basically it doesn't BUT when you (or at least when I do) start thinking about the code it will matter slightly. For me it would now be obvious that there will never be more than single item in that table (or if there is more than one, the idea of the filtering must be changed and it will make you stop a bit).

[#3]

Jarmo, thank you for that excellent explanation.  

[#4]

The trigger for good community posts are good questions.
Thanks @GM-FPP .

[#5]

Thank you @hogi I appreciate your message.