The error says :

Please enter an address number
Communication type  cannot be used

This error is because of the print program (used in output type) the three fields listed were not populated.
addr_key-addrnumber, addr_key-persnumber, and addr_key-addr_type.

Below is the call function where these 3 fields need to be exported. Please try putting values in debug mode and it should work.

CALL FUNCTION ‘ADDR_GET_NEXT_COMM_TYPE‘
EXPORTING
strategy = nast-tcode
address_number = addr_key-addrnumber
person_number = addr_key-persnumber
IMPORTING
comm_type = lvs_comm_type
comm_values = lvs_comm_values

The values for the 3 fields are in addr_key table.

Lets see an example for the same, where different function module is used ( at the time of Billing).

vbco3-mandt = sy-mandt.
vbco3-spras = nast-spras.
vbco3-kunde = nast-parnr.
vbco3-parvw = nast-parvw.

CALL FUNCTION ’RV_BILLING_PRINT_VIEW‘
EXPORTING
comwa                        = vbco3
IMPORTING
kopf                         = vbdkr
TABLES
pos                          = tvbdpr
EXCEPTIONS
terms_of_payment_not_in_t052 = 1
error_message                = 5
OTHERS                       = 4.
IF NOT sy-subrc IS INITIAL.
IF sy-subrc = 1.
syst-msgty = ’I’.
PERFORM protocol_update.
ENDIF.
ENDIF.

* fill address key –> necessary for emails
ADDR_KEY-ADDRNUMBER = vbdkr-ADRNR.
ADDR_KEY-PERSNUMBER = vbdkr-ADRNP.
ADDR_KEY-ADDR_TYPE  = vbdkr-ADDRESS_TYPE.

You might also be interested in these posts:

1. ABAP Automailer program for sending output of SAP TCodes in Background
2. ABAP Editor: Create custom Pattern
3. Catch the Dump in ABAP – I

For the same purpose, we can use SCC1 Tcode.  SCC1 T-Code u can do the transport in same R/3 System but different client like

Source : 100(DEV)
Target-1 : 200 (QAS)
Target-2: 300 (PRD)

SCC1 Just specify Source Client and the Request number and import the request.
In this process u don’t have to release the transport request.

You might also be interested in these posts:

1. Transport SAP Table contents
2. Downloading PF-Status(GUI Status) in SAP
3. Tcodes in SAP – Part 1

The following file describes folowing SAPScript Forms Components in details:

• Header data
• Page layout
• Paragraph formats
• Character formats
• Documentation
• Text Elements
• Print Program
• Control Commands
• Symbols
• Formatting Options

Link : SAPScript Forms

You might also be interested in these posts:

1. Advantage Smartform: Migrating SAPScript to Smartforms in SAP
2. Formatting SAPScript / SMARTFORMS in SAP
3. Smartforms Vs SAPScript, the Battle Royale in SAP

SAPScript Formatting

Smartforms Formatting

Following are the few useful formatting options:

Offset

N left-most characters of the symbol value will not be displayed.

If symbol has the value 123456789, the following will be displayed:

&symbol& -> 123456789

&symbol+3& -> 456789

&symbol+7& -> 89

&symbol+12& ->

&symbol+0& -> 123456789

Output Length

to define how many character positions should be copied from the value.

If symbol has the value 123456789.

&symbol(3)& -> 123

&symbol(7)& -> 1234567

The SYST-UNAME field contains the logon name of a user called Einstein. The

Dictionary entry for this field contains an output length of 12.

&SYST-UNAME&… -> Einstein…

&SYST-UNAME(9)&… -> Einstein …

&SYST-UNAME(*)&… -> Einstein …

Omitting the Leading Sign

The S option can be used to ensure that the value is formatted without the sign.

The ITCDP-TDULPOS field contains the value -100.00. The ABAP/4 Dictionary

definition for this field includes a leading sign.

&ITCDP-TDULPOS& -> 100.00-

&ITCDP-TDULPOS(S)& -> 100.00

Leading Sign to the Left

This option enables you to specify that the leading sign should be placed to the left of the number.

&ITCDP-TDULPOS& -> 100.00-

&ITCDP-TDULPOS(<)& -> -100.00

Leading Sign to the Right

If you used the SET SIGN LEFT control command to specify that the leading sign should be output before the value, this specification can be overridden for individual symbols to enable these to be output with the leading sign to the right.

Syntax:

&symbol(>)&

Omitting Leading Zeros

Certain symbol values are output with leading zeros. If you wish to suppress these, you may do so with the Z option.

Assuming the current date is 1.1.1994, &DAY& -> 01

&DAY(Z)& -> 1

Space Compression

The C option has the effect of replacing each string of space characters with a single space and shifting the ’words’ to the left as necessary to close up the gaps.

Assuming ‘ Albert Einstein ‘ is the symbol value,

&symbol& -> Albert Einstein

&symbol(C)& -> Albert Einstein

Number of Decimal Places

A program symbol of one of the data types DEC, QUAN and FLTP can contain decimal place data. This option is used to override the Dictionary definition for the number of decimal places for the formatting of this symbol value.

The EKPO-MENGE field contains the value 1234.56. The Dictionary definition specifies 3 decimal places and an output length of 17.

&EKPO-MENGE& -> 1,234.560

&EKPO-MENGE(.1) -> 1,234.6

&EKPO-MENGE&(.4) -> 1,234.5600

&EKPO-MENGE&(.0) -> 1,235

Specifying an Exponent for Floating Point Numbers

The way that a floating point number is formatted depends on whether an exponent is specified.

PLMK-SOLLWERT field is assumed to have the value

123456.78 and to be of data type FLTP.

&PLMK-SOLLWERT& -> +1.23456780000000E+05

&PLMK-SOLLWERT(E3)& -> +123.456780000000E+03

&PLMK-SOLLWERT(E6)& -> +0.12345678000000E+06

&PLMK-SOLLWERT(E0)& -> +123456.780000000

&PLMK-SOLLWERT(E)& -> +123456.780000000

Right-Justified Output

Right-justified formatting can be specified with the R option. This option has to be used in conjunction with an output length specification. If symbol has the value 1234.

&symbol& -> 1234

&symbol(8R) -> 1234

Fill Characters

Leading spaces in a value can be replaced with a fill character.

The figure for customer sales in the KNA1-UMSAT field is $700. The Dictionary description of the field specifies an output length 8.

&KNA1-UMSAT& -> 700.00

&KNA1-UMSAT(F*)& -> **700.00

&KNA1-UMSAT(F0)& -> 00700.00

Suppress Output of Initial Value

The I option can be used to suppress the output of symbols which still contain their initial value.

Assuming KNA1-UMSAT contains the value 0 and the currency is DEM.

&KNA1-UMSAT& -> 0,00

&KNA1-UMSAT(I)& ->

If the field contains an amount other than 0, this value will be output in the normal way.

&KNA1-UMSAT& -> 700,00

&KNA1-UMSAT(I)& -> 700,00

Ignore Conversion Routines

SAPscript conversion routines specified in the Dictionary are automatically recognized and used when program symbols are being formatted. Using the K option can prevent these conversions.

Date Mask

The formatting for date fields can be defined with the SAPscript SET DATE MASK command. Executing this command causes all subsequent date fields to be output using the specified formatting.

/: SET DATE MASK = ‘date_mask’

The following templates may be used in the date mask:

DD day (two digits)

DDD name of day (abbreviated)

DDDD name of day (written out in full)

MM month (two digits)

MMM name of month (abbreviated)

MMMM name of month (written out in full)

YY year (two digits)

YYYY year (four digits)

LD day (formatted as for the L option)

LM month (formatted as for the L option)

LY year (formatted as for the L option)

Time Mask

You can use the SAPscript SET TIME MASK command to format time fields in a way that differs from the standard setting.

Assuming the current time is 10:08:12.

&TIME& -> 10:08:12

/: SET TIME MASK = ‘HH:MM’

&TIME& -> 10:08

/: SET TIME MASK = ‘HH hours MM minutes’

&TIME& -> 10 hours 08 minutes

&TIME(Z)& -> 10 hours 8 minutes

Other Standard Outputs:

&DAY&, &MONTH&, &YEAR&, &HOURS&, &MINUTES&, &SECONDS&, &DATE&, &TIME&, &PAGE&, &NEXTPAGE&.

You might also be interested in these posts:

1. Debugging Smartforms and SAPScript in ABAP
2. Smartforms Vs SAPScript, the Battle Royale in SAP
3. Advantage Smartform: Migrating SAPScript to Smartforms in SAP

Lets look at the steps for each debegging options.

1)  DEBUG Smartforms

a) Use T-Code SFTRACE – Using the Smart Form trace, you can trace how a Smart Form was processed during printing. You can then see, for example, the sequence in which the nodes were run or the point at which processing terminated due to an error.

b) Hardcode the BREAK-POINT: We just have to put the BREAK-POINT statement whereever we want to stop the code and look inside in Debugger.

c) Breakpoint using BREAK user-name: We can put the break point using the statment user name addition to the break command, for example BREAK NAVEEN. These break points would not stop any other users who would run this Smartform.

d) Breakpoint on the fly: To put a break point on the fly, we can follow these simple steps to put a breakpoint as required.

Step1: Open your Smartform and Copy the text as which you want to put a break point and press the Test Button. It will bring you the Function Builder.

Step 2: Press the display button to open the code of the function.

Step 3: Press the Find (control+F) button.

Step 4: In the find screen, paste the copied text (control+V) in the Text.
Select the option “In main Program”
Press Enter

Step 5: From the hit list, go to the source code by doing doubleclick on the search results. Now, put a Cursor on the line and press the “Set Breakpoint” button.

That’s it. So, when you run the application it will stop to this break point.

2). DEBUG SAPScript

They are two ways to debug the SAPScript.

a). Use Tools – > Word Processing – > Layout Set (SE71). Enter name of layout set and then Utilities – > Activate Debugger.

It is of no consequence which layoutset you enter when selecting the SAPscript debugger. (Menu path: Tools – > Wordprocessing – > Forms, Utilities – > Activate Debugger) The next layoutset called will invoke the debugger.

b). Another way to set the SAPScript debugger is to run program RSTXDBUG.

When you debug Print program it is same as you debug any other ABAP program. While when you debug SAPScript, you actually debug the code ( scripting) you have written SAPScript Form.

You might also be interested in these posts:

1. Advantage Smartform: Migrating SAPScript to Smartforms in SAP
2. Smartforms Vs SAPScript, the Battle Royale in SAP
3. Debugging RFC functions in SAP