7/14/2019 Locking problems in collective conversion of planned orders

http://slidepdf.com/reader/full/locking-problems-in-collective-conversion-of-planned-orders 1/2

04/18/2013 Page 1 of 2

SAP Note 504255 - Locking problems in collectiveconversion of planned orders

 Note Language: English Version: 11 Validity: Valid Since 03/15/2002

Summary

Symptom 

You convert planned orders with Transaction CO41 or COR8 (collective

conversion) into production or process orders. Planned orders with the same

material, the same sales order or the same inspection lot are converted in

this case one after the other.

The first planned order is converted successfully, on the other hand the

conversion of the following planned orders runs incorrectly. From the

conversion log of the affected orders it follows, that the conversion of

the planned orders was terminated due to already locked material, sales

order or inspection lot.

Other terms

Collective conversion, CO41, COR8, lock, M3 897, M3897, CO 875, CO875,production order, process order, lock management, enqueue, dequeue

Reason and Prerequisites

During collective conversion, the planned orders are converted and updated

separately. Now, if several planned orders are converted for the same

material, sales order or inspection lot and delays of the update task

occurs, the lock situations described can occur as the locks of the

previously processed order have not yet been released by the update

program.

Solution

The MODIFICATION specified in the attachment has the effect that the system

only continues with the program during saving after the update task has

written all data to the database and the locks have been released. This

modification can impair the performance when saving the production or the

process orders including the planned order conversion and the mass

processing transactions which is the reason why this modification is not

included as a function in the R/3 standard system.

Remember that this note describes a MODIFICATION which differs from 

the standard behavior of the system. Therefore, the customer assumes

the responsibility for the implementation of this source code

change. Due to this reason, SAP AG does not provide any support or

 maintenance for the changed source code.

Header Data

Release Status: Released for Customer

Released on: 06/18/2012 14:09:40

Master Language: German

Priority: Recommendations/additional info

Category: Modification

Primary Component: PP-SFC-PLN Order Planning

Secondary Components:

PP-PI-POR Process Order

7/14/2019 Locking problems in collective conversion of planned orders

http://slidepdf.com/reader/full/locking-problems-in-collective-conversion-of-planned-orders 2/2

04/18/2013 Page 2 of 2

SAP Note 504255 - Locking problems in collectiveconversion of planned orders

 Valid Releases

Software Component Release From

Release

To

Release

and

Subsequent

SAP_APPL 46 46A 46BSAP_APPL 46C 46C 46C

SAP_APPL 470 470 470

SAP_APPL 500 500 500

SAP_APPL 600 600 600

SAP_APPL 602 602 602

SAP_APPL 603 603 603

SAP_APPL 604 604 604

SAP_APPL 605 605 605

SAP_APPL 606 606 606

Related Notes

Number Short Text

1529380 PPBICO40/PPBICOR8: Planned order conversion fails

374931 Inspection lots in status CRTD; without determined sample

170183 What to consider when applying modifications

 Attributes

Attribute Value

Transaction codes CO41

Modification the note contains a

modification

Correction Instructions

Correcti

on

Instruct

ions

Valid

from

Valid

to

Software

Component

Typ

e

*)

Reference

Correction

Last

Changed

379864 46C 470 SAP_APPL C 05/19/2003

01:40:59556038 46A 46B SAP_APPL C 05/14/2003

22:50:02

797388 500 602 SAP_APPL C 11/24/2008

08:31:53

1034411 603 603 SAP_APPL C 11/24/2008

23:22:36

1034416 604 605 SAP_APPL C 06/18/2012

07:05:46

1473293 605 606 SAP_APPL C 06/18/2012

07:04:57

*) C Correction, B Preprocessing, A Postprocessing, M Undefined Work