Sales Order Credit Block To Allowed Confirmed Quantity
目录
I would like to keep the Credit Status Block on a Sales Order when it is created and over the credit limit and at the same time be able to Confirm the Order Quantity (if inventory is available) on the Schedule Line.
In the IMG --> Sales and Distribution --> Basis Functions --> Credit Management/Risk Management --> Credit Management --> Define Automatic Credit Control --> If I remove the Status/Block indicator the schedule line does confirm the sales order quantity but the sales order is not blocked and a delivery can be created.
Answer
Please go to IMG -> Sales and Distribution -> Basis Functions -> Transfer of requirements -> Maintain requirements for Transfer of Requirements and remove the 101 Routine number so that when credit block on order, still the quantity is confirmed to sales order. Because of this Routine it is removing the reservation while in credit block.
I have tested it and it is working. I have similar scenario and it is working fine.
Other Suggestion 1
There are two ways to block the sales order - one is to not confirm the Schedule line i.e. block delivery... block further action that can be taken. The second is to not let the person save the sales order.
Another option is to get Just a warning message, that the credit limit has been exceeded, but able to save the sales order with a confirmed schedule line.
The setting will be in OVA8.
For the Document Value you make the setting C or A. and make sure the block is not set.
Don't worry about the Open order or open delivery unless you want the system to perform a credit check considering the orders that are already existent. Same with open delivery. It will take into account all the cost of the orders that are open for delivery.
Now here some options
Either consider a 'warning' by the system good enough and still be able to confirm the schedule line.
(ii) Put in a Delivery Block in the Sales Document Types, in the Shipping tab. That way, you will be able to save the sales doc. but not be able to deliver it.
(iii) Put a Billing Block in the Sales Doc type, in the Billing tab. You will be able to deliver but not bill.
(iv) Create a new routine (with the help of an ABAP guy) and place it in the auto credit check, 'Reaction' field where it will place a Delivery Block.
Other Suggestion 2
Another option is that you go to SPRO -> Sales and Distribution -> Basic Functions -> Availability check and Transfer of Requirements -> Transfer of Requirements -> Block Quantity Confirmation in Delivery Blocks
Select Deliveries: Blocking reasons/Criteria
Now here you can either create a new entry or go with 01- Credit limits.
There will be Conf. with a check mark on it. Remove that. And to make sure that the sales order is not printed, check mark where it says 'Print' and 'DDueList' (so system won’t create delivery automatic).
This way, the sales order will be saved with a confirmed schedule line, but picking or automatic delivery creating won’t happen. It will need to be manually processes further on.
Notes
Please also see OSS Note 886038 - No confirmed quantity after sales order credit release
Credit value update problem
Skip to end of banner
Go to start of banner
Possible causes of inconsistencies
Skip to end of metadata
Created by Former Member on Jan 26, 2015
Go to start of metadata
Symptom
You determined that there are inconsistent credit values in the system. How this can be done you can read HERE.
You would like to know why this happens.
Analysis
To avoid that problem is caused by a program error please check the support package level of your system (Menu: System -> Status: SAP System Data, Product version, open the Components with the loop and search for SAP_APPL). With that please search for program errors in the component SD-BF-CM and implement these notes.
Check which update type is used for the info structure S066. For that goto 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. See also SAP Note: 426202 - Incorrect update of credit values during V2 update
The update modes V1 (synchronous) and V2 (asynchronous) work as follow
V1: If there are problems that result in the termination of statistics, the original documents are NOT saved.
V2: With this update type, the document update is made separately from the statistics update. A termination of the statistics update has NO influence on the document update.
That means, with the V2 update it is possible, that update of statistics values (e.g. credit values) terminates, but the document is updated. So the credit values are not updated in such a case. When using the V1 update, this can not happen. In V1 update, when statistics update terminates, the document is not saved. That's the reason why it is very important to choose the V1 update for credit values.
In most of the cases the wrong updates are caused by customer modification of the field UPDKZ in userexits. Please read SAP Notes 178328 and 208010 and review your userexits (especially MV45AFZZ and for LE please see note 415716 - User exits in delivery processing).
There is an analysis tool also available with regard to userexit modification effects on credit values, please see these notes 1612842 and 1606681 and ensure all related notes are implemented too.
Further on this please read here: UPDKZ modification
It can be caused by incorrect customizing. especially with batch subitems. For that please read these notes:
77414 - Billing during batch split
860621 - Negative open delivery value with batch after billing doc
1714643 - RVKRED77: Incorrect values for batch and FKREL = "H"
There are some special cases when RVKRED77 does not correct the values or it calculates an incorrect open credit value. Please read HERE more about that.
Confirmed quantity is present in the order, but there is no updated credit value
Skip to end of metadata
Created by Former Member on Nov 24, 2014
Go to start of metadata
Symptom
Sales order is credit blocked, VBUK-CMGST = B;
Standard requirement 101 is used for the follow-on function 'Reqs/availability';
Even though the confirmed quantity is not deleted;
As a result, you expect the system to update an open credit value (S066-OEIKW) based on the confirmed delivery that is still to be delivered.
Analysis
The condition 101 for the follow-on function requirement/availability is not valid for items that are not relevant for requirements and therefore are not MRP-relevant. How you can determine this, you can read HERE. In case of a non-MRP material, the system does not remove the confirmed quantity if there is a credit block (VBUK-CMGST = 'B').
Please check if the Transfer of requirement is deactivated (-BEDSD = ' ') for the relevant items either in schedule line category (TVEP) or in the requirements class (T459K). How you can check this, please read HERE.
If the transfer of requirement is deactivated for the non-MRP materials, even though there is a confirmed quantity in case of a credit block, no credit value update occurs. During the update of open credit values, these items behave in the same way as an item that is relevant for requirements and ATP-relevant.
For these items the credit value is updated once the sales document is released.
Please read SAP Note: 914627 - No open credit value despite confirmed quantity
Credit value calculation of a document
Skip to end of metadata
Created by Former Member on Jan 15, 2015
Go to start of metadata
You would like to know how is the credit value of a document calculated.
For the necessary customizing settings please read note 18613. Also you can use report CHECK_CM to check sales documents with regard to their credit management information in one step. You can read more about this HERE.
For the credit price calculation following needs to be determined in the sales order:
Credit price - CMPRE
Transaction V/08 - In the pricing procedure used for pricing, subtotal "A" must be entered in a line for determining the credit value. 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".
Than go to V/08, Pricing procedure, select the corresponding one, mark the pricing procedure and doubleclick on "Control". Search for the line with subtotal = 'A'
Confirmed quantity - KBMENG
If an item has no confirmed quantity (VBEP-BMENG), the system does not calculate nor update an open sales order value.
This also occurs for documents that are blocked by the credit check. As a result of the credit block, the confirmed quantities are deleted so that an open sales order value can no longer be updated.
You can use requirements to delete confirmed quantities in credit blocked sales orders. These requirements are defined in transaction VOFM under the menu path 'Requirements -> Subsequent functions -> Reqs.availability'. The system asks you for a credit status in the respective user requirement. If this is set to 'Blocked', the system cancels the confirmed quantity. In the standard the requirement 101 is used for this purpose.
You may want the system to behave differently. If this is the case, you can store a separate requirement which does not cancel the confirmed quantity. As a result, the sales order item has a confirmed quantity again and consequently, it updates the open sales order value although the document is credit blocked.
...
