SD Credit Management Settings

Hi,
We have the business scenario as follows.
1. Need to do the credit check in 2 levels i.e. sales order creation level & delivery order creation level
2. Open sales order SHOLD NOT consider for credit check. The sales order should get blocked if the total value of open deliveries + receivables exceeds the credit limit. I could not find any configuraton to satisfy this requirement.
I tried followings:
1. Static Check > Reaction = C > Status = Yes > Open orders = NO > Open Deliveries = NO: This does not meet business need as it does not check credit check at order creation stage althogh there are oustading deliveries and receivables available which exceed the credit limit
2. Dynamic Check > Reaction = C > Status = Yes: Again this setting also not ok as it consider open sales order also together with open deliveries & receivables.
I'm not sure whether there is a possibility for not taking open sales order values in the credit exposure.
Thanks in advance having your recommendation for the required configurations.
Br
Rambuk

Hi,
Go to T code OVAK maintain the credit group aganist the sales document type "01" for sales order, "02" for delivery & "03" for post goods issue accordingly
Then go to T code "OVAD" maintain delivery credit group against delivery type "02"
Then goto T code "OVA8" choose High Risk Sales Order and maintain Check againist Dynamic Reaction "D" and check the Status Block. For open Items Check against open items & choose "D" under reaction and check the Status/Block
For High Risk Delivery Check the Statuc Choose reaction "C" and check the Status Block also select Critical Fields Reaction "D" and check the status/Block and also check open orders and open deliveries
then goto T code FD32 and choose the Payer and Credit Control Area and set the Total amount, Individual limit & Currency also set the credit limit , credit horizon date and do not forget to maintain Risk Category and then save and then try to create the sales order.
I hope this will resolve your issue
You can try this and revert back
Thanks
Anil

Similar Messages

Issue log for credit management in SAP SD.

Dear Experts,
I am stuck at a situation where I have found that the credit exposure has exceeded it's credit limit being specified, under FD32 screen, in credit management scenario. How this happened?
Details of the issue :
1) Credit master has not been maintained.
2) If credit master has not been maintained then how the system was able to show the credit exposure of the respective customer?
3) If the credit management settings were pre configured correctly then, why the sysytem didn't blocked the sales order in initial stages itself?
Required guidance :
1) why the credit check was not performed while processing the sales order?
2) Why the sales order was not blocked when it exceeded the specified credit limit?
3) What needs to be done now?
Scenario:                     Credit limit : 1000 INR
                                    Credit exposure : 10000 INR
                                    Credit limit used : 999.99%
Kindly suggest & assist.
Thanks & regards,
M.S.Kumar.

Not sure but you can have a look at the following from SD side.
1) In your pricing procedure, SubTotal "A" should have been maintained for your basic price
2) In FD32, for that customer, the field "Credit account" should not have a different code. It can either be blank or the same customer code
3) In OVA7, for your item category, you should have activated for credit check
4) In OVFL, check what credit control area is assigned to your sales area
5) In XD02 for that customer code (Payer) check which credit control area is assigned
thanks
G. Lakshmipathi

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 - Maximum time overdue limit for open item

Dear all,
I've this scenario to configure for automatic credit control. A customer is billed on Jan 22nd '10 and now the account receiveable shows an open item. This customer is allowed 52 calendar days to make payment for this invoice, hence no credit block yet. As such, the customer can still make orders.
In my existing configuration, I've already enable "static" credit check on "open orders" and "open deliveries". The static check is to check against the customer's credit limit.
So, if I were to add in the earlier mentioned overdue open items check, is it sufficient to just maintain the field "Days oldestItem" with "52" within the automatic credit control screen?
Thanks.
Steven

Hi
The sytstem will shows oldest open items depending on the payment terms from the invoice date.
Once it crosses the days of payment then it will show in oldest open items
if you want to extend some more days for that then you need to maintain the days in "Days oldestitem" the automatic credit control area
Prerequisites for credit management to work in Sales and Distribution:
1.Assign credit control area to company code
2.Maintain the credit limit in FD32 with details of risk category and the credit limit value
3.Do the settings in OVA8 -automatic credit control area with combination of Credit control area/Risk category /credit group.
4.Assign the credit groups to the sales and delivery document types.
5.Maintain the Subtotal 'A' in the pricing procedure against which value the sytem should check the credit limit.
If you have any further clarifications on above let me know
Regards
Damu

Credit management and Terms of Payment

Hi
Can anybody throw some light on the role of Terms of Payment in .Credit Management.
Thanks in advance
Ravi

Dear sankar ravi,
Credit management
Purpose
Outstanding or uncollectible receivables can spoil the success of the company greatly. Credit Management enables you to minimize the credit risk yourself by specifying a specific credit limit for your customers. Thus you can take the financial pulse of a customer or group of customers, identify early warning signs, and enhance your credit-related decision-making. This is particularly useful if your customers are in financially unstable industries or companies, or if you conduct business with countries that are politically unstable or that employ a restrictive exchange rate policy.
Integration
If you are using the Accounts Receivable (FI-AR) component to manage your accounting and an external system for sales processing, Credit Management enables you to issue a credit limit for each customer. Every time you post an invoice (created in FI-AR), the system then checks whether the invoice amount exceeds the credit limit. Information functions such as the sales summary or early warning list help you to monitor the customers credit situation.
If you are using both the Accounts Receivable (FI-AR) component to manage your accounting and the Sales and Distribution (SD) component for sales processing, you can also use Credit Management to issue credit limits for your customers. You can make settings in Customizing to decide the scope of the check and at what stage in the process (for example, order entry, delivery or goods issue) a credit limit should take place. General information functions are also available for use with credit checks.
Features
If you are using both the SD and FI-AR components, Credit Management includes the following features:
Depending on your credit management needs, you can 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 (for example, order entry, delivery, goods issue) the system carries out these checks.
During order processing, the credit representative automatically receives information about a customers critical credit situation.
Critical credit situations can also be automatically communicated to credit management personnel through internal electronic mail.
Your credit representatives are in a position to review the credit situation of a customer quickly and accurately and, according to your credit policy, decide whether or not to extend credit.
You can also work with Credit Management in distributed systems; for example if you were using centralized Financial Accounting and decentralized SD on several sales computers.
Hope this helps you.
Do award points if you found them useful.
Regards,
Rakesh
P.S. you can send me a mail at my mail id [email protected] for any specific details

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.

How to determine the week for credit management?

Is there a transaction that will show the week for which credit is determined. For example, when running RVKRED88, it shows the week the order is processed under.

Hi Rocha,
In Credit management S066 and S067 information structures play a vital role in updating the credit values of a customer. This works in tandem with the update group present in the OVA8 settings in case of automatic credit check.
When an order is created S066 information structure and OEIKW field is updated which increases open order value. when order is delivered S067 information structure and OLIKW field is updated which increases open delivery value and decreses S066-OEIKW
When delivery is billed S067-OFAKW value (Open billing)gets increased and S067-OLIKW gets decreased.
Updation is through the information structures S066 and S067.
In the transaction code OMO1 select the information structure and double click it. You will be faced with parameters pop-up.
In this pop-up you have radio buttons day ,week and Month. _Based on the value you choose here you will get day or week or month for the Period split: info structure field present just besides horizon field of dynamic credit check in OVA8 Screen_If you choose week it will be till the end of the week and if you choose Month it will be end of the month. it is how system considers.
For example if we have created an order today i.e. 19/08/2011 and the Period split: info structure in the OVA8 has 1month.
System evaluates dynamic credit check as today's date + one month =19/09/2011which is =30th september,2011.
So while evaluating credit for the order, system will consider all the open orders whose delivery date is on or before 30th september + open deliveries + open bills + A/C receivables.
Edited by: mokirala tilak on Aug 19, 2011 11:00 AM
Edited by: mokirala tilak on Aug 19, 2011 11:23 AM

Exclusion of open sales order in credit management

Hi friends,
My requirement is that, all open sales orders should not be considered into credit management.
Is this possible in simple credit check or Automatic creidt check? Tell me the settings.
Regards
Rama

Dear Rama,
You can definitely Exclude Open Orders in Automatic Credti Management.
Use T-Code - OVA8
Select the required combination of Credit Control Area, Risk Cat. & Credit Group & double click.
Under Checks Tab There is Check Box for Open Orders.
In your case as you want to exclude Open Orders, just uncheck the box.
Hope this helps...
Give points if useful...
Thanks,
Jignesh Mehta

Service Interfaces for Credit Management using WS-RM

Hi,
We are implementing FSCM Credit Management on EHP 5 without using PI. For this we are WS-RM and have configured following service interfaces:
CreditCommitmentNotification_In
CreditCommitmentNotification_Out
CreditWorthinessQuery_In
CreditWorthinessQuery_Out
However, when we create sales order, credit check is not being perfomed. Do we need any other service interface for implementing Credit Management?

Hello,
I am using ECC 6 ehp 5 Which Enables you to Implement FSCM services via WS-RM (Web Service Reliable Messaging) instead of having to use Previously PI.
I require to implement the scenario is:
Credit Management (FSCM) and Integration with FICA without requiring PI.
I think I have covered all the technical configuration, but do not know how to test credit management and integration with FI-CA, appreciate if you can do to get a guide.
As indicated by the WSRM configuration guide, run the report SRT_ADMIN_CHECK and the result is:
Cross-checking system settings
bgRFC destination is Operational
bgRFC destination is registered supervisor
WSRM event handler is activated
Task is active watcher
Data collector for monitoring is not activated
ICF All nodes are active for SOAP Runtime
Ending cross-check of system settings
thank you for your help.
Regards.

Credit Management using WS-RM EhP5

I am using ECC 6 ehp 5 Which Enables you to Implement FSCM services via WS-RM (Web Service Reliable Messaging) instead of having to use Previously PI.
I require to implement the scenario is:
Credit Management (FSCM) and Integration with FICA without requiring PI.
I think I have covered all the technical configuration, but do not know how to test credit management and integration with FI-CA, appreciate if you can do to get a user guide.
As indicated by the WSRM configuration guide, run the report SRT_ADMIN_CHECK and the result is:
Cross-checking system settings
bgRFC destination is Operational
bgRFC destination is registered supervisor
WSRM event handler is activated
Task is active watcher
Data collector for monitoring is not activated
ICF All nodes are active for SOAP Runtime
Ending cross-check of system settings
thank you for your help.
Regards.
Yumarli
FI Consultant.

Hello..
you need to activate :
o (FIN_FSCM_CCD_3) business function
o Business function Enhancements to Reusable SOA Functions (FND_SOA_REUSE_1)
You can see also:
http://help.sap.com/saphelp_nw73/helpdata/en/47/ab7d3e49f84848e10000000a421138/frameset.htm
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d06b6392-cde7-2c10-8f8b-bdea5d781dd9?QuickLink=index&overridelayout=true
I hope help,
Yumarli.

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

Credit Management- KRML Output not generated for Sales Order ( v.v.u.)

<u>Credit Management - Credit control check at Sales order Level</u>
While saving the Sales order,which failed the Credit check ( As per Automatic Credit Check Settings), there is no output generated for output type KRML, for Partner Fn KB/KM. Normally,If credit check is NOK, then while saving the sales order, an internal mail is sent to the SAP office inbox of the Credit representative ( KB/KM). There is option for an external send also. The problem faced by us is that, the mail is not going in SAP Office inbox in quality server , it is going in developement server.We checked in table NAST that the Output for KRML (o/p type) is not generated. Kindly suggest what could be the reason.
Regards
Sunil Kumar

Dear Mr. Gauravjit,
Thank you for your valuable reply.
At the Extra-Output-Header-edit-goto-det analysis ,system give message as KRML o/p is not generated since Requirement 009 is not being fulfilled. But we checked the VBUK-CMGST = B is satisfied. Still the o/p not generated!
Also , in VV11 we maintained the Cond Records. Still the o/p is not coming.
The output is coming in Devlopment , but in Quality the output is not coming.
Can anybody please help !
P.S. I am colleague of Mr. Sunil Kumar, and reply on behalf of him.
With Best Regards,
Kaustuv

Credit Management System - Update of SD Documents after CMS start

Hi,
we are starting CMS functionality in our SD module. CMS (Credit Management System) works remotely by an XI connection. When we switch to use CMS in production system, we have to transfer all opened orders (not yet invoiced) to CMS system.
How can we achieve it? Can program RFDKLI20 (t-code F.28) be used for this purpose? Does it require any settings to point out the CMS connection?
Thank you
/BR

Hi Wojciech
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.
Reward if useful to u

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.

F.28 transaction for credit management

Hi
Any body can explain detail information on below
In F.28 transaction what is the use of
1.FI data only and 2.Recreate FI and SD data
Please explain details what will happen after executing this above.
Regards

hi
If you check the Indicator: FI data only
    The result is that only financial accounting data is reconstructed.
    Sales documents (orders, supplies, invoices) are not taken into account.
IF you check Indicator:Recreate Fi and SD Data Only?
It will recreate both SD and FI data if you have any changes in SD and FI settings in credit management
     Setting this indicator has the effect that only sales documents (orders,
     deliveries, billing documents) are recreated.
Use
     This indicator is only useful if you have made changes in Credit
     Management that only necessitate a recreation of the FI & SD data. In this
     case you should set the indicator for performance reasons.
regards

SD Credit Management Settings

Similar Messages

Maybe you are looking for