Scheduling Agreement - Cannot Release, cant create message in LPA

Hello,
I have gone through all the threads on Scheduling Agreement but could not find the answer to the problem I am facing.
I created scheduling agreement through LP, everything went through smooth.
Now while create scheduling agreement through LPA, I am facing these problems, I cannot create output message while using ME38, but can create message through ME32L, but message output through me32L just creates printout of required quantity, no line items printed on it, and when I try to create output message through ME38 the message window comes in display mode, whereas while creating output message through LP, it allowed me to configure it. So first question, how can I enter my output setting in ME38 where SA is created through LPA.
Secondly document is created through LPA, but I cannot release it through ME84. I followed all the required settings, but its not letting me release the document, the traffic light is constant RED. Any ideas?
Lastly, No GR. Going through forum messages, I learnt that until the document is not released I cannot do GR. The dates of lines I changed it to post date, even behind the post date, but its still coming up as document doesnot have selectable items. Please help
Thanks/Afshad

Hello Prasand,
Your answer was helpful, but all these steps mentioned by you were already followed by me. My one question got answered there, why I get the messages in ME38 in uneditable format, but when I use ME84 for SA release, the result comes up in Red, and there I dont see any option to go further. Am I missing any step before it?
I clicked on List>Print Preview, the messages of JIT are there, then I click List> Print, dialog box comes up asking Output Device, I use default device LP01 there and then when I click OK message comes up Spool request (number 0000005941) created without immediate output and the problem remains no Sa released. Any help?
3. Ensure that the output message condition records for output types LPJ1 / LPH1 maintained.
Is this line refering to Customizing>MM>Purchasing>Messages>Output control>conditions tables?Define Condition tables, if yes I dont know how to configure this and havent read anywhere how to get this part configured.
I configured Output control>Messages Determination Schemas>Define messages schemas for SA>Define Message determination schemas, there in control data, i put LPJ1 and LPH1 requirements as 105 which is for delivery schedule, earlier it was pointing to 109 and 111, then Assign Schema: Sa release/expiditer I checked the R indicator. Am I correct?
I guess without the SA release, I cannot do the GR against my SA as when I do GR it gives message no selectable items.
Edited by: Afshad Irani on Dec 11, 2008 6:46 AM
Edited by: Afshad Irani on Dec 11, 2008 7:24 AM

Similar Messages

  • GR refer to schedule agreement without release

    Hi
    We want to do GR according to a schedule agreement without release. but sap cannot skip release process.  I find out the configuration is common for both PO and schedule agreement. everybody can give me some solution?
    I also see some difference between schedule agreement type(LP/LPA). but this not solved my issue.
    Regards
    Henry

    Hi Henry
      If u want to release the schedule agreement even though u use LP document type then
    Goto SPRO-MM-Purchasing-Schedule agreement-Define document types....Here in LP document type, click the check box of release docu.    Then system will prompt for release...
    Regards,
    Dharshan

  • Printout of schedule agreement before Release

    hi all,
    i have created release strategy for schedule agreement at three level EX, MM & GM, problem is that i want to print schedule agreement number thru ME9l after releasing it from EX level. can anyone please tell me that is it possible to print schedule agreement before releasing from all three EX, MM & GM?
    if yes then how? or plzz tell me if any other option to print the same.
    regards saurabh.
    Edited by: saurabh srivastava on May 5, 2009 12:20 PM

    If your strategy is set up so that all three levels must release the agreement before it is final released I do not believe you can generate a printout.
    Regards

  • Scheduling agreement- With Release

    Dear All,
    Can anybody give the steps for Scheduling agreement with Release documentation from SPRO settings and ME84.
    Also Delivery schedule print settings with re to scheduling agreement also needed.
    Regards

    Hi
    You can refer the below link
    http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm

  • Scheduling Agreement - Automatic Release Individual Schedule Lines

    Dear all.
    I've create a "LPA" scheduling Agreement and its release type is "JIT". So, I use to ME38 to maintain the individual JIT delivery schedule lines.
    The problem I have is this method requires the person to manually release each individual delivery schedule line document on the due date before GR is allowed. Hence, is there a SAP system function that can automatically release any due delivery schedule line document without having to manually track and release using ME38 each day/week/month?
    Thanks.
    Steven

    Hello
    use t.code ME84 then system release the sch.lines automatically those maintained with me38.
    Laxman

  • Exit in VA31 To Prevent Creating of Scheduling Agreement

    Hello,
    I have looked through the threads and did not fnd my answer, so I am opening this thread.  I have a requirement that under certain conditions a scheduling agreement cannot be created for a particular ship-to and/or bill-to.  Is there a particular ext that someone have used before to provide this type of functionality?
    Regards, Dean.

    hi
    you may use here form USEREXIT_CHECK_VBAK in program MV45AFZB
    to display MESSAGE E...
    regards, darek

  • ME38 resets Release strategy of Scheduling agreement

    Hello,
    It seems when the users change the delivery date  in the delivery schedule (transaction ME38), the system in some cases resets the release strategy of the scheduling agreement from "Release" to "Not Release".It happened only in some case,release indicator set to "4" in our case.
    I cannot understand why this happens.
    Has anyone encountered such a problem before.
    Thanks
    Sunil

    Below are the (changed) item fields :
    Purchasing Document Item Change Date   AEDAT
    Item Delivery Date   EINDT
    Schedule Line is "Fixed  "FIXKZ
    Below are the (changed) header fields :
    Release Indicator: Purchasing Document  FRGKE
    Release status  FRGZU
    Purchasing document processing state PROCSTAT
    Item and header changes have same "Change document number " and transaction code "ME38" , this happened only in some cases,Rel Strategy is on  document type level ,I am also confused on this .
      Please assist  on this

  • Release date and release no of Scheduling Agreement

    Hi All,
    I have a problem with Scheduling agreement.
    I have created a scheduling agreement with long validity period.
    I maintained delivery schedules within that validity period.
    I have generated forecast schedules. then using ME84, creating a releases.
    the problem is occurs here.
    it was not updating the release no and release date for the schedule line.
    still it is showing a *yellow light* .
    where is the problem and why it was not updating.
    and can u please explain the process and significance of those lights.
    Thanks in Advance.
    Regards
    Kishore

    Verify the table T161M has the values
    kvewe = 'B'
    kappl = 'EL'
    druvo = 1
    kschl = LHPA
    as mentioned in the code.
    The solution is add in SPAD the

  • Stock Transport Scheduling Agreement - error message: 'Stock in transit...

    Stock Transport Scheduling Agreement - error message: 'Stock in transit exceeded'
    Hi, I do have a question about transport scheduling agreements.
    I have created a stock transport scheduling agreement via ME37, doc. type LU for a stock material from issuing plant TT01 to receiving plant TH01. The material is maintained in both plants.
    After that,I maintain the delivery schedule via ME38 for a quantity for today. The quantity is available at issuing plant TT01, checked via MMBE.
    Then, I try to post the goods via MIGO. When I try to post the document, I get the following error message: "PL Stock in transit exceeded by 1,000 T% : 794 TH01 S1". Why do I get that? My target is to decreate the stock quantity in TT01 and to increase the stock quantity in TH01.
    Thanks, Peter

    Hi,
    This happens when you are issuing more on the schudle qty, Check you have anything on the transit receive it the try agin to process the issue.
    Hope it helps.
    Suresh

  • How are deliveries automatically created from scheduling agreement?

    How are deliveries automatically created from the schedule line of the scheduling agreement? Can anybody explain this step by step? Can we use the code VL10BATCH for this purpose? If we can, how is this code used?
    Thanks in advance.

    hi
    A customer scheduling agreement is an outline agreement with the customer containing delivery quantities and dates. These are then entered as schedule lines in a delivery schedule. You can either create schedule lines when you create the scheduling agreement or you can create them later.
    You fulfill a scheduling agreement by creating the deliveries in the schedule as they become due. You process deliveries for a scheduling agreement in exactly the same way as you process a normal delivery. After you have carried out the delivery, the system updates the Delivered quantity field in the scheduling agreement item with the delivery quantity.
    The scheduling agreement is used as a basis for delivering a material. The customer sends in scheduling agreement releases, referred to as delivery schedules, at regular intervals to release a quantity of the material.
    Document Types
    To configure document types for scheduling agreements, choose Sales -> Sales Documents -> Sales Document Header -> Define sales document types in Customizing for Sales and Distribution.
    The R/3 System contains the following document types for component suppliers:
    LZ - Scheduling agreement with delivery schedules (no external agents)
    LZM - Scheduling agreement with delivery orders
    LK - Scheduling agreement with delivery schedules (external agents)
    ED - Delivery by external agent (consignment issue)
    EDKO - External agent correction
    RZ - Scheduling agreement returns (no external agents)
    KAZU - Consignment pick-up for external agents
    KRZU - Consignment returns for external agents
    Item Categories
    To configure item categories for scheduling agreements, choose Sales -> Sales Documents -> Sales Document Item -> Define item categories in Customizing for Sales and Distribution.
    The system determines the following item categories for the related document types in
    documents containing materials with item category group NORM:
    Item category LZN for scheduling agreement type LZ
    Item category LZMA for scheduling agreement type LZM
    Item category LKN for scheduling agreement type LK
    Item category KEN for document type ED
    Item category EDK for positive corrections (or the manual alternative EDK1 for
    negative corrections) for document type EDKO
    Item category REN for document type RZ
    Item category KAN for document type KAZU
    Item category KRN for document type KRZU
    Schedule Line Categories
    To configure schedule line categories for scheduling agreements, choose Sales -> Sales Documents -> Schedule lines -> Define or Assign schedule line categories in Customizing for Sales and Distribution.
    The R/3 System contains the following schedule line categories for component suppliers:
    L1, BN, L2, and CN for item category LZN
    E4, E0, E5, and BN for item category LKN
    L2 for item category LZMA (standard for delivery order processing)
    Schedule Line Types
    To configure schedule line types for scheduling agreements, choose Sales -> Sales Documents -> Scheduling Agreements with Delivery Schedules -> Define schedule line types in Customizing for Sales and Distribution.
    Creating Scheduling Agreements
    To create a scheduling agreement with delivery schedules:
    1. In the Sales menu http://Ext. choose Scheduling agreement ->Create.
    2. Enter scheduling agreement type LK (standard) or LZ (external agents) and the
    relevantorganizational data.
    3. Choose ENTER.
    4. Enter the following data:
    Sold-to or ship-to party number
    Purchase order or closing number
    Material or customer material number
    You can use the Description field to identify the scheduling agreement. For
    example,
    you could enter the model year for a particular production series.
    The system allows up to 35 digits for a customer material number.
    Rounding quantity
    Usage
    Choose Goto -> Header -> Sales to enter the usage at header level, or Goto ->
    Item-> Sales A to enter it at item level. The system proposes usage S, for series, as default in both cases.
    Planning indicator
    Choose Goto -> Header ->Sales.
    Target quantity
    Mark an item and choose Goto -> Item -> Sales A
    Partners
    For scheduling agreements with external agents , choose Goto -> Header
    ->Partners to enter the external agent as forwarding agent and special stock partner
    on the partner function screen.
    5. Create a delivery schedule
    Mark an item in the scheduling agreement and choose Goto -> Item -> <Delivery
    schedule>. Enter:
    A delivery schedule number and date
    The cumulative quantity received by the customer
    The last delivery confirmed by the customer
    A schedule line with date, time, and quantity
    To enter additional data in the delivery schedule, choose DlvSch.Hdr (delivery schedule header).
    configuration:
    img->SD->Sales->sales document->scheduling agreements with delivery schedules->
    step1: define schedule line types
    schedule line types are not schedule line categories. Schedule line types are used for information purpose only.
    stds are 1. fixed date 2. backlog 3. immediate requirement
    4. estimate
    step2: maintain planning delivery sched. instruct/splitting rules
    The planning delivery schedule is an internal delivery schedule used to plan requirement s more efficiently.  It is sub divided into 3 parts
    2.1 delivery schedule splitting rules
    2.2 dly schedule instrusctions
    2.3 assign dly schedule splitting rules
    step3: define sales documents type
    step4 : define item categories
    step5: define schedule line categories
    step6: maintain copy control
    PROCESS
    step1:  create scheduling agreement
    VA31
    enter SP,SH valid from, valid to,
    goto ITEM OVERVIEW tab
    enter material, rouding qty
    select ITEM  click on FORECAST DLSCH
    enter different dly dates and qties
    save it.
    step2: create sales order with reference to above
    step3: create delivery
    step4: create billing
    regards
    krishna

  • Schedule agreement releases

    How I will come to know the Schedule Agreement is released or not in ME84? LPA is agreement type.
    ME84 I have executed and next screen green light is coming.
    But while going to ME33L and seeing Release number ,its 0.
    Please explain how I can do this?
    Thanks

    Hi PS,
    You need to output the last relase. Once you process it's output successfully, it would be considered. Otherwise not.
    Any release which is not transmitted, is not considered as valid for use in SA.
    Sanjeev
    Edited by: Sanjeev Shrivastava on Mar 24, 2008 6:50 AM

  • Scheduling agreement with relase - doc type LPA with JIT

    Hi
    can any one give the steps for Scheduling agreement with relase - doc type LPA with JIT process.. and explain how the JIT will work in SA.
    Pls advise what are config required and what the user tcode needed to perform the SA with JIT concept.

    Dear Friend,
    Without release documentation(Document type LP)
    The delivery schedule lines have official character-that is to say,they are transmitted to the vendor as they are saved in the system.The system does not document in detail releases aganist the scheduling agreement that have been sent to the vendor.Therefore,in the case of the document type without release documentation,the message control facility should be set up in such a way that a message is immediately sent to vendor if any changes are made to the delivey schedule stored in the system.
    With release documnetation(Document type LPA)
    If you use scheduling agreement with release documentation,the delivery schedule lines are not transmitted directly to the vendor.Intially ,the lines of the delivery schedule stored in the system for an LPA scheduling agreement for an internal information only.A message informing the vendor of your material requirements cannot be transmitted to the vendor until you explicitly create an SA release,that is forecast (FRC) or Just in Time(JIT) delivey schedule.Through this process,you can change the way schedule lines are represented.With release documentation,you can disply the SA releases(delivery schedules) transmitted to a vendor over a certain period of any time.This enables you to trace precisely when you sent which information to vendor.
    Regards
    Pramod

  • Document type LPA in schedule agreement

    any one can explain me document type LPA in schedule agreement. I read books as that is document type with release documentation. And what is the diff between LP and LPA?

    Dear,
    Please find below, which I found by search and posted by fellow collegues earlier....
    Default quantity for goods receipt
    In the standard system, the quantity open to date from the last- transmitted SA release is used in the case of scheduling agreements with release documentation (document type LPA). In the case of scheduling agreements without release documentation (document type LP), the open quantity to date is used.
    Document Type of Scheduling Agreement
    As a rule, the APO scheduling agreement in the SAP R/3 system is a scheduling agreement with the document type LP or a scheduling agreement without release documentation.
    If you use scheduling agreements of the document type LPA without confirmation control key then no default quantities can be determined from the release upon goods receipt.
    If you use scheduling agreements of the document type LPA with confirmation control key then the default quantities from the confirmation (shipping notification) are used.
    As a rule, the OLTP scheduling agreement in the SAP R/3 System is a scheduling agreement with the document type LPA.
    A scheduling agreement is a longer trem agreement with a vendor covering the supply of materials subject to predefined conditions.The conditions are valid for a pre defined period and a pre defined total purchase order quantity.
    You can enter the Target value in the header data of the scheduling agreement.You can enter the Target quantity in the item overview for each item
    You can use scheduling agreement with or without release documentation.The advantage of working with scheduliing agreement release documentation is that you always have a record of when you sent which delivery schedule information to your vendor,which you can display at any time.
    Without release documentation(Document type LP)
    The delivery schedule lines have official character-that is to say,they are transmitted to the vendor as they are saved in the system.The system does not document in detail releases aganist the scheduling agreement that have been sent to the vendor.Therefore,in the case of the document type without release documentation,the message control facility should be set up in such a way that a message is immediately sent to vendor if any changes are made to the delivey schedule stored in the system.
    With release documnetation(Document type LPA)
    If you use scheduling agreement with release documentation,the delivery schedule lines are not transmitted directly to the vendor.Intially ,the lines of the delivery schedule stored in the system for an LPA scheduling agreement for an internal information only.A message informing the vendor of your material requirements cannot be transmitted to the vendor until you explicitly create an SA release,that is forecast (FRC) or Just in Time(JIT) delivey schedule.Through this process,you can change the way schedule lines are represented.With release documentation,you can disply the SA releases(delivery schedules) transmitted to a vendor over a certain period of any time.This enables you to trace precisely when you sent which information to vendor.
    Regards,
    Syed Hussain.

  • LPA scheduling agreement

    Hi All,
    May I know what is LPA Scheduling Agreement and how do we set up messaging functionality for these Scheduling Agreements?
    Kindly revert ASAP.
    Thanks
    Surya

    You can use scheduling agreement with or without release documentation.The advantage of working with scheduliing agreement release documentation is that you always have a record of when you sent which delivery schedule information to your vendor,which you can display at any time.
    Without release documentation(Document type LP)
    The delivery schedule lines have official character-that is to say,they are transmitted to the vendor as they are saved in the system.The system does not document in detail releases aganist the scheduling agreement that have been sent to the vendor.Therefore,in the case of the document type without release documentation,the message control facility should be set up in such a way that a message is immediately sent to vendor if any changes are made to the delivey schedule stored in the system.
    With release documnetation(Document type LPA)
    If you use scheduling agreement with release documentation,the delivery schedule lines are not transmitted directly to the vendor.Intially ,the lines of the delivery schedule stored in the system for an LPA scheduling agreement for an internal information only.A message informing the vendor of your material requirements cannot be transmitted to the vendor until you explicitly create an SA release,that is forecast (FRC) or Just in Time(JIT) delivey schedule.Through this process,you can change the way schedule lines are represented.With release documentation,you can disply the SA releases(delivery schedules) transmitted to a vendor over a certain period of any time.This enables you to trace precisely when you sent which information to vendor.
    Chk the link below for profile creation and assigning the same to SA, for LPA process
    http://help.sap.com/saphelp_47x200/helpdata/en/75/ee0ef255c811d189900000e8322d00/frameset.htm
    Hope this will help you
    BR,
    Krishna

  • 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

Maybe you are looking for

  • Can anyone tell me how to make a video clip in color transition?

    Can anyone tell me how to make a video clip in color transition like the opening of "Oh Brother where art though" ? You know the scene at the start where it starts off Black and White then as we move down the timeline it transitions to a rusty brown

  • Final cut stuck when opens on "Restoring the window layout"

    The software crashed and after I started it again there was a mess of files which are not found although I downlaoded them from the camera. Now the software doesn't show anything. Only gray screen and it is stuck on "restoring window layout"

  • Cursors - More number of repeated full table scans

    Hai, If i execute the below mentioned query in sql*plus select distinct cod_acct_no, a.cod_cc_brn, a.cod_prod from account_master a, product_master b where a.prod_no = b.prod_no and b.cod_sc_pkg = var_pi_cod_sc_pkg and cod_acct_stat not in ( 1,5) UNI

  • How to manage/copy/track  db in Oracle

    Hi, I'm working on dev ORacle db so we have couple of changes every day and then we go to change control location to log most recent source for each object: sp, package, ddl, etc.. Is there any good auto tool to make snapshot for the whole db and hav

  • Java 6 plug-in

    I have been updating Java 6 with update 1,2,3,5,7,11 and J2SE runtime environment 5.0 update 6,9,10. They are all listed in the add/remove program section of xp. Are they all being used when I use java or simply occupying space on the HD? Could I uni