Google

ALE CODING WITH DISTRIBUTING OF CUSTOMER DATA FROM HR TO FI SYSTEM

Applies To:

ABAP

Summary

A business scenario and technical solution in detail to depict the customizing data distribution process through ALE along with some extra light on HR documentation.

By: Samasivarao

Date: 08 Jan 2006

Business Requirements

  • Standard tables, Custom table with HR-documentation maintained in HR system
  • Receiving SAP FI system make use of Master data Distributed from HR system, in developing a new custom application

Technical Solution

  1. Data Maintenance of standard tables in the HR systems
  2. Master Data distributed from HR system to FI system by ALE process
  3. A new custom table created in HR and FI System
  4. HR documentation maintained in HR system
  5. Custom table data distributed from HR to FI system via ALE customizing data distribution

Process in Detail

Custom Tables

  1. Custom tables created in HR and FI system with required fields. For Example, we create a custom table ZTIME to maintain time IDs.

Also we create a field to maintain Time ID documentation in the table.

Custom tables created in SE11 transaction with required fields, data elements, and domain. We just concentrate on HR documentation.

    1. Create a new field INFO in the custom table ZTIME with following attributes : Data type : CHAR

Data length: 1

Description : Time ID Documentation

Save; activate the table with extended table maintenance.

(Funk. Group ZTIME_EXT, Screen 0001)

INFO ZINF CHAR 1 0 Time id Documentation

    1. We need to design the ZTIME table maintenance screen for documentation field.

· Go to transaction se80.

· Enter Function group : ZTIME_EXT

· Select screen 0001.

· Go to Screen painter.

· Create a Pushbutton with following attributes :

EI type: Pushbutton

Name : DOCU_BUTTON

With Icon: X

Fctcode: 0%%%

Output field: X

  • Create a new PBO module in Screen 0001 flow logic :

MODULE HRDOC_LIST OUTPUT

IF STATUS-ACTION EQ AENDERN

OR STATUS-ACTION EQ ANZEIGEN.

DOCU_BUTTON = ICON_INFORMATION.

LOOP AT SCREEN.

IF SCREEN-NAME = 'DOCU_BUTTON'.

SCREEN-ACTIVE = 1.

SCREEN-INPUT = 1.

MODIFY SCREEN.

ENDIF.

ENDLOOP.

ELSE.

CLEAR DOCU_BUTTON.

LOOP AT SCREEN.

IF SCREEN-NAME EQ 'DOCU_BUTTON'.

SCREEN-INPUT = '0'.

SCREEN-ACTIVE = '0'.

MODIFY SCREEN.

ENDIF.

ENDLOOP.

ENDIF.

ENDMODULE.

Icon with ‘INFORMATION’ symbol will be passed at runtime.

C. Till now Custom table and a field for documentation is created. Now we need to write flow-logic modules in screen 0001 to invoke HR documentation. (Similar functionality of PDSY transaction).

  1. Create a Time id documentation class ‘ZTIME” in PDSY transaction with required attributes :

Document class : ZTIME

Obj.documentation : X

Client-specific: X

Object table: ZTIME

2. Create a PAI module ZHRDSYS_DOCU_EDIT_FUNX with following code.

CALL FUNCTION 'HRDSYS_VIEW_DOCU_EDIT'

EXPORTING

STATUS_ACTION = STATUS-ACTION

OFIELD1 = 'TIMEID'

OTYPE = 'ZTIME'

NEXTLINE = NEXTLINE

TABLES

EXTRACT = EXTRACT

TOTAL = TOTAL

X_NAMTAB = X_NAMTAB

CHANGING

FUNCTION = FUNCTION

XACTION =

ACTION =

EXCEPTIONS

FIELDNAME_ERROR = 1

INDEX_ERROR = 2

OTHERS = 3.

IF SY-SUBRC <> 0.

* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO

* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.

ENDIF.

D. Now custom table ZTIME is ready to maintain Timeid attributes and Documentation:

Go to transaction SM30.

Enter table name: ZTIME

Click on Information button to maintain documentation as follows:

Transport Entries of Standard Custom Tables

Whenever data is maintained in standard and custom table in a development client, a transport request is created.

There is no problem for the transport entries of standard table.

When we create a transport request for custom table, only table contents show up in the request. No objects related to Time ID documentation stored up.

We need to add some extra modules in the extended table maintenance.

    1. Go to transaction code SE11.
    2. Go to extended table maintenance screen of ZTIME.
    3. Go to Maintenance Events and maintain the following modules and events.

01 F_HRDSYS_SAVE_01

02 F_HRDSYS_SAVE_02

11 F_HRDSYS_TRANSPORT

    1. Maintain these modules in subroutine of function group ZTIME_EXT.

FORM F_HRDSYS_SAVE_01.

CALL FUNCTION 'HRDSYS_VIEW_SAVE_01'

EXPORTING

OFIELD1 = 'TIMEID'

ACTION =

TABLES

TOTAL = TOTAL

X_NAMTAB = X_NAMTAB

HRDSYS_ACTIONS = HRDSYS_ACTIONS

EXCEPTIONS

FIELDNAME_ERROR = 0

OTHERS = 0.

ENDFORM.

FORM F_HRDSYS_SAVE_02.

CALL FUNCTION 'HRDSYS_VIEW_SAVE_02'

EXPORTING

OTYPE = 'TIMEID'

CORR_NBR = -CORR_NBR

TABLES

HRDSYS_ACTIONS = HRDSYS_ACTIONS.

ENDFORM. “f_hrdsys_save

FORM F_HRDSYS_TRANSPORT.

CALL FUNCTION 'HRDSYS_VIEW_TRANSPORT'

EXPORTING

OTYPE = 'ZTIME'

OFIELD1 = 'TIMEID'

XMARK =

CORR_ACTION = CORR_ACTION

STATUS_ACTION = STATUS-ACTION

E071K = E071K

TABLES

X_NAMTAB = X_NAMTAB

CORR_KEYTAB = CORR_KEYTAB

EXTRACT = EXTRACT

EXCEPTIONS

FIELDNAME_ERROR = 0

OTHERS = 0.

ENDFORM. “f_hrdsys_transport

Addition of the above subroutines allows creating a transport entry for custom table contents along with its documentation.

Transport request contains following objects:

ALE Distribution of Customizing Data from HR to FI Systems

Design a ALE model distribution system as follows:

Go to Transaction SALE

Navigate to step -> Synchronization of customizing data ->

Maintain Distribution groups.

1 .Create a new distribution group ZTIME_DG with following customizing objects:

Actually LODC and PHDC are logical objects related to Time ID documentation.

To include PHDC in the distribution group list, need to add up one more setting:

Go to transaction SOBJ.

Change the transport attributes of PHDC object to ‘Manual Transport’ and Save.

Come back to distribution group list and save the entries.

All entries will be saved successfully.

Distribute the distribution group to receiving system.

  1. Create a ALE model system with sending system as HR system and receiving system as FI . Add Message type CONDA2 to distribute the customizing data.

To CONDA2 message type, add the distribution group ZTIME_DG. Generate Partner profiles and distribute the ALE model.

  1. Now ALE model is ready for distribution. Whenever master data maintained in standard and custom tables, transport request will be created in the HR system.

From HR system, Run a stand-alone program RBDCUS44 (Tran. Code: BDXE)

This program will collect all the transport entries related to customizing objects modeled in ALE process and transport the same to receiving system transport buffer.

  1. Receiving system is ready to import the transport requests from the buffer via transaction BDXD.

These stand-alone programs can be scheduled in the background mode on timely basis.

At last master data of standard and custom table with time ID documentation is available in the receiving system.

It is time for the receiving FI system to make use of data to build a new application.

Disclaimer & Liability Notice

This document may discuss sample coding, which does not include official interfaces and therefore is not supported. Changes made based on this information are not supported and can be overwritten during an upgrade.

SAP will not be held liable for any damages caused by using or misusing of the code and methods suggested here, and anyone using these methods, is doing it under his/her own responsibility.

SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of the technical article, including any liability resulting from incompatibility between the content of the technical article and the materials and services offered by SAP. You agree that you will not hold SAP responsible or liable with respect to the content of the Technical Article or seek to do so.