Ansicht
Dokumentation

SIMG_ISHCM_GD_SEND - Explain Message Dispatch Customizing

RFUMSV00 - Advance Return for Tax on Sales/Purchases   General Material Data  
This documentation is copyright by SAP AG.

This documentation describes how a non-SAP system is connected to IS-HCM normal dispatch from the perspective of the SAP IS-H system. It basically comprises a list of the necessary Customizing steps.

1. Install the HCM transceiver on the non-SAP system

The HCM transceiver is a program package that is used by SAP. It has to be installed in the local area network in such a way that it can be accessed from the SAP gateway. Usually the transceiver is installed on the computer on which the application to be connected is also running.

Should the application use a computer for which SAP cannot (yet) provide a transceiver, an alternative solution has to be found. However, it is important that the transceiver is capable of storing the transfer files in a file system for which both communication partners have write access (here the communications partner on the IS-H side is the SAP gateway).

Caution: when you transfer executable files via FTP, you always have to use binary mode! When transferring all other files (shell scripts, documentation), please use ASCII mode.

Regarding the actual installation: the connection is established via the SAP gateway. This necessitates that the gateway user (usually adm with system Id ) has access to this host (freely definable password).

The file .rhosts should be created in the $HOME directory of the gateway user on this host. In this file, you specify from which host the SAP gateway will establish the connection. Consequently, there is no need to make an entry in the hosts.equiv file. For more information on this procedure, please refer to the documentation on hosts.equiv in your UNIX manual.

If you are installing the transceiver yourself, please proceed as described in the Installation instructions for the SAP CPIC transceiver module for communication with subsystems. You will find this documentation under Installation Instructions for the Transceiver.

The characteristics peculiar to IS-H must be taken into account when installing the transceiver. These are documented under Information on the SAP Communication Module.

1. Maintain number range ISH_NC02 (TNKRS)

Unique numbers are required for dispatch orders and messages ready to send. You have to set up their number ranges. You do this in the IMG activity Define Number Ranges.

1. Activate normal dispatch in the institution (TN00E)

Automatic message dispatch must be active (activated) for the corresponding institution(s). This requires you to have maintained institution-specific basic control.

Attention: when using batch input you should consider whether it makes sense to first deactivate automatic message dispatch.

1. Create partner system in the SAP System (TXCOM)

The SAP System has to know the technical data for the partner system. You make this declaration in the IMG activity Maintain TXCOM.

Note

To facilitate the creation of a new partner system you can also use report RNCUTL19. Please refer to the program documentation.

1. Maintain system and system attributes (TN02S)

In this step you specify the logical systems and their attributes. This involves maintaining the corresponding system attributes for a logical system name. This name then represents the partner designation within the IS-H System.

Attention: On no account make changes to (other) existing entries. Always contact the system administrator before deleting entries. In particular, systems of the type R3 or R2 are essential for productive IS-H operation even when no HCM connections are used.

1. Check installation (program RNCCHK01)

You should now execute the installation check. Please take note of any warnings or error messages issued.

1. Set up dispatch control (TNCO1, TNCO2)

You now have to specify which events are to be reported to the partner system(s). These specifications are T H E most important in HCM normal dispatch.

IS-H basically supports the automatic dispatch of particular messages triggered by the corresponding events. These dispatch options are supplied with the standard version and may not be modified.

Dispatch control, i.e. to which partner system and when a message is to be sent, provides two variants:

• variant 1: control independent of the organization unit involved

• variant 2: control dependent on the organizational unit involved

You specify which variant is used for which event/message combination in the IMG activity Dispatch options. If the indicator for organizational unit-related dispatch control (field '0') is set for the corresponding message type, dispatch will be exclusively controlled in this manner.

Here you have to maintain when which message is to be sent to which partner system. To do this, you first have to use dispatch control to determine the correct variant for the corresponding event. Select the maintenance function in relation to the variant:

• dispatch control w/o reference or

• dispatch control with reference to the organizational units
  

1. List settings - extended check (program RNCLST01)

Here you should generate a list of the settings for this system. Please take note of any warnings or error messages issued.

You can archive a hardcopy of this list in order to track subsequent changes to settings.

1. Test dispatch order creation (NC01)

At this point you can and should test whether the specifications you have made do in fact result in the creation of a dispatch order.

To do this, you basically have to trigger the maintained event by branching to the corresponding IS-H transaction. The event occurs when you save.

Note

You simply have to change a comment.

No matter how you created the corresponding dispatch order, this must directly result in (at least) one entry in the dispatch order table NC01.

If you have already scheduled message formatting program RNCBLD00 to run in your system as a periodic background job, this dispatch order will disappear after a certain amount of time. In this case, you have to carry out the NC01 check fairly quickly. Display the table using transaction SE16 (you may have to check several times, since the data might not be inserted synchronously into the database).

If you have not yet set up automatic message formatting, this is a definite advantage as regards testing. It means you can basically follow the various steps. We are not interested in automatic formatting at this stage. In this case, check whether a corresponding entry exists in table NC01.

If there is no entry in table NC01, check the steps you have already worked through.

1. Test message formatting (NC02)

If nothing has been installed yet, you should first generate SAP structures, then generate customer structures.

If errors occur in segments when you generate your customer structures, these relate to your own segment formats. Please refer to the documentation Create customer message formats.

If you have not yet set up automatic message formatting in your system, please go ahead and start RNCBLD00 manually (for instance, via Utilities). The program usually runs without dialog. Upon completion, it reports the number of dispatch orders processed.

Upon completion of the message formatting program, all NC01 entries should have disappeared and new entries should be appended to table NC02. Table NC02 contains the messages ready for dispatch.

To display the processed messages that are ready for dispatch you execute auxiliary program RNCUTL04 (for instance, via Utilities). This program displays all NC02 entries in full. Program RNCUTL21 enables you to display the message content field by field. This facilitates the field check immensely.

Check whether the actual message is correct. Program RNCUTL04 displays each message structured in lines containing 70 characters and blocks of up to 1024 characters. Of particular importance is the header entry with the specification of the message type and its owner code. Was the message formatted in the required format (-> owner code)?

If you have already scheduled message dispatch program RNCSND01 to run as a periodic background job in your system, this message ready for dispatch should disappear after a certain period of time. In this case, data transfer to the non-SAP system would already have completed successfully.

Here again, you have to be fairly quick with the NC02 check. Remember that some time might be required for the data to be inserted into the database.

1. Test message dispatch (NC00)

If you have not yet set up automatic message dispatch in your system, go ahead and start program RNCSND01 manually (for instance, via Utilities). The program usually runs without dialog. Only upon completion does it display how many messages existed and how many were delivered successfully.

Program RNCSND02 can also be used for this. This program works selectively. You can restrict dispatch to one or more receivers.

If an error occurs on the receiving side, the program first attempts to re-establish the connection and transfer the data.

If this fails, the dispatch program discontinues further processing and issues a message accordingly. In background operation, processing is of course not interrupted. The system simply writes a corresponding message into the job log.

Caution: cancelling processing here will result in inconsistent entries in tables NC02 and NC00! This increases the probability of repeated dispatch, not only to the one receiver!

Tip: take note of the error message(s) (F1 provides more detail). Then confirm the message by choosing ENTER, so that the dispatch program can complete processing correctly.

After the message dispatch program has run without errors, all NC02 entries should have disappeared. Of course, if you have run the selective program RNCSND02 this applies only for the selected receivers.

New entries must have been appended to table NC00. This table contains the trace of all messages dispatched successfully (dispatch log file). Select your message(s) in the dispatch log display.

Check whether these are in fact the required messages (outbound message number, target system, dispatch date/time).

If the NC02 entry still exists, please first check whether the Old message indicator is correctly set ('X') in table NC02 for the oldest still existing message to this receiver.

Then check whether the partner system is available. If this is the case, the system supervisor should check the transceiver installation.

Common causes of error:

• SAP gateway connection missing

• wrong/missing path specification in gateway environment

• missing (write) authorization for SAP gateway

• insufficient storage space for creating/appending files

Please refer to the appendix Troubleshooting.

1. Check interface file

When the NC02 entries in the IS-H system have been successfully processed (i.e. dispatched), you should also check the transfer file(s) on the non-SAP system side.

The messages are made available in 4K lines in the interface file on the partner system. In other words, a line in the interface file contains up to 4096 characters. If the message is longer, it is continued in the next line(s). The total length of the message is normally given in the header segment. You find the position in the message segment description.

Display the file(s). Check the number of messages. Take particular note of messages composed of several lines! If you desire, also test appending new messages to still existing interface files.

1. Test transfer to the non-SAP system

You should also make a point of carrying out this test. Have the non-SAP system import the content of the interface file and then delete the interface file. If possible, check the lock mechanism for the interface status file (SS_STAT.dat).

1. Set up periodic formatting/dispatch

This is basically the task of the system administrator. He/she is also responsible for reorganizing the job log file. Reorganization may need to be more frequent if normal dispatch is active (see explanation below).

Before going ahead with your settings, first check that corresponding jobs do not already exist. To do this, branch to the job overview. Here search for jobs whose name starts with ISHCM* regardless of user names. Any jobs you may find must be examined closely. Check whether they have been configured correctly and completely.

If you do not find any ISHCM* jobs, you have to define/create background jobs. In doing so, it is essential to respect the IS-H name conventions

1. Delete old HCM dispatch logs periodically (NC00)

The use of automatic dispatch means that messages are dispatched on an ongoing basis. The date/time of dispatch and the messages themselves(!) are recorded in log file NC00.

Inevitably an ever increasing number of successfully dispatched messages are appended to file NC00. This results in extensive disk space requirements. Finally, dispatch can fail due to the database storage constraints.

The background jobs themselves write many logs which in turn require storage space.

To ensure smooth operation, you should set up background job ISHCM_CLEAR_PROTOCOLS_xxx. This ensures the orderly deletion of old logs.

RFUMSV00 - Advance Return for Tax on Sales/Purchases   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 17525 Date: 20240523 Time: 231442     sap01-206 ( 260 ms )