Ansicht
Dokumentation

SIMG_XXMENUOLSDVOTX4 - Set Up Text Determination for Billing Item

SIMG_XXMENUOLSDVOTX4 - Set Up Text Determination for Billing Item

CL_GUI_FRONTEND_SERVICES - Frontend Services   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.
SAP E-Book

Set up the rules used to perform text determination.

You can define the rules that should be used to perform text determination.

You can define text determination rules for the following text objects:

  • Customer master
  • Sales document header, sales document item, delivery header, billing header, billing item

As a result, when you are creating or editing a customer master record or a sales and distribution (SD) document, the system runs the text determination procedure that has been defined for text types (that is, text IDs), such as item notes, production memos, and packing and shipping notes.

Prerequisites

Define text types for text objects.

Defining Access Sequences for Determining Texts

You can define access sequences to be used in a text determination procedure for the text object. The access sequence defines how the system is to search for texts.

When creating access sequences, their IDs must range from 9000 to 9999. You can delete custom access sequences.

NOTE: You can define access sequences only for text objects in SD documents. There is no need to define access sequences for customer master, because texts are not copied but manually specified by users.

In each access sequence, you need to define the sequence and search requirements.

This allows you, for example, to have the system check whether a text exists in the customer language. If this is not the case, the system can search for a text in the sales organization's language. If this is also unsuccessful, you can have the system carry out the search in English.

You can make the following specifications for each access sequence:

  • SeqNo (sequence number)
You can define the order in which the text objects of an access sequence are read. The element with the lowest number is read first. If an appropriate text is found, the search ends. Otherwise, the system checks the element with the next lowest number.
For a standard access sequence, sequence numbers for text IDs must range from 90 to 99. For a custom access sequence, sequence numbers for text IDs must range from 0 to 99. You can delete custom entries for text IDs in an access sequence.
  • Text object
You can define which text objects are checked by the system for an access sequence.
In the standard system, for example, in the access sequence 0001 for the text object sales document header, the system first searches for a form header text in the preceding document (text object VBBK) and then for a sales note in the customer master record (text object KNVV).
  • ID (text type)
You can define which text type is read from the specified text object.
It is recommended that you select the same text type for the source text and target text involved in text determination. For example, the text for the sales note for customer (text type 0001) in the customer master record should be copied to the sales note for customer (text type 0001) of a sales document.
  • Text name
You can specify the text name of a predefined standard text. If a standard text serves as the text source, set the text object to "TEXT", the text ID to "ST", and enter a text name here.
NOTE: The standard text must have been maintained in the Maintain Standard Texts app.
  • Partner function
For texts copied from a customer master record, you can define which partner function is included in the text search.
  • Original language
You can specify language requirements for the text to be copied:
  • All Languages

The system copies texts regardless of language.
  • Language

The system copies texts available in specified language.
  • Partner Function Language

The system copies texts available in the language of the specified partner.
For example, if you specify the partner function of the sold-to-party, the text is only copied if it is available in the sold-to-party's language.
  • Sales Organization Language

The system copies texts available in the sales organization's language.

In each access, you can also assign custom routines for copying requirements and data transfer, if relevant BAdIs have been implemented in the Custom Logicapp:

  • Copying requirement
If you have assigned a copying requirement to an access, text copying occurs only if the requirement is fulfilled.
  • Data transfer
If you have assigned a data transfer routine to an access, the system copies the text source defined in the relevant BAdI implementation, instead of the default one predefined in the access.

NOTE: For every text type, you must maintain separate access sequences.

NOTE

  • Existing requirements are pre-delivered by SAP and refer to copying text from preceding documents.
  • For every text type, you must maintain separate access sequences.

The text types of a text object are grouped together in text determination procedures. You assign a text determination procedure using certain keys, for example, account group customer or sales document type.

Defining and Assigning Text Determination Procedures

You can define text determination procedures for the text object as follows:

  • You select one of the text determination procedures, then you assign text types for the selected text determination procedure. You must set the fields of the text type in text procedure with the relevant values.
  • For text objects in SD documents, you define the access sequences and assign text types to these access sequences. You must set the fields of the access sequence for text type with the relevant values.

When you are editing a customer master record of the assigned account group or a sales document of the assigned document type, the system offers the text types of the corresponding text determination procedure.

Defining Text Determination Procedures

You can define text determination procedures for the text object as follows:

  1. Select an existing text determination procedure.
  2. Identify text types to be considered in the procedure.
  3. (Applicable only to SD documents) Specify an access sequence for each text type.

When adding text IDs into a procedure, their sequence numbers must start with 1, 2, 3, or 4 and contain 1-3 digits. You can delete custom entries for text IDs in a procedure.

You can also change the following settings for each text type:

  • Refer/Duplicate
You can specify whether a text is duplicated or referenced. If you select this option, the text is duplicated. Otherwise, it is referenced.
If a text is duplicated, the system creates an independent copy of the text. You can change either the source or target text without affecting the other.
If a text is referenced, it only exists once in the database. A change in the source text triggers a concurrent change in the target text in the subsequent document. However, the system deletes the reference once you change the target text.
  • FGrp (error group)
Using the error group, you can mark texts as relevant for the incompletion log of the sales documents. If a relevant text of this text type is missing in the sales document, a note is included in the incompletion log.
  • Text is obligatory
You can specify whether a text is mandatory, and whether the system displays the text when it is copied (such as from the customer master record to a sales document).
Note that this setting only applies to Sales Document Header, Sales Document Item, and Delivery Header.

Afterwards you assign the defined text determination procedures as follows:

Text Object   Key
Customer master record   Account group
Sales document header   Sales document type
Sales document item   Item category
Delivery header   Delivery type
Delivery item   Item category
Billing header   Billing type
Billing item   Billing type

NOTE:

Currently you cannot set up your own error groups for the incompletion log for texts in customizing.

In the standard system, error group "50" is defined for texts. The incompletion log takes it into account if the texts are additionally characterized as required in the procedure.

 

You can only include text types in a procedure which you have defined beforehand.

  • The account groups, document types, and item categories must already be defined. They are then proposed to you automatically for assignment.
 
  1. Check to what extent you can use the text determination procedures contained in the standard system.
  2. Change the existing text determination procedures according to your needs or create new ones.
To do this, branch to the text determination procedures for a text object and display the texts in the procedure.
  1. Assign the text determination procedures.
There are two ways to do this:
  • by calling up the text determination procedure assignment

Here, you can carry out the assignment for the selected text determination procedure.
  • by calling up text determination procedure usage

Here, the assignments are displayed for the account groups, the document types and item categories.
 

To initiate transport, select 'Text - Transport' in the initial screen.

Assigning Text Determination Procedures

You can assign text determination procedures for the following text objects:

Text Object   Procedure Assigned To...
Customer master record   Account group
Sales document header   Sales document type
Sales document item   Item category

NOTE: The account groups, document types, and item categories must have been defined.

Quick Reference (Entry Creation, Entry Deletion, and Namespace Requirements)

Object New Entries Allowed? Deletion Allowed for Custom Entries? Namespace Requirements
Procedure No N/A N/A
Text ID in procedure Yes Yes Sequence Number: A number that starts with 1, 2, 3, or 4 and contains 1-3 digits
Access sequence Yes Yes 9000-9999
Text ID in standard access sequence Yes Yes Sequence number: 90-99
Text ID in custom access sequence Yes Yes Sequence number: 0-99






TXBHW - Original Tax Base Amount in Local Currency   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 14671 Date: 20240523 Time: 174924     sap01-206 ( 156 ms )