3550194 - "BSEG-VBUND" does not exist in dynpro SAPMF05A 0300

In the 'Free Form Payment' App an error ""BSEG-VBUND" does not exist in dynpro SAPMF05A 0300" is encountered while posting the data.

1. A custom field called YY1_TradingPartner of type Code list based CDS view was created and adapted in the Free Form Payment App under the posting tab.
2. A code was written to the extension point FINS_PAYT_REQUEST_ACCTG_DOC to transfer the value from the input field into the backend.
3. Open the Free Form Payment App.
4. Select the variant COST/PROFIT/TP.
5. Click on Post and Release.
6. An error "BSEG-VBUND" does not exist in dynpro SAPMF05A 0300 is thrown.

The trading partner is determined in the background as it is read from the business partner or G/L account master record as described in the SAP blog. Trading partner field in master data and reporting

Besides in the documentation of the BADI FINS_PAYT_REQUEST_ACCTG_DOC it is written that Trading Partner(BSEG-VBUND) can only be changed, provided it has not been preset by the business partner.

If G/L account need to be used, then maintain the Trading Partner directly in the G/L account.

Below steps can be followed

• Maintain G/L account in Manage G/L Account Master Data app
• Create the payment request
• Post the payment request
• The Journal Entry will be created with the Trading Partner from corresponding G/L account. 

Trading partner field in master data and reporting
App Extensibility: Free Form Payments

Free Form Payment App, Extensibility, Trading Partner, BSEG-VBUND, SAPMF05A 0300, custom field, YY1_TradingPartner, Code list based CDS view, FINS_PAYT_REQUEST_ACCTG_DOC, posting data. , KBA , CA-GTF-FXU-FI-AP , Fiori FXU Accounts Payable FI-FIO-AP , Problem