Custom Dispositon Action Not Removing Storage Location After Item Marked Transferred. (Doc ID 2642577.1)

Last updated on MAY 31, 2023

Applies to:

Symptoms

We created three custom dispositions to mimic the stock main "transfer" disposition action because it is not possible to create a custom disposition action based on just "transfer" action. These three custom disposition are based on the following stock actions.

Approve transfer (leave meta)
Mark Transfer (leave Meta)
Mark All Revisions Delete completed (leave metadata)

However, after taking an physical item through disposition (based on custom actions), the storage location values persists. The expected behavior is for these storage location values to be removed after the item has been transferred, which is how the stock "transfer" action behaves.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.