Not able to create index for organization
in transaction ses_admin, i created an index for business object BAS_BUPA of type 1,ie individual account.
However, i am not able to create index for BAS_BUPA of type 2
It says "No entry in table SIC_INDEX_MAIN for index object BAS_BUPA and index 2"
hi,
The index is for Business Partner, so it includes both Persons and Organizations. So, only one index needs to be created for both.
The functioning is correct, just that i missed it.
Similar Messages
-
Question - are we not able to create indexed items in custom folders?
Just a question here. I would like to use the index/Value option for parameters in a workbook. This is where the List of Values drop down box for the parameter would show both the index number and the value and let you choose to select based on the index or on the value. An obvious example of this would be with months, where you would have January (1), February (2), March (3), and so forth. To do this, you have to set up indexed items in Discoverer Administrator.
That is where I am running into a problem/issue. I am not being able to pick an item and click to look at its properties, scroll down to the Indexed Item property, click on that property, and get a list of items to pick from. On the indexed item property I see a value of <None>, and when I click on that property, no list of items pops up.
I have defined indexed items before, but that was always done on regular folders (imported from the database). In this case, I am working with a custom folder.
The SQL that I have keyed in for this custom folder is this -
SELECT flex_value, description, flex_value_set_id, flex_value_id
FROM fnd_flex_values_vl
WHERE flex_value_set_id = 1011187
ORDER BY flex_value;
FND_FLEX_VALUES_VL is an Oracle view, that combines Oracle tables FND_FLEX_VALUES and FND_FLEX_VALUES_TL.
My goal would be to show both the FLEX_VALUE and the DESCRIPTION in the parameter to the users, so they can better decide what value(s) they want to pick. This is a general ledger application that I am working with, with the General Ledger account number segments and the Flexfield value set for each segment (we are using 7 segments to define our general ledger account number).
Am I not able to define indexed items when working with a custom folder? The documentation is not real clear. It talks about simple folders and complex folders, but does not mention custom folders, at least that I can find. Or perhaps I need to do something different with how I code the SQL for the custom folder to enable me to define indexed items in the custom folder?
Hope this makes some sense. Always a challenge to explain the situation in a clear manner. Thanks for any insight/assistance anyone can give me on this.
John DickeyAhh, those picky little details. Once I created an Item Class LOV on my item, then I could click on the Indexed Item property and get the list of fields in the folder to show up and pick my item (to be the indexed item) from that list. I went back to the user guides and the documentation sure does not indicate this requirement. For example, in the Discoverer Administrator guide, you have the section (page 9-30 in the version I have) titled "How to assign an indexed item to an item". Nowhere in that section does it say that you have to create an Item Class LOV first to be able to do this. Though it does show how if you do not have an LOV on the item you pick to be the indexed item, you will be prompted to create an LOV for that item. In the past I had my LOVs created first. This time I was trying to do the indexed item first before creating my LOVs. So lesson learned - you have to create an Item Class LOV first before you can assign an indexed item to an item.
Thanks for the assistance.
John Dickey -
Not able to create entries for ALBTCMON (SCM 4.10)
I am trying to create entries for monitoring jobs that start with "SAP_*" and I am trying to add entry into ALBTCMON table. But system is trowing the message as below.
===============================================================
Create data processing function module
Message no. SV023
Diagnosis
You have called the function for editing view contents. The function modules needed for the maintenance functionality of this view are not available in the system.
Procedure
The data processing function module must be re-generated.
Contact the system administration.
===============================================================
Can somebody tell whats wrong. I am working in SCM 4.10.
Regards,
GiridharaMake sure the xWebsites metadata field has the siteId of your site. And as Srinath said, make sure it's "Released"; which can take a moment or two.
-
Not able to create request for multiple user in oim 11gr2
Hi,
I am trying to assign a resource to multiple user using oim identity console as System Administrator.
But when i am assigning the resource to multiple user its taking the same value for both the users.
Please let me know how to add the different value for different users.
ThanksThat's the rules of how it works. A request has 1 request form per resource for all users on the request. Those fields must all be marked as available in bulk as well to be viewed if you have more than 1 user on the request. If you need to provide different values based on the user, your best option is pre-populate adapters on the process form and use logic to populate the fields. You will not be able to manually provide different values during the request.
-Kevin -
Mdm_clnt_extr is not able to create idoc for material
Hello ,
In my scenario material data has to transfered from ECC6.0 to MDM5.5 using XI.
Scenario is configured in XI.
Trying to extreact materials from ECC6.0 using mdm_clnt_extr.
Material_extract is extraction object used in variant required for mdm_clnt_extr.
once I give values for matnr and starts extraction, background job goes into error
saying 'This idoc is permitted for XI logical system'. where In we20 of ECC6.0 , I have MATMAS04 and MATMAS05. In both cases I am getting error 'This idoc is permitted for XI logical system'.
At the same one bp document od MDM , message type MATMDM is given, but i dont see that in ECC6.0.
Pl can anyone suugest on this.
thanks,
SharadaHi Sharada,
i think there is some problem in your RFC destination settings,tats why the error is coming.
I am trying to get the exact solution for your error,meanwhile you can check your configuration settings.
I will outline the ALE Settings .
1 WE21 : Set up the port in IDOC Processing
2 SM59 : Set the RFC Destination to XI and check it.
3 WE20 : Create a partner profile with Partner Type LS (Logical System) for XI
Include the message types : DEBMDM, MATMAS, MDMRECEIPT
4 BD64 : Create a Distribution model with Sender as SAP and receiver as XI.
Include the message type DEBMDM,MDMRECEIPT,MATMAS,/SAPSSLL/MATMAS_SLL
5 Generate partner profile. This will generate it in the receiving system.
Following transactions are useful for trouble shooting any idoc issues
WE02, WE20 ,BD87,SMQ2,SMQ3 and SALE->System Monitor->trfc check
Hope it will solve your problem.
<b>Please remark iof it really helped you :-)</b>
Thanks,
shiv prashant dixit -
Not able to create new e-mail on N8 using Mail for...
Not able to create new e-mail on N8 using Mail for Exchange.
Currently using google for my domain, but settings are the same as explained on the google Sync webpage: http://www.google.com/support/mobile/bin/answer.py?hl=en&answer=147951
When creating reply on mail the application crashes. When creating new mail it says "Kan bewerking niet uitvoeren" in english: "Unable to execute action".
Any idea why creating mail is not possible?
Regards,
Jorisproblem is known
more info there:
/t5/Nseries-and-S60-Smartphones/N8-syncing-with-Google-contacts-amp-calendar/td-p/772020
there is little workaround aslo. -
Not able to create EAR file for WAR file extracted project
Hi Experts,
I am trying to import a WAR file, make changes to the project and create an EAR file for the same. I am not able to remove import
errors despite of adding required jar files to it.
Also, I am not able to create an EAR file for the same.
I have copied the steps here with screen shots. Below are the steps :
Import WAR file in NWDS 7.3 – Enterprise Portal perspective
Select WAR file to create WAR and EAR project for it.
Project created with import errors. e.g – com.sapportals.portal.prt*
Found jar file from Class – target jar file table.
e.g – for Class com.sapportals.portal.prt.resource.IResource needed jar file is tc~epbc~prt~api.jar
Copied required jar files in WEB-INF -> lib folder.
Configure Build path and Add External jars.
Portalapp file screen shot
I think errors should go now, but they still exist.
Next I right click on WAR project and tried updating related EAR project.
Next, Export EAR file from EAR project.
I have tried both EAR types.
But EAR file is not created.
Please help me in removing the errors.
Thanks in advance :-)
Anubha PandeyHi Anubha,
I feel that you're missing JAR dependencies and hence not able to resolve the above import errors.
Please go through the below thread for the AFP Masthead customization and follow the same:
How to download and change AFP Masthead on SAP Portal 7.3
Hope, this will help!!!
BR,
Anurag -
I am not able to create a hotspot form my iphone 4 after upgrading to ios 7 . Do any one have solution for it
Verify that your carrier supports Personal Hotspot for your device and that you have Personal Hotspot enabled on your cellular plan:
From Here > http://support.apple.com/kb/HT3574
Trouble Shooting > http://support.apple.com/kb/TS2756 -
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 do GR for STO delivery with packing.
Hi All,
Hi All,
I am not able to do GR for STO delivery.
I am getting the following error:
Data for creating a delivery is incomplete (Vendor)
Message no. M7279
Business scenario:
STO between two plants of same company code with packing material.
Sales Org(Supp)-4444
Sales Org(Rec)- 3333
Plant(Supp)-2003
Plant(Rec)-2002
ME21N->VL10B->PGI->VF01(Proforma)->MIGO w.r.t outbound delivery(error)
Note: PGI with packing material-separate line item generated for packing material-movement type for main material-641 and for packing material-601)
with regards
Azeez.MohdHi,
When the stock is going to be moved between two plants or two storage locations that are under single company code called as stock transfer order business process. Receiving plant raises the purchase order with supplying plant; supplying plant delivers the goods to the receiving plant by raising sales order.
Config Steps
Create Vendor: Transaction code: XK01
Assign Plant to Vendor
Go to change mode of Vendor [XK02]
Specify Vendor number that we created in the previous step
Define shipping data for plants
Create material by maintaining u201CPurchasingu201D view: Transaction code: MM01
Extend the material from XXXX to YYYY plants
As we are extending material from plant XXXX into YYYY plant, system copies all the data into the new plant.So that we have to change the delivering plant in delivering plant field as YYYY in Sales: Sales organization data 1 view.
Create Purchase order: Transaction code: ME21N
Activities due for Shipping (Purchase order fast display): Transaction code: VL10B
Display stock in transit: Transaction code: MB5T
Goods receipt: Transaction code: MIGO
Stock movement types: INTRAand INTER
INTRA
Stand order type (Document type) = UB
Delivery type = NL
Determination of document type:
Supplying plant + Receiving plant = UB
Supplying plant + UB = NL
Movement types:
Issuing plant Receiving plant
Single step 647 101
Two step 641 101
INTER
Standard order type (Document type) = NB
Delivery type = NLCC
Determination of document type:
Supplying plant + Receiving plant = NB
Supplying plant + NB = NLCC
Movement types:
Issuing plant Receiving plant
Single step 645 101
Two step 643 101
PBXX is the Gross price condition type for Stock Transfer Order
Vendor = Supplying plant
Customer = Receiving plant
NOTE: In single step method updations takes place in both plats simultaneously.
In two-step method updations should takes place manually. -
Not able to create function in ALBPM Studio 6.0
Hi,
I am trying to write a method that returns a string.
But i keep on getting an error which says that return statement can only be present in functions.
Now I tried all possible ways but i was not able to create a function.
Could anyone please help me out with creating a function in ALBPM. else tell me how do i return a string from a method.Hi,
I suspect you have written a method having String return type but the method does not have return statement.
Go to the Catalogue component->BPM Object->Right click on the BPM object and select New Method->Give the method name. Now the method window will be opened. Go to the propertied tab of the right most panel. Set the return type as string. In the method window editor write your business logic. The below mentioned code is for sample one.
String msg = "Hello World";
return msg;
Bibhu -
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 -
Not able to create a material document with movement type 103
I am not able to create a material document with movement type 103,
The system is populating the value as 101 .
How do I create a matdoc with movement type 103?What is the error you receive? Please specify with message number.
On MIGO, you need to change the default value mvmt type value to 103 before you enter the PO number to be able to do 103.
Once this defualt value is set, you can enter the PO and item number in the document number fields and proceed with 103.
But you cannot change the mvmt type for already entered items from 101-103 or vice versa.
I think the 101-103 and 103-101 mvmt type conversion message is standard error message -
I am not able to create a new tab, eventhough i have tried all ways to do it.
Normally the existing (current) tab has at the end an "+", and that gives you the option to make a new tab to the right. My Firefox tab does not have the "+", and I'm not able to create a new tab for another link. The new tab option is not working on my Mozilla internet browser.
Use Hotkey CTRL + T to Open a Blank Tab. Do the following too:
go to Help Menu -> select "Restart with Add-ons Disabled"
Firefox will close then it will open up with just basic Firefox. You can enable the Add-ons later. Check and tell if its working. -
Not able to create a customer master record with US as the country code
Hey All,
I am not able to create customer master data in the Transaction Code XD01/FD01 with the country code as US.
The error message for the same is *NO JURISDICTION CODE* COULD BE DETERMINED. I have checked the tax code settings but could not locate the problem.
I have checked the field in the account group(OBD2) but tax code is in optional status
and also checked the country settings for US in the transaction code OY17 still the same error message,
but when I tried checking the settings for a different company code's customer data base (us in county code)
I can see that there is a number mentioned in the address tab under tax jurisdiction field (beside time zone) which is not populating for this company code.
So, do anyone know where exactly we mention this number so that it populates in that field of address.
Hope am clear.
hope to receive a solution
thanks & regards
vinilaHi,
You need to maintain the JURISDICTION CODE for country US. This JURISDICTION CODE code mainatanance purely FI/CO part.. it depends on the country's tax procedures.. Better take the help from your FI/CO consultant..
Menu path for Defining tax jurisdiction code
IMG -- Financial accounting -- Financial accounting global settings -- tax on sales and purchases -- basic settings -- define tax jurisdiction
reward if helps
Muthu
Edited by: Muthupandiyan on Mar 14, 2008 11:09 AM
Maybe you are looking for
-
Why do we get the data from a view to a report.
hi why do we get the data from a view to a report. is it possible to get the data from a view in all the cases?
-
What does it mean and how to I get out / avoid / fix it? Thanks!
-
What's it mean when variables are defined with boolean operators? I've seen it before but can't find any help on it in the Java Tutorial so I don't really know what it means. e.g. int var1 = (var2 & var3) | var4
-
Role Expert Workflow Approval Criteria
Hi, I am trying to add workflow approval criteria to Role Expert I have gone to the configuration menu -->workflow --> approval criteria I have set-up an approval expression 'Functional Area' = Finance. However when I go to search for an approver or
-
The program button icons are broken in dreamweaver CS6
I open up Draem Weaver CS6 and all the iconsa re broken though out teh program. I tried re-installing but it still has had no effect. Also I have logged out and back in but change.