153_BB_ConfigGuide_EN_PT
Comments
Description
EHP3 for SAP ERP 6.0 September 2009 English Printing: Forms (153) Building Block Configuration Guide SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany SAP Best Practices Printing: Forms (153): Configuration Guide Copyright © Copyright 2009 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 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 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 Page 2 of 28 SAP Best Practices Printing: Forms (153): Configuration Guide © SAP AG Page 3 of 28 . and individual key words of a programming language. screen titles. source code. function keys (such as F2) or the ENTER key. transaction codes. upgrade and database tools. names of variables and parameters as well as names of installation. when surrounded by body text. titles of graphics and tables.SAP Best Practices Printing: Forms (153): Configuration Guide Icons Icon Meaning Caution Example Note Recommendation Syntax Typographic Conventions Type Style Example text Description Words or characters that appear on the screen. for example. Exact user entry. for example. Screen output. Keys on the keyboard. These include field names. Variable user entry. This includes file and directory names and their paths. program names. table names. pushbuttons as well as menu names. SELECT and INCLUDE. These are words or characters that you enter in the system exactly as they appear in the documentation. These include report names. Example text EXAMPLE TEXT Example text <Example text> © SAP AG Page 4 of 28 . Pointed brackets indicate that you replace these words and characters with appropriate entries. paths and options. Names of elements in the system. Example text EXAMPLE TEXT Emphasized words or phrases in body text. messages. Cross-references to other documentation. .....2 Assigning MM Forms........1.......9.......1............................27 © SAP AG Page 5 of 28 ....1 Assigning Forms for Interest Indicators.......1....10 Assigning QM Forms...........................21 3............9..........................24 3.1....................9..1.1................9.............5 Setting Up Payment Methods per Company Code for Payment Transact – Forms.6 Define Sender Details for Correspondence Form..13 3..3 Defining Dunning Procedure ...................................1..... Letter Header and Footer Texts.......................................1..............................................3 Assigning Forms (Layout Sets) for Print Reports................6 2...1 Activating Smart Forms.1 Dunning Form..................................5 Copying Print Programs into Customer Namespace.................................................................................................14 3...1............................................................1................................1...................................................................1................1......................................22 3...........................................SAP Best Practices Printing: Forms (153): Configuration Guide Content 1 Purpose.................................................................12 3.........................1..........................26 3.........................1...16 3................................1............................12 3...............13 3....24 3....20 3....................4 Assigning Form for Picking List.................................................1.1 Activating Print Programs............................Form Selection for Dunning Notices..................1.21 3........1.....................6 3....................19 3....................................................................................................................................................1...............................................2 Assigning Text Modules to Sales Organization......................................................6 Using and Assigning Text Modules..................................6 3 Configuration....2 Defining Form Names for Correspondence Print...........15 3.7 3..................................................1.............................................1 Styles & Text Modules....1....23 3........21 3.......1........7 3........9.........6 3...9................................21 3........8 Assigning SD and MM Forms...................1 Prerequisites.......................1...............11 3....................8.....1........................................9........1...........................14 3...7 Assigning Standard Texts for Invoice Verification Forms............................4 Defining Sender Details for Dunning Forms...................................1 Copying Styles for SMART FORMS into Customer Namespace..9 Assigning FI Forms and Text Modules........3 Defining Form Check Deposit..............8.....................1................................1........................................1......5........................23 3..................................................1 Using Text Modules for Sender.................1...............10 3.....1.................3 Copying SAPscript Forms from Client 000..4 Setting Up Paying Company Codes for Payment Transactions – Forms......9..8.....1....13 3.....................2 Copying Text Modules into Customer Namespace.......6........1..3 Assigning Text Modules to Purchasing Organization............6....6 3............................2 Form selection for Legal Dunning Procedure...........6.......................4.15 3............25 3.........9..................9.....6 2 Preparation..............................4 Copying Smart Forms into Customer Namespace.........................................1 Assigning SD Forms........8.................... This document can be found on the SAP Best Practices documentation DVD in the folder . the placeholder [xx] depends on the SAP Best Practices version you use.xls.1. On the SAP Smart Forms: Initial Screen choose Style and then choose Copy (Ctrl + F5). 2 Preparation 2. Copying Styles for SMART FORMS into Customer Namespace Procedure Carry out the following steps: 1. see the building block prerequisite matrix (Prerequisites_Matrix_[xx]_EN_DE.\BBLibrary\Documentation\. In Target Object.1 Use Process this activity to make sure that the used styles are copied into your customer namespace.SAP Best Practices Printing: Forms (153): Configuration Guide Printing Forms 1 Purpose This configuration guide provides the information you need to set up the configuration of this building block manually. activate building block 153 in the Installation Assistant. 3 Configuration 3. In Source Object. 4. For more information. BL refers to the SAP Best Practices Baseline Package: Prerequisites_Matrix_BL_EN_DE. enter the name of the style you want to copy. Source Object /SMBA0/AA_BL_SF /SMBA0/AA_SFSTYLE 5.1 Prerequisites Before you start installing this building block. If you do not want to configure manually and prefer an automated installation process using eCATT and other tools.1 Styles & Text Modules 3. enter the new name in your customer namespace. you must install prerequisite building blocks. e. Access the activity using one of the following navigation options: IMG Menu Transaction Code Tools Form Printout Smartforms SMARTFORMS 2. 3. Target Object YBPT_BL_SF YBPT_SFSTYLE © SAP AG Page 6 of 28 .xls). Save the new Style..g. Target Object YBPT_ADR1 YBPT_HEAD1 YBPT_FOOTER YBPT_FOOTER1 YBPT_FOOTER2 YBPT_FOOTER3 YBPT_FOOTER4 YBPT_GRUSS YBPT_ADR_SENDER YBPT_BILL_TO YBPT_PAGE_INFORMATION YBPT_SENDER YBPT_TEL_SENDER YBPT_FAX_SENDER YBPT_MAIL_SENDER YBPT_QMCON_BEGIN1 YBPT_QMCON_BEGIN2 YBPT_QMCON_END 3.2 Use Copying Text Modules into Customer Namespace Process this activity to make sure that the used text modules are copied into your customer namespace. Source Object /SMB79/PT_ADR1 /SMB79/PT_HEAD1 /SMB79/PT_FOOTER /SMB79/PT_FOOTER1 /SMB79/PT_FOOTER2 /SMB79/PT_FOOTER3 /SMB79/PT_FOOTER4 /SMB79/PT_GRUSS /SMB79/PT_ADR_SENDER /SMB79/PT_BILL_TO /SMB79/PT_PAGE_INFORMATION /SMB79/PT_SENDER /SMB79/PT_TEL_SENDER /SMB79/PT_FAX_SENDER /SMB79/PT_MAIL_SENDER /SMB79/PT_QMCON_BEGIN1 /SMB79/PT_QMCON_BEGIN2 /SMB79/PT_QMCON_END 5. 4. In Source Object.1. Procedure Carry out the following steps: 1.1. In Target Object.3 Copying SAPscript Forms from Client 000 Use © SAP AG Page 7 of 28 . On the SAP Smart Forms: Initial Screen choose Text Module and then choose Copy (Ctrl + F5). Access the activity using one of the following navigation options: IMG Menu Transaction Code Tools Form Printout Smartforms SMARTFORMS 2. 3. enter the new name in your customer namespace. enter the name of the text module you want to copy.SAP Best Practices Printing: Forms (153): Configuration Guide 3. Save the new Text Module. On Copy Forms Between Clients screen.SAP Best Practices Printing: Forms (153): Configuration Guide The purpose of this activity is to copy the following SAPscript forms from client 000 into the customer namespace YB_* in your installation client: • • • • • • • • • • • • • • • • • • • • • • • • • • • • /SMB15/AA_LVSTAE /SMB15/AA_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 FIAA_F001 /SMB15/YBAA_QMIN Note that if you have already installed this building block in another client in your system. choose Execute (F8) from the application bar. you must remove the objects from the transport request in the other client (transaction SE09) before you can carry out this step. 4. This means that the forms are locked for change in the current implementation client and an error will occur. Access the activity using one of the following navigation options: IMG Menu Transaction Code System Services Reporting SA38 2. Procedure Carry out the following steps: 1. enter the following data: © SAP AG Page 8 of 28 . In this case. enter the following data: Field name Program Description User action and values RSTXFCPY Comment 3. On the ABAP: Program Execution screen. On the ABAP: Program Execution screen. the forms will already be included in a transport request. 7. enter in the field Package the value of your required package (for example: Z001) and create a new workbench request if required.SAP Best Practices Form Name Source Client 000 Printing: Forms (153): Configuration Guide Target Form Original Language Only Deselect Flow Trace Select /SMB15/AA_LVSTAE 5. YB_LVSTAEINZEL 6. Choose Execute (F8). Repeat steps 1 to 9 for the following forms: Form Name Source Client 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 Target Form Original Language Only Deselect Deselect Deselect Deselect Deselect Deselect Deselect Deselect Deselect Deselect Deselect Deselect Deselect Deselect Deselect Deselect Deselect Deselect Deselect Deselect Deselect Deselect Deselect Deselect Deselect Deselect Deselect Deselect Deselect Flow Trace Select Select Select Select Select Select Select Select Select Select Select Select Select Select Select Select Select Select Select Select Select Select Select Select Select Select Select Select Select /SMB15/AA_LVSTAE /SMB15/AA_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_01 F130_ERROR_02 F110_D_AVIS SD-CAS-MAIL SD_EXPORT_FECO SD_EXPORT_EUDC /SMB15/YBAA_QMIN FIAA_F001 YB_LVSTAEINZEL YB_LVSTALISTE YB_LVSTOSOLO YB_LVSKOMMIL1 YB_LVSKOMMIL2 YB_F_M40S_CHEQUE YB_F140_ACC_STAT YB_F140_CASH_DOC YB_F_DUZI_01 YB_PAY_DE_DTAUS0 YB_PAY_DE_DTAZV YB_F110_D_SCHECK YB_F110_EDI_01 YB_F140_IND_TEXT YB_F140_INT_DOCU YB_F140_PAY_CONF YB_F130_LIST_02 YB_F130_RESULT02 YB_INVENT YB_SD_PICK_SINGL YB_F110_D_UEBERW YB_F130_CONFIRM YB_F130_ERROR_02 YB_F110_D_AVIS YB_SD-CAS-MAIL YB_EXPORT_FECO YB_EXPORT_EUDC YB_QM_INSP_RESUL YB_FIAA_F001 © SAP AG Page 9 of 28 . Choose Back (F3). 8. On the Create Object Directory Entry screen. 4.1. 3.4 Copying Smart Forms into Customer Namespace Use Process this activity to make sure that the smart forms are copied into your customer namespace. choose Copy (Ctrl + F5). Access the activity using one of the following navigation options: IMG Menu Transaction Code Tools Form Printout Smartforms SMARTFORMS 2. On the SAP Smart Forms: Initial Screen. In Target Object.Agr. 3. Procedure Carry out the following steps: 1.SAP Best Practices Form Name Source Client 000 Printing: Forms (153): Configuration Guide Target Form Original Language Only Deselect Flow Trace Select QM_COMPLAIN YBAA_QMCOM Result The SAPscript forms are copied from client 000. enter the new name in your customer namespace. enter the name of the smart form you want to copy.Outl. In Source Object. Source Object Sales /SMB79/PT_SDINQ /SMB79/PT_SDQUO /SMB79/PT_SDORC /SMB79/PT_SDCSH /SMB79/PT_SDCON /SMB79/PT_SDSDA Shipping /SMB79/PT_SDDLN /SMB79/PT_SDBLD Billing /SMB79/PT_SDINV Purchasing RFQ /SMB79/PT_MMRFQ Purchase Order /SMB79/PT_MMPO Purch. YBPT_MMPO YBPT_MMRFQ YBPT_SDINV YBPT_SDDLN YBPT_SDBLD YBPT_SDINQ YBPT_SDQUO YBPT_SDORC YBPT_SDCSH YBPT_SDCON YBPT_SDSDA Target Object © SAP AG Page 10 of 28 . Choose Change. choose Activate. 4. Save the new smart forms as Active version. Check if SAP Smart Forms has the Active status (information to the right of name of the form). Procedure Carry out the following steps: 1. 3.SchAgrRelease /SMB79/PT_MMDLS Inventory Management /SMB79/PT_MMGR1 /SMB79/PT_MMGR2 /SMB79/PT_MMGR3 /SMB79/PT_MMGI1 /SMB79/PT_MMGI2 /SMB79/PT_MMGI3 FI /SMB79/PT_FIMA PP /SMB79/PT_PROD_ORD Service Entry /SMB79/PT_MMSER Quality Management /SMB79/PT_QMCOM Printing: Forms (153): Configuration Guide Target Object YBPT_MMCON YBPT_MMDLS YBPT_MMGR1 YBPT_MMGR2 YBPT_MMGR3 YBPT_MMGI1 YBPT_MMGI2 YBPT_MMGI3 YBPT_FIMA YBPT_PROD_ORD YBPT_MMSER YBPT_QMCOM 5. If not. On the SAP Smart Forms: Initial Screen. enter your new smart form (see list above).4. 6. 5.1. (match). © SAP AG Page 11 of 28 .1 Use Activating Smart Forms Process this activity to make sure that the smart forms are active. you will be asked to enter a Workbench Request. Access the activity using one of the following navigation options: IMG Menu Transaction Code Tools Form Printout Smartforms SMARTFORMS 2. During Smart Form Activation. Result The smart forms are activated. Go back to continue the configuration. 3.SAP Best Practices Source Object /SMB79/PT_MMCON Purch. 5 Copying Print Programs into Customer Namespace Use Process this activity to make sure that the smart form print programs are copied into your customer namespace. Source Program /SMBA0/AA_RVADOR01 /SMBA0/AA_RLE_DELNOTE /SMBA0/AA_RLB_INVOICE /SMBA0/AA_FM06P /SMBA0/AA_M07DR /SMBA0/AA_SFCOPCT_SFORM /SMBA0/AA_MMSER /SMBA0/AA_LVSTAE /SMBA0/AA_RQQMRB01 Target Program YBPT_RVADOR01 YBPT_RLE_DELNOTE YBPT_RLB_INVOICE YBPT_FM06P YBPT_M07DR YBPT_SFCOPCT_SFORM YBPT_MMSER YBPT_LVSTAE YBPT_RQQMRB01 3. 4.5. 4. Choose Copy (Ctrl + F5). Access the activity using one of the following navigation options: Transaction Code SE38 2. Print Program YBPT_RVADOR01 © SAP AG Page 12 of 28 . choose Select all and then choose Continue. 3. Choose Match (Shift + F9). In the target program.1.1.SAP Best Practices Printing: Forms (153): Configuration Guide 3. Procedure Carry out the following steps: 1. Procedure Carry out the following steps: 1. enter the name of the new program. 3. On the ABAP Editor: Initial Screen enter the source program. If a dialog box occurs. Access the activity using one of the following navigation options: IMG Menu Transaction Code System → Services → Reporting SA38 2.1 Use Activating Print Programs Process this activity to make sure that the Print Programs are active. 5. Repeat the step for the following Print Programs. On the ABAP Editor: Initial Screen enter the Print Program. 6.1.SAP Best Practices YBPT_RLE_DELNOTE YBPT_RLB_INVOICE YBPT_FM06P YBPT_M07DR YBPT_SFCOPCT_SFORM YBPT_MMSER YBPT_LVSTAE YBPT_RQQMRB01 6. purchasing organization and company code. Four text areas are provided for the output of the footer texts. 1 . Access the activity using one of the following navigation options: IMG Menu Sales and Distribution → Basic Functions → Output Control → Output Determination → Process Output and Forms → Assign Form Texts → Assign form texts per sales organization © SAP AG Page 13 of 28 . the corresponding footer area will be empty. 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. Go back to continue the configuration. the final text module name is concatenated without the organizational unit (sales organization. 3. Therefore it is necessary to maintain only the prefix for the Smart Forms text modules.1 Using Text Modules for Sender. company code). Procedure Carry out the following steps: 1.6 Using and Assigning Text Modules 3.1. purchasing organization. 3.6. Printing: Forms (153): Configuration Guide Result The Print Programs are activated. 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. (No.4).2 Use Assigning Text Modules to Sales Organization Process this activity to assign the text modules to your sales organization. Prefix + <1-4> Example: /SMBA0/AA_FOOTER2 • If no smart forms text module is found.1. choose New Entries. Access the activity using one of the following navigation options: IMG Menu IMG Activity 3. © SAP AG Page 14 of 28 . Materials Management → Logistics Invoice Verification → Message Determination → Define Sender Details for Forms OMRU On the Change View “Sender Texts for Invoice Verification Forms”: Overview screen. Access the activity using one of the following navigation options: IMG Menu Transaction Code 2. Select the purchasing organization and choose Details (Ctrl + Shift + F2).3 Use Assigning Text Modules to Purchasing Organization Process this activity to assign the text modules to your purchasing organization. Procedure Carry out the following steps: 1. Save your settings. Make the following entries: Sales Org. 3. YBPT_FOOTER YBPT_FOOTER Greeting text Text SDS sender 3. 3. Save your settings.6.1. On the New Entries: Details of Added Entries screen. Make the following entries: Text Sndr Line YBPT_ADR1 Letter heading YBPT_HEAD1 Text: footer YBPT_FOOTER Text: Close Materials Management → Purchasing → Messages → Texts for messages → Define Texts for Purchasing Organization V_024E_T (SM30) 2.7 Assigning Standard Texts for Invoice Verification Forms Use Process this activity to assign the text modules for invoice verification to your company code. 3. 1000 1100 Address Text YBPT_ADR1 YBPT_ADR1 V/85 Printing: Forms (153): Configuration Guide Letter header YBPT_HEAD1 YBPT_HEAD1 Footer text li. Procedure Carry out the following steps: 1. enter the values shown below. 4.SAP Best Practices Transaction Code 2.1. 1. On the Conditions for output type screen.g. 7. Description Printing: Forms (153): Configuration Guide User action and values e. 5. On the Display View “Output type”: Overview screen. Assigning SD Forms Procedure Carry out the following steps: 1.8. Access the activity using one of the following navigation options: Transaction Code NACE 2. 4.SAP Best Practices Field name Company Code Text ID Header Text Footer Text Signature Text Sender 4. 1000 ADRS ADRS_HEADER ADRS_FOOTER ADRS_SIGNATURE ADRS_SENDER Comment 3.1 Use Process these activities to configure the SD Smart Forms. Choose Back (F3). Save your settings. Choose New Entries and enter the following data: Output Type Application Medium Program Form routine SmartForm 6. select the application type (for example V1 for Sales) in the application column and choose Output types (F5).6 for the documents specified below: AN00 V1 1 (Print output) YBPT_RVADOR01 ENTRY YBPT_SDQUO © SAP AG Page 15 of 28 .1. 5. Choose the output type (for example AF00 for Inquiry) and double-click on processing routines in the left frame Dialog structure.8 Assigning SD and MM Forms 3. Repeat procedure 4 . choose the Change mode to change the configuration. 3. Save your settings. 8. of Origin FECO EU Result After processing these steps the SD Smart Forms configuration is set up in your system. 3.2 Use Assigning MM Forms Process these activities to configure the MM Smart Form. Procedure Carry out the following steps: © SAP AG Page 16 of 28 .1.SAP Best Practices Printing: Forms (153): Configuration Guide Description Quotation Order confirmation Cash Sale Contract Scheduling Agreement Output Applic Mediu Program Type ation m AN00 BA00 RD03 KO00 LP00 V1 V1 V1 V1 V1 V2 V2 V3 V1 V1 V1 V1 V1 V2 V2 V3 K1 V3 V3 1 1 1 1 1 1 1 1 2 2 2 2 2 2 2 2 1 1 1 YBPT_RVADOR01 YBPT_RVADOR01 YBPT_RVADOR01 YBPT_RVADOR01 YBPT_RVADOR01 YBPT_RLE_DELNOTE YBPT_RLE_DELNOTE YBPT_RLB_INVOICE YBPT_RVADOR01 YBPT_RVADOR01 YBPT_RVADOR01 YBPT_RVADOR01 YBPT_RVADOR01 YBPT_RLE_DELNOTE YBPT_RLE_DELNOTE YBPT_RLB_INVOICE RVCASM01 RVADAUS1 RVADAUS1 Form routine ENTRY ENTRY ENTRY ENTRY ENTRY ENTRY ENTRY ENTRY ENTRY ENTRY ENTRY ENTRY ENTRY ENTRY ENTRY ENTRY ENTRY Smart Form / Form YBPT_SDQUO YBPT_SDORC YBPT_SDCSH YBPT_SDCON YBPT_SDSDA YBPT_SDDLN YBPT_SDBLD YBPT_SDINV YBPT_SDQUO YBPT_SDORC YBPT_SDCSH YBPT_SDCON YBPT_SDSDA YBPT_SDDLN YBPT_SDBLD YBPT_SDINV YB_SD-CASMAIL (Form) Delivery Note LD00 Bill of Lading YBL1 Sales Invoice RD00 Quotation Order confirmation Cash Sale Contract Scheduling Agreement AN00 BA00 RD03 KO00 LP00 Delivery Note LD00 Bill of Lading YBL1 Sales Invoice RD00 Direct Mailing MAAK Export Declaration FEEX ENTRY_F YB_EXPORT_E EEX UDC ENTRY_F YB_EXPORT_F ECO ECO Cert. choose the Change mode to change the configuration.6 for the documents specified below: Description Outpu t Type NEU MAHN ABSA NEU MAHN AUFB NEU Appli catio n EA EA EA EF EF EF EV Medi um 1 1 1 1 1 1 1 Program Form routine Smart Form / Form YBPT_MMRFQ YBPT_MMRFQ YBPT_MMRFQ YBPT_MMPO YBPT_MMPO YBPT_MMPO YBPT_MMCON NEU EA 1 (Print output) YBPT_FM06P ENTRY_NEU YBPT_MMRFQ RFQ RFQ-Urging/ Reminder RFQ-Quo rejection PO PO-Urging /Reminder PO-Ack. 4. Access the activity using one of the following navigation options: Transaction Code NACE 2. Repeat procedure 4 . Expediter Contract (Scheduling Agreement) Contract(SA)Ack. Choose New Entries and type the following data: Output Type Application Medium Program Form routine SmartForm 6. 7. Expediter Delivery Schedule YBPT_FM06P YBPT_FM06P YBPT_FM06P YBPT_FM06P YBPT_FM06P YBPT_FM06P YBPT_FM06P ENTRY_NEU ENTRY_MAHN ENTRY_ABSA ENTRY_NEU ENTRY_MAHN ENTRY_AUFB ENTRY_NEU AUFB EV 1 YBPT_FM06P ENTRY_AUFB YBPT_MMCON LPET EL 1 YBPT_FM06P ENTRY_LPET YBPT_MMDLS © SAP AG Page 17 of 28 .SAP Best Practices Printing: Forms (153): Configuration Guide 1. Choose the output type (for example NEU for RFQ) and double-click on processing routines in the left frame Dialog structure 5. On the Conditions for output type screen. Save your settings. select the application type (for example EA for Purchasing RFQ) in the application column and choose Output types (F5) 3. On the Display View “Output type”: Overview screen. SAP Best Practices Printing: Forms (153): Configuration Guide Description Outpu t Type LPH2 LPJ2 LPMA WE01 WE02 Appli catio n EL EL EL ME ME Medi um 1 1 1 1 1 Program Form routine Smart Form / Form YBPT_MMDLS YBPT_MMDLS YBPT_MMDLS YBPT_MMGR1 YBPT_MMGR2 DLSForecast DLS-JIT DLS-Urging/ Reminder Goods Receipt Slip1 Goods Receipt Slip 2 Goods Receipt Slip 3 Goods Issue Slip1 Goods Issue Slip 2 Goods Issue Slip3 Service Entry Sheet RFQ RFQ-Urging/ Reminder RFQ-Quo rejection PO PO-Urging /Reminder PO-Ack. Expediter Delivery YBPT_FM06P YBPT_FM06P YBPT_FM06P YBPT_M07DR YBPT_M07DR ENTRY_LPHE_ CD ENTRY_LPJE_ CD ENTRY_LPMA ENTRY_WE01 ENTRY_WE02 WE03 ME 1 YBPT_M07DR ENTRY_WE03 YBPT_MMGR3 WA01 WA02 WA03 NEU NEU MAHN ABSA NEU MAHN AUFB NEU ME ME ME ES EA EA EA EF EF EF EV 1 1 1 1 2 2 2 2 2 2 2 YBPT_M07DR YBPT_M07DR YBPT_M07DR YBPT_MMSER YBPT_FM06P YBPT_FM06P YBPT_FM06P YBPT_FM06P YBPT_FM06P YBPT_FM06P YBPT_FM06P ENTRY_WA01 ENTRY_WA02 ENTRY_WA03 ENTRY_NEW ENTRY_NEU ENTRY_MAHN ENTRY_ABSA ENTRY_NEU ENTRY_MAHN ENTRY_AUFB ENTRY_NEU YBPT_MMGI1 YBPT_MMGI2 YBPT_MMGI3 YBPT_MMSER YBPT_MMRFQ YBPT_MMRFQ YBPT_MMRFQ YBPT_MMPO YBPT_MMPO YBPT_MMPO YBPT_MMCON AUFB EV 2 YBPT_FM06P ENTRY_AUFB YBPT_MMCON LPET EL 2 YBPT_FM06P ENTRY_LPET YBPT_MMDLS © SAP AG Page 18 of 28 . Expediter Contract (Scheduling Agreement) Contract(SA)Ack. 8.SAP Best Practices Printing: Forms (153): Configuration Guide Description Outpu t Type Appli catio n Medi um Program Form routine Smart Form / Form Schedule DLSForecast DLS-JIT DLS-Urging/ Reminder Goods Receipt Slip1 Goods Receipt Slip 2 Goods Receipt Slip 3 Goods Issue Slip1 Goods Issue Slip 2 Goods Issue Slip3 Service Entry Sheet GR Prod. Procedure Carry out the following steps: 1.3 Use Assigning Forms (Layout Sets) for Print Reports Process these activities to configure the MM SAPScript Forms. Vers.2 LPH2 LPJ2 LPMA WE01 WE02 EL EL EL ME ME 2 2 2 2 2 YBPT_FM06P YBPT_FM06P YBPT_FM06P YBPT_M07DR YBPT_M07DR ENTRY_LPHE_ CD ENTRY_LPJE_ CD ENTRY_LPMA ENTRY_WE01 ENTRY_WE02 YBPT_MMDLS YBPT_MMDLS YBPT_MMDLS YBPT_MMGR1 YBPT_MMGR2 WE03 ME 2 YBPT_M07DR ENTRY_WE03 YBPT_MMGR3 WA01 WA02 WA03 NEU WF01 WF02 ME ME ME ES ME ME 2 2 2 2 1 1 YBPT_M07DR YBPT_M07DR YBPT_M07DR YBPT_MMSER YBPT_M07DR YBPT_M07DR ENTRY_WA01 ENTRY_WA02 ENTRY_WA03 ENTRY_NEW ENTRY_WF01 ENTRY_WF02 YBPT_MMGI1 YBPT_MMGI2 YBPT_MMGI3 YBPT_MMSER YBPT_MMGR1 YBPT_MMGR2 3. Ord. Access the activity using one of the following navigation options: IMG Menu Materials Management → Inventory Management and Physical Inventory → Print Control → Assign Forms (Layout Sets) for Print Reports © SAP AG Page 19 of 28 . Ord.1 GR Prod. Vers.1. On the Change View “Layout Set Versions”: Overview screen select the line with the following entry: Report RM07IDRU 3. Choose Details.4 Use Assigning Form for Picking List Process these activities to assign the form for the picking list. On the Change View “Processing Routines”: Details screen make the following entries: Processing 1 Program RVADEK01 5. 4. 4. On the Determine Work Area: Entry screen make the following entries: Output Type EK00 Application V4 3. Choose Continue (Enter). Report Title Print Physical Inventory Document Version EA P 4 Act X 3. Access the activity using one of the following navigation options: IMG Menu Transaction Code none V/53 2. Form Routine ENTRY Form YB_SD_PICK_SINGL © SAP AG Page 20 of 28 .1. Procedure Carry out the following steps: 1.8. On the Change View: Layout Set Versions: Details screen make the following entry: Form YB_INVENT 5.SAP Best Practices Transaction Code OMBU Printing: Forms (153): Configuration Guide 2. See also note 145136. Save your settings. Save your settings. The forms defined here are used.1.9. 01 3. make the following entries Field name Ref.1 3. Dunning Procedure for texts Description User action and values 0001 Comment © SAP AG Page 21 of 28 . Save your settings.1.1. Procedure Carry out the following steps: 1. you can specify which form is to be used for the letter on interest.2 Use Form selection for Legal Dunning Procedure In this step.1. On the Change View “Forms for Interest Calculation”: Overview screen choose New Entries: Int. on areas or account balance interest for each interest indicator.9 Assigning FI Forms and Text Modules 3. On the Maintain Dunning Procedure: Overview screen. Access the activity using one of the following navigation options: IMG Menu Financial Accounting (New) → Accounts Receivable and Accounts Payable → Business Transactions → Business Transactions → Dunning → Dunning Procedure → Define Dunning Procedures FBMP IMG Activity 2. 3.ind.9. if no other form is specified when calculating interest. On the Maintain Dunning Procedure: List screen.SAP Best Practices Printing: Forms (153): Configuration Guide 3.9.1. CoCd <company code> Form Type SAPSCRIPT Form Name YB_F_DUZI_01 3. you can specify reference data for the dunning procedure. Dunning Form Assigning Forms for Interest Indicators Procedure Carry out the following steps: 1.1.1 Use In this step. Access the activity using one of the following navigation options: IMG Menu Financial Accounting (new) → Accounts Receivable and Accounts Payable → Business Transactions → Interest Calculation → Print → Assign Forms for Interest Indicators V_T056D (SM30) IMG Activity 2. choose procedure 0001. Choose Back. you can specify the form selection for the dunning procedure. 10.1. On the pop-up. Choose Continue. 12. On the pop-up. Choose Back.3 Defining Dunning Procedure . choose procedure YB30. On the Maintain Dunning Procedure: Dunning texts screen. Save your entries. Choose Continue. make the following entries: Normal dunning procedure 1 2 3 4 7. On the Maintain Dunning Procedure: Dunning texts screen.9. 8. On the Maintain Dunning Procedure: List screen. On the Maintain Dunning Procedure: List screen. choose dunning texts. Access the activity using one of the following navigation options: IMG Menu Financial Accounting (New) → Accounts Receivable and Accounts Payable → Business Transactions → Business Transactions → Dunning → Dunning Procedure → Define Dunning Procedures FBMP IMG Activity 2.1.SAP Best Practices 4. 4. 3. On the Maintain Dunning Procedure: List screen. On the Maintain Dunning Procedure: Overview screen. choose procedure YB30. 5. 11. On the Maintain Dunning Procedure: Overview screen. Procedure Carry out the following steps: 1. choose procedure 0001. make the following entries: Field name Ref. 6. Printing: Forms (153): Configuration Guide 5. On the Maintain Dunning Procedure: Overview screen. 6. 9. Description User action and values YB30 Comment 3. choose dunning texts.Form Selection for Dunning Notices Use In this step. Dunning Procedure for texts 7. make the following entries: Normal dunning procedure 1 Form YBPT_FIMA Form YBPT_FIMA YBPT_FIMA YBPT_FIMA YBPT_FIMA © SAP AG Page 22 of 28 . choose company code 1000. choose company code 1000. SF Footer YBPT_FOOTER SF Sender YBPT_ADR1 SF Greeting Text YBPT_GRUSS 4. Make the following entries: SF Header Text YBPT_HEAD1 2.1. Access the activity using one of the following navigation options: IMG Menu Financial Accounting →Financial Accounting Global Settings → Correspondence → SAPscript-Based Forms → Define Form Names for Correspondence Print V_001F_B (SM30) IMG Activity 2.2 Use Defining Form Names for Correspondence Print In this activity.ID Form YB_F140_PAY_CONF YB_F140_ACC_STAT YB_F140_INT_DOCU YB_F140_IND_TEXT © SAP AG Page 23 of 28 . you define the names of the forms which are to be used for printing the correspondence in FI (SAPScript Forms). Save your entries. Procedure Carry out the following steps: 1.4 Use Defining Sender Details for Dunning Forms Process this activity to assign the text modules used for dunning notices / interest calculations to your company code.1.1. Save your settings. 3. Printing: Forms (153): Configuration Guide 3.9.9. On the Determine Work Area: Entry screen enter the company code and choose Enter.SAP Best Practices 13. Procedure Carry out the following steps: 1. Access the activity using one of the following navigation options: IMG Menu Financial Accounting → Accounts Receivable and accounts payable → Business Transactions → Dunning → Printout →Define Sender Details for Dunning Forms V_T047I (SM30) IMG Activity 3. On the Change View: Forms for Correspondence screen choose New Entries: CoCd 1000 1000 1000 1000 Program RFKORD00 RFKORD10 RFKORD30 RFKORD40 Fo. If you wish to print payment advice notes or an EDI accompanying sheet. You can go directly from this transaction to the transaction for editing forms and text modules. © SAP AG Page 24 of 28 .9. Program RFKORD80 SAPF130D SAPF130D SAPF130D SAPF130D SAPF130K SAPF130K SAPF130K SAPF130K Fo.3 Use Defining Form Check Deposit In this step you specify a form for the check deposit list.1. specify the form name.ID Form YB_F140_CASH_DOC YB_F130_CONFIRM ER LI RE YB_F130_ERROR_02 YB_F130_LIST_02 YB_F130_RESULT02 YB_F130_CONFIRM ER LI RE YB_F130_ERROR_02 YB_F130_LIST_02 YB_F130_RESULT02 3.SAP Best Practices Printing: Forms (153): Configuration Guide CoCd 1000 1000 1000 1000 1000 1000 1000 1000 1000 3.9. Procedure Carry out the following steps: 1. Specify also the SAPscript text modules that contain details about the sender that are to be printed on the payment advice note. Description User action and values YB_F_M40S_CHEQUE Comment 3. Save your settings. On the Change View “Manual Check Deposit Firms”: Overview screen. you make the forms and sender details for advice notes and EDI accompanying sheets.4 Use Setting Up Paying Company Codes for Payment Transactions – Forms In this activity. make the following entries Field name SAPscript Form 3. Access the activity using one of the following navigation options: IMG Menu IMG Activity Financial Accounting (New) → Bank Accounting → Business Transactions → Check Deposit → Define Forms OT54 2.1. Save your entries. Access the activity using one of the following navigation options: 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 © SAP AG Page 25 of 28 . Specify also the SAPscript text modules that contain details about the sender that are to be printed on the payment advice note. On the Change View “Paying Company Codes”: Overview screen. specify the form name.1. you make the forms and sender details for advice notes and EDI accompanying sheets. choose Sender Details and make the following entries: Field name Text ID Letter header Footer Signature text Sender 5. choose company code 1000. You can go directly from this transaction to the transaction for editing forms and text modules. 3.5 Use Setting Up Payment Methods per Company Code for Payment Transact – Forms In this activity.9. Description User action and values ADRS ADRS_HEADER ADRS_FOOTER ADRS_SIGNATURE ADRS_SENDER Note 3.SAP Best Practices Printing: Forms (153): Configuration Guide Procedure Carry out the following steps: 1. choose Forms and make the following entries: Field name Form for the Payment Advice EDI accompanying sheet form Form SAPscript SAPscript User action and values YB_F110_D_AVIS ADRS_HEADER 4. On the Change View “Paying Company Codes”: Details screen. If you wish to print payment advice notes or an EDI accompanying sheet. Access the activity using one of the following navigation options: 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 Paying Company Codes for Payment Transactions SPRO IMG Activity 2. Save your entries. On the Change View “Paying Company Codes”: Details screen. Procedure Carry out the following steps: 1. Access the activity using one of the following navigation options: IMG Menu Financial Accounting (New) → General Ledger Accounting © SAP AG Page 26 of 28 . choose company code 1000 and payment method E. choose company code 1000 and payment method O. 3. choose company code 1000 and payment method A.1. On the Change View “Maintenance of Company Code Data for a Payment Method”: Overview screen. Save your entries. Choose Back.6 Use Define Sender Details for Correspondence Form In this activity. choose Form Data and make the following entries: Field name Next form 10. 9. On the Change View “Maintenance of Company Code Data for a Payment Method”:D screen. 6.9. On the Change View “Maintenance of Company Code Data for a Payment Method”:D screen. 5. This applies to the following: • • • letter header letter footer sender address Procedure Carry out the following steps: 1.SAP Best Practices Printing: Forms (153): Configuration Guide Payment Methods per Company Code for Payment Transactions IMG Activity SPRO 2. Choose Back. 3. On the Change View “Maintenance of Company Code Data for a Payment Method”: Overview screen. On the Change View “Maintenance of Company Code Data for a Payment Method”: Overview screen. On the Change View “Maintenance of Company Code Data for a Payment Method”:D screen. choose Form Data and make the following entries: Field name Next form 4. choose Form Data and make the following entries: Field name Next form 7. you define which texts are to be used in the letter window and the signature line for each company code. Description User action and values YB_F110_D_SCHECK Comment Description User action and values YB_PAY_DE_DTAUS0 Comment Description User action and values YB_PAY_DE_DTAUS0 Comment 11. 8. Choose Back. + Shift + F2): Paper: 5999 (Rejection Report) 6. Save your entries. Access the activity using one of the following navigation options: IMG Activity OID1 2. 4.SAP Best Practices Printing: Forms (153): Configuration Guide (New) → Business Transactions → Correspondence: Internal Document → Make and Check Settings for Correspondence → Define Sender Details for Correspondence Form IMG Activity SPRO 2.10 Use Assigning QM Forms Process these activities to configure the QM Smart Forms. Choose Enter. On the Change View “Shop Papers”: Details screen make the following entries: Field name Output Program Form Routine Description User action and values YBPT_RQQMRB01 PRINT_PAPER Comment © SAP AG Page 27 of 28 . 5. make the following entries: Field name Company Code Program Name Text-ID Standard Texts Header Text Standard Texts Footer text Standard Texts Signature text Sender 4. select New Entries. On the Choose Activity screen select Assign Shop Papers to Notification Type. On the New Entries: Details of Added Entries screen. 3. On the Determine Work Area: Entry screen enter “N” (Notifications (PM/QM) in the field Application Area. On the Change View “Shop Papers”: Overview screen select the following paper and choose Details (Ctr. ADRS_SENDER ADRS_SIGNATURE ADRS_FOOTER Description User action and values 1000 RFKORD00 ADRS ADRS_HEADER Comment 3. 3.1. Procedure Carry out the following steps: 1. On the Change View “Sender Details For Correspondence”: Overview screen. ID 7. Choose Save.SAP Best Practices Field name Form Description Archive obj. Description Printing: Forms (153): Configuration Guide User action and values YBPT_QMCOM Rejection Report QMOLETTER1 Comment © SAP AG Page 28 of 28 .
Copyright © 2024 DOKUMEN.SITE Inc.