You can perform a load transfer coupled-field analysis using either separate databases or a single database with multiple physics environments. In both cases, use LDREAD to read the results and apply them as loads.
Figure 5.1: Data Flow for a Load Transfer Coupled-Field Analysis Using Separate Databases shows the data flow for a typical load transfer analysis done with separate databases. Each database contains the appropriate solid model, elements, loads, etc. You can read information from a results file from the first database into another database. Element and node numbers must be consistent between the databases and the results file.
Figure 5.2: Data Flow for a Load Transfer Coupled Physics Analysis Using Multiple Physics Environments shows the data flow using a single database and multiple physics environments. In this approach, a single database must contain the elements and nodes for all the physics analyses that you undertake. For each element or solid model entity, you must define a set of attribute numbers, including an element type number, a material number, a real constant number, and an element coordinate system number. All of these numbers will remain constant across all the analyses. However, the actual properties associated with a given attribute number can vary among all the physics environments, as can the definition of the parameters in real constant sets and the element type number. Regions of the model may be inactive for a particular physics solution, as this chapter will explain later.
Figure 5.2: Data Flow for a Load Transfer Coupled Physics Analysis Using Multiple Physics Environments

Build the ANSYS database with the requirements of each physics environment in mind. Before creating any physics environments, assign the element type number, material number, real constant set number, and element coordinate set number of each distinct region for each area or volume. (See the descriptions of the AATT and VATT commands.) Be careful when working with problems where a given area or volume is part of the problem domain for two different physics types.
Using separate databases is ideal for one-way load transfer coupling, such as a typical thermal-stress analysis. Using a single database with multiple physics environments allows you to quickly switch between physics environments, which is ideally suited for fully coupled scenarios requiring multiple passes between physics solutions. Induction heating is a typical example of a case requiring the single database/multiple physics environment approach.
Note that the database file may grow in size during multiple solution passes unless you take one of the following actions:
Issue a SAVE after creating the physics environments and a RESUME after each physics solution.
Do not write results into the database (only write to the results file). You will then need to issue a SET command whenever you want to read data from the results file into the database for postprocessing. To invoke this option, either issue the command /CONFIG,NOELAB,1 or insert the line "NO_ELDBW = 1" into the config.ans file.