scheduling aggremets

[Former Member]

hi friends

i am deva

what is scheduling agrremnts? what is the purpose of its? process of scheduling agrrements?

[Former Member]

Hi

A schedule agreement contains details of a delivery schedule but a contract just contains quantity and price information and no details of specific delivery dates

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.

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, cum 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.

<b>For Further details make small search in sdn posts</b>

[Former Member]

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 surprise you with a large order qty, where your lead times are 5+ days. The foretasted qtys they sent last week should account for this.

To create a scheduling agreement, proceed as follows:

1. On the initial screen, choose Logistics

2. Sales and distribution Sales. Choose Outline agreement

3. Scheduling agreement Create. Enter the scheduling agreement type and, if necessary, the organizational data.

The values for sales organization, for distribution channel and the division are usually proposed from user-defined parameters. Entries for the sales office and the sales group are optional.

4. Choose Enter.

5. Enter the following data:

– Customer number of the sold-to party

– Customer purchase order number

– Material numbers

– Order quantities for the materials

6. To enter the delivery dates for an item, select the relevant item in the item overview and choose Goto

7. Item Schedule lines. Enter the necessary schedule lines.

http://web.mit.edu/sapr3/windocs/bpors11m.htm

[Former Member]

hi,

there are different types of scheduling agreements in SD:

- scheduling agreements without delivery schedules (like DS, or LP in German). This kind of scheduling agreements is similar to the standard order, but has a target quantity and multiple schedule lines to each item, which should be created manually.

- scheduling agreements with delivery schedules, here there are:

a) 'normal' scheduling agreements with delivery schedules (like LZ in the standard), the flow here: scheduling agreement => delivery

b) scheduling agreements with delivery orders (like LZM in the standard), the flow here: scheduling agreement LZM => delivery order TAM (is the order) => delivery

c) scheduling agreements with external agent service (like LK in the standard), the flow here: scheduling agreement LK => delivery to the consigment storage location => external agent delivery order ED (is the order) => delivery

d) scheduling agreements for self-billing process (like LZS in the standard), they are similar to LZ, but can be invoiced via self-billing IDOC only.

e) in Automotive system there are also specual scheduling agreements for JIT process.

All scheduling agreements can be created in transaction VA31, changed in VA32, displayed in VA33.

For sceduling agreement with delivery schedules you can use both forecast and JIT (Just-in-Time) delivery schedules. And you can indicate "MRP for DS type" (VBAK-ABDIS) from which schedule and when the requirements and deliveries could be created.

The first steps in VA31: give the sales area and scheduling agreement type, ENTER, give the sold-to party, PO number, material number, ENTER. Save.

The scheduling agreement is created.

To create the forecast schedule: VA32, mark the item, press the button "Forecast DS" below and then you can indicate the delivery schedule number, delivery schedule date and create the schedule lines. Save.

Similarly you can create the JIt schedule, but then you have to indicate JIT horizon, until the schedule is valid.

Deliveries can be created by a normal way.

If you create a new delivery schedule, you have to use the buttons "New DS w/o proposal" or "New DS with proposal". Lease take into account that creation of a new delivery schedule means that the old delivery schedule will be completely overwritten.

1. An outline agreement that is created for one or more materials and outlines the overall expected quantity of the material(s) to be delivered to the customer over a specific period of time. The scheduling agreement is used as a basis for delivering a material. The customer sends in scheduling agreement releases, referred to as delivery schedules, at regular intervals to release a quantity of the material.

2. The basic difference between contract and scheduling agreements is that - goods are delivered on specified dates and in specified quantities as per the agreement in case of scheduling agreements on the other hand contracts is just an agreement to supply either a certain quantity or certain value of items over certain period of time (validity period) to the customer. It doesn’t fix and delivery dates as in the case of scheduling agreements.

3. Data in scheduling agreements comes from three sources: (a) the customer sends in requested quantities and dates, normally by Electronic Data Interchange (EDI). (b) The component supplier enters data manually. (c) The system automatically copies data into the scheduling agreement from master records.

4. If there are still outstanding items in the agreement but you nevertheless want to close it, you can assign a reason for rejection to these items. The system then sets the status of the agreement as complete and the outstanding items no longer appear in the delivery due list.

5. To configure scheduling agreements IMG – sales and distribution – sales – sales documents – scheduling agreements with delivery schedules – define schedule line types (and) maintain planning delivery schedule. Instructions/splitting rules.

6. Option - define schedule line types - is nothing to do with schedule line categories. They are used for information purposes only. We will be focusing on JIT (Just In Time) delivery scheduling. Proceed to planning delivery schedule which is an internal delivery schedule used to plan requirements more efficiently.

7. Maintain planning delivery schedule instructions – these instructions determine the characteristics of the planning delivery schedule. RULES – these define “the split of schedule line quantities” between different days in planning delivery schedule and forecast delivery schedule.

Scheduling Agreement is an agreement between company and customer.

Basically the settings is create new sales document type copied fm LZM

I.category is LZN, for this we have to determine I.category(u know hw to do),

before that while creation of material u have to select and fill all MRP fields,

then only it's useful for MD04 and Availability check, after that create sch.agreements by va31, while creation of sch.agreement have to mentioned dates fm date to end date, based on dates u can create delivery and billing any time as a normal process.

CHAN