on ‎2018 Oct 03 6:09 AM
Hi All,
I created some z fields in KNVV table. I followed a document on how to add custom fields in standard entity in customer master. I added the fields in Data model, generated structure, checked the fields in USMD_DATA_MODEL, did editting in SMT and then configured the fields in UI. When I activate change request in MDG , the fields are not transferring in active area nor in ECC.
I m not sure what I have missed. Is there any suggestion?.
Request clarification before answering.
Hi ,
I was able to resolve the problem. It was in the BP API mapping where , the 2 structures "CMDS_EI_SALES_DATA" and "CMDS_EI_SALES_DATA_X" did not have the right fields. Our fields in ECC and attributes in MDG were not similar. In ECC the custom field was lets say "ZZABCDE" whereas in MDG the mapping attribute in data model was defined as "ZZABC". In the append structure we appended the wrong source fields.
An easy way to check such SMT issues is to check the fields in "CMDS_EI_SALES_DATA" and in "CMDS_EI_SALES_DATA_X". They should be the same.
After correcting the fields in structure I regenerated the structures and the problem was solved
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Muhammad,
create a CR that contains values in your custom fields. Don't approve / activate the CR via the MDG UI. Instead call transaction SWO1 with your CR. Choose method "ACTIVATE_2" for debugging. Set a breakpoint in function module "CVI_EI_INBOUND_MAIN". In the given complex structure, check whether your data is in, or not. If it is in, there's some issue in the later SAVE of CVI. If not, there is an issue in mapping from staging to active area. You can use the call stack to find the access class SAVE method for a breakpoint for more detailed debugging. 😉
Best regards
Michael
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Rohit,
I have 6 custom attributes and yes we have custom data elements for each one of them
When I activate a CR and check the changes in my custom attributes in MDG UI for that customer the changes have disappeared, let alone it being replicated into ECC.
Regards
Muhammad
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Rohit
Thanks for your reply. I put the data directly in XD02 and it did replicate into MDG. Why do you say that this is a CVI issue? I checked CVI settings and it seems fine.
We are using MDG 8.0.
Do let me know what are your inputs on CVI.
Regards
Muhammad
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Muhammad,
What are your custom attributes and are you using custom data elements for them ?
How many custom attributes you have created ?
I said its' a problmen in CVI, because while activating CR, CVI kicks in and takes the data from CR to Respective Master Domain.
In this case, BP gets activated and then CVI takes the data from Staging to Customer Master and in between it's getting lost.
-Rohit
Muhammad,
I am assuming that Data is going to Staging Area and you are able to see the data in the Change Request when the CR is in workflow and as soon as you activate it, data vanishes ? Is that correct.
To find out if there is an issue in SMT Mapping, try putting the data in the KNVV table directly for a Customer for your custom attributes and then open this customer in MDG. If you are able to view the data in MDG UI, then there must be some issue with CVI mapping but if you are not able to see the saved data in custom attributes then in that case there is an issue in SMT mapping.
Which version of MDG you are using. Is it happening to all of the Custom attributes you have created for Customers or specific to KNVV section?.
If you have done everything correct and still having issues, then try looking at NOTE 2496834. We have updated our system from MDG v9.0 to v9.1 and immediately after that all our custom attributes stopped working. We applied the mentioned note and then it worked. Reason being all the SMT extensions never inserted in the generated code so we have to do the workaround mentioned in the NOTE.
Cheers,
Rohit
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
markus.greutter ....I followed your posts on this . We have a similar issue. I did ran USMD_ADAPT_BRF after reading your blog post. but still the fields dont replicate in active area. CAn you please help
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Muhammad,
unfortunately the report USMD_ADAPT_BRF does not always do what you would expect it to do.
If you start USMD_RULE again the structures used in the BRF+ rules should be regenerated again based on Data Model changes.
If this does not solve the issue you can check your data model enhancement. Did you maintain a structure and field for the new attribute?
Best regards,
Markus
Hi Teena ,
I already followed the document , but I had no success. Did the config again and again. I guess there is some issue in SMT mapping
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Muhammmad,
See the below link. It may help.
https://answers.sap.com/questions/99931/how-to-add-customadditional-field-of-kna1knvv-in-m.html
Thanks
Teena
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 9 | |
| 7 | |
| 6 | |
| 4 | |
| 3 | |
| 3 | |
| 3 | |
| 2 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.