corrects both the confirmationcounter and the quantities, dates, and activities posted with the confirmation if the confirmation is a time ticket confirmation and if there is only one confirmation for the operation or for the phase.
You enter or cancel a confirmation for the operation or for the header of a production order, or for a phase or for the header of a process order.
This results in the runtime error SAPSQL_ARRAY_INSERT_DUPREC in the program SAPLCORV in the function module CO_RU_VB_CONFIRMATION_POST at the followingstatement:
INSERT afru FROM TABLE afru_i.
46C to 617
checks and corrects (if the UPDATE indicator is set) the confirmation counter in operations and phases.
46C to 617
checks and corrects (if the UPDATE radio button is set) the confirmation counter in the order header.
One or more confirmations have been posted for operations of production orders or phases of process orders. The confirmed quantities (yield, scrap, rework, where applicable) in the operation or phase data do not correspond to the actually confirmed quantities.
repairs inconsistent reservations with negative qtys like RESB-ESMNG for co- and byproducts
In an order with co-products or by-products the header quantity is changed. Afterwards the quantity of an order item is negative.For by-products, the quantity of the corresponding reservation items is negative.If the order is integrated with the SAP APO, the BOM item in question disappears in the APO as your receipt quantity is no longer greater than zero.As a consequence the system might generate short dump DYNPRO_FIELD_CONVERSION during the confirmation in the goods movement overview or for a goods movement.
Corrects status objects (JEST, JSTO) of objects within production orders with incorrect status.
In a production order/network/process order/maintenance order, there are objects for which no statuses exist. If you, for example, try to go to the operation overview, program termination "OBJECT_NOT_FOUND" occurs.Furthermore, when updating a production/process order an update termination with message "SAPSQL_ARRAY_INSERT_DUPREC" can occur in program SAPLBOOK. This is caused by temporary status objects in the database.
searches for long texts for production order reservations where the reservation doesn't exist anymore and deletes them
When you convert a planned order into a production order, the system issues error message TD607 when you save "I/O error for text AUFK xxxxxx MATK D". The system may issue the error if the bill of material (BOM) contains items that have more than one line of text.
compares the runtime of the MRP execution and also provides the total of planning elements (planned orders, purchase requisitions, etc) changed, created or deleted. It also shows which planning parameters where used and how much time MRP spent on each step (database read, BOM explosion, MRP calculation, scheduling, BAdIs, etc). With this information is possible to observe the relation of runtime and number of elements changed/created/deleted and also to see on which step MRP is taking more time.
for MRP performance issues
shows the "material hit list", that means, which materials had the highest runtime during the MRP execution and also on which step MRP is taking more time. Knowing which materials have the highest runtime, allow you to isolate the problem and reproduce it on MD03, where it is possible to run an ABAP or SQL trace for a more detailed analysis.
Capacity requirements planning terminates with error message BS 001 "No status object is available for ..." because incorrect status objects are stored in the database table KBED.The dump SAPSQL_ARRAY_INSERT_DUPREC occurs in CY_BT_KBED_POST_IN_OTHER_TASK due to an Insert into the table KBEZ.