Q

Workflow template -- container element not passed

I have a custom Workflow template in which one of the container elements (defined as structure BAPIADDR1) is being passed between the Workflow template to a standard task.

Nothing happens, the container element is being filled but isn't passed. Is there a size restriction (255 characters) on container elements. I'm on a 4.6c system. I plan on having someone search OSS for any issues that may be related to this.


Something doesn't seem right. While 4.6c does have a limitation of 255 character length, I would not expect the container element to be empty, just truncated.

Are you sure that the container element is marked as IMPORTING? Perhaps its worth while considering a different approach. Rather than passing in the structure, why not pass in the IDOC BOR object instance and have a method retrieve the relevant segment?


This was first published in April 2004

Dig deeper on SAP workflow development

Pro+

Features

Enjoy the benefits of Pro+ membership, learn more and join.

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

0 comments

Oldest 

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

-ADS BY GOOGLE

SearchManufacturingERP

SearchOracle

SearchDataManagement

SearchAWS

SearchBusinessAnalytics

SearchCRM

SearchContentManagement

SearchFinancialApplications

Close