A4 MIO Instal Guide NetWeave

8/8/2019 A4 MIO Instal Guide NetWeave

1/36

Microsoft Dynamics TM NAV

Multi-site and InternationalOrganizations: Integration ofSAP and Microsoft DynamicsNAV Installation GuideBased on SAP NetWeaver for the mySAP Business Suite

White Paper

Created by Magnus Management Consulting and Qurius

March 2007

www.microsoft.com/dynamics/nav

INTEGRATION


2/36

2

MULTI-SITE AND INTERNATIONAL ORGANIZATIONS: INTEGRATION OF SAP AND MICROSOFT DYNAMICS NAV

Contents

1. Introduction .........................................................................................................3

1.1 Business Transactions ................ ................ ................ ................ ................ ................ ................ ................. ................ ............. 3

2. System Landscape................................................................................................6

2.1 Hardware & Software platform....................... ................ ................ ................ ................ ................ ................. ................ ..... 6

3. System settings and Master data........................................................................7

3.1 SAP Customizing ...................................................................................................................................................................... 7

3.2 SAP Master Data......................................................................................................................................................................13

3.3 Setting up Microsoft Dynamics NAV ............... ................ ................ ................. ................ ................ ................ .............. 14

3.4 Microsoft Dynamics NAV database modifications.....................................................................................................16

3.5 Microsoft Dynamics NAV setup remarks ................ ................ ................. ................ ................ ................ ................ ...... 18

4. Master Data Upload to Microsoft Dynamics NAV ...........................................19

4.1 IDoc setup for master data transfer.................................................................................................................................19

5. Financial Consolidation .....................................................................................21

5.1 SAP specific settings/Financial Statements ............... ................ ................ ................ ................ ................. ................ ...21

5.2 Interfacing with SAP ............... ................ ................ ................ ................ ................. ................ ................ ................ .............. 21

6. SAP NetWeaver XI..............................................................................................23

6.1 Interfacing from and to SAP ............... ................ ................ ................ ................. ................ ................ ................ .............. 23

6.2 Interfaces....................................................................................................................................................................................246.3 Transport....................................................................................................................................................................................25

6.4 Importing the packages in XI............................................................................................................................................26

7. Custom Abap in the R/3 IDES system ...............................................................28

7.1 Custom BAPI functions........................................................................................................................................................28

7.2 User exit......................................................................................................................................................................................32

8. Custom ABAP in the XI system .........................................................................34

8.1 Removing namespaces in XI .............................................................................................................................................34

9. Appendix ............................................................................................................36


3/36

3


1. IntroductionThis document describes a Multi-site and International Organization business scenario involving a

parent company and sales offices (sites). The parent company runs SAP R/3 while its sales offices

register sales and other business activities in Microsoft Dynamics NAV. The business transactions

between parent and sales office are supported by the exchanging messages. The content of this

document is focused on the step by step implementation of business processes and integration

between SAP and Microsoft Dynamics NAV. It will deal with both functional and technical issues. The

business processes are explained in the first part of the document; the second part has a more

technical nature and describes the NetWeaver Exchange Infrastructure (XI) and custom ABAP

programming.

A demonstration environment has been set up to implement the scenario1. The business scenario can

be simulated using a demo script which describes the transactions from a user point of view in both

Microsoft Dynamics NAV and SAP. Please refer to this document for practical information concerning

the use of SAP and Microsoft Dynamics NAV application components in relation to the scenario.

The parent company and the sales offices have a vendor-customer relationship. The sales offices

purchase at the parent company and keep stock as a buffer for their own sales. In this scenario the

end-customers receive deliveries directly from the sales office. This document describes a single sales

office setting.

The reader is assumed to have basic knowledge about SAP and/or Microsoft Dynamics NAV in order

to build up a similar scenario.

1.1 Business Transactions

The parent company sells products to the sales office. The basic elements of this order-to-stock

transaction between sales office and parent are shown in the figure below.

1 The scenario in this document uses Microsoft Dynamics NAV release 4.0. This same scenario can also beimplemented with release 5.0.

R 3

Sales Order

Advanced Shipping

Notification +Delivery

Purchase order

Goods Receipt

Purchase invoiceSales invoice

S.O. Re ection Modif P.O.


4/36

4


In this scenario, the SAP parent and Microsoft Dynamics NAV sales office essentially have a vendor-

customer relationship. Information is exchanged, goods are shipped.

1.1.1 Purchase order from Microsoft Dynamics NAV to SAP

Internal business rules in a sales office trigger purchase activities since in this scenario demand

planning is done locally at the sales office. A purchase order containing quantities, prices and a

required delivery date is sent from Microsoft Dynamics NAV to SAP. A standard SAP sales order is

created upon receipt of a purchase order coming in from Microsoft Dynamics NAV. A SAP sales order

number is automatically created if the transaction is successful. The sales order captures the Microsoft

Dynamics NAV purchase order number which is used as a tracking reference number both by SAP

(parent company) and Microsoft Dynamics NAV (sales office) throughout the business process.

A custom-made program and a standard SAP BAPI for sales order generation are used to transform

the inbound Microsoft Dynamics NAV purchase order into a SAP sales order.

1.1.2 Sales order rejection from SAP to Microsoft Dynamics NAV

When the sales order is created in SAP, an availability check is made to determine if there is enough

stock in the warehouse to be delivered on the date requested by the sales office. If there is not enough

stock on hand, a schedule line with zero confirmed quantity for that item will be created. Before the

sales order is saved, a User-Exit (which is additional programming logic that was added to the sales

order program) will run to check the schedule lines. If the program discovers one schedule line in the

order that has zero quantity confirmed, the user exit will enter a Reason for Rejection for each item

line in the order and block the whole order for delivery on the header level. This means that a

complete delivery cannot be fulfilled. A Sales Order Reject message is then automatically sent to

Microsoft Dynamics NAV when the sales order is saved. The delivery block in a SAP sales order will

prevent a delivery note being created for the order and the reason for rejection in the order is similar todeleting the item lines in an order. Microsoft Dynamics NAV will then decide whether to accept or

resend a new purchase order with smaller requested quantities.

The Sales Order Reject message can also be sent manually to Microsoft Dynamics NAV in the event

the SAP sales order is changed; for example, in the case of cancellations requested by the Microsoft

Dynamics NAV sales office. In this case, a reason for rejection can be entered manually into the SAP

sales order and the order blocked for delivery. Upon saving the change, a Sales Order Reject

message is sent to Microsoft Dynamics NAV. This interface message consists of information such as the

reason for rejection, a blank expected delivery date and zero delivery quantity for each line item

in the order.

The mechanism for the interface uses a standard SAP IDoc. The IDoc is generated via the print

program in the order document as soon as the document is saved.

Note: Whatever the result of the availability check, a sales order confirmation is sent to Microsoft

Dynamics NAV. However, only the documents with a rejection code will be passed on to Microsoft

Dynamics NAV by the SAP XI server. Sales order confirmations with confirmed quantity will not reach

the sales office. It is more realistic to send an advanced shipping notification prior to physical delivery.

1.1.3 Shipping notification and delivery from SAP to Microsoft Dynamics NAV

If the complete order can be delivered, a delivery is created after which a goods issue is done in SAP.

Both transactions are manual. The delivery note created in SAP acts as a pick request for the

warehouse to pick the order. The picked quantities are then manually updated in the delivery note. A

goods issue in SAP depletes the stock levels in the system and makes a financial posting to reduce the

value of the stock. This usually happens when the actual physical goods leave the warehouse to bedelivered.


5/36

5


A goods issue process results in a material and accounting documents being created in SAP. The

creation of the delivery note, updating the pick quantities and goods issue can be done directly in the

delivery note (one transaction in SAP). When the goods issue is done and the delivery note is saved,

the shipping notification message is automatically triggered and sent to Microsoft Dynamics NAV. The

shipping notification provides a due date to Microsoft Dynamics NAV when the complete order (totalquantity of all requested items) will arrive at the sales office.

The mechanism for the interface uses a standard SAP IDoc. The IDoc is generated via the print

program in the order document as soon as the document is saved.

1.1.4 Invoice document from SAP to Microsoft Dynamics NAV

Before the sales invoice can be created, the outbound delivery and goods issue will first have to be

created in SAP since the sales invoice is delivery-based. The sales invoice message consists of the sales

price for each item that has been ordered from the Microsoft Dynamics NAV sales office. The total

amount to be paid to the parent company is calculated in Microsoft Dynamics NAV. The Microsoft

Dynamics NAV purchase order number is also recorded in the sales invoice. The invoice is created

manually, referencing the Microsoft Dynamics NAV purchase order.

The mechanism for the sales invoice interface uses a standard SAP IDoc. The IDoc is generated via the

print program in the sales invoice document as soon as the document is saved.


6/36

6


2. System Landscape

2.1 Hardware & Software platform

Hardware Software

SAP R/3 Compaq ProLiant

2x 550 Mhz Pentium III

2 Gb RAM

100 Gb hard drive capacity

Microsoft Windows Server 2000 + SP4

Oracle Database 9.2.0.6

SAP R/3 470x110 IDES (ABAP 6.20)

SAP NetWeaverExchange Infrastructure

(XI)

Compaq ProLiant 3000

2x 600 Mhz Pentium III

3 Gb RAM

90 Gb hard drive capacity

Microsoft Windows Server 2003

Oracle Database 9.2.0.6

SAP NetWeaver Exchange Infrastructure 3.0

(ABAP 6.40 + JAVA 6.40)

Microsoft Dynamics NAV Virtual Server: WindowsServer 2003

Microsoft Dynamics NAV 4.00 build 19914

Microsoft Dynamics NAV Application Server


7/36

7


3. System settings and Master dataThe business transactions described above depend on system settings and master data. The system

settings form the organizational and technical structure while the master data is the basis for content inthe business transactions. This section describes the system settings for both SAP and Microsoft

Dynamics NAV concerning the integration of their processes. The starting point for the SAP

configuration is a running IDES (Internet Demo and Evaluation System) system. The Microsoft

Dynamics NAV setup details begin at the installation of the Microsoft Dynamics NAV database and

client.

3.1 SAP Customizing

SAP system configuration is called customizing. This functionality provides all the means to configure

the system and make it fit to an organization and its business processes. In other words, the

customizing activity does not concern operational data, but rather the business structure and business

process definition. SAP customizing is done in the Implementation Management Guide (IMG) and hasa tree-likestructure. Screenshots of the relevant areas in this structure have been included in the text

below.

3.1.1 Customizing the organizational structure in SAP

A standard SAP IDES environment has been customized to incorporate the Microsoft Dynamics NAV

sales office on an operational and financial level. This paragraph describes the elements that have been

customized to create the scenario.

SAP Transaction: SPRO

SAP Implementation guide: Enterprise Structure - Definition

IMG Area Activity Description

Define company code 2500 Create a company code for the parentcompany. This is the smallest organizationalunit where accounting transactions areregistered. There is one single, standardcompany code for the SAP parent for whicha chart of accounts has been defined. Allfinancial transactions which involve theparent company are registered in thiscompany code.

Financial Accounting

Define company code 2510 The Microsoft Dynamics NAV sales officesare represented as separate company codesin the SAP system. The reason for this setupis that it facilitates the financial consolidationof the sales offices. This is explained below.

Define plant 2500 Create a site which represents the operatingarea of the parent company.

Logistics General

Define division 00 A division is an organizational part of thesales area through which products are soldto customers.

Define Sales Organization 2500 All sales are registered on this organizationallevel.

Sales & Distribution

Define Distribution Channel 12 Part of the sales area.


8/36

8


MaterialsManagement

Define Storage Location 0001 Physical location where stock is kept.

Logistics Execution Define Shipping Point 2500 Point from which deliveries leave the plant.


SAP Implementation guide: Enterprise Structure - Assignment


Financial Accounting Assign company code 2500 to creditcontrol area 1000

Credit control area 1000 is the standard IDEScontrol area for Europe.

Controlling Assign company code 2500 tocontrolling area 1000

Activate cost accounting functionality for thecompany code. Controlling area 1000 is thestandard IDES controlling area for Europe.To make postings to cost elements possible(to distribute the costs to a cost center,internal order, etc) it is needed to assign acompany code to a controlling area. For thisdemo we used account 792000 which is alsopresented as a cost element in controlling

(Because of this SAP standard setup). Ofcourse the decision for having a controllingarea can depend and for this demo it is notreally relevant.

Logistics General Assign plant 2500 to company code2500

A plant belongs to one company code.

Assign sales organization 2500 tocompany code 2500

Link financial accounting (company codelevel) to the sales activities.

Assign distribution channel 12 tosales organization 2500

Assign division 00 to salesorganization 2500

Set up sales area 2500/12/00

Distribution channels and divisions arelinked to sales organizations. The sales areacan then be set up using combinations ofsales organizations, distribution channelsand divisions. For the scenario, a single salesarea is used, there being just one saleschannel for intra-company sales.

Sales & Distribution

Assign sales organization distribution channel plant

Define the plant that will provide goods forthe sales area.

Logistics Execution Assign shipping point 2500 to plant

2500

A shipping point is part of a plant.


SAP Implementation guide: Financial Accounting


Financial AccountingGlobal Settings

Assign chart of accounts INT tocompany codes 2500 and 2510

The standard SAP chart of accounts INT isused for both parent and sales office.

General LedgerAccounting Business

Transactions Closing Documenting

Define Financial Statement version2510

2510 is the company code similar to 2510 inMicrosoft Dynamics NAV. The Financial

Statement Version is a default SAP standardFinancial Statement containing Assets,


9/36

9


Liabilities, P&L, Financial result, Taxes etc.This Financial statement was alreadyavailable in the system and did not needimprovement.

General LedgerAccounting BusinessTransactions Closing Documenting

Define Financial Statement version2500

2500 is the consolidation company code.Therefore we would only like to see theconsolidation accounts in the FinancialStatement Version. A new Financialstatement was needed.

SAP Transaction FS00

Change reconciliation account forvendor

Reconciliation accounts for a vendor orcustomer are setup in SAP for automaticposting only. Therefore you cannot postdirectly to these accounts. Account 165000needed to be changed so that manuallyposting is possible for this demo. Therefore

for this demo we connected 165000 to ageneral ledger account group without thecheck for automatic posting. Beware thatthis is a necessary setting, since otherwise, aposting cannot be possible.

The resulting system setting/customizing consists of organizational structures that allow:

General Ledger accounting for company code 2500 (parent company) Cost accounting for company code 2500 in controlling area 1000 Sales activities in sales area 2500/12/00 (Sales Organization/Distribution Channel/Division)

3.1.2 Customizing Sales & Distribution in SAP

Two sales documents are used in the scenario:

Sales order confirmation Sales invoice

Both the sales order confirmation and the sales invoice used in the scenario are standard SAP IDocs.

There are no modifications in the way the documents are generated: the scenario is based on standard

SAP functionality. All the parameters described below are available in a standard SAP IDES environment.

The first step for sending a sales order confirmation is the Output Type definition for the sales order.

Output type BA00 is the standard type for sales order confirmation and can be accessed in the path

shown below. The sales invoice is set up in the same way but has output type RD00. The rest of thisparagraph describes the process of setting up the sales order confirmation message.


10/36

10


The output type does not define a single medium which is used for creating the output. The image

below shows that there are various methods to output a sales order confirmation. (Printer, fax, EDI)

Medium six allows us to send IDoc messages and will be explained in the next step.

In the second step, the system can link the output type and specific medium to a business partner.This is useful because you might deal with business partners who want to have paper forms while

others prefer electronic messages. The condition record created below shows that sales order

confirmations for business partner 2510 are created using medium 6 which means that an electronic

message is created as soon as the sales order has been saved in the SAP system. This is not part of the

customizing but is closer to transactional/master data and thus accessed in the standard SAP user

menu as transaction W11.


11/36

11


An actual sales order document (transaction VA03 display) contains the reference to the output type

and shows the status of this output whether it is paper or other. This is illustrated below. The log for

sales order 9366 show that output type BA00 (order confirmation) has been created in the form of an

IDoc message which has been forwarded for transmission.

At this point we turn to the configuration of the IDoc subsystem where partner profiles are created for

every business partner with whom the system needs to exchange electronic messages. Partner profiles

are accessed using transaction WE20.

Note: for paper output, the process would stop right here.


12/36

12


The sales office is represented as a standard customer, this is explained later. A corresponding partner

profile has been created to define that the system will allow three types of IDoc messages to be sent to

this particular business partner (outbound parameters):

Message Type Description Basic Type

DESADV Advanced shipping notification DELVRY01

ORDRSP Sales order confirmation ORDERS05

INVOIC Sales invoice INVOIC01

In the details of each message type there are further configuration settings like the basic type and their

message control. A basic type is a hierarchical division of messages types. A message type is a generic

name for EDI messages, while a basic type is the message itself. In other words, a message type groups

one or more basic types. The message control parameters define for which specific output type an

IDoc can be created. For the sales order confirmation this is output type BA00.This concludes the setup for the sales order confirmation and invoice messages. The configuration

above allows the automatic creation and transmission of IDocs and uses standard SAP functionality.

Sales Order Confirmation

Sales Document Type OR Standard Order

Output type BA00 Order Confirmation

Output Determination Procedure V10000 Order Output

Message Type ORDRSP Purchase order / order confirmation

Basic Type ORDERS05 Purchasing/Sales

As indicated earlier, the sales order confirmation will only reach the sales office if the parent company

cannot meet the requirements of the purchase order which was sent by the sales office.

Sales Invoice

Billing Type F2 Invoice

Output type RD00 Invoice

Output Determination Procedure V10000 Billing Output

Message Type INVOIC Invoice/Billing Document

Basic Type INVOIC01 Invoice/Billing document

3.1.3 Customizing Logistics Execution in SAP

The advanced shipping notification IDoc is customized in the same way as the sales documents

described above. The output type for this message is LAVA and is created sent after the Goods Issue

(GI) has been posted in the system.

Shipping Notification


13/36

13


Delivery Type LF Delivery

Output Type LAVA Outg. ship.notifica.

Output Determination Procedure V10000 Header Output

Message Type DESADV Delivery: Shipping notification

Basic Type DELVRY01 Delivery interface

3.2 SAP Master Data

Besides the customizing described above, the SAP environment needs master data to process the

business transactions. The following paragraphs describe the master data needed to set up the multi-

site and international organization integration.

3.2.1 Sales offices as customers to parent company

Customer master record 2510

In an all-SAP solution where both parent and sales offices operate within a SAP landscape, the sales

offices would be separate plants and/or sales organizations depending on whether they would carry

inventory or not. This setting would make it possible to register the individual sales activities of every

sales office. However, the multi-site and international organization scenario demands another

approach where end-customer sales are registered at the parent company as monthly net figures

provided by the sales office. The replenishment of stock at a sales office takes place in a vendor-

customer relationship. This allows the parent company to capture its intra-company sales and isolate it

for financial consolidation purposes in a later stage. In order to create this scenario, the sales office is

set up as a standard customer master record in the SAP system. This customer master is referenced

when creating sales orders for the sales office. For this scenario, customer master record 2510 has been

created using transaction XD01.

3.2.2 Sales offices as company codes in SAP

Company code 2510

Sales offices are set up as company codes in order to create financial postings for the consolidation at

the end of the month. Company code 2510 has been created for this purpose in the same way as the

company code 2500 for the parent company.

3.2.3 Products used in transactions

Material master records P-100 up till P-108

Material Masters P-100 up till P-108 have been set up for selling to the sales office. They are finished

products (type FERT) with standard cost price. These material masters are part of the IDES system and

have not been changed for this scenario. Access the material master using transaction MM03.

3.2.4 Price lists

Currently 2 types of price lists have been setup in SAP with the help of transaction VK31. One price list

is an Inter-company Price List providing transfer prices which are prices that are agreed between the

parent company and its sales offices as a purchase price. The other price list is a Retail Price List that

consists of prices that the parent company has set as the suggested retail price when sales are made to

end-customers. The price lists have been created using the standard SAP price list with no

modifications. Only the sales prices (no taxes) are listed. The mechanism for interfacing is using an


14/36

14


IDoc. Only the Inter-company Price List is sent to Microsoft Dynamics NAV for this scenario since

end-customer sales are outside the scope of this scenario.

3.2.5 Chart of accounts

The standard SAP international chart of accounts (INT) is used to do G/L accounting in the parent

company code 2500 and sales office 2510.

Chart of Accounts INT

3.2.6 End-customer masters

The end-customer master data will be interfaced between SAP and Microsoft Dynamics NAV. The

standard SAP customer master has been used with no modifications. The mechanism for the interface

uses a standard SAP IDoc. Each end-customer will have a SAP customer and this same number will be

used in Microsoft Dynamics NAV when an end-customer sale is made. End-customer master data is

transferred for demonstrational purposes but is not used in actual sales transaction.

C1_2510 End-customer 1 for sales office

C2_2510 End-customer 2 for sales office

3.3 Setting up Microsoft Dynamics NAV

The organizational structure in a Microsoft Dynamics NAV sales office is simpler compared to SAP.

There is a company definition with an area of activity represented by a division. This division sells to


15/36

15


end-customers in this scenario and generates sales revenues which, at a later stage, are consolidated in

the SAP Company.

The next paragraph provides the installation steps for Microsoft Dynamics NAV. The setup is based on

the FOB file bundled with this document (Microsoft Dynamics NAVRelease_MBS.zip).

3.3.1 Installation procedures

Install the Microsoft Dynamics NAV database server from the CD using the standard MicrosoftDynamics NAV Installation manual.

Install a Microsoft Dynamics NAV Client from the CD using the standard Microsoft DynamicsNAV Installation manual.

Install the Microsoft Dynamics NAV Application Server from the CD using the standardMicrosoft Dynamics NAV Installation manual.

Use the startup-parameter HUBSPOKE for the NAS

Have the NAS run with a User account which has all rights in the folders in the chapter Setupinformation. In Microsoft Dynamics NAV this user has to have SUPER/ALL rights

Import the FOB file into the database.3.3.2 Post installation setup

In Microsoft Dynamics NAV go to Administrator Application Setup General Company

Information. Fill the fields in the Inter-company tab with the correct information.

Field Description

Timer Interval The interval the NAS uses to poll for XML documents

Item Inbox The folder name where the item documents are saved by SAP XI

Customer Inbox The folder name where the customer documents are saved by SAP XI

Purchase Price Inbox The folder name where the Purchase price documents are saved by SAP XI

Shipment Confirmation Inbox The folder name where the Shipment confirmation documents are saved by SAP XI

Shipment Rejection Inbox The folder name where the Shipment rejection documents are saved by SAP XI

Invoice Inbox The folder name where the invoice documents are saved by SAP XIConsolidation Outbox The folder that is used as standard outbox for consolidation documents


16/36

16


Make sure all these folders exist. Also make sure all these folders have an Archive and Error

subfolder. Processed documents are moved to Archive, documents which result into an error are

moved to Error.

After entering and saving this information the NAS needs to be (re)started. Check the Windows event

log for error or warning messages.

Make sure these folders are available for the user running the NAS from the machine that is running

the NAS.

Drive mappings cannot be used because they probably do not exist in the service context of the user.

3.4 Microsoft Dynamics NAV database modifications

The following paragraphs give a summary of what has been modified in the Microsoft Dynamics NAV

database compared to standard functionality.

3.4.1 Import overall (NAS startup)

Added fields to the Company Information table which represent the import folders of thedifferent kinds of data.

Created a "NAS Code unit" which initializes a timer to process the import folders. Added logic to Code unit 1 to use the NAS with parameter HUBSPOKE.

All data will automatically import.

3.4.2 Import of items (same for customers and purchase prices)

Created inbound table for the XML data. Created new Code unit which uses XMLDOM to import & validate the material data. Used XMLDOM because of some problems with namespace tags which are in the XML

document (mandatory for SAP XI).

Import is done in 2 steps Import into inbound table. Process of the inbound table. This is done because it is now possible to split the process in two: importing and processing

which can be done by 2 different NAS.

3.4.3 Import sales shipment notification Created new Code unit to strip-off the namespace (50005: XMLDOM Remove namespace). Automatically imported into the inter-company inbox transactions. Will not be automatically processed because there is a "manual" decision to be made (No

action/accept/cancel/return to IC partner).

A new function is created in Code unit 427 ICInboxOutboxMgt called ConfPurchDocument, which

matches the imported confirmation with the purchase order based on the field Your Reference.

Once a match is found, the purchase receipts are posted in Microsoft Dynamics NAV. No financial

postings are generated in the General Ledger. The expected cost postings have been set to false in the

Inventory setup.


17/36

17


3.4.4 Import sales shipment rejection (same as sales shipment notification)

A new function is created in Code unit 427 ICInboxOutboxMgt called RejectPurchDocument, which

creates a Handled IC Inbox document. If the user wishes, the purchase order can be exported to SAP

again.

3.4.5 Import invoice (same as sales shipment notification)

A new function is created in Code unit 427 ICInboxOutboxMgt called InvoicePurchDocument, which

matches the imported invoice confirmation with the purchase order based on the field Your

Reference. Once a match is found, the purchase invoice is posted in Microsoft Dynamics NAV. The

financial postings are generated in the General Ledger. Inventory is valued at standard cost based on

the Item. The difference between the standard cost and the purchase price is posted as purchase

variance.

3.4.6 Export of purchase order

There is no change with the export of Purchase Order to SAP. Standard functionality is used.

Export of purchase order to the IC Outbox Transactions, where the user sends to IC Partner.

3.4.7 Export of financial consolidation

Created menu option to start the export. Created new form from where the user can enter start date, end date and filename. After this

the user can start the export.

Created XMLPort for the export of the data.3.4.8 Modified Microsoft Dynamics NAV Objects

The table below summarizes the objects that have been modified to implement the business scenario.

Type ID Name Version List New/Changed

Table 79 Company Information NAVW14.00,NAVNL3.70 Changed

Table 418 IC Inbox Transaction NAVW14.00 Changed

Table 420 Handled IC Inbox Trans. NAVW14.00 Changed

Table 426 IC Outbox Sales Header NAVW14.00 Changed

Table 427 IC Outbox Sales Line NAVW14.00 Changed

Table 50000 Item Synch New

Table 50001 Customer Synch New

Table 50002 Bank Synch New

Table 50003 Purchase Price Synch New

Form 1 Company Information NAVW14.00 Changed

Form 50 Purchase Order NAVW14.00,NAVNL3.70 Changed

Form 50000 Consolidation New

Report 511 Complete IC Inbox Action NAVW14.00 Changed

Report 8001 Inventory Status NAVW14.00 Changed

Codeunit 1 ApplicationManagement NAVW14.00,NL4.00 Changed

Codeunit 427 ICInboxOutboxMgt NAVW14.00 Changed


18/36

18


Codeunit 435 IC Inbox Import NAVW14.00 Changed

Codeunit 50000 NAS Startup Hub-Spoke New

Codeunit 50005 XMLDOM Remove namespace New

Codeunit 50011 Import Item XMLDOM New

Codeunit 50012 Import Customer XMLDOM New

Codeunit 50013 Import Purchase Price XMLDOM New

XMLPort 12 IC Outbox Imp/Exp NAVW14.00 Changed

XMLPort 50002 Consolidation Synch Export New

MenuSuite 90 Company New

3.5 Microsoft Dynamics NAV setup remarks

XMLDOM: There were some difficulties at the start of the project with the namespaces SAP XI deliveredto Microsoft Dynamics NAV (import). The XML ports are not able to work with this.

XMLPorts: For all documents which are exported from Microsoft Dynamics NAV to SAP XI, XMLPorts

are used because these are standard Microsoft Dynamics NAV.

Preprocessor: A pre-processor has been built because there are some documents which are imported

through the same XMLPorts as other documents are exported. There were problems with the

namespace.

File system for transport between SAP and Microsoft Dynamics NAV: The file system for transport is

used because this is a very easy transport and the only one that is fully integrated into Microsoft

Dynamics NAV. Another possibility would have been MSMQ (communication components), especially

when both systems are not on the same location.Costing Method for Items

The costing method is set as Standard Costing in Microsoft Dynamics NAV and SAP. The standard

cost is not changed. If the standard cost has to be changed, it has to be changed in both SAP and

Microsoft Dynamics NAV. Before changing in Microsoft Dynamics NAV, standard functionality of

revaluation has to be followed.

Expected cost posting is set to false for inventory of items

This is done to show General Ledger postings generated by Microsoft Dynamics NAV for inventory is

the same as that is generated by SAP, so as not to complicate the consolidation. Financial postings for

inventory are generated only at invoicing of purchase orders.

All / Nothing on Purchase Receipts / Rejection

Invoices exported from SAP are imported into Microsoft Dynamics NAV as confirmation only,

Microsoft Dynamics NAV posts the purchase orders to invoice based on data available in Microsoft

Dynamics NAV and not on imported Purchase invoice from SAP.

For the purpose of this project, the vendor pricing of items, imported from SAP to Microsoft Dynamics

NAV, is presumed to be static. Only new prices are added for new items that are created in SAP for

export to Microsoft Dynamics NAV.


19/36

19


4. Master Data Upload to Microsoft Dynamics NAVCertain SAP master data will need to be uploaded into Microsoft Dynamics NAV to facilitate the

business processes. This master data needs to be present in Microsoft Dynamics NAV before any

sales/purchase activity can take place. There are four sets of master data to be uploaded to Microsoft

Dynamics NAV:

Chart of Accounts

The chart of accounts as it is defined in SAP will be mirrored in Microsoft Dynamics NAV. A Microsoft

Excel file with all the BS/P&L accounts will be integrated in Microsoft Dynamics NAV. This makes end-

of-month financial bookings and consolidation more straightforward. The file is transferred directly to

Microsoft Dynamics NAV for manual integration and does not pass through the SAP XI server. This was

done because it is a one-time setup and would be relatively time-consuming to process through the

SAP XI server.

Product Master

The standard SAP product master structure is used for purchasing and sales activities. Standard cost

price based information is included. Export to Microsoft Dynamics NAV using the standard IDoc

MATMAS03.

Product Pricing

Two sets of lists are created. One contains the inter-company pricing agreements and the other

contains end-customer pricing recommendations for the sales offices. For this scenario, only the inter-

company price list is interfaced with Microsoft Dynamics NAV. Information upload through the

standard IDoc COND_A01.

End-Customer MasterThis master data is transferred for technical/demo purposes mostly. End-Customers have SAP sales

offices (the sales offices) assigned to them. Customer master records C1_2510 and C2_2510 represent

two end-customers for sales office 2510 for example. Export to Microsoft Dynamics NAV using

standard IDoc DEBMAS06.

Message Type Description BasicType

COND_A Conditions: master data for price determination COND_A01

DEBMAS Customer master data distribution DEBMAS06

MATMAS Material master MATMAS03

4.1 IDoc setup for master data transfer

The outbound IDocs are set up in a similar way as the inbound IDocs discussed earlier. However, the

difference is that the partner profile for the outbound IDocs is linked to a logical system and not to a

customer profile. The logical system is the SAP XI server which is the logical destination of the

outbound IDocs. Second, there is no business trigger for the distribution of master data; this is done

manually using standard SAP transactions. The process of uploading master data is described in detail

in the demo script document.


20/36

20



21/36

21


5. Financial ConsolidationEnd-of-month consolidation will take place in SAP and is done by uploading the total purchasing

amounts from Microsoft Dynamics NAV in a XML file to SAP. SAP NetWeaver is bypassed as a means

of interface. Both Microsoft Dynamics NAV and SAP have the same chart of accounts with identical

G/L accounts, so therefore every account in Microsoft Dynamics NAV is mirrored in SAP.

5.1 SAP specific settings/Financial Statements

In SAP two company codes have been set up: 2500 and 2510. Company 2500 is the parent company

and uses financial statement version 2500 for the end consolidation. This financial statement is defined

by using the totalinter-company accounts. Company 2510 serves as the financial connection betweenMicrosoft Dynamics NAV and SAP. Company 2510 uses a different Financial Statement Version: 2510.

This is a standard SAP financial statement version.

5.2 Interfacing with SAP

To be able to post the purchasing-results from Microsoft Dynamics NAV to SAP it is needed to use a

SAP posting interface which creates an official SAP posting. Therefore we need to use standard BAPI

(Business Application Programming Interfaces). The BAPI used is BAPI_ACC_GL_POSTING_POST. BAPIs

in SAP allow us to post SAP standard postings with all the normal posting checks we need.

5.2.1 Graphic display of the consolidation process

Exchange of purchasing total accounts/amounts:

Explanation:

Above graphics show the matches of the accounts in both system Accounts payable are the total I/C postings on all accounts payable in Microsoft Dynamics

NAV

Finished goods inventory are the totals of the standard cost price of the purchased goods

2510

Accounts Pa able 1 Accounts Pa able

Tax account Tax account

Loss frei ht Variances Loss frei ht Variances

165000

145000

231100

Finished Goods Finished Goods inventor792000


22/36

22


Loss freight variance is the total of the difference between the standard cost price and thetransfer price calculated.

Showing the results on company 2510 in SAP

The results on company 2510 will be shown when running Balance/Financial Statement named 2510.Report RFBILA00 is a standard functionality used to display the Balance/Financial Statement. This

Financial statement is a standard statement.

Showing the consolidation results on company 2500 in SAP

In company 2500 it is needed to see the financial consolidation. Therefore you must run RFBILA00 with

Financial Statement 2500. This Financial statement is made of with the intercompany accounts to show

the total amounts of the consolidation


23/36

23


6. SAP NetWeaver XIThe SAP Exchange Infrastructure (XI) is used in the multi-site and international organization scenario as

an integration broker between SAP and Microsoft Dynamics NAV. The communication between SAP

and XI is carried out by IDOCs (SAP standard interfacing documents) and BAPIs (SAP Business

Objects). In the picture below shows the interfaces.

6.1 Interfacing from and to SAP

There are two interfacing methods used:

IDocOutbound IDocs are documents that can be created by SAP. For example, when a sales order

has been created and saved (trigger) an IDoc with all information of the sales order is sent to

another system.

For SAP inbound IDocs it is possible to trigger an action, e.g. creating a material. Anothersystem can send an IDoc with material master information and SAP can create a material

based on this information.

BAPIBAPIs contain functions that can be executed from outside SAP by using RFC connections.

There is an RFC to create a material. The structure to call this function is far less complex than

sending an IDoc with the same information.


24/36

24


Choice between BAPIs and IDOCS

Due to the complexity of IDocs, the scenario uses BAPIs for the inbound SAP-interfaces. The structures

and tables as input for the BAPIs are less complex than for IDocs. For the outbound SAP interface,

IDocs are implemented, because these are created by SAP and contain far more data than BAPIs can

return.

6.2 Interfaces

Below the interfaces of the multi-site and international organization model are summed up:

Interface Source Destination

1. Materials (IDOC MATMAS03) SAP Microsoft Dynamics NAV

2. Customers (IDOC DEBMAS03) SAP Microsoft Dynamics NAV

3. Pricing (IDOC CondA) SAP Microsoft Dynamics NAV

4. PurchaseOrder (Z_BAPI_CREATESALESORDER FROMDAT2 MicrosoftDynamics NAV

SAP

5. Sales order Rejection (IDOC ORDERS05) SAP Microsoft Dynamics NAV

6. ShipmentNotification (IDOC DELVRY01) SAP Microsoft Dynamics NAV

7. Invoice (IDOC INVOIC01) SAP Microsoft Dynamics NAV

8. Financial Consolidation (BAPI Bapi_Acc_GL_

Posting_Post)

MicrosoftDynamics NAV

SAP

6.2.1 SAP Document definitions

All document definitions of the SAP interfaces are determined based on BAPIs and IDocs in SAP. For

the BAPIs there are input/output definitions, which can be imported in SAP XI. For example theZ_BAPI_SALESORDER_CREATEFROMD2 :

The IDocs are messages defined in SAP. The structure of an IDoc can also be automatically imported

by SAP XI. This is an example of the IDoc MATMAS03:


25/36

25


6.2.2 Document definitions Microsoft Dynamics NAV

The document definitions of Microsoft Dynamics NAV have been added to SAP XI manually, because

there were no XSD schemas available.

6.2.3 Interface Mappings

All mappings are included in the package of SAP XI. The functional description of the mappings are

included in the mapping documents (See appendix).

6.3 Transport

The transport method between XI and Microsoft Dynamics NAV is FTP.

Interface Source Destination Transport Location

1. Materials

(IDOC MATMAS03)

SAP MicrosoftDynamics NAV

FTP/Fileshare

\XMLDocuments\SAP_To_MicrosoftDynamics NAV\Materials

2. Customers

(IDOC DEBMAS03)


FTP/Fileshare

\XMLDocuments\SAP_To_MicrosoftDynamics NAV\Customers

3. Pricing

(IDOC CondA)


FTP/Fileshare

\XMLDocuments\SAP_To_MicrosoftDynamics NAV\Pricing

4. PurchaseOrder

(Z_BAPI_CREATESALESORDER

FROMDAT2

MicrosoftDynamics

NAV

SAP FTP/Fileshare

\XMLDocuments\MicrosoftDynamicsNAV_To_SAP\PurchaseOrder

5. Sales order rejection SAP Microsoft FTP/File \XMLDocuments\SAP_To_Microsoft


26/36

26


(IDOC ORDERS05) Dynamics NAV share Dynamics NAV\OrderConfirmation

5. ShipmentNotification

(IDOC DELVRY01)


FTP/Fileshare

\XMLDocuments\SAP_To_MicrosoftDynamics NAV\ShipmentNotification

6. Invoice

(IDOC INVOIC01)


FTP/Fileshare

\XMLDocuments\SAP_To_MicrosoftDynamics NAV\Invoice

7. Financial Consolidation

(BAPI Bapi_Acc_GL_

Posting_Post)

MicrosoftDynamics

NAV

SAP FTP/Fileshare

\XMLDocuments\ MicrosoftDynamicsNAV_To_SAP\FinancialConsolidation

6.4 Importing the packages in XI

There are four packages to be imported in XI after the standard configuration.

Integration Builder

Package Filename

MBS Integration package XI3_0_GENERATEPRODUCTSCATALOG.tpz

SAP Application XI3_0_SAP_APPL_4.70.tpz

Integration Directory

Package Filename

MES_Natech03 XI3_0_MES_Natech03_1.tpz

TIX_Natech05 XI3_0_TIX_Natech05_1.tpz

To import a package in XI follow the next steps:

1. Copy the file (e.g. XI3_0_SAP_APPL_4.70.tpz to the\\natech05\e$\usr\sap\TIX\SYS\global\xi\repository_server\import directory of the SAP XI

server)

FTP

Server/

File

shareSAP XI Microsoft

D namics

Polling (5 second interval)

Polling (30 second interval)


27/36

27


2. Login to the Integration builder and import the package: Tools/Import Design Objects

3. Select the package from the import directory and press OK

This step completes the import of the package. Repeat the import of each package in the Integration

builder. The integration Directory has the same functionality to import packages (Directory:\\natech05\e$\usr\sap\TIX\SYS\global\xi\directory_server\import ).


28/36

28


7. Custom Abap in the R/3 IDES systemTo apply the demo it is necessary to do some custom ABAP programming in R/3. All the custom ABAP

programs are described in this section.

7.1 Custom BAPI functions

Start transaction SE80. Create a new Function group with the name ZMICROSOFT DYNAMICS NAV.

You have now created a container for the two custom BAPIs which will create the sales order and do

the financial consolidation.

7.1.1 Z_BAPI_SALESORDER_CREATEFROMD2

This BAPI creates a new sales order in the SAP system. It is a wrapper around the standard BAPI

BAPI_SALESORDER_CREATEFROMDAT2. A custom wrapper is used because we can do explicit assumption

about the business scenario and generate an implicit database commit, so the update is made withouta call of a second commit BAPI.

Create a new function with the name Z_BAPI_SALESORDER_CREATEFROMD2.

Check the radio button Remote-enabled module. This enables the BAPI to be called from external

systems. Then go to the Import subscreen and fill in the following data:


29/36

29


Go to the tab Tables:

Now go to the source tab and follow the menu

Utilities more utilities Upload/Download Upload and upload the file

Z_BAPI_SALESORDER_CREATEFROMD2_SOURCE in the folder ABAP Source

7.1.2 Z_BAPI_ACC_GL_POSTING_POST

The next BAPI we have to make is a wrapper around the standard BAPIBAPI_ACC_GL_POSTING_POST.


30/36

30


Also for convenience, a custom BAPI has been created to avoid the necessity to call a second BAPI to

do the commit end for making explicit the functional assumptions explicit.

The steps are the same as the previous one.

Start transaction SE80 and open function group ZMICROSOFT DYNAMICS NAV, if not already open.

Go in the left navigation tree:

Mark Function Modules and in de context menu create a new function module with the name

Z_BAPI_ACC_GL_POSTING_POST.

Now go to the Attribute tab and again mark the radio button Remote-enabled module.


31/36

31


Go to the Import tab:

Go to the export tab:


32/36

32


Go to the tables tab:

Go to the source tab and upload the following file:

Z_BAPI_ACC_GL_POSTING_POST_SOURCE in the map ABAP source

Dont forget to make the function remote enabled!Finally activate the function group.

7.2 User exit

To realize the business scenario where a sales order should be rejected when too much quantity is

required (asking for more than available stock), a custom User-Exit is used just before the sales order is

saved. User-Exit assigns the rejection reason. This rejection reason is then sent with the IDoc message

to SAP XI, which uses content base mapping on this field to decide if it should forward the message to

Microsoft Dynamics NAV or not. Only a rejection should be forwarded to Microsoft Dynamics NAV.

The reason to do this is that the standard IDOC message hasnt any field filled where one can see that

the sales order has been rejected for stock reasons. Weve solved this to fill, just before saving, therejection field. The IDOC which is generated has then a rejection field filled. Succeeding we can make a

content based routing on this field to decide to sent the message to Microsoft Dynamics NAV (sales

order rejected) or not.

Start transaction SE38. Fill in the name MV45AFZZ and click on change.


33/36

33


Now you are asked to give a modification key. Ask for one on the OSS.

Then put some code in the form USEREXIT_SAVE_DOCUMENT_PREPARE. This form is at the end.

Now upload the file userexit_save_document_prepare_SOURCE in the folder ABAP Source and

activate the changes.


34/36

34


8. Custom ABAP in the XI systemMinimal coding is to be done in the SAP XI system. Microsoft Dynamics NAV cannot handle

namespaces in messages and mappings in SAP XI require namespaces. So when a message comes in

from Microsoft Dynamics NAV to SAP XI a namespace has to be added, and when a message goes

from SAP XI to Microsoft Dynamics NAV the namespace has to be removed.

One could argue where these additional steps have to be taken: on the XI side or the Microsoft

Dynamics NAV side. We have decided to do the addition of namespaces in SAP XI and the removing

of namespaces in Microsoft Dynamics NAV.

Furthermore there are more methods to achieve this:

ABAP coding JAVA coding XLST sheets

Weve decided to use XSLT sheets because it is an open standard and it is fully supported by the ABAP

workbench.

Especially the test environment doesnt acquire additional setups, as with JAVA or ABAP coding.

8.1 Removing namespaces in XI

Start transaction SE80. Create a new package ZMICROSOFT DYNAMICS NAV.

To add namespaces we will create XSLT sheets for the two incoming messages from Microsoft

Dynamics NAV: one for the sales order creation and one for the financial consolidation.


35/36

35


8.1.1 The purchase order message

Go to the left navigation window, mark node ZMICROSOFT DYNAMICS NAV and open the context

menu: Create More Transformation. Now you see a modal window:

Fill in the name Z_PO_FROM_MICROSOFT DYNAMICS NAV_TO_SAP in the field Transformation. Enter a

description and transformation type XSLT. Then click enter.

Upload the file Z_PO_FROM_MICROSOFT DYNAMICS NAV_TO_SAP_XSLT in the folder ABAP Source

8.1.2 The financial consolidation message

Go to the left navigation window, mark node ZMICROSOFT DYNAMICS NAV and open the context

menu: Create More Transformation. Fill in the name Z_FC_FROM_MICROSOFT DYNAMICS

NAV_TO_SAP and upload the file

Z_FC_FROM_MICROSOFT DYNAMICS NAV_TO_SAP_XSLT in the folder ABAP Source

Activate the changes.


36/36

9. AppendixFurther details of SAP Microsoft Dynamics NAV interface mappings can be found in the following

files:

Filename

SAP-NAV Customer_Master.xls

SAP-NAV ItemMaster.xls

SAP-NAV Intercompany Product Price List.xls

SAP BAPISOCreate_NAV XML-PO v2.xls

SAP-NAV Sales Invoice (Intercompany).xls

SAP-NAV Sales Order Confirmation (Reject) v2.xls

SAP-NAV Shipping Notification (SAP LAVA).xls

SAP-NAV BAPI GL_POST.xls

About Microsoft Dynamics

Microsoft Dynamics is a line of financial, customer relationship, and supply chain management solutions that help businesses workeffectively. Delivered through a network of channel partners providing specialized services, these integrated, adaptable businessmanagement solutions work like and with familiar Microsoft software to streamline processes across an entire business.

For more information about Microsoft Dynamics, please visit www.microsoft.com/dynamics.

Address:MicrosoftFrydenlunds All 62950 VedbaekDenmarkTel +45 45 67 80 00Fax +45 45 67 80 01

The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication.Because Microsoft must respond to changing market conditions, this document should not be interpreted to be a commitment on the part of Microsoft,and Microsoft cannot guarantee the accuracy of any information presented after the date of publication.

This white paper is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED, OR STATUTORY, AS TO THE INFORMATIONIN THIS DOCUMENT.

Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may bereproduced, stored in or introduced into a retrieval system, or t ransmitted in any form or by any means (electronic, mechanical, photocopying, recording,or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document.Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any li cense to thesepatents, trademarks, copyrights, or other intellectual property.

A4 MIO Instal Guide NetWeave

Documents

Transcript of A4 MIO Instal Guide NetWeave