This Blog is mainly on SAP Exam Questions and Selected "How-to" SAP processes

Showing posts with label ~ Q&A in Class (2024-05-09) S4600. Show all posts
Showing posts with label ~ Q&A in Class (2024-05-09) S4600. Show all posts

Tuesday, May 7, 2024

Q&A in Class (2024-05-09) S4600

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Vistex & SAP SD

A Rebate is a financial incentive that manufacturers or service providers offer purchasers, typically used as a marketing strategy to boost sales and customer loyalty. Unlike immediate discounts at the point of Sale, Rebates are refunded after the Purchase or Sales has been made. In SAP ECC, the processes for Rebate processing are configured and handled separately for MM and SD module. 

Due to the motivation of  the "Simplification Project" in S/4HANA, SAP "retooled" the Classic ECC Rebate (now obsolete in S/4) into an entirely new module called "Settlement Management (or Condition Contract Management (CCM))". The new "Settlement Management" component supports all types of settlement processes, including core business processes that need to be fully integrated in the order-to-cash cycle or within in a procure-to-pay scenario via a "Condition Contract" with the Business Partner Customer or Vendor. 

Note that in ERP 6.0 EHP 6, SAP introduced Condition Contract Settlement (CCS) as an alternative to the existing rebate settlement functions in SAP MM and SAP SD; in ECC6, SAP users have a choice to use either the Classic Rebate of CCS. BUT in S/4HANA, the Classic MM and SD Rebate Processing are now deactivated (Obsolete). 

Please find the Blog Posts related to Settlement Management in the following link:

Vistex (incorporated in 1999), is a 3rd party software company that create the solution for managing pricing, trade, royalties and incentive programs and has partnership with SAP for 14 years since 2006 (when SAP introduced its ECC system) and in 2020, Vistex, Inc. received an equity investment from SAP SE (NYSE: SAP) signifying a closer relationship between the companies to SAP’s focus to accelerate innovation with its ecosystem on the areas of pricing, complex commission calculations, trade and rebate processing. Since 2006, Vistex (SAP Partner) has been part of the SAP Solution Extension initiative for eighteen years, earning recognition as an industry standard. The latest new cloud solutions expand the existing solution extension portfolio by Vistex to enable each company's journey to the cloud.

However, how deep is the Vistex solution integration to SAP S/4 CCM (Condition Contract Management) requires further investigation. 

Link to SAP CCM and Vistex: 

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

S/4 EWM Tables

Here are the link to the Blog Posts for the Common Tables for SAP EWM.


OR via SE11 and check the following:
  • /SCWM/LAG* -- Storage Bins Tables
  • /SCWM/O* -- Warehouse task Tables
  • /SCWM/TU* -- Handling Unit Tables
  • /SCWM/W* -- Warehouse Order Tables
  • /SCWM/WAVE* -- Package wave Tables
  • /SCDL/DB* -- Inbound/Outbound Delivery Tables
  • /1OM/* -- Value-Added-Service Order Tables
  • /LIME* -- Physical Inventory Tables
  • /SAPAPO/MAT* -- Master Data Tables
Refer to Blog Post: 

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

S/4 BRF+ for Output

Th Classic Condition technique, based on the NAST table (via Access Sequence Technique) for Message Output (for Printing, Email, EDI etc.) for various modules (eg: Logistics and Finance alike) are so far still available in the S/4 HANA system. An Access Sequence is a Search Strategy with the aid of which the SAP System searches for valid Condition Records of a certain Condition type (Message Type) to determine the Message Output requirement for a specific Document (like Order Confirmation, Outbound Delivery Document, Billing Document). 

BRF+ is an ABAP based framework and is a component of the NetWeaver (previously called BASIS) stack. BRF+ stands for "Business Rule Framework Plus", which provides a all-encompassing API (Application Programming interface and user interface) for defining Business Rules. It enables users (configurators) to define Business Rules without the need to write ABAP codes. 

BRF+ is not new and even not directly related to S/4HANA, but with the release of S/4HANA 1610, BRF+ gained a lot of attention since it is launched as the go-to solution for some business processes. AND one of the most important ones are the incorporation of BRF+ into Output Management for Logistics Modules: 
  • MM Purchasing - Purchase Order document Message Output
  • MM Inventory Management - Goods Movement and Physical Inventory Message Output
  • SD Sales & Distribution - Order Confirmation Message Output
  • SD Outbound Delivery - Outbound Delivery Document Message Output
  • SD Billing - Billing Document Message Output
  • and many more Message Output applications.
User (Configurators) can now configure BRF+ Message Output for "ALL modules" in one single IMG transaction in IMG - Cross Application - Output Management. However, there is still an option to retain the use of the classic NAST for Message Output.


Click to Google Drive to check the step-by-step example of BRF+ configuration the SD Order Confirmation: 

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Sales Order upload

The "Import Sales Order" Fiori App (App ID F4293) allows Internal Sales Representatives to create (mass upload) Sales Orders from Spreadsheet. The spreadsheets can be local Microsoft Excel (*.xlsx) files, or web-based Google Sheets. (Once have access to this App will create a Blog Post). 

Similar to many "mass upload from Spreadsheet" Apps, this SD App allows users to first Download/Import the "Spreadsheet Template", then just fill up the Sales Order header and Item data into the Spreadsheet - Check/Review - then Upload into SAP via the same App.

https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/#/detail/Apps('F4293')/


See link to help.sap.com for Documentation of the App: 

For Authorization setup, refer to the App in:
Technical Catalog: SAP_TC_CEC_SD_COMMON
Business Catalog: SAP_SD_BC_SO_IMPORT
Business Role: SAP_BR_INTERNAL_SALES_REP

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Standard Split/Combine Criteria for Outbound Delivery document creation

Which fields will lead to Delivery Splits for SAP Outbound Delivery creation with reference to the Sales Orders? 

The SAP S/4HANA offers the following as standard fields (already configured via the SAP Routines in the "Copy Control" from Sales Order Type to Outbound Delivery Type and its associated Item Category) for Delivery Splits or Convergence (Combinations): 
  • Ship to Party (tested)
  • Delivery date (tested)
  • Incoterms (tested)
  • Shipping point (tested)
  • Shipping condition (tested)
  • Route (tested) 
  • Delivery Priority

Basically, all fields which are copied to the header of the delivery (table LIKP) via the routines of the copy control lead to a delivery split.
Split fields that cannot be changed are:
  • VSTEL Shipping point
  • ROUTE Route
According to SAP Notes, the following split-relevant fields can be affected via the "Copy Control", however, please test them to verify if the are effective:
  • VKORG Sales organization
  • AUTLF Full delivery indicator
  • VSBED Shipping condition
  • FKARV Billing type (customer billing document)
  • LIFSK Delivery block
  • STAFO Update group for statistics
  • STWAE Statistics currency
  • KKBER Credit control area
  • KNKLI Account number of the customer with the
  • credit limit default
  • GRUPP Customer credit group
  • SBGRP Processor group for credit management
  • CTLPC Credit management: Risk category
  • CMWAE Currency key of the credit control area
  • WAERK Currency of the sales document
  • INCO1 Incoterms 1
  • INCO2 Incoterms 2
  • KZAZU Indicator order combination
  • KDGRP Customer group
  • PERFK Invoicing dates (calendar identification)
See the following:

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Standard Split/Combine Criteria for Billing Document creation

Standard Fields that always cause a Split (based on SAP documentation) with the following data fields:
  • Sales organization
  • Distribution channel
  • Division
  • Sold-to party
  • Bill-to party
  • Payer
  • Document currency
  • Tax departure country/region
  • Tax destination country/region
  • Customer reference
  • Payment terms
  • Incoterms
  • Incoterms (part 2)
  • Incoterms version
  • Incoterms location 2
See the following: 

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Outbound Delivery listing Output before Pick/Pack

The Fiori App "Manage Outbound Delivery" (App ID F0867A) will be able to list Outbound Deliveries as a Worklist:
  • Ready for Picking
  • Ready for Confirmation (for Warehouse Management)
  • Ready for Goods Issue
In the current version SAP S/4HANA 2023 FPS01, this App do not have Status "Ready for Packing". 


click to check Blog Post 

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
at No comments:
Labels:
Subscribe to: Posts (Atom)