Understanding Oracle’s road map of Classic to Fluid page conversion

As part of PUM 29, Oracle released a new Fluid page for Position Data which includes a new record definition, POSITION_DATA_E, with the effective sequence as the new key field. The search record was also modified to remove the ability to search for Positions based on Business Unit and Department. Our understanding of Oracle’s road map of Classic to Fluid page conversion was only to modernize the look and feel of self-service pages in the “e” modules. With PUM 29 it looks like Oracle is planning to implement Fluid concepts for transaction pages that are part of the core modules.