How can we delete Accounting data with null UniqueName?

To deactivate the accounting objects with a null UniqueName you have to use Full Load or a Load and Delete operation. Usually only the Load operation is visible in the data import section, not the Load and Delete. The full load only keeps the data matching the data in the csv file and will deactivate everything else, including the accounting objects with a null UniqueName.

To work around this you can use the Import Batch Data task instead. This task does a Load and Delete operation. For this you need to:

1. Create a file with the correct accounting data that contains the current data with UniqueName populated.
2. Zip the file as per the file name convention for Supported Files (View Supported Files after clicking the Import button). The csv file within the zip has to have the correct spelling.
3. Select operation as Full Load, browse the file and click OK. Anything not in the csv file will be deactivated.

Some Accounting Elements such as AccountingCombinations, WBSElements, Projects etc., in specific variants does not have the UniqueName as a required field even though UniqueName is the lookup key.

When you have loaded such data, the Delete operation for Data Imports doesn't work since it's specifically looking for a UniqueName to delete/deactivate. Since it's null, the lookup fails and nothing is deleted.

Core Procurement > Core Administration > Core Accounting
Invoicing