Sold-To Party determination by the Reporter

Hi,
We are the VAR partner and using Solution Manager for incident management.
Now with the Ibase, I can assign Sold to party easily. (as default)
But in our configuration, it's not mandatory to enter Ibase or anything.
So I need to determine Sold-to Party from only Reporter information. Is there any way to do it?
Regards
Tutku

Hi,
I've discussed this issue from a guy from SAP, now the sold-to-party is assigned correctly. Solution is below.
Regards
Tutku
1.) Create Access Sequence
SPRO
Create a new access sequence and define the parameter as mentioned below
2.) Assign Access Sequence
Select your determination procedure which is assigned to your used transaction type
Mark Function ‘Sold-To Party (CRM) in node ‘Partner Functions in Procedure’
Define your newly created access sequence

Similar Messages

  • Sold-to party determination from ship-to

    Hi,
    I have sucha case:
    I am enering SO using va01.
    I select sales area on the first screen and then on the second screen (SO screen) I put ship-to party.
    System pops up selection screen with three possible SOLD-TOs to be selected.
    How the sold-to determination is working? the customer master for selected ship-to/sales area combination contans only one SP.

    Hi,
    If your ship to party is linked with one or more than one ship to part in customer master, then it will show all the attached sold to party's at the time of order creation.
    Kapil

  • Shipment Output Determination: Sold To Party needed in the access seqeunce

    Hi Gurus,
    I need to create a new access sequence for Shipment Output determination including the Shipment Type, Shipping Point and Sold-To party.
    Can someone provide the steps involved to add the Sold-To party in the access sequence and the enhancement which I can use to populate the Sold-To party field.
    Thanks in advance for the help.
    Gajendra

    Murali,
    Thanks for your reponse. The way you suggested I have tried creating a new access table but the issue is Sold-To field is not available as a selection in the field catalog when you are in create access table screen (spro->Logistics Execution->Transportation->Basic Transportation Functions->Output Control-> Maintain Output Determination for Shipments->Maintain Condtion Tables->Maintain Output Condition Table for Shipments).
    When I go to the field catalog maintenance (spro->Logistics Execution->Transportation->Basic Transportation Functions->Output Control-> Maintain Output Determination for Shipments->Maintain Condtion Tables->Field catalog: Messages for transportation) the field KUNAG - Sold To Party does exist in the field catalog. However this doesn't show up on the access table maintenance screen as an available field.
    Could you please explain how to make this field available for access table maintenance?
    Regards,
    Gajendra

  • Sold-To Party determination using Reported-By partner function in SolMan 4

    Hi,
    I'm trying to populate the Sold-To party field via Reported-By partner function in Solution Manager 4.0.
    That means in the Organizational model the Sold-To-Party is a Organization Business Partner, and the person who create the Support Message or Service Order is a person (Person BP) who works for the Sold to Party Org. Unit, then I request that when a Support Message is reported by a person that belong to The Org, Model, the system fulfill Sold-To-Party automatically.
    Example:
    Org. Unit: 10000 (BP Organzation) <----
    Sold to Party
    Employee: 10001 (BP: Person) <----
    Reported by
    Any hints how I could acheive this?
    Will award points.

    Hi,
    Just to clrify few things.... In terms of Solution Manager, the sold to party gets populated from the BP that is assigned to the Install Base Component. It is not required to have the BP maintained as a Sold-To to populate the Sold-To party field.
    I know that is confusing. But that is how it works. So in very general terms I'm looking a way to bypass the BP assignment to Install base and get the BP number of the Org unit that the user(employee) is been assigned to populate the Sold-To party field. Pls note that the Org Units are not maintained as Sold To parties.
    Thanks

  • How to determine the Support Team from the Reported by?

    Hello Everyone,
    I am working with Solution Manager 4.0 and I want to use Automatic Partner Determination in Service Desk. My employer wants the Support Team (SLFN0003) to be determined by the Reported by (SLFN0002).
    There are already parts of the Automatic Partner Determination that work, like determining the Sold-to Party from the IBase component. Because of that I believe the customizing leading to a correct Partner Determination Procedure is working. But somehow I can’t seem to get the determination of the Support Team from the Reported by to work. Hopefully someone can help me on this matter.
    Thanks in advance!
    Best regards,
    Michael Sital

    method if_ex_order_save~check_before_save.
      data gs_status type zsmgl_status.
      data lt_tguid  type crmt_object_guid_tab.
      data lt_orderadm_h type crmt_orderadm_h_wrkt.
      data lt_status type crmt_status_wrkt.
      data ls_status like line of lt_status.
      data lt_partner type crmt_partner_external_wrkt.
      data ls_partner like line of lt_partner.
      data lt_partner_h  type table of crmt_partner_com.
      data lt_partner_h1 type crmt_partner_comt.
      data ls_partner_h like line of lt_partner_h.
      data ls_field_names type crmt_input_field_names.
      data lt_field_names type crmt_input_field_names_tab.
      data lv_logical_key(42) type c.
      data lt_input_fields  type crmt_input_field_tab.
      data ls_input_fields like line of  lt_input_fields  .
      data gt_partner_h type crmt_partner_external_wrkt.
      data gs_partner_h like line of gt_partner_h.
      data lt_cjest type table of crm_jest.
      data ls_cjest type crm_jest.
      clear lt_status.
      clear lt_partner.
      clear lt_orderadm_h.
      insert iv_guid  into table lt_tguid.
      call function 'CRM_ORDER_READ'
        exporting
          it_header_guid       = lt_tguid
        importing
          et_status            = lt_status
          et_orderadm_h        = lt_orderadm_h
          et_partner           = lt_partner
        exceptions
          document_not_found   = 1
          error_occurred       = 2
          document_locked      = 3
          no_change_authority  = 4
          no_display_authority = 5
          no_change_allowed    = 6
          others               = 7.
      if sy-subrc = 0.
    Get in only  if status is changed to Inprogress.
        clear ls_cjest.
        select single * from crm_jest into ls_cjest where objnr = iv_guid and inact = ' '.
        if ls_cjest-stat = 'E0010'.
          read table lt_status into ls_status with key status = 'E0002'.
          if sy-subrc = 0.
    Read Status from Intermidiate Table.
            select single * from zsmgl_status into gs_status
                                     where guid = iv_guid
                                     and   stat = 'E0002'
                                     and   inact = ''.
            if sy-subrc = 0.
    make copy to _h table
              loop at lt_partner into ls_partner.
                move-corresponding ls_partner to ls_partner_h.
                append ls_partner_h to lt_partner_h.
                clear ls_partner_h.
              endloop.
              loop at lt_partner_h into ls_partner_h where partner_fct = 'SLFN0003' or partner_fct = 'SLFN0004'.
                case ls_partner_h-partner_fct.
                  when 'SLFN0003'.
                    ls_partner_h-ref_partner_no = gs_status-partner_number.
                    ls_partner_h-partner_no = gs_status-partner_number.
                    modify lt_partner_h from ls_partner_h transporting  ref_partner_no partner_no.
                    clear ls_partner_h.
                  when 'SLFN0004'.
                    if gs_status-bu_partner is not initial.
                      ls_partner_h-ref_partner_no = gs_status-bu_partner.
                      ls_partner_h-partner_no = gs_status-bu_partner.
                    else.
                      ls_partner_h-partner_no = ' '.
                      ls_partner_h-ref_partner_no = ' '.
                    endif.
                    modify lt_partner_h from ls_partner_h transporting  ref_partner_no partner_no.
                    clear ls_partner_h.
                endcase.
              endloop.
            endif.
            lt_partner_h1[] = lt_partner_h[].
            loop at lt_partner_h1 into ls_partner_h where ref_partner_fct = 'SLFN0003' or ref_partner_fct = 'SLFN0004' .
              clear ls_field_names.
              ls_field_names-fieldname = 'PARTNER_FCT'.
              insert ls_field_names into table lt_field_names.
              ls_field_names-fieldname = 'PARTNER_NO'.
              insert ls_field_names into table lt_field_names.
              ls_field_names-fieldname = 'DISPLAY_TYPE'.
              insert ls_field_names into table lt_field_names.
              ls_field_names-fieldname = 'NO_TYPE'.
              insert ls_field_names into table lt_field_names.
              ls_field_names-fieldname = 'KIND_OF_ENTRY'.
              insert ls_field_names into table lt_field_names.
              ls_input_fields-ref_guid    = iv_guid.
              ls_input_fields-ref_kind    = 'A'.
              ls_input_fields-objectname  = 'PARTNER'.
              ls_input_fields-field_names = lt_field_names.
              lv_logical_key = '0000'.
              lv_logical_key+4 = ls_partner_h-partner_fct.
              lv_logical_key+12 = ls_partner_h-partner_no.
              lv_logical_key+28 = ls_partner_h-ref_display_type.
              lv_logical_key+30 = ls_partner_h-ref_no_type.
              ls_input_fields-logical_key = lv_logical_key.
              insert ls_input_fields into table lt_input_fields.
            endloop.
            call function 'CRM_ORDER_MAINTAIN'
              exporting
                it_partner        = lt_partner_h1
              changing
                ct_input_fields   = lt_input_fields
              exceptions
                error_occurred    = 1
                document_locked   = 2
                no_change_allowed = 3
                no_authority      = 4
                others            = 5.
          endif.
        endif.
      endif.
    endmethod

  • Failing to determine sales area in sales order for many BP's(Sold-To Party)

    Hi Experts
    In SAP CRM version 4.0, when I enter the Sold-to party (BP) in the sales order transaction, for some it determines the sale area automatically and for most of the BP's it is not determining.
    The Determination rule is organizational Model.
    The determination rule used is 91000141 (ZORGMAN_RA = Organization based on BP and trans.)
    Under Container tab in this determination rule, using simulate Rule resolution button, for some BP, it find the agent with green light when I place a BP in the Container element value field but for many BP's, it shows as No agent found.
    Org. data profile used is ZORGPROF_RA (Mandatory are sales Org, Dist. Ch, Sales Off.) and has set the above determination rule.
    In the Organizational model, the General attributes are country, currency, dist. Ch & division.
    So, Why Org determination is working for some BP and not for all.. I've checked each field in BP transaction comparing those BP where the org detrmination is automatic with those where it is not determining...but not able to find a clue also to trace it.
    we are introducting a sales order block in BP (under sales tab) for some specific Sold-To party and in webshop when these Sold-to party are tried to place an order then an error message will show that this "Sold-To party has a  sales area block".
    To achieve this, first the org determination should work automatically for all BP's otherwise for those BP which cannot detrmine the sales area in the sales order transaction will allow to place order (which should not be in our case)
    Can any one throw some light in this case..please do ask if you need more clarification in my question.
    Thank & Regards
    Pravin Babu

    Hello Maggie
    Thanks for your reply.
    I found the cause of the failure, in not determining  the sales area  automatically in sales transaction for some BP's.
    It is due to the BP settings, under sales area view, under organization tab, by pressing 'Choose sale area" button, I can see the sales Organization has uncheck for 'sales'  but it is check for all others - shipping, billing, partner, status, Organization.
    It is due to -> no data mainatined for the BP under Sales tab, after mainatianing it, I can see the check by pressing the 'choose sale area under organization tab.
    Now, in Order transaction, the sale area is determined automatically when I enter the BP.
    So this was the reason that some BP's was able to determine the sales area automatically but not for others in the sales transaction.
    Regards
    Pravin
    Edited by: Pravin Babu on Jul 14, 2010 3:49 PM

  • Change the sold to party

    Hi expert,
                     Can i change " Sold to party code"  after the creation of the sales order.
    Regard
    Shashi

    Hi
    After the sales order say order no 10000 saved for sold to party as X you cannot change the sold to party in VA02 transaction as Y for order no 10000
    That means if the order is created and saved then you cannot change the Sold to party for that order
    But while processing it self before saving in VA01 transaction itself it is possible to change the SP
    after the creation of the sales order.
    Not possible
    You cannot touch SP in VA02 transaction irrespective of subsequent document is there or not and the
    img settings said under partner determination for sales document types  say TA for standard order there also i dont think you can change the standard settings as the SP is mandatory and not modifiable
    You cannot  remove the tick in non modifiable for  SP for TA the standard sales doc type partner determination and make it
    modifiable
    Regards
    Raja
    Edited by: ramanathan raja on Nov 1, 2009 12:33 PM

  • Hi , i want to find the names of ship to party , sold to party based likp

    Hi ,
    Could you plz help me .
    how to find the names of the ship to party , sold to party depending on the
    sold to party (likp-kunnr) and ship to party(likp-kuang).
    Thanks
    Suresh.

    Sold-to-party
    Take ur likp-kunnr ,do compare compare with kna1-kunnr,take adrnr number from kna1,use adrc table..
    so adrc table field is name1
    Ship-to-party :
    take LIKP-kunag,do compare with kna1-kunnr,get adrnr field from kna1,do compare with ADRC Table with adrnr,
    so you can use ADRC-NAME1 field
    Thanks
    Seshu

  • Reversing the billing an change the sold to party...

    Hello Experts...
    We have a complete Sales Order submitted which has a mile stone based billing. The sold to party (A) has paid 4 installments out of 10 installments. He now wants to take back his 4 payments and change the Sold to Party to B. The new Sold to party (B) will pay the 4 installments and continue with the payment of balance installements. There is no change in the materials sold and pricing. The customer does not want to cancel the sales order and create a new sales order.
    This is a high priority issue. Kindly advice asap.
    Thanks and Regards

    Dear Patnaik,
    I think you can do like this, try with this......
    You do the reverse or cacel for the 4 instalments which sold to party A has paid.
    You need to reverse or cancel the all susequent documents of the sales order
    Make sales order status as open
    Now you can change sold to party to B in the sales order in VA02 transaction
    I hope it will help you
    Regards,
    Murali.
    Edited by: Murali Mohan.Tallapaneni on May 16, 2008 2:43 PM

  • 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

  • Sold to Party rebate

    Hi,
    We have a scenario where the Sold to and the payer differs. In this case we need to give the Rebate to the Sold to party and not the Payer.
    Standard SAP looks at Payer for the rebate. Could you help me with a work around?
    Is there an user exit, some modifcation which can be done wwhcih will link the rebate amount to the Sold to party, we will then manage this through a report.
    Any ideas, Tips are welcome.
    thanks in advance.
    Supreeth

    Remember, I need not see you personally but can assess individuals by the words used in their query. You used 'user exits' which usually advanced users are allowed to work on real life.
    OK lets forget the past.
    *I worked on your requirement and it worked for me. I am giving detail steps. It should work for you too. I am giving steps for creating rebate agreement based on customer / material. *
    - Go to IMG - SD- Billing - Rebate processing - condition technique for rebate processing
    - click maintain access sequences for example select access sequence B002.
    - click accesses
    - select access which has description 'customer / material'
    click fields.
    You can see field with label "payer".
    The reason why the system calculates rebates for payer is because of this field in access sequence.
    Now lets work on your requirement
    - Create a new condition type for e.g ZKAM (copy it from existing condition type say B002)
    - Create a new access sequence for e.g ZKAM (copy it from existing access sequence say B002). select copy so that it would copy all records.
    - select accesses and after that select access which has description customer / material
    - click fields
    - select the field 'KUNNR' with label 'payer'.
    - select the field catalog button at bottom and you would be in display view "fields" overview button
    - locate the field 'KUNNR' which has label name 'sold to party'
    - double click this field and you would be back in change view "fields" screen but now "sold to party is selected.
    - save it
    - now go back to condition type ZKAM and add your newly created access sequence ZKAM to it. 'Access sequence' field is at the top & save it.
    - Now select maintain pricing procedures. select your pricing procedure lets say standard 'RVAA01'.
    - select step which has condition type B002 (In SAP standard step number is 902).
    - copy it by using copy function. rename it to ZKAM and for example give step number as 906.
    - save it.
    - Define new agreement type ZKAM by copying existing agreement type 0002
    - In Assign Condition Types/Tables To Condition Type Groups, select condition type group 0002, using copying function copy it and change 'cntr' to 2 and 'cnty' to ZKAM and save it.
    - In Assign condition type groups to rebate agreement types, see whether your agreement type is assigned to condition type group '0002'.
    In Easy Access
    - In the customer master record, indicate that sold to party is relevant for rebates.
    - In the customer master record of sold to party, select sales area button, select partner functions tab, against payer field, indicate payer account number. This is as per your requirement.
    - Activate your sales orgn & billing types relevant for rebates.
    - Create rebate agreement type by using agreement type ZKAM. In conditions button select condition type as ZKAM and complete the data required.
    - create sales order for sold to party, deliver it, complete billing.
    - go back to your rebate agreement type and see whether rebate has been processed for sold to party.

  • Sold to party and Ship to part y fields in VA01 disabled.

    01.10.2008
    Hi friends,
    In one of the client when i use transaction code VA01 for a particular document type i find the Sold to Party and Ship to party are greyed off. I am not able to enter any data into it.
    In the sand box the same document type works fine. How will i trace which transaction variant is linked which is disabling this fields. Please advise.
    Regards,
    udaynath.

    Hi Krishnan
    It is not the problem with the Document type.
    I think,you have not assigned the "Partner Type" to the "Partner Function".
    Just go to your Partner determination Procedure in IMG, go to  "Partner Function" folder in the dialog box.
    Select your Sold-to-party and assign the "Partner Type" KU (Customer) to it.
    Similarly assignthe Partner Type KU to your Ship-to-party and save it.
    Now, create an order and there will be no problem.

  • Ship-to party is not assigned to a sold-to party

    Dear Experts
    I am creating Sales ORder VA01
    my customer is 42
    so i have enterd 42 in Ship to party and Sold to party
    but getting error is
    Ship-to party 42 is not assigned to a sold-to party
    could u please guide me
    Regards
    Amol

    Hi,
    Goto the T.Code "XD03".
    Enter the customer number as "42".
    Maintain the company code and sales area.Enter.
    Goto the sales area tab.Click on "Partner functions" tab.
    Check whether the ship-to-party is 42 or not.I think it is not 42,so that only,you are getting this error message.
    In sales order,enter the sold-to-party as "42".The ship-to-party will be auto determined from the customer master.After this you can change it to 42 if the following setting is maintained for your partner determination procedure.
    Goto the path:
    SPRO>Sales and Distribution>Basic Functions>Partner Determination>Set Up Partner Determination-->Set Up Partner Determination for Sales Document Header.
    Click on "Partner Determination Procedure Assignment".Identify the procedure assigned to your document type.
    Click on "Partner Determination Procedures".Select that procedure.
    Double click on "Partner Functions in Procedure".
    Ensure that for "SH" partner function,the field "Not modifiable" is not ticked.
    Save.
    Regards,
    Krishna.

  • Contract determination form the service order

    Hello everyone,
    I am working on CRM 5.0 service order and service contracts.
    I created an IBase and I assigned it to the products in the service contract on the item level (in object list) and the same I did on the item level in the service order (in object). But When I enter the product in the service order it gives me an error that a "new contract for the item 10 should be run" with execution choice to run it.
    After I ran the contract I found the product price is not picked from the service contract and picked form the pricing of the service order and a message in the tab page contract that “no contract has been determined”
    The IBase created contains only the product ID and quantity field and linked with a business partner – sold to party
    Is it possible to make the contract determination depends only on the organizational structure and sold to party and remove the Ibase form this determination
    Thanks in advance
    Jacopo François

    Hi Pratik Patel
    I want to know why this problem happen the error message "new contract for the item 10 should be run" shows that there is a contract have been determined but the product price is not picked from the service contract and picked form the pricing of the service order and a message in the tab page contract that “no contract has been determined”
    Would you please help me to implement this badi?
    Thanks
    Jacopo François

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

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

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

Maybe you are looking for