on 11-25-2008 2:57 AM
Hi,
I've created a DME tree, since I need to create another DME file with same number of fields, only the field contents are different, I tried to copy my tree A to tree B (new), things are copied over, however the node ID are remained the same, when I tried to change the attribute of node in tree B, it would also change the content in tree A.
How can I create a new tree with reference to the old one?
Regards,
Junior
use copy function.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
The system comes with a sample format tree for making automatic payments by bank transfer in the form of DME files, based on the file format of the ChoHung bank in South Korea. You can copy format tree KR_CHB and adjust it to fit your own requirements. Refer to the format-tree documentation for KR_CHB for further details.
Features
The format tree is designed to work with payment method T (bank transfer) and Payment Medium Workbench (PMW) format KR_CHB, both of which are supplied with the system. Once you create your own format tree, you need to configure your system to work with this payment method and PMW format, as described in SAP Note 881637.
You then generate the payment media using the Payments program.
Payments
Purpose
You can use the payment program to process international payment transactions with customers and vendors.
Information on payment transactions in Euro can be found by choosing "Cross-application components" and then "European Monetary Union", and also in the SAP Library under European Monetary Union: Euro (CA-EUR)
Implementation Considerations
Configuration of the payment program is described in Customizing the Payment Program
Integration
The payment program is used by the following components: Accounts Receivable (FI-AR), Accounts Payable (FI-AP), Treasury (TR), and Bank Accounting (FI-BL).
Features
The payment program lets you handle both outgoing and incoming payments. It is flexible enough to allow you to define those payment features that vary from country to country such as payment method, payment form, or data carrier specifications.
The standard system contains the common payment methods and the corresponding forms that have been defined separately for each country.
The standard payment methods include check, transfer, and bill of exchange. Country-specific payment methods, such as the POR procedure in Switzerland, the bill of exchange payment request, and the PBC procedure have also been defined.
Other special features include:
Clearing open items between customers and vendors
Inter-company payments, that is one company code pays centrally for others
Paying or clearing any type of open item, for example clearing down payments
Restricting access to the payment program by assigning authorizations
Payment Medium Workbench
Purpose
The Payment Medium Workbench (PMW) is a tool used to configure and create payment media sent by organizations to their house banks. This generic tool will gradually phase out the classic payment medium programs (RFFO*) due to the range of advantages that it provides.
Superior control and verification of payment procedure
Improved performance with mass payments (> 50,000)
Better sort functions with payment advice notes
Clearer to work with than the myriad previous payment medium programs
Easier to maintain and to extend
Implementation Considerations
Before you can use the Payment Medium Workbench, you have to make various settings in Customizing. You can find the relevant activities in Customizing for Financial Accounting, under Accounts Receivable and Accounts Payable ® Business Transactions ® Outgoing Payments ® Automatic Outgoing Payments ® Payment Media ® Make Settings for Payment Medium Formats from Payment Medium Workbench.
Integration
The Payment Medium Workbench can be used by several components, for example FI-AP/AR, FI-TV, HR-PY, TR-CM, and TR-TM.
Features
The Payment Medium Workbench is embedded in a development environment. You can access all Workbench objects, (program objects, dictionary objects, and mapping tool objects) with a double-click. The Payment Medium Workbench encompasses the following areas:
Customizing for payment media
Defining Payment Medium Formats
Adjusting payment medium formats
Adjusting the Note to Payee
Assigning payment medium format and note to payee
Creating, Assigning, and Transporting Selection Variants
Creating Payment Media
Creating payment media without documents in file form
Output of the created data media into DME administration
DME administration supports both files stored in the TemSe or the file system, and payment messages like Internet payments (OFX) or IDoc.
Creation of payment advice notes
Output of the created payment advice notes as letter, fax, or IDoc
Creation of an output log (an error log too, if necessary) for each program run of the payment medium program
Constraints
At the present time, not all formats that can be created using the classic payment medium programs (RFFO*) are supported. You can display a complete list of available payment medium formats in format definition, or by using input help (in configuration of payment methods in the country, for example).
Data Medium Exchange Engine
Use
The Data Medium Exchange (DME) Engine enables you to define file formats that meet the requirements of your financial institution. By doing so, you model an externally defined bank format in the SAP system, which allows you to send or receive data in the form of DME files in this format.
The ability to define these formats in the system is particularly important as there is no worldwide or regional standard format. In some cases, no country standard exists and the file must comply with bank-specific standards. Covering such numerous and varied local format requirements is very difficult in standard software, but the DME Engine now enables you to define your particular local format yourself u2013 without any ABAP programming knowledge or coding. With this Customizing tool, in the form of a graphical editor, you can define new formats flexibly and, as format requirements change, modify existing ones efficiently.
Integration
Once you have modeled an external file format as a format tree in the DME Engine, calling applications can use it to:
· Generate an outgoing DME file as a flat file or an XML file
· Convert an incoming DME file to a format that the system can process
Features
The system comes complete with predefined format trees, which represent the file format requirements in a number of countries.
You can also transport format trees to other systems, or alternatively upload and download as XML files.
I hope this link will help you out.
http://help.sap.com/erp2005_ehp_03/helpdata/EN/43/fb329a295e025be10000000a1553f7/frameset.htm
Regards
Odaiah
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
94 | |
11 | |
9 | |
5 | |
3 | |
3 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.