Sold to party popup

Hi Experts,
I am having a peculiar problem which goes as: I have maintained a few business partners(Persons) and their sold to party relationship with organization. the business partners (Persons) are not extended to sold to party role, only the relation organization are extended to that role. All partner determination and org determination seems correct. but when I create the transactions Service orders, as i enters the main business partners, i get popup for org data determination, which includes one organization that i maintained in relationship which is correct, but with that i also found the leading business partner (Person) as sold to party!!
ideally there should be no popup as only one organization is maintained in sold to party relationship, but i m getting 2 option in popup, one being organization and one the person itself.
Kindly Help

If the popup values are not needed directly in the va01 screen - then one way could be defining a field exit on sold-to field for this screen.
In the field exit u can call a Z func module passing the soldto number.
In the FM you can put your code to get the details u want , then use FM POPUP_WITH_TABLE_DISPLAY to display the contracts in the popup window.
Though there is not much u can do in a field exit - but u can give it a try.
- Kalpana
Message was edited by: Kalpana Tyagi

Similar Messages

  • Sold-to Party (Document header)

    Hi,
    when i create a sales order by a certain type and if in sold-to-party field i write a certain customer, a popup dialog Sold-to Party (Document header) appears with some information fields: Postal code, Email, Fax, Street adress,PO Box addres,Communication,....
    I want to modify the default value in Postal Code/City? How can i do that?

    hello, friend.
    are you referring to the cash sales type of order, and a customer that is of the one-time type (account group DEBI)?  if so, the system behavior is correct.  the customer is just a dummy and you enter the name and address of the actual sold-to.
    if above is not the case, please post again.
    regards.

  • How to create multiple ship to parties to one sold to party.

    Hi  ALL,
    Presently we are working with one sold to party having one ship to party.Now the same customer have placed the order with two different delivery points.For this existing customer, how i can create one more ship to party with different delivery address.Can anybody guide me where to start doing the configuration for this along with T codes.
    Thanks in advance
    kumar

    Hi Ramesh,
    As you said I have created one more SH and assinged to existing customer master record.When I am creating the sales order Popup is showing SH party with selection option of one SH.Here I am not able to create one sales order with two ship to parties.Can you come clear on this.Is it possible to create one sales order with two SH?
    Thanks in advance
    kumar

  • How to change sold to party in sales order

    Hi
    We have the below requirment of changing sold to party after creation of sales order...
    Below is the scenario
    Once sales order is created,purchase requisition is created autamatically and purchase order is created with reference to the purchase requisition..So when Goods receipt is done,the respective stock is getting reserved for that sales order...
    We wanted to change the sold to party option.
    After creation of purchase order,sold to party option in sales order is display only..
    Can u tell us how to make it changeable...
    Regards
    Sudha

    Hi,
    Why don't you try to make the Partner Function for Sold to Party as Modifible (Don't select Non Modifible) for the Sales Order Header in partner determination determintaion setting in customizing.
    You have to check with the partner determination procedure assigned to your sales order type and check accordingly.
    Reward points if it helps.
    Regards,
    Harsh

  • Sold-to-party Text data not getting displayed; Urgent

    I am current using a BI content 0CRM_COMP which contains sold-to-party, i have loaded this ODS, but when i view the data in bex i could only see the Key value and not the Text, even though i change the display mode to Key and Text both the columns displays only the Key value. is it because the master data is not loaded, i have also tried to load the Business Partner master data attributes and text till no use. Please help
    Note: These business partners are created in CRM and are nor from R/3

    Hi,
    Just check whether for this infoobject has master data and text option ticked or not in infoobject.
    If text option in there then search for the data scource0CRM_SOLDTO_TEXT or something like that which contain text for this particular infoobject and then laod the text for the same.
    Just got to the modelling tab -> infoprovider-> Application component in which you infoobject is present-> right click insert object as dat target-> give the name of your object this will give you data target one for master data one for text->activate data source and replicate in BW if not presen in BW-> make infosource on the text data source->make update rules for the text target and load.
    Or as Anil said sold to party is reference to customer load text into the custome with the same method iot will work fine.
    Hope it helps
    Thanks

  • Create Incident via CRM_UI, non-SAP components depending of sold-to-party

    Hello!
    We are using CRM_UI on Solman 7.1 ( SPS 10 ) to create Incidents. On the 3'rd step there is option to select SAP Components or non-SAP Components if defined. We are using a lot of non-SAP components.
    Is it possible to prevent users to choose all SAP component, only few of them depending of customer ( BP sold-to-party  )? Does it exist authorisation object for this?
    Thank's in advance!
    Best regards,
    Renato

    Hello,
    Please run SPRO tcode and search for
    Maintain User Application Components
    Use
    This activity maintains your application components. Create your own component hierarchy, and add it to the default SAP application components.
    Recommendation: Choose component names that are easy to recognize and distinguish.
    Activities
    1. Specify a component. If your components are hierarchical, enter the leading component first.
    2. Enter a description of the component.
    3. Specify the hierarchy level of the component (01-0n). Create the component hierarchy top-down.
    4. Specify the node type. Use node type 0 for a header, and 1 for normal nodes.
    5. Flag whether the node is selectable.
    6. Save.
    To configure the display of value help in the SAP component search, edit the VH_SAPCOMP_TREE parameter in the Define Parameters activity.
    BR,
    K.

  • SP ( Sold to Party )is not in table

    Hi
    This is Srikanth Can Some help me when i am creating a customer master with the account group 0001 after completing all the required fields  when want to save the record i am getting an error as Sp Sold to party is not table XXXX like that only for all these SH,BP PY.

    Hi,
    In VBPA table you will get the PARTNER FUNCTIONS of the SALES DOCUMENT
    Goto VBPA table with the VBELN number which is Sales document number , then check the PARVW field for the required Partner function
    The Partner functions maintained in the CUSTOMER MASTER are available in KNVP table
    There will be difference you can find between these two table if any thing added manually during processing of sales order.
    Hope it is clear,
    regards,
    santosh

  • CRM To ECC Sold to party Communication Details Not populated in ECC

    Hi All
    i have one problem when we create sales order through crmd_order we need to give sold to party and ship to party numbers suppose like
    8000002166 for both and status i keep as order created and in partner tab i i seem all partner funtions(sold to, ship to ,bill to, payer)with 8000002166
    in header overivew i given posting date as feature date like 30-09-2013 then i try to save this order.
    the order generated sucussfully but problem is i am not getting sold to party details in ECC when i check VA03 And open cretaed order in CRM and clicking on sold to party and i seem details for this but i am not getting communication details like telephone number and email id extension number.
    for this sold to party we already maintained all communication details in CRM.When i open this sold to party BP i am able to see all details
    didnt understand why these details not replicated to ECC?
    We implemented one custom class there we implemented badi.
    IF_EX_CRM_DATAEXCHG_BADI~CRM_DATAEXCH_AFTER_BAPI_FILL
    i am not getting BAPI ADDRESS Table values into  CT_BAPIADDR1
    how can i send communciation details to ECC For sold to party?
    The code part we follow like below
    TYPES : BEGIN OF t_otc,                                                        " Type to create a table with the given columns.
              bpid            TYPE bu_partner,                                       " variable of store processed business partner ID's
              otcid           TYPE bu_partner,                                       " variable of store processed OTC ID's
              otcguid         TYPE bu_partner_guid,                                  " variable of store processed OTC GUID's
              address         TYPE bapibus1006_address,
              tel1_numbr      TYPE ad_tlnmbr1,
              tel1_ext        TYPE ad_tlxtns1,
              e_mail          TYPE ad_smtpadr,
              END OF t_otc.
    *&                             V A R I A B L E S                         &*
      DATA : lv_bp_payer      TYPE bu_partner,                                       " Variable To Cast the payer Id into BU_Partner data type.
             lv_partner_fct   TYPE crmt_partner_fct,                                 " Variable To Store Partner Function Number.
             lv_partner       TYPE bu_partner,                                       " Variable To Store Current Business Partner ID.
             lv_process_type  TYPE crmt_process_type,                                " Variable to Store process type.
             lv_sales_org     TYPE crmt_sales_org,                                   " Variable to store sales org. name of order
             lv_dis_channel   TYPE crmt_distribution_channel,                        " Variable to store distribution channel of order.
             lv_division      TYPE crmt_division,                                    " Variable to store division of sales org. data.
             lv_role          TYPE comt_partner_parvw,                               " Variable to store retrieved role from FM.
             lv_role_value    TYPE parvw,                                            " Variable to store the role value of Partner Functions.
             lv_otc_guid      TYPE bu_partner_guid,                                  " Variable to store OTC GUIDs for the OTC ID.
             lv_otc_id        TYPE kunnr.                                            " Varaible to OTC ID revocered from Table.
      DATA: lv_busspartner           TYPE bapibus1006_head-bpartner,
            lw_central_data          TYPE bapibus1006_central,
            lw_centraldata_person    TYPE bapibus1006_central_person.
    *&                             W O R K A R E A S                         &*
      DATA : lw_address       TYPE bapibus1006_address,                              " Work Area to store address recovered for BPID.
    *Start of code change for Defect 904 Fix
             lw_tel           TYPE bapiadtel,
             lw_email         TYPE bapiadsmtp.
    *End of code change for Defect 904 Fix
    *&                          INTERNAL TABLES                              &*
      DATA : li_otc           TYPE TABLE OF t_otc,                                   " Internal Table to Store the OTC IDs and BPS.
             li_values        TYPE          zconst_values_t,
    *Start of code change for Defect 904 Fix
             li_tel           TYPE STANDARD TABLE OF bapiadtel,
             li_email         TYPE STANDARD TABLE OF bapiadsmtp.
    *End of code change for Defect 904 Fix
    *                       F I E L D - S Y M B O L S                         *
      FIELD-SYMBOLS: <f_orderadm>      TYPE bad_orderadm_h_mess,
                     <f_otc>           TYPE t_otc,                                   " Field-Symbol to Read the OTC TABLE data.
                     <f_partner>       TYPE bad_partner_mess,                        " Field-Symbol of Partner Table For Looping.
                     <f_bapiparnr3>    TYPE bapiparnr3,                              " Field-Symbol to Store The Row of BAPIPARNR3.
                     <f_bapiaddr1>     TYPE bapiaddr1,
                     <f_orgman>        TYPE bad_orgman_mess,                         " Field-Symbol to Read the ORGMAN table.
                     <f_values>        TYPE zcr_const_values.
    *&                             C O N S T A N T S                         &*
      CONSTANTS :  lc_program_name     TYPE progname      VALUE 'ZOTC',
                   lc_param_payer      TYPE paramname     VALUE 'PAYER',              " Constant to Store Payer Parameter name.
                   lc_ref_kind         TYPE crmt_object_kind VALUE 'A',
                   lc_req_1            TYPE zrequest_no VALUE '1',
                   lc_req_2            TYPE zrequest_no VALUE '2'.
    * Retrieving the general and Common Data for a Order.
      READ TABLE it_bus_trans_msg-orderadm_h INDEX 1 ASSIGNING <f_orderadm>.
      IF sy-subrc EQ 0.
        lv_process_type = <f_orderadm>-process_type.
      ENDIF.
    * Reading the Orgnisation Details from ORGMAN Table.
      READ TABLE it_bus_trans_msg-orgman WITH KEY ref_kind = lc_ref_kind ASSIGNING <f_orgman>.
      IF sy-subrc EQ 0.
    *   Storing the Sales Organisational Data to find the OTC_ID.
        lv_sales_org = <f_orgman>-sales_org.
        lv_dis_channel = <f_orgman>-dis_channel.
        lv_division = <f_orgman>-division.
      ENDIF.
    * Retrieving the partner function number for the payer by giving requirement no 2 and rule no 1.
      CALL FUNCTION 'ZCRAN_GET_CONSTANT_VALUES'
        EXPORTING
          pi_program_name = lc_program_name
          pi_req_no       = lc_req_2
        IMPORTING
          po_const_values = li_values.
      IF sy-subrc <> 0.
        RETURN.
      ENDIF.
    * Reading the value for the constant with the name as PAYER.
      READ TABLE li_values WITH KEY param_name = lc_param_payer ASSIGNING <f_values>.
      IF sy-subrc NE 0.
        RETURN.
      ENDIF.
    * Retrieving the Partner ID for the PAYER.
      READ TABLE it_bus_trans_msg-partner ASSIGNING <f_partner> WITH KEY ref_partner_fct = <f_values>-constant_value.
      IF sy-subrc EQ 0.
    *   Storing the current partner ID.
        lv_bp_payer = <f_partner>-ref_partner_no.
      ENDIF.
      REFRESH li_values.
    * Retrieving the Partner Function Number which are to be checked for replacing with the OTC ID with request no 1 and rule no 01.
      CALL FUNCTION 'ZCRAN_GET_CONSTANT_VALUES'
        EXPORTING
          pi_program_name = lc_program_name
          pi_req_no       = lc_req_1
        IMPORTING
          po_const_values = li_values.
      IF sy-subrc <> 0.
        RETURN.
      ENDIF.
    * Transferring the constant value to our table for Partner Fucntion.
      LOOP AT li_values ASSIGNING <f_values>.
    * Read Partner table for Header data and the reference partner function retrieved.
        READ TABLE it_bus_trans_msg-partner WITH KEY ref_kind = lc_ref_kind ref_partner_fct = <f_values>-constant_value ASSIGNING <f_partner>.
        IF sy-subrc EQ 0.
    *     Storing Current Partner Function.
          lv_partner_fct = <f_partner>-ref_partner_fct.
    *     Storing Current Partner No.
          lv_partner = <f_partner>-ref_partner_no.
    *     Retrieving the Partner Role (R/3) for the current partner function of CRM.
          CALL FUNCTION

    The problem is in the Lotus Notes security level, not in SAP.

  • How to update Sold-To Party (In ORDER_SAVE BADI)

    Hi,
    I have a requirement as follows:
    In for a Sales Order, In ORDER_SAVE BADI, I have to do validation for Sold-to Party. If validation fails, I need to display an error message and I need to clear the Sold-to Party field, hence user has to select another sold-to party.
    Could you please let me know, how can I clear the sold-to party, in ORDER_SAVE BadI. Any FM's to do that?
    Thanks,
    Sandeep

    Hello Sandeep,
    why you want to delete the sold-to ? I think its just easier to give a error message in the log, so the users  could enter a new sold-to. Within the badi order_save you can prvent saving with exception do_not_save  - see note 1519171 for detailed information.
    Best regards
    Rene

  • Excise invoice to ship-to-party but billing to Sold-to-party

    Hi Experts,
    My client wants to send pro-forma excise invoice to ship-to-party but wants billing to Sold to party. here Sold to party and Ship to party address will be different. can you tell me the settings which should I do.
    Thanks in advance.

    Hi,
    Create the Ship to party as a contact person and trigger the proforma excise invoice output type during proforma invoice creation.
    In the case of Normal Billing to Sold to party.
    regards,

  • Not able to change the value in 'sold to party' once disabled.

    Hi,
    I am validating the Business partner entered in the 'sold to party' field while creating a sales order in webclient UI.
    The error message pop up as expected but the field becomes disabled. I tried changing the field to editable by setting  rv_disabled = 'FALSE' in method GET_I_SOLDTO_NAME.
    Now the field is editable but it does not take the new value which i enter. it takes the old value only.
    How do i make the field to accept new values?
    Thanks in advance.
    Regards
    Shanthi.

    Hi Shanthi,
    Just check small config in your Partner determination profile if it helps you:
    Path: SPRO->CRM->Partner Processing->Define Partner Determination Procedure-
    Open you Partner determination Profile and go in details Sold-to-party partner and Mark Check box Changable to allow to make changes in partner.
    Regards,
    Dipesh.

  • 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

  • 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

Maybe you are looking for