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

Similar Messages

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 />

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

Data of preceding document was not transmitted

HI,
data of preceding document was not transmitted
Im getting the above error i have created SO with respect to Project and Creating Delivery from project in CNS0
While creating delivery for project im getting the error
I have copied Delivery Type from LP to XXXX
When im using delivery type LP and while creating Project delivery that there is no above error but status is not getting change that is Delivery is Open which should be "Delivery Completed" after PGI
Pls Suggest
Thank you,
Regards,
Naveen

SPRO - Logistics General - Handling Unit Management - Materials Management - HU Requirement for Storage Locations and Default Values for Deliveries.
Select the plant and go to the storage location.
Enter the Sales org, Distribution channel, Shipping point, Vendor and Customer.
So then the entry which you create through inventory management will create using this customer for outbound delivery and vendor for inbound delivery, if there is none specified.
Now you can use MB1B to create the delivery for 311 movement type.

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

Error occured for "APP-PO-14090: Document was not created

Hi All,
Can anbody please help for the error occured as
"APP-PO-14090: Document was not created", while creating purchase order through Auto create feature in Purchasing Module.
So request you please help me.
Thanks for your response in advance.
Thanks & Regards,
Ram.V

Hi All,
Thanks for the replies, I found the sollution.
for further references here I am providing the sollution.
The issue happens when ship to bill to location is there but the organization is not given in the location definition form while defining the location. In order to reference the organization to location please perform the following steps:-
1. Go into the responsibility: India Local Inventory
2. Navigate to Oracle Inventory > Setup > Organizations > Locations > Query Location
3. Navigate to Other tab and provide the name of organization. Save changes.
4. Retest the issue.
5. Migrate the solution as appropriate to other environments.
Thanks & Regards,
Ram.V
Edited by: 901012 on Dec 11, 2011 11:31 PM

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.

Production order status was not changed to 'CNF' after final confirmation.

Hi guru.
I experienced very special case that production order status was not changed to CNF after final confirmation.
I did final confirmation and canceled confirmation. (CNF -> REL)
And I did final confirmation again because of fixing activity quantity.
the strange thing is that production order status wasn't changed from REL to CNF.
I did confirmation again with 0 activity, thereby I solved this problem
BUT i don't know why this case happened.
Please, explain the reason.
Thanks.

Hi,
As per my observation, their is not any change in the status of the order REL with confirmation CNF, instead of this, it has change from CRTD & then to TECO.
Sequence of the status of the order as below
1) CRTD MANC NMAT SETC
2) REL NMAT SETC - Changes from CRTD to REL after releasing of the order
3) REL CNF PRC CSER ERTR OPGN SETC - After confirmation, it updated after the order REL status.
Rgd,
Chetan

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

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

The password for the account "account name" was not changed. Your system administrator may not allow you to change your password or there was some other problem with your password. Contact your system administrator for help.

I have a user who's Active Directory password is going to expire. I had her reset her password by going to apple > system prefs > user > and clicking change password. She received the error "The password for the account "account name" was not changed. Your system administrator may not allow you to change your password or there was some other problem with your password. Contact your system administrator for help."
I had her change her password via the kpasswd command in terminal and that changed her password on the server sucessfully however the laptop has FileVault on it. Filevault is not recognizing the new password just the old password.
I have deleted the keychain which didn't resolve and now I am going to decrypt and reencrypt the drive. I'm hoping this is an isolated issue I have over 25 laptops configured like this.

I "think" the trick was unbinding and rebinding the computer account.
After unencrypting and trying to reencrypt Filevault would still not take the new password.
Rebooted the prompt to update the keychain appeared. Updated the keychain. Filevault would still not take the new password.
Unbinded and rebinded the computer account. It worked and let me add the user to filevault.

APP-PO-14090: dOCUMENTS WAS NOT CREATED

Dear all,
I am trying to Auto-create PO from PR 123. however the error appears and error detail is mentioned below.
APP-PO-14090: DOCUMENTS WAS NOT CREATED
POSSSIBLE CUASES:
1: AN EXCEPTIN OCCURED IN THE PO ACCOUNTING GENERATOR WORKFLOW DURING THE DOCUMENT CREATION PROCESS.
2: SOME OTHER ERROR
Regards
Nain

Hello Nain,
Please refer below matalink note, it may help you to resolve your issue.
Troubleshooting Guide To Resolving Error APP-PO-14090: No Requisition Lines Were Autocreated (Doc ID 283494.1)

In sales quotation document number not changed..

hiii guys
i getting some problem in sales quotation about document number.....
actually i opened by another user like sham.he is sales department..he have only sales authorizations..when we press add button, data has been saved..but number not changed... but after saving,we close form and open again then that that time number automatically changed..its comes serial number..when we press add button,,we getting same problem...

hi
I think you got confused with document and draft no on Approval documents.
Ofcourse many user,got this confusion.
The Document number wont be generated in Sales Quotation till you add it(i.e when waiting for approval)
The document number which is shown in that document when pending for the approval, is not the finalised number.
Its just the next number of sales quotaion which wont get stored in sales quotation,rather it will store in Draft table ODRF.
when you have too many documents which is waiting for approval,you can notice that document number will be same for all the other documents.
So you note down the Draft Number which is UNIQUE.
For Ex:
you are creating sales quotation which has the document number as '335'.
so when you sending it for approval the draft number will be staored as '211'.
after getting the approval,when you add it,document number will be generated as '337' because two documents were posted when the draft no:211 is waiting for approval.
revert me for any clarification.
Edited by: kambadasan on Feb 23, 2012 1:41 PM

Error saving multiple Sales document modified by the BAPI (with cnfg)

Dear Sir/Madam,
I have a requirement for which i am modifying a Sales Quotation and
then Sales Contract created w.r.t. Sales Quotation. I am using the
following function modules in sequence specified to modify the
documents:
1. BAPI_CUSTOMERQUOTATION_CHANGE - to change Sales Quotation
2. SD_SALESDOCUMENT_CHANGE - to change the Sales Contract with the
parameter CALL_FROM_BAPI marked as 'X' if the quotation was processed
successfully but not saved to the database
The BAPI transaction commit is called only after both the Sales
documents have been processed successfully. In case there is an error
in updation in any one of the Sales documents then the
BAPI_TRANSACTION_ROLLBACK is called.
After successful processing both the documents are getting commited
with the correct reference of the Quotation item in the contract items.
Now when i view the Sales Contract all updations have happened
successfully and i can view the data properly, also the items
configuration data.
When i go to view the Sales Quotation i can see that the new item which
needed to be added to this document has been added successfully however
when i go to view the configuration data for the newly added item i get
an error V1854 , 'Internal error in communication between configuration
and sales document in the form GET_CONFIG_MODE'.
If i do a commit individually after the each function module call then
all documents are saved properly and can be viewed without any errors.
Please advise why this error is happening.
warm regards,
Nitesh

I think I found a way to get it to do what I want,,,
1) Use the first signature collection lock to lock only the fields that that person is signing-off on.
2) The next manager then signs off and locks only his comments and text boxes, as well as the signature of the preceeding manager. This way text fields are only locked by one signature collection and thus to edit anything you have to clear that manager's signature to edit the related text boxes, then to re-sign that section you must clear the other (higher level) signatures to open up the signature field for resigning,,, I think this is providing the protection I want,,, Yea,,, let's get this form back into our stupid ISO system ;)

Accounting Document was not generated

Hi Friends,
While doing Post goods issue, Material document was created but system does not create accounting document.
One sales order having two items (10&20)
Both iteams having same material
In case of items number 10(system generate accounting document)
In case of Item number 20(System does not generate accounting document)
What could be the reason..
Please help me....
Thanks
NPR

Hi,
Open the billing document number generated using t.code VF02 or VF03. Then from the menu bar choose Environment and choose Account determination analysis revenue account. From there you will see where the correction will be made.
But possible reasons for the error are account 1. account assignment group is not tagged in sales area data in the customer master 2. account assignment group is not tagged in the material master.
Try also releasing the document by clicking on release to accounting icon (green flag)
Thanks.
Rachelle

Sales document was not changed BAPI

Similar Messages

Maybe you are looking for