ABEND RS_EXCEPTION (000): Part-field access (offset = 45, length = 45) ...

Hi BI Experts,
We are getting error below when run the query in BEx Broadcaster whereas the same query can be run without error in RSRT. One of the object used in the query is 0TCTBISBOBJ (BI Application Obj). When i remove this object from the query, i am able to execute the query in BEx Broadcaster. Please advice.
Error: com.sap.ip.bi.base.application.exceptions.AbortMessageRuntimeException
com.sap.ip.bi.base.exception.BIBaseRuntimeException ERROR
com.sap.ip.bi.base.application.exceptions.AbortMessageRuntimeException
Log ID: 00144F25CCDC303C0000010600005CBD00046ADC8504A84D
Initial cause
ABEND RS_EXCEPTION (000): Part-field access (offset = 45, length = 45) to a data object of the size 60 exceeds valid boundaries.
MSGV1: Part-field access (offset = 45, length = 45) to a
MSGV2: data object of the size 60 exceeds valid
MSGV3: boundaries.
Stack trace: com.sap.ip.bi.base.application.exceptions.AbortMessageRuntimeException: Termination message sent
We have recently upgraded to SAP BI7.0 SP19.
Thanks in advance.
Best Regards,
Pei Fung

Can someone throw some light on this? Thanks.

Similar Messages

Error : ABEND RS_EXCEPTION (000): Invalid column name 'TXTMD'

Dear Team,
Am getting this Dump / Error Msg. when tring to execute the query in BI Java Stack, the same query is executing perfectly in BI ABAP Stack, could some one throw some light to how to fix this, we are in process of Upgradating from BI 3.5 to BI 7.0 EHP1,
all production report of earlier version is being upgraded to BI. 7, currently our Java Stack is on SP 6.
The details of the error Msg:
The initial exception that caused the request to fail was:
Termination message sent
ABEND RS_EXCEPTION (000): [Microsoft][SQL Server Native Client 10.0][SQL Server]Invalid column name 'TXTMD'.
MSGV1: [Microsoft][SQL Server Native Client 10.0][SQL
MSGV2: Server]Invalid column name 'TXTMD'.
pl. revert. Your early responses are highly appreciated..!
Thanks in Advance.

Nasiroddin,
according following post:
Re: 500 Internal Server Error
might be that some of variables linked to characteristics that is contained in free characteristics area is corrupted. Try to remove it.
BR
m./

Re:invalid partial field access: negative offset

Hi,
       iam getting error invalid partial field access: negative offset, what is this mean

negative off set not allowed
Access Using Offset and Length Specifications
Offset and length specifications are generally critical since the length of each character is platform-dependent. As a result, it is initially unclear as to whether the byte unit or the character unit is referred to in mixed structures. This forced us to put in place certain considerable restrictions. However, access using offset or length specifications is still possible to the degree described in the following. The tasks subject to this rule include accessing single fields and structures, passing parameters to subroutines and working with field symbols.
Single field access
Offset- or length-based access is supported for character-type single fields, strings and single fields of types X and XSTRING. For character-type fields and fields of type STRING, offset and length are interpreted on a character-by-character basis. Only for types X and XSTRING, the values for offset and length are interpreted in bytes.
Structure access
Offset- or length-based access to structured fields is a programming technique that should be avoided. This access type results in errors if both character and non-character-type components exist in the area identified by offset and length.
Offset- or length-based access to structures is only permitted in a UP if the structures are flat and the offset/length specification includes only character-type fields from the beginning of the structure. The example below shows a structure with character-type and non-character-type fields. Its definition in the ABAP program and the resulting assignment in the main memory is as follows:
BEGIN OF STRUC,
a(3) TYPE C,   "Length: 3 characters
b(4) TYPE N,   "Length: 4 characters
c     TYPE D,   "Length: 8 characters
d     TYPE T,   "Length: 6 characters
e     TYPE F,   "Length: 8 bytes
f(26) TYPE C,   "Length: 28 characters
g(4) TYPE X,   "Length: 2 bytes
END OF STRUC.
Internally, the fragment view contains four fragments. Offset- or length-based access in this case is only possible in the first fragment. Statements like struc(21) or struc7(14) are accepted by the ABAP interpreter and treated like a single field of type C. By contrast, struc57(2) access is now only allowed in an NUP. If offset-/length-based access to a structure is permitted, both the offset and length specifications are generally interpreted as characters in a UP.
Passing parameters to subroutines
Up to now, parameter passing with PERFORM has allowed you to use cross-field offset and length specifications. In future, this will no longer be allowed in a UP. In a UP, offset and length-based access beyond field boundaries returns a syntax or runtime error. For example, access types c15 or c5(10) would trigger such an error for a ten-digit C field c.
If only an offset but no length is specified for a parameter, the entire length of the field instead of the remaining length was previously used for access. As a result, parameter specifications are cross-field if you use only an offset, and therefore trigger a syntax error in a UP. PERFORM test USING c+5 is consequently not permitted.
In addition, in a UP, you can continue to specify the remaining length starting from the offset off for parameters using the form field+off(*).
Ranges for offset and length access when using field symbols
A UP ensures that offset- or length-based access with ASSIGN is only permitted within a predefined range. Normally, this range corresponds to the field boundaries in case of elementary fields or, in case of flat structures, to the purely character-type starting fragment. Using a special RANGE addition for ASSIGN, you can expand the range beyond these boundaries.
Field symbols are assigned a range allowed for offset/length specifications. If the source of an ASSIGN statement is specified using a field symbol, the target field symbol adopts the range of the source. If not explicitly specified otherwise, the RANGE is determined as follows:
ASSIGN feld TO <f>.
In a UP, the field boundaries of field are assigned to <fs> as the range, where field is no field symbol.
ASSIGN <g> TO <f>.
<fs2> adopts the range of <fs1>.
ASSIGN elfeld+off(len) TO <f>.
In a UP, the field boundaries of the elementary field elfield are assigned to <fs> as the range.
ASSIGN <elfld>+off(len) TO <f>.
<fs> adopts the range of the elementary field <elfield>.
ASSIGN struc+off(len) TO <f>.
ASSIGN <struc>+off(len) TO <f>.
In a UP, the purely character-type starting section of the flat structures struc or <struc> determines the range boundaries.
If the assignment to the field symbol is not possible because the offset or length specification exceeds the range permitted, the field symbol is set to UNASSIGNED in a UP. Other checks such as type or alignment checks return a runtime error in a UP. As a rule, offset and length specifications are counted in characters for data types C, N, D, and T as well as for flat structures, and in bytes in all other cases.
Offset without length specification when using field symbols
Up to now, ASSIGN field+off TO <fs> has shown the special behavior that the field length instead of the remaining length of field was used if only an offset but not length was specified. Since an ASSIGN with a cross-field offset is therefore problematic under Unicode, you must observe the following rules:
As previously, the field length of field is used as the length. Using ASSIGN field+off(*)... you can explicitly specify the remaining length.
ASSIGN <fs1>+off TO <fs2> is only permitted if the runtime type of <fs1> is flat and elementary, that is, C, N, D, T (offset in characters), or X (offset in bytes).
ASSIGN field+off TO <fs2> is generally forbidden from a syntactical point of view since any offset <> 0 would cause the range to be exceeded. Exceptions are cases in which a RANGE addition is used.
These rules enable you also in future to pass a field symbol through an elementary field using ASSIGN <fs>+n TO <fs>, as it is the case in a loop, for example.
Processing Sections of Strings
You can address a section of a string in any statement in which non-numeric elementary ABAP types or structures that do not contain internal tables occur using the following syntax:
<f>[+<o>][(<l>)]
By specifying an offset <o> and a length (<l>) directly after the field name <f>, you can address the part of the field starting at position <o>1 with length <l> as though it were an independent data object. The data type and length of the string section are as follows:
Original field
Section
Data type
Data type
Length
C
C
<l>
D
N
<l>
N
N
<l>
T
N
<l>
X
X
<l>
Structure
C
<l>
If you do not specify the length <l>, you address the section of the field from <o> to the end of the field. If the offset and length combination that you specify leads to an invalid section of the field (for example, exceeding the length of the original field), a syntax or runtime error occurs. You cannot use offset and length to address a literal or a text symbol.
You should take particular care when addressing components of structures. To ensure the correct platform-specific alignment of type I and F components, they may contain filler fields, whose lengths you need to consider when calculating the correct offset. Furthermore, SAP plans to convert the internal representation of character types to UNICODE, in which one character will no longer occupy one byte, but instead two or four. Although offset and length specifications can work for character fields (types C, D, N, and T) or for hexadecimal fields (type X), incompatible changes may occur in structures containing a mixture of numeric, character, and hexadecimal fields. SAP therefore recommends that you do not use offset and length to address components of structures.
In nearly all cases, you must specify offset <o> and length <l> as numeric literals without a preceding sign. You may specify them dynamically in the following cases:
When assigning values using MOVE or the assignment operator
When assigning values with WRITE TO
When assigning field symbols using ASSIGN.
When passing actual parameters to subroutines in the PERFORM statement.
DATA TIME TYPE T VALUE '172545'.
WRITE TIME.
WRITE / TIME+2(2).
CLEAR TIME+2(4).
WRITE / TIME.
The output appears as follows:
172545
25
170000
First, the minutes are selected by specifying an offset in the WRITE statement. Then, the minutes and seconds are set to their initial values by specifying an offset in the clear statement.
Offset and Length Specifications in the MOVE Statement
For the MOVE statement, the syntax for specifying offset and length is as follows:
MOVE <f1>[<o1>][(<l1>)] TO <f2>[<o2>][(<l2>)].
Or, when you use the assignment operator:
<f2>[<o2>][(<l2>)] = <f1>[<o1>][(<l1>)].
The contents of the part of the field <f1> which begins at position <o1>1 and has a length of <l1> are assigned to field <f2>, where they overwrite the section which begins at position <o2>1 and has a length of <l2>.
In the MOVE statement, all offset and length specifications can be variables. This also applies to statements with the assignment operator, as long as these can also be written as MOVE statements. In statements where no field name is specified after the assignment operator, (for example, in Numeric Operations), all offset and length specifications must be unsigned number literals.
SAP recommends that you assign values with offset and length specifications only between non-numeric fields. With numeric fields, the results can be meaningless.
DATA: F1(8) VALUE 'ABCDEFGH',
F2(20) VALUE '12345678901234567890'.
F26(5) = F13(5).
In this example, the assignment operator functions as follows:
DATA: F1(8) VALUE 'ABCDEFGH',
F2(8).
DATA: O TYPE I VALUE 2,
L TYPE I VALUE 4.
MOVE F1 TO F2. WRITE F2.
MOVE F1+O(L) TO F2. WRITE / F2.
MOVE F1 TO F2+O(L). WRITE / F2.
CLEAR F2.
MOVE F1 TO F2+O(L). WRITE / F2.
MOVE F1O(L) TO F2O(L). WRITE / F2.
This produces the following output:
ABCDEFGH
CDEF
CDABCD
ABCD
CDEF
First, the contents of F1 are assigned to F2 without offset specifications. Then, the same happens for F1 with offset and length specification. The next three MOVE statements overwrite the contents of F2 with offset 2. Note that F2 is filled with spaces on the right, in accordance with the conversion rule for source type C.
Offset and Length Specifications in the WRITE TO Statement
For the WRITE TO statement, the syntax for specifying offset and length is as follows:
WRITE <f1>[<o1>][(<l1>)] TO <f2>[<o2>][(<l2>)].
The contents of the part of the field <f1> which begins at position <o1>1 and has a length of <l1> are converted to a character field and assigned to field <f2>, where they overwrite the section which begins at position <o2>1 and has a length of <l2>.
In the WRITE TO statement, the offset and length specifications of the target field can be variables. The offset and length of the target field must be numeric literals without a preceding sign.
DATA: STRING(20),
NUMBER(8) TYPE C VALUE '123456',
OFFSET TYPE I VALUE 8,
LENGTH TYPE I VALUE 12.
WRITE NUMBER(6) TO STRING+OFFSET(LENGTH) LEFT-JUSTIFIED.
WRITE: / STRING.
CLEAR STRING.
WRITE NUMBER(6) TO STRING+OFFSET(LENGTH) CENTERED.
WRITE: / STRING.
CLEAR STRING.
WRITE NUMBER TO STRING+OFFSET(LENGTH) RIGHT-JUSTIFIED.
WRITE: / STRING.
CLEAR STRING.
This produces the following output:
123456
123456
123456
The first six characters of the field NUMBER are written left-justified, centered, and right-justified into the last 12 characters of the field STRING.

ABEND RSBOLAP (000): Program error in class SAPMSSY1 method : UNCAUGHT_EXCE

Hello,
A BI Report contains a field "X" & a field "Y".
Y is a sub part of X. Means on clicking upon X, Y opens.
This report runs on date basis. For each date Y contains Zero value, but in the result Y contains some value greater than zero.
Now when i execute this report in Portal, clicking on X for the dates opens up Y.
But in the result column, Clicking on X giveg the following error:
Root Cause
The initial exception that caused the request to fail was:
Termination message sent
ABEND RSBOLAP (000): Program error in class SAPMSSY1 method : UNCAUGHT_EXCEPTION
MSGV1: SAPMSSY1
MSGV3: UNCAUGHT_EXCEPTION
Pl. note that this report is running fine in BEx analyer & not giving any such error.
Thanks & Regards

In SE 38 run RSPOR_SETUP and see if all the 12 steps are ok, as I see this is a an issue with java server not able to commute with BI., you need to exchange java certificates to BI and vise versa.,(basis can do this step)
Hope this helps.,

ABEND RS_EXCEPTION (105): Error in BW: error creating tmp table

Hello Experts,
We have recently upgraded to EHP1 from BI 7.0. After that I have applied executed the report SAP_DROP_TMPTABLES as per the note 1139396.
When we run reports, we are getting error "ABEND RS_EXCEPTION (105): Error in BW: error creating tmp table
MSGV1: error creating tmp table".
Please let me know if any one faced the same problem.
Thanks,
Venkatesh

Hello Colum,
Thanks for the reply. I have done recommendations the issue resolved.
But few reports giving the below error.
ABEND RSBOLAP (000): Program error in class SAPMSSY1 method :
UNCAUGHT_EXCEPTION
MSGV1: SAPMSSY1
MSGV3: UNCAUGHT_EXCEPTION
Can you please help to resolve the issue?
Thanks,
Venkatesh

Service replication Dump SYSFAIL Invalid subfield access: Offset too large.

Hello,
I am working with SRM 7.0, Backend: SAP ERP 6.0 EHP4
My problem is that I have replicated the SERVICE MASTER from R/3.But in
tcode SMQ1 for Queue: R3AI_SERVICE_MASTER the system shows the following
error message:SYSFAIL Invalid subfield access: Offset too large.
In SRM the Range are SRM external match with R/3 internal.
I have already replicated OK the following:
DNL_CUST_PROD0
DNL_CUST_PROD1
DNL_CUST_SRVMAS
Could anybody please advise, it would be well appreciated.
Kind regards,

Hello,
the problem was the table CRMSUBTAB for the Service line had a field ticked as inactive.

Error:Could not load type from assembly Culture=neutral, PublicKeyToken=null' because it contains an object field at offset 75 that is incorrectly aligned or overlapped by a non-object field.

I got an error while I creating a structure.
[FieldOffset(72)]
[MarshalAs(UnmanagedType.ByValArray,SizeConst= 3)]
public int[] DC;
[FieldOffset(75)]
[MarshalAs(UnmanagedType.ByValArray, SizeConst = 8)]
public float[] WIN;
[FieldOffset(83)]
[MarshalAs(UnmanagedType.ByValArray, SizeConst = 20)]
public byte[] name;
[FieldOffset(103)]
[MarshalAs(UnmanagedType.ByValArray, SizeConst = 3)]
public byte[] SET;
[FieldOffset(106)]
[MarshalAs(UnmanagedType.ByValArray, SizeConst = 50)]
public byte[] ID;
Error as like this-->object field at offset 75 that is incorrectly aligned or overlapped by a non-object field. But here size constant is 3 so I think after 72 offset will be 75..If I change the offset to 76 it will works fine. I think reason is that
size of int is 4. After changing that code will be like this.
[FieldOffset(72)]
[MarshalAs(UnmanagedType.ByValArray,SizeConst= 3)]
public int[] DC;
[FieldOffset(76)]
[MarshalAs(UnmanagedType.ByValArray, SizeConst = 8)]
public float[] WIN;
[FieldOffset(84)]
[MarshalAs(UnmanagedType.ByValArray, SizeConst = 20)]
public byte[] name;
[FieldOffset(104)]
[MarshalAs(UnmanagedType.ByValArray, SizeConst = 3)]
public byte[] SET;
[FieldOffset(107)]
[MarshalAs(UnmanagedType.ByValArray, SizeConst = 50)]
public byte[] ID;
But at that time I got the error as object field at offset 107 that is incorrectly aligned or overlapped by a non-object field..Can anyone tell me what is the main reason behind this..
Thanks..

Hi,
Please firstly take a look at this documentation:
MarshalAsAttribute.SizeConst Field
Indicates the number of elements in the fixed-length array or the number of characters (not bytes) in a string to import
Change your code like this should work:
[FieldOffset(72)]
[MarshalAs(UnmanagedType.ByValArray,SizeConst= 3)]
public int[] DC;
[FieldOffset(84)]//72+4*3
[MarshalAs(UnmanagedType.ByValArray, SizeConst = 8)]
public float[] WIN;
[FieldOffset(116)]//84+4*8
[MarshalAs(UnmanagedType.ByValArray, SizeConst = 20)]
public byte[] name;
[FieldOffset(136)]
[MarshalAs(UnmanagedType.ByValArray, SizeConst = 3)]
public byte[] SET;
[FieldOffset(139)]
[MarshalAs(UnmanagedType.ByValArray, SizeConst = 50)]
public byte[] ID;
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

500 Java bean field access exception

Installed the APSB07-06 Security patch, and now I am getting
a "500 Java bean field access exception" error in CF Admin when
clicking on Settings. I also get "500 Class jrunx/logger/Logger
violates loader constraints" when clicking on "Caching"
This is on a Win2K, IIS5
CFMX 7,0,2,142559
Java 1.4.2_09
I Installed JRE 1.4.2_14 per recommendations from reading
other posts. CF Admin still shows 1.4.2_09.
JRE installed in C:\Program Files\Java\j2re1.4.2_14. If I
point CF to that directory, CF will not start. I even followed the
Technote
http://www.adobe.com/go/2d547983
Anyone actually get this fixed?
Is it possible to remove the APSB07-06 Security patch?

quote:
Originally posted by:
JrLz
I've read that you cannot install only the JRE, but you have
to install JDK (for the --server parameter to work), and after that
you need to change the java.home section in
c:\cfusionmx7\runtime\jvm.config, point it to your new Java sdk dir
I have tried both, JRE and JDK. When I change the java.home
to the new directory, CF fails to start. Can't recall the exact
message as it's been a few weeks. I am almost to the point of
re-installing CF.

ABEND RSBOLAP (000): error in class SAPMSSY1 method - after report move Pro

Hi Guys,
We recently moved a report to production and got the following error (500 Internal Error) when executing from Query designer
ABEND RSBOLAP (000): Program error in class SAPMSSY1 method : UNCAUGHT_EXCEPTION
MSGV1: SAPMSSY1
MSGV3: UNCAUGHT_EXCEPTION
I saw in one of the threads to run the Program RSPOR_SETUP and see if all the 12 steps are ok and they are not but they are not ok in Dev and Qua as well where its running fine. Appreciate if somebody can advise.

Hi,
Check your Query in RSRT properties tab and make necessary settings.
Do OLAP check in RSCRM_BAPI t-code. It will show the inconsistencies in your query.......
Regards,
Suman

Check rel. part field on sales contract

Hi all,
In sales contract screen, on Header -> Sales, we have a field "Check rel. part". Please update that where in SPRO, I can maintain options for this field.
Many Thanks.
Best Regards,
AI.

Hi,
Check rel. part field value is coming from the sales document type.
Goto sales document types (VOV8). Select the contract document type and choose details.
you can find this field check partner authorization field in contract sub heading. Here you can choose relevant one.
Regards,
Chandrasekhar

Memory leak in String(byte[] bytes, int offset, int length)

Has anyone run into memory leak problem using this String(byte[] bytes, int offset, int length) class? I am using it to convert byte array to string, and I am showing memory leak using this class. Any idea what is going on?

Hi,
If you post in Native methods forum I assume you are using this constructor in the native side.
Be aware that getting char * from jstring eats memory that you must free before returning from native with env->ReleaseStringUTFChars().
--Marc (http://jnative.sf.net)

SAP Cloud SDK : How to create the Note Field with Char 1000 length

Hi Experts,
I have a requirement to create Note type fields in the standard business object. and that note field should be 1000 char length.
Also I need to check whether that Note field we can add under the standard report or not with report enhancement?
1) How to make a Note type field using SDK with length 1000 char? Is it possible? If yes How ?
2) If using SDK Note type field possible then how to display that field in report ?
Many Thanks,
Mithun

Hi Frank and Horst,
I have followed the steps you have mentioned in the post.
1) Create Business Object Extension.
2) Add the Custom Field with Type " LANGUAGEINDEPENDENT_EXTENDED_Text".
3) Enhance the Screen and Add into the Header section of the COD_TI screen.
I have successfully entered the unrestricted character into that field.
But I want to add that custom field into the Standard Data Source or Standard Report.
1) Is it possible to add custom field under the Standard Data Source or Report Using SDK?
2) Is it Possible to display the 1000 character length on the Report field?
3) Is it possible to display the created extension field under the report / data source using SDK?
Many Thanks,
Mithun

Field type String (long length more than 1500)

Hi All,
we have requirement like one custom table with field string type(1500 length) should update through the report.
problem is, it is not updating that many characters through the report.
(till 255 chars only updating in the table)
i have to update full string in the custom table.
the code is below, please help me any one come accross the situation.
thanks in advance.
data: lv_test type string,
      lv_test1 type string,
      lv_num type i,
      it_test type table of ZFEILD_TEST,
      wa_test type zfeild_test.
do 10 times.
lv_test = 'thptjpojtgpeojygpeojhpoewjhpojwhjwpohjopsjhoptrjhopjwhopjwpojhpowjhopwjojwpojhpowjhpowjkahglfdglkaglkahklrhlfhslhkalklklhkalhalkhlahlkajljhlajhlajlajlkajlhjaljlajlhjaljhlajhlahpojwpohjwopjhojhwjhojopjwopjhwojhotjhwojwhojwpojhpwojhpowjophjwpojh'
lv_test1 = lv_test.
concatenate lv_test lv_test1 into lv_test1.
clear: lv_test.
enddo.
lv_num = strlen( lv_test1 ).
wa_test-STRIN = lv_test1.
wa_test-znumber = '001'.
append wa_test to it_test.
loop at it_test into wa_test.
write: / wa_TEST-strin.
modify zfeild_test from wa_test.
endloop.

Hi,
I assume you have chunks of the string and you need to concatenate it and put it to the table.
You can try this.
data : begin of w_string occurs 0,
         string type string,
         end of w_string.
data : w_char1(255) type c value 'BLAUGBUSSUSSF',
          w_char2(255) type c value 'GSIUHFSHF',
w_string-string+0(255) = w_char1.
w_string-straing+255(255) = w_char2.
so on....
append w_string.
Regards,
Pramod

Install(byte[] buffer,short offset, byte length)

Anyone could tell me where i can find the defination of data format of 'buffer' in 'install(byte[] buffer,short offset, byte length)', it is standard, right?!

Look in appendix A.2 of the GlobalPlatform Card Specifications 2.1.1 (pages 160,161). The same information is specified for the install() method in the Java Card 2.2 API spec. The format is the same for Java Card 2.1.1 and GlobalPlatform 2.0.1'.
G

Part Appraisers Access

Hi All,
I hav made an Appraisal Template which has 2 Part Appraiser and 1 final Appraiser. Now for the 1st part appraiser i have made all the column entries as mandatory ie required entries but for second i want to make few columns as optinal entry or no entry, but its not happening as the condition applied to 1st part appraiser applies to all part appraisers.
Any idea how to change the Part Appraisers column access fields????
I would really appreciate ur help...
Anupama

Raghu,
There is no standard delivery for PartAppraisers & futherparticipants.But u can tailoring it with ease. Copy the 'app for managers' and pass different params (part_app) in <b>'HRHAP_DOCUMENT_GET_LIST'</b>
call function 'HRHAP_DOCUMENT_GET_LIST'
      exporting
*      sel_filter                  = 'TODO_LIST'
        add_on_application          = 'PA'
        plan_version                = '01'
*     T_TEMPLATES                 =
*     T_TMPL_DETAIL               =
*      t_appraisers                = t_appraisers
*     S_AND_OR                    = "where appraiser OR part
*     T_APPRAISEES                =
        t_part_appraisers         = lt_part_appraisers
Rgds,
Jothi.P

ABEND RS_EXCEPTION (000): Part-field access (offset = 45, length = 45) ...

Similar Messages

Maybe you are looking for