<?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: BAPI_ACC_DOCUMENT_POST in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-acc-document-post/m-p/2794502#M652190</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Joe,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please leave all the three header fields of the blank :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think the fields are OBJ_TYPE, OBJ_KEY, and OBJ_SYS. This should be left blank if your are posting an accounting document which has an internal numbering range.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can probably use ''RFBU' as your BUS_ACT.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope it helps.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 17 Sep 2007 03:33:54 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-09-17T03:33:54Z</dc:date>
    <item>
      <title>BAPI_ACC_DOCUMENT_POST</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-acc-document-post/m-p/2794501#M652189</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Experts,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I want to create FI Doc through BAPI BAPI_ACC_DOCUMENT_POST. but I do not know how to get the below fields for import parameters DOCUMENTHEADER:&lt;/P&gt;&lt;P&gt;OBJ_TYPE&lt;/P&gt;&lt;P&gt;OBJ_KEY&lt;/P&gt;&lt;P&gt;BUS_ACT&lt;/P&gt;&lt;P&gt;I try to use the function module GET_NEXT_FI_DOCUMENT_NUMBER to get above fields but it do not work, Because OBJ_KEY is the FI doc number, How I can get the FI doc number before calling the BAPI. I try to use the function module NUMBER_GET_NEXT to get next doc number but it seems that it is not a good idea, Would you please give me an example for this issus?? Thanks very much and you will be rewarded if it is helpful.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 17 Sep 2007 03:29:02 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-acc-document-post/m-p/2794501#M652189</guid>
      <dc:creator>former_member249594</dc:creator>
      <dc:date>2007-09-17T03:29:02Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI_ACC_DOCUMENT_POST</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-acc-document-post/m-p/2794502#M652190</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Joe,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please leave all the three header fields of the blank :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think the fields are OBJ_TYPE, OBJ_KEY, and OBJ_SYS. This should be left blank if your are posting an accounting document which has an internal numbering range.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can probably use ''RFBU' as your BUS_ACT.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope it helps.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 17 Sep 2007 03:33:54 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-acc-document-post/m-p/2794502#M652190</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-09-17T03:33:54Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI_ACC_DOCUMENT_POST</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-acc-document-post/m-p/2794503#M652191</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Here's a snippet of code from a place we have used it, which agrees with the post above... our FI document numbers are internally assigned.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jonathan&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;* Document header
*
* Sender ID - We don't have an external ref, so let SAP set these
*
  ls_fi_doc_header = is_fi_doc_header.

  ls_fi_doc_header-obj_type   = space.
  ls_fi_doc_header-obj_key    = space.
  ls_fi_doc_header-obj_sys    = space.        "blank for same as current
*
* Fill in some known knowns :-)
*
  ls_fi_doc_header-comp_code  = gc_bukrs.     "Our Company code
  ls_fi_doc_header-username   = sy-uname.     "Current user
  ls_fi_doc_header-bus_act    = gc_glvor_fi_posting. "RFBU

  if ls_fi_doc_header-pstng_date is initial.
    ls_fi_doc_header-pstng_date = sy-datum.   "Post today
  endif.

  if ls_fi_doc_header-doc_date is initial.
    ls_fi_doc_header-doc_date   = sy-datum.   "Assume today
  endif.
*" etc etc&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 17 Sep 2007 03:42:55 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-acc-document-post/m-p/2794503#M652191</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-09-17T03:42:55Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI_ACC_DOCUMENT_POST</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-acc-document-post/m-p/2794504#M652192</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Srihari Hebbar  and Jonathan Coleman , the problem had been solved and the issued was closed. Thanks for your kindness.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Joe&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 17 Sep 2007 05:02:34 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-acc-document-post/m-p/2794504#M652192</guid>
      <dc:creator>former_member249594</dc:creator>
      <dc:date>2007-09-17T05:02:34Z</dc:date>
    </item>
  </channel>
</rss>

