Import File Specifications
The recommended method for creating import files is to use the Data Manager page. However, you can create your own import file by following these specifications.
Types of Files
You can use Notepad, Excel or any other desktop applications to create import files. When you create an import files, it must be saved as one of two types.
• A .csv file (comma-separated variable)
Create a .csv file for each table of data. For example, to import both part and location records, do the following:
1. Create a .csv file for all the part records.
2. Create another .csv file for all the location records.
• Am .xlsx file (Microsoft Excel)
Data for multiple tables can be contained in one .xlsx file (workbook). However, data for each table must be separated into worksheets. For example, to import both part and location records, do the following:
1. Create one .xlsx file that has two worksheets.
2. Include all part records in one of the worksheets.
3. Include all location records in the other worksheet.
4. Delete all unused worksheets.
Each worksheet name must match the related table name. For example, if you are uploading part type data, the worksheet containing that data must be named "parttype". Worksheet names are not case-sensitive. Table names can be found in IPCS_IMPORT in the Name column.
Structure of Files
The first row of the import file must be the data fields to be uploaded. These names must comply with the names found in the Data Download table that you wish to populate.
The names of the data fields can be found in several places:
• In the FullDB.sql file that was used to define the tables during the initial installation.
• In the Master Data Mapping Sheet that was used by the system architect to load the data into the application originally.
• In the Data Dictionary documentation provided at installation time.
• Using the tools at the disposal of the database administrator for your database.
Once an import file is built, you can upload it to the system.
Format of Files
The data you upload must comply with the rules for the data in the table.
• Dates must be entered in yyyymmdd format
• Numeric fields must be entered as numbers
• You must supply valid values for all non-null fields in the table. The one exception to this rule is the DownloadID field, which is supplied by the import process and should never be added to the list.
 |
Any field that is named Host<name>ID is a key field for another table. For example, HostPartID is a key to IPCS_PART_MASTER. If you are loading the data, the field should be consistent with data that was loaded previously. Generally, this is assigned logically. Thus, HostPartID is generally going to have the same value as PartNumber, but it is good practice to verify this with your database administrator.
|
Valid .xlsx File Names
When importing Excel (.xlsx) files, data for each table must be separated into worksheets and these worksheet names must be the same name as the table. The following are valid Excel worksheet names for Excel (.xlsx) import files. Worksheet names are not case-sensitive.
• ActionParams
• ActionSchemeCovgs
• AdjustmentProfile
• AdjustmentProfileCovg
• AdjustmentProfileDetails
• AdjustmentProfileStream
• Alert
• AutopilotParams
• Calendar
• CalendarOffDates
• CausalInputGroup
• CausalInput
• CfCausalType
• CfCausalValue
• CfContract
• CfFailureRate
• CfPartCausalType
• CfProdBom
• CfProductRollout
• CfWeightFactor
• CfWeightFactorDetail
• ContractType
• CopyDemand
• Cost
• Currency
• CustomDisplayDef
• CustomerPartProps
• CustomerProdProps
• DemandDetail
• Demand
• EolSku
• EventCoverage
• Event
• EventProductBOM
• EventProduct
• EventSchedule
• ExternalStockLevel
• ForecastConsumptionExtCovg
• ForecastConsumptionExt
• ForecastConsumptionIntCovg
• ForecastConsumptionInt
• Forecast
• InstallBase
• InstallSite
• JournalDetails
• Journal
• LLPCurrentUsageSN
• LLPCustomerPartInfo
• LLPCustomerUsage
• LLPUsageLimit
• Location
• Location
• LocationType
• LocHier
• LocHierDetail
• LocLocLT
• LTBDecayRateParamCovg
• LTBDecayRateParam
• LTBDemandHistory
• LTB
• LTBProfileDetail
• LTBProfile
• MEOBudgetParamCovg
• MEOBudgetParam
• MEOServiceGroupParamCovg
• MEOServiceGroupParam
• OptSchemeCoverage
• OptSchemes
• OptSubSchemeCoverage
• OptSubSchemes
• OrderParamCovg
• OrderParam
• OrderPlan
• OrderTypeParam
• PartChainDetails
• PartChain
• PartChainLocation
• PartCritical
• PartFamily
• Part
• PartKitBom
• PartKit
• PartKitLocs
• PartList
• PartListPart
• PartnerGeoCoverage
• PartnerLocCapacity
• PartShipment
• PartSubstitution
• PartType
• PlannerCodes
• PlanningParamCoverage
• PlanningParams
• PoolCoverage
• PoolScheme
• Price
• PriceAction
• PriceClass
• PriceFeedback
• PriceLine
• PricingGroupStepLevel
• PricingMarketGroup
• PricingMarket
• PricingMarketRelationship
• PricingMarketRelationshipType
• PricingSimpleGroup
• PricingSurveyCompany
• PricingSurveyData
• PricingSurveyDetail
• PricingSurveyPart
• PricingSurveySource
• ProcCoverage
• ProductBomCausal
• ProductBom
• ProductGroup
• Product
• ProductLine
• ProductRollOut
• ProductShipment
• PromotionCost
• PromotionHistory
• Promotion
• PromotionPrice
• PromotionVolume
• Region
• RepairOptions
• ReplCoverage
• ReplScheme
• ReplSKUParams
• ReviewCoverage
• ReviewDetails
• ReviewParams
• SalesOrder
• SalesReturn
• SCSCoverage
• SCSParamList
• SCSParamMaster
• SCSSKU
• SeasonalIndex
• SeasonalParam
• SeasonalParamsCoverage
• SeasonalProfiles
• SegCovgCriteria
• SegmentDimensions
• Segments
• SegmentTree
• ServiceGroupParamLocationContract
• ServiceGroupParamLocation
• SKU
• SKULocLT
• SkuOverride
• SkuPSetCovg
• SkuPSet
• SkuReplacementRate
• SsfProfileDetails
• SsfProfile
• State
• StockAmount
• StockingCoverage
• StockLevel
• StockLevelSlice
• StreamConfigDetails
• StreamConfigs
• TierGroupSurveyPart
• TransportMode
• TransportModeParamCovg
• TransportModeParams
• TransportModeProc
• VendorGroupMoq
• Vendor
• VendorLoc
• VendorLocLimit
• VendorLocLoc
• VendorLocPart
• VendorLocPartPB
• VendorLocSKULT
• VendorLocSKUPB
• VendorProgram
• VendorProgramLoc
• VendorProgramPart