Most of the time it is ok but if you run above command immediately after kicking off the script then you can get more than one process returned. Why is that ?
Think of changing command above to use ps l command but do not understand what the first column represents. It is F for field but I do not understand how to understand the results in the F column.
ie what does 200001 mean
If you get multiple processes then your script (or more accurately, the shell running it) must have forked for some reason. Without seeing the script there is no way to be more specific.
You will need to do a "man ps" to see what the F field means on your system. It is "Flags", that is, some bits that are turned on or off. Which flags and what meaning they have varies from system to system. And as is customary here, you did not reveal which system you are using. Most people just ignore that field these days. For example, on HP-UX, one bit means "locked in core". The trouble is that these days a process is not a monolith but rather a collection of regions. If one region is locked, do you set the bit? Another example, one bit means "in-core". How can that bit have any meaning at all in a demand-paged environment? Those flags were invented in a simpler time.
As Perderabo noted separately, your shell probably forked.
Another hint: You can save a process --- and time unless $USER has thousands of processes running but maybe even then --- this way (idea from Essential System Administration by Aeleen Frisch, 2nd edition, but I think a 3rd is out now):
Why this works is left as an exercise for the reader ...