‎2009 Jan 21 5:22 PM
Hi all,
My requirement is to create a ZFunction Module that Generated a sales order
for multiple line items and works for both Variant Configurable material and a Normal Material.
I am using BAPI_SLSTRANSACT_CREATEMULTI in my Zfunction Module to create a
Sales order
My ZFunction Module works well if I give normal material as input.
It also works well and generates a sales order if I give all Variant Configurable materials as input.
But if I give both Variant Configurable material and a normal material it throws a run time error.
Can some one tell me what is wrong? can some one suggest me how to debug this run time error
Termination occurred in the ABAP program "SAPLCRM_CONFIG_OW" - in
"CONFIG_TO_CBASE".
The main program was "RS_TESTFRAME_CALL ".
In the source code you have the termination point in line 63
of the (Include) program "LCRM_CONFIG_OWF02".
Source Code Extract
Line SourceCde
-
| 33| LT_CUXI_CUPRT
| 34| LT_CUXI_CUVAL
| 35| LT_CUXI_CUVK
| 36| LS_CUXI_CUCFG.
37 |
| 38| PERFORM CREATE_PRICING_CSTIC USING IS_CONFIG-CUCFG-CFGINFO.
39 |
| 40|* set config to cbase
| 41| CALL FUNCTION 'COM_CUXI_SET_SINGLE_CFG'
| 42| EXPORTING
| 43| I_CFG_HEADER = LS_CUXI_CUCFG
| 44| I_ROOT_INSTANCE = CV_INT_OBJ_NO
| 45| I_LOGSYS = LV_LOGSYS
| 46| IMPORTING
| 47| E_ROOT_INSTANCE = CV_INT_OBJ_NO
| 48| TABLES
| 49| I_TAB_INSTANCES = LT_CUXI_CUINS
| 50| I_TAB_PART_OF = LT_CUXI_CUPRT
| 51| I_TAB_VALUES = LT_CUXI_CUVAL
| 52| I_TAB_VAR_KEYS = LT_CUXI_CUVK
| 53| I_TAB_RESTRICTIONS = LT_CUXI_CURES
| 54| EXCEPTIONS
| 55| INVALID_INSTANCE = 1
| 56| INTERNAL_ERROR = 2
57 | OTHERS = 3. 58 |
| 59| IF SY-SUBRC <> 0.
| 60| if sy-msgno is initial.
| 61| MESSAGE X010 WITH 'COM_CUXI_SET_SINGLE_CFG'.
| 62| else.
|>>>>>| MESSAGE ID SY-MSGID TYPE 'X' NUMBER SY-MSGNO
| 64| WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
| 65| endif.
| 66| ENDIF.
67 |
| 68|ENDFORM. " CONFIG_TO_CBASE
-
‎2009 Jan 21 5:27 PM
Click on ABAP Editor where you see the dump and put a break point there. I hope you are checking this in ST22
‎2009 Jan 21 5:43 PM
By the way i forgot to tell you..i am doing this in CRM. this is a Zfunction Module that generates a sales order for VC and normal material in CRM.
Only if i don through my Zprog i get this error. if i create an order on screen i dont get any error
Did u ecnounter this before? how to solve this error?
Edited by: jessica sam on Jan 22, 2009 5:00 PM
‎2009 Jan 22 5:55 PM
I think this error will only come in particular scenarios as Message type is X.
Place a break-point at
CALL FUNCTION 'COM_CUXI_SET_SINGLE_CFG'
and check.
You may check for OSS note for this. As this si compeltely based on scenarios. do cross check witht he different datas to figure out exact error.
‎2009 Jan 22 6:30 PM
Hey Amit...
Can I Create a Sales order for VC and Non VC items using BAPI_SLSTRANSACT_CREATEMULTI
Is it a limitation for BAPI_SLSTRANSACT_CREATEMULTI
I am trying to create a Sales Order using a Zprogram. I have used BAPI_SLSTRANSACT_CREATEMULTI. If I give the input as Normal material I am able to generate a sale order. If I give the input as VC material I am able to generate a sales order. But if I give both VC and Normal material as input, I get a run time error as follows.
Is it a limitation for BAPI_SLSTRANSACT_CREATEMULTI that we cannot create a sales order with both VC and Non-VC items or am I missing some data which I need to pass when I give both VC and Non VC items? I get this error only for my Zprogram. But if I try to create an order on screen manually I donu2019t get any error. This happens only if I create an order with my Zprogram.
Some one please help me u2026I am just stuggling to get this doneu2026
I dint find any posts that gives me information about this error.
CUX1 034 u201CNo root instance found in header datau201D
In the source code you have the termination point in line 63 of the (Include) program "LCRM_CONFIG_OWF02".
‎2009 Jan 22 9:42 PM
I dont have much idea about CRM side....what I replied earlier is based on general debugging techniques..
Check the Documentation of BAPI in your CRM system and test it to know more till you find any suitable reply
‎2009 Jan 23 7:16 PM
‎2009 Jan 22 6:14 PM
Jessica,
After getting short dump, click ABAP EDITOR or some button on upper left hand side.
It will take you to the error location in the debugger screen.
Keep a session break-point before the error location and execute the program again.
This way you will be able to debug.
To keep a session break-point in the debugger screen, all you need to do is keep a break-point and save it.
Mubeen