yxylog101
31st July 2013, 09:30
We are using baan4c4 and our supplier is usinginforLN.
If we want sending our edi purchase to supplier,although both of baan4c4 and inforLN is using BEMIS standar,caninforLN read the edi data from baan4c4
without translate ?
Or we must use a EDI translator for interchange EDI data between Baan4c4 and inforLN?
which edi translator is recommended ?

Thanks!

bdittmar
31st July 2013, 10:06
We are using baan4c4 and our supplier is usinginforLN.
If we want sending our edi purchase to supplier,although both of baan4c4 and inforLN is using BEMIS standar,caninforLN read the edi data from baan4c4
without translate ?
Or we must use a EDI translator for interchange EDI data between Baan4c4 and inforLN?
which edi translator is recommended ?

Thanks!

Hello,

we use this scenarion between our BaaN IV and LN sites without an external EDI Translator.

Regards

yxylog101
31st July 2013, 10:41
Thank you!
Could you tell me how do you make it between our BaaN IV and LN sites without an external EDI Translator.
Because I asked infor Xtreme,and they tell me we need a external EDI software package to read the file according to the new structure
by KB 1150761
https://www.inforxtreme.com/espublic/EN/AnswerLinkDotNet/Solutions/ViewSolution.aspx?Solutionid=1150761
Structure of EDI messages in Baan IV and ERP LN
--------------------------------------------------------------------------------

Attachments (0) | Linked KBs

--------------------------------------------------------------------------------

Description:
The structure of the EDI files is different between BaanIV and ERP LN:
In Baan IV the files looks like this:
Header
Line 1
Details for line 1
Line 2
Details for line 2
.
.
And in ERPLN:
Header
Line 1
Line 2
Detail for line 1
Detail for line 2
.


Steps To Reproduce:

The data structure is indeed different between BaanIV and ERP LN.
The BEMIS definition of the EDI messages in ERP LN has been designed in such a way that the structure is :
SA1
SA2
SA3
SA3
SA5
SA5
SA6
SA6

etcetera.
This is by design.
It would require a redefinition of the EDI conversion setups to change this.
The best way forward is to modify the external EDI software package to read the file according to the new structure.