Problem while triggering DTP

When I am triggering the DTP, job is not getting started but it automatically getting cancelled. Any help..

Hi,
There must be some Short Dump, Get into ST22 and analyze your Dump. You may find some inconsistent requests in the system. Locate them and delete them. This should allow you to run DTP smoothly.
Regards,
Suman

Similar Messages

Problem while triggering IDoc

hi,
When i am triggering idoc from R/3 , it is saying idoc transferred to port,
but when i am checking the idoc in XI system idx5 , i am not able to view the idocs,
What could be the reason for this?
Also when i am creating distribution model in BD64 and then saying distribute , it is giving this message:
Model view BANK_CREAT has not been updated
Reason: Maintenance systems for model view BANK_CREAT are not identical
..... Maintenance system in sending system DMYCLNT702
..... Maintenance system in receiving system DMYCLNT100
Note:DMYCLNT702 - Testing client
DMYCLNT100 - Development
Urgent help needed,
Thanks,
Loveena

Hi,
Chk the following details which will be helpful:
A Summary of the Steps to be carried out to enable a SAP R/3 System send Idocs to SAP Exchange Infrastructure.
First - Maintain the Sender R/3 System:
SM59 : Create a RFC destination to XI
WE21 : Create a TRFC Port ->Specify the RFC Destination Created
BD54 : Create a Logical System for the Idoc Receiver
WE20 : Create Partner Profile ->Maintain Outbound and the Inbound Parameters
Second - Log on to XI System:
SM59 : RFC Destination for Sender System
IDX1 : Create the port to get Idoc Metadata from Sender System ( The Port Name must match the port name in the idoc header - Usually in format SAP<System ID>. eg. SAPID1 [Optional Step. Not mandatory]
IDX2 : Maintain the Idoc Metadata. This is needed only by XI, and not by other SAP systems. IDX2 is needed because XI needs to construct IDoc-XML from the IDoc. No other SAP system needs to do that.
Also chk the following link providing details of pushing idocs:
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi

Problem in Triggering the Mail to SAP Inbox

Dear Experts,
                 I have a problem for triggering the Mail option to SAP Inbox.
We created a Job assigning the program RSEIDOCA,RSWUWFML2 by creating a variant for those programs. We are scheduling the job, It is showing as
24.11.2010 12:43:46 Job started                                                                     00           516          S
24.11.2010 12:43:46 Step 001 started (program RSEIDOCA, variant ZRSEIDOCA, user ID__ )        00           550          S
24.11.2010 12:43:48 Error situation found by evaluation                                             E0           596          S
24.11.2010 12:43:48 Step 002 started (program RSWUWFML2, variant ZRSWUWFML2, user ID__)      00           550          S
24.11.2010 12:43:49 Job finished                                                                    00           517          S
But while checking in SOST, we are unable to see those mails. eventhough the user is unable to get those mail in SAP INBOX.
I think, is there any authorization problem while triggering the mail for that particular user id.. Please tell me the solution, this is very high requirement for me.
Thanks in Advance.
Regards,
Srini

Hi Chandra,
          Thanks for your reply. Actually i am not workflow consultant, thats why i asking this question. Where to assign the Receipient Type and Recipient Notification.
you give Recipient Type as position and Recipient of Notification must be position of the reciepient,
Regards,
Srini

Problem while creating data transfer process

Hi friends
I am using BI 7.0 version.
I m getting a problem while creating dtp
After activating DTP and selecting the execute button, I am getting the following error message:
Request cannot be processed in its current state
Messg no : RSBK209
can anyone help me on this problem
Thank

Hi Deepthi,
Also check the error message(long text) and paste it here...
check if you are either creating a "second" Delta DTP ( if an existing Delta DTP exists, then system will not allow you create a second DTP) and will throw an "overlapping" error
Hope this helps
Thanks
Kalyan

Error in workflow while triggering.

hi all .
I am facing a problem while triggering my workflow when i am changing the material no. In the SWEL it is showing only standard buisness object and not my object.
kindly help me in this matter.
thanxs in advance.

it is showing only standard buisness object and not my object
What do you mean by the above statement What is your Object
Check whether you have assigned START EVENTS in the workflow basic data or not
If you declare the start event of the workflow then you can see the Name Of the Receiver
Got to SWDD open your workflow definiton and then press CTRL+ F8 and there you can see a Start Events tab under that tab spcify the BO , BONAME and the EVENT CHANGED

Error DBIF_RSQL_SQL_ERROR and DBIF_REPO_SQL_ERROR while running DTP

Hi to all,
I am loading the data from PSA to DSO, while running DTP, after some records load a run time error coming DBIF_RSQL_SQL_ERROR or DBIF_REPO_SQL_ERROR .
Also i tried the Number of Processes reduce from 3 to 1 in DTP, but still same error .
i have searched the SDN and found that it is due to table space problem.
if it is due to table space , how i will find it and how to correct it.
Please can any one tell we why it is coming and what is the solution for that.
i shall be thankful to you for this.
Regards
Pavneet Rana

Thanks for reply,
i have checked ST22 . and found the error text for 2 runtime error .
first for DBIF_RSQL_SQL_ERROR
second for DBIF_REPO_SQL_ERROR
Runtime Errors DBIF_RSQL_SQL_ERROR
Exception CX_SY_OPEN_SQL_DB
Date and Time 14.03.2011 22:00:21
Short text
 SQL error in the database when accessing a table.
What can you do?
 Note which actions and input led to the error.
 For further help in handling the problem, contact your SAP administrator
 You can use the ABAP dump analysis transaction ST22 to view and manage
 termination messages, in particular for long term reference.
How to correct the error
 Database error text........: "SQL30081N A communication error has been
 detected. Communication protocol being used: "TCP/IP". Communication API being
 used: "SOCKETS". Location where the error was detected: "200.1.1.66".
 Communication function detecting the error: "recv". Protoco"
 Internal call code.........: "[RSQL/FTCH/RSBMONMESS ]"
 Please check the entries in the system log (Transaction SM21).
 If the error occures in a non-modified SAP program, you may be able to
 find an interim solution in an SAP Note.
 If you have access to SAP Notes, carry out a search with the following
 keywords:
 "DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
 "CL_RSBM_LOG_REQUEST_ROOT======CP" or "CL_RSBM_LOG_REQUEST_ROOT======CM00F"
 "GET_STATIC_BUFFER"
 If you cannot solve the problem yourself and want to send an error
 notification to SAP, include the following information:
 1. The description of the current problem (short dump)
 To save the description, choose "System->List->Save->Local File
 (Unconverted)".
 2. Corresponding system log
 Display the system log by calling transaction SM21.
 Restrict the time interval to 10 minutes before and five minutes
 after the short dump. Then choose "System->List->Save->Local File
 (Unconverted)".
 3. If the problem occurs in a problem of your own or a modified SAP
 program: The source code of the program
 In the editor, choose "Utilities->More
 Utilities->Upload/Download->Download".
 4. Details about the conditions under which the error occurred or which
 actions and input led to the error.
 The exception must either be prevented, caught within proedure
 "GET_STATIC_BUFFER" "(METHOD)", or its possible occurrence must be declared in
 the
 RAISING clause of the procedure.
 To prevent the exception, note the following:
Information on where terminated
 Termination occurred in the ABAP program "CL_RSBM_LOG_REQUEST_ROOT======CP" -
 in "GET_STATIC_BUFFER".
 The main program was "RSBATCH_EXECUTE_PROZESS ".
 In the source code you have the termination point in line 29
 of the (Include) program "CL_RSBM_LOG_REQUEST_ROOT======CM00F".
 The program "CL_RSBM_LOG_REQUEST_ROOT======CP" was started as a background job.
 Job Name....... "BIDTPR_2256_1"
 Job Initiator.. " a"
 Job Number..... 18254200
 The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
 procedure "GET_STATIC_BUFFER" "(METHOD)", but it was neither handled locally
 nor declared
 in the RAISING clause of its signature.
 The procedure is in program "CL_RSBM_LOG_REQUEST_ROOT======CP "; its source
 code begins in line
 1 of the (Include program "CL_RSBM_LOG_REQUEST_ROOT======CM00F ".
Source Code Extract
Line SourceCde
 1 method get_static_buffer.
 2 data l_s_storage type rsbm_s_storage.
 3 l_s_storage = get_s_storage( ).
 4 check l_s_storage-type = rsbm_c_storagetype-database..
 5 delete o_th_nodes_static where logid = n_logid.
 6 delete o_t_msg_static where logid = n_logid.
 7 delete o_t_logpar_static where logid = n_logid.
 8 select *
 9 from rsbmnodes connection (l_s_storage-id)
 10 appending corresponding fields of table o_th_nodes_static
 11 where logid = n_logid.
 12
 13 data l_count_monmess type sytabix.
 14 select count( * ) from rsbmonmess
 15 into l_count_monmess
 16 where logid = n_logid.
 17 if l_count_monmess > 50000.
 18 select * from rsbmonmess up to 50000 rows connection (l_s
 19 appending corresponding fields of table o_t_msg_static
 20 where logid = n_logid
 21 and posit < 50
 22 order by node posit.
 23 else.
 24 select * from rsbmonmess connection (l_s_storage-id)
 25 appending corresponding fields of table o_t_msg_static
 26 where logid = n_logid
 27 order by node posit.
 28 endif.
>>>>> select * from rsbmlogpar
 30 appending corresponding fields of table o_t_logpar_static
 31 where logid = n_logid.
 32 field-symbols: <l_s_nodes> type rsbmnodes,
 33 <l_s_log> type s_log.
 34 read table o_th_log assigning <l_s_log>
 35 with table key logid = n_logid.
 36 if sy-subrc <> 0.
 37 break hoeferf. "
 38 endif.
 39 loop at o_th_nodes_static assigning <l_s_nodes>.
 40 if <l_s_nodes>-node > <l_s_log>-maxnode.
 41 <l_s_log>-maxnode = <l_s_nodes>-node.
 42 endif.
43 endloop.
44 * --- set datapackage buffer
45 cl_rsbk_dp_state=>free_buffer( n_requid ).
46 cl_rsbk_dp_state=>fill_buffer( n_requid ).
47 endmethod.
Runtime Errors DBIF_REPO_SQL_ERROR
Date and Time 14.03.2011 15:34:32
Short text
 SQL error "-99999" occurred when accessing program
What can you do?
 Note which actions and input led to the error.
 For further help in handling the problem, contact your SAP administrato
 You can use the ABAP dump analysis transaction ST22 to view and manage
 termination messages, in particular for long term reference.
How to correct the error
 Database error text........: "CLI0108E Communication link failure.
 SQLSTATE=40003"
 Triggering SQL statement...: "CX_SY_NATIVE_SQL_ERROR========CP "
 Internal call code.........: "[REPO/*/43/LOAD/CX_SY_NATIVE_SQL_ERROR===
 Please check the entries in the system log (Transaction SM21).
 If the error occures in a non-modified SAP program, you may be able to
 find an interim solution in an SAP Note.
 If you have access to SAP Notes, carry out a search with the following
 keywords:
 "DBIF_REPO_SQL_ERROR" " "
 "SAPLSYDB" or "LSYDBU27"
 "DB_COMMIT"
 If you cannot solve the problem yourself and want to send an error
 notification to SAP, include the following information:
 1. The description of the current problem (short dump)
 To save the description, choose "System->List->Save->Local File
 (Unconverted)".
 2. Corresponding system log
 Display the system log by calling transaction SM21.
 Restrict the time interval to 10 minutes before and five minutes
 after the short dump. Then choose "System->List->Save->Local File
 (Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
 In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
Information on where terminated
 Termination occurred in the ABAP program "SAPLSYDB" - in "DB_COMMIT".
 The main program was "RSBATCH_EXECUTE_PROZESS ".
 In the source code you have the termination point in line 7
 of the (Include) program "LSYDBU27".
 The program "SAPLSYDB" was started as a background job.
 Job Name....... "BIDTPR_2252_1"
 Job Initiator.. "A"
 Job Number..... 12541100
Source Code Extract
Line SourceCde
 1 FUNCTION DB_COMMIT.
 2 *"----------------------------------------------------------------------
 3 *"*"Lokale Schnittstelle:
 4 *"----------------------------------------------------------------------
 5
 6 EXEC SQL.
>>>>> COMMIT WORK
 8 ENDEXEC.
 9
 10 ENDFUNCTION
please can any one tell me cause for runtime error.
i shall be thankful to you for this.
regards
pavneet rana
Edited by: pavneet rana on Mar 15, 2011 1:29 PM

SHORT DUMP WHILE EXECUTING DTP.

Hi Gurus,
I have got a short dump while executing DTP the Error is as Follows.
Runtime Error: MESSAGE_TYPE_X.
Reasons for Error: 1.The installation of the SAP GUI on the present server is faulty or obselete
2.There is a error in the application program
And i have sent the sreen shot of the Short Dump to BASIS TEAM and they have replied me that they have to install some patches and it will take some time.
But i have no much time and i have to someway or the other execute the DTP and load the data.
Is there any shortcuts for this i mean to say without the involvement of Basis team that i can do in th BI System
Regards
Amar.

Hi Amar,
If the problem is with with System itself, how can we all have a short cut in that case. You may give it another trial, but you have to wait for the patches to be applied. Ask your basis team to get it done ASAP.
Thanks..
Shambhu

Error while executing DTP

Hi gurus,
Iam trying to extract the data from r/3 using generic extractor the data is loaded into PSA sucessfully, but iam getting following errors while executing DTP.
1.An error occurred while executing a transformation rule:
The exact error message is:
The argument 'EA' cannot be interpreted as a number
The error was triggered at the following point in the program
GP4D35STLXQI3SHIVNQC2FSJ7MB 791
2.The data record was filtered out because data records with the same key
have already been filtered out in the current step for other reasons and
the current update is non-commutative (for example, MOVE). This means
that data records cannot be exchanged on the basis of the semantic key.
Please guide me accordingly.
Regards
Amar.

Hi
While mapping the Qty Fields it is must to add UOM to the Qty Fields and map it with relevant Info Objects.
The Semantic Keys defined at DTP are also has some issues, try to give a dummy key figure if you are using DSO in the data flow as the DSO has the Overwrite mode.
(Choose Semantic Groups to specify how you want to build the data packages that are read from the source (DataSource or InfoProvider). To do this, define key fields. Data records that have the same key are combined in a single data package. This setting is only relevant for DataStore objects with data fields that are overwritten. This setting also defines the key fields for the error stack. By defining the key for the error stack, you ensure that the data can be updated in the target in the correct order once the incorrect data records have been corrected.)
Hope it helps and clear

Error while creating DTP from DS to Infoobject

Dear All,
I am getting one error while creating DTP from Datasource to Info object can any one give some suggetion regarding this issue.
Issue:Enter a valid value
Msg No:00002
Procedure: Display the allowed values withF4 and correct your entry,
Regards,
Satya

Hi Satya,
Trying logging off the system and log in again and try to activate Data source Infoobject and transformation again and try creating DTP by selecting Selecting the source system by pressing F4. I hope it should work.
I don't find any specific problem or any patch problem with the error you are getting.
Hope it helps !
Regards,
Rose.

I face a problem while making a confirmation on portal.

Hello ,
Can anyone help me I am facing a problem while making confirmation in the portal.
the system pops up an error as mentioned below. Please help
 Folgender Fehlertext wurde im System SRP prozessiert: Speicherungsform der Produkt-ID ist im Customizing noch nicht definiert
 Der Fehler trat auf dem Applikationsserver eccprd-srp_SRP_50 und im Workprozess 3 auf.
 Die Abbruchart war: TH_RES_FREE
 Die ABAP-Aufrufhierarchie war:
Form: READ_SETTINGS of program SAPLCOM_PR_CONVERSION
Function: CONVERSION_EXIT_PRID1_INPUT of program SAPLCOM_PR_CONVERSION
Function: BBP_PDH_PRODUCT_READ_BUFFER of program SAPLBBP_PDH
Form: GET_LOCAL_PRODUCT of program SAPLBBP_ECI
Form: APPLY_OLD_MAPPING of program SAPLBBP_ECI
Function: BBP_PRODUCT_MAP of program SAPLBBP_ECI
Function: B31I_PO_GETDETAIL of program SAPLBBP_BD_DRIVER_31I
Function: META_PO_GETDETAIL of program SAPLBBP_BD_META_BAPIS
Function: BBP_BE_PO_GETHISTORY of program SAPLBBP_PDH_HISTORY
Function: BBP_PDH_SEARCH_PO_SUBLIST of program SAPLBBP_PDH_SEARCH
Best Regards,
Sairam

Hi,
Pls see if the foll notes are useful.
Note 911217 - Copy vendor product number from contract search help to PO
1047769 - No returns for search by Product ID in Monitor Shopping Cart
Note 1023012 - BBPSC: Long product ID triggers short dump
BR,
Disha.
Pls reward points for useful answers.

Getting error while running dtp

Hi
i am getting this error while running dtp, i am uisng BI 7.0 write optimized DSO
Duplicate data record detected (DS GMND0002 , data package: 000001 , data record: 4 )
ple let me know ur solutions for this problem,

Hi,
You are bound to get this error as write optimized behave in this pattern.
open the write opt DSO and in the settings you can see a check box for 'Do not check uniquness of data'
Check it if you want to use the duplicate records. But there will be two records (duplicate) uniquely identified by the technical key.
Now if you want to use delta concept in this then in DTP use delta by request.
If you further want to use delta then refer to this thread..
[write oprimized dso(URGENT);
Regards,
Priti

Process chain failing while executing DTP

Hi All,
My process chain is failing while executing DTP.
Error i got is: OBJECTS_OBJREF_NOT_ASSIGNED
Access not possible using 'NULL' object reference.
The dump is occuring in method : GET_FIELD_LIST_INBOUND
TRY.
      CALL METHOD cl_rstran_model=>factory
        EXPORTING
          i_tranid = i_tranid
        RECEIVING
          r_r_model = l_r_model.
    CATCH cx_rstran_exception.
      RAISE EXCEPTION TYPE cx_rs_step_failed
ENDTRY.
From SDN , i am quite sure that its a SAP problem and needs to apply some Note.
Could anyone please tell me, which note i should apply ?
Thanks.

Hi,
check the note note 1081884 it may help you ..
check link ..
/message/2817339#2817339 [original link is broken]
Reagrds,
Shikha
Edited by: Shikha Goel on Oct 10, 2008 6:21 AM

Dump while Executing DTP

Hi All,
In process chain, While executing DTP( from PSA to ZINFOOBJECT-Master data), I am getting the following ABAP Dump:
Runtime Errors TSV_TNEW_PAGE_ALLOC_FAILED
The internal table "???" could not be further extended. To enable
error handling, the table had to be delete before this log was written.
As a result, the table is displayed further down or, if you branch to
the ABAP Debugger, with 0 rows.
At the time of the termination, the following data was determined for
the relevant internal table:
Memory location: "Session memory"
Row width: 5356
Number of rows: 0
Allocated rows: 138348
Newly requested rows: 2 (in 69173 blocks)
How to correct the error
 The amount of storage space (in bytes) filled at termination time was:
 Roll area...................... 416432
 Extended memory (EM)........... 2002720576
 Assigned memory (HEAP)......... 1999932640
 Short area..................... " "
 Paging area.................... 24576
 Maximum address space.......... 4294967295
 If the error occures in a non-modified SAP program, you may be able to
 find an interim solution in an SAP Note.
 If you have access to SAP Notes, carry out a search with the following
 keywords:
 "TSV_TNEW_PAGE_ALLOC_FAILED" " "
 "SAPLRSSTATMAN" or "LRSSTATMANU12"
 "RSSTATMAN_UPDATE_DATASTATE_EXT"
Could any one suggest solution
Thanks and Regards,
Umakanth Jaldu

Hi Ramanm
Please suggest how to do repair custom info object in RSRV and the info object is loading from two different dtps and both dtps are failing because of same error.The process of DTP is showing but not moving to next process type.
Dump:
Runtime Errors TSV_TNEW_PAGE_ALLOC_FAILED
Date and Time 31.03.2015 22:19:53
|Short text |
| No more storage space available for extending an internal table. |
|What happened? |
| You attempted to extend an internal table, but the required space was |
| not available. |
|What can you do? |
| Note which actions and input led to the error. |
| |
| For further help in handling the problem, contact your SAP administrator |
| . |
| |
| You can use the ABAP dump analysis transaction ST22 to view and manage |
| termination messages, in particular for long term reference. |
| |
| Try to find out (e.g. by targetted data selection) whether the |
| transaction will run with less main memory. |
| |
| If there is a temporary bottleneck, execute the transaction again. |
| - |
| |
| If the error persists, ask your system administrator to check the |
| following profile parameters: |
| |
| o ztta/roll_area (1.000.000 - 15.000.000) |
| Classic roll area per user and internal mode |
| usual amount of roll area per user and internal mode |
| o ztta/roll_extension (10.000.000 - 500.000.000) |
| Amount of memory per user in extended memory (EM) |
| o abap/heap_area_total (100.000.000 - 1.500.000.000) |
| Amount of memory (malloc) for all users of an application |
| server. If several background processes are running on |
| one server, temporary bottlenecks may occur. |
| Of course, the amount of memory (in bytes) must also be |
| available on the machine (main memory or file system swap). |
| Caution: |
| The operating system must be set up so that there is also |
| enough memory for each process. Usually, the maximum address |
| space is too small. |
| Ask your hardware manufacturer or your competence center |
| about this. |
| In this case, consult your hardware vendor |
| abap/heap_area_dia: (10.000.000 - 1.000.000.000) |
| Restriction of memory allocated to the heap with malloc |
| for each dialog process. |
| Parameters for background processes: |
| abap/heap_area_nondia: (10.000.000 - 1.000.000.000) |
| Restriction of memory allocated to the heap with malloc |
| for each background process. |
| Other memory-relevant parameters are: |
| em/initial_size_MB: (35-1200) |
| Extended memory area from which all users of an |
| application server can satisfy their memory requirement. |
|Error analysis |
| The internal table "???" could not be further extended. To enable |
| error handling, the table had to be delete before this log was written. |
| As a result, the table is displayed further down or, if you branch to |
| the ABAP Debugger, with 0 rows. |
| |
| At the time of the termination, the following data was determined for |
| the relevant internal table: |
| |
| Memory location: "Session memory" |
| Row width: 5356 |
| Number of rows: 0 |
| Allocated rows: 138348 |
| Newly requested rows: 2 (in 69173 blocks) |
|How to correct the error |
| The amount of storage space (in bytes) filled at termination time was: |
| |
| Roll area...................... 416432 |
| Extended memory (EM)........... 2002720576 |
| Assigned memory (HEAP)......... 1999932640 |
| Short area..................... " " |
| Paging area.................... 24576 |
| Maximum address space.......... 4294967295 |
| |
| If the error occures in a non-modified SAP program, you may be able to |
| find an interim solution in an SAP Note. |
| If you have access to SAP Notes, carry out a search with the following |
| keywords: |
| |
| "TSV_TNEW_PAGE_ALLOC_FAILED" " " |
| "SAPLRSSTATMAN" or "LRSSTATMANU12" |
| "RSSTATMAN_UPDATE_DATASTATE_EXT" |
| |
| If you cannot solve the problem yourself and want to send an error |
| notification to SAP, include the following information: |
| |
| 1. The description of the current problem (short dump) |
| |
| To save the description, choose "System->List->Save->Local File |
| (Unconverted)". |
| |
| 2. Corresponding system log |
| |
| Display the system log by calling transaction SM21. |
| Restrict the time interval to 10 minutes before and five minutes |
| after the short dump. Then choose "System->List->Save->Local File |
| (Unconverted)". |
| |
| 3. If the problem occurs in a problem of your own or a modified SAP |
| program: The source code of the program |
| In the editor, choose "Utilities->More |
| Utilities->Upload/Download->Download". |
| |
| 4. Details about the conditions under which the error occurred or which |
| actions and input led to the error. |
| |
|System environment |
| SAP-Release 701 |
| |
| Application server... "sapXXXa1" |
| Network address...... "10.10.29.72" |
| Operating system..... "AIX" |
| Release.............. "7.1" |
| Hardware type........ "00CB77444C00" |
| Character length.... 16 Bits |
| Pointer length....... 64 Bits |
| Work process number.. 4 |
| Shortdump setting.... "full" |
| |
| Database server... "sXXX341.sac.XXX" |
| Database type..... "ORACLE" |
| Database name..... "XXX" |
| Database user ID.. "SAPSR3" |
| |
| Terminal.......... "GSSM0510" |
| |
| Char.set.... "C" |
| |
| SAP kernel....... 720 |
| created (date)... "Feb 10 2014 21:43:58" |
| create on........ "AIX 2 5 00092901D600" |
| Database version. "OCI_102, 11.2.0.2.0, V1, default" |
| |
| Patch level. 525 |
| Patch text.. " " |
| |
| Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*" |
| SAP database version. 720 |
| Operating system..... "AIX 2 5, AIX 3 5, AIX 1 6, AIX 1 7" |
| |
| Memory consumption |
| Roll.... 416432 |
| EM...... 2002720576 |
| Heap.... 1999932640 |
| Page.... 24576 |
| MM Used. 3938002576 |
| MM Free. 59192960 |
|User and Transaction |
| Client.............. 100 |
| User................ "XXXX" |
| Language Key........ "E" |
| Transaction......... " " |
| Transactions ID..... "551B198729F80700E10080000A0A1D12" |
| |
| Program............. "SAPLRSSTATMAN" |
| Screen.............. "SAPLRSBM_REQUEST_GUI 0300" |
| Screen Line......... 5 |
| |
| Information on caller of Remote Function Call (RFC): |
| System.............. "XXX" |
| Database Release.... 701 |
| Kernel Release...... 720 |
| Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.) |
| Call Type........... "synchronous and non-transactional (emode 0, imode 0)" |
| Inbound TID.........." " |
| Inbound Queue Name..." " |
| Outbound TID........." " |
| Outbound Queue Name.." " |
| |
| Client.............. 100 |
| User................ "XXXX" |
| Transaction......... "RSA1" |
| Call Program........."SAPLRSM1" |
| Function Module..... "RSS2_CALL_FCODE_EMPTY_GLOBALS" |
| Call Destination.... "NONE" |
| Source Server....... "sapXXXa1_XXX_12" |
| Source IP Address... "10.10.29.72" |
| |
| Additional information on RFC logon: |
| Trusted Relationship " " |
| Logon Return Code... 0 |
| Trusted Return Code. 0 |
| |
| Note: For releases < 4.0, information on the RFC caller are often |
| only partially available. |
|Information on where terminated |
| Termination occurred in the ABAP program "SAPLRSSTATMAN" - in |
| "RSSTATMAN_UPDATE_DATASTATE_EXT". |
| The main program was "SAPMSSY1 ". |
| |
| In the source code you have the termination point in line 306 |
| of the (Include) program "LRSSTATMANU12". |
|Source Code Extract |
|Line |SourceCde |
| 276| l_s_ext_db-records_techok <> l_s_ext-records_techok. |
| 277| l_s_ext-ts_tech_changed = l_timestamp. |
| 278| l_s_ext-ts_data_changed = l_timestamp. |
| 279| l_changed = 'X'. |
| 280| else. |
| 281| l_s_ext-ts_tech_changed = l_s_ext_db-ts_tech_changed. |
| 282| endif. |
| 283| if l_s_ext-requests_techok = 0. |
| 284| clear l_s_ext-ts_tech_changed. |
| 285| endif. |
| 286| |
| 287| if l_s_ext_db-requests_error <> l_s_ext-requests_error or |
| 288| l_s_ext_db-records_error <> l_s_ext-records_error. |
| 289| l_s_ext-ts_error_changed = l_timestamp. |
| 290| l_s_ext-ts_data_changed = l_timestamp. |
| 291| l_changed = 'X'. |
| 292| else. |
| 293| l_s_ext-ts_error_changed = l_s_ext_db-ts_error_changed. |
| 294| endif. |
| 295| if l_s_ext-requests_error = 0. |
| 296| clear l_s_ext-ts_error_changed. |
| 297| endif. |
| 298| |
| 299| if l_s_ext_db-requests_all <> l_s_ext-requests_all or |
| 300| l_s_ext_db-records_all <> l_s_ext-records_all. |
| 301| l_s_ext-ts_data_changed = l_timestamp. |
| 302| l_changed = 'X'. |
| 303| endif. |
| 304| |
| 305| l_t_part[] = i_t_part[]. |
|>>>>>| sort l_t_part by timestamp_verb descending. |
| 307| read table l_t_part into l_s_part index 1. |
| 308| l_s_ext-ts_last_request = l_s_part-timestamp_verb. |
| 309| l_s_ext-last_request = l_s_part-partnr. |
| 310| if l_s_ext_db-ts_last_request <> l_s_ext-ts_last_request or |
| 311| l_s_ext_db-last_request <> l_s_ext-last_request. |
| 312| l_s_ext-ts_data_changed = l_timestamp. |
| 313| l_changed = 'X'. |
| 314| endif. |
| 315| if l_changed = 'X'. |
| 316| modify rsmdatastate_ext from l_s_ext. |
| 317| endif. |
| 318| endif. |
| 319| |
| 320| if not ( i_dta_type = rsstm_c_types-psa_new or |
| 321| i_dta_type = rsstm_c_types-psa_old ). |
| 322| call function 'RSM_LAST_CHANGE_CHECK_UPDATE' |
| 323| exporting |
| 324| i_dta = i_dta(30) |
| 325| i_tstmp = l_s_ext-ts_data_changed. |
|
|Active Calls/Events |
|No. Ty. Program Include Line |
| Name |
| 16 FUNCTION SAPLRSSTATMAN LRSSTATMANU12 306 |
| RSSTATMAN_UPDATE_DATASTATE_EXT |
| 15 FORM SAPLRSM1 LRSM1U23 768 |
| RSM1_UPDATE_RSMDATASTATE |
| 14 FORM SAPLRSM1 LRSM1F08 5520 |
| RSM1_INIT_PARTTAB |
| 13 FORM SAPLRSM1 LRSM1U23 187 |
| RSSM_UPDATE_RSMDATASTATE |
| 12 FUNCTION SAPLRSM1 LRSM1U23 139 |
| RSSM_UPDATE_RSMDATASTATE |
| 11 METHOD CL_RSSM_STATMAN===============CP CL_RSSM_STATMAN===============CM00L 15 |
| CL_RSSM_STATMAN=>IF_RSBK_REQUEST_OBSERVER~AFTER_FINAL_STATE_TRANSITION |
| 10 METHOD CL_RSBK_REQUEST_STATE=========CP CL_RSBK_REQUEST_STATE=========CM01S 13 |
| CL_RSBK_REQUEST_STATE=>AFTER_FINAL_STATE_TRANSITION |
| 9 METHOD CL_RSBK_REQUEST===============CP CL_RSBK_REQUEST===============CM00H 11 |
| CL_RSBK_REQUEST=>IF_RSBK_REQUEST~SET_USTATE_RED |
| 8 FORM SAPLRSBM_REQUEST_GUI LRSBM_REQUEST_GUIF01 26 |
| SET_USTATE_300 |
| 7 MODULE (PAI) SAPLRSBM_REQUEST_GUI LRSBM_REQUEST_GUII01 122 |
| USER_COMMAND_0300 |
| 6 MODULE (PAI) SAPLRSBM_REQUEST_GUI LRSBM_REQUEST_GUII01 70 |
| USER_COMMAND_100 |
| 5 FUNCTION SAPLRSBM_REQUEST_GUI LRSBM_REQUEST_GUIU01 24 |
| RSBM_SHOW_REQUEST |
| 4 FUNCTION SAPLRSS2 LRSS2U26 39 |
| RSS2_CALL_FCODE_EMPTY_GLOBALS |
| 3 FORM SAPLRSS2 LRSS2U26 1 |
| RSS2_CALL_FCODE_EMPTY_GLOBALS |
| 2 FORM SAPMSSY1 SAPMSSY1 85 |
| REMOTE_FUNCTION_CALL |
| 1 MODULE (PBO) SAPMSSY1 SAPMSSY1 30 |
| %_RFC_START |
Please advise me,
Thanks and Regards,
Uma

Dump while Executing DTP - PSA To ODS

While executing DTP, I am getting the following ABAP Dump: "MESSAGE_TYPE_X".
"MESSAGE_TYPE_X" " "
"SAPLRSSTATMAN" or "LRSSTATMA
"RSSTATMAN_GET_PARTTAB_PSA"
I was facing some selection issue in the Info Package (generic Data source), then I have deleted all the entries in the table u201CRSSELDONEu201D against that Data source. After that I was able to load the data from R/3 server to PSA smoothly.
Now I am facing the issue while loading data from PSA to ODS through DTP. I already activated all the objects again (Data Source, ODS, & DTP).
Please guide me.
Thanks in Advance u2026u2026
Kiruthika

I tried with Error DTP, I am getting same Dump. When I click Execute button with debug option directly it's going to Dump.
I am getting the following Error message
Runtime Errors         MESSAGE_TYPE_X
keywords:
"MESSAGE_TYPE_X" " "
"SAPLRSSTATMAN" or "LRSSTATMA
"RSSTATMAN_GET_PARTTAB_PSA"
Information on where terminated
    Termination occurred in the ABAP program "SAPLRSSTATMAN" - in
     "RSSTATMAN_GET_PARTTAB_PSA".
    The main program was "RSAWBN_START ".
    In the source code you have the termination point in line 1165
    of the (Include) program "LRSSTATMANU10".
I have deleted all the entries in the table u201CRSSELDONEu201D against that Data source. After that I was able to load the data from R/3 server to PSA smoothly. As per my understanding table u201CRSSELDONEu201D is used for info package selection.
If there any problem related to this, please guide me.
Regards,
Kiruthika
Edited by: kiruthika marappan on Sep 4, 2009 2:16 PM

Problem while using trigger from line of 6534

I have faced some problems while using triggering with 6534. They are listed below. Please provide solution me.
1. ) i was using pattern input with triggering(buffered) in which i am using the example given in library buffered pattern input-triggered.vi
Now i am using port 0 to take input. From line 0 of port 2 i want to generate a pulse which can trigger the operation & start acquisition. For that i am using write to single line.vi . My DPULL is open so bydefault the line will be at low level & by vi i will make it high which will trigger the operation.
In normal condition if we use write to a single line.vi it will write the given status on that line within a fraction of second and abort execution. But when i am usin
g it for trigger in following manner, it did not work.
First i started the VI buffered pattern input-triggered.vi.I have configured the start trigger with leading edge trigger. I have set the time limit properly.Synchronous operation is set at the front panel of vi.
Now if start the write to a single line.vi to give start trigger, nether it triggered the operation,nor it abort execution of single line write vi.When time out occured in triggered vi, then both vis stopped simultaneously. Why this happened?
2.) Similar problem i faced when i wanted to perform the change detection.vi Port 0 is configured for input.Line 1 to 7 are fixed with some status by connecting them to Vcc or GND. I have connected port 0 line 0 with port 2 line 0. So when i change status of line 0 of port 2 change detection should be occured o port 0. i am changing the status of line 0 of port 2 by write to a single line.vi But here i faced same problem as first that it was not writing to port 0 line 0. And bo
th process stopped when time limit occured in change detection vi.
So what can be the problem? Please help me.

Hi Vishal,
1) You should check to see that when you are writting a static 1 to line 0 you see a pulse high. You should also make sure that you wire this line to the STARTTRIG for group 0.
2) If you solve question 1 you will also have question 2 solved.
It might be helpful to create a program that configures both programs (pattern I/O on port 0 and static I/O on port 2) in the same program and then starts both groups. I would do a little testing to see exactly what signals you do or do not see.
Ron

Problem while triggering DTP

Similar Messages

Maybe you are looking for