KOMK Fields not displaying values in sales order.
Hi all,
I have created an additional tab for VA01,02 and 03. I have added fields from VBAP table and KOMK structure.
Now fields added from KOMK structure are displaying empty fields(no value). The fields areVAT REG NO (KOMK-stceg) and Tax Code (KONP-MWSK1).
i have added fields with same name, so i have not coded anything. Do i need to code something for these fields?
Please suggest the possible solution.
Thanks in advance for your suggestions.
Regards,
NarsiReddy cheruku.
Hi Edgar Soares,
Thanks for your reply,
Yes you are right, i am using BADI_SLS_ITEM_SCR_CUS.
now i have added KNA1-STCEG to screen and in PBO module i coded as follows.
(In top include i declared Tables kna1 and Tables VBAK.)
data vat type kna1-stceg.
data wa type kna1.
SELECT SINGLE * from kna1 INTO wa.
vat = wa-stceg.
But it is not displaying Vat reg num on screen only displaying empty field.
Please suggest where i went wrong.
Thanks & Regards,
NarsiReddy Cheruku.
Similar Messages
-
He material is not displayed as valuated Sale Order Stock
Sale Order has been created and MRP execution is done at MD04.
The Sale Order is released as Production Order.
But when I am executing T Code MBBS I am getting error message syaing
The material is not displayed as valuated Sale Order Stock.
Diagnosis
The system has not found any stock that satisfies the selection criteria entered.
Possible reasons for this are:
The material does not exist. Have you entered the right material number?
Your selection is too restrictive. The system was not able to find any stock that satisfies all selection criteria.
The stock balance is zero.
Procedure
Check all the selection criteria you entered.
Stock overview has displayed enough stock for material.
Please adivse me how Material can be displayed as valuated Sale Order Stock at MBBS.
RegardsHi,
Check whether the Production order execution is done and any GR has been done against the Order.
Once the above is done, check in MBBS, the stock will sit in the Valuated SO stock.
Even wait for any other replies.
Thanks & Regards,
Ravi Kumar -
Different field mode(display/change) in sales order payment terms (VA02)
Hello All,
In the VA02 transaction, when we are changing the sales orders, in the billing document of that material shows different modes for different fields.
VA02->DOUBLE CLICK ON THE MATERIAL->BILLING DOCUMENT->FIELD PAYMENT TERMS.
For some orders, field is in display mode and for some orders, it is in changeable mode.
Could anyone please let me know about this..?
thanks and regards,
MERVINDear Jignesh
As you would be aware Payment Terms will flow in SO both at header level and at item level.
So in order to control the item level changes, go to VOV7, select the item category and untick the box [Business Item] By doing so, whatever header level datas flows into SO, that will be copied to item level also and you will be controlling the changes at item level and end users cannot make changes at item level.
Now you have to control at header level for which you have to apply User exits in the program MV45AFZZ - USEREXIT_MOVE_FIELD_TO_VBAK
thanks
G. Lakshmipathi -
Net value in billing doc not matching as in sales order
Hi,
I have a scenario wherein the net value in billing document does not match as in the sales order for 2 item categories maintained in the sales order. The net value in sales order has one line item category as 10 and the other as 20 but the same is not picked in billing document.
Any pointers?1. Check the copy control setting at item level for Pricing type.
2. Check the pricing procedure in sales order type & Billing type. Is it same or different.
3. Possibily the condition valuemay have been changed manually in Sales order or Billing Document type.
4. Check Document Pricing procedure in sales order type & Billing type. is it same or Different. If it is blank in Billing type, then it will consider the one maintained in sales order type.
The above are the possibilities,
Regards,
Rajesh Banka
Hope it help to resolve your issue. -
Pricing amount and condition value in sales order
Hi all,
I have noticed for a sales order we are not able to see condition type amount, condition value in sales order even though it shows net price finaly ofr a sales order. Not even able to select the condition lines.
To be specific not able to find value in field KBETR - amount column and KWERT - condition value column
When we go to sales order line item and select condition tab, do see value displayed in Amount and Condition column. Is there are specific reason it is doing visa vis in our production we see both values.
Advise what could be the reason value not getting displayed in Amount and Condition value column.
thanksIt is due to auth for specific columns we have solved the problem.
-
Not able to create sales order using BAPI - BAPI_SALESORDER_CREATEFROMDAT2
Hi Experts,
I am not able to create sales order . I am using BAPI - BAPI_SALESORDER_CREATEFROMDAT2
to create sales order .I am passing external sales order number to the parameter
SALESDOCUMENTIN.
I am getting following error.
"524 |Only quantity 1 EA is allowed (Item 00001"
Here EA is UOM(Unit of measurement).
Below is the sample program through which i am trying to create the sales order.
*& Report ZSDC_SALES_TEST
report zsdc_sales_test.
*DATA: wa_bapi_header TYPE bapisdhd1.
Include Name - ZSDC_SALES_ORD_UPLOAD_TOP
Program Name - ZSDC_SALES_ORD_UPLOAD_1393
Program Title - Include for Data Declaration and selection screen
Created by - Lalitha W
Created on - 18-Nov-2008
Object ID - SD_C_1393_SALES_ORDER_UPLOAD
Request Id - SD3K905579
Description - This is a common INCLUDE for data declarations and
*selection screen details.
HISTORY
Date |Developer |Req by | Description |Reference ID
| | | |
| | | |
TYPE-POOLS
*TYPE-POOLS: truxs, abap, slis.
TABLES
*TABLES: t100.
TYPES
types:begin of ty_header,
auart(4) type c, " Sales Order Type
vkorg(4) type c, " Sales Organization
vtweg(2) type c, " Distrubution Channel
spart(2) type c, " Division
kunnr_1(10) type c, " Sold to Party
kunnr_2(10) type c, " Ship to Party
augru(3) type c, " Order Reason
bstkd(35) type c, " PO Number
bstdk(10) type c, " PO Date
ketdat(10) type c, " Required Delivery Date
zterm(4) type c, " Payment Terms
inco1(3) type c, " Inco Terms -1
inco2(28) type c, " Inco Terms -2
prsdt(10) type c, " pricing date
waerk(5) type c, " Document Currency
vkbur(4) type c, " Sales Office
vkgrp(3) type c, " Sales group
pltyp(2) type c, " Price List type
kdgrp(2) type c, " Customer Group
bstkd_e(35) type c, " Ship-to-party PO number
submi(10) type c, " Collective Number
bname(35) type c, " Name
ihrez(12) type c, " Your Reference
kschl_1(4) type c, " Condition Type
kbetr_1(11) type c, " Amount
kschl_2(4) type c, " Condition Type
kbetr_2(11) type c, " Amount
kschl_3(4) type c, " Condition Type
kbetr_3(11) type c, " Amount
partner_1(25) TYPE c, " Partner(Bill To Party Number)
partner_2(25) TYPE c, " Partner(Payer Number)
partner_3(25) TYPE c, " Partner(Sales Responsible Number)
partner_4(25) TYPE c, " Partner(Order admin)
partner_5(25) TYPE c, " Partner(Contact person)
partner_1(10) type c, " Partner(Bill To Party Number)
partner_2(10) type c, " Partner(Payer Number)
partner_3(10) type c, " Partner(Sales Responsible Number)
partner_4(10) type c, " Partner(Order admin)
partner_5(10) type c, " Partner(Contact person)
tdspras_1(2) type c,
text_1(500) type c, " Text Before Items Z012
tdspras_2(2) type c,
text_2(500) type c, " Invocie Up Z034
tdspras_3(2) type c,
text_3(500) type c, " Invocie Down Z035
tdspras_4(2) type c,
text_4(500) type c, " Customer Reference Continue Z018
tdspras_5(2) type c,
text_5(500) type c, " Dispatch Marks/ Order Z019
tdspras_6(2) type c,
text_6(500) type c, " Ordered By Z003
tdspras_7(2) type c,
text_7(500) type c, " Sales Parameters Z002
kvgr1(3) type c, " Industry
kvgr2(3) type c, " customer BU
end of ty_header.
types: begin of ty_item,
bstkd(35) type c, " PO Number
bstdk(10) type c, " PO Date
bstkd_e(35) type c, " Ship-to-party PO number
posnr(6) type c, " POSTION NUMBER
matnr(18) type c, " Material Number
kwmeng(18) type c, " Order Quantity
pstyv(4) type c, " Sales doc. item categ
kursk(18) type c, " EXCHANGE RATE****
ffprf(8) type c, " DIP PROFILE
werks(4) type c, " Delivering Plant
vstel(4) type c, " SHIPPING POINT
lgort(4) type c, " STORAGE LOCATION
route(6) type c, " Route
kurrf(18) type c, " EXCHANGE RATE-FI
ntgew(18) type c, " Net Weight
brgew(18) type c, " Gross Weight
gewei(3) type c, " Weight Unit
prctr(10) type c, " profit center
abgrs(6) type c, " RESULT ANALYSIS KEY
kalsm_k(4) type c, " COSTING SHEET
kschl_1(4) type c, " Condition Type
kbetr_1(11) type c, " Amount
kschl_2(4) type c, " Condition Type
kbetr_2(11) type c, " Amount
kschl_3(4) type c, " Condition Type
kbetr_3(11) type c, " Amount
text_1(500) type c, " material Text 0001
tdspras_1(1) type c,
text_2(500) type c, " Pr Text 9001
tdspras_2(1) type c,
end of ty_item.
types: begin of ty_schedule_line,
bstkd(35) type c, "PO number
bstdk(10) type c, "PO date
bstkd_e(35) type c, "Ship-to-party PO number
posnr(6) type c, "sales doc.Item
etdat(10) type c, "Schedule line date
wmeng(2) type c, "Order Quantity
end of ty_schedule_line.
types: begin of ty_err ,
auart(4) type c, " Sales Order Type
vkorg(4) type c, " Sales Organization
vtweg(2) type c, " Distrubution Channel
spart(2) type c, " Division
kunnr_1(10) type c, " Sold to Party
kunnr_2(10) type c, " Ship to Party
augru(3) type c, " Order Reason
bstkd(35) type c, " PO Number
bstdk(10) type c, " PO Date
ketdat(10) type c, " Required Delivery Date
zterm(4) type c, " Payment Terms
inco1(3) type c, " Inco Terms -1
inco2(28) type c, " Inco Terms -2
prsdt(10) type c, " pricing date
waerk(5) type c, " Document Currency
vkbur(2) type c, " Sales Office
vkgrp(3) type c, " Sales group
pltyp(2) type c, " Price List type
kdgrp(2) type c, " Customer Group
bstkd_e(35) type c, " Ship-to-party PO number
submi(10) type c, " Collective Number
bname(35) type c, " Name
ihrez(12) type c, " Your Reference
kschl_1(4) type c, " Condition Type
kbetr_1(11) type c, " Amount
kschl_2(4) type c, " Condition Type
kbetr_2(11) type c, " Amount
kschl_3(4) type c, " Condition Type
kbetr_3(11) type c, " Amount
partner_1(25) type c, " Partner(Bill To Party Number)
partner_2(25) type c, " Partner(Payer Number)
partner_3(25) type c, " Partner(Sales Responsible Number)
partner_4(25) type c, " Partner(Order admin)
partner_5(25) type c, " Partner(Contact person)
tdspras_1(2) type c,
text_1(500) type c, " Text Before Items Z012
tdspras_2(2) type c,
text_2(500) type c, " Invocie Up Z034
tdspras_3(2) type c,
text_3(500) type c, " Invocie Down Z035
tdspras_4(2) type c,
text_4(500) type c, " Customer Reference Continue Z018
tdspras_5(2) type c,
text_5(500) type c, " Dispatch Marks/ Order Z019
tdspras_6(2) type c,
text_6(500) type c, " Ordered By Z003
tdspras_7(2) type c,
text_7(500) type c, " Sales Parameters Z002
kvgr1(3) type c, " Industry
kvgr2(3) type c, " customer BU
message(600) type c,
end of ty_err.
types: begin of ty_t685a,
kschl type kschl,
krech type krech,
end of ty_t685a.
INTERNAL TABLES
***header
data: g_krech_1(4) type c, " Calculation type for condition
g_krech_2(4) type c, " Calculation type for condition
g_krech_3(4) type c. " Calculation type for condition
g_krech_4(4) TYPE c, " Calculation type for condition
g_krech_5(4) TYPE c, " Calculation type for condition
g_krech_6(4) TYPE c, " Calculation type for condition
g_krech_7(4) TYPE c, " Calculation type for condition
g_krech_8(4) TYPE c, " Calculation type for condition
g_krech_9(4) TYPE c, " Calculation type for condition
g_krech_10(4) TYPE c, " Calculation type for condition
g_krech_11(4) TYPE c, " Calculation type for condition
g_krech_12(4) TYPE c, " Calculation type for condition
g_krech_13(4) TYPE c, " Calculation type for condition
g_krech_14(4) TYPE c, " Calculation type for condition
g_krech_15(4) TYPE c, " Calculation type for condition
g_krech_16(4) TYPE c, " Calculation type for condition
g_krech_17(4) TYPE c, " Calculation type for condition
g_krech_18(4) TYPE c, " Calculation type for condition
g_krech_19(4) TYPE c, " Calculation type for condition
g_krech_20(4) TYPE c. " Calculation type for condition
Items
data: g_krech_item_1(4) type c, " Calculation type for condition
g_krech_item_2(4) type c, " Calculation type for condition
g_krech_item_3(4) type c. " Calculation type for condition
g_krech_item_4(4) TYPE c, " Calculation type for condition
g_krech_item_5(4) TYPE c, " Calculation type for condition
g_krech_item_6(4) TYPE c, " Calculation type for condition
g_krech_item_7(4) TYPE c, " Calculation type for condition
g_krech_item_8(4) TYPE c, " Calculation type for condition
g_krech_item_9(4) TYPE c, " Calculation type for condition
g_krech_item_10(4) TYPE c, " Calculation type for condition
g_krech_item_11(4) TYPE c, " Calculation type for condition
g_krech_item_12(4) TYPE c, " Calculation type for condition
g_krech_item_13(4) TYPE c, " Calculation type for condition
g_krech_item_14(4) TYPE c, " Calculation type for condition
g_krech_item_15(4) TYPE c, " Calculation type for condition
g_krech_item_16(4) TYPE c. " Calculation type for condition
data: it_t685a type standard table of ty_t685a.
data: wa_bapi_header type bapisdhd1,
wa_bapi_headerx TYPE bapisdhd1x,
it_bapi_item type table of bapisditm,
it_bapi_itemx TYPE TABLE OF bapisditmx,
it_bapi_cond type table of bapicond,
it_bapi_condx TYPE TABLE OF bapicondx,
it_bapi_partner type table of bapiparnr,
it_bapi_shdl type table of bapischdl,
it_bapi_shdlx TYPE TABLE OF bapischdlx,
it_bapi_order_text type TABLE OF BAPISDTEXT,
it_bapireturn type table of bapiret2.
data: wa_bapi_item like line of it_bapi_item,
wa_bapi_itemx LIKE LINE OF it_bapi_itemx,
wa_bapi_cond like line of it_bapi_cond,
wa_bapi_condx LIKE LINE OF it_bapi_condx,
wa_bapi_partner like line of it_bapi_partner,
wa_bapi_shdl like line of it_bapi_shdl,
wa_bapi_shdlx LIKE LINE OF it_bapi_shdlx,
wa_bapi_order_text like LINE OF it_bapi_order_text,
wa_bapireturn like line of it_bapireturn.
*DATA: zmode(1) VALUE 'N'.
data: it_header type standard table of ty_header.
*DATA: it_temp_header TYPE STANDARD TABLE OF ty_header.
data: it_item type standard table of ty_item.
*DATA: it_temp_item TYPE STANDARD TABLE OF ty_item.
data: it_err type standard table of ty_err.
data: it_fline1 type standard table of tline,
wa_fline1 type tline.
data: it_thead1 type thead.
data: it_fline2 type standard table of tline,
wa_fline2 type tline.
data: it_thead2 type thead.
data: it_fline3 type standard table of tline,
wa_fline3 type tline.
data: it_thead3 type thead.
data: it_fline4 type standard table of tline,
wa_fline4 type tline.
data: it_thead4 type thead.
data: it_fline5 type standard table of tline,
wa_fline5 type tline.
data: it_thead5 type thead.
data: wa_header like line of it_header,
wa_item like line of it_item,
wa_err type ty_err,
wa_bill LIKE LINE OF it_bill,
wa_bill1 LIKE LINE OF it_bill,
wa_iterr like line of it_err,
wa_t685a like line of it_t685a.
wa_bill_item TYPE ty_bill_item.
data: it_schedule_line type standard table of ty_schedule_line,
wa_schedule_line type ty_schedule_line.
data: sales_order_no type bapivbeln-vbeln.
data: ext_sales_order_no type bapivbeln-vbeln.
Variable to be used to separate the fields which are concatenated by a
runtime character
*DATA: g_tabchar(1) TYPE c VALUE cl_abap_char_utilities=>horizontal_tab.
*DATA: wa_truxs_t_text_data TYPE truxs_t_text_data.
*DATA: g_filename TYPE string,
g_path TYPE string,
g_fullpath TYPE string,
g_user_action TYPE i,
g_file_encoding TYPE abap_encoding.
*DATA : g_text(8192),
data : g_mstring1(100) type c,
g_mstring2(100) type c,
g_mstring3(100) type c,
g_mstring4(100) type c,
g_mstring5(100) type c.
data: g_count1 type ebelp,
g_str_count1(6) type c.
data: g_count type ebelp,
g_str_count(6) type c.
*DATA: f_subrc LIKE sy-subrc,
f_subrc1 LIKE sy-subrc,
f_error(500) TYPE c,
item1(27) TYPE c,
item2(27) TYPE c,
item3(27) TYPE c,
item4(27) TYPE c,
i TYPE ekpo-ebelp.
*DATA: g_billplan_header TYPE c,
g_billplan_item TYPE c.
data : g_external_so type vbak-vbeln. "SO
SELECTION-SCREEN
selection-screen begin of block frame1 with frame title text-001 .
parameters:p_file1 type rlgrap-filename, "OBLIGATORY, "Header data.
p_file2 type rlgrap-filename, "OBLIGATORY, "Item Data.
p_file3 type rlgrap-filename, "Schedule line.
p_file4 type rlgrap-filename ."OBLIGATORY. "Error file.
selection-screen end of block frame1.
start-of-selection.
wa_bapi_header-doc_type = 'Z0MX'. "order type
wa_bapi_header-sales_org = '0130'."sales org
wa_bapi_header-distr_chan = '13'. "distr channel
wa_bapi_header-division = '13'. "division
Old code from copied program
wa_bapi_header-purch_no_s = wa_header-kunnr_2. " Ship to party
New code as required in Finland project
We are using to Header ->Order Tab -> Ship to Party -> Purchase order no (BSTKD_E) to store Old legacy SO number
wa_bapi_header-purch_no_s = 'MX100443'. "External SO i.e Old legacey SO number
wa_bapi_header-ref_1_s = '0000666666'. "Sold to party
wa_bapi_header-ord_reason = wa_header-augru.
wa_bapi_header-purch_no_c = 'ddr1234'. " PO number
wa_bapi_header-purch_date = sy-datum. " PO date
wa_bapi_header-req_date_h = sy-datum. " Required Delivery Date
wa_bapi_header-pmnttrms = '01'. " Payment Terms
wa_bapi_header-incoterms1 = wa_header-inco1.
wa_bapi_header-incoterms2 = wa_header-inco2.
wa_bapi_header-price_date = wa_header-prsdt. " Pricing date
wa_bapi_header-currency = wa_header-waerk. " Document Currency
wa_bapi_header-sales_grp = wa_header-vkgrp. " Sales group
wa_bapi_header-price_list = wa_header-pltyp. " Price list type
wa_bapi_header-cust_group = wa_header-kdgrp. " Cust Group
wa_bapi_header-ship_type = wa_header-vsart. " Shipping Type
wa_bapi_header-purch_no_s = wa_header-bstkd_e. " Ship-to-party po number
wa_bapi_header-collect_no = wa_header-submi. " Collective No.
wa_bapi_header-name = wa_header-bname. " Name
wa_bapi_header-ref_1 = wa_header-ihrez. " Your Reference
wa_bapi_header-cust_grp1 = wa_header-kvgr1. " Industry
wa_bapi_header-cust_grp2 = wa_header-kvgr2. " Customer BU
*ENDFORM. " f_header
IF wa_header-partner_1 IS NOT INITIAL.
wa_bapi_partner-partn_role = 'AG'.
wa_bapi_partner-partn_numb = '0000666666'.
wa_bapi_partner-itm_number = '000000'.
append wa_bapi_partner to it_bapi_partner.
clear wa_bapi_partner.
ENDIF.
call function 'CONVERSION_EXIT_ALPHA_INPUT'
exporting
input = wa_header-partner_2
importing
output = wa_header-partner_2.
IF wa_header-partner_2 IS NOT INITIAL.
wa_bapi_partner-partn_role = 'WE'.
wa_bapi_partner-partn_numb = '0000666666'.
wa_bapi_partner-itm_number = '000000'.
append wa_bapi_partner to it_bapi_partner.
clear wa_bapi_partner.
ENDIF.
perform f_item.
data : order_items_inx type table of bapisditmx with header line.
order_items_inx-material = 'X'. "
order_items_inx-target_qty = 'X'. "
order_items_inx-comp_quant = 'X'. "
order_items_inx-trgqty_den = 'X'.
order_items_inx-rnddlv_qty = 'X'.
order_items_inx-updateflag = 'I'.
order_items_inx-target_qu = 'X'.
order_items_inx-plant = 'X'. "
append order_items_inx.
call function 'BAPI_SALESORDER_CREATEFROMDAT2'
exporting
salesdocumentin = 'MX11111152'
order_header_in = wa_bapi_header
order_header_inx = wa_bapi_headerx
importing
salesdocument = sales_order_no
tables
return = it_bapireturn
order_items_in = it_bapi_item
order_items_inx = order_items_inx
order_partners = it_bapi_partner
order_conditions_in = it_bapi_cond.
if sy-subrc is initial.
commit work.
endif.
*& Form f_item
text
form f_item .
call function 'CONVERSION_EXIT_ALPHA_INPUT'
exporting
input = wa_item-posnr
importing
output = wa_item-posnr.
wa_item-posnr = '000010'.
IF sy-subrc EQ 0. "IS INITIAL.
move wa_item-posnr to g_str_count."commented out by shakti
ENDIF.
wa_bapi_item-itm_number = wa_item-posnr. " Line item
WA_BAPI_ITEM-PO_ITM_NO = WA_ITEM-EBELP.
wa_bapi_item-division = wa_item-spart.
wa_bapi_item-purch_no_c = 'ddr1234'. " po number
wa_bapi_item-purch_date = sy-datum. " po date
wa_bapi_item-purch_no_s = 'MX11111112'. " Ship-to-party po number
wa_item-matnr = 'MAXIMO_SERVICE'.
call function 'CONVERSION_EXIT_MATN1_INPUT'
exporting
input = wa_item-matnr
importing
output = wa_item-matnr
exceptions
length_error = 1
others = 2.
if sy-subrc is initial.
wa_bapi_item-material = wa_item-matnr. "material
endif.
wa_bapi_item-target_qty = '1'. " Order qty
wa_bapi_item-comp_quant = '1'.
wa_bapi_item-target_qu = 'EA'.
wa_bapi_item-fixed_quan = '1'.
wa_bapi_item-comp_quant = wa_item-kwmeng.
wa_bapi_item-trgqty_den = '1'.
wa_bapi_item-rnddlv_qty = wa_item-kwmeng.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
EXPORTING
input = wa_item-ps_psp_pnr
IMPORTING
output = wa_item-ps_psp_pnr.
IF sy-subrc = 0.
wa_bapi_item-wbs_elem = wa_item-ps_psp_pnr.
ENDIF.
wa_bapi_item-item_categ = 'ZMAX'.
wa_bapi_item-ex_rate_fi = wa_item-kurrf.
wa_bapi_item-dli_profil = wa_item-ffprf. " Dynamic item processor profile
wa_bapi_item-route = wa_item-route. " route
wa_bapi_item-exchg_rate = wa_item-kursk.
wa_bapi_item-plant = '2090'. " Plant
wa_bapi_item-ship_point = 'FN11'. " Shipping point
wa_bapi_item-store_loc = wa_item-lgort. " stg loc
REPLACE ALL OCCURRENCES OF ',' IN wa_item-ntgew WITH '.'.
REPLACE ALL OCCURRENCES OF ',' IN wa_item-brgew WITH '.'.
wa_bapi_item-net_weight = wa_item-ntgew. "
wa_bapi_item-gross_wght = wa_item-brgew. "
call function 'CONVERSION_EXIT_CUNIT_INPUT'
exporting
input = wa_item-gewei
language = sy-langu
importing
output = wa_item-gewei.
EXCEPTIONS
unit_not_found = 1
OTHERS = 2.
IF sy-subrc <> 0.
ENDIF.
wa_bapi_item-untof_wght = 'KG'. " weight unit
replace all occurrences of ',' in wa_item-kursk with '.'.
replace all occurrences of ',' in wa_item-kurrf with '.'.
wa_bapi_item-profit_ctr = wa_item-prctr. " Profit center
wa_bapi_item-resanalkey = wa_item-abgrs. " RESULT ANALYSIS KEY
wa_bapi_item-cstg_sheet = wa_item-kalsm_k. " COSTING SHEET
append wa_bapi_item to it_bapi_item.
endform. " f_item
Thanks & regards,
Chetansee the following to create sales order:-
*& Report ZSALESORDER
*&DEVELOPED BY JANI KRUPA 4.10.2008
REPORT ZSALESORDER.
Parameters
Sales document type
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text FOR FIELD p_auart.
PARAMETERS: p_auart TYPE auart OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Sales organization
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text1 FOR FIELD p_vkorg.
PARAMETERS: p_vkorg TYPE vkorg OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Distribution channel
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text2 FOR FIELD p_vtweg.
PARAMETERS: p_vtweg TYPE vtweg OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Division.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text3 FOR FIELD p_spart.
PARAMETERS: p_spart TYPE spart OBLIGATORY.
SELECTION-SCREEN END OF LINE.
SKIP 1.
Sold-to
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text4 FOR FIELD p_sold.
PARAMETERS: p_sold TYPE kunnr OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Ship-to
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text5 FOR FIELD p_ship.
PARAMETERS: p_ship TYPE kunnr OBLIGATORY.
SELECTION-SCREEN END OF LINE.
SKIP 1.
Material
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text6 FOR FIELD p_matnr.
PARAMETERS: p_matnr TYPE matnr OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Quantity.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text7 FOR FIELD p_menge.
PARAMETERS: p_menge TYPE kwmeng OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Plant
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text9 FOR FIELD p_plant.
PARAMETERS: p_plant TYPE werks_d .
SELECTION-SCREEN END OF LINE.
Complete Deliver
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text10 FOR FIELD p_autlf.
PARAMETERS: p_autlf TYPE autlf DEFAULT 'X'.
SELECTION-SCREEN END OF LINE.
Data declarations.
DATA: v_vbeln LIKE vbak-vbeln.
DATA: header LIKE bapisdhead1.
DATA: headerx LIKE bapisdhead1x.
DATA: item LIKE bapisditem OCCURS 0 WITH HEADER LINE.
DATA: itemx LIKE bapisditemx OCCURS 0 WITH HEADER LINE.
DATA: partner LIKE bapipartnr OCCURS 0 WITH HEADER LINE.
DATA: return LIKE bapiret2 OCCURS 0 WITH HEADER LINE.
DATA: lt_schedules_inx TYPE STANDARD TABLE OF bapischdlx
WITH HEADER LINE.
DATA: lt_schedules_in TYPE STANDARD TABLE OF bapischdl
WITH HEADER LINE.
DATA: lt_schedules_ink TYPE STANDARD TABLE OF bapisdhead1
WITH HEADER LINE.
Initialization.
INITIALIZATION.
v_text = 'Order type'.
v_text1 = 'Sales Org'.
v_text2 = 'Distribution channel'.
v_text3 = 'Division'.
v_text4 = 'Sold-to'.
v_text5 = 'Ship-to'.
v_text6 = 'Material'.
v_text7 = 'Quantity'.
v_text9 = 'Plant'.
v_text10 = 'Complete delivery'.
Start-of-selection.
START-OF-SELECTION.
Header data
Sales document type
header-doc_type = p_auart.
headerx-doc_type = 'X'.
Sales organization
header-sales_org = p_vkorg.
headerx-sales_org = 'X'.
Distribution channel
header-distr_chan = p_vtweg.
headerx-distr_chan = 'X'.
Division
header-division = p_spart.
headerx-division = 'X'.
headerx-updateflag = 'I'.
*Complete delivery
header-COMPL_DLV = p_autlf.
header-COMPL_DLV = 'X'.
Partner data
Sold to
partner-partn_role = 'AG'.
partner-partn_numb = p_sold.
APPEND partner.
Ship to
partner-partn_role = 'WE'.
partner-partn_numb = p_ship.
APPEND partner.
ITEM DATA
itemx-updateflag = 'I'.
Line item number.
item-itm_number = '000010'.
itemx-itm_number = 'X'.
Material
item-material = p_matnr.
itemx-material = 'X'.
Plant
item-plant = p_plant.
itemx-plant = 'X'.
Quantity
item-target_qty = p_menge.
itemx-target_qty = 'X'.
item category
itemx-ITEM_CATEG = 'X'.
APPEND item.
APPEND itemx.
ITEM DATA
itemx-updateflag = 'I'.
Line item number.
item-itm_number = '000020'.
itemx-itm_number = 'X'.
Material
item-material = p_matnr.
itemx-material = 'X'.
Plant
item-plant = p_plant.
itemx-plant = 'X'.
Quantity
item-target_qty = p_menge.
itemx-target_qty = 'X'.
APPEND item.
APPEND itemx.
Fill schedule lines
lt_schedules_in-itm_number = '000010'.
lt_schedules_in-sched_line = '0001'.
lt_schedules_in-req_qty = p_menge.
APPEND lt_schedules_in.
Fill schedule line flags
lt_schedules_inx-itm_number = '000010'.
lt_schedules_inx-sched_line = '0001'.
lt_schedules_inx-updateflag = 'X'.
lt_schedules_inx-req_qty = 'X'.
APPEND lt_schedules_inx.
Fill schedule lines
lt_schedules_in-itm_number = '000020'.
lt_schedules_in-sched_line = '0001'.
lt_schedules_in-req_qty = p_menge.
APPEND lt_schedules_in.
Fill schedule line flags
lt_schedules_inx-itm_number = '000020'.
lt_schedules_inx-sched_line = '0001'.
lt_schedules_inx-updateflag = 'X'.
lt_schedules_inx-req_qty = 'X'.
APPEND lt_schedules_inx.
Call the BAPI to create the sales order.
CALL FUNCTION 'BAPI_SALESDOCU_CREATEFROMDATA1'
EXPORTING
sales_header_in = header
sales_header_inx = headerx
IMPORTING
salesdocument_ex = v_vbeln
TABLES
return = return
sales_items_in = item
sales_items_inx = itemx
sales_schedules_in = lt_schedules_in
sales_schedules_inx = lt_schedules_inx
sales_partners = partner.
Check the return table.
LOOP AT return WHERE type = 'E' OR type = 'A'.
EXIT.
ENDLOOP.
IF sy-subrc = 0.
WRITE: / 'Error in creating document'.
ELSE.
Commit the work.
COMMIT WORK AND WAIT.
WRITE: / 'Document ', v_vbeln, ' created'.
ENDIF. -
Delivery note with reference to sales order - 0 quantity items
Hi all,
our system allows items with quantity 0 to be created in delivery notes with reference to sales orders.
This happens when some items in a sales order are out of stock while others are availiable. The unavailable items are included in the delivery note, but have quantity 0.
The requirement is to eliminate this behavior and to create delivery notes with availiable items only.
I would be grateful for any advice how to realise this.
Best regards, AndreasMake the necessary configuration i.e. Check quantity 0 field value should be maintained as B in the respective delivery item category using transaction 0VLP.
Regards,
GSL. -
Net Value in Sales order item and header URGENT
Hi experts
In some sales orders the net value is not shown but it is available in PR00 condition.
Where should i check pricing proceedure or copy control,
In the same sales order type i.e ZRP other sales orders are having net value,
this sales order is created with reference to sales order type RE.
Pls guide where to check and what correction needs to be done.
Thank u in advance.
regards
SMHi,
Pricing procedure in tcode V/08, check the field 'SubTo'.
Copy control in tcodes VTFA (between SO and invoices).Check the field 'pricing type' for conditions.
I hope this help you,
Regards,
Eduardo -
Discount Condn Type changeable in Quotation and Display Mode in Sales Order
Hi Friends,
There is requirement of having a Discount Condition Type to be in Changeable mode in Quotation and must not be in Changeable mode in Sales Order. That no user is allowed to change the discount value in Sales Order and whatever maintained in QT must be applcable for Sales Order till billing.
Would like to have functional possibilities. Guide me gurus.
Surya.Hi
Would you like your user who is making the sales order to view the pricing conditions or you would also like him to change certain conditions/values (Except for discount conditions) ?
If the above is applicable then in my suggestion you should go in for a Transaction Variant wherein you can either completely hide or make the pricing conditions in display only.
R/Sanjeev -
Creating a delivery note based on a sales order in SBO2005
Hi
I am using the diapi to create a delivery note based on a sales order. Everything works well apart from I have 3 user defined fields on the sales order lines, 2 numeric and one which is a combo box.
The 2 numeric values as copied across ok but the combo is not.
I don't know what the delivery number is as I guess SAP assigns that after I save the delivery note.
Can anyone help me with this please ?
Regards AndyHi Paul & Gilbert,
As you assumed, the docentry is created at the moment when you are saving the document.
The docentry for the last created document can be retrieved from the Company object. There are two alternative methods for this: GetNewObjectCode and GetNewObjectKey. Please see the DI API reference for more details. These are the only reliable way to get the last created docentry. A query might work nicely in 95% of the cases, but in a multi-user environment it will sooner or later produce incorrect results.
Henry -
VARIENT PRICING NOT REFLECTING IN MY SALES ORDER
Hello Gurus
I'm maintaining a varient condition type VA00 for varients in my pricing procedure and PROO for the main item in my pricing procedure, but in my sales order PR00 is reflecting where as VA00 is not reflecting. i'm maintaining the standard pricing procedure.
scenario:
Main item is Villa: PR00 is condition type
Varients: VA00 is condition type:
The following are the varients: Marble , Granite ,Tiles ,Wooden,
Maintined condition records for both main item as wellas varient item , but main item PR00 is showing in my sales order where as VA00 is not showing in my sales order conditions kindly help me where i'm missing
Thank you in advance
venkatDear Venkata,
Can you check and update few informations for our understanding:
1. Maintain Variants - VK30
2. Have you created Conditions Records for VA00 - VK11 (Case-sensitivie)
3. Go to, T. Code: V/06 and select Condition Type: VA00 and see the proper access sequence as VA00 and
Tab: Control Data 1
Field: Condition category as "O - Variant" is maintained or not.
If all up to this point, go to:
T. Code: CU50
There, from Pop-up Window, select for a characteristic. Select a value which has the VA00 condition defined for it. You will see a button with a Pricing symbol on it. Click on this and enter the characteristic value which is defined for the price. This creates the true "link" between the characteristic value and the Price record.
Best Regards,
Amit.
Note: I assume, things have been configured, properly in respective T. Codes: CT04, CL01, CU41 -
Quantity is not getting conformed in sales order
HI SD Gurus,
i have one issue we are not able to solve i need your help, it is very urgent,
My issue:we created sales order but quantity was not getting conformed is sales order even though we have enough stock
but it was consumed the stock in MD04,
we ran the SDRQCR21 program but issue is still exist,
1. we checked all the ATP configuration every thing is fine,
2.we replicated the scenario in quality it is working fine
3.we try simulated in production but not conformed the stock
4. total stock is in unrestricted only
5. no block in sales order
6. same material working fine with different plant
7. in same plant different materials working fine
available stock level in MMBE and MD04 is 330 qty unrestricted
sales order created for 165
then stock reduced in MD04 to 165,and sales order displayed in MD04 with quantity 165
but it was not conforming the schedules in sales order(with any dates)
I am requesting you to reply ASAP if any one faced the same scenario
BR,
CSHi CS,
Please check the stock availability in CO09. If CO09 shows available quantity as zero then the sales order quantity cannot be confirmed.
Please review SAP Note Number 89362 - No confirmation despite available quantity/stock for further information on this transaction.
You will also find further information in this document:
http://scn.sap.com/docs/DOC-58040
I hope this helps.
Kind regards,
Catherine -
Mass update exchange rate type (not rate) in open sales orders
Hi all,
Our requirement is to update the exchange rate type at sales order header (VBAK-KURST) for all open sales orders with a new type created. (Z001). This field does not appear in MASS transaction for sales orders despite being present in the structure MASSSDHEAD.
This field cannot be located even in VA02 transaction (I am not sure if standard SAP masks or shows this field at header; I also can't find any transaction variants assigned).
Can anyone suggest how this field can be updated for sales orders either individually or in mass mode.
Regards,
KC
SAP SDYou are correct in indicating that Exchange rate type field is not seen in Header data of sales order. I checked screen layouts for various screens for sales order data and this field is not suppressed. The only reason could be that this field is not used in sales order screens
If you are interested, you could also check in the following way
1. Go to SE11, enter database table as VBAK
2. Once inside data dictionary table, click where used list button, select programs and screens and execute
3. click continue (don't select background)
4. now you would have list of programs and screens, this table is used
5. now start another session and go to transaction SE51
6. indicate program name as SAPMV45A and screen numbers as listed in step 4. you can check all screen numbers to see whether Exchange rate type field is listed in sales order layout.
7. Of particular interest would be screen number 4311 as this contains Financial accounting data & 4303 Billing data
8. you can check screen layout for screen 4311 & 4303. you would see Exchange rate type field is not indicated.
9. in case you could find this field in any screen, you could ask your ABAP consultant to add this field in the layout screen.
Hope this answers your question -
Hi All,
Any one know how the system set net value in sales order item? (VBAP-NETWR)
I mean, what kind of condition type will be considered in net value calculation.
Thank youHi,
In Sales Order net value (NETWR) is always value before tax, it means the condition type determined before tax condition will be considered in sales order Net Value.
In other words if conditon type have a category defined as D-Tax and Cond. class as D- Taxes, the value of this condition type will not be considered in Net value.
regards
Vivek.
Edited by: Vievk Vardhan on Jan 7, 2010 2:00 PM -
How to make a field profit center mandatory in sales order?
Dear GURUS,
Please help in getting answer for following question.
How to make a field profit center mandatory in sales order?
With Regards
Sandeep D.Hi,
There are 2 ways to make profit center mandatory
1.Transaction Variant
2.Incompletion procedure
1.Transaction Variant
Step 1:Goto Tcode shd0 and input transaction as va01 and give name of transaction variant as ( example. zva01 ) and click on create or F5
Step 2.Then it takes you to sales order screen.Just click on enter untill you see profit center field.
Step 3.check the box required against profit center.
Step 4.click on save ( under a package name or as local object ) and exit
Step 5.Assign transaction variant to your sales order type through tcode v0v8.
2.Incompletion Procedure
You can add the field table-vbap,field- prctr,status-04,check-warning to your existing incompletion procedure Tcode- ova2 assigned to your order type in tcode vov8 and check the box - incomplete messeges for your order type through tcode vov8.
If incompletion procedure is not assigned to your order type than you have to create a new incompletion procedure and assign it to order type.
Maybe you are looking for
-
On my Powerbook G4 running OSX Panther, I just encoded a peice of video taken from a DVD -r I burned using my Panasonic DVD recording deck. Handbreak did the job, but I have noticed that during playback on my iPod there is a split second break in sou
-
Chose from list in internal error?
Hi expert i want to use chose from list from udf object. Private Sub LoadingCFL(ByVal oForm As SAPbouiCOM.Form) Try Dim oCFLs As SAPbouiCOM.ChooseFromListCollection 'Dim oCons As SAPbouiCOM.Conditions 'Di
-
Hi, How can I return only few required attributes in SPML response instead of the complete user data? For ex: My sample SPML soap request to add a user is given below: <?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://sche
-
I have recently changed my email address and cosequent apple ID when I went to buy Lion download the old email address comes up?
-
How to stop scrolling on screen
Hi all, I've created screen which is big enough for scrollbars to show up. Problem is that when user move down to change some field and he enforce PAI to being executed (by example by pressing F4), scroll is returning to it's initial position. How ca