Skip to Content
author's profile photo Former Member
Former Member

Sales Order BAPI Extension


We would like to pass custom fields data to Custom screens in VA01 Standard Sales Order. For that we are extending standard BAPI BAPI_SALESORDER_CREATEFROMDAT2 using EXTENSION parameter. We have appended custom structures to VBAKKOZ. VBAKKOZX, BAPE_VBAK,BAPE_VBAKX and able to pass information from portal upto 480 characters using

valuepart1 and valuepart2.

But when we are trying to extend it further, standard sales order BAPI


CALL METHOD cl_abap_container_utilities=>fill_container_c


im_value = da_bape_vbap


ex_container =



illegal_parameter_type = 1


We need to extend it up to 900 chars.

Any help on this will be greatly apprecited.



Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on Jul 22, 2008 at 03:07 PM

    We have run into the same problem.

    We applied the following notes to get over the original problem, which was a Unicode conversion error, and then got the same error as you have here.

    1091771 Problems when filling data containers II

    1092829 BAPI terminates w/ runtime error UC_OBJECTS_NOT_CONVERTIBLE

    Since lenstruc is defined as a constant in LVBAKTOP, there is a syntax error.

    Have you found a solution for this yet?

    Are there additional notes?


    Edited by: Brian Sammond on Jul 22, 2008 11:07 AM

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      I found shortly after posting my message that the notes had not been correctly applied as the Notes Assistant ended with an error, and the error that resulted in this failure had not been corrected. The basis folks failed to inform me that this error had occured in applying the notes. I discovered it through testing. Had you applied the notes and run into the same error?

      When we subsequently corrected for this, the issue with lenstruc went away and everything appears to be OK. The real problem was that due to the error in the Notes Assistant the updated version of LVBAKTOP with the definition of lenstruc did not get activated. It was left in a state where it needed an SSCR key to be applied manually, which should all have been handled automatically with SNOTE.

      Once this was done and the source was activated, the original error went away. The two notes seem to have solved the original Unicode issue as well.

      We still have this update in the development area only since the CRM enhancements that caused the original problem with an append to the VBAK structure are also still in development. We will be testing those changes together before moving everything up. If there are any further issues that come up, I'll let you know.

      What I am wondering is if you had a similar problem applying the above notes, since the problem went away for us when the notes to handle the Unicode conversion were properly applied.


      Edited by: Brian Sammond on Jul 24, 2008 10:55 AM

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.