Debugging customized function module when Idoc is triggered via ALE

Former Member — Fri, 18 Jan 2008 23:03:40 GMT

Hi,

Whenever we save the billing document, an outbound idoc is triggered via ALE. The logic for the data to be included in the idoc is written in a customized function module.

However we are making some changes and would like to include some more data in the idoc. But we find that when we put a breakpoint in the function module, on saving the billing document, the flow does not stop at the break point. We are 100% sure that the code in the function module gets executed based on the data in the idoc.

How do we get into debug mode and break the flow in the function module so that we can debug in the function module?

Any help would be greatly appreciated.

Thanks in advance,

Mick

Re: Debugging customized function module when Idoc is triggered via ALE

Former Member — Sat, 19 Jan 2008 04:59:23 GMT

Hi Mick, this might be of some help 4 u.

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 - Create Model View

Tcode BD82 - Generate partner Profiles & Create Ports

Tcode BD64 - Distribute the Model view

This is Receiving system Settings

Receiving System(Inbound ALE )

Tcode SALE - for

a) Define Logical System

b) Assign Client to Logical System

Tcode SM59-RFC Destination

Tcode BD64 - Check for Model view whether it has distributed or not

Tcode BD82 -- Generate partner Profiles & Create Ports

Tcode BD11 Getting Material Data

Tcode WE05 - Idoc List for inbound status codes

Message Type MATMAS

Tcode BD10 - Send Material Data

Tcode WE05 - Idoc List for watching any Errors

1)a Goto Tcode SALE

Click on Sending & Receiving Systems-->Select Logical Systems

Here Define Logical Systems---> Click on Execute Button

go for new entries

1) System Name : ERP000

Description : Sending System

2) System Name : ERP800

Description : Receiving System

press Enter & Save

it will ask Request

if you want new request create new Request orpress continue for transfering the objects

B) goto Tcode SALE

Select Assign Client to Logical Systems-->Execute

000--> Double click on this

Give the following Information

Client : ERP 000

City :

Logical System

Currency

Client role

Save this Data

Step 2) For RFC Creation

Goto Tcode SM59-->Select R/3 Connects

Click on Create Button

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

give the information for required fields

RFC Destination : ERP800

Connection type: 3

Description

Target Host : ERP000

System No:000

lan : EN

Client : 800

User : Login User Name

Password:

save this & Test it & RemortLogin

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

cheers,

Hema.

Re: Debugging customized function module when Idoc is triggered via ALE

Former Member — Sat, 19 Jan 2008 15:27:06 GMT

Thanks.

However how do I go into debug mode and debug in the customized function module after saving the billing document?

Regards,

Mick

Re: Debugging customized function module when Idoc is triggered via ALE

Former Member — Sat, 19 Jan 2008 15:44:30 GMT

Ok... follow these steps to enter into debug mode...

1. Set break-point in function module.

2. Before saving i.e. before clicking on Save button enter /H in command line and press enter.

3. then click on save button.

4. then you'll enter in debug mode (NOT into your funtion module)

5.Then in menu select

settings----> Update debugging

you can see message 'Update debugging switched on'

6. then press F8.

7. this time control will stop at break-point in your FM.

Basically update debugging is to call background programs like print programs while generating PO output etc.

In normal debug mode you can't debug background processing.

in such cases you've to follow above procedure.

Re: Debugging customized function module when Idoc is triggered via ALE

Former Member — Sat, 19 Jan 2008 16:24:21 GMT

Thanks Perez.

This solved the problem.

Points awarded.

topic Debugging customized function module when Idoc is triggered via ALE in Application Development and Automation Discussions

Debugging customized function module when Idoc is triggered via ALE

Re: Debugging customized function module when Idoc is triggered via ALE

Re: Debugging customized function module when Idoc is triggered via ALE

Re: Debugging customized function module when Idoc is triggered via ALE

Re: Debugging customized function module when Idoc is triggered via ALE