<?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: FB60 in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/fb60/m-p/3560119#M856651</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;table name : &lt;STRONG&gt;MODSAP&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TCODES &lt;STRONG&gt;CMOD,SMOD&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;V.Balaji&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward if Usefull...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 28 Mar 2008 11:56:07 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-03-28T11:56:07Z</dc:date>
    <item>
      <title>FB60</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/fb60/m-p/3560117#M856649</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In vendor invoice,T.code FB60, in reference document field, the user should not enter the same reference document number twice.The system should give an error message ' reference document already exists'.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can this achieved by writing a validation. If so, How to create a validation? Or we should implement  any standard BADI.&lt;/P&gt;&lt;P&gt;Please suggest.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks &lt;/P&gt;&lt;P&gt;Vijay&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 28 Mar 2008 11:47:15 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/fb60/m-p/3560117#M856649</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-03-28T11:47:15Z</dc:date>
    </item>
    <item>
      <title>Re: FB60</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/fb60/m-p/3560118#M856650</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Try exploring the user exit.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;F050S001            FIDCMT, FIDCC1, FIDCC2: Edit user-defined IDoc segment&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;F050S002            FIDCC1: Change IDoc/do not send&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;F050S003            FIDCC2: Change IDoc/do not send&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;F050S004            FIDCMT, FIDCC1, FIDCC2: Change outbound IDoc/do not send&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;F050S005            FIDCMT, FIDCC1, FIDCC2 Inbound IDoc: Change FI document&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;F050S006            FI Outgoing IDoc: Reset Clearing in FI Document&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;F050S007            FIDCCH Outbound: Influence on IDoc for Document Change&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;F180A001            Balance Sheet Adjustment&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;FARC0002            Additional Checks for Archiving MM Vendor Master Data&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;RFAVIS01            Customer Exit for Changing Payment Advice Segment Text&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;RFEPOS00            Line item display: Checking of selection conditions&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;RFKORIEX            Automatic correspondence&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;SAPLF051            Workflow for FI (pre-capture, release for payment)&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Morris Bond.&lt;/P&gt;&lt;P&gt;Reward Points if Helpful.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 28 Mar 2008 11:52:45 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/fb60/m-p/3560118#M856650</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-03-28T11:52:45Z</dc:date>
    </item>
    <item>
      <title>Re: FB60</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/fb60/m-p/3560119#M856651</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;table name : &lt;STRONG&gt;MODSAP&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TCODES &lt;STRONG&gt;CMOD,SMOD&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;V.Balaji&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward if Usefull...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 28 Mar 2008 11:56:07 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/fb60/m-p/3560119#M856651</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-03-28T11:56:07Z</dc:date>
    </item>
    <item>
      <title>Re: FB60</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/fb60/m-p/3560120#M856652</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;have a look at:&lt;/P&gt;&lt;P&gt;SPRO&lt;/P&gt;&lt;P&gt;Materials Management&lt;/P&gt;&lt;P&gt;Logistics invoice verification&lt;/P&gt;&lt;P&gt;Incoming invoice&lt;/P&gt;&lt;P&gt;Set check for duplicate invoices&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;and here´s part of the documentation:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Set Check for Duplicate Invoices&lt;/P&gt;&lt;P&gt;In this step, you can configure for each company code if the system is to check for duplicate invoices when you enter invoices.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This check should prevent incoming invoices being accidentally entered and paid more than once.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can choose whether to activate or deactivate the check criteria of company code, reference document number and invoice date for each company code. The more criteria that you activate, the lower the probability of the system finding a duplicate invoice. The Accounting documents are checked first, followed by documents from Logistics Invoice Verification (only incorrect invoices or those entered for verification in the background).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 28 Mar 2008 15:51:06 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/fb60/m-p/3560120#M856652</guid>
      <dc:creator>former_member182371</dc:creator>
      <dc:date>2008-03-28T15:51:06Z</dc:date>
    </item>
  </channel>
</rss>

