printing: forms (153) -...

EHP4 for SAP ERP 6.0

June 2010

English

Printing: Forms (153)

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany

Building Block Configuration Guide

SAP Best Practices Printing: Forms (153): Configuration Guide

Copyright

© Copyright 2010 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 Business ByDesign, and other SAP productsand 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, WebIntelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects 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 of 30


Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Business Process Alternative/Decision Choice

Typographic Conventions

Type Style Description

Example textWords 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 TEXTKeys 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 andcharacters with appropriate entries.

© SAP AG of 30


ContentsPrinting Forms................................................................................................................................ 5

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

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

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

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

3.1 Styles & Text Modules...................................................................................................5

3.1.1 Copy Styles for SMARTFORMS into Customer Namespace....................................5

3.1.2 Copy Text Modules into Customer Namespace.........................................................6

3.1.3 Copy SAPscript Forms from Client 000.....................................................................7

3.1.4 Copy Smart Forms into Customer Namespace.........................................................9

3.1.4.1 Activate Smart Forms..........................................................................................11

3.1.5 Copy Print Programs into Customer Namespace....................................................11

3.1.5.1 Activate Print Programs......................................................................................12

3.1.6 Use and Assignment of Text Modules......................................................................13

3.1.6.1 Use of Text Modules for sender, letter header and footer texts...........................13

3.1.6.2 Assign Text Modules to Sales Organization........................................................13

3.1.6.3 Assign Text Modules to Purchasing Organization...............................................14

3.1.7 Assign Standard Texts for Invoice Verification Forms..............................................14

3.1.8 Assign MM and SD Forms.......................................................................................15

3.1.8.1 Assign SD Forms................................................................................................15

3.1.8.2 Assign MM Forms...............................................................................................16

3.1.8.3 Assign Forms (Layout Sets) for Print Reports.....................................................19

3.1.8.4 Assigning Form for Picking List...........................................................................20

3.1.9 Assign FI Forms and Text Modules.........................................................................20

3.1.9.1 Dunning Form.....................................................................................................20

3.1.9.1.1 Assign Forms for Interest Indicators..........................................................20

3.1.9.1.2 Form selection f. legal dunning proceed....................................................21

3.1.9.1.3 Def. Dunning Proc. - Form selection f. dunning notices.............................22

3.1.9.1.4 Define Sender Details for Dunning Forms.................................................22

3.1.9.2 Define Form Names for Correspondence Print...................................................23

3.1.9.3 Define Form Check Deposit................................................................................24

3.1.9.4 Set Up Paying Company Codes for Payment Transactions – Forms..................24

3.1.9.5 Set Up Payment Methods per Company Code for Payment Transact – Forms. .25

3.1.9.6 Define Sender Details for Correspondence Form...............................................27

3.1.10 Assigning QM Forms...............................................................................................28

© SAP AG of 30


Printing Forms

1 PurposeThis configuration guide provides you with the information you need to set up the configuration of this building block manually.

If you do not want to configure manually and prefer an automated installation process using BC Sets and other tools, refer to the SAP Best Practices Quick Guide, located on the SAP Note..

2 Preparation

2.1 PrerequisitesBefore you start installing this building block, you must install prerequisite building blocks. For more information, see the Building Block Prerequisite Matrix for Baseline. The matrix (an Excel file) is linked on the solution's DVD/website in one of the following two locations: Content Library Site Map

3 Configuration

3.1 Styles & Text Modules

3.1.1 Copy Styles for SMARTFORMS into Customer Namespace

UseProcess this activity to make sure that the used Styles are copied into your Customer Namespace.

Procedure1. Access the activity using one of the following navigation options:

IMG Menu Tools Form Printout Smartforms

Transaction Code SMARTFORMS

2. On the SAP Smart Forms: Initial Screen choose Style and then choose Copy (Ctrl + F5).

3. In Source Object, enter the name of the Style you want to copy.

4. In Target Object, enter the new name in your customer namespace.

© SAP AG of 30


Source Object Target Object

/SMBUSE/US_SFSTYLE YBUS_SFSTYLE

/SMBUSE/US_BL_SF YBUS_BL_SF

/SMBUSE/US_BC YBUS_BC

5. Save the new Style.

3.1.2 Copy Text Modules into Customer Namespace

UseProcess this activity to make sure that the used Text Modules are copied into your Customer Namespace.




2. On the SAP Smart Forms: Initial Screen choose Text Module and then choose Copy (Ctrl + F5).

3. In Source Object, enter the name of the Text Module you want to copy.



/SMBUSE/US_ADR1 YBUS_ADR1

/SMBUSE/US_FOOTER YBUS_FOOTER

/SMBUSE/US_FOOTER1 YBUS_FOOTER1




/SMBUSE/US_HEAD1 YBUS_HEAD1

/SMBUSE/US_GRUSS YBUS_GRUSS

/SMBUSE/US_ADR_SENDER YBUS_ADR_SENDER

/SMBUSE/US_BILL_TO YBUS_BILL_TO

/SMBUSE/US_PAGE_INFORMATION YBUS_PAGE_INFORMATION

/SMBUSE/US_SENDER YBUS_SENDER

/SMBUSE/US_FAX_SENDER YBUS_FAX_SENDER

/SMBUSE/US_TEL_SENDER YBUS_TEL_SENDER

/SMBUSE/US_MAIL_SENDER YBUS_MAIL_SENDER

/SMBUSE/US_BL_SENDER YBUS_BL_SENDER

© SAP AG of 30



/SMBUSE/US_BL_BILL_TO YBUS_BL_BILL_TO

/SMBA0/AA_QMCON_BEGIN1 YBAA_QMCON_BEGIN1

/SMBA0/AA_QMCON_BEGIN2 YBAA_QMCON_BEGIN2

/SMBA0/AA_QMCON_END YBAA_QMCON_END

5. Save the new Text Module.

3.1.3 Copy SAPscript Forms from Client 000

UseThe purpose of this activity is to copy the following SAPscript forms from client 000 into the customer namespace YB_* in your installation client:

/SMBUSE/US_LVSTA /SMBUSE/US_LVLIST LVSTOSOLO

LVSKOMMIL1 LVSKOMMIL2 F_M40S_CHEQUE

F140_ACC_STAT_01 F140_CASH_DOC_01 F_DUZI_01

FPAYM_DE_DTAUS0 FPAYM_DE_DTAZV F110_D_SCHECK

F110_EDI_01 F140_IND_TEXT_01 F140_INT_DOCU_01

F140_PAY_CONF_01 F130_LIST_02 F130_RESULT_02

INVENT SD_PICK_SINGLE F110_D_UEBERWEIS

F130_CONFIRM F130_ERROR_02 SD-CAS-MAIL

SD_EXPORT_FECO SD_EXPORT_EUDC QM_INSP_RESULT

FIAA_F001 /SMBUSE/US_CHK_U /SMBUSE/US_FISTM

/SMBUSE/US_REMIT /SMBUSE/US_CHK_N /SMBUSE/US_STMTB

MR_REKL PM_COMMON /SMB15/YBAA_QMIN

If you have already installed this building block in another client in your system, the forms will already be included in a transport request. This means that the forms are locked for change in the current implementation client and an error will occur. In this case, you must remove the objects from the transport request in the other client (transaction SE09) before you can carry out this step.


IMG Menu System Services Reporting

Transaction Code SA38

2. On the ABAP: Program Execution screen, enter the following data:

© SAP AG of 30


Field name Description User action and values Comment

Program RSTXFCPY

3. On the ABAP: Program Execution screen, choose Execute (F8) from the application bar.

4. On Copy Forms Between Clients screen, enter the following data:

Form Name Source Client

Target Form Original LanguageOnly

Flow Trace

/SMBUSE/US_LVSTA 000 YBUS_LVSTAE Deselect Select

5. Choose Execute (F8).

6. On Create Object Directory Entry screen, enter the following data: in the field Package the value of your required package(such as Z001) and create a workbench request if required.

7. Choose Back (F3).

8. Repeat steps 1 to 9 for the following forms:


Target Form Original Language Only

Flow Trace

/SMBUSE/US_LVSTA 000 YBUS_LVSTAE Deselect Select

/SMBUSE/US_LVLIST 000 YBUS_LVLIST Deselect Select

LVSTOSOLO 000 YBUS_LVSTOSOLO Deselect Select

LVSKOMMIL1 000 YBUS_LVSKOMMIL1 Deselect Select

LVSKOMMIL2 000 YBUS_LVSKOMMIL2 Deselect Select

F_M40S_CHEQUE 000 YBUS_F_M40S_CHE Deselect Select

F140_ACC_STAT_01 000 YBUS_F140_ACC01 Deselect Select

F140_CASH_DOC_01 000 YBUS_F140_CASH1 Deselect Select

F_DUZI_01 000 YBUS_F_DUZI_01 Deselect Select

FPAYM_DE_DTAUS0 000 YBUS_FPM_DTAUS0 Deselect Select

FPAYM_DE_DTAZV 000 YBUS_FM_DTAZV Deselect Select

F110_D_SCHECK 000 YBUS_F110_D_SCH Deselect Select

F110_EDI_01 000 YBUS_F110_EDI_01 Deselect Select

F140_IND_TEXT_01 000 YBUS_F140_TXT_1 Deselect Select

F140_INT_DOCU_01 000 YBUS_F140_DOC1 Deselect Select

F140_PAY_CONF_01 000 YBUS_F140_PCNF1 Deselect Select

F130_LIST_02 000 YBUS_F130_LST2 Deselect Select

F130_RESULT_02 000 YBUS_F130_RSLT2 Deselect Select

INVENT 000 YBUS_INVENT Deselect Select

SD_PICK_SINGLE 000 YBUS_SD_PICK_SIN Deselect Select

F110_D_UEBERWEIS 000 YBUS_F110_D_UEB Deselect Select

F130_CONFIRM_01 000 YBUS_F130_CNFM1 Deselect Select

© SAP AG of 30



Target Form Original Language Only

Flow Trace

F130_ERROR_02 000 YBUS_F130_ER2 Deselect Select

F110_D_AVIS 000 YBUS_F110_AVIS Deselect Select

SD-CAS-MAIL 000 YBUS_SD-CAS-MAIL Deselect Select

SD_EXPORT_FECO 000 YBUS_SD_EXP_FE Deselect Select

SD_EXPORT_EUDC 000 YBUS_SD_EXP_EU Deselect Select

QM_INSP_RESULT 000 YBUS_QM_INS_RLT Deselect Select

FIAA_F001 000 YBUS_FIAA_F001 Deselect Select

/SMBUSE/US_CHK_U 000 YBUS_CHK_U Deselect Select

/SMBUSE/US_FISTM 000 YBUS_FISTM Deselect Select

/SMBUSE/US_REMIT 000 YBUS_REMIT Deselect Select

/SMBUSE/US_CHK_N 000 YBUS_CHK_N Deselect Select

/SMBUSE/US_STMTB 000 YBUS_STMTB Deselect Select

/SMB15/YBAA_QMIN 000 YBUS_QMCOM Deselect Select

MR_REKL 000 YBUS_MM_MR_REKL

Deselect Select

PM_COMMON 000 YBUS_QM_PM_COMM

Deselect Select

ResultThe SAPscript forms are copied from client 000.

3.1.4 Copy Smart Forms into Customer Namespace

UseProcess this activity to make sure that the Smart Forms are copied into your Customer Namespace.




2. On the SAP Smart Forms: Initial Screen, choose Copy (Ctrl + F5).

3. In Source Object, enter the name of the Smart Form you want to copy.



Sales

© SAP AG of 30



/SMBUSE/US_SDINQ YBUS_SDINQ

/SMBUSE/US_BL_SDQUO_L YBUS_SDQUO

/SMBUSE/US_BL_SDORC_L YBUS_SDORC

/SMBUSE/US_SDCSH YBUS_SDCSH

/SMBUSE/US_SDCON YBUS_SDCON

/SMBUSE/US_SDSDA YBUS_SDSDA

Shipping

/SMBUSE/US_BL_SDDLN_L YBUS_SDDLN

/SMBUSE/US_BL_BOL_DLN_L YBUS_SDBLD

Billing

/SMBUSE/US_BL_SDINV_L YBUS_SDINV

Purchasing RFQ

/SMBUSE/US_BL_MMRFQ_L YBUS_MMRFQ

Purchase Order

/SMBUSE/US_BL_MMPO_L YBUS_MMPO

Purch.Outl.Agr.

/SMBUSE/US_BL_MMCON_L YBUS_MMCON

Purch.SchAgrRelease

/SMBUSE/US_MMDLS YBUS_MMDLS

Inventory Management

/SMBUSE/US_BL_MMGR1_L YBUS_MMGR1

/SMBUSE/US_MMGR2 YBUS_MMGR2

/SMBUSE/US_MMGR3 YBUS_MMGR3

/SMBUSE/US_BL_MMGI1_L YBUS_MMGI1

/SMBUSE/US_MMGI2 YBUS_MMGI2

/SMBUSE/US_MMGI3 YBUS_MMGI3

FI

/SMBUSE/US_FIMA YBUS_FIMA

PP

/SMBUSE/US_BL_PROD_ORD YBUS_PROD_ORD

Service Entry

/SMBUSE/US_MMSER YBUS_MMSER

Quality Management

/SMB15/AA_QMCOM YBUS_QMCOM

© SAP AG of 30


5. Save the new Smart Forms as Active version.

3.1.4.1 Activate Smart Forms

UseProcess this activity to make sure that the Smart Forms are active.




2. On the SAP Smart Forms: Initial Screen, enter your new Smart Form (see list above).

3. Choose Change.

4. Check if SAP Smart Forms has the Active status (this information is mentioned at the right of form’s name). If not, choose the Activate button (match).

5. During Smart Form activation, you will be asked to enter a Workbench Request.

6. Go back to continue the configuration.

ResultThe Smart Forms are activated.

3.1.5 Copy Print Programs into Customer Namespace

UseProcess this activity to make sure that the Smart Form print programs are copied into your Customer Namespace.


Transaction Code SE38

2. On the ABAP Editor: Initial Screen enter the source program.

3. Choose Copy (Ctrl + F5).

4. In the target program, enter the name of the new program.

Source Program Target Program

/SMBUSE/US_FM06P YBUS_FM06P

/SMBUSE/US_M07DR

YBUS_M07DR

/SMBUSE/US_RVADOR01 YBUS_RVADOR01

/SMBUSE/US_RLE_DELNOTE YBUS_RLE_DELNOTE

/SMBUSE/US_RLB_INVOICE YBUS_RLB_INVOICE

© SAP AG of 30


Source Program Target Program

/SMBUSE/US_FM06P YBUS_FM06P

/SMBUSE/US_M07DR

YBUS_M07DR

/SMBUSE/US_SFCOPCT_SFORM YBUS_SFCOPCT_SFORM

/SMBUSE/US_MMSER YBUS_MMSER

/SMBUSE/US_LVSTAE YBUS_LVSTAE

/SMBA0/AA_RQQMRB01 YBUS_RQQMRB01

3.1.5.1 Activate Print Programs

UseProcess this activity to make sure that the Print Programs are active.


IMG Menu System Services Reporting

Transaction Code SA38

2. On the ABAP Editor: Initial Screen enter the Print Program.

3. Choose Match (Shift + F9).

4. If a dialog box displays, choose Select all and then choose the Continue button.

5. Repeat the step for the following Print Programs.

Print Program

YBUS_FM06P

YBUS_M07DR

YBUS_RVADOR01

YBUS_RLE_DELNOTE

YBUS_RLB_INVOICE

YBUS_FM06P

YBUS_M07DR

YBUS_SFCOPCT_SFORM

YBUS_MMSER

YBUS_LVSTAE

YBUS_RQQMRB01

© SAP AG of 30


6. Go back to continue the configuration.

ResultThe Print Programs are activated.

3.1.6 Use and Assignment of Text Modules

3.1.6.1 Use of Text Modules for sender, letter header and footer texts

The Smart Forms text modules for the sender address (field ”Address text”) and the address in the letter header of the receivers address (field ”letter header”) can be maintained per sales organization (see 3.1.6.2), purchasing organization (see 3.1.6.3) and company code (for dunning notice and interest calculation, see 3.1.9.1.4).

Four text areas are provided for the output of the footer texts. (No. 1 - 4). Therefore it is necessary to maintain only the prefix for the Smart Forms text modules. Within the form processing the final text module name is concatenated in the following manner:

Prefix + <1-4> + _ + organizational unit

Example: /SMBA0/AA_FOOTER1_1000

If no Smart Forms text module is found, the final text module name is concatenated without the organizational unit (sales organization, purchasing organization, company code).

Prefix + <1-4>

Example: /SMBA0/AA_FOOTER2

If no Smart Forms text module is found, the corresponding footer area will be empty.

3.1.6.2 Assign Text Modules to Sales Organization

UseProcess this activity to assign the text modules to your Sales Organization.


IMG Menu Sales and Distribution Basic Functions Output Control Output Determination Process Output and Forms Assign Form Texts Assign form texts per sales organization

Transaction Code

V/85

2. Make the following entries:

Sales Org.

Address Text

Letter header Footer text li. Greeting text

Text SDS sender

1000 YBUS_ADR1 YBUS_HEAD1 YBUS_FOOTER

1100 YBUS_ADR1 YBUS_HEAD1 YBUS_FOOTER

3. Save your settings.

© SAP AG of 30


3.1.6.3 Assign Text Modules to Purchasing Organization

UseProcess this activity to assign the text modules to your Purchasing Organization.


IMG Menu Materials Management Purchasing Messages Texts for messages Define Texts for Purchasing Organization

IMG Activity

V_024E_T (SM30)

2. Select the purchasing organization and choose Details (Ctrl + Shift + F2).


Text Sndr Line Letter heading Text: footer Text: Close

YBUS_ADR1 YBUS_HEAD1 YBUS_FOOTER


3.1.7 Assign Standard Texts for Invoice Verification Forms

UseProcess this activity to assign the text modules for invoice verification to your company code.

Procedure 1. Access the activity using one of the following navigation options:

IMG Menu Materials Management Logistics Invoice Verification Message Determination Define Sender Details for Forms

Transaction Code

OMRU

2. On the Change View ”Sender Texts for Invoice Verification Forms”: Overview screen, chooseNew Entries.

3. On the New Entries: Details of Added Entries screen, enter the values shown below.

Field name Description User action and values Note

Company Code For example, 1000

Text ID ADRS

Header Text ADRS_HEADER

Footer Text ADRS_FOOTER

Signature Text ADRS_SIGNATURE

© SAP AG of 30



Sender ADRS_SENDER


5. Choose Back (F3).

3.1.8 Assign MM and SD Forms

3.1.8.1 Assign SD Forms

UseProcess these activities to configure the SD Smart Forms.


Transaction Code NACE

2. On the Conditions for output type Screen, select the application type (for example V1 for Sales) in the application column and choose Output types (F5).

3. On the Display View ”Output type”: Overview Screen, choose the change mode to change theconfiguration.

4. Choose the output type (for example AF00 for Inquiry) and double-click the processing routines in the left frame Dialog structure.

5. Choose New Entries and enter the following data:

Output Type AN00

Application V1

Medium 1 (Print output)

Program YBUS_RVADOR01

Form routine ENTRY

SmartForm YBUS_SDQUO

6. Save the setting.

7. Repeat procedure 4 - 6 for the documents specified below:

DescriptionOutputType

ApplicationMediumProgram Form routine Smart Form / Form

Quotation AN00 V1 1 YBUS_RVADOR01 ENTRY YBUS_SDQUO

Order confirmation

BA00 V1 1 YBUS_RVADOR01 ENTRY YBUS_SDORC

Cash Sale RD03 V1 1 YBUS_RVADOR01 ENTRY YBUS_SDCSH

Contract KO00 V1 1 YBUS_RVADOR01 ENTRY YBUS_SDCON

Scheduling Agreement

LP00 V1 1 YBUS_RVADOR01 ENTRY YBUS_SDSDA

Delivery LD00 V2 1 YBUS_RLE_DELNOTEENTRY YBUS_SDDLN

© SAP AG of 30


DescriptionOutputType

ApplicationMediumProgram Form routine Smart Form / Form

Note

Bill of Lading

YBL1 V2 1 YBUS_RLE_DELNOTEENTRY YBUS_SDBLD

Sales Invoice

RD00 V3 1 YBUS_RLB_INVOICE ENTRY YBUS_SDINV

Quotation AN00 V1 2 YBUS_RVADOR01 ENTRY YBUS_SDQUO

Order confirmation

BA00 V1 2 YBUS_RVADOR01 ENTRY YBUS_SDORC

Cash Sale RD03 V1 2 YBUS_RVADOR01 ENTRY YBUS_SDCSH

Contract KO00 V1 2 YBUS_RVADOR01 ENTRY YBUS_SDCON

Scheduling Agreement

LP00 V1 2 YBUS_RVADOR01 ENTRY YBUS_SDSDA

Delivery Note

LD00 V2 2 YBUS_RLE_DELNOTEENTRY YBUS_SDDLN

Bill of Lading

YBL1 V2 2 YBUS_RLE_DELNOTEENTRY YBUS_SDBLD

Sales Invoice

RD00 V3 2 YBUS_RLB_INVOICE ENTRY YBUS_SDINV

Direct Mailing

MAAK K1 1 RVCASM01 ENTRY YBUS_SD-CAS-MAIL (Form)

Export Declaration

FEEX V3 1 RVADAUS1 ENTRY_FEEX YBUS_SD_EXP_EU

Cert. of Origin EU

FECO V3 1 RVADAUS1 ENTRY_FECOYBUS_SD_EXP_FE

ResultAfter processing these steps the SD Smart Forms configuration is set up in your system.

3.1.8.2 Assign MM Forms

UseProcess these activities to configure the MM Smart Form.


Transaction Code NACE

2. On the Conditions for output type Screen, select the application type (for example EA for Purchasing RFQ) in the application column and choose Output types (F5)

© SAP AG of 30


3. On the Display View ”Output type”: Overview Screen, choose the change mode to change theconfiguration.

4. Choose the output type (for example NEU for RFQ) and double-click the processing routines in the left frame Dialog structure

5. Choose New Entries and type the following data:

Output Type NEU

Application EA

Medium 1 (Print output)

Program YBUS_FM06P

Form routine ENTRY_NEU

SmartForm YBUS_MMRFQ

6. Save the setting.

7. Repeat procedure 4 - 6 for the documents specified below:

Description OutputType

Applic. Medium Program Form routine Smart Form / Form

RFQ NEU EA 1 YBUS_FM06P ENTRY_NEU YBUS_MMRFQ

RFQ-Urging/Reminder

MAHN EA 1 YBUS_FM06P ENTRY_MAHN YBUS_MMRFQ

RFQ-Quo rejection

ABSA EA 1 YBUS_FM06P ENTRY_ABSA YBUS_MMRFQ

PO NEU EF 1 YBUS_FM06P ENTRY_NEU YBUS_MMPO

PO-Urging/Reminder

MAHN EF 1 YBUS_FM06P ENTRY_MAHN YBUS_MMPO

PO-Ack. Expediter

AUFB EF 1 YBUS_FM06P ENTRY_AUFB YBUS_MMPO

Contract (Scheduling Agreement)

NEU EV 1 YBUS_FM06P ENTRY_NEU YBUS_MMCON

Contract(SA)-Ack. Expediter

AUFB EV 1 YBUS_FM06P ENTRY_AUFB YBUS_MMCON

Delivery Schedule

LPET EL 1 YBUS_FM06P ENTRY_LPET YBUS_MMDLS

DLS-Forecast

LPH2 EL 1 YBUS_FM06P ENTRY_LPHE_CD YBUS_MMDLS

DLS-JIT LPJ2 EL 1 YBUS_FM06P ENTRY_LPJE_CD YBUS_MMDLS

DLS-Urging/Reminder

LPMA EL 1 YBUS_FM06P ENTRY_LPMA YBUS_MMDLS

Goods Receipt Slip1

WE01 ME 1 YBUS_FM06P ENTRY_WE01 YBUS_MMGR1

Goods WE02 ME 1 YBUS_FM06P ENTRY_WE02 YBUS_MMGR2

© SAP AG of 30




Receipt Slip 2

Goods Receipt Slip 3


Goods Issue Slip1

WA01 ME 1 YBUS_FM06P ENTRY_WA01 YBUS_MMGI1

Goods Issue Slip 2


Goods Issue Slip3


Service EntrySheet

NEU ES 1 YBUS_MMSER ENTRY_NEW YBUS_MMSER

RFQ NEU EA 2 YBUS_FM06P ENTRY_NEU YBUS_MMRFQ

RFQ-Urging/Reminder

MAHN EA 2 YBUS_FM06P ENTRY_MAHN YBUS_MMRFQ

RFQ-Quo rejection

ABSA EA 2 YBUS_FM06P ENTRY_ABSA YBUS_MMRFQ

PO NEU EF 2 YBUS_FM06P ENTRY_NEU YBUS_MMPO

PO-Urging/Reminder

MAHN EF 2 YBUS_FM06P ENTRY_MAHN YBUS_MMPO

PO-Ack. Expediter

AUFB EF 2 YBUS_FM06P ENTRY_AUFB YBUS_MMPO

Contract (Scheduling Agreement)

NEU EV 2 YBUS_FM06P ENTRY_NEU YBUS_MMCON

Contract(SA)-Ack. Expediter

AUFB EV 2 YBUS_FM06P ENTRY_AUFB YBUS_MMCON

Delivery Schedule

LPET EL 2 YBUS_FM06P ENTRY_LPET YBUS_MMDLS

DLS-Forecast

LPH2 EL 2 YBUS_FM06P ENTRY_LPHE_CD YBUS_MMDLS

DLS-JIT LPJ2 EL 2 YBUS_FM06P ENTRY_LPJE_CD YBUS_MMDLS

DLS-Urging/Reminder

LPMA EL 2 YBUS_FM06P ENTRY_LPMA YBUS_MMDLS

Goods Receipt Slip1




© SAP AG of 30






Goods Issue Slip1


Goods Issue Slip 2


Goods Issue Slip3


Service EntrySheet

NEU ES 2 YBUS_MMSER ENTRY_NEW YBUS_MMSER

GR Prod. Ord. Vers.1

WF01 ME 1 YBUS_M07DR ENTRY_WF01 YBUS_MMGR1

GR Prod. Ord. Vers.2

WF02 ME 1 YBUS_M07DR ENTRY_WF02 YBUS_MMGR2

Invoice Verification

REKL MR 1 RM08NAST ENTRY_REKL YBUS_MM_MR_REKL

3.1.8.3 Assign Forms (Layout Sets) for Print Reports

UseProcess these activities to configure the MM SAPScript Forms.


IMG Menu Materials Management → Inventory Management and Physical Inventory → Print Control → Assign Forms (Layout Sets) for Print Reports

Transaction Code

OMBU

2. On the ”Change View: Layout Set Versions: Overview” screen select the line with the following entry:

Report Report Title Version P Act

RM07IDRU Print Physical Inventory Document EA 4 X

3. Choose Details.

4. On the Change View: Layout Set Versions: Details screen, make the following entry:

Form

YBUS_INVENT


© SAP AG of 30


3.1.8.4 Assigning Form for Picking List

UseProcess these activities to assign the form for the picking list.

For more information, see SAP note 145136.

ProcedureCarry out the following steps:

1. Access the activity using one of the following navigation options:

IMG Menu none

Transaction Code V/53

2. On the Determine Work Area: Entry screen make the following entries:

Output Type Application

EK00 V4

3. Choose Continue (Enter).

4. On the Change View “Processing Routines”: Details screen make the following entries:

Processing 1

Program Form Routine Form

RVADEK01 ENTRY YBUS_SD_PICK_SIN


3.1.9 Assign FI Forms and Text Modules

3.1.9.1 Dunning Form

3.1.9.1.1 Assign Forms for Interest Indicators

UseIn this step, you can specify which form is to be used for the letter on interest on arrears or account balance interest for each interest indicator. The forms defined here are used if no other form is specified when calculating interest.


IMG Menu

Financial Accounting (new)→ Accounts Receivable and Accounts Payable → Business Transactions → Interest Calculation → Print → Assign Forms for Interest Indicators

© SAP AG of 30


IMG Activity

V_T056D (SM30)

2. On the ”Change View: Forms for Interest Calculation: Overview” screen choose ”New Entries”:

Int.ind. CoCd Form Type Form Name

01 <company code> SAPSCRIPT YBUS_F_DUZI_01


3.1.9.1.2 Form selection f. legal dunning proceed

UseIn this step, you can specify reference data for the dunning procedure.


IMG Menu

Financial Accounting (New) Accounts Receivable and Accounts Payable Business Transactions Business Transactions Dunning Dunning Procedure Define Dunning Procedures

IMG Activity

FBMP

2. On the Maintain Dunning Procedure: List screen, choose procedure 0001.

3. On the Maintain Dunning Procedure: Overview screen, make the following entries


Ref. Dunning Procedure for texts 0001

4. Select back.

5. On the Maintain Dunning Procedure: List screen, choose procedure YB30.

6. On the Maintain Dunning Procedure: Overview screen, make the following entries


Ref. Dunning Procedure for texts YB30

7. Save your entries.

3.1.9.1.3 Def. Dunning Proc. - Form selection f. dunning notices

UseIn this step, you can specify the form selection for the dunning procedure.

Procedure

© SAP AG of 30



IMG Menu

Financial Accounting (New) Accounts Receivable and Accounts Payable Business Transactions Business Transactions Dunning Dunning Procedure Define Dunning Procedures

IMG Activity

FBMP

2. On the Maintain Dunning Procedure: List screen, choose procedure 0001.

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

4. On the dialog box, choose company code 1000.

5. Choose Continue.

6. On the Maintain Dunning Procedure: Dunning texts screen, make the following entries

Normal dunning procedure Form

1 YBUS_FIMA

2 YBUS_FIMA

3 YBUS_FIMA

4 YBUS_FIMA

7. Choose Back twice.

8. On the Maintain Dunning Procedure: List screen, choose procedure YB30.

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

10. On the dialog box, choose company code 1000.

11. Choose Continue.

12. On the Maintain Dunning Procedure: Dunning texts screen, make the following entries

Normal dunning procedure Form

1 YBUS_FIMA


3.1.9.1.4 Define Sender Details for Dunning Forms

UseProcess this activity to assign the text modules used for dunning notices / interest calculations to your company code.


IMG Menu

Financial Accounting Accounts Receivable and accounts payable Business Transactions Dunning Printout Define Sender Details for Dunning Forms

© SAP AG of 30


IMG Activity

V_T047I (SM30)

2. On the ”Determine Work Area: Entry” screen enter the company code and choose Enter.


SF Header Text SF Footer SF Sender SF Greeting Text

YBUS_HEAD1 YBUS_FOOTER YBUS_ADR1 YBUS _GRUSS


3.1.9.2 Define Form Names for Correspondence Print

UseIn this activity, you define the names of the forms that are used for printing the correspondence in FI (SAPScript Forms).


IMG Menu

Financial Accounting → Financial Accounting Global Settings → Correspondence → SAPscript-Based Forms → Define Form Names for Correspondence Print

IMG Activity

V_001F_B (SM30)

2. On the ”Change View: Forms for Correspondence” screen choose ”New Entries”:

CoCd Program Fo.ID Form

1000 RFKORD00 YBUS_F140_PCNF1

1000 RFKORD10 YBUS_F140_ACC01

1000 RFKORD30 YBUS_F140_DOC1

1000 RFKORD40 YBUS_F140_TXT_1

1000 RFKORD80 YBUS_F140_CASH1

1000 SAPF130D YBUS_F130_CNFM1

1000 SAPF130D ER YBUS_F130_ER2

1000 SAPF130D LI YBUS_F130_LST2

1000 SAPF130D RE YBUS_F130_RSLT2

1000 SAPF130K YBUS_F130_CNFM1

1000 SAPF130K ER YBUS_F130_ER2

1000 SAPF130K LI YBUS_F130_LST2

1000 SAPF130K RE YBUS_F130_RSLT2

© SAP AG of 30


CoCd Program Fo.ID Form


3.1.9.3 Define Form Check Deposit

UseIn this step you specify a form for the check deposit list.


IMG Menu Financial Accounting (New) Bank Accounting Business Transactions Check Deposit Define Forms

IMG Activity

OT54

2. On the Change View ”Manual Check Deposit Firms”: Overview screen, make the following entries


SAPscript Form YBUS_F_M40S_CHE


3.1.9.4 Set Up Paying Company Codes for Payment Transactions – Forms

UseIn this activity, you make the Forms and sender details for advice notes and EDI accompanying sheets If you wish to print payment advice notes or an EDI accompanying sheet, specify the form name. Specify also the SAPscript text modules that contain details about the sender that are to be printed on the payment advice note. You can go directly from this transaction to the transactionfor editing forms and text modules.


IMG Menu

Financial Accounting (New) Accounts Receivable and Accounts Payable Business Transactions Outgoing Payments Automatic Outgoing

© SAP AG of 30


Payments Payment Method/Bank Selection for Payment Program Set UpPaying Company Codes for Payment Transactions

IMG Activity

SPRO

2. On the Change View ”Paying Company Codes”: Overview screen, select Company Code 1000.

3. On the Change View “Paying Company Codes”: Details screen, choose Forms and make thefollowing entries:

Field name Form User action and values

Form for the Payment Advice SAPscript YBUS_F110_D_AVIS

EDI accompanying sheet form SAPscript ADRS_HEADER

4. On the Change View ”Paying Company Codes”: Details screen, select Sender Details and make the following entries


Text ID ADRS

Letter header ADRS_HEADER

Footer ADRS_FOOTER

Signature text ADRS_SIGNATURE

Sender ADRS_SENDER


3.1.9.5 Set Up Payment Methods per Company Code for Payment Transact – Forms

UseIn this activity, you make the Forms and sender details for advice notes and EDI accompanying sheets If you wish to print payment advice notes or an EDI accompanying sheet, specify the form name. Specify also the SAPscript text modules that contain details about the sender that are to be printed on the payment advice note. You can go directly from this transaction to the transactionfor editing forms and text modules.


IMG Menu

Financial Accounting (New) Accounts Receivable and Accounts Payable Business Transactions Outgoing Payments Automatic Outgoing Payments Payment Method/Bank Selection for Payment Program Set Up Payment Methods per Company Code for Payment Transactions

IMG Activity

SPRO

© SAP AG of 30


2. On the Change View ”Maintenance of Company Code Data for a Payment Method”: Overview screen, select Company Code 1000 and Payment Method 1.

3. On the Change View ”Maintenance of Company Code Data for a Payment Method”:D screen,select Form Data and make the following entries


Form the Payment Medium YBUS_CHK_U

4. Choose Back.




Form the Payment Medium YBUS_CHK_N

Next form YBUS_REMIT

7. Choose Back.





10. Choose Back.





Next form YBUS_REMIT

13. Choose Back.

14. On the Change View ”Maintenance of Company Code Data for a Payment Method”:I screen, select Form Data and make the following entries


Next Form F110_US_AVIS

© SAP AG of 30


15. Choose Back.

16.

17. On the Change View ”Maintenance of Company Code Data for a Payment Method”: Overview screen, select Company Code 1000 and Payment Method Z.



Form the Payment Medium YBUS_REMIT

Next form F110_US_DTA


3.1.9.6 Define Sender Details for Correspondence Form

UseIn this activity, you define which texts are to be used in the letter window and the signature line foreach company code. This applies to the following:

letter header

letter footer

sender address


IMG Menu

Financial Accounting (New) General Ledger Accounting (New) Business Transactions Correspondence: Internal Document Make and Check Settings for Correspondence Define Sender Details for Correspondence Form

IMG Activity

SPRO

2. On the Change View ”Sender Details For Correspondence””: Overview screen, select New Entries.

3. On the New Entries: Details of Added Entries screen, make the following entries


Company Code 1000

Program Name RFKORD00

Text-ID ADRS

Standard Texts

Header Text

ADRS_HEADER

Standard Texts

Footer text

ADRS_FOOTER

© SAP AG of 30



Standard Texts

Signature text

ADRS_SIGNATURE

Sender ADRS_SENDER


3.1.10 Assigning QM Forms

UseProcess these activities to configure the QM Smart Forms.

ProcedureCarry out the following steps:


IMG Activity OID1

2. On the Determine Work Area: Entry screen enter “N” (Notifications (PM/QM) in the field Application Area.

3. Choose Enter.

On the Change View “Shop Papers”: Overview screen select the following papers, choose Details(Ctr. + Shift + F2) and make the following entries:

Shop Paper

Output Program Form Routine Form Description Archive obj.ID

1010 RIPRAT00 PRINT_PAPER YB_QM_PM_COMMON Activity Report

PMONOTFPAP

1020 RIPRBD00 PRINT_PAPER YB_QM_PM_COMMON Breakdown Report

PMONOTFPAP

1030 RIPROV00 PRINT_PAPER YB_QM_PM_COMMON Notification Overview

PMONOTFPAP

1500 RIPRSN00 PRINT_PAPER YB_QM_PM_COMMON Service Notification

PMOSERVPAP

5999 YBUS_RQQMRB01 PRINT_PAPER YBUS_QMCOM Rejection Report

QMOLETTER1

4. Choose Save.


IMG Activity OID1

6. On the Determine Work Area: Entry screen enter “O” (Maintenance Orders) in the field Application Area.

7. Choose Enter.

© SAP AG of 30


8. On the Change View “Shop Papers”: Overview screen select the following papers, choose Details (Ctr. + Shift + F2) and make the following entries:

Shop Paper

Output Program

Form Routine Form Description Archive obj.ID

2010 RIPRCT00PRINT_PAPER YB_QM_PM_COMMON Operation

Control TicketPMOWORKPAP

2020 RIPRGI00PRINT_PAPER YB_QM_PM_COMMON Material Issue

SlipPMOWORKPAP

2030 RIPRJT00 PRINT_PAPER YB_QM_PM_COMMON Job Ticket PMOWORKPAP

2040 RIPRMP00 PRINT_PAPER YB_QM_PM_COMMON Pick List PMOWORKPAP

2060 RIPRTT00 PRINT_PAPER YB_QM_PM_COMMON Time Ticket PMOWORKPAP

2062 RIPRTTS0PRINT_PAPER YB_QM_PM_COMMON Time Ticket for

Split RecordsPMOWORKPAP

2070 RIPRCS00PRINT_PAPER YB_QM_PM_COMMON Completion

Confirmation Slip

PMOWORKPAP

2072 RIPRCSS0PRINT_PAPER YB_QM_PM_COMMON Compl.Conf.Slip

for Split RecsPMOWORKPAP

9. Choose Save.

© SAP AG of 30

printing: forms (153) -...

Documents