Not able to create plnd order in prod view
Hi,
When I try to create an order using product view, it gives me an error message,
'Invalid product-location combination (pegging area), A product-location combination exists in the APO database but not in liveCache'
Can someone help me with getting apo data into LC?
Thanks
Hi Vardev,
Try the following optilons.
1) Use transaction /SAPAPO/RRP_NETCH and create pegging areas for the location product and then try
2) Check both the location and product are in active integration model
3) If it did not work, carry out a CIF run for the location product run and then try
4) Check both the location and product are assigned to active model 000
5) Check master data in R/3 (material master)
I think step 1 should resolve your problem.
Please confirm
Regards
R. Senthil Mareeswaran.
Similar Messages
-
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. -
Not able to create purchase orders
Hi Experts,
I am not able to create purchase order , it is not allowing me to save , I I am giving purchase requisition number in Po and trying to crete po .When i give purchase requistion number all the revelant data is copied and when i click on item level tab of delivery address following error occurs : Address doesn't exist T001W 2000 00010. Then the entire PO is cancelled. not able to save going out of po screen
Please give me your valuable advice so that it can help me in resolving this issue
Please do the need ful
Regards
AyubHi
We had to change the name text of he plant from ABCD COMPANY TO ABCD COMPANY PRIVATE LTD so , we had change and in both name 1:ABCD COMPANY PRIVATE LTD and NAme 2: ABCD COMPANY PRIVATE LTD
but in print out it the plant name appearing twice we decided to to erase name 1 that is we left blank and gave name 2:ABCD COMPANY PRIVATE LTD
But while creatimg Po from req ad the clicking item level adress tab eror pops up , and if i click on error tick mark it will take you out from Po screen
Regards
Ayub -
hi gurus,,,
my order type --or
item category group - norm
item category --tan
and i have two customers ...,, 10 and 11
, three materials ...m10, m11, m12.
when i try to create the order with the combination of 10 and m10 ,the system come up with error massage " No item category available (Table T184 OR 0001 CSEL TAN)" ...
and i am able to create remaining all combination
cust no material no status
10 m10 not possible to create order( error"-No item category available (Table T184 OR 0001 CSEL TAN0))
10 m11 possible
10 m12 possible
10 m13 possible
11 m10 possible
11 m11 possible
11 m12 possible
11 m13 possible
can u give me the solutionhi
if u have created ur own doc type without referring to std doc type then u have to carry out all customising related to doc type define/assign,item catg define/assign,sched lincat define/assign.in spro.
if u have created referring to sap std doc type with copy all data then system by default does all these .
In other words
Check if the combination of your sales order type and item category type exist.
In customizing you need to set up which item category types can be linked to the sales order types. -
Not able to create sales orders.
Dear Friends,
am new to SAP-PS. I have following query.
- Hide quoted text -
m creating an Demo Project for help.sap.com. for - Engineer to Order(ETO) of Trubine - Link is http://help.sap.com/saphelp_46c/helpdata/en/a3/c23cdaa62d11d3b544006094b90caa/frameset.htm
i m into order processing and i want to create an Sales Order (VA01).
I have followed all steps as mentioned in example.
i.e.
Call up the transaction as follows: Menu Path
Logistics
® Sales and Distribution ® Sales ® Order ® Create
Transaction Code
VA01
Enter the following data: Field
Data
Order type
PS1 (PS order)
Sales organization
1000
Distribution channel
10
Division
00
Choose .
Enter the following data: Field
Data
Sold-to party
1600
Purch. order no.
Any number
Req. deliv.date
Today's date + 1.5 years
Material
T-20000
Order quantity
1
Choose . In the dialog box, choose .
Select the sales items and choose .
Choose the Account assignment tab page.
Enter the following data: Field
Data
WBS Element
T-10056 ( Created Project in CJ20N)
The request for quotation is assigned to the billing element for the turbine project.
Choose the Conditions tab page.
Overwrite the amount for condition PR00 as follows: Field
Data
CnTy
PR00
Amount
1.760.000
You agreed this price with the customer on the basis of the quotation.
Choose .
At this Step when i want to SAVE the project i am getting an dialog box Create Network: Project Allocation (Plz see an attach image).
I have tried with all project nos but i am not able to save the project and get the sale order no .
Can anyone try this example tell me how to get an Order no. and why it's happening
Your help is apprciated.
regards,
Atul R. RajmaneHi,
If you enter a WBS element in the sales order, you need to mention a network element form the WBS.
Prase -
Not able to create transfer order..
Hi all,
When i am trying to create Transfer order,it gives an error"No items that are to be picked were found".
I have maintained all the settings regarding item categories and delivery item categories.
i am using Lean ware house management,What I feel is that there is some error in ware house settings.Please suggest..
Roopakhi,
i think you have 2 or more line item in sales order, the delivery date for one or two item will be in the past,so when you create delivery the item which is in the past delivey date will not get copied to delivery.
check all item is there in the delivery document,if no check the mising item delivery date, create the delivery based on that delivery data.
update the thread
regards
senya -
Not able to create an event in month view of iCal?
I used to be able to create an event from the month vien of iCal, and it doesn't work anymore. Anyone knows how to fix this?
ThanksSo sorry to not have a solution but I wanted to chime in and say "me, too!". Not only create an event, but I can't edit it in month view, either. I thought it was my entire iCal program, since I just upgraded to Lion today, but after reading your post I realize I can edit events in week mode, just not month mode.
-
Not able to create sales order.
Guru's,
I unable to create the sales order.
After entering sold to,material and qty and plant system is giving error Template material processing is deactivated
Murali suggested to implement the note 1094540.
But I am facing this problum in one box. remaining boxes working fine with out implementing the above note.
Please let me know from configuration side we can do any settings .
HIGHLY REWARDED
THANKS IN ADVANCE.
Its very urgent.Guru's,
I unable to create the sales order.
After entering sold to,material and qty and plant system is giving error Template material processing is deactivated
Murali suggested to implement the note 1094540.
But I am facing this problum in one box. remaining boxes working fine with out implementing the above note.
Please let me know from configuration side we can do any settings .
HIGHLY REWARDED
THANKS IN ADVANCE.
Its very urgent. -
Not able to create Follow up transaction since it has been grayed out
Hi Experts,
We have a scenario where in we will create the Sales Transactions (OR) in ECC and then it will replicates to CRM.
In CRM we wants to create Returns Order (RE) as a follow up Transaction to OR (which is replicated from ECC to CRM) .
When I tried to create Returns Order (RE) in CRM as a follow up document to Sales Transaction (OR), the follow up Transaction CRM Returns (RE) has been grayed out. I mean it is in display mode only.
And then I created Sales Transaction (OR) in CRM itself and then I tried to create follow up Returns Transaction (RE) I was able to create.
But I am not able to Create Returns Order (RE) for the Sales Transactions (OR) that have been replicated from ECC to CRM.
Can anybody help me in resolving this issue. Any help ful answer will be rewarded with points.
Thanks in advance,
-Frederick Johnson.Hi Fredrick,
Please check, whether you have completed all the steps for Copying Control for Business Transactions in the following path in IMG:
SPRO->Customer Relationship Management->Transactions->Basic Settings->Copying Control for Business Transactions:
- Define Copying Control for Transaction Types
In this step, you define the control for copying business transaction types.
To do this, you enter a source tranaction type and a target transaction type, and define the corresponding conditions for this combination.
- Define Copying Control for Item Categories
In this step, you define the control for copying item categories.
To do so, you enter a source item category and a target item category, and define the corresponding conditions.
- Define Item Category Determination when Copying
In this step, you define a specific item category determination which should be run during copying. The item category is used to find the target item category in the source transaction for the transaction type in the target transaction. This means that the transaction type for the source transaction is not relevant for the item category determination.
If the system cannot find an entry for the copying transaction in this table, the item category is found in the target transaction using the normal item category determination.
This might help you
regards
Srikantan -
Ship-To not assigned to Sold-To, even though able to create an order
Hi,
We have a peculiar scenario.
We have a Sold-To Ex: 1100, ship to 1200 and 1300 for a sales area, ex 1000-10-10. Here only 1200 Ship-to is assigned to Sold to 1100. ( SH 1300 is not assigned to SP 1100).
I am able to create an order for 1100 and 1200 for the above sales area, it is fine with the system.
But system is allowing me to create and order for 1100 and 1300 toooo. As per my knowledge system should not accept this order and system should give us a message like this "ship to is not maintained for this sold to" or some thing like that.
This is happening in ECC6.0. As i already checked with the system there is no enhancement or user exits used. Is it standard behavior of ECC6.0 or is there any solution for this problem.
Any help help form any one so much help full.
Thanks
Venkat Cheedalla.Hi Venkatesh,
You can do this in Customer Master of Sold-to party: 1100. In master, go to Sales Area Data Tab --> Partners Tabstrip. There you will find a Ship-to-Party Customer Code. Here change the 1100 code to 1200. Then Save.
Now while creation of Sale Order, system will automatically give you the Ship-to party as 1200. And if you want to change that Ship-to Party, then system will give you an Information message that Ship-to needs to be redetermined.
If you want that this Information Message should come as Error Message, then I think some customizations needs to be done in SPRO.
Regards,
Vishal -
Users are not able to create POs from PRs having Production Order (F)
Hi Gurus
Users are not able to create POs from PRs having Production Order (F) as creation indicator.
Whenever we are trying to convert the PR to PO we are getting the error message "Requisition has different doc. type NB and item cat. >&<" based on the below OSS# 938154 condition for the creation indicator type F.
Would you please investigate and advise what OSS notes are required to be able to use item category L (subcontracting) on a PO for a requisition generated from a network activity via Procurement Type = "Preliminary requisition for WBS element".
Thanks,
Sada.Hi Ajay & Andra
Whenever we are trying to convert the PR to PO we are getting the error message "Requisition has different doc. type NB and item cat. >&<" based on the below OSS# 938154 condition for the creation indicator type Production order (F).
Our Business requirement as shown below.
1).The problem - we currently have no way to "direct requisition" an item to be procured via subcontracting - only itu2019s possible via MRP.
2).These behaviors are inconsistent as the requisition process should not impact the procurement process. Can we find a way to influence the creation indicator on the requisition so that it does not appear as a production order?
Please suggest any alternate method for achieving this.
Thanks & Regards
Sada -
Not able to create a universe when using nav. att. 0MATL_TYPE in the query
Dear experts,
A few days ago I posted a message in the BO General Category due to this error and I was adviced to install SP19 in BW (3.5). We've allready installed it but the issue is still arising. I am posting this thread now in this category since maybe the other category was too general and this one a little bit more specified.
The error we are having is the following:
We are having an issue when trying to create a universe over a BEx query which uses navigational attribute 0MATL_TYPE of 0MATERIAL (0MATERIAL__0MATL_TYPE).
No matter where do we insert this nav. attribute in the query (lines, columns, free characteristics...) that we are not able to create the universe. We receive a message when trying to create it such as "error without message"
We have other navigational attributes from several characteristics which are not giving us any problems in universes, just nav attributes 0MATL_TYPE and a Z characteristic (ZMATPR) which is the same as 0MATL_TYPE (it is defined the same way, not related).
We are working with:
BW 3.5 - SP19, BEx 3.x
BOBJ XI 3.0 (without service pack or fix pack)
Does any one have any clue on what could be the reason for this issue??
Thanks in advance for your interest!
Best regards!!!!
CeciliaHello Ingo,
First of all thanks for your help, since we are really concerned about this issue.
We have been analysing the file you have talked us about. The thing is that a week and a half ago we had to write an OSS message to SAP concerning another issue, and we were recommended to install note 1260004 which involves editing the registry in order to show SOFA logs, and if we have understood correcty, the file you have given us modifies as well the server registry in order to show sofa logs.
Does the file you have given us includes new information in the SOFA logs, what is the difference between what we have changed with the SAP note and what you have given us?
Nevertheless, we have retrieved two logs from two executions (having navigational attribute 0MATL_TYPE in the query from which we want to create the universe) in case you could help us to interpret the informations given since we are not able to understand it. (You can seen them below my signature.....haven't find a way to attach files....sorry....)
Thank's very much in advance for your help!!!! This is so disconcerting.......
Best regards!
No way , I cannot copy the logs since the message format is destroyed when I copy it..... If you need it please inform me and we will send it to you!
Thanks again for the help!!!
Cecilia
Edited by: Cecilia Guerra on May 11, 2009 1:56 PM
Edited by: Cecilia Guerra on May 11, 2009 2:09 PM -
Inbound document not able to created from an outbound message EDI
Dear all,
Our inbound delivery was not able to create automatically during GI for an outbound delivery. Our inbound delivery is created via an EDI output type in the header of the outbound delivery as soon as the GI is posted.
All along, all the inbound docs are able to generate. However, for this particular outbound document, which has already GI, does not trigger the inbound document creation, and I notice that the output type message having a red light status in the message output.
When I checked the error processing log on this output message type (i.e. the red status), error message said
No goods receiving point for the combination of plant 1120 and stor.loc.
Message no. VL377
Diagnosis
No goods receiving point could be found for plant 1120 and storage location for the inbound delivery item. The delivery should still take place for the goods receiving point .
System Response
The system does not permit creation of and/or changes to the inbound delivery item.
Procedure for System Administration
Check your settings in Customizing for Determining the goods receiving point.
The funny thing is I check the SPRO setup (i.e. Assign Goods Receiving Points for Inbound Deliveries), and I notice that the goods receipt point has been assigned and configured. Further, other Delivery Order which is having the same data, does not generate such error in the message output, and the inbound is able to create.
WHy?
thanks.
Edited by: tuffy on May 12, 2011 12:04 PMHi Sudhir,
This is a production thus, I don't want to save the inbound delivery, but it seem no problem of creating it, I will have the business create it.
So, how do i debug the idoc?
at first how do I find the idoc number of the failed transaction as when i go to the output message (i.e. in DO header) and check the processing log, system said..
Object 0082658402 (i.e. DO number)
output type: Stk Transfe Crte Deliv
Processing log for program /spe/sto_id_processing
no goods receiving point for the combination of plant 1120 and stor loc
no inbound delivery create for the replenishment order
There is IDOC no for this faild message (though GI is incurs)?
thanks. -
PARTNER PROCESSING OBJECT BUS2032 NOT FOUND WHILE CREATING SALES ORDER
Hi All,
I am not able to create a sales order it gives a Error "PARTNER PROCESSING OBJECT BUS2032 not found". Can any one inform me what could be a problem. Thanks in advance.Yes, The Partner function SP is active.
We had a work around.
When the sales order was saved, being in Partner function Tab we got the error message. However when we returned to the Overview and saved the Order, we were through with the same. But, Iam not sure how could this happen. -
Not Able to see PO Orders in Isupplier Portal.
Hi,
1)I have created supplier
2) I Have created PO orders and approved .
3) Then I switch responsbility to Isupplier Portal full access.
4) It tried to create Advance billing notification (ABN ) but I am not able to see PO orders .( I am not able to see any PO so far )
any idea why I am not able to see any PO.
Thaks
RajHi Raj,
Please check your securing attributes at the supplier user level. The securing attributes values are created atthe time of supplier registry or can be added/updated manually at the user form (sysadmin).
For instance : if there is securing attribute 'ICX_SUPPLIER_CONTACT_ID' with a specific value, than that mean that only po documents that have this supplier contact id can be displayed in the portal.
Nira.
Maybe you are looking for
-
Client Drive Mapping (Windows) not working in SGD 4.6
I've upgrade your sgd 4.5 to 4.6. Currently we are using Virtual Desktop Connector 1.0 with VMware. Now I'm ran into a problem with client drive mapping for Windows. CDM has changed in 4.6 from smb to rdp-protocol. So there ist no need for the Enhanc
-
After 3.0.1 upgrade Music takes 1-2 min before playing each song
Both of my Apple TVs are doing the same thing. Prior to the upgrade everything was working fine. I have everything in my itunes (music, movies, tv shows). All of them are on my drobo which I've tried hard wired and using my drobo share. Movies and TV
-
I chose the wrong album name from a choice of 3 provided by iTunes and now I can't change how my CD automatically imports the tunes to the corrcet album name
-
Removing space between components in a Repeater
Hi, I have a component, based on a canvas, which is shown in a Repeater component. Unfortuantely the Repeater is add a space between each component, how can I remove the space created between each component so that they all sit next to each other. Th
-
Post Author: shikhirgupta CA Forum: Migration to XI R2 We have requirement in one of the project whereby they have BUSINESS QUERY (used in lower version of BO 6.x) to be migrated to LIVE OFFICE u2013 new product available in BOXI r2. This cannot be