
:quality(98)/www.dehn.de/store/f/10536157/HDVORSCHAU/951310.jpg)
The TIN, name control, plan number, or TC000 intent indicator on screen display line 1 has been altered after initial request input.
#EPLAN TN CODE#
The TIN or file source code is not valid for EPMF. Invalid entry of " SAME" in administrator name first line.ĭata entry outside the delimited input positions. The dummy account created by EPLAN is already on the TIF. Valid State Abbreviations (ADP) and District Office Codes (DO)ĮPLAN Messages Displayed on Screen Line 24 First two must be a valid District Office Code. The first two must be a valid District Office Code. If ADM2 is not administrator secondary-sort name line, the "]" must go in 1st position. Do not overlay "]" in position 1.ġst position: A–Z, 0–9. For valid input EPLAN displays "REQUEST COMPLETED" and builds a GENDATA record.Īll the delimiters are overlaid by data, except the "]" in line 4, position 1.Īll entries must begin in the first position of the input field first positions must not have blanks.ĭata must not follow 2 consecutive blanks.Ġ00, 011, 012, 013, 016, 017, 020, 053, 127, 128Ī–Z, 0–9, &, %, /, or blank. Errors consist of fields with unacceptable content, required fields containing blanks, disallowed fields containing data, and related fields with inconsistent entries. The EPLAN response screen redisplays the request line sans definer and the user's input. Transmitting the input brings up the response screen. Each transaction code uses a unique subset of these fields. It displays 17 data entry fields marked by delimiters and identified with abbreviations. The EPLAN screen redisplays the request line sans definer. The request-assuming it passes validity checks and the database files are available-gets the formatted EPLAN screen. To use CC EPLAN, first enter the EPLAN request on line one of the unformatted screen. See Exhibit 2.4.46-7 through Exhibit 2.4.46-18 that covers the transaction codes individually.Ĭhange both plan name and plan administrator data See Exhibit 2.4.46-6 for a table that summarizes which transaction codes use which data entry fields. See Exhibit 2.4.46-5 for Screens messages and Error flags.


See Exhibit 2.4.46-4 for valid abbreviations and District Office codes. See Exhibit 2.4.46-2 EPLAN screen layout. See Exhibit 2.4.46-1 Command Code EPLAN Request shows what data in what format to enter to get the EPLAN screen. Program Goals: The exhibits that follow this section cover specific information about using Command Code EPLAN. Primary Stakeholders: LMSB- Large Mid Size Business Division, SB/SE- Self-Employed/Small Business Division, TE/GE- Tax-Exempt/Government Entitles Division, W&I- Wage and Investment Division Purpose: Use Command Code (CC) EPLAN to add, revise, or delete a plan data module of an Employee Plans Master File (EPMF) entity record.
