To write a mapping for this scenario we need to create the actual temp table in our dev machines only then we will be able to make use of the table as a source/destination to map input/output columns. So after creating the temp table and writing a data flow to make use of the temp table and then dropping the temp table, the workflow will look like below.
But when we try to execute this package or when we deploy them to a test server it will give Validation errors like below.
This is because the table is yet to be created/found in the specified destination connection. To enable smooth move to testing/production we need to set the "Delay Validation" property to True for the dataflow which makes use of the yet to be created temp table. This property is highlighted below.
