LPA scheduling agreement - Messaging functionalities

Hi,
Please may I know how I would set up messaging functionality for LPA Scheduling Agreements.
We need to email/fax the delivery schedules to our vendors.
Can any help me how I can configure to fulfill this requirement.
Regards,
Surya

Hi Surya,
You can go in customising of
OLME -->Messages >Message types->Define message type for SA>maintain message types
There are different message types
LPE2 ,
here you can put the standard programs and forms
Program SAPFM06P
Form routine ENTRY_LPE2
Form MEDRUCK
for LPET and so on .....it similar to customising of PO message outputs

Similar Messages

GR in LPA Schedule agreement

Hi
I am not able to perform GR for LPA schedule agreement, i did below
-- > Delivery scheduled maintained for today delivery via ME38
--> Message condition record maintained for JIT and forecast
--> JIT and Forecast are generated
I am not able to perform GR, please suggest what i missed
Thanks

This is what i followed
--->ME31l : created schedule agreement
---> Me38: delivery schedules created: few past and current date
---> ME84: JIT and FRC schdules are generated
---> messages for JIT/FRC are green, chose option of immediate output
When i go to ME38 --> delivery schedules -->SA release JIT and FRC lare yellow though messages are green
not able to post GR, not sure what i am missing

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

LPET Output equivalent for LPA Scheduling Agreements?

I am trying to capture the creation schedule lines on a Scheduling Agreement Delivery Schedule to communicate the demands to Third Party Carrier. I would like to use an Output with Special Function (Type 8) to gather data from the Scheduling Agreement and call our XI system (via Proxy) to generate a communication to the Third Party Carrier. My problem is that I don't want to communicate at the Release level, since it will be aggregate information. I am looking to communicate at the Delivery Schedule Line level.
The LPET output looks like a good choice, but it doesn't work for LPA Scheduling Agreements. Does anyone know of a way to configure the LPET Output to work with LPA documents? Or is there a different Delivery Schedule / Schedule Line Item Output that can be generated for LPA Scheduling Agreements?
Any help you could provide would be appreciated.
Thanks-
Ron

Hi,
LPA SA will only work as far as I am concerned with LPH1 (for FRC schedule releases) and LPJ1 (for JIT schedule releases). Is there any particular reason why the SA without release documentation can't work for your particular case?
Cheers,
HT

Schedule Agreement Message Output Determination

Hi Vishal
Can you give me some more details for Configuring the Schedule Agreement Output Determination in the same manner for which you have given for a PO.
My scenerio:
Making a contract with a Vendor --> Maintain Source list --> Giving MRP indicator as 2 in the source list for that delivery --> Running MRP for that material --> Checking the Schedule lines are generated in the Stock/Req list --> Now the schedule lines should send message output to the vendor via EDI/Print.
So give the answer relevant to above situation.
points already awarded to the previous question.
Thanks Vishal
Regards
Maruthi Ram

Hi,
PO Output Determination
Output of Purchase Order
1. Condition Table
SPRO > Material Management> Purchasing -> Message -> Output Control->Condition Tables->Define Condition Table for Purchase Order
Select:
Purchasing Doc. Type,
Purch. Organization,
Vendor
2. Access Sequences
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Access Sequences->Define Condition Table for Purchase Order
3. Message Type
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Types->Define Message Type for Purchase Order
4. Message Determination Schemas
4.1. Message Determination Schemas
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Maintain Message Determination Schema
4.2. Assign Schema to Purchase Order
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Assign Schema to Purchase Order
5. Partner Roles per Message Type
SPRO -> Material Management-> Purchasing -> Message -> Output Control-> Partner Roles per Message Type ->Define Partner Role for Purchase Order
6. Condition Record
Navigation Path: SAP Menu-> Logistics -> Material Management -> Purchasing-> Master data->Messages-> Purchase Order-> MN04-> Create
Now you create PO (ME21N) and save it. Go to ME22N and print the PO by giving output type.
GR Output Determination
Instead of Purchase order use Scheduling agreement
Output of GR
After setting table, access sequence and output type for GR,run MB02 transaction, enter material document number. Double click one line item and select messages. Separate screen will be opened to configure outputs. Give the required fields and save the document. Now Run MB90, you can take printout. Output Type: WE03 or WE01 or WE02
G.Ganesh Kumar

JIT output message appearing in FRC - LPA Schedule agreement

We have seperate messages for JIT and FRC, When i set JIT message condition record, its appearing in both JIT and FRC, not sure why, it suppose to be appearing in JIT only
Can some one help/suggest

Hi
You need to check the fine tune control of message type in the below config
spro>MM>purchasing>messagesoutput control->message types>define message type for SA/release
When you click there you get fine tune option. In that 9 for FRC and A for JIT. If you don't want to trigger FRC for XYZ condition type, remove that assign ment.
regards
Antony

LPA Schedule Agreement

Hi
1 Using LPA SA, Does allowed to make the MRP generated schedule lines delivery date manually ?. Prior to release or after the release before GR.
2 Even throug first time released prior to GR can i make again change in delivery date and re-release again.
Pls show some light on changes.
Rgds
Govind

Hi Govind,
As far as I know, standard SAP doesn't prevent manual changes to the delivery schedule after release of an LPA SA. Your creation profiles defines among many other things, which changes to the delivery schedule should trigger "re-release". You define them as percentage for the different periods, e.g. any change for the comming week, but only changes more than +/- 10% after the next week.
BR
Raf

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 Sheduling Agreement can not do GR

Hello all:
I creat a LPA Sheduling Agreement,and generate Forc/JIt Sched.the delivery time is today
But when i use MIGO can not make GR
Error message is"Document 5500000149   does not contain any selectable items"
Someone can give me some advice?
Thanks a lot

Hi!
Yes, in a LPA Scheduling Agreement the fact that no messages have been transmitted to the vendor is the reason why no goods receipts can be posted.
See the SAP Note 874264 (MB01/MIGO: Default quantity for goods receipt posting) about this:
This document type 'LPA' has been customized to work with Release Documentation:
Under the IMG path:
Materials Management
-> Purchasing
   -> Scheduling Agreement
      -> Define Document Types
you will see that the document type LPA has the "Indicator for scheduling agreement release documentation" (V_T161-LPHIS) set.
Starting with Release 4.5, for Scheduling Agreements with Release Documentation (this is, those with document type LPA), the open quantity is determined on the basis of the quantity known by the vendor:
When goods receipting a scheduling agreement that uses release documentation, in order to process a goods receipt, the system proposes the quantity from the last transmitted output message (please, take into account that this logic only works with scheduling agreements with release documentation (LPA), not so with LP).
This information can also be seen in the note 493404 - FAQ: Scheduling agreements.
The explanation given in this message is contained under the question number 9.
I hope this helps!
Esther

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

MRP Run with Scheduling Agreement

Hi All,
Can anyone explain the the Scheduling Agreements, we are running the MRP with schedule lines generated.I want to know the complete cycle with the T-codes in sequence they are executed.My requirement is business people need a demo of the Scheduling Agreement,type LP,LPA how they work and difference between LP and LPA.They run the MRP everyday.
Thanks,
Kris
Edited by: Csaba Szommer on Sep 19, 2011 12:52 PM

Hi,
The basic difference between LP and LPA is the way that the schedules are communicated to the vendor.
for more clarity please refer the blow links.
LP and LPA in scheduling agreement?????
Difference between LP and LPA scheduling agreements
http://it.toolbox.com/wiki/index.php/Scheduling_Agreement
Thanks.

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.

Reg. Scheduling agreements and contracts

Hi Dears
Please explain in greate details "what is schedule agreements" , "contracting", "How to use Scales in standard PO" and what is scales.
I couln't find the proper explanation in our Forums.
Bye
Rajkumar

Hi
(1) - Schedule agreements allow you to have 2 different sets of schedule lines (VBEP-ABART). Standard SAP you should have two sets of tabs - of schedule lines. One Forecast & the other JIT. Forecast forwards the schedule lines to planning (seen in MD04) and JIT passes them to shipping (VL10). They can be identical or different. Typically these are used for component supplier customers (namely Automotive). The customer will provide you 4-10 weekly buckets (usually a
Monday date) of future forecast qtys. Also send you 1-2 weeks of individual FIRM ship dates - which are entered on the JIT. It comes down to the customer not knowing exactly what they need next week, but they don't want to suprise you with a large order qty, where your lead times are 5+ days. The forecasted qtys they sent last week should account for this.
(2) Cumulative Quantities are tracked and influence how the schedule agreement passes requirements to both forecasting and shipping. These qtys are sometimes requested by the customer on ASNs. Cumulative qtys reset at year end unless you've got a customer calendar or you've modified standard SAP user exits to not reset.
Schedule agreements are very nice when the customer sends EDI data (830s = forecast or 862s = JITs). Outside of that they can really cause trouble regarding daily maintenance, missing requirements, *** qty corrections, year end processing, etc.
One alternative would be to use customer independent requirements - entering the weekly, monthly forecasting qtys and entering standard sales orders (with or without multiple schedule lines) to represent the true firm qtys.
Refer below
http://www.sap-basis-abap.com/mm/gr-creation-for-schedule-agreement.htm
You can fix a price in the info record for a say qty from 1-100 price RS150 & if the order qty is 101- 500- the prices is 140 . Scales cannot be used directly in PO but can be pulled into the PO from various master data like info record, quota arrangement.
For further details refer sdn thread below
Contracts
scheduling agreements
Message was edited by:
SHESAGIRI.G

LPA schdeluing agreement - GR b4 del date

Experts..
I created a LPA scheduling agreement. when I try to post goods reciept one day before the delivery date system is not allowing me. It showing "no suitable document found". but the same is possible in LP scheduling agreement.
How can we make LPA sch. agreement to allow GR before the delivery date??
Regards
RS

This is a standard SAP functionality, in which you cannot make GR before del date. If you wants to post GR then you need to change del date in LP.

LPA scheduling agreement - Messaging functionalities

Similar Messages

Maybe you are looking for