ECC to S4 conversion, how to identify call transaction in custom code

[r010101010]

Hi,

I am currently working on a project where we are analysing the impact of the migration of ECC EHP4 to S/4HANA 1909 on the existing custom codes.

I have launched the report ATC with the variant S4HANA_READINESS_1909 which lists the impact on the custom code as suggested by SAP. Below is a section of the list of notes and descriptions for the S4.

From what I have understood, any call transaction to XD01 will be redirected to the BP transaction. If there is any BDC call in existing codes, this will result in some kind of error on S4. My issue is that I am not able identify individual BDC call from the ATC report, so i am not able to estimate the code adaptation phase. I really do not want to perform a code scan with the key words 'CALL TRANSACTION' or 'USING bdcdata OPTIONS'.

My question is : how can I identify all BDC call transaction in existing custom code ?

Thanks in advance for your help.

Deenesh

[BaerbelWinkler · Accepted solution]

Hi Deenesh,

I recently also ran S/4HANA readiness checks for our Z-code (finding some interesting stuff while doing so). In order to sift through the results more easily than in the ATC-transaction, I downloaded the results with all possible fields into Excel. It's then possible to filter e.g. programs affected by "business partner" to get a list of affected programs:

This may obviously need to be refined for other cases by for example filtering on referenced object type for "TRAN".

Hope this helps!

Cheers

Bärbel

[r010101010 · Accepted solution]

Hi Bärbel,

Thank you very much for your reply. Yes this is what I was expecting, but I dont have this control in the report that I got from ATC remote run.

I my case the client did the run on their system and in fact i received the extract in excel, but it does not contain any check either on the object TRAN nor the note 2226131 !!

I will revert back to the client to check the issue with the ATC run, thanks again for the reply

Regards,

Deenesh.

[BaerbelWinkler · Accepted solution]

r010101010

Deenesh - either there are no cases where one of the then obsolete TCodes is used for BDC (somewhat unlikely I guess?) or there may have been a restriction on the objects looked at via e.g. an object set or package selection. Do you happen to know a program which should have been found via the check but wasn't? This might help to narrow down the reason - if any.

[r010101010 · Accepted solution]

Hi Bärbel,

I checked the restriction on the package and we are analysing all objects in the packages Y* and Z*.

And I did what you proposed, there are in fact a few call transaction with BDC in the system but there must be some configuration missing on the ATC system to check all the controls.

Since we are currently in a planning phase and trying to estimate the impact of S4 on the custom codes, I went for a code scan with 'CALL TRANSACTION' and identified all the calling programs. I am then checking manually if those transactions still exist on S4, which in my case, most of them are still available on S4.

As recommended, we will have to launch ATC after the system conversion to correct the blocking points.

Thank you very much for your guidance,

Regards,

Deenesh