Elegant customiz. to have multiple IC Partners per company?
Miklos_Hollender
Member Posts: 1,629
Currently you can have only one vendor or customer as an IC partner per actual real life company. If you use multiple customer or vendor accounts per subsidiary or sibling company, (you like to separate currencies because then you can verify the exchange rate adjustment routines better or separate goods from services etc.) you can only send to one of them. Why? Because if you set up in your say DE company two vendors, FR and FR_SERV for example, and you send an electronic PO through the IC functionality to your FR company, then it cannot import it if in the XML file it says FR_SERV and not FR.
The goal would be, if a subisdiary sends you a PO to your secondary vendor no. in their database, then accept it and treat is as if it came from their secondary customer no. in your database, so primary is DE customer -> FR vendor, secondary is DE_SERV customer -> FR_SERV vendor for example.
Now I tried to customize it, basically with extra fields change the code so that when I am FR and I get a PO from the IC partner DE, but the PO is address to FR_SERV, then accept it and treat it as coming from DE_SERV, right? However I realized these IC Partners are looked up so many times both in the XMLPort and in the Codeunit that it would be very ugly, too many changes in the standard code.
Is there are more elegant customization possibility here?
The goal would be, if a subisdiary sends you a PO to your secondary vendor no. in their database, then accept it and treat is as if it came from their secondary customer no. in your database, so primary is DE customer -> FR vendor, secondary is DE_SERV customer -> FR_SERV vendor for example.
Now I tried to customize it, basically with extra fields change the code so that when I am FR and I get a PO from the IC partner DE, but the PO is address to FR_SERV, then accept it and treat it as coming from DE_SERV, right? However I realized these IC Partners are looked up so many times both in the XMLPort and in the Codeunit that it would be very ugly, too many changes in the standard code.
Is there are more elegant customization possibility here?
0
Comments
-
I'd look to dimensions in that case...0
-
no thanks, they have the separate customer / vendor accounts since 2005 when NAV was implemented.ppavuk wrote:I'd look to dimensions in that case...0 -
Hi Miklos,
its maybe a bit radical to do so, but have you considered making the IC code a flow field where it is dependent on further fields?
with best regards
Jens0
Categories
- All Categories
- 75 General
- 75 Announcements
- 66.7K Microsoft Dynamics NAV
- 18.8K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 610 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 253 Dynamics CRM
- 103 Dynamics GP
- 6 Dynamics SL
- 1.5K Other
- 991 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 28 Design Patterns (General & Best Practices)
- Architectural Patterns
- 9 Design Patterns
- 4 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1K General Chat
- 1.6K Website
- 77 Testing
- 1.2K Download section
- 23 How Tos section
- 249 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions