SAP R/3 форум ABAP консультантов
Russian ABAP Developer's Club

Home - FAQ - Search - Memberlist - Usergroups - Profile - Log in to check your private messages - Register - Log in - English
Blogs - Weblogs News

SD Enhanced credit management



 
Post new topic   Reply to topic    Russian ABAP Developer's Club Forum Index -> SD
View previous topic :: View next topic  
Author Message
admin
Администратор
Администратор



Joined: 01 Sep 2007
Posts: 1636

PostPosted: Sat Apr 12, 2008 3:12 pm    Post subject: SD Enhanced credit management Reply with quote

SD Enhanced credit management

1) Calling a credit check function
FUNCTION SD_ORDER_CREDIT_CHECK

2) Credit release function (related TCODE: VKM1)
FUNCTION SD_ORDER_CREDIT_RELEASE

3) on the credit check call and Updating Unconfirmed Sales Document (V_V1)
SDV03V01

4) user interface can be enhanced
Credit Check
If you want to carry out your own individual credit checks, that differ from those in the standard system, you must define them in the following user exits:
LVKMPTZZ
LVKMPFZ1: USER_CREDIT_CHECK1
LVKMPFZ2: USER_CREDIT_CHECK2
LVKMPFZ3: USER_CREDIT_CHECK3

User exit for availability check
User exit USEREXIT_AVAIL_CHECK_CREDIT exists in Include MV45AFZF.

5 Important structures
Open deliveries/billing documents (S067)
S067-OFAKW - Open billing document credit value
s067-OLIKW - Open delivery credit value

Open orders (S066)
s066-oeikw - Open sales order credit value (schedule lines)
SD_CREDIT_EXPOSURE : Get open order, delivery and invoices

6) can refer to the function LVKMPF0G

7)
Code:
CALL FUNCTION 'CREDIT_EXPOSURE'
        EXPORTING
          kkber                = wa_result-kkber
          kunnr                = wa_result-kunnr
          date_credit_exposure = '99991231'
        IMPORTING
          creditlimit          = old_klimk
          open_delivery        = old_olikw
          open_invoice         = old_ofakw
          open_items           = old_skfor
          open_order           = old_oeikw
          PERCENTAGE           = old_KLPRZ
          sum_opens            = old_oblig.


Transactions used

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
- credit control area
- risk category
- 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.

17. Program: RVKRED77, RVKRED07
SD: Reorganization of Credit Values after Update Errors
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic    Russian ABAP Developer's Club Forum Index -> SD All times are GMT + 4 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum


All product names are trademarks of their respective companies. SAPNET.RU websites are in no way affiliated with SAP AG.
SAP, SAP R/3, R/3 software, mySAP, ABAP, BAPI, xApps, SAP NetWeaver and any other are registered trademarks of SAP AG.
Every effort is made to ensure content integrity. Use information on this site at your own risk.