Upgradation -hard Coding issue

[Former Member]

Hi,

I'm working in an Upgradation Project(from 4.6c to ECC 6.0) where I need to remove Hard Coding in general.

I met with a situation where I have to use hard coding, but it's not good to use interms of performance.

Could anyone post the solution for this.

[Former Member]

for BDC recordings better not to replace the harcoded values,let them be like the same..

what i say is,the removing of the hardcoded values ignore for the BDC recordings..

[former_member242255]

you can declare it as a constant and use the same..

else

tell us the situation or issue so that we can find some solution.

[Former Member]

I met the issue while working with BDC Programs in case of perform statements where I need to do Hard Coding.

[Sm1tje]

In terms of performance, or in subroutines using PERFORM statement?

[Former Member]

In subroutines using 'perform' keyword.

[former_member242255]

for BDC recordings better not to replace the harcoded values,let them be like the same..

what i say is,the removing of the hardcoded values ignore for the BDC recordings..

[Former Member]

There would not be much of performance issue while using BDC.

It matter's in other cases.

Regards,

Saurabh

[Sm1tje]

Up front, I would agree with Sravan, however, you haven't posted any example of one of the subroutines in which you have used some hard-coding. But normally, when you are for example using screen field names for calling these subroutines, I wouldn't mind doing some hard coding since these screen will 'never' change anyway. It would be a hell of a job correcting all the BDC programs and replacing these with constants.

[Former Member]

Hi,

Its better to declar the constants for hardcoded values, but in case of BDC, there is no much need to declar the constants for field names & all.

Rgds,

Sachin