Hello,
I'm trying to use LTMOM and to have some variables. With LSMW, it was easy to add a variable, and during convert phase, user fixes the value and we move into the variable. It's simple and for example, field like accounting date, it's perfect.
In LTMOM, how can we declare variable that the user will fixed during the conversion/preparation phase ?
Philippe
4 Answers
-
Best AnswerPosted on Jul 14, 2020 at 10:07 AM
I don't really understand the idea which you have in mind, you plan to reuse the filled templates?
E.g. upload again the same data and just change certain fields?
I ask, because for go-live (at least in the projects where I participated so far) the same person who uploads the files is performing the steps in LTMC, which means that there is no much difference between entering a specific values in the template and then uploading it compared to modifying a value in the uploaded file before you start with simulation step.
If you want to ensure that specific fields in the template are not modified unintentionally, you can try protecting these with password (most users will not know how to bypass this)
You can certainly maintain your own mappings - e.g. account A in the template corresponds to account B in the target system. This can be done in LTMC or in LTMOM. I would use LTMC if this is just a few entries, for more entries LTMOM is a better option in my opinion (you can upload the mapping from file), or if the value of B is based on a specific logic, which you want to ensure that it is not violated - you can create a custom mapping rule with free coding.
There are some very nice examples in a recent openSAP course for data migration, if you are interested in creating your own rules, I would highly recommend that you enroll (it is free of charge, but you have to register to consume the content): Migrating Your Business Data to SAP S/4HANA – New Implementation Scenario.
So far I assumed that you meant migration via file upload, if this is a different scenario - staging tables, direct transfer - these topics are also covered in the course.
For me personally (I am not a developer), the main challenge in creating your own rules is that some statements that you can use for free coding (specific to data migration) are not well documented in the official help documentation, so there is some digging and frustration until you get these working.
Add a comment
-
Posted on Jul 13, 2020 at 08:22 PM
I'm not sure that I understood you - you need a way to populate specific parameters in the underlying function modules, but not via a template file and not by setting a constant or by implementing certain logic that the person uploading the file cannot influence. Is this correct?
If yes - take a look at the migration object for creating business partners - how they give the option to choose internal or external numbering (you select the option in LTMC). I think that this is close to what you are asking, but (of course) you will probably need to adapt your migration object.
If you meant using constants instead of entering the same data in the migration template - just use the rule MOVE and enter the desired fixed value with quotes, e.g. 'CD'.
If you meant something like determining the value via complex logic without the need of entering the information in templates or relying on the user to select the right value - create your own rule with free coding
Add a comment
-
Posted on Jul 14, 2020 at 12:43 AM
Please check the below blogs.
Thanks,
NSK
Add a comment
-
Posted on Jul 14, 2020 at 09:31 AM
Thanks for your return Veselina Peykova.
First I would like to use a dynamic date, if I fix it in the template ... users in charge of migration can't change it. We have to upload the GL balance of each month of previous FY.
Second, I would like to improve rule for translation, for example chart of accounts in source and target (S4) are differents. In source system, some accounts are GL accounts, in target there are vendor position. Other cases are in source it's a standard vendor position, in S4, it's a vendor position using Special GL transaction. It's why I need to adjust the standard object to take in consideration all the business rules.
Thanks Narasimhulu Konnipati for your links,
Philippe
Add a comment
Add a comment