SAP S/4 HANA新变化-SD销售与分销

SAP S/4 HANA新变化-SD销售与分销

 

http://mp.weixin.qq.com/s?__biz=MzAwMjgyMTA4MQ==&mid=2652153152&idx=1&sn=8a2f1e8310c83fa692696a80fab0c53e&chksm=81249bf6b65312e08e953903eb6eec726c01fd328583da1d48976510135a4a69ab2356480617&mpshare=1&scene=5&srcid=1201VWTGVXTbqpToXPgctoCH#rd

 

1、数据库表变化

简化了数据模型：

取消了状态表VBUK, VBUP，状态表相关字段移到了销售对象表中，包括VBAK 、VBAP、LIKP、 LIPS、VBRK。

? Simplification of Document Flow tableVBFA 简化了凭证流表VBFA

? Field length extension of SD documentcategory: Data element VBTYP (Char1) has been replaced by data element VBTYPL(Char4), also: elimination of field VBTYP_EXT (Char4)

? Elimination of redundancies – DocumentIndex Tables 取消了冗余的索引表VAKPA , VAPMA, VLKPA, VLPMA, VRKPA,VRPMA

? Elimination of redundancies – RebateIndex Table VBOX: see simplification item SD Rebate Optimization 取消了返利索引表

 

Each append field must have the same nameand the same data type as it does in the source table, and each one has to beappended to the table-specific status include structure (DDIC structures VBAK_STATUS,LIKP_STATUS,VBRK_STATUS, VBAP_STATUS or LIPS_STATUS). Only then will the field beconsidered by the automatic data conversion from VBUK to VBAK/LIKP/VBRK andfrom VBUP to VBAP/LIPS, as well as by read function modules that can be used toreplace direct SELECTs to the deprecated status tables VBUK/VBUP.

 

2、KONV表已被PRCD_ELEMENTS取代

 

Business documents within the SAP BusinessSuite such as the sales order or the purchase order used to store the pricing result in the databasetable KONV. In SAP S/4HANA, table KONV was replaced in its data persistency role by the new table PRCD_ELEMENTS. However, KONV is and can still be used for data declarationpurposes. It still defines the structure of the pricing result within the application coding. The content of KONV is transferred to PRCD_ELEMENTS when moving to SAP S/4HANA;

 

3、GTS

SD的外贸功能已被更家完整的GTS(国际贸易服务)所取代。GTS原来是对立的外贸模块，现在已经完整集成到hana s/4 1511版本中。

Currently there are two software services for international tradetransactions: Foreign Trade and Global Trade Service. Foreign Trade is part ofthe normal SD. GTS is an external service that can be installed on anadditional instance. With SAP S/4HANA on-premise edition 1511, the ForeignTrade functionality will be not available because SAP Global Trade Services(GTS) is the successor for the business requirement. For Intrastata customer canleverage functionality within SAP S/4HANA, on-premise edition 1511. Forthe functionalities Letter of Credit; LegalControl andPreference Management the functionalities based on SAP Global Trade Services(GTS) can be used. SAP GTS can be natively integrated with S/4HANA. Additional functionalitiesfor Import- and Export Management are available with SAP GTS.

 

4、Optimization of SD Rebate Processing for TPM Customers

Customers, who will integrate theirexisting CRM TPM scenario with S/4HANA,still have to use SD Rebate Processing, even though a successor is alreadybeing provided by Settlement Management (cp. simplification item SD Rebate Processing replaced bySettlement Management).

For those customers, the existing SDRebate functionality is optimized with regard to the data base footprint.

For this purpose, from a technicalstandpoint, the rebate index table VBOX is not available.

Please note, that also TPM customers are not able to create new rebate agreements in S/4HANA or extend

existing ones (cp. simplification item SD Rebate Processingreplaced by Settlement Management). However,for the TPM process this is not necessary at all, since for this businessprocess rebate agreements are created by CRM TPM.

 

Transaction not available in SAP

S/4HANA on-premise edition 1511

VBO1 Create Rebate Agreement

VB(D Extend Rebate Agreements

 If the customer is using the extended SD rebateprocessing a rebuild of the S469 content is required

after the upgrade.

· The customer has to maintain new customizingsettings.

SAP Note: 2200691

实际的情况是创建返利协议：VBO1，仍然可以使用。

未来的趋势，应该是CRM功能会集成到HANA中。

 

5、SD Rebate Processing replaced by Settlement Management

In general, SD Rebate Processing is not availablewithin SAP S/4HANA. The functional equivalent in SAP S/4HANA is SD Rebate Processingis Settlement Management.

However, there is one exception. CRM TPMcustomers can still use SD Rebate Processing for their business process, buthave to adapt to a SAP S/4HANA optimized solution (cp. simplification itemOptimization of SD Rebate Processing for TPM Customers).

 

In SAP S/4HANA, SettlementManagement replaces SD Rebate Processing, which means that existing rebate agreementscan only be processed up until the end of the validity date of the agreementand must then be closed by a final settlement. New agreements can only becreated based on condition contracts. Therefore, the corresponding transactioncodes VBO1 resp. VBD for the creation of rebate agreements is not available anymore.

SAP Note: 2226380