Skip to Content
author's profile photo Former Member
Former Member

delivery schedules in SA(LPA)

Gurus,

I have created a LPA scheduling agreement and generated JIT schedule lines with Firm and Tradeoff zones through MRP.

Now, I want to release them manually.

could anyone let me know how these have to be released and sent to vendor with all the information about the zones.

I would really appreciate your help in this regard.

Cheers

Mittu G

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on Nov 22, 2007 at 08:29 AM

    Hi

    You can create the SA release using transaction ME84.

    Use transaction ME35L for approving/releasing the scheduling agreement.

    For SA releases to be transmitted as messages to the vendor, the following settings must be made in Customizing for Purchasing:

    Releases (Message Determination) at Item Level

    In order for a separate message to be generated for each SA release (i.e. per scheduling agreement item and release type), you must set the Release message indicator in Customizing for Purchasing under

    Define Message Schemas for SA Release/Expediter - > Assign Schema: SA Release/Expediter.

    If you do not select the Release message indicator, the messages will be generated at header level. You can then view the messages under

    Header-> Messages.

    If you select the Release message indicator, the messages will be generated at item level. The messages generated are listed in the release documentation.

    If you have initially not selected the indicator, messages will be generated at header level. If you select the Release message indicator at a later point in time, you will find the newly generated messages in the release documentation. You will still find the already generated messages under Header ->Messages.

    Define "Main Message Type"

    You must designate just one message type as the "main message type" for each SA release type (FRC or JIT delivery schedule) in Customizing for Purchasing, and set the indicator A (update print-dependent data) for this message type.

    This means that when an SA release with the "main message type" is outputted, the print-dependent data is updated in the SA item, the SA releases, and the delivery schedule lines. Only if an SA release is outputted with the main message type is it taken into account in the current stock/requirements list, for example.

    You set this indicator using the fine-tuned control facility for the message type.

    In the case of scheduling agreements with release documentation (document type LPA), the message types LPH1 and LPJ1 are used for forecast delivery schedules and JIT delivery schedules respectively in the standard system.

    In the case of scheduling agreements without release documentation (document type LP), the message type LPET is used in the standard system. In this case, no release is created. Instead, the message is generated as soon as the scheduling agreement delivery schedule (specifying the scheduled quantity) is created or changed.

    Outputting Releases in the Main Message Type

    All releases must always be created with the main message type because the system will otherwise not update the print-dependent data. This is particularly important if you are working with different message types.

    You send SA releases to the vendor with the main message type LPH1. You provide the forwarder or carrier with a copy (message type LPH2) and create a printout for your own files (message type LPH3).

    If you send SA releases to the majority of your vendors as printouts (i.e. in hardcopy form) and have an EDI arrangement with just a few of them, you can create message records for the main message type:

    At document type level with the transmission medium "Print", and

    At vendor/purchasing organization/EDI level with the transmission medium "EDI" for the EDI vendors.

    Do not set the change indicator in the message overview. A set indicator has no effect in the case of scheduling agreement releases. As a general rule, the system outputs all releases that have not yet been transmitted.

    For full details you can follow the link

    http://help.sap.com/saphelp_47x200/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm

    Thanks & regards

    Kishore

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Mittu,

      This depends a bit on how you communicate to your vendors.

      Assuming EDI, then the message to the vendor will contain a few date fields

      A. ABFDE End of production go-ahead

      Which is the 'end' of the FIRM ZONE

      B. ABMDE End of material go-ahead

      Which is the 'end' of the TRADEOFF ZONE.

      Upon receipt the vendors system will recognize these dates.

      Assuming printout, you need to work in SAP-Script/Smartform to detail the effect of these date on your print.

      Either by also mentioning these in the item header (remember each item has an unique FZ/ToZ setting). Or by using special markers on the date lines, based on these dates.

      KR

      Jan Tjalling

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.