20. System Modifications (1hr 10min)

Question 1

1. What are the module objectives? (3 items)

Answer 1

1. Define the account groups required for maintaining customer master records;
2. Explain how to adapt screens that use the display element “table control” to meet your requirements;
3. Create transaction variants.

Question 2

2. What is the module content? (1 item)

Answer 2

Techniques for avoiding system modifications.

Question 3

3. Explain general data (3 items):

Answer 3

1. Sales data is the basic data for SD;
2. Company code data is the basic data for FI;
3. To make general data valid for both the various codes and sales areas you have to assign it to the clients. This makes the customer number in SD identical as the one in FI.

Question 4

4. The account group, which is a classification within the customer master records, specifies (5 items):

Answer 4

1. Which entries in the master record are required or optional (field selection);
2. The number range for the customer account number;
3. Whether the number is assigned by the user or system (external or internal number assignment);
4. Whether the account is a one-time account or not;
5. Which output determination procedure is used.

Question 5

5. Explain field selection for data groups (3 items):

Answer 5

1. In customer master you find the general data; data specific to SD as well as company code;
2. The field selection allows you to determine which ones are mandatory;
3. You can hide any fields that are not required.

Question 6

6. Explain field selection for account groups (2 items):

Answer 6

1. The standard partner functions for which account groups are already setup are: sold-to party, ship-to party, payer, bill-to party;
2. You can select specific fields for each of these account groups, which depends on the function within the partner function.

Question 7

7. In addition to account group, the transaction for creating, changing and displaying a customer master record also influence field selection. You can use transactions to (5 items):

Answer 7

1. From a SD perspective;
2. From a FI perspective;
3. From both perspectives centrally;
4. To process a customer master record;
5. You can maintain banking details using either the accounting or the central transaction, for example.

Question 8

8. Explain linking rules for field selection (3 items):

Answer 8

1. The field statuses are: hide, display, required or optional;
2. The two influencing factors are: account group and transaction;
3. The field status information for the two factors is combined in pairs and the status with highest priority is always chosen first.

Question 9

9. Table control is a display element that enables you to configure the table view to meet customer requirements. The user can customize the view of the data by (5 items):

Answer 9

1. Changing the sequence of columns;
2. Changing the width of columns (incl. making them invisible);
3. Saving the settings as a display variant;
4. Making the display variant the standard setting;
5. An administrator can also make fields invisible for the whole system.

Question 10

10. Explain transaction variants / screen variants / GuiXT (3 items):

Answer 10

1. Transaction processes can be simplified via screen variants, which can enter default values in the fields, hide and change ready-for-input status of fields or hide whole screens;
2. A transaction variant is made up of screen variants and are only permitted for dialog transactions (variants values not taken into account for batch input or batch input recording);
3. The supplementary tool GuiTX allows for flexible design of individual screens.

Question 11

11. Explain the options for calling transaction variants for VA01 (2 items):

Answer 11

1. Using a variant transaction, which can be incorporated in a user role. It is necessary to assign the entry NO VARIANT in the variant field for the doc type you have called;
2. Using the sales doc type by assigning a transaction variant in the variant field in Customizing.