<?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 BAPI in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi/m-p/2203473#M471067</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;how can we use the BAPI_SALESDOCU_CREATEWITHDIA?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;what are the parameters to be used in it?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 27 Apr 2007 10:38:35 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-04-27T10:38:35Z</dc:date>
    <item>
      <title>BAPI</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi/m-p/2203473#M471067</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;how can we use the BAPI_SALESDOCU_CREATEWITHDIA?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;what are the parameters to be used in it?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 27 Apr 2007 10:38:35 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi/m-p/2203473#M471067</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-04-27T10:38:35Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi/m-p/2203474#M471068</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; Text&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;     Creating a Sales and Distribution Document&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;   Functionality&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;     Using this method, you can create sales documents with items, schedule&lt;/P&gt;&lt;P&gt;     lines and item conditions.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;     You must enter at least sales order header data (via the structure&lt;/P&gt;&lt;P&gt;     ORDER_HEADER_IN) and partner data (via the table ORDER_PARTNERS).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;     Enter the item data via the table ORDER_ITEMS_IN. You can enter the item&lt;/P&gt;&lt;P&gt;     number manually, by filling in the relevant fields, or automatically,&lt;/P&gt;&lt;P&gt;     corresponding to Customizing, by leaving the relevant fields blank. If&lt;/P&gt;&lt;P&gt;     you decide to enter item numbers using R/3, no schedule lines or&lt;/P&gt;&lt;P&gt;     conditions can be entered, as these cannot be linked to the&lt;/P&gt;&lt;P&gt;     corresponding item.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;     If you are dealing with configurable items, you must enter the&lt;/P&gt;&lt;P&gt;     configuration data in the tables ORDER_CFGS_REF, ORDER_CFGS_INST,&lt;/P&gt;&lt;P&gt;     ORDER_CFGS_PART_OF, ORDER_CFGS_VALUE and ORDER_CFGS_BLOB.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;     The scheduling data can be published via the structure&lt;/P&gt;&lt;P&gt;     SALES_SCHEDULE_IN.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;     Document condtions to be created can be entered via the structure&lt;/P&gt;&lt;P&gt;     SALES_CONDITIONS_IN.&lt;/P&gt;&lt;P&gt;Credit card data can be published via the structure SALES_CCARD, card&lt;/P&gt;&lt;P&gt;identification data on the one hand, data on an authorization that has&lt;/P&gt;&lt;P&gt;taken place in an external system on the other.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Once you have created the sales document successfully, you will receive&lt;/P&gt;&lt;P&gt;the document number (field SALESDOCUMENT_EX).  (Feld SALESDOCUMENT_EX).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Errors which might occur will be announced via the parameter RETURN.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Using the checkbox:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can generate the individual components for a sales document with or&lt;/P&gt;&lt;P&gt;without a checkbox. If you decide on the first possibility, only fields&lt;/P&gt;&lt;P&gt;with unequal SPACE will be copied. In the second case (field&lt;/P&gt;&lt;P&gt;UPDATEFLAG), only fields which have an 'X' in the box are copied. As a&lt;/P&gt;&lt;P&gt;result, fields, which are preassigned to default values by the system,&lt;/P&gt;&lt;P&gt;can be set on SPACE again.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Notes&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  1.  If no object references are to be written, the&lt;/P&gt;&lt;P&gt;      (parameters) should be initialized:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;            BINARY_RELATIONSHIPTYPE&lt;/P&gt;&lt;P&gt;            SALES_HEADER_IN-REFOBJECTTYPE&lt;/P&gt;&lt;P&gt;            SALES_HEADER_IN-REFOBJECTKEY&lt;/P&gt;&lt;P&gt;            SALES_HEADER_IN-REFDOCTYPE&lt;/P&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;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;rameters&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  SALESDOCUMENT&lt;/P&gt;&lt;P&gt;  SALES_HEADER_IN&lt;/P&gt;&lt;P&gt;  SALES_HEADER_INX&lt;/P&gt;&lt;P&gt;  SENDER&lt;/P&gt;&lt;P&gt;  BINARY_RELATIONSHIPTYPE&lt;/P&gt;&lt;P&gt;  CONVERT_PARVW_AUART&lt;/P&gt;&lt;P&gt;  SYNCHRONOUS&lt;/P&gt;&lt;P&gt;  SALESDOCUMENT_EX&lt;/P&gt;&lt;P&gt;  RETURN&lt;/P&gt;&lt;P&gt;  SALES_ITEMS_IN&lt;/P&gt;&lt;P&gt;  SALES_ITEMS_INX&lt;/P&gt;&lt;P&gt;  SALES_PARTNERS&lt;/P&gt;&lt;P&gt;  SALES_SCHEDULES_IN&lt;/P&gt;&lt;P&gt;  SALES_SCHEDULES_INX&lt;/P&gt;&lt;P&gt;     SALES_CFGS_REF&lt;/P&gt;&lt;P&gt;     SALES_CFGS_INST&lt;/P&gt;&lt;P&gt;     SALES_CFGS_PART_OF&lt;/P&gt;&lt;P&gt;     SALES_CFGS_VALUE&lt;/P&gt;&lt;P&gt;     SALES_CFGS_BLOB&lt;/P&gt;&lt;P&gt;     SALES_CCARD&lt;/P&gt;&lt;P&gt;     PARTNERADDRESSES&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; Exceptions&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; Function Group&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;     VBAK&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;, better way u go to TC : se37, type the name of FM and then click on FM Documentation, u will get all the information on that FM and thr parameters.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think this will help u.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward points if helpful&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Nilesh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 27 Apr 2007 10:45:13 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi/m-p/2203474#M471068</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-04-27T10:45:13Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi/m-p/2203475#M471069</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;For learning about any BAPI, the best place is to check its documentation in SE37, as thats the best help available.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For this one as given by SAP-&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You must enter at least sales order header data (via the structure&lt;/P&gt;&lt;P&gt; ORDER_HEADER_IN) and partner data (via the table ORDER_PARTNERS).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; Enter the item data via the table ORDER_ITEMS_IN. You can enter the item&lt;/P&gt;&lt;P&gt; number manually, by filling in the relevant fields, or automatically,&lt;/P&gt;&lt;P&gt; corresponding to Customizing, by leaving the relevant fields blank. If&lt;/P&gt;&lt;P&gt; you decide to enter item numbers using R/3, no schedule lines or&lt;/P&gt;&lt;P&gt; conditions can be entered, as these cannot be linked to the&lt;/P&gt;&lt;P&gt; corresponding item.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; If you are dealing with configurable items, you must enter the&lt;/P&gt;&lt;P&gt; configuration data in the tables ORDER_CFGS_REF, ORDER_CFGS_INST,&lt;/P&gt;&lt;P&gt; ORDER_CFGS_PART_OF, ORDER_CFGS_VALUE and ORDER_CFGS_BLOB.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; The scheduling data can be published via the structure&lt;/P&gt;&lt;P&gt; SALES_SCHEDULE_IN.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; Document condtions to be created can be entered via the structure&lt;/P&gt;&lt;P&gt; SALES_CONDITIONS_IN.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; Credit card data can be published via the structure SALES_CCARD, card&lt;/P&gt;&lt;P&gt; identification data on the one hand, data on an authorization that has&lt;/P&gt;&lt;P&gt; taken place in an external system on the other.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; Once you have created the sales document successfully, you will receive&lt;/P&gt;&lt;P&gt; the document number (field SALESDOCUMENT_EX).  (Feld SALESDOCUMENT_EX).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; Errors which might occur will be announced via the parameter RETURN.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Using the checkbox:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can generate the individual components for a sales document with or&lt;/P&gt;&lt;P&gt;without a checkbox. If you decide on the first possibility, only fields&lt;/P&gt;&lt;P&gt;with unequal SPACE will be copied. In the second case (field&lt;/P&gt;&lt;P&gt;UPDATEFLAG), only fields which have an 'X' in the box are copied. As a&lt;/P&gt;&lt;P&gt;result, fields, which are preassigned to default values by the system,&lt;/P&gt;&lt;P&gt;can be set on SPACE again.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Notes&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.  If no object references are to be written, the following fields&lt;/P&gt;&lt;P&gt;    (parameters) should be initialized:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;          BINARY_RELATIONSHIPTYPE&lt;/P&gt;&lt;P&gt;          SALES_HEADER_IN-REFOBJECTTYPE&lt;/P&gt;&lt;P&gt;          SALES_HEADER_IN-REFOBJECTKEY&lt;/P&gt;&lt;P&gt;          SALES_HEADER_IN-REFDOCTYPE&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Rohit&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 27 Apr 2007 10:48:19 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi/m-p/2203475#M471069</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-04-27T10:48:19Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi/m-p/2203476#M471070</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi &lt;/P&gt;&lt;P&gt;Here is the function module documentation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This might help u.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Short Text&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    Creating a Sales and Distribution Document&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  Functionality&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    Using this method, you can create sales documents with items, schedule&lt;/P&gt;&lt;P&gt;    lines and item conditions.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    You must enter at least sales order header data (via the structure&lt;/P&gt;&lt;P&gt;    ORDER_HEADER_IN) and partner data (via the table ORDER_PARTNERS).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    Enter the item data via the table ORDER_ITEMS_IN. You can enter the item&lt;/P&gt;&lt;P&gt;    number manually, by filling in the relevant fields, or automatically,&lt;/P&gt;&lt;P&gt;    corresponding to Customizing, by leaving the relevant fields blank. If&lt;/P&gt;&lt;P&gt;    you decide to enter item numbers using mySAP ERP, no schedule lines or&lt;/P&gt;&lt;P&gt;    conditions can be entered, as these cannot be linked to the&lt;/P&gt;&lt;P&gt;    corresponding item.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    If you are dealing with configurable items, you must enter the&lt;/P&gt;&lt;P&gt;    configuration data in the tables ORDER_CFGS_REF, ORDER_CFGS_INST,&lt;/P&gt;&lt;P&gt;    ORDER_CFGS_PART_OF, ORDER_CFGS_VALUE and ORDER_CFGS_BLOB.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    The scheduling data can be published via the structure&lt;/P&gt;&lt;P&gt;    SALES_SCHEDULE_IN.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    Document condtions to be created can be entered via the structure&lt;/P&gt;&lt;P&gt;    SALES_CONDITIONS_IN.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    Credit card data can be published via the structure SALES_CCARD, card&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    identification data on the one hand, data on an authorization that has&lt;/P&gt;&lt;P&gt;taken place in an external system on the other.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Once you have created the sales document successfully, you will receive&lt;/P&gt;&lt;P&gt;the document number (field SALESDOCUMENT_EX).  (Feld SALESDOCUMENT_EX).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Errors which might occur will be announced via the parameter RETURN.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Using the checkbox:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can generate the individual components for a sales document with or&lt;/P&gt;&lt;P&gt;without a checkbox. If you decide on the first possibility, only fields&lt;/P&gt;&lt;P&gt;with unequal SPACE will be copied. In the second case (field&lt;/P&gt;&lt;P&gt;UPDATEFLAG), only fields which have an 'X' in the box are copied. As a&lt;/P&gt;&lt;P&gt;result, fields, which are preassigned to default values by the system,&lt;/P&gt;&lt;P&gt;can be set on SPACE again.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;identification data on the one hand, data on an authorization that has&lt;/P&gt;&lt;P&gt;taken place in an external system on the other.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Once you have created the sales document successfully, you will receive&lt;/P&gt;&lt;P&gt;the document number (field SALESDOCUMENT_EX).  (Feld SALESDOCUMENT_EX).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Errors which might occur will be announced via the parameter RETURN.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Notes: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If no object references are to be written, the following fields&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; BINARY_RELATIONSHIPTYPE&lt;/P&gt;&lt;P&gt; SALES_HEADER_IN-REFOBJECTTYPE&lt;/P&gt;&lt;P&gt; SALES_HEADER_IN-REFOBJECTKEY&lt;/P&gt;&lt;P&gt; SALES_HEADER_IN-REFDOCTYPE&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Deepti&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 27 Apr 2007 10:52:01 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi/m-p/2203476#M471070</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-04-27T10:52:01Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi/m-p/2203477#M471071</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;check...&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_thread" href="https://community.sap.com/" __jive_macro_name="thread" modifiedtitle="true" __default_attr="377173"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;this has solution which u can use it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;reward if useful.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 27 Apr 2007 10:52:17 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi/m-p/2203477#M471071</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-04-27T10:52:17Z</dc:date>
    </item>
  </channel>
</rss>

