<?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 FOR KB31N in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-for-kb31n/m-p/1798304#M342896</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Smith,&lt;/P&gt;&lt;P&gt;Please, Go thru the Documentation of the BAPI and check all fields are correctly filled or not once again.  It will helps you to fix problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;FU BAPI_ACC_STAT_KEY_FIG_POST&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;____________________________________________________&lt;/P&gt;&lt;P&gt;Short Text&lt;/P&gt;&lt;P&gt;Accounting: Post Statistical Key Figures&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Functionality&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;This method posts a document with statistical key figures.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The DOC_HEADER structure contains the document header data. The CO_AREA field must contain the controlling area in which you are to post. For an external number range, the DOC_NO field is specified for the document number.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The fields DOCDATE (document date) and POSTGDATE (posting date) are optional. For empty fields, the system enters the current date. The OBJ_KEY enables you to specify the number and organization of a reference document (each with 10 characters ). The OBJ_TYPE type field is defined for the object type of the reference document of the sending system.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;You should only fill the LOGSYSTEM field if this document belongs to an external system. You can enter a document header text in the DOC_HDR_TX field. If a suitable screen variant exists, you can archive it in the VARIANT field. It only makes sense to fill the VERSION field if you are posting to a business process&amp;lt;/b&amp;gt;. This is because if Activity-Based Costing is active as a parallel accounting system, you must specify a delta version. Otherwise you may only post in version 0, which is also set as the default.&lt;/P&gt;&lt;P&gt;The USERNAME field is a required field.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The document item data is transferred to the  DOC_ITEMS table. This consists of:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Field name    Description                                Optional&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-&lt;/P&gt;&lt;HR originaltext="---------------------------------------------------------------" /&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;STATKEYFIG    Statistical key figure&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;STAT_QTY      Statistical quantity&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PERS_NO       Personnel number                               X&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SEG_TEXT      Segment text                                    X&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;REC_CCTR      Receiver cost center&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ACTVTYTYPE    Activity type&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;RECEIV_ORD    Receiver order&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;REC_WBS_EL    Work breakdown structure element (WBS element)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;RECSALEORD    Receiver sales order&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;RECITEM       Item number in the receiver sales order&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;RECCOSTOBJ    Receiver cost object&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;RECBUSPROC    Receiver business process&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;REC_NETWRK    Receiver network&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;RECOPERATN    Receiver network activity&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;RRE_COMP_CODE Company code of the receiving real estate object&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;RRE_BUS_ENT   Receiver business entity - Real Estate&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;RRE_PROPERTY  Receiver property - Real Estate&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;RRE_BUILDING  Receiver building - Real Estate&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;RRE_RENT_UNIT Receiver rental unit - Real Estate&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;RRE_LEAS      Receiver lease - Real Estate&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;RRE_MGMT_CON  Receiver management contract&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;RRE_INC_EXP   Receiver service charge key - Real Estate&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;RRE_SETT_UNIT Receiver settlement unit - Real Estate&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;RRE_REF_DATE  Receiver reference date for settlement - Real Estate&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;RRE_CON_NO    Receiver contract - Real Estate&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;REC_FUND      Receiver fund&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;REC_FUNCTION  Receiver functional area&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;REC_GRANT     Receiver grant&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The SRE_* fields are for sender real estate objects are obsolete and are not used.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The system displays the collected messages in the MESSAGES structure. With a successful posting, the system archives the document number in the DOC_NO parameter.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Parameters&lt;/P&gt;&lt;P&gt;DOC_HEADER&lt;/P&gt;&lt;P&gt;IGNORE_WARNINGS&lt;/P&gt;&lt;P&gt;DOC_NO&lt;/P&gt;&lt;P&gt;DOC_ITEMS&lt;/P&gt;&lt;P&gt;RETURN&lt;/P&gt;&lt;P&gt;CUSTOMER_FIELDS&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;Arjun &lt;/P&gt;&lt;P&gt;Reward point if it helps&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 04 Jan 2007 13:25:32 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-01-04T13:25:32Z</dc:date>
    <item>
      <title>BAPI FOR KB31N</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-for-kb31n/m-p/1798303#M342895</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;   I have a problem in the bapi for kb31n  ,   I made a program used the bapi "API_ACC_STAT_KEY_FIG_POST"    . But Same times , the program didn't work succeed.    When I debug this program , Everything is succeed.&lt;/P&gt;&lt;P&gt;   How to do this?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks in advance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;bob&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Jan 2007 03:45:07 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-for-kb31n/m-p/1798303#M342895</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-01-04T03:45:07Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI FOR KB31N</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-for-kb31n/m-p/1798304#M342896</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Smith,&lt;/P&gt;&lt;P&gt;Please, Go thru the Documentation of the BAPI and check all fields are correctly filled or not once again.  It will helps you to fix problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;FU BAPI_ACC_STAT_KEY_FIG_POST&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;____________________________________________________&lt;/P&gt;&lt;P&gt;Short Text&lt;/P&gt;&lt;P&gt;Accounting: Post Statistical Key Figures&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Functionality&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;This method posts a document with statistical key figures.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The DOC_HEADER structure contains the document header data. The CO_AREA field must contain the controlling area in which you are to post. For an external number range, the DOC_NO field is specified for the document number.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The fields DOCDATE (document date) and POSTGDATE (posting date) are optional. For empty fields, the system enters the current date. The OBJ_KEY enables you to specify the number and organization of a reference document (each with 10 characters ). The OBJ_TYPE type field is defined for the object type of the reference document of the sending system.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;You should only fill the LOGSYSTEM field if this document belongs to an external system. You can enter a document header text in the DOC_HDR_TX field. If a suitable screen variant exists, you can archive it in the VARIANT field. It only makes sense to fill the VERSION field if you are posting to a business process&amp;lt;/b&amp;gt;. This is because if Activity-Based Costing is active as a parallel accounting system, you must specify a delta version. Otherwise you may only post in version 0, which is also set as the default.&lt;/P&gt;&lt;P&gt;The USERNAME field is a required field.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The document item data is transferred to the  DOC_ITEMS table. This consists of:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Field name    Description                                Optional&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-&lt;/P&gt;&lt;HR originaltext="---------------------------------------------------------------" /&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;STATKEYFIG    Statistical key figure&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;STAT_QTY      Statistical quantity&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PERS_NO       Personnel number                               X&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SEG_TEXT      Segment text                                    X&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;REC_CCTR      Receiver cost center&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ACTVTYTYPE    Activity type&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;RECEIV_ORD    Receiver order&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;REC_WBS_EL    Work breakdown structure element (WBS element)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;RECSALEORD    Receiver sales order&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;RECITEM       Item number in the receiver sales order&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;RECCOSTOBJ    Receiver cost object&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;RECBUSPROC    Receiver business process&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;REC_NETWRK    Receiver network&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;RECOPERATN    Receiver network activity&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;RRE_COMP_CODE Company code of the receiving real estate object&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;RRE_BUS_ENT   Receiver business entity - Real Estate&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;RRE_PROPERTY  Receiver property - Real Estate&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;RRE_BUILDING  Receiver building - Real Estate&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;RRE_RENT_UNIT Receiver rental unit - Real Estate&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;RRE_LEAS      Receiver lease - Real Estate&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;RRE_MGMT_CON  Receiver management contract&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;RRE_INC_EXP   Receiver service charge key - Real Estate&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;RRE_SETT_UNIT Receiver settlement unit - Real Estate&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;RRE_REF_DATE  Receiver reference date for settlement - Real Estate&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;RRE_CON_NO    Receiver contract - Real Estate&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;REC_FUND      Receiver fund&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;REC_FUNCTION  Receiver functional area&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;REC_GRANT     Receiver grant&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The SRE_* fields are for sender real estate objects are obsolete and are not used.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The system displays the collected messages in the MESSAGES structure. With a successful posting, the system archives the document number in the DOC_NO parameter.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Parameters&lt;/P&gt;&lt;P&gt;DOC_HEADER&lt;/P&gt;&lt;P&gt;IGNORE_WARNINGS&lt;/P&gt;&lt;P&gt;DOC_NO&lt;/P&gt;&lt;P&gt;DOC_ITEMS&lt;/P&gt;&lt;P&gt;RETURN&lt;/P&gt;&lt;P&gt;CUSTOMER_FIELDS&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;Arjun &lt;/P&gt;&lt;P&gt;Reward point if it helps&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Jan 2007 13:25:32 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-for-kb31n/m-p/1798304#M342896</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-01-04T13:25:32Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI FOR KB31N</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-for-kb31n/m-p/1798305#M342897</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;thanks:  Arjun .&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Jan 2007 05:38:08 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-for-kb31n/m-p/1798305#M342897</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-01-05T05:38:08Z</dc:date>
    </item>
  </channel>
</rss>

