Advertising:

Texts in master records and documents: Difference between revisions

From SAP Knowledge Base
No edit summary
 
(7 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{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.
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 is the 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)]].
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 ====
== Based on naming convention database table STXL ==


{| class="wikitable"
{| class="wikitable"
Line 44: Line 46:
|-
|-
|Position: info record
|Position: info record
|INFNR(Infosatznummer)
|INFNR(info record id)
|AT
|AT
|EINA
|EINA
|-
|-
!colspan="5"|Stock-/requirements list
!colspan="5"|stock-/requirements list
|-
|-
|Material memo
|Material memo
Line 70: Line 72:
!colspan="5"|production order
!colspan="5"|production order
|-
|-
|Vorgang: Langtext
|operation: longtext
|MANDT + AUFPL + APLZL
|MANDT + AUFPL + APLZL
|AVOT
|AVOT
Line 79: Line 81:
|MATK
|MATK
|AUFK
|AUFK
|With FuBa [[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.
|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
!colspan="5"|material
|-
|-
|Basic data text
|Basic data text
Line 97: Line 99:
!colspan="5"|billing document
!colspan="5"|billing document
|-
|-
|Position: Materialverkaufstext
|Position: material sales text
|VBELN + POSNR
|VBELN + POSNR
|0001
|0001
Line 111: Line 113:
|}
|}


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


Mapping understanding
Mapping understanding

Latest revision as of 17:48, 31 December 2024

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_TEXT or something newer the class CL_MM_PUR_TEXT_FACTORY (Read hint in class).

Based on naming convention database table STXL

Textname Text-ID Text-Object Hints
request for quotation
Position: item text EBELN + EBELP A02 EKPO
Position: material purchase order text EBELN + EBELP A03 EKPO
sales order
Position: salestext VBELN + POSNR 0001 VBBP
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
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
purchase requisition
Position: item text BANF + BNFPO B01 EBAN
Position: material purchase order text BANF + BNFPO B04 EBAN
production order
operation: longtext MANDT + AUFPL + APLZL AVOT AUFK
component: longtext MANDT + RSNUM + RSPOS MATK AUFK With fm 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.
material
Basic data text MATNR GRUN MATERIAL
outline agreement
Position: info purchase text EBELN + EBELP K02 EKPO
billing document
Position: material sales text VBELN + POSNR 0001 VBBP
condition contract
head text GUID Defined in customizing Defined in customizing With fm 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
CDS-View Hints
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.

This is a wiki created in the spare time of a private person working in the SAP ERP area. The aim is to collect knowledge for the own use. The wiki is maintained to the best of knowledge and belief.
All products shown, including in form of screenshots, belong to SAP SE. Their trademarks are, among others: SAP®,ABAP®,SAP Fiori®,SAP HANA®,SAP NetWeaver®,SAP® R/3®,SAP S/4HANA®,SAP S/4HANA® Cloud

Retrieved from "https://unirab.org/index.php?title=Texts_in_master_records_and_documents&oldid=714"