R/3 IDOC - XI- ORACLE Error Handling

Hi,
All
we have to send IDOC Data to ORACLE system Through XI.
R/3 IDOC (OB)->XI ->ORACLE(IB)
In This scenarion How we can handle the errors between
R/3 IDOC (OB) ->XI
And
XI->ORACLE
Here we need to check the Null Values and invalid Data. in XI.
Thnx in Advance
regards
kumar

Hi,
Michal
Thankyou for your prompt reply and I appreciate your help.
Ans:if you need to check if the idoc has all fields
you can do checks in the mapping .
In value mapping or in User define function we can check?
Ans: if it does not have everything start an exception
in the mapping
how this exception will intimate us does this data having errors?
regards
kumar

Similar Messages

Oracle Error Handling in Shell Scripts

I need to manage 2 diferente class of errors :
Oracle Errors(produced in compilation time) and
Operating Syste Error(e.g. No Datbase conection ORA-1017,etc) my shell its KSH.
Please can you help me how can I manage then?
this my alternative but is not correct ;
#creating conexion with sql
exit | sqlplus -s $USERPV_DB/$PWDPV_DB @$VORDSQLPATH/ord.extractor_porven.sql $VFDESDE $VFHASTA > $VORDDATOS_PATH/ord.extractor_porven$VDATE.dat 2>> $VLOG
     #Evaluating last sentence (sqlplus . . . . )
     VERROR=$?
     #Si VERROR=0 should stop process execution and alert with echo ".."Oracle error handling before compilation time
     if [ $VERROR != 0 ]
     then
     echo "value of VERROR are:$VERROR"
     echo "`date +"$V_FORMATDATE"` DATA EXTRACTION WAS NOT SUCESSFUL ERROR BEFORE COMPILATION TIME" >> $VLOG 2> /dev/null
     " Here show VERROR
     else #Oracle error handling in compilation time
     echo "`date +"$V_FORMATDATE"` DATA EXTRACTION WAS NOT SUCESSFUL ERROR BEFORE COMPILATION TIME " >> $VLOG
     " Here show VERROR
else if [ $VERROR = 0 ]
" DATA EXTRACTION WAS SUCESSFUL"
fi
Would apreciate your help its very urgent.
Best Regards
Antonio

user5647282 wrote:
I need to manage 2 diferente class of errors :
Oracle Errors(produced in compilation time) and
Operating Syste Error(e.g. No Datbase conection ORA-1017,etc) my shell its KSH.
Please can you help me how can I manage then?
this my alternative but is not correct ;
#creating conexion with sql
exit | sqlplus -s $USERPV_DB/$PWDPV_DB @$VORDSQLPATH/ord.extractor_porven.sql $VFDESDE $VFHASTA > $VORDDATOS_PATH/ord.extractor_porven$VDATE.dat 2>> $VLOG
Piping the output of 'exit' to sqlplus????????? what do you expect from this?
     #Evaluating last sentence (sqlplus . . . . )
     VERROR=$?any error returned by sqlplus as $? would be a fatal error of sqlplus itself, not any error returned by processing a sql statement. If your script ord.extractor_porven.sql were to generate, say, an ORA-00001, that is NOT an error in sqlplus and so does not return to the OS as an error of sqlplus.
     #Si VERROR=0 should stop process execution and alert with echo ".."Oracle error handling before compilation time
     if [ $VERROR != 0 ]
     then
     echo "value of VERROR are:$VERROR"
     echo "`date +"$V_FORMATDATE"` DATA EXTRACTION WAS NOT SUCESSFUL ERROR BEFORE COMPILATION TIME" >> $VLOG 2> /dev/null
     " Here show VERROR
     else #Oracle error handling in compilation time
     echo "`date +"$V_FORMATDATE"` DATA EXTRACTION WAS NOT SUCESSFUL ERROR BEFORE COMPILATION TIME " >> $VLOG
     " Here show VERROR
else if [ $VERROR = 0 ]
" DATA EXTRACTION WAS SUCESSFUL"
fi
Would apreciate your help its very urgent.
there is no "urgent" here.
"Urgent" means one of two things -
1) people are dying, or
2) you have a customer-facing, revenue-producing production system that is down.
(And to get some perspective on the second case, keep the first in mind.)
For the first, you call whatever civil emergency service seems appropriate.
For the second, you open an SR with Oracle - which requires a paid-up support contract. For them to consider your problem "urgent", you will need to demonstrate that your problem falls under item #2. I seriously doubt your problem fits that criteria.
Best Regards
Antonio

IDOC to JDBC :Error handling in Query execution

Hi,
I have a scenario idoc to JDBC, here I will get 'n' number of segments in an idoc corresponding to 'n' records which needs to be updated in SQL Database table.
In this scenario how we can handle the error when any record is failing while updating into the table?
Is there any method by which we can know which records are successfull and which records are unsuccessfull?
Please provide your valuable ideas.
Regards,
Shiva.

Hi Soorya,
thanks for the response.
Actually I want to know how to handle the situation when we are trying to insert/update 10 records and if 6th,7th and 8th records failed to insert/update then
1. Will the other records are insert/updated in to the DB?
If yes : then how to get know the failed records(6th , 7th and 8th) i.e., how the response msg will be?
If no : then how the response msg will be?
2. Is this achieved thru normal sql query or need to use stored procedure?
Regards,
Shiv.

Oracle error handling

Hi, all
I'm new to Oracle and trying to find which Oracle predefined exceptions to handle explicityly in my sp/package. I'll need to do this to capture all available for specific action, then translate them into "User friednly" message to be sent to client without going into ORA-9999 details. I excpect to hard code most probable Exceptions and the rest hadnle with WHEN OTHER..
Also what the best way to keep ORA-9999 type messages for later review, is there any special logging mechanism for Oracle, so I can access them after execution.
Also I read that EXCEPTION should be coded at the end of the sql block, that bit confusing for me, is it alwayse it's the end of actual procedure ? or there is some type of "block" delimiter. In another words, can I write some other code after EXCEPTIONS?
For my case I'm looking for list of EXCEPTION for the following sql code:
for SELECT (to cursor):
for UPDATE:
Thansk
T

You will, of course, handle the exceptions you expect to see - like NO_DATA_FOUND, and other typical processing exceptions.
For the others, you have three choices
1. Let the exception bubble up to the user so that he can see that something really bad happened. When he opens a trouble ticket to report that something awful happened, he will pass the full text of the exception message ticket and you will have some idea of what happened and where in the code.
2. Capture the input arguments and processing steps along the way in the procedure and write them to a log - delete anything over three days old. Then when something bad happens place a marker entry into the log with the error stack, call stack. Now you can pass a message back to the user to say something like 'Something bad happened. Please contact application support.'.
3. Create a package to handle exceptions for you - this is a rather sophisticated piece of code - that will trap and log exception details and, possibly, create an entry in the alert log or trace file. You will call this from the exception handler, then return and pass a message back to the user telling him that something bad happened.
Some how or other, you will need the information provided by the error stack to help you identify the root cause and fix the problem.

IDOC to SOAP asynchronous scenario Error handling

Need an expert!!!!!!!!! advise on error handling for IDOC--PI--
SOAP scenario.This is a asynchronous scenario where PI is calling a Legacy system using SOAP adapter.My question is how i can do error handling in this scenario.If i get an alert in pi with payload variable that would be fine, do i need to use BPM and if that is tthe case what will be steps.
Appreciate your help.
Manish

Hello Manish,
My question is how i can do error handling in this scenario.
Use the standard alert framework. Search on SDN / SAP Help for details.
do i need to use BPM and if that is tthe case what will be steps.
BPM is not required to raise alerts, as this is an async call.
Regards,
Neetesh

Error Handling in File to Multiple IDOC Scenario?

Hello Experts,
My scenario is file with Multiple records and I want to send it to SAP system.If there will be 10 Records in my file I need to create 10 IDOC in Target system.
I can use below of the two options.
1) File to Multiple Idoc (1.N Mapping)
2) Using BPM
3)Directly place the file in SAP application server and process it via ABAP Program.
However I am not clear in which option error handling will be more effective.Please suggest.
Basically I want to handle If out of 10 records 9 are correct and 1 record is not correct then I should be able to report within PI without affecting 9 correct records.Is it possible 9 records will be sent to SAP system and PI will only show error for 1 incorrect record.
Also I will be doing this scenrio for transaction data with huge size (1 Million Records).Which approach will be more effective in this case.
Thanks,
Pushkar

Hi Patel,
I want to handle If out of 10 records 9 are correct and 1 record is not correct then I should be able to report within PI without affecting 9 correct records.Is it possible 9 records will be sent to SAP system and PI will only show error for 1 incorrect record.
when working on graphical mapping, the target structure is created when there are no errors in all records of source structure.
suppose if we have validation error in 9th and 10th record, then we can not process the first eight records and inturn we can not store the two error records in XI for further.
i suggest you the third option, you can directly place the file in SAP application server and process it via ABAP Program.
this is far better because you can do more customizations as you have to deal with millions of records.
Regards,
Pradeep A.

For IDOC monitoring, analysis and error handling in ALE & idoc

Hello...experts..can u please tell me about idoc monitoring,analysis and error handling..and can u please tell as per interview point of view in this area..if availble can u send material about this...
thx
Message was edited by:
durga kottapalli

Hi,
Reprocessing IDocs with errors
Outbound (BD88)
Once the error has been determined and corrected it is not necessary to resend the IDoc again. You simply resend the IDocs that have already been generated.
Using the IDoc overview screen you need to take note of the following for each IDoc that was not processed:
Error number: 2, 4, 5, 25, 29
Error number: 30 (Execute Check IDoc dispatch to process)
IDoc number
Using the Error number, the IDoc number and the transaction BD88 , with the required message type you can resend the IDoc. Match the error number with this transaction and execute the function for the IDocs incorrectly processed.
Just check the below link, u will get all IDOC related Interview questions
http://www.allsaplinks.com/idoc_sample.html
http://www.allsaplinks.com/
http://www.sappoint.com/abap.html
http://www.sap-img.com/
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
http://www.sappoint.com/abap.html
http://sap.ittoolbox.com/documents/popular-q-and-a/extending-a-basic-idoc-type-2358
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://expertanswercenter.techtarget.com/eac/knowledgebaseCategory/0,295197,sid63_tax296858_idx0_off50,00.html
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
http://help.sap.com/saphelp_47x200/helpdata/en/dc/6b7eee43d711d1893e0000e8323c4f/frameset.htm
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sap-img.com/
http://www.allsaplinks.com/
Regards,
Suresh.
Message was edited by:
SureshKumar Ramamoorthy

Error handling in bdc Fb01along with erros in Idoc.

Hi,
Can any one send me the sample code for the error handling in bdc Fb01along with erros in Idoc. Actually, mail should be sent
Thanks
Avi.

Hi,
This may help you.
<b>FORM send_mail USING   receiver.
CLEAR: w_lines,tbl_packing_list,tbl_object_header,
             tbl_contents_txt, tbl_receivers.
REFRESH:tbl_packing_list, tbl_object_header,
           tbl_contents_txt,tbl_receivers.
SORT tbl_err.
DELETE ADJACENT DUPLICATES FROM tbl_err COMPARING ALL FIELDS.
IF NOT tbl_err[] IS INITIAL.
Preparing the email.
    PERFORM prepare_email.
ELSE.
   If sy-subrc NE 0.
      MOVE sy-subrc TO w_code.
   ENDIF.
    EXIT.
ENDIF.
Get the content of header e-mail document data
PERFORM document_data.
Get details of the error file attached (like type of file and format)
PERFORM packing_list.
Get receiver mail id's
tbl_receivers-receiver = receiver.
tbl_receivers-rec_type = 'C'.
tbl_receivers-express = c_flag.
tbl_receivers-sap_body = c_flag.
APPEND tbl_receivers.
Call FM to send E-mails to receivers
CALL FUNCTION 'SO_NEW_DOCUMENT_ATT_SEND_API1'
       EXPORTING
            document_data              = st_document_data
            put_in_outbox              = 'X'
       TABLES
            packing_list               = tbl_packing_list
            object_header              = tbl_object_header
            contents_txt               = tbl_contents_txt
            receivers                  = tbl_receivers[]
       EXCEPTIONS
            too_many_receivers         = 1
            document_not_sent          = 2
            document_type_not_exist    = 3
            operation_no_authorization = 4
            parameter_error            = 5
            x_error                    = 6
            enqueue_error              = 7
            OTHERS                     = 8.
ENDFORM.                    " send_mail
*&      Form prepare_email
      text
--> p1        text
<-- p2        text
FORM prepare_email.
E-Mail body content
IF NOT w_lifnr IS INITIAL.
    CONCATENATE text-015 w_docnum text-016
           INTO tbl_contents_txt-line
      SEPARATED BY space.
ENDIF.
APPEND tbl_contents_txt.
CLEAR tbl_contents_txt.
E-mail error file attachment header
CONCATENATE text-063 text-064
               text-065 text-066 c_comma
         INTO tbl_contents_txt-line
    SEPARATED BY c_comma.
APPEND tbl_contents_txt.
CLEAR tbl_contents_txt.
E-mail error file attachment content
LOOP AT tbl_err.
    CONCATENATE w_docnum tbl_err-v_segnum
                tbl_err-msg tbl_err-type
      INTO tbl_contents_txt-line
      SEPARATED BY c_comma.
    CONCATENATE c_linefeed tbl_contents_txt-line c_comma
           INTO tbl_contents_txt-line.
    APPEND tbl_contents_txt.
    CLEAR tbl_contents_txt.
ENDLOOP.
ENDFORM.                    " prepare_email
*&      Form document_data
      text
--> p1        text
<-- p2        text
FORM document_data.
CLEAR w_line.
IF NOT w_lifnr IS INITIAL.
    CONCATENATE text-075 text-027 sy-datum sy-uzeit INTO w_line
    SEPARATED BY c_uscore.
ENDIF.
st_document_data-obj_name = w_line.
st_document_data-obj_descr = w_line.
st_document_data-priority = 1.
st_document_data-obj_prio = 1.
ENDFORM.                    " document_data
*&      Form packing_list
      text
--> p1        text
<-- p2        text
FORM packing_list.
CLEAR w_lines.
DESCRIBE TABLE tbl_err LINES w_lines.
READ TABLE tbl_contents_txt INDEX w_lines.
tbl_packing_list-head_start = 1.
tbl_packing_list-head_num   = 1.
tbl_packing_list-body_start = 1.
tbl_packing_list-body_num   = 1.
tbl_packing_list-doc_type   = 'RAW'.
APPEND tbl_packing_list.
tbl_packing_list-head_start = 1.
tbl_packing_list-head_num   = 0.
tbl_packing_list-body_start = 2.
tbl_packing_list-body_num   = w_lines + 1.
tbl_packing_list-doc_type   = 'CSV'.
tbl_packing_list-obj_descr = 'Error_Attachment'(060).
IF NOT w_lifnr IS INITIAL.
    tbl_packing_list-obj_name   = 'Idoc Number is'(072).
ENDIF.
tbl_packing_list-doc_size   = 255 * ( w_lines + 1 ).
APPEND tbl_packing_list.
ENDFORM.                    " packing_list
</b>
Thanks
Manju.

Error handling in Oracle

Hello,
Could anyone help to convert the following T-SQL statement to PL-SQL? Thanks inadvance!
BEGIN TRAN
UPDATE Table1 SET .......
SELECT @ReturnCode = @@error
IF @ReturnCode <> 0
     BEGIN
          SELECT @msg = 'Error - update date feed'
GOTO Err_Handler
     END
COMMIT TRAN
RETURN 0
Err_Handler:
          ROLLBACK TRAN
          INSERT INTO LogTable(ProcessName, ProcessStatus)
               VALUES('Daily date feed', @msg)
          EXEC msdb.dbo.sp_send_dbmail
               @recipients = '[email protected]',
               @Subject = 'Daily datafeed process failed',
               @body = @msg
          RETURN 1

Sänjay wrote:
Hi,
Anonymous block example
SQL> declare
2   x number ;
3 begin
4    select count(*) into x from dual ;
5    update emp set empno=empno ;
6    dbms_output.put_line('Rows updated '|| sql%rowcount);
7 exception -- Exception Or Error Handling
8   when others then
9    rollback ;
10    dbms_output.put_line(SQLERRM);
11 end ;
12 /
Rows updated 14
PL/SQL procedure successfully completed.SSAwful example! I would fire programmers who would repeatetly produce such code. Rule #1: Avoid "when others expetions" wherever possible!
I know you're capable of give much better examples.
Btw: This code would produce the same result in sql*plus without any exception block:
proof
SQL> select * from v$version;
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
PL/SQL Release 10.2.0.4.0 - Production
CORE    10.2.0.4.0      Production
TNS for HPUX: Version 10.2.0.4.0 - Production
NLSRTL Version 10.2.0.4.0 - Production
SQL>
SQL> drop table test;
Table dropped.
SQL> set serveroutput on
SQL> create table test (col1 number);
Table created.
SQL>
SQL> /* first without exception */
SQL> declare
2     x number ;
3 begin
4     insert into test values (1);
5     select length(dummy) into x from dual where 1=1;
6 end;
7 /
PL/SQL procedure successfully completed.
SQL>
SQL> select * from test;
      COL1
         1
SQL>
SQL> /* now add some error */
SQL>
SQL> declare
2     x number ;
3 begin
4     insert into test values (2);
5     select length(dummy) into x from dual where 1=2;
6 end;
7 /
declare
ERROR at line 1:
ORA-01403: no data found
ORA-06512: at line 5
SQL>
SQL> select * from test;
      COL1
         1
SQL>
SQL> As you can see the second insert was rollbacked. But be careful, this works only for ANONYMOUS pl/sql blocks.
Edited by: Sven W. on Jul 24, 2009 3:17 PM

Error handling limitations in XI3.0 SP11 when using IDOC's

Backround: Sending IDOC's from XI to a 6.20 SAP system with ALEAUD turned on.
We have found a couple of limitations with XI 3.0 SP11 regarding error handling and are wondering what other XI Developers are doing to work around them:
1) Unable to generate Alerts from global Alert Rules (PMI) in a BPM
2) Unable to handle IDOC negative acknowledgments in a BPM
3) Unable to generate Alerts from Alert Rules (PMI) for negative IDOC acks when NOT using a BPM
So far we are designing around these issues by using deadline monitoring steps in BPM's to handle IDOC posting errors and raising an Alert (the beauty of this workaround is that the BPM will automatically continue when the IDOC data is corrected and posted), and for non-BPM interfaces the errors must be handled in the receiving SAP system.
We have sent these issues in to OSS but the replies have come back stating that it is 'by design'.
Thx,
Jason.

Did you get any better solution now?
Regards
Mike

Oracle stored procedure call failed,but not captured by the error handling

Hi All,
I have a unix shelll script which calls a stored proc in Oracle, the stored proc call failed due to "ORA-01033: ORACLE initialization or shutdown in progress".
But it is not captured in the error handling block, Any ideas why this had happened?
SQL file had : my_test_sql.sql
exec my_proc(..............);
Unix shell script has this call:
sqlplus -s my_user/my_pwd@db1 @my_test_sql.sql
if [[ $? -ne 0 ]]; then
echo "failed"
exit 1
else
echo "success"
fi
If i execute the above shell, I'm getting the following
ERROR:
ORA-01033: ORACLE initialization or shutdown in progress
SP2-0306: Invalid option.
Usage: CONNÝECT¨ Ýlogon¨ ÝAS SYSDBA¨
where <logon> ::= <username>Ý/<password>¨Ý@<connect_identifier>¨ | /
success.
This puzzled me, any pointers?

The $? status variable shows the return code of the last command executed. It will be difficult to determine what the exit status of your sql script is without knowing the script. Do you have any "WHENEVER SQLERROR EXIT" statements in the script?
The ORA-01033 error happens when the database is not open, perhaps in recovery, or startup or shutdown is halted due to a failed or full disk, error in archiving or writing to redo, etc.

How to handle an Oracle error

I want to handle an Oracle Error in my code where the "execute immediate" statement comes to play.
My code goes against several tables
ID_TABLE_08
ID_TABLE_07
ID_TABLE_06
If table does not exist in database (ie: ID_TABLE_05) I get : Oracle Error ORA-0942 table or view does not exist.
How can I capture and handle this error so
1. The code will continue to run getting the next value
2. The bad record still will get written in to a table called bad_table.
v_year := TO_CHAR (pp_eff_dtg (indx), 'yy');
BEGIN
EXECUTE IMMEDIATE
'SELECT DISTINCT ID_number
FROM ID_TABLE_'|| v_year||'
WHERE NAME = :NAME
AND EFFECTIVE_DATE = : EFFECTIVE_DATE
INTO v_ID_number
USING pp_NAME (indx),
pp_eff_dtg (indx);
GOTO END_LOOP;
EXCEPTION
WHEN NO_DATA_FOUND THEN
GOTO INSERT_ADD_RECORD;
END;
Thank you for your help!

if you want to handle a specific oracle error number you can also declare an exception, match that exception to the error number and handle it.
Like this (not syntax checked)
declare
e_table_does_not_exist exception;
pragma exception_init (-942,e_table_does_not_exist); -- I hope I got the parameters in the right order
begin
   EXECUTE IMMEDIATE('select * from ID_TABLE_'|| v_year||' where ...');
exception
   when e_table_does_not_exist then -- handle specific error
       raise_application_error(-20001,'The table ID_TABLE_'|| v_year||' could not be found. Next time enter a valid year!');
end;

Regarding Error handling and customisation in RFC, Idocs and Proxy

Hi,
I wanted to compare RFC, Proxy and Idocs on the basis of the amount of customisation required in ECC when sending data from ECC to XI using the above stated means and also the error handling provided in these methods.
Please let me know in detail if possible.
Regards,
Sampada

Hi ,
Check this blog to know when to use which adapter:
/people/ravikumar.allampallam/blog/2005/08/14/choose-the-right-adapter-to-integrate-with-sap-systems
we use proxy in sap 6.0 version or higher.
Basically used for adapter less communication
& very high volume of data has to be transfered.
Step for Configuration fo IDOC in R/3
1) RFC Destination (SM59)
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.
2) Create Port (IDX1)
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
3) Load Meta Data for IDOC (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
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.
2) Create Port (We21)
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
3) Create Partner Profile (WE20)
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.
In SLD System Landscape Directory
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.
In Transaction SALE
Define and Assign the logical system name.
Regards,
Vinod.

Error Handling in Oracle Sales Cloud

Is there a best practice guide/document for error handling in Oracle Sales Cloud?
For example: Error handling in groovy scripts, business processes.
Can someone provide a starting point to this topic?
Thanks,
Abhishek

Hi.
Please review this short video showing you the online logging feature for Application Composer - Groovy. It's very simple and gives you a basic debug capability.
https://www.youtube.com/watch?v=RcyeKQY2ZGo&index=35&list=PL1ZiAfFIniZf_Uu4qTcp5IZYdFOm9K5o3
Kind regards,
Richard
FA Developer Relations

Outbound Idoc error handling through workflow

Hi,
I am trying to set up the workflow for outbound error handling. I found that there is a task TS00007989 which need to set up.
How this task can be triggered when outbound idoc error occurs in the system?
Kr,
Vithalprasad
Edited by: Vittalprasad on Jun 9, 2010 11:52 AM

Hi,
Have a look
Outbound IDoc Error Handling via Workflow
Outbound idoc error handling through workflow

R/3 IDOC - XI- ORACLE Error Handling

Similar Messages

Maybe you are looking for