Prior to the Feb, 2018 release, the following did not always hold true. If you are/were seeing inconsistencies, see Bug Report: Push Data failed. It also includes information about how the data cap works, as it is different between Data Maps and Smart Pushes, which is worth reading.

Data Movement Limits Identified

I got the following information from Oracle, and it is useful if you are using the data movement functionality. When these are developed, it is a good idea to evaluate the size and plan for growth. If the production data movements are nearing the thresholds, it is recommended to be proactive and try to reduce the POV that is used to move the data. If it can’t be reduced, one option is to split it into multiple pushes which can be done with Smart Pushes on the Data Form save, or with Groovy. Groovy also allows you to further condense the POV by dynamically changing the POV based on the cells edited, which is the most productive and efficient way to handle these.

So, here is what was documented. The data limits imposed on the movement methods are below.

There is not a cap when running a Data Map

When executing the following, there is a cap of 100MB

Smart Push on a Data Form

Smart Push via a Groovy Calculation

Data Map via a Groovy Calculation

Summary

If you are not seeing this, I would recommend opening a ticket with Oracle to resolve. I will be writing a post explaining how to execute and override POVs in Smart Pushes and Data Maps with a Groovy Calculation in the near future, so look for an article in my Adventures in Groovy series.