WIXLIB

V1.0Microsoft Dynamics NAV 2013Lesson 1: The Objects of the Intercompany Functionalityin Microsoft Dynamics NAV 2009This lesson explains which objects are specific to the Intercompany functionality inMicrosoft Dynamics NAV 2009.The following objects are part of the Intercompany functionality in Microsoft Dynamics NAV2009:Note: Tables range 410-442 (except no. 422, 425 which are not used) Forms range 600-620 (except no. 604 which is not used) Forms range 636-652 Reports range 511-513 Codeunits range 427-431 Codeunit 435 XMLports range 10-12 Pages range 600-620 (except no. 604 which is not used) Pages range 636-652The holes in the objects range are reserved for a future usage.Posting objects as codeunit 12 are participating in the Intercompany posting as well, butare not specific to that functionality.Tip:You may be able to find the objects used for the Intercompany functionality by filteringtheir name with the substring IC.Microsoft ServicesMicrosoft Confidential - For Internal Use Only11

V1.0Microsoft Dynamics NAV 2013Lesson 2: The Objects of the Intercompany Functionalityin Microsoft Dynamics NAV 2013This lesson explains what are the new objects and fields specific to the Intercompanyfunctionality in Microsoft Dynamics NAV 2013.No new object specific to the Intercompany functionality have been introduced in MicrosoftDynamics NAV 2013.On the other hand, the fields Ship-to Address 2 (no. 16) and Ship-to Post Code (no. 91)have been added to the following tables: No. 426 IC Outbox Sales Header. No. 428 IC Outbox Purchase Header. No. 430 Handled IC Outbox Sales Header. No. 432 Handled IC Outbox Purch. Hdr. No. 434 IC Inbox Sales Header. No. 436 IC Inbox Purchase Header. No. 438 Handled IC Inbox Sales Header. No. 440 Handled IC Inbox Purch. Header.In addition, the field Promised Delivery Date (no. 5791) have been added to the table 427IC Outbox Sales Line.Finally, the field Request Receipt Date (no. 5790 in Purchases tables) and RequestDelivery Date (no. 5790 in Sales tables) have been added to the following tables: No. 428 IC Outbox Purchase Header. No. 429 IC Outbox Purchase Line. No. 434 IC Inbox Sales Header. No. 435 IC Inbox Sales Line. No. 437 IC Inbox Purchase Line.Microsoft ServicesMicrosoft Confidential - For Internal Use Only12

V1.0Microsoft Dynamics NAV 2013Following is the summary of the new fields in Microsoft Dynamics NAV 2013 (columnsrepresent fields and lines represent tables):Table 1: New Fields in Microsoft Dynamics NAV 2013 Intercompany Tables426. IC Outbox SalesHeader16. Ship-toAddress 291. Ship-toPost CodeXX5790. Request 5790. Request 5791. PromisedReceipt DateDelivery Date Delivery Date427. IC Outbox SalesLine428. IC OutboxPurchase HeaderXXX429. IC OutboxPurchase LineXX430. Handled ICOutbox Sales HeaderXX432. Handled ICOutbox Purch. HdrXX434. IC Inbox SalesHeaderXXX435. IC Inbox SalesLine436. IC InboxPurchase HeaderXXX437. IC InboxPurchase LineX438. Handled ICInbox Sales HeaderXX440. Handled ICInbox Purch. HeaderXXNote:The Forms are not used anymore in Microsoft Dynamics NAV 2013.Those new fields are not used for a new functionality, but as an enhancement of theexisting one. In fact, those important fields where not transferred in the past betweenthe different companies.Microsoft ServicesMicrosoft Confidential - For Internal Use Only13

V1.0Microsoft Dynamics NAV 2013Module 3: Setup the Intercompany FunctionalityThis module explains the different screens (Pages) to fill to setup the Intercompanyfunctionality.Before You BeginBefore starting this module, you should: Be familiar with Microsoft Dynamics NAV 2013 Role Tailored Client. Have launched Microsoft Dynamics NAV 2013 Role Tailored Client.What You Will LearnAfter completing this module, you will be able to: Explain the basics of the Intercompany setup for two or more companies. Setup the Intercompany functionality within a company.Microsoft ServicesMicrosoft Confidential - For Internal Use Only14

V1.0Microsoft Dynamics NAV 2013Lesson 1: Basics of the Intercompany FunctionalitySetupThis lesson explains why you need to setup the Intercompany functionality and how thissetup is used in the different companies of the group.Even in a homogenous group, each company of the group may have its own Chart ofAccounts. In addition, they generally sell or buy their own goods, and then may have alsospecific Dimensions for that.Conclusively, as the different companies in the group may not be stored in the samedatabase (although sometimes not on the same server), Microsoft Dynamics NAV 2013 needsome information regarding the posting of Sales and Purchases documents (as Posting G/LAccounts or Item references) within each company. The information regrouping thosedata is called an IC Partner.This particular setup allows the different companies of the group to exchange tradedocuments based on their own accountancy, not necessary needing the same setup.In Microsoft Dynamics NAV 2013, you can run the Intercompany setup from theIntercompany menu. To access the Intercompany menu: Select Departments, select Administration, select Application Setup, selectFinancial Management and then select Intercompany Postings.Microsoft ServicesMicrosoft Confidential - For Internal Use Only15

V1.0Microsoft Dynamics NAV 2013Lesson 2: Setup the Intercompany PartnersThis lesson provides a detailed explanation of what IC Partners are and how to set them up.What You Will LearnAfter completing this lesson, you will be able to: Understand the usage of an IC Partner. Setup an IC Partner.When you create a Sales or a Purchases document, you have to indicate if the destination ofthat document (the Customer or the Vendor) is another company of the group. In that case,you are using an IC Partner.To access to the IC Partner Card, go to IC Partners in the Intercompany setup list. Whenyou open a card, you have the following screen:Figure 1: IC Partner CardThe following list provides an explanation of each field and its value: Code—this is the code to identify the Card. Name—this is the name of the company it refers to. You usually use a completename as the company name within an unique Microsoft Dynamics NAV 2013databaseMicrosoft ServicesMicrosoft Confidential - For Internal Use Only16

V1.0Microsoft Dynamics NAV 2013 Currency Code—Identify the Currency Code of the company. This is usually theLCY Code of its General Ledger Setup. Inbox Type—This field identifies how the Intercompany data are exchanged withthat IC Partner. The following values are available:oFile location—The transactions between the companies are stored within anXML file. Use the field Inbox Details to select or create the relevant file.oDatabase—The transactions between the companies are coming from acompany stored within the same database. Use the field Inbox Details to selectthe relevant company.oE-mail—The information of transactions is stored within attachment files of emails. Use the field Inbox Details to fill the e-mail address of the IC Partner.oNo IC Transfer—the information of transactions are not transferred for thecurrent Partner. Inbox Details—See the previous field Inbox Type. Blocked—Use this field to block the usage of that IC Partner. Receivables Account—Select here the G/L Account in which the Sales Amountswill be posted for that IC Partner.If the transaction do contain a Customer No. the Receivable Account of its CustomerPosting Group will be used instead.Note: Payables Account—Select the G/L Account in which the Purchases Amounts willbe posted for that IC Partner.If the transaction do contain a Vendor No. the Payable Account of its Vendor PostingGroup will be used instead.Note: Outbound Sales Item No. Type—In most situations, the trade documents arebased on Items. On the other hand, the Items nos. may be different in the twocompanies. The field used in the Intercompany documents to store the Item No. iscalled IC Partner Reference. This option controls how the IC Partner Referencefield is filled from the Item No. (Field No. for a line of type Item) for Salesdocuments. The following values are available:oInternal No.—this is the same no. as the Item No. (field No.) of the Sales line.oCommon Item No.—you use this option to copy the Common Item No. field ofthe Item Card in the IC Partner Reference. The Common Item No. is astandardized item number. See the Item setup in the Item Card.Microsoft ServicesMicrosoft Confidential - For Internal Use Only17

V1.0Microsoft Dynamics NAV 2013The Common Item No. is not visible by default in the Item Card.Note:oCross-Reference—the objective of an Item Cross-Reference is to create amapping table between the different companies of the group for item numbers.To use this option, you have to create an entry for that Item with the followingvalues: Cross-Reference Type Customer. Cross-Reference Type No. Customer No. Cross-Reference No. the Item No. of the group.See:More:The Item setup in the Item Card (ask for button Item, Cross References in the ItemCard—Master Data). Outbound Purch. Item No. Type—this option is similar to the previous one, but forPurchases documents, there is also an additional value:oVendor Item No.: this option is similar to the Cross-Reference one, but forVendor Items. To use this option, you have to create an entry for that Item withthe following values: Vendor No.—the Vendor no Vendor Item No.—no. of Item of that Vendor Lead Time Calculation empty.See:More:The Item setup in the Item Card (ask for button Item, Cross References in the Item Card- Vendors). Cost Distribution in LCY—check this option if you want to consider the costs to beallocated in the local currency of one (or several) IC partners.Important:The same IC Partner Card is used as well for Purchases than for Sales. However, iftransactions are posted in only one sense, you can setup one of the both parts.Note:It is possible to setup some Dimensions for an IC Partner. To do so, go to the tabNavigate in the ribbon and click Dimensions. Here you will find the local Dimensions.See Lesson 6 of that Module for Dimensions mapping.Microsoft ServicesMicrosoft Confidential - For Internal Use Only18

V1.0Microsoft Dynamics NAV 2013Lesson 3: Setup the Company as an IntercompanyPartnerThis lesson provides a detailed explanation of company setup as an IC Partner.What You Will LearnAfter completing this lesson, you will be able to: Define a company as an IC Partner.In a large group, there might be many companies using the Intercompany functionality.Outside of the IC Partners, each company must identify itself as an IC Partner with aunique ID everywhere in the group.This part is made in the Company Information window, tab Communications. You will seethat relevant fields are similar to the IC Partner card.Following are the explanation of each field and its value: IC Partner Code—this is the unique ID of the partner. That means that all othercompanies which refer to that company must use this ID as the IC Partner Code(field Code in the IC Partner card) IC Inbox Type: this field identifies how the Intercompany data are usuallyexchanged for that company. The following values are available: oFile location: the transactions between the company and other one are storedwithin an XML file. Use the field IC Inbox Details to select or create the relevantfileoDatabase: the transactions between the company and other one are donewithin the databaseIC Inbox Details: if you have chosen an IC Inbox Type of type File Location, enterhere the pathname of the relevant fileMicrosoft ServicesMicrosoft Confidential - For Internal Use Only19

V1.0Microsoft Dynamics NAV 2013Lesson 4: Setup the Intercompany Chart of AccountsThis lesson provides a detailed explanation of what is the IC Chart of Accounts and how tosetup it.What You Will LearnAfter completing this lesson, you will be able to: Understand the usage of the IC Chart of Accounts. Setup the IC Chart of Accounts.All the companies in a same group have to agree on a common Chart of Accounts. Once thisis done, each company creates a mapping table between that common Chart of Accountsand its own one. Then, when an Intercompany document will be posted with a G/L Accountin it (like on a document line), the IC Chart of Account will be used as follows: For the Vendor, the local G/L Accounts used in the document are transformed usingthe corresponding G/L Account in the mapping table. For the Customer, the G/L Accounts used in the Intercompany document aretransformed to the local G/L Accounts using the mapping table.To access to the IC Chart of Accounts, go to IC Chart of Accounts in the Intercompanysetup list. In demo database, a copy of the local Chart of Account is presented with thesame organization and a mapping to the same G/L Account. The mapping is done using thefield Map-to G/L Acc. No. in the last column of the list.Two main Actions are available from the Actions tab of the ribbon:Note: Map to Acc. with Same No.—this batch will copy the G/L Account No. to the Mapto G/L Acc. No. field for the selected lines. If the G/L Account in the IC Chart ofAccounts do not exist in the general Chart of Accounts, its value wouldn’t bechanged. Copy from Chart of Accounts—this batch will copy the entire general Chart ofAccounts to the IC Chart of Accounts. No current IC G/L Account will be deleted,then if a specific IC G/L Account have been created (that does not

The objective of the Intercompany functionality in Microsoft Dynamics NAV 2013. Estimated time to complete this module: 2 minutes Module 2: Objects Involved in the Functionality This module summarizes the main objects used in the Intercompany functionality in Microsoft Dynamics NAV 2009, and the new objects and fields added in Microsoft Dynamics