Blocking a particular customer for immediate delivery creation

Hi All,
I have the following requirement
Right now whenever the sales orders comes from the customers through EDI, the deliveries were created immediately. This was set up through the sales document. This is being used for the document KE.
Now we need to stop this immediate delivery creation for a particular customer when orders come through EDI.
We can not do this by blocking the customer for deliveries(VD05) because this will block all the sales documents for deliveries. We need this to happen only for KE.
We cannot remove the immediate delivery creation set up from the sales document(KE) because this will affect all the customers(for other customers this should create immediate delivery).
I feel this has to be controlled through a user exit.
In that case what should be the logic used?
What should be checked before blocking the delivery for a particular customer?
Please advise on this.
Thanks in advance for your help.

Harini,
I am sure you do not want to take the route of achieving this by u2018Userexitu2019
Here is the alternate solution by simple customizing.
You need to do it in two steps:
Step 1:  Define reasons for Blocking the delivery
IMG > Logistics Execution > Shipping > Deliveries > Define Reasons for Blocking in Shipping
Select :  Deliveries: Blocking Reasons/Criteria 
u2022  Define a blocking reason : say  ZZ u2013 delivery Hold.
u2022  Check  the Order check box
u2022  Save
Select:  Delivery Blocks
u2022   Assign  SO to Delivery ( I guess KE to whatever delivery type you have configured)
STEP 2:
Go to Customer Master record for whom you want to block them for normal process:
XD02 > enter customer master in change mode.
Select u2018Extrasu2019 tab in main menu
You see u201C sales and Distribution blocksu201D
Under this click on  delivery block ( for  All sales areas or desired sales area)
You will find the reason for blocking (ZZ)  you created in STEP 1
Assignu2019 ZZu2019  to this customer and save.
Thatu2019s itu2026u2026 !!!!!
When  a sales order received with this customer through your EDI, the order will be blocked for delivery.
One need to release the order manually by releasing this block
VA02 >  sales tab : remove the block from the delivery block
Hope this helps.

Similar Messages

  • BAPI for Outbound Delivery Creation with reference to Sales Order - VL01N

    Hi Everybody,
           We are in ECC 5.0 version.
           I want to create a enhancement for Outbound Delivery Creation with reference to a Sales Order.
           Is any BAPI available for this ?
           Any input on this will be very much helpfull.
           Please suggest any BAPI available for this, or should I go for BDC using VL01N or VL04 ?
           Thanks in advance.
    regards,
    Nagarajan.J

    Hi Nagarajan,
    The BAPI BAPI_DELIVERYPROCESSING_EXEC meets your requirement. You can create delivery with reference to sales order.
    The below is the sample code...
      data:lt_request      like bapideliciousrequest
                                    occurs 0 with header line,
           lt_createditems like bapideliciouscreateditems
                                    occurs 0 with header line,
           lt_return       like bapiret2
                                    occurs 0 with header line.
        lt_request-document_type      = 'A'.
        lt_request-document_numb      = vbeln.
        lt_request-document_item      = posnr.
      lt_request-material           = matnr.
      lt_request-plant              = werks.
      lt_request-stge_loc           = lgort.
      lt_request-quantity_base__uom = base_uom_qty.
      lt_request-delivery_date      = sy-datum.
      append lt_request.
      call function 'BAPI_DELIVERYPROCESSING_EXEC'
      EXPORTING
        DELIVERY_EXTEND       =
        TECHN_CONTROL         =
        tables
          request               = lt_request
          createditems          = lt_createditems
          return                = lt_return.
      loop at lt_return where type = 'A'
                          or  type = 'E'.
        exit.
      endloop.
      if sy-subrc <> 0.
    Use the BAPI for Commit
        call function 'BAPI_TRANSACTION_COMMIT'
             exporting
                  wait = 'H'.
      endif.
    Thanks
    Ramakrishna

  • BAPI for Outbound Delivery Creation with reference to Sales Order

    Dear all,
    I'm on R/3 4.6B platform and to develop an RFC for outbound Delivery creation instead of using the standard VL01N transaction.
    I've review BAPI for Outbound Delivery Creation with reference to Sales Order - VL01N thread which suggest BAPI_DELIVERYPROCESSING_EXEC .
    However, in 4.6B, that function module doesn't exist. Appreciate any suggestion and or workaround.
    Thanks.
    Steven
    Edited by: Steven Khoo on Mar 25, 2010 7:13 AM
    Edited by: Steven Khoo on Mar 25, 2010 7:14 AM

    Not required anymore

  • Immediate Delivery Creation on Sales Order Save

    Hi,
    For one my scenario I want delivery to be created immediately after saving the sales order.
    For which i have set the immediate delivery'X' in the sales document type. But when i create the sales order, which is confirmed for today, delivery is not immediately created.
    Let me know what could be the possible reason for this and is there any other place i need to make additional settings?
    Thanks

    Hi there,
    I guess that materials will be maintained in separate storage loc to process immediate delivery scenarios in your company sothat item is confirmed for today.
    When immediate delivery is not happening, thenit means that the system is not calling the delivery creation prog immediately after order save.
    So in sales order prog MV45AFZZ put a code that if the order has to create immediate delivery (like rush orders SO, cash sale BV), system should check if the material is confirmed for today. If yes, it should call delivery creation prog SAPMV50A
    Regards,
    Sivanand

  • User exit to change partner for inbound delivery creation

    Hello,
    I have a requirement to change the partner number for
    the inbound delivery creation.
    I only see the USEREXIT_MOVE_FIELD_TO_LIKP but I am not sure if this is
    the right user exit for this requirement.
    Is there the user exit for modifying partner in the inbound delivery?
    Thanks in advance,

    HI
    There is a program with which you can find the available exits as per your requirement. You have to execute the same and give your transaction code. Hope this helps...
    *& Report  ZFINDUSEREXIT
    report  zfinduserexit.
    tables : tstc, tadir, modsapt, modact, trdir, tfdir, enlfdir.
    tables : tstct.
    data : jtab like tadir occurs 0 with header line.
    data : field1(30).
    data : v_devclass like tadir-devclass.
    parameters : p_tcode like tstc-tcode obligatory.
    select single * from tstc where tcode eq p_tcode.
    if sy-subrc eq 0.
    select single * from tadir where pgmid = 'R3TR'
    and object = 'PROG'
    and obj_name = tstc-pgmna.
    move : tadir-devclass to v_devclass.
    if sy-subrc ne 0.
    select single * from trdir where name = tstc-pgmna.
    if trdir-subc eq 'F'.
    select single * from tfdir where pname = tstc-pgmna.
    select single * from enlfdir where funcname =
    tfdir-funcname.
    select single * from tadir where pgmid = 'R3TR'
    and object = 'FUGR'
    and obj_name eq enlfdir-area.
    move : tadir-devclass to v_devclass.
    endif.
    endif.
    select * from tadir into table jtab
    where pgmid = 'R3TR'
    and object = 'SMOD'
    and devclass = v_devclass.
    select single * from tstct where sprsl eq sy-langu and
    tcode eq p_tcode.
    format color col_positive intensified off.
    write:/(19) 'Transaction Code - ',
    20(20) p_tcode,
    45(50) tstct-ttext.
    skip.
    if not jtab[] is initial.
    write:/(95) sy-uline.
    format color col_heading intensified on.
    write:/1 sy-vline,
    2 'Exit Name',
    21 sy-vline ,
    22 'Description',
    95 sy-vline.
    write:/(95) sy-uline.
    loop at jtab.
    select single * from modsapt
    where sprsl = sy-langu and
    name = jtab-obj_name.
    format color col_normal intensified off.
    write:/1 sy-vline,
    2 jtab-obj_name hotspot on,
    21 sy-vline ,
    22 modsapt-modtext,
    95 sy-vline.
    endloop.
    write:/(95) sy-uline.
    describe table jtab.
    skip.
    format color col_total intensified on.
    write:/ 'No of Exits:' , sy-tfill.
    else.
    format color col_negative intensified on.
    write:/(95) 'No User Exit exists'.
    endif.
    else.
    format color col_negative intensified on.
    write:/(95) 'Transaction Code Does Not Exist'.
    endif.
    at line-selection.
    get cursor field field1.
    check field1(4) eq 'JTAB'.
    set parameter id 'MON' field sy-lisel+1(10).
    <b>Do reward if useful...</b>
    Regards
    Dinesh

  • BAPI for AFS Delivery creation

    Hi all,
    Does anyone know which BAPI can be used for creating Delivery for AFS items with ref to Sales Order ?
    I tried BAPIs like BAPI_OUTB_DELIVERY_CREATE_SLS but there's no field to input schedule line number. So all content I input is not to SL-level but only to Sales order item level.
    Thanks!
    Edited by: George Sung on May 27, 2010 12:16 PM

    Dear Kumar/All
    Is it possible to create AFS PO using bapi_po_create1 with  delivery schedules
    if you done that , kindly let me know it will be of great help.
    thanks
    Prabhu Shanmugham

  • Confirmation control key check for inbound delivery creation

    Hi,
    Currently, in the Client's company, the process of receiving goods from purchase orders looks like that (SAP-wise):
    - create a purchase order,
    - receive goods using MIGO and automatically create an inbound delivery,
    - pack the delivery and post goods receipt.
    Recently, some patches have been installed, including one described by note 1602047 (which basically enforces checking confirmation control keys if goods receipt assignment and goods receipt relevance are activated for inbound deliveries). Note says that it only affects two-step stock transfer and creation of automatic inbound deliveries using SPED output but it seems it also affects other basic processes like PO receipt in MIGO.
    Now, when using the old control key (that had MRP-Relevant and GR-Relevant fields checked), the system is unable to automatically create an inbound delivery after the goods receipt is posted with MIGO (with message VL148 - Not possible to create an inbound delivery). I learned that this is because the "GR Assignment" field must be checked in the confirmation control key so it's possible to automatically create aninbound delivery after receiving a purchase order in MIGO.
    After changing the confirmation control key to have the missing field checked it's not possible anymore to receive goods from PO in MIGO as the PO requires shipping notification in order to be processed in MIGO thus requiring of manual creation of an inbound delivery.
    Is there any way to skip this check so the process would remain the same (this model has been working fine for few years in the Client's system) and the inbound delievery would be created automatically after posting the receipt in MIGO?
    Thanks in advance,
    Piotr

    Hi,
    don't know if you found a solution, but we received the following message from SAP:
    The advent of the new version requires some attention to the users. It
    was necessary to avoid inconsistencies which in the past version the
    system was susceptible.
    Main Program SAPMM07M
    Source code of MM07MLVS
    sy-msgid VL sy-msgty E sy-msgno 148
    I have checked the process and through debugged I could confirm the
    following information SAP is providing to all similar incidents reportedfor us:
    Error message VL 148 is issued if in the confirmation control key used
    in the purchase order, the fields for MRP-relevance (T163G-KZDIS),
    GR relevance (T163G-WEREL) and GR assignment indicator (T163G-WEZUO)
    are not set.
    The correction of note 1602047 was necessary to avoid inconsistencies
    (table EKES) in the purchase order. Without having the GR assignment
    (T163G-WEZUO) set, there is no unique reference created between the
    purchase order history (table EKBE) and the inbound delivery
    confirmation (table EKES) at goods receipt which leads to a problem if
    several inbound deliveries exist for the same purchase order.
    If you set T163G-WEZUO to 'X', this assures that, for an inbound
    delivery, the confirmation record (EKES) belonging to this inbound
    delivery (EKES-VBELN) is also accurately updated at goods receipt.
    How to solve the issue?
    Use a confirmation control key with the GR assignment indicator set
    and then create the inbound delivery with VL31N. If you want to be able
    to create the inbound delivery with reference to a certain line item in
    the PO, use transaction VL34.
    If you still want to use transaction MIGO, there is the following
    workaround:
    - Create a purchase order without any confirmation control key
    - Create a goods receipt (GR) in transaction MIGO with reference to this PO and post the GR to a non-HU-managed storage location
    - Create a transfer posting with MIGO using movement type 311 to
    transfer the goods from the non-HU-managed storage location to the
    HU-managed storage location.
    As the transfer posting is an additional step for the user, the whole
    process could be automated using a partner storage location
    (T001l-PARLG) for the GR which then triggers (through a modification)
    the BAPI 'BAPI_GOODSMVT_CREATE' to create the transfer posting without
    user interaction.
    I hope to have satisfied you on the reason why it is now happening and
    also I believe you can explain to business that it is a new behavior
    necessary done from SAP side to avoid worse situations, we are aware of
    potential dissatisfaction it might cause. SAP Support is always
    available to clarify any issue.
    Sorry for not having a more positive answer.
    I hope it helps!
    Leentje

  • Blocking a particular vendor for doing Migo in his account

    Dear Guru's
    My question is that is it possible to block a vendor so that no transaction can be done in his vendor account number. For example in our senario duplicate vendor number has been created for a particular vendor number and now i want to block one account so as nobody can do MIGO,MIRO or any payment in his account is it possible. I have tried with XK05 total block but it is not working . Problem is that before blocking many PO of that vendor is standing and they are reciving the material from that Po and system is allowing it to do so.
    Therefore i want to block the vendor so that no transaction can be done in his account. Kindly help me out

    Hi.
    I am Basically MM guy. To resolve this issue I would like to suggest a work around.
    You can use the two payment terms.
    1) One payment term in the company code (In vendor master record in the Payment transaction accounting). In this payment term you have set a payment block indicator
    By doing this system will block all the invoices or Down payment which are posted in FI. Against this vendor. Hence system will not allow you to pay to this vendor against down payment.
    2) Another payment terms in the purchasing view of the Vendor master. In this payment terms do not set any block.
    When you post an invoice against a PO your accounting document will not be blocked.
    Hence you can pay to a vendor with reference to PO invoice.
    I am not sure. I hope it will work. If it helps award me.
    Cheers
    Umakanth

  • BAPI for inbound delivery creation

    Hi,
    I have to create and modify inbound deliveries from a code, so I'm wondering if exists any BAPI (or function module) to create or modify inbound delivery.
    Thanks in advance

    This is an example of BAPI_INB_DELIVERY_CHANGE. It is in the documentation of the function
    I hope it helps you...
    Example
    If you want to change the quantity for a distributed quantity, then following entries are required for the transfer to the connected system:
    In the header data of inbound delivery parameter (HEADER_DATA)
    The delivery number (DELIV_NUMB)
    In parameter item data of inbound delivery (ITEM_DATA)
    The delivery number (DELIV_NUMB)
    The delivery item (DELIV_ITEM)
    The delivery quantity in sales unit (DLV_QTY)
    The actual delivery quantity in base UoM (DLV_QTY_IMUNIT)
    The sales unit (SALES_UNIT)
    The ISO code for the sales unit (SALES_UNIT_ISO)
    The base unit of measure (BASE_UOM)
    The ISO code for the base unit of measure (BASE_UOM_ISO)
    In the control of the inbound delivery at item level parameter (ITEM_CONTROL)
    The delivery number (DELIV_NUMB)
    The delivery item (DELIV_ITEM)
    The Change Delivery Quantity indicator(CHG_DELQTY)

  • IDoc or BAPI for inbound delivery creation with reference to PO.

    Hi
    I have requirement to create a inbound delivery, I  will get a ASN from external system with PO, Vendor Material number & batch. I want to know is there any BAPI or IDoc that can be used to create inbound delivery in R/3. I used BBP_INB_DELIVERY_CREATE to create inbound delivery and I was successful but problem is that inbound delivery was not updated with Vendor Material number & Batch.  Can some one suggest me any other BAPI or IDoc ?
    Thanks in advance
    Nagendra P Boggarapu
    Edited by: Nagendra P Boggarapu on May 6, 2010 4:06 PM

    Use Delvry0* IDOC.
    Reddy

  • Issue in automatic delivery creation

    Hello,
    This is to reframe the issue again and give you some more details on
    this issue –
    As per SAP standard we have configured our salers order for
    immediate delivery creation with a default delivery block – XX. Hence
    as
    per config whenever we create a sales order, it gets created with a
    default delivery block – XX which later on users removes manually and
    system subsequently as per design creates the delivery document
    automatically.
    We are facing two issues in case of sales order design –
    1. Some time even after removing the delivery block –XX manually,
    system do not create the delivery document automatically against those
    sales order.
    2. Some time if sales order is created with a credit block in
    addition to Delivery Block – XX, system doesn’t create automatic
    delivery document against those sales orders even after releasing /
    removing the credit block as well as Delivery block.
    But if you just open those sales orders in VA02 and make any change for
    example – Carry out new pricing Or carry out Availability check for any
    one item and save the sales order without making any change into it,
    system is creating delivery document against that sales order
    automatically.
    This issue is happening sporadically. There is no specific pattern
    where
    this issue is happening. This is an inconsistent issue. We could not
    replicate this issue in any of our Non-production SAP system.
    Whenever we tried to investigate it in debug mode for the sales orders
    where this issue has happened, it worked well and created delivery
    document automatically.
    Requesting you to kindly look into this issue again and help us to fix
    it as early as possible.
    Thanks and Best Regards,
    Pankaj Jain

    Hi,
    plz confirm if the automatic delivery creation is activated to few sales order types
    as it is most frequently used for Cash sales and Rush Orders
    more ever Credit check not Applicable for cash and rush sales

  • Blocking a partcular batchnummber for a bussiness partner

    Hi all,
    It's possible to block a particular batchnumber (at article level) for deliveries/goods receipt, or block it for all movements etc.
    Is it also possible to block a particular batchnumber for delivery to a certain business partner?
    In the batchmanagement there's no possibillity to do this.
    We can ofcourse create a udf field at row level in the sales order to put information in for the pickinglist, but is it maybe possible in an other way?
    Any suggestion?
    Best regards,
    Carl Verhagen

    You can try to use the Batch Status for this as an workaround.
    Status : Displays the current batch status as follows:
    Released u2013 enables you to perform transactions on a batch.
    Not Accessible u2013 you cannot release a batch in a sales document or an A/P credit memo, because the status defines the batch in the middle of a production process or a quality check. However, you can release a batch in a stock transfer document.
    Locked u2013 you can release the batch in stock documents only, for example, a stock transfer or goods issue.
    You can have the Batch Status as Not Accessible/ Locked depending upon the requirment.

  • Billing block at the customer level.

    I have defined a billing block and have assigned that block to a customer for a particular sales area. After that I created an order for that customer. I was assuming that the Billing Block field on the sales order will be populated with the block I assigned at the customer level. But that is not happening. Am I missing some step or is this the standard process, that the billing block assigned at the customer level will not appear on the sales order and this comes into picture only when I try to create the invoice?

    Hi Ginu
    Billing Block will not worked if you did not assign it
    Define the possible block indicators in SM30 - V_TVFS 
    and 
    allocate them to the billing types concerned in SM30 - V_TVFSP.
    Your Billing Block will not worked if you did not assigned it to the desired billing types.
    You can auto block by :- 
    1.  sales document type in transaction VOV8, fields Billing Block,
    or
    2.  item categories in SM30 - V_TVAP, by filling the fields Billing Block.
    Reward if useful to u

  • Block Sales Document type for a set of customers

    Hi,
    I have to block the processing of particular sales document type, say XX or a scheduling agreement for a specific set of customers. Can anyone suggest me some inputs on this.
    Thanks in advance
    Suresh

    Thanks all for quick response.
    1. By blocking the sales document type by setting the block in VOV8 will not allow u to process that particular sales document type at all.. ie for all customers..But my problem is to block, say ZCAL for particular set of customers only..say customer 1234 of sales org 0001, customer 2132 of sales org 0001, customer 1315 of sales org 0002 etc..Apart from these setof customers, it should be able to process the document type for other customers.
    2. By blocking the customer in VD05, it will block the customer for all sales operations. But i dont want to block the same customer for other sales document types.. Say, it should be blocked for ZCAL but not for all document types.
    My requirement:
    When we create an scheduling agreement, we give the sales area in the initial screen and enter. Then we give the Sold to party.Here it should check whether the customer entered is in the list of customers blocked for scheduling agreement. If so, it should pop up an error message stating" you cannot process scheduling agreement for customer X" If not, it should allow further processing.
    I will try with the suggested User exit.
    Please suggest if u have got any more ideas.
    Thanks
    Suresh

  • The userexit is not working in integration scenario- inb. delivery creation

    Hi Experts please help,
    We know that vl31n is for inbound delivery creation.
    in one of the userexits of vl31n, I did code ( shifting the batch to vendor batch )...
    So,the user enters batch number under batch field and
    fill all other required information and saves to create inbound delivery.
    Whilw inbound delivery creation my coding in user exit gets executed and shifts the batch number to Vendor batch field.
    This we observed when we check in vl32n or vl33n, the batch entered shifted to Vendor batch field() batch field is space.
    This is working fine with vl31n inb. delivery creation.
    But in integration testing it failed.
    In Integration, what is happening the other system called "ICH" is creating ASN (shipping note) with the batch number, which inturn created the inbound delivery in R/3 via XI as shown like below.
    Integration scenario :
    ICH System (ASN)   --> XI -->  R/3 System (Inb. delivery creation)
    So when "ICH" triggers ASN to R/3 the inbound delivery creation is happening but the batch number is not shifting to vendor batch field.
    when we open the inbound delivery in vl32n, the batch number is under batch field only...it should be under vendor batch field.
    My understanding is my user exit coding of vl31n not getting executed in the integration process.
    Kindly help me what can I do to shift the batch sending from ICH to shift to vendor batch field.
    Please let me know if I could not explain the scenario.
    THANKS IN advance.
    YOUR HELP WILL BE GREATLY APPRECIATED.

    the ASN from ICH, it uses a standard idoc function module IDOC_INPUT_DESADV1 and there is one user exit EXIT_SAPLV55K_012 which calls ZXTRKU07
    need to code there.
    solved by meetings with some other experts.
    THANKS.

Maybe you are looking for