Process documentationCustomizing Settings for Customer Fields

 

You make Customizing settings to be able to perform reporting using customer fields.

Prerequisites

Before you create a customer field, you must always run a data backup.

Process

Caution Caution

No postings may occur at the time when the field is created and at the time of the transport to the production system.

End of the caution.
  1. Defining the Coding Block

    Note Note

    • Note that you can no longer delete a customer field from the coding block as easily (that is, not with standard means).

    • To avoid naming conflicts, the customer fields must have names falling within the customer namespace. For more information about customer namespaces, see SAP Note 16466 and the related notes.

    End of the note.

    In the first step, you have to include the customer field in the coding block. You do this in the following IMG activity: Start of the navigation path Financial Accounting (New) Next navigation step Financial Accounting Global Settings (New) Next navigation step Ledgers Next navigation step Fields Next navigation step Customer Fields Next navigation step Edit Coding Block End of the navigation path.

    No posting transactions may be performed while you are including the customer field. We recommend using the “light” mode. For this, you only need to make the following entries so that all necessary changes to the dictionary and to the tables are performed automatically in the background:

    • Collection (package)

    • Field name

    • Field description

    • Data type

      • Character field (CHAR)

      • Character field with digits only (NUMC)

    Depending on system performance, this may take some time. The system outputs the result in a log.

    For detailed information, see the documentation on the IMG activity Edit Coding Block.

  2. Changing the Field Status of a Customer Field

    To be able to change and display a customer field in documents, you need to open it in the field status groups.

    To change the field status groups for the G/L account, perform the IMG activity under the following path: Start of the navigation path Financial Accounting (New) Next navigation step Financial Accounting Global Settings (New) Next navigation step Ledgers Next navigation step Fields Next navigation step Define Field Status Variants End of the navigation path. Customer fields are located in the subgroup Additional Account Assignments. Depending on the G/L accounts that you want to use, you can open the customer field in all field status groups or just in the relevant ones.

    Besides the field status groups for G/L accounts, you also have to open the field in the field status for the posting key. You do this in the following IMG activity:

    Start of the navigation path Financial Accounting (New) Next navigation step Financial Accounting Global Settings (New) Next navigation step Document Next navigation step Define Posting Keys End of the navigation path.

    Since only G/L account items can have additional account assignments in the form of a customer field, only the posting keys for G/L accounts can be used here. We recommend including the customer field in the posting keys for G/L accounts as an optional field and using the field status groups for further control. It may be possible to define the customer field as a required entry field for some of the G/L accounts selected, and as an optional field for other G/L accounts. This option is particularly relevant if the customer field is substituted partially. As an alternative to specifying required entry fields in the field status, you can also use validation.

  3. Setting Up Check on Customer Fields (Optional)

    When you have included a customer field in the coding block, you can enter any information in this field - but this data is not checked. Since a customer field is generally applied for specific structured data or a limited number of characteristic values need to be entered, we recommend that you always run a check. This is possible in the following ways:

    Check Using a Validation

    You can use a validation in Financial Accounting to check the entries or the substituted field contents. This is useful if the validation rules are kept relatively simple and in a manageable number. You set up the validation by performing the following IMG activity:

    Start of the navigation path Financial Accounting (New) Next navigation step Financial Accounting Global Settings (New) Next navigation step Tools Next navigation step Validation/Substitution Next navigation step Validation in Accounting Documents End of the navigation path.

    Here, you could choose between event 2 (document item) and event 3 (complete document).

    Check Using a Check Table

    Instead of performing a check using a validation, you can use a customer-specific, transparent table as a check table containing all possible characteristic values. You can define the customer-specific table using a table maintenance dialog. In this case, proceed as follows:

    1. In transaction SE11, define a check table in the repository.

    2. Create a table in the customer namespace. Such a table can have the following simple structure (as in the case of a business line):

      Example: Check Table

      Field Name

      Key

      Data Element

      Type

      Length

      Name

      MANDT

      X

      MANDT

      CLNT

      3

      Client

      BUSLINE

      X

      ZZBUSLINE(*)

      NUMC

      3

      Business Line

      TEXT50

       

      TEXT50

      CHAR

      50

      Description

      *) Note that you should use the data element from coding block maintenance.

    3. If you want to use a multilingual check, you have to move the texts to a separate table.

    4. You can store this table in the BSEG as a check table for your customer field and in the structure CI_COBL under Foreign Key.

    Search Help for Customer Fields

    You can create a search help so that not only a check is performed on the customer field but a search help also appears.

    1. In transaction SE11, select the Search Help option. For this, select the elementary search help.

    2. As the selection method, enter the check table you created previously.

    3. As search help parameters, see the example below.

      Example: Check Table

      Parameter

      IMP

      EXP

      Data Element

      BUSLINE

      X

      X

      ZZBUSLINE

      TEXT50

       

       

      TEXT50

    4. On the Entry Help/Check tab page, enter the search help in structure CI_COBL.

  4. Defining the Master Data Check

    To perform the allocation in new General Ledger Accounting, you need to define a master data check for customer fields. If you use a customer-specific check table, you can use it for this purpose. You can base your entry on the existing entries delivered by SAP and copy a suitable entry to your customer field. Specify your own table as the value table and text table. You define the master data check in the following IMG activity:

    Start of the navigation path Financial Accounting (New) Next navigation step Financial Accounting Global Settings (New) Next navigation step Ledgers Next navigation step Fields Next navigation step Customer Fields Next navigation step Define Master Data Check End of the navigation path

  5. Including Customer Fields in Enjoy Transactions

    In the entry variants of the Enjoy transactions, you can choose up to five generic fields under the technical name ACGL_ITEM_GEN-GEN_CH and occupy these fields with your customer fields.

    1. Include the desired fields with the following IMG activity:

      Start of the navigation path Financial Accounting (New) Next navigation step Financial Accounting Global Settings (New) Next navigation step Ledgers Next navigation step Fields Next navigation step Customer Fields Next navigation step Include Customer Fields in Enjoy Transactions End of the navigation path.

    2. You can use the transaction Transaction and Screen Variants (SHD0) to show the fields. On the Screen Variant tab, specify the desired Enjoy transactions (FB50, FB60, and so on) as well as the screen variants.

    3. In the field overview that appears, switch the desired generic fields in the Hidden column to visible by deactivating the Hidden indicator.

    For more information, see the documentation on the transaction SHD0. You call up the documentation by choosing the Online Handbook (Online Handbook) pushbutton in the transaction.

  6. Including Customer Fields in Document Splitting

    Document splitting is used to split posting data according to specific document splitting criteria defined in General Ledger Accounting. Typically, document splitting is used to create balance sheets at the profit center level or used for segment reporting. Nevertheless, document splitting can also be applied to customer fields. It can be used even to create balance sheets with customer fields.

    If you decide to perform document splitting using customer fields, we recommend examining your processes with regard to document splitting and drawing up a corresponding concept for those processes. In some circumstances, incorrect or incomplete document splitting settings can negatively effect General Ledger Accounting. See also SAP Note 891144Information published on SAP site.

    As with the standard fields, you can use the Required Entry Field and Zero Balance options for customer fields. You should use no more than two or three fields - standard fields and customer fields alike - for document splitting. If you intend to use more fields for document splitting, you should seriously consider whether you really need to create a complete balance sheet for all dimensions.

    You make the document splitting settings under Start of the navigation path Financial Accounting (New) Next navigation step General Ledger Accounting (New) Next navigation step Business Transactions Next navigation step Document Splitting End of the navigation path.

    For more information on document splitting, see Document Splitting.