Lanham EDI : Ship-for Code?

jversusj

Hello,
I am trying to get my head around some new requirements our top customer is throwing at us.

We use Lanham EDI. We receive this customer's orders via EDI. They may send a single PO that is intended for multiple stores, sometimes being sent to a DC where the customer will finish the routing. they are sending an SDQ segment and the field is called ID Code - this field holds the final destination for the goods in the case of us sending the order to a DC.

I have been digging through the Lanham code and trying some different things to see where I can dump this SDQ ID code on the sales header. I thought the EDI Ship-for Code was the perfect place for it so i tested what would happen if i put the final destination ship-to code in this field. I was shocked that validation logic then proceeded to change the EDI Ship-to Code and that changed the Navision Ship-to Code! So, I wanted to identify on the header the final destination of the product and it ultimately changed the ship-to?! We have to ship to the DC, not the store, so this seems like bad logic to me. I would think that EDI Ship-to and EDI Ship-for should be separate fields, not linked together as the validation logic does. I should be able to ship to 1 place and record who it is ultimately for in a 2nd place.

We are using 3.7b objects, so can anyone tell me if this has been changed in newer versions? It seems stupid. They are redundant fields as is - i can't change 1 without changing the other such that both always have the same value.

Any ideas what i could do (short of upgrading)? The other problem is that our sales header is completely full (we have hit the 4kb record limit on the table), so i cannot add another field to map this to. am i missing some piece of EDI functionality here? i am also hesitant to start hacking away at the Lanham code with my own modifications.

thanks in advance!

Savatage

I don't know if this helps - but here is our 850 with SQD
http://savatage99.googlepages.com/SQD.pdf

jversusj

thanks - i see you are using SDQ Ship To to trigger a generation of a sales order per shipping destination. I do not think that will work for us because this vendor demands 1 invoice per PO. By creating a sales order for each ship-to using standard NAV, we would not be able to invoice correctly. our system has been modified to create master orders and suborders, and you invoice from the master order level. also, this setup would not help when we receive an order that is supposed to ship to a DC but needs marked for the store, would it? we'd still apparently lose that visibility due to how it is coded.

do you have any information on why the EDI ship-to and EDI ship-for are so intertwined that they always equal the same value?

Savatage

In the partner store setup - you can choose store or distribution center under "ship-to type"
Thyere is also a "default dist center" check box - we've never used them so I can't tell you what it does.
perhaps its a way to group?

But I try to stay away from the Lanham code. I'm afraid to screw it up.
Perhaps MVP Alex Chow can help you, if i remember he's great at this edi stuff.

jversusj

thanks...

same here, i don't want to mess up the code. the bottom line, i need my sales order to have the final destination on it somewhere, so i can send this back to the customer per their requirement. not sure if that default DC would help us either, because we ship to a number of DCs.

some orders are placed by a store for themselves - these are easy (destination is the ship-to).
some orders are drop-shipments, and thanks to our master order process, we end up sending them to where the belong - again easy (destination = ship-to, and we get that destination manually by looking up the SDQ ID Code on the edi document)
some orders are sent to a DC/Consolidation Whse for specific store - here is where i have my problem. the ship-to is where the goods physically go, but i have no field saying who it belongs to once it gets to the DC. How can i leverage Lanham EDI to get the final destination on the order? The store no is manually derived from the SDQ ID code as mentioned above.

Savatage

As far as distribution centers go. If a company wants us to ship a bunch of merchandise to a DC then I'll leave what goes where up to them. We have a customer that we ship directly to all the stores, but a few items they order a specific item in large qty's to get a lower price. The individual stores then can order what they need directly from the DC so we're not really involved anymore once we get it to the dc.

jversusj

our customer has a system to track orders with their vendors and part of the requirements is that we send them a CSV file at every touch point on the order (dates changed, shipments posted, etc.) and they require to know what store the product is destined for. to make it even better, they send us the store as X digit code, but expect us to translate it and send it back as the actual Y digit code. we can do this with the edi cross referencing, but i think it reflects a customer who bullies their vendors (and of course the customer _is_ always right).

Savatage

are their initials BBB Edi can be tough - once i get it to work i try not to mess with it again. EDI saounds like a great idea on paper but not always easy to accomplish. Maybe an edi guru will chime in. [-o<

Alex_Chow

With SDQ orders, one 850 can contain multiple POs. In the SDQ segment, if you setup as an element of SDQ SHIP TO (make sure you check on Trigger on the Quantity element, but check your mapping guide), it will create multiple SOs to different ship-to codes for one 850.

I'm not sure if this answers your question?

jversusj

Alex Chow wrote:

With SDQ orders, one 850 can contain multiple POs. In the SDQ segment, if you setup as an element of SDQ SHIP TO (make sure you check on Trigger on the Quantity element, but check your mapping guide), it will create multiple SOs to different ship-to codes for one 850.

I'm not sure if this answers your question?

thanks, i was able to figure this bit out by reading the code, but i do not think it will help with my current issue.

it seems like maybe i am missing the boat regarding what use the EDI Ship-for field is when it seems completely interrelated with EDI Ship-to.

in your example above, consider an EDI document for 1 QTY of 1 ITEM for 1 customer store (#X). the customer, however, does not want you to ship the product to store #X, they want you to ship to DC #Y, with the carton marked for store #X. I would intuitively think that EDI Ship-to would refer to DC #Y and NAV Ship-to code would be defined appropriately. EDI Ship-for would then refer to store #X (since you are shipping to Y for X). Reality, however, shows that both fields are defined as #Y when the sales order is created from the EDI received doc.

Based on the above anecdote, are there any other ideas? Thanks!

Alex_Chow

Yes, I would intitutively think that the ship-for code is what's needed. I remember the ship-to code and the ship-for code is independent of each other, is this not the case?

I would check with the trading partner (and the mapping guide) to see how they want it to be displayed when you send back the 856, 810, etc.

jversusj

Alex Chow wrote:

Yes, I would intitutively think that the ship-for code is what's needed. I remember the ship-to code and the ship-for code is independent of each other, is this not the case?

I would check with the trading partner (and the mapping guide) to see how they want it to be displayed when you send back the 856, 810, etc.

OnValidate of EDI Ship-For ultimately calls the validation logic for EDI ship-to in our system, which ultimately changes the sales header.ship-to code field, such that i cannot validate the ship-for field without changing where the product is being shipped. maybe they have changed this in a new version.

i think i have devised a way to do get this value at run time, but i shudder at its performance:
with sales header, get the EDI Rec. Doc Hdr.
with the EDI rec. doc hdr., get the EDI Rec. Doc fields.
filter to the SDQ segment, element 3 ID Code and grab the store no.
cross reference that store no with edi customer cross reference to find nav record for that store (now i have store no.)

thanks.

Alex_Chow

Ok, it uses the Ship-to code for the EDI Customer Cross Reference. Just you just need to set the Default Dist. Center based on the store's resupply DC.

But I would check the mapping guide on what you are sending back. If they specify the ship-to code for the DC on the SDQ and only using store's address as a reference, just use the Virtual fields to reference it back to them. If they're giving you the store's code, then using the Default Dist. Center on the Customer Cross Reference should be what you need.

jversusj

Alex Chow wrote:

Ok, it uses the Ship-to code for the EDI Customer Cross Reference. Just you just need to set the Default Dist. Center based on the store's resupply DC.

But I would check the mapping guide on what you are sending back. If they specify the ship-to code for the DC on the SDQ and only using store's address as a reference, just use the Virtual fields to reference it back to them. If they're giving you the store's code, then using the Default Dist. Center on the Customer Cross Reference should be what you need.

thank you for the idea, but i am afraid i do not understand. I do not know what the virtual fields are in Lanham EDI. Is this the EDI Rec Doc field entry?

i do NOT know if we know the default DC for any given store to configure this , but i still question how it would work.

Let us say i have 5 customer cross reference records; 2 are DCs and 3 are stores.
Code, Type, Default DC
DC1, Dist.Center,
DC2, Dist.Center,
ST1, Store, DC1
ST2, Store, DC1
ST3, Store, DC2

the EDI order identifies that the order will be shipped to DC1 (this is sent in N1 and not in SDQ) and in the SDQ says we need to ship it to ST1. I do not have ST1 mapping to anywhere on the header, so how would the above cross reference map help? Couldn't it think that ST1 and ST2 are both valid stores for that DC? Sorry - i am completely ignorant in this set-up and configuration. i looked for how-to docs on Lanham's site, but didn't see anything. i guess i'll look again.

i should point out that i am not our edi coordinator, so i will also take these questions up with her when she gets back in the office next week - although i question whether or not she will have the answer either.

Alex_Chow

Ok, in the scenario:
DC1, Dist.Center,
DC2, Dist.Center,
ST1, Store, DC1
ST2, Store, DC1
ST3, Store, DC2

You would setup ST1 as EDI Ship To Code on the E.D.I. Customer Cross Reference table. Set the Default Dist. Center as DC1.

This way, the ship-for will be for the store, and the ship-to will be the DC.

Hope this helps.

gogojlwc

Hi,

Is there any one can share their mapping for SDQ here?
I have problem to do SDQ mapping. Do I need to create customer cross reference for SDQ SHIP TO?
And, how did you do to map on N1 and PO1?

your help is much appreciated

Sincerely,
Jimmy