Credit/Debit Memo Request Approval Workflow

Hi All,
I have this requirement of activating a workflow for credit and debit memo requests.
It should be that the approvers will be determined by:
1. Amount
2. Order reason code (if error in data entry - CSR manager, if price error - Sales manager, etc.)
3. Product category (prescription, nutritional, etc)
4. Sales Organization and Distribution Channel
My question is, can I use the HR org structure to determine my approvers? Can it identify approvers/personnels related per sales area and all that criteria? I want to use the HR Org structure because it makes it easier to move/traverse the approval process on a 1up basis (direct manager). I've heard about needing something like cost centers and delegated authorities to link the HR org structure with the workflow, but I'm really lost at this point.
Really appreciate your help!

In our project,we had a similar requirement.
For this,I suggest you to create a new Ztable for holding the values for the fields.The approvers will be maintained by using the personnel number which is being from HR team.
We have written an ABAP code which is being called in save exit of the sales order.
Then an E-mail will be triggered to teh approver and the approver will approve the request by checking in SBWP T.Code.

Similar Messages

  • Credit/debit memo request

    1) credit memo request - After create invoice in vf01, then if credit memo needed, must create credit memo request in va01 then only can create credit memo in fb75?
    2) debit memo request - After create invoice in vf01, then if debit memo
    needed, must create debit memo request in va01 then only can create debit memo in fb70?
    3) credit/debit memo can only be created after credit/debit memo request is created?
    4) if credit/debit memo not created in fb75/fb70, where in sd can create?
    5) credit/debit memo request done via which tcode if not va01.

    Hi Eliana,
    1. A transaction that reduces Amounts Receivable from a customer is a credit memo. For eg. The customer could return damaged goods.  A debit memo is a transaction that reduces Amounts Payable  to a vendor because, you send damaged goods back to your vendor.
    2. Credit memo request is a sales document used in complaints processing to request a credit memo for a customer. If the price calculated for the customer is too high, for example, because the wrong scale prices were used or a discount was forgotten, you can create a credit memo request. The credit memo request is blocked for further processing so that it can be checked. If the request is approved, you can remove the block. The system uses the credit memo request to create a credit memo.
    You can use credit memos in Sales and Distribution (SD) for assigning credit memo requests to the open invoices and in Financial Accounting (FI) for assigning  credit memos and payments to the open invoices and carry out clearing with them.  If you use both Financial Accounting (FI) and Sales and Distribution (SD),  there is a 1:1 relationship between the credit memo request and the credit memo item posted in Financial Accounting (FI). As soon as you bill the credit memo request together with other sales orders, or distribute the items of one credit memo request to several billing documents, the assignment is no longer valid and the system will not process it.
    For  credit memos, credit memo requests, and payments, you have the following assignment options:
    - Assignment to a single invoice
    - Assignment of a partial amount to an invoice
    - Assignment to several invoices
    When you post  credit memos, the payment programme processes them automatically. If the credit memo is specifically related to a particular open invoice item, the payment program automatically attempts to offset the credit memo against the open item. If it is not possible to completely offset the credit memo against an invoice, you can post a debit memo to the vendor, who is to reimburse the amount.  Then you can apply a multilevel dunning program. 
    3.  Debit memo request is a sales document used in complaints processing to request a debit memo for a customer. If the prices calculated for the customer were too low, for example, calculated with the wrong scaled prices, you can create a debit memo request. The debit memo request can be blocked so that it can be checked. When it has been approved, you can remove the block. It is  like a standard order. The system uses the debit memo request to create a debit memo.
    4.  As mentioned above, creating a credit or debit memo request enables you to create credit or debit memos based on a complaint. For this first create a sales document with the order type for a credit or debit memo  request. You can create the debit  or credit memo requests in the following ways: 
    – Without reference to an order
    – With reference to an existing order
    Here you enter which order the complaint refers to.
    – With reference to an invoice
    Here you enter which invoice the complaint refers to.
    In all cases, you specify the value or quantity that should be in the credit or debit memo
    5. You can block the credit or debit memo  request from being billed in Customizing. Go to Sales -> Sales Documents -> Sales document header -> Define sales document type and select the billing block field in the billing section.  This request can later be reviewed along with similar ones, - if necessary, by another department. The request for a credit or debit memo  can then be approved or rejected.
    Credit memo and debit memo is created used the T.Code VF01, in which we have to choose the billing type as Credit Memo or Debit Memo.
    Credit Memo Request or Debit Memo request are created using T.Code VA01, in which we have to select document type as G2 or L2.
    Hope this gives you some idea.

  • Credit/Debit Memo Request with reference to Billing document via IDoc

    Hello Experts,
    It seems SAP doesn't support Credit/Debit Memo Request with reference to Billing document via IDoc. Via IDoc, we can create sales document only with reference to contract or quotation but not with reference to billing/invoice document.
    Wanted to check if anybody came across such requirement and what would be the best way to acheive (Other than custom program using BAPI).
    Additional Information: Its ECC 6.0 Environment with AFS 6.03
    Appreciate your help.

    Please Help... it is Urgent...  Thank you

  • Credit / Debit Memo Request Using XI

    I need some help regarding posting Credit / Debit Memo Requests to create invoices from an external system to SAP.  I want to know the best solution for this using XI (PI), whether there is a BAPI or it would be better to use iDoc, RFC or proxies.  I've been searching SDN but haven't found anything based on this criteria.  I was able to find BAPI_ACC_INVOICE_RECEIPT_POST, but am trying to figure out if it does what I need and whether it is possible to use this with XI.
    I need something that will update tables BSEG and BKPF, but I'm unable to find much information.
    Also if some examples could be provided, I would appreciate it.

    I usually create memo requests with IDOC orders
    (the same as with creation of standard sales order)
    the only thing I program additionally is which lines to take from the SO
    to this memo request (but it's easy as this idoc uses batch input)
    then you can create an invoice from such a memo request in SAP
    either manually or with a use of standard reports
    Michal Krawczyk

  • Billing Block for Credit/Debit Memo Can Be Removed Via TCode VA02

    Dear All,
    During the credit/demo memo request creation, there will be a billing block that will be released via tcode v.23. I realized that user is also able to release the billing block if refer back to the credit/debit memo request at tcode va02.
    Kindly advise how can I prevent superuser/expert user from removing the billing block this way when they have to request for approval from their upper management  to release the billing block ia v.23.
    Appreciate all of your inputs on this enquiry.
    Thank you in advance!

    Hi Friend,
    There are two solutions for this
    You can use USER EXIT    USEREXIT_FIELD_MODIFICATION in MV45AFZZ and create one Ztable and add the user details .
    This will restrict the users to change the Billing Block 
    Also search for the OSS notes for more info   208245
    Create Transaction variant in SHD0  FOR VA02  and make Billing block in display  after creating the sales order.
    Hope it is clear,

  • Workflow Approval for AR Credit/Debit Memo

    Hi All,
    I am looking for document on setting up Approval workflow for AR Credit / Debit Memo. Can any one share me document on how to set up AME for AR credit / debit memo approval.
    Thanks & Looking forward to your reply. Please send the document to [email protected]
    Siva Kalyan.

    Thanks John,
    the function module which you suggested SD_SALESDOCUMENT_CREATE has all the fields i require. But, i am not able to find the fields KUNAG (sold to party) and KUNWE (ship to party) in this function module to enter the data.
    If i run the function module by entering all the data, i get the error asking me to enter ship to party and sold to party. Could you please help me out in finding these fields.
    Thanks & Regards!

  • Enter sold-to party debit memo request - credit memo request

    Hi Gurus,
    I have a scenario here while creating a Debit memo request.
    1. I create a Debit memo request with sold-to party 1000
    2. I create a Credit memo request with the same sold-to party 1000.
    That will be saved,
    but when you enter VA02 or VA03 for CMR, a message displays "Enter a Sold-to Party".
    So in VA02, I will refill it with Sold-to party 1000, then I can save it.  But when I view it again, I will encounter the same message again.
    However, if I use a different sold-to party 2000, the CMR will be saved normally, and if you view it via VA02, you will see it is correct (you can see sold-to party 2000).
    Why?  Cant I use the same sold-to party for DMR to CMR?
    Please help....

    Check whether the partner functions are mantained properly for customer 1000. Go to VD01 and maintain.

  • Add debit memo request to Sap credit exposure formula

    can any body plz suggest me how to add debit memo request(DR) to sap credit exposure formula.

    We have a requirement from business to create debit memo request with refernce to a credit memo
    Both are created wit refrance to order or billing document or without.
    Still you want it then set copy controll for this in VTFA , VTAA

  • Debit memo request with reference to the credit memo request

    Dear SD Consultants,
    I have a business scenario in which I create a credit memo request with reference to a debit memo request but the problem is that ,i can create many debit memo requests with reference to the same credit memo request even if the all target quantity was referenced , I still can create many debit memo requests with reference to the credit memo request so can any one tell me how to restrict creating debit memo request with reference to the credit memo request up till the all target quantity was referenced.
    SD Consultant

    Dear Saju.S,
    I have checked all the positive/negative values in the item copy control but none of the values works as i still can create many debit memo requests with reference to the credit memo request.
    Sd Consultant

  • BAPIs to create sales orders for Returns and Debit Memo Request

    I have to create a sales order for document type Returns as well as a debit memo request.The BAPI 'BAPI_SALESORDER_CREATEFROMDAT2' is giving the following error message for Debit Memo Request document creation as well as for Returns.
    761 Unpermitted combination of business object BUS2032 and sales doc. category L
    I found BAPIs:
    ‘BAPI_CUSTOMERRETURN_CREATE’ for creating sales document of type ZDRE and SD document category ‘H’.
    ‘BAPI_DEBITREQUEST_PROXY_CREATE’ for creating sales document of type ZDDR and SD document category ‘L’.
    please let me know if anybody have used them. If so what values need to be passed to I_UPLOAD_ID,I_DESTIN,I_SFA_REL parameters of BAPI_DEBITREQUEST_PROXY_CREATE. Are there any alternative solutions using the Salesorder bapi.
    I have to create documents based on the flat file data no reference sales document numbers are available.
    Appreciate your help..
    Good Day

    Look at the code done by me
    Program Name:                                                        *
    SAP Name    : ZAXXXXXX               Version    :                    *
    Programmer  : Chris Dong of ITDC                    *
    Description :                                                        *
    Includes        :                                                    *
    Function Modules: XX_XXXXXX                                          *
    Transactions    :                                                    *
    Programs        :                                                    *
                     LINE-COUNT 65
                     MESSAGE-ID ZA
                     NO STANDARD PAGE HEADING.
    CLEAR l_order_partners.
    l_order_partners-partn_role = 'AG'.
    l_order_partners-partn_numb = '0001202491'.
    APPEND l_order_partners TO li_order_partners.
    CLEAR l_order_partners.
    l_order_partners-partn_role = 'WE'.
    l_order_partners-partn_numb = '0001202491'.
    APPEND l_order_partners TO li_order_partners.  
    Sales document type
    l_order_header_in-doc_type = 'ZDR'.  
    Sales organization
    l_order_header_in-sales_org = '1000'. 
    Distribution channel
    l_order_header_in-distr_chan = '01'.  
    l_order_header_in-division = '04'. 
    l_order_header_in-REF_DOC = '9100000144'.
    order reason
    l_order_header_in-ord_reason = '925'.
    item number
    l_order_items_in-itm_number = '000001'. 
    material no
    l_order_items_in-material = '000000000007000012'. 
    l_order_items_in-target_qty = '0000000000100.000'. 
    APPEND l_order_items_in TO li_order_items_in. 
    *BUS2094 Credit memo request " OSS NOTE 93091
    *BUS2096 Debit memo request " OSS NOTE 93091
    ORDER_HEADER_IN = l_order_header_in
    SALESDOCUMENT = l_vbeln
    RETURN = li_return
    ORDER_ITEMS_IN = li_order_items_in
    ORDER_PARTNERS = li_order_partners
    Message was edited by:
            Chris Dong

  • Debit Memo Request Issue

    Dear friends,
    The copy controls are set for  a) Sales Order to Debit memo request (VTAA) & b) Billing to Debit Memo Request (VTAF)
    Scenario #1. Sales Order Qty  is 10 No (Delivery and Billing done for 10 Nos) and I have created a DMR for qty 5 Nos with reference to the sales order  and created the Debit Memo.
    Now when I create one more DMR with reference to the same sales order, the qty referenced in the DMR is 15 No
    Scenario #2. Sales Order Qty  is 10 No (Delivery and Billing done for 10 Nos) and I have created a DMR for qty 5 Nos with reference to the Billing doc and created the Debit Memo.
    Now when I create one more DMR with reference to the same Billing doc, the qty referenced in the DMR is 10 No
    1. While creating a Credit Memo Request or Debit Memo request whats the standard reference document to be used? Is it Sales order or a Billing doc?
    2. I have tested this using standard doc types and I think this is not the correct behaviour.
    In both the scenarios, the referenced qty should be 5No when you are creating the DMR for the second time.
    Somebody let me know what should be the Ideal way to do it......

    Hi Isaac,
    In transaction code VTAA goto OR to DR  and look for your Item Category and in that there is a field by name Pos./neg. quantity
    and in that you will find the help details as shown below:
    The below details will help you for all the documents like Quotatio, Sales Order , billing etc.
    Quantity is calculated positively, negatively or not at all                                                                               
    Indicates whether, during copying, the quantity or value in the target  
         document has a negative effect, positive effect, or no effect at all on 
         the quantity still to be completed in the source document.                                                                               
    The system uses this indicator to determine how the quantity in the     
         source document is affected. For example, if you                                                                               
    o   Create a quotation item for 100 pieces,                                                                               
    o   Copy the quotation into a sales order, and                                                                               
    o   Create a sales order item for 80 pieces,                                                                               
    the copying has a positive effect on the quotation. In effect, you have 
         added 80 pieces to the quotation quantity that is now considered        
         complete. 20 pieces in the quotation remain to be completed.            
      If you do not make an entry in this field, or set indicator 0, the     
      source document is not blocked, which allows you to create several     
      target documents at once (for example, when using EDI and frequent     
      contract releases).                                                                               
    While the source document (such as quotation or quantity contract) is  
      being processed, it is blocked. For instance, if you are working on a  
      quantity contract, no one can create a release order for that contract).
                                                                                    In sales documents, for example, you can expect the following results: 
    o   Quotation   -> Sales order: positive                                                                               
    o   Contract    -> Return: negative                                                                               
    o   Sales order -> Sales order: no effect                                                                               
    In billing documents, for example, you can expect the following results:
    o   Delivery    -> Invoice: positive                                                                               
    o   Delivery    -> Cancellation: negative                                                                               
    o   Delivery    -> Pro-forma invoice: no effect         

  • Foreign trade data in Credit/Debit Memo

    Foreign trade default data are not copied in to Credit/Debit Memo. I have set customizing, and assign foreign trade default procedure for proper Item Categories (G2N and L2N). What can I do more?
    Edited by: Malgorzata Paraficz on Nov 16, 2010 1:42 PM

    after doing the settings in ITEM CATEGORIES.
    if it is not executing.
    then you are requested to go into
    VTFF - copy controls for L2 - F2 as well as G2 - F2 basing on your requriment. select it and go to details.
    in that screen in determne export data you will fine two options A - cpy export data in delivery and B - redermine export.
    i think that you have to go for B.
    because you said that you are not able to redetermine the export data.

  • Automatic Credit/Debit Memo linked to Usage Decision Code

    Dear SAP Masters,
    Can any one help me in setting up a process in system for automatic creation of Credit/Debit memo on selection of usage decision code in notification?
    Points will be awarded to any useful reply.
    Thanks and regards

    Dear Sir
    What is you business can you explain it in detailed?
    Because there is facility available to create (SDMR) Service Debit Memo Request  or SCMR(Service credit memo request) against the order & not notification.
    if you tell me ur business i can put more focus on it .

  • Credit & Debit Memo Issue

    Hi All,
    Once i created the Billing and issue to the Customer , my problem is due to some reason my client want to increase or decrease the price for that particular Invoice or Multiple Invoices
    and also one more important point is accounting document is open (  Payment is not happened ) some invoices
    I have checked the Retro billing Its not working
    Can you please tell me how to handle this In SAP because i am new to this scenario

    In VOV8 you can check that Invoice Correction document has "D" as indicator due to which there are two item generated for Copy control, which you can check in VTAF ( copy from Invoice to Order).
    Invoice correction request, has SD doc category as K - Credit memo request, and Indicator as D - Invoice correction request.
    The indicator "D - Invoice correction request" will control the debit and credit line with the difference.
    The standard docment type is RK (T.code VOV8) define in the system for invoice correction request. The credit memo (G2 as standard) will be created as billing document.
    An invoice correction request has the following structure:
    This contains the data that is relevant for the whole invoice correction request, e.g. sold-to party and payer.
    Item pairs
    The system creates two items in the invoice correction request for each item in the invoice:
                         Item              Indicator
    First item       Credit item     Credits
    Second item   Debit item      Debits
    You can also set the system so that it doesnu2019t repeat pricing.
    You can control this in Customizing under Sales and Distribution  Billing  Billing documents Maintain copying control for billing documents in the Pricing type field.
    The contents of the field depend on the category of the invoice correction request.
    Sales document category    Field contents
    CR (credit memo request)   E
    DR (debit memo request)    F
    You can run new pricing for the debit memo request by defining another pricing category in the pricing category field 2.
    3.  In the credit item, the system completely credits the incorrect invoice item. You cannot change the credit item (apart from the Deletion, Reason for rejection, Billing block and Account assignment fields).  Enter the correct price or quantity in the debit memo item. You can let a new pricing run for the item. The correct amount is finally posted.
    4.  The system calculates the difference between the credit and debit memo item. If there are several corrected items, the system cumulates the values of all the items and calculates a total value.
    5.  As in credit and debit memo requests, you can:
    - Set a billing block for the invoice correction request (or change the settings in the billing type in Customizing so that the system does it automatically).
    - Enter a reason for rejection for one or several items. 
    You can only delete credit items together with their corresponding debit items. You delete items that you havenu2019t changed with a function.
    7.  The system generates a credit memo. If the total value is positive, the credit memo item does not have a + sign, if the total value is negative, it has a u2013 sign.
    If the invoice correction request is characterized as a debit memo request, the opposite occurs.
    8. The title of the printout for the credit or debit memo depends on the characteristic that has been assigned to it (sales document category) and not the total value:
    Sales document category     Title
    CR (credit memo request)   Credit memo
    DR (debit memo request)    Debit memo
    In the credit item, the system credits the customer with the full value. If you change the debit item (for example, due to new pricing or a change in quantities), this results in a difference amount.
    The price condition types used in invoice and in the invoice correction has to be the same. (new condition type added in invoice correction will be ignored).

  • Creating a debit memo request with reference to an invoice

    An invoice shows wrong MWST value because of incorrect customer tax classification as Tax exempt. I corrected the cust tax classification to "Liable for Tax". Then I tried to create a debit memo request with reference to the incorrect invoice. Thats a requirement by the customer. Invoices with incorrect VAT are not to be cancelled. A specially created VAT only sales order (Debit memo request) is used to create a sales order with 0 net value and correct MWST . But while trying to create the debit memo request, the system picks up the same old condition record for the MWST. How to overcome this situation ?
    The copy control for the item category from billing doc to debit memo request is set to "B" that is  new pricing. I even tried to update pricing. But it does not work. Changing the Service rendered date or the pricing date to current date also does not help.
    Please help.

    This is working fine. What I did was
    1: create a new pricing procedure
    2: made the PR00 condition statistical
    3: using a routine calculate the MWST based on the PR00. But PR00 itself does not contribute to the net value. This part is working fine. I could create debit memos successfully.
    The problem is if we change either the customer or the material tax classification after creating the invoice, and then create a debit request with reference to the incorrect invoice, the system still considers the old tax classfication and therefore the old MWST rate. If I create a debit request without reference, the new rate is applicable.
    I hope I have made clear.

Maybe you are looking for