Avoid DME File duplication & Payment Medium Proposal pop up

[former_member228896]

Dear Experts

Avoid Duplication of DME files

After F110 is executed successfully DME is automatically created

however subsequently when user  clicks on "PRINT OUT" tab DME is generated automatically.

I tried with solution "OBA5 ---> App Area "BFIBL02"---> Msg 166

although this is working , we want to restrict it to a xyz company code only.

Any suggestions

Avoid Payment Medium proposal  pop up         

while executing payment proposal, payment medium proposal pop's up , if checked, its creating duplicating DME.

How to avoid this pop up?

Regards

Sanjai

[AntonFarenyk]

I tried with solution "OBA5 ---> App Area "BFIBL02"---> Msg 166
although this is working , we want to restrict it to a xyz company code only.

Message 166 works fine for me too. So why to ccode xyz only? You can try to modify standard include FPAYM_STA  (which raises BFIBL02 166) to enhance with your logic by ccode but it takes access key and usually it's dangerous to modify standard SAP program.

while executing payment proposal, payment medium proposal pop's up , if checked, its creating duplicating DME.
How to avoid this pop up?

No need to mess with pop-up, just remove activity 15 from users/roles with auth.objects F_REGU_KOA and F_REGU_BUK.

[former_member228896]

Hi Anton,

Thanks for your reply, I have query for the below response

No need to mess with pop-up, just remove activity 15 from users/roles with auth.objects F_REGU_KOA and F_REGU_BUK

Other than F110 , does any other transaction code can generate "payment proposal medium"

Reason is, security team says though they remove the authorization object 15 for F110 , there are other T Codes that this authorization object is attached, where user can execute and generate the payment proposal medium .

Regards

Sanjai

[AntonFarenyk]

Reason is, security team says though they remove the authorization object 15 for F110 , there are other T Codes that this authorization object is attached, where user can execute and generate the payment proposal medium .

First, in my reply I suggest to remove activity 15 only, not the whole object. Hope this is your typo error.

Second, to answer your question – yes i.e. F111, but why it matters?

If your security team is unsure then they need to compare list of users who have F110 with a list of those having each of 2 objects mentioned above with field FBTCH = 15. This way they will be able to assess the impact of removing this activity from particular roles and not disturb anything or anybody else. Armed with SUIM and SU24 they should be able to do so. It all depends on how your roles are build, but it’s off topic.

Alternatively you might want to look to modify standard screen 1106 in program SAPF110V and try to remove checkbox F110V-XMITD. But IMHO it’s much worse then remove authorization values from roles.