Smartforms XML Format

SAP AG
SAP BC-XSF
Vladislav Bezrukov
Andreas Deutesfeld
Dr.Rainer Hoch
SAP Smart Forms XSF

XML Output for Smart Forms
Version 1.11.2
August 17th, 2000
Please visit our web page at www.sap.com/csp/scenarios

for examples and the latest version of this document.
SAP AG
SAP BC-XSF
Copyright 2000 SAP AG. All rights reserved.

No part of this document may be reproduced or transmitted in any form or for any purpose without
the express permission of SAP AG. The information contained herein may be changed without prior
notice.
Some software products marketed by SAP AG and its distributors contain proprietary software
components of other software vendors.
Microsoft, WINDOWS and EXCEL and SQL-Server are registered trademarks of Microsoft
Corporation.
IBM, OS/2, DB2/6000 and AIX are a registered trademark of IBM Corporation.
OSF/Motif is a registered trademark of Open Software Foundation.
ORACLE is a registered trademark of ORACLE Corporation, California, USA.
INFORMIX-OnLine IRU6$3 is a registered trademark of Informix Software Incorporated.
UNIX is a registered trademark of SCO Santa Cruz Operation.
ADABAS is a registered trademark of Software AG.
SAP, R/2, R/3, RIVA, ABAP/4, SAPoffice, SAPmail, SAPaccess, SAP-EDI,
InterSAP, SAP Business Workflow, are registered trademarks of SAP AG.
All rights reserved.
SAP AG
SAP BC-XSF
;0/IRU6$36PDUW)RUPV&RQFHSWDQG8VH
3UHUHTXLVLWHVDQG&RQGLWLRQVRI8VHRIWKH;6)
;6)3URJUDP,QWHUIDFH

(QDEOLQJ;6)2XWSXWDW5XQWLPH

(QDEOLQJ;6)RXWSXWVWDWLFDOO\

,QWHUDFWLRQ$SSOLFDWLRQ3URJUDP6$36PDUW)RUPV27)

,QWHUDFWLRQ$SSOLFDWLRQ3URJUDP6$36PDUW)RUPV;6)
6$36PDUW)RUPV;6)2XWSXW6WUHDP

(OHPHQWKHDGHU!
4.1.1
4.1.2
4.1.3
4.1.4
4.1.5

Header Element <general>

Header Element <page>
Header Element <archive>
Header Element <mail>
Header Element <telefax>
8
9
10
11
11
(OHPHQWGDWD!
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.2.6
4.2.7
4.2.8
4.2.9
4.2.10
4.2.11
4.2.12
4.2.13
4.2.14

Element <window>
Element <graphics>
Element <address>
Element <section>
Element <new-page>
Element <print-control>
Text elements
Element <p> (paragraph format)
Element <chr> (character format)
Element <sym> (field)
Element <url>
Element <new-line>
Element <tab> (tabstop)
Element <table>
11
12
12
13
13
13
13
14
15
15
15
15
15
16

6W\OHLQIRUPDWLRQLQWKH;6)6WUHDP

(VFDSHGFKDUDFWHUVDVRI5HO

/DQJXDJHDQGFRGHSDJHVXSSRUW

6HWXS2XWSXW'HYLFHIRU;6)6SRRO0RGH

$SSHQGL[$;6)'RFXPHQW7\SH'HILQLWLRQ;6)'7'

$SSHQGL[%6DPSOHRI$%$33URJUDP*HQHUDWLQJ;6)2XWSXW6WUHDP

$SSHQGL[&6DPSOHRI;6)2XWSXW6WUHDP

$SSHQGL['*ORVVDU\DQG$EEUHYLDWLRQV

5HIHUHQFHV

SAP AG

SAP BC-XSF
;0/IRU6$36PDUW)RUPV&RQFHSWDQG8VH
External text management systems can be connected via the SAP Smart Forms XML Interface
(XSF). XSF is an XML based language. This interface contains all R/3 forms data, but no layout
information such as font or page size. Document data is formatted and managed either by the
external system outside R/3 or by an R/3 application program. Mail processing is an important
application that uses this procedure: the external system sorts the interface document data and
passes on the documents appropriately.
XSF is a certified interface which provides a high-quality external system connection, however, at
the price of losing some R/3 System integration. It is, for example, not possible to find out from
within an R/3 application whether external printing and sending of correspondence was successful.
Changes to standard forms also require extra effort because both internal and external forms must
be changed. The external tool is not integrated into the ABAP Development Workbench, so ABAP
Dictionary field information (type, output length, etc.) is not available.
XSF output is a successor of RDI output >5',@. RDI output is implemented in SAPscript Forms,
XSF output is part of the SAP Smart Forms Development Project.

3UHUHTXLVLWHVDQG&RQGLWLRQVRI8VHRIWKH;6)
5&XVWRPL]LQJIRU3ULQWLQJYLD;6)
An R/3 System form can be flagged for external printing. If a form is not explicitly
flagged, application-dependent customizing settings apply (if available). For details see
section 3.
([WHUQDO3ULQWLQJ2XWSXW'HYLFH
At least one output device must be set up for the external printing device type (PLAIN)
delivered by SAP. For details refer to section 5 or to the online documentation (spool
administration).
'HILQLWLRQRI([WHUQDO)RUPVDQG$VVLJQPHQWWR5)RUPV
The external text system must contain a form definition for each R/3 Smart Form that is
to be printed externally. In particular, appropriate variables must be defined.
([WHUQDO;6)5HDG3URJUDP
The external program reads the XSF stream according to the XSF DTD specification (see
Appendix A) and then formats and eventually prints or displays the documents.
;6)'DWD6WDWXV&RQWURO
The current print status of all documents to be printed externally should be displayable.
An overview of unsuccessful print requests is also required >%&;20@.
2SWLRQDO$UFKLYLQJ
The external system should be able to send the printout to an archive if required. See also
.
>$5/,1.@
SAP AG

SAP BC-XSF
;6)3URJUDP,QWHUIDFH
XSF output can be activated:
at runtime via the parameter structure OUTPUT_OPTIONS
statically by setting the flag XSF Output active in the Smart Form

(QDEOLQJ;6)2XWSXWDW5XQWLPH
The fields of parameter OUTPUT_OPTIONS (DDIC structure SSFCOMPOP), which can be set at
runtime, are listed in Table 1. This parameter is passed to the generated Smart Form function
module. See also Appendix B for the sample program.
Table 1
Field
Description
;6)&02'(
Determines whether the runtime settings (XSFCMODE=X) or static

settings (XSFCMODE=VSDFH) from the Smart Form header should be
taken.
1RWH the flag XSFCMODE itself neither enables nor disables XSF output.
;6)
Controls whether XSF (XSF=X) or OTF (XSF=space) output should be

produced. XSF output and OTF output cannot be combined.
;6)28702'(
Specifies the output type. At present the values A (application) and

S(spool) can be specified.
;6)28702'( $ : the XSF output stream is passed directly to the
calling application as an internal table of ABAP type STRING. This table
is part of parameter JOB_OUTPUT_INFO (ABAP DDIC structure
SSFCRESCL) and is stored under the name JOB_OUTPUT_INFOXSFDATA (ABAP DDIC table type TSFXRDI).
;6)28702'( 6 : the generated data stream is redirected to the SAP
spool system in form of a spool request. The ID of the generated spool
request can be found in the export parameter JOB_OUTPUT_INFOSPOOLIDS.
;6)287'(9
Determines the output spool device (for example, printer name, usually of
type PLAIN). This field makes sense only when spool output is enabled
(XSFOUTMODE=S).

(QDEOLQJ;6)2XWSXW6WDWLFDOO\
It is possible to enable XSF output statically on the'Output options' tab of the form in the Form
Builder:
The flag XSF Output active has the same meaning as field XSF in section 3.1.
The field Output mode has the same meaning as field XSFOUTMODE in section 3.1.
The field Output device has the same meaning as field XSFOUTDEV in section 3.1.
The static setting can be overwritten at runtime using parameter OUTPUT_OPTIONSXSFCMODE=X (see section 3.1).
SAP AG

SAP BC-XSF
,QWHUDFWLRQ$SSOLFDWLRQ3URJUDP6$36PDUW)RUPV27)
When using OTF (Output Text Format) as output format, the output component (Spool, Archive,
SAPconnect, etc.) receives a description of the Smart Form , which includes formatting information.

,QWHUDFWLRQ$SSOLFDWLRQ3URJUDP6$36PDUW)RUPV;6)
When using XSF (XML output for SAP Smart Forms) as output format, no formatting information
is passed. XSF can be redirected to the spool or returned to the calling R/3 application.
SAP AG

SAP BC-XSF
6$36PDUW)RUPV;6)2XWSXW6WUHDP
This section describes the XSF elements and their relationships. XSF is an XML based
language>;0/@. The XSF output of a Smart Form represents the structure of the Smart Form at
runtime mixed with the data from an application. The XSF stream represents the final state of the
Smart Form. This means that, in particular, all conditional statements are resolved and the field
substitution is done. Thus the XSF output stream cannot be considered as a complete XML
container of the form. It is a result of form processing with particular application data.
SAP reserves the right to embed this stream into other XML streams or pack it into an SAP-defined
XML envelope. The specification of these streams goes beyond the scope of this document. The
formal specification of XSF is defined in the XSF DTD (Appendix A). The current version of the
DTD is 1.11.
As with every XML stream, the XSF stream begins with an XML tag, e.g.:
<?xml version="1.0" encoding="iso-8859-1" ?>
and continues with root element <smartxsf> to encapsulate one form. This root element contains
control and data parts (elements <header> and <data> respectively) as direct subnodes to
describe the contents of the form. In case of multiple forms within one spool job, the following XSF
output is appended to the last one. This means that several XML tags can occur within one XSF
stream, which is the only variation from the XML standard.
The chosen model of representing information is windows-oriented, not page-oriented. This means
that, in particular, the main window is unique in the stream (data part) and may continue over
several pages. To which pages the other windows belong, is determined by a reference mechanism
(see also section 4.1.2). The pages actually processed at runtime are listed in the header part and
have unique identifiers. The windows actually processed (data part) refer to those pages, so that it is
always possible to figure out which page a window belongs to.

(OHPHQWKHDGHU!
Element <header> contains control information, which is not supposed to be printed. There may
be just one header element in the XSF stream.
The header comprises:
general information of a form (element <general>)
list of processed pages (elements <page>)
archive information (element <archive>), optional (see also >$5/,1.@)
mailing attributes (element <mail>), optional (see also >%&,@)
telefax attributes (element <telefax>), optional (see also >6$3&211(&7@ and
>6$3&200@)
SAP AG

SAP BC-XSF
+HDGHU(OHPHQWJHQHUDO!
Element <general> comprises the information about XSF version, form name and language,
output device, preview and print settings, etc. The elements XSF version (<version>), form
name (<form>), form language (<language>), device name (<device>) and device type
(<device-type>) are obligatory, all other elements are optional. For the complete list of
supported elements refer to Table 2 (sorted by element name).
Table 2
Element
Optio
ABAP
nal
Reference Type
Description
GHYLFH
TDDEVICE
Output device (for example, PRINTER,

MAIL, FAX)
GHYLFHW\SH
RSPOPTYPE
Device type (for example, HPLJ5)
IRUP
TDSFNAME
Form name
ODQJXDJH
SPRAS
Form language
RSPOPNAME
Printer name (initial if DEVICE is not

PRINTER)
WGDXWKRULW\
SYPRBER
Print: authorization
WGFRSLHV
TDCOPIES
Number of identical copies
WGFRYHU
SYPRSAP
Print: SAP cover page
WGFRYWLWOH
SYPRTXT
Print parameters: text for cover page
WGGDWDVHW
RSPO0NAME
Spool request: Name
WGGHOHWH
SYPRREL
Print parameters: delete after printing
WGGLYLVLRQ
SYPRABT
Print parameters: department on cover

page
WGLH[LW
TDIMMEXIT
Immediately exit after printing/faxing

from print preview
WGLPPHG
SYPRIMM
Print parameters: print immediately
WGOLIHWLPH
SYPEXPI
Print parameters: spool retention period
WGQHZLG
SYPRNEW
Print parameters: new spool request
RXWSXW
GHYLFH
The output device name in the XSF stream comes from the application program, from customizing
or from user settings and in general does not correspond to the output device name in the Smart
Form header.
8
SAP AG
SAP BC-XSF
Optio
ABAP
nal
Reference Type
WGQRDUFK
TDNOARCH
No changes by user in archiving mode
WGQRSUHY
TDNOPREV
No print preview
7GQRSULQW
TDNOPRINT
No printing from print preview
7GSDJHVHOHFW
TDPAGESLCT
Pages selected for printing
7GUHFHLYHU
SYPRREC
Print parameters: recipient
7GVXIIL[
RSPO1NAME
Spool request: Suffix 1
7GVXIIL[
RSPO2NAME
Spool request: Suffix 2
7GWLWOH
TDTITLE
Title in dialog box
XSF Version
Element
9HUVLRQ

Description
+HDGHU(OHPHQWSDJH!
Element <page> is used to identify the pages in the XSF stream. Each page element has two
attributes: name and ID. The attribute name is the name of the page layout that comes from the
Smart Form. The attribute ID is generated at runtime to distinguish between pages with the same
layout.
A Smart Form contains a page FIRST with a window MAIN. In the flow logic of that
window a <new-page> command is defined. This command points to the same page FIRST. At
runtime the data is displayed on page FIRST until the <new-page> command occurs. At that
point, the current page is completed with other auxiliary windows on the page. In case of XSF
output the element <page name=FIRST id=001/> is generated. The next page to be
processed has the same layout (due to the <new-page> command pointing again to page
FIRST). To distinguish between such pages, the next page gets a unique identifier and the element
<page name=FIRST id=002/> will be generated.
([DPSOH
The <window> elements refer to the <page> elements (see section 4.2.1-4.2.3) so that it is
possible to reconstruct a page content by collecting all windows that refer to that page. The only
exception is the main window. In each form, there can be only one main window. The main window
refers to the page on which it occurs for the first time. Since the XSF stream contains no formatting
information that can influence the window size, the implicit page breaks (when the main window is
full) do not appear in the XSF stream. In contrast, the explicit page breaks triggered by a NEWPAGE command are included in the flow of the MAIN window as a <new-page> element (see
section 4.2.5).
SAP AG

SAP BC-XSF
+HDGHU(OHPHQWDUFKLYH!
Element <archive> contains information (as attributes to the element) on archiving as described
in Table 3. Attributes with initial values or default values (see XSF DTD in Appendix A) are
omitted in the output stream (this rule applies to all XSF elements).
Table 3
ABAP
Attribute
Reference Type
Description
'DWH
SAEABLDATE
SAP ArchiveLink: archiving date
'RFW\SH
SAEDOKTYP
SAP ArchiveLink: document class
)RUPDW
SAEFORM
SAP ArchiveLink: output format
,QIR
SAEINFO
SAP ArchiveLink: info field
,QWHUIDFH
SAEAAPROG
SAP ArchiveLink: name of

communication connection component
/RJ
SAEPROTOKO
SAP ArchiveLink: storage connection

protocol
0RGH
SYARMOD
Print: archiving mode
PRGHPRGLI\HQDEOHG
Changes by user allowed in archiving

mode (YES/NO)
REMHFW
SAEOBJART
Document type
REMW\SH
SAEANWDID
SAP ArchiveLink: object type of

business object
SDWK
SAEARCPATH
SAP ArchiveLink: standard archive

path
UHSRUW
SAEREPORT
SAP ArchiveLink: report name
USFKRVW
SAERPCHOST
SAP ArchiveLink: RPC host
USFVHUYLFH
SAERPCSERV
SAP ArchiveLink: RPC service / RFC

destination
WDUJHWV\VWHP
SAEARCHIV
SAP ArchiveLink: target storage

system
WH[W
SAETEXT
SAP ArchiveLink: text information

field
XVHU
SAEUSER
Data element for user
YHUVLRQ
SAEVERSION
SAP ArchiveLink: version number
10
SAP AG

SAP BC-XSF
+HDGHU(OHPHQWPDLO!
Mail information is only written if the mail device is used. There are two elements permitted within
the MAIL element for every document: mail sender (element <sender>), mail recipient (element
<recipient>). These elements do not contain an e-mail address. They contain R/3 internal
information (SAP Smart Forms/SAPconnect) that might be helpful for addressing.

+HDGHU(OHPHQWWHOHID[!
The telefax information is only written if the telefax device is used. It provides amongst others the
fax number and country.

(OHPHQWGDWD!
Element <data> contains data coming from the application program. The data is structured at
runtime by means of embedding it into the specific Smart Forms elements.
The default style of the Smart Form is defined in the attributes style and variant (see section
4.3). This default style is to be applied to a subelement if no other style is defined.
The valid subelements of element <data> are <window>, <graphics>, and <address>
(sections 4.2.1, 4.2.2 , 4.2.3 respectively).

(OHPHQWZLQGRZ!
Element <window> describes a logical unit of structured information.

Each window refers to a certain page via the attributes page and page-id (see section 4.1.2 for
detailed description). There are two types of windows: main and auxiliary. The main window is
unique throughout the form and can spread over several pages. Auxiliary windows are located
completely on a certain page. The attribute type indicates whether the window is of type main
(type=MAIN). The value type=AUX indicates an auxiliary window and is optional.
Element <window> may contain elements such as <graphics>, <address>, <section>,
<text>, <include-text>, <new-page> (reasonable in main window only), <printcontrol>, and <table>. Windows cannot be nested.
11
SAP AG

SAP BC-XSF
(OHPHQWJUDSKLFV!
Element <graphics> can occur both as a separate window and as part of a regular window
(main/auxiliary).
If this element represents a separate window the attributes page and page-id refer to the
appropriate page. The attributes of element <graphics> are listed in Table 4.
Table 4
Attribute
Description
,G
R/3 Dictionary key field: graphic Id (BMAP)
1DPH
Name of the graphic object in the Smart Form
2EMHFW
R/3 Dictionary key field: object type (GRAPHICS)
2EMQDPH
R/3 Dictionary key field: graphic name
3DJH
Page name (applied for GRAPHICS as a window)
SDJHLG
Page ID (applied for GRAPHICS as a window)
5HVROXWLRQ
Graphic resolution
7\SH
R/3 Dictionary key field: color (BCOL) / black-and-white

(BMON)
Element <graphics> is an empty element.

(OHPHQWDGGUHVV!
Element <address> can occur both as a separate window and as part of a regular window
(main/auxiliary).
If this element represents a separate window the attributes page and page-id refer to the
appropriate page. The attributes of element <address> are listed in Table 5.
Table 5
Attribute
Description
$GGUQXPEHU
R/3 Dictionary key field: Company number in the SAP Central

Address Management System (CAM)
1DPH
Name of the address object in the Smart Form
3DJH
Page name (applied for ADDRESS as a window)
SDJHLG
Page ID (applied for ADDRESS as a window)
3HUVQXPEHU
R/3 Dictionary key field: Personal number in the SAP CAM
Element <address> contains only element <text> with the textual information of the resolved
address.
12
SAP AG

SAP BC-XSF
(OHPHQWVHFWLRQ!
Element <section> is used to group other elements.

The element has the attributes name, style, and variant (for the attributes style and
variant see Section 4.3).
Element <section> may contain header (<shead>, optional), body (<sbody>), and
footer(<sfoot>, optional) elements. Sections can be nested.

(OHPHQWVVKHDG!VERG\!VIRRW!
These elements can contain graphics (element <graphics>), addresses (element <address>),
other sections (element <section>), text elements (elements <text> and <include-text>),
page breaks (element <new-page>), and print control elements (element <print-control>).
The section body element (<sbody>) can, in addition, contain tables (element <table>).

(OHPHQWQHZSDJH!
Element <new-page> is used for explicit page breaks within a Smart Form. This element may
occur only within the main window. In Smart Forms, there are explicit and implicit page breaks. An
implicit page break is issued at runtime when the main window on the current page is full and there
are more data to be printed. Since the implicit page break depends on the formatting information
(for example, font size), there are QRLPSOLFLWSDJHEUHDNVin the XSF stream. It is the task of the
external application that process the XSF stream to set the implicit page break in the form properly.
Element <new-page> (attributes page and page-id) refers to the page that must be processed
when the processing of the current one is completed.
Element <new-page> is an empty element.

(OHPHQWSULQWFRQWURO!
Element <print-control> contains printer escape sequences >6322/(6&@.

7H[W(OHPHQWV
Text elements contain the textual information that can be further structured (with paragraphs,
characters, logical tabstops, line breaks, etc.) At present, there are two types of text elements:
embedded texts (element <text>) and external texts (element <include-text>, see
>,1&/8'(7(;7@). Both elements contain the structured text. The only difference between them
are the reference attributes for external texts.
For the Text Modules (see >7(;702'8/(@ there will be a new element. For the time being the
text modules are presented as <text> elements.

(OHPHQWWH[W!
The attributes of element <text> are text node name (attribute name), current style (attribute
style) and style variant (attribute variant). See section 4.3 for more details on styles. As of R/3
Release 5.0 there is a new attribute lang that defines the text language.
Element <text> can contain a set of paragraphs (element <p>) that can be further structured (see
section 4.2.8 for details on paragraphs).
13
SAP AG

SAP BC-XSF
(OHPHQWLQFOXGHWH[W!
The attributes of element <include-text> are text node name (attribute name), current style
(attribute style) and style variant (attribute variant; see section 4.3 for more details on styles),
and reference attributes (objname, id, object, and language). The reference attributes
comprise the unique R/3 key in the standard-text database. The attributes of element <includetext> are listed in Table 6.
Table 6
Attribute
Description
LG
R/3 Dictionary key field: Text IDd
ODQJXDJH
R/3 Dictionary key field: Text language
QDPH
Name of the textual object in the Smart Form
REMHFW
R/3 Dictionary key field: Object
REMQDPH
R/3 Dictionary key field: Text name
VW\OH
Style name
YDULDQW
Style variant
Element <include-text> can contain a set of paragraphs (element <p>) that can be further
structured (see section 4.2.8 for details on paragraphs). For details on SAPscript include texts see
>,1&/8'(7(;7@.

(OHPHQWS!3DUDJUDSK)RUPDW
Element <p> describes a logical text paragraph.

The element is always named (attribute name) and can be found in the definition of the active style
(in R/3). Another attribute of element <p> indicates the current append mode of the paragraph
(attribute appmode). It determines how the current paragraph should be appended to the previous
one. This attribute can have three possible values:
new-paragraph (default value) appends the current paragraph as an independent

paragraph, thus inheriting all attributes from the paragraph definition in the style.
new-line merges the current paragraph with the previous one using a line break as a
conjuctor.
append fully merges the current paragraph with the previous one. No line break is
inserted between these paragraphs.
Element <p> can contain plain text, fields (element <sym>), character formats (element <chr>),
tabstops (element <tab>), URLs (<url>), and line breaks (element <new-line>). Paragraphs
cannot be nested.
14
SAP AG

SAP BC-XSF
(OHPHQWFKU!&KDUDFWHU)RUPDW
Element <chr> describes a logical unit of text within a paragraph format (element <p>). The
attribute name contains the name of the character format and can be found in the definition of the
currently active style (in R/3 System).
Element <chr> can contain plain text, fields (element <sym>), tabstops (element <tab>), line
breaks (element <new-line>), and other characters (element <chr>).
(OHPHQWV\P!)LHOG
Element <sym> describes the data fields of Smart Forms. A field in Smart Forms is a variable that
is substituted at runtime (field substitution). For details on the Smart Forms fields see [FIELD].
The attribute name contains the name of the field. The value of the field is stored as element
content.
Example:
<sym name=TOTAL>1000</sym> <sym name=TOTAL_CURRENCY>EUR</sym>
(OHPHQWXUO!
Element <url> is used for Universal Resource Locator (URL) specification. The URL address is
defined as element content, not as an attribute(see example 4.2.11-1). This can be subject to changes
in future releases. The element content can be further structured (see example 4.2.11-2). The
external application program must be able to extract the URL address from the structured element
content.
Example 4.2.11-1 of a simple URL element:
<url>www.mySAP.com</url>
Example 4.2.11-2 of a structured URL element:
<url>www.<chr name=I>mySAP</chr>.com</url>
(OHPHQWQHZOLQH!
Element <new-line> is used for explicit line breaks in the text element. It has the same effect as
HTML element <BR>. The absence of a line break in the text means that the text is splitted into
lines by the processing application (for example, browser). In contrast does the presence of a line
break mean that the text is splitted rigidly at the specified point.
Element <new-line> is an empty element.
(OHPHQWWDE!7DEVWRS
Element <tab> splits a text line into logical pieces. The formatting attributes corresponding to the
current tabstop can be found in the current paragaraph of the currently active style.
Element <tab> is an empty element.
15
SAP AG
SAP BC-XSF
(OHPHQWWDEOH!
Element <table> defines a table structure. The table concept of the Smart Forms is based on the
row-oriented model. This means, in particular, that any row can have a different layout and number
of cells. The only restriction is the width of the table (which has no meaning in the pure XSF output,
since the formatting data is not supplied) all table rows must have the same width.
Element <table> has the following attributes: table name (attribute name), frame pattern
(attribute pattern), and style information (attributes style and variant). The frame pattern is
a number that identifies the used pattern in the internal list of patterns. This pattern defines which
rows and/or cells should be framed (bordered). The patterns cover the framing of first/last row and
first/last column as well as the framing of the entire table or framing of all cells/all rows/all columns
in the table.
A table structure comprises header (element <thead>, optional), body (element <tbody>,
obligatory), and footer (element <tfoot>, optional).
(OHPHQWVWKHDG!7DEOH+HDGHUWERG\!7DEOH%RG\WIRRW!7DEOH
)RRWHU
The elements <thead>, <tbody>, and <tfoot> define table header, body, and footer,
respectively. The elements <thead> and <tfoot> are optional (can be disabled in the Smart
Form).
The elements comprise table rows (element <tr>) or grouped table rows (element <section>).
(OHPHQWWU!7DEOH5RZ
Element <tr> defines a table row.

Table 7
Attribute
Description
5RZ
Current row number (only for Templates)
OW\SH
Assigned layout
A table row comprises table cells (element <tc>).

(OHPHQWWF!7DEOH&HOO
Element <tc> defines a table cell.

Table 8
Attribute
&HOO
Description
Cell number
The application program should be able to sort the cells within a table row according to attribute
cell and fill the missing cells in the table.
16
SAP AG

SAP BC-XSF
6W\OH,QIRUPDWLRQLQWKH;6)6WUHDP
The attributes style and variant contain the name and variant of the current Smart Style. Although
the information how to format a Smart Form is not provided in the XSF stream, the appropriate
XSF elements have a pointer to the style. The information about the current style formats is located
in the attributes style and variant and in the paragraph and character elements (elements <p> and
<chr>, attribute name). This information can be extracted by third-party tools in order to define their
own formats to these elements. In future releases, SAP will provide the CSS [CSS] and XSLT
[XSLT] streams as an extension of the XSF stream, which will contain the current formatting data.

(VFDSHG&KDUDFWHUVDVRI5HO
Since the ampersand character (&) and the left angle bracket (<) are used as XML markup
delimiters (see XML 1.0 specification, section 2.4 >;0/@) they and some other characters are
escaped in the XSF stream as of R/3 Release 5.0. Before Release 5.0, no characters are escaped in
the XSF stream. For the complete list of escaped entities in XSF see Table 9.
Table 9
Entity

Escaped sequence
&
&
<
>
/DQJXDJHDQG&RGHSDJH6XSSRUW
The header element <language> defines the language of the Smart Form according to ISO
standard.
In R/3 Releases 4.6C and 4.6D, the XSF stream sets a default value for data encoding.
The default is ODWLQ. The generated XSF processing instruction looks as follows:
<?xml version=1.0 encoding=latin1?>
As of R/3 Release 5.0 there is a new attribute lang that defines the text language.
17
SAP AG

SAP BC-XSF
6HWXS2XWSXW'HYLFHIRU;6)6SRRO0RGH
To pass the XSF data to an external system, a special output device must be created. R/3 spool
administration transaction SPAD is used to create the device. When creating an output device the
maintenance screens offer the following parameters:
Table 10
Parameter
Description
2XWSXW'HYLFH
Every outgoing document in R/3 requires a destination. Since output

can be sent not only to printers but also to fax or archiving devices, the
general term in R/3 for these destinations is output device.
'HYLFH7\SH
In order to format a document, R/3 must have some information on the

capabilities of the output device (for example, a list of available fonts).
This kind of information is contained in a device type definition. For
every output device that exists in R/3, a device type must be specified,
which will be used when processing the output document. To one
physical printer several output devices with different device types can
be assigned in R/3.
$FFHVV0HWKRG
The access method (plus associated parameters like printer queue

name or name of network host) tells the R/3 spooler how to route the
print data to its destination. In general, access methods can be
subdivided into local and remote access methods.
&RPPDQG6HW
It is possible to specify the command line executed by R/3 when

passing an output request to the UNIX/NT spooler on a per-device
basis. For every output device using access method L, a command set
can be specified that defines the contents of the command line used to
transfer the spooler file to the operating system spooler (a second
command line must be specified for querying the job status).
For details about creating a new device refer to the online documentation >6322/@.
The device type should be PLAIN which is a special device type for XSF (no fonts are used, no
conversion due to different codepages is executed).
The easiest way to route the XSF data to the external system is to choose access methods L (local)
or E (external). Access method L allows you to define a command set. Example of a command set
for XSF (UNIX):
command to transfer print data:
cp &F /usr/sap/BIN/SYS/&f
command to query the job status:
echo ok
where &F is the path and filename of the R/3 print file, &f is the filename.
18
SAP AG
SAP BC-XSF
$SSHQGL[$;6)'RFXPHQW7\SH'HILQLWLRQ;6)'7'
<!DOCTYPE smartxsf [

<!ENTITY lt "<">
<!ENTITY gt ">">
<!ENTITY amp "&">
<!ENTITY % Flow-text
"sym | chr | url | tab | newline" >
<!ENTITY % Text-element
"(include-text | text)"
>
<!ENTITY % Table-contents "(thead?, tbody, tfoot?)"
>
<!ENTITY % Section-contents
"(graphics | address | section | %Text-element; |
new-page | print-control | tr)"
>
<!ENTITY % Tcell-contents
"(graphics | address | section | %Text-element;)"
>

<!ELEMENT smartxsf
(header, data+)
>
<!ELEMENT header)
(general | page+ | sort? | archive? |
mail? | telefax? )*
>

<!ELEMENT general
(version | device | form | language |
output-device?
| device-type |
tdtitle? | tdnoprev? | tdnoprint? | tdnoarch?
|
tdiexit? | tddataset? | tdsuffix1? |
tdsuffix2? | tdcovtitle? | tdnewid? |
tdimmed?
| tddelete?
| tdlifetime? |
tdauthority? | tdcover? | tdreceiver? |
tddivision? | tdcopies? | tdpageselect?)* >
<!ELEMENT version
>
(#PCDATA)
19
SAP AG
SAP BC-XSF
<!ELEMENT
<!ELEMENT
>
<!ELEMENT
>
<!ELEMENT
>
<!ELEMENT
>
<!ELEMENT
>
<!ELEMENT
>
<!ELEMENT
>
<!ELEMENT
>
<!ELEMENT
>
<!ELEMENT
>
<!ELEMENT
>
<!ELEMENT
>
<!ELEMENT
>
<!ELEMENT
>
<!ELEMENT
>
<!ELEMENT
>
<!ELEMENT
>
<!ELEMENT
>
<!ELEMENT
>
<!ELEMENT
>
<!ELEMENT
>
<!ELEMENT
>
<!ELEMENT
>
device
form
(#PCDATA)
(#PCDATA)
language
(#PCDATA)
output-device
(#PCDATA)
device-typ
(#PCDATA)
tdtitle
(#PCDATA)
tdnoprev
(#PCDATA)
tdnoprint
(#PCDATA)
tdnoarch
(#PCDATA)
tdiexit
(#PCDATA)
tddataset
(#PCDATA)
tdsuffix1
(#PCDATA)
tdsuffix2
(#PCDATA)
tdcovtitle
(#PCDATA)
tdnewid
(#PCDATA)
tdimmed
(#PCDATA)
tddelete
(#PCDATA)
tdlifetime
(#PCDATA)
tdauthority
(#PCDATA)
tdcover
(#PCDATA)
tdreceiver
(#PCDATA)
tddivision
(#PCDATA)
tdcopies
(#PCDATA)
tdpageselect
(#PCDATA)
<!ELEMENT page
>
<!ATTLIST page
>
EMPTY
name
id
NMTOKEN #REQUIRED
NMTOKEN #IMPLIED
20
>
SAP AG
SAP BC-XSF

<!ELEMENT data
>
<!ATTLIST data
preserve
(window | graphics | address)+

xml:space (default | preserve)
style
variant
<!ELEMENT window
<!ATTLIST window
#REQUIRED
NMTOKEN
#IMPLIED
NMTOKEN
#IMPLIED >
(%Section-contents; | table)*
name
NMTOKEN
type
page
(main|aux)
NMTOKEN
>
"aux"
#REQUIRED
page-id
NMTOKEN
#REQUIRED >
<!ELEMENT graphics
>
<!ATTLIST graphics
#REQUIRED
EMPTY
name
NMTOKEN
page
NMTOKEN
page-id
NMTOKEN
#IMPLIED
#IMPLIED
objname
object
id
type
resolution
<!ELEMENT address
<!ATTLIST address
#REQUIRED
NMTOKEN
NMTOKEN
NMTOKEN
NMTOKEN
NMTOKEN
#REQUIRED
#REQUIRED
#REQUIRED
#REQUIRED
#IMPLIED >
(text)
name
NMTOKEN
>
page
NMTOKEN
page-id
NMTOKEN
#IMPLIED
#IMPLIED
addrnumber
persnumber
<!ELEMENT section
>
<!ATTLIST section
#REQUIRED
NMTOKEN
NMTOKEN
#REQUIRED
#IMPLIED >
(shead?, sbody, sfoot?)*

name
style
variant
<!ELEMENT shead
>
<!ELEMENT sbody
>
NMTOKEN
NMTOKEN
#IMPLIED
NMTOKEN
#IMPLIED >
(%Section-contents;)*
(%Section-contents; | table )*
21
SAP AG
SAP BC-XSF
<!ELEMENT sfoot
>
(%Section-contents;)*
<!ELEMENT new-page
>
<!ATTLIST new-page
EMPTY
#IMPLIED
page
page-id
NMTOKEN
#IMPLIED
NMTOKEN
>
<!ELEMENT print-control
>
<!ATTLIST print-control
EMPTY
name
<!ELEMENT include-text
>
<!ATTLIST include-text
#REQUIRED
NMTOKEN
#REQUIRED >
(p)*
name
NMTOKEN
objname
NMTOKEN
#REQUIRED
id
object
language
style
variant
<!ELEMENT text
>
<!ATTLIST text
#REQUIRED
NMTOKEN
#REQUIRED
NMTOKEN
#REQUIRED
NMTOKEN
#REQUIRED
NMTOKEN
#IMPLIED
NMTOKEN
#IMPLIED >
(P)*
name
NMTOKEN
style
variant
<!ELEMENT p
>
<!ATTLIST p
#REQUIRED
NMTOKEN
NMTOKEN
#IMPLIED
#IMPLIED
>
(#PCDATA|%Flow-text;)*
name
appmode
NMTOKEN
(new-paragraph|new-
line|append)
"new-paragraph"
<!ELEMENT url
>
(#PCDATA | %Flow-text;)*
<!ELEMENT chr
>
<!ATTLIST chr
#REQUIRED >
(#PCDATA | %Flow-text;)*
<!ELEMENT sym
>
<!ATTLIST sym
<!ELEMENT new-line
>
(#PCDATA)
name
name
EMPTY
22
>
NMTOKEN
>
SAP AG
SAP BC-XSF
<!ELEMENT tab
>
EMPTY
<!ELEMENT table
>
<!ATTLIST table
#REQUIRED
(%Table-contents;)
name
pattern
style
variant
NMTOKEN
NMTOKEN
#IMPLIED
NMTOKEN
#IMPLIED
NMTOKEN
#IMPLIED >
<!ELEMENT thead
>
(tr | section)*
<!ELEMENT tbody
>
(tr | section)*
<!ELEMENT tfoot
>
(tr | section)*
<!ELEMENT tr
>
<!ATTLIST tr
#IMPLIED
(tc)+
row
ltype
<!ELEMENT tc
>
<!ATTLIST tc
#IMPLIED >
NMTOKEN
NMTOKEN
#IMPLIED
>
(%Tcell-contents;)+
cell
NMTOKEN

<!ELEMENT sort
>
<!ELEMENT sort-field
>
(sort-field)*
(#PCDATA)

<!ELEMENT archive
>
<!ATTLIST archive
EMPTY
mode
NMTOKEN
#REQUIRED
mode-modify-enabled (yes | no)
"yes"
objtype
NMTOKEN
object
NMTOKEN
#IMPLIED
#IMPLIED
target-system NMTOKEN
#IMPLIED
doctype
#IMPLIED
23
NMTOKEN
SAP AG
SAP BC-XSF
rpc-host
NMTOKEN
rpc-service
NMTOKEN
interface
NMTOKEN
report
NMTOKEN
info
NMTOKEN
text
NMTOKEN
date
NMTOKEN
user
NMTOKEN
format
NMTOKEN
path
NMTOKEN
log
NMTOKEN
version
NMTOKEN
#IMPLIED
#IMPLIED
#IMPLIED
#IMPLIED
#IMPLIED
#IMPLIED
#IMPLIED
#IMPLIED
#IMPLIED
#IMPLIED
#IMPLIED
#IMPLIED
>

<!ELEMENT mail
<!ELEMENT sender
>
<!ATTLIST sender
(sender, recipient)
EMPTY
system
objtype
NMTOKEN
#REQUIRED
NMTOKEN
#IMPLIED
objkey
NMTOKEN
description
NMTOKEN
#IMPLIED
#IMPLIED
>
<!ELEMENT recipient
>
<!ATTLIST recipient
#REQUIRED
EMPTY
system
NMTOKEN
objtype
NMTOKEN
objkey
NMTOKEN
description
NMTOKEN
#IMPLIED
#IMPLIED
#IMPLIED
>
<!ELEMENT telefax
>
<!ATTLIST telefax
#REQUIRED
EMPTY
country
24
NMTOKEN
>
SAP AG
SAP BC-XSF
number
NMTOKEN
extnumber
NMTOKEN
user
NMTOKEN
format
NMTOKEN
schedule
NMTOKEN
senddate
NMTOKEN
#REQUIRED
#IMPLIED
#REQUIRED
#REQUIRED
#REQUIRED
#REQUIRED
sendtime
]>
25
NMTOKEN
#REQUIRED >
SAP AG
SAP BC-XSF
$SSHQGL[%([DPSOHRIDQ$%$33URJUDP*HQHUDWLQJ;6)2XWSXW6WUHDP

!#"$%'& & ((
)

*+! ,-. /.+-103245"7685"79666
*:'& & (/
;

!
<'=.!->
)
>
-& ?!:*%->!

@'
->A BC0$DFE -.!E HG>IJ
&K HGCLM%N

>!H/O'P!H/O'-1"
-10Q?

RS.+-,HB' >!A K ?

.+-1L
/ FT ,HB' >
!H8U'E/T 1"

#0
!R'?&! .+-,HB' >! ?&! .+-,-/&E
2V"
! 'E ? .+T!#0W!R'?

.+-(/
?

RS.+-/&E Y
XZ* [5XQYXZ* [5X"
-10Q?&!
!
HB' ,HB '?&!
!#L
A K.T )!
HB' ,HB FA K.T )!#L
?TT ?.+T!HB' ,HB '?TT ?.+T!#"
-10Q& & ' .+T!
HB' >!!H/? #L
?T
'EF

!HB' >!!H/?
E #L
& & '-
HB' >!!H/?
! ?'EV"
\?.OG%'& & (-
& & ' .+T! P!H/
]YX^_X"
& & ' .+T! P!H/?-
]YX^_X"
& & ' .+T! P!H/& -,]YXbCX"
& & ' .+T! P!H//
c]>! ?1"
`3%'& & ,?.OG

àN
! /
>
)

à' 'E
`%
.T ) edf &
hg
%!.HE T ,- i

& & ' .+T! -.+-,]>! ?1"
& & ' .+T! -T jS.+-,]>! ?1"
?T
'EF

! T '-.+'E ),]YX^_X"
\->

.+HG'E

H/
,- F

.+HG'E;?= T ).T ),?&!
!lk+m
A K.T )!lk+m
?TT ?.+T!lk+mF"
\?'EE !
(/

;2V"W
! 'E+G>T ,/n)T
- n/&T ?.+T
?'EEn/&T ?.+ToXbhpi @<FqRiO p*Hi+VX
P
.T )r/
T
]YXb 2VX
.+
.T )r/ FT
](/ FT
P? .+T!,T /

]2
T /&T ?.+TR'-&E ,],9
=
!
](85"
. /s! B !&A
?,tu,61"

,= T -'E.T )
!! )v.+->! B ! ).+-,HB' >! B ! )HBT& A
,! B ! )T
jS.+=,! B ! )HG2 ! B ! )HG9>! B ! )HG8s! B ! )HGw1"
P.+1"
T -. /5"
\91"Q?'EE%n/&T ?.+T-&E ,T -> !!-
?'EEn/&T ?.+T / FT
P
.T )
?T
'EF

!
],?T
'EF

!
& & ' .+T!
],& & ' .+T!
&!
RF! .T )!
]>! ?
?&!
!
],?&!
!
A K.T )!
]>A K.T )!
?TT ?.+T!
],?TT ?.+T!
.+
.T )rx
AR'& & S.TH/
],& & '-
P? .+T! /
.T ) '

]2
.T
T 'E'

],9
! T - '

](8
&!
R'?T ?'E ],w
=
!
],y1"
26
SAP AG
SAP BC-XSF
. /s! B !&A
?,tu,61"

,= T -'E.T )
!! )v.+->! B ! ).+-,HB' >! B ! )HBT& A
,! B ! )T
jS.+=,! B ! )HG2 ! B ! )HG9>! B ! )HG8s! B ! )HGw1"
T -. /5"

/
,- F

.+HG'E &!.T )>R'?&!
!
HB' ,HB '?&!
!
RFA K.T )!
HB' ,HB FA K.T )!
R'?TT ?.+T!HB' ,HB '?TT ?.+T!#"
! 'E ?e:/
>! ?&! v.T ,AE >R'?&!
!
jF=
v.+-,]>!R'?&! .+
-
,A B
.+
BK HBC"
! 'E ?e:/
>!A K
.T ,AE >RFA K.T )!
jF=
,?&! .+-,]>!R'?&! .+-,T -,?

.+-v.T,!R'?

.+
-
,A B
.+
BK HBC"
! 'E ?e:/
>!H/E.
.T ,AE >R'?TT ?.+T!
/
'EE;T
.+!(.T,RFA K.T )!
jF=
,?

.+-,]>RFA K.T )! ?

.+T -,?TT.+-,]>RFA K.T )! ?TT.+
-
,A B
.+
BK HBC"
T -/
1"
27
SAP AG
SAP BC-XSF
$SSHQGL[&([DPSOHRI;6)2XWSXW6WUHDP
tP'E%G
!.+T ]S`+2V"76S` T ?-.T )]S`+E .T2ù
t!
P!H/u
t= -
u
t)T
'E u
tHG
!.+T u'2V" 22 t G
!.+T u
t/
uH 2 tR/
u
t'E T )& )u t+E T )& )u
t-HG.+?u'q i <t -HG.+?u
t& & -HG.+?u289t & & -HG.+?u
t-HG.+? HB' u[*wt -HG.+? HB' u
t--! uH+ <t --! u
t-!&H//.+P'2 u289t -!&H//.+P'2 u
t-!&H//.+P9uIp Dt -!&H//.+P9u
t-'E. /.+uUt -'E. /.+u
t-?.+! u66'2 t -?.+! u
t )T
'E u
t
?=.OG,-]S`+2` - -. / B T AE -]S` B!` u
t )>T ]S`+q < `;.+-]S` 66'2` u
tO= -
u
x
x
t->! HBE ]S` 2` u
t)
=.+?!,T ]S`+i

#` A T ]S`+i

#` A ?]S` N+['qR@ ;
` .+-]S`RI+F` H B' ]S`RI @*'`
)]S`+q < `: ) .+-]S` 66'2` u
t jS.T - j T ]S`R+Sq iF` HB' ]S` .T`: )]S`+q < `: ) .+-]S` 66'2` u
tP>T ]S` q i < p @<FqRiF`:! HBE ]S` 2` u
t,T ]S` ` u
=
)=
(T,&T -([

T#L7tT j E.T u
tO u
t,T ]S` ` u
jS.
j
T>q =T T,! =
;G
A&T -T#L j'TT;.+,-.+(/'E )T -(?=T&T )>A 'E -> A )'E .+?= T
j
-T#"3
-!
T ))T )A
?= D

& T,A -TK T jS.
,&T!#"7tT j E.T utT j E.T u
tO u
t Pu
tAE >T ]S` <I*H`:! HBE ]S` 2` u
t= -u
t
sE HB' ]S` <I*H[RF` u
t?,?'EE ]S`+2` u
tP>T ]S`R[RO@*H2`:! HBE ]S` 2` u
t,T ]S` <[F` u
N!
tO u
t Pu
t ?u
t?,?'EE ]S` 9S` u
tP>T ]S`R[RO@*+9S`:! HBE ]S` 2` u
t,T ]S` <[F` u
*.T.+
tO u
t Pu
t ?u
t?,?'EE ]S`R8F` u
tP>T ]S`R[RO@* 8F`:! HBE ]S` 2` u
t,T ]S` <[F` u
EH& )-&
tO u
t Pu
t ?u
t?,?'EE ]S` wS` u
tP>T ]S`R[RO@*+wS`:! HBE ]S` 2` u
t,T ]S` <[F` u
AH/EH& )
tO u
t Pu
t ?u
t?,?'EE ]S` yS` u
tP>T ]S`R[RO@*+yS`:! HBE ]S` 2` u
t,T ]S` <[F` u
tA utA u
.!
tO u
t Pu
t ?u
t
u
t = -u
tA -HBu
t! ?.+T,T ]S` *OOI F`:! HBE ]S` 2` u
28
SAP AG
SAP BC-XSF
t!A -HBu
t! ?.+T,T ]S` *OO@ii+@< `:! HBE ]S` 2` u
t!A -HBu
t
sE HB' ]S` <I*H ` u
t?,?'EE ]S`+2` u
tP>T ]S`RI @*H2`:! HBE ]S` 2` u
t,T ]S` <IF` u
t! B>T ]S` HI 'q i N @'q F` up+tO! Bu
tO u
t Pu
t ?u
t?,?'EE ]S` 9S` u
tP>T ]S`RI @*+9S`:! HBE ]S` 2` u
t,T ]S` <IF` u
t! B>T ]S` HI 'q i N @ii'q F` u6w'2 tO! Bu
tO u
t Pu
t ?u
t?,?'EE ]S`R8F` u
tP>T ]S`RI @* 8F`:! HBE ]S` 2` u
t,T ]S` <IF` u
t! B>T ]S` HI 'q i N * +<` u9U1"76U1"79666tO! Bu
tO u
t Pu
t ?u
t?,?'EE ]S` wS` u
tP>T ]S`RI @*+wS`:! HBE ]S` 2` u
t,T ]S` <IF` u
t! B>T ]S` H@ii+@<FqRi <Fq ` u'2 w10 8610766tO! Bu
tO u
t Pu
t ?u
t?,?'EE ]S` yS` u
tP>T ]S`RI @*+yS`:! HBE ]S` 2` u
t,T ]S` <IF` u
tA ut! B>T ]S` HI 'q i N + @p+F` u
6tO! ButA u
t! B>T ]S` HI 'q i N + @p #` uqR<*+tO! Bu
tO u
t Pu
t ?u
t
u
tO!A -HBu
tO! ?.+T u
t! ?.+T,T ]S` *OO@ii+@< `:! HBE ]S` 2` u
t!A -HBu
t
sE HB' ]S` <I*H ` u
t?,?'EE ]S`+2` u
tP>T ]S`RI @*H2`:! HBE ]S` 2` u
t,T ]S` <IF` u
tO u
t Pu
t ?u
t?,?'EE ]S` 9S` u
tP>T ]S`RI @*+9S`:! HBE ]S` 2` u
t,T ]S` <IF` u
t! B>T ]S` HI 'q i N @ii'q F` u
6 w'2 tO! Bu
tO u
t Pu
t ?u
t?,?'EE ]S`R8F` u
tP>T ]S`RI @* 8F`:! HBE ]S` 2` u
t,T ]S` <IF` u
t! B>T ]S` HI 'q i N * +<` u'2 1" 22V"79666tO! Bu
tO u
t Pu
t ?u
t?,?'EE ]S` wS` u
t,T ]S` <IF` u
t! B>T ]S` H@ii+@<FqRi <Fq ` u'2 w10 8610766tO! Bu
tO u
t Pu
t ?u
t?,?'EE ]S` yS` u
t,T ]S` <IF` u
29
SAP AG
SAP BC-XSF
tA ut! B>T ]S`HI 'q i N + @p+F` u

6tO!
B utA u
t! B>T ]S`HI 'q i N + @p #` uqR<*+tO! Bu
tO u
t Pu
t ?u
t
u
tO!A -HBu
tO! ?.+T u
t! ?.+T,T ]S` *OO@ii+@< `:! HBE ]S` 2` u
t!A -HBu
t
sE HB' ]S` <I*H ` u
t?,?'EE ]S`+2` u
tP>T ]S`RI @*H2`:! HBE ]S` 2` u
t,T ]S` <IF` u
tO u
t Pu
t ?u
t?,?'EE ]S` 9S` u
tP>T ]S`RI @*+9S`:! HBE ]S` 2` u
t,T ]S` <IF` u
t! B>T ]S` HI 'q i N @ii'q F` u8y6wtO! Bu
tO u
t Pu
t ?u
t?,?'EE ]S`R8F` u
tP>T ]S`RI @* 8F`:! HBE ]S` 2` u
t,T ]S` <IF` u
t! B>T ]S` HI 'q i N * +<` u691" 2 91"79666tO! Bu
tO u
t Pu
t ?u
t?,?'EE ]S` wS` u
t,T ]S` <IF` u
t! B>T ]S` H@ii+@<FqRi <Fq ` u'2 y1076610766tO! Bu
tO u
t Pu
t ?u
t?,?'EE ]S` yS` u
t,T ]S` <IF` u
61L766tO!
B utA u
t! B>T ]S` HI 'q i N + @p #` utO! Bu
tO u
t Pu
t ?u
t
u
tO!A -HBu
tO! ?.+T u
t! ?.+T,T ]S` *OO@ii+@< `:! HBE ]S` 2` u
t!A -HBu
t
sE HB' ]S` <I*H ` u
t?,?'EE ]S`+2` u
tP>T ]S`RI @*H2`:! HBE ]S` 2` u
t,T ]S` <IF` u
tO u
t Pu
t ?u
t?,?'EE ]S` 9S` u
tP>T ]S`RI @*+9S`:! HBE ]S` 2` u
t,T ]S` <IF` u
t! B>T ]S` HI 'q i N @ii'q F` u8y6wtO! Bu
tO u
t Pu
t ?u
t?,?'EE ]S`R8F` u
tP>T ]S`RI @* 8F`:! HBE ]S` 2` u
t,T ]S` <IF` u
t! B>T ]S` HI 'q i N * +<` u82V" 2 91"79666tO! Bu
tO u
t Pu
t ?u
t?,?'EE ]S` wS` u
t,T ]S` <IF` u
30
SAP AG
SAP BC-XSF
t! B>T ]S`H@ii+@<FqRi <Fq ` u'2 y1076610766tO! Bu

t O u

t Pu
t ?u
t?,?'EE ]S` yS` u
t,T ]S` <IF` u
61L766tO! ButA u
t! B>T ]S` HI 'q i N + @p #` utO! Bu
tO u
t Pu
t ?u
t
u
tO!A -HBu
tO! ?.+T u
tO!A -HBu
tO! ?.+T u
t A -HBu
t/u
t
sE HB' ]S` <I*Hh+<F` u
t?,?'EE ]S`+2` u
tP>T ]S` <<h* <R< `:! HBE ]S` 2` u
t,T ]S` <[F` u
N! !&
tO u
t Pu
t ?u
t?,?'EE ]S` 9S` u
t! ?.+T,T ]S`+q i+h*OpF`:! HBE ]S` 2` u
t!A -HBu
tP>T ]S` <<h*'`:! HBE ]S` 2` u
t,T ]S` <IF` u
tA ut?=
,T ]S`RIF` ut! B>T ]S` H< p + @p+F` u
61L766tO! But ?=
utA u
t?=
,T ]S`RIF` ut! B>T ]S` H< p + @p #` utO! But ?=
u
tO u
t Pu
tP>T ]S` <<h*'`:! HBE ]S` 2` u
t,T ]S` <IF` u
tA ut?=
6tO! But ?=
utA u
t?=
,T ]S`RIF` ut! B>T ]S` H< p + @p #` uqR<*+tO! But ?=
u
tO u
t Pu
tP>T ]S` <<h*'`:! HBE ]S` 2` u
t,T ]S` <IF` u
tA ut?=
61L766tO! But ?=
utA u
t?=
,T ]S`RIF` ut ?=
u
tO u
t Pu
tP>T ]S` <<h*'`:! HBE ]S` 2` u
t,T ]S` <IF` u
tA ut?=
61L766tO! But ?=
utA u
t?=
,T ]S`RIF` ut! B>T ]S` H< p + @p #` up tO! But ?=
u
tO u
t Pu
tO!A -HBu
tO! ?.+T u
t ?u
t
u
t /u
t AE u
tP>T ]S` N+<Fq i N `:! HBE ]S` 2` u
t,T ]S` ` u
tO u
t,T ]S` ` u
tO u
t,T ]S` ` u
.+(/
&T -'E.+?= T;N'
T tT j E.T uq +>[ * 'q i NnNtT j E.T u
tO u
t Pu
t jS.T - j'u
x
t jS.T - j T ]S` + `: )]S`+q < `: ) .+-]S` 66'2` ux
t.T ?'EH& - P>T ]S` O q i @*'`:! HBE ]S` + ` A T ]S` iF`;.+-]S` ` A ?]S` <R< `
E T )& )]S`R` u
t,T ]S` F` u
t?=
,T ]S`RIF` uq +>['E -.T )Nt ?=
u1L ! /?= 1L (&!
! -
tO u
t .T ?'EH& - Pu
31
SAP AG
SAP BC-XSF
t--
!!, )]S`+q < `: ) .+-]S` 66'2` --
T& A
]S` 66666w'2 wS` u
tP>T ]S` + `:! HBE ]S` 2` u
t,T ]S` ` u
,+<SqH*:* p <FqRi ,NI[M@C" NtT j E.T ui& (I=T= /!
,9'2 tT j E.T u
tT j E.T u 8U <C"aq i NI <tT j E.T utT j E.T utT j E.T utT j E.T u
tT j E.T utT j E.T utT j E.T u
tO u
t Pu
t --
!! u
t jS.T - j'u
t jS.T - j T ]S` q i+ `: )]S`+q < `: ) .+-]S` 66'2` u
tP>T ]S` q i+ <R< `:! HBE ]S` 2` u
t,T ]S` ` u
t?=
,T ]S`RIF` u?=T&T )t ?=
utT j E.T utT j E.T u
tO u
t,T ]S` ` u
t?=
,T ]S` ` upT!
;?=A
A .+
tA ut ?=
u[

T !
tO u
t,T ]S` ` u
t?=
,T ]S` ` uH<'E /T tA ut ?=
uVd 6 hg 2 6
tO u
t,T ]S` ` u
t?=
,T ]S` ` uH<'E /PtA ut ?=
uVd 6 hg 2 9
tO u
t,T ]S` ` u
t?=
,T ]S` ` u.+?= T tA ut ?=
u8 %2
tO u
t,T ]S` ` u
t?=
,T ]S` ` u &T -TT&
tA ut ?=
ut! B>T ]S` H@p < q F` u66666699tO! Bu
tO u
t,T ]S` ` u
t?=
,T ]S` ` u& tA ut ?=
ut! B>T ]S`
+<pF` u'21"76y1"79666tO! Bu
tO u
t Pu
t jS.T - j'u
t jS.T - j T ]S`++<F`: )]S`+q < `: ) .+-]S` 66'2` u
tP>T ]S`Rp*'`:! HBE ]S` 2` u
t,T ]S` ` u
I!& ?= T;.+>A.+>&T!
A .+10
t?=
,T ]S` F` u' t ?=
ut&
E u jjj "7t?=
,T ]S`RIF` u.+-! )t ?=
u1"7-tO&
E u
tO u
t Pu
x
x
t.T ?'EH& - P>T ]S`++<O q i @*'`:! HBE ]S` + ` A T ]S` h+<F`;.+-]S` ` A ?]S` <R< `
E T )& )]S`R` u
t,T ]S`++< ` u
tT j E.T u&!
!
2 (&!
! - ! /?= ( (&!
! - M<'E /T d 6
hg 6 M<'E P,w ,6
6 ,&!- M<'E /P d 6 hg 2 9 tT j E.T u D'EHK!A TKsH
TKH/&
;d I*
99 hg\y6,
w ,
6 Sq+<>+v
! ).
K T
EH!
&= ;d I*6 66 hg (8
tT j E.T u
! -T
ITKsH
TKH/&
;d I*,U66 hg\
w 222;66 Sq+<>+>, & ! ?=
ITK [A&
) d I*(466 hg\
6 ,yyyyy Sq+<>p <>%tT j E.T u D
! T -10M<'= !;?= .+-
'=
T I.!= M@'= T 'E h.HEE .TM.+)
&=;<K = !=. ).!
)
.+?= ([.+-'EHA
)([I
tO u
t .T ?'EH& - Pu
t jS.T - j'u
t -u
tO!
P!H/u
32
SAP AG
SAP BC-XSF
$SSHQGL['*ORVVDU\DQG$EEUHYLDWLRQV
Include Text
SAPscript Texts stored in the SAP R/3 System; R/3 clientdependent.
RDI
Raw Data Interface. Interface to external application programs

for SAPscript. Result of processing a SAPscript form,
alternative to OTF Output, no layout information is provided.
Template
A table that is completely located on one page; and therefore

contains no header/footer parts. In opposite to regular tables the
template cells can be filled out in an arbitrary order, by means of
direct addressing of the cell (specifying row and cell number)
Text Module
The successor of SAPscript include texts. Can be referred to or

included in Smart Forms; R/3 client-independent.
XSF
XML for SAP Smart Forms. A successor of RDI. Result of

processing a Smart Form in the XML-compatible form, no
layout information is provided.
33
SAP AG
SAP BC-XSF
5HIHUHQFHV
SAP Archive Link

See SAP Library: Basis ComponentsBasis Services / Communication InterfacesSAP
ArchiveLinkBC - SAP ArchiveLink
>$5/,1.@
>%&,@
See SAP Library: Basis ComponentsBasis Services / Communication

InterfacesCommunication InterfacesSAP Internet Mail Gateway
Output Management Interface.
http://www.sap.com/csp/scenarios/index.htm
>%&;20@
>&66@ Cascading Style Sheets (CSS) Version 2.0. W3C Recommendation.

http://www.w3.org/Style/CSS/
Smart Forms Documentation on Fields.

Smart FormsUsing SAP Smart FormsUsing Parameters in a FormUsing Fields in
the Form
>),(/'@
>,1&/8'(7(;7@SAPscript Documentation on Include Texts.

InterfacesSAPscriptBC Style and Form MaintenanceSAPscript Control
CommandsIncluding Other Texts: INCLUDE
See also in SAP Library: Basis ComponentsBasis Services / Communication
InterfacesSAPscriptBC SAPscript: Printing with FormsSAPscript in
DetailInserting Other TextsIncluding TextsIncluding other Texts
>5',@
SAPscript Raw Data Interface (RDI) Version 1.13. SAP White Paper.
>6$3&200@

InterfacesCommunication InterfacesBC The SAP Communications Server
>6$3&211(&7@

InterfacesCommunication InterfacesBC SAP Connect
SAP Spool documentation on printer escape sequencies,
See SAP Library: Basis ComponentsComputing Center Management SystemBC SAP Printing Guide
>6322/@
SAP Spool documentation on printer escape sequencies,

See SAP Library: Basis ComponentsComputing Center Management SystemBC SAP Printing GuideDevice Types for SAP Output DevicesDefining a New Device
TypePrint Controls
>6322/(6&@
Associating Style Sheets with XML documents. W3C Recommendation.

http://www.w3.org/TR/xml-stylesheet/
>67</(;0/@
>7(;702'8/(@

Smart FormsText Modules
Extensible Markup Language (XML) 1.0. W3C Recommendation.
http://www.w3.org/TR/1998/REC-xml-19980210
>;0/@
34
SAP AG
SAP BC-XSF
XSL Transformations (XSLT) Version 1.0. W3C Recommendation.

http://www.w3.org/TR/xslt
>;6/@
35

Smartforms XML Format

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Smartforms XML Format

Enviado por

Direitos autorais:

Formatos disponíveis

SAP AG

SAP Smart Forms XSF

August 17th, 2000

Please visit our web page at www.sap.com/csp/scenarios

Copyright 2000 SAP AG. All rights reserved.

Header Element <general>

XSF output can be activated:

at runtime via the parameter structure OUTPUT_OPTIONS

Determines whether the runtime settings (XSFCMODE=X) or static

Controls whether XSF (XSF=X) or OTF (XSF=space) output should be

Specifies the output type. At present the values A (application) and

Output device (for example, PRINTER,

Device type (for example, HPLJ5)

Printer name (initial if DEVICE is not

Number of identical copies

Print: SAP cover page

Print parameters: text for cover page

Spool request: Name

Print parameters: delete after printing

Print parameters: department on cover

Immediately exit after printing/faxing

Print parameters: print immediately

Print parameters: spool retention period

Print parameters: new spool request

No changes by user in archiving mode

No printing from print preview

Pages selected for printing

Print parameters: recipient

Spool request: Suffix 1

Spool request: Suffix 2

Title in dialog box

SAP ArchiveLink: archiving date

SAP ArchiveLink: document class

SAP ArchiveLink: output format

SAP ArchiveLink: info field

SAP ArchiveLink: name of

SAP ArchiveLink: storage connection

Print: archiving mode

Changes by user allowed in archiving

SAP ArchiveLink: object type of

SAP ArchiveLink: standard archive

SAP ArchiveLink: report name

SAP ArchiveLink: RPC host

SAP ArchiveLink: RPC service / RFC

SAP ArchiveLink: target storage

SAP ArchiveLink: text information

Data element for user

SAP ArchiveLink: version number

Element <window> describes a logical unit of structured information.

R/3 Dictionary key field: graphic Id (BMAP)

Name of the graphic object in the Smart Form

R/3 Dictionary key field: object type (GRAPHICS)

R/3 Dictionary key field: graphic name

Page name (applied for GRAPHICS as a window)

Page ID (applied for GRAPHICS as a window)

R/3 Dictionary key field: color (BCOL) / black-and-white

Element <graphics> is an empty element.

R/3 Dictionary key field: Company number in the SAP Central

Name of the address object in the Smart Form

Page name (applied for ADDRESS as a window)

Page ID (applied for ADDRESS as a window)

R/3 Dictionary key field: Personal number in the SAP CAM

Element <section> is used to group other elements.

Element <print-control> contains printer escape sequences >6322/(6&@.

`3%'& & ,?.OG

%!.HE T ,- i

tA ut! B>T ]S`HI 'q i N + @p+F` u

t! B>T ]S`H@ii+@<FqRi <Fq ` u'2 y1076610766tO! Bu

>&66@ Cascading Style Sheets (CSS) Version 2.0. W3C Recommendation.

>,1&/8'(7(;7@SAPscript Documentation on Include Texts.