2009 Oct 28 1:34 PM
Dear all,
We have a rather strange and a very high priority problem while using the BADI WORKORDER_UPDATE for creation of Maintenance orders.
We have added some bespoke code into the method BEFORE_UPDATE of the BADI WORKORDER_UPDATE and expect it to be called everytime a maintenance order is created. It is called every single time a maintenance order is created, but only once if I schedule orders to be created through a maintenance plan.
For example, if I try to schedule a maintenance plan and create 10 orders using transaction IP10, the WORKORDER_UPDATE BADI is called only while creation of the first order and not the subsequent ones. We are in a fix at this stage since we have a lot of bespoke code which updates customer tables and the data for the 9 orders is totally lost!!
I just wonder why the BADI isn't called everytime !!! Any inputs please?!
Warm regards,
Vijay.
2009 Oct 28 1:44 PM
>
> Dear all,
>
> We have a rather strange and a very high priority problem while using the BADI WORKORDER_UPDATE for creation of Maintenance orders.
>
> We have added some bespoke code into the method BEFORE_UPDATE of the BADI WORKORDER_UPDATE and expect it to be called everytime a maintenance order is created. It is called every single time a maintenance order is created, but only once if I schedule orders to be created through a maintenance plan.
>
> For example, if I try to schedule a maintenance plan and create 10 orders using transaction IP10, the WORKORDER_UPDATE BADI is called only while creation of the first order and not the subsequent ones. We are in a fix at this stage since we have a lot of bespoke code which updates customer tables and the data for the 9 orders is totally lost!!
>
> I just wonder why the BADI isn't called everytime !!! Any inputs please?!
>
> Warm regards,
> Vijay.
As per my understanding this is similar to billing document and billing plan. which means, billing plan will have all the billing documents in the list so you need to check if it has any table which holds all the data.
When you schedule, may be all the 10 orders in one of the table in the badi and you may need to change the logic to see if there are any documents exists.
>
> Dear all,
>
> We have a rather strange and a very high priority problem while using the BADI WORKORDER_UPDATE for creation of Maintenance orders.
>
> We have added some bespoke code into the method BEFORE_UPDATE of the BADI WORKORDER_UPDATE and expect it to be called everytime a maintenance order is created. It is called every single time a maintenance order is created, but only once if I schedule orders to be created through a maintenance plan.
>
> For example, if I try to schedule a maintenance plan and create 10 orders using transaction IP10, the WORKORDER_UPDATE BADI is called only while creation of the first order and not the subsequent ones. We are in a fix at this stage since we have a lot of bespoke code which updates customer tables and the data for the 9 orders is totally lost!!
>
> I just wonder why the BADI isn't called everytime !!! Any inputs please?!
>
> Warm regards,
> Vijay.
As per my understanding this is similar to billing document and billing plan. which means, billing plan will have all the billing documents in the list so you need to check if it has any table which holds all the data.
When you schedule, may be all the 10 orders in one of the table in the badi and you may need to change the logic to see if there are any documents exists.
2009 Oct 28 1:44 PM
>
> Dear all,
>
> We have a rather strange and a very high priority problem while using the BADI WORKORDER_UPDATE for creation of Maintenance orders.
>
> We have added some bespoke code into the method BEFORE_UPDATE of the BADI WORKORDER_UPDATE and expect it to be called everytime a maintenance order is created. It is called every single time a maintenance order is created, but only once if I schedule orders to be created through a maintenance plan.
>
> For example, if I try to schedule a maintenance plan and create 10 orders using transaction IP10, the WORKORDER_UPDATE BADI is called only while creation of the first order and not the subsequent ones. We are in a fix at this stage since we have a lot of bespoke code which updates customer tables and the data for the 9 orders is totally lost!!
>
> I just wonder why the BADI isn't called everytime !!! Any inputs please?!
>
> Warm regards,
> Vijay.
As per my understanding this is similar to billing document and billing plan. which means, billing plan will have all the billing documents in the list so you need to check if it has any table which holds all the data.
When you schedule, may be all the 10 orders in one of the table in the badi and you may need to change the logic to see if there are any documents exists.
2009 Oct 28 1:53 PM
Thanks Sampath !!!
You are absolutely spot on there. All the orders are getting processed only once and the table it_header contains all orders that I was looking for.
Fantastic, Thanks!
Vijay
| User | Count |
|---|---|
| 3 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |