How to validate Sold to party while creating sales order

Hi All,
I need to validate the sold to party which is entered when a order is created.
I able to read the Partner no using the FM u2018CRM_ORDER_READ_OWu2019, but how can I check if this partner number has u2018sold to partyu2019 function assigned.
Thanks & Regards
Shanthi

Hi Shanti,
There is a little twist in the validation that you intend to do to meet your business requirement. I will provide you with the Sap help link also. Have a look at this and you will understand the same.
[Partner Function|http://help.sap.com/saphelp_sm40/helpdata/EN/3c/92eceb484a11d5980800a0c9306667/content.htm] - Come to very end. Here there is a pictorial representation of how you can map a Partner function with the Business Partner Master Data. The system also maps in the similar way.
The Database tables which might be of help to you are BUT050 - Business Partner Relationship Category,  CRMC_PARTNER_PFT - Definition of Partner Function Types. The rest you need to follow your own logic. I guess this will be enough to help you to get started. Let me know if you need any more inputs.
Hope this helps.
Thanks,
Samantak.

Similar Messages

  • User Exit for correct ship-to Party while Creating Sales Order

    Dear Friends,
    Pls let me know which User Exit should I use to validate the Ship-to Party on the basis of Sold-to Party, while creating a sales order.
    In other words we wish to make sure that the user gives the correct Ship-to party corresponding to the Sold-to party, while creating a sales order.
    Regards,
    Alok.

    Dear Naveen,
    Thanks for replying.
    I do agree with you that SAP may validate the Ship-to Party in accordance with the Sold-to Party. But still the user may change  that Ship-to Party value and save the Sales Order with a wrong Ship-to Party.
    Here, my user wants a check/validation that no one should be able to save the sales order with wrong Ship-to Party other than the ones defined in Customer Master.
    Hope you got the issue now.
    Regards and thanks once again,
    Alok.

  • How to manual maintain TAX condition value while creating sales order

    Hi
    I am creating one Tax condition suppose JLST without access sequence .
    while creating sales order I am manually maintain the % value of TAX. suppose it is 1%
    then I see It show some value in TAX .
    save that sales order & creating delivery document for that but when I create Invoice its show error.
    " Tax code  in procedure CMTAXP is invalid ".
    I know the configuration only for Tax condition with vk11 condition record .
    BUT now I want to maintain TAX condition at the time of creating sales order.
    so I remove the access sequence of that condition .
    but It shows tax code error while billing.
    My main question is that If i maintain condition record while creating sales order then how i can assign Tax code .
    Can it is possible ?
    if yes then How?
    please help me.
    thank you

    Hi,
    The "straight-forward" answer for Tax Code creation is contact the FI consultant. He shall help you, by creating Tax codes.
    I have tested, with creating a tax cond type (copy of MWST) & manually entering values. I can create Sorder, Dlv and Bill but I cannot create an Accounting document. That is because of every line (amount) a Tax code is necessary.
    I THINK, you can NOT have manually filled tax codes; access sequence is needed to get the tax value (%) and the Tax code from the condition record.
    There is lot of material on the web to understand Tax classification, code etc. etc. See a useful link below -
    http://www.sapgeek.net/2010/04/sd-determines-tax-code/
    In short Tax code is a must and take the help of your FI consultant for the configuration of the same.
    BTW - Tax code is already made created for MWST, therefore I suggested that you can use MWST. Furthermore, you can change the values corresponding to Tax codes in FTXP.
    But if you are a beginner in these things, better take help.

  • How to block the material qty to 1 while creating sales order (VA01)?

    Hi All,
    Scenario :  We have 20 Materials each with 100 qty in Plant. In the sales order we should have all the 20 materials with qty one. The sales order should throw an error if the material qty is more than 1 and should not allow to create a sales order.
    so is there any transaction code where we can block the entire material qty to 1 from the same plant while creating sales order?
    Note: We should not set in MM01 "Minimum order qty". Assume we have 100 material in plant we can't set for each material one by one "minimum order qty".Instead of that is there any option to set the whole material qty to 1 as minimum while creating sales order?
    Kindly guide me how to proceed.
    Thanks,
    Renjith

    If you have access to idoc before calling the processing Function module, Adding header text segments E1EDKT1 and E1EDKT2 to the idoc will create the header text.
    Regards
    Sridhar

  • While creating sales order I am getting  Sanctioned party list blocked  but I am able to create delivery, and PGI

    Dear GTS Experts,
    While creating sales order I am getting  Sanctioned party list blocked, but I am able to create delivery, and PGI.
    Where Is the wrong ?
    Thanks a lot
    Venu gopal

    Dear Venu
    Based on your message shown in the system, can you check the field in Control Settings for System Reaction in the Document type settings via Application Levels in the feeder system. This Field '' System Response in Feeder system if SAP GTS fails'' should be maintained with ''A''. I think in your case it could be 'Blank'' Thats why the system is allowing you to create the subsequent documents accordingly.
    Please let me know if any further inputs required.

  • How to restrict the order reason in Tcode Va01 while creating sales order

    Hi Gurus,
    My requirement is
    while creating sales order in VA01
    if order type is Zvol
    than the list of order reasons has to be restricted.
    Now 15 are coming from OVAU  tcode
    I need only 5 from these.
    Thanks & Reagrds
    kals.

    Hi,
    By doing the user exit in IW32 we achieved the requirement of restriction of maintenance order TECO functionality if any Service Entry sheet pending with reference of maintneance order.
    regards
    JKM

  • How to change the status of material while creating sales order via BDC

    Hai.
    In BDC while creating sales order( va01 posting ) it is stucking up in middle saying material is new. I.e Sales order (va01) is not  getting created because  of material status is new . I want to create sales order  (va01) even  material status is new.
    pls give me out the solution. Points will be rewarded.
    thanks & regards,
    sami.

    Hi,
    If you drag the line item a little towards the right side, you will find a filed material entered. The one you see in the material filed on sales order over view screen is the one determined. You can as well double click and see the fields material entered and material determined.
    Is there anything else you are expecting to see as part of analysis ?
    Regards
    Sadhu Kishore

  • How to hide componant row of BOM while creating sales order  OR AR Invoice

    Dear expert
    my client wants to create Sales order with Sales BOM, but they do not want to see componant product while create sales order or AR invoice they want to see only parent items.
    Please help me asap

    Hi,
    check below link
    Avoid printing child items of Sales BOM in AR Invoice
    Regards
    Deepak Tyagi

  • 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

  • Change the Sold to Party(SP) in sales order in change mode

    Hi,
    Is it possible to change the Sold to Party(SP) in sales order in change mode?
    If yes then How??
    Regards
    Somnath

    Hi somnath,
    It is very much possible to change the sold-to-party in the change mode of Sales order(VA02).
    Goto VA02-->enter the sale order number.
    Press enter.
    In the overview screen if you change the sold-to-party then every thing will be redetermined(Taxes and pricing procedure etc...).These will be determined from CMr etc.
    You cannot change the sold-to-party at the partners tab that is present in the Header details.
    It will be greyed out.
    If you change the sold-to-party at the overview screen as suggested earlier it will not apply to the item.
    You are also going to see this message while changing.
    And finally save the document.
    Regards,
    Krishna.

  • Hi   error while creating  sales order

    hi
    i am getting 'not able to save' message while i am creating sales order.
    how should i proceed to know where is the problem???
    i tried debugging but it is taking lots of time, is there any other way i can know the reason for this error in standard code.
    there is no wrong data entry while creating sales order.
    i just want to know what are the ways to know where is the problem in the standard code.
    thanx
    rocky

    hi ,
    try too create a sales order after that check transaction code ST22 U WILL FIND AN SHORT DUMP  then check in the source code extract an pointer will be visible where the error is coming and it will also show the program name , please read the dump analysis care fully
    srinivas

  • Automatic creation of  settlement rule while creating sales order

    Hi Friends,
    Can any one help me how to create settlement rule automatically while creating sales order i.e saving sales order. Is there any function module or any badi which can be used.. please suggest.
    thanks
    bobby

    Hi,
    Here is the solution , First Create a sustitution by going into OPSN Transaction , only user exit say 'U902'
    and write the form routine in Program named 'ZRGGBS000'
    The code is below ,
    *&      Form  U902
       Automatic Generation of Settlement Rule For WBS and Company 4180
    FORM u902.
    Exit For Automatic Settlement Rule Creation for WBS Billing elements
      IF sy-tcode = 'CJ20N' or sy-tcode = 'CJ01' or sy-tcode = 'CJ02'.
        DATA   lv_proj TYPE ps_pspid.
        lv_proj = proj-pspid.
        EXPORT lv_proj TO MEMORY ID 'PSPID'.
    Calling YGPS_CJB1EXEC Program For Creating Settlement Rule
        SUBMIT ygps_cjb1exec AND RETURN.
      ENDIF.
    ENDFORM.                                                    "u902
    *& Program  YGPS_CJB1EXEC
    PROGRAM  ygps_cjb1exec.
       Automatic Generation of Settlement Rule For WBS and Company 4180
    Called From Exit For Automatic Settlement Rule Creation for WBS Billing elements
    DATA: bdcdata_wa  TYPE bdcdata,
          bdcdata_tab TYPE TABLE OF bdcdata,
          itab TYPE TABLE OF bdcmsgcoll.
    DATA :lv_currm LIKE bkpf-monat,
          lv_curry LIKE bkpf-gjahr,
          lv_prevm LIKE bkpf-monat,
          lv_prevy LIKE bkpf-gjahr,
          lv_proj TYPE ps_pspid,
          lv_mode TYPE c,
          lv_time TYPE sy-uzeit.
    DATA :g_datfm            LIKE usr01-datfm,
          g_dd(2)            TYPE c,                         " Day
          g_mm(2)            TYPE c,                         " Month
          g_yyyy(4)          TYPE c,                         " Year
          g_sydatum(10)      TYPE c.
    IMPORT lv_proj FROM MEMORY ID 'PSPID'.
    lv_mode = 'N'.
    CLEAR bdcdata_wa.
    bdcdata_wa-program  = 'SAPLKAZB'.
    bdcdata_wa-dynpro   = '1000'.
    bdcdata_wa-dynbegin = 'X'.
    APPEND bdcdata_wa TO bdcdata_tab.
    CLEAR bdcdata_wa.
    bdcdata_wa-fnam = 'BDC_CURSOR'.
    bdcdata_wa-fval = 'PRZB-VARIANT'.
    APPEND bdcdata_wa TO bdcdata_tab.
    CLEAR bdcdata_wa.
    bdcdata_wa-fnam = 'PRZB-VARIANT'.
    bdcdata_wa-fval = 'ZGPS0001'.
    APPEND bdcdata_wa TO bdcdata_tab.
    CALL FUNCTION 'GET_CURRENT_YEAR'
      EXPORTING
        bukrs = '4180'
      IMPORTING
        currm = lv_currm
        curry = lv_curry
        prevm = lv_prevm
        prevy = lv_prevy.
    CLEAR bdcdata_wa.
    bdcdata_wa-fnam = 'RKAUF-FROM'.
    bdcdata_wa-fval = lv_currm.
    APPEND bdcdata_wa TO bdcdata_tab.
    CLEAR bdcdata_wa.
    bdcdata_wa-fnam = 'RKAUF-GJAHR'.
    bdcdata_wa-fval = lv_curry.
    APPEND bdcdata_wa TO bdcdata_tab.
    CLEAR bdcdata_wa.
    bdcdata_wa-fnam = 'BDC_OKCODE'.
    bdcdata_wa-fval = '=VARC'.
    APPEND bdcdata_wa TO bdcdata_tab.
    CLEAR bdcdata_wa.
    bdcdata_wa-program  = 'RKPSEL00'.
    bdcdata_wa-dynpro   = '1000'.
    bdcdata_wa-dynbegin = 'X'.
    APPEND bdcdata_wa TO bdcdata_tab.
    CLEAR bdcdata_wa.
    bdcdata_wa-fnam = 'BDC_CURSOR'.
    bdcdata_wa-fval = 'CN_PROJN-LOW'.
    APPEND bdcdata_wa TO bdcdata_tab.
    CLEAR bdcdata_wa.
    bdcdata_wa-fnam = 'CN_PROJN-LOW'.
    bdcdata_wa-fval = lv_proj.
    APPEND bdcdata_wa TO bdcdata_tab.
    CLEAR bdcdata_wa.
    bdcdata_wa-fnam = 'CN_PSPNR-LOW'.
    bdcdata_wa-fval = space.
    APPEND bdcdata_wa TO bdcdata_tab.
    CLEAR bdcdata_wa.
    bdcdata_wa-fnam = 'CN_NETNR-LOW'.
    bdcdata_wa-fval = space.
    APPEND bdcdata_wa TO bdcdata_tab.
    CLEAR bdcdata_wa.
    bdcdata_wa-fnam = 'CN_ACTVT-LOW'.
    bdcdata_wa-fval = space.
    APPEND bdcdata_wa TO bdcdata_tab.
    CLEAR bdcdata_wa.
    bdcdata_wa-fnam = 'CN_MATNR-LOW'.
    bdcdata_wa-fval = space.
    APPEND bdcdata_wa TO bdcdata_tab.
    CLEAR bdcdata_wa.
    bdcdata_wa-fnam = 'BDC_OKCODE'.
    bdcdata_wa-fval = '/00'.
    APPEND bdcdata_wa TO bdcdata_tab.
    CLEAR bdcdata_wa.
    bdcdata_wa-fnam = 'BDC_OKCODE'.
    bdcdata_wa-fval = '=SAVE'.
    APPEND bdcdata_wa TO bdcdata_tab.
    CLEAR bdcdata_wa.
    bdcdata_wa-fnam = 'BDC_OKCODE'.
    bdcdata_wa-fval = '=VBAC'.
    APPEND bdcdata_wa TO bdcdata_tab.
    CLEAR bdcdata_wa.
    bdcdata_wa-program  = 'SAPLSPO1'.
    bdcdata_wa-dynpro   = '0100'.
    bdcdata_wa-dynbegin = 'X'.
    APPEND bdcdata_wa TO bdcdata_tab.
    CLEAR bdcdata_wa.
    bdcdata_wa-fnam = 'BDC_OKCODE'.
    bdcdata_wa-fval = '=YES'.
    APPEND bdcdata_wa TO bdcdata_tab.
    CLEAR bdcdata_wa.
    bdcdata_wa-program  = 'SAPLKAZB'.
    bdcdata_wa-dynpro   = '1000'.
    bdcdata_wa-dynbegin = 'X'.
    APPEND bdcdata_wa TO bdcdata_tab.
    CLEAR bdcdata_wa.
    bdcdata_wa-fnam = 'RKAUF-BATCH'.
    bdcdata_wa-fval = 'X'.
    APPEND bdcdata_wa TO bdcdata_tab.
    CLEAR bdcdata_wa.
    bdcdata_wa-fnam = 'RKAUF-TEST'.
    bdcdata_wa-fval = space.
    APPEND bdcdata_wa TO bdcdata_tab.
    CLEAR bdcdata_wa.
    bdcdata_wa-fnam = 'BDC_OKCODE'.
    bdcdata_wa-fval = '=RUN'.
    APPEND bdcdata_wa TO bdcdata_tab.
    CLEAR bdcdata_wa.
    bdcdata_wa-program  = 'SAPLKABA'.
    bdcdata_wa-dynpro   = '0210'.
    bdcdata_wa-dynbegin = 'X'.
    APPEND bdcdata_wa TO bdcdata_tab.
    CLEAR bdcdata_wa.
    bdcdata_wa-fnam = 'KABA01-JNAME'.
    bdcdata_wa-fval = 'CJB1_EXEC'.
    APPEND bdcdata_wa TO bdcdata_tab.
    CLEAR bdcdata_wa.
    bdcdata_wa-fnam = 'BDC_SUBSCR'.
    bdcdata_wa-fval = 'SAPLKABA'.
    APPEND bdcdata_wa TO bdcdata_tab.
    Extract the date format from the user settings
    PERFORM f_get_dateformat CHANGING g_datfm.
    Changing the current date format to User Profile Date Settings
    PERFORM f_format_date USING   g_datfm
                                  sy-datum+4(2)
                                  sy-datum+6(2)
                                  sy-datum+0(4)
                         CHANGING g_sydatum.
    CLEAR bdcdata_wa.
    bdcdata_wa-fnam = 'KABA01-STDAY'.
    bdcdata_wa-fval = g_sydatum.
    APPEND bdcdata_wa TO bdcdata_tab.
    lv_time = sy-uzeit  + 30.
    CLEAR bdcdata_wa.
    bdcdata_wa-fnam = 'KABA01-STTME'.
    bdcdata_wa-fval = lv_time.
    APPEND bdcdata_wa TO bdcdata_tab.
    CLEAR bdcdata_wa.
    bdcdata_wa-fnam = 'KABA01-PRIKZ'.
    bdcdata_wa-fval = space.
    APPEND bdcdata_wa TO bdcdata_tab.
    CLEAR bdcdata_wa.
    bdcdata_wa-fnam = 'BDC_OKCODE'.
    bdcdata_wa-fval = '=TAKE'.
    APPEND bdcdata_wa TO bdcdata_tab.
    Calling Transaction 'CJB1' for creating settlement rule
    CALL TRANSACTION 'CJB1'  USING bdcdata_tab MODE lv_mode .
    IF sy-subrc = 0.
    ENDIF.
    *&      Form  F_GET_DATEFORMAT
          This subroutine returns the date format in the user setttigs
         <--P_G_DATFM  Date Format
    FORM f_get_dateformat CHANGING p_g_datfm.                   "#EC *
      SELECT SINGLE datfm FROM usr01 INTO p_g_datfm
      WHERE bname = sy-uname.
    ENDFORM.                    " F_GET_DATEFORMAT
    *&      Form  F_FORMAT_DATE
          This subroutine returns the date as per the user settings
         -->P_G_DATFM  Date Format
         -->P_G_MM  Month
         -->P_G_DD  Day
         -->P_G_YYYY  Year
         <--P_G_DATE  Date
    FORM f_format_date USING    p_g_datfm
                                p_g_mm
                                p_g_dd
                                p_g_yyyy
                       CHANGING p_g_date.                       "#EC *
      CONSTANTS: c_dot VALUE '.',
                 c_slash VALUE '/',
                 c_dash VALUE '-',
                 c_1 VALUE '1',
                 c_2 VALUE '2',
                 c_3 VALUE '3',
                 c_4 VALUE '4',
                 c_5 VALUE '5',
                 c_6 VALUE '6'.
      DATA: l_day(2),
            l_month(2).
      l_day = p_g_dd.
      l_month = p_g_mm.
      CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
        EXPORTING
          input  = l_month
        IMPORTING
          output = l_month.
      CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
        EXPORTING
          input  = l_day
        IMPORTING
          output = l_day.
      CASE p_g_datfm.
        WHEN c_1.
          CONCATENATE l_day l_month p_g_yyyy INTO p_g_date
              SEPARATED BY c_dot.
        WHEN c_2.
          CONCATENATE l_month l_day p_g_yyyy INTO p_g_date
           SEPARATED BY c_slash.
        WHEN c_3.
          CONCATENATE l_month l_day p_g_yyyy INTO p_g_date
              SEPARATED BY c_dash.
        WHEN c_4.
          CONCATENATE p_g_yyyy l_month l_day INTO p_g_date
              SEPARATED BY c_dot.
        WHEN c_5.
          CONCATENATE p_g_yyyy l_month l_day INTO p_g_date
              SEPARATED BY c_slash.
        WHEN c_6.
          CONCATENATE p_g_yyyy l_month l_day INTO p_g_date
              SEPARATED BY c_dash.
      ENDCASE.
    ENDFORM.                    " F_FORMAT_DATE
    thanks
    bobby

  • I want to know about ATP check requirement .generally we assigned yes or no while creating sales order

    I want to know about ATP check requirement .generally we assigned yes or no while creating sales order what it means when we give Yes or No. how pegging flows
    Regards
    virender

    Virender,
    Can you be a bit more specific about ".....generally we assigned yes or no while creating sales order....."   Exactly what field(s) did you 'assign'?  Screenshots would be helpful.
    With respect to pegging; in general, ATP has very little to do with pegging.  Pegging is more of a planning concept, and not an 'availability checking' concept.  There are a few exceptions in APO, but they are not commonly implemented.
    Can you elaborate about exactly what you want to know with respect to 'pegging' and ATP?
    Best Regards,
    DB49

  • How/ where to  check output type while saving sales order for confirmation

    Hi All,
    Could you anyone pls let me know How/ where to  check output type while saving sales order for confirmation.
    Present scenario : when the Sales Order is created the Order confirmation is sent irrespective of credit block of the sales order.
    Requirement : Order confirmation “ZA00” sent to the partner only for those Sales orders which does not have credit block and ZCLE sent to the partner if the order has credit block.
    Now i want to know where exactly to check the output types "ZA00" and 'ZCLE' based on the credit block to send the confirmation to partener.
    Quick help highly appreciated......
    Preetham

    Hi Santosh,
    Thanks for the info. But here in this case I have to send the confiramation based on credit limit check. If credit limit check exceeds "ZCLE' should go as confirmation else 'ZA00' should go as confirmation.
    Where can we check the credit limit whether it exceeded or not. My doubt is whether it is config issue or do we need to write code user exit or routine to send the specific output type for confirmation.
    Thanks & Regards,
    Preetham

  • Report for Sold to Party code against Sales order number

    Hi,
            Is there any standard report to take out the Sold to Party code against Sales order number as i have the sales order number.
    I don't want to use Tables ,so pls tell standard report if any.

    Dear   Monty garg.
    You can use u201CVA05Nu201D to find the sales orders which have been created against for the particular customer/sold to party.
    Please let me know if any further clarifications pertinent to this.
    Thanks&Regards
    Raghu.k

Maybe you are looking for