Mapping of the GatewayDocSetup to - Microsoft Dynamics AX Implementation Guide

IntercompanyEndpointActionPolicy tables

This table shows the mapping of the GatewayDocSetup to IntercompanyEndpointActionPolicy tables.

Commerce Gateway Field

AIF Field Comments

GatewayOrgId

Foreign key from the AifEndoint table. This field is mapped directly.

This focuses only on SalesOrder and PurchOrder enumerations because intercompany is developed to use these two options specifically.

The SalesOrder and PurchOrder enumerations are mapped to the #DefaultSalesOrderAction and

#DefaultPurchaseRequisitionAction defined in the Intercompany macro.

Note All other fields in the IntercompanyEndpointActionPolicy table are set to their default values.

Before you begin upgrading

Before you begin upgrading, be aware of the following restrictions and requirements.

Restrictions

There are a number of upgrade restrictions that you should be aware of before actually starting the upgrade:

Version support

Upgrade to Microsoft Dynamics AX 4.0 must be from Microsoft Axapta 3.0 with or without one of the service packs.

Because data dictionary changes, and as a consequence DEL_ prefixed tables and fields, are typical from one version to the next, you cannot skip a full version when you

upgrade. For example, you cannot upgrade Axapta version 2.5 information directly to Microsoft Dynamics AX version 4.0. You must upgrade to version 3.0 first, and then to version 4.0. If you skip a version, the data upgrade facilities cannot handle data upgrade, and you are liable to lose data. For more information about upgrading from versions prior to Axapta 3.0, see Note on upgrading from releases prior to 3.0.

Upgrade restriction: Axapta 3.0 with multi-code page data cannot be upgraded

Axapta 3.0 had the documented limitation that a single Microsoft Dynamics AX installation could not use multiple code pages, and that such installations were not supported. Partners may nevertheless have succeeded in making such installations work in version 3.0. These installations cannot be upgraded to Microsoft Dynamics AX.

During the upgrade to Unicode, the database code page is used and multi-code page data cause data corruption:

 If the "enable database for Unicode" option is not selected, all character data (string and memo) that is not in the code page of the database is lost.

 If the "enable database for Unicode" option is selected, any data of the memo data type that is not in the code page of the database is lost.

For more information about the Unicode upgrade, see About the Dynamics AX DB Upgrade Preparation Tool.

Requirements

Before you begin upgrading, check the following:

Set appropriate user permissions

Before beginning the Microsoft Dynamics AX upgrade process, ensure that the account you log on with on each server has appropriate permissions. The permissions listed below are implemented using the principle of least privilege.

Note If you upgrade Microsoft Dynamics AX using a domain account other than your own, that account must have appropriate permissions in the system.

Action Permissions required for account

Install Application Object Server (AOS) Member of Administrators group on the local computer

Create a Microsoft SQL Server database Member of Database Creators role on the SQL Server instance

Connect AOS to a SQL Server database Member of Database Security

Administrators role on the SQL Server instance

Create Oracle database Member of SYSDBA on Oracle database server

Connect AOS to an Oracle database Member of SYSDBA on Oracle database server

Install application file server Member of Administrators group on the local computer

Install Microsoft Dynamics AX client Member of Administrators group on the

Action Permissions required for account local computer

Run the DB Upgrade Preparation Tool SQL Server – Ensure all objects are created with dbo as the owner. The minimum level of permissions for the user that is running the tool to ensure this happens is that they are a member of the ddl_admin, db_datareader and db_datawriter roles.

Oracle – Create a user called ―dbo‖ with a random maximum length password (20 characters). All objects created must be created with the dbo user as the

owner/schema.

Run the Upgrade checklist During the client startup, the current Windows user is designated as the Microsoft Dynamics AX Administrator.

In Axapta 3.0: Move any packed identification references

The record identification upgrade handled by the Microsoft Dynamics Database Preparation Upgrade tool is unable to locate existing record identification references that are packed inside containers and stored in the database. Such record identification references must be moved to a dedicated field prior to the upgrade.

In your Axapta 3.0 modifications, this is what you should look for:

 A class that extends the SysPackable class, and

 A field containing a record identification is packed inside the pack() method of that class, and

 The packed data is subsequently saved to a database table.

If your Axapta 3.0 code has such modifications, this is what you must do before running the Dynamics AX Database Preparation Upgrade tool:

1. Create a dedicated field in the relevant table to store the record identification reference.

2. Unpack existing packed data and move it into the dedicated field.

This is needed to ensure that data import and export can correctly handle record identifications.

In Axapta 3.0: Disable Keep update objects configuration key

If not already done, disable the Keep update objects configuration key

(SysDeletedObjects30). This ensures that redundant tables and fields with prefix DEL_

are deleted from your system when the system is synchronized.

If these application objects with prefix DEL_ are left in your system, you are prompted to delete them later when you synchronize during upgrade to Microsoft Dynamics AX 4.0.

Back up your data

Before you begin upgrading you should:

 Back up your existing Axapta application files (*.aod, *.add, *.ald, *.ahd, and

*.khd files).

 Back up your data. See SQL Server information at Microsoft SQL Server documentation.

 Back up your local hard drive.

Disconnect Internet connections

Do not have any Internet connection to the Application Object Servers or database servers during upgrade to reduce the chance of outside attack.

Clean up data

Remove data in the Microsoft Axapta 3.0 database that is not needed for audit trails, and that is slowing down performance or making the database unnecessarily large.

Before you upgrade your database, select the type of data that you want to clean up by using the standard filtering mechanism.

1. Start Axapta 3.0 in your test environment (Start > All programs > Navision Axapta), and log on.

2. Open the Application Object Tree (AOT).

3. Under \Menu Items\Action, open and run the following forms to clean up the respective types of data:

 SysUserLogCleanUp

 SysDatabaseLogCleanUp

 ProdJournalCleanUp

 InventJournalCleanUp

 ProdTableCleanUp

 SalesParmCleanUp

 PurchParmCleanUp

 LedgerJournalCleanUp

In document Microsoft Dynamics AX Implementation Guide (Page 87-91)