I am trying to do background processing of updating the quotation status(VA22) through BDC. I extended the object bus2031 with a method for bdc. it is testing fine in method. But when testing the workflow - status is not bieng updated, in other words BDC is not working properly. What could be the problem. Please advice.
Please check the Binding between the Workflow->Task and Task->method and vice versa. Please check the Workflow Container element and Task container whether it is appearing properly. Please make sure you are using identical Business object in Method and Workflow. It should be BUS2031 if it is delegated to your custom BO.
Thanks guys --- the problem was I was using z business object in method and business obj in workflow, as arghadip pointed out. Bindings were good. Problem was resolved when I used BUS2031 in both workflow and method.
But I still dont understand why this should be a problem.
Also, I had another problem while implementing BDC. When I copy pasted the program from SE38 into method - its giving me syntax error saying incomplete nesting for form subroutine while everything is perfect in SE38. I resolved this by calling bdc report in se38 and passing values by import and export statements. What do you guys think might have caused the problem.
Posted the question in the same thread as it is relevant.
Did you have a form inside your program? Methods in BOR object types are really forms, just double-click the "begin_method" statement in the program and you'll see it in the macro definition. It is impressive how well BOR functions and acts as an object-oriented solution, when it's all really just an OO facade for standard programs, held together by macro definitions.
Anyway, if you try to define a form inside a method you get an error, as nested forms are not allowed. Instead you should define a separate method, just like you would if you were implementing an ABAP Object class for the same purpose. Alternatively, just "outsource" the whole thing and call a function module or submit a report as I understand you have done.
It's a long shot, but are you filling out more rows than can fit in one default size screen? Normally it should be possible to get a hint at what the error is by checking the messages returned by the BDC call, so I would start by capturing those.
Check your bindings from wf <->Task and then Task <-> Method. You can test your task through SWUS to see where the problem is.....It could be an authorisation issue with WF-BATCH....also, check the wf log to see if there were any errors tRFC, etc.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.