Error log for BBP_LOCATIONS_GET_ALL after SRM 5 upgrade

[Former Member]

Hello,

We recently upgraded our EBP 3.5 to SRM 5.0 with R/3 46C (classic). As part of the post-upgrade activities we ran the report BBP_LOCATIONS_GET_ALL. We looked at the SLG1 and found a message with the following:

_________________________________________________________

The region MOW is not defined for country RU.

Error creating Location AMOW system: TN2CL100

_________________________________________________________

I believe that the system is looking to see if there is a region MOW (moscow?) for the country RU (Russia) - before converting it into a location.

Has anyone encountered this problem?

I am not sure if the error is indicating that the R/3 plants are not ISO standard?

Any help would be greatly appreciated.

Thank you very much.

[former_member184214 · Accepted solution]

Hello,

I think that your problem is that you have in backend defined in address of AMOW region MOW.

Check in SRM IMG > SAP WAS > General Settings > Set Countries if you have MOW defined for RU.

HTH

Gordan

[Former Member · Accepted solution]

Hi Gordan,

You have been a tremendous help. I looked at the R/3 Country and Regional code and apparently R/3 uses a customized region code. And the BBP_LOCATIONS_GET_ALL is very picky about the data apparently.

We are going to just ignore the those "plants" that were not transferred.

Thank you.

[Former Member · Accepted solution]

Hi Jay,

you can create your customised region codes in EBP as well which will allow you to transfer the plants.

Regards

Chris