SAP ABAP IMG Activity TRFDUE_JBMU (Check Required/Optional Control)
Hierarchy
☛ EA-FINSERV (Software Component) SAP Enterprise Extension Financial Services
   ⤷ FIN-FSCM-TRM-TM (Application Component) Transaction Manager
     ⤷ FTAC (Package) R/3 customizing for Treasury money, forex, forward
IMG Activity
ID TRFDUE_JBMU Check Required/Optional Control  
Transaction Code S_ALR_87007865   IMG Activity: TRFDUE_JBMU 
Created on 19981222    
Customizing Attributes TRFDUE_JBMU   Check Required/Optional Control 
Customizing Activity TRFDUE_JBMU   Check required/optional control 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name TRFDUE_JBMU    

In this step you generate a list of the relevant fields that are required from the old/legacy systems to fill the receiver structure fields. The system interprets all relevant Customizing settings for this.

Requirements

Depending on the transfer category, different settings must have been made in Customizing. For the transfer category period values for example, the corresponding operating concern must have been created.

Activities

  1. Select the transfer category for which you wish to determine the required/optional fields. The system determines the corresponding receiver structure and displays the required/optional fields.
  2. Choose Display. You get to the screen with the required/optional fields.
  3. The fields to be filled with data are split according to priority:
    • 1: Required fields
      • Required fields contain information which must be imported (for example, company code for many categories). Data records, whose required fields are not filled, cannot be transferred.
    • 2: Dependent fields
      • Data is put into dependent fields when it may be required or left blank under certain conditions (for example, the field external partner ID only has to be filled if a business partner is going to be referenced by its external number during a transfer of accounts). Usually two or more dependent fields form a group from which a field will be filled while the others remain empty. This may be because they contain alternative information (for example external vs. internal account number).
    • 3: Optional fields
      • Optional fields contain information which is not absolutely necessary. You can however, use these fields to transfer additional information (for example, user-defined characteristics for transferring finance objects).
    • 4: Initial fields
      • Initial fields cannot be filled. For example, when transferring finance objects for accounts, of the key fields for the original objects, only the internal or external account number can be filled. All of the other origial object keys such as order number, loan number, etc. must remain empty. If initial fields are filled and transferred, the data content will be overwritten by R/3 data.
    • ?: Indefinite fields
      • For some transfer categories, additional Customizing settings are relevant for generating required/optional field display. You can enter or change these under Settings -> Change selection. The possible (or selected) settings are displayed in the header part of the list.

Additional functions

  • Display with documentation

    Under List -> Display with docu, you can display and print a list with the documentation for all fields.

  • You can also display the documentation for each field directly via F1 help (by placing the cursor on the field and pressing F1).
  • You can check the meaning of the columns in the displayed list also using F1.
    • Technical information

By double-clicking on a field, you can go to the ABAP Dictionary.

Example

You want to find out which fields in the receiver structure must be/can be filled. By selecting a transfer category, you can obtain a list of all the relevant fields. The colour of the column headed Rq/Op indicates whether a field is required or optional.

The system determines which fields are compulsory using the Customizing entries. Some additional fields are also required for the transfer itself. The list does not allow you to differentiate between the fields according to source.

You can control which structures within a transfer object are transferred via Record categories.

Activities

General Procedure for External Data Transfer

Further notes

Transfer mode

Record categories

Transfer categories

Transfer R/2 Financial Assets Management

Business Attributes
ASAP Roadmap ID 152   Design data acquisition 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG TRFDUE_JBMU 0 HLA0100063 O HLA0100104 O  
SIMG TRFDUE_JBMU 1 KFM0000003 Business Partner 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
IMGDUMMY D - Dummy object JBMU TRFDUEJBMU Display required/optional control 
History
Last changed by/on SAP  20000801 
SAP Release Created in