SAP ABAP IMG Activity ISH_EDI_FILENAME (Define File Name Composition)
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_EDI_FILENAME Define File Name Composition  
Transaction Code S_KK4_96000305   (empty) 
Created on 20000209    
Customizing Attributes ISH_EDI_FILENAME_ATR   IS-H: Define EDI File Name Composition 
Customizing Activity ISH_V_TNC301F0   Define File Name Composition 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name ISH_EDI_FILENAME    

Use

In this IMG activity, you specify how the file names for EDI procedures with a complex file name logic are to be created.

These specifications are relevant for procedures in the country version Singapore only.

Specifications are not permitted in other country versions.

Activities

  1. You can combine several constants, a date specification and a number of counters in a file name.
  2. You can create file names that differ according to institution, data collection point and message type.
  3. If you wish to use the same logic for all data collection points, make a generic entry (*) in the Data cllcPnt field. Note that this is only possible if the additional counters are also to be incremented across all data collection points.
  4. You can also make a generic entry (*) for the message type, if you wish all message types to be written to the same file when the file is created. If only one message type per file is permitted, you have to specify the message type here.

Example

File name logic for DRG data exchange in the country version Singapore:

The file name is composed of (in the following order):

  1. Hospital ID, e.g. XY
  2. Last two digits of the year specification
  3. Month
  4. Constant for the respective message type, e.g. I
  5. Counter that is incremented on a monthly basis, first from 1-9, then from A-Z

Thus the name of the second file in April 2000 is XY0004I2.

Requirements

You must have maintained the data collection points.

Standard settings

Recommendation

Since the alphabetical mode of counting runs strictly from A to Z, this function cannot be used in languages with a different alphabet. For such languages, use the numerical mode of counting only.

Activities

Further notes

  • If you have implemented your own EDI procedure, check whether you also wish to use this file name logic.
  • Function module ISH_EDI_ISHFILENAME_BUILD automatically calls function module ISH_EDI_DATAFILENAME_BUILD that creates the file name from this Customizing table.

    If the system couldn't determine a file name, it then calls your EDI-specific function module ISH_xxx_ISHFILENAME_BUILD, in which you create the file name according to the conventions of your EDI procedure.

Business Attributes
ASAP Roadmap ID 152   Design data acquisition 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
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_TNC301F0 V - View SM30  
History
Last changed by/on SAP  20000210 
SAP Release Created in