Over the years Location Master (F4100) contains huge orphaned data in it. To minimize possible performance impact across EnterpriseOne system unnecessary data needs to be purged.
Currently there is no batch application which purge data from F4100 rather Location Master (P4100) is to be used to delete records which appear in grid. For additional information refer to E1: ENV: Archive and Purging within EnterpriseOne (Doc ID 1082128.1).
In deleting data through P4100 it validates deletion by checking data from Item Location File (F41021). If there is any data WHERE ( (F4100.MCU = F41021.MCU) AND (F4100.LOCN = F41021.LOCN)) hard error Delete Not Allowed - Item/Location Info (Error 3256) is to be issued.
Potential Process (make sure to backup data before proceeding):
Run R4102P to purge data from F41021
Delete F4100 through P4100
Or
Purge all the data from F4100
Run Build Location Master (R41820) which creates F4100 based on F41021.
Or
Use SQL tools (outside JDE - this process is not supported by Global Support Services)
Verify/count/update number of orphaned data from F4100
Delete it
Check existence
sql> select count(*) from proddta.f4100 where not exists (select * from proddta.f41021 where (f41021.lilocn = f4100.lmlocn and f41021.limcu = f4100.lmmcu) )
(optional) update
sql> update proddta.f4100 set lmurrf = 'tobedeleted' where lmlocn in ( select lmlocn from proddta.f4100 where not exists (select * from proddta.f41021 where f41021.lilocn = f4100.lmlocn and f41021.limcu = f4100.lmmcu ) )
Delete
sql> delete proddta.f4100 where lmurrf='tobedeleted'
Note:
There is no table to archive so it is always proper to back up data before take any action against a certain database and tables
Before purge data from F4100, get familiar with how data from F41021 are to be purged