P. 1
LSMW

LSMW

|Views: 260|Likes:
Published by Md Rehan
LSMW
LSMW

More info:

Published by: Md Rehan on Jan 29, 2013
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

10/30/2014

pdf

text

original

In a field withABAP processing type, the contents of the corresponding field of the customer
structure is processed before the respective field in the automation data structure is
populated. You can determine the correct value for a field in the automation data structure
using this field rule to access database tables and perform calculations or further processing.
Figure 4-3 shows theField Rule Maintenance screen.

Figure 4-3 Field Maintenance Screen

To implement the code, choose the

button in theRule sub-screen and use the following

symbolic variables:

o$C$ is used as the placeholder for the field in the customer structure.

o$S$ is used as the placeholder for the field in the automation data structure.

Migration of FI-CA-Based Industry Solutions – IS Migration Workbench

Version 1.02

86

@ Copyright SAP AG 2009

The load program generator replaces the symbolic variables using the correct field
references to the fields in the customer and automation data structure when you generate
the load report. The simplest code is $S$ = $C$. This moves the information from the field
of the customer structure to the automation data structure without further processing. A more
complex example is shown in Figure 4-4 ABAP Code in ABAP field Rule
. This code is implemented for the BU_RLTYP field of PARTNER migration object.

Code in ABAP Rule

Generated Code in Load Program

Figure 4-4 ABAP Code in ABAP field Rule

The load program generator replaces the symbolic variable $C$ with the correct reference
z_EMG_EKUN_INIT-BU_RLTYP and the symbolic value $S$ with EMG_EKUN_INIT-
BU_RLTYP.

You can change the length of the field in the customer structure. To do this, mark theAltern.
Field Lgth field and enter the desired field length in theCharacters field. Instead of defining
the field in the customer structure with its original data dictionary attributed, the field is now
defined as a character field with the entered number of characters. We recommend using
this option when the field is defined in the data dictionary with the data type P (packed
number) or I (integer).

The load program generator implements the execution of a conversion exit if one is defined
in the dictionary for this field. The conversion exit will process the field in the automation
structure.

It is technically possible to reference any field of the customer structure by preceding the field
name by the symbolic variable$C$- (for example, $C$-fieldname) or any field of the
automation data structure by preceding the field name by the symbolic variable$S$- (for
example, $S$-fieldname). The load program generator replaces these symbols with the
respective structure name instead of the complete field reference of the field that is currently
processed. Even if it is possible to access all fields, the implemented ABAP code should be
restricted to operate on only the field for which the field rule has been defined, except for
custom fields (for more information, see chapter 4.4.1Additional Fields in the IS Migration
Workbench). This is because the load program generator determines the order of the
execution of the field rules. There is no guarantee that a field in the automation structure has
already been populated by another field rule when processing the ABAP code field rule.

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->