SAP ABAP IMG Activity ISH_HCM_301_PARTNER (Connect Data Transfer System)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM (Application Component) Customer Relationship Management
     ⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       ⤷ NBAS (Package) Appl. development Hospital System master data, catalogs
IMG Activity
ID ISH_HCM_301_PARTNER Connect Data Transfer System  
Transaction Code S_KK4_74000125   IMG Activity: ISH_HCM_301_PARTNER 
Created on 19990816    
Customizing Attributes ISH_HCM_301_PARTNER   Connect Data Transfer System 
Customizing Activity ISH_HCM_301_PARTNER   Connect Data Transfer System 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name ISH_HCM_301_PARTNER    

Use

In this IMG activity, you make all the specifications for connecting the encryption and transfer system.

Activities

  1. EDI Procedure with File Handling

    You can only use one system of this kind in a given institution. If you use the same transfer system from different institutions or clients, SAP recommends that you separate the data physically (using different directories).

    Work through the following steps:

    • Consider whether and for which direction of data exchange you want to use the all-in-one directory logic.
    • Set up number range ISH_NC301X for the relevant institution and for each EDI procedure used. Here you can use different intervals for different EDI procedures within one institution. You can, however, use the same number range interval for several EDI procedures active within an institution. Set up the number ranges in accordance with the capabilities of the transfer system.
    • If you require a physical sender specification different to that of the procedure standard, enter the required sender identification here. This is at present only possible for Paragraph 301 and Paragraph 302 in Germany. Note that this specification is case-sensitive.
    • Specify the path.
    • Use the same file naming conventions (prefix, sequence number, suffix) as those of the communications server.

      Specify the transfer directory logic:

      The original SAP control comprises one directory per data collection point for outbound files and a separate directory per data collection point for inbound files. You have to specify these directories in the partner agreements with the data collection points.

      Select the directory logic in accordance with the capabilities of the transfer system, or switch over to an all-in-one transfer directory. If you choose to do this, the system places all files to be transmitted to whatever data collection point in, or retrieves these files from this one directory (again distinguished by direction of transfer).

      If you select this all-in-one directory logic, you must also specify the name of the directory. This also requires you to specify a unique file name.

      You can specify the file name according to either of the following conventions:

    • Direct File and Path Name. Here you can specify a file prefix and postfix which together with a configurable number of digits from the sequence number of the file (with regard to this transfer system) make up the file name.
    • Logical file and path name. If you choose this naming convention, you have to set the Log. Name/Path indicator explicitly. The specified file name will then be interpreted as the logical platform-independent file name. In this case, you can make full use of the SAP possibilities for this logical file name. For more information on this type of file handling, see Cross-Client Maintenance of File Names and Paths.

      Note that the following parameters are transferred by the IS-H System to form the physical file name/path definition from the logical name:

    • The current institution for variable <PARAM_1>
    • The sequence number of the file (with regard to this transfer system) for variable <PARAM_2>. The length of this number corresponds to the specified number of digits.
      • Example: The sequence number of the file is 1234567. The number of digits to be used is specified as '3'. The resulting value transferred in the parameter for variable <PARAM_2> is '567'.

      To fully automate file creation and sending, the file transfer system can be called by Remote Function Call (RFC) immediately after the file is created (more exactly: after the creation of all files in a creation run). This means that further processing can be initiated directly afterwards.

      The interface of this function can be recognized from the call:

      call function itnc301x-rfnameout destination itnc301x-rfcdest
      exporting EINRI = EINRI
      tables FNAMES = FNAMES.

      The field EINRI is the only authorized value for the import parameter of this function. This field must be defined LIKE TN01-EINRI. The list of created files is transferred in table FNAMES. This table comprises a single column which must be created LIKE RNCFNAME-FNAME. Each table row contains one complete file name (file name with complete path).

      A corresponding function (within the RFC API) must be available on the transfer system side. The name of this function is user-defined. You have to specify the name of this function together with the name of the RFC destination here.

      The function module ISH_301_PARTNER_RCV_OUTBOUND serves as a template for RFC stub generation, in other words for the interface of the external C program. You can generate this C program as a server program using transaction se37.

  2. EDI Procedure Without File Handling

    If data is exchanged synchronously via a program interface rather than by means of a file, there is no need to Customize the file-related fields. In such cases, specify the RFC destination and the name of the function module which receives the data.

    You can use function module ISH_NPMI_ACCEPT_TEMPLATE which implemented the NPMI interface as a template for generating a server program.

Business Attributes
ASAP Roadmap ID 151   Design interfaces 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG ISH_HCM_301_PARTNER 0 I010004233 Communication with Systems Outside the Hospital 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
V_TNC301X V - View SM30 0000000000 Connect Data Transfer System 
History
Last changed by/on SAP  19990816 
SAP Release Created in