As mentioned before, a SAP script text consists of a text header and the text lines. If, according to the storage mode, the corresponding text object is stored in a text file, these two text components are stored in separate tables.To avoid inconsistencies, use only the corresponding SAPscript function modules to read texts from or write them to text files.The system stores only those texts in the text file, that have the values 'D' (direct) or 'V' (update task) specified as storage mode.

STXH: Store text header

The text header is stored in the transparent table STXH. This table contains both the text headers of SAPscript texts and of texts with other formats. When reading the table, the system copies this information into the corresponding fields of structure THEAD, which is the basic structure of the internal work area of the text header.

STXL: Store text lines in ITF format
Table STXL stores the text lines of a text in ITF format. This is a non-transparent table, which can be accessed

using IMPORT FROM DATABASE / EXPORT TO DATABASE. The text lines are stored in compressed form.

STXB: Store text lines in other formats
If in field TDTEXTTYPE of the text header a text format appears, the text module has a non-SAPscript format. The lines of such texts are stored in table STXB. This table can also store non-representable characters (HEX codes < style=""> Standard text. Theà Word processing àtransaction, choose Tools authorization object is S_SCRP_TEXT, with the fields TEXTNAME Name of the standard text TEXTID ID of the standard text LANGUAGE Language key of the standard text ACTVT Activity For TEXTNAME, TEXTID, and LANGUAGE, you can enter single values, intervals, and generic entries, if allowed as authorization values. For the activity, SAPscript distinguishes between display and change only. The authorization for changing a standard text does not automatically imply the authorization for displaying it.

If you want a user to both display and change a text, you must allocate authorizations for both activities. SAPscript executes a create/change or display authorization check when the transaction SO10 is called. To include a standard text into another Standard... in the editor, the user needs onlyà Text àusing Include display authorization.

The same applies if the user includes standard texts using the control statement INCLUDE. The system executes the check when processing the text module for output. If the user has no authorization, the system ignores the INCLUDE statement.

If an INCLUDE statement in the layout set specifies a standard text to be included into the output, the system does not execute a check. To check whether a user has authorizations for standard texts, use the function module CHECK_TEXT_AUTHORITY. Authorization checks for other texts For texts allocated to an object other than TEXT, SAPscript does not execute authorization checks.

Since these texts are usually allocated to business application objects, SAPscript assumes that the application program checks whether the user is authorized to use the object. If a user is authorized to display a material, this implies the authorization to display the texts allocated to this material. If you want these texts to be independent of the object authorization, you must define new authorization objects for the texts and include an appropriate authorization check call into the application program.

STORE TEXTS Modifications to texts should be executed in the same ways as modifications to the application object to which the text is allocated via the text object. This means that text modifications must be stored in the update task whenever the application object uses the update task to store data. You use the storage mode to determine how a text is stored.

You can set the storage mode for each text object used to allocate texts to application objects. The storage modes used by SAPscript are stored in table TTXOB:

• D = Store changes directly: The system immediately executes all SAPscript functions that change text files

• V = Store changes in update task: The system saves changes to text modules internally when the corresponding function is called and only writes them to the text file in the update task, together with changes to the application object.

All other storage modes are not supported by SAPscript. Those texts are not stored in the text file. If you want to store a text that uses such a storage mode using functions from the SAPscript programming interface, the corresponding function module triggers the exception SAVEMODE and stops. Store texts directly Store texts in update task Rename texts STORE TEXTS DIRECTLY If a text has the attribute 'direct storage', all changes are written to the text database as soon as SAPscript calls the corresponding function modules (SAVE_TEXT, DELETE_TEXT, ...


CRM Middle ware System Architecture
CRM Middle ware Enhancement

No comments :

Post a Comment