LPA Process

Dear All,
Our client needs SA LPA. I tried it out with it at ME38 i am getting an error while trying to generate Forc. Sch or JIT Sch. I get the following error.
Also check following can be the error sources;
- 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: Mintain 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.
Im MM - Purchasing view maintained JIT. MRP View Maintaind - PD & EX as per the Sap help.
If i try it out in ME84 getting error:-
no processing error message ME 857.
What is the procedure for it.
Based on this thread made it:-
me84 sa release problem
ME84 ISSUE
Tell me the process flow & if any config. How to maintain Condition in MN10 for output type.
Flow-
ME31L
MD03
ME38
ME84
ME9F
For this flow what is the Setting needed.
Thanks in Advance,
sapuser

Hi,
Please see IMG documentation at path.
Txn OLME>Messages >Output Control >Message Types >Define Message Types for Scheduling Agreement Release/Expediter
1. First maintain message types
Maintain Message Types for Forecast Delivery Schedule/Expediter
2. Then maintain that message type in Fine tuned and also set the "Update Print-Dependent Data" indicator
Fine-Tuned Control: Forecast Delivery Schedule/Expediter
3. If in print parameter for message type at step first is maintained as purchasing group, then ensure printer is defined for purchasing group at node "Assign Output Devices to Purchasing Groups" (same customizing path)
4. Maitain the condition record for message output type.
Kind Regards,
Suneet

Similar Messages

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

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.

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

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

How to create SA LPA from (ME31L,ME38,ME84, ME9E,Migo,Miro)

Hi,
Could any one tell me the process to use the transactions ME84.
What are all the configurations needs to be done ?
What are all the master data needs to be maintained ?
What is the business process process cycle.
Providing SAP library link for the above topic will be highly appreciated.
Regards,
DilliB

Hi,
In MM Purchasing, this term is used
A) as a generic term covering various kinds of order document issued against outline agreements (these may be release orders issued against contracts or - as here - scheduling agreement releases, i.e. types of rolling delivery schedule issued against scheduling agreements), and
B) in connection with an internal approval or expenditure authorization process for purchasing documents. In both cases, "releasing" can be regarded as equivalent to "giving the green light" to go ahead with a certain action (e.g. to the vendor to deliver a certain quantity of materials, to Purchasing to create or issue a PO for items requested by a user department).
---With release documentation (in the standard system, document type LPA)
The schedule lines in the system have internal character. This means that you can change them in any way you wish. They are not transmitted to the vendor until you explicitly create a scheduling agreement release (technically, such a release consists of a header and the current version of the delivery schedule and may take one of two forms: a forecast delivery schedule or a JIT delivery schedule).
The release documentation allows you to display the releases transmitted to a vendor over a certain period in order to establish exactly when you transmitted which information to the vendor.
---Without release documentation (in the standard system, document type LP)
The schedule lines immediately have official character. This means that they are transmitted to the vendor as soon as you save the schedule. There is no release documentation in this case.
rgds
Chidanand

SA doc.type LPA

Hi,
we are trying to work with SA doc.type LPA
Maintain:
1.JIT indicator in Material master
2.JIT indicator in SA additional data
3.creation profile in SA additional data
4.maint source list mrp relevant 2
5.created message record LPJ1 JIT Delivery Sched.(tcode mn10)
6.created message record LPJ2 JIT Delivery Sched.(tcode mn10)
7.created message record LPH1 ForecastDlv schedule
(tcode mn10)
8.created message record LPH2 ForecastDlv schedule
(tcode mn10)
9.maintain SA delivery sehdule Tcode ME38
10.WHILE CREATING RELEASES ME84 THE SYSTEM GIVE ERROR ( NO PROCESSING ERROR MESSAGE ME 857)
HOW COME TO CORRECT THIS ERROR

hi
the message is f
me 857 Not possible to determine valid ISO code for language
so try finding the language used or relevent configuration
language of plant and co code
regards
kunal

ME84 - how to exclude Sched Agreement LPA not valide anymore?

Hello all,
We work with LPA scheduling aggreements and define one per year. So validity dates are as follow
validity start 01.01.2008
validity end date 31.12.2008
Unfortunetly, ME84 selects all LPA SA , even those that have their valididity date in the past : for example , it tried to create release on SA valide in year 2007. Consequence : many errors are generated and disturb the MRP controller.
Who has the solution ?
thanks
BR

if there are no schedule lines then how the system is generating the release for those SA. i cant understand.
the process is as follows
create SA
generate schedule lines
and then release those schedule line using t-code ME84
but as per your comments there are no Schedule lines but for which schedule lines the system is generating release

Error while invoking a process

Hi Team,
I get the following error while invoking a process.
ALC-DSC-125-000: com.adobe.idp.dsc.registry.EndpointNotEnabledException: SOAP endpoint is not enabled for: ExtractingXML/ReadResource
at com.adobe.idp.dsc.provider.impl.base.AbstractMessageReceiver.validateEndpoint(AbstractMes sageReceiver.java:258)
at com.adobe.idp.dsc.provider.impl.soap.axis.sdk.SoapSdkEndpoint.invokeCall(SoapSdkEndpoint. java:136)
at com.adobe.idp.dsc.provider.impl.soap.axis.sdk.SoapSdkEndpoint.invoke(SoapSdkEndpoint.java :81)
at sun.reflect.GeneratedMethodAccessor755.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.axis.providers.java.RPCProvider.invokeMethod(RPCProvider.java:397)
at org.apache.axis.providers.java.RPCProvider.processMessage(RPCProvider.java:186)
at org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:323)
at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:454)
at org.apache.axis.server.AxisServer.invoke(AxisServer.java:281)
at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:699)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper. java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at com.adobe.idp.dsc.provider.impl.soap.axis.InvocationFilter.doFilter(InvocationFilter.java :43)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at com.adobe.idp.um.auth.filter.CSRFFilter.doFilter(CSRFFilter.java:41)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletC ontext.java:3496)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2 180)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Can anyone please help me with this error.

I checked my server (which has all the default Adobe services) and the only service I have that comes close is:
the Repository service's "Read Resource Content" operation. In the list that comes up as RepositoryService.
The Barcode's Extract to XML service. In the list that comes up as BarcodedFormsService
Neither of these is an exact match to the error. Is your process calling a sub process you built? Does that service actually exist on the server? If you do a record/playback (in workbench) on which step does the process fail?
If you look through the entire list of SOAP services (in Adminui) are any of them disabled?

Logical GR in Third Party Process

Hi Friends
There is logical GR involved in third party process. What if we do not want to trigger it?

very useful thraed for your Qn-
[stock not updating after doing MIGO (gr) for third party sales |stock not updating after doing MIGO (gr) for third party sales;
BR
Raj

EH&S WWI for GLM print request processing

Hi all,
we installed EH&S WWI for GLM print request processing scenario, following the note:"1394553", but when we try to print we receive this error from WWI:
Start Function 'WWI_PRINTREQUEST_CREATE'
Initializing parameters
Receiving data from client
   calling RfcGetData returned 0
    receiving data lasted: 0.0 sec.
    Retrieving print request data from RFC interface
    Using Temp Directory E:\WWI\TEMP\BSV100000000000062
   Delete files in E:\WWI\TEMP\BSV100000000000062
    Creating text file E:\WWI\TEMP\BSV100000000000062\r000000000062.val
    Writing data to text file 39 lines, 1009 characters
    Updating print request status from 0 to 1
    [DB time] Writing print request lasted 9 ms
Start processing command 'Create print request' in synchronous mode
Creating print request 000000000062
WwiSapDms::retrieveDocument: RFC error when calling ABAP function moduleRFC connection is not Unicode
WwiSapDms::retrieveDocument: RFC error when calling ABAP function module
key     : RFC_ERROR_SYSTEM_FAILURE
message : See RFC trace file or SAP system log for more details
Reading SBV document IB0120510 from Cache failed
    WwiCacheRead resulted with -1
    Updating print request status from 1 to 5
    [DB time] Writing print request lasted 4 ms
##### Command 'Create print request' finished with status E #####
    Storing ERR file E:\WWI\TEMP\BSV100000000000062\l000000000062.err into DMS succeeded
    22 lines
Sending data to client
   calling RfcSendData returned 0
    sending data lasted: 0.0 sec.
Elapsed time : 0.1 sec.
We don't understand what kind of RFC or what part of customizing we have to check, could you please help us?
Thanks,
Christian

Dear Pugal
we are not using GLM + and I am not sure about the technqiue used there to handle load balancing. Regarding general WWI setup I assume you know this Note: EH&amp;S: Availability and performance of WWI and Expert servers
On the top there is a further SAP Note abvailable which might be of interest. This is referenced here:
http://de.scribd.com/doc/191576739/011000358700000861002013-e
May be check OSS note: 1958655; OSS Note 1155294 is more related to normal WWI stuff; but may be check it as well. May be 1934253 might help better
May be this might help.
C.B.
PS: may be check as well: consolut - EHS_MD_140_01 - EH&amp;S-Management-Server einrichten
The load balancing of synchron WWi servers is donein the "RFC" layer, therefore you have no inffluence here, for asynchron WWI servers you can do a lot to manage the WWI load balancing by using "exits" etc.

If-statement in application-process

Hi,
First I will tell you which APEX I am using: 3.0.1
Ok, I have got a form where there are 4 fields:
P13_ACCTNO (Popup LOV (fetches first rowset)),
P13_LOCATION_NAME(Text Field (Disabled, saves state)),
P13_COMP_ACCTNO( Popup LOV (fetches first rowset)),
P13_LOCATION(Text Field (Disabled, saves state))
In my table, the company is always filled in, no null values (but it is not the PK, this is the acctno). But location may be null.
When I select a location (popup will only show fields which are filled in), then the other fields are filled in as well. So the Location (number) and the acctno is the same.
Now, when I select a comp_acctno, the rest of the fields are filled in automatically. But the Location (number) will remain from the first select, although no location might be there.
So I have got 2 javascript codes on the page and 2 applicationprocesses and 1 application item.
I would like to have an if-statement in my application-process (instead of " HTP.prn ('<item id="P13_LOCATION">' || v_null || '</item>');", something like:
if :p13_location_name is null then
:p13_location = ' ';
end if;
But I don't know how to put this into the following code, because it is a mixture, which I don't understand completely.
DECLARE
v_acctno primemines.acctno%type;
v_company primemines.company%type;
v_mineloc primemines.mineloc%type;
v_commodity primemines.commodity1%type;
v_null varchar2(5);
CURSOR cur_c
IS
SELECT acctno, mineloc, company, commodity1
FROM primemines
WHERE acctno = TO_NUMBER (:temporary_application_item);
BEGIN
FOR c IN cur_c
LOOP
v_acctno := c.acctno;
v_company := c.company;
v_mineloc := c.mineloc;
v_commodity :=c.commodity1;
END LOOP;
v_null := '';
OWA_UTIL.mime_header ('text/xml', FALSE);
HTP.p ('Cache-Control: no-cache');
HTP.p ('Pragma: no-cache');
OWA_UTIL.http_header_close;
HTP.prn ('<body>');
HTP.prn ('<desc>this xml genericly sets multiple items</desc>');
HTP.prn ('<item id="P13_ACCTNO">' || v_company || '</item>');
HTP.prn ('<item id="P13_LOCATION_NAME">' || v_MINELOC || '</item>');
HTP.prn ('<item id="P13_COMMODITY">' || v_commodity || '</item>');
HTP.prn ('<item id="P13_LOCATION">' || v_null || '</item>');
HTP.prn ('</body>');
and also I have discovered that the automatically filling of the fields is only working sometimes (i don't know whether it depends on the company I select). Any ideas, why this is happening?
could somebody help me with the code please?
Thanks,
regards,
Denise

Hi,
@Chad: thanks for the code, I think it works (UPDATE: no, it does not work :-( )
now i am just left with the other problem that it works only sometimes
@user512746: yes, i guess you have understood correctly. I have changed the items P13_ACCTNO source used to "always replace" and taken out the default value, which I had set to &P13_ACCTNO.
But it still only works partly, I don't know why?
any other ideas?
Thanks so much for your help so far, both of you.
Regards,
Denise

ANY SY-INDEX REFLECT CHANGES WHEN CONTROL BREAK STATEMENT PROCESS

Dear Guru's,
                 I have a requirement where i have to move the values to variable when control break (AT END OF) process. So i want to move the values according to the end of Vendor so for that i want to know is there any sy-index available which reflects changes when Control break (AT end of) process.
LIKE Sy-subrc = 0 when select statement fetches record or sy-tabix is like counter for loop.
Hope to get reply soon.
Regards,
Himanshu Rangappa

Hi,
There is no system Fields for it.
But your requirement can be done with 'AT NEW' and 'AT END' statement.
Refer this sample example,
loop at otab.
    at new module.
      move otab-module to otab2-module.
    ENDAT.
      at END OF effort.
      sum.               "Do your calculations here
      move otab-count to otab2-count.
      append otab2.
    endat.
endloop.

Invoices are not getting displayed in the process receivables for a cust.

Dear All.
Collection Management
I have a situation here in prod environment the worklist is displaying the customer and his outstanding balances/all the data when we select that customer and go for process receivables then i cant find any invoices/documents under the invoices tab.
But we have the open invoices in AR for that particular customer, I am wondering how the invoices will get deleted
Can some one help me in this issue..
Thank you,
D vasanth

Hi ,
Based on the requirement , check whether the customer contact has been done carried out for the invoice , then possibility it must have gone out of the worklist , chekc whether the Invoice posted in the AR has been transferred to FSCM collection .

LPA Process

Similar Messages

Maybe you are looking for