Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Author:
Creation Date: March 7, 2017
Last Updated: September 15, 2017
Document Ref:
Version: DRAFT 1A
MD.050 Application Extensions Functional Design Doc Ref:
September 15, 2017
Document Control
Change Record
1
Reviewers
Name Position
Distribution
2
3
4
Note To Holders:
If you receive an electronic copy of this document and print it out, please write your
name on the equivalent of the cover page, for document control purposes.
If you receive a hard copy of this document, please write your name on the front cover,
for document control purposes.
Contents
Document Control...................................................................................................................2
Topical Essay............................................................................................................................4
Business Summary............................................................................................................4
User Procedures................................................................................................................4
Form and Report Descriptions..............................................................................................6
Dealer Portal Master Table Integration Process..........................................................6
Dealer Portal Sales Order Interface Process.................................................................7
CIPL Portal Order Tax Updation...................................................................................8
Pre-Requisites...........................................................................................................................9
Pre-Requisites .9
Open and Closed Issues for this Deliverable....................................................................11
Open Issues......................................................................................................................11
Closed Issues...................................................................................................................11
User Procedures
Below is the detailed step by step process for Sale through PEP.
1. Before proceeding to any transaction in PEP the Tax Master and Customer
Master need to interface from Oracle Master to PEP. Program Name Dealer
Portal Master Table Integration Process should run in Oracle to interface the
Oracle Tax Master, Item Master and Customer to the PEP system.
2. Tax team maps the tax defaultation by combining the Item, Ship from and ship
to location with Tax Category.
3. Partners create the Order in PEP for purchasing goods from CIPL. Tax
defaultation will be applicable once PEP user selects the Item, Ship from and
ship to from list of values in PEP.
Doc Ref:
5. For Sales Order creation in Oracle order Management, the Portal Order Import
request set program runs in Oracle system to import the information captured
in the interface tables to Oracle Base tables along with tax details.
6. Portal Order Import request set contains the following child programs.
7. Sales order created from import process requires validation which is done by
the finance team. The report name Orders on Credit Check Hold Report
(CSV)/text runs to validate the sales orders pending for booking and requires
release hold. Once credit hold team release Sales Order, then sales order is
booked by the same team. Staus update information of the sales order will
revert back to PEP by program name Dealer Portal Sales Order Status Interface
Process via interface.
8. Now pick release and ship confirm process is done by the logistics team and
goods are delivered to the partner. For validation of the sales orders which are
booked but Awaiting shipping or booked but on hold will be done by running
the report name CANON Pending Orders Reports.
10. To validate the sales Invoice with taxes, tax team uses report name MIS Sales
Day Book Report from Oracle which provides all the required details of taxes.
11. After invoice creation VAT state Invoice Print Report runs to generate
Customer Invoice which includes HSN code wise Amount with tax details.
12. For tax payment user refer Sales Day Book Report for cross verification.
The program interfaces the Oracle Tax Master, Customer master and Item Master to the
PEP system.
The tables from where the Tax master details are pulling from Oracle will be change as
per GST requirement.
The tax master details are flowing to PEP from Oracle and Tax defaultation is setup in
the PEP by combining the Item and Ship from location.
Below is the list of Tax columns flowing to PEP from Oracle Master.
Tax ID
Tax Name
Tax Desription
Tax Type
Percentage
Tax Amount
Proposed Changes:
The Tax Category will be maintained in the PEP system which will interfaced from
Oracle Master to PEP system. Tax Category defaultation should be on the basis of Item
(HSN Code), Ship from (Canon Warehouse) and Ship to (Customer) Location.
Below is the list of tax details should flow to PEP system from Oracle Master:
Tax Category Name Capture the Category name from Category table.
Tax Type - Capture Tax type from Tax Rate table and tax type table.
As Tax category is the combination of the Tax Rates defined in the Oracle system which
will be same interfaced to the PEP system.
The Logic in PEP should be in such a way that, once they select the Item, Ship From and
Ship to location, the Tax Category should picked up by default in the line of Purchase
order.
For Example:
Below are the columns with data need to flow from Oracle Master Table to PEP system
Tax Category Name Tax Tax Category Tax Name Tax Tax Tax Tax Tax
Category Description ID Description Percentage Amount Type
ID
On the basis of the above data, tax team map the tax with Item, Ship from and Ship to
Location.
The Program runs in the Oracle system, transfers the PEP transactions (Purchse Order)
to Oracle standard oe_interface table and associated tax details to custom interface
table.
There are two separate tables which are used to store the data from PEP to import in
Oracle.
Oracle standard interface table In which the Sales order details are captured
before import in Oracle base tables. The data captured in this table does not
contain any tax details.
Custom Tax Table In which all the tax details entered during the PO creation
by PEP user will be captured w.r.t to the Transaction ID.
Proposed Changes:
Program logic of transferring tax detail to custom Tax table will change as per GST
requirement. New fields need to be added for GST taxes.
The Tax Category ID will flow with Tax Rate ID w.r.t the Transaction ID in Custom Tax
Table.
For Example: The transaction ID xyz is created in PEP by creating a Purchase Order
with default tax category SGST@8%+CGST@8%. Below are the detailswhich should be
captured in the Custom Tax Table w.r.t Transaction ID.
Transaction ID Tax Category ID Tax ID Tax Rate Tax Amount Tax Type
The program is used to interface the tax details from Custom Tax table to base tax
tables. The program triggers once the Sales Order created in the Oracle with Transaction
ID.
The Tax ID stored in the Custom Tax Table will interface into Base Tax Table w.r.t to the
transaction ID of Sales Order created in Oracle Order Management.
Proposed Changes:
The Tax Category ID will flow with the Tax Rate ID in the Base Tax tables which are
changed as per GST requirement.
Below is the list of the columns flow in the Base Tax Table:
Tax Category
CGST ID
SGST ID
IGST ID
Tax Category ID will match with the Oracle Tax Master Category ID and same is
applied to the respective transaction in India Local Tax detail form.
Prerequisites
1. Tax Regime
2. Tax Type
3. Tax Name
4. Tax Categories
Open Issues
Closed Issues