topic Re: Synatx Error for POS and LEN data in ABAP coding in Application Development and Automation Discussions

Synatx Error for POS and LEN data in ABAP coding

Former Member — Sat, 19 Mar 2016 16:58:08 GMT

Hi,

I am writing this small code in ABAP editor. I am facing a syntactical error of Filed Type 'I' does not permit a sub field access.

Please explain this error type and also explain how to clear this error.

Please is my program( Just trying to write system date).

DATA: POS TYPE I VALUE 5,

LEN TYPE I VALUE 25.

WRITE AT/ POS(LEN) '********'.

SKIP.

WRITE AT: POS 'DATE', 20 SY-DATUM,

POS 'TIME', 20-SY-UZEIT.

ULINE AT/POS(LEN)

Regards

Shafali Jain

Re: Synatx Error for POS and LEN data in ABAP coding

Clemenss — Sat, 19 Mar 2016 18:03:23 GMT

which line the error is raised? Definitely wrog is 20-SY-UZEIT

you may check Positioning WRITE Output on the List - BC - ABAP Programming - SAP Library

or ABAP Keyword Documentation

Regards Clemens

Re: Synatx Error for POS and LEN data in ABAP coding

Former Member — Sat, 19 Mar 2016 20:09:56 GMT

Hi Shafali Jain,

Use the below code.

DATA: POS TYPE I VALUE 5,

LEN TYPE I VALUE 25.

WRITE AT : POS(LEN)'**************************'.

NEW-LINE.

WRITE AT : POS 'DATE', 20 SY-DATUM.

NEW-LINE.

WRITE AT : POS 'TIME', 20 SY-UZEIT.

NEW-LINE.

WRITE AT : POS(LEN) SY-ULINE.

Re: Synatx Error for POS and LEN data in ABAP coding

Former Member — Wed, 23 Mar 2016 13:09:08 GMT

Thanks.

Re: Synatx Error for POS and LEN data in ABAP coding

Former Member — Wed, 23 Mar 2016 13:26:50 GMT

Point of order.

The question has not been answered - some one has just given you code that works. You will never learn this way.

I type fields are integer fields and internally they are not held as digits but as binary codes. As a simple example a number from 0 to 65535 can be defined using a 2 byte code where (dependant on what type of processor you are using) you multiply the 2nd character by 256 and add the first.

Similarly Packed BCD's are represented by hex characters representing the values 0 to 9. Floting Point numbers contain a mantissa and an exponent. In all these cases to split them in any way would yield meaningless results.

In reference to your code, as it stands in your original post, the error is not the error quoted but 'Field "AT/" is unknown.

Please try to be correct when you are posting information since incorrect information can waste peoples time.

Rich

Re: Synatx Error for POS and LEN data in ABAP coding

Former Member — Wed, 23 Mar 2016 14:05:18 GMT

Hi Richard,

I am really sorry. I have just started learning SAP ABAP and with that lots of questions/queries arises.

I am sorry for putting incomplete information.

I will try not to do so again.

Regards

Shafali Jain

Re: Synatx Error for POS and LEN data in ABAP coding

Former Member — Wed, 23 Mar 2016 14:18:58 GMT

Shafali,

You only learn by doing things yourself. You asked a specific question: 'Please explain this error type' with reference to your 'Type I subfield access' error.

Not one of the people answered this question. Instead they concentrated on the second part of your post which was far easier to answer. Even then they did not explain what they had done - just posted a code listing.

Do you know exactly what was wrong with your code ?

You are just learning. Please don't learn by rote - it does you no good. There is a good site which gives you pointers to asking questions and getting answers:
http://www.catb.org/esr/faqs/smart-questions.html.

Have a good read, and if you cannot see why code works or why it appears different then always ask. And if you still have unanswered questions, re-iterate them in the same thread.

Rich

Re: Synatx Error for POS and LEN data in ABAP coding

Former Member — Wed, 23 Mar 2016 14:23:10 GMT

Richard,

Thanks for guiding me.

I'll try to fix the code and also consult the site you have provided and if still faces some issue will update in a proper format.

Thanks.

Shafali

Re: Synatx Error for POS and LEN data in ABAP coding

Former Member — Wed, 23 Mar 2016 14:26:59 GMT

NP.