cancel
Showing results for 
Search instead for 
Did you mean: 

RFC_READ_TABLE Options - Text length

Former Member
0 Kudos

Hi,

Is there a limit on the amount of characters you can use in the RFC_TABLE_READ > option > text parameter (where clause) seems to ignore and syntax after approximately 70 characters, just wondering if anyone has any experience using this call through xMII - need to cut down the returned data using this parameter significantly ?

Thanks,

Emmett

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Emmett,

yes that is exactly what I mean. Please remember to Append XML the item structure to

the OPTIONS fields.

Regards and let me know.

Pedro

Answers (2)

Answers (2)

Former Member
0 Kudos

Emmett,

if you need more then 72 character, then you need to define more items in the OPTIONS fields like this

example:

1. item = AUFNR EQ '000000700023' OR AUFNR EQ '000000700003'

2. item = OR AUFNR EQ '000000700006' OR AUFNR EQ '000000700007'

3. item = OR AUFNR EQ '000000700011' OR AUFNR EQ '000000700005'

Important is that the 1. item start with the condition.

Hope this will help you.

Regards

Pedro

Former Member
0 Kudos

Pedro,

When you say item 1 etc. should it be in the form of

SAPJCOFunction_0.Request{/RFC_READ_TABLE/TABLES/OPTIONS/item[1]/TEXT} =AUFNR EQ '000000700023' OR AUFNR EQ '000000700003'

SAPJCOFunction_0.Request{/RFC_READ_TABLE/TABLES/OPTIONS/item[2]/TEXT} =OR AUFNR EQ '000000700006' OR AUFNR EQ '000000700007'

SAPJCOFunction_0.Request{/RFC_READ_TABLE/TABLES/OPTIONS/item[3]/TEXT} =OR AUFNR EQ '000000700011' OR AUFNR EQ '000000700005'

etc. ?

Thanks again,

Emmett

Former Member
0 Kudos

Helo Emmett,

OPTION have a length of 72 characters.

Regards

Pedro

Former Member
0 Kudos

Pedro,

Any way to get around this length restriction that you know of ?

Line Breaks - xml input etc. ??

Thanks,

Emmett