AccessibilitySkip to Top NavigationSkip to Main ContentHome  |  Contact IRS  |  About IRS  |  Site Map  |  Español  |  Help  

Part 2. Information Technology

Chapter 3. IDRS Terminal Responses

Section 12. Command Code ACTON

2.3.12  Command Code ACTON

2.3.12.1  (01-01-2006)
General

  1. A control base is appended to a module on IDRS to record the employee to whom a case is assigned and other case control information. See IRM 2.3.11 for the format and contents of the Control History Group as displayed by CC TXMOD.

  2. The presence of an open control base on a module indicates that the module is controlled for the purpose of adjustment, correspondence with the taxpayer, or other action. A control base in a tax module indicates that the module is under control to the assignee. A control base in an entity module signifies that all modules in the account are, in effect, controlled.

  3. Control bases may be updated when necessary to indicate changes in status or actions taken on a case. The presence of an open control base will cause the retention of the module on IDRS.

  4. A history item is appended to a module on IDRS to record significant action without placing a module under control. See IRM 2.3.11 for the format and contents of the Action History Group as displayed by CC TXMOD.

  5. The requested module must be present on IDRS in order for a history item to be appended. Use CC MFREQ if necessary to establish a module on the TIF.

  6. Once entered, a history item cannot be altered or added to; additional history items may be input however. The appending of a history item alone will not generate a TC 902, nor is its presence a criterion for the retention of a module on IDRS.

  7. When establishing an entity on IDRS, appending a history item with activity code "ENTC" will cause IDRS to retain the entity posted transactions on the entity module for 49 days from the date that the history item was input.

  8. If the entity is on IDRS, but the entity posted transactions are not and this information is needed for research, append a history item with an activity code of "ENTC" and then use CC MFREQ to request a re-extract of the entity from the Master File to bring the posted entity transactions to IDRS. The previously appended history item will cause the transactions to be retained.

  9. Command Code ACTON with Definer "D" may be used to delete a History Item. Action item to be deleted must be the current (latest) item on database. Program will not search backwards trying to find the action item. Employee number on the input command must match number on database. Action item must have been added with ACTON (i.e., source code " G" on database). Program will not delete action items from other command codes.

2.3.12.2  (01-01-2000)
Case Control Using Command Code ACTON

  1. Command Code ACTON may be used to establish control bases, to update or close control bases that are open, to correct name controls on dummy accounts, to append history items to modules on IDRS, and to generate TC 902s to secure tax modules and their related entity data from the Master File.

  2. ACTON generates a TC 902 only when establishing a dummy account or module on the TIF or when updating the name control on a dummy account. If the requested account and/or module is already present on the TIF and a TC 902 must be generated, use CC MFREQ, which generates a TC 902 for every accepted input. See IRM 2.3.10 for MFREQ input instructions.

  3. Most ACTON fill-ins for data fields are optional and various combinations of these elements may be input. Input fields are required and/or chosen based on which prerequisite command code is used and the type of action being taken. See Exhibit 2.3.12–1 for description and validity of ACTON input fields.

  4. A valid input of CC ENMOD, SUMRY, TXMOD, LPAGD, ADJ54, FRM34, FRM77, STAUP, DRT24, DRT48, ACTON or REINF (when default from SUMRYR) must precede each ACTON input request, Pertinent input data from these command codes is stored in terminal memory and need not be re-entered as part of the ACTON request. All prerequisite commands store the TIN and the file source. In addition, CC ENMOD and CC TXMOD store the MFT, the plan number/report number if applicable, and the tax period for use by ACTON. When using ACTON following CC LPAGD make sure that the message "REQUEST COMPLETED-TIN STORED FOR ACTON" has been received before attempting an ACTON input request. See Exhibit 2.3.12–1 for instructions regarding use of ACTON following LPAGD.

  5. Generally, the research sequence for controlling a module will be the use of CC SUMRY, followed by TXMOD, followed by an ACTON request. CC TXMOD input is not necessary however, if SUMRY shows that the account is not on the TIF or that the tax module to be controlled is not on the file.

    1. When a SUMRY request yields the message " NO DATA AVAILABLE" , verify that the input TIN and file source are correct to prevent the establishment of a dummy account with erroneous account data, and then proceed from SUMRY directly to in ACTON request for the specific tax period. This will establish the dummy module on IDRS with an open control base and, for non-NMF accounts, generate a TC 902 to bring the requested tax module and its related entity data from the Master File to IDRS.

    2. If SUMRY shows that the requested tax module is present on the TIF, TXMOD must be input before entering an ACTON request for that module, or the error message "INITIATE TXMOD" will result. Although BATCH ACTON does not require this procedure it is recommended that prior control bases research be done. This is to direct the examiner's attention to possible control or other pertinent information in the module.

    3. When a SUMRY request indicates that a memo account is present on the file (indicating that the account has been resequenced to another TIN, use caution when establishing a new control base on any module within the account. If an ACTON request is input to establish a new control base, all old account data is deleted from the TIF, a dummy module is established, and a TC 902 is generated to reactivate the account. If there is an open control base or other important information present in the memo account, this information is lost. Also, since an account merge has taken place, care should be taken before attempting to reactivate the account.

    4. When a SUMRY request is made and there is only one tax module present in an account, the SUMRY request returns a TXMOD display of that module. If this is not the module to be controlled, input TXMOD for the MFT, plan number and tax period desired. This will result in a SUMRY display. Now input ACTON, re-entering the MFT, plan number and tax period of the module to be controlled.

  6. Once a control base has been established on a module, the original entries may be altered and/or a record of any significant action taken may be appended to the Control History Section by the input of an additional ACTON request. The ACTON request must reference the established control sequence number (e.g. "CO2" ), and can include as few as one or as many as all of the optional input fields. See Exhibit 2.3.12–2 for sample inputs.

  7. All ACTON control base entries are recorded by control sequence number in chronological order in the Control History Section. A changed record is available for display as appended or altered, immediately after the ACTON input is accepted and can be inspected using CC ENMOD or CC TXMOD. All history items are recorded in chronological order in the Action History Section and can also be inspected immediately using CC ENMOD or CC TXMOD.

2.3.12.3  (01-01-2000)
Batch ACTON

  1. ACTON has the ability to establish control bases, update control bases or establish history items on multiple tax modules as long as the TIN is the same for each module. Batch ACTON provides for batch processing of a maximum of 10 control bases or 10 history items on one screen input. Since Batch ACTON information is duplicated — ONLY use ACTONB when the same information is desired in all control bases

    1. Batch ACTON requires a command code definer of "B" .

    2. The tax modules in lines 4 through 12 will be updated with the same input data on lines 2 and 3.
      Activity code
      Case status code
      Category code
      Employee number
      IRS received date

    3. The first 3 lines of the screen must be valid and consistent before the batch lines are processed. Errors from line 1 through 3 will be reflected on line 24. Errors encountered on batch work lines will be displayed to the right of the affected line. The error message will begin in column 40.

    4. Several ACTON and ACTONB error messages dealing with MFT, Tax period or Group number, have been abbreviated to accommodate the length constraints of the batch work line.

    5. Batch ACTON will not update EPMF.

    6. History items or control bases cannot be mixed on the same input screen. Also control bases cannot be established (i.e. C#) and updated (i.e. Cnn) on the same screen.

    7. After an error is encountered, screen information may be corrected and reinput.

    8. ACTONB will not establish or update any history items or control bases until the entire screen can be processed.

    9. Tax modules can be input in any sequence but duplicate tax modules are not permitted and entity inputs can only be done on the first three lines.

2.3.12.4  (01-01-2003)
Terminal Response Command Code ACTON

  1. Terminal Input: See Exhibit 2.3.12–2 for ACTON sample input.

  2. Terminal Response:

    1. Invalid Response: Error messages are displayed in inverse video beginning in position 1 of line 24. Correct the error and re-enter the screen. See Exhibit 2.3.12–3 for ACTON error messages.

    2. System Error Response: System error messages are displayed in inverse video beginning in position 1 of line 24. System errors reflect a problem relating to the availability of a file or an error with a common subroutine. In many cases an RPA should be notified, and a print made of screen input and response to aid in analysis and correction of programming or data base problems. See the Miscellaneous Error Messages section of IRM 2.3.2.5 for definitions of these messages and corrective measures.

    3. Valid Response: If the ACTON request is accepted, the input screen is redisplayed and "REQUEST COMPLETED" is displayed on line 24.

Exhibit 2.3.12-1  (01-01-2003)
ACTON Input Format

Input Format Command Code ACTON

This image is too large to be displayed in the current screen. Please click the link to view the image.

The above graphic is an example of the input screen for CC ACTON with the fields defined in the table below.

Record Element Description

Element Line Position Description and Validity
1 1 1–5 Command Code — " ACTON"
2 1 6 CC Definer "B " or blank
3 1 7–8 MFT Code — See IRM 2.3.8, Standard Validity Criteria. Required field if ACTON follows ACTON, ADJ54, DRT24, DRT48, FRM34, FRM77, LPAGD, REINF, RELES, STAUP, or SUMRY.
4 1 10–15 Tax Period — See IRM 2.3.8, Standard Validity Criteria. Required field if ACTON follows ACTON, ADJ54, DRT24, DRT48, FRM34, FRM77, LPAGD, REINF, RELES, STAUP, or SUMRY.
5 1 17–21 Name Control Field
      (a) If the account is not on the TIF, the name control must be input and must not be followed by the slash "/" .
      (b) If a real account is present on the TIF, it is not necessary to input the name control. If input it must match the TIF name control and must not be followed by the slash " /" .
      (c) If a dummy account is present on the TIF with all blanks in the name control field, an input name control followed by a slash "/" is required.
      (d) If a dummy account is established on the TIF with an incorrect name control, input ACTON with the correct name control followed by a slash "/" . Any transaction input made prior to the name control change will have to be reinput. Use CC TERUP if the error is discovered soon enough.
      Note that you cannot change the Name Control on a real account using Command Code ACTON.
5.1 1 17–21 Name Control — See IRM 2.3.8, Standard Validity Criteria. Required if the account is not on the TIF or the TIF name control on a dummy account is blank. Must be preceded by a blank and followed by a blank or slash "/" .
5.2 1 17–21 Name Control Change Indicator (slash "/" ) — Must be input when requesting a name control change to a dummy account on the TIF. Entering the correct name control followed by a slash "/" updates the incorrect dummy name control with the screen input Name Control and generates a correct TC 902 to the Master File.
6 1 23–25 Plan /Report Number — Required only if the prior command is other than TXMOD and the request is for MFT CODES 46, 68 or 76 or EPMF tax module. ValidEPMF plansare 100–999; MFT 46 are 000,100–199, 300–399, 500–599, 700–799, 900–999; MFT 68 are 001–999; MFT 76 are 000–999.
7 2 1–3 History or Control Group Number Field
7.1 2 1–3 Control Group Number — Must be "C#" for the establishment of a new control base or "Cnn" (nn = 01–99) for the update of an existing control base. The Control Group Number field must be followed by a comma** (see footnote) if "C#" is input or followed by a comma or blank if "Cnn" is input.
7.1 2 1–2 History Group Number — Must be "H" or "H#" for history item input and must be followed by a comma.
8 2 5–14* Activity Code — Must be 2–10 alphanumeric characters and must be on the approved list of activity codes. Authorized activity codes can be found in the Case Control Codes section of IRM 2.7 and in local IDRS bulletins. Required for history item input; optional for case control or update input.
9 2 16* Case Status Code — Must be "A" , "B" , "C" , "M" , or "S" . Required with " C#" but optional with "Cnn" . Invalid with "H" . Must be followed by a comma unless it is the last field input on the line; then the field must be followed by a blank. See the Case Control Codes section of IRM 2.7 for definitions of case status codes.
10 2 18–21* Control Category — Must be approved by the National Office. See the Case Control Codes section of IRM 2.7 for a list of approved control categories. Required with " C#" , optional with "Cnn" , and invalid with "H" .
11 2 23–24 ORIGINATOR CODE — must be two numeric characters or blank. Only required with a control category of "PREA" . This field is never followed by a comma.
12 3 1–10* Assignee Employee Number — Must be 10 numeric characters or be input as an asterisk * . The asterisk * will cause the terminal operator's employee number to be generated. Must be followed by a comma unless it is the last field input on the line. Required with "C#" , optional with "Cnn" , and invalid with " H" .
13 3 12–19 IRS Received Date — Must be 6 numeric characters in MMDDYYYY format or be input as an asterisk "*" . The asterisk "*" will cause the current date to be generated. A future date is invalid. Also, any date which is more than one year old is valid only if the Old Date Indicator is " V" . Required with "C#" , optional with " Cnn" , and invalid with "H" . This field is never followed by a comma.
14 3 20* Old-Date-Indicator — Optional; must be "V" if an IRS Received Date over one year old is entered else blank. It may not be used with the asterisk (*).
15 4–12 1–3 Control Group Number (See Elements 7 and 7.1 above). This is a required field if the batch work line is present.This field must be followed by a comma.
16 4–12 5–6 MFT Code — See IRM 2.3.8, Standard Validity Criteria. This is a required field if the batch work line is present. It must be followed by a comma.
17 4–12 8–13 Tax Period — See IRM 2.3.8, Standard Validity Criteria. This is a required field if the batch work line is present. When MFT is 46 or 76, it must be followed by comma.
18 4–12 15–17 Plan/Report Number. Valid for MFT 46, 68, 76 or EPMF Modules
*Note: The above Record Element Specification describes the maximum input for CC ACTON. The character positions for the optional fields marked by an asterisk are variable.
**Note: Commas are required following elements 7–14 whether or not the related field is input; the only exception to this is when the related field is the last item to be input on that screen line. For a control base update ("Cnn" ), only those fields which are being changed are required.

Exhibit 2.3.12-2  (01-01-2006)
ACTON Sample Inputs

Establishing a new control base on an existing account after ENMOD or TXMOD inquiry:

This image is too large to be displayed in the current screen. Please click the link to view the image.

The graphic above is an example of the CC ACTON screen for establishing a new control base on an existing account after CC ENMOD or TXMOD with the fields defined in the table below:

Element Line Position Description and Validity
1 1 1–5 Command Code — " ACTON"
2 1 6 CC Definer blank
3 2 1–3 History or Control Group Number Field
3.1 2 1–3 Control Group Number — Must be "C#" for the establishment of a new control base or "Cnn" (nn = 01–99) for the update of an existing control base. The Control Group Number field must be followed by a comma** (see footnote) if "C#" is input or followed by a comma or blank if "Cnn" is input.
4 2 5–14* Activity Code — Must be 2–10 alphanumeric characters and must be on the approved list of activity codes. Authorized activity codes can be found in the Case Control Codes section of IRM 2.7 and in local IDRS bulletins. Required for history item input; optional for case control or update input.
5 2 16* Case Status Code — Must be "A" , "B" , "C" , "M" , or "S" . Required with " C#" but optional with "Cnn" . Invalid with "H" . Must be followed by a comma unless it is the last field input on the line; then the field must be followed by a blank. See the Case Control Codes section of IRM 2.7 for definitions of case status codes.
5 2 18–21* Control Category — Must be approved by the National Office. See the Case Control Codes section of IRM 2.7 for a list of approved control categories. Required with " C#" , optional with "Cnn" , and invalid with "H" .
6 3 1–10* Assignee Employee Number — Must be 10 numeric characters or be input as an asterisk * . The asterisk * will cause the terminal operator's employee number to be generated. Must be followed by a comma unless it is the last field input on the line. Required with "C#" , optional with "Cnn" , and invalid with " H" .
7 3 12–19 IRS Received Date — Must be 6 numeric characters in MMDDYYYY format or be input as an asterisk "*" . The asterisk "*" will cause the current date to be generated. A future date is invalid. Also, any date which is more than one year old is valid only if the Old Date Indicator is " V" . Required with "C#" , optional with " Cnn" , and invalid with "H" . This field is never followed by a comma.
*Note: The above Record Element Specification describes the maximum input for CC ACTON. The character positions for the optional fields marked by an asterisk are variable.

Establishing a new control base after an ACTON, ADJ54, DRT24, DRT48, FRM34, FRM77, LPAGD, REINF, RELES, STAUP, OR SUMRY request:

This image is too large to be displayed in the current screen. Please click the link to view the image.

The graphic above is an example of the CC ACTON screen for establishing a new control base after CC ACTON, ADJ54, DRT24, DRT48,FRM34 FRM77,LPAGD,REINF, RELES, STATUP OR SUMRY Request with the fields defined in the table below:

Element Line Position Description and Validity
1 1 1–5 Command Code — " ACTON"
2 1 6 CC Definer blank
3 1 7–8 MFT Code — See IRM 2.3.8, Standard Validity Criteria. Required field if ACTON follows ACTON, ADJ54, DRT24, DRT48, FRM34, FRM77, LPAGD, REINF, RELES, STAUP, or SUMRY.
4 1 10–15 Tax Period — See IRM 2.3.8, Standard Validity Criteria. This is a required field if the batch work line is present. When MFT is 46 or 76, it must be followed by comma.
5 1 17–21 NAME CONTROL
(a) If the account is not on the TIF, the name control must be input and must not be followed by the slash "/" .
5.1 1 17–21 (b) If a real account is present on the TIF, it is not necessary to input the name control. If input it must match the TIF name control and must not be followed by the slash " /" .
5.1 1 17–21 (c) If a dummy account is present on the TIF with all blanks in the name control field, an input name control followed by a slash "/" is required.
5.1 1 17–21 (d) If a dummy account is established on the TIF with an incorrect name control, input ACTON with the correct name control followed by a slash "/" . Any transaction input made prior to the name control change will have to be reinput. Use CC TERUP if the error is discovered soon enough.
5 2 16* Note that you cannot change the Name Control on a real account using Command Code ACTON.
5 2 18–21* Name Control — See IRM 2.3.8, Standard Validity Criteria. Required if the account is not on the TIF or the TIF name control on a dummy account is blank. Must be preceded by a blank and followed by a blank or slash "/" .
5.1 1 17–21 Name Control Change Indicator (slash "/" ) — Must be input when requesting a name control change to a dummy account on the TIF. Entering the correct name control followed by a slash "/" updates the incorrect dummy name control with the screen input Name Control and generates a correct TC 902 to the Master File.
6 2 1–2 History or Control Group Number Field
6.1 2 1–2 Control Group Number — Must be "C#" for the establishment of a new control base or "Cnn" (nn = 01–99) for the update of an existing control base. The Control Group Number field must be followed by a comma** (see footnote) if "C#" is input or followed by a comma or blank if "Cnn" is input.
7 2 5–14* Activity Code — Must be 2–10 alphanumeric characters and must be on the approved list of activity codes. Authorized activity codes can be found in the Case Control Codes section of IRM 2.7 and in local IDRS bulletins. Required for history item input; optional for case control or update input.
8 2 16* Case Status Code — Must be "A" , "B" , "C" , "M" , or "S" . Required with " C#" but optional with "Cnn" . Invalid with "H" . Must be followed by a comma unless it is the last field input on the line; then the field must be followed by a blank. See the Case Control Codes section of IRM 2.7 for definitions of case status codes.
9 2 18–21 Control Category — Must be approved by the National Office. See the Case Control Codes section of IRM 2.7 for a list of approved control categories. Required with " C#" , optional with "Cnn" , and invalid with "H" .
10 3 1–10 Assignee Employee Number — Must be 10 numeric characters or be input as an asterisk * . The asterisk * will cause the terminal operator's employee number to be generated. Must be followed by a comma unless it is the last field input on the line. Required with "C#" , optional with "Cnn" , and invalid with " H" .
*Note: The above Record Element Specification describes the maximum input for CC ACTON. The character positions for the optional fields marked by an asterisk are variable.

Establishing a new control base on an EMPF account:

This image is too large to be displayed in the current screen. Please click the link to view the image.

The above graphic is an example of CC ACTON screen for establishing a new control base on an EMPF Account with the fields defined in the table below:

Element Line Position Description and Validity
1 1 1–5 Command Code — " ACTON"
2 1 6 CC Definer blank
3 1 7–8 MFT Code — See IRM 2.3.8, Standard Validity Criteria. Required field if ACTON follows ACTON, ADJ54, DRT24, DRT48, FRM34, FRM77, LPAGD, REINF, RELES, STAUP, or SUMRY.
4 1 10–15 Tax Period — See IRM 2.3.8, Standard Validity Criteria. This is a required field if the batch work line is present. When MFT is 46 or 76, it must be followed by comma.
5 1 17–21 NAME CONTROL
(a) If the account is not on the TIF, the name control must be input and must not be followed by the slash "/" .
5.1 1 17–21 (b) If a real account is present on the TIF, it is not necessary to input the name control. If input it must match the TIF name control and must not be followed by the slash " /" .
5.1 1 17–21 (c) If a dummy account is present on the TIF with all blanks in the name control field, an input name control followed by a slash "/" is required.
5.1 1 17–21 (d) If a dummy account is established on the TIF with an incorrect name control, input ACTON with the correct name control followed by a slash "/" . Any transaction input made prior to the name control change will have to be reinput. Use CC TERUP if the error is discovered soon enough.
5.1 1 17–21 Note that you cannot change the Name Control on a real account using Command Code ACTON.
5.1 1 17–21 Name Control — See IRM 2.3.8, Standard Validity Criteria. Required if the account is not on the TIF or the TIF name control on a dummy account is blank. Must be preceded by a blank and followed by a blank or slash "/" .
5.1 1 17–21 Name Control Change Indicator (slash "/" ) — Must be input when requesting a name control change to a dummy account on the TIF. Entering the correct name control followed by a slash "/" updates the incorrect dummy name control with the screen input Name Control and generates a correct TC 902 to the Master File.
6 1 23–25 Plan /Report Number — Required only if the prior command is other than TXMOD and the request is for MFT CODES 46, 68 or 76 or EPMF tax module. ValidEPMF plansare 100–999; MFT 46 are 000,100–199, 300–399, 500–599, 700–799, 900–999; MFT 68 are 001–999; MFT 76 are 000–999.
7 2 1–2 History or Control Group Number Field
7.1 2 1–2 Control Group Number — Must be "C#" for the establishment of a new control base or "Cnn" (nn = 01–99) for the update of an existing control base. The Control Group Number field must be followed by a comma** (see footnote) if "C#" is input or followed by a comma or blank if "Cnn" is input.
8 2 5–14* Activity Code — Must be 2–10 alphanumeric characters and must be on the approved list of activity codes. Authorized activity codes can be found in the Case Control Codes section of IRM 2.7 and in local IDRS bulletins. Required for history item input; optional for case control or update input.
9 2 16 Case Status Code — Must be "A" , "B" , "C" , "M" , or "S" . Required with " C#" but optional with "Cnn" . Invalid with "H" . Must be followed by a comma unless it is the last field input on the line; then the field must be followed by a blank. See the Case Control Codes section of IRM 2.7 for definitions of case status codes.
10 3 18–21* Control Category — Must be approved by the National Office. See the Case Control Codes section of IRM 2.7 for a list of approved control categories. Required with " C#" , optional with "Cnn" , and invalid with "H" .
11 3 1–10 Assignee Employee Number — Must be 10 numeric characters or be input as an asterisk * . The asterisk * will cause the terminal operator's employee number to be generated. Must be followed by a comma unless it is the last field input on the line. Required with "C#" , optional with "Cnn" , and invalid with " H"
*Note: The above Record Element Specification describes the maximum input for CC ACTON. The character positions for the optional fields marked by an asterisk are variable.

Correcting the IRS received date on an open control base:

This image is too large to be displayed in the current screen. Please click the link to view the image.

The above graphic is an example of screen for CC ACTON for correcting the IRS Received Date on an open control base with the fields defined in the table below:

Element Line Position Description and Validity
1 1 1–5 Command Code — " ACTON"
2 1 6 CC Definer blank
3 2 1–3 History or Control Group Number Field
3.1 2 1–3 Control Group Number — Must be "C#" for the establishment of a new control base or "Cnn" (nn = 01–99) for the update of an existing control base. The Control Group Number field must be followed by a comma** (see footnote) if "C#" is input or followed by a comma or blank if "Cnn" is input.
4 3 12–19 IRS Received Date — Must be 8 numeric characters in MMDDYYYY format or be input as an asterisk "*" . The asterisk "*" will cause the current date to be generated. A future date is invalid. Also, any date which is more than one year old is valid only if the Old Date Indicator is " V" . Required with "C#" , optional with " Cnn" , and invalid with "H" . This field is never followed by a comma.
*Note: The above Record Element Specification describes the maximum input for CC ACTON. The character positions for the optional fields marked by an asterisk are variable.

Establishing a new control base with an old IRS Received Date using the Old Date Indicator:

This image is too large to be displayed in the current screen. Please click the link to view the image.

The above graphic is an example screen for CC ACTON for establishing a new control base with an old IRS Received Date using the Old Date Indicator with the fields defined in the table below:

Element Line Position Description and Validity
1 1 1–5 Command Code — " ACTON"
2 1 6 CC Definer blank
3 1 7–8 MFT Code — See IRM 2.3.8, Standard Validity Criteria. Required field if ACTON follows ACTON, ADJ54, DRT24, DRT48, FRM34, FRM77, LPAGD, REINF, RELES, STAUP, or SUMRY.
4 1 10–15 Tax Period — See IRM 2.3.8, Standard Validity Criteria. Required field if ACTON follows ACTON, ADJ54, DRT24, DRT48, FRM34, FRM77, LPAGD, REINF, RELES, STAUP, or SUMRY.
5 2 1–3 History or Control Group Number Field
5.1 2 1–3 Control Group Number — Must be "C#" for the establishment of a new control base or "Cnn" (nn = 01–99) for the update of an existing control base. The Control Group Number field must be followed by a comma** (see footnote) if "C#" is input or followed by a comma or blank if "Cnn" is input.
5.1 2 1–2 History Group Number — Must be "H" or "H#" for history item input and must be followed by a comma.
6