cancel
Showing results for 
Search instead for 
Did you mean: 

Help with bypassing credit check during V_V2

0 Kudos

I have created a requirement to bypass the credit check for orders that have previously been released. (VBUK-CMGST = D) The requirement is listed in the "No Credit Check" field in the credit risk category.

IF xvbak-netwr <= yvank-netwr

          IF xvbuk-cmgst = 'D'

          bypass-static_limit          =     'X'

          bypass-documentvalue  =     'X'

          bypass-open_items        =     'X'

          bypass-oldest_op           =     'X'

          status_reset-static_limit          =     'X'

          status_reset-documentvalue   =     'X'

          status_reset-open_items        =     'X'

          status_reset-oldest_op           =     'X'

     ENDIF.

ENDIF.

This code is not working during the V_V2 rescheduling jobs. The credit department will release the orders via transaction VKM1 and the next day the rescheduling job will run and the order will go back on credit hold. Each time the V_V2 will run it changes the status in the VBUK-CMGST field. The value will go from 'D' to blank, V_V2 will run again and the value will go from blank to 'B'. Putting the order back on hold. The net value of the orders are not changing during V_V2. Only schedule line dates are changing in the order. If anything even changes at all.

I also have 999 listed in the "Number of Days" field for a released document to go unchecked.

Neither the requirement nor the configuration are preventing the orders from going back onto credit hold once they've been released.

Does anyone have any suggestions on how to keep orders from going back on credit hold once it has been released?

Thanks,

Hollie

Accepted Solutions (0)

Answers (1)

Answers (1)

0 Kudos

We determined that when dealing with the credit, the older orders needed to filter thru before picking up the changes. Once they were re-released, they did not go back on hold.