BDOC Error : Partner function Sold-To Party occurs more often than specified in Customizing

Hi,
I am new to middleware and would like to know how to solve the below error.
My scenario is I am trying to perform an initial download for equipment from ECC to CRM. Most of the blocks get successfully uploaded, but for a few cases I get this error.
CRM_EQ_DMBDOC: Partner function Sold-To Party occurs more often than specified in Customizing
As my block size is 50, I would like to know which entry has this error and how to fix it. Once I fix it do I reprocess the BDOC.
Please advice me how to go about this. Thank you for your time.
Regards,
Dhruv

Hi Willie,
Thanks for your reply.
I applied the Note 1762574 and tried reprocessing the BDOC but it does not get processed.
The other note 1414329 de-implements the change made by the first one, so I did not use it.
Do you have any other suggestion?
Regards,
Dhruv

Similar Messages

  • In the SLFN transaction type partner function sold-to-party

    Dear all,
            We have connected 7 satelite systems to the solution manager server when the end user create the ticket in the satelite system  automatically transaction type will create .When the super user open the transaction type In the Sold-to-party partner function that satelite system name have to display how to canfigure that can Suggest ?.
    Regards,
    Pavan.
    Edited by: pavan reddy on Feb 28, 2008 11:23 AM

    Dear pavan,
    If am not wrong you already created IBASE component for all the 7 components
    Now create BP using BP tcode  of organization & sold to party type of satellite system name using external naming system.
    And in IB52 just assign using goto partner to these sold to party for e.g.
    system A client 500.......................create a BP of name System A of sold to party with BP tcode
    and
    Goto IB52 select the component and assign the System A to sold to party.
    PLEASE REWARD POINTS

  • Partner function sold to party to be disabled itself at overview screen

    Dears
    i have a scenario where client wants that sold to party at overview screen of sales order,must be disabled after saving of the
    sales document i.e  it should appears grey after saving of the document.
    Regards
    KAPIL MORE

    Dear Kapil
    Apologies for a late reply. Try using this exit: MV45AFZZ for sales document processing,  USEREXIT_FIELD_MODIFICATION. Take an ABAP person help in writing down a code.
    Just ensure that your action does not have any impact to the document status, particularly if you are using Credit checks. Try this option and please let me know if it works to your requirements.
    Thanks
    Nara

  • You cannot maintain the address (partner function 'Ship-to party' is empty)

    Dear Experts,
          I create one outbound delivery but when I click on address ( Symbol next to ship to party) it is showing below error.
    You cannot maintain the address (partner function 'Ship-to party' is empty)
    Message no. VPD017
    I also check customer master , address is maintain properly.
    in partner functions Sold-to party , Bill-to party , Payer , Ship-to party all are same. ( example: if bill to party is ABC then payer , ship to pary , bill to party all are ABC).
    Please help.
    Regards,
    Nirav Desai

    Hii Nirav Desai,
    You do correctly "configure automatic partner determination". The steps are as below -
    Customer Master
    Sales Document Header
    Sales Document Item
    Delivery Type
    Shipment Type
    Billing Header
    Billing item
    Sales Activities
    1.     How to define partner?
    A grouping of partner functions. The procedure specifies which partner functions are allowed for a particular business transaction (for example, for processing a sales order) and which of those partner functions are mandatory.
    Use
    You define partner determination procedures in SD Customizing through Functions -> Partner determinat.
    u2022     In sales documents, for example, you can specify the partner determination procedure according to sales document type and item category. During order entry, the system first proposes partners from the customer master record of the sold-to party. If this information does not exist in the customer master, the system automatically proposes the mandatory partners from the partner determination procedure that you specify in the document header.
    u2022     For billing documents, for example, you can specify a partner determination procedure where the sold-to party, bill-to party, and payer are mandatory but the ship-to party is not (for billing, you are more interested in who orders and pays for the goods than in who receives them).
    Thanks and Regards,
    Santanu

  • 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

  • "Partner function CA can only occur 1 times in procedure TA (Sales Document

    Dear Experts,
    I have a requirement where I need to capture the Partner function more than once....
    Say  i need to capture the two or more commission agents in one sales order....
    But when I enter the second comm agent the system triggers
    "Partner function CA can only occur 1 times in procedure TA (Sales Document Header)
    Cheers

    Hi,
    Go to VOPA....
    1.Create Partner Functions as many as required....say PF1,PF2 and so on...
    2.Assign all the partner functions to the account group.
    3.mark the partners as mand or notchang in the procedure details....
    Once u r done with this u can add the PF1..PF2 .....in the customer master/sales doc....
    Hope this will help u.
    Thanks
    Ivy

  • Legal Error: Partner Function Mapping not Maintained

    Hello SD Gurus,
    When i create a order and save, i get this pop-up (but i can save the order if i click ok)...
    the pop-up is:
    <u>Legal Error: Partner Function Mapping not Maintained</u>
    Can someone explain why is this appearing and how to correct this?
    Thanks in advance,
    Regards
    Jag

    Hi
    Go to transaction VOPA and maintain partner determination
    In the customer master , VD01 maintain partners for this customer for whom you are creating the sales order
    Hope this helps
    Cheers
    N Ganesh

  • I have a Canon MX882 and more often than note get an error message saying the printer is not connected. I check the printer and the get the message that the access point is accessed. I have reloaded the software and it worked for awhile. Any ideas?

    I have a Canon MX882 printer and more often than note get an error message that says "Printer not Connected." When I check the printer itself, I get confirmation that the access point is connected. I tried reloading the software and that seemed to have solved the problem for awhile but I'm experiencing the same problem. Any ideas what is causing this?

    Did you delete all receipts with iDVD in the file name  with either a .PKG or .BOM extension that reside in the HD/Library/Receipts folder and from the /var/db/receipts/  folder before installing the new copy?  If not then do so and delete the new application also.
    Click to view full size
    Then install iPhoto from the disk it came on originally and apply all necessary updaters: Apple - Support - Downloads
    OT

  • Partner determination sold to party and ship to party.

    Hi frnds,
      Currently in the customer master in partner function we are maintaining ship to party the same as sold to party , now for some of the customer the ship to party and sold to party are different , so while creating a sales when i enter the sold to party , the system propose the ship to party and on that basis the delivery and billing should take place.
    What are the configuration settings required to be done to this , i will maintain the ship to party in customer master partner determaination, but when i create the sales order and when i enter the sold to party , it should propse the ship

    Hi  Rakesh,
    As per SAP standard setting ship to party will be determined from Sold to party master , if that is maintained. I suggest to copy Standard and test again.
    Also ,hope you have not made any changes to the partner determination procedure fro Sales Document at header Level. This will also impact .
    Sharing a few useful link for more clarity :--
    http://www.freesaptutorial.com/partner-determination-in-sap-sd/
    Re: Ship-to party is not assigned to a sold-to party
    http://www.sap-basis-abap.com/sd/steps-for-partner-determination-config-in-img.htm
    http://help.sap.com/saphelp_crm40/helpdata/en/3c/92ecee484a11d5980800a0c9306667/content.htm
    http://wiki.sdn.sap.com/wiki/display/Snippets/howtogetship-topartyforasoldto+party
    Thanks/Rajesh

  • Customer is not assigned to a partner function

    Hi Experts,
    I'm encountering the same error. When I view the Customer and click Customer Partner Functions, system throws a message Customer SP0003 is not assigned to a partner function
    How do I assign my newly created Customer to a Partner Function Sold-to-Party?
    I've checked the setup for Partner Determination: Customer Master, the settings are as follows:
    Partner Determination Procedures:
    AG Sold-To Party
    IN Sales Prospect
    KO Consumer
    RE Bill-to Party
    RG Payer
    SO Assortment cust.
    WE Ship-to party
    WESR GR w/ MatSafSheetRec
    Partner Functions in Procedure:
    AG SP Sold-to party NotModifiabe, Mandatory
    AG BP Bill-to party Mandatory
    AG PY Payer Mandatory
    AG SH Ship-to party Mandatory
    Partner Determination Procedure Assignment:
    Account Group YG01 (account group of new Customer) assigned to AG (Sold-to-Party)
    Account Groups - Function Assignment:
    SP Sold-to party YG01 Customer BP
    Is there any other config I should do?

    Go to IMG path -- SD --> Basic Functions --> Partner Determination --> Setup Partner Determination --> Set Up Partner Determination for Customer Master. 
    -  There block "AG Sold To Party" and double click on "Partner Functions in Procedure".
    -  Ensure that for AG, you have maintained SP and the box Mandatory is checked.
    -  Block AG/SP and double click on "Partner Determination Procedure Assignment" and see for Group 0001, AG is assigned
    -  Click on "Partner Functions" and see for SP, KU is maintained under the tab Partner Type and the box is checked
    -  Click on Account Groups-Function Assignment.  Here ensure that the Account Group are assigned to your SP.
    thanks
    G. Lakshmipathi

  • In CRM relationship appends the Changed partner function in R/3 -Middleware

    Hi Experts,
    Partner functions in R/3 are mapped as relationship categories in CRM and the transfer is happening through middleware.
    However if I change the BP for an existing partner function in R/3, it is not changing the BP in corresponding relationship in CRM.Instead it is adding a new relationship category.
    Currently we are in CRM2007(6.0 version).
    Ex.
    - An account in R/3 has a partner function "Sold to Party" as BP Id "01234". This does create a relationship category in CRM "has sold to party" with BP Id 01234. -- it is working fine.
    - Later if I "change" the BP id 01234 to a new BP Id "05678" in R/3 for Sold to Party partner function, it does not update the relationship category in CRM. Instead it adds a new relationship category for "Sold to Party" with BP Id 05678.  This is issue now.
    We dont want to create a new relationship, instead we would like to update the relationship for new BP Id.
    If anyone has any any clue how to resolve this, please share your thoughts. It is a very critical requirement.
    Appreciate your help on this.
    appends relationship in CRM
    Regards,
    Srini

    Hi Shourav,
    Thanks for your reaply. I agree with you for the general scenario. But my question is littlebit different what you understand.
    I try to explain little bit detail this time.. Hope you undrstood my issue.
    We are facing issue in partner relationship deletion  functionality from ECC to CRM.
    Issue: Partner functions in R/3 are mapped as relationship categories in CRM and the transfer is happening through middleware.
    However if I change the BP for an existing partner function in R/3, it is not changing the BP in corresponding relationship in CRM. Instead it is adding a new relationship category.
    Ex.
    - An account in R/3 has a partner function "Sold to Party" as BP Id "01234" and a partner function relationship as ship to party with BP id  u201C05678u201D  and it is replicating this relationship correctly in CRM .
    - Later if I "change" the BP id 05678 to a new BP Id "05679" in R/3 for Sold to Party partner function, it does not update the relationship category in CRM. Instead it adds a new relationship category for "Sold to Party" with BP Id 05679. This is issue now.
    Any notes or work around solution for this issue is helpfull.
    Regards,
    Srini

  • Middleware: Changed partner function in R/3, appends relationship in CRM

    Hi Group
    Partner functions in R/3 are mapped as relationship categories in CRM and the transfer is happening through middleware.
    However if I change the BP for an existing partner function in R/3, it is not changing the BP in corresponding relationship in CRM.Instead it is adding a new relationship category.
    Ex.
    - An account in R/3 has a partner function "Sold to Party" as  BP Id "1234". This does create a relationship category in CRM "has sold to party" with BP Id 124.    -- Works fine. No issues.-
    - Later if I "change" the BP id 1234 to a new BP Id "5678" in R/3 for Sold to Party partner function, it does not update the relationship category in CRM. Instead it adds a new relationship category for "Sold to Party" with BP Id 5678.   ISSUE.
    We dont want to create a new relationship, instead we would like to update the relationship for new BP Id.
    If anyone has any any clue how to resolve this, please share your thoughts. It is a very critical requirement.
    Answer will be suitably rewarded with points.
    Thanks & Regards
    Vishal Mani

    Hi Michael,
    Thanks for asking . This Dinesh ( Vishal's colleague ) ..We found that the Dumps are because of the implmentation of the SAP Note 497146 which provides a enhancement to the existing FM BUPA_MWX_BDOC_MAP_REL_CENTRAL . This is throwing the short dump.
    We raised a OSS message and SAP replied back saying the behivour of the sytsem is as per standard and its not a bug .
    Can you please us to achive the following !!
    We want to avoid the replication of BP relationship ( sold to party to Z Custom A/c group  ) which does not have a Sales area ? Do  you know a BADI which can help us to achive this functionility ??
    I mean we want a control of the BP releationship replication via Middleware using BADI  .. Can you please help us here . Also please provide any list of BADIs which can help us on this ?
    Please get back at the earliiest , as we have a Go-live tommorow .
    Thanks and Regards
    Dinesh

  • Sold to Party from Ship to Party

    Hi,
    We have a requirement that when creating a service order, we need the sold to party to be determined when the ship to party is entered.
    Can someone pls tell how this can be achieved
    Points will be given
    Prachi

    Hi Prachi,
    This process is known as reverse determination. and reversal of the search direction for partner determination uses business partner relationships using the field Reverse Determination within the access sequence customizing setting. Path is IMG>CRM>Basic functions--> Partner Processing
    You create a access sequence for partner determination which should have only a single step.
    This setting is only relevant when you enter either Business Partner Relationships or BP Relationships by Sales Organization as the source for this single access.
    During partner determination using business partner relationships, the system normally looks in a partner's master data for the "Has the ..." relationship, such as "Has the ship-to party". Marking this field sets the system to look for the same relationship, but in the reverse direction, such as "Is the ship-to party".
    Leave the field Reverse Determination unmarked to set the system to function as usual.
    Mark the field to set it to read relationships in reverse for this single access.
    You make the following settings for the access sequence with one single access:
    <b>Source: Business Partner Relationships
    Details on the source: Ship-to Party
    Reverse source (this field): marked</b>
    You assign this single access to the partner function Sold-to Party.
    For the Ship-to Party, you can have either of the following settings :
    1) If the document does not have a preceding document then do not assign any access sequence to the Ship-to-Party partner function or
    2) If the document have a preceding document which will pass on the Ship-to Party details to the current one , then you can assign standard Access Sequence 1000 or your own copy of the standard access sequence number 1000.
    Hope this would help.
    Regards,
    Rekha Dadwal
    <b>
    You gain a point for every point that you reward. So reward helpful answers generously</b>

  • Creating multiple partner function for a sale order @ header level

    Hi All,
    I have a requirement where in i have to create more than one partner funtion for a sale order @ header level. But the system did not allow this sort of scenario and i got the error,
    Partner function ZZ can only occur  1 times in procedure TA (Sales Document Header)
    the function module that was giving this error was SD_PCHECK_PARVW_COUNT_OK
    here the function module checks if a partner function already exists if so it throws that error. This also updates the VBPA table where partner function is one of the key fields.
    Our issue is that we have to allow the system to enable posting 2 or more partner function for the same sale order. It was also verified that the unique key was unchecked during configuration.
    is there any other way of over coming this issue as we are updating the standard table. Is it possible??
    Thanks a lot in advance for your reply....

    I believe this is a configuration setting, based upon the details of your post.  Typically, a sales order can have multiple partner functions, but usually the partner type is not duplicated at a single level (header or one item).  For example, it would not be logical to have multiple ship-to partners at the header level...these would be unique at the item level, if required.
    Speak to your SD functional specialist about the configuration controls for partners, if you must have more than one partner with parvw = ZZ, for the entire order (header level).
    Edited by: DaveL on Aug 23, 2011 3:00 PM

  • Error msg: Partner Function SH already exists (only defined once)

    hi,
    when i am trying to enter two ship to parties for a sold-to party, i am getting this error
    Partner function SH already exists (only defined once)
    Message no. F2188
    Please advise why i am unable to add ONLY a ship-to party more than once, but i am able to add payer and bill-to party more than once.
    I have also defined customer hierarchy. Could it be a reason?
    Thanks in advance.

    Check the following note
    Note 1415987 - CMD_API: check for unicity of partner function
    G. Lakshmipathi

Maybe you are looking for