ISTech Support Forum

ISTech Support Forum
http://www.istechforum.com/YaBB.pl
Evo-ERP and DBA Classic >> System Manager >> EDI : DE-P-B
http://www.istechforum.com/YaBB.pl?num=1175787902

Message started by RPCAdmin on 04/05/07 at 08:45:02

Title: EDI : DE-P-B
Post by RPCAdmin on 04/05/07 at 08:45:02

Allen or someone else - hopefully a simple one...

When importing an EDI order, on the ED-B screen, after it imports the DBASO.IN file, it asks "Do you want to clear the DBASO.IN file? If you hit yes, the DBASO.IN file stays in the directory (it is not deleted - it would be great if it did get deleted). Would it be possible to make this work? It would eliminate the need to manually delete this file before each new import, and simplify our EDI process immensely.

Thanks!!

Title: Re: EDI : DE-P-B
Post by kevind on 04/05/07 at 10:36:21

Make sure that SD-Q (Is Tech Support Configuration) has the option 'Remove EDI SO.IN file' is set to 'Y'.
This option is in the 'System Mgr' group button at the bottom of the SD-Q Screen.

Title: Re: EDI : DE-P-B
Post by RPCAdmin on 04/10/07 at 11:53:46

:-?I have that setting at Y and it still doesn't work. The DBASO.in file stays there even when you tell it to clear it. The only thing I can think of is that I changed the default directory that DBA looks into for the DBASO.in file. I may play with that a bit before I flatly say that it doesn't work!!

Title: Re: EDI : DE-P-B
Post by RPCAdmin on 04/10/07 at 12:00:27

Nope - tried a variety of directories and no matter what setting I use, the DBASO.IN file never goes away (is erased?) Unless the software means that it is taking the data out?? I haven't checked that, but I would rather just have the file be erased.

Title: Re: EDI : DE-P-B
Post by NovaZyg on 04/10/07 at 12:27:09

I'll take a look..

Title: Re: EDI : DE-P-B
Post by NovaZyg on 04/10/07 at 12:42:39

I looked..

msg "You have just imported " + trim(trim(str(head_cntr),'T'),'L') * " EDI SO headers, " + trim(trim(str(line_cntr),'T'),'L') * " EDI Line Items, and "+ trim(trim(str(note_cntr),'T'),'L') * " EDI Notes from "+trim(bkedi.mst.path,'T') * file_name * " Importing now complete. Proceed to view/edit in ED-C. " windows 'I'

if ists.cfg.csout $ "YA"
if ists.cfg.csout = "Y"
if .n. zask("Do you want to clear the DBASO.IN file?",.t.)
goto exit
endif
endif
close @in_file
if delf(path*'dbaso.in') = .f.
msg "Error deleting "+path*'DBASO.IN' windows 'i'
endif
endif

The code looks fine to me... Are you getting the question "Do you want to clear the DBASO.IN file?" when running DE-P-B? is your menu calling ISEDIB.RUN?

Title: Re: EDI : DE-P-B
Post by kkmfg on 04/10/07 at 19:39:45

Not to whip a dead horse into mush but.. since you did include some source code there...

You do realize that if we all had the source code we could debug ourselves, right?

For instance, in this case personal debugging would probably best go down this path:

First, reduce the source you posted to just:

msg "You have just imported " + trim(trim(str(head_cntr),'T'),'L') * " EDI SO headers, " + trim(trim(str(line_cntr),'T'),'L') * " EDI Line Items, and "+ trim(trim(str(note_cntr),'T'),'L') * " EDI Notes from "+trim(bkedi.mst.path,'T') * file_name * " Importing now complete. Proceed to view/edit in ED-C. " windows 'I'

close @in_file
if delf(path*'dbaso.in') = .f.
msg "Error deleting "+path*'DBASO.IN' windows 'i'
endif

This would remove all pertinent conditional expressions from the mix thus isolating whether the deleting statement is working. If it is then the conditionals I removed could be put back one by one until the problem is found (well, they should be commented out initially and uncommented in sequence but you get the point.) If, however, it still doesn't work then investigation into why not might be served by moving the message on failure out of the if block thus making it alway happen. Then the end user can see what path + file it's trying to delete.

All of this is to say, in the right hands end users having source can be a good thing. Some of us have enough experience with debugging to find the problem ourselves.

Title: Re: EDI : DE-P-B
Post by RPCAdmin on 04/11/07 at 04:53:23

Allen,

The code looks fine to me... Are you getting the question "Do you want to clear the DBASO.IN file?" when running DE-P-B? is your menu calling ISEDIB.RUN?

Yes, I definitely get the question "Do you want to clear the DBASO.IN file?"

No, it is running T6EDIB.RUN.

Also (not sure if it makes a difference), but we don't run CANDOEDI, so it is not running during these operations.

Title: Re: EDI : DE-P-B
Post by RPCAdmin on 04/11/07 at 04:57:25

Allen,

Actually, DE-P-B thru D are all running the T6 versions.

Title: Re: EDI : DE-P-B
Post by RPCAdmin on 04/11/07 at 06:09:15

Allen,

OK - it looks like the function works properly with the ISEDIB.RUN file but not with the T6EDIB.RUN file.

Title: Re: EDI : DE-P-B
Post by NovaZyg on 04/11/07 at 11:47:10

You were correct, the T6EDIB still had that bug, it was fixed in ISEDIB but not in T6, I just fixed it and sent to Lynn
The only difference between T6EDIB and ISEDIB is T6 lets you import 5000 lines and IS only does 500.

Title: Re: EDI : DE-P-B
Post by RPCAdmin on 04/11/07 at 11:57:30

Allen,

Don't think that will be an issue. I don't expect any of our PO's to be anywhere near 500 lines. If they are, I can ask Lynn to get me the updated versions of the T6 files, or if she reads this, she can e-mail them to me.

Thanks!! ;D