In earlier releases, the PRODUCTIVITY_TYPE column in the YFS_PRODUCTIVITY_TYPE table was localizable but the same column in the YFS_TASK_TYPE table was not localizable. For example, in an existing localized environment, the value in the PRODUCTIVITY_TYPE column in the YFS_PRODUCTIVITY_TYPE table would be in the localized language and the same value in the PRODUCTIVITY_TYPE column in the YFS_TASK_TYPE table would be in the English language. In Release 9.1, both columns are not localizable. However, for existing localized environments, if resource planning is enabled at the warehouse, creating/modifying shipment may give a null pointer exception.
While looking for Productivity Type in the localized database, system takes the Productivity Type from the YFS_TASK_TYPE table, which is in the English language. Because Productivity Type in the YFS_PRODUCTIVITY_TYPE table is localized, no result is fetched from the YFS_PRODUCTIVITY_TYPE table.
This section describes the migration process.
None.
You must manually change the localized value in the PRODUCTIVITY_TYPE column in the YFS_PRODUCTIVITY_TYPE table to the corresponding value in the English language.