Issue in production

1)WHEN EVER I DELETE A RECORD FROM MUL_TEST TABLE IT SHOULD RAISE A TRIGGER AND CALL A PROCEDURE THAT IS GIVEN BY ME .
2 )FOR THAT DELETED RECORD IN THAT PROCEDURE FIRST IT SHOULD HAVE TO CHECK FOR ACCOUNTNO IN MUL_TEST TABLE WITH ACCOUNTNO IN REG TABLE (THE DELETED RECORD ONLY) IF IT IS THERE THEN NO ISSUE IF IT IS NOT THERE THEN IT HAS TO CHECK FOR MOBILE NUMBER IN MUL_TEST WITH REG TABLE IF IT IS ALSO NOT THERE THEN THAT PARTICULAR deleted RECORD HAVE TO BE INSERTED IN EMAILINFO TABLE(MESSAGE COLUMN) GIVEN BELOW
Mul_test: TABLE
SET DEFINE OFF;
Insert into TEST.MUL_TEST
(EMPNO, ENAME, JOB, MGR, HIREDATE,
SAL, COMM, DEPTNO, ACCOUNTNUMBER, MOBILENUMBER)
Values
(7369, 'SMITH', 'CLERK', 7902, TO_DATE('12/17/1980 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
800, NULL, 20, '123456', '8897136043');
Insert into TEST.MUL_TEST
(EMPNO, ENAME, JOB, MGR, HIREDATE,
SAL, COMM, DEPTNO, ACCOUNTNUMBER, MOBILENUMBER)
Values
(7499, 'ALLEN', 'SALESMAN', 7698, TO_DATE('02/20/1981 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
1600, 300, 30, '123457', '8897136044');
Insert into TEST.MUL_TEST
(EMPNO, ENAME, JOB, MGR, HIREDATE,
SAL, COMM, DEPTNO, ACCOUNTNUMBER, MOBILENUMBER)
Values
(7521, 'WARD', 'SALESMAN', 7698, TO_DATE('02/22/1981 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
1250, 500, 30, '123458', '8897136045');
Insert into TEST.MUL_TEST
(EMPNO, ENAME, JOB, MGR, HIREDATE,
SAL, COMM, DEPTNO, ACCOUNTNUMBER, MOBILENUMBER)
Values
(7566, 'JONES', 'MANAGER', 7839, TO_DATE('04/02/1981 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
2975, NULL, 20, '123460', '8897136046');
Insert into TEST.MUL_TEST
(EMPNO, ENAME, JOB, MGR, HIREDATE,
SAL, COMM, DEPTNO, ACCOUNTNUMBER, MOBILENUMBER)
Values
(7654, 'MARTIN', 'SALESMAN', 7698, TO_DATE('09/28/1981 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
1250, 1400, 30, '123461', '8897136047');
Insert into TEST.MUL_TEST
(EMPNO, ENAME, JOB, MGR, HIREDATE,
SAL, COMM, DEPTNO, ACCOUNTNUMBER, MOBILENUMBER)
Values
(7698, 'BLAKE', 'MANAGER', 7839, TO_DATE('05/01/1981 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
2850, NULL, 30, '123462', '8897136048');
Insert into TEST.MUL_TEST
(EMPNO, ENAME, JOB, MGR, HIREDATE,
SAL, COMM, DEPTNO, ACCOUNTNUMBER, MOBILENUMBER)
Values
(7782, 'CLARK', 'MANAGER', 7839, TO_DATE('06/09/1981 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
2450, NULL, 10, '123463', '8897136049');
Insert into TEST.MUL_TEST
(EMPNO, ENAME, JOB, MGR, HIREDATE,
SAL, COMM, DEPTNO, ACCOUNTNUMBER, MOBILENUMBER)
Values
(7788, 'SCOTT', 'ANALYST', 7566, TO_DATE('12/09/1982 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
3000, NULL, 20, '123464', '8897136050');
Insert into TEST.MUL_TEST
(EMPNO, ENAME, JOB, MGR, HIREDATE,
SAL, COMM, DEPTNO, ACCOUNTNUMBER, MOBILENUMBER)
Values
(7839, 'KING', 'PRESIDENT', NULL, TO_DATE('11/17/1981 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
5000, NULL, 10, '123465', '8897136051');
Insert into TEST.MUL_TEST
(EMPNO, ENAME, JOB, MGR, HIREDATE,
SAL, COMM, DEPTNO, ACCOUNTNUMBER, MOBILENUMBER)
Values
(7844, 'TURNER', 'SALESMAN', 7698, TO_DATE('09/08/1981 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
1500, 0, 30, '123466', '8897136052');
Insert into TEST.MUL_TEST
(EMPNO, ENAME, JOB, MGR, HIREDATE,
SAL, COMM, DEPTNO, ACCOUNTNUMBER, MOBILENUMBER)
Values
(7876, 'ADAMS', 'CLERK', 7788, TO_DATE('01/12/1983 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
1100, NULL, 20, '123467', '8897136053');
Insert into TEST.MUL_TEST
(EMPNO, ENAME, JOB, MGR, HIREDATE,
SAL, COMM, DEPTNO, ACCOUNTNUMBER, MOBILENUMBER)
Values
(7900, 'CLERK', 'CLERK', 7698, TO_DATE('12/03/1981 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
950, NULL, 30, '123468', '8897136054');
Insert into TEST.MUL_TEST
(EMPNO, ENAME, JOB, MGR, HIREDATE,
SAL, COMM, DEPTNO, ACCOUNTNUMBER, MOBILENUMBER)
Values
(7902, 'FORD', 'ANALYST', 7566, TO_DATE('12/03/1981 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
3000, NULL, 20, '123469', '8897136055');
Insert into TEST.MUL_TEST
(EMPNO, ENAME, JOB, MGR, HIREDATE,
SAL, COMM, DEPTNO, ACCOUNTNUMBER, MOBILENUMBER)
Values
(7934, 'MILLER', 'CLERK', 7782, TO_DATE('01/23/1982 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
1300, NULL, 10, '123470', '8897136056');
Insert into TEST.MUL_TEST
(EMPNO, ENAME, JOB, MGR, HIREDATE,
SAL, COMM, DEPTNO, ACCOUNTNUMBER, MOBILENUMBER)
Values
(7369, 'SMITH', 'CLERK', 7902, TO_DATE('12/17/1980 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
800, NULL, 20, '654321', '8897136043');
Insert into TEST.MUL_TEST
(EMPNO, ENAME, JOB, MGR, HIREDATE,
SAL, COMM, DEPTNO, ACCOUNTNUMBER, MOBILENUMBER)
Values
(7499, 'ALLEN', 'SALESMAN', 7698, TO_DATE('02/20/1981 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
1600, 300, 30, '654322', '8897136044');
Insert into TEST.MUL_TEST
(EMPNO, ENAME, JOB, MGR, HIREDATE,
SAL, COMM, DEPTNO, ACCOUNTNUMBER, MOBILENUMBER)
Values
(7521, 'WARD', 'SALESMAN', 7698, TO_DATE('02/22/1981 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
1250, 500, 30, '654323', '8897136045');
Insert into TEST.MUL_TEST
(EMPNO, ENAME, JOB, MGR, HIREDATE,
SAL, COMM, DEPTNO, ACCOUNTNUMBER, MOBILENUMBER)
Values
(7566, 'JONES', 'MANAGER', 7839, TO_DATE('04/02/1981 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
2975, NULL, 20, '654324', '8897136046');
Insert into TEST.MUL_TEST
(EMPNO, ENAME, JOB, MGR, HIREDATE,
SAL, COMM, DEPTNO, ACCOUNTNUMBER, MOBILENUMBER)
Values
(7654, 'MARTIN', 'SALESMAN', 7698, TO_DATE('09/28/1981 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
1250, 1400, 30, '654325', '8897136047');
Insert into TEST.MUL_TEST
(EMPNO, ENAME, JOB, MGR, HIREDATE,
SAL, COMM, DEPTNO, ACCOUNTNUMBER, MOBILENUMBER)
Values
(7698, 'BLAKE', 'MANAGER', 7839, TO_DATE('05/01/1981 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
2850, NULL, 30, '654326', '8897136048');
Insert into TEST.MUL_TEST
(EMPNO, ENAME, JOB, MGR, HIREDATE,
SAL, COMM, DEPTNO, ACCOUNTNUMBER, MOBILENUMBER)
Values
(7782, 'CLARK', 'MANAGER', 7839, TO_DATE('06/09/1981 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
2450, NULL, 10, '654327', '8897136049');
Insert into TEST.MUL_TEST
(EMPNO, ENAME, JOB, MGR, HIREDATE,
SAL, COMM, DEPTNO, ACCOUNTNUMBER, MOBILENUMBER)
Values
(7788, 'SCOTT', 'ANALYST', 7566, TO_DATE('12/09/1982 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
3000, NULL, 20, '654328', '8897136050');
Insert into TEST.MUL_TEST
(EMPNO, ENAME, JOB, MGR, HIREDATE,
SAL, COMM, DEPTNO, ACCOUNTNUMBER, MOBILENUMBER)
Values
(7839, 'KING', 'PRESIDENT', NULL, TO_DATE('11/17/1981 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
5000, NULL, 10, '654329', '8897136051');
Insert into TEST.MUL_TEST
(EMPNO, ENAME, JOB, MGR, HIREDATE,
SAL, COMM, DEPTNO, ACCOUNTNUMBER, MOBILENUMBER)
Values
(7844, 'TURNER', 'SALESMAN', 7698, TO_DATE('09/08/1981 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
1500, 0, 30, '654330', '8897136052');
Insert into TEST.MUL_TEST
(EMPNO, ENAME, JOB, MGR, HIREDATE,
SAL, COMM, DEPTNO, ACCOUNTNUMBER, MOBILENUMBER)
Values
(7876, 'ADAMS', 'CLERK', 7788, TO_DATE('01/12/1983 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
1100, NULL, 20, '654331', '8897136053');
Insert into TEST.MUL_TEST
(EMPNO, ENAME, JOB, MGR, HIREDATE,
SAL, COMM, DEPTNO, ACCOUNTNUMBER, MOBILENUMBER)
Values
(7900, 'CLERK', 'CLERK', 7698, TO_DATE('12/03/1981 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
950, NULL, 30, '654332', '8897136054');
Insert into TEST.MUL_TEST
(EMPNO, ENAME, JOB, MGR, HIREDATE,
SAL, COMM, DEPTNO, ACCOUNTNUMBER, MOBILENUMBER)
Values
(7902, 'FORD', 'ANALYST', 7566, TO_DATE('12/03/1981 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
3000, NULL, 20, '654333', '8897136055');
Insert into TEST.MUL_TEST
(EMPNO, ENAME, JOB, MGR, HIREDATE,
SAL, COMM, DEPTNO, ACCOUNTNUMBER, MOBILENUMBER)
Values
(7934, 'MILLER', 'CLERK', 7782, TO_DATE('01/23/1982 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
1300, NULL, 10, '654334', '8897136056');
Insert into TEST.MUL_TEST
(EMPNO, ENAME, JOB, MGR, HIREDATE,
SAL, COMM, DEPTNO, ACCOUNTNUMBER, MOBILENUMBER)
Values
(7499, 'ALLEN', 'SALESMAN', 7698, TO_DATE('02/20/1981 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
1600, 300, 30, '123457', '8897136044');
Insert into TEST.MUL_TEST
(EMPNO, ENAME, JOB, MGR, HIREDATE,
SAL, COMM, DEPTNO, ACCOUNTNUMBER, MOBILENUMBER)
Values
(7521, 'WARD', 'SALESMAN', 7698, TO_DATE('02/22/1981 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
1250, 500, 30, '123458', '8897136045');
Insert into TEST.MUL_TEST
(EMPNO, ENAME, JOB, MGR, HIREDATE,
SAL, COMM, DEPTNO, ACCOUNTNUMBER, MOBILENUMBER)
Values
(7654, 'MARTIN', 'SALESMAN', 7698, TO_DATE('09/28/1981 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
1250, 1400, 30, '1', '9440320402');
Insert into TEST.MUL_TEST
(EMPNO, ENAME, JOB, MGR, HIREDATE,
SAL, COMM, DEPTNO, ACCOUNTNUMBER, MOBILENUMBER)
Values
(7698, 'BLAKE', 'MANAGER', 7839, TO_DATE('05/01/1981 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
2850, NULL, 30, '2', '9440320403');
Insert into TEST.MUL_TEST
(EMPNO, ENAME, JOB, MGR, HIREDATE,
SAL, COMM, DEPTNO, ACCOUNTNUMBER, MOBILENUMBER)
Values
(7844, 'TURNER', 'SALESMAN', 7698, TO_DATE('09/08/1981 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
1500, 0, 30, '3', '9440320404');
Insert into TEST.MUL_TEST
(EMPNO, ENAME, JOB, MGR, HIREDATE,
SAL, COMM, DEPTNO, ACCOUNTNUMBER, MOBILENUMBER)
Values
(7900, 'CLERK', 'CLERK', 7698, TO_DATE('12/03/1981 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
950, NULL, 30, '4', '9440320405');
Insert into TEST.MUL_TEST
(EMPNO, ENAME, JOB, MGR, HIREDATE,
SAL, COMM, DEPTNO, ACCOUNTNUMBER, MOBILENUMBER)
Values
(7499, 'ALLEN', 'SALESMAN', 7698, TO_DATE('02/20/1981 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
1600, 300, 30, '5', '9440320406');
Insert into TEST.MUL_TEST
(EMPNO, ENAME, JOB, MGR, HIREDATE,
SAL, COMM, DEPTNO, ACCOUNTNUMBER, MOBILENUMBER)
Values
(7521, 'WARD', 'SALESMAN', 7698, TO_DATE('02/22/1981 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
1250, 500, 30, '6', '9440320407');
Insert into TEST.MUL_TEST
(EMPNO, ENAME, JOB, MGR, HIREDATE,
SAL, COMM, DEPTNO, ACCOUNTNUMBER, MOBILENUMBER)
Values
(7654, 'MARTIN', 'SALESMAN', 7698, TO_DATE('09/28/1981 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
1250, 1400, 30, '7', '9440320408');
Insert into TEST.MUL_TEST
(EMPNO, ENAME, JOB, MGR, HIREDATE,
SAL, COMM, DEPTNO, ACCOUNTNUMBER, MOBILENUMBER)
Values
(7698, 'BLAKE', 'MANAGER', 7839, TO_DATE('05/01/1981 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
2850, NULL, 30, '8', '9440320409');
Insert into TEST.MUL_TEST
(EMPNO, ENAME, JOB, MGR, HIREDATE,
SAL, COMM, DEPTNO, ACCOUNTNUMBER, MOBILENUMBER)
Values
(7844, 'TURNER', 'SALESMAN', 7698, TO_DATE('09/08/1981 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
1500, 0, 30, '8', '9440320410');
Insert into TEST.MUL_TEST
(EMPNO, ENAME, JOB, MGR, HIREDATE,
SAL, COMM, DEPTNO, ACCOUNTNUMBER, MOBILENUMBER)
Values
(7900, 'CLERK', 'CLERK', 7698, TO_DATE('12/03/1981 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
950, NULL, 30, '9', '9440320411');
COMMIT;
REG TABLE:
Insert into TEST.REG
(EMPNO, ENAME, JOB, MGR, HIREDATE,
SAL, COMM, DEPTNO, ACCOUNTNUMBER, MOBILENUMBER)
Values
(7369, 'SMITH', 'CLERK', 7902, TO_DATE('12/17/1980 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
800, NULL, 20, '123456', '8897136043');
Insert into TEST.REG
(EMPNO, ENAME, JOB, MGR, HIREDATE,
SAL, COMM, DEPTNO, ACCOUNTNUMBER, MOBILENUMBER)
Values
(7499, 'ALLEN', 'SALESMAN', 7698, TO_DATE('02/20/1981 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
1600, 300, 30, '123457', '8897136044');
Insert into TEST.REG
(EMPNO, ENAME, JOB, MGR, HIREDATE,
SAL, COMM, DEPTNO, ACCOUNTNUMBER, MOBILENUMBER)
Values
(7521, 'WARD', 'SALESMAN', 7698, TO_DATE('02/22/1981 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
1250, 500, 30, '123458', '8897136045');
Insert into TEST.REG
(EMPNO, ENAME, JOB, MGR, HIREDATE,
SAL, COMM, DEPTNO, ACCOUNTNUMBER, MOBILENUMBER)
Values
(7566, 'JONES', 'MANAGER', 7839, TO_DATE('04/02/1981 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
2975, NULL, 20, '123460', '8897136046');
Insert into TEST.REG
(EMPNO, ENAME, JOB, MGR, HIREDATE,
SAL, COMM, DEPTNO, ACCOUNTNUMBER, MOBILENUMBER)
Values
(7654, 'MARTIN', 'SALESMAN', 7698, TO_DATE('09/28/1981 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
1250, 1400, 30, '123461', '8897136047');
Insert into TEST.REG
(EMPNO, ENAME, JOB, MGR, HIREDATE,
SAL, COMM, DEPTNO, ACCOUNTNUMBER, MOBILENUMBER)
Values
(7698, 'BLAKE', 'MANAGER', 7839, TO_DATE('05/01/1981 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
2850, NULL, 30, '123462', '8897136048');
Insert into TEST.REG
(EMPNO, ENAME, JOB, MGR, HIREDATE,
SAL, COMM, DEPTNO, ACCOUNTNUMBER, MOBILENUMBER)
Values
(7782, 'CLARK', 'MANAGER', 7839, TO_DATE('06/09/1981 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
2450, NULL, 10, '123463', '8897136049');
Insert into TEST.REG
(EMPNO, ENAME, JOB, MGR, HIREDATE,
SAL, COMM, DEPTNO, ACCOUNTNUMBER, MOBILENUMBER)
Values
(7788, 'SCOTT', 'ANALYST', 7566, TO_DATE('12/09/1982 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
3000, NULL, 20, '123464', '8897136050');
Insert into TEST.REG
(EMPNO, ENAME, JOB, MGR, HIREDATE,
SAL, COMM, DEPTNO, ACCOUNTNUMBER, MOBILENUMBER)
Values
(7839, 'KING', 'PRESIDENT', NULL, TO_DATE('11/17/1981 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
5000, NULL, 10, '123465', '8897136051');
Insert into TEST.REG
(EMPNO, ENAME, JOB, MGR, HIREDATE,
SAL, COMM, DEPTNO, ACCOUNTNUMBER, MOBILENUMBER)
Values
(7844, 'TURNER', 'SALESMAN', 7698, TO_DATE('09/08/1981 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
1500, 0, 30, '123466', '8897136052');
Insert into TEST.REG
(EMPNO, ENAME, JOB, MGR, HIREDATE,
SAL, COMM, DEPTNO, ACCOUNTNUMBER, MOBILENUMBER)
Values
(7876, 'ADAMS', 'CLERK', 7788, TO_DATE('01/12/1983 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
1100, NULL, 20, '123467', '8897136053');
Insert into TEST.REG
(EMPNO, ENAME, JOB, MGR, HIREDATE,
SAL, COMM, DEPTNO, ACCOUNTNUMBER, MOBILENUMBER)
Values
(7900, 'CLERK', 'CLERK', 7698, TO_DATE('12/03/1981 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
950, NULL, 30, '123468', '8897136054');
Insert into TEST.REG
(EMPNO, ENAME, JOB, MGR, HIREDATE,
SAL, COMM, DEPTNO, ACCOUNTNUMBER, MOBILENUMBER)
Values
(7902, 'FORD', 'ANALYST', 7566, TO_DATE('12/03/1981 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
3000, NULL, 20, '123469', '8897136055');
Insert into TEST.REG
(EMPNO, ENAME, JOB, MGR, HIREDATE,
SAL, COMM, DEPTNO, ACCOUNTNUMBER, MOBILENUMBER)
Values
(7934, 'MILLER', 'CLERK', 7782, TO_DATE('01/23/1982 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
1300, NULL, 10, '123470', '8897136056');
COMMIT;
TRIGGER CREATED BY ME:
CREATE OR REPLACE TRIGGER TEST AFTER DELETE ON MUL_TEST
CALL Test_Nagendra
CREATE TABLE TEST.MUL_TEST
EMPNO NUMBER(4),
ENAME VARCHAR2(10 BYTE),
JOB VARCHAR2(9 BYTE),
MGR NUMBER(4),
HIREDATE DATE,
SAL NUMBER(7,2),
COMM NUMBER(7,2),
DEPTNO NUMBER(2),
ACCOUNTNUMBER VARCHAR2(20 BYTE),
MOBILENUMBER VARCHAR2(20 BYTE)
CREATE TABLE TEST.REG
EMPNO NUMBER(4) NOT NULL,
ENAME VARCHAR2(10 BYTE),
JOB VARCHAR2(9 BYTE),
MGR NUMBER(4),
HIREDATE DATE,
SAL NUMBER(7,2),
COMM NUMBER(7,2),
DEPTNO NUMBER(2),
ACCOUNTNUMBER VARCHAR2(20 BYTE),
MOBILENUMBER VARCHAR2(20 BYTE)
CREATE TABLE TEST.EMAILINFO
MESSAGE VARCHAR2(1000 BYTE)
);

914547 wrote:
2 )FOR THAT DELETED RECORD IN THAT PROCEDURE FIRST IT SHOULD HAVE TO CHECK FOR ACCOUNTNO IN MUL_TEST TABLE WITH ACCOUNTNO IN REG TABLE (THE DELETED RECORD ONLY) IF IT IS THERE THEN NO ISSUE IF IT IS NOT THERE THEN IT HAS TO CHECK FOR MOBILE NUMBER IN MUL_TEST WITH REG TABLE IF IT IS ALSO NOT THERE THEN THAT PARTICULAR deleted RECORD HAVE TO BE INSERTED IN EMAILINFO TABLE(MESSAGE COLUMN) GIVEN BELOW Isn't that just an "on delete cascade" ?

Similar Messages

To restrict Issue for production than planned qty in production order

Hi Experts,
In my scenario, the production staff will prepare production order and right click in production order document and select "Issue Components" option to Issue raw materials for production floor. After issuing the raw materials to production floor closes the "Issue for Production" document and now we have "Production Order" document open in screen. When he again select "Issue Components" option and issues the raw materials once again. Materials are issued once again wrongly. This happens since the production order document is not getting refresh after "Issue for Production" document is done.
Is there any way to restrict issue of raw materials than the planned qty.?
I have tried lot of ways to restrict this through SP. Please revert me an solution to this issue.
The procedure should trigger immediately when the "Issue Components" option is selected second time (If the raw materials are issued in full in first time itself). And it should allow only the qty which is to issued to production order qty (if they issue part issue to production order)
Thanks in advance
Raja.S

Hi Neetu,
Thanks for your quick response. I have tried this query. But it is not blocking the issue for production document even the raw materials are issued already for the production order.
I'll explain my work flow again. The Production staff will prepare production order and then release the same and update the production order after changing the status for "Release". Then he will right click the Mouse button and select "Issue Components" option and perform the Issue for Production process. He will issue the required raw material completely in one shot and add the Issue for Production document.
After adding the Issue for Production document he will close that document and now we will be in Production order document. Now our production order document will not get refreshed. Now the Production staff go for "Issue components" option, then it should not allow him to issue the components once again. But it is allowing him to issue components any number of times. there is no control.
If we browse the production order document to previous record and browse back to the same record then my Production order document get refreshed and now we can control the issue. But what should i do to control in the earlier case. Since they want to perfrom lot of production order, there is a chance to issue components for same production order more than one time before the production order document get refreshed.
Please provide me the SP to control this scenario.
Thanks in advance.
Raja.S

Print layout - Goods issue & Issue for Production

I designed two print layouts separately 1 in Goods issue for Goods issue in inventory module
and 1 in Issue for production for Issue for production in production module.
If i take a print preview or print in Issue for production , it will reflects the print layout designed in Goods issue.
regards
kavitha S

Hi Kavitha,
I think, are you duplicate the Goods issue PLD Template to Issue for Production PLD Template on Duplicate Layout Template.
Best, Try to create a New PLD from Issue for Production(System) PLD.
Regards,
Madhan.

Report issue in Production

Hi Experts,
I got an issue in production that it should trigger mails daily once. But this program is triggering for every hour,where to look it pls how to debug this issue?can this FM can check?
call function 'DURATION_DETERMINE'
    importing
      duration                   = lv_duration
    changing
      start_date                 = ls_history-datum
      start_time                 = ls_history-uzeit
      end_date                   = p_datum
      end_time                   = p_uzeit
    exceptions
      factory_calendar_not_found = 1
      date_out_of_calendar_range = 2
      date_not_valid             = 3
      unit_conversion_error      = 4
      si_unit_missing            = 5
      parameters_not_valid       = 6
      others                     = 7.
if sy-subrc <> 0.
Thanks

Hi ,
Youi can check this tables
                    MKPF               material document
     MSEG               material document (item level)
                    RESB                                Material reservations
     RKPF                                 header
Rergards
SANIL

Good issue to Production order - Allows it in back posting date

Dear all,
Good issue to Production order ( 261 Movement ), allows us to post the component in back dated eventhough stock is not avaible on that date.
Example - Component stock on date 10.02.2010 = Zero , I made it Good receipt on date 18.02.2010 and now stock is available on date 18.02.2010.
Now GI to Production it allows the qty on current and back Posting date also , I want control on date with error message. It should not allowed the GI for back date from 18.02.2010.
Because of this our MB5B report shows the negetive issue qty if i post in back date.
Waiting for reply
Thanks and Regards,
Saurabh

Hi SAurabh,
PLease check whether Negative Stock is allowed for the valuation Area (plant).
GOTO >> SPRO >> MM>> Invetnroy management and physical inventory >> Goods issue/ Transfer Posting >> Allow Negative stock.
Untick the Negative stock allowed for your valuation area (PLant)
Regards,
Pravin

Error while adding the issue for production (item cost not found)

Hi all,
The scenario is,
when the user is trying to add the issue for production system is showing error item cost not
found.The item which is issued is Inventory + purchase item with manual issue method.The valuation
method for that item is FIFO.since the valuation method is FIFO,error related to item cost should
not occur.
Since the valuation method is FIFO.Item cost error should not occur.
The error related to item cost must not occur at the time of issue for production.
Regards-
Mona.

Hi!
Please check these threads
Sales Delivery Document
Item Cost Error
No item cost was found

Error While Updating Issue For Production

Hi,
        When i am trying to update an UDF in issue for production i am getting the following error message.
Item is Not a Component to the Referenced work order[Goods Issue - Object Type] Message 3560 -5

Dear Manikandan K,
Regarding the message we can tell you that the error message
"Item is not a component of the referenced Work Order" usually appears
because there is a case sensitive problem between the item code given
in the BOM and the item code given in the item master data.
Please check if the item codes of the BOM are exactly the same as the
codes given in the item master data. There should not be any differences
between spelling of the codes (for example item code in the item master
data is with capital letters X00014447 while the item code in the BOM
is with normal letters x00014447).
In case you find item with this issue please correct its item code
in the BOM manually so it will be exactly identical with the code given
in the item master data.
Regards,
Marcella Rivi
SAP Business One Forums Team

Error while doing Good Issue for Production Order using BAPI

Hi All,
I am facing an error like 'u2018Content of order 1011907: MDT218AJ10 transferred to interface (IMSEG): T-86410-71".
I have written the code as below. Please let me know what is missing when using the BAPI 'BAPI_GOODSMVT_CREATE'. What is the cause of this error ?
*Action in Transaction (GM_CODE)
*GM Code for Goods Issue for Production Order is 03
gs_gmcode-gm_code = '03'.
*Header Data
*Posting date
gs_header-pstng_date = sy-datum.
*Document date
gs_header-doc_date   = sy-datum.
*Item Data
*Material
gs_item-material = zptp_s_rf_migo_261-matnr1.
*Movement Type
gs_item-move_type = '261'.
*Movement Indicator
gs_item-mvt_ind   = 'F'.
*Stock Type
gs_item-stck_type = 'F'.
*Plant
gs_item-plant     = gv_plant.
*Storage Location
gs_item-stge_loc = gv_str_loc.
*Quantity
gs_item-entry_qnt = zptp_s_rf_migo_261-menge2.
*Unit
gs_item-entry_uom = gv_uom.
*ISO code for unit of measurement
gs_item-entry_uom_iso = gv_uom.
*Order Number
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
    EXPORTING
      input = zptp_s_rf_migo_261-aufnr
    IMPORTING
      output = gs_item-orderid.
*Reservation Number
gs_item-reserv_no = gv_resv_num.
*Reservation Item
gs_item-res_item = gv_resv_itm.
*Reservation Type
gs_item-res_type = gv_resv_type.
APPEND gs_item TO gt_item.
Calling BAPI_GOODSMVT_CREATE to create the Material Document Number
CALL FUNCTION 'BAPI_GOODSMVT_CREATE'
    EXPORTING
      goodsmvt_header       = gs_header
      goodsmvt_code         = gs_gmcode
    IMPORTING
      goodsmvt_headret      = gs_headret
    TABLES
      goodsmvt_item         = gt_item
      goodsmvt_serialnumber = gt_serial
      return                = gt_return.
Thanks in Advance.

hi,
did you look at message ?
System says, there are differences between the interface data and the order data. It can be anything. I think you should check
data in the interface .
this is the long explanation of your message :
Diagnosis
When calling the function module MB_CREATE_GOODS_MOVEMENT or the BAPI GoodsMovement.CreateFromData (BAPI_GOODSMVT_CREATE) to post a goods receipt for a production order, there are differences between the interface data and the order data.
Example: The order was created for plant 0001, but plant 0002 is passed on in the interface.
The system checks this for the material and the order item.
System response
Due to this difference, the system cannot post the goods receipt.
Procedure
Check the data in the interface (IMSEG-WERKS, IMSEG-AUFNR). If necessary, correct the plant or the order number in the interface.
<< Moderator message - Point begging removed >>
Edited by: Rob Burbank on Feb 6, 2012 11:24 AM

Goods Issue from Production Order in SAP

Dear experts,
I faced one issue not yet solve is that my customer created the production order
then already issue for production for all quantities of child item .
Example:
Production OrderItem A
Item A1 = 2 Qty
Item A2 = 2 Qty
Item A3 = 2 Qty
Issue for Production Item A
Item A1 = 2 Qty
Item A2 = 2 Qty
Item A3 = 2 Qty
But later on, my customer found out that 1 Qty of Item A1 already damaged.
So they want to issue one more Qty of Item A1 instead of one that already damaged.
How can I issue one more Qty for this item?
Please your advices are necessary for me.
Best regard,
Borey

Hello Borey,
Solutions may depend upon the way you want to book the cost for the damaged part A1.
     (a) If you want to book the cost to the production order itself (production order is a cost object), manually book consumption for another quantity using MB1A, 261 movement (you will have to mention the production order during posting this consumption).
     (b) If you do not want to book higher cost to that production order, you can:
           1. Extract damaged quantity of A1 from that production order using MB1A 262 movement.
           2. Create a manual QM lot and after rejection, move that damaged quantity to blocked stock.
           3. You can scrap or rework from that blocked quantity later.
           4. Issue another quantity of A1 from unrestricted stock to that production order using MB1A                261 movement.
Hope I could help you.
Best Regards.
Rajen

ABAP Error:Illegal interruption of the event LOAD-OF-PROGRAM (in MIGO-Goods issue to Production)

Hi Experts,
while i am doing MIGO(Goods Issue to Production Order, I am getting the below ABAP Error:
Please give solution, It is urgent requirement.
THE ERROR IS:
Short text
     Illegal interruption of the event LOAD-OF-PROGRAM.
What happened?
     Error in the ABAP Application Program
     The current ABAP program "/MRSS/SAPLRAP_INT_OB" had to be terminated because it
      has come across a statement that unfortunately cannot be executed.
Error analysis
     During the flow of the event LOAD-OF-PROGRAM (event for the
     initialization of an ABAP program), a condition occurred under which
     the event was to be left early. This is not permitted as it would
     result in an inconsistent status in the ABAP program.
Trigger Location of Runtime Error
    Program /MRSS/SAPLRAP_INT_OB
    Include /MRSS/LRAP_INT_OBF00
    Row                                     34
    Module type                             (FORM)
    Module Name                             GLOBAL_INIT
Source Code Extract
Line SourceCde
    4
    5 *&---------------------------------------------------------------------*
    6 *&      Form global_init
    7 *&---------------------------------------------------------------------*
    8 *       text
    9 *----------------------------------------------------------------------*
   10 FORM global_init.
   11
   12 * local data
   13   DATA lv_badi_impl_exists TYPE flag.
   14
   15
   16 * get ref to BAdIs
   17   CALL METHOD cl_exithandler=>get_instance "#EC CI_BADI_GETINST
   18     CHANGING
   19       instance = gv_ref_badi_inter_company.
   20 * CALL METHOD cl_exithandler=>get_instance
   21 * CHANGING
   22 *      instance = gv_ref_badi_rap_back.
   23 * CALL METHOD cl_exithandler=>get_instance
   24 *    CHANGING
   25 *      instance = gv_ref_badi_ps_int.
   26   CALL METHOD cl_exithandler=>get_instance "#EC CI_BADI_GETINST

Hi Rob thanks for your response. I thought about doing an OSS note however; I would think I would need to get the problem in config corrected first as it contradicts each other. The problem I am talking about is how they are to return material to vendor....I have never even seen this as a process in my 10 years....
Process.....when the PO is a return to vendor PO they go to migo and choose the goods receipt and mvmt type 101 and the system will default the 161 in the item level....the two are inconsistent. If I try to change the top level to a 161 mvmt (as this is what I am used to seeing) it gives the error that the PO is not a stock transport order... Would you agree that I should correct that problem first before creating an OSS note?

Issue from Production !!!!!!!!!!!!!!

Hi Everyone !!!!!!
Actually i had made Production Order Form in which i can populate all the Production order with respect to BOM (Bill of Material).
Now i want to Populate Specific Production Order Number another form which is "Issued for Prouction " Basically Now i want to developed another form which can be worked Like Issue from Production Screen.
For this i have to use Production Order Object in SAP based....
Could anybody have sample code for this .......that would be really helpful for me,
The Main Problem is that i do not know how it will start ? how can i get the Production Order as well as their Item List.....and how can i issued Production Order in Issue from Production Form.....
could you guide me that where should i have to start ........
Thanks
Regards..
Rizwan

hello
Check the following thread:
Regards
János

How to get material's last posting date of issuing to production order?

Hi,
In my scenario, I need to get material's last posting date of issuing to production order (e.g. mov. typ. 261).
I tried to select the material documents whose movement type is 261, and restrict the posting date from month to month each time, until the first material document is selected.
But this method seems quite inefficient.
What kind of algorithm is more effient to do this?
Thanks
Wesley

Hi,
select max( budat )
from mkpf
into gv_budat
where mblnr in ( select mblnr
                     from aufm
                    where aufnr = gv_aufnr "(Prod. Order)
                        and matnr = gv_matnr "(Issued Material)
                        and bwart = '261' ).
Edited by: Azeem Ahmed Matte on Mar 12, 2010 12:33 PM

How to show returned components on Issue for Production on a query.

Hi Guru's,
Is there a way to show the items that have been returned (Return Components) on Issue for Production using a query?
Thanks and Regards,
Christian

Hi,
1. Create row level UDF for issue from production order.
2. Assign below FMS to this UDF and set it auto refresh based on quantity.
SELECT T0.[Quantity] FROM IGN1 T0 WHERE T0.[BaseRef] = $[$13.61.number] and T0.[ItemCode] = $[$13.1.0]
Thanks & Regards,
Nagarajan

Issue for Production

We are getting the following error when we use the "Issue for Production" form
"StoreDocData: 0 : The Loged on User does not have permission to use the object"
Is there an authorization I have missed?
Thanks,
Rob

Hi,
Please check if you are using any add-on and the user has relevant permission.
Also please check the code if any, given in SP_Transaction Notificication.
Regards
VIkas
SAP Business One Forums Team.

Issue in Production for Workflow not getting Triggered .

Hi Guys,
I have a workflow, which is properly triggering in the development and Quality but not getting triggered in the Production. Can't get the Exaact reason because by using T-code PFTC when i test the workflow independantly its working properly and even BOR does not have any problem. Please Help me guys as this is a issue in Production.
The workflow is a customized one, It getting triggered throught the funtion call in User Exit of MM01.
Thanks

It getting triggered throught the funtion call in User Exit of MM01.
1. I hope the workflow customization is done properly in production system, as you stated that if you are trying to trigger from PFTC then it is working fine, can you please try to Refresh Organizational Environment from SBWP ---> On MEnu ---> Settings --> Workflow Settings ---> Refresh Organizational Environment and secondly try to refresh the buffer from txn SWU_OBUF
2. Make sure the user exit is transported to Production.
3. Check the workflow log from the txn SWIA if you have proper authorizations for the userid.

Customer adopted parts to be issued in production line

Dear Experts,
I need some help for this scenario. Customer will provide a part to assemble in the main production line. Business will have to mainatain that material & issue to production order. How to handle this. Like is there any movement type from SD for handling customer adopted parts. Please suggest.

Check this thread
[Re: how to manage customer supplied materials in SAP |Re: how to manage customer supplied materials in SAP;
thanks
G. Lakshmipathi

Issue in production

Similar Messages

Maybe you are looking for