Scribd Logo
Upload

Welcome to Scribd!

  • Wrong Price Update Issue

    Uploaded by

    Srinivasa Reddy Kotha
    119 views2 pages
    A custom program updated product hierarchy values and pricing on open sales orders from CRM, but incorrectly also updated invoiced (closed) sales orders, setting prices to zero. This was because the BAPI used treated the logic switch parameter as indicating a "trusted source" and updated values without checks, instead of only updating open orders. A solution is needed to prevent invoiced orders from being updated in the future.

    Original Description:

    Original Title

    Wrong Price Update Issue.doc

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    A custom program updated product hierarchy values and pricing on open sales orders from CRM, but incorrectly also updated invoiced (closed) sales orders, setting prices to zero. This was because the BAPI used treated the logic switch parameter as indicating a "trusted source" and updated values without checks, instead of only updating open orders. A solution is needed to prevent invoiced orders from being updated in the future.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOCX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as docx, pdf, or txt
    119 views2 pages

    Wrong Price Update Issue

    Uploaded by

    Srinivasa Reddy Kotha
    A custom program updated product hierarchy values and pricing on open sales orders from CRM, but incorrectly also updated invoiced (closed) sales orders, setting prices to zero. This was because the BAPI used treated the logic switch parameter as indicating a "trusted source" and updated values without checks, instead of only updating open orders. A solution is needed to prevent invoiced orders from being updated in the future.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOCX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as docx, pdf, or txt
    of 2

    Issue: Sales orders update in PH Go-Live What happened?

    ? Zero prices updated on invoiced sales orders which were came from CRM. Why it was happened? Requirement is like below 1) Update the product hierarchy values on open and invoiced (Closed) sales order item level. 2) Update the new pricing procedure for only open sales orders. NOT for closed or invoiced. For this created one time custom program ZUVO2494. As per logic in program ZUVO2494, Passing all the open sales orders with below parameters to BAPI BAPI BAPI_SALESORDER_CHANGE EXPORTING Sales order Number Order_header_inx Logic_switch TABLES Return Order_item_in Order_item_inx

    Here Logic_switch has structure with below fields and populated with below values PRICING ATP_WRKMOD SCHEDULING NOSTRUCTURE COND_HANDL = B -> to carry out the new pricing

    = X -> this will not create a new entry but update the existing one

    But BAPI has treating Logic_switch-Cond_handl like below.


    * * * * * * * Split up handling of header conditions into two different cases: a) standard R/3 handling via function module SD_SALES_CONDITION_MAINTAIN (every line checked and processed sperately) b) handling of header condition coming from a so called 'trusted source' as e.g. MSA or CRM (no checks, just take over result) See also comments at section 10, item processing.

    As per the point B, Invoiced CRM orders got updated with NULL. Proposed solutions : ??????????????

    You might also like