Authorizations in Credit Control Configuration

Dear Friends
I am configuring "automatic credit control " for our client. The requirement is 4 levels of authorizations. I've completed the settings for credit check at transaction level.
Now, How do I maintain the Authorizations (4 levels) I am aware that there are 3 controls , user1, user2 & user3 in OVO8 control.
Any help/suggestion, will surely be appreciated.
Rgds
Sumanth.Gururaj

hi friend
You mean you want to create 4 level release authorizations, right?
As we know, user1, user2 & user3 in OVO8 control are customized credit checking user exit. we can add our specific checking logic on it.
But for credit release, there is a standard function as VKM1.
As your requirements, I think there is a standard function maybe can help u, named User Status Control.
You can add some status to control the sales document, for example, block delivery, block billing.
If document has not been approved, system will reject further action according to your status settings.
Hope this can take some help for u.
Wink.

Similar Messages

Credit Card Configuration in SAP

Dear All,
Can I have the information on Credit Card Configuration.
Regards,
Geroge

Dear George,
Please find the relevant details related to credit Crads as follows:
Overview
This document attempts to explain in the brief the credit card processing in SAP.
SAP provides a flexible and secure payment card interface that works with the
software of selected partners that provide merchant processes and clearing house
services. In SAP the credit card processing is integrated with the sales and
distribution module.
Payment card configuration
Much of what is required for credit card processing to work with VISA, Master
Card, and American Express is already set up in SAP.
For all credit card configurations refer to
Define Card Types
Transaction SPRO IMG Sales and Distribution Billing Payment Cards
Here we define the type of cards that can be used in the system. A four-letter
code is given for each card type. E.g. MAST for Master Card, VSAJ for Visa
Japan. A function module for checking the card number is also specified here.
1. Define Card Types
Credit Card Configuration And Processing In SAP
Maintain Card Categories
(a) Define card Categories: Here we specify the card category of the
payment card. With this the system automatically determines the card
category when you enter a card number in master data or sales
documents.
(b) Determine card categories: Here we specify the acceptable number
ranges for different card types. Also card categories are assigned to the
card types. Even though SAP comes with card checking algorithms
(Function Modules) for standard card types this configuration setting
is particularly useful to those cards that do not contain any standard
checking algorithm already set up in SAP.
2. Determine Card Categories
Maintain Payment Card Plan Type
In this step, you assign the payment plan type for payment cards, the payment
card plan type, to all sales document types in which you will be using payment
cards. You cannot process payment cards if you have not made this assignment
The standard system contains payment plan type 03 for processing payment
cards. 3. Show the screen where this assignment is done.
Credit Card Configuration And Processing In SAP
3. Maintain Payment Plan Type
Maintain Blocking Reasons
In this step, you define blocking reasons for payment cards. You enter these in
the payer master record to block cards. The standard system contains blocking
reason 01 for lost cards.
Risk Management for Payment Cards
Transaction SPRO IMG Sales and Distribution Billing Payment Cards
Authorization and settlement Risk Management for payment cards.
Risk Management plays a central role within Sales, providing you with checks
and functions to minimize your credit risk. In addition to letters of credit and
export credit insurance, payment cards are among the payment guarantee forms
that you can use to insure payment for sales order items. SAP comes with predefined
payment forms of guarantee as shown below. Customer can also
maintain other forms of payment suited for their line of business.
Credit Card Configuration And Processing In SAP
Define forms of payment guarantee
3. Define forms of payment guarantee
Maintain payment guarantee procedures
In this step, you define Payment guarantee procedure. These procedure controls,
which form of payment guarantee, are valid for a particular customer, and for a
particular sales document type.
The various settings done under this configuration are
Define payment guarantee procedures
Maintain customer determination procedure
Maintain document determination procedure
Assign sales document types
Determine payment guarantee procedures
Maintain authorization requirements*
Here requirements* are set to tell the system how and when to carry out
authorization when a sales order is saved. SAP comes with two requirements
Form routine 1. Carry out authorization only when the sales document is
complete. The system carries authorization when the order is saved.
Form routine 2. Carry out authorization only when the sales document is
complete, but the authorization for all the complete documents is carried out in
batch.
Additional requirements* can be assigned here as per the business requirements.
*Requirements are ABAP/4 code. Requirements for various functions can be accessed using transaction VOFM
Credit Card Configuration And Processing In SAP
4. Maintain Card Authorization Requirements
Maintain Checking Groups
How and when authorizations are carried out depends on the setting you make in
the customizing for maintain checking group routines.
The three main settings that influence authorization are:
a) Authorization requirements
b) Authorization horizon
c) Preauthorization
There are two settings under this setting.
Define checking group: Here a checking group is defined and the
authorization requirement (described in the previous section), Authorization
horizon (described below) and preauthorization settings are done for this
checking group.
5. Define Checking Group
Credit Card Configuration And Processing In SAP
Here you can see a checking group C1 is defined with the authorization
requirement 902. Checking the pre-authorization tells the system to carryout preauthorization
if the order fulfillment date falls outside the horizon. The
authorization horizon specifies the number of days before the material
availability date, or billing date, that the system is to initiate authorization. If a
sales order is saved within the authorization horizon, the system carries out
authorization immediately. If a sales order is saved before the authorization
horizon comes into effect, the system does not authorize at all, or carries out
preauthorization.
6. Preauthorization Concept
In this example, the system has been set to authorize one day before delivery
creation. The system does not carry out authorization when the order is saved on
Day 0, rather on Day 2. Note that the authorization validity period has been set to
14 days in Customizing IMG Authorization and settlement Specify
authorization validity periods. The transaction will have to be reauthorized if
delivery activities take longer than 14 days.
Assign checking groups: Here the checking groups defined earlier are
assigned to different sales document types as shown 8.
Specify authorization validity periods
Here number of days that an authorization can remain valid for different card
types are maintained. Refer to 9.
Credit Card Configuration And Processing In SAP
8. Assign checking groups
9. Assign validity period for authorization for different card types
Credit Card Configuration And Processing In SAP
Account Determination
Transaction SPRO IMG Sales and Distribution Billing Payment Cards
Authorization and settlement Maintain Clearing House
In the following steps, you set the condition technique for determining
clearinghouse reconciliation accounts for authorization and settlement. The
system uses the entries here to determine the clearing account for the payment
card charges. When settlement is run, the postings in the receivable account for
the payment card will be credited and a consolidated debit will be created and
posted to the clearinghouse account. These accounts are a special type of general
ledger account that is posted from Sales and Distribution.
Here, you maintain:
Maintain field catalog.
Condition tables and the fields that they contain
Access sequences and condition types
Account determination procedures
You then assign these accounts to condition types.
Add to field catalog
Here you maintain the fields that can be used in the condition table. 10.
Shows the transaction to maintain the field catalog.
10. Maintain Field Catalog.
Maintain condition tables
Here condition tables are maintained with fields that are added to the field
catalog. SAP comes pre-configured with two condition tables 4 and 6. Refer
11.
Credit Card Configuration And Processing In SAP
11. Maintain Condition Table
Maintain access sequences
In this step we define an access sequence and link the access sequence with the
condition tables.
Here an access sequence is defined. SAP comes with the access sequence A001.
12. Define Access Sequence
Once the new access sequence is defined, it is linked to the condition tables as
shown in the next screen.
Credit Card Configuration And Processing In SAP
13. Maintain Access For Access Sequence
Selecting an access and clicking fields will display the fields for the selected
access as shown below for access 10 as shown above.
14. Display Access Fields
Maintain condition types
Here condition types are defined and the access sequence to linked to it.
Condition types are contained in account determination procedures and control
which access sequences the system uses to find condition records.
These are The condition tables.
Credit Card Configuration And Processing In SAP
15. Define condition type
Maintain account determination procedure
In this step an account determination procedure is defined and linked to the
condition type (which in turn is linked to the access sequence).
Define account determination procedure
16. Assign account determination procedure.
Here an account determination procedure CC01 is defined and the condition type
CC01 is assigned to it.
Access sequence linked to the condition type
Credit Card Configuration And Processing In SAP
Assign account determination procedures
In this customizing the previously set up account determination procedure is
assigned to different billing documents.
Assign Accounts (G/L)
G/L accounts are assigned here for the combination of Sales organization, Card
type, chart of accounts and condition types as shown in the 17.
17. Assign G/L accounts
Set authorization / settlement control per account
Each G/L account is assigned an authorization and a settlement function module.
The system will read the configuration a call the authorization and settlement
function module during authorization and settlement respectively.
Credit Card Configuration And Processing In SAP
18. Set Authorization and settlement function module
Maintain merchant IDs per account
A merchant may have one or more IDs for each clearinghouse with which it does
business. Here, you assign these different merchant IDs to their related
receivables accounts.
19. Assign Merchant IDs
Credit Card Configuration And Processing In SAP
Authorization and Settlement in SAP
20. Sales Order Cycle With Credit Card Authorization
When an order is placed through the front-end system, the order information,
credit card information, billing information, shipping information is passed to
SAP. SAP processes the order calculates the taxes, the shipping costs and reads
the configuration information settings and executes the function module setup as
described in Fig. 18. The function module formats the data and makes a RFC *
call to the payment application**.
The payment application screens the order for fraud, encrypts the data and
communicates with the third party processor who in turns communicates with
the card association and card issuer.
*RFC (Remote Function Call)
*Payment Application: Middle ware between SAP and third party processor/bank.
Credit Card Configuration And Processing In SAP
The third party processor responds back with the response whether the
transaction is approved or declined or referred.
Note: When any item in the order does not have a confirmed quantity, then
authorization is not carried out for the full amount. A small dollar amount
usually ($1) is used as the authorization amount. During the rescheduling run
the system will check for the material availability. If the material can be
delivered within the horizon date, a full authorization for the order is carried
out.
Approved: When the credit card transaction is approved the systems checks for
the material availability, confirms the material for the ordered quantity and saves
the order.
Declined: The material availability check for the material is not made, and the
order is rejected.
Referred: The order is saved and is blocked for delivery. In this situation is
merchant calls the bank checks for the available credit on the card and a manual
authorization is carried out.
21. Sales Order Entry Screen in SAP
Payment Card
Information
Credit Card Configuration And Processing In SAP
The first line in payment card screen is the card check performed by SAP system,
using the card check algorithm function module as described in 1. And the
remaining lines represent the actual authorizations that are carried out.
22. Payment Card Screen
Path Header Payment Cards.
Settlement
Legally the merchant can charge the credit card after the order has been
completely processed. In SAP this happens after a delivery is created and the
goods has been shipped. In case there is not enough authorization for the order
to be delivered, the system goes out the get the authorization for the remaining
amount.
In SAP settlement is initiated using the transaction FCC1. All the valid
authorization is submitted in a batch to the payment application at scheduled
intervals as specified by the third party processor.
The payment application encrypts this data and communicates with the third
party processor. The third party processor checks if the settlement request has a
valid authorization against it. The third party processor then transfers the fund
from the cardholders bank to the merchant bank.
Authorization
Response
Credit Card Configuration And Processing In SAP
Regards,
Rakesh

The minimum hardware configuration to support the Diameter credit control

Hello.
I'd like to know what the minimum hardware configuration is required to support the Diameter credit control application?

Hello Mr.. Tarasenko,
According to the information found the diameter credit control application does not specify how many or which type units are bought/used and which items are charged. This is left to the company’s needs.
Diego Rodriguez
Cisco network engineer
Thank you

Authorization for credit limit - risk categoryu200F

Hi All,
I would like to control field risk category by authorization.
I have configure in Field Groups and assign it to user roles using object
F_KNKA_AEN.
and below for the authorization objects for credit management:
1)V_VBUK_FRE
2)V_KNKK_FRE
3)F_KNKA_KKB
4)F_KNKA_MAN
5)F_KNKA_AEN
But the fields are still not grey out.
Is there any other configurations not completed?
Is there any alternative methods?

Hi,
Take the help of basis consultant and give authorization for display onely then it will appear as gray
Kapil

User exit for merging the credit limit in different credit control area.

Dear All,
Please provide user exit for the merging the credit limit in different credit control area as well as logic for the same.
I have to merge the overall credit limit of the customer for some divisions. At this time in one company code we have created 9 credit control area as per product line. While creating customer master data and Credit management (FD32) user has assigned the different limit with respective to credit control area e. g Customeru2019s total limit assigned is 10 laks. For credit control 1100 Limit is Rs. 3 laks and for credit control area 2200 limit is 7 laks. Now the user wants to merge the credit limit for only above two credit control area. The sales orders should get created in any credit control area up to 10 laks.
Regards,
Suresh

Dear Damodhar/All,
Would you please explain me prerequisite setting from functional side for these user exit?
I want complete functional setting prior to ABAP application so that it work properly post configuration.
Regards,
Suresh

Authorizations in Credit Management

Hi,
There is a requirement to control the release of the Blocked Sales Orders due to credit check through a customized transactions. For this a Z transaction has been developed which will have a list of Sales orders which are blocked due to Credit Check. In this case Authorized users need to release the sales orders from the check for further processing. The release of the sales orders Authorization is given to set of people who will release the sales orders based on the Document value.For example if the document value is upto 1000pounds, XYZ user will release the sales order. If 1000 to 3000 pounds, ABC user will release the order. In this case system should not allow the XYZ user to release the sales order or value more than 1000 pounds. Can we control this through Authorization? If yes can you please brief about the same.
Thanks in advance.
Regards
Narendra

For maintaining authorization:
SPRO --> IMG >SD> BF> CM/RM> CM/RM settings --> Maintain authorizations
<b>Document Value Class:</b>
Document value classes provide a means of assigning sales order and sales and distribution documents depending on their document value
Using the document value classes, credit representatives, for example, can be given different authorizations for credit allocations depending on the document value.
Actions
1. Create document value classes according to your requirements by entering a three-character alphanumeric key and a textual description.
2. Make sure that the credit representatives are allocated to the document value classes.
Assign Document value Classes:
1. Enter a credit control area and allocate a credit value to it in a relevant currency.
2. Allocate a document value class.
3. Make sure that the credit control area was entered in the corresponding customer master records.
Maintain Authorizations:
Here u need to create roles and for perticular user , you can assign that authorizations.
If you need more help prefer implementation guide in help.sap.com

Urgent: Need help in automatic credit control

Hi SD Seniors
Please help me in the URGENT Credit check Control Configuration.
According to the user requirement, need to have simple static credit control in the place of sales order & delivery.
When credit check fails during the order creation,
1.     Wants to popup the warning message without blocking the delivery
2.     And wants to block the delivery from the PGI process.
I have already done the necessary credit check configuration in my test system. Based on the simple credit limit check,
System issues the warning message correctly at the time of order creation.
And I have configured the automatic credit check control configuration for the blocking the delivery PGI steps. But system doesnt block
The delivery and it still allow proceeding for PGI without any error message.
Please refer by below automatic credit control check for blocking the delivery. Please let me know, is there any other step I missed out here.
1. Credit control area is assigned to the company code.
2. Credit control area is assigned to the sales area.
3. Credit control area is assigned to the payer.
5. OBZK:   Assigned
7. Risk category for each credit control area.
8. OVA8: -Credit control area + Risk category + Credit group
9. FD32: -Credit limit, Risk category, Currency: assigned
10. OVA7/VOV7: - Activated correctly
11. V/08: - Pricing Procedure subtotal set to A
12. OB45: - Update Group 00012
Your help is very much appreciated.
Thanks in advance
Regards
Priyan

Karan, Thanks For you Quick Response.
OVO8: Cr.Ctrl.Area + Rick.Catg + Credit.Group (03)
The same credit group was assigned to the OVAD also.
OVAD: Dely.credit.grp = 03   (Credit group for goods issue)
AND
GI.Credit.group = 03 (Credit group for goods issue)
Is it correct?
My doubt is where exactly, we are telling the system to block the delivery.
In OV08, could you please tell me what are all the settings need to be done for
block delivery PGI
Regards
Priyan

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

Authorization for Credit, Commitment Limit and Payment Terms

It's very required to have authorization for Credit Limit, Commitment Limit and Payment Terms change. Currently it's very hard to control limits as every user can change these values and omit approval procedure or authorization for Confirm Credit Line Deviation and Confirm Debt Line Deviation.

Thanks, You were right. It runs well for the sales order with out delivery. After I create delivery in reference to this sales order and change payment terms in sales order there is no new credit control check.
Is there a possibility to run credit control check after a delivery is created?

Use of customer hirearchy in credit control

Dear Friends,
Good evening.
I would like to know whether we can use customer hirearchy for credit control purpose.
If answer is yes how it can be done ?
Scenrio:
One company code,4 sales areas.
The objective is define seperate credit limit and risk profile for each sales area in which customer is extended.
May Kindly suggest solution keeping in view following entries hiting customer account:
1.Invoices
2.Payments (specialy advance payments)
3.Credit & debit note passed through FI (tcode FB70)
4.Validation to ensuer that Invoice/Debit note of one credit control area shall not be knocked off through payment/credit note of different control area.
Regards
Sanjay

Hi chandershaker,
Thanks for your suggestions.
I had thinking on same line though have configured system accordingly.
I need an alternate solution to evaluate and expert advice of the forum.
The objective is in one line that we need single customer code with AR & credit control division wise.
May pls advise.
Regards
Sanjay

Credit control field not visible in customer master after checking Spro

Hello Gurus,
I have configured Automatic Credit Control In IMG.
I have checked all the necessary spets required for the avtivation of Automatic Credit Control.
But I am facing in problem and will appreciate all your help for this problem.
In Customer master> Sales area data> Billing Document--> delivery and payment terms. Within delivery and payment terms the feild for credit control area is not visible.
I have checked in spro>financial accounting> Ac rec & Ac payable>customer account>master data>preparation for creating customer master> define account groups with screen laypouts (customers).
Within Define account groups with screen laypouts (customers)>account group 001(soldtoparty)details>field status>sales data>billing-->Hedging and credit contr. area I have tried it with optional as well as reuired entry and still the credit control field is not visible in customer master.
Pls provide me the steps as well as solutions for the problem.
Thanks & regards,
Dev.

pls check accunt group again
rgds
nitin

*Billing Document Splitting with Credit control Area*

Hi
please give me solution for the following matter
there have some invoice splitting with credit control area from sales order header , because some orders available credit control area some order not available credit control area . can i create one billing document for those without splitting?
thanks
L.C

Hi L.C,
You can see VBAK-KNKLI field differs in sales document. The split is standard system behavior since
these are header fields. Please refer to note 11162 for details on split criteria for invoices.
In order to avoid the split you can either clear the fields in the copy control or you can change your credit management
configuration so that the credit accounts determined are the same.
I hope it can help you.
Regards
Ruy Castro

Problem in credit control area

Hi Gurus,
We have configured credit control area using Static Credit check.
We have assigned the same to order type and delivery type also.
While creating sales order, even though the total value is crossing the credit limit which is set in FD32. the system is not prompting any error.
Please suggest, where we could have gone wrong..
Sridhar.P

Hi gupta,
you need to check the following in customizing settings.
Credit checks can run at different times during order processing.
For delivery creation, you can additionally specify whether the automatic credit check occurs at the time of delivery creation and/or goods issue.
In this menu option, you specify the sales document types for which a credit check should be carried out. Here, delivery types can be controlled separately and specifically at the time of goods issue.
At the same time, you specify the system responses if credit checks are set. The system can respond in the following ways:
     Warning message
The document can be saved.
     Error message
The document cannot be saved.
     Setting a delivery block (credit status)
The document can be saved. However a block is automatically set in the credit status.
Actions
1. Define for each sales document type whether a credit check should be carried out. Enter "D" if an automatic check should be carried out.
2. Specify a credit group.
3. Specify a credit group for the delivery type for which you want to carry out a credit check.
4. Specify a goods issue credit group for the delivery type for which
Reward points.
Regards
Manoj

Credit control by Division wise

Hi Consultants,
How can we configure Credit control by division wise.
Thanks&Regards,
Siva

No, to the best of my knowledge, Credit Management works COmpany code-wise & Crediot Control area-wise.
Thanks,
Jignesh Mehta

Credit Control Area Management

Dear All
As part of Enhancement, we are configuring the "Customer Credit management" with Credit Control area organizational object.
Client has identified to use "Decentralized" Credit control management, but however, all comapny codes are assigned with one controlling area since implementation (since 2.5 years).
Though Credit Control area was assigned during implementation, it was actually not used. Now they wanted to use the same. However, they wanted different Credit controlling area for different company codes.
However, If I am assigning new Credit controlling area now to respective company codes, then system is considering the AR transaction data posted from the date it is assigned. but, we want new credit control areas to consider all the data from past 2.5 years. Is this possible?
If possible, please help, how to fix this.
Your help highly appreciated
best regards
S Habib Pasha.

Hi Habib
There is a standard SAP program that lets you revamp all the entered data to their correct credit control area and the steps involved are:
u2022     Table dumps of KNKK, S066, S067 on the old Credit Control Area
u2022     Check and export the values from Report VKM4 to ascertain the number of blocked orders
u2022     In SM30, Update the Tables T014n and T001cm
u2022     Go to Transaction OB38 and assign your new CCA as default for the company codes
u2022     Run the transaction F.28/RFDKLI20 execute without any parameters {check the test run output}
u2022     Execute Program RVKRED09 {might not be required u2013 since RFDKLI20 does redo the credit check}
u2022     Validate VKM4 for all blocked orders
u2022     If there were any discrepancy between AR receivables and the Credit Master, it can be viewed by executing the Program RFCORR40
Also make sure that if you are using the different CCA for the same Co Code, in OB38 - you have checked the 'Overwrite CCA'' check box.
Hope this helps you; let me warn you - its a very tedious process and it might take a whole weekend to run this in a Production Client
Good luck
Rukshana

Authorizations in Credit Control Configuration

Similar Messages

Maybe you are looking for