Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Data element on structure for interface

former_member222946
Participant
0 Kudos

Hi all,

I'm working on the development of one interface from a non-sap system to SAP where on a first step SAP will capture a flat file into one structure "ZZZ" but I'm doubting about how to create this structure.

At first I was thinking on identifying a suitable component type/data element for each field (f.i. WAERS for currency field ZZZ-WAERS) but meanwhile I have noticed that for a similar interface the corresponding XXX structure was created using as data elements CHAR* type, where the * was the field length.

Which criteria would you choose in my case? and what will it depend on?

Thanks in advance.

Abdali

1 ACCEPTED SOLUTION

ThomasZloch
Active Contributor
0 Kudos

I think it is a good idea to use only CHAR-definitions for importing flat file data. Here the focus is to have a fixed column length and avoid conversion errors during import, as opposed to neat F1 help texts, for example.

When further processing the data inside SAP you can move the data to another structure with proper data elements (like WAERS or WRBTR), checking for consistency and catching conversion errors in the process.

Thomas

2 REPLIES 2

ThomasZloch
Active Contributor
0 Kudos

I think it is a good idea to use only CHAR-definitions for importing flat file data. Here the focus is to have a fixed column length and avoid conversion errors during import, as opposed to neat F1 help texts, for example.

When further processing the data inside SAP you can move the data to another structure with proper data elements (like WAERS or WRBTR), checking for consistency and catching conversion errors in the process.

Thomas

0 Kudos

Thanks a lot for you help Thomas.

Regards,

Abdali