SAP Library - Find your answers

How to test the sending of documents from R/3 applications via fax, paging or Internet mail?

What are the system requirements? What do you have to configure?

The sending of documents via external communications services like fax, paging (radio call services, SMS), Internet mail, X.400, and so on is carried out with the components SAPoffice and SAPconnect. For an 'actual' sending via the corresponding communications services you still need R/3-external additional components ("SAPconnect node") which are delivered either by SAP (for example SAP Internet Mail Gateway or SAP Exchange Connector) or by external manufacturers (for example, fax servers).

 . . . . . . . . . . . . . . . . .
.                               .
.   R/3                         .
.                               .
.   +----------------------+    .
.   !      Application     !    .
.   +----------------------+    .
.              |                .
.              |    <------- Business Communication Interface
.              v                .
.   +----------------------+    .
.   !      SAPoffice       !    .
.   +----------------------+    .
.              |                .
.              |    <------- SAPoffice/SAPconnect send queue
.              v                .
.   +----------------------+    .
.   !      SAPconnect      !    .
.   +----------------------+    .
.              |                .
. . . . . . . .|. . . . . . . . .
               |
               |    <------- RFC Interface BC-CON
               v
    +----------------------+
    ! Communication system !
    ! ="SAPconnect node"   !
    +----------------------+
               |
               v
      Data transfer network

1. 'Actual' test
Documents are actually transferred via the communications services. Precondition is the installation of an external communication system and its connection to the data transfer networks (telephone line, Intra/Internet...).
This way, the documents can be transferred to any participant of the corresponding communications service (fax machines, mailboxes...).

2. 'Loop-back' test
The documents are returned here to the own R/3 System which functions like a SAPconnect node and are stored in the SAPoffice inbox of an R/3 user. The operation of an external communications system is nonrequired in this case.
In general, all points relevant for application can be checked during this test: Contents and structure of the documents, entry of sender and receiver addresses, format of the documents for transmission, handling of status confirmations and so on

 . . . . . . . . . . . . . . . . .
.                               .
.   +-------------+             .
.   ! Application !             .
.   +-------------+             .
.         |                     .
.         v                     .
.   +-------------+--------+    .
.   !  SAPoffice  ! Inbox  !    .
.   +-------------+--------+    .
.         |           ^         .
.         v           |         .
.   +----------------------+    .
.   !      SAPconnect      !    .
.   +----------------------+    .
.         |           ^         .
. . . . . | . . . . . | . . . . .
          |           |
          \___________/

1. 'Actual' test
Contact the R/3 System administration to set up the R/3-external infrastructure necessary for the required communication service and to carry out the R/3 internal configuration.

2. 'Loop-back' test

a) Address management
All R/3 users who want to send documents via a communication service need an address of the respective communication service type which is used as a sender specification.
All users also need an address of this type to receive documents in the R/3 System via a communications service and under which they are attainable as receivers.
If documents are to be sent to the own R/3 user during the loop-back test, a single address of the corresponding communication service suffices for this user. This is then used both as sender and as receiver specification.

Create addresses
The address maintenance of R/3 users is carried out either via the R/3 User Maintenance (Transaction SU01) or the Private office settings (Transaction SO12):
Address --> Other communication...
Selection of the required communication service.
Enter address.
Copy or save.

b) Configuration of SAPconnect (Transaction SCOT)
Set communication method
4.0 + 4.5: Goto --> Customizing --> Communication methods
as of 4.6: Settings --> Communication methods
Set the method of the required communication service to the value 'SAPCONNECT' and save the setting.

Create node
View --> Nodes, node --> Create
Nodes = for example system name/client "ALR003"
For example, Description = "ALR client R/3 System 003"
RFC destination = 'NONE'
Address type = Selection of the required communication service.
Address area = for example '*'
Format = 'PDF' for fax, 'RAW' for paging and Internet mail
Device type = 'POST2' for fax, 'ASCIPRI' for paging and Internet mail
Restrict send time = do not flag
Country = 'DE' (only for fax)
Flag Node-specific fax number changes... = (only for fax)
Enter two entries in the table: (only for fax)
Begin. no Substitute Comment
-----------------------------------
00 + foreign country
0 +49 home country
Set further address type = 'no'
Maximum waiting time... = enter nothing
Node can resolve path references = do not flag
Node is to be monitored by the alert monitor = do not flag
Node in use = mark

Schedule send process
View --> Jobs, job --> Dispatch
Job name = for example 'SAPconnect'
--> place cursor on variant SAP&CONNECTALL Schedule job (F6)
Schedule periodically, for example 5 minutes.

After sending a document from an R/3 application this is displayed in the outbox of the sender (if requested SAPoffice interface). After the next SAPconnect transmission process (according to the period chosen when scheduling the job) the document is displayed in the inbox of the receiver.

What are the system requirements? What do you have to configure?

The sending of documents via external communications services like fax, paging (radio call services, SMS), Internet mail, X.400, and so on is carried out with the components SAPoffice and SAPconnect. For an 'actual' sending via the corresponding communications services you still need R/3-external additional components ("SAPconnect node") which are delivered either by SAP (for example SAP Internet Mail Gateway or SAP Exchange Connector) or by external manufacturers (for example, fax servers).

 . . . . . . . . . . . . . . . . .
.                               .
.   R/3                         .
.                               .
.   +----------------------+    .
.   !      Application     !    .
.   +----------------------+    .
.              |                .
.              |    <------- Business Communication Interface  .              v                .  .   +----------------------+    .  .   !      SAPoffice       !    .  .   +----------------------+    .  .              |                .  .              |    <------- SAPoffice/SAPconnect send queue  .              v                .  .   +----------------------+    .  .   !      SAPconnect      !    .  .   +----------------------+    .  .              |                .  . . . . . . . .|. . . . . . . . .                 |                 |    <------- RFC Interface BC-CON                 v      +----------------------+      ! Communication system !      ! ="SAPconnect node"   !      +----------------------+                 |                 v        Data transfer network  

1. 'Actual' test
Documents are actually transferred via the communications services. Precondition is the installation of an external communication system and its connection to the data transfer networks (telephone line, Intra/Internet...).
This way, the documents can be transferred to any participant of the corresponding communications service (fax machines, mailboxes...).

2. 'Loop-back' test
The documents are returned here to the own R/3 System which functions like a SAPconnect node and are stored in the SAPoffice inbox of an R/3 user. The operation of an external communications system is nonrequired in this case.
In general, all points relevant for application can be checked during this test: Contents and structure of the documents, entry of sender and receiver addresses, format of the documents for transmission, handling of status confirmations and so on

 . . . . . . . . . . . . . . . . .
.                               .
.   +-------------+             .
.   ! Application !             .
.   +-------------+             .
.         |                     .
.         v                     .
.   +-------------+--------+    .
.   !  SAPoffice  ! Inbox  !    .
.   +-------------+--------+    .
.         |           ^         .
.         v           |         .
.   +----------------------+    .
.   !      SAPconnect      !    .
.   +----------------------+    .
.         |           ^         .
. . . . . | . . . . . | . . . . .
         |           |
         \___________/

1. 'Actual' test
Contact the R/3 System administration to set up the R/3-external infrastructure necessary for the required communication service and to carry out the R/3 internal configuration.

2. 'Loop-back' test

a) Address management
All R/3 users who want to send documents via a communication service need an address of the respective communication service type which is used as a sender specification.
All users also need an address of this type to receive documents in the R/3 System via a communications service and under which they are attainable as receivers.
If documents are to be sent to the own R/3 user during the loop-back test, a single address of the corresponding communication service suffices for this user. This is then used both as sender and as receiver specification.

Create addresses
The address maintenance of R/3 users is carried out either via the R/3 User Maintenance (Transaction SU01) or the Private office settings (Transaction SO12):
Address --> Other communication...
Selection of the required communication service.
Enter address.
Copy or save.

b) Configuration of SAPconnect (Transaction SCOT)
Set communication method
4.0 + 4.5: Goto --> Customizing --> Communication methods
as of 4.6: Settings --> Communication methods
Set the method of the required communication service to the value 'SAPCONNECT' and save the setting.

Create node
View --> Nodes, node --> Create
Nodes = for example system name/client "ALR003"
For example, Description = "ALR client R/3 System 003"
RFC destination = 'NONE'
Address type = Selection of the required communication service.
Address area = for example '*'
Format = 'PDF' for fax, 'RAW' for paging and Internet mail
Device type = 'POST2' for fax, 'ASCIPRI' for paging and Internet mail
Restrict send time = do not flag
Country = 'DE' (only for fax)
Flag Node-specific fax number changes... = (only for fax)
Enter two entries in the table: (only for fax)
Begin. no Substitute Comment
-----------------------------------
00 + foreign country
0 +49 home country
Set further address type = 'no'
Maximum waiting time... = enter nothing
Node can resolve path references = do not flag
Node is to be monitored by the alert monitor = do not flag
Node in use = mark

Schedule send process
View --> Jobs, job --> Dispatch
Job name = for example 'SAPconnect'
--> place cursor on variant SAP&CONNECTALL Schedule job (F6)
Schedule periodically, for example 5 minutes.

After sending a document from an R/3 application this is displayed in the outbox of the sender (if requested SAPoffice interface). After the next SAPconnect transmission process (according to the period chosen when scheduling the job) the document is displayed in the inbox of the receiver.

Follow the steps to print SAP R/3 documents using printer attached on Linux PC:-


SAPGUI for Java should be installed on my Linux. We can’t use Frontend Printing (F acces method) since there was no SAPLPD program on it.

The SAPLPD package on SAPGUI for Windows is duplicate Linux’s LPD flow. It is using same architecture and working method. Since Linux already had it LPD (and CUPS), it doesn’t need SAPLPD anymore. You can use LPD (and CUPS) to replace SAPLPD function.

SAPGUI for Java on Linux can use U : Print Using Berkeley Protocol acces method. Fill the Host printer column with name of your printer defined on your Linux PC. Use simple name and no space. On Destination host, fill with IP address of your Linux PC where your printer attached.

After that, open your inetd.conf file and add this at the end of lines.

printer stream tcp nowait lp /usr/lib/cups/daemon/cups-lpd cups-lpdand you need to restart your inetd daemon or reboot your PC.

If you are using xinetd.conf, please add this at the end of lines.

service printer { socket_type = stream protocol = tcp wait = no user = lp server = /usr/lib/cups/daemon/cups-lpd }Restart your xinetd daemon.

Before you print your SAP R/3 documents, please make sure your LPD (and/or CUPS ) daemon is running well.

When we do a Client Copy we often here that Changed Documents are not copied to the new client.

Changed Documents:- Change documents are nothing but history of changes made in the client. Example change data in Material Master, changes to Purchase Req (PR), Purch Orders, Contracts, Sales Orders, and many more

Changes to a lot of SAP documents are stored in table CDHDR and table CDPOS.

SAP recordes every changes of any data in the database. which is called change documents.

From Basis Point of View, e.g. if we create a role and after that what ever changes made to that role, all the changes are recorded in the database. The changes recorded in the database is called change documents in terms of client copy.

Even if we copy a client by the profile SAP_ALL the change documents are not copied.

CDHDR Change document header
CDPOS Change document items
JCDS Change documents for System/User statuses (Changes to table JEST)

Function modules

Tables CDHDR and CDPOS can be read with functionmodules

CHANGEDOCUMENT_READ_POSITIONS
CHANGEDOCUMENT_READ_HEADERS

Note

Procedure

If you want to use applicant lists to display documents stored for an applicant, proceed as follows.

1. On the SAP R/3 System screen, choose Human resources
® Personnel management ® Recruitment, and then Reporting ® Report selection.

This accesses the Report Tree: Initial Screen.

2. Enter the required report tree and choose Report tree ® Display.

This takes you to the Display Report Tree screen.

3. Place the cursor on the Personnel Management sub-tree and choose Edit ® Expand sub-tree.

You can also save the Recruitment sub-tree as your initial screen. To do this, place the cursor on Recruitment and choose Edit ® Set focus. Then choose Settings ® Define initial position. The next time you access the report tree for Personnel Management, the Recruitment sub-tree is displayed immediately.

4. Underneath Recruitment, select Applicants and choose Nodes ® Execute.
5. Place the cursor on the report that you require and choose Nodes ® Execute.

This takes you to the initial screen of the chosen report.

6. Enter your selection criteria, if necessary, and choose Program ® Execute.

The system displays a list of applicants who meet the selection criteria.

7. Place the cursor on the applicant whose documents you want to display and choose Environment
® Display facsimiles.

The system displays a list of all documents stored for the applicant.

8. Select the required document types and choose Display facsimiles.

Result

Procedure

If you want to display all of the documents stored for an applicant, proceed as follows.

1. On the SAP R/3 System screen, choose Human resources
® Personnel management ® Recruitment, and then Appl. master data ® Display.

This takes you to the Display Applicant Master Data screen.

2. Enter an applicant number.
3. Choose Extras
® Display all facsimiles.

The system displays a list of all documents stored for the applicant you specified.

4. Select the required document types and choose Display facsimiles.

Result

Keyword: SAP HR
Title : AS-IS Phase, AS IS Documents