ALE/IDOC Mapping
Hello all,
Can anyone tell me where I need to mention the name of the FM MASTERIDOC_CREATE_SMD_DEBMAS in the ALE Configuration to trigger the change pointers?
Do I need to mention it in the OUTBOUND PARAMETERS of the PARTENER PROFILES or just activate it in the trnx BD60.
I appreciate your help.
Thank you.
Hi Joslyn,
You need to setup change pointer for DEBMAS message type.
For more information on change pointer configuration, please check this link.
http://help.sap.com/saphelp_erp2005/helpdata/en/12/83e03c19758e71e10000000a114084/content.htm
then you need to setup ALE distribution model (BD64) for sender and receiver systems, partner profile (WE20) and file ports (WE21).
At last, you can execute program <b>RBDMIDOC</b> (BD21) to generate DEBMAS IDocs.
Hope this will help.
Regards,
Ferry Lianto
Please reward points if helpful.
Similar Messages
-
Hi ,
I am new to SAP PI. We are using B2B scenario in office. We are getting ALE idoc from one system and generating idoc to receiver system inbetween we need to map the fields by using PI. Please help me on this, How to Map the idoc fields in PI?
Thanks in advance.Hi,
Can you explain what type of IDOCs you are using. And also you specified that its a B2B scenario, but you are having 2 R/3 systems on both sides right?
Specify the type of business scenario.
Thanks,
Anudeep. -
Hi,
I can see the ALE IDOC configurations at many places . Whats the process to send an IDOC to External Non-SAP System?
Does it differ much??
Please explain the steps.Hi,
Pushing the IDOC from SAP to External:
IDOC are SAP specifc data structure. Only SAP understands IDOCS natively. Normall what you can do is write a process that maps the IDOC to the format the recieving system is looking for. ie: flat file etc... Or if the external system can be coded to understand the IDOC structure, you could put a flat file with this structure to be read by teh external system.
Pulling from the External system:
Usin connectors, the external system can call a BAPi or RFC function module that can create IDOCS and pass the data to the external system using the IDOC structure.
thanks.
JB -
ALE IDoc Conversion Rule or BADI
Hi,
I'm new to ALE IDoc. I have a requirement to hide some sensitive data field for the HR information when outbound the Idoc.
Example, I need to outbound the IT8 Basic Pay with payscale area etc but not with the basic pay amount. I can convert the basic pay amount to zero when the idoc is being created.
I've searched through some information and found out that there are several ways to achieve it. However, I'm not sure which one is a better way.
Is it using the Conversion Rule (BD62) or using Badi or Idoc Reduction method is better?
Kindly give me some hints as I'm very confuse of which one is the better solution.
Many thanks in advance.No user exit is needed for conversion rule.
However, you should remember that conversion rules are applied segment fields for a particular message type. So wherever the IDoc message type is used the rule will be applied. If you want to associate the rule for any other condition in addition to message type better to go with a BADI
These are steps to create and apply a conversion rule to a message type:
1. Transaction BD62 - Create conversion rule and assign it to a IDoc segment
2. Transaction BD79 - Define the conversion rule by selecting your field and clicking display button. Once inside you can use various options like set constant to map 0 to the basic pay
3. Finally assign the conversion rule to your message type using BD55
As for BADIs, IDOC_DATA_MAPPER is also suited for your requirement, the method PROCESS, allows you to manipulate your IDoc fields whichever way you want. You get the control record, data records, using which you can restrict your manipulation to specific message type or other conditions
To above post, BADI IDOC_CREATION_CHECK should not be used for mappings/conversions as its specific purpose is to stop creation of an IDoc under required conditions -
ALE/Idoc configuration - (R3--XI--File)
Iam XI developer and know basic ABAP. Client is NOT using any Idocs right now. I have to develop a scenarios ( including ALE/Idoc Configuration on R3 for standard Idocs like MATMAS, DEBMAS, CREMAS etc ) both Master data and change pointer to XI and then to File.
Would some one show me step by step procedures for ALE/Idoc configuration on R3 and XI.I need to send both Master data and incremental data to XI possibly by bundling Idocs to XI.Hi Ram...
Once the mapping is done then re-check the ALE settings.
<b>SAP XI</b>
1) <b>RFC Destination (SM59)</b>
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
<b>2) Create Port (IDX1)</b>
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
<b>3) Load Meta Data for IDOC (IDX2)</b> a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
<b>SAP R/3
1) RFC Destination (SM59)</b>
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
<b>2) Create Port (We21)</b>
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
<b>3) Create Partner Profile (WE20)</b>
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
<b>In SLD System Landscape Directory</b>
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
<b>In Transaction SALE</b>
Define and Assign the logical system name.
Cheers,
raghavesh -
Hi every one,
I am new to ALE/IDOC can any one send me one or two complete scenerio and faqs on ale/idoc. this is my mail id [email protected]
Regards,
VenkatThere is no standard way to send ALE IDOC back to SAP R3 if mapping fails in middleware.
But this can be handled through BPM.I am not sure if you are from XI background or R3 background
The BPM design looks like this,
Receive( IDOCs from R3 ) -
> Block step ( Inside block Mapping-> If mapping success>.Send to Target application
If mapping Fails(System Error)>Mapping (MAP ALE IDOC with respective details)->Send IDOC to R3 system.
Hope thsi helps -
Upload CRM activity using ALE IDOC
Hi All,
I am uploading the crm activity using ale idoc in lsmw , i mapped the partner information in to segments and passing value to the fields but it is not getting values , please give what may be th problem.
Regards,
Naveenanswered
-
Mass Upload - ALE/IDOC or BAPI approch
Hi Guys,
I have to upload material master and we have options to do it by either ALE/IDOC or BAPI approach. The quantity of materials is quite huge. I tried to find some comparison about different approaches so as to know when to use what but not able to get exact information. Kindly suggest which one is usually preferred for mass upload and if possible provide some links for more references.
Thanks,
Brijesh SoniI have never seen such recomendations or benchmarks
SAP has a homepage for benchmarks: http://www.sap.com/solutions/benchmark/index.epx
the source is the same, then result is the same. all steps in LSMW are the same. you have to map the same fields in any method.
BAPI may have some more structures than IDOC or batch input. so just minutes more to assign the source structure to the target structure. .
it is a historical growth or development. It started with batch input to process SAP transactions en mass
then the IDOCs came to exchange data between 2 SAP systems.
and then we got the BAPIs to execute SAP transactions even from a non-sap system.
the result is in all three methods a created material master.
LSMW is a toolbox which gives you any of the available import methods.
there are other aspects to be considered in a migration.
What if you have errors? do you correct them yourself, or do you want the business people to fix them.
if you want business people to fix wrong data, then a batch import method may be the first option, as you can process it in foreground. It is too much complicated for a Non-IT-person to edit values in IDOCs. (even the performance may be better than a batch input) -
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. -
Hi,
For exchanging data between two systems(not between two clients of the same system) using ALE iDoc , logical systems should be maintained in both the systems?
For eg: there are two systems, system A and system B.
i have maintained the logical systems as SYSA (for system A) and SYSB ( for system B) in the system A using the transaction 'SALE'. Should this need to be maintained in system B also?
Thanks & Regards,
Soumya.Hi,
In both the systems you have to Define the Logical systems,
but in you assign only one to the client,
i.e. in system A you assign the Logical Sytem of of A to the Client in SALE
transaction the same goes for B.
and you don't need to create a distribution model for both the systems,
you can create it in one system and send it to the other system.
Regards,
Samson Rodrigues. -
Upload data from legacy system to SAP through ALE IDOC
Hello All,
I have a requirement where i need to upload the data from legacy system to SAP. So i am using ALE IDOC.
In my requirement i need to extend the Standard IDOC. I have extended the IDOC and even found the exit for the updation of the extended fields to SAP. My data would be be placed in the application server.
Can anybody tell me how to retrieve the data and update in the tables for the extended fields.
Could you please provide a sample program for retrieving data for IDOC.
ThanksHi,
You can find the sample code in the following link.
Re: calling idoc_input_creditor
Regards
Sajid -
Error in ALE-IDOC related to HR data posting in ECC 6.0
Hello People,
Upgradation done from 4.6B to ECC 6.0.
Here the data comes from the 3rd part s/w and then gets posted through a Z program which in tern calls SAP standard program " RSEINB00" and FM "IDOC_INBOUND_FROM_FILE" is used in this std program to post the data to the corresponding HR tables through IDOC postings.
ALE-IDOC Z program works fine in 4.6B but gives error in ECC 6.0.
Error in subroutine read_namtb for structure of infotype Message no. 5-109 Diagnosis An error has occurred in subroutine read_namtb for structure of infotype .
Procedure
Check the entry for infotype in table T777D (structure, IDoc segment, expanded structure) and the corresponding structures.
As per the error message it seems that some table () needs to be maintained with some values, but this was working fine with the 4.6 B with current settings.
Is this error due to version change to ECC 6.0? What extra settings need to be done with respect to IDOC so that the posting program works fine without giving the stated error. Kindly let me know.
Thanks and regards,
Gaurav Joshi.Please keep in mind ECC 6.0 is an UniCode based system.
as 4.6C was not,
did the Z-program have been tested before in the current environment?
Some special functions (keywords hints ...) are no longer supported after the upgrade.,
this was shown during the upgrade in the unicode migration tools
For sure all the own programms needs to be verfied, after an upgrade.
commonly this should be done
in the quality assurance test to avoid touble in production. -
Error while crating Sales Order using ALE-IDoc?
Hi all,
I have developed an ALE-Idoc interface to create Sales Order automatically When the user created a purchase order. It is working fine since past two months.
But now one SO is not created and the error message in Inound idoc is 'Sales Area not defined' message no V1316.
The material used in Po creation is created recently and using first time . i am expecting the problem is with in this material because the PO's created based on other materials is still creating the SO successfully.
Please help me in solving this problem?
Thanks,
Vamshi.Hi shan ,
Thanks for you reply. The sales area for customer and vendor is maintained in VOE2 and taking correctly for other materials except for the new material.
Also in Inbound IDoc which contains the error is having correct sales area in it's segment . But showing that in the error message as 'sales area & & & is not defined' here the sales area is wrong one it is dispalying.
so please help me on identifying the problem?
Thanks,
vamshi. -
How to create a sales order using PO ALE Idoc
Hi,
I have a purchase order in my ECC6 system, and output for this PO is ALE idoc.
Now I want to create a Sales order using that Idoc in the same system,
can anbody please tell the procedure
sreeramDo NOT USE BAPI_SALESORDER_CREATEFROMDATA, that FM is obsolete!
Use BAPI_SALESORDER_CREATEFROMDAT1 .
To build a reference to your contract you have to supply ORDER_HEADER_IN.
Here´s a sample:
MOVE:
gs_vbak-vbeln TO ls_bapisdhd1-refobjkey,
gs_vbak-vbeln TO ls_bapisdhd1-ref_doc,
gs_vbak-vbtyp TO ls_bapisdhd1-refdoc_cat,
gs_vbak-auart TO ls_bapisdhd1-refdoctype.
also gothrouh the links
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/snippets/abap%2b-%2bsimple%2bprogram%2bto%2bcreate%2bsales%2border%2busing%2bbapi -
How to use ale/idocs in sap crm to transfer master and transactional data
hi all,
I am working on sap crm7.0 ehp1. I want to transfer my master and transactional data from crm development system to crm quality system here through idocs. I am aware of basic ale settings and successfully transfe the ztable data through idocs. But i am not able to find any proper step by step procedure for maste and transactional data in sap crm. Also sap ecc tcode NACE is not available here.
pls help..
regards,
kavita chaudharyKavita,
In CRM, Exchange Interface (XIF) ALE/IDOC is available to transfer master and transaction data. You can go through the following link for set up.
Basic Data exchange set up for ALE IDocs - Wiki - SCN Wiki
You can extend the standard XIF IDOCs using Transaction BDFg as well.
Thanks,
Ravi
Maybe you are looking for
-
Voice memos on iPhone automatically go to iTunes
Every time I record a voice memo on my iPhone, it shows up in my music library in iTunes. SO I delete it. But is there a way to prevent it from showing up there in the first place?
-
Hard drive will not mount - SMART STATUS "not supported"
I was in the process of "sanitizing" an iMac G5 last night by erasing the data with Disk Utility and the hard drive is not not recognized...and some alarming noises periodically come from the drive. Is there something else I should try to determine i
-
How to include jar files in jdk1.7
Please can anybody tell me that how can i include jar files in jdk1.7
-
Linking/Calling to files in Numbers
Hello, I am trying to reference cells from different numbers files through the iPad and having some difficulty. For example, if I enter a name/phone number/address in some cells in spreadsheet A, I'd like certain cells in spreadsheet B to fill based
-
Forms, RAISE Application Error
Hi, How to get the message in forms (front-end) from Oracle DB procedures/triggers.The message is being used in a RAISE APPLICATION_ERROR built-in in the DB procedure. Is there any other ways to communicate the messages from back-end to front-end. Th