Shelf Life Expiration Date in SAP Material Master: End Users Guide

Shelf life expiration date (SLED) is a date that indicates the end of a product’s usability. In SAP Material Master Data, SLED is used to control the inventory of perishable goods and to prevent the delivery of expired products to customers.

SLED is calculated based on the following information in the material master:

– Minimum remaining shelf life: The minimum number of days that a product must have left until its expiration date at the time of goods receipt or delivery.
– Total shelf life: The maximum number of days that a product can be stored before it expires.
– Period indicator for SLED: The unit of time (days, weeks, months, etc.) used to specify the minimum remaining shelf life and the total shelf life.
– Rounding rule for calculation of SLED: The rule that determines how the SLED is rounded up or down based on the period indicator.

For example, if a product has a total shelf life of 90 days, a minimum remaining shelf life of 10 days, a period indicator of days, and a rounding rule of round up to next day, then the SLED is calculated as follows:

– If the product is received on April 1st, 2023, then the SLED is April 1st + 90 days = June 30th, 2023.
– If the product is delivered on June 20th, 2023, then the remaining shelf life is June 30th – June 20th = 10 days, which meets the minimum requirement.
– If the product is delivered on June 21st, 2023, then the remaining shelf life is June 30th – June 21st = 9 days, which does not meet the minimum requirement. The system will issue a warning or an error message depending on the configuration.

SLED is an important feature in SAP Material Master Data that helps to ensure the quality and safety of products and to optimize the inventory management of perishable goods.
In the end user document provided in link, you are guided through:

  • Maintenance of General Plant Data/Storage view in MM01 transaction code,
  • Definition of Span for the Material
  • Browse Material Shelf Life Lists in MB5M

Read more

ABAP Debugger Guide for Functional Consultants

The debugger is a tool that can be used to execute ABAP programs by line or by section. It is the most basic tool that can be utilized to reach the root cause of any day-to-day issue faced in SAP. It not only lets you troubleshoot effectively but also helps you visualize ‘what-if’ scenarios. With this tool, you can display data objects and check the flow logic of programs.
The shared documents covers following topics:

  • Introduction to ABAP Degugger
  • Classic Debugger vs New ABAP Debugger
  • Advanced features of ABAP debugger
  • Different types of breakpoints
  • Flow of Control
  • Debugging various ABAP objects – SAP Script
  • Debugging various ABAP objects – Smartforms
  • Debugging various ABAP objects – Batch Jobs

Read more

Packing (Handling Unit Management) Process in SAP: Introductory Presentation

Packing is a process of grouping materials or products into containers or units for easier handling, transportation and storage. In SAP, packing is integrated with various modules such as sales and distribution, warehouse management and production. Handling Unit Management (HUM) is a functionality in SAP that allows users to manage the packing process more efficiently and flexibly.

HUM enables users to create, change and monitor handling units (HUs), which are logical or physical representations of packing materials and the goods contained in them. HUs can have unique identification numbers (HUIDs) that can be scanned using barcodes or RFID tags. HUs can also have hierarchical structures, meaning that one HU can contain one or more sub-HUs.

In this presentation business process of packing or Handling Unit Management in SAP is described.

Packing (Handling Unit Management) in SAP
Packing (Handling Unit Management) in SAP
  • Benefit of Packaging
  • Management of Packaging Materials
  • Scenarios of Packaging Materials
  • Post Goods Issue

Read more

SAP S/4HANA Sales Revenue Reporting Compliant to IFRS15

This document aims to show how to process sales orders while complying with IFRS15 regulations. It also discusses the configurations required in the system to achieve this using integrations between SAP SD (operational system) and SAP RAR (Revenue Accounting and Reporting system). Additionally, it provides some examples of sales processing scenarios with IFRS15 compliant revenue postings.
For the purpose of demonstration, following sales scenarios are included:

  • Sale of service items with time related revenue recognition compliant to IFRS15
  • Sale of stock items with event related revenue recognition compliant to IFRS15

Content of the document is as follows:

  • IFRS15 Revenue Reporting Requirements
  • System Architecture and SAP RAR (Revenur Accounting and Reporting) Deployment Options
  • Configuration Nodes
  • GUI Settings
    • Integration of Operational System (SAP SD) with SAP RAR
    • SAP Revenue Accounting and Reporting (SAP RAR) settings
  • BRF+ Settings
  • Performance Obligation Determination
  • Scenario Illustration
  • Non-Bundled Sales
  • Bundedsales
  • Bunded Sales With Billing Plans

Read more

How to Create Custom CDS View in SAP S/4 HANA

CDS stands for Core Data Services, which is a framework for defining and consuming data models in SAP applications. CDS views are one of the key features of CDS, which allow developers to create reusable and consistent data definitions that can be accessed by various tools and technologies.

One of the main benefits of using CDS views is that they enable a simplified and harmonized data access layer for SAP S/4 HANA, the next-generation ERP system from SAP. CDS views can leverage the power and performance of SAP HANA’s in-memory database, as well as provide a common semantic layer for reporting and analytics.

Why Custom CDS Views is used in SAP S/4 HANA ?
Sometimes the standard CDS views provided by SAP may not meet the specific business requirements or scenarios of the customers. In such cases, customers can create their own custom CDS views to extend or enhance the existing data models. Custom CDS views can be created using the ABAP Development Tools (ADT) in Eclipse, which provide a graphical editor and a code editor for defining the CDS view properties and logic.

Some of the use cases for creating custom CDS views are:

– To add additional fields or calculations to an existing CDS view
– To join or aggregate data from multiple CDS views or tables
– To filter or restrict data based on certain conditions or parameters
– To expose custom fields or annotations for consumption by other applications or tools

Custom CDS views can be consumed by various SAP technologies, such as ABAP programs, OData services, Fiori apps, Smart Business KPIs, etc. They can also be exposed to external tools or systems via SQL or REST interfaces.

Custom CDS views are an important and flexible way to tailor the data models in SAP S/4 HANA to suit the customer’s needs and preferences. They can help to optimize the performance, usability, and maintainability of the data access layer in SAP S/4 HANA.

In this document, the author illustrates how CDS views can be created with oDATA

Read more

COPA in SAP S/4 HANA: Training Presentation

COPA is a component of SAP’s controlling modules that deals with profitability reporting across various dimensions. It’s commonly referred to as SAP-COPA. It enables you to evaluate your company’s profit or contribution margin by market segment or by strategic business unit such as a sales organization or profit center. Profitability Analysis provides your sales, marketing, product management, and corporate planning departments with information to support internal accounting and decision-making.
In this presentation document, following SAP CO-PA topics in S/4 HANA are outlined;

  • Key reporting dimensions of SAP-COPA
  • Types of COPA
  • Drawbacks of account based COPA
  • Advantages of Costing based COPA (CBC) over Account based COPA (ABC)
  • Dataflow in COPA
  • SAP S/4HANA – COPA modifications
  • Account based v/s Costing based COPA in S4/HANA
  • Why Account based COPA is better than Costing based COPA in S4/HANA
  • Advantages of Combined profitability analysis over Costing based profitability analysis

Read more

SAP EWM: End Users Guide to Kit to Stock Process

Kit to stock is a process in SAP Extended Warehouse Management (EWM) that allows you to create kits from individual components and store them in the warehouse. A kit is a set of products that are sold or used together, such as a gift basket or a repair kit.
The kit to stock process enables you to optimize your inventory management and reduce your storage space requirements. You can also use it to prepare kits in advance for seasonal or promotional demand.
A typical Kit-to-Stock Process flow chart is as follows in SAP:

Kit to Stock Process Flow Chart in SAP EWM
Kit to Stock Process Flow Chart in SAP EWM

Read more

Categories EWM