By default after a service order is saved, there is a distribution lock set, which prevents you from editing this order in status transferring. Click edit button you will meet with error message below until it has successfully been transferred.
In blog Regarding Service Order distribution lock and status I introduce the step how to avoid this distribution lock. Nevertheless there is still BDOC and an inbound CSA queue automatically generated. The purpose of CSA queue has already been well explained by Rohit Sharma in this thread:
In case you really would like that for a given transaction type, no BDOC and inbound CSA queue should be generated for whatever reasons, you can suppress this behavior by enhancement on function module CRM_ORDER_SAVE_OW.
In this function module, the BDOC and CSA queue will be created by function module CRM_ORDER_UPLOAD_SINGLE only when ALL the THREE condition in IF are fulfilled. The second condition, lv_send_bdoc is controlled by a switch.
So the solution would be: Create a new enhancement on function module CRM_ORDER_SAVE_OW:
Insert one line below:
Suppose you would like that for transaction type ZSRV, no BDOC should be generated, then the source code of run method:
METHOD run.
DATA lv_process_type TYPE crmt_process_type.
LOOP AT it_object_list ASSIGNING FIELD-SYMBOL(<guid>).
CALL FUNCTION 'CRM_ORDERADM_H_READ_OW'
EXPORTING
iv_orderadm_h_guid = <guid>
IMPORTING
ev_process_type = lv_process_type
EXCEPTIONS
admin_header_not_found = 1
OTHERS = 2.
CHECK lv_process_type = 'ZSRV'.
CALL FUNCTION 'CRM_ORDER_SET_NO_BDOC_SEND_OW'
EXPORTING
iv_guid = <guid>
iv_flag = 'N'.
ENDLOOP.
ENDMETHOD.
Now the lv_send_bdoc will be set as false in the runtime according to the switch you set in enhancement, as a result no BDOC and inbound queue will be created any more.
Now after service order is saved you can still continue to edit.
Update on 2017-01-23
I am told by my colleague today that there is a better solution to leverage BAdI CRM_DATAEXCHG_BADI:
要获取更多Jerry的原创文章,请关注公众号"汪子熙":
相关推荐
CIP(Customer Interaction Platform)Inbound Queue 是一种关键的IT系统组件,主要处理客户交互过程中的数据流动。本文将深入探讨CIP Inbound Queue的问题发现、监控和处理策略。 首先,我们关注的是“LI-CRM ...
- **LS Inbound**: 目标系统接收IDOC并生成销售订单,`BORDE`是创建销售订单的IDOC类型,确保正确处理装运点确认以避免数量确认错误。 - **KU Outbound**: 销售订单被创建后,系统将输出消息回写到采购订单进行...
在SAP PI(Process Integration)系统中,配置和开发涉及一系列步骤,确保数据和服务在不同系统间顺畅交互。本文将详细解析从SLD到测试代理类的整个过程,并解决sxi_monitor不记录错误消息的问题。 首先,我们从SLD...
- **操作路径**:在SAP系统中,执行完下达命令后,系统通常会自动提示保存,或者手动点击工具栏上的保存按钮完成保存动作。 - **注意事项**:检查订单的所有信息是否准确无误,避免因数据错误而导致后续问题。 ##...
选择好后,点击“保存”,接着选择编辑,并在“Type”中选择“CATT”(Cross Application Test Tool),这是SCAT的另一种形式,专用于创建和执行测试脚本。 接下来,你可以开始录制屏幕操作。点击“记录”按钮,...
在SAP PI(Process Integration)系统中,消息保留设置是一个重要的管理方面,它涉及到系统如何处理和存储消息。本文将详细解释AEX 7.5版本中关于消息保留的参数设置,这对于理解如何管理和优化SAP PI的性能至关重要...
SAP Java Connector (SAP JCo) 是一个关键的中间件技术,它的主要功能是为SAP组件和Java应用程序提供通信桥梁。SAP JCo允许双向通信,即 inbound calls(Java调用ABAP)和outbound calls(ABAP调用Java),这极大地...
SAP WM 在拣货支持方面,只能按单个订单拣货,或者将订单合并进行拣货,缺乏更多种灵活的拣货方式,如批量拣货,按车拣货,散装拣货,按灯拣货等等。 WM 60 Cycle Count 盘点冻结库存 SAP WM 在盘点冻结库存时,...
传统的采购订单和申请单事务得以延续,确保了系统升级后业务流程的连续性,避免了学习新系统的额外成本。 #### Reports for Inclusion of Derivative Financial Instruments in Balance Sheet 衍生金融工具纳入资产...
- 编写ABAP程序处理IDoc的生成和接收,包括 inbound 和 outbound 过程。 - 使用ST05事务码监控和调试IDoc通信。 5. **IDoc在业务流程中的应用**: - 供应链管理:如供应商门户集成、订单处理和库存同步。 - ...
SAP Process Orchestration The Comprehensive Guide, 2nd Edition SAP流程编制综合指南 1 Introduction to SAP Process Orchestration 1.1 Historical Overview and Evolution 1.1.1 SAP Process Integration ...
业务伙伴接收数据后,又通过相似的流程将数据送回SAP系统,最终在SAP系统中生成应用文档。 三、IDOC结构 IDOC包含了多个段(segment),而每个段又包含多个字段。IDOC共有三种类型的记录:一条控制记录,一个或多个...
SAP Java Connector (SAP JCo) 是JAVA与SAP相互通信的中间件组建。该组建支持双向通讯模式(inbound calls 和 outbound calls )。JCo支持Connection Pools和Direct两种方式的连接。直接连接需要开发者来控制连接的...
SAP SNC 技术文档包含了对SAP SNC (供应链网络通信) 中的业务附加程序接口(BAdI)的详细列表和说明,这些BAdI允许技术人员为SNC组件自定义和扩展功能。BAdI是SAP中用于实现扩展点的一种技术,以便于开发人员能够按照...
SAP Java JCo 3.1.7 ... The SAP JCo supports both communication directions: inbound Remote Function Calls (Java calls ABAP) as well as outbound Remote Function Calls (ABAP calls Java). 更新于:230309
SAP IDOC(Intermediate Document)是SAP系统中用于企业间数据交换的一种标准接口,它允许SAP系统与其他系统(如非SAP系统)进行数据交互。以下是对SAP IDOC配置的详细解释: 1. **SAP-Inbound Configuration** -...
### SAP PI 异步接口创建步骤详解:MB PI 九恒星到SAP的POS过账及冲销接口 在企业级应用集成中,SAP Process Integration (SAP PI) 是一个非常重要的工具,用于实现不同系统之间的数据交换与集成。本文将详细介绍...
SAP JCo不仅支持Java向ABAP(SAP的应用服务器编程语言)发起的请求(即inbound calls),也支持从ABAP向Java发起的请求(即outbound calls),这种双向通信的能力极大地扩展了SAP系统的集成能力。 #### SAP JCo的...