You are on page 1of 18

EHP4 for SAP ERP

6.0
December 2010
English

Correspondence
Framework
(Y25)
Building Block Configuration Guide

SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany

XML. OSF/1. System i5. World Wide Web Consortium. BusinessObjects. the Adobe logo. z/OS. HTML. PartnerEdge. Inc. System i. RETAIN. 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. SAP. BatchPipes. System p5.. and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP France in the United States and in other countries. Redbooks. and other countries. These materials are subject to change without notice. Crystal Decisions. National product specifications may vary. Clear Enterprise. PostScript. Crystal Reports. eServer. System z10. R/3. IBM. XHTML and W3C are trademarks or registered trademarks of W3C®. used under license for technology invented and implemented by Netscape. © SAP AG Page 2 of 18 . DB2. PowerPC. SAP NetWeaver. z/VM. X/Open. and PowerPoint are registered trademarks of Microsoft Corporation. Massachusetts Institute of Technology. System x. Xcelsius. JavaScript is a registered trademark of Sun Microsystems. z9. VideoFrame. Adobe. MetaFrame. Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. POWER5. Business Objects and the Business Objects logo. Oracle is a registered trademark of Oracle Corporation. ByDesign. i5/OS. S/390. SAP BusinessObjects Explorer. and MultiWin are trademarks or registered trademarks of Citrix Systems. System z. Data contained in this document serves informational purposes only. AS/400. Citrix. Inc. System p. WebSphere. DB2 Connect. AIX.S. Duet. without representation or warranty of any kind. System z9. zSeries. OS/400. RACF. WinFrame. Java is a registered trademark of Sun Microsystems. 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. Power Architecture. if any. MVS/ESA. POWER5+. Windows. iSeries. UNIX. The information contained herein may be changed without prior notice. BladeCenter. HACMP. PowerVM. All other product and service names mentioned are the trademarks of their respective companies. S/390 Parallel Enterprise Server. Parallel Sysplex. Program Neighborhood. Excel. and Motif are registered trademarks of the Open Group. xSeries.SAP Best Practices Correspondence Framework (Y25): Configuration Guide Copyright © 2010 SAP AG. Acrobat. Microsoft. Outlook. Inc. OS/390. Web Intelligence. All rights reserved. POWER. OpenPower. GPFS. DB2 Universal Database. Linux is the registered trademark of Linus Torvalds in the U. OS/2. System Storage. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only. Nothing herein should be construed as constituting an additional warranty. Netfinity. POWER6. z10. and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. ICA. Intelligent Miner. POWER6+. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. pSeries. and SAP Group shall not be liable for errors or omissions with respect to the materials.

for example. paths and options. and individual key words of a programming language. © SAP AG Page 3 of 18 F2) or the . program names. Example text Exact user entry. Example text Emphasized words or phrases in body text. Pointed brackets indicate that you replace these words and characters with appropriate entries. pushbuttons as well as menu names. upgrade and database tools. Example text Screen output. names of variables and parameters as well as names of installation. SELECT and INCLUDE. These include report names. screen titles. EXAMPLE TEXT Keys on the keyboard. These include field names. EXAMPLE TEXT Names of elements in the system. for example. This includes file and directory names and their paths. when surrounded by body text. table names. titles of graphics and tables. source code. messages. transaction codes. <Example text> Variable user entry. Cross-references to other documentation. These are words or characters that you enter in the system exactly as they appear in the documentation.SAP Best Practices Correspondence Framework (Y25): Configuration Guide Icons Icon Meaning Caution Example Note Recommendation Syntax Typographic Conventions Type Style Description Example text Words or characters that appear on the screen. function keys (such as ENTER key.

.........................6 Correspondence Classes for Inbound Process..............1 Define Rules for Matching Correspondence Objects..4............2.........1.......................................................................................1 Define Business Partner Group...................................................................................SAP Best Practices Correspondence Framework (Y25): Configuration Guide Content 1 2 3 Purpose.....................................16 3........ 5 Preparation & Prerequisites........11 3........................1............................5 Define Correspondence Classes.9 3........................................................4 Define Correspondence Recipient Types............8 3...1 Define Communication Channels (Standard Configuration)........ 12 3...1......................8 3.......2...................................................8 3........2 Correspondence Messaging Interface...............................................................................8 3..................................5 Define Internal Recipients..........................................2.........................3 Correspondence Activities....................2 Define Correspondence Activities ..............1 General Settings for Business Correspondence...........2........... 18 © SAP AG Page 4 of 18 .................4 Define Number Ranges for Correspondence Object ID........7 Define Communication Profiles (Create Profiles)..................18 4 Forms and Alerts..................................................................................1.......................................9 Define Communication Profiles (Define Profiles).....2 Define Format Metatypes (Standard Configuration).........12 3................6 3......................2 Assign Attributes for Business Partner Groups.......................2...................16 3..3 Define Formats (Standard Configuration)...........................8 Assign Formats.........................................................1............................................................................................... 6 3.1 Define Correspondence Activities ..................................7 3...................8 3......................3...........11 3.................................4 Match Correspondence Objects....................................................9 3...........................5 Configuration.......3..............................6 3.....2....................................................................18 3.......................Foreign Exchange............2........................................................13 3................2....................2.........................17 3...........................Money Market....................3 Define Number Ranges for Match IDs........10 3...............

If you do not want to configure manually and prefer to use an automated installation process using BC Sets and other tools. the following business functions need to be activated:  FIN_TRM_LR_FI_AN TRM: Hedge Management.Foreign Exchange (FX)-Forward © SAP AG File Fax E-Mail SWIFT 320 SWIFT 300 Page 5 of 18 . Correspondence Framework TRM. refer to the Quick Guide of your SAP Best Practices package. This configuration is based on the following criteria:   Business Partner – ID: DEUBA Company Code 1000  Correspondence / Product Type: External – Confirmation: Print Y10 Money Market (MM) Y00 . SWIFT  FIN_TRM_CORR_FW TRM. field SMTP_ADDR).Fixed-Term Deposit-Investment Y40 Foreign Exchange (FX) Y03. New Instruments.0 with EHP 4 must be installed.SAP Best Practices Correspondence Framework (Y25): Configuration Guide Correspondence Framework: Configuration Guide 1 Purpose The purpose of this document is to describe the general configuration steps required to manually set up the configuration within the system landscape that has already been installed using the corresponding installation or configuration guides for installation. 2 Preparation & Prerequisites Enhancement package 4 for SAP ERP 6. The business function for Asset Management must be activated. All individual users must have a valid e-mail address specified in their user address data (transaction SU0: address data. A PDF-enabled printer needs to be installed for communication with the correspondence monitor. The following Enterprise Extensions need to be activated:  EA-FIN Financial Extension  EA-FS Financial Services Also. Hedge and Exposure SAP Note 1320374 has to be implemented. New Key Figures  FIN_TRM_LR_FI_AN_2 Management. which you can find on the documentation DVD. This is needed for communication in the correspondence monitor.

This is later assigned to the business partner. On the Change View “Business Partner Group”: Overview screen.1. make the following entries: Business Partner Group ID Text Active/Inactive Indicator YTBPG_DEUBA YTBPG_DEUBA Flag Name the group of all business partners using the same business settings. such as counterconfirmation behavior of the communication or status relevance of a message. You can use the business partner group to define the business settings and business attribute definitions of a correspondence for a group of business partners.1. from those of technical attributes.2 Assign Attributes for Business Partner Groups Use © SAP AG Page 6 of 18 . Procedure 1. Access the activity by choosing the following path: IMG Path Financial Supply Chain Management Treasury and Risk Management  Transaction Manager  General Settings  Correspondence  General Settings  General Settings  Define Business Partner Group Transaction Code SPRO 2. you make the required settings for a business partner group. matching requirement. This differentiates the business attribute definitions such as counterconfirmation requirement. and others.SAP Best Practices Correspondence Framework (Y25): Configuration Guide Transaction Internal – Dealing Slip to Back Office: Print File Fax Y10 Money Market (MM) Y00 Fixed-Term Deposit Investment E-Mail X 3 Configuration 3.1 General Settings for Business Correspondence 3. which defines the business settings of a correspondence.1 Define Business Partner Group Use In this Customizing activity. 3.

DEAL_MM = Area Money Market The correspondence recipient type is mainly used to differentiate between internal and external recipients/senders. It might be necessary to define more than one recipient/sender type for one recipient/sender if you want to use different communication channels (such as e-mail. and other attributes of TRM correspondence communication.A correspondence is to be automatically marked as completed . but you can also add your own. make the following entries: Automatic Counter Confirmation Business Partner Group ID Text Correspondence Class Recipient/ SenderType CorresStatus pondence Relevant Required YTBPG_DEUBA YTBPG_DEUBA YTDEAL_MM_FILE YTCOUNTERPARTY X X X YTBPG_DEUBA YTBPG_DEUBA YTDEAL_FX_FILE YTCOUNTERPARTY X X X YTBPG_DEUBA YTBPG_DEUBA YTDEAL_MM_EMAIL YTINTERNAL X X Correspondence classes are used as configuration terms to control the channel. format. partner settings.1.Reconciliation is required .Release is required before sending.The information about the external reference and contact person in the deal has to be updated with the information received in a status-relevant incoming correspondence Procedure 1. It is also a controlling parameter when outgoing/ incoming messages are created. you make the required settings for business partner groups. New correspondence classes should be added if a new transaction type (with new format. and file). Access the activity by choosing the following path: IMG Path Financial Supply Chain Management Treasury and Risk Management  Transaction Manager  General Settings  Correspondence  General Settings  Assign Attributes for Business Partner Groups Transaction Code SPRO 2. 3. and recipient/sender type. This activity assigns business attributes to the business partner. correspondence class. status relevance and so on) is defined.Automatic correspondence is required .SAP Best Practices Correspondence Framework (Y25): Configuration Guide In this Customizing activity. On the Change View “Assign Attributes for Business Partner Groups”: Overview screen. Correspondence classes are delivered by SAP. The business attributes specify whether: . .The correspondence object is deal status relevant . The release flag determines whether the release tool has to be called before the correspondence object is sent. you define the number ranges for match IDs.3 Define Number Ranges for Match IDs In this Customizing step. © SAP AG Page 7 of 18 .Counterconfirmation is required from the counterparty . fax.

On the Display View “Communication Channels”: Overview screen. The number ranges settings should not be transported. the channel controls the format of a message. you define number ranges for the correspondence ID. Channels can also have channel-specific attributes that have profiledependent values. Procedure 1.1 Define Communication Channels (Standard Configuration) Use In this Customizing activity. We recommend that you manually create the number ranges separately in each system.1. Access the activity by choosing the following path: IMG Path Financial Supply Chain Management Treasury and Risk Management  Transaction Manager  General Settings  Correspondence  Correspondence Messaging Interface  Define Communication Channels Transaction Code SPRO 2. No-Interval 3. Using the correspondence class and correspondence recipient type. No Interval 3. check the following entries: Short Response Channel Description Expected EMAIL Email FILE File System © SAP AG Page 8 of 18 .2.1.5 01 0000000000000001 to 9999999999999999 Define Internal Recipients This field represents the recipients of correspondences that are internal to the organization. Business Partner Group ID Text YTINTERNAL Internal Correspondence 3. You define the adaptor type and configuration to be used to process incoming and outgoing messages.4 01 0000000000000001 to 9999999999999999 Define Number Ranges for Correspondence Object ID In this Customizing step.2 Correspondence Messaging Interface 3.SAP Best Practices Correspondence Framework (Y25): Configuration Guide The number ranges must be customized in the target system. you define the way in which incoming and outgoing messages are handled.

If the network provides such a service.2. the metatype could define a method to derive the current message type from the formatted content of the incoming message. and attributes are assigned to them when TRM correspondence is processed. On the Display View “Define Format Metatypes”: Overview screen. Access the activity by choosing the following path: IMG Path Financial Supply Chain Management Treasury and Risk Management  Transaction Manager  General Settings  Correspondence  Correspondence Messaging Interface  Define Formats Transaction Code SPRO © SAP AG Page 9 of 18 . Procedure 1. Metatypes are used to facilitate the processing of incoming messages. Access the activity by choosing the following path: IMG Path Financial Supply Chain Management Treasury and Risk Management  Transaction Manager  General Settings  Correspondence  Correspondence Messaging Interface  Define Format Metatypes Transaction Code SPRO 2. Procedure 1. After the response arrives. If the format of an incoming message is not clear from other parameters (such as the import folder). the status of the correspondence objects is set to Awaiting acknowledgement.2 Define Format Metatypes (Standard Configuration) Use In this Customizing activity. you specify the class of the types of a message format group. you can receive technical responses from the processing network.SAP Best Practices FAX PRINT Correspondence Framework (Y25): Configuration Guide Fax Print Example: The checkbox is selected for FILE: Sending messages as files SWIFT networks delivers ACK and NAK messages to confirm the receipt and the correctness of the sent messages.2. you specify a structural definition. This class has a common header or characteristic for all message formats in the group. check the following entries: Format Metatype FORM SWIFT 3. Depending on the network. 3. the status is set to Delivered or Send error. which makes it possible to identify the exact format of a given message of this class.3 Short Description PDF/SAPScripts SWIFT messages Define Formats (Standard Configuration) Use In this Customizing activity.

A metaformat can include many formats and they can be assigned to more than one format group. the payload of the correspondence object is mapped to the configured format as usual. But a format group is not necessarily a subclass of metaformats.or outbound message Normal in. Access the activity by choosing the following path: IMG Path Financial Supply Chain Management Treasury and Risk Management  Transaction Manager  General Settings  Correspondence  Correspondence Messaging Interface  Define Correspondence Recipient Types Transaction Code SPRO 2.2.Foreign Exchange MT300 Confirmation Swift MT320 . make the following entries Internal Recipient/SenderType Short description recipient YTCOUNTERPARTY COUNTERPARTY YTINTERNAL INTERNAL X *1) *1) This indicates that the correspondence message (converted. the delivered status is also set. It is also a controlling parameter when outgoing/incoming messages are created. check the following entries: Format Short Description Swift MT300 . Procedure 1. On the Display View “Define Formats”: Overview screen. Format Group: Format groups are means of defining more detailed classification than metaformats. 3. and so on). although this is usually the case.SAP Best Practices Correspondence Framework (Y25): Configuration Guide 2. 3. If the given correspondence is status-relevant. On the Change View “Define Correspondence Recipient Types”: Overview screen. A field defined in the format syntax can be filled with other values for different partners. file system. The created message is stored in the document management system and can be displayed at any time later.5 Define Correspondence Classes Use © SAP AG Page 10 of 18 . If this checkbox is selected. but the created message is not sent (by using any middleware.Fixed Loan/Deposit MT320 Confirmation Money market: PDF Dealing slip PDF_DS_MM form Message Type Normal in.4 Define Correspondence Recipient Types Use The correspondence recipient type is mainly used to differentiate between internal and external recipients/senders. storage. formatted content) is not sent.or outbound message Normal in.2.or outbound message Format Group SWIFT SWIFT PDF Format: The semantics of the structure can depend on the communication partner.

format. Access the activity by choosing the following path: IMG Path Financial Supply Chain Management Treasury and Risk Management  Transaction Manager  General Settings  Correspondence  Correspondence Messaging Interface  Correspondence Classes for Inbound Process Transaction Code SPRO 2. status relevance and so on) is defined. you assign formats to the correspondence classes based on the recipient type and communication channel. make the following entries: Correspondence Class Short description YTDEAL_FX_FILE Deal: Foreign Exchange ( FILE ) YTDEAL_MM_EMAIL Deal: Money Market ( EMail ) YTDEAL_MM_FILE Deal: Money Market ( File ) 3. Procedure 1. On the Change View “Inbound Correspondence Function”: Overview screen. Access the activity by choosing the following navigation option: IMG Path Financial Supply Chain Management Treasury and Risk Management  Transaction Manager  General Settings  Correspondence  Correspondence Messaging Interface  Define Correspondence Classes Transaction Code SPRO 2. partner settings. Procedure 1. Correspondence classes are delivered by SAP.2. but you can also add your own.6 Correspondence Classes for Inbound Process Use In this Customizing activity. make the following entries: Format MT300 MT320 3. and other attributes of TRM correspondence communication. © SAP AG Page 11 of 18 .2. New correspondence classes should be added if a new transaction type (with new format.7 Recipient/SenderType YTCOUNTERPARTY YTCOUNTERPARTY Correspondence Class YTDEAL_FX_FILE YTDEAL_MM_FILE Define Communication Profiles (Create Profiles) Use In this Customizing activity.SAP Best Practices Correspondence Framework (Y25): Configuration Guide Correspondence classes are used as configuration terms to control the channel. On the Change View “Define Correspondence Classes”: Overview screen. you configure the settings to assign correspondence classes for inbound processes.

and received. Procedure 1.2. you assign formats to the correspondence classes based on the recipient type and communication channel. make the following entries: Test Ad Hoc Profile Short Description Profile Profile YTCOMPROF_DEUBA Corr.8 Assign Formats Use In this Customizing activity. make the following entries: Correspondence Profile Class Recipient/SenderType Channel Format YTCOMPROF_DEUBA YTDEAL_MM_FILE YTCOUNTERPARTY FILE MT320 YTCOMPROF_DEUBA YTDEAL_FX_FILE YTCOUNTERPARTY FILE MT300 YTCOMPROF_DEUBA YTDEAL_MM_EMAIL YTINTERNAL EMAIL PDF_DS_MM The profile contains all technical attributes that control how messages are created. Access the activity by choosing the following path: IMG Path Financial Supply Chain Management Treasury and Risk Management  Transaction Manager  General Settings  Correspondence  Correspondence Messaging Interface  Define Communication Profiles Transaction Code SPRO Communication Profiles 2. On the Change View “Assign Formats”: Overview screen.SAP Best Practices Correspondence Framework (Y25): Configuration Guide Procedure 1. 3. Profile for Deuba 3. Access the activity by choosing the following path: IMG Path Financial Supply Chain Management Treasury and Risk Management  Transaction Manager  General Settings  Correspondence  Correspondence Messaging Interface  Assign Formats Transaction Code SPRO 2. On the Change View “Define Communication Profiles”: Overview screen.9 Define Communication Profiles (Define Profiles) Use In this Customizing activity. you assign formats to the correspondence classes based on the recipient type and communication channel.2. sent. © SAP AG Page 12 of 18 .

and make the following entries. 5. the channel controls the format of a message. Select the row you entered and double-click the Channel Assignment folder. Assigned Format Metatypes Metatypes are used to facilitate the processing of incoming messages.SAP Best Practices Correspondence Framework (Y25): Configuration Guide This activity needs to be done manually when the system is being implemented. 6. If the format of an incoming message is not clear from other parameters (such as the import folder). Channel Assignment Using the correspondence class and correspondence recipient type. Configuration is not delivered using BC Set or eCATTs. 7. the metatype could define a method to derive the current message type from the formatted content of the incoming message. 4. choose New Entries. followed by New Entries. YTCOUNTERPARTY. and doubleclick the Assigned Format Metatypes folder. Save your entries. Save your entries. Channels can also have channel-specific attributes that have profiledependent values. and FILE. Select the required row and double-click the Assigned Format Metatypes folder: CorrespondClass YTDEAL_MM_FILE YTDEAL_FX_FILE YTDEAL_MM_EMAIL Recpt/Send Type YTCOUNTERPARTY YTCOUNTERPARTY YTINTERNAL Channel FILE FILE EMAIL a) Settings for correspondence class YTDEAL_MM_FILE (Deal: Money Market (File)): Select the row with YTDEAL_MM_FILE. and make the following entries: Test Ad-hoc Profile Short description Profile profile YTCOMPROF_DEUBA Corr-Profile for Deuba 3. On the Change View “Define Communication Profiles”: Overview screen. choose Change Mode. Procedure 1. © SAP AG Page 13 of 18 . Access the activity by choosing the following path: IMG Path Financial Supply Chain Management Treasury and Risk Management  Transaction Manager  General Settings  Correspondence  Correspondence Messaging Interface  Define Communication Profiles Transaction Code SPRO Communication Profiles 2. In the Channel Assignment folder.

/tmp’ stands for the path ‘…\work\tmp’. Make sure that the output and import folders exist on the application server. select the row with YTDEAL_FX_FILE. In the Channel-Dependent Attributes folder. 13. In the Format-Dependent Attributes folder. as well as to identify the format of incoming messages. Select the row you entered and double-click the Format-Dependent Attributes folder. Save your entries. Save your entries.SAP Best Practices Correspondence Framework (Y25): Configuration Guide 8. 10. See also the external ID of the format. © SAP AG Page 14 of 18 . make the following entries for MT320: MT320 External format ID 320 15. Format Metatype MT320 SWIFT Choose SWIFT for the File messages MT320 9. You must use different folders. b) Settings for correspondence class YTDEAL_FX_FILE (Deal: Foreign Exchange (FILE)): In the Channel Assignment folder. and FILE. If the format for incoming messages is not found using the prefix. the metatype implementation is used. and double-click the Assigned Format Metatypes folder. In the Assigned Format Metatypes folder. If the format of an incoming message is not clear from other parameters (such as the import folder). choose New Entries and make the following entries. Assigned Format Metatypes Metatypes are used to facilitate the processing of incoming messages. Save your entries. 11. 16. YTCOUNTERPARTY. Select the row you entered and double-click the Channel-Dependent Attributes folder: Channel-Dependent Attributes Channel-dependent attributes are used to create files for outgoing messages. /tmp 0 12. This ID is used to fill the header of an outgoing SWIFT message. the metatype could define a method to derive the current message type from the formatted content of the incoming message. It can also be used to identify the format of an incoming message.’ stands for the path ‘…\work\’ and input folder ‘. Format-Dependent Attributes 14. Return to the Channel Assignment folder by double-clicking it. choose New Entries and make the following entries for MT320: Filename Output Import Codepage of Format prefix folder folder channel MT320 MT320 . Ensure that the folder exists or change the definition in this Customizing activity. Output folder ‘.

’ stands for the path ‘…\work\’ and input folder ‘. If the format of an incoming message is not clear from other parameters (such as the import folder) the metatype could define a method to derive the current message type from the formatted content of the incoming message./tmp’ stands for the path ‘…\work\tmp’. In the Channel-Dependent Attributes folder. Save your entries. select the row with YTDEAL_MM_EMAIL. and EMAIL. Select the row you maintained and double-click the Channel-Dependent Attributes folder: Channel-Dependent Attributes Channel-dependent attributes are used to create files for outgoing messages.SAP Best Practices Correspondence Framework (Y25): Configuration Guide 17. choose New Entries and make the following entries for MT300: Filename Output Import Codepage of Format prefix folder folder channel MT300 MT300 . Return to the Assigned Format Metatypes folder by double-clicking it. 19. 21. the metatype implementation is used. 25. Select the row you entered and double-click the Format-Dependent Attributes folder. If the format of incoming messages is not found using the prefix. You must use different folders. In the Assigned Format Types Folder. 24. Ensure that the folder exists or change the definition in this Customizing activity. check the following entries or maintain the missing entry: Format Metatype MT300 SWIFT 18. as well as to identify the format of incoming messages. In the Assigned Format Types Folder. In the Format-dependent Attributes folder. See also the external ID of the format. It can also be used to identify the format of an incoming message. Make sure that the output and import folders exist on the application server. Output folder ‘. /tmp 0 20. choose New Entries and make the following entries for MT300: MT300 External format ID 300 23. YTINTERNAL. choose New Entries and make the following entries: Format Metatype © SAP AG Page 15 of 18 . Format-Dependent Attributes 22. Save your entries. c) Settings for correspondence class YTDEAL_MM_EMAIL (Deal: Money Market (EMail)): In the Channel Assignment folder. and double-click the Assigned Format Metatypes folder. This ID is used to fill the header of an outgoing SWIFT message. Assigned Format Metatypes Metatypes are used to facilitate the processing of incoming messages.

as well as to identify the format of incoming messages. Make sure that the output and import folders exist on the application server. the metatype implementation is used. Procedure 1. and for the transaction type for an activity.Money Market Use You assign each correspondence function code to a product type for an activity and also for a recipient type. This activity acts as one of the prerequisites for creating correspondence objects for money market contract types. Select the row you entered and double-click the Format-Dependent Attributes folder. based on the correspondence class and recipient assigned for that product type. Format-Dependent Attributes 31.1 Define Correspondence Activities . If the format of incoming messages is not found using the prefix. Output folder ‘.3 Correspondence Activities 3. In the Format-Dependent Attributes folder. See also the external ID of the format.3. Save your entries.SAP Best Practices E-Mail Correspondence Framework (Y25): Configuration Guide FORM Choose FORM for the E-Mails 26. Select the row you entered and double-click the Channel-Dependent Attributes folder: Channel-Dependent Attributes Channel-dependent attributes are used to create files for outgoing messages. 27. choose New Entries and make the following entries for e-mail: Format PDF_DS_MM 29. 30.Money Market Transaction Code SPRO © SAP AG Page 16 of 18 . Save your entries. Ensure that the folder exists or change the definition in this Customizing activity./tmp’ stands for the path ‘…\work\tmp’. 28. The correspondence object is created for a financial transaction. Access the activity by choosing the following path: IMG Path Financial Supply Chain Management Treasury and Risk Management  Transaction Manager  General Settings  Correspondence  Correspondence Activities Define Correspondence Activities . You must use different folders.’ stands for the path ‘…\work\’ and input folder ‘. make the following entries for E-Mail and save: Form Name FormCategory E-Mail YTDS_MM 1 PDF 3. In the Channel-Dependent Attributes folder.

4.1 Define Rules for Matching Correspondence Objects The correspondence class for a money market deal of incoming correspondence can be matched with a correspondence class for a money market deal of outgoing correspondence based on the deal number of the correspondence object table as the parameter.4 Match Correspondence Objects 3. 3.Foreign Exchange Transaction Code SPRO 2. This activity acts as one of the prerequisites for creating correspondence objects for money market contract types. On the Change View “Correspondence Activities: Money Market”: Overview screen. make the following entries: Company Code Product Category 1000 510 1000 510 1000 510 1000 510 Product Type Transaction Type Y10 Y10 Y10 Activity Category 20 YTCOUNTERPA YTDEAL_MM_ RTY FILE 21 YTCOUNTERPA YTDEAL_MM_ RTY FILE 20 Y10 Correspondence Internal Recipient/Sender Recipient Type Class 1*) 21 YTINTERNAL YTDEAL_MM_ EMAIL YTINTERN AL YTINTERNAL YTDEAL_MM_ EMAIL YTINTERN AL 1*) This field represents the recipients of correspondences that are internal to the organization. Procedure 1. and for the transaction type for an activity.3. Select the first row and choose Allowed BP Groups. On the Change View “Correspondence Activities: Foreign Exchange”: Overview screen. Outgoing Function © SAP AG Incoming Function Table Name Field Name Page 17 of 18 . The correspondence object is created for a financial transaction.Foreign Exchange Use You assign each correspondence function code to a product type for an activity and also for a recipient type. Access the activity by choosing the following path: IMG Path Financial Supply Chain Management Treasury and Risk Management  Transaction Manager  General Settings  Correspondence  Correspondence Activities Define Correspondence Activities . based on the correspondence class and recipient assigned for that product type.SAP Best Practices Correspondence Framework (Y25): Configuration Guide 2. Correspondence Class YTCOUNTERPARTY YTDEAL_FX_FILE 3.2 Define Correspondence Activities . make the following entries: Company Code Product Transaction Product Activity Category Type Type Category Recipient/SenderType 1000 600 Y40 Y04 30 3.

you can make your changes. When you develop new forms. Create. for example. you use the alert category assigned to the product type of that transaction. any inconsistency in the form may lead to runtime errors when financial transactions are created. You may need to develop a new form script by copying an existing standard form. the form YT_TR_CONFIRM_ALL and copy from the standard SAP form F_TR_CONFIRM_ALL. and correspondence confirmation. To create and assign this type of notification. note that if these are assigned for automatic print processing.SAP Best Practices Correspondence Framework (Y25): Configuration Guide YTDEAL_FX_FILE YTDEAL_FX_FILE TCORT_CODMD CURRENCY_PAY YTDEAL_FX_FILE YTDEAL_FX_FILE TCORT_CODMD CURRENCY_RCV YTDEAL_FX_FILE YTDEAL_FX_FILE TCORT_CODMD END_TERM YTDEAL_FX_FILE YTDEAL_FX_FILE TCORT_CODMD NOM_AMOUNT_PAY YTDEAL_FX_FILE YTDEAL_FX_FILE TCORT_CODMD NOM_AMOUNT_RCV YTDEAL_FX_FILE YTDEAL_FX_FILE TCORT_CODMD RATE YTDEAL_MM_FILE YTDEAL_MM_FILE TCORT_CODMD END_TERM YTDEAL_MM_FILE YTDEAL_MM_FILE TCORT_CODMD INT_CURRENCY YTDEAL_MM_FILE YTDEAL_MM_FILE TCORT_CODMD INT_CURRENT YTDEAL_MM_FILE YTDEAL_MM_FILE TCORT_CODMD NOM_AMOUNT YTDEAL_MM_FILE YTDEAL_MM_FILE TCORT_CODMD START_TERM 4 Forms and Alerts Forms SAP supplies standard forms that can be used for correspondence. Then assign the form in Customizing activity Define Correspondence Activities – Money Market in Customizing for correspondence. You can create forms using transaction SE71. Alerts The SAP system allows you to send alert notifications for a pending transaction activity such as a settlement. make changes as per your specific requirement. In YT_TR_CONFIRM_ALL. and assign the form in correspondence area Customizing for the transaction activity. You then need to assign this category to product types or money market transaction types. you must first define the alert category. for example. Whenever an alert notification has to be sent for a transaction. The correspondence function provided by SAP is freely definable. and can also be assigned with any other custom made forms. Most customers want to adjust the forms to reflect heir own design. You can find the relevant Customizing activities under the following path: IMG Path Financial Supply Chain Management Treasury and Risk Management  Transaction Manager  General Settings  Correspondence  Alert Transaction Code SPRO © SAP AG Page 18 of 18 . The new forms need to be changed in the print version. posting.