Account Assignment descriptions are blank

[Former Member]

Hi,

SRM 7.0 , Classic scenario    

Account assignment descriptions - CC / WBS & GL Account Description are blank during the SC creation. This issue happens only in one environment and in all other environments the same is working correctly.

Any light on this issue would be appreciated.

Regards

Sudhakar

[Former Member · Accepted solution]

Hi Sudhakar,

Did you check the IMG config for account assignment?

If not please check from below IMG path

SPRO > SRM > SRM server > cross application basic settings > Account assignment >

--> Define G/L acct for product category & acct.assignment category

Also, it is working fine in other environments you just compare the same with other systems.

Remember, Account assignment category attribute needs to be maintained / defaulted for user / Org. Unit in order to get the category list in shopping cart account assignment category tab.

Regards,

Govardhan

[Former Member · Accepted solution]

Hi Govsrdhan,

I think you didn't understand my query properly. I know the above config's usage and its functionalities. My issue is CC Description and GL Description is not getting updated. ( For ex : CC - 80150 is updated where as its description - ' Consult support' is not updated and similarly for GL ). There are so many notes available for this issue but i could not find relevant one for SRM 7.0.

Regards

Sudhakar

[Former Member · Accepted solution]

Hi Sudhakar,

Which SRM support pack level / EHP level your are? Our systems are 7.0 EHP 1 and GL / Cost centers descriptions are populating for us without any issues.

Regards,
Govardhan

[laurent_burtaire]

Hello,

check if translation is OK for your account assignment descriptions.

Regards.

Laurent.

[Former Member]

Hi Sudhakar,

Which system you are having such issue? Are you guys recently upgraded? If you are having issue in Dev or QA system while Production is fine then there may be chances that some enhancements or notes you are applying to fix something may have caused the issue.

Thank you

Ritesh