Skip to Content

Collective Availability Check results getting deleted (possibly because of CIF)

Our system landscape is an integration between APO – R3. APO creates the planned orders and sends them to R3. Once the planned orders are in R3, we run MRP to generate capacity requirements and propose production/scheduled dates for the parent planned orders and explode requirements to the child proposals and generate PRs/planned orders.

Now during planned order processing, we do a collective availability check via tcodes MDVP / COMAC / COHV for all planned orders to ensure that all components are available before we convert them to production orders.

After the checks, standard SAP behavior would be to propose “Commitment Qtys” to compare to the “Requirement Qty” and indicate which components in the order are Missing Parts (marked with X)

COMAC/MDVP/COHV transactions would do this as expected BUT whenever we exit the transaction, the Availability Check results are NOT saved and wiped out.

Now we ran a test and closed all integration models and now no CIF queues are open and ran the Availability Check again. We saw that upon exit, the availability check results are saved and stay in the system.

My question is that what could be causing the wiping out of the data after every Availability Check and is there some setting we need to turn on in APO to stop this?

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Apr 26, 2017 at 08:15 AM

    Upvoting this thread

    Add comment
    10|10000 characters needed characters exceeded