Debit Memo Request with Reference to Service Order

Hi Team,
I need to create the following business process
Service Notification -> Service Order -> Debit Memo Request -> Debit Memo.
I'm able to create the notification and the service order. However while creating the debit memo request with reference to the service order I'm stuck. Not sure where and how do I give the reference document number for the data to flow from the Service Order to Debit Memo Request.
Regards
Nadarajah Pratheb

Hi Nadarajah,
The following may help you.
1.Check the sales document category of the service order you are using.
2. Check which kind of document given in the with reference screen has the same sales document category.
3. For that document type, enter the service order as the reference.
4. Now you can see the details getting copied to the debit memo request.
5. Make sure copy controls are properly maintained from service order to debit memo request.
Please assign reward points if it helps.

Similar Messages

  • Creating a debit memo request with reference to an invoice

    Hi,
    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.
    Regards.

    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.
    Regards.

  • 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.
    Thanks,
    Shekhar.

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

  • 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.
    Regards,
    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.
    Regards,
    Sd Consultant

  • Message V1478 - Credit memo request with reference to an invoice

    Dear all,
    Creating a credit memo request with reference to an invoice, I get the following message "Material in item 000060 does not exist in plant/storage location".
    Of course, this material exists in the plant and the storage location, as we could create the invoice without any problem.
    Any idea?
    Best regards,
    Iné

    Hello
    Generally, these errors may appear due to:
    - The plant is marked for deletion.
    - The plant should be copied from the referenced item.
    So, I would suggest you to
    - Check copying control for Invoice to Credit memo request, particularly, item.
    - Try and create Credit Memo Request with reference to sales order.
    - Or if you want rectify a invoice, then use invoice coreection request.
    Thanks & Regards
    JP

  • Credit Memo request with reference to billing document

    Dear all,
    I am having a requirement to create credit memo request with reference to Billing document. But the issue is, I have separate pricing procedure for normal sales to billing, and different pricing procedure for CMR to Credit memo.
    When I am creating CMR with reference to Billing document it copies the pricing procedure, Please suggest how to block pricing procedure to get copied. (please note that B: redetermine pricing, is not working in this case)
    Suitable points for valuable answers guerenteed.
    Regards
    Bidhu

    Hi,
    In VTAF maintain the folowing parameters,
    HEADER
    053,103 and 03 in the Data T in this order from top to bottom,maintain 021 in the billing header box and check the copy item number box.
    ITEM
    153,104,004 in the Data T in this order from top to bottom,maintain 303 in the copying requirements box and pricing type E.
    This should resolve your issue.

  • Credit Memo request with reference to Billing Document number via IDoc

    Hi,
    I want to create credit memo request with reference to billing document number via IDocs.
    I have tried through ORDERS05, but when I process I saw that it is only processing with reference to contract  number or quotation.
    So is any other way of creating credit memo request creation with reference to Billing document number via IDocs?
    Thank you in advance.
    Regards,
    Santhi

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

  • Credit memo request with reference to many invoices

    Hello All
    I am having a business case where  the user trying to create a credit memo request with reference to the invoice which is already issues to the customer
    there he realized there are around 60 line item from different invoice has to be created for the same payer
    Is there is any way where we could create one credit memo request with reference to many invoices for only one payer?
    Thanks

    Hello,
    I doubt whether this can be possible to create a credit memo request from many invoice's line items together.....
    But it is (the answer given above) worth trying in your test/ QA system before recommending it to the user.
    Regards,
    SAM

  • Create sales order with reference to service order

    Hi
    I need to create sales order based on the service order . Is there any BAPI function module available for this ?
    Please help...
    Regards
    Sujith

    ** プログラムID       : ZBAPI_SALESORDER_CREATE               *
    ** プログラム名称         : Upload Sales Order Creation                   *
    ** 処理概要           :                                       *
    ** 作成者           : Karthik.P                             *
    ** 作成日           : 2006/08/10                            *
    REPORT  ZBAPI_SALESORDER_CREATE LINE-SIZE 132 MESSAGE-ID ZMMBAPI .
           Internal table definition                                     *
    ****<<<<<Communication Fields: Sales and Distribution Document Header>>>>>>>>
    DATA: GT_ORDER_HEADER_IN LIKE BAPISDHD1,
    *******<<<Checkbox Fields for Sales and Distribution Document Header>>>>>>>>>
          GT_ORDER_HEADER_INX  LIKE    BAPISDHD1X,
    *****<<<<<Return Parameter>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
          GT_RETURN LIKE BAPIRET2 OCCURS 0 WITH HEADER LINE,  " Return Messages
    *********<<<Communication Fields: Sales and Distribution Document Item<>>>>>
          GT_ORDER_ITEMS_IN LIKE BAPISDITM OCCURS 0 WITH HEADER LINE, " Item Data
    *********<<<Communication Fields: Sales and Distribution Document Item>>>>>>>
          GT_ORDER_ITEMS_INX LIKE BAPISDITMX OCCURS 0 WITH HEADER LINE, "Item Data Checkbox
    *********<<<Communication Fields: Sales and Distribution Document Item>>>>>>>
          GT_SALESDOCUMENT LIKE BAPIVBELN-VBELN , "Number of Generated Document
    *********<<<Communications Fields: SD Document Partner: WWW>>>>>>>>>>>>>>>>>>
          GT_ORDER_PARTNERS  LIKE BAPIPARNR OCCURS 0 WITH HEADER LINE, "Document Partner
    ********<<<<Communications Fields: SD Document Partner: WWW>>>>>>>>>>>>>>>>>>
          GT_ORDER_SCHEDULES_IN LIKE BAPISCHDL OCCURS 0 WITH HEADER LINE, "Schedule Line Data
    ****<<<<<<<<Checkbox List for Maintaining Sales Document Schedule Line>>>>>>>>
          GT_ORDER_SCHEDULES_INX LIKE BAPISCHDLX OCCURS 0 WITH HEADER LINE, " Checkbox Schedule Line Data
    *******Communication Fields for Maintaining Conditions in the Order
          GT_ORDER_CONDITIONS_IN  LIKE BAPICOND OCCURS 0 WITH HEADER LINE,
    ******Communication Fields for Maintaining Conditions in the Order
          GT_ORDER_CONDITIONS_INX LIKE BAPICONDX OCCURS 0 WITH HEADER LINE.
           Data definition                                               *
    DATA:  BEGIN OF GT_FT_SALES OCCURS 0,
           DOC_TYPE(4)  ,        "Sales Document Type
           SALES_ORG(4) ,        "Sales Organization
           DISTR_CHAN(2)  ,      "Distribution Channel
           DIVISION(2)   ,       "DIVISION(2)
           SALES_DIST(6)  ,      "Sales district
           INCOTERMS1(3)  ,      "Incoterms (part 1)
           INCOTERMS2(28)  ,     "Incoterms (part 2)
           PMNTTRMS(4)  ,        "Terms of payment key
           PRICE_DATE(8) ,       "Date for pricing and exchange rate
           PURCH_NO_C(35)  ,     "Customer purchase order number
           PURCH_NO_S(35)  ,     "Ship-to Party's Purchase Order Number
           EXCHG_RATE(8)  ,      "Directly quoted exchange rate for pricing and statistics
           CURRENCY(5) ,         "SD document currency
           MATERIAL(18),         "MATERIAL
           TARGET_QTY(13)  ,     "Target quantity in sales units
           ITEM_CATEG(4)  ,      "Sales document item category
           MATL_GROUP(8)  ,      "Material Group
           PURCH_NO_C1(35),      "Customer purchase order number
           SALES_DIST1(6)  ,     "Sales district
           INCOTERMS11(3)  ,     "Incoterms (part 1)
           INCOTERMS21(28),     "Incoterms (part 2)
           PMNTTRMS1(4)  ,     "Terms of payment key
           EXCHG_RATE1(8) ,    "Directly quoted exchange rate for pricing and statistics
           PRICE_DATE1(8) ,    "Date for pricing and exchange rate
           TRG_QTY_NO(5)    , "Factor for converting sales units to base units (target qty)
           DIVISION1(2)     ,                                   "DIVISION1
           SALQTYNUM(5)     , "Numerator (factor) for conversion of sales quantity into SKU
           GROSS_WGHT(3)    , "Gross Weight of the Item
           NET_WEIGHT(15)    , "Net Weight of the Item
           UNTOF_WGHT(3)    ,"Weight Unit
           PARTN_ROLE(2)   ,"Partner function
           PARTN_NUMB(10)   ,"Customer Number 1
    ********<<<<Communications Fields: SD Document Partner: WWW>>>>>>>>>>>>>>>>>>
           ITM_NUMBER(6) ,"Item number of the SD document
           REQ_QTY(8)  , "Schedule line date
           DLV_DATE(8)  , "Schedule line date
           MS_DATE(8)  , "Material availability date
           LOAD_DATE(8) , "Loading time (local time with reference to a shipping point)
           GI_DATE(8), "Time of goods issue (local DATE, with reference to a plant)
           TP_DATE(8)  , "Transportation planning -time (local w/ref. to shipping pnt)
           ITM_NUMBER2(6) , "Condition item number
    END OF GT_FT_SALES,
           MSG(240) TYPE  C,  " Return Message
           E_REC(8) TYPE C,    " Error Records Counter
           REC_NO(8) TYPE C, " Records Number Indicator
           S_REC(8) TYPE C,   " Successful Records Counter
           T_REC(8) TYPE C.   " Total Records Counter
    selection block for EXCEL UPLOAD FILE>>>>>>>>>>>>>>>>>>>>>>>>
    SELECTION-SCREEN BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-000.
      PARAMETERS FILE TYPE  IBIPPARMS-PATH OBLIGATORY.
    SELECTION-SCREEN END OF BLOCK B1.
    *<<<<AT SELECTION-SCREEN ON VALUE-REQUEST FOR FILE .>>>>>>>>>>>>
    AT SELECTION-SCREEN ON VALUE-REQUEST FOR FILE .
      CALL FUNCTION 'F4_FILENAME'
        EXPORTING
          PROGRAM_NAME  = SYST-CPROG
          DYNPRO_NUMBER = SYST-DYNNR
        IMPORTING
          FILE_NAME     = FILE.
    **<<<<<<<<<<<<<<<<<START-OF-SELECTION.>>>>>>>>>>>>>>>>>>>>>>>>>>>
    START-OF-SELECTION.
      CALL FUNCTION 'WS_UPLOAD'                                 "#EC *
        EXPORTING
          FILENAME                = FILE
          FILETYPE                = 'DAT'
        TABLES
          DATA_TAB                = GT_FT_SALES
        EXCEPTIONS
          CONVERSION_ERROR        = 1
          FILE_OPEN_ERROR         = 2
          FILE_READ_ERROR         = 3
          INVALID_TYPE            = 4
          NO_BATCH                = 5
          UNKNOWN_ERROR           = 6
          INVALID_TABLE_WIDTH     = 7
          GUI_REFUSE_FILETRANSFER = 8
          CUSTOMER_ERROR          = 9
          NO_AUTHORITY            = 10
          OTHERS                  = 11.
      IF  SY-SUBRC <> 0  .
        MESSAGE E000.
      ENDIF.
      SKIP 3.
      FORMAT COLOR COL_HEADING INVERSE ON.
        WRITE 40 TEXT-001.
      FORMAT COLOR COL_HEADING INVERSE OFF.
      SKIP 1.
      FORMAT COLOR COL_NEGATIVE INVERSE ON.
        WRITE :/ TEXT-002, 13 SY-MANDT , 104 TEXT-003, 111 SY-UNAME,
                  / TEXT-004, 13 SY-DATUM , 104 TEXT-005, 111 SY-UZEIT.
      FORMAT COLOR COL_NEGATIVE INVERSE OFF.
      SKIP 3.
      LOOP AT GT_FT_SALES.
          PERFORM SLALE_UPLOAD_DATA.
      ENDLOOP.
      T_REC = E_REC + S_REC.
      SKIP 3.
      FORMAT COLOR COL_TOTAL INVERSE ON.
        WRITE: /38 TEXT-007, T_REC.
      FORMAT COLOR COL_TOTAL INVERSE OFF.
      FORMAT COLOR COL_NEGATIVE INVERSE ON.
        WRITE: /38 TEXT-008, E_REC.
      FORMAT COLOR COL_NEGATIVE INVERSE OFF.
      FORMAT COLOR COL_TOTAL INVERSE ON.
        WRITE: /38 TEXT-009, S_REC.
      FORMAT COLOR COL_TOTAL INVERSE OFF.
    *&      Form  SLALE_UPLOAD_DATA
          text
    -->  p1        text
    <--  p2        text
    FORM SLALE_UPLOAD_DATA .
    *******<<<<<<<<<<Communication Fields: Sales and Distribution Document Header>>>>>>
        GT_ORDER_HEADER_IN-DOC_TYPE =    'TA'.
        GT_ORDER_HEADER_IN-SALES_ORG =  GT_FT_SALES-SALES_ORG . "'0001'
        GT_ORDER_HEADER_IN-DISTR_CHAN = GT_FT_SALES-DISTR_CHAN. "'01'
        GT_ORDER_HEADER_IN-DIVISION  =   GT_FT_SALES-DIVISION.  " '01'
        GT_ORDER_HEADER_IN-SALES_DIST = GT_FT_SALES-SALES_DIST ."'000001'
        GT_ORDER_HEADER_IN-INCOTERMS1 = GT_FT_SALES-INCOTERMS1.  "'CFR'
        GT_ORDER_HEADER_IN-INCOTERMS2 = GT_FT_SALES-INCOTERMS2 . "'HAMBURG'
        GT_ORDER_HEADER_IN-PMNTTRMS = GT_FT_SALES-PMNTTRMS .    "'0001'
        GT_ORDER_HEADER_IN-PRICE_DATE = GT_FT_SALES-PRICE_DATE ."'20060818'
        GT_ORDER_HEADER_IN-PURCH_NO_C =  '32'.
        GT_ORDER_HEADER_IN-PURCH_NO_S =   '32'.
        GT_ORDER_HEADER_IN-EXCHG_RATE =  GT_FT_SALES-EXCHG_RATE ."'1.00000'
        GT_ORDER_HEADER_IN-CURRENCY = GT_FT_SALES-CURRENCY . " 'EUR'
    ********<<<Checkbox Fields for Sales and Distribution Document Header>>>>>>>>>
        GT_ORDER_HEADER_INX-DOC_TYPE   = 'X'.
        GT_ORDER_HEADER_INX-SALES_ORG  = 'X'.
        GT_ORDER_HEADER_INX-DISTR_CHAN = 'X'.
        GT_ORDER_HEADER_INX-DIVISION   = 'X'.
        GT_ORDER_HEADER_INX-SALES_DIST = 'X'.
        GT_ORDER_HEADER_INX-INCOTERMS1 = 'X'.
        GT_ORDER_HEADER_INX-INCOTERMS2 = 'X'.
        GT_ORDER_HEADER_INX-PMNTTRMS =   'X'.
        GT_ORDER_HEADER_INX-PRICE_DATE = 'X'.
        GT_ORDER_HEADER_INX-PURCH_NO_C = 'X'.
        GT_ORDER_HEADER_INX-PURCH_NO_S = 'X'.
        GT_ORDER_HEADER_INX-EXCHG_RATE =  'X'.
        GT_ORDER_HEADER_INX-CURRENCY = 'X'.
    *****<<<<<<Communication Fields: Sales and Distribution Document Item>>>
        GT_ORDER_ITEMS_IN-ITM_NUMBER = '000010'.
        GT_ORDER_ITEMS_IN-MATERIAL  =  GT_FT_SALES-MATERIAL .
        GT_ORDER_ITEMS_IN-PO_ITM_NO = '32'.
        GT_ORDER_ITEMS_IN-CUST_MAT22 = 'AGNI-IV'.
        GT_ORDER_ITEMS_IN-BILL_DATE = '20060808'.
        GT_ORDER_ITEMS_IN-PLANT = '0001'.
    *GT_ORDER_ITEMS_IN-STORE_LOC = '0001'.
        GT_ORDER_ITEMS_IN-TARGET_QTY = GT_FT_SALES-TARGET_QTY . "'1000'
        GT_ORDER_ITEMS_IN-ITEM_CATEG = GT_FT_SALES-ITEM_CATEG . "'TAN'
        GT_ORDER_ITEMS_IN-MATL_GROUP = GT_FT_SALES-MATL_GROUP . "'01'
        GT_ORDER_ITEMS_IN-PURCH_NO_C = GT_FT_SALES-PURCH_NO_C . "'32'
        GT_ORDER_ITEMS_IN-SALES_DIST = GT_FT_SALES-SALES_DIST . "'000001'
        GT_ORDER_ITEMS_IN-INCOTERMS1 = GT_FT_SALES-INCOTERMS1 . "'CFR'
        GT_ORDER_ITEMS_IN-INCOTERMS2 = GT_FT_SALES-INCOTERMS2 . "'HAMBURG'
        GT_ORDER_ITEMS_IN-PMNTTRMS = GT_FT_SALES-PMNTTRMS  .    "'0001'.
        GT_ORDER_ITEMS_IN-EXCHG_RATE = GT_FT_SALES-EXCHG_RATE . "'1.00000'
        GT_ORDER_ITEMS_IN-PRICE_DATE = GT_FT_SALES-PRICE_DATE . "'20060808'
    *GT_ORDER_ITEMS_IN-SALES_UNIT = 'DZ'.
        GT_ORDER_ITEMS_IN-TRG_QTY_NO = GT_FT_SALES-TRG_QTY_NO . "'23'
        GT_ORDER_ITEMS_IN-DIVISION = GT_FT_SALES-DIVISION   .   "'01'
        GT_ORDER_ITEMS_IN-SALQTYNUM = GT_FT_SALES-SALQTYNUM .   "'32'
        GT_ORDER_ITEMS_IN-GROSS_WGHT = GT_FT_SALES-GROSS_WGHT.  " ' 25272000'
        GT_ORDER_ITEMS_IN-NET_WEIGHT = GT_FT_SALES-NET_WEIGHT.  "'24464000'
        GT_ORDER_ITEMS_IN-UNTOF_WGHT = GT_FT_SALES-UNTOF_WGHT . " 'KG'
    *GT_ORDER_ITEMS_IN-CURRENCY = 'EUR'.
        APPEND  GT_ORDER_ITEMS_IN.
    ****<<<<<<Communication Fields: Sales and Distribution Document Item>>>
        GT_ORDER_ITEMS_INX-ITM_NUMBER = '000010'.
        GT_ORDER_ITEMS_INX-MATERIAL = 'X'.
    *GT_ORDER_ITEMS_INX-PO_ITM_NO = 'X'.
        GT_ORDER_ITEMS_INX-CUST_MAT22 = 'X'.
        GT_ORDER_ITEMS_INX-BILL_DATE = 'X'.
        GT_ORDER_ITEMS_INX-PLANT = 'X'.
    *GT_ORDER_ITEMS_INX-STORE_LOC = 'X'.
        GT_ORDER_ITEMS_INX-TARGET_QTY = 'X'.
        GT_ORDER_ITEMS_INX-ITEM_CATEG = 'X'.
        GT_ORDER_ITEMS_INX-MATL_GROUP = 'X'.
        GT_ORDER_ITEMS_INX-PURCH_NO_C = 'X'.
        GT_ORDER_ITEMS_INX-SALES_DIST = 'X'.
        GT_ORDER_ITEMS_INX-INCOTERMS1 = 'X'.
        GT_ORDER_ITEMS_INX-INCOTERMS2 = 'X'.
        GT_ORDER_ITEMS_INX-PMNTTRMS = 'X'.
        GT_ORDER_ITEMS_INX-EXCHG_RATE = 'X'.
        GT_ORDER_ITEMS_INX-PRICE_DATE = 'X'.
    *GT_ORDER_ITEMS_INX-SALES_UNIT = 'X'.
        GT_ORDER_ITEMS_INX-TRG_QTY_NO = 'X'.
        GT_ORDER_ITEMS_INX-DIVISION = 'X'.
        GT_ORDER_ITEMS_INX-SALQTYNUM = 'X'.
        GT_ORDER_ITEMS_INX-GROSS_WGHT =  'X'.
        GT_ORDER_ITEMS_INX-NET_WEIGHT = 'X'.
        GT_ORDER_ITEMS_INX-UNTOF_WGHT = 'X'.
    *GT_ORDER_ITEMS_IN-CURRENCY = 'x'.
        APPEND  GT_ORDER_ITEMS_INX.
    *****<<<<<<Communications Fields: SD Document Partner: WWW
        GT_ORDER_PARTNERS-PARTN_ROLE =   'WE'.
        GT_ORDER_PARTNERS-PARTN_NUMB =  '0000000057'.
    ***GT_ORDER_PARTNERS-ITM_NUMBER = GT_FT_SALES-ITM_NUMBER . " '000010'.
        APPEND  GT_ORDER_PARTNERS.
    *********<<<<Communications Fields: SD Document Partner: WWW>>>>>>>>>>>>>>>>>>
        GT_ORDER_SCHEDULES_IN-ITM_NUMBER = GT_FT_SALES-ITM_NUMBER." '000010'
        GT_ORDER_SCHEDULES_IN-REQ_QTY = GT_FT_SALES-REQ_QTY .   "'234'
        GT_ORDER_SCHEDULES_IN-DLV_DATE = GT_FT_SALES-DLV_DATE  ."  '20060824'.
        GT_ORDER_SCHEDULES_IN-MS_DATE =  GT_FT_SALES-MS_DATE .  "'20060808'
        GT_ORDER_SCHEDULES_IN-LOAD_DATE = GT_FT_SALES-LOAD_DATE.  " '20060822'
        GT_ORDER_SCHEDULES_IN-GI_DATE = GT_FT_SALES-GI_DATE . " '20060823'
        GT_ORDER_SCHEDULES_IN-TP_DATE = GT_FT_SALES-TP_DATE .   "'20060821'
        APPEND  gt_ORDER_SCHEDULES_IN.
    *********<<<<Communications Fields: SD Document Partner: WWW FLAG>>>>>>>>>>>>>>>>>>
        GT_ORDER_SCHEDULES_INX-ITM_NUMBER = '000010'.
        GT_ORDER_SCHEDULES_INX-REQ_QTY = 'X'.
        GT_ORDER_SCHEDULES_INX-DLV_DATE = 'X'.
        GT_ORDER_SCHEDULES_INX-MS_DATE = 'X'.
        GT_ORDER_SCHEDULES_INX-LOAD_DATE = 'X'.
        GT_ORDER_SCHEDULES_INX-GI_DATE = 'X'.
        GT_ORDER_SCHEDULES_INX-DLV_DATE = 'X'.
        APPEND  gt_ORDER_SCHEDULES_INX.
    ********Communication Fields for Maintaining Conditions in the Order
        GT_ORDER_CONDITIONS_IN-ITM_NUMBER = GT_FT_SALES-ITM_NUMBER ." '000010'
        APPEND GT_ORDER_CONDITIONS_IN.
    ***Communication Fields for Maintaining Conditions in the Order
        GT_ORDER_CONDITIONS_INX-ITM_NUMBER = '000010'.
        APPEND GT_ORDER_CONDITIONS_INX.
        CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'
          EXPORTING
       SALESDOCUMENTIN               =
            ORDER_HEADER_IN               = GT_ORDER_HEADER_IN
            ORDER_HEADER_INX              = GT_ORDER_HEADER_INX
      SENDER                        =
      BINARY_RELATIONSHIPTYPE       =
      INT_NUMBER_ASSIGNMENT         =
      BEHAVE_WHEN_ERROR             =
      LOGIC_SWITCH                  =
      TESTRUN                       =
      CONVERT                       = ' '
         IMPORTING
           SALESDOCUMENT                  = GT_SALESDOCUMENT
          TABLES
           RETURN                         = GT_RETURN
            ORDER_ITEMS_IN                = GT_ORDER_ITEMS_IN
            ORDER_ITEMS_INX               = GT_ORDER_ITEMS_INX
            ORDER_PARTNERS                = GT_ORDER_PARTNERS
           ORDER_SCHEDULES_IN            =  GT_ORDER_SCHEDULES_IN
           ORDER_SCHEDULES_INX           =  GT_ORDER_SCHEDULES_INX
           ORDER_CONDITIONS_IN           =  GT_ORDER_CONDITIONS_IN
           ORDER_CONDITIONS_INX          =  GT_ORDER_CONDITIONS_INX
      ORDER_CFGS_REF                =
      ORDER_CFGS_INST               =
      ORDER_CFGS_PART_OF            =
      ORDER_CFGS_VALUE              =
      ORDER_CFGS_BLOB               =
      ORDER_CFGS_VK                 =
      ORDER_CFGS_REFINST            =
      ORDER_CCARD                   =
      ORDER_TEXT                    =
      ORDER_KEYS                    =
      EXTENSIONIN                   =
      PARTNERADDRESSES              =
        IF GT_RETURN-TYPE EQ 'E' .
          E_REC = E_REC + 1.
          READ TABLE GT_RETURN WITH KEY ID = 'V1'.
          FORMAT COLOR COL_NEGATIVE INVERSE ON.
          REC_NO = E_REC + S_REC.
              CONCATENATE TEXT-006 REC_NO ':'
              GT_RETURN-MESSAGE INTO MSG SEPARATED BY SPACE .
              CONDENSE MSG.
              WRITE: / MSG.
          FORMAT COLOR COL_NEGATIVE INVERSE OFF.
      ELSEIF GT_RETURN-TYPE EQ 'S'.
          S_REC = S_REC + 1.
          FORMAT COLOR COL_POSITIVE INVERSE ON.
              MSG = GT_RETURN-MESSAGE.
              CONDENSE MSG.
              WRITE: / MSG .
          FORMAT COLOR COL_POSITIVE INVERSE OFF.
         PERFORM COMMIT_MM.
    ENDIF.
          CLEAR:  GT_RETURN[], MSG.
    ENDFORM.                    " SLALE_UPLOAD_DATA
    *&      Form  COMMIT_MM
          text
    -->  p1        text
    <--  p2        text
    FORM COMMIT_MM .
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
          EXPORTING
            WAIT   = 'X'
          IMPORTING
            RETURN = GT_RETURN.
      clear:      GT_ORDER_ITEMS_IN[],GT_ORDER_CONDITIONS_IN[].
    ENDFORM.                    " COMMIT_MM

  • Credit Memo Request w.r.t Service Orders

    Hi All
    We want to create Credit Memo request (CMR ) as follow up w.r.t CRM Service Orders, as of now below process is available
    Service order --> Confirmation --> Invoice --> CMR --> Credit Note.
    can anyone helpe me in configuring the below process
    Service order -->  CMR --> Credit Note.
    Best Regards
    Nagaraj G

    Hello Nagaraj
    The service order posts the planned cost in the system. and your requirement is to reduce the planned costs from the system by creating credit memo request in the system.
    As per the OSS message also this credit memo request will reduce the actual Cost/revenue not the planned cost/revenue.
    What i believe is  if you want to reduce the plan cost/ revenue. You just reduce the value in the service order itself rather than creating the credit memo request.
    Please let me know if i understood your scenario correctly below.
    you created a service order and planned cost/revenue  is posted into the system and later you realized that this service are not actually performed and there is no service confirmation is posted in the system. but you want to remove planned cost also from the internal order. 
    So in this above case i would suggest you either change the value in the service order itself. or cancel your service order.
    regards
    Naresh

  • Down payment request with reference to sales order

    Hi all,
    I have configured a down payment scenario integrated with SD module for delivery based order.
    the flow is working fine when I post the down payment with transaction f-29 and insert the reference to the sales order (without item).
    but when i try to do the same process using also the step of down payment request f-37 the system force me to insert also the item of the sales order in the down payment request. in fact the system issue error message
    Enter the item number
        Message no. V1125
    Diagnosis
        You have entered a sales document number without the item number.
        However, the item number is necessary.
    Procedure
        Enter the item number."
    I'm using special GL indicator "A" in both transaction.
    any idea?
    thanks
    Paolo

    Hi
    This could be possible if you activate the Business Function SD_01 delived in EhP 2 in ECC 6.0. Note this activation is an irreversable function.
    Read the utilities of the function for more details.
    Regards
    Sanil Bhandari

  • Copy Control from Billing doc to Debit memo request

    hi,
    we are trying to sort the follwing problem out. We create a debit memo request with reference to the invoice, we then change the sold to party, however the pricing is carried out again. we want to retain the invoice values but only change the sold to party and quantities. i have change the copy control to "copy pricing elements unchanged" however it still reprices the debit memo.

    Hi,
    As per your question, You have invoiced customer X wants to issue debit memo request to  customer Y.
    How come is it possible?Could you elaborate the scenario?
    SAP system retrieve master data from sold -to-party record for Sales order and also  access ship-to-party record for delivery and access Payer's record for Billing.
    You change sold to party in Debit memo request.SAP system access record of new sold-to-party  for debit memo req.(It is sales order type).
    In T-code VTAF - You  changed Pricing type to D-copy pricing elements unchanged.It is not sufficient to fulfill your requirement.In this transaction other Data transfer routine also affects copying.These are Data transfer routine 104(business data item billing) and 004(Billing item partner).
    Data transfer routine allow you to fine tune the transferred fields during the copying process.It specifies the item business data to be transferred from a billing document item to a sales document item.Special checks are also performed to be sure that SOLD -TO-PARTY IS THE SAME PRIOR TO initiating data transfer of the item related business data.Iten related business data are incoterms,taxes discount applicable to Sold-to-party.
    In your case sold-to- party is changed.It also changes business data and pricing.
    Hope it would help you.
    Thanks,
    Vrajesh

  • How to avoid more than one debit memo request referenced to an invoice

    Hello Experts,
    Please if you have answer to the following question let me know it, the case is the following:
    I can create a debit memo request with reference to an invoice more than once time, which means I can have many debit memos request with whole reference to the same invoice number. How can I avoid it or notify to the user while creating a debit memo request that an invoice number has already a created debit memo request.
    I already check the requirement and transfer routines in copy control but I cannot use table VBFA to verify if there is a previous debit memo request, and also I verify the configuration of the debit memo request.
    Thanks a lot for your help.
    Best Regards

    Hello,
    You're saying that you cannot check VBFA for previous Debit Memo Requests - is this because the previous Debit Memo Requests do not appear in the invoice's document flow? If so, please check Copying Control: Billing Document to Sales Document (item) - is the Update document flow box checked?
    Regards,
    Joã

  • Add debit memo request to Sap credit exposure formula

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

    Hi.
    We have a requirement from business to create debit memo request with refernce to a credit memo
    HOW IT IS FESIABLE TO CREATE ???
    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
    Kapil

  • 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....
    Ram

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

Maybe you are looking for

  • Uploading and reading file from application server

    Hi My problem is when am uploading a file to application server it is getting stored in usr/sap/transyp1/prod/in   directory after that i want to read that file from application server to update database when  using below code it is showing some othe

  • Tutorial: Print index cards without removing paper from tray for Officejet Pro 8000.

    The HP Officejet Pro 8000 and Officejet Pro 8000 wireless do not have a slot for inserting index cards and envelopes. If you are wanting to print index cards without removing the paper from the tray, follow these steps. The steps below are for 3 x 5

  • Error when trying to load OEM on OEL5 OC4J_DBConsole

    I have 11g installed on OEL5, I am able to connect to it via SQL on the server itself and from clients, I am currently importing the DB from a client and added it to the 9i OEM tree from my old 9i server without an issue. Believe this is an enviormen

  • FBZP APP configuration - Urgent

    Hi sap guru's, I had encountered with the following problem.  Our client has 3 a/c's with a bank SBI at same branch(mumbai) and he issues cheques from all 3 a/c's. Here how the configuration should be done for check payment method for APP.  can any o

  • Please provide the external testing process in QM

    Hi,            My client want to MAP external testing process in their business scenario.pls update me how we can MAP in our QM process.           process is :-                          1) Material sample will go to external testing (external vendor)