4.3 Source Refresh - Not Possible Scenarios

This topic provides systematic instructions to Source Refresh - Not Possible Scenarios.

Source refresh is not possible in below scenarios:

1. If Parent Function id LOV modified after child refresh if same LOV used in Child function id after next refresh those LOV'S Should be Modified manually.
2. If Fields data type are changed (examples Increase/Decreased length, Number to varchar2) in custom layer, Later Kernel changed same fields data type those changes would not be reflected in Custom layer. If these changes requires in Custom layer manually (Using ODT Function generation options to refresh data type) needs to change.
3. The Following Custom attributes are changed in custom layer, Later Kernel same custom attributes are changes (Add/Deleted) those changes would not be reflected in Custom layer. If these changes requires in Custom layer (Using ODT Function generation options to refresh data type) manually needs to change Radio Button, Static List values.
4. There should not be nay naming conflicts in elements across releases (KERNEL, CLUSTER, CUSTOM) or across the parent-child functions.
   For example: same field set should not be created in both Parent and Child Function Hence a standard naming convention has to be followed for each release type/and function type so that names does not conflict.
   For instance: All Field Sets in a Custom Parent has to follow convention like FST_U.
5. Upgrade feature in not available for Summary Nodes.