SAP – Sales and Distribution – Text control – Lesson 12
Text is required by the business to display texts on various outputs in sales order, delivery and billing. Text can be maintained manually in the sales document or can be referenced and copied from previous sales document. Text can be maintained as per language of the customer or the sales organization.
In the document level, text can be displayed both at the header and item level.
Examples of different types of text in sales order
- Reference of previous sales order of the same customer can be given in the header level text of the sales order
- Shipping instructions like delivery of certain items will be done separately due to different shipping requirements like refrigeration.
All such different text types are created and grouped under text objects. Text types from these text objects can be then referenced and copied in the text of subsequent documents.
Standard Text objects
- KNA1 (Group for text types defined in customer master – General / central level)
- KNVV (Group for text types defined in customer master –Sales area level)
- VBBK (Group for text types defined for document type – header or item level)
Text procedure – It lists all the text types required for customer master or document.
Text procedure determination
- Customer master – Based on customer account group
- Document - Based on document type like order / delivery / billing type and item category
Source for text type can be from different sources. This is configured assigning access sequence to text type.
Example – Sales note for customer text in sales order can be searched from reference sales document like contract or customer master text at sales area / general level.
Follow Menu Path: IMG –> Sales and Distribution –> Basic Functions –> Text control
Customer Master Text
Let us understand how text control can be used in the customer master.
List types of text (called here as Text type) are required at central / general level of the customer master.
Create text types for these
All these text types exist as a part of text object, KNA1 (text objects group text types of same object, example – texts created at central level of customer fall under text object, KNA1)
Step 2: Add text types in text determination procedure
Click on “Display”
Enter these text types as a part of Text procedure.
Select text procedure 01 and click on
Now, assign text procedure 01 to customer account group, 0001 used for sold-to party so that all the text types required in the text at customer – central level are available while maintaining customer master.
After the above configuration is setup, check where these texts are available in customer master data
Double click any of these text ids and enter text and
Pricing condition text
It is configured similarly for pricing condition text, which is configured for a condition type.
Sales document text
In case of sales order, delivery and billing document, text can be maintained both at header and item level.
There are 2 additional configurations when compared with customer master text.
Each text type can be configured to be mandatory.
Each text type will have an access sequence that will make it possible to control the source of the text from various text objects.
Let us see how it can be set for text in a sales order.
List types of text (called here as Text type) are required at the sales order, header level.
All standard text types are displayed. TextID identifies text type in configuration.
For each of the text type, the text can be copied from text types of different text objects.
This is managed using access sequence.
Text objects for sales order header level can be
Sales header text (VBBK) – Text could be copied from reference contract header level text or other sales order header text
Central customer text (KNA1) - Text could be copied from customer master text, at the central level.
Customer texts, sales (KNVV) – Text could be copied from customer master text, at the sales area level.
Click on Access sequence for text ID’s
Search is done from different text objects. Search stops once system gets the text.
Access 10 above checks whether reference document exists for the document in process.
(This is done using requirement program /routine 1)
If it exists then it copies text from the reference document for that text type. Text is copied in all the languages, in which it is maintained in the reference sales document.
Access 30 – If no text found in access10, then it searches text in the sales area text of sold-to party customer in the language of the sold-to party customer.
Access 40 - If no text found in access 30, then it searches text in the sales area text of sold-to party customer in the language of the sales organization of the document.
This search continues till access 50. If no text found then text is blank in the document.
Add text types in text procedure
In a text procedure, some of the text types can be made mandatory choosing
Last column shows access sequence assigned. Step 4:
Assign text determination procedure to the sales order type. Click on
Delivery and billing texts are setup similarly at header and item level.