Seeburger syntax rules

Hi everyone,
I have an EDI 322 V4010 the segment Q5 has the following rule
P0304 : If either Q503 or Q504 is present, then the other is required.
But when i suppress value for Q504 seeburger not show me any issue about it....i suppposed that seeburger also validate this rules...maybe something is missing or maybe seeburger dont do that....
any answer, please??
lpbuff

Hi Rajesh,
well these values, both are optional but it is not the problem.....exist a syntax rule in EDI structure, it 's a conditional in the standars for EDI...it says P0304 : If either Q503 or Q504 is present, then the other is required.
If you go to the segment and see the properties in the BIC tool it says that....so I suppose...that should be a message that told me that is not correct to have value Q5/03 without Q5/04....
i think that also seeburger validate it? or why they have the Rule if they are optional...?
thanks,
Lpbuff

Similar Messages

Syntax rules for dimension member?

What are the rules regarding a dimension member? Is there a character limit? I keep getting an Incorrect Syntax for member error (3305).
Error log looks like this(I know it's hard to read):
\\Record #25621 - Incorrect Syntax For Member XTO 20 PIPELINE (USE 707702) UNIT 073919     U073919     XTO 20 PIPELINE (USE 707702) U073919 (3305)
ETX      '
65600     '
EAST TX-OP '
65600     '
65600.0001     '
UNIT 073919     '
XTO 20" PIPELINE (USE 707702) UNIT 073919     '
U073919     '
XTO 20" PIPELINE (USE 707702) U073919'
('-designates end of line)

from the dbag:
When naming dimensions, members, and aliases in the database outline, follow these rules:
Use no more than the maximum lengths that are specified in Appendix A, “Limits”.
Names are not case-sensitive unless case-sensitivity is enabled. See “Setting Outline Properties” in the Essbase Administration Services Online Help.
Do not use " (quotation marks) or tabs anywhere in a name.
Do not place spaces at the beginning or end of a name. Analytic Services ignores spaces at the beginning or end of a name.
Do not use the following characters at the beginning of a name:
@ at signs
() parentheses
\ backslashes
. periods
{ } braces
+ plus signs
, commas
- dashes hyphens, or minus
_ underscores
= equal signs
| vertical bars
< less than signs
'single quotation marks
Do not use the following words as dimension or member names:
Calculation script commands, operators, and keywords. For a list of commands, see the Technical Reference.
Report writer commands. For a list of commands, see the Technical Reference.
Function names and function arguments. For a list of functions, see the Technical Reference.
Names of other dimensions, members (unless the member is shared), generation names, level names, and aliases in the database.
Any of the following words:
Note: If you enable Dynamic Time Series members, do not use the associated generation names—History, Year, Season,
Period, Quarter, Month, Week, or Day. See “Applying Predefined Generation Names to Dynamic Time Series
Members” on page 436.
Any of the following words:
ALL
AND
ASSIGN
CALC
CALCMBR
COPYFORWARD
CROSSDIM
CURMBRNAME
DIM
DIMNAME
DIV
DYNAMIC
EMPTYPARM
EQ
EQOP
EXCEPT
EXP
EXPERROR
FLOAT
FUNCTION
GE
GEN
GENRANGE
GROUP
GT
ID
IDERROR
INTEGER
LE
LEVELRANGE
LOOPBLOCK
LOOPPARMS
LT
MBR
MBRNAME
MBRONLY
MINUS
MISSING
MUL
MULOP
NE
NON
NONINPUT
NOT
OR
PAREN
PARENPARM
PERCENT
PLUS
RELOP
SET
SKIPBOTH
SKIPMISSING
SKIPNONE
SKIPZERO
TO
TOLOCALRATE
TRAILMISSING
TRAILSUM
UMINUS
UPPER
VARORXMBR
XMBRONLY
$$$UNIVERSE$$$
#MISSING
#MI

How do you enforce specific password syntax rules?

Hi Guys,
I'm setting up iPlanet Directory Server 5.1.3 and I need to configure it to enforce a password rule which says that you must have at least one letter and one number in your password. I've searched the documentation and googled the heck out of it, but I can't seem to find any reference as to how to do that. Does anybody have any info on if this is possible and where I might look for some info on how to do it?
Thanks,
Mike

Thanks gary, excelent find, ive just installed it on solaris 10.
heres what happened when i tried to use a password
test
then tester
then tester1
$ passwd
passwd: Changing password for admin
Enter existing login password:
New Password:
passwd: Password too short - must be at least 6 characters.
Please try again
New Password:
passwd: The password must contain at least 1 numeric or special character(s).
Please try again
New Password:
Re-enter new Password:
Your new password was rejected for the following reason:
it is based on a dictionary word
Permission denied
to build get hold of pam_cracklib.tar.gz, from sourceforge and
cracklib,2.7.tar.gz
first cracklib, change the DICTPATH in the Makefile for
/usr/dict/pw_dict
do
CC=/opt/sfw/bin/gcc; export CC
and in the utils directory change the make file so all the cc's are gcc
then
make all
now cd cracklib and cp libcrack.a /usr/lib and packer.h to /usr/include
cd to the utils directory and copy all the binaries to /usr/bin
cp mkdict testlib testnum teststr unpacker /usr/bin
now move on to the pam part
unpack and cd to pam_cracklib
edit the GNUmakefile as follows or use this GNUmakefile
# !!! Hello !!!
# Make sure you are using GNU Make, and not some cheap imitation.
# !!! Thank you !!!
OS=$(shell uname)
ARCH=$(shell uname -p)
CRACKLIB_TARGET=pam_cracklib.so
DESTDIR=/usr/lib/security
PERMS=0700
PASSWORD_SRCS=pam_password.c
COMMON_SRCS=pam_module.c logging.c util.c
CRACKLIB_SRCS=cracklib.c $(COMMON_SRCS) $(PASSWORD_SRCS)
CRACKLIB_OBJS=$(CRACKLIB_SRCS:.c=.o)
DICTPATH="/usr/dict/pw_dict"
INCL=
LIBS=-lpam
CRACK_LIBS=-lcrack
CC=gcc
CFLAGS=-g -Wall -fPIC -D$(OS) -D$(ARCH)
LD=ld
ifeq ($(OS),SunOS)
LDFLAGS=-G -z redlocsym -L/usr/lib -R/usr/lib
else
LDFLAGS=-x --shared -L/usr/lib -R/usr/lib<br />
endif
RM=rm
FORCE_REBUILD=
password: $(CRACKLIB_TARGET)
# We will use this when cproto(1) stops sucking
# %.h : %.c $(FORCE_REBUILD) # A ".o" file depends on the corresponding ".c" fil
e
# cproto -E 0 $<
%.o : %.c $(FORCE_REBUILD) # A ".o" file depends on the corresponding ".c" file
$(CC) $(INCL) $(CFLAGS) -c $< -o $@
% : %.o # override default linking rule just in case
@echo
@echo $@ is not a valid target
@echo
$(CRACKLIB_TARGET) : CFLAGS += -DMODULE_NAME=\"$(CRACKLIB_TARGET)\" -DCRACKLIB_
DICTPATH=\"$(DICTPATH)\"
$(CRACKLIB_TARGET) : $(FORCE_REBUILD) $(CRACKLIB_OBJS)
$(LD) $(LDFLAGS) -o $@ $(CRACKLIB_OBJS) $(LIBS) $(CRACK_LIBS)
@echo
@echo $@ built successfully!
@echo
# Need -O so the inline "stat()" gets compiled, grr
$(DESTDIR)/$(CRACKLIB_TARGET) : $(CRACKLIB_TARGET)
@echo installing...
test -d $(DESTDIR) || mkdir -p $(DESTDIR)
cp $(CRACKLIB_TARGET) $(DESTDIR)
chown root $(DESTDIR)/$(CRACKLIB_TARGET)
chgrp root $(DESTDIR)/$(CRACKLIB_TARGET)
chmod $(PERMS) $(DESTDIR)/$(CRACKLIB_TARGET)
$(FORCE_REBUILD):
@echo rebuilding...
install: $(DESTDIR)/$(CRACKLIB_TARGET)
rebuild:
$(MAKE) $(MOREMAKEFLAGS) "FORCE_REBUILD=REBUILD"
clean:
$(RM) -f $(CRACKLIB_TARGET)
$(RM) -f $(CRACKLIB_OBJS)
$(RM) -f #*
$(RM) -f *~
now run gmake
and gmake install
edit /etc/pam.conf as follows
95 #
96 other password required pam_dhkeys.so.1
97 other password requisite pam_authtok_get.so.1
98 other password requisite pam_cracklib.so
99 other password requisite pam_authtok_check.so.1
100 other password required pam_authtok_store.so.1
101 #
102 # Support for Kerberos V5 authentication and example configurations can
103 # be found in the pam_krb5(5) man page under the "EXAMPLES" section.
104 #
this is adding line 98 and save the file
thats it
regards peter

B2B-51510 - Syntax Errors

How can we relax the default validation errors ? where are the syntax rules defined ?
We are seeing the following while sending an outbound txn
If either of BPR12, BPR13 is present, then all must be present. The syntax rule P1213 of Segment BPR is violated. Segment BPR is defined in the guideline at position 020.{br}{br}This error was detected at:{br}{tab}Segment Count: 2{br}{tab}Element Count: 10{br}{tab}Characters: 4726 through 4726
At least one of N102, N103 must be present. The syntax rule R0203 of Segment N1 is violated. Segment N1 is defined in the guideline at position 070.{br}{br}This error was detected at:{br}{tab}Segment Count: 20{br}{tab}Element Count: 2{br}{tab}Characters: 8405 through 8405

You may disable validation at agreement level to not have incoming/outgoing payload validated against ecs.
Regards,
Anuj

ABAP in SapScript : syntax, data types, ... ?

Hello,
Can someone tell me what are the biggest differences between regular ABAP and ABAP in SapScript? Like syntax rules, possible data types, and so on.
Thanks!

Ok, thanks for the answers.
Just one more question
Is it then also possible to create a SmartForm form (or Adobe Form) from within SapScript? I am looking for a workaround solution for correspondence in Training and Event Management. Only SapScript forms are possible, but if it is possible to create other forms with ABAP code in the SapScript, it could work, I think?

Password Policy Syntax

I need to set up a password policy where both uppercase and lowercase letters must coexist in the selected password.
I haven't seen this option in the password parameter fields in OID.
Is it possible to specify a additional or different password syntax rule?
Oriol

Which version of OID are you using. e.g. with 10.1.4. you can specify/configure this in OID.
regards,
--Olaf

LDAP Password Policy - Syntax

Hi,
I am trying to find out if there is a way to define password syntax rules from within the LDAP server (I am using IPlanet version 5.1 Service Pack 2).
The password syntax used at my company specifies that all passwords must contain at least one lowercase letter, one uppercase letter, and one number. Also, passwords may not contain any part of the username or any part of the user's full name.
Is there a way to get the LDAP server to perform these checks? And if so, how?
Thanks!

DS does not support this at the server level. You may have to build a pre-op plugin

Generic syntax symetry

The generic method syntax is:
MethodHeader ::= MethodModifiersOpt TypeParametersOpt ResultType MethodDeclarator
ThrowsOptWon't it be more natural (subjective concept) to have it like this (sorry, I can't access the JLS now that java.sun.com is down, to check for MethodDeclarator definition):
MethodHeader ::= MethodModifiersOpt ResultType MethodDeclarator ThrowsOpt
MethodDeclarator ::= MethodName TypeParametersOpt MethodParametersThat way, you write:
public T foo<T>(T x)instead of
public <T> T foo(T x)The reasons (again subjective):
- Orthogonality of the language, adding symetrie with generic class definitions, where generic parameters appears after class name.
- Parameters, generic or not, are listed after the method name. For a human being, educated to functional languages, it's more obvious.
Well, parsing is a bit more difficult as a type parameter use can appear before its definition.
Is it only a matter of taste or is there another hidden reason against this syntax?

Hi,
Ambiguities in this syntax can be resolved with one character look ahead in the parser, making it context free.
But isn't a similar a rule already introduce to disambiguate the >> and >>> sequences? The syntax rules are not particularly simple too:ReferenceType ::= ClassOrInterfaceType | ArrayType | TypeVariable
ClassOrInterfaceType ::= Name | Name < ReferenceTypeList1
ReferenceTypeList1 ::= ReferenceType1| ReferenceTypeList , ReferenceType1
ReferenceType1 ::= ReferenceType > | Name < ReferenceTypeList2
ReferenceTypeList2 ::= ReferenceType2 | ReferenceTypeList , ReferenceType2
ReferenceType2 ::= ReferenceType >> | Name < ReferenceTypeList3
ReferenceTypeList3 ::= ReferenceType3 | ReferenceTypeList , ReferenceType3
ReferenceType3 ::= ReferenceType >>>
TypeParameters ::= < TypeParameterList1
TypeParameterList1 ::= TypeParameter1 | TypeParameterList , TypeParameter1
TypeParameter1 ::= TypeParameter > | TypeVariable extends ReferenceType2I fear that the foo<T>(T x) syntax could appear in Java in a second shot, to accomodate programmers knowing other languages or to make it more orthogonal. Just like the String[] array or String array[] syntax is already accepted to accomodate C and C++ programmers...

Any good doc showing all ABAP syntax?

I found a web page showing all ABAP syntax rules with hyper links :
http://www.sts.tu-harburg.de/teaching/sap_r3/ABAP4/abapindx.htm
It's a very helpful way to describe the language itself. Have we any internal materials doing the same?
Thanks in advance.

Hi,
chk this.
Please visit this link. I hope this will help you a lot.
LINK : http://sapabap.iespana.es/sapabap/manuales/learnabap/
http://help.sap.com/saphelp_nw2004s/helpdata/en/43/41341147041806e10000000a1553f6/frameset.htm
rgds
anver

EDI Convertion Space Issue

Hi
We are converting EDI to XML using "localejbs/X12ConverterModule" , after conversion we still see D_I06 has space left over, which is failing in VM mapping, i stripped out space using UDF, works fine, anyone experienced same issue in EDI convertion
To test it, I took XMl form B2B mapping http://sap.com/xi/B2B/Examples/ANSIX12 > MM_ASC850_4010_TO_ORDERS05, by default D_I06 has space left over, I understand for D_I02 & D_I04 but not clear for D_I06
<?xml version="1.0" encoding="UTF-8"?>
<ns0:ASC850_004010 xmlns:ns0="http://sap.com/xi/B2B/Examples/ANSIX12">
   <S_ISA>
      <D_DATAELEMENTSEPARATOR>*</D_DATAELEMENTSEPARATOR>
      <D_I01>00</D_I01>
      <D_I02>          </D_I02>
      <D_I03>00</D_I03>
     <D_I04>          </D_I04>
     <D_I05>ZZ</D_I05>
      <D_I06>SAP0001       </D_I06>
Check the attached document
Checked with X12 modules still the same
Configuring the Converter Module Parameters - SAP NetWeaver Process Integration, business-to-business add-on 1.0 - SAP L…

Hello,
Seeburger apparently just pushes the content to the target message. The B2B add-on contains business logic to verify lengths, based on the XML schema.
Seeburger also uses logic to verify that incoming EDI-Files are following the syntax rules, and also verifies outgoing EDI messages in the same way to make sure that all EDIFACT/ANSI X12 Syntax rules are fullfilled.
However in this example an incoming ANSI X12-file is translated to the XML-equivalent and for the XML-ANSI X12 which is then created from the original ANSI X2 file, not the same "syntax rules" need to be applied (as they cannot be applied anyway with the XML-possibilities)....also there is no definition existing on how an XML-equivalent of an ANSI X12 file need to look like....therefor it is just a defined behaviour of Seeburger that this incoming field is modified by stripping away the leading spaces....(since field length are anyway not verified on XML-side)
Kind Regards
Stefan

Importing internal table from one program to another program

Hi everybody,
i have one small doubt.
i am using submit statement and passing the values from this program to another program selection screen. in that program logic is written.In that program one internal table values are being exported to the memory id of that program. now i have to import that internal table values into my program by using import statement. i am using the following syntax
import itab from menory id 'program name'.
but i am getting an error saying program name is unknown.
what is the exat syntax for this .
thanking you,
giri.

hi,
check these statements.
IMPORT - Get data
Variants:
1. IMPORT obj1 ... objn FROM DATA BUFFER f.
2. IMPORT obj1 ... objn FROM INTERNAL TABLE itab.
2. IMPORT obj1 ... objn FROM MEMORY.
3. IMPORT obj1 ... objn FROM SHARED MEMORY itab(ar) ID key.
4. IMPORT obj1 ... objn FROM SHARED BUFFER itab(ar) ID key.
5. IMPORT obj1 ... objn FROM DATABASE dbtab(ar) ID key.
6. IMPORT obj1 ... objn FROM DATASET dsn(ar) ID key.
7. IMPORT obj1 ... objn FROM LOGFILE ID key.
8. IMPORT DIRECTORY INTO itab FROM DATABASE dbtab(ar) ID key.
9. IMPORT (itab) FROM ... .
In some cases, the syntax rules that apply to Unicode programs are different than those for non-Unicode programs. For more details, see Storing Cluster Tables.
Variant 1
IMPORT obj1 ... objn FROM DATA BUFFER f.
Extras:
1. ... = f (for each object to be imported)
2. ... TO f (for each object to be imported)
3. ... ACCEPTING PADDING
4. ... ACCEPTING TRUNCATION
5. ... IGNORING STRUCTURE BOUNDARIES
6. ... IGNORING CONVERSION ERRORS
7. ... REPLACEMENT CHARACTER c
8. ... IN CHAR-TO-HEX MODE
9. ... CODE PAGE INTO f1
10. ... ENDIAN INTO f2
The syntax check performed in an ABAP Objects context is stricter than in other ABAP areas.
See You Cannot Use Implicit Field Names in Clusters.
Effect
Imports the data objects obj1 ... objn from the data buffer declared. The data buffer must be of type XSTRING . The data objects obj1 ... objn can be fields, structures, complex structures, or tables. The system imports all the data that has been stored in the data buffer f using the EXPORT ... TO DATA BUFFER statement and is listed here. It also checks that the structure used in the IMPORT statement matches the one in the EXPORT statement.
The Return Code is set as follows:
SY-SUBRC = 0:
The existing data objects in the data cluster specified were imported. The rest remain unchanged. (In some circumstances, this may mean that no data objects were imported).
SY-SUBRC = 4:
The data objects could not be imported. The contents of all the objects remain unchanged.
Addition 1
... = f (for each object to be imported)
Addition 2
... TO f (for each object to be imported)
Effect
The object is stored in the field f.
Addition 3
... ACCEPTING PADDING
Effect
This addition allows you to append new fields to the end
of structures, sub-structures, and internal tables. The IMPORT statement fills the additional fields with initial values; make existing fields (C, N, X, P, I1, and I2) longer; map character-type fields to STRING-type fields; or to map byte-type fields to XSTRING-type fields.
Addition 4
... ACCEPTING TRUNCATION
Effect
This addition allows you to shorten the last CHAR
fields, or to omit the last component at the top level. (Until Release 4.6, you could do this without using an addition).
Addition 5
... IGNORING STRUCTURE BOUNDARIES
Effect
This addition means that only the fragment sequence is
relevant - that is, that any sub-structures match. If you use this addition, the system ignores any alignment changes necessitated by Unicode - such as inserting named includes.
You cannot use this addition with either addition 3 (enlarge structure) or addition 4 (shorten structure), since it specifies that structure and include boundaries are to be ignored.
From Release 6.10 onwards, the include information is stored in datasets, so that the system can also check that includes match - that is, that sub-structures and includes (named or unnamed) are treated equally. When data is imported in a Release prior to 6.10, includes are not checked.
Addition 6
...IGNORING CONVERSION ERRORS
Effect
This addition prevents the system from triggering a
runtime error, if an error occurs when the character set is converted. '#' is used as a replacement character.
Addition 7
... REPLACEMENT CHARACTER c
Effect
The replacement character is used if a particular
character cannot be converted when the character set is converted.
This addition can only be used in conjunction with addition 6.
Addition 8
... IN CHAR-TO-HEX MODE
Effect
Not all character-type fields are converted. To convert
a field, you must create a field (or structure) that is identical to the exported field or structure, except that all its character-type components must be replaced with hexadecimal fields.
You can only use this addition in Unicode programs, to allow you to import camouflaged binary data as single-byte characters.
Moreover, you cannot use this addition in conjunction with the additions 3, 4, 5, 6, or 7.
Addition 9
... CODE PAGE INTO f1
Effect
The code page of the exported data is stored in the
character-type field f1 - for example, to analyze data that has been imported with the IN CHAR-TO-HEX MODE addition.
Addition 10
... ENDIAN INTO f2
Effect
The byte order (LITTLE or BIG) of the
exported data is stored in the field f2 - for example, to analyze data that has been imported with the IN CHAR-TO-HEX MODE addition. The field f2 must have the type ABAP_ENDIAN, which is defined in the type group ABAP. For this reason, the type group ABAP must be included in the ABAP program using a TYPE-POOLS statement.
Variant 2
IMPORT obj1 ... objn FROM INTERNAL TABLE itab.
Extras:
1. ... = f (for each object to be imported)
2. ... TO f (for each object to be imported)
3. ... ACCEPTING PADDING
4. ... ACCEPTING TRUNCATION
5. ... IGNORING STRUCTURE BOUNDARIES
6. ... IGNORING CONVERSION ERRORS
7. ... REPLACEMENT CHARACTER c
8. ... IN CHAR-TO-HEX MODE
9. ... CODE PAGE INTO f1
10. ... ENDIAN INTO f2
The syntax check performed in an ABAP Objects context is stricter than in other ABAP areas. See No implicit field names in cluster.
Effect
Imports the data objects obj1 ... objn (fields, structures, complex structures, or tables) from the specified internal table itab. The first column in the internal table must be of the predefined type INT2 and the second must be type X. To define the first column you must refer to a data element in the ABAP Dictionary that has the predefined type INT2.
All data that was stored in the internal table itab using EXPORT ... TO INTERNAL TABLE and listed, is imported. The system checks that the EXPORT and IMPORT structures match.
The Return Code is set as follows:
SY-SUBRC = 0:
The existing data objects in the specified data cluster were imported, the rest remain unchanged (it is possible that no data object was imported).
SY-SUBRC = 4:
The data objects could not be imported.
The contents of all listed objects remain unchanged
Addition 1
... = f (for each object to be imported)
Addition 2
... TO f (for each object to be imported)
Effect
Places the object in the field f.
Addition 3
... ACCEPTING PADDING
Effect
This addition allows you to add new fields to the ends
of structures, even to substructures and internal tables (the additional fields are filled with initial value during the IMPORT). It also allows you to increase the size of existing fields (C, N, X, P, I1, and I2) and to map Char fields to STRING type fields or byte fields to XSTRING type fields.
Addition 4
... ACCEPTING TRUNCATION
Effect
This addition allows you to shorten the last CHAR
field or omit the last component on the highest level (till Release 4.6 this was possible without specifying an addition).
Addition 5
... IGNORING STRUCTURE BOUNDARIES
Effect
This addition means that only the page order is
relevant, that is any substructures match. With this addition, the system also ignores alignment changes arising from the Unicode conversion (for example, due to subsequent insertion of named includes).
This addition rules out any subsequent structural enhancements (addition 3) or structural shortening (addition 4) because with this addition it is the structural limits and include limits that are to be ignored.
As from Release 6.10, the include information will also be stored in the dataset, so that it is possible to also check whether the includes match, that is substructures and includes (named or unnamed) are treated the same. When importing data that was exported in a Release lower than 6.10, the includes are not checked.
Addition 6
...IGNORING CONVERSION ERRORS
Effect
This addition has the effect that an error in the
character set conversion does not cause a runtime error. The system uses "#" as a replacement character.
Addition 7
... REPLACEMENT CHARACTER c
Effect
The system uses the specified replacement character if a
character cannot be converted during a character set conversion. If this addition is not specified, the system uses "#" as a replacement character.
This addition can only be used in conjunction with addition 6.
Addition 8
... IN CHAR-TO-HEX MODE
Effect
No character type fields are converted. For this you
must create a field or structure that is identical to the exported field or exported structure, except that all character type fields must be replaced with hexadecimal fields.
This addition, which is only allowed in programs with a set Unicode flag, allows you to import binary data disguised as single byte characters. This addition cannot be used in conjunction with additions 3, 4, 5, 6, and 7.
Addition 9
... CODE PAGE INTO f1
Effect
The codepage of the exported data is stored in the
character-type field f1 (for example, to be able to analyze the data imported with the addition IN CHAR-TO-HEX MODE).
Addition 10
... ENDIAN INTO f2
Effect
The byte order (LITTLE or BIG) of the
exported data is stored in the field f2 (for example, to be able analyze the data imported using the addition IN CHAR-TO-HEX MODE). The field f2 must be of type ABAP_ENDIAN, defined in type group ABAP. You must therefore include the type group ABAP in the ABAP program with a TYPE-POOLS statement.
Variant 3
IMPORT obj1 ... objn FROM MEMORY.
Extras:
1. ... = f (for each object to be imported) 2. ... TO f (for each object to be imported)
3. ... ID key
4. ... ACCEPTING PADDING
5. ... ACCEPTING TRUNCATION
6. ... IGNORING STRUCTURE BOUNDARIES
The syntax check performed in an ABAP Objects context is stricter than in other ABAP areas. See You Must Enter Identification and Cannot Use Implicit Field Names inClusters
Effect
Imports data objects obj1 ... objn (fields, structures, complex structures or tables) from a data cluster in the ABAP memory (see EXPORT). Reads in all data without an ID that was exported to memory with "EXPORT ... TO MEMORY.". In contrast to the variant IMPORT FROM DATABASE, it does not check that the structure matches in EXPORT and IMPORT.
The Return Code is set as follows:
SY-SUBRC = 0:
The existing data objects in the data cluster specified were imported. The rest remain unchanged (in some circumstances, this may mean that no data objects were imported).
SY-SUBRC = 4:
The data objects could not be imported, probably because the ABAP memory was empty.
The contents of all objects remain unchanged.
Note
You should always use the addition 3 (... ID key) with the statement. Otherwise, the effect of the variant is not certain (EXPORT statements in different parts of a program overwrite each other in the ABAP memory), since it exists only for reasons of compatibility with R/2.
Additional methods for selecting and deleting data clusters in the ABAP memory are provided by the system class CL_ABAP_EXPIMP_MEM.
Please consult Data Area and Modularization Unit Organization documentation as well.
Addition 1
... = f (for each object to be imported)
Addition 2
... TO f (for each object to be imported)
Effect
The object is placed in field f.
Addition 3
... ID key
Effect
Imports only data stored in ABAP memory under the ID key.
Notes
The key, key, must be a character-type data object (but not a string).
The Return Code is set as follows:
SY-SUBRC = 0:
The existing data objects in the data cluster specified were imported. The rest remain unchanged (in some circumstances, this may mean that no data objects were imported).
SY-SUBRC = 4:
The data objects could not be imported, probably because an incorrect ID was used.
The contents of all objects remain unchanged.
Addition 4
... ACCEPTING PADDING
Effect
This addition allows you to append new fields to the end of structures, sub-structures, and internal tables. The IMPORT statement fills the additional fields with initial values; make existing fields (C, N, X, P, I1, and I2) longer; map character-type fields to STRING-type fields; or to map byte-type fields to XSTRING-type fields.
Addition 5
... ACCEPTING TRUNCATION
Effect
This addition allows you to shorten the last CHAR field, or to omit the last component at the top level. (Until Release 4.6, you could do this without using an addition).
Addition 6
... IGNORING STRUCTURE BOUNDARIES
Effect
This addition means that only the fragment sequence is relevant - that is, that any sub-structures match. If you use this addition, the system ignores any alignment changes necessitated by Unicode - such as inserting named includes.
You cannot use this addition with either addition 3 (enlarge structure) or addition 4 (shorten structure), since it specifies that structure and include boundaries are to be ignored.
From Release 6.10 onwards, the include information is stored in datasets, so that the system can also check that includes match - that is, that sub-structures and includes (named or unnamed) are treated equally. When data is imported in a Release prior to 6.10, includes are not checked.
Related
EXPORT TO MEMORY, DELETE FROM MEMORY, FREE MEMORY
Variant 4
IMPORT obj1 ... objn FROM SHARED MEMORY itab(ar) ID key.
Extras:
1. ... = f (for each object to be exported) 2. ... TO f (for each object to be exported)
3. ... CLIENT g (before ID key)
4. ... TO wa (after itab(ar) or ID key )
5. ... ACCEPTING PADDING
6. ... ACCEPTING TRUNCATION
7. ... IGNORING STRUCTURE BOUNDARIES
The syntax check performed in an ABAP Objects context is stricter than in other ABAP areas.
See You Cannot Use Implicit Field Names in Clusters and You Cannot Use Table Work Areas.
Effect
Imports the data objects obj1 ... objn (fields, structures, complex structures, or tables) from shared memory. The data objects are read using the ID key from the area ar in the table itab - c.f. EXPORT TO SHARED MEMORY). You must use itab to specify a database table although the system reads from a memory table with the appropriate structure.
The Return Code is set as follows:
SY-SUBRC = 0:
The existing data objects in the data cluster specified were imported. The rest remain unchanged. (In some circumstances, this may mean that no data objects were imported).
SY-SUBRC = 4:
The data objects could not be imported. You may have used the wrong ID. The contents of all the objects remain unchanged.
Notes
The table dbtab named according to SHARED MEMORY must be declared using TABLES (except in addition 2).
The structure of fields (field symbols and internal tables) to be imported must match the structure of the objects exported in the dataset. The objects must be imported under the same names as those under which they were exported. Otherwise, they will not be imported.
The key length consists of: the client (3 digits, but only if tab is client-specific); area (2 characters); ID; and line number (4 bytes). It must not exceed 64 bytes - that is, the ID must not be longer than 55 characters, if the table is client- specific.
The key, key, must be a character-type data object (but not a string).
Additional methods for selecting and deleting data clusters in the shared memory are provided by the system class CL_ABAP_EXPIMP_SHMEM.
Please consult Data Area and Modularization Unit Organization documentation as well.
Addition 1
... = f (for each object to be imported)
Addition 2
... TO f (for each object to be imported)
Effect
The object is stored in the field f.
Addition 3
... CLIENT g (before ID key)
Effect
The data is imported from client g (provided the import/export table is tab client-specific). The client, g must be a character-type data object (but not a string).
Addition 4
... TO wa (after itab(ar) or ID key)
Effect
You need to use this addition if user data fields have been stored in the application buffer and are to be read from there. The work area wa is used instead of the table work area. The target area must correspond to the structure of the called table tab.
Addition 5
... ACCEPTING PADDING
Effect
This addition allows you to: append new fields to the end of structures, sub-structures, and internal tables. The IMPORT statement fills the additional fields with initial values; make existing fields (C, N, X, P, I1, and I2) longer; map character-type fields to STRING-type fields; or to map byte-type fields to XSTRING-type fields.
Addition 6
... ACCEPTING TRUNCATION
Effect
This addition allows you to shorten the last CHAR fields, or to omit the last component at the top level. (Until Release 4.6, you could do this without using an addition).
Addition 7
... IGNORING STRUCTURE BOUNDARIES
Effect
This addition means that only the fragment sequence is relevant - that is, that any sub-structures match. If you use this addition, the system ignores any alignment changes necessitated by Unicode - such as inserting named includes.
You cannot use this addition with either addition 4 (enlarge structure) or addition 5 (shorten structure), since it specifies that structure and include boundaries are to be ignored.
From Release 6.10 onwards, the include information is stored in datasets, so that the system can also check that includes match - that is, that sub-structures and includes (named or unnamed) are treated equally. When data is imported in a Release prior to 6.10, includes are not checked.
Related
EXPORT TO SHARED MEMORY, DELETE FROM SHARED MEMORY
Variant 5
IMPORT obj1 ... objn FROM SHARED BUFFER itab(ar) ID key.
Extras:
1. ... = f (for each object to be exported) 2. ... TO f (for each object to be exported)
3. ... CLIENT g (before ID key)
4. ... TO wa (last addition or after itab(ar))
The syntax check performed in an ABAP Objects context is stricter than in other ABAP areas.
See Cannot Use Implicit Fieldnames in Clusters und Cannot Use Table Work Areas.
Effect
Imports data objects obj1 ... objn (fields or
tables) from the cross-transaction application buffer. The data objects are read in the application buffer using the ID key of the area ar of the buffer area for the table itab (see EXPORT TO SHARED BUFFER). You must use dbtab to specify a database table although the system reads from a memory table with an appropriate structure.
The Return Code is set as follows:
SY-SUBRC = 0:
The existing data objects in the data cluster specified were imported. The rest remain unchanged (in some circumstances, this means that no data objects were imported).
SY-SUBRC = 4:
The data objects could not be imported, probably because an incorrect ID was used.
The contents of all objects remain unchanged.
Example
Import two fields and an internal table from the application buffer with the structure INDX:
TYPES: BEGIN OF ITAB3_LINE,
         CONT(4),
       END OF ITAB3_LINE.
DATA: INDXKEY LIKE INDX-SRTFD VALUE 'KEYVALUE',
      F1(4),
      F2(8) TYPE P DECIMALS 0,
      ITAB3 TYPE STANDARD TABLE OF ITAB3_LINE,
      INDX_WA TYPE INDX.
Import data.
IMPORT F1 = F1 F2 = F2 ITAB3 = ITAB3
       FROM SHARED BUFFER INDX(ST) ID INDXKEY TO INDX_WA.
After import, the data fields INDX-AEDAT and
INDX-USERA in front of CLUSTR are filled with
the values in the fields before the EXPORT
statement.
Notes
You must declare the table dbtab, named after DATABASE using a TABLES statement.
The structure of the fields, structures, and internal tables to be imported must match the structure of the objects exported to the dataset. Moreover, the objects must be imported with the same name used to export them. Otherwise, the import is not performed.
The maximum total key length is 64 bytes. It must include: a client if the table is client-specific (3 characters); an area (2 characters); identification; and line counter (4 bytes). This means that the number of characters available for the identification of a client-specific table is 55 characters.
The key, key, must be a character-type data object (but not a string).
Additional methods for selecting and deleting data clusters in the cross-transaction application buffer are provided by the system class CL_ABAP_EXPIMP_SHBUF.
Please consult Data Area and Modularization Unit Organization documentation as well.
Addition 1
... = f (for each object to be imported)
Addition 2
... TO f (for each object to be imported)
Effect
The object is placed in the field f
Addition 3
... CLIENT g (after dbtab(ar))
Effect
Takes the data from the client g (if the import/export table dbtab is client-specific). The client g must be a character-type data object (but not a string).
Addition 4
... TO wa (as the last addition or after itab(ar))
Effect
You need to use this addition if you want to save user data fields in the application buffer and then read them from there later. The system uses a work area wa instead of a table work area. The target area must have the same structure as the table tab.
Example
DATA: INDX_WA TYPE INDX,
      F1.
IMPORT F1 = F1 FROM SHARED BUFFER INDX(AR)
               CLIENT '001' ID 'TEST'
               TO INDX_WA.
WRITE: / 'AEDAT:', INDX_WA-AEDAT,
       / 'USERA:', INDX_WA-USERA,
       / 'PGMID:', INDX_WA-PGMID.
Variant 6
IMPORT obj1 ... objn FROM DATABASE dbtab(ar) ID key.
Extras:
1. ... = f (for each object to be imported)
2. ... TO f (for each object to be imported)
3. ... CLIENT g (before ID key )
4. ... USING form
5. ... TO wa (last addition or after dbtab(ar))
6. ... MAJOR-ID id1 (instead of ID key)
7. ... MINOR-ID id2 (with MAJOR-ID id1 )
8. ... ACCEPTING PADDING
9. ... ACCEPTING TRUNCATION
10. ... IGNORING STRUCTURE BOUNDARIES
11. ... IGNORING CONVERSION ERRORS
12. ... REPLACEMENT CHARACTER c
13. ... IN CHAR-TO-HEX MODE
14. ... CODE PAGE INTO f1
15. ... ENDIAN INTO f2
The syntax check performed in an ABAP Objects context is stricter than in other ABAP areas. See Cannot Use Implicit Fieldnames in Clusters and Cannot Use Table Work Areas.
Effect
Imports data objects obj1 ... objn (fields, structures, complex structures, or tables) from the data cluster with ID key in area ar of the database table dbtab (see EXPORT TO DATABASE).
The Return Code is set as follows:
SY-SUBRC = 0:
The existing data objects in the data cluster specified were imported. The rest remain unchanged (in some circumstances, this may mean that not data objects were imported).
SY-SUBRC = 4:
The data objects could not be imported, probably because an incorrect ID was used.
The contents of all objects remain unchanged.
Example
Import two fields and an internal table:
TYPES: BEGIN OF TAB3_TYPE,
          CONT(4),
       END OF TAB3_TYPE.
DATA: INDXKEY LIKE INDX-SRTFD,
      F1(4), F2 TYPE P,
      TAB3 TYPE STANDARD TABLE OF TAB3_TYPE WITH
                NON-UNIQUE DEFAULT KEY,
      WA_INDX TYPE INDX.
INDXKEY = 'INDXKEY'.
IMPORT F1   = F1
       F2   = F2
       TAB3 = TAB3 FROM DATABASE INDX(ST) ID INDXKEY
       TO WA_INDX.
Notes
You must declare the table dbtab, named after DATABASE, using the TABLES statement (except in addition 5).
The structure of fields, field strings and internal tables to be imported must match the structure of the objects exported to the dataset. In addition, the objects must be imported under the same name used to export them. If this is not the case, either a runtime error occurs or no import takes place.
Exception: You can lengthen or shorten the last field if it is of type CHAR, or add/omit CHAR fields at the end of the structure.
The key, key, must be a character-type data object (but not a string).
Additional methods for selecting and deleting data clusters in the database table specified are provided by the system class CL_ABAP_EXPIMP_DB.
Addition 1
... = f (for each object to be imported)
Addition 2
... TO f (for each object to be imported)
Effect
The object is placed in field f.
Addition 3
... CLIENT g (before the ID key)
Effect
Data is taken from the client g (in client-specific import/export databases only). Client g must be a character-type data object (but not a string).
Example
DATA: F1,
      WA_INDX TYPE INDX.
IMPORT F1 = F1 FROM DATABASE INDX(AR) CLIENT '002' ID 'TEST'
               TO WA_INDX.
Addition 4
... USING form
Note
This statement is for internal use only.
Incompatible changes or further developments may occur at any time without warning or notice.
Effect
Does not read the data from the database. Instead, calls the FORM routine form for each record read from the database without this addition. This routine can take the data key of the data to be retrieved from the database table work area and write the retrieved data to this work area. The name of the routine has the format <name of database table>_<name of form>; it has one parameter which describes the operation (READ, UPDATE or INSERT). The routine must set the field SY-SUBRC in order to show whether the function was successfully performed.
Addition 5
... TO wa (after key or after dbtab(ar))
Effect
You need to use this addition if you want to save user data fields in the cluster database and then read from there. The system uses the work area wa instead of a table work area. The target area entered must have the same structure as the table dbtab.
Example
DATA WA LIKE INDX.
DATA F1.
IMPORT F1 = F1 FROM DATABASE INDX(AR)
               CLIENT '002' ID 'TEST'
               TO WA.
WRITE: / 'AEDAT:', WA-AEDAT,
       / 'USERA:', WA-USERA,
       / 'PGMID:', WA-PGMID.
Addition 6
... MAJOR-ID id1 (instead of the ID key).
Addition 7
... MINOR-ID id2 (with MAJOR-ID id1)
This addition is not allowed in an ABAP Objects context. See Cannot Use Generic Identification.
Effect
Searches for a record the first part of whose ID (length of id1) matches id1 and whose second part - if MINOR-ID id2 is also declared - is greater than or equal to id2.
Addition 8
... ACCEPTING PADDING
Effect
This addition allows you to append new fields to the end of structures, sub-structures, and internal tables. The IMPORT statement fills the additional fields with initial values; make existing fields (C, N, X, P, I1, and I2) longer; map character-type fields to STRING-type fields; or to map byte-type fields to XSTRING-type fields.
Addition 9
... ACCEPTING TRUNCATION
Effect
This addition allows you to shorten the last CHAR fields, or to omit the last component at the top level. (Until Release 4.6, you could do this without using an addition).
Addition 10
... IGNORING STRUCTURE BOUNDARIES
Effect
This addition means that only the fragment sequence is relevant - that is, that any sub-structures match. If you use this addition, the system ignores any alignment changes necessitated by Unicode - such as inserting named includes.
You cannot use this addition with either addition 8 (enlarge structure) or addition 9 (shorten structure), since it specifies that structure and include boundaries are to be ignored.
From Release 6.10 onwards, the include information is stored in datasets, so that the system can also check that includes match - that is, that sub-structures and includes (named or unnamed) are treated equally. When data is imported in a Release prior to 6.10, includes are not checked.
Addition 11
...IGNORING CONVERSION ERRORS
Effect
This addition prevents the system from triggering a runtime error, if an error occurs when the character set is converted. '#' is used as a replacement character.
Addition 12
... REPLACEMENT CHARACTER c
Effect
The replacement character is used if a particular character cannot be converted when the character set is converted. If you do not use this addition, '#' is used as a replacement character.
This addition can only be used in conjunction with addition 11.
Addition 13
... IN CHAR-TO-HEX MODE
Effect
All character-type fields are not converted. To convert a field, you must create a field (or structure) that is identical to the exported field or structure, except that all its character-type components must be replaced with hexadecimal fields.
You can only use this addition in Unicode programs, to allow you to import camouflaged binary data as single-byte characters. Moreover, you cannot use this addition in conjunction with the additions 8, 9, 10, 11, and 12.
Addition 14
... CODE PAGE INTO f1
Effect
The code page of the exported data is stored in the character-type field f1 - for example, to analyze data that has been imported with the IN CHAR-TO-HEX MODE addition.
Addition 15
... ENDIAN INTO f2
Effect
The byte order(LITTLE or BIG) of the exported data is stored in the field f2 - for example, to analyze data that has been imported with the IN CHAR-TO-HEX MODE addition. The field f2 must have the type ABAP_ENDIAN, which is defined in the type group ABAP. For this reason, the type group ABAP must be included in the ABAP program using a TYPE-POOLS statement.
Variant 7
IMPORT obj1 ... objn FROM DATASET dsn(ar) ID key.
This variant is not allowed in an ABAP Objects context. See Cannot Use Clusters in Files
Note
This variant is no longer supported and cannot be used.
Variant 8
IMPORT obj1 ... objn FROM LOGFILE ID key.
Note
This statement is for internal use only.
Incompatible changes or further developments may occur at any time without warning or notice.
Extras:
1. ... = f (for each field f to be imported) 2. ... TO f (for each field f to be imported)
The syntax check performed in an ABAP Objects context is stricter than in other ABAP areas. See Cannot Use Implicit Field Names in Clusters
Effect
Imports data objects (fields, field strings or internal tables) from the update data. You must specify the update key assigned by the system (with current request number) as the key.
The key, key, must be a character-type data object (but not a string).
The Return Code is set as follows:
SY-SUBRC = 0:
The existing data objects in the data cluster specified were imported. The rest remain unchanged (in some circumstances, this may mean that no data objects were imported).
SY-SUBRC = 4:
The data objects could not be imported. An incorrect ID may have been used.
The contents of all objects remain unchanged.
Addition 1
... = f (for each object to be imported)
Addition 2
... TO f (for each object to be imported)
Effect
The object is placed in field f.
Variant 9
IMPORT DIRECTORY INTO itab FROM DATABASE dbtab(ar) ID key.
Extras:
1. ... CLIENT g (after dbtab(ar)) 2. ... TO wa (last addition or after dbtab(ar))
The syntax check performed in an ABAP Objects context is stricter than in other ABAP areas. See Cannot Use Table Work Areas.
Effect
Imports an object directory stored under the specified ID with EXPORT TO DATABASE into the table itab. The internal table itab may not have the type HASHED TABLE or ANY TABLE.
The key, key, must be a character-type data object (but not a string).
The Return Code is set as follows:
SY-SUBRC = 0:
The directory was successfully imported.
SY-SUBRC = 4:
The directory could not be imported, probably because an incorrect ID was used.
The internal table itab must have the same structure as the Dictionary structure CDIR (INCLUDE STRUCTURE).
Addition 1
... CLIENT g (before ID key)
Effect
Takes data from the client g (only with client-specific import/export databases). Client g must be a character-type data object (but not a string).
Addition 2
... TO wa (last addition or after dbtab(ar))
Effect
Uses the work area wa instead of the table work area. When you use this addition, you do not need to declare the table dbtab, named after DATABASE using a TABLES statement. The work area entered must have the same structure as the table dbtab.
Example
Directory of a cluster consisting of two fields and an internal table:
TYPES: BEGIN OF TAB3_LINE,
         CONT(4),
       END OF TAB3_LINE,
       BEGIN OF DIRTAB_LINE.
         INCLUDE STRUCTURE CDIR.
TYPES END OF DIRTAB_LINE.
DATA: INDXKEY LIKE INDX-SRTFD,
      F1(4),
      F2(8)   TYPE P decimals 0,
      TAB3    TYPE STANDARD TABLE OF TAB3_LINE,
      DIRTAB TYPE STANDARD TABLE OF DIRTAB_LINE,
      INDX_WA TYPE INDX.
INDXKEY = 'INDXKEY'.
EXPORT F1 = F1
       F2 = F2
       TAB3 = TAB3
       TO DATABASE INDX(ST) ID INDXKEY " TAB3 has 17 entries
       FROM INDX_WA.
IMPORT DIRECTORY INTO DIRTAB FROM DATABASE INDX(ST) ID INDXKEY
       TO INDX_WA.
Then, the table DIRTAB contains the following:
NAME     OTYPE FTYPE TFILL FLENG
F1         F      C      0      4
F2         F      P      0      8
TAB3       T      C      17     4
The meaning of the individual fields is as follows:
NAME:
Name of stored object
OTYPE:
Object type (F: Field, R: Field string / Dictionary struc

I m not able to create xml file in Java Project

hi all,
I have created one java project just to try with Ant Builder. I have created one class inside it. and now i m creating an XML file inside that project.
But as soon as i try to create the File -> New -> File and give the .xml extention of the file this gives error into the project.
Will you suggest me the solution for that?
Thanks in advance.

Assuming that you are facing this problem in NDS, here is the solution.
Go to Windows--> Preferences --> WorkBench -->File Associations
In the File Types list select *.xml
This will display the default associated XML editor as
XML Editor(default) in the bottom list box.
Click on add button near the bottom list box and select Text Editor, click Ok.You will see one more entry in the list box as "Text Editor".
Select this entry and click on the default button.
Click Ok and close the preferences dialogue.
Now create a new xml file.You wont see the error this time.
Please note that this will treat all simple xml files you will create as TEXT Files and always open with Text Editor.You can override this behaviour with right click on the file and select appropriate editor from the "Open With" context menu.
The error you are talking about is because the XML editor tries to check well-formedness and basic syntax rules for the file that you newly created, actually is a noce feature of the IDE.
Rgds,
Amol

Function module to check if a file is already open

Hi All,
Could any one of you tell me a function module which checks whether a given file on the application server is currently being open or not.
Regards
Amit Mishra

Amit,
Try GET DATASET.
Basic form
GET DATASET dsn.
Extras:
1. ... POSITION pos
2. ... ATTRIBUTES attr
In some cases, the syntax rules that apply to Unicode programs are different than those for non-Unicode programs. For details, see File Interface.
Effect
Used to get the properties of a file already open.
You can use this statement without additions to determine whether the file is open.
If the file is not open, an exception of the type CX_SY_FILE_OPEN_MODE is triggered.
Regards,
Rao A
Message was edited by: Rao Arimilli

How to know whether the file is opened or not

Hi All,
In the file handling,
Before writing OPEN DATA SET, I want to know the file is already opened or not.
Please help me out in this regard.
Thanks and regards,
Mallareddy

Hi,
Please try GET DATASET statement.
Syntax:
GET DATASET dsn.
Extras:
1. ... POSITION pos
2. ... ATTRIBUTES attr
In some cases, the syntax rules that apply to Unicode programs are different than those for non-Unicode programs. For details, see File Interface.
Effect
Used to get the properties of a file already open.
You can use this statement without additions to determine whether the file is open.
If the file is not open, an exception of the type CX_SY_FILE_OPEN_MODE is triggered.
Regards,
Ferry Lianto

Reading foxpro dbf files from forms6i

hi all,
can anyone tell me how can i read a dbf file and access data from that.
Thanks
Uday

Exec_Sql Package allows you to acess non Oracle Database
You will have to follow following steps as follows:-
1-First Find OCA.PLL and EXEC_SQL.PLL libraray.
2-Attach Both libraries to ur concerned Forms.
3-Create VFP odbc driver.
3-Create a Button to write follwing codes on WHEN-BUTTON-PRESSED trigger or u can write
these code on any Trigger as you required.
Decalre
conidodbc exec_sql.conntype;
B varchar2(100);
C varchar2(100);
curid exec_sql.cyrstype;
sqlstr varchar2(1000);
nres pls_integer;
Begin
--This exec_sql.open_connection Procedure connect your
--non Oracle Database through ODBC Driver
coniidodbc:=exec_sql.open_connection
('scott/tiger@odbc:yourodbcdivername');
--exec_sql.opne_cursor return the curid of your non
--Oracle Database
curid:=exec_sql.opne_cursor(conidodbc);
--It is Your non Oracle Database Statement follow there
--Syntax rule of your non Oracle Database Syntax
sqlstr:='Select A from yourdbffilename ';
--exec_sql.Parse procedure parse your Stement to non
--Oracle Database
exec_sql.Parse(connidodbc,curid,sqlstr,exec_sql.V7);
--After succesful Parsing it Executes your Ststment
nres:=exec_sql.execute(conidodbc,curid);
--exec_sql.Define column mapping for your local
--variable to Non Oracle Database Column
exec_sql.Define column (conidodbc,curid,B,30);
while (Exec_Sql.fetch_rows(conidodbc,curid)>0)
loop
--Exec_Sql.column_value intiliaze your Non Oracle
--Database to your Local Variable
Exec_Sql.column_value (conidodbc,curid,1,B);
C:=B;
message('C value '||C);
end loop;
End;
--Rest Explanation About Exec_Sql Package Find Help in
--You Forms Still If any Problem then add me on MSN my id
--is [email protected] may be I can help you more
Thanks
Khurram Siddiqui

Seeburger syntax rules

Similar Messages

Maybe you are looking for