Smartforms Adaptation en In

EHP5for SAP ERP 6.0

March 2011

English

Smartforms: Adaptation of Text Modules and Graphic

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany

SAP Best Practices Smartforms: Adaptation of Text Modules and Graphic

Copyright

© 2011 SAP AG. All rights reserved.

No part of this publication 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, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

© SAP AG Page 2 of 7


Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

External Process

Business Process Alternative/Decision Choice

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.

Cross-references to other documentation.

Example text Emphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXT Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example text> Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.



Contents

1 Purpose.................................................................................................................................. 5

2 Adaptation of Text Modules....................................................................................................5

3 Adaptation of Graphic.............................................................................................................6



Smartforms: Adaptation of Text Modules and Graphic

1 PurposeThis document describes how the text modules and the graphic delivered with the SAP Best Practices Baseline Package can be adapted.

2 Adaptation of Text ModulesDuring the installation of Building Block 153 (Printing Forms) the below listed text modules are copied from the source object to the target object in customer namespace. The copied objects contain the data delivered with the SAP Best Practices Baseline Package. To adapt this data (for example, company name, address) carry out the following steps:

SAP ECC menu Tools Form Printout Smartforms

Transaction code SMARTFORMS

1. On the SAP Smart Forms: Initial Screen select Text Module and enter the text module you want to change.

2. Choose Change.

3. On the Change XXXX Text Module screen choose the Text tab page.

4. Change the entries as required.

5. Choose Save.

All text modules are delivered in original language English. If you also want to change the text modules in additional languages, you will have to translate the changed texts as described below.

1. Access the transaction choosing one of the following navigation options:

SAP ECC menu Tools ABAP Workbench Utilities Translation Short and Long Textss

Transaction code SE63

2. Choose Translation ABAP Objects Other Long Texts.

3. On the Object Type Selection screen choose FS Forms and Styles SSF SAP Smart Form.

4. On the Other Long Texts: SAP Smart Form screen enter the object name, choose EN as Source Language and choose the required Target language.

5. Choose Edit.

6. On the SSF (..) Form EN To XX: ... screen make the necessary translations.

7. Choose Save Active.

Source Object Target Object Content

/SMB14/IN_ADR1 YBIN_ADR1 Header Address

/SMB14/IN_HEAD1 YBIN_HEAD1 Address

/SMB14/IN_FOOTER YBIN_FOOTER Footer



Source Object Target Object Content

/SMB14/IN_FOOTER1 YBIN_FOOTER1 Telephone

/SMB14/IN_FOOTER2 YBIN_FOOTER2Web, email, tax numbers

/SMB14/IN_FOOTER3 YBIN_FOOTER3 commercial register

/SMB14/IN_FOOTER4 YBIN_FOOTER4 Bank

/SMB14/IN_GRUSS YBIN_GRUSS regards

/SMB14/IN_ADR_SENDER YBIN_ADR_SENDER Address

/SMB14/IN_BILL_TO YBIN_BILL_TO Address

/SMB14/IN_PAGE_INFORMATION

YBIN_PAGE_INFORMATION

Page Information

/SMB14/IN_SENDER YBIN_SENDERAddress, telephone, email, Web

/SMB14/IN_TEL_SENDER YBIN_TEL_SENDER Telephone

/SMB14/IN_FAX_SENDER YBIN_FAX_SENDER Fax

/SMB14/IN_MAIL_SENDER YBIN_MAIL_SENDER email

/SMB14/IN_QMCON_BEGIN1 YBAA_QMCON_BEGIN1 QM letter

/SMB14/IN_QMCON_BEGIN2 YBAA_QMCON_BEGIN2 QM letter

/SMB14/IN_QMCON_END YBAA_QMCON_END QM letter

3 Adaptation of GraphicDuring the installation of Building Block 100 (SAP Best Practices Installation) the graphic file “smb40_leaf.bmp” is uploaded into the system and stored as “/SMBA0/AA_LEAF”. This graphic is used in all preconfigured Smartforms.

To replace the graphic file delivered with the SAP Best Practices Baseline Package with your own logo you have the following possibilities:

1. Adaptation before installation

Rename you own graphic file and use the new name “smb40_leaf.bmp”. Copy this file to folder containing the installation data (replace the original file). During the installation the modified graphic file will be used.

2. Adaptation after installation

Carry out the following steps to replace the already uploaded graphic file with your own one.

SAP ECC menu Tools Form Printout Administration Graphic

Transaction code SE78

1. On the Administration of Form Graphics screen expand the tree Stored on Document Server down to BMAP Bitmap Images (on the left side).

2. Select the entry BMAP Bitmap Images (double-click).

3. Select Color Bitmap Image.

4. Choose the menu entry Graphic Import.

5. Select your graphic file.



6. Enter the name /SMBA0/AA_LEAF and a description.

7. Select the Print Attributes

o Reserve Height Automatically

o Compression

8. On the Import Graphic pop-up screen confirm the message “Graphic /SMBA0/AA_LEAF already exists.Overwrite?” with Y.

For an optimal resolution the graphic should have the size of 109 * 109 pixels.


Documents

Smartforms Adaptation en In