Credit Block Again After Release Sap
Article: Problem of credit block recurrence in SAP.
Summary: Article includes the case report for credit block recurrence in agribusiness along with the solution delivered.
Author: Kamal Dial
Created on: 30th September, 2013
Author Bio: Kamal is a Consultant at Infosys and has over 3 years of professional piece of work experience in SAP Sales and Distribution module. He is technology graduate from PEC Chandigarh and postal service graduate in Management from Symbiosis Pune. He would similar to thank his team members Amerjit Singh Isle of man, Satish Sivasankar, Arturo Minguer and Naveen Advani for their contribution towards this implementation.
Credit Management –Introduction
Credit is facility provided to customers and then they need not pay immediately and payment tin can be washed at a future bespeak of fourth dimension afterward receiving the goods or services. The amount of credit extended is determined by the customer's credit worthiness which is called credit Limit.
Purpose:
Credit direction involves managing credit limits for every client at regular intervals which helps in keeping track of payment records for customers .It helps in increasing the sales for an organization along with risk mitigation.
Example study:
This case report is specific to agribusiness industry where problem of recurrence of credit block impacts the whole business organization line taking into consideration the modest shelf life of seeds sold to the stop client. Its increases in the lead time of the whole process from order to invoicing involving additional approvals and unnecessary credit blocks becomes clogging in the delivery procedure.
Problem statement: After sales orders are released from credit cake it may happen that after some other availability check of the document, the document runs through the credit checks and is blocked.
Reason:
The credit block recurrence occurs due to changes the confirmation quantity in the order which leads to credit cake again and again. Information technology happens in the scenario where shortage occurs and before delivery arrangement carries out another availability bank check which confirm more than than the initial released quantity.This problem of recurrence leads to additional approvals from Credit managers increasing the lead time in the system.
Credit exposure calculation and moment of updating the same– Exposure calculation is based on the confirmed quantity and exposure is likewise updated in case order goes into credit block.It leads to scenario where subsequent orders are also blocked as exposure is updated past initial society of high credit value.
Hence this leads to problem of recurrence which impacts the overall delivery fourth dimension and increases the lead fourth dimension involved which is very disquisitional for agribusiness industry.
SAP notes referred: SAP Note 100861, 1042857, 1324433 ,377165,751044,666587.
SAP Standard Behaviour with As IS situation:
As per standard SAP calculation of Credit Exposure involves receivables, Spl Liability and sales Lodge value. Receivables are total billed transactions passed to accounting and Spl Liability includes the advance payments.
Full sales order value is summation of open Order value, open delivery value and open up billing value.
– – Open up order value
• The open order value is the value of all order items which accept not been delivered withal.
– – Open delivery value
• The open commitment value is the value of all delivery items which have not been billed.
– · Open billing value
• The open billing value is the value of all billing items which have non been transferred to Bookkeeping.
For below example: With ordered quality as 100EA, confirmed quality as 50 EA and credit value x$ , Full sales order value becomes 500$
Nosotros consider business scenario where credit exposure (chiliad$) exceeds the credit limit
Since initially stock confirmed is 50 EA, lodge credit value is 500$ and Credit exposure is updated to 1500$.
If stock confirmation quantity increases to 80 EA, Club credit value becomes 800$ and order goes into bank check block once again. In one case released exposure is updated to 1800$.
Hence even after releasing the club increase in the confirmation leads to credit block once again and again.
Solution implemented
ane) 1) This involves changes in the standard SAP User exits RMCS1US1 and RMCS1US3.
For credit release –sales lodge value should be updated based on the guild quantity instead of open confirmed quantity. This can exist controlled via changes in the standard user exists RMCS1US1.
To make sure released credit value and update of open up sales order credit value remain aforementioned, this this involves lawmaking changes in the standard user exist RMCS1US3
Restriction of behavior can be done using TVARVC variant to exclude detail business organization process from scope of the changes.
two) Resetting of confirmation in example of check block as per Standard SAP behavior.
Creation of new requirement routine RV07A999 and TVARVC was done to exclude particular business process from telescopic of the changes.
Behavior after implementation:
After implementation -society credit value is calculated based on the club quality and credit exposure is updated by total order value once released.
Hence increment in stock confirmation does non lead to another credit check since order is released initially on the total order value.
Explanation of post implementation behavior considering below scenario`southward without credit cake and with credit block.
Instance A) Credit limit is not exceeded –Behavior is based on the standard SAP. Order release value is calculated on the Sales lodge value which is based upon the confirmed quantity.
Hence in below example credit exposure is increased by 50$.
Case B) Credit limit is exceeded –Behavior is based on the solution implemented. Order release value is calculated on the Total Sales order value which is based upon the ordered quantity
Hence in above case credit exposure is increased by 1000$.
Key challenges involved:
1) Changes were involved in the standard SAP functional modules hence it was very of import to check the system behavior in all aspects earlier going live in product.
2) To deliver the expected business result without any adverse impact on the system or any other process.
3) It covered vast scope of functional testing considering all the given possible business organization scenarios.
4) Isolating few business lines from this change as per the business requirement.
5) User training and guidelines to be provided to accommodate new ways of working.
Decision:
1) –Later on implementation – gild credit value is calculated based on the lodge quality and credit exposure is updated by full order value one time released from credit block.
2) –Increase in stock confirmation does not pb to another credit check since order is released initially on the full lodge value.
3) –Problem of recurrence is resolved with this change hence removing the boosted credit approval in the business process.
four) –Information technology led to removal of the bottle neck and streamlining the approval process in instance society goes into the credit block.
five) –Increasing efficiency of the business procedure which decreased the overall atomic number 82 time.
Business Benefits:
- Polish Credit management with i time approval process.
- Enhanced commitment process with reduction in the commitment lead time.
- Reliable and rigid- delivery plans with correct scheduling arrangements.
- Reduction in manpower & try savings.
- Customer satisfaction and repeat client sales.
- Increment in revenues and cost optimization.
Recommendations:
1) Post implementation it is required to update /correct the incorrect credit values using the report standard SAP report- RVKRED77.This study should be used when all users are locked since information technology locks the standard SAP tables.
two) Implementation of new Z report Z_CREDIT_VALUE_COMPARE, This report simulates the first step in the recreation of open credit values (in accordance with study RVKRED88) and afterwards compares the results with the values that are currently in the database. The result returns a list with credit customers for whom there are incorrect open credit values. The incorrect values are highlighted in the list .This helps to identify the list of customers with the wrong open credit values.
three) Acceptable grooming for the end key users and credit approvers to adapt new ways of working.
Source: https://blogs.sap.com/2013/09/29/problem-of-credit-block-recurrence-in-sap/#:~:text=The%20credit%20block%20recurrence%20occurs,than%20the%20initial%20released%20quantity.
0 Response to "Credit Block Again After Release Sap"
Postar um comentário