Community
Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Read only

Scheduling Operations for Work Order

Former Member

‎2006 Feb 17 4:39 PM

0 Likes
381

I'm having problems scheduling operations for work order <u>through the portal</u>. I'm encountering this error in both 4.6C and 4.7 portals.

From the portal, create a work order and save. Then go to operations and modify the first operation by adding the number of persons and duration. Then add 2 additional operations and save.

Now go to IW32 in R/3 and go to the operations tab. The number of persons and duration for my first operation are blank even though I modified it. And if I double-click on this operation, the "Requirement Assignment" tab is missing. But the rest of the operations are fine. It doesn't necessairly happen always on the first operations. Sometimes it's on the last one, kinda random.

But if I do this all in R/3 (create and add operations), everything is working well.

I'm using the BAPI_ALM_ORDER_MAINTAIN and although I did debugged it to find out the problem, I can't find it.

Any suggestions are highly appreciated.

I'm having problems scheduling operations for work order <u>through the portal</u>. I'm encountering this error in both 4.6C and 4.7 portals.

From the portal, create a work order and save. Then go to operations and modify the first operation by adding the number of persons and duration. Then add 2 additional operations and save.

Now go to IW32 in R/3 and go to the operations tab. The number of persons and duration for my first operation are blank even though I modified it. And if I double-click on this operation, the "Requirement Assignment" tab is missing. But the rest of the operations are fine. It doesn't necessairly happen always on the first operations. Sometimes it's on the last one, kinda random.

But if I do this all in R/3 (create and add operations), everything is working well.

I'm using the BAPI_ALM_ORDER_MAINTAIN and although I did debugged it to find out the problem, I can't find it.

Any suggestions are highly appreciated.

Reply
1 REPLY 1
Read only

suresh_datti
Active Contributor

‎2006 Feb 18 10:02 PM

0 Likes
352

Hi JB,

Did you go through the Documentation of this BAPI? It explains the various peculiarities in processing with this BAPI. Also there is a list of functions that cannot be performed with this BAPI. PL see if you might need to use BAPI_TRANSACTION_COMMIT.

Regards,

Suresh Datti