VERSION(S):
E-Sales 2.2

SITUATION IDENTIFIED IN:
E-Sales 2.2.1

====================================
SITUATION DESCRIPTION

E-Sales / Baan EDI does not make use of the semaphore functionality
with the result that orders can be lost.

====================================
SOLUTION DESCRIPTION: 


Note new functionality!!

To export orders to 
- local webserver or 
- share or 
- ftp location (Baan on a Unix Server)

manager--->ESales--->OrderExportFile

[
example: Order Export File paths
ftp://user:password@servername/edi/appl_to/order.e11
D:\Program Files\Baan-EDIData\E20SLS\appl_to\order.e11
\\computername\Baan-EDIData\E20SLS\appl_to\order.e11
]

Per BISInstance is also possible to define the timeout of the ftp connection (default = 3 sec)
manager-->EDashboard--->BisInstances--->BisPropertyValues

Info about Semaphore functionality:
By running Service Order Export

There are different new submitted orders with different Edifilename paths (different locations per BISID)
 
- Create command folder and command\comm.yes file (if necessary)
- Check command.fil exists
- Check if EdiFile exists in appl_to folder
- There are four different situations: BaanEdi session starts (only if comm.yes is present). 
It puts command.fil in command folder. Esales is allowed to write. 
If order export service has finished ESales deletes command.fil. 
BaanEdi is allowed to move the EdiFile to the store_recv directory. 
If BaanEdi sessie starts again, it puts command.fil in Command folder


a.	Command.fil exists  and EdiFile exists in appl_to 
Esales is allowed to write. Add items to EdiFile and delete command.fil

b.	Command.fil exists  and EdiFile DOESN’T exist in appl_to
Esales is allowed to write. It creates an EdiFile, adds items, and delete command.fil

c.	Command.fil DOESN’T exist  and EdiFile exists in appl_to
Esales is NOT allowed to write

d.	Command.fil DOESN’T exist  and EdiFile DOESN’T exist in appl_to
Esales is allowed to write. It creates an EdiFile and adds items.


If BaanEdi sessie starts again, it put command.fil in Command folder
If there aren't orders to process, ESales will delete command.fil 


The solution can be found on the Support FTP Site. 

It contains 2 files.

1 - readme.txt: This solution description

2 - 221_119501.exe
       Copy this file to your local web server. Extract to a temp folder and run the install.exe. This installation program will execute the following tasks:
	-	Check on pre-requisites and dependencies
	- 	Detect the current configuration settings
	- 	Create a pre-install report for customizations
	- 	Install the Webapplication files
	- 	Install/register Com and MTS Components
	- 	Backup the customized files and copy these files in a sub folder of the E-Enterprise installation folder.
	- 	Create a log file for each installation task and place these files in a sub folder of the E-Enterprise installation folder.
	-	Update the Registry and Metabase after the installation


The extracted solution folder contains 3 files 

	1. ESales.dll	
	2. EEOrderProcess.dll	
	3. Ftp_Timeout.sql  (Database EDashboard - BisProperty table is updated)

========================
PATH TO SOLUTION: 

ftp://ftp.support.baan.com/updates/E-Enterprise/E-Sales/2.2.1/ 2.2.1.119501