SAP R/3 форум ABAP консультантов
Russian ABAP Developer's Club

Home - FAQ - Search - Memberlist - Usergroups - Profile - Log in to check your private messages - Register - Log in - English
Blogs - Weblogs News

FAQ



 
Post new topic   Reply to topic    Russian ABAP Developer's Club Forum Index -> Interfaces | Интерфейсы
View previous topic :: View next topic  
Author Message
admin
Администратор
Администратор



Joined: 01 Sep 2007
Posts: 1636

PostPosted: Wed Sep 05, 2007 6:33 pm    Post subject: FAQ Reply with quote

BAPI
BAPI Step-by-Step
List of BAPIs

ALE/ IDOC
ALE & IDOC Quick Reference Guide

Changing SAP IDOCs Status In Mass / Mass Deletion Of IDOCs


IDOC - XML convert
FM IDOC_XML_TRANSFORM
FM IDOC_XML_FROM_FILE

Main Transaction Codes

Main Menus
WEDI EDI Related Activities
BALE ALE Related Activities
SWLD Workflow Related Activities
SALE ALE Configuration
NACE Message Control Configuration

IDOC Definition
SE11 Data Dictionary
WE30 IDoc type editor
WE31 Segment editor
BD53 Reduction of IDoc types
WE60 Documentation for IDoc types
WE61 Documentation for IDoc record types

IDOC Monitoring
WE02 IDoc display
WE05 IDoc Lists
WE06 Active IDoc monitoring
WE07 IDoc statistics

Configuration(ALE and EDI)
BD54 Maintain logical systems
BD64 Maintain distribution model
BD71 Distribute Customer Model
BD82 Generate partner profiles
FILE Logical File Paths
PFTC Task Definition
PPOC Maintain Organization Structure
SM59 Maintain RFC Destinations
SWE2 Event Linkage
SWU3 Basic Workflow Settings
WE20 Partner profiles
WE21 Port definition

Run Time Workflow
SO01 SAP Inbox
SWEL Event Log
SWI1 Workflow Log
SWI2 Work Item Analysis
SWI5 Workload Analysis

Message Control
Message Control (Output Control) for ALE
NACE Condition Record Maintenance
VOK2 SD Message Control Components
VOK3 Purchasing message Control Components
VOFM View Message Requirements
V/86 Condition Table Field Catalog
WE15 IDoc test: Outbound from MC

Testing
WE19 Test tool
WE12 IDoc test: Inb. Procg of Outb. File
WE16 IDoc test: Inbound File
WE17 IDoc test: Inbound status report

Reprocessing IDOCS
BD87 Process inbound IDocs
BD88 Process outbound IDocs

System Monitoring
SM12 Locked Entries
SM13 Update Monitoring
SM21 System Log Display
SM58 Transactional RFC Log
SM66 Debug Async Update Tasks
ST22 Dump Analysis

Change IDOC status
RC1_IDOC_SET_STATUS - EHS: Report to Convert the IDoc Status

Creating and Evaluating Change Pointers

Other Relevant Transaction Codes
AL05 Monitor current workload
AL11 Display SAP Directories
AL18 Local File System Monitor
AL19 Remote File System Monitor
AL21 ABAP Program analysis
ALO1 Data Relationship Browser
ANA_VAR Table Analysis: Analysis Variants
BA10 Subsystem Config.
BA11 Channel Definition for Transceiver
BD10 Send Material
BD100 IDoc display object channel view
BD101 Consistency check
BD102 Outbound registry
BD103 Inbound registry
BD104 maintain tbd53
BD105 maintain tbd54
BD11 Fetch Material
BD12 Send customer
BD13 Open customer
BD14 Send vendor
BD15 Open vendor
BD16 Send Cost Center
BD17 Get Cost Center
BD18 Send General Ledger Account
BD19 Get General Ledger Account
BD20 IDoc passed to application
BD21 Select change pointer
BD22 Delete change pointers
BD23 Delete serialization data
BD24 Send Cost Elements
BD25 Send Activity Type
BD26 Get Activity Type
BD27 Send cost center activity prices
BD28 Send obj/cost element control data
BD30 Distribute material object list
BD31 Distribute document object list
BD32 Distribute plant allocations(matBOM)
BD40 Read change pointer for group
BD41 Dispatch IDocs for group
BD42 Check IDocs for group
BD43 Post IDocs for group
BD44 Assign message types to ser. group
BD47 Dependencies between methods
BD48 Dependency method – message
BD50 Activ. change pointer for mess.type
BD51 Maintain function modules (inbound)
BD52 Maintain change-relevant fields for message type
BD53 Reduction of IDoc types
BD55 Maintain IDoc conversion
BD56 Maintain IDoc segment filtering
BD57 Maintain link and serialization ty.
BD58 Convert Org. units
BD59 Allocation object type -> IDoc type
BD60 Additional data for message type
BD61 Activate change pointer
BD62 Define segment conversion rule
BD63 Transport ALE tables to message type
BD65 Maintain IDoc type required fields
BD66 IDoc type field -> change doc.field
BD67 Maintain input methods
BD68 Maintain lists
BD69 Assign message type to IDoc
BD70 Adjust number ranges
BD72 Activate events
BD73 Reposting of IDocs (ALE)
BD75 Convert IDoc status
BD76 Model upload/download monitoring
BD77 Distribution of control data
BD78 Monitoring control data distribution
BD79 Maintain IDoc conversion rules
BD80 Conversion pre-production/production
BD81 Filter objects parameter filtering
BD83 Send IDocs after an ALE error
BD84 Post IDocs after ALE error
BD85 Consistency check for transfer
BD86 Consistency check for sales
BD89 Control data model. – initial screen
BD90 Start DA-OU
BD91 Send characteristic
BD92 Send class
BD93 Send classification
BD94 OA – file transfer
BD95 Specify ALE object types
BD96 filter objects of receiver determin.
BD97 Assign RFC dest. to logical systems
BD98 ALE consistency check active
BD99 Message type dependencies
BDA1 Call RSARFCEX
BDA4 Specify ALE object types
BDA5 Distribute documents
BDBG Generate ALE interface (BAPI)
BDBP Hierarchy maintenance of BAPI param.
BDBS Generate coding for mapping
BDCP Number range maintenance: ALE_CP
BDLS Mapping Logical System Names
BDM2 Monitoring: IDocs with receiver
BDM5 Consistency check
BDM6 Monitor: Check input workflow
BDM7 ALE Audit: statistical analyses
BDM8 ALE Audit: Sending the confirmations
BDM9 Reorganizing the audit database
BDMC Upload info structures
BDR1 Display application log for recovery
BDR2 Reorganization of recovery data
BDRC ALE: Determine recovery objects
BDRL ALE: Process recovery objects
OE2C Process Code Inbound
OYE0 EDI: Maintain Port Def. arfc
OYE3 Display EDI Ports
OYE4 Display ALE Ports
OYED Maintain Port Definitions
OE3C System Process Code
OE1C Process Code (OutB)
OYEL Display EDP21 (InB Partner Profile)
OYEX Create EDP21 (InB Partner Profile Overview)
OYEH Display EDP12 (Msg Control)
OYER Create EDP12 (Msg Control Overview)
OYEI Display EDP13 (OutB Partner Profile)
OYEU Create EDP13 (OutB Partner Profile overview)
OYSM Number Range Port Definition
OYSN Number Range For IDOCS
OYSO Number Range IDOC Types
WE08 EDI: File Processing Status (EDFI2)
WE09 IDoc lists enhanced
WE10 IDoc lists enhanced
WE14 IDoc test: Outb. from IDoc
WE30 IDoc type editor
WE32 View editor
WE33 Value tables for IDoc documentation
WE40 System process codes
WE41 Process codes, outbound
WE42 Process codes, inbound
WE43 Funct.module: Status record display
WE44 Partner Types and selection reports
WE45 Forward (inbound) (V3, EDILOGADR)
WE46 IDoc administration
WE47 Status Maintenance
WE48 Inbound process codes: Texts
WE49 Inbound process codes: Change texts
WE50 System process codes: Texts
WE51 System process codes: Change texts
WE52 Outbound process codes: Texts
WE53 Outbound process codes: Change texts
WE54 FMs for changing file names
WE55 FMs for path names
WE56 Status process codes
WE57 Messages and application objects
WE58 Status process codes: Texts
WE59 Change status process codes
WE62 Documentation for segments
WE63 Parser for IDoc types and rec.types
WE70 Conversion: Basic types
WE71 Conversion: Extensions
WE72 Conversion: IDoc types
WE73 Conversion: Logical messages
WE80 IDoc types: Overview
WE81 Logical message types
WE82 Assignment IDoc type – Message
WE83 Extensions: Overview (EDCIM)
WE84 Assignment of IDoc and appl. fields
WECP Display CPIC interface status (R/2)
WEL0 Forward (inbound) (EDILOGADR)
WEL1 EDI: Interface Invoice for EDILOGADR
WENA Messages on basis of changes

WorkFlow Configuration
OOAW & SWLV Subordinate And Peer Definition
PFAC Standard Roles
PO13 Maintain Substitutes
SWO1 Business Object Builder

Study material on ABAP and Cross Applications

Q. What is the difference Between IDOC type and Message type? How to link the IDOC type with Message type?
A. Message type gives the meaning of the IDOC and IDOC type gives the structure of an IDOC.
The linkage will happen in WE82.
In the OO(Object Oriented) approach, Message Type can be refferred to a Class and IDOC Type as an instance of the class Message Type

Q. Where the IDOC information gets stored?
A.
EDIDC Stores the Control information an IDOC
EDID4 Stores the Data Records from 4.0 onwards
EDIDS Stores the Status of an IDOC

Q. What is process code? What are type of process codes

A. Process code refers to an workflow or a function module which helps in reading or writing data from/to Idoc. Following are types of process code:
- Outbound Process Code This will read application data and place data in Idoc
- Inbound Process Code This will Idoc and create corresponding application data
- System Process Code This will create work item in case some error occurs in idoc / application document processing
- Status Proces Code This will handle error that occurs when a idoc is sent to some other system

Q. How to reprocess an IDOC?
A. You can use the below Programs for IDocs Reprocessing:
  • RBDMANI2 : Reprocess Idocs manually
  • RBDMANIN : Posting of IDocs with Status 51
  • RBDMOIND : Outbound Idocs status 03->12
  • RSEOUT00 : For Processing 30 Status IDocs
  • RBDAPP01 : For Processing 64 Status IDocs
  • RBDAGAIN : Reprocess Incorrect Outbound IDocs
  • RBDAGAI2 : Reprocessing of IDocs after ALE Input Error

Q. How to trace the IDocs of the Receiving system from the Sending system?

A. Steps:
  • Execute the transaction BD87
  • Give the Outbound IDocs in the IDoc Number field and execute or Just
  • Note the Start time and End time when u execute the Master Data
  • Transaction say for eg.BD10 and specify the same in the Time Created input field of BD87,also give the Message Type and the Receiving System Names and execute.
  • Select the Repective Message Type and Press the Trace IDoc Button.

Q. How to trace IDocs based on the data .

A. Steps:
  • Execute Transaction WE09
  • Put in the message type name in the field labeled 'Logical Message' Ex - DEBMAS
  • Now we will move to the section 'Criteria for Search in Data Records '
  • In this section we will put the Segment name in which we want to search the existance of data in the field labeled 'Search in Segment' EX - E1KNA1M
  • In the field labeled 'Search in Field' we will put the field name of the segment in which we want to search the existance of data. Ex - KUNNR for searching IDOCs for certain customer number.
  • Now in the field labeled 'For Value' we will put the search value. Ex - Customer number as 100 .
  • We will now execute the transaction.
  • The result can be a single Idoc or a list of multiple IDOCS depending upon the Search Criteria entered.


SAP Utility Programs from ERPGenie.com
Gentran IDoc Data Definition File Generation Tool - Gentran’s mapping tool maps 1 structure to another structure. Typically, 1 structure is an EDI standard which is provided by Sterling Commerce. In this case we assume the other structure to be SAP’s Idoc structure.
1 click abap tool - This is a tool for quickly selecting last objects used for editing purposes. Very useful for developers to quickly access their common objects.
EDI Utilities - Contains Workflow Utilities Differences in SWETYPV entries across environments & Send email to managers of agents who are no longer there. Contains EDI Utilities Send Email when IDoc hasn’t changed status for a period. Update IDOC Status, Analyze EDPAR.
Find PO in IDOC - Find Inbound Idocs for a particular PO number.
IDOC Excel Upload - Changing an Idoc’s status with an Excel upload.

SAP Help: ALE Introduction and Administration

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://www.supinfo-projects.com/en/2005/idocs_en/1/

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

ALE Scenario Development Guide
ALE Scenario Development Guide

ALE Scenario: Material Master Distribution

Note 321493 - Editing IDoc
Symptom
The Display -> Change function in the IDoc display menu is missing.
WE02, WE05, WE07
Solution
The Display -> Change function will still be available from within the control record and data record detailed view.You can call the detailed view by double-clicking on the icon in front of each record in the navigation tree on the left side of the screen.
In addition, you still cannot start Idoc processing from within the monitor transactions after it has been edited.You can start the further processing from within the ALE transactions or you can carry out editing and the further processing under the control of the SAP Business Workflow.

В We02 проваливаемся в конкретный айдок, просматриваем сегменты с данными и дважды кликаем на листик слева от названия сегмента. В появившемся окне выбираем по меню опцию "изменить".

Необходимые транзакции в порядке работы с IDOC.
WEDI - меню
SALE – полная. (настройка логических систем через нее) и далее
SM59 – настройка RFC соединения. Здесь задается пароль пользователя под которым будет осуществляться соединение систем. Соединение должно быть настроено на пользователя XXXXXX c соответствующим паролем. Ошибки RFC соединений могут быть связаны именно с этим.
BD64 – задание моделей распределения и фильтров данных.
WE19 – инструмент для тестирования IDOC. Можно скопировать существующий idoc в новый и запустить с указанием FM. Также можно запустить idoc, указав message type или base type.

WE21 – создание порта типа ТРАНЗАКЦИОННЫЙ PFC
WE20 – создание партнеров логических систем Здесь заполняем выходной параметр для исходящей системы и входной параметр для системы входящей. Также здесь используем в выходном параметре ранее созданный порт RFC соединения. Помимо типа сообщения необходимо указывать пользовательское расширение (если оно есть). Здесь также мы настраиваем момент отправки IDOC в другую систему. Например в продуктиве настроена немедленная отправки, а в тесте через программу фоновой обработки (также при нажатии кнопки обработать в тр. BD87 находясь на документе IDOC нашего типа сообщения).

WE57 – Связь между Message Type и обрабатывающим Functional Module.

BD21 – выгрузка изменений в IDOC.
PFAL – выборочное формирование IDOC из указанных объектов.
BD87 – Загрузка IDOC.
WE30 - Создание типов IDOC
WE31 - Создание сегмента
WE60 - Документация по типам IDOC
BIT300 - SAP Курс

IDOC CRETION PROCEDURE
7 Steps For ALE Configuration
ALE Implementation Guide and IDOC Creation
ALE-IDOC Scenario using Custom IDOC
Beginner’s Guide to ALE and IDocs - a step-by-step approach

Creating IDoc Extensions
http://download.oracle.com/docs/cd/E11223_01/doc.910/e11210/app_a_idoc_extn.htm
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/e02a6877-dad1-2c10-ffb1-bb1276e61556

Variant 1
BD60
Change FM for processing BATMAS from SAP to Customer

Variant 2 – не рабочий, перепутаны Inbound и Outbound
WE31
Z1W_BATMAS03
Press button: Create
Field name: ZDUMMY
Data Element: DUMMY
Save
Menu: Edit – Set Release

WE30
Obj.name: Z1W_E1BPBNCOMZ
Extension: X
Press button: Create
Create New: BATMAS03
Description: Replicate batch extended
Press button: Create
(If message appear: 'Action is not possible for generated idoctypes'
Set break point in include MSED5F02
if l_edbas-generated eq 'X'.
And clear this field in debugger.)
Set cursor at segment: E1BPBNCOMZ
Press button: Create
Segm.type: Z1W_E1BPBNCOMZ
Minimum number: 1
Maximum number: 9999999999
Save
Menu: Utilities (M) – Enhancement – Assign Basic Type – ‘BATMAS03’
Menu: Edit – Set Release

WE81
New Entries:
Message Type: BATMAS

WE82
New Entries:
Message Type: BATMAS
Basic type: BATMAS03
Extension: Z1W_ BATMAS03
Release: 700

SE37
Create Function Module Z_E_BAPI_IDOC_INPUT_BATMAS
As copy of BAPI_IDOC_INPUT1

Template
Code:
FUNCTION z_e_bapi_idoc_input_batmas.
*"----------------------------------------------------------------------
*"*"Local Interface:
*"  IMPORTING
*"     VALUE(INPUT_METHOD) LIKE  BDWFAP_PAR-INPUTMETHD
*"     VALUE(MASS_PROCESSING) LIKE  BDWFAP_PAR-MASS_PROC
*"  EXPORTING
*"     VALUE(WORKFLOW_RESULT) LIKE  BDWF_PARAM-RESULT
*"     VALUE(APPLICATION_VARIABLE) LIKE  BDWF_PARAM-APPL_VAR
*"     VALUE(IN_UPDATE_TASK) LIKE  BDWFAP_PAR-UPDATETASK
*"     VALUE(CALL_TRANSACTION_DONE) LIKE  BDWFAP_PAR-CALLTRANS
*"  TABLES
*"      IDOC_CONTRL STRUCTURE  EDIDC
*"      IDOC_DATA STRUCTURE  EDIDD
*"      IDOC_STATUS STRUCTURE  BDIDOCSTAT
*"      RETURN_VARIABLES STRUCTURE  BDWFRETVAR
*"      SERIALIZATION_INFO STRUCTURE  BDI_SER
*"  EXCEPTIONS
*"      WRONG_FUNCTION_CALLED
*"----------------------------------------------------------------------

  DATA:
      t_edidd  LIKE edidd OCCURS 0 WITH HEADER LINE,
      bapi_idoc_status LIKE bdidocstat-status.

*   select segments belonging to one IDoc                              *
  REFRESH t_edidd.
  LOOP AT idoc_data WHERE docnum = idoc_contrl-docnum.
    APPEND idoc_data TO t_edidd.
  ENDLOOP.

*   through all segments of this IDoc                                  *
  CATCH SYSTEM-EXCEPTIONS conversion_errors = 1.
    LOOP AT t_edidd INTO idoc_data.

      CASE idoc_data-segnam.

        WHEN 'E1BPBATCHATT'.
        WHEN 'E1BPBATCHATTX'.
        WHEN 'E1BPBATCHSTATUS'.
        WHEN 'E1BPBATCHSTATUSX'.
        WHEN 'Z1W_E1BPBNCOMZ'.
        WHEN 'E1BPBATCHCTRL'.
        WHEN 'E1BPBNCOM'.
        WHEN 'E1BPBNCOMZ'.
        WHEN 'E1BPMGVMATNR'.
        WHEN 'E1BP3060_ALLOCATION'.
        WHEN 'E1BP3060_VALUATION_CHAR'.
        WHEN 'E1BP3060_VALUATION_CURR'.
        WHEN 'E1BP3060_VALUATION_NUM'.

      ENDCASE.
    ENDLOOP.
  ENDCATCH.

*   call BAPI-function in this system                                  *
  CALL FUNCTION 'BAPI_IDOC_INPUT1'
    EXPORTING
      input_method          = input_method
      mass_processing       = mass_processing
    IMPORTING
      workflow_result       = workflow_result
      application_variable  = application_variable
      in_update_task        = in_update_task
      call_transaction_done = call_transaction_done
    TABLES
      idoc_contrl           = idoc_contrl
      idoc_data             = idoc_data
      idoc_status           = idoc_status
      return_variables      = return_variables
      serialization_info    = serialization_info
    EXCEPTIONS
      wrong_function_called = 1.

ENDFUNCTION.

WE57
New Entries
Function module: Z_E_BAPI_IDOC_INPUT_BATMAS
Function type: F
Basic type: BATMAS03
Extension: Z1W_BATMAS03
Message Type: BATMAS
Direction: 02 (inbound)

WE20
Create Partner
Partner Type LS
Outbound parmtrs.
+
Message Type: BATMAS
Transfer IDoc Immed.: X
Basic Type: BATMAS03
Extension: Z1W_BATMAS03


MSC2N
Change any Batch fields

SE38
Report: RBDMIDOC
F8
Message type: BATMAS

Example 1. IDOC steps
Intermediate Document
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. IDoc is not a process.
- IDocs are stored in the database.
- In the SAP system, IDocs are stored in database tables.
- IDocs are independent of the sending and receiving systems.
- IDocs are independent of the direction of data exchange.

Creation of IDOCs
Transaction code: WE 30
Defining Segment:
Creating Segment : Tcode - WE31
Creating Message Type : Tcode - we81
Assigning Message type to Idoc type: Tcode - we82
Process

The two processes for IDoc are Outbound Process and Inbound Process.
Outbound Process
When the data is sent out from the system, the process is called Outbound Process and the IDoc is known as Outbound IDoc.
Inbound Process
When the data is coming in, the process is called Inbound Process and the IDoc is known as Inbound IDoc.

Outbound Process (Sending System) steps:

Step 1) Goto Tcode SALE:
Click on Sending & Receiving Systems a Select Logical Systems
Here Define the Logical Systems a Click on Execute Button
Go for New Entries
1. System Name : LOG1
Description: Sending System
2. System Name : LOG2
Description: Receiving System
Press Enter & Save it will ask for Request if you want new request create new request or press continue for transferring the objects.
Assigning Client to the Logical System:
Select Assign Client to Logical Systems -a Execute
- 100 a Double click on this and give the following information
Client: Sending System
City: Chennai
Logical System: LOG1
Currency:
Client role:
- 250 a Double click on this and give the following information
Client: Receiving System
City:
Logical System: LOG2
Save this Data.

Step 2) For RFC Creation:
- Goto Tcode SM59 a Select R/3 Connects
Click on create Button
RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles
Give the information for required fields:
RFC Destination : LOG2
Connection type : 3
Target Host : sappdc.wipro.com
System No : 00
Client : 210
User : Login user name
Password :
Save this & Test it and Remote Login

Step 3) Goto Tcode BD64: - Click on the change button
Click on the create model view
Short Text: model view
Technical Name: LMOD
Save this & press ok
Select just created model view
Name: "LMOD"
Goto add message type
Model Name : LMOD
Sender : LOG1
Receiver : LOG2
Message type: ZAZHARMESS
Save and press Enter.

4) Goto Tcode BD82:
Give Model View : LMOD
Partner system : LOG2
Execute this by pressing F8
It will gives you sending system port No: A00000000089 (Like)

5) Goto Tcode BD64:
Select the model view
Goto a Edit a model view a Distribute
Press ok & Press Enter.

Run your Zprogram

Code:
REPORT  ZIDOC1                             .
DATA: Begin of imara occurs 0,
matnr like mara-matnr,
mtart like mara-mtart,
end of imara.
DATA: wamas_con LIKE edidc,
imas_data LIKE edidd OCCURS 0 WITH HEADER LINE,
icom_con LIKE edidc OCCURS 0 WITH HEADER LINE.
PARAMETERS: e_matnr LIKE mara-matnr,
e_msgtyp LIKE edidc-mestyp,
e_rcvprn LIKE edidc-rcvprn.
* retrive app. data from DB
SELECT matnr mtart FROM mara INTO TABLE imara
  WHERE matnr = e_matnr.
*Master idoc control record
wamas_con-rcvprt = 'LS'.
wamas_con-rcvprn = e_rcvprn.
wamas_con-idoctp = 'ZAZHARIDOC'.
wamas_con-mestyp = e_msgtyp.

* master idoc data records
LOOP AT imara.
  imas_data-segnam = 'ZAZHARSEG'.
  move imara to imas_data-sdata .
  APPEND imas_data.
ENDLOOP.

CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
  EXPORTING
    master_idoc_control = wamas_con
  TABLES
    communication_idoc_control = icom_con
    master_idoc_data = imas_data
COMMIT WORK.

6) Verifying Transfer of IDOCs Tcode - we05
ALE/IDOC Status Codes (outbound):
01 a IDoc Added
30 a IDoc ready for dispatch
29 a Error in ALE service Layer
12 a Dispatch ok
03 a Data passed to port ok.

Inbound Process (Receiving System) Steps:
Do the same step as you did in sending system
- Creating IDoc
- Defining the Segment
- Creating Message Type
- Assigning the Message Type
- Defining the Logical System
- Assigning the Logical System
- Creating the Distribution Model

Goto Tcode - we57:
Assign function module to IDoc type
Module: Function module
Basic type:
Message type:
Direction: 2 (inbound)
Creating Inbound process code - we42
Verifying Idoc List Tcode - we05

ALE/IDOC Status Codes (Inbound):
50 a IDoc Added
51 a Application Document not posted
64 a IDoc ready to be transferred to application
62 a IDoc passed to application
53 a Application Document posted

Example 2.
Q. Can somebody give me the step by step procedure for Creating an Inbound Idoc communication in ALE? Not in EDI. Detailed description with Transaction Codes would attract reward points.

A. These are ale configuration steps:

Sending System(Outbound ALE Process)
Tcode SALE - for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 - Create Model View
Tcode BD82 - Generate partner Profiles & Create Ports
Tcode BD64 - Distribute the Model view

Message Type MATMAS
Tcode BD10 - Send Material Data
Tcode WE05 - Idoc List for watching any Errors

Receiving System(Inbound ALE )
Tcode SALE - for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination

Tcode BD64 - Check for Model view whether it has distributed or not
Tcode BD82 - Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 - Idoc List for inbound status codes

ALE IDOC Steps

Sending System(Outbound ALE Process)
Tcode SALE - for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 - Create Model View
Tcode BD82 - Generate partner Profiles & Create Ports
Tcode BD64 - Distribute the Model view

This is Receiving system Settings

Receiving System (Inbound ALE)
Tcode SALE - for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination

Tcode BD64 - Check for Model view whether it has distributed or not
Tcode BD82 - Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 - Idoc List for inbound status codes

Message Type MATMAS
Tcode BD10 - Send Material Data
Tcode WE05 - Idoc List for watching any Errors

1)a Goto Tcode SALE
Click on Sending & Receiving Systems-->Select Logical Systems
Here Define Logical Systems---> Click on Execute Button
go for new entries
1) System Name : ERP000
Description : Sending System

2) System Name : ERP800
Description : Receiving System
press Enter & Save
it will ask Request
if you want new request create new Request orpress continue for transfering the objects

B) goto Tcode SALE

Select Assign Client to Logical Systems-->Execute
000--> Double click on this
Give the following Information
Client : ERP 000
City :
Logical System
Currency
Client role

Save this Data

Step 2) For RFC Creation
Goto Tcode SM59-->Select R/3 Connects
Click on Create Button

RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles

give the information for required fields
RFC Destination : ERP800
Connection type: 3
Description
Target Host : ERP000
System No:000
lan : EN
Client : 800
User : Login User Name
Password:

save this & Test it & RemortLogin

3) Goto Tcode BD64 - click on Change mode button
click on create moduleview
short text : xxxxxxxxxxxxxx
Technical Neme : MODEL_ALV
save this & Press ok
select your just created modelview Name :'MODEL_ALV'.
goto add message type

Model Name : MODEL_ALV
sender : ERP000
Receiver : ERP800
Message type :MATMAS

save & Press Enter

4) Goto Tcode BD82

Give Model View : MODEL_ALV
Partner system : ERP800
execute this by press F8 Button

it will gives you sending system port No :A000000015(Like)

5) Goto Tcode BD64

seelct the modelview
goto -->edit-->modelview-->distribute
press ok & Press enter

6) goto Tcode : BD10 for Material sending

Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute

7) goto Tcode : BD11 for Material Receiving

Material : mat_001
Message Type : MATMAS
and Execute --> 1 request idoc created for message type Matmas

press enter

Here Master Idoc set for Messge type MATMAS-->press Enter
1 Communication Idoc generated for Message Type

this is your IDOC

Change Pointers
I know how to change the description of a material using ALE Change Pointers.
I will give the following few steps

1) Tcode BD61---> check the change pointers activated check box
save and goback.

2) Tcode BD50---> check the MATMAS check box save and comeback.

3) Tcode BD51---> goto IDOC_INPUT_MATMAS01 select the checkbox save and comeback.

4) Tcode BD52---> give message type : matmas press ok button.
select all what ever you want and delete remaining fields.
save & come back.
5) 5) go to Tcode MM02 select one material and try to change the description and save it

it will effects the target systems material desciption will also changes

6) goto Tcode SE38 give program Name is : RBDMIDOC and Execute
give Message type : MATMAS and Executte


ALE/IDOC Status Codes/Messages

01 Error --> Idoc Added
30 Error --> Idoc ready for dispatch(ALE Service)
then goto SE38 --> Execute the Program RBDMIDOC
29 Error --> ALE Service Layer
then goto SE38 --> Execute the Program RSEOUT00
03 Error --> Data Passed to Port ok
then goto SE38 --> Execute the Program RBDMOIND
12 Error --> Dispatch ok

Inbound Status Codes

50 Error --> It will go for ALE Service Layer

56 Error --> Idoc with Errors added

51 Error --> Application Document not posted

65 Error --> Error in ALE Service Layer

for 51 or 56 Errors do the following steps
goto WE19 --> give the IDOC Number and Execute--> Press on Inbound function Module

for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error

Example 3.

Outbound idoc procedure:
1. Creating logical systems: TCode is BD54,
2. Assigning appropriate client: SCC4,
3. Create RFC Destination: SM59,
4. Port Creation: WE21,
5. Partner Profiles Creation: WE20,
6. Disribution Model: create, generate; distribute (TCode: BD64),
7. Consistency Check: BDM5

Inbound idoc procedure:
1. Creating logical systems: BD54,
2. Assigning appropriate client: SCC4,
3. Partner Profiles Creation: WE20.

In Inbound side, Process Code is mandatory.
WE42 - Inbound Process Code

In Outound side, Port is mandatory.
Also we have IDoc Type, EDI Structure.

WE81 - create message type - required in both Outbound; Inbound side
WE82 - for IDoc type; message type relationship - required in both Outbound; Inbound side
WE31 - for segment type relationship, segment creation

Outbound Process - Determine receiver, Segment filtering, Field Conversion, Version Conversion

Inbound process - Version Conversion, Segment filtering, Field Conversion

Serialization - extra in Inbound process

WE47 - Gives full list of IDoc Status
WE60 - IDoc Documentation
BD64 - IDoc Filtering
BD56 - Segment Filtering
BD55 - Field Conversion
BD62 - Relationship b/w Conversion rule; segment
BD79 - (Actual values we are going to send in Conversion Rule) Segment, Conversion rule
BD44 - Serialization Groups - implemented in Inbound side
BD102 - ALE: Outbound Channel Registery
BD103 - ALE: Inbound Channel Registery

Outbound Status T Codes:

Status 42 - when we create Idoc with test tool (WE19),
Status 01 - Idoc created,
Status 29 - ALE Service Layer error,
Status 26 - Syntax error issue,
Status 25 - forced along with syntax errors,
Status 30 - Ready for dispatch to partners,
Status 03 - Idoc with port,
Status 12 - Idoc dispatched already

Inbound Status T Codes:
Status 50 - when added into Inbound system,
Status 65 - ALE Service Layer error,
Status 60 - Syntax errors,
Status 61 - forced along with syntax errors,
Status 64 - Ready to pass to ALE Service layer,
Status 66 - Serialization info. needed, actual Idoc will wait,
Status 62 - Ready to pass to Application layer,
Status 51 - Data/logic issues,
Status 52 - Incomplete posting,
Status 53 - Successful implementation (Application document posted),
status 68 - you can't clear it, needed to recreate Idoc from inbound side,
Status 74 - Idoc created by test tool,
Status 58 - transactional RFC

Batch processing:
RBDAPP01 ALE inbound processing
RBDMANI2 ALE inbound error reprocessing
All TCodes related to IDoc: WEDI

Example 4.
Wrote by lumer
1.WE21 – Определяю порт LUM_FS
1.1.Встаем на типе порта «Файл»
1.2.Кнопка «Создать»
1.3.Порт – «LUM_FS» + произвольное описание ниже
1.4. Убираем Галочку «формат уникода»
1.5.на вкладке «Выходной файл»
1.5.1.галочка «ФизКаталог»
1.5.2.каталог прописываем «/usr/sap/trans/1»
1.5.3.файл lum_fs_file
1.5.4.Save
1.5.5.Кнопка «Тест доступа» выдает «ОК»
2.SPRO-SAP NW – AppServ – IDOC/ALE – Basic – LogicSystems
2.1.Присвоение имени лог. Системе
2.2.Создаю новую строку «LUM_FIL_LS» с текстовым описанием
3.WE20 – определяю партнера LUM_FIL_LS
3.1.Кнопка «Создать»
3.2.№ партнера – lum_fil_ls, вид партнера – LS (логическая система)
3.3.На вкладке «Постобработка …»
3.3.1.Вид – US (Пользователь)
3.3.2.Обработчик – <мой логин>
3.3.3.Язык – RU
3.4. Добавил Outbound параметр (иконка Плюс).
4.BD64 – создаем соединение LUM_CONN
4.1.Кнопка «создание ракурса модели», название LUM_CONN
4.2. Кнопка «вставка типа сообщения»
4.2.1.Отправитель – текущий мандант
4.2.2.Получатель – LUM_FIL_LS
4.2.3.Тип сообщения – MATMAS (стандартный)
5.Создаем данные для передачи – материал через MM01
6.Отправляем изменения через BD10

Пример 3.
Define Logical System through tranaction SALE
Logical Systems - Change View
Allocate Logical System to Client
Set Up RFC Destination SM59
Define Partner Profile:WE20
Define Port for communication- WE21
Define Customer Model:BD64
Generating Partner profile
Transaction : BD82
Activate Change Pointers Globally:BD61
Activate Change Pointer for Message Type: BD50 then go for BD52.
Change ALE Object Type : BD95
Assignment of Object type to Message:BD95
Schedule Program RBDMIDOC to generate IDOCS whenever there is
creation or change in Master Application
Check the IDOC using WE02 or WE05.
Check the Status of the IDOC on both Inbound as well as Outbound side.

RFC
Implementing Parallel Processing - http://help.sap.com/saphelp_47x200/helpdata/en/fa/096e92543b11d1898e0000e8322d00/content.htm

LSMW
Step-by-Step Guide for using BAPI in LSMW

LSMW - Legacy System Migration Workbench

The LSM Workbench is an SAP R/3 based tool that supports the one-time or periodic transfer of data from non-SAP systems ("legacy systems") to SAP systems.
The LSM Workbench helps you to organize your data migration project and guides you through the process by using a clear sequence of steps.

The most common conversion rules are predefined. Reusable conversion rules assure consistent data conversion for different data objects.

How to create a LSMW?

LSMW vs DX Workbench

The LSM Workbench covers the following steps:
Read the legacy data from one or several files (e.g. spreadsheet tables, sequential files).
Convert the data from source format to target format.
Import the data using standard interfaces (Batch Input, Direct Input, BAPI, IDoc).



Experiences made in successful implementation projects have shown that using the LSM Workbench significantly contributes to accelerating data migration.

SAP provides this tool along with documentation to customers and partners free of charge.

Users of the LSM Workbench receive the usual support via SAP Net - R/3 Frontend (component BC-SRV-DX-LSM).

Releases:

Version 1.7.2 of the LSM Workbench ("LSMW 1.7.2") available
Attention : LSMW 1.7.2 requires an SAP R/3 system with SAP R/3 4.0 or SAP R/3 4.5.

Version 1.8.0 of the LSM Workbench (1.21mb) ("LSMW 1.8.0") available
Attention : LSMW 1.8.0 requires an SAP R/3 system with SAP R/3 4.6.

Version 3.0 of the LSM Workbench (1.89mb) ("LSMW 3.0") available for Web Application Server 6.10
Attention : LSMW 3.0 requires a SAP WAS 6.10. Functionality of version 1.7.2 and 3.0 are identical !

Version 4.0 of the LSM Workbench ("LSMW 4.0") integrated in Web Application Server 6.20
Attention : LSMW 4.0 is an integrated part of SAP WAS 6.20.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic    Russian ABAP Developer's Club Forum Index -> Interfaces | Интерфейсы All times are GMT + 4 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


All product names are trademarks of their respective companies. SAPNET.RU websites are in no way affiliated with SAP AG.
SAP, SAP R/3, R/3 software, mySAP, ABAP, BAPI, xApps, SAP NetWeaver and any other are registered trademarks of SAP AG.
Every effort is made to ensure content integrity. Use information on this site at your own risk.