Interface Functional Design O2C3 From ETMS To EFSS Sales Orders Import Release 9.0.0

Document Title:
Interface Functional Design O2C3 from ETMS to EFSS Sales

Orders Import Release 9.0.0
Doc Number.
Ver. 9.2.1 Effective Date: Approval Date
EFSS_0055_FS
Interface Functional Design O2C3 from ETMS to

EFSS Sales Orders Import
Release 9.0.0
The information and contents of this document and any notes or handouts contain confidential and proprietary information, and are not to be
disseminated, reproduced, printed, translated or transmitted in any form, in whole or in part, without the prior written consent or express
permission of Pfizer, Inc. Use and distribution limited solely to authorized personnel.
Accessed By: Harte,Jason Effective

1 of 30
Access Date: 09-Sep-2013 12:04:59 PM GMT Page 1 of 30

Internal Use Only
Document Title:
Doc Number.
EFSS_0055_FS
Document Authors, Reviewers, Approvers

This document is authored by:
Marisa Martin
Order Management, Italy O2C Team
This document was reviewed by:

PDM Functional Hub, AD Team Lead
This document was approved by:

AD Lead , Release Lead and Pfast QA

2 of 30

Internal Use Only
Document Title:
Doc Number.
EFSS_0055_FS
Table of Contents
Document Authors, Reviewers, Approvers........................................................................................2
Document History.............................................................................................................................5
1.0 Document Purpose.....................................................................................................................8
2.0 Requirements .............................................................................................................................9

2.1.1 General Process Overview........................................................................................................ 9
2.1.2 French Requirements................................................................................................................ 9
2.1.3 Italian Requirements ................................................................................................................. 9
2.1.4 German Requirements............................................................................................................ 10
2.1.5 General Requirements ............................................................................................................ 10
2.1.6 User Requirements: ................................................................................................................ 11
2.1.7 Assumptions: .......................................................................................................................... 11
2.1.8 Contingency Procedures: ........................................................................................................ 13
3.0 Functional Design ....................................................................................................................14

3.1 Design........................................................................................................................................ 14
3.1.1 Process Flow .......................................................................................................................... 14
3.1.2 Detailed Description of Interface.............................................................................................. 14
4.0 Data Processing .......................................................................................................................15

4.1 Data Processing ........................................................................................................................ 15
4.1.1 Extract Parameters: ................................................................................................................ 15
4.1.2 Data Processing:..................................................................................................................... 15
4.1.3 Free of Charge, Sample and Promotional Goods .................................................................... 17
4.1.4 Item Cross Reference Conversions......................................................................................... 17
4.1.5 Price Modifers/Adjustments..................................................................................................... 17
4.1.6 Modifier Setup used to Import Discount Adjustments............................................................... 23
4.1.7 Figure 1.0 Example of Modifier Setup used to Import Discount Adjustments........................... 24
4.1.8 Returns................................................................................................................................... 25
4.1.9 Performance Considerations: .................................................................................................. 25
5.0 Error Handling .........................................................................................................................26

5.1 Extraction .................................................................................................................................. 26
5.2 Interface Processing ................................................................................................................. 26
5.3 Order Import process................................................................................................................ 26
6.0 Test Approach..........................................................................................................................28
7.0 Key Contacts ...........................................................................................................................29

3 of 30

Internal Use Only
Document Title:
Doc Number.
EFSS_0055_FS
8.0 Open / Closed Issues ................................................................................................................30

8.1 Open Issues .............................................................................................................................. 30
8.2 Close Issues.............................................................................................................................. 30

4 of 30

Internal Use Only
Document Title:
Doc Number.
EFSS_0055_FS
Document History
Ver. # Date Author(s) Summary of Changes/Comments

D.1 20-Sep-02 Leon Cunningham Original spec
D.2 8-Nov-02 Leon Cunningham Integration of PPG EDI requirements.
Consolidation of FD assumptions. Additionally
completed data mapping from EDI extract to
Oracle.
Relates to archived document of the same name.
Which sits in the Archive folder
D.3 11-Nov-02 Leon Cunningham Included the functionality to enable orders with
specific reservation detail to be imported. i.e.
requested lot
D.4 28-Nov-02 Leon Cunningham Consumer review comments incorporated. Main
change to the format of the import table
D.5 03-Dec-02 Leon Cunningham Added Descriptive Flexfield Attribute3 to the
mapping table
1.0 27-Jan-03 Leon Cunningham Applied the validated template format.
Additionally checked all table details
1.1 14-Mar-03 Eugenio Sacristan Document Split from O2C2 original doc in order
to separate ETMS and EDI sources.
1.2 12-May-03 Eugenio Sacristan Change Request CR41: Added explanation to get
the item identifier through the Item cross
references functionality (4.1.2 Section)
1.3 09-June-04 Costi Karayannis Updated for Spain Go Live:
- remove references to modifiers/discounts
- provide clarity on use of free/promo
goods
1.4 28-Jul-04 Mike Turner Sections 2.1.4 and 4.1.2 updated to clarify that
manual pricing (ie prices included in the
interface data) are not used lines are priced by
the import process.
5.0 30/11/2005 Anthony Thorp CR1460e Interface updated to support RMAs.
Sections 2.1.4 and 4.1.2 updated to indicate that
manual pricing is now supported.
7.0.0 17-May-06 Declan Barry CRFRxxx
Interface updated for France requirements for the
LAULAE ETMS interface
1. To import discounts / modifiers relating to sales
order/lines
2. Line details modified to allow the selling_price

5 of 30

Internal Use Only
Document Title:
Doc Number.
EFSS_0055_FS

be imported and set separately
3. Allow the Calculate_Price_Flag be imported
and set via the file import
Redefined Item Cross reference process to only
use the item validation org
Also, tidied up layout, added more
content/explanation
9.0.1 06-Jun-06 Marisa Martn New Italian requirements:

1. Add a field for PGP Italy for storing the
customer price
2. Add a DFF at line level for PCH Italy for
storing the discount applied (only for
information) as they are going to send the net
price.
3. Add the line type for promotionals, samples
4. Add a field to store the original sales order, so
that the price can be copied for PCH returns
5. Add a DFF at line level for storing the lot
information for the returns.
9.1.1 20-Jun-06 Marisa Martn - Update the lot information that has to be only for
returns records
Barry Declan
- Add the salesrep field at header level
- Exclude requirement for 9.0.1 2.above in
the form of a DFF. Added detail to use
OE Price Adjs import instead and to mark
the Adjustment modifier as Information
Only.
- Added more detail to 9.0.1 detail to aid
eAi team
- Put requirements under separate headings
for each country
- Modified CR1460e to change reference
to return reason code being set in
OE_LINES_IFACE_ALL instead of
OE_HEADERS_IFACE_ALL. This
reflects actual change made in eAi.
- Example Modifier setup
9.2.1 12-Sep-06 Richard Gibson Updated for German Returns (RMA)
Requirements

6 of 30

Internal Use Only
Document Title:
Doc Number.
EFSS_0055_FS

9.2.1 31-Oct-06 Nicky Carpenter Formatted headers, footers, table layouts and
reviewer / approver sections
9.2.1 03-Nov-06 Nicky Carpenter Formatted header and updated contents page

7 of 30

Internal Use Only
Document Title:
Doc Number.
EFSS_0055_FS
1.0 Document Purpose

This document outlines the functional requirements and the proposed solution required to support the
import of Sales Order data in Oracle.
The proposal is that this interface will be used to support the import of sales data from ETMS systems.
ETMS are local systems that manage Sales Orders acquired from Customers by Pfizer Sales Reps out in
the field.
The interface will be used to ensure that the sales order detail created by the source application, is
successfully transferred to and processed by EFSS.
The interface will address the following:
Transfer and processing of data through the interface solution
o Data Mapping
o Data validation
Error handling of rejected data from Oracle
The interface Functional Specification does not address
Detailed technical requirements of hardware/software to support the interface

8 of 30

Internal Use Only
Document Title:
Doc Number.
EFSS_0055_FS
2.0 Requirements
2.1.1 General Process Overview
Customer orders will be received from local applications such as ETMS, a system used to collect Sales
Orders from customers by Pfizer Sales Reps in the field.
The process is envisaged to work as follows:
Order detail will be imported into Oracle via an interface function (details of the interface are
explained in the document).
Orders being imported into Oracle can be imported with one of two statuses either BOOKED or
ENTERED.
ENTERED status should be used in order to be able to review these entered orders and make
any updates or amendments required to approve the order. It is at this stage that Credit Checking will
take place, as well as customer and item validation.
Once the order is approved, it will be assigned a status of Booked.
As a Booked order , it is now eligible to be picked and shipped to the customer.
2.1.2 French Requirements
CR5287 for France requires that Price Modifier/Adjustments relating to Sales Order header an/or
lines be imported. This change is to accommodate requirements for the LAULAE ETMS interface for
France and possible future requirements.
2.1.3 Italian Requirements
Italy requires several new changes to meet Italian requirements for Order Entry & Import as follows:-
Add a field for line type at line level (for promotional and samples, as they can be in the same
sales order but with different sales order line type).
This will allow the interface to dictate the type of the line with the related quantity field
indicating the quantity of that order line. If this field is populated its functionality should take
precedence over the existing functionality using FreeQty and PromoQty fields.
Add a field for the customer price for PGP for being able to see if there is any discrepancy
between the customer and the oracle price. This filed is the customer_net_price and it has to be
not updatable once inserted (so the pll has to be customized as this field can be fullfiled also
manually but not updated).

9 of 30

Internal Use Only
Document Title:
Doc Number.
EFSS_0055_FS
Allow Discount Information be imported that is classed as Information Only for PCH specific
Orders. PCH will import Orders that use the List Price in the Oracle Price List and apply an
imported discount to get the selling price.
This will allow the Discount be viewed as normal through the View Adjustments form and also
allow such discounts be excluded from having accounting information assigned or being shown
on invoices.
N.B. The Invoice Print and Accrual Accounting extensions will need to be modified to exclude
this type of Modifier from processing
For PCH returns, the requirement is to store the original sales order to take the original price to
add to the return and also store for all in a Return DFF (RETURN_ATTRIBUTE5 for the DFF
Additional Line Return Information) the lot information to send in the interface to WMS system
in P2P4.
Add the salesrep field at header level (SALESREP column from OE_HEADERS_IFACE_ALL)
it has to be validated in the egate that the value exists as a correct value on the salesrep table
(NAME column from JTF_RS_SALESREPS).
For Italian PCH orders that have to be on hold the status will be ENTERED and will be not Book
till OPS system decide it with the actions interface for Sales Orders (O2C69).
2.1.4 German Requirements
For returns (RMA) processing additional information will be passed using Descriptive Flexfields on the
DFF Additonal Line Return information.
(RETURN_ATTRIBUTE6 for the DFF Additional Line Return Information) will contain the
SUBLOT number.
Lot Expiration Date.
Sub inventory code.
Other information is required however this is readily available from other sources. Locator is in
Return_Attribute4 and Lot Number is in Retrun_Attribute5. The quantity can be selected from the
standard column on OE_LINES_IFACE_ALL.
2.1.5 General Requirements
The interface will be required facilitate the automatic creation of Sales Orders sent from ETMS
applications.
From System:
ETMS, local market field Sales Order capture system

10 of 30

Internal Use Only
Document Title:
Doc Number.
EFSS_0055_FS
To System:
EFSS (Order Management module)
Transaction Volume:
For ETMS orders - Up to 100 orders per day with up to approximately 100 lines.
Average 20 orders of 8-10 lines, each, daily.
Input File Size 2 kb- 30 kb.
Spain across the different business units imports about 700 orders on a monthly basis. Around 90% of
these orders have 20+ order lines.
Frequency:
Dependent on local market.
2.1.6 User Requirements:
Currently, the ETMS system executes daily analysis all reps direct orders for the day. It then creates a file
containing order data for each SKU for each customer, which is transmitted to the SAP system.
A similar design is anticipated using EFSS. Daily Sales data will be collated and transmitted to
the EFSS Oracle system. The order data will include delivery data and pricing information.
The pricing information will enable the reps to override the unit selling price from the price list
but will not allow them to apply line- or header-level discounts.
France CR5287 requires that Price Modifier/Adjustments relating to Sales Order header an/or
lines be imported. This change is to accommodate requirements for the LAULAE ETMS
interface for France and possible future requirements.
Italy requires the following:-
That an Information Only Price Modifer Adjustment be imported showing the discount
applied. This has been flagged as Information Only using a Line Classifcation
attribute on the Additional Info for List Lines DFF in Advanced Pricing.
By flagging the Modifier as such it can be excluded from subsequent Accounting and
Invoice processing in AR .
For returns, the price will be calculated from the original sales order. In addition, the Lot
Number needs to be stored when processing returns (RMAs)
2.1.7 Assumptions:
OE module will be set-up to use NAME or SEGMENT columns during order import

11 of 30

Internal Use Only
Document Title:
Doc Number.
EFSS_0055_FS
Order lines with Free goods / sample quantities will necessitate the creation of a new order line
using the specified quantity as the new order quantity
Italy: Order line types can be sent now to the interface.
Extract data will be sent from separate organizations. Each extract will include details of the
organization owning the order detail.
Only existing in EFSS and active Customers will be able to place orders. New customers will not
be created during the order import process.
New or one time Shipment, Delivery or Invoicing address will not be created during the Order
Import process.
Defaulting Rules will be created for each import organization. This will facilitate the automatic
assignment of standard order detail i.e. Payment Terms, Shipment Method etc.
A separate run will be submitted for each Operating Unit and only data for this Competing
Organization will be processed during the run.
The local ETMS system will generate a unique Order Number. This Order Number will be
referenced in Oracle and stored in the ORIGINAL_SYS_DOCUMENT_REF field. Oracle also
generates its own order number.
Oracle Order Import Exception Report will be used to identify errors.
Orders lines without price will be priced within Oracle using the standard functionality to retrieve
the appropriate price list. If a price is supplied in the interface it will be used rather than the
standard pricing functionality.
It is anticipated that you have the choice of allocate a status of BOOKED in Imported Sales
Orders. These orders will be eligible for pick release i.e. inventory allocation/reservation and
picking. Normally, orders will be allocated a status of ENTERED. These orders will then be
modifiable by customer services. It is envisaged that the criteria governing the status of an order
will be part of the imported data.
Italy: Can now import other status or actions for a sales order and sales order line: BOOKED,
ENTERED, CANCEL, HOLD and RELEASE HOLD within the O2C69 Interface only from Italy
PCH to Oracle.
Only SALES ORDER order types will be imported, RETURNS will not be imported, these
will be created manually within Oracle.
CR1460e: Returns can now be imported

12 of 30

Internal Use Only
Document Title:
Doc Number.
EFSS_0055_FS
Italy: Returns from Italy have to take the price for the original sales order if this is in the records
to import and also lot information can be stored to send in P2P4 to the warehouse to receive the
corresponding RMA.
It has to be taken into account that the original sales order cannot be copied into the return
information, as it will generate an issue with EFSS AR. So this number has to be used just for
retrieving the price into the return information.
Germany
Three new DFFs allocated for Germany on the Return Information DFF. Return_Attribute6
holds SubLot, Return_Attribute7 holds Lot Expiration Date and Return_Attribute8 holds
Subinventory Code
The rounding (up or down) of orders quantities and the use of Selling UOM will not be managed
through the interface. It is assumed that these changes will take either before or after the data has
been imported. Thus the interface will not perform any additional data manipulation.
A common file format will be used to manage all imported data from all sources
There will be no modifiers sent in the ETMS file.
France CR5287: Modifier/Price Adjustments can now be imported.
2.1.8 Contingency Procedures:
During the import process, if a specific sales order line is found to be in error, then the entire order will be
flagged as being in error, even if all other associated lines are correct.

13 of 30

Internal Use Only
Document Title:
Doc Number.
EFSS_0055_FS
3.0 Functional Design

3.1 Design
3.1.1 Process Flow

The diagram below gives a high level view of how the interface will work
EDI or ETMS Oracle - EFSS
Oracle Transaction
eGate Manager
ETMS
Custmoer 6
EDI Orders Order 5
Header 5
OE_ORDER
_HEADERS
1 _ALL
3
4
Order
Staging table OE_ORDER
Detail
7 _LINES_ALL
Inbound
Directory
2
Outbound
Directory
3.1.2 Detailed Description of Interface

1. The order data will be transferred directly to the Oracle Order Open Interface from the source
application (ETMS) by eAi.
The interface process will consist of two steps
o File transfer The file will be transferred to EFSS and processed by the application.
o Data transformation The transferred data will be mapped to the Order Management
Open Interface tables by an eAi programme.
Error handling during this phase will be managed through the interface.
Failure of any component or process should result in the notification of the
appropriate support team and source users
2. The processing and validation of the imported detail will be managed using the standard Oracle
Order Import functionality
3. Order Management automatically generates an Order Import processing results summary log,
which identifies the total number of successful and failed imported orders.

14 of 30

Internal Use Only
Document Title:
Doc Number.
EFSS_0055_FS
4.0 Data Processing

4.1 Data Processing
4.1.1 Extract Parameters:
Order Import is an Order Management Open Interface that consists of open interface tables and a set of
APIs. The procedure can import new, changed, and completed sales orders or returns from the customer
data transmitted from varying source applications.
Order Import features include validation of fields with the set up of the Order Management module,
defaulting values when sales orders are created, processing constraint checks, applying and releasing of
order holds, scheduling of shipments, then ultimately inserting, updating or deleting the orders in the base
Order Management tables.
Valid transactions are then converted into orders with lines, reservations, price adjustments, and sales
credits in the base Order Management tables.
The source data for the import process will come from ETMS order detail. The detail will consist of a
mixture of valid approved orders.
Data will be mapped directly from the staging tables, and used to populate the Open Interface tables.
The input file will consist of three record types
Order Header Information - Mandatory one per order

Order Line detail - Mandatory one to many lines per header record
With France CR5287

Price Modifier information is now in scope in this interface and optional Price Adjustment Records can
also be imported.
The layout of these extract files can be found in a separate spreadsheet accompanying this document
(SD_Interface_FD_O2C3_fromETMS_to_EFSS_SalesOrderImport.xls)
4.1.2 Data Processing:
The Process Order Interface is the central application process interface (API) provided by Order
Management to perform all common operations such as inserting, updating, deleting, and validating an
order or order line. This API is called by Order Import.
Order Import passes one order, with all lines and other entities, at a time to the Process Order Interface,
along with the operations that need to be completed on the order or line such as, inserting or updating an
order or line.

15 of 30

Internal Use Only
Document Title:
Doc Number.
EFSS_0055_FS
Errors at any line or entity level will cause the order to fail the importing of the entire order. In addition,
Order Import processes only those orders and lines that meet the validation criteria to generate a new
order within Oracle.
Each time Order Import is run, Order Management automatically generates an Order Import Processing
results summary log which identifies the total number of successful and failed imported orders.
Order Import uses the following interface tables during processing, the tables used to achieve the
functionality under this Function Design are flagged,
Interface Table Name Description Used

by
O2C2/3
OE_CUSTOMER_INFO_IFACE_ALL Interface table to add new customers and associated address No
and contact info.
OE_HEADERS_IFACE_ALL This is a multi-org table for sales order headers open interface. Yes
This table stores order header information that is imported from a
feeder system into Oracle Order Management using Order
Import.
OE_LINES_IFACE_ALL This is a multi-org table for sales order lines open interface. This Yes
table stores order lines information that is imported from a feeder
system into Oracle Order Management using Order Import.
OE_ACTIONS_IFACE_ALL This is a multi-org table for sales order actions (holds, booking Yes
etc.) open interface
OE_PRICE_ADJS_IFACE_ALL This is a multi-org open interface table for sales order/line price Yes
adjustments. This table stores price adjustment information that
is imported from a feeder system into Oracle Order Management
using Order
OE_PRICE_ATTS_IFACE_ALL This is a multi-org Interface table to populate No

OE_ORDER_PRICE_ATTRIBS. This table stores pricing
attributes information that is imported from a feeder system into
Oracle Order Management using Order Import.
OE_CREDITS_IFACE_ALL This is a multi-org table for sales order/line credits open No

interface. This table stores sales credits information that is
imported from a feeder system into Oracle Order Management
using Order Import.
OE_LOTSERIALS_IFACE_ALL This is a multi-org table for return line lot serials open interface. No
This table stores return line lot serial information that is imported
from a feeder system into Oracle Order Management using
Order Import
OE_RESERVTNS_IFACE_ALL This is a multi-org table for inventory reservations open interface. No

This table stores reservation details that is imported from a
feeder system into Oracle Order Management using Order
Import.

16 of 30

Internal Use Only
Document Title:
Doc Number.
EFSS_0055_FS
4.1.3 Free of Charge, Sample and Promotional Goods
Sales Orders can contain a number of Order Lines for items that are Free of Charge to the Customer,
Samples or Promotional items and the eAi Load and Import process must handle them accordingly.
Examples of different scenarios for these items are as follows, Free of Charge items would be when a
customer orders a large amount of a Pfizer item in a period, Pfizer will give some of the product for free
due to the large volumes; Pfizer may also give Samples of new or existing Pfizer products to Doctors to
promote these items; They may also run Promotions of their products by including non Pfizer items such
as Tee-Shirts, pens etc advertising Pfizer product as part of a Marketing campaign.
The eAi programme that loads the Order Data in the Oracle Open Interface tables needs to handle Free of
Charge , Promotional and Sample goods as follows:-
If a Free Goods is greater than zero is sent for these Goods then a new order line should be created and
should assume a line type that is
1. Associated with order type set against customer ship-to site and
2. Has ATTRIBUTE2 = Y on Transaction Type DFF (marked as Free of Charge)
If a value is sent for Promo/Sample Goods then a new order line should be created and should assume the
default line type from the order type but with a zero unit selling price.
For Italy its needed that different line types will be sent by this interface.
4.1.4 Item Cross Reference Conversions
Incoming Orders may contain the Items defined in the Local Market Item code, EAN number, National
Code or some other cross reference. These Item Codes are set up in Oracle to Cross reference with the
Oracle Item Code which is used internally with the Oracle systems as the Item reference.
The Local Item Code or other cross reference Conversion will be done through the Item Cross References
functionality as follows:
All the Item Cross References will be maintained at the Item Validation Organization (IVO).
The Item Validation Organization can be recovered from the OE_SYSTEM_PARAMETERS table
using the Operating Unit Identifier.
4.1.5 Price Modifers/Adjustments
France CR5287
This CR applies to France and the import of Price Adjustments relating to Sales Orders from the
LAULAE interface. For this interface, it is required that the list price and related discount
amount are imported by the Order Import and that the selling price is subsequently calculated by
the pricing engine using the imported list price and not the Price available on the Oracle price
list. This is required so that the discount can be displayed on the Invoice.

17 of 30

Internal Use Only
Document Title:
Doc Number.
EFSS_0055_FS
This is achieved by importing the price adjustment and setting the calculate_price_flag on the
Order Lines Interface table, OE_LINES_IFACE_ALL to P for partial which allows the Price
engine be called to process the Adjustment Modifier but not to replace the imported List price
with the Oracle List Price for the item.
In order to do this, several changes would need to be incorporated to handle the import of Price
Adjustments for this interface. Rather than design the change specifically for the above and as
the changes required are close to a generic import of Price Adjustments it has been decided that
this change should handle the import of Price Adjustments in general.
The following areas need to be addressed :-
1. Add the required fields to the existing Price Adjustment (Price Mods) record on the eAi
file in order to make the Price Adjustments import work
See section on OE_PRICE_ADJS_IFACE_ALL
2. Add a field to allow the CALCULATE_PRICE_FLAG on the Order interface Lines be

set from within the file rather than within the eAi load programme
See section on CALCULATE_PRICE_FLAG
3. Add a field to hold the UNIT_SELLING_PRICE at Line level so that this can be
populated separately if required
See section on CALCULATE_PRICE_FLAG
OE_PRICE_ADJS_IFACE_ALL
In order to Import Price Adjustments/Modifers, a modifier header and line must first be set up that
contains default information relating to the type of price adjustment to be applied.
The OE_PRICE_ADJS_IFACE_ALL table needs to be populated as per table below
Column Required Value Comment

order_source_id Yes Same as
Order
Header
orig_sys_document_ref Yes Same as
Order
Header
orig_sys_line_ref Conditionally Same as This should only be
Order Line populated if the
modifier_level_code is

18 of 30

Internal Use Only
Document Title:
Doc Number.
EFSS_0055_FS

'LINE'.If
modifier_level_code is
'ORDER' then it implies
a Header level Discount
is applied, if 'LINE' the a
Line Level Discount is
applied.
orig_sys_discount_ref Yes Unique Unique sequence number
Sequence reference to discount, i.e.,
Number If there are 3 modifiers to
be applied then there
would be 3 records with
Order Discount Ref of
1,2,3
Creation_date Yes Sysdate
created_by Yes Standard
eAi user
Last_update_date Yes Sysdate
Last_updated_by Yes Standard
eAi user
list_name Yes Modifier This will represent the
Number Name of the
Modifier/Discount to be
applied to the order and
is the value defined in the
form QP: Define
Modifier->Main-
>Number field
list_line_number Yes Modifier This will represent the
Line Name of the
Number Modifier/Discount to be
applied to the order and
is the value defined in the
form QP: Define
Modifier->Main->
Modifiers Summary->
Modifier No field
list_line_type_code Yes Modifier list_line_type_code value
List Line returned from lookup
Type
Automatic_flag Yes Value in Value returned from
modifier lookup.
Line
Set to manual (Uncheck
Automatic flag on
Modifier Line) if you do

19 of 30

Internal Use Only
Document Title:
Doc Number.
EFSS_0055_FS
Column Required Value

Comment
not want the Modifier
Applied Automatically
when an Order Is created
manually.
Applied_flag Yes Y Apply the modifier
Operation_code Yes CREATE Create a new adjustment
Operand Yes Modifier If the PriceModValue is
List Line populated on the file the
Operand use this value otherwise
use the Operand value
returned from lookup
arithmetic_operator Yes Modifier Arithmetic Operator
List value returned from
Arithmetic lookup
Operator
adjusted_amount Conditionally, if The Adjusted Amount of
CALCULATE_PRICE_FLAG Discount which is
= N negative for a Discount
adjusted_amount_per_pqty Conditionally, if Adjusted amount per

CALCULATE_PRICE_FLAG pricing quantity.E.g., If
= N the arithmetic_operator is
AMT then this will be
same value. If
arithmetic_operator is
% then it will be the
actual amount value you
get after applying the %.
This is also negative for a
Discount.
E.g List Price = 40,

Operand = 15, Arithmetic
Op = %, Adjusted
Amount = -6,
adjusted_amount_per_pq
ty = -6 ,
operand_per_pqty = 15
operand_per_pqty Conditionally, if Operand per pricing
CALCULATE_PRICE_FLAG quantity. E.g., If the
= N arithmetic_operator is
AMT then this will be
same value. if
arithmetic_operator is
% it will also be the
same.

20 of 30

Internal Use Only
Document Title:
Doc Number.
EFSS_0055_FS
update_allowed No Setting this to N should

mean that the Adjustment
Modifier cannot have the
value changed/saved and
re-applied through the
View Adjustments
form in OM.
This appears Not to work
correctly as the Order
Import resets it to Y
regardless but leave for
future use but populate
from file
updated_flag No If you want to have the
imported discount value
be applied and not
overwritten by the default
value in the Modifier
setup then set this to Y
otherwise set it to N or
leave blank to have
default applied.
CALCULATE_PRICE_FLAG
The purpose of The CALCULATE_PRICE_FLAG on the order line interface is to control whether a
pricing/discount - charge calculation should be done on the line once imported
Value Meaning Action Comment

Y Calculate Both pricing and discount / If the calculate_price_flag is set to Y and the
Price freight charge calculations unit_list_price and unit_selling_price are populated and a
price adjustment record is populated :-
are done
Then the pricing engine will be called and will overwrite the
imported unit_list_price with that of the price on the Oracle
price list associated with the order and the price adjustment
will then be applied to this to get the unit_selling_price
If the calculate_price_flag is set to Y and the

unit_list_price and unit_selling_price are blank and a price
adjustment record is populated :-
Then the pricing engine will be called and will populate the
unit_list_price with that of the price on the Oracle price list
associated with the order and the price adjustment will then
be applied to this to get the unit_selling_price
P Partial Only the discount / freight If the calculate_price_flag is set to P and the

21 of 30

Internal Use Only
Document Title:
Doc Number.
EFSS_0055_FS
Value Meaning Action Comment

Price charge calculation is done unit_list_price and unit_selling_price are populated and a
Then the imported Unit_List_Price will be used and NOT the

Oracle list price. The Pricing Engine will be called and the
price adjustment will then be applied to this to get the
unit_selling_price.
If the calculate_price_flag is set to P and the

unit_list_price and unit_selling_price are NOT populated
and a price adjustment record is populated :-
Then neither Unit_List_Price or Unit_Selling_Price will be

populated and the pricing engine will not populate these with
the Oracle list price and the price adjustment will NOT be
applied. This effectively leaves an incomplete Order Line
without any pricing.
N Freeze Neither pricing nor discount If the calculate_price_flag is set to N and the
Price / freight charge is done unit_list_price and unit_selling_price are populated and a
Then the imported Unit_List_Price and Unit_Selling_Price

will be used and NOT the Oracle list price as the Pricing
Engine is NOT called. The price adjustment will be imported
intp the OE_PRICE_ADJUSTMENTS table but will NOT be
applied to the UNIT_LIST_PRICE, again because the
Pricing Engine is not called.
If the calculate_price_flag is set to N and the

unit_list_price and unit_selling_price are NOT populated
and a price adjustment record is populated :-
Then neither Unit_List_Price or Unit_Selling_Price will be

populated and the pricing engine will not populate these with
the Oracle list price and the price adjustment will NOT be
applied. This effectively leaves an incomplete Order Line
without any pricing.
If CALCULATE_PRICE_FLAG field is populated for a line then it takes precedence and should
be mapped to the CALCULATE_PRICE_FLAG on the interface line if it is blank then the
programme should default to its current functionality defined below:-
Orders lines without price will be priced within Oracle using the standard functionality to retrieve the
appropriate price list. This standard functionality is triggered in the interface process by the
CALCULATE_PRICE_FLAG being set to Y for all imported order lines. If a manual price is provided
on the interface the CALCULATE_PRICE_FLAG field will be set to N and the price value supplied
will be used rather than calculated.
If the UNIT_SELLING_PRICE is populated on the Line then it takes precedence and should be used to
populate the UNIT_SELLING_PRICE on the Interface line table otherwise the existing functionality
should be used where by it is populated from the UNIT_LIST_PRICE.

22 of 30

Internal Use Only
Document Title:
Doc Number.
EFSS_0055_FS
4.1.6 Modifier Setup used to Import Discount Adjustments
The setup in Figure 1.0 Example of Modifier Setup used to Import Discount Adjustments
Below shows the Modifier Discount List and the Modifier List Line, The Modifier List Number and
Modifier List Line Number should be communicated to the Market as this is what they will use to Supply
the discounts.
N.B. Qualifiers still need to be applied in the normal way
Setting the Modifier List Line to Manual allows the Adjustment be imported and applied if it qualifies but
will not automatically be applied for Orders that would qualify but for which you do not want to apply an
Adjustment. The Application method can be any valid method, for example, % or AMT

23 of 30

Internal Use Only
Document Title:
Interface Functional Design O2C3 from ETMS to EFSS Sales Orders Import
Ver. 9.1.1 Effective Date: 20-June-2006 Doc Number. EFSS_0055_FS
Value is set to 0 as a contingency in case the Automatic setting was switched on and the value applied inadvertently.
The Line Classification DFF is used to further flag the type of Modifier. Information Only in this case will allow the extension for automatic
Discount & Accrual distributions and the Invoice Print programme be modified to exclude Information Only discounts from processing
4.1.7 Figure 1.0 Example of Modifier Setup used to Import Discount Adjustments
Type Discount List Number FR01 LAULAE DIS

FR01 LAULAE Discount FR01 LAULAE Discount Version
Currency EUR Start Date
Description EFSS FR01 LAULAE Discount for use in import of O2C2/3 Price End Date
Adjustments
Active Yes Automatic

Business Code N/A Market
Modifier Level Modifier Print on Automatic Override Pricing Phase Application Accrue Value DFF Value
No Type invoice Method
LAULAE Line Discount No No Yes List Line Percent or Yes/No 0 Line IM

_LINE_D Adjustment Amt Classification
IS

24 of 30
Access Date: 09-Sep-2013 12:04:59 PM GMT Internal Use Only

Page 24 of 30
Document Title:
Orders Import
Doc Number.
Ver. 9.1.1 Effective Date: 20-June-2006
EFSS_0055_FS
4.1.8 Returns
CR1460e
The Oracle Order Import process can also handle the import of Returns, known as Return Material
Authorizations (RMAs) in Oracle. The data required is similar to that for Orders
RETURN_REASON_CODE to be added to the interface to be inserted into the OE_LINES_IFACE_ALL

table to enable the interface to support RMA transactions.
The returns from Italy have to take the price for the original sales order if this is in the records to import
and also the lot information.
For Achieve the return with the original price, there has to be a calculation of the price of the original
sales order recorded in the interface for the return. The original sales order cannot be copied in the record
to import, just use it to take the price.
A summarised layout of the mapping between the proposed extract files and the Oracle Open
interfaces tables can be found in a spreadsheet accompanying this document
(SD_Interface_FD_O2C3_fromETMS_to_EFSS_SalesOrderImport.xls)
4.1.9 Performance Considerations:
Files received from ETMS Systems will be allocated in the inbound directory, then processed by the
interface in order to populate Open Interface standard tables, and after that Import Process will be
run.

25 of 30

Internal Use Only
Document Title:
Orders Import
Doc Number.
EFSS_0055_FS
5.0 Error Handling
Error handling will be split across 2 phases on the following areas of validation
5.1 Extraction
Basic validation of the extract detail should occur prior to the data be transferred.
5.2 Interface Processing
The interface solution will be responsible for maintaining the structure and integrity of the data
being transferred.
Should any process or component fail, during this stage, a notification should be sent to the
destination user (informing them of error), the appropriate interface support team (eGate) and the
Customer Services Group.
If an error is encountered on a single order line whilst being processed, then this f failure would
not necessitate the cancellation of the whole batch. Instead the order line and associated header
can be placed in error and processed at a later date.
5.3 Order Import process
Standard Oracle functionality will be used to manage of any errors encountered during this
process. They will be the responsibility of the EFSS solution support team. This team will then
be responsible for informing the Customer Services group.
Problem Possible Occurs in Recognition Solution Strategy

cause
Triggering Interface WMS At the A certain number of attempts
mechanism of function interface within a limited time frame. Each
outbound interface cant be destination, attempt is logged. If they all fail,
fails. called expected notification sent to local
data is application support. Interface
missing. must be rerun.
Transfer fails Technical SeeBeyond Operations Operations provide guaranteed
(inbound or errors during monitoring delivery. If a transfer fails
outbound). transfer operations will be notified and
resolve the technical issues.
Triggering File is not External SeeBeyond A certain number of attempts
mechanism of available application throws an within a time frame. Each attempt
Oracle inbound exception is logged. If they all fail,
fails. notification to the local team. The
interface must be rerun.

26 of 30

Internal Use Only
Document Title:
Orders Import
Doc Number.
EFSS_0055_FS
Problem Possible Occurs in Recognition Solution Strategy

cause
Data manipulation Required SeeBeyond SeeBeyond Notification to the local team,
fails on Oracle fields empty throws an which must investigate, and
inbound. exception. possibly get in touch with the
EFSS application support.
Skipped lines must be corrected
and run through the interface
later.
Mapping SeeBeyond SeeBeyond Notification to the local team,
table not up- throws an which must investigate, and
to-date exception. possibly get in touch with the
EFSS application support.
Skipped lines must be corrected
and run through the interface
later.
Data load into Inconsistent Oracle Oracle error If the error occurred during the
Oracle fails data, data handling Order Import validation process),
validation the entire transaction group is
fails. marked with an error code, whilst
the row(s) that actually failed will
have an error explanation.
The EFSS application support
team will then be responsible for
correcting the problem and re-
submitting the interfaced rows.

27 of 30

Internal Use Only
Document Title:
Orders Import
Doc Number.
EFSS_0055_FS
6.0 Test Approach

Testing of this interface will be carried out in line with defined testing approach adapted by EFSS and
the local business owners. Validation testing will be in line with the approach agreed by the EFSS
Validation Manager and Pfizer Quality Operations.
CR5287: Testing should involve all combinations based on the comments field on the
CALCULATE_PRICE_FLAG section table
Italy: Testing should involve also the P2P4 review of the lot information to be sent.
Price Adjustment Import should be tested for Italy

28 of 30

Internal Use Only
Document Title:
Orders Import
Doc Number.
EFSS_0055_FS
7.0 Key Contacts

EFSS
Declan Barry Application Architecture

29 of 30

Internal Use Only
Document Title:
Orders Import
Doc Number.
EFSS_0055_FS
8.0 Open / Closed Issues
8.1 Open Issues
ID Issue Resolution Responsibility Target Impact

Date Date
8.2 Close Issues
ID Issue Resolution Responsibility Target Impact

Date Date

30 of 30

Internal Use Only

Interface Functional Design O2C3 From ETMS To EFSS Sales Orders Import Release 9.0.0

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Interface Functional Design O2C3 From ETMS To EFSS Sales Orders Import Release 9.0.0

Încărcat de

Drepturi de autor:

Formate disponibile

Document Title:

Interface Functional Design O2C3 from ETMS to EFSS Sales

Interface Functional Design O2C3 from ETMS to

Accessed By: Harte,Jason Effective

Access Date: 09-Sep-2013 12:04:59 PM GMT Page 1 of 30

Document Authors, Reviewers, Approvers

This document was reviewed by:

This document was approved by:

Accessed By: Harte,Jason Effective

Access Date: 09-Sep-2013 12:04:59 PM GMT Page 2 of 30

1.0 Document Purpose.....................................................................................................................8

2.0 Requirements .............................................................................................................................9

3.0 Functional Design ....................................................................................................................14

4.0 Data Processing .......................................................................................................................15

5.0 Error Handling .........................................................................................................................26

6.0 Test Approach..........................................................................................................................28

7.0 Key Contacts ...........................................................................................................................29

Accessed By: Harte,Jason Effective

Access Date: 09-Sep-2013 12:04:59 PM GMT Page 3 of 30

8.0 Open / Closed Issues ................................................................................................................30

Accessed By: Harte,Jason Effective

Access Date: 09-Sep-2013 12:04:59 PM GMT Page 4 of 30

Ver. # Date Author(s) Summary of Changes/Comments

Accessed By: Harte,Jason Effective

Access Date: 09-Sep-2013 12:04:59 PM GMT Page 5 of 30

Ver. # Date Author(s) Summary of Changes/Comments

9.0.1 06-Jun-06 Marisa Martn New Italian requirements:

Accessed By: Harte,Jason Effective

Access Date: 09-Sep-2013 12:04:59 PM GMT Page 6 of 30

Ver. # Date Author(s) Summary of Changes/Comments

Accessed By: Harte,Jason Effective

Access Date: 09-Sep-2013 12:04:59 PM GMT Page 7 of 30

1.0 Document Purpose

The interface will address the following:

Transfer and processing of data through the interface solution

Error handling of rejected data from Oracle

The interface Functional Specification does not address

Detailed technical requirements of hardware/software to support the interface

Accessed By: Harte,Jason Effective

Access Date: 09-Sep-2013 12:04:59 PM GMT Page 8 of 30

The process is envisaged to work as follows:

Once the order is approved, it will be assigned a status of Booked.

As a Booked order , it is now eligible to be picked and shipped to the customer.

2.1.2 French Requirements

2.1.3 Italian Requirements

Accessed By: Harte,Jason Effective

Access Date: 09-Sep-2013 12:04:59 PM GMT Page 9 of 30

2.1.4 German Requirements

2.1.5 General Requirements

ETMS, local market field Sales Order capture system

Accessed By: Harte,Jason Effective

Access Date: 09-Sep-2013 12:04:59 PM GMT Page 10 of 30

EFSS (Order Management module)

2.1.6 User Requirements:

Italy requires the following:-

Accessed By: Harte,Jason Effective

Access Date: 09-Sep-2013 12:04:59 PM GMT Page 11 of 30

Italy: Order line types can be sent now to the interface.

Oracle Order Import Exception Report will be used to identify errors.

CR1460e: Returns can now be imported

Accessed By: Harte,Jason Effective

Access Date: 09-Sep-2013 12:04:59 PM GMT Page 12 of 30

There will be no modifiers sent in the ETMS file.