Delivery Creation Issue - Intercompany STO

Dear All,
I had configured the Intercompany stock transfer scenario. When I am trying to create a delivery, I am getting the below message.
"When the system checked whether saving delivery was
permitted, it determined that the requirements stored in
Define Incompletion Procedures for this document do not
allow this subsequent function."
I had removed the incompletion log assignment from the Delivery type NLCC & Item category NLC.
But still I am getting the error.
What may be the issue?
Rgds,
Senni.B

Hi,
Check whether Checcking Rule is assigned to the Purchase order type, Delivery type in ONGN and also check on the settings for the Checking Rule in OMGN

Similar Messages

  • Delivery Creation for an STO - Help needed!!

    I have a requirement to update an STO ( quantities etc) , subsequently create a Delivery for the changed STO .... Now , the processing is, of an Inbound IDoc by a Custom Function Module .... Initially I was creating the delivery with a BDC on VL10B ... it was working fine whenever we processed an IDoc template in WE19 or reprocess an IDoc using BD73... Now, whenever an actual IDoc is received from the external system , the VL10B transaction fails ( GUI exception is raised).... According to OSS note 310022 , VL10* transactions do not have GUI support .. the note also mentions that the solution to the problem is to call the background program RVV50R10C ....
    I used a SUBMIT within my function module to RVV50R10C supplying the necessary selection parametes ... but the problem still persists .... In ST22 .. the dump for the rfc user is appearing as:
    "The termination occurred in the ABAP program "CL_GUI_CUSTOM_CONTAINER=======CP"
    in "CONSTRUCTOR".
    The main program was "RVV50R10C ". "
    Please help !!! Top priority problem!!!

    Try using the function module BAPI_DELIVERYPROCESSING_EXEC instead:
    Ex:
    form bapi_create_deliveries tables gtab_data structure zre029_crea_del
                                using  gw_ebeln
                                gw_tcode.
      data: ptab_request type  bapideliciousrequest occurs 0 with header line,
            ptab_items   type table of bapideliciouscreateditems,
            ptab_return  type table of bapiret2,
            pwa_request  type bapideliciousrequest.
      data: pw_error_occured,
            pwa_return type bapiret2,
            pwa_data   type zre029_crea_del.
    *        gw_frgzu   TYPE ekko-frgzu.
      constants: begin of pw_msgty,
                   error      like syst-msgty value 'E',
                   abend      like syst-msgty value 'A',
                   warning    like syst-msgty value 'W',
                   info       like syst-msgty value 'I',
                   success    like syst-msgty value 'S',
                 end of pw_msgty.
      clear gtab_data.
      loop at gtab_data into gwa_data.
        ptab_request-document_type          = 'B'.
        ptab_request-delivery_date          = sy-datum.
        ptab_request-document_numb          = gw_ebeln.
        ptab_request-document_item          = gwa_data-ebelp.
        ptab_request-quantity_sales_uom     = gwa_data-menge.
        ptab_request-sales_unit             = gwa_data-meins.
        ptab_request-document_type_delivery = 'NL'.
        append ptab_request.
      endloop.
      call function 'BAPI_DELIVERYPROCESSING_EXEC'
        tables
          request      = ptab_request
          createditems = ptab_items
          return       = ptab_return.
    * check protocol
      loop at ptab_return into pwa_return.
        if pwa_return-type = pw_msgty-error or
           pwa_return-type = pw_msgty-abend.
          message id pwa_return-id type pwa_return-type
                                  number pwa_return-number.
          pw_error_occured = 'X'.
          message e001(vl) with 'Unable to create deliveries, errors with BAPI!!!'.
          exit.
        endif.
      endloop.
      if pw_error_occured is initial.
        call function 'BAPI_TRANSACTION_COMMIT'
          exporting
            wait = 'X'.
      endif.
    Leonardo De Araujo

  • Delivery creation issue - Inter Company STO

    Dear All,
    I had configured the Intercompany stock transfer scenario. When I am trying to create a delivery, I am getting the below message.
    "When the system checked whether saving delivery was
    permitted, it determined that the requirements stored in
    Define Incompletion Procedures for this document do not
    allow this subsequent function."
    I had removed the incompletion log assignment from the Delivery type NLCC & Item category NLC.
    But still I am getting the error.
    What may be the issue?
    Rgds,
    Senni.B

    what did you specify in OSS search? I used VL10 User Exit, and got the desired results.
    A summary of all user exits from Include RVV50TOP is contained in the advance corrections as comment Includes.
    Through this, every user exit can be accessed by forward navigation from Include RVV50TOP via Include V50R_USEREXITS.

  • EDLNOT - Delivery creation issue

    Hi
    I had a quick question on EDLNOT message type of IDOC. Please let me know the answer when you get a chance.
    here document flow here is as follows:
    Scheduling agreement LK =>
    Delivery into Consignment storage location =>
    ED-Order (pick up from the consignment storage location) =>
    Delivery to the customer.
    We use inbound EDLNOT (DESADV01) . The inbound The EDLNOT has to create the ED-Consignment Order.
    Function Module - IDOC_INPUT_EDLNOT_START
    Inbound Prcoessing code - EDLN
    OVD0 - Settings done
    *****************************************************************Problem.....
    Delivery by ext. agent created successfully but outbound  delivery is not created .
    Please see the message : Delivery by ExtAgent 8053513 has been saved (no delivery created)
    Please help me is there any seetings needs to be maintained for outbound delivery and PGI creation .
    Thanks,
    Shankara Narayanan G
    Edited by: ShankarG on Aug 6, 2009 11:26 AM

    Hi,
    Check whether Checcking Rule is assigned to the Purchase order type, Delivery type in ONGN and also check on the settings for the Checking Rule in OMGN

  • Delivery creation date under shipping tab in STO

    Dear Experts,
    please explain me how the Delivery creation date is calculated IN STO order, and the same date is carried to the MRP date of Supplying plant in MD04.
    thanks
    Satya

    Please check these answered links:
    Delivery Creation date in STO
    Re: Delivery dates in STO
    STO Delivery date
    Edited by: Afshad Irani on Apr 29, 2010 10:04 AM

  • Rework batch stock not propose at a time of delivery creation,

    Hi, Experts,
    I have face one issue at a time of delivery creation:
    Issue : All FG stock availbale in table MSKA , that all stock prapose in availibility run in SO but the same quantity not prapose in delivery document,
    For example : In table MSKA , Initially stock is 100 with 10 batch with 10 quantity fo each batch, Out ot 10 , 2 batch marked for rework, & that batch against consumption (261) also done, AFter consumption in MSKA stock available 80,
    But when we create delivery document , System propose only 60 quantity insted of 80, Actully FG stock availble 80 in table MSKA,
    In SO - Availibility run time system propose 80 quantity, Only delivery time propose 60 quantity,
    We are using MTO scenarion in my company,
    Pls revert me with solution, Any Std. configuration is missing for rework process,
    Request you to alos send me which STd.configuration require for rework process,
    Thanks a lot in advance,
    Regards:
    Happy,

    Resolved,

  • Intercompany STO Delivery Creation

    Hi  Experts
    Scenario: Intercompany STO Delivery creation.
    When delivery creation though Tcode - VL10B, in the shipping side if no enough stock, is it possible stop creating delivery orders and  to throw error.
    I dont want to use the P.O side ATP check settings, as P.O raising shouldn't be stopped.
    Appreciated your help.
    Regards
    GJ

    Hi
    OVLP - Avilablity Check Indicator is Set Blank already.
    However, currently even if no stock also still the delivery order able to be created by VL10B. Just only can't do PGI.
    Requirement is First place the delivery creation in VL10B itself to stopped by showing error as deficit of stock for the material.
    All the settings in Purchasing --> Purchase Order --> Setup stock transport order seems it relevant to the Purchase Order not to control the delivery creation.
    Appreciated further advise.
    Regards
    RG

  • Creation of  Sales Order throogh Intercompany STO

    Dear SAP Gurus,
    I have a question
    In the intercompany stock trasnport orders.As per the standard process
    i) Creation of STO
    ii) Creation of replenishment delievry.
    iii) Goods Issue from the supplying plant.
    iV) Good receipt at the receiving plant.
    Our requirement is to create a sales order through IDOC in place of delivery at the delivering company code.
    All the subsequent docuements like delivery and shipment will be based on this newly created sales order.
    I want to know primarily that is there anyway of creating a sales order instead of Delievery subsequent to creation of STO.
    IF so how can we disable the SAP standrad process ( Std Intercompany STO process) and enable our requirement.
    A quick response is highly appreciated.
    Regards
    Ganesh

    Hi,
    You can create sales order in the background while creating intercompany purchase order.
    By using BAPI BAPI  BAPI_SALESORDER_CREATEFROMDAT1.
    Ask your technical team to desing.
    Regards
    Ravi Shankar.

  • STO- Delivery Creation

    Hi
    Intercompany STO Process
    Could any suggest the necessaryconfiguration steps for the Automatic Delivery order creation against the STO P.O.
    Appreciated if could send me also  Text Removed
    Regards
    RG
    Edited by: Lakshmipathi on Jan 4, 2011 7:23 PM
    Being an old member, dont you aware of forum rules not to ask to share any information to personal mail id ??  Please dont deviate the forum rules

    Hi R G,
    Adding to Balaji's solution just check if the following configuration helps you to map the requirement:
    a) SPRO > Purchasing > Purchase Order > Set up Stock Transport Order > Activate Automatic Delivery Creation and CRM Billing - This config is useful - If you want to create a replenishment delivery immediately after creation of the stock transport order, set the Auto Delv. indicator.
    Here If you use this function the system does not perform an availability (ATP) check when it creates the delivery. It assumes that the availability has already been checked during stock transport order processing.
    b) SPRO > Purchasing > Purchase Order > Set up Stock Transport Order > Assign Document Type, One-Step Procedure, Underdelivery Tolerance.
    If you set the indicator for the one-step procedure i.e "Stock Transfer According to One-Step Procedure", the goods receipt is posted in the receiving plant at the same time as the goods issue is posted in the issuing plant.
    Hope the above helps.
    Regards,
    Ajinkya

  • Unable to Invoice Intercompany STO delivery

    Hi,
    We have an Intercompany STO wherein we are unable to call out the Delivery to Invoice.
    What should be checked to sort this out.
    Please advice.
    Regards,
    Sophia Xavier.

    CHECK THE SETTINGS SOPHIA
    The following steps have to be followed in order to configure stock transport order between two plants.
    1. Create a vendor for the Company code of the receiving plant using account group 0007 via T-Code XK01.
    2. In the purchasing data view assign the supplying plant and the schema group
    3. Create customer with the sales area of the vendor.
    4. The shipping conditions, the delivering plant and the transportation zone determine the route in the STO.
    5. In the pricing procedure determination relevant to the STO assign document pricing procedure and customer pricing procedure to get the pricing in the invoice.
    6. Maintain condition records for pricing condition.
    7. Maintain carrier as a partner in the customer master.
    8. In OMGN select the supplying plant and assign the company code and sales area. Similarly select the receiving plant and assign the company code and sales area (The company code to which the plant is assigned to).
    9. Assign the delivery type and checking rule to the document type.
    10. And finally, assign the purchasing document type to the supplying plant and the receiving plant.
    11. Create the STO using T-Code ME 21N and save.
    12. Check for release strategy if any and release using T-Code ME 28.
    13. Create delivery in background using VL10G.
    14. If delivery is created, it is an indication of correct configuration and master data creation.
    Stock transfer between two plants in different company codes is known as inter company stock transfer.
    Material should be maintained in both supplying and receiving plant MM01
    Stock should maintain only in supplying plant MB1C
    Create receiving plant as a customer in supplying plants company code and sales area XD01
    Assign this customer number in receiving plant details OMGN
    Assign supplying sales area in supplying plant details OMGN
    Assign delivery type NB for in combination of supplying/ receiving plants.
    Create STO ME21N
    As it is normal there in the item details we should get shipping date i.e. customer number
    Go for Delivery VL10B
    Shipping point *****
    Select PO go for execute
    then select the delivery then go for delvy ............create delvy,,,, delvy number generated.
    Goods Issue VL02
    Delvy doc **********
    Click on picking
    enter the picking qty
    Click on PGI
    HERE GENERATE INVOICE USING VF01
    in the mean time check in the PO history you will get the details
    Goods receipt MIGO
    Stock overview the stock will be updated
    reward points if useful

  • Critical intercompany STO issue

    Hello Together,
    We are facing a strange issue in Intercompany STO process. Supplying plant has done the goods issue ( movt type 643 ) against STO order and sent us the delivery document.
    Accordingly we have changed the Import STO Po & manintained the BCD, CVD & other duty in PO. With refect to PO we did the custom MIRO for Intercompany STO PO.
    But when i try to do goods receipt against outbond delivery then system ask me to put the MIRO no . When i put the MIRO no then the excise values should be come by defalut but
    in my case the excise values are not comming by default.
    The defalut excise values are coming by defalut in case of normal import PO ( not STO ) when i try to do the goods receipt against PO & not against outbond delivery.
    Why it is so ? Could u please help us.
    We are working in SAP 4.7 version and just 2 weeks back we have updated Patch level 35 ( support package SAPKH47035).
    Thanks in advance

    Hi,
    Did you change the PO after doing the PGI and delivery ? If it so try keeping the CVD values before doing the Delivery.
    Regards,

  • FIFO break during delivery creation against STO

    Hi,
    I am running a batch job which is responsible for delivery creation against STO.
    There are 3 STOs I have in system - STO1 from receiving plant - RP1 & STO2 & STO3 from receiving plant RP2.
    In all 3 STO, I have same issuing plant(IP1).
    I expect, when the delivery creation batch job gets triggered, it should create delivery against STO1, later to STO2 & STO3.
    Important parameters as per configuration is set to as below -
    Logistics execution -> Shipping -> Worklists -
    The batch job has shipping due list with
    option "1 Ship-to party and source document" and package type as 1 "All items for  document type and ship to party"
    Any body has any clue, how we can address this?
    Regards,
    Dipak

    Hi,
    Thank you for your reply.
    Below is my MD04 screen -
    The situation is, once GR is done in above plant, stock gets reflected in this issueing plant.
    Next activity is delivery creation batch job triggers.
    System should create delivery for the STO PO for receiving plant SP1.
    Rather than that system creates outbound delivery for receiving plant SP2 & SP3.
    Which I feel is FIFO break.
    My shipping due list has below parameter -
    Delivery creation profile -
    So any idea what causes this FIFO break.
    Also not sure what is this "planned delivery creation dates" you referred earlier.
    Regards,
    Dipak

  • STO Auto delivery Creation - Batch Job

    Hi Friends,
    I am facing issue related to auto delivery creation through batch Job for STO.
    I created a variant for auto Creation of delivery for batch Job using T code VL10BATCH, using the parrameter Shipping Point and Deliv. Creation date. The Batch Job is running fine, but my Client wants the delivery shoud be created from Delivery Date instead  of Deliv. Creation date.
        I tried to change the varriant , but could not find the delivery date as a parmeter to be selected.
    Is there any possible way to use delivery date for creation of Auto delivery instead of Deliv. Creation date.
    If not please tell why only deliv. creation date is given in varriant creation ,
    Regards,
    Kunal

    Hi,
    GO to VL04 there u just fill required fields and then go to menu bar program - execute in back ground then it will show u output parameters popup screen then enter. There u just give start data and time and then clikc on periodic values button there u select daily. Finally save. This will be run in back ground every day on specified time..
    Regards
    Sankar

  • Movement type for goods issue in intercompany STO business scenario

    Hi, everyone,
    In intercompany STO scenario, firstly we should create a purchase order with a transfer order type just like as UB,
    then we use T-code: VL10B to create the delivery note by referencing the purchase order created in first step, in succession, billing, goods reciept.
    Actually I have a question about the movement type in goods issue process. The standard is 643 deliveried by SAP.
    Can I customize the movement type in intercompany STO business scenario

    hi,
    The following are the scenarios of cross plant goods movements:
    Alternate plant procurement of purchased items
    Alternate plant production
    Plant-to-plant goods transfer of grouped project stock
    Stock transfer without reference to a stock transfer order (STO)
    1 Step – 301
    1 Step reversal – 302
    Stock transfer with reference to an STO in the receiving plant without SD
    2 Steps - 351 and 101
    2 Steps reversal – 102 and 352
    Stock transfer with reference to an STO in the receiving plant with SD delivery
    2 Steps – 641 and 101
    2 Steps reversal – 102 and 642
    1 Step – 647
    1 Step reversal – 648
    Movement Type &  Description
    301 / 302
    Goods receipt into production order in another plant. This is a one-step, cross-plant stock transfer. This movement type does not use STOs but behaves like a goods receipt of stock, except that the stock comes from another plant into the current plant. Movement 302 is the reverse of 301.
    351 / 352
    Stock transfer that is in transit between two plants. This is a two–step, cross-plant stock transfer, because after movement 351, you do not immediately see the stock in the receiving plant. After movement 351, the stock is in transit between the two plants. Only after you have performed a goods receipt (movement 101/102)of this ”in-transit” stock into the receiving plant can you see this stock in the receiving plant. Movement 352 is the reverse of 351.
    641 / 642
    Stock transfer that is in transit between two plants, with delivery documents (Sales and Distribution). This is a two-step, cross-plant transfer of stock, because after movement 641, you do not immediately see the stock in the receiving plant. After movement 641, the stock is in transit between the two plants. Only after you have performed a goods receipt (movement 101/102 ) of this ”in-transit” stock into the receiving plant can you see this stock in the receiving plant. Movement 642 is the reverse of 641.
    647 / 648
    Stock transfer to another plant, with delivery documents (Sales and Distribution), with STO. This is a one-step, cross-plant stock transfer because after movement 647, you cannot immediately see the stock in the receiving plant. The stock is never in transit with this movement type, but the stock is transferred with reference to an STO with Sales and Distribution documents. Movement 648 is the reverse of 647.
    regards,
    Siddharth

  • Automating Goods issue during Delivery creation

    Hi all,
    We have a requirement to automate the Goods issue creation for certain type of orders when the Delivery is getting created. The orders that need to be automatically Goods issued during delivery creation are identified based on certain plants. These plants are linked to certain output type and in the output type routine is the standard program RVADEK01 with one additonal code for automating the Goods Issue creation.
    We have a custom table that holds the status of orders and there is a code in user exit userexit_save_document_prepare which changes the status of the order as closed when the goods issue is done.
    But when the delivery is saved, in this case when an automatic goods issue needs to happen, when the flow reaches this user exit, the output type code dosenot get executed and the Goods issue is not done and so the custom table will not be updated with the closed status. So we are in need to findout a place where we can update the status of the order in that table.
    The output type code is not executed even before the other user exit userexit_save_document. The output type code gets executed and goods issue is done after the this userexit_save_document when the COMMIT statement is executed in the subroutine BELEG_SICHEN_POST in the include FV50XF0B_BELEG_SICHERN.
    I need help in finding out if any user exit or badi is called after this commit statement, so that I can add my code to close the status of the order in my custom table. Just after this commit the Goods issue happens and the VBFA table gets updated with the 'R' records for goods issue.
    Please let me know if anyone has any idea on this. The ultimate goal is to find some place after the goods issue is done to update the status of the order as closed in the custom table we have.
    Thanks,
    Packia

    Dear Siva,
    As informed yesterday I changed the language from DE to EN, to match the other shipping points settings in table V_TVST, this did not bring the solution.
    Please let me summarize, I am really desparate here:
    This is only IM related, Not WM.
    Picking lists are not printed for any Shipping Point from this warehouse, this is just a small subsidiary of my customer in Finland.
    Issue is not Aut. PGI.
    VP01SHP has not been configured for any shipping points, still there we do get the PR except for the new shipping point.
    In the deliveries of correct processed shipping points  I do not find any picking output type.
    Item category in new shipping is equal to Item category in already existing shipping points, so no need to config here.
    There is no picking block active.
    PR creation happens once I enter the pick qty in the delivery in VL02N. This is the part that we need to have automated.
    Can you please try to help me out?
    Tnx & regards,
    Chris

Maybe you are looking for