Skip to Content
avatar image
Former Member

inconsistency in BW reportdue to Sales orders archiving

1.) Sometimes Sales Contracts/Sales Orders get archived when saved. Sales documents u201Cnot in the database or have been archivedu201D as per ECC design are coming up in the BW reports, one of the reports being the open contracts reports.

All the data is coming from ECC.

2.) Since these contracts are coming up in the open contracts report but do not exist in the ECC database, the business is getting contracts that are not relevant to them. Is there any way to control that if the contract is archived when saved should not consider by the BW report. Without BW reload how can we prevent ECC to not to send archived Sales document to BW.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Aug 05, 2011 at 11:25 AM

    Dear Naveen,

    It sounds like you are getting an update termination while saving the sales orders/contracts. This means that the system could not save the document correctly. A document number is generated but no sales order / contract was created. If this happens again you can get more details on what happened in transaction ST22 (for the short dump) and SM13 (update rrequests).

    It seems the issue of BW being updated with the order number could be caused by user exit code.

    The following is the call stack when the user saves the sales order:

    program MV45AF0b_BELEG_SICHERN (update document)

    CALL FUNCTION 'RV_SALES_DOCUMENT_UPDATE' IN UPDATE TASK
    ......
    * Userexit
          PERFORM USEREXIT_SAVE_DOCUMENT.
    
    * Statistik-Fortschreibung
          PERFORM STATISTIK_UPDATE.
    ....
      COMMIT WORK.
    ....
    ENDFORM.
    

    -> 1) all internal tables e.g. xvbap and yvbap are passed to the

    update module RV_SALES_DOCUMENT_UPDATE in update task.

    -> 2) afterwards USEREXIT_SAVE_DOCUMENT and Statistic update is called.

    -> commit work initiates update.

    Issues could be caused if values are changed in the user exit. If for example an error occurs after the COMMIT WORK and the system needs to make a rollback. Please have your ABAPer go through the short dump in ST22 if this issue occurs again. Also check user exits in MV45AFZZ, MV45AFZA and MV45AFZB to ensure there are no COMMIT WORK statements in your custom code.

    I hope this helps.

    Best regards,

    Ian Kehoe

    Add comment
    10|10000 characters needed characters exceeded