I was faced with this question yesterday and it seems that few payment DMEEs will result in different output when copied into a bespoke Z* or Y* tree. Found out that some of these DMEEs have BADI implemented for them and changing the final file output according to the specific DMEE tree. So, for those who're looking for a reason why your bespoke output file doesn't match the original, do check those available BADI under *DMEE*.
Example that I did yesterday was a copied version of DK_PAYMUL_DOMESTIC. The final file has UNA header as UNA:+,? '. As much as I tried to put a constant in the DMEE tree on a bespoke copy, it won't get copied over to the output file. Found out that there is BADI implemented for that particular DMEE tree, under DMEE_BADI_01 with implementation name DMEE_DK_BADI_01. Copied that and add my bespoke DMEE into the filter and wallah, the output file matches the original.
Hope the above helps those who're stuck wondering why your bespoke copied version won't give the same output result as the standard one.
Subscribe to:
Post Comments (Atom)
TOUCHTAB report, regenerate all ABAPs related to changed/modified structure
I was working on S4HANA OnPremis and tried to do an enhancement to BP's additional info structure by appending fields, but decided that ...
-
Was looking for the best AC wifi router to replace my Buffalo WHR-G300NH and found that TP-Link has just released an Archer C7 V2 which has ...
-
I've come across many posting on the Internet (via google search), people asking on how to debug a DMEE for payment program. One of the ...
-
I've just subscribed to Astrill vpn service with a thought that they've openwrt scripting works as per the old twitter post that say...
No comments:
Post a Comment