Tasks

------------
1. Fill Out Header Section
2. Fill Out Segment Details => Approvals - Schedule - Planning => SAVE
3. Execute Risk Assessment
- Risk Assessment Findings
- Fill Out Risk Assessment
- Execute Risk Calculation
- Check - Risk Assessment Box =>SAVE
4. Task Creation
5. Attach Artefacts - Set 1 ( TR Details, UAT Evidence )
6. Send for Assessment
7. Update SI Change Manager

N1 : Status Moves to => Assessment

-----------------------------------------------------------------------------------
----------------
8. Confirm Status => Plan & Build
9. Attach Artefacts - Set 2 ( Approvals - Business, IT & Summer Freeze )
10. Close Task assigned to you & save

N2 : Status Moves to => Review

=================================================================================
Approval Email Formats
=====================

wonder at all why this is the 1st choice for so many user who start using LSMW for
data migration. It may be understandable for people in my age who had to use batch
input recording in the ancient times before LSMW was released, but looking at the
Avatars here in SCN I see mainly young people….having trouble with their LSMW
recording.

Why do they use recordings if SAP has already provided import methods? Did they
miss to read the documentation?

from: SAP Library – Legacy System Migration Workbench

You can use the recording function to create a new object (or a new “import
method”) if neither a standard batch input program nor a standard direct input
program nor the BAPI/IDoc method is available for a data object.

No, I do not want to demonize LSMW recording. I use it too, for data objects where
SAP has not provided any import method, and as well for some quick and dirty mass
changes on 1 or 3 fields. I have even used it for material master, in case the
change was in the initial screen and in Z-fields which are not available in
standard import methods.

But let me try to explain why the recording method is not suitable for a material
master.

The LSMW recording is a static method. The program which is generated from a
recording does exactly the same screen sequence as earlier recorded. It puts the
cursor into the same fields like in your recording. It expects the same error
cases. Just the data itself can be variable.
The material master is rather dynamic, depending on the material type customizing
you may have different views to maintain, you may even have different or additional
fields in the same view, eventually having different field attributes
(mandatory/optional).

In short using a static method for a dynamic data object is like doing a break-
dance with a full body plaster cast.

Here the proof with some screen shots.

A recording is made for a spare part material. Only Basic data view, Purchasing
view, MRP1 view and General Plant data / Storage 2 view is selected.