Credit Management: Any setting to warn or avoid Project creation in PS

Is there any standard credit management setting that would warn or doesn't allow to save the creation of the project in PS , just like warning or stop from saving the service notification by credit management

Not sure why you're asking a PS question in the SD module...
To my (very limited) knowledge, there is nothing like credit management in PS. And how do you envision this would work? The project doesn't have any value per se, so what would you check against? Also Partner data in PS is optional, unlike Sold-to in SD, so there is hardly any link.
There are a bunch of user exits / BADIs available in PS, which could be used for additional data validation.

Similar Messages

Credit managment reports

Hi
Can anyone please tell me what is the purpose and functionalities of programs RVKRED77 , RVKRED06, RVKRED08, RFDKLI10 ,RFDKLI20 .... and if possible mention on example
Regards
ALI

hi,
please follow this :
Program        Function
RFDKLI10 Customers with Missing Credit Data
Checks whether the data regarding credit limits is complete and issues relevant error lists. These enable you to maintain the relevant definitions either manually or with batch input.
RFDKLI20     Reset Credit Limit for Customers
Resets the credit limit information in the control areas.
RFDKLI30    Credit Limit Overview
Lists the central and control area data for each customer.
RFDKLI40    Credit Overview
Provides a comprehensive overview of the customeru2019s credit situation.
RFDKLI41    Credit Master Sheet
Displays and prints the customer master data for an individual account that is needed for credit management.
RFDKLI42    Early Warning List
Displays and prints customers in Credit Management who have been listed by the credit check as critical.
RFDKLI50    Credit Limit Data Mass Change
Changes all the credit management master data together.
RFDKLIAB    Display Changes to Credit Management
Displays the changes to credit management master data for all accounts.
RVKRED06    Check Blocked Credit Documents
Checks all the documents blocked for credit reasons. The report is started in the background and should run after the incoming payments programs.
RVKRED77    Reorganize SD Credit Data
Reorganizes open credit, delivery and billing values. It can be used in the event of an update error, for example.
RVKRED08   Checking sales documents which reach the credit horizon
Rechecks all sales documents that fall within the credit limit horizon of the dynamic credit limit check. The report is run at regular intervals and should be run at the start of each period. The system uses the current date and the period split for the open order values to propose the u2018next credit check dateu2019.
RVKRED09   Check Credit Documentsin Background
Checks released documents whose validity period of the release has been exceeded (number of days).
RVKRED88   Simulating Reorganization of SD Credit Data
goto SE38 and execute.
hope this clears your issue.
COURTESY : SAP LIABRARY.
balajia

Credit Managment : Profile tab is not visible in BP

Hi All ,
I am working on FSCM credit managment project.
For FSCM credit managment :
I have activated the Badi : activation of SAP credit managment (Interface Set Active and FI_AR_Upadte mode)
1)Set Active
E_ACTIVE_FLAG = 'X' .
E_ERP2005 = 'X'
2)FI_AR_Upadte mode
E_DIRECT_UPDATE = 'X'.
But when I am selecting the Bussiness partner under (SAP credit managment role ).Profile tab is not visible .
Please help me out .
Regards
Rahul

Hi,
Pls check note 956054 and see if you have set up the business partner the correct way. This is the basis.
Rgds,
Richard

Credit Management- i want to allocate inventory but block the delivery

Dear SAP Gurus,
i am having a problem with Credit Mgt.
when order get blocked for credit check that time i want inventory i mean material should allocate to that customer but the delivery should be blocked.
whats are the customisation needed for such scenario
Please help me to solve this problem .
Thanks in advance
Regards
Vishal

Vishal,
Why dont you try checking credit limit at delivery or PGI level ?
Standard Process in SAP is providing check at three levels
1. Order level
2. Delivery Level
3. PGI level.
Check OVA8 settings for credit management at Delivery and PGI level
So after creation of delivery the stock or inventory be allocated to the user and then u can have delivery block.
Thanks,
Raja

Credit Managament: avoid credit block for down payment invoices

1) Downpayment - when an order is blocked, can we create a billing
document of the downpayment request created in slaes order. Logically
the customer wants to pay for this downpayment immediately and process
the order
Notes: If credit management is activated at sales order level and In
Milestone Billing scenario or Project Sales order scenario, at Sales
order level we have a Downpayment (Z0000 - Downpayment) Milestone
usage and Other Milestone invoice Usages.
The business requirement is Customer need to pay the downpayment
invoice before executing the Sales order.
In SAP when the Sales order is blocked for Credit Management, system is
not able to create the Downpayment invoice also. to creat the invoice
we have to release the order first. However we dont want to release the
order but want to receivce the downpayment and then may be we can
manually release the order and process. The reason is suppose we have
an automatic release to production or PR or creation of service order,
we would like to process them only after the downapayment, now for
creating the wownpayment invoice for receiving the downpayment, we have
to release the order which shall further process the order
automatically. Please suggest a solution for the same to avoid the
credit block for the Downpayment invoices.

I think this can be enabled easily.
For the combination of Credit Control Area, Credit Group and Risk Category, you should have enabled the Dynamic/Static credit check, you can configure it such a way that it only gives you a warning message and doesnot block your sales order. This should solve ur problem

Credit Management-Sales value updated in FD32 even though credit set up is not active

Dear Team,
We are facing an issue where, for a sample order - sales value got updated as open sales order value against a customer in FD33.
Credit set up is not active for the sales order type (OVAK) or the delivery type (OVAD). Since this has occurred in 2003, we have no clue what exactly has happened. We cannot locate any change logs in the configuration level.
1) What is the possibility for credit management to be active for a document type, which was not meant for credit set up?
2) How to remove the open order/ delivery value for the customer?
Thanks and regards.
Sivarajesh

Credit set up is not active for the sales order type (OVAK) or the delivery type (OVAD).
the above two settings are credit checks at what level( example order level or delivery etc) you what to block the customer if the customer payer exceeds the credit limit.
Where as if the credit active field is active in VOV7 in corresponding item category, system update the respective document values in to credit management (FD32/33) in your example open order value.
Even though OVAK, OVAD settings are not done still system update the document values in to FD33 subject to credit active field is active in t code VOV7 .
Please check in your item category whether credit active field active.
thanks,
Srinu.

Setting approval level for credit management in SD

Dear Gurus,
I have a case like this:
My client would like to use credit management in SD. They have few approval levels for for credit limit release.
Exp: With SD has amount under from 1000$, Mr. A has the right to approve and release it
        With SD has amount bigger than 1000$, Mr. A have to release it and then Mr. B check again afterwards Mr. B can reject and release it up to his decision.
As I see in SAP, maybe there is only one level for check and after release the SO doesn't need other approve anymore. But I am still concerning about how to find or config to satisfy this requirement.
Thank for nice support!

In our case we have maintained a view named as "ZVW_OAR_WF_CTRL" which is created by our ABAPer.
The fields in this view are
   FIELD NAME                              DATA ELEMENT         TYPE         LENGTH
1) MANDT                                          MANDT                         CLNT             3
2)PROCESS                                      ZDE_WF_PROCESS      CHAR           2
3)KKBER                                           ZDE_KKBER                  CHAR          4
4)GRUPP_F                                       ZDE_GRUPP_CM_FROM CHAR         4
5)GRUPP_T                                       ZDE_GRUPP_CM_TO      CHAR         4
6)LEVELS                                         ZDE_WF_LEVEL              CHAR         5
7)VALUE_F                                       ZDE_NETWR_AK_FROM   CURR       15
8)VALUE_T                                       ZDE_NETWR_AK_TO         CURR       15
9)APPR                                            ZDE_PLANS                       NUMC      8
10)APPR_AD1                                  ZDE_PLANS1                    NUMC       8
11)APPR_AD2                                  ZDE_PLANS1                   NUMC        8
12)BOX_AC_APPR                           ZDE_AD_SMTPADR_BOX CHAR       241
13)BOX_AC_REJC                            ZDE_AD_SMTPADR_REJ   CHAR      241
14)NEXT_LEVEL                              ZDE_WF_LEVEL_NXT         CHAR       5
You can ask your ABAPer such that your view contains the above mentioned fields and in the the approvers you have to enter the "Pernr id" s of approver s which can be taken from HR people.

Credit Management Process based on Terms of Payment.

Hi All,
My Client wants to use SAP Credit Managment Process. The SAP is currently being used but without Credit Management. As per my initial discussion I have enclosed the requirments below. Your Kind Help will be highly appreciated.
1.     The Process has to be implemented in a 2 Step Process.
2.     The Initial Requirement is based on Terms of Payment. If the Number of Days is Overdue for the Invoice for a particular Customer, the system should issue a warning message (in the Form of Mail or any other way) which can be shown as evidence to the Customer for collection of Payment so that further Sales Transactions can take place.
(Is there the standard Process in Credit Management based on Terms of Payment)
3.     In the next step Value Base Credit Check has to be implemented. The Value will be set for a particular Customer in Credit Master. When the Sales Order is raised and if the Credit Limit is exceeded the System should issue the warning message. Based on the Warning Message Issued an email should triggered to the particular person in Finance that the Credit Limit for a particular person has been exceeded and Credit Limit needs to be increased.
Thanks & Regards,
Sam.

Dear Mr F Farooq,
1. The Process has to be implemented in a 2 Step Process.
Do the following configurations for credit management :
Refer the following link.
http://wiki.sdn.sap.com/wiki/display/ERPLO/CreditManagementConfigaration
2. The Initial Requirement is based on Terms of Payment. If the Number of Days is Overdue for the Invoice for a particular Customer, the system should issue a warning message (in the Form of Mail or any other way) which can be shown as evidence to the Customer for collection of Payment so that further Sales Transactions can take place.
(Is there the standard Process in Credit Management based on Terms of Payment)
Now for this requirement, since different billing documents for the same customer can have different payment terms (whcih means different billing will be due on different date) , please make the following changes in OVA8
Check for 'oldest open item'
Now follow my reply in the below thread.
Sales order to be blocked based on customer payment terms and credit limit
You can use WORKFLOW to trigger mail when such a message is triggered in the sales order , due to credit check.
Ask your ABAP-er for details on workflow.
3. In the next step Value Base Credit Check has to be implemented. The Value will be set for a particular Customer in Credit Master. When the Sales Order is raised and if the Credit Limit is exceeded the System should issue the warning message. Based on the Warning Message Issued an email should triggered to the particular person in Finance that the Credit Limit for a particular person has been exceeded and Credit Limit needs to be increased.
Just configure according to the thread given for 1st POINT.
CHECK FOR DYNAMIC and set reaction as 'C' and check STATUS /BLOCK.
Maintain the credit limit in the FD32.
Now when the sales order value exceeds the credit limit , a message will be triggered.
Use the concept of WORKFLOW to create mail based on this message .
When the user gets mail, he can maintain the new credit limit in FD32 and release the document for delivery/billing in VKM3.
Revert back if there is any issues.
Thanks & Regards,
Hegal K Charles
Edited by: Hegal . K . Charles on Aug 7, 2011 1:19 AM

Maximum open item % and no of days open item in credit management

Hi
Can any body explain how works " Maximum open item % and no of days open item " after checked in ova8 with examples.in credit management.
regards

hello, friend.
maximum open items is helpful for you if the customer is still within credit limit but has overdue open items.
let's say your customer has a credit limit of $100,000.00. and you set in OVA8 for maximum of 20% or $20,000.00.
now let's say your customer's total exposure is $43,699.00, which is still within credit limit. however, out of this, $21,245.00 is over the credit terms of 14 days. now if you set "1" in days in OVA8, 1 day after overdue the system will either block the newly processed sales order or issue a warning, depending on OVA8 settings.
regards.

Effect of Payment Terms in Credit Management

Can Any One tell me the effect of Payment terms in Credit management. How the effect will be for different Payment terms .and i want to know the implication of it.
Regards
Madhav

hello, friend.
a simple effect of payment terms on credit management is that when a customer open receivables remains uncleared beyond terms set, then credit management will allow the system to automatically either block any sales transactions or issue a warning message when these transactions are processed.
this feature is complementary to other control parameters such as credit limit (value), document value, open items, longest open items, etc.
regards.

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

What is credit management how should we tell

hi
gurus my question is what is credit management.
2) If one customer exceeds his credit limit the sales order is blocked in the enduser system. WHO will release that order. Whether enduser called his higher authority by telephone or mailed or it is automatically knows by the superior means who is working in the managerial level working in n.s.o.
thanks in advance

hi
The customers credit limit is assigned to the customer by going to the Logistics overview screen, Accounting, Financial accounting, Accounts receivable, Master records, Credit management, Change.
A credit control area is an organizational unit that is comprised of one or more company codes.
Create a credit control area and assign it to a company code in the Enterprise structure under financial accounting.
A customers risk category is a grouping category that controls the credit checks when automatic credit control takes place.
In SD credit check can occur in only three places: sales order, delivery and goods issue.
The system can use a simple credit check, static credit check or a dynamic credit check.
The simple credit check is set at the document type level e.g., sales order, delivery etc.
Simple Credit Check
Assign credit limit check to the sales doc type:
A warning message
B Error message
C Delivery block
D Automatic credit control
SAP enables static and dynamic credit checks so that a sales order for a good customer with a low risk credit rating is created and a sales order for a high risk customer with a high risk rating for the same doc type is blocked.
Automatic credit control divides the sales doc types, delivery doc types, and goods issue into specific credit groups.
An outcome procedure is defined using the credit group, the customers risk category along with the credit control area.
Risk categories are defined in the FI module.
Create the different credit groups e.g., for sales order, delivery, goods issue.
Assign the credit groups to the sales and delivery doc types.
Now define the settings for automatic credit control -> combination of credit control area, customers risk category, and credit group.
All that remains is the assignment of the risk category to the customer master record. This occurs in Finance by going to the Logistics overview screen -> Accounting, Financial Accounting, Accounts receivable, Master records, Credit management, Change or FD32.
The static credit check is a check comparing the credit limit assigned to the customer to the total value of open sales orders, plus the total value of open deliveries not yet invoiced, plus the total value of open billing documents not yet passed on to accounting, plus the total value of billing documents that have been passed on to accounting, but which have not been paid by the customer.
The dynamic credit check is a check comparing the credit limit assigned to the customer to the total value of open sales orders not yet delivered, plus the total value of open deliveries not yet invoiced, plus the total value of open billing documents not yet passed on to accounting, plus the total value of billing documents that have been passed on to accounting, but which have not been paid by the customer. The dynamic credit check has an attached time period that states that the system is not to include sales orders in the total of outstanding items created after the specified time period.
The credit relevant data is updated into an information structure, where it is accessed and updated. Thus each automatic credit control must be assigned an update group. The system allows for no update, and update group 000012, 000015 and 000018. However, update group 000012 is thorough and used in most businesses.
To view the customers credit master sheet, proceed from the logistics screen and go to accounting, financial accounting, accounts receivable, environment, credit management, check, credit master sheet [F.35].
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.
Reward if USeful
Thanx & Regrads.
Naren..

Credit Management not activated in Delivery Order

Hi,
I've made relevant configurations in SPRO such that during the creation of sales order, credit management is activated. A warning message popup to warn user of the credit exceeded.
However, during delivery order creation, such warning message does not get popup.
I'm using the simple credit checks. In spro->sales & distribution ->basic functions->credit management->assign sales docs & delivery docs-> credit limit check for delivery types, i've set the relevant delivery type to have credit group 02 (Delivery) & 03 (PGI). Under the item cat for delivery order, i've also checked the active credit checkbox.
Any config i've missed out?
Thanks
Regards,
HweeLing

Hi,
According to your reply, I can only set credit checks popup message at only 1 place - Either sales order OR delivery order?
Does it mean that if i have the check in sales order, I cannot have the same popup message in delivery order?
Currently, i have the popup message in sales order.
I do not want to block delivery order. I only want a warning message thats all.
Thanks

Credit management....sales area data

hi gurus,,
I have some doubts in Credit Management>
1. In my development Server....Customer Master data > Sales Area Data > Billing Tab Page>CREDIT CONTROL AREA...is not reflecting.
using version 4.7... why is was not reflecting... any configaration settings is required??.
Anybody having configuration material of CREDIT MANAGEMENT and FREE GOODS DETERMINATION..
MAIL ID::: [email protected]

Hi ravi,
Notes on Credit mangement
SAP SD 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.
SM30 - Table/View
V_TVTW - Define Distribution Channel
V_TVTA_KKB - Assign sales area to credit control area
V_T014 - FI - Define Credit Control Area
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
Check Credit
A - Credit limit check and warning message
B - Credit limit check and error message (no sales order can be created)
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)
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
Credit group
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
whether the automatic credit check occurs at the time of delivery creation and/or goods issue
OVA7 - Define credit limit check by item category
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).
SAP default credit groups
01 - credit group for sales order
02 - credit group for delivery
03 - credit group for goods issue
OVA8 - Automatic credit control - Double click on the line items
You can have the followings credit limit check :-
Static
Depends on the customer total value of open orders, deliveries, billing documents and open items.
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.
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.
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.
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)
Free goods determination
Free Goods Determination in Sales Order
Free goods has the following limitations:
- Free goods can only be supported on a 1:1 ratio. This means that an order item can lead to a free goods item. Agreements in the following form are not supported: With material 1, material 2 and material 3 are free of charge or If material 1 and material 2 are ordered at the same time, then material 3 is free of charge.
- Free goods are not supported in combinations with material structures (for example, product selection, BOM, variants with BOM explosion).
- Free goods are only supported for sales orders with document category C (for example, not quotations).
- Free goods are not supported for deliveries without reference to a sales order.
- Free goods cannot be used in make-to-order production, third-party order processing and scheduling agreements.
- If you defined a free goods for variants in a generic article (only SAP Retail), you can only process the variants in the purchase order and goods receipt individually (as single articles). In other words, you cannot process them using the generic article matrix.
4.6x
Not all Sales Order can be used for free goods determination. You have to check the SD document category if it does not work. Only category 'C' are supported. Check transaction VOV8.
Assume that you want to configure an inclusive FREE goods routine. Customers must order a minumum quantity of 5 before any free goods can be assign. For every quantity of 3, the customer will be given 1 free goods.
WC07 - Maintain Number Range Intervals
e.g.
No   From number       To number
01    0000010000         0000099999
IMG -> Sales and Distribution -> Basic Functions -> Free Goods ->
Maintain Access Sequences
New Entries
Acsq
NA00
Save
Maintain Condition Types
New Entries
Ctyp   Name             AcSq
FREE Free Goods    NA00
Save
Maintain Pricing Procedures
Procedures
New Entries
Procedure   Description
FREE           Free Goods
Select Procedure FREE then click Control data
Step   Cntr   Ctyp
10       10      FREE
V/N6 - Activate Free Goods Determination
Assign Order Type OR with Document Procedure A with Procedure FREE
VBN1 - Create free goods determination
e.g. FREE inclusive
Material Min qty   From   are free good   Calc Rule   Free Goods
                       5           3                1                      1                1
In this example, if you create a Sales Order for a quantity of 10, SAP will prompt you 7 as the customer order qty and 3 will be free. Customer only pay for the 7 quantity.
Reward points if it helpful

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

Credit Management: Any setting to warn or avoid Project creation in PS

Similar Messages

Maybe you are looking for