Creation of customer with contact person detials using BAPI

Hi,
What is the standard BAPI for creating customer. I need to create the customer with contact person
details, what BAPI i can use for this, i was trying with 'BAPI_CUSTOMER_CREATEFROMDATA1' by populating structure personal data and copy reference data.. but it is giving some problem like currency is not entered..... can any one send me the sample code with this BAPI. Any help will be highly appreciated.
Thanks a lot in advance.

Similar Messages

Including Contact person detials in MDG 6.1 - Customer

Hello All,
While Creating MDG - Customer, I need to include Contact person information. I can see Contact Person tab in Customer FPM screen(Organisation type) but not able to relate to Business Partner ID.
My specific questions are
1. How to create BP/Customer with Contact Person?
2. Do we need to create Contact Person first and then relate to BP/Customer? If so, how i can i co-relate that ealier created Contact person with my current CR, which is being created for Customer.
3. I need to create Customer that includes Contact person details under same CR.
Please suggest me how to go forward?

Looks like the Contact Person needs to be created in role BUP001 as a Business Partner first.
Then after activating the Contacts functionality you will have the following subscreen in the UI:
Clicking on the New button will allow you to select the Contact Person from the Busines Partners table and also to specify data you need like address, function, etc. See below:
Hope that helps you get the idea on how it works...
Perhaps someone who played more with it would be able to contribute here , it's an interesting topic.
Regards,
Boris

Email notfication for Customer and Contact person Created In CRM to the User

Hi All,
In one of my requirement, when a customer and Contact person is created in ECC or CRM a Mail should send to the user who created. There is
middleware setting between ECC and CRM. Mail Should trigger in CRM system only.
I know to trigger email for transaction data using Action Profile.
Could any One guide me to trigger email notification for Master data (Business Partner).
Thanks in Advance.
Regards
RR Pradhan

Good afternoon Pradhan
1.I think it would normally be done through a mini wf which should start on event "partner created".
Your wf should have another step with a custom method to determine the email address and feed it to a container. You would then use this container in a subsequent email step with recipient type "email address".
2.In the case of actions I think you should use as processing time the option : Processing using the Selection Report (Action Monitor) (tnx sppfp)
As processing type you should probably have a method that sends an email.
Most likely the recipient email address should be determined in the same method by reading the attribute BusinessPartnerERM.CreatedBy.
In the scheduling conditions you could use the standard attribute BusinessPartnerERM.CreatedOn, in a combination like BusinessPartnerERM.CreatedOn = Today () ;
Hope this helps.
Regards
Razvan Zainea

Creating \ Changing Functional Location With Contact Person.

Hello.
I'm looking for BAPI / Function for creating/changing "Functional Location" with Adding, deleteing OR changing "Contact Person"
I Have found the BAPI's : BAPI_FUNCLOC_CHANGE
BAPI_FUNCLOC_CREATE
but thier is no option to handle with "contact person" .
(SAP Table "IHPA").
Best Regards'
Haim B.

Hello,
Instead of searching for any FM or anything. Go and create a flow thorugh LSMW and change the desired contact person through it..
I assure you this is the best and most efficient way.
first run LSMW and create a flow by changing the contact person of any one functional location and then assign the flow of that lSWM through external notepad file.
Get in the notepad all the desired FL you want to change run that within minutes your job will be done.

Sales order creation with reference to quote using BAPI

Hi All,
I am trying to create a sales order with reference to quote using BAPI BAPI_SALESORDER_CREATEFROMDAT2.
I am passing the Quote number and preceding doc.category (B) at the header level and
at item level I am passing the quote number and the line item number in the quote for REF_DOC and REF_DOC_IT.
The order is created but there seems to be some issue with the document flow.
I do not see the Reference Doc number at the header level from the Sales order document flow whereas I can see the Reference Doc for each line item.
In VBFA I can see the Ref.Doc number at the header level along with the Ref.Doc at the line item level.
Why do you think it is not showing at the header level from Sales Document Document Flow?
Is there any bug in the standard BAPI or is there any OSS note?
Any answer would be greatly appreciated.
Thanks
Sandeep

hi,
Are you giving different quotation numbers in the different line items, if that is the case you will not get that in the header document flow, as it cann't point to all the quotations.
Thanks,
Mahesh.

Creation of material Documents for RMPM adjustments using BAPI

Hi
can any one help me Creation of material Documents for RMPM adjustments using BAPI...
i should be grateful to you...
advance thank you
with regards
venkat

You can check MB_CREATE_GOODS_MOVEMENT which has mkpf as inporting parameter.

Target group with customer and contact person

Hi experts,
I want to create a target group with customer data and the names of the main contact person to execute a campaign.
During execution I need the name of the contact person to personalize my forms, the campaign activity should be connected to the customer (and not the contact person).
Is there a functionality to solve my problem? (CRM 7.0)
Thanks in advance.
Werner

Hi Werner,.
I assume you want to select for Organizations (BUT000 Type 2) and you want to see in the Target Group the Contact Persons which are assigned via Relationship to the Orgnizations.
Create for example a Datasource with Infoset CRM_MKTTG_BP_ORG, and under Details for Business Partner use BUT000_PER-PARTNER_GUID.
In Field Function Module maintain CRM_MKTTG_PF_BP_TAB_TO_CP.
Create an Attribute List an assign the Datasource. After Creating the Target Group you will see the Organizations with all the assigned Contact Persons via Relationsship.
Regards
Andreas
Another Tip: Create a Target Group for Persons, assign it to the Campaign, and now set the B2B Flag. Depending from your SP Level you have to apply a note so that the B2B Flag is visible (1263915)
If you set the B2B flag you will get Communication Data for letters, for a Call List from the Relationship.
Regards,
Andreas
Edited by: Andreas Pauli on Apr 29, 2009 10:18 AM

Error while posting Customer with Multiple sales areas using DEBMAS05.

Dear experts,
We are generating IDOCS vis SAP DS for posting Customer master. The message type used is DEBMAS and basic type is DEBMAS05. we have a requirement to create 1 customer with multiple sales areas. However, we are ending up with a strange error: "Fill all required fields SAPMF02D 0111 ADDR1_DATA-NAME1". Despite the IDOC going into status 51, the customer gets created and the 1st sales area too. the 2nd sales area however is not created! The IDOC data definitely contains Name1, otherwise the customer would not have been created in the first place.
As the error message is related to the Address data, I also explored upon exploring this erorr further on the lines of Central Address management where in the ADRMAS and DEBMAS have to be passed together(IDOC Serialiization). OSS Note (384462) provides further details about this. One Important point from the note is:
"As you have to specify the logical name of the sending system among other things, SAP is not able to make any default settings in the standard systems. When you use the serialization groups delivered as a standard by SAP, the address objects are imported before the master objects.Thus the sequence address data before master objects must only be adhered to if one of the following points applies to your application:
Such fields are set as required entry fields that are only provided by the BAS in the Customizing of the customer or vendor master.
For your customers, contact persons exist to which a private address or a different business address is assigned.".
This is not the case in our situation, as we do not have required entry fields in customizing that are only provided by the BAS, so the error is all the more confusing and I am not too sure what the cause is.
If someone have experienced the same issue before and have found a solution to it, kindly help out.

I have found the cause and solution to this problem.
This error ”Fill all required fields SAPMF02D 0111 ADDR1_DATA-NAME1” and other similar errors like “Fill all required fields SAPMF02D 0111 ADDR1_DATA-SORT1“ which occurrs during the IDOC posting when there are more than one sales area or company code occurs when the customer number range is set up for Internal numbering. This means, that the number gets generated only at the time of save and upon debugging the IDOC, we found out that after creating the customer and the first sales area/company code record, the segment E1KNA1M is cleared completely! This is the reason, it throws an error which points to a mandatory KNA1 field as missing. (Like NAME1, SORT1 etc.)
This was resolved by splitting the IDOC into 2.
The solution is to First post only the KNA1 segment and create the customer.
In the second step, pass the IDOC with all other segments along with E1KNA1M, but pass only KUNNR in E1KNA1M and the rest of the fields in E1KNA1M as “/”: you would have got the KUNNR after the first step.
Important note: This requirement to split the IDOCs does not occur when the customer number is known upfront. (Meaning cases where the customer number is externally generated) I also tested this and created a customer with external numbering and I was able to post more than 1 sales area with the same IDOC.
I noticed multiple threads with the same issue, but none of it had a concrete answer. I hope this information will be useful for anyone facing similar problems.
Cheers
Venkat

Target group with Contact Person from Organisation

Dear experts,
we are currently on CRM 7.0 SP06.
In segment Builder (GUI) there is an option in context menu for target group which allows us to create a new target group with all the contact persons from an existing target group with organisations.
I know that we have to use the WEB UI. But there I could not find this functionality.
Although we can achieve the same building up our own infoset, I would like to know if this functionaltiy is actually missing, or not supported anymore.
Kind regards
Hannes

H isubash,
thanks for your answer. I know that this funciotnality is not available in WEB UI, although it is provided in conetxt menu in GUI.
Does anyone know if SAP simply not provided this functionality in current releases?
Kind regards
Hannes

Creation of sales order with reference to Quotation using BAPI

Hi All,
I am using BAPI "BAPI_SALESORDER_CREATEFROMDAT2" for creating sales order. Can you please tell how can I create a sales order with reference to a Quotation.

Vinit,
In your header structure, set like this:
hdr-REF_DOC = i_order-vbeln. "assign quotation # to sales order
hdr-REFDOC_CAT = 'B'.         "assign Quotation to VBTYP_N.
For each line item, set as follows:
Assigning ref doc to create line item entries in VBFA.
    itm-REF_DOC    = i_order-vbeln. "quote number
    itm-REF_DOC_IT = i_vbap-posnr.   "quote line item #
    itm-REF_DOC_CA = 'B'.
data: ret_text type BAPIRET2.
CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'
    EXPORTING
      ORDER_HEADER_IN           = hdr
      convert                   = 'X'
    IMPORTING
      SALESDOCUMENT             = salesdoc
    TABLES
      return                    = ret_tbl
      ORDER_ITEMS_IN            = itm
      ORDER_PARTNERS            = prtnr
      ORDER_ITEMS_inx           = itmx
      ORDER_CONDITIONS_IN       = conds
      ORDER_CONDITIONS_INX      = condsx
      order_schedules_in        = schd_lin.
Don't forget those points.

Problem with Contact person Relationship...

Hi All,
I got the following issue.
"Contact person relationship already exists between partners &1 and &2...."
For this, I have checked the Business partners, tables and GUID's in R/3 and as well as in CRM and checked BP consistency fix...
I have seen change history also, this problem occured to BUPA_REL B.Doc type. While after doing the Synchronization also i am getting errors like "BP already exists and Partner (GUID No) errors occured...
Please advise regarding this issue...
Thanks in Advance.....

Hello,
You are leaving an unmanaged object in the tree when the transaction attempts to commit. If you are going to persist a new VerticalUser, it must reference an existing or managed VerticalHommeArt.
If the VerticalUser references a new VerticalHommeArt, either persist the VerticalHommeArt before or set the verticalHommeArt relationship to cascade persist
Best Regards,
Chris

Creation of po with mutiple line items using BDC

Hi Gurus,
      Can any body hav notes for creating po's using BDC with multiple line items in transaction ME21. I hav created po for single line item but if i tried to create multiple line items, it ll create multiple po's...
thanks in advance
arun

See the Below Logic for me22 and it is also same for me21
report zpochange.
data : i_error like bdcmsgcoll occurs 0 with header line.
data : i_bdcdata like bdcdata occurs 0 with header line.
tables : ekko, ekpo.
data :c1(10) value 'ME22',
      c2(1) value ',',c3(10).
data : var1(20). " LIKE EKKO-EBELN.
data : var2 like ekko-ebeln.
data : begin of i_ekko occurs 0,
          header(2),
          ebeln like ekko-ebeln,
          end of i_ekko.
data : begin of i_ekpo occurs 0,
item(2),
        ebeln like ekpo-ebeln,
        ebelp like ekpo-ebelp,
        menge(10), " LIKE EKPO-MENGE,
       end of i_ekpo.
data : v like ekpo-ebelp.
data: begin of itab occurs 0,
         text(300),
        end of itab.
parameters: p_file like ibipparms-path.
*PARAMETERS: PONUMBER LIKE EKPO-EBELN.
at selection-screen on value-request for p_file.
call function 'F4_FILENAME'
exporting
    program_name        = syst-cprog
    dynpro_number       = syst-dynnr
   FIELD_NAME          = ' '
importing
    file_name           = p_file
start-of-selection.
*SELECT EBELN FROM EKKO INTO TABLE I_EKKO WHERE EBELN = PONUMBER.
      SELECT EBELN EBELP MENGE FROM EKPO INTO TABLE I_EKPO WHERE EBELN
*= PONUMBER.
perform get_data.
*LOOP AT ITAB.
WRITE :/ ITAB.
ENDLOOP.
loop at itab.
var1 = itab-text+0(1).
if var1 = 'H'.
*I_EKKO-EBELN = ITAB-TEXT.
split itab at c2 into i_ekko-header
                       i_ekko-ebeln.
SPLIT ITAB AT ',' INTO I_EKKO-EBELN.
                    " I_EKPO-EBELP
                    " I_EKPO-MENGE
                    " var1.
append i_ekko.
else.
split itab at c2 into i_ekpo-item
                        i_ekpo-ebeln
                        i_ekpo-ebelp
                        i_ekpo-menge.
append i_ekpo.
endif.
*var2 = i_ekpo-ebeln.
MOVE VAR1 TO I_EKPO-EBELN.
MOVE VAR1 TO I_EKKO-EBELN.
APPEND: I_EKPO.
*if not var1 is initial.
    split var1 at ',' into i_ekpo-ebelp
                           i_ekpo-menge.
i_ekpo-ebeln = var2.
append i_ekpo.
*endif.
endloop.
loop at i_ekpo.
write :/ i_ekpo.
endloop.
loop at i_ekko.
perform fill_data. " TABLES I_EKPO.
endloop.
LOOP AT I_EKPO.
WRITE :/ I_EKPO.
ENDLOOP.
*&      Form GET_DATA
      text
--> p1        text
<-- p2        text
*LOOP AT I_ERROR.
WRITE :/ I_ERROR.
ENDLOOP.
form get_data.
call function 'WS_UPLOAD'
exporting
   codepage                      = ' '
   filename                      = p_file
   filetype                      = 'ASC'
   headlen                       = ' '
   line_exit                     = ' '
   trunclen                      = ' '
   user_form                     = ' '
   user_prog                     = ' '
   dat_d_format                  = ' '
IMPORTING
FILELENGTH                    =
tables
    data_tab                      = itab
exceptions
   conversion_error              = 1
   file_open_error               = 2
   file_read_error               = 3
   invalid_type                  = 4
   no_batch                      = 5
   unknown_error                 = 6
   invalid_table_width           = 7
   gui_refuse_filetransfer       = 8
   customer_error                = 9
   others                        = 10
if sy-subrc <> 0.
message id sy-msgid type sy-msgty number sy-msgno
         with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
endif.
endform.                    " GET_DATA
*&      Form FILL_DATA
      text
     -->P_I_EKPO text
form fill_data. " tables   i_ekpo .
perform bdcscreen using 'SAPMM06E' '0105'.
perform bdcfield using 'RM06E-BSTNR' i_ekko-ebeln.
perform bdcfield using 'BDC_OKCODE' '/00'.
loop at i_ekpo where ebeln = i_ekko-ebeln.
V = I_EKPO-EBELP.
perform bdcscreen using 'SAPMM06E' 0120.
perform bdcfield using 'BDC_CURSOR' 'RM06E-EBELP'.
perform bdcfield using 'RM06E-EBELP' i_ekpo-ebelp.
perform bdcfield using 'BDC_OKCODE' '/00'.
perform bdcscreen using 'SAPMM06E' 0120.
perform bdcfield using 'BDC_CURSOR' 'EKPO-MENGE(01)'.
perform bdcfield using 'RM06E-EBELP' i_ekpo-ebelp.
perform bdcfield using 'EKPO-MENGE(01)' i_ekpo-menge.
perform bdcfield using 'BDC_OKCODE' '/00'.
*PERFORM BDCSCREEN USING 'SAPMM06E' 0120.
*PERFORM BDCFIELD USING 'BDC_CURSOR' 'RMO6E-EBELP'.
*CLEAR V.
endloop.
perform bdcfield using 'BDC_OKCODE' '=BU'.
call transaction c1 using i_bdcdata mode 'A'
                                   messages into i_error.
refresh i_bdcdata.
endform.                    " FILL_DATA
*&      Form BDCSCREEN
      text
     -->P_0140   text
     -->P_0120   text
form bdcscreen using    p_program p_screen.
i_bdcdata-program = p_program.
i_bdcdata-dynpro = p_screen.
i_bdcdata-dynbegin = 'X'.
append i_bdcdata.
clear i_bdcdata.
endform.                    " BDCSCREEN
*&      Form BDCFIELD
      text
     -->P_0145   text
     -->P_I_EKPO_EBELN text
form bdcfield using    fnam fval.
i_bdcdata-fnam = fnam.
i_bdcdata-fval = fval.
append i_bdcdata.
clear i_bdcdata.
endform.                    " BDCFIELD
Reward Points if it is helpful
Thanks
Seshu

Creation of saleorder with reference to order using BAPI_SALESORDER_CREATE

hello
iam trying to create a sale order with respect to order BAPI_SALESORDER_CREATEFROMDAT2.
the parameters i am passing is
*Fill the header information for the order.
wa_order_header_in-doc_type = Sales Doc type of order to be created.
wa_order_header_in-sales_org = sales org.
wa_order_header_in-distr_chan = distribution channel.
wa_order_header_in-division = division.
wa_order_header_in-ref_doc = order number(This is the order i refer to).
wa_order_header_in-refdoc_cat = 'C' (c stands for order).
*Fill the item level information for the order.
wa_order_items_in-itm_number = item number.
wa_order_items_in-material = material number.
wa_order_items_in-ref_doc = order number(This is the order i refer to).
wa_order_items_in-ref_doc_it = Item number of order i create.
wa_order_items_in-ref_doc_ca = 'C'.
APPEND wa_order_items_in TO i_order_items_in.
*Fill the partner information for the order.
wa_order_partners-partn_role = partner function.
wa_order_partners-partn_numb = partner number.
APPEND wa_order_partners TO i_order_partners.
& likewise conditions structure
i have done bapi_transaction_commit after bapi call.
probelm which i am facing is , BAPI is creating a new sale order.. but it is not creating a order with reference order.
thanks

see this example as how to add text and multiple lines...
loop at it_tab into wa_tab.
        record_no = sy-tabix.
        serial_no = wa_tab-ser_no.
*       ORDER_TYPE = WA_TAB-ORD_TYP.
        sales_office = wa_tab-sal_off.
        sales_group = wa_tab-sal_grp.
        old_ref_no = wa_tab-ref_shp_to_par.
        shipping_condition = wa_tab-ship_cond.
        perform sales_info using sales_office sales_group
shipping_condition.
        condense shipping_condition.
        ship_cond = shipping_condition.
        on change of old_ref_no.
          refresh it_bapisdhead.
          refresh it_bapisdhead1x.
          refresh it_bapiparnr.
             wa_bapisdhead-doc_type     = wa_tab-ord_typ.
             wa_bapisdhead1x-doc_type   = 'X'.
             wa_bapisdhead-sales_org    = '5088'.
             wa_bapisdhead1x-sales_org = 'X'.
             wa_bapisdhead-distr_chan   = '01'.
             wa_bapisdhead1x-distr_chan = 'X'.
             wa_bapisdhead-division     = '00'.
             wa_bapisdhead1x-division   = 'X'.
             wa_bapisdhead-sales_grp    = sales_group.
             wa_bapisdhead1x-sales_grp = 'X'.
             wa_bapisdhead-sales_off    = sales_office.
             wa_bapisdhead1x-sales_off = 'X'.
             wa_bapisdhead-purch_no_c   = wa_tab-po_no.
             wa_bapisdhead1x-purch_no_c = 'X'.
             wa_bapisdhead-purch_date   = wa_tab-po_date.
             wa_bapisdhead1x-purch_date = 'X'.
             wa_bapisdhead-req_date_h   = wa_tab-req_del_date.
             wa_bapisdhead1x-req_date_h = 'X'.
             wa_bapisdhead-incoterms1   = 'EXW'.
             wa_bapisdhead1x-incoterms1 = 'X'.
             wa_bapisdhead-incoterms2   = wa_tab-inco_terms2.
             wa_bapisdhead1x-incoterms2 = 'X'.
             wa_bapisdhead-ship_cond    = ship_cond.
             wa_bapisdhead1x-ship_cond = 'X'.
             wa_bapisdhead-ref_1        = wa_tab-ref_sld_to_par.
             wa_bapisdhead1x-ref_1      = 'X'.
             wa_bapisdhead-ref_1_s      = wa_tab-ref_shp_to_par.
             wa_bapisdhead1x-ref_1_s    = 'X'.
             append wa_bapisdhead to it_bapisdhead.
             append wa_bapisdhead1x to it_bapisdhead1x.
             wa_bapiparnr-unload_pt    = wa_tab-unload_pt.
             wa_bapiparnr-partn_role   = 'AG'.
             wa_bapiparnr-partn_numb   = wa_tab-sld_to_par.
             append wa_bapiparnr to it_bapiparnr.
             clear wa_bapiparnr.
             wa_bapiparnr-partn_role   = 'VE'.
             wa_bapiparnr-partn_numb   = '777'.
             append wa_bapiparnr to it_bapiparnr.
             clear wa_bapiparnr.
             wa_bapiparnr-partn_role   = 'ZM'.
             wa_bapiparnr-partn_numb   = '999'.
             append wa_bapiparnr to it_bapiparnr.
             clear wa_bapiparnr.
           if wa_tab-bill_to_par <> ' '.
             wa_bapiparnr-partn_role   = 'RE'.
             wa_bapiparnr-partn_numb   = wa_tab-bill_to_par.
             append wa_bapiparnr to it_bapiparnr.
             clear wa_bapiparnr.
           endif.
           if wa_tab-payer <> ''.
             wa_bapiparnr-partn_role   = 'RG'.
             wa_bapiparnr-partn_numb   = wa_tab-payer.
             append wa_bapiparnr to it_bapiparnr.
             clear wa_bapiparnr.
           endif.
           if wa_tab-ship_to_par <> ''.
             wa_bapiparnr-partn_role   = 'WE'.
             wa_bapiparnr-partn_numb   = wa_tab-ship_to_par.
             append wa_bapiparnr to it_bapiparnr.
             clear wa_bapiparnr.
           endif.
           wa_bapisdtext-text_id   = 'Z113'.
           wa_bapisdtext-langu     = 'EN'.
           wa_bapisdtext-text_line = wa_tab-add_txt.
           append wa_bapisdtext to it_bapisdtext.
           clear wa_bapisdtext.
           if wa_tab-banker <> ''.
             wa_bapisdtext-text_id   = 'ZKT1'.
             wa_bapisdtext-langu     = 'EN'.
             wa_bapisdtext-text_line = wa_tab-banker.
             append wa_bapisdtext to it_bapisdtext.
             clear wa_bapisdtext.
           endif.
           if wa_tab-fwd_age <> ''.
             wa_bapisdtext-text_id   = 'ZKT1'.
             wa_bapisdtext-langu     = 'EN'.
             wa_bapisdtext-text_line = wa_tab-fwd_age.
             append wa_bapisdtext to it_bapisdtext.
             clear wa_bapisdtext.
           endif.
        endon.
*                  ***** ITEM LEVEL DATA *****
             wa_bapiitemin-material     = wa_tab-matno.
             wa_bapiiteminx-material    = 'X'.
             wa_bapiitemin-target_qty   = wa_tab-qty.
             wa_bapiiteminx-target_qty = 'X'.
             wa_bapiitemin-plant        = wa_tab-plant.
             wa_bapiiteminx-plant       = 'X'.
             wa_bapiitemin-item_categ   = 'YAPS'.
             wa_bapiiteminx-item_categ = 'X'.
             append wa_bapiitemin to it_bapiitemin.
             append wa_bapiiteminx to it_bapiiteminx.
             clear wa_bapiitemin.
             clear wa_bapiiteminx.
*             WA_BAPICOND-COND_TYPE      = 'PR00'.
*             WA_BAPICONDX-COND_TYPE     = 'X'.
             wa_bapicond-cond_value     = wa_tab-amt * wa_tab-qty.
             wa_bapicondx-cond_value    = 'X'.
             append wa_bapicond to it_bapicond.
             append wa_bapicondx to it_bapicondx.
             clear wa_bapicond.
             clear wa_bapicondx.
        at end of ref_shp_to_par.
          call function 'BAPI_SALESORDER_CREATEFROMDAT2'
            exporting
*             SALESDOCUMENTIN               =
              order_header_in               = wa_bapisdhead
              order_header_inx              = wa_bapisdhead1x
*             SENDER                        =
*             BINARY_RELATIONSHIPTYPE       =
*             INT_NUMBER_ASSIGNMENT         =
*             BEHAVE_WHEN_ERROR             =
*             LOGIC_SWITCH                  =
*             TESTRUN                       =
*             CONVERT                       = ' '
*           IMPORTING
*             SALESDOCUMENT                 =
            tables
              return                        = it_errmsg
              order_items_in                = it_bapiitemin
              order_items_inx               = it_bapiiteminx
              order_partners                = it_bapiparnr
*             ORDER_SCHEDULES_IN            =
*             ORDER_SCHEDULES_INX           =
              order_conditions_in           = it_bapicond
              order_conditions_inx          = it_bapicondx
*             ORDER_CFGS_REF                =
*             ORDER_CFGS_INST               =
*             ORDER_CFGS_PART_OF            =
*             ORDER_CFGS_VALUE              =
*             ORDER_CFGS_BLOB               =
*             ORDER_CFGS_VK                 =
*             ORDER_CFGS_REFINST            =
*             ORDER_CCARD                   =
              order_text                    = it_bapisdtext
*             ORDER_KEYS                    =
*             EXTENSIONIN                   =
*             PARTNERADDRESSES              =
    read table it_errmsg into wa_errmsg with key type = 'E'
    binary search.
    if sy-subrc ne 0.
             call function 'BAPI_TRANSACTION_COMMIT'
    endif.
endloop.

Updating Custom field in Table BUT000 using BAPI 'BAPI_ISUPARTNER_CHANGE'.

Hi,
I have added a new custom field in table BUT000. Now i want to update that field with 'X' and i have used EXTENSIONIN parameter in the BAPI 'BAPI_ISUPARTNER_CHANGE'. i have populated the field name(Custom field name) and value 'X' to that structure and passed to BAPI. But that field value was not getting updated. So can any one help me how to resolve this issue.
Thanks,
Sushma

Hi Ravi,
Thanks for your response.
I have passed the Structure name in parameter EXTENSIONIN, but still i am facing the same problem.
Thanks,
Sushma

Create contract with Purchase Requisition reference using BAPI

Hi friends! I need some help here to create a contract with reference to some purshase requisition. I found BAPI_CONTRACT_CREATE to do this, but I have no idea how to do to create with reference to pruchase requisition.
Anyone can give me a sample code or an idea how I can do this?
Thanks in advance for any help.

Thanks friend. I filled Header, Headerx, item e itemx but I'm getting this error:
No instance of object type PurchasingContract has been created. External reference: # 1
Item category 9 not supported
I need fill something else?

Creation of customer with contact person detials using BAPI

Similar Messages

Maybe you are looking for