18. Text Control (1hr 20min)

Question 1

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

Answer 1

1. Identify the source of texts in SD;
2. Describe the criteria that influence text determination;
3. Define and assign text types in Customizing;
4. Edit texts manually in the sales doc.

Question 2

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

Answer 2

Text control.

Question 3

3. Explain the areas where you can maintain texts for your business requirements (4 items):

Answer 3

1. Customer master record;
2. Material master record;
3. Customer-material-info record;
4. In all documents.

Question 4

4. List texts in customer master (4 items):

Answer 4

1. Central texts;
2. Financial accounting texts;
3. SD texts;
4. Contact person texts.

Question 5

5. List texts in material master (2 items):

Answer 5

1. PO text;

2. Sales text.

Question 6

6. Explain texts in business processes (5 items):

Answer 6

1. Stored in master data and copied to the docs;
2. Copied from the reference doc;
3. Texts can be copied in a specific language;
4. You can specify the conditions under which texts are copied (e.g. From reference doc or from master record);
5. You can also copy a standard text into a sales doc (e.g. Christmas greeting).

Question 7

7. Give an overview of text control (5 items):

Answer 7

1. Text control is used to determine text automatically when you create a text object;
2. You can define different text determination procedures for each text object (e.g. Sales doc header or central texts for a customer);
3. Text determination procedure is assigned to a sales doc and consists of different text types;
4. Each text type is attached with an access sequence;
5. You can also bring these text types into the incompletion log during the process.

Question 8

8. List text objects (14 items):
9. Customer (3 items)
10. Info record (1 item)
11. Pricing conditions (2 items)
12. Sales doc (2 items)
13. Delivery (2 items)
14. Billing doc (2 items)
15. Contacts (1 item)
16. Transport (1 item)

Answer 8

1. Customer: central texts, contact person, SD;
2. Info record: customer/material;
3. Pricing conditions: agreements, conditions;
4. Sales doc: header, item;
5. Delivery: header, item;
6. Billing doc: header, item;
7. Contacts: general texts;
8. Transport: header.

Question 9

9. Explain text types in text control (3 items):

Answer 9

1. Text type is created after selecting a specific text object;
2. Text types are like condition types in pricing;
3. Examples for Customer/SD text object: external sales note, shipping instructions, marketing notes.

Question 10

10. Explain access sequence in text control (2 items):

Answer 10

1. Every access step contains a specified text object as the text source for the access;
2. You can specify conditions for each access step to limit the search to specific partner functions, languages and other user defined criteria.

Question 11

11. List the permitted text objects (15 items):

Answer 11

1. KNA1 - central customer texts;
2. KNMT - text for customer material info;
3. KNVK - contact person texts, sales;
4. KNVV - customer texts, sales;
5. KONA - agreement texts;
6. MATERIAL - material texts, purchasing/storage;
7. MVKE - material texts, sales;
8. TEXT - SAP script standard texts;
9. VBBK - sales header texts;
10. VBBP - sales item texts;
11. VBKA - sales CAS texts;
12. WBHI - trading contract item;
13. WBHK - trading contract header;
14. WBRK - agency doc header texts;
15. WBRP - agency doc item texts.

Question 12

12. Explain text determination procedure in text control (4 items):

Answer 12

1. Text types are included in a text determination procedure;
2. Text determination procedures contain all text types available for a text object;
3. The attributes of text determination procedure vary for customer or document text objects;
4. You can determine whether text should be copied or referenced.

Question 13

13. For document text determination procedures you can also specify whether (3 items):

Answer 13

1. A text should be mandatory (incompleteness log);
2. Text should be determined automatically;
3. Whether text is displayed in a text popup window when it is transferred to the document.

Question 14

14. Explain procedure assignment in text control (3 items):

Answer 14

1. Each attribute of a text object must be assigned to a text determination procedure;
2. If the text object belongs to customer for example, you need to assign the customer account group (e.g. 001 SP, 002 SH) to the specific text det. procedure;
3. If the text object belongs to document, the procedure has to be assigned to the sales doc type for header level determination (e.g. OR standard order > 01 sales doc header) and to the item category for item level determination (e.g. TAN normal item > 01 sales doc item).

Question 15

15. Explain analysis in text control (1 item):

Answer 15

You can analyze the text determination by going to menu path: GoTo > Header (or Item) > Texts > Log.

Question 16

16. Explain the use of texts as reference (3 items):

Answer 16

1. As long as text in sales doc 2 refers to text in sales doc 1, it cannot be changed;
2. If text in sales doc 1 is changed, text in sales doc 2 is also changed;
3. If text in sales doc 2 is changed, it looses reference to sales doc 1 (i.e. duplicated).

Question 17

17. Explain the copying texts option (3 items):

Answer 17

1. The duplicated text can be changed in the doc;
2. If text is changed in sales doc 1, it does not affect sales doc 2;
3. This option requires more memory than referencing texts from a source doc.

Question 18

18. Explain text source “preceding document” in the billing document (3 items):

Answer 18

1. Only one source can be referenced as a preceding doc for the text objects VBBK (SD header texts) and VBBP (SD item texts);
2. If you want to use the sales order as the source text then the “text delivery” box in billing type config should not be selected;
3. If you want the delivery doc as the source text, then the box should be selected.

Question 19

19. Explain customer-specific data transfer routines for texts (2 items):

Answer 19

1. Data transfer routines can be created via VOFM t-code;

2. Use numbers between 50 and 99 when creating customer-specific routines.