SAP® Documentation

Single view

/PM0/ABP_DC_CHECK_FM_STRUC - Check Consistency of DC FM, UBOI FM, and UBOI Structures

BAL_S_LOG - Application Log: Log header data   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

This report primarily checks the consistency between the UBOI-FM structures and the related DC-FM structures. It also checks whether the UBOI-FM structures are compatible with the UBOI data structures (persistent, transient).

Integration

Prerequisites

Features

Selection

  • Check All DC Tables
The data container tables are the starting point for any check. There are two ways of specifying which tables are to be checked.
  • If this checkbox is selected, the data container tables to be checked are determined from the entities entered in tables /PM0/ABP_BTXCCTE and /PM0/ABP_BTX_CTE.

  • If this checkbox is not selected, all tables that technically look like data container tables are checked.

  • Also Display Matches
If you select this checkbox, any matches that are found are also displayed.
  • Ignore OID Warnings
There are a series of UBOI-FM fields that end in _OID and for which there are no corresponding fields (with the same name) in the UBOI data structures. The user is informed about these with a warning.
  • If this checkbox is not selected, this warning is displayed.

  • If this checkbox is selected, this warning is suppressed.

  • Ignore Superfluous Fields
If there are UBOI-FM fields without related UBOI data fields or more DC-FM fields than UBOI-FM fields, the user is informed with a warning.
  • If this checkbox is not selected, this warning is displayed.

  • If this checkbox is selected, this warning is suppressed.

  • Also Consider /PMB/ Objects (Optional)
You should only select this field if there are problems with /PMB/ objects. These /PMB/ objects are obsolete and are no longer used.
  • RFC Destination (Optional)
If an RFC destination is specified, the following checks are run in addition to the above checks:
  • The includes for the persistent fields are compared with those in the RFC destination.

  • The includes for the transient fields are compared with those in the RFC destination.

  • The includes for the UBOI-FM structures are compared with those in the RFC destination.

  • The includes for the DC-FM structures are compared with those in the RFC destination.

Note: The system checks whether a local system field exists in the structure or table of the same name in the RFC destination, and vice versa. The other properties of the field definition (data element, domain, and so on) are not checked.
  • RFC System
This field is currently not used.

Standard Variants

The standard settings are as follows:

  • Check All DC Tables
  • Do Not Display Matches
  • Ignore OID Warnings
  • Ignore Superfluous Fields

Output

The results of the check are displayed in an ALV list. The columns in this list have the following meanings:

  • Entity
The core name of the entity together with the letters of the line of business (if both have been determined).
  • First Table/Structure
  • Category: A rough classification of the structure or table in question. For example, DC-TAB for data container table or UBOI-FM for the UBOI-FM structure.

  • Field Position: The position number of the field in question (if relevant).

  • Field Name: The name of the field in question.

  • Second Table/Structure
  • Category: A rough classification of the structure or table in question. For example, DC-TAB for data container table or UBOI-FM for the UBOI-FM structure.

  • Field Position: The position number of the field in question (if relevant).

  • Field Name: The name of the field in question.

  • Error Status
An icon that indicates the severity of the error.
  • Info
A descriptive text that explains the error.
  • Intermediary UBOI-FM Structure
When the name of the UBOI-FM structure is determined from the name of the data container FM structure this can sometimes lead to an incorrect result. Only an additional conversion step can determine the correct name of the UBOI-FM structure. The "interim result" is displayed in this column.

Activities

After you have run the report you must check the result by visual examination. This is mainly because the algorithm is relatively stringent and can overlook some anomalies.

An error has occurred if:

  • There is no UBOI-FM field with the same name for a UBOI data field
  • There is no DC-FM field in the same position for a UBOI-FM field

There is a minor hitch in the algorithm if:

  • There are more DC-FM fields than UBOI-FM fields
  • There is no UBOI data field for a UBOI-FM field

In addition to checking whether a field exists in the DC-FM in the same position when the system compares the UBOI-FM structure with the related DC-FM structure it also checks whether the name of the DC-FM field complies with the corresponding rule.

The rule governing the naming of such fields states that:

  1. If the name of the UBOI-FM field is longer than 14 characters, only the first 14 characters are considered. Character 15 and subsequent characters are ignored.
  2. If the UBOI-FM field name has to be abbreviated, add _X at the end.
  3. If there is already a field with the above name in a different position, add _Y instead of _X.
  4. If this field already exists in another position in the DC-FM structure, add _Z instead of _Y.
  5. There is currently no stipulated replacement for _Z.

If the rule governing the naming of the DC-FM structure field has not been complied with, the system displays a corresponding message in the results of the check. However, this does not mean that an error has occurred. The message can be ignored if the two fields in question belong together. If these two fields do no belong together, then this message indicates that the sequence of the fields in the two structures is not the same or that there are too many fields in one of the structures and not enough in the other.

This report should therefore always be called when changes have been made to the UBOI structures (persistent, transient, field modifier) or to the structures and tables of the data container (specifically the DC-FM structure).

Example






General Data in Customer Master   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 8645 Date: 20200226 Time: 134513     sap01-206 ( 47 ms )

Our Service

Looking for Support? Questions?

The

Consolut

Callback-Service

Leave us your contact details and we will call you back. Panels marked with * are mandatory.