Convert SAPscript into Smart Form

Digg This!     StumbleUpon     Del.icio.us

RELATED CONTENT SAPscript and Smart Forms Modifying standard SAP Smart Forms for purchase orders How to solve output alignment problems with SAPscript printing Using SAP Smart Forms to change layout of Plant Maintenance How to fix Smart Forms printing double purchase orders Deriving the name of a Smart Style from a Smart Form Fixing a common OPEN_FORM and START_FORM error in SAPscript Avoid printing out blank address lines in SAP Smart Forms Setting soft breakpoints in ABAP that reside in Smart Forms Printing specifics on the last page of a Smart Form Unwelcome change in Smart Forms icons SAPscript and Smart Forms Modifying standard SAP Smart Forms for purchase orders How to solve output alignment problems with SAPscript printing Using SAP Smart Forms to change layout of Plant Maintenance How to fix Smart Forms printing double purchase orders Deriving the name of a Smart Style from a Smart Form SAP administration information for a Basis interview Transferring R/3 Admin skills to SAP NetWeaver Easier maintenance of output types, procedures, conditions, etc. Avoid printing out blank address lines in SAP Smart Forms Setting soft breakpoints in ABAP that reside in Smart Forms SAPscript and Smart Forms Research

RELATED RESOURCES 2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems Search Bitpipe.com for the latest white papers and business webcasts Whatis.com, the online computer dictionary

You have come up with an elegant approach for dynamic handling of language-specific output in SAPscript. Unfortunately, as you probably have found already, this particular approach does not work in Smart Forms.

Within a Smart Form, you can set up an 'Include text' node to access standard texts as used in SAPscript. In addition, you can specify dynamically the language to retrieve (via a variable in the language parameter). However, any commands within these standard texts -- such as DEFINE -- are ignored.

Thus, I would recommend simplifying your approach. Based on your example above, since you can no longer assign the words 'To be priced' and 'A prÉmarquer' to variables within standard texts, why not put the words directly into these standard texts (or into text modules) instead and invoke them solely when you wish to produce output? As an alternative -- if you need tighter control over how these words appear or wish to minimize external text retrieval -- insert a language-dependent CASE statement assigning the words to variables within the Smart Form itself (in the Initialization section or a Program node).

Either approach will allow you to rely upon a single Smart Form for your multi-language output. If there are many, many such texts you may wish to reevaluate whether the benefits outweigh the disadvantages of having a single form for multi-language output.