<?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 IDOC message type for billing documents in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/idoc-message-type-for-billing-documents/m-p/2033649#M417581</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have a need to export billing items out of SAP. Stumbled over this messagetype &amp;lt;b&amp;gt;SISINV/SISINV01&amp;lt;/b&amp;gt;. How to generate the messagetype with standard programs? Are there any standard programs that can generete these (so an abap similar to &amp;lt;b&amp;gt;BD10/RBDSEMAT&amp;lt;/b&amp;gt;)?&lt;/P&gt;&lt;P&gt;What customising in SIS covers this?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 13 Mar 2007 08:55:30 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-03-13T08:55:30Z</dc:date>
    <item>
      <title>IDOC message type for billing documents</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/idoc-message-type-for-billing-documents/m-p/2033649#M417581</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have a need to export billing items out of SAP. Stumbled over this messagetype &amp;lt;b&amp;gt;SISINV/SISINV01&amp;lt;/b&amp;gt;. How to generate the messagetype with standard programs? Are there any standard programs that can generete these (so an abap similar to &amp;lt;b&amp;gt;BD10/RBDSEMAT&amp;lt;/b&amp;gt;)?&lt;/P&gt;&lt;P&gt;What customising in SIS covers this?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 13 Mar 2007 08:55:30 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/idoc-message-type-for-billing-documents/m-p/2033649#M417581</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-03-13T08:55:30Z</dc:date>
    </item>
    <item>
      <title>Re: IDOC message type for billing documents</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/idoc-message-type-for-billing-documents/m-p/2033650#M417582</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;IDoc message type for billing documents (VF03) is INVOIC. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is no standard program per se, it's transaction data, so you will need to link IDoc to the output or something. Not sure hough what SIS has to do with it...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 20 Mar 2007 21:29:53 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/idoc-message-type-for-billing-documents/m-p/2033650#M417582</guid>
      <dc:creator>Jelena_Perfiljeva</dc:creator>
      <dc:date>2007-03-20T21:29:53Z</dc:date>
    </item>
    <item>
      <title>Re: IDOC message type for billing documents</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/idoc-message-type-for-billing-documents/m-p/2033651#M417583</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;The message type for billing document IDOC is INVOIC and the IDOC is INVOIC02.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You configurate the condition for output record using&amp;lt;b&amp;gt; T. Code NACE.&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Whever the document is created / changed, based on the configuration, output control can be used to automate subsequent processing of partner-specific messages using different processing options.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sap supports following processing options:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;Medium  Text
------- ------------
1	Print output
2	Fax
4	Telex               
5	External send
6	EDI
7	SAPoffice
8	Special function
9	Events (SAP Business Workflow)
A	Distribution (ALE)
T	Tasks (SAP Business Workflow)&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It uses the condition technique to determine what, if any, output is to be produced. The condition technique works by selecting key fields from the document and matching them to condition records you have previously set up.  You can also define your custom fields also for condition technique ( using user-exit )&lt;/P&gt;&lt;P&gt;If there is a match, then output is produced. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Refer below given links if you need more information.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_erp2004/helpdata/en/67/8473289a6511d2b7140000e8160175/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_erp2004/helpdata/en/67/8473289a6511d2b7140000e8160175/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_erp2004/helpdata/en/c8/19878343b111d1896f0000e8322d00/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_erp2004/helpdata/en/c8/19878343b111d1896f0000e8322d00/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let me know if you need further information.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;RS&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 20 Mar 2007 21:50:48 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/idoc-message-type-for-billing-documents/m-p/2033651#M417583</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-03-20T21:50:48Z</dc:date>
    </item>
  </channel>
</rss>

