SAP을 즐기는 사람들

Step1: SE61 T-CODE를 실행시킨다.
Step2: 화면에 아래와 같이 입력한다.

Step3: change 버튼을 클릭하여 변경할수 있다.  최대 16행 70열을 입력할수 있으며 @<code>@ 사이에 01 02 0A 9A등 아이콘 코드를 넣어 아이콘으로 표시할 수 있다. 만약 편집기를 바꾸고 싶으면 Goto -> Change editor를 통해서 편집기를 상호 전환 할 수 있다.

Wage_Type_Characteristic.xlsx

Wage_Type_List.xlsx

Wage_Type.xlsx

Payroll_Infotype.xlsx

RPTQTA00

Automatic generation of IDOC when we change the MASTER DATA:

Change Pointers:
Change documents are working based on change document technique which
tracks changes made to the key documents (Material Master, Customer Master,
Vendor Master.Etc) in SAP.

Changes made to the keydocuments are recorded in the change document Header
table i.e. CDHDR and Item table CDPOS, Additional change pointers are written
in the BDCP and BDCPS tables.

Change pointers technique is used to initiate the outbound process automatically
when master data is created or changed.

A standard program RBDMIDOC is sechuled to run on periodic basis to evaluate the change pointers for a message type and starts the ALE process for distributing the Masterdata to the appropriate destination.

'Object' is collection of fields of different database tables. T.code for creating an object
is SCDO.

Configuration for Change Pointers:

1. BD61 Active change pointers generally
- Check the checkbox "Change pointers activated -generally"
- Save it
2. BD50 Active change pointers for Message Type

Message Type Active
DEBMAS Check the check box

3. BD52 Maintain Table Views

Enter the Message type "DEBMAS" and press enter.

For example
OBJECT TABLE NAME FIELD NAME
DEBI KNA1 NAME1

5. WE21 Port
6. WE20 Partner Profile
7. BD64 Distribution Model

Use RBDMIDOC program.for executing this program we need to give message type like
MATMAS or
DEBMAS or
CREMAS
depending on your requirement.

----go to SE38 tcode Maintain variants then use the same back in scheduling.

STEPS IN BACKGROUND SCHEDULING:

Use tcode SM36
Click Job wizard in the button set
Click Continue
Enter Job name and press continue
Select ABAP program and press Continue
enter Program name and press continue
and again press Continue
set Schedule type immediately and continue
Select periodic job checkbox, press continue
Select none of the above and click on other periods – give one-minute and then press create
Press continue and then press complete.

참조할 부분:

Change document object 생성 방법

Proceed as follows:

1. Call the change document maintenance transaction (Tools
® ABAP/4 Workbench ® Development ® Other tools ® Change doc. object). An overview of existing change document objects is displayed.
2. Choose the menu option Create.
3. Enter a name for the change document object which is to be created. It can be any name starting with "Y" or "Z" (customer name area).
4. Choose Continue. A new window for inputting the associated tables appears.
5. Enter a descriptive short text for the change document object.
6. Make the following entries for each table whose changes are to be logged in the change document for this change document object:

- Table name
Name of the table, as defined in the Dictionary

- Copy as internal table flag.
If the change data are to be passed in an internal table (multiple case), mark this field. If it is not marked, the change data are passed in a work area (single case).

- Doc. for individual fields at delete flag
If you want separate log entries for each field when data are deleted, mark this field. If it is not marked, the deletion of all relevant fields is entered in one document item.

- Ref. table name. (Name of the reference table)
If the currency and unit fields are defined in a reference table, rather than in the table passed, you must pass the name of the reference table, and the field referred to, to the function module. Create an INTTAB structure in the Dictionary, and define fields for this structure, which are made up of the names of the associated reference table and the reference fields.
Enter the name of this structure here.
In the individual case, the reference information is passed in the form of two extra work areas (old, new). In the collective case, the internal tables are extended to include the reference structure.

- Name of the old record fields
Only possible for single case, i.e. when passing change data in a work area: If you do not want to use the * work area, enter an alternative work area name here.

7. After inputting all relevant tables, choose Insert entries. The new entries are copied into the display.
8. Save your entries.

Transport change document object

The change document objects are a transport object type, a change request is made when the object is created.

During transport the object-specific update is generated in the target system.

Step-1. T-CODE WE31

IDOC Segment를 생성하는 단계이다.
생성 버튼을 클릭하여 전송에 필요한 필드들을 정의하여 준다.
테스트이므로 필드는 간단하게 material number만 준다.
모두 만들어 준다음 we31 초기화면으로 돌아와서 상단메뉴에서 edit->set release를 한번 클릭해준다.


STEP-2. T-CODE WE30

IDOC 타입을 설정하는 단계이다. 아래 그림과 같이 OBJ. Name을 입력하고 basic type으로 선택한 다음 생성 버튼을 클릭한다.
create new를 선택한다음 description을 적당하게 입력해주고 나서 확인 버튼 클릭

IDOC 타입에 커서를 옮겨놓고 생성 버튼을 클릭하면 아래와 같은 화면이 튀어 나오는데 STEP-1에서 만들어줬던 IDOC segment type을 입력해주고 나머지 최소 최대 건수를 적당히 입력해준 다음 확인 버튼 클릭

1번 스텝과 마찬가지로 WE30 초기화면에 돌아온뒤 메뉴에서 Edit->set release를 한번 클릭하여 준다. 단 한번 release 시키고 나면 다시는 수정할 수가 없으므로 실제 개발할 시에는 release할때 조심해서 해야 한다.

Step-3. T-CODE WE81

메시지 타입을 생성하는 단계이다.  변경모드로 수정한 다음 new entries 버튼을 클릭하여 아래와 같이 입력하고 저장해준다.
현재까지 진행한 작업을 idoc document (T-CODE WE60)에서 조회하면 아래와 같다.


STEP-4 T-CODE: SM59

Receiver system 에 대한 RFC connection을 정의하는 단계이다. 이부분에 대해서는 XI 컨설턴트나 BASIS의 도움을 받을 수도 있겠다. 우선 ABAP connectors 폴더를 선택하고 생성 버튼을 클릭한다.
우선 technical settings 탭을 선택하고 target host, system number, ip address, gateway host, gateway service 등을 입력해준다. 이러한 정보들은 XI 혹은 BASIS 컨설턴트에게 요구하면 제공해줄수 있다.

다음 logon & security 탭에서 XI 서버의 로그인에 필요한 client 아이디 패스워드 정보를 입력한다. 이러한 정보도 역시 XI 컨설턴트에게 요구하면 되겠다.


STEP-5 T-CODE: WE21

Receiver system의 IDOC 프로세싱에 필요한 포트를 정의하는 단계이다. 우선 Transactional RFC 폴더를 선택하고 생성 버튼을 클릭한다.
포트 이름을 아래와 같이 입력해주고 확인 버튼을 클릭한다. 

Description을 적당히 적어넣고 STEP-4에서 정의한 RFC destination을 RFC destination에 넣고 저장한다.


STEP-6 T-CODE: BD54

Receiver System의 logical system을 정의하는 단계이다. new entries를 클릭하여 logical system과 이름을 입력해주자. 여기서는 PD1CLNT230을 사용하겠다. 단 이때 logical system 명칭과 RFC desination 명칭 사이에는 사실 아무런 관계가 없다.


STEP-7 T-CODE: WE20

Receiver system의 파트너 프로파일을 정의하는 단계이다. Partner Type LS(Logical system)을 선택하고 생성 버튼을 클릭하여 아래와 같이 입력해준다. 이때 partner No.는 step-6에서 정의한 logical system을 입력해주고 파트너 타입은 LS를 선택하여 준다.
우선 Post processing: permitted agent에서 type은 US를 Agent는 XI 서버의 사용자 아이디를 선택하여 준다.
다음 CLASSFICATION TAB에서 Partner status가 A로 되었는지를 한번 확인해준다.
다음 outbound parameters에서 새라인 추가 버튼을 클릭하여 step-3에서 만들었던 메시지 타입을 추가해주고 receiver port는 step-5에서 정의했던 포트를 넣어주면 된다. outbound mode에서는 trans idoc immed를 선택해주고 basic type에는 step-2에서 정의한 IDOC 타입을 입력하도록 한다.

여기까지 해서 Receiver 시스템에 대한 sender system쪽의 셋팅은 끝났다. 다음에는 XI 서버에서 Sender system에 대한 셋팅 부분이 되겠다.

STEP-8 T-CODE: SM59

XI 시스템에 로그인한뒤 XI에서의 RFC destination을 정의해주는 단계이다. 설정하는 방식은 step-4와 흡사하며 이때 host나 gateway 등등은 모두 SAP R/3의 정보를 입력해 주어야 한다.
접속정보도 마찬가지로 R/3 정보를 입력해주고 저장한다.

STEP-9 T-CODE: IDX1

IDOC Adapter에 대한 port 및 logical system을 정의하는 단계이다. 포트명을 정의할때 주의해야 할 점이 하나있는데 반드시 SAP+SYSTEM ID 세자리로 해서 만들어주어야 한다. 여기서는 SAPAD1이 되겠다. 그리고 RFC destination에는 step-8에서 정의한 rfc destination을 지정하면 된다. 아래와 같이 입력하고 저장한다.
이것으로 양쪽 시스템의 세싱은 전부 끝났고 이제는 테스트 하는 일만 남았다.

테스트는 T-CODE WE19에서 진행 할 수 있으며 아래와 같이 BASIC TYP을 입력하고 실행 버튼을 클릭한다.
다음 EDIDC를 더블 클릭하여 아래와 같은 컨트롤 정보를 입력한다.  여기서 receiver쪽 정보는 우리가 R/3에서 셋팅했던 정보이고 sender쪽 정보는 XI에서 셋팅 했던 정보들이다.
그다음 ZMATERIAL_DETAILS를 더블클릭하여 전송에 필요한 정보를 입력하고 확인버튼을 클릭한다. 그다음 상단 툴바의 standard outbound processing 버튼을 클릭하여 확인 버튼을 클릭하여 주면 outbound process가 시작되는데 만약 위의 셋팅에 아무런 문제가 발생하지 않았다면 idoc sent to SAP system or external program이라는 정보 메시지가 튀어나오게 될것이다.

idoc이 SAP->XI 로 정상적으로 나갔는지 여부는 WE02/WE05 Transaction을 통해서 모니터링 할 수 있다.
XI서버에 데이타가 제대로 들어왔는지는 SXMB_MONI T-CODE를 이용해서 체크 할 수 있는데 이부분은 XI 컨설이 작업하는 부분이라 ABAP쪽에서는 나가는것까지만 체크하면 되겠다. 남의 밥그릇까지는 건들지 말자..^^

LE – Application Link Enabling is a mechanism by which SAP systems communicate with each other and with non-SAP EDI subsystems. Thus it helps integration of distributed systems. It supports fail-safe delivery which implies that sender system does not have to worry about message not reaching the source due to unavoidable situations. ALE can be used for migration and maintenance of master data as well as for exchanging transactional data.

The messages that are exchanged are in the form. of IDocs or Intermediate Documents. IDocs act like a container or envelope for the application data. An IDOC is created as a result of execution of an Outbound ALE. In an Inbound ALE an IDOC serves as an input to create application document. In the SAP system IDocs are stored in the database tables. They can be used for SAP to SAP and SAP to non-SAP process communication as long as the participating processes can understand the syntax and semantics of the data. Complete documentation on IDOC is obtained by using transaction WE60.

Every IDoc has exactly one control record along with a number of data records and status records. Control record has the details of sender/receiver and other control information. Data records contain the actual business data to be exchanged while the status records are attached to IDoc throughout the process as the IDoc moves from one step to other.

Now, let us understand the ALE Configuration by means of an example scenario below:

The Scenario

 

 

Data from custom tables (created in customer namespace) is to be formatted into an IDoc and sent from one SAP R/3 system to another using ALE service. We need to have two instances of SAP R/3 systems or we can simulate this on two clients of the same SAP R/3 system.

Create three tables as shown below.

 

 

Creating Custom IDoc type and Message type
All the objects created should be present on both source as well as target system(s).

1. Create segments – Transaction WE31

• Create a segment ZRZSEG1
• Add all fields of table ZCUSTOMERS to it
• Save the segment
• Release it using the menu path Edit -> Set Release
• Similarly create two more segments given below
• Seg. ZRZSEG2 – to hold all fields of table ZSOHEADERS
• Seg. ZRZSEG3 – to hold all fields of table ZSOITEMS

2. Create Basic IDoc type – Transaction WE30

 

• Create a Basic type ZRZORDER
• Add the created segments in the hierarchy shown
• Maintain attributes for each of the segments
• Save the object and go back
• Release the object using the menu path Edit -> Set Release

3. Create/Assign Message type – Transactions WE81/WE82

• Go to WE81
• Create a new Message type ZRZSO_MT
• Save the object
• Go to WE82 and create new entry
• Assign the message type ZRZSO_MT to the basic type ZRZORDER
• Also specify the Release Version
• Save the object

Outbound Settings

Define Logical Systems and Assign Client to Logical System – Transaction SALE

 

 

• Go to Define Logical System (See the figure)
• Define a new logical system to identify the local system and save it
• Now, go to Assign Client to Logical System (See the figure)
• Add a new entry
• Specify the client, previously created logical system and other attributes
• Save the entry
• Define a new logical system to identify the partner system and save it

Maintain RFC Destinations – Transaction SM59

• Create a new RFC destination for R/3 type connection
• Specify the target host on Technical settings tab
• Provide the Logon credentials on the Logon/Security tab
• Save the settings
• To verify the settings, Click on Test connection or Remote logon

Define Ports – Transaction WE21

• We need to define a tRFC port for the partner system
• Click on Transactional RFC node
• Create a new port
• Provide a description
• Specify the name of the target RFC destination
• Save the object

Maintain Distribution Model – Transaction BD64

• Click on Change
• Create a new model view
• Provide a Short text and Technical name to the model view
• Add message type
• Specify sender and receiver systems
• Also, specify the message type that we created previously
• Save the Distribution model

Generate/Create Partner Profile – Transactions BD82/WE20

 

 

• To generate Partner profiles automatically you may use BD82 or go to BD64 and use the menu path Environment -> Generate partner profiles
  • Otherwise, you may use transaction WE20 to create a partner profile
• On selection screen, specify the model view, target system and execute
• The result log will be displayed on the next screen
• To verify the partner profile go to WE20
• Check the partner profile for the target system

Distribute Model View – Transaction BD64

• Select the Model View
• Go to menu path Edit -> Model View -> Distribute
• Result log will be displayed on the next screen

Outbound IDoc Generation Program

Create an executable program ZRZ_ORDER_IDOC in SE38. Below, I have described the program logic:

• Fetch the data from the DDic tables ZCUSTOMERS, ZSOHEADERS and ZSOITEMS as per the selection criteria
• Fill the control record structure of type EDIDC
  • Specify message type, Basic IDoc type, tRFC Port, Partner number and Partner type of the receiver
• Fill the data records
  • Define structures like the IDoc segments
  • Fill the structures with fetched data
  • Pass the segment name and the above structure to the appropriate fields of EDIDD type structure
  • Append the EDIDD structure to the EDIDD type internal table
• Now, call the function module MASTER_IDOC_DISTRIBUTE and pass the IDoc control record structure and data record table
• Commit work if return code is zero
• Function module returns a table of type EDIDC to provide the details about generated IDoc
• Display appropriate log

Inbound IDoc Posting Function Module

In the receiving system, create a function module Z_IDOC_INPUT_ZRZSO_MT using SE37. Below, I have described the logic for the same.

Add Include MBDCONWF. This include contains predefined ALE constants.
Loop at EDIDC table

• Check if the message type is ZRZORDER. Otherwise raise WRONG_FUNCTION_CALLED exception
• Loop at EDIDD table
  • Append data from the segments to appropriate internal tables
  • For example: append data from ZRZSEG1 segment to the internal table of type ZCUSTOMERS
• Update the DDic tables from internal tables
• Depending on the result of the update, fill the IDoc status record (type BDIDOCSTAT) and append it to the corresponding table.
  • Status 53 => Success
  • Status 51 => Error

Inbound Settings

• Define Logical Systems – Transaction SALE (Please refer to Outbound Settings)
• Assign Client to Logical System – Transaction SALE (Please refer to Outbound Settings)
• Maintain RFC Destinations – Transaction SM59 (Please refer to Outbound Settings)
• Define Ports – Transaction WE21 (Please refer to Outbound Settings)
• Generate/Create Partner Profile – Transactions BD82/WE20 (Please refer to Outbound Settings)
• Assign Function Module to Logical message – Transaction WE57
  • Create a new entry
  • Specify name of the Function Module as Z_IDOC_INPUT_ZRZSO_MT
  • Also, specify Type as F, Basic IDoc type as ZRZORDER, Message type as ZRZSO_MT and Direction as 2 (Inbound)
  • Save the entry
• Define Input method for Inbound Function Module – Transaction BD51
  • Create a new entry
  • Provide Function Module name as Z_IDOC_INPUT_ZRZSO_MT
  • Specify the Input method as 2
  • Save the entry
• Create a Process Code – Transaction WE42
  • Create a new Process Code ZPCRZ
  • Select Processing with ALE Service
  • Choose Processing type as Processing by function module
  • Save the entry
  • On the next screen, select your function module from the list
  • Save the changes
  • Now you will be taken to the next screen
  • Double-click on Logical message
  • In the Assignment to logical message, specify the message type ZRZSO_MT
  • Save the changes

Send and receive data

On the sender system, execute the IDoc Generation Program. Check the status of IDoc using transaction WE02.

 

 

Check the status of the IDoc in the receiver system using transaction WE02. You can also check the contents of DDic tables to make sure that the records have been created in the receiver system.

 

 

Thus to summarize we have learned how to:

• Create a custom IDoc
• Write an Outbound IDoc Generation Program
• Write Inbound Function Module to post Inbound IDoc
• Configure and test ALE scenario to transmit data between systems distributed across the network

Source: http://www.riyaz.net/blog/index.php/2008/01/19/beginners-guide-to-ale-and-idocs-a-step-by-step-approach/

IDOC TO XI 왕초보 가이드  STEP BY STEPidoc_beginner_guide.pdf