2.4.46. Command Code EPLAN

(1) Purpose: Use Command Code (CC) EPLAN to add, revise, or delete a plan data module of an Employee Plans Master File (EPMF) entity record.

(2) Audience: LMSB, SBSE, TEGE, W&I

(3) Program Owner: AD Submission Processing

(4) 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

(5) Program Goals: The exhibits that follow this section cover specific information about using Command Code EPLAN. See Exhibit 2.4.46-1 Command Code EPLAN Request shows what data in what format to enter to get the EPLAN screen. See Exhibit 2.4.46-2 EPLAN screen layout. See Exhibit 2.4.46-3 for input fields. See Exhibit 2.4.46-4 for valid abbreviations and District Office codes. See Exhibit 2.4.46-5 for Screens messages and Error flags. See Exhibit 2.4.46-6 for a table that summarizes which transaction codes use which data entry fields. See Exhibit 2.4.46-7 through Exhibit 2.4.46-18 that covers the transaction codes individually.

(1) Use Command Code (CC) EPLAN to add, revise, or delete a plan data module of an Employee Plans Master File (EPMF) entity record. The ten transaction codes (TC) used with CC EPLAN determine the types of changes the user can make:

(2) To use CC EPLAN, first enter the EPLAN request on line one of the unformatted screen. The request—assuming it passes validity checks and the database files are available—gets the formatted EPLAN screen.

(3) The EPLAN screen redisplays the request line sans definer. It displays 17 data entry fields marked by delimiters and identified with abbreviations. Each transaction code uses a unique subset of these fields. Transmitting the input brings up the response screen.

(4) The EPLAN response screen redisplays the request line sans definer and the user's input. It adds messages and error flags. Errors consist of fields with unacceptable content, required fields containing blanks, disallowed fields containing data, and related fields with inconsistent entries. For valid input EPLAN displays "REQUEST COMPLETED" and builds a GENDATA record.

(1) The exhibits that follow this section cover specific information about using CC EPLAN. See Exhibit 2.4.46-1,Command Code EPLAN Request, shows what data in what format to enter to get the EPLAN screen ( See Exhibit 2.4.46-2, EPLAN Screen layout). See Exhibit 2.4.46-3 and See Exhibit 2.4.46-4 deal with entering data. See Exhibit 2.4.46-5 covers messages and error flags. See Exhibit 2.4.46-6 has a table that summarizes which transaction codes use which data entry fields. See Exhibit 2.4.46-7 through See Exhibit 2.4.46-18 cover the transaction codes individually.

(1) The EPLAN request format:

(2) You must enter the first 6 elements. Element 7, the TC000 intent indicator, depends on the transaction code.

(3) A valid EPLAN request brings up the formatted EPLAN screen. See Exhibit 2.4.46-2.

(1) The EPLAN request ( See Exhibit 2.4.46-1 ) gets the formatted EPLAN screen that allows the user to tab from data entry field to data entry field. EPLAN screen layout:

(2) The EPLAN request ( See Exhibit 2.4.46-1 ) is redisplayed on line 1 positions 1–28, but the CC definer is omitted. Position 23 has default "N" if it was blank in the request.

(3) The screen shows 18 data input fields with delimiters (" =","+", or "]"). It identifies each field with an abbreviation (literal). The abbreviation follows the right delimiter unless it doubles as delimiter. The positions and names of the display literals:

(1) EPLAN data entry screen layout with input fields shaded:

(2) Data fields information:

(1) EPLAN flags errors with asterisks (*). This screen layout shades the error indicator locations and the message line:

(2) Message line 24 of the EPLAN screen can display any of these messages:

(3) The message "REQUEST COMPLETED" indicates successful data input. It is the only non-error message.

(1) The table below gives a summary of the required (R), optional (O), and disallowed (shaded black) input fields for the ten transaction codes used with EPLAN. See Exhibit 2.4.46-7 through See Exhibit 2.4.46-18 show the input screen layouts for the individual transaction codes (TC).

(2) Note that both TC000 and TC128 have two versions of the required, optional, or disallowed data entry fields. You enter either the administrator-same indicator or the full administrator information.

(1) See Exhibit 2.4.46-1, paragraph 2—especially the description of element 7—for the EPLAN screen request to use with Transaction Code 000. On the EPLAN screen layout below the only permitted input fields are blocked out of character by character, and the required fields are shaded as well as blocked.

(2) Here is the first ( See Exhibit 2.4.46-8 for the second) of two screens for TC000 showing the input with the administrator-same indicator:

(3) The required input fields for TC000, first version:

1. Transaction code (TCN), which must be 000

2. Plan year ending month (PY)

3. Administrator same indicator (ASI), which must be 1

4. Remarks (RM)

5. Plan name first line (P1)

(4) The optional input fields for TC000, first version:

1. Plan effective date (EFDT)

2. Plan filing requirement code (PFRC)

3. Posting delay code (PDC)

4. Plan name second line (P2)

(1) See Exhibit 2.4.46-1, paragraph 2—especially the description of element 7—for the EPLAN screen request to use with Transaction Code 000. On the EPLAN screen layout below the only permitted input fields are blocked out character by character, and the required fields are shaded as well as blocked.

(2) Second ( See Exhibit 2.4.46-7 for the first) of two screens for TC000, showing the input that does NOT use the administrator-same indicator:

(3) The required input fields for TC000, second version:

1. Transaction code (TCN), which must be 000

2. Plan year ending month (PY)

3. Remarks (RM)

4. Plan name first line (P1)

5. Administrator name first line (ADM1)

6. Administrator city (CY)

7. Administrator state (ST)

8. Administrator ZIP code (ZC)

9. Administrator EIN (AEIN)

(4) The optional input fields for TC000, second version:

1. Plan effective date (EFDT)

2. Plan filing requirement code (PFRC)

3. Posting delay code (PDC)

4. Plan name second line (P2)

5. Administrator name second line (ADM2)

6. Administrator street address (STR)

(1) See Exhibit 2.4.46-1, paragraph 2—especially the description of element 7—for the EPLAN request format to use with Transaction Code (TC) 011. On the layout below the only permitted input fields are blocked out character by character, and the required fields are gray as well as blocked.

(2) EPLAN input screen layout for TC011:

(3) Required input fields for TC011:

1. Transaction code (TCN), which must be 011

2. New plan number (NPL)

3. Remarks (RM)

(4) Optional input field for TC011:

1. Posting delay code (PDC)

(1) See Exhibit 2.4.46-1, paragraph 2—especially the description of element 7—for the EPLAN request format to use with Transaction Code (TC) 012. On the layout below the only permitted input fields are blocked out character by character, and the required fields are gray as well as blocked.

(2) EPLAN input screen layout for TC012:

(3) The required input fields for TC012:

1. Transaction code (TCN), which must be 012

2. Remarks (RM)

(4) The optional input fields for TC012:

1. Plan year ending month (PY)

2. Plan effective date (EFDT)

3. Plan filing requirement code (PFRC)

4. Posting delay code (PDC)

(1) See Exhibit 2.4.46-1, paragraph 2—especially the description of element 7—for the EPLAN request format to use with Transaction Code (TC) 013. On the layout below the only permitted input fields are blocked out character by character, and the required fields are gray as well as blocked.

(2) CC EPLAN input screen for TC013:

(3) Required input fields for TC013:

1. Transaction code (TCN), which must be 013

2. Remarks (RM)

3. Plan name first line (P1)

(4) Optional input fields for TC013:

1. Plan effective date (EFDT)

2. Plan filing requirement code (PFRC)

3. Administrator-same indicator (ASI), which must be 1

4. Posting delay code (PDC)

5. Plan name second line (P2)

(1) See Exhibit 2.4.46-1, paragraph 2—especially the description of element 7—for the EPLAN request format to use with Transaction Code (TC) 016. On the layout below the only permitted input fields are blocked out character by character, and the required fields are gray as well as blocked.

(2) EPLAN input screen layout for TC016:

(3) Required input fields for TC016:

1. Transaction code (TCN), which must be 016

2. Plan filing requirement code (PFRC)

3. Remarks (RM)

(4) Optional input field for TC016:

1. Posting delay code (PDC)

(1) See Exhibit 2.4.46-1, paragraph 2—especially the description of element 7—for the EPLAN request format to use with Transaction Code (TC) 017. On the layout below the only permitted input fields are blocked out character by character, and the required fields are gray as well as blocked.

(2) EPLAN input screen layout for TC017:

(3) Required input fields for TC017:

1. Transaction code (TCN), which must be 017

2. File folder number (FFN)

3. Remarks (RM)

(4) Optional input fields for TC017:

1. Plan effective date (EFDT)

2. Plan filing requirement code (PFRC)

3. Posting delay code (PDC)

(1) See Exhibit 2.4.46-1, paragraph 2—especially the description of element 7—for the EPLAN request format to use with Transaction Code (TC) 020. On the layout below the only permitted input fields are blocked out character by character, and the required fields are gray as well as blocked.

(2) EPLAN input screen layout for TC020:

(3) Required input fields for TC020:

1. Transaction code (TCN), which must be 020

2. Remarks (RM)

(4) Optional input field for TC020:

1. Posting delay code (PDC)

(1) See Exhibit 2.4.46-1, paragraph 2—especially the description of element 7—for the EPLAN request format to use with Transaction Code (TC) 053. On the layout below the only permitted input fields are blocked out character by character, and the required fields are gray as well as blocked.

(2) EPLAN input screen layout for TC053:

(3) Required input fields for TC053:

1. Transaction code (TCN), which must be 053

2. Plan year ending month (PY)

3. Remarks (RM)

(4) Optional input field for TC053:

1. Posting delay code (PDC)

(1) See Exhibit 2.4.46-1, paragraph (2)—especially the description of element 7—for the EPLAN request format to use with Transaction Code (TC) 127. On the layout below the only permitted input fields are blocked out character by character, and the required fields are gray as well as blocked.

(2) EPLAN input screen layout for TC127:

(3) Required input fields for TC127:

1. Transaction code (TCN), which must be 127

2. Remarks (RM)

3. Administrator name first line (ADM1)

4. Administrator city (CY)

5. Administrator state (ST)

6. Administrator ZIP code (ZC)

7. Administrator EIN (AEIN)

(4) Optional input fields for TC127:

1. Plan filing requirement code (PFRC)

2. Posting delay code (PDC)

3. Administrator name second line (ADM2)

4. Administrator street address (STR)

(1) See Exhibit 2.4.46-1, paragraph 2—especially the description of element 7—for the EPLAN screen request to use with Transaction Code (TC) 128. On the EPLAN screen layout below the only permitted input fields are blocked out character by character, and the required fields are shaded as well as blocked.

(2) First ( See Exhibit 2.4.46-18 for the second) of two screens for TC128, showing the input without the administrator-same indicator:

(3) The required input fields for TC128, first version:

1. Transaction code (TCN), which must be 128

2. Plan year ending month (PY)

3. Remarks (RM)

4. Plan name first line (P1)

5. Administrator name first line (ADM1)

6. Administrator city (CY)

7. Administrator state (ST)

8. Administrator ZIP code (ZC)

9. Administrator EIN (AEIN)

(4) The optional input fields for TC128, first version:

1. Plan effective date (EFDT)

2. Plan filing requirement code (PFRC)

3. Posting delay code (PDC)

4. Plan name second line (P2)

5. Administrator name second line (ADM2)

6. Administrator street address (STR)

(1) See Exhibit 2.4.46-1, paragraph 2—especially the description of element 7—for the EPLAN screen request to use with Transaction Code 000. On the EPLAN screen layout below the only permitted input fields are blocked out character by character, and the required fields are shaded as well as blocked.

(2) Second See Exhibit 2.4.46-17 for the first) of two screens for TC000, showing the input version with the administrator-same indicator:

(3) Second version of the required input fields for TC128:

1. Transaction code (TCN), which must be 128

2. Plan year ending month (PY)

3. Administrator same indicator (ASI), which must be 1

4. Remarks (RM)

5. Plan name first line (P1)

(4) Second version of the optional input fields for TC128:

1. Plan effective date (EFDT)

2. Plan filing requirement code (PFRC)

3. Posting delay code (PDC)

4. Plan name second line (P2)