Credit control procedure/user exit

Hi,
Is it possible to set credit control block for the customer who has not configured credit limit in FD32?
I looked in VOFM and in the include LVKMPFZ1 but as far as I can see these programs are started only if there are records in FD32 (table KNKK).
many thanks
Piotrek

Hello Piotrek,
Unfortnately it is not possible in the standard. You need to mainatin the credit management master data in FD32 if you want to use the credit control block functionality.
Best regards,
Lela

Similar Messages

Credit Control Area User exit

What is user exit in credit Management?
What is the use of it?
How to configure it?
Plz let me know?
Bye

Hi,
user exits are used when u r unable to configure some requirements with standards..for credit management SAP provided number of user exits..mainly 2 will be used.
1.LVKMPTZZ
2.LVKMPTF1
these will be used as per the requirements of the clients..
regards..
yogi..

Export Control /Legal control: need user exit to customize

I have a situation where I want to determine the export control license for a sales order. SAP uses the function module RV_EXPORT_CONTROL to carry out the required check.
The FM uses the country defined for the ship-to-party as the destination country and carries out checks to determine if there is an embargo for the good in the line item to destination country.
My requirement is that the actual destination country or the ultimate destination country ( which is known and not same as the country of the ship to party ) be used to carry out the embargo check.
I could not find any user exit/badi for the same. Is there a way to achieve this functionality. It has been hard coded in the FM. Can we do any customizing settings to achieve this? I could find two partner function EU ( End user for foreign trade ) and UC ( Ultimate Consignee )...can these be somehow used/ configured to achieve the desired functionality? Or is there any other different approach to the issue.
Currently I plan to copy the standard FM and add my functionality. I will turn off the standard export control and then I i will call the custom FM in the end ( userexit_save ) as the export control is carried out at save.
Any suggestion/approaches will be appreciated.

I too have same issue, from where the Fm RV_EXPORT_CONTROL is triggering
Edited by: erakarthi on Jul 14, 2011 8:44 AM

Simple Credit check _ User Exits

Dear Expert,
Please find my scenario,
I am using simple credit check
When i am creation sales order with reference to quotation
Item      Amount
00010 1000
00020 2000
I am getting two messages
1)Credit limit exceeded by 1000
2) Credit limit exceeded by 3000(1000+2000)
But Customer wants in one message like Credit limit exceeded by 3000
Please advice, its very urgent
and also suggest if any user exits available
Regards

Thank you for your reply
Is it possible to achieve the same by using static credit check?
When i tested this static check, i am getting message for the first line item
Ex:
Item      Amount
0010      100
0020      200
System shows " Static credit check 100 Exceeds" and it goes to sales order details screen when i am referring from quotation.
Regards

Customer Credit Balance with user exit: LVKMPFZ1

Hi SD Gurus,
Is it possible to use exit:LVKMPFZ1 with USER 1 in transaction OVA8 to be able not to check credit limit when the customer has credit balance....If possible, please advise.
Thanks
Themba

Hi,
Good evening and greetings,
In the dunning procedure, FBMP transaction code click on the Dunning Levels and inside the dunning levels there is an option under the print parameter tab to print all items...Check that box and the system would include even the credit line items lying in the customer account and that can be printed out.
Please reward points if found useful
Thanking you
With kindest regards
Ramesh Padmanabhan

User exit for merging the credit limit in different credit control area.

Dear All,
Please provide user exit for the merging the credit limit in different credit control area as well as logic for the same.
I have to merge the overall credit limit of the customer for some divisions. At this time in one company code we have created 9 credit control area as per product line. While creating customer master data and Credit management (FD32) user has assigned the different limit with respective to credit control area e. g Customeru2019s total limit assigned is 10 laks. For credit control 1100 Limit is Rs. 3 laks and for credit control area 2200 limit is 7 laks. Now the user wants to merge the credit limit for only above two credit control area. The sales orders should get created in any credit control area up to 10 laks.
Regards,
Suresh

Dear Damodhar/All,
Would you please explain me prerequisite setting from functional side for these user exit?
I want complete functional setting prior to ABAP application so that it work properly post configuration.
Regards,
Suresh

Set Credit control status in user Exit LVKMPFZ1

Dear all
we like to set the credit control status in the above mentioned user exit. Is there a better way than
*VBUK-CMGST = 'B'.
MODIFY *VBUK.
Is there a FM, Bapi or something that can be used?
Thank you
Herbert

User Exits For Credit Checks And Risk Management
   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:
     o   LVKMPTZZ
     o   LVKMPFZ1: USER_CREDIT_CHECK1
     o   LVKMPFZ2: USER_CREDIT_CHECK2
     o   LVKMPFZ3: USER_CREDIT_CHECK3
     User exit for availability check
     User exit USEREXIT_AVAIL_CHECK_CREDIT exists in Include MV45AFZF.
     This user exit allows you to determine whether the system should or
     should not carry out an availability check after a blocked document has
     been released or after a new credit check.
   Risk Management for Receivables
Regards
Prabhu

User Exit for bypassing Dynamic Credit Control Check in Del Cre via VL01N

Hi All,
I have a scenario where I need to bypass a credit check for a particular condition in the sales document(i will be able to check this condition if i know the sales order no) before delivery creation via VL01N. I have searched through for user exits/BADi's but havent got any. If any one has any pointers for the same, it would be of great help.
Regards,
Karthik

User Exits For Credit Checks And Risk Management
   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:
     o   LVKMPTZZ
     o   LVKMPFZ1: USER_CREDIT_CHECK1
     o   LVKMPFZ2: USER_CREDIT_CHECK2
     o   LVKMPFZ3: USER_CREDIT_CHECK3
     User exit for availability check
     User exit USEREXIT_AVAIL_CHECK_CREDIT exists in Include MV45AFZF.
     This user exit allows you to determine whether the system should or
     should not carry out an availability check after a blocked document has
     been released or after a new credit check.
   Risk Management for Receivables
Regards
Prabhu

User exit to activate few controls after the order goes to credit hold

Hi, we would like to turn on the fixed qty flag at the line item level and an header delivery block if an order goes on credit hold.
We are looking out for the user exit which might can be used for this purpose (which can be executed after the credit check was done and before the order is saved either manually or automatically).
Mothish babu

but we want a credit check for certain customers only
Activate credit check for the sales order. If you want to have credit check only for certain customers, maintain relevant credit limit records only for those customers in t.code FD32. If this does not solve the purpose, then you can make use of the field No credit check in t.code OVA8. Develop a routine to check for only certain customers in t,code VOFM ->Requirements->Credit check and assign this routine in OVA8.
Regards,

User exit for Credit Memo creation

I want to create an IDOC when the credit memo will be created.
What is the name of the user exit where I can write the IDOC generation code ?
Edited by: Alvaro Tejada Galindo on Feb 18, 2008 9:47 AM

IDoc Inbound User Exits
1. ACC_BILLING
Accounting: Post invoice (OAG: LOAD RECEIVABLE)
- ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
2. ACC_EMPLOYEE_EXP
FI/CO: HR posting GL (AcctngEmplyeeExenses)
- ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
3. ACC_EMPLOYEE_PAY
FI/CO: HR posting AP (AcctngEmplyeePaybles)
- ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
4. ACC_EMPLOYEE_REC
FI/CO: HR posting AR (AcctngEmplyeeRcvbles)
- ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
5. ACC_GL_POSTING
Accounting: General G/L account posting
- ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
6. ACC_GOODS_MOVEMENT
Accounting: Post goods movement (OAG: POST JOURNAL)
- ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
7. ACC_INVOICE_RECEIPT
Accounting: Post invoice receipt (OAG: LOAD PAYABLE)
- ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
8. ACLPAY Accounting: Inbound invoice
- ACCID001 EXIT_SAPLACC1_031 IDoc ACLPAY: Userexit for creditor in accounting document
- ACCID001 EXIT_SAPLACC1_032 IDoc ACLPAY: Userexit for GL posting in accounting document
- ACCID001 EXIT_SAPLACC1_033 IDoc ACLPAY: Userexit for taxes in accounting document
9. ACLREC
Accounting: Billing document
- ACCID001 EXIT_SAPLACC1_011 IDoc ACLREC: Userexit for debitor in accounting document
- ACCID001 EXIT_SAPLACC1_012 IDoc ACLREC: Userexit for GL posting in accounting document
- ACCID001 EXIT_SAPLACC1_013 IDoc ACLREC: Userexit for taxes
10. ACPJMM
Posting in accounting from materials management
- ACCID001 EXIT_SAPLACC1_021 IDoc ACPJOU: Userexit for GL posting in accounting document
11. ARTMAS
Create and change of material master (Retail)
- MGV00003 EXIT_SAPL1001_003 Enhancement for article master: IDoc inbound
12. BLAOCH
Purchasing contract change
- MM06E002 EXIT_SAPLEINN_001 Customer enhancements for Idocs: contracts
- MM06E002 EXIT_SAPLEINN_002 Customer enhancements for Idocs: contracts
- MM06E002 EXIT_SAPLEINN_003 Customer enhancements for Idocs: contracts
13. BLAORD
Purchasing contracts
- MM06E002 EXIT_SAPLEINN_001 Customer enhancements for Idocs: contracts
- MM06E002 EXIT_SAPLEINN_002 Customer enhancements for Idocs: contracts
- MM06E002 EXIT_SAPLEINN_003 Customer enhancements for Idocs: contracts
14. BLAREL
Release order documentation for distributed contracts
- MM06E001 EXIT_SAPLEINM_004 Customer enhancements for release documentation inbound
15. COND_A
Conditions: master data for price determination
- VKOI0001 EXIT_SAPLVKOI_001 Interchange of Conditions: Inbound Processing Modifications E1KOMG Segment
- VKOI0001 EXIT_SAPLVKOI_002 Interchange of Conditions: Inbound Processing Customer Segments
16. CREMAS
Distribute vendor master
- VSV00001 EXIT_SAPLKD02_001 Inbound: Read and process vendor segments
17. DEBMAS
Customer master
- VSV00001 EXIT_SAPLVV02_001 Inbound: Read and update additional customer master segments
18. DELINS
Delivery schedule/JIT schedule
- VED40001 EXIT_SAPLVED4_001 Modify Warnings in Table XVBFS
- VED40001 EXIT_SAPLVED4_002 Copying Data to Screens for Incoming EDI Docs
- VED40001 EXIT_SAPLVED4_003 Customer-Specific Changes in the Workflow Parameters
- VED40001 EXIT_SAPLVED4_004 Determination of mail receiver during inbound processing
19. DESADV
Delivery: Shipping notification
- LMELA010 EXIT_SAPLEINM_010 Customer enhancement shipping notification inbound: line item
- MM06E001 EXIT_SAPLEINM_006 Customer enhancements for shipping notification inbound
- V55K0001 EXIT_SAPLV55K_001 Delivery (inbound): Take data
- V55K0002 EXIT_SAPLV55K_002 Delivery (inbound): Prepare processing
- V55K0003 EXIT_SAPLV55K_003 Delivery (inbound): Evaluate result
- V55K0011 EXIT_SAPLV55K_011 Shipping notification (inbound): Take data
- V55K0012 EXIT_SAPLV55K_012 Shipping notification (inbound): Prepare processing
- V55K0013 EXIT_SAPLV55K_013 Shipping notification (inbound): Evaluate result
20. DOCMAS
Master document
- CVDS0001 EXIT_SAPLCVALE_001 Userexit for ALEDVS (DOCMAS inbound)
21. DOLMAS
Document-object links
- CVDS0001 EXIT_SAPLCVALE_003 Userexit for ALEDVS (DOLMAS inbound)
22. EDLNOT
EDL delivery notes
- VED40001 EXIT_SAPLVED4_001 Modify Warnings in Table XVBFS
- VED40001 EXIT_SAPLVED4_002 Copying Data to screens for Incoming EDI Docs
- VED40001 EXIT_SAPLVED4_003 Customer-Specific Changes in the Workflow Parameters
- VED40001 EXIT_SAPLVED4_004 Determination of mail receiver during inbound processing
23. FIDCC1
Send entire FI documents (user exit 003/4)
- F050S001 EXIT_SAPLF050_002 IDoc inbound: read user-defined IDoc segment
- F050S002 EXIT_SAPLF050_004 FIDCC1 IDoc inbound: Change IDoc / do not process
- F050S005 EXIT_SAPLF050_008 IDoc inbound: change fields in ACC structures (FI document)
- F050S005 EXIT_SAPLF050_009 IDoc inbound: change fields in parked documents
24. FIDCC2
Send entire FI documents (user exit 005/6)
- F050S001 EXIT_SAPLF050_002 IDoc inbound: read user-defined IDoc segment
- F050S003 EXIT_SAPLF050_006 FIDCC2 IDoc inbound: Change IDoc / do not process
- F050S005 EXIT_SAPLF050_008 IDoc inbound: change fields in ACC structures (FI document)
- F050S005 EXIT_SAPLF050_009 IDoc inbound: change fields in parked documents
25. FIDCMT
Sending single items for FI-GL
- F050S001 EXIT_SAPLF050_002 IDoc inbound: read user-defined IDoc segment
- F050S005 EXIT_SAPLF050_008 IDoc inbound: change fields in ACC structures (FI document)
26. FINSTA
Bank Statement
- FEDI0005 EXIT_SAPLIEDP_201 FI-EDI: inbound - bank statement/ Lockbox - Final processing
- FEDI0005 EXIT_SAPLIEDP_202 FI-EDI: inbound - bank statement/ Lockbox - Processing of segments
27. FIROLL
General ledger rollup for FI-GL (delta f. line items FIDCMT)
- F050S001 EXIT_SAPLF050_002 IDoc inbound: read user-defined IDoc segment
28. GSVERF
Cred. memo procedure
- VED50001 EXIT_SAPLVED5_001 User Exit for Condition Value Tolerances in the Self- Billing Procedure
- VED50001 EXIT_SAPLVED5_005 Customer-Specific Changes in Workflow Parameters
- VED50001 EXIT_SAPLVED5_006 Copying Data to Screens for Incoming EDI Docs
29. HRMD_A
HR: Master data and organizational data (appl. system)
- RHALE001 EXIT_SAPLRHA0_002 HR-CA: ALE inbound processing: Export parameter
- RHALE001 EXIT_SAPLRHAL_002 HR-CA: ALE inbound processing: Change info type data
- RHALE001 EXIT_SAPLRHAL_004 HR-CA: ALE inbound processing: conversion segment/ info type
30. INFREC
Purchasing info record
- MMAL0004 EXIT_SAPLMEAI_004 ALE source list distribution: inbound processing userdefined data
- MMAL0004 EXIT_SAPLMEAI_003 ALE purchasing info record distribution: inbound processing segments
31. INVOIC
Invoice / Billing document
- FEDI0001 EXIT_SAPLIEDI_001 FI-EDI: Invoice receipt - Determine G/L account per invoice line
- FEDI0001 EXIT_SAPLIEDI_002 FI-EDI: Invoice receipt - Determine add. acct assignm. per line item
- FEDI0001 EXIT_SAPLIEDI_003 FI-EDI: Invoice receipt - Fill the screen field 'Allocation'
- FEDI0001 EXIT_SAPLIEDI_004 FI-EDI: Invoice receipt - Determine the segment text
- FEDI0001 EXIT_SAPLIEDI_005 FI-EDI: Invoice receipt - Determine the name of the BDC session
- FEDI0001 EXIT_SAPLIEDI_011 MM-EDI: Invoice receipt - Determine purchase order item
- FEDI0001 EXIT_SAPLIEDI_101 FI-EDI: Invoice receipt INVOIC01 - additional assignment
- FEDI0001 EXIT_SAPLIEDI_102 FI-EDI: Invoice receipt INVOIC01 - add data
- FEDI0001 EXIT_SAPLIEDI_111 MM-EDI: Invoice receipt INVOIC01 - additional assignment
- FEDI0001 EXIT_SAPLIEDI_112 MM-EDI: Invoice receipt INVOIC01 - add data
- MRMH0002 EXIT_SAPLMRMH_011 Logistics Invoice Verification:inboud EDI message, company code
- MRMH0002 EXIT_SAPLMRMH_012 Logistics Invoice Verification:inboud EDI message, control flags
- MRMH0002 EXIT_SAPLMRMH_013 Logistics Invoice Verification:inboud EDI message, assignment
- MRMH0002 EXIT_SAPLMRMH_014 Logistics Invoice Verification:inboud EDI message, segments
- MRMH0002 EXIT_SAPLMRMH_015 Logistics Invoice Verification:inbound EDI message, before posting
32. LIKOND
Listing conditions
- WSOR0001 EXIT_SAPLWSOI_001 Enhancement for assortments: inbound IDoc
33. MATMAS
Material Master
- MGV00001 EXIT_SAPLMV02_002 Enhancement for material master IDoc: Update
34. MRESCR
Create reservation
- SAPLMEWB EXIT_SAPLMEWB_001 Customer exit for processing of reservations via BAPIs
35. ORDCHG
Purchase order/order change
- MM06E001 EXIT_SAPLEINM_012 MM EDI ORDERS/ ORDCHG: enhancement configuration
- MM06E001 EXIT_SAPLEINM_013 MM EDI ORDERS/ ORDCHG: enhancement configuration
- VEDB0001 EXIT_SAPLVEDB_001 SD EDI incoming change orders: read additional data from IDoc
- VEDB0001 EXIT_SAPLVEDB_002 SD EDI incoming change orders: additional data for dynpros
- VEDB0001 EXIT_SAPLVEDB_003 SD EDI incoming change orders: further activities after calling
- VEDB0001 EXIT_SAPLVEDB_004 SD EDI incoming change orders: closing activities per
- VEDB0001 EXIT_SAPLVEDB_005 SD EDI incoming change orders: closing activities by order block
- VEDB0001 EXIT_SAPLVEDB_006 SD EDI incoming change orders: setting order type
- VEDB0001 EXIT_SAPLVEDB_007 SD EDI incoming change orders: additional checks of IDoc
- VEDB0001 EXIT_SAPLVEDB_008 SD EDI incoming change orders: error handling
- VEDB0001 EXIT_SAPLVEDB_009 SD EDI incoming change orders: additional checks of IDoc segments
- VEDB0001 EXIT_SAPLVEDB_010 SD EDI incoming change orders: manipulation of status ecords
- VEDB0001 EXIT_SAPLVEDB_012 SD EDI incoming change orders: change internal table
36. ORDERS
Purchase order / order
- MCP20008 EXIT_SAPLMCP2_008 User exit: Processing of purchase order header
- MCP20008 EXIT_SAPLMCP2_009 User exit: Processing of purchase order item
37. ORDERS
Purchase order / order
- MM06E001 EXIT_SAPLEINM_012 MM EDI ORDERS/ ORDCHG: enhancement configuration
- MM06E001 EXIT_SAPLEINM_013 MM EDI ORDERS/ ORDCHG: enhancement configuration
- VEDA0001 EXIT_SAPLVEDA_001 SD EDI incoming orders: read additional data from IDoc
- VEDA0001 EXIT_SAPLVEDA_002 SD EDI incoming orders: additional data for dynpros
- VEDA0001 EXIT_SAPLVEDA_003 SD EDI incoming orders: further activities after calling
- VEDA0001 EXIT_SAPLVEDA_004 SD EDI incoming orders: closing activities per order
- VEDA0001 EXIT_SAPLVEDA_005 SD EDI incoming orders: closing activities by order block
- VEDA0001 EXIT_SAPLVEDA_006 SD EDI incoming orders: setting order type
- VEDA0001 EXIT_SAPLVEDA_007 SD EDI incoming orders: number of ordering party
- VEDA0001 EXIT_SAPLVEDA_008 SD EDI incoming orders: error handling
- VEDA0001 EXIT_SAPLVEDA_009 SD EDI incoming orders: additional checks of IDoc segments
- VEDA0001 EXIT_SAPLVEDA_010 SD EDI incoming orders: manipulation of status records
- VEDA0001 EXIT_SAPLVEDA_011 SD EDI incoming orders: change internal table
- WVFB0001 EXIT_SAPLWVFB_002 Customer exists for store order PO confirmationdata seg.
38. ORDRSP
Purchase order / order confirmation
- MM06E001 EXIT_SAPLEINM_005 Customer enhancements for order confirmation inbound
- MM06E001 EXIT_SAPLEINM_007 Customer enhancements inbound confirmation: reading
- MM06E001 EXIT_SAPLEINM_008 Customer enhancements inbound confirmation: final
- WVMI0001 EXIT_SAPLWVMI_003 ORDRSP VMI inbound, modification before creating purchase order
39. PORDCR
Create purchase order
- SAPLMEWP EXIT_SAPLMEWP_002 Customer exit for processing of purchase orders via BAPIs
40. PREQCR
Create purchase requisition
- SAPLMEWQ EXIT_SAPLMEWQ_001 Customer exit for processing of requisitions via BAPIs
41. PROACT
Stock and sales data
- WVMI0001 EXIT_SAPLWVMI_002 IDoc PROACT inbound: prior to processing
42. REMADV
Payment advice
- FEDI0002 EXIT_SAPLIEDP_101 FI-EDI: Incoming pmnt advice - Extended allocatn of IDOC -> applicatn data
- FEDI0002 EXIT_SAPLIEDP_102 FI-EDI: Incoming pmnt adivce - Closing allocatn of IDOC -> applicatn data
43. REQOTE
Inquiry
- VEDQ0001 EXIT_SAPLVEDQ_001 SD EDI inbound inquiry: read additional data from IDoc
- VEDQ0001 EXIT_SAPLVEDQ_002 SD EDI inbound inquiry: additional data for dynpros
- VEDQ0001 EXIT_SAPLVEDQ_003 SD EDI inbound inquiry: further activities after calling
- VEDQ0001 EXIT_SAPLVEDQ_004 SD EDI inbound inquiry: closing activities per inquiry
- VEDQ0001 EXIT_SAPLVEDQ_005 SD EDI inbound inquiry: closing activities by inquiry block
- VEDQ0001 EXIT_SAPLVEDQ_006 SD EDI inbound inquiry: setting inquiry type
- VEDQ0001 EXIT_SAPLVEDQ_007 SD EDI inbound inquiry: number of sold-to party
- VEDQ0001 EXIT_SAPLVEDQ_008 SD EDI inbound inquiry: error handling
- VEDQ0001 EXIT_SAPLVEDQ_009 SD EDI inbound inquiry: additional checks of IDoc segments
- VEDQ0001 EXIT_SAPLVEDQ_010 SD EDI inbound inquiry: manipulation of status records
- VEDQ0001 EXIT_SAPLVEDQ_011 SD EDI inbound inquiry: change internal table
44. SBINV
Credit memo procedure with invoice creation
- VED50001 EXIT_SAPLVED5_002 User Exit for messages in the Self-Billing Procedure SBINV
- VED50001 EXIT_SAPLVED5_003 User Exit for Tolerances in the Self- Billing Procedure SBINV
- VED50001 EXIT_SAPLVED5_004 Customer-Function for changing invoice data SBINV
- VED50001 EXIT_SAPLVED5_005 Customer-Specific Changes in Workflow Parameters
- VED50001 EXIT_SAPLVED5_006 Copying Data to Screens for Incoming EDI Docs
45. SDPACK
Packing confirmation
- VMDE0001 EXIT_SAPLVMDE_001 Shipping Interface: Error Handling - Inbound IDoc
- VMDE0004 EXIT_SAPLVMDE_004 Shipping Interface: Message SDPACK (Packing, Inbound)
46. SDPICK
Picking confirmation
- VMDE0001 EXIT_SAPLVMDE_001 Shipping Interface: Error Handling - Inbound IDoc
- VMDE0003 EXIT_SAPLVMDE_003 Shipping Interface: Message SDPICK (Picking, Receipt)
47. SHP_IBDLV_CONFIRM_DECENTRAL
Confirmation (Inbound Delivery)
- V50B0001 EXIT_SAPLV50I_002 User exit for BAPI Verification of Inbound Deliveries
48. SHP_IBDLV_SAVE_REPLICA
BAPI Function Module for Duplication of Outbound Deliveries
- V50B0001 EXIT_SAPLV50I_001 User exit for BAPI Duplication of Inbound Deliveries
49. SHP_OBDLV_CONFIRM_DECENTRAL
Confirmation (Customer Delivery)
- V50B0001 EXIT_SAPLV50I_004 User exit for BAPI Verification of Outbound Deliveries
50. SHP_OBDLV_SAVE_REPLICA
BAPI Function Module for Duplication of Outbound Deliveries
- V50B0001 EXIT_SAPLV50I_003 User exit for BAPI Duplication of Outbound Deliveries
51. SHPCON
Delivery: Shipping confirmation
- V55K0001 EXIT_SAPLV55K_001 Delivery (inbound): Take data
- V55K0002 EXIT_SAPLV55K_002 Delivery (inbound): Prepare processing
- V55K0003 EXIT_SAPLV55K_003 Delivery (inbound): Evaluate result
- V55K0011 EXIT_SAPLV55K_011 Shipping notification (inbound): Take data
- V55K0012 EXIT_SAPLV55K_012 Shipping notification (inbound): Prepare processing
- V55K0013 EXIT_SAPLV55K_013 Shipping notification (inbound): Evaluate result
52. SHPMNT
Shipping outbound
- V55K0020 EXIT_SAPLV55K_020 IDoc SHPMNT: Modification Control/ Data before processing
- V55K0021 EXIT_SAPLV55K_021 Processing of segments IDoc SHPMNT
- V55K0022 EXIT_SAPLV55K_022 Update of user defined tables for inbound IDoc SHPMNT
53. SRCLST
Source List
- MMAL0002 EXIT_SAPLMEAI_001 ALE source list distribution: inbound processing segments
- MMAL0002 EXIT_SAPLMEAI_002 ALE source list distribution: inbound processing user defined data
54. SRVMAS
Master data service master
- BASI0001 EXIT_SAPLBASI_001 Userexit IDoc inbound service master: segment
- BASI0001 EXIT_SAPLBASI_002 Userexit IDoc inbound service master: database
55. TPSSHT
Shipping planning system: Transfer planned shipments
- V56I0010 EXIT_SAPLV56I_010 IDoc TPSSHT01: Input of planned shipments: Modification of IDoc segments
- V56I0010 EXIT_SAPLV56I_011 IDoc TPSSHT01: Input of planned shipments: modification of transport tab, processing
- V56I0010 EXIT_SAPLV56I_012 IDoc TPSSHT01: Input of planned shipments: update of own tables
56. WHSCON
Delivery: Stock confirmation
- V55K0001 EXIT_SAPLV55K_001 Delivery (inbound): Take data
- V55K0002 EXIT_SAPLV55K_002 Delivery (inbound): Prepare processing
- V55K0003 EXIT_SAPLV55K_003 Delivery (inbound): Evaluate result
- V55K0011 EXIT_SAPLV55K_011 Shipping notification (inbound): Take data
- V55K0012 EXIT_SAPLV55K_012 Shipping notification (inbound): Prepare processing
- V55K0013 EXIT_SAPLV55K_013 Shipping notification (inbound): Evaluate result
57. WMBBIN
Block Storage Bins
- MWMIDI01 EXIT_SAPLLIDI_001 Customer enhancement for error handling of inbound IDoc
- MWMIDI04 EXIT_SAPLLIDI_004 Customer enhancement for IDoc WMBBID01
58. WMCATO
Reversal/Reversal request for transfer order
- MWMIDI01 EXIT_SAPLLIDI_001 Customer enhancement for error handling of inbound IDoc
- MWMIDI03 EXIT_SAPLLIDI_003 Customer enhancement for IDoc WMCAI01
59. WMINVE
Inventory count input
- MWMIDO07 EXIT_SAPLLMDE_001 Customer enhancement for error handling of inbound IDoc
- MWMIDO09 EXIT_SAPLLMDE_003 Customer enhancement for message WMINVE
- MWMIDO07 EXIT_SAPLLMDE_001 Customer enhancement for error handling of inbound IDoc
60. WMMBXY
IDoc Report goods movements in IM
- MWMIDO08 EXIT_SAPLLMDE_002 Customer enhancement for message WMMBXY (goods movement) inbound
61. WMSUMO
Move storage unit
- MWMIDI01 EXIT_SAPLLIDI_001 Customer enhancement for error handling of inbound IDoc
- MWMIDI06 EXIT_SAPLLIDI_006 Customer enhancement for IDoc WMSUID01
62. WMTOCO
Transfer order
- MWMIDI01 EXIT_SAPLLIDI_001 Customer enhancement for error handling of inbound IDoc
- MWMIDI02 EXIT_SAPLLIDI_002 Customer enhancement for IDoc WMTCID01
63. WMTORD
Transfer order
- MWMIDO07 EXIT_SAPLLMDE_001 Customer enhancement for error handling of inbound IDoc
- MWMIDO10 EXIT_SAPLLMDE_004 Customer enhancement for message WMTORD (Create TO) inbound
- MWMIDO11 EXIT_SAPLLMDE_005 Customer enhancement for message WMTORD (Create TO) inbound
64. WMTREQ
Create/Cancel transfer order
- MWMIDI01 EXIT_SAPLLIDI_001 Customer enhancement for error handling of inbound IDoc
- MWMIDI05 EXIT_SAPLLIDI_005 Customer enhancement for IDoc WMTRID01
65. WPUBON
POS interface: Upload sales documents (compressed)
- WPUE0002 EXIT_SAPLWPUE_104 IDoc WPUBON01: prior to inbound processing
- WPUE0002 EXIT_SAPLWPUE_105 Check, whether transaction of IDoc WPUBON01 is compressable
- WPUE0002 EXIT_SAPLWPUE_106 IDoc WPUBON01: processing user segment
- WPUE0002 EXIT_SAPLWPUE_109 IDoc WPUBON01: after to inbound processing
66. WPUFIB
POS interface: Upload Fin.Acc. interface SRS/POS
- WPUE0002 EXIT_SAPLWPUE_130 IDoc WPUFIB01: prior to update
- WPUE0002 EXIT_SAPLWPUE_131 IDoc WPUFIB01: processing user
67. WPUFIB
POS interface: Upload Fin.Acc. interface SRS/POS
- WPUE0002 EXIT_SAPLWPUE_132 IDoc WPUFIB01: prior to inbound processing
- WPUE0002 EXIT_SAPLWPUE_139 IDoc WPUFIB01: after to inbound processing
68. WPUKSR
POS upload cashier data
- WPUE0002 EXIT_SAPLWPUE_120 IDoc WPUKSR01: prior to update
- WPUE0002 EXIT_SAPLWPUE_122 IDoc WPUKSR01: processing user segment
- WPUE0002 EXIT_SAPLWPUE_123 IDoc WPUKSR01: prior to inbound processing
- WPUE0002 EXIT_SAPLWPUE_129 IDoc WPUKSR01: after to inbound processing
- WPUE0002 EXIT_SAPLWPUE_152 IDoc WPUTAB01: prior to inbound processing
- WPUE0002 EXIT_SAPLWPUE_159 IDoc WPUTAB01: after to inbound processing
69. WPUUMS
POS interface: Upload sales data (compressed)
- WPUE0002 EXIT_SAPLWPUE_110 IDoc WPUUMS01: prior to update
- WPUE0002 EXIT_SAPLWPUE_112 IDoc WPUUMS01: prior to inbound processing
- WPUE0002 EXIT_SAPLWPUE_113 IDoc WPUUMS01: processing user segment
- WPUE0002 EXIT_SAPLWPUE_119 IDoc WPUUMS01: after to inbound processing
70. WPUWBW
POS interface: Upload goods movements
- WPUE0002 EXIT_SAPLWPUE_140 IDoc WPUWBW01: prior to update
- WPUE0002 EXIT_SAPLWPUE_141 IDoc WPUWBW01: processing user segment
- WPUE0002 EXIT_SAPLWPUE_142 IDoc WPUWBW01: prior to inbound processing
- WPUE0002 EXIT_SAPLWPUE_149 IDoc WPUWBW01: after to inbound processing
71. WVINVE
Store physical inventory / sales price revaluation
- WVFI0001 EXIT_SAPLWVFI_001 Inbound IDoc store phys. inv.: override Customizing
- WVFI0002 EXIT_SAPLWVFI_002 Inbound IDoc store phys. inv.: process customer segment

User Exit for credit management at confirmed quantity in sales order

Dear All ,
kinldy tell how to define a user exit and where i can write for credit check to be done to the confirmed quantity in the sales order .
Also pls tell me that how to define the user exit and attach to customer reserve field in the customising for automatic credit control .
regards
Baranidharan Ramar

Hi
The following is the information from the sap documentation...you can also refer from IMG - SD - System modification - userexit - userexit for credit check
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.
This user exit allows you to determine whether the system should or should not carry out an availability check after a blocked document has been released or after a new credit check.
Thanks,
Ravi

Sales Order Line Items User Exit - Credit Management/ Exposure Calculation

Hello Folks
I am looking for a solution to a peculiar problem we have in credit management.
In case of Drop Ship sales order life cycle, the system automatically creates two line items per sales order - one each for Freight and Handling Fees. these are NOT relevant to schedule line delivery, nor are they billed to the customer along with the material billing. The default update rule for credit control area concerned is 12. The system, on finding line items not relevant to schedule line delivery automatically switches from rule 12 to 18. This leads to Open Deliveries field (S067-OLIWW) being updated instead of Open Orders (S066-OEIKW) on saving the sales order.
Once the sales order is billed for the material, the system should logically display net value as zero for the open order (as the 2 lines of fees and freight are not yet billed, the order is still open). But the system considers this figure at SALES DOCUMENT HEADER level and considers the net value as the total value of the sales document (including the material that is already billed).
What I am looking for is if there is an exit available whereby the system considers only those line items whose billing status indicator is "not complete". As such, the net value should be updated to the S067-OLIKW field net of the billed items.
Please advise if there is any such user exit available. Also, is there a way to customize this? We are exploring this at our end, but would appreciate an expert advise. Right advise will be awarded with brownie points
Regards
Mandar Barve

VKM1 uses FM SD_ORDER_CREDIT_RELEASE to release orders on credit.

How to create user credit control via customization

Hi !
I have to create user credit control via Transaction :
SPRO.
path:
Sales and Distribution->Basic Functions->Credit Management/Risk Management->Credit Management->Define Automatic Credit Control.
I want to check the user checkbox, and create my logic
of credit control.
In the help of credit control screen, it says that i have
to use user exits LVKMPTZZ and LVKMPFZ1.
However when i looked for that user exits at SMOD
that user exit don't exist !!!
How do i use those user exits ? Why can't i find those user exit ?
Can you give me please a code example of how to use
the user checkbox to change the logic of credit control ? or any material about the issue.
thanks
moshe

Hi,
You dont find the programs LVKMPTZZ and LVKMPFZ1 in SMOD transaction, check in SE38 by typing the program names, there you have the provision to write your custom code,
As user exits are specific to the business, it would be difficult to send the sample code to cater the functionality expected by your business,
Hope this helps,
Rgds,

User Exit after the credit release by VKM1/VKM3 (database commit)

Hi All,
We have a requirement where once the credit manager releases the order from block through transaction VKM1 or VKM3, an e-mail should be triggered stating that the order has been released.
I tried putting the code in EXIT_SAPFV45K_001(include ZXVVAU03 ) which checks the status in vbuk-cmgst for value 'D' and send the mail.But there are 2 problems with this appproach.
1) The database table VBUK is not getting updated at this stage.So the CMGST value doesnt change. Even the last change value in VBAK( VBAK-CMFRE) is not getting updated.
I tried Implementing this solution as well.
"Perform f0001_download_data on commit"
but even then the tables are not getting updated at this point.
2) This user exit is called in transaction VA02 as well.so the mail is getting triggered whenever someone saves anything in VA02. Chances are thetre might be other transacyions using this exit like va01.
Can anyone help me with this scenario? Is there any other user exit which can be used or any other way this can be done ??
Thanks
Shwet
Edited by: Shwet Priy Anand on Jun 29, 2010 7:16 PM

Output determination requires both config and development and it's the standard method for triggering document-related communications (printing, faxing, emailing, etc.). When you block or release a sales order for credit check, you are changing that order and thus you can use output determination to trigger any type of communication related to the change. There is a standard output type and standard requirements for credit holds; you can create your own for credit releases. You can find thousands of posts on this site related to output determination and emailing and there is an abundance of documentation in the IMG (SD -> Basic functions -> Output control) and in the help files.
Don't put emails in user exits unless it's a last resort - there's no error handling and logging available.

CREDIT MANAGEMENT - EXPOSURE CALCULATION USER EXIT

Hello Folks
I am looking for a solution to a peculiar problem we have in credit management.
In case of Drop Ship sales order life cycle, the system automatically creates two line items per sales order - one each for Freight and Handling Fees. these are NOT relevant to schedule line delivery, nor are they billed to the customer along with the material billing. The default update rule for credit control area concerned is 12. The system, on finding line items not relevant to schedule line delivery automatically switches from rule 12 to 18. This leads to Open Deliveries field (S067-OLIWW) being updated instead of Open Orders (S066-OEIKW) on saving the sales order.
Once the sales order is billed for the material, the system should logically display net value as zero for the open order (as the 2 lines of fees and freight are not yet billed, the order is still open). But the system considers this figure at SALES DOCUMENT HEADER level and considers the net value as the total value of the sales document (including the material that is already billed).
What I am looking for is if there is an exit available whereby the system considers only those line items whose billing status indicator is "not complete". As such, the net value should be updated to the S067-OLIKW field net of the billed items.
Please advise if there is any such user exit available. Also, is there a way to customize this? We are exploring this at our end, but would appreciate an expert advise. Right advise will be awarded with brownie points
Regards
Mandar Barve

Hi,
Actually I have got some User exits for credit checks...
LVKMPTZZ
LVKMPFZ1: USER_CREDIT_CHECK1
LVKMPFZ2: USER_CREDIT_CHECK2
LVKMPFZ3: USER_CREDIT_CHECK3
And trying with that also but looking for any other solution if it is available..
And using another Sales Document Type is not possible in this case..
Any inputs...?? anybody???
Thanks..
HP

Credit control procedure/user exit

Similar Messages

Maybe you are looking for