Quantcast
Channel: SCN: Message List
Viewing all articles
Browse latest Browse all 9076

Call Transaction Raising CNTL_ERROR confirmaton window YES/NO

$
0
0

Hello,

 

I am getting a dump CL_GUI_CUSTOM_CONTAINER=======CP CNTL_ERROR when I'm using Call Transaction.

 

Scenario:

 

    A request is coming from third party system to SAP ECC (in the form of XML). This will be submitted to SPROXY.

    From this XML file, a field (customer number - for example) is fetched and is fed to the corresponding field in screen ('BDC_CURSOR' 'KNA1-KUNNR').

  

The tcode used in call transaction checks if the customer is available in the database already.

 

                       IF customer exists already,

                          Trigger MESSAGE 'Customer Exists already'.

                                          ------------- "In this condition, call transaction works good and the above MESSAGE is updated in MESSTAB.

                       ELSE.

                          raise confirmation window (asking 'Save customer YESNO).

                                           ------------ The dump occurs here when the the 'confirmation window' has to be handled.

                       ENDIF.

  

     The code for Call Transaction at the above (ELSE condition) part is  :

 

                            'Screen Name'    0100  'X'

                                                                           BDC_OKCODE    =YES.

 

    I am using ---

                                  CALL TRANSACTION 'tcode'

                                                     USING bdcdata

                                                     MODE 'Q'

                                                      UPDATE 'S'

                                                      MESSAGES into messtab.

 

  •       I've checked previous discussions and understood enjoy transactions doesn't fit into CALL TRANSACTION.
  •       But, given that I do not have any FM or a BAPI, I've to get rid of the above mentioned problem with CALL TRANSACTION itself.
  •       I also did not use Session method. I will be using it today. But I don't see how session method can even solve my problem.

 

    FYI, the process is being submitted to a DIA process, which I hope the call transaction is not running in background.

 

May some one please help me out. I am in urgent need of getting rid of the situation as deadline is nearing. I will be submitting the actual code shortly.

 

Regards,

Pradeep.


Viewing all articles
Browse latest Browse all 9076

Trending Articles