sapdev logo background
sapdev logo sapdev logo
Comments

SAP OO OBS CLUSTER WA 1 documentation, setup help and example usage



Return to SAP documentation index


INCLUDE
ARTICLE

No Use of Table Work Areas

If user data fields are to be transported to or from cluster databases or the cross-transaction application buffer, the addition FROM|TO wa
must be specified with the statements EXPORT/IMPORT ... TO/FROM DATABASE/SHARED BUFFER in ABAP Objects.

  • The following cannot be used in ABAP Objects:


  • dbtab-... = ...

    EXPORT ... TO DATABASE dbtab(ar) ID id.
    EXPORT ... TO SHARED BUFFER dbtab(ar) ID id.

    IMPORT ... FROM DATABASE dbtab(ar) ID id.
    IMPORT ... FROM SHARED BUFFER dbtab(ar) ID id.

    ... = dbtab-
  • Correct syntax:


  • DATA wa TYPE dbtab .

    wa-... = ...

    EXPORT ... TO DATABASE dbtab(ar) ID id FROM wa.
    EXPORT ... TO SHARED BUFFER dbtab(ar) ID id FROM wa.

    IMPORT ... FROM DATABASE dbtab(ar) ID id TO wa.
    IMPORT ... FROM SHARED BUFFER dbtab(ar) ID id TO wa.

    ... = wa-...
  • Reason:


  • If the addition FROM|TO wa is not specified, the system tries to transport the user data fields of the table work area declared by
    TABLES . If the table work area is not found, the user data fields are not transported. A table work area can be declared in the main program of local classes; however, it should not be used. In global classes the table work area cannot be used at all.
    Documentation extract taken from SAP system, � Copyright SAP AG. All rights reserved




    OO_OBS_CLUSTER_NAMES_1
    OO_OBS_COMMON_1




    comments powered by Disqus