ALE - Trace triggering program

Dear all,
I got Message type and Basic type. I need to trace the Message type is being used/triggered by which method, either stand-alone customized program, or transaction doc's output type.
Could you please advice?
Thanks in advance.

Similar Messages

How to Debug / Trace a Program

Dear Sir,
We need to make certain enhacement in MIGO Program . Before going for enhancement , we need to understand that during the execution of this Tcode what are the screens / Function Modules etc being called .
We tried to put a Break-point in the Prgram SAPLMIGO , but to trace the program with this approach it is very difficult .
We request you to kindly guide us as what is the best procedure to be followed to have the complete trace of a Program execution.
Pl help us .
With Thanks and Rgds
Sonia

Hi,
use /h is another dubugging methos run the total program in debugging mode and check total program.
and check below link for sql trace
/people/siegfried.boes/blog/2007/09/05/the-sql-trace-st05-150-quick-and-easy
Regards,
Madhu

How to make a trace to program ?

Hi
Does somebody can tell me how can i make a trace to program in order to find in wich code point the process is getting 'stand-by' (does not finish) ; that is, in wich DB access, LOOP, etc. the program is making the work wich takes a lot of time.
I need to discover where are the performance problems and how much the program access the DB with SELECTS.
Regards
Frank

Hi,
make use of the transaction code ST05 for the trace of database selects, Just press the Trace on button and run your program, and inthe ST05, press the Trace off button and look at the list, you will understand.
Even you can use the transaction ST04 -> Database performance analyzer
ST03 -->Workload on the System
Regards
Sudheer

Email triggering program in version ECC6

Hello experts,
In version 4.6c, program RSCONN01 will trigger all email requests waiting in the queue to be sent out. After upgrading to ECC6, the same email requests now have status of 'Still no entry in queue' and never be triggered by the program. SAP has recommended to put a COMMIT WORK as a pamameter to the function module or as an ABAP statement in the calling program to send emails. This can lead to program errors if COMMIT WORK is not put at the right place.
Did SAP create a replacement program that can be used to trigger those email requests with such status? Do you have any other ideas or solutions? Please help!
Best regards,
Chuong Le

in ST05 there is an option for RFC trace. Not sure how much detail that will give you but you can try.
It is possible that your userid doesn't have an RFC call authorization in R/3. Do a SU53 immediately after running the program.
Also, replace the FM with any other FM that you know for sure runs (eg some BAPI FM) and run it - either in SE37 in R/3 with RFC destination for BW, or, from your code itself and see if that works (you can check return code).

Enable ABAP trace for programs running in BI process chains

Hi
Can anyone please indicate how can we enable a ABAP trace for a long running program, that runs through Process chains of SAP BI.

well i´m not a 100% sure, but this task has not so much workload that you cant give it a shot

Trace a program?

Hello Gurus,
i´ve got a problem.
I need to trace a programm. But i need not an SQL trace.
I need to know what steps was done in the program. Which functions, were called, which forms and so on.
Is it possible?

From se30 u can display the call list of a prog. To do this u need to create a variant in the se30 screen...
Give a name of the variant and press create button.
In the next screen give description..and then goto tab Duration/Type,
and under Aggregation choose None check box and save the variant.
Now Run a trace for the transaction/prog with this variant...after completion press analysis button and then follow the menu path Goto->Call hierarchy->Include display. U will get a list where u can search for ur FM call.
Also try menu paths:
Goto->Who calls whom
Goto->Group hit list
Regards,
Joy.

Error while triggering program through output type while saving invoice

Hi,
I have a scenario where in my Z program needs to be triggered when saving a invoice.
For that we have attached out Z program to output type which gets picked while saving invoice.
In the Z program we have written the entire code in Form Entry subroutine.
In the Z program we have called a FM "SD_SALESDOCUMENT_CREATE", to create a sales order.
After sales order is created we have used a Commit statement.
If I run the Z program individually, Salesorder gets created perfectly.
How ever as per scenario when trying to save the invoice, output type gets picked. But program doesn't get called.
and when I go to the saved the invoice I get the following error immediately:
"Error document - Update was terminated"
I have found that the problem is with COMMIT statement through transaction SM13.
Can anybody help me with this. I cannot save the sales order without COMMIT, so I have to use it.
Thanks in Advance,
Rohan.

Hi Rohan,
I have worked on almost similar kind of requirement as you.
"Error document - Update was terminated" is because saving of invoice is done in u201CUpdate Tasku201D. Again in that work process, FM also calls for update task, which is not allowed and give short dump.
Here are two different approaches to cope up in this scenario.
1.Call FM in NEW TASK.
Calling Function module in new task will assign new work process and will use different update task.
Use:
CALL FUNCTION 'SD_SALESDOCUMENT_CREATE' STARTING NEW TASK 'task'
This will not give update termination error.
Call of FM in this way will work, but as this will be asynchronies call you will be not able to get status/message out of the FM call result.
If capturing return message is mandatory, use below approach
2, Process output type via Job
Set output type, dispatch time u201CSend with periodically scheduled jobu201D in u201CDefault valueu201D tab.
Run batch job for program u201CRSNAST00u201D with appropriate variant.
Please let me know if you need any further details.
Best Regards,
Nisarg

Help needed to trace a program ...

Hi,
I am trying to reach the program which actually generates the PO from ME21N/ME22N. Could you please help me trace or let me know the program name ??
Once PO is created and if I have the print option set in the "Messages", the PO is printed to the printer. I want to trace after the point, the PO is saved in the table. i.e. from the time PO output is assembled for printing. also i want to know if its in .txt format ??
thanks

Hi Rad Sha,
your program should be run in background, if you want to look that, you have to activate the background debuging.
To do that, start a ME22N/ME21N, put /hs (in the field for the transaction). Save your PO, that will go in debuging. Use the button Setting, select the background debugging and press save.
After this you could press the key F8.
You will have a new window that will appear, in debug mode. This window correspond of the background.
Rgd
Frédéric

How to trace a program in TOAD

Hi,
Can any person tell me how to trace a tabel be called by which program/programs in TOAD? Or how to realize it ?
Thanks a lot
LC

Hi,
If you are having the access to the dba module funtion in TOAD, Then you can copy the Synch Script and use that script in Sql editor of Toad or even Sql*plus and execute that. You will get the desired result. but If you dont have access to DBA module , that script only be read only or you can say View only.
Regards,
Navneet

How to trace deleted program.....who has deleted

Hi all,
I was using one program ( se38). anyone has deleted that program from development server,
i want to see the details who has deleted and when.is it possible to find out these details.
Thanks in advance.
Sujeet

Hi Sujeeth,
Goto table E071 with OBJ_NAME EQ programm name
Search record with OBJFUNC EQ 'D'
Goto E070 with TRKORR EQ E071-TRKORR
Look at E070-AS4USER (user name, who deleted programm)
you can see a log in this table also.
D010SINF
Thanks & regards,
Dileep .C

ALE Configuration HCM - Program read table idoc_structure error

Hello SCN community,
I have small problem with ALE Configuration of HRMD_A message type. I created extension named 'ZRMD_A06'.
When I'm trying to run t-code: bd21 (report RBDMIDOC)
I'm getting following error message:
At the beginning I thought there is problem with segment structure of Z1P2006 of extension 'ZRMD_A06'
I compared segment Z1P2006 with structure 'P2006' in se11 - and it is the same.
Next I checked the bd21 transaction in debug mode.
I figured out that there is error in FM 'RH_MASTER_IDOC_DISTRIBUTE_HRMD' in include 'LRHALF10'.
Could you please help me?

Hello,
Thank you all for your help.
I'm writing this post to provide solution for others like me.
To solve this problem you need to apply this sap note:
HR-CA-ALE: Segment Z1Pnnnn prevents distribution
for me:
As of Release 4.6: In the customer enhancement RHALE001, fill the function exit EXIT_SAPLRHA0_004 with the line
F_idoc_control-cimtyp = 'ZRMD_AXX'.
steps:
1. Go to SE37
2. Enter EXIT_SAPLRHA0_004
3. Double click on INCLUDE ZXHALU08 . (in my case)
4. Add to the code this line: F_idoc_control-cimtyp = 'ZRMD_A06'. (ZRMD_A06 - because I called so my custom extension)
5. and have a nice day because you solved this problem!

Triggering program form(subroutine) from MIGO using output types gives lock issue with Bapi_sag_change

Hi,
On creating the GR from MIGO tcode, based on the quantity check i am updating the field ELIKZ using BAPI_SAG_CHANGE.
And updation logic is written in a zprogram using with in FORM XXXXX...ENDFORM XXXXX. ( FORM XXXXX is configured in the output type ).
So the problem i am facing is on creation of the first GR with scheduling agreement number GR is posted successfully and under the output tab the i can see the green icon.
But on creation of the second GR with same scheduling agreement its showing red icon. The following is the error message " User locked the scheduling agreement ...."
I even tried using dequeue fm and transaction commit, but it didnt work. Please let me know how to over come the lock issue.
Thanks & regards,
Manojkumar K

Solved it myself....
Regards,
Manoj

Program execution trace

Hi,
does exist any tool how to trace whole path a program was going through ?
Thank you.
Marian,

Hi Marian,
The best way to trace a program would be by looking at the call stack and the overview details in the debugging mode.If you want to analyse the performance of selects in the program then use the transaction ST05.If you are still not satisfied then run through the entire execution process by entering into the debugging mode.
The answers that you have recieved so far should be sufficient to close the thread.Please reward some points and kindly close the thread.
Cheers
Nishanth

DISTRIBUTION OF ALE IDOC

HI GURUS
i want detailed distributiuon on ale idoc processing along with transaction codes step by step
plzzz its urgent
baskar

ALE
Outbound:
Step 1. Application document is created when transaction is saved.
2. Message control is invoked.
3. Messages are processed by system.
4. Messages are Edited (if desired).
5. Output (ALE / EDI) is checked
6. Validate against Message control record from Partner Profile
7. Application Document is saved.
8. Entry NAST table is created for every selected output program
along with Medium & Timing.
9. Check for Process Immediately .
If (yes)
Determine Processing Program from TNAPR Table.
ELSE
Execute RSNASTED Program.
10. Read Partner Profile to determine Process Code.
11. Process Code points to the Function Module & Invoked.
12. IDoc is generated.
13. Check for ALE Request.
if (Yes)
Perform Filters, Conversions, Version Changes etc.
Else.
IDoc is stored in DATABASE.
INBOUND:
Step 1. EDI Subsystem creates an IDoc file from EDI Messages
2. Subsystem calls Functional Module EDI_DATA_INCOMING from startRFC program.
3. Data in Control Record is validate against the Partner Profile.
4. IDoc is generated in Database and syntax check is carried out.
5. IDoc file is deleted once file read.
6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow.
7. Check for Process Immediately.
If NO
Execute RBDAPP01 Program
Else
Read Process Code from Partner Profile
Process Code Points to Function Module
Application Document Posted.
further help:
check url
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/ale/configuration.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapdevelopment.co.uk/training
And also u can get lots of inof from the below link.
http://www.sapgenie.com/ale/why_ale.htm
**************************************************8
http://service.sap.com/ale
ABOUT ALE AND IDOC
Go through this hope u can understand .
ALE/IDOC
IDOC Programming
There are two processes in IDOC processing one is INBOUND PROCESS( IDOC coming to the system and its handling at various stages) and the other is OUTBOUND PROCESS( IDOC is send to other system . Separate ABAP programs are written for these 2 processes and different configuration settings are required for each one .Depending upon the trigeering mechanism different programming approaches are used.OUTBOUND PROGRAMS handle the IDOC creation and INBOUND PROGRAMS handle the inbound IDOC and the data trasfer from the IDOC to the database tables.
NEED FOR ABAP PROGRAMMING arises if
1)New IDOC was created
Depending upon the triggering mechanism i.e change pointer,message control
etc the programming technique changes and the type of process.
2)Existing IDOC was extended
User Exits are used to populate data in new segments added and to read them
back.
3)To enhance an exsiting process.
User Exits are used .
Basic structure of an OUTBOUND PROGRAM
The basic structure of all outbound programs is same. The CONTROL
record which is of TYPE EDIDC has to be filled. It contains important fields like
IDOCTP IDOC type
MESTYP Message Type
RCVPRN Recieving Partner (Destination)
RCVPRT Partner Type (it is LS i.e Logical System)
The DATA RECORD internal table which is of TYPE EDIDD has to be filled
in the same order as there are segments in the IDOC definition.
It has 2 important fields which are to be filled ,these are
SEGNAM Name of the segment
SEGDATA Data in the segment and can be upto 1000 bytes.This field
is corresponds to each data segment in the IDOC.
e.g.
DATA INT_EDIDD LIKE EDIDD OCCURS 0 WITH HEADER LINE.
DATA W_SEGDATA LIKE zsegment "custom segment zsegment
INT_EDIDD-SEGNAM = 'ZSEGMENT'
W_SEGDATA-field1 = value "taken from some table
W_SEGDATA-field2 = value "taken from some table
INT_EDIDD-SEGDATA = W_SEGDATA
APPEND INT_EDIDD
This will fill the data record corresponding to the segment ZSEGMENT . For all
segments the sam steps will be repeated until all the data corresponding to all the
segments in the idoc is filled in the internal table of type EDIDD.
There is only one control record and can be multile data records in the idoc
structure.
Which data is to be extracted from the tables to be filled in EDIDD type internal table is determined in standalone programs from the objects which are specified in the selection screen and from the object key passed to the function module in case of message control and is taken from BDCP table in case of change pointers using function modules "CHANGE_POINTERS_READ"
In case of stand alone programs and function modules based on change pointers method the function module "MASTER_IDOC_DISTRIBUTE" is used to send the IDOC to ALE layer for distribution ,in case of message control it is handled automatically by the RSNASTED program invoked by the message control.
OUTBOUND PROCESS AND OUTBOUND PROGRAM.
Outbound programs are used in outbound process to genearte IDOCs . There
purpose is to extract the data from the tables and to fill the IDOC data records
and the control record in the IDOC and pass ito the ALE layer for distribution to the recieving system .
Depending upon the triggering mechanism (how and when the outbound program will be started different techniques and interface is used for outbound program.
1)Message control
Application like PO(purchase order) creation use this technique , where the output type is linked to the application(Message control is a configurable cross application component which can be set in IMG .Such programs are created in the form of function modules and linked to the output type which is linked to the apllication.These have predefined interfaces.
In outbound programs(function module) that use message control the key of the
application document is passed to the function module whcig will read the data from the table depending upon the key passed(NAST structure) and fill the IDOC segemnts with the application data.The control record is also passed to the function module but is not fully filled, the rmaining fields are filled and the control is passed back to the calling program which is RSNASTED and is invoked by the
message control to process ALE and EDI output types and this program on recieving the IDOC data will create the physical IDOC in the system.
The parameteers passed to the function module are
IMPORTING PARAMETERS
OBJECT LIKE NAST
It contains documents key.
CONTROL_RECORD_IN LIKE EDIDC
It contains the partailly filled control record
EXPORETING PARAMETER
OBJECT_TYPE
CONTROL_RECORD_OUT LIKE EDIDC
TABLES
INT_EDID LIKE EDIDD
The internal table used to fill the data records in the same order as they exists in the IDOC.
The important parameters that should be filled in the custom function module are
CONTROL_RECORD_OUT and INT_EDIDD .The OBJK field of the structue NAST contains the key of the apllication document.
2)Stand alone programs
Generally used for Master Data transfer and as such depending upon the requirement can have different interfaces.The programs have a selection screen which has select options to select the objects, and parameters for specifying the recipient Logical System and the Message Type.
Data is selected based on the specified objects from the tables . and control record of type EDIDC is created and filled with important values like DIRECTION ,IDOCTP,RCVPRT,RCVPRN and MESTYP .
Data is filled in an internal table of TYPE EDIDD according to segment definitions
and in same order and the function module MASTER_IDOC_DISTRIBUTE is called passing the control record and the internal table containg IDOC data and importing an internal table consisting of control records for each communication IDOCS created.
3)Change pointer
Change Pointer table is read and checked if changes were made to important fields , if so the outbound program will be triggered automatically , these have predefined interfaces
ALE/IDOC Transaction
SALE Area Menu for ALE configurations.It includes transactions for
Logical System definition and linking it to a client, Transactions for
RFC Destination and Port Definition Etc.
SM59 RFC Destination
Here we specify the login settings for the destination including
the I.P address or Application Server name and the User name and
password.The information entered here is used to run Remote Function
Calls(RFC ) on the destination server .We can create number of types
of RFC Destinations but 3 types are important .
R/3 (R/3 to R/3), LS(logical system) and TCP/IP.
The name of the RFC destination should be same as that of Logical
System as it helps in creation of automatic partner profiles.
WE21 Port Definition.
There are 6 types of ports but only 2 types File and Transactional RFC
types of ports are important.
We have to specify the RFC Destination before a port can be created.
WE57 This is used to assign the Inbound function module to the Message Type
and to the IDOC Type.
WE42 This is used to define the process Code for Inbound Processing.
BD95 Define Filter object type .We can specify the field and the table it belongs
to as a filter object .
BD59 Assignment of Filter object type to the Message Type .Here we create the
link between Filter object and the segment and the message type and the
segment Field.
BD50 Set message Type to reducible.
BD65 Define Mandatory Fields.
BD64 Distribution Model . Also known as Customer Distribution Model Used to
define all the messages that will be exchanged between remote systems
and the name of thes logical systems. Any filters can also be specified.
The model once created has to be distributed on every system which will
be communicating ,It can be maintained on only One system.
BD21 Creating IDOcs from change pointers.
This can be used to create IDOCs from change pointers for a particular
message LIKE MATMAS.
BD22 This can be used to delete change pointers.
BD87 Status Monitor. Idocs can be selected base on number of criteria and there
processing status can be seen in detail.
BD10 Material Master Data Distribution .
Based on Message MATMAS.
BD12 Customer Master Data Distribution .
Based on Message CREMAS.
BD14 Vendor Master Data Distribution
Based on Message DEBMAS .
BDFG Generate ALE Interface for BAPI.
Here we specify the Business Object and the BAPI Function module for
which the interface has to be created.
WE31 Segment Editor.
This is used to create segments. We create the segment type and
segment definition is automatically created by editor e.g. Z1DUMMY is
segment type and Z2DUMMY is the segment definition .We specify the
fields and the data elements these cp\orresponds to create segments.
WE30 IDOC Editor
It is used to create a new IDOC Type or IDOC Extension .We specify the
segments that will be addd to the IDOC type.
WE02/05 IDOC List.
Various selct options and parameters are provided to select IDOCs
depending on the date, direction , mesage type etc.
WE20 Partner Profile
Here we create partner profile for each and every partner from / to which
the messages will be exchanged.There are 6 types of PF generally only
profiles of type LS(Logical System) ,KU(Customer) ,LI(Vendor) is used.
We specify the partner number and partner type and the agent and
the agent type responsible for handling of errors .
For every message send to the partner we have a outbound record and for
evry message coming from the partner we have the inbound record .
We specify the message in the otbound/inbound records ,double
clicking will take us to the detailed screen where the IDOC Type ,Port
and whether the IDCO will be immediatelt processed or collected are
mentioned.
Steps relate to idoc
Creation of IDoc
To Create Idoc we need to follow these steps:
1)Create Segment ( WE31)
2)Create Idoc Type ( WE30)
3)Create Message Type ( WE81)
4)Assign Idoc Type to Message Type ( WE82)
Creating a Segment
a)Go to transaction code WE31
b)Enter the name for your segment type and click on the Create icon
c)Type the short text
d)Enter the variable names and data elements
e)Save it and go back
f)Go to Edit -> Set Release
g)Follow steps to create more number of segments
Create IDOC Type
a)Go to transaction code WE30
b)Enter the Object Name, select Basic type and click Create icon
c)Select the create new option and enter a description for your basic IDOC type and press enter
d)Select the IDOC Name and click Create icon
e)The system prompts us to enter a segment type and its attributes
f)Choose the appropriate values and press Enter
g)The system transfers the name of the segment type to the IDOC editor.
h)Follow these steps to add more number of segments to Parent or as Parent-child relation
i)Save it and go back
j)Go to Edit -> Set release
Create Message Type
a)Go to transaction code WE81
b)Change the details from Display mode to Change mode
c)After selection, the system will give this message The table is cross-client (see d)Help for further info). Press Enter
e)Click New Entries to create new Message Type
f)Fill details
g)Save it and go back
Assign Message Type to IDoc Type
a)Go to transaction code WE82
b)Change the details from Display mode to Change mode
c)After selection, the system will give this message The table is cross-client (see d)Help for further info). Press Enter.
e)Click New Entries to create new Message Type.
f)Fill details
g)Save it and go back
Look at these links
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
ALE/ IDOC/ XML
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://www.thespot4sap.com/Articles/SAP_XML_Business_Integration.asp
http://help.sap.com/saphelp_srm30/helpdata/en/72/0fe1385bed2815e10000000a114084/content.htm
Just follow the procedure
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
STEP 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
-System Name : ERP000
-Description : Sending System
-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
STEP 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
STEP 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)
STEP 5) Goto Tcode BD64
select the modelview
goto >edit>modelview-->distribute
press ok & Press enter
STEP 6) goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
STEP 7)goto Tcode : BD11 for Material Receiving
Material : 100-300
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
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
vasu

User Exit Program works Differently

I'm trying to sync user info from HCM system to a destination system. There is a limitation in SAP HCM system, which allows only full load and not incrememental load or sync up based on events(New Joinee, Position change, Employee Exit) to happen from source to destination. So, I thought User exit could fix this issue.
When a person inserts or changes or changes the status of an employee to quit through PA30 and saves it, the user exit program should pass the personnel number (numbers) of the user(s) as input to the report RPLDAP_EXTRACT_IDM.
I am trying to trigger a report(RPLDAP_EXTRACT_IDM) which exports the data from HCM to a destination system(IDM) with the help of a user exit program. Using PA30 when I change the user info and when I save it, through User exit program I'm passing the personnel number of the user(whose data has been changed) as an input to the report, which inturn will replicate the change to the destination.
Problem:
User Exit works differently here. After configuring User exit for this tcode(PA30), once I change a user's info and click save, without saving the data, it triggers the User exit program. Usaully while chanign user info, when I click 'SAVE', i get a message 'Recod changed', but now after sonfiguring User Exit program, since the program runs immediately as soon as i click SAVE, I see the following message' Successfully exported Data to the destination' . And the change that i make is not reflected.
Shouldn't the User Exit program be triggerred after the data is saved?
Is there a way where I can trigger the User Exit Program after saving the record.

Not an ABAP expert, but I remember hearing something about PAI and PBO modules and separate user exit includes depending on where you are executing it. Is it worth investigating on these lines?
Also is it worthwhile configuring Change Pointers to capture whether a change has been made instead of coding user exits in PA30. You could code uxerexits in the ALE data transfer program to analyse the data based on change pointers and transfer data pertaining to New Joinees etc.
Again I am not ALE epxert, I am just giving my views For what they are worth. For better results perhaps you should post in ABAP forum.

ALE - Trace triggering program

Similar Messages

Maybe you are looking for