Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Links
http://datamediumexchange.blogspot.com/
http://help.sap.com/saphelp_erp2004/helpdata/EN/e0/443d38a4136168e10000009b
38f8cf/content.htm
required steps to successfully configure the DME in the SAP system in order to generate a payment file
using the F110 transaction.
Create Payment Medium Format: SPRO
Financial Accounting New Accounts Receivable and Accounts Payable Business
Transactions Outgoing PaymentsAutomatic Outgoing Payments Payment Media Make Settings for
Payment Medium Formats from Payment Medium Workbench Create Payment Medium Formats
In this step of the configuration the Payment medium formats need to be created for each DMEE tree
configured. The new format must contain the same name as the DMEE format tree. We then choose the
format output Payment medium Without Docs to designate only the payment file will be generated and the
type File to signal a flat file will be generated rather than an IDoc or XML file type. Next, under Program
Control, set the Mapping using DME engine indicator, which links the format to the custom DMEE
object. Last, the Company Code check box is selected which instructs the program to create a file for
each company code involved in the payment run.
Assign Payment Medium Format to Payment Method at Country Level: Transaction FBZP
Financial Accounting New Accounts Receivable and Accounts Payable Business
Transactions Outgoing PaymentsAutomatic Outgoing Payments Payment Media Make Settings for
Payment Medium Formats from Payment Medium Workbench Assign Payment Medium Format and
Note to Payee to Payment Method
For each country and each payment method the Payment Medium Workbench must be assigned. This is
done by selecting the country and the corresponding payment method which will be using the Data
Medium Exchange (DME). The option button Use Payment Medium Workbench is then selected and
the Payment Medium Format, which was created in the previous step and which also possesses the
same name as the DME file structure is assigned in the format field.
**Documentation from http://help.sap.com/ was used to source portions of the above information
This site is in no way affiliated with SAP AG.
Posted by essman at 4:43 PM 4 comments
Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest
Labels: Data Medium Exchange, Data Medium Exchange Engine, DME, DMEE, SAP
SUNDAY, OCTOBER 9, 2011
The purpose of mapping is to reconstruct a file from the SAP system, which then bank can then use to
process payments.
The process of mapping begins with the bank first providing a file format. The format documents and file
examples are then used to map the fields in SAP.
Once complete the mapping is attached to the SAP Accounts Payable configuration so an output file can
be generated during a payment run.
File Structure:
The first two levels are mandatory, and the levels beneath the dotted line differ depending on the structure
of the bank file format. This ability to define the various subnodes within the payment file allows the user
to define the structure of the file according to the banks specifications.
DMEE Tree: Properties
Root:
------------------------------------------Header Record:
Payment Record:
Trailer Record:
Sorting:
Node Types:
Segment Group
Segment groups are used for arranging segments. Segment groups can be followed by these nodes:
segment groups or segments. In most cases, a new level in a DMEE tree begins with a segment group.
Segment
A segment represents a record in the target file. In an active format tree, each segment must have at least
one composite
or one element as a subnode. If you created a segment that contains only segments and segment groups
as subnodes, you can convert the node to a segment group.
Composite
You create a composite for the purpose of grouping elements. Such a grouping is logical if, for example,
one condition applies to several consecutive elements.
Element
An element represents a field in the target file. For each element, you specify with which value or from
which source field this file field is to be filled. If more than one mapping rule applies to an element - if the
rules are dependent on conditions or if different parts of the element are to be filled from different
sources - then you should define several atoms as subnodes of the element.
Technical Node
A technical node is an element that is not output to the target file. It stores values that are used in other
tree nodes (elements, atoms) by
reference to the technical node. For this reason, a technical node generally contains a reference ID. If you
wish to output the contents of the technical node to the target file, then you can convert the node to an
element.
Atom
You need to create an atom when you define more than one mapping rule for an element.
Selected Node for Detail View
This node was selected by double-clicking it. The details displayed on the top right belong to this
node. All toolbar operations (delete, copy, and so on) apply to this node. In contrast, all operations that
you can select from the context-sensitive menu with a right mouse click refer to the node which is
currently selected by a single click.
Reference ID of Node
A node that contains a reference ID can be referenced from other nodes in the format tree. You can
specify such a reference when you define mapping rules, conditions, or aggregation. You must assign
unique reference IDs (within the tree). When you delete a node that contains a reference ID, be sure that
no references to this node exist.
Reference to another node exists
This node contains a reference to another node. Moving the node could result in inconsistencies since
certain references are not permitted in parts of the tree.
**Documentation from http://help.sap.com/ was used to source portions of the above information.
Data Element:
Atom:
Data Element:
Tabs:
1.
Attributes
a.
Attribute Types
Constant Example:
Aggregation Example:
Conditions Example:
mentation from http://help.sap.com/ was used to source portions of the above information.
Click Enter:
The "Create Payment Medium" check box tells the program to generate the file.
In this case we are generating the file from the payment proposal. This is usually left unchecked until the
payment portion of the run.
Click Status again and buttons next to the status button will appear.
Click enter:
The Printjob is scheduled, and then press status again.
The file generated from the program will now be in the local directory you have specified.
This method is mostly used to test the file formats before "go-live."
In most cases, in a "live" environment, the file will be generated to a secure location such as a unix
The required directory location can be determined when setting up the variant for SAP program
"SAPFPAYM."
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 R/3 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.