Scheduling agreement cancel correction delivery

Hello,
I created a correction delivery by mistake in a Scheduling agreement. I tried to search a procedure for my case, but I did not find what I am looking for.
Can anyone suggest me what should I do to correct the wrong correction delivery?

Hi Joseph,
Create another correction delivery with the same Qty but now with the opposite sign. Say you have created correction delivery for 25 PCs then you now have to create the correction delivery with -25 PCs. Please ensure that you enter the same date as you entered earlier, else it may affect your Cumulative Qty..
Thanks,
Pushparaj

Similar Messages

  • Return process in Scheduling agreement and correction delivery creation

    Hi Experts,
    I have couple of Questions:
    1) I want to know the return process in case of scheduling agreement, how exactly we should go about it.
    2) Regarding creation correction deliveries in the scheduling agreements.
    I enter in a valid scheduling agreement number into transaction VA32, click the "JIT DlSch" button, click "Corr. Delivery" button and then enter in a date and quantity.
    After I hit "Save" button, I am taken back to the initial VA32 screen and see the following message...
    Sched. Agr. w/ Rel. ####### has been saved (no delivery created)
    Message no. V1261
    Does anybody have any insight to why this is happening? Thanks in advance.
    Sourabh

    Whether it is a scheduling agreement or sale order, in case of returns, you need to generate the following:-
    a)  Return Sale order or scheduling agreement referencing the parent billing document
    b)  Return delivery if goods are taken back in parent plant via VL01N
    c)  Credit note to customer via VF01
    d)  Excise credit via J1IH
    Last but not least, please spell the name correctly.
    thanks
    G. Lakshmipathi

  • About selecting Scheduling Agreement and Forecast delivery schedule

    Hi Experts,
    i want to write a Report, with 2 parameters for the selection : Sold-to-party and Period
    For this Sold-to-party/Period, I want to list all scheduling agreement + Forecast delivery schedule.
    I already found the Function SD_VBEP_READ_WITH_VBELN to read all Forecast delivery schedule lines using Sales Doc.No. , but how can I select all Scheduling Agreement for the Period ?
    Regards,
    David

    Solution:
    by selecting data from table VEPVG (Delivery Due Index) and using function SD_VBEP_READ_WITH_VBELN for each SD Document.
    Regards,
    David

  • Create correction delivery

    Hi,
    I need help at creating a correction delivery.
    To create a correction delivery manually go to transaction VA32, select a scheduling agreement and go to the forecast delivery schedule view. Here you can press the button "Corr. delivery". Enter a date and an amount and submit. After saving the scheduling agreement the correction delivery can be found in the document flow.
    This process (create a correction delivery) I want to do automatically. Do you know a BAPI or something else for this process?
    I try different function modules for creating an outbound delivery without success. Also it is not possible to create a correction delivery (type LFKO) manually in transaction VL01N.
    Thanks
    Andrea

    Hi,
    thanks for your reply.
    The WS_DELIVERY_* function modules have no input parameter to change the cumulative delivered quantity or to create a correction delivery with reference to the scheduling agreement.
    The function modul BAPI_OUTB_DELIVERY_CREATENOREF I canu2019t use because I need the reference to the scheduling agreement.
    When I try function module BAPI_OUTB_DELIVERY_CREATE_SLS I get the error
    E V50R                 051 Fehlende Daten in der BAPI-Schnittstelle: VBAK VBTYP E (Missing date in BAPI interface)
    because the type of the scheduling agreement (E) is checked. This function is not allowed for type E and F.
    (Standard Code u2013 Program SAPLV50R_CREA Form DCS_CHECK_SO_VS_INTERFACE Line 72+)
    * any order types which are not allowed? -------------------------
      loop at ix_sd_orders-vbak assigning <ls_vbak>
                                where vbtyp ca 'EF'.
        clear ls_mess.
        ls_mess-msgid = 'V50R'.
        ls_mess-msgno = '051'.
        ls_mess-msgty = 'E'.
        ls_mess-msgv1 = 'VBAK'.
        ls_mess-msgv2 = 'VBTYP'.
        ls_mess-msgv3 = <ls_vbak>-vbtyp.
        append ls_mess to ct_mess.
        if 1 = 2. message e051(v50r) with space space space space. endif.
        cf_subrc = 1.
        exit.
      endloop.
    Any other ideas?
    Thanks!

  • Unable to create Correction Delivery for Sales Agreement

    We are having the issue of not being able to create correction deliveries for ceartain Scheduling Agreements.  I enter in a valid scheduling agreement number into transaction VA32, click the "JIT DlSch" button, click "Corr. Delivery" button and then enter in a date and quantity.
    After I hit "Save" button, I am taken back to the initial VA32 screen and see the following message...
    Sched. Agr. w/ Rel. ####### has been saved (no delivery created)
    Message no. V1261
    Does anybody have any insight to why this is happening?  Thanks in advance.
    Mike

    Hi,
    What is the Correction Delivery Type that you used? Please check in the definition of Sales Document VOV8 (Scheduling Agreement) in 'Corr. delivery type' field under 'Scheduling Agreement' section.
    And also, please refere to the links below. These may provide you with some additional information:
    http://help.sap.com/saphelp_45b/helpdata/en/4b/3f4486a38a11d194e900a0c9306794/content.htm
    http://help.sap.com/saphelp_46b/helpdata/en/35/b0e85787a62488e10000009b38f9b7/content.htm
    Regards,
    Raja

  • Error In scheduling agreement proccessing

    Hi Friends
    1. If I enter new schedule line  in JIT  Delivery tab of   scheduling agreement and try to save  it  , it is throwing error that u201CDelivery go ahead was reducedu201D. Message no. V4042.
    I went ahead and saved the  scheduling agreement  .
    2. When I try to create delivery with reference to this scheduling agreement it is throwing error that u201Corder canu2019t be deliveredu201D  Message no. VL461  and no schedule lines are due upto selection date .
    Could you help me to correct it .
    Jaya

    Hi Jaya,
    what i meant is that, if you have changed the existing JIt delivery schedules i.e changing the existing schedule line qty.
    If the Jit delivery schedules are not saved with open quantity in the Scheduling Agreement, cannot creat delivery for that schedules.
    Regards
    vk

  • SCHEDULING AGREEMENT AND SCHEDULING LINE CREATION

    Hello Guys,
    I trying creating a scheduling agreement(SA) for vendor & material combination.
    I have created a Scheduling agreement in ME31L then maintained in ME38.
    In ME38 i have also mentioned the delivery date. when i am checking EKKO for Purchasing document , its created with the delivery date specified.
    My question is how to create a schedule line ? Do we need to maintain a source list of that material, plant and vendor.
    If we have the source list maintained, then what is the next step after SA is created and maintained.
    Do we need to do MIGO? because i tested by creating one SA in ME31L and maintained in ME38. I mentioned the delivery date as today and when i checked EKKO table the Purchasing document is created.
    Do i need to create a Purchase Order?
    If no then do i need to do MIGO? If i need to do MIGO, for what reference do i need to do MIGO???
    My client never maintained a Scheduling agreement, they want the scheduled lines to be created and sent to vendor and we need to receive  the goods on specified delivery date.
    Help will be appreciated.
    Thanks.

    Hi,
    You need to make a distinction between the scheduling agreement (ME31L/ME32L) and the delivery schedule creation (ME38/ME84)
    With ME31L you create the scheduling agreement. In the scheduling agreement which is created for a vendor you maintain the parts that you will order at this vendor, the target quantity that you will order over a certain period and the price.
    In ME38 you use the scheduling agreement number that is created with ME31L to create schedule lines (manually). These schedule lines consist of a date and an quantity. This is the data that needs to be transmitted to the vendor and against which the vendor is shipping the ordered materials.
    Once the vendor ships the materials you post the goods receipt in Migo against the scheduling agreement number.
    That is the basic working of the scheduling agreement and the delivery schedule.
    Now some remarks.
    You need to set-up the required output conditions for transmitting the data to the vendor either via print, fax, email or EDI.
    You can do this manually in each scheduling agreement and each release but typically you maintain the output condition records.
    For scheduling agreement contract (ME31L) you use transaction MN07.
    For the delivery schedule (ME38/ME84) you use transaction MN10.
    In order for you to be able to post the goods receipt the delivery schedule needs to have been transmitted otherwise you will get a message that not requirement are found when trying to post goods receipt.
    Also the goods receipt can only be posted if the requirements are valid on the day that you are performing MIGO. This means if you would post GR today then the open requirements in the scheduling agreement need to be for today or already from previous dates. The system will not allow you to post GR for quantities that are only due tomorrow (if this is required a user exit needs to be set-up).
    If you want schedule lines created via MRP then you need to set-up a source list using ME01. You have to make sure that the MRP key is set to 2 in orer for the system to generate schedule lines and you also have to make sure that you have the correct MRP parameters set-up.
    You can use ME84 to transmit the delivery schedule lines generated by MRP if no changes are required. With the ME84 you can transmit multiple releases at once, however this transaction can not be used to make manual changes to the MRP proposal.
    The scheduling agreement offers lot's more possibilities but the above should get you going with the basics.
    Hope this will help you on your way.

  • Error generating release against scheduling agreement  (cause 6) in ME38

    Hello Experts,
    Need your inputs on the the below error getting generated in ME38
    Error generating release against scheduling agreement  (cause 6)
    Message no. 06857
    Diagnosis
    The function module for generating a scheduling agreement release (forecast delivery schedule or JIT delivery schedule) has run up against an error, causing processing to be terminated.
    In this case the cause of the error is 6.
    System Response
    The error may involve one of the following situations:
    1: The nature of the error cannot be specified precisely.
    2: The forecast delivery schedule or the JIT delivery schedule was generated but no message record could be generated.
    3: A document type for which the functions "Generate forecast delivery schedule" or "Generate JIT delivery schedule" are not defined may be involved.
    4: A material for which the function "Generate JIT delivery schedule" is not defined may be involved.
    5: A scheduling agreement that has not yet been released by all persons responsible may be involved.
    6: The factory calendar has not been maintained correctly.
    Procedure
    Error source 1:
    Check whether the vendor and plant shown in the PO actually exist in the system.
    Error source 2:
    Check the Customizing facility for message determination with respect to delivery schedules created under scheduling agreements (print operation '9').
    Error source 3:
    In Customizing, maintain the document types accordingly ( Define document types for scheduling agreement). Then create a new scheduling agreement with a document type for which release documentation is defined.
    Error source 4:
    Maintain the JIT delivery schedule indicator in the material master record.
    Error source 5:
    Have the scheduling agreement released by the person(s) responsible.
    Error source 6:
    If you are using a release creation profile without aggregation, you must maintain the factory calendar for the next 999 days
    Regards,
    Santosh

    Hello Mallinath,
    I referred the note and following are the observarion in the system.
    Step1:Run T-code SE16 (table T001W) to check the calendar ID of the plant.
    -----Referred the Calendor ID
    Step2: Check the JIT/Forecast delivery schedule of release creation profile in customizing. (T-code OLME -> Scheduling Agreement -> Maint. Rel. Creation Profile for Sched. Agmt. w. Rel. Docu.)
    Run T-code SCAL to adjust the period of the calendar ID which checked in STEP 1 according to the JIT/Forecast delivery schedule of the release creation profile which checked in STEP 2.
    (For example, if the JIT/Forecast delivery schedule of the release creation profile is "999" days, then the calendar should be extended for the next 999 days at least)
    ---------In this case factory calendor is valid till 2015 and according to note needs to change the factory calendor till 2018( or for 999 days) ?
    Waiting for your inputs.
    Thanking you,
    Santosh

  • Scheduling Agreement for Imported Material

    Hello Friends
    I am doing import cycle through scheduling agreement.I maintained all the conditions(custom duty and CVD with custom clearing vendor) in scheduling agreement.Now i am doing first LIV to capture planned delivery cost of bill of entry in t code MIRO for that i am selecting layout as planned delivery cost.but the system gives the error msg as no delivery cost exist for PO 5500000000 (SA number)
    Please help me out why system is not recoginizing custom clearing vendor and how to sort this out
    Regards
    VS

    Hello Priyanka,
    Following message am getting while doing first LIV for planned delivery cost in case of import process against scheduling agreement.
    No delivery costs exist for purchase order 5500000000 00000
    Message no. M8014
    Diagnosis
    You have chosen Delivery costs -> Planned -> By purchase order. This function allows you to process delivery costs which were planned in the puchase order. The purchase order which you are currently processing does not contain any planned delivery costs.
    Procedure
    Check the purchase order number. If it is correct, you can only post the delivery costs as unplanned delivery costs
    Regards
    Vivek

  • SUS Scheduling agreement - MM SUS Scenario

    Hi,
    In MM SUS scenario, we create Scheduling agreement and the delivery schedule will be released and schedule will be sent to SUS which is a standard functionality.
    But our requirement is to send the Scheduling agreement as whole..like we sned PO from MM to SUS. Does it work if I create a custom idoc message type similar to PO (orders) with proper segments relevant to Scheduling agreement and corresponding mapping with XML in SUS ?
    Has anybody worked on this kind of development? if yes please share some inputs.
    Appreciate any help
    Regards
    Kiran

    Hi Abhishek,
    we don't want to change the idoc type: we would like to know if is correct to configure idoc DESADV for ASN created on SUS from a scheduling agreement release...because the idoc DESADV is not registered on ECC6 because of the error mentioned in my first post.
    Anyway, the note you suggested is referred to software components that differ from ours.
    Thanks for suggestion.
    Francesca

  • Schedule agreement LPA

    Dear All,
    I have maintained the Scheduling agreement with LPA doc type with creation profile 0001 after JIT indicator maintained in material master.
    I maintained delivery schedule in ME38 and saved.
    But when i try to Generate JIT or Forecast schedules error appears as below.
    Error generating release against scheduling agreement  (cause 2)
    Message no. 06857
    Diagnosis
    The function module for generating a scheduling agreement release (forecast delivery schedule or JIT delivery schedule) has run up against an error, causing processing to be terminated.
    In this case the cause of the error is 2.
    System Response
    The error may involve one of the following situations:
    1: The nature of the error cannot be specified precisely.
    2: The forecast delivery schedule or the JIT delivery schedule was generated but no message record could be generated.
    3: A document type for which the functions "Generate forecast delivery schedule" or "Generate JIT delivery schedule" are not defined may be involved.
    4: A material for which the function "Generate JIT delivery schedule" is not defined may be involved.
    5: A scheduling agreement that has not yet been released by all persons responsible may be involved.
    6: The factory calendar has not been maintained correctly.
    Procedure
    Error source 1:
    Check whether the vendor and plant shown in the PO actually exist in the system.
    Error source 2:
    Check the Customizing facility for message determination with respect to delivery schedules created under scheduling agreements (print operation '9').
    Error source 3:
    In Customizing, maintain the document types accordingly ( Define document types for scheduling agreement). Then create a new scheduling agreement with a document type for which release documentation is defined.
    Error source 4:
    Maintain the JIT delivery schedule indicator in the material master record.
    Error source 5:
    Have the scheduling agreement released by the person(s) responsible.
    Error source 6:
    If you are using a release creation profile without aggregation, you must maintain the factory calendar for the next 999 days.
    Please advice how to proceed further?
    I tried to run ME84 but no output found.
    Regards

    Kindly check the thread
    SA delivery schedule release problem

  • Scheduling Agreement question

    I'm trying to figure out how scheduling agreements are used and have referred the SAP help at: http://help.sap.com/saphelp_scm50/helpdata/en/35/3c6c39c71c0324e10000000a114084/frameset.htm. Please let me know if my understanding is correct. Scheduling Agreement is basically a source of supply which creates a Tlane is APO. So, the Tlane is between the supplier and the plant, right? When there is a demand on the plant and heuristics runs, what is created at the supplier location based on the scheduling agreement?

    Hi,
    Delivery schedule lines are created which specify how much quantity of a material and by what date it should be delivered.
    These delivery schedule line are with reference to the scheduling agreement which is  a like contract between a company and a supplier to supply a list of materials within the specified time frame, at agreed time frame and with the agreed advance notice.
    Regards
    Datta

  • Why does Scheduling Agreements create multiple deliveries?

    Hello SAP Experts,
    We are on 4.7c.  Our scheduling agreements automatically create deliveries; and I was wondering why instead of putting the scheduled lines onto one delivery, it automatically creates multiple deliveries for the scheduling agreements. 
    Could someone please explain this to me?  Thank you for your time.
    Best Regards,
    WC

    Hello,
    Thank you for response.  I checked the settings and they are correct. 
    In addition, I checked to make sure the Scheduling Agreement Header Details had the "Order Combination" box checked, which will allow multiple scheduling agreements to be combined in one delivery. 
    Our scheduling agreement runs on the weekends where it automatically creates the deliveries for them.
    My question is why do the scheduling agreements with the "Order Combination" box checked do not always put the scheduling agreements into one delivery. but separates them, when they are in the same automated run. 
    For example:
    Scheduling Agreement 0001 through 0045 will be created on Delivery 100001, but Scheduling Agreements 0046 though 0048 will be created on Delivery 100002...and they both have the order combination selected. 
    Why is Scheduling Agreements 0046 through 0048, not automatically creating on Delivery 100001 as the other scheduling agreements?
    Thank you for your time!
    Best regards,
    WC

  • Why do Scheduling Agreements create multiple deliveries?

    Hello SAP Experts,
    We are on 4.7c. Our scheduling agreements automatically create deliveries; and I was wondering why instead of putting the scheduled lines onto one delivery, it automatically creates multiple deliveries for the scheduling agreements.
    Could someone please explain this to me? Thank you for your time.
    Best Regards,
    WC

    Hello,
    Thank you for response.  I checked the settings and they are correct. 
    In addition, I checked to make sure the Scheduling Agreement Header Details had the "Order Combination" box checked, which will allow multiple scheduling agreements to be combined in one delivery. 
    Our scheduling agreement runs on the weekends where it automatically creates the deliveries for them.
    My question is why do the scheduling agreements with the "Order Combination" box checked do not always put the scheduling agreements into one delivery. but separates them, when they are in the same automated run. 
    For example:
    Scheduling Agreement 0001 through 0045 will be created on Delivery 100001, but Scheduling Agreements 0046 though 0048 will be created on Delivery 100002...and they both have the order combination selected. 
    Why is Scheduling Agreements 0046 through 0048, not automatically creating on Delivery 100001 as the other scheduling agreements?
    Thank you for your time!
    Best regards,
    WC

  • MRP Strategies that work well with schedule agreements

    Hello Experts, We are having a disucsion on using schedule agreements with our consignment process. What MRP Types and lot size keys work with scheduling agreements? One of our managers insists on using reorder point, and everything I have read seems to lead towards deterministic prodeure PD, and an exact lot size. I was hoping you could provide a proven strategy or tips.
    Thank you in advance,
    Brian

    Hello, Thank you both for your quick replies. Our company strategy is a reorder point strategy, that we force our vendors to read off of a web page, but the settings in the system are PD, and usually a 4 week lot size. The MRP data is dumped to the same web page as the reorder point information. It is expected that our vendor is managing the inventory. We also use a PO for the year parked at the end of the year for the entire supply. This method does not allows us to measure the vendor performance.
    We are currently have new proposal to use contracts and Kanbans with MRP. Where MRP is used for forecast information and Kanban controls the replenishment by sending a replenishment order to the vendor. This will give us a consumption based process, that can be measured.
    The other proposal is to use a schedule agreement with the same reorder point strategy. This is why I asked my question. I don't think that the reorder point strategy works with this type of order. From my understanding the scheduling agreement controls the delivery of the incoming material based on forecast and real demand. Is my understanding correct?
    The ulitimate goal is to have a system that provides our material on-time when it is needed. Easy for our vendors, and so we can measure the vendor against. On time delivey and stock outs.

Maybe you are looking for