ALE ,Idoc For MIGI transction

Hi Friends,
i am working with Idocs on MIGO Transction its for goods receipt application. when i am traying to genarate ioutbound idocs. in their is no process code. what can i do, can i write a function module (or) trigger ai idoc from BADI programming.

Hi, Bass,
Thanks for your replay, but we r using idoctype: WMMBID02
                                    MESSAGETYPE:    WMMBXY,
                                 SEGMENTS: E1BXYJ,
                                                     E1BXYI,
                                                    E1BXYH,
This is requirment,   pls give me as possible as.

Similar Messages

ALE/IDOC for Data Migration of some master data

Are ALE/IDOC available for data migration of the following master data:?
1)General Tasklists in PM
2)Equipment Tasklists in PM
3)Single Cycle plans in PM
4)Strategy plans in PM
5)Equipments
6)Functional locations
7)Measuring points
8)Work Centers
9)Equipment BOMS
10)QM Info Records
11)Sampling procedure
12)Certificate Profiles QM
13)Inspection Plans
14)Material master-QM View
15)PP Recipes
16)Equipment BOM
If anyone has worked worked on ALE/IDOC for data migration, please guide

Hi Dirk ,
Thanks for your reply . Can we use matmas03 for loading. What will be the differences between these two IDOCS.

Urgent: Creating ALE IDOC for SALES ORDER

hi
please tell me <b>step by step procedure to create ALE IDOC for SALES ORDER?</b>
reward for sure
regards
ravish

Hi,
ALE IDOC
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 ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Create Model View
Tcode BD82 !V Generate partner Profiles & Create Ports
Tcode BD64 !V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 !V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 !V Send Material Data
Tcode WE05 !V 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
Regards

ALE & IDOCs for beginners

Hi All,
I am an abaper with 1.5 yrs of experiance, i have worked in BDC, Reports, SAP Scripts, Smartforms & dailog programming.
I am Intrested in learning ALE & IDOCs.
please provide some info like What is ALE & IDOCs, How it is used & where it is used.
Appropriate points will be rewarded.
Thanks in Advance.

HI,
IDOC stands for Intermediate Document. It is simply a data container used to exchange information between any two processes that can understand the syntax and semantics of the data. IDOCs are stored in database .
IDOC Type defines the structure and format of the business document that is to be exchanged between two systems. (Transaction WE30)
Characteristics:
Name
Permitted Segments
Hierarchy of segments
Mandatory/Optional segment
Min/Max range of each segment
A message type represents a specific type of document that is transmitted between two partners. Messages will be logically related.
A segment defines the format and structure of a data record. Segments are reusable components, which can be used in more than one IDOC type. (Transaction WE31)
Components:
Segment type
Segment Definition
Segment Documentation
At runtime the following events occur:
A unique IDOC Number is allocated
One control record is attached to the IDOC
Segments translate into data records
Status records are attached
Syntax rules are checked
It contains all of the control information about an IDOC. It includes the IDOC number, sender and receiver information, and information such as the message type it represents and the IDOC Type. Control records are stored in EDIDC table.
Administrative section contains the segment
     name, client, IDOC No, segment No and
     hierarchy level information
Data section of a data record is a stream of
    1000 bytes where the actual data resides.
    The data section is mapped to a segment
     type to interpret the meaning of various
     data values in a record
Status records are attached to an IDOC throughout the process as the IDOC achieves different milestones or encounters an error. At every milestone a status code, date, and time are assigned. Status codes 01 to 49 are reserved for outbound process, and 50 and above are reserved for inbound process. It is stored in EDIDS table .
Developing IDOC Type
Analyze the Data
Create Data Elements (SE11)
Create Segments (WE31)
Create Basic IDOC Type (WE30)
Release the Segment Type and
     Basic IDOC Type
Configuration for Outbound
Create a new Message Type (WE81)
Link the IDOC type and Message
     Type (WE82)
Create/Change Partner Profiles (WE20)
Program Flow for Outbound
Provide the selection Screen to enable a
    user to specify the objects for which IDOCs
    are to be generated.
Data Retrieval
Populate the Control Record
Populate the Data Records
Call the ALE/IDOC layer to create IDOCs
Create a new Message Type (WE81)
Link the IDOC type and Message
     Type (WE82)
Allocate the Function Module to the Logical
     Message (WE57)
Define the Settings for Inbound Function
     module (BD51)
Configuration for Inbound
Create a new Process Code (WE42)
Create/change Partner Profiles
Program Flow for Inbound
Read the control record information and
     validate.
Read the IDOC data for an IDOC.
Parse through each data record and build
     the required internal table.
Post it to Database.
Populate the Return Parameters
Dear SWAROOP,
User ID:     p238055
Password:     e?dR9$ac
Dear MANIKANDAN,
User ID:     p238058
Password:     wm2FfKP?
Dear ravi,
User ID:     p233746
Password:     apBtUcP9
HI,
IAM ALSO GIVING A DOCUMENT WHICH HELPS YOU TO UNDERSTAND EASILY AND YOURSELF CAN WORKOUT WITH THIS REAL TIME SCENARIO WHICH TRANSFERS THE DATA BETWEEN TWO SYSTEMS.
Application Linking and Enabling (ALE)
In this document you will learn the step-by-step procedure to setup the ALE system and go through a transaction between two clients
For our purpose we have two clients
namely Client 100 and Client 200.
System name is SAPKDC (FOR BOTH 100 AND 200 CLIENTS).
Distribution of Material Master Data Between two Systems
1) SETUP LOGICAL SYSTEM: (Note: Do Not Create This Step)
To do this follow the following steps
Execute SALE Transaction Code
On The Screen Click on Sending and Receiving Systems.
Then Click on Logical Systems.
Then Click Defining Logical Systems.
Click New Entries Button
(E.g. (LG100 sending system)
(LG200 receiving system))
Enter two logical system names and their description.
Save
Comeback to SALE Transaction Code screen.
2) Now you have to allocate the created logical systems to respective clients.( Note: Do Not Create This Step)
LG100 assign to client 100
LG200 assign to client 200
To do this, do the following.
Click Assigning Client to Logical System.
Ignore the message that comes up on the screen.
Select client 100
Click details button on the toolbar icon or press F2.
In the logical system box, enter LG100.
Click on the save Icon
Click the back button.
Now select client 200.
Click details icon or press f2.
In logical Systems box, enter LG200.
Save
Back.
Comeback to SALE Transaction Code screen.
3) Maintain RFC Destination: (TR.CODE:SM59)
(Note: Do Not Create This Step)
Click Create Button on the Screen
On the Screen Maintain RFC Destination i.e LG200.
Enter LG200 in RFC destination box.
Connection type is 3
Give a description for the RFC destination.
Maintain Technical Settings on Details on Technical Settings tab
Target Host as : SAPKDC (NOTE: Save it as a Host Name)
Maintain Logon Details on Logon/Security tab.
Language: EN.
User:      MMUSER200 (This is the logon for dist.)
Client :      200
Password:      MM1234.
Save.
Click on create to do the above process for Client 200 in
The client 200 system.
4) Maintain Distribution Model.(BD64). (ABAPer role starts here)
Execute Maintain distribution model directly for
creating the model.
Click on change mode button on App tool bar of the Screen.
Create Model View pushbutton on App tool bar of the Screen.
A pop screen will appear in which you specify
Short text as Distribution for MM Data.
Enter Technical Name as LGMODEL.
Select Model View and Click on Add Message Type Pushbutton on App toolbar of the Screen.
A popup screen will appear in which you specify
Model View as      LGMODEL.
Sender as           LG100.
Receiver as      LG200.
Again Click on Add Message Type Pushbutton on App toolbar of the Screen.
A popup screen will appear in which you specify
Model View as      LGMODEL.
Sender as           LG200.
Receiver as      LG100.
SAVE.
On the same screen goto Menubar and select Environment.
And then select Generate Partner Profiles , then execute it.
On the Screen specify the Logical System as LG200.
Then execute the screen.
Click back.
Again On the same screen goto Menubar and select EDIT.
Again select Model View and then select Distribute.
****LOGIN to client 200.
Execute Tr.code BD64 and again On the same screen goto Menubar and select Environment.
And then select Generate Partner Profiles , then execute it.
On the Screen specify the Model View as LGMODEL
And Specify the Logical System as LG100.
Then execute the screen.
Click back.
*******Switch back to client 100 Session.
5) Create Material using MM03 Tr.Code.
Enter the material name as LGMATERIAL
Industry sector as      Mechanical Engineering
Material Type as           Finished Products.
And then Click on Data Pushbutton on the App tool bar.
Select views.
In the select views box for materials check basic data 1 AND 2.
Click enter icon.
In the next screen that you get
Give the text of the material as NEW MATERIAL.
Base unit of measure as KG.
Gross Weight as 200.
Net Weight as 100.
Weight Unit as KG.
In the description area language (E) and material description.
Click Save.
Now I Created a Material in Client 100 , I want to transfer this data to Client 200.
6) Execute BD10 to transfer the material in which you specify
the material as LGMATERIAL and
message type as MATMAS (client100).
Then a Screen will be displayed in which it shows that
1 Master Idoc Generated .. Enter
1 Communication Idoc Generated..Enter.
*******LOGIN to Client 200.
7) Execute BD11 to get the material in which you specify
the material as LGMATERIAL and
message type as MATMAS (client200).
8) Execute Tr.code MM03 and give the material as LGMATERIAL
and see that the material is displayed as it was in Client 100.
If not follow these steps.
9) Execute Tr.code WE19( for rectification of errors in client200).
Specify the Existing Idoc Number and Executes it .
A Screen is displayed in which you specify the corresponding Function Module as INPUT_IDOC_MATMAS01 and execute it.
10) Execute Tr.code MM03 and give the material as LGMATERIAL
and see that the material is displayed as it was in Client 100.
Now the Material is correctly displayed in Client 200.
11) Monitoring of IDOCS.
Transaction Codes:
IDOC Display of Status: WE 05.
IDOC Date and Time:   WE07.

Regarding ALE-iDoc for Customer Master, J1ID and FD32

Hello all
Scenario:
As per client's requirement we have to develop idoc so that followings requirements will meet:
Say there are two servers a) MDM Server b) PRD Server
1] As and when I'll create customer master data in MDM server then customer master should get created with that data in PRD server
which I can achieve through BD12 by doing some idoc enhancements
2] Simillarly when i'll create data using transaction J1ID and FD32 in MDM Server (Data relevant to customer master) then that data also should get created in PRD server using Idoc
May I know which
1)message type we can use (as we use DEBMAS in case of Customer Master) for J1ID and FD32
2) Any transaction to send data from one server to another server for transaction J1ID and FD32 (as we use BD12 in case of Customer master for sending data created using transaction XD01)
Thanks,
Mahesh

Hello Mahesh,
In the case of customer master it would be better if you would use standard message types and t code to transfer ddata.
But in the case J1ID and FD32 you can build a standalone idoc
Follow these steps to build custom message types and futher transactions
WE81 - Create message type
WE31 - Create segment
WE30 - Create Idoc type
SALE - Define Logical system (not required if already exists)
SM59 - Define RFC (not required if already exists)
WE21 - Define ports (both in sender and receiver)
WE20 - Define Partner profile (both in sender and receiver)
BD46 - Distribue the model view.
SE38 - Create a program to send the idoc in the sender sytem.
SE37 - Build inbound function module to receive the idoc for receiver system
WE57 - Assign FM to message type
BD51 - to change the characteristics for inbound FM
WE42 - Create Inbound process code.
Hope this would help you.
Thanks and Regards,
Ranjith Nambiar

ALE/iDoc for Work Center data transfer

Hello, community.
I am working on several interfaces for the PP and PM modules using iDocs/ALE.
One of the requirements is that only created and modified data must be distributed from R/3.
For Work Centers, we are using basic type LOIWCS02 and message type LOIWCS. We are generating iDocs through transaction POIM, which has two transfer modes: Complete (data for all Work Centers etc.) and Change (only new and updated data).
The Change Transfer Mode assumes you have set both Change Pointers and Change Documents for the objects to be transfered. Otherwise, it'll work just like the Complete Transfer Mode.
Our PP consultant told me there is no configuration to generate Change Documents for Work Center data modifications.
Can anybody give me other opinions? I'll resort to Z-table solutions only if I have no other options.

Hi Danilo,
Do you know what the process codes are for
LOIWCS and LOIROU ?
Appreciate your help.
Thanks,
Gopi.

ALE IDOC for Purchase order to sales order

Hi Friends,
I am sending P.O. from one system to other,using message type ORDERS and basic type ORDERS05 .
On receiving system I am using inbound process code ORDE.
Sending is successful but on receiving side its giving me error, VKORG, VTWEG, SPART cannot be determined for customer 0000000001 .
So please suggest me some solution on this ,,
Proper points will be rewarded to helpful answer.
Thanks,
Brijesh........

Hi brijesh,
I am also working on creating PO to SO . The problem you are getting is one of the problem i have faced . But we can solve this easily.
In your outbound idoc you have 4 fields with E1EDK14.
This segment stores the values for SPART,VTWEG,VKORG .
So in the qualifying fields of this segment 006,007,008 should be there for the above fields respectively and their values in the orgid field.
I have written the coding in outbound side user exit.
MM06E001 in the 11th function module .
so try this it will solve the problem.
Thanks
vamshi

Ale idocs for hr

hi,, can any one help me out in message types and idoc types in HR and their functionality..
thanks in advance...

Hi,
Have a look at below link.
http://www.erpgenie.com/sap/sapedi/message_types_bp_hr.htm
<b>Reward points</b>
Regards

ALE/IDOC failure

Dear all,
We setup the ALE Idoc for OrgModeler 4.1 which runs fine for initial few minutes and then dies down with following lines
[Fatel Error] :-1:-1: Premature end of file.
I have tested the same setup in DEV SAP system and it worked fine with the additional config required in JCo files/versions etc. but the moment I change the connection string to the PRD SAP system we encounter this issue.
Any clues in this case?
Best regards.
Mohammad

Mohammad.
Some things to consider...
1) Have you replicated the precise set-up you have in DEV in PRD?
i.e. have you worked through each step in the "ALE Setup and Data Extraction" section in the VSN41 Deployment Guide and not received any error message at any stage. If you are unsure I would suggest working through it again to confirm.
2) Have you tested your modified connection string in AdminConsole (or did you just change it)?
3) Does the account you are using for the production system definitely have the appropriate authorisations in place?
4) Have you tried an out of the box build (minimal configuration - just enough to connect & authenticate) to confirm this isn't somehow related to anything specific to your configured build?
Regards,
Stephen.

ALE IDOC object development

Hi All,
I am developing one object using ALE IDOC. But i have little knowledge of ALE IDOC.
The requirement is to pass data from from corporate HCM side to SAP BW side if there
is corresponding field in the SAP BW side. i know i have to use ALE ,IDOC for this. i am planning
to proceed as below (this help i got from SDN site only).
1) Creating a Function Module.
2) Using t-code BD51 to define the ALE attributes of the func module so that it can be assigned to process
code latter.
3) Execute WE 57 to assign func module to idoc type and message type.
4) Execute WE 42 to define the process code and assign func module to the process code.
5) Create/ Modify the partner profile and include the new process code.
Please tell me how can i use these steps in my object development. Also i dont have any idea of "process code". Can any one of u help me in solving this.
Thanks,
Rupesh

what is the trigger point for data transfer ? that decides the exact process.

How many types of ports are there which we use for data transfe in ale/idoc

friends let me know how many types of ports are there which we use for transfering
data in ale/idocs?

Hello,
you can use file port,trnasactional RFC port.FI you are using IDOC-XML conversion combination,then you can XML port also.
Thanks

In ALE/IDOC Change Pointer using Maintenance order for message Type

Hi All Expert,
I am using Maintenace order to send via ALE/IDOC(Change ponters), i need standard message Name for Maintenance Order,

Hello,
I'm not sure you're taking the best approch.
Usually when you need to migrate ISU contracts into an ISU-CRM integrated system, you first migrate everything you need in ISU through the VERY powerful migration workbench available (transaction code EMIGALL), and then you replicate your data to CRM via INITIAL download.
That's definitely the strategy that will give you the best performance, and less work.
Kind regards,
Nicolas Busson.

ALE/IDOC and RFC/BAPI Integration Scenarios with SAP DS for ESA v3

Hi,
we are planning two PoCs of Integration Plattforms. One of our major requirement set is SAP Integration into our existing SOA.
Because we also have R/3 4.7 Systems in production, we are planning to test ALE/IDOC and RFC/BAPI Integration scenarios with these Integration Plattforms.
My question is:
We are looking for are smart solution to get a SAP Test Environment, where we can test ALE/IDOC und RFC/BAPI Integration scenarios.
It is possible to do this with SAP DS for ESA v3 or shall we better use IDES for that purpose?
Best regards,
Steven

Hi Abhishek,
This is our scenario. We are doing an integration of SAP HR r/3 system with the CRM system. We need housing information details of the employees which we have in custom infotype 9310 in SAP HR system and we need those details in the CRM system. So am planning out for an ALE/IDOC approach for the integration and gonna maintain the 9310 details in a custom table. In the CRM system, we gonna build a BOL layer for accessing the 9310 details. Also i'm preparing a HLD for this process. I wanna read and go through few same HLD's before i submit my proposal to my client. Please suggest me and help me out.
Thanks in advance.
Regards,
Arunmozhi.

LSMW: ALE/IDOC, getting the Create a partner profile for message type

Hi Gurus,
In my current project, i need to upload the employee data using the ALE/IDOC method with the LSMW
when i'm generating the idoc in the 13th step, its posing the information message stating that:
Create a partner profile for message type 'ZEMP_MSG'
In partner profile i already assigned the message type .
How to solve this issue, <inappropriate urgency removed by moderator>
Thnks&regards,
sree
Edited by: Thomas Zloch on May 13, 2011 9:55 AM

This forum's aim is not only to search for information and ask the members questions, but also to share knowledge. When you have asked a question and found a solution, do share with the rest.

How is partner profile for ALE/IDOC transported?

Hi experts,
How is a request created for transporting configurations in ALE/idoc.
Valuable answers will be generously rewarded.
regards,
Shrita.

Hi,
some configurations are client dependent and some are client independent.
so client dependent configurations are transported to different clients using SCC1 transaction.
and client independent configurations they refelect automatically.
Regards
vijay

ALE ,Idoc For MIGI transction

Similar Messages

Maybe you are looking for