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.

Similar Messages

  • Debit memo and credit memo rule

    hi
    may i know why there is debit memo like bank transfer(debit memo), returned debit memo, check debit memo
    and credit memo like check credit memo through bank
    in posting rule.
    what is the meaning of debit memo and credit memo in posting rule of electronic banking.
    thanks

    hi elina,
    Debit Memo - It 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.
    Credit Memo - 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.
    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.
    T.codes FB75 or FB70
    To create Credit / Debit Memo request:
    - Use the same procedure that you use for Creating Sales Orders i.d T Code VA01
    - Give Order Type as CR for Credit Memo and DR for Debit Memo reuest
    While creating the request you have to enter Customer Number, Reason for the request. and Material and its quantity. Once the credit or debit memo request is released you can create credit or debit memo. The credit memo request will be automatically blocked for checking with Billing Block 08 (to check credit memo) & 09 (to check debit memo) for the sales order type “CR”
    ranjit

  • Diff bet credit memo and credit memo request

    Hi
    Can any one tell the difference between Credit Memo and Credit Memo Request
    Thanks in advance

    Hi,
    Below is the information on crdit memo request.
    Definition: A credit memo request is a sales document used in complaints processing to request credit for a customer.
    Use: If the price calculated for the customer was too high (for example, with the wrong scaled prices or because a discount was forgotten), you can create a credit memo request. The credit memo request can be automatically blocked for checking. Once it has been approved, you can remove the block.The system uses the credit memo request to create a credit memo.
    Structure: A credit memo request is another type of sales document like a standard order. For more information on sales documents, see Working with Sales Documents.A credit memo request starts the billing process.
    =============================================
    Below mentioned is the information on Credit Memo.
    Definition: The term credit memo always refers to a credit memo from the vendor. Therefore, posting a credit memo always leads to a debit posting on the vendor account.
    Use: As in the case of invoices, credit memos refer to purchase orders or goods receipts. They are used to correct the purchase order history if the quantity invoiced was too high, for example, if an invoice was too high or if part of the quantity was returned.
    When you post a credit memo, the total quantity in the purchase order history is reduced by the credit memo quantity.
    If you do not want the total quantity invoiced to be reduced, you must post the credit memo as a subsequent credit.
    Hope this helps. Please let me know if you need more information and please assign points.
    Rgds
    Manish

  • Program terminated error after entering sold to party no. in sales order

    hello friends,
                      can any help me, i was doing the topic of user exit for pre-defined sold to party using v45a0002 in cmod and i wrote a program for include 'if sy-uname= 'sapuser'.
    message e000(0) with ' you are not authorised to create so'
    endif
    while activating i got error msg 'The last statement is not complete (period missing)."  & i have saved inspite error
    after i tried create a order
    program terminated error after entering sold to party no. in sales order
    so i have deactivated the project created in cmod & deleted the project inspite i am getting the program terminated error
    i am sending total error plz reply quickly urgent friends
    Runtime Errors         SYNTAX_ERROR
    Date and Time          19.04.2008 17:51:58
    ShrtText
    Syntax error in program "SAPLXVVA ".
    What happened?
    Error in ABAP application program.
    The current ABAP program "SAPLVKMP" had to be terminated because one of the
    statements could not be executed.
    This is probably due to an error in the ABAP program.
    In program "SAPLXVVA ", the following syntax error occurred
    in the Include "ZXVVAU04 " in line 5:
    "The last statement is not complete (period missing)."
    Author and last person to change the Include are:
    Author "SAPUSER "
    Last changed by "SAPUSER "
    What can you do?
    Please eliminate the error by performing a syntax check
    (or an extended program check) on the program "SAPLXVVA ".
    You can also perform the syntax check from the ABAP/4 Editor.
    If the problem persists, proceed as follows:
    Print out the error message (using the "Print" function)
    and make a note of the actions and input that caused the
    error.
    To resolve the problem, contact your SAP system administrator.
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer
    termination messages, especially those beyond their normal deletion
    date.
    is especially useful if you want to keep a particular message.
    Error analysis
    In program "SAPLXVVA ", the following syntax error occurred:
    "The last statement is not complete (period missing)."
    How to correct the error
    Probably the only way to eliminate the error is to correct the program.
    If you cannot solve the problem yourself and you wish to send
    an error message to SAP, include the following documents:
    1. A printout of the problem description (short dump)
    To obtain this, select in the current display "System->List->
    Save->Local File (unconverted)".
    2. A suitable printout of the system log
    To obtain this, call the system log through transaction SM21.
    Limit the time interval to 10 minutes before and 5 minutes
    after the short dump. In the display, then select the function
    "System->List->Save->Local File (unconverted)".
    3. If the programs are your own programs or modified SAP programs,
    supply the source code.
    To do this, select the Editor function "Further Utilities->
    Upload/Download->Download".
    4. Details regarding the conditions under which the error occurred
    or which actions and input led to the error.
    System environment
    SAP Release.............. "640"
    Application server....... "mtpl7"
    Network address.......... "192.100.10.1"
    Operating system......... "Windows NT"
    Release.................. "5.1"
    Hardware type............ "2x Intel 801586"
    Character length......... 8 Bits
    Pointer length........... 32 Bits
    Work process number...... 0
    Short dump setting....... "full"
    Database server.......... "MTPL7"
    Database type............ "ORACLE"
    Database name............ "ERP"
    Database owner........... "SAPERP"
    Character set............ "English_United State"
    SAP kernel............... "640"
    Created on............... "Nov 4 2004 23:26:03"
    Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
    Database version......... "OCI_920_SHARE "
    Patch level.............. "43"
    Patch text............... " "
    Supported environment....
    Database................. "ORACLE 8.1.7.., ORACLE 9.2.0.."
    SAP database version..... "640"
    Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
    Memory usage.............
    Roll..................... 8112
    EM....................... 8362368
    Heap..................... 0
    Page..................... 122880
    MM Used.................. 4229224
    MM Free.................. 995472
    SAP Release.............. "640"
    User and Transaction
    Client.............. 800
    User................ "SAPUSER"
    Language key........ "E"
    Transaction......... "VA01 "
    Program............. "SAPLVKMP"
    Screen.............. "SAPMV45A 4701"
    Screen line......... 16
    Information on where terminated
    The termination occurred in the ABAP program "SAPLVKMP" in
    "SD_DETERMINE_KKBER".
    The main program was "SAPMV45A ".
    The termination occurred in line 0 of the source code of the (Include)
    program " "
    of the source code of program " " (when calling the editor 00).
    Contents of system fields
    Name
    Val.
    SY-SUBRC
    0
    SY-INDEX
    0
    SY-TABIX
    1
    SY-DBCNT
    1
    SY-FDPOS
    4
    SY-LSIND
    0
    SY-PAGNO
    1
    SY-LINNO
    8
    SY-COLNO
    1
    SY-PFKEY
    U
    SY-UCOMM
    SY-TITLE
    Create Standard Order kb: Overview
    SY-MSGTY
    E
    SY-MSGID
    VP
    SY-MSGNO
    106
    SY-MSGV1
    BUS2032
    SY-MSGV2
    SY-MSGV3
    SY-MSGV4
    Active Calls/Events
    No.   Ty.          Program                             Include                             Line
    Name
    13 FUNCTION     SAPLVKMP                            LVKMPU41                               91
    SD_DETERMINE_KKBER
    12 FUNCTION     SAPLVKMP                            LVKMPU41                               91
    SD_DETERMINE_KKBER
    11 FUNCTION     SAPLV09B                            LV09BU30                              148
    SD_PCHECK_PAYER_IN_CREDITAREA
    10 FUNCTION     SAPLV09B                            LV09BU26                              296
    SD_PARTNER_EXECUTE_CHECKS
    9 FUNCTION     SAPLV09B                            LV09BU25                               57
    SD_PARTNER_CHECK_BEFORE
    8 FUNCTION     SAPLV09A                            LV09AU26                              342
    SD_PARTNER_SINGLE_MODIFY
    7 FORM         SAPLV09A                            LV09AF39                              176
    PARTNER_SELECTION
    6 FUNCTION     SAPLV09A                            LV09AU29                              820
    SD_PARTNER_DETERMINATION
    5 FUNCTION     SAPLV05E                            LV05EU01                              654
    VIEW_KUAGV
    4 FORM         SAPMV45A                            MV45AF0K_KUAGV_SELECT                  40
    KUAGV_SELECT
    3 FORM         SAPMV45A                            MV45AF0A_AUFTRAGGEBER_PRUEFEN          46
    AUFTRAGGEBER_PRUEFEN
    2 FORM         SAPMV45A                            MV45AF0K_KUNDEN_PRUEFEN               454
    KUNDEN_PRUEFEN
    1 MODULE (PAI) SAPMV45A                            MV45AI0K_KUNDEN_PRUEFEN                15
    KUNDEN_PRUEFEN
    Chosen variables
    Name
    Val.
    No.      13 Ty.          FUNCTION
    Name  SD_DETERMINE_KKBER
    I_KKBER_KNVV
    2222
    0000
    I_KKBER_T001
    8888
    3333
    8888
    I_KKBER_TVTA
    2222
    0000
    I_KUNNR
    7000000000
    3333333333
    7000000000
    I_SPART
    SM
    54
    3D
    I_VKORG
    T000
    5333
    4000
    I_VTWEG
    S4
    53
    34
    XVBAK
    00000000000000            000000000000000000000000         00000000
    2222222222222333333333333332222222222223333333333333333333333332222222223333333322222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    E_KNVV_FLG
    2
    0
    RC
    0
    0000
    0000
    XVBKD[]
    Table[initial]
    XVBPA[]
    Table IT_1743[2x542]
    FUNCTION=SD_PCHECK_PAYER_IN_CREDITAREADATA=LVT_CREDIT_XVBPA
    Table reference: 275
    TABH+  0(20) = 70A2883B388BC43B0000000013010000CF060000
    TABH+ 20(20) = 020000001E020000FFFFFFFF04910100D82F0000
    TABH+ 40( 8) = 02000000C1248400
    store        = 0x70A2883B
    ext1         = 0x388BC43B
    shmId        = 0     (0x00000000)
    id           = 275   (0x13010000)
    label        = 1743  (0xCF060000)
    fill         = 2     (0x02000000)
    leng         = 542   (0x1E020000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000209
    occu         = 2     (0x02000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    collHash     = 0
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 1
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x28C1883B
    pghook       = 0x00000000
    idxPtr       = 0x00000000
    refCount     = 1     (0x01000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 2     (0x02000000)
    lineAlloc    = 2     (0x02000000)
    store_id     = 690   (0xB2020000)
    shmIsReadOnly = 0     (0x00000000)
    >>>>> 1st level extension part <<<<<
    regHook      = 0x00000000
    hsdir        = 0x00000000
    ext2         = 0x28A4883B
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0x109C883B
    delta_head   = 000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x00000000
    pb_handle    = 0x00000000
    I_KKBER
    2222
    0000
    FCODE_KOMM_LIEF_MENGE_SICH
    MOD2
    44432222222222222222
    DF420000000000000000
    SYST-REPID
    SAPLVKMP
    5454544522222222222222222222222222222222
    310C6BD000000000000000000000000000000000
    %_SPACE
    2
    0
    FCODE_KONFIGURATION1
    POKO
    54442222222222222222
    0FBF0000000000000000
    CREDIT_CHECK
    2222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000
    SY-REPID
    SAPLVKMP
    5454544522222222222222222222222222222222
    310C6BD000000000000000000000000000000000
    SAV_BUKRS
    SS00
    5533
    3300
    CHAR_
    2
    0
    %_DUMMY$$
    2222
    0000
    AUTOMO_VOLVO
    08
    33
    08
    SPACE
    2
    0
    FCODE_ABRUF_GENERIEREN
    PABG
    54442222222222222222
    01270000000000000000
    XVBRK
    00000000          0000000
    2222222222222222222222222222222222222222222222223333333322222222223333333222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    KOPGR_LIEFERPLAN
    LL
    4422
    CC00
    FCODE_ZUSAETZE_FAB
    PFZU
    54552222222222222222
    06A50000000000000000
    FCODE_REPARATUR
    PREP
    55452222222222222222
    02500000000000000000
    XVBKD
    000000                                                 #####0000000000       ####
    2222222222222333333222222222222222222222222222222222222222222222222200000333333333322222220000
    000000000000000000000000000000000000000000000000000000000000000000000000C000000000000000000000
    FCODE_GEFAHRGUT
    KGGP
    44452222222222222222
    B7700000000000000000
    I_KKBER_HELP
    2222
    0000
    T001
    800SS00SRIYA TEXTILES           HYDERABAD                IN INR  EINT 10K41      0000050495DE1
    3335533554542545544452222222222245445444422222222222222224424452244452334332222223333333333443
    800330032991045849C530000000000089452121400000000000000009E09E20059E4010B410000000000050495451
    FCODE_STOFFBERICHTE
    IEHS
    44452222222222222222
    95830000000000000000
    T001-BUKRS
    SS00
    5533
    3300
    No.      12 Ty.          FUNCTION
    Name  SD_DETERMINE_KKBER
    I_KKBER_KNVV
    2222
    0000
    I_KKBER_T001
    8888
    3333
    8888
    I_KKBER_TVTA
    2222
    0000
    I_KUNNR
    7000000000
    3333333333
    7000000000
    I_SPART
    SM
    54
    3D
    I_VKORG
    T000
    5333
    4000
    I_VTWEG
    S4
    53
    34
    XVBAK
    00000000000000            000000000000000000000000         00000000
    2222222222222333333333333332222222222223333333333333333333333332222222223333333322222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    E_KNVV_FLG
    2
    0
    RC
    0
    0000
    0000
    XVBKD[]
    Table[initial]
    XVBPA[]
    Table IT_1743[2x542]
    I_KKBER
    2222
    0000
    XVBKD
    000000                                                 #####0000000000       ####
    2222222222222333333222222222222222222222222222222222222222222222222200000333333333322222220000
    000000000000000000000000000000000000000000000000000000000000000000000000C000000000000000000000
    I_KKBER_HELP
    2222
    0000
    No.      11 Ty.          FUNCTION
    Name  SD_PCHECK_PAYER_IN_CREDITAREA
    FIC_OBJECTKEY
    2222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000
    FIC_OBJECTTYPE
    BUS2032
    4553333222
    2532032000
    FIF_CHECKTYPE
    I
    4
    9
    FIF_MSGTYPE
    E
    4
    5
    FIF_NRART
    KU
    45
    B5
    FIF_PARGR
    TA
    5422
    4100
    FIF_PARNR
    7000000000
    3333333333
    7000000000
    FIF_PARVW
    RG
    5422
    2700
    FIF_POSNR
    000000
    333333
    000000
    FIF_RTYPE
    0003
    3333
    0003
    FIS_SDORGDATA
    T000S4SMZSOR
    533353545545222222
    4000343DA3F2000000
    FRF_MESSAGES
    0
    0000
    0000
    FRF_MESSAGE_COUNT
    0
    0000
    0000
    LVF_KKBER2
    2222
    0000
    LVF_KUNNR
    7000000000
    3333333333
    7000000000
    SYST-REPID
    SAPLV09B
    5454533422222222222222222222222222222222
    310C609200000000000000000000000000000000
    LVF_KURGV2
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    SY-MSGV4
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    SY-MSGV2
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    FIS_SDORGDATA-SPART
    SM
    54
    3D
    FIS_SDORGDATA-VKORG
    T000
    5333
    4000
    FIS_SDORGDATA-VTWEG
    S4
    53
    34
    %_O_SD_PARTNER_CONTEXT-HEX_0004
    1
    0
    LVT_CREDIT_XVBPA
    Table IT_1743[2x542]
    LVF_KKBER1
    2222
    0000
    GCS_HERTAB
    ABCDEFG
    24444444
    01234567
    %_DUMMY$$
    2222
    0000
    SY-SUBRC
    0
    0000
    0000
    LVF_BEFORE_PARVW
    2222
    0000
    No.      10 Ty.          FUNCTION
    Name  SD_PARTNER_EXECUTE_CHECKS
    FIC_OBJECTKEY
    2222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000
    FIC_OBJECTTYPE
    BUS2032
    4553333222
    2532032000
    FIF_BEFORE
    2
    0
    FIF_CHECKTYPE
    I
    4
    9
    FIF_DIALOG
    2
    0
    FIF_MSGTYPE_TO_EXEC
    E
    4222
    5000
    FIF_NRART
    KU
    45
    B5
    FIF_PARGR
    TA
    5422
    4100
    FIF_PARNR
    7000000000
    3333333333
    7000000000
    FIF_PARVW
    RG
    5422
    2700
    FIF_POSNR
    000000
    333333
    000000
    FIF_RTYPE
    0003
    3333
    0003
    FIS_SDORGDATA
    T000S4SMZSOR
    533353545545222222
    4000343DA3F2000000
    FRF_MESSAGES
    0
    0000
    0000
    FRF_MESSAGE_COUNT
    0
    0000
    0000
    LVF_ALL_PREDECESSORS_SUCCEEDED
    X
    5
    8
    FALSE
    2
    0
    GS_MARKED_PARTNERS
    222222222222
    000000000000
    LVT_CHECKCALLSTACK
    Table IT_1515[21x52]
    FUNCTION=SD_PARTNER_EXECUTE_CHECKSDATA=LVT_CHECKCALLSTACK
    Table reference: 219
    TABH+  0(20) = E8C3863B0000000000000000DB000000EB050000
    TABH+ 20(20) = 1500000034000000F00000000491010058090000
    TABH+ 40( 8) = 15000000C1248000
    store        = 0xE8C3863B
    ext1         = 0x00000000
    shmId        = 0     (0x00000000)
    id           = 219   (0xDB000000)
    label        = 1515  (0xEB050000)
    fill         = 21    (0x15000000)
    leng         = 52    (0x34000000)
    loop         = 240   (0xF0000000)
    xtyp         = TYPE#000033
    occu         = 21    (0x15000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    collHash     = 0
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x90BF863B
    pghook       = 0x00000000
    idxPtr       = 0x00000000
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 21    (0x15000000)
    lineAlloc    = 21    (0x15000000)
    store_id     = 595   (0x53020000)
    shmIsReadOnly = 0     (0x00000000)
    >>>>> 1st level extension part <<<<<
    regHook      = Not allocated
    hsdir        = Not allocated
    ext2         = Not allocated
    >>>>> 2nd level extension part <<<<<
    tabhBack     = Not allocated
    delta_head   = Not allocated
    pb_func      = Not allocated
    pb_handle    = Not allocated
    LVS_CHECKCALLSTACK_WA
    80000018BUS2030   SD_PCHECK_PAYER_IN_CREDITAREA   XX
    3333333345533332225455444445545455445454445454422255
    80000018253203000034F03853BF01952F9EF325494125100088
    GT_MARKED_FOR_DEL_PARTNERS
    Table[initial]
    LVS_CHECKCALLSTACK_WA-FUNCNAME
    SD_PCHECK_PAYER_IN_CREDITAREA
    545544444554545544545444545442
    34F03853BF01952F9EF32549412510
    GC_NO_ACTION
    2
    0
    GC_NEW_PARTNER
    I
    4
    9
    GVC_PARTNER_CONTEXT
    CONTEXT_X_SD_PARTNER_CONTEXT            fò####################################################
    44454555555455455445544454552222222222226F0000000000000000000000000000000000000000000000000000
    3FE4584F8F34F0124E52F3FE4584000000000000620000000000000000000000000000000000000000000000000000
    GC_ERROR
    E
    4
    5
    GC_PROCESSMODE_DIALOG
    D
    4
    4
    LVF_MSGTYP
    E
    4
    5
    BUFFER_FULL_FILLED
    F
    4
    6
    POS_NUL
    000000
    333333
    000000
    BUFFER_PARTITIAL_FILLED
    P
    5
    0
    %_ARCHIVE
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    GCS_PARTNER_ROLETYPES
    0001000200030004000500060007000800090010001100120013NONE
    33333333333333333333333333333333333333333333333333334444
    0001000200030004000500060007000800090010001100120013EFE5
    GCS_PARTNER_TYPE
    KUAPLIPE
    45454454
    B510C905
    LVF_RTYPE
    0003
    3333
    0003
    GCS_PARTNER_CALL_BACK_EVENTS
    CHANGE    DELETE    NEW
    444444222244445422224452222222
    381E75000045C5450000E570000000
    %_PRINT
    000                                                                                0 ##
    2222333222222222222222222222222222222222222222222222222222222222222222222222222222222222223200
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    GCF_INITIAL_PARTNER
    0
    32
    00
    GCF_CALLER_TRANSPORT
    T
    5
    4
    TPACHECKRELATION
    0000000000
    2223333333333
    0000000000000
    GC_APPL_LOG
    SDBFPD
    54445422222222222222
    34260400000000000000
    SY-REPID
    SAPLV09B
    5454533422222222222222222222222222222222
    310C609200000000000000000000000000000000
    GVC_PARTNER_CONTEXT-B0007-PARVW
    RG
    54
    27
    No.       9 Ty.          FUNCTION
    Name  SD_PARTNER_CHECK_BEFORE
    FIC_OBJECTKEY
    2222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000
    FIC_OBJECTTYPE
    BUS2032
    4553333222
    2532032000
    FIF_BEFORE
    2
    0
    FIF_CHECKTYPE
    I
    4
    9
    FIF_DIALOG
    2
    0
    FIF_NRART
    KU
    45
    B5
    FIF_PARGR
    TA
    5422
    4100
    FIF_PARNR
    7000000000
    3333333333
    7000000000
    FIF_PARVW
    RG
    5422
    2700
    FIF_POSNR
    000000
    333333
    000000
    FIF_RTYPE
    0003
    3333
    0003
    FIS_SDORGDATA
    T000S4SMZSOR
    533353545545222222
    4000343DA3F2000000
    FRF_MESSAGES
    0
    0000
    0000
    FRF_MESSAGE_COUNT
    0
    0000
    0000
    LS_STATISTICS
    ########################4   ################
    00000000000000000000000032220000000000000000
    00000000000000000000000040000000000000000000
    No.       8 Ty.          FUNCTION
    Name  SD_PARTNER_SINGLE_MODIFY
    FIC_OBJECTKEY
    2222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000
    FIC_OBJECTTYPE
    BUS2032
    4553333222
    2532032000
    FIF_BOKRE
    2
    0
    FIF_CLEAR_APPL_LOG
    X
    5
    8
    FIF_DIALOG
    2
    0
    FIF_HARD_DELETION
    2
    0
    FIF_HISTUNR
    00
    33
    00
    FIF_HZUOR
    00
    33
    00
    FIF_INITIAL_VALUE
    X
    5
    8
    FIF_KNREF_PARNR
    2222222222
    0000000000
    FIF_KUNNR_NEW
    7000000000
    3333333333
    7000000000
    FIF_KUNNR_OLD
    2222222222
    0000000000
    FIF_LISTPROCESSING
    2
    0
    FIF_MANUAL_ADDRESS
    2222222222
    0000000000
    FIF_MANUAL_ADDRESS_ORIGIN
    2
    0
    FIF_NO_CPD_DIALOG
    2
    0
    FIF_NO_DIALOG
    2
    0
    FIF_NO_MESSAGES
    2
    0
    FIF_PARGR
    TA
    5422
    4100
    FIF_PARTIAL_NEW_DETERMINATION
    2
    0
    FIF_PARVW
    RG
    5422
    2700
    FIF_POSNR
    000000
    333333
    000000
    FIF_PRFRE
    2
    0
    FIF_VKORG
    2222
    0000
    FIS_SDORGDATA
    T000S4SMZSOR
    533353545545222222
    4000343DA3F2000000
    FEV_ACTION_DONE
    I
    4
    9
    FRF_LOG_COUNT
    0
    0000
    0000
    SYST-REPID
    SAPLV09A
    5454533422222222222222222222222222222222
    310C609100000000000000000000000000000000
    GVT_LOCAL_CALL_BACK_MEMORY[]
    Table[initial]
    %_SPACE
    2
    0
    SY-REPID
    SAPLV09A
    5454533422222222222222222222222222222222
    310C609100000000000000000000000000000000
    LVF_ACTION_TODO
    I
    4
    9
    GC_UPD_PARTNER
    U
    5
    5
    %_VIASELSCR
    0
    4
    %_ARCHIVE
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    GCS_PARTNER_ROLETYPES-SHIP_TO
    0002
    3333
    0002
    LVF_NRART
    KU
    45
    B5
    LVF_KUNNR_NEW
    7000000000
    3333333333
    7000000000
    GCS_ADDRESS_GROUP
    SD01CA01
    54334433
    34013101
    GCF_APPL_TABLE_SD
    VBUK
    5454222222
    625B000000
    LVF_ROLETYPE
    0003
    3333
    0003
    RSJOBINFO
    00000000000000                                  ####
    222222222222222222222222222222223333333333333322222222222222222222222222222222220000
    000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    LVF_MESSAGE_COUNT
    0
    0000
    0000
    %_DUMMY$$
    2222
    0000
    GCF_ADDRESS_TYPE_CONT_PERSON
    3
    3
    3
    No.       7 Ty.          FORM
    Name  PARTNER_SELECTION
    TVTA
    000
    222222222222222222222222222222222333222222222222222
    000000000000000000000000000000000000000000000000000
    TPAER
    00
    22222222222222332222
    00000000000000000000
    LVS_XVBPA
    000000RG7000000000          0000000000000000000000050510
    2222222222222333333543333333333222222222233333333333333333333333333332222222222222222222222222
    0000000000000000000277000000000000000000000000000000000000000000505100000000000000000000000000
    LVF_PARNR
    7000000000
    3333333333
    7000000000
    PIC_OBJECTKEY
    2222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000
    PIC_OBJECTTYPE
    BUS2032
    4553333222
    2532032000
    PIF_NO_DIALOG
    2
    0
    PIF_PARGR
    TA
    5422
    4100
    LVF_PARVW
    RG
    5422
    2700
    PIF_POSNR

    Hi Kartik,
    Could you please be more clearer as to how do you want me to proceed so that this syntax error stops bothering me while creating a standard order thru TCode VA01.Also what do you mean by "well comment the code in the include and activate the include"
    I created a projet in CMOD and than added the enhancement  V45A0002.The components shown as EXIT_SAPMV45A_002(Predefined sold to party when making the standard order),i double click on the exit and entered into the function module.After that i double clicked on the include ZXVVZU04 and entered in and wrote E_KUNNR=100171
    While activating i got error msg 'The last statement is not complete (period missing)." & i have saved inspite the error .After that i tried to create a order and program terminated error came after entering sold to party no. in sales order
    so now i have deactivated the project which i created in CMOD & deleted the project also inspite of this i am getting the program terminated error while making the order
    I would be great ful if somebody helps me *** out of this syntax error.
    Thanks
    Rishi

  • Sapscript for Debit Memo and Credit Memo

    I want to create the debit memo and credit memo scripts.
    I am not getting the standard scripts and output type so that i can modify it and according to my requirement.
    Please let me know the standard sapscripts for the credit memo and debit memo.

    Hi
    use the same Invoice Script/smartform for Credit/debit memo's
    INVOICE
    Output type         : RD00
    ScriptForm Name     : RVINVOICE01
    Driver Program Name : RVADIN01
    smartform name      : LB_BIL_INVOICE
    Smartform Driver Pgm: RLB_INVOICE
    Regards
    Anji

  • Report to identify invoices, debit memos and credit memos

    Hi,
    Just enquiring if there is a report in SAP that will identify all invoices debit memos and credit memos issued within a particular date range.
    Thank you.

    Hi,
    You can try VF05 as Navaneet indicated and also you can try VF05N (for only the header details), if you are using ECC 6.0
    If you have VF05N, then you can tick 'Biling Documents in FI'. It will give you the billing docs for a date range and the ones that have been released to accounting....
    Hope this helps
    Thanks
    Mukund S
    Edited by: MukundHS on Jul 26, 2010 6:52 AM

  • Debit memo and Credit memo

    Dear Expert,
    I always confused on Debit memo and Credit memo...especially the business scenario behind and how it is reflecting in SAP system.
    Let's take this example:
    e.g the Price in the main Invoice is lesser than the actual price, and the difference needs to be recovered from the customer.
    My analysis:
    "The invoice is lesser than the actual price", Means Product should cost 100 USD, but we billed customer only in 80 USD, there are 20 USD difference.  Customer should pay us the rest 20 USD.  So our Account receiivable should be increased. So we need create Debit memo to customer and ask them to pay the money.  Customer received the Debit memo, they will create credit memo and send it to us said they will pay the money.
    Am i understanding correct???  Please kindly share in case you have better simple example. Thank you very much.

    Your understanding on the subject is absolutely correct.
    Let me share an another example with you for debit memo.
    These manufacturer of nuts and bolts. Previously they have 100 nuts in one pack, but then they changed it to 120. But the order which was already made for 10 pkts delivered 1200 nuts instead of 1000. So they require to raises Debit memo.
    But, these Debit memo generally avoid, b'coz people take at most care in creating a invoice. And people do like to pay when they are receiving end.
    Where as, Credit memo can be result of return or complaint of defect or less quantities delivered.
    Well, their behavior is control by SD document categ at billing doc type (Tcode VOFA)
    - P is for Debit Memo (L2)
    - O is for Credit Memo (G2)
    These SD document category classify for the different types of documents that you can process in the sales and distribution system (for example: quotations, sales orders, deliveries, and invoices). So, these determines how the system stores and keeps track of document data. It enables the system to provide you with status information about delivery processing, billing, and documents that are used for reference (for example, inquiries and quotations).
    So, if we summaries it,
    Credit memo - Created to reduce the amount of an existing vendor payable, or customer receivable.
    Debit memo - Used to recover costs from another department or faculty. May also be used to correct an incorrectly posted entry.
    Hope this suffice your requirement.
    Thanks & Regards
    JP

  • BAPI to park Debit Note (Vendor credit memo) Doc Type: 'KG'

    Hi All,
    A friend of mine desperately needs to know any BAPI for parking Debit Note (Doc.type : KG Vendor credit memo)... Please let me know if you know about any BAPI / Funcation module to do it and a little chunk of sample code will surely help me a lot....
    Thanks in Advance,
    Regards,

    Hi Savitha,
    Well, we have experiemented with this BAPI "BAPI_INCOMINGINVOICE_PARK" earlier, but we found out that it dose not work properly for Service Orders; also it dose not seem to post proper debit note. Anyways, we have used another BAPI "BAPI_ACC_GL_POSTING_POST", it worked but it posts the debit note (Vendor Credit Memo) but we only want to park the debit note and let the user review it and then the user can post it manually or so afterwards...
    Regards,
    Athar

  • Please enter sold-to party or ship-to party USING BAPI_SALESORDER_CREATEFRO

    Hello Guys,
    Im having a hard time in inserting the data using BAPI_SALESORDER_CREATEFROMDAT2.
    The return error is Please enter sold-to party or ship-to party  how can i solve this?whats the reason  behind this?
    The return error are :
       |V4                  |219   |Sales document  was not changed        
       |VP                  |112   |Please enter sold-to party or ship-to pa
       |V4                  |219   |Sales document  was not changed        
    Please help. Will reward points to those helpful one.
    Thanks in advance.
    aVaDuDz
    This is my sample code.
    *& Report  Z_ORDER_CREATE_SPA_HBR
    REPORT  z_order_create_spa_hbr.
    Parameters
    PARAMETERS: p_order LIKE vbak-vbeln.
    We need to create a new order number P_New from an existing order
    *P_order
    linked to an existing quotation P_quote
    Tables
    TABLES: vbak,
            vbap,
            vbkd. "Sales Document: Business Data
    Data and internal table
    DATA:  order_header_in1       LIKE bapisdhd1.
    DATA:  order_header_intx      LIKE bapisdhd1x.
    DATA : salesdocument1         TYPE bapivbeln-vbeln.
    DATA : return2                TYPE bapiret2.
    DATA:  order_partners1        TYPE bapiparnr  OCCURS 0 WITH HEADER LINE.
    DATA:  order_items_in1        TYPE bapisditm  OCCURS 0 WITH HEADER LINE.
    DATA:  order_items_in1x       TYPE bapisditmx OCCURS 0 WITH HEADER LINE.
    DATA:  order_schedules_in1    TYPE bapischdl  OCCURS 0 WITH HEADER LINE.
    DATA:  order_schedules_in1x   TYPE bapischdlx OCCURS 0 WITH HEADER LINE.
    DATA : return1                TYPE bapiret2   OCCURS 0 WITH HEADER LINE.
    START-OF-SELECTION.
      PERFORM order_header_in.
      PERFORM ORDER_PARTNERS.
      PERFORM order_schedules_in.
      PERFORM ORDER_ITEMS_IN.
      PERFORM call_function.
    *& Form call_function
    text
    --> p1 text
    <-- p2 text
    FORM call_function .
      CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'
        EXPORTING
       SALESDOCUMENTIN               = P_new
        order_header_in               = order_header_in1
      ORDER_HEADER_INX              = order_header_intX
      SENDER                        =
      BINARY_RELATIONSHIPTYPE       =
      INT_NUMBER_ASSIGNMENT         =
      BEHAVE_WHEN_ERROR             =
      LOGIC_SWITCH                  =
      TESTRUN                       =
      CONVERT                       = ' '
      IMPORTING
        salesdocument                 = salesdocument1
      TABLES
        return                        = return1
        order_items_in                = order_items_in1
      ORDER_ITEMS_INX               = ORDER_ITEMS_IN1X
        order_partners                = order_partners1
        order_schedules_in            = order_schedules_in1
      ORDER_SCHEDULES_INX           = ORDER_SCHEDULES_IN1X
      ORDER_CONDITIONS_IN           =
      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 NOT salesdocument1 IS INITIAL.
        CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
          EXPORTING
            wait   = 'X'
          IMPORTING
            return = return2.
      ELSE.
        CALL FUNCTION 'BAPI_TRANSACTION_ROLLBACK'.
      ENDIF.
    ENDFORM.                    "call_function
    *&      Form  ORDER_HEADER_IN
          text
    -->  p1        text
    <--  p2        text
    FORM order_header_in .
      order_header_in1-doc_type   = 'ZMCH'.
      order_header_in1-sales_org  =  '2000'.
      order_header_in1-distr_chan =  '20'.
      order_header_in1-division   =   '30'.
      order_header_in1-incoterms1 = 'FH'.
      order_header_in1-sales_off  = '3102'.
      order_header_in1-sales_grp = '301'.
      order_header_in1-ORD_REASON = 'Cost Center RelevanT'.
      order_header_in1-SALES_DIST  = '230144'.
      order_header_in1-PURCH_DATE = '07/31/2008'.
      order_header_in1-PURCH_NO_C = 'UPLOAD2-TEST'.
      APPEND order_items_in1.
    ENDFORM.                    " ORDER_HEADER_IN
    *&      Form  order_schedules_in
          text
    -->  p1        text
    <--  p2        text
    form order_schedules_in .
    order_schedules_in1-req_date     = sy-datum + 20.
      order_schedules_in1-req_qty      = vbap-kwmeng.
      APPEND order_schedules_in1.
    endform.                    " order_schedules_in
    *&      Form  ORDER_PARTNERS
          text
    -->  p1        text
    <--  p2        text
    form ORDER_PARTNERS .
      order_partners1-partn_role         = 'PH'.
      order_partners1-partn_numb         = '1200038'.
       APPEND order_partners1.
    endform.                    " ORDER_PARTNERS
    *&      Form  ORDER_ITEMS_IN
          text
    -->  p1        text
    <--  p2        text
    form ORDER_ITEMS_IN .
    order_items_in1-ITM_NUMBER = 1.
    order_items_in1-MATERIAL ='300040'.
    order_items_in1-TARGET_QTY = 1.
    order_items_in1-SALES_UNIT = 'MON'.
    APPEND order_items_in1.
    endform.                    " ORDER_ITEMS_IN

    Hi AVA MARIE TRINIDAD.
    Pass QUOTATION_PARTNERS-ITM_NUMBER = '0000000'.
    And pass customers like this.
    QUOTATION_PARTNERS-PARTN_NUMB = '1000000'.
    CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
       EXPORTING
         INPUT         = QUOTATION_PARTNERS-PARTN_NUMB
      IMPORTING
        OUTPUT        = QUOTATION_PARTNERS-PARTN_NUMB

  • Need Debit Memo and Credit Memo

    Hi,
    What is the purpose of Debit Memo and Credit Memo, Is it bothe useful for Customer and Vendor.
    If any body having document on this pls. What are the steps need to process.
    Urgent
    Rgds
    sunfico

    Hi,
    Good morning and greetings,
    You can raise a Credit Memo for a Vendor using the transction code FB65 (without reference to an invoice) or MIRO (if it is with reference to an invoice) and the system would pass the following accounting entry
    Dr. Expenses A/c
    Cr. Vendor A/c
    This particular document would have a payment term and payment due date. While running Automatic Payment Process, depending on the payment method the system will pick up the document and create a cheque / electronic transfer etc for the vendor with the following entry
    Dr. Vendor A/c
    Cr. Bank Clearing A/c
    In the case of Customer you can account the credit memo (without reference to invoice) using FB75 or VA01 (Order Type CR, if it is with reference to an invoice). While you create the billing document for the order type CR the system would raise the following accounting
    Dr. Expenses A/c
    Cr. Customer A/c
    This particular document would have a payment term and payment due date. While running Automatic Payment Process, depending on the payment method the system will pick up the document and create a cheque / electronic transfer etc for the customer with the following entry
    Dr. Customer A/c
    Cr. Bank Clearing A/c
    Hope this meets your requirement...Please reward points if found useful
    Thanking you
    With kindest regards
    GVR

  • Difference betn credit memo n credit memo for returns

    Hi,
    What is difference betn credit memo n credit memo for returns?

    Hi
    CREDIT MEMO:
    Suppose, you have chrged (Price) the customer more or you have charged the customer for say 10 pieces but you have send actually 8 pieces,for which customer has paid you.
    In both the above scenarios, you need to pay back the excess amount paid by him.
    To payback, we create a Billing document called Credit memo. In standard SAP, Billing Type G2 is created for Credit memo.
    This Credit memo(G2) is created with reference to a Credit memo request (Sales document type) with Order type "CR".
    This Credit memo Request (CR) is created either with reference to Sales order or Billing document.
    Ofcourse, it can also be created with out any reference document also. In real time scenario, we normally create this Credit memo Request with reference to the Billing document (Invoice).
    No Delivery takes place in this scenario while creating a Credit memo (G2).
    CREDIT FOR RETURN
    When goods are physically returned back by the customer due to some complaint, then we first, create a Return order(Order Type RE) with reference to either Sales order or Billing document. Normally, in real time scenarios, we refer the Billing document.
    Return order can also be created with out any reference .
    In situation like, suppose you had sent 10 pieces of certain material to the customer for which he has paid. But he found that 2 pieces are defective or damaged in transit. So he has returned it to you for which you need to create a Return order(RE).
    From this Return order(RE) -
    > Return Delivery is created -
    > PGR.
    As customer has returned the goods to you, then there are 2 options with you. Either you may send fresh stock ,which we normally call "Replacement" OR you may pay back the value for the returned goods.
    If, we pay back, then we create a Credit memo for return, which called "Credit for Return" and in standard SAP represented by Billing Type (RE).
    In standard system, this "Credit for Return(RE)" is ALWAYS created with reference to the "Return Order(RE)".
    Even though, physical delivery takes place in return process, still the "Credit for return(RE)" is created with reference to the "Return order(RE)".
    If, client requires it to be created from Return delivery then you need to establish necessary settings in customisation which has already beed discussed in this forum several times.
    Hope, it is clear.
    Regards

  • Difference between Rebate Credit Memo and Credit Memo

    Dear Experts,
    Can an

    Credit Memo:
    Credit Memo issued for the price difference or if over billed . Credit memo always assoicated with Quantity and price.
    Rebate Credit Memo:
    Rebate credit memo is issued for the accruals ( Discount amount disbursed to the customers based on agreement).
    Rebate credit memo cannot be created manually in VA01. Accrual amount is calculated by the system based on the settle periods maintained in the rebate aggreement however accrual amt can be changed manually in Aggreement.
    Contact for further clarifications
    Senthils

  • Credit memos vs Credit memos - Genneral

    Dear all
    I am confused when I should use Credit memo or Credit memo-General
    Anyone tell me the difference between Credit Memo and Credit memo-General. How can I use it each type?
    Thank in advance
    Minh

    Hello Tran
    It is observed that you have posted around 80 questions so far on the forum and out of which you have closed around 15 and 65 remain unanswered according to the status.
    When members reply to your questions, they spend time and effort to give a suitable solution or advise.
    Assigning points motivate members in a healthy environment.
    Each of us here are trying to learn/ enhance / and share the little knowledge we have.
    Please do motivate members, to serve all better.
    Reg
    Suresh

  • Change condition value in debit memo and credit memo

    Hi Experts,
    When I am trying to create Credit Memo/Debit memo I could able to change the condition value for which condition type the value is there in Sales Order, but where as for other condition types it is not changeable.
    For example for Freight the Condition type is ZFRE,  value is 100 rs in sales order 90000001.
    If I create credit memo with reference to sales order I can able to change freight value from rs100 to rs 75.
    But what to do If I do not maintain freight value initially in sales order and if I want to adjust freight value ZFRE as rs 60 in credit memo. Presently I could not able to enter values in C/D Memo.
    Hope my question is clear to you all.
    Thanks & Regards
    Naresh

    Hi Naresh
    If I understand correctly,  then you want to include the freight amount automatically in the Credit memo which was not featuring in the Credit memo request.
    If it is so, then first see which is Pricing procedure working  for your Credit memo Request.
    In the Pricing Procedure, check the freight condition type (e,g. KF00).
    See the what is Acees sequence assigned to it and in the Access sequence what are table assigned.
    In  condition type KF00,  Access sequence assigned is KF00 and two condition tables "Incoterm" and "Incoterm Part1 + Part2" are assigned to it.
    In the Access sequnce of your Freight condition type , add another/new condition table "350" (Sales organisation). This table is already available in standard system.
    Select the new condition table row, and click on the "Field" in the dialog box till the technical names are opened up / shown inspite of warning.
    Once the technical names of the fields are shown , you can see the green light there, then save it.
    Now, create a condition record (VK11) for your Freight condition (e,g. KF00) by choosing the "Sales organisation" level  from the key combination.
    Then go to the Copy control (VTFA), find the combination "G2 from CR "> go to Item level > select item category G2N and go to details.
    Here, you change the "Pricing type" value to " H " and save it.
    Now, when you will create a Credit memo with reference to the Credit memo request, the  new Freight condition (KF00) will come into effect in the Credit memo, even if ,it was not there in the reference document.

  • Debit balance on Credit Memo

    We are in the process of implementing Oracle Receivables v. 11.0. Is there a way to make sure that credit memos do not have a debit balance? (i.e. users don't forget to put the negative sign in on a line causing a debit balance?) We do plan to have mixed signs on the credit memo, but they should never have a positive balance. For instance - we want to credit the returned product, but debit a discount given for that product. Any help would be appreciated. Thanks.

    Hi Hoo Laa,
    Your statements are absolutely right.
    Suppose we area a seller and our customer is a buyer.
    We sold the goods to customer and due to some reason customer return these goods (Bad quality etc), suppose before returning the goods we have already billed the customer
    Now upon returning the goods, this is our responsbility to credited the customer account.
    Just opposite in the debit memo, we have sold the goods 100$ per piece. Now after selling the goods, we and customer are agreed that the price should be 120$ per piece. Now we have to debited the customer account for 20$ per piece.
    Hope it clarify your doubt.
    Regards,
    MT

Maybe you are looking for