Credit Management doesn't release hold from order (11i)

Hi guys...
In some cases Credit Management doesn't release the hold from order automatically.
I'm debugging CM Workflow and I didn't find anything.
So in these cases we need to force it by executing a custom concurrent.
I've found some open bugs at metalink but I'd like to know the reason for that.
Anybody knows?
Tks
Best Regards,

I have a very similar problem:
I wrote an application that uses SAP DI and writes many dozents of draft documents. It doesn´t make a difference if I set
objDoc = objCompany.GetBusinessObject(SAPbobsCOM.BoObjectTypes.oDrafts) for each document or not: every document leeches round about 2-4 MB. That is, in case of an import of 100 documents, up to 400 MB are used.
Isn´t there a possibility to minimize the volume of leeched memory?
Info: I´m using DI and UI, but I am filtering ANY Events from the UI (just need it for singel-sign on).
regards,
Marian

Similar Messages

Credit management: how to release all sales order after credit blocking

Hi,
Is there a way to release all sales orders that have been blocked (for credit limit or late open items) first and for which invoices have been then paid.
That can be done manually with transaction VKM1 but I would like to know if there is any way I could that for all my invoices in the same time and for all my customers?
Thanks in advance for your help.
Ronan

Try using transaction code VKM4.
Rgds,
Nagaraj

Releasing hold by order type

Hi
Is it possible to give the authority of removing hold from the orders of a certain order type to a certain user ?
I have User A and I want him to only release holds from the order type " Alpha"
I have another user b and I want him to only release hold from the order type " beta"
Version: Oracle EBS 11.5.10.2
Regards
Nouman Shaikh

1) If you can create 2 holds such as Alpha Hold and Beta Hold, then you can give RespA the access to release Alpha Hold and RespB the access to release the beta hold. And then you can give the responsibilities to appropriate users.
2) If that is not possible, you can consider writing a personalization on the release screen that enforces your rule.
Hope this helps,
Sandeep Gandhi

Credit Management: Use of release button in VKM2

3)what is the use of release button in VKM2. where does it releases?
Notes: If Credit Management is activated at Sales Order level and the credit block is removed through VKM1,VKM3 or VKM4, we can see the in VKM2 transaction code. But in VKM2 transaction code, we have release option .
What is the purpose of this options. Please assist me regarding the VKM2 transaction code.

The release button in VKM2 will have no affect on the document if it has already been released. I guess that if you release the document again the release date would be updated but nothing more.
I hope this helps.
Gerard

Update Credit managment dispay in some of the orders with same Payer

Hi,
I have some sales orders created with same PO, same sold to party and same payer. In one of the Sales Order
credit control area and credit account is updated but the other order's did not update with this information.
I can see the Credit account dispay in that Sales Order which got updated but the other orders are giving the message "Cannot display credit limit as no credit management account is available"
Please let me know how to fix the other Sales orders Credit accounts, these all orders have same Payer and we have issue in the Consolidate billing of these orders and all these orders have subsequent documents like Delivery and Invoice.
VBAK-KKBER and VBAK-KNKLI fields are blank in these Orders except the one which got updated.
Thanks in advance.
- Fract

Hi Charles,
The Order with values filled in VBAK-KKBER and VBAK-KNKLI is not a latest order, We have orders after and before this order also.
I already executed F.28 but nothing got changed.
Regards,
Fract
Edited by: fract_get on Nov 15, 2011 10:26 PM

Dynamic Credit Management - issue with released documents

Hi,
I have a problem concerning automatic credit check.
In my project we activated the option "Dynamic Credit Check" to check the customer credit exposure and also the open order value.
Everything is working perfect, and the system blocks when the conditions are not meet.
The problem is:
When the SO is blocked, and after beeing released, everytime we save that SO it triggers the credit check and put it blocked again.
Even with a simple output msg creation, or a change in a text field, triggers the credit check, and everytime we must to release the SO again.
In customizing I see that there are the parameter "Number of Days" in tab "Released Docs are Still Unchecked", however it seems that parameter has no any effect with "Dynamic Check" option.
Do you know if there is some way to avoid to do SO release again and again (after release first time)?
Many thanks,
André

Dear Andre,
this is the standard SAP behavior, I mean when ever you are changing any thing in the sales order after releasing the Credit block which may again affect the credit, it will go into the credit Block again.....
And in your case also it might be the problem. So after releasing when you are saving the sales order, again Dynamic credit check is occurring and putting Sales order into block.
If you dont want this, then follow these
1. Go to VOFM :
2, Click on requirement --> credit check...
3. Write a suitable routine with the help of ABAPer for bypassing check on the things like, adding text, some small modification etc, but not for Quantity and Value
4. Assign this routine in OVA8 for credit group + risk category + credit group combination.
I hope it will help.
Thanks,
Raja

Credit Management - Document somehow released via VA02

I have a sales document that shows Overall status of Credit Checks changed via VA02 in the change log. There have been no changes to the customer activity (Payer) that would justify this. No payments have been posted, orders cancelled, returns received etc. The document should have remained on credit hold.
The user that modified the sales doc only made a few changes and that was to some delivering plants for several line items. These changes then updated availability, etc (moved confirmed schedule lines to further in the future). However, they also somehow changed the credit status on the order (VBUK-CMGST) from B to A.
Additionally I have checked VBAK-CMNGV (next date) for the document and found it to be in the past which is rather odd considering there are multiple line items with upcoming confirmed availability via the schedule lines.
Note that I have a similar thread in which I need to know how the users can manually change the status of VBUK from A back to B

Hi Rebecca,
I would recommedn the following steps:
- First run report CHECK_CM to get an overview of the affected sales document.
- set a breakpoint in FM sd_order_credit_check and do a recheck in TA VKM4.
- check the user-exits in MV45AFZZ: are there field UPDKZ or internal tables like XVBAP, XVBEP modified.
Regards,
Andreas

User Exit for credit management at confirmed quantity in sales order

Dear All ,
kinldy tell how to define a user exit and where i can write for credit check to be done to the confirmed quantity in the sales order .
Also pls tell me that how to define the user exit and attach to customer reserve field in the customising for automatic credit control .
regards
Baranidharan Ramar

Hi
The following is the information from the sap documentation...you can also refer from IMG - SD - System modification - userexit - userexit for credit check
Credit Check
If you want to carry out your own individual credit checks, that differ from those in the standard system, you must define them in the following user exits:
LVKMPTZZ
LVKMPFZ1: USER_CREDIT_CHECK1
LVKMPFZ2: USER_CREDIT_CHECK2
LVKMPFZ3: USER_CREDIT_CHECK3
User exit for availability check
User exit USEREXIT_AVAIL_CHECK_CREDIT exists in Include MV45AFZF.
This user exit allows you to determine whether the system should or should not carry out an availability check after a blocked document has been released or after a new credit check.
Thanks,
Ravi

Availability Check , Credit Management

currently when sale order is blocked due to credit management check and released after few days ( say 2 or 3 days) the availablity check is not activated .( it means that the delivery date will be the old schedule line date) but the document is released after couple of days due to business reason.
The solutions which we are currently working on
1) we have found a user exit in system modifications - not meeting our requirement.
- we need to run thre availablity check when it is released from vkm1 or vkm3 as though we are entering new lines in va02. ( release date will be the current date)

Hi,
I'm not sure whether I understand your problem proberly. But perhaps you have a look at the program SDV03V02 (Transaction Code V_V2). Perhaps you can run it as a job and got the new availability after release the sales order for credit check.
Regards Thomas

Open Billing Doc value table in Credit management

Hello All,
I am having the open billing document vaule in credit management,
I need the details that from which billing document, what value has come.
Is there any table for get these details.
Advance thanks
Thanks and Regards
Sridhar

Hi,
the system updates open values for credit management. These are:
Open sales order credit value (S066-OEIKW)
Open delivery credit value (S067-OLIKW)
Open billing document credit value (S067-OFAKW)
The system updates the open values in standard SIS structures S066 and S067. Technically, the structures are transparent tables. You can display the contents using transaction SE16 or using table maintenance.
The S067-OLIKW will give the open delivery credit values credit.Check in you system whether this table is updated with the delivery values for the credit account(customer number)
RVKRED77 u2013 Reorganize SD credit data
When updating errors occur, it enables you to reorganize the open credit, delivery and billing document values.
If the table is not updated run this report in background.
Regards,
Saju.S

Credit management urgent

Dear sap gurus,
after implementing credit management in middle or not from beginning and if you want to have the history a particular customer updated in LIS or if we want to know about his credit exposure.
What should be done.Kindly help me.
regards,

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.
Difference Between Simple and Automatic Credit Check Types
In automatic check, difference between static and dynamic checks.
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 & Transfered 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 Catageory + 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 Catageory : Based on the risk catageories company decide 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 delievered
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 transfered 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 lost 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)
Set Up for Credit Card Payment Processing
Given below is the set up for credit card payment processing:
Set Up Credit Control Areas:
Define Credit Control Area
Transaction: OB45
Tables: T014
Action: Define a credit control area and its associated currency. The Update Group should be u201800012u2019. This entry is required so the sales order will calculate the value to authorize
Assign Company Code to Credit Control Area
Transaction: OB38
Tables: T001
Action: Assign a default credit control area for each company code
Define Permitted Credit Control Area for a Company
Code
Transaction:
Tables: T001CM
Action: For each company code enter every credit control area that can be used
Identify Credit Price
Transaction: V/08
Tables: T683S
Action: Towards the end of the pricing procedure, after all pricing and tax determination, create a subtotal line to store the value of the price plus any sales tax. Make the following entries:
Sub to: u201CAu201D
Reqt: u201C2u201D
AltCTy: u201C4u201D
Automatic Credit Checking
Transaction: OVA8
Tables: T691F
Action: Select each combination of credit control areas, risk categories and document types for which credit checking should be bypassed. You need to mark the field u201Cno Credit Checku201D with the valid number for sales documents.
Set Up Payment Guarantees
Define Forms of Payment Guarantee
Transaction: OVFD
Tables: T691K
Action: R/3 is delivered with form u201C02u201D defined for payment cards. Other than the descriptor, the only other entry should be u201C3u201D in the column labeled u201CPymtGuaCatu201D
Define Payment Guarantee Procedure
Transaction:
Tables: T691M/T691O
Action: Define a procedure and a description.
Forms of Payment Guarantee and make the following entries Sequential Number u201C1u201D
Payment Guarantee Form u201C02u201D
Routine Number u201C0u201D Routine Number can be used to validate payment card presence.
Define Customer Payment Guarantee Flag
Transaction:
Tables: T691P
Action: Define a flag to be stored in table.
Create Customer Payment Guarantee = u201CPayment Card Payment Cards (All Customers can use Payment Cards)u201D.
Define Sales Document Payment Guarantee Flag
Transaction:
Tables: T691R
Action: Define the flag that will be associated with sales document types that are relevant for payment cards
Assign Sales Document Payment Guarantee Flag
Transaction:
Tables: TVAK
Action: Assign the document flag type the sales documents types that are relevant for payment cards.
Determine Payment Guarantee Procedure
Transaction: OVFJ
Tables: T691U
Action: Combine the Customer flag and the sales document flag to derive the payment guarantee procedure
Payment Card Configuration
Define Card Types
Transaction:
Tables: TVCIN
Action: Create the different card types plus the routine that validates the card for length and prefix (etcu2026)
Visa , Mastercard, American Express, and Discover
Create the following entries for each payment card
AMEX American Express ZCCARD_CHECK_AMEX Month
DC Discover Card ZCCARD_CHECK_DC Month*****
MC Mastercard ZCCARD_CHECK_MC Month
VISA Visa ZCCARD_CHECK_VISA Month
The Routines can be created based on the original routines delivered by SAP.
*****SAP does not deliver a card check for Discover Card. We created our own routine.
Define Card Categories
Transaction:
Tables: TVCTY
Action: Define the card category to determine if a
payment card is a credit card or a procurement card.
Create the following two entries
Cat Description One Card Additional Data
CC Credit Cards No-check No-check
PC Procurement Cards No-check Check
Determine Card Categories
Transaction:
Tables: TVCTD
Action: For each card category map the account number range to a card category. Multiple ranges are possible for each card category or a masking technique can be used. Get the card number ranges from user community. Below is just a sample of what I am aware are the different types of cards.
Visa Credit Expires in 7 days.
400000 405500
405505 405549
405555 415927
415929 424603
424606 427532
427534 428799
428900 471699
471700 499999
Visa Procurement Expires in 7 days.
405501 405504
405550 405554
415928 415928
424604 424605
427533 427533
428800 428899
Mastercard Credit Expires in 30 days
500000 540499
540600 554999
557000 599999
Mastercard Procurement Expires in 30 days
540500 540599
555000 556999
American Express Credit Expires in 30 days
340000 349999
370000 379999
Discover Card Credit Expires in 30 days
601100 601199
Set Sales Documents to accept Payment Card Information Transaction:
Tables: TVAK
Action: Review the listing of Sales Document types and enter u201C03u201D in the column labeled u201CPTu201D for each type which can accept a payment card
Configuration for Authorization Request
Maintain Authorization Requirements
Transaction: OV9A
Tables: TFRM
Action: Define and activate the abap requirement that determines when an authorization is sent. Note that the following tables are available to be used in the abap requirement (VBAK, VBAP, VBKD, VBUK, and VBUP).
Define Checking Group
Transaction:
Tables: CCPGA
Action: Define a checking group and enter the
description. Then follow the below guidelines for the remaining fields to be filled.
AuthReq Routine 901 is set here.
PreAu If checked R/3 will request an authorization for a .01 and the authorization will be flagged as such. (Insight does not use pre-authorization check).
A horizon This is the days in the future SAP will use to determine the value to authorize
(Insight does not use auth horizon period).
Valid You will get warning message if the payment card is expiring within 30 days of order entry date.
Assign Checking Group to Sales Document
Transaction:
Tables: TVAK
Action: Assign the checking group to the sales order types relevant for payment cards
Define Authorization Validity Periods
Transaction:
Tables: TVCIN
Action: For each card type enter the authorization validity period in days.
AMEX American Express 30
DC Discover card 30
MC Master card 30
VISA Visa 7
Configuration for clearing houses
Create new General Ledger Accounts
Transaction: FS01
Tables:
Action: Two General Ledger accounts need to be created for each payment card type. One for A/R reconciliation purposes and one for credit card clearing.
Maintain Condition Types
Transaction: OV85
Tables: T685
Action: Define a condition type for account determination and assign it to access sequence u201CA001u201D
Define account determination procedure
Transaction: OV86
Tables: T683 / T683S
Action: Define procedure name and select the procedure for control. Enter the condition type defined in the previous step.
Assign account determination procedure
Transaction:
Tables:
Action: Determine which billing type we are using for payment card process.
Authorization and Settlement Control
Transaction:
Tables: TCCAA
Action: Define the general ledger accounts for reconciliation and clearing and assign the function modules for authorization and settlement along with the proper RFC destinations for each.
Enter Merchant IDu2019s
Transaction:
Tables: TCCM
Action: Create the merchant idu2019s that the company uses to process payment cards
Assign merchant idu2019s
Transaction:
Tables: TCCAA
Action: Enter the merchant idu2019s with each clearinghouse account
Reward points if useful.
Regards,
Anbu

"Sales value" in FD33, credit management

Hi Experts,
I have configured Credit management.
After creating a sales order. The field "Sales value" (RF02L-SAUFT) in FD33 is NOT getting updated. It remains 0,00.
After I have created a bill, field "Receivables" gets updated.
Could you please advise how field "Sales value" could be correctly updated (i.e. with values of the sales orders that have not yet been transferred to FI )?
Because of the above, I can not get a warning or error message, at creation of sales order stage, when credit exposure > credit limit.
PS - I have tried VKM3, releasing sales orders, but issue still persists.
I have also executed RVKRED77

Hey!
Go to transaction VOV7 and make sure of the following:
n item is relevant for billing
n item is relevant for credit
n the item does not have a check mark in ‘item relv for delv’. This is for text and value items which have no value in R/3 – see note 67748
n the item is not statistical
If these are not configured correctly, the item will have no value.
Go to the sales order and make sure that the items have a confirmed schedule line. Without a confirmed schedule line, the item will have no credit value. Next check the pricing procedure. You can go to the analysis button to find out which pricing procedure is being used. Go to transaction V/08 and go to the details level of the pricing procedure. Make sure that an ‘A’ is set in the ‘Sub to’ column for something reasonable like the total of the document.
Hope it helps.

Any batch process to release the sales order with status profile

Hi,
The sales manager need to release the sales order 1 by 1.
This is very tedious.
Is there a process for her to release selectively?
For example,
if the sales value of the order is visible and within the approval limit or too small,
she could release, says, more than 10 sales order in a single click.
Possible?????
Bye

Hi,
I like to perform a mass release of multiple Sales order from the proposed custom report.
I would like to built the releasing coding into the report.
I need some references on how to set the release.
Maybe, there is a standard function for me to pass it in and it would release the sales order status.
if that the case, it is BONUS.
Otherwise, there must be some steps that need to be built to set the release.
what I am asking, is there any such routines that would define the steps to release the sales order in coding?
I understand there would be a change in status aftef the released and it is also vital to enable the audit log for future investigation.
Having a BAPI would result the audit issue as the system would have taken care of it.
I hope it is clearer now as to why I am requesting a sample of the standard routine.
If there is no such routine, do let me be aware of it.
Thanks

Open Delivery value update error in credit management

Hi
We have credit management active at delivery level. The value of open deliveries is not getting updated correctly for items with material substitution (material determination). For all other items, its getting updated correctly.
E.g Let say the credit limit set in FD32 is 10000 and the credit limit used % is 98 and the credit exposure value is 9800.
Now when I create an order with qty 10 for mat A, it creates a sub item B due to material determination and the value of the item is Rs.1200. In our system, the sub item with TAPS item category is relevant for pricing.
Then I create a delivery in VL01N and save it.
Now if i check in FD33, the credit limit used should be 101% and the credit exposure value should be 11000, but its not updating the open delivery value correctly. Its not considering the value of the new delivery.
However, If I add a normal item (TAN) in the same sales order and create a delivery for that item and save it, its updating the credit exposure based on the value of the normal item in the delivery correctly.
How to make the system update the open delivery values correctly by taking the items with material determination also into account.??
Please advise if any specific settings need to be done.
Regards
Madhu

Hi,
the system updates open values for credit management. These are:
Open sales order credit value (S066-OEIKW)
Open delivery credit value (S067-OLIKW)
Open billing document credit value (S067-OFAKW)
The system updates the open values in standard SIS structures S066 and S067. Technically, the structures are transparent tables. You can display the contents using transaction SE16 or using table maintenance.
The S067-OLIKW will give the open delivery credit values credit.Check in you system whether this table is updated with the delivery values for the credit account(customer number)
RVKRED77 u2013 Reorganize SD credit data
When updating errors occur, it enables you to reorganize the open credit, delivery and billing document values.
If the table is not updated run this report in background.
Regards,
Saju.S

How to set the overall credit status as "partial release" on SO header?

Hey guys,
Do you have any idea on how did the overall credit status become "partial release" on sales order header level?
Because as my understanding in SAP, i am not sure whether there is a way to partial release a sales order with multiple item lines.
Jasper

Hi balajia,
after seeing your description i have gone to VKM4.
i have executed OVER ALL CREDIT STATUS with A.
then i am able to see one sales order with OVCS - 'A'.
then i have given OVCS as 'B' & also "C' - i am not able to see any sales order OVCS as B & C.
that means here there are options to use if OVCS in sales order status is B or C as it has executed for A.
so,
some where in sales order program it is hard coded i think so - i am saying this because there is a link between sales order header:
Delivery status Not delivered
Credit status Not performed
Overall blkd status Blocked
so if it is hard coded with B and C also you can use these options in VKM4.
that's is what my R & D on this says.
regadrs,
balajia

Credit Management doesn't release hold from order (11i)

Similar Messages

Maybe you are looking for