Create subordinate values for Characteristics

Hi ,
I am using BAPI to create the characteristic
    CALL FUNCTION 'BAPI_CHARACT_CREATE'
    EXPORTING
    charactdetail = gs_charactdetail
    keydate = gv_keydate
    TABLES
    charactdescr = gt_charactdescr
    charactvaluesnum = gt_charactvaluesnum
    charactvalueschar = gt_charactvalueschar
    charactvaluescurr = gt_charactvaluescurr
    charactvaluesdescr = gt_charactvaluesdescr
    charactreferences = gt_charactreferences
    charactrestrictions = gt_charactrestrictions
    return = gt_return .
But there is no way which i can create suboridinate values for (charactvalueschar) . Please let me know how can i create soubordinate values for char values
Reagrds
Ramesh

describe your problem.
It does not really matter if you use standard batch input or IDOC, both will lead to the same result.
However, object 0150 and CLFMAS are 2 different things.
0150 is characteristics while CLFMAS is classification
if you want classify with standard batch input then you should use 0130 instead of 0150.

Similar Messages

Please enter valid value for characteristics

Hi,
One of our user got this error when opening a query Please enter valid value for characteristics.
How do I fix this since I couldn't see any errors in SU53 and authourization logs.
thanks

Hi Bhat,
Check SAP notes : 1077144
Thanks,
Vijay.

Issue in creating limits value for service PR using BAPI_REQUISITION_CREATE

HI Experts
I am creating a service PR using bapi bapi_requisition_create.I am able to create service PR successfully, but I am not able to set value for overall limit and the Expected value.
I am passing the limits values through bapi, but when I am trying to display those value in the limits tab in ME53N, it gives dump.
Please suggest how can I set the limits value.
regards
Ashwini

Could Ashwini or anyone else please suggest how this issue was resolved? I am using BAPI_REQUISITION_CREATE, but the limits I enter in the REQUISITION_LIMITS table, do not get saved, although the Purchase Requisition itself gets created.

How to create valid values for button

Hi,all
I want put valid values to button like copy from or copy to functionality is it possible.
if u have idea plz post it..?
by
Firos.C

Hi,
Actually u cannot have valid values for buttons. IN SAP we have Copy to and Copy from but the same kind of button cannot be created in SDK..... so u need to use the combo box and add ur valid values.
Hope it helps,
Vasu Natari.

Values for Characteristics entered on Orders with Configurable Products

Hello all,
I have a system that has Configurable Products to be used in Sales Orders. I have a requirement to provide the values stored against some characteriestics for an online report. Can anyone point me in the direction of tables that hold the values entered for characteristics at the order level?
Many thanks,
Jon

Hello,
thanks for your answer.
But I cannot restrict the values for each characteristic, I need to restrict it per material for each characteristic? So where can I do that?
Thanks
Anne

Values for Characteristics in COPA

Hello Gurus,
If we have maintained the possible values for a characteristic in COPA, is it possible to have other values. For example, in our scenario, Brand is a characteristic and we are deriving it from the classification view in Material Master. In that case, is it necessary to maintain Values for this Characteristic in COPA. Is there any necessity to maintain the possible values in separate Table.
Please Advise.
Thanks
PM

Hi Praveen
when you create a WW char in COPA, you have 2 options (2 radio buttons) i.e. With own value Maintenance and w/o Own value Maintenance....
If you choose with own value maintenance, then you need to maintain permitted char values (brand values) in KES1... If you choose "w/o own...", then you need not
Regards
Ajay M

Create a value for Decision table with gc_option_not_initial.

Dear Expert,
I am filling in a decision table with coding. I load an excel file, create a range for eatch value with the folling method:
   cl_fdt_convenience=>create_simple_range( EXPORTING iv_application_id = lv_application_id
                                                                              iv_option = if_fdt_range=>gc_option_equal
                                                                              iv_test_parameter = lv_id
                                                                              iv_low = lv_value
                                                                              iv_activate = abap_false
                                                                    IMPORTING ev_range_id = ls_table_data-expression_id ).
            INSERT ls_table_data INTO TABLE lts_table_data.
            CLEAR ls_table_data-expression_id.
But the following code is not working:
   cl_fdt_convenience=>create_simple_range( EXPORTING iv_application_id = lv_application_id
                                                                              iv_option = if_fdt_range=>gc_option_not_initial
                                                                              iv_test_parameter = lv_id
                                                                              iv_activate = abap_false
                                                                    IMPORTING ev_range_id = ls_table_data-expression_id ).
            INSERT ls_table_data INTO TABLE lts_table_data.
            CLEAR ls_table_data-expression_id.
What is wrong?
How to create than a range for a decision table cell with option: 'not initial'?
Thank you very much in advance?
Best regards
Ahmed

I found the same problem in the comments of this post Filtering Rules using SAP HANA Decision Table.
A possible solution is to implement a solution directly in SQLScript. Hints can be found in Filtering Rules using SAP HANA Decision Table

Create hash value for clob column ?

Hi,
does anybody know a way to calculate a hash value for a clob column (9i) ?
DBMS_UTILITY.GET_HASH_VALUE could only handle varchar2(4000).
Thank you!
Regrads
Michael
Message was edited by:
mseiwert

I can't reproduce it on my 10.2.0.4.0. CTL file:
load data
INFILE *
Replace into table samp
fields terminated by ","
trailing nullcols
no,
col1 Char(100000000) ,
col2 Char(100000000) enclosed by '"' and '"'
BEGINDATA
1,asdf,"assasadsdsdsd""sfasdfadf""sdsdsa,ssfsf"
2,sfjass,"dksadk,kd,ss""dfdfjkdjfdk""sasfjaslaljs"Loading:
SQL> Create table samp
2 (
3 no number,
4 col1 clob,
5 col2 clob
6 );
Table created.
SQL> host sqlldr scott/tiger control=c:\temp\samp.ctl log=c:\temp\samp.log
SQL> select * from samp
2 /
        NO
COL1
COL2
         1
asdf
assasadsdsdsd"sfasdfadf"sdsdsa,ssfsf
         2
sfjass
dksadk,kd,ss"dfdfjkdjfdk"sasfjaslaljs
        NO
COL1
COL2
SQL> SY.

ECCS- CX0AA- Default Values for Characteristics

Hello All,
I have an issue in my project concerned with ECCS.
We have maintained default values in CX0AA say we have maintained CCA (Sub Item Category) with a particular default value, now this default value has to be removed and even the Sub item Category CCA has to be removed from CX0AA. I tried it by the transaction code CX0A1, but I am unable to do it.
Can any one please let me know how to remove this default value maintainance in complete from CX0AA.
Thanks for the help in advance.
Best Regards,
Satish

or in my box: CX01->Master Data->(Characteristic) Default Values
looks like an extension to add additional fields for consolidation below the standard SAP delivered ones for master data like items and subitems. it may well be dead end for development as EC-CS is being superseded by SEM-BCS and possibly some reincarnation of Business Objects.
other config transactions in the family are:
CX0A1                Edit Characteristics
CX0A2                Edit Field Groups
CX0A3                Generate Master Data Maint. Modules
CX0A4                Reorg.View Maintenance (master data)
CX0A5                Maintain Characteristic Values
CX0A6                Display Characteristic Values
CX0A7                Maintain Characteristic Values
CX0A8                Display Characteristic Values
CX0AA                Maintain Default Values
CX0AB                Display Default Values
CX0AC                Attrib for CU: Maint. Char. Values
CX0AD                Attrib for CU: Displ. Char. Values
CX0AE                Subassign.: Maintain Char Values
CX0AF                Subassign.: Display Char Values

Special Authorization Values for characteristics

I had a question about the authorization value '*' (asterisk)
SAP defines how this can be used as follows:
(asterisk)
.. Denotes a set of arbitrary characters
.. Used alone to grant access to all values
.. Used at the end of a value to specify a simple pattern (example: SAP*)
Here is my situation:
InfoObject A: Values can be: A,B, C, A1, B1, C1, C2, A1G, B1D, C1A, C2A etc.
If a user has authorization of C, it automatically means he is authorized to view values C1, C2, C1A and C2A. In this case can I assign values
C, C and C** (I am doubtful abt using *(double asterisk))
Please clarify.
Thanks

Asterisk denotes a set of arbitary characters
Used alone to grant access to all values
used at the end of a value to specify a simple pattern(example SAP *)
+(Plus)
Denotes exactly one character
Used at the end of a value to specify a simple pattern (example - RED+)
Used to specify date patterns(only for validity (OTCAVALID))
Hope it Helps
Chetan
@CP..

Can't create the key for DisallowRun

Hello.
I am trying to use the DisallowRun method for restricting web browsers on certain computers. I can create the disallow run *value* in HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer, and I can create a subkey (New Key #1) in
the same key to create the values for the various browsers to restrict, but I am unable to name that subkey *DisallowRun* as the documentation that I've seen says it needs to be named. When I try to do it in the registry editor, I get an error saying the key
cannot be renamed (although I can rename it to other names), and when I try to do it in Notepad, I get an error saying "Cannot import \\sharepath\file.reg: Error accessing the registry".
If I change the key name, however, the import is successful (for example [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer\DisallowRun2]
"1"="iexplore.exe").
Any ideas why I am prevented from creating the specific key name that Microsoft says the key needs to be? Is there some other policy setting that allows/disables the ability to make this key in the first place?

> that subkey *DisallowRun* as the documentation that I've seen says it
> needs to be named. When I try to do it in the registry editor, I get an
> error saying the key cannot be renamed (although I can rename it to
I verified (on 2012R2), and I had no problem to do so. I can create
DisallowRun, can create values, can rename and delete, all without issues.
Do you have special security software on your computers?
Martin
Mal ein
GUTES Buch über GPOs lesen?
NO THEY ARE NOT EVIL, if you know what you are doing:
Good or bad GPOs?
And if IT bothers me - coke bottle design refreshment :))

Hxc_timestore_deposit.create_time_entry creating negative values

Hi,
I am trying to create time entry through back end using API (hxc_timestore_deposit.create_time_entry) as
declare
l_time_building_block_id hxc_time_building_blocks.time_building_block_id%TYPE;
l_tbl_attributes_info hxc_self_service_time_deposit.app_attributes_info ;
l_return_status varchar2(30);
l_tbl_timecard_info hxc_self_service_time_deposit.timecard_info ; --hxc_block_table_type;
begin
hxc_timestore_deposit.create_time_entry (
p_start_time=> fnd_date.canonical_to_date('2009/09/02 09:00:00'),
p_stop_time=> fnd_date.canonical_to_date('2009/09/02 17:00:00'),
p_resource_id=> 7427, --9389, -- Identifies a person on our DB, REPLACE WITH YOUR IDs
p_app_blocks=> l_tbl_timecard_info,
p_app_attributes=> l_tbl_attributes_info,
p_time_building_block_id=> l_time_building_block_id
l_return_status := fnd_api.g_ret_sts_success;
DBMS_OUTPUT.PUT_LINE('TESTING of hxc_timestore_deposit');
DBMS_OUTPUT.PUT_LINE('return_status : ' ||l_return_status);
DBMS_OUTPUT.PUT_LINE(' l_time_building_block_id :- '||l_time_building_block_id);
end;
Above code is creating negative values for time_building_block_id.
Can anyone pls help me.
Thanks
Rutuja

Hi,
I have developed one more script to create a time card.
It is also generating negative values.
Can anyone knows the problem
Pls help me regarding the same.
Thanks in advance.
Rutuja
DECLARE
-- Constant declarations
-- This is the appl_id for OTL, do not change
c_otl_appl_id CONSTANT NUMBER (3) := 809;
c_proj_attr1 CONSTANT VARCHAR2 (7) := 'Task_Id';
c_proj_attr2 CONSTANT VARCHAR2 (10) := 'Project_Id';
c_proj_attr3 CONSTANT VARCHAR2 (16) := 'Expenditure_Type';
c_proj_attr4 CONSTANT VARCHAR2 (19) := 'Expenditure_Comment';
c_proj_attr5 CONSTANT VARCHAR2 (23) := 'SYSTEM_LINKAGE_FUNCTION';
v_msg_info                VARCHAR2(20000);
x_status_msg                VARCHAR2(20000);
vx_msg_index_out           NUMBER;
-- Variable declarations
-- declare the PL/SQL Table that will hold the complete timecard (all the BBs)
l_tbl_timecard_info hxc_self_service_time_deposit.timecard_info;
-- declare the PL/SQL Table that will hold all the attributes
l_tbl_attributes_info hxc_self_service_time_deposit.app_attributes_info;
-- declare the PL/SQL Table that will hold the messages returned by the API
l_tbl_messages hxc_self_service_time_deposit.message_table;
-- person ID that this TC belongs to, Replace with your own
l_person_id per_all_people_f.person_id%TYPE := 2638;--9389;
-- Replace with your own IDs
l_task_id VARCHAR2 (4) := '2011';--HOLIDAY--'221';
-- (l_project_id is NOT the same as task id, they just happen to have the
-- same ID on our database)
l_project_id VARCHAR2 (3) := '803';--'221';
-- Replace with your own values
l_expenditure_type VARCHAR2 (15) := 'Professional';
l_ot_expenditure_type VARCHAR2 (15) := 'Overtime';
l_system_linkage_id VARCHAR2 (15) := 'ST';
l_ot_system_linkage_id VARCHAR2 (15) := 'OT';
-- Will hold TC_ID, returned by the deposit process
l_new_timecard_id NUMBER;
-- Will hold TC ovn, returned by the deposit process
l_new_timecard_ovn NUMBER;
l_message fnd_new_messages.message_text%TYPE;
l_start_time DATE := fnd_date.canonical_to_date('2009/09/16 00:00:00');
l_stop_time DATE := fnd_date.canonical_to_date('2009/09/22 23:59:59');
l_tc_bb_id hxc_time_building_blocks.time_building_block_id%TYPE;
l_day_bb_id hxc_time_building_blocks.time_building_block_id%TYPE;
l_detail_bb_id hxc_time_building_blocks.time_building_block_id%TYPE;
l_time_attribute_id hxc_time_attributes.time_attribute_id%TYPE;
BEGIN
-- First initialize your session, this needs to be done for internal reasons so
-- the TimeStore knows who is trying to deposit the information. When you log
-- into SS, the same is done for you by the framework, here however we have to do
-- it manually.
dbms_application_info.set_client_info(206);
FND_GLOBAL.APPS_INITIALIZE(1781,51681,809 );-- This is the appl_id for OTL, do not change
-- PART 1: POPULATE TABLES --
-- First populate the timecard PL/SQL table:
-- Start with the TIMECARD BB
hxc_timestore_deposit.create_timecard_bb(
p_start_time=> l_start_time,
p_stop_time=> l_stop_time,
p_resource_id=> l_person_id,
p_comment_text=> 'Created using API: Weekly Project TC',
p_app_blocks=> l_tbl_timecard_info,
p_time_building_block_id=> l_tc_bb_id);
DBMS_OUTPUT.PUT_LINE(' l_tc_bb_id :- '||l_tc_bb_id);
FOR j IN 1..FND_MSG_PUB.Count_Msg
     LOOP
FND_MSG_PUB.GET( p_msg_index => -1
,p_encoded => 'F'
,p_data => v_msg_info
,p_msg_index_out => vx_msg_index_out);
x_status_msg := x_status_msg || v_msg_info;
     END LOOP;
DBMS_OUTPUT.PUT_LINE(' 1st API STATUS :- '||x_status_msg);
COMMIT;
-- Now we create the DAY BB, 7 in total, and since they are all the same we
-- will loop 7 times
FOR i_day IN 0 .. 6
LOOP
hxc_timestore_deposit.create_day_bb (
p_day => TRUNC (l_start_time)+ i_day,
p_parent_building_block_id=> l_tc_bb_id, -- returned by create_timecard_bb
p_comment_text=> 'Created using API',
p_app_blocks=> l_tbl_timecard_info,
p_time_building_block_id=> l_day_bb_id);
DBMS_OUTPUT.PUT_LINE(' l_day_bb_id :- '||l_day_bb_id);
v_msg_info := NULL;
x_status_msg := NULL;
vx_msg_index_out := NULL;
FOR j IN 1..FND_MSG_PUB.Count_Msg
     LOOP
FND_MSG_PUB.GET( p_msg_index => -1
,p_encoded => 'F'
,p_data => v_msg_info
,p_msg_index_out => vx_msg_index_out);
x_status_msg := x_status_msg|| v_msg_info;
     END LOOP;
                         DBMS_OUTPUT.PUT_LINE(' 2nd API STATUS :- '||x_status_msg);
-- The next call would also work but we choose to use the first one
-- since we know the TIMECARD's Id. If you do not know the ID you should
-- use this next call commented out here.
/* hxc_timestore_deposit.create_day_bb (
p_day => TRUNC (l_start_time)
+ i_day,
p_resource_id=> l_person_id,
p_comment_text=> 'Created using API',
p_app_blocks=> l_tbl_timecard_info,
p_time_building_block_id=> l_day_bb_id
-- We can attache the DETAIL BB for every DAY BB that represents 'normal'
-- work hours as well here as they are all the same
-- We only need to do this for weekdays though
IF i_day < 5
THEN
hxc_timestore_deposit.create_detail_bb (
p_type=> 'MEASURE',
p_measure=> 8,
p_parent_building_block_id=> l_day_bb_id,
p_comment_text=> 'Created using API: NT',
p_app_blocks=> l_tbl_timecard_info,
p_app_attributes=> l_tbl_attributes_info,
p_time_building_block_id=> l_detail_bb_id
DBMS_OUTPUT.PUT_LINE(' l_detail_bb_id :- '||l_detail_bb_id);
v_msg_info := NULL;
x_status_msg := NULL;
vx_msg_index_out := NULL;
FOR j IN 1..FND_MSG_PUB.Count_Msg
     LOOP
FND_MSG_PUB.GET( p_msg_index => -1
,p_encoded => 'F'
,p_data => v_msg_info
,p_msg_index_out => vx_msg_index_out);
x_status_msg := x_status_msg|| v_msg_info;
     END LOOP;
                         DBMS_OUTPUT.PUT_LINE(' 3nd API STATUS :- '||x_status_msg);
-- The next call would also work but we choose to use the first one
-- since we know the DAY's Id. If you do not know the ID you should
-- use this next call commented out here. In fact we use it ourselves
-- later to add the overtime.
/* hxc_timestore_deposit.create_time_entry (
p_measure=> 8,
p_day => TRUNC (l_start_time)
+ i_day,
p_resource_id=> l_person_id,
p_comment_text=> 'Created using API: NT',
p_app_blocks=> l_tbl_timecard_info,
p_app_attributes=> l_tbl_attributes_info,
p_time_building_block_id=> l_detail_bb_id
-- We can also attach the attributes to every BB that represent
-- 'normal' work hours
-- Attribute1
hxc_timestore_deposit.create_attribute (
p_building_block_id=> l_detail_bb_id,
p_attribute_name=> c_proj_attr1,
p_attribute_value=> l_task_id,
p_app_attributes=> l_tbl_attributes_info
-- Attribute2
hxc_timestore_deposit.create_attribute (
p_building_block_id=> l_detail_bb_id,
p_attribute_name=> c_proj_attr2,
p_attribute_value=> l_project_id,
p_app_attributes=> l_tbl_attributes_info
-- Attribute3
hxc_timestore_deposit.create_attribute (
p_building_block_id=> l_detail_bb_id,
p_attribute_name=> c_proj_attr3,
p_attribute_value=> l_expenditure_type,
p_app_attributes=> l_tbl_attributes_info
-- Attribute4
hxc_timestore_deposit.create_attribute (
p_building_block_id=> l_detail_bb_id,
p_attribute_name=> c_proj_attr4,
p_attribute_value=> 'Expenditure Comment created by API',
p_app_attributes=> l_tbl_attributes_info
-- Attribute5
hxc_timestore_deposit.create_attribute (
p_building_block_id=> l_detail_bb_id,
p_attribute_name=> c_proj_attr5,
p_attribute_value=> l_system_linkage_id,
p_app_attributes=> l_tbl_attributes_info
END IF; -- Only for weekdays
END LOOP; -- End creating normal working days + time
-- And now we add the Overtime to Tuesday and Wednesday
-- We have to use create_time_entry here because we do not have the ID
-- for the Wednesday TBB anymore, using create_time_entry we do not need it
-- Tuesday
hxc_timestore_deposit.create_time_entry (
p_measure=> 1,
p_day => TRUNC (l_start_time)+ 1,
p_resource_id=> l_person_id,
p_comment_text=> 'Created using API: OT',
p_app_blocks=> l_tbl_timecard_info,
p_app_attributes=> l_tbl_attributes_info,
p_time_building_block_id=> l_detail_bb_id
-- Attribute1
hxc_timestore_deposit.create_attribute (
p_building_block_id=> l_detail_bb_id,
p_attribute_name=> c_proj_attr1,
p_attribute_value=> l_task_id,
p_app_attributes=> l_tbl_attributes_info
-- Attribute2
hxc_timestore_deposit.create_attribute (
p_building_block_id=> l_detail_bb_id,
p_attribute_name=> c_proj_attr2,
p_attribute_value=> l_project_id,
p_app_attributes=> l_tbl_attributes_info
-- Attribute3
hxc_timestore_deposit.create_attribute (
p_building_block_id=> l_detail_bb_id,
p_attribute_name=> c_proj_attr3,
p_attribute_value=> l_ot_expenditure_type,
p_app_attributes=> l_tbl_attributes_info
-- Attribute4
hxc_timestore_deposit.create_attribute (
p_building_block_id=> l_detail_bb_id,
p_attribute_name=> c_proj_attr4,
p_attribute_value=> 'Expenditure Comment created by API',
p_app_attributes=> l_tbl_attributes_info
-- Attribute5
hxc_timestore_deposit.create_attribute (
p_building_block_id=> l_detail_bb_id,
p_attribute_name=> c_proj_attr5,
p_attribute_value=> l_ot_system_linkage_id,
p_app_attributes=> l_tbl_attributes_info
-- Wednesday
hxc_timestore_deposit.create_time_entry (
p_measure=> 2,
p_day => TRUNC (l_start_time)
+ 2,
p_resource_id=> l_person_id,
p_comment_text=> 'Created using API: OT',
p_app_blocks=> l_tbl_timecard_info,
p_app_attributes=> l_tbl_attributes_info,
p_time_building_block_id=> l_detail_bb_id
-- Attribute1
hxc_timestore_deposit.create_attribute (
p_building_block_id=> l_detail_bb_id,
p_attribute_name=> c_proj_attr1,
p_attribute_value=> l_task_id,
p_app_attributes=> l_tbl_attributes_info
-- Attribute2
hxc_timestore_deposit.create_attribute (
p_building_block_id=> l_detail_bb_id,
p_attribute_name=> c_proj_attr2,
p_attribute_value=> l_project_id,
p_app_attributes=> l_tbl_attributes_info
-- Attribute3
hxc_timestore_deposit.create_attribute (
p_building_block_id=> l_detail_bb_id,
p_attribute_name=> c_proj_attr3,
p_attribute_value=> l_ot_expenditure_type,
p_app_attributes=> l_tbl_attributes_info
-- Attribute4
hxc_timestore_deposit.create_attribute (
p_building_block_id=> l_detail_bb_id,
p_attribute_name=> c_proj_attr4,
p_attribute_value=> 'Expenditure Comment created by API',
p_app_attributes=> l_tbl_attributes_info
-- Attribute5
hxc_timestore_deposit.create_attribute (
p_building_block_id=> l_detail_bb_id,
p_attribute_name=> c_proj_attr5,
p_attribute_value=> l_ot_system_linkage_id,
p_app_attributes=> l_tbl_attributes_info
-- END OF PART 1: POPULATE TABLES --
-- PART 2: DEPOSIT TIMECARD --
-- Now we call the deposit process, passing in the PL/SQL tables we just
-- created and populated
hxc_timestore_deposit.execute_deposit_process (
p_validate=> FALSE,
p_app_blocks=> l_tbl_timecard_info,
p_app_attributes=> l_tbl_attributes_info,
p_messages=> l_tbl_messages,
p_mode=> 'SUBMIT',
p_deposit_process=> 'OTL Deposit Process',
p_timecard_id=> l_new_timecard_id,
p_timecard_ovn=> l_new_timecard_ovn
-- END OF PART 2: DEPOSIT TIMECARD --
END;
COMMIT;

Display multiple values for a characteristic for Equipment.

Hi is there any way to display multiple values for characteristics of an equipment. Ex. An equipment (Presss) produces multiple ROH Parts. The class VN_TOOl with charactersistic "Part Produced" . When I run IH08 and execute the query, >Show , hide classification I can only get just one part instead of multiple parts. How do I get multiple values for the characteristic

Yes Chandra,
You are not getting it in IH08, but you are getting it in IE07. See this.
IH08
IE07
If you want the report in the ALV layout, then you need to go for a development using FMs in Classification areas such as:
'BAPI_OBJCL_GETCLASSES' 'ALM_ME_CLASS_CHAR_GETDETAIL'
Jogeswara Rao K

Assigning of characteristics value for a batch

Hi All,
Please help regarding the assigning of characteristics value for a batch in transaction code MSC2N or MSC2 in the classification tab.
If Function modules or BAPI is available pls advise the inputs to be provided for the function modules.
Here is one function module which i searched, but if i run this function module, i am not able to commit my characteristics value.
The function module is CIF_BATCHCHAR_MAP.
For the above function module the inputs which i have given are...
Material number
Batch
Plant
Class type
Class Number
Characteristics name
Characteristics value
Expecting your earliest reply.
Thanks,
G.C.Arravind Kumar Vikram

Try the code below
*.1 create key
it_objects-key_field = 'MATNR'.
it_objects-value_int = matnr.
APPEND it_objects.
it_objects-key_field = 'CHARG'.
it_objects-value_int = charge.
APPEND it_objects.
CLEAR l_objectkey.
CALL FUNCTION 'BAPI_OBJCL_CONCATENATEKEY'
    EXPORTING
      objecttable    = 'MCH1'
    IMPORTING
      objectkey_conc = l_objectkey
    TABLES
      objectkeytable = it_objects
      return         = it_return2.
2 fill it_num it_char it_curr with values
3 change characteristics
CALL FUNCTION 'BAPI_OBJCL_CHANGE'
    EXPORTING
      objectkey          = l_objectkey
      objecttable        = 'MCH1'
      classnum           = it_class-classnum
      classtype          = '023'
    TABLES
      allocvaluesnumnew = it_num
      allocvaluescharnew = it_char
      allocvaluescurrnew = it_curr
      return             = it_return.

Regarding characteristics subordinate values

Hi gurus
I have a requirement
I have a characteristics with two values and each value have 4 subordinate values, my requirement is
eg say 10_1000 with subordinate values as 10_1001, 10-1002, 10-1003, 10-1003
and 20_2000 with subordinate values as 20_2001, 20_2002, 20_2003, 20_2004
this is one characteristcs
now i have a charactertics for price like two values Pice1 and price2 now the requirment is
supoose if i selection of values with subordianate is from as 10_1000 - 10_1001,10_1002, 10_1003 and 10_1004 the price 1 should come as default and for the recpective another price 2 i want to fix like this
how to do that
Thanks in advance

Hi Rajesh,
Was you problem resolved? If so can you tell us all how did it as it helps us also.
Thanks,
Manjula.S

Create subordinate values for Characteristics

Similar Messages

Maybe you are looking for