ALE

[Former Member]

Hello,

I have a doubt regarding uploading of data into the same system. Can we transfer the data from local system to a client using ALE-Idoc. We can do this by BDC. But, I have doubt whether we can do by using ALE i.e., by giving same host in sender and receiver in distribution model.

Thanks,

Prasad.

[Former Member]

Hi Prasad,

Yes we can give the same host in sender and receiver side in Distribution model using ALE-IDocs.

Refer this link once.........

http://www.saptechnical.com/Tutorials/ALE/MaterialMaster/Distribute1.htm.

Reward if it useful.....

Lakshmi.

[Former Member]

Hi,

1.In same host it is possible to have sender and Receiver.

2.The distribution model can be distributed in same Client and In different Client.

For further Details:

Data Creation in Idoc

IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an

asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.

While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.

IDoc is a intermediate document to exchange data between two SAP Systems.

*IDocs are structured ASCII files (or a virtual equivalent).

*Electronic Interchange Document

*They are the file format used by SAP R/3 to exchange data with foreign systems.

*Data Is transmitted in ASCII format, i.e. human readable form

*IDocs exchange messages

*IDocs are used like classical interface files

IDOC types are templates for specific message types depending on what is the business document, you want to exchange.

WE30 - you can create a IDOC type.

An IDOC with data, will have to be triggered by the application that is trying to send out the data.

FOr testing you can use WE19.

How to create idoc?

*WE30 - you can create a IDOC type

For more information in details on the same along with the examples can be viewed on:

http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404

http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm

http://www.sappoint.com/presentation.html

http://www.allsaplinks.com/idoc_search.html

http://www.sapgenie.com/sapedi/idoc_abap.htm

http://www.erpgenie.com/sapedi/idoc_abap.htm

To Create Idoc we need to follow these steps:

Create Segment ( WE31)

Create Idoc Type ( WE30 )

Create Message Type ( WE81 )

Assign Idoc Type to Message Type ( WE82 )

Creating a Segment

Go to transaction code WE31

Enter the name for your segment type and click on the Create icon

Type the short text

Enter the variable names and data elements

Save it and go back

Go to Edit -> Set Release

Follow steps to create more number of segments

Create IDOC Type

Go to transaction code WE30

Enter the Object Name, select Basic type and click Create icon

Select the create new option and enter a description for your basic IDOC type and press enter

Select the IDOC Name and click Create icon

The system prompts us to enter a segment type and its attributes

Choose the appropriate values and press Enter

The system transfers the name of the segment type to the IDOC editor.

Follow these steps to add more number of segments to Parent or as Parent-child relation

Save it and go back

Go to Edit -> Set release

Create Message Type

Go to transaction code WE81

Change the details from Display mode to Change mode

After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter

Click New Entries to create new Message Type

Fill details

Save it and go back

Assign Message Type to IDoc Type

Go to transaction code WE82

Change the details from Display mode to Change mode

After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter.

Click New Entries to create new Message Type.

Fill details

Save it and go back

Check these out..

Check below link. It will give the step by step procedure for IDOC creation.

http://www.supinfo-projects.com/cn/2005/idocs_en/2/

ALE/ IDOC

http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm

http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc

http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419

http://www.netweaverguru.com/EDI/HTML/IDocBook.htm

http://www.sapgenie.com/sapedi/index.htm

http://www.sappoint.com/abap/ale.pdf

http://www.sappoint.com/abap/ale2.pdf

http://www.sapgenie.com/sapedi/idoc_abap.htm

http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm

http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm

http://www.allsaplinks.com/idoc_sample.html

http://www.sappoint.com/abap.html

http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm

http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc

http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419

http://www.netweaverguru.com/EDI/HTML/IDocBook.htm

http://www.sapgenie.com/sapedi/index.htm

http://www.allsaplinks.com/idoc_sample.html

http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs

go trough these links.

http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm

http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc

http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419

http://www.netweaverguru.com/EDI/HTML/IDocBook.htm

http://www.sapgenie.com/sapedi/index.htm

http://www.sappoint.com/abap/ale.pdf

http://www.sappoint.com/abap/ale2.pdf

http://www.sapgenie.com/sapedi/idoc_abap.htm

http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm

http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm

http://www.allsaplinks.com/idoc_sample.html

http://www.sappoint.com/abap.html

http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm

http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc

http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419

http://www.netweaverguru.com/EDI/HTML/IDocBook.htm

http://www.sapgenie.com/sapedi/index.htm

http://www.allsaplinks.com/idoc_sample.html

http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm

An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...

1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.

2.IDOCs are independent of the sending and receiving systems.

3.IDOCs are independent of the direction of data exchange.

The two available process for IDOCs are

Outbound Process

Inbound Process

AND There are basically two types of IDOCs.

Basic IDOCs

Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.

Extended IDOCs

Extending the functionality by adding more segments to existing Basic IDOCs.

To Create Idoc we need to follow these steps:

Create Segment ( WE31)

Create Idoc Type ( WE30)

Create Message Type ( WE81)

Assign Idoc Type to Message Type ( WE82)

imp links

http://www.allsaplinks.com/idoc_sample.html

http://www.sapgenie.com/sapedi/idoc_abap.htm

www.sappoint.com

--here u can find the ppts and basic seetings for ALE

http://sappoint.com/presentation.html

www.sapgenie.com

http://www.sapgenie.com/ale/index.htm

WE30 - you can create a IDOC type.

An IDOC with data, will have to be triggered by the application that is trying to send out the data.

Try this..Hope this will help.

SAP ALE & IDOC<<<<

Steps to configuration(Basis) >>

1. Create Logical System (LS) for each applicable ALE-enabled client

2. Link client to Logical System on the respective servers

3. Create background user, to be used by ALE(with authorizaton for ALE postings)

4. Create RFC Destinations(SM59)

5. Ports in Idoc processing(WE21)

6. Generate partner profiles for sending system

The functional configuration(Tcode: SALE)

• Create a Customer Distribution Model (CDM);

• Add appropriate message types and filters to the CDM;

• Generate outbound partner profiles;

• Distribute the CDM to the receiving systems; and

• Generate inbound partner profiles on each of the clients.

Steps to customize a new IDoc >>>

1. Define IDoc Segment (WE31)

2. Convert Segments into an IDoc type (WE30)

3. Create a Message Type (WE81)

4. Create valid Combination of Message & IDoc type(WE82)

5. Define Processing Code(WE41 for OUT / WE42 for IN)

6. Define Partner Profile(WE20)

Important Transaction Codes:

SALE - IMG ALE Configuration root

WE20 - Manually maintain partner profiles

BD64 - Maintain customer distribution model

BD71 - Distribute customer distribution model

SM59 - Create RFC Destinations

BDM5 - Consistency check (Transaction scenarios)

BD82 - Generate Partner Profiles

BD61 - Activate Change Pointers - Globally

BD50 - Activate Change Pointer for Msg Type

BD52 - Activate change pointer per change.doc object

BD59 - Allocation object type -> IDOC type

BD56 - Maintain IDOC Segment Filters

BD53 - Reduction of Message Types

BD21 - Select Change Pointer

BD87 - Status Monitor for ALE Messages

BDM5 - Consistency check (Transaction scenarios)

BD62 - Define rules

BD79 - Maintain rules

BD55 - Defining settings for IDoc conversion

WEDI - ALE IDoc Administration

WE21 - Ports in Idoc processing

WE60 - IDoc documentation

SARA - IDoc archiving (Object type IDOC)

WE47 - IDoc status maintenance

WE07 - IDoc statistics

BALE - ALE Distribution Administration

WE05 - IDoc overview

BD87 - Inbound IDoc reprocessing

BD88 - Outbound IDoc reprocessing

BDM2 - IDoc Trace

BDM7 - IDoc Audit Analysis

BD21 - Create IDocs from change pointers

SM58 - Schedule RFC Failures

Basic config for Distributed data:

BD64: Maintain a Distributed Model

BD82: Generate Partner Profile

BD64: Distribute the distribution Model

Programs

RBDMIDOC – Creating IDoc Type from Change Pointers

RSEOUT00 – Process all selected IDocs (EDI)

RBDAPP01 - Inbound Processing of IDocs Ready for Transfer

RSARFCEX - Execute Calls Not Yet Executed

RBDMOIND - Status Conversion with Successful tRFC Execution

RBDMANIN - Start error handling for non-posted IDocs

RBDSTATE - Send Audit Confirmations

FOr testing you can use WE19.

There are two filtering in IDoc.

Segment Filtering:

Segment filtering can be achieved using T/Code BD56. Here you can suppress a whole segment irrespective of data inside it . You have to give Message Type / Sender Prrtner / Receiver Partner.

Data Filtering:

Data filtering can be done in dustribution model (BD64) where you can restrict whole IDOCS or partials IDOCS to be send based on data in fields inside IDOC depending on whether the segment in which you filter is at the highest level or at a lower level. For example in MATMAS if you put a filter of E1MARCM for a particular plant , only data for this plant will go and other plants will be ignored.

Please check this link for more information.

http://help.sap.com//saphelp_470/helpdata/EN/0b/2a611c507d11d18ee90000e8366fc2/frameset.htm

Regards,

Shiva

[Former Member]

Hi Prasad,

The bestway to approach is with BDC. I tried by giving the same message type while creating model view in customer distribution model. The customer distribution model is not accepting the same message type. So, it is not possible to upload data to the same client.

Reward me if useful..

[Former Member]

Hi ,

For ur refernce i am attaching client - client scenario ..

-

-

---

MASTER DATA TRANSFERMATION BETWEEN 2 DIFF CLIENTS

• For this scenario Client 800 is the Sender and 810 is the receiving system

1. Creating Logical Systems

o Login using 800 client

o Go to T. Code SALE

o Expand Sending and Receiving Systems

o Expand Logical Systems

o Click on Define Logical System

o Click on New Entries

o Create STUD_S, STUD_R Logical Systems

o Save and come back

o Assign the STUD_S Logical System to client 800

o Assign the STUD_R Logical System to client 810

2. Creating the RFCs

o Go to T. Code SM59

o Expand R/3 Connections

o Enter RFC Name as STUD_S

o Connection Type as 3

o Language as EN

o Client as 800

o User as SAPUSER

o PWD as abap

o Target host as sap

o Click on Remote logon button to test the RFC

o Enter RFC Name as STUD_R

o Connection Type as 3

o Language as EN

o Client as 800

o User as SATISH

o PWD as abap

o Target host as sap

o Click on Remote logon button to test the RFC

3. Creating the Message Type

o Go to T. Code WE81

o Click on change, continue

o Click on New Entries button

o Give message type as ZBAPI_STUD_MAS and description

o Save and back

4. Creating the Segment

o Go to T. Code WE31

o Give segment name as ZBAPI_STUD_SEG

o Enter Short Text

o Enter the Field Name and Data Element in the text boxes

o Save, continue,

o Click on Edit -> Set Release.

5. Creating the Basic IDOC Object

o Go to T. code WE30

o Give obj. name as ZBAPI_STUD_IDOC

o Click on create

o Select create new radio button, give description and continue

o Select the IDOC obj name and click on create button

o Enter the segment name which is create earlier

o Select the check box if you want to make the segment mandatory

o Enter 1 in minimum number 99999 in maximum number, continue

o Save and back

o Click on Edit -> Set Release

6. Creating Customer Distribution Model

o Go to T. Code BD64

o Click on change and Create model view button

o Enter the short text and Technical name as ZSTUDENT

o Select the model and click on Add Message Type Button

o Give the Sender as STUD_S,

o Receiver as STUD_R,

o Message Type as ZBAPI_STUD_MAS

o Select the model view & click on Environment -> Generate Partner Profiles

o Select Transfer IDOC Immediately and Trigger Immediately radio buttons

o Click on Execute

o You should get a list in green color which means it executed successfully.

o Back to main screen, select the model view

o Click Edit->Model view->Distribute

o Click on continue

o You should get a list saying model view is distributed successfully.

7. Checking the Port

o Go to T. Code WE21

o Expand Transactional RFC

o Find the port from the list which is created using BD64 for STUD_R (Receiving system) RFC Destination.

8. Checking the Partner Profiles.

o Go to T. Code WE20

o Expand Partner Type LS

o Select the Partner profile STUD_R

o Double click on Message Type ZBAPI_STUD_MAS in Outbound parmtrs.

o Check Receiver Port is assigned correctly

o Check the Basic type as your Basic IDOC object.

9. Assigning the Message Type to Basic IDOC Object

o Go to T. Code WE82

o Click on Change & continue, New Entries button

o Give the Message type as ZBAPI_STUD_MAS

o Give Basic Type as ZBAPI_STUD_IDOC

o Release as 46C

o Save and back

10. Creating Inbound Function Module (Posting Program)

o Go to T. Code SE37

o Create a function Module IDOC_INPUT_ZBAPI_STUD_MAS

o Set the Processing type as Remote Enabled Module and mode as start immed, in Attributes Tab.

o Import Parameters

INPUT_METHOD LIKE BDWFAP_PAR-INPUTMETHD

MASS_PROCESSING LIKE BDWFAP_PAR-MASS_PROC

NO_APPLICATION_LOG LIKE SY-DATAR

MASSSAVEINFOS LIKE MASSSAVINF

o Export Parameters

WORKFLOW_RESULT LIKE BDWF_PARAM-RESULT

APPLICATION_VARIABLE LIKE BDWF_PARAM-APPL_VAR

IN_UPDATE_TASK LIKE BDWFAP_PAR-UPDATETASK

CALL_TRANSACTION_DONE LIKE BDWFAP_PAR-CALLTRANS

o Tables

IDOC_CONTRL LIKE EDIDC

IDOC_DATA LIKE EDIDD

IDOC_STATUS LIKE BDIDOCSTAT

RETURN_VARIABLES LIKE BDWFRETVAR

SERIALIZATION_INFO LIKE BDI_SER

o Exceptions

WRONG_FUNCTION_CALLED

o Source Code

DATA: FIRST_TRANC LIKE MARA_UEB-TRANC,

ZBAPI_STUD_SEG like zbapi_stud.

DATA: ZBAPI_STUD LIKE ZBAPI_STUD.

DATA: I_ZBAPI_STUD LIKE ZBAPI_STUD.

DATA: C_TRUE VALUE 'X'.

DATA: C_FALSE VALUE ' '.

DATA: BEGIN OF T_IDOC_ROLLNO OCCURS 0,

DOCNUM LIKE EDIDC-DOCNUM,

ROLLNO LIKE ZBAPI_STUD-ROLLNO,

END OF T_IDOC_ROLLNO.

DEFINE APPEND_RESFIELDS.

PERFORM APPEND_RES_FIELDS TABLES T_MFIELDRES

T_RES_FIELDS

USING &1

COUNTER-D_IND.

END-OF-DEFINITION.

DATA: I_MARA_UEB LIKE MARA_UEB.

DATA: I_ZSTUD_UEB LIKE ZBAPI_STUD.

DATA: I_MAKT_UEB LIKE MAKT_UEB.

DATA: I_MARC_UEB LIKE MARC_UEB.

DATA: I_MARD_UEB LIKE MARD_UEB.

DATA: I_MFHM_UEB LIKE MFHM_UEB.

DATA: I_MARM_UEB LIKE MARM_UEB.

DATA: I_MEAN_UEB LIKE MEA1_UEB.

DATA: I_MBEW_UEB LIKE MBEW_UEB.

DATA: I_STEU_UEB LIKE STEU_UEB.

DATA: I_STEUMM_UEB LIKE STEUMM_UEB.

DATA: I_MLGN_UEB LIKE MLGN_UEB.

DATA: I_MLGT_UEB LIKE MLGT_UEB. " //br010797 neu zu 4.0

DATA: I_MPGD_UEB LIKE MPGD_UEB.

DATA: I_MPOP_UEB LIKE MPOP_UEB.

DATA: I_MVEG_UEB LIKE MVEG_UEB.

DATA: I_MVEU_UEB LIKE MVEU_UEB.

DATA: I_MVKE_UEB LIKE MVKE_UEB.

DATA: I_MPRW_UEB LIKE MPRW_UEB.

DATA: I_LTX1_UEB LIKE LTX1_UEB.

DATA: HELP_MARC_UEB LIKE MARC_UEB.

DATA: T_MARA_UEB LIKE MARA_UEB OCCURS 0.

DATA: T_MAKT_UEB LIKE MAKT_UEB OCCURS 0.

DATA: T_MARC_UEB LIKE MARC_UEB OCCURS 0.

DATA: T_MARD_UEB LIKE MARD_UEB OCCURS 0.

DATA: T_MFHM_UEB LIKE MFHM_UEB OCCURS 0.

DATA: T_MARM_UEB LIKE MARM_UEB OCCURS 0.

DATA: T_MEAN_UEB LIKE MEA1_UEB OCCURS 0.

DATA: T_MBEW_UEB LIKE MBEW_UEB OCCURS 0.

DATA: T_STEU_UEB LIKE STEU_UEB OCCURS 0.

DATA: T_STEUMM_UEB LIKE STEUMM_UEB OCCURS 0.

DATA: T_MLGN_UEB LIKE MLGN_UEB OCCURS 0.

DATA: T_MLGT_UEB LIKE MLGT_UEB OCCURS 0. " //br010797 neu zu 4.0

DATA: T_MPGD_UEB LIKE MPGD_UEB OCCURS 0.

DATA: T_MPOP_UEB LIKE MPOP_UEB OCCURS 0.

DATA: T_MVEG_UEB LIKE MVEG_UEB OCCURS 0.

DATA: T_MVEU_UEB LIKE MVEU_UEB OCCURS 0.

DATA: T_MVKE_UEB LIKE MVKE_UEB OCCURS 0.

DATA: T_MPRW_UEB LIKE MPRW_UEB OCCURS 0.

DATA: T_LTX1_UEB LIKE LTX1_UEB OCCURS 0.

• Internal fields/ tables

• DATA: FLAG_ERROR_HAPPENED.

• DATA: flag_material_exists. "//br210397 zu 4.0 keine Verwendung mehr

DATA: FLAG_EXIT_TO_BE_DONE.

DATA: HELP_TABIX LIKE SY-TABIX.

DATA: HELP_TRANC LIKE MARA_UEB-TRANC.

DATA: HELP_ALAND LIKE STEU_UEB-ALAND.

DATA: HELP_VKORG LIKE MVKE-VKORG.

DATA: HELP_WERKS LIKE T001W-WERKS.

DATA: HELP_LFDNR LIKE STEU_UEB-LFDNR.

DATA: LAST_MARC_TRANC LIKE MARA_UEB-TRANC.

DATA: LAST_MLGN_TRANC LIKE MARA_UEB-TRANC. " //br010797 neu zu 4.0

DATA: LAST_TEXT_TRANC LIKE MARA_UEB-TRANC.

DATA: CURRENT_TABIX LIKE SY-TABIX.

DATA: GENERAL_SUBRC LIKE SY-SUBRC.

DATA: HELP_FACTOR TYPE P DECIMALS 3.

DATA: USER_SEGMENTS LIKE EDIDD OCCURS 0 WITH HEADER LINE. " insert

DATA: CUST_SEGMENT LIKE EDIDD.

DATA: I_MFIELDRES LIKE MFIELDRES.

• DATA: I_MERRDAT LIKE MERRDAT.

DATA: I_EDIDD LIKE EDIDD.

" //br neu zu 3.1g

DATA: T_RES_FIELDS LIKE DELFIELDS OCCURS 0 WITH HEADER LINE.

DATA: T_MFIELDRES LIKE MFIELDRES OCCURS 0.

DATA: T_MERRDAT LIKE MERRDAT OCCURS 0.

DATA: T_EDIDD LIKE EDIDD OCCURS 0.

• DATA: BEGIN OF t_matnr OCCURS 0, "//br210397 zu 4.0

• matnr LIKE mara-matnr, " wird nicht mehr verwendet

• END OF t_matnr. "

DATA: BEGIN OF COUNTER,

TRANC LIKE MARA_UEB-TRANC,

D_IND LIKE MARA_UEB-D_IND,

END OF COUNTER.

• DATA: BEGIN OF t_idoc_tranc OCCURS 0, " 4.0

• docnum LIKE edidc-docnum, "

• tranc LIKE mara_ueb-tranc, "

• END OF t_idoc_tranc. "

DATA T_IDOC_TRANC LIKE MATIDOCTRANC OCCURS 0 WITH HEADER LINE."

DATA: FLAG_FITS.

DATA: APPLICATION_SUBRC LIKE SY-SUBRC.

DATA FLAG_MUSS_PRUEFEN LIKE SY-DATAR.

DATA MAX_ERRORS LIKE T130S-ANZUM. " 4.0

• note 419281

DATA : FLG_MASS.

CLEAR : FLG_MASS.

FIELD-SYMBOLS: . " 4.0

• ALE-distribution unity : IDOC status set by locking "note0361838

data: "note0361838

it_dsp_idocstat like bdidocstat "note0361838

occurs 0 with header line. "note0361838

• Initialize data - general

REFRESH T_MFIELDRES.

REFRESH T_IDOC_TRANC.

REFRESH T_IDOC_TRANC. "JH/02.02.98/4.0C KPr100004993

• REFRESH t_idoc_tranc_segment. " //br 40 : unnötig

• REFRESH matnr_tranc. " -"-

• REFRESH t_matnr.

COUNTER-TRANC = 1.

COUNTER-D_IND = 1.

REFRESH T_MARA_UEB.

REFRESH T_MAKT_UEB.

REFRESH T_MARC_UEB.

REFRESH T_MARD_UEB.

REFRESH T_MFHM_UEB.

REFRESH T_MARM_UEB.

REFRESH T_MEAN_UEB.

REFRESH T_MBEW_UEB.

REFRESH T_STEU_UEB.

REFRESH T_STEUMM_UEB.

REFRESH T_MLGN_UEB.

REFRESH T_MLGT_UEB. " //br010797 neu zu 4.0

REFRESH T_MPGD_UEB.

REFRESH T_MPOP_UEB.

REFRESH T_MVEG_UEB.

REFRESH T_MVEU_UEB.

REFRESH T_MVKE_UEB.

REFRESH T_MPRW_UEB.

• REFRESH VKORG_ALAND.

• REFRESH WERKS_ALAND.

CLEAR APPLICATION_SUBRC.

REFRESH T_MERRDAT.

• Check if right function is called

READ TABLE IDOC_CONTRL INDEX 1.

IF SY-SUBRC <> 0.

EXIT.

ELSE.

IF IDOC_CONTRL-IDOCTP <> 'ZBAPI_STUD_IDOC'.

RAISE WRONG_FUNCTION_CALLED.

ENDIF.

ENDIF.

LOOP AT IDOC_CONTRL.

• Initialize data - per IDOC

• t_idoc_tranc-docnum = counter-tranc.

T_IDOC_TRANC-DOCNUM = IDOC_CONTRL-DOCNUM.

T_IDOC_TRANC-FIRST_TRANC_IDOC = COUNTER-TRANC + 2.

APPEND T_IDOC_TRANC.

• Select segments which belong to IDOC

REFRESH T_EDIDD.

LOOP AT IDOC_DATA WHERE DOCNUM = IDOC_CONTRL-DOCNUM.

APPEND IDOC_DATA TO T_EDIDD.

ENDLOOP.

• BUSINESS TRANSACTION EVENT (header / data) "note0388000

call function 'OPEN_FI_PERFORM_MGV00200_E' "note0388000

exporting "note0388000

idoc_header = idoc_contrl "note0388000

FLG_APPEND_STATUS = 'X' "note0388000

tables "note0388000

• (DEL) idoc_data = idoc_data "note0388000 note0418561

idoc_data = t_edidd "note0418561

idoc_status = idoc_status "note0388000

exceptions "note0388000

others = 1. "note0388000

if sy-subrc = 1. "note0388000

continue. "note0388000

endif. "note0388000

• Within one IDOC: loop through data segments:

• Prepare internal tables for the current material

LOOP AT T_EDIDD INTO IDOC_DATA.

• Transform from CoreData to Normal Data if necesary

CASE IDOC_DATA-SEGNAM.

• WHEN 'E1MARAC'.

*--COMMENTED BY SATISH

• PERFORM MOVE_E1MARAC_TO_E1MARAM USING IDOC_DATA.

• WHEN 'E1MAKTC'.

• PERFORM MOVE_E1MAKTC_TO_E1MAKTM USING IDOC_DATA.

*--COMMENTES ENDED BY SATISH

WHEN 'ZBAPI_STUD_SEG'.

• PERFORM MOVE_E1MARAC_TO_E1MARAM USING IDOC_DATA.

CLEAR I_ZBAPI_STUD.

• Second: Move E1MARAC into E1MARAM

I_ZBAPI_STUD = IDOC_DATA-SDATA.

• Third: Move E1MARAM back into IDOC-line

IDOC_DATA-SDATA = I_ZBAPI_STUD.

IDOC_DATA-SEGNAM = 'ZBAPI_STUD_SEG'.

ENDCASE.

CURRENT_TABIX = SY-TABIX.

COUNTER-D_IND = COUNTER-D_IND + 1.

COUNTER-TRANC = COUNTER-TRANC + 2.

CASE IDOC_DATA-SEGNAM.

WHEN 'ZBAPI_STUD_SEG'.

• Initialize data - per material

COUNTER-D_IND = 1.

FIRST_TRANC = COUNTER-TRANC.

• interpret segment

ZBAPI_STUD_SEG = IDOC_DATA-SDATA.

MOVE-CORRESPONDING ZBAPI_STUD TO I_ZSTUD_UEB.

T_IDOC_ROLLNO-DOCNUM = IDOC_CONTRL-DOCNUM.

T_IDOC_ROLLNO-ROLLNO = I_ZSTUD_UEB-ROLLNO.

APPEND T_IDOC_ROLLNO.

ENDCASE.

if not ZBAPI_STUD_SEG is initial.

• ZBAPI_STUD-MANDT = ZBAPI_STUD_SEG-MANDT.

• ZBAPI_STUD-ROLLNO = ZBAPI_STUD_SEG-ROLLNO.

• ZBAPI_STUD-FNAME = ZBAPI_STUD_SEG-FNAME.

• ZBAPI_STUD-LNAME = ZBAPI_STUD_SEG-LNAME.

INSERT ZBAPI_STUD FROM ZBAPI_STUD_SEG.

COMMIT WORK.

ENDIF.

*-- ALE ditribution unity : update IDOC status "note03618

LOOP AT it_dsp_idocstat. "note036

LOOP AT IDOC_STATUS WHERE DOCNUM = it_dsp_idocstat. "note036

DELETE idoc_status INDEX sy-tabix. "note036

ENDLOOP. "note036

APPEND it_dsp_idocstat TO idoc_status. "note036

ENDLOOP. "note036

*--GENERATING THE IDOC STATUS

PERFORM HANDLE_ERROR_EXT " //br40

TABLES "

IDOC_CONTRL "

IDOC_STATUS "

RETURN_VARIABLES "

T_MERRDAT "

T_IDOC_TRANC "

T_IDOC_ROLLNO "JH/4.0C/KPr100004993

USING "

GENERAL_SUBRC "

NO_APPLICATION_LOG "

MASSSAVEINFOS "wk/40c

CHANGING "

WORKFLOW_RESULT. "

PERFORM HANDLE_ERROR

TABLES

IDOC_CONTRL

IDOC_STATUS

RETURN_VARIABLES

T_MERRDAT

T_IDOC_ROLLNO "JH/4.0C/KPr100004993

USING

APPLICATION_SUBRC

CHANGING

WORKFLOW_RESULT.

SORT T_IDOC_ROLLNO BY ROLLNO. "note 315124

• React on general error

DATA: I_MERRDAT LIKE MERRDAT.

IF GENERAL_SUBRC <> 0.

I_MERRDAT-MSGTY = 'E'.

I_MERRDAT-MSGID = SY-MSGID.

I_MERRDAT-MSGNO = SY-MSGNO.

I_MERRDAT-MSGV1 = SY-MSGV1.

I_MERRDAT-MSGV2 = SY-MSGV2.

I_MERRDAT-MSGV3 = SY-MSGV3.

I_MERRDAT-MSGV4 = SY-MSGV4.

APPEND I_MERRDAT TO T_MERRDAT.

ENDIF.

LOOP AT T_MERRDAT INTO I_MERRDAT

WHERE MSGTY = 'S' "success

OR MSGTY = 'D' "dummy

OR MSGTY = 'I' "Information " //br011097 zu 3.1I

OR MSGTY = 'H' "dummy " 4.0

OR MSGTY = 'W'. "warning

DELETE T_MERRDAT.

ENDLOOP.

ENDLOOP.

ENDLOOP.

ENDFUNCTION.

*&----

---

*

*& Form handle_error_ext

*&----

---

*

FORM HANDLE_ERROR_EXT

TABLES

IDOC_CONTRL STRUCTURE EDIDC

IDOC_STATUS STRUCTURE BDIDOCSTAT

RETURN_VARIABLES STRUCTURE BDWFRETVAR

T_MERRDAT STRUCTURE MERRDAT

IDOC_TRANC STRUCTURE MATIDOCTRANC

• JH/02.02.98/4.0C KPr100004993 (Anfang)

T_IDOC_ROLLNO STRUCTURE T_IDOC_ROLLNO

• JH/02.02.98/4.0C KPr100004993 (Ende)

USING

GENERAL_SUBRC LIKE SY-SUBRC

NO_APPLICATION_LOG LIKE SY-DATAR

MASSSAVEINFOS LIKE MASSSAVINF

CHANGING

WORKFLOW_RESULT LIKE BDWF_PARAM-RESULT.

DATA FLAG_ERROR_HAPPENED.

DATA I_MERRDAT LIKE MERRDAT.

DATA IDOC_INDEX_2_SUBRC LIKE SY-SUBRC.

DATA AL_HANDLES TYPE BAL_T_LOGH. "//br99

SORT T_IDOC_ROLLNO BY ROLLNO. "note 315124

• React on general error

IF GENERAL_SUBRC <> 0.

REFRESH T_MERRDAT.

• i_merrdat-tranc = 0. " //br261197

READ TABLE IDOC_TRANC INDEX 1. " zu 40b

I_MERRDAT-TRANC = IDOC_TRANC-FIRST_TRANC_IDOC. "

I_MERRDAT-MSGTY = 'E'.

I_MERRDAT-MSGID = SY-MSGID.

I_MERRDAT-MSGNO = SY-MSGNO.

I_MERRDAT-MSGV1 = SY-MSGV1. I_MERRDAT-MSGV2 = SY-MSGV2.

I_MERRDAT-MSGV3 = SY-MSGV3. I_MERRDAT-MSGV4 = SY-MSGV4.

APPEND I_MERRDAT TO T_MERRDAT.

ENDIF.

DATA: C_TRUE,

C_FALSE VALUE 'X'.

• If error happened ==> Rollback whole work....

LOOP AT T_MERRDAT INTO I_MERRDAT WHERE MSGTY NA 'SDHWI'.

EXIT.

ENDLOOP.

IF SY-SUBRC = 0.

FLAG_ERROR_HAPPENED = C_TRUE.

ROLLBACK WORK.

ELSE.

FLAG_ERROR_HAPPENED = C_FALSE.

ENDIF.

• ----------------------------------------------------------------------

• Set IDOC status

• two cases:

• single IDOC-processing: ==> error can be written in IDOC status

• package processing ==> anononymous "package error" for all IDOCs

• ----------------------------------------------------------------------

READ TABLE IDOC_CONTRL INDEX 2.

IDOC_INDEX_2_SUBRC = SY-SUBRC.

IF SY-SUBRC = 0.

IF 1 = 2. "//br40

MESSAGE E051(B1). "

ENDIF. "

CLEAR I_MERRDAT.

I_MERRDAT-MSGID = 'B1'.

I_MERRDAT-MSGTY = 'E'.

I_MERRDAT-MSGNO = '051'.

ENDIF.

IF IDOC_INDEX_2_SUBRC NE 0 OR FLAG_ERROR_HAPPENED = C_FALSE.

• Nur in diesen Fällen wird Application Log geschrieben

• Delete all Successes and Dummy records from t_merrdat

• DELETE t_merrdat WHERE msgty = 'S' "success " testweise

• OR msgty = 'D'. "dummy "

LOOP AT T_MERRDAT INTO I_MERRDAT WHERE MSGTY = 'D'. "

I_MERRDAT-MSGTY = 'S'. "

MODIFY T_MERRDAT FROM I_MERRDAT. "

ENDLOOP. "

ENDIF.

WORKFLOW_RESULT = 0.

LOOP AT IDOC_CONTRL.

• Set IDOC status

CLEAR IDOC_STATUS.

IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.

IF FLAG_ERROR_HAPPENED = C_FALSE.

• Application log

PERFORM WRITE_APPL_LOG TABLES IDOC_TRANC

T_MERRDAT

IDOC_STATUS

USING IDOC_CONTRL

FLAG_ERROR_HAPPENED

NO_APPLICATION_LOG

MASSSAVEINFOS

AL_HANDLES.

• idoc_status-status = '53'. "OK!

• APPEND idoc_status.

• JH/02.02.98/4.0C KPr100004993 (Anfang)

• Fill Return variables

CLEAR RETURN_VARIABLES.

RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.

RETURN_VARIABLES-WF_PARAM = 'Processed_IDOCs'.

APPEND RETURN_VARIABLES.

• Verknüpfungseintrag anlegen

READ TABLE T_IDOC_ROLLNO WITH KEY ROLLNO = IDOC_CONTRL-DOCNUM

BINARY SEARCH.

IF SY-SUBRC = 0.

RETURN_VARIABLES-DOC_NUMBER = T_IDOC_ROLLNO-ROLLNO.

RETURN_VARIABLES-WF_PARAM = 'Appl_Objects'.

APPEND RETURN_VARIABLES.

ENDIF.

• JH/02.02.98/4.0C KPr100004993 (Ende)

ELSE.

IF IDOC_INDEX_2_SUBRC NE 0.

• Application Log

PERFORM WRITE_APPL_LOG TABLES IDOC_TRANC

T_MERRDAT

IDOC_STATUS

USING IDOC_CONTRL

FLAG_ERROR_HAPPENED

NO_APPLICATION_LOG

MASSSAVEINFOS

AL_HANDLES.

ELSE.

IDOC_STATUS-MSGID = I_MERRDAT-MSGID.

IDOC_STATUS-MSGTY = I_MERRDAT-MSGTY.

IDOC_STATUS-MSGNO = I_MERRDAT-MSGNO.

IDOC_STATUS-MSGV1 = I_MERRDAT-MSGV1.

IDOC_STATUS-MSGV2 = I_MERRDAT-MSGV2.

IDOC_STATUS-MSGV3 = I_MERRDAT-MSGV3.

IDOC_STATUS-MSGV4 = I_MERRDAT-MSGV4.

IDOC_STATUS-STATUS = '51'. "ERROR!

APPEND IDOC_STATUS.

ENDIF.

• Fill Return variables

CLEAR RETURN_VARIABLES.

RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.

• return_variables-wf_param = c_wf_par_processed_idocs.

RETURN_VARIABLES-WF_PARAM = 'Error_IDOCs'.

APPEND RETURN_VARIABLES.

WORKFLOW_RESULT = 99999.

ENDIF.

• APPEND idoc_status.

ENDLOOP.

IF NO_APPLICATION_LOG IS INITIAL.

CALL FUNCTION 'BAL_DB_SAVE' "//br99

EXPORTING

I_IN_UPDATE_TASK = ' '

I_SAVE_ALL = ' '

I_T_LOG_HANDLE = AL_HANDLES.

• EXCEPTIONS

• LOG_NOT_FOUND = 1

• SAVE_NOT_ALLOWED = 2

• NUMBERING_ERROR = 3

• OTHERS = 4.

CALL FUNCTION 'BAL_GLB_MEMORY_REFRESH' "//br99

EXPORTING

• I_AUTHORIZATION =

I_REFRESH_ALL = ' '

I_T_LOGS_TO_BE_REFRESHED = AL_HANDLES.

• EXCEPTIONS

• NOT_AUTHORIZED = 1

• OTHERS = 2

ENDIF.

ENDFORM. " handle_error

Save, check and activate

11. Assigning the Inbound Function Module to Basic Type & Message Type

o Go to T. Code WE57

o Click on change, continue, continue and New Entries Button

o Enter the Module as IDOC_INPUT_ZBAPI_STUD_MAS

o Type as “F”

o Basic Type as ZBAPI_STUD_IDOC

o Message Type as ZBAPI_STUD_MAS.

o Direction as 2

o Save and back

Now Login in 810 client

12. Assigning the Inbound Function Module in ALE Table

o Go to T. Code BD51

o Click on continue, New Entries button

o Give the Inbound Function Module IDOC_INPUT_ZBAPI_STUD_MAS

o Give Input t. as 0 (zero)

o Save and back

13. Creating Process Code

o Go to T. Code WE42

o Click on Change, New Entries Button

o Give Process Code name as ZSTUD, give Description & Save

o Select Processing with ALE Services Radio button

o Select Processing by Function Module Radio button

o Click the ALE Table (arrow Icon) in Identification

o Give the Function Module Name ZIDOC_INPUT_ZBAPI_STUD_MAS

o Give maximum number of repeats 0

o Save and back, back

o Select the process code from the list & click on Logical Messages Icon

o Give the Message Type as ZBAPI_STUD_MAS

o Save & Back, Save & Back, Save & Back

14. Changing the Customer Distribution model in Receiving system

o Go to T. Code BD64

o Click on change and Create model view button

o Select the model view & click on Environment -> Generate Partner Profiles

o Select Transfer IDOC Immediately and Trigger Immediately radio buttons

o Click on Execute

o You should get a list in green color which means it executed successfully.

15. Assigning the Process Code to Message Type in Receiving System

o Go to T. Code WE20

o Expand Partner Type LS

o Select the Partner Profile STUD_S

o Double click on Message Type ZBAPI_STUD_MAS in Inbound parmtrs.

o Give the Process Code as ZSTUD

o Click on Trigger Immediately Radio button

o Save & Back

o Save & Back

16. Creating the Selection Program (Outbound Program)

• Login in client 800.

• Go to T. Code SE38

• Create a Report Program as ZSTUD_SEND with the following code

REPORT ZSTUD_SEND

NO STANDARD PAGE HEADING.

TABLES: ZBAPI_STUD.

DATA: IT_STUD LIKE ZBAPI_STUD OCCURS 0 WITH HEADER LINE.

SELECTION-SCREEN:BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-H01.

SELECT-OPTIONS: S_ROLLNO FOR ZBAPI_STUD-ROLLNO.

SELECTION-SCREEN SKIP.

SELECTION-SCREEN:BEGIN OF BLOCK B2 WITH FRAME TITLE TEXT-H02.

PARAMETERS: P_MESTYP LIKE EDIDC-MESTYP,

P_RCVPRN LIKE TBDLST-LOGSYS.

SELECTION-SCREEN:END OF BLOCK B2.

SELECTION-SCREEN:END OF BLOCK B1.

START-OF-SELECTION.

PERFORM CREATE_STUDENT.

PERFORM CREATE_IDOC.

*&----

---

*

*& Form CREATE_STUDENT

*&----

---

*

• sending student

*----

---

*

FORM CREATE_STUDENT.

SELECT * FROM ZBAPI_STUD

INTO TABLE IT_STUD

WHERE ROLLNO IN S_ROLLNO.

ENDFORM. " CREATE_STUDENT

*&----

---

*

*& Form CREATE_IDOC

*&----

---

*

• IDOC Creation

*----

---

*

FORM CREATE_IDOC.

DATA : IMAS_DATA LIKE EDIDD OCCURS 10 WITH HEADER LINE,

IMAS_CON LIKE EDIDC OCCURS 10 WITH HEADER LINE,

ICOM_CON LIKE EDIDC OCCURS 10 WITH HEADER LINE.

IMAS_CON-RCVPRT = 'LS'.

IMAS_CON-RCVPRN = P_RCVPRN.

IMAS_CON-IDOCTP = 'ZBAPI_STUD_IDOC'.

IMAS_CON-MESTYP = P_MESTYP.

IMAS_CON-DIRECT = 1.

APPEND IMAS_CON.

LOOP AT IT_STUD.

IMAS_DATA-SEGNAM = 'ZBAPI_STUD_SEG'.

IMAS_DATA-SDATA = IT_STUD.

APPEND IMAS_DATA.

ENDLOOP.

CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'

EXPORTING

MASTER_IDOC_CONTROL = IMAS_CON

• OBJ_TYPE = ''

• CHNUM = ''

TABLES

COMMUNICATION_IDOC_CONTROL = ICOM_CON

MASTER_IDOC_DATA = IMAS_DATA

• EXCEPTIONS

• ERROR_IN_IDOC_CONTROL = 1

• ERROR_WRITING_IDOC_STATUS = 2

• ERROR_IN_IDOC_DATA = 3

• SENDING_LOGICAL_SYSTEM_UNKNOWN = 4

• OTHERS = 5

.

IF SY-SUBRC <> 0.

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

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

ENDIF.

COMMIT WORK.

LOOP AT ICOM_CON.

WRITE 😕 'IDOC: ', ICOM_CON-DOCNUM, 'CREATED SUCCESSFULLY'.

ENDLOOP.

ENDFORM. " CREATE_IDOC

17. Transferring the student records from 800 to 810 client

• Execute Report Program ZSTUD_SEND

• Give the Range of Roll Nos to Transfer

• Give Message Type as ZBAPI_STUD_MAS

• Give Receiver Logical system as STUD_R

• Execute

• You should get the IDOC Number

• Take the IDOC Number and go to T. Code WE05 & Execute

• In Outbox you can see the IDOC Status

• Select the status record in left side window

• Double click on the Status record in right side window

• You can see the Control Record, Data Record and Status Records for that IDOC

• If the ICON is green and the status code is 3, it means the IDOC is passed to PORT Successfully.

Now Login in 810 client

• Go to T. Code WE05 & Execute

• You can see the status record in left side window

• If the status no is 53 and color is green, it means the IDOC is Posted to Application successfully.

• You can see the Log Information by double clicking on the status record in right side window.

• Now in left side window, you can see the Control Record, Data Record & Status Record of the IDOC

• Now go to T. Code SE16

• Give the table name ZBAPI_STUD & press F7

• See the contents of the table

• The table is updated with the students records transferred from 800 client with our selection program.

-

-

---

Reward if usefu

Thanks

Jagadeesh.G