Variant configuration steps

Dear experts,
I am using bom usage 1 for material bom for fert and variant material. now i when i create sales order the is bom should expold the material bom and i want to edit the bom values ie zero quantity the same bom should hit to production.
vishal H K
Thanks in advance
Experts

Hi Vishal,
Here are the steps you have to follow then what ever you want to do the experiment u can do:
1) MM01 with 25 strategy. (KMAT)
2) assign it to KMAT material
3) create BOM cs01
4) create routing CA01
5) Create Characteristics in CT04
6) Create class 300 variant class CL01.
7) assign characteristics to class in CL02
8) Then go to CU41 Configuration profile and assign the 300 variant class.
9) If you want to write dependencies u can give in characteristics.
10) You can also give in BOM or maintain in BOM.
11) Go to CS02 and give the variants you want and assign or create dependencies to them then the BOM can be called as Super BOM.
12) Go to Routing and re-assign the operations then it can be called as Super Routing.
13) Then create the sales order VA01 hope then you can select the variants if you maintained properly every thing ok.
Hope it helps you any queries please revert me back.
Regards,
Madhu.G

Similar Messages

Variant configuration process

Hi,
Can any one tell me variant configuration step by step process.
Regards
Sasikanth.Ch

Hi,
Pl. follow these steps.
Create a Material - KMAT type with Item category (002)
Create Charateristics in CT04 - Zbike, where in values mention the Color of the bile like Red, Blue etc
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)
Assign these two characteristics to a Class in CL01 - ZBikeclass ( Type 300) in characteristics tab page.
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
Now go back go to extras - Other Dependencies - assignments and assign relationship ( by default it will come just save)
Now select Blue- go to extras - Other Dependencies - Editor - Select Procedure enter in front of 10 write - $self.ZPrice='Blue' and save
Now go back go to extras - Other Dependencies - assignments and assign relationship ( by default it will come just save)
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.
Hope it helps. Pl reward if it helps.
Sadhu Kishore

Variant Configuration teg

Hi Sapgurus,
Could you please explain Variant Configuration steps in detail.It's little urgent.And also if you have any detailed document please send to the following mail.Points will be awarded.
with Regards,
mhreddy

Hi,
Pls. find the Varian Configuration step by step procedure as below :
VARIANT CONFIGURATION
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 Zbikeclass.
6.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.
7.Now go back go to extras - Other Dependencies - assignments and assign relationship ( by default it will come just save).
8.Now select Blue- go to extras - Other Dependencies - Editor - Select Procedure enter in front of 10 write - $self.ZPrice='Blue' and save.
9.Now go back go to extras - Other Dependencies - assignments and assign relationship ( by default it will come just save).
10.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.
Variant Configuration: Complete Maintenance
Tasks
The variant configuration processor sets up the rules for multi-variant products and maintains them in the database. He or she simulates and executes the configuration. This role is required wherever variant configuration is used.
The complete model also contains sales order processing (VA01/VA02), and the connection to SCE/Internet Sales and Mobile Sales.
Activities in Variant Configuration
Transaction     Activity
CC04     Display product structure
CWBPP     Engineering Workbench
Variant Configuration
VA01     Create sales order
VA02      Change sales order
VA03     Display sales order
CU51     Maintain configurable order BOM (multilevel)
CU52     Maintain configurable order BOM (single level)
CU50     Configuration simulation
CU80     Reporting functions for characteristics and values
Configured Objects
CU44     Material
CU45     Standard network
Assignment of Configured Materials
CS40     Create assignment for configured material
CS41      Change assignment for configured material
CS42     Display assignment for configured material
Configuration Profile
CU41     Create configuration profile
CU42     Change configuration profile
CU43     Display configuration profile
Dependencies: Single Dependency
CU01     Create single dependency
CU02     Change single dependency
CU03     Display single dependency
Dependencies: Dependency Net
CU21     Create dependency net
CU22     Change dependency net
CU23     Display dependency net
Dependencies: General
CU05     Dependency where-used list
CU04     Dependency list
Tools: Variant Function
CU65     Create function
CU66     Change function
CU67     Display function
CU68     List functions
Variant Table Structure
CU61     Create variant table
CU62     Change variant table
CU63     Display variant table
CU64     List variant tables
Variant Table Contents
CU60     Maintain variant table contents
CU59     Transfer variant table contents to database table
Knowledge Base for SCE: Knowledge-Base Object
CU31     Create knowledge-base object
CU32     Change knowledge-base object
CU33     Display knowledge-base object
Runtime Version
CU34     Create runtime version
CU35     Change runtime version
CU36     Display/export runtime version
CU37     Create SCE database schema on PC
Integration
There are further single roles for other aspects of the configuration environment.
Also required are the individual roles for all BOM processing (SAP_LO_MD_BOM_MAINTAIN), and classification (SAP_CA_CL_MAINTAIN).
Useful Tables for VC:
Characteristics :
CABN Characteristics ( o.a. batch/vendor)
CABNT Characteristics description
CAWN Characteristics ( o.a. material)
CAWNT Characteristics description
AUSP Characteristic Values
Class types and objects :
TCLAO Several class types for object
TCLA Class types ( vb. lfa1 => v10 en 010)
TCLAT Class type text
TCLT Classifiable objects
TCLC Classification status
Links :
INOB Link between Internal Number and Object
KLAH Class header data
KSSK Allocation Table: Object (vb.matnr) to Class
KSML Characteristics for a class (internal number)
Hope this helps.
Pls. provide mail id full so I can send other doc.
Regards,
Tejas

Steps for Variant Configuration

Hi Gurus,
Can any body tell me step by step procedure for variant configuration.
My e-mail id. <REMOVED>
Regds.......
Sumit

Hi Sumit,
Variant configuration is for manufacturing complex products. The manufacturer always has to offer new variants of its products. Often, new variants are created by modifying existing product designs as you process the order. The important thing is to react quickly to customers' requirements.
The customer determines the features of the product. A customer buying a car, for example, can choose the features of the car and combine these features as required.
The product configurator improves information exchange between sales, engineering, and production. Variant configuration helps the customer or salesperson to put together specifications for the product and ensure that the product can be produced from these specifications. It also ensures that production costs do not overstep the mark.
Procedure -
Create a Material - KMAT type with Item category (002)
Create Characteristics in CT04 - Zbike, where in values mention the Color of the bile like Red, Blue etc
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)
Assign these two characteristics to a Class in CL01 - ZBikeclass (Type 300) in characteristics tab page.
Then go to CU41 Configuration profile select the material and enter the description click on the class assignment i.e. 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
Now go back go to extras - Other Dependencies - assignments and assign relationship ( by default it will come just save)
Now select Blue- go to extras - Other Dependencies - Editor - Select Procedure enter in front of 10 write - $self.ZPrice='Blue' and save
Now go back go to extras - Other Dependencies - assignments and assign relationship ( by default it will come just save)
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.
Variant configuration is for manufacturing complex products. The manufacturer is
always having to offer new variants of its products. Often, new variants are created
by modifying existing product designs as you process the order. The important thing
is to react quickly to customers' requirements.
The customer determines the features of the product. A customer buying a car, for
example, can choose the features of the car and combine these features as required.
The product configurator improves information exchange between sales, engineering,
and production. Variant configuration helps the customer or salesperson to put
together specifications for the product and ensure that the product can be produced
from these specifications. It also ensures that production costs do not overstep the
mark.
Integration
Variant configuration is integrated in the following applications:
a.. CA Classification
b.. LO Material Master
c.. PP Bill of Material
d.. PP Routings
e.. PP-PI Master Recipes
f.. SD Sales
g.. SD Conditions
h.. MM Purchasing
i.. CO Costing
j.. PP Material Requirements Planning (MRP)
k.. PP Production Orders
You can configure the following objects:
a.. Materials
b.. Standard networks in the Project System.
c.. PM General maintenance task lists
d.. Model service specifications
Features
You do not need to create a separate material for each variant of a product in your
company. You can use one configurable material to cover all variants. You create a
super BOM and a super routing for this material, containing all the components and
operations for producing all variants of the product.
To define the features of a configurable material, you use characteristics. To
enable you to use characteristics to configure a material, you assign the material
to a class of class type 300. Possible characteristics of a car, for example, are
model, country, color, and engine. The customer can choose from among different
options for each characteristic (values).
The only limitations are combinations of features that are not possible for either
technical or marketing reasons. You cannot combine all types of car engine with all
types of transmission, for example, or certain types of upholstery are only
available for more expensive models. In Variant Configuration, you use dependencies
to control this. This prevents combinations of options that are not allowed.
Dependencies also select exactly the right BOM components and operations to produce
a variant.
Each configurable object must have a configuration profile. The configuration
profile for a material controls the configuration process in the sales order.
You can make the price of a variant dependent on the characteristic values assigned
(Pricing). You can use variant conditions to define surcharges and discounts for a
variant.
For variants that are required frequently, you can create material variants, which
can be produced without a sales order and kept in stock. When you receive a sales
order, you can check whether the variant required is in stock, so that you can
deliver immediately.
Pl go thr below links:
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/LOVC/LOVC.pdf
http://sap-img.com/sap-sd/steps-for-sd-variant-configuration.htm
Please Reward If Really Helpful,
Thanks and Regards,
Sateesh.Kandula

Wants to know the practical steps in Variant Configuration process.

Dear Experts,
I want to know the practical steps being performed under the variant configuration process being followed under textile industry or a pharmaceutical industry. Can anybody please help me out of this issue?

Dear Santosh,
I think you are aware Variant config. is used to configure the material according to the requirement of the customer at the time of processing the sale order.But to my knowledge of pharma business the material will be produced in advance and there will be lot of planning associated to increase the business,and there will be different combinations and strengths available at the disposal,there will not be any make to order scenario.Since it is an ongoing process.It will be like the number of end users of that particular product in the market(here end users will be the patients to whom the medicine has been prescribed).I hope this will be of some help to you.If am wrong pls correct me.
Regards,
Ramesh.

Variant Configuration - product validation step at sales order

Hi all,
By using Variant Configuration, new products can be created at sales order entry ==> is there any way to put a validation process in place where a number of checks (by different people) should be performed before being able to save the order?
thanks
Bart

Hi Vineet,
Thanks for your answer.
I realize dependencies can help control which characteristics value can be choosen. In the meantime my question became; how I can prevent that my sales order gets visible for the planning department (typically they would look in transaction MD04 I guess)? I will post this question under the appropriate topic.
This is the type of flow I have in mind:
customer service fills in the order, specifies the values for the characteristics, Availability check runs and the order is saved
order is saved but not confirmed so it is not transferred to planning
planning (or other department like production) checks the order and the variant. If it is ok, they will confirm the order so it gets to the planning. If not, they will get in contact with customer service.
I'm not experienced in availability check, planning, etc so I might have written big mistakes here.
Kr,
Bart

Error message while creating configurable material for variant configuration.

Dear All,
I want to create configurable material for the purpose of variant configuration. When trying to create configurable material using mm 01 or mm k1, it is displaying an error message that internal number assignment is not possible for the material type configurable materials as well in using external number also. Can anyone specify the steps to be done in creating the configurable material. Thank you all.
Regards
Akula Sivaji Kumar Madhu Kiran

If you want to set these material type to another group (Which has a internal number and external number range), then you can do it.
In MMNR, Click on the Edit Group.
Then select the material type and click select element.
Then mark a tick option in another group and then press Element/Group.
Then you can see the material type will come under this group.
Now save your entry, and create a material with this material type.

Product costing by sales order configuration steps

hi
plz send me product costing by sales order configuration steps.
sir, i know manufacturing order configuration step but i do not sales order configuration.
in the sales order also is same as manufacturing order like first we have to make planning cost , the planning cost should be updated to material master and next configure the actual cost.
for first step- costing variant -okkn
next -costing variant -opl1
for sales order also same we need to update planning price first- what is costing variant
for actual cost - what is costing variant
plz tell me detail
regards,
sowmya
Moderator: Please, read forum rules before posting

Hi Sashikanth,
Please send me the Configuration document for make to sales order.We are at Blue print stage need some docment for make to sales order.Plese send me the document it will will be very help full for me.
My id is [email protected]
Thanks in advance
Regards,
Nagaraju
Edited by: nagaraju sami on Mar 9, 2008 11:58 AM

Why don't we do the confirmation in variant configuration?

Hello guys,
As far as i know that in variant configuration we don't do the confirmation, we directly do the goods receipt.Is it right?If yes than why?
Following are the steps we do while doing the variant configuration scenario:
1)First we create the characteristics and give the values inside it.
2)Then we create the class of class type 200 and give characteristics defined in it.
3)Then we create the variant of class type 300 and give all the characteristics inside it.
4)Now we create the configurable material with Basic data 1,2, MRP 1,2,3,4 , Classification view ,workscheduling view.
In classification view, we give the variant of class type 300.So it shows all the characteristics and its value over there.There we select all the values.
5)Now we create the super bom of configurable material and in class tab we give all the classes of class type 200.Here even we can maintain the dependencies if we define all the characteristics value in item tab.
6)Then we create the super routing and inside it we give all the possible operations inside it.Right now my routing contains operations which are necessary all the times.
7)Then we create the configurable profile for configurable material of class type 300.
8)Now we give the requirement in md81 for configurable material and there we select the characteristics values which we want.
9)After that we run the mrp for configurable material and it generates procurement proposals(planned order) for it.
10) Afer this we convert this planned order into production order and release it and save it.
11) After this we do the goods receipt for the production order in mb31.Because of this it shows the stock of sales order as production order qty.
This procedure my tutor has taught me.Have i missed any steps or am i wrong somewhere?If that the case than plz guide me.

if you can generate a production order then you can always confirm it according to SAP PP logic.
we use variant configuration for the manufacturing of complex products. once the component quantities and
operation are selected for a particular variant and copied to Production order, the rest of the process is same
as normal Production Control. Revert back with any queries you have.
Regards,

Variant configuration-- syntax error in creation of object dependencies

In variant configuration when i try to create object dependency (tcode=cu01), after entering the dependency and also description when i enter the syntax in the source code it is giving error: error in syntax check for simple condition
I have entered syntax as : engine_cap in ('1000','1400','2000'), pls guide me with the solution to create object dependency

Dear, Shakeer
Please follow along with my very own config guide of variant config.
1)     Create a configurable Material Using KMAT u2013Material Type. Item Category 0002 and Item Category Group 0002. Go to classification tab-here you maintain the class type 300 and assign the class, we will create this shortly. (So after creating class come back into MM02 and input the class that you create in step 2.)
2)     Create a class in T-Code CL01. Use class type 300 for Variants. In this we assign the characteristics we will create shortly.
3)     Create characteristics in T-Code CT04. Create your characteristic like for example, Z_Type, Z_Model, and Z_Color.
4)     We must create a characteristic for the pricing. Example, Z_CarPrice inside this characteristic we must maintain. Table Name SDCOM, Field Name VKOND in the additional data tab. Also, go to restrictions tab and enter the class type 300 Variants. Now in order to make this pricing work for you, you must maintain (enter) all the values from the characteristics. For example, Red, Blue, Black, Honda, Toyota, GLI, XLI, and 2.0D.
5)     Now going back to the characteristics in CT04 change mode. Make sure Basic Data has *Multiple Selections circled. * Character Format has 26 and a check in case sensitive. Make sure in restrictions tab class type 300 Variants is present. Go back to Values and highlight the first one. Example, Red then go to Extras->Object Dependencies->Assignments You must maintain this code $self.Z_CarPrice=u2019Redu2019 in basic data make sure itu2019s released & procedure is filled in. Go back to dependency editor and paste the same code there after 000010 $self.Z_CarPrice=u2019Redu2019 and do this for each and every value. Very Important * Maintain configuration profile in T-Code CU41 for the material -> Priority 01, Variant Configuration, Class 300, status, Released 1, then click save. Note: If 2 conditions are inactive use class group A instead of B in SPRO for Condition type VA00.
6)     Go to T-Code VK11 and enter VA00 condition type. Enter all the values maintained in the characteristics for example, Red, Blue, Black, Toyota, Etc and enter the price then click on save. Now it should work fine in VA01. Make sure you have assigned the VA00 condition type in the pricing procedure.
Good Luck,
Muhammad Ali Lozada

Create a production order with variant configurator data

Hello,
Can anyone tell me the way to create a production order with variant configurator data. Is there a BAPI ? an IDOC ?
Is there several steps ?
I have to create an interface which creates automatically PP orders. The data input is a file.
Thanks for your help

Hi,
There are fews BAPI's available for creation of Production Order. They are:
BAPI_PRODORD_CREATE
This bapi will suit to your requirement, as input will be provided from file.
Others are
BAPI_PRODORD_CREATE_FROM_PLORD " this converts planned order to production order
BAPI_PRODORD_CREATE_FROM_REF " this creats production order considering other production order as reference.
Hope your query is answered.
Regards,
Brajvir

How to create Variant Configuration Material Master in SAP PP

Dear Friend's,
Pl 's guide me for How to Create Variant Configuration Material Master.
Give me step by step procedure for Creation of Variant Configuration.If some of you having screen shots for the same with one Example, that will be a very helpful to me for creating VC.
Thanks & Regards,
Sandeep N.Theurkar

Hi,
Eg: Ford car.If a sale order is raised for fiesta lxi model the system should choose red colour & for vxi blue colour respectively.
ie you need to define the characteristic and assign the values .
This characteristic need to assigned to class.
class need to be assigned to material master
1. T.code : CT04(characteristic) FORD_MODEL, Choose single value & entry required tab & give the input as 01 - fiesta_lxi & 02 - fiesta_vxi.( characteristic values)
2.Tcode: CT04, FORD_BODY( another characteristic)
Choose single value , don't click entry required.
01 - Red( characteristic values)
02- Blue
3. Create class T.code : CL02
fiesta_class
type : 300
4. OBJECT DEPENDENCY:
T.CODE : CT04
FORD_MODEL
CLICK VALUES TAB,
IN FIESTA_LXI CLICK THE 'O' meant for Obj dependency, action & extra.
Edit the dependecy,
010 $Self.ford_body = '01'. & save
Repeat the same for FIEST_VXI & instead of '01' give '02' for blue colour.
, then create a ROH as ford_body. & a KMAT material for the car. .
Then create a Super BOM with usage 3 & give component as ford_body
Then use T.code cu41 (Create config profile)
enter a profile name & class 300 & choose class assignment, choose fiest_class ,
Use T.code cu50 to check the values.
Then create a sale order.
Pl. reward if helpful.
Regards,
nandha

Risk Mgmnt COnfiguration steps

Hello Friends
Can anyone please tell me the complete steps to configure "Risk Management " with LoC (Letter of Credit) & what is the necessary data to be collected from the business, for configuring the same.
Regards
Sumanth.Gururaj

Hi,
The configuration steps for risk management
How To Do Configuration For Credit Management
Credit and risk management takes place in the credit control area. According to your corporate requirements, you can implement credit management that is centralized, decentralized, or somewhere in between.
An organizational unit that represents the area where customer credit is awarded and monitored.   This organizational unit can either be a single or several company codes, if credit control is performed across several company codes. One credit control area contains credit control information for each customer.
For example, if your credit management is centralized, you can define one credit control area for all of your company codes.
If, on the other hand, your credit policy requires decentralized credit management, you can define credit control areas for each company code or each group of company codes.
Credit limits and credit exposure are managed at both credit control area and customer level. You set up credit control areas and other data related to credit management in Customizing for Financial Accounting. The implementation guide is under Enterprise Structure -> Definition or Assignment -> Financial Accounting and then Maintain credit control area. You assign customers to specific credit control areas and specify the appropriate credit limits in the customer master record.
Settings for determining the credit control area of a document. The settings of items 1 - 4 are taken into account according to their priority. The credit control area found is stored in field VBAK-KKBER.
1. Transaction OB38
   Check which credit control area is assigned to the company code.
   Company code:
   Credit control area:
2. Transaction OVFL
   Check which credit control area is assigned to the sales area.
   Sales area:
   Credit control area:
3. Transaction XD02 or VD02
   Check which credit control area is assigned to the payer.
   Payer:
   Credit control area:
4. Transaction SE37
   Is user exit EXIT_SAPV45K_001 being used?
5. Transaction OBZK
   For the settings under items 2 - 4, field "All company codes" must be marked in Transaction
OB45, or the credit control area must be entered under the relevant company code in table T001CM of the credit control areas allowed.
Company code:
Credit control areas allowed:
6. Settings for the credit checks
7. Transaction OVAK
   Which settings do exist for the sales document type used?
   Sales document:
Check credit:
Credit group:
8. Transaction OVAD
   Which settings do exist for the delivery type used?
Delivery type:
Credit group for delivery:
Credit group for goods issue:
9. Transaction OB01
   Credit management/Change risk category
   Definition of the risk category for each credit control area. This risk category can be assigned to a credit account by using Transaction FD32.
10. Transaction OVA8
    Here, the individual credit checks for key fields
    o credit control area
    o risk category
    o credit group are set. Take these key fields from the above settings and go to the detail screen. In particular, check whether fields "Reaction" and "Status/block" are set correctly. To carry out follow-up actions in case of a credit block, the credit check status must be set (field "Status/block").
11. Transaction FD32
    Credit master data for the payer of the relevant document.
    Credit account:
    Credit limit:
    Risk category:
    Currency:
12. Settings for updating the credit values Update of the credit values is required for the limit check (static or dynamic credit limit check).
13. Transaction OVA7
    Update of the credit value is active for the corresponding item type if the check box is marked. This field corresponds to
    field "Active receivable" in Transaction VOV7.
Item type:
Active receivable:
14. Transaction V/08, Pricing
    In the pricing procedure used for pricing, subtotal "A" must be entered in a line for determining the credit value (mark the pricing procedure and doubleclick on "Control").
Usually, the net value plus taxes is used. This way the system is determined to use this subtotal for credit pricing. The credit price is stored in field VBAP-CMPRE and used for update and credit check.
You can find the used pricing procedure of the order under "Item -> Condition -> Analysis".
Pricing procedure:
Line with subtotal = 'A':
15. Transaction OB45
    Which update group (field "Update") do you use in the relevant credit control area? The default setting is "12". If you use another update group, check whether this is fine with you. If you open an OSS message, please tell us the alternative update group.
Credit control area:
Update:
16. Transaction OMO1
    Which kind of update did you choose for structure S066?
     In any case, "Synchronous update (1)" has to be chosen as the kind of update. All other settings will lead to errors.
Credit Management Reports
The following table provides an overview of all the reports that are available for credit management:
Program     Function
RFDKLI10     Customers with Missing Credit Data
Checks whether the data regarding credit limits is complete and issues relevant error lists. These enable you to maintain the relevant definitions either manually or with batch input.
RFDKLI20     Reset Credit Limit for Customers
Resets the credit limit information in the control areas.
RFDKLI30     Credit Limit Overview
Lists the central and control area data for each customer.
RFDKLI40     Credit Overview
Provides a comprehensive overview of the customeru2019s credit situation.
RFDKLI41     Credit Master Sheet
Displays and prints the customer master data for an individual account that is needed for credit management.
RFDKLI42     Early Warning List
Displays and prints customers in Credit Management who have been listed by the credit check as critical.
RFDKLI50     Credit Limit Data Mass Change
Changes all the credit management master data together.
RFDKLIAB     Display Changes to Credit Management
Displays the changes to credit management master data for all accounts.
RVKRED06     Check Blocked Credit Documents
Checks all the documents blocked for credit reasons. The report is started in the background and should run after the incoming payments programs.
RVKRED77     Reorganize SD Credit Data
Reorganizes open credit, delivery and billing values. It can be used in the event of an update error, for example.
RVKRED08     Checking sales documents which reach the credit horizon
Rechecks all sales documents that fall within the credit limit horizon of the dynamic credit limit check. The report is run at regular intervals and should be run at the start of each period. The system uses the current date and the period split for the open order values to propose the u2018next credit check dateu2019.
RVKRED09     Check Credit Documentation Background
Checks released documents whose validity period of the release has been exceeded (number of days).
RVKRED88     Simulating Reorganization of SD Credit Data
To run a report:
1.     Choose System ® Services ® Reporting.
2.     Enter the name of the report.
3.     Choose Program ® Execute.
4.     Enter your selection criteria.
5.     Choose Program ® Execute or Program ® Execute and print.
SAP SD Credit Management Tcodes
All business have their own credit management needs, SAP allows you to specify your own automatic credit checks based on a variety of criteria. You can also specify at which critical points in the sales and distribution cycle the system carries out these checks.
SM30 - Table/View
u2022     V_TVTW - Define Distribution Channel
u2022     V_TVTA_KKB - Assign sales area to credit control area
u2022     V_T014 - FI - Define Credit Control Area
u2022     T001CM - FI - Assign Permitted Credit Control Area to company code
OVXG - Set up Sales Areas
e.g. Sales Organization
                  Distribution Channel
                              Division
                  Distribution Channel
                              Division
FD32 - Customer Credit Management
OVAK - Define credit limit check by sales document type
u2022     Check Credit
o     A - Credit limit check and warning message
o     B - Credit limit check and error message (no sales order can    be created)
o     C - Credit limit check and delivery block (block delivery if hit   credit limit)
     Options B and C -> used for checking open order values (when you create/change the sales order)
o     D - Automatic credit control with open order values
     More control in transaction OVA8 - Automatic credit control
     You check for open orders and deliveries, or just open deliveries.
     or open order values with other options
u2022     Credit group
o     Allows you to combine different sales document types for the credit limit check
VKM1 - Blocked SD Documents - Finance have to released the delivery block
OVAD - Define credit limit check by delivery order
u2022     whether the automatic credit check occurs at the time of delivery creation and/or goods issue
OVA7 - Define credit limit check by item category
u2022     Set whether to include/exclude item category for credit limit check
OVA6 - Define credit group. You can groups together different business transactions which should be dealt with in the same manner with regard to the credit check.
You enter the credit groups when you configure the sales document types for credit management and define the (D - automatic credit check).
u2022     SAP default credit groups
o     01 - credit group for sales order
o     02 - credit group for delivery
o     03 - credit group for goods issue
OVA8 - Automatic credit control - Double click on the line items
You can have the followings credit limit check :-
u2022     Static
Depends on the customer total value of open orders, deliveries, billing documents and open items.
u2022     Open items
No of days open
Overdue open items checks is based on the ratio of open items that are overdue by a certain number of days.
Max open items %
The customer balance must not exceed a certain percentage.
u2022     Oldest open items
If you don't want to deliver to the customer at all when even only 1 invoice is overdue.
Tick the Check for Oldest Open Item and Set the field Days oldest item = 1.
Dayu2019s oldest item
No of days allowed for overdue or payment terms.
Use of the credit checks Oldest Open Item. If a user attempts to alter the order quantity of a released sales document
that was previously blocked, it would be re-blocked again by the system. The system only re-blocks the sales document if the new order quantity is above a certain % amount.
u2022     Released documents are still unchecked
The preset % is whatever you want to set it as when configuring your automatic credit processing. You enter a deviation % and number of days,eg, you can set it so that an order can be changed by up to 10% within 30 days of original order entry date without it going back on credit block.
u2022     Next Review Date
If a customer has a credit limit of 1000 USD, and you would like to restrict this credit limit only to be available in current month (say March). If the document date is in April then the credit limit is zero.
You can use the "NextReview date" and "Number of days" fields and combined it with the "Last int.review" field in customer credit master "Status" view (FD32).
VOKR - Display of work list for credit management (configure the display variant)
SIMPLE CREDIT CHECK:
Tr.Code - FD32
It Considers the Doc.Value + Open Items.
Doc.Value: Sales Order has been saved but not delivered
Open Item: Sales Order has been saved, Delivered, Billed & Transferred to FI, but not received the payment from the customer.
Eg: Customer Credit Limit is Rs.1, 00,000/-
Suppose Doc.Value + Open Item Value is Rs.1,10,000/-
Here credit limit exceeds then system reacts.
Options: A) Warning Message
B) Error Message (Sales Order won't be saved)
C) Error Message with Delivery Block
AUTOMATIC CREDIT CHECK: Give extra credit facilities to the particular customer.
STATIC CREDIT LIMIT DETERMINATION: Checking Group + Risk Category + Credit Control Area.
A) Credit Checking Groups: Types of Checking Groups.
01) Sales
02) Deliveries
03) Goods Issue
At all the above 3 levels orders can be blocked.
B) Risk Category: Based on the risk Categories Company decides how much credit has to give to the customer.
HIGH RISK (0001) :      LOW CREDIT
LOW RISK (0002) :      MORE CREDIT
MEDIUM RISK(0003): AVERAGE CREDIT
Static Credit Check it checks all these doc value & check with the credit limit
1) Open Doc.Value / Sales Order Value: Which is save but not delivered
2) Open Delivery Doc.Value: Which is delivered but not billed
3) Open Billing Doc.Value: Which is billed but not posted to FI
4) Open Item: Which is transferred to FI but not received from the customer.
DYNAMIC CREDIT CHECK:
1) Open Doc
2) Open Delivery
3) Open Billing
4) Open Items
5) Horizon Period = Eg.3Months
Here the System will not consider the above 1,2,3& 4 values for the last 3 months
Then assign the Sales Doc & Del Documents.
Sales Doc.Type(OR) + credit Check (0) + Credit Group (01)
Credit Limit Check for Delivery Type : Del.Type (LF) + Del Credit
Group (02) + Goods Issue Credit Group (03)
User Exits For Credit Checks And Risk Management
Credit Check
I hope this will resolve your issue
Thanks
Anil Hooda

COPA Report as Per Characterstics in Variant Configuration

Hi,
I need to develop a COPA Report for the characterstics which are created in Variant Configuration. Kindly help me in bringing those Variant configuration characterstics to COPA.
1. How can i add those characterstics in COPA?
2. How can i bring them to COPA?
3. What should i do if the values of those characterstics into COPA?
Kindly Help me ...
Thanks
Kishore

Hi Kishore,
Please have a look at note 1344848 (Derivation of Variant configuration characteristics). This note explains you all the required steps you should take to derive the charachteristics.
I hope it helps.
Best Regards,
Abhisek

Variant configuration rules verification

Hello All,
We are using variant configuration in our company and have loaded BOMs with rules. So next step is to verify if the rules are correct or not. Now one option is to use CU50 to simulate the config but that can be done one by one material and if you have several charachtericts to assign value to then it becomes very painful to get teh list of components and compare them with the correct list.
So I would like to know if this can be automated using LSMW , BAPI etc. Thanks
Atul

Hi,
You cannot use LSMW or CATT for this purpose. You only have to test each of the dependencies and know the results.
You can use CATT may be to create test cases automatically. Or you can use some other testing tools to test the rules correctly.

Variant configuration steps

Similar Messages

Maybe you are looking for