segunda-feira, 30 de dezembro de 2019

Set Up Batch Determination in Sales and Distribution

Purpose

Learn the process of setting up the batch determination in sales and distribution scenario.

Overview

Set up a sample of batch determination in Sales and Distribution.

<Prerequisite>

  • A Batch Managed Material must be created with Sales view maintained in material master.
     
  • Several batches are created and classified.
     
  • Goods receipt has been posted to the batch to make sure there are stocks.
     

<Steps>

  1. Selection Class is created in CL01. The characteristics in the selection class should be part of the batch class in the material master, but some of the standard characteristics may not need to be entered in the batch class but only need to be entered in the selection class. For example, LOBM_RLZ and LOBM_LFDAT.
     
  2. Sorting Rule is created in CU70. The characteristics in the sort rule should be part of the batch class in the material master, but some of the standard characteristics may not need to be entered in the batch class but only in the sort rule. For example, LOBM_MENGE and LOBM_LGORT.
     
  3. Batch Search Strategy setup in VCH1.

    Batch search strategy customizing in OCHA.


    Create batch search strategy for proper combination.


    Setup the basic information for the strategy.


    Maintain the selection criteria by using the selection class created before.


    Add the sort rule that is created before. 
  4. Batch Search Procedure is assigned to the corresponding sales area and document type in OCHA customizing.

<Test>

  • Test in Sales Order in VA01.



    If you have more than one characteristic in sort rule, then it will first follow the first characteristic then if there are same value for the first characteristic, it will sort them follow the second characteristic and so on.

    In sales order, no matter what you have defined of the batch split in the batch search strategy, there will be only ONE split of batch record.
  • Test in outbound delivery in VL01N.



    If the batch determination should be carried out automatically is defined in customizing OCHA for the specific item category.

    Batch determination result can be checked in the item detail batch split tab.

    The batch determination can be manually carried out again to check the details. 

Related Content

Related Documents

Related SAP Notes/KBAs


SAP Screen Personas 3.0 SP10 now available. SAP Fiori 3 ready.

One of the most anticipated benefits of SAP Fiori 3 is the UX consistency it will deliver across a wider portion of SAP’s product portfolio. With SAP Screen Personas 3.0 SP10, we make it possible to apply the SAP Fiori 3 theme, also known as “quartz”, to your classic transactions. This means you can run simplified SAP GUI transactions in your SAP S/4HANA, SAP Business Suite on SAP HANA, or ECC system, on your desktop, tablet, or phone. As more customers are deploying SAP Screen Personas to more scenarios, we have focused this release on streamlining large-scale deployments.
We have been seeing more SAP S/4HANA customers using SAP Screen Personas to provide the SAP Fiori user experience to SAP GUI transactions that do not yet have corresponding SAP Fiori apps. Some of their most common requests are what we have put into SAP Screen Personas 3.0 SP10:
  • Simpler and more comprehensive SAP Fiori launchpad integration
  • Consistent UX across SAP-shipped Fiori apps, custom-built SAP Fiori apps, and SAP Screen Personas flavors
  • Easier way to manage large numbers of flavors, especially to reuse scripts across flavors via Global Scripts
  • Better rendering of tables on mobile devices
In addition, customers from our SAP Screen Personas Practitioner Forum community provided suggestions for usability improvements. These ideas, plus those from the usability testing sessions at SAPPHIRE and SAP TechEd, are found in various enhancements to the flavor editor and admin transaction.
Integrating SAP Screen Personas flavors into the SAP Fiori launchpad has more options
Many customers choose to use the SAP Fiori launchpad as the single entry point to all their SAP ERP functionality. This is the standard approach for SAP S/4HANA and a nice usability enhancement for ECC systems. Using SAP Fiori-themed SAP GUI transactions through the SAP Fiori launchpad means your users have a consistent experience, whether the tile goes to a standard SAP Fiori app or an SAP Screen Personas flavor.
We have made several improvements to the Slipstream Engine launchpad plugin to allow for better navigation between the flavors and other applications using SAP Fiori launchpad, such as prompting the user for unsaved changes when navigating away from Slipstream Engine.
Also, in response to several customer requests, we added an option to render the flavors in launchpad using the full screen width instead of the default letterboxing rendering.
The SAP Fiori 3 “quartz” theme comes with SAP Screen Personas 3.0 SP10
At SAPPHIRE 2019, SAP introduced SAP Fiori 3, bringing consistency, intelligence, and integration across our portfolio. With more out of the box apps shipping with the SAP Fiori 3 appearance, customers need an easy way to bring this to their SAP GUI transactions in SAP S/4HANA or even ECC. SP10 includes the SAP Fiori 3 theme, so it’s very easy to apply the “quartz” theme to your flavors, if you want the latest look for your transactions.
 
Quartz (SAP Fiori 3) theme on the left; Belize theme on the right.
SAP Fiori 3 theme requires SAPUI5 version 1.65 or higher, Refer to note for Service pack pre-requisites for SAPUI5 and SAP_UI (https://launchpad.support.sap.com/#/notes/2844656)
Managing global scripts is much easier and more flexible
We introduced global scripts in SAP Screen Personas 3.0 SP09. This allows you to use the same script in multiple flavors, potentially reducing the development and maintenance time for writing and editing scripts. With this service pack, we have made several enhancements:
  • Global scripts include a “final” flag so you can prevent accidental changes to a script you have already tested and deployed to several flavors.
  • We have added translation support for the global scripts, to make it easier to reuse scripts in distributed, global environments.
  • To manage these scripts, there is a new global scripts management section in the SAP Screen Personas admin transaction.
  • In addition, you can use the Relations tab in the Global Scripts under Object Maintenance in the Admin UI, to see which flavors are using the script and also get the change history for the script
Mobile rendering with the Slipstream Engine gets better
The Slipstream Engine, introduced with SAP Screen Personas 3.0 SP06, continues to improve. As more customers use it to run SAP Screen Personas flavors on their phones and tablets, including some very advanced warehouse scenarios with barcode scanning, we are receiving some great ideas to expand its functionality as they push its boundaries. For SP10, we have added:
  • Better integration with different SAPUI5 versions
  • Improved mobile rendering for tables
  • Many under the hood improvements based on your feedback
Slipstream Engine rendering a flavor on a phone.
There are more shortcuts in the flavor editor
Merging information from across tabs is a very common way to simplify screens and reduce the number of clicks a user needs to press to complete a task. While the dragging information to the side and realigning has been the recommended method for several years, we have now simplified the process by allowing you to cut/copy controls from one tab and paste to another. This removes the intermediate step of parking the items elsewhere on the screen.
The right-click option has been popular with users, so we have added more things you can do.

The admin transaction makes it easier to manage large deployments
  • Improved user management section for the Personas transaction
  • New Global Script management option under Object Maintenance
  • More usability improvements to the SAP Screen Personas admin transaction

Support runs through 2024
Here is our current support strategy for SAP Screen Personas 3.0.
  1. SAP Screen Personas 3.0 will be supported until at least Dec. 31, 2024. This rolling 5-year support is the same as S/4HANA. This is a minimum of five years from the release of this service pack, rounded to end of the calendar year. This remains the same as SP09, which we released earlier in 2019.
  2. We support the current as well as the two previous Service Packs. What does this mean to you?
    • SP10 will receive continuous innovation
    • SP09 will get important fixes and selected down ports
    • SP08 will receive emergency fixes
    • SP07 and earlier will no longer be supported (time to upgrade!)
System requirements
SAP Screen Personas 3.0 SP10 works on a variety of systems from SAP S/4HANA to some much older versions. Specifically:
BasisMinimum Service PackAdditional Notes Required?Supported Kernels
S/4HANAAllNo749+
750AllNo749, 753
740SP03Yes749, 753
731SP07Yes722
702SP09Yes722
701SP10Yes722
700SP25Yes722

For SAP Screen Personas 3.0 SP10, the supported kernel releases and their corresponding minimum and recommended (as of November 12, 2019) patch levels are listed below. You do not need to update your kernel to move to the latest version of SAP Screen Personas, if your system is on a supported kernel release.

Kernel release 777 –> No minimum patch level
Kernel release 773 –> No minimum patch level –> Recommended patch level 200 or higher
Kernel release 753 –> Minimum patch level 27 –> Recommended patch level 500 or higher
Kernel release 749 –> Minimum patch level 400 –> Recommended patch level 700 or higher
Kernel release 722 –> Minimum patch level 400 –> Recommended patch level 800 or higher
Kernel releases 742 and 745 are not supported, since they are out of maintenance.
See the SAP Screen Personas 3.0 SP10 Master Note 2844656 for more details and updated recommendations.
Continuous improvement
Please send us your requests (via email or as a comment to this blog) for anything you would like to see in SP11 and beyond.
Next Steps

For the SAP Screen Personas product team, Peter Spielvogel.

SAP Fiori for SAP S/4HANA – Leading Practices for Home Page Design

Or how to change your Fiori launchpad Home page User Experience from a “tiles everywhere” bathroom to a “focused workspace” dining table.
How do you meet the challenge of the scale of new User Experience that comes with SAP S/4HANA? The more SAP Fiori you give to your business users, the more SAP S/4HANA innovations they can consume.   But you will only get the value of those innovations if you have good user adoption.  You certainly do not want your new Intelligent Enterprise solution falling at the first hurdle, when a user first logs on and gets their first glimpse of the system.    This is particularly true if you are using a showcase role approach where your first carefully targeted business roles are intended to motivate driving more value out of your SAP S/4HANA solution.
Good Home Page design is essential to set first impressions and first expectations with your business users. This is an example of the sort of Home Page you want to aim for to optimize user experience – clean, simple and well ordered. Everything is relevant and important to your business role.
My very first experience of the SAP Fiori launchpad Home Page in SAP S/4HANA was very different.  I was sitting with one of our sales guys – let’s call him George –  who was working on a demo using SAP S/4HANA 1511.  By this time, I had a couple of years’ experience with SAP Fiori, so I was curious and a little perplexed to see how with trembling hand and eyes screwed up George clicked on the Login button. And then came the sudden realization of the problem of scale.  There was an onslaught of tiles! Followed by a hopeless and despairing search to find the tile he actually wanted.  No wonder George was afraid to even login.  Take a moment to think – what was the real problem here and how do you avoid it?
Sascha Weninger gave a great talk “Deploying SAP Fiori at Scale” at SAP TechEd Las Vegas 2019 which explained the challenge and how Orica handled it.  Sascha is part of the Orica project where they are deploying over 1400 apps on their SAP Fiori launchpad.  The Orica team have put a lot of effort into optimizing their Fiori launchpad for performance.  But even with their SAP Fiori launchpad optimized to run swiftly even in remote geographical locations, the problem of my too many tiles remain. To paraphrase Sascha “unless you have some kind of advanced Tetris skills, how can you focus when your Home page looks like a bathroom – tiles everywhere!”.  You need a better plan.
Interestingly this was not a challenge we came across when using SAP Fiori with SAP Business Suite or Suite on HANA or SAP Cloud Platform or even SAP SuccessFactors, where SAP Fiori is used extensively. Most of these solutions only need to assign maybe 5-20 apps to most users so a focussed Home Page is easy to do. It was relatively easy to create something that matched the original intention of SAP Fiori as seen in the Red Dot awards or SAPPHIRE NOW, or as explained in SAP Fiori launchpad setting up the right environment.
This challenge was new in SAP S/4HANA.  It is a challenge of scale of new User Experience.
You see even in SAP S/4HANA 1511, George had already around 150 tiles on his home page. To most of us in User Experience, that’s more than a little crazy.  For most people that’s just a huge cognitive overload.  Initially I put this down to early missteps – easily fixed with a little thought and some configuration.  Surely, it’s obvious to anyone logging in that you don’t want to be flooded with apps?!  Most of use phones and tablets and we are used to moving our favourites to the front page.
Except in the SAP S/4HANA RIG (Regional Implementation Group) we kept hearing complaints – usually in the form of performance such as “our launchpad takes a long time to load”. Then when we looked at the system, there was some poor user whose launchpad was jammed full of tiles.  The worst case we found was one poor user who had 500 tiles on their Home page!  How does this happen?
From our experiences with SAP S/4HANA customers so far, these are the common missteps that result in this kind of overloaded Home Page.
  • Too many business roles assigned to the same user, especially in development environments to functional consultants
  • “Everything on the home page” approach taken to custom roles
This is an example of the sort of Home Page you want to avoid – too many business roles assigned to one users, too many tiles trying to grab your attention, hard to pick out what is relevant to your most important tasks.
To be brutally fair, this was not assisted by the SAP delivered business roles.  Many of the early business roles suffered from the same tendency to put too many apps on the Home Page in the hope that the user would pick out the most useful apps. Even within the trial systems for demo convenience we often provide grouped users with overloaded Home Pages. We have had to step back and think through this within SAP ourselves and come up with some best practices to point a better way further for role and app owners.
So how do you meet this challenge in a pragmatic way on your own SAP S/4HANA projects?  As one of our moving to SAP S/4HANA customers stated in the SAP Coffee Corner podcast puts it, it’s about “presenting information in a way that drives you to do whatever you need to do”.
The good news is great Home Page design is already possible. However, it is clear that it doesn’t happen by accident.
Read on to get an idea of:
  • What you need to include in your SAP S/4HANA project
  • Some leading practices guidelines, based on SAP Fiori design intention and experiences across many customers
  • Some practical strategies to improve your home page design, especially if you are coming to this a little late in your project.
All of these are based on experiences with real SAP Fiori and SAP S/4HANA customers.  They have been discussed with SAP Fiori design leadership to understand the design intention and to consider the early possibilities and outlook as more of the SAP Fiori 3 design vision comes into play.
Within SAP our business role owners are also looking to follow many of these particularly with new business roles, and where possible to remediate old business roles.  Why are we not just reworking all the old business roles as well?  There are additional business challenges with introducing changes to a working system where users have already started to personalized their apps. So you definitely want to tackle good Home Page design from your first SAP S/4HANA project.

Building Good Home Page Design into your SAP S/4HANA Project

Providing a good Home Page at go-live doesn’t happen by accident.  You need to plan it into your project.
You need to include these project activities:
  • Establish your User Experience Strategy up front to guide your Home Page design
  • Design and implement your Home Page
  • Prepare your business users for the changes

Your User Experience Strategy guides your Home Page design

This is the domain of your User Experience expert, UX Lead or UX Architect – whatever you call them on your project – and it needs to be done very early in the project. This will set the expectation with all of the functional and technical teams around what to expect and what they can use.
For the Home Page these are key decisions to include in your strategy:
  • Confirm the scope impact of your project, which business users will be impacted and to what degree
  • Decide on your business role granularity
  • Decide at a high level which shared launchpad features will be used as part of the User Experience, e.g. SAP Fiori Search, Notifications, and Personalization options
  • Decide the entry point per business role – will everyone use Fiori launchpad via the Web Browser, or will some use the SAP Business Client Launchpad Connection option
If you have users with existing SAP knowledge, you may also want to decide early if you will make the SAP Easy Access Menu and SAP Menu available in the App Finder.
You will need to understand what options are available to you for configuring the home page on your SAP S/4HANA release. It’s always worth checking with the SAP Fiori launchpad guide for your SAP S/4HANA release:
  • What optional features are available in the SAP Fiori launchpad that will smooth the User Experience, e.g. “show one group at a time” (tabs) mode, GUI inplace mode
  • What exactly can be shown on tiles and links – and with in future SAP Fiori 3 you may need to consider Cards as well
  • What tools and best practice guidelines are available for configuring launchpad content
You also need to make sure your functional teams and organizational change management teams in particular are enabled in shared SAP Fiori launchpad features, so they can use them in their designs.

Designing and implementing your Home Page

While your User Experience expert will provide some input and guidance, in most cases this will need to involve your functional teams to add their business process perspective to the following activities:
  • Design your home page approach per business role, preferably with a few carefully selected business users if you can
  • Walk through your Home Page design with more users to get feedback and iterate as needed
  • Walk through your Home Page with your organizational change management team so they understand how this will work, and can prepare the rest of the business user community
  • Implement your Home Page, using the available tools and launchpad configuration options
Design doesn’t need to be exhaustive. You are aiming at a good enough for day one go-live experience, and then let the users personalize from there.   With one of our Public Sector customers we ran a series of 1 hour workshops with different sets of business users using post-it notes to represent each app, and separate boards for the Home Page and App Finder.
You will need to adjust the effort to your scope.  One of our Utilities customers who was doing a large digital transformation had a single dedicated designer to work through Home Page design for 60 business roles in around eight weeks.
Ideally you want Home Page design to happen as early as you can.   Logically the earliest time is towards the end of your Explore phase or fit-gap analysis when you already have a reasonable idea of:
  • Which processes and tasks are relevant to which business roles
  • Which apps will be assigned to which business roles
  • Which shared launchpad features will be used to support completing tasks efficiently
That will give you enough information to consider what is an appropriate app to app navigation flow as business users complete their tasks.

Preparing your business users

Preparing your business users depends on your approach to organizational change management.  There is no one right way to prepare users.
Many customers use different approaches to training their business users. Some have formal training plans, some do short workshops, some provide dedicated e-learning, and some provide no training at all – relying on the in-app help to cover the gap.
Naturally explaining the why of the change and being able to articulate benefits of the change to them and to the company is important.
A primary consideration in deciding on your preparation approach is whether your existing business users are:
  • New to SAP – so everything is change anyway
  • Used to SAP, and currently use SAP Logon as an entry point
  • Used to SAP, and currently use SAP Business Client as an entry point
  • Used to SAP, and currently use SAP Enterprise Portal as an entry point
  • Experienced with apps on web browsers
  • Experienced with apps on mobile devices

Leading practices for a better Home Page design

A big of part getting to a good home page design is making the most of the SAP Fiori insight to action approach that powers SAP S/4HANA as explained in Understanding insight to action app to app navigation.   This is the starting point for understanding why you do not need every tile shown as an app or link on your home page.  You only need the entry points.
What you are aiming for a is a focused workspace.  Think of it more as a dining table experience.
Do you set your dining table with every plate, every bowl, every cup, every platter, every wine glass, every fork, every knife, every spoon, every pair of chopsticks, every condiment jar and then try to eat your meal? Of course not! There would nowhere left to eat.
Or do you put only what you need so you can focus on your meal, your family and friends?
Well yes of course you do – less is more!
So our recommended leading practices are:
  1. Keep the home page slim, focusing on what is really essential for the user
  2. The home page requires a clear structure following business criteria (not technical criteria)
  3. Focus the home page on how the user understands their role
  4. Focus the home page on the entry points for the user’s most important/urgent tasks
  5. To minimize scrolling, aim for approx. 5 groups and a maximum of 64 (8×8) tiles in total across all groups for most users
  6. For users who are assigned to multiple roles, consider defaulting Home Page mode to show one group at a time
  7. Remember there is rarely one size fits all! Personalization enables the user to optimize the home page for their personal productivity
Tip: Naming and terminology used on your tiles does matter, even with a user with only a few tiles. At one site, when we went back and asked a business user what they were using, they told us they were only using two of the tiles.  Why? Most of the names on the tile didn’t make sense to them.  They didn’t understand what the tile was for, so they never clicked on it. They had a job to do – they didn’t have time for detective work.

Practical strategies for improving home page design

If your current existing Home Page design, nearly any improvement will help user adoption and personal productivity.  So here are a few techniques to consider how to get from an overcrowded home page design to a slim home page.

Focus on Insight to Action entry points

For example, use one of the over 50 delivered Overview Pages to see the insights, as show in Overview Pages in SAP S/4HANA – a good place to start. Then navigate to other apps to act at the point of insight as already explained in Understanding insight to action app to app navigation. You can tailor this navigation to your own requirements as explained in Adjusting insight to action app to app navigation.

Replace Create/Read/Update/Delete (CRUD) tiles or links with  central dashboard apps

Replace multiple tiles for the same business object with a single tile to a central dashboard for all actions on a business object.
Not only do you reduce the number of tiles on the Home Page, using dashboards makes it easier for business users to find and prioritize their workload, using the filters and additional information displayed.
There are a lot of apps with the Manage, Monitor, or Worklist in the name that can act as central dashboards for acting on business objects.
For example instead of having multiple tiles for purchase order:
Create Purchase Order, Change Purchase Order, Display Purchase Order, Release Purchase Order, Print Purchase Order
Replace these with a single tile to a dashboard app such as:

Limit Smart Business KPI tiles visible on the home page to those of real interest to the user

Too many KPIs can be distracting. Focus on KPIs that:
  • Support primary immediate job goals/aims – e.g. maximize throughput, minimize spend
  • Support career aspirations & promotion opportunities –  e.g. be the best Purchaser to grow to a Strategic Buyer position
  • Minimize negative career consequences – e.g. My Inbox approvals outstanding, stay within budget

Remove Display tiles or links in favour of Fiori Search

Where business objects are searchable by Fiori Search (i.e. Enterprise Search), Fiori Search is usually a better answer for your business users than a link to a display transaction.
Instead of having to know the exact business object id, they can search on reference, partial reference and wildcards.
The search results give a summary of resulting objects for quick identification.
Some business objects even provide quick filters to help identify the correct object quickly.
From the search results list, users can expand or drill down on the results to display more details.
They can also access any of the apps related to that business object, so there is no need to return to the Home Page.

Replace less important static tiles with links

Where there is no dynamic data shown on the tile, and the tile is not an important or urgent task, changing a static tile to a link provides a significant saving in space and mental overload, without impacting performance.
You can do this in the Launchpad Designer by editing the Tile Group to change entries from tiles to links.
Tip: Business users can also personalize this in Edit Home Page using the Convert Tile to Link option.

Becoming a SAP Fiori for SAP S/4HANA guru

In the comments please let us know your thoughts on Home Page Design.
What strategies or practices you have found that work at your site?
What has been the response of your users?
You’ll find much more on our SAP Fiori for SAP S/4HANA wiki
Brought to you by the S/4HANA RIG