ABAP Coding change impact info - Linux to Windows

[former_member558419]

All,

We are having ECC5 system that currently runs on Linux. But we are migrating the OS to Windows. So my question is what will be coding impact related to custom programs after migrating into Windows from Linux.

Please clarify below points.

1. Programs have application server path has hardcoded with linux separation ie //temp/tmp like that is this having impact if move to Windows?

2. SFTP commands like PUT, LS, CD , whether these will work when move to windows?

3. Currently some outbound files that encrypted in Linux level before sending, is the encryption will work while moving to Windows

4. Any other points in which code change is needed? like any ABAP syntax which we have written in Linux may not work in windows that need a change.?

Thanking you.

Please reply

[Sandra_Rossi]

Good question, no idea whether someone has defined a checklist.

Yes you must test 1, 2 and 3.

+ SXPG stuff (SXPG + jobs executing OS commands)

+ printing

and so on.

[former_member558419]

Thanks Sandra,

Can you please explain more on what kind of impact on printing?

Thanks

[Sandra_Rossi]

I was thinking of Linux/Unix printers (access method in SPAD). It's something I would test just because there might be an impact, but I'm not expert.

[FredericGirod]

You should have define an external print server, so it is only a connection

Did you check for usage of SM69 ?

Did you check all the Filename as also a windows entry (transaction File) ?

[DominikTylczyn]

Hello ar.subramony

Changing the operating system from Linux to Windows should have zero impact on ABAP programs, unless problems have been asked for. Let me explain

ABAP programming as such is OS agnostic, i.e. it doesn't depend on the underlying operating system. An ABAP program is compiled to byte code and executed by a kind of virtual machine. The concept is very similar to that of Java. In short, ABAPs will run no matter what OS you have.

Application server paths must not ever be hardcoded in ABAP programs. Logical paths defined in the SFILE transaction should be used instead.

Operating system external commands should not be called directly. The commands should be defined in SM49 or SM69 and they should be used in ABAP programs by calling SXPG_COMMAND_EXECUTE module.

If you stick to ABAP programming good practices then switching the operating system will be a breeze, at least from ABAP programming perspective.

Naturally, the switch does have an overall impact on the system and it has to be tested.

Best regards

Dominik Tylczynski

[S_Sriram]

Hi Ram,

1. First check the SAP ECC 5 supported OS / DB, as per SAP PAM SAP ECC 5 end of extended maintenance 31/03/2013, also the latest Windows OS will not support ECC 5

2. You have to upgrade the existing SAP ECC 5 to ECC 6 and then do the migration to Windows OS. Could you share the current OS/DB version details?

3. You can create the SAP sandbox system either from production or development system and do the upgrade & migration as per the SAP guido.

Regards

SS