Sales document (order) credit check

Dear colleagues,
we have an automatic credit check in sales orders . Days overdue - oldest open item. (OVA8)
We want to change this, checking not the overdue days of the oldest open item but the days from create date (of the oldest item) to current date against a specific limit of days for the specific credit area-risk category-doc.
Any help will be appreciated.
BR
John

Hello John,
there is no standard customizing solution for your request.
You might program you requirement in user function 1 in credit management by using
LVKMPFZ1 (FORM USER_CREDIT_CHECK1). If you branch into function module SD_ORDER_CREDIT_CHECK you can use the coding of FORM OLDEST_OPEN_ITEM_CHECK as an example for your needs and change the dates that you would like to check.
Best regards, Baerbel

Similar Messages

Add Sales Document to Credit Limit Calculate

Hi,
How to Add Sales Document to Credit Limit Calculate?
both for, to increase credit limit/to decrease credit limit.
Thanks in advance.
Swetha

Hi,
We assign sales document type to credit group.(OVAK)
With credit groupcredit control arearisk category we maintain automatic credit control
in credit control area we specify the credit limit(FD32) with the indivisual customer.
1) SPRO- Enterprise Structure- Definition-Financial account- Define Credit Control area (OB45)
The Credit limits specified here applies for new customers.
2) Assigning company Code to credit Control (OB38)
3) Credit control area is assigned to the sales area (OVFL)
5) Defining Risk Categories (OB01)-High, low, medium
6) Assign risk category to FD32 customer credit master data
7) OVA7-item category type assignment (credit active)
8) Define credit group (OB46)-sales doc., delivery doc., PGI
9) OVAK-Sales doc. Type assignment
10) Assignment of credit group (OVAD) to sales & delivery & PGI
11) Maintaining Credit limits for Customer FD32
12) Automatic Credit Control (OVA8): credit groupcredit control arearisk category
Edited by: susrikant on Sep 4, 2008 8:02 AM

Sales Order credit check

Hi Gurus,
I'm new to FSCM. My requirement is that I have to implement the BADI UKM_CHECK_STEP so that a Sales Order is blocked when the Payment Term has value 'XXXX' even if the customer has sufficient available credit limit. Can anybody please suggest me how to do it? Do I have to create any credit rule? if yes, how?
Thanks in advance,
Sarif

Hello..
'Critical fields' check in tcode OVA8 also provide similar function to control change of critical fields like payment term, fixed value date, additional value date..
If your requirements is payment term change of sales order, it's not catched in FSCM and it'd be better to develop using Routine in OVA8.
You can control many cheks in Routine. In OVA8 -> No credit check in Document controlling tab.
Your SD guys can help you more detail for this Routine.
About debugging, that BAdI is not debugged while saving order because credit check messages are sent via PI interface(BAdI BADI_SD_CM is last point of debugging before message sent). You can only debug in simulation function of BP or direct run in SPROXY.
Read more docs about FSCM and Credit management and it'd help you.

Sales Order Credit Check after Booking

Hi Gurus,
I have to meet the below requirement in Sales order entry:
Credit Check is enabled during Booking of the sales order. A sales order is entered now with one item and 10 numbers as quantity. While booking, the system checks for credit limit and the order is now in 'Booked' status. Now, when I change the quantity to 15 from 10, the system has to again do the credit checking process. Can this be achieved using functionality like processing constraints or any other? If so please elaborate me the setup required for the same.
Thanks
Best Regards,
Prasad Dhanakodi

Hi Prasad,
When defining the Transactions Type, you need to define the Credit Check Rule when it fires like BOOKING/PICKING/SHIPPING/PAKCING.
Navigation--> Order Management Responsibliity-->Setup-->Transaction Types-->Define
Thanks & Regards,
Srinivasulu Vakati

Order Credit Check of The Dealer

Dear
Hi, This is Little bit techno-Functional , Kindly help me out
This is the Scenario
While Creating delivery from The Sale Order , The Order is blocked due to credit Check .
But Ther dealer is having Least Amount balance, we want to create Delivery For The Avail amount Based on material Wise .In The Order Header status , Credit Check has been updated, we want 2 know which table/ field is updated, when i try to get The field thru F1 help , its found a structure (Description )
Structure name is VBSTT-CMGST_BEZ
I need a Table name / where the description like approved/ released get Saved.
Thanks in Advance

hi
check the following tables hope you may get the required data
VBUK-CMGST
VAKCR-CMGST
REGARDS
rithvika

Order Credit Check for the Dealer

Dear
While Creating delivery from The Sale Order , The Order is blocked due to credit Check
But Ther dealer is having Least Amount balance, we want to create Delivery For The Avail amount Based on material Wise .In The Order Header status , Credit Check has been updated, we want 2 know which table/ field is updated, when i try to get The field thru F1 help , its found a structure (Description )
Structure name is VBSTT-CMGST_BEZ
I need a Table name / where the description like approved/ released get Saved.
Thanks in Advance .

Check the table: VBUP
fields : CMPPI,
LFSTA

Releasing the document from credit check

Hi,
I had a credit check at delivery level and its working fine. Now an order was blocked for delivery. Now I want to release this particular order manually for delivery. Can anyone help me out.
Ramesh

The Delivery Block needs to be manually released in the Sales Order.
On the Initial Screen of Sales Order, remove the Delvery Block
or
Remove the Delivery Block in the Sales Order Header --> Shipping Tab.
Regards,
Praveen
Pl reward if helpful

Credit Check in Sales order with partner other than payer

Hello,
We have typical business scenario in the sales process in yarn industry. Details are mention below:
- Complete sales process starts with agent and ends with agent but payer(debtor) are always the end customer(Form C customers) which are also provided by Agents
- Credit Limit are maintained with respect to Agents and there is no possible combination is to which customer will order goods via which agents
- Major issue we are facing how to perform credit check as at Agent level bcoz invoices are created for end customer
Options:
- In order to use Standard functionality is that created multiple payers in the system belonging to combination of agent and customer and use A/R parent customer concept in credit master data were we can map them as Agent.
But issue with this solution is lot of payers will be created in the system.
Not sure if customer hierarchy concept can be useful.
So kindly request to suggest best possible solution available for above process.
Regards
Sagar

Dear Magge,
This is the standard SAP behaviour. Please refer to SAP Note 706034.
As per this note
"This is required due to the following:
During creation, the credit managment checks a document with "OK". For a
later change of the document, the credit check is "not OK". Since the
reaction "Error message (Error)" is set in the Customizing, the system
could not save the document.
Due to this, the system cannot set the credit status "not OK" for the
document, in order to prevent follow-up activities. Therefore the system
displays a warning message instead of the error message, so that you can
save the document and thus set the credit status (blocked). The document is
blocked now for follow-up activities."
We faced the same issue in our project and found we cannot change the Warning message to Error as it is hardcoded as warning. Hence we used USER EXIT and gave the logic that if this warning message is called when in T code VA02 then throw Error Message.
Hope this will be helpful.
Regards
Mayank

Credit check in sales order

Hi all,
Credit limi check at sales order is working fine, while i am creating a sales order it is giving popup if limit is high then system is giving error message and it is not allowing to save the document. If i save with less quantity and again VA02 with same sales document it is allowing the values if it is above credit limit.
Can anybody suggest where do i check and give the controls
Kindly revert back,
Thanks,
MSRP

Dear Magge,
This is the standard SAP behaviour. Please refer to SAP Note 706034.
As per this note
"This is required due to the following:
During creation, the credit managment checks a document with "OK". For a
later change of the document, the credit check is "not OK". Since the
reaction "Error message (Error)" is set in the Customizing, the system
could not save the document.
Due to this, the system cannot set the credit status "not OK" for the
document, in order to prevent follow-up activities. Therefore the system
displays a warning message instead of the error message, so that you can
save the document and thus set the credit status (blocked). The document is
blocked now for follow-up activities."
We faced the same issue in our project and found we cannot change the Warning message to Error as it is hardcoded as warning. Hence we used USER EXIT and gave the logic that if this warning message is called when in T code VA02 then throw Error Message.
Hope this will be helpful.
Regards
Mayank

Block sales order for credit check

I have created 1 sales order. I want to know how we can find out that sales order is in block.
Also I want to block the sales order created for credit check . What I can do that sales order will go in block.

Hi KiranCG,
--For Credit check go to T.Code FD32 & give customer number & Credit control area & enter the credit limit amount & save it.
-Do the Cutomization for Credit Management
IMG-S&D-Basic Functions-Credit Management & Risk Management-Credit Management
--Define Account groups
--Assign the credit group (01) to your Sales Document type.
--Define Automatic Credit Control (or) T.Code OVA8 Assign CCARisk categoryCredit group -01 (Sales Order) & also Fill the required fields
--In Check column Check mark the Static or Dynamic credit & put reaction as C & check mark the status/block & save it.
--Now raise the sale order in VA01 if the credit limit exceeds the system will through you an error message.But you can still save the document.
--Go to T.Code VKM1 to view the Blocked sales document & enter Credit Control Area,Credit account,Risk category& customer credit group.
--.In order to release the Sales order document go to T.Code VKM3
Let me know if your problem is solved
Regards
Pradeep

Sales order credit control area

Hi,
How can i identify the credit control area the sales order belongs to?
Is there any way to identify in the SO itself?
(not checking the sales org and checking the cc ar)

Credit Control
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
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.
u2022 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 donu2019t 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.Days oldest item
No of days allowed for overdue or payment terms.
Use of the credit check Oldest Open Item. If a user attempts to alter the order quantity of a released sales document
that was previously blocked, it would be reblocked again by the system. The system only reblocks 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 day is in April then the credit limit is zero.You can use the u201CNextReview dateu201D and u201CNumber of daysu201D fields and combined it with the u201CLast int.reviewu201D field in customer credit master u201CStatusu201D view (FD32).
VOKR - Display of work list for credit management (configure the display variant)
Releasing the Credit Block
These are the three transaction code you can used for releasing the SAP credit management block.
VKM3 - Sales Order
VKM5 - Delivery Order
VKM4 - Both Sales Order and Delivery Order
There are basically two types of customers:
1)Credit worthy
2)Normal customers
Coming to credit worthy customers these customers we can believe and we will give some credit ness for them.For such a type of customers we are going to set them some credit limit.Based on that we will give service to them till that limit.It the limit crosses we will get the messages while creating orders for them.
Their credit limit can be set in FD32 T.Code.
Automatic credit check will be maintained in OVA8
Follow these steps:
1. Go to IMG - enterprise structure - definition - financial accounting - define credit control area.
2. Assignment of company code to credit control area & sales area to credit control area.
3. Go to OVAK select ur sales document type and in the check credit column choose from A B or C. D is for automatic credit control for which you have to maintain the credit group and risk categories.
4. In FD32 you select your customer and click on STATUS icon and press enter. here u maintain the credit amount allowed. but this is done by the Finance people.
5. Now when you create the sales order and if the amount exceeds the credit limit then u will get the message as you maintained in the TC OVAK. Normally the system starts doing credit checks from the second sales.
order.
What are the different types of credit checks?
By Sunilmadho
Credit Check can be :
1) Simple Credit Check
2) Automatic Credit Control
Automatic Credit Control can be at various levels :
1) Order
2) Delivery
3) Goods Issue
Automatic Credit Check is of many types :
1) Static
2) Dynamic
3) MaximumDocument Value
4) Maximum Open Items in percentage
5) Oldest Open Item in number of days
6) Crtitical fields change
7) Highest dunning level, etc.
You can create more.
Credit Check happens only in SD module, never in FI. Because the stage of the check is in the sales cycle, which exists in SD. FI guys will check the credit master sheets of the customer, the MIS, the analysis etc, review the credit limits of customers. But the check will happen only in SD, while creating order, delivery or doing the goods issue.
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.
Days oldest item
No of days allowed for overdue or payment terms.
Use of the credit check Oldest Open Item. If a user attempts to alter the order quantity of a released sales document
that was previously blocked, it would be reblocked again by the system. The system only reblocks 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 day 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)
In credit mgmt how the Amount & limit can be can be configured at sales order,delivery & PGI Level.
Please give me the solution .
1)First create Credit control area
Path:IMG\ES\Definition\FA\Define Credit Control Area
2) Assign your credit control area to your company code
Path:IMG\ES\Assignment\FA\Assign Company code Credit Control Area
3) And enter the credit limit using above mentioned transaction code FD32.
4) And assign this credit control area in your customer master Sales Org Data (XD02)
5)if you have maintained the credit control area for your customer then goto T.Code FD32.
6)Enter your customer number and the credit control area.
7)Select the status tab.Press enter.
8)Maintain the credit limit in the field.Save.
9)Go to OVA8 T.Code and then click on open orde

Credit check at Delivery

For one of our risk categories, we would like the credit check to occur at both the Sales Order and Delivery creation events. In transaction OVA8, I have created records for the credit control area/risk category/credit group. The credit groups are assigned to the document types properly (01 - at Order, and 02 - at Delivery).
When I create an order which exceeds the credit limit, I release it from credit block in VKM1. I then proceed to create a delivery. At this point, I would like the delivery to block, but it is not doing so. On the Header--> Processing tab, the Credit Status is "D" (Released). This implies that just because the order was released, the delivery will not block.
A few questions....(a) does the "Number of days" in the risk category need to be set to zero? (b) does the delivery need to have value to block? Any additional thoughts you have would be greatly appreciated.
Thanks.

Dear dbrennan,
It is a standard functionality and for your questions
(a) does the "Number of days" in the risk category need to be set to zero?
SAP says
The current date is not greater than the Release date + the Number of days specified in the Rick category.
and System is not allowing negative ( -1) date too.
(b) does the delivery need to have value to block?
In practical, Is the sales order credit check and Delivery order credit parameters were different?
Regards,
Mani

Sales document creation using bapi

Hi Experts ,
When i try create sales order using bapi " BAPI_SALESDOCU_CREATEFROMDATA'" , it says error like this , Please enter sold to party and ship to party, even though we are sending partner number it shows same error , if we pass values directly in se37 we get the correct result , but when we are calling it in program it says error.
Error on this field : partner Number
Thanks & Regards
Siva Krishna

Hi shiva,
           Please go through the documentation,
Sales document type is checked with sales and distribtion document type.
You must at least enter order header data (using the structure ORDER_HEADER_IN) and partner data (using the table ORDER_PARTNERS).
Furthermore, you must enter the business object for which the sales document is to be created:
               - BUS2030 for inquiries
               - BUS2031 for quotations
               - BUS2032 for sales orders
I think ur program,
does not pass business object , kindly check

User Exit related Credit check

HI All,
I have createed one sales oreder, initailly credit check status is NOT APPROVED, i have released SO manually from t-code VKM3 . then the status has changed to APPROVED.
if change the sales order through VA02 on the same day status is not changes(still APPROVED status, this is fine),
is we change next day(from creation date) credit status is NOT approved..
what user exit is triggering the second block to happen.
we are chnaging bulk sales order, which iare comnig frm Legacy system.
Regards,
DSK

Thank you,
Can u explain some more detail?
How do i check whether VL10C triggers this exit in OVA8?
Actually , it is triggering for VL01N or VL02N but not triggering for VL10c.
And Will there be chances like , it triggers sometimes and not sometimes based on any condition?
Regards
Ramakrishna L

Unable to create a sales document

Hi frns,
while creating sales document (order) an error poping up saying No customer master record exists for Sold to Party.. Pls advise how to solve da above
regards,
kk

There is a possibility that a Customer Master record is not created, or if it is created, it may not be created in the required Sales Area. Please create Customer Master Data in XD01 & after that create Sales Order. It certainly shoule create Sales order. Also check your configuration for SD:
SD Configuration:
Enterprise Structure:
1. Maintaining Sales Organization
Sales Organization is an organizational unit responsible for the sale of certain products or services.
IMG -> Enterprise Structure -> Definition -> Sales and Distribution -> Define, copy, delete, check Sales organization
2. Assigning Sales Organization to Company Code
This assignment ensures all the sales made through this Sales Organization are accounted for in the assigned Company Code (Company Code is created by FI Consultant).
IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign Sales Organziation to Company Code
3. Maintaining Distribution Channel
Distribution Channel is the way, in which Products or Services reach Customers.
IMG -> Enterprise Structure -> Definition -> Sales and Distribution -> Define, copy, delete, check distribution channel
4. Assigning Distribution Channel to Sales Organization
This assignment ensures, a Sales Organization can supply Materials to Customers through this Distribution Channel.
IMG -> Enterprise Structure -> Assignment -> Sales and Distribution > Assign distribution channel to sales organization
5. Maintaining Division
Division is a way of grouping materials, products, or services.
IMG -> Enterprise Structure -> Definition -> Logistics - General -> Define, copy, delete, check division
6. Assigning Division to Sales Organization
IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign division to sales organization
7. Setting up Sales Area
All the sales are made from a particular sales Area. For creating a Sales Order Sales Area is compulsory.
IMG ->Enterprise Structure -> Assignment -> Sales and Distribution -> Set up sales area
8. Assigning Sales Organization- Distribution Channel- Plant
Plant is created ny MM Consultant.
IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign sales organization - distribution channel - plant
9. Define Shipping Points
Shipping Point is the Organizational element, which is responsible for shipping the Materials to the Customers.
IMG -> Enterprise Structure -> Definition -> Logistics Execution -> Define, copy, delete, check shipping point
10 Assigning Shipping Point to Plant
This assignment ensures that goods from different Plant can be dispatched from different Shipping Points.
IMG -> Enterprise Structure -> Assignment -> Logistics Execution -> Assign shipping point to plant
Note: Ensure to do the undermentioned configuration also though it is not in Customizing node of Enterprise Structure.
11. Defining Common Distribution Channels for Master Data
Use
The purpose of this activity is to define distribution channels which have common master data..
Procedure
Access the activity using one of the following navigation options:
IMG Menu -> Sales and Distribution -> Master Data -> Define Common Distribution Channels
Transaction Code: VOR1
12. Defining Common Divisions for Master DataUse
The purpose of this activity is to define distribution channels which have common master data..
Procedure
Access the activity using one of the following navigation options:
IMG Menu -> Sales and Distribution -> Master Data -> Define Common Division
Transaction Code: VOR2
Pricing Procedure
In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.
In SD, the steps to configure Pricing procedure are as under:
Step 1:
Condition table: If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Table (select the required fields combination, which will store condition record).
Step 2:
Access Sequence: If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.
Step 3:
Condition Type: If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Type. It is always recommended to copy an existing similar condition type & make the neccessary changes. Here we assign Access sequence to Condition type.
Step 4:
a. Pricing Procedure: It is recommended to copy a similar pricing procedure & make the neccesary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Maintain Pricing Procedure.
b. Pricing Procedure: After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure.
5. Condition record: Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc.
Normal Sales Order Cycle:-
Step 1: Sales Document Type
IMG > Sales and Distribution > Sales > Sales Documents >
Sales Document Header:
1. Sales Document Type:The sales document types represent the different business transactions, such as Inquiry, Quotation, Sales Order, etc. To create new sales order type, always copy as with reference to similar sales order. If possible use standard sales order.
2. Define Number Ranges For Sales Documents: Maintain number range with discussion with core team.
3. Assign Sales Area To Sales Document Types:
A. Combine sales organizations / Combine distribution channels / Combine divisions: Ensure to maintain these, else Sales Order creation will give error.
B. Assign sales order types permitted for sales areas: Assign only required Sales Order Types to required Sales Area. This will minimize selection of Sales Order Type as per sales area.
Sales Document Item:
1. Define Item Categories: If possible use Standard Item Category. Incase if required to create new, copy as from standard & maintain New.
2. Assign Item Categories: If possible, use standard. Formula for deriving item category: Sales Document Type + Item Category Group + Usage + Higher Level Item Category = Item Category
Schedule Line:
1. Define Schedule Line Categories: If possible use Standard Schedule Lines. Incase if required to create new, copy as from standard & maintain New.
2. Assign Schedule Line Categories: If possible, use standard. Formula for deriving Schedule Line: Item Category + MRP Type / No MRP Type.
Step 2:
IMG > Logistic Execution > Shipping > Deliveries >
1. Define Delivery Types: If possible use Standard Delivery Type. Incase if required to create new, copy as from standard & maintain New.
2. Define Item Categories for Deliveries: If possible use Standard Item Categories for Delivery Type. Incase if required to create new, copy as from standard & maintain New.
3. Define Number Ranges for Deliveries: Ensure to maintain number range.
Step 3:
IMG > Sales and Distribution > Billing >
1. Define Billing Types: If possible use Standard Billing Type. Incase if required to create new, copy as from standard & maintain New.
2. Define Number Range For Billing Documents: Ensure to maintain number range.
3. Maintain Copying Control For Billing Documents: Maintain relevant copy controls such as Sales Order to Billing, Deliver to Billing, etc.
The configuration differs from scenario to scenario & requirement of the client.
Regards,
Rajesh Banka
Reward point if useful.

Sales document (order) credit check

Similar Messages

Maybe you are looking for