Same Classification
We need to do exception handling for addln data tab when DIR staus got chaned from DR from RA.
For same values at author, owner and approver,
There is one exit(CLCTMS02) available that can be use for to check characteristic values .
But this exit will not trigger incase of Do not check in same classification tab of a class .
So need to activate warning message for class in order to achieve exception handling , and i want to make sure that no other impact by changing this config.
Or Will it impact system performance?
Edited by: nhgoel on Feb 29, 2012 2:12 PM
Hi,
maybe the user exit CLFM0003 and CLFM0002 could be more useful for this issue.
Best regards,
Christoph
Similar Messages
-
Classification - inheritance by batch of material classification
Is there a way to have the classification settings i.e. values, for a material automatically inherited by a batch created for that material ?
And if so:
What are the pre-requisites ? e.g. presumably both objects must have the same classifications
Where are the settings to achieve this and what settings to make ?
ThanksHI,
Check this link
http://help.sap.com/erp2005_ehp_04/helpdata/EN/f2/05c838f2fbb363e10000000a114084/content.htm
Regards
KK -
Insert Classification for customer master
Hi All,
In XD01 when creating customer(SOLD-TO) I have to assign classification of SOLD-TO to all the partner functions (i.e SHIP-TO,BILL-TO, PAYER). To assign classification i am using Userexit exit_sapmf02d_001 and CLAF_CLASSIFICATION_OF_OBJECTS fm.
When i am using this FM i am getting a error "Updation termination of sold-to ".
Can anyone please help me out to figure out y this error is coming.
Or any other place were i can include the code to assign classification.
Regards
venuHi ,
when inserting the classification for sold to (in tcode xd01=>extras=>classification), same classification we need to insert the partner functions also. Can u plz tell me the right place for inserting the classification for partner functions. I have tried in user exit(sapmf02d). when inserted the classification for partner functions its terminate the sold inserting classification(standard functionality). Even i am not calling any standerd functional modules .just i am checking the classification exist or not for partner functions.if does not exist then direct i am inserting the classification into table KSSK.
waiting for suggitions.....
Regards,
Rao. -
Hi Gurus,
1. I have created one contract in CRM and incepted.
2. Then I have applied Change process On that contract same time I have Changed the Classification forcebily and I have incepted the contract now I am able to see Changed classification in CRM but I am Unable to the classification in R/3 it is showing same Classification which is First one not changed one but I am getting Force = X.
3. Please help me in this regard.
Thanks & regardsHi,
You can search an object in class using transaction CL30N and CL31, but you need to know at least the class name or the characteristics for the object.
Phyllis. -
Copy the material classification
Hello,
I have already classified the material and now want to use exactly the same classification for our documents. Therefore I would like to copy the material classes and use them as document classes.
Unfortunately this is not possible and I get the following error message:
"Class types 017 and 001 have different object tables".
Is there another possibility to copy our classes?
Thank you very much for your help.
Regards,
MarkusHello Markus,
refer to www.im-solution.eu/downloads. There you will find a migration tool which provides migration of complete classifications and characteristics to SAP.
1st step:
download (via SE16) the actual classification & characteristics to the database.
2nd step:
change class type at the database.
3rd step:
export classification from database and upload via SAP standard reports "RCC*".
You use only SAP standard technologies => no development required.
brgds
IMCSM -
Dear all,
I am using itunes to control all my music and i like to use my iphone, or my ipad to control my music with the remote app.
But i have a problem: all the music i have in my iphone count as double play.
To explain everything since the beginning, i personally don't like and don't trust at all the music sync capability of itunes.
So i have my music on my pc, and i load every type of music as a single playlist (ex a Pop-Rock folder, with all artists folders and so on, makes me a Pop-Rock playlist).
For my iphone, i created a iphone music folder, with the same classification.
It means that i don't have all my Pop-Rock music, only a selection. But of course the selected music appears also in my complete music collection.
So in itunes i created a folder playlist named iphone music, with inside one playlist by type of music (exemple : Pop-Rock, which contains some files of my main Pop-Rock collection).
So i do have duplicates in my hard drive. But when i selected the playlists to be shared on home sharing in itunes, i selected only the main playlists, not my iphone playlists! But still, when i look for ACDC artist for example, i should see only what i have on my pc, not what i have also on my iphone.
The result is if i play an album for example Back In Black (i have it full on my hard drive, and full on my iphone too), then every song is displayed in remote app in double, and also played in double:
Here is how it is displayed:
Song 1
Song 1
Song 2
Song 2
So the remote app plays Song 1 one time, then Song 1 (the second Song 1) one time and continues like this to Song 2 etc...
I guess that if i put my selection of songs on my ipad, i will then have everything in triple....
It is very annoying. Is there a way for me to change that? Or for an update to be made (based on ID3 Tag) to not play everything twice or more? It would have an ID3 Tag No Double toggle button.
I don't want to select from my main music to send elements to my iphone as doing that i lost a lot of music multiple times. This way of doing is not safe at all (at least for me).
What is possible to do? Is there room for improvement here (i believe so). Is there a way for me to avoir this very annoying effect?
I would really like to put my music to my iPad2 also, but after i'll have triple play....
Thank you for your help.Nobody knows? Not even administrators?
Please it would be really nice to have help on that to take all the benefit of the remote app.
Thank you very much in advance. -
Release strategy for purchase requisition does not kick in
Hi Gurus!
I've been struggling with this issue for some weeks now.
I have set up the release strategy configuration for purchase requisitions with classifications.
However, if I create a purchase requisition the release functionality is not taken into account by the system.
See below some more information regarding my configuration:
1. I've created a new characteristic "REL_PR_GROUP". Status: released, Multiple values, Number of Chars 3, 7 values (TR1, TR2, TR3....TR7), Table name: CEBAN, Field name: EKGRP, Procedure for value assignment set to not ready for input.
2. I've created a new class: "REL_PR_ANPC". Class type 032, Status: released, Same classification: do not check, Char: "REL_PR_GROUP"
3. I have one release group "T1", Rel. object 1, OverReqRel is marked, Class: "REL_PR_ANPC"
4. I have 5 release codes. Grp: T1, Code: 01....05
5. I have 2 release indicators:
"R = Released", Rel. for ordering is marked, Changeabil: 4, Value chgs. 100,0
"X = Blocked", Changeabil: 4, Value chgs. 100,0
6. I have 1 release strategy:
"T1 with Grp T1"
- one release group, 01 Manager
- release prerequisites not applicable because of only one release group
- release status, nothing marked = blocked, 01 marked = released
- classification, purchasing group is TR1 or TR2 or TR3 or TR4 or TR5 or TR6 or TR7
I intentionally kept the configuration as simple as possible so I can try to get it working first.
Now if I create a purchase requisition for an item with release group T1, I would expect the release strategy to be activated. However, this is not the case. I don't see the "release status" tab in the PR, and if I try to relase via ME54 the system says the PR is not relevant for release.
Could you please assist in getting this working?Hi,
Have you checked in CL30/CL30N if your release strategy is derived successfully?
See section 3 of Note 365604. A small section of it:
You can use transaction CL30 search for an object using the data
of the purchase requisition/purchase order. Here, it is important
that the object search determines exactly one strategy. If this
is not the case, this indicates that there are overlapping
strategies in the system or that the release strategies in
Customizing do not correspond with those from transaction CL24.
See the previous point. If the object search returns more than
one result, the system subsequently determines an incorrect
release strategy or no release strategy at all.
If it is derived successfully, next, check the user exit EXIT_SAPLEBND_001 as per Note 371667:
The following assignment statement has to exist within activated SAP
enhancements M06B0002 (include zxm06u13) and M06B0005 (include zxm06u31)
for purchase requisitions:
E_CEBAN = I_CEBAN.
Regards,
Purnima. -
Variant Configuration
Variant configuration is for manufacturing complex products in which customer determines the features of the product. Objective of variant configuration is to react quickly to customers' requirements.
Here it needs not to create separate material for each variant of a product. When companies introduce variant configuration this often goes beyond a business process re-engineering project. Variant configuration offers an opportunity to restructure product structures for which then processes are defined. This has a direct impact to the core areas such as marketing and product data management.
2 Advantages of VC
 No need to Create separate material master for each variant combination.
 Super BOM and Super Routing is enough for representing all possible Variants and Operations.
 Able to react more flexible to customer demands.
 Increase Information exchange between sales, engineering and production.
3 What is Configurable Material?
 A material with different features or characteristics and options is known as configurable material. Example: PC, Car.
 Configurable materials are either created in a material type that allows the configuration (n the standard system, the material type KMAT) or they are given the indicator Configurable in the material master record.
4 Master Data used for VC
Following Objects are used as Master data for Variant configuration.
1. Super BOM
2. Super Routing
3. Characteristic
4. Class
5. Object Dependencies
6. Configuration Profile
7. SD Condition records
4.1 Super BOM
Super BOM Contains all the components for producing configurable product. It contains both variant as well as non-variant parts required for producing configurable product.
4.1.1 Super BOM configuration
Super BOM can be created either one of the following methods.
 Create BOM with class Item of 200-class type that contains all characteristic of a configurable material.
 Create BOM with all possible materials as its components. Then assign /define dependencies to each component.
The different between this two method is
 BOM with class item, no need to assign or define object dependencies. Instead of that each material is classified in material master itself using class 200.
 For both cases all characteristics are assigned to class 300 which is again assigned to KMAT material in order to trigger configuration in configuration profile.
4.1.2 Super BOM with Class Item
Class items used to control the selection of variant parts in a BOM. Variant parts are classified in a class, and the class is entered in the BOM as a class item. When you configure the material, the class is replaced by a suitable variant part.
4.1.3 Advantages of using Class Item in BOM
 Only one item for the class is enough, instead of several items for the individual variant parts.
 No need to create and assign selection conditions.
 Able to classify additional objects in the class at any time, without having to change the BOM.
4.1.4 Steps involved in super BOM with Class
Define all Characteristics and its Values assign it to Class with type 200.
Assign characteristic Values to materials by Classification material
Assign class 200 with material instead of assigning all BOM items.
Create and Assign class 300 (with same characteristics) with configurable product using configuration profile.
4.1.5 Super BOM with Material Components
This bill of material (BOM) of a configurable material contains all the components that are required to manufacture the material. The BOM contains components that are only used in specific variants (variant parts), as well as components that are used in all variants (non-variable parts).
4.1.6 Steps involved in super BOM with Material Components
Define all Characteristics and its values assign it to Class with type 300.
Assign Class with configurable material in Configuration profile.
BOM is created with all variant and non-variant items.
Define interdependency between objects (Characteristic, BOM item, Routing Operation etc ) by using Object Dependencies.
Assign class 300 with configurable product using configuration profile.
4.2 Super Routing
A configurable routing describes the production process for all variants of a product. Instead of creating a routing for each variant of a product, you can create operations for one routing, or a "super" routing.
It is possible to maintain Object dependencies for following in super routing:
 Sequences
 Operations/sub-operations
 Production resource/tool assignments
The routing is configured by system, when order is created for KMAT material.
4.3 Characteristic
Characteristic is used to define the features of a configurable material. To enable to use characteristics to configure a material, assign the material to a class of class type 300. The customer can choose from among different options for each characteristic.
 Characteristics describe the properties of objects. The values of a characteristic specify these properties.
 Value assignment to characteristic may be single value or multiple value with required entry or restrict able entry.
 In characteristic it is also possible to use table name and its field name in order to change the Object quantity or values. I.e. BOM item quantity or Operation time, which is known as reference characteristic.
 In Restriction screen allowed Class types are entered i.e. for what are the class this characteristic may used. In general for Variant configuration class 200 and 300 are used.
 It is also possible to assign Dependency to characteristic values maintained in Characteristic.
4.4 Variant Class
 In Variant configuration, Class is used to hold the characteristics that describe about configurable material. Class type to determine which object types can be classified.
 Class is used in variant configuration if the class has a class type that supports variant configuration. In Customizing for Classification, the Variant class type indicator must be set for the class type. In the standard system, this is class type 300.
4.5 Dependencies
 Dependencies restricts the combinations of options i.e. characteristic that are not allowed. It also select exactly the right BOM components and operations to produce a variant.
 It also describe the interdependencies between characteristics and characteristic values
 It control which components are selected from a bill of material (BOM) and which operations are selected from a task list
 It also changes the values of fields in BOM items and operations during configuration.
4.5.1 Global and Local Dependencies
Global dependencies have the following properties:
 They are independent of any object.
 They are identified by a name that you assign, and are maintained and managed centrally.
 If you change a global dependency, the change affects all the objects where the dependency is used
Local dependencies have the following properties:
 They are only available to the object for which you create them
 You cannot use the central maintenance functions on these dependencies, and you cannot allocate them to other objects
 They are identified by a number assigned by the system, not an external name
Local dependencies are only used where certain dependency will not be needed elsewhere
The differences between global and local dependencies are as follows:
 Global dependencies are created centrally and can be assigned to several objects.
 Local dependencies are created for one object and can only be used with this object
4.5.2 Declarative and Procedural Dependency
 In Declarative dependencies the result are explained logically
 Declarative dependencies are easier to trace than procedural dependencies, because the point in time when the dependency is processed and the sequence in which the dependencies are processed are not relevant.
 Example for Declarative dependency:
- Constraint
- Actions
- Preconditions (provided that they contain no non-declarative expressions)
- Selection conditions (provided that they contain no non-declarative expressions)
 In Procedural Dependency result depends on the processing sequence and the point in time when the dependency is processed.
- Procedures
- Preconditions (only if they contain non-declarative expressions)
- Selection conditions (only if they contain non-declarative expressions)
4.5.3 Dependencies Types
The SAP System supports the following types of dependencies:
 Preconditions
 Selection conditions
 Procedures
 Actions (obsolete)
 Constraints
4.5.4 Preconditions
Preconditions can be allocated to the following objects:
 A characteristic that you want to hide
 A characteristic value that you want to hide
Preconditions are used to hide characteristics and characteristic values that are not allowed and thereby ensure that the configuration of an object is consistent. In the precondition, it is also possible define the circumstances under which a characteristic or value is hidden.
A precondition is fulfilled if the condition you enter is either true or not violated.
4.5.5 Selection Conditions
Selection conditions used to ensure that all the objects relevant to a variant are selected:
 Selection conditions determine which variants require a specific component or operation
 Selection conditions determine when it is mandatory to assign a value to a characteristic
Selection conditions may allocate to the following objects:
 Characteristics
 BOM items
 Operations in task lists
 Sub-operations
 Sequences of operations
 Production resources/tools (PRTs)
A selection condition is fulfilled if the condition in it is unambiguously true.
4.5.6 Procedure
Procedures can be assigned to the following objects:
 The characteristic value that triggers the procedure
 The characteristic that triggers the procedure
 The configuration profile of the configurable object
Procedure is used for following purposes.
 A procedure is used to infer a value for a characteristic, you enter the variable $SELF before the characteristic.
 Procedures can overwrite values that are set by other procedures.
 Procedures are always used for pricing (see Variant Conditions).
Processing Sequences of Procedure
If an object has more than one procedure, a processing sequence is used to define the point when the procedure is processed.
4.5.7 Action
Actions are used to infer characteristic values. An action is processed as soon as the characteristic to which it is assigned has a value. It is not possible to overwrite the characteristic values that are set by an action.
The following Objects can assign to action:
 The characteristic value that triggers the action
 The characteristic that triggers the action
 The configuration profile of the configurable object
 Configuration profile
 BOM items to change the quantity
 Operations in task lists to change the standard values
Since Action is lead to serious system performance problems, it is replaced by Procedure and Constraint.
4.5.8 Constraint
This dependency type is mainly for intensively interactive configuration tasks and for configuration tasks in which you need to take into account the dependencies between the characteristics of several objects. The main purpose of a constraint is to monitor the consistency of a configuration.
Constraints have the following distinguishing features:
 Constraints are used to describe the dependencies between completely different objects and their characteristics.
 Constraints are used to store information on which conditions must be fulfilled if the configuration is to be consistent.
 Constraints are not directly allocated to individual objects. They are grouped together to form dependency nets and allocated to a configurable material in the configuration profile.
 In constraints, you enter objects in their general form of expression, without using $SELF, $ROOT, or $PARENT to identify objects. As a rule, you refer to objects in constraints by entering the class to which the objects are allocated.
 Constraints are declarative dependencies. The processing sequence of constraints and the point in time when constraints are processed is not relevant.
 Constraints are not processed in a specific order. You cannot determine when a specific constraint is used.
In any processing situation, a constraint is only processed once. If a value that is relevant to the constraint is changed, the constraint is triggered again.
4.5.8.1 Structure of Constraints
There are four sections in a constraint. Each part is identified by a keyword. A colon follows the keyword. Each section ends with a period.
OBJECTS:
In this section, you enter the objects that are relevant to the constraint. You must enter the relevant objects in all constraints. You can also define variables for objects or characteristics.
CONDITION:
The condition entered here must be fulfilled in order for the constraint to be used. You do not need to enter a condition in a constraint. You can leave out the keyword CONDITION: if required. However, if you enter the keyword you must enter a condition.
RESTRICTIONS:
In this section, you enter the relation that must exist between the objects and characteristics if the configuration is to be consistent. You must enter a restriction in a constraint.
INFERENCES:
In this section, you enter the characteristics for which characteristic values are to be inferred. The main purpose of constraints is to check the consistency of a configuration. Usually, values are only inferred if you make an entry in this section.
For reasons of performance, only use constraints to infer values if it is really necessary. Constraints are grouped together to form dependency nets. The dependency net is allocated to a configurable material in the configuration profile.
4.5.9 Dependency Net:
Constraints are grouped together in dependency nets. For this reason, the variant configuration menu does not support a function for creating constraints directly. So that only constraints are defined within a dependency net.
5 Configuration Profile
The configuration profile for a material controls the configuration process in sales order. Configurable profile also used to define central settings for configuring the object. Using this profile it is possible to hide some of the characteristic value defined during characteristic creation. We can assign any number profile for a configurable material in which selection is based on either priority or manual selection during configuration.
By defining a filter in the configuration profile, possible to determine the scope of the BOM items to improve system performance when exploding the BOM. The filter is active in high-level configuration, in result-oriented BOMs, and in SET processing.
5.1 Filters in Configurable Profile
Following objects can be used as filter:
 Object type
Class, material, document, text
In the standard system, all object types are selected and therefore exploded in the configuration. Deselect the object types that you do not want to be displayed.
 Item category, for example, stock or non-stock item
All item categories in the configuration are exploded in the standard system. Remove the selection for the item categories you do not want to be displayed.
 Item status
You maintain the status of a BOM item in maintain BOM dependent on its usage.
All items are displayed regardless of their item status in the standard system. However, only the items with this status are displayed when you select specific item statuses. Items are not displayed that do not have the selected status.
 Sort string
You can assign sort strings for BOM items in maintain BOM. You can restrict the display of the BOM items by using these sort strings.
Only items that carry sort strings are checked and only those that match are displayed. Items that have no sort string are always displayed.
5.2 Component availability in the configuration profile
The availability check is just a snapshot, telling that whether the materials required are in stock at this moment. Several users can access the same material at once. This means that supply problems can sometimes be overlooked.
Example: Only 2 pieces of a material are in stock, but the material is used in 3 BOMs. The availability check does not detect a supply problem. The availability check for all 3 BOMs shows 2 pieces in stock.
5.3 Process Overview
There are different processes for configurable materials in sales documents. These processes can be defined on the Configuration initial screen tab in the configuration profile, by choosing the Configuration parameter tab.
The Process are described in the following scenarios:
Planned/Production orders
This processing type is used to describe variant products whose configurable materials are assembled using planned and production orders. The bill of material (BOM) can have single-level, multi-level, or no explosion.
Sales Order (SET)
This processing type is used to describe variant products that comprise salable configurable materials. These products are supplied together, but are not assembled in a production order. Only sales-relevant BOM items are exploded in the sales order.
Order BOM.
You use this processing type if you want to make customer-specific changes to the BOM of a material that you configure in the sales order. In the sales order, you assign values to the characteristics of the header material, but the BOM is not exploded in the sales order.
6 Material Variant and Planning Material
6.1 Material Variant
 Material Variant is an material that can arises from individual Configuration of a configurable product and can be kept in stock
 For variants that are required frequently, we can create material variants, which can be produced without a sales order and kept in stock. When a sales order is received, it is possible to check whether the variant required is in stock, so that it can deliver immediately.
 For material variants, a separate material master record is created with a material type that is kept in stock.
 Separate BOM and routing for a material variant, or you can link the material variant to the BOM and routing of the configurable material. The correct BOM items and operations are determined from the characteristic values assigned to the variant.
6.2 Planning Material
 Planning Material is a material, which contains all the non-variant parts.
 By using planning material all non-variants are procured / produced before sales order.
 It is also possible for Planing the Planning Materials without reference to any sales requirement.
 Planning material is planned separately using strategy 65 and produced before sales order creation.
7 Planing in VC
The following strategies are used for planning configurable materials and its variant parts.
Make to Order production of Variants
Make to Order for Material Variant. - 26
Planning Variants without final Assembly- 55
Planning Variants with planning Material - 65
Make to order with configurable material.- 25
Characteristic Planning with dependent requirement - 56 and
Assembly Processing with Characteristic Planning - 89
8 Variant Configuration: (Object Diagram)
9 Variant Pricing and Surcharges
9.1 Sales BOM
A bill of material (BOM) describes the different components that together create a product. A BOM for a bicycle, for example, consists of all the parts that make up the bicycle: the frame, the saddle, wheels, and so on.
When you enter the material number of a bill of materials that is relevant for sales order processing, the system displays the material that describes the whole bill of materials as a main item. The individual components are displayed as lower-level items.
There are two ways to process a bill of materials in Sales. Once you have entered a bill of material in a sales order, the system runs pricing, inventory control, and delivery processing at: Main item level if the material is assembled, or - Component level if the material is not assembled.
9.2 Processing at Main Item Level (ERLA)
If you want the system to carry out pricing, inventory control, and delivery processing at main item level, enter ERLA in the Item category group field of the Sales: sales org. 2 screen in the material master record of the finished product. This means that the components only function as text items and are not relevant for delivery.
9.3 Processing at Component Level (LUMF)
If you want the system to carry out pricing, inventory control, and delivery processing at the component level, enter LUMF in the Item category group field of the Sales: sales org. 2 screen in the material master record of the finished product. In this case, only the components are relevant for delivery. During processing the system automatically creates a delivery group. The latest delivery date among all the components becomes the delivery date for the entire delivery group.
10 Configuration of VC
10.1 Production Planning and Control
10.1.1 Creating Material
Use
The purpose of this activity is to create the material masters for the materials required in this scenario.
Procedure
Access the activity using one of the following navigation options:
SAP Menu Logistics  Materials Management  Material Master  Material  Create (General)  Immediately
Transaction Code MM01
In Material Master of KMAT material following settings are maintained:
 Configurable material indicator in Basic Data must set.
 MRP type is PD.
 Lot size EX ( Lot for lot size)
 Availability check 02
 Planning Strategy 25 is entered in MRP 3 screen view.
 Item category group 0002 or 0004 is to be given in sales view.
10.1.2 Creating Bill of Material
Purpose:
 The purpose of this activity is to create bills of material (BOMs) for the configurable material which is known as super BOM
 Super BOM comprise all the variant as well as non-variant parts required for producing configurable material.
Procedure
1. Access the activity using one of the following navigation options:
SAP Menu Logistics  Production  Master Data  Bills of Material  Bill of Material  Material BOM  Create
Transaction Code CS01
 The Create Material BOM: initial screen appears. On this screen, data that identifies the bill of material are maintained as well effectivity data.
 In the Material field, the configurable material for which super BOM need to create is entered.
 Plant and BOM usage is entered. In general BOM usage 1 for production and 3 is for Universal.
 In Component screen list of variant and non-variant parts are entered along with that quantity is entered based on Base qty. of the configurable material.
 It is also possible to enter a class as a BOM component with item category class Item. This class must hold all characteristics and also classified with each material.
 Class type 200 and 300 can be used as a class item.
Following Procedure is followed for assigning class with BOM as a class Item.
 Enter the item category for class items in BOM.
 Make entries in the fields that identify the class
Class types
Class
 Enter the quantity.
- Enter a unit of measure if appropriate.
- The system determines the unit of measure from the additional data of the class.
- If a unit of measure without a dimension is maintained in the additional data of the class, you cannot change this unit.
10.1.3 Creating Characteristic
Purpose:
 Characteristic is created with possible values.
 It is also possible to use table name and its field name in order to change the Object quantity or values. Ie BOM item quantity or Operation time. This is known as Reference characteristic.
 For changing BOM quantity Characteristic is created with table name STOP-MENGE is used.
 For Variant pricing purpose SDCOM-VKOND is used.
 Characteristics allow describing and distinguishing between objects, such as length, color, or weight within the classification system.
Procedure
SAP Menu Logistic->Centralfunction->Environment->classification->Chracteristics
Transaction Code CT04
 From the classification menu, choose Characteristics.
 Enter data on the initial screen.
 In the Characteristic field, enter a name for new characteristic
 Enter a change number if you want to create the characteristic using engineering change management.
 To do this, choose processing type Create characteristic.
 You can also copy the data of an existing characteristic. Use the pushbutton Create by copying. Enter the name of a characteristic you want to copy.
 Confirm the entries.
 On the Basic data tab page enter the most important control data for the characteristic.
 You must maintain the basic data for all characteristics. All other screens are optional.
 In the formatting data for value assignment, whether a characteristic is single-value, multiple-value, or retractable is defined. It is not possible change the value assignment indicator once it has set. It applies wherever the characteristic is used.
 The data type of the characteristic determines which values can be entered for the characteristic. I can any one of the following
- Characters
- Numeric
- Time format/Date format
- Currency format and
- User defined data type.
 For numeric characteristic it need to maintain that whether interval values to a numeric characteristic, or only individual values need to be maintain in Basic Data screen itself.
 Languages in which characteristic want to describe are entered.
 Choose the tab page Values.
 Enter values in the entry fields. Enter each value in a separate field.
 The values must match the format that you defined on the Basic Data screen. You can enter up to the number of characters that you defined in the format.
 If your characteristic is an alphanumeric characteristic, enter a language-dependent value description. You can enter up to 30 characters.
 It is not possible to enter a language-dependent description for numeric values
 It is also possible to define one value as a default value. This value then appears as a default in characteristic value assignment functions
 Additional value indicator determines that whether values that are not defined as allowed values can be assigned to a characteristic
 The following value check strategies are available in value maintenance screen.
- Allowed Values:
- Check Tables
- Function module
- Catalog character
 Allowed values permits only values defined in characteristics maintenance are used to check a characteristic value
 Check table permits only values entered in characteristics maintenance is used to check a value
 Function module entered is used to check characteristic values.
 Value catalog entered is used to check characteristic values
 Documents, such as drawings or photographs, with characteristics can be linked in additional data screen. Before link a document to a characteristic, it must create a document info record in the document management system.
 In this screen it also possible to restrict or hidden or displaying only allowed values to characteristic.
 It is possible to that characteristic can be only assigned to particular class type by assigning type in restriction screen.
 To change a characteristic selects the pushbutton Change in characteristics after entering the characteristic. To display the characteristic chooses the pushbutton Display.
10.1.4 Creating Class:
Purpose:
 A class is used to hold the characteristics that describe a configurable material. By linking the class to the configurable material, you allow the material to be configured using the characteristics of the class.
Procedure
SAP Menu Logistic->Central function->Environment->classification->Class
Transaction Code CL01
 Class holds all characteristics describe configurable material.
 Class with class type 300 is used in configuration profile.
 On basic Data screen class description, its status is entered. Status determines:
 whether a class can be maintained
 whether objects can be allocated to a class
 whether the class can be used for selecting objects
 Class group is used to group together related classes and also for finding classes quickly via a matchcode.
 Same Classification indicator determines whether system check for identical characteristic values. In this case, where several objects are assigned that have the same values for all characteristics to the same class. Depends upon indicator system give warning or error message or no message.
 Keyword string is used for finding a class via matchcode.The description entered on the basic data screen serves as the first keyword
 On characteristic screen list characteristic which has to attach with configurable material is entered.
 Using document tab screen it is possible to assign documents related to configurable object.
 On additional data screen whether or not this class can be used as a class component in bills of material. If it is yes then Unit of measure in which stocks of the material are managed. The system converts all the quantities you enter in other units of measure (alternative units of measure) to the base unit of measure and resulting item category which will replace this class item in BOM (i.e. Stock, Non-stock item etc ).
10.1.5 Creating Dependency
Purpose
Dependency describes the interdependencies between characteristics and characteristic values and it controls which components to be selected from a bill of material (BOM) and which operations to be selected from a task list. It also changes the field values in BOM items and operations during configuration.
Procedure
SAP Menu Logistic->Central function->Variant Configuration->dependency->Single Dependency->Create Dependency
Transaction Code CU01
 From the variant configuration menu, choose Dependency -> Single dependency-> Create
 In initial screen name of the dependency is entered. If dependency need to create for a specific date, enter a change number. It is also possible to create dependency by copying from existing dependency.
 On basic data screen the following data are required to enter
- A language-dependent description for the dependency
- Also possible to enter descriptions in different languages by choosing Descriptions.
- Long texts for the dependency, choose Extras -> Documentation.
- In the standard R/3 System, the status In preparation when a dependency is created first time. The status is set to Released when the source code is syntactically correct.
- Finally suitable dependency type is selected.
 In Dependency editor the source code for the dependency is entered. Once the source code is syntactically correct, the source code is saved.
 Now the status of the dependency is turns to Released. Save the Dependency and exit.
10.1.6 Changing Bill of Material (Assign Dependencies)
Purpose:
By assigning dependencies to BOM components, it is possible to restrict the selection of irrelevant variant parts.i.e correct BOM components are get selected at result of configuration. It is also possible to change the component quantity depends upon characteristic value changed.
Procedure
1. Access the activity using one of the following navigation options:
SAP Menu Logistics  Production  Master Data  Bills of Material  Bill of Material  Material BOM  Change
Transaction Code CS02
 Dependencies are assigned with respect to characteristic for each variant part.
 Dependencies are created either locally within object or globally which can be assigned to any objects.
 In BOM General Item overview screen choose the component in which dependency need to assign and choose menu path Extras -> Dependency -> assignment of dependency for assignment.
 It also possible to enter dependency directly in BOM itself by choosing Extras -> Dependency -> dependency editor.
10.1.7 Creating Configuration Profile
Purpose
 Configuration profile used for assigning configurable material with variant class (300) and also used to maintain some central settings.
 It is possible to assign more than one configurable profile for one KMAT material.
 The selection of profile depends upon either by priority or by manual selection.
 It is also possible to assign dependencies to configurable profile.
 Class with type 300, which hold the entire characteristics of KMAT material, are assigned to each profile
Procedure:
Access the activity using one of the following navigation options:
SAP Menu Logistics  Production  Master Data  Material Master  Environment  Configuration Profile  Create
Transaction Code CU41
 From the Variant Configuration menu, choose Configuration profile->Create.
 A dialog box will be displayed. The object name is entered. Confirm your entries.
 On profile overview screen the following data need to be entered.
 Profile name and the class type of classes used for configuration. In Customizing for the Classification System, the class type must be defined as a variant class type.
 Choose Goto -> Class assignments or the Class assignment pushbutton to assign the object to a class.
 In the classification screen, names of the classes are entered.
 It is possible to restrict allowed characteristic values for the configurable object if required.
 Release of profile is possible only if configurable object is assigned to a class. To go to the detail screen, where you define further settings, choose the Profile detail pushbutton or double-click on the profile.
10.1.7.1 Optional Settings on the Profile Overview
 Organizational Areas
You can specify organizational areas for configuration. If you restrict a profile to specific organizational areas, you only see the characteristics that are relevant to your area when you configure the object.
You can change how characteristics are displayed according to organizational area for your user on the value assignment screen.
 Priority of Configuration Profiles
You can create several configuration profiles for a configurable material. The profile with the lowest number has the highest priority.
If you define several profiles for an object, you see a dialog box for selecting a profile when you start configuration. The profile with the highest priority is at the top of the list.
The priority is also relevant if you use Application Link Enabling (ALE) or intermediate documents (IDocs) to run configuration, rather than dialog mode. In this case, the profile with the highest priority is selected for the object. Profiles that have no priority are at the top of the list, because they automatically have priority 0.
10.1.7.2 Profile Detail
 Configuration Profiles for Materials
The configuration profile has several screens. Depending on what you enter for the BOM explosion and configuration process, fields are shown or hidden.
The parameters you maintain for a material apply to the material as a header material in a BOM structure. You cannot define separate settings for use of a configurable material as an assembly in a BOM.
- By choosing the Assignments pushbutton, you can assign dependencies to the configuration profile. You also see this pushbutton on the basic data tab, once at least one dependency is assigned.
 Basic Data Tab
- In the basic data, click on the profile overview data.
- If configuration process need to starts with a Start logo, documents are assigned such, as a graphic showing the product you want to configure, to the variant class.
- Configuration Initial Screen Tab
 Configuration parameters
- The parameters for BOM explosion and the configuration process in the sales order are specified here.
- BOM application must be entered, if BOM explosion None is selected rather than single and multi level explosion is selected.
- By entering a level of detail for a multi-level configuration, system performance will be improved.
- It is also possible to define a filter and set the indicator for an availability check on assemblies.
10.1.8 Changing Configuration Profile: Add User Interface Settings
Purpose
Settings for the configuration editor in user interface.
- An interface design is used to group characteristics together on the value assignment screen.
- Here it also possible to define object-specific settings for functions in the configuration editor. These settings are defaults for configuration, and can be overwritten for your user in the configuration editor.
- For all configuration parameters except BOM explosion None, manually select the screens for the configuration editor and define which screen configuration starts with. The start screen must be one of the allowed screens.
- The indicator for the configuration browser independently of the other start screens can be selected, because the browser is an additional screen section.
Configuration Profiles for Objects Other than Materials
- Object-specific settings for displaying characteristics and characteristic values in the configuration editor can be defined. These settings are defaults for configuration, and can be overwritten for your user in the configuration editor.
Procedure
Access the activity using one of the following navigation options:
SAP Menu Logistics  Production  Master Data  Material Master  Environment  Configuration Profile  Change
Transaction Code CU42
10.1.9 Configuration Simulation
Purpose:
 Configuration simulation is used to check the configuration model. In the configuration simulation, the whether or not Object structure is created correctly and dependencies are working fine is checked.
 Simulation of Sales/Engineering
- The configuration parameters in the configuration profile apply. Whether the configuration is simulated from the sales point of view or the engineering point of view is defined.
- If select Sales & distribution is selected the configuration in a sales document will be simulated (sales order or quotation), so the BOM explosion depends on the settings in the configuration profile.
- If Engineering is selected, the configuration in order BOM processing will be simulated. The configuration and BOM explosion depend on the configuration parameters in the same way as when maintaining an order BOM. For example, we cannot configure the header material, because the configuration is copied from the sales order.
 Simulation of a Planned Order
- On the characteristic value assignment screen, we can choose Planned order to display the components that are determined in material requirements planning (MRP) according to the characteristic values assigned. This is especially relevant to assemblies whose BOMs are exploded in MRP, not in Sales & distribution (for example, assemblies with the BOM explosion setting None in their configuration profile).
Procedure:
SAP R/3 menu Logistics  Production  Master Data  Bills of Material  Environment  Variant Configuration  Environment  Configuration Simulation
Transaction Code CU50
 On the initial screen of the configuration simulation, select BOM to display the entire structure on the result screen.
 If you have created more than one configuration profile for a material, you see a dialog box. Select a profile and choose Continue. If you want to call detailed information on the profile, choose Profile Detail or double-click on the profile.
 To display the task list of an assembly on the result screen, select the assembly and choose View  Objects  Task list.
 You see the operations or activities in the task list that was selected for the assembly during configuration.
 Operations that have been changed by dependencies have an information icon next to them. You can display changes by choosing Information.
 To return to the BOM explosion, choose View  Objects  BOM
10.2 Sales and Distribution
10.2.1 Creating Condition Records - VA00
Purpose:
The purpose of this activity is to create condition records for VA00.
Procedure
1. Access the activity using one of the following navigation options:
SAP Menu Logistics  Sales and Distribution  Master Data  Conditions  Select Using Condition Type  Create
Transaction Code VK11
 Create price for each value of the characteristics by select using condition type VA00.
 Create the Price for the condition type that represents these types of the standard-delivered condition type for this functionality is VA00.
 Condition type VA00 requires as key fields the sales Organization, distribution channel, and material number of the configurable.
 Condition type PR00 used to maintain base price of the configurable material.
 Using VA01it is also possible to maintain Surcharges and discounts.
10.2.2 Condition records for Variant Price and Surcharges
Purpose
Condition records allow you to store and retrieve pricing data in the system. All the pricing elements of your daily business - the prices, discounts, and surcharges for freight and taxes - that you want to use for automatic pricing must be stored in the system as condition records. You can define as many condition records as you want for the different pricing elements for any validity period.
You create condition records for all the pricing elements that the system takes into account during automatic pricing. During document processing, the system transfers data from the condition records and determines the amounts for individual pricing elements (prices, discounts and surcharges) and the final amount for the sales document
Procedure
10.2.2.1 Create a characteristic for the Pricing
- Create Pricing characteristic like CAR_Pricing and go to additional data tab give SDCOM table name VKOND field name.
SAP Menu Logistic->Centralfunction->Environment->classification->Chracteristics
Transaction Code CT04
10.2.2.2 Assign the characteristic to the class
Assign given characteristics to class, In variant configuration, a class is used to hold the characteristics that describe a configurable material. By linking the class to the configurable material, it allows the material to be configured using the characteristics of the class. In the standard R/3 System, the class type for configurable material is 300.
SAP Menu Logistic->Central function->Environment->classification->Class
Transaction Code CL01
10.2.2.3 Create a dependency that triggers the price
A Dependency is a rule that defines how the different options and option values, represented by characteristics and characteristic values, relate to one another. To create a dependency, follow the menu path
SAP Menu Logistic->Central_function->VariantConfiguration->dependency->Single Dependency->Create Dependency
Transaction Code CU01
10.2.2.4 Assign the dependency to the characteristic value that triggers the price
For example eCar2002, the value V8 refers to the engine selected by the customer. Therefore, the dependency must be linked to the value V8 of the characteristic that represents the engine type. To do this, go to the master data record of the characteristic CAR_ENGINE
SAP Menu Logistic->Centralfunction->Environment->classification->Chracteristics
Transaction Code CT04
Go to the Values tab. From there, select theV8 entry and use the menu path Extras Object dependencies Assignments, which brings you to the screenshot to the right; if you have created a global dependency, you can link it to the characteristic value.2 Once the dependency has been assigned, the information on this screen, such as the description (Engine price), will default to the information entered when you created the characteristic.
10.2.2.5 Create variant price
Create price for each value of the characteristics using condition type (or transaction VK11). Create the Price for the condition type that represents these types of the standard-delivered condition type for this functionality is VA00. Condition type VA00 requires as key fields the sales Organization, distribution channel, and material number of the configurable.
In the same way using condition type VA01 is also used to maintain prices for surcharges and discounts.
10.2.2.6 Creating the output condition records for sales
Output types are used to represent various forms of output in the SAP system. Examples of output types in Sales and Distribution processing are order confirmations, freight lists, and invoices. You use the output type to control how the output should be transmitted, for example whether an order confirmation should be sent via EDI, or be printed
10.2.3 Creating Output Condition Records: Sales
Purpose:
Output types are used to represent various forms of output in the SAP system. Examples of output types in Sales and Distribution processing are order confirmations, freight lists, and invoices. You use the output type to control how the output should be transmitted, for example whether an order confirmation should be sent via EDI, or be printed
Procedure
1. Access the activity using one of the following navigation options:
SAP Menu Logistics  Sales and Distribution  Master Data  Output  Sales Document  Create
Transaction Code VV11
 Choose Edit >Key combination
 Select the key combination for which condition records are to be created.
 Choose Enter.
 Enter the appropriate key for each condition record, according to the key combination you selected.
 For transmission medium 1 (Print output) or 7, you can maintain the communication data. To do this, choose Communication.
 Save the condition records.
10.2.3.1 Creating Output Condition Records: Billing
Purpose
The purpose of this activity is to create output condition records for billing. Output types are used to represent various forms of output in the SAP system. Examples of output types in Sales and Distribution processing are order confirmations, freight lists, and invoices. You use the output type to control how the output should be transmitted, for example whether an order confirmation should be sent via EDI, or be printed
Procedure
1. Access the activity using one of the following navigation options:
SAP Menu Logistics  Sales and Distribution  Master Data  Output  Billing Document  Create
Transaction Code VV31
Enter an output type.
 Choose Edit >Key combination
 Select the key combination for which condition records are to be created.
 Choose Enter.
 Enter the appropriate key for each condition record, according to the key combination you selected.
 For transmission medium 1 (Print output) or 7, you can maintain the communication data. To do this, choose Communication.
 Save the condition records.
10.2.4 Order BOM
Purpose:
Products that are made to order in plant engineering and construction and mechanical engineering are generally very complex and are specific to one customer. For this reason, you cannot define a BOM entirely in advance. Once you have created your sales order, you need to make manual changes to the BOM by creating an order BOM especially for the sales order, without changing the original BOM.
The sales order, sales order item, and material number identify an order BOM. In variant configuration, you can work with 2 types of order BOM. The difference is in the way they are saved.
Knowledge based order BOM
The order BOM is saved as a copy of the super BOM with manual changes and dependencies.
Result Oriented BOM
The configuration result is saved as an order BOM, with manual changes but without dependencies.
Procedure (For knowledge based BOM)
SAP Menu Logistics  Production Planning  Master Data  Bills of Material -> Order BOM Maintain (Multi-Level)
Transaction Code CU51
 The Create Order BOM: initial screen appears.
 Enter the sales order number, the order item, the material number and the BOM usage
 If you want to use material BOM, or an existing order BOM to copy from, go to step 4. If you want to create an order BOM without a reference, click and go to step 7
 You cannot use a configurable BOM as a reference
 Click on copy order BOM or Click on copy material BOM
 The Copy material BOM or Copy order BOM dialog box appears
 Enter the data required and click . The item overview appears, for the bill of material you are using as a reference.
 Enter new items and alter items if necessary. Entering items in order BOMs is similar to entering items in material BOMs. However, you<u><i><b>Steps for SD Variant Configuration</b></i></u>
Some light on Variant Configuration in Detail.
The procedure is as follows:
1. Create a Material - KMAT type with Item category (002)
2. Create Charateristics in CT04 - Zbike, where in values mention the Color of the bile like Red, Blue etc
3. Create another characteristics in CT04 - ZPrice, where directly go the additional data tab and maintain the table SDCOM and field VKOND (ABAP Dictionary it will ask for)
4. Assign these two characteristics to a Class in CL01 - ZBikeclass ( Type 300) in characteristics tab page.
5. Then go to CU41 Configuration profile select the material and enter the description click on the class assignment ie assign Zbikclass.
Now go back to CT04 - enter Zbike -go to values- select Red- go to extras - Other Dependencies - Select Procedure enter in front 10 write - $self.ZPrice='Red' and save
6. Now go back go to extras - Other Dependencies - assignments and assign relationship ( by default it will come just save)
7. Now select Blue- go to extras - Other Dependencies - Editor - Select Procedure enter in front of 10 write - $self.ZPrice='Blue' and save
8. Now go back go to extras - Other Dependencies - assignments and assign relationship ( by default it will come just save)
9. Now go to VK11 - Enter VA00 (Condition)(For Std RVA001 Pricing Procedure) - enter variant Red and Blue give the rates accordingly and create the sales order.
Reward if it helps
Regards,
Anbu -
Error in Fast Formula for Supplemental Earnings Elements
Hi,
I have an requirement in Supplement Earning Elements for US Localization. I need to define some Supplement Earning Elements that should comes in Payroll with the extension of existing Elements.
Here are the Steps for setups which i have done so far-
Step 1:Created new Elements with their values with effective dates for existing user Table name
Step 2:Done the setup for New Elements with classification as Supplemental and Category also attached the formula like "FLAT AMOUNT" formula for Calculation rule in Element Earning screen.
Step 3: when i tried to query for the element i have created, the value in Calculation Field is "Elementname_FLAT_AMOUNT_RWSI" which is not same for the existing elements.Existing Element which is of same classification and same category the Calculation rule field is "ElementName_FLAT_AMOUNT".
Step 4: After that i did setup for Element Description and Element Link.
Step 5: Then i have copied the Formula from Existing element(which is previously configured and working fine for the existing elements ), made the modifications for the newly created element. When Compiling the formula ,i am getting an Error "Incorrect Data type"
I have two queries -
1- The setup in Earnings Screen with Calculation Rule is correct or not. As the Calculation Field for newly elements and the existing elements are different (as mentioned in Step 3).
2- Compilation Error "Incorrect Data Types" in Fast Formula.(as mentioned in Step 5).
I m pasting the Fast Formula code here for ready reference
Default for TERMINATED_EMPLOYEE is 'N'
Default for RUN_TYPE is 'R'
Default for FINAL_PAY_PROCESSED is 'N'
default for PAYROLL_TERMINATION_TYPE is 'L'
default for BG_TERMINATION_TYPE is 'L'
default FOR LAST_STANDARD_PROCESS_DATE_PROCESSED IS 'N'
DEFAULT FOR ELEMENT_NAME_NEG_EARNINGS_ASG_GRE_ITD IS 0
DEFAULT FOR ELEMENT_NAME_ADDITIONAL_ASG_GRE_ITD IS 0
DEFAULT FOR ELEMENT_NAME_REPLACEMENT_ASG_GRE_ITD IS 0
DEFAULT FOR ELEMENT_NAME_ASG_GRE_YTD IS 0
DEFAULT FOR ELEMENT_NAME_ASG_GRE_RUN IS 0
Default for PAY_EARNED_START_DATE is '02-JAN-0001' (DATE)
Default for PAY_EARNED_END_DATE is '02-JAN-0001' (DATE)
Default for ASG_NUMBER is ' '
Default for ELEMENT_NAME_ASG_GRE_FYTD IS '0'
Default for CURRENT_ELEMENT_TYPE_ID is 0
Default for GROUP_KF_PAY_FREQUENCY is '0'
DEFAULT FOR Amount IS 0
INPUTS ARE Amount
IF ELEMENT_NAME_REPLACEMENT_ASG_GRE_ITD WAS DEFAULTED OR ELEMENT_NAME_REPLACEMENT_ASG_GRE_ITD = 0 THEN
pay_frequency = GROUP_KF_PAY_FREQUENCY
ELEMENT_TYPE_ID_PASSED = CURRENT_ELEMENT_TYPE_ID
annual_rate = HCS_GET_SUPPLEMENT_RATE(ELEMENT_TYPE_ID_PASSED, PAY_EARNED_END_DATE, 'General Rate')
annual_bal = ELEMENT_NAME_ASG_GRE_FYTD
IF annual_bal = annual_rate THEN
Amount = 0.00
mesg = 'Contract amount '||TO_CHAR(annual_rate)||' fully paid for '||ASG_NUMBER
ELSE
Amount = annual_rate / TO_NUMBER(pay_frequency)
If abs(annual_bal+amount-annual_rate) < 1 then
Amount = annual_rate-annual_bal
IF ELEMENT_NAME_ASG_GRE_RUN=0 THEN
flat_amount = Amount
+ ELEMENT_NAME_ADDITIONAL_ASG_GRE_ITD
+ ELEMENT_NAME_NEG_EARNINGS_ASG_GRE_ITD
ELSE
( flat_amount = Amount )
ELSE
(flat_amount = ELEMENT_NAME_REPLACEMENT_ASG_GRE_ITD + ELEMENT_NAME_ADDITIONAL_ASG_GRE_ITD
+ ELEMENT_NAME_NEG_EARNINGS_ASG_GRE_ITD
clear_repl_amt = -1 * ELEMENT_NAME_REPLACEMENT_ASG_GRE_ITD
IF ELEMENT_NAME_ASG_GRE_RUN = 0 THEN
IF ELEMENT_NAME_ADDITIONAL_ASG_GRE_ITD <> 0 THEN
clear_addl_amt = -1 * ELEMENT_NAME_ADDITIONAL_ASG_GRE_ITD
IF flat_amount < 0 THEN
(IF (PAYROLL_TERMINATION_TYPE WAS DEFAULTED AND
BG_TERMINATION_TYPE = 'A' AND
TERMINATED_EMPLOYEE = 'Y' AND
FINAL_PAY_PROCESSED = 'N') OR
(PAYROLL_TERMINATION_TYPE = 'A' AND
TERMINATED_EMPLOYEE = 'Y' AND
FINAL_PAY_PROCESSED = 'N') OR
(PAYROLL_TERMINATION_TYPE WAS DEFAULTED AND
BG_TERMINATION_TYPE = 'L' AND
TERMINATED_EMPLOYEE = 'Y' AND
LAST_STANDARD_PROCESS_DATE_PROCESSED = 'N') OR
(PAYROLL_TERMINATION_TYPE = 'L' And
TERMINATED_EMPLOYEE = 'Y' AND
LAST_STANDARD_PROCESS_DATE_PROCESSED = 'N') THEN
neg_earn = -1 * ELEMENT_NAME_NEG_EARNINGS_ASG_GRE_ITD
ELSEHuman Resource Management (HRMS)
(neg_earn = flat_amount - ELEMENT_NAME_NEG_EARNINGS_ASG_GRE_ITD
flat_amount = 0
ELSE
(IF ELEMENT_NAME_NEG_EARNINGS_ASG_GRE_ITD <> 0 THEN
neg_earn = -1 * ELEMENT_NAME_NEG_EARNINGS_ASG_GRE_ITD
IF (PAYROLL_TERMINATION_TYPE WAS DEFAULTED AND
BG_TERMINATION_TYPE = 'A' AND
TERMINATED_EMPLOYEE = 'Y' AND FINAL_PAY_PROCESSED = 'N') OR
( PAYROLL_TERMINATION_TYPE = 'A' AND
TERMINATED_EMPLOYEE = 'Y' AND FINAL_PAY_PROCESSED = 'N') OR
(PAYROLL_TERMINATION_TYPE WAS DEFAULTED AND
BG_TERMINATION_TYPE = 'A' AND
TERMINATED_EMPLOYEE = 'Y' AND FINAL_PAY_PROCESSED = 'Y'
AND RUN_TYPE != 'R') OR
( PAYROLL_TERMINATION_TYPE = 'A' AND
TERMINATED_EMPLOYEE = 'Y' AND FINAL_PAY_PROCESSED = 'Y' AND
RUN_TYPE != 'R') THEN
(STOP_ENTRY = 'Y'
mesg = ' ELEMENT_NAME earning has been stopped for this assignment.'
ln_calc_meth = SET_ALTRNT_FLAT_RATE_CALC_METH('NOT_APPLICABLE','NOT_APPLICABLE')
if (1 = 1) then (
soe_run = ELEMENT_NAME_ASG_GRE_RUN
soe_ytd = ELEMENT_NAME_ASG_GRE_YTD
RETURN flat_amount, clear_addl_amt, clear_repl_amt, neg_earn, STOP_ENTRY, mesg
Can anyone help me in solving this problem. Any kind of pointers would be helpful.
Thanks
Pradeep.Hi Pradeep,
Hope you created the new element using the 'Earnings Template' form. If it is created using the 'Earnings Template' form then the calculation rule
should be correct. You said you are modifying the new element formula by using the existing element formula code, have you checked if the
formula code to the old and new once have changed anything other than the element name and standard input elements reference. Try to use
the debug messages in formula and see if that give you any clue. You should find the document in metalink how to debug a formula.
Thanks,
Satin -
How to setup a release strategy for store generated purchase order
Hi there,
Does anybody know how to setup a release strategy for store/plant generated purchase order? I have a request from our client, but I never cross this before. Please help and let me know the step with every single detail.
Greatly thank for your help.
Kind Regards,
2teaPlease go thru the below Release Procedure and check whether you have maintained all the settings properly.
PO RELEASE STRATEGY
The release code is a two-character ID allowing a person to release (clear, or approve) a requisition or an external purchasing document. The release codes is basically controlled via a system of authorizations (authorization object M_EINK_FRG).
Use SE12, structure CEKKO to check all the fields available for controlling the Purchase Order.
e.g. If the total value for the Purchase Order exceeds 10,000, release strategy 01 is assigned to the Purchase Order. There is only one characteristic created in this example. For controlling the Purchase Order type, create characteristic for CEKKO-BSTYP and the value NB.
CT04 - Create Characteristic e.g. NETVALUE
Click Additional data Table name CEKKO Field name GNETW and press enter
(for currency dependent field, you are prompt to enter the currency which the system then converts the currency of the Purchasing document into this currency)
In the Basic data (X refers to tick),
X Mutliple values
X Interval values
In the Value data, in the Char. value column, type >10000 and press enter
Save your data
CL02 - Class
Class - Create REL_PUR
Class type - 032
Click Create
Description - Release Procedure for Purchase Order
In the Same Classification section, click Check with error
In the Char. (characteristic) tab, type NETVALUE to assign your characteristics to the class
OMGS - Define Release Procedure for Purchase Order Type
Release Group - New entries
Rel.group Rel. Object Class Description
02 REL_PUR Rel. Strategy for PO
Release codes - New entries
Grp Code
02 01
Release indicators
Release indicators Release Description
0 Blocked
1 X Release
Release Strategy
Release group 02
Rel.strategy 01
Release codes 01
Release status 01
Classification Choose your check values
OMGSCK - Check Release Strategies
(make sure there are no error messages)
Once the Purchase Order is not release, buyers will not be able to print the Purchase Order.
Goods Receipts will be shown with Message no. ME 390 - Purchasing document XXXXXXX not yet released.
In 4.6c, Purchase Order with Release Strategy have a tabs at the end of the Header. This allowed the buyers to check the release status of the Purchase Order.
The person with the release authorization have to use ME28 to release the Purchase Order.
Regards,
Ashok -
Recommendation for maintaining pricing in CRM when R/3 is also in landscape
Hi,
in out context we have already SAP R/3 in the landscape, all the pricing in done in R/3. lot of custom pricing routines are also written in r/3.
now we in the process of implementing CRM and plan to do Quotations in CRM and replicate in SAP R/3 . what is the recommendation for such a scenario.
do we replicate all pricing conditions/procedures in CRM? do we need to re-do all procedures in IPC?
can we re-determine pricing in R/3 so that we can avoid such work in CRM? we are using configurable products in R/3.
please share your thoughts/best practices and any document will be of help.
thanks
RHHi Swaroop,
The Assignment of Buisness Partner classification from CRM to R3 is purely based on Classification
so your initial Entry
I chose B as classification & Z001 as an account group which is a copy of 0001. System takes it.
was taken by the system
now when you tried to make another Entry by the same Classification
chose B again & this time Z002 acc gp (copy of 0002), and system does not allow?
it checks for the Existing Classification and so does not allow the same
Delete the Previous Entry and then Try Entering the New Entry
The System shall Take it
Hope it Answered your Queries...
Revert Back for any Doubts..
Also Chk the Link for details:http://help.sap.com/saphelp_crm50/helpdata/en/04/4d9ac77b2b11d3b52f006094b9114a/content.htm
Thanks and Regards,
RK. -
Check in new documents in DMS with specific access permissions
Hi,
we have an RFC which creates new documents in DMS.
This calls one after another these FBs:
- CVAPI_DOC_CREATE
- CVAPI_DOC_CHECKIN
- BAPI_DOCUMENT_CHANGE2 for a additional classification of the new document
Now we have a new request from our customer: to give the document specific access permissions.
We try the following:
- manually check in a document template with the necessary permissons.
- the permissions are given in a classification ("O,MW-T-D*,IB,02/03/52/53")
- This is named "authority characteristic" and is checked somewhere else, I do not really know how this works in detail ( but it works)
- check in a new document with a reference to the template and in expectation that the new document has the same classification and therefore the same access permissions
- If I do this manually in CV03N is does work
- We do this with CVAPI_CHECK_IN_WITH_TEMPLATE - but this FB does not copy the classification ( only the description and the attached original documents , and the documentnumber of the new document is an mandatory parameter which is not allowd in our case since we use internal creation of document numbers)
My question is: Is this a possible way to create new documents with specific permissions
Is there a possibility to give the permissions to the documenttype instead of give them to every single document of this documenttype ?
Thanks
KerstinMy guess is that at some point you propagated the ACL entry for "everyone deny delete" to all your folders and sub-folders and their contents by selecting Apply to All in a GetInfo window. Try doing a search in the Leopard forums for
ACL chmod
and you'll find a whole raft of discussions about the problem and suggestions for fixes.
Francine
Francine
Schwieder -
Purchase Order not subject to release strategy
Good day everyone!
I've created one release strategy for all my purchasing documents. The characteristic is net value, and the value of this characteristic is >=0.00. Meaning, ALL purchase orders are subject to release strategy.
After I did the release strategy in SPRO, I created a few PO and when I tried to release them, I got this message: "Purchasing document 45xxxxxxxx not subject to release strategy".
My question is: How to assign purchasing document to release strategy?
Please help. Thank you in advance.
Anisahhi
yes you have to use table CEKKO for PO release strategy , now , in PO you can't create without clasification so it will be applicabe for whole PO not for line items ,
now below i am giving u one by one steps , follow and let me know .
The release code is a two-character ID allowing a person to release (clear, or approve) a requisition or an external purchasing document. The release codes is basically controlled via a system of authorizations (authorization object M_EINK_FRG).
Use SE12, structure CEKKO to check all the fields available for controlling the Purchase Order.
e.g. If the total value for the Purchase Order exceeds 10,000, release strategy 01 is assigned to the Purchase Order. There is only one characteristic created in this example. For controlling the Purchase Order type, create characteristic for CEKKO-BSTYP and the value NB.
CT04 - Create Characteristic e.g. NETVALUE
Click Additional data Table name CEKKO Field name GNETW and press enter
(for currency dependent field, you are prompt to enter the currency which the system then converts the currency of the Purchasing document into this currency)
In the Basic data (X refers to tick),
X Mutliple values
X Interval values
In the Value data, in the Char. value column, type >10000 and press enter
Save your data
CL02 - Class
Class - Create REL_PUR
Class type - 032
Click Create
Description - Release Procedure for Purchase Order
In the Same Classification section, click Check with error
In the Char. (characteristic) tab, type NETVALUE to assign your characteristics to the class
OMGS - Define Release Procedure for Purchase Order Type
Release Group - New entries
Rel.group Rel. Object Class Description
02 REL_PUR Rel. Strategy for PO
Release codes - New entries
Grp Code
02 01
Release indicators
Release indicators Release Description
0 Blocked
1 X Release
Release Strategy
Release group 02
Rel.strategy 01
Release codes 01
Release status 0
1
Classification Choose your check values
OMGSCK - Check Release Strategies
(make sure there are no error messages)
Once the Purchase Order is not release, buyers will not be able to print the Purchase Order.
Goods Receipts will be shown with Message no. ME 390 - Purchasing document XXXXXXX not yet released.
In 4.6c, Purchase Order with Release Strategy have a tabs at the end of the Header. This allowed the buyers to check the release status of the Purchase Order.
The person with the release authorization have to use ME28 to release the Purchase Order.
regards
ravikant dewangan -
BAPI_DOCUMENT_CHANGE2 - Characteristic Number of User-Defined Data Type
We are using classifications in the DMS system (it is the same classification system as the sales order and a few other transaction types). We also have defined our own characteristic data types. If we manually go into CV01n and enter in values into the user defined characteristics everything works fine. However, if I specify them in BAPI_DOCUMENT_CHANGE2 the values are not created/stored. I get a null return on the return parameter so there isn't a warning nor is there an error.
Is there another way to set these values as it doesn't look like it will work with BAPI_DOCUMENT_CHANGE2?
Regards,
DavisWe are using classifications in the DMS system (it is the same classification system as the sales order and a few other transaction types). We also have defined our own characteristic data types. If we manually go into CV01n and enter in values into the user defined characteristics everything works fine. However, if I specify them in BAPI_DOCUMENT_CHANGE2 the values are not created/stored. I get a null return on the return parameter so there isn't a warning nor is there an error.
Is there another way to set these values as it doesn't look like it will work with BAPI_DOCUMENT_CHANGE2?
Regards,
Davis -
Hi
Can someone suggest me how to configure VAT/GST in case of services.Shipla,
Configuration Path:
IMG --> SD --> BF --> Taxes
a. Define Tax determination rules
you will have to maintain ZCST and ZVAT against the Country.
b. Define regional Codes. Create City code within India - IN
c. Assign Delivering plants for tax determination. Click details button of your plant and mainatain country and city for your plant
d. Define Tax Relevancy of master records For Customer Taxes and Material Taxes
Click on customer Taxes
Maintain Tax category as ZCST and tax class 0,1,2 (Depending on your requirement)
Similarly mainatin it for ZVAT (0,1)
Maintain same classification for Material taxes.
e. Maintain these values in Customer master record and Material master records appropriately.
Now create condition types ZVAT and ZCST, maintain condition records through VK11
Service tax - JSER = 10%
Education cess - JECE = 2% (it will be calculate on service tax)
Secondary education cess - JSEC = 1% (it will be calculate on service tax)
Pricing procedure
FROM TO
10 PR00 Price
20 ZCST CST 10
30 ZVAT VAT 10
35 Netprice 10 30
40 JSER Service 35
50 JECE Edu. cess 40
60 JSEC Sec. Edu. Cess 40
Mainatain Account ting keys accordingly for all the condition types excpt "Netprice".
Hope you are clear
Regards
Sathya
Maybe you are looking for
-
How to personalize the content users see with a set of questions/answers?
Hi I have built my website using dreamweaver CS5.5 and would like users to be able to personalize the content that is displayed. Users will first see a page with three questions. Once they have answered the questions, they should then click 'submit'
-
Essbase add-in Error (duplicate name found in grid)
Hi, I have upgraded from 7.3 to 9.2 essbase add-in and get the following error when zooming into a product dimension - seems to be a problem with base member name and alias showing duplicates! However this error does not occur on a new installation o
-
Anybody have one they're not using? It's the dongle with a /8" mini-plug and a black and yellow-green dongle that has 2 coax and 2 toslink connectors. I "misplaced" mine and I now need it.... it came with my Optical Digital I/O 2. Help!!!
-
Oracle VM - deployment strategy
Hi All, This is my first post on this forum, and am curious to see how this forum works!!! We are planning to use OracleVM and Oracle EL in a new setup. I have scanned through the Oracle VM Manager and Oracle VM server guides and have few queries whe
-
Oracle Reports -- printing 1/3 the way down the second page.
I modifying an Oracle Report that outputs a rtf-formmated word doc. When things go to the second page (because things on the first page have fully occupied the first page), they always appear 1/3 down the page. I would like them to be close to the to