sap

SAP CRM的前世今生 在我之前的微信公众号文章 SAP的这三款CRM解决方案，您能区分清楚么 我曾经提到过我作为成都SAP研究院CRM产品开发团队的一员工作过一段时间。 我向在SAP德国总部工作的德国老前辈们请教SAP CRM最早的版本是何时问世的，得到的答复是 上世纪末本世纪初 。 作为一个PC游戏迷，我联想到了供我领略众多国内外游戏大作的微软操作系统DOS, Windows 95, 98, 2000, Me和XP, 20年转瞬即逝，如今它们已经远离我们的视线了。 再回到我曾经工作的SAP CRM。每当Jerry在SAPGUI里调试着SAP CRM那些Created字段显示为本世纪初的ABAP代码时，脑子里情不自禁地浮现出曹老板和他神作里的千里马形象: * 同样, SAP的这三款CRM解决方案，您能区分清楚么 里也提到了另一款SAP成都研究院的开发团队参与开发的产品： S/4HANA for Customer Management 1.0 今天(2018年2月28日)，这款产品终于揭开了TA的神秘面纱 : 在SAP成都研究院开发团队和SAP全球其他部门同事们的共同努力下， S/4HANA for Customer Management 1.0 问世了！ SAP CRM On-Premises (下文简称为 SAP CRM )的部分销售和服务功能已经成功集成到了S/4HANA里

I'm currently trying to setup a web-socket server on an SAP application server as a proof of concept. The application which is connecting to the web-socket server is not going to be a UI5 or WebDynpro application but just a middle-ware program running on a headless computer. Following a quick guide, I've setup the push channel and I have an object with the interface methods ON_START , ON_MESSAGE and etc. I'm currently testing the interface using wscat which you can get from npm . When I tried connecting to my service for the first time using wscat I was receiving a HTTP 500 error. I wasn't

I have a problem. I am working on java application server(sap netweaver) with I am using ejb 3.0 So I want to database insert one by one. Because I have too much data and i have to divide data. So I made try test code and it did work but it did not work as I want. I want to create a new transaction for each part and of course at the end method(transaction) should be commit. Sample code is below; package com.transaction.jobs; import javax.ejb.Local; /** * * @author muratdemir */ @Local public interface TestTransactionLocal { public void onStart(); public void insertObject(int i); } and package

I am trying to create an entry in SAP with the functions and structures I got from ABAP. I was referring to this link Creating Purchase Info Record in SAP The same problem happens to me. I could not see the record. When we are checking ERRORS as suggested by the above post.... We got this error.. RFC_ERROR_SYSTEM_FAILURE: THE CURRENT APPLICATION TRIGGERED A TERMINATION WITH A SHORT DUMP. Since there is a short dump, we need to check the transaction code ST22 to check the exact error for the issue. Then we can adjust the calling code according to the dump details. 来源： https://stackoverflow.com

有的时候，SAP标准的OData实现或者相关的工具没有提供我们想记录的日志功能，此时可以利用SAP系统强大的扩展特性，进行自定义日志功能的二次开发。 以SAP CRM Fiori应用“My Opportunity”为例：我们首先在其OData服务CRM_OPPORTUNITY的实现类CL_CRM_OPPORTUNITY_IMPL的构造函数方法CONSTRUCTOR里设置一个值为GET_BADI的动态断点，这样调试模式下，ABAP调试器会自动停在所有出现了GET BADI关键字调用的地方。 通过这个方法，我们很快找到了一个能够放置我们自定义日记记录逻辑的地方：就是代码85行的BAdI定义，CRM_OPPORTUNITY_ODATA_DB. 在SAP标准OData服务实现的读取操作里，每次从数据库调用One Order API读取Opportunity数据后，都要执行这个BAdI. 这是该BAdI执行的调用栈： 事务码SE18，根据我们刚刚找到的BAdI定义创建一个增强实现： 这个增强实现类ZCL_JERRY_ODATA_TRACE里，现在可以编写我们的日志记录逻辑了。 首先创建一个数据库表，用于存放我们的日志记录。为简单起见，我仅仅记录了请求的用户名，请求日期和时间，大家可以根据自己实际需求添加相关字段。 增强代码也很简单： DATA(ls_log) = VALUE zorder

I needed a function to send an email to an ordinary email address and to send on too to an SAP Inbox. I found this function: CALL FUNCTION 'SO_NEW_DOCUMENT_ATT_SEND_API1' EXPORTING document_data = gd_doc_data put_in_outbox = 'X' commit_work = 'X' TABLES packing_list = it_packing_list contents_txt = it_message receivers = it_receivers EXCEPTIONS too_many_receivers = 1 document_not_sent = 2 document_type_not_exist = 3 operation_no_authorization = 4 parameter_error = 5 x_error = 6 enqueue_error = 7 OTHERS = 8. The it_receivers it's filled like this: FREE wa_it_receivers. wa_it_receivers-receiver

I'm trying to use the function module REUSE_ALV_FIELDCATALOG_MERGE to pass the field label in ddic to display in the column header of the alv report. But, that didn't work. If I comment the I_STRUCTURE_NAME = 'TY_YNAH_CUS_OBJ_REQ' line, it give me runtime error state The ABAP program lines are wider than the internal table. But if I uncomment it ,the program still did not work REPORT YALV_TEST. tables sscrfields. type-pools : slis. "CREATE STRUCTURE -1 TYPES: BEGIN OF TY_YNAH_CUS_OBJ_REQ, REQID TYPE YNAH_REQ_ID, REQUESTOR TYPE YNAH_REQUESTOR, BUSINESS_OWNER TYPE YNAH_BUS_OWN, FUNCTIONAL_OWNER

安装SAP在REHL76 系统要按SAP管网的说明配置 具体如下 limits 配置 cat /etc/security/limits.conf|grep -v ^#|grep -v ^$: soft core 65536 hard rss 65536 hard nproc 65536 soft nproc 65536 oradev soft nproc 65536 oradev hard nproc 65536 oradev soft nofile 65536 oradev hard nofile 65536 oradev soft stack 65536 oradev hard stack 32768 oradev hard memlock 8000000 oradev soft memlock 8000000 oracle soft nproc 65536 oracle hard nproc 65536 oracle soft nofile 65536 oracle hard nofile 65536 oracle soft stack 65536 oracle hard stack 32768 oracle hard memlock 8000000 oracle soft memlock 8000000 @sapsys hard nofile 32800 @sapsys