APO type of scheduling agreements

Hi Experts,
Here I really struggling with source of supply determination for APO type of scheduling agreements. In my case for OLTP type scheduling agreements, source of supply is getting determined but not for APO type. I have maintained required master data(LP type and ext planning indicator 1) in ECC. Please give your inputs this is very critical situation.
Thanks,
Shirish

Are the transportation lanes in APO maintained properly?
Aban

Similar Messages

Information on Requirements type in scheduling agreement

Does anyone can give me infomation about 'requirements type' found in the procurement tab of the scheduling agreement?

Hi,
The requirement type determination in orders/ SA as follows: requirements types are determined according to a specific search strategy beginning with the material strategy group. Strategy for Determining the Requirements Type
1. First, an attempt is made to find a requirements type using the strategy group in the material master.(note: Define a requirement type and a class for each strategy which you will define in the production module)
2. If the strategy group has not been maintained, the system will determine it using the MRP group.
3. If the MRP group has not been defined, the system uses the material type instead of the MRP group when accessing the corresponding control tables.
4. If no requirements type is found here, the system assumes a special rule and attempts to find a requirements type with the aid of the item category and the MRP type.
5. If this is not possible, a last attempt is made to find a requirements type with the item category only.
6. If the last attempt fails, the system declares the transaction as not relevant for the availability check or transfer of requirements
Hope this will help you to understand better
Regards,
Krishna O

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

Condition Types in Scheduling Agreement(Urgent)

Dear Experts.
This is a query with reference to my earlier issue Changes in Condition ME32L.As per suggestions, to get validity periods i have clicked on Time dependent Condition In SPRO settings Under Define document Types.
After that i am not able to enter Custom Conditions while creating a Scheduling Agreement.So i tried by removing this Time dependent setting,then was able to enter Custom Conditions...
But i need to see validity periods too when i change condition types through ME32L...
So,Please give me appropriate Suggestion....
Thanks and Regards
MK

I'm not sure about your own pric proc, but in standard it should works, and also its apply per organization level.
RM0000 and RM1000
    Control the price determination process in POs, quotations, and
    scheduling agreements.
    Both calculation schemas require 2 condition types for the gross
    price: one for automatic price determination (standard: PB00) and
    one for manual maintenance (standard: PBXX).
RM0001 and RM1001
    Determine which condition types you can enter in purchasing document
    headers with time-dependent conditions (e.g. contracts).

Change history (for perticular condition type) in scheduling agreement

All SAP Gurus,
We have a scheduling agreement, in which certain condition (condition type for freight condition) value have changed several times.
Where we can find the changes in the value of this condition type?
Regards,

Hi Rajan,
You should be able to see in
Item -- Statistics -- Changes. You can find that line item wise.

Date Type in Scheduling Agreements

Hi,
In a scheduling agreement when we have weekly or monthly schedules the system displays the date in the screen as 12/2010 or 13/2010 for say a weekly schedule.
However when the data is stored in the table the delivery date is always the first working day of the week. In this case when the week is 13/2010 the data is stored in the table as 22/03/2010.
Is there any way to change this to the last working day of the week?
Thanks in advance for your help.

Please check this:
I think you can configure the dates based on the splitting rules. Please check T Code VOZP
Define Splitting rules according to your requirement, maintain planning delivery schedule instructions and assign delivery schedule splitting rules.
Hope this helps

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.

Scheduling Agreements / Delivery Schedule / Firm zone, Trade zone

Dear all.
I am in the process of setting up scheduling agreements (LPA type) with firm zone and trade zone in SAP 4.5b
The following issues I have:
1.) with the release via ME84, it gives me an error 'no processing message ME 857, no message record found'.
As far as I know the customizing is correct. Can some one give a tip about what I maybe have forgotten?
2.) I am also using the firm and trade zone, but in the automatic generated delivery schedules line it is not turning up?
If there is any one who can help me with this subject, any information is welcome.
Thanks in advance.
Regards,
Wilfred

You have to create a condition record for your message type LPH1 in order to be able to generate the message (mn10).
At funcional level, try to update your schedule line manually through TCode me37 and then go to the ME84.
At customizing level, here are some things that were missing when it occurred to me :
Check in SPRO - Purchasing - Messages - Output Control - Message Types -
Define message type for scheduling agreement schedule lin - Fine-Tuned Control: Forecast Delivery Schedule/Expediter that you have operation 9 for LPH1 and the checkbox activated.
Check in SPRO - Purchasing - Messages - Output Control - Message Determination Schemas - DefineMessage Schema for Scheduling Agreement Release - Define Message Determ. Schema: Forecast Delivery Schedule/Ex in the control data : You must havefor LPH1 the requirement 109.
Hope it helps
Regards

IDOC for scheduling agreement

i need to create a Z output type for scheduling agreement(application EV in NACE) which triggers an idoc...Its for the whole agreement and not for each line item. ..i need to know the basic idoc type for scheduling agreement to be assigned in partner profile (like DELFOR for delivery schedule) in WE20..
Edited by: nevinphilip on May 10, 2010 9:30 AM

The DELFOR.DELFOR01 IDoc can be used for delivery scheduling. Is that what you're looking for?

Rounding quantity field in scheduling agreement not considered in JITK

Hello ALL,
I would like to consult to you a scenario I am facing when it comes to creating a scheduling agreement (VA31) and maintaining a Rounding Quantity (field ABLFZ) in it.
When using the standard LZ type scheduling agremeent, the Rounding quantity is considered when creating a delivery in VL10.
However, when using the LZJ type of scheduling agreement, the Rounding quantity is NOT considered when creating a delivery in JITK.
Can you please tell me what causes the case in LZJ scheduling agreement?
Thank you all in advance.

Hi,
This field is not available for Scheduling Agreement. It is only available for Purchase Order.
Even you will not get this in Field selection also.

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 without usage in MRP / MD04

Hello,
i want to use a scheduling agreement which isn't relevant for MRP. I use the standard agreement type LPA (Scheduling Agreement). The storage location for this process is marked as u201Cstock excluded from MRPu201D and the Source list record is also not relevant to MRP. Although I set these parameters, the schedules appear in MD04.
Is there any possibility like the requirement class in SD? In SD I can set the parameter "Transfer of requirements".
Regards
Andreas

It wont be possible to exclude seperate document type from MRP.
Excluding a Sloc wont work. MD04 list will show the Scheduling Agreement.
You can use a Custom 'Z' Logic to supress the Scheduling agreement from MD04. the program can be written in ABAP Code.

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 agreements with delivery schedule - Copy control

Hi,
I wonder, if it would be possible / would make sense to specify for sales document type "LZ - Scheduling agreements with delivery schedule" a copy control for referenced documents like quotations.
Is there anybody who already has experience in that field?
Thank you in advance for your answers.
Best Regards,
Melanie

Hi,
It is obvious that, a schedule agreement needs to come with the fixed delivery qty and dates.
Pls explain your requirement in detail so that you will get a clear solution.
Rgds,
Sivarajesh. j

APO type of scheduling agreements

Similar Messages

Maybe you are looking for