Error while GR against scheduling agreement

Hello,
I am doing the GR against the scheduling agreement, but system doesn't allow me to do GR. I get the error message as 'Transaction cannot be posted due to errors in price determination' error ME573.
What can be the cause of this error?
Thanks,
Input

Input_Output wrote:
Hello,
>
> I am doing the GR against the scheduling agreement, but system doesn't allow me to do GR. I get the error message as 'Transaction cannot be posted due to errors in price determination' error ME573.
>
> What can be the cause of this error?
>
> Thanks,
> Input
Hi,
Check the pricing procedure you have used if it is properly assigned to the vendor thru schema group and to the purch organization. Perhaps assignments are missing.
Shiva

Similar Messages

  • Error generating release against scheduling agreement

    Need help in resolving the below error msg for Scheduling Agreement.
    ERROR message:
    "Error generating release against scheduling agreement  (cause 2)"
    "2: The forecast delivery schedule or the JIT delivery schedule was generated but no message record could be generated."

    Yes.. its solved now...
    problem areas:
    1: delivery date not matching GR date.
        solution: chng delvry date to GR date in ME38 and thn do GR.
    2: Release not hapnd properly incase if u hav used doc typ LPA for JIT/Forcasting.
        solution: in ME84, chk if the indicator for 'create release' is 'green' for ur SA#. In ME38, select the line and click on 'Release" icon. Select ur relevant delivery schudle line and click on JIT release or Forcast Release icon. See if the indicator is 'Green". If not, the issue is wit message output for the perticular delivry date. (use msg typ LPET process for output) MAKE SURE U SAVE THIS CHNG. Chk againg for the Release indicator for delivry line. If green thn.. its done..
    Let me know if it was hlpful... or need clarity

  • 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

  • Error generating release against Scheduling agreement (Cause 2)

    dear Sap Experts,
    Please advise me that Error generating release against Scheduling agreement (Cause 2)
    As i have already used transaction code OMQP  and click print operation 9 for LPH1 & LPJI A,
    How can i sort this problem.
    Thanks
    mohit

    Hi,
    pls find below thread
    SA delivery schedule release problem
    you have to Maintain condition records for LPJ1 and LPF1 in NACE
    maintain condition record in transaction MN10 for schedule release. And Generally in the condition records will be maintained for LPH1 & LPJ1in MN10.
    Once you maintain that, you can go to ME84 and ME38 release the schedule
    the JIT indicator in MMR for your material.
    Check that and also you can maintain a release creation profile in VMR or ME31L.
    Regards
    Raj.

  • Sap Error generating release against scheduling agreement  (cause 2)

    Hi,
    Please help me on this issue
    Error generating release against scheduling agreement  (cause 2)
    Message no. 06857
    Regards
    Amey

    Hi,
    For EDI you might be missing settings in:
    1) Matrl Mng -> Purchasing -> Messages -> Output control -> Output types -> Define Message Types for Scheduling Agreement Release/Expediter -> Fine-Tuned Control: Forecast Delivery Schedule/Expediter (check one of the outputs for 9 and for A )
    2) WE20  - EDI settings for partner that is a vendor who should receive your release information  DELFOR / DELJIT (if you do not manage other EDI settings then also other WEDI setings should be maintained)
    Best Regards,
    Tomek

  • Error while I maintian Schedule agreement

    Hi ,
    As i amintian the Schedule agreement material in   Me38 , i have defined the dates and quantity and the st del date , and then i try to save the same it give the following error.
    *"SCOURDE NOT INCLUDED IN LIST DESPITE SOURCE LIST REQUIRMENT"
    Kindly let me know what is the likely error and how it could be resolved.
    regards
    Kim Roger.

    Hi,
    check in MM01 in Purchasing View Below tab
    Uncheck the Source list.
    also check in IMG
    Materials Management > Source list> Source Req. at Plant level
    Uncheck the box for your plant.
    or else
    mainain a proper source of supply

  • Perform Post Goods Receipt Against Scheduling Agreement

    Dear all,
    I've weird problem here. This is concering GR against Scheduling Agreement. I've a "LPA" type Scheduling Agreement and all the delivery schedule maintained and schedule line released successfully in ME38.
    When I do GR via MIGO by entering the Scheduling Agreement #, a prompt was given with no items selected. Note: My schedule line delivery date = GR posting date.
    What I did was, inside MIGO I go to Settings | Default Values and check on "Propose All Items". Finally, the affected line item appears but with "blank" quantity. So, I key in the actual quantity per the released schedule line and complete the GR posting successfully.
    Question 1: Why do I need to perform the MIGO propose all items setting? Normal PGR against PO doesn't require this.
    Question 2: Is this a standard SAP behavior or I'm doing PGR - scheduling agreement process the wrong way?
    Appreciate any expert clarification.
    Thanks in advance.
    Steven

    Hi Jurgen,
    I've read Notes 493404 and I'm facing Question 10
    10. Question:
    For the goods receipt for the scheduling agreement the system displays error M7 064: "Document xx does not contain any selectable items".
    Answer:
    A possible reason is that the document is subject to a release strategy and has yet to be released. You can check this using transaction ME33 and release it subsequently if necessary.
    Another reason can be that although a confirmation control key that contains a confirmation category with GR assignment has been maintained for the scheduling agreement item, this category has yet to be confirmed. You can check this using transactions ME33 and OMGZ. If necessary, create the relevant confirmation.
    Another reason may be that no undelivered schedule line exists up to the posting date. If nevertheless you want to post the GR, you can use transaction ME38 to bring the next schedule line date forward, or in transaction MB01 you can select the "Suggest Zero Lines" field or in transaction MIGO the "Propose All Items" field under Settings - Default values.
    From the snapshot of the notes 493404 above:
    1. I don't have a release strategy for the scheduling agreement. Have checked via ME33L
    2. I didn't implement any confirmation control in the scheduling agreement. Have checked via ME33L
    3. I've a delivery schedule line up to the posting date. In my scenario, schedule line date = GR posting date
    Therefore, I'm still truly puzzle with the system behavior. Any further help will be most appreciated.
    Thanks.
    Steven

  • Good Receipt against Scheduling Agreement

    Hi,
    I have created Scheduling Agreement and maintained delivery Schedule.
    No while making Good Receipt against scheduling agreement, system give message that no item exist.
    I have given date in delivery schedule for e.g 27.06.2008 and I am entering good receipt on 26.06.2008. But it is not possible.
    Once I change the date to 26.06.2008 in delivery schedule, then system allow to post a good receipt.
    Why, Is there any setting to remove this?
    Waiting for your reply.
    Thanks,
    Samir Bhatt

    Hi,
    Definition of Scheduling Agreement: - A form of outline purchase agreement under which materials are procured on predetermined dates within a certain time period.
    This means schedule lines are fixed and you can only do Goods Receipt on the prodefined schedules. If you do not want this function then better create Contracts and then PO w.r.t. Contract.

  • Error in creating a schedule agreement

    hi friends
    i got an error in creating a scheduling agreement
    the error reads- 'zjk5(the output type ) is not defined'
    condition records,port definition,partner profiles everything is fine.
    another error that reads is 'No communication data is set for medium 6ie edi'
    please answer this problem.thanks is advance.

    Hi,
    Check the Output type was created or not for that Scheduling Afreement?
    check the table T685 for that Output type?
    And n the diocument have you configured the Output type with the correct medium (EDI  value 6) and have you assigned the same in NACE tcode?
    check
    reward points if useful
    regards,
    Anji

  • Getting multiple error while refreshing or scheduling WebI report

    Hi BO Admin Experts ,
    Feacing  multiple errors  while refreshing or scheduling webi reports in BI4.0 CMC ,
    Please find the below errors :
    1)report schedule status failed
    2)Parameters : xxxcorp-franklinee; ATOu supply unv
    Error Message : An internal error occured while calling 'ProcessDPcmndsEx' API (Error:ERR_WIS_30270)
    3 ) Format : WebI
    Parameters : 10000000000159270
    Error Message :CORBA error while communicating with the SL service
    Could you please help me on the abive 3 issues for the WebI schedule reports
    Cheers ,
    Pradeep Gorpadu

    Hi,
    While refreshing the WEBI Reports would recommend you check the WEBI PROCESSING Server's last changed date from CMC--> Servers.
    Check when you are refreshing the reports, do you see the time stamp changed of WEBI PROCESSING servers?
    Do you keep getting this error messages for all WEBI reports? Can you re-produce this with simple e-fashion reports as well?
    After that go to the node where WEBI PROCESSING servers installed and check on the event viewer details if you see any relevant error messages.
    Regards,
    Upendra

  • OIM 11g error while running the scheduler

    Hi All,
    we have created on few custom schedulers to carry out trustetd recon and doing the create , modify and delete operations on OIM entities. all were running fine earlier. Now we started facing the below error while running any scheduler. Please find the OIM diagonostic logs below.
    scheduler status is not changing to running and scheduler logs and events r also not getting generated. please find the logs below.
    2012-09-04T11:03:38.355+05:30] [oim_server1] [NOTIFICATION] [IAM-0080006] [oracle.iam.platform.kernel.impl] [tid: [ACTIVE].ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: xelsysadm] [ecid: 11d1def534ea1be0:5b04d370:1398fc0c0cc:-8000-0000000000000067,0] [APP: oim#11.1.1.3.0] Orchestration process moved to failed stage, and the corresponding error is - {0}[[
    oracle.iam.platform.kernel.EventFailedException: Operation - UNSCHEDULE that is submitted as part of the orchestration is not supported.
    Completed orchestration with action result - oracle.iam.platform.kernel.EventFailedException: Operation - UNSCHEDULE that is submitted as part of the orchestration is not supported.
    [2012-09-04T11:03:38.430+05:30] [oim_server1] [NOTIFICATION] [IAM-1010010] [oracle.iam.platform.authz.impl] [tid: [ACTIVE].ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: xelsysadm] [ecid: 11d1def534ea1be0:5b04d370:1398fc0c0cc:-8000-0000000000000067,0] [APP: oim#11.1.1.3.0] ********** Entering the Authorization Segment with parameters:: LoggedInUserId = 1, target resourceID = null, Feature = SCHEDULER, Action = JOB_MODIFY **********
    [2012-09-04T11:03:38.430+05:30] [oim_server1] [NOTIFICATION] [IAM-1010029] [oracle.iam.platform.authz.impl] [tid: [ACTIVE].ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: xelsysadm] [ecid: 11d1def534ea1be0:5b04d370:1398fc0c0cc:-8000-0000000000000067,0] [APP: oim#11.1.1.3.0] OES Results found in cache with Key F: SCHEDULERS: 1P: JOB_MODIFYOESDefinition
    [2012-09-04T11:03:38.431+05:30] [oim_server1] [NOTIFICATION] [IAM-1010021] [oracle.iam.platform.authz.impl] [tid: [ACTIVE].ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: xelsysadm] [ecid: 11d1def534ea1be0:5b04d370:1398fc0c0cc:-8000-0000000000000067,0] [APP: oim#11.1.1.3.0] Validating the Internal Obligations: [InternalObligation: name: noop, values: [true], convertToObligation: false, InternalObligation: name: noop, values: [true], convertToObligation: false]
    [2012-09-04T11:03:38.431+05:30] [oim_server1] [NOTIFICATION] [IAM-1010022] [oracle.iam.platform.authz.impl] [tid: [ACTIVE].ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: xelsysadm] [ecid: 11d1def534ea1be0:5b04d370:1398fc0c0cc:-8000-0000000000000067,0] [APP: oim#11.1.1.3.0] ---------- The list of Internal Obligation is satisfied, returning TRUE ----------
    [2012-09-04T11:03:38.431+05:30] [oim_server1] [NOTIFICATION] [IAM-1010026] [oracle.iam.platform.authz.impl] [tid: [ACTIVE].ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: xelsysadm] [ecid: 11d1def534ea1be0:5b04d370:1398fc0c0cc:-8000-0000000000000067,0] [APP: oim#11.1.1.3.0] ********** Exiting the Authorization Segment with result Decision :PERMIT[[
    Obligations from policy: **********
    [2012-09-04T11:03:38.598+05:30] [oim_server1] [NOTIFICATION] [IAM-0080013] [oracle.iam.platform.kernel.impl] [tid: [ACTIVE].ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: xelsysadm] [ecid: 11d1def534ea1be0:5b04d370:1398fc0c0cc:-8000-0000000000000067,0] [APP: oim#11.1.1.3.0] Kernel executing default validation with process id, event id, entity and operation 709,251.0.JobDetails.UPDATE
    [2012-09-04T11:03:38.875+05:30] [oim_server1] [NOTIFICATION] [IAM-0080014] [oracle.iam.platform.kernel.impl] [tid: [ACTIVE].ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: xelsysadm] [ecid: 11d1def534ea1be0:5b04d370:1398fc0c0cc:-8000-0000000000000067,0] [APP: oim#11.1.1.3.0] Kernel executing default action handler with process id, event id, entity and operation 709,251.2,295,568.JobDetails.UPDATE.entityId=null
    [2012-09-04T11:03:38.875+05:30] [oim_server1] [NOTIFICATION] [IAM-0080001] [oracle.iam.platform.kernel.impl] [tid: [ACTIVE].ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: xelsysadm] [ecid: 11d1def534ea1be0:5b04d370:1398fc0c0cc:-8000-0000000000000067,0] [APP: oim#11.1.1.3.0] An error occurred while executing the kernel event handler.[[
    oracle.iam.platform.kernel.EventFailedException: Operation - UPDATE that is submitted as part of the orchestration is not supported.
         at oracle.iam.platform.kernel.impl.EntityDefaultActionHandler.execute(EntityDefaultActionHandler.java:53)
    thanks.

    I got one similar issue before. In my case was with event handler. It was a sintax issue.
    Example:
    I wrote this: <action-handler Class="...
    instead of this: <action-handler class="...
    So, in your case III suggest you to check if have any plugin invalid syntax and re-import your schedule task plugin.
    <oimplugins xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <plugins pluginpoint=.....
    <plugin pluginclass= .....
    </plugin>
    Let me know if you have any doubt.
    I hope this helps,
    Thiago Leoncio.

  • Movement Type 351 against scheduling agreement for future dates

    Dear Gurus,
    For stock transfer orders(Inter Plant Transfers), if the schedules in receiving plants are available only in future(say after 15 days), the sending plant is able to make 351 against such scheduling agreements today itself.
    Is there any way to control 351 movements against these scheduling agreements.
    Please reply.
    Points would be awarded.
    Regards
    Shankar

    Hi,
    we are taking multiple GR against Scheduling Agreement hence for Parking Invoice we are using "Delivery Note" as reference.
    but when we maintain delivery note system is not showing multiple GRs against Scheduling Agreement
    Invoice Parking is not done against these Invoice
    Please advce

  • Pending DO list against Scheduling Agreement

    Hi All,
    Could someone tell me how to extraxt list for pending DO list against Scheduling Agreement?
    Please reply me.
    Thanks,
    Sangeetha

    Use t.code ME3L report select selection perameters according to your requirement.
    Material wise ME3M - By material
    Material group wise ME3C - By material group .

  • DO List against Scheduling Agreement

    Hi All,
    Could someone tell me how to extraxt list for pending DO list against Scheduling Agreement?
    Please reply me.
    Thanks,
    Sangeetha

    Hi,
    Check if  ME91E(Scheduling Agreement Schedules: Urging/Reminders) can be used.
    Regards

  • In MIGO against Scheduling agreement for Consignment error

    Dear SAP Gurus,
    I m getting abn error in MIGO for SA
    "Maintain pricing conditions for the material for the excise invoice date"
    vinod

    >
    GSMY Volvo wrote:
    > Hello,
    >
    > We want to receive material against delivery schedules of Scheduling agreement.
    >
    > Our setting are.
    > No MRP
    > Delivery schedules are created manually.
    > No confirmatin control.
    >
    > Issue is, delivery schedules are future date but i want to make MIGO today without changing the delivery schedules in ME38.
    > Is it standard SAP setting that we will not be able to receive the material for future dates ? or is there some setting in background ?
    >
    > Sundar
    Its standard SAP setting that migo cannot be done with delivery in future dates. To do migo, change the delivery schedule to today's date and then do the GR against the SA.

Maybe you are looking for