FM ABAP coding error
i created GENERIC datasource and i am trying to fill the values in that datasource using Fm.
Within my FM i want to call FM- CRM_ORDER_READ to get the values.
now when u execute CRM_ORDER_READ, i want the data from segments
ET_ORDERADM_H : GUID
ET_ORDERADM_H : OBJECT ID
& ET_ORDERADM_I : HEADER
ET_ORDERADM_I : ITM_TYPE
now, when HEADER = guid extract ALL ITEM TYPES
extract data for all guids. (guid is something like order number which is key in between different segments.)
my code below gives NO-Error and short dumps at execution in RSA3-
ERROR IS : FM- CRM_ORDER_READ is called with ITM-TYPE. ITM_TYPE is not defined.
can somebody suggest corrections:
CASE I_DSOURCE.
WHEN 'ZCRM_COMP_TEST_D2'.
WHEN OTHERS.
IF 1 = 2. MESSAGE E009(R3). ENDIF.
LOG_WRITE 'E' "message type
'R3' "message class
'009' "message number
I_DSOURCE "message variable 1
' '. "message variable 2
RAISE ERROR_PASSED_TO_MESS_HANDLER.
ENDCASE.
APPEND LINES OF I_T_SELECT TO S_S_IF-T_SELECT.
S_S_IF-REQUNR = I_REQUNR.
S_S_IF-DSOURCE = I_DSOURCE.
S_S_IF-MAXSIZE = I_MAXSIZE.
ELSE. "Initialization mode or data extraction ?
loop at s_s_if-t_select into l_s_select
where fieldnm = 'ITM_TYPE'.
move-corresponding l_s_select to L_R_ITM_TYPE.
append L_R_ITM_TYPE.
endloop.
OPEN CURSOR WITH HOLD S_CURSOR FOR
SELECT * FROM CRMD_ORDERADM_H
WHERE PROCESS_TYPE EQ 'STT1'.
ENDIF. " this endif is for the IF S_COUNTER_DATAPAKID = 0.
" this will ensure the base records are selected from header with a pariticular doc type for the
" for the cursor
FETCH NEXT CURSOR S_CURSOR
APPENDING CORRESPONDING FIELDS
OF TABLE E_T_DATA
PACKAGE SIZE S_S_IF-MAXSIZE.
IF SY-SUBRC EQ 0.
Here select the guid of the header table which can be used in the FM
DATA : LT_HEADER TYPE CRMT_OBJECT_GUID_TAB .
SELECT GUID FROM CRMD_ORDERADM_H
INTO TABLE LT_HEADER
WHERE PROCESS_TYPE EQ 'STT1'.
"CAll the FM here
CALL FUNCTION 'CRM_ORDER_READ'
EXPORTING
IT_HEADER_GUID = LT_HEADER
IMPORTING
ITM_TYPE = CRMD_ORDERADM_I-ITM_TYPE.
" MOdify e_t_data .... transporting your fields from FM
ENDIF .
IF SY-SUBRC <> 0.
CLOSE CURSOR S_CURSOR.
RAISE NO_MORE_DATA.
ENDIF.
S_COUNTER_DATAPAKID = S_COUNTER_DATAPAKID + 1.
ENDIF. "Initialization mode or data extraction ?
ENDIF.
ENDFUNCTION.
any inputs??
so i modified the code , it is bringing values for GUID & Object id (Order Numbers) but the field for ITEM_TYPE is always empty.
what modification needs to be done in code so that it item_type is populated.
(the logic is something like when GUID of et_orderadm_h = Header of et_orderadm_i, bring in all ITEM TYPES)
so data in et_orderadm_h is
GUID--OBJECT ID
111.......101
112.......102
and data in et_orderadm_i is :
GUID--Header guid.........item types
911.......111........................ORD1
912.......111........................ORD2
913.......111........................ORD3
914.......112........................ORD4
915.......112........................ORD5
916.......112........................ORD6..............
IF S_COUNTER_DATAPAKID = 0.
loop at s_s_if-t_select into l_s_select
where fieldnm = 'ITM_TYPE'.
move-corresponding l_s_select to L_R_ITM_TYPE.
append L_R_ITM_TYPE.
endloop.
OPEN CURSOR WITH HOLD S_CURSOR FOR
SELECT * FROM CRMD_ORDERADM_H
WHERE PROCESS_TYPE EQ 'ZSRV'.
FETCH NEXT CURSOR S_CURSOR
APPENDING CORRESPONDING FIELDS
OF TABLE E_T_DATA
PACKAGE SIZE S_S_IF-MAXSIZE.
IF SY-SUBRC EQ 0.
DATA : LT_HEADER TYPE CRMT_OBJECT_GUID_TAB .
SELECT GUID FROM CRMD_ORDERADM_H
INTO TABLE LT_HEADER
WHERE PROCESS_TYPE EQ 'ZSRV'.
"CAll the FM here
CALL FUNCTION 'CRM_ORDER_READ'
EXPORTING
it_header_guid = lt_header_guid
it_requested_objects = lt_request_objs
IMPORTING
et_orderadm_h = lt_orderadm_h
et_orderadm_i = lt_orderadm_i
et_status = lt_status.
ENDIF .
IF SY-SUBRC <> 0.
CLOSE CURSOR S_CURSOR.
RAISE NO_MORE_DATA.
ENDIF.
S_COUNTER_DATAPAKID = S_COUNTER_DATAPAKID + 1.
ENDIF...
any inputs???????
Similar Messages
-
Enhance BW Extractor - Transactional data ABAP CODING ERROR
i need to enhance CRM extractor with additional field.
This is transactional data so i used Exit_rs_001
Here is the extractor result -
Guid...date...........objectid...item guid
1122......1.1.10....901..........8811
1122......2.1.10....901..........8812
1123......1.1.10....902..........8813
1123......2.1.10....902..........8814
now i need field Product id in it which is called from DB Table CRMD_SRV_REFOBJ
itemguid...referencekey...product
8811............01.................110011
8812............02.................110012
8813............03.................110013
now i want to extract data--
Guid...date...........objectid...item guid...product
1122......1.1.10....901..........8811.........110011
1122......2.1.10....901..........8812.........110012
1123......1.1.10....902..........8813.........110013
so i appended the extractor...with field zproduct
FOLLOWING Code doesnot work:::
DATA: L_S_INFOSTRU LIKE ziw_orderma_i.
CASE I_DATASOURCE.
FIELD-SYMBOLS: <PRO_01> TYPE ziw_orderma_i.
CASE i_datasource.
WHEN 'ziw_orderma_i.'. " Upper case
LOOP AT c_t_data ASSIGNING <PRO_01>.
SELECT PRODUCT_ID INTO <PRO_01>-zZPRODUCT
FROM CRMD_SRV_REFOBJ UP TO 1 ROWS
WHERE ITEM_GUID = <PRO_01>-CRMD_SRV_REFOBJ.
ENDSELECT. " not whole primary key
ENDLOOP.
ENDCASE.actually
coding doesnt give any error
but in output in rsa3 i dont see any data
it worked fine wit the same code for master data datasource in exit...2
now same code different parameters doesnt work in exit..1 for transactional data. -
Enhance BW Extractor -abap coding error
hi gurus
i need to enhance extractor 0customer_attr so that field from KNKK-GRUPP is pulled in along with 0customer_attr extraction
so i enhance the extractor using append and type it in the data element, PROVIDED zzxyzno in the field name
Activated it and UNHIDE it.
now my abap code in CMOD in ZXRSAU01 for EXIT RS*01 DOESNT WORK...
now i wrote below code:
DATA: L_S_INFOSTRU LIKE biw_kna1_s.
CASE I_DATASOURCE.
WHEN '0ustomer_attr'.
DATA: biw_kna1_s_data LIKE biw_kna1_s.
LOOP AT C_T_DATA INTO L_S_INFOSTRU.
L_TABIX = SY-TABIX.
biw_kna1_s_data-ZZXYZNO = KNKK-GRUPP
ENDLOOP.
ENDCASE.
but it is still not pulling in values from extractor...
can you please correct my code ???Try something like
FIELD-SYMBOLS: <customer_attr> TYPE biw_kna1_s.
CASE i_datasource.
WHEN '0CUSTOMER_ATTR'. " Upper case
LOOP AT c_t_data ASSIGNING <customer_attr>.
SELECT grupp INTO <customer_attr>-zzxyzno
FROM knkk UP TO 1 ROWS
WHERE kunnr = <customer_attr>-kunnr.
ENDSELECT. " not whole primary key
ENDLOOP.
ENDCASE.
If performance problems arise ("SELECT in a LOOP"), first fill an internal table with a FOR ALL ENTRIES IN c_t_data in a sorted internal table (kunnr and grupp field, key kunnr) , then in the LOOP use a READ TABLE. (mandatory if you use such exits on big extractions.
Regards,
Raymond -
ABAP coding error...enhance transactional datasource
i need to enhance CRM extractor with additional field.
This is transactional data so i used Exit_rs_001
Here is the extractor result -
Guid...date...........objectid...item guid
1122......1.1.10....901..........8811
1122......2.1.10....901..........8812
1123......1.1.10....902..........8813
1123......2.1.10....902..........8814
now i need field Product id in it which is called from DB Table CRMD_SRV_REFOBJ
itemguid...referencekey...product
8811............01.................110011
8812............02.................110012
8813............03.................110013
now i want to extract data--
Guid...date...........objectid...item guid...product
1122......1.1.10....901..........8811.........110011
1122......2.1.10....901..........8812.........110012
1123......1.1.10....902..........8813.........110013
so i appended the extractor...with field zproduct
FOLLOWING Code doesnot work:::
DATA: L_S_INFOSTRU LIKE ziw_orderma_i.
CASE I_DATASOURCE.
FIELD-SYMBOLS: <PRO_01> TYPE ziw_orderma_i.
CASE i_datasource.
WHEN 'ziw_orderma_i.'. " Upper case
LOOP AT c_t_data ASSIGNING <PRO_01>.
SELECT PRODUCT_ID INTO <PRO_01>-zZPRODUCT
FROM CRMD_SRV_REFOBJ UP TO 1 ROWS
WHERE ITEM_GUID = <PRO_01>-CRMD_SRV_REFOBJ.
ENDSELECT. " not whole primary key
ENDLOOP.
ENDCASE.Hi,
For this, you can do as below
REFER EXTRACTOR GUID --1122
Find GUID References for guid = 1122 in table CRMD_ORDERADMI (item level table)
for the guid reference in CRMD_ORDERADMI, find the Product >0 in table CRMD_SRV_REFOBJ
select that Product and write into extractor field zzproduct#
WHEN 'ziw_orderma_i'.
LOOP AT c_t_data INTO l_s_ziw_orderma_i.
l_tabix = sy-tabix.
data: temp_guid like CRMD_ORDERADM-GUID. to create a temporary variable
SELECT single GUID FROM CRMD_ORDERADMI INTO temp_guid
WHERE GUIDREF = l_s_ziw_orderma_i-GUID.
The above statement would give you value for GUID from this table i.e. z1122
SELECT PRODUCT_IT FROM CRMD_SRV_REFOBJ INTO l_s_ziw_orderma_i-ZZPRODUCT
WHERE GUID = temp_guid.
MODIFY c_t_data FROM l_s_ziw_orderma_i INDEX l_tabix.
ENDSELECT.
This would fetch your value
clear temp_guid. to clear this temporary variable
ENDLOOP.
WHEN OTHERS.
EXIT.
ENDCASE.
PS: It appears that you have corrected already so not requried any more
Edited by: Rahul K Rai on Oct 17, 2010 9:27 PM -
ABAP coding issues after BW upgrade
Hello Gurus,
We recently did a BW upgrade from version 3.5 to 7.31 and even since have been encountering few strange issues with many of our ABAP coding.
For example, there is an APPEND statement in one of our Update Rules as below:
APPEND <lw_rtab_wa> TO <lt_rtab>.
Before upgrade, this was working as expected and the contents of <lw_rtab_wa> was getting transferred to <lt_rtab> without any issues.
Now after upgrade, we find that the contents of <lw_rtab_wa> is being clubbed together in the 1st few columns of <lt_rtab>.
Both the <lw_rtab_wa> & <lt_rtab> have the same fields, but the length of few fields in <lt_rtab> is bigger than that in <lw_rtab_wa>. For example DOC_NUMBER in <lw_rtab_wa> is of type C(10) while in <lt_rtab> it is C(20). This difference is causing the data of the 2nd field also to be over-writen in the DOC_NUMBER field of <lt_rtab>.
Please let us know if you have encountered similar situations after your BW upgrade. Any possible solutions to this would be very much appreciated as this is causing PROD issues at the moment!
Thanks
ArvindHi Arvind,
After Upgrade In BW 7.3 or higher versions All data elements that use the domain RSCHAVL are converted from CHAR60 to SSTRING. thats the reason you are getting that syntax error.
Take help of some ABAP programmer and try to change the syntax as suggested from below link.
Just scroll down and check the same. even though link shows for BW 7.4 issues, its applicable for 7.3 too. Please let me know
http://scn.sap.com/community/data-warehousing/bw/blog/2014/07/28/sap-bw-74-analysis-issues
Thanks
Ajay -
Expalin about ABAP Logical errors?
Help me sending appropriate link to understand more.
Moderator Message: Read the Rules of Engagement of this forum.
Edited by: kishan P on Dec 27, 2011 9:50 PMHi Vinay,
You can't delete the ABAP Runtime errors. But you can catch the errors using catch exception Statement.
For Example,
Class-based exceptions are handled in the following control structure:
TRY.
... " TRY block (application coding)
CATCH cx_... cx_... ...
... " CATCH block (exception handler)
CATCH cx_... cx_... ...
... " CATCH block (exception handler)
CLEANUP.
... " CLEANUP block (cleanup context)
ENDTRY.
Try This Sample Code,
*--EXAMPLE FOR RUNTIME ERROR--
*DATA : VALUE1 TYPE I.
*VALUE1 = 1 / 0. -
>>>>>> IT MAKES RUN TIME ERROR.
*WRITE : VALUE1.
*-EXAMPLE FOR HOW TO CATCH THE ARITHMETIC ERROR AT THE RUN TIME USING SUBRC----
DATA : VALUE1 TYPE I.
CATCH SYSTEM-EXCEPTIONS ARITHMETIC_ERRORS = 1.
VALUE1 = 1 / 0.
WRITE : VALUE1.
ENDCATCH.
IF SY-SUBRC = 1.
WRITE : ' IT MAKES ERROR'.
ELSE.
WRITE : VALUE1.
ENDIF.
Thanks,
Reward If Helpful. -
ABAP Runtime Error CONVT_NO_NUMBER
Dear all,
I am calling transaction F-02 for posting G/L Account from an FM. I tried with the Header Data and Account and Cost Centre but it says ABAP Runtime Error CONVT_NO_NUMBER. I undersood that its because of the Number interpretation and coded accordingly but still it throws the same error.
Can you please help me in this....
With Regards
JayDear all,
Thanks for giving me some hope. I tried the possiblities but still it says the same error. I have pasted the FM in nutshell. Can you please see that and help me.
FUNCTION ZUPLOAD_XLS.
""Local interface:
*" IMPORTING
*" REFERENCE(P_BUKRS) LIKE BKPF-BUKRS
*" REFERENCE(P_BLDAT) LIKE BKPF-BLDAT
*" REFERENCE(P_BUDAT) LIKE BKPF-BUDAT
*" REFERENCE(P_MONAT) LIKE BKPF-MONAT
*" REFERENCE(P_WAERS) LIKE BKPF-WAERS
*" REFERENCE(P_BKTXT) LIKE BKPF-BKTXT
*" TABLES
*" IN_JE_XLS STRUCTURE ZFGI_JE_STR
ITAB-BSCHL = 40.
ITAB-SAKNR = '812070'.
ITAB-WRBTR = '30881.00'.
ITAB-KOSTL = '11620009'.
APPEND ITAB.
MOVE P_BUDAT(4) TO TEM+4(4).
MOVE P_BUDAT+4(2) TO TEM(2).
MOVE P_BUDAT6(2) TO TEM2(2).
MOVE P_BUDAT(4) TO TEM+4(4).
MOVE P_BUDAT+4(2) TO TEM(2).
MOVE P_BUDAT6(2) TO TEM2(2).
MOVE P_BLDAT(4) TO TEM1+4(4).
MOVE P_BLDAT+4(2) TO TEM1(2).
MOVE P_BLDAT6(2) TO TEM12(2).
MOVE P_BLDAT(4) TO TEM1+4(4).
MOVE P_BLDAT+4(2) TO TEM1(2).
MOVE P_BLDAT6(2) TO TEM12(2).
WRITE ITAB-WRBTR TO WRBTR.
CONDENSE WRBTR NO-GAPS.
WRITE ITAB-BSCHL TO T_BSCHL NO-GROUPING LEFT-JUSTIFIED.
IF ITAB-KOSTL+8(2) EQ SPACE.
MOVE ITAB-KOSTL TO HOLD_KOSTL+2(8).
MOVE '00' TO HOLD_KOSTL(2).
ELSE.
MOVE ITAB-KOSTL TO HOLD_KOSTL.
ENDIF.
FIELD_LENGTH = STRLEN( ITAB-SAKNR ).
IF FIELD_LENGTH EQ 10.
MOVE ITAB-SAKNR TO HOLD_SAKNR.
ELSE.
MOVE ITAB-SAKNR(6) TO HOLD_SAKNR+4(6).
MOVE '0000' TO HOLD_SAKNR(4).
ENDIF.
PERFORM NEW_DYNPRO USING 'SAPMF05A' '0100'.
PERFORM NEW_FIELD USING 'BKPF-BUDAT' TEM.
PERFORM NEW_FIELD USING 'BKPF-BLDAT' TEM1.
PERFORM NEW_FIELD USING 'BKPF-MONAT' P_MONAT.
PERFORM NEW_FIELD USING 'BKPF-WAERS' 'USD'.
PERFORM NEW_FIELD USING 'BKPF-BUKRS' P_BUKRS.
PERFORM NEW_FIELD USING 'BKPF-BKTXT' P_BKTXT.
PERFORM NEW_FIELD USING 'RF05A-NEWBS' T_BSCHL.
PERFORM NEW_FIELD USING 'RF05A-NEWKO' HOLD_SAKNR.
PERFORM NEW_FIELD USING 'BDC_OKCODE' '/11'.
PERFORM NEW_DYNPRO USING 'SAPMF05A' '0300'.
PERFORM NEW_FIELD USING 'BSEG-WRBTR' WRBTR.
PERFORM NEW_FIELD USING 'RF05A-NEWKO' ' '.
PERFORM NEW_FIELD USING 'RF05A-NEWBS' ' '.
PERFORM NEW_FIELD USING 'BDC_OKCODE' '/11'.
PERFORM NEW_DYNPRO USING 'SAPLKACB' '0002'.
PERFORM NEW_FIELD USING 'COBL-KOSTL' HOLD_KOSTL.
CALL TRANSACTION 'F-02' USING BDCDATA MODE 'A' UPDATE 'S'. -
ABAP Runtime Error CONV_NO_NUMBER
Dear all,
I am calling transaction F-02 for posting G/L Account from an FM. I tried with the Header Data and Account and Cost Centre but it says ABAP Runtime Error CONV_NO_NUMBER. I undersood that its because of the Number interpretation and coded accordingly but still it throws the same error.
Can you please help me in this....
With Regards
JayHi Sharma
the dump occured CX_SY_CONVERSION_NO_NUMBER
while executing the transaction some of the procedures may not raise and this dump throws, make a note of the actions in st22 and intimate to the ABAP team.
Follow the link
http://www.bwexpertonline.com/downloads/source_code.doc
Regards
Bhaskar
Edited by: bhaskar1818 on Jun 20, 2008 5:25 PM -
What is difference among F5 and F6 and F7 in ABAP coding?
what is difference among F5 and F6 and F7 in ABAP coding ? Can u give me any example regarding this thread ?
Some additional info which can be quite helpful.
a watchpoint is an indicator in a program that tells the ABAP runtime processor to interrupt the program at a particular point. Unlike breakpoints, however, watchpoints are not activated until the contents of a specified field change. Watchpoints, like dynamic breakpoints, are user-specific, and so do not affect other users running the same program. You can only define watchpoints in the Debugger.
Use
You set watchpoints in the Debugger to monitor the contents of specific fields. They inform you when the value of a field changes. When the value changes, the Debugger interrupts the program.
Features
· You can set up to five watchpoints in a program.
See also Setting Watchpoints.
· You can also specify the conditions under which a watchpoint is to become active.
· You can specify a logical link for up to five (conditional) watchpoints.
See also Specifying Logical Links.
· You can define watchpoints as either local or global. If you define a global watchpoint, it is active in all called programs. Local watchpoints are only active in
the specified program.
· You can change and delete watchpoints.
See Changing Watchpoints
· You can use watchpoints to display changes to the references of strings, data and object references, and internal tables.
See Memory Monitoring with Watchpoints
Breakpoints
Apart from being able to execute an ABAP program in the Debugger, you can also start the Debugger call by the choosing a breakpoint. This is achieved by setting one or more of these breakpoints in the program. A breakpoint is a signal at a particular point in the program that tells the ABAP runtime processor to interrupt processing and start the Debugger. The Debugger is activated when the program reaches this point.
There is also a special kind of breakpoint called a watchpoint. When you use watchpoints, the Debugger is not activated until the contents of a particular field change. For more information, refer to the chapter Watchpoints.
Breakpoint Variants
The Debugger contains different breakpoint variants:
Static
A user-specific breakpoint is inserted in the source code as an ABAP statement using the keyword BREAK-POINT. A non user-specific breakpoint is set in the ABAP Editor using the BREAK user name statement.
Directly set
dynamic breakpoints
Can be set in the ABAP Editor or the Debugger by double-clicking a line, for example. Dynamic breakpoints are always user-specific, and are deleted when you log off from the R/3 System.
Breakpoints
at statements
The Debugger stops the program immediately before the specified statement is executed.
Breakpoints
at subroutines
The Debugger stops the program immediately before the specified subroutine is called.
Breakpoints at function modules
The Debugger stops the program immediately before the specified function module is called.
Breakpoints at methods
The Debugger stops the program immediately before the specified method is called.
Breakpoints at exceptions and system exceptions
The Debugger stops the program immediately after a system exception, that is, after a runtime error has been intercepted.
Static Breakpoints
Static breakpoints are always user-independent if there is no specification of a user name. Once a user has inserted the statement BREAK-POINT or BREAK name in an ABAP program, the system always interrupts the program at that point for that user or only for the user name. This procedure is only useful in the development phase of an application when program execution is always to be interrupted at the same place. For more information, refer to the chapter Static Breakpoints.
In HTTP sessions, a static breakpoint is skipped if you did not set additional dynamic HTTP breakpoints in the editor of a BSP page. Instead, a corresponding system log entry is written, which can be checked using transaction SM21.
Dynamic Breakpoints
Dynamic breakpoints are user-specific. Therefore, you should use them if you only want the program to be interrupted when you run it yourself, not when it is being executed by other users. All dynamic breakpoints are deleted when you log off from the R/3 System.
Dynamic breakpoints are more flexible than static breakpoints because you can deactivate or delete them at runtime. They have the following advantages:
· You do not have to change the program code.
· You can set them even when the program is locked by another programmer.
· You can define a counter that only activates the breakpoint after it has been reached.
Special dynamic breakpoints are useful when you want to interrupt a program directly before a particular ABAP statement, a subroutine, or an event, but do not know exactly where to find it in the source code. Event here is used to refer to the occurrence of a particular statement, for example, or calling up a method. Special dynamic breakpoints are user-specific. You can only set them in the Debugger. For more information, refer to the chapter Dynamic Breakpoints.
In HTTP sessions, the system stops both at static and dynamic breakpoints if a dynamic breakpoint was set in the editor of a BSP page before program execution.
Lifetime and Transfer of Breakpoints
A static breakpoint remains intact as long as the BREAK-POINT or BREAK-POINT name statement is not removed from the source code. Without saving, dynamic breakpoints only remain intact in the relevant internal session. However, they remain in effect during the entire user session if they are saved by choosing the menu path Breakpoints ® Save in the ABAP Debugger. For more details on the subject of user sessions and modes, refer to Modularization Techniques in the ABAP keyword documentation.
If you call an HTTP session during a user session, only the HTTP breakpoints are loaded when the HTTP session is started. You activate HTTP debugging in the ABAP Editor by choosing Utilities ® Settings ® HTTP Debugging. Depending on the setting, the system then displays either the HTTP or standard breakpoints in the Editor.
If you call an update session during a user session, breakpoints that were defined beforehand in the calling processing unit are copied to the new update session, where they can be displayed under Breakpoints. If, in the ABAP Debugger, you check Update Debugging under Settings and then, for example, call the update module func using CALL FUNCTION func IN UPDATE TASK, a new window is opened in which you can debug this function module in the update session. All the breakpoints that were set in the calling processing unit can also be processed here.
we can keep them at :
Statements
Subroutines
Function Module Calls
at Methods
System Exceptions
break point :
we can start debugging from that point or if we keep break point at some place we can directly got ot htat point using f6.
watch point: for example if we have to check the output for 4000 records based on a field value i.e.for vendor number 'in'we have to check then we will create watchpoint on field LIFNR value '2000'. then we can directly go to vendor whose numbe ris 2000 -
ASN Error on Save / publish -"Posting Illegal Statement" ABAP Runtime error
Hi All,
I am working on the ASN Scenario in SNC 7.0. Whenever I create an ASN in the SNC web UI and Save or/and Publish it, the following actions occur:
1. I get the message "ASN got saved / published successfully" in the SNC Web UI
2. Everytime I do this, a ABAP runtime error gets logged in the system. The Runtime Error is "Posting_Illegal_Statement" (seen under ST22)
3. I do not see any XML messages in SXI_Monitor.
4. I do not see any log entries in SLG1
Can anyone explain how to debug this error and what may be the possible causes for this error?
Also can anyone explain how to send the XML messages manually using the report "/N/SCA/DLV_PUBLISH". Whats the config / action needed to trigger the XML and send it to PI?
Thanks,
BharathHallo,
I have had the same problem. The ASN coding crashed and I could not reprocess the ASN posting within the PPF.
The ABAP /SCA/DLV_PUBLISH checks, wether the ASN is meant to be sent by the PPF. Just overwrite the check within the debugger and the ASN will be posted via a XML message.
Set gs_dlv-send_mode to 'D' within the debugger.
In ABAP
Publish ASN
PERFORM publish_asn.
Form publish_asn
IF gs_dlv-send_mode <> /scmb/cl_c_order=>gc_publ_method_direct. -
>> Set Mode in debugger
MESSAGE ID '/SCA/DM'
TYPE 'I'
NUMBER '136'
WITH lv_asn_number.
gv_error = 'X'.
RETURN.
ELSE.
Regards
Martin
Edited by: Martin Renardy on Oct 20, 2011 1:32 PM
Edited by: Martin Renardy on Oct 20, 2011 1:42 PM
Edited by: Martin Renardy on Oct 20, 2011 1:43 PM -
What is LUW? How do we use it in SAP ABAP coding?
Hi Friends,
Kindly explain me what is LUW with examples and how do we use it in our ABAP coding with scenarios why and when we use it?
Regards,
PradeepHi,
SAP LUW
Die Verbuchungsverwaltung
The Open SQL statements INSERT, UPDATE, MODIFY, and DELETE allow you to program database changes that extend over several dialog steps. Even if you have not explicitly programmed a database commit, the implicit database commit that occurs after a screen has been processed concludes the database LUW. The following diagram shows the individual database LUWs in a typical screen sequence:
Under this procedure, you cannot roll back the database changes from previous dialog steps. It is therefore only suitable for programs in which there is no logical relationship between the individual dialog steps.
However, the database changes in individual dialog steps normally depend on those in other dialog steps, and must therefore all be executed or rolled back together. These dependent database changes form logical units, and can be grouped into a single database LUW using the bundling techniques listed below.
A logical unit consisting of dialog steps, whose changes are written to the database in a single database LUW is called an SAP LUW. Unlike a database LUW, an SAP LUW can span several dialog steps, and be executed using a series of different work processes. If an SAP LUW contains database changes, you should either write all of them or none at all to the database. To ensure that this happens, you must include a database commit when your transaction has ended successfully, and a database rollback in case the program detects an error. However, since database changes from a database LUW cannot be reversed in a subsequent database LUW, you must make all of the database changes for the SAP LUW in a single database LUW. To maintain data integrity, you must bundle all of you database changes in the final database LUW of the SAP LUW. The following diagram illustrates this principle:
Database Logical Unit of Work (LUW)
From the point of view of database programming, a database LUW is an inseparable sequence of database operations that ends with a database commit. The database LUW is either fully executed by the database system or not at all. Once a database LUW has been successfully executed, the database will be in a consistent state. If an error occurs within a database LUW, all of the database changes since the beginning of the database LUW are reversed. This leaves the database in the state it was in before the transaction started.
The database changes that occur within a database LUW are not actually written to the database until after the database commit. Until this happens, you can use a database rollback to reverse the changes. In the R/3 System, database commits and rollbacks can be triggered either implicitly or using explicit commands.
Implicit Database Commits in the R/3 System
A work process can only execute a single database LUW. The consequence of this is that a work process must always end a database LUW when it finishes its work for a user or an external call. Work processes trigger an implicit database commit in the following situations:
When a dialog step is completed
Control changes from the work process back to the SAP GUI.
When a function module is called in another work process (RFC).
Control passes to the other work process.
When the called function module (RFC) in the other work process ends.
Control returns to the calling work process.
When a WAIT statement interrupts the work process.
Control passes to another work process.
Error dialogs (information, warning, or error messages) in dialog steps.
Control passes from the work process to the SAP GUI.
Explicit Database Commits in the R/3 System
There are two ways to trigger an explicit database commit in your application programs:
Call the function module DB_COMMIT
The sole task of this function module is to start a database commit.
Use the ABAP statement COMMIT WORK
This statement starts a database commit, but also performs other tasks (refer to the keyword documentation for COMMIT WORK).
Implicit Database Rollbacks in the R/3 System
The following cases lead to an implicit database rollback:
Runtime error in an application program
This occurs whenever an application program has to terminate because of an unforeseen situation (for example, trying to divide by zero).
Termination message
Termination messages are generated using the ABAP statement MESSAGE with the message type A or X. In certain cases (updates), they are also generated with message types I, W, and E. These messages end the current application program.
Explicit Database Rollbacks in the R/3 System
You can trigger a database rollback explicitly using the ABAP statement ROLLBACK WORK. This statement starts a database rollback, but also performs other tasks (refer to the keyword documentation for COMMIT WORK).
From the above, we can draw up the following list of points at which database LUWs begin and end.
A Database LUW Begins
Each time a dialog step starts (when the dialog step is sent to the work process).
Whenever the previous database LUW ends in a database commit.
Whenever the previous database LUW ends in a database rollback.
A Database LUW Ends
Each time a database commit occurs. This writes all of the changes to the database.
Each time a database rollback occurs. This reverses all of the changes made during the LUW.
Database LUWs and Database Locks
As well as the database changes made within it, a database LUW also consists of database locks. The database system uses locks to ensure that two or more users cannot change the same data simultaneously, since this could lead to inconsistent data being written to the database. A database lock can only be active for the duration of a database LUW. They are automatically released when the database LUW ends. In order to program SAP LUWs, we need a lock mechanism within the R/3 System that allows us to create locks with a longer lifetime (refer to The R/3 Locking Concept).
The bundling technique for database changes within an SAP LUW ensures that you can still reverse them. It also means that you can distribute a transaction across more than one work process, and even across more than one R/3 System. The possibilities for bundling database changes within an SAP LUW are listed below:
The simplest form of bundling would be to process a whole application within a single dialog step. Here, the system checks the users input and updates the database without a database commit occurring within the dialog step itself. Of course, this is not suitable for complex business processes. Instead, the R/3 Basis system contains the following bundling techniques.
Bundling using Function Modules for Updates
If you call a function module using the CALL FUNCTION... IN UPDATE TASK statement, the function module is flagged for execution using a special update work process. This means that you can write the Open SQL statements for the database changes in the function module instead of in your program, and call the function module at the point in the program where you would otherwise have included the statements. When you call a function module using the IN UPDATE TASK addition, it and its interface parameters are stored as a log entry in a special database table called VBLOG.
The function module is executed using an update work process when the program reaches the COMMIT WORK statement. After the COMMIT WORK statement, the dialog work process is free to receive further user input. The dialog part of the transaction finishes with the COMMIT WORK statement. The update part of the SAP LUW then begins, and this is the responsibility of the update work process. The SAP LUW is complete once the update process has committed or rolled back all of the database changes.
For further information about how to create function modules for use in update, refer to Creating Function Modules for Database Updates
During the update, errors only occur in exceptional cases, since the system checks for all logical errors, such as incorrect entries, in the dialog phase of the SAP LUW. If a logical error occurs, the program can terminate the update using the ROLLBACK WORK statement. Then, the function modules are not called, and the log entry is deleted from table VBLOG. Errors during the update itself are usually technical, for example, memory shortage. If a technical error occurs, the update work process triggers a database rollback, and places the log entry back into VBLOG. It then sends a mail to the user whose dialog originally generated the VBLOG entry with details of the termination. These errors must be corrected by the system administrator. After this, the returned VBLOG entries can be processed again.
For further information about update administration, see Update Administration
This technique of bundling database changes in the last database LUW of the SAP LUW allows you to update the database asynchronously, reducing the response times in the dialog work process. You can, for example, decouple the update entirely from the dialog work process and use a central update work process on a remote database server.
Bundling Using Subroutines
The statement PERFORM ON COMMIT calls a subroutine in the dialog work process. However, it is not executed until the system reaches the next COMMIT WORK statement. Here, as well, the ABAP statement COMMIT WORK defines the end of the SAP LUW, since all statements in a subroutine called with PERFORM ON COMMIT that make database changes are executed in the database LUW of the corresponding dialog step.
The advantage of this bundling technique against CALL FUNCTION... IN UPDATE TASK is better performance, since the update data does not have to be written into an extra table. The disadvantage, however, is that you cannot pass parameters in a PERFORM... ON COMMIT statement. Data is passed using global variables and ABAP memory. There is a considerable danger of data inconsistency when you use this method to pass data.
Bundling Using Function Modules in Other R/3 Systems
Function modules that you call using CALL FUNCTION... IN BACKGROUND TASK DESTINATION... are registered for background execution in another R/3 System when the program reaches the next COMMIT WORK statement (using Remote Function Call). After the COMMIT WORK, the dialog process does not wait for these function modules to be executed (asynchronous update). All of the function modules that you register in this way are executed together in a single database LUW. These updates are useful, for example, when you need to maintain identical data in more than one database.
For further details, refer to the keyword documentation.
For more details of RFC processing, refer to the Remote Communications section of the Basis Services documentation.
Pls. reward if useful.... -
ABAP Runtime Error while executing planning folder
Hi experts.
We have a situation where I can access our planning folders but that's not the case for one of our user. She encountered with an ABAP Runtime Error as follow:
Appreciate if anyone can help me out with this.
Runtime Error RAISE_EXCEPTION
Date and Time 20.04.2007 16:50:23
ShrtText
Exception condition "X_MESSAGE" raised.
What happened?
The current ABAP/4 program encountered an unexpected
situation.
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
is especially useful if you want to keep a particular message.
Error analysis
A RAISE statement in the program "SAPLRSSBR" raised the exception
condition "X_MESSAGE".
Since the exception was not intercepted by a superior program
in the hierarchy, processing was terminated.
Short description of exception condition:
Cancel
For detailed documentation of the exception condition, use
Transaction SE37 (Function Library). You can take the called
function module from the display of active calls.
How to correct the error
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"RAISE_EXCEPTION" C
"SAPLRSSBR" or "LRSSBRU03"
"RSSB_AUTHORITY_IOBJVL_CHECK"
or
"SAPLRSSBR" "X_MESSAGE"
or
"UPB_PM_CUST_START " "X_MESSAGE"
If you cannot solve the problem yourself and you wish to send
an error message to SAP, include the following documents:
1. A printout of the problem description (short dump)
To obtain this, select in the current display "System->List->
Save->Local File (unconverted)".
2. A suitable printout of the system log
To obtain this, call the system log through transaction SM21.
Limit the time interval to 10 minutes before and 5 minutes
after the short dump. In the display, then select the function
"System->List->Save->Local File (unconverted)".
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, select the Editor function "Further Utilities->
Upload/Download->Download".
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
System environment
SAP Release.............. "640"
Application server....... "S53KJ165"
Network address.......... "10.1.53.165"
Operating system......... "AIX"
Release.................. "5.3"
Hardware type............ "00C3A11F4C00"
Character length......... 8 Bits
Pointer length........... 64 Bits
Work process number...... 3
Short dump setting....... "full"
Database server.......... "S53KJ170"
Database type............ "ORACLE"
Database name............ "BWP"
Database owner........... "SAPBWP"
Character set............ "en_US.ISO8859-1"
SAP kernel............... "640"
Created on............... "Oct 29 2006 20:42:11"
Created in............... "AIX 1 5 00538A4A4C00"
Database version......... "OCI_920 "
Patch level.............. "155"
Patch text............... " "
Supported environment....
Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE
10.2.0.."
SAP database version..... "640"
Operating system......... "AIX 1 5, AIX 2 5, AIX 3 5"
Memory usage.............
Roll..................... 16128
EM....................... 16759712
Heap..................... 0
Page..................... 57344
MM Used.................. 10079624
MM Free.................. 2487240
SAP Release.............. "640"
User and Transaction
Client.............. 350
User................ "S51643"
Language key........ "E"
Transaction......... "UPSPL "
Program............. "SAPLRSSBR"
Screen.............. "SAPLUPB_PM_ALV 1000"
Screen line......... 2
Information on where terminated
The termination occurred in the ABAP program "SAPLRSSBR" in
"RSSB_AUTHORITY_IOBJVL_CHECK".
The main program was "UPB_PM_CUST_START ".
The termination occurred in line 416 of the source code of the (Include)
program "LRSSBRU03"
of the source code of program "LRSSBRU03" (when calling the editor 4160).
Source Code Extract
Line
SourceCde
386
l_s_range-low = l_activity.
387
APPEND l_s_range TO l_sx_auth_check_detail-range.
388
INSERT l_sx_auth_check_detail INTO TABLE <l_sx_auth_check>-auth_check_detail.
389
390
CALL FUNCTION 'RSSB_AUTHORITY_IOBJVL_REDUCED'
391
EXPORTING
392
i_infocube = g_sx_iobjvl_check-infocube
393
i_uname = l_uname
394
i_th_hierarchy = g_sx_iobjvl_check-hierarchy
395
i_message = i_message
396
i_activity_force_check = i_activity_force_check
397
CHANGING
398
c_tsx_auth_check_detail = <l_sx_auth_check>-auth_check_detail
399
c_tx_no_auth = l_tx_no_auth
400
c_ts_auth_tlevel = e_ts_auth_tlevel
401
EXCEPTIONS
402
user_not_authorized = 1
403
auth_check_failure = 2
404
auth_check_error = 3
405
inherited_error = 4
406
x_message = 5.
407
IF sy-subrc = 0.
408
REFRESH l_tx_no_auth.
409
CR 20050826 HW873685 SP29 Part 2/3 begin
410
SY-SUBRC = 2 means Auth-Obj missing in users profiles, we need this later
411
ELSEIF sy-subrc = 2.
412
ao_missing = rs_c_true.
413
e_subrc = 2.
414
CR 20050826 HW873685 SP29 Part 2/3 end
415
ELSEIF sy-subrc = 5.
>>>>>
RAISE x_message.
417
ELSE.
418
e_subrc = 2.
419
ENDIF.
420
421
correct the kid now
422
LOOP AT l_tx_no_auth INTO l_sx_no_auth.
423
l_sx_no_auth-kid = <l_sx_auth_check>-kid.
424
APPEND l_sx_no_auth TO e_tx_no_auth.
425
ENDLOOP.
426
427
ENDLOOP.
428
429
End LOOP: Check all SUBNR (FEMS)
430
431
432
CR 20050826 HW873685 SP29 Part 3/3 begin
433
If an Auth-Obj. is missing, no SUBNR can be authorized. Due to OLAP-logic
434
this means empty no_auth table
435
IF ao_missing = rs_c_true.
Contents of system fields
Name
Val.
SY-SUBRC
5
SY-INDEX
1
SY-TABIX
0
SY-DBCNT
0
SY-FDPOS
1
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
210
SY-UCOMM
SELECT
SY-TITLE
Execute All Cost Element
SY-MSGTY
E
SY-MSGID
R7
SY-MSGNO
057
SY-MSGV1
0CO_AREA
SY-MSGV2
A
SY-MSGV3
SY-MSGV4
Active Calls/Events
No. Ty. Program Include Line
Name
40 FUNCTION SAPLRSSBR LRSSBRU03 416
RSSB_AUTHORITY_IOBJVL_CHECK
39 FORM SAPLRSDRC LRSDRCF15 113
AUTHORITY_CHECK
38 FORM SAPLRSDRC LRSDRCF27 57
BASIC_QUERY_DATA_GET_ROLAP
37 FUNCTION SAPLRSDRC LRSDRCU05 44
RSDRC_BASIC_QUERY_DATA_GET
36 FUNCTION SAPLRSDRC LRSDRCU15 189
RSDRC_BASIC_CUBE_DATA_GET
35 FORM SAPLRSDRC LRSDRCF25 373
DATA_GET
34 FUNCTION SAPLRSDRC LRSDRCU02 249
RSDRC_CUBE_DATA_GET
33 FUNCTION SAPLRSDRI LRSDRIU01 352
RSDRI_INFOPROV_READ
32 FORM /1SEM/UPCBW_350TMWPA01 UPC_BWINTERFC__FIX 174
DATA_READ
31 FUNCTION SAPLUPCBW LUPCBWU06 56
UPC_BW_DATA_READ
30 FUNCTION SAPLUPC1 LUPC1U06 67
UPC_DATA_READ
29 METHOD /1SEM/CL_DATA_350TMWPA01======CP UPC_DATA_READ_DB 25
/1SEM/CL_DATA_350TMWPA01=>IF_SEM_DATA_INTERNAL~READ_DB
28 METHOD /1SEM/CL_BUFFER_350TMWPA01====CP UPC_BUFFER_GET 167
/1SEM/CL_BUFFER_350TMWPA01=>IF_SEM_BUFFER~GET
27 METHOD /1SEM/CL_BUFFER_350TMWPA01====CP UPC_BUFFER_READ 5
/1SEM/CL_BUFFER_350TMWPA01=>IF_SEM_BUFFER~READ
26 METHOD /1SEM/CL_DATA_350TMWPA01======CP UPC_DATA_READ 46
/1SEM/CL_DATA_350TMWPA01=>IF_SEM_DATA~READ
25 FORM 45AJEHYBGH37F61DTX80Q9ZFP UPP_PLAN 395
READ_TRANSACTION_DATA
24 FORM 45AJEHYBGH37F61DTX80Q9ZFP UPP_PLAN 561
GET_DATA
23 FORM 45AJEHYBGH37F61DTX80Q9ZFP UPP_PLAN 800
EC500_SELECT_DATABASE
22 FORM SAPLUPP_PP_KERNEL LUPP_PP_KERNELF97 575
SELECT_DATABASE
21 FORM SAPLUPP_PP_KERNEL LUPP_PP_KERNELF97 464
SELECT_AND_FIND_HEADER_COMBI
20 FORM SAPLUPP_PP_KERNEL LUPP_PP_KERNELF97 217
LOGICAL_SCREEN_FILL_HEADER
19 FORM SAPLUPP_PP_KERNEL LUPP_PP_KERNELF97 60
LOGICAL_SCREEN_FILL
18 FUNCTION SAPLUPP_PP_KERNEL LUPP_PP_KERNELU01 114
UPP_PP_KERNEL_CONSTRUCTOR
17 METHOD CL_UPB_PL_ALV=================CP CL_UPB_PL_ALV=================CM01E 176
CL_UPB_PL_ALV=>CONSTRUCTOR
16 FORM SAPLUPB_PM_ALV LUPB_PM_ALVF01 623
OUTPUT_CREATE
15 FORM SAPLUPB_PM_ALV LUPB_PM_ALVF01 202
OUTPUT_INIT
14 FORM SAPLUPB_PM_ALV LUPB_PM_ALVF01 1062
OUTPUT_PROCESS
13 FORM SAPLUPB_PM_ALV LUPB_PM_ALVF01 1225
OUTPUT_SWITCH_TO_LAYOUT
12 FORM SAPLUPB_PM_ALV LUPB_PM_ALVF05 748
INIT_CONTROLS
11 MODULE (PBO) SAPLUPB_PM_ALV LUPB_PM_ALVO01 13
STATUS
10 FUNCTION SAPLUPB_PM_ALV LUPB_PM_ALVU01 24
UPB_PM_ALV_START
9 METHOD CL_UPB_PM_APPLC===============CP CL_UPB_PM_APPLC===============CM00A 88
CL_UPB_PM_APPLC=>EXECUTE_PM
8 METHOD CL_UPB_PM_ADMIN===============CP CL_UPB_PM_ADMIN===============CM00L 76
CL_UPB_PM_ADMIN=>PAI_ONE_NODE
7 METHOD CL_UPB_PM_ADMIN===============CP CL_UPB_PM_ADMIN===============CM00L 23
CL_UPB_PM_ADMIN=>PAI_ONE_NODE
6 METHOD CL_UPB_PM_ADMIN===============CP CL_UPB_PM_ADMIN===============CM003 121
CL_UPB_PM_ADMIN=>PAI
5 FORM SAPLUPB_PM LUPB_PMF04 80
USER_COMMAND_0210
4 MODULE (PAI) SAPLUPB_PM LUPB_PMI04 11
USER_COMMAND_0210
3 FUNCTION SAPLUPB_PM LUPB_PMU22 86
UPB_PM_MAIN
2 FORM UPB_PM_CUST_START UPB_PM_START_ADMIN 251
PM_START
1 EVENT UPB_PM_CUST_START UPB_PM_START_ADMIN 14
START-OF-SELECTION
Chosen variables
Name
Val.
No. 40 Ty. FUNCTION
Name RSSB_AUTHORITY_IOBJVL_CHECK
I_ACTIVITY
03
33
03
I_ACTIVITY_FORCE_CHECK
2
0
I_MESSAGE
X
5
8
I_SX_IOBJVL_CHECK
ZCTMWMA05 ####
5454544332222222222222222222222222222222222222222222222222222222222222222222222222222222220000
A34D7D1050000000000000000000000000000000000000000000000000000000000000000000000000000000000000
I_UNAME
S51643
533333222222
351643000000
E_SUBRC
0
0000
0000
E_TS_AUTH_TLEVEL
Table[initial]
E_TX_NO_AUTH
Table[initial]
RSSB_C_AUTH_KEYFIGURE
1KYFNM
3454442222
1B96ED0000
SY-REPID
SAPLRSSBR
5454555452222222222222222222222222222222
310C233220000000000000000000000000000000
SYST-REPID
SAPLRSSBR
5454555452222222222222222222222222222222
310C233220000000000000000000000000000000
%_SPACE
2
0
RS_C_RANGE_SIGN
IE
44
95
SY-SUBRC
5
0000
0005
L_TX_NO_AUTH
Table[initial]
SY-XFORM
CONVERSION_EXIT
444545544454545222222222222222
3FE65239FEF5894000000000000000
SYST
0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1. ###################################################à##############
0000000000000000000000000002000000000000000000000000000000000000000000000000000E00000000000000
0001000000000000000000000000000000000000000000010001000000010000000000000000000000000000000000
L_SX_NO_AUTH
############ÿÿÿÿ
000000000000FFFF
000000000000FFFF
L_SX_NO_AUTH-KID
Table[initial]
<L_SX_AUTH_CHECK>-KID
Table IT_33029[1x4]
FUNCTION-POOL=RSSBRDATA=G_SX_IOBJVL_CHECK-AUTH_CHECK[1]-KID
Table reference: 2052
TABH+ 0(20) = 07000000908D2FD0000000000000000000000000
TABH+ 20(20) = 00000804000081050000000100000004FFFFFFFF
TABH+ 40(16) = 040002F1000003480001432821000000
store = 0x07000000908D2FD0
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 2052 (0x00000804)
label = 33029 (0x00008105)
fill = 1 (0x00000001)
leng = 4 (0x00000004)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000003
occu = 1 (0x00000001)
access = 2 (ItAccessSorted)
idxKind = 0 (ItIndexNone)
uniKind = 1 (ItUnique)
keyKind = 2 (table_line)
cmpMode = 5 (cmpSingle)
occu0 = 0
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 1
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x07000000908E0CC8
pghook = 0x0000000000000000
idxPtr = 0x0000000000000000
refCount = 1 (0x00000001)
tstRefCount = 0 (0x00000000)
lineAdmin = 1 (0x00000001)
lineAlloc = 1 (0x00000001)
store_id = 6998 (0x00001B56)
shmIsReadOnly = 0 (0x00000000)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
hsdir = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
No. 39 Ty. FORM
Name AUTHORITY_CHECK
I_TH_SFC
Table IT_32090[14x128]
FUNCTION=RSDRC_BASIC_CUBE_DATA_GETDATA=L_TH_SFC
Table reference: 1757
TABH+ 0(20) = 070000009052D8F8070000009081372800000000
TABH+ 20(20) = 000006DD00007D5A0000000E00000080FFFFFFFF
TABH+ 40(16) = 040002DB000017C80010839401000000
store = 0x070000009052D8F8
ext1 = 0x0700000090813728
shmId = 0 (0x00000000)
id = 1757 (0x000006DD)
label = 32090 (0x00007D5A)
fill = 14 (0x0000000E)
leng = 128 (0x00000080)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000099
occu = 16 (0x00000010)
access = 4 (ItAccessHashed)
idxKind = 0 (ItIndexNone)
uniKind = 1 (ItUnique)
keyKind = 3 (user defined)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x0700000090811F18
pghook = 0x0000000000000000
idxPtr = 0x070000009052D950
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 16 (0x00000010)
lineAlloc = 16 (0x00000010)
store_id = 6872 (0x00001AD8)
shmIsReadOnly = 0 (0x00000000)
>>>>> 1st level extension part <<<<<
regHook = 0x0700000090813588
hsdir = 0x0000000000000000
ext2 = 0x0000000000000000
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
CL_RSO_REPOSITORY=>P_C_BAL_LOG_SUBOBJEC_INST
SY-REPID
SAPLRSDRC
5454554542222222222222222222222222222222
310C234230000000000000000000000000000000
L_S_RANGE-LOW
1ROWCOUNT
354544545222222222222222222222222222222222222222222222222222
12F73F5E4000000000000000000000000000000000000000000000000000
<L_S_SFK>-KYFNM
1ROWCOUNT
354544545222222222222222222222
12F73F5E4000000000000000000000
RSDRC_C_QUERYMODE-CUMULATIVE
C
4
3
S_S_COB_PRO
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
L_SX_SELDR-RANGE+8(8)
Table IT_32110[2x136]
FUNCTION-POOL=RSDRCFORM=AUTHORITY_CHECKDATA=L_SX_SELDR
Table reference: 1902
TABH+ 0(20) = 0700000090813D10000000000000000000000000
TABH+ 20(20) = 0000076E00007D6E0000000200000088FFFFFFFF
TABH+ 40(16) = 040002DB00001AA00010254421000000
store = 0x0700000090813D10
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 1902 (0x0000076E)
label = 32110 (0x00007D6E)
fill = 2 (0x00000002)
leng = 136 (0x00000088)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000112
occu = 16 (0x00000010)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 2 (table_line)
cmpMode = 8 (cmpManyEq)
occu0 = 1
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 1
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x07000000908800F8
pghook = 0x0000000000000000
idxPtr = 0x0000000000000000
refCount = 1 (0x00000001)
tstRefCount = 0 (0x00000000)
lineAdmin = 16 (0x00000010)
lineAlloc = 16 (0x00000010)
store_id = 6876 (0x00001ADC)
shmIsReadOnly = 0 (0x00000000)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
hsdir = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
L_S_RANGE
IEQ1ROWCOUNT
4453545445452222222222222222222222222222222222222222222222222222222222222222222222222222222222
95112F73F5E40000000000000000000000000000000000000000000000000000000000000000000000000000000000
L_TSX_SELDR
Table IT_32094[13x120]
FUNCTION-POOL=RSDRCFORM=AUTHORITY_CHECKDATA=L_TSX_SELDR
Table reference: 1870
TABH+ 0(20) = 0700000090813AE007000000908DF36800000000
TABH+ 20(20) = 0000074E00007D5E0000000D00000078FFFFFFFF
TABH+ 40(16) = 040002DB000018A8000C4B9C01000000
store = 0x0700000090813AE0
ext1 = 0x07000000908DF368
shmId = 0 (0x00000000)
id = 1870 (0x0000074E)
label = 32094 (0x00007D5E)
fill = 13 (0x0000000D)
leng = 120 (0x00000078)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000103
occu = 12 (0x0000000C)
access = 2 (ItAccessSorted)
idxKind = 1 (ItIndexLinear)
uniKind = 1 (ItUnique)
keyKind = 3 (user defined)
cmpMode = 3 (cmpSingleMcmpU)
occu0 = 1
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x070000009087FB40
pghook = 0x0700000090813D68
idxPtr = 0x0700000090813DA0
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 36 (0x00000024)
lineAlloc = 36 (0x00000024)
store_id = 6875 (0x00001ADB)
shmIsReadOnly = 0 (0x00000000)
>>>>> 1st level extension part <<<<<
regHook = 0x07000000908DED00
hsdir = 0x0000000000000000
ext2 = 0x0000000000000000
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
L_SX_SELDR
00001KYFNM ########300 0 ####ÿÿÿÿ#### 0 ######## ####ÿÿ
333334544422222222222222222222222222000000003332223222220000FFFF0000223200000000222222220000FF
00001B96ED00000000000000000000000000000000003000000000000000FFFF0000000000000000000000000000FF
G_RUNNING
0
0000
0000
L_BASICCUBE
ZCTMWMA05
545454433222222222222222222222
A34D7D105000000000000000000000
L_TH_FREE
Table IT_32093[6x30]
FUNCTION-POOL=RSDRCFORM=AUTHORITY_CHECKDATA=L_TH_FREE
Table reference: 1763
TABH+ 0(20) = 0700000090813760000000000000000000000000
TABH+ 20(20) = 000006E300007D5D000000060000001EFFFFFFFF
TABH+ 40(16) = 040002DB00001B800010831401000000
store = 0x0700000090813760
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 1763 (0x000006E3)
label = 32093 (0x00007D5D)
fill = 6 (0x00000006)
leng = 30 (0x0000001E)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000116
occu = 16 (0x00000010)
access = 4 (ItAccessHashed)
idxKind = 0 (ItIndexNone)
uniKind = 1 (ItUnique)
keyKind = 2 (table_line)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x07000000908137B8
pghook = 0x0000000000000000
idxPtr = 0x07000000908139B0
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 16 (0x00000010)
lineAlloc = 16 (0x00000010)
store_id = 6874 (0x00001ADA)
shmIsReadOnly = 0 (0x00000000)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
hsdir = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
SYST-REPID
SAPLRSDRC
5454554542222222222222222222222222222222
310C234230000000000000000000000000000000
L_SX_IOBJVL_CHECK
ZCTMWMA05 ####
5454544332222222222222222222222222222222222222222222222222222222222222222222222222222222220000
A34D7D1050000000000000000000000000000000000000000000000000000000000000000000000000000000000000
L_ACTIVITY
03
33
03
SY-UNAME
S51643
533333222222
351643000000
S_MULTICUBE
222222222222222222222222222222
000000000000000000000000000000
E_SUBRC
0
0000
0000
%_VIASELSCR
0
4
S_CHANM
222222222222222222222222222222
000000000000000000000000000000
I_RAISE_EXCEPTION
X
5
8
RS_C_TRUE
X
5
8
SCREEN
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
No. 38 Ty. FORM
Name BASIC_QUERY_DATA_GET_ROLAP
E_T_DATA
Table[initial]
E_END_OF_DATA
2
0
C_FIRST_CALL
X
5
8
S_S_QPARAM
XX 0 ##ÿÿÿÿ####DB-VIEW R ###dABAP-TABLE
25523200FFFF0000442544522222222222222222222222222222222222222222222222520006444525444422222222
08800000FFFF000042D6957000000000000000000000000000000000000000000000002000041210D412C500000000
C_S_QPARAM-AUTHORITY_CHECK
R
5
2
RSDRC_C_AUTHCHK-NONE
2
0
RSJOBINFO
00000000000000 ####
222222222222222222222222222222223333333333333322222222222222222222222222222222220000
000000000000000000000000000000000000000000000000000000000000000000000000000000000000
RSD_C_DPANM
0REQUID 0CHNGID 0RECORDTP 0IOB
3545544222222222222222222222223444444222222222222222222222223544454552222222222222222222223444
025159400000000000000000000000038E794000000000000000000000000253F244000000000000000000000009F2
SPACE
2
0
I_BASICCUBE
ZCTMWMA05
545454433222222222222222222222
A34D7D105000000000000000000000
I_TH_SFC
Table IT_32090[14x128]
I_TH_SFK
Table IT_32091[2x128]
FUNCTION=RSDRC_BASIC_CUBE_DATA_GETDATA=L_TH_SFK
Table reference: 1767
TABH+ 0(20) = 0700000090887AC00700000090813CD800000000
TABH+ 20(20) = 000006E700007D5B0000000200000080FFFFFFFF
TABH+ 40(16) = 040002DB000018380010839421000000
store = 0x0700000090887AC0
ext1 = 0x0700000090813CD8
shmId = 0 (0x00000000)
id = 1767 (0x000006E7)
label = 32091 (0x00007D5B)
fill = 2 (0x00000002)
leng = 128 (0x00000080)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000101
occu = 16 (0x00000010)
access = 4 (ItAccessHashed)
idxKind = 0 (ItIndexNone)
uniKind = 1 (ItUnique)
keyKind = 3 (user defined)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 1
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x0700000090884C90
pghook = 0x0000000000000000
idxPtr = 0x0700000090827A98
refCount = 1 (0x00000001)
tstRefCount = 0 (0x00000000)
lineAdmin = 16 (0x00000010)
lineAlloc = 16 (0x00000010)
store_id = 6857 (0x00001AC9)
shmIsReadOnly = 0 (0x00000000)
>>>>> 1st level extension part <<<<<
regHook = 0x0700000090813B38
hsdir = 0x0000000000000000Have you check or trace Authorization??
In DUMP:
Information on where terminated
The termination occurred in the ABAP program "SAPLRSSBR" in
"RSSB_AUTHORITY_IOBJVL_CHECK".
The main program was "UPB_PM_CUST_START ". -
ABAP Runtime error while activating Update rules.
Hi Gurus,
Actually we are in NW 2004's SP9.
While activating the update rules of cube "0PY_PPC01" it is going to ABAP runtime error. It is giving the key words like "MESSAGE_TYPE_X"
"%_T005K2" or "INSTANTIATE". And i apply NOTEs also i am unable to fix it.
Can any one give correct NOTE number that can fix it or any suggestions.
Thanks in advance.
Thanks
Raju.kHi Sven,
Now we are also in SP11, But the thing is all the other UR are working fine Except
this UR. Even there is no perticular NOTE number for this.
Thanks
Raju.k -
ABAP Runtime error in FM BBP_VENDOR_GET_DATA2 in R/3
Hi Gurus
We are receiving nearly 1000 ABAP runtime error in the Functional Module BBP_VENDOR_GET_DATA2 in the user ID as RFCPROD in the ST22 and in the dump details as soon below.
Possible error causes:
o The maximum size of an SQL statement was exceeded.
o The statement contains too many input variables.
o The input data requires more space than is available.
And this is happening in this place.
48| IF NOT LRT_ADDRNR[] IS INITIAL. |
|>>>>>| SELECT * APPENDING TABLE ITAB_ADRC FROM ADRC .
We enter the T-code XK01, XK02 and XK03 , then enter the details of vendor , press enter immediately one count is increasing in the ST22.
Please any one can suggest .
Thanks & Regards
SadaHi Sadasivam Soliyappan,
Could you please share the SAP Note number with us urgently?
We have been encountered with the same problem unfortunately.
Thanks in advance.
Dolunay. -
Dear All,
We are setting up Solman 7.1 sp08 for VAR scenario.
As we faced some issues with duplicated ibase components SAP suggested us to implement note 2012029.
After following step by step and running the reporrts mentioned in above note like report AI_CRM_PRODUCT_DELETE we started getting an abap runtime error.
SAP is telling us to re implement the note but it does not resolve our issue.
Now we are unable to create incidents, or to run trx ib_gen.
Because of this, job refresh_admin_data_from_support is getting cancelled.
find attached screenshot showing dump.
all suggestions or comments are welcome!
regards,
GermanHi German,
Looks like your report CL_AI_CRM_OBJECT_LMDB============CP is corrupted. Can you try restoring this program to original version by going to Version management in SE38?
Regards,
Vivek
Maybe you are looking for
-
Premiere elements 12 organizer blocked by revel screen
I just installed Premiere Elements 12. When I open the organizer, immediately a screen promoting Revel comes up, blocks organizer and there is no way I can find to close it. Can anyone help? Thanks engelsda
-
Getting my itunes library to my iphone
just need to know if i am syncing right? i want to sync my itunes library to my iphone, it says if i sync it will remove and replace everything on the phone with the music library, is it just talking about the music? its not going to erase my whole
-
User Exit for Amount Rounding in FI Postings
Hi, Can any body tell the name of User Exit / BADI for FI postings, which helps me to round off the amounts while i post the transactions. Eg. If a enter an amount of 10,000.65 then while saving the document, it should roundoff the amount to 10,001.
-
Crystal Reports 10 Error "Unknown Query Engine Error"
Hi guys, after creating reports with crystal reports 2008 fails,because there's no 64-bit runtime version i try to develope my reports now with Crystal Reports 10 (ships with Visual Studio 2008). I've minimized the complexity to a minimum - a simple
-
How to roatate .out fies for weblogic in windows
Hi , I am getting large amount of .out files in my manage servers.now i am able to raotating .log files.IN the way how can i roatate .out files in windows. Regards Mad