Connector 2.0 Problem - Negative offset

I am using SAP .Net COnnector 2.0. I am trying to send data from VB.Net to a custom BAPI. The BAPI has both structures and tables. If I invoke the BAPI with blank data, it will work. If I invoke with tables only, it will work. However, if I invoke with the structure, I always get "Invalid partial field access: Negative offset".
I have been working at this for weeks. I have no idea what this means. The full error message is ...
SAP.Connector.RfcSystemException: Invalid partial field access: Negative offset at SAP.Connector.ThrowRfcException(...) at SAP.Connector.Rfc.RfcInvoke(...) at SAP.Connector.SAPClient.SAPInvoke(...) at SAP_Test_Connect.SAPProxy1.Zbapi_Complaint_Createcomplain(...)
The "SAP_Test_Connect" is just my program and "Zbapi_Complaint_Createcomplain" is the custom BAPI.
Please help. Thank you.

David , were you able to resolve this problem?. Could you post the solution, thanks in advance.
I see a core dump on the backend. The coments :
The current ABAP program SAPLRSDN_CUBE had to be terminated.
import parameters I_DIMENSION in RSD_CUBE_GET_FROM_DIME appears to be negative value.
Please help

Similar Messages

Payroll Error msg "The gross wages do not cover the negative offset that has been forwarded, therefore, no grossup is permitted".

Hi Experts,
I am getting the below error msg while running payroll for an US employee.
"The gross wages do not cover the negative offset that has been forwarded; therefore, no grossup is permitted."
I am getting this error msg just after USTAX function processing part of UTX0 subschema. I am highlighting below facts & findings for your reference.
As per a client requirement, I have configured a new gross up WT (ER benefit contribution) for a benefit plan (IT 0168) and the changes are in QAS system. The changes have to be reflected in period 20/2014 (4th May'14- 10th May'14) with retro effective 01/01/2014 as per the benefit plan record maintained from 01/01/2014.
This error msg is coming only for few employees. In my example, when I am running payroll in period 20/2014 with forced retro as 01/01/2014, system is giving error in period 14/2014 (23rd Mar'14-29th Mar'14). When I checked the pay result of this employee for period 14/2014, I can see the /101 is in -ve value and there is claim generated for this period. So I think, eventhough, a value of $ 2.53 is getting added as per the IT 0168 record, its not helping to give a +ve gross value and thus tax is not able to recoved on the same.
I hope you have come across this issue and can help me to assist to resolve the error msg.
Regards,
Prakash

If you have correctly configured payroll the system should automatically off set that and should create wage tyes /561 or /563 in RT.

Problem with offset values

Hi Experts,
I have a problem with offset values. I have create a variable on OFISCPER, it's characteristic value, indivdual value, mandatory and ready for the input. I need to show the varibel period and the l previous period and so on till 12 periods. I used the offset values (-1, -2, etc.) but when I execute the query I can show just the variable period and the period previous I don`t see. The query is based on multiprovider and don´t has filters. Can anyone help me?

Leonel,
You may nt need to have 12 columns in the query designer.
You could include the keyfigure and restrict it to the variable and create the offset for the 12 periods
Check this http://help.sap.com/saphelp_nw04/helpdata/en/00/e8d13f7fb44c21e10000000a1550b0/frameset.htm
-Doodle

Problem with offset length

Hi,
i have a problem with offset length please see below code and suggest :
data: content_new LIKE soli-line. "It has a length of 255 charecter
content_new = 'MTE:SD0\nwssd01_SD0_00\CPU\CPU_Utilization'.
content_new = content_new+4(251).
it is giving result:
content_new = SD0\nwssd01_SD0_00\CPU\CPU_Utiliza "it is removing last 4 charecter of UTILIZATION also
while i need :
content_new = 'SD0\nwssd01_SD0_00\CPU\CPU_Utilization'.
can anyone plz help me?
regards.
Moderator Message: Duplicate Post.
Edited by: kishan P on Oct 28, 2010 9:44 AM

You can find string length first. Subtract length by 4, Then use like new = str+4(len), use condense if required.

Negative offset detected, what dose it mean and how to delete it?

hi there,
i'm using FMS4.5.1 x64 on redhat5.7 x64, and came into an issue, that large files on storage lead to storage breakdown often, screenshot is as below while in fact my local disk is only 50GB.
and i found info in core.00.log as follows:
2012-04-20 03:38:04 22547 (i)2581173 Negative offset detected (/opt/adobe/fms/applications/liveTest/streams/q0zMo5g/live) : offset=-507374138652348382711520804962356974692518660038953004926260333415884728326174302 890304320038885215498198753334804692186466314664151670746002929865085836375544673427508409 682193412203496985536544362336214981856211063971185660760696718376693690811125567146445634 05586620533964800.000000
any idea on what dose that mean and what should i try to delete the offset so that my storage can work fine again?
Many thanks.

Not much sure on this, but is your system time in sych with current time. Also, how are these files created? Can you explain the scenario when you get "Negative offset detected" in core logs?

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.

Problem with Offset account showing Negative Values

Hi,
In our system, Offset account is showing Negative amount. We want to ZERO this.
This account have Price Diff. amount....Now how can do the same...
Please guide..

Hi,
Using F-02 you can transfer the balance.
e.g.
Dr Offsetting account
Cr Price difference/XXXX account
Rgds
Murali. N

Problems performing offset null and shunt calibration in NI PXI-4220

I am using a 350 ohm strain gage for the measurements, i have already create a task in MAX, when i want to perform offset null in the task, the program shows a waiting bar and the leds in the 4220 board start to tilting, but when the waiting bar stops, MAX gets blocked. it has been impossible to me to perform the offset null, what can i try?.
which will be the correct values for the parameters beside the gage parameters for the strain measures?

Hello,
Thank you for contacting National Instruments.
Usually when this problem occurs, it is do to incorrect task configuration or incorrectly matched quarter bridge completion resistor. Ensure that you have the correct Strain Configuration chosen. The default is Full Bridge I. If you only have a single strain gauge in your configuration, you will need to change your configuration. Also ensure that if your are using a quarter bridge completion resistor make sure that it is 350Ohm not 120Ohm. If the resistor if 120Ohm you will more thank likely not be able to null your bridge.
Please see the PXI-4220 User Manual for more information about your configuration and signal connections: http://digital.ni.com/manuals.nsf/websearch/F93CCA9A0B4BA19B86256D60
0066CD03?OpenDocument&node=132100_US
Also, you can download and install the latest NI-DAQ 7.2 driver: http://digital.ni.com/softlib.nsf/websearch/50F76C287F531AA786256E7500634BE3?opendocument&node=132070_US
This 7.2 driver has a signal connections tab displayed when configuring your DAQmx Task which show you how to correctly connect your signals.
Regards,
Bill B
Applications Engineer
National Instruments

Problem with offset settings CS5

I have got a large indesign CS5 (Win) document with many photos linked (all in RGB).
How should I prepare pdf for offset?
I am not sure the RGB-> CMYK conversion. If I can used conversion from Indesign which settings shoudl I choose.
I tried Pdf/X-1a 2001 but I am not sure about quality of phaotos and conversion RGB-> CMYK, apart of this text in
such a pdf is not sharp, seems pixelised.
Could you help me to solve this problem?
Is there any difference between external RGB->CMYK conversion with photoshop and those automatic from Indesign?offset, pdf
Please help

If I make a page with a frame filled with a color where it's easy to spot a conversion—something like 0/0/10/50—and export it as PDF/X-1a, AcrobatX's preflight tells me the profile is DeviceCMYK not the Fogra27 Output Intent Profile I exported.
If I open Acrobat's Output Preview, the default Simulation Profile is the output intent profile and the gray shows the same 0/0/10/50 separation as in ID. If I change the Simulation Profile to US Sheetfed the separation panel does not show a conversion—I still get 0/0/10/50.
If I print separations to the different destination profiles the results match the Output Preview, in both cases the cyan and magenta plates are blank. I don't see anyway to force a CMYK-to-CMYK conversion from the Print dialog.
If I export the page again and include a destination profile rather than an output intent (by setting the Standard to None) I get very different results.
Preflight shows Fogra as the profile. In this case the Output Preview simulation defaults to my Acrobat working CMYK space and I get a conversion (because it is not Fogra). If I select Fogra as the simulation there's no conversion, which is what I expect. Again my printed separations match the simulations—by default I get a CMYK-to-CMYK conversion.

Problem regarding offset length while upgrading from 4.7 to ECC 6.0

Hello Friends,
We are upgrading our system from 4.7 to ECC 6.0, during the this I have come across one problem in custom program. Program is not syntactically correct. It's giving error at write statment. WRITE : W_LFA1 +3(1429) to T_FILE. W_LFA1 is having of type LFA1. Error is "The sum of the offset and length (=1432) exceeds the length of the start (=1232) of the structure." Can anyone guide me in this.

Hi Chetan,
This should be an unicode error.
Try to replace your write statement by WRITE : W_LFA1 3(1429) to T_FILE and see.
Regards
Sayee

Custom InfoObject for date, problem with offset

Hi all,
I have a BEx reports presenting 0CALWEEK and another IO I created for dates.
This IO has the same properties as 0CALWEEK (but it was not created as a reference of 0CALWEEK).
In my report I'd like to use offsets for both IO's.
It works perfectly for 0CALWEEK, but it doesn't work at all for the other IO. Actually, only the first offset is shown. For all others weeks, I get "#".
Additionally, I made some calculations based on the week difference (using formula variables). Of course, every time a "#" appears, the calculation cannot be done (otherwise it works like it should).
Could anybody help me out with this?
Thanks in advance

Hi Jagadeesh,
did I understand you correctly that:
1) offsets only work with standard characteristics? (this seems really weird to me...)
2) if I want to use offsets with with Z_* characteristic, I will need ABAP?
The problem is that I don't know anything about ABAP.
Do you know any "typical" code to use to resolve this type of problem?
Where do I have to use this code: in the query, in the IO, in a start routine somewhere?
Thanks

Business Connector 4.8 - Problems while creating listener - Unicode

Hello,
we have a problem with the creation of the listener in the business connector 4.8.
We are sure that our system parameters are correct.
But we are missing the unicode button on the BC configuration page.
Our ERP is unicode, so the listener should support unicode as well.
Is this now by default in the new version 4.8 ?
Kind Regards
Tanja

I think BC 4.8 recognizes that automatically correctly.
If the button is not there anymore, you dont have to care about it.
Just give it a try...
CSY

Business Connector - JRE memory problem

Hi,
We have an Business Connector v4.0.1 under win2000 that uses IBM jvm 1.3.0 and due to the DST change we upgarde the JVM to SUN JRE 1.3.1_19,
The problem that we have is that the Xmx limit for Sun JRE 1.3.1_19 is limited to arounf 1.7 M.
However before the upgrade with the IBM jvm 1.3.0 we can use a value of Xmx up to 3G.
The question is why the Sun JRE is limited to 1.7 and not the IBM jvm..
Thanks for your help,
Chak,

Hi,
Please see the below links
WAS - Business Connector
business connector documentation
SAP Business Connector
Business connector
Will Business Connector 4.6 be affected by new Daylight savings changes
Business connector
More info on XI can be found at https://service.sap.com/xi
and webAS on http://help.sap.com/saphelp_nw04/helpdata/en/f3/e20f3adfd0a706e10000000a114084/frameset.htm
Check this also-
http://help.sap.com/saphelp_nw2004s/helpdata/en/6f/1bd5c2a85b11d6b28500508b5d5211/frameset.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b4f3755a-0401-0010-b6b3-9b65bb7d4503
Regards
Chilla..

Generic technology connector and SPML problems

I'm having some trouble finding docs for my problem. What I'm trying to do is create my own spml web service (employing the new Java 6 JWS technology), which can be used by OIM by means of a generic technology connector . But no matter what I do, I can't seem to make the two communicate. I can't find any documentation explaining how to create a SOAP web service for SPML: what methods should be created, their signature, whether there is any specific WSDL that I should use to generate the Java classes and methods for the web service, etc...
I actually don't even know whether the new JWS can be used at all. Perhaps I should be using Apache Axis (or Axis2) or something else.
Thanks.

This is what I've found in the docs:
"Each SPML request is sent in a SOAP message. The SOAP header carries authentication information for the request. The actual SPML request data is the SOAP message body. "
All I'm trying to do is create a SOAP web service (in this case with Java 6, but that's not fundamental) that can intercept that message and grab the SPML request (and then do what I have to do).
I tried with something like the following code:
package wsspml;
import javax.jws.WebService;
import java.io.IOException;
import java.util.logging.*;
@WebService
public class SPMLServer {
public String processRequest(String requestData) {
but it won't work. It's like the exposed SOAP method "processRequest" is invisible. It's not being called. Perhaps the signature is wrong. I don't know what to make of it. I'm trying to understand how to grab that SPML request that's coming from OIM through the custom generic technology connector that I configured.

Data Synchronizer GroupWise connector time shift problem

I have recently installed the latest 1.2.2 Data Synchronizer Mobility with GroupWise connector, one bug I have found when looking at time stamps of emails sent and received from the connector perspective I am seeing a 20 hrs time shift i.e. from my Android device I send an email to myself at 06:00 May 6 local the time it will show received at 10:00 May 5 also looking at sent time on the device it will say sent at 10:00 May 5. When I look at the GroupWise client or WebAccess sent and received time and date are correct. Conclusion it's only the Data Synchronizer showing time date incorrectly. Any thoughts welcome.

Update - This problem appears to be phone specific it is a Motorola MB525 with Android 2.2.2 we have some HTCs which do NOT have a problem with time zone. Another minor problem is items deleted on the device do not sync up to GroupWise

Connector 2.0 Problem - Negative offset

Similar Messages

Maybe you are looking for