Unnecessary Purchasing Processing Time in scheduling agreement

According to its business logic, the scheduling agreement is a document that has already been released by purchasing department, and its scheduling lines, that have been created by MRP are valid for goods receipt without any need for additional purchasing processing time. However, MRP scheduling incorrectly takes purchasing processing time into account (as defined in the IMG in plant parameters for external procurement - TCODE OPPQ) when calculating planned availability date. Please advise how to correct this issue.
Best Regards,
Itzik Eshed

This can be customized in
SAP Customizing Implementation Guide
-> Production
--> Material Requirements Planning
---> Planning
> Procurement Proposals
> Define External Procurement
Here you can select the indicator "Scheduling according to purchasing info record or agreement" either at plant or MRP group level.

Similar Messages

Is it possible to create a Purchase order wrt a Scheduling agreement?

Is it possible to create a Purchase order wrt a Scheduling agreement?

Hi,
It is not possible to create PO wrt a Scheduling Agreement. Po is basically a formal instruction given to the supplier by the purchasing dept. It is non-binding. Delivery of the goods is not mandatory for a PO. However, in the case of SA, we create SA
and maintain SA Schedule lines (ME38) with reference to SA. The agreement created with vendor is binding and fixed.
Hope it clarifies.
Regards,
Bijoy Kumar S.P.

BZTEK - Purchasing Processing Time to convert PR in PO

Hi all,
In SAP stanrdard, Purchasing Processing Time to convert PR in PO is maintainable in customizing at plant level.
As anyone any advice of solution to implement when there is a business need to have this time depending on:
- PO type
- PO type / material
Thank you,
Laetitia

Hello, Laëtitia,
not in standard; but you can modify the field FRGDT "Purchase Requisition Release Date" through customer enhancement MEREQ001 "Customers' Own Data in Purchase Requisition" / function EXIT_SAPLMEREQ_005 "Checking Customer's Own Purchase Requisition Data" -- yep, it sounds strange that you can change some standard fields thou function called " "Checking Customer's Own Data", but that is how it works (see enhancement documentation for details).
Of course, the PO type (or rather PREQ type) / Material Purchasing Processing Time will have to be stored in custom tables.
Kind Regards
TomT

BAPI_SCHEDULE_MAINTAIN throws error for time- independent scheduling agreement

Hi All,
I get the below error while modifying a stock transport Scheduling agreement in UI5 using BAPI “BAPI_SCHEDULE_MAINTAIN”
“Scheduling agreements with time-independent conditions are not supported”
Found a note 1046794-
"BAPI_SAG_CHANGE (and BAPI_SAG_CREATE) can only treat scheduling agreements with time-dependent conditions. Document conditions are not supported. Therefore, this kind of scheduling agreements cannot be processed. This is a missing functionality”
To meet some finance requirements, we need to use time-independent conditions in the scheduling sgreement, in order for a custom condition type to be picked up.
I'd appreciate any advice I can get about how to fix this functionality in the BAPI or alternatively how to link the pricing condition type to the Scheduling agreement document type?
Thanks so much.

Link between Time dependent / independent condition and Scheduling agreement document type is in configuration under SPRO>MM>PURCHASING>SCHEDULING AGREEMENT>DEFINE DOCUMENT TYPES>SCROLL TO THE RIGHT here you find a check box Time-D.C.
Thanks
DD

Planned delivery time in Scheduling agreement and MRP

Hello,
Do you know is it possible to determine system so that MRP run will consider the planned delivery time from the scheduling agreement line instead of material master? Now the system read planned delivery time from material master when creating schedule lines automatically by MRP-run.
Regards, jaana

This can be customized in
SAP Customizing Implementation Guide
-> Production
--> Material Requirements Planning
---> Planning
> Procurement Proposals
> Define External Procurement
Here you can select the indicator "Scheduling according to purchasing info record or agreement" either at plant or MRP group level.

Planned elivery time in scheduling agreement

Hi experts
problem is that the schedule lines (for external procurement) generated from MRP are not taking the "" Planned delivery time into consideration"". System is only taking the G.R processing time.
I have mentioned the Planned delivery time in .
1) Scheduling agreement for 1 day.
2) In material master for one day.
3) In info record 1 day.
e.g Suppose req date is 13.07.2008. MRP run date 4.07.2008.
a) Planned delivery time = 1 day . B) .r processing time = 3 days.
Now when i run the MRP on 4.07.2008.
Schedule line is generated on - 11.07.2008
Please Guide . How can i correct this.
Regards
Rahul Bhardwaj

dear colleagues,
please check in OPPQ , external procurement, and set the flag 'scheduling'
best regards

IDOC: MM purchase order to SD scheduling agreement

Dear experts,
Is below scenario technically feasible?
- Purchase order created in customer system, and sent to vendor system via IDOC
- Scheduling Agreement created in vendor system against the received IDOC
- Goods issue posted for delivery schedule of Scheduling Agreement, and sent to customer system via IDOC as Shipping Notification
- Inbound Delivery created for purchase order in customer system against the received IDOC.
- Billing created in vendor system and sent to customer system via IDOC
- Invoice verification created in customer system against the received IDOC.
The scenario is obviously feasible between Purchase Order-Sales Order, but I'm not sure whether it will work with Purchase Order- SD Scheduling Agreement or not. According to SAP Help, it seems that only MM Scheduling Agreement can work SD Scheduling Agreement.
Thanks a lot,
Duc.

Hello Indu,
I created two partner profiles but still receive that message above:
Partner No: 999999
Partner Type: LI
Outbound parameters: ORDERS
Outbound Options
Message type: ORDERS
Receiver port: A0000000006
Pack. size: 1
Basic type: ORDERS05
Message Control
Application: EF
Message type: Z40B
Process code: ME10
Partner No: XXXCLNT100
Partner Type: LS
Inbound parameters: ORDERS
Inbound Options
Message type: ORDERS
Process code: ORDE
Kind Regards,
Florian

Time-indepement Scheduling agreement with reference to contract

I want to attach pricing procedure to scheduling agreement, so I change LPA SA from time-dependent to time-independent.
But after the change, I can't reference contract to create SA. error message as below "Contr. release order only allowed for sch. agmts. w. time-dep. conditions".
How shoud I do to attach pricing procedure and create SA with reference to contract at the same time?

Hi,
please see the notes
160630 - Conditions in scheduling agreement with reference to contract
1046794 - FAQ: BAPI for outline agreement, questions 1 and 5
1034912 - MEMASSSA - document conditions are deleted
456691 - FAQ: Price determination in purchasing, question 4
Regards,
Edit

Concept of just in time in Scheduling Agreements

hi ,
can any one pl help out the concept of "JUST IN TIME "(JIT) , in Scheduling Agreements .

hi,
Schedule agreements allow you to have 2 different sets of schedule lines (VBEP-ABART).
In Standard SAP you can have two sets of schedule lines. One Forecast & the other JIT(just in time)
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 userexits to not reset.
pls reward points if the answer is helpful
REgards
Murali

Hw to caculate setup & Process time while scheduling?

Gurus,
Kindly guide me how the setup times & processing times are calculated in
http://help.sap.com/saphelp_46C/helpdata/EN/a5/63198843a211d189410000e829fbbd/frameset.htm
Really, I could not understand, why 1/8 (7.5 min) is added for setup time & 4/8 (30min) is added to process time in the example.
Best regards,
Kumar.

Sorry Gurus,
URL is not working fine. Hence iam pasting the content.
Example: Determining the Operation Dates
An order contains two operations (operation 10 and operation 20). The order quantity is 100 pieces and the order start date has been set to Tuesday, May 2nd. The scheduling type is forward scheduling.
Duration of the Individual Operation Segments for Operation 10
First, the system calculates the duration of the time segments for the operations (see Duration of the Operation Segments). To calculate the execution time, the system uses the formulas stored in the work center for setup, process or teardown and takes into account the performance efficiency rate specified for the individual standard values:
1 hour setup + 4 hours processing + 1 hour teardown = 6 hours execution time
The operation lead time is calculated by adding queue time and wait time to the execution time:
4 hours queue + 6 hours execution + 15 hours wait = 25 hours lead time
A move time of 0.5 hours is maintained between operation 10 and operation 20. This is assigned to the preceding operation (operation 10).
Calculating the Operating Time for Operation 10
The operating time of the work centers is calculated as follows:
The system calculates the working hours (standard available capacity) of the work center:
16:00 work finish - 7:00 work start = 9 working hours
The break times are subtracted from the working hours:
9 working hours - 1 hour breaks = 8 hours
The operating time of the move time is specified in the move time matrix: The shift starts at 7:00 and finishes at 17:00 and is a total of 10 hours.
Selecting a Calendar
The system now selects the valid factory calendars. The same factory calendar is maintained in both work centers. According to the factory calendar, work is carried out from Monday to Friday.
Calculating the Dates for Operation 10
The system has now collected all information relevant to scheduling and has calculated the duration of the individual operation segments. The next step is to calculate the operation dates. The system lines up the order floats and the individual operation segments along the time axis, taking into account the operating times.
The production order is scheduled using forwards scheduling so the system starts with the order start date (Tuesday, May 2nd).
Starting at the order start date, the float before production of one day is first added to the time axis. The scheduled start of the order is, therefore, Wednesday, May 3rd.
Starting from the scheduled start, the operation segments are now lined up on the time axis and the breaks are distributed proportionally among the individual operation segments.
Calculating the Operation Dates for Operation 10 Without Queue Time (Earliest Date)
Segment     Duration     Operating time/day     Start     Finish
Setup     1 hr     8 hr     3rd May 07:00:00     3rd May 08:07:30 1)
Process     4 hr     8 hr     3rd May 08:07:30      3rd May 12:37:30 2)
Teardown     1 hr     8 hr     3rd May 12:37:30      3rd May 13:45:00
Wait     15 hr     24 hr 3)     3rd May 13:45:00     4th May 04:45:00
Move      0.5 hr     10 hr     4th May 07:00:00      4th May 07:30:00
1) The wait time is scheduled independently of the factory calendar.
2) The duration of the setup results from: Setup = 1 hour * (1 + 1/8) = 1 hour 7.5 minutes
3) The duration of processing results from: Processing = 4 hour * (1 + 4/8) = 4.5 hours
Calculating the Operation Dates for Operation 10 with Queue Time (Earliest Date)
Segment     Duration     Operating time/day     Start     Finish
Queue     1 hr     8 hr     3rd May 07:00:00     3rd May 11:30:00 AM
Setup     1 hr     8 hr     3rd May 11:30:00      3rd May 12:37:30
Process     4 hr     8 hr     3rd May 12:37:30     4th May 08:07:30
Teardown     1 hr     8 hr     4th May 08:07:30     4th May 09:15:00
Wait     15 hr     24 hr *     4th May 09:15:00     5th May 00:15:00
Move      0.5 hr     10 hr     5th May 07:00:00     6th May 07:30:00

Delivery date is no use in scheduleing agreement.

We are using scheduling agreement and automatic schduling line for purchasing.
I already maintain delivery days =2 days and GR day=2days in scheduling agreement.
after MRP running, I found the delivery days is no use.
For example.
requirement date:2009.04.17
MRP result: scheduling line delivery date=2009.04.15 ( !only GR day=3 is in use)
I think the delivery date should be 2009.04.13
I am using standard TB (daiy lot size and the setting for Scheduling Requirements date := delivery date)
why is the delivery date no use in MRP running?
tks in advance.

Hi
If you have used GR processing time in scheduling agreement (example 2 days) if the requirement is on 25.04.2009, then proposed delivery date is for 23.04.2009. GR processing time reduces plans 2 worksday for processing and reduces 2 working days as per factory calender to propose delivery date.
Planned delivery time will not be considered if the requirement date is more closer than the planned delivery time. You will see an exception message in MRP results for that.
Regards
Antony

Update purchasing group in scheduling agreements

Hi gurus,
I'm trying to update purchasing group field in scheduling agreements, which are time-independent (EKKO-STAKO = ' ').
In my environment, I'm not authorized to use CALL TRANSACTION statement.
If possible, I'd need a way that works both in 4.6c and 6.0 versions.
I have tried several options, but none works:
-BAPI_SAG_CHANGE: "Scheduling agreements with time-independent conditions are not supported" (OSS note 1046794) (Also, this is not available in 4.6c)
-BAPI_SCHEDULE_MAINTAIN: "Scheduling agreements with time-independent conditions are not supported" (OSS note 1046794) (Also, this is not available in 4.6c)
-BAPI_AGREEMENT_MAINTAIN: Does not have the possibility to change field 'purchasing group'. (Moreover, it internally performs a CALL TRANSACTION).
-ME_UPDATE_AGREEMENT_PO: I've been not able to change field 'purchasing group'.
I'd be grateful about any hint. Thanks in advance!

In case it is useful for anyone else, I have solved the problem using:
CALL FUNCTION 'ME_UPDATE_DOCUMENT'
Thanks anyway!

Difference between Purchase Order and Scheduling Agreement

Can any one explain the main differences between a Purchase Order and a Scheduling Agreement?
Thanks in advance

Hi,
A Purchase Order is a document that is given to Vendor to indicate our intention to buy goods from them. It contains what is the desired goods, how much quantity, price, and the delivery date, among other things.
A standard procurement cycle for this is:
PR --> PO --> GR --> IV
A Scheduling Agreement however, is a type of an Outline Agreement. Outline Agreements are divided into 2, first one is Contracts and second is Scheduling Agreement. So this is basically a long term agreement with a particular vendor that contains details on what is the desired goods, quantity, and the exact delivery dates.
A standard cycle for this is:
PR --> Create Scheduling Agreement --> Maintain Delivery Schedule (agreed dates on when vendor will send the goods and time) --> GR --> IV
As you can see, for Scheduling Agreement, PO is not required, but instead we would need to Maintain Delivery Schedule.
Just to share on Contracts, it appears as below:
PR --> Contract Creation --> PO --> GR --> IV
Regards,
Nazrin

Purchase group Processing Time - Types,

Hi All,
I am looking into the different time taken for the purchase department to process their acitvities.
I could list a few times lke
1) PurchasING processing time ( T code - OMDT)
2) Pur Req to PO Conversion time (path : SPRO-IMG-MM-PURCHASING-PUR REQ-PROCESSING TIME)
Similarly I want your help in identifying if any more such times exists for Purchase dept in SAP.
Thanks,
Vengal Rao.

You have considered both the processing time defined for Purchasing. I believe there is no other processing time defined exclusively for Purchasing in SAP.

Reg purchasing department processing time MRP

Is The purchasing department processing time defined for the plant is taken into consideration by MRP while calculating purchase requisition release date??? If not then what is the use of this ? [Where do we configure this in SPRO] ?
SAP help says ..
The planned delivery time from the purchasing info record and the GR processing time are only taken into account if the purchase requisition was generated via materials planning.

This is what i understood please correct me if i am wrong
Requirement Date <GR Processing Time> Delivery Date <Plan Delivery Date>PODate <Plant purchase processing time> PR Release Date
Purchase process time will have effect on PR Release date not on Delivery date
Edited by: sasibhushan334 on Apr 28, 2010 2:08 AM

Unnecessary Purchasing Processing Time in scheduling agreement

Similar Messages

Maybe you are looking for