BaanERP (Grieg) The BEMIS V Cookbook (Structure, master data, and configuration of BEMIS V)

Transcription

1 BaaERP (Grieg) The BEMIS V Cookbook (Structure, master data, ad cofiguratio of BEMIS V)

2 A publicatio of: Baa Developmet B.V. P.O.Box AC Bareveld The Netherlads Prited i the Netherlads Baa Developmet B.V All rights reserved. The iformatio i this documet is subject to chage without otice. No part of this documet may be reproduced, stored or trasmitted i ay form or by ay meas, electroic or mechaical, for ay purpose, without the express writte permissio of Baa Developmet B.V. Baa Developmet B.V. assumes o liability for ay damages icurred, directly or idirectly, from ay errors, omissios or discrepacies betwee the software ad the iformatio cotaied i this documet. Documet Iformatio Code: U7315A US Group: User Documetatio Editio: A Date: August, 1999

3 Table of cotets 1 Itroductio: cocept ad structure of BEMIS V Master data i BEMIS V 2-1 Fudametal EDI parameters 2-1 Orgaizatio 2-3 New Date / Time Format 2-4 Networks 2-5 BEMIS Messages - Covetios 2-8 Messages 2-9 Maiteace of BEMIS V Message Versios 2-10 Namig of the Message File 2-13 Messages by orgaizatio 2-13 Busiess Parter EDI Data by etwork 2-14 EDI Messages Supported by Busiess Parter 2-15 Geeratio of outgoig messages Coversio settigs 3-1 Geeral iformatio Code tables ad coversio tables 4-1 Geeral iformatio 4-1 Code ad Coversios 4-2 Coutry Codes 4-2 Currecy Codes 4-4 Uit Codes 4-6 Order Types 4-8 Address / Parter Codes ID s 4-9 Address / Parter Types 4-10 Tax Codes ID 4-11 Tax Codes 4-12 Coversios by Busiess Parter 4-13 Item Code Coversios 4-13 Item Codes Evaluatio expressios 5-1 Applicatio of evaluatio expressios 5-1 Maiteace of evaluatio expressios 5-1 i

4 Table of cotets 6 Import ad export of the defaults.edi file 6-1 Startig positio 6-1 Export of EDI data 6-2 Import of EDI data Iterface 7-1 Overview etwork directories 7-2 Default commuicatio over the semaphores 7-3 Turig off the default commuicatio Glossary of terms ad abbreviatios 8-1 ii

5 About this documet This documetatio provides a overview over the BAAN Electroic Message Iterchage System (BEMIS V) for BAAN ERP. It describes the positioig, structure ad workig method, as well as the requiremets for the correct operatio. Furthermore, the ecessary data settigs, which support the correct cofiguratio of BEMIS V are described i detail. This documet is iteded for everyoe who wats to use the advatages of the EDI fuctioality i coectio with a BAAN ERP eviromet, as well as for every cosultat who implemets such a solutio. This documetatio does ot cotai a detailed or complete descriptio of the whole EDI fuctioality i BAAN, but is limited to the aspects cocerig BEMIS V. For further details about EDI, see the EDI Users Guide (U7100C US). Users Guides are also available for each of the specific file types supported by BEMIS V (for example, orders, orderrsp). After the Itroductio, this Users Guide is divided ito seve chapters: Chapter 1 describes the structure of BEMIS V ad its fuctioig as iterface betwee the EDI subsystem ad the BAAN ERP-System. It cotais defiitios of the idividual BEMIS V compoets ad their fuctios. Chapter 2 describes the master data settigs which are ecessary for the correct fuctioig of BEMIS V. Chapter 3 describes the coversio settigs which are ecessary for the correct fuctioig of BEMIS V. Chapter 4 describes the code ad coversio tables which are ecessary for the correct fuctioig of BEMIS V. Chapter 5 cotais iformatio about the used evaluatio expressios. Chapter 6 describes the import ad export of the defaults.edi file Chapter 7 describes the iterface betwee the EDI subsystem ad BAAN ERP. A glossary of terms ad abbreviatios is provided at the ed of the book. iii

6 About this documet iv

7 1 Itroductio: cocept ad structure of BEMIS V I commo BEMIS represets the stadardized iterface to import or to export No Automotive ad Automotive related messages.i the tradig busiess we ormally have to deal with EDIFACT messages. Lookig at the automotive idustrie i germay curretly the VDA stadard is used. I cotrast to that, the stadard ODETTE is used i other Europea coutries ad ANSI X.12 is used i the Uited States. Each stadard is distiguished from the others by differet trasmissio formats ad data iterpretatio. More ad more compaies are migratig to EDIFACT message stadard. Moreover the BEMIS V message stadard is ot oly desiged for exteral EDI. Aother focus i developemet was to make this stadard more suitable for Itercompay EDI i a BAAN ERP Multi Site eviromet. The BAAN Electroic Message Iterchage System (BEMIS V) has bee developed as fixed, stadardized iterface to the outside world of EDI to esure a cosistet processig of the differet stadards from the side of the BAAN ERP-System. BEMIS V make use of BAAN ERP stadard, i.e. the BAAN ERP stadard is used to stadardize a iterface. BEMIS V cosists of the followig compoets: BEMIS BEMIS Message Defiitios BAAN Stadard EDI Modul EDI DLL s BEMIS EDI-Default Data (defaults.edi) BEMIS Traiig Dipl. Ig. Jörg Buchholz

8 Itroductio: cocept ad structure of BEMIS V Therefore, BEMIS V provides the followig advatages for BAAN ERP Idepedece from which EDI stadard is used Process security whe usig aother EDI stadard Reductio of ecessity for developmet by cocetratig o oe iteral stadard ad for suppliers of EDI subsystems Possibility to estimate the ecessary efforts for the acquisitio to BAAN ERP. Reductio of developmet scope through defied iterface The diagram o the followig page shows the areas, i which BEMIS V ca be used i the EDI commuicatio chai. Betwee the EDI subsystems, messages are trasmitted with a certai stadard (for example, VDA, ODETTE) usig remote data trasmissio. The commuicatio betwee the EDI subsystem ad BAAN ERP is carried out via BEMIS V. BEMIS V cosists of several compoets to carry out its task i a flexible ad correct way, as is show i Figure 1. BAAN EDI / BEMIS V Compoets EDI Sub-System BEMIS V EDI Master Data BAAN ERP VDA ODETTE EDIFACT ANSI X12 BEMIS MESSAGE FILE Code- ad Coversio Tables BAAN Coverter Coversio Setup Modules DLL S Order Maagemet Warehousig Maufacturig Evaluatio... Expressio Dipl. Ig. Jörg Buchholz Figure 1, BEMIS V compoets 1-2

9 Itroductio: cocept ad structure of BEMIS V The idividual compoets have the followig fuctios: BAAN EDI i-house format iterface file The BAAN EDI i-house format iterface file serves as iterface to the EDI subsystem. A defied format is available for icomig ad outgoig messages for every message type supported. For icomig messages, the EDI subsystem creates from the received file a iterface file with the agreed format. For outgoig messages, BAAN ERP creates from BAAN data a iterface file with this format, which the EDI subsystem will process, covert ito a trasmissio file, ad trasmit. BAAN ERP EDI Coverter Outgoig: The EDI Coverter creates from BAAN data (for example, schedules, purchase cotracts) a iterface file with the appropriate format for the message type required. Icomig: The EDI Coverter creates from the iterface file the appropriate data (for example, schedules, ivoices), i the appropriate format, which will the be processed i the BAAN ERP modules. EDI Master Data The EDI Master Data provide fudametal iformatio about the fuctioality ad operatioal capacity of the system cocerig the etwork used, messages supported ad commuicatio parters ivolved. Coverter Settigs The coverter settigs cotai the istructios for the BAAN ERP EDI Coverter, icludig the format of the iterface file by message type ad trasmissio directio. These settigs defie for icomig messages how ad where the iformatio of the iterface file will be stored i BAAN ERP. For outgoig messages, they defie how ad which BAAN ERP data will be writte to the iterface file. Code Tables ad Coverter Tables The code ad coversio tables defie which data have to be coverted by the EDI Coverter for processig. That way, customer or supplier data (for example, item umbers, item codes, quatity uits) ca be coverted to BAAN ERP iteral data ad the other way roud. The coverter settigs determie whe these settigs are valid. Evaluatio expressios The evaluatio expressios defie the coditios uder which the EDI Coverter carries out certai actios. The coverter settigs determie whe these settigs are valid. 1-3

10 Itroductio: cocept ad structure of BEMIS V Dyamic Lik Libraries (DLLs) Dyamic Lik Libraries, which the EDI Coverter uses at lead time to carry out certai actios, are available for every supported message type, by trasmissio directio. They ca be adapted to the applicatio as required. 1-4

11 2 Master data i BEMIS V The followig parameters ad master data have to be defied, etered ad possibly maitaied to be able to use the BAAN Electroic Message Iterchage System V ad to esure its fuctioig: Orgaizatios Networks Messages EDI Busiess Parter Code Tables ad Coversio Tables The followig sectios detail the steps ecessary, ad illustrates them with examples. The data of the examples refer to the BAAN ERP iteral EDI subsystem BEMIS V. This system has bee developed to become idepedet of the various EDI orgaizatios/stadards, which are curretly used i the automobile idustry or i tradig busiess. Whe you set up your system, you should use the values give i the examples, or oly make chages if you are certai what the effect will be. Fudametal EDI parameters This sessio defies the fudametal parameters for the BAAN ERP EDI module. Some of them ca be redefied i other sessios. 2-1

12 Master data i BEMIS V EDI Implemeted Stadard Path Make use of Tracefile Our Idetificatio Referece Number Fixed Part Date Format First free umber Actio o First Message o New Date This field has to be set to Yes ad the BAAN ERP EDI module has to be istalled. This Uix / NT directory, where the messages ad cotrol files will be stored, is used for the commuicatio betwee BEMIS V ad the EDI-subsystem. The stadard directory is also used as the source for the default.edi. Whe processig messages, all actios will be recorded i a sub-directory ( Tracefile ) of the Stadard Path. This field cotais the etwork idetificatio of the trasmitter, which is eclosed i outgoig messages. (The ecoded umber of the compay from which the messages were geerated is usually eclosed as well). The message referece for outgoig messages will be geerated o the basis of the subsequet 4 fields. The message referece cosists of at maximum 14 characters ad cotais the fixed part/date/serial umber. This is the fixed part of the message referece. Differet date formats (for example, with or without cetury) ca be selected i this field. The selected format ca the be used for the date i the referece umber. Use without cetury here because of the fact that the referece umber is limited to 14 characters. The serial umber will be icreased from this umber. For every ew date the serial umber will be set back to

13 Master data i BEMIS V Orgaizatio I BEMIS V, the orgaizatios are used as commo stadard for the data trasmissio. These stadards are for example VDA i Germay (automobile idustry) or ODETTE i Europe. BEMIS V itself does ot use these stadards but a BAAN iteral orgaizatio/stadard BEM, which is able to support VDA ad ODETTE messages. These also meas that BEMIS V is the BAAN iteral message stadard comparable to exteral stadard like the metioed above. The orgaizatio BEM has to be etered i the BAAN sessio ecedi0503m000: 2-3

14 Master data i BEMIS V New Date / Time Format For the BAAN Versios b ad c2/3 we have defied a date format usig up to 6 umerical digits. Comig with BAAN IVc3scc1 the date format has bee chaged to 8 digits at maximum. Now with BEMIS V we have defied a ew date / time format. The ew format is ow: CCYYMMDDHHMMSS. The date / time iformatio is put as a umerical field to the positio withi the message. 2-4

15 Master data i BEMIS V Networks The fudametal commuicatio parameters (for example, stacker directories, structure of the message files, date formats, separators, ad special characters withi the message files) are defied i the etwork settigs. The etwork used for the commuicatio has to be etered i the BAAN sessio ecedi0520s000. Please defie a etwork for every message type. 2-5

16 Master data i BEMIS V Path Our Idetificatio Geeral Referece Fixed Part First Free Number Actio o New Date This Uix / NT directory, where the messages ad cotrol files will be stored, is used for the commuicatio betwee BEMIS V ad the EDIsubsystem. This field cotais the etwork idetificatio of the trasmitter, which is eclosed i outgoig messages. (The ecoded umber of the compay from which the messages were geerated is usually eclosed as well). The message referece for outgoig messages will be geerated o the basis of the subsequet 4 fields. The message referece cosists of 14 characters ad cotais the fixed part/date/serial umber. The BAAN compay umber has to be etered ito this field as fixed part of the geeral referece. The serial umber will be icreased from this umber. For every ew date the serial umber will be set back to 1 Example: O the basis of the above iformatio, the message referece umber for outgoig messages will be: F The first message referece umber for the ext day would be: F

17 Master data i BEMIS V The importat iformatio about the record format is etered i the secod form: Record Separator LF (LieFeed) idicates the ed of a record. Field type The idividual fields i the records do ot cosist of a certai umber of characters, but are separated by separators. Separator Sig The fields are separated by a semicolo (;) Sig Aroud Strigs Strigs have to be put i iverted commas ( ). Leadig Zeroes Fields are ot to be filled up with leadig zeroes, as the field type is delimited. Suppress Stadard The stadard commuicatio procedure betwee BEMIS Commuicatio V ad the exteral EDI subsystem is activated. Tip: If you wat defie a ew etwork please copy the default etwork BEMISV. Thus you will automatically get the correct settig for the delimiters. Examples:...; ABCDEFG ;... strig ABCDEFG...; ;... empty strig...; ;... strig with oe blak...;199;... umber ; 199 ;... strig ;;... Field will ot be read or filled. Date fields will be trasmitted as strigs. 2-7

18 Master data i BEMIS V BEMIS V Messages - Covetios The followig geeral rules apply to a message record i a BEMIS message file: 1 Every message record starts with SAx 2 Every message record eds with SAx_END 3 The legth of a data record ca vary. 4 The message record must cosist of all fields, eve if ot every field cotais a value. 5 The fields i the file must be separated by a ;. 6 A filled strig field have to be put i.... As defied i BEMIS a positio withi a message file is poited out usig two semicolos. To draw a example: p6$;p3rvlwlrqp6$;b(1'p If a positio i a BEMIS Message File is ot take by a value (this meas the positio is empty), the positio is poited out as show above. Moreover the BAAN EDI Module distiguishes betwee umerical ad alphaumerical data format. If a positio defied as umerical is empty the positio is poited out usig semicolos. O the other had empty alphaumerical positios are exported i two way. The first way is to poit out a positio usig the semicolos. The secod way BAAN exports empty alphaumerical positios is to write two iverted commads withi the positio. This depeds whether the alphaumerical field exists i BAAN s database or ot. Fially we take a look at the followig example: empty umerical Positio: p6$;pp6$;b(1'p empty alphaumerical Positio: p6$;pp6$;b(1'p or p6$;pppp6$;b(1'p 2-8

19 Master data i BEMIS V Messages You must defie the messages processed by BEMIS V i the BAAN ERP sessio ecedi0105s000. I that sessio you ca also defie message-specific sessios (DLLs), which have to be executed to process such a message. The geeral message ORD001 must have bee defied whe processig schedules i the BAAN EDI stadard ihouse format. Library for icomig/outgoig messages Processig type (i) File Layout Level Idetificatio Positio Level Idetificatio Legth The sessios used for the processig of messages will be recorded i this field. They are adapted to BEMIS V ad every message type. The system checks icomig EDI messages ad processes the messages without error. All record types of oe message are trasmitted i oe file (sigle). The first part of the record is the idetificatio of the record type. The idetificatio of the record type cosists of three characters I BEMIS V the idetificatio of the record type is by default SAx, with x = 1,2,3,... represetig the level of the record type (1 = highest level). 2-9

20 Master data i BEMIS V Maiteace of BEMIS V Message Versios Comig with BEMIS V, we itroduce a ew message amig ad versioig: a) Each message type is amed by abbreviatio ad its versio umber. To draw a example: ORD 001 Message Type: ORD for ORDERS Versio: 1 b) It is possible to defie differet releases to oe message, e.g. Release A, B,... a.s.o. Example: To draw a example: ORD001 A Release 2-10

21 Master data i BEMIS V I case of addig ew positios to message type a ew versio will be released. Therefore if you copy a coversio setup etry do ot use as a codig A, B, C,... We have the aim that the BEMIS V Message stadard fits to eeds of exteral ad iteral EDI. Hece we decided to deliver two differet coversio setups for oe release. Oe for exteral EDI ad oe for iteral EDI. The coversio setup für iteral EDI gets additioally the extesio I. The structure is the same. For the iteral EDI a coversio is oly for the busiess parter codes ecessary. Therefore the setup for the iteral EDI has a miimum of coversios. It is also possible to use the iteral setup for exteral EDI ad the other way aroud if additioaly coversio is eeded or ot. 2-11

22 Master data i BEMIS V To draw a example: Example: To draw a example: ORD001 A ORD001 AI Release A for exteral EDI Release A for iteral EDI 2-12

23 Master data i BEMIS V Namig of the Message File I order to make it more easier to use the BEMIS message stadard for Multi Site Eviromets, icomig ad outgoig messages have ow the same file ame. Moreover the ame of the message file is ow depeded from the message versio. To draw a example: file ame for Orders Versio 1: ord001.txt Messages by orgaizatio Followig the defiitio of the orgaizatio (that is, system) ad the messages, you defie which messages are supported, i which directio they are supported, ad which orgaizatio they are supported for. You ca also use this sessio to determie the code for the message i the message file (field code i message). Active Code i Message The correspodig message is activated i this orgaizatio. The processig/geeratio will be carried out whe this field is set to Yes. This code idetifies the message type i the message file. 2-13

24 Master data i BEMIS V Busiess Parter EDI Data by etwork Followig the defiitio of the busiess parter, you eed to assig him to a etwork i the BAAN sessio ecedi0128s000 for the commuicatio. I this sessio you eed to eter the etwork address of the busiess parter, which will be used i the message file. Network Address New Batch Number Icomig messages cotai this etwork address, which is used to determie the relatioship with the correspodig customer umber i BAAN. For outgoig messages (for example, schedules) use the umber of the relatioship here. A ew message referece umber is applied to for every ew message. This umber is used to idetify the records of oe message. Use here always: By Message NOTE Network Address BAAN creates by busiess parter (customer or supplier) ad message type oe etwork address, which is idetified by idetificatio ad path. This etwork address has to be uique. The EDI subsystem has to store a icomig message file from the busiess parter with the agreed file ame uder the correspodig path of the busiess parter ad message type. The idetificatio of the etwork address has to be writte to the record type SA1 i positio 3. For the idetificatio of cotracts, you ca determie i BAAN additioal busiess parters, for example the ship-to busiess parter, o the basis of the message cotets (plat/fial delivery locatio). The data of the etworks ad busiess parter idetificatios have to be settled amogst the EDI subsystem ad BAAN o the basis of the busiess parter relatioship. 2-14

25 Master data i BEMIS V EDI Messages Supported by Busiess Parter NOTE I the sessio ecedi0111s000 you defie which busiess parter ad which kid of message is liked to a particular. You also have to eter the coversio settigs to be used for the creatio or processig of the message with the BAAN iteral EDI coverter. These coversio settigs iform BEMIS V about the format of the message files as well as about possibly ecessary coversios of idividual field cotets of these files. The defiitio ad fuctioig of the coversio settigs will be explaied i the followig chapter. The below defied settigs for icomig schedules have to be etered by message. 2-15

26 Master data i BEMIS V Type of Number Prit Icomig Message Processig Type For icomig messages, the umber will be determied o the basis of the idicated type of umber ad the series o form 2-2 (ext page). Outgoig EDI messages will usually be created by a prit sessio. If No is etered i this field, the messages are created but ot prited. The system automatically checks ad processes icomig messages while readig the message file. 2-16

27 Master data i BEMIS V Geeratio of outgoig messages The geeratio of outgoig messages i BAAN ERP is usually prepared with prit sessios. After havig started the prit job, a message is prepared for the EDI module. The referece umber idicatig the outgoig message which has to be created will be stored i the table ecedi700. Based upo this referece, BEMIS V automatically or iteractively creates the actual message. These sessios are already programmed i the appropriate way. For example for: Message Sessio ORD001 tdpur4401m000 Prit Purchase Order The BAAN sessio ecedi0115m000 Outgoig messages by Sessio defies which message has to be prepared for which orgaizatio i the appropriate prit sessio. The correspodig orgaizatio ad message have to be etered to prepare the geeratio of schedule messages via the sessio tdpur4401m000 Prit Purchase Order. These etries are ecessary for the geeratio of outgoig orders. 2-17

28 Master data i BEMIS V 2-18

29 3 Coversio settigs WARNING Geeral iformatio Receivig a message file from the busiess parter, the EDI subsystem creates o the basis of the icomig stadard format (for example, VDA, ODETTE) a message file i accordace with the BAAN EDI Message i-house File Format. This file will be processed i BEMIS V ad the for this ecessary actios will be executed i BAAN. Sedig a EDI message to a busiess parter, BEMIS V creates from the BAAN data a message file i the BAAN EDI Message i-house Format, correspodig to the message type. This file will be processed i the EDI subsystem, coverted to a file with a stadard format (for example, VDA, ODETTE) ad set. All these iformatio, which BEMIS V requires for the processig (icomig ) or geeratio (outgoig) of the BEMIS V message file, are defied i the coversio settigs of the BAAN EDI module by message type ad message directio. The ame ad geeral iformatio about various record types as well as the idetificatio, umber ad positio of their key fields are recorded i the BAAN sessio ecedi5112m000. The detailed structure of the file i coectio with the liks betwee a message file field ad the correspodig BAAN table field is stored i the BAAN sessios ecedi5110m000 ad ecedi5110s000. Furthermore, you will fid i these sessios iformatio about liked code ad coversio tables or evaluatio expressios (outgoig), which will be used for the geeratio or processig of the BEMIS V message file. Chages of the default settigs give i the followig chapter will lead to malfuctioig of BEMIS V. 3-1

30 Coversio settigs 3-2

31 4 Code tables ad coversio tables Geeral iformatio I BEMIS V the code tables ad coversio tables icrease the flexibility of the data iterchage betwee BAAN ad the busiess parters. There are three kids of Code ad Coversio tables which are really importat for BEMIS: a) Codes ad Coversios b) Coversios by Busiess Parter c) Item Code Coversio 4-1

32 Code tables ad coversio tables Code ad Coversios Coutry Codes The code table Coutries, which cotais the allowed values for the coutry codes, will be maitaied by orgaizatio. The codes i this table refer to ISO4217. A coversio table, which defies the coutry code to be coverted, is available for both message directios (icomig/outgoig). The codes are agreed to by the EDI subsystem supplier. This code table will be imported usig a stadard BEMIS defaults.edi s. 4-2

33 Code tables ad coversio tables To draw a example here are the two sessio to maitai for icomig ad outgoig messages. Icomig: Outgoig: 4-3

34 Code tables ad coversio tables Currecy Codes The code table Currecies, which cotais the allowed values for the currecy codes, will be maitaied by orgaizatio. The codes i this table refer to ISO A coversio table, which defies the currecy code to be coverted, is available for both message directios (icomig/outgoig). The codes are agreed to by the EDI subsystem supplier. This code table will be imported usig a stadard BEMIS defaults.edi s. Like show above Currecy Codes have to be maitai for icomig ad outgoig messages. 4-4

35 Code tables ad coversio tables Icomig: Outgoig: 4-5

36 Code tables ad coversio tables Uit Codes The code table Uits, which cotais the allowed values for the uit codes, will be maitaied by orgaizatio. The codes i this table refer to Odette ODDC 25. A coversio table, which defies the uit code to be coverted, is available for both message directios (icomig/outgoig). The codes are agreed to by the EDI subsystem supplier. This code table will be imported usig a stadard BEMIS defaults.edi s. This is also oe of the code tables which has to be maitaied for the icomig ad outgoig directio. 4-6

37 Code tables ad coversio tables Icomig: Outgoig: 4-7

38 Code tables ad coversio tables Order Types To lik a Order Type to a outgoig message the followig sessio has to be maitaied. Thus the related prit sessio for outgoig orders will prepare edi messages. Please otice that the defied order type for this kid of message must be the same as defied i the followig sessio: 4-8

39 Code tables ad coversio tables Address / Parter Codes ID s After the import of the BEMIS V defaults.edi oe ew etry has bee added to table Tecedi218: This qualifier will be eeded as described i the followig sectio. 4-9

40 Code tables ad coversio tables Address / Parter Types The Address / Parter Types above will be imported. These qualifiers ad the Address / Parter Code Id ZZ are used to determie the Busiess Parter. To determie the busiess parter please refer to these examples: Icomig: 4-10

41 Code tables ad coversio tables Outgoig: Tax Codes ID This qualifier is used to covert the Tax Codes. It is a part of the distributed default.edi data. 4-11

42 Code tables ad coversio tables Tax Codes These are some sample codes which have to be agreed to the EDI parter system. Moreover this sessio is used to maitai the base table. The coversio tables for icomig ad outgoig messages refer to Tecedi212. Icomig: Please ote, that the coversio is also depedet o the coutry code. 4-12

43 Code tables ad coversio tables Outgoig: Coversios by Busiess Parter The followig Busiess Parter related Code ad Coversio Tables have to be maitaied if you eed the codes i a icomig or outgoig message. If you are ot sure about that please refer to the BEMIS V Message Defiitios: Coversio of Purchase Cotract Codes by BP Coversio of Forwardig Aget Codes by BP Coversio of Discout Codes by Busiess Parter Coversio of Discout Method by Busiess Parter Coversio of Lot Selectio Codes by Busiess Parter Coversio of Lot Code Id by Busiess Parter Item Code Coversios Item Codes I compariso to BAAN IV the coversio of the Item Codes (customer s item code) has bee chaged. BEMIS comes with two predefied qualifiers i order to determie the iteral item code. The Item Code Id s are used i order to distiguish betwee a geeral item coversio ad a coversio which is busiess parter related. 4-13

44 Code tables ad coversio tables Therefore two Codes for the Item System are defied. Lookig at BAAN ERP Commo data we will fid the used table to traslate the item codes: a) Geeral Code System: 4-14

45 Code tables ad coversio tables b) Busiess Parter specific Code System: The exported BAAN ERP Item Code is a strig with at maximum 47 digits. At miimum the item code cotais 10 digits. To draw a example:...1 (ie leadig blaks ad at miimum oe sig). WARNING The BEMIS V coverter settigs defie, if these tables will be used for the geeratio or processig of the message, by settig the coversio optio to Yes whe mappig the correspodig BAAN field. The followig chapter provides a detailed descriptio of the coverter settigs. The settigs of the code ad coversio tables of course deped o the requisitios of the busiess parters ad the capacity of the used EDI subsystem. Therefore, o the ext pages oly the default settigs for the correct processig of the BEMIS V i-house data formats will be described. The followig coversios will be described: Coutries (outgoig) Uits (icomig/outgoig) Release date (icomig/outgoig) Chages of the followig default settigs will lead to malfuctioig of BEMIS V. 4-15

46 Code tables ad coversio tables 4-16

47 5 Evaluatio expressios Applicatio of evaluatio expressios For the geeratio of outgoig messages it is possible to use evaluatio expressios i the coversio settigs. I this way a coditio is liked to a field which decides whether the field will be writte or ot. I additio the evaluatio expressios ca cotrol uder which coditios whole record types will be writte. Maiteace of evaluatio expressios The evaluatio expressios are recorded i the BAAN default text compoets. Importig the defaults.edi, the evaluatio expressios will be etered i the curret BAAN laguage versio. For example, if the curret laguage of the importig user is Germa the the evaluatio expressios will be imported ito the Germa text compoets. This eeds to be take ito accout whe settig up the BAAN EDI module because otherwise the i-house format files will ot be writte complete. 5-1

48 Evaluatio expressios 5-2

49 6 Import ad export of the defaults.edi file Startig positio Updates of the BAAN EDI fuctioality ca cocer the followig areas: Sessios Data Updates of the sessios will be executed with the BAAN default update procedure. O the ext pages will be described how to carry out updates of EDI relevat data (for example, implemetatio of ew messages or trasmissio stadards, format chages of messages files). The followig cases ca be executed with the available export ad import fuctioality: Backup of EDI basic data by export Recovery of EDI basic data by import Trasmissio of EDI relevat data from old ito ew compay by export/import Etry of all for EDI ecessary data for the empty compay by import Etry of data updates from BAAN by import 6-1

50 Import ad export of the defaults.edi file Export of EDI data To backup the EDI basic data, the easiest way is to export these data as a ASCII file usig the BAAN sessio ecedi6221m000 Export EDI Data. Code Tables Coversio Message Specificatio Orgaizatio EDI Message Network Code tables will be exported as well. Note: The correspodig coversio tables for icomig ad outgoig messages will ot be exported. The coverter settigs will be exported. Selectio of the orgaizatios to be exported. Selectio of the messages to be exported. Selectio of the messages to be exported. 6-2

51 Import ad export of the defaults.edi file The export icludes the followig EDI tables: BAAN table Descriptio Selectio coditio ecedi003 Orgaizatio accordig to selectio ecedi005 EDI Messages accordig to selectio ecedi001 Supported EDI Messages accordig to selected orgaizatio ecedi015 Outgoig Messages by accordig to selected messages sessio ecedi020 Networks accordig to selectio ecedi500 Coversio Setups (Name) accordig to selected orgaizatio if field set to Yes ecedi501 Coversio Setups (Defiitios) accordig to selected orgaizatio if field set to Yes ecedi502 Coversio Setups (Relatioships) accordig to selected orgaizatio if field set to Yes ecedi 505 Evaluatio Expressios all, if field coverter settigs set to Yes ecedi200 Order Types Accordig to selected orgaizatio if field set to Yes ecedi218 Address Code IDs Accordig to selected orgaizatio if field set to Yes ecedi224 Address / Parter Types Accordig to selected orgaizatio if field set to Yes ecedi226 Coutries Accordig to selected orgaizatio if field set to Yes ecedi228 Terms of Delivery Accordig to selected orgaizatio if field set to Yes ecedi230 Uits Accordig to selected orgaizatio if field set to Yes ecedi232 Item Code IDs Accordig to selected orgaizatio if field set to Yes ecedi240 Tax Code Id s accordig to selected orgaizatio if field set to Yes ecedi292 Currecies accordig to selected orgaizatio if field set to Yes ecedi294 Terms of Paymet accordig to selected orgaizatio if field set to Yes NOTE I geeral, all EDI data (for example, customers, suppliers, items), which cotai refereces to BAAN iteral data, but which do ot belog to the EDI module, will ot be exported. These data iclude the coversio tables which belog to the code tables, the additioal SCH coversio tables (requiremet types, requiremet frequecies, release date) ad the busiess parter idetificatio by etwork. 6-3

52 Import ad export of the defaults.edi file Import of EDI data The followig procedures are possible to establish a ew compay with all EDI relevat data: Maual etry of the required data Import of a file with EDI basic data ad maual completio of the missig data You will fid a detailed descriptio of the previous sectios. The secod method will be described i the followig sectio. For this method there has to be a export file of a EDI basic settig, which has bee created as described above. Aother coditio is the defiitio of the EDI parameter ecedi000. The file to be imported has to be stored uder the ame defaults.edi i the file path, which is defied i the field Stadard Path. 6-4

53 Import ad export of the defaults.edi file This file will be imported ito the ew (empty) compay i the BAAN sessio ecedi6220m000 Import EDI Data. Whe you importig data you must ote the followig poits: The error message Error opeig file fileame press <retur> appears: I this case the import file is stored i the wrog directory or has got the wrog ame. The error messages Default text group by user ot available appears: I this case you eed to create the correspodig text group for the importig user uder BAAN Tools / Text Maagemet / Text Parameters. 1. Maitai Text Widows Í create 2. Maitai Text Groups Í create 3. Maitai Default Text Groups by User Í create Whe you import, existig EDI basic data will ot be overwritte. Data with already existig key fields will ot be take over, ew data will be added. Whe you import, already-existig data i code tables will ot be overwritte. Data records with already existig key fields will ot be altered, ew data will be added. 6-5

54 Import ad export of the defaults.edi file Whe you import, already existig coverter settigs will be overwritte. To keep existig settigs, copy them to aother key field (orgaizatio, ame) before you start the import. Whe you import, a selectio is ot possible. All data of a file will be imported uder cosideratio of the above metioed restrictios. If the correspodig Uix directories are ot available durig the import of the etwork data, a error messages appears o the scree. Nevertheless, the data will be imported ad the directories have to be created afterwards. The import icludes the followig EDI tables: BAAN table ecedi003 ecedi005 ecedi001 ecedi015 ecedi020 ecedi500 ecedi501 ecedi502 ecedi505 ecedi200 ecedi218 ecedi224 ecedi226 ecedi228 ecedi230 ecedi232 ecedi240 ecedi292 ecedi294 Descriptio Orgaizatio EDI messages Supported EDI messages Outgoig message by sessio Networks Coversio setups (ame) Coversio setups (defiitios) Coversio setups (relatioships) Evaluatio expressio Order types Address code IDs Address / Parter Types Coutries Terms of delivery Uits Item code IDs Tax Code Id s Currecies Terms of Paymet 6-6

55 Import ad export of the defaults.edi file The followig data have to be maitaied maually (this is ot a complete list. please refer to the message defiitios): BAAN Table Descriptio Lik to BAAN Master Data ecedi011 EDI Messages supported by Busiess Parter Busiess Parter ecedi028 ecedi432 ecedi433 ecedi302/440/ ecedi300/430 ecedi304/442 ecedi306/444 Busiess Parter EDI by Network Coversio of the Sales Order Types (out) Coversio of the Purchase Order Types (out) Coversio of Coutry Codes (i/out) Coversio of Delivery Coditio Codes (i/out) Coversio of uit codes (i/out) Coversio of Item Codes by Relatio (i/out) Busiess Parter Order types Order types Coutries Terms of delivery Uits Item master data To import a ew defaults.edi: Whe you import a curret defaults.edi file, you are recommeded to carry out the followig procedure to update the coversio tables (especially the tables TBecedi500 ad TBecedi501). Before startig the import you are recommeded to store the curret coversio settigs uder a differet ame ad the to delete the old settigs. You ca the start the import of the ew defaults.edi file. 6-7

56 Import ad export of the defaults.edi file 6-8

57 7 Iterface This chapter describes the techical lik betwee the BAAN Electroic Message Iterchage System BEMIS V ad the correspodig EDI subsystem. You must take ito accout the followig two compoets whe lookig at the iterface betwee the EDI subsystem ad the default software of BAAN ERP: The BEMIS V i-house files to be exchaged The commuicatio method ecessary for the exchage EDI subsystem EDI subsystem BAAN IV Commuicatio level: Remote data trasmissio (e.g. VDA messages) Commuicatio level BAAN/EDI subsystem: Exchage of BAAN i-house Format files Figure 2, Commuicatio method Separate User Guides are provided which describe the BEMIS V i-house file formats. I this chapter, commuicatio methods are described which give a well-ordered ad error-free exchage of the BEMIS V message files. The geeral fuctioig of the BAAN EDI module is also described. I BAAN ERP, data are geerally exchaged o the basis of semaphores. With the help of a shell script this exchage ca be carried out i a more flexible way. Furthermore, the BAAN EDI module ca geerate or record messages over its iteral job maagemet with the crotab file. 7-1

58 Iterface Overview etwork directories The so-called etwork directories form the basis of the commuicatio betwee the EDI subsystem ad BAAN ERP. These directories are established i BAAN. The etwork basis directories for each etwork will be defied i the BAAN sessio ecedi0120m000. For the etwork BEMIS V, the basis directories ca be idicated i the followig way: $BSE/bemisv/ord001 $BSE/bemisv /ti001 BAAN will additioally create the followig subdirectories: $BSE/bemisv/ord001/appl_from/ $BSE/bemisv/ord001/appl_to/ $BSE/bemisv/ord001/commad/ $BSE/bemisv/ord001/store_recv/ $BSE/bemisv/ord001/store_set/ $BSE/bemisv/ord001/trace/ The above directories have the followig fuctio: 1.../appl_from/: I this directory, BAAN ERP records the outgoig messages which are the defied BEMIS V i-house format files. The EDI subsystem ca collect them from here. 2.../appl_to/: The EDI subsystem writes the icomig message ito this directory i the BAAN ERP i-house format. 3.../commad/: Directory of the semaphores. 4.../store_recv/: BAAN ERP stores i this directory processed icomig messages, if the cofiguratio is accordigly. Durig this process a additioal subdirectory by icomig message file will be created which is amed with a date ad time stamp idicatig whe the message was moved. 5.../store_set/: BAAN ERP stores i this directory processed outgoig messages if the cofiguratio is accordigly. Durig this process a additioal subdirectory by outgoig message file will be created which is amed with a date ad time stamp idicatig whe the message was moved. 6.../trace/: BAAN creates uder this directory a log of the icomig ad outgoig messages i the processig order, if the cofiguratio is accordigly. 7-2

59 Iterface Default commuicatio over the semaphores I geeral, the BAAN ERP EDI subsystem works i two phases: Firstly, the outgoig messages will be created ad secodly, the icomig messages will be read. I the directory.../commad will be defied, if BAAN ERP or the EDI subsystem writes or reads. The followig poits describe the order for the exchage of the temporary format files: 1 The commuicatio betwee BAAN ERP ad the EDI subsystem is oly possible, whe the correspodig etwork has bee activated. BAAN ERP checks the correspodig directory.../commad for the semaphore comm.yes. If this semaphore is ot set, the the etwork for BAAN ERP has ot bee activated ad the EDI subsystem is ot ready for commuicatio. 2 After the EDI subsystem has set comm.yes, BAAN ERP geerates a correspodig message file i the directory.../appl_from/. Before writig the outgoig message file, BAAN ERP geerates a log file i the directory.../trace/. 3 After BAAN ERP has geerated the message file, the semaphore commad.fil is writte ito the directory.../commad. BAAN ERP the waits util this semaphore is deleted by the EDI subsystem. 4 The EDI subsystem reads the messages which BAAN ERP geerated i the directory.../appl_from/ ad writes the icomig messages ito the directory.../appl_to/. 5 After havig fiished this procedure, the EDI subsystem deletes the semaphore commad.fil i the directory.../commad. 6 The BAAN ERP starts to record the message files, which the EDI subsystem stored i the directory.../appl_to/. This procedure will also be logged i the directory.../trace/. 7 BAAN will copy the message geerated by BAAN ad the icomig message file from the EDI subsystem ito the directory.../store_set/ or.../store_recv/. 8 BAAN ERP writes the semaphore commad.ed ito the directory.../commad. This step brigs the commuicatio betwee the EDI subsystem ad BAAN ERP to a ed. 9 Fially, the EDI subsystem deletes the semaphores comm.yes ad commad.ed i the directory.../commad. 7-3

60 Iterface Step The followig table displays a overview over the used patter of the semaphores: Semaphores i directory.../commad BAAN writes semaphore(s) EDI subsystem writes semaphore(s) EDI subsystem deletes semaphore(s) Status commuicatio I. empty Network directory deactivated II. comm.yes Network directory activated by EDI subsystem III. comm.yes Commad.fil BAAN ERP has geerated messages IV. comm.yes commad.fil The EDI subsystem records commad.fil outgoig messages or writes icomig messages V. comm.yes BAAN ERP reads icomig messages ad stores them VI. comm.yes commad.ed Ed of commuicatio VII. comm.yes commad.ed comm.yes commad.ed Discoectig etwork VIII. Network deactivated 7-4

61 Iterface Turig off the default commuicatio BAAN ERP geerates or reads messages, eve if the commuicatio based o semaphores i BAAN has bee tured off. Please ote the followig poits: Whe BAAN geerates ad stores messages i the directory.../appl_from/, these messages will either be deleted or copied. The message file which has bee geerated by BAAN will be stored i the directory. Whe ew messages are geerated, they will be appeded to the old message file i the directory.../appl_from/. Message files, which have bee stored i the directory.../appl_to/ by the EDI subsystem, will be deleted after BAAN has read them. If this commuicatio method is beig selected, the EDI subsystem has to guaratee, that: Icomig ad outgoig messages have to be stored i the BAAN i-house format Outgoig messages have to be deleted i the directory.../appl_from/ after beig trasmitted to the EDI subsystem. 7-5

62 Iterface 7-6

63 8 Glossary of terms ad abbreviatios appl ANSI BEM BEMIS V Busiess parter C defaults.edi DELINS EDI Applicatio America Natioal Stadards Orgaisatio Baa Electroic Message - abbreviated form of BEMIS V used with the defiitio of the EDI orgaizatio Baa Electroic Message Iterchage System for BAAN ERP Customer or supplier Coditioal, that is, optioal message Export file detailig master EDI data Odette Delivery Istructio (Schedule) Electroic Data Iterchage; electroic exchage of documets i stadard formats EDIFACT Electroic Data Exchage For Admiistratio, Commerce ad Trasport. A ISO stadard. ELP Exteral Logistic parter evaluatio expressio If statemet i the coversio setup for outgoig messages ISO Iteratioal Stadards Orgaizatio ISO 4217 Code table M Madatory (compulsory) message MAIS Geeral Motor s iterpretatio of the subset of EDIFACT DELJIT Message Messg Message etwork address Folder (directory) path o etwork ODDC Oddette Code Table ODDC25 Odette Code Table 25 ODETTE Europea stadard for electroic data exchage Org Orgaizatio, that is, system SCH Supply Chai Semaphore Method to show a status usig files with zero legth Traslatio Coversio of oe data format to aother, for example Baa i-house data format to ODETTE 8-1

64 Glossary of terms ad abbreviatios VDA X12 Stadard used for electroic data exchage i Germay Stadard used for electroic data exchage i the Uited States 8-2