SAP ABAP IMG Activity SIMG_XXAK_OXK3 (Edit Coding Block)

Hierarchy

☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM (Application Component) Customer Relationship Management
     ⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       ⤷ GBAS (Package) FI-SL Customizing / integration / Basis

IMG Activity

ID	SIMG_XXAK_OXK3	Edit Coding Block
Transaction Code	S_ALR_87006426	IMG Activity: SIMG_XXAK_OXK3
Created on	19981222
Customizing Attributes	SIMG_XXAK_OXK3	Maintain Coding Block
Customizing Activity	SIMG_XXAK_OXK3	Maintain Coding Block

Document

Document Class	SIMG	Hypertext: Object Class - Class to which a document belongs.
Document Name	SIMG_XXAK_OXK3

In the coding block of the system you can create your own fields. The new coding fields can then be used in:

• FI G/L accounts
• MM inventory management
• MM purchasing

These new fields are also updated in the line items created in the Controlling applications.

If you have created customer fields, they are updated by the system during automatic postings. To enable you to post these fields in the Enjoy transactions manually, you must assign the fields to the entry variants in the Enjoy posting transactions. To do this, choose Include Customer Fields in Enjoy Transactions.

Requirements

You require a test system in order to include coding fields.

The changes are recorded in the test system in a transport request and can thus be transported into other systems.

To include coding fields, you require the following authorizations:

• New field inclusion in coding block         X_COBLMOD
• Maintenance of cross-client tables            S_TABU_CLI   
• Dictionary authorization                        S_DEVELOP   
• Transport authorization                        S_TRANSPRT   

Recommendation

We recommend that you create a concept for your own coding field as early as possible and make the necessary changes to the coding block.

Caution

Define the final format (data type and length) for the new coding field as soon as possible. You cannot make subsequent changes to the field format or delete a coding field once it has been included using standard methods (see also the additional technical information).

Check whether a suitable standard SAP coding field already exists that fulfills your requirements. If this is the case, use that field, otherwise create a new coding field.

As soon as a client has been flagged as a production client in a system, the Include fields function is locked for that system. This ensures that no subsequent changes can be made.

The system adds the newly included coding fields to the existing ABAP Dictionary tables.

Changes to the ABAP Dictionary tables can, in the case of errors, lead to a loss of data. Carry out a backup before you insert coding fields.

During the execution of these Dictionary operations, no other users should be working in the system. Any other users working in parallel in the system could be hampered by the DDIC activities.

Cross-client objects are maintained with this function. The maintenance of these objects thus affects all the clients in the system.

Activities

Basic and expert modes are available for this function. The default setting is the basic mode. If the basic mode covers your needs, you should use this mode.

Basic Mode

1. Choose Include fields.
2. Carry out the necessary settings in the Process control group box.
3. Enter the development class.

   The development class must be assigned to a transport layer that has the same target system as the SAP standard objects.

   We recommend that you create your own development class to extend the coding block.

4. In basic mode, you can insert one or more fields in the coding block. You must make the following entries for each new field:
• Field Name
Enter the field name here using the following name convention: The field name must begin with ZZ or YY.
• Field Description
Enter the field description here that is to appear on the subscreens.
• Data Type
CHAR or NUMC are offered as data types for a coding field. CHAR has an ALPHA conversion, that is, numerical values are portrayed internally with leading zeros.
• Field Length
The field length must not exceed 22 characters.
5. Choose the Test run function.

   The system simulates a production run and tests whether your entries are valid.

6. When you remove the flag from the Test run field, you automatically set the production run status.

   In the production run, you are asked to enter a correction number and a repair number for table BSEG. Both specifications must be contained in the same transport request in order to import the enhancement correctly into the EDI subsystem. The system creates a log of all the changes you have made, allowing you to analyze any errors that occurred in the Dictionary functions performed during this transaction.

7. Choose Execute.

   Note
   Once you have made your entries in the process control, you can make other settings. For more information see Further steps below.

   As of SAP Basis Release 7.00, you can add your own coding fields to table BSEG without modifications. To do this, you have to include the structure CI_COBL in your APPEND structure. This APPEND structure can be included in BSEG afterwards, so that all customer fields are included in table BSEG implicitly by means of CI_COBL. For more information about this procedure and for a description of how you can subsequently still swap out customer-specific fields into an APPEND structure, see SAP Note 1451330.

Expert Mode

Use the expert mode if you cannot carry out your settings using the basic mode. In order to work with the expert mode, you must have ABAP Dictionary knowledge. The expert mode allows you to perform step-by-step all the functions that the basic mode carries out automatically in the background. This affords you greater freedom when defining the various parameters you require. The individual steps involved include:

1. Choose Coding fields -> Expert mode.
2. Create domain.

   Create a domain for the new coding field.

   If required, you can enter fixed values or a check table for this domain.

   Note:

   The complete functionality is only available for the fields of data types CHAR and NUMC in all transactions that use the coding block. For other data types such as amount and date fields, problems can occur in various transactions, and they can only be avoided with a customer-specific modification.

3. Create data element

   Create a data element for the new coding field.

4. Include field general

   Incorporate the new field in the include structure CI_COBL.

   CI_COBL has been included in all the tables relevant to the coding block, so that new field can thus be entered in these tables.

5. Include field BI

   Incorporate the new field in the include structure CI_COBL_BI.

   This structure is used in FI for entering documents in batch. If you have been working in expert mode and have used a format other than CHAR for your new field, you also have to add a field with format CHAR and the same output length as your new field for use with this include. You may have to define an appropriate data element and the relevant domain as well.

6. Include field BSEG

   Caution
   The new field must be added to the end of table BSEG.

   Note
   As of SAP Basis Release 7.00, you can add your own coding fields to table BSEG without modifications. To do this, you have to include the structure CI_COBL in your APPEND structure. This APPEND structure can be included in BSEG afterwards, so that all customer fields are included in table BSEG implicitly by means of CI_COBL. For more information about this procedure and for a description of how you can subsequently still swap out customer-specific fields into an APPEND structure, see SAP Note 1451330.

7. Include ST entries

   Using the Include control entries function, you can maintain the appropriate system control tables automatically. This makes the new field available in Customizing just like any other standard SAP field.

8. Delete ST entries

   You can delete these control entries as long as there are no Customizing entries related to the field in question. Although deleting the control entries suppresses the field in Customizing, it still exists on the database and cannot be deleted using standard functions without leading to a loss of data.

9. Choose Execute.

   Note
   Once you have made your entries in the process control, you can make other settings. For more information, see Further steps below.

Further Steps

• Create subscreen

  You can define suitable subscreens for your new field using the function Environment -> Create Subscreen. (See Define Subscreens for the Coding Block. For an overview of subscreens, choose Environment ->Subscreen).

• Check Field Entries

  You can check the field entries in

Business Attributes

ASAP Roadmap ID	203	Establish Master Data
Mandatory / Optional	1	Mandatory 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_XXAK_OXK3	0	HLA0001333	Account Assignment Combinations

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
OXK3	T - Individual transaction object	OXK3	9999999999	☐	☐	Maintain Coding Block

History

Last changed by/on	SAP	20040226
SAP Release Created in