Stock/Requirement list contains important transaction data such as various stock quantities, customer orders, purchase orders, production orders, and much more. Running program RMCPAMRP, which sends over the entire stock/requirement list at the material-plant level, triggers the transaction. The external system recognizes the type of transaction data by reading the relevant IDoc fields, and then extracts the information it needs for the DRP planning.

A few options are offered for program RMCPAMRP:

• If the aggregation flag is on, the program aggregates the sales order quantities per customer per day and suppresses the sales order numbers. This option is particularly useful for demand situations when high volume orders are presented.

• The net change flag is designed to reduce data traffic along with the no-MRP flag. If MRP is not used in the R/3 implementation, turning on both net change flag and no-MRP flag will only dispatch the stock/requirement lists of the materials for which an MRP-related transactions (such as creation, deletion and change of the sales orders, planned orders, edc.) have happened since running RMCPAMRP from the last time. If MRP is used, only the net-change flag should be turned on for net-change functionality. Program RMCPAMRP will then dispatch the stock/requirement lists of the materials for which an MRP-related transactions have happened since the last MRP run. Of course, you can turn off both flags in order not to use the net-change feature of the program.