If I can't use compound characteristics ( in case of Material , for example) , how can I have different value for atributtes that depends on organizational levels? Such as MRP Type or Materials group?
In few of my projects the same problem we have handled by introducing a new characteristic in the CVC which will be derived by concatenating the product and sales org. This characteristic we will not use for planning purpose and will only be used for maintaing those attributes which are product and sales org specific.For example say one SKU P1 is a new sku in sales org S1 but the same SKU is selling from a long time in Sales org S2. suppose we have an attribute NPI(New product introduction) .In this case the NPI will be X for new characteristic for sales org S1 and blank for S2.
I have two different sales org. I need to use Material Pricing group as an atribut in Demand Planning (for agregattion , selection,..so on) but I have different values for the same Material depending on the sales org. I'm using a compound characteristic CMATER for materials in order to be able to have different values of this atribute depending on the sales org (As we do in BW) . Now I guees I can't use it, so the question is, how can I manage to do it if I can't do it this way? You konw what I mean?
Example: Material A- Sales Org. 1000- Material pricing grp.01
Material A- Sales Org. 2000- Material pricing grp. 02
Please refer the following thread about compound characteristics -
So, Compound characteristics are not supported in DP. For your issue, you use simple characteristics for Material and Sales org. For sales org. characteristic, you can maintain Material pricing grp as the navigational attribute. Then based on the Material pricing grp, you can do selection and aggregation in Planning book.
I have worked with DP Planning area having Compound Characteristic in my previous project. But to my surprise, when we had opened a OSS msg to resolve some issue with our DP planning area, SAP informed us Compound Characteristics are not supported with APO Demand Planning and they will not be able to support this message. Fortunately we could resolve that matter ourselves. I suggest you please verify and confirm this point again and plan accordingly. If others has similar experience they can comment as well.
I think Manimaran has valid point. You can handle this requirement by creating Naviation Attribute as Material pricing grp to Sales Org Characterisics.
Sorry, but if I mantain Material Pricing Group as a navigational attribute for Org. Sales, how can I manage to have two different values for different materials?
F.Ex:
Materials A Org. Sales 1000: Material pricing Group 01
Material A Org. Sales 2000: Material pricing Group 02
Material B Org. Sales 1000: Material pricing Group 03
Exactly what are you trying to analyze? Sales orders? Doesn't the source where you are getting your key figures also have your Material Pricing Group in the data?
we are using Compounded Characteristic within our APO DP implementation. In fact SAP is "strongly recommends against the use of compound characteristics" because of perfromance problems. But because of the same reasons you have mentioned we are using them!
The only way to avoid Compounded Characteristic is to generate different characteristic combinations for example fpr every plant material combination:
material 4711 | plant A | keyfigure
material 4711 | plant B | keyfigure
An other option is to concaternate the key parts material plant into one characteristic value:
material + plant -> matplant
4711 A 4711_A
We decided that Compounded Characteristics are a valid technology within BW and we are using a couple of them without trouble.
I did not come across any issue with Life Cycle Planning dur to usage of Compound Characteristic in Planning Area. What is the issue you are facing with Life Cycle Planning ?
When we try to use a Compounded Characteristic in defining basic settings for Life Cycle, the systems displays an error that says: 'Characteristic C_MATER can not be used, it is compounded.'
Yes, In Basic Settings you cannot have compound characteristics while configuring Life Cycle Planning. But work around for this to have another characteristics in PA which can do the trick.
Example -
MATERIAL - Product Charact.
MATCUST - which is Material + Customer forms my Compound Charactristic.
CUSTOMER - Customer.
You can define Basic setting with MATERIAL and CUSTOMER, this should take care of your requirement.
I have a similar situation where my client has a requirement to segment two characteristics , to enable the Automatic Statistical Forecasting without creating the selection Id's. Will concatenating help me resolve this issue? And also how can I show the new characteristic in the Planning area.
We have a GAP for Demand Planning that is about u201CSEGMENTATION through COMPOUND ATTRIBUTESu201D
Follows some details of this GAP:
We have characteristics such as NSV, ABC, Customer, etc. We would like to segemnt them in order to have easy access for the users instead of making the selection ID's.
One idea is to use Compound Attributes or to concatenate two characteristics. If I concatenate how can I see them in the planning area? If I concatenate does this create additional CVC's?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.