Risk Categories

Hi,
Can anyone tell me where the risk categories are configured in Credit Management? Transaction code and Menu path.
Thanks
Raghu.

Hi,
Risk categories are not linked to Credit Control Area. Risk Categories are assigned to Credit Master in Transaction Code FD32 / FD33.
Further for each risk category in Automatic credit control ?(T.code OVA8), the different checks to be carried out and the message (error / warning) is configured.
Thanks
Murali.

Similar Messages

Relation Between Interest and Risk Categories for Customers

Hi
Can somebody tell me if there is a relationship between interest rates and risk categories. We have not implemented neither treasury nor Hedging.
Would like to link the interest as per the risk categories. As the risk changes, interest should also vary.
Can this be achieved
Prasad

Hi Prasad,
It is all AR functionality: Dunning/Interest Calculation/Credit Management/Risk Categories; I think it is doable to adjust interest on late payments based on customer risk category; but I doubt you will get detailed answer on this forum. FICO forum may be better.
Manish

Risk Categories in credit management

Hello Gurus,
How can I get the configuration details for the different risk categories that are defined in an sap systems for credit controlling area?
Thank you.

Hi
Risk categories are defined in OB01.
Regards
Sowmya

Risk Categories in OVA8 - New Customers

Hello,
We recently set up new risk categories in OVA8. One of the things we would like to do is put an overall block on any account in a risk category New Customer status. Our intentions were to block users from entering orders before we were able to complete the Credit Management set-up so that we can prevent orders from going in on accounts that we have not approved. Is anyone aware of a setting that would accomplish this?
Thanks, Kevin

Maintain billing block in the sales order type's Billing section in tcode VOV8.
To brief you on billing block - It indicates if the item is blocked for billing. The system can automatically propose a billing block for sales documents that must be checked before billing. If the system proposes a block, you can change the block manually for each item. If the system does not propose a block, enter one of values predefined for your system. If the item has more than one schedule line, the block applies to each line. You can change the block for individual schedule lines.
Simply, it can be controlled by giving authorization for VA01(CREATE), VA02(CHANGE) and VA03(DISPLAY). Give authorization to VA02 to one whom you want it to be controlled by. Give authorization VA01 and VA03 one who creates sale order. By doing so billing block can be removed by one who is authorization to access VA02.
OR
Maintain authorisation object.
Then auth object V_VBAK_AAT Activity 43 in Tcode SU21.
You need to create the object for field FAKSK ie. Billing block in VBAK.
Then you need to assign the same in respective roles.
Assign the same to the respective users.
Thanks & Regards
JP

Compliance Calibrator 5.1 Risk Categories

Hello.
Is there a difference in the way the systems reacts to a risk category i.e. if the risk is classified as High, does it stop a user from doing something? Is there any difference between medium and low or are the categories merely used in the risk analysis reports as a statistic?
Thanks.

It is still preventative in that you can perform a risk analysis simulation. That is, you can test for risks <i>before</i> you grant the user access. It is also preventative in that it is testing segregation of duties controls, which are a type of preventative control.
Risk Terminator leverages from the Compliance Calibrator rule-sets and basically modifies the user maintenance and role maintenance tcodes to add a risk-analysis step in there. So, for example, if you are maintaining a role, when you go to generate, it will perform a risk analysis and you will have to document the reasons for creating/changing a risky role. Same when you assign roles to a user that combine to cause a risk. So, yes, Risk Terminator is also preventative. As is Access Enforcer.

Sytem should not allow to save the sales order based on risk category

Hi,
My user want to control the creation of sales orders based on risk category in credit control area.
We created a new risk category - 30 Not authorized.
And we made necessary configs also , like assignment of risk category and company code in OVFL.
We assigned 30 risk category in FD32 for customers also.
But while creation of sales order system is allowing to save the order.
My user requirement system shoud not allow to save the sales orders for those are customers belongs to 30 risk category.
How can we config. this
thanks
Sateesh

hi,
dont want to save the sales order if the credit limit exist ?
then maintain block in OVA8
choose
your credit control area risk categories credit group
1000 30 Not authorized 01
checks tab
choose static and maintain B
this will give you error message and it will not allow you to save the sales order
regards
senya
Edited by: senya_1111 on Oct 1, 2009 2:26 PM

Risk Mgmnt COnfiguration steps

Hello Friends
Can anyone please tell me the complete steps to configure "Risk Management " with LoC (Letter of Credit) & what is the necessary data to be collected from the business, for configuring the same.
Regards
Sumanth.Gururaj

Hi,
The configuration steps for risk management
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.
Credit Management Reports
The following table provides an overview of all the reports that are available for credit management:
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 Documentation Background
Checks released documents whose validity period of the release has been exceeded (number of days).
RVKRED88     Simulating Reorganization of SD Credit Data
To run a report:
1.     Choose System ® Services ® Reporting.
2.     Enter the name of the report.
3.     Choose Program ® Execute.
4.     Enter your selection criteria.
5.     Choose Program ® Execute or Program ® Execute and print.
SAP SD Credit Management Tcodes
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
u2022     V_TVTW - Define Distribution Channel
u2022     V_TVTA_KKB - Assign sales area to credit control area
u2022     V_T014 - FI - Define Credit Control Area
u2022     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
u2022     Check Credit
o     A - Credit limit check and warning message
o     B - Credit limit check and error message (no sales order can    be created)
o     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)
o     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
u2022     Credit group
o     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
u2022     whether the automatic credit check occurs at the time of delivery creation and/or goods issue
OVA7 - Define credit limit check by item category
u2022     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).
u2022     SAP default credit groups
o     01 - credit group for sales order
o     02 - credit group for delivery
o     03 - credit group for goods issue
OVA8 - Automatic credit control - Double click on the line items
You can have the followings credit limit check :-
u2022     Static
Depends on the customer total value of open orders, deliveries, billing documents and open items.
u2022     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.
u2022     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.
Dayu2019s oldest item
No of days allowed for overdue or payment terms.
Use of the credit checks Oldest Open Item. If a user attempts to alter the order quantity of a released sales document
that was previously blocked, it would be re-blocked again by the system. The system only re-blocks the sales document if the new order quantity is above a certain % amount.
u2022     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.
u2022     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 date 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)
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 & Transferred 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 Category + 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 Category: Based on the risk Categories Company decides 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 delivered
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 transferred 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 last 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)
User Exits For Credit Checks And Risk Management
Credit Check
I hope this will resolve your issue
Thanks
Anil Hooda

SD - Risk Management

Dear expert gurus ,
i would like to know how sap system controls the level of risks in risk management (High/Medium/Low).
and also where to do the settings to block the order when the risk is High.
Thank you very much.......

Hi,
You find the SD risk management settings in IMG-SD-BF-Credit Management/Risk Management-Credit Management
Here check this below configurations and read the Documentation
1.Define Credit Groups(where u can set the credit checking)
2.Assign Sales Documents and Delivery Documents
3.Define Automatic Credit Control( here u hv to set ur credit check determination based on the combination of ur credit cont.area ,Risk category and credit grp)
Craete ur Risk categories in IMG-Financial Accounting (New)-Accounts Receivable and Accounts Payable-Credit Management-Credit Control Account-Define Risk Categories(high/med/low) ..
and maintain customer credit limits in t-code FD32.here in status ..enter ur Risk category of ur customer
for more search topic on Credit management in forums...
Reg
JJ
Edited by: Jagsap on Jul 14, 2009 11:13 AM

Risk Code

Hi All,
Please let me know what Risk code and Enginnering Series related to MM module.... please let me know the table name to get these fields.
Regards,
Amogh

in which tcode u are seeing risk code .
are u talking abt risk categories ?
Regards
Prabhu

Does Simple Credit Limit Check Include Checking for Open Orders

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

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

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

Report to display Average time taken for processing payments".

Hi,
I have been asked to develop a report for "Report to display Average time taken for processing payments".
Could any one guide me technically what are the different tables i need to take to generate the report. Treat this is very urgent. Pls provide sample code too....
Thanks in advance....

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 00012. 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: A
Reqt: 2
AltCTy: 4
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 no Credit Check 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 02 defined for payment cards. Other than the descriptor, the only other entry should be 3 in the column labeled PymtGuaCat
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 1
Payment Guarantee Form 02
Routine Number   0    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 = Payment Card Payment Cards (All Customers can use Payment Cards).
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 (etc)
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 03 in the column labeled PT 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 A001
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 IDs
Transaction:
Tables: TCCM
Action: Create the merchant ids that the company uses to process payment cards
Assign merchant ids
Transaction:
Tables: TCCAA
Action: Enter the merchant ids with each clearinghouse account

Credit check at Delivery

For one of our risk categories, we would like the credit check to occur at both the Sales Order and Delivery creation events. In transaction OVA8, I have created records for the credit control area/risk category/credit group. The credit groups are assigned to the document types properly (01 - at Order, and 02 - at Delivery).
When I create an order which exceeds the credit limit, I release it from credit block in VKM1. I then proceed to create a delivery. At this point, I would like the delivery to block, but it is not doing so. On the Header--> Processing tab, the Credit Status is "D" (Released). This implies that just because the order was released, the delivery will not block.
A few questions....(a) does the "Number of days" in the risk category need to be set to zero? (b) does the delivery need to have value to block? Any additional thoughts you have would be greatly appreciated.
Thanks.

Dear dbrennan,
It is a standard functionality and for your questions
(a) does the "Number of days" in the risk category need to be set to zero?
SAP says
The current date is not greater than the Release date + the Number of days specified in the Rick category.
and System is not allowing negative ( -1) date too.
(b) does the delivery need to have value to block?
In practical, Is the sales order credit check and Delivery order credit parameters were different?
Regards,
Mani

New Company code creation

Hi,
Client wants to split one company code to 8 company codes.
Could you please explain what are the neccessary steps to take for this ?
What are the precautions to take in creating Company code, Chart of accounts, AP,AR related,AA and consolidation ?
Regards
Madan

Hello,
You can keep concentration on the following transaction codes.
These may be useful guide to you.
FI Enterprise Structure Transaction Codes
Transaction Code     Description
OBY7     Copy Chart of Accounts
OB29     Fiscal Year Variant
OBBO     Posting Period Variant
OX02     Company Codes - Create Check and Delete
OBY6     Company Code Global Parameters
EC01     Copy Company code
OY01     Country Definitions
OB22     Parallel Currencies
OX03     Business Areas
OKBD     Functional Areas
FI Enterprise Structure Transaction Codes (Continued)
Transaction Code     Description
OBBG     Assign Country to Tax Calculation Procedure
OBCO     Specify Structure for Tax Jurisdiction Codes
OBCP     Define Tax Jurisdiction Codes
FTXP     Maintain Tax Rates
OBCL     Set Tax Codes for Non-Taxable Transactions
General Ledger / Chart of Accounts Transaction Codes
Transaction Code     Description
OBD4     Account Groups
OB53     Retained Earnings Variant
OB15     Sample Account Rule Types
FSK2     Sample Account Data Transfer Rules
OB67     Allocate a Company Code to a Sample Account Rule Type
OBY9     Transport Chart of Accounts
OBY2     Copy GL Accounts from the Chart to the Company Code
OBC4     Field Status Variants
OB41     Posting Keys
FBKP     Automatic Account Assignments
OB40     Define Tax Accounts
OBYA     Cross Company Code Automatic Account Assignment
OBYC     MM Automatic Account Assignment
VKOA     SD Revenue Account Assignment
OB58     Financial Statement Version
O7Z3     Line Item Layouts
OBVU     Special Fields
O7S7     Sort Variants
O7R1     Totals Variants
OBA4     Tolerance Groups
OB57     Allocate Users to Tolerance Groups
FBN1     GL Number Ranges
OBA7     Document Types
OBU1     Assign Default Posting Keys to Document Types
O7E6     Fast Entry Screens
ORFB     Financial Accounting Configuration Menu
OBL1     Automatic Postings Documentation
OB32     Maintain Document Change Rules
General Ledger / Chart of Accounts Programms
Transaction Code     Description
RFBISA10
RFBISA20
RFTAXIMP
General Ledger / Chart of Accounts Tables
Transaction Code     Description
BSEG     GL Document Line Item Table
TTXD     Tax Jurisdiction Code Structure Table
T030     Automatic Account Assignments Table
TZUN     GL Account Sort Key (Allocation Field) Table
Accounts Payable Transaction Codes
Transaction Code     Description
FI12     House Banks
FCHI     Check Lots
FCHV     Void Reason Codes
FBZP     Payment Programme
OBD3     Vendor Groups
XKN1     Create Number Ranges for Vendor Groups
OBAS     Assign Number Ranges to Vendor Account Groups
FK15     Copy Vendor Master Records Creation Programme
FK16     Copy Vendor Master Records Creation Programme
Accounts Receivable and Credit Management Transaction Codes
Transaction Code     Description
OBB8     Terms of Payment AP and AR
OB46     Interest Indicator
OB82     Make Interest Indicator Available to the Interest Calculation Program
OBAC     Reference Interest Rates
OB81     Assign Reference Interest Rates to Interest Indicators
OBV1     Interest Calculation Automatic Account Assignment
OBBE     Reason Codes
OBCR     Reason Code Conversion Version
OBCS     Map External Reason Codes to Internal Reason Codes
OBXL     Assign GL Accounts to Reason Codes
OBXI     Cash Discount Amount
OBA3     Customer Tolerance Groups
OB45     Credit Control Areas
OB01     Credit Risk Categories
OB02     Credit Representative Groups
OB51     Assign Employees to Credit Representative Groups
OB39     Days in Arrears Calculation
OBD2     Customer Groups
Treasury Transaction Codes
Transaction Code     Description
OB10     Create Lockbox Accounts
OBAY     Define Lockbox Control Parameters
OBAX     Lockbox Posting Data
OT05     Source Symbols
OT14     Planning Levels
OT13     Planning Groups
OT47     Assign Logistics Transactions to Planning Levels
OT17     Treasury Groupings
OT18     Treasury Grouping Headers
OT16     Cash Management Account Names
OT29     Activate Company Code Treasury Updates
OBBY     Electronic Bank Statement Transaction Types
OT55     Assign Transaction Types to House Banks
OT57     Electronic Bank Statement Posting Rules
OT51     Map External Transactions to Posting Rules
OT59     Posting Rules Automatic Account Assignment
GCRF     Currency Translation Ratios
Regards,
Ravi

Credit management configuration in Third party sales

Dear All,
Please let me know , what are the configuration setting for Credit Management in Third Party Sales.
Regards
SKumar

Hi...
For Third Party, since there is no Delivery and PGI, the block can be at Billing.
however the total outstanding value from the customer at the time of billing along with the days as set in the credit limit shall be basis of blocking.
Config Steps:
u2022     Assigned the credit control area to the company code
Financial Accounting (New)  Accounts Receivable and Accounts Payable  Credit management  Credit Control Account  Assign Permitted Credit Control Area to Company Code
u2022     Assign Sale Document and Delivery Document, The credit limit check for the selected sales document type is set to automatic control.
Sales and Distribution  Basic Functions  Credit management / Risk management Credit Management Assign Sales Documents and Delivery Document  Credit limit check for order types
u2022     Assigning Risk Category to Credit Control Area
Financial Accounting (New)  Accounts Receivable and Account Payable  Credit management  Credit Control Account  Define Risk Categories
u2022     Defining Automatic Credit Control
Financial Supply Chain Management  Credit Management  Integration with Accounts Receivable Accounting and Sales and Distribution  Integration with Sales and Distribution Define Automatic Credit Control

Risk Categories

Similar Messages

Maybe you are looking for