Implementing Credit Management without the SD module

Hi SAP Gurus,
Greetings to all. I would just like to confirm if we can actually implement the Credit Management module within FI without the SD module? We are only intending to use Credit Management to control the credit limits assigned to customers. We might be also utilizing some of the basic credit control reports available.
Hoping for some advice / comments from you guys.
Thanks a lot

Hi,
Yes, you can implement the credit management without SD module.
So you cna check the credit limit againest the open exposure consisting of open AR due.
Regards,
Gaurav

Similar Messages

Implementing Credit management without AR

Hello,
Is it possible to impliment the Credit Management with out the AR module?
we are using the Oracle apllication for AR,
Just when creating orders in SD i want the credit check to be started
Thank's
Yehudit

Hi,
Please check the following links
[Credit Management|http://help.sap.com/printdocu/core/print46c/en/data/pdf/FIARCR/FIARCR.pdf]
[SD Credit Management Wiki|http://wiki.sdn.sap.com/wiki/display/ESpackages/Credit+Management]
[SAP Library|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00a9015a-3664-2e10-5bb2-a3ab2b61f5d8?quicklink=index&overridelayout=true]
Kindly close thread if answered.
Regards,
Amit

Release Strategy for Credit Note un the QM Module

Good SAP Guru's,
I have a very important question for you:
Is it possible within in the QM module (Transaction QM12) to implement a Release Strategy based on the value of the credit note to be created.
This should work on the same lines as the Purchase Order Release strategy.
Any guide lines and/or assistance will be gratefully appreciated.
Kind regards,
Leslie

Dear Leslie
We had done a similar kind of development in notification, not for credit memo though , but certainly can be incorporated in this case.We had done this for approving Short shipment and devaitions. If there has to be short shipment to be sent to a customer a notification will be trigered to manager and if he approves it will go for higher approval.
Please find my suggestion for this development
1) Make 3 task codes. for eg Task 1 for credit note is for less than u20AC500.00 . Task 2one for more than 501 and Task 3other one for more than 2001.
2) According the need of the credit notes to be created let the user assign the task and release it.
3) For task no 2 and task No3 a workflow triggers to the corresponding roles Sales manager & General Manager. ( please note that notifications are workflow freindly and standard workflows are available for the same)
4) if Manager wants to approve he can make the Task Complete. ( Notification tasks have 4 stages, outstanding, release, complete, Succussful)
5) Based on the status of the task you can make use of the action box in notification for creating the credit memo.
6) The credit memo creation will have to be developed. You will have to get ABAP support for this. They can either do it through user exit, or call transaction , and incorporate the same in the Action box of notification. (QQMA0001: User Subscreen for Notification Header, QQMA0014 Checks before saving notification )
please let me know your apprehensions
Regards
gajesh

Credit management without accounting document

Hi,
In the SAP implementation for my client there is no FI module. FI is handled in third party ERP software.
The Billing Document will not be posted to accounting as there is no FI module. Each billing document will be passed to the third party ERP Software where accouting document will be generated.
My question is related to Credit Management in such environment.
The credit management is to be used in SD area. As the accounting document is not there credit balance will be
credit limit- (open ordersopen deliveriesopen billing documents).
The client requires the open items (as available from third party software) to be considered in the credit check.
I have prospoed the solution as below.
Update the fd32 receivables daily (or at a appropriate frequency) from third party to SAP. If receivables are updated in fd32 it can be considered in the credit check.
My question is, is anybody handled such scenario? Is it possible and recommended to updated fd32 receivables in the database table directly?
Is there any other solution to map this requirement?
Regards,
Sachin.

No idea about your solution, it seems to work but I'mnot sure.
Anyway have a look to this link about Credit Management in Distributed Systems:
http://help.sap.com/saphelp_47x200/helpdata/en/4d/0a4aa3b26811d194f400a0c9306794/content.htm
pls. reward if helpful
Regards
Roberto

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.

Fixing the color management in the print module.

Some printers are supported some not. Some profiles
will show on the manage color list, most not. Photoshop
has a sRGB printer profile, could one be made available
for Lightroom? I have read a lot of post concerning
poor print colors from Lightroom, at the very least Lightroom
should allow any printer to manage the color.
Thank You
Tom

I have read a lot of post concerning poor print colors from Lightroom, at the very least Lightroom should allow any printer to manage the color.
I agree, but it doesn't let the Canon S9000 or HP D7460, it will not let these printers manage the color,the colors come out muddy looking when I manage by printer. I assume these two printers do not have paper profiles because nothing shows in the profile list. I'm not an expert on printing but I can get decent prints out of any other software I use except from Lightroom. As for the sRGB it would be better then nothing and that is what I have now. I have tried using other profiles with limited success.
I have given up trying to print from Lightroom, to bad because all the other modules work fine.

Using gift card to purchase tv shows, and not! Credit card without the "none" option being there

i search up a show I click purchase and type in my password it asks for credit card info, it doesnf let me select none, i want to use my iTunes gift card help I'm three seconds away from throwing out my ipad :-/

Your balance covers the the show's price (plus any applicable taxes), and it this the first time that you've tried to download something with the account ? If it is the first time, then unless the instructions on this page are followed when creating an account : http://support.apple.com/kb/HT2534
then credit card details will need to be entered before the account can be used to download any item from the store.
If you are getting a prompt to review your account then you could see if this post by mountaingoatgirl lets you do so without needing to enter credit card details : https://discussions.apple.com/message/24303054#24303054
If not then you will need to enter your card details, you should be able to remove them after entering them.

Credit management(Blocking the PGI if due payment is not paid)

Hi,
I have a problem in Problem in Credit control.
I have a customer having credit limit 100 INR
I am creating sales order & in that sales order payment term is Immediate due.Now I Invoiced that order of Rs 50.
Now next day I am creating the another sales order of Rs 10 .But the customer has never paid the amount which is due so I want to block the PGI.Credit limit is still not exhausted but the customer is not paid the due amount so thats why I want to block the PGI.
I have maintain credit group rik cat. & credit control area & do the proper settings .
But it is not blocking the PGI.
Please help me to do that settings
Sunil Garg

Hi sunil,
you have horizion period id there.. pls do that setting, in days/months..in OVA8..
next your update group 000012 in OVA8...
check the open iorder/delieviesr in OVA8..
pls get back if have nay doubts
Reward if it helps
Ramki

Interface with Sales Order to the Credit Management(FSCM)

Hello,
In Our Scenario Sales and Distrubution and Credit management in the Same Sytem and in the Same Client
Can we do the Credit Check from Sales Order Without enbling the XI Interfaces?How?
Thanks.

Hi Guys,
No matter they both exits in same system still you need XI/PI to implement SAP FSCM Credit management. Thats how its designed. after the activation of new Credit management communication happens via PI only.
regards,
--Kathir

Credit management not updated for the first credit blocked order only

Hi experts,
Pls help to solve. Thx.
Case: The first sales order is created against credit block because the credit limit is exceeded. In FD33, no credit data related to the first order indicates, i.e. credit limit used shows zero as well as sales value, credit exposure. In VKM1, the blocked order can be captured.
As long as the second order is created, the credit management can be updated. But, it still does not capture the data from the first order.
The sales orders I test have the same delivery date.
Questions:
1. Is the standard behavior for the dynamic credit check?
2. If not, how to make credit management consider the first order data?
PS. In OVA8, update 000012 is applied while horizon is 4 months.

Hello Jonathan,
After testing, I found credit management can consider the first order data if using 000018 only. Why 000012 cannot consider it?
I have checked the explanation for those two update groups by F4. I feel obscure about the explanation of sales order between them (see below).
000012:
Sales order
Increases open order value from delivery-relevant schedule lines
000018:
Sales order
Increases open delivery value
By the way, my testing data as below:
1. were the two sales orders of the same document type? Answer: yes. Same document type, same customer, same delivery date, etc.
2. were the item categories the same? if not, was one not relevant for credit check? Answer: Yes, the same.
3. did the documents have the same value? if the second order had a lower value and was not blocked for credit, the exposure will be updated. Answer: yes, credit management can consider the second order data ONLY. It seems the first order have not been created if checking credit management.

Credit Management Process based on Terms of Payment.

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

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

Service Interfaces for Credit Management using WS-RM

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

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

Credit management 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 System - Update of SD Documents after CMS start

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

Hi Wojciech
CREDIT MANAGEMENT
Credit and risk management takes place in the credit control area. According to your corporate requirements, you can implement credit management that is centralized, decentralized, or somewhere in between.
An organizational unit that represents the area where customer credit is awarded and monitored. This organizational unit can either be a single or several company codes, if credit control is performed across several company codes. One credit control area contains credit control information for each customer.
For example, if your credit management is centralized, you can define one credit control area for all of your company codes.
If, on the other hand, your credit policy requires decentralized credit management, you can define credit control areas for each company code or each group of company codes.
Credit limits and credit exposure are managed at both credit control area and customer level. You set up credit control areas and other data related to credit management in Customizing for Financial Accounting. The implementation guide is under Enterprise Structure -> Definition or Assignment -> Financial Accounting and then Maintain credit control area. You assign customers to specific credit control areas and specify the appropriate credit limits in the customer master record.
Settings for determining the credit control area of a document. The settings of items 1 - 4 are taken into account according to their priority. The credit control area found is stored in field VBAK-KKBER.
1. Transaction OB38
Check which credit control area is assigned to the company code.
Company code:
Credit control area:
2. Transaction OVFL
Check which credit control area is assigned to the sales area.
Sales area:
Credit control area:
3. Transaction XD02 or VD02
Check which credit control area is assigned to the payer.
Payer:
Credit control area:
4. Transaction SE37
Is user exit EXIT_SAPV45K_001 being used?
5. Transaction OBZK
For the settings under items 2 - 4, field "All company codes" must be marked in Transaction
OB45, or the credit control area must be entered under the relevant company code in table
T001CM of the credit control areas allowed.
Company code:
Credit control areas allowed:
6. Settings for the credit checks
7. Transaction OVAK
Which settings do exist for the sales document type used?
Sales document:
Check credit:
Credit group:
8. Transaction OVAD
Which settings do exist for the delivery type used?
Delivery type:
Credit group for delivery:
Credit group for goods issue:
9. Transaction OB01
Credit management/Change risk category
Definition of the risk category for each credit control area. This risk category can be
assigned to a credit account by using Transaction FD32.
10. Transaction OVA8
Here, the individual credit checks for key fields
o credit control area
o risk category
o credit group are set. Take these key fields from the above settings and go to the detail
screen. In particular, check whether fields "Reaction" and "Status/block" are set
correctly. To carry out follow-up actions in case of a credit block, the credit check
status must be set (field "Status/block").
11. Transaction FD32
Credit master data for the payer of the relevant document.
Credit account:
Credit limit:
Risk category:
Currency:
12. Settings for updating the credit values Update of the credit values is required for the limit
check (static or dynamic credit limit check).
13. Transaction OVA7
Update of the credit value is active for the corresponding item type if the check box is marked. This field corresponds to
field "Active receivable" in Transaction VOV7.
Item type:
Active receivable:
14. Transaction V/08, Pricing
In the pricing procedure used for pricing, subtotal "A" must be entered in a line for
determining the credit value (mark the pricing procedure and doubleclick on "Control").
Usually, the net value plus taxes is used. This way the system is determined to use this
subtotal for credit pricing. The credit price is stored in field VBAP-CMPRE and used for
update and credit check.
You can find the used pricing procedure of the order under "Item -> Condition -> Analysis".
Pricing procedure:
Line with subtotal = 'A':
15. Transaction OB45
Which update group (field "Update") do you use in the relevant credit control area? The
default setting is "12". If you use another update group, check whether this is fine with
you. If you open an OSS message, please tell us the alternative update group.
Credit control area:
Update:
16. Transaction OMO1
Which kind of update did you choose for structure S066?
In any case, "Synchronous update (1)" has to be chosen as the kind of update.
All other settings will lead to errors.
Reward if useful to u

CO-PA, is credit management suppose to block orders from posting to CO-PA?

We are currently using CO-PA to track the $ amount of sales orders that were booked for a particular date range, and it will show the sales order created or changed and the $ amount that was added or taken away from the bookings for that day. This report is to show management how much sales has been recorded for the day, but not necessarily shipped out yet.
What we are currently facing is problems with credit management blocking the order from posting into the CO-PA tables. When the order is created and the order desk hits save it first goes through credit management, and if it is put onto the blocked order lists to be released it does not post the value that was created for that day into CO-PA. Also when we run our rescheduling report for orders that have already been created the order can again go back and forth on and off credit hold, and each time it posts an entry into CO-PA.
I was wondering if anyone has been requested to have a report written to record bookings of sales for a particular day, and have you run into the issue of the credit management posting over and over onto the report and how do you get around this.
We just want to see if any new orders have been created for that day, if current orders have been added on to or taken off from, and have a report to show the order #, dollar value and quantities.
Thank you,
Karen Kim

Dear Karen,
You cannot see blocked SD documents for credit check in CO-PA. Values are transfered to CO-PA after the sales order is processed or after the billing document is posted. So if the sales order is not
processed because it is blocked for credit check, naturally it will not be transfered to COPA. The logic to exempt orders on credit hold was implemented in release 40A.
To overcome your problem you may implement the modification described in the note 214059. Please be aware that this is a modification note. Please implement in a development environment first and retest.
regards
Waman

Implementing Credit Management without the SD module

Similar Messages

Maybe you are looking for