ALE

 Segment Creation WE31

 Basic IDOC Type Creation WE30
 Message Type Creation: WE81
 Assign Message Type to Basic IDOC Type: WE82
 Distribution Model BD64
 Writing Report Program SE38
Partner Profile WE20
Message control NACE
 Check IDOCs WE02, WE05

Conversion Rule

 Maintain Conversion Rules - BD62

 Create Conversion Rule BD55
 Make Changes in the conversion rule - BD79

Change Pointers

 Activate change pointer - BD61

 Activate change pointer for message type BD50
 Segment Field-Change Document field- BD66

CIF VS IDocs

In decentralized EWM systems SAP recommends creating reduced IDoc Z-message types for MATMAS, CREMAS and
DEBMAS. The key reason being by reducing the number of segments and fields, we are also reducing the number of
customizing tables that need to be synchronized between both the systems. Thus, we are only sending the data to EWM
from ERP which is necessary to drive the process in EWM, not all the data fields would be needed in EWM, unlike ERP.

Screen Painter - SE51

 Components of a Class:

1. Attributes

 Static Attributes
 Instance Attributes

2. Methods

 Static Methods
 Instance Methods - Methods which can be ONLY called using the object reference. Instance methods can
access instance attributes and instance events

3. Events

4. Interfaces
Constructors
Constructors are special methods that are called automatically, either while creating an object or
accessing the components of a class. Constructor gets triggered whenever an object is created. 

Attributes
Attributes are data fields of a class that can have any data type such as C, I, F, and N. They are declared
in the class declaration. These attributes can be divided into 2 categories: instance and static attributes.
An instance attribute defines the instance specific state of an object. The states are different for
different objects. An instance attribute is declared by using the DATA statement.
Static attributes define a common state of a class that is shared by all the instances of the class. That is,
if you change a static attribute in one object of a class, the change is visible to all other objects of the
class as well. A static attribute is declared by using the CLASS-DATA statement.
Methods
A method is a function or procedure that represents the behavior of an object in the class.

INTERFACE is not a class. It is an entity which CANNOT have an implementation. It can only have EMPTY
method declaration and components. INTERFACE components are always PUBLIC. INTERFACE is a
concept by which the same method names will behave differently in different classes. The point to be
noted is, INTERFACE just contains methods WITHOUT any implementations. INTERFACE helps in re-
usability and maintain standard project framework.

An object is a pattern or instance of a class.

What is an Abstract Class?

1. Abstract Class is a special kind of class which can’t be instantiated. We can only instantiate the
subclasses of the Abstract class if they are not abstract. Abstract class should at least contain
one abstract method. Abstract methods are methods without any implementation – only a
declaration. We can certainly define the variables referencing to Abstract class and instantiate
with specific subclass at runtime. We can achieve Polymorphism by using an abstract class.

2. Constructors

Constructors are special methods that are called automatically, either while creating an object
or accessing the components of a class. Constructor gets triggered whenever an object is
created, 
Differences

Since both abstract class and interface are different entity, they have few differences:

 Multiple Inheritance: We can achieve multiple inheritance using Interfaces. Since ABAP doesn’t support more
than one Super class, we can have only one abstract class as Super class.

 New Functionality: If we add a new method in the Interface, all the implementing classes have to implement
this method. If we don’t implement the method, it would result into Run-time error. For Abstract class, if we
add a non-abstract method, its not required to redefine that in each and every inherited class.

 Default Behavior: We can have a default behavior of a non-abstract method in abstract class. We can’t have any
implementation in Interface as it only contains the empty stub.

 Visibility: All interface components are PUBLIC by default. For Abstract class, we can set the visibility of each
component.

Static class - Static methods are methods which can be called irrespective to the class instance. You can access only static
attributes and static events within the Static method.

Down Cast means assigning the reference of a Super Class back to a Subclass. Those objects which refer to the Super
Class can also refer to the Subclass reference at the runtime.

To sum up, when we assign the reference of Parent Class to Child, it is termed as Widening Cast or Down Casting. When
Child Class reference is assigned to Parent Class, it is termed as Narrowing Cast or Up Casting

What is Customer Exits?

Customer exits are "hooks" provided by SAP within many standard programs, screens and menus on which customers
may "hang" custom functionality to meet business requirements.  

1. Function Module Exits

2. Screen Exits

3. Menu exits

Syntax: CALL CUSTOMER-FUNCTION '004'

Format: CALL CUSTOMER-SUBSCREEN CUSTSCR2
Format: +CUS (additional item in GUI status)

What is a USER EXIT?

User Exit serve the same purpose as Customer Exits but they are available only for the SD module. The exit is
implemented as a call to a Function Module. The code is written by the developer.
 Well know User Exit in SD is MV45AFZZ

 USEREXIT_FIELD_MODIFICATION - To modify screen attributes.

CIF

 CFM1 - Create Integration Model, Program name: RIMODGEN

 CFM2 - Activate Integration Model, Program name: RIMODACT   

 Background Transaction: CFM3, Report: RIMODAC2, Initial transfer report: RIMODINI 

 The table which connects ERP and SCM Products is: /SAPAPO/MATMAP

 CFM5 - Search for Filter Objects in Integration Model 

 Function Module: CIF_PRODUCT_SEND > It hands over the data from ERP to the SCM side
 User exit at ERP side to enhance product transfer via CIF: EXIT_SAPLCMAT_001 (via SMOD =
CIFMAT01 / Components)
 Function Module: /SAPAPO/CIF_PROD_INBOUND > It receives the data to SCM side

 CALL METHOD lv_badi->exit_/sapapo/saplcif_prod_001  > The SMOD_APOCF005 is called

CALL FUNCTION '/SAPAPO/DM_PRODUCTS_MAINTAIN'   > Products are maintained in the
database incl. change document registration. Enhancement option: EXIT_SAPMMDUSER_005

 Function Modules: /SAPAPO/DM_PRODUCTS_POST (database operations) and

/SAPAPO/DM_PROD_POST

 CALL FUNCTION '/SAPAPO/DM_SUP_PLANT_MAINTAIN'  > Maintain Supplying Plant