Skip to Content

Regarding parameters of LVKMP001

Hi.
I have implemented LVKMP001 from Tr-cd: OVA8 to bypass credit check.

But, I don't know what effect below parameters. If you can, let me know the effect.


BYPASS-SECURITY
BYPASS-STATIC_LIMIT
BYPASS-DYNAMIC_LIMIT
BYPASS-DOCUMENTVALUE
BYPASS-CRITICAL_FIELDS
BYPASS-REVIEWDATE
BYPASS-OPEN_ITEMS
BYPASS-OLDEST_OP
BYPASS-DUNNING_LEVEL
BYPASS-USER1
BYPASS-USER2
BYPASS-USER3
BYPASS-CREDIT_MANAGEMENT

I think, "BYPASS-CREDIT_MANAGEMENT" is parameter to bypass credit check.

I atached screen shot regarding the parameters. Please see that.

Best regards.


ova8.png (128.4 kB)
parameters-1.png (180.5 kB)
parameters-2.png (110.0 kB)
Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Best Answer
    Posted on Jul 15, 2020 at 09:12 AM

    By stating that you have implemented LVKMP001 you probably mean that you have simply assigned the example routine delivered in standard in OVA8.

    This is probably unwise, because the routine is just an example, you have to create your own routine in the customer name range and adapt the logic to your needs.

    The meaning of the bypass statement is explained in note 895630 - Use of the requirement "No check".

    BYPASS-CREDIT_MANAGEMENT bypasses the credit checks if you use FSCM Credit Management as explained in note 2469457 - Bypass credit check in custom routine in SAP Credit Management(FSCM).

    The other parameters which you mentioned influence the corresponding checks in SD Credit Management.

    Speak with your functional consultant to find out for which of these solutions you have to bypass credit checks - SD Credit Management or FSCM Credit Management.

    Edit: now i saw that you have added tag S/4HANA. If you are on S/4HANA, then you are right, BYPASS-CREDIT_MANAGEMENT is the correct parameter to bypass credit checks for S/4HANA systems.

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi Peykova.

      Thank you for your comment! :)

      >>well, you will have to specify when to bypass credit check, not just bypass it unconditionally

      I see, typically the credit check will be run, but when it was called by BAPI "BAPI_SALESORDER_SIMULATE", we bypass the credit check. We control the identification by "ABAP MEMORY".

      ( We set a flag before call "BAPI "BAPI_SALESORDER_SIMULATE" to identify who calld the program )

  • Posted on Jul 15, 2020 at 08:06 AM
    -1

    Can you please share as to why you want to bypass the credit check and why you have gone for an enhancement ? Some times, with the standard configuration and master data, the Business requirements can be met.

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi, Ganesan. Thank you for your response.

      I will explain the background below.
      In our project, we receive a interface file to resister a sales order.
      The program which resistor a sales order is triggered by daily job schedule.
      The program will call 2 standard BAPI
      "BAPI_SALESORDER_SIMULATE"
      and
      "BAPI_SALESORDER_CREATEFROMDAT2".

      * "BAPI_SALESORDER_SIMULATE" is for a check before register


      If we don't address any more then credit check will run 2 times. It made performance degradation.
      So, I would like to bypass credit check when "BAPI_SALESORDER_SIMULATE" called.

      According to OSS's suggesting, if we implement a customer logic via OVA8 then we can bypass the credit check. but there are lot of parameters in the logic LVKMP001. I would like to make sure the effective of parameters before release to PRD environment.

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.