View source for Texts in master records and documents

{{Template:MetaDesc|A list of texts and notes for master records and documents at header and item level. Exact information on how parameters for coding must be filled out.}}
[[category:forms]]
For some requirements, texts from master records or documents are required. For example to put texts in forms or from one business process to another business process.

Very famous to get texts is function module [[Read_texts_and_notes_with_function_module_READ_TEXT|READ_TEXT]] or something newer the class [[Read_texts_and_notes_with_classic_class_CL_MM_PUR_TEXT_FACTORY|CL_MM_PUR_TEXT_FACTORY (Read hint in class)]].

== Based on naming convention database table STXL ==

{| class="wikitable"
|
|'''Textname'''
|'''Text-ID'''
|'''Text-Object'''
|'''Hints'''
|-
!colspan="5"|request for quotation
|-
|Position: item text
|EBELN + EBELP
|A02
|EKPO
|-
|Position: material purchase order text
|EBELN + EBELP
|A03
|EKPO
|-
!colspan="5"|sales order
|-
|Position: salestext
|VBELN + POSNR
|0001
|VBBP
|-
!colspan="5"|purchase order
|-
|Position: item text
|EBELN + EBELP
|F01
|EKPO
|-
|Position: info purchase order text
|EBELN + EBELP
|F02
|EKPO
|-
|Position: info record
|INFNR(info record id)
|AT
|EINA
|-
!colspan="5"|stock-/requirements list
|-
|Material memo
|MATNR + WERKS
|MDTXT
|LTXT
|Text name has a total of 45 characters. 40 characters of the material 1 space and 4 characters of the plant. If the material number does not have 40 characters, it must be filled with spaces
|-
!colspan="5"|purchase requisition
|-
|Position: item text
|BANF + BNFPO
|B01
|EBAN
|-
|Position: material purchase order text
|BANF + BNFPO
|B04
|EBAN
|-
!colspan="5"|production order
|-
|operation: longtext
|MANDT + AUFPL + APLZL
|AVOT
|AUFK
|-
|component: longtext
|MANDT + RSNUM + RSPOS
|MATK
|AUFK
|With fm [[Read_texts_and_notes_with_function_module_READ_TEXT|READ_TEXT]] the long text can only be read if the long text has more than one line. The first line is written into the 'BOM item text (line 1) [RESB-POTX1]' field.
|-
!colspan="5"|material
|-
|Basic data text
|MATNR
|GRUN
|MATERIAL
|-
!colspan="5"|outline agreement
|-
|Position: info purchase text
|EBELN + EBELP
|K02
|EKPO
|-
!colspan="5"|billing document
|-
|Position: material sales text
|VBELN + POSNR
|0001
|VBBP
|-
!colspan="5"|condition contract
|-
|head text
|GUID
|Defined in customizing
|Defined in customizing
|With fm [[Read_texts_and_notes_with_function_module_READ_TEXT|READ_TEXT]] the GUID must be taken as the name via the table WCOCOH / I_ConditionContract, see table an example entry in database table STXL.
|}

== Based on naming convention from CDS-Views ==

Mapping understanding
* ArchObjectNumber = text_objectid / text_name
* DocumentText = text_id
* TechnicalObjectType = text_object
* language = spras

{| class="wikitable"
|
|'''CDS-View'''
|'''Hints'''
|-
!colspan="3"|purchase requisition
|-
|header notes
|C_PurchaseReqnHeaderNotes
|
|-
|item notes
|C_PurchaseReqnItemText
|For automatically copied texts that end up in purchase requisition, the text is only saved with the UUID. The same applies if a text has been edited and is still in draft.
|}