Credit Management Error

Hello,
When entering customer number in FD32 it shows "Central Data not mentained for the Customer"
Please help to solve this error.

hello, friend.
when you create a customer using a Sold-to account group, a credit master is automatically created. however, you must maintain the credit master using FD32.
when you execute FD32 for the customer credit account for the first time, you must enter the credit account, the credit control area, and check at least Central data and Status. press 'Enter'. you will be brought to these 2 screens. to create these screens just press 'Enter' until prompted to save. after this you will not get the message anymore.
hope this helped.
regards.

Similar Messages

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

Error on Loading Credit Management Setups using iSetup in target instance

Hi All,
I am trying to migrate Oracle credit management functional setups(Scoring model, Checklist, Automation rules) from source instance to target instance. I am trying to achieve this by the usage of iSetup. Once the Load is done, I am getting the following error and the setups are not migrated. This error comes up only for Credit management Setups. Not for other functionalities. Please help me out on this.
+---------------------------------------------------------------------------+
Application Implementation: Version : 12.0.0
Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
AZR12LOADER module: iSetup R12 Loader
+---------------------------------------------------------------------------+
Current system time is 09-OCT-2013 03:15:18
+---------------------------------------------------------------------------+
Concurrent Request Parameters
RELOAD_REQUEST_ID=
DBC_FILE_NAME=DEVF.dbc
SNAPSHOT_REQUEST_TYPE=E
SNAPSHOT_NAME=RAC Credit Management Test
RELOAD_METHOD=
REQUEST_TYPE=L
IS_REMOTE=Y
JOB_NAME=RAC Credit Management Test1
USER_NAME=DEPPS
Downloading the extract from central instance
Successfully copied the Extract
Time taken to download Extract and write as zip file = 0 seconds
Validating Primary Extract...
Parsing driver.xml
Time taken to parse the Driver file and construct setup objects:6 milliseconds
Sorting Apis based on their dependency...
Time taken to sort the Apis=12 milliseconds
Printing sorted Apis
Load Sequence 1
1)AR_CMGT_Scores
Oct 9, 2013 3:15:48 AM oracle.adf.share.config.ADFConfigFactory findOrCreateADFConfig
INFO: oracle.adf.share.config.ADFConfigFactory No META-INF/adf-config.xml found
Name: AR_CMGT_Scores
Type: BC4J
Path: oracle.apps.ar.ispeed.creditmgt.scores.server.ScoresAM
Time Taken(seconds): 2.0
Importing rows from xml file, and validating rows ......
Message not found. Application: AZ, Message Name: AZW_FWK_USER_ROW_EXCEPTION. Tokens: VONAME = Scores; KEY = Score Model Id = 'null'
; EXCEPTION = oracle.jbo.RowCreateException: JBO-25017: Error while creating a new entity row for ScoresEO.
java.lang.Integer incompatible with java.lang.Long
Message not found. Application: AZ, Message Name: AZW_FWK_USER_ROW_EXCEPTION. Tokens: VONAME = Scores; KEY = Score Model Id = 'null'
; EXCEPTION = oracle.jbo.RowCreateException: JBO-25017: Error while creating a new entity row for ScoresEO.
java.lang.Integer incompatible with java.lang.Long
Message not found. Application: AZ, Message Name: AZW_FWK_USER_ROW_EXCEPTION. Tokens: VONAME = Scores; KEY = Score Model Id = 'null'
; EXCEPTION = oracle.jbo.RowCreateException: JBO-25017: Error while creating a new entity row for ScoresEO.
java.lang.Integer incompatible with java.lang.Long
Message not found. Application: AZ, Message Name: AZW_FWK_USER_ROW_EXCEPTION. Tokens: VONAME = Scores; KEY = Score Model Id = 'null'
; EXCEPTION = oracle.jbo.RowCreateException: JBO-25017: Error while creating a new entity row for ScoresEO.
java.lang.Integer incompatible with java.lang.Long
Message not found. Application: AZ, Message Name: AZW_FWK_USER_ROW_EXCEPTION. Tokens: VONAME = Scores; KEY = Score Model Id = 'null'
; EXCEPTION = oracle.jbo.RowCreateException: JBO-25017: Error while creating a new entity row for ScoresEO.
java.lang.Integer incompatible with java.lang.Long
Message not found. Application: AZ, Message Name: AZW_FWK_USER_ROW_EXCEPTION. Tokens: VONAME = Scores; KEY = Score Model Id = 'null'
; EXCEPTION = oracle.jbo.RowCreateException: JBO-25017: Error while creating a new entity row for ScoresEO.
java.lang.Integer incompatible with java.lang.Long
Message not found. Application: AZ, Message Name: AZW_FWK_USER_ROW_EXCEPTION. Tokens: VONAME = Scores; KEY = Score Model Id = 'null'
; EXCEPTION = oracle.jbo.RowCreateException: JBO-25017: Error while creating a new entity row for ScoresEO.
java.lang.Integer incompatible with java.lang.Long
Message not found. Application: AZ, Message Name: AZW_FWK_USER_ROW_EXCEPTION. Tokens: VONAME = Scores; KEY = Score Model Id = 'null'
; EXCEPTION = Updates are not supported by this API.
74 rows processed, now posting changes to the database ......
Transaction committed.
Processed API:AR_CMGT_Scores
Status: WARNING
Concurrent program completed.
+---------------------------------------------------------------------------+
Start of log messages from FND_FILE
+---------------------------------------------------------------------------+
+---------------------------------------------------------------------------+
End of log messages from FND_FILE
+---------------------------------------------------------------------------+
+---------------------------------------------------------------------------+
Executing request completion options...
Finished executing request completion options.
+---------------------------------------------------------------------------+
Concurrent request completed
Current system time is 09-OCT-2013 03:15:50
+---------------------------------------------------------------------------+

Vivek,
Thanks for the update.
Regards,
Hussein

Workflow error in Oracle Credit management

Hi,
I got the following error in the credit management workflow(ARCMGTAP).
The following details I got from wfstatus.sql file.
Can you please any one help on this.
Enter value for 1: ARCMGTAP
Enter value for 2: 1177582
**** WorkFlow Item
Item Type Item Key Begin Date End Date Activity
ARCMGTAP 1177582 10-SEP-09 08:02:12 AR_CMGT_APPLICATION_PROCESS
**** Activity Statuses
Begin Date Activity Status Result User
10-SEP-09 08:02:12 ROOT/Credit Management Application Process ACTIVE #NULL
10-SEP-09 08:04:25 Credit Management Application Process/Start COMPLETE #NULL
10-SEP-09 08:04:25 Credit Management Application Process/Create COMPLETE
Party Profile
10-SEP-09 08:04:26 Credit Management Application Process/Generat COMPLETE #FORCE
e Credit Classification
15-SEP-09 13:15:37 Credit Management Application Process/Generat ERROR #EXCEPTION
e Credit Classification
**** Errored Activities
Activity Result Error Name
Error Message
Error Stack
Generate Credit Classification #EXCEPTION -29280
ORA-29280: invalid directory path
AR_CMGT_WF_ENGINE.GENERATE_CREDIT_CLASSIFICATION(ARCMGTAP, 1177582, ORA-29280: invalid directory pat
Wf_Engine_Util.Function_Call(ar_cmgt_wf_engine.generate_credit_classification, ARCMGTAP, 1177582, 16
*** Error Process Activity Statuses
Begin Date Activity Status Result User
10-SEP-09 08:04:26 ROOT/Default Error Process ACTIVE #NULL
10-SEP-09 08:04:26 Default Error Process/Start COMPLETE #NULL
10-SEP-09 08:04:26 Default Error Process/Initialize Error COMPLETE COMPLETE
10-SEP-09 08:04:26 Default Error Process/Notify Administrator NOTIFIED SYSADMIN
15-SEP-09 13:15:37 ROOT/Default Error Process ACTIVE #NULL
15-SEP-09 13:15:37 Default Error Process/Start COMPLETE #NULL
15-SEP-09 13:15:37 Default Error Process/Initialize Error COMPLETE COMPLETE
15-SEP-09 13:15:37 Default Error Process/Notify Administrator NOTIFIED SYSADMIN
8 rows selected.
**** Error Process Errored Activities
Thanks in advance.
Regards,
Raghavendra K

Hi,
In the AR_TOP there is no file with this name .
Please let me know is there any other top related to CreditManagement.
I used this command in unix server to find this file.But there is no results.
find . -name ARCMGTAP.wft -exec ls {} \;
Thanks,
Raghav

Getting Msg: Error when calling Credit Management: Technical Error

Hi All,
While creation of sales order in ECC, i am getting a message "Error when calling Credit Management: Technical Error"
Can you help me in this case
Regards,
Satish

Satish,
Just so you know, this BADI "links" SD module to FSCM credit management. If you use the right code in this BADI, it copies over credit information on to the sales order such as Credit Account, Risk Class and Credit representative code. (Later this risk class, order's credit control area and credit group is used to look up the appropriate line in OVA8 settings)
Now you could be getting this error for any of the issues:
1. If the business partner is not created for the customer for which you're trying create a sales order (The credit account (sales order header) should have a relevant BP already) Check if the BP is correctly created.
2. Next if the credit data has been maintained for the BP in credit management.
3. XI/PI connectivity issues etc
Check if all this is maintained and you should be good. Cheers

Error:pricing procedure is getting changed in credit management

Hi,
Sales order is created.delivery is created
In invoice its picking value from credit management.
here pricing procedure is changing.
What is issue for changing pricing during invoice and taking credit managment.
regards
SAP SD User

In invoice its picking value from credit management.
here pricing procedure is changing.
What is issue for changing pricing during invoice and taking credit managment.
Can you please explain your requirement with some more examples?I did not understand the the above.
thanks,
Srinu.

Credit management

We have open sale order for a customer after which the credit management was activated. In FD 32 the credit limit was set.
The risk category used is 006.
We have used static check. We have ticked on open orders and open items.
We want the system to prompt at the sale order level if we are trying to change the quantity.
After maintaining the master when we create order and if it exceeds the limit we are getting the error message that credit limit exceed by -
value.
For orders that are raised before fd32, we are not getting the error message.
Could anyone please guide

Hi Pooja
In OVA8 , for static check change the Reaction box to error and then check , but generally the open orders, open deliveries work for dynamic credit check and not for static credit check
Regards
Srinath

Credit Management requirement for cash business

Hi Gurus,
Actually my client business is a cash business, there is no credit concept for the customers.
My requirement is when i create a sales order, system should check the credit balance of the customer(Business receives the payment through cheque and entry is made in f.28 transaction) and should compare with the current document value and if it exceeds, then system should through the error.
And if any open sale orders exists for this customer, system should even consider those values while credit check is happening.
And the exceptions for this requirement is
1.Credit check option should be there only for specific case of customers i,e based on account group of customers.
2.There are very few customers(around 5) where they give credit.
Pls guide me, early resposes woould be highly appreaciable.
Thanks in advance
Regards
Mahendar.

hello, friend.
you can consider using the payment guarantee scenario in credit management. the customer advance payment could be treated sort of as a financial document or payment card.
as for the selective application of credit controls based on customer group, i believe you do this be configuring risk categories and assigning them to the appropriate credit account master data.
regards.
Edited by: jonathan y on Apr 24, 2009 12:57 PM

Credit management and credit exposure

Hi experts,
Pls anybody clarify my doubt in Credit management.
I activated the credit control areas update as 000015(Open delivery and billing document value).And activated dynamic credit management "Automatic credit control".Now i explain with some example how it working. Fixed credit limit for customer A Rs.30,000/-, Receivables amount 22,000/-. Now if create a sales order for value >8000 i m not getting the credit lock waring messages.
(I.e) i am creating one sales Order for value Rs.9,000/-.(So credit limit crossed and not getting error msg or waring messages)
After that creating another sales order for same customer i am getting Warning msg like"Credit limit crossed_____amount".
So finally, CCR Rs.30,000/, Recei Rs.22,000/- but i can able to make even Sales Order value for Rs One lakh. I want here to block sales order should not be create.
Thanks in advance.
SR

When a sales order is created , only the confirmed quantity is taken for pending sales value even if sale order qty is more
Check OVA8 setting , open deliveries and open orders should be selected
You can set reaction status as warning or error.
Pricing procedure - Subtotal should be A . This will update structure s066
The above condition will work only for order creation . For sales order ammendment you have do the same setting for credit group 02.
If Dynamic credit check works with credit Horizon date . It is better to have static credit check.
Check MC30 after creating sales order whether structure s066 updated for the order.
check and confirm
Senthils

Down Payment cleared against invoice but in credit management not updated

Dear all,
A down payment of 185,000 was cleared against an invoice last year. But that value is still showing in the credit management Special liabilities. The orders are being blocked because of this. what should i do?
Regards,
shahzad khero

Sir,
Clearing has been done in FI via F-39. The document is cleared and is showing in FBL5n cleared data. I think this is an update error or some thing.
Regards,
Shahzad

Unallocated sales order is out of Credit management

Dear gurus
On credit management, if inventory is NOT allocated to sales order
(Ex. No inventory at storage location),
warning or error message show up even if the credit amount is
exceeded the limitation.
After created sales order without inventory allocation, then inventory
is allocated later, and error message show up
as delivery, because the credit amount is exceeded the limiation.
What is the concept of SAP behind this logic?
Why SAP doesn't count unallocated sales order to credit management?
Y.Kaneko

if i understand you correctly, you need to know why an order does not have a allocated stock if it is credit blocked, & why does the order goes back to credit hold when it is released & availbility check is carried out.
from a credit management view, allocation of stock to a blocked order is not followed in business, lets take a logic example if you have 100 qty in stock & u have order for 80 qty from a customer on normal scenario you will have this order confirmed, but since he is on credit block, the confirmation for him will not happen, there is no point in reserving the stock for a credit blocked customer, if at all it happens you may not be able to confirm a new order for 70 qty for a customer who is of cash sale type.
next order going back to credit hold after confirmation : this may be a scenario in material determination, you might have entered say $5 manually for a material & you had saved the document that will be of $5 value, once you release the order ( you will release the value as $5 against the order), now the determined material will have a condition record of $6 & hence will go for a block,( means if the manually entered price is lesser than the condition value) you will have the order going for block again.
let me know if my understanding on your question is right
rgds
ilango

Regarding open items in credit management

Dear friends
My query is that is it possible to restrict credit management for credit and debit open items? See i am using oldest open item blocking in my scenario. Now credit and debit amounts are both considered as open item for credit management. I want only invoice (Debit entry) for consideration and not his payment(credit entry).
Please advise is it possible or not and if possible where to define that???
With regards
Inder

Hi,
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 dont 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)
regards,
Siddharth.

Open Billing Doc value table in Credit management

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

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

I want field (Credit management) is the exception field for split billing

My system is R/3 4.6c
I have a mistake setting in Credit Management, and I can't remove
credit data from heading of sale order data. This error is cause of
spliting of invoice when I use transaction VF01. If I want to avoid it I have two questions to ask expert,
1. I should to modify pgm to avoid a billing split or NOT.
2.1 If NOT, please tell me how to clear credit data at order document ( I try F.28 but it not work)
2.2 If I must to modify pgm. which pgm that is modified. (From note
36832 I don't sure how to insert what line in copy routine 360-TH split
routine)
Thanks you.
Best Regards,
Kasem T.

Your Pages is behaving as it should. You have to add paragraph breaks to get to the line you want.
I am not a fan of tables but in this case it might be better to use one.

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 Error

Similar Messages

Maybe you are looking for