How to associate Ship-To-Party to a Sold-To-Party using BAPI

I am looking for a BAPI that will allow me to associate existing Ship-To-Party to an existing Sold-To-Party. I tried to search for the BAPI that might do this job but could not find one. Any help is greatly appreciated.
System: SAP R/3 4.7
Edited by: Jignesh Jethva on Nov 19, 2009 12:11 AM

Hi,
Check table CRMM_BUT_LNK0141 to obtain the sales area of a BP (by BP Guid).
If you need the sales office and sales group, read GuidSet of that table and check table CRMM_BUT_SET0140 to list the sales office and sales group by that Guid set.
There are some function modules too:
CMS_BUPA_ORGDATA_GET_BL among others.
Regards,
Susana Messias

Similar Messages

No.of ship-to-parties to one sold-to-party

how to update the no. of ship-to-parties of one sold-to-party, 999 nos is standard
plz give the answer to my question and where standard will locate?
jagan

Hi Jagmohan
well in SAP the max limit to a line item would be 999 ,there is nothing we can do about this ,so you cant have more than 999 Partner functions and there is no user exit also for this.
this is similar to in a sale order you cant have more than 999 line item and in case you have the system will split the order
Hope this helps
Cheers

Ship to party change to Sold to party

Hi,
I want to change the following code which is for Ship to party, to for Sold to Party. How to go ahead?
<select name="headerShipTo">
<isa:iterate id="shipTo"
name="<%= MaintainBasketBaseAction.SC_SHIPTOS %>"
type="com.sapmarkets.isa.businessobject.ShipTo">
<% String selected = "";
if (soldTo.equals(header.getSoldTo())) {
selected = " selected";
} %>
<option <%= selected %> value="<%= shipTo.getTechKey() %>"><%= shipTo.getShortAddress() %></option>
</isa:iterate>
</select>
IS MaintainBasketBaseAction.SC_SOLDTOS will work? I am not able to find API for this.
Shaun.

Hi
Use XD07 Transaction code.
regards
Srinivas

Maxinum number of ship-to party for a sold-to party?

Dear Expert,
Is there any limitation on the number of the ship-to party that a sold-to party can have? I was told that one sold-to party can have maximally 999 ship-to party? Is it true? If it is true, what if a sold-to party does have more than 999 ship-to parties?
This could be the potential problem of my client, because the number of the ship-to party for one sold-to party is increasing intensively and may exceed the LIMIT in the future?
Any input will be appreciated.
Thanks!
Regards,
Wang Hui

Hi Bashir,
The problem has been solved.
Actually in sales order, you are allowed to put ship-to party which is not linked to the sold-to party in the master data, that means you can manually key in any ship-to party as you like. I didn't know this before:(
In our case, the orders are transmitted via EDI and created automatically, so the ship-to party is also determined automatically in a user exit, so we can have as many ship-to party as we want.
Thanks!
Regards,
Wang Hui
>
Bashir wrote:
> Hi,
>
>
> I will need more information on your query to solve
> Can you provide the details of industry ur client belongs to
>
>
> As it will be more complex to select 1 ship to party from the xxxx numbers, Can you try this with customer Hierarchy functionality.
>
>
> Regards,
> Bashir

Validate ship to party depending on sold to party

i need Validate ship to party depending on sold to party from the table knvp in which userExit should i write the code??

Hi,
sold to party is the partner who ordered , and the shipt o party is where actually the goods to be delivered.
if in an organization it has one sales department and one manufacturing department then sales Dept orders goods on behalf of Manufacturing plant and the good will be delivered at plant premises. here sales dept is sold to party and Manufacturing plant in ship to party.
Go through this link it is very useful for u
https://forums.sdn.sap.com/click.jspa?searchID=12912281&messageID=3626601
Thanks&Regards,
Naresh

How create to master contracts for each new sold to party

Hey SAP geeks,
I have a scenario, in which I need to create a maitenance contract based on support items in a billing document. The system should create a master contract for a particular sold to party if that sold to party has ordered support for the first time.(system should first search whether any master contracts exist for this particualr sold to and then create one if there arent any already created.) After the master contract is automatically created ,the system should create maintenance contracts based upon the support items in the billing document and then assign this contract to the master contract for that particualr sold to party. Is this possible? Can you tell me how we can do this? Points will be awarded. I guess this requires lot of ABAP programming. but it would be great if some help is provided.
Thanks.
Naveen

Dear Hanumant,
As per my view,,
You can use one time customer functionality to full fill your requirement.
When you create sales order with one time customer system take you to the customer data maintanence screen through that you can maintain the one time customer data.
Same one time customer number you can use for every new order through maintaining different data.
I hope this will help you,
Regards,
Murali.
Edited by: Murali Mohan.Tallapaneni on Dec 19, 2008 6:08 AM

How to find out Sales organization of a sold to party from tables

Hi all experts, I have the following questions:
1. How to find out Sales organization of a sold to party using tables?
2. Also please tell any function module which gives relationship between sold-to-party and sales organization to which it belongs.

Hi,
Check table CRMM_BUT_LNK0141 to obtain the sales area of a BP (by BP Guid).
If you need the sales office and sales group, read GuidSet of that table and check table CRMM_BUT_SET0140 to list the sales office and sales group by that Guid set.
There are some function modules too:
CMS_BUPA_ORGDATA_GET_BL among others.
Regards,
Susana Messias

How to retrieve data from catsdb table and convert into xml using BAPI

How to retrieve data from catsdb table and convert into xml using BAPI
Points will be rewarded,
Thank you,
Regards,
Jagrut BharatKumar Shukla

Hi,
This is not your requirment but u can try this :
CREATE OR REPLACE DIRECTORY text_file AS 'D:\TEXT_FILE\';
GRANT READ ON DIRECTORY text_file TO fah;
GRANT WRITE ON DIRECTORY text_file TO fah;
DROP TABLE load_a;
CREATE TABLE load_a
(a1 varchar2(20),
a2 varchar2(200))
ORGANIZATION EXTERNAL
(TYPE ORACLE_LOADER
DEFAULT DIRECTORY text_file
ACCESS PARAMETERS
(FIELDS TERMINATED BY ','
LOCATION ('data.txt')
select * from load_a;
CREATE TABLE A AS select * from load_a;
SELECT * FROM A
Regards
Faheem Latif

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

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

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

Ship-to-party to corresponding sold-to-party

hi all,
i need to know how to find out the ship-to-party for the corresponding sold-to-party, what is table used to determine this relation .
thanks,
ravi.s

Hi,
If you want optimized (buffered) table access, you can use the function module SD_KNVP_READ. This returns the relevant partners as FET_KNVP.
CALL FUNCTION 'SD_KNVP_READ'
       EXPORTING
            FIF_VKORG             = p_vkorg
            FIF_VTWEG             = p_vtweg
            FIF_SPART             = p_spart
            FIF_KUNNR             = customer
            FIF_FILTER_PARVW      = 'WE'     "Space gives all partners
            FIF_FILTER_PARNR      = ' '
            FIF_CONSUMER          = ' '
            FIF_BUFFER_NOFILL     = ' '   "Pass 'X' if frequent access in the program
            FIF_CLEAR_BUFFER      = ' '   "as needed
       IMPORTING
            FES_KNVP              = dummy_knvp
            FEF_KNVP_RECORDS_READ = dummy_int
       TABLES
            FET_KNVP              = t_shipto
Hope this helps,
Bhanu

Delivery report output for'Ship-to party address and Sold-to party address'

Hi Experts,
We have an report output generated upon delivery creation.
We need print following fields:
Ship-to party #
Ship-to party Name
Ship-to Party Address
Sold-to party #
Sold-to party Name
Sold-to Party Address
As per i understand, we could get those field according to partner function....
So experts, could please advise me from which table and field and logic to get above information....
Thank you very much!!

Hi,
Are you changing partner details in delivery document?
This partner address details will be updated in VBPA table.
E.g change the partner street no. in delivery document manually.
Now goto VBPA table, enter correspondence sales document number for that delivery and execute.
Click on partner function AG / WE get the address number (ADRNR) .
Now goto ADRC table, enter this address number in ADRNR field and execute. you will get partner details.
Regards,
Chandra

Multiple ship to parties for one sold to party.

Hi all,
Suppose we get a P.O which has material A quantity is 10. the sold to party tells that each of the 10 items must be edlivered to 10 different ship to parties. I mean each ship to party recieves 1 qty of material A. Can you explain what setting should be done to process this type of process.

Hi Vikrant,
For restricting the quantity to 1 for each ship-to party, you need to go to VOV7, choose your Item Category, there you'll find a check box "Order quantity equal to 1". But in this case for every ship-to party you need to create sparate Order.
Hope this will prove helpful to you
Reward points if so
Regards
SD

How to create a Sales order with ref. with serial number using BAPI

Hi Gurus...
I have a requirement where, i need to create an order with reference to serial number using a BAPI.
The inputs will be the Order type..Sales area..Sales office..Sales group..Sold-To-party..Material number...Serial number...
When i create the order using VA01 the configuration data will be automatically copied from the BUMP order which will have all the required information.
But to create using a BAPI, i am struck ed..Please help
Thanks in advance..
Srinu

You can use this BAPI.
You can pass ITM_NUMBER to the ORDER_ITEMS_IN parameter. I think this will act as serial number.
Regards,
Murali

One Sold to Party to Multiple Sold to Party (Legacy IDs)

Hi All,
Can we have multiple sold to party (which are the legacy customer IDs. Multiple legacy system. The same customer has different IDs in each legacy system) for a customer in SAP.
Please let me know if you need any more info.
Thanks,
Himanshu.

Refer one my earlier discussed SDN thread.
- search for customer using KNB1-ALTKN
I believe that should be helpful to you.
Let us know whether that was helpful to you.
Or you need further assistance.
Regards
JP

How do you know which fields are mandatory while uploading PO using BAPI.

How do you know which fields are mandatory while uploading PO data using BAPI. in a structure how do you know which fields are mandatory.
and also, where how do you check that, the BAPI function module is executed.
Thanks in Advance.
Naveen.

hi
hope it will help you.
Reward if help.
REPORT zpo_bapi_purchord_tej.
DATA DECLARATIONS *
TYPE-POOLS slis.
TYPES: BEGIN OF ty_table,
v_legacy(8),
vendor TYPE bapimepoheader-vendor,
purch_org TYPE bapimepoheader-purch_org,
pur_group TYPE bapimepoheader-pur_group,
material TYPE bapimepoitem-material,
quantity(13),
delivery_date TYPE bapimeposchedule-delivery_date,
net_price(23),
plant TYPE bapimepoitem-plant,
END OF ty_table.
TYPES: BEGIN OF ty_alv,
v_legs(8),
success(10),
v_legf(8),
END OF ty_alv.
TYPES: BEGIN OF ty_alv1,
v_legf1(8),
v_msg(500),
END OF ty_alv1.
*-----Work area declarations.
DATA: x_table TYPE ty_table,
x_header TYPE bapimepoheader,
x_headerx TYPE bapimepoheaderx,
x_item TYPE bapimepoitem,
x_itemx TYPE bapimepoitemx,
x_sched TYPE bapimeposchedule,
x_schedx TYPE bapimeposchedulx,
x_commatable(255),
x_alv TYPE ty_alv,
x_alv1 TYPE ty_alv1,
x_alv2 TYPE ty_alv1.
*-----Internal table declarations.
DATA: it_table TYPE TABLE OF ty_table,
it_commatable LIKE TABLE OF x_commatable,
it_item TYPE TABLE OF bapimepoitem,
it_itemx TYPE TABLE OF bapimepoitemx,
it_sched TYPE TABLE OF bapimeposchedule,
it_schedx TYPE TABLE OF bapimeposchedulx,
it_alv TYPE TABLE OF ty_alv,
it_alv1 TYPE TABLE OF ty_alv1,
it_alv2 TYPE TABLE OF ty_alv1.
DATA: po_number TYPE bapimepoheader-po_number,
x_return TYPE bapiret2,
it_return TYPE TABLE OF bapiret2,
v_file TYPE string,
v_temp(8),
v_succsount TYPE i VALUE 0,
v_failcount TYPE i VALUE 0,
v_total TYPE i.
DATA: v_temp1(5) TYPE n VALUE 0.
DATA: x_event TYPE slis_t_event,
x_fieldcat TYPE slis_t_fieldcat_alv,
x_list_header TYPE slis_t_listheader,
x_event1 LIKE LINE OF x_event,
x_layout1 TYPE slis_layout_alv,
x_variant1 TYPE disvariant,
x_repid2 LIKE sy-repid.
DATA : it_fieldcat TYPE TABLE OF slis_t_fieldcat_alv.
SELECTION-SCREEN *
SELECTION-SCREEN BEGIN OF BLOCK v_b1 WITH FRAME.
*-----To fetch the flat file.
PARAMETERS: p_file TYPE rlgrap-filename.
SELECTION-SCREEN END OF BLOCK v_b1.
AT SELECTION-SCREEN *
AT SELECTION-SCREEN.
IF p_file IS INITIAL.
MESSAGE text-001 TYPE 'E'.
ENDIF.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.
*-----To use F4 help to find file path.
CALL FUNCTION 'F4_FILENAME'
EXPORTING
program_name = syst-cprog
dynpro_number = syst-dynnr
IMPORTING
file_name = p_file.
v_file = p_file.
START-OF-SELECTION *
START-OF-SELECTION.
PERFORM gui_upload.
LOOP AT it_table INTO x_table.
PERFORM header_details.
v_temp = x_table-v_legacy.
LOOP AT it_table INTO x_table WHERE v_legacy = v_temp.
PERFORM lineitem.
PERFORM schedule.
ENDLOOP.
DELETE it_table WHERE v_legacy = v_temp.
PERFORM bapicall.
MOVE po_number TO x_alv-success.
APPEND x_alv TO it_alv.
CLEAR x_alv.
*-----To clear the item details in internal table after the operation for a header.
REFRESH: it_item,
it_itemx,
it_sched,
it_schedx.
CLEAR: v_temp1.
ENDLOOP.
v_total = v_succsount + v_failcount.
PERFORM display_alv.
FORM GUI_UPLOAD *
FORM gui_upload .
CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
filename = v_file
filetype = 'ASC'
TABLES
data_tab = it_commatable
EXCEPTIONS
file_open_error = 1
file_read_error = 2
no_batch = 3
gui_refuse_filetransfer = 4
invalid_type = 5
no_authority = 6
unknown_error = 7
bad_data_format = 8
header_not_allowed = 9
separator_not_allowed = 10
header_too_long = 11
unknown_dp_error = 12
access_denied = 13
dp_out_of_memory = 14
disk_full = 15
dp_timeout = 16
OTHERS = 17
IF sy-subrc = 0.
*-----To fetch the comma seperated flat file into an internal table.
LOOP AT it_commatable INTO x_commatable.
IF x_commatable IS NOT INITIAL.
SPLIT x_commatable AT ',' INTO
x_table-v_legacy
x_table-vendor
x_table-purch_org
x_table-pur_group
x_table-material
x_table-quantity
x_table-delivery_date
x_table-net_price
x_table-plant.
APPEND x_table TO it_table.
ENDIF.
CLEAR x_table.
ENDLOOP.
ENDIF.
ENDFORM. " gui_upload
FORM HEADER_DETAILS *
FORM header_details .
MOVE 'NB' TO x_header-doc_type.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
EXPORTING
input = x_table-vendor
IMPORTING
output = x_table-vendor
MOVE x_table-vendor TO x_header-vendor.
MOVE x_table-purch_org TO x_header-purch_org.
MOVE x_table-pur_group TO x_header-pur_group.
x_headerx-doc_type = 'X'.
x_headerx-vendor = 'X'.
x_headerx-purch_org = 'X'.
x_headerx-pur_group = 'X'.
ENDFORM. " header_details
FORM LINEITEM *
FORM lineitem .
v_temp1 = v_temp1 + 10.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
EXPORTING
input = v_temp1
IMPORTING
output = v_temp1.
MOVE v_temp1 TO x_item-po_item.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
EXPORTING
input = x_table-material
IMPORTING
output = x_table-material.
MOVE x_table-material TO x_item-material.
MOVE x_table-quantity TO x_item-quantity.
MOVE x_table-net_price TO x_item-net_price.
MOVE x_table-plant TO x_item-plant.
x_itemx-po_item = v_temp1.
x_itemx-material = 'X'.
x_itemx-quantity = 'X'.
x_itemx-net_price = 'X'.
x_itemx-plant = 'X'.
APPEND x_item TO it_item.
APPEND x_itemx TO it_itemx.
CLEAR: x_item, x_itemx.
ENDFORM. " lineitem1
FORM SCHEDULE *
FORM schedule .
MOVE x_table-delivery_date TO x_sched-delivery_date.
MOVE v_temp1 TO x_sched-po_item.
x_schedx-delivery_date = 'X'.
x_schedx-po_item = v_temp1.
APPEND x_sched TO it_sched.
APPEND x_schedx TO it_schedx.
CLEAR: x_sched, x_schedx.
ENDFORM. " schedule
FORM BAPICALL *
FORM bapicall .
CALL FUNCTION 'BAPI_PO_CREATE1'
EXPORTING
poheader = x_header
poheaderx = x_headerx
IMPORTING
exppurchaseorder = po_number
TABLES
return = it_return
poitem = it_item
poitemx = it_itemx
poschedule = it_sched
poschedulex = it_schedx.
IF po_number IS NOT INITIAL.
v_succsount = v_succsount + 1.
MOVE x_table-v_legacy TO x_alv-v_legs.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
ELSE.
v_failcount = v_failcount + 1.
MOVE x_table-v_legacy TO x_alv-v_legf.
MOVE x_table-v_legacy TO x_alv1-v_legf1.
LOOP AT it_return INTO x_return.
IF x_alv1-v_msg IS INITIAL.
MOVE x_return-message TO x_alv1-v_msg.
ELSE.
CONCATENATE x_alv1-v_msg x_return-message INTO x_alv1-v_msg SEPARATED BY space.
ENDIF.
ENDLOOP.
APPEND x_alv1 TO it_alv1.
CLEAR x_alv1.
ENDIF.
ENDFORM. " bapicall
FORM DISPLAY_ALV *
FORM display_alv .
PERFORM x_list_header.
PERFORM build_fieldcat CHANGING x_fieldcat.
x_repid2 = sy-repid.
x_event1-name = 'TOP_OF_PAGE'.
x_event1-form = 'TOP_OF_PAGE'.
APPEND x_event1 TO x_event.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
i_callback_program = x_repid2
is_layout = x_layout1
it_fieldcat = x_fieldcat
i_callback_user_command = 'USER_COMMAND'
i_callback_top_of_page = 'TOP_OF_PAGE'
i_save = 'A'
is_variant = x_variant1
it_events = x_event
TABLES
t_outtab = it_alv
EXCEPTIONS
program_error = 1
OTHERS = 2.
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. " display_master_data
FORM USER_COMMAND *
FORM user_command USING ucomm LIKE sy-ucomm selfield
TYPE slis_selfield.
READ TABLE it_alv INTO x_alv INDEX selfield-tabindex.
CLEAR : x_alv2,it_alv2[].
LOOP AT it_alv1 INTO x_alv1 WHERE v_legf1 = x_alv-v_legf.
x_alv2 = x_alv1.
APPEND x_alv2 TO it_alv2 .
ENDLOOP.
DATA : it_fieldcat TYPE slis_t_fieldcat_alv.
DATA : x3_fieldcat LIKE LINE OF it_fieldcat.
CLEAR : x3_fieldcat,it_fieldcat[].
CLEAR x3_fieldcat.
x3_fieldcat-col_pos = '1'.
x3_fieldcat-fieldname = 'V_LEGF1'.
x3_fieldcat-reptext_ddic = text-111.
x3_fieldcat-ref_tabname = 'IT_ALV2'.
APPEND x3_fieldcat TO it_fieldcat.
CLEAR x3_fieldcat.
CLEAR x3_fieldcat.
x3_fieldcat-col_pos = '1'.
x3_fieldcat-fieldname = 'V_MSG'.
x3_fieldcat-reptext_ddic = text-112.
x3_fieldcat-ref_tabname = 'IT_ALV2'.
APPEND x3_fieldcat TO it_fieldcat.
CLEAR x3_fieldcat.
x_layout1-colwidth_optimize = 'X'.
x_layout1-zebra = 'X'.
IF it_alv2[] IS NOT INITIAL.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
i_callback_program = x_repid2
is_layout = x_layout1
it_fieldcat = it_fieldcat
i_save = 'A'
i_callback_top_of_page = 'TOP'
is_variant = x_variant1
it_events = x_event
TABLES
t_outtab = it_alv2
EXCEPTIONS
program_error = 1
OTHERS = 2.
ENDIF.
ENDFORM.
FORM USER_COMMAND *
FORM top.
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
EXPORTING
it_list_commentary = 'Commentry'.
ENDFORM.
FORM BUILD_FIELDCAT *
FORM build_fieldcat CHANGING et_fieldcat TYPE slis_t_fieldcat_alv.
DATA: x1_fieldcat TYPE slis_fieldcat_alv.
CLEAR x1_fieldcat.
x1_fieldcat-col_pos = '1'.
x1_fieldcat-fieldname = 'V_LEGS'.
x1_fieldcat-reptext_ddic = text-108.
x1_fieldcat-ref_tabname = 'IT_ALV'.
APPEND x1_fieldcat TO et_fieldcat.
CLEAR x1_fieldcat.
x1_fieldcat-col_pos = '2'.
x1_fieldcat-fieldname = 'SUCCESS'.
x1_fieldcat-key = 'X'.
x1_fieldcat-reptext_ddic = text-109.
x1_fieldcat-ref_tabname = 'IT_ALV'.
APPEND x1_fieldcat TO et_fieldcat.
CLEAR x1_fieldcat.
x1_fieldcat-col_pos = '3'.
x1_fieldcat-fieldname = 'V_LEGF'.
x1_fieldcat-key = 'X'.
x1_fieldcat-reptext_ddic = text-110.
x1_fieldcat-ref_tabname = 'IT_ALV'.
APPEND x1_fieldcat TO et_fieldcat.
CLEAR x1_fieldcat.
ENDFORM. " build_fieldcat
FORM BUILD_LIST_HEADER *
FORM x_list_header.
DATA: x_list_header1 TYPE slis_listheader.
*-----List Header: type H
CLEAR x_list_header1 .
x_list_header1-typ = 'H'.
x_list_header1-info = text-105.
APPEND x_list_header1 TO x_list_header.
*-----List Key: type S
x_list_header1-typ = 'S'.
x_list_header1-key = text-106.
x_list_header1-info = v_total.
APPEND x_list_header1 TO x_list_header.
*-----List Key: Type S
CLEAR x_list_header1 .
x_list_header1-typ = 'S'.
x_list_header1-key = text-107.
x_list_header1-info = v_succsount.
APPEND x_list_header1 TO x_list_header.
ENDFORM. " build_list_header
FORM TOP_OF_PAGE *
FORM top_of_page.
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
EXPORTING
it_list_commentary = x_list_header.
ENDFORM. " TOP_OF_PAGE

How to associate Ship-To-Party to a Sold-To-Party using BAPI

Similar Messages

Maybe you are looking for