Entering content frame

Procedure documentation Adding Customer Attributes to Core Object Entity Locate the document in its SAP Library structure

Prerequisites

You have decided to enhance the core entity using the criteria mentioned in Selecting and Implementing Customer Enhancement Types .

Procedure

1

If necessary, familiarize yourself with the contents of the BDT developers' handbook. Pay particular attention to the following points:

  • Function overview
  • Basic settings
  • Applications
  • Function overview
  • Dialog
  • Program logic
  • Implementation schedule
  • New table fields and new tables
  • New table field through participating application
  • Implementation schedule
  • New object part
  • Implementation schedule
  • Enhancing screen layout and sequence

2

Create a function group for processing the enhancement fields and define the screen fields in the global memory.

3

Create the APPEND structure for the table CACS_CTRTBU in the DDIC. A prerequisite here is that all other necessary data dictionary objects have already been created (data elements in the customer name range, value tables, and so on).

4

Write the coding for the PAI and PBO routines necessary for each view and define the screens.

Entries in the screen fields are checked in the PAI routines, values are converted to the internal format, depending on their type, and transferred to the internal tables. PBO routines transfer any converted values from the internal table to the screen fields.

Caution

  • You must always work with the current version.
  • If you want to carry out checks on standard fields (in addition to the standard checks or in combination with enhancement fields), you can do this using functions that must first be defined in the BDT under Further checks. The PAI routines for standard views cannot be replaced with customer routines.

Note

Further information:

  • Sample coding for standard PAI and PBO routines.

5

Using the area menu CACSBDT, create the BDT entries required for screen layout (field groups, views, sections, screens) for the new fields.

6

In the area menu CACSBDT, make the necessary assignments using AssgnScrnField ® DBField.

7

Create the necessary function modules at the following events for processing the enhancement fields for this enhancement type.

8

In the area menu CACSBDT, define the function modules for the program logic using the path Events ® Assign Event ® Function Module.

Note

Other information:

9

Create a routine that corresponds to the form "get_val_dyn" in the sample coding (you can give it any name). This calls function CACS_CSC_GETACTVERS, which determines the version to be displayed. The current screen values are determined from the internal table, which contains the current data for the commission contract (in conjunction with the version currently valid), and then they are transferred to the BDT work structure with the screen output fields (fields of the same name - the rest must be transferred explicitly, for example in the ISDST module).

Note

You will find program examples here that you can use to program event modules for this change type.

Result

You have carried out all the necessary activities, and you can now begin testing the commission contract and its enhancements.

 

 

 

 

 

 

 Leaving content frame