Debugging Append Structure Function Module

Hi,
If we enhnace the extract structure with append structure and write a function module to fill the data for append structure then how do we debug this function module. When this function module will be executed?
Thanks.

Whenever you enhance an extraction structure, the right place to include and execute the code for populating the appended fields is in CMOD.
In there, you can create a "CASE" entry for your datasource and put the code for it. If you want to call a function module in here, you can do so.
This code will be executed after the "main" fields in the datasource are filled, right before they're sent to BW.
You can easily put a "breakpoint" in that code, execute a test extraction using RSA3 and debug your code and logic.
Regards,
Luis

Similar Messages

Vendor-Customer balances in group currency-table/structure/function module?

Hi All,
Which table/structure/function module can be used to get balances for vendors and customers in group currency? We just wnat to extract balances in group currency so FBL1N and FBL5N are not options. Is there any SAP report which can provide these balances for both vendors and customers?
Thanks and regards,
Pinky

Hi Pinky,
I came across one report S_ALR_87012079 - Transaction Figures: Account Balance, Program RFSRRCUA, which extracts Account Balances of Vendor. Once the report is executed, you can do Currency Translation from one currency to different currencies. In the output screen, in the Top Menu, select 'Settings -> Currency' and you can convert to another currency. I am not sure, if this helps you. If this helps, kindly update your comments here.
Thank you.
Suresh Jayanthi.

V Urgent : Debugging an RFC function Module in another R/3 system

Hi All
I have a function module in a R/3 system ( say WB1 ) and i am calling it from another R/3 system (say WD1) . Both have their RFC destinations set up as trusted system mutually . However when i try to debug that FM while in WD1 ( which basically exists only in WB1) i am not able to get inside that FM . Are there some settings that we need to do to allow us to debug function module in another R/3 system ? .
Yes ,we cant do this debugging if RFC function module is in a non SAP system but am sure it can be done atleast for R/3 to R/3 .
Any pointers to this as to what setting needs to done ?
Does some system parameter needs to be set in RSPARAM program for debugging RFC?
Please help
Regards
Shovit

Hi
Can you do a remote logon through the SM59 connection (the trusted one)?
If so, then the only thing preventing you would be debugging autorization.
If not, make sure you have trusted system logon auth (not part of SAP_ALL!).
Cheers
Dom

How to debug a RFC function module remotely from another R/3 system?

Hi experts,
   I have RFC function module in one R/3 system. I am calling this from another R/3 system that is cross apps (Xapps).
   This function module is Synchronous.
Is it possible to debug this function module from cross apps?
Can somebody give me the steps?
Thanks & Regards
Gopal

Hi Shree,
   Can you explain it bit more?
   Do I have to call the function module with "IN BACKGROUND TASK"?
   Or is it that I have to just put external breakpoint in the function module?
   Please help
Thanks
Gopa

How to debug a remote function module in calling system? Help!

Hi Experts,
   I have a ABAP report (in System A) from where I am calling a remote function module which exists in a different system B.
ABAP Program(System A)<----calls--
RFC(System B)
Can I debug the RFC funnction module in system A using ABAP debugger? In other words if i put a breakpoint on the "call function" statement then in debug mode I want to see that the control is going to system B and I should be able to process the FM code line by line. Is this possible?
Is there any special transaction or settings?
Is there any alternative?
Please help
Thanks
Gopal

hello,
Try this method.
first check whether RFC connection is working b/w 2 systems.
if connection is working, then do like this.
In System B , put endless loop in FM before some main select statement.
like
DATA : v_a TYPE c VALUE space
DO .
   IF v_a = 'X'.
     EXIT.
   ENDIF.
ENDDO.
the above code will be endleep loop.
In system A, when cursor goes to CALL FUNCTION DESTINATION 'XXXXX'.
u shud be logged in system B. the moment control comes to system B.goto tcode SM50 . check ur username . choose that particular checkbox then in menu bar --> program/session --> Program --> Debugging.
i hope it will help u.
try & let us know.
Thanks,
Manjunath MS

Debugging an RFC function module

Hi,
I am making an RFC call from Server(RDH) to server(RDI).The problem i am facing is that i am not being able to return debug the function module nor is this returning any values. The function module has been transported to the RDH and Rdi servers.
One reason could be that the destination returned by teh function module us wrong but the people concerned insist that it is correct. I am at a loggerheads.
Thanks
CALL FUNCTION '/GLB/RGT_RFC_DESTINATION'
    EXPORTING
      destsysttype                 = l_c_o "commercial box
    IMPORTING
      rfcdest                      = v_comdest
    EXCEPTIONS
      no_destination_found         = 1
      own_logical_system_not_found = 2
      OTHERS                       = 3.
IF sy-subrc <> 0.
    MESSAGE i004."Destination not maintained
    LEAVE LIST-PROCESSING.
ENDIF.
CALL FUNCTION '/AOA/FAO_RFC_BILL_INFO'
    DESTINATION v_comdest
    EXPORTING
      im_i_bsid10           = i_bsid10
    IMPORTING
      ex_i_billing          = i_billing
      ex_i_vbfa             = i_vbfa
      ex_i_vbpa             = i_vbpa
    EXCEPTIONS
      communication_failure = 1
      system_failure        = 2
      OTHERS                = 3.

Did you check in SM59 whether the said RFC destination is maintained and if it is able to connect to the destination.

Debugging of ABAP Function Module through ISA Application CRM B2C 4.0

Hi Experts
There is way to Debug ABAP FM through ISA CRM b2c Application by Modifying some XML Files as per Extn Guide.
I tried modifying the <APPLICATION_HOME>\WEB-INF\xcm\customer\modification\modification-config.xml After that I restarted the Application .
But it is not Breaking for Both Statefull & Stateless FM after running my Application.
With Some Help i found that if we try it on Remote System ( Means SAP GUI has to in Same System where CRM is Installed ???????????). but that is not Advisable Right !!!.
So if i am able to Debug ABAP Function Module through ISA Application from any Other remote System.
I think it will be very Useful.
Thanks & Regards
Ravi Sah

Ravi
It is other way around !!!
You should have SAP GUI installed on the machine in which you start(access) your B2C Application. This enables for ABAP Debugging.
We have tried this and works fine for us !!!
Thanks
Jack
<b>Allot points if my post helps !!!</b>

How to debug outbound Idoc function module for invoice

I have to debug the outbound IDOC function module and UserExit for invoice message type INVOIC, process code SD09, function module is IDOC_OUTPUT_INVOIC and user exit for the function module LVEDF001.
I tried putting the break point in function module IDOC_OUTPUT_INVOIC and recreate the IDOC using WE19 but it creates the idoc but does not stop at the break point. I have also tried generation of idoc through VF02. It again creates the idoc but does not stop at the function module.
Please let me know if I am missing any thing and not doing it right.
Appreciate your help.
Rohit

Hi Ali,
I faced the same problem. Thing is the break point is not getting triggered when i ran tha IDOC through WE19.
What i have done is i created a project for my exit in CMOD and kept some junk code in the exit and executed it through BD21. Then the Break point got triggered. See if it works.
Regards,
Uday S.

MRBR Report- Price and qty variance tables/structure/Function module

Hi
I am in the process of developing a customised report similar to MRBR report. I am not very clear on the logic used for "Difference Qty" and "Difference Value".
MRBR is taking values from strucrure ARSEG. Is anybody aware if there are any tables from where we can get this information ? Are there any Function modules that SAP uses to arrive at this difference.
I am aware that we canget the information from EKBE table and calculate our seleves. At times the values do not match and the logic do not seem to be straight forward.
Has someone worked around this area ?
Thanks for your time in advance.
Dasaradh

Hi,
RBKP_BLOCKED is one important table from where this program gets the blocked invoices.
Hope this helps.

Debugging RFC function module from ECC to CRM

Hi All,
My requirement is to debug an RFC function module present in CRM(7.0) system from ECC(6.0) system. A report program in ECC will call CRM custom FM. I found many posts in SDN with the same issue and tried to implement suggestions provided there. But I couldn't succeed. The approach I followed is:
I logged in to ECC report program and kept an external breakpoint just before the function module call.
I logged in to CRM system, opened the function module and kept an external breakpoint there.
In both the systems I provided the dialogue userid( id through which I log in to SAPGUI) in the system->settings->debugging option.
In CRM I activated the external break point in transaction SRDEBUG.
Now when I execute the report program in ECC, control stops at the breakpoint. If I press F5 at the function call, control is not going to the external break point set in the CRM FM. I am getting output of FM directly.
I tried with different settings like turning on the check box for IP matching and session breakpoint active immediate, switching to classic debugger etc. I also tried to provide the RFC user id instead of dialogue user but system throws exception saying only dialogue userids are allowed. I found that by inserting an infinite loop statement, control goes inside the RFC CRM FM but I prefer not to change the code.
Please let me know if I missed anything.
Thanks and Regards,
Naren

Hi,
Debug RFC calls
When an RFC function module is called it is usually not possible to debug the call, using the below techniques we can achieve the same. For this example we are calling an RFC enabled FM in ECC system from CRM system.
Scenario 1: Calling a custom RFC FM
STEP 1: Add an infinite loop in the remote custom Function Module (adding a u201CDO. ENDDO.u201D statement at the start of the FM would be enough).
STEP 2: Execute your program in the CRM system. The execution stops at the RFC call, because of the infinite loop.
STEP 3: Now login to the ECC system and go to transaction SM51 select the process which is executing the RFC and navigate to the menu: u201CProgram/Session->Program->Debuggingu201D this triggers the debugger session in a separate window.
Scenario 2: Calling a Standard RFC FM
When we are debugging a standard program we cannot add the infinite loop, hence we cannot go to SM51 and debug the work process. The RFC destination for the ECC system has a User specified, the RFC function module gets executed using this users credentials. Usually the basis team set up the RFC user as non Dialog user, this does not allow debugging. Contact your Basis team and get this changed to a dialog user enabling you to debug RFC function calls via the normal debugger.
Note: User name configured in the RFC destination (transaction SM59)
Note: User type for the RFC User (transaction SU01D)
Hope this will be helpful..

How to debug mapping function module during delta extraction?

Hi experts,
Somehow our delta is not working properly, and i would like to debug our mapping function module. How can i debug it during a delta extraction?
Some info:
Our source system is CRM and our extractor is extracting one order document (contracts in this case). I know that when we modify a contract, a bdoc is generated and then passed throught the mapping function then the extracted data to the delta queue. I just need to debug when the bdoc is being mapped to see what's wrong with the extracted data.
Thanks in advance,
Van

Hi,
Since you are using a Function Module for the Extraction. Edit the Function Module and give "BREAK-POINT" before the loop command. Check and activate the Function Module.
Now Extract the datasource using RSA3. Now you can debug it. After checking remove the "BREAK-POINT" from the function module. Also Check and activate the same.
Regards
Jayaram M

Debugging customized function module when Idoc is triggered via ALE

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

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
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
cheers,
Hema.

How to Debug During Event Linkage( Reciever Function Module )

Hi all,
If anybody knows how to debug a reciever function module in event linkage method then please respond.The scenario is that whenever service order is changed the change event will fire the custom business object which has a supertype BUS2088.

Hi Nishanth,
You can debug event linkage using the transaction SWUE.
Here you can raise an event and specify an object key (using an already created service order).
Just flag the trigger receiver FM synchr. checkbox and your break point will be hit.
Hope that helps.
Cheers,
Brad

In WE19 getting error Message as Function module missing

Hi Friends,
I need to debug the Inbound function module
so in WE19 i am providing the IDOC number and clicking on the Inbound function module then i am getting pop-up
i am able to select my function module name
and checking the Fore ground processing Radio button
for debugging
I am getting a Warring Message as
Interface or Function module <NAME> is Incorrect
Kindly suggest me
where the mistake might be
and how to correct IT
Thanks in Advance
Ganesh

Hi Ganesh,
I believe you are using a non IDOC function module, that's the reason you are getting that error.
Use the appropriate IDOC function module and then select the Debug check box and it will stop.
If you can provide me the IDOC message then I can help you by giving the correct Function Module.
Thanks,
Mahesh.

Error in the SAP standard function module 'RSDRI_INFOPROV_READ'.

Hello Experts,
We upgraded from 3.5 to 7,0 support pack 17 .
After upgrade we are getting error
with return code 11 'Others´'.
While debugging the standard function module we found that the standard method s_r_infoprov->read is being executed with the return code = 8 (inherited_error).
Any suggestions?
Regards,
Vivek

Not sure if the parameters provided were correct,you may wish to do a sanity check
Input Parameters:
1. I_INFOPROV - This will hold the Name of the Info Cube from where we need the pull the data.
2. I_T_SFC - This parameter is in the format of Internal Table which holds the Character Info Objects we need to pull from the Source Cube.
3. I_T_SFK - This parameter is also in the format of Internal Table which holds the Key Figure Info Objects which we need to pull from the Source Cube.
4. I_T_RANGE - This is also in the format of Internal Table which holds the Selection criteria for which we need to pull from the Source Cube u2013 For example the Company Code u2013 001 and Fiscal Year Period u2013 001/2006.
5. I_T_REQUID u2013 Selection of cube data based on Request Id.
6. I_SAVE_IN_TABLE u2013 In case you need to save the data in DB table
7. I_REFERENCE_DATE u2013 This holds the current date.
8. I_AUTHORITY_CHECK u2013 This will hold the value u2018Ru2019, which is meant for READ.
9. I_DEBUG u2013 This is for Debugging mode and holds the default value u2018Yu2019.
Output Parameters:
1. E_T_DATA u2013 This Output Parameter is of internal table format, in which we can mention the output fields (For all the fields mentioned in the Input Parameter, this output parameter will hold the values).
2. E_END_OF_DATA u2013 Once the FM is executed successfully, this output parameter will hold the value u2018Xu2019, means extraction completed successfully.
Hope it Helps
Chetan
@CP..

Debugging Append Structure Function Module

Similar Messages

Maybe you are looking for