ger managing a configuration in a configuration tree

8/19/2019 GER Managing a Configuration in a Configuration Tree

1/23

Task List

Simon and Isaac manage a Configuration inConfigurations Tree

AX7 technical preview


2/23

Microsoft Confidential2

© 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 realassociation 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 usethis document for your internal, reference purposes.


3/23


Scenario setup• Focuses on a tool to manage customizations of the structure of

electronic documents (due to the implementation of new legalrequirements, for instance) that are required in particular businessprocesses

• Presents the ability to either introduce your own customizations of

such documents structure or adopt any changes to it that have beenmade 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 shouldcontain all required details of payments providing via UK BACS

system• Use the GBSI legal entity (logged company) of your AX instance for

this scenario


4/23


Scenario setup 2 – Vendor bank accountGo to Accounts payable > All vendors

Select Vendor GB_SI_000001Click Vendor > Bank accounts to create a vendor bank account

Click NewSet Bank account to OPERSet Name to Operational GBP

Set Bank group to BankEURSet Routing number to 800008Set Bank account number to 700007Set SWIFT to BARCGB22Set IBAN to GB75BARC20041568088306Set Currency to GBPClick Save and close the form

In the Vendor formSet a default Bank account to OPERSet a default Tax exempt number to DE123321123Click Save


5/23


Scenario subjects / objectsSimon

represents ‘Litware, Inc.’ company ( http://www.litwareinc.com

/ )located in UK and have customers in EU

dealing as MS partner with AX competencesubscribed to MS service of AX maintenance including support of paymentformats in accordance to EU law

providing own customers with a service of adoption of EU payment formatsto UK local requirements

Isaakrepresents ‘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 ofmaintenance of payment formats in accordance to EU law and UK localrequirements

http://www.litwareinc.com/http://www.litwareinc.com/http://www.proseware.com/http://www.proseware.com/http://www.proseware.com/http://www.litwareinc.com/


6/23


Task 1As your AX instance will represent the environment of both involvedcompanies, create individual records to introduce them as aconfiguration providers for identifying developed by themconfigurations 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 aprovider of configurations for service subscribers (including Simon)

Create a new record in it for Litware, Inc. company havinghttp://www.litware.com internet addressCreate a new record in it for Proseware, Inc. company havinghttp://www

.proseware.com internet address

http://www.litware.com/http://www.proseware.com/http://www.proseware.com/http://www.proseware.com/http://www.litware.com/


7/23Microsoft Confidential7

Task 2According to service subscription, Simon registered a new repository Ato get from it all incoming from MS configurations:

Open the configuration listRegister a new repository

Select Ax resources repository type*Select Microsoft as a Configuration providerName it as MS repository

* In the future Ax resources type will be replaced by LCSone to getonline access to MS configurations stored in cloud based Microsoft LifeCycle Services from any AX instance.



Task 3As a service provider in UK (support of payment formats in accordanceto EU and UK laws), Simon registered a new repository B for storing hisoutgoing configurations to be distributed among subscribed customers(including Isaak):

Open the configuration listRegister a new repository

Select File system repository type*Select Litware, Inc. as a Configuration providerName it as Litware repository

* In the future File system type will be replaced by LCSone to get onlineaccess to partners configurations stored in cloud based Microsoft LifeCycle Services from any AX instance.


9/23



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

Open the configuration list

Open earlier created MS repository Select UK BACS format configuration in configurations treeSelect version 1.1 of UK BACS format configurationImport selected format configuration with all its parent ones to thecurrent AX instance



Task 6Take a few minutes and review the imported UK BACS configurations:

Open the Configurations list formSelect UK BACS format configuration:

Select its completed version 1.1

Review its format structure and using datasources, applicability in AXcompanies 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.



Task 7Simon tested uploaded UK BACS version 1.1 format on non-posted yetpayment journal to create credit transfer payments electronic documentin GBSI company:

Open the payment journals formCreate a new Vendor payment journal and open Journal lines

Create Payment proposal for vendor GB_SI_000001 and transferproposal to the journal linesInitiate payment generation process:

select Electronic reporting format optionselect UK BACS payment format ( imported earlier )define a file name of generating electronic payment

select GBSI OPER bank account* for lines filteringdefine processing date

Confirm payment generation process executionReview created file with electronic payment document:

Compare its content with the structure of the format explored earlier



Task 8As a service provider for MS customers managing localizations in UK,Simon implements a new UK specific requirement for UK BACSpayment format: in addition to company name, present in eachpayment 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 2new child of transaction component positioning between vendName andamount components

Use Mapping to Bind inserted vendCountryResidenceCode formatcomponent with CountryOfResidence field of Creditor record fromPayments records list of used data modelComplete the draft version of UK BACS (local) format configuration asversion 1.1.1


14/23



Task 10Simon uploaded completed & tested UK BACS (local) configurationversion 1.1.1 to repository B to make it available for subscribedcustomers (including Isaak):

Open the configuration listSelect competed UK BACS (local) configuration version 1.1.1Upload it into Litware repository

Open the configuration listOpen Litware repository Select competed UK BACS (local) configuration in the tree

make sure that UK BACS (local) configuration version 1.1.1 is in thereas well as parent UK BACS version 1.1 and Payments version 1

Subscribed customers are notified about this format*



Task 11Isaak received* Simon’s notification about availability of UK BACS(local) configuration version 1.1.1. He uploaded it from repository C tohis AX instance:

No actions are needed in this task as we use same AX instance to

represent Simon’s and Isaak’s AX installations and created by SimonUK BACS (local) configuration version 1.1.1 already looks likeuploaded by Isaak

Isaak started using it for actual payments processing



Task 12Isaak received a request to make specific customization for the UK

BACS format of the Barclay bank his company is using for paymentsprocessing: to present for each payment record creditor’s bank SWIFTcode:

Create a new UK BACS (local & Barclay specific) formatconfiguration:

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 8new child of transaction component positioning betweenvendBankAccNum and vendName components

Bind inserted vendBankAccSwiftCode format component with BIC FIfield (Bank Identification Code) of CreditorAgent record of Paymentsrecords list of using data modelComplete the draft version of UK BACS (local & Barclay specific)format configuration as version 1.1.1.1



Task 13Isaak tested customized UK BACS (local & Barclay specific) version1.1.1.1 format on non-posted yet payment journal for actual credit transferpayments 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 selectedReview created file with electronic payment document:

Compare its content with the structure of the using formatCompare its content with the result of usage of UK BACS 1.1Compare its content with the result of usage of UK BACS (local) 1.1.1

note that the SWIFT bank code is presented in payment linesas well as residence country code introduced earlier

Isaak started using this for actual payments processing



Task 14Simon implements a new UK specific requirement for UK BACS (local)payment format: present in each payment record creditor’s accountIBAN 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 22new child of transaction component positioning betweenvendBankAccNum and vendName components

Bind inserted vendBankAccIBANCode format component with IBANfield of Identification record of CreditorAccount record fromPayments records list of used data modelComplete the current draft version of UK BACS (local) formatconfiguration as version 1.1.2 and upload it to repository B

Subscribed customers are notified about this format*



Task 15Isaak received* Simon’s notification about availability of UK BACS(local) configuration version 1.1.2. He uploaded it from repository C tohis AX instance:

As we use same AX instance to represent Simon’s and Isaak’s AX

installations, created by Simon UK BACS (local) configurationversion 1.1.2 already looks like uploaded by Isaak



Task 16Isaak wants to adopt Simon’s 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 configurationfrom UK BACS (local) version 1.1.1 to version 1.1.2 in a new draftversion of UK BACS (local & Barclay specific)Verify a new created version of UK BACS (local & Barclay specific)

Simon’s localizations and Isaak’s customization are presented in a newdraft version: creditor’s residence country code, bank SWIFT code andIBAN account code are in placeNo conflicts between introduced localization and customization changeshave been discovered

Isaak completed this configuration draft version as 1.1.1.2



Task 17Isaak tested customized UK BACS (local & Barclay specific) version1.1.1.2 format on non-posted yet payment journal for actual credit transferpayments 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 Noneexcept 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 earlieras well as residence country code introduced earlier

Isaak started using this for actual payments processing


23/23

Task 18Assume that Isaak wants to make latest Simon’s format changeseffective from Jan 1 st, 2016:

Define UK BACS (local & Barclay specific) format configurationversion 1.1.1.2 effective from Jan 1 st, 2016Make sure that session date is earlier than Jan 1 st, 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 1 st, 2016, version 1.1.1.1 is in use:

note that the bank account IBAN code is not presented in payment linesunlike introduced earlier SWIFT bank code and residence country code

Change session date to Jan 1 st, 2016Create 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 1 st, 2016, version 1.1.1.2 is in use:note that the bank account IBAN code is presented in payment linesas well as introduced earlier SWIFT bank code and residence country code

ger managing a configuration in a configuration tree

Documents