Adding Forwarding Agent to Partner details in a Sales Order.

Hi Experts,
  Below is the detailed scenario :
  We have inbound orders been created by Idocs Orders04 using the Idoc_Input_orders function module.
the requirement is that if the partner forwarding agent is not been populated in Idoc then we need to add the same in the SO Partner details from Z table based on the sold to party in the idoc.
Can anyone please help how I can proceed with the requirement. I have created a Z table and maintain the entries. I am not understanding where i should be doing the Coding for the same.
Thanks and Regards,
Nimisha.

Hello,
inside the VA01-transaction there are the userexits EXIT_SAPLV09A_001 to  EXIT_SAPLV09A_004 influencing the partner determination. Think most probably you could use the EXIT_SAPLV09A_004
(Enhancement is V09A0004).
You could switch on that one and look, which partners are in the order at that point of time.
Regards
Wolfgang

Similar Messages

  • Not able to get the Quantity and partner details in the sales order created

    Hi Experts,
    I am creating a followup order using the FM "BAPI_BUSPROCESSND_CREATEMULTI" . The parameters iam passing are process type, quantity , sold to party (partner) and product ID. I am able to create a sales order but the Quantity and sold to party (partner) are not getting updated in the the sales order when i check in the transaction CRMD_ORDER. When i check in the crm_orderadm_h table and give the Headerguid , i am able to see the process type and when i check in the crm_order_index table, if i give the header i am not getting the partner no and there are two lines created for one header guid. I am providing the code which i have written. Can anyone please help me in this issue??
    *& Report  ZCREATEORDER_LUCKY_TEST
    REPORT  ZCREATEORDER_LUCKY_TEST.
    DATA : LV_HEADER_GUID  TYPE  GUID_32,
    WA_HEADER             TYPE                   BAPIBUS20001_HEADER_INS,
    ITAB_HEADER           TYPE STANDARD TABLE OF BAPIBUS20001_HEADER_INS,
    ITAB_CREATED_PROCESS  TYPE STANDARD TABLE OF BAPIBUS20001_HEADER_INS,
    ITAB_OBJECTS_TO_SAVE  TYPE STANDARD TABLE OF BAPIBUS20001_GUID_DIS,
    ITAB_PARTNER          TYPE STANDARD TABLE OF BAPIBUS20001_PARTNER_INS,
    LT_PRODUCT_I          TYPE STANDARD TABLE OF BAPIBUS20001_ITEM,
    WA_PRODUCT_I          TYPE                   BAPIBUS20001_ITEM,
    LT_SCHEDLIN_I         TYPE STANDARD TABLE OF BAPIBUS20001_SCHEDLIN,
    WA_SCHEDLIN_I         TYPE                   BAPIBUS20001_SCHEDLIN,
    ITAB_INPUT_FIELDS     TYPE TABLE OF          bapibus20001_input_fields,
    ls_inputfields        TYPE                   bapibus20001_input_fields,
    WA_PARTNER            TYPE                   BAPIBUS20001_PARTNER_INS,
    ITAB_RETURN           TYPE                   STANDARD TABLE OF BAPIRET2,
    WA_OBJECTS_TO_SAVE    LIKE                   LINE OF ITAB_OBJECTS_TO_SAVE,
    ITAB_PRICING          TYPE STANDARD TABLE OF BAPIBUS20001_PRICING,
    WA_PRICING            TYPE                   BAPIBUS20001_PRICING,
    *To store the Objects to be saved.
    WA_CREATED_PROCESS    LIKE LINE OF ITAB_CREATED_PROCESS,
    ITAB_SAVED_OBJECTS    TYPE STANDARD TABLE OF BAPIBUS20001_OBJECT_ID,
    WA_SAVED_OBJECTS      LIKE LINE OF ITAB_SAVED_OBJECTS,
    GC_X type c.
    gc_x = 'x'.
    CALL FUNCTION 'GUID_CREATE'
      IMPORTING
        ev_guid_32 = lv_header_guid.
      CLEAR : WA_HEADER.
    * Passing the respective values from the Header table to internal table.
    WA_HEADER-GUID          =  LV_HEADER_GUID.
    WA_HEADER-PROCESS_TYPE  =  'ZTA'.
    APPEND WA_HEADER TO ITAB_HEADER.
    *Appending the values to the ITAB_HEADER.
    *appending orderadm_i to input fields
    * ls_inputfields-ref_guid =  LV_HEADER_GUID.
    * ls_inputfields-REF_KIND = 'A'.
    ls_inputfields-objectname = 'ORDERADM_I'.
    ls_inputfields-ref_handle = '0000000001'.
    * ls_inputfields-logical_key = ' '.
    ls_inputfields-fieldname = 'ORDERED_PROD'.
    APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
      CLEAR ls_inputfields.
    * ls_inputfields-ref_guid =  LV_HEADER_GUID.
    * ls_inputfields-REF_KIND = 'A'.
    ls_inputfields-objectname = 'ORDERADM_I'.
    * ls_inputfields-logical_key = ' '.
    ls_inputfields-fieldname = 'MODE'.
    ls_inputfields-ref_handle = '0000000001'.
    APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
      CLEAR ls_inputfields.
    ****** CHANGES MADE
    * ls_inputfields-ref_guid =  LV_HEADER_GUID.
    * ls_inputfields-REF_KIND = 'B'.
    ls_inputfields-objectname = 'SCHEDLIN'.
    ls_inputfields-ref_handle = '0000000001'.
    ls_inputfields-fieldname = 'LOGICAL_KEY'.
    APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
    CLEAR ls_inputfields.
    * ls_inputfields-ref_guid =  LV_HEADER_GUID.
    * ls_inputfields-REF_KIND = 'B'.
    ls_inputfields-objectname = 'SCHEDLIN'.
    ls_inputfields-ref_handle = '0000000001'.
    * ls_inputfields-logical_key = ' '.
    ls_inputfields-fieldname = 'QUANTITY'.
    APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
    CLEAR ls_inputfields.
    * ls_inputfields-ref_guid =  LV_HEADER_GUID.
    ls_inputfields-REF_KIND = 'B'.
    ls_inputfields-objectname = 'SCHEDLIN_I'.
    ls_inputfields-ref_handle = '0000000001'.
    * ls_inputfields-logical_key = ' '.
    * ls_inputfields-fieldname = 'MODE'.
    APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
    CLEAR ls_inputfields.
    ****** CHANGES MADE
    WA_PARTNER-REF_GUID =  LV_HEADER_GUID.
    WA_PARTNER-REF_KIND = 'A'.
    WA_PARTNER-REF_PARTNER_HANDLE = '0001'.
    WA_PARTNER-PARTNER_FCT = '00000001'.
    WA_PARTNER-PARTNER_NO =  '10017'.
    WA_PARTNER-KIND_OF_ENTRY =  'C'.
    WA_PARTNER-NO_TYPE = 'BP'.
    WA_PARTNER-DISPLAY_TYPE  =  'BP'.
    APPEND WA_PARTNER TO ITAB_PARTNER.
    *"ADDING VALUES TO CT_ORDERADM_I
      wa_product_i-header        = lv_header_guid.
      wa_product_i-handle        = '0000000001'.
      wa_product_i-ordered_prod  = '12000014'.
      wa_product_i-mode          = 'A'.
      APPEND wa_product_i TO lt_product_i.
    *"ADDING VALUES TO IT_SCHEDLIN_I
      wa_schedlin_i-GUID    =  LV_HEADER_GUID.
      wa_schedlin_i-quantity   = '30'.
      wa_schedlin_i-handle = '0000000001'.
      wa_schedlin_i-mode  =  'A'.
      APPEND wa_schedlin_i TO lt_schedlin_i.
    *  wa_schedlin_i-schedlines = lt_schedlines.
    *"ADDING VALUES TO WA_PRICING
    wa_PRICING-REF_GUID    =  LV_HEADER_GUID.
      wa_PRICING-REF_KIND   = 'A'.
    *  wa_schedlin_i-handle = '0000000001'.
      APPEND wa_PRICING TO ITAB_PRICING.
    *  wa_PRICING-REF_GUID    =  LV_HEADER_GUID.
      wa_PRICING-REF_KIND   = 'B'.
      wa_schedlin_i-handle = '0000000001'.
      APPEND wa_PRICING TO ITAB_PRICING.
    ls_inputfields-ref_guid =  LV_HEADER_GUID.
    ls_inputfields-REF_KIND = 'A'.
    ls_inputfields-objectname = 'PARTNER'.
    ls_inputfields-logical_key = '0001'.
    ls_inputfields-fieldname = 'REF_PARTNER_HANDLE'.
    APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
      CLEAR ls_inputfields.
    ls_inputfields-ref_guid =  LV_HEADER_GUID.
    ls_inputfields-REF_KIND = 'A'.
    ls_inputfields-objectname = 'PARTNER'.
    ls_inputfields-logical_key = '0001'.
    ls_inputfields-fieldname = 'PARTNER_FCT'.
    APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
      CLEAR ls_inputfields.
    ls_inputfields-ref_guid =  LV_HEADER_GUID.
    ls_inputfields-REF_KIND = 'A'.
    ls_inputfields-objectname = 'PARTNER'.
    ls_inputfields-logical_key = '0001'.
    ls_inputfields-fieldname = 'PARTNER_NO'.
    APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
      CLEAR ls_inputfields.
      ls_inputfields-ref_guid =  LV_HEADER_GUID.
    ls_inputfields-REF_KIND = 'A'.
    ls_inputfields-objectname = 'PARTNER'.
    ls_inputfields-logical_key = '0001'.
    ls_inputfields-fieldname = 'NO_TYPE'.
    APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
      CLEAR ls_inputfields.
      ls_inputfields-ref_guid =  LV_HEADER_GUID.
    ls_inputfields-REF_KIND = 'A'.
    ls_inputfields-objectname = 'PARTNER'.
    ls_inputfields-logical_key = '0001'.
    ls_inputfields-fieldname = 'DISPLAY_TYPE'.
    APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
      CLEAR ls_inputfields.
        ls_inputfields-ref_guid =  LV_HEADER_GUID.
    ls_inputfields-REF_KIND = 'A'.
    ls_inputfields-objectname = 'PARTNER'.
    ls_inputfields-logical_key = '0001'.
    ls_inputfields-fieldname = 'KIND_OF_ENTRY'.
    APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
      CLEAR ls_inputfields.
    CALL FUNCTION 'BAPI_BUSPROCESSND_CREATEMULTI'
      TABLES
        HEADER          = ITAB_HEADER
        ITEM            = lt_product_i
        RETURN          = ITAB_RETURN
        PARTNER         = ITAB_PARTNER
        INPUT_FIELDS    = ITAB_INPUT_FIELDS
        CREATED_PROCESS = itab_created_process
        SCHEDULELINE    = lt_schedlin_i
        PRICING         = ITAB_PRICING.
    READ TABLE ITAB_CREATED_PROCESS INTO WA_CREATED_PROCESS WITH KEY GUID = LV_HEADER_GUID BINARY SEARCH.
    WA_OBJECTS_TO_SAVE-GUID = WA_CREATED_PROCESS-GUID.
    * Appending the Guid of the contract to be saved to the internal table
    APPEND WA_OBJECTS_TO_SAVE TO ITAB_OBJECTS_TO_SAVE.
    CALL FUNCTION 'BAPI_BUSPROCESSND_SAVE'
      EXPORTING
        update_task_local = space
        save_frame_log    = GC_X
      TABLES
        objects_to_save   = itab_objects_to_save
        saved_objects     = itab_saved_objects
        return            = itab_return.
    * Calling the Standard BAPI to Commit the transcation.
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
    WRITE: / 'HEADER GUID: ',lv_header_guid.
    Any inputs will be highly appreciated!!
    Thanks a lot in Advance.
    Lakshman.

    solved

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

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

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

  • Partner function change in sales order

    Hi,
    I have partner function ZR (sales employee) defined for customer master. I enter a particular employee no 100 in the customer master. and subsequnetly the partner function ZR gets copied into a contract with value 100.
    now another user is trying to change the value to 200 from 100, but the system is giving a message that partner function ZR not defned for partner procedure.
    If i go to partner determination for  sales order , then i see that there is no partner function ZR assigned for a patner procedure.
    my question is that the above is happening due to lack of master data for emploee id 200 from HR module or is it that we have to maitain partner function ZR for sales order (I have seen that ZR is not maintained for sales order. ).Iam assuming that for contracts aslo, the config needs to be done in parnter determination for sales order.
    regards
    sachin

    Hi Sachin,
    I assume that you have configured the partner functions for Customer master including ZR, also enabled ZR for the partner procedure applicable for the sales document type.
    If this is done, then the partner function ZR should be available for entry in the sales order.
    Now the problem is that
    You shoudl have assigned the partner function ZR to some account group, while creating this partner function, and customer 100 shoudl have belonged to this account group.
    However the customer 200 whom you want to update as the new ZR doesnt belong to this account group.
    You can use only those customers belonging to the account group which is linked to the partner function ZR as sales employees.
    So find out the customers belonging to the account group, which is linked to the partner function ZR. Make sure their masterdata is correct for the sales area which you wnat to use. If all the things satisfy, then you should be able to use them as ZR partner in your sales document.
    This should solve your problem.
    Pls reward if this helps you to solve the problem

  • Read details of a sales order using bapi

    Hi All,
    Can somebody tell me how to read details of a sales order that is under creation using a BAPI? Also I need to change some of the parameters eg, pricing details, using some API.
    Regards,
    - Prasenjit

    Even if the order is under creation, you should know guid of it.
    Where do you plan to call this function module?
    For example, common usage is to call this function module from order_save implementation. There you have parameter IV_GUID which holds guid of sales document.
    Hope this helps.
    Regards,
    Kaushal

  • Partner Function Structure in Sales Order

    Hi All,
    What is the Partner Function Structure in Sales Ordere (Item Level)?
    (In which structure the partner functions are displays in sales order item level?)
    Thanks in advance.

    HI Raja,
    Thanks for your replay.
    I did the same thing what ever u said, but the thing is while doing debugging the values are not showing in that structure. Like header and item data will available in KOMK and KOMP structurs, not in screen field strucuture. I am thinking that there may be some structure for partner functions like KOMP, KOMK.
    Thanks

  • C form Details table for sales order

    Hi Experts,
    What is the tsble for C form details in a sales order.
    Thanks,
    Anu

    Hi,
    The tcode for maintaing C form for sales orders is J1IUN. The table is J_1IFRDTSO.
    You can find J1IUN Under area menu J1ILN - India Localization Menu.
    Regards,
    Vinod

  • Using bsid and bsad I needed get partner name related to sales order

    Hi
    Using bsid and bsad I needed get partner name related to sales order
    I have gone through the tables but its vbeln column is blank
    How can I make relation between bsid and bsad with vbak if vbeln and column is blank in the table bsid and bsad.
    Please guide me.
    Regards
    Sebastian
    Edited by: Sebastian John on Apr 21, 2009 3:35 PM

    BSID-VBELN = VBRK-VBELN.
    Billing document number is there in BSID table.
    Regs.

  • Adding the E-Mail Adress to partner Goods Recipient in Sales order

    Hello.
    We are creating sales orders either with EDI (IDOC ORDERS) or function module BAPI_SALESORDER_CREATEFROMDAT2.
    In both cases the tables for partners doesn't include a field for the E-Mail adress.
    So we send the E-Mail Adress as Name4.
    When creating the sales order we want to send the Goods Recipient a message by Mail using the SAP-Standard routines. Therefore we need the Mail Adress in the corresponding field in the header-partner.
    Does anyone have an idea how the move the Mail Adress from Name to Mail adress?
    During creation of the sales order the adressnumber is not defined.
    Best Regards
    Gerhard

    Hi Srinu,
    Thank u for ur help!
    "Please note in xd02 you can assign many different patterns with same partner type but in VA02 you can only assign one parter type for one line item un like in XD02."
    This was a very nice tip.
    I am sorry to bother u more, and since we are on this topic, can I ask u one more question?
    I have now made the SP Modifiable just to check if we can change it, and what impact does it have on the DOC header. But I still cannot modify it!.
    Note: I saved the configuration, used /nva01 just to be sure the VA01 was not open already(which would have not picked the new configuration). So I let the system save and try new setting.
    See config:
    Then VA01

  • Updation of partner address data in sales order

    Hi,
       I am trying to create a sales order using an Idoc of the message type ORDERS.
       Within this Idoc, the street number for the Sold-to partner is blank.
       However, by the time the Idoc is processed and the order is created, the street address
       for the Sold-to partner gets picked up from the customer master where this field is not
       blank for the partner.
       Is there any way to avoid this so that the sales order reflects the partner address
       details as it is in the IDoc and this street address remains blank.
    Regards,
    Sudeep

    Hi Sudeep,
    You could try the below solution(as i cant think of a straight forward solution) to this.
    Export the value of street in one of the customer exits in IDOC_INPUT_ORDERS, and then implement the implicit enhancement option in the FM "SD_PARTNER_READ", in this enhancement import the value that you earlier exported, if the import succeeds then the call is via "IDOC_INPUT_ORDERS"(hence this enhancement will not affect dialog users/other interfaces), then check if the imported value is blank, if so then clear the value in I_XVBPA.
    Note: If the program doesnt get into SD_PARTNER_READ, the you can try with user exit for VBAP/save_document_prepare.
    Regards,
    Chen

  • Customer Hierarchy Partner determination in a Sales Order using Payer ?

    Dear SD Experts/Gurus
    We use Customer Hierarchies extensively in Sales Orders for Pricing & Rebates and it all works fine.
    The Hierarchy structure consists at the bottom level of a SoldTo linked to a Hierarchy Customer and many SoldTos can have the same Hierarchy Customer.
    We set price conditions at the Hierarchy Customer and that all works fine.
    We would like to change our Customer Hierarchy to link the Hierarchy Customer to the Payer rather than to all the individual SoldTos.
    This is because we have many SoldTos linked to 1 Payer and this will allow us to have simpler Customer Hierarchy structures making it easier to setup and maintain.
    I have changed the SAP configuration to do this and I can certainly maintain the Customer Hierarchy without any problem using transaction VDH1N.
    But when I create a Sales Order, the Hierarchy Customer does not get pulled through to the Sales Order Header Partners based on the Order Payer and hence no Hierarchy Customer price conditions are pulled through.
    Is what I'm trying to do possible in SAP ?
    If so please advise how this can be achieved.
    Thanks David
    Edited by: David Steele on Apr 15, 2008 1:57 PM

    Hello,
    I have a similar requirement, although we are building the hierarchies directly in CRM (as we are with BP's in general), and I am using hierarchy category 01 - PRICING.
    What I have found is that a sold-to BP must:
    1. be assigned to a hierarchy node
    2. appear TWICE (!!!) in the document part.det.procedure, once in partner function 000001 (sold to) and again in partner function 00000121 (Authorized partner: sold to).
    When the sold to customer exists in both functions within the document, I am able to determine the hierarchy node properly.
    Now, my question is, can anyone guess why the main partner (sold to) must appear twice??? or, is this an error in my customizing?
    Thank you in advance for your help, and I do hope my observation can help others find a solution.
    Regards,
    Allon
    PS in terms of customizing, I used the following:
    partner function 00000001 - sold to
    partner function 00000121 - Auth. Partner: Sold-to Party
    access for Auth. Partner: 0017 - current partner: sold to *this copies the sold to partner into this partner*
    partner function 00000076 - Hierarchy Node Partner
    access for hier.node partner: CRM_PARTNER_G Pricing hierarchy
    The last bit presupposes that the hierarchy is set up using hierarchy category '01 - pricing'.
    Message was edited by:
            Allon Riczker - Added configuration steps

  • Multiple Partner Function in a sales Order

    Hi
    I have created a partner function  ZR Referred By ( Type Customer) but not able to enter multiple ZR in a sales Order
    Error .VPD012. Partner Function can occur only 1  in ..
    The requirement is to attach the referred customers for reporting purpose and there can be more than one customer referring this new Customer / Order.

    Hi
    Thanks for the input but  the solutions suggested by you all does not work.
    The Unique button is only relevant for Customer Master and not the Order. In the Order you can have only one.
    The Button Modifiable is only for allowing you to change a Partner and not adding another partner with the same partner function.
    Any way I figured a way out,  we can use the system provided AA ( Partner Function) and able to use multiple AAs in a Service Contract./Scheduling agreements.
    But if you need to have multiple partner in a sales Order ...Only way seems to be to have Z1, Z2 Etc ...
    Thanks

  • Wrong contact partner in the CRM sales order come from ISA

    Hello,
    I'd like to know if is it possible to manage the partner dermination "contact from a shopping basket created in ISA.
    in my case, i have a shopphing basket created by a user XX and this shopping basket is used by a other  one (user ZZ) to create a crm sale order; The problem is that the contact filled in the crm order is the partner XX instead of ZZ. Is it possible to manage the determination by customizing XCM ou SPRO to define the suitable partner (ZZ)
    Best regards.
    CMA.

    Hello CMA,
    Thanks for explaining the problem clearly. Looks like you've got an issue. Though you created an "order" with reference to a "template", ISA doesn't use any Copy function configured in the backend. It is all done piece by piece using Java and ABAP code.
    This is certainly a bug in standard code - unless somebody finds a note that explains. I couldn't find any SAP notes on this issue. The "Create new order on the basis of an order template" finally uses the action CreateFromPredecessorAction. While there is code available to address the "Ship-To list", "drop ship - ship-to", "Sold-To", "Requested Delivery date" etc. of the  source (template) to target (basket or order), the code essentially misses to change the Contact person of the target document to the current user.
    You can address this issue in two ways. # Ask SAP to fix the bug in the above class or # Do it your own way, by just introducing an action to "massage" the data the way you want. The CreateFromPredecessorAction action has one outcome editdoc.
              <action path="/b2b/createfrompredecessor" type="com.sapmarkets.isa.isacore.action.CreateFromPredecessorAction">
                   <forward name="editdoc" path="/b2b/updatedocumentview.do"/>
    Introduce a custom action ZFixContactPersonAction immediately after like this:
              <action path="/b2b/createfrompredecessor" type="com.sapmarkets.isa.isacore.action.CreateFromPredecessorAction">
                   <forward name="editdoc" path="/b2b_custom/zFixContact.do"/>
              <action path="/b2b_custom/zFixContact." type="com.parxlns.action.ZFixContactPersonAction">
                   <forward name="success" path="/b2b/updatedocumentview.do"/>
    In this custom action, you can add some quick code to "fix" the contact person partner from the header.
    import com.sapmarkets.isa.businessobject.header.*;
    import com.sapmarkets.isa.businessobject.order.*;
    SalesDocument salesDoc = null;
    BusinessObjectManager bom =
            (BusinessObjectManager) userSessionData.
            getBOM(BusinessObjectManager.ISACORE_BOM);
    salesDoc = bom.getBasket();
        HeaderSalesDocument  header =
            (HeaderSalesDocument) request.
            getAttribute(MaintainBasketBaseAction.RK_HEADER);
    String selectedPartnerID = bom.getUser().getContactData().getId();
    String selectedPartnerGUID = (String) bom.getUser().getContactData().getTechKey();
    PartnerList partnerList = new PartnerList();
    //Get the document header - partner list value
                   PartnerList partnerList = header.getPartnerList();
                PartnerListEntry contactData = new PartnerListEntry(selectedPartnerGUID, selectedPartnerID );
    //Set the Contact partner in partner list
                partnerList.setContact(contactData);
    //Set this partner list back to header.
    header.setPartnerList(partnerList);
    return ("success");
    Hope this helps with little changes.
    (sorry, there I am not aware of any solution with simple customization in the backend)
    Easwar Ram
    http://www.parxlns.com

  • How to block a business partner...in sales order????

    Hi all,
               While generating the sales order....In the customer tab i will select one business partner from CFL,after choosing i want one particular customer to be blocked....means it should unable to post the sales order.....i know that i should write my coding in the customer tab LOST FOCUS event......can anybody suggest me the coding for this problem....
    regards,
    shangai.

    Shangai,
    How about blocking some partner from ChooseFromList of BP in Sales Order?
    Meaning that blocked some bp with criteria in Choose From List. Sample code:
    If pVal.FormType = 139 And pVal.EventType = SAPbouiCOM.BoEventTypes.et_CHOOSE_FROM_LIST Then
                If pVal.ItemUID = "4" Then
                    If pVal.InnerEvent And pVal.Before_Action Then
                        BubbleEvent = False
                        Dim oForm As SAPbouiCOM.Form
                        oForm = SBO_Application.Forms.Item(FormUID)
                        Dim oCons As SAPbouiCOM.Conditions                   
                        Dim oCFL As SAPbouiCOM.ChooseFromList
                        'oCFL = oCFLs.Add(oCFLCreationParams)
                        oCFL = oForm.ChooseFromLists.Item("2")
                        oCons = oCFL.GetConditions()
                        'Note: Add the condition only once.
                        If 0 = oCons.Count Then
                            Dim oCon As SAPbouiCOM.Condition
                            oCon = oCons.Add()
                            oCon.Alias = "Cardcode"
                            oCon.Operation = SAPbouiCOM.BoConditionOperation.co_EQUAL
                            oCon.CondVal = "C0001"
                            'Set your own condition here instead of the system conditions
                            oCFL.SetConditions(oCons)
                        End If
                        BubbleEvent = True
                    End If
                End If
            End If
    Regards, Yatsea

  • ITEM DETAILS: CONFIGURATION  in sales order

    Dear  guru,
    In the sale order if we want to see the variant configuration details for a particular line item then after selecting the line item we press
    the ITEM DETAILS: CONFIGURATION icon. Once we press this icon then the system will take us to a display characteristic value screen where we
    can see the configuration details of that particular line item. But now in PRODUCTION SYSTEM we are not finding any value for a variant
    configuration material in the sale order display characteristic value screen, eventhough it is maintained in the material master MRP3 view.
    But in deveploment  client  it is showing correctly.
    Pl. suggest

    Get with the VC person and have them move all the model details to PRD

Maybe you are looking for

  • Printer no longer works in the re-install of Leopard....

    ....here are some screenshots of the problem I suddenly ran into after a re-install of Leopard: http://www.PictureTrail.com/gid22335136 I've tried everything that I can think of and still not able to print anything. The printer was operating fine pri

  • Saving a PDF that is open in Firefox

    After opening a PDF in Firefox, I want to save it on my computer. The problem is that the "save a copy" box, where you name the file, always opens in full-screen mode. I need the "save a copy" box to open smaller-- the same size as in most other appl

  • How do I block a website on Firefox?

    I would like to block a website on the internet.

  • Printing Report without ORARRP

    Hy all, Please Help me, I want create report aplication with printing direct from default printer but without use orarrp. cause,I have any problem when use orarrp and my boss want the report printing direct from printer without pop up printer propert

  • Error : Workflow definition does not exits(T-code : SWU7 )

    Hi All, I checked my workflow template in SWU7 .Its gives me error "Workflow definition does not exits". In the bottom left of screen it displays message : "Container Element ZBUS2081 is not used". How can remove this error ? Please help..