Grace period in Credit Management

Hi All,
Can any one let me know how are grace periods in Risk categories maintained in Credit Management .
For Instance Low risk category:5days
Medium Risk Category :2days
And where does the effect can be seen ?
Regards,Rajneesh

Hi...
Grace periods are configured based ipn risk category. Risk category is alloacted to the customer based on his past history. Like you dont want to block the customer who has good credit history but could not pay his last invoice on time and you want to give him 7 days grace period rather blocking the deliervy for the same.

Similar Messages

Credit Terms with Grace Period in Credit Management -

Team,
I want to know how to define the following:
Credit Terms: Net 30 days
Grace Period: 5 days
The systems should not put Sales Orders on 'credit hold' upto 35 days. On the 36th day (and beyond) Sales Orders should be put on 'credit hold' by the system.
Please let me know where and how to configure above scenario in R/3.
Thanks

Hi Reji,
To achieve this, you assign two different credit control areas to two different sales areas. Then in "OVA8" you maintain the horizon period differently.(You can maintain in days aswell). and you maintain the overall credit limit as it is in the Customer Credit Master record (FD32) .This should solve the problem.
Regards
Ram Pedarla

How can we change horizone period from Months to days in credit management

Hi SAP SD gurues,
                              Can anybody tell the procedure "how to change Horizone period from months to days in credit management in "OVA8" . As you may get month is greyed out in horizone period settings. Advance Thanks with warm regards.
                                                                      Kartik

Dear Sadhu,
                  Sorry still i am not satisfied with your answer.As you hav told to go through the TC OVBI, there i found it is no where or little related to Horizon period of Credit management of SD module. In OVBI it is meant for "Maintain Billing plan type for Period Billing". Yes there is a combo box called "HORIZON", but i believe the purpose of this Horizon is diffrentthan the "Horizon period in SD Credit management. Pls correct me and explain me how it is related if i am wrong. Hope you'll do so.Thanks for yr valuable reply.Kartik...

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]

List of released sales orders which were blocked during credit management

If sales order is blocked during credit management, then it is released by Authorised person using VKM3 Tcode. Further if we want to see list of released documents, VKM2 shows the same. However VKM2 does not shows the released documents once that are billed (using VF01). Suppose post billing one wants to see how many orders were released during specific period, how it can be seen. Is there any transaction code to see such records.
Vijay

You can use V.23 to view the report. The report will show you what sales order is ready for release for billing.

Credit management requirement

Hi,
Guys i have the b/m requirement w.r.t. credit management.
i am very confused on the same.
-.The credit period of 45 days from the date of placing the order(i.e sales order) will be admissible to the customers of the company.
-. Customer will be required to issue a post-dated cheque on the due date of payment for 95% value of the order.
& The order will be taken for production by the plant only after post dated cheque for 95% value of the order has been received by the branch and confirmed to Head Office.
-.The balance amount against the supplies received by the BP against the purchase order shall be payable after the receipt of the goods by him. This outstanding amount shall be a part of credit limit.
-.At no given time the total credit exposure (including the value of post dated cheque) against BP shall exceed 50% of the invoice value to him in preceding 90 days. In case the business partner has already utilized the credit limit agreed for him, the supplies will be made against cash payment only.
-.If any payment is received from BP in less than 45 days, he shall be entitled for credit note @ 1.5% per month.
CAN ANYBODY HELP ME TO MAP THE SCENARIO IN SAP ON THE SAME.
Rgds

Hi,
For credit period of 45 days. configure payment terms.
SAP does not have a solution for post dated cheques. However you can use F-49 - Noted Items for post dated cheques.At the end of due date, use F-28 - incoming payments.
For Credit Limit, Configure Credit Management,Refer to this website.
http://www.sap-img.com/sap-sd/credit-management.htm
In case of cash payment, you can use F-28 or F110, you have to use cash GL Account.
Please let me know if you need more information.
Assign points if useful.
Regards
Sridhar M

Credit managment against payment terms and credit limit

Dear All,
I have two query against credit management
1 Can We maintain credit managment as per payment days. My client want system should give bolck as per payments days,say if payment terms is 30 days and within 30 days customer has not made payment against invoice so sales order should block. ( sales order will create but shown as block)
2 Credit block with ref to credit limit given to customer, they want credit block with reference to open order.open delivery and open invoice. Means system will check all open order,all open deliveries and all open invoice while considering credit limit.and give the block accordingly.
I am sure about credit limit but how to give block according to payment days (payment terms) and how to give path to check all open order,all open deliveries and all open invoice.
waiting for you valuable input.
Thank you
SD Consultant

Hello,
In OVA8, for the combination of credit group & risk category you maintain the following
(1) CHECK against DYNAMIC with reaction C & TICK in BLOCK
NOTE:path to check all open order,all open deliveries and all open invoice is maintained in OB45 (update 000012)
(2) CHECK against OLDEST OPEN ITEM with reaction C & TICK in BLOCK
(do not maintain any value in DAYS OLDEST ITEM, but maintain the payment terms in the Customer master)
for example, block as per payments days,say if payment terms is 30 days and within 30 days customer has not made payment against invoice so sales order will be blocked.
In both the cases ( credit limit and credit period,the sale orders blocked , can be released by VKM3.
Regards,
Hegal

Link between Payment Terms and Credit Management .

Hi Friends
Where and how does Payment Terms interact with Credit Management ? Is it with Horizon date or open items check ?
Regards
Mahesh

Hi
Payment terms means the time given to a customer or vendor to pay the value of goods.
credit management is used to check whether the customer has excedded his credit limit given to him.
An agreement the company has with its customers or vendors, including:
Payment period
Price list
Total discount in the document
This information is used to calculate prices for the items; the due
dates of invoices and the total discount.
A key functional area of mySAP CRM that provides credit check with use of information about payment history and credit risk analysis.
Please let me know if you need more information.
Assign points if useful.
Regards
Sridhar M

How to determine the week for credit management?

Is there a transaction that will show the week for which credit is determined. For example, when running RVKRED88, it shows the week the order is processed under.

Hi Rocha,
In Credit management S066 and S067 information structures play a vital role in updating the credit values of a customer. This works in tandem with the update group present in the OVA8 settings in case of automatic credit check.
When an order is created S066 information structure and OEIKW field is updated which increases open order value. when order is delivered S067 information structure and OLIKW field is updated which increases open delivery value and decreses S066-OEIKW
When delivery is billed S067-OFAKW value (Open billing)gets increased and S067-OLIKW gets decreased.
Updation is through the information structures S066 and S067.
In the transaction code OMO1 select the information structure and double click it. You will be faced with parameters pop-up.
In this pop-up you have radio buttons day ,week and Month. _Based on the value you choose here you will get day or week or month for the Period split: info structure field present just besides horizon field of dynamic credit check in OVA8 Screen_If you choose week it will be till the end of the week and if you choose Month it will be end of the month. it is how system considers.
For example if we have created an order today i.e. 19/08/2011 and the Period split: info structure in the OVA8 has 1month.
System evaluates dynamic credit check as today's date + one month =19/09/2011which is =30th september,2011.
So while evaluating credit for the order, system will consider all the open orders whose delivery date is on or before 30th september + open deliveries + open bills + A/C receivables.
Edited by: mokirala tilak on Aug 19, 2011 11:00 AM
Edited by: mokirala tilak on Aug 19, 2011 11:23 AM

Credit management ECC 6.0 implementation

Hi Experts/Gurus,
One of our clients have done a technical upgrade from SAP 4.6c to ECC 6.0.
Now they want to know what will be the timeline required for implementation of the Integrated credit management functionality of ECC6.0 in their SAP system if they go on for functional upgrade.
Now following are my doubts:
1) How to compare their existing credit management process/Functionality with the new ECC 6.0 integrated credit management functionality?
2) How to decide upon the timeline required to implement the new credit management functionalityof ECC 6.0?
Thanks in Advance!

Hi,
Its depend on your company upgrade strategies, compair 40. credit mgt. functionality & 6.0 functionality.
then go for upgradre
Heer I some comments on upgrade
Upgrade Scenarios
Customers who are motivated to upgrade to ECC 6.0 generally pursue at least one of the four key goals just discussed as the primary goal of the upgrade.
Improved business strategy
Sustainability
Operational excellence,
Lower TCO
SAP takes three major approaches to upgrading, each driven by a different motivation and leading to a different ROI and payback periods.
u2022 Technical upgrade:
Focuses on risk mitigation and sustainability of the existing SAP solution.
u2022 Functional upgrade:
Focuses on reducing TCO by reducing system complexity u2013 for example, by returning custom modifications and custom code to SAP standard code
u2022 Upgrade with strategic business improvements:
Considers major reengineering and implementation of new strategic business applications as part of the project scope. These approaches are summarized below.
The three major approaches can be complemented by other compelling changes such as system landscape consolidation, the implementation of shared service center(s), and so forth.
In summary, the more your upgrade decision is driven by business improvement goals, the better your expected ROI. Upgrade experiences and customer statistics confirm that the decision for an SAP software upgrade is usually determined by a mix of business, technology, and strategic criteria.

DNB integration with FSCM SAP Credit management

Hi,
Any body worked on or integrated DNB with FSCM SAP Credit management ? if it is please share some information /document on integration.
Thx
DD

Hi Ankur
You can integrate with DNB either online or batch mode .
.Online mode
    In this mode, a request is sent from FSCM to DNB for credit data. A response is sent by the DNB synchronously, for the request initiated from FSCM.
    Following was done to implement this. Middle ware (java based) created a web service and in FSCM we created a client proxy to consume the web service.
To initiate the request from FSCM, we called a web service method using a custom program passing the relevant information like agency name, customer name etc.
To call the web service method through the proxy, we had to pass the port name in the proxy call. The URL for the web service was configured in the port (transaction LPCONFIG). Middle ware got the request and in real time passed it to the DNB using integration technique   The DNB sent response back to Middle Ware in real time and Middle ware passed it back to FSCM using the same web service used for the request from FSCM.
. Batch mode -
In this mode, there was no request from FSCM side. Middle ware will aggregate credit data from DNB on periodic basis and dump the data as xml files in FSCM application server. A batch job (custom program) will be    scheduled in FSCM to process the xml files provided by Middle ware and update credit data from agencies in FSCM.
Thanks
Rajesh Kanamarlapudi

Grace Period for document process

A document is submitted for approval. There is a defined length of time (grace period) that any approval can stay without being approved. If the document exceeds the grace period a reminder email is sent to the approver(s). If it exceeds the defined length of time times X (deadline period) then an email is sent to the requestor and a manager
     A field that defines the grace period. This field must be editable by the document administrator
     A field that defines the deadline period. This field must be editable by the document administrator
     Define standard email text that is editable by the document administrator. The standard text could be different for each email
     Review the grace period and compare it to documents that have been put in approval
     Send an email based on the comparison to the approver(s) with standard text
     Review the documents and compare it to the deadline period
     Send an email based on the comparison to the requestor and manager with standard text
can anyone help
thanks

Hi Venu,
I only said "like time based publishing service", I didn't say that you should use it. I only wanted to say: Look at how TBP service works, the same idea could be the basis for your implementation.
Properties: Under System Administration -- System Configuration -- Knowledge Management -- Configuration -- Content Management -- Global Services you will find Property Metadata and Property Structures (with different subfolders). Just walk through them carefully to understand how properties are managed within KM. Once you got it, it's easy to implement/extend the given properties with your own ones.
Hope it helps
Detlev

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 for IT industry

Hi,
As we want to use credit management functionality of SAP but really not understand how to implement it
Means at level check should be happen because we are a service industry where we have contract with customer for varying periods 1 year,2 year....etc and accordingly resources are deployed in it.
So our current process is we create the sales contract and do the billling of it.
So at what event ny credit event should trigger-- I can't stop billing bcoz efforts are already been put by resources and i can't check at order level as contract is for long period.
What is the actual process of credit management in a n IT industry ?

Hi Cecilia,
Please check below link. This could be useful.
http://scn.sap.com/thread/1892805
Regards,
Gaurav

Typical requirement in Credit Management-

Hi ALL,
I have posted same query earlier too,but i havent get any satisfactory reply.so
time being i closed that thread.
Here is my client req, regarding Credit Management.
Client is restricting customers credit based on Credit period ( payment terms)
Client wants to check customers based on Credit limit & credit period whichever is earlier/lower.
eg: Customer -X credit limit: 1,00,000/-
Credit period - 30 days
then when creating Order, if customer's outstanding exceeds credit limit then
block should trigger- ( which is std settings)
- if customer has not cleared open items which is 30 days old,block should trigger
irrespective of value. ( which can be achieved through "open item"- in OVA8)-
customer place the release schedules everymonth, for the next 3 months.
eg: Material- A, req - April- 1000pcs / May-2000pcs/June-1500 pcs
where as in Std, I have maintained "Fixed date & qtty" in availability check in OVZJ
so that only "confirmed qtty" should transferred to MD04 ( as per credit block,requirement will not
be confirmed in schedule lines in order for all items)
as per credit check result,requirement of May/June should not transfer to MD04
only April req should transfer to MD04.
Any Ideas -

Hi,
I'm not sure, but perhaps you can define an own subroutine in OVB8, subroutine 101 (report LV07A101). Design the algorithm for months and check it.
Another idea. Check the BADI 'MD_CHANGE_MRP_DATA', method 'CONSIDER_OTHER_SD_TYPES'. Considerer the example implementation.
I hope this helps you,
Regards,
Eduardo

Grace period in Credit Management

Similar Messages

Maybe you are looking for