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的原創文章,請關注公眾號"汪子熙":
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/24475491/viewspace-2716194/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- SAP S/4HANA OData Mock Service 介紹Mock
- SAP S/4HANA Cloud SDK 入門介紹Cloud
- SAP S/4HANA extensibility擴充套件原理介紹套件
- SAP S/4HANA New Simplified Data Model (NSDM) 模型介紹模型
- SAP S/4HANA CDS View的訪問控制實現:DCL介紹View
- SAP S/4HANA Cloud 系統整合的一些場景介紹Cloud
- SAP CRM WebClient UI的Delta處理機制介紹WebclientUI
- SAP HANA,S/4HANA 和 SAP BTP 的辨析
- SAP S/4HANA Cloud 上 in-app 和 side-by-side 兩種擴充套件方式的介紹CloudAPPIDE套件
- Generate Distribution Model from SAP ERP to SAP EWM in SAP S/4Hana
- 一些SAP Partners能夠通過二次開發實現打通C/4HANA和S/4HANA的方法介紹
- SAP S/4HANA key user tool extensibility原理
- SAP S/4HANA 2020安裝實錄
- Spring的Factories機制介紹Spring
- SAP S/4HANA中的採購簡化
- linux漏洞緩解機制介紹Linux
- Flink 類載入機制介紹
- SAP R/3,SAP ECC 和 SAP S/4HANA 的聯絡和區別
- SAP ECC,SAP HANA和SAP S/4HANA之間有什麼區別?
- SAP Cloud for Customer 如何直接消費S/4HANA APICloudAPI
- SAP BOPF介紹
- SAP S4CRM 1811 服務訂單API介紹API
- 簡單介紹python的垃圾回收機制Python
- 給某個 SAP S/4HANA 使用者分配 Business Role
- SAP ABAP Append structure 介紹APPStruct
- SAP Java Connector 元件介紹Java元件
- OkHttpClient原始碼分析(三)—— 快取機制介紹HTTPclient原始碼快取
- 資料庫系列:MySQL InnoDB鎖機制介紹資料庫MySql
- Flink狀態管理和容錯機制介紹
- jQuery的事件機制,事件物件介紹,外掛機制,多庫共存,each()jQuery事件物件
- 如何使用Key User Tool擴充套件SAP S/4HANA Fiori UI套件UI
- SAP S/4HANA Material Fiori應用的搜尋實現原理
- SAP S/4HANA裡extension include view和extension view的區別View
- SAP S/4HANA Customer Management(CRM)模組的Partner模型設計模型
- SAP S/4HANA: 一條程式碼線,許多種選擇
- 哲訊分享:你不知道的SAP S/4HANA Cloud功能!Cloud
- SAP工作流介紹之ABAP Business Workflow介紹
- SAP S/4 HANA 1809簡介