Skip to Content
avatar image
Former Member

Exceed Credit limit in sales order requirements not tranfer to MRP

Hi SAP Gurus,

I have one intergration issue of SD and PP.That is,In make to order when the credit limit exceed to thatcustomer in sales order requirements not to transfer to MRP(Material Requirement Planing).

For Exp: Credit exceed 10000/- for customer, sales order has to save.But requirement should not pass MRP like MD04.

Advance Thanks

Regards

Vikram.M

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • avatar image
    Former Member
    Mar 13, 2007 at 05:43 AM

    Hi Vikram,

    Yes this can be done with OVZ7 by ticking Conf. Block.

    Reward if it helps

    regards

    Srini

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Srinivas,

      Thanks for kind reply,but OVZ7 only its not conform the order quantity.For my client issue should not pass to MRP like not to go Production.

      Regards

      Vikram.M

  • avatar image
    Former Member
    Mar 13, 2007 at 06:28 AM

    Hi Vikram,

    You should try and use one of the standard requirements.

    See in transaction "VOFM".

    Under Requirements / Subsequent Functions / Reqs.Availablity.

    Try using routine 103, you may have to tweak if it doesn't work exactly as you'd like.

    For example, you can write a routine 903 because you only wanted this reaction for certain business units. Irregardless, using a routine similar to this will prevent the requirement from appearing in MD04 for orders blocked on credit.

    Code:

    DATA: W_ZSDCRD TYPE ZSD_CREDITBLCK.

    DATA: W_CMGST LIKE VBUK-CMGST.

    SELECT SINGLE * INTO W_ZSDCRD

    FROM ZSD_CREDITBLCK

    WHERE KKBER = VBAK-KKBER

    AND CTLPC = VBAK-CTLPC.

    IF SY-SUBRC = 0 AND VBUK-CMGST CA 'B'.

    IMPORT VBUK-CMGST TO W_CMGST FROM MEMORY ID 'CREDIT'.

    IF W_CMGST = SPACE.

    MESSAGE I706(Z1).

    EXPORT VBUK-CMGST TO MEMORY ID 'CREDIT'.

    ENDIF.

    *} REPLACE

    *{ INSERT DEVK966908 1

    *} INSERT

    • Read the subsequent function information for the message

    PERFORM FOFUN_TEXT_READ USING GL_FOFUN

    CHANGING FOFUN_TEXT.

    MESSAGE ID 'V1' TYPE 'E' NUMBER '849'

    WITH FOFUN_TEXT

    RAISING ERROR.

    *{ INSERT DEVK966908 2

    *} INSERT

    ENDIF.

    ENDFORM.

    Please take the help of your abaper to do this. Please reward if it answers your requirement.

    Thanks & Regards

    Sadhu Kishore

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Sadhu,

      I have a similar problem as this thread. We are implementing a new process by which instead of putting a sales order directly on a plant which will do the assembly (and where the production order is created), we putting a process in place where we place a sales order on Plant XXXX, but after MRP runs, the requirements will be passed on to Plant YYYY, where a Production Order will be created.

      The issue we have run into is that even though the sales order may fail the credit checks, once MRP is executed the requirements to go create the production order are passed on to Plant YYYY. We do not want this to happen. Our goal is to put something in place which will prevent the passing of requirements once MRP is executed UNTIL the sales order has been released from credit hold.

      I sat with an ABAP'er and we went over the code provided in your original response. However, I did not understand how creating a routine, such as 903 would prevent the requirements from showing up in MD04. Could you explain a bit further, so I can follow your logic? Thanks.

      One thing we were thinking of doing was putting a user-exit in place to change the schedule line category from CP to CN to prevent the requirements from being passed on (when the order was on credit hold) and then changing the schedule line category to CP (once it was released from credit hold). However, this seems very messy to accomplish. I would think there would be a better way of getting this done, as opposed to changing the schedule line categories on the order.

      Would appreciate any additional help. Thanks.

      Tom Brown

  • avatar image
    Former Member
    May 30, 2007 at 03:17 AM

    Hi All,

    We needn't require any user exits for these sort of requirements.

    Just put a reason for rejection in your sales order items and your requirements will not pass to MRP.

    By putting reason for rejection ,your order status will be completed and hence no requirements to MD04.But just do a small config explained by me below.

    In order to make your reason for rejection successful ,just do a small configuration.

    speosd-sales-sales document item-reason for rejection.

    under reason for rejection just tick the blocked for billing field for a particular reason for rejection.

    Rest everything will be done.

    No need of taking any help from ABAPer.

    In future if you want to put the requirements to MRP ,just search all the orders for that reason thru table VBAP and remove the reason for rejection.

    Reward points if it helps.

    Regards

    Karan

    Add comment
    10|10000 characters needed characters exceeded