cbudoris
Active Member
Anybody know what could cause leading spaces to be stripped out of a field after a fetch? This started happening to us last week.
The MCUS field in the F0006 looks like it should when viewed in the database- 12 length, right justified with leading spaces ' 20333'. But now, in the ER code after a fetch or fetch single, its coming out as '20333'. The variable we're assigning it to is also defined as MCUS. We've tried creating a new field, using MCU as the variable field, but got same results.
The NER business function its in has been in use since '08, and has not been modified in the time frame when this start happening (sometime in the last month).
We've considered it could be data dictionary related, and we did recently rebuild the data dictionary. But we didn't touch that data item at all. And its just acting that way in the F0006- a similar fetch in the F1506 to the MCUS field does NOT recreate the error. So you'd think if this was data dictionary related, it would affect all MCUS fields, but that's not what we're seeing.
We've also tried removing and adding back the value in the MCUS record on F0006- indeed it right justifies the data as expected. But when you retrieve it in ER, it still strips the leading spaces.
Any ideas out there what could be going on?
ERP 8.12
Tools 8.98.3.4
database: Oracle 11GR1
The MCUS field in the F0006 looks like it should when viewed in the database- 12 length, right justified with leading spaces ' 20333'. But now, in the ER code after a fetch or fetch single, its coming out as '20333'. The variable we're assigning it to is also defined as MCUS. We've tried creating a new field, using MCU as the variable field, but got same results.
The NER business function its in has been in use since '08, and has not been modified in the time frame when this start happening (sometime in the last month).
We've considered it could be data dictionary related, and we did recently rebuild the data dictionary. But we didn't touch that data item at all. And its just acting that way in the F0006- a similar fetch in the F1506 to the MCUS field does NOT recreate the error. So you'd think if this was data dictionary related, it would affect all MCUS fields, but that's not what we're seeing.
We've also tried removing and adding back the value in the MCUS record on F0006- indeed it right justifies the data as expected. But when you retrieve it in ER, it still strips the leading spaces.
Any ideas out there what could be going on?
ERP 8.12
Tools 8.98.3.4
database: Oracle 11GR1
