Hi all,

In all standard reports of ERPLn, the date is being printed as YYYY-MM-YY. How can we change the date format as DD-MM-YYYY in all reports. I hope it must be picking from some tools date format setting.

Awaiting help.

Vishal

In B4 , ttadv4180m000 has the date format and $BSE/lib/datecurr has date formats . Similar stuff must exist in Ln.

Hi

Please go through it

Dates

| Suppose date format 002 is: "year/month/day in month"
string result(80)
result = sprintf$("%D002", 727168)

| result contains "1991/12/2"

| Example of substitution symbol %D(format)
string result(80)
result = sprintf$("%D(Date: %02d/%02m/%04Y)", date.num())
| result contains "Date: 12/07/1993"
result = sprintf$("Date: %D(%02d %-20H %04Y)", date.num())

| result contains "Date: 12 June 1993"
UTC dates and times

| Date format 002 is "year/month/day in month"
| Time format 001 is "12 hour format:minutes:seconds AM/PM symbol"
string result(80)
result = springf$("%u002 %001", utc.num(), utc.num())

| Result contains "1997/01/01 10:02:53 pm"

string result(80)
result = sprintf$("UTC: %u(%02d/%02m/%04Y) %U(%02h%x%02m%x%025 %a)", utc.num(), utc.num())
| result contains "UTC: 22/07/1997 06:24:53 am"
| provided that for the user's language the time

| separator is ":" and the AM symbol is "am"

© 1998 Baan Development B.V. All rights reserved

Hi all,

I logged incident with Infor and Infor technical consultant guided to use session ttaad1510m000 (Software Languages). In this session we have to specify the sequence of each date part and do CRDD from specific menu, so that these settings are saved in datecurr file.

Further to give effect for all users, it is required to do CRDD for all user profiles. This brings desired date format in all reports without any modification.

Hope this helps.

Vishal

Hi all,

May I ask what is CRDD? We also need to set the desired date format for each client pc.

THanks in advance

Hi all,

May I ask what is CRDD? We also need to set the desired date format for each client pc.

THanks in advance

Hello,

CRDD stands for CreateRuntimeDataDictionary !

Regards

Dear all gurus

Our company is using LN6 with UNIX, and need your help.
After setting using session ttaad1510m000 (Software Languages). In this session we specified the sequence of each date part and done Convert Run Data Dictionary (ttams2200m000) from specific menu at Maintain User.
But the display for date format still fail to follow the date format Software Languages and also done setup the UNIX date format.

Are there anyone successfully using LN6 with UNIX OS for the mentioned steps above (i.e without setting all pc clients' date format)?

Please advise and thanks.

rgds
Brad

From reading this there are two crdd's that need to be done. First the one after you change the date format. Then you have to crdd on the users profile. Never done this myself - but did you do both CRDD's?

Hi Mark

Thanks for your prompt reply. Do you use LN6 with UNIX?
In LN6, what is CRDD for user profile?
Isn't the "CRDD for user profile" same as the "Convert Changes to Runtime Data Dictionary (ttams2200m000) from specific menu at Maintain User" (which was performed)?

I'm not sure how many are using LN6 with UNIX but successful do the above date format without setting it in every computer client.
Hope those gurus or others can help me.


rgds
Brad

Sorry - I don't use LN. I just know some sessions like this update some runtime data dictionaries. Then there is CRDD - which creates run time files for the users profiles. Again this is only what I know from the 4c4 side and ln could be completely different. Just reading this thread made it sound like 2 CRDD needed to be completed - one to make the change. Then another to make it active for the users.

Hello,

For LN !!!!

Software Languages (ttaad1110s000)
Use this session to maintain Software Language definitions that can be used in different applications.
Field Description
Language Select the Software Language of language-dependent parts of an application.
Data Language Select the Data Language that you want to link to the Software Language.
ERP LN displays application data in this data language, if no data language is specified in your user data. For details, refer to Multilanguage Application Data.
Date Format The sequence in which the date will be displayed for the specified language, in accordance with the date format defined in the Date Formats (ttadv4180s000) details session. To start the details session, double-click a date format in the Date Formats (ttadv4580m000) overview session.
Thousand Sign The sign used as the thousand sign for the specific language.
Note
This thousand sign is only applicable for figures other than amounts or prices, such as conversion factor in a unit, or a length or width in a bill of material, and so on. Thousand signs in amounts and prices depend on the thousand sign defined for the applicable currency. They can be defined in the Generic Units (ttaad1106m000) session.
Decimal Sign The sign used as the decimal sign for the specific language.
Note
This decimal sign is only applicable for figures other than amounts or prices, such as a conversion factor in a unit, or a scrap factor in a bill of material, and so on. Decimal signs in amounts and prices depend on the decimal sign defined for the relevant currency, as defined in the Generic Units (ttaad1106m000) session.
Date Separator The character used to separate the day, month, week and year, in a date displayed on a form or report for a specific language. This is used when the field Separator (no/language separator/specific) in the Date Formats (ttadv4180s000) details session has been filled with Language Separator. To start the details session, double-click a date format in the Date Formats (ttadv4580m000) overview session.
Time Separator The character used to separate the time, hours, minutes, and seconds, in a time displayed on a form or report for a specific language. This is used when the field Separator in the Date Formats (ttadv4180s000) details session has been filled with the Language Separator. To start the details session, double-click a date format in the Date Formats (ttadv4580m000) overview session.
Character Set Select the character set.
Character Set The description or name of the code.
Bi directional If this check box is selected, the characters can be used bi directional.
Description AM Enter the AM description for the selected language.
Description PM Enter the PM description for the selected language.

In session ttaad1110s000 :

date fiormat .
The formats are effected by the client, too.
(see date/time settings at your PC)

Regards

Dear all gurus

Thanks for all your suggestions even though I had in fact done all the suggested method (I actually followed one suggested earlier in this thread which need to run the 2 CRDD before I posted here).

Look like for LN6 UNIX OS, all pc windows clients need to be setup through the windows regional date format.
If anyone have solved it without setting it in all the pc clients, please let me know.

rgd
Brad

Hello Brad,

session Software Languages where you initially set the date format also has Specific/convert to runtime DD option, which in fact crates new datecurr file.

I just had the same problem today and succesfully solved it. Ijust edited format, then did above procedure on Software Languages session, logged out and logged in again. I didn't even CRDD users or profiles. It seems to me that the system reads datecurr file, which is currently on disk.

VishalMistry already described procedure, it works on ERP LN FP6.

Hi Justone

Do you really solve it but is it on UNIX server or Microsoft Windows server?
Also do your LN6 date format (what format date?) doesn't really follow your PC client windows regional date (what format date?) setting?
In Session Software Language date format , I key-in Day,Week, Month, Year but what did you key-in?


Currently in Baan4 running on UNIX is OK but in LN6 running on UNIX OS will the date problem.
Mine are still same problem, I need setup to all pc windows clients through the windows regional date format.

The datecurr file (both existing Baan4 & LN6) showed similarly contains :
D|0012|DMY|%02d-%02m-%02y|
D|0022|DMY|%02d-%02m-%04Y|
D|0032|DMY|%d-%h-%04Y|
D|0042|DMY|%d-%h|
D|0052|DMY|%02d/%02m/%02y|
and so on.

The $BSE/lib for all users in (both existing Baan4 & LN6) showed similarly contains following:
imeam: am
timepm: pm
dateformat:DDMMYY

But why Baan4 running on UNIX is OK but in LN6 running on UNIX OS will the date problem?

Since you successful solved in UNIX OS, appeciate if you can please help me?


rgds
KS







rgds
Brad

I had problem with fomat mm-dd-yyyy setting in english language since our local setting is dd.mm.yyyy.

Despite local Windows settings (which is dd.mm.yyyy), worktop displayed dates in mm-dd-yyyy format.

I did the change in attachment and converted it to runtime.

But as I'm thinking further you might have a different problem, where you want your local PC's to behave like LN does. Mine was quite opposite, since I only sinchronized LN with existing local setting.

What is you local PC (windows) setting?

Maybe I was a bit misleading, I just checked once agian, and it looks like there is na influence on the report, but not on form. I changed format on test system back to mm-dd-yyyy and did convert to runtime.

Attached is the influence on such setting on form and report. Obviously on fom level local (windows) setting is taken, but on report level unix setting is stronger (probably since report is created on server).

So in fact it should work, at least on my server, report is taking datecurr setting and ignoring local windows setting. But I didn't check the behaviour of BW print

Hi Justone

Thanks for your 2 replies.
In our local country, we use dd/mm/yyyy which is similar to yours.
I'm more concern on the PO, SO, Production and Inventory display (i.e not concern on report).
User may key-in wrongly in LN6 because 3/4/11 may means 3 April 2011 or 4 March 2011 depend on the local client PC setting.
In Baan4, it is not a problem.

You asked me what is my local(i.e client) PC (windows) setting?
There is no one my setting but many local client PC setting depending on the user.
We have many various for MANY local client PC(s) (windows) as it depends on whatever setting by users themselves.
But in Baan4, it is not a problem as all the local client PCs follows the Baan4 systems whereby Session Software Language date format which key-in as Day,Week, Month, Year.
Also in Baan4 HP-Unix server OS is setup for our country date format of dd/mm/yyyy.
Outcome: OK as all the Purchase, Sales, Production Orders and Inventory dates are displayed as dd/mm/yyyy.


But in LN6, which setup is exactly as Baan4 (including Session Software Language date format which key-in Day,Week, Month, Year).
And even the LN6 HP-Unix server is setup for our country date format of dd/mm/yyyy.
Outcome: FAIL as all the Purchase, Sales, Production Orders and Inventory dates are NOT displayed as dd/mm/yyyy.
It display in many various date format which according to whatever the users' local(i.e client) PC (windows) setting.

Based on your 2nd reply subject, "one more detail".
Correct me if I'm wrong that yours (for PO,SO,Production,Inventory "display" date) is actually not working (similarly to my condition)?

If yours really work using UNIX OS for the LN6, I hope you can further help me by explaining more detail to me.
(i.e all local client PCs to follow LN6 system, will display date dd/mm/yyyy in PO, SO, Production and Inventory date so that it can prevent user key-in error).

rgds
Brad

Hi all,

I would like to pick up on this old thread as I am facing a similar challenge now.

We would like to set up the date formats per country rather than per language which seems impossible in LN (FP7).

Brad, or anyone else, were you able to find any solution for this?

Regards,
Eli

Hi Vishal Mistry,

I got same problem with date format. As per your suggestion I am able to solve
the problem. Thanks.

Thank you! It helped me.