I am not getting the upload poin and recipient feilds in the PO.

Question

Hi Friends,
When i am converting a  Purchase Order with reference to Purchase Requisition with account assignment cat = network  and uploading point field data and recipient data  and the item type D ,we are not getting uploading point data and recipient data.
for this i used BADI ME_PROCESS_PO
and the INTERFACE    IF_EX_ME_PROCESS_REQ
I REALLY DONT NO HOW TO USE METHODS AND HOW TO WRITE A CODE IN THAT PLEASE HELP ME TO GET THE VALUES OF UPLOADING POINT AND RECIPIENT FIELDS DATA SHOULD POPULATE IN PURCHASE ORDER WITH RESPECT TO THA PURCHASE REQUISITION.
HELP ME WITH SUITABLE CODE FOR THE METHOD...
THANKS IN ADVANCE ........
UPENDAR G

Answer 1

I would just like to add to Billy's remarks: PL/SQL exception management is not just a language function, it also affects the database itself.
If you "swallow" exceptions, you have defeated the language and you have probably also corrupted data.
Why do I say this? Because PL/SQL exceptions cause changes in the data to roll back. If you "swallow" the exception, whatever changes you made before the error happened will not be rolled back. This is a huge threat to transactional integrity.
Here is a demonstration:SQL> create table t(k number);
table T created.
SQL> begin
insert into t values(1);
insert into t values('a');
end;
Error starting at line 6 in command:
begin
insert into t values(1);
insert into t values('a');
end;
Error report:
ORA-01722: invalid number
ORA-06512: at line 3
01722. 00000 -  "invalid number"
*Cause:   
*Action:
SQL> select * from t;
NO ROWS SELECTEDYou see, the "correct" insert into table t was rolled back automatically. This ensures the "all or nothing" property of transactions called "atomicity".
Now look what happens if you "swallow" the exception:SQL> begin
insert into t values(1);
insert into t values('a');
EXCEPTION WHEN OTHERS THEN NULL;
end;
anonymous block completed
SQL> select * from t;
K
1The first insert is not rolled back, so if the calling program commits you will have changed data without respecting transaction boundaries.