05-18-2016 10:35 AM
Articles in SAP Retail have descriptions in table MAKT, which can be distributed to stores with message type WP_PLU > structure E1WPA03. But they can also have several other texts such as the brand, URL for QR code, additional price label texts etc.
Segment E1WXX01 could be used for such texts, if each store had only one language. But in some regions of the world it's suitable / a legal requirement presenting the texts in multiple languages (think: Parts of Russia or China or multinational cities like Bruxelles).
What do you consider as best practice to distribute the same customized text in multiple languages?
05-18-2016 6:45 PM
Hi Sune,
If I understand your problem correctly, there is a provision to maintain the different language descriptions under POS view of article master. When they are maintained with different IDs, it can be included in standard WP_PLU or WBBDLD IDoc to send the same to POS.
We had similar requirement to download English and Arabic description to POS in Saudi Arabia.
Alternatively, we need to use enhancements and user exit to include the customize field in an extra segment and then populate them while preparing IDoc.
Let us know if this is not what you wanted to discuss.
Regards,
Amit
05-18-2016 6:45 PM
Hi Sune,
If I understand your problem correctly, there is a provision to maintain the different language descriptions under POS view of article master. When they are maintained with different IDs, it can be included in standard WP_PLU or WBBDLD IDoc to send the same to POS.
We had similar requirement to download English and Arabic description to POS in Saudi Arabia.
Alternatively, we need to use enhancements and user exit to include the customize field in an extra segment and then populate them while preparing IDoc.
Let us know if this is not what you wanted to discuss.
Regards,
Amit
05-19-2016 9:46 AM
Thank you. The problem is that the texts are housed in a home made table (Zxxxx). As SAP already supports distribution of texts residing in the right place (table MAMT), my current challenge about many languages is not an SAP problem.
05-19-2016 1:50 PM
Hi Sune,
If the descriptions are in custom table, then you need to do enhancement to IDoc and then implement user-exit to populate them.
With these steps, your descriptions will be included in the IDoc and can send to partner through integration.
I hope this will help.
Regards,
Amit
05-19-2016 2:20 PM
Hi Amit
It is no law that we should also keep the data in a custom table in the future. But your suggestion about using the POS view (table MAMT) has some weaknesses. E.g. transaction MM41-MM43 can only show/enable maintenance entries where MAMT-MTXID = 02. Furthermore function module POS_MATERIAL_GET line 127-136 prohibits other standard text IDs than MAMT-MTXID = 02.
Of course we can just make an extension. However, I wonder that every SAP Retail customer must use its own extension for language specific texts, as every SAP Retail customer has such texts. I cannot avoid considering that as a significant room for improvement by SAP.
05-19-2016 3:09 PM
Hi Sune,
Thanks for sharing information about MAMT.
I was wondering we can maintain multiple language article description using the counter. Please see below image:
Standard SAP IDoc WP_PLU should be able to include these texts in IDoc, or we can include them using the user-exit.
Just shared my thought.
Regards,
Amit
05-19-2016 3:44 PM
Hi SAP
The solution suggested by Amit technically works. But is that really the way you want us to maintain QR codes (which may require more than the 40 characters in one line), extra texts for invoices by the store system (which may not always exist) etc.?