Hierarchy
SAP_HRCNL (Software Component) Sub component SAP_HRCNL of SAP_HR⤷
PY-NL (Application Component) The Netherlands⤷
P05C (Package) HR Customizing: Netherlands
IMG Activity
| ID | PAY_NL_B2A_EDM_130 | Define file names/location |
| Transaction Code | S_L7D_24000197 | (empty) |
| Created on | 20060531 | |
| Customizing Attributes | PAY_NL_B2A_EDM_130 | Define file names/location |
| Customizing Activity | PAY_NL_B2A_EDM_130 | Check file names |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | PAY_NL_B2A_EDM_130 |
Use
In this step, you can set up the names and locations for the various messages (files) that are sent during the Day-one-announcement (EDM) process.
The directory structure of the server is used to manage the files, e.g. Day-one-announcements to be sent, response messages, etc.
The logical file paths and names are not linked to a specific operating system.
Requirements
The following logical file paths are included in the standard delivery:
- HR_NL_EDM_OUT
Path for EDMs to be sent - HR_NL_EDM_IN
Path for received response messages. When importing response messages into the SAP system, this is the location where the system will search for the file. - HR_NL_EDM_DONE
Path for processed response messages. After being processed the response messages are copied to this location.
The following logical file names are included in standard delivery:
- HR_NL_EDM_OUT
File for EDMs to be sent. The file is built up as follows:
<PARAM_1> with: - 'EM'
- Leper (CHAR 4)
- Creation date (CHAR 6: JJMMDD)
- Personnel number (PERNR, NUMC 8)
- SoFi number (SOFIN, NUMC 9)
- '.XML'
Example
EM000106072300062458123456782.XML
After the files have been created, all the EDMs that have to be sent simultaneously must be zipped to a zip file with the following name format:
- 'EM'
- Leper (CHAR 4)
- Creation date (CHAR 6: YYMMDD)
- '.ZIP' or '.GZ'
Example
EM0001060723.ZIP
- HR_NL_EDM_IN
File for received response messages. The file is saved in path HR_NL_EDM_IN. Since the filename is determined by the tax authorities (belastingdienst) and is not known in advance, this must remain empty.
Standard settings
Activities
Enter the corresponding file path for the existing operating systems (syntax groups). You can do this using the FILE transaction. In dialog structure 'define logical files Path' select EDM (HR_NL_EDM_IN, HR_NL_EDM_OUT, HR_NL_EDM_DONE) and for all three of the mentioned paths, go to Assign logical path - physical paths. In this view, you need to enter the physical path for the operating system (syntax group) in use.
- Define variables
The FILENAME variable is mandatory. This is normally included in the SAP standard delivery. If this is not the case, you need to set it up.
The following activities have already been implemented in the SAP standard delivery and do not have to be executed again.
- Define Syntax groups
Syntax groups are used for similar directory paths. You need to define these here, and indicate the maximum file-name length.
- Assigning the operating system
Assigning an operating system creates a link between a syntax group and an operating system.
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 1 | Mandatory activity |
| Critical / Non-Critical | 1 | Critical |
| Country-Dependency | I | Valid for countries specified |
| Customizing Attributes | Country Key | Country Name |
|---|---|---|
| PAY_NL_B2A_EDM_130 | NL | Netherlands |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | PAY_NL_B2A_EDM_130 | 0 | HLA0009652 | The Netherlands |
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 |
| IMGDUMMY | D - Dummy object | OG01 | TFILE |
History
| Last changed by/on | SAP | 20060622 |
| SAP Release Created in |
