01-14-2009 5:22 AM
Hi Gurus,
We are trying to deallocate (undispatched) a bunch of planned orders using BDC through transaction CM40.
After getting all the planned orders to be deallocated into an internal table, I then passed it to the BDC "on the screen multiple selections" at the levelling in batch (filter), I have an error saying "Screen 0000 is too large for the batch input".
Is there any other way to pass this data to the BDC or is there a BAPI to deallocate (undispatch) planned orders.
Thanks for your help.
Edited by: Basil Balogun on Jan 14, 2009 6:23 AM
Edited by: Basil Balogun on Jan 14, 2009 6:23 AM
01-14-2009 6:39 AM
Hi,
This program might give you some hints:
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/scm/planned%2border%2bidoc%2bprogram
cheers
Aveek
04-07-2010 4:43 PM
Hello Basil,
did you get a solution for your problem? I have all planed orders in an internal table and want to undispatch only these planed orders via cm40.
Thx
Johannes Schulte
09-24-2014 11:36 PM
I had a similar problem and if you are tyring a BDC with CM40 the BDc exits when you click execute on the capacity levelling screen
thats because CM40 does a submit program to generate the selection screen for Capacity levelling and a leave statement inside it kicks it out of the selection sccreen
In online process that works fine, but when you call cm40 in a bdc then the leave statement takes it out of the bdc and does not dispatch/deallocate the orders
my solution was to do a sumbit program RCCYMAB1 with selection table
i dont know if this is the same problem that is depicted here, but for anyone in future this might help