Cost Center and HR master exits and BADIs

FOR COST CENTER master

1. Determine the receiving Partner Profile to receive.
2. Put COSMAS as message type on the receiving partner (only specified partner will have the  extended sgment)
3. include YCOSMA01 as the extended idoc for COSMAS mess type basic idoc COSMAS01
4. add additional code in badi :
   implementation name: ZCOOM_CI_CSKS_IDOC
   definition name: COOM_CI_CSKS_IDOC
   interface name: IF_EX_COOM_CI_CSKS_IDOC
   implementing class: ZCL_IM_COOM_CI_CSKS_IDOC

       CODE: upload data to segment as long as cost center date is valid.

FM: MASTERIDOC_CREATE_SMD_COSMAS <--- exits can be found here

Configuration for message type HRMD_A change pointer

1. Use message type hrmd_a (Your custom IDoc should have a Message Type and the Change Pointer should be activated for this Message Type. You can activate this via transaction SALE)
2. Use bd59 to define ALE obj
3. Activate change pointer globally in bd61

Just a checklist for ALE change pointer configuration

I want to share the steps in ALE/IDOC/EDI configuration. 

Below are the steps to look at in creating change pointer. The ff. steps are standard all across SAP IDOC/EDI/ALE related projects. No matter what you are aiming for as long as change pointer or IDOC is concerned, you are required to consider the steps below:

1. SM59(Create RFC destination)
2. WE21(Create TRFC-PORT)

Change pointer in IDOC (when data was changed)

Change pointer is the process in SAP IDOC triggered every time there are changes on master tables for both fields and records. Thus, for example you add or edit any information with your customer information and once change pointer program has been triggered, then that is also the time it will be populated and will create an IDOC. Change pointer can also be setup in a customized IDOC or message type.

Transferring/receiving data from SAP r/3 to other box or third party software

Many existing organizations run their business from a different systems or platforms. This may include SAP R/3, JAVA J2EE, .NET or legacy systems such as Mainframe/COBOL.

In legacy systems, transferring data is usually done through a dump file or a txt file which has been formatted according to agreed format with the handler system.

In SAP, transferring data is done through IDOC using ALE and EDI technology.

IDOC stands for intermediate document comprises of a segment and fields that forms a certain file layout. In non-SAP system, their IDOC is commonly referred as the input and output dump file or simply text file. In SAP, it is quite more sophisticated and intact. IDOC in SAP world is used as a medium of transferring data to one box or to a third party software.


IDOC will work only by configuring it with ALE and EDI technologies. ALE stands for Application Link Enabling or a technology incorporated by SAP to synchronize and to manage the changes done between data of separate  boxes within SAP only.


EDI stands for Electronic Data Interchange. This serves as the medium to transfer or to communicates the IDOC to other system outside SAP in order for them to be transferred and delivered successfully.

Function Exit in SAP DMEE

Introduction:


Data Medium Exchange Engine (DMEE) is where you define the fields of your FTE or IDOC.


It is defined also by SAP AG as:
    The Data Medium Exchange Engine (DMEE) enables you to define file formats that meet the requirements   of your financial institution. This is particularly important as there is no worldwide or regional standard. In some cases, no country standard exists and the file must comply with bank-specific standards. With no ABAP programming knowledge required, this tool enables you to flexibly define new formats and to efficiently modify existing ones. In addition, DMEE can be used by calling applications to generate a DME file.

Objective:


In this topic, I will show you how to use the function exit in DMEE of a certain bank of a country.