Step by step: | Deck of Cards |
---|
startHidden | false |
---|
effectDuration | 0.5 |
---|
id | OCCURRENCES |
---|
effectType | horizontal |
---|
loopCards | true |
---|
| Card |
---|
default | true |
---|
id | 0. Instructions for resolution |
---|
label | 0. Instructions for resolution |
---|
| Depending on which of the following two occurrences you have identified in your process, check the parameters and processes/fields required to solve your problem:
"Tab 1" for orders unduly released. (should have been blocked but weren't) "Tab 2" for orders unduly blocked. (should have been released but weren't) "Tab 3" if you check everything in the tabs pertaining your scenario but find no cause for the occurrence.
First, you need to check whether the Order is Blocked for lack of Credit. To do this, query through one of the methods below: - Credit Analysis of Sales Order (MATA450): Check whether the order has a Blue Caption (Blocked – Credit)
- Customer Credit Analysis (MATA450A): Identify the customer to which you are trying to sell a product. Click “Manual” and in tab “Orders”, the system displays all orders of this customer that have Credit Blocking
- Release of Credit and Stock (MATA456): Check whether the order has a Blue Caption (Blocked – Credit)
|
Card |
---|
default | true |
---|
id | Average Cost |
---|
label | 1. Order "Unduly" RELEASED by Credit |
---|
| If the order is "Unduly" Released by Credit, check the following Parameters and Fields in the Tabs below: Deck of Cards |
---|
startHidden | false |
---|
effectDuration | 0.5 |
---|
id | Verifications |
---|
effectType | horizontal |
---|
loopCards | true |
---|
| Card |
---|
default | true |
---|
id | Average Cost |
---|
label | 1. PARAMETERS |
---|
| - MV_BLOQUEI: To activate the Credit Evaluation in Order Release, the parameter must be active (.T.)
- MV_LIMINCR: Set the Minimum Value to submit the Orders to Credit Evaluation
- MV_CREDCLI: Check whether it is set to the letter C (Customer), in which case the system uses the Credit from all stores (A1_LOJA) of this Customer (A1_COD). If another store has credit, the order is released.If any store has the field A1_MSBLQL = 1 (Status = Inactive), the information are still used in the credit evaluation
- MV_RISCO: If the customer has overdue bills, the system checks the risk entered in field “Risk” (A1_RISCO) and compares it with the content of the equivalent MV_RISCO. Example: The customer has the field “Risk” (A1_RISCO) filled in as “B – Risk B”, the system checks parameter “MV_RISCOB”. Learn more.
Aviso |
---|
| If the customer has overdue bills with a deadline after the one set in MV_RISCO and the system is not Blocking his Credit, make sure the overdue bills have the field “Status” (E1_STATUS) filled in with “A” (Open). Otherwise, they do not figure in the calculation for Customer Credit validation. |
|
Card |
---|
default | true |
---|
id | 060720201 |
---|
label | 2. FIELDS AND PROCESSES |
---|
| 1. The fields “Released Orders Balance” (A1_SALPEDL) and "Trade Notes Balance" (A1_SALDUP) indicate how much of the “Credit Limit” (A1_LC) has already been used. Check the field contents, which compromise the results of the Automatic Analysis when incorrect. Learn more.
2. Are you performing Automatic Release of Credit? If you use the option "MANUAL", the system disregards the configuration of Customer Credit and does a "Forced" Release. Learn more.
3. Values of Taxes and Expenses: It is vital to clarify that Taxes and Incidental Expenses (Shipping/Insurance/Expenses) do not figure in the Automatic Credit Release calculation. These values are only deducted from Credit available after billing; that is, for the customer's next purchases. Learn more.
4. It is vital to clarify that, even if the Register of this Customer is Blocked through field “A1_MSBLQL”, the definitions in its register continue to be used for Credit Analysis. The Blocking only prevents using the record in other routines. Learn more.
5. Bills of type “RA” (Advanced Receipt) are considered Credit for the customer. When added, their value is deducted from field “Trade Notes Balance (A1_SALDUP)". When overdue, they are not used in Risk Analysis.
Dica |
---|
| Module Financials (SIGAFIN) offers the routine “Redo Customer / Supplier Data” (FINA410). This routine updates the data of fields of Customer Register (MATA030). If you discover any inconsistent field information, run this routine and check whether it has been corrected. Learn more in: https://tdn.totvs.com/x/bqFc. |
|
|
|
Card |
---|
default | true |
---|
id | 060720201 |
---|
label | 2. Order "Unduly" BLOCKED by Credit |
---|
| If the order is "Unduly" Blocked by Credit, check the following Parameters and Fields in the Tabs below: Deck of Cards |
---|
startHidden | false |
---|
effectDuration | 0.5 |
---|
id | Verifications 2 |
---|
effectType | horizontal |
---|
loopCards | true |
---|
| Card |
---|
default | true |
---|
id | Custo Médio |
---|
label | 1. PARAMETERS |
---|
| - MV_BLQCRED:
T - Block the Credit on purpose, if there is no Available Stock Balance to meet the order, in order to not compromise the Credit Limit balance. F - Do not block the credit.
- MV_PERMAX: Maximum use percentage in relation to the credit limit (A1_LC) to be used in evaluations.
Expandir |
---|
title | Exemple of MV_PERMAX |
---|
| Example of MV_PERMAX use Example: In a sales order, supposing a customer with a given credit limit at its maximum capacity; that is, with no purchases made that would debit any quantity from its limit: - Credit Lim. (A1_LC) = 1,000
- MV_PERMAX = 50 (%)
In a credit analysis with the above configurations, parameter MV_PERMAX causes only 50% of the total to be used; hence, it is as if the customer had the credit limit A1_LC = 500 (50% of 1,000). If the same customer of the example above places a Sales Order (MATA410) with a BRL 600.00 total and releases it, they get blocked by credit. |
- MV_LIBNODP:
N - Do not evaluate credit of sales orders with TIO (F4_DUPLIC = 'S - Yes') T - Evaluate credit of sales orders with TIO (F4_DUPLIC = 'S - Yes')
|
Card |
---|
default | true |
---|
id | 060720201 |
---|
label | 2. FIELDS AND PROCESSES |
---|
| 1. The Automatic Credit Analysis deducts from the Customer Credit Limit (A1_LC) the value of Orders Released (A1_SALPEDL) and the value of Bills Pending (A1_SALDUP). Check the contents of these three fields. Learn more.
2. Check the content of field “Risk” (A1_RISCO) in the Customer Register (MATA030), whether the risk of the customer is B, C or D. Check the content of parameter “MV_RISCOB/C/D”, evaluating whether this customer has bills with “Status” (E1_STATUS) equal to “A” (Open) with a deadline after the one entered in the Parameter
3. If the content of field “Risk” (A1_RISCO) is E, all its billings are Blocked by Credit, which requires the Manual Release of Credit. Learn more.
4. Check whether this customer has bills in financials that, even if posted, retain the “Status” (E1_STATUS) equal to “A” (Open), because such bills will be used in the consumption of Customer Credit and in Risk Analysis. If you find this occurrence in your environment, contact the Support of Module Financials (SIGAFIN)
5. Check whether the content of fields “LC Currency” (A1_MOEDALC) of the Customer Register, “Currency” (C5_MOEDA) of the Sales Order and of parameter “MV_MCUSTO” are equal. These records must have the same content
6. Check whether the content of field Cred Class (A1_CLASSE) is A/B/C. If so, check the setting of parameter MV_PEDIDOA/B/C, because this parameter defines the Maximum Sales Value by Sales Order allowed for this customer. Learn more. |
|
|
Card |
---|
default | true |
---|
id | Information to be sent |
---|
label | 3. Information to be sent for analysis if no cause is identified |
---|
| If, after checking the parameters and processes in the documentation pertaining your situation, you still have not found the error, submit the following for analysis (screenshot or in writing):
1 - Content of parameters: - MV_BLQCRED
- MV_LIBNODP
- MV_PERMAX
- MV_AVALEST
- MV_BLOQUEI
- MV_LIMINCR
- MV_CREDCLI
- MV_RISCO
- MV_MCUSTO
- MV_PEDIDOA, MV_PEDIDOB and MV_PEDIDOC
2 - Content of fields (TES): - F4_DUPLIC of TIO of sales order (C6_TES)
3 - Content of items for sales order release: - C9_BLWMS
- C9_BLEST
- C9_BLCRED
4 - Field contents of the customer whose sales order is being blocked: - A1_CLASSE
- A1_MOEDALC
- A1_RISCO
- A1_LC
- A1_VENCLC
- A1_SALDUP
- A1_SALPEDL
5 - Content of sales order fields:
6 - Enter the process verification: - Is the sales order release automatic or manual?
7 - Screenshot of routine "Accounts Receivable [FINA740]", filtered by the customer with the sales order blocked as follows: ("E1_CLIENTE" and "E1_STATUS = A"), displaying the captions: Image Added Image Added
|
|
Dica |
---|
title | For Your Information |
---|
| By viewing the records from Table SC9 of the system, through routine "Generic Queries " (EDAPP), you can check the cause of Credit Blocking in the contents of field “Credit Blocking” (C9_BLCRED). Learn more in: https://tdn.totvs.com/x/Zk1tDQ |
|