expertsask994@gmail.com
My Account
  • Home
  • Blog
  • eBooks
  • SAP FICO Course
  • About
  • Contact Us
  • My account

No products in the cart.

  • Home
  • Blog
  • eBooks
  • SAP FICO Course
  • About
  • Contact Us
  • My account

No products in the cart.

  • Home
  • Blog
  • eBooks
  • SAP FICO Course
  • About
  • Contact Us
  • My account

No products in the cart.

  • Home
  • Blog
  • eBooks
  • SAP FICO Course
  • About
  • Contact Us
  • My account
Blog
Home FICO Note to Payee Functionality
FICO

Note to Payee Functionality

ERP College December 18, 2021 1 Comment

Note to Payee is a functionality available in SAP DME to meet legal / bank requirements of additional details along with payment file.

Also, many times, note to payee information is required by bank/supplier, along with DME XML/FLAT file.

Basically, note to payee is information of paid line items for each vendor/business partner. Note to payee can be any information about payment as per the requirement of bank.

Below are few e.g.

  • Legally required information of each payment
  • Official document number, which is being paid
  • Common reference number between business partner

So note to payee is just additional information you have to print in output file. Just like we print other payment related details. Hence it is possible to do same kind of mapping in DMEE tcode itself and print these details. But SAP has provided separate function of Note to Payee to have greater flexibility.

Note: As a prerequisite to have fair understanding of this blog post, one should be familiar with DME functionality and DME tree structure. If you are new with DME then you can refer this eBook to learn DME.

Configuration steps for Note to Payee functionality in SAP:

Below transaction codes need to configure Note to payee in SAP:

  • Payment medium format (OBPM1)
  • OBPM2
  • FBZP
  • DMEE
  1. Payment medium format (OBPM1)

Select the concern payment format and go to tab ‘Text fields for reference information’

Here enter the information like type, field length, no of fields.

Field length will depend on requirement, where as No. of fields will depend on payment file structure. Let’s say if you have configured DME tree like separate line for each invoice then No. of fields 1 is sufficient.

But if you have configured DME tree for separate line for each vendor (multiple invoices) then No of fields should maximum like 99.

  1. Note to Payee (OBPM2)

From the same screen you can either click on Note to Payee button or go to transaction OBPM2

Create note to payee nodeCreate Note to Payee node

Then select option – Note to payee layout using function module and enter the function module name

Before this step as prerequisite this function module should be available/created. When you will ask ABAPer to develop such function module below are the things you should ask for apart from field and data logic:

  1. This function module should be called at the time of payment run
  2. Whenever Create payment medium checkbox is ticked
  3. Data of Note to Payee should be stored in table DFPAYHT

DFPAYHT table should store values as per the structure of Note to payee

Table DFPAYHT

Note: Reference FM for creating ZFM is – FM FI_PAYMEDIUM_SAMPLE_DETAILS

Well, if you want to go for customizing option, then it includes below steps:

Go to ‘Default Note to Payee’ section in OBPM2 after ticking ‘Note to payee using customizing’ option

Here in this tab we have option to play with SAPScript data. As you can see in notification type we can select the behaviour of output for Note to payee text field values. Values can be taken from three structures FPAYP, FPAYHP & FPAYHX. If you are confused about variables or other signs then just click F4 in Note to Payee text field and just select required fields.

You can also check the preview by selecting preview button for your payment medium format

These fields will be updated in table DFPAYHT.

Also Read: Functioning of CO-PA in make to order scenario

  • Maintain payment program FBZP

Select payment method in country

Select Country and payment method and go to tab Note to payee origin

Here in note to payee field enter the note to payee name which we created in OBPM2 transaction. This will help trigger FM and correct note to payee.

After this go to DMEE tree

Here we have to modify DMEE Tree and link note to payee in DME.

Create a node for Note to Payee where note to payee details should appear. This node is based on exit function. We need new function module for this node. Remember the function module we created and assigned in OBPM2 settings, that FM updates table DFPAYHT right. Here we need FM that can pull the information updated in DFPAYHT.

Checkout eBook: Manual and electronic bank reconciliation in SAP

a

If you remember previous screenshot of DFPAYHT table, there all the fields of note to payee is stored in separate line. So this FM should concatenate these fields into one single line.

Note: Reference FM to create ZFM is – DMEE_EXIT_TEMPLATE_ABA

Alternate to this option, if you don’t want to use exit function module, is to call structure DMEE_PAYD – TEXT

You can also visit this similar blogpost on Note to Payee functionality.

Below are some important points to note in Note to payee functionality:

  • Most of the times to match the requirement, standard customizing is not enough so in that case custom FM is much better and useful way to configure Note to Payee
  • Note to Payee is like free form text, it changes from bank to bank, organization to organization. In some cases, it is mandatory to print note to payee info in DME file. In some cases, it is not even required

This is simpler than how it looks; you just need to try this once. If you want to know more about DME then consider reading this eBook.

If you enjoy the blogpost, then you can stay connected with us on below platforms:

YouTube

LinkedIn FICO Page

LinkedIn ABAP Page

LinkedIn Logistics Page

Instagram

Also subscribe below to receive update of new blogpost

119
6827 Views
AboutERP College
ERP College is a knowledge portal for all of those who want to learn SAP. This is a one-stop reference for your entire SAP needs. Here you will find blogs that will help you to point out daily support issues. The blog covers technical, educational, and psychological aspects of working with SAP, mostly from the point of view of consultants or people responsible for implementing SAP software.
In Socials:
PrevWhat is MT101 file format and it's application in SAPAugust 24, 2021
The Art of Google Search [Must read guide for every SAP consultant]December 18, 2021Next

Related Posts

FICOGeneral SAP

Everything about Profit Center Accounting

This blogpost is a humble attempt to present the scope of Profit Center in SAP...

ERP College September 3, 2023
FICO

How to Copy Header Text to Line Item Text in FB60 and FV60 for better search capability by some Magic?

Introduction It is very useful to Copy Header Text to Line Item Text in FB60 and...

Arghadip Kar December 11, 2020

Comment (01)

  1. Pingback: Everything about OB52 authorization group (Full configuration guide)

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

  • Home
  • About
  • Contact
Categories
  • ABAP 8
  • FICO 23
  • General SAP 29
  • MM 1
  • SD 2
Products
  • SAP Accounts Payable (AP) Training
    Rated 4.00 out of 5
    ₹1,999.00 ₹1,699.00
  • Controlling - Profitability analysis (CO-PA): Comprehensive coverage of the SAP CO-PA module
    Rated 4.40 out of 5
    ₹449.00 ₹299.00
  • SAP Classic Vs New GL Accounting
    Rated 5.00 out of 5
    ₹999.00 ₹799.00
  • Learn to Debug ABAP Programs
    Rated 4.33 out of 5
    ₹499.00 ₹449.00
Sign Up to get update of latest Blogs

Find Us

Address
123 Main Street
New York, NY 10001

Hours
Monday–Friday: 9:00AM–5:00PM
Saturday & Sunday: 11:00AM–3:00PM

About This Site

This may be a good place to introduce yourself and your site or include some credits.

Contacts
Website: https://erpcollege.co/
Email: expertsask994@gmail.com
Terms & Condition

Copyright © 2020 ERP College by Smarksys Technologies. All Rights Reserved.