---------------------------------------------------Can Refresh Snapshots in Mode "Complete", "All Snapshots" be run AFTER Collections and ASCP.---------------------------------------------------Refresh Snapshots currently runs every night before Standard Collections and ASCP. It is known that Refresh Snapshots need not be run unless there is question about integrity of data from Standard Collections, but it is a 'security blanket'. Last month ASCP was moved off the EBS Transaction Server to a distributed Planning Server. Now Refresh Snapshots is no longer part of a Report Set run every night before Standard Collections and ASCP. Given concern that it might not complete in the EBS Server before Standard Collections launches in the Planning Server, the thought is to run Refresh Snapshots nightly after ASCP finishes. If this is done, would there be any concern about integrity of data collected by Standard Collections 18 hours later in the next night's Planning cycle?Standard collections process: Using the standard collections process, you can manually runthree types of collection methods including a complete refresh, a net change refresh, or atargeted refresh on specific business entities.Standard collections process: Using the standard collections process, you can manually runthree types of collection methods including a complete refresh, a net change refresh, or atargeted refresh on specific business entities.Standard Collections to collect new or changed reference information from specifiedInstancesThe Complete Refresh method clears all transaction data for all business entities from theplanning server (for the source instance being collected), then copies over information aboutthe user-selected entities. This method can be time consuming.You should use Complete Refresh the first time you perform collections from a source instanceto the planning server. You may also wish to use complete refresh collections after asignificant proportion of the setup data in your transaction system has been altered, and youwould like to make a fresh copy of all source instance business entities (items, bills of material,sourcing rules, resources, and so on) on the planning server. You typically collect all businessentities in a Complete Refresh Collection.The Targeted Refresh method clears transaction data for only the user-selected businessentities from the planning server, and then copies the entity information over from thetransaction instance. Information about nonselected entities remains intact on the planningserver. All planning business entities are supported by Targeted Refresh collections.You should use Targeted Refresh if you would like to update the planning server informationfor some (but not all) business entities, and some of these entities fall outside the category ofsupply and demand entities supported by Net Change Refresh. For example, to update theplanning server with a newly rebuilt manufacturing calendar, you would run Targeted Refreshcollections for just the calendar business entity. Data on the planning server about all otherbusiness entities would remain unaffected by this collection.You would also use Targeted Refresh (in lieu of Net Change Refresh) to bring over the latestpicture of supply and demand to the planning server in cases when the incremental changes tosupply and demand on the source instance since the last collection are very extensive. In thiscase, the update mechanism employed by Targeted Refresh collections (wholesale deletionfollowed by rebuilding of data on the planning server) is faster than the mechanism employedby Net Change Refresh collections (incremental insertions into existing data on the planningserver).The Net Change Refresh method copies only incremental changes to business entities to theplanning server (and is thus faster), but is supported mainly for demand and supply businessentities only.You should use Net Change Refresh if you would like to update the supply and demand pictureon the planning server as quickly as possible, and the incremental changes to supply anddemand in the source instance since the last collection have not been extensive relative to theexisting (already collected) body of supply and demand information. In this case, Net ChangeRefresh is the fastest way to achieve the desired update of the planning server operational datastore, because it copies over from the source instance only the incremental changes in supplyand demand since the last collection.