Simple Credit check _ User Exits

Dear Expert,
Please find my scenario,
I am using simple credit check
When i am creation sales order with reference to quotation
Item Amount
00010 1000
00020 2000
I am getting two messages
1)Credit limit exceeded by 1000
2) Credit limit exceeded by 3000(1000+2000)
But Customer wants in one message like Credit limit exceeded by 3000
Please advice, its very urgent
and also suggest if any user exits available
Regards

Thank you for your reply
Is it possible to achieve the same by using static credit check?
When i tested this static check, i am getting message for the first line item
Ex:
Item      Amount
0010      100
0020      200
System shows " Static credit check 100 Exceeds" and it goes to sales order details screen when i am referring from quotation.
Regards

Similar Messages

Simple credit check for service orders(TAD)

hi
we have configured simple credit check for ZOR and with delivery block. since TAD is order related billing even though credit limit exceeds they can bill the customer.Now I have to configure simple credit check for serive orders with item category TAD and it should give billing block.please give me the details on this.

Hello Chait
To release credit block from CRM GUI, please go to header status tab here is the button 'Credit Release'.
To release credit block in WEBUI, please check the items block, in more functions you can find the 'release credit block' link.
Best regards,
Maggie

Simple credit check - value need to be blocked from particular sales order to be post in f.35

Dear Expert,
I have a case here to find, the client uses simple credit check , we have different order types ( Example 6 order types), out of which we want to restrict the value of one order type to be posted in f.35 i.e the value should not effect credit limit used or open sales order.
Is there any standard procedure by which this can be done or do we have to use userexit.
Also can i know in which screen do we have to keep the userexits so that the value of the order type will not have impact on the f.35 or crdit limit used.
Regards
Abhishek Ojha

Sorry small correction to my initial post.
Even though you removed the credit group for the respective sales order type still system update the values subject to if the respective item category the "field credit active" active.
Removing the credit group to sales order type controls whether you want to perform the credit check or not. And your requirement is not to update the particular sales order document values in FD32 so the actual control is credit active field for that particular item category.
Since you have mentioned that you don't want to update that particular sales order document values( assuming that you are taking about receivable only).
Please note sales order determines the item category, so do as below.
De select( un check) the credit active field in the item category which is determined based on the sales order type for which you don't want to update credit values.
Please test and update here.So far I did not check this in my system.
thanks,
Srinu.

What is Simple Credit check??

Can any body explain about Simple credit Check??

A credit limit check can be carried out when sales documents are created or changed. The check is carried out within one credit control area . When changing a document, the check is repeated if changes regarding quantity or value are made. A credit control area consists of one or more company codes. A sales document belongs to one credit control area depending on the allocation of the sales organization to a company code. The SAP System checks the credit limit which was granted to the customer in this credit control area. The credit control areas and the credit limit of a customer are defined in financial accounting and entered in the customer master record. During the check, the SAP System totals the receivables, the items from special G/L transactions and the net value of the sales order for every item of a sales document. The open items take into account obligations bound by contract which are not recorded for accounting purposes but which involve expenses through diverse business transactions. The total is compared with the credit limit. If the limit is exceeded, the system responds in the way defined by you in the configuration menu.
Requirements
The sales document types must already be defined. The SAP System automatically proposes the defined sales document types for maintaining the credit limit check.
Actions
Define whether a credit limit check should be carried out for the individual sales document types. Also define how the system should respond if the limit is exceeded. The following system responses are possible:
Warning
Warning and delivery block
The document can be saved but is automatically blocked for delivery.
Error message The document cannot be saved.

Automatic V simple credit check

what r the advantages of automatic over simple credit management

Simple credit limit check
A credit limit check can be carried out when sales documents are created or changed. The check is carried out within one credit control area. When changing a document, the check is repeated if changes regarding quantity or value are made. A credit control area consists of one or more company codes. A sales document belongs to one credit control area depending on the allocation of the sales organization to a company code. The SAP System checks the credit limit which was granted to the customer in this credit control area. The credit control areas and the credit limit of a customer are defined in financial accounting and entered in the customer master record. During the check, the SAP System totals the receivables, the open items from special G/L transactions and the net value of the sales order for every item of a sales document. The open items take into account obligations bound by contract which are not recorded for accounting purposes but which involve expenses through diverse business transactions. The total is compared with the credit limit. If the limit is exceeded, the system responds in the way defined by you in the configuration menu.
Automatic Credit Check
The automatic credit check can target certain aspects during a check and run at different times during order processing. In this menu option, you can define your own credit checks to correspond to your requirements in the area of Credit Management.
You can determine an automatic credit check for any combination of the following:
Credit control area
Risk class (classifying attribute for your customers from the viewpoint of credit risk which is maintained in FI Customizing)
Credit group
Example
You can define a credit check for a certain credit control area and for all sales orders in which the customer has risk class 2 (RK2).
It is possible to define a system response for each credit check (for example, warning message). In the case of a warning message, a block can be set in the credit status of a document.
When you define automatic credit checks, you can also freely define requirements which cause a document or the forwarding of the material requirements to MRP to be blocked. This is described in the IMG section "Make default settings for Credit Management".
If you define your own credit checks, proceed as follows:
specify type of check
specify scope of check
specify system response to check
allocate credit control areas
define and allocate risk classes if necessary
allocate credit group
assign description to the credit check
Types of credit check
The following types of credit checks can be carried out:
Static credit limit check
Credit allocation depends on the total value of open orders, deliveries, billing documents and open items.
Dynamic credit limit check
The dynamic check includes both a static part which checks all open items, deliveries and billing documents and a dynamic part which checks all outstanding order values, that is, all orders not yet delivered or partially delivered. The value resulting from the checks is accumulated up to the shipping date in the information structure "S066" in freely definable time units or periods (day, week, month). This information structure is entered in Logistics Controlling and described in the section "Carry out default settings for credit management" under Basic functions.
To define the credit check, you specify a certain number of relevant periods from which a date in the future can be calculated (for example, 10 days or 2 months depending on the selected period). This ensures that sales orders which lie further in the future are not used to determine the credit exposure.
The total of the static and dynamic part of the check must not exceed the granted credit limit.
Credit check on the basis of the maximum document value
The sales order value or the value of goods to be delivered must not exceed a certain value defined for the credit check. The value is stored in the currency of the credit control area. In particular, this check is useful if the credit limit of new customers has not yet been specified. This check can be accessed explicitly by a risk class reserved for new customers.
Credit check when changing critical fields
The credit check is started when changes are made to credit-relevant document fields so that they differ from the default values proposed from the customer master record (terms of payment, value days and fixed value date).
Credit check at the time of the next internal check
The credit check is started automatically on a certain date. All sales orders entered up to this time are regarded as not critical.
Credit check on the basis of overdue open items
The ratio between open items, which are overdue by more than a certain number of days, and the customer balance must not exceed a certain percentage.
Credit check on the basis of the oldest open items
The oldest open item may only be a certain number of days overdue.
Credit check against maximum allowed dunning levels
The dunning level of the customer may only assume a certain maximum value.
Customer-specific credit checks
If you require further checks to those defined in the standard system, you can define them in the corresponding user exits (LVKMPTZZ and LVKMPFZ1).
Regards
Nadarajah Pratheb

Checks Or User exits in PP

Hi experts
My user is asking for two check points,
1.If sale order line item is closed,It should not allow to Create production Order,can this be possible through User exit.
2.Production order Qnty for Particular Sale Order Line item, should not be allowed to Create more than sale Order Line item quantity.
ex-Suppose SO line item qnty is 100pc,Po should not be allowed to Create more than 100Pc.
Regards
Sandeep patil
Edited by: Isabelle Britten on Jul 15, 2008 8:40 AM

Hi,
I think your scenario is Make to Order, then
Try below user exit for Production Order when saving exit will work - PPCO0007 (goto SMOD) - Function module - EXIT_SAPLCOZV_001
sit down with your ABAPer on this
you need to consider below
1.Sales order line closed or open status (Table VBAP and VBUP)
2.Sales order line Qty (Table VBAP)
Regards,
Sankaran

Infotype check and user exit

hi All,
With the help of answer from my previous post I understand that I need to implement a user exit to do a particular check on my field. Actually when a user inputs a field then i need to compare it to field from some other table.
My doubt is what user exit i need to use..
ZXPADU01 or ZXPADU02 or ZXPADU03.
My understanding is that ZX*02 is for me since it is implemented in PAI module of screen 2000 for MP999900.
Also can someone explain what different situations we need to use this exits?
Also please mention if BADI exists with the same functionality.
thanks and regards,
Reena

if it is a Z infotype then as per my previous post just go to se80 and ur concerend module pool program.
and write a module in PAI on tht particular field as in my post..
if u want to compare it with another table value then u can simply fetch data frm tht table in this module and compare it with ur field.
U need not to go for USer Exit for the Z infotype.
amit

NOTIFICATION STATUS CHECKING IN User Exit 'QQMA0014'--iw21

Hello,
Myself sudip..i have to do a exit on QQMA0014 for iw21 ...so. i need to check every time notification status field( STTXT ), contain value osno/techo...when osno then something happen and also when techo something will happen..but how to check notification status field.( STTXT ).can you help me....PLEASE....
VALUE T_VIQMMA ONLY CONTAIN THAT FIELD .THAT'S WHY I USED IT FOR STTXT CHECKING..BUT CAN'T GETTING....

Hi Sudip,
I think I can help you.
One correction in your post. There will not be TECO. It is NOCO in Notification
This is the answer
There is no need of STTXT for your purpose. In other words you need another field which is a part of VIQMEL table. i.e., PHASE.
Follow these values.
Value '1' for Status OSNO (Outstadning)
Value '2' for Status NOPO (Postponed)
Value '3' for Status NOPR (In Process)
Value '4' for Status NOCO (Completed)
Value '5' for Status DLFL (Deletion Flag)
So your syntax will go like this
IF I_VIQMEL-PHASE = '1' .....
Revert back if any further queries are there.
For syntax related queries, you may refer to this document User Exit 'QQMA0014', the applications
Best of Luck
Jogeswara Rao K

Credit Control Area User exit

What is user exit in credit Management?
What is the use of it?
How to configure it?
Plz let me know?
Bye

Hi,
user exits are used when u r unable to configure some requirements with standards..for credit management SAP provided number of user exits..mainly 2 will be used.
1.LVKMPTZZ
2.LVKMPTF1
these will be used as per the requirements of the clients..
regards..
yogi..

Batch checking by user exit

Hi all,
I've an requirement to check the valuation type when creating a batch with MSC1N.
I've tried using various user exits, especially EXIT_SAPLV01Z_004, ZXVBZU04.
It is not called in MSC1N. What's wrong is there?
(Another exit EXIT_SAPLV01Z_006 in MSC2N > ZXVBZU13 can be called with MSC2N.)
Thanks.

Hello,
I am facing the same issue I want to update a date 6 field while the user create a Bacth thurogh MSC1n.
I am using the EXIT_SAPLV01Z_013 to update the same.
But This Exit is not called as there is a condition which fails while this exit is called thru FM VB_CREATE_BATCH.
the field NO_CFC_CALLS is set to "X" in Include LCHRGF02.
CALL FUNCTION 'VB_CREATE_BATCH'
        EXPORTING
          ymcha                        = akt_mchx
          new_lgort                    = dfbatch-lgort
          bypass_lock                  = 'X'
          kzcla                        = ' '
          xkcfc                        = ' '
          no_check_of_qm_char          = 'X'
          no_change_document           = ' '
          check_external               = space
          check_customer               = space
          no_cfc_calls                 = 'X'.
Can you please help how do we resolve this issue i am using SAP 4.7.
Thanks
Solanki Ritesh

To check the user exit

Hi,
I want to debug the user exit EXIT_SAPLIPW1_001.Can anyone tell me how to do this?

Hi,
First check if the exit is implemented. There will be an include program inside this Function module. Check if the program is created and activated.
Then put a break-point in that include and execute the transaction. This will enable you to debug the exit.
thanks and regards,
Lakshmi.

Customer Credit Balance with user exit: LVKMPFZ1

Hi SD Gurus,
Is it possible to use exit:LVKMPFZ1 with USER 1 in transaction OVA8 to be able not to check credit limit when the customer has credit balance....If possible, please advise.
Thanks
Themba

Hi,
Good evening and greetings,
In the dunning procedure, FBMP transaction code click on the Dunning Levels and inside the dunning levels there is an option under the print parameter tab to print all items...Check that box and the system would include even the credit line items lying in the customer account and that can be printed out.
Please reward points if found useful
Thanking you
With kindest regards
Ramesh Padmanabhan

Credit control procedure/user exit

Hi,
Is it possible to set credit control block for the customer who has not configured credit limit in FD32?
I looked in VOFM and in the include LVKMPFZ1 but as far as I can see these programs are started only if there are records in FD32 (table KNKK).
many thanks
Piotrek

Hello Piotrek,
Unfortnately it is not possible in the standard. You need to mainatin the credit management master data in FD32 if you want to use the credit control block functionality.
Best regards,
Lela

User exit for credit check

Hi all,
Can anyone give the user exit name for credit check.

Hello,
Following exits are available:
LVKMPFZ1
LVKMPFZ2
LVKMPFZ3
Regards,
John.

Does Simple Credit Limit Check Include Checking for Open Orders

Hi all,
I have this issue here where I have configured the system to use simple credit limit check with error message. I did not use the standard/common automatic credit limit check since user insist on a pop-up warning and that the order could not be saved. But, I realized that it does not take open orders into account too although I have set the risk categories. Is it true and what solution is there for this issue then.
Thank you for all your help in inputs.
Regards,
Yvonne

Hi,
Please follow the below configuration settings for Simple credit check process.
Simple credit check: In simple credit check the system compares the credit exposure with payers credit limit. The
credit exposure results from the total of the net document value and the value of the open items.
We can set the following system responses at when the credit limit has been reached.
A u2013Warning message
B u2013 Error message
C u2013 Delivery block
Specify in VOV8  Credit limit [C]
Configuration settings:
Sales documents types u2013 Credit limit check: Transaction code: OVAK
Path:
 IMG
 Sales and Distribution
 Basic functions
 Credit management/Risk management
 Simple credit limit check
 Choose sales document type OR
 Specify value
[ ] = No credit limit check
[A] = Run simple credit limit check and warning message
 = Run simple credit limit check and error message
[C] = Run simple credit limit check and delivery block
 Save and Exit
Define credit control area: Transaction code: OB45
Credit control area is an organizational unit that specifies and checks the credit limit for customers. A credit control
area can include one or more company codes. It means we can assign one credit control area to number of company
codes.
NOTE: Within credit control area the credit limit must be specified in the same currency.
Path:
 IMG
 Enterprise structure
 Definition
 Financial accounting
 Define credit control area
 Go to new entries
(OR)
 Choose existing credit control area
 Select it and click on copy icon
 Rename it and click on details icon
Specify currency [INR]
257
Data for updating SD fields
Update [000012]: Open order value on time axis, delivery and billing document value. This field value controls
when the values are open sales orders, deliveries, billing documents are updated in LIS. We can specify the
following update groups for updating credit related statistics.
 Update group 000012:
Sales order: Increase open order value from delivery relevant schedule lines.
Delivery: Reduces open order value from delivery relevant schedule lines.
Increases open delivery value
Billing document: Reduces the open delivery value, increases open billing document value.
Financial accounting document: Reduces open billing document value
Increases open items.
 Update group 000015:
Delivery: Increases open delivery value.
Increases open billing document value.
Financial accounting document: Reduces open billing document value
Increases open items.
 Update group 000018:
Sales order: Increases open delivery value
Billing document: Reduces open delivery value.
Increases open billing document value.
Financial accounting document: Reduces open billing document value.
Increases open items.
Fiscal year variant [K4]: It indicates specific fiscal year variant for particular credit control area. The fiscal year
variant is essential when a credit control area covers multiple company codes whose fiscal years are different. Then
the values of the open orders are updated by posting period.
Specify risk category [001]: 001 = High risk
002 = Medium risk
003 = Low risk
This risk category entered in the related control area of the customeru2019s credit master record, which is automatically
created when a customer is created in a company code.
The credit master record is automatically maintained when at least one of the below fields is maintained for the
corresponding control area.
(A) Risk category
(B) Credit representative group
(C) Credit limit
Credit limit: The credit limit that we enter here in the specific credit control area of the customeru2019s credit master
record. This is automatically created when a customer is created in a company code (in XD01).
NOTE: This credit limit is not a total credit limit for the control area.
Representative group [001]: Define credit representative group in IMG.
 All company codes: If we want to tell to the system that, this credit control area is permitted for
postings in every company code we have defined.
 Save and Exit
NOTE: After this create Risk categories and Credit representative groups and come back to this step and assign
these values to our credit control area.
Risk category and Representative group defined and maintained by FI/CO consultants in IMG.
258
Assign company code to credit control area: Transaction code: OB38
Path:
 IMG
 Enterprise structure
 Assignment
 Financial accounting
 Assign company code to credit control area
 Choose our company code from position button
 Click on assign button on the application tool bar
 Select our credit control area from the list and assign it
 Save and Exit
 Go to FD32 and check whether system created customeru2019s credit master data automatically or not.
System creates customers credit master data automatically when we (FI/CO) people) configure credit control area in
IMG.
So as to perform simple credit check we have to specify customer master payers limit in the credit control area, and
create customer master in XD01 transaction code.
 Specify reconciliation account number (GL account number)
 Payment history record: Check payment history record control in payment transaction tab. It is the
control parameter to update the payment details that are made by customers and system will show the
payment details in the FD32.
 Specify the credit control area in credit control area field in billing document tab.
 Save and Exit
 Go to VA01 and raise the sales order
Check the system responses in each and every level of sales document processing and check whether the system
blocked the delivery document (due to the setting in VOV8 of OR in check credit limit field [C] = Blocked for
delivery).
 To release the delivery go to VKM4 and release the delivery document.

Simple Credit check _ User Exits

Similar Messages

Maybe you are looking for