Function documentationUnited States Federal Government Fields

 

The Governmentwide Treasury Account Symbol Adjusted Trial Balance System (GTAS) and Intra-Governmental Payment and Collection System (IPAC) require the recording of additional US Federal Government fields. These fields include trading partner Treasury Account Symbols (TP TAS) and trading partner Business Event Type Codes (TP BETC).

The following table lists the use of various individual trading partner TAS components for reporting to GTAS and IPAC:

Trading Partner TAS Fields

Use

Sub-level Prefix (SP)

IPAC

Allocation Transfer Agency ID (ATA)

IPAC

Agency ID (AID)

GTAS and IPAC

Beginning Period of Availability (BPOA)

IPAC

Ending Period of Availability (EPOA)

IPAC

Availability Type Code (ATC)

IPAC

Main Account Code (MAIN)

GTAS and IPAC

Sub-Account Code (SUB)

IPAC

Trading Partner BETC

IPAC

Integration

You can capture these trading partner fields in various entry transactions using a flexible entry screen. In addition to the TP TAS and TP BETC fields, you can define additional customer-specific fields. The US Government fields are entered in the beginning of a document chain and copied to subsequent documents. Entry of US Government fields is supported for the following initial transactions:

  • Sales Order (SO) on the line item level

  • Purchase Order (PO) on the line item level

  • Earmarked funds (funds commitment, funds reservation, forecast of revenue) on the line item level

  • Financial (FI) documents (FB01, FB50, FB60/FB65, FB70/FB75) on the line item level, general ledger accounts

  • Budgeting workbench (FMBB) on the document header on the Additional Data tab

  • Selected asset acquisition and disposal transactions on the document header on the Additional Data tab

Subsequent documents of the above initial documents inherit the US Government fields. This is supported for the following transactions:

  • Down payments and down payment requests

  • Goods receipts

  • Invoice receipts

  • Sales and Distribution billing documents

  • FI customer and vendor invoices and credit memos

  • Payment documents

Activities

  1. Maintain derivations for SGL attributes.

    For actual documents and budget documents, the US Federal fields are automatically transferred from the entry document to the ledger document. However, this is only done on the level where the US Government fields are entered or transferred from the predecessor document.

    To update additional line items and subsequent documents where you cannot enter the fields, you must use the split processor and commitment string. To use this function, complete the Customizing activity Maintain Derivations for SGL Attributes under Start of the navigation path Public Sector Management Next navigation step Functions for US Federal Government Next navigation step General Settings End of the navigation path. Select GTAS Attribute Derivation at Time of Posting, and create a new derivation rule that uses function module FMFG_DERIVE_USGOVKEY_FIELDS. This function module reads the US Government key using the commitment string. Since the commitment string is part of the splitting logic for US Federal agencies, you can use it within the document chain to find the US government fields from the initial document (such as sales order, purchase order, and funds commitment).

    For example, in a vendor invoice referencing a purchase order line item, the commitment string is part of the vendor line and can be used to update the vendor line in the US Federal Ledger with the US Government fields. Subsequently, the clearing document for vendor invoices contains the commitment string, and the disbursement in transit account and the cash account can be updated with the US Government fields.

    Note Note

    Standard derivation functions still apply. It is possible to alter the result of the direct entry of US Government fields in the entry document by the above function module and further derivation rules.

    End of the note.

  2. Define US Federal Government field values (optional).

    You can define the field values for US Federal Government fields and their field value text in Customizing activity Define US Federal Government Field Values under Start of the navigation path Public Sector Management Next navigation step Functions for US Federal Government Next navigation step General Settings Next navigation step US Federal Government Fields End of the navigation path.

  3. Define the US Federal Government field list for which you want to provide field values and field value texts (optional).

    You can also provide F4 functions for the fields and field value checks for data entry screens. You can provide hard-coded field values in your own Business Add-In (BAdI) implementation or by using a Customizing table that contains the field values. See Customizing activity BAdI: Definition of US Federal Government Fields under Start of the navigation path Public Sector Management Next navigation step Functions for US Federal Government Next navigation step General Settings Next navigation step US Federal Government Fields End of the navigation path.

  4. Set functions for US Federal Government Fields dialog (optional).

    You can do the following:

    • Prefill field values in the US Federal Government fields.

    • Specify display options (display only, mandatory, or hidden) for each field that appears in the US Federal Government Fields dialog.

    • Adjust the field checks in the dialog or on the document level.

    See Customizing activity BAdI: Functions for US Federal Government Fields Dialog under Start of the navigation path Public Sector Management Next navigation step Functions for the US Federal Government Next navigation step Integration Next navigation step General Settings Next navigation step Business Add-Ins for US Federal Government Fields Dialog End of the navigation path.

  5. Add customer fields to the US Federal Government Fields dialog (optional).

    You can use a BAdI to include customer-specific fields for entry within the US Government framework.

    See Customizing activity BAdI: Customer Fields in the US Federal Government Fields Dialog under Start of the navigation path Public Sector Management Next navigation step Functions for the US Federal Government Next navigation step Integration Next navigation step General Settings Next navigation step Business Add-Ins for US Federal Government Fields Dialog End of the navigation path.

    Note Note

    If you are adding customer fields and want to update the fields in a chain of documents using the commitment string, you should not allow changes to these fields in the middle of a process chain. Follow the logic for SAP-delivered fields such as Trading Partner TAS and Trading Partner BETC.

    End of the note.