Characteristic Update

Hi experts,
The SAP module which I work on is DMS u2013 Document Management System.
1)     We use u2018Classificationu2019 to classify the document.
2)     For documents we use the class of type 017. This class will have u2018characteristicsu2019 (ct04)
3)     Document when created, will have those characteristics.
4)     Now I have 2 documents. These documents are in parent and child relationship.( The characteristics need not be same for both.)
5)     In the child document I input a value to a characteristic. As soon as I input the value and save the document, a characteristic in the parent document should be updated with a value.
Please let me know any FM for updating the characteristic.
Regards,
Rohan

Hi pravin,
Could you help us how did you resolve the issue of characteristic upload with sales order.
I am still struggling with this.
Please give me some example of raw data how u did to upload.
Needing help badly.
Regards
deepak

Similar Messages

Dependent characteristic Updation using QP02

Hi ,
Could you please help me regarding updation of dependent characteristics in the transaction QP02.
My requirement is i will give the plant and group and material no in the first screen and i select the first entry and i will click inspection characteristics in the appl tool bar and then i will select master inspection characteristics and i have to press dependent characteristics update
to update
diameter,unit of measurment.... based on material assignment. CAn i use any BAPI for this?
I am using 'bapi_inspectionplan_create ' but it is not update.
If i am using BDC program I am facing problem with selection of line item in inspection charcterisitic based Material Inspection characteristic and
In the Dependent characteristic i am updating based on Customer Number .But how i can select the particular line item based on customer number.
If you anybody know the solution please help to me .
Regards
Nandan.

Hi,
We have more than 10000 entires its not possible using this Transaction .
Can anybody help me regarding solving my problem.
Regards
Nandan.N

Characteristic updation in copa

Hi All,
Please help me in updating characteristic in COPA document
Client Requirement is: They want Date of Sale should be updated in copa document. Date of sale is document date in the sales order.
My issue: How should I update this date into copa document.
Because the document date in VBAP table is grey so I cannot use this feild.
Please tell me the solution for the same.
Thanks & Regards,
Reva.

Hi,
SAP strongly recommends not to use any date as a characteristic. The CE4XXXX (XXXX = operating concern) table basically holds a unique PA segment no for a unique combination of characteristics
. For example let us say you have only 2 characteristics customer and product. Then let us say for customer 1 and product 1 you have PA no 1; for customer 2 and product 2 PA no 2 and so on. Every time you post a document with customer 1 and product 1 the same PA no 1 will be reused
i.e. no new entry will be made to CE4.
Now if you were to introduce a new characteristic called date in this table then every time the date changes a new PA no will have to be generated and the entries in CE4 table will grow. This will make
reporting more difficult and will also cause performance problems.
The harm caused by this characteristic on your performance will far outweigh any benefits that it might have on your profitability analysis.
I request you to think of dropping the idea of having this characteristic. The final decision is yours.
regards
Waman

MIC update in QM - LIMS interface

Hi friends,
I am working with QM - LIMS interface. I am getting a problem for characteristic update in SAP specifically for 04 lots. The detailed descriptuion is as follows:
Plant: 1000; Tasklist Group: 1 Tasklist Usage: Universal ;
so that my tasklist and MIC for a material are same despite of lot origin.
Now say for a material A (all lot type) results and UD with above combination is getting updated through interface, but for a material B with above combination data is updated for 01, 03, 09, 07 etc lot origin but
for lot origin 04 I am getting a pop up in QM saying valuate the non valuated characteristics manually, which prevents data uploading from interface.
Can anyone help me on this issue?
Thanks in advance
Regards
Vrish

I'm going to go out on a limb here and suggest that your looking in the wrong place for this issue.
If your using the same inspection plan for multiple materials and it works with them, and it works for the same material across inspection types then I think there might be an issue on the LIMS side, not SAP, as most LIMS interfaces provide the valuation to SAP.
The only other thing is to double check the inspection type settings in the problem material against a material that is working. Some settings in the inspection type can preclude automatic valuation I believe. But if these are identical settings, then I think you need to look close at LIMS.
Craig

Launch of new NW2004s-BI Frontend from transaction rrmx

Hi,
my customer has upggraded to NW2004s. We are on Support Package 7. The NW2004s-BI Frontend is FEP701.
When I enter transaction <rrmx> the "old" BW 3.5 Bex Frontend launches.
Is there a way to have <rrmx> call the new NW2004s-BI frontend?
I have been toggling the "Launch Legacy Version from RRMX" flag on and off in the new NW2004s BI Frontend but nothing but the 3.5 Analyzer lauches?
Can you help with that issue?
Thanks
Christian

Hi Christian! in this reply you could find your solution.
 but attached file is available only by OSS!
If you think this helps, don't forget give me points!
see note 933768
Symptom
Error in Business Explorer Components like Analyzer, Report Designer, Web Application Designer, Query Designer, Open/Save Dialog, Value Help Dialog
Other terms
Business Explorer, Frontend, BW, BI 7.0, BI, Hotfix, advance correction, Analyzer, Report Designer, Web Application Designer, Query Designer, Open/Save Dialog, Value Help Dialog, Selector, characteristic restriction, filter, filter value, variables
Reason and Prerequisites
You have installed NetWeaver 2004s BI Add-On Frontend Patch 700, and you need a hotfix (advance correction) for certain problems that are caused by the BI Add-On (frontend).
This note will be updated as solutions for newly detected problems are available. Hence you should check the actuality of this note, if you have already applied hotfixes for the patch level of your BI Add-On.
Solution
Attached to this note you will find frontend components (DLL files) that correct certain errors. You will find a list and descriptions of solved problems in the following. It is recommended to replace all respective DLLs in the setup directory of the BI Add-On with the attached DLLs. However, you can also selectively replace individual DLLs that are required for the solution of problems that you encountered. In the following it is described which DLLs are required to solve specific problems.
The Open/Save dialog and the Value Help dialog (selector) are components that are used by several SAP Business Explorer applications. Hence, if you encounter errors in one of those applications, please also check the dialogs sections below for a solution.
SAP Business Explorer Web Application Designer
SAP Business Explorer Analyzer and Variables Screen
New property to adjust the size of the Drop-down item added.
Known errors occuring, while entering the values in variable screen pop-up, have been corrected
SAP Business Explorer Query Designer
Corrected critical error at saving of reusable elements (especially evident with calculated key figures using variables). We strongly recommend to apply this hotfix.
If a presentation hierarchy is selected for a drilldown, it is not possible any more to restrict the characteristic to a hierarchy node from another hierarchy.
Refresh problem solved with repeated query execution in web browser.
Dimension preview is enabled again and allows scrolling.
Problems with query variable order presentation and editing are solved.
Structure member selections using calculated key figures display further calcuated key figure properties.
Error with characteristic value variables replaced by queries corrected.
Errors with structure member descriptions corrected.
There were too many characteristics offered as aggregation reference for formulas. Now only characteristics of the corresponding InfoProvider are listed.
Paste of multiple characteristics when restricting structure member selections is working again.
Error when creating structure member hierarchies with formulas is solved.
Copy and paste of a structure member without changing the focus was not possible. This is now enabled.
Variables could not be entered in the editors for conditions and exceptions. This is possible now. Also variables for key date can now be entered.
Error when adding attributes by drag and drop corrected.
Sorted display of query elements corrected.
Paste of a second reusable structure enabled again.
It is not allowed to restrict a structure member to a characteristic value if the other structure already contains a restriction of this characteristic. This check is now implemented.
Sometimes values for Zero Suppression were not correctly saved. This is corrected now (updated 04 May 2006)
Restricted and Calculated key figure folders did not display if the user started Query Designer more than once from Analyzer. (updated 04 May 2006)
It was not possible to delete a Characteristic from filter if a reusable filter contained this characteristic (updated 04 May 2006)
Paste of InfoObjects and reusable Elements was errorneously possible to Exception and Condition area. Is frobidden now. (updated 04 May 2006)
Text variables with repalcement path are now always not inputable (updated 04 May 2006)
Variables were not displayed correctly if the user started Query Designer more than once from Analyzer. (updated 04 May 2006)
There could be a runtime error (occasionally) in Anaylzer after user selected "Exit and use query" in Query Designer due to a still processed error check. (updated 04 May 2006)
There is now a check if a presentation hierarchy exists on server. If not, the user is informed by a warning (updated 04 May 2006)
New warning informs user about non existing presentation hierarchies (updated 15 May 2006)
Formula variables with replacement path "by attribute" offer now only numerical attributes. (updated 15 May 2006)
Empty formulas now cause an error message, not just a warning message, because queries with empty formulas are not executable. (updated 15 May 2006)
For compounded characteristics in InfoProvider tree the compound info was not displayed in all cases, this is corrected now (updated 15 May 2006)
Variables replaced by query result or by a replacement table can be just used in Filter. The user is informed by an error message if such variables are used anywhere else (updated 15 May 2006).
Queries with cell were sometimes saved with wrong coordinates for cells. Such queries are not executable. This is corrected now. Wrong queries are auto corrected, if they are loaded and saved with this corrected version (updated 15 May 2006).
Problem with "hanging" explorer during execution of a query in web solved (updated 15 May 2006).
Variable order setting is now also possible for new queries (updated 15 May 2006)
Empty structures cause now an error message, not just a warning message, because queries with empty structures are not executable. (updated 15 May 2006)
There were some cases where Text variables were not stred correctly and as a consequence not replaced. All known issues are now corrected. (updated 15 May 2006)
With this hotfix the Note 948374 should be also implemented in the backend system, it prevents some save prolems.
Small usability improvements in Varible-, Exception- and Condition editor (updated 23 May 2006)
Multiple keyfigures are not allowed in Filter, but it was possible to do this with copy and paste of multiselected keyfigures (updated 23 May 2006)
There were cases where users could create different components with same technical names, this is checked now (updated 23 May 2006)
Variables replaced by query result or by a replacement table reported an incorrect message if they were defined with "Input allowed = true", this is corrected (updated 23 May 2006)
SAP Exit variables were errorneously not allowed to be used in non content systems, this is corrected (updated 23 May 2006)
In variable editor for Formula variables replaced by attribute value there were not offered all possible numeric variables offered. This caused a runtime error if especially variables created with Query Designer 3.x were edited. This is corrected now (updated 23 May 2006)
Due to a program error any saved formula might have been saved incorrectly, if it is using any variables (formula or text variables). This is a critical error which might lead to not understandable error messages during query execution or missing text variable replacement for formulas. The error is corrected the was that any corrupt query can be loaded and after a save it is repaired. We strongly recommend to use this hotfix for all installations!
SAP Business Explorer Report Designer
Introduced Versioning and added Version checks. More recent versions of Report Designer are able to design reports with new features. If such a report is edited with an older version of Report Designer some design features might be lost in the report or loading the report might not be possible.
Images from Mime repository can be added to the report.
Sequence of Report Sections is saved and loaded in the right order.
Query Text Elements for more than one Dataprovider are correctly dsiplayed in the Report Item. Property Dialog shows the name of the Dataprovider of the selected Text Element.
Conditional Formatting for Hierarchy nodes enabled.
Open Dialog/Save Dialog
Value Help Dialog (Characteristics Restriction/Filter Selection)
Search can be performed by entering the search criteria in value help dialog and then by pressing the <Enter> keyboard button
or see note 929632
Symptom
There are errors in Business Explorer components such as Analyzer, Report Designer, Web Application Designer, BEx Query Designer, Open/Save dialog, input help dialog.
Other terms
Business Explorer, Front end, BW, BI 7.0, BI, Hotfix, advance correction, Analyzer, Report Designer, Web Application Designer, BEx Query Designer, Open/Save dialog, input help dialog, selector, characteristic restriction, filter value, variables
Reason and Prerequisites
You have installed NetWeaver 2004s BI Add-On Front End Patch 02 and you require advance corrections for certain problems that are caused by the BI Add-On (front end).
Solution
You can find front end components (DLLs) that correct the errors described below attached to this note. We recommend that you replace all attached DLLs in the setup directory of the BI Add-On. However, you can also replace only those DLLs required to correct a problem that occurred in your system. The following sections describe which DLLs correct which problems.
The Open/Save dialog and the input help dialog are components that are used by several SAP Business Explorer applications. Therefore, check whether the correction of a problem that occurred in one of the applications is described there.
SAP Business Explorer Web Application Designer
 Up to now, there are no advance corrections.
SAP Business Explorer Analyzer and variable screen
 To correct the problems in the Analyzer and the variable screenthat are described here, the files BExApi.dll, BExAddin.dll, BExAnalyzer.xla, BExVariableScreen.dll, BExLocalFormulaParser.dll, BExQueryDesigner.dll, BExSelectorAPI.dll and BExSelectorDialog.dll are required.
In the variable screen, the formats for the calendar year and calendar month characteristics have not been transferred correctly to the server. As a result, error messages occurred during the check.
When deleting an item in design mode, the system did not remove the displayed data of the item in analysis mode, rather it still displayed this data.
The display of the checkbox item and the radio button item has been corrected.
Errors occurred when you saved variants on the variable screen. All known errors have been corrected.
The security certificate for the Analyzer has expired and the advance corrections contain a new security certificate.
SAP Business Explorer Query Designer
 To correct the problems in the Query Designer that are described here, the files BExQueryDesigner.dll, BExSelectorAPI.dll and BExSelectorDialog.dll are required.
Executing in the Web no longer opens different browser windows, rather the system always uses the same one.
In certain cases, queries that contain attributes were not saved correctly and as a result, they could not be loaded. This problem has been corrected in all known the cases.
In certain cases, queries that contain cells were not saved correctly and as a result, they could not be loaded. This problem has been corrected in all known the cases.
If queries are saved incorrectly (for example with incorrect attributes or incorrect cells), the system issues messages for all cells that are incorrect and it refers to a possible solution. Currently, all text messages are in English and they will be translated in Support Package Stack 8.
You can now insert and resort attributes at any position. You can do this using drag and drop or cut and paste.
Formula variables with replacement path now also permit the setting of the dimension.
If you edited attributes for an object and you then saved your changes immediately without exiting the field, the system did not save the change in this field. This problem has now been corrected.
Texts of attributes are now displayed correctly after you load the query again (up to now, the system displayed only technical names).
Constant selection was not displayed correctly in the context menu of a selection. Now, the system displays a checkmark to indicate that constant selection is activated.
Attributes of display hierarchies are now displayed and saved correctly.
The system no longer displays operators twice in technical names in formulas. Up to now, [+] + was displayed.
The system no longer displays UIDs as technical names for structure items and cells in formulas.
Structures with hierarchical structure items: In certain cases, structure elements disappeared during the hierarchical setup. However, these were saved and they caused an endless loop on the server. This problem has been corrected. You can use the BEx Query Designer to open queries that were saved with these "vanished" structure elements and the "vanished" structure elements are displayed again.
Errors and terminations on the server now cause a message in the message window of the BEx Query Designer telling you to close and to restart the BEx Query Designer.
For variables with replacement path, the system displayed too many characteristics (some technical characteristics) for the replacement characteristic. This problem has been corrected.
Further consistency checks have been implemented and the corresponding messages are displayed in the message list. The system now checks not only queries but it also checks restricted and calculated key figures, variables, and cells.
If you change a reusable element, the system does not save it automatically. An information message is displayed telling the user that saving the element may affect other queries. You can save the element normally using a save function in the context menu. If the element is used in the query, it is always saved with the query.
When you exit the BEx Query Designer, the system checks which reusable elements have not yet been saved. The system displays a list containing all unsaved elements and it asks the user whether these elements should be saved.
There is a new menu function "Save All" that saves all changed reusable elements.
When you select text variables, the system now displays the correct variable type "Text variable" in the selection.
You were able to use cut and paste for conditions and exceptions, but this always caused a runtime error. The functions have been deactivated for the moment to avoid program terminations.
You can now define variables with a replacement from an attribute.
You can now also display only posted values in the value help (read mode D).
For text and formula variables with replacement path, you can no longer create on the technical characteristic 1TEXT or 1FORMULA. Any existing variables (that were created with earlier versions) are reported as incorrect and you should delete them.
For restricted or calculated key figures or for variables, if you made changes and you saved these changes online and confirmed with OK, the system sometimes issued message "Not saved - object is not changeable". This problem has been corrected.
When creating new reusable elements, the system only checked if the user was authorized to create new elements for this InfoProvider, but it did not check whether the user was authorized to create elements with the given technical name. This problem has been corrected.
You can now move and copy cells using cut and paste and copy and paste. Unfortunately, you still cannot use drag and drop.
In formulas, multiline headers of structure elements are correctly displayed in single lines and no longer in several lines.
In certain cases, hierarchy node variables were saved without a corresponding hierarchy assignment and you could not use them in the report that was being executed.
After each time you saved data, the context menu of the currently selected object was incorrect. This problem has been corrected.
You could not delete filter values directly in the BEx Query Designer, rather you had to do this in the filter dialog.
You could not change characteristics of attributes.
The system now issues a corresponding success message after each successful saving process.
SAP Business ExplorerReport Designer
 Up to now, there are no advance corrections.
Open dialog/Save dialog
 Up to now, there are no advance corrections.
Input help dialog (characteristic value restriction/filter selection)
 To correct the problems in the value help dialog that are described here, the files BExQueryDesigner.dll, BExSelectorAPI.dll and BExSelectorDialog.dll are required.
You can now edit variables in the value help for all variable types and not only for characteristic value variables.
You can now create variables in the value help for all variable types and not only for characteristic value variables.
When changing an offset, negative offsets are displayed as -5 and no longer as 5-. Variable offsets are displayed directly in the right area of the value help.
Variables as the to-value of intervals no longer cause terminations.
In the value range editor, the value you entered manually was not transferred if you directly chose the transfer arrow.
In the value help for reference characteristics, the system did not display the variables for basic characteristics and therefore there were usually fewer variables than in the BEx Query Designer.
When you select the hierarchy, the system now correctly displays the date and version variables and no longer hierarchy variables as was incorrectly the case before.
When you call the value help from the variable entry screen, the system sometimes displayed all master data values (read mode "M") even though it should only display posted values (read mode "D"). This problem has been corrected.

Batch Characteristic not updating with result for linked MIC

Hi,
I have created a MIC and linked to a batch characteristic i.e. potency and included the characteristic in a specific batch class. This MIC is part of the inspection plan for a certain material.
If I generate a lot of origin 01 and 09 for the material and record a result for the MIC and apply a UD, the batch characteristic is not updated with the result recorded in the batch master record..
If I generate a lot origin 89 for the same material, when the result is recorded for the MIC and apply a UD the batch characteristic is updated with the mic value in the batch master record.
Can you help regards?

Ok. I am a little bit further.
I put a trace (ST05) on the result recording and I find a difference between 4.7 and ECC6.0.
In ECC6.0 I've an deletion in table "AUSP". This deletion isn't performed in the 4.7 system.
Hope that this can help to solve my problem.
Regards,
René
@ Mayank
Above, all the master data and customizing is mentioned to transfer the result to the batch classification
Edited by: Rene Fuhner on Jul 30, 2010 7:03 PM

Batch characteristic in classification not updating

Hello expert,
I have created classification for batch (class type 023) with characteristic MCH1 -LWEDT to record last GR date. Batch number has to be entered manually during GR posting. And i expect that during GR posting, characteristic value of GR date will be automatically updated in the classification but i've found that it is blank.
My query is, do GR date in characteristic value of batch class can be automatically updated during GR posting?
If it yes, what's wrong with my class? and how to make it works as expected?
Really appreciate your help.
Thank you in advance

Hi Rahul,
Just to make sure. Have you created a characteristic named MCH1-LWEDT or have you actually linked your characteristic to the field MCH1-LWEDT in the "Addtnl Data" tab in CT04?
BR
Raf
Edited by: Rafael Zaragatzky on Aug 5, 2011 1:03 PM

How to update sales order number (KAUFN) characteristic in the profitability segment of the PA document created at the time of service entry sheet confirmation, as a result of shipment cost document

Hi,
We have a scenario wherein we create shipment cost documents against delivery. As a result of shipments fully transferred, a PO for freight vendor is automatically created and a service entry sheet confirmation happens. As a result of service entry sheet confirmation, we have Financial accounting, Controlling and profitability analysis documents created. We have a requirement wherein we need to have the characteristic “sales order number (KAUFN)” populated in the profitability analysis document created as a result of service entry sheet confirmation.
Could someone please advice how could this be attained in COPA. Thanks for your help in advance.
Regards,
Sandeep

Hi Ajay,
Thank you for the quick update.
The document is updated to COPA through OKB9 settings. The profitability segment is updated with fields like customer, product, company code, plant, sales area data, profit center, etc; however the sales order number is missing.
Could you please elaborate further how could FI substitution be implemented to call for the FM COPA_PROFITABILITY_SEGMENT through user exit? Are you recommending the substitution through GGB1? What could be the possible validation to call for the user exit to be implemented?
Regards,
Sandeep Kulkarni

BAPI to update a single characteristic in IE02

Hi,
I am trying to update a single characteristic in IE02.I am able to do that with the BAPI "BAPI_OBJCL_CHANGE",but this BAPI is updating only 1 characteristic and is initializing all the remaining characteristcs.
Any pointers on this is highly appreciable.
Navin

Hi,
the documentation of the bapi says:
Caution
This BAPI only changes the parameters of an existing assignment (or creates a whole new assignment), but it does not delete the assignment to a class and replace it with an assignment to another class. If you want to reassign an object, the old assignments must be read with BAPI_OBJCL_GETCLASSES and deleted with BAPI_OBJCL_DELETE, then the new assignments must be created with BAPI_OBJCL_CREATE.
The information transferred by this BAPI replaces all old information. An empty field means "delete entry!", not "no change".
This BAPI does not change the database. To change the database, call BAPI BapiService.TransactionCommit afterwards.
You can only use this BAPI for objects that are not classes!
This BAPI only processes assigned values for classification - not for configuration
so i guess you have to pass all information you do not want to lose.
i´ve found this as well:
http://www.sapfans.com/forums/viewtopic.php?t=125320
Best regards.
Edited by: Pablo Casamayor on Jan 2, 2009 7:08 PM

Condition type value updation using characteristic value in sales order

Hi Experts,
We are implementing SAP for one of our Spain client. In that one of the Legal requirements is, whenever they are selling the finished products to domestic customers who contain OIL as one of the component then, some additional cost needs to be calculated and collected from customer and which needs to be paid back to Spain Government every month on Region basis.
If OIL is not a component to produce the finished product then, not required to charge the customer additionally.
The OIL content used to produce every finished product will vary based on product characteristic value. Meaning, for some finished product the OIL used will be 2.2 KG and for some products it will be 3.5, 4.3 KG and etc.
Since various combinations of products are available for the client, during sales order creation we are planning to update some special characteristic which the data flow from u201CVariant Tableu201D. In the variant table we are going to maintain the OIL Quantity required making finished product.
But we are not sure how to activate a new condition type with the value fetched in the special characteristic. This new condition type needs to be activated based on this characteristic value and multiplied with total order quantity and price to charge from customer.
Example, the special characteristic fetched the value of 2.2 KG based on variant table. Total Order quantity is 10 PC and charge is 0.06 EURO per KG. in this case, (2.2 x 10 ) x 0.06 EURO = 1.32 EURO
I need the expert opinion how to activate the new condition type based on characteristic value and achieve the above requirement.
Thanks in advance.
Warm Regards,
VEL

Hello,
I have replicated the whole requirememt in IDES and getting the price calculation as needed but the only issue with the Conversion factor for the condition type. Either you need to maintian the conv factor in material master or need to enter manually for the condition type in SO. Some how you have to maintain the conversion factor to calculate the price for the condition type in different unit.
For easy of understanding Lets make the whole requirement in 2 parts
Part - 1
Oil qty calculation. For convenience sake I have taken oil qty also in TO
1) Created a num char OIL_QTY1 with length 9 and decimal places 5 and UOM as TO
2) Created Variant table to infer the OIL qty in TO per piece of finished prod ( This oil qty data may be depends on various factors). For certain Finished products the oil qty may be 0 or blank
3) Created a REF char SO_QTY to pull the SO qty to configuration and add this char in class 300(Table:VBAP,Field :KWMENG)
4) Created another char SO_OIL_QTY (Num with length 9 and decimal places 5 and UOM as TO)
5) Created a PROCEDURE say PROC_SO_OIL_QTY with code
*$self.SO_OIL_QTY = $self.OIL_QTY1 * $self.SO_QTY*
6) Create another PROCEDURE as mentioned earlier with modified code
$SELF.A_VARCOND = 'TEST_001' if OIL_QTY1 specified,
$SET_PRICING_FACTOR ($SELF,A_VARCOND,'TEST_001', SO_OIL_QTY)
Note: Maintain proper seq of the procedures in profile. The Qty cal proc should be before the price related procedures.
PART-2
1) For the condition type maintained 60 EUR per TO (0.06 EUR per KG)
Now if you create SO for the Finished product of 10 PC
the Char values will be
OIL_QTY1 = 0.00022 TO (inferred from Variant table th proc)
SO_QTY = 10
SO_OIL_QTY = 0.0022 TO
Get into conditions tab
Here Condition type ZSIG will be displayed as error with Amount 60 EUR per TO and condition value will be blank. Just enter value 1 in the col NumC and CCon fields.
Now the Condition value will appear as 1.32 EUR.
Hope this gives some more clarity
Regards
Brahmaji D

User exit to update characteristic attributes in sales order

Hi all,
I am having one queer requirement.
We are having variant configuration. We are manufactiuring a material which is having lenght as one of the characteristic.
While creating the sales order the user will enter the value against length. This we have to pull in the inspection lot with range.
For ex. if the length required by customer is 1000 mm then depending upon the tolerance limit say +/-1.5 %, another characteristic should get updated with the allowed range (here in this example the lower range 985 and upper range 1015) against another characteristic.
This characteristis will sever as class characteristic for QM master inspection characteristic.
Here the problem is the functionality can't be mapped with object dependency in satandard SAP (you can't derive range with object dependency), so I am looking for user exit to update the second characteristic depending upon the value of first characteristic and allowed percentage.
The user exit should be effective for sales order creation as well as sales order change.
Please help.

Hello Nikhil,
I am looking for the tolerance limit to upadte against one char only and not two separate chars.
If the range is against only one char (and that too again in numeric format and not characteristic format) same shall can be pulled against master inspection characteristic in inspection lot.
Looking forward for the soution.
Mimiri

Auto Update of characteristic values in PO from SRM.

Hi,
For Configurable material we have characteristics values.
Material is configurable material with material type as services.
Same ECC material is replicate in SRM.
Create Shopping cart in portal SRM EBP for Multiple line item for material. Each material item will have different characteristics value.
Currently User attaching excel sheet with different characteristic value in Shopping cart.
Once Shopping cart no is created and Shopping cart no goes for approval.
Once approved, PR is created automatically.
Attached document is available in PR.
Buyer has to maintain manually characteristics value for material in Purchase order (PO) for each material item.
Is any way to Update Characteristics values in PR automatically when saving?
Regards,
Swapnil

check if the condition is marked as statstical one in the pricing procedure

Best practice for updating ATWRT (Characteristic Value) in AUSP

I've notice that when we change the Characteristic Value of a Classification, that it does not update in the MM record. We have to go into MM02 for each material number that references Char Value and manually change it for row in AUSP to get updated.
Should i just create a report to Loop through and update table AUSP directly? Or is there a better way to do this via a function or BAPI etc? Wanting to know what best practice is recommended.

Hi Scott
You can use a BAPI to do that.
Check the following thread:
BAPI to update characteristics in Material master?
BR
Caetano

Not able to update more than 10,000 records in CT04 for a characteristic

Hi all,
We are not able to update more than 10,000 records in CT04 for a certain characteristic.
Is there any possible way to do this?
Please advise...its a production issue.
Thanks.

Hello ,
Please consider using a check table for the characteristic involved if you are working with large
number of values assigned
With a check table you have a possibility to work with a huge amount of values , also the performance should improve
Please refer to the link
http://help.sap.com/saphelp_erp60_sp/helpdata/en/ec/62ae27416a11d1896d0000e8322d00/frameset.htm
Section - Entering a Check Table
Hopefully the information helps
Thanks
Enda.

Function Module to update Characteristic Value (AUSP table entry)

Looking for a function module/BAPI to update a characteristic value (AUSP table entry).
This is for a material master Material classification value, not a Variant Config value that I need to update.
Anybody have one? I have one that will find the value, but not change it.
Thanks.

That wasn't it, but it gave me the one piece I was missing.
Answer is:
Function Module "CLAE_CLASSIFY_OBJECT"
In CHANGE_KSSK
M = 0
KLA = (Class Type)
OBJEK = (Material Number for the Material Characteristic being changed)
OBTAB = MARA
CLASS = (Class Name with Characteristic to be changed)
S = 1
S = (blank)
AENNR = (EC Change Number or Blank)
DATUV = (Today's Date or date for change)
C = "X"
In CHANGE_AUSP
OBJEK = (Material Number for the Material Characteristic being changed)
ATINN = (Chararacteristic to be changed)
M = 0
KLA = (Class Type)
ATWRT = (New Value for Characteristic)
C = X

Characteristic Update

Similar Messages

Maybe you are looking for