Ansicht
Dokumentation
BBP_TEXT_SCHEMA - Define Text Types
CL_GUI_FRONTEND_SERVICES - Frontend Services SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3upThis documentation is copyright by SAP AG.
In this IMG activity you define text types. Once you have defined them, the text types are bundled and assigned to the transaction types.
The standard system contains the following text types:
| CHT1 | Customer text at header 1 | ||
| CHT2 | Customer text at header 2 | ||
| CIT1 | Customer text at item 1 | ||
| CIT2 | Customer text at item 2 | ||
| DTXT | Participant conditions | ||
| HREJ | Rejection text at header | ||
| HTXT | Header long text | ||
| IREJ | Rejection text at item | ||
| ITXT | Item long text | ||
| NOTA | Note from bidder | ||
| NOTE | Note | ||
| NOTM | Approval note | ||
| REMA | Comment from bidder | ||
| REMB | Comment for bidder | ||
| RREJ | Rejection reason | ||
| UNKN | Unknown |
To define text types, proceed as follows:
- Select the text object BBP_PD and click Text Type.
- Click New Entries and specify the ID and meaning.
- Save your entries.
- Then, assign the text types to text schemas. You do this in the IMG activity Define Text Schemas.
General Data in Customer Master SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up
This documentation is copyright by SAP AG.
Length: 3146 Date: 20240607 Time: 130110 sap01-206 ( 19 ms )
