Created by Jerry Wang on Feb 15, 2015

system for Example: AHN/504

process type: OPSM

text determination procedure: OPSM0001

Four types of text object configured:

 

Access sequence: OPSM0001

reference determination FM: CRM_OPPORT_TEXT_DETER_STANDARD

Test

In the runtime, when you create a new Opportunity with type OPSM:

 

you can find totally three texts are determined automatically and displayed in webclient UI:

 

 

How does text determination work

  

the name of reference standard text template for each text object is determined by FM CRM_OPPORT_TEXT_DETER_STANDARD:

 

 

open the name you found in debugger via tcode SO10: CRM_OPPORT_OPSM0001_A002

 

The content of the text template is just exactly what you have seen in webclient UI:

 

The reason why we have configured four text objects in customizing, but we only saw three notes in webclient ui: There is no result for text determination against text object O003:

 

since there is no standard template maintained for this text object: