on 2023 Jul 05 1:18 AM
Hello.
I'm facing the problem for value mapping for Key for Task List Group, which are mapped PLPO-PLNNR, doesn't have automatical mapping to source group.
The question is :
1. For Direct Transfer - does value for task list have internal number range, or external number range? in staging tables - there is a value which can be chosen, but in direct transfer - it doesn't. I think It can be a source of problem because they automatically mapping the internal number range AFTER migration.
2. Currently I'm implemented skip rule, which are skipping for creating routing for deleted material at plant level - Migration Cockpit tries to make Routing for deleted material, which makes an error because it's deleted. It can be problem? I think it isn't, but I have to think all the ways which can be problematic.
3. For extend question 1, Is there a way to find why it's mapping value is empty? As I know of, all of other object's mapping rule is 'as same as source', so i don't have to check every mapping value, which can be 2M+ - but in BOM and Routing group number, it doesn't.
I don't mind it's target side, or source side - Any help would be appreciated.
Request clarification before answering.
It's odd - But find an answer.
There is a mapping rule, which are named as 'MAP_PLNNR', set for updating group number AFTER migration, which imply this object is for internal number range.
If you want to 1:1 mapping, which are truly want use external number range to target system, you should modify mapping rule like other rules - input value to output value, not return from target system.
Simulation done nicely and Migration too - It has the group number, same as source system.
But It also makes me a question - why default setting is internal, in object document says you should setting external number range setting.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
20 | |
10 | |
8 | |
7 | |
7 | |
6 | |
6 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.