Re: Bulk POs.

Sairam Bharadwaj wrote:
> one of our partners started sending Bulk PO in advance to actual POs.
> This is just FYI type information but we don't have to do any real
> shipments against it.
So why aren't you interested in the information they're sending?

> So, we decided not to load it into our backend system. Now, how do we
> process this in our translator (Gentran NT 5).
Same as you do any other transaction set with business data. The
question isn't as much what you do with it in Gentran, the question is
what you do with the data after it comes out of Gentran.

> If we want to fail it based on some logic, we would send a failure 997
> to partner which is not acceptable to them.
And they're right. You are confusing a business level rejection with a
syntax level rejection. The 997 deals with the latter and you don't
reject the document with a 997 unless there's a syntax problem. I'm not
even sure that you want to send a business level rejection, either. If
you don't want the data and can't use it, probably best to contact the
trading partner and ask them to stop sending it rather than do a
business level reject every time you receive one (which I think you
could do with an 824 or an 855 if you wanted).

> Can we write it into a different location based on PO#?
Sure, if there's some logic to the way the PO# is constructed. Why?

> Please suggest if you have come across similar situation and how your
> are handling it.
If the order management system can't make use of a blanket PO (receive
releases against it) or a forecast, then output the transaction set from
Gentran as a report and give it to your order management people. The
system may not be able to use it, but the people might. If you go this
route you'll need key off of something in the transaction set to tell
you that you're dealing with a bulk PO as opposed to a regular PO. If
the trading partner only sends you bulk POs, then just set up a
different map for them. However, it may be a bit more complicated if
they can send you regular POs. In that case you could do something like
key off the BEG01 value to do different processing (force a reject,
whatever).

Mike

--
---------------------------------------------------------------
Michael C. Rawlins, Rawlins EC Consulting
www.rawlinsecconsulting.com