Ah, I see. Well, that, I cannot answer, sorry. I do wish you luck though. I'm thinking your first EDI example should work for what you're trying to do, it's just a matter of getting Syspro to recognize what you mean (now, that is the tricky part).
Leah ________________________________ From: Rich Silva <[email protected]> To: [email protected] Sent: Saturday, June 25, 2011 10:18 PM Subject: RE: [EDI-L] <Reprise> EDI, the Incoming 846 and LOT numbers... Hi Leah! Yes, to this client, its important to know the Quantity On Hand per LOT (At least they currently think so… I’ve been asking them the same question) Yes, the issue is with the ERP, its Syspro w/ Cadecus EDI installed… and I have a good relationship with the Syspro folks… and with a few others in this group who know Syspro. The Business Process I am trying to support is Inventory Maintenance. In particular I’m trying to reconcile an “actual cycle count” at the Warehouse with the Stock Levels that are reported in Syspro. The idea is to receive an EDI 846 from the Warehouse and with that produce a Variance Report against the Stock Levels in Syspro…. Then negotiated action will take place to reconcile those variances. I’m fairly certain that once I come up with a description of what I want that I can get Syspro/Cadecus to impement this as an enhancement. I want to make sure what I ask for is actually a reasonable thing… Rich From: [email protected] [mailto:[email protected]] On Behalf Of Leah Halpin Sent: Saturday, June 25, 2011 4:20 PM To: Rich Silva; [email protected] Subject: Re: [EDI-L] <Reprise> EDI, the Incoming 846 and LOT numbers... Rich, I have very limited experience with the 846 and none with "lot" numbers (except Honda Lot Numbers and small lot numbers, but, hey, that's a whole different story). So, I have a question, is it important to know the quantity per lot number? It seems like you want to know it, but you haven't explicitly said so. I also have a comment and a suggestion. Comment: It seems like the issue is with the ERP rather than the EDI, so maybe if you mentioned what the ERP is or asked people in a group related to your ERP you might get a better answer. My suggestion is to clearly state what business process you are trying to support or business problem you are trying to solve and someone on this list might be able to share an innovative solution that you have not thought of, which may or may not involve the 846. In any case, I wish you luck. Leah ________________________________ From: Rich Silva <[email protected] <mailto:richsilv%40pacbell.net> > To: [email protected] <mailto:EDI-L%40yahoogroups.com> Sent: Saturday, June 25, 2011 1:50 PM Subject: [EDI-L] <Reprise> EDI, the Incoming 846 and LOT numbers... Hi, <Maybe this will make this a little more readable> I wanted to maybe clear up a few points... I know that this depends on the relevant Specs... Except that neither I, nor the Warehouse involved have a spec that covers or has an example of this issue... But they are willing to send what I need to receive to have the expected results... I can go to the SW provider and ask for an Enhancement... But if I go that route, I want to make doubly sure I am not asking for a "square peg" to fit in a "round hole"... And I want to make sure I am asking for something that actually aligns with Best Practices (whatever that means with respect to EDI) = = = = Original message, reformatted, subtly changed, follows = = = = Have any of you experience with the Incoming (or even Outgoing) 846 and Stock Codes with more than one LOT number? If you have Stock distributed across a number of LOTs at your warehouse, how would that be documented in an EDI 846? I would think that you should be able to document the QTY on hand (or available) of each LOT for each Stock Code? As an experiment I manipulated the Stock/LOT levels for a couple of Stock Codes within the Application and then manually generated an 846 "from my Warehouse" for those two Stock Codes matching the levels I had set. The Stock and LOT distribution as in the below table… Lot Stock code WH received on hand Expiry date Creation date 0111 43.539V 90 8,000 8,000 06/22/11 01/22/11 0211 43.539V 90 2,000 2,000 06/22/11 02/22/11 0311 43.539V 90 1,000 1,000 06/22/11 03/22/11 0611 43.505 90 8,000 8,000 06/22/12 06/22/11 0711 43.505 90 2,000 2,000 07/22/12 06/22/11 0811 43.505 90 1,000 1,000 08/22/12 06/22/11 The 846 I generated contained (amongst the usual fluff) the following detail lines: LIN**VN*43.505*UP*830324001410*LT*0611 QTY*33*8000*EA LIN**VN*43.505*UP*830324001410*LT*0711 QTY*33*2000*EA LIN**VN*43.505*UP*830324001410*LT*0811 QTY*33*1000*EA LIN**VN*43.539V*LT*0111 QTY*33*8000*EA LIN**VN*43.539V*LT*0211 QTY*33*2000*EA LIN**VN*43.539V*LT*0311 QTY*33*1000*EA My expectation was that importing this would generate no variances since each Stock/LOT number QTY matched the On Hand QTY? Instead I received a variance for each line, declaring the Total Stock QTY. (And then I checked, no there is no option to recognize the Stock any other way) That doesn’t seem right to me… So, I generated, this time using the Same application I am Importing the 846 through, an outgoing 846 for the same Warehouse, the lines in it look like: LIN**VN*43.505*UP*830324001410*LT*JUL08 LIN**VN*43.505*UP*830324001410*LT*0611 LIN**VN*43.505*UP*830324001410*LT*0711 LIN**VN*43.505*UP*830324001410*LT*0811 QTY*33*11000*EA LIN**VN*43.539V*LT*0111 LIN**VN*43.539V*LT*0211 LIN**VN*43.539V*LT*0311 QTY*33*11000*EA (FWIW, the JUL08 LOT has no On Hand or Available stock) Which at least suggests what LOTs exist, but not how much stock is available in each of them… So maybe I am a bit confused… Anyone have some comments on this? Am I expecting something that just isn’t going to arrive in an 846? Or is there a different way (or document) I can use to do the same thing? Richard Silva Silva Software Services – United States Phone: (310) 387-8364 Email: [email protected] <mailto:RichSilv%40Pacbell.net> ü Please consider the environment before printing this email. [Non-text portions of this message have been removed] [Non-text portions of this message have been removed] [Non-text portions of this message have been removed] ------------------------------------ ... 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/
