General View – Main Applications

1.

General View – main Applications
Centeral
CMR
ESI
SOF
Local
SOF
ESI
BillTool
INFO
COMPLEX
LEKACH
INFO

2.

Customer Master Record Flow
CMR
CMR
System for entering customer data and addresses
SOF
(To be sunset)
INFO
(To be sunset)
LOCAL
APPLICATIONS
Sunset of
SOF & INFO
will require
solution of
CMR
replacement
before the
Sunset
LOCAL
INTERFACES
Central
Application
SOF - The central system, for managing orders, customers, machines, etc. Most of the
domains were transferred to IERP management (about two years ago). In the past,
customer data was mined directly to the SOF system. With the transition to IERP, the
CMR system was developed above, for this purpose and it is the one that feeds the SOF
for the use of old applications.
INFO- A collection of tables that are built mainly on the basis of SOF files, including
tables that contain customer data and addresses for the use of local applications and
interfaces for systems in Israel and abroad.
Local Interfaces
To BMS / CFTS system abroad
To RCMS technicians abroad
To CARS system abroad
To the CUSTLIST system in Haifa
HRL
Centeral App
ESI, NILS , CARS , CHIS , RCMS,
iERP
Local Apps
BILTOOL BMS invoices, laboratory
invoices
COMPLEX: Transaction invoices, Lekach /
Aviv invoices
LEKACH: Interfaces from / to Lekach.
LOCAL CARS TABLES / REPORTS
LOCAL ESI Interfaces to ESI
INFO online Dynamic queries, credit
letters to CARS

3.

BMS BILLING FLOW
CFT/S
Contract loaded to CFT/S.
A Billing movement is been release.
Receive from CFT/S by an interface.
DB2
A new Table developed in Israel BMS.BMSTB01.
TABLE BMS.BMSTB01
The Program pulls out from Interface only specific fields that are
defined for Billing/Invoicing/Accounting purpose.
BILTOOL
Receive from Table, calculate/update and handle the Billing
Movements according to the indicators and Client
ROBOT
The Invoice information is been “Manually typeed “
ESI
Invoice the Billing as requested
PRINTER
Invoice is been printed

4.

BMS/LAB ROBOT FLOW
After several attempts
by LOGIN and LOGOFF
the error record will
be set aside and will
not prevent the
further work.
The record will wait to
be hand and release
for billing by a User.
BILTOOL
ROBOT
DISPATCHER
ESI (On Line 2)
+ Print/PDF
The Robot dispatcher pulls out from DB2 only
specific records that are defined for
Billing/Invoicing/Accounting purpose.
An Error Session A –Receive the records from DB2, reads
Record each record (BM) and handle/Prepars the Billing
Movements according to the received BM
Session B - Checks if there are BM in stock.
BM’s received from TSO is been Manually type
including all required PFs in ESI screens
Session C – Starts working by searching the
proposal number. Valid all fields and pre-Invoice
is been created.
The Billing is Invoiced as requested
and printed or PDF
An Error occurred
ESI (On Line 1)
An Error occurred
TSO
A Billing movement is been release.
Marks the incorrect
record with a different
status and in addition,
writes the cause of the
problem over the
screen.

5.

LAB BILLING FLOW
LAB
Manually input
ROBOT
The Invoice information is been “Manually typeed“
ESI
Invoice the Billing as requested
Invoice is been printed
PRINTER

6.

COMPLEX LEKACH FLOW
SAP )LEKACH(
DB2
HOST
Contract loaded to MELACH (‫)מל"ח‬.
A File including all Billing movement is been
release.
Receive from SAP by an interface developed
in Israel.
The Host pulls out from DB2 only specific
fields that are defined for
Billing/Invoicing/Accounting purpose.
(INFO, BLFE, CMR, CARS)
Receive from Host, handle the Billing
Movements by planting the BM in the
transaction and payment level.
The transaction status is been changed to F
ESI
The invoice information is been “Manually
typeed “
COMPLEX
ECW )BILINVO(
SAP
Invoice the Billing as requested
Invoice is been printed

7.

COMPLEX LEKACH FLOW
SAP )LEKACH(
DB2
HOST
Contract loaded to MELACH (‫)מל"ח‬.
A File including all Billing movement is been
release.
Receive from SAP by an interface developed
in Israel.
The Host pulls out from DB2 only specific
fields that are defined for
Billing/Invoicing/Accounting purpose.
(INFO, BLFE, CMR, CARS)
Receive from Host, handle the Billing
Movements by planting the BM in the
transaction and payment level.
The transaction status is been changed to F
ESI
The invoice information is been “Manually
typeed “
COMPLEX
ECW )BILINVO(
SAP
Invoice the Billing as requested
Invoice is been printed