J16 BB ConfigGuide en US

Release 1.470

November 2003

English

J16 – Smart Forms

SAP AGNeurottstr. 1669190 WalldorfGermany

Building Block Configuration Guide

SAP Best Practices Building Block Title: Configuration Guide

Copyright

© Copyright 2003 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®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks of Microsoft Corporation.

IBM®, DB2®, DB2 Universal Database, OS/2®, Parallel Sysplex®, MVS/ESA, AIX®, S/390®, AS/400®, OS/390®, OS/400®, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere®, Netfinity®, Tivoli®, Informix and Informix® Dynamic ServerTM are trademarks of IBM Corporation in USA 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®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc.

HTML, DHTML, XML, XHTML 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.

MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One.

SAP, SAP Logo, R/2, R/3, mySAP, mySAP.com, xApps, mySAP Business Suite, 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 in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies.

© SAP AG Page 2 of 12


Icons

Icon Meaning

Caution

Example

Note or Tip

Recommendation

Syntax

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.



ContentsSmart Forms: Configuration Guide.................................................................................................5

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

2 Preparation.............................................................................................................................. 5

2.1 Prerequisites..................................................................................................................5

2.2 Uploading the Configuration Role..................................................................................5

3 Configuration........................................................................................................................... 5

3.1 Customizing in SD: Assigning SAP Smart Form Print Programs and Forms.................5

3.2 <Next Component or Configuration Step >....................................................................8



Smart Forms: Configuration Guide

1 PurposeThe purpose of this document is to describe the general configuration steps required to manually set up the configuration within the system landscape that has already been installed using the corresponding installation or configuration guides for installation.

The Building Block Configuration Guide describes how to set up the configuration of a building block manually, without the support of automated configuration tools. If you want to use BC Sets and CATT procedures for an automated installation process, refer to the Building Block Installation Guide of this building block

2 Preparation

2.1 PrerequisitesList dependencies with other building blocks and describe the general prerequisites that you have to fulfill to install this building block. Do not repeat preparation settings already described in other building block guides.

2.2 Uploading the Configuration Role

UseBefore you start with the configuration according to the manual procedures described in this Configuration Guide, you can upload the configuration role and assign it to your user.

This building block provides a configuration role for each SAP component that is involved in its configuration, such as SAP APO; SAP R/3, or SAP CRM. The configuration role enables you to comfortably access all transactions required for the configuration from the relevant system. The following roles are available:

Technical name Description File name for upload

ProcedureFor details how to upload the configuration roles to the system and how to work with the roles please refer to the document Essential Information.



3 Configuration

3.1 Customizing in SD: Assigning SAP Smart Form Print Programs and Forms

3.1.1 Sales Documents

Use In this task, you learn to assign SAP Smart Form print programs and forms to sales documents, such as inquiry, quotation, order confirmation, contract, and scheduling agreement.

Procedure 1. To carry out the activity, choose one of the following navigation options:

IMG Menu

Transaction Code V/G7

2. On the Determine Work Area Entry dialog box, make the following entries:

Field name Description R/O/C User action and values Note

Output type AF00 Sales Inquiry

3. Choose .

4. On the Change View "Processing Routines" : Overview screen, assign the Smart Form print program to the appropriate Smart Form name, and to the desired medium (such as fax). In the next step, refer to the chart that maps each form to the corresponding output type, Smart Form print program name, and country specific Smart Form name.

Below is an example of the configuration for Sales Inquiry Output Type AF00 where there is a



Smart Form assigned to Medium 1:

5. For each desired Medium, Under Program, in the Change View “Processing Routines” screen, enter the Smart Form Print program, and under SmartForm, enter the corresponding Smart Form.

6. Once the configuration has been completed for one Output type, to save the changes, choose Save.

7. Enter configuration for the next Output Type until all needed forms have been configured.

Document Types

Output Types Transaction Code

Smart Form Program

Smart Form

Sales Inquiry AF00 (Inquiry) V/G7 /SMB40/RVADOR01 /SMB40/SDINQ_L

/SMB40/SDINQ_A

Quotation AN00 (Quotation) V/G7 /SMB40/RVADOR01 /SMB40/SDQUO_L

/SMB40/SDQUO_A

Order Confirmation

BA00 (Order Confirmation)

V/G7 /SMB40/RVADOR01 /SMB40/SDORC_L

/SMB40/SDORC_A

Cash Sales Receipt

RD03 (Cash Sales) V/G7 /SMB40/RVADOR01 /SMB40/SDCSH_L

/SMB40/SDCSH_A

Contract KO00 (Contract) V/G7 /SMB40/RVADOR01 /SMB40/SDCON_L

/SMB40/SDCON_A

Scheduling Agreement

LP00 (Scheduling Agreement)

V/G7 /SMB40/RVADOR01 /SMB40/SDSDA_L

/SMB40/SDSDA_A

8. Assign other Smart Forms to other mediums as needed (for examle, Fax).

9. To save the changes, choose .



3.1.2 Delivery Notes

Use


IMG Menu

Transaction Code V/G9

2. In the Determine Work Area Entry dialog box, in Output type, enter LD00.

3. Choose .

4. On the Change View “Processing Routines”: Overview screen, in the first medium, for Print output, enter the Smart Form print program RLE_DELNOTE under Program and the Smart Form name according to the following chart under SmartForm.

Document Types


Smart Form Program

Smart Form

Delivery Note LD00 (Delivery Note)

V/G9 RLE_DELNOTE /SMB40/SDDLN_L

/SMB40/SDDLN_A


3.1.3 Billing Documents

Use


IMG Menu

Transaction Code V/83

2. On the Determine Work Area Entry dialog box, in Output type, enter RD00.

3. Choose .

4. On the Change View “Processing Routines” : Overview screen, in the first medium, for Print output, enter the Smart Form print program RLB_INVOICE under Program and Smart Form /SMB40/SDINV_L under SmartForm.

Document Types


Smart Form Program

Smart Form

Sales Invoice RD00 (Invoice) v/83 RLB_INVOICE /SMB40/SDINV_L

/SMB40/SDINV_A




3.1.4 Picking List

Use


IMG Menu

Transaction Code V/38

2. On the Display View "Output Types": Overview screen, in the Output type group box, select EK00.

3. In the left frame, under Dialog Structure, double-click on the Processing routines folder.

4. On the Change View "Processing Routines": Overview screen, choose .

5. In the first medium, for Print output, enter the Smart Form print program /SMB40/RVADEK01 under Program and Smart Form /SMB40/SDPIK_L under SmartForm.

Document Types


Smart Form Program

Smart Form

Picking List EK00 v/38 /SMB40/RVADEK01 /SMB40/SDPIK_L

/SMB40/SDPIK_A


3.2 Customizing in MM: Assigning SAP Smart Form Print Programs and Forms

3.2.1 Material Management Documents

Use In this task, you assign SAP Smart Form print programs and forms to Material Management (MM) documents such as request for quotation, purchase order, contract/scheduling agreement, and delivery schedule.

After the transport is imported into the target system, each Smart Form must be activated before it can be used. Activation also applies to new forms created in the system. For example, you must activate a form if you have copied a form into the customer namespace.


IMG Menu

Transaction Code NACE

2. On the Conditions for Output Control screen, in the Application / Description box, select EA / Purchasing RFQ.



3. Select Output types.

4. On the Display View “Output Types”: Overview screen, in the Output type group box, select NEU.

5. In the left frame, under Dialog Structure, double-click on the Processing routines folder.

6. On the Change View “Processing routines”: Overview screen, choose .

7. In the first medium, for Print output, enter the Smart Form print program /SMB40/FM06P under Program and in our example, Smart Form /SMB40/MMRFQ_L under SmartForm. Select the appropriate Smart Form for your country

Document Types

Application Output Types

Smart Form Program

Smart Form

Request for Quotation

EA NEU (RFQ)

/SMB40/FM06P /SMB40/MMRFQ_L

/SMB40/MMRFQ_A


9. For additional MM document types:

Document Types

Application Output Types Smart Form Program

Smart Form

Purchase Order EF NEU (Purchase Order)

/SMB40/FM06P

/SMB40/MMPO_L

/SMB40/MMPO_A

Contract/Scheduling Agreement

EV NEU (Outline agreement)

/SMB40/FM06P

/SMB40/MMCON_L

/SMB40/MMCON_A

Delivery Schedule

EL LPET (SchedAgrmtSchedLine)

/SMB40/FM06P

/SMB40/MMDLS_L

/SMB40/MMDLS_A

3.2.2 Goods Receipt Slips

Use


IMG Menu

Transaction Code M706

2. On the Display View “Output Types”: Overview screen, in the Output Types group box, select the desired goods receipt version (for example, WE01 for goods receipt version 1).

3. In the left frame, under Dialog Structures, double-click on Processing routines.

4. On the Change View “Processing routines”: Overview screen, choose .

5. In the first medium, for Print output, enter the Smart Form print program /SMB40/M07DR under Program and Smart Form /SMB40/MMGR1_L under SmartForm.




7. Repeat the above configuration for the following MM goods receipt document types:

Document Types Output Types Transaction Code

Smart Form Program

Smart Form

Goods Receipt Slip (Individual Item)

WE01 (GR Note Vers.1)

M706 /SMB40/M07DR /SMB40/MMGR1_L

/SMB40/MMGR1_A

Goods Receipt Slip (Individual Item with Inspection text)



/SMB40/MMGR2_A

Goods Receipt Slip (Multiple Items)



/SMB40/MMGR3_A

Goods Issue 1 (Individual Item with Inspection text)

WA01 (GI Note Vers.2)

M706 /SMB40/M07DR /SMB40/MMGI1_L

/SMB40/MMGI1_A

Goods Issue 2 (Individual Item with Inspection text)



/SMB40/MMGI2_A

Goods Issue 3 (Multiple Items)



/SMB40/MMGI3_A

3.3 Customizing in FI: Assigning SAP Smart Form Print Programs and Forms

3.3.1 Finance Documents

Use In this task, you assign SAP Smart Form print programs to Finance (FI) documents such as dunning note.


IMG Menu

Transaction Code FIBF

2. On the SAP Business Framework: Business Transaction Events screen, from the menu bar choose Settings -> P/S function modules -> … of an SAP appl.

3. Choose twice.

4. On the Change View “Application components per Publish & Subscribe interfac screen, in the Appl. box, select FI-FI.

5. In the Function module box next to FIFI, enter the print program FI_PRINT_DUNNING_NOTICE_SMARTF.




After the transport is imported into the target system, each Smart Form must be activated before it can be used. Activation also applies to new forms created in the system. For example, you must activate a form if you have copied a form into the customer namespace.

7. To carry out the activity, choose one of the following navigation options:

IMG Menu

Transaction Code F150

8. On the Dunning screen, from the menu bar choose Environment Change configuration.

9. On the Maintain Dunning Procedure: List screen, select 0001 under Procedure then choose the Choose button.

10. On the Maintain Dunning Procedure: Overview screen, choose Dunning texts.

11. On the Company Code/Account Type dialog box, in Company Code, enter your company code, then choose .

12. On the Maintain Dunning Procedure: Dunning texts screen, on the Normal dunning procedure tab, enter appropriate localized form according to the below chart. In our example, we use the Generic form, /SMB40/FIDUN_L in the Form column for all dunning levels.

Document Types

Output Types

Transaction Code

Smart Form Program

Smart Form

Dunning Notice FIBF, F150 FI_PRINT_DUNNING_NOTICE_SMARTF

/SMB40/FIDUN_L

/SMB40/FIDUN_A

13. Choose .


4 SupportTo report a problem, please open an Online Service System problem in the appropriate component area listed below, or call the hotline:

In the United Kingdom: +44 (0) 870 608 8000

In the United States: 1-888-216-ASAP.

For problems specifically related to our Preconfigured Smart Forms, use component SV-SMB-AIO-PSF.

For problems related to the Smart Forms tools, use component BC-SRV-SSF.

Notes to fix known problems can be found in the same component area. Customers should check both the CSN component above regarding our preconfigured Smart Forms, and the CSN component for the associated application or CSN component for the Smart Forms tool, depending on the nature of the problem encountered.
