Vous êtes sur la page 1sur 11

# Activity Activity Owner Task# Sub-Task# Sub-Sub-

Task#

1 Customer Creation ERP Finance Team 1.1


ERP Team 1.2
API Proxy 1.3

2 Customer Deactivation ERP Finance Team 2.1


ERP Team 2.2
API Proxy 2.3

3 Prepaid Product Payment Portal 3.1


Suscription
-ACTIVATION FLOW
ERP Team 3.2

ERP Team 3.3

API Proxy 3.4 3.4.1

ERP Team 3.4.2 3.4.2.1

ERP Team 3.4.2.2


ERP Team 3.4.2.3
ERP Team 3.4.2.4
3.4.2.5
ERP Team 3.4.3

4 Prepaid Product ERP Team 4.1


Suscription
-DEACTIVATION
FLOW
ERP Team 4.2

API Proxy 4.3

ERP Team 4.3.1


ERP Team 4.3.2 4.3.2.1
ERP Team 4.3.2.2
5 Postpaid Product Payment Portal 5.1
Suscription
-ACTIVATION FLOW
ERP Team 5.2

ERP Team 5.3


ERP Team 5.4

ERP Team 5.5

API Proxy 5.6

ERP Team 5.6.1


ERP Team 5.6.2

6 Postpaid Month-End API Proxy 6.1


Processing Flow for
New/Old Customer
ERP Team 6.2

ERP Team 6.3


ERP Team 6.4
ERP Team 6.5
ERP Team 6.6

ERP Team 6.6.1


ERP Team 6.6.2 6.6.2.1

ERP Team 6.6.2.2


API Proxy 6.7

7 Daily Postpaid Payment Portal 7.1


Processing Flow for
New/Old Customer
(Stand-alone)
ERP Team 7.2
ERP Team 7.3 7.3.1

ERP Team 7.3.1.1


ERP Team

ERP Team

ERP Team 7.3.1.2


Task Description Source Destination Frequency

New Customer Creation in Oracle AR ERP One-Time


Sending New Customer Information ERP API Proxy One-Time
Customer Creation Feedback API Proxy ERP One-Time

Customer Deactivation in Oracle AR ERP One-Time


Sending Deactivated Customer Info. ERP API Proxy One-Time
Customer Deactivation Feedback API Proxy ERP One-Time

Sending Product Subscription with amount Payment Portal ERP TBD

Cash Receipts Creation at Oracle AR ERP Scheduled

Product Subscription Activation Requests ERP API Proxy Scheduled

Feedback: Product Subscription Activation API Proxy ERP TBD


Requests
IF Feedback --> SUCCESS ERP Scheduled

Invoice Creation ERP Scheduled


Sending Invoice details to customers ERP APIM Scheduled
Sending Invoice details to Payment Portal ERP Payment Portal Scheduled
Apply Cash Reciepts to Invoice in AR ERP Scheduled
IF Feedback --> FAILURE ERP Scheduled

At the end of subscription plan plus grace ERP Scheduled


period, ERP deactivates product subscription
plan.F21

At the end of subscription plan plus grace ERP API Proxy Scheduled
period, ERP sends deactivation request to
API Proxy
API Proxy feeds back on deactivation status API Proxy ERP TBD

IF Feedback --> SUCCESS ERP Team


IF Feedback --> FAILURE ERP Team
sends alert notification to Support Team ERP Team Support Team
email distribution list.
Sending Product Subscription with Payment Portal ERP Team TBD
committement fee

ERP validates customers account and ERP Team Payment Portal Scheduled
product subscription plan and sends status
feedback to Payment Portal.
Activate Customer Pos-paid subscription ERP Team TBD
ERP creates receipt for the payment ERP Team TBD

ERP posts Product Subscription Activation ERP Team API Proxy TBD
Request to API Proxy.
API Proxy feedback to ERP on API Proxy ERP Team TBD
success/failure.
IF Feedback --> SUCCESS ERP Team
IF Feedback --> FAILURE ERP Team

API Proxy sends API usage to ERP. API Proxy ERP Team TBD

Generate AR invoice for customer ERP Team TBD

Send invoice details to Payment Portal ERP Team Payment Portal TBD
Send invoice details to Customer ERP Team Customer TBD
ERP Apply receipts to invoice ERP Team TBD
ERP checks, month-end + grace period ERP Team
=SYSDATE
IF Invoice BALANCED ERP Team
IF Invoice NOT BALANCED ERP Team

Send Deactivate requests to API proxy ERP Team API Proxy


API proxy send feeback to ERP API Proxy ERP Team

Payment Portal pushes postpaid account Payment Portal ERP Team TBD
payment to ERP

Create Cash Receipts ERP Team


Check Postpaid customer deactivation status ERP Team

IF Customer already in DEACTIVATED ERP Team


status
If Invoice BALANCED, send activate the ERP Team API Proxy
account and send activation mail to API
proxy
If Invoice NOT-BALANCED, send activate ERP Team
the account and send activation mail to API
proxy
IF Customer already in ACTIVATED status ERP Team
Comments

Customer details will be sent to API Proxy using middleware


API Proxy server pushes feedback to ERP tables

Customer details will be sent to API Proxy using middleware


API Proxy server pushes feedback to ERP tables

Based on the event triggered at Payment portal, it will populate


ERP table with product subscription details

Job/CP will be created at ERP to check new payment details


populated in ERP and create receipts
Using middleware the activation requests will be posted to API
proxy
Feedback should be populated in ERP table.

Job/CP will be created at ERP to update the subscrption plan


(start_date and end_date) based on the timestamp from API proxy

Create AR invoice for the customer


ERP Sends invoice details via middleware
ERP Sends invoice details via middleware
Job/CP will be created at ERP to apply receipts to invoice
Job/CP will be created at ERP to send alert notification to Support
Team email distribution list.

Job/CP will be created at ERP to check subscription for


deactivated.

Middleware will be pushing the deactivaiton requests to API


Proxy.

Based on the event triggered at API proxy, it will populate ERP


table with product deactivation details
No action will be taken

Middleware will send email notification


Based on the event triggered at Payment portal, it will populate
ERP table with product subscription details

Based on the table data ERP will validate the informaiton and
sends feedback via Middleware.

ERP will activate the subscription


Once Subscription is activated, ERP will create cash receipts in
AR
Once after creating receipts activation requests will be posted to
API proxy via middleware.

ERP activates and set subscription plan for the current month.
ERP sends alert notification to Support Team email distribution list
via middleware.

API proxy will populate ERP tables with API usage details

ERP generates invoice based on the API usage and price(s) of


subscribed postpaid product(s).I41
Invoice details will be sent via Middleware
ERP will send invoice details to customer

NO action will be taken if invoice is balanced.

ERP Deactivates customer account and postpaid product


subscription.
The deactivation requests will be sent via middleware

Payment Portal will populate postpaid payment details in ERP


tables.

ERP will create AR cash receipts for postpaid customers


ERP will validate the customer deactivation status.

ERP apply existing receipts to invoice


No Action taken by ERP

No Action taken by ERP until month end.


Open Question
We do not know based on what event the actiity have to be performed in ERP

Vous aimerez peut-être aussi