Skip to main content

S4HANA - Simplification List in 1709 Sales


This Blog will emphasis on Simplification of S4HANA  Logistics.



Sales:-



  • Advanced Order Processing and Billing for Contractors to the public sect :  This Functionality is completely Obsoleted and No Improvement available in this Area

  • Billing Document Output Management :  BRF + is new advancement in this area

  • Business Role Internal Sales Representative : New BP role is available for Internal Sales Representative.

  • Credit Management : This Functionality is not available and replaced with SAP FSCM Credit management.

  • Data Model Changes in SD Pricing : Changes to the existing Functionality such as new Table PRCD_ELEMENTS has to be used for KONV

  • ERP SD Revenue Recognition :  this Functionality is No Longer Available and is replaced with Revenue Accounting and Reporting. 

  • Foreign Trade : This Functionality is replaced with  GTS and International Trade

  • Operational Data Provisioning : This Functionality is no longer Available and it replaced with SD Analytics ( approach based on ODATA and CDS)

  • Optimization of SD Rebate Processing for TPM Customers:  Settlement Management is the Proposed Solution

  • Sales Activities : This Functionality is Completely obsoleted in S4HANA and a equivalent is existing in CRM Onpremise

  • SD Complaint Handling : this Functionality is obsoleted and SAP recommends to use SD Standard Complaints Handling through CMP_PROCESSING

  • SD Rebate Processing replaced by Settlement Management : SAP Condition Contract and Settlement Management

  • SD Simplified Data Models:  There are few Changes to existing Data tables



  • VBFA - Indirect Docflow Relationships : Changes to the File STUFE - This field has been Re-introduced in 1709

  •  





Labels:

Comments

  1. AnonymousApril 21, 2020 at 11:11 AM

    Kindly update blog with 1809 and 1909 as welll

    ReplyDelete
  2. UnknownApril 22, 2020 at 7:37 AM

    Thank you for providing very good information

    ReplyDelete

Post a Comment

Popular posts from this blog

SAP PM/CS / EAM : Refurbishment Process

Refurbishment A refurbishment order is a standard Maintenance Order type. In customizing for order, we first create an order type ( such as PM04) In the configuration we have to create a new order type in OIOA and activate this for Refurbishment process. Process flow: Business process steps 1. Damaged equipment/ spares if can be repaired will be done by the PM order of type PM04 2. Equipment/Spares needs repairing should have the item code if it is serialized item then with the serial number. 3. Item should have the valuation type for repair category too. 4. Create PR through refurbishment order for repair of the item with split valuation type of repair. Proper G/L codes and order for the repair indent should be provided in the indent 5. After approval of the requisition, the requisition and item should be send to the stores/Purchase section for further actions. 6. Stock will get updated after MIGO of the item 7. The activity type cost
2 comments
Read more

TO MAKE INACTIVE CONDITION ACTIVE IN SAP

This blogger contains details on how to set an INACTIVE CONDITION  to ACTIVE while processing Sales Order content: 1.  BUSINESS REQUIREMENT Due to some legal restrictions in Russia, Russia Local Plant cannot hold any stock for the material and hence it is non valuated which means the Standard Price is Zero ( 0 $ ) The stock will be replenished from another company code and we used our Standard Third Party process  in which PR is created which will be converted to PO and when we do GR, the Standard Price of that plant is calculated in the GR. The baseline pricing structure is mapped in such a way that VPRS is calculated from the Material master and on which 15% markup is added as base price. Since the Cost price in VPRS condition is Zero Markup calculated on VPRS will be obviously calculates to Zero and both conditions were set as INACTIVE as per the condition properties 2.  CREATE SALES ORDER we will create a sales order for a material, whose standard Price
3 comments
Read more

S4HANA-Project Systems Operative Indicators in WBS- CJ20N

  Use and Purpose of Operative Indicators in WBS elements When a customer Requests for ATO or ETO process where we create a Project with Integration between SD and PS ( project systems) As a First step we create a Project in CJ20N and under the Project we will Create Multiple WBS elements which has to be set for Operative Indicators This article deals with Operative Indicators in WBS elements. WE Use Operative Indicators to define characteristics of WBS and to specify which tasks WBS can perform during Execution In General, we have three Operative Indicators such as 1. Planning Indicator 2. Account Assignment Indicator 3. Billing Indicator Planning Element: WBS Elements will be set for planning Element,if we we want a plan cost to be enabled For Example, While Creating a Project- Manufacturing an Equipment. We will Create different WBS elements for each Level such as Design, Procurement of components, Production, Assembly and Installation. During Each state some cost is incurred and we
2 comments
Read more