SAP ABAP IMG Activity SIMG_CFMENUOLMEXOMFJ (Maintain Transfer Structure)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM (Application Component) Customer Relationship Management
     ⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       ⤷ ME0C (Package) Customizing R/3 Purchasing
IMG Activity
ID SIMG_CFMENUOLMEXOMFJ Maintain Transfer Structure  
Transaction Code S_ALR_87002059   IMG Activity: SIMG_CFMENUOLMEXOMFJ 
Created on 19981222    
Customizing Attributes SIMG_CFMENUOLMEXOMFJ   Maintain Transfer Structure 
Customizing Activity SIMG_CFMENUOLMEXOMFJ   Maintain Transfer Structure 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_CFMENUOLMEXOMFJ    

In this step, you create the data structures for the purposes of data transfer. The step covers the following activities:

  1. Extract the data that are to be transferred from the source system using a program you have written yourself and write the data to a sequential file.
  2. To use the SAP data structure definitions in your old system, you can run a record layout generator. This generates an INCLUDE in one of the programming languages COBOL, C, PL/1, or ASSEMBLER, according to choice.

Record layout

The following table structures are available for the record layout

BGR00     session record
BEBA0     BTCI header data
BEBAN     item data
BEBKN     account assignment
BKOMP     components
BLINES    text lines






























The files to be transferred are expected in the sequential file in the following order:

  • For each session, a session record (BGR00, record type 0)
    All further records up to the next session record are assigned to the last-read session.

  • For each transaction, a header record (BEBA0, record type 1)
    All further records up to the next header record are assigned to the last-read transaction.
    In addition to the transaction code, the header record contains all the data of the initial screen.

  • For each requisition item, a record (BEBAN, record type 2, table name BEBAN).

  • For each account assignment, a record (BEBKN, record type 3, table name BEBKN).

  • For each subcontracting component, a record (BKOMP, record type 4, table name BKOMP).

  • For each long text line, a record (BLINES, record type 5). With the table name, you can specify which text type is to be used. For example, use 01 as the table name for the item text with the text ID B01.

If a batch input structure is subsequently extended, the end of the structure is marked by a special field (SENDE). If you are already working with the new, extended structure, fill this field with the special character NODATA when initializing the structure. This enables the system to recognize whether the data are based on the old or the new structure when the structure is imported.

Note

Please note the following:

  • You can select comprehensive preliminary checks per parameter.

  • During creation, the number can be assigned either internally or externally.

  • You must define an entry for each field. This can be:

  • an explicitly entered field value (to transfer a certain value)

  • a blank character (to delete an entry when changing)

  • a special character (to transfer no value)
    The special character must be defined in the session record in the field "BGR00-NODATA".

  • You must define all fields in output format.

  • When transferring long texts, note that changes to the long text are not supported.

  • However, you can achieve this as follows:

    1st. transaction: deletion of long text.
    2nd. transaction: re-creation of long text.

  • In the standard system, the format 'New paragraph' (*) is set for the first line of the long text.
    The format 'New line' (/) is also allowed although it corresponds to the character for 'NODATA'; that is to say an assigned format is always adopted.

  • If you wish to use INCLUDEs in a standard text, you must enter them as a line of long text in the following form:

    INCLUDE TEXTXY OBJECT TEXT ID ST LANGUAGE E

    For performance reasons, you should use the separate SAPscript
    tool when transferring long texts.

  • Note the following rules regarding authorizations when running the sessions:

  • If a session is run in the foreground, the user running it must have the appropriate authorizations to maintain purchase requisitions.

  • If a session is run in the background, the user entered in the session record under "USER-ID", must have the appropriate authorizations to maintain purchase requisitions.
Business Attributes
ASAP Roadmap ID 253   Create Data Transfer Programs 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 1   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 SIMG_CFMENUOLMEXOMFJ 0 HLA0006039 Purchase Requisitions 
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 OMFJ OLMEXOMFJ C MM-PUR record layout for batch input requisition 
History
Last changed by/on SAP  19981222 
SAP Release Created in