Data Management Capabilities > Using Packages to Import and Export Data for Offline Collaboration > Import Received Delivery > Importing Received Delivery Files
  
Importing Received Delivery Files
After uploading all received delivery files and optionally specifying any attribute mappings, you can import the received delivery file contents into your Windchill system, whether it is a full or incremental delivery. For more information about incremental deliveries, see Importing Incremental Received Delivery Files.
* 
• For the Import Received Delivery action to be available, the received delivery must have an import status of either Ready, Unsuccessful: Import Failure, or Unsuccessful: Partial Import. If the import status is Unsuccessful: Partial Import, the import options cannot be changed before reattempting import.
• When importing a received delivery, if it is partially imported and you try to import the same received delivery again, the previous import logs will be retained with the new import logs.
1. Select import received delivery from one of the following locations:
◦ The Received Delivery Management table as a right-click or table-level action.
◦ The Actions menu on the received delivery information page.
2. In the Import Received Delivery window, verify that the version information mapping is correctly defined for the source system. When the target system is configured for an implicit mapping, the Version Information Mapping field displays Position based. When the target system uses the version information from the source system without an implicit mapping, the field displays None. For more information, see Defining Received Delivery Version Mapping.
3. Select the appropriate checkboxes, depending on your anticipated conflicts:
Checkbox
Description
Use the default resolutions available for conflicts
Uses the default resolutions provided by Windchill for all conflicts. Any conflicts found are resolved with the default resolution and not reported in the Event Management utility.
For more information, see Conflict Messages for Packages.
Use the previously saved resolutions
Uses any saved resolutions you set with the Event Management utility on a previous import from this source system. Optionally, resolutions can be saved during import or defined by loading them into your system. For more information, see Defining Received Delivery Conflict Resolutions Using a Load File.
If you select this option with the Use the default resolutions available for conflicts option, any saved resolutions are applied and, if no saved resolution is available for the conflict, the default resolution is applied.
Save the latest resolutions provided by you during this import process
Saves any resolutions you select in the Event Management utility to be used again with this source system. You can select resolutions to any conflicts reported in the Event Management utility. Any resolutions saved for a source system can be reviewed using the Download Resolutions action from the Mapping Management utility.
If you select this option with the Use the previously saved resolutions option, any previously saved resolutions are applied first, and resolutions to any new conflicts that arise can be selected using the Event Management utility. If both options are selected, resolutions selected during this import are added to previously saved resolutions.
4. Select the import location from the Import Into drop-down list:
Option
Description
Current Context
Uses the context in which the received delivery resides as the target context for all imported objects. This context is also used to determine mapping values that are dependent on the context.
Mapped Context
Uses the context from the sending system for each imported object. If a defined context mapping exists, it is used as the target context. If there is no defined context mapping, Windchill searches for the same context name on the current system. If the matching context exists, it is used. If there is no matching context, a conflict is identified, and the import fails.
5. Click Import.
The status of the received delivery will be In Progress until the import completes. Depending on your settings, the import may not succeed if there are no resolutions found for a conflict.
* 
Import the received delivery in the same order as they were exported from the source system. To determine the appropriate order, you can sort the Received Delivery Management table based on the Source Zip Creation Time column. For more information on this and other import-related best practices, see Best Practices for Importing Received Delivery Objects.
* 
• To optimize the CPU usage and queue operation, set Type of cleanUpMissTargetInfoQueue to Process. If the Type is set to Pool, delete the queue cleanUpMissTargetInfoQueue at the Site level. When the Received Delivery ZIP file (that includes the missing object dataset) starts to import to the target Windchill server at the site level, a new queue is created with Type as Process.
• Authorization requirements vary based on the actual objects being imported. In general, importing an object requires the same authorization as the corresponding action in the Windchill system. For example, Create permission is required to create a new object via import. Alternative resolutions may be available if the user is not authorized to complete an action.
• After uploading received delivery files containing large numbers of objects, Windchill may divide the objects into multiple import transactions. The default threshold to use multiple transactions is 50,000 objects. Objects are divided into the multiple transactions in a way that does not cause import errors. For example, if two objects are linked, they will be included in the same transaction. For more information, see How to Write Exp/Imp Handlers.
• If you receive a Commit Mismatch exception while importing a received delivery, configure the wt.pom.dbConnectionPropertiesNameList=oracle.jdbc.javaNetNio, wt.pom.dbConnectionPropertiesValueList=false properties in the WT_HOME\db\db.properties file.