从 SAP Portal 调用时,SCMS_AO_URL_READ 返回通信错误

发布于 2024-08-20 21:41:30 字数 651 浏览 6 评论 0原文

我们已将开发 SAP 系统(ECC6 和 SAP Portal)从 SPS3 升级到 SPS5

现在,当用户登录 SAP Portal 并运行定制的 Java Web Dynpro 屏幕(该屏幕又调用 SAP 标准功能模块 SCMS_AO_URL_READ 以检索 UWL)时,会返回异常。

当从SAP ECC系统手动调用功能模块SCMS_AO_URL_READ(通过从SAP GUI运行事务SE37)并传递相同的参数时,不会返回异常。

调查显示,当调用目标SAPGUI的SAP标准功能模块RFC_PING时,会发生故障(调用顺序为SCMS_AO_URL_READ -> SCMS_DOC_URL_READ -> SCMS_URL_GENERATE - >执行location_from_lca->SCMS_FE_CHECK_REG_SERVER->SCMS_FE_CHECK_GUI)。例外情况 正在返回“通信失败”。

此错误不会在修补前或在我们尚未修补的相同系统中发生。

有什么想法为什么参数没有被自动填充吗?

谢谢。

We have upgraded our development SAP system from (ECC6 and SAP Portal) from SPS3 to SPS5.

Now when a user logs onto the SAP Portal and run a bespoke Java Web Dynpro screen (which in turn calls SAP standard Function Module SCMS_AO_URL_READ in order to retrieve a UWL), an exception is returned.

When the Function Module SCMS_AO_URL_READ is manually called from the SAP ECC system (by running transaction SE37 from the SAP GUI) and the same parameters are passed, no exception is returned.

Investigation has shown that the failure occurs when SAP standard Function Module RFC_PING for destination SAPGUI is called (the call sequence is SCMS_AO_URL_READ -> SCMS_DOC_URL_READ -> SCMS_URL_GENERATE -> perform location_from_client -> perform location_from_lca -> SCMS_LOCATION_GET -> SCMS_FE_CHECK_REG_SERVER -> SCMS_FE_CHECK_GUI -> RFC_PING). The exception
'Communication failure' is being returned.

This error did not occur pre-patching, or in an identical system that we have which has not been patched.

Any ideas why the parameters are not being automatically populated?

Thanks.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

琉璃繁缕 2024-08-27 21:41:30

经过进一步调查,我们发现该问题是在用户有权访问授权对象S_RFC_ADM时引起的。

我还不知道为什么会这样(特别是 SAP 授权应该是累积的并且没有排除),但这绝对是问题所在。

After further investigation we found that the issue is caused when the user has access to the Authorisation Object S_RFC_ADM.

I do not know why this is yet (especially as SAP authorisations are supposed to be accumulative and not have exclusions), but that is definitely the issue.

鹤舞 2024-08-27 21:41:30

我不知道所涉及的功能模块的详细信息,但目的很明确 - 程序想要确保存在“真正的”SAP GUI,但显然当您在 WebDynpro 世界中时情况并非如此。 RFC 目标 SAPGUI 是一个“虚拟”目标,它始终“返回”到执行程序的用户会话的 GUI 实例。我建议创建 SAPnet 消息并直接询问 SAP。

I don't know the details of the function modules involved, but the purpose is clear - the program wants to make sure that a "real" SAP GUI is present, and obviously that's not the case when you're in the WebDynpro world. The RFC destination SAPGUI is a "virtual" destination that always points "back" to the GUI instance of the user session executing the program. I'd recommend creating a SAPnet message and asking SAP directly.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文