>no, its not a trick question. The "change" response does contain the data >has been changed but there's >no field indicating such a change has happenend. If they send the original >order with a quantity of 5 and >have it decreased by one by an ORDCHG, the "change" order response IDoc >will reflect this (qty=4) >however there's no way of telling that the quantity did indeed change so >yeah the questions is really >how to tell one type of order response from another.
In ANSI (what I know best) , the inbound '860' document contains a "change or response type code" in segment POC (line item) element two. This code will be (well, "should be") "QI" for quantity increase or "QD" for quantity decrease and in these cases elements three and four will be "qty ordered" and "qty left to receive" respectively. That is, you should know what kind of change has occurred based on the '860' document itself. (There are lots of other valid codes). Unfortunately.... "should" does not always translate into "does"... a lot of buyers seem to 'make up' their own meanings for these elements and code values, so in any event you will be checking with your partner for the precise format in which they intend to send what kind of changes. In the EDIFACT ORDCHG document - not my strong suit - I guess I'll have to rtfm.... http://www.unece.org/trade/untdid/d09b/trmd/ordchg_c.htm This is the segment usage page for the ORDCHG document. You can probably find some kind of "reason code" or "type of change code" in a relevant segment somewhere to mirror the ANSI X12 usage. But again I'd think you will have to consult with your partner on the same subject: "How do you intend to convey what types of changes?" (Looks like you could search here: "Segment group 28: LIN-PIA-IMD-MEA-QTY-PCD-ALI-DTM-MOA-GEI-GIN-GIR- QVR-DOC-PAI-MTD-FTX-SG29-SG30-SG32-SG33-SG34-SG35- SG38-SG39-SG40-SG44-SG50-SG52-SG53-SG54-SG56-SG57- SG59 A group of segments providing details of the individual line items. This Segment group may be repeated to give sub-line details." I think I see some 'type of change' segments/elements) > I'm not familiar with >X12 but I believe they have >a separate transaction for this: 865. The ANSI '865' document is defined as the "response to buyer-initiated purchase order change [860] document ." Michael C. Mattias Tal Systems Inc. Racine WI [email protected] ------------------------------------ ... Please use the following Message Identifiers as your subject prefix: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> Job postings are welcome, but for job postings or requests for work: <JOBS> IS REQUIRED in the subject line as a prefix.Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/EDI-L/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/EDI-L/join (Yahoo! ID required) <*> To change settings via email: [email protected] [email protected] <*> To unsubscribe from this group, send an email to: [email protected] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
