Ansicht
Dokumentation

_FICAODN_ODNSUBID - Define Sub-IDs for Document Class Determination

_FICAODN_ODNSUBID - Define Sub-IDs for Document Class Determination

ROGBILLS - Synchronize billing plans   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.
SAP E-Book

In this Customizing activity, you define sub-IDs that enable you to adapt document class determination for ODN to your requirements. Sub-IDs allow you to control document class determination at a very detailed level based on the values of certain document attributes.

Note
Sub-IDs are available only for Convergent Invoicing in Extended FI-CA (S), Telecommunications (T), Media (M), IS-Utilities (R), and Public Sector (P).

In this Customizing activity, you define the following:

  • Attribute set: You define one or more sets of application-specific database fields according to your requirements (for example, document type, item type, and business place).
  • Metadata schema: You define the required country/region-specific metadata schemas, to which you can assign an attribute set. You specify a valid-from date for each schema.
  • Sub-ID: You define one or more sub-IDs for each country/region-specific metadata schema. For each sub-ID, you specify the values of the attributes that are derived from the attribute set that is assigned to the metadata schema.

You can assign sub-IDs to document classes in the Customizing activity Assign Document Classes to Document Types and Origin Keys. The system determines the sub-ID, and therefore the document class, based on the relevant country/region-specific metadata schema and the values of the attributes that are assigned to the sub-ID.

When the system assigns an official document number to a document, it does the following:

  1. Determines the relevant country/region
  2. Determines if there is a valid metadata schema for that country/region with an attribute set assigned to it
    Note that if there is a valid metadata schema, but it does not have an attribute set, sub-ID determination is deactivated.
  3. Checks if country/region-specific sub-IDs are assigned to the schema

If sub-IDs are assigned to the schema, the system does the following:

  1. Determines the relevant sub-ID by comparing the values of the attributes specified for the sub-ID (for example, document type 01, item type 0TAXITEM) with the values in the document that requires an official document number.
  2. Checks if the sub-ID is assigned to a document class in the Customizing activity Assign Document Classes to Document Types and Origin Keys.

    Based on the result, the system does the following:
  • If the sub-ID is assigned to a document class, the system uses this document class and the related number range to number the document.

  • If the sub-ID is not assigned to a document class, the system does not number the document.

Convergent Invoicing:

To use sub-ID determination for Convergent Invoicing, you have assigned the following function modules as installation-specific function modules in Customizing for Contract Accounts Receivable and Payable under Program Enhancements -> Define Customer-Specific Function Modules:

  • FKKINV_EVENT_2658_XX_GEN
  • FKKINV_EVENT_2667_XX_GEN

For more information see the documentation of the corresponding sample function modules FKK_SAMPLE_2658 and FKK_SAMPLE_2667.

IS-Utilities:

Business function ISU_LOC_ODN_SUBID, IS-U Localization ODN Sub-ID must be activated in your IS-U system. Go to transaction SFW5.

To use sub-ID determination for IS-Utilities, you have assigned the following function modules as installation-specific function modules in Customizing for Contract Accounts Receivable and Payable under Program Enhancements -> Define Customer-Specific Function Modules:

  • ISU_EVENT_R431_ODN_XX_GEN must be assigned to event R431.

For more information see the documentation of the corresponding sample function modules ISU_SAMPLE_R431.

Note
Sub-ID in IS-U is not used for the following country: Slovenia.

In the standard system, you can use sub-IDs only for the applications that are offered in the input help of the Application Type field.

To use sub-IDs for document class determination, make the following settings:

  1. Define an attribute set (name and description) and assign database fields to the attribute set.
    When you assign the fields, you must specify the sequence in which the system checks the fields when it determines the sub-ID.
  2. Define a metadata schema for each relevant country/region.
    You specify the valid-from date of the schema, and you can assign an attribute set to it.
    Note that if you do not assign an attribute set, this deactivates sub-ID determination as of the valid-from date of the schema. This enables you to deactivate sub-ID determination for a country/region for which a different schema is already in use.
  3. Define the required sub-IDs for the country/region-specific metadata schema.
    You enter the sub-ID and a description. Note the following:
  • You cannot use sub-ID 999 or 000 because these values are used to control sub-ID determination. The system returns sub-ID 000 if sub-ID determination is deactivated. It returns sub-ID 999 if no suitable sub-ID was found for the document. For more information, see the documentation of the Sub-ID field.

  • A sub-ID can be used in different schemas for a specific country/region, but the meaning of the sub-ID should always be the same in the different schemas.

  1. For each sub-ID, specify the attribute values that enable the system to determine the sub-ID at runtime.
    The system displays the fields in the sequence defined in the attribute set (from left to right). You can enter a specific value, or you can use a wildcard ("*") if you want to define a generic assignment rule for the assignment of a sub-ID.
    If you create both generic and explicit assignment rules, the value ranges of the fields derived from the attribute set may overlap. In this case, the system always considers the more specific rule first and then the more generic one, regardless of the order in which you enter the assignments in the system.
Note
You can use the report Simulation of ODN Attributes (RFICA_ODN_ATTR_SIM) to check the Customizing settings for sub-ID determination. The report simulates the determination of the sub-ID for specific attributes (for example, country/region, application, and date) or for a specific invoice. You use transaction SA38 to call the report.

You want to use different numbering for invoices, credit memos, and debit memos. To do this, you must assign the CORRCAT field to the attribute set. When you define the sub-ID determination for the schema, you must enter the following values for the CORRCAT field:

  • Invoices: " "
  • Credit memos: "C0"
  • Debit memos: "D0"






BAL Application Log Documentation   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.

Length: 8133 Date: 20240523 Time: 171222     sap01-206 ( 129 ms )