Definition of Data Elements at Data Section Level

Use

You can maintain your own data so that it is fully integrated into standard maintenance of business location master data.

Features

For information about the basic concept and steps required for implementing user-defined data elements for business locations, see Definition of Characteristic Data Elements for Locations .

The following differences apply to user-defined data elements at data section level:

Data sections are integrated into standard SAP Oil & Gas screens as subscreens:

Data sections can be used and called at business location type level and at business type level. This makes coding of the user exit slightly more complex.

Activities

As in Definition of Characteristic Data Elements for Locations , function pool SAPLXOIF is used, but different user exits are called within this function pool. You find these user exits in enhancement OIFA0113 using transaction CMOD. This enhancement contains three exits:

EXIT_SAPMOIFA_113 SSR data sections: data transfer to customer work area

This user exit is used to pass general data to the function pool, and is called in the PBO of the SSR main screen. It transfers the following data:

Table OIFSPBL for the general location data
Table OIRBPBLB for the business-specific data.

In addition, it passes the:

Business type for which location maintenance was called
Address information for the business location.

EXIT_SAPMOIFA_114 SSR data sections: data section specific information to customer work area

This user exit is called in the PBO of the SSR main screen. It transfers the following data to the user function pool:

Specific data section data such as program name and screen number that is called (assigned in customizing)
Data section business type (which can be different from the business type in EXIT_SAPMOIFA_113)
Transaction type (create, change, or display)

EXIT_SAPMOIFA_115 SSR data sections: data transfer from customer work area

This user exit is called in the PAI of the SSR main screen. It transfers changes made to OIFSPBL and OIRBPBLB. If any changes occurred in the customer-defined subscreen in structures OIFSPBL or OIRBPBLB, the dataloss flag has to be set accordingly.

Recommendation

SAP recommends that you create APPEND structures to OIFSPBL for data at general business location level and APPEND structures to OIRBPBLB for data at business type level. The customer data section should contain mainly fields from the append structure. The standard SAP Oil & Gas transaction for maintenance of the location master automatically saves these fields to the database when you save entries.

End of the recommendation.

You can only make changes to fields delivered by SAP if you do not use those fields at another place in location master maintenance. Otherwise, the field value from the SAP field may overwrite the field value from the user-defined field or vice versa.

Note Note

When you are making changes to a business location at business type level, table contents from OIFSPBL (location general data) are passed to the subscreen pool only for informational purposes. Any changes to these fields will not be saved. Therefore, if you really need these fields at business type level, you should define them as display only fields.

End of the note.

If you simply use customer data sections for maintaining data at the general level or data from the same business type (meaning transaction business type equals data section business type), you code the user exit and the screen logic as described in Definition of Characteristic Data Elements for Locations .

If you want to display data from different business types (for example, display shop information when you are maintaining the business location for fuels), more complex coding is required.