112: /*
113: * Fix for bug 6713003:
114: *
115: * The payee address fields are picked up from three
116: * possible sources: HR_LOCATIONS, PER_ADDRESSES
117: * and HZ_LOCATIONS. Therefore, the field sizes
118: * should be the maximum of the corresponding column
119: * sizes from these three tables.
120: *
118: * should be the maximum of the corresponding column
119: * sizes from these three tables.
120: *
121: * Usually, HZ_LOCATIONS field sizes are sufficient.
122: * But for state, county and provice fields, HR_LOCATIONS /
123: * PER_ADDRESSES has larger field sizes.
124: *
125: * Therefore, for these three fields, we use HR_LOCATIONS
126: * for the field sizes.
121: * Usually, HZ_LOCATIONS field sizes are sufficient.
122: * But for state, county and provice fields, HR_LOCATIONS /
123: * PER_ADDRESSES has larger field sizes.
124: *
125: * Therefore, for these three fields, we use HR_LOCATIONS
126: * for the field sizes.
127: */
128: payee_party_state HR_LOCATIONS.region_2%TYPE,
129: payee_party_province HR_LOCATIONS.region_1%TYPE,
124: *
125: * Therefore, for these three fields, we use HR_LOCATIONS
126: * for the field sizes.
127: */
128: payee_party_state HR_LOCATIONS.region_2%TYPE,
129: payee_party_province HR_LOCATIONS.region_1%TYPE,
130: payee_party_county HR_LOCATIONS.region_1%TYPE,
131:
132: payee_party_postal HZ_LOCATIONS.postal_code%TYPE,
125: * Therefore, for these three fields, we use HR_LOCATIONS
126: * for the field sizes.
127: */
128: payee_party_state HR_LOCATIONS.region_2%TYPE,
129: payee_party_province HR_LOCATIONS.region_1%TYPE,
130: payee_party_county HR_LOCATIONS.region_1%TYPE,
131:
132: payee_party_postal HZ_LOCATIONS.postal_code%TYPE,
133: payee_party_country HZ_LOCATIONS.country%TYPE,
126: * for the field sizes.
127: */
128: payee_party_state HR_LOCATIONS.region_2%TYPE,
129: payee_party_province HR_LOCATIONS.region_1%TYPE,
130: payee_party_county HR_LOCATIONS.region_1%TYPE,
131:
132: payee_party_postal HZ_LOCATIONS.postal_code%TYPE,
133: payee_party_country HZ_LOCATIONS.country%TYPE,
134: