mkkaleem
17th October 2012, 15:14
Hi
I tried to import baan4 customized sessions in LN FP7.
During the import I got error.
I need your help.
Thanks in advance.
This log file details:
2012-08-25[15:09:48(UTC-02:00)]:baan: Repair cpac vrc structure for tr
2012-08-25[15:09:48(UTC-02:00)]:baan: Repair cpac vrc structure for ts
2012-08-25[15:09:48(UTC-02:00)]:baan: Error 205 on ttadv401.ctnm
2012-08-25[15:09:48(UTC-02:00)]:baan: ttadv401.cdom = fea.barbutdi
2012-08-25[15:09:48(UTC-02:00)]:baan: ttadv401.cnst = 15
2012-08-25[15:09:48(UTC-02:00)]:baan: ttadv401.cpac = sa
2012-08-25[15:09:49(UTC-02:00)]:baan: ttadv401.ctnm =
2012-08-25[15:09:49(UTC-02:00)]:baan: ttadv401.cust = mash
2012-08-25[15:09:49(UTC-02:00)]:baan: ttadv401.rele = c4
2012-08-25[15:09:49(UTC-02:00)]:baan: ttadv401.vers = B40m
2012-08-25[15:09:49(UTC-02:00)]:baan: ttadv401.za_clab =
jclju1
18th October 2012, 13:53
Can you explain more what are you doing? You exported SW from Baan IV and now you are trying to import it into ERPLN?
mark_h
18th October 2012, 14:53
Can you explain more what are you doing? You exported SW from Baan IV and now you are trying to import it into ERPLN?
That is how I take it - they created an customization in baan 4 and trying to import it to LN. I assumed they used an export of software components. I am not sure that would work from 4 to ln. Then again I do not know anything about LN and importing custimizations on it.
jclju1
18th October 2012, 15:09
In my opinion, this scenario is not possible. Tools tables in these two versions are different, table ttadv401 for example, has an additional field in ERPLN.
jclju1
18th October 2012, 15:10
And also there are differencies in SW - dynamic forms, reports and forms layouts are not language dependent components, ....
mkkaleem
19th October 2012, 01:06
Thanks for reply.
ok first ill explain completely what i need.
1.We are using baan 4 past few years at that time there is lot of customization session in 4.
2. Now we are planning to migrate LN FP7 because there is lot of new functionality added.
3. Our main problem with Customization component
In Baan 4 one complete custm package is there, we want same package in LN . i tried different ways.
First i tried from baan 4 Export component session
Next In LN tried to Import that baan 4 Export component.
During import i got above error.
Can you suggest me is there any different ways or not.
Thanks in advance
sanjana
19th October 2012, 07:36
First you have to make the patch in baan 4 for all ur components , then create the same module in LN ,link the package & module, transfer the patch in LN server , then import the patch in LN through session ttiex1285m000 .
You will get all your components in LN . Then you have to Convert the sessions to dynamic through session ttadv2900m000.compile the script & session , then run ,your session will be opened.
grzegorz
26th October 2012, 14:45
The problem is rather complicated. You will meet at least three categories of issues:
- functional : you must decide whether your customization is still required; some requirements that needed customizations in Baan IV may be covered by existing LN functionality
- conceptional : there are so many differences between BaaN IV and LN flow of operations; many customizations may have to be redesigned deeply
- technical : moving software components from Baan IV to LN is in common not possible with Export/Import Runtime DD or PMC; there is a lot of manual work.
Of course, your effort depends on number of customizations you have and how deep they touch standard functionality. There are major table changes in practically all modules - new tables, old tables renamed, domains changed etc.
Many sessions are different than they were in Baan IV, so if you used AFS to perform some tasks, you must redesign your code. Even if you used only your own tables, you still have to redesign your application to make it consistent with LN "look and feel"; there are dynamic forms, no more "choice.user.*" events and many other changes.
So IMHO its is not impossible to move your customizations to LN, but it is not easy at all.