dynamic modification in customer report

[Former Member]

hi,

i have a specific requirement to be done . (i.e) i have to modify possible obsolete statement in ECC 6.0 into non-obsolete by automatically . which i can achieve using insert report from itab . my query is when we try to access the program of client manually then it ask for a transport request number but when i modify the the automatically it doesn't ask for transport request .

so plz tell me can i proceed with the modification r i have do some thing else.

[ThomasZloch]

Well, you have to include the changed objects explicitely in a transport request using function modules, please search the forums, this has been frequently discussed.

I'm interested in how you automatically replace obsolete statements with valid ones, would you disclose?

Thomas

[Former Member]

@Thomas : I am working something similar requirement, to change the Non-unicode syntaxes to unicode syntax by a program. Be it OPEN DATASET, DESCRIBE FIELD etc. We are doing this using the READ REPORT, INSERT REPORT, SYNTAX CHECK and SCAN ABAP SOURCE syntaxes. And the rest is all string operations by parsing the string to tokens for analyzing.

@Rahul : To include the modifications to a transport request, you can use the FM's,

TR_INSERT_REQUEST_WITH_TASKS - Create new Transport Request

TRINT_OBJECTS_CHECK_AND_INSERT - Attach the objects to the transport request.

Regards

Ranganath

[Former Member]

hi,

thnx for the function module .

i have an another issue in the automation process of Unicode error . The respective change of popup_to_confirm_with_message is popup_to_confirm but the problem in the DIAGNOSE_OBJECT parameter in the function .

In old funtion module diagnose is as char and in new one we need to maintain via se61 tcode .

is there any way through which i can make these above things automatically .

[Former Member]

Worked on the very same requirement. But we decided to go with concatenation of diagnose object parameters if passed as string/constant in the old Fm as text parameter passed with the new FM. As it is just the matter of the information being presented, as functionality is nowhere affected. But if they are passing the se61 object, then we are not auto-remediating the FM.

Regards

Ranganath