为什么运行时 KOFAX SAP 功能模块 Z_DICOM_STORE_USING_FB60_FB65 未填充？
我们已将开发 SAP 系统从 ECC6 SPS3 升级到 ECC6 SPS5。
SAP 外部的应用程序（KOFAX - SAP 认证产品）将发票图像和发票数据传递到 SAP 系统。然后，它调用功能模块 Z_DICOM_STORE_USING_FB60_FB65（由 KOFAX 提供），以便将图像存储在 SAP Content Server 上并触发工作流程。
在SAP系统升级之前，这有效，现在不行了。 check_and_add_delimiter（子例程池 SCMS）中引发异常，该异常是从功能模块 SCMS_ARCHIVE_INFO_GET 有效调用的。
引发异常是因为当调用类方法 CL_GUI_OBJECT->CLASS_INIT 时，标志：
- GUI_IS_RUNNING
- ACTIVEX
- JAVABEAN
- WWW_ACTIVE
设置为空白值。
当从 KOFAX GUI 启动进程时会发生这种情况。如果我从事务 SE37 运行 Z_DICOM_STORE_USING_FB60_FB65 并使用相同的数据填充结构，则会存储图像并触发工作流程。
请您建议为什么程序运行时没有填充标志？
谢谢。
We have upgraded our development SAP system from ECC6 SPS3 to ECC6 SPS5.
An application external to SAP (KOFAX - a SAP certified product) passes an invoice image and invoice data to the SAP system. It then calls the Function Module Z_DICOM_STORE_USING_FB60_FB65 (supplied by KOFAX) in order to store the image on the SAP Content Server and trigger a workflow.
Before the upgrade of the SAP system, this worked, now it does not. An exception is raised within form check_and_add_delimiter (subroutine pool SCMS) which is effectively called from function module SCMS_ARCHIVE_INFO_GET.
The exception is raised because when class method CL_GUI_OBJECT->CLASS_INIT is called, the flags:
- GUI_IS_RUNNING
- ACTIVEX
- JAVABEAN
- WWW_ACTIVE
are set to blank values.
This happens when the process is kicked off from the KOFAX GUI. If I run Z_DICOM_STORE_USING_FB60_FB65 from transaction SE37 and populate the structures with the same data, the image is stored and the workflow is triggered.
Please can you suggest why the flags are not being populated when the program runs?
Thanks.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
这是您其他帖子的“技术副本”。同样，问题很清楚 - “KOFAX GUI”似乎使用 RFC 连接来调用功能模块，但功能模块随后使用一些其他不需要 RFC 连接的东西，但另一个需要成熟的 SAP GUI结束，因为它尝试访问 SAP GUI 属性。我不喜欢 CMS，所以我无法帮助您弄清楚为什么在升级过程中发生了变化......
This is a "technical duplicate" of you other posting. Again, the issue is clear - the "KOFAX GUI" appears to use a RFC connection to call the function module, but the function module then uses some other stuff that requires not a RFC connection, but a full-blown SAP GUI at the other end because it tries to access SAP GUI attributes. I'm not into CMS, so I can't help you to figure out why this was changed during the upgrade...
对于大多数情况，普通的 RFC 连接就足够了，仅当您尝试在功能模块内执行 BDC 时才需要 SAP GUI（例如“直接过账”）。既然你说它之前有效，我只能假设情况并非如此。
不会是图片上传的时候出错吧？也许升级对内容服务器配置造成了一些影响？您可以运行一个针对内容服务器的测试程序。
For most scenarios a normal RFC connection is sufficient, SAP GUI is only required if you try to execute BDC within the function module (e.g. for "direct posting"). Since you say that it worked before I can only assume that this is not the case.
Could it not be that the error happens during the upload of the image? Maybe the upgrade did something to the content server configuration? There is a test program for the content server that you can run.
我们的一位开发人员解决了这个问题。他给我的答案是：
This was resolved by one of our develpers. The answer he gave me was: