Nigel,
Thanks for the input. We are not using Service Connect, we are
calling the web services directly for a number of things within our
internally developed Intranet so we did the same thing with this project.
Yep, 6000 lines is not out of the ordinary for us. We sell graphic
signage to retail operations and when they are opening a new store or
if they are pushing out new signs to all their locations the orders
get pretty large. In this case, if you go down to the sales kit
contents there are a total of about 55,000 lines!
We are considering writing directly to the database but our director
of IT wants us to exhaust all other avenues first.
Thanks for the input. We are not using Service Connect, we are
calling the web services directly for a number of things within our
internally developed Intranet so we did the same thing with this project.
Yep, 6000 lines is not out of the ordinary for us. We sell graphic
signage to retail operations and when they are opening a new store or
if they are pushing out new signs to all their locations the orders
get pretty large. In this case, if you go down to the sales kit
contents there are a total of about 55,000 lines!
We are considering writing directly to the database but our director
of IT wants us to exhaust all other avenues first.
--- In vantage@yahoogroups.com, "Nigel Kerley" <nigel.kerley@...> wrote:
>
> Hi Joe,
>
> By "web services" do you mean Service Connect? If so, then we have
> found out when loading in multiple EDI POs that Service Connect likes
> multiple smaller individual files, rather than one large file.
>
> We regularly have Sales Orders of c.100 lines and we either paste
> them in or use a Service Connect workflow. Am I reading you posting
> correctly - you have an order with 6000 lines? Based on our
> experiences of 100 lines, I just shudder to think about it!
>
> If I was doing this, I would look into inserting the lines directly
> into the database using ODBC. This by-passes any Vantage data-
> checking and so should be considerably faster, but bypasses the data-
> checking...
>
> Nigel.
>
>
> --- In vantage@yahoogroups.com, "jmilton59" <jmilton@> wrote:
> >
> > I have a unique problem and I am not making much headway. I am
> trying
> > to: (a)create anywhere from 60 to 200 new parts for manufacturing;
> > (b)create unique sales kits from these parts, one kit per shipping
> > location (up to 6000 locations) and each kit having between 1 and 60
> > items; (c)load 6000 sales kits and there components into a single
> > sales order.
> >
> > The kit configurations are coming from an external database and I
> have
> > been able to do this on a smaller scale using the web services
> (after
> > a lot of banging my head against the wall trying to figure out the
> > minimum required data for each service).
> >
> > Based on the time it takes to do the small order, creating the large
> > order will take about 110 hours to generate. And throw in the mix
> > that the order may change after it is generated...nightmare waiting
> to
> > happen. Has anyone had any experience creating large orders? Any
> > suggestions would be welcome.
> >
> > Thanks
> >
> > Joe
> >
>