You are on page 1of 4

Application Display Name : Request Channel Partner

Foams Location : --
\\citrix\Greatplus\INDIA\SHEELA_ERP\C_MASTER\

The forms name which are using in this process are :-

1. Request Channel partner  REQ_CHAN.fmb


2. Request mail.  REQ_EMAIL.fmb
3. Channel partner  Cchnlptr.fmb
4. Closed email.  REQ_CMAIL.fmb

The database which are using in this process are :-

1. DB01.
2. Webdb.

The schema which are using in this process are:-

1. erp_centeral.  erp_centeral / erp_centeral@db01.


2. erp_summary  erp_summary / erp_summary@webdb.

The table name which are using in this process are:-

1. ERP_CENTERAL.REQUEST_CHANNEL_PARTNER.
2. ERP_CENTERAL.REQUEST_CHANNEL_PARTNER_DTL.
3. ERP_SUMMARY.REQUEST_EMAIL_TRANSACTIONS.

The structures of the tables are:-

1. ERP_CENTERAL.REQUEST_CHANNEL_PARTNER:-

create table ERP_CENTERAL.REQUEST_CHANNEL_PARTNER


(
PTY_NAME VARCHAR2(50) not null,
SHORT_NM VARCHAR2(10),
CATEGORY VARCHAR2(50),
CHANNEL_PARTNER_GROUP VARCHAR2(50),
TERRITORY_ALLOWED VARCHAR2(50),
ADDRESS1 VARCHAR2(33),
ADDRESS2 VARCHAR2(32),
ADDRESS3 VARCHAR2(32),
ADDRESS VARCHAR2(100),
CITY VARCHAR2(30),
PIN_CD VARCHAR2(10),
STATE VARCHAR2(25),
COUNTRY VARCHAR2(25),
PHONE VARCHAR2(40),
FAX VARCHAR2(40),
EMAIL VARCHAR2(40),
WEBSITE VARCHAR2(100),
LED_NAME VARCHAR2(50),
EXCISE_COMM_RATE VARCHAR2(40),
EXCISE_RANGE VARCHAR2(40),
EXCISE_DIVISION VARCHAR2(40),
EXCISE_DVN_ADR VARCHAR2(40),
EXCISE_ECC_NO VARCHAR2(40),
EXCISE_CERC_NO VARCHAR2(40),
EXCISE_PLA_NO VARCHAR2(40),
PAN_NO VARCHAR2(25),
CST_NO VARCHAR2(30),
LST_NO VARCHAR2(30),
REMARK VARCHAR2(1000),
INSERTED_BY VARCHAR2(50),
INSERTED_DATE DATE,
UPDATED_BY VARCHAR2(50),
UPDATED_DATE DATE,
LAST_MODIFIED_BY VARCHAR2(50),
LAST_MODIFIED_ON DATE,
LAST_MODIFIED_REMARK VARCHAR2(1000),
ZONE VARCHAR2(8),
ACTIVE VARCHAR2(1),
TAX_FORM VARCHAR2(10),
COMPANY_UNIT_CODE VARCHAR2(100),
ACCEPTED_BY VARCHAR2(50),
EMAIL_SENT VARCHAR2(50)
)
constraints:-

Alter table ERP_CENTERAL.REQUEST_CHANNEL_PARTNER


add constraint PK_REQ_CHANNEL_PARTNER primary key (PTY_NAME).

2. ERP_CENTERAL.REQUEST_CHANNEL_PARTNER_DTL:-

create table ERP_CENTERAL.REQUEST_CHANNEL_PARTNER_DTL


(
PTY_NAME VARCHAR2(50) not null,
COMPANY_UNIT_CODE VARCHAR2(7) not null,
TAX_FORM VARCHAR2(10),
FREIGHT_TYPE VARCHAR2(15)
)

Constraints:-

Alter table ERP_CENTERAL.REQUEST_CHANNEL_PARTNER_DTL


add constraint PK_REQUEST_CHANNEL_PARTNER_DTL primary key(PTY_NAME,COMPANY_UNIT_CODE)

Alter table ERP_CENTERAL.REQUEST_CHANNEL_PARTNER_DTL


add constraint FK_REQ_CHANNEL_PARTNER_DTL foreign key (PTY_NAME)
references ERP_CENTERAL.REQUEST_CHANNEL_PARTNER (PTY_NAME) on delete cascade;

3. ERP_SUMMARY.REQUEST_EMAIL_TRANSACTIONS:-

create table ERP_SUMMARY.REQUEST_EMAIL_TRANSACTIONS


(
TRANSACTION_DATE DATE default sysdate,
FROM_NAME VARCHAR2(500),
TO_NAMES VARCHAR2(500),
SUBJECT VARCHAR2(500),
STATUS VARCHAR2(50),
CLOSED_STATUS VARCHAR2(50),
PTY_NAME VARCHAR2(50),
ITEM_NAME VARCHAR2(50)
)

Brief Description of Request Channel partner master:-

1. Users enter the request for open the channel partner from Request channel Partner.
2. One mail goes to User as Acknowledgement that his request has been submitted successfully.
3. Other mail goes to IT Services and Mr.kuldeep Singh mail id.
4. When Channel partner is submitted finally in ERP for transactions one final mail goes to the user that his
request has been accepted by the IT Department.
DATA FLOW DIAGRAM
USER R.C.P MAIL

Mail to IT

Mail
R.C.P R.C.P Dtl
Mail to User

C.P Mail Closed Mail


to User

C.P C.P.Dtl