Select collection then delete several tables

Question

BEGIN
;WITH MyResult AS
SELECT containerID AS barCode, dbo.fn_checkExpiration(containerID) AS containerExpired
FROM [Barcode].[dbo].ContainerHistory
WHERE dateEntered >= DATEADD(DAY, DATEDIFF(DAY, 0, CURRENT_TIMESTAMP) -1, 0)
AND dateEntered < DATEADD(DAY, DATEDIFF(DAY, 0, CURRENT_TIMESTAMP), 0)
AND stateID = 1
DELETE FROM PalletBarcodes WHERE barcode IN (
SELECT barCode FROM MyResult WHERE containerExpired = 1)
DELETE FROM LotContainers WHERE barcode IN (
SELECT barCode FROM MyResult WHERE containerExpired = 1)
barCode FROM MyResult WHERE containerExpired = 1)
END
This TSQL code works for what I have to do of deleting records from several tables, except I get an error when executing this as a stored procedure. Why can't I use the collection select query MyResult without having to do the MyResult collection
query a 2nd time for the 2nd DELETE of  LotContainers ? 

Answer 1

Please follow basic Netiquette and post the DDL we need to answer this. Do you know how to follow industry and ANSI/ISO standards. You should follow ISO-11179 rules for naming data elements. You have no idea! You should follow ISO-8601 rules for displaying
temporal data. Avoid dialect in favor of ANSI/ISO Standard SQL. 
Please do not use UDFs. It is bad declarative programming, cannot port and cannot be optimized. Even worse, the “fn_” prefix is taken from FORTRAN I and II and from 1960's BASIC. These compilers were so weak they had to use the prefixes as a signal! But OO
programmers who never learned to think in SQL use them to mimic methods from their “native language” 
Please learn basic RDBMS; a data element has one and only one name! Is it a “bar_code” or a “container_id” in this data model? Since bar codes are a data format and not a logical data element, this is a real design problem. 
As an aside we no longer use camelCase; it has ISO problems in many standards and does not work. Your eyes jump to the uppercase letter, then twitches back to the start of the word. It is painful to read. 
But the worst problem is “state_id”, so wrong! A column can be “<something in particular>_status” or “<something in particular>_id” but never some weird hybrid chain of what ISO-11179 calls attribute properties. This looks like noob with a 1950's
assembly language bit flag used in his bad SQL. 
An SQL programmer would have an “expiration_date” and not use a silly “container_expiry_flg” you have. We use predicates to get facts; assembly language looks for flags that were set and might be current. 
Since we have a DATE data type, you can write: entry_date = CAST (CURRENT_TIMESTAMP AS DATE).
Since you did not have the Netiquette to post DDL, I will guess that the deletions you did in separate statements should have been done with ON DELETE CASCADE clauses! 
>> This TSQL code works for what I have to do of deleting records [sic] from several tables, .. <<
Rows are not records! You really have no idea how to write SQL, do you? Want to try again and be polite? 
--CELKO-- Books in Celko Series for Morgan-Kaufmann Publishing: Analytics and OLAP in SQL / Data and Databases: Concepts in Practice Data / Measurements and Standards in SQL SQL for Smarties / SQL Programming Style / SQL Puzzles and Answers / Thinking
in Sets / Trees and Hierarchies in SQL