<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: FB02 - Payment Block in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/fb02-payment-block/m-p/4589251#M1082301</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If I remember correctly, you control this via field status variants in customizing and "block reasons".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What applies there, applies to the transaction processing as well generally (the inability to remove a payment block, for example). But FB02 is a G/L journal transaction... so such "logistically dependent" events are sometimes missing such checks because they are not intended if the user gets that far...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The fastest way to check is to debug it and jump to the source code location to see your options.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Whether there is a customizable exception or an object which can be used I don't know off-hand. Perhaps your choice of transaction for this requirement is not correct....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Julius&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 23 Sep 2008 21:12:15 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-09-23T21:12:15Z</dc:date>
    <item>
      <title>FB02 - Payment Block</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/fb02-payment-block/m-p/4589250#M1082300</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have a security requirement to control the payment block field in transaction FB02. Does anyone know if any authorization objects exist for this field?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 23 Sep 2008 20:54:59 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/fb02-payment-block/m-p/4589250#M1082300</guid>
      <dc:creator>former_member443713</dc:creator>
      <dc:date>2008-09-23T20:54:59Z</dc:date>
    </item>
    <item>
      <title>Re: FB02 - Payment Block</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/fb02-payment-block/m-p/4589251#M1082301</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If I remember correctly, you control this via field status variants in customizing and "block reasons".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What applies there, applies to the transaction processing as well generally (the inability to remove a payment block, for example). But FB02 is a G/L journal transaction... so such "logistically dependent" events are sometimes missing such checks because they are not intended if the user gets that far...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The fastest way to check is to debug it and jump to the source code location to see your options.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Whether there is a customizable exception or an object which can be used I don't know off-hand. Perhaps your choice of transaction for this requirement is not correct....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Julius&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 23 Sep 2008 21:12:15 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/fb02-payment-block/m-p/4589251#M1082301</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-09-23T21:12:15Z</dc:date>
    </item>
  </channel>
</rss>

