Tables of credit Management

HI!!,
Please let me know list of tables in Credit management.
-AKASH

Hi Akash Tambi
T691F Control of Automatic Credit Control
KNKA Customer master credit management: Central
KNKK Customer master credit management: Control
KNKKF1 Credit Management: FI Status Data
KNKKF2 Credit Management: Open Items by Days in A
KLPARAM Credit Limit: Tab for Controlling Ext. Def
KLSDCPARAM Credit Limit: Controlling External Default
UKM_TRANSFER_AR Data from AR for SAP Credit Management
UKM_TRANSFER_ARV Data from AR for SAP Credit Management
VBKK SD Doc.Export Letter of Credit
VBUK Sales Document: Header Status and Administ
VBUP Sales Document: Item Status
T014 Credit control areas
T014N New credit control areas to be set up
T014T Credit control area names
T024B Credit management: Credit representative g
T024P Credit Management: Credit Representatives
T042U Block Entries for Debit Customers/Credit V
T5UDO Benefit credit grouping
Reward if useful to u

Similar Messages

Open Billing Doc value table in Credit management

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

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

Tables for Collection, dispute and credit management

Hi SAP Gurus,
I would appreciate if any one could provide the list of tables for collection, dispute and credit management. Thanks!
Regards,
aj

I think you mean the tables for FSCM.
The easiest way to find it is to do SE16 FDM*
FDM_AR_WRITEOFFS               FSCM-DM: Automatic Write-Offs Not Executed
FDM_BUFFER                     Cluster for Decoupling in 1-System Scenari
FDM_BW_INV_DELTA               Delta Queue for BI Invoice Extractor
FDM_COLL_CCOLOAD               Company Codes for which Initial Load Perfo
FDM_COLL_CFIELD                FSCM-COL: Relevant Fields for Document Cha
FDM_COLL_COMPCOD               FSCM-COL: Active Company Codes of Collecti
FDM_COLL_DUNNLEV               Harmonized Dunning Levels
FDM_COLL_LASTPAY               Last Payments of Business Partner
FDM_COLL_LTRIG                 Missing Entries of Table FDM_COLL_STRIG
FDM_COLL_SFIELD                FSCM-COL: Relevant Fields for Document Cha
FDM_COLL_STRIG                 FSCM-COL: Control of Trigger Update in TRO
FDM_COLL_TROBJ                 FSCM-COL: Trigger Table for Collections Ma
FDM_CONTACT_BUF                Personalization of Contact Person Data
FDM_DCOBJ                      FSCM-DM Integration: Disputed Objects
FDM_DCPROC                     FSCM-DM Integration: Dispute Case Processe
FDM_P2P_ATTR                   Attributes of Promise to Pay; Required for
FDM_PERSONALIZE                Personalization of Collections Management
FDM1                           Cash Management & Forecast: Line Items of
FDM2                           Cash management line items from MM purchas
FDMV                           Cash Planning Line Items of Earmarked Fund
Hope this helps, award points if useful.

Risk category field is missing in dso for 0fiar_o09 credit management.

Hi BI Experts,
I am using the standard extractor for the credit management dso 0fiar_o09. The field for risk category originates from our R3 system in table knkk-ctplc. It displays correctly in the psa. The transformation rsds 0fi_ar_9 maps it to 0risk_categ. It appears as an infoObject in the infoSource. The trcs transformation maps the rule also.
However, when I try to display the data in the dso, the risk category field does not display at all.
Please help with any possible suggestions to display the missing field.
Kind regards,
Cheryl Adamonis

I resolved this issue by removing the check in the 'attribute only' selection on the general tab of the infoObject.

Open Sales Order Values in Credit Managment

Hi,
1. I want to include the open sales orders that were created before implementing the functionality of Credit Managment. How to check the credit limits for that sales orders.
Fro Example. If i want do the credit checks for 1000 open sales orders.
2. How to reset the customer credit limit in FD32. I tried using the t.code f.28, but it will not be reset to zero(0).
Thank you,
Ravi

Hello Ravi,
You can try this: in table VBAK, you might have the date when this a particular order was created( ERDAT or sometihng like that..). You'll have to join table VBAK/VBAP/VBRK(billing table)/VBFA and the logic should be that the program should pick up all the orders created before 1 yr and should also check that the items are not rejected, and the delivery not yet created.
Check the following fields:
VBAK-ERDAT, VBAP-ERDAT, VBAP-ABGRU, VBAP-AEDAT.
Regards,
Raghu.

Open Delivery value update error in credit management

Hi
We have credit management active at delivery level. The value of open deliveries is not getting updated correctly for items with material substitution (material determination). For all other items, its getting updated correctly.
E.g Let say the credit limit set in FD32 is 10000 and the credit limit used % is 98 and the credit exposure value is 9800.
Now when I create an order with qty 10 for mat A, it creates a sub item B due to material determination and the value of the item is Rs.1200. In our system, the sub item with TAPS item category is relevant for pricing.
Then I create a delivery in VL01N and save it.
Now if i check in FD33, the credit limit used should be 101% and the credit exposure value should be 11000, but its not updating the open delivery value correctly. Its not considering the value of the new delivery.
However, If I add a normal item (TAN) in the same sales order and create a delivery for that item and save it, its updating the credit exposure based on the value of the normal item in the delivery correctly.
How to make the system update the open delivery values correctly by taking the items with material determination also into account.??
Please advise if any specific settings need to be done.
Regards
Madhu

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

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

Credit Management with Letter of Credit.

Hi Gurus,
We need to consider the "Letter of Credit" amout in credit management.
ie. if there is LC created on customer worth Rs. 5lacs, system should not block the sales order unless 5 lacs is consumed.
Pls suggest any workarounds.
Reg.
Amol

Dear Amol Tamhane,
Have not worked on 'letter of credit'.
But if there is any accounting document which gets created due to letter of credit, then you can use the exit for credit management in SALES ORDER LEVEL and write the code to BLOCK THE SALES ORDER ONLY IF
(CREDIT LIMIT + LETTER OF CREDIT AMOUNT ) - (PREVIOUS EXPOSURE + SALES ORDER VALUE ) < 0
You can check BSEG, if accounting document gets created for 'letter of credit' or you can check any tables related to letter of credit based on customer code.
Thanks & Regards,
Hegal K Charles

Configuring SAP Credit management interfaces in PI 7.0

Hi all,
I am working on PI 7.0 instance and have an issue while trying to connect Accounts receivable accounting with SAP Credit Management.
Did anybody configure this kind of interfaces (Credit cOMMITMENT & Credit Payment) so that they could be integrated with PI?
If so, could you please tell me the steps to configure the mappings and CCs in IR and ID?
i am following SAP Credit mngmnt config guide, but there is no info regarding this.
TCODES are: UKM_TRANSFER_ITEM & UKM_TRANSFER_VECTOR
Best regards,
David

try sapsr3.<table> instead of sap<sid>
SAPSR3 is the schema now. Once lock is removed , try to login with sap*/ddic with master password which you gave while installing.
Thanks
Prince Jose

Regarding open items in credit management

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

Hi,
All business have their own credit management needs, SAP allows you to specify your own automatic credit checks based on a variety of criteria. You can also specify at which critical points in the sales and distribution cycle the system carries out these checks.
SM30 - Table/View
V_TVTW Define Distribution Channel
V_TVTA_KKB Assign sales area to credit control area
V_T014 FI - Define Credit Control Area
T001CM - FI Assign Permitted Credit Control Area to company code
OVXG - Set up Sales Areas
e.g. Sales Organization
Distribution Channel Division Distribution Channel Division
FD32 - Customer Credit Management
OVAK - Define credit limit check by sales document type
Check Credit
A Credit limit check and warning message
B Credit limit check and error message (no sales order can be created)
C Credit limit check and delivery block (block delivery if hit credit limit)
Options B and C -> used for checking open order values (when you create/change the sales order)
D Automatic credit control with open order values
More control in transaction OVA8 - Automatic credit control
You check for open orders and deliveries, or just open deliveries.
or open order values with other options
Credit group
Allows you to combine different sales document types for the credit limit check
VKM1 - Blocked SD Documents Finance have to released the delivery block
OVAD - Define credit limit check by delivery order
whether the automatic credit check occurs at the time of delivery creation and/or goods issue
OVA7 - Define credit limit check by item category
Set whether to include/exclude item category for credit limit check
OVA6 - Define credit group. You can groups together different business transactions which should be dealt with in the same manner with regard to the credit check.
You enter the credit groups when you configure the sales document types for credit management and define the (D automatic credit check).
SAP default credit groups
01 credit group for sales order
02 credit group for delivery
03 credit group for goods issue
OVA8 - Automatic credit control Double click on the line items
You can have the followings credit limit check :-
Static
Depends on the customer total value of open orders, deliveries, billing documents and open items.
Open items
No of days open
Overdue open items checks is based on the ratio of open items that are overdue by a certain number of days.
Max open items %
The customer balance must not exceed a certain percentage.
Oldest open items
If you dont want to deliver to the customer at all when even only 1 invoice is overdue.
Tick the Check for Oldest Open Item and Set the field Days oldest item = 1.
Days oldest item
No of days allowed for overdue or payment terms.
Use of the credit check Oldest Open Item. If a user attempts to alter the order quantity of a released sales document
that was previously blocked, it would be reblocked again by the system. The system only reblocks the sales document if the new order quantity is above a certain % amount.
Released documents are still unchecked
The preset % is whatever you want to set it as when configuring your automatic credit processing. You enter a deviation % and number of days,eg, you can set it so that an order can be changed by up to 10% within 30 days of original order entry date without it going back on credit block.
Next Review Date
If a customer has a credit limit of 1000 USD, and you would like to restrict this credit limit only to be available in current month (say March). If the document day is in April then the credit limit is zero.
You can use the NextReview date and Number of days fields and combined it with the Last int.review field in customer credit master Status view (FD32).
VOKR - Display of work list for credit management (configure the display variant)
regards,
Siddharth.

Table for credit limit for risk category for all CCA

Hi All,
I want to know in which table I can see default credit limit which is associated to particular risk category for all credit control area.
Regards
Nidhi

Hi Nidhi Srivastava,
Check in SE16
KNKA - Customer Master Credit Management
KNKK - Customer Master Credit Control Area Data (credit limits)
Regards
Pradeep

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

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

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

Credit management urgent

Dear sap gurus,
after implementing credit management in middle or not from beginning and if you want to have the history a particular customer updated in LIS or if we want to know about his credit exposure.
What should be done.Kindly help me.
regards,

How To Do Configuration For Credit Management
Credit and risk management takes place in the credit control area. According to your corporate requirements, you can implement credit management that is centralized, decentralized, or somewhere in between.
An organizational unit that represents the area where customer credit is awarded and monitored. This organizational unit can either be a single or several company codes, if credit control is performed across several company codes. One credit control area contains credit control information for each customer.
For example, if your credit management is centralized, you can define one credit control area for all of your company codes.
If, on the other hand, your credit policy requires decentralized credit management, you can define credit control areas for each company code or each group of company codes.
Credit limits and credit exposure are managed at both credit control area and customer level. You set up credit control areas and other data related to credit management in Customizing for Financial Accounting. The implementation guide is under Enterprise Structure -> Definition or Assignment -> Financial Accounting and then Maintain credit control area. You assign customers to specific credit control areas and specify the appropriate credit limits in the customer master record.
Settings for determining the credit control area of a document. The settings of items 1 - 4 are taken into account according to their priority. The credit control area found is stored in field VBAK-KKBER.
1. Transaction OB38
Check which credit control area is assigned to the company code.
Company code:
Credit control area:
2. Transaction OVFL
Check which credit control area is assigned to the sales area.
Sales area:
Credit control area:
3. Transaction XD02 or VD02
Check which credit control area is assigned to the payer.
Payer:
Credit control area:
4. Transaction SE37
Is user exit EXIT_SAPV45K_001 being used?
5. Transaction OBZK
For the settings under items 2 - 4, field "All company codes" must be marked in Transaction
OB45, or the credit control area must be entered under the relevant company code in table
T001CM of the credit control areas allowed.
Company code:
Credit control areas allowed:
6. Settings for the credit checks
7. Transaction OVAK
Which settings do exist for the sales document type used?
Sales document:
Check credit:
Credit group:
8. Transaction OVAD
Which settings do exist for the delivery type used?
Delivery type:
Credit group for delivery:
Credit group for goods issue:
9. Transaction OB01
Credit management/Change risk category
Definition of the risk category for each credit control area. This risk category can be
assigned to a credit account by using Transaction FD32.
10. Transaction OVA8
Here, the individual credit checks for key fields
o credit control area
o risk category
o credit group are set. Take these key fields from the above settings and go to the detail
screen. In particular, check whether fields "Reaction" and "Status/block" are set
correctly. To carry out follow-up actions in case of a credit block, the credit check
status must be set (field "Status/block").
11. Transaction FD32
Credit master data for the payer of the relevant document.
Credit account:
Credit limit:
Risk category:
Currency:
12. Settings for updating the credit values Update of the credit values is required for the limit
check (static or dynamic credit limit check).
13. Transaction OVA7
Update of the credit value is active for the corresponding item type if the check box is marked. This field corresponds to
field "Active receivable" in Transaction VOV7.
Item type:
Active receivable:
14. Transaction V/08, Pricing
In the pricing procedure used for pricing, subtotal "A" must be entered in a line for
determining the credit value (mark the pricing procedure and doubleclick on "Control").
Usually, the net value plus taxes is used. This way the system is determined to use this
subtotal for credit pricing. The credit price is stored in field VBAP-CMPRE and used for
update and credit check.
You can find the used pricing procedure of the order under "Item -> Condition -> Analysis".
Pricing procedure:
Line with subtotal = 'A':
15. Transaction OB45
Which update group (field "Update") do you use in the relevant credit control area? The
default setting is "12". If you use another update group, check whether this is fine with
you. If you open an OSS message, please tell us the alternative update group.
Credit control area:
Update:
16. Transaction OMO1
Which kind of update did you choose for structure S066?
In any case, "Synchronous update (1)" has to be chosen as the kind of update.
All other settings will lead to errors.
Difference Between Simple and Automatic Credit Check Types
In automatic check, difference between static and dynamic checks.
SIMPLE CREDIT CHECK : Tr.Code - FD32
It Considers the Doc.Value + Open Items.
Doc.Value : Sales Order Has been saved but not delivered
Open Item : Sales Order has been saved , Delivered, Billed & Transfered to FI, but not received the payment from the customer.
Eg: Customer Credit Limit is Rs.1,00,000/-
Suppose Doc.Value + Open Item Value is Rs.1,10,000/-
Here credit limit exceeds then system reacts.
Options : A) Warning Message
B) Error Message (Sales Order won't be saved)
C) Error Message with Delivery Block
AUTOMATIC CREDIT CHECK : Give extra credit facilities to the particular customer.
STATIC CREDIT LIMIT DETERMINATION :Checking Group + Risk Catageory + Credit Control Area.
A) Credit Checking Groups : Types of Checking Groups.
01) Sales
02) Deliveries
03) Goods Issue
At all the above 3 levels orders can be blocked.
B) Risk Catageory : Based on the risk catageories company decide how much credit has to give to the customer.
HIGH RISK (0001) : LOW CREDIT
LOW RISK (0002) : MORE CREDIT
MEDIUM RISK(0003) : Average Credit
Static Credit Check it checks all these doc value & check with the credit limit
1) Open Doc.Value / Sales Order Value : Which is save but not delievered
2) Open Delivery Doc.Value : Which is delivered but not billed
3) Open Billing Doc.Value : Which is billed but not posted to FI
4) Open Item : Which is transfered to FI but not received from the customer.
DYNAMIC CREDIT CHECK : 1) Open Doc
2) Open Delivery
3) Open Billing
4) Open Items
5) Horizon Period = Eg.3Months
Here the System will not consider the above 1,2,3& 4 values for the lost 3 months
Then assign the Sales Doc & Del Documents.
Sales Doc.Type(OR) + credit Check(0) + Credit Group (01)
Credit Limit Check for Delivery Type : Del.Type (LF) + Del Credit
Group (02) + Goods Issue Credit Group (03)
Set Up for Credit Card Payment Processing
Given below is the set up for credit card payment processing:
Set Up Credit Control Areas:
Define Credit Control Area
Transaction: OB45
Tables: T014
Action: Define a credit control area and its associated currency. The Update Group should be u201800012u2019. This entry is required so the sales order will calculate the value to authorize
Assign Company Code to Credit Control Area
Transaction: OB38
Tables: T001
Action: Assign a default credit control area for each company code
Define Permitted Credit Control Area for a Company
Code
Transaction:
Tables: T001CM
Action: For each company code enter every credit control area that can be used
Identify Credit Price
Transaction: V/08
Tables: T683S
Action: Towards the end of the pricing procedure, after all pricing and tax determination, create a subtotal line to store the value of the price plus any sales tax. Make the following entries:
Sub to: u201CAu201D
Reqt: u201C2u201D
AltCTy: u201C4u201D
Automatic Credit Checking
Transaction: OVA8
Tables: T691F
Action: Select each combination of credit control areas, risk categories and document types for which credit checking should be bypassed. You need to mark the field u201Cno Credit Checku201D with the valid number for sales documents.
Set Up Payment Guarantees
Define Forms of Payment Guarantee
Transaction: OVFD
Tables: T691K
Action: R/3 is delivered with form u201C02u201D defined for payment cards. Other than the descriptor, the only other entry should be u201C3u201D in the column labeled u201CPymtGuaCatu201D
Define Payment Guarantee Procedure
Transaction:
Tables: T691M/T691O
Action: Define a procedure and a description.
Forms of Payment Guarantee and make the following entries Sequential Number u201C1u201D
Payment Guarantee Form u201C02u201D
Routine Number u201C0u201D Routine Number can be used to validate payment card presence.
Define Customer Payment Guarantee Flag
Transaction:
Tables: T691P
Action: Define a flag to be stored in table.
Create Customer Payment Guarantee = u201CPayment Card Payment Cards (All Customers can use Payment Cards)u201D.
Define Sales Document Payment Guarantee Flag
Transaction:
Tables: T691R
Action: Define the flag that will be associated with sales document types that are relevant for payment cards
Assign Sales Document Payment Guarantee Flag
Transaction:
Tables: TVAK
Action: Assign the document flag type the sales documents types that are relevant for payment cards.
Determine Payment Guarantee Procedure
Transaction: OVFJ
Tables: T691U
Action: Combine the Customer flag and the sales document flag to derive the payment guarantee procedure
Payment Card Configuration
Define Card Types
Transaction:
Tables: TVCIN
Action: Create the different card types plus the routine that validates the card for length and prefix (etcu2026)
Visa , Mastercard, American Express, and Discover
Create the following entries for each payment card
AMEX American Express ZCCARD_CHECK_AMEX Month
DC Discover Card ZCCARD_CHECK_DC Month*****
MC Mastercard ZCCARD_CHECK_MC Month
VISA Visa ZCCARD_CHECK_VISA Month
The Routines can be created based on the original routines delivered by SAP.
*****SAP does not deliver a card check for Discover Card. We created our own routine.
Define Card Categories
Transaction:
Tables: TVCTY
Action: Define the card category to determine if a
payment card is a credit card or a procurement card.
Create the following two entries
Cat Description One Card Additional Data
CC Credit Cards No-check No-check
PC Procurement Cards No-check Check
Determine Card Categories
Transaction:
Tables: TVCTD
Action: For each card category map the account number range to a card category. Multiple ranges are possible for each card category or a masking technique can be used. Get the card number ranges from user community. Below is just a sample of what I am aware are the different types of cards.
Visa Credit Expires in 7 days.
400000 405500
405505 405549
405555 415927
415929 424603
424606 427532
427534 428799
428900 471699
471700 499999
Visa Procurement Expires in 7 days.
405501 405504
405550 405554
415928 415928
424604 424605
427533 427533
428800 428899
Mastercard Credit Expires in 30 days
500000 540499
540600 554999
557000 599999
Mastercard Procurement Expires in 30 days
540500 540599
555000 556999
American Express Credit Expires in 30 days
340000 349999
370000 379999
Discover Card Credit Expires in 30 days
601100 601199
Set Sales Documents to accept Payment Card Information Transaction:
Tables: TVAK
Action: Review the listing of Sales Document types and enter u201C03u201D in the column labeled u201CPTu201D for each type which can accept a payment card
Configuration for Authorization Request
Maintain Authorization Requirements
Transaction: OV9A
Tables: TFRM
Action: Define and activate the abap requirement that determines when an authorization is sent. Note that the following tables are available to be used in the abap requirement (VBAK, VBAP, VBKD, VBUK, and VBUP).
Define Checking Group
Transaction:
Tables: CCPGA
Action: Define a checking group and enter the
description. Then follow the below guidelines for the remaining fields to be filled.
AuthReq Routine 901 is set here.
PreAu If checked R/3 will request an authorization for a .01 and the authorization will be flagged as such. (Insight does not use pre-authorization check).
A horizon This is the days in the future SAP will use to determine the value to authorize
(Insight does not use auth horizon period).
Valid You will get warning message if the payment card is expiring within 30 days of order entry date.
Assign Checking Group to Sales Document
Transaction:
Tables: TVAK
Action: Assign the checking group to the sales order types relevant for payment cards
Define Authorization Validity Periods
Transaction:
Tables: TVCIN
Action: For each card type enter the authorization validity period in days.
AMEX American Express 30
DC Discover card 30
MC Master card 30
VISA Visa 7
Configuration for clearing houses
Create new General Ledger Accounts
Transaction: FS01
Tables:
Action: Two General Ledger accounts need to be created for each payment card type. One for A/R reconciliation purposes and one for credit card clearing.
Maintain Condition Types
Transaction: OV85
Tables: T685
Action: Define a condition type for account determination and assign it to access sequence u201CA001u201D
Define account determination procedure
Transaction: OV86
Tables: T683 / T683S
Action: Define procedure name and select the procedure for control. Enter the condition type defined in the previous step.
Assign account determination procedure
Transaction:
Tables:
Action: Determine which billing type we are using for payment card process.
Authorization and Settlement Control
Transaction:
Tables: TCCAA
Action: Define the general ledger accounts for reconciliation and clearing and assign the function modules for authorization and settlement along with the proper RFC destinations for each.
Enter Merchant IDu2019s
Transaction:
Tables: TCCM
Action: Create the merchant idu2019s that the company uses to process payment cards
Assign merchant idu2019s
Transaction:
Tables: TCCAA
Action: Enter the merchant idu2019s with each clearinghouse account
Reward points if useful.
Regards,
Anbu

Complete End User transactions of Credit management and Cash Remittance

Hi All
Can any one please Guide me on what are all transactions the end users need to perform in the below areas -
1 - Collections
2 - Credit Management
2 - Cash Remittance
4 - Tax Processing
I have to give the trainings on these areas and these are very much new areas to me
Appreciate your Quick Response
Aadi
Moderator
http://help.sap.com/saphelp_erp60_sp/helpdata/en/d2/9202b646f111d189430000e8323c4f/frameset.htm

Hi,
You got this message because you set check for "Permitted aging of A/R summary" on OVA8. And you also chose to create AR summary on table T000CM.
You can do one of following:
1. on OVA8, make "permitted days and monthes" blank.
2. delelte entries in table T000CM
3. Make "permitted days and monthes" longer, and delete and re-create AR summary by FCV2 and FCV1.
Hope it helps.

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

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

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

Tables of credit Management

Similar Messages

Maybe you are looking for