Message No BS027 - Create Sales Document is not Allowed

Hi All
I have created a status profile zfm00001 copying the status profile FM000001.
I have created a new user status as OPEN in which I have allowed all the transactions including create sales document.
All the possible transactions in Funds Management object type is set as allowed.
After I release these status for " * " FC & " * " CI for 2011, All other transactions are working properly.
I am getting an error during Sales Order creation as " Message No BS027 - Create Sales Document is not Allowed", even though I have set the status for "Create sales document" as allowed.  I am going wrong somewhere..Please help
Rgds

Hi,
Please, maintain in BS12, VA01-relevant business  transactions for object type FS0.
Regards,
Eli

Similar Messages

  • Delta changes in R/3 sales document are not coming into CRM

    Hi Middleware experts,
    We are on CRM 5.0 SP 005 with ECC 5.0 SP 007 and using the scenario X for sales documents replication.
    Now the order is created in CRM and successfully transfered to R/3. I can see 3 Bdocs in SMW01 with green lights. First Bdoc says 'R/3 adapter is called', second Bdoc says 'the order is successfully saved' and displays a warning 'The sales document is not yet complete: Edit data' and third Bdoc has no messages. Also I do not see any struck queues in CRM and in R/3
    I am able to edit the sales document in both the systems as per the scenario X. Now I have completed and saved the document in R/3. Surprisingly these changes are not coming into CRM and no new entries in SMW01. Also R/3 SMQ1 and CRM SmQ2 doesn't show any entries. I am also not able to debug, since I do not see any Bdocs in SMW01.
    Now, if I changes the document in CRM and these changes are coming into R/3.
    Also all documents created in R/3 are successfully going into CRM including delta changes in R/3.
    I do not have any clue on what is happening? Highly appreciated, if you can help me.
    Thanks,
    PK

    Hi PK,
    In R3AC1 only we put the filter. So if you do not have any other filter then make sure that you are changing the order which was created not before the date mentioned.
    I would recommend you to just deregister the CRM system in R/3 Transaction SMQS and do some changes in the orders and check any queues are getting created corresponding to that order, If yes that means filter is not an issue. Then debug the queue and find the exact problem. Also make sure that the order you are changing in R/3 is of the same order type what you have mentioned in the filter.
    Make sure to registor back the CRM other wise all the queues will get stuck in R/3 outbound.
    <b>Reward points if it helps!!</b>
    Best regards,
    Vikash.
    Message was edited by: Vikash Krishna

  • Sales document was not changed BAPI

    Hi Experts,
            Am trying to upload sales documents using BAPI_SALESDOCU_CREATEFROMDATA1, but am getting an error like "sales document was not changed". here is my sample code. Thanks in Advance.
    TYPE-POOLS : TRUXS.
    types : BEGIN OF TY_file,
    auart TYPE auart,
    vkorg TYPE vkorg , "
    vtweg TYPE vtweg ,
    spart TYPE spart ,
    KUNNR  TYPE kunnr ,
    KUNNR1  TYPE kunnr ,
    matnr TYPE matnr  ,
    dzmeng TYPE dzmeng  ,
    WERKS_d TYPE werks_d ,
    END OF TY_file.
    *TYPES : tt_file TYPE STANDARD TABLE OF ty_file.
    data : it_file TYPE TABLE OF TY_FILE,
                   wa_file TYPE TY_file.
    PARAMETERs : p_file TYPE IBIPPARMS-PATH.
    at SELECTION-SCREEN on VALUE-REQUEST FOR p_file.
       PERFORM browse_file.
       START-OF-SELECTION.
       PERFORM LOAD_FLAT_FILE.
       PERFORM CALL_BAPI_CREATE.
    FORM browse_file .
    CALL FUNCTION 'F4_FILENAME'
      IMPORTING
        FILE_NAME           = p_file
    ENDFORM.                    " browse_file
    FORM LOAD_FLAT_FILE .
       DATA : LT_RAW TYPE TRUXS_T_TEXT_DATA.
       CALL FUNCTION 'TEXT_CONVERT_XLS_TO_SAP'
         EXPORTING
           I_FIELD_SEPERATOR          = 'X'
          I_LINE_HEADER              = 'X'
           I_TAB_RAW_DATA             = LT_RAW
           I_FILENAME                 = P_FILE
         TABLES
           I_TAB_CONVERTED_DATA       = IT_FILE
        EXCEPTIONS
          CONVERSION_FAILED          = 1
          OTHERS                     = 2
       IF SY-SUBRC = 0.
         MESSAGE 'UPLOADED' TYPE 'I'.
           ENDIF.
    ENDFORM.                    " LOAD_FLAT_FILE
    FORM CALL_BAPI_CREATE .
    DATA: v_vbeln            LIKE vbak-vbeln.
    DATA: header             LIKE bapisdhead1.
    DATA: headerx            LIKE bapisdhead1x.
    DATA: item               LIKE bapisditem  OCCURS 0 WITH HEADER LINE.
    DATA: itemx              LIKE bapisditemx OCCURS 0 WITH HEADER LINE.
    DATA: partner            LIKE bapipartnr  OCCURS 0 WITH HEADER LINE.
    DATA: return             LIKE bapiret2    OCCURS 0 WITH HEADER LINE.
    DATA: lt_schedules_inx   TYPE STANDARD TABLE OF bapischdlx
                              WITH HEADER LINE.
    DATA: lt_schedules_in    TYPE STANDARD TABLE OF bapischdl
                              WITH HEADER LINE.
    LOOP AT IT_FILE INTO WA_FILE.
       header-doc_type = WA_FILE-auart.
       headerx-doc_type = 'X'.
       header-sales_org = WA_FILE-vkorg.
       headerx-sales_org = 'X'.
       header-distr_chan  = WA_FILE-vtweg.
       headerx-distr_chan = 'X'.
       header-division = WA_FILE-spart.
       headerx-division = 'X'.
       headerx-updateflag = 'I'.             " flag for create a new document
       partner-partn_role = 'AG'.
       partner-partn_numb = WA_fILE-KUNNR.
       APPEND partner.
       partner-partn_role = 'WE'.
       partner-partn_numb = WA_fILE-KUNNR1.
       APPEND partner.
       itemx-updateflag = ''.
       item-itm_number = '000010'.
       itemx-itm_number = 'X'.
       item-material = WA_FILE-matnr.
       itemx-material = 'X'.
       item-plant    = WA_FILE-WERKS_d.
       itemx-plant   = 'X'.
       item-target_qty = WA_fILE-dzmeng.
       itemx-target_qty = 'X'.
       APPEND item.
       APPEND itemx.
       lt_schedules_in-itm_number = '000010'.
       lt_schedules_in-sched_line = '0001'.
       lt_schedules_in-req_qty    = WA_FILE-DZmeng.
       APPEND lt_schedules_in.
       lt_schedules_inx-itm_number  = '000010'.
       lt_schedules_inx-sched_line  = '0001'.
       lt_schedules_inx-updateflag  = 'X'.
       lt_schedules_inx-req_qty     = 'X'.
       APPEND lt_schedules_inx.
       CALL FUNCTION 'BAPI_SALESDOCU_CREATEFROMDATA1'
            EXPORTING
                 sales_header_in     = header
                 sales_header_inx    = headerx
            IMPORTING
                 salesdocument_ex    = v_vbeln
            TABLES
                 return              = return
                 sales_items_in      = item
                 sales_items_inx     = itemx
                 sales_schedules_in  = lt_schedules_in
                 sales_schedules_inx = lt_schedules_inx
                 sales_partners      = partner.
    *  LOOP AT return WHERE type = 'E' OR type = 'A'.
    *    EXIT.
    WRITE : / RETURN-NUMBER, RETURN-TYPE, RETURN-MESSAGE.
    *  ENDLOOP.
    *  IF sy-subrc = 0.
    *    WRITE: / 'Error in creating document'.
    *  ELSE.
    *    COMMIT WORK AND WAIT.
    *    WRITE: / 'Document ', v_vbeln, ' created'.
    *  ENDIF.
    *  LOOP AT RETURN.
    *WRITE : / RETURN-NUMBER, RETURN-TYPE, RETURN-MESSAGE.
       ENDLOOP.
       END

    Hi Experts,
            Am trying to upload sales documents using BAPI_SALESDOCU_CREATEFROMDATA1, but am getting an error like "sales document was not changed". here is my sample code. Thanks in Advance.
    TYPE-POOLS : TRUXS.
    types : BEGIN OF TY_file,
    auart TYPE auart,
    vkorg TYPE vkorg , "
    vtweg TYPE vtweg ,
    spart TYPE spart ,
    KUNNR  TYPE kunnr ,
    KUNNR1  TYPE kunnr ,
    matnr TYPE matnr  ,
    dzmeng TYPE dzmeng  ,
    WERKS_d TYPE werks_d ,
    END OF TY_file.
    *TYPES : tt_file TYPE STANDARD TABLE OF ty_file.
    data : it_file TYPE TABLE OF TY_FILE,
                   wa_file TYPE TY_file.
    PARAMETERs : p_file TYPE IBIPPARMS-PATH.
    at SELECTION-SCREEN on VALUE-REQUEST FOR p_file.
       PERFORM browse_file.
       START-OF-SELECTION.
       PERFORM LOAD_FLAT_FILE.
       PERFORM CALL_BAPI_CREATE.
    FORM browse_file .
    CALL FUNCTION 'F4_FILENAME'
      IMPORTING
        FILE_NAME           = p_file
    ENDFORM.                    " browse_file
    FORM LOAD_FLAT_FILE .
       DATA : LT_RAW TYPE TRUXS_T_TEXT_DATA.
       CALL FUNCTION 'TEXT_CONVERT_XLS_TO_SAP'
         EXPORTING
           I_FIELD_SEPERATOR          = 'X'
          I_LINE_HEADER              = 'X'
           I_TAB_RAW_DATA             = LT_RAW
           I_FILENAME                 = P_FILE
         TABLES
           I_TAB_CONVERTED_DATA       = IT_FILE
        EXCEPTIONS
          CONVERSION_FAILED          = 1
          OTHERS                     = 2
       IF SY-SUBRC = 0.
         MESSAGE 'UPLOADED' TYPE 'I'.
           ENDIF.
    ENDFORM.                    " LOAD_FLAT_FILE
    FORM CALL_BAPI_CREATE .
    DATA: v_vbeln            LIKE vbak-vbeln.
    DATA: header             LIKE bapisdhead1.
    DATA: headerx            LIKE bapisdhead1x.
    DATA: item               LIKE bapisditem  OCCURS 0 WITH HEADER LINE.
    DATA: itemx              LIKE bapisditemx OCCURS 0 WITH HEADER LINE.
    DATA: partner            LIKE bapipartnr  OCCURS 0 WITH HEADER LINE.
    DATA: return             LIKE bapiret2    OCCURS 0 WITH HEADER LINE.
    DATA: lt_schedules_inx   TYPE STANDARD TABLE OF bapischdlx
                              WITH HEADER LINE.
    DATA: lt_schedules_in    TYPE STANDARD TABLE OF bapischdl
                              WITH HEADER LINE.
    LOOP AT IT_FILE INTO WA_FILE.
       header-doc_type = WA_FILE-auart.
       headerx-doc_type = 'X'.
       header-sales_org = WA_FILE-vkorg.
       headerx-sales_org = 'X'.
       header-distr_chan  = WA_FILE-vtweg.
       headerx-distr_chan = 'X'.
       header-division = WA_FILE-spart.
       headerx-division = 'X'.
       headerx-updateflag = 'I'.             " flag for create a new document
       partner-partn_role = 'AG'.
       partner-partn_numb = WA_fILE-KUNNR.
       APPEND partner.
       partner-partn_role = 'WE'.
       partner-partn_numb = WA_fILE-KUNNR1.
       APPEND partner.
       itemx-updateflag = ''.
       item-itm_number = '000010'.
       itemx-itm_number = 'X'.
       item-material = WA_FILE-matnr.
       itemx-material = 'X'.
       item-plant    = WA_FILE-WERKS_d.
       itemx-plant   = 'X'.
       item-target_qty = WA_fILE-dzmeng.
       itemx-target_qty = 'X'.
       APPEND item.
       APPEND itemx.
       lt_schedules_in-itm_number = '000010'.
       lt_schedules_in-sched_line = '0001'.
       lt_schedules_in-req_qty    = WA_FILE-DZmeng.
       APPEND lt_schedules_in.
       lt_schedules_inx-itm_number  = '000010'.
       lt_schedules_inx-sched_line  = '0001'.
       lt_schedules_inx-updateflag  = 'X'.
       lt_schedules_inx-req_qty     = 'X'.
       APPEND lt_schedules_inx.
       CALL FUNCTION 'BAPI_SALESDOCU_CREATEFROMDATA1'
            EXPORTING
                 sales_header_in     = header
                 sales_header_inx    = headerx
            IMPORTING
                 salesdocument_ex    = v_vbeln
            TABLES
                 return              = return
                 sales_items_in      = item
                 sales_items_inx     = itemx
                 sales_schedules_in  = lt_schedules_in
                 sales_schedules_inx = lt_schedules_inx
                 sales_partners      = partner.
    *  LOOP AT return WHERE type = 'E' OR type = 'A'.
    *    EXIT.
    WRITE : / RETURN-NUMBER, RETURN-TYPE, RETURN-MESSAGE.
    *  ENDLOOP.
    *  IF sy-subrc = 0.
    *    WRITE: / 'Error in creating document'.
    *  ELSE.
    *    COMMIT WORK AND WAIT.
    *    WRITE: / 'Document ', v_vbeln, ' created'.
    *  ENDIF.
    *  LOOP AT RETURN.
    *WRITE : / RETURN-NUMBER, RETURN-TYPE, RETURN-MESSAGE.
       ENDLOOP.
       END

  • Post order processing for sales document is not yet complete

    hi,
    sap gurus,
    i am facing the error while saving the sales order and this ticket is unique and it is saying that
    "post order processing for sales document is not yet complete".
    please help me in this regard.
    and it is blocking the order for further processing.
    regards,
    balajit

    I dont think this is a standard error message.  Some exit is applied for sale order to meet some requirements.  You need to check with your ABAPer.
    In fact, you can conclude yourself based on the error message number.  If it starts with Z, then the above holds good.
    thanks
    G. Lakshmipathi

  • Sales Document type not defined

    Hi
    I am working on an interface. Design is like below
    Purchase Order->File Adapter->XI (BPM)->RFC Adapter->Sales Order in R/3
    When I am trying to cretae a sales document in R/3, I am getting a message back from R/3 saying 'Sales Document is not defined'. But when Checked in R/3, that sales document type is existing. I don't see any Mapping execption in monitoring, but I am receiveing this message back from R/3
    Any feedback will be highly appreciate.
    Cheers
    Rajiv P

    Hi
    Well initially it was a value-mapping problem. It is possible to debug a BAPI/RFC from XI. If it is possible, the please advise me of the procedure. My XI is working fine but I am getting a message back from R/3 as below. Any feedback will be highly appreciated
    <?xml version="1.0" encoding="UTF-8" ?>
    - <rfc:BAPI_SALESORDER_PROXY_CREATE.Response xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
      <E_SALESDOCUMENT_EX />
      <E_STATUS>E</E_STATUS>
    - <RETURN>
    - <item>
      <TYPE>S</TYPE>
      <ID>V4</ID>
      <NUMBER>233</NUMBER>
      <MESSAGE>SALES_HEADER_IN has been processed successfully</MESSAGE>
      <LOG_NO />
      <LOG_MSG_NO>000000</LOG_MSG_NO>
      <MESSAGE_V1>VBAKKOM</MESSAGE_V1>
      <MESSAGE_V2 />
      <MESSAGE_V3 />
      <MESSAGE_V4 />
      <PARAMETER>SALES_HEADER_IN</PARAMETER>
      <ROW>0</ROW>
      <FIELD />
      <SYSTEM>UD1CLNT010</SYSTEM>
      </item>
    - <item>
      <TYPE>E</TYPE>
      <ID>V1</ID>
      <NUMBER>384</NUMBER>
      <MESSAGE>Sales unit ****** is not defined for item 000000</MESSAGE>
      <LOG_NO />
      <LOG_MSG_NO>000000</LOG_MSG_NO>
      <MESSAGE_V1>******</MESSAGE_V1>
      <MESSAGE_V2>000000</MESSAGE_V2>
      <MESSAGE_V3 />
      <MESSAGE_V4 />
      <PARAMETER>SALES_ITEM_IN</PARAMETER>
      <ROW>1</ROW>
      <FIELD />
      <SYSTEM>UD1CLNT010</SYSTEM>
      </item>
    - <item>
      <TYPE>E</TYPE>
      <ID>V4</ID>
      <NUMBER>248</NUMBER>
      <MESSAGE>Error in SALES_ITEM_IN 000001</MESSAGE>
      <LOG_NO />
      <LOG_MSG_NO>000000</LOG_MSG_NO>
      <MESSAGE_V1>VBAPKOM</MESSAGE_V1>
      <MESSAGE_V2>000001</MESSAGE_V2>
      <MESSAGE_V3 />
      <MESSAGE_V4 />
      <PARAMETER>SALES_ITEM_IN</PARAMETER>
      <ROW>1</ROW>
      <FIELD />
      <SYSTEM>UD1CLNT010</SYSTEM>
      </item>
    - <item>
      <TYPE>E</TYPE>
      <ID>V4</ID>
      <NUMBER>219</NUMBER>
      <MESSAGE>Sales document was not changed</MESSAGE>
      <LOG_NO />
      <LOG_MSG_NO>000000</LOG_MSG_NO>
      <MESSAGE_V1 />
      <MESSAGE_V2>000001</MESSAGE_V2>
      <MESSAGE_V3 />
      <MESSAGE_V4 />
      <PARAMETER />
      <ROW>0</ROW>
      <FIELD />
      <SYSTEM>UD1CLNT010</SYSTEM>
      </item>
    - <item>
      <TYPE>E</TYPE>
      <ID>C_</ID>
      <NUMBER>005</NUMBER>
      <MESSAGE>The object references could not be written to the CRMKEY</MESSAGE>
      <LOG_NO />
      <LOG_MSG_NO>000000</LOG_MSG_NO>
      <MESSAGE_V1 />
      <MESSAGE_V2 />
      <MESSAGE_V3 />
      <MESSAGE_V4 />
      <PARAMETER />
      <ROW>0</ROW>
      <FIELD />
      <SYSTEM>UD1CLNT010</SYSTEM>
      </item>
      </RETURN>
      <TI_EXTENSIONIN />
      <TI_ORDER_CCARD />
      <TI_ORDER_CFGS_BLOB />
      <TI_ORDER_CFGS_INST />
      <TI_ORDER_CFGS_PART_OF />
      <TI_ORDER_CFGS_REF />
      <TI_ORDER_CFGS_REFINST />
      <TI_ORDER_CFGS_VALUE />
      <TI_ORDER_CFGS_VK />
    - <TI_ORDER_CONDITIONS_IN>
    - <item>
      <ITM_NUMBER>000001</ITM_NUMBER>
      <COND_ST_NO>000</COND_ST_NO>
      <COND_COUNT>00</COND_COUNT>
      <COND_TYPE>EDI1</COND_TYPE>
      <COND_VALUE>57.600000000</COND_VALUE>
      <CURRENCY>AUD</CURRENCY>
      <COND_UNIT />
      <COND_P_UNT>1</COND_P_UNT>
      <CURR_ISO />
      <CD_UNT_ISO />
      <REFOBJTYPE />
      <REFOBJKEY />
      <REFLOGSYS />
      <APPLICATIO />

  • Error "The sales document is not yet complete" when using SD_SALES_DOCU_MAINTAIN

    Hi there,
    I have built an update program for updating the sales documents (VA42). In that program I am using the BAPI-SD_SALES_DOCU_MAINTAIN. It works fine except for the sales docs that are incomplete. For those sales docs I have the following messages in the Return-internal tab. from the BAPI:
    V4
    233
    VBAKKOM has been processed successfully
    V4
    233
    VBAPKOM has been processed successfully
    V4
    233
    VBAPKOM has been processed successfully
    V4
    233
    VBAPKOM has been processed successfully
    V1
    555
    The sales document is not yet complete: Edit data
    V1
    311
    Collection Contract 55259592 has been saved
    The sales doc is indeed incomplete. What is missing in this sales doc is the prices. After discussion with the people from the business, I found out that it is impossible to complete those sales docs.
    In the transaction-VA42 it is possible to save such sales docs, after clicking the "Save" button in the pop-up "The sales doc is incomplete. (Save - Edit - Cancel)".
    The standard reports SDVBUV00 and SDVBUK00 do not help.
    Is there any other possibility or other BAPI that I could use to save such sales docs?
    Thanks,
    Dimce

    no issue anymore. On the QA-system it didn't work and on the production one it works.

  • Create Sales Document

    Hi All,
    I am new to SD, MM.
    What are prerequisites to create sales document number?
    How vendor no , Material number, Purchase order.....( in between there are many terms which I don't know ) are linked. I just wanted to know how to create a Sales Document Number from scratch.
    Regards,
    Raghavendra

    hi raghavendra,
    Create a Sales Order, Delivery and Billing Invoice
    • the SD end user, logs into the ECC system to create a sales order.he goes to transaction code va01, enters in sales order type ZOG, fills in the details,presses the Enter key and clicks Save to generate sales order 334.
    • He then creates a delivery for this order by clicking on Sales Document in the top menu and selecting Deliver. he enters Shipping Point BP01, enters in sales order 334 and then Saves to generate delivery 80000
    •He then creates the billing invoice by going to transaction code VF01. he selects Billing Type F8 Pro Forma Invoice for Delivery and clicks Save to generate billing document number 90000088
    Steps:
    1a) Log in to the ECC system. Create a sales order by going to transaction code VA01.
    Enter the following details:
           Order Type ZOG
           Sales Organization BP01
          Distribution Channel 01
          Division 01
    Press the Enter key. Then enter the following details:
         Sold-To Party 31
         Ship-To Party 31
         Purchase Order TESTGTS
         Item 10
         Material 53
         Order Quantity 3
         Plant BP01
    Press the ENTER key and click Save to generate a sales order. Make a note of
    this sales order number.
    1b) Create a delivery for the sales order by clicking on Sales Document
    &#56256;&#56518; Deliver in the top menu and then Deliver. Make a note of the Delivery number.
    1c) Create a F2 billing invoice by going to transaction code VF01.
    Select F8(Proforma Invoice for Delivery), type in the delivery number obtained from step 1b,and click Save. Make a note of the generated billing invoice number.
    regards,
    sravanthi

  • Create sales document with reference document

    Hi Experts:
                    In the case of create sales document ,i set that create sales order with reference a billing document.
                    But i have a problem,the Pricing procedure in billing document is A, after coping from it,the sales document
                    Pricing procedure is A also,it can't work using Pricing Procedure Determination in config.
                    Actually,i want the sales document using a new  pricing procedure.
                    Pls help to give me some advice.
                                                      Thank you very much.
                            Best Regards!

    Go to VOFA, select your billing type and execute.  There maintain a different document pricing procedure from what you maintained for your sale order type in VOV8. 
    Next go to OVKK and assign the new pricing procedure to the document pricing procedure of what you maintained in VOFA
    Finally, go to VTAF, select your source billing document type and order type and execute.  There assign routine 053 for the first "DataT"
    Now try how it works.
    thanks
    G. Lakshmipathi

  • Warning 'sales document is not yet complete' with BAPI_SALESORDER_CHANGE after deleting correspnding delivery

    Hi,
    I'm trying to change a sales order (add some positions) after deleting the corresponding delivery to it.
    But I get the warning "sales document is not yet complete: Edit Data", because of incomplete dates in schedule lines.
    The schedule lines are filled correctly.
    When I have a Sales Order without corresponding delivery, this Order could be changed successful with BAPI BAPI_SALESORDER_CHANGE.
    But if there is a Sales Order with corresponding Delivery (where I do delete the delivery first with BAPI BAPI_OUTB_DELIVERY_CHANGE ), than the BAPI for changing the Order gives a warning "sales document is not yet complete: Edit Data".
    This is confusing.
    Is there something I have to consider when changing a sales order after deleting its delivery?
    Coding:
    "1. delete delivery to sales order
    CLEAR ls_header_data.
       CLEAR ls_header_ctrl.
       ls_header_data-deliv_numb = iv_vbeln.
       ls_header_ctrl-deliv_numb = iv_vbeln.
       ls_header_ctrl-dlv_del    = abap_true. "set flag for deletion
    * call BAPI to delete delivery
       CALL FUNCTION 'BAPI_OUTB_DELIVERY_CHANGE'
         EXPORTING
           header_data    = ls_header_data
           header_control = ls_header_ctrl
           delivery       = iv_vbeln
         TABLES
           return         = et_msg.
    IF ...
    COMMIT WORK AND WAIT.
    ELSE.
    ENDIF.
    "2. change Sales order (adding new item positions)
    "add new/changed data
       LOOP AT IT_NEW_ITEMS ASSIGNING <ls_new_items>.
         CLEAR: ls_order_item_in,
                ls_order_item_inx,
                ls_schedule_line,
                ls_schedule_linex.
         add 10 to lv_posnr.
         ls_order_item_in-itm_number = lv_posnr. "posNr
         ls_order_item_in-material = <ls_new_items>-matnr. "material
         ls_order_item_in-target_qty = <ls_new_items>-menge.  "quantity
         ls_order_item_in-sales_unit = <ls_new_items>-MEINH. "sales unit
         APPEND ls_order_item_in TO lt_order_item_in.
         "fill order item check table
         ls_order_item_inx-itm_number = lv_posnr.
         ls_order_item_inx-updateflag = 'I'.
         ls_order_item_inx-material   = abap_true.
         ls_order_item_inx-target_qty = abap_true.
         ls_order_item_inx-sales_unit = abap_true.
         APPEND ls_order_item_inx TO lt_order_item_inx.
         "schedule lines
         ls_schedule_line-itm_number   = lv_posnr. "posnr
         ls_schedule_line-sched_line   = '1'.
         ls_schedule_line-req_qty      = ls_order_item_in-target_qty. "quantity
         ls_schedule_line-req_date      = lv_lfdate.               "schedule line date
         APPEND ls_schedule_line TO lt_schedule_line.
         "schedule lines check table
         ls_schedule_linex-itm_number   = lv_posnr. "posnr
         ls_schedule_linex-sched_line   = '1'.
         ls_schedule_linex-req_qty      = abap_true. "quantity
         ls_schedule_linex-req_date      = abap_true.               "schedule line date
         ls_schedule_linex-UPDATEFLAG  = 'I'.
         APPEND ls_schedule_linex TO lt_schedule_linex.
       ENDLOOP.
       "call bapi to add items to sales order
       CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
         EXPORTING
           SALESDOCUMENT    = iv_sales_order
           ORDER_HEADER_INX = ls_order_header_inx
         TABLES
           RETURN           = et_msg
           ORDER_ITEM_IN    = lt_order_item_in
           ORDER_ITEM_INX   = lt_order_item_inx
           SCHEDULE_LINES   = lt_schedule_line
           SCHEDULE_LINESX  = lt_schedule_linex.
    IF....
    COMMIT WORK AND WAIT.
    ELSE.
    ENDIF.

    The first thing I would try is to use fm BAPI_TRANSACTION_COMMIT (with parameter WAIT = 'X') instead of COMMIT WORK AND WAIT which is directly put in your code (this is almost the same but not exactly).
    Then make sure that if your code performs two BAPI calls one after the other, they are separated with either a call to fm BAPI_TRANSACTION_COMMIT or BAPI_TRANSACTION_ROLLBACK.
    Then - if the above is applied and still does not help - I would suspect that some invalid / incomplete data is passed to fm BAPI_SALESORDER_CHANGE.
    regards

  • Document assembly not allowed

    I have created several PDF forms using Adobe Designer 7.0 for Windows XP and I want to compile them into a single PDF document using Adobe Acrobat Professional 7.0's "Create PDF from multiple files" option. But when I try, I get a message that "The file (name) is protected. It cannot be used for this command" for each file in turn. When I open the files individually and look at the security settings, I see "Document Assembly: Not Allowed". I was wondering how I could change the settings to allow document assembly. Acrobat Help just tells me to contact the original document author...but I *am* the original document author!

    Once a form is made in Designer, it can't be edited in Acrobat. They are two totally different technologies.

  • The sales unit is not allowed+STO plant to plant

    Dear Friends,
    In plant to plant stock transfer,while creating delivery in VL04,system is giving the following message-
    'The sales unit is not allowed for the  material in item 000010'
    I have not assigned any sales unit to the material still it is giving this error.
    Please advice

    Have a look at the following note:-
    Note 140551 - VL384 Stock transport order and batch selection
    G. Lakshmipathi

  • Sales order does not allow make-to-order production

    Dear Friends,
    I am trying to do do planned order for sales order in MD50 it was showing the error message as
    "Sales order does not allow make-to-order production"
    Can any one solve this
    Shakthi

    Hi Shakthi,
    It is also possible to set the priority for Requirement Type determination like
    0 Material master strategy, then item category and MRP type
    1 Item Category and MRP Type
    2 as 1, with check for allowed requirement type.
    The transaction for this is same as "Requirement Type Determination :
    Sales and Distribution --> Basic Functions --> Availability Check and Transfer of Requirements --> Transfer of Requirements --> Determination Of Requirement Types Using Transaction
    Look for "Source".
    In this transaction, Please, check "Requirements".
    Please, make sure of the following 2 things :
    1. If you do not set an indicator for maintaining the requirements class: Transfer of requirements is not carried out, irrespective of the specification you make at schedule line level for the transaction.
    So it is necessary to mantain the setting first at the Requirements Class. As mentioned in my earlier posts, the requirement class for the material can be found out from Planning Strategy / MRP3 view --> Main strategy (defined in the strategy group) --> Requirement Class for Customer Requirements.
    The IMG path for "Define Strategy" is Production --> Production Planning --> Demand Management --> Planned Independent Requirements --> Planning Strategy --> Define Strategy.
    2. Once the "Requirements" indicator is set in Requirement Class, the requirements indicator at the Schedule Line decides whether or not you require transfer of requirments for the relevant transaction.
    I hope this should solve your problem.
    Regards,
    Sandeep

  • Error message MH 175 "The listing end is not allowed to be in the past"

    Hi,
            While I try to execute listing in the new article creation using particular disctribution chain, i.e. with reference to a Sales Org and distribution channel, the error message MH 175, 'The listing end is not allowed to be in the past' popped up. Can you please help me on what could be the cause for this error to be displayed.
    thank you
    regards
    prahlad

    Hi,
       Go to mm42.. enter the article number and distribution chain and then select the Listing View.... Please check the "Listed to" and "for Sale till" date is in past. if so change the date to future and try agian.
    Regards
    GK

  • Message F5 568: Fiscal year 2010 is not allowed

    Hi All,
    While creating reservation through MB21,
    we are transfernig our stock material from one company code to another company code.
    First company code is activated with CALENDAR YEAR, while the other is with FISCAL YEAR (JUL-JUN)
    While creating the reservation, it prompts the following error
    Message F5 568: Fiscal year 2010 is not allowed
    Any suggestion?
    Warm Regards,
    N

    The error is happening because the company codes invloved have different fiscal year variants assigned to them and SAP does not support constellation.
    However, you may want to try opening period 2010 for both company codes if you've not yet done so and try again to see if you will get the same error.
    Please use transaction code OB29 to open calendar year 2010.  This is done by clicking on periods in OB29.
    Elias
    Edited by: Elias Akorli on Oct 28, 2009 12:20 PM
    Edited by: Elias Akorli on Oct 28, 2009 12:25 PM

  • ERROR MESSAGE : display of the query spec is not allowed

    Hi all,
    I have many queries built under a multiprovider. The problem is if i try to chane a query it is not allowing me to do it. Even for a query which i built it is not allowing. It is displaying an error message 'display of the query spec is not allowed'.
    Can anyone help me in understanding this issue?
    Thanks,
    Raj.

    Have you check your authorizaiton trace with ST01?
    You need authorization for this query in auth obj S_RS_COMP or S_RS_COMP1

Maybe you are looking for