Payment Medium Workbench

PMW has two types of formats

• Code-based formats – These are formats that are based on ABAP function modules.
• DMEE Tree – Data Medium Exchange Engine. A transaction that allows for creation of drag and drop file formats using a tree structure.

There are two types of files that can be created with DMEE trees:

• Flat files
• XML files

Key Transaction Codes

• FBZP – Payment Program Configuration
• OBPM1 – Display Code formats and DMEE tree formats
• OBPM2 – Assign Note to Payee
• OBPM3 – Assign customer function modules to formats
• OBPM4 – Create/Assign Selection variants for PMW formats
• DMEE – Display Data Medium Exchange Engine format

Payment Medium Workbench Configuration Path

Financial Accounting (New) – Accounts Receivable and Accounts Payable – Business Transactions – Outgoing Payments – Automatic Outgoing Payments – Payment Media – Make Settings for Payment Medium Formats from Payment Medium Workbench

Prerequisites to Generate PMW File

There are two pieces of dependent configuration required in order to generate PMW files:

• Payment method by Country configuration sets up a payment method to generate a specific type of file.
• Create/Assign Selection Variants sets up a combination of the entities and banks that can generate a particular PMW file.

Payment methods for a Country are associated with the PMW layout

Create/Assign Selection Variants

• Variants are created to determine which bank output can be created.
• The same variant can be used across multiple house banks

Payment Medium Workbench Examples

• DMEE Tree XML example: CGI_XML_CT
• DMEE tree flat file example: 005 (Canadian Payment Association layout), similar to a US ACH payment)

DMEE — Updating SAP-Delivered XML Format

Download format from OSS onto local machine

If any customer modifications have been made, save a copy of the file

Log on in language to be used for modifications, and upload via DMEE transaction Format tree

Upload File

Press Enter through any warnings and save to transport when prompted. Navigate to file on local machine, and select the copy option.

XSLT for XML File Layouts

• Extensible Stylesheet Language Transformations (XSLT) are used to transform XML files into other XML files or other formats
• XSLT programs must be used with XML layouts when there are any nodes that may be empty on the payment layout

Node Types for XML Files

• Elements – Represent one line of an XML file; can contain a value itself, or it can be used to group elements as sub nodes.
• Attributes – Represent a sub node of an element; provide detailed information for an element; can contain atoms as sub nodes (for example, to map conditions)
• Technical node – Element that is not output to a target file; it stores values that are used in other tree nodes (elements, atoms) by a reference to this node.
• Atom – Used: 1.) to output more than one value to a single element, or 2.) to control which value is output to an element (based on conditions)

DMEE — Mapping Procedures for Elements

• Constant – Value is constant
• Structure Field – Refers to a field in any of the three payment structures FPAYH, FPAYHX, or FPAYP
• Reference to tree node – An attribute that refers to another node in the tree.
• Aggregation – Used to aggregate numerical values and make available for output in the file
• Exit module – When a user exit is used to retrieve a value or create a value.
• Own mapping (atoms) – When conditional mapping is needed based on user-specified conditions.
• No mapping – These elements contain no values but are used to perform groupings of elements in the XML structure.

Node Types for XML Files — Element and Attribute Examples

Node Types for XML Files — Atoms

DMEE — User Exits, Customer Function Modules

Users exist and Customer function modules are used when necessary field does not exist in the FPAYH, FPAYHX, or FPAYP structure. The conversion functions provided by SAP do not meet your requirements.

Customer Function Modules

FPAYHX structure has a series of 10 user-defined text fields available for custom. Mapping. Customer function modules are created to map the fields into the available Z fields. The structure and Z fields are then available for use in a format tree as elements.

DMEE — User Exit Example

DMEE Tree — Node Types for Flat Files

• Segment group – Used to group segments.
• Segment – Represents a record in the target file
• Composite – Used to group elements.
• Element – Represents a target field of the DME file
• Atom – Used: 1.) to output more than one value to a single element, or 2.) to control which value is output to an element (based on conditions)
• Technical node – Element that is not output to a target file; it stores values that are used in other tree nodes (elements, atoms) by a reference to this node S

DMEE Tree Flat File Example

Flat files are built in the DMEE transaction. The payments example will show how records get

grouped, how elements get conditionally populated and how file totals get created

Segment Group

• Segment groups are used when there are a series of segments needed on a file
• Groups help provide which levels of detail belong together
• Many flat file layouts need segment groups in order to get the appropriate details and looping
• correct

Atom Mapping

• Record Type is an example of an element that receives a value through the mapping provided in the file
• The overall element contains the length of the value for the file
• There are two atoms that provide possible values, C and D

Technical Node

Technical nodes store values but are not output directly on the file themselves.

Aggregation

• Aggregates are often used in totals records, as they help ensure no records were truncated from the file.
• Record counts and transaction amounts for files are extremely common for payment files.

For detailed step-by-step instructions on SAP ACH, Wire,  configuration, development using PMWB and DMEE follow along with my video tutorial below : Payment Automation in SAP-Wire, ACH, DMEE