Message Boards
ECommerce function question
Michael Forman, modified 3 Years ago.
ECommerce function question
Post Date: 12/14/11 (Platinum, 334 Posts) Recent PostsFirst, QAD eB2 SP9 or so, Progress 10.2.
I have a situation where in the same EDI transmission, a customer may
send multiple separate documents for the same part... picture
kanban-type requirements, each sent in a separate EDI transaction
instead of multiple FST loops in the same transaction. Processing them
directly results in each one overwriting the previous one and leaving
only the last one "alive".
I'm looking at how best to handle it in QAD's EDI ECommerce. Thoughts
that cross my mind...
1. Somehow check the EDI transmission or processing date for each
requirement, and if it's close enough to be the same one, combine them
instead of replacing
2. Perform some kind of pre-processing step to combine the requirements
together into a single document
Hmmm... I thought I had more, but I guess not.
Anyone have any thoughts or comments on how best to handle this?
Thanks.
Scott
Scott M Dulecki Pridgeon and Clay Inc.
616/252-2337 [email protected]
MWUG: 18-20 Mar MPUG: 18 Jan WMPUG: 19 Jan
Chris Theisen, modified 13 Years ago.
Re: ECommerce function question
Post Date: 7/1/12 (Silver, 79 Posts) Recent PostsAt this version level, the primary option is to enable many-to-many processing on the transforamtion and use F:Check-Hash on the header write to control the application repository sequence pointer. Many-to-many will increase the scope of the transaction to include all sequences in the session, and the F:Check-Hash will allow you to write to multiple application sequences within the same session.
At higher versions you can now setup RSS execution in REQ scheduled orders to run each time a new release is created. This along with RSS merge would continue to accumulate each new requirement under a new RSS.
Hope this helps.
Vinod Kumar, modified 13 Years ago.
Re: ECommerce function question
Post Date: 10/9/12 (Gold, 123 Posts) Recent PostsMessage place holder
Forums