Task List

Simon and Isaac manage a Configuration in

Configurations Tree
AX7 technical preview

 2015 Microsoft Corporation. All rights reserved.

This document is provided as-is. Information and views expressed in
this document, including URL and other Internet Web site references,
may change without notice. You bear the risk of using it.
Some examples are for illustration only and are fictitious. No real
association is intended or inferred.
This document does not provide you with any legal rights to any
intellectual property in any Microsoft product. You may copy and use
this document for your internal, reference purposes.

Microsoft Confidential

Scenario setup
Focuses on a tool to manage customizations of the structure of
electronic documents (due to the implementation of new legal
requirements, for instance) that are required in particular business
processes
Presents the ability to either introduce your own customizations of
such documents structure or adopt any changes to it that have been
made by other party service provider managing such documents
Assumes that the business domain for usage of such documents is
electronic bank payments area and configuring documents should
contain all required details of payments providing via UK BACS
system
Use the GBSI legal entity (logged company) of your AX instance for
this scenario

Microsoft Confidential

Scenario setup 2 Vendor bank account

Go to Accounts payable > All vendors
Select Vendor GB_SI_000001
Click Vendor > Bank accounts to create a vendor bank account

Click New
Set Bank account to OPER
Set Name to Operational GBP
Set Bank group to BankEUR
Set Routing number to 800008
Set Bank account number to 700007
Set SWIFT to BARCGB22
Set IBAN to GB75BARC20041568088306
Set Currency to GBP
Click Save and close the form

In the Vendor form

Set a default Bank account to OPER
Set a default Tax exempt number to DE123321123
Click Save
4

Microsoft Confidential

Scenario subjects / objects

Simon
represents Litware, Inc. company (http://www.litwareinc.com/ )
located in UK and have customers in EU

dealing as MS partner with AX competence

subscribed to MS service of AX maintenance including support of payment
formats in accordance to EU law
providing own customers with a service of adoption of EU payment formats
to UK local requirements

Isaak
represents Proseware, Inc. company (http://www.proseware.com/ )
located in UK and have vendors in EU

using AX ERP solution (for making payments to vendors as well)

as using EU payments electronic formats, subscribed to Litware service of
maintenance of payment formats in accordance to EU law and UK local
requirements

Microsoft Confidential

Task 1
As your AX instance will represent the environment of both involved
companies, create individual records to introduce them as a
configuration providers for identifying developed by them
configurations in case of using them in other locations / instances:
Open configuration provider table form:
Please, note that Microsoft record is already available presenting MS as a
provider of configurations for service subscribers (including Simon)

Create a new record in it for Litware, Inc. company having

http://www.litware.com internet address
Create a new record in it for Proseware, Inc. company having
http://www.proseware.com internet address

Microsoft Confidential

Task 2
According to service subscription, Simon registered a new repository A
to get from it all incoming from MS configurations:
Open the configuration list
Register a new repository
Select Ax resources repository type*
Select Microsoft as a Configuration provider
Name it as MS repository

* In the future Ax resources type will be replaced by LCS one to get

online access to MS configurations stored in cloud based Microsoft Life
Cycle Services from any AX instance.

Microsoft Confidential

Task 3
As a service provider in UK (support of payment formats in accordance
to EU and UK laws), Simon registered a new repository B for storing his
outgoing configurations to be distributed among subscribed customers
(including Isaak):
Open the configuration list
Register a new repository
Select File system repository type*
Select Litware, Inc. as a Configuration provider
Name it as Litware repository

* In the future File system type will be replaced by LCS one to get online
access to partners configurations stored in cloud based Microsoft Life
Cycle Services from any AX instance.

Microsoft Confidential

Task 4
According to service subscription, Isaak registered a new repository C
in his AX instance to get from it all incoming from Litware, Inc.
configurations:
No actions are needed in this task as we use same AX instance to
represent Simons and Isaaks AX installations and registered by
Simon outgoing Litware repository will play the role of incoming
Litware repository for Isaak.

Microsoft Confidential

Task 5
As a subscriber of MS service, Simon received a notification about new
EU payment format availability*. He uploaded UK BACS version 1.1
format configuration from repository A to his AX instance:

10

Open the configuration list

Open earlier created MS repository
Select UK BACS format configuration in configurations tree
Select version 1.1 of UK BACS format configuration
Import selected format configuration with all its parent ones to the
current AX instance

Microsoft Confidential

Task 6
Take a few minutes and review the imported UK BACS configurations:
Open the Configurations list form
Select UK BACS format configuration:
Select its completed version 1.1
Review its format structure and using datasources, applicability in AX
companies from country related jurisdiction stand point, validity period, etc.

Select Payments model configuration:

Select its completed version 1
Review its model structure and using AX datasources for accessing data,
validity period, etc.

11

Microsoft Confidential

Task 7
Simon tested uploaded UK BACS version 1.1 format on non-posted yet
payment journal to create credit transfer payments electronic document
in GBSI company:
Open the payment journals form
Create a new Vendor payment journal and open Journal lines
Create Payment proposal for vendor GB_SI_000001 and transfer
proposal to the journal lines
Initiate payment generation process:
select Electronic reporting format option
select UK BACS payment format (imported earlier)
define a file name of generating electronic payment
select GBSI OPER bank account* for lines filtering
define processing date

Confirm payment generation process execution

Review created file with electronic payment document:

Compare its content with the structure of the format explored earlier
12

Microsoft Confidential

Task 8
As a service provider for MS customers managing localizations in UK,
Simon implements a new UK specific requirement for UK BACS
payment format: in addition to company name, present in each
payment record its residence country code:
Create a new UK BACS (local) format configuration:
deriving it from UK BACS configuration 1.1 (earlier received from MS)

Localize this format of electronic payment document:

Edit existing format by adding a new vendCountryResidenceCode:
type String component with min and max length limits defined as 2
new child of transaction component positioning between vendName and
amount components

Use Mapping to Bind inserted vendCountryResidenceCode format

component with CountryOfResidence field of Creditor record from
Payments records list of used data model
Complete the draft version of UK BACS (local) format configuration as
version 1.1.1
13

Microsoft Confidential

Task 9
Simon tested localized UK BACS (local) version 1.1.1 format on nonposted yet payment journal for actual credit transfer payments in GBSI
company:
Perform same payment generation steps as it was done for UK BACS
version 1.1:

if you use the same payment lines reset Payment status to None
except payment format selection: instead of UK BACS the format UK BACS
(local) must be selected

Review created file with electronic payment document:

Compare its content with the structure of the using format

Compare its content with the result of usage of version UK BACS 1.1
make sure that the residence country code is presented in payment lines

Simon started using this for actual payments processing

14

Microsoft Confidential

Task 10
Simon uploaded completed & tested UK BACS (local) configuration
version 1.1.1 to repository B to make it available for subscribed
customers (including Isaak):
Open the configuration list
Select competed UK BACS (local) configuration version 1.1.1
Upload it into Litware repository
Open the configuration list
Open Litware repository
Select competed UK BACS (local) configuration in the tree
make sure that UK BACS (local) configuration version 1.1.1 is in there
as well as parent UK BACS version 1.1 and Payments version 1

Subscribed customers are notified about this format*

15

Microsoft Confidential

Task 11
Isaak received* Simons notification about availability of UK BACS
(local) configuration version 1.1.1. He uploaded it from repository C to
his AX instance:
No actions are needed in this task as we use same AX instance to
represent Simons and Isaaks AX installations and created by Simon
UK BACS (local) configuration version 1.1.1 already looks like
uploaded by Isaak
Isaak started using it for actual payments processing

16

Microsoft Confidential

Task 12
Isaak received a request to make specific customization for the UK
BACS format of the Barclay bank his company is using for payments
processing: to present for each payment record creditors bank SWIFT
code:
Create a new UK BACS (local & Barclay specific) format
configuration:
deriving it from UK BACS (local) configuration 1.1.1 (earlier received
from Litware, Inc.)

Customize this format of electronic payment document:

Edit existing format by adding a new vendBankAccSwiftCode:
type String component with min and max length limits defined as 8
new child of transaction component positioning between
vendBankAccNum and vendName components

Bind inserted vendBankAccSwiftCode format component with BICFI

field (Bank Identification Code) of CreditorAgent record of Payments
records list of using data model
Complete the draft version of UK BACS (local & Barclay specific)
format configuration as version 1.1.1.1
17

Microsoft Confidential

Task 13
Isaak tested customized UK BACS (local & Barclay specific) version
1.1.1.1 format on non-posted yet payment journal for actual credit transfer
payments in GBSI company:
Generate payments document as it was done for UK BACS version 1.1:
if you use the same payment lines reset Payment status to None
except payment format selection: instead of UK BACS the format UK BACS
(local & Barclay specific) must be selected

Review created file with electronic payment document:

Compare its content with the structure of the using format
Compare its content with the result of usage of UK BACS 1.1
Compare its content with the result of usage of UK BACS (local) 1.1.1
note that the SWIFT bank code is presented in payment lines
as well as residence country code introduced earlier

Isaak started using this for actual payments processing

18

Microsoft Confidential

Task 14
Simon implements a new UK specific requirement for UK BACS (local)
payment format: present in each payment record creditors account
IBAN code:
Select draft version of UK BACS (local) format configuration:
Localize this format of electronic payment document:
Edit existing format by adding a new vendBankAccIBANCode:
type String component with min and max length limits defined as 22
new child of transaction component positioning between
vendBankAccNum and vendName components

Bind inserted vendBankAccIBANCode format component with IBAN

field of Identification record of CreditorAccount record from
Payments records list of used data model
Complete the current draft version of UK BACS (local) format
configuration as version 1.1.2 and upload it to repository B

Subscribed customers are notified about this format*

19

Microsoft Confidential

Task 15
Isaak received* Simons notification about availability of UK BACS
(local) configuration version 1.1.2. He uploaded it from repository C to
his AX instance:
As we use same AX instance to represent Simons and Isaaks AX
installations, created by Simon UK BACS (local) configuration
version 1.1.2 already looks like uploaded by Isaak

20

Microsoft Confidential

Task 16
Isaak wants to adopt Simons changes from UK BACS (local)
configuration version 1.1.2 in his customized UK BACS (local &
Barclay specific) configuration version 1.1.1.1:
Rebase UK BACS (local & Barclay specific) format configuration
from UK BACS (local) version 1.1.1 to version 1.1.2 in a new draft
version of UK BACS (local & Barclay specific)
Verify a new created version of UK BACS (local & Barclay specific)
Simons localizations and Isaaks customization are presented in a new
draft version: creditors residence country code, bank SWIFT code and
IBAN account code are in place
No conflicts between introduced localization and customization changes
have been discovered

Isaak completed this configuration draft version as 1.1.1.2

21

Microsoft Confidential

Task 17
Isaak tested customized UK BACS (local & Barclay specific) version
1.1.1.2 format on non-posted yet payment journal for actual credit transfer
payments in GBSI company:
Generate payments document as it was done for UK BACS version 1.1:
if you use the same payment lines reset Payment status to None
except payment format selection: instead of UK BACS the format UK BACS
(local & Barclay specific) must be selected

Review created file with electronic payment document:

Compare its content with the structure of the using format
note that the bank account IBAN code is presented in payment lines
as well as the SWIFT bank code introduced earlier
as well as residence country code introduced earlier

Isaak started using this for actual payments processing

22

Microsoft Confidential

Task 18
Assume that Isaak wants to make latest Simons format changes
effective from Jan 1st, 2016:
Define UK BACS (local & Barclay specific) format configuration
version 1.1.1.2 effective from Jan 1st, 2016
Make sure that session date is earlier than Jan 1st, 2016
Create payments document as it was done for UK BACS version 1.1:
selecting format UK BACS (local & Barclay specific)

Review created file with electronic payment document:

as session date is before Jan 1st, 2016, version 1.1.1.1 is in use:
note that the bank account IBAN code is not presented in payment lines
unlike introduced earlier SWIFT bank code and residence country code

Change session date to Jan 1st, 2016

Create payments document as it was done for UK BACS version 1.1:
selecting format UK BACS (local & Barclay specific)

Review created file with electronic payment document:

as session date is Jan 1st, 2016, version 1.1.1.2 is in use:
note that the bank account IBAN code is presented in payment lines
as well as introduced earlier SWIFT bank code and residence country code
23

Microsoft Confidential