PI-ECC connection (IDOC scenario), how to debug? (External BP)

Hello everybody,
In PI -> ECC IDOC scenario I have encountered a debugging problem
Delivery IDOC is being sent from PI to ECC.
It is processed with IDOC_INPUT_DELVRY FModule.
The question is how to debug this communication?
I try to set external breakpoint in IDOC_INPUT_DELVRY with the user I can see in IDOC processing log
(IDOC Status details -> 'Logging' tab -> 'Message from' section -> 'User name').
This user is used to serve communication with PI.
User is set as dialog and has debugging rights
When I trigger communication from PI - IDOC is sent but debugger does not popup
Is my debugging approach incorrect?
I would appreciate every comment on this.
Kind Regards,
P.

Pothana Yadav
Thanks a lot for reply!
What do you mean by checking at Master_Idoc level?
I am setting a BreakPoint in IDOC_INPUT_DELVRY FModule at the very beginning. Also tried to set BP insidy my BAdi method (which is for sure being call during communication).
Or maybe you know some other way how to debug such IDOC communication triggered from PI into ECC?
I know I could use 'endless loop / sm50' trick but then I need to transport source code, which in case of Production is not feasible.
Regards,
P.

Similar Messages

Idocs with errors added status-56 in file to idoc scenario- how to rectify

hi ,
in file to idoc scenario when i m sending the file from ftp server to IS Retail, file is successfully getting processed but the idoc is showing error ,when we see using WE05 tcode or BD87 , pl sugggest how to rectify it to make the status 53

Hi,
Have you configured the partner profile details? check these steps..
1. In the receiver system you must configure the partner profile for your sender system in WE20.
2. Add the IDoc message type to inbound parameters of the partner profile and configure the appropriate process code.
2. Fill the Logical system name for your senderservice-->Adapter Specific identifiers in ID.
<a href="/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi File-to-IDOC Scenario</a> By Venugopalarao
<a href="/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi Steps for Posting IDOC's</a> By Ravikumar Allampalam
Regards
San

XI-- IDOC scenario, how to link process code with function module

Hi Forum,
I have a XI--->IDOC (R/3) scenario,
where i m creating a IDOC in XI and sending it to R/3,
i have done all settings to send the IDOC from XI to the R/3,
i also have the function module to process that IDOC in R/3,
the problem is:
I want to know in details (step by step) how to make a Idoc Inbound process code, link it with the function module and use the process code in the Partner Profile in R/3,
pls help

HI,
FOr this u need to go to transaction WE41 for inbound and WE40 for outbound there u assign the function module.
Now u go to WE20 transaction for partner profile and u can assign the proces code to the inbound message.
Go to the below help for more information:
http://help.sap.com/saphelp_nw04/helpdata/en/72/c18ee5546a11d182cc0000e829fbfe/frameset.htm
Inbound process code:
http://help.sap.com/saphelp_nw04/helpdata/en/72/c18ee5546a11d182cc0000e829fbfe/frameset.htm
Thnx
Chirag

IDoc Scenario - how to jump in context

Hello,
I need help for my iDoc -> XML scenario.
follow situation
IDOC
---SEC1
VAL1=11
VAL2=aa
---SEC1
VAL1=22
VAL2=bb
---SEC1
VAL1=33
VAL2=cc
---SEC2
SEC2.1
VAL1=11
VAL2=ab
SEC2.1
VAL1=22
VAL2=bc
SEC2.1
VAL1=33
VAL2=cd
SEC2.2
VAL1=22
VAL2=xyz
I have to test
If IDOC/SEC1/VAL1=22 then write IDOC/SEC1/VAL2 into INVAL1
If IDOC/SEC1/VAL1=22 doesn't exist
then go down to IDOC/SEC2/ and compare all VAL1 only in SEC2.1
if IDOC/SEC2/SEC2.1/VAL1=22 then write IDOC/SEC2/SEC2.1/VAL2 into INVAL1
It could be any number of SEC1 and SEC2.1
Thanks for any ideas
Andrej

Hi,
Use If Then else:
First IF Condition will be as follows.
IDOC/SEC1/VAL1--> Fix values (Default false, 22 = true)
Then Pass,
IDOC/SEC1/VAL1 --> Target
Else Pass output of below mapping
Use If without else.
If
IDOC/SEC2/SEC2.1/VAL1 --> format by example = 22
Then,
pass IDOC/SEC2/SEC2.1/VAL1
-Gouri

File to idoc scenario . how to create logical system

logical system asking user authorization what should i do.
what should be logical for whic we should degine partner profiles
apoclnt800 or xi7clnt001

Hi,
The partner profile to be maintained in we20 (in backend systems -ECC/CRM etc) should be based on logical system for the sender.
For ex: Src (File) -> PI -> Tgt(ECC)
In SLD you have created Technical System(TS) and Business System(say BS) for Src. Also a Logical System name (Say LSNAME) is associated with BS.
In ECC, goto tcode - sale, create a logical system of name LSNAME. Now goto we20 and create a partner profile of name LSNAME. Provide the message type of Idoc in the required place.
Souvik

HOW TO DEBUG EXTERNAL ABAP PROGRAM

HI ALL ,
I am new to Webdynpro Java. I am unabe to debug the ABAP program through web dynpro java application .
I want to debug the external abap program through web dynpro java application.
If it possible please let me know the required procedure for debugging.
Thanks in advance...!

Hi,
I donu2019t have any documents for that. But I vl give some points plz go through that.
1. Login into the ECC System with respective of User name and Password.
2. Enter T -Code (SE 37). Here Pass to the you are Functional Module Name (BAPI/RFC).
(By using that same BAPI/RFC u have to develop the that WDJAVA Application)
3. Pass the RFC and Click on Display Button. That RFC will be open.
4. Here u have find it Red Icons available (External/Internal Debug) Click on that External Debug.
5. Finally deploy your WDJAVA Application that time automatically youu2019re ECC System Opened.
Please check it these
F5 - Step by Step debugging
F6 - Skips loops and Subroutines
F7 - Skips the loop or subroutine and returns to the last cursor point.
F8 - Execute and come out of debugging
Hope this helps!!
Best Regards
Vijay K

Reg File to IDOC scenario with Acknowledgment

Hi Experts!
In a File to IDOC scenario , how to get the acknowledgment back to PI after posting the IDOC to SAP system and send the acknowledgment to the sender system.
What setting needs to be done in Sap and PI? Is it better if we have a BPM or is it good to have another interface to pass the acknowledgment IDOC back to the file sender.
Regards,
Srini

Dear All,
For file to idoc scenario is there any possibility to get line items details or xml details i.e the segments and its related field details using reference id, transaction id or interface name or message id in SAP PI 7.0. I know we need to click each and every message in sxi_monitor and look for details.
For SAP(R3 System) I can create a report and set the job for specific time period so automatically it throws the details(like reference no, document date, invoice no from) in ftp path as .csv file. The same ftp path is maintained in program.
I wanted to check FTP--->PI postings and I have set the job at r3 system it is working fine and Im monitoring it too.
Now the end to end scenario is FTP--->PI--->ECC(R3 system). Please help.Many Thanks.

XI unable to post IDOC to ECC the interface is FILE-to-IDOC scenario

Hi All,
The XI interface is a FILE-2-IDOC scenario and some times IDOC's in the receiver system are not posted. I did see successfully message for that particular messages but the IDOC's were not created in the ECC. If the messages is reprocessed then IDOC's are posted successfully to the ECC system. The message has checkered flag in the SXMB_MONI tcode.
This issue is occurring intermittently so could some point me in the right direction how to trouble shoot the issue.
Thanks,
Sarvesh

Hi,
Interesting problem...since its intermittant..
You cannot use any of the traditional RWB or message monitoring or cc chanel monitoring here as the error is in the ecc system, so from an XI standpoint it has left XI succssfully..that explains all the chequered flags..indicating success.
we19, we12, we14(process all idocs) test out the whole process with a load..use transaction we46..this can tell you why it is failing....in r/3
from the ecc system to check inbound queue monitoring.
from there you can select the IDocs or queues which you want to monitor, using the specified selection parameters available.
Look at the status record for the idoc that should give you more information, processing status of the idoc...that should tell you the status code assigned to it..
There is one other option here....if you can figure out what sequence they need to be posted in...that might be the reason for the failure..you can specify the sequence to post the idocs in, use qRfc ..
Hope that helps
Regards
Ravi Raman

IDOC scenario Debugging

Hi,
I want to debug the IDOC senarios(Both File to Idoc and Idoc to file ).. for this.. from where can we start.. and what are the things we need to check.. how can we debug the scenarios...
i mean.. just give me the descriptive steps..
Thanks
BABU

HI,
1. Start with checking the status in sm58 of sender R/3
Follow the steps
No message in found in XI in IDOC to FILE scenario
2. Try deleating the IDoc from IDX2 and refiring the same.
3. Check your RFC destination definition (the one pointing to your XI server) to confirm that it is of type '3' (R/3 system) and not 'T' (TCP/IP).
In your ID, in the Sender Business System --> Adapter Specific Identifiers, give the logical name for the business System pointing to the R3 system
4. Monitor the SM58 in R/3 for IDOC status.
5. Trouble shooting file to IDOC and IDOC to file
/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/error%2bhandling%2bin%2bfile-idoc%2bscenario
Refer below links for indepth troubleshooting
File to IDOC, trouble shooting
Refer below steps
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
IDOC to File steps to be followed please verify your scenario with it
R3 system.
1. Create SM 59 RFC destination to XI,.
2. We21 - Create port to XI.
3. We 20 -- Maintain Partner Profile for the outbound Idoc.
XI SLD
1. Create technical system for R3 system
2. Create Business System for the Client of the R3 system.
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
These are the required steps for IDoc to File scenario...
In R3 (i.e., your IDES system)...
RFC dest to XI (sm59) - any name
Logical system (bd54) - any name
Port to XI (we21) - any name
Partner profile for the logical system (we20) - use Logical system name created in bd54
In XI...
RFC dest to R3 (sm59) -
Port to R3 (idx1) -
create metadata for the idoc (idx2)
In sld...
create business system for R3 with Logical system name as r3 sys.
In we19
and give in control record as
Sender : Port ; Partner
Receiver : Port = <Port created in WE21> ; Partner = <Partner created in we20>
see the below links
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
idoc settings /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
Also
/people/sravya.talanki2/blog/2005/10/27/idoc146s-not-reaching-xi133-not-posted-in-the-receiver-sap-systems133
IDOc testing - /people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario
Thanks
Swarup
Edited by: Swarup Sawant on Feb 9, 2008 1:32 PM

How to debug a failed shopping cart transfer to ECC in classic mode

Hello,
I am using SRM 5 in classic mode, connected to ECC 6.0.
I have an error message in the administrator monitor that tells me a transfer a shopping cart to ECC has failed.
"Shopping cart 1000000123: Error creating the follow-on document"
(Message is BBP_PU 367)
This is located in the "local errors" section of the administrator monitor.
The follow on doucment will be a PO in ECC.
This message does not tell me the cause of the problem therefore I need to retrnsmit the cart and debug to find the error message that is being returned from ECC.
I have browsed the forum and there are various answers about debugging but but have not found exact instructions on how to debug, and it is now always clear on whether the instructions apply to classic or extended classic.
I have seen reference to the method in note 539978 that creates test data with FBGENDAT for the ECC BAPI. However this method does not seem suitable for a production system because it will interfere with all shopping carts being transferred while the shoppign cart with the problem is being debugged.
Therefore I would like to debug in SRM just for the shoppign cart with the problem.
Hopefully this thread will become the defintiive poitn of reference for debuggin a classic shopping cart transfer to ECC in SRM 5.
I propose to use function module BBP_PD_SC_TRANSFER to transfer the shopping cart again by entering the shopping cart GUID.
Question 1) Can this error message be returned by checks in SRM before the BAPI is called in ECC? If so, where do I place a breakpoint to find the error determined by the checks in SRM?
Question 2) If the system is getting as far as calling the BAPI in ECC, is it possbile to find the error message passed back from ECC by this approach, given that the actual transfer is carried out by the spooler?
Question 3) If this approach is valid, in which method/function module do I need to place a breakpoint, at which statement is the error message passed back to SRM from ECC?
Your help would be appreciated,
Reagrds

Hi Paul,
a small correction to Dishas comment:
The class CL_BBP_BS_ADAPTER_PO_CRT_470_1 is used for the backend release 4.7, so it is not relevant for you. Instead of this, you have to take the CL_BBP_BS_ADAPTER_PO_CRT_ERP10 and method CREATE_DOCUMENT. This is the last step, before the SRM calls the backend system.
From the alert "local errors" I suppose, that there is an error in the SRM customizing (in case the error message comes from the backend system, you get the message into the "Backend Application error").
Typical customizing error, when e.g. the number range of the purchase REQUISITION is not correctly customized (in case the prerequisits for a PO are not fulfilled, the system tried to create a purchase requisition). See the note 1173815 regarding this problem.
Back to your questions:
The activating of the FBGENDAT was a good idea, but I would give here two hints:
- I case of production system you can use only the "Mode B".
- Activate the FBGENDAT only for a short term:
-- at first set the breakpoint in the method CREATE_DOCUMENT (as above described)
-- execute the BBP_PD_SC_TRANSFER
-- you will be stopped at the breakpoint.
-- Now you can activate the FBGENDAT in the backend
-- go on with F8 in the debugger in the SRM system
-- >>> test data will be filled in the backend system (BAPI_PO_CREATE1)
-- deactivate the FBGENDAT
You can do this in one min. and the worst what can happen is that you have 2-3 test data in the BAPI_PO_CREATE1 additionally to the erronous SC.
Question 1) Can this error message be returned by checks in SRM before the BAPI is called in ECC? If so, where do I place a breakpoint to find the error determined by the checks in SRM?
- Maybe... Places for setting breakpoints
-- FM "BBP_PD_MSG_ADD"
-- System command "RAISE"
-- FM "META_BAPI_DISPATCH" (typical problem, see above, and also the note 1173815)
Question 2) If the system is getting as far as calling the BAPI in ECC, is it possible to find the error message passed back from ECC by this approach, given that the actual transfer is carried out by the spooler?
- Yes, you can find the message in the:
-- Test data of the BAPI_PO_CREATE1, if you have activated the FBGENDAT
-- In the method CREATE_DOCUMENT if you "comes back" from the RFC call from the backend
Question 3) If this approach is valid, in which method/function module do I need to place a breakpoint, at which statement is the error message passed back to SRM from ECC?
- see above, CL_BBP_BS_ADAPTER_PO_CRT_ERP10 method CREATE_DOCUMENT
Kind regards,
Peter

How to handle the control records in case of file to idoc scenario.

Hi All,
can you please clarify me how to handle the control records in case of file to idoc scenario.

Hi,
In File to Idoc scenario even though you selected apply control record values from payload and you are not getting those correct values which you have provided in the mapping.
Also check the checkboxes Take sender from payload and Take receiver from payload along with the Apply control record values from payload checkbox
Regards
Seshagiri

Regarding RFC connection in File to IDOC Scenario

Hi everyone,
I was configuring file to Idoc Scenario, i have made all the required configurations in SLD, IR and ID, in XI system and in R/3 System. i have created RFC connection from XI to R/3 system, and its working fine. i have created an Partner profile in WE20 with sender file system name with inbound parameters. But still i am getting error as EDI Partner Profile not defined in WE05- iDOC ADDED WITH ERRORS. Do we need to create an RFC connection from R/3 system to XI for file to Idoc Scenario
!!! Note: RFC connection from R/3 system to XI is not working, will this be a problem for file to idoc scenario. !!!
Regards,
Varun Reddy.K

Hi Varun
Follow these steps
First - Maintain the Sender R/3 System:
SM59 : Create a RFC destination to XI
WE21 : Create a TRFC Port ->Specify the RFC Destination Created
BD54 : Create a Logical System for the Idoc Receiver
WE20 : Create Partner Profile ->Maintain Outbound and the Inbound Parameters
Second - Log on to XI System:
SM59 : RFC Destination for Sender System
IDX1 : Create the port to get Idoc Metadata from Sender System ( The Port Name must match the port name in the idoc header - Usually in format SAP<System ID>. eg. SAPID1 [Optional Step. Not mandatory]
IDX2 : Maintain the Idoc Metadata. This is needed only by XI, and not by other SAP systems. IDX2 is needed because XI needs to construct IDoc-XML from the IDoc. No other SAP system needs to do that.
Regards,
Santosh

How can I include the Header Information....for a File to IDOC Scenario

Hi,
I made a File to IDOC Scenario with DEBMDM06 for MDM>XI>SAP R/3. The Header Information in the XML File which is at the XI end is Missing. For that reason In Tcode SXMB_MONI we are getting an Error that "HEADER Information Missing: Message should Start with EDI_DC40" i.e the Header Information.
My Question is that whether we can do some changes in the Message mapping Step in the Integration Repository. I HardCoded the Few mandatory Fields that were there but it Again gave me the Same Error as above.
Can you please Suggest some Solution for this. Since the data is Coming in from MDM part the Header information is not there but It actually Important as it has got all the Port Information.
Kindly Inform me some Solutions.
Thanks & Regards
Somnath

Hi Suraj,
Thanks for ur Reply, but Since we are Doing a File to IDOC Scenario the IDOC DEBMDM is on the Right Side in Message Mapping and as U know it is Mandatory to Map an IDOC on the Right Part. EDI_DC40 is coming as it is there in the IDOC but our XML File Does not have that. If we Don't Map then it Becomes RED, which is an Error.
Furthermore in the Receiver Agreement we have put the Necessary Details such as Sender Service and Receiver Service along with the IDOC Communication Channels.
Can U give as a Better Insight on this Note how to check the Header Part as it is mandatory to MAP.We also tried to HARDCODE it by putting those Values and Mapping them to a Constant but it is Giving the Same Error.
Thanks and Regards
Somnath

How to reduce processing time in case of jms to idoc scenario

hi all,
i am doing jms to idoc scenario.
in this i'm using xslt and graphical mapping.
while perfroming E2E testing the messages are taking lot of time to get processed.
please tell me as how can i reduce this processing time or in short how can i overcome this problem.this is a critical issue in production.
regards
madhu

Hi,
1. To reduce the processing time for JMS -> IDOC scenario, try to get the Average processing time taken by JMS adapter, IE, IDOC adapter for the messages that are processed so far by going thro the Adapter Audit logs, SXMB_MONI race and Time in WE02 in R/3 system. Calculate this for 5 - 10 messages at different time to get the clear idea of which step is consuming more time. Then it will be helpful to focus on tuning that specific step. If you are using BPM, check the processing time taken by PE.
2. Check the Inbound and Outbound queues used by this interface, if required try to configure Prioritized Queue with more time allocated for this interface in Integration Engine.
3. Check the load on the Integration Server when this Interface messages are getting processed, to understand/ isolate the interfaces which are consuming more processing time and system resources.
4. If this is not in Production try to perform the Mapping/ transformation in graphical mapping itself, it will be helpful to minimise use of XSLT mapping to get better performance.
5. Check if the Archive and Delete jobs are running successfully in the Integration Server, since this will free up the occupied resources in the system.
6. If possible post seperate Forum questions for issues in different Interface scenarios, it will be easy to understand the problem for all of us.
Hope this will be helpful,
Regards,
S.Santhosh Kumar

I have a scenario, ECC-PI-Message broker. ECC sending IDOC to PI, PI execute mapping and sending data to Message borker.(with almost one to one mapping)., IDOC(AAE)-PI-JMS. Now my requirement is., from PI after mapping we need to save file in SAP fold

I have a scenario, ECC-PI-Message broker. ECC sending IDOC to PI, PI execute mapping and sends data to Message borker(thru JMS channel).(with almost one to one mapping)., IDOC(AAE)-PI-JMS. Now my requirement is., from PI after mapping we need to create file with same data what ever send to Message broker and put the file in SAP folder without touching mapping. Is it possible? Please advise with the steps. We are using the ICO for this senario. Quick response is appriciated.

Hi Pratik,
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/502991a2-45d9-2910-d99f-8aba5d79fb42?quicklink=index&overridelayout=true
This link might help.
regards
Anupam

PI-ECC connection (IDOC scenario), how to debug? (External BP)

Similar Messages

Maybe you are looking for