SAP ABAP IMG Activity SIMG_SSR_0156 (Define additional fields for value conversion)

Hierarchy

☛ IS-OIL (Software Component) IS-OIL
   ⤷ IS-OIL-DS-SSR (Application Component) Service Station Retailing
     ⤷ OIR (Package) SSR Service Station Retailing (master/overall)

IMG Activity

ID	SIMG_SSR_0156	Define additional fields for value conversion
Transaction Code	S_SO6_65000965	(empty)
Created on	20000919
Customizing Attributes	SIMG_SSR_0156	Define additional fields for value conversion
Customizing Activity	SIMG_SSR_0156	Define additional fields for value conversion

Document

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

SAP delivers a set of standard fields for which value conversion is supported in the interface. This field catalog contains material ID, service type and further fields.

In this step you can define additional fields.

First you need to define the field ID. Secondly, you need to specify all interface structures and the names which the field has within these structures.

NOTE: There are some fields that must not be defined for conversion:

• In the case of the retail network interface, location ID must not be converted in inbound structures. This is because the incoming location ID is used to find the conversion group in the standard system set-up. The location ID itself can only be converted in the business add-ins directly.
• The SAP currency key must not be converted in the outbound structures for the clearing house settlement message structures (ROIRHDTFK and ROIRHDTFP). This is because this key is needed in the outbound function for formatting the value fields and for retrieving the ISO codes. If you need to have a differently formatted currency key, you have to create a new field in its own settlement message structure and fill it in the appropriate business add-in.
• If units of measure or country codes are converted, the retrieval of ISO codes for these will not work any more.

For the structure names, examine the appropriate BAPI function in transaction SE37 and look up the parameter type.

BAPIs used are:

• BAPI_BLM_SAVEMULTIPLE for meter reading inbound processing
• BAPI_BLD_SAVEMULTIPLE for dip reading inbound processing
• BAPI_BLPCP_UPLOAD for payment card inbound processing
• BAPI_BLP_SAVECOMPETITORSURVEY for the competitor survey upload
• BAPI_BLP_COMPAREPRICES for price check inbound processing
• BAPI_BLP_RECEIVEMULTIPLE for price outbound processing
• BAPI_BL_RECEIVEDETAIL for location master outbound processing

In the case of clearing house settlement message outbound processing, the structures in which you can convert are ROIRHDTFK (for sales transaction headers) and ROIRHDTFP (for sales transaction items).

Example

For conversion of the incoming payment card data field CURRENCY, you could define :

• Field CURRENCY
• Structures BAPIBULOCPCP01 (type for the parameter PAYMENTCARDHEADERS of function module BAPI_BLPCP_UPLOAD)
• Structure field CURRENCY (field name within structure BAPIBULOCPCP01)
• Offset 234
• Length 5

In the subsequent Customizing step, Define conversion groups, you can then define the appropriate conversion record (for example, you can define "DOLLAR" to "USD" as an inbound record).

Requirements

Standard settings

Recommendation

Activities

Further notes

Business Attributes

ASAP Roadmap ID	151	Design interfaces
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	SIMG_SSR_0156	0	I400022112	Service Station Retailing

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
VC_OIRHCVFDDEFC	C - View cluster	SM34		☐	☐

History

Last changed by/on	SAP	20030617
SAP Release Created in