Printing Forms Adaptation Guide en CN
July 13, 2016 | Author: Sathish Kumar Dhoni | Category: N/A
Short Description
Printing Forms Adaptation Guide en CN...
Description
EHP7 for SAP ERP 6.0 April 2014 English
Printing: Adaptation Guide
SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany
Forms
SAP Best Practices
Printing: Forms adaptation guide
Copyright © 2014 SAP AG or an SAP affiliate company. 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. National product specifications may vary. 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 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. Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.
© SAP AG
Page 2 of
SAP Best Practices
Printing: Forms adaptation guide
Icons Icon
Meaning Caution Example Note Recommendation Syntax External Process Business Process Alternative/Decision Choice
Typographic Conventions Type Style
Description
Example text
Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options. Cross-references to other documentation.
Example text
Emphasized words or phrases in body text, titles of graphics and tables.
EXAMPLE TEXT
Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.
Example text
Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.
EXAMPLE TEXT
Keys on the keyboard, for example, function keys (such as 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.
Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.
© SAP AG
F2)
or the
Page 3 of
SAP Best Practices
Printing: Forms adaptation guide
Contents Printing: Forms Adaptation Guide.................................................................................................. 5 1
Purpose.................................................................................................................................. 5
2
Adaptation of forms objects.................................................................................................... 5
3
2.1
Adaptation of Text Modules............................................................................................. 5
2.2
Adaptation of Graphic...................................................................................................... 6
2.3
Adaptation of Standard Texts.......................................................................................... 7
Default Setting: Sending Forms via E-Mail.............................................................................8 3.1
Maintaining User Settings............................................................................................... 8
3.2
Specify Default Values per Output Type (Optional).........................................................9
3.3
Output Condition Records.............................................................................................10
3.3.1
Output Condition Records: Sales (BA00, KO00)....................................................10
3.3.2
Output Condition Records: Sales (AN00)...............................................................10
3.3.3
Output Condition Records: Shipping......................................................................11
3.3.4
Output Condition Records: Billing..........................................................................12
3.3.5
Output Condition Records: Entry Sheet.................................................................12
3.3.6
Output Condition Records: Scheduling Agreement Delivery Schedule..................13
3.3.7
Output Condition Records: Outline Agreement......................................................14
3.3.8
Output Condition Records: Purchase Order...........................................................14
3.3.9
Output Condition Records: Purchasing RFQ..........................................................15
3.4
4
Additional Settings in SD (optional)...............................................................................16
3.4.1
Defining Print Parameters Shipping (optional).......................................................16
3.4.2
Defining Print Parameters Sales Organization (optional).......................................16
3.5
Additional Customizing for Rejection Report in QM.......................................................17
3.6
Changing Master Data.................................................................................................. 17
3.6.1
Vendor Master Records..........................................................................................17
3.6.2
Customer Master Records.....................................................................................18
Defining Header, Sender, and Footer for Additional Organizational Units............................18 4.1
Text Modules................................................................................................................. 18
4.1.1
Automated Determination of Text Modules.............................................................18
4.1.2
Creating Additional Text Modules...........................................................................19
4.2
Standard Texts.............................................................................................................. 20
4.2.1
Creating Additional Standard Texts........................................................................21
4.2.2
Assigning Additional Standard Texts......................................................................22
4.2.3
Assigning Standard Texts for Invoice Verification Form..........................................22
© SAP AG
Page 4 of
SAP Best Practices
Printing: Forms adaptation guide
Printing: Forms Adaptation Guide 1 Purpose This document describes how different forms objects delivered with the SAP Best Practices Baseline Package can be adapted. You can also find a description on how to switch from paper print out to sending forms via e-mail as a default setting.
2 Adaptation of forms objects 2.1 Adaptation of Text Modules With the installation of Building Block 153 (Printing Forms), the listed text modules are copied from the source object to the target object in customer namespace. The copied objects contain the data delivered with the SAP Best Practices Baseline Package. To adapt this data (for example, company name, address) carry out the following steps: SAP ECC Menu
Tools Form Printout Smartforms
Transaction Code
SMARTFORMS
1. On the SAP Smart Forms: Initial Screen select Text Module and enter the text module you want to change. 2. Choose Change. 3. On the Change XXXX Text Module screen, choose the Text tab. 4. Change the entries as required. 5. Save your entries.
All text modules are delivered in original language English. To change the text modules in additional languages, translate the changed texts as described below. 1. Access the transaction choosing one of the following navigation options: SAP ECC Menu
Tools ABAP Workbench Utilities Translation Short and Long Texts
Transaction Code
SE63
2. Choose Translation ABAP Objects Other Long Texts. 3. On the Object Type Selection screen, choose FS Forms and Styles SSF SAP Smart Form. 4. On the Other Long Texts: SAP Smart Form screen, enter the object name, choose EN as Source Language and choose the required Target language. 5. Choose Edit. 6. On the SSF (..) Form EN To XX: ... screen, make the necessary translations. 7. Choose Save Active. Source Object
Target Object
Content
/SMBA0/AA_ADR1
YBAA_ADR1
Header Address
/SMBA0/AA_HEAD1
YBAA_HEAD1
Address
© SAP AG
Page 5 of
SAP Best Practices
Printing: Forms adaptation guide
Source Object
Target Object
Content
/SMBA0/AA_FOOTER
YBAA_FOOTER
Footer
/SMBA0/AA_FOOTER1
YBAA_FOOTER1
Telephone
/SMBA0/AA_FOOTER2
YBAA_FOOTER2
Web, email, tax numbers
/SMBA0/AA_FOOTER3
YBAA_FOOTER3
commercial register
/SMBA0/AA_FOOTER4
YBAA_FOOTER4
Bank
/SMBA0/AA_GRUSS
YBAA_GRUSS
regards
/SMBA0/AA_ADR_SENDER
YBAA_ADR_SENDER
Address
/SMBA0/AA_BILL_TO
YBAA_BILL_TO
Address
/SMBA0/AA_PAGE_INFORMATION
YBAA_PAGE_INFORMATION
Page Information
/SMBA0/AA_SENDER
YBAA_SENDER
Address, telephone, email, Web
/SMBA0/AA_TEL_SENDER
YBAA_TEL_SENDER
Telephone
/SMBA0/AA_FAX_SENDER
YBAA_FAX_SENDER
Fax
/SMBA0/AA_MAIL_SENDER
YBAA_MAIL_SENDER
email
/SMBA0/AA_QMCON_BEGIN1
YBAA_QMCON_BEGIN1
QM letter
/SMBA0/AA_QMCON_BEGIN2
YBAA_QMCON_BEGIN2
QM letter
/SMBA0/AA_QMCON_END
YBAA_QMCON_END
QM letter
2.2 Adaptation of Graphic During the installation of Building Block 100 (SAP Best Practices Installation) the graphic file smb40_leaf.bmp is uploaded into the system and stored as /SMBA0/AA_LEAF. This graphic is used in all preconfigured Smartforms. To replace the graphic file delivered with the SAP Best Practices Baseline Package with your own logo you have the following possibilities: 1. Adaptation before installation Rename your own graphic file and use the new name smb40_leaf.bmp. Copy this file to the folder containing the installation data (replace the original file). The modified graphic file is used during installation. 2. Adaptation after installation Carry out the following steps to replace the already uploaded graphic file with your own one. SAP ECC Menu
Tools Form Printout Administration Graphic
Transaction Code
SE78
1. On the Administration of Form Graphics screen expand the tree Stored on Document Server down to BMAP Bitmap Images (on the left side). 2. Select the entry BMAP Bitmap Images (double-click). 3. Select Color Bitmap Image. 4. From the menu, choose Graphic Import.
© SAP AG
Page 6 of
SAP Best Practices
Printing: Forms adaptation guide
5. Select your graphic file. 6. Enter the name /SMBA0/AA_LEAF and a description. 7. Select the following Print Attributes: o
Reserve Height Automatically
o
Compression
8. On the Import Graphic dialog box, confirm the message Graphic /SMBA0/AA_LEAF already exists.Overwrite? with Y.
For optimal display, the graphic should have the size of 109 * 109 pixels.
2.3 Adaptation of Standard Texts SAPScript Standard Texts are used:
to generate the e-mail body (send forms via e-mail functionality) or
as header and footer for SAPScript forms.
You can adapt the following standard texts to your own needs. These standard texts are copied to the YBxx namespace with the activation of BB 153. Source Object
Target Object
Text ID
Content
/SMBA0/EMAIL_BODY_CUST
YBAA_EMAIL_BODY_CUST
ST
Used for e-mails to customers.
/SMBA0/EMAIL_BODY_VEND
YBAA_EMAIL_BODY_VEND
ST
Used for e-mails to vendors.
/SMBA0/ADRS_SENDER
YBAA_ADRS_SENDER
ADRS
Used as header / footer in SAPscript forms.
/SMBA0/ADRS_FOOTER
YBAA_ADRS_FOOTER
ADRS
Used as header / footer in SAPscript forms.
/SMBA0/ADRS_HEADER
YBAA_ADRS_HEADER
ADRS
Used as header / footer in SAPscript forms.
/SMBA0/ADRS_SIGNAT
YBAA_ADRS_SIGNAT
ADRS
Used as header / footer in SAPscript forms.
/SMBA0/EMAIL_F150
YBAA_EMAIL_F150
FIKO
Used for e-mails related to dunning of customers.
To adapt these standard texts carry out the following steps:
© SAP AG
Page 7 of
SAP Best Practices
Printing: Forms adaptation guide
SAP ECC Menu
Tools Form Printout SAPscript Standard Text
Transaction Code
SO10
1. On the Standard Text: Request screen, make the following entries: Field Name
Description
User action and values
Text Name
Name of standard text
Enter the name of the target object, for example, YBAA_EMAIL_BODY_CUST
Text ID
Type of standard text
ST, ADRS, or FIKO
Language
Enter the language in which you want to maintain the standard text, for example, EN
2. Choose Change. 3. On the Change Standard text: XXX Language XX screen, make the required adaptations. 4. Save your entries.
3 Default Setting: Sending Forms via E-Mail The print-out of forms is the default setting after you have activated the Baseline Package. If you want to use the sending forms via e-mail functionality, you must apply some additional system settings that are listed in the sections Printing and Outbound e-mail configuration (optional) in the Quick Guide to Implement the SAP Best Practices Baseline Package. With these settings, you can also send a single form via e-mail. You can find a detailed description on how to do this in the respective section of each affected BPD. If you want to change the default setting from forms print out to sending forms via e-mail you must perform the steps listed in the subsequent sections additionally.
3.1 Maintaining User Settings Inform the users to assign the printer MAIL to their default values using the following procedure: 1. Access the activity using one of the following navigation options: SAP ECC Menu
System ® User Profile ® Own Data
Transaction Code
SU3
1. On the Maintain User Profile screen, choose the Defaults tab. 2. In the Spool Control section enter the OutputDevice MAIL. 3. Select the Print immed. and Delete After Output checkboxes. 4. Save your entries.
Use the printer name MAIL for the aforementioned settings.
Assigning the output device MAIL as the default output device could also have an effect in various applications not listed in the subsequent sections. For example: the transfer order (YBxx_LVSTAEINZEL) is sent to your e-mail address, instead of being printed out.
© SAP AG
Page 8 of
SAP Best Practices
Printing: Forms adaptation guide
3.2 Specify Default Values per Output Type (Optional) With the activation of BB 153 the default setting for each output type is set to transmission medium 1 Print output. To change this setting to 5 External send you must perform the following steps. 1. Access the activity using the following navigation option: NACE
Transaction Code
2. On the Conditions four Output Control screen select the required Application (see following list). 3. Choose Output types. 4. On the Display View “Output Types”: Overview screen, choose Display -> Change (Ctrl + F1). 5. Select the required OutputType (see following list) and choose Details (Ctrl + Shift + F2). 6. On the Display View “Output Types”: Details screen, choose the Default values tab. 7. Change the Dispatch time to 4 Send immediately (when saving the application). 8. Change the Transmission Medium to 5 External send. 9. Enter the communication strategy CS01. 10. Save your entries. Application
description
output type
V1
Quotation
AN00
V1
Order Confirmation
BA00
V1
Contract
KO00
V2
Delivery Note
LD00
V2
Bill of Lading
YBL1
V3
Sales Invoice
RD00
EA
RFQ
NEU
EA
RFQ-Urging/Reminder
MAHN
EA
RFQ-Quo rejection
ABSA
EF
PO
NEU
EF
PO-Urging/Reminder
MAHN
EF
PO-Ack. Expediter
AUFB
EV
Contract
NEU
EV
Contract-Ack. Expediter
AUFB
EL
Delivery Schedule
LPET
EL
DLS-Forecast
LPH2
EL
DLS-JIT
LPJ2
EL
DLS-Urging/Reminder
LPMA
ES
Service Entry Sheet
NEU
© SAP AG
Page 9 of
SAP Best Practices
Printing: Forms adaptation guide
3.3 Output Condition Records The condition records created with the activation of BB 153 use the transmission medium 1 Print output. To change this setting to 5 External send you must perform the steps described in the subsequent sections.
3.3.1
Output Condition Records: Sales (BA00, KO00)
1. Access the activity using one of the following navigation options: SAP ECC Menu
Logistics ® Sales and Distribution ® Master Data ® Output ® Sales Document ® Change
Transaction Code
VV12
2. On the Change Output – Condition Records: Sales screen, enter the required Output Type. Output Type
Description
BA00
Order Confirmation
KO00
Contract
3. Choose Enter. 4. On the Change xxx: Selection screen, make the following entries: Field Name
Description
Sales Organization
User Action and Values required Sales Organization (for example, 1000)
5. Choose Execute (F8). 6. On the Change Condition Records (xxx): Fast Change screen, change the Medium to 5 External send for all required sales document types (SalesDocTy). 7. Select each line (one after the other). 8. Choose Communication (F2). 9. On the Change Condition Records (xxx): Communication screen, make the following entries: Field Name
Description
User Action and Values
Comm.strategy
CS01
Output device
Mail
Print immediately
select
Release after output
select
10. Save your entries. 11. Choose Back (F3). 12. Repeat the steps 4 to 11 for all required sales organizations.
3.3.2
Output Condition Records: Sales (AN00)
1. Access the activity using one of the following navigation options: SAP ECC Menu
Logistics ® Sales and Distribution ® Master Data ® Output ® Sales Document ® Change
Transaction Code
VV12
2. On the Change Output – Condition Records: Sales screen, enter the required Output Type.
© SAP AG
Page 10 of
SAP Best Practices
Printing: Forms adaptation guide
Output Type
Description
AN00
Quotation
3. Choose Enter. 4. On the Change xxx: Selection screen, choose Execute (F8). 5. On the Change Condition Records (xxx): Fast Change screen, change the Medium to 5 External send for all required sales document types (SalesDocTy). 6. Select each line (one after the other). 7. Choose Communication (F2). 8. On the Change Condition Records (xxx): Communication screen, make the following entries: Field Name
Description
User Action and Values
Comm.strategy
CS01
Output device
Mail
Print immediately
select
Release after output
select
9. Save your entries.
3.3.3
Output Condition Records: Shipping
1. Access the activity using one of the following navigation options: SAP ECC Menu
Logistics ® Sales and Distribution ® Master Data ® Output ® Shipping ® Change
Transaction Code
VV22
2. On the Change Output – Condition Records: Sales screen, enter the required Output Type. Output Type
Description
LD00
Delivery Note
YBL1
Bill of Lading
3. Choose Enter. 4. On the Change xxx: Selection screen, make the following entries: Field Name
Description
Shipping Point/Receiving Pt
User Action and Values all required Shipping Points (for example, 1000)
5. Choose Execute (F8). 6. On the Change Condition Records (xxx): Fast Change screen, change the Medium to 5 External send for all required shipping points (Ship Point). 7. Select each line (one after the other). 8. Choose Communication (F2). 9. On the Change Condition Records (xxx): Communication screen, make the following entries: Field Name
Description
User Action and Values
Comm.strategy
CS01
Output device
Mail
Print immediately
select
© SAP AG
Page 11 of
SAP Best Practices
Printing: Forms adaptation guide
Release after output
select
10. Save your entries.
3.3.4
Output Condition Records: Billing
1. Access the activity using one of the following navigation options: SAP ECC Menu
Logistics ® Sales and Distribution ® Master Data ® Output ® Billing Document ® Change
Transaction Code
VV32
2. On the Change Output – Condition Records: Billing screen, enter the required Output Type. Output Type
Description
RD00
Invoice
3. Choose Enter. 4. On the Change xxx: Selection screen, make the following entries: Field Name
Description
Sales Organization
User Action and Values all required Sales Organizations (for example, 1000)
5. Choose Execute (F8). 6. On the Change Condition Records (xxx): Fast Change screen, change the Medium to 5 External send for all required billing types (Bill. Type). 7. Select each line (one after the other). 8. Choose Communication (F2). 9. On the Change Condition Records (xxx): Communication screen, make the following entries: Field Name
Description
User Action and Values
Comm.strategy
CS01
Output device
Mail
Print immediately
select
Release after output
select
10. Save your entries.
3.3.5
Output Condition Records: Entry Sheet
1. Access the activity using one of the following navigation options: SAP ECC Menu
Logistics ® Materials Management ® Purchasing ® Master Data ® Messages ® Service Entry Sheet ® Change
Transaction Code
MN14
2. On the Change Output – Condition Records: Entry Sheet screen, enter NEU: Entry of Srvc Prfrmd. 3. Choose Enter. 4. Choose the Key Combination Purchasing Output Determination: Document Type. 5. Choose Enter. 6. On the Change Entry of Srvc Pr (NEU): Selection screen, choose Execute (F8).
© SAP AG
Page 12 of
SAP Best Practices
Printing: Forms adaptation guide
7. On the Change Condition Records (Entry of Srvc Prfrmd): Fast Change screen, change the Medium to 5 External send for all required document types (Doc. Type). 8. Select all lines (one after the other). 9. Choose Communication (F2). 10. On the Change Condition Records (Entry of Srvc Prfrmd): Communication screen, make the following entries: Field Name
Description
User Action and Values
Comm.strategy
CS01
Output device
Mail
Print immediately
select
Release after output
select
11. Save your entries.
3.3.6
Output Condition Records: Scheduling Agreement Delivery Schedule
1. Access the activity using one of the following navigation options: SAP ECC Menu
Logistics ® Materials Management ® Purchasing ® Master Data ® Messages ® Scheduling Agreement Delivery Schedule ® Change
Transaction Code
MN11
2. On the Change Output – Condition Records: Purch.SchAgrRelease screen, enter the required Output Type. Output Type
Description
LPET
Delivery Schedule
LPH2
DLS-Forecast
LPJ2
DLS-JIT
LPMA
DLS-Urging/Reminder
3. Choose Enter. 4. Choose the Key Combination Purchasing Output Determination: Document Type. 5. Choose Enter. 6. On the Change xxx: Selection screen, choose Execute (F8). 7. On the Change Condition Records (xxx): Fast Change screen, change the Medium to 5 External send for all required document types (Doc. Type). 8. Select all lines (one after the other). 9. Choose Communication (F2). 10. On the Change Condition Records (xxx): Communication screen, make the following entries: Field Name
Description
User Action and Values
Comm.strategy
CS01
Output device
Mail
Print immediately
select
Release after output
select
11. Save your entries.
© SAP AG
Page 13 of
SAP Best Practices
3.3.7
Printing: Forms adaptation guide
Output Condition Records: Outline Agreement
1. Access the activity using one of the following navigation options: SAP ECC Menu
Logistics ® Materials Management ® Purchasing ® Master Data ® Messages ® Outline Agreement ® Change
Transaction Code
MN08
2. On the Change Output – Condition Records: Purch.Outline Agr. screen, enter the required Output Type. Output Type
Description
NEU
Contract
AUFB
Contract-Ack. Expediter
3. Choose Enter. 4. Choose the Key Combination Purchasing Output Determination: Document Type. 5. Choose Enter. 6. On the Change xxx: Selection screen, choose Execute (F8). 7. On the Change Condition Records (xxx): Fast Change screen, change the Medium to 5 External send for all required document types (Doc. Type). 8. Select all lines (one after the other). 9. Choose Communication (F2). 10. On the Change Condition Records (xxx): Communication screen, make the following entries: Field Name
Description
User Action and Values
Comm.strategy
CS01
Output device
Mail
Print immediately
select
Release after output
select
11. Save your entries.
3.3.8
Output Condition Records: Purchase Order
1. Access the activity using one of the following navigation options: SAP ECC Menu
Logistics ® Materials Management ® Purchasing ® Master Data ® Messages ® Purchase Order ® Change
Transaction Code
MN05
2. On the Change Output – Condition Records: Purchase Order screen, enter the required Output Type. Output Type
Description
NEU
PO
3. Choose Enter. 4. Choose the Key Combination Purchasing Output Determination: Document Type. 5. Choose Enter. 6. On the Change xxx: Selection screen, choose Execute (F8).
© SAP AG
Page 14 of
SAP Best Practices
Printing: Forms adaptation guide
7. On the Change Condition Records (xxx): Fast Change screen, change the Medium to 5 External send for all required document types (Doc. Type). 8. Select all lines (one after the other). 9. Choose Communication (F2). 10. On the Change Condition Records (xxx): Communication screen, make the following entries: Field Name
Description
User Action and Values
Comm.strategy
CS01
Output device
Mail
Print immediately
select
Release after output
select
11. Save your entries.
3.3.9
Output Condition Records: Purchasing RFQ
1. Access the activity using one of the following navigation options: SAP ECC Menu
Logistics ® Materials Management ® Purchasing ® Master Data ® Messages ® Request for Quotation ® Change
Transaction Code
MN02
2. On the Change Output – Condition Records: Purchasing RFQ screen, enter the required Output Type. Output Type
Description
NEU
RFQ
MAHN
RFQ-Urging/Reminder
ABSA
RFQ-Quo rejection
3. Choose Enter. 4. Choose the Key Combination Purchasing Output Determination: Document Type. 5. Choose Enter. 6. On the Change xxx: Selection screen, choose Execute (F8). 7. On the Change Condition Records (xxx): Fast Change screen, change the Medium to 5 External send for all required document types (Doc. Type). 8. Select all lines (one after the other). 9. Choose Communication (F2). 10. On the Change Condition Records (xxx): Communication screen, make the following entries: Field Name
Description
User Action and Values
Comm.strategy
CS01
Output device
Mail
Print immediately
select
Release after output
select
11. Save your entries.
© SAP AG
Page 15 of
SAP Best Practices
Printing: Forms adaptation guide
3.4 Additional Settings in SD (optional) 3.4.1
Defining Print Parameters Shipping (optional)
1. Access the activity using one of the following navigation options: IMG Menu
Logistics Execution Shipping Basic Shipping Functions Output Control Define print parameters shipping
Transaction Code
VP01SHP
2. On the Print Parameters screen, locate and double-click Delivery Note (LD00). 3. Change the following data: Ship Point
Output Device
1000
Mail
1010
Mail
4. Choose Save and then choose Back.
3.4.2
Defining Print Parameters Sales Organization (optional)
Use In this step, you define the print parameters for sales, shipping, billing, transportation, and sales activity output, for example. This is dependent on a predefined key.
Procedure 1. Access the activity using one of the following navigation options: IMG Menu
Sales and Distribution Basic Functions Output Control Define Print Parameters
Transaction Code
VP01
2. On the Print Parameters screen, locate and double-click the condition types listed below. 3. Change the following data: CTyp
SOrg.
Output Device
AF00
1000
Mail
AF00
1010
Mail
AN00
1000
Mail
AN00
1010
Mail
BA00
1000
Mail
BA00
1010
Mail
RD00
1000
Mail
RD00
1010
Mail
KO00
1000
Mail
KO00
1010
Mail
5. Save your entries. 6. Choose Back.
© SAP AG
Page 16 of
SAP Best Practices
Printing: Forms adaptation guide
3.5 Additional Customizing for Rejection Report in QM Use If the transmission medium 5 External send should be the default setting, the following additional user specific setting is required.
Procedure 1. Access the activity using one of the following navigation options: IMG Menu
Quality Management Quality Notifications Notification Processing Print Control Define Printer User-Dependent Print Control
Transaction Code
SPRO
2. On the Determine Work Area: Entry screen, make the following entry and choose continue (Enter). Field Name
Description
User Action and Values
Application area
N (Notifications (PM/QM..))
3. On the Change View “User-Specific Print Control”: Details screen, choose New Entries (F5). 4. On the New Entries: Details of Added Entries screen, make the following entries: Field Name
Description
User Action and Values
User
Enter * if this setting is relevant for all users.
Shop paper
5999 (rejection report)
OutputDevice
MAIL
Print Now
X
Delete After Output
X
5. Save your entries.
3.6 Changing Master Data 3.6.1
Vendor Master Records
Use The vendor master records created with the activation of the Baseline Package do not include the assignment of an e-mail address. Perform the following steps to assign an e-mail address to a vendor master record. Outgoing e-mails to this vendor are sent to this e-mail address.
Procedure 1. Access the activity using one of the following navigation options: SAP ECC Menu
Logistics ® Materials Management ® Master Data ® Vendor ® Central ® Change
Transaction Code
XK02
2. On the Change Vendor: Initial Screen, make the following entries:
© SAP AG
Page 17 of
SAP Best Practices Field Name
Printing: Forms adaptation guide Description
User Action and Values
Vendor
Address
select
3. Choose Enter. 4. On the Change Vendor: Address screen, make the following entries: Field Name
Description
E-Mail
User Action and Values
5. Save your entries.
3.6.2
Customer Master Records
Use The customer master records created with the activation of the Baseline Package do not include the assignment of an e-mail address. Perform the following steps to assign an e-mail address to a customer master record. Outgoing e-mails to this customer are sent to this e-mail address.
Procedure 1. Access the activity using one of the following navigation options: SAP ECC Menu
Logistics Sales and Distribution Master Data Business Partner Customer Change Complete
Transaction Code
XD02
2. On the Customer Change: Initial Screen screen, make the following entries: Field Name
Description
Customer
User Action and Values
3. Choose Enter (Enter). 4. On the Change Customer: General Data screen, make the following entries: Field Name
Description
E-Mail
User Action and Values
5. Save your entries.
4 Defining Header, Sender, and Footer for Additional Organizational Units With the activation of BB 216 Enterprise Structure Extension new sales organizations, a new purchasing organization and a new company code are created. To use different text modules or standard texts such as header, footer or sender for these new organizational units, check the description of the following subsections.
4.1 Text Modules 4.1.1
Automated Determination of Text Modules
For the Smartforms used within the scope items 123 Cross-Company Sales Order Processing and 141 Internal Procurement: Cross-Company Stock Transfer an automated determination of text modules has been enabled within the definition of these Smartforms.
© SAP AG
Page 18 of
SAP Best Practices
Printing: Forms adaptation guide
These Smartforms are: Source form
Target form
Description
/SMBA12/CN_MMPO
YBCN_MMPO
Purchase Order
/SMBA12/CN_MMGR1
YBCN_MMGR1
Goods Receipt (Individual Item)
/SMBA12/CN_MMGR2
YBCN_MMGR2
Goods Receipt (Individual Item with inspection text)
/SMBA12/CN_MMGR3
YBCN_MMGR3
Goods Receipt (Multiple Items)
/SMBA12/CN_SDORC
YBCN_SDORC
Order Confirmation
/SMBA12/CN_SDDLN
YBCN_SDDLN
Delivery Note
/SMBA12/CN_SDBLD
YBCN_SDBLD
Bill of Lading
/SMBA12/CN_SDINV
YBCN_SDINV
Sales Invoice
The text modules that are determined automatically are: Source Object
Target Object
/SMBA0/AA_ADR1
YBAA_ADR1
/SMBA0/AA_HEAD1
YBAA_HEAD1
/SMBA0/AA_SENDER
YBAA_SENDER
/SMBA0/AA_FOOTER1
YBAA_FOOTER1
/SMBA0/AA_FOOTER2
YBAA_FOOTER2
/SMBA0/AA_FOOTER3
YBAA_FOOTER3
/SMBA0/AA_FOOTER4
YBAA_FOOTER4
For the newly created organizational units you can create new textmodules (for example, with a different address). The name of these new text modules must be identical to the already existing textmodules, but must include a suffix indicating the number of the new organizational unit. It is not required to add these newly created textmodules to any customizing settings. Within the form processing the final text module name is concatenated in the following manner:
Prefix + + _ + organizational unit Example: If you are processing a sales order within the sales organization 1010 the textmodule for footer1 is: YBAA_FOOTER1_1010
If no textmodule is found with that name, the final text module name is concatenated without the organizational unit (Example: YBAA_FOOTER1).
To create additional textmodules for the new organizational unit, follow the detailed description in the next section.
4.1.2
Creating Additional Text Modules
Use The purpose of this activity is to define specific text modules for sales organizations, purchasing organizations and company codes. Newly created textmodules must be assigned in customizing or maintained in the respective forms afterwards (exceptions are listed in the previous section).
Procedure 1. Access the activity using one of the following navigation options
© SAP AG
Page 19 of
SAP Best Practices
Printing: Forms adaptation guide
IMG Menu
Tools Form Printout Smartforms
Transaction Code
SMARTFORMS
2. On the SAP Smart Forms: Initial Screen screen select Text Module and then choose Copy (Ctrl + F5). 3. In the Source Object field, enter the name of the Text Module you want to copy (see table below in the next step for further information). 4. In the Target Object field, enter the new name of the target object. XXXX means the number for a specific sales organization, company code, or purchasing organization (for example, 1010). Source Object
Target Object
Content
/SMBA0/AA_ADR1
YBAA_ADR1_XXXX
Header Address
/SMBA0/AA_HEAD1
YBAA_HEAD1_XXXX
Address
/SMBA0/AA_FOOTER
YBAA_FOOTER_XXXX
Footer
/SMBA0/AA_FOOTER1
YBAA_FOOTER1_XXXX
Telephone
/SMBA0/AA_FOOTER2
YBAA_FOOTER2_XXXX
Web, email, tax numbers
/SMBA0/AA_FOOTER3
YBAA_FOOTER3_XXXX
commercial register
/SMBA0/AA_FOOTER4
YBAA_FOOTER4_XXXX
Bank
/SMBA0/AA_GRUSS
YBAA_GRUSS_XXXX
regards
/SMBA0/AA_ADR_SENDER
YBAA_ADR_SENDER_XXXX
Address
/SMBA0/AA_BILL_TO
YBAA_BILL_TO_XXXX
Address
/SMBA0/AA_SENDER
YBAA_SENDER_XXXX
Address, telephone, email, Web
/SMBA0/AA_TEL_SENDER
YBAA_TEL_SENDER_XXXX
Telephone
/SMBA0/AA_FAX_SENDER
YBAA_FAX_SENDER_XXXX
Fax
/SMBA0/AA_MAIL_SENDER
YBAA_MAIL_SENDER_XXXX
email
5. Save the new text module. If the sysem displays a dialog box, enter a transport request and a development class (for example, Z001). 6. Maintain the address data for the respective sales organizations, company code, and purchasing organization: On the SAP Smart Forms: Initial Screen screen select Text Module and then enter the text module object you want to change. 7. Choose Change. 8. On the Change YBAA_*******_XXXX Text Module screen, perform your changes on the Text tab. 9. Save your entries.
Result You have created different text modules for different sales organizations, purchasing organizations and company codes.
© SAP AG
Page 20 of
SAP Best Practices
Printing: Forms adaptation guide
4.2 Standard Texts For the invoice verification, a SAPScript form (MR_REKL, YBDE_MM_MR_REKL) in combination with Standard Texts is used for print-out. In this case you must create and assign additional Standard Texts for the additional company code (for example, 1010) in case you want to use different standard texts.
4.2.1
Creating Additional Standard Texts
Use Process this activity to copy the already existing SAPScript standard texts to new standard texts.
Procedure 1. Access the activity using one of the following navigation options: IMG Menu
System Services Reporting
Transaction Code
SA38
2. On the ABAP Editor: Initial Screen, in the Program field, enter RSTXTCPY and choose Execute (F8). 3. On the Copy Texts Between Clients screen, make the following entries and choose Execute (F8) for each standard text (keep Action log activated and Overwrite after confirmation deactivated). Text Name
Object name
Text ID
Language
Source client
Target Name
/SMBA0/ADRS_SENDER
TEXT
ADRS
EN
000
for example, YBAA_ADRS_S_1010
/SMBA0/ADRS_FOOTER
TEXT
ADRS
EN
000
for example, YBAA_ADRS_F_1010
/SMBA0/ADRS_HEADER
TEXT
ADRS
EN
000
for example, YBAA_ADRS_H_1010
If required repeat these steps replacing language EN with your local language. 4. To adapt these standard texts carry out the following steps: SAP ECC Menu
Tools Form Printout SAPscript Standard Text
Transaction Code
SO10
5. On the Standard Text: Request screen, make the following entries: Field Name
Description
User action and values
Text Name
Name of standard text
Enter the name of the target object, for example, YBAA_ADRS_S_1010
Text ID
Type of standard text
ADRS
Language
Enter the language in which you want to maintain the standard text, for example, EN
6. Choose Change. 7. On the Change Standard text: XXX Language XX screen, make the required adaptations.
© SAP AG
Page 21 of
SAP Best Practices
Printing: Forms adaptation guide
8. Save your entries.
Result The SAPScript standard texts have been created.
Currently the created standard texts are not recorded in a workbench request automatically. To get standard texts for SAPscript forms transported, run the (TA SE38) RSTXTRAN report. Prerequisite: A workbench request with a development/correction task is required
Run the report and select the standard texts you would like to record in a workbench request.
Choose Enter to come to the next screen (Final List of Texts ...) and choose the Trsfr. texts to corr. (F5) button.
The selected texts are recorded in the workbench request.
4.2.2
Assigning Additional Standard Texts
4.2.3
Assigning Standard Texts for Invoice Verification Form
Use Process this activity to assign the newly created standard texts 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, choose New Entries.
3.
On the New Entries: Details of Added Entries screen, enter the following values: Field name
User action and values
Comment
Company Code
for example, 1010
Text ID
ADRS
Header Text
for example, YBAA_ADRS_H_1010
Footer Text
for example, YBAA_ADRS_F_1010
Signature Text
for example, YBAA_ADRS_SIGNAT
Sender
for example, YBAA_ADRS_S_1010
© SAP AG
Description
Page 22 of
SAP Best Practices 4.
Save your settings.
5.
Choose Back (F3).
© SAP AG
Printing: Forms adaptation guide
Page 23 of
View more...
Comments
