This content has been marked as final. Show 5 replies
Actually all the information in FDM are stored in the FDM application's database.
Therefore you can create this locations by SQL statment.
As far as I know, there is a table called "TPOVPARTITION" which can find each location's record.
I think you can first manually create one-two entities from FDM web. Then see what records in TPOVPARTITION table. Then write SQL statement to insert other locations.
So in table TPOVPARTITION you should have all your entities in it?
I have not done it before but I think it would be a way to insert many entities at once.
If you cannot get the entities in FDM, there should be something to add at other database tables.
I think you can create a database monitor to see what changes after one location is created. Then you can use SQL statement to do the same thing.
Two things :
#1 - The tables you need to add data to are : tPOVPartition, tStructPartitionHierarchy, tStructPartitionLinks. The first table is the basic location information. The last two tables define the relationship hierarchy of where the locations belong. I would expect that if the Strcut information is missing, FDM will not be able to place it anywhere on the locations screen.
Additionally, for the tPOVPartition, there is required information and you need to make sure you are including all of that info when you create your record.
#2 - If you are handy at coding, I'm positive there is an API call to create a location. It would make more sense perhaps to write a script that uses the APIs to create the locations so that you can be sure that it is being done right.