Sold to Party in Support notification

Hi Gurus
Is it possible to populate Sold-to-Party and Requestor automatically in the Support notification in Solman? We have same username in Soution Manager and other satellite systems. The corresponding BP's are also there in the solution Manager system.
We have only one Sold-To-Party and that needs to be populated automatically whenever a user create a messages. Also the requestor BP also needs to be populated automatically.
Our Solution manager system is Solman 7.0 EHP1 SPS25.
Thanks
Rajat Sarkar

Hi,
Yes, it is possible. You need to define Sold to Party for your IBase in IB52 and you need to define BP for all users in solution manager system. Please make sure that in BP for each user, corresponding system field should be populated so that requester field in Support desk message will be automatically populated.
Thanks
Sunny

Similar Messages

  • Service Desk Determination. In the support message Sold to party &

    Dear Friends,
    Sold to Party , IBASE & Component are not fetching the support message created from Satellite system BI.
    I have configured the Service Desk for satellite system ECC 6.0. Now I have configured it to BI, but Sold to party & IBASE & Component are not fetching in the support desk message.
    Following things done for adding satellite system BI to Solman.
    1) IBase creation for BI is done.
    2) SMSY configiration also done for BI
    3) BP no created in Solman, mapped identification also.
    What else i need to check.
    Can anybody tell me which roles I need to assign the BI end users for raising the message. Is this issue related to roles
    Regards
    PK

    Hi,
    There are several predefined roles for Support Desk, containing specific authorizations.
    Rolle
    SAP_SUPPDESK_ADMIN Administrator role for Support Desk. Comprises
    authorizations to configure Support Desk
    SAP_SUPPDESK_PROCESS Role for processing Support notifications. Comprises all the
    authorizations for notification processing and using the Solution Database
    SAP_SUPPDESK_DISPLAY General display role, no authorization to create or change
    notifications
    SAP_SUPPDESK_CREATE Role to create Support notifications. This role must be
    assigned to both users who will create notifications in the
    SAP Solution Manager and to users who will create
    notifications from the satellite systems in the SAP Solution
    Manager.
    Regards,
    Deepanshu

  • Sold-To Party and Reported missing when doing Help - Create Support Message

    Sorry, I know this has been asked multiple times, but I'm missing something in the responses.  The responses I am finding either don't seem to apply to my situation, or aren't detailed enough to explain what I'm supposed to be doing.
    Solution Manager 7.0 EhP1 SAPKITL435.
    If we try to do a "Help - Create Support Message" from within our production Solution Manager system, the "Reported by" field is correct, but the Sold-To Party is blank.
    If we try to do a "Help - Create Support Message" from within our non-production Solution Manager system, both the "Reported by" and  Sold-To Party fields are blank.
    If we try to do a Help - Create Support Message" from another SAP system whose RFC is pointing to our non-production Solution Manager system, both the "Reported by" and  Sold-To Party fields are blank.
    I've looked at IB52, as well as the SPRO activities under "Partner Determination Procedure."  I think a big part of my problem is that they just don'e make sense to me yet, because I can't figure out what I should be changing.
    For example, IB52 looks to me like it only applies if you want to assign something to the same person all the time.  Am I missing something there, or is that an answer to a different question?
    I also can't figure out if I need to create something new in "Define Access Sequences," or modify something existing, and, if I modify, to what?
    Does anyone know where I could find specific instructions for setting this up?

    Hi Brenda,
    Regargind this issue, please check if Sold-To party is maintained for
    your system with IB52 in your solman system as the steps below:
    SOLUTION MANAGER system
    ->IB52
    ->select the system on left hand side
    ->click on 'goto' on top menu
    ->Select 'partner'
    ->Now maintain Sold-To party
    Also check below note:
    1165357    Sold-to-Party is not assigned to Service Desk messa
    As you said ou already assigned then i would request you to please check if you have assigned at the system level or not. Somtimes people define at top of the tree and also at system level. Please assign at system level and delete all other. Most of the times this is the issue Sold-to-party doesnt fill automatically.
    For reported by field:
    Please check the note: 824640: Customizing missing for Service Desk in Solution
    read this note carefull and this will help you fixing the reported by issue.
    Please, make sure you have applied the following corrections:
    1439191 Incident Create: Message Reporter or Processor is not saved
    1486132 Incident Create: Enhance search help of Reporter field
    1497700 Work center: Message details not updated after refresh
    After this if you still having issue you need to provide more details but i think this will fix the issue.
    Thanks
    Regards
    Vikram

  • Sold to Party data transfer from Order to Notification

    Hi,
    According to our process, the person who reports a malfunction or requests service for customer can also generate the appropriate order. In Order Customizing, the indicator "Maintain Notification data on order header" is set, this enables system to immediately create a notification in the background when you create the order. Due to this, reference objects, dates, work center, etc are automatically copied from Order to Notifications as expected. However, Sold-to Party / Customer is not getting copied from Order to Notification.
    Following items have been configured:
    - Both order & notification have the same partner procedure
    - No user-exit is active
    - We do not copy the partner from the reference object(e.g. equipment) to the service order. We plan to enter the customer number directly in the service order (as the equipment is not going to have a customer/partner number)
    - "Copy Partner Functions to Master and Movement Data" customizing is activated for our partner procedure
    Any suggestions, which will enable copying of customer / sold-to party data from Order to notification through configuration.
    Thanks in advance. Please let me know if you need any further details.
    Regards,
    Avinash

    [OSS Note 546738|https://websmp130.sap-ag.de/sap%28bD1lbiZjPTAwMQ==%29/bc/bsp/spn/sapnotes/index2.htm?numm=546738]
    http://www.sapfans.com/forums/viewtopic.php?f=7&t=323195&start=0&st=0&sk=t&sd=a
    Please check the above links. Also make that partner function as mandatory for that notification type & then try.

  • Sold-to party rol doesn't fit new support message

    Hi,
    I'm configuring Solution Manager SP17, I work at VAR SAP so I've to manage many customer numbers. Some scenarios are running.
    I've a customer with three SAP systems, these SAP systems have been defined at smsy transaction in Sol. Man. VAR successfully. So these systems exists at ib52 transaction too.
    From satellite SAP (customer site):
       1.- system->system->status Installation number is 0020225238
       2.- at service.sap.com for this customer this is the installation number that appears for this SAP system.
    At Solution Manager VAR SAP(VAR site):
       1.- smsy->systems at the header data tab this installation number appears 0020225238
       2.- ib52 for this SAP system I've defined this system with one entry to the correct client:
                  BWP 0020225238 100
       3.- I've filled for this SAP System and the other two SAP systems for this customer partner so I select BPW SAP system->goto->partner.The business partner with function sold-to party has these roles: business partner and sold-to party. At the identification tab it has 3 entries(one per SAP system):
        BWP 0020225238 100 SANTI
    If I execute steps to create a support message:
    1.- from satellite SAP system(customer site) help->create support message I create and send successfully the support message
    2.- from Solution Manager VAR SAP(VAR site) crm_dno_monitor transaction I open the support message just created and :
               - sold-to party field is empty.
    (this field is filled successfully to the other two SAP systems for this customer)
              -  at transaction data buttton->SAP Attributes tab the installation number that appears is 0120009939 and not 0020225238.
    Please could you help me?
    Thanks and Regards.
    Raul

    Hi Sreedhar,
    Thanks for your reply.
    As I typed at my first description. The role sold-to party is working. This customer has three SAP systems: R/3 development, R/3 productive, BW productive. So when the customer sends a SAP message from his SAP satellite system to our SAP VAR solution manager, the sold-to party rol works only to R/3 development, R/3 productive but doesn't work to BW productive(Netweaver 04).
    I've chequed that:
    - ib52 transaction the SAP satellite system BW productive has the same installation number that you can view If you logon at the SAP satellite system BW productive->system->status. The client is correct too.
    - bp transaction the sold-to party Business Partner has three lines( one per SAP system).
    Please could you help me?
    Thanks and Regards.
    Raul

  • Default value for Sold to Party and Reported By with Support Message

    I have customized the service desk scenario and went through the entire service desk implementation guide part I blog that talks about the partner setup.
    When I create a support message through the service desk scenario (under help) in the satellite system it does default the sold-to-party and the reported by person in the resulting document.
    When I create a support message in Solution Manager out of DSWP or SOLAR02 it does as well.
    However when I create the support message out of Solution Manager under help it does NOT default the sold to party and reported by, and I always have to correct that in the document later on.
    Has anyone experienced this before and can tell me why this happened. Obviously has something to do with setting up the partner in Solution Manager, but I do not understand how it can work for the Satellite system but not in Solution Manager itself.
    Thanks
    Paul

    > Has anyone experienced this before and can tell me why this happened. Obviously has something to do with setting up the partner in Solution Manager, but I do not understand how it can work for the Satellite system but not in Solution Manager itself.
    Did you generate BP entries for the SolMan system itself?
    Markus

  • 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

  • Service Desk Message - Sold-to Party and Reported by

    Hi Team,
    The Sold-to Party, Reported by are automatically populated in CRMD_ORDER whenever I create Service Desk Message from Satellite Systems, But when I create Support Message in Solution Manager, these does not get populated.
    Thanks,

    Hi NIshkam ,
    If you are creating the support message from help->create support message in solution manager
    Please check the following
    1. Whether the solution manager is set up in the I-Base in transaction IB52.
    2. Check if your ID is maintained in the identification tab of Business Partner for the    solution manager server.
       (path : transaction- BP -> enter the login ID ->Select change in BP role as Business Partner (Gen.)
                -> Select the Identification tab.)
       your ID should be maintained as below for the solution manager:
    ID Type              System - Installation Number - Client - BP ID
    CRM0001             zzz   - xxxxxxxxxx          -   999  - login ID.
    if these are done then system should be able to recognize the reported by and sold to party.
    if you are using CRMD_ORDER trasnaction for the creation of the support message, then the reported by field, SAP Component field and I-Base are entry fields and are not automated. On entering these and save the reported by , support team and Sold to party will be determined base on your configuration.
    check if this of help,
    regards,
    Srinivas
    Edited by: Srini24 on May 4, 2010 9:06 AM

  • How to update Sold to Party for a contract

    Hi Gurus,
    I got a strange and fuzzy requirement. My client wants to update the Sold-to-party in 2011 for the contracts created in 2010 with any status and with any sub-sequent documents to that particular contract. I know SAP wont support on this. because it is a standard functionality that we cannot update Sol-to-Party rather we can update BP,PY ans Shipto etc.... But still this my requirement. Anybody any solution is always helpful to me..
    Thanks,
    Bhargav.

    Hi all,
    I just want to add one more point to my requirement I am using this FM SD_SALESDOCUMENT_CHANGE to update Partners other than Sold-to-party. And I found out that we have another FM SD_PARTNER_SINGLE_MODIFY to update partners. this second FM is there in the first FM. So please provide your valuble solutions/comments
    Anticipating for your replies,
    Regards,
    Bhargav.

  • Table for Process type with BP Number of sold to party

    Hi Friends,
    Please share me Table name where i'll get the Process Type (Transaction Type) and Sold to Party Number or BP Guid of the transaction.
    I want to create Target group for BP's who are involve in Particular Transaction.
    For infoset creation i have already tried Table CRMD_ORDERADM_H and CRMD_ORDER_INDEX but not able to join exact conditions.
    Regards,
    DD's

    HI frieds,
    Thanks for u r support i have created Infosets using table CRMD_ORDERADM_H, CRMD_LINK & CRMD_PARTNER and, made joining link between them (Actually both Guids in CRMD_LINK and CRMD_PARTNER are not maching)
    Next step is i have created Datasource using my infoest and created Attribute list for same.
    After all this excercise i tried to Create target group for BP's who are involved in particular transaction(Process type) but in target group count come to ZERO !!!!!!!!! why this happening ???
    Please understand my final expected output which is in bold
    Regards,
    DD's

  • "sold-to party" role "sales area"

    Hi,
    I'm working at VAR Solution Manager 7.0 SP17.
    When I create a support message from satelllite system or workcenter this support message is created successfully but when I open it at crm_dno_monitor I get two errors:
    Pricing data for partner 323 could not be read.
    Enter a Currency
    About detail error:
    Diagnosis
    The attempt to read the pricing data for the current, valid business partner from the customer master was unsuccessful.
    The access was carried out with sales organization 'O 50000721', distribution channel '' and division ''
    If you have maintained a sales area conversion in R/3 that must be loaded per download into the CRM System (tables SMOTVTA and SMOTVKOS), this sales area is converted before the actual access.
    System Response
    The document is incorrect until the pricing data can be determined.
    Procedure
    The pricing view is probably missing for your business partner in the customer master. Maintain this data. To do this, you can call up transaction BP for maintaining the business partner. In the locator select your business partner and load it by double-clicking. Choose the "sold-to party" role. Press the "sales area" button and choose the sales area given above. Maintain the incorrect data in the billing data screen.
    I know the error reason but I don't know how to solve it. About errors:
    BP 323 is the sold-to party so if I go to TA bp->323->sold-to party role->button "sales area data" -> Sales area->Sales Organization any value appears. The same to Distribution Channel field
    I know that this error is generated by ppoma_crm configuration so at this TA my conf is:
    GRUPOTEC(organizational unit)
    tab function->checkbox sales->checked Sales Organization
    tab function->checkbox service->checked Service Organization
    tab attributes->checked Obj. Permitted in Determination
    tab attributes->country->ES
    Check consistency->green
    GENERAL(organizational unit)
    tab function->service->local->checked service team
    tab attributes-> sales -> NO checked Obj. Permitted in Determination
    tab attributes-> service -> checked Obj. Permitted in Determination
    Check consistency->green
    GENERAL(manager)
    tab attributes-> service -> checked Obj. Permitted in Determination
    Check consistency->green
    Please could you help me?
    Thanks and Regards.
    Raul

    Hi Prakhar,
    I've checked this parameters and it contains values
    spro->CRM->master data->org management->Division Settings->Define Divisions:
    Division     Description
    00     Product Division 00
    01     Product Division 01
    10     Product Division 10
    20     Product Division 20
    spro->CRM->master data->org management->Organizational Data for Sales Scenario->Define Distribution Channels
    Dist. Chan.    Description
    01                 Distribution channel 01
    spro->CRM->master data->org management->Organizational Data for Sales Scenario->Define Combination of Distribution Channel and Division
    01     Distribution channel 01     01     Product Division 01
    Regards
    Raul

  • Default Sold To Party and Message Processor on a Message

    Hi All,
    I have 2 questions on here regarding Service Desk.
    I have set a BP as Sold To Party in tcode BP and maintain its address. In IB52 transaction I already set the respective BP as sold party to all satellite system. Somehow when I create the message, and open the created message from service desk, the Sold To party field is still blank. What did I miss here ?
    Second, with PFAC_RESPO I've assigned an users as default support team for based on message component. But this setting only for set the default Support Team in the message, not the message processor. How do I set the default message processor ?
    Thanks & Regards

    hi,
    this is depending on what you want to set-up (every company has his own strategy)
    in big company you want to assign the support team only and let the agents pick-up message for their team, in smaller you might want to assign the processor also
    if you want to assign support team based in IBASE component you need to continue like you need
    but you need to add the SLFN0003 in your IBASE profile
    1. For doing this you need to go in CRM customizing by following this path
    Master data
    Installed base
    Assign partner determination procedure
    go and check the line for the IBASE category 01, in standard should be 0000032, you need to define your own profile (keeping the standard like it is)
    2. Go now in partner profile change follwoing this path
    Basic function
    Partner processing
    Define partner determination procedure ZIBASEXX (name you want) by copy of 000032
    Add the support team SLFN0003
    3. and go back to change the IBASE category 01 changing 0000032 into ZIBASEXX
    that's it !
    If you want to let the processor depend on IBASE, you can do the same or usually you define your own action for this
    I hope it helps
    br Xavier

  • Change Request SDCR - Sold to Party has to appear by default from IbaseComp

    Hi,
    TCode: CHARM_CREATE
    In this screen I dont want to enter the Sold to party.
    'Sold to party' has to come by default  based on the IBase Component entered In Change Request SDCR Transaction. Is there any setting for the same.
    In case of support desk when we create a message, sold to party comes automatically, Bcz in IBase Partner Sold to party is maintained. Like this can we make it for Change Request(SDCR) transaction.
    Regards
    Praveen Khot
    +91 9724035023

    Hello Praveen,
    To make the "Sold To Party" be determined from the IBase in the SDCR, you have to adjust the partner determination procedure SDCR0001 using the same access sequence for "Sold To Party" than in the partner determination procedure for the SLFN (i.e. 0018 SAP Service: Determination via IBase/Ind Object from Ref. Object Set).
    Then in CHARM_CREATE, leave the "Sold To Party" field blank. It will be populated during the creation. Go to CRMD_ORDER to check the assignment.
    Hope this helps.
    BR
    Stéphane.

  • Err.Sold-to party 1 not mainted for sales area EL01 01 01

    Hello SAP Gurus
    I am trying to save a quote from an external application using .NET connector which calls the bapi 'BAPI_QUOTATION_CREATEFROMDATA2'.
    I am getting back an error 
    E        VP     197       Sold-to party 1 not mainted for sales area EL01 01 01 .
    I am trying to search for this error on all SAP related areas and am not able to find anything that answers my question.
    Any feedback will be highly appreciated.
    Thanks
    Ram

    >
    Ram Prasad wrote:
    > Fortunately or unfortunately I am the only SAP guy in my company and I am actually certified in XI and but am wearing different caps at different time.
    ..Exactly You remind me my early career of SAP,I was the Only Person In My project,No matters it was kind of Support one,But i had been asked to handle some Tedious Asset Accounting isses-Some how i servived and turn the things around me,And Believe me The Stuff i learnt in such tiny 7 month is far More than i learnt my rest of my Life.
    Fortunately~

  • How to automatically set value of sold to party field in crmd_order screen?

    Hi Experts,
    We have a requirement where we have to automatically populate a standard SAP screen field when the screen opens. The T-code is crmd_order and the field is present in the fast entry tab whenu201Dcreate support messageu2019 is clicked. Now I am trying to achieve this by implementing the BADI which this T code calls. There are no user exits to this as per my understanding. There are some 20 BADIs this Tcode calls before opening. I have tried implementing almost all of them but the value is not getting reflected on the screen field. List of BADIu2019s called are as below.
    We are trying to automatically populate the sold to party field based upon the guid of the support message. Based upon this guid of the support message we are fetching list of partner function from u201CBAPI_ACTIVITYCRM_GETDETAILMULTu201D. Then we are taking the partner function value of u201CSLFN0002u201D. The BP number captured from this partner function will be passed to u201CBAPI_BUPA_ADDRESS_GETDETAILu201D to get the country of the super user. Based on this country the sold to party is to be determined.
    We have made a Z table for fetching this sold to party/region based on the country derived from above logic:
    Z Table
    Country                 Region/Customer/sold to party
    IN                            IN/BAN-C1
    BD                          IN/BAN-C2
    US                          US/CAN-C1
    Now these unique (sold to party/region) values  based on the country has to be populated automatically on the sold to party field of the screen (CRMD_ORDER).
    The logic for deriving the same is correct and the main problem is to default it on the screen field.After getting the value of the required field I am trying to display it on the screen by using the standard FM u201CCRM_ORDER_MAINTAINu201D and passing the value in IT_PARTNER.The FM is getting executed but the value is not getting reflected on the screen. I donu2019t understand where it is going wrong I am not able to solve this.Kindly let me know if anyone can throw some light on this.
    Regds,
    vlp

    Hi vlp,
    You can achive it with BAdI:CRM_ORDER_FIELDCHECK. Actually I've implemented the similar case  with this BAdI. This BAdI is called many times because it always works when any field is changed. So you should restrict the timing your logic works.
    Regards,
    Masayuki

Maybe you are looking for