SAP Community
Products and Technology
Additional Blogs by Members
Preparing for SMLT ("Was dem einen recht ist, ist ...
Additional Blogs by Members
All community
This category
Blog
Knowledge base
Users
Managed tags
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Search instead for
Did you mean:
Preparing for SMLT ("Was dem einen recht ist, ist dem anderen billig", Part II)
former_member18
1923
Active Participant
Options
Subscribe to RSS Feed
Mark as New
Mark as Read
Bookmark
Subscribe
Printer Friendly Page
Report Inappropriate Content
12-07-2006
8:42 AM
0
Kudos
In a post here:
Was dem einen recht ist, ist dem anderen billig
and a series of posts here:
The Diachronic Metadata Repository (DMDR) as a Tool for Risk Reduction via Conflict-Prevention Durin...
The Diachronic Metadata Repository (DMDR) as a Tool for Risk Reduction via Conflict-Prevention Durin...
The Diachronic Metadata Repository (DMDR) as a Tool for Risk Reduction via Conflict-Prevention Durin...
The Diachronic Metadata Repository (DMDR) as a Tool for Risk Reduction via Conflict-Prevention Durin...
The Diachronic Metadata Repository as a Tool for Risk Reduction via Conflict-Prevention During Legac...
The Diachronic Metadata Repository as a Tool for Risk Reduction via Conflict-Prevention During Legac...
The Diachronic Metadata Repository as a Tool for Risk Reduction via Conflict-Prevention During Legac...
The Diachronic Metadata Repository as a Tool for Risk Reduction via Conflict-Prevention During Legac...
The Diachronic Metadata Repository as a Tool for Risk Reduction via Conflict-Prevention During Legac...
The Diachronic Metadata Repository as a Tool for Risk Reduction via Conflict-Prevention During Legac...
The Diachronic Metadata Repository as a Tool for Risk Reduction via Conflict-Prevention During Legac...
I suggested that SAP does not make its own metadata sufficiently transparent to support all activities requiring knowlege of SAP architecture, particularly activities such as "AsIs:ToBe" mappings in Legacy -> ERP conversions, or creation of Enterprise SOA services. So I'd like to share something that recently happened at work, in order to illustrate this point. The customer is opening a plant in a different country and must run SAP in a different language. So the first thing it wants to do is run SMLT with a list of tables that are involved in the transactions which will be run in the new language. Ah - but how to get this list of tables ...! Shouldn't there be an absolutely transparent utility which takes the set of transactions from the blueprint and produces a list of tables that need to be fed to SMLT to support these transactions? Alternatively, shouldn't SAP "open up" the metadata and metaprocesses behind the Repository Information system, so that an enterprising customer can write such a utility itself? Am I missing something here? If so, I've posted this post in the ABAP General Forum also, so that anyone who wants some points can tell everyone how and why this problem is really not a problem. (If more than one good solution is posted, I promise I'll ask Craig/Mark to award "10" to each one.)
david halitsky
Retagging Required
2 Comments
Related Content
Warum ihr den SAP BTP Partner Summit 2024 nicht verpassen solltet
in
Technology Blogs by SAP
yesterday
Warum Ihr den SAP BTP Partner Summit 2024 nicht verpassen solltet
in
Technology Blogs by SAP
yesterday
Warum Ihr den SAP BTP Partner Summit 2024 nicht verpassen solltet
in
Technology Blogs by SAP
yesterday
SAP variant configuration and pricing - manual exchange rate for a quote from SAP CPQ
in
CRM and CX Questions
yesterday
SAP Customer Data Cloud Integration with Commerce Cloud and Composable Storefront
in
CRM and CX Blogs by SAP
yesterday
Popular Blog Posts
Are you there, SAP? It's me, Jelena
Integration Point of MM-FI-SD in SAP ERP
SAP Project System - A ready Reference ( Part 1 )
Top kudoed authors
User
Count
rkumar_47
1
brenton_ocallag
han
1
View all