SAP ABAP IMG Activity PAY_NL_B2A_LA_130 (Define file names/location)
Hierarchy
☛
SAP_HRCNL (Software Component) Sub component SAP_HRCNL of SAP_HR
⤷ PY-NL (Application Component) The Netherlands
⤷ P05C (Package) HR Customizing: Netherlands
⤷ PY-NL (Application Component) The Netherlands
⤷ P05C (Package) HR Customizing: Netherlands
IMG Activity
ID | PAY_NL_B2A_LA_130 | Define file names/location |
Transaction Code | S_PCO_36000243 | (empty) |
Created on | 20050506 | |
Customizing Attributes | PAY_NL_B2A_LA_130 | Define file names/location |
Customizing Activity | PAY_NL_B2A_LA_130 | Define file names/location |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | PAY_NL_B2A_LA_130 |
Use
This is where you configure the names and locations for the different notifications (files) sent during the wage return process.
The server directory structure is used for managing files, for example wage returns to be submitted, response messages and notifications for incorrect nominative returns (abbreviated in Dutch to MFNA's).
The logical file paths and names are not linked to any particular operating system.
Requirements
The following logical path names are part of the standard delivery:
- HR_NL_LAA_OUT
Path for wage returns to be sent - HR_NL_LAA_IN
Path for received notifications. When importing reply notifications into the SAP system, the system searches for files in this location.
The following logical file names are part of the standard delivery:
- HR_NL_LAA_OUT_NEW
File for wage returns to be sent. The file has the following structure:
LA<PARAM_1> with: - "WR"
- Wage tax number (CHAR 12)
- <Return period (In-period) (CHAR 4: YYMM)
- Last two digits of the sequence number of the wage return (NUMC 2)
- "XML"
Example
LA262222644L01060117.XML - HR_NL_LAA_IN
File for received notifications. The file is stored in log HR_NL_LAA_IN. This file name must remain blank. See report documentation for more information.
Standard settings
Activities
Enter the corresponding file path for existing operating systems (syntax groups).
- Defining variables
The following definition is required:
Variable Value
FILENAME file name - Defining syntax groups
Syntax groups are used for similar directory paths
Example:
UNIX all Unix platforms - Assigning an operating system - syntax group
This is where you assign the required syntax group to each operating system.
Example:
AIX Unix IBM
=> Syntax group Unix all Unix platforms
Linux Linux
=> Syntax group Unix all Unix platforms - Assigning a logical path - physical paths
Define the physical path for each operating system you wish to use (syntax group).
Example:
Log. path HR_NL_LAA_OUT
Description Directory for storing certificate data
Syntax group UNIX all Unix platforms
Phys. path /usr/sap/tmp/<FILENAME>
Example
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_LA_130 | NL | Netherlands |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | PAY_NL_B2A_LA_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 | 20050511 |
SAP Release Created in | 600 |