cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Title: Issue with Table Sequencing When Transitioning from "In Scope" to "Supported Features" in SAP

sdtckr
Newcomer
0 Kudos
188

Title: Issue with Table Sequencing When Transitioning from "In Scope" to "Supported Features" in SAP

Description:

Hello,

In our SAP system, we have been using the "In Scope" version, and the sequence of our tables was as follows:

  1. Initial load of products
  2. Basic data
  3. Plant data
  4. MRP area
  5. Storage location
  6. Valuation data
  7. Distribution chain data
  8. Description data
  9. Units of measure data
  10. Tax classifications
  11. Production resources tools
  12. Inspection setup data
  13. Warehouse number data
  14. Storage type data
  15. Data transfer for forecast values
  16. Data for quality management
  17. Additional EANs

However, we are now required by SAP to use the "Supported Features" version, and the sequence of tables in this system has changed to:

  1. Basic data
  2. Additional descriptions
  3. Alternative unit of measure
  4. Additional GTINs
  5. Distribution chains
  6. Tax classification
  7. Plant data
  8. Forecasting data
  9. Storage locations
  10. Production resources tools
  11. Inspection setup data
  12. MRP area
  13. Warehouse number data
  14. Storage type data
  15. Valuation data
  16. Valuation current period
  17. Valuation future prices
  18. Internal number range

This new sequence is causing issues in our current business processes and data flow. How can we ensure that our data is processed in the same sequence as in the old version ("In Scope") while using the new system?

We tried using LTMOM (Landscape Transformation Mapping and Object Modeling) to revert the table sequence to the old version, but we couldn't fully understand how to do it.

Question:

How can we use the LTMOM tool in SAP to restore the table sequence from the old version ("In Scope") to the new system ("Supported Features")? Could you provide detailed steps and examples?

Thank you.

Accepted Solutions (0)

Answers (0)