Skip to Content

Relationships of routing tables:

/wp-content/uploads/2016/09/image_png_1031004.png

When deletion indicator in routing tables is set

PLPO-LOEKZ

LOEKZ in table PLPO is only set if you delete a sub-operation.

PLAS-LOEKZ

Deleting an operation should set the deletion flag in table PLAS.

See the explanation of this design in note 43595.

PLFL-LOEKZ

But deleting the entire sequence won’t set the indicator PLAS-LOEKZ, it will set PLFL-LOEKZ.

If the operations are deleted online in the routing – via the transaction CA02/CA22 – the operations are no longer shown on the operations screen of the routing, but they are still in the table PLPO without a deletion flag. The PLPO entries are deleted if one runs the transaction CA98 with the radio button “Objects Deleted Online” set for the respective routings.

PLMZ-LOEKZ

When deleting a component in CS02, the table PLMZ is NOT updated.  Items in table PLMZ are only deleted (or flagged with PLMZ-LOEKZ) from CA02/CA12/CA22/CA32 by removing the component allocation assignment. This is because the assignment itself is NOT stored in table PLMZ.  The component allocation is based upon a relationship between 2 tables, STPO and PLMZ. Deletion indicators are NOT set in table PLMZ when deleting BOM components from CS02. This is consistent to the design of the BOM and routing transactions. This behavior cannot be changed.

It is recommended to remove the component allocation associated with the items of a BOM in a routing, before deleting the BOM or the items themselves. Otherwise, it may leave orphaned PLMZ entries in the system.

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply