A.Exception Types

B.Users

C.Suppliers

D.User Group mapping

E.Supplier Catalogs

A.A custom Form Template such as vrealm 1936.formDoc_18697.Lessons Learned

B.A custom Enumeration such as Contracts_Contract Type

C.A custom Flex Master Data Template such as vrealm 1936fmd_58984.Hospital

D.A standard class such as ariiba.basic.core.CommodityCode

A.Only the data of the flex master data templates is migrated; templates must bee created manually.

B.The templates are migrated by the tool, but the data must be loaded manually later.

C.Both the templates and their data are fully migrated by the tool.

D.Neither the templates nor the data is migrated using the tool

A.Select Field Configuration, find the class, and select the Layout tab. Here you can drag and drop the order of the fields. Once all changes are performed, publish all changes via Customizing Publish.

B.Select Field Configuration and under the advanced tab select property Sequence. Fields are sorted by this field in the UL. Once all changes are performed, publish all changes via Customizing Publish.

C.Navigate to the UI where the class is presented, select Customize in the banner, select Edit, and drag and drop the fields in the order they should be presented. Once all changes are performed, publish all changes via Customizing → Publish

D.The fields are presented in alphabetical order of the field label. By carefully choosing the

A.if

B.then

C.replace

D.else