SAP S/4HANA Cross Selling机制介绍
This step-by-step document mainly follows the guide mentioned in SAP help:
(1) Create custom condition table via Sales and Distribution->Basic Functions->Cross Selling->Define determination procedure for cross selling->Create Condition Tables:
For my requirement, I would simply would like to make new material determined by existing material entered in Sales order line item plus customer as sold to party, so I only choose two fields: Customer and Material.
Use 503 as condition table ID and generate it. Write down the name of this condition table: KOTD503 for later usage.
(2) Create a new Access sequence Z001, and assign the condition table created previously to it.
(3) Create a new condition type ZS01 and assign the access sequence created in step two to it.
(4) Create a new determination procedure ZS0001 based on Usage D ( Material Determination ), Application VS (Cross Selling) and assign the condition type ZS01 created in previous step to it.
(5) Define customer procedure for cross selling:
B for Cross selling:
And assign it to Sales document type OR:
(6) Create a new Cross Selling profile Z00001, and assign the cross selling procedure created in step 4 to it.
Assign this profile to a given combination of Sales Organization, Distribution Channel and Division, plus Cross selling procedure as below.
(7) Create Cross selling condition record via menu path: Sales and Distribution->Master Data->Products->Cross Selling
Use the condition type created in step 3, ZS01:
Suppose I have three products with ID 11, 13 and 14. When 11 is entered in Sales Order line item, I would like that 13 and 14 are automatically determined for cross-selling purpose.
As a result I maintain the following condition record for material 11 as base:
Now it’s ready for test. Create a Sales order with type OR, maintain 11 as line item and press enter key, another two materials 13 and 14 are determined and displayed in popup as expected.
Set a breakpoint on condition determination entry point function moduleSD_COND_ACCESS to observe how they are determined.
Based on the passed application VS ( cross selling ), ZS01(condition type) and sales area data,
the condition records maintained via conditiona table KOTD503(created in step 1) are retrieved.
Alternatively you can also switch on material determination trace for observation purpose.
要获取更多Jerry的原创文章,请关注公众号"汪子熙":
相关文章
- SAP UI5 Form 和 Simple Form 的设计规范
- SAP UI5 应用中的 sap.ui.require 使用场景
- 关于 SAP UI5 所有控件的共同祖先 - sap.ui.base.ManagedObject
- SAP UI5 sap.ui.Device.media.initRangeSet 方法的单步调试
- SAP UI5 XML 视图在实例化时就已经确定了 BindingSyntax 的实现版本了
- SAP UI5 Smart Table 和 Smart Filter Bar 的联合使用方法介绍
- 81. 使用 SAP ABAP Memory Inspector 对应用程序消耗内存进行检测时常犯的错误
- 关于微软 Edge 浏览器无法访问笔者 SAP UI5 教程示例代码的问题
- SAP MM 物料移动平均价的修改历史(续)
- 关于 SAP UI5 接口 sap.ui.core.IAsyncContentCreation 的问题讨论
- 安装SAP,Linux获台前瞻未来(linux安装sap)
- SAP 锁机制详解编程语言
- SAP中如何创建parameter ID详解编程语言
- SAP ALV demo—-自用(新显示函数,不用自定义GUI状态)详解编程语言
- SAP ABAP常见错误记录之一:In RFC modules, only parameters with pass by value are allowed (参考参数在更新任务中不允许)详解编程语言
- SAP用户权限控制设置及开发详解编程语言
- sap bw详解编程语言
- SAP财务清账原理与方式详解编程语言
- SAP SHD0的详细简介详解编程语言
- SAP在Linux上安装(sap安装linux)
- 系统SAP在Linux系统上的开启之旅(sap启动linux)
- SAP vs Oracle:差异点与解析(sap和oracle的区别)
- Oracle与SAP在仓储领域的联姻(仓库oracle和sap)
- 系统Oracle公司收购SAP系统开启新的商业时代(Oracle公司sap)