Authorization control in Credit Managment

In Credit Management, I want to control the Check box Blocked for certain users in FD32. Let me know if any authorisation mechanism to access the change/display according to specific Users.

Dear:
Ask you Basis consultant to implement authorization's checks against F_KNKA_AEN (Credit Management: Change Authorization for Certain Fields) for this Transaction code for the user profiles as desired by you. Before that do the necessary customization in SPRO as follows:
Define your change groups in the task level menu of Financial Accounting >A/R & A/P -> Credit management -> Define Field group-> Assign Fields -> Groups.
While assigning you can find the field KNKK-CRBLB (Blocked) .
Regards

Similar Messages

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

Credit management automatic credit control use of credit group

Hello gurus
1)In the credit management we have credit groups( which enables us to combine different sales
document types for the purposes of credit management).
In the simple credit check also we will assign the doc types to check the credit. Then please tell me why we need credit groups in automatic credit control? Here also we can assign the doc types to check the credit ?then what exactly is the use of credit group ?
2)where will we specify the total credit amount allowed of the credit control area?
3)In the automatic credit control (ova8) against to static check box option we have open orders and open delivers checkboxes. is this two boxes only specific to static or it also belongs to dyanic?
Is it necessary to check this boxes?
4)is any one have used any of the routines in automatic credit control( document controlling tab we have no credit check field here we specify the routine? If any business need please share with me
Thank you in advance for all the replies

Hi
For your 1st query , In credit mgmt we assign credit grps to sales document type. So as you said we will assign credit grps at simple credit check and coming to the Automatic credit check we assign credit grp for the sales document type also .But the difference is credit grp can be at order level or Delivery Level or PGI level in OVA8 in Automatic credit check .
Coming to your 2nd Query , we will specify the total credit limit in FD32.
For your 3rd query , In OVA8 apart from the static check we check the boxes open orders and open deliveries also because once you activate Automatic credit check and once you maintain credit limit for any customer then system will check the open orders and open deliveries also of that customer
Coming to your last query the routine feild can be used when some requirements have to be fulfilled then only automatic credit check should work for customers. or else the sales order ->delivery->PGI will happen normally
Regards
Srinath

Credit management Authorization Based on Value.

Hi All,
Can help me out to find whether we can implement Credit management based on different level of Values or not.As i know we can do authorization based on % like 100%, 110% etc.
But i want to activate release authorization based on the Amount like
level 1 Rs 1 lakh( Can release upto 1 lakh) when it reaches to above of 1 lakh
level2 Rs 2 lakh ( it will release upto 2 lakh)
like wise.As what i understand whatever the standard roles are given relevant to % basis only.

hello, friend.
yes, you can do this in a few ways...
1. try 'Document Class' - a document class is assigned a certain value, which is assigned to a user (the link to credit management is indirect)
2. the traditional way is to use 'Risk Category', and you can set specific values (e.g. maximum document values) when doing OVA8.
i seem to recall there may also be a way to assign values to risk category, but i will check on this.
regards.

Credit Management control

I am having this senario...
Our Credit management system was just configured / activated on the month june this year.
When I run T. code VKM4, found out there are credit values from the transaction of the previous closed fiscal year. If I want Credit Mgt system to only monitor / capture values of delivery,invoices, receivable from the date of activation of the Credit Mgt, is there any setting to control this?
Thanks you
Rgds
Henery

hello, friend.
in VKM4 you can specify the credit status (enter required status), document status (enter A to C) and/or delivery date. doing this, you can limit the list to your requirements.
however, you cannot display invoices directly in this transaction.
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 - Maximum time overdue limit for open item

Dear all,
I've this scenario to configure for automatic credit control. A customer is billed on Jan 22nd '10 and now the account receiveable shows an open item. This customer is allowed 52 calendar days to make payment for this invoice, hence no credit block yet. As such, the customer can still make orders.
In my existing configuration, I've already enable "static" credit check on "open orders" and "open deliveries". The static check is to check against the customer's credit limit.
So, if I were to add in the earlier mentioned overdue open items check, is it sufficient to just maintain the field "Days oldestItem" with "52" within the automatic credit control screen?
Thanks.
Steven

Hi
The sytstem will shows oldest open items depending on the payment terms from the invoice date.
Once it crosses the days of payment then it will show in oldest open items
if you want to extend some more days for that then you need to maintain the days in "Days oldestitem" the automatic credit control area
Prerequisites for credit management to work in Sales and Distribution:
1.Assign credit control area to company code
2.Maintain the credit limit in FD32 with details of risk category and the credit limit value
3.Do the settings in OVA8 -automatic credit control area with combination of Credit control area/Risk category /credit group.
4.Assign the credit groups to the sales and delivery document types.
5.Maintain the Subtotal 'A' in the pricing procedure against which value the sytem should check the credit limit.
If you have any further clarifications on above let me know
Regards
Damu

Credit Management requirement for cash business

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

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

Credit Management: How to include back orders value in credit exposure?

Hello,
We have to have credit management implemented for some sales order types.
Credit exposure is working fine with normal sales orders.
But credit exposure is not taking into consideration the value of backorders which are present prior to credit management was implemented (with horizon period of 2 months).
Please let me know how we can include the value of back orders in credit exposure?
Thanks in advance for your answer.
Mallik

hi
goto OVAD
assign delivery type with dly credit group 02, GI credit group 03. s ave
goto OVAk
assing order type with check credit D credit group 01
goto OVA8 double click on relevant credit control
field Oldest open item select it, then Days oldest item assign value
regards
[email protected]

Credit management and credit exposure

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

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

AR Report Requirement - Customer Credit Management - 0FI_AR_9

HI There,
We have a requirement in AR report to add the below fields from Customer Credit Management Datasource 0FI_AR_9
KNKLI - Credit Control Account- 0CRED_ACCNT
KLIMK - Credit Limit - 0CRED_LIMIT
CTLPC - Risk Category - 0RISK_CATEG
Except KNKLI (Credit control account), remaining two fields are master data.
Can we use the data from 0FI_AR_9 by writing look up? Please suggest.
Thanks
Vandana

Hi,vandana_ir
i don't know what's your requirement else,if you wanna add those fields to the report
those below solution may be can help you
1.data loading into InfoObject etc.0customer
2.using virutal key figure tech to read customer value from infoObject.

Update Credit managment dispay in some of the orders with same Payer

Hi,
I have some sales orders created with same PO, same sold to party and same payer. In one of the Sales Order
credit control area and credit account is updated but the other order's did not update with this information.
I can see the Credit account dispay in that Sales Order which got updated but the other orders are giving the message "Cannot display credit limit as no credit management account is available"
Please let me know how to fix the other Sales orders Credit accounts, these all orders have same Payer and we have issue in the Consolidate billing of these orders and all these orders have subsequent documents like Delivery and Invoice.
VBAK-KKBER and VBAK-KNKLI fields are blank in these Orders except the one which got updated.
Thanks in advance.
- Fract

Hi Charles,
The Order with values filled in VBAK-KKBER and VBAK-KNKLI is not a latest order, We have orders after and before this order also.
I already executed F.28 but nothing got changed.
Regards,
Fract
Edited by: fract_get on Nov 15, 2011 10:26 PM

Credit Managament: avoid credit block for down payment invoices

1) Downpayment - when an order is blocked, can we create a billing
document of the downpayment request created in slaes order. Logically
the customer wants to pay for this downpayment immediately and process
the order
Notes: If credit management is activated at sales order level and In
Milestone Billing scenario or Project Sales order scenario, at Sales
order level we have a Downpayment (Z0000 - Downpayment) Milestone
usage and Other Milestone invoice Usages.
The business requirement is Customer need to pay the downpayment
invoice before executing the Sales order.
In SAP when the Sales order is blocked for Credit Management, system is
not able to create the Downpayment invoice also. to creat the invoice
we have to release the order first. However we dont want to release the
order but want to receivce the downpayment and then may be we can
manually release the order and process. The reason is suppose we have
an automatic release to production or PR or creation of service order,
we would like to process them only after the downapayment, now for
creating the wownpayment invoice for receiving the downpayment, we have
to release the order which shall further process the order
automatically. Please suggest a solution for the same to avoid the
credit block for the Downpayment invoices.

I think this can be enabled easily.
For the combination of Credit Control Area, Credit Group and Risk Category, you should have enabled the Dynamic/Static credit check, you can configure it such a way that it only gives you a warning message and doesnot block your sales order. This should solve ur problem

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

Arrear after net due date - FD33 Credit Management

Arrears after net due date is not appearing in the payment history of FD33 customer credit management report(it is showing as zero days), bur the same is appearing in the FDL5N report.
The credit control area and payment terms are same as other customer wherein the arrear days are getting appear properly

Hi,
I moved your question tnto this forum.
Mario

Authorization control in Credit Managment

Similar Messages

Maybe you are looking for