fnd_conc_clone.setup_clean vs cmclean.sql

fnd_conc_clone.setup_clean
====================
fnd_conc_clone  ===> is package
setup_clean ====> it is procedure name
When we run fnd_conc_clone.setup_clean it deletes the information from the below tables.
Delete from fnd_concurrent_queue_size
Delete from fnd_concurrent_queues_tl
Delete from fnd_concurrent_queuesDelete from fnd_nodes;

We use fnd_conc_clone.setup_clean to cleanup fnd_nodes table in the target to clear source node information as part of cloning.

below syntax to execute:
SQL> sho user
USER is "APPS"
SQL> exec fnd_conc_clone.setup_clean;
PL/SQL procedure successfully completed.
SQL> commit;
Commit complete.
First run the autoconfig on DB tier and middle tier this will regiser the nodes in fnd_nodes tables.

cmclean.sql
=========
If we stop conc manager using abort options then concurrent requests will be in running state ,Next when we start concurrent manager the processes will not start properly.
To cleanup running and pending requests we use cmclean.sql this script will update the below tables.
UPDATE fnd_concurrent_processes
UPDATE fnd_concurrent_queues
UPDATE fnd_concurrent_requests
UPDATE fnd_conflicts_domain
UPDATE fnd_concurrent_conflict_sets
Download cmclean.sql: 
=================
Concurrent Processing - cmclean.sql - Non Destructive Script to Clean Concurrent Manager Tables [ID 134007.1]
Note: cmclean.sql and fnd_conc_clone.setup_clean touch different set of concurrent request tables.
Its better idea to run both during the clone.