NLS Lookup Problem

[Berke]

Hello Erman,

Today, we were trying to detect and correct our NLS conversion errors by following your article "http://ermanarslan.blogspot.com.tr/2013/05/investigating-ebs-nls-data-load-problems.html"

But we weren't able to solve one of our problems which was uploading the correct translation for a value set. The picture below summarizes our problem.



Then we found the name of the module with the forms name.



We then found the ldt.

[applmgr@T1VSTEBSAPP01 US]$ find ./ -name "*.*" -exec grep -Hsi 'Civil War Invalid' {} \;
./loc_ro/perzzlookup00000.ldt:    MEANING = "Civil War Invalid"
./loc_ro/perzzlookup00000.ldt:    DESCRIPTION = "Civil War Invalid"
./loc_kr/perzzlookup00000.ldt:    MEANING = "Civil War Invalid"
./loc_kr/perzzlookup00000.ldt:    DESCRIPTION = "Civil War Invalid"

I found the lct by reading the ldt file.



Then I tried the following command but failed.






What could be the problem?

Thanks

[Berke]

Hi,

I have attached a couple of files. First is adident Header results of the fmb and fmx files. Then I put the aflvmlu.lct and perzzlookup00000.ldt files for examination.

Below is the link.

Files.rar

Thanks,

[ErmanArslansOracleBlog]

Hi,

Does the ldt that you are trying to upload contains the correct translation for the data? I mean, you checked the ldt right? Please check the lct too.
If they are both correct.
Then please walk through the steps documented in the following docs:
Troubleshooting Incorrect Translations with FNDLOAD (Doc ID 299080.1)
Troubleshooting NLS issues with Oracle Applications (Doc ID 1478859.1)

If the issue persist, send me an update.

[ErmanArslansOracleBlog]

I think that ; the mesage "No data found for upload" may be actually caused by ORA-01403 which is No Data Found Oracle Error. On the other hand, FNDLOAD may masking the ORA error messages..

FNDLOAD may be selecting from some TL tables , and can not find what it needs.
Something like this : EBS 12.1.3 Upgrade Fails at ap12alu.ldt With ORA-01403: No Data Found (Doc ID 1595582.1)  -- this is for 12.1.3 but your case may be similar.

Set the event in the database; and send me the trace file.. If it is really caused by ORA-01403 , we can see it in the trace.. we can see the failing sql and values too..

event = "1403 trace name errorstack: 10046 trace name context forever, level 12"

[Berke]

Hi,


Regarding the first update, In ldt which is found under the "/u01/install/APPS/fs2/EBSapps/appl/per/12.0.0/patch/115/import/US/loc_kr" there are english translations. However under the ldt found in the /u01/install/APPS/fs2/EBSapps/appl/per/12.0.0/patch/115/import/TR/loc_kr there are not any Turkish translations.


The lct file that I have mentioned has only the queries which doesnt explain much therefore I couldnt verify
it.

I have checked NLS Translation Troubleshooting guide and formed my FNDLOAD command accordingly. When I issued the find command, it gave me the ldt. Then I checked the ldt and found the lct.  

I have also analyzed the part where it talks about the forms translation issues but It didnt solve my problem.

I have recompiled this particular form in case there may be a problem reagarding it but it didnt change.

[ErmanArslansOracleBlog]

/u01/install/APPS/fs2/EBSapps/appl/per/12.0.0/patch/115/import/TR/perzzlookup00000.ldt contains Turkish translations right?


If it is correct, please set the ORA event, and reproduce the issue.
Then attach the relevant trace file.

[Berke]

No it doesnt have the turkish translations. I will be attaching the ldts.

[Berke]

Hi,

I have attached the perzzlookup file. In it you may find the corresponding lookups,ldt and lct files.
Perzzlookup.7z


[applmgr@T1VSTEBSAPP01 115]$ find . -name perzzlookup00000.ldt
./import/US/loc_ro/perzzlookup00000.ldt
./import/US/loc_kr/perzzlookup00000.ldt
./import/US/perzzlookup00000.ldt
./import/TR/loc_ro/perzzlookup00000.ldt
./import/TR/loc_kr/perzzlookup00000.ldt
./import/TR/perzzlookup00000.ldt


In summary Turkish ldts dont have any translations and the lct file doesn't give us anything therefore it is logical that our command didnt execute. Do we need to ask for a TSP?

[ErmanArslansOracleBlog]

I think this is a translation bug ..
There arent any directory named loc_tr  in the PER_TOP , and there arent any translation files in the filesystem. I have checked another EBS 12.2 environment and I have seen the same problem in the PERWSDIS .
Workaround can be manually preparing a LDT with the translated words in it, and loading it using FNDLOAD. But, I suggest you to open a bug record for this.
I will also open one..

[ErmanArslansOracleBlog]

Alternatively, you can edit/modify the file perzzlookup00000.ldt in $PER_TOP/patch/115/import/US/loc_ro/perzzlookup00000.ldt , change the meaning 's to be in your language for example: War Orphan = Savas Yetimi (in turkish)..
and use something like the following to upload it..

FNDLOAD apps/apps 0 Y UPLOAD /u01/install/APPS/fs2/EBSapps/appl/fnd/12.0.0/patch/115/import/aflvmlu.lct /u01/install/APPS/fs2/EBSapps/appl/per/12.0.0/patch/115/import/US/loc_ro/perzzlookup00000.ldt UPLOAD_MODE=NLS WARNINGS=TRUE


This will solve your specific nls translation issue. On the other hand, this time all the users(even US users ) will see only the translated values..
So it s better to open an SR to record a bug for it.

[Berke]

Hi,

To avoid such an issue, should we create a  loc_tr directory unde $PER_TOP/patch/115/import/TR and then place the editied file to there. Then we may issue the same command?

[erman]

please read my previous update

[Berke]

Sorry about that. You are right. We have opened a SR. We will update you when this issue is concluded.

Thanks

[ErmanArslansOracleBlog]

Any news Berke?

[Berke]

Not yet. I dont know if you can see the SR but we are waiting for a response.
Below is the SR if you can search for it.

Severity 2 SR 3-10717221841 : Oracle EBS NLS Lookup Problem

[Berke]

Hello Erman,

I was wondering if you have anything new on your end? Did you by any chance find the solution?

Thanks

[ErmanArslansOracleBlog]

hi Berke,

This problem identified in this issue, should be fixed by a new NLS patch. This is a bug or constraint in NLS patching of EBS 12.2.
So I was waiting for your update actually :)
What about the SR that you have created for this? Did you request the patch?

[Berke]

Hi,

They are still working on it however they weren't able to find anything yet. They didnt ask for a TSP Patch.
I will be updating you with the results.