Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 304 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Lanham EDI - Single Customer Multiple Trading Partners
pbarry76
Member Posts: 5
When creating ASNs we are having issues with the correct Trading Partner (TP) being used. Our setup is such that we have one customer that has uses four different Trading Partners.
Customer 1
Ship-to Location 1 (relates to TP 1)
Ship-to Location 2 (relates to TP 2)
Ship-to Location 3 (related to TP 3)
Ship-to Location 4 (relates to TP 4)
The EDI Trading Partner field on the Customer 1 customer card is set to nothing to prevent NAV from always picking the same TP because we would like it to depend on the ship-to code.
From the customer card, when creating a new ship-to location, there is no field to designate EDI TP. The only thing on the ship-to location card is packing rule.
The sales order has the EDI Trading Partner field set to TP 2,
the EDI Sell-to field set to Customer 1,
the EDI Ship-to Code and Ship-for Code are set to Ship-to Location 2.
Within EDI Trading Partners the TP 2 has EDI Customer Cross Reference set to
EDI Sell to Code - Customer 1
Navision Sell To Code - Customer 1
EDI Ship To Code - Ship-to Location 2
Navision Ship To Code - Ship-to Location 2
We perform shipping through pack line scanning.
When the process of EDI - Send ASN from the BOL is run, the ASN is created from the TP 1 regardless of the ship-to code.
Does anyone know of a setting that I'm missing that controls the ability to compile an ASN based off the ship-to code?
Customer 1
Ship-to Location 1 (relates to TP 1)
Ship-to Location 2 (relates to TP 2)
Ship-to Location 3 (related to TP 3)
Ship-to Location 4 (relates to TP 4)
The EDI Trading Partner field on the Customer 1 customer card is set to nothing to prevent NAV from always picking the same TP because we would like it to depend on the ship-to code.
From the customer card, when creating a new ship-to location, there is no field to designate EDI TP. The only thing on the ship-to location card is packing rule.
The sales order has the EDI Trading Partner field set to TP 2,
the EDI Sell-to field set to Customer 1,
the EDI Ship-to Code and Ship-for Code are set to Ship-to Location 2.
Within EDI Trading Partners the TP 2 has EDI Customer Cross Reference set to
EDI Sell to Code - Customer 1
Navision Sell To Code - Customer 1
EDI Ship To Code - Ship-to Location 2
Navision Ship To Code - Ship-to Location 2
We perform shipping through pack line scanning.
When the process of EDI - Send ASN from the BOL is run, the ASN is created from the TP 1 regardless of the ship-to code.
Does anyone know of a setting that I'm missing that controls the ability to compile an ASN based off the ship-to code?
0
Comments