ME84 / Messages for scheduling agreement Release

Hallo,
I wold like to create SA releases(agreement type = LPA) via ME84 separately for JIT-schedules and FRC-schedules.
I use LPH1 as message type for the FRC-schedule and LPJ1 as message type for the JIT-schedule.
The creation of JIT-schedules works fine if I select 'JITSchds Only' in ME84. The result is ONE LPJ1-message with the content of the JIT-schedule.
But I have a problem with the FRC-release, because when I select 'FRC-release Only' in ME84 I get
one LPH1-message and one LPJ1-message as well (both messages have the content of the FRC-release).
But I expect only ONE LPH1-message.
Please advise what I have to do to get only ONE LPH1-message in case of creation of FRC-release.
Thanks a lot
Olga

Hi,
Do check if any changes are carried for your schedule lines as both JIT and FRC  was generated.
Do check also the below thread which was discussed for similar query which might help you.
http://scn.sap.com/thread/3352142

Similar Messages

  • EDI Message for Scheduling Agreement Schedule Lines

    Hi Experts,
    My client has the EDI set up for the SASL and is running fine.
    Currently we have scheduled background program to trigger the IDOC and convert the IDOC into XML to send the information to the external system via interface after MRP run.Output type in the SASL will be triggered at header level (Without release documentation) whenever there is a new or change in the schedule line. Schedule line will be fixed automatically for every MRP run based on the Firm zone maintained in scheduling agreement.
    Now the requirement is, Client wants to send the schedule lines regardless of New or change after MRP run sothat all the information will be sent to the suppliers. This requirement may be contradictory one but the client needs it.
    1) For the New schedule line creation the output type will be triggered so no issues the program will take care
    2) For the change schedule line also the output type will be triggered so No problem.
    Requirement :
    1) When there is no new & change in the schedule lines , how we can handle this???
    2) Client wants to fix the schedule lines based on the planned delivery time and they do not want to maintain this PDT in the Firm zone field.??
    Kindle explore and provide me the inputs. Appreciate your help.
    Thanks /Karthik

    Can you elaborate bit more on the issue.
    see if you are not mentioning the PDT in the firm zone field. then it means the schedule lines can be changed and once they are changed the change idoc will get trigger.
    however if there is no change in the schedule line and since its a old one there will not be any idoc generation for this.
    seems as per your requirement you want to get the idoc generated for the old line as welll then u need to look for the anhancement badi/uer exit to map this.
    need more insight of the issue to resolve it

  • Schedulling agreement release output issue/.........

    Hi All,
    This issue is related to scheduling agreement release. I've mentained condition record for doc type/ purch. org/ vendor through transaction MN10 for this.
    Now i am maitaining Delivery schedule for this, but system is not fetching the output type automatically here. Nor its is allowing me to put it manualluy as the whole field is greyed out.
    Can anybody help in resolving this issue?
    Thanks in advance.

    >
    aakansha kumar wrote:
    > Hi All,
    >
    > This issue is related to scheduling agreement release. I've mentained condition record for doc type/ purch. org/ vendor through transaction MN10 for this.
    >
    > Now i am maitaining Delivery schedule for this, but system is not fetching the output type automatically here. Nor its is allowing me to put it manualluy as the whole field is greyed out.
    >
    > Can anybody help in resolving this issue?
    >
    > Thanks in advance.
    Check if your output type is present in the output type determination in the following path:
    Materials Management -> Purchasing -> Messages -> Output Control -> Message Determination Schemas ->  Define Message Schema for Scheduling Agreement Release/Expediter
    Also check the analysis tab while you check the SA release, it will give you clearer idea about the problem.
    Regards,
    Aroop

  • Idoc Message type for Scheduling agreement

    Dear Experts,
    How to configure to create Idoc for Scheduling agreement (not the releaseed schedule lines) ?
    I am trying to use message type ORDERS05 but it is not working.
    Will any body guide me preferably step by step process for this ?
    Thanks in Advance,
    Best Regards,
    Raju

    Hi Anji,
    Thanks for the Reply. But i think ORDRSP is for Order Confirmations.
    But I have to send Outbound Idoc for a Schedule Agreement.
    Whether the same  Idoc type & Messge type used for SO/PO(e.g ORDERS05, ORDERS/ORDCHG) can be used for Scheduling Agreement.
    Please Advice.
    Regards,
    Anbalagan

  • Message type for Scheduling Agreement - Outbound IDoc

    Hi All,
    I have to create an Idoc for Scheduling Agreement through a Z program based on some conditions. I have bit confusion, whether i can use Idoc type for Orders(e.g ORDERS01..05) & Message type ORDERS / ORDCHG to generate Outbound Idoc.
    Already there is process code for for ORDCHG mappig IDOC_OUTPUT_ORDCHG & ORDERS mappig IDOC_OUTPUT_ORDERS.  Whether there will be any impact on this.
    Appreciate your help.
    Regards,
    Anbalagan.

    Hi Anji,
    Thanks for the Reply. But i think ORDRSP is for Order Confirmations.
    But I have to send Outbound Idoc for a Schedule Agreement.
    Whether the same  Idoc type & Messge type used for SO/PO(e.g ORDERS05, ORDERS/ORDCHG) can be used for Scheduling Agreement.
    Please Advice.
    Regards,
    Anbalagan

  • Release strategy for Scheduling Agreement(SA)

    Dear Forum,
    This issue is with regards to the release strategy for Scheduling Agreement(SA)
    Until now release has only been applicable to contracts at our client site. But we now plan to introduce it for SA as well. Such a feature is available in SAP but the problem is that with the given release strategy GR is not allowed until the release is affected. The system allows you to post the delivery schedule.
    Now what I want is that after making the SA the system should not allow to make delivery schedule if release is not affected.
    We also have MRP run at client site..Kindly suggest the procedure as, how to configure it.Are der any User Exit for the same,if so please discuss..
    Warm Regards
    Nainesh
    SAP ECC 6.0

    Hi,
    What's the SA Type that was created via MRP.
    If it's LP (without release document), release will not do anything BUT
    If it's LPA (release document), then you will not be able to Post the GR until release is affected.
    Thanks.
    Scheduling Agreement can be categories as
    1) LP (without release document) and
    2) LPA (with release document)
    If use LP, you can do GR without release but with LPA, you need to release the schedule line via ME38.
    Thanks.
    NanoSAP  
    Posts: 58
    Registered: 1/5/09
    Forum Points: 6 
       Re: release strategy for Scheduling Agreement(SA)  
    Posted: Jun 26, 2009 8:32 AM    in response to: sathish.kumar           Reply 
    Dear Mr.Satish,
    Thanks a lot for your earliest reply...But my point is i want the system should not allow to make delivery schedule if release is not affected...Though schedule lines are generating through MRP run...Is is possible,by any chance...??

  • Problem Regarding TABLE updation for Scheduling Agreement

    Dear Experts,
    We have noticed that whenever we are releasing any Delivery Schedule for a line item against a Scheduling Agreement the table field ABART(Scheduling Agreement Release Type) in table EKET is not getting updated,but the same field or column in TABLE EKEH or EKEK is getting updated.
    Please advice what is the problem and how to resolve the same.
    Regards,
    Soumick

    Hi,
    The scheduling agreement schedule line is not firmed physically:The fixing indicator (EKET-FIXKZ) is empty for this schedule line.
    This can be checked in Transaction ME39 or with Transaction SE16 for table EKET for the corresponding schedule line.
    In the MRP group of the corresponding material, it is set that only transferred scheduling agreement schedule lines should be regarded as firmed (Transaction OPPR, firming scheduling agreement, Firm transmSLines [Field XFAT1]).
    In this case, only such scheduling agreement schedule lines are firmed which were transferred by message transmission through purchasing to the vendor. (see also the F1 help for the field).
    However, the system displays all scheduling agreement schedule lines as fixed in Transaction MD04 within the release period and assigns them with a star ('*'), that is, this applies also scheduling agreement schedule lines with a transmitted quantity of 0.
    In contrast to the above, these schedule lines are not displayed as fixed in Transaction MD05 or in the planning with 'Display result'.
    Note 354164 explains this system behavior.
    For the planning, the transmitted quantity is considered as fixed if this is correspondingly set in the MRP group of the material.
    If the transmitted quantity was updated correctly, it should be contained in field AMENG of table EKET.
    By using Transaction SE16 for this table and the corresponding schedule line (scheduling agreement number EBELN, item EBELP, schedule line ETENR), you should be able to find out....
    transmitted quantity was written to the database and a fixing can be carried out correspondingly in amount of the transmitted quantity or whether no update of the transmitted quantity occurred (see below Notes 82169, 117093, 134356).
    Solution
    First, the system behaves as intended.
    It should be checked whether the function, which is controlled by this indicator, is actually wanted this way (to firm only scheduling agreement schedule lines which actually have been transferred).
    In addition, problems can occur in purchasing when the printed quantity is updated (AMENG).This symptom can especially occur after you have upgraded from a release < Release 4.0A to a release > Release 4.0B.
    In this regard, see the related Notes 82169, 117093 and 134356.
    Regards,
    Udaya.

  • P.o for scheduling agreement

    Dear SAPians
    Is it necessasry to create a Purchase Oredr for scheduling agreement or can it be directly send to a vendor

    Have you set the condition record on MN11?
    Usually is set LPH1 for EDI and LPH2 for printer. Set 3 on dispatch time if you want to execute ME84 and ME9E after (by yourself or via job). If you want to send automatically through ME84 set the dispatch time (mn11) as 4.
    Execute ME84. Enter the agreement or the parameters to select the agreements that you want and execute. Check the error messages and if everything is okay run it again unchecking the Test run field.
    If you need more information just let us know.
    regards.

  • Print scheduling agreement release with zero demand

    Hello all,
    we have a print problem with purchasing scheduling agreements:
    when I go to ME38 to the scheduling agreement release docu and print out the latest release which has a zero amount for scheduled quantity, I'll get the error message
    no print relevant changes to document xxxx exist.
    ME140
    I know there are already some threads about this topic in the forums but I was not able to find a helpful answer yet.
    Thanks
    Anne

    hi
    please check the message which are already available status is "Green". if its green you have to create another message and you have to print it again..

  • Deactivate Scheduling Agreement Release Profile

    Hi,
    We have configured scheduling agreement release profile for JIT and forecast delivery schedules.
    For some reasons we do not want to use the release profile, we do not wont schedule line release using ME84.
    Can any one pls suggest how to deactivate the release and also if any other settings has to be unchecked.
    Pls do the needful.
    Regards,
    Neha

    Hi Prashanth,
    Changing the setting from 2 to 1 in source list will not be relevant as schedule lines has to be generated while MRP run.
    I understand that if the material is checked for JIT in material master and when the Doc type is LPA then the scheduling agreement automatimatically goes for release. Correct me if I am wrong.
    Should the config setting for creation profile to be deleted from SPRO settings.
    Pls lemme know.
    Regards,
    Neha

  • Exit for role determination via exit for scheduling agreement and contract?

    Hi..
    I have a requirement to fetch the agents in run-time for PO,PR,SCHEDULE AGREEMENT, CONTRACT..
    For PO i am using EXIT : - M06E0005
    For PR release i am using EXIT :- M06B0001
    By using above 2 exits i am getting the agents at run-time...
    Same way i need the EXIT for SCHEDULE AGREEMENT and CONTRACT..
    if there is any EXIT for this please share with me..
    Regards,
    Imtiaz Khan

    Hi Imtiaz,
    Ideally you should have your agent determination logic in workflow itself instead of determinining them in EXIT.
    Can you tell me why you are determining agents in exit and how you are making use of it ?
    Also let us know how your workflows are getting trigger for all these documents.
    Regards,
    Ibrahim

  • Scheduling Agreement Release Comparison

    Hi Experts
    does Scheduling agreement release comparison works for JIT delivery schedule (Doc Type LP) in SNC?
    if yes then how it works and how it is different than forecast delivery schedule release comparison (Doc Type LPA)
    Thanks

    Hi Indira,
           The are two ways to address your business case :
    1. The simple way is to forward the work item to the concerned person (by selecting the user from user list) for releasing the work item.
    2. In the second option, we need to modify the workflow. A conditional work item (Accept/Reject) needs to be inserted immdtly after the SA workitem to accept or reject the user decision. Based on the decision, the workitem will either show him the SAP user list to redirect the same for releasing or it should go to the concerned user automatically (in static agent assignment). In case of acceptance, it will go to next step bypassing the rejection loop.
    In case of any further queries, please revert.
    Regards,
    Ashish J. K.

  • Confirmation Control for Scheduling Agreement

    Hello Experts,
    I have got situation for subcontracting scheduling agreement where client doesn't need confirmation control. They want to perform GR against scheduling agreement after creating delivery schedule without extra activity(Confirmation).
    Process flow is:
    1. Create work order(generates purchase requisition for subcontracting activity)(CO01)
    2. Create delivery schedule against purchase requisition for scheduling agreement(ME38)
    3. Create delivery to supplier through ME2O
    4. Confirm Goods receipt(ME38)
    5. Goods receipt(MIGO)
    I am trying to avoid step 4.
    Standard scheduling agreement setup automaticially fetches confirmation control key 0004. If I am disabling it manually, and not performing step 4, system throws message "no GR relevant item in PO"
    Can somebody suggest settings to achieve my scenarion
    Thanks and Regards
    Gyanesh

    Hello PavanKumar,
    The inbound delivery is one type of confirmation you are receiving from the vendor so I dont think you will be able to create the inbound delivery without confirmation control key.
    Hope this helps.
    Arif Mansuri
    Reward if answre is helpful.

  • Automatic delivery schedule for Scheduling Agreement

    Hi all...........
    I like to create automatic delivery schedule both JIT & FRC schedules for Schedule agreement, means system has to suggest the schedule lines.
    I created SA and creation profile, when Im trying to generate JIT schedule system showing "Error generating release against scheduling agreement  (cause 2)".
    Pls let me know wht configuration I hve to do and pls let me know all the steps.
    I like to know output determination setting for SA releases also.
    regards
    Durga Ram

    Hi
    'Propose all Items" is ticked so that MIGO proposes all the items irrespective of the delivery date and quantity. This means that even if the delivery date has not yet been reached or the complete qty has been received, the system will still allow you to do the GR.
    Hope this clarifies.
    Thanks

  • Bapi for scheduling agr release

    hi could someone help me to findout bapi for scheduling aggrement releases
    transaction me84.

    Hi Alok,
    I am not sure about BAPI for this function.I suggest you try this kind of function with user exit like COOPA002 using appropriate program logic.
    Regards,
    Ashok

Maybe you are looking for