Question:
Hi,
I have to load transportation lanes into APO.
I tried to write a batch input for trans /SAPAPO/SCC_TL1.
But that doesn't work.
Does anyone know, if there is a Bapi or function module or what ever to get the data in. My source is a spreedsheet.
many thanks for you help
Answer:
Hi -
Use 'BAPI_TRLSRVAPS_SAVEMULTI' . Let me know if you have any questions.
vreddy5@ford.com
Regards
Answer:
Hi,
well I tried this BAPI already.
But its seem that there is no migration function coded yet.
This Bapi is doing all the checking’s and when everything is ok its calls a user exit. The user exit is of course empty. That’s all.
The same situation is with the function module
/SAPAPO/TR_TRANSPORTLANE_MAINT this module is doing all the checking’s and call then /SAPAPO/TR_TRANSPORTLANE_POST.
This one again is only a shell.
thanks
regars
Answer:
Hi-
What do mean by a migration function? This BAPI will rollback if there is any errors while commit. I guess you may be passing the parameters incorrectly. The main issue is with time series for Prod Procurement VALFR and VALTO also with Mean of Transport VALFR and VALTO. Let me know if you still have the issue. I can send my code if needed.
Regards
BSVR
Answer:
Hi ,
well you can't do much wrong with the parameters. format YYYYMMDD.
But there will be no commit in the BAPI you have to do this outside, as in all Bapi's.
Also the model Version is always checked against Version space.
Have you run this bapi successful in Version APO 3.0?
regard
Joachim
Answer:
Hi -
We have APO 3.1 . Commit is internal for this BAPI. I am not sure about this in 3.0. I have run this quite a times. Time series format is YYYYMMDDHHMMSS .
Regards
BSVR
Answer:
Hi,
the problem is that we are running APO 3.0.
The Bapi and also the function modules are already there,
but the update function is not included. It went in with APO 3.1
We will contact SAP. Maybe there is a delta package available.
Otherwise --
many thanks
Joachim
Answer:
Hi -
Did you try 'BAPI_TRANSACTION_COMMIT' for commit externally?
regards
BSVR
Answer:
Might be 3.0 not being up to date, I seem to remember that the excel based loader (which is just a front end to the BAPIs ) did not work in 3.0a for transport lanes specifically becuase the BAPI was not complete. Time for an OSS to SAP I think.
Also remember the general BAPI rules about total number of parameters (I could never get any BAPI to work with more than 149 parameters in total in 3.0).