While importing a model from other environments to Agile Business Suite, you might encounter some issues and behavioural differences. You must follow the guidelines given below for some of the importing issues:
Logically Deleted Records and the LookUp Command
In Enterprise Application Environment release 3.x, LOOKUP; commands had differing behaviour depending upon the context in which they were executed:
When executed within an Ispec, LOOKUP; command ignored logically deleted records (that is, component records that had been deleted, so that MAINT was set to 'D').
When executed within a Report, LOOKUP; command read logically deleted records.
In Agile Business Suite, to make the behavior of the LOOKUP; command more uniform and consistent, the LOOKUP; command always retrieves logically deleted records.
To maintain the existing behavior in migrated systems, some additional LDL+ logic is included in LOOKUP; commands coded within insertables and segment methods and ispecs. This logic causes logically deleted records to be rejected or skipped by LOOKUP; commands.
There are two situations where the LOOKUP; command can be used.
Looping forms of LOOKUP; command coded within ispecs, insertables, and segment methods read logically deleted records into memory, but the added logic results in them being skipped or ignored. However, if a looping form of LOOKUP; command reads only logically deleted records, Glb.Status is set to spaces because at least one record has been read into memory.
The additional logic to skip logically deleted records is added to LOOKUP; commands within ispecs, insertables, and segment methods. When a Report calls an insertable or segment method that performs a Lookup, the logically deleted records are skipped (due to the included logic).
Auto Entry Ispec and its instance
During migration of an Auto Entry Ispec from EAE, the import process creates an instance of the Ispec with the name "_AutoIspec" appended to Ispec name. This instance is then placed under the folder named "AutosForIspecs". For example, if CUST is an Auto Entry Ispec in your model, the instance Cust_AutoIspec is created and placed under AutosForIspecs folder after migration.