Upload new phrases in the system

Question

Hi,
We are currently upgrading from 46c to ECC604. In 46C we use a very small functionality of the dangerous goods master. Just some info for entering UN numbers, hazardous substances and user defined texts (5x). We have our own forms and print some fields from this masterrecord.
According to SAP we have run DGCONVERT to convert the texts into phrases.
- UN numbers in 46C was customizing and now they are maintained in phrases. Every key gets CUST-xxxxxxxxxx numbers, but the link with the UN number and the description of the UN number is not 1:1 anymore. You could enter an other description for the same UN number. So UN numbers is not customizing anymore, just masterdata in DGP2. Is that correct? Or can I make a direct link to the description?
- Because running the conversion report, every text (hazardous substances and user defined texts) are moved to phrases with CUST-xxxxxxxxxxx key. For us a problem because for us that key does not say anything, so probably we need to create new phrases. I have seen that there is CG3Y and CG3Z for uploading/downloading, but it expects /usr/sap/EHS_DATA/stocker/substanc.dat file for downloading. So is there an other way to upload our own phrases? so we can do a data migration from 46c to 604 without using the conversion report.
- In the tab 'printed text' of DGP2, you see the description of user defined text (UsDefTxt 1). Is there a way to change this description as this was possible in 46C.
- Is it possible not to use CUST- in for the phrases?
Any info would be appreciated! Thanks!

Answer 1

Hi, I set my question as answered as most of my questions have been answered or we have done some things differently. I just saw an other posting directing to this one so I sum up a little what we have done.
Please take in mind that we have the EH&S module but only use a small portion of the dangerous goods master (DGP2) as in only being able to put some info in the dangerous goods master, into the delivery documents. As I experienced from all the other sites this will be a bigger issue, but for the moment this is from the upgrade part:
1) Start first with setting the enhancement switch EA-PLM in customizing, else it will not work properly. See note 1157472 as in our case the menu structure was not visible in SAP menu.
2) Starting point (for us) has been note 692664. This report describes the steps you have to make to convert your texts with reports DGCONVERT used in the dangerous goods master (like texts maintained in DGTU and DGTD , specific and user defined texts). Read carefully as it seems that you must not run DGCONVERT for the same checkbox so do this step-by-step.
3) The UN number is not customizing anymore, you would have read it in note 1157472 already. This leads to converting. But the result is that you get stupid phrases (CUST-10000000012312). As the direct link to UN number and the description has been broken, we have finally created new phrases in the format like CUST-UN1133, so that the users at least know which description is the correct one.
4) For running the DGCONVERT you maybe endup in strange errors. The main cause was that the customizing and the texts must be maintained in the old system at least with AN translation in the language you run the report. Like the tables TDG33 (with text table TDG34) and TDG66 (with text table TDG67), we did not maintain every key in a language. So no empty values allowed. When one of them is empty in that translation, program stops. So we already prepared this in the old system. This also applies for the user defined text and standard text. At least the text translation must exist (and text maintained with at least an empty line) in one language. So if you have 100 texts maintained in DE and 2 are empty, we added the 2 in the system and run the program in DE language. That should work. Hope it's clear. Else ask an abapper, that's why I know this.
5) UN number / phrases / translation. In our case we do not get content (I do not know how this works and how and why). So our content is the old SAP version. Basically we did the DGCONVERT, then found out UN number was not nice, so downloaded TDG66/67.
- First we created LSMW to create the phrases in CG11. Ask your abaper to create one where you can maintain multiple languages.
- Next we linked the phrases to the correct phrase set in LSWM with CG12 to phrase set PHRASE_SET_UN_IDENTIFIER.
- Then we did an change DGP2 LSMW. Please be aware: slow!!! As we have couple of thousands materials we have to link to the new UN phrases, the performance is slow --> 20 hrs for us. (4400 materials).
6) Basically we did the same for our user defined texts. Only SAP converts them not in the correct fields, also the user defined texts are in 1 phrase set available (SAP_EHS_1022_042_TEXT). We have 5 user defined fields, and to be able to print correctly we have created 5 new phrase sets SAP_EHS_1022_042_TEXT_1 until SAP_EHS_1022_042_TEXT_5. Put the correct values in the phrase sets and then did a fresh change of masterdata DGP2 into the correct fields. In CGAB transaction you can change the phrase set to a new one (see note 632534 and look at the part: important information). In our case we linked in DGTM2:
PDGF5     User-Defined Text Key 5     SAP_EHS_1022_042_TEXT_5
PDGF4     User-Defined Text Key 4     SAP_EHS_1022_042_TEXT_4
PDGF3     User-Defined Text Key 3     SAP_EHS_1022_042_TEXT_3
PDGF2     User-Defined Text Key 2     SAP_EHS_1022_042_TEXT_2
PDGF1     User-Defined Text Key 1     SAP_EHS_1022_042_TEXT_1
7) As the conversion from 46C to 6.04 with DGCONVERT also created phrase sets for UN we actually did not want, it seems that the big amount of phrases in the phrase set is therefore slow, see point 5. So we deleted these, but also take into mind, with LSMW delete a phrase is also slow. So we think of the option not to convert this with DGCONVERT so we just do a fresh upload and link. Maybe this is faster. Currently busy with this.
8) During testing creating phrases, if you delete a phrase and create a new one with the same name SAP will give message. Run program RC1PHDEL to actual delete this from the database. See also note 1043546.
After this, we finally have everything back as we wanted and now we are able to print the data (with new selections on phrases) on our forms.
Hope this helps
Edited by: K. Peters on Apr 2, 2010 3:30 PM