E1-VCP Mapping 2011-01-12 AIA 3 1 Release

This document defines the mapping for the E1 to VCP integration and the
There are two sets of worksheets: E1:Extract/Import file Mapping and ODS:File Mapping
ODS Mapping
Notes:
Sections highlighted at the end of the worksheet define high level selection criteria Field Mappings/Logic may include: * A mapping from an extracted file * A mapping from a User Defined Data file * A Parameter value (defined in User Defined Data spreadsheet) * A literal value e.g. "2", <null> etc. Entity Name
Flow from E1 Extracts to VCP

Entity Group
*02 Calendar *02 Calendar *02 Calendar *02 Calendar *02 Calendar *99 Existing Demantra Integ *04 Unit of Measure *04 Unit of Measure *04 Unit of Measure *05 Analysis Codes *05 Analysis Codes *05 Analysis Codes *07 Trading Partners *07 Trading Partners *07 Trading Partners *07 Trading Partners *07 Trading Partners *07 Trading Partners *07 Trading Partners *07 Trading Partners *07 Trading Partners *10 Item *10 Item *10 Item *10 Item *10 Item *10 Item *10 Item *15 Item Subst/etc. *30 Resources
Calendars Workday Patterns Shift Times Calendar Exceptions Shift Exceptions CalendarAssignments Units of Measures
Units of Measure Conversions Units of Measure Class Conversions Demand Classes
Sales Channel Planners Trading Partners - Suppliers Trading Partners - Customers Trading Partners - Organizations Trading Partner Sites - Suppliers Trading Partner Sites - Customers Trading Partner Sites - Organizations
Location Associations - Suppliers Location Associations - Customers Location Associations - Organizations Items - Main Items - Master Product Families
Category Sets Item Categories Safety Stocks

Onhand Supplies
Price List Item Substitutes Resource Groups
*30 Resources *30 Resources *40 Routings *40 Routings *40 Routings *50 BOMs *50 BOMs *55 Change Over Tables *55 Change Over Tables *55 Change Over Tables *63 Distribution and Supply Setup *63 Distribution and Supply Setup *63 Distribution and Supply Setup *63 Distribution and Supply Setup *63 Distribution and Supply Setup *63 Distribution and Supply Setup *63 Distribution and Supply Setup *63 Distribution and Supply Setup *65 Supplies Transactions *65 Supplies Transactions *65 Supplies Transactions *65 Supplies Transactions *68 Demand Transactions *68 Demand Transactions *68 Demand Transactions *68 Demand Transactions *70 Work Orders *70 Work Orders *70 Work Orders *80 Demantra Flat file extracts *80 Demantra Flat file extracts *80 Demantra Flat file extracts *80 Demantra Flat file extracts *80 Demantra Flat file extracts *80 Demantra Flat file extracts
Flow from VCP Plans to E1
Resources
Resource Shifts
Routings Routing Operations Operation Resources Bills of Material Headers Bills of Material Components
Resource Setups Setup Transitions Standard Operation Resources
Shipping Methods - Purchasing Shipping Methods - Distribution Shipping Methods - Sales Supplier Items Item Sourcing - Purchasing Item Sourcing - Inter Org Item Sourcing - Manufacturing Item Sourcing - Customers Purchase Order Supplies Requisition Supplies Intransit Supplies - Purchase Orders Intransit Supplies - Transfer Orders Forecast Demands Forecast Designators
Sales Order Demands (Sales Orders) Sales Order Demands (Transfer Orders) Work Order Supplies
Work Order Component Demands Resource Requirements

Demand History List Price ItemCost.txt Price History APConfirm.txt Deductions.txt Purchaseplan deploymentplan - Main deploymentplan - DRP Detailed Production Plan Master Production Plan Forecast.txt
*90 Publish Files into E1 *90 Publish Files into E1 *90 Publish Files into E1 *90 Publish Files into E1 *90 Publish Files into E1 *95 Demantra Flat file updates
*95 Demantra Flat file updates *95 Demantra Flat file updates *95 Demantra Flat file updates *95 Demantra Flat file updates
PromotionPricing Delete_PromotionPricing DeductionDisposition Claim
E1 Mapping
Worksheets for XML files have the suffix ".xml" in the work sheet name Worksheets for flat files will have ".txt" in the work sheet name (followed by the parent UBE that generates them)
Column headings for XML files

E1 Table E1 Field XML Field Name XML Object Name Notes Required Key Missing in E1 Integration Use The mapping appears in XML Entity/XML field name order (that is, how they appear in the XML file)
Column headings for flat files (.txt). These files are suffixed with the parent UBE that generates it
E1 Column E1 Name E1 Table E1 Integration Notes
File mapping definitions

E1 Extracts
Base.xml BeginningInventory.xml Customer.xml Distribution.xml Manufacturing.xml PurchaseOrders.xml SalesOrders.xml Supplier.xml TransferOrders.xml TimeSeries.xml WorkOrders.xml Calendar.txt (R34A705) SalesOrderHistory.txt (R34A400) PriceList.txt (R34A400) PriceHistory.txt (R34A400)
E1 Imports
DeploymentPlan.xml PurchasePlan.xml MasterProductionPlan.xml
DetailedProductionPlan.xml EnterpriseForecast.xml
Unused ODS Legacy Mapping

Flow from E1 Extracts to VCP
Entity Group *70 Work Orders *30 Resources *05 Base Data *30 Resources *55 Demands *55 Demands *55 Demands *55 Demands *58 Forecasts *65 Supplies *65 Supplies *15 Item Subst/etc. *40 Routings *68 Demand Transactions *68 Demand Transactions *50 BOMs *50 BOMs *95 Other *98 Out of Scope *98 Out of Scope *98 Out of Scope *98 Out of Scope *98 Out of Scope *98 Out of Scope *98 Out of Scope *98 Out of Scope *99 CP *99 CP *99 CP *99 CP *99 CP *99 Not Needed *99 Not Needed *99 Not Needed *99 Not Needed *99 Not Needed *99 Existing Demantra Integ *99 Existing Demantra Integ *99 Old Demand Planning *99 Old Demand Planning *99 Old Demand Planning *99 Old Demand Planning *99 Old Demand Planning Entity Name Fiscal Calendars UOM Conversions Resources Availability Demand Schedule Demands Demand Schedule Designators Plan Order Designators Manufacturing Forecast# Reservations Plan Order Supplies Supply Demand Currency Conversions ItemRelationships Operation Networks Price List# Booking and Shipment History Co Products Component Substitute Partner Contacts Project Tasks Sub Inventories Supplier Capacities Supplier Flex Fences IROSupplies IRODemand EROSupplies ERODemand Company Users Customer Items Groups Group Company Associations Serial Number Details OSFM Material Requirement OSFM Operation Resource OSFM Operation OSFM Operation Network Profile Shipment Data# Booking Data# Composite Calendars# Custom Stream Data# Level Associations LevelOrgAsscns Level Values
*99 Old Demand Planning
Setup Parameters
to VCP integration and the return publish
worksheet define high level selection criteria References to fields from the files use the following structure: For XML files: "<File name>:<XML Object name>:<XML field name>" For flat files (including User Defined Data) "<File name>:<Field name>" OA Template File name
Calendar WorkdayPatterns ShiftTime CalendarException ShiftException CalendarAssignments UOM UOMConversion UOMClassConversion DemandClass SalesChannel Planner TradingPartner TradingPartner TradingPartner TradingPartnerSite TradingPartnerSite TradingPartnerSite LocationAssociation LocationAssociation LocationAssociation Item Item CategorySet Category SafetyStock SupplyOnhand Price List ItemSubstitutes ResourceGroup
DepartmentResource ResourceShift Routing RoutingOperation OperationResource BOM BOMComponent Resource Setups Setup Transitions Standard Operation Resources ShipmentMethod ShipmentMethod ShipmentMethod SupplierItem SourcingRule SourcingRule SourcingRule SourcingRule PurchaseOrderSupply PurchaseRequisitionSupply SupplyInTransit SupplyInTransit DemandForecast Designator SalesOrder SalesOrder WorkOrderSupply DemandWorkOrder ResourceDemand DemHistory.dat (flat file) ListPrice.txt ItemCost.txt PriceHistory.txt APConfirm.txt Deductions.txt Publish Purchase Plan to E1 Publish Transfers to E1 Publish Transfers to E1 Publish Work Orders to E1 Publish work order (deletions) to E1 Publish Forecast.txt to E1
Publish Promotion Pricing to E1 Publish "Delete Promotion Pricing" to E1 Publish Deduction Dispositions to E1 Publish Claims to E1
arent UBE that generates them)
The table in E1 where the data is sourced from The field name in the above table for this data item The field (or tag) name used in the XML file Any processing notes sasociated with this entry Is the field a required field Is this field part of the key for this entity This XML field is defined in the XML file definition but is not supported / populated by E1 Internal only
name order (that is, how they appear in the XML file)
th the parent UBE that generates it

The field name in the above table for this data item The descriptive name for the field name The table in E1 where the data is sourced from Any additional notes
OA Template File name Time DPUOMConversion ResourceChange DemandMDS DesignatorMDS DesignatorPlanOrder ManufacturingForecast# Reservations PlannedOrderSupply SupplyDemand CurrencyConversion ItemRelationship OperationNetwork PriceList# DemHistory COProduct ComponentSubstitute PartnerContact Project SubInventory SupplierCapacity SupplierFlexFence IROSupplies IRODemand EROSupplies ERODemand CompanyUser CustomerItem Group GroupCompany SerialNumber OSFMMaterialRequirement OSFMOperationResource OSFMOperation OSFMOperationNetwork Profile ShipmentData# BookingData# CompositeCalendar# CSData# LevelAssociation LevelOrgAsscns LevelValue
SetupParameter
n publish
Not used in integration Not used in integration Not used in integration Not used in integration
s not supported / populated by E1
Table Description VCP-ODS
CALENDAR_CODE CALENDAR_START_DATE CALENDAR_END_DATE QUARTERLY_CALENDAR_TYPE SR_INSTANCE_CODE DESCRIPTION WEEK_START_DAY
OVERWRITE_FLAG
COMPANY_NAME
MSC_CALENDARS
MSC_CALENDARS stores the definition of your workday calendar Description
Workday calendar identifier. Calendar code and source instance code should be unique. Beginning date for the calendar Ending date for the calendar Quarterly calendar type code. Valid values are: 1 - 4/4/5 Week pattern, 2 - 5/4/4 Week pattern, 3 - Calendar months, 4 - 13 Periods. Source instance code defined on the planning server Description of the calendar Valid values are: 1 - Monday, 2 - First day of the calendar Valid values are: Y - Yes, N - No. If the value is null then by default the value is taken as N. This flag determines whether to overwrite an existing calendar or not. Required only for Collaborative Planning. You should provide the party name with which the company is registered in Collaborative Planning. For a planning (APS) only environment, this should be left null.
Logic
Fields Referenced Calendar.txt:BranchPlant Calendar.txt:WorkCenter Calendar.txt:Calendar Type Calendar.txt:Calendar Name
E1 Table E1 Field F0007 F0007 F0007 F0007 MMCU MCU WDCT WDCK
Refer to Comment for detailed processing Parameters.Base_Effective_Date Parameter.Calendar_End_Offset + Plan Option.Base_Date Parameter.Quarterly_Calendar_Type Parameter.Source_Instance <same as Calendar Code> Parameter. Work Start Day Should be N when loaded first time that particular code otherwise Y
Parameter.CP_Company_Name
Return to File Definitions Comment
CALENDAR_CODE DAYS_ON DAYS_OFF SR_INSTANCE_CODE
SHIFT_NUM SHIFT_NAME DESCRIPTION
COMPANY_NAME
MSC_WORKDAY_PATTERNS
Workday calendar identifier. Should refer to a valid calendar code in MSC_CALENDARS.
Source instance code defined on the planning server.
Either this or SHIFT_NAME may be provided to identify a shift. If both not there it means that the pattern is valid for the entire calendar. Either this or SHIFT_NUM may be provided to identify a shift. If both are not there it means that the pattern is valid for the entire calendar. Description Required only for Collaborative Planning. You should provide the party name with which the company is registered in Collaborative Planning. For a planning (APS) only environment, this should be left null.
Logic
E1 Table F0007 F0007 F0007 F0007
E1 Field MMCU MCU WDCT WDCK
Refer to Comment for detailed processing Parameter.Days On Parameter.Days Off Parameter.Source_Instance "Shift Information".Shift Number (shift numbers relavent for this calendar can be deduced from searching the extract extensions of Work Centre) "Shift Information".Shift Name "Shift Information".Shift Description
CALENDAR_CODE SHIFT_NAME SR_INSTANCE_CODE FROM_TIME TO_TIME
COMPANY_NAME
This table will be primarily formed by joining the Calendar file with the user data "ShiftTimes".
MSC_SHIFT_TIMES
Workday calendar identifier. Should refer to a valid calendar code in MSC_CALENDARS. Source instance code defined on the planning server. Shift time should not overlap with the already-defined timings Shift time should not overlap with the already defined timings Required only for Collaborative Planning. You should provide the party name with which the company is registered in Collaborative Planning. For a planning (APS) only environment, this should be left null.
This table will be primarily formed by joining the Calendar file with the user data "ShiftTimes".
Logic
E1 Table F0007 F0007 F0007 F0007
Refer to Comment for detailed processing "Shift Information".Shift Name (numeric) "Parameters".Source_Instance "Shift Information Details".From Time converted to seconds "Shift Information Details".To Time converted to seconds
ith the user
MSC_CALENDAR_EXCEPTIONS EXCEPTION_DATE EXCEPTION_TYPE SR_INSTANCE_CODE
COMPANY_NAME
OBDWCAL gives us the actual working days, Where there is a difference, there will be a CalendarException record created
MSC_CALENDAR_EXCEPTIONS
MSC_CALENDAR_EXCEPTIONS stores exception dates for a calendar. You can define these exception dates to be working or non-working d generate your workday calendar Description
Workday calendar identifier. Should refer to a valid calendar code in MSC_CALENDARS. Should be within the calendar start date and end date. Exception type. Valid values are: 1- On, 2 - Off. Source instance code defined on the planning server Required only for Collaborative Planning. You should provide the party name with which the company is registered in Collaborative Planning. For a planning (APS) only environment, this should be left null
OBDWCAL gives us the actual working days, Where there is a difference, there will be a CalendarException record created
u can define these exception dates to be working or non-working days. The workday calendar program uses this information to Logic Fields Referenced Calendar.txt:BranchPlant Calendar.txt:WorkCenter Calendar.txt:Calendar Type Calendar.txt:Calendar Name E1 Table F0007 F0007 F0007 F0007 E1 Field MMCU MCU WDCT WDCK
Refer to Comment for detailed processing Where there is a conflict between OBDWCAL and WorkingDays Nature of conflict Parameter.Source_Instance
Return to File Definitions
Comment
CALENDAR_CODE EXCEPTION_DATE EXCEPTION_TYPE SR_INSTANCE_CODE SHIFT_NAME
COMPANY_NAME
MSC_SHIFT_EXCEPTIONS
Workday calendar shift exceptions Description
Workday calendar identifier. Should refer to a valid calendar code in MSC_CALENDARS. Exception date. Should be within the calendar period Exception type. Valid values are: 1 - On, 2 - Off. Source instance code defined on the planning server. Name or SHIFT_NUM may be provided to identify a shift. Required only for Collaborative Planning. You should provide the party name with which the company is registered in Collaborative Planning. For a planning (APS) only environment, this should be left null.
OBDWCAL gives us the actual working days, Where there is a difference, there will be a ShiftException record created
Logic
E1 Table F0007 F0007 F0007 F0007
Refer to Comment for detailed processing Where there is a conflict between OBDECAL and WorkingDays Nature of conflict Parameter.Source_Instance "Shift Information".Shift Name
difference,
CALENDAR_CODE Calendar Type Association Type @ Partner Type Partner Name Partner Site Code Organization Code Source Instance Code Carrier Partner Code Ship Method Code Company Name Association Level
@ Association Type Valid values are: Value 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Association type 10,11 7,8 9 5,6 1,2 3 4
Calendar Assignment.dat
Assign suppliers to calendars Description
Workday calendar identifier. Should refer to a valid calendar code in MSC_CALENDARS. Valid values are RECEIVING, 'SHIPPING, CARRIER' Valid values are 1-15 Valid values are 1-supplier, 2- customer, 3- Org, 4- Carrier Partner Name (Refer table below) Partner site code (Refer table below) Organization code (Refer table below) Source Instance Code is defined on the planning server. Carrier partner code (Refer table below) Ship method code Company Name Valid values are 1,2,3,4
For Each Supplier in supplier.xml, if ("S",parameter.field_delimiter Parameter.Master_Branch, parameter.field_delimiter, supplier.xml:supplierList:supplier:supplierCode) exists in Calendar.dat, create a Calendar Assignment record Same logic as specifying calendar in "Trading Partner - 1"
values are: Description Vendor Customer Organization Carrier Vendor Site Customer Site Carrier/Vendor Carrier/Customer Carrier/Organization Carrier/Vendor Site Carrier/Customer Site Item/Vendor Item/Vendor Site Calendar Association Type
Partner_name Not Null Not Null Not Null Not Null
Logic
Fields Referenced
E1 Table
E1 Field
"S",parameter.field_delimiter Parameter.Master_Branch, parameter.field_delimiter, supplier.xml:supplierList:supplier supplier.xml:supplierList:supplier:supplierCode :supplierCode F43090 "SHIPPING" "5" "1" Supplier.xml:supplierList:supplier:name Supplier.xml:supplierList:supplier :name F43090 supplier.xml:supplierList:supplier :supplierCode F43090
AN8
ALPH AN8
Supplier.xml:supplierList:supplier:supplierCode <null> Parameter.Source_Instance <null> <null> <null> decode(ASSOCIATION_TYPE,11,1,10,1,9,3,8,3,7,3,6,2,5,2,4,4,3,4,2,4,1,4)
endar.dat,
Organization Code
Not Null
Not Null
UNIT_OF_MEASURE
UOM_CODE
UOM_CLASS
BASE_UOM_FLAG SR_INSTANCE_CODE DISABLE_DATE DESCRIPTION
COMPANY_NAME
MSC_UNITS_OF_MEASURE
Unit of measure definitions Description
Unit Of Measure
UOM Code
UOM Class
Whether Base UOM (Yes) or not (No). One class can have one and only one Base UOM. Source instance code defined on the planning server.
Required only for Collaborative Planning. You should provide the party name with which the company is registered in Collaborative Planning. For a planning (APS) only environment, this should be left null.
Aggregated values for Base.xml:item for each of the listed UOMs.
Aggregated values for Base.xml:item for each of the listed UOMs. REFER TO FDD FOR DETAILED PROCESSING STEPS
Logic
Fields Referenced
E1 Table
E1 Field
Base.xml:item:planningUom
F34A10
see comment
Base.xml:item:planningUom or Base.xml:item:shippingUom or Base.xml:item:weightUom or Base.xml:item:volumeUom or Base.xml:itemUom:toUOM or Manufacturing.xml:operation:operationdur:durationU nit or Parameters.Base_Time_UOM REFER to FDD for detailed processing steps Base.xml:item:planningUom or Base.xml:item:shippingUom or Base.xml:item:weightUom or Base.xml:item:volumeUom or Base.xml:itemUom:toUOM or Manufacturing.xml:operation:runTimeUnit or Parameters.Base_Time_UOM Base.xml:item:planningUom need to look up or Base.xml:item:shippingUom or Base.xml:item:weightUom or Base.xml:item:volumeUom or Base.xml:itemUom:toUOM "toUOMType" (Count if null)
Base.xml:item:shippingUom Base.xml:item:weightUom Base.xml:item:volumeUom Base.xml:itemUom:toUOM
F34A10 F4101 F4101 V41003A
assignment UWUM UVM1
Manufacturing.xml:operation:op erationdur:durationUnit
see comment
see UNIT_OF_MEASURE
"Time" for records from Manufactoring.xml or see UNIT_OF_MEASURE Parameters.Base_Time_UOM Base.xml:itemUom:toUomType "Y" if UOM =Parameter.Base_Time_UOM|Parameter.Base_UOM _Volume | Weight | Count and to_uom_type = "Time"|"Volume"|Weight"|"Count" otherwise "N" Parameter.Source_Instance <null> sames as "Unit Of Measure"
F34A30
Return to File Definitions Comment CMUM is retrieved from F34A10 where F34A10.SY = '34A' assignment = if F34A10.CMUM = '01', then planningUom = F4101. UOM1 if F34A10.CMUM = '02', then planningUom = F4101.UOM2 if F34A10.CMUM = '03', then planningUom = F4101.UOM3 if F34A10.CMUM = '04', then planningUom = F4101.UOM4 if F34A10.CMUM = '05', then planningUom = F4101.UOM6 if F34A10.CMUM = '06', then planningUom = F4101.UOM8 if F34A10.CMUM = '07', then planningUom = F4101.UOM9 if F34A10.CMUM = '08', then planningUom = F4101.UWUM SVUM is retrieved from F34A10 where F34A10.SY = '34A' assignment = same logic as planningUom except that F34A10.SVUM is used for comparison
assignment = if F34A120.TUOM = 'S' then durationUnit = "Seconds" else if F34A120.TUOM = 'M' then durationUnit = "Minutes" else if F34A120.TUOM = 'H' then durationUnit = "Hours" else if F34A120.TUOM = 'D' then durationUnit = "Days" else durationUnit = "Hours"
UNIT_OF_MEASURE UOM_CODE UOM_CLASS
CONVERSION_RATE
DEFAULT_CONVERSION_FLAG SR_INSTANCE_CODE DISABLE_DATE ITEM_NAME
COMPANY_NAME
MSC_UOM_CONVERSIONS
This table stores the different non-base unit of measures known conversions Description
Primary unit of measure long name. You should refer to a valid unit of measure in MSC_UNITS_OF_MEASURE. Destination unit of measure short name. You should refer to a valid unit of measure code in MSC_UNITS_OF_MEASURE. Destination class of conversion.
Conversion rate from conversion unit to base unit of class. Conversion rate should be greater than zero. Indicates whether the conversion factor applies for this particular item, or if it is defined as the standard conversion factor. Valid values are: 1- Yes, 2 - No. Source instance code defined on the planning server. Date when the conversion is no longer valid to be used in the system (transactions, etc). Item name should already be defined on the planning server if DEFAULT_CONVERSION_FLAG = N Required only for Collaborative Planning. You should provide the party name with which the company is registered in Collaborative Planning. For a planning (APS) only environment, this should be left null.
Create Records for UOM conversions where the fromUOM (UNIT_OF_MEASURE) and the toUOM (UOM_CODE) are for the SAME class. Traverse itemUOMlist, for each record look up item and use the planning UOM as the source UOM for this record ONLY do this for records with Base flag set to "Y" REFER TO FDD FOR DETAILED PROCESSING STEPS Base_UOM_Conv(#) = if primary UOM = Parameters. Base_UOM_Volume/Weight/Count then Base_UOM_Conv=1 else Base_UOM_Conv = Base.xml:itemUOM where itemCode=current item and toUom=Parameters. Base_UOM_Volume/Weight/Count toUomType=Current Class
toUomType=Current Class
sions Logic Fields Referenced E1 Table E1 Field
Base.xml:itemUomList:toUom REFER TO FDD FOR DETAILED PROCESSING STEPS Base.xml:itemUomList:toUom Class for the above UOM_CODE field
Base.xml:itemUom:toUom see UNIT_OF_MEASURE see UOM_CLASS from Unit of Measure mapping
F41002
see comment
1/Base.xml:itemUom:factor * Base_UOM_Conv(# see below) Base.xml:itemUom:factor
F41002
see comment
"1" if from itemUom Parameter.Source_Instance <null> Base.xml:itemUom:itemCode Base.xml:itemUom:itemCode F41002 ITM
Return to File Definitions Comment assignment = if F41002.UM = planningUom (value assigned in the item Object), then toUom = F41002.RUM else toUom = F41002.UM From = X To = Y Factor = C if (X = planning UOM) ToUom = Y and factor = C else (toUom = X and Factor = 1/C)
assignment = if F41002.UM = planningUom (value assigned in the item Object), then factor = the inversion of F41002.CONV else factor = F41002.CONV where F41002.UM = planningUom
FROM_UNIT_OF_MEASURE FROM_UOM_CODE
FROM_UOM_CLASS
TO_UNIT_OF_MEASURE
TO_UOM_CODE TO_UOM_CLASS
CONVERSION_RATE SR_INSTANCE_CODE DISABLE_DATE ITEM_NAME
COMPANY_NAME
MSC_UOM_CLASS_CONVERSIONS
Conversions between base units of two different classes Description
Base unit of measure of the item's base class. It should refer to a valid unit of measure if MSC_UNITS_OF_MEASURE with base_uom_flag = Y. Base unit of measure short name for the item's base class. It should refer to a valid unit of measure if MSC_UNITS_OF_MEASURE with base_uom_flag = Y.
Base class of the item.
Base unit of the class to which the conversion is defined. It should refer to a valid unit of measure if MSC_UNITS_OF_MEASURE with base_uom_flag = Y. Base unit short name of the class to which the conversion is defined. It should refer to a valid unit of measure if MSC_UNITS_OF_MEASURE with base_uom_flag = Y. Class to which the conversion is defined.
Conversion rate from the item's class base unit to the "To" class base unit. Conversion rate should be greater than zero. Source instance code defined on the planner server. Date when the define interclass conversion rate can no longer be used. Inventory item name. Item name should be defined in MSC_SYSTEM_ITEMS table. Required only for Collaborative Planning. You should provide the party name with which the company is registered in Collaborative Planning. For a planning (APS) only environment, this should be left null.
Not needed when toUOM is in the base UOM
Logic
Fields Referenced
E1 Table
E1 Field
Base.xml:item:planningUom REFER TO FDD FOR DETAILED PROCESSING STEPS Base.xml:item:planningUom
Base.xml:item:planningUom see FROM_UNIT_OF_MEASURE see UOM_CLASS for "From" Unit from Unit of Measure mapping
F34A10
see comment
From UOM.dat for From UOM Code
Base.xml:itemUomList:toUom
Base.xml:itemUom:toUom
F41002
see comment
Base.xml:itemUomList:toUom From UOM.dat for To UOM Code
See TO_UNIT_OF_MEASURE see UOM_CLASS for "To" Unit to Unit of Measure mapping
Base.xml:itemUom:factor Parameter.Source_Instance <null> Base.xml:itemUom:itemCode
Base.xml:itemUom:factor
F41002
see comment
Base.xml:itemUom:itemCode
F41002
ITM
Return to File Definitions Comment CMUM is retrieved from F34A10 where F34A10.SY = '34A' assignment = if F34A10.CMUM = '01', then planningUom = F4101. UOM1 if F34A10.CMUM = '02', then planningUom = F4101.UOM2 if F34A10.CMUM = '03', then planningUom = F4101.UOM3 if F34A10.CMUM = '04', then planningUom = F4101.UOM4 if F34A10.CMUM = '05', then planningUom = F4101.UOM6 if F34A10.CMUM = '06', then planningUom = F4101.UOM8 if F34A10.CMUM = '07', then planningUom = F4101.UOM9 if F34A10.CMUM = '08', then planningUom = F4101.UWUM
assignment = if F41002.UM = planningUom (value assignment = if F41002.UM = planningUom (value assigned in the assigned in the item Object), then toUom = item Object), then toUom = F41002.RUM F41002.RUM else toUom = else toUom = F41002.UM F41002.UM From = X To = Y Factor = C if (X = planning UOM) ToUom = Y and factor = C else (toUom = X and Factor = 1/C) From = X To = Y Factor = C if (X = planning UOM) ToUom = Y and factor = C else (toUom = X and Factor = 1/C)
assignment = if F41002.UM = planningUom (value assigned in the item Object), then factor = the inversion of F41002.CONV else factor = F41002.CONV where F41002.UM = planningUom
Demand Class
Meaning
Description From Date To Date Enabled Flag Source Instance Code
Company Name Deleted Flag
MSC_DEMAND_CLASSES
This table stores the demand classes Description
Name of the demand class.
Meaning
Description of the demand class. From Date To Date Enabled Flag Source instance code defined on the planning server. Required only for Collaborative Planning. You should provide the party name with which the company is registered in CP. For a planning (APS) only environment, this should be left null. Valid values are: 1 - Yes, 2 - No. If 1, then this row is deleted.
Derived from CustomerGroup using the Parameter "Demand_Class_Category" (refer to complex modelling on Category Codes in FDD)
Logic Customer Categories pointed to by Parameter.Demand_Class_Category Refer to the FDD Complex modelling seciton on categroy codes Customer Categories pointed to by Parameter.Demand_Class_Category Refer to the FDD Complex modelling section on category codes If customergroup:description is not null,use customergroup:description;else use customergroup:name Parameters.Base_Effective_Date <Null> "1" Parameter.Source_Instance
Fields Referenced
E1 Table
E1 Field
Customer.xml:customerGroup:na me F0101
concatenation
see "Demand Class" Customer.xml:customerGroup:de scription F0005
DL01
Parameter.CP_Company_Name "2"
egory Codes
concatenation = data dictionary description for data items AC01 AC30|F0101.AC01 - AC30
assignment = if F41002.UM = planningUom (value assigned in the item Object), then toUom =
Lookup Code
Meaning
Description
From Date To Date Enabled Flag Source Instance Code
Company Name Deleted Flag LOOKUP_TYPE
MSC_SALES_CHANNEL
This table stores the Sales Channels Description
Name of the sales channel.
Meaning
Description of the demand class.
From Date To Date Enabled Flag Source instance code defined on the planning server. Required only for Collaborative Planning. You should provide the party name with which the company is registered in CP. For a planning (APS) only environment, this should be left null. Valid values are: 1 - Yes, 2 - No. If 1, then this row is deleted.
Derived from CustomerGroup using the Parameter "Sales_Channel_Category" (refer to complex modelling on Category Codes in FDD)
Logic The parameter "Sales_Channel_Category" indicates which customer groups are to be used to create the sales channels. Refer to the FDD on complex modeling. Customer Categories pointed to by Parameter.Demand_Class_Category Refer to the FDD Complex modelling section on category codes If customergroup:description is not null,use customergroup:description;else use customergroup:name
Fields Referenced
E1 Table
E1 Field
Customer.xml:customerGroup:na me F0101
concatenation
see "Demand Class" Customer.xml:customerGroup:de scription F0005
DL01
Parameters.Base_Effective_Date <Null> "1" Parameter.Source_Instance
Parameter.CP_Company_Name "2" "SALES CHANNEL"
egory Codes
assignment = if F41002.UM = planningUom (value assigned in the item Object), then toUom = F41002.RUM else toUom = F41002.UM From = X To = Y Factor = C if (X = planning UOM) ToUom = Y and factor = C else (toUom = X and Factor = 1/C)
PLANNER_CODE ORGANIZATION_CODE DESCRIPTION
DISABLE_DATE ELECTRONIC_MAIL_ADDRESS CURRENT_EMPLOYEE_FLAG USER_NAME SR_INSTANCE_CODE
COMPANY_NAME DELETED_FLAG
MSC_PLANNERS
This table stores and maintains a list of planner codes. Description
Planner code Organization code in which the planner code is being created Description of code
Date on which the planner record is disable. Planner's Email address. Flag indicating whether the employee record is current. Planner's user name. Source instance code defined on the planning server. Required only for Collaborative Planning. You should provide the party name with which the company is registered in Collaborative Planning. For a planning (APS) only environment, this should be left null. Valid values are: 1 - Yes, 2- No. If 1 then this row is deleted
Aggregrate plannernumber in itembranch by branch and planner
Logic
Fields Referenced
E1 Table
E1 Field
Base.xml: itemBranch.plannerNumber Base.xml: itemBranch:branchCode Base.xml: itemBranch.plannerName
Base.xml: itemBranch.plannerNumber Base.xml: itemBranch:branchCode Base.xml: itemBranch.plannerName
F4102 F4102 F0101
ANPL MCU ALPH
<null> Base.xml: itemBranch.plannerEmail 1 Base.xml: itemBranch.plannerNumber Parameter.Source_Instance Base.xml: itemBranch.plannerNumber F4102 ANPL Base.xml: itemBranch.plannerEmail F01151 EMAL
<null> "2"
Table Description VCP-ODS PARTNER_TYPE PARTNER_NAME SR_INSTANCE_CODE
ORGANIZATION_CODE DISABLE_DATE STATUS MASTER_ORGANIZATION_CODE PARTNER_NUMBER
CALENDAR_CODE MAXIMUM_WEIGHT MAXIMUM_VOLUME WEIGHT_UOM VOLUME_UOM PROJECT_REFERENCE_ENABLED PROJECT_CONTROL_LEVEL DEMAND_LATENESS_COST SUPPLIER_CAP_OVERUTIL_COST RESOURCE_CAP_OVERUTIL_COST TRANSPORT_CAP_OVER_UTIL_COST USE_PHANTOM_ROUTINGS INHERIT_PHANTOM_OP_SEQ DEFAULT_ATP_RULE_NAME DEFAULT_DEMAND_CLASS MATERIAL_ACCOUNT EXPENSE_ACCOUNT ORGANIZATION_TYPE SERVICE_LEVEL
COMPANY_NAME PLANNING_ENABLED_FLAG MODELED_supplier_NAME MODELED_supplier_SITE_CODE MODELED_SUPPLIER_NAME MODELED_SUPPLIER_SITE_CODE INHERIT_OC_OP_SEQ_NUM
RESOURCE_TYPE
MSC_TRADING_PARTNERS (Suppliers)
This table stores information about the different organizations: customers, vendors, and planned organizations. Suppliers in this case Description Valid values are: 1 - Vendor, 2 - supplier, 3 - Organization , 4 - Others.
Source instance code defined on the planning server. Organization name of the organization being loaded. Required only if partner type is Organization. Valid values are: 1 - Active, 2 - Inactive. For example, a DUNSNUMBER is the Dun & Bradstreet global identifier of organizations used in the classic commercial credit tracking service.
Calendar used for this partner. The code includes instance code and calendar code from the source apps. Weight capacity. Volume capacity. Weight unit of measure. Volume unit of measure. Flag indicates whether project references are allowed in the organization or not. Specifies whether project references are being tracked at the project or task level. Demand lateness cost. Supplier over-utilization cost. Resource over-utilization cost. The penalty cost for transportation capacity. Use phantom-routings flag. Inherit phantom op-sequence flag. Future
Valid value 1 (Discrete Org) Required only for Collaborative Planning. You should provide the party name with which the company is registered in Collaborative Planning. For a planning (APS) only environment, this should be left null. supplier that is modeled as inventory organization. supplier site which is modeled as inventory organization. Supplier that is modeled as inventory organization. Supplier site which is modeled as inventory organization. Value of profile option INHERIT_OPTION_CLASS_OP_SEQ Used in SRP only. Valid values are: 1 - Employee, NULL - supplier. This column should be used only for supplier. In other cases it should have NULL.
ers, vendors, and planned organizations. Suppliers in this case Logic "1" (Supplier) Supplier.xml:supplierList:supplier:name Parameter.Source_Instance
Fields Referenced
E1 Table
E1 Field
Supplier.xml:supplierList:supplier :name F43090
ALPH
<null> <null> "1" <null> Supplier.xml:supplierList:supplier:supplierCode Supplier.xml:supplierList:supplier :supplierCode F43090 AN8
if ("S",parameter.field_delimiter Parameter.Master_Branch, parameter.field_delimiter, supplier.xml:supplierList:supplier:supplierCode) exists in Calendar.dat then use this Supplier.xml:supplierList:supplier otherwise use <null> :supplierCode F43090 <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null>
AN8
Parameter.CP_Company_Name <null> <null> <null> <null> <null>
<null>
assignment = if F41002.UM = planningUom (value assigned in the item Object), then toUom = F41002.RUM else toUom =
Table Description VCP-ODS PARTNER_TYPE
PARTNER_NAME SR_INSTANCE_CODE
CALENDAR_CODE MAXIMUM_WEIGHT MAXIMUM_VOLUME WEIGHT_UOM VOLUME_UOM PROJECT_REFERENCE_ENABLED PROJECT_CONTROL_LEVEL DEMAND_LATENESS_COST SUPPLIER_CAP_OVERUTIL_COST RESOURCE_CAP_OVERUTIL_COST TRANSPORT_CAP_OVER_UTIL_COST USE_PHANTOM_ROUTINGS INHERIT_PHANTOM_OP_SEQ DEFAULT_ATP_RULE_NAME
DEFAULT_DEMAND_CLASS MATERIAL_ACCOUNT
EXPENSE_ACCOUNT ORGANIZATION_TYPE SERVICE_LEVEL
COMPANY_NAME PLANNING_ENABLED_FLAG MODELED_supplier_NAME MODELED_supplier_SITE_CODE MODELED_SUPPLIER_NAME MODELED_SUPPLIER_SITE_CODE INHERIT_OC_OP_SEQ_NUM
RESOURCE_TYPE CUSTOMER_NUMBER
CUSTOMER_CLASS_CODE
MSC_TRADING_PARTNERS Customers)
This table stores information about the different organizations: customers, vendors, and planned organizations. Customers in this case Description Valid values are: 1 - Vendor, 2 - supplier, 3 - Organization , 4 - Others.
Source instance code defined on the planning server.
Organization name of the organization being loaded. Required only if partner type is Organization. Valid values are: 1 - Active, 2 - Inactive. For example, a DUNSNUMBER is the Dun & Bradstreet global identifier of organizations used in the classic commercial credit tracking service.
Valid value 1 (Discrete Org) Required only for Collaborative Planning. You should provide the party name with which the company is registered in Collaborative Planning. For a planning (APS) only environment, this should be left null. supplier that is modeled as inventory organization. supplier site which is modeled as inventory organization. Supplier that is modeled as inventory organization. Supplier site which is modeled as inventory organization. Value of profile option INHERIT_OPTION_CLASS_OP_SEQ Used in SRP only. Valid values are: 1 - Employee, NULL - supplier. This column should be used only for supplier. In other cases it should have NULL.
PROPOSED Aug 11 bug 8787342
If <parentAddressNumber> or <parentName> is null, the set them to the current <customerCode> and <name> Check all <parentAddressNumber> records exist in Tcustomer.xml, if the parent exist then set <parentAddressNumber> and <parentName> to <customerCode> and <name> *** At this point all records should have a valid customer record for the parent *** Extract all the <parentAddressNumber> and aggregate by <parentAddressNumber> *** One record now exists for each parent to be created *** Using this key then create a TradingPartner(2) record based on the values in the <customer> record pointed to by parentAddressNumber Non key fields will be derived from the <customer> record pointed to by the aggregated parentAdderessNumber used above Non key fields will be derived from the <customer> record pointed to by the aggregated parentAdderessNumber used above
ers, vendors, and planned organizations. Customers in this case Logic "2" (Customer) Customer.xml:customer:parentName USE the record pointed to by the parentaddressnumber if null or zero use the current record Parameter.Source_Instance
Fields Referenced
E1 Table
E1 Field
Customer.xml:customer:parentN ame F0101
ALPH
<null> <null> <null> <null> Customer.xml:customer:parentAddressNumber (see the logic below)
Customer.xml:customer:parentA ddressNumber F43090
AN8
if ("C",parameter.field_delimiter, Parameter.Master_Branch, parameter.field_delimiter, customer.xml:customerList:customer:customerCode) exists in Calendar.dat then use this else <null>) USE the record pointed to by the Customer.xml:customer:parentA parentaddressnumber ddressNumber F43090 <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> From Customer.xml:customergroup. The group to use is determined by Parameter.Demand_Class_Category). Refer to the FDD on the handling of category codes. USE the record pointed to by the Customer.xml:customerGroup:na parentaddressnumber me F0101 <null>
AN8
concatenation
<null> <null> <null>
Parameter.CP_Company_Name <null> <null> <null> <null> <null> <null>
<null> Customer.xml:customer:parentAddressNumber (see the logic below)
Customer.xml:customer:parentA ddressNumber F43090
AN8
From Customer.xml:customergroup. The group to use is determined by Parameter.Customer_Class_Code_Category). Refer to the FDD on the handling of category codes. USE the record pointed to by the Customer.xml:customerGroup:na parentaddressnumber me F0101
concatenation
em to the current
the parent does not customerCode> and
d for the parent *** ntAddressNumber>
the values in the
ted to by the aggregated
ted to by the aggregated
F0101.AN8 = parentAddressNumber
Table Description VCP-ODS PARTNER_TYPE PARTNER_NAME SR_INSTANCE_CODE
CALENDAR_CODE MAXIMUM_WEIGHT MAXIMUM_VOLUME WEIGHT_UOM VOLUME_UOM PROJECT_REFERENCE_ENABLED PROJECT_CONTROL_LEVEL DEMAND_LATENESS_COST SUPPLIER_CAP_OVERUTIL_COST RESOURCE_CAP_OVERUTIL_COST TRANSPORT_CAP_OVER_UTIL_COST USE_PHANTOM_ROUTINGS INHERIT_PHANTOM_OP_SEQ DEFAULT_ATP_RULE_NAME DEFAULT_DEMAND_CLASS MATERIAL_ACCOUNT EXPENSE_ACCOUNT ORGANIZATION_TYPE SERVICE_LEVEL
COMPANY_NAME PLANNING_ENABLED_FLAG MODELED_CUSTOMER_NAME MODELED_CUSTOMER_SITE_CODE MODELED_SUPPLIER_NAME MODELED_SUPPLIER_SITE_CODE INHERIT_OC_OP_SEQ_NUM
RESOURCE_TYPE
OPERATING_UNIT_NAME
BUSINESS_GROUP_NAME
LEGAL_ENTITY_NAME CALENDAR_CODE Calendar Exception Set id
MSC_TRADING_PARTNERS (Branches/Organizations)
This table stores information about the different organizations: customers, vendors, and planned organizations.Organizations in this case Description Valid values are: 1 - Vendor, 2 - Customer, 3 - Organization , 4 - Others. Source instance code defined on the planning server. Organization name of the organization being loaded. Required only if partner type is Organization. Valid values are: 1 - Active, 2 - Inactive. Operating/financial unit For example, a DUNSNUMBER is the Dun & Bradstreet global identifier of organizations used in the classic commercial credit tracking service.
Valid value 1 (Discrete Org) Required only for Collaborative Planning. You should provide the party name with which the company is registered in Collaborative Planning. For a planning (APS) only environment, this should be left null. Customer that is modeled as inventory organization. Customer site which is modeled as inventory organization. Supplier that is modeled as inventory organization. Supplier site which is modeled as inventory organization. Value of profile option INHERIT_OPTION_CLASS_OP_SEQ Used in SRP only. Valid values are: 1 - Employee, NULL - customer. This column should be used only for customer. In other cases it should have NULL.
Not supported by OATemplate
ers, vendors, and planned organizations.Organizations in this case Logic "3" (Branch) Base.xml:branchList:branch:branchName Parameter.Source_Instance
Fields Referenced
E1 Table
E1 Field DL01
Base.xml:branchList:branch:branchName F0006
Base.xml:branchList:branch:branchCode <null> 1 Base.xml:branchList:branch:branchCode <null> if the calendar "M" + delimiter + branchCode" exists then use this. if the calendar "M" + delimiter + Parameter.Master Branch" exists then use this. Otherwise set to <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> Parameter.Phantom Routings flag(2) Parameter.Inherit phantom op-sequence flag("2") <null> <null> <null> <null> 1- Discrete (Process is not supported in phase one) <null>
Base.xml:branchList:branch:branchCode F41001
MCU
Parameter.CP_Company_Name Not used <null> <null> <null> <null> "2"
<null> used in SPP only
Category code pointed to by Parameters.Branch_Operating_Unit_Category Refer to the Complex Modeling section, on the use of Category Codes in the FDD Base.xml:branchGroup:name F0006 Category code pointed to by Parameters.Branch_Business_Group_Category Refer to the Complex Modeling section, on the use of Category Codes in the FDD Base.xml:branchGroup:name F0006 Category code pointed to by Parameters.Branch_Legal_Entity_Category Refer to the Complex Modeling section, on the use of Category Codes in the FDD Base.xml:branchGroup:name F0006 Parameter.Default_Currency_Code Bug 9711346 "-1"
category code value
category code value
category code value
possible category code groups = RP01 through RP30
Table Description VCP-ODS PARTNER_NAME TP_SITE_CODE PARTNER_TYPE
PARTNER_ADDRESS LOCATION LONGITUDE LATITUDE SR_INSTANCE_CODE
COMPANY_NAME SHIPPING_CONTROL
SOURCE_SR_TP_ID
SOURCE_SR_TP_SITE_ID OPERATING_UNIT_NAME COUNTRY
STATE CITY
POSTAL_CODE deleted flag
MSC_TRADING_PARTNER_SITES(Suppliers)
This table stores information about the different sites of an organization. Suppliers in this case Description PARTNER_NAME for PARTNER_TYPE 1 and 2; Organization code for PARTNER_TYPE 3 Trading partner site code (Not Null for PARTNER_TYPE 1 and 2 and NULL for 3) Valid values are: 1 - Vendor, 2 - Customer, 3 - Organization
Address of the partner site Location of the site (Not Null for PARTNER_TYPE -3 )
Source instance code defined on the planning server. Required only for Collaborative Planning. You should provide the party name with which the company is registered on the system. For a planning (APS) only environment, this should be left null. Valid Values - 'BUYER','SUPPLIER','NONE'. Please provide the Trading Partner ID for the Trading Partner in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Trading Partner Site ID for the Trading Partner Site in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Not supported by OATemplate
n. Suppliers in this case Logic Supplier.xml:supplierList:supplier:name Supplier.xml:supplierList:supplier:supplierCode "1"
Fields Referenced E1 Table Supplier.xml:supplierList:supplier :name F43090 Supplier.xml:supplierList:supplier :supplierCode F43090
E1 Field ALPH AN8
Supplier.xml:supplierList:supplier :city F0116 Supplier.xml:supplierList:suppl ier:stateProvince F0116 Supplier.xml:supplierList:suppl ier:country F0116
CTY1
ADDS
CTR Supplier.xml:supplierList:supplier:city/stateProvince/c ountry/postalCode seperated by Parameter.Field Supplier.xml:supplierList:suppl delimiter ier:postalCode F0116 ADDZ <null> Supplier.xml:supplierList:suppl ier:longitude Supplier.xml:supplierList:supplier:longitude Not mapped Supplier.xml:supplierList:suppl ier:latitude Supplier.xml:supplierList:supplier:latitude Not mapped Parameter.Source_Instance
<null> "SUPPLIER"
<null>
<null> <null> Supplier.xml:supplier:country Supplier.xml:supplier:stateProvince Supplier.xml:supplier:city Supplier.xml:supplier:postalCode 2 Supplier.xml:supplierList:suppl ier:country Supplier.xml:supplierList:suppl ier:stateProvince Supplier.xml:supplierList:suppl ier:city Supplier.xml:supplierList:suppl ier:postalCode F0116 F0116 F0116 F0116 CTR ADDS CTY1 ADDZ
PARTNER_NAME
TP_SITE_CODE PARTNER_TYPE
SOURCE_SR_TP_ID
SOURCE_SR_TP_SITE_ID OPERATING_UNIT_NAME
COUNTRY
STATE CITY
POSTAL_CODE
CUST_ACCOUNT_NUMBER deleted flag
Two records need to be created for each customer (one for the shipping and one for billing ) Where the values of these records differ they have a (1) or (2) recorded against them
MSC_TRADING_PARTNER_SITES(Customers)
This table stores information about the different sites of an organization. Customers in this case Description
PARTNER_NAME for PARTNER_TYPE 1 and 2; Organization code for PARTNER_TYPE 3
Trading partner site code (Not Null for PARTNER_TYPE 1 and 2 and NULL for 3) Valid values are: 1 - Vendor, 2 - Customer, 3 - Organization
Source instance code defined on the planning server. Required only for Collaborative Planning. You should provide the party name with which the company is registered on the system. For a planning (APS) only environment, this should be left null. Valid Values - 'BUYER','SUPPLIER','NONE'. Please provide the Trading Partner ID for the Trading Partner in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only.
Please provide the Trading Partner Site ID for the Trading Partner Site in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only.
Not supported by OATemplate
Two records need to be created for each customer (one for the shipping and one for billing ) Where the values of these records differ they have a (1) or (2) recorded against them
n. Customers in this case Logic 1.Customer.xml:customer.parentName 2.Customer.xml:customer.parentName if parentName is null or zero, set to Customer.xml:customer:name
Fields Referenced
E1 Table
E1 Field
Customer.xml:customer:parentN ame F0101 Customer.xml:customer:name F0101 Customer.xml:customer:custome rCode F03012 Customer.xml:customer:name F0101
ALPH ALPH AN8 ALPH
1.Customer.xml:customer:customerCode + Parameter.Field_Delimiter + Customer.xml:customer:name (max 30 chars) 2.customer:billToNumber + Parameter.Field_Delimiter + Customer.xml:customer:customerCode + Parameter.Field_Delimiter + Customer.xml:customer:billToName (max 30 chars) if billToName or billToNumber are null or zero, use customerCode and name "2"
Customer.xml:customer:billtona me F0101
ALPH
Customer.xml:customerList:custo mer:city F0116 Customer.xml:customerList:custo mer:stateProvince F0116 Customer.xml:customerList:custo mer:city:country F0116 Customer.xml:customerList:custo mer:postalCode F0116 Customer.xml:customer:custome rCode F03012 Customer.xml:customer:billtona me F0101 Customer.xml:customer:billToNumber
CTY1
ADDS
1.Customer.xml:customerList:customer:city/stateProv ince/country/postalCode seperated by Parameter.Field delimiter 2."E1_BILL_TO" + Parameters.Field_Delimiter + Customer.xml:customer.customerCode + Parameter.Field_Delimiter + customer:billToNumber + Parameter.Field_Delimiter + Customer.xml:customer:billToName If if billToName or billToNumber are null or zero, use customerCode and name instead <null> <null> <null> Parameter.Source_Instance
CTR
ADDZ
AN8
ALPH
<null> "BUYER"
<null>
<null> 1 & 2.Category code pointed to by Parameters.Operating_Unit_Category Refer to the Complex Modeling section, on the use of Customer.xml:customerGroup:na Category Codes in the FDD me F0101 Customer.xml:customerList:custo customer.xml:customer:country mer:city F0116 Customer.xml:customerList:custo customer.xml:customer:stateProvince mer:stateProvince F0116 Customer.xml:customerList:custo customer.xml:customer:city mer:city:country F0116 Customer.xml:customerList:custo customer.xml:customer:postalCode mer:postalCode F0116
concatenation CTY1 ADDS CTR ADDZ
Customer.xml:customer:parentAddressNumber F0150 PA8 Customer.xml:customer:parentAddressNumber ,if null Customer.xml:customer:custome customercode rCode F03012 AN8 2
ey have a (1)
B90CB124/D90CB124 DefaultSoldToShipTo passin F03012.an8 = mnShipToAddress get mnSoldToAddress assignment = if F41002.UM = planningUom (value assigned in the item Object), then toUom = F41002.RUM else toUom =
B90CB124/D90CB124 DefaultSoldToShipTo passin F03012.an8 = mnShipToAddress
Table Description VCP-ODS PARTNER_NAME TP_SITE_CODE PARTNER_TYPE
SOURCE_SR_TP_ID
SOURCE_SR_TP_SITE_ID OPERATING_UNIT_NAME COUNTRY
STATE CITY
POSTAL_CODE deleted flag
MSC_TRADING_PARTNER_SITES(Organizations)
This table stores information about the different sites of an organization. Organizations in this case Description PARTNER_NAME for PARTNER_TYPE 1 and 2; Organization code for PARTNER_TYPE 3 Trading partner site code (Not Null for PARTNER_TYPE 1 and 2 and NULL for 3) Valid values are: 1 - Vendor, 2 - Customer, 3 - Organization
Source instance code defined on the planning server. Required only for Collaborative Planning. You should provide the party name with which the company is registered on the system. For a planning (APS) only environment, this should be left null. Valid Values - 'BUYER','SUPPLIER','NONE'. Please provide the Trading Partner ID for the Trading Partner in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Trading Partner Site ID for the Trading Partner Site in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Not supported by OATemplate
n. Organizations in this case Logic Base.xml:branchList:branch:branchCode <null> "3"
Fields Referenced E1 Table Base.xml:branchList:branch:bran chCode F41001
E1 Field MCU
Base.xml:branchList:branch:city
F0116
CTY1
Base.xml:branchList:branch:state Province F0116 Base.xml:branchList:branch:coun try F0116 Base.xml:branchList:branch:city/stateProvince/countr Base.xml:branchList:branch:post y/postalCode seperated by Parameter.Field delimiter alCode F0116 Base.xml:branchList:branch:bran <null> chCode F41001 <null> <null> Parameter.Source_Instance
ADDS
CTR
ADDZ MCU
<null> "SUPPLIER"
<null>
<null> <null> Base.xml:branchList:branch:country Base.xml:branchList:branch:stateProvince Base.xml:branchList:branch:city Base.xml:branchList:branch:postalCode 2 Base.xml:branchList:branch:city Base.xml:branchList:branch:state Province Base.xml:branchList:branch:coun try Base.xml:branchList:branch:post alCode F0116 F0116 F0116 F0116 CTY1 ADDS CTR ADDZ
Table Description VCP-ODS LOCATION_CODE PARTNER_NAME TP_SITE_CODE PARTNER_TYPE SR_INSTANCE_CODE ORGANIZATION_CODE DELETED_FLAG
COMPANY_NAME
SOURCE_SR_TP_ID
SOURCE_SR_TP_SITE_ID
SOURCE_LOCATION_ID
MSC_LOCATION_ASSOCIATIONS(Suppliers)
This table stores location associations for organization, customer, customer sites, supplier, and supplier sites. Suppliers in this case Description Location code Partner name Trading partner site code Valid values are: 1 - Vendor, 2 - Customer, 3 - Organization, 4 - Others, etc. Source instance code defined on the planning server. Organization code for legacy users. Valid values are: 1 - Yes, 2 - No. If 1, then this row is deleted. Required only for Collaborative Planning. You should provide the party name with which the company is registered in CP. For a planning (APS) only environment, this should be left null. Please provide the Trading partner ID for the Trading partner in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Trading Partner Site ID for the Trading Partner Site in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Location ID for the Location in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only.
mer sites, supplier, and supplier sites. Suppliers in this case Logic Supplier.xml:supplierList:supplier:supplierCode Supplier.xml:supplierList:supplier:name Supplier.xml:supplierList:supplier:supplierCode "1" Parameter.Source_Instance SUPPLIER.SUPPLIERCODE "2"
Fields Referenced Supplier.xml:supplierList:supplier :supplierCode Supplier.xml:supplierList:supplier :name Supplier.xml:supplierList:supplier :supplierCode
E1 Table F43090 F43090 F43090
E1 Field AN8 ALPH AN8
<null>
<null>
<null>
COMPANY_NAME
SOURCE_SR_TP_ID
SOURCE_LOCATION_ID
mer sites, supplier, and supplier sites. Suppliers in this case Logic use the site code used for Trading Partner Sites (Partner Type=2) customer.xml:customerList:customer:name use the site code used for Trading Partner Sites (Partner Type=2) "2" Parameter.Source_Instance CUSTOMERCODE.CUSTOMERCODE "2"
Fields Referenced
E1 Table
E1 Field
Customer.xml:customer:name F0101
ALPH
<null>
<null>
<null>
COMPANY_NAME
SOURCE_SR_TP_ID
SOURCE_LOCATION_ID
mer sites, supplier, and supplier sites. Suppliers in this case Logic Base.xml:branchList:branch:branchCode Base.xml:branchList:branch:branchCode Base.xml:branchList:branch:branchCode "3" Parameter.Source_Instance Base.xml:branchList:branch:branchCode "2"
Fields Referenced Base.xml:branchList:branch:bran chCode Base.xml:branchList:branch:bran chCode Base.xml:branchList:branch:bran chCode
E1 Table F41001 F41001 F41001
E1 Field MCU MCU MCU
Base.xml:branchList:branch:bran chCode F41001
MCU
<null>
<null>
<null>
Table
MSC_ST_SYSTEM_ITEMS
Description VCP-ODS ORGANIZATION_CODE ITEM_NAME LOT_CONTROL_CODE
MSC_SYSTEM_ITEMS stores the organization items defined at source applications. It also stores a cop Most of the columns in MSC_SYSTEM_ITEMS correspond to columns from the Oracle Inventory Item Description The organization in which the item is being defined. The name of the item that you are creating. Derive from LOT_CONTROL_FLAG in case of XML, else populate directly. Valid values are: 1 - No lot control, 2 - Full lot control.
ROUNDING_CONTROL_TYPE IN_SOURCE_PLAN
Valid values are: 1 - Round order quantities, 2 - Do not round order quantities. Flag indicating whether the item is in the plan. (The snapshot initially gets more items than planned items.) Valid values are: 3 - MRP planning, 4 - MPS planning, 6 - Not planned, 7 - MRP and DRP planning, 8 - MPS and DRP planning, 9 - DRP planning.
MRP_PLANNING_CODE
FULL_LEAD_TIME
Full lead time If shipping from the supplier its start date to the dock date
UOM_CODE MRP_CALCULATE_ATP_FLAG ATP_COMPONENTS_FLAG BUILT_IN_WIP_FLAG
Unit of measure code. Valid values are: 1 - Yes, 2 - No. Valid values are: Y - Item may have component requiring ATP check, N - No. Valid values are: 1 - Yes, 2 - No.
PURCHASING_ENABLED_FLAG PLANNING_MAKE_BUY_CODE REPETITIVE_TYPE ENGINEERING_ITEM_FLAG
Valid values are: 1 - Yes, 2 - No. Indicate if this item should be made or bought. Make(1), Buy(2) Flag to indicate whether the item is built repetitive Valid values are: 1 - Yes, 2 - No. Flag indicates if engineering items are used for prototypes or research. Used for UI and reports. Valid values are: 1 - User-defined quantity, 2 - User-defined percentage, or mean absolute deviation.
MRP_SAFETY_STOCK_CODE EFFECTIVITY_CONTROL INVENTORY_PLANNING_CODE ATP_FLAG SR_INSTANCE_CODE DESCRIPTION LOTS_EXPIRATION
Valid values are: 1 - Yes, 2 - No. Source instance code defined on the planning server. Item description.
SHRINKAGE_RATE FIXED_DAYS_SUPPLY FIXED_ORDER_QUANTITY
Percentage of shinkage for this item Order Modifier:Period of the supply days (in days) Order Modifier:Fixed size for the orders
FIXED_LOT_MULTIPLIER MINIMUM_ORDER_QUANTITY
Order Modifier:Fixed size for the lot Order Modifier:Minimum size of an order
MAXIMUM_ORDER_QUANTITY
Order Modifier:Maximum size of an order Order Modifier: field is addressed to above Planning time fences days of the item
PLANNING_TIME_FENCE_DAYS
DEMAND_TIME_FENCE_DAYS RELEASE_TIME_FENCE_CODE RELEASE_TIME_FENCE_DAYS REVISION
Demand time fence days Release time fence code Release time fence time Item revision code
CATEGORY_NAME
Category name for the planning category
ABC_CLASS_NAME
Inventory item identifier ABC class (use for UI and reports)
ABC_CLASS_NAME FIXED_LEAD_TIME VARIABLE_LEAD_TIME
Inventory item identifier ABC class (use for UI and reports) Fixed lead time Variable lead time
PREPROCESSING_LEAD_TIME
Preprocessing lead time
POSTPROCESSING_LEAD_TIME
Postprocessing lead time
CUMULATIVE_TOTAL_LEAD_TIME Cumulative total lead time CUM_MANUFACTURING_LEAD_TIM E Cumulative manufacturing lead time
UNIT_WEIGHT
Weight of the item
UNIT_VOLUME WEIGHT_UOM VOLUME_UOM
Volume of the item Unit of measure for the weight Unit of measure for the volume
PRODUCT_FAMILY_ITEM_NAME ATP_RULE_CODE STANDARD_COST CARRYING_COST ORDER_COST DMD_LATENESS_COST SS_PENALTY_COST SUPPLIER_CAP_OVERUTIL_COST
Product Family to which the item belongs ATP rule identifier Standard cost of an item Carrying cost Order cost Demand lateness cost for item Penalty cost for saftety stock violations Supplier cap over utilization cost
LIST_PRICE
List price of the item
AVERAGE_DISCOUNT
END_ASSEMBLY_PEGGING_FLAG END_ASSEMBLY_PEGGING FULL_PEGGING WIP_SUPPLY_TYPE MRP_SAFETY_STOCK_PERCENT SAFETY_STOCK_BUCKET_DAYS INVENTORY_USE_UP_DATE
Average discount Valid values are: A - Full pegging, B - End assembly/full pegging, I - Net by project/ ignore excess, N - None, X - Net by project/net excess, Y - End assembly pegging. Peg to the end assembly on reports (value is populated by the plan) Full pegging flag Valid values are: 1 - Push, 2 - Assembly pull, 3 - Operation pull, 4 - Bulk, 5 Supplier, 6 - Phantom, 7 - Based on bill. Percent of average gross requirement for dynamically calculated safetystocks. Days over an average demand for MRP planned safety stock percent. Use-up date
BUYER_NAME
Name of buyer (for reporting)
PLANNER_CODE PLANNING_EXCEPTION_SET EXCESS_QUANTITY EXCEPTION_SHORTAGE_DAYS EXCEPTION_EXCESS_DAYS
Planner code (for reporting) Identifier of the planning exception set Excess quantity of this item Exception shortage days Exception excess days
EXCEPTION_OVERPROMISED_DAYS Exception over-promised days REPETITIVE_VARIANCE_DAYS BASE_ITEM_NAME BOM_ITEM_TYPE ATO_FORECAST_CONTROL ACCEPTABLE_EARLY_DELIVERY ACCEPTABLE_RATE_INCREASE ACCEPTABLE_RATE_DECREASE Valid values are: 1 - Model, 2 - Option Class, 3 - Planning, 4 - Standard, 5 Product family Valid values are: 1 - Consume, 2- Consume and derive, 3 - None. Acceptable early days
PRIMARY_SUPPLIER_NAME INVENTORY_ITEM_FLAG REVISION_QTY_CONTROL_CODE EXPENSE_ACCOUNT INVENTORY_ASSET_FLAG MATERIAL_COST RESOURCE_COST
Primary supplier Valid values are: 1- Yes, 2 - No. 1 Not under revision quantity control 2 Under revision quantity control Expense Account Valid values are: 1 - Yes, 2 - No. Item Material Cost Item Resource Cost
SOURCE_ORG_CODE
Source Organization Code
PICK_COMPONENTS_FLAG ALLOWED_UNITS_LOOKUP_CODE SERVICE_LEVEL REPLENISH_TO_ORDER_FLAG
Flag indicating whether all shippable components should be picked. Service level Flag indicating item to be planned as replenish to order Required for Collaborative Planning. You should provide the party name with which the company is registered in CP. For a planning (APS) environment only, this should remain null. Min Minmax Quantity Max Minmax Quantity Whether the item is serial number controlled in this Organization. Valid values are 1 - Yes and 2 - No. Substitution Window for the Item. Create supply flag (1=Yes, 2=No).
COMPANY_NAME MIN_MINMAX_QUANTITY MAX_MINMAX_QUANTITY SERIAL_NUMBER_CONTROL_CODE PIP_FLAG SUBSTITUTION_WINDOW CREATE_SUPPLY_FLAG SERIAL_NUMBER_CONTROL_CODE CRITICAL_COMPONENT_FLAG REDUCE_MPS VMI_MINIMUM_UNITS VMI_MINIMUM_DAYS VMI_MAXIMUM_UNITS VMI_MAXIMUM_DAYS VMI_FIXED_ORDER_QUANTITY SO_AUTHORIZATION_FLAG CONSIGNED_FLAG ASN_AUTOEXPIRE_FLAG VMI_FORECAST_TYPE FORECAST_HORIZON BUDGET_CONSTRAINED
Flag for indicating item is critical or not. Indicates how MPS orders are reduce when the plan is re-run. Minimum quantity in units. Minimum quantity in days. Maximum quantity in units. Maximum quantity in days. Fixed order quantity in units. SO release authorization flag 1- authorization by customer required 2authorization not required. VMI Consigned flag 1-consigned, 2-unconsigned. Auto-expiring ASN flag 1 ASN auto-expired, 2- ASN not auto-expired. Forecast type for average flag 1- order forecast, 2- sales forecast, 3- historical sales. Forecast horizon for average daily demand calculation. Budget Constrained Flag 1-Yes, 2-No.
DAYS_TGT_INV_SUPPLY DAYS_TGT_INV_WINDOW DAYS_MAX_INV_SUPPLY DAYS_MAX_INV_WINDOW CONTINOUS_TRANSFER CONVERGENCE DIVERGENCE
Target inventory level days supply. Target Inventory level window. Max inventory level days supply. Max inventory level window Continuous Inter Organization transfers 1-Yes, 2-No, 3-Use Global Value. Convergent Supply Consumption Pattern 1-Series, 2-Parallel, 3-Use Global Value. Divergent Supply Feeding Pattern 1-Series, 2-Series with MTQ, 3-Use Global Value. Please provide the Inventory Item ID for the Item in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Organization ID for the Organization in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Primary Supplier ID for the Primary Supplier in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Base Item ID for the Base Item in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the ABC Class ID for the ABC Class in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Repair lead time(days). Required only for Service Requirement Planning (SRP). Preposition Inventory. Required only for Service Requirement Planning (SRP). Valid values are 'Y' and 'N'. Repair yield percentage. Required only for Service Requirement Planning (SRP). Repair Program definition. Required only for Service Requirement Planning (SRP). Valid values are 1 - Advanced exchange on defective receipt, 2 Advanced exchange on PO issue, 3 - Repair Return Checkbox to enable or disable DRP Planning. Valid values are 1 ( For YES) and 2 (For NO)
SOURCE_SR_INVENTORY_ITEM_ID
SOURCE_SOURCE_ORG_ID
SOURCE_PRIMARY_SUPPLIER_ID
SOURCE_BASE_ITEM_ID
SOURCE_ABC_CLASS_ID REPAIR_LEAD_TIME PREPOSITION_POINT REPAIR_YIELD
REPAIR_PROGRAM DRP_PLANNED
SOURCE_TYPE
rce applications. It also stores a copy of items planned by the planning process. ns from the Oracle Inventory Item master Logic Fields Referenced Base.xml:itemBranch:branchCode Base.xml:itemBranch:branchCode Base.xml:itemBranch:itemCode Base.xml:itemBranch:itemCode Base.xml:itemBranch:lotStatusCode Base.xml:item:roundToWholeNumbers Y -> 1 <null> -> 2 N -> 2 U -> Parameter(Setting_to_use_on_round_up) <null> <the plan populates this field> Base.xml:itemBranch:planningCode in E1 we will have a UDC translation table based on MPST. Base.xml:itemBranch:lotStatusCode
E1 Table F4102 F4102 F4102
Base.xml:item:roundToWholeNumbers
F4101
Base.xml:item:planningCode Base.xml:itemBranch:itemType
F4102 F4102
If Purchased (base.xml:itemBranch:itemType = "P"): then Supplier.xml:supplier:supplieritem:standardLeadTi me (LVLT) (key is item/branch) (use lowest cost Supplier.xml:supplier:supplieritem:standard record) LeadTime F43090 else base.xml:itemBranch:fixedLeadTime Base.xml:itemBranch:fixedLeadTime F4102
Base.xml:item:planningUom Parameter.MRP Calculate ATP Flag(2) Parameter.ATP Components Flag(n) Parameter.Built_In_WIP (1)
F34A10
If Purchased (base.xml:itemBranch:itemType = "P") then 1 otherwise 2 Base.xml:itemBranch:itemType (M->1, p->2) Parameter.Repititive Type (1) "2" <null> Parameter.Safety Stock Code (1) Parameter.Effectivity Control (1) parameter.Inventory Planning Code (6) "2" Parameter.Source_Instance Base.xml:item:description Base.xml:itemBranch:shelfLife Bug 2010-05-27 Base.xml:itemBranch:shrinkageRate / 100 Documentation Note: make sure user set shrink method to "%" Base.xml:itemBranch:fixedDaysSupply Base.xml:itemBranch:fixedOrderQuantity If Base.xml:itemBranch:orderMultiplier=0 then <null> else Base.xml:itemBranch:orderMultiplier(Bug 10135494) Base.xml:itemBranch:minimumOrderQuantity
Base.xml:itemBranch:itemType Base.xml:itemBranch:itemType
F4102 F4102
Base.xml:item:description Base.xml:itemBranch:shelfLife
F4101 F4102
Base.xml:itemBranch:shrinkageRate Base.xml:itemBranch:fixedDaysSupply Base.xml:itemBranch:fixedOrderQuantity
F4102 F4102 F4102
Base.xml:itemBranch:orderMultiplier F4102 Base.xml:itemBranch:minimumOrderQuanti ty F4102
If Base.xml:itemBranch:maximumOrderQuantity=0 then <null> else Base.xml:itemBranch:maximumOrderQuantity Base.xml:itemBranch:maximumOrderQuanti (Bug 10135494) ty F4102 Base.xml:item:roundToWholeNumbers Base.xml:item:roundToWholeNumbers F4101 Base.xml:itemBranch:freezeTimeFenceDays Base.xml:itemBranch:freezeTimeFenceDays F4102 Base.xml:inventoryPolicy:forecastConsumptionTim eFence Documentation Note: Make sure forecastConsumptionRule is "Order - Greater" and Base.xml:inventoryPolicy:forecastConsumpti UOM is "Days" onTimeFence F4102 Parameter.Release Time Fence Code Parameter.Release Time Fence Days Parameter.Revision (<null>) Base.xml:itemgroup..refer to the FDD section on Category Codes, the parameter for this field will be Parameter.Item_Default_Category Base.xml:itembranch:ABCS or Base.xml:itembranch:ABCI or Base.xml:itembranch:ABCM The parameter.ABC field name will determine which to use
Base.xml:itemgroup Base.xml:itembranch:abcSales
F4101 F4102
Base.xml:itembranch:abcInvestmentInvento ry F4102
Base.xml:itembranch:ABCS or Base.xml:itembranch:ABCI or Base.xml:itembranch:ABCM The parameter.ABC field name will determine which to use Base.xml:itemBranch:fixedLeadTime Base.xml:itemBranch:variableLeadTime If Purchased (supplier item record exists in Supplier.xml (key is item&branch)):): Parameter.Purchased Preprocessing Lead Time (<null>) For Manufactured Items: Parameter.manufactured Preprocessing Lead Time (<null>) For Purchased Items ((base.xml:itemBranch:itemType = "P" ): Parameter.Purchased Postprocessing Lead Time (<null>) For Manufactured Items: Parameter.manufactured Postprocessing Lead Time (<null>) For Purchased Items: Parameter.Purchased Cumm Total Lead Time (<null>) For Manufacturing Items: Parameter.manufactured Cumm Total Lead Time (<null>) <null>
Base.xml:itembranch:abcMarginInventory Base.xml:itemBranch:fixedLeadTime Base.xml:itemBranch:variableLeadTime
F4102
Base.xml:itemBranch:itemType
F4102
F4102
F4102
Base.xml:item:weightUom
F4101
Work with UOM Conversions in Base.xml:item:weightUom
Base.xml:itemUom:factor Base.xml:item:volumeUom
F41002 F4101 F41002 F4101 F4101
Work with UOM Conversions in Base.xml Base.xml:item:weightUom Base.xml:item:volumeUom
Base.xml:itemUom:factor Base.xml:item:weightUom Base.xml:item:volumeUom
Base.xml:itembranch:masterPlanningFamily Parameter.ATP Rule Code(<null>) Base.xml:itenBranch:itemCost Parameter.Carrying Cost % of standard cost Parameter.Order Cost % of standard cost * (Standard Cost/100) Parameter.Demand Lateness Cost % of standard cost * (Standard Cost/100) Parameter.SS Penalty Cost % of standard cost * (Standard Cost/100) Parameter.Supplier Cap Over Utilization Cost % of standard cost * (Standard Cost/100) Base.xml:itemBranch:timeVaryingEvent:itemPrice (time varying event..use the one which covers Options.Base_Date)
Base.xml:itembranch:masterPlanningFamily F4102 Base.xml:itenBranch:itemCost Base.xml:itenBranch:itemCost Base.xml:itenBranch:itemCost Base.xml:itenBranch:itemCost Base.xml:itenBranch:itemCost Base.xml:itenBranch:itemCost Base.xml:itemBranch:timeVaryingEvent:ite mPrice F4105 F4105 F4105 F4105 F4105 F4105
F4106
Parameter.Average Discount
Parameter.End Assembly Pegging Flag (B) Parameter.End Assembly Pegging (<null>) Parameter. Full Pegging (1) <null> Parameter.MRP Safety Stock Percent(<null>) Parameter.Safety Stock Bucket Days(<null>) <null> <null> Buyer number on Item Master not needed as not supporting requisitions IF 'Base.xml:itemBranch:plannerNumber' <> 0 use 'Base.xml:itemBranch:plannerNumber' otherwise use Parameters.Default_Planner_Number Base.xml:itemBranch:plannerNumber Parameter.Planning Exception Set (null) <null> Parameter.Exception Shortage Days (<null>) Parameter.Exception Excess Days (<null>) Parameter.Exception Over Promised Days Parameter.Repetitive Variance Days <null> (used in end_item_substitution). Parameter.BOM Item Type (4) (1) for ATO items if ATO comes into scope Parameter.ATO Forecast (2) Parameter.Acceptable Early Delivery (<null>) Parameter.Acceptable Rate Increase (<null>) Parameter.Acceptable Rate Decrease (<null>) Supplier.xml:supplier:supplierItem:item = current item (key is item/branch) Use the Supplier with the lowest cost Supplier.xml:supplier:supplierItem:item Parameter.Inventory Item Flag (1) Parameter.Revision Quantity Control Code(1) Parameter.Expense Account (<null>) Parameter.Inventory Asset Flag(N) <null> <null>
F4102
F43090
If in Manufacturing.xml there is a producedItem with itemCode=Base.xml:itemBranch:itemCode and branchCode= Base.xml:itemBranch:branchCode Then set to Base.xml:itemBranch:branchCode Else Search distribution.xml where Distribution.xml:lane:destinationBranchCode= Base.xml:itemBranch:branchCode and Distribution.xml:lane: transportModeCode: itemCode= Base.xml:itemBranch:itemCode Note Branch is translatable Parameter.Pick Components Flag (<null>) Kits and configured items are not covered by the current extracts <null> Parameter.Service Level (<null>) Parameter.Replenish To Order Flag(N)
Manufacturing.xml:operation:producedItem F3003 Manufacturing.xml:operation:producedItem :producedItemBom F3003 Base.xml:itemBranch:branchCode Distribution.xml:lane:destinationBranchC ode Distribution.xml:lane:transportMode:itemTr ansportMode:itemCode Distribution.xml:lane:originBranchCode F4102 F3403 F3403 F3403
Parameter.CP_Company_Name <null> <null> Parameter.Serial Number Control Code("2") Parameter.PIP Flag (<null>) Parameter.Substitution Window(<null>) Parameter.Create Supply Flag(1) Parameter.Serial Number Control Code(<null>) Parameter.Critical Component Flag (<null>) Parameter.Reduce MPS (<null>) <null> <null> <null> <null> <null> <null> Parameter.Consigned_Flag Parameter.ASN Autoexpire Flag (<null>) <null> Parameter.Forecast Horizon (<null>) Parameter.Budget Constrained (2)
Parameter.Days TGT Inv Supply (<null>) Parameter.Days TGT Inv Window (<null>) Parameter.Days Max Inv Supply (<null>) Parameter.Days Max Inv Window (<null>) Parameter.Continuous Transfer(<null>) Parameter.Convergence(<null>) Parameter.Divergence(<null>)
Same as "Item Code" above
Same as "Organisation Code" above use the value populated into "Primary Supplier Name"
<null> use the same value used for "ABC Class Name" above <null> <null> <null>
<null> Base.xml:itembranch:drpPlanned (Yes-> Y, No-> N) Base.xml:itembranch:drpPlanned F4102
IF Supplier.xml:supplier:supplierItem:item = current item (key is item/branch) exists then set to "2" Else Set to "1"
Supplier.xml:supplier:supplierItem:branchCo de F43090 Supplier.xml:supplier:supplierItem:itemCod e F43090
E1 Field MCU ITM LOTS
Comment
SNS
MPST STKT
ALTD LTLV
see comment
CMUM is retrieved from F34A10 where F34A10.SY = '34A' assignment = if F34A10.CMUM = '01', then planningUom = F4101. UOM1 if F34A10.CMUM = '02', then planningUom = F4101.UOM2 if F34A10.CMUM = '03', then planningUom = F4101.UOM3 if F34A10.CMUM = '04', then planningUom = F4101.UOM4 if F34A10.CMUM = '05', then planningUom = F4101.UOM6 if F34A10.CMUM = '06', then planningUom = F4101.UOM8 if F34A10.CMUM = '07', then planningUom = F4101.UOM9 if F34A10.CMUM = '08', then planningUom = F4101.UWUM if F34A10.CMUM = '09', then planningUom = F4101.UVM1
STKT STKT
DSC1 SLD
SRNK see comment see comment Item.Branch.Order Policy(OPC)=4 use item.branch:item_value_policy(OPV) otherwise <null> Item.Branch.Order Policy(OPC)=2 use item.branch:item_value_policy(OPV) otherwise <null>
MULT RQMN
RQMX SNS MTF2
MTF1
see comment ABCS ABCI
possible category code groups = SRP1, SRP2, SRP3, SRP4, SRP5, SRP6, SRP7, SRP8, SRP9, SRP0, CARS, CARP, PRP1, PRP2, PRP3, PRP4, PRP5, PRP6, PRP7, PRP8, PRP9, PRP0, SHCN, SHCM, CYCL
ABCM
STKT
STKT
STKT
UWUM
see comment UVM1 see comment UWUM UVM1
itemCode and toUOMType in JOIN criterea assignment = if F41002.UM = planningUom (value assigned in the item Object), then factor = the inversion of F41002.CONV else factor = F41002.CONV where F41002.UM = planningUom itemCode and toUOMType in JOIN criterea assignment = if F41002.UM = planningUom (value assigned in the item Object), then factor = the inversion of F41002.CONV
PRP4 UNCS UNCS UNCS UNCS UNCS UNCS
UPRC
ANPL
ITM
KIT MMCU MCU cmcu itm mmcu
MPST
MCU ITM
Table
MSC_ST_SYSTEM_ITEMS
Description VCP-ODS ORGANIZATION_CODE ITEM_NAME
MSC_SYSTEM_ITEMS stores the organization items defined at source applications. It also stores a cop Most of the columns in MSC_SYSTEM_ITEMS correspond to columns from the Oracle Inventory Item Highlighted fiels indicate the mapping differs from actual items Description The organization in which the item is being defined. The name of the item that you are creating.
LOT_CONTROL_CODE
Derive from LOT_CONTROL_FLAG in case of XML, else populate directly. Valid values are: 1 - No lot control, 2 - Full lot control.
ROUNDING_CONTROL_TYPE IN_SOURCE_PLAN
Valid values are: 1 - Round order quantities, 2 - Do not round order quantities. Flag indicating whether the item is in the plan. (The snapshot initially gets more items than planned items.) Valid values are: 3 - MRP planning, 4 - MPS planning, 6 - Not planned, 7 - MRP and DRP planning, 8 - MPS and DRP planning, 9 - DRP planning.
MRP_PLANNING_CODE
FULL_LEAD_TIME
Full lead time If shipping from the supplier its start date to the dock date
UOM_CODE MRP_CALCULATE_ATP_FLAG ATP_COMPONENTS_FLAG BUILT_IN_WIP_FLAG
Unit of measure code. Valid values are: 1 - Yes, 2 - No. Valid values are: Y - Item may have component requiring ATP check, N - No. Valid values are: 1 - Yes, 2 - No.
PURCHASING_ENABLED_FLAG PLANNING_MAKE_BUY_CODE REPETITIVE_TYPE ENGINEERING_ITEM_FLAG
Valid values are: 1 - Yes, 2 - No. Indicate if this item should be made or bought. Make(1), Buy(2) Flag to indicate whether the item is built repetitive Valid values are: 1 - Yes, 2 - No. Flag indicates if engineering items are used for prototypes or research. Used for UI and reports. Valid values are: 1 - User-defined quantity, 2 - User-defined percentage, or mean absolute deviation.
MRP_SAFETY_STOCK_CODE EFFECTIVITY_CONTROL INVENTORY_PLANNING_CODE ATP_FLAG SR_INSTANCE_CODE DESCRIPTION LOTS_EXPIRATION
Valid values are: 1 - Yes, 2 - No. Source instance code defined on the planning server. Item description.
SHRINKAGE_RATE FIXED_DAYS_SUPPLY FIXED_ORDER_QUANTITY FIXED_LOT_MULTIPLIER MINIMUM_ORDER_QUANTITY MAXIMUM_ORDER_QUANTITY
Percentage of shinkage for this item Order Modifier:Period of the supply days (in days) Order Modifier:Fixed size for the orders Order Modifier:Fixed size for the lot Order Modifier:Minimum size of an order Order Modifier:Maximum size of an order Order Modifier: field is addressed to above Planning time fences days of the item
PLANNING_TIME_FENCE_DAYS
DEMAND_TIME_FENCE_DAYS RELEASE_TIME_FENCE_CODE RELEASE_TIME_FENCE_DAYS REVISION
Demand time fence days Release time fence code Release time fence time Item revision code
CATEGORY_NAME
Category name for the planning category
ABC_CLASS_NAME FIXED_LEAD_TIME VARIABLE_LEAD_TIME
Inventory item identifier ABC class (use for UI and reports) Fixed lead time Variable lead time
PREPROCESSING_LEAD_TIME
Preprocessing lead time
POSTPROCESSING_LEAD_TIME
Postprocessing lead time
CUMULATIVE_TOTAL_LEAD_TIME Cumulative total lead time CUM_MANUFACTURING_LEAD_TIM E Cumulative manufacturing lead time UNIT_WEIGHT UNIT_VOLUME WEIGHT_UOM VOLUME_UOM PRODUCT_FAMILY_ITEM_NAME ATP_RULE_CODE STANDARD_COST CARRYING_COST ORDER_COST DMD_LATENESS_COST SS_PENALTY_COST SUPPLIER_CAP_OVERUTIL_COST LIST_PRICE AVERAGE_DISCOUNT Weight of the item Volume of the item Unit of measure for the weight Unit of measure for the volume Product Family to which the item belongs ATP rule identifier Standard cost of an item Carrying cost Order cost Demand lateness cost for item Penalty cost for saftety stock violations Supplier cap over utilization cost List price of the item Average discount Valid values are: A - Full pegging, B - End assembly/full pegging, I - Net by project/ ignore excess, N - None, X - Net by project/net excess, Y - End assembly pegging. Peg to the end assembly on reports (value is populated by the plan) Full pegging flag Valid values are: 1 - Push, 2 - Assembly pull, 3 - Operation pull, 4 - Bulk, 5 Supplier, 6 - Phantom, 7 - Based on bill. Percent of average gross requirement for dynamically calculated safetystocks. Days over an average demand for MRP planned safety stock percent. Use-up date
END_ASSEMBLY_PEGGING_FLAG END_ASSEMBLY_PEGGING FULL_PEGGING WIP_SUPPLY_TYPE MRP_SAFETY_STOCK_PERCENT SAFETY_STOCK_BUCKET_DAYS INVENTORY_USE_UP_DATE
BUYER_NAME
Name of buyer (for reporting)
PLANNER_CODE PLANNING_EXCEPTION_SET EXCESS_QUANTITY EXCEPTION_SHORTAGE_DAYS EXCEPTION_EXCESS_DAYS
Planner code (for reporting) Identifier of the planning exception set Excess quantity of this item Exception shortage days Exception excess days
EXCEPTION_OVERPROMISED_DAYS Exception over-promised days REPETITIVE_VARIANCE_DAYS BASE_ITEM_NAME BOM_ITEM_TYPE ATO_FORECAST_CONTROL ACCEPTABLE_EARLY_DELIVERY ACCEPTABLE_RATE_INCREASE ACCEPTABLE_RATE_DECREASE PRIMARY_SUPPLIER_NAME INVENTORY_ITEM_FLAG REVISION_QTY_CONTROL_CODE EXPENSE_ACCOUNT INVENTORY_ASSET_FLAG MATERIAL_COST RESOURCE_COST Valid values are: 1 - Model, 2 - Option Class, 3 - Planning, 4 - Standard, 5 Product family Valid values are: 1 - Consume, 2- Consume and derive, 3 - None. Acceptable early days
Primary supplier Valid values are: 1- Yes, 2 - No. 1 Not under revision quantity control 2 Under revision quantity control Expense Account Valid values are: 1 - Yes, 2 - No. Item Material Cost Item Resource Cost
SOURCE_ORG_CODE
Source Organization Code
PICK_COMPONENTS_FLAG ALLOWED_UNITS_LOOKUP_CODE SERVICE_LEVEL REPLENISH_TO_ORDER_FLAG
Flag indicating whether all shippable components should be picked. Service level Flag indicating item to be planned as replenish to order Required for Collaborative Planning. You should provide the party name with which the company is registered in CP. For a planning (APS) environment only, this should remain null. Min Minmax Quantity Max Minmax Quantity Whether the item is serial number controlled in this Organization. Valid values are 1 - Yes and 2 - No. Substitution Window for the Item.
COMPANY_NAME MIN_MINMAX_QUANTITY MAX_MINMAX_QUANTITY SERIAL_NUMBER_CONTROL_CODE PIP_FLAG SUBSTITUTION_WINDOW
CREATE_SUPPLY_FLAG SERIAL_NUMBER_CONTROL_CODE CRITICAL_COMPONENT_FLAG REDUCE_MPS VMI_MINIMUM_UNITS VMI_MINIMUM_DAYS VMI_MAXIMUM_UNITS VMI_MAXIMUM_DAYS VMI_FIXED_ORDER_QUANTITY SO_AUTHORIZATION_FLAG CONSIGNED_FLAG ASN_AUTOEXPIRE_FLAG VMI_FORECAST_TYPE FORECAST_HORIZON BUDGET_CONSTRAINED DAYS_TGT_INV_SUPPLY DAYS_TGT_INV_WINDOW DAYS_MAX_INV_SUPPLY DAYS_MAX_INV_WINDOW CONTINOUS_TRANSFER CONVERGENCE DIVERGENCE
Create supply flag (1=Yes, 2=No).
Flag for indicating item is critical or not. Indicates how MPS orders are reduce when the plan is re-run. Minimum quantity in units. Minimum quantity in days. Maximum quantity in units. Maximum quantity in days. Fixed order quantity in units. SO release authorization flag 1- authorization by customer required 2authorization not required. VMI Consigned flag 1-consigned, 2-unconsigned. Auto-expiring ASN flag 1 ASN auto-expired, 2- ASN not auto-expired. Forecast type for average flag 1- order forecast, 2- sales forecast, 3- historical sales. Forecast horizon for average daily demand calculation. Budget Constrained Flag 1-Yes, 2-No. Target inventory level days supply. Target Inventory level window. Max inventory level days supply. Max inventory level window Continuous Inter Organization transfers 1-Yes, 2-No, 3-Use Global Value. Convergent Supply Consumption Pattern 1-Series, 2-Parallel, 3-Use Global Value. Divergent Supply Feeding Pattern 1-Series, 2-Series with MTQ, 3-Use Global Value. Please provide the Inventory Item ID for the Item in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Organization ID for the Organization in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Primary Supplier ID for the Primary Supplier in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Base Item ID for the Base Item in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the ABC Class ID for the ABC Class in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Repair lead time(days). Required only for Service Requirement Planning (SRP). Preposition Inventory. Required only for Service Requirement Planning (SRP). Valid values are 'Y' and 'N'. Repair yield percentage. Required only for Service Requirement Planning (SRP). Repair Program definition. Required only for Service Requirement Planning (SRP). Valid values are 1 - Advanced exchange on defective receipt, 2 Advanced exchange on PO issue, 3 - Repair Return Checkbox to enable or disable DRP Planning. Valid values are 1 ( For YES) and 2 (For NO)
SOURCE_SR_INVENTORY_ITEM_ID
SOURCE_SOURCE_ORG_ID
SOURCE_PRIMARY_SUPPLIER_ID
SOURCE_BASE_ITEM_ID
SOURCE_ABC_CLASS_ID REPAIR_LEAD_TIME PREPOSITION_POINT REPAIR_YIELD
REPAIR_PROGRAM DRP_PLANNED
SOURCE_TYPE A SINGLE record is created for each PRODUCT_FAMILY_ITEM_NAME used in items.dat (1) aggreegated by (product_family_item_name and organisation). The BOM Item type for these records will be "5". The fields that need to be specifically set for this record type have their mapping highlight in orange The other values can be retrieved from any of the items that are a member of that family
rce applications. It also stores a copy of items planned by the planning process. ns from the Oracle Inventory Item master Logic Base.xml:itemBranch:branchCode Base.xml:item:masterPlanningFamily Fields Referenced Base.xml:itemBranch:branchCode E1 Table F4102
Base.xml:itembranch:masterPlanningFa mily F4102 Base.xml:itemBranch:lotStatusCode Base.xml:item:roundToWholeNumbers Y -> 1 <null> -> 2 N -> 2 U -> Parameter(Setting_to_use_on_round_up) <null> <the plan populates this field> Base.xml:itemBranch:planningCode in E1 we will have a UDC translation table based on MPST. Base.xml:itemBranch:lotStatusCode F4102
Base.xml:item:roundToWholeNumbers
F4101
Base.xml:item:planningCode Base.xml:itemBranch:itemType
F4102 F4102
If Purchased (base.xml:itemBranch:itemType = "P"): then Supplier.xml:supplier:supplieritem:standardLeadTi me (LVLT) (key is item/branch) (use lowest cost Supplier.xml:supplier:supplieritem:stand record) ardLeadTime F43090 else base.xml:itemBranch:fixedLeadTime Base.xml:itemBranch:fixedLeadTime F4102
Base.xml:item:planningUom Parameter.MRP Calculate ATP Flag(2) Parameter.ATP Components Flag(n) Parameter.Built_In_WIP (1)
F34A10
"2" Base.xml:itemBranch:itemType (M->1, p->2) Parameter.Repititive Type (1) "2" <null> Parameter.Safety Stock Code (1) Parameter.Effectivity Control (1) parameter.Inventory Planning Code (6) "2" Parameter.Source_Instance same as Item name <above> Base.xml:itemBranch:shelfLife Bug 2010-05-27 Base.xml:itemBranch:shrinkageRate / 100 Documentation Note: make sure user set shrink method to "%" <null> <null> <null> <null> <null> <null>
F4102
Base.xml:itemBranch:shelfLife
F4102
Base.xml:itemBranch:shrinkageRate
F4102
Base.xml:itemBranch:freezeTimeFence Days Base.xml:itemBranch:freezeTimeFenceDays F4102 Base.xml:inventoryPolicy:forecastConsumptionTim eFence Documentation Note: Make sure forecastConsumptionRule is "Order - Greater" and Base.xml:inventoryPolicy:forecastConsu mptionTimeFence UOM is "Days" F4102 Parameter.Release Time Fence Code Parameter.Release Time Fence Days Parameter.Revision (<null>)
Base.xml:itemgroup..refer to the FDD section on Category Codes, the parameter for this field will be Parameter.Item_Default_Category Base.xml:itembranch:ABCS or Base.xml:itembranch:ABCI or Base.xml:itembranch:ABCM The parameter.ABC field name will determine which to use Base.xml:itemBranch:fixedLeadTime Base.xml:itemBranch:variableLeadTime
Base.xml:itemgroup Base.xml:itembranch:abcSales
F4101 F4102
Base.xml:itembranch:abcInvestmentInve ntory F4102 Base.xml:itembranch:abcMarginInventor y F4102 Base.xml:itemBranch:fixedLeadTime Base.xml:itemBranch:variableLeadTime
If Purchased (supplier item record exists in Supplier.xml (key is item&branch)):): Parameter.Purchased Preprocessing Lead Time (<null>) For Manufactured Items: Parameter.manufactured Preprocessing Lead Time Base.xml:itemBranch:itemType (<null>) For Purchased Items ((base.xml:itemBranch:itemType = "P" ): Parameter.Purchased Postprocessing Lead Time (<null>) For Manufactured Items: Parameter.manufactured Postprocessing Lead Base.xml:itemBranch:itemType Time (<null>) For Purchased Items: Parameter.Purchased Cumm Total Lead Time (<null>) For Manufacturing Items: Parameter.manufactured Cumm Total Lead Time (<null>) <null> <null> <null> <null> <null> <null> Parameter.ATP Rule Code(<null>) <null> <null> <null> <null> <null> <null> <null> <null>
F4102
F4102
Parameter.ATP Rule Code(<null>)
Parameter.End Assembly Pegging Flag (B) Parameter.End Assembly Pegging (<null>) Parameter. Full Pegging (1) <null> Parameter.MRP Safety Stock Percent(<null>) Parameter.Safety Stock Bucket Days(<null>) <null> <null> Buyer number on Item Master not needed as not supporting requisitions
IF 'Base.xml:itemBranch:plannerNumber' <> 0 use 'Base.xml:itemBranch:plannerNumber' otherwise Base.xml:itemBranch:plannerNumber use Parameters.Default_Planner_Number Parameter.Planning Exception Set (null) <null> <null> <null> <null> Parameter.Repetitive Variance Days <null> (used in end_item_substitution). "5" Parameter.ATO Forecast (2) Parameter.Acceptable Early Delivery (<null>) Parameter.Acceptable Rate Increase (<null>) Parameter.Acceptable Rate Decrease (<null>) <null> Parameter.Inventory Item Flag (1) Parameter.Revision Quantity Control Code(1) Parameter.Expense Account (<null>) Parameter.Inventory Asset Flag(N) <null> <null> If in Manufacturing.xml there is a producedItem with itemCode=Base.xml:itemBranch:itemCode and branchCode= Base.xml:itemBranch:branchCode Then set to Base.xml:itemBranch:branchCode Else Search distribution.xml where Distribution.xml:lane:destinationBranchCode= Base.xml:itemBranch:branchCode and Distribution.xml:lane: transportModeCode: itemCode= Base.xml:itemBranch:itemCode Note Branch is translatable Parameter.Pick Components Flag (<null>) Kits and configured items are not covered by the current extracts <null> Parameter.Service Level (<null>) Parameter.Replenish To Order Flag(N)
F4102
Manufacturing.xml:operation:producedIt em F3003
Parameter.CP_Company_Name <null> <null> Parameter.Serial Number Control Code("2") Parameter.PIP Flag (<null>) Parameter.Substitution Window(<null>)
Parameter.Create Supply Flag(1) Parameter.Serial Number Control Code(<null>) Parameter.Critical Component Flag (<null>) Parameter.Reduce MPS (<null>) <null> <null> <null> <null> <null> <null> Parameter.Consigned_Flag Parameter.ASN Autoexpire Flag (<null>) <null> Parameter.Forecast Horizon (<null>) Parameter.Budget Constrained (2) Parameter.Days TGT Inv Supply (<null>) Parameter.Days TGT Inv Window (<null>) Parameter.Days Max Inv Supply (<null>) Parameter.Days Max Inv Window (<null>) Parameter.Continuous Transfer(<null>) Parameter.Convergence(<null>) Parameter.Divergence(<null>)
<null>
<null>
<null>
<null>
<null> <null> <null> <null>
<null> Base.xml:itembranch:drpPlanned (Yes-> Y, No-> N) Base.xml:itembranch:drpPlanned F4102
IF Supplier.xml:supplier:supplierItem:item = current item (key is item/branch) exists then set to "2" Else Set to "1"
Supplier.xml:supplier:supplierItem:branc hCode F43090 Supplier.xml:supplier:supplierItem:itemC ode F43090
E1 Field MCU
Comment
PRP4 LOTS
SNS
MPST STKT
ALTD LTLV CMUM is retrieved from F34A10 where F34A10.SY = '34A' assignment = if F34A10.CMUM = '01', then planningUom = F4101. UOM1 if F34A10.CMUM = '02', then planningUom = F4101.UOM2 if F34A10.CMUM = '03', then planningUom = F4101.UOM3 if F34A10.CMUM = '04', then planningUom = F4101.UOM4 if F34A10.CMUM = '05', then planningUom = F4101.UOM6 if F34A10.CMUM = '06', then planningUom = F4101.UOM8 if F34A10.CMUM = '07', then planningUom = F4101.UOM9 if F34A10.CMUM = '08', then planningUom = F4101.UWUM if F34A10.CMUM = '09', then planningUom = F4101.UVM1
see comment
STKT
SLD
SRNK
MTF2
MTF1
see comment ABCS ABCI ABCM
possible category code groups = SRP1, SRP2, SRP3, SRP4, SRP5, SRP6, SRP7, SRP8, SRP9, SRP0, CARS, CARP, PRP1, PRP2, PRP3, PRP4, PRP5, PRP6, PRP7, PRP8, PRP9, PRP0, SHCN, SHCM, CYCL
STKT
STKT
ANPL
KIT
MPST
MCU ITM
CATEGORY_SET_NAME CONTROL_LEVEL SR_INSTANCE_CODE DESCRIPTION
DEFAULT_FLAG
COMPANY_NAME
SOURCE_SR_CATEGORY_SET_ID
Defined in the Complex modelling section of the FDD, Always populate from itemgroup section of Base.xml. If "Parameters.Use_Branch_based_Categories" is Yes, then we need to do this for branch
MSC_CATEGORY_SETS
This tables stores different category sets for an item Description
Category set name Control level. Valid values are: 1 - Master Org level, 2 - Child Org level Source instance code defined on the planning server Category set description
Flag indicating whether this is default category set. Valid values are: 1- Yes, 2 - No Required only for Collaborative Planning. You should provide the party name with which the company is registered in Collaborative Planning. For a planning (APS) only environment, this should be left null. Please provide the Category Set ID for the Category Set in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only.
Logic
Fields Referenced
E1 Table
E1 Field
Refer to the FDD for details on this formulation. Records exist for Base.xml:itemGroupList:itemGroup Base.xml:branchGroupList:branchGroup
Base.xml:itemGroupList:itemG roup F4101
category code value
For each of these the <name> is a concatenated string joined by "|", the category set name is the first field in this concatenated string Base.xml:branchGroupList:bra Refer to the FDD on the handling of category codes. nchGroup F0006 "2" Parameter.Source_Instance same as Category Set name same as Category Set name If the Categroy Set Name = Parameter.Item_Default_Category set to "1" otherwise "2"
category code value
<null>
opulate from
ed to do this
Return to File Definitions Comment possible category code groups = SRP1, SRP2, SRP3, SRP4, SRP5, SRP6, SRP7, SRP8, SRP9, SRP0, CARS, CARP, PRP1, PRP2, PRP3, PRP4, PRP5, PRP6, PRP7, PRP8, PRP9, PRP0, SHCN, SHCM, CYCL
CATEGORY_NAME SR_INSTANCE_CODE
DESCRIPTION DISABLE_DATE START_DATE_ACTIVE END_DATE_ACTIVE
ITEM_NAME ORGANIZATION_CODE
CATEGORY_SET_NAME
COMPANY_NAME
SOURCE_ORG_ID
SOURCE_INVENTORY_ITEM_ID
SOURCE_SR_CATEGORY_SET_ID
SOURCE_SR_CATEGORY_ID Enabled_Flag Summary_Flag
MSC_ITEM_CATEGORIES
This tables stores different category sets for an item Description
Name of category Source instance code defined on the planning server
Category description Disable date
Item name should be present in MSC_SYSTEM_ITEMS Organization code should exist for this instance
Should exist in the MSC_CATEGORY_SETS table Required only for Collaborative Planning. You should provide the party name with which the company is registered in Collaborative Planning. For a planning (APS) only environment, this should be left null. Please provide the Organization ID for the Organization in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Inventory Item ID for the Item in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Category Set ID for the Category Set in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Category ID for the Category in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only.
For each itemGroup Get each item [multiple items possible for each group] Lookup item branch (key = item) [multiple branches possible for each item] Create a record for each category-item-branch combination For each branchGroup Get each branch [multiple branches possible for each group] Lookup item branch (key = branch) [multiple items possible for each branch]
Logic
Fields Referenced
E1 Table
E1 Field
Refer to the FDD for details on this formulation. Records exist for Base.xml:itemGroupList:itemGroup Base.xml:branchGroupList:branchGroup
Base.xml:itemGroupList:itemG roup F4101
category code value
For each of these the <name> is a concatenated string joined by "|", the category name is the second field in this concatenated string Base.xml:branchGroupList:bra Refer to the FDD on the handling of category codes. nchGroup F0006 Parameter.Source_Instance description in customerGroup|itemGroup|branchGroup refer to Complex modelling section in FDD <null> <null> <null> items appearing under the members of this set. Base.xml:itemBranch:itemCode F4102 Base.xml:itemBranch:branchCod e F4102
category code value
ITM MCU
Base.xml: each branch associated with this item in Base.xml
Refer to CategorieSets.dat. Records come from Base.xml:itemGroupList:itemGroup Base.xml:branchGroupList:branchGroup Base.xml:itemGroupList:itemG For each of these the <name> is a concatenated string roup F4101 joined by "|", the category set name is the first field in Base.xml:branchGroupList:bra this concatenated string nchGroup F0006 category code value category code value
<null> Base.xml:itemBranch:branchCod e F4102
<branch code>
MCU
<itemcode>
Base.xml:itemGroup:itemCode
F4101
ITM
Refer to CategorieSets.dat
<null> "Y" "N"
opulate from
eed to do this
Return to File Definitions Comment possible category code groups = SRP1, SRP2, SRP3, SRP4, SRP5, SRP6, SRP7, SRP8, SRP9, SRP0, CARS, CARP, PRP1, PRP2, PRP3, PRP4, PRP5, PRP6, PRP7, PRP8, PRP9, PRP0, SHCN, SHCM, CYCL
possible category code groups = SRP1, SRP2, SRP3, SRP4, SRP5, SRP6, SRP7, SRP8, SRP9, SRP0, CARS, CARP, PRP1, PRP2, PRP3, PRP4, PRP5, PRP6, PRP7, PRP8, PRP9, PRP0, SHCN, SHCM, CYCL possible category code groups = RP01 through RP30
Table Description VCP-ODS Organization Code Item Name Period Start Date Safety Stock Quantity
Company Name Source Instance Code Deleted Flag Project Number Task Number
MSC_SAFETY_STOCKS Safety stock levels Description Organization code where this resource and department exist. Inventory item name
Required only for Collaborative Planning. You should provide the party name with which the company is registered in CP. For a planning (APS) only environment, this should be left null. Source instance code defined on the planning server. Valid values are: 1 - Yes, 2 - No. If 1, then this row is deleted.
Logic Base.xml:ItemBranch:Branch (MCU) Base.xml:ItemBranch:item (UITM)
Fields Referenced Base.xml:ItemBranch:Branch Base.xml:ItemBranch:item
E1 Table F4102 F4102
E1 Field MCU ITM
Parameter.Effective_Date_Offset + Option.Base_Date Base.xml:ItemBranch.SafetyStock (SAFE) Base.xml:ItemBranch.SafetyStock F4102
SAFE
Parameter.CP_Company_Name Parameter.Source_Instance 2 <null> <null>
Table Description VCP-ODS Item Name Organization Code Unit Number
New Order Quantity Firm Planned Type Source Instance Code Project Number Task Number
Planning Group Sub-inventory Code Lot Number Expiration Date Deleted Flag
Company Name VMI Flag
Source Org ID
Source Inventory Item ID
Source Project ID
Source Task ID
Source supply ID
Source Disposition ID SR Customer Account ID Order_Type Planning_Partner_Site_Code
Planning TP Type
BeginningInventory.xml Select only selected lotStatus types (Pegged and Available) (ParametersValid_QOH_Status_Codes) Aggregate multiple records to branch/item level and accumulate the quantity (prior to Enh 9552786)
MSC_SUPPLIES This table lists all the supplies for this plan. The supplies created by the planning process are added to this table. Description Name of item for which you are posting on-hand Organization
Supply quantity Flag indicating whether the order is firm Source instance code defined on the planning server
Project planning group. If more than one project belongs to the same planning group then this column is used to net the demand/supply across the projects Sub-inventory for on-hand quantities. This value should be specified in case of SRP. Lot number for on-hand quantities Lot expiration date Valid values are: 1 - Yes, 2 - No. If 1, then this row is deleted Required only for Collaborative Planning. You should provide the party name with which the company is registered in Collaborative Planning. For a planning (APS) only environment, this should be left null. Flag to identify VMI. Please provide the Organization ID for the Organization in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Inventory Item ID for the Inventory Item in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Project ID for the Project in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Task ID for the Task in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide a unique ID to identify this supply in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only Please provide the Disposition ID for the Supply in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Source side customer account id. Not in .dat files but needs to be populated in MSC_SUPPLIES (refer to Anwesh for details)
BeginningInventory.xml Select only selected lotStatus types (Pegged and Available) (ParametersValid_QOH_Status_Codes) Aggregate multiple records to branch/item level and accumulate the quantity (prior to Enh 9552786)
Supply Types 12 Intransit receipt 5 Planned order 7 Non-standard job 8 PO in receiving 11 Intransit shipment 1 Purchase order 2 Purchase requisition 3 Discrete job 4 Suggested aggregate repetitive schedule 13 Suggested repetitive schedule 14 Discrete job by-product 15 Nonstandard job by-product 16 Repetitive schedule by-product 17 Planned order by-product 27 Flow schedule 28 Flow schedule by-product 29 Payback supply 18 - on hand supply ???
planning process are added to this table. Logic
Fields Referenced E1 Table BeginningInventory.xml:beginnin BeginningInventory.xml:beginningInventory:itemCode gInventory:itemCode F41021 BeginningInventory.xml:beginningInventory:branchCo BeginningInventory.xml:beginnin de gInventory:branchCode F41021 <null>
E1 Field ITM MCU
BeginningInventory.xml:beginnin gInventory:beginningInventory:q BeginningInventory.xml:beginningInventory:beginningInventory:quantity uantity F41021 "2" Parameter.Source_Instance <null> <null>
calculation
<null> <null> <null> <null> "2"
Parameter.CP_Company_Name Parameter.Supply_Onhand_VMI_Flag (<null>)
<null>
see item name above
<null>
<null>
<null>
<null> <null> "18" see organization code above
"2"
calculation = if PO Quantity In Transit = '1', then quantity = F41021.PQOH + F41021.QTTR if PO Quantity In Inspection = '1', then quantity = F41021.PQOH + F41021.QTIN if PO Quantity In Operation 1 = '1', then quantity = F41021.PQOH + F41021.QTO1 if PO Quantity In Operation 2 = '1', then quantity = F41021.PQOH + F41021.QTO2 else quantity = F41021.PQOH
Table Description VCP-ODS Item_Name Price_List_Name Start_Date
End_Date
Price
Priority Primary_Uom_Flag Product_Uom_Code
Primary_UOM_Code
SR_INSTANCE_CODE
MSC_ST_PRICE_LIST This tables stores item price lists Description Name of Item. Same as in Item.dat file. Name of price list Effective start date for this price
Effective end date for this price
Unit price of the item
If multiple price lists exist for the item with overlapping dates, then what is the priority of the price list (i.e. which takes precedence) Whether the UOM code is primary/base UOM Code The UOM code for which this price is being set. e.g. say the price is $ 9.99 and the UOM code is Kilogram
The base/primary UOM code for this item (say Pound)
Source instance code defined on the planning server
Average of customer.xml:itemprice with supporting data coming from item in base.xml (joined by itemcode)
Note. The Time Varying Event is at the customer-item-branch level, this record is time varying event at the item level.
Logic Customer.xml:customer:itemPrice:itemCode Parameter.Price_List_Name
Fields Referenced E1 Table Customer.xml:customer:itemPrice:ite mCode F4106
Customer.xml:customer:itemPrice:ite Start Date of the time varying event. Refer to the FDD mCode:timeVaryingEvent:effectiveDat e on time varying events. Customer.xml:customer:itemPrice:ite End Date of the time varying event. Refer to the FDD mCode:timeVaryingEvent:effectiveDat e on time varying events. Average of customer.xml:itemprice: timevaryingevent:price where the current date is used to determine the time varying event record to be used customer.xml:itemprice: timevaryingevent:price Consolidate prices by item F4106 "1" "1"
F34A10
Base.xml:item:planningUom Parameter.Source_Instance
F34A10
g from item
Return to File Definitions E1 Field

ITM
Comment
UPRC
assignment
assignment
Substitute Item Name
Item Name
Not Implem
Customer Name Customer Site Code Effective Date Disable Date Reciprocal Flag
Substitution Set Partial Fulfillment Flag Source Instance Code
Company Name
Relationship Type
Organization Code Deleted Flag
Note: E1 supports a substitution ratio, VCP does not, so customers MUST set the ratio to 1 to have consistent results.
MSC_ITEM_SUBSTITUTES This table stores all the Relationships between Item Substitutes for planning. Description
Substitute Item
Item Name
Not Implemente
Customer Name. Not needed for relationship_type 5,8,18 Customer Site Name. Not needed for relationship_type 5,8,18 Effective Date of the Item Relationship Disable Date of the Item Relationship Defines whether the substitution relationship is effective in both the directions(1 Yes & 2 - No) Substitution set name used to define the Item relationship. Oracle APS will plan using the substitution definitions tied to an Substitution Set and
this enables the simulation of Substitution Partial Fulfillment of substitution is allowed or not( 1- Yes & 2 - No). Not needed for relationship_type 5,8,18 Source instance code defined on the planning server. Required only for Collaborative Planning. You should provide the party name with which the company is registered in Collaborative Planning. For planning (APS) only environment this should be left null. Type of relationship between two items. Valid values are : 2 (substitute relationship), 5 (service relationship), 8 (supersession relationship), 18 (repair to relationship). If no relationship type is given it defaults to 2.
Organization name in which relationship has been defined . Valid values are 1- Yes, 2- No
Note: E1 supports a substitution ratio, VCP does not, so customers MUST set the ratio to 1 to have consistent results.
ning. Logic Customer.xml:customerProductSubstitutionList:custo merProductSubstitution:substituteItemCode (item code to be decoded) Customer.xml:customerProductSubstitutionList:custo merProductSubstitution:itemCode (item code to be decoded) Find Customer.xml:Customer record where Customer.xml:Customer:customerCode=Customer.xm l:customerProductSubstitutionList:customerProductS ubstitution:customerCode Customer.xml:customer:parentName USE the record pointed to by the parentaddressnumber if null or zero use the current record Fields Referenced E1 Table Customer.xml:customerProductSubstituti onList:customerProductSubstitution:subs tituteItemCode F4104 Customer.xml:customerProductSubstituti onList:customerProductSubstitution:item Code F4104
lemented !
"2"
Customer.xml:customerProductSubstituti on:customerCode F4104
Customer.xml:customer:parentName F0101 Customer.xml:customerProductSubstitutionList:custo Customer.xml:customerProductSubstituti merProductSubstitution:customerCode on:customerCode F4104 Parameters.Base_Effective_Date <Null>
Parameter.Item_Substitution_Substitution_Set
Parameter.Item_Substitution_Partial_Fulfillment_Flag (2) Parameter.Source_Instance
<null>
Customer.xml:customerProductSubstituti Customer.xml:customerProductSubstitutionList:custo onList:customerProductSubstitution:bran merProductSubstitution:branchCode chCode F4102 "2"
Return to File Definitions E1 Field Comment
CITM
ITM for F4104.CITM is retrieved from F4101
ITM
AN8 ALPH AN8 F0101.AN8 = parentAddressNumber
MCU
Table Description VCP-ODS GROUP_CODE MEANING DESCRIPTION FROM_DATE TO_DATE ENABLED_FLAG SR_INSTANCE_CODE
COMPANY_NAME DELETED_FLAG
We will be using a User defined table "Resource Groups" to populate this table. Need to create the "hard coded" groups Machines, Crews, and Tools for each Organisation as well
MSC_RESOURCE_GROUPS This table stores different resource groups Description Identifier to define a group of resources. Description of the group. Effective start date of the group. Effective end date of the group. Source instance code defined on the planning server. Required only for Collaborative Planning. You should provide the party name with which the company is registered in CP. For a planning (APS) only environment, this should be left null. Valid values are: 1 - Yes, 2 - No. If 1, then this row is deleted.
We will be using a User defined table "Resource Groups" to populate this table. Need to create the "hard coded" groups Machines, Crews, and Tools for each Organisation as well - note from date is mandatory
Logic Resource Groups:Group Code (max 10 chars) Resource Groups:Meaning Resource Groups:Description Resource Groups:From Date Using Sys date Resource Groups:To Date Resource Groups:Enabled Flag Parameter.Source_Instance
Fields Referenced
E1 Table
ORGANIZATION_CODE LINE_FLAG AGGREGATED_RESOURCE_FLAG AVAILABLE_24_HOURS_FLAG SR_INSTANCE_CODE
RESOURCE_CODE
DEPARTMENT_CODE DEPARTMENT_CLASS OWNING_DEPARTMENT_CODE
CAPACITY_UNITS MAX_RATE MIN_RATE
RESOURCE_GROUP_NAME RESOURCE_GROUP_CODE RESOURCE_BALANCE_FLAG
BOTTLENECK_FLAG START_TIME STOP_TIME DEPARTMENT_DESCRIPTION
RESOURCE_DESCRIPTION OVER_UTILIZED_PERCENT UNDER_UTILIZED_PERCENT RESOURCE_SHORTAGE_TYPE RESOURCE_EXCESS_TYPE
USER_TIME_FENCE
UTILIZATION
EFFICIENCY
RESOURCE_INCLUDE_FLAG
CRITICAL_RESOURCE_FLAG RESOURCE_TYPE DISABLE_DATE DATE CTP_FLAG
DEPT_OVERHEAD_COST
RESOURCE_COST
RESOURCE_OVER_UTIL_COST PLANNING_EXCEPTION_SET DELETED_FLAG
COMPANY_NAME BATCHABLE_FLAG BATCHING_WINDOW MIN_CAPACITY MAX_CAPACITY UNIT_OF_MEASURE UOM_CLASS_TYPE
SOURCE_ORGANIZATION_ID
SOURCE_DEPARTMENT_ID
SOURCE_RESOURCE_ID
SOURCE_OWNING_DEPARTMENT_ID Idle_Time_Tolerance BATCHING_PENALTY Sds_scheduling_window SCHEDULE_TO_INSTANCE setup_time_percent UTILIZATION_CHANGE_PERCENT SETUP_TIME_TYPE UTILIZATION_CHANGE_TYPE
MSC_DEPARTMENT_RESOURCES This table stores the resources available for planning. Description
Organization code where this resource and department exist. Flag to indicate whether or not this resource is a line.
Valid values are: 1 - Available 24 hours, 2 - Not available 24 hours. Source instance code defined on the planning server.
Resource unique identifier.
Department unique identifier. Department class. For example, a grouping of departments in one class for reporting purposes. Owning department unique identifier.
Capacity/unit of resource in this department Maximum rate of production for a repetitive line. Minimum rate of production for a repetitive line.
Name Group name of the resource. Group code of the resource. Flag to indicate whether a resource is load balanced. Valid values are: 1 - Yes, 2 No.
Flag to indicate whether a resource is considered to be a bottleneck. Valid values are: 1 - Yes, 2 - No. Start time of the line. Stop time of the line. Description of the department or line.
Description of the resource. Over-utilization tolerance. Under-utilization tolerance.
The number of days within which planning generates an exception message.
Flag to indicate whether resource is to be considered during planning.
Flag to indicate if this is a critical resource. Used by LP and HLS. Valid values are: 1 - Machine, 2 - Person, 3 - Space, 4 - Miscellaneous, 5 - Amount. Disable date Flag indicating whether department resource is used for ATP or not. Valid values are: 1 - Yes, 2 - No.
Department overhead cost
Resource cost
Resource over-utilization cost Valid values are: 1 Yes, 2 - No. If 1, then this row is deleted. Required only for Collaborative Planning. You should provide the party name with which the company is registered in CP. For a planning (APS) only environment, this should be left null. Batchable flag Batching window Minimum capacity Maximum capacity Unit of measure Unit of measure class type Please provide the Organization ID for the Organization in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Department ID for the Department in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Resource ID for the Resource in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Owning Department ID for the Owning Department in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only.
Logic Manufacturing.xml:machineList:branchCode Manufacturing.xml:crewList:branchCode Manufacturing.xml:toolList:branchCode <null> (in case null defaults it to 2) <null> (if not aggregate populate 2) If all six shifts are 0 then set to "1" else "2" Parameter.Source_Instance Manufacturing.xml:machineList:machineCode Manufacturing.xml:crewList:crewCode Manufacturing.xml:toolList:toolCode
Fields Referenced Manufacturing.xml:machineList:branchCode Manufacturing.xml:crewList:branchCode Manufacturing.xml:toolList:branchCode
E1 Table
F34A110
Manufacturing.xml:machineList:machineCode Manufacturing.xml:crewList:crewCode Manufacturing.xml:toolList:toolCode
F34A110
If Parameter.Model_Department_Level = "WorkCenter" then Manufacturing.xml:machine:workCenter Manufacturing.xml:crew:workCenter Manufacturing.xml:tool:workCenter else Manufacturing.xml:machineList:branchCode Manufacturing.xml:crewList:branchCode Manufacturing.xml:toolList:branchCode <null> <null>
Manufacturing.xml:machine:workCenter Manufacturing.xml:crew:workCenter Manufacturing.xml:tool:workCenter Manufacturing.xml:machineList:branchCode Manufacturing.xml:crewList:branchCode Manufacturing.xml:toolList:branchCode
F34A110
F34A110
Manufacturing.xml:machineList:availableCapacity Manufacturing.xml:crewList:availableCapacity Manufacturing.xml:toolList:availableCapacity <null> <null> Use entry in Resource_Group_Details table (key branch/resource), if not present set to "Machine" or "Crew" or "Tool" based on the type of resource (max 10 chars) <Same as for Resource Group> Parameter.Resource Balance Flag (2) Manufacturing.xml:crew:criticalResource Manufacturing.xml:tool:criticalResource Manufacturing.xml:machine:criticalResource <null> <null> Use value from Dept Code above
Manufacturing.xml:machineList:availableCapacit y Manufacturing.xml:crewList:availableCapacity Manufacturing.xml:toolList:availableCapacity F34A110
Manufacturing.xml:crew:criticalResource Manufacturing.xml:tool:criticalResource Manufacturing.xml:machine:criticalResource
F30006
Use value from Dept Code above
Manufacturing.xml:machineList:name Manufacturing.xml:crewList:name Manufacturing.xml:toolList:name Parameter.Resource_Over_Utilization_%(101) Parameter.Resource_Under_Utilization _%(0) Parameter.Resource_Shortage_Type(180) (Period of Time to calc resource under util) Parameter.Resource_Excess_Type(180) (Period of Time to calc resource over util) Parameter.Resource_User_Time_Fence(<null>) (The number of days within which planning generates an exception message) Manufacturing.xml:crew:resourceUtilization Manufacturing.xml:tool:resourceUtilization Manufacturing.xml:machine:resourceUtilization Manufacturing.xml:crew:resourceEfficiency Manufacturing.xml:tool:resourceEfficiency Manufacturing.xml:machine:resourceEfficiency Manufacturing.xml:crew:criticalResource Manufacturing.xml:tool:criticalResource Manufacturing.xml:machine:criticalResource Manufacturing.xml:crew:criticalResource Manufacturing.xml:tool:criticalResource Manufacturing.xml:machine:criticalResource 1 if from machineList, 2 if from crewList, 4 if from toolList <null> Parameter.Resource_CTP_Flag (N)
Manufacturing.xml:machineList:name Manufacturing.xml:crewList:name Manufacturing.xml:toolList:name
F34A110
Manufacturing.xml:crew:resourceUtilization Manufacturing.xml:tool:resourceUtilization Manufacturing.xml:machine:resourceUtilization F30006 Manufacturing.xml:crew:resourceEfficiency Manufacturing.xml:tool:resourceEfficiency Manufacturing.xml:machine:resourceEfficiency Manufacturing.xml:crew:criticalResource Manufacturing.xml:tool:criticalResource Manufacturing.xml:machine:criticalResource Manufacturing.xml:crew:criticalResource Manufacturing.xml:tool:criticalResource Manufacturing.xml:machine:criticalResource
F30006
F30006
F30006
Manufacturing.xml:<resourcetype>:branchResou rceOHCosts F30008 If Parameter.Resource Costing Basis = "Machine" use Manufacturing.xml:<resourcetype>:branchResourceO HCosts If Parameter.Resource Costing Basis = "Labour" use Manufacturing.xml:<resource Manufacturing.xml:<resource type>:branchLaborOHCosts type>:branchLaborOHCosts
F30008
If Parameter.Resource Costing Basis = "Machine" use Manufacturing.xml:<resourcetype>:branchResourceC osts If Parameter.Resource Costing Basis = "Labour" use Manufacturing.xml:<resourcetype>:branchResou Manufacturing.xml:<resourcetype>:branchLaborCosts rceCosts F30008
Manufacturing.xml:<resourcetype>:branchLabor F30008 Parameter.Resource Over Util Cost_%(100) * Resource_Cost/100 ( Parameter.Resource Over Util Cost_% is % of Resource costs as a penality for over util) Parameter.Planning Exception Set (CATCHALL) 2
See RESOURCE_COST
Parameter.CP_Company_Name <null> <null> <null> <null> Parameter.Resource_unit_of_Measure (<null>) Parameter.Resource_UOM_Class_Type (<null>) Manufacturing.xml:machineList:branchCode Manufacturing.xml:crewList:branchCode Manufacturing.xml:toolList:branchCode Manufacturing.xml:machine:workCenter Manufacturing.xml:crew:workCenter Manufacturing.xml:tool:workCenter Manufacturing.xml:machineList:machineCode Manufacturing.xml:crewList:crewCode Manufacturing.xml:toolList:toolCode Manufacturing.xml:machine:workCenter Manufacturing.xml:crew:workCenter Manufacturing.xml:tool:workCenter <null> <null> <null> "2" <null> <null> <null> <null>
Manufacturing.xml:machineList:branchCode Manufacturing.xml:crewList:branchCode Manufacturing.xml:toolList:branchCode Manufacturing.xml:machine:workCenter Manufacturing.xml:crew:workCenter Manufacturing.xml:tool:workCenter Manufacturing.xml:machineList:machineCode Manufacturing.xml:crewList:crewCode Manufacturing.xml:toolList:toolCode Manufacturing.xml:machine:workCenter Manufacturing.xml:crew:workCenter Manufacturing.xml:tool:workCenter
MMCU
RESCD
MCU
MMCU
AVCAP
CRTW
1,2,3 are Yes 4,N are No
DL01
WORU
WORE
CRTW
CRTW
if(F3009.PORR = 'P') Then rate = (F30008.STRF/100) * F30008.STLF else rate = F30008.STRF F30008 record selected base MCU, MMCU and cost code equal to 07 if(F3009.PORR = 'P') Then rate = (F30008.MSTF/100) * F30008.MSFR else rate = F30008.MSTF F30008 record selected base MCU, MMCU and cost code equal to 07 MSFR
calculation calculation
F30008 record selected base MCU, MMCU and cost code equal to 07
STLF
F30008 record selected base MCU, MMCU and cost code equal to 07
DEPARTMENT_CODE
RESOURCE_CODE
SHIFT_NAME
ORGANIZATION_CODE SR_INSTANCE_CODE DELETED_FLAG
COMPANY_NAME
CAPACITY_UNITS
MSC_RESOURCE_SHIFTS Resource shift information Description
Department unique identifier. This department should already be defined in the table MSC_ST_DEPARTMENT_RESOURCES.
Resource unique identifier. This resource should already be defined in the table MSC_ST_DEPARTMENT_RESOURCES.
Shift name defined in Calendar BO.
Organization code where this resource and department exist. Source instance code defined on the planning server. Valid values are: 1 - Yes, 2 - No. If 1, then this row is deleted. Required only for Collaborative Planning. You should provide the party name with which the company is registered in CP. For a planning (APS) only environment, this should be left null.
Capacity Units
Logic Get the Dept Code from DepartmentResource.dat for this Resource Code alternatively (and less desirably) If Parameter.Model_Department_Level = "WorkCenter" then Manufacturing.xml:machine:workCenter Manufacturing.xml:machine:machineCode Manufacturing.xml:crew:crewCode Manufacturing.xml:tool:toolCode
Fields Referenced Manufacturing.xml:machine:workCenter Manufacturing.xml:crew:workCenter Manufacturing.xml:tool:workCenter Manufacturing.xml:machineList:branchCode Manufacturing.xml:crewList:branchCode Manufacturing.xml:toolList:branchCode Manufacturing.xml:machineList:machineCode Manufacturing.xml:crewList:crewCode Manufacturing.xml:toolList:toolCode
E1 Table
F34A110
F34A110
F34A110
Manufacturing.xml:machine:shift1 to 6 Manufacturing.xml:crew:shift1 to 6 Manufacturing.xml:tool:shift1 to 6 F30006 Manufacturing.xml:machine:shift1 to 6 Manufacturing.xml:crew:shift1 to 6 Manufacturing.xml:tool:shift1 to 6 F30006 Manufacturing.xml:machine:shift1 to 6 Manufacturing.xml:crew:shift1 to 6 Manufacturing.xml:tool:shift1 to 6 F30006 Manufacturing.xml:machine:shift1 to 6 Manufacturing.xml:crew:shift1 to 6 Manufacturing.xml:tool:shift1 to 6 A record will be created for each non-null or non zero shift Manufacturing.xml:machine:shift1 to 6, if shift1 is not null, then set to1, etc. Manufacturing.xml:crew:shift1 to 6, if shift1 is not null, then set to1, etc. Manufacturing.xml:tool:shift1 to 6, if shift1 is not null, then set to1, etc. Manufacturing.xml:machine:branchCode Manufacturing.xml:crew:branchCode Manufacturing.xml:tool:branchCode Parameter.Source_Instance "2" F30006 Manufacturing.xml:machine:shift1 to 6 Manufacturing.xml:crew:shift1 to 6 Manufacturing.xml:tool:shift1 to 6 F30006 Manufacturing.xml:machine:shift1 to 6 Manufacturing.xml:crew:shift1 to 6 Manufacturing.xml:tool:shift1 to 6 F30006 Manufacturing.xml:machineList:branchCode Manufacturing.xml:crewList:branchCode Manufacturing.xml:toolList:branchCode
F34A110
Parameter.CP_Company_Name Manufacturing.xml:machine|crew|tool:timeVaryingE vent:availableCapacity - Use the value active for plan Manufacturing.xml:machine|crew|tool:timeVary option.base Date ingEvent:availableCapacity F34A110
MCU
MMCU
RESCD
WRHR
WRH2
WRH3
WRH4
WRH5
WRH6
MMCU
AVCAP
ROUTING_NAME ASSEMBLY_NAME ROUTING_TYPE ORGANIZATION_CODE SR_INSTANCE_CODE ROUTING_COMMENT ALTERNATE_ROUTING_DESIGNATOR PROJECT_NUMBER TASK_NUMBER LINE_CODE
UOM_CODE CFM_ROUTING_FLAG CTP_FLAG
ROUTING_QUANTITY BOM_NAME ALTERNATE_BOM_DESIGNATOR DELETED_FLAG
COMPANY_NAME FIRST_OPERATION_SEQ_CODE LAST_OPERATION_SEQ_CODE COMMON_ROUTING_NAME ITEM_PROCESS_COST
SOURCE_ASSEMBLY_ITEM_ID
SOURCE_ROUTING_SEQUENCE_ID
SOURCE_TASK_ID
SOURCE_LINE_ID
SOURCE_BILL_SEQUENCE_ID
SOURCE_COMMON_ROUTING_SEQ_ID
MSC_ROUTINGS This table stores the different routings available for a bill of material. Description
Name of routing. If routing name is not provided, it will be substituted with ASSEMBLY_NAME. Name of item or component.
Organization code where this resource and department exist. Source instance code defined on the planning server.
Identifier to specify if routing is primary or alternate.
Valid values are: 1 - Yes, 2 - No. Flag indicating that this routing is used in and ATP calculation. Valid values are: 1 Yes, 2 - No.
Routing quantity
Alternate BOM reference Valid values are: 1 - Yes, 2 - No. If 1, then this row is deleted. Required only for Collaborative Planning. You should provide the party name with which the company is registered in CP. For a planning (APS) only environment, this should be left null.
Common Routing Sequence Name Processing cost of the Item. Please provide the Organization ID for the Organization in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Assembly Item ID for the Assembly Item in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only.
Please provide the Routing Sequence ID for the Routing Sequence in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Task ID for the Task in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Line ID for the Line in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Bill Sequence ID for the Bill Sequence in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Common Routing Sequence ID for the Common Routing Sequence in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only.
Logic
Fields Referenced
E1 Table
Manufacturing.xml:RoutingList:routing:routingCod e 28004|59412|M |1| | (second field) Manufacturing.xml:RoutingList:routing:routingCod e 28004|59412|M |1| | (second field) "1" 1=Manufacturing, 2=Engineering Manufacturing.xml:RoutingList:routing:routingCode 28004|59412|M |1| | (first field) Parameter.Source_Instance Manufacturing.xml:RoutingList:routing:routingCode (all fields) <null> <null> <null> <null>
Manufacturing.xml:RoutingList:routing:routingC ode F3003 Refer to ROUTING_NAME
Refer to ROUTING_NAME
Planning UOM from Base.xml:item where the item code is the primary item for the routing (2nd field of Manufacturing.xml:RoutingList:routing:routingCode 28004|59412|M |1| | ) "2"
F34A10
Parameter.Routing CTP Flag (2) Manufacturing.xml:RoutingList:routing:routingCode 28004|59412|M |1| | (fourth field) Refer to ROUTING_NAME If zero, set to one Manufacturing.xml:RoutingList:routing:routingCod Refer to ROUTING_NAME e 28004|59412|M |1| | (second field) <null> "2"
Parameter.CP_Company_Name <null> <null> <null> <null> Manufacturing.xml:RoutingList:routing:routingCode 28004|59412|M |1| | (first field) Manufacturing.xml:RoutingList:routing:routingCode 28004|59412|M |1| | (second field)
<null>
<null>
<null>
<null>
<null>
Return to File Definitions E1 Field Comment if UDC(34A|GU).special Handeling = 1 concatenation = MMCU|KIT|TRT|BQTY|OPSQ|OPSC|LINE|EFFF else concatenation = MMCU|KIT|TRT|BQTY|OPSC|LINE
concatenation
assignment
ROUTING_NAME ASSEMBLY_NAME ALTERNATE_ROUTING_DESIGNATOR
OPERATION_SEQ_CODE
EFFECTIVITY_DATE OPTION_DEPENDENT_FLAG
DEPARTMENT_CODE ORGANIZATION_CODE SR_INSTANCE_CODE OPERATION_DESCRIPTION DISABLE_DATE FROM_UNIT_NUMBER TO_UNIT_NUMBER OPERATION_TYPE
MINIMUM_TRANSFER_QUANTITY
YIELD OPERATION_LEAD_TIME_PERCENT CUMULATIVE_YIELD REVERSE_CUMULATIVE_YIELD NET_PLANNING_PERCENT SETUP_DURATION TEAR_DOWN_DURATION UOM_CODE STANDARD_OPERATION_CODE DELETED_FLAG
COMPANY_NAME
SOURCE_OPERATION_SEQUENCE_ID
SOURCE_OPERATION_SEQ_NUM
SOURCE_DEPARTMENT_ID Setup_Code ORIG_RESOURCE_SEQ_CODE
MSC_ROUTING_OPERATIONS This tables stores the operations composing each routing. Description
Name of routing. Name of the item or component. Identifier to specify if routing is a primary or an alternate. Default is primary.
Identifier or code for a single step in an operation sequence.
Effective start date of an operation. Flag to indicate this operation is option dependent.
Department unique identifier. This department should already be defined in the table MSC_ST_DEPARTMENT_RESOURCES. Organization code where this resource and department exist. Source instance code defined on the planning server.
Effective from this unit number. Effective up to this unit number. Valid values are: 1, 2, 3, and Null.
Indicating the amount of overlap its lead time has with the parent lead time. Cumulative process yield from the beginning of the routing to this operation. Cumulative process yield from the end of the routing to this operation. Duration of the set up. Duration of the tear down for this operation. Unit of measure Valid values are: 1 - Yes, 2 - No. If 1, then this row is deleted. Required only for Collaborative Planning. You should provide the party name with which the company is registered in CP. For a planning (APS) only environment, this should be left null. Please provide the Organization ID for the Organization in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Operation Sequence ID for the Operation Sequence in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Operation Sequence Number for the Operation Sequence in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Department ID for the Department in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only.
The primary data source is the operationSetList in Manufacturing.xml In E1 there will only be one operationCode per operationSet
Logic
Fields Referenced
E1 Table
Manufacturing.xml:RoutingList:routing:routingCod Manufacturing.xml:RoutingList:routing:routingC e 28004|59412|M |1| | (second field) ode F3003 Manufacturing.xml:RoutingList:routing:routingCod Refer to ROUTING_NAME e 28004|59412|M |1| | (second field) <null>
The fifth field of Operation Code * 100 Can be derived by analysing OperationSetList and Network. Refer to the FDD section "Determining Operation Sequence Code" use effectivity dates on Manufacturing.xml:branchoperation (joined by branch and operation) Parameter.Option Flag (1) Get the Dept CodeDependent from DepartmentResource.dat for this Resource Code alternatively (and less desirably) If Parameter.Model_Department_Level = "WorkCenter" then Retreive Work Centre from the 8th field of OperationCode (Manufacturing.xml:routingList:routing:operationsSet List:operation) (28004|59409|M |100|10.00| | |WC2-104) else Retreive Work Centre from the first field of OperationCode (Manufacturing.xml:routingList:routing:operationsSet List:operation) (28004|59409|M |100|10.00| | |WC2-104) Manufacturing.xml:RoutingList:routing:routingCode 28004|59412|M |1| | (first field) Parameter.Source_Instance Manuifacturing.xml:routing:operationSet:operationCo de Refer to the effectivity date section in the "Complex Modeling Solutions" section of the FDD <null> <null> <null>
Manufacturing.xml:operation:operationCode Manufacturing.xml:branchOperation:timeVaryin gEvent
F3003
Manufacturing.xml:machine:workCenter Manufacturing.xml:crew:workCenter Manufacturing.xml:tool:workCenter Refer to ROUTING_NAME
F34A110
Manufacturing.xml:operation:operationCode
<null> Bug 8992729: Manufacturing.xml:operation:resourceSet:operationB OR:timeVaryingEvent:lotMulti ple for the resource specified in Manufacturing.xml:operation:factorResourceOrSet for that operation If Manufacturing.xml:operation:producedItemList:prod ucedItem:producedItemBom:yield exists then Manufacturing.xml:operation:producedItemList:prod ucedItem:producedItemBom:yield/100 else "1" Where operation is the operation for this record, (in phase one we are only expecting one produced item per operation, but just select first to avoid future issues) Calculate starttime as a % of total network time Read the explanation <null> <null> <null> <null> <null> Parameter.Base_Time_UOM<null> <null> "2"
Manufacturing.xml:operation:resourceSet:opera tionBOR:timeVaryingEvent:lotMultiple
Manufacturing.xml:operation:producedItemList: producedItem:producedItemBom:yield
Parameter.CP_Company_Name Manufacturing.xml:RoutingList:routing:routingCode 28004|59412|M |1| | (first field)
<null>
<null>
<null> <null> "10"
concatenation
concatenation
if UDC(34A|GU).special Handeling = 1 concatenation = F3003.mmcu|F3003.kit|F3003.trt|F3003.bqty|F3003.opsq|F3003. opsc|F3003.line|F3003.efff|F3003.mcu else concatenation = F3003.mmcu|F3003.kit|F3003.trt|F3003.bqty|F3003.opsq|F3003. opsc|F3003.line|F3003.mcu
MCU
assignment
assignment = hard coded value of "100"
ROUTING_NAME
ASSEMBLY_NAME
OPERATION_SEQ_CODE
RESOURCE_SEQ_CODE
DEPARTMENT_CODE
RESOURCE_CODE
ALTERNATE_NUMBER
PRINCIPAL_FLAG BASIS_TYPE RESOURCE_USAGE
UOM_CODE ORGANIZATION_CODE SR_INSTANCE_CODE
MAX_RESOURCE_UNITS
RESOURCE_UNITS
RESOURCE_TYPE DELETED_FLAG
COMPANY_NAME ALTERNATE_ROUTING_DESIGNATOR
OPERATION_EFFECTIVITY_DATE ACTIVITY_GROUP_ID
SCHEDULE_FLAG RESOURCE_OFFSET_PERCENT
SOURCE_ROUTING_SEQUENCE_ID
SOURCE_OPERATION_SEQUENCE_ID
SOURCE_RESOURCE_SEQ_NUM
SOURCE_RESOURCE_ID
SOURCE_DEPARTMENT_ID SETUP_CODE
ORIG_RESOURCE_SEQ_CODE
ROUTING_NAME ASSEMBLY_NAME OPERATION_SEQ_CODE RESOURCE_SEQ_CODE DEPARTMENT_CODE RESOURCE_CODE ALTERNATE_NUMBER PRINCIPAL_FLAG BASIS_TYPE RESOURCE_USAGE UOM_CODE ORGANIZATION_CODE SR_INSTANCE_CODE MAX_RESOURCE_UNITS RESOURCE_UNITS RESOURCE_TYPE DELETED_FLAG COMPANY_NAME ALTERNATE_ROUTING_DESIGNATOR OPERATION_EFFECTIVITY_DATE ACTIVITY_GROUP_ID SCHEDULE_FLAG RESOURCE_OFFSET_PERCENT SOURCE_ROUTING_SEQUENCE_ID SOURCE_OPERATION_SEQUENCE_ID SOURCE_RESOURCE_SEQ_NUM SOURCE_RESOURCE_ID SOURCE_DEPARTMENT_ID
MSC_OPERATION_RESOURCES This table stores operation resources from a resource sequence. For each resource sequence, we have an alternative between different set Description
Routing unique identifier. Routing should be defined prior to specifying an operation resource.
Name of assembly or inventory item name.
Derived in the post processing stage.
Resource sequence identifier.
Department unique identifier.
Resource identifier for the operation. Resource should be defined in MSC_ST_DEPARTMENT_RESOURCES.
Flag indicating whether the resource is a principal resource or not. Costing basis type. Valid values are: 1 - Item, 2 - Lot, 3 - Resource Units, 4 - Resource Value, 5 - Total Value, 6 - Activity Usage of the resource.
Unit of measure Organization code where this resource and department exist. Source instance code defined on the planning server.
Maximum number of resource units consumed by the operation.
Number of units of the resource
Machine or labor Valid values are: 1 - Yes, 2 - No. If 1, then this row is deleted. Required only for Collaborative Planning. You should provide the party name with which the company is registered in CP. For a planning (APS) only environment, this should be left null. Routing unique identifier. Routing should already be defined.
All activities within an operation that need to be processed on the same resource (alternate) have the same setup group id
Schedule Flag Please provide the Routing Sequence ID for the Routing Sequence in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Operation Sequence ID for the Operation Sequence in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Resource Sequence Number for the Resource Sequence in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Resource ID for the Resource in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Department ID for the Department in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only.
Primarily from the OperationBOR in Manufacturing.xml, this is linked to the
Primarily from the OperationBOR in Manufacturing.xml, this is linked to the Routing via the operation Traverse from Routing->operationSetList->operationsCode -> then look this operation up in OperationList/operation and use the operationBOR underneath it Note: When there are alternates involved the entire routing operationresource for the operation will need to be replicated. NOTE: This area is in a state of review at present An Operation requires Machine: Press 1 (20 mins) OR Press 2 (30 mins) ; Duration resource Machine: Packer ; not a duration resource Crew: Press Operator All resources start at the same time and have the same usage.
Press 1
10 Press 1 0 1
DESIGNATOR
EQUENCE_ID
ch resource sequence, we have an alternative between different set of operation resources. This is described by the Alternate Number. Logic Fields Referenced E1 Table Manufacturing.xml:RoutingList:routing:routingCod e 28004|59412|M |1| | (second field) (the routing Manufacturing.xml:RoutingList:routing:routingC is the found by looking up the operation in OperationSet List) ode F3003
Manufacturing.xml:RoutingList:routing:routingCod e 28004|59412|M |1| | (second field) see ROUTING_NAME
F3003
Can be derived by analysing OperationSetList and Network. Refer to the FDD section "Determining Operation Sequence Code" Manufacturing.xml:operation:operationCode As we don't support activities this will always be 10.that is all activities in an operation happen at the same time Manufacturing.xml:machine:workCenter Get the Dept Code from DepartmentResource.dat for Manufacturing.xml:crew:workCenter this Resource Code Manufacturing.xml:tool:workCenter Manufacturing.xml:machineList:machineCode Manufacturing.xml:operation:resourceSetList:resourc Manufacturing.xml:crewList:crewCode eSet:OperationBor:resourceCode Manufacturing.xml:toolList:toolCode If preference for this "set of resources". See FDD for description in the "Complex Modelling" section to see how to calculate this Set to 1 if duration resource, otherwise set to 2. The duration resource is determined by the set pointed to by durationResourceOrSet "1" Manufacturing.xml:operation:resourceSetList:resourc eSet:OperationBor:duration Manufacturing.xml:operation:resourceSetList:resourc eSet:OperationBor:timevaryingevent (use base date):durationUnit Manufacturing.xml:operation:resourceSetList:resourc eSet:OperationBor:branchCode Parameter.Source_Instance
F3003
F34A110
F34A110
Manufacturing.xml:operation:resourceSetList:res ourceSet:OperationBor:duration F34A120 Manufacturing.xml:operation:resourceSetList:res ourceSet:OperationBor:branchCode F34A120
Manufacturing.xml:<resource|Crew|Machine|Tool>:< timeVaryingEvent>availableCapacity (join operationBOR to crew|machine|tool by branch code and resourceCode)
Manufacturing.xml:machineList:availableCapacit y Manufacturing.xml:crewList:availableCapacity Manufacturing.xml:toolList:availableCapacity F34A110
Manufacturing.xml:operation:resourceSetList:resourc Manufacturing.xml:operation:resourceSetList:res eSet:OperationBor:capacityRequired ourceSet:OperationBor:capacityRequired F34A120 Determine if resource appears in MachineList or CrewList or ToolList. 0 = Machine, 1=Crew, 0 = Tool "2"
Parameter.CP_Company_Name <null> use effectivity dates on Manufacturing.xml:branchoperation (joined by branch and operation) <null> "1" valid values are 1,2,3,4. 1 Yes 2 No 3 Prior 4 Next 0
Manufacturing.xml:branchOperation:timeVaryin gEvent
<null>
<null>
<null>
<null>
<null> If SetupAllocations(branch, item, operation_sequence,resource) exists, then use SetupAllocations from that entry If SetupAllocations(branch, item_category (using Parameters.Change_Over_Category,resource), operation_sequence) exists, then use SetupAllocations from that entry Otherwise <null> Refer to the FDD for use of Category Codes "10"
is linked to the
is linked to the
> then look this
Press 2
Press Crew
Packer
10 Press 2 1 1
10 Press Crew 0 2
10 Packer 0 2
Return to File Definitions Comment if UDC(34A|GU).special Handeling = 1 concatenation = MMCU|KIT|TRT|BQTY|OPSQ|OPSC|LINE|EFFF else concatenation = MMCU|KIT|TRT|BQTY|OPSC|LINE if UDC(34A|GU).special Handeling = 1 concatenation = MMCU|KIT|TRT|BQTY|OPSQ|OPSC|LINE|EFFF else concatenation = MMCU|KIT|TRT|BQTY|OPSC|LINE if UDC(34A|GU).special Handeling = 1 concatenation = F3003.mmcu|F3003.kit|F3003.trt|F3003.bqty|F3003.opsq|F3003. opsc|F3003.line|F3003.efff|F3003.mcu else concatenation = F3003.mmcu|F3003.kit|F3003.trt|F3003.bqty|F3003.opsq|F3003. opsc|F3003.line|F3003.mcu
nate Number. E1 Field
concatenation
concatenation
concatenation
MCU
RESCD
APSDUR MMCU
AVCAP
CAPREQ
Press Crew
Packer
10 Press Crew 1 2
10 Packer 1 2
BOM_NAME ORGANIZATION_CODE ASSEMBLY_NAME ASSEMBLY_TYPE SR_INSTANCE_CODE ALTERNATE_BOM_DESIGNATOR SPECIFIC_ASSEMBLY_COMMENT PENDING_FROM_ECN BOM_SCALING_TYPE ASSEMBLY_QUANTITY
UOM DELETED_FLAG
COMPANY_NAME ITEM_PROCESS_COST
MSC_BOMS This table represents the Bills Of Material of an item created at source applications. Description
Bill of Material name. This value defaults to Assembly Name if left null. Organization Identifier on the planning server. Item name Valid values are: 1 - Manufacturing bill, 2 - Engineering bill Source instance code defined on the planning server. Alternate BOM's reference. Comments ECO pending number (OPM) Controls scaling behavior Assembly quantity
Unit of measure code Valid values are: 1 - Yes, 2- No. If 1, then this row is deleted. Required only for Collaborative Planning. You should provide the party name with which the company is registered in CP. For a planning (APS) only environment, this is left null. Processing cost of the Item. Please provide the Organization ID for the Organization in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Bill Sequence ID for the Bill Sequence in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Inventory Item ID for the Item in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only.
Routings->Operations->ProducedItemList
pplications. Logic Fields Referenced E1 Table
Manufacturing.xml:RoutingList:routing:routingCod e 28004|59412|M |1| | (second field) Manufacturing.xml:routing:routingCode (first component) Manufacturing.xml:RoutingList:routing:routingCod e 28004|59412|M |1| | (second field) 1 Parameter.Source_Instance <null> Manufacturing.xml:routing:description <null> <null> quantity from produced Item in Manufacturing.xml.
Manufacturing.xml:RoutingList:routing:routingC ode F3003 Refer to BOM_NAME Refer to BOM_NAME
Manufacturing.xml:routing:description
F3003
Manufacturing.xml:operation:producedItemB om:quantity F3003
Planning UOM for the above item code (Base.xml) 2
F34A10
Parameter.CP_Company_Name <null> Manufacturing.xml:routing:routingCode (first component)
Refer to BOM_NAME
<null> Manufacturing.xml:routing:routingCode (second component)
Refer to BOM_NAME
concatenation
KITL
BQTY
if F3003.BQTY > 0, then quantity is converted to planning unit of measure else quantity = "1"
assignment
COMPONENT_NAME COMPONENT_TYPE
BOM_NAME ORGANIZATION_CODE ASSEMBLY_NAME REVISION USAGE_QUANTITY
COMPONENT_YIELD_FACTOR
UOM_CODE SR_INSTANCE_CODE ALTERNATE_BOM_DESIGNATOR CHANGE_NOTICE SCALING_TYPE EFFECTIVITY_DATE DATE DISABLE_DATE USE_UP_CODE OPERATION_OFFSET_PERCENT OPTIONAL_COMPONENT
WIP_SUPPLY_TYPE PLANNING_FACTOR ATP_FLAG
OPERATION_SEQ_CODE DELETED_FLAG DRIVING_ITEM_NAME
COMPANY_NAME ROUNDING_DIRECTION
SOURCE_COMPONENT_SEQUENCE_ID
SOURCE_USING_ASSEMBLY_ID
SOURCE_DRIVING_ITEM_ID
MSC_BOM_COMPONENTS This table stores Bill of material data for plans in Oracle Advanced Planning and Oracle Supply Chain Hub products. Description
Component's item name. Valid values are: 1 - Component, -1 - Ingredient Component, 2 - By-Product
Bill of material name. Defaults to Assembly Name if null. Organization Identifier on the planning server. Item name Inventory item revision code Component's quantity per assembly
Value should be less or equal to 1.
Unit of measure code Source Instance Code is defined on the planning server. Alternate BOM's reference ECO pending number Scaling type Date from which the component becomes effective on the bill of material. Date to which the component is effective on the bill of material. Valid values are: 1 - Yes, 2 - No. If Yes, this component is effective until the available quantity becomes null. Value should be less than or equal to 100. Valid values are: 1 - Yes, 2 - No. If optional, use planning factor to determine demand.
1, 2, 3, 4, 5, 6, 7 Value should be less than or equal to 100. Valid values are: 1 -Yes, 2 - No.
Valid values are: 1 - Yes, 2 - No. If 1, then this row is deleted. Item whose consumption determines the switch to this component. Required only for Collaborative Planning. You should provide the party name with which the company is registered in CP. For a planning (APS) only environment, this should be left null. Rounding Direction. Please provide the Organization ID for the Organization in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Bill Sequence ID for the Bill Sequence in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Component Sequence ID for the Component Sequence in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Using Assembly ID for the Assembly in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Inventory Item ID for the Item in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Driving Item ID for the Driving Item in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only.
Primarily retreived from consumedItemSet in Operation using the most prefered for each consumeditemset
ing and Oracle Supply Chain Hub products. Logic Fields Referenced E1 Table Manufacturing.xml:operation:consumedItemSet:c onsumedItemBom:itemCode (from lowest preference record in consumedItemSet - use preference under timevaryingevent) For phase one there will only be the preferred Manufacturing.xml:operation:consumedItemSet: raw material consumedItemBom:itemCode F3002 "1"
Manufacturing.xml:routing:routingCode (second component) Manufacturing.xml:routing:routingCode (first component) Manufacturing.xml:routing:routingCode (second component) <null> Manufacturing.xml:operation:consumedItemBom:qua ntity 1(Manufacturing.xml:operation:consumedItemBom:scr ap factor / 100)
Manufacturing.xml:RoutingList:routing:routingC ode F3003 Refer to BOM_NAME Refer to BOM_NAME Manufacturing.xml:operation:consumedItemBo m:quantity F3002 Manufacturing.xml:operation:consumedItemBo m:scrap factor F3002
Planning UOM for the component item (Base.xml) Parameters.Source_Instance <null> <null> <null> operation:consumedItemSet:consumedItemBom:time VaryingEvent:effectiveDate Refer to the effectivity date section in the "Complex Modeling Solutions" section of the FDD "2" <null> "2"
F34A10
operation:consumedItemSet:consumedItemBom :timeVaryingEvent:effectiveDate operation:consumedItemSet:consumedItemBom :timeVaryingEvent:effectiveDate
look the compnent up in Item.dat (component name=item) and use that items "WIP Supply Type" Manufacturing.xml:consumeditemBom:bomPlanningF Manufacturing.xml:consumeditemBom:bomPlan actor ningFactor F3002 Parameter.ATP_Flag (2)
The fifth field of Operation Code * 100 Get this from the RoutingOperation.dat where the operation code in Manufacturing.xml if the is the key to RoutingOperation.dat Manufacturing.xml:operation:operationCode "2" <null>
F3003
Parameter.CP_Company_Name Parameter.Component_Rounding_Direction(<null>) Manufacturing.xml:routing:routingCode (first component) Manufacturing.xml:routing:routingCode (second component)
Refer to BOM_NAME
Refer to BOM_NAME
<null>
<null>
<null>
<null>
ITM
concatenation
if UDC(34A|GU).special Handeling = 1 concatenation = MMCU|KIT|TRT|BQTY|OPSQ|OPSC|LINE|EFFF else concatenation = MMCU|KIT|TRT|BQTY|OPSC|LINE
QNTY
converted to planning unit of measure
SCRP
assignment
FTRP
concatenation
if UDC(34A|GU).special Handeling = 1 concatenation = F3003.mmcu|F3003.kit|F3003.trt|F3003.bqty|F3003.opsq|F3003. opsc|F3003.line|F3003.efff|F3003.mcu else concatenation = F3003.mmcu|F3003.kit|F3003.trt|F3003.bqty|F3003.opsq|F3003. opsc|F3003.line|F3003.mcu
Table Description VCP-ODS SR_Instance_Code Resource_Code Organization_code Setup_Code Setup_Description
Retrieved from user defined table "Setup Definitions"
MSC_ST_RESOURCE_SETUPS Defines te setup codes against resources and organisations Description
Retrieved from user defined table "Setup Definitions"
Logic Parameter.Source_Instance Setup Definitions.Resource_Code Setup Definitions.Branch Setup Definitions.Setup_Code Setup Definitions.Setup_Description
Fields Referenced
E1 Table
Table Description VCP-ODS Sr_Instance_Code resource_code organization_code from_setup_code to_setup_code standard_operation_code transition_time transition_uom transition_penalty
department_code
Retrieved from user defined table "Setup Transitions"
MSC_ST_SETUP_TRANSITIONS The transition information from one setup type to another Description Sr_Instance_Code resource_code organization_code from_setup_code to_setup_code standard_operation_code transition_time transition_uom transition_penalty
department_code
Retrieved from user defined table "Setup Transitions"
Logic Fields Referenced Parameter.Source_Instance Setup Transitions.resource_code Setup Transitions.branch Setup Transitions.from_setup_code Setup Transitions.to_setup_code Setup Transitions.standard_operation_code Setup Transitions .transition_time Setup Transitions.transition_uom Setup Transitions.transition_penalty Get Department_Code From DeptResources.dat table (or workCenter from Manufacturing.xml) (join by Resource_code and organization_code)
E1 Table
Table Description VCP-ODS sr_instance_code standard_operation_code resource_code organization_code department_code resource_seq_code resource_usage basis_type resource_units substitute_group_num uom_code schedule_flag operation_code
MSC_ST_STD_OP_RESOURCES Standard Operations associated with setup types Description
Retrieved from user defined table "Standard Operation Resources"
Logic Standard Operation Resources:standard_operation_code Standard Operation Resources:resource_code Standard Operation Resources:organization_code From Dept Resources (join by Resource_code and organization_code) "10" Standard Operation Resources:resource_usage "2" (lot) Standard Operation Resources:resource_units <null> Standard Operation Resources:uom_code Standard Operation Resources:schedule_flag (set to 1 if "Yes", otherwise set to 2) Used the same value used for standard_operation_code (above)
Fields Referenced E1 Table
E1 Field
Table Description VCP-ODS From Organization Code To Organization Code Source Instance Code Ship Method Default Flag In-transit Time Time UOM Code Weight Capacity Weight UOM Code Volume Capacity Volume UOM Cost Per Weight Unit Cost Per Volume Unit Transportation Capacity Over-utilization cost
Company Name From Location Code To Location Code To Region Type To Country To Country Code To State To State Code To City To City Code To Postal Code From To Postal Code To To Zone From Region Type From Country From Country Code From State From State Code From City From City Code From Postal Code From From Postal Code To From Zone deleted flag
Mainly from Supplier.xml:SupplierItem aggregate to one record per supplier/branch
MSC_INTERORG_SHIP_METHODS - Purchasing This table stores the different shipment methods and their availability. Description Organization code for point of origin of the shipment. Organization code for destination of the shipment. Source instance code defined on the planning server. Method of shipment
Required only for Collaborative Planning. You should provide the party name with which the company is registered in Collaborative Planning. For a planning (APS) only environment, this should be left null. Ship from location in the shipment method relationship. Ship to location in the shipment method relationship. To Region Type To Country To Country Code To State To State Code To City To City Code To Postal Code From To Postal Code To To Zone From Region Type From Country From Country Code From State From State Code From City From City Code From Postal Code From From Postal Code To From Zone
Mainly from Supplier.xml:SupplierItem aggregate to one record per supplier/branch
Logic <null> <null> Parameter.Source_Instance "Purchasing" "1" 0 Supplier.xml:supplier:supplierItem:leadTimeUom <null> <null> <null> <null> <null> <null> <null>
Fields Referenced
E1 Table
Supplier.xml:supplier:supplierItem:leadTime Uom
Parameter.CP_Company_Name <null> Supplier.xml:supplier:supplierItem:branchCode <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> 2 Supplier.xml:supplier:supplierItem:branchCo de F43090
hard coded to "Days"
MCU
Table Description VCP-ODS From Organization Code To Organization Code Source Instance Code Ship Method
Default Flag
In-transit Time
Time UOM Code
Weight Capacity
Weight UOM Code
Volume Capacity
Volume UOM
Cost Per Weight Unit
Cost Per Volume Unit
Transportation Capacity Over-utilization cost
Company Name From Location Code To Location Code To Region Type To Country To Country Code To State To State Code To City To City Code To Postal Code From To Postal Code To
To Zone From Region Type From Country From Country Code From State From State Code From City From City Code From Postal Code From From Postal Code To From Zone
Mainly from Distribution.xml Join with user defined table "ShippingMethods" key =
Mode
MSC_INTERORG_SHIP_METHODS - Inter Org This table stores the different shipment methods and their availability. Description Organization code for point of origin of the shipment. Organization code for destination of the shipment. Source instance code defined on the planning server. Method of shipment
Required only for Collaborative Planning. You should provide the party name with which the company is registered in Collaborative Planning. For a planning (APS) only environment, this should be left null. Ship from location in the shipment method relationship. Ship to location in the shipment method relationship. To Region Type To Country To Country Code To State To State Code To City To City Code To Postal Code From To Postal Code To
To Zone From Region Type From Country From Country Code From State From State Code From City From City Code From Postal Code From From Postal Code To From Zone
Mainly from Distribution.xml Join with user defined table "ShippingMethods" key = Distribution.xml:lane:originBranchCode=ShippingMethods:FromBranch Distribution.xml:lane:destinationBranchCode=ShippingMethods:ToBranch Distribution.xml:lane:transportMode:transportModeCode=ShippingMethods:Transport Mode NOTE: ShippingMethods will have original branch codes, that is will need translation
Logic Distribution.xml:lane:originBranchCode
Fields Referenced Distribution.xml:lane:originBranchCode
E1 Table F3403
Distribution.xml:lane:destinationBranchCode Distribution.xml:lane:destinationBranchCode F3403 Parameter.Source_Instance Distribution.xml:lane:transportMode:transportModeC Distribution.xml:lane:transportMode:transportM ode odeCode F3403 Distribution.xml:lane:transportMode:timeVaryin Determine the cost for this transport mode (refer to gEvent:costPerWeightUnit FDD on effective date and use plan_options.base date as the date for the time varying event). Of the Three costs, use the cost referred to by Parameters.Cost_to_determine_default_transport_co st. For a particular lane the default lane is the transport method with the lowest cost. Populate this with a 1 for the shipment method with the lowest cost, otherwise populate with 2. If more than one record has the same lowest cost then the first one is set to "1" and the remaining records are Distribution.xml:lane:transportMode:timeVaryin set to "2" gEvent:costPerVolumeUnit If ShippingMethods missing or ShippingMethods:TransitTime = <null> Distribution.xml:lane:transportMode:leadTime else ShippingMethods:TransitTime Distribution.xml:lane:transportMode:leadTime F3403 If ShippingMethods missing or ShippingMethods:leadTimeUom = <null> Distribution.xml:lane:transportMode:leadTimeUom else Distribution.xml:lane:transportMode:leadTimeU ShippingMethods:TimeUOMCode om If ShippingMethods missing or ShippingMethods:WeightCapacity = <null> Distribution.xml:lane:transportMode:weightCapacityP erVehicle (it says per vehicle, but in SCBM integ we used this as total capacity) else Distribution.xml:lane:transportMode:weightCap ShippingMethods:WeightCapacity acityPerVehicle If ShippingMethods missing or ShippingMethods:WeightUOMCode = <null> Distribution.xml:lane:transportMode:weightCapacity Uom else Distribution.xml:lane:transportMode:weightCap ShippingMethods:WeightUOMCode acityUom
If ShippingMethods missing or ShippingMethods:VolumeCapacity = <null> Distribution.xml:lane:transportMode:volumeCapacity PerVehicle (it says per vehicle, but in SCBM integ we used this as total capacity) else Distribution.xml:lane:transportMode:volumeCap ShippingMethods:VolumeCapacity acityPerVehicle If ShippingMethods missing or ShippingMethods:VolumeUOMCode = <null> Distribution.xml:lane:transportMode:volumeCapacity Uom else Distribution.xml:lane:transportMode:volumeCap ShippingMethods:VolumeUOMCode acityUom If ShippingMethods missing or ShippingMethods:costPerWeightUnit = <null> Distribution.xml:lane:transportMode:costPerWeightU nit else Distribution.xml:lane:transportMode:costPerWei ShippingMethods:costPerWeightUnit ghtUnit If ShippingMethods missing or ShippingMethods:costPerVolumeUnit = <null> Distribution.xml:lane:transportMode:costPerVolumeU nit else Distribution.xml:lane:transportMode:costPerVol ShippingMethods:costPerVolumeUnit umeUnit If ShippingMethods missing or ShippingMethods:Transportation Capacity Overutilization cost = <null> Parameter.Transport_Over_Utilization_Cost * (cost pointed by Parameters.Cost_to_determine_default_transport_co st)/ 100 else ShippingMethods:Transportation Capacity Overutilization cost
Parameter.CP_Company_Name <null> is required for suppliers <null> is required for customers <null> <null> <null> <null> <null> <null> <null> <null> <null>
<null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null>
omBranch ods:ToBranch
hippingMethods:Transport
hat is will need translation
Return to File Definitions E1 Field mmcu cmcu Comment
concat
All UDC values from 00|TM
trlt
Table Description VCP-ODS From Organization Code To Organization Code Source Instance Code Ship Method Default Flag In-transit Time Time UOM Code Weight Capacity Weight UOM Code Volume Capacity Volume UOM Cost Per Weight Unit Cost Per Volume Unit Transportation Capacity Over-utilization cost
Company Name From Location Code
To Location Code To Region Type To Country To Country Code To State To State Code To City To City Code To Postal Code From To Postal Code To To Zone From Region Type From Country From Country Code From State From State Code From City From City Code From Postal Code From From Postal Code To From Zone
Mainly from Customer.xml:CustomerSourcing aggregate to one record per customer/branc Join with user defined table "ShippingMethods" key = Customer.xml:customer:customerSourcing:branchCode=ShippingMethods:FromBranch Customer.xml:customer:customerCode=ShippingMethods:ToCustomer
Customer.xml:customer:customerCode=ShippingMethods:ToCustomer
NOTE: ShippingMethods will have original branch codes, that is will need translation
MSC_INTERORG_SHIP_METHODS - Inter Org This table stores the different shipment methods and their availability. Description Organization code for point of origin of the shipment. Organization code for destination of the shipment. Source instance code defined on the planning server. Method of shipment
Required only for Collaborative Planning. You should provide the party name with which the company is registered in Collaborative Planning. For a planning (APS) only environment, this should be left null. Ship from location in the shipment method relationship.
Ship to location in the shipment method relationship. To Region Type To Country To Country Code To State To State Code To City To City Code To Postal Code From To Postal Code To To Zone From Region Type From Country From Country Code From State From State Code From City From City Code From Postal Code From From Postal Code To From Zone
Mainly from Customer.xml:CustomerSourcing aggregate to one record per customer/branch Join with user defined table "ShippingMethods" key = Customer.xml:customer:customerSourcing:branchCode=ShippingMethods:FromBranch Customer.xml:customer:customerCode=ShippingMethods:ToCustomer
Customer.xml:customer:customerCode=ShippingMethods:ToCustomer
NOTE: ShippingMethods will have original branch codes, that is will need translation
Logic <null> <null> Parameter.Source_Instance "Sales" "1" ShippingMethods:TransitTime ShippingMethods:TimeUOMCode ShippingMethods:WeightCapacity ShippingMethods:WeightUOMCode ShippingMethods:VolumeCapacity ShippingMethods:VolumeUOMCode ShippingMethods:costPerWeightUnit ShippingMethods:costPerVolumeUnit ShippingMethods:Transportation Capacity Overutilization cost
Fields Referenced
E1 Table
Parameter.CP_Company_Name Customer.xml:customer:customerSourcing:branchCod Customer.xml:customer:customerSourcing:branc e hCode F40306 Customer.xml:customer:customerCode + Parameter.Field_Delimiter + Customer.xml:customer:name (max 30 chars) Customer.xml:customer:customerCode F03012 Customer.xml:customer:name F0101 <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null>
d per customer/branch
ethods:FromBranch
eed translation
MCU
AN8 ALPH
Table Description VCP-ODS Item Name Organization Code Vendor Name Source Instance Code Processing Lead Time Minimum Order Quantity
Fixed Lot Multiple Delivery Calendar Code Vendor Site Code Supplier Cap Over Utilization Cost
Company Name
Purchasing Unit Of Measure VMI Flag Minimum of Min-max quantity Maximum of Min-max quantity Maximum Order Quantity VMI Unit Of Measure VMI Replenishment Approval
Enable VMI Auto Replenish Flag Supplier Item Name Planner Code ASL Level Min Minmax Days Max Minmax Days Fixed Order Quantity Forecast Horizon Replenishment Method
Item Price
MSC_ITEM_SUPPLIERS This table stores the processing lead time, order modifier, and delivery calendar information for each item - supplier/site Description Inventory item name Organization code for legacy users Supplier name Source instance code defined on the planning server Processing lead time of supplier Minimum ordered quantity
Fixed lot multiplier Delivery calendar code Supplier site code Supplier capacity over-utilization cost Required only for Collaborative Planning. You should provide the party name with which the company is registered in Collaborative Planning. For a planning (APS) only environment, this should be left null.
Flag on ASL to determine whether item is VMI planned or not. Qty below which replenishment is generated in VMI planning. Qty above which exceptions are generated in VMI planning.
Flag to determine whether VMI replenishments need to be approved before they can be release. Valid values are: NONE, BUYER, SUPPLIER_OR_BUYER. Flag to determine whether to generate VMI replenishments of exceptions: Valid values are: N or null: Generate only exceptions, Y: Generate both exceptions and suggested replenishment Name of the item as the supplier refers to Planner code tied to the item. Whether the supplier is global or local. Valid values are: 1 - Global, 2 - Local. Min days of supply in VMI Max days of supply in VMI Fixed order quantity for VMI Forecast horizon (used in VMI) VMI planning method
Price of the Item.
calendar information for each item - supplier/site Logic Supplier.xml:supplier:supplierItem:itemCode Supplier.xml:supplier:suppierItem:branchCode Supplier.xml:supplierList:supplier:name Parameter.Source_Instance Supplier.xml:supplier:supplierItem:standardLeadTime (needs to be converted to days) <null>
Fields Referenced Decoded Item using Supplier.xml:supplier:supplierItem:itemCode Supplier.xml:supplier:suppierItem:branchCode Supplier.xml:supplierList:supplier:name
E1 Table F43090 F43090 F43090
Supplier.xml:supplier:supplierItem:standardLead Time F43090
Bug 9193304 if Supplier.xml:supplier:suppierItem:orderMultiple = 0 Then use <null> Else use Supplier.xml:supplier:suppierItem:orderMultiple Supplier.xml:supplier:suppierItem:orderMultiple F4102 <null> Supplier.xml:supplier:supplierCode Supplier.xml:supplier:supplierCode F43090 <null>
Base.xml:item:planningUom <null> <null> <null> <null> <null> <null>
F34A10
<null> <null> <null> "1" <null> <null> <null> <null> <null>
<null>
Return to File Definitions E1 Field ITM MCU ALPH Comment
ALTD
MULTt AN8
see comment
Sourcing Rule Name Effective Date Allocation Percent Source Type Planning Active Assignment Type
Organization Code Source Instance Code Disable Date
NOT USED
Rank
Description Ship Method Item Name Category Name Receipt Organization Code Receipt Org Instance Code Source Organization Code Source Org Instance Code Source Partner Name Source Partner Site Code Assignment Set Name
Company Name
Source Organization ID
Source Receipt Organization ID
Source Category Set ID
Source Category ID
Source Partner ID
Source Partner Site ID
Source Supplying Org ID
Source Sourcing Rule ID
Source Assignment Set ID
Source Receipt Organization Line ID
Source Organization Line ID
Source Assignment ID
From SupplierItem Records in Supplier.xml
MSC_ITEM_SOURCING - Purchasing This table stores sourcing information for an item used in Oracle Advanced Planning and Scheduling. Description
OT USED
Effective start date of the sourcing rule. Percentage of the supply allocated to a source. Valid values are 1-Transfer from, 2- Make at, 3- Buy from Planning Active Valid values are 1,2,3,4,5,6 Organization code where this resource and department exist. Source instance code defined on the planning server. Effective end date of the sourcing rule. A ranking or order for this sourcing rule (relative to another sourcing rules with common item-supplier combinations). Description of the sourcing rule. Method of shipment Inventory item name Item category name Organization receiving materials. Instance code defined on the planning server for the receiving organization. Organization shipping materials. Instance code defined on the planning server. Name of the supplier providing materials. Name of supplier's site. Assignment set used in supply planning. Required only for Collaborative Planning. You should provide the party name with which the company is registered in Collaborative Planning. For a planning (APS) only environment, this should be left null. Please provide the Organization ID for the Organization in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Receipt Organization ID for the Receipt Organization in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Inventory Item ID for the Inventory Item in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only.
Name of the sourcing rule you define.
Please provide the Category Set ID for the Category Set in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Category ID for the Category in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Partner ID for the Partner in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Partner Site ID for the Partner Site in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Organization ID for the Organization in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Sourcing Rule ID for the Sourcing Rule in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Assignment Set ID for the Assignment Set in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Receipt Organization Line ID for the Receipt Organization Line in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Organization Line ID for the Organization Line in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Assignment ID for the Assignment in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only.
From SupplierItem Records in Supplier.xml
ED
ced Planning and Scheduling. Logic Fields Referenced Supplier.xml:supplier:supplierItem:branchCode + Parameters.Field_Delimiter Supplier.xml:supplier:supplierItem:itemCode Supplier.xml:supplier:suppierItem:branchCode Supplier.xml:supplier:supplierItem:itemCode Parameters.Base_Effective_Date "100" "3" "1" "Item-Org" (6) Supplier.xml:supplier:supplierItem:branchCode Parameter.Source_Instance <null> Supplier.xml:supplier:suppierItem:branchCode
E1 Table
F43090 F43090
F43090
Parameters.txt:Supplier_Preference will be either Cost or LeadTime and indicate how to determine the ranking Sort SupplierItem by standardLeadTime or standardCost depending upon the field indicated by Parameters.txt:Supplier_Preference. Numerically rank the entries starting from 1 Supplier.xml:supplier:supplierItem:branchCode + Parameters.Field_Delimiter Supplier.xml:supplier:supplierItem:itemCode "Purchasing" Supplier.xml:supplier:supplierItem:itemCode <null> Supplier.xml:supplier:suppierItem:branchCode Parameter.Source_Instance <null> Parameter.Source_Instance Supplier.xml:supplier:supplierName Supplier.xml:supplier:supplierCode "ASSIGN-SET-" + parameter.Default_Assignment_Set
Supplier.xml:supplier:supplierItem:standardLead Time F43090 Supplier.xml:supplier:supplierItem:standardCost F43090
Supplier.xml:supplier:suppierItem:branchCode Supplier.xml:supplier:supplierItem:itemCode Supplier.xml:supplier:supplierItem:itemCode
F43090 F43090 F43090
Supplier.xml:supplier:suppierItem:branchCode
F43090
Supplier.xml:supplier:supplierName Supplier.xml:supplier:supplierCode
F43090 F43090
Supplier.xml:supplier:supplierCode
Supplier.xml:supplier:supplierCode
F43090
F43090
Supplier.xml:supplier:supplierItem:itemCode
Supplier.xml:supplier:supplierItem:itemCode
F43090
MCU ITM
MCU
ALTD ACST
MCU ITM ITM
MCU
ALPH AN8
AN8
MCU
ITM
Organization Code Source Instance Code Disable Date Rank
NOT USED
Description Ship Method Item Name Category Name Receipt Organization Code Receipt Org Instance Code Source Organization Code Source Org Instance Code Source Partner Name Source Partner Site Code Assignment Set Name
Company Name
Source Category ID
Source Partner ID
From Distribution.xml, ONLY LOAD THE SOURCING RECORD THAT EQUATES TO THE DEFAULT METHOD IN SHIPMENTMETHOD.dat
MSC_ITEM_SOURCING - Inter Org This table stores sourcing information for an item used in Oracle Advanced Planning and Scheduling. Description
OT USED
Name of the sourcing rule you define. Effective start date of the sourcing rule. Percentage of the supply allocated to a source. Valid values are 1-Transfer from, 2- Make at, 3- Buy from Planning Active Valid values are 1,2,3,4,5,6 Organization code where this resource and department exist. Source instance code defined on the planning server. Effective end date of the sourcing rule. A ranking or order for this sourcing rule (relative to another sourcing rules with common item-supplier combinations). Description of the sourcing rule. Method of shipment Inventory item name Item category name Organization receiving materials. Instance code defined on the planning server for the receiving organization. Organization shipping materials. Instance code defined on the planning server. Name of the supplier providing materials. Name of supplier's site. Assignment set used in supply planning. Required only for Collaborative Planning. You should provide the party name with which the company is registered in Collaborative Planning. For a planning (APS) only environment, this should be left null. Please provide the Organization ID for the Organization in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Receipt Organization ID for the Receipt Organization in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Inventory Item ID for the Inventory Item in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Category Set ID for the Category Set in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only.
Please provide the Category ID for the Category in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Partner ID for the Partner in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Partner Site ID for the Partner Site in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Organization ID for the Organization in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Sourcing Rule ID for the Sourcing Rule in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Assignment Set ID for the Assignment Set in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Receipt Organization Line ID for the Receipt Organization Line in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Organization Line ID for the Organization Line in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Assignment ID for the Assignment in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only.
From Distribution.xml, ONLY LOAD THE SOURCING RECORD THAT EQUATES TO THE DEFAULT METHOD IN SHIPMENTMETHOD.dat
ED
ced Planning and Scheduling. Logic Distribution.xml:lane:originBranchCode + Parameters.Field_Delimiter Distribution.xml:lane:destinationBranchCode + Parameters.Field_Delimiter Distribution.xml:lane:transportMode:itemTransportM ode:itemCode Parameter.Base_Effective_Date "100" "1" "1" Item-Org (6) Distribution.xml:lane:destinationBranchCode Parameter.Source_Instance <null> "1" (as we will only be loading one sourcing record in phase one) Distribution.xml:lane:originBranchCode + Parameters.Field_Delimiter Distribution.xml:lane:destinationBranchCode + Parameters.Field_Delimiter Distribution.xml:lane:transportMode:itemTransportM ode:itemCode Distribution.xml:lane:transportMode:transportModeC ode Distribution.xml:lane:transportMode:itemTranspor tMode:itemCode <null> Distribution.xml:lane:destinationBranchCode Parameter.Source_Instance Distribution.xml:lane:originBranchCode Parameter.Source_Instance <null> <null> "ASSIGN-SET-" + parameter.Default_Assignment_Set
Fields Referenced Distribution.xml:lane:originBranchCode Distribution.xml:lane:destinationBranchCode
E1 Table F3403 F3403
Distribution.xml:lane:transportMode:itemTransp ortMode:itemCode F3403
Distribution.xml:lane:destinationBranchCode
F3403
Distribution.xml:lane:originBranchCode Distribution.xml:lane:destinationBranchCode
F3403 F3403
Distribution.xml:lane:transportMode:itemTransp ortMode:itemCode F3403 Distribution.xml:lane:transportMode:transportM odeCode F3403 Distribution.xml:lane:transportMode:itemTransp ortMode:itemCode F3403 Distribution.xml:lane:originBranchCode Distribution.xml:lane:originBranchCode F3403 F3403
Distribution.xml:lane:originBranchCode
Distribution.xml:lane:originBranchCode
F3403
F3403
Distribution.xml:lane:transportMode:itemTransportM Distribution.xml:lane:transportMode:itemTransp ode:itemCode ortMode:itemCode F3403
<null>
<null>
<null>
<null>
<null>
<null>
<null>
<null>
<null>
<null>
T EQUATES
Return to File Definitions E1 Field mmcu cmcu itm Comment
cmcu
mmcu cmcu
itm concat itm mmcu mmcu All UDC values from 00|TM
mmcu
cmcu
itm
Organization Code Source Instance Code Disable Date Rank
NOT USED
Description Ship Method
Item Name Category Name Receipt Organization Code Receipt Org Instance Code Source Organization Code Source Org Instance Code Source Partner Name Source Partner Site Code Assignment Set Name
Company Name
Source Category ID
Source Partner ID
From Manufacturing.xml, create a record for each <producedItem> record
MSC_ITEM_SOURCING - Manufacturing This table stores sourcing information for an item used in Oracle Advanced Planning and Scheduling. Description
OT USED
Name of the sourcing rule you define. Effective start date of the sourcing rule. Percentage of the supply allocated to a source. Valid values are 1-Transfer from, 2- Make at, 3- Buy from Planning Active Valid values are 1,2,3,4,5,6 Organization code where this resource and department exist. Source instance code defined on the planning server. Effective end date of the sourcing rule. A ranking or order for this sourcing rule (relative to another sourcing rules with common item-supplier combinations). Description of the sourcing rule. Method of shipment Inventory item name Item category name Organization receiving materials. Instance code defined on the planning server for the receiving organization. Organization shipping materials. Instance code defined on the planning server. Name of the supplier providing materials. Name of supplier's site. Assignment set used in supply planning. Required only for Collaborative Planning. You should provide the party name with which the company is registered in Collaborative Planning. For a planning (APS) only environment, this should be left null. Please provide the Organization ID for the Organization in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Receipt Organization ID for the Receipt Organization in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Inventory Item ID for the Inventory Item in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only.
Please provide the Category Set ID for the Category Set in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Category ID for the Category in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Partner ID for the Partner in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Partner Site ID for the Partner Site in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Organization ID for the Organization in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Sourcing Rule ID for the Sourcing Rule in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Assignment Set ID for the Assignment Set in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Receipt Organization Line ID for the Receipt Organization Line in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Organization Line ID for the Organization Line in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Assignment ID for the Assignment in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only.
From Manufacturing.xml, create a record for each <producedItem> record
ED
ced Planning and Scheduling. Logic "Manu" + Parameters.Field_Delimiter Manufacturing.xml:operation:producedItem:produce dItemBom:branchCode + Parameters.Field_Delimiter Manufacturing.xml:operation:producedItem:itemCod e Parameter.Base_Effective_Date "100" "2" "1" Item-Org (6) Manufacturing.xml:operation:producedItem:prdoduc edItemBom:branchCode Parameter.Source_Instance <null> "1" (as we will only be loading one sourcing record in phase one)
Fields Referenced E1 Table Manufacturing.xml:operation:producedItem:pro ducedItemBom:branchCode F3003 Manufacturing.xml:operation:producedItem:ite mCode
F3003
Manufacturing.xml:operation:producedItem:pro ducedItemBom:branchCode F3003
Manufacturing.xml:operation:producedItem:pro "Manu" + Parameters.Field_Delimiter ducedItemBom:branchCode F3003 Manufacturing.xml:operation:producedItem:produce dItemBom:branchCode + Parameters.Field_Delimiter Manufacturing.xml:operation:producedItem:itemCod Manufacturing.xml:operation:producedItem:ite e mCode F3003 <null> Manufacturing.xml:operation:producedItem:itemCod e <null> Manufacturing.xml:operation:producedItem:prdoduc edItemBom:branchCode Parameter.Source_Instance Manufacturing.xml:operation:producedItem:prdoduc edItemBom:branchCode Parameter.Source_Instance <null> <null> "ASSIGN-SET-" + parameter.Default_Assignment_Set Manufacturing.xml:operation:producedItem:ite mCode
F3003
Manufacturing.xml:operation:producedItem:pro ducedItemBom:branchCode F3003 Manufacturing.xml:operation:producedItem:pro ducedItemBom:branchCode F3003
Parameter.CP_Company_Name Manufacturing.xml:operation:producedItem:prdoduc Manufacturing.xml:operation:producedItem:pro edItemBom:branchCode ducedItemBom:branchCode F3003 Manufacturing.xml:operation:producedItem:prdoduc Manufacturing.xml:operation:producedItem:pro edItemBom:branchCode ducedItemBom:branchCode F3003 Manufacturing.xml:operation:producedItem:itemCod Manufacturing.xml:operation:producedItem:pro e ducedItemBom:branchCode F3003
<null>
<null>
<null>
<null>
<null>
<null>
<null>
<null>
<null>
<null>
m> record
Return to File Definitions E1 Field MMCU Comment
KIT
MMCU
MMCU
KIT
KIT
MMCU
MMCU
MMCU
MMCU
MMCU
Sourcing Rule Name Effective Date Allocation Percent
Source Type Planning Active Assignment Type Organization Code Source Instance Code Disable Date
NOT U
Rank
Description Ship Method Item Name
Category Name
Receipt Organization Code Receipt Org Instance Code Source Organization Code Source Org Instance Code Source Partner Name Source Partner Site Code Assignment Set Name
Company Name
Source Category ID
Source Partner ID
MSC_ITEM_SOURCING - Customers This table stores sourcing information for an item used in Oracle Advanced Planning and Scheduling. Description
Name of the sourcing rule you define. Effective start date of the sourcing rule. Percentage of the supply allocated to a source.
Valid values are 1-Transfer from, 2- Make at, 3- Buy from Planning Active Valid values are 1,2,3,4,5,6
Organization code where this resource and department exist. Source instance code defined on the planning server. Effective end date of the sourcing rule.
NOT USED
A ranking or order for this sourcing rule (relative to another sourcing rules with common item-supplier combinations).
Description of the sourcing rule. Method of shipment Inventory item name
Item category name
Organization receiving materials. Instance code defined on the planning server for the receiving organization. Organization shipping materials. Instance code defined on the planning server. Name of the supplier providing materials. Name of supplier's site. Assignment set used in supply planning. Required only for Collaborative Planning. You should provide the party name with which the company is registered in Collaborative Planning. For a planning (APS) only environment, this should be left null.
Please provide the Organization ID for the Organization in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Receipt Organization ID for the Receipt Organization in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Inventory Item ID for the Inventory Item in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Category Set ID for the Category Set in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Category ID for the Category in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Partner ID for the Partner in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Partner Site ID for the Partner Site in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Organization ID for the Organization in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Sourcing Rule ID for the Sourcing Rule in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Assignment Set ID for the Assignment Set in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Receipt Organization Line ID for the Receipt Organization Line in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Organization Line ID for the Organization Line in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Assignment ID for the Assignment in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only.
ced Planning and Scheduling. Logic Customer.xml:customer:customerCode + Parameters.Field_Delimiter Customer.xml:customer:customerSourcing:branchCod e + Parameters.Field_Delimiter Customer.xml:customer:customerSourcing:itemCode Customer.xml:customer:customerSourcing:effectived ate "100" Determined if a routing.dat exists for this item name exists in this organisation.(key is Assemly name and organisation in routing.dat) "1" if a routing does not exist at this location, "2" if a routing does exist at this location. "1" Item-Org (6) Customer.xml:customer:customerSourcing:branchCod e Parameter.Source_Instance Customer.xml:customer:customerSourcing:effectived ate (of previous record) - 1 Customer.xml:customer:customerSourcing:preference (E1 allows 0, if EBS does not ..add 1) Refer to Complex Modelling section in the FDD Customer.xml:customer:customerCode + Parameters.Field_Delimiter Customer.xml:customer:customerSourcing:branchCod e + Parameters.Field_Delimiter Customer.xml:customer:customerSourcing:itemCode "Sales" Customer.xml:customer:customerSourcing:itemCode retrieve from items.dat for Customer.xml:customer:customerSourcing:itemCode Customer.xml:customer:customerCode + Parameter.Field_Delimiter + Customer.xml:customer:name Parameter.Source_Instance Customer.xml:customer:customerSourcing:branchCod e Parameter.Source_Instance <null> <null> "ASSIGN-SET-" + parameter.Default_Assignment_Set
Fields Referenced
E1 Table
T USED
Customer.xml:customer:customerSourcing:branchCod e
Customer.xml:customer:customerCode
Customer.xml:customer:customerSourcing:itemCode
<null>
<null>
<null>
<null>
<null>
<null>
<null>
<null>
<null>
<null>
Table Description VCP-ODS Item Name Organization Code
Supplier Name Firm Planned Type Supplier Site Code Purchase Line Number Order Number Source Instance Code Revision Unit Number New Order Quantity Project Number Task Number Planning Group
Delivery Price Qty Scrapped From Organization Code Deleted Flag
Company Name End Order Number End Order Release Number End Order Line Number Order Release Number Comments Ship To Party Name Ship To Site Code Need By Date Promise Date Old Schedule Date New Schedule Date Original Need By Date New Order Placement Date Subinventory Code Postprocessing Lead Time Original Quantity Acceptance Required Flag
Source Org ID
Source Vendor ID
Source Vendor Site ID
Source Project ID
Source Task ID
Source From Organization ID
Source supply ID
Source Disposition ID Order Type
Supplied by PurchaseOrder.xml for Orders with ship > current date
MSC_Supplies MSC_Supplies lists all the supplies for this plan - This spreadsheet contains Purchase Orders Description Inventory item name Organization
Supplier code Flag indicating whether the order is firm. Supplier location name Purchase order line number Order number (purchase order number). Source instance code defined on the planning server. Inventory item revision code Unit number Supply quantity Project name Task name Project planning group
Supply unit price for purchasing supply Current job scrapped units From organization code Valid values are: 1 - Yes, 2 - No. If 1, then this row is deleted. Required only for Collaborative Planning. You should provide the party name with which the company is registered in Collaborative Planning. For a planning (APS) only environment, this should be left null. Pegged transaction order number. Pegged transaction order release number. Pegged transaction order line number. Release number in the PO posted to the system. Comments for entries posted to the system.
Need by date. Promise date. Old Schedule Date. New Schedule Date. Need By Date on PO shipment when PO shipment was originally created. New Order Placement Date. Subinventory Code. Item's post processing lead time. Quantity on PO shipment when PO shipment was originally created. Acceptance Required Flag for PO.
Please provide the Organization ID for the Organization in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Inventory Item ID for the Item in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Vendor ID for the Vendor in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Vendor Site ID for the Vendor Site in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Project ID for the Project in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Task ID for the Task in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the From Organization Id for the Sourcing Organization (mentioned in the From Organization Code) in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide a unique ID to identify this supply in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only Please provide the Disposition ID for the Supply in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide a valid order type. Valid values are : 2- Purchase Req, 87 - external repair requisition, 73 - internal repair order.
Supplied by PurchaseOrder.xml for Orders with ship > current date
ins Purchase Orders Logic PurchaseOrders.xml:purchaseOrder:purchaseOr derDetail:itemCode PurchaseOrders.xml:purchaseOrder:purchaseOrder:d estinationBranchCode Supplier.xml:supplierList:supplier:name pointed to by PurchaseOrders.xml:purchaseOrder:purchaseOrder:su PurchaseOrders.xml:purchaseOrder:purchaseOrderDe tail:fix (yes ->1 ; no->2) PurchaseOrders.xml:purchaseOrder:purchaseOrder:su pplierCode PurchaseOrders.xml:purchaseOrder:purchaseOrderDe tail:lineItem PurchaseOrders.xml:purchaseOrder:purchaseOrder:p urchaseOrderCode Parameter.Source_Instance <null> <null> PurchaseOrders.xml:purchaseOrder:purchaseOrderDe tail:quantity <null> <null> <null>
Fields Referenced PurchaseOrders.xml:purchaseOrder:purchaseOr derDetail:itemCode PurchaseOrders.xml:purchaseOrder:purchaseOr der:destinationBranchCode Supplier.xml:supplierList:supplier:name PurchaseOrders.xml:purchaseOrder:purchaseOr der:supplierCode PurchaseOrders.xml:purchaseOrder:purchaseOr derDetail:fix PurchaseOrders.xml:purchaseOrder:purchaseOr der:supplierCode PurchaseOrders.xml:purchaseOrder:purchaseOr derDetail:lineItem PurchaseOrders.xml:purchaseOrder:purchaseOr der:purchaseOrderCode
E1 Table F4311 F4311 F43090 F4311 F4311 F4311 F4311 F4311
PurchaseOrders.xml:purchaseOrder:purchaseOr derDetail:quantity F4311
PurchaseOrders.xml:purchaseOrder:purchaseOrderDe PurchaseOrders.xml:purchaseOrder:purchaseOr tail:unitCost derDetail:unitCost F4311 <null> <null> "2"
Parameter.CP_Company_Name <null> <null> <null> <null> <null> <null> <null> PurchaseOrders.xml:purchaseOrder:purchaseOrderDe tail:arriveDate PurchaseOrders.xml:purchaseOrder:purchaseOrderDe tail:arriveDate <null> <null> <null> <null> <null> <null> <null> <null>
PurchaseOrders.xml:purchaseOrder:purchaseOr derDetail:arriveDate F4311 PurchaseOrders.xml:purchaseOrder:purchaseOr derDetail:arriveDate F4311
PurchaseOrders.xml:purchaseOrder:purchaseOrder:d PurchaseOrders.xml:purchaseOrder:purchaseOr estinationBranchCode der:destinationBranchCode F4311 PurchaseOrders.xml:purchaseOrder:purchaseOrderDe PurchaseOrders.xml:purchaseOrder:purchaseOr tail:itemCode derDetail:itemCode F4311 PurchaseOrders.xml:purchaseOrder:purchaseOrder:su PurchaseOrders.xml:purchaseOrder:purchaseOr pplierCode der:supplierCode F4311 PurchaseOrders.xml:purchaseOrder:purchaseOrder:su PurchaseOrders.xml:purchaseOrder:purchaseOr pplierCode der:supplierCode F4311
<null>
<null>
<null>
<null>
<null> 1
Return to File Definitions E1 Field ITM MCU ALPH AN8 assignment AN8 LNID concatenation concatenation = F4311.DOCO|F4311.KCOO|F4311.DCTO|F4311.SFXO assignment = if F4311.UNCD = 'Y' or F4301.HOLD is not blank, then fix = "Yes" else fix = 'No' Comment
UOPN
calculation
calculation = if converting F4311.UOPN to planning unit of measure changed the quantity, then unitCost = F4311.AEXP / F4311.UOPN else unitCost = F4311.AMC3
PDDJ PDDJ
format = yyyy-mm-ddT00:00:00 format = yyyy-mm-ddT00:00:00
MCU
ITM
AN8
AN8
Table Description VCP-ODS Item Name Organization Code New Schedule Date New Order Quantity Firm Planned Type Supplier Name Purchase Line Number Order Number Supplier Site Code Source Instance Code Revision Unit Number New Dock Date Project Number Task Number
Planning Group Delivery Price Qty Scrapped From Organization Code Deleted Flag
Company Name Source Org Instance Code New Order Placement Date
Source Org ID
Source Vendor ID
Source Project ID
Source Task ID
Source supply ID
Source Disposition ID Order Type Shipment Method
MSC_Supplies MSC_Supplies lists all the supplies for this plan - This spreadsheet contains Trransfer Orders Description Inventory item name Organization End date of the supply (completion date of the first unit). Supply quantity Flag indicating whether the order is firm. Supplier code Requisition line number Requisition number Supplier location name Source instance code defined on the planning server. Inventory item revision code Unit number p Project name Task name Project planning group. If more than one project belongs to the same planning group, this column is used to net the demand/supply across projects. Supply unit price for purchasing supply. Current job scrapped units. From organization code Valid values are: 1 - Yes, 2 - No. If 1, then this row is deleted. Required only for Collaborative Planning. You should provide the party name with which the company is registered in Collaborative Planning. For a planning (APS) only environment, this should be left null. Source instance code for source organization. New Order Placement Date. Please provide the Organization ID for the Organization in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Inventory Item ID for the Item in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Vendor ID for the Vendor in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Vendor Site ID for the Vendor Site in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Project ID for the Project in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only.
Please provide the Task ID for the Task in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the From Organization Id for the Sourcing Organization (mentioned in the From Organization Code) in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide a unique ID to identify this supply in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only Please provide the Disposition ID for the Supply in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide a valid order type. Valid values are : 1- Purchase Order, 74 - external repair order
Supplied by TransferOrder.xml for Orders with ship > current date and quantity > 0
ins Trransfer Orders Logic TransferOrders.xml:transferOrder:transferOrderD etail:itemCode TransferOrders.xml:transferOrder:destinationBranchC ode TransferOrders.xml:transferOrder:transferOrderDetail :arriveDate TransferOrders.xml:transferOrder:transferOrderDetail :quantity TransferOrders.xml:transferOrder:transferOrderDetail :fix (yes ->1 ; no->2) <null> TransferOrders.xml:transferOrder:transferOrderDetail :lineItem
Fields Referenced TransferOrders.xml:transferOrder:transferOrder Detail:itemCode TransferOrders.xml:transferOrder:destinationBra nchCode TransferOrders.xml:transferOrder:transferOrder Detail:arriveDate TransferOrders.xml:transferOrder:transferOrder Detail:quantity TransferOrders.xml:transferOrder:transferOrder Detail:fix
E1 Table F4311 F4311 F4311 F4311 F4311
TransferOrders.xml:transferOrder:transferOrder Detail:lineItem F4311 TransferOrders.xml:transferOrder:transferOrder TransferOrders.xml:transferOrder:transferOrderCode Code F4311 <null> Parameter.Source_Instance <null> <null> TransferOrders.xml:transferOrder:transferOrderDetail TransferOrders.xml:transferOrder:transferOrder :arriveDate Detail:arriveDate F4311 <null> <null>
<null> <null> <null> TransferOrders.xml:transferOrder:originBranchCode "N" TransferOrders.xml:transferOrder:originBranchC ode F0006
Parameter.CP_Company_Name Parameter.Source_Instance TransferOrders.xml:transferOrder:transferOrderDetail TransferOrders.xml:transferOrder:transferOrder :arriveDate Detail:arriveDate F4311 TransferOrders.xml:transferOrder:destinationBranchC TransferOrders.xml:transferOrder:destinationBra ode nchCode F4311 TransferOrders.xml:transferOrder:transferOrderDetail TransferOrders.xml:transferOrder:transferOrder :itemCode Detail:itemCode F4311
<null>
<null>
<null>
<null>
<null> TransferOrders.xml:transferOrder:transferOrderCode + TransferOrders.xml:transferOrder:teansferOrderDetail :lineItem
TransferOrders.xml:transferOrder:transferOrder Code F4311 TransferOrders.xml:transferOrder:transferOrder Detail:lineItem F4311
<null> "2" <null>
Return to File Definitions E1 Field ITM MCU PDDJ UOPN assignment format = yyyy-mm-ddT00:00:00 converted to planning unit of measure assignment = if F4311.UNCD = 'Y' or F4301.HOLD is not blank, then fix = "Yes" else fix = 'No' Comment
LNID concatenation concatenation = F4311.DOCO|F4311.KCOO|F4311.DCTO|F4311.SFXO
PDDJ
format = yyyy-mm-ddT00:00:00
MCU
MCU is retrieved from F0006 where F0006.AN8 = F4311.AN8
PDDJ
MCU
ITM
concatenation LNID
concatenation = F4311.DOCO|F4311.KCOO|F4311.DCTO|F4311.SFXO
Table Description VCP-ODS Item Name Organization Code New Schedule Date Order Type Firm Planned Type Source Instance Code Revision Unit Number
Supplier Name New Order Quantity Purchase Line Number Source Sr. Instance Code New Dock Date Project Number Task Number Planning Group Order Number
Delivery Price Qty Scrapped From Organization Code Deleted Flag
Company Name Supplier Site Code Subinventory Code
Source Org ID
Source Vendor ID
Source Project ID
Source Task ID
Source supply ID
Source Disposition ID
PurchaseOrder.xml where shipDate is <= Option.Base Date
MSC_Supplies MSC_Supplies lists all the supplies for this plan - This spreadsheet contains In-Transit Supplies for Purchase Orders Description Inventory item name Organization End date of the supply (completion date of first unit). Type of order: planned order, purchase order, etc. 11 - In-transit shipment, 12 - Intransit receipt Flag indicating that the order is firm. Source instance code defined on the planning server. Inventory item revision code Unit number
Supplier code Supply quantity. Shipment line number Source application instance code Suggested dock date. Project name Task name Project planning group Order number (purchase order number)
Supply unit price for purchasing supply Current job scrapped units From organization code Valid values are: 1 - Yes, 2 - No. If 1, then this row is deleted. Required only for Collaborative Planning. You should provide the party name with which the company is registered in Collaborative Planning. For a planning (APS) only environment, this should be left null. Supplier Site Code Subinventory Code Please provide the Organization ID for the Organization in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Inventory Item ID for the Inventory Item in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Vendor ID for the Vendor in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only.
Please provide the Vendor Site ID for the Vendor Site in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Project ID for the Project in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Task ID for the Task in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the From Organization Id for the Sourcing Organization (mentioned in the From Organization Code) in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide a unique ID to identify this supply in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only Please provide the Disposition ID for the Supply in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only.
PurchaseOrder.xml where shipDate is <= Option.Base Date
ins In-Transit Supplies for Purchase Orders Logic PurchaseOrders.xml:purchaseOrder:purchaseOrderDe tail:itemCode PurchaseOrders.xml:purchaseOrder:destinationBranc hCode PurchaseOrders.xml:purchaseOrder:purchaseOrderDe tail:arriveDate "11" "1" Parameter.Source_Instance <null> <null>
Fields Referenced PurchaseOrders.xml:purchaseOrder:purchaseOr derDetail:itemCode PurchaseOrders.xml:purchaseOrder:purchaseOr der:destinationBranchCode PurchaseOrders.xml:purchaseOrder:purchaseOr derDetail:arriveDate "11" "1" Parameter.Source_Instance <null> <null>
E1 Table F4311 F4311 F4311
Supplier.xml:supplierList:supplier:name pointed to by PurchaseOrders.xml:purchaseOrder:purchaseOrderDe tail:supplierCode Purchasing.xml:purchaseOrder:purchaseOrderDetail:q uantity Purchasing.xml:purchaseOrder:purchaseOrderDetail:li neItem Parameter.Source_Instance Purchasing.xml:purchaseOrder:purchaseOrderDetail:a rriveDate <null> <null> <null> Purchasing.xml:purchaseOrder:purchaseOrder:purcha seOrderCode
Supplier.xml:supplierList:supplier:name PurchaseOrders.xml:purchaseOrder:purchaseOr der:supplierCode PurchaseOrders.xml:purchaseOrder:purchaseOr derDetail:quantity PurchaseOrders.xml:purchaseOrder:purchaseOr derDetail:lineItem
F43090 F4311 F4311 F4311
PurchaseOrders.xml:purchaseOrder:purchaseOr derDetail:arriveDate F4311
PurchaseOrders.xml:purchaseOrder:purchaseOr der:purchaseOrderCode F4311
Purchasing.xml:purchaseOrder:purchaseOrderDetail:u PurchaseOrders.xml:purchaseOrder:purchaseOr nitCost derDetail:unitCost F4311 <null> <null> "2"
use whatever Company Name was used on Supplier PurchaseOrders.xml:purchaseOrder:supplierCode <null> PurchaseOrders.xml:purchaseOrder:purchaseOr der:supplierCode F4311
PurchaseOrders.xml:purchaseOrder:purchaseOrderDe PurchaseOrders.xml:purchaseOrder:purchaseOr tail:destinationBranchCode der:destinationBranchCode F4311 PurchaseOrders.xml:purchaseOrder:purchaseOrderDe PurchaseOrders.xml:purchaseOrder:purchaseOr tail:itemCode derDetail:itemCode F4311 PurchaseOrders.xml:purchaseOrder:purchaseOrderDe PurchaseOrders.xml:purchaseOrder:purchaseOr tail:supplierCode der:supplierCode F4311
<null>
<null>
<null>
<null>
<null>
<null>
Return to File Definitions E1 Field ITM MCU PDDJ format = yyyy-mm-ddT00:00:00 Comment
ALPH AN8 UOPN LNID converted to planning unit of measure
PDDJ
concatenation
concatenation = F4311.DOCO|F4311.KCOO|F4311.DCTO|F4311.SFXO calculation = if converting F4311.UOPN to planning unit of measure changed the quantity, then unitCost = F4311.AEXP / F4311.UOPN else unitCost = F4311.AMC3
calculation
AN8
MCU
ITM
AN8
Table Description VCP-ODS Item Name Organization Code New Schedule Date Order Type Firm Planned Type Source Instance Code Revision Unit Number Supplier Name New Order Quantity Purchase Line Number Source Sr. Instance Code New Dock Date Project Number Task Number Planning Group Order Number Delivery Price Qty Scrapped From Organization Code Deleted Flag
Company Name Supplier Site Code Subinventory Code
Source Org ID
Source Vendor ID
Source Project ID
Source Task ID
Source supply ID
Source Disposition ID shipment method
TransferOrder.xml where shipDate is <= Option.Base Date
MSC_Supplies MSC_Supplies lists all the supplies for this plan - This spreadsheet contains In-Transit Supplies for Transfer Orders Description Inventory item name Organization End date of the supply (completion date of first unit). Type of order: planned order, purchase order, etc. 11 - In-transit shipment, 12 - Intransit receipt Flag indicating that the order is firm. Source instance code defined on the planning server. Inventory item revision code Unit number Supplier code Supply quantity. Shipment line number Source application instance code Suggested dock date. Project name Task name Project planning group Order number (purchase order number) Supply unit price for purchasing supply Current job scrapped units From organization code Valid values are: 1 - Yes, 2 - No. If 1, then this row is deleted. Required only for Collaborative Planning. You should provide the party name with which the company is registered in Collaborative Planning. For a planning (APS) only environment, this should be left null. Supplier Site Code Subinventory Code Please provide the Organization ID for the Organization in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Inventory Item ID for the Inventory Item in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Vendor ID for the Vendor in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Vendor Site ID for the Vendor Site in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Project ID for the Project in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only.
Please provide the Task ID for the Task in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the From Organization Id for the Sourcing Organization (mentioned in the From Organization Code) in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide a unique ID to identify this supply in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only Please provide the Disposition ID for the Supply in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only.
TransferOrder.xml where shipDate is <= Option.Base Date
ins In-Transit Supplies for Transfer Orders Logic TransferOrders.xml:transferOrder:transferOrderDetail :itemCode TransferOrders.xml:transferOrder:destinationBranchC ode TransferOrders.xml:transferOrder:transferOrderDetail :arriveDate
Fields Referenced TransferOrders.xml:transferOrder:transferOrder Detail:itemCode TransferOrders.xml:transferOrder:destinationBra nchCode TransferOrders.xml:transferOrder:transferOrder Detail:arriveDate
E1 Table F4311 F4311 F4311
"11" "1" Parameter.Source_Instance <null> <null> <null> TransferOrders.xml:transferOrder:transferOrderDetail TransferOrders.xml:transferOrder:transferOrder :quantity Detail:quantity F4311 TransferOrders.xml:transferOrder:transferOrderDetail :lineItem TransferOrders.xml:transferOrder:transferOrder Parameter.Source_Instance Detail:lineItem F4311 TransferOrders.xml:transferOrder:transferOrderDetail TransferOrders.xml:transferOrder:transferOrder :arriveDate Detail:arriveDate F4311 <null> <null> <null> TransferOrders.xml:transferOrder:transferOrderCode TransferOrders.xml:transferOrder:transferOrder [entire field] Code F4311 <null> <null> TransferOrders.xml:transferOrder:originBranchC TransferOrders.xml:transferOrder:originBranchCode ode F0006 "2" Whatever was used on Company_Name for dest branch <null> <null> TransferOrders.xml:transferOrder:destinationBranchC TransferOrders.xml:transferOrder:destinationBra ode nchCode F4311 TransferOrders.xml:transferOrder:transferOrderDetail TransferOrders.xml:transferOrder:transferOrder :itemCode Detail:itemCode F4311
<null>
<null>
<null>
<null>
<null>
<null>
<null> <null>
Return to File Definitions E1 Field ITM MCU PDDJ format = yyyy-mm-ddT00:00:00 Comment
UOPN
LNID PDDJ format = yyyy-mm-ddT00:00:00
concatenation
MCU
MCU
ITM
Table Description VCP-ODS Item Name Schedule Date Organization Code Using Assembly Item Name
Using Assembly Demand Date Using Requirement Quantity Demand Type Source Instance Code
Assembly Demand Comp Date Demand Schedule Name Project Number Task Number
Demand Class
Demand Lateness Cost
Demand Satisfied Date Dmd Split Flag Confidence Percentage Bucket Type Bill Code
Forecast Designator Customer Name Forecast MAD Probability Deleted Flag
Company Name
Comments Schedule Line Number Order Priority Schedule Line Num
Source org ID
Source Using Assembly Item ID
Source Sales Order Line ID
Source Project ID
Source Task ID
Source Customer Site ID
Source Customer ID
Source Bill ID
MSC_Demands This table stores all the demands taken into account for planning. In this case Forecasts Description Item for which MDS demand is given. Inventory item name. Schedule Date. Organization End assembly name
Forecast date. Must be a valid work day. Original forecast quantity. Demand Type. Instance code defined on the planning server. Rate end date (should be a valid work day). Use this if entity is for a bucket. Then from forecast date to rate end date forecast quantity is assumed for each date. Demand Schedule Name. Project identifier. This should be predefined in MSC_PROJECTS. Task identifier. This should be predefined in MSC_PROJECT_TASKS.
Demand class.
Required for SCO
Required for SCO Required for SCO Confidence percent. This should be less than or equal to 100. Valid values are: 1 - Daily, 2 - Weekly, 3 - Period Wise Forecast bill to site code
Name or identifier of a forecast Customer Name Mean absolute deviation of the forecast compared to actual values. A value between 0 and 1, which weights the probability of this forecast. Valid values are: 1 - Yes, 2 - No. If 1, then this row is deleted. Required only for Collaborative Planning. You should provide the party name with which the company is registered in CP. For a planning (APS) only environment, this should be left null.
Comments for entries posted to the system. Schedule Line Number. Priority of the Order. Schedule Line Number. Please provide the Organization ID for the Organization in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Inventory Item ID for the Item in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Assembly Item ID for the Assembly Item in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Sales Order Line ID for the Sales Order Line in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Project ID for the Project in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Task ID for the Task in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Customer Site ID for the Customer Site in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Customer ID for the Customer in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Bill ID for the Bill in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only.
Primarily from TimeSeries.xml
is case Forecasts Logic TimeSeries.xml:timeSeriesDetail:itemCode TimeSeries.xml:timeSeriesDetail:bucket:startdate TimeSeries.xml:timeSeriesDetail:branchCode TimeSeries.xml:timeSeriesDetail:itemCode TimeSeries.xml:timeSeriesDetail:bucket:startDate (if not a work day, make it the next work day) Check Calendar Exception, if no record check Calendar, if a non work day, add 1 day and repeat (14 days lookahead is fine) TimeSeries.xml:timeSeriesDetail:bucket:quantity <null> <null>
Fields Referenced TimeSeries.xml:timeSeriesDetail:itemCode
E1 Table F3460
TimeSeries.xml:timeSeriesDetail:bucket:startdate TimeSeries.xml:timeSeriesDetail:branchCode F3460 TimeSeries.xml:timeSeriesDetail:itemCode F3460
TimeSeries.xml:timeSeriesDetail:bucket:startdate TimeSeries.xml:timeSeriesDetail:bucket:quantity
<null> LAST 10 chars of (TimeSeries.xml:timeSeries:timeSeriesCode) <null> <null> Get Default Demand Class from Customer.xml using customer in TimeSeries.xml:timeSeriesDetail:customerOrGroup if this is not found use Parameter.Forecast_Demand_Lateness_Cost_%/100 * base.xml:itemBranch:itemPrice (join by item/branch) TimeSeries.xml:timeSeriesDetail:bucket:startDate or End date. Determined by parameter.Forecast_Demand_Satisfied_Date_Field <null> Parameter.Forecast_Confidence_Percentage(100) if TimeSeries.xml:timeSeries:periodSize="Daily" set to 1, if "Weekly" set to 2 otherwise 3 <null> If customerOrGroup is not null then look up the translation table for customerOrGroup with a key of "FORECAST_DESIGNATOR" if not found use Parameter.Default_Forecast_Designator If customerOrGroup is null then look up the translation table for branchCode with a key of "FORECAST_DESIGNATOR" if not found use Parameter.Default_Forecast_Designator <null> Parameters.Forecast_MAD (<null>) Parameters.Forecast_Probability (1) "2"
TimeSeries.xml:timeSeries:timeSeriesCode
Default Demand Class from Customer.xm F0101 TimeSeries.xml:timeSeriesDetail:customerOrGro up F3460
base.xml:itemBranch:itemPrice TimeSeries.xml:timeSeriesDetail:bucket:startdate TimeSeries.xml:timeSeriesDetail:bucket:enddate
F4106
TimeSeries.xml:timeSeries:periodSize
TimeSeries.xml:timeSeriesDetail:customerOrGro up F3460
<null>
TimeSeries.xml:timeSeries:timeSeriesCode TimeSeries.xml:timeSeriesDetail:customerOrGroup <null> <null>
TimeSeries.xml:timeSeries:timeSeriesCode TimeSeries.xml:timeSeriesDetail:customerOrGro up F3460
<null>
<null>
<null>
<null>
<null>
<null>
<null>
<null>
<null>
Return to File Definitions E1 Field ITM Comment
MCU ITM
concatenation AN8
UPRC
AN8
AN8
Table Description VCP-ODS Designator Organization Code Source Instance Code Description Disable Date Demand Class Consume Forecast Update Type Forward Update Time Fence Backward Update Time Fence Outlier Update Percentage Customer Name Ship To Site Code Bill To Site Code Bucket Type Forecast Set Probability
Company Name MPS_Relief
MSC_DESIGNATORS This table stores MPS and MDS schedule names defined at source applications and planning server. MPS_RELIEF indicates whether or not t Description Forecast name/designator Organization Instance code defined on the planning server. Description Disable date for the forecast designator Name or identifier of a demand class. Whether or not forecast consumption is required. Valid values are: 1 - Yes, 2 - No. Forecast update type code. Valid values are: 2 - Ship To, 3 - Bill To, 4 - Ct., 6 - Item. Forward consumption days Backward consumption days Forecast outlier update percentage. This should be less than 100. Customer Name Forecast ship code Forecast bill code Valid values are: 1 - Days, 2 - Weeks, 3 - Periods. Forecast set name. Value is derived in accordance with the forecast versioning architecture (of DP/CP integration). Required only for Collaborative Planning. You should provide the party name with which the company is registered in CP. For a planning (APS) only environment, this should be left null
cations and planning server. MPS_RELIEF indicates whether or not the Planning Manager should consume this master demand or master production Logic Fields Referenced E1 Table Directly from "Forecast Designators" Directly from "Forecast Designators" Directly from "Forecast Designators" Directly from "Forecast Designators" Directly from "Forecast Designators" Directly from "Forecast Designators" Directly from "Forecast Designators" Directly from "Forecast Designators" Directly from "Forecast Designators" Directly from "Forecast Designators" Directly from "Forecast Designators" Directly from "Forecast Designators" Directly from "Forecast Designators" Directly from "Forecast Designators" Directly from "Forecast Designators" Directly from "Forecast Designators" Directly from "Forecast Designators"
mand or master production E1 Field
Table Description VCP-ODS Item Name Organization Code Primary UOM Quantity Completed Quantity Requirement Date Sales Order Number Line Num Source Instance Code Reservation Type Reservation Quantity Subinventory
Demand Class Sales Representative Contact Ordered Item Name Customer Name
Ship To Site Code
Bill To Site Code Planning Group Demand Priority Request Date Selling Price Demand Visible Forecast Visible CTO Flag Original System Reference Original System Line Reference Deleted Flag
Company Name Comments Order Release Number End Order Number End Order Release Number
End Order Line Number
End Order Type New Order Placement Date Original Item Name Demand Source Type New Order Placement Date Order Date Type Code Schedule Arrival Date
Latest Acceptable Date Shipping Method Code Promise Date Org Firm Flag Ship Set name Arrival Set Name
Source Demand Source Header ID
Source Original Item ID
Source Demand ID
Source Customer ID
Source Bill To Site Use ID
Source Ship to site Use ID
Source Demand Source Line Project Number Task Number
Sales Orders from the SalesOrder.xml file
MSC_SALES_ORDERS This table stores sales order demand and reservations from source application instances. (in this case from Sales Orders) Description MDS item name. Organization. Quantity ordered. Shipped quantity. Need-by date. Order number.
Instance code defined on the planning server. Valid values are: 1 - Soft reservation, 2 - Hard reservation, 3 - Supply order reservation. Reservation quantity. Code for a sub-inventory.
Name or identifier of a demand class.
Valid values are: Y - Yes, N - No. Valid values are: Y - Yes, N - No. Configure to order. Default 2 for legacy/exchange. Valid values are: 1 - Yes, 2 - No. The reference number of a sales order if it is loaded from another source. The reference number of a line on a sales order if it is loaded from another source. Valid values are: 1 - Yes, 2 - No. If 1, then this row is deleted. Required only for Collaborative Planning. You should provide the party name with which the company is registered in CP. For a planning (APS) only environment, this should be left null. Comments for entries posted to the system. Release number in the sales order posted to the system. Order number for each pegged transaction. Order release number for each pegged transaction.
END_ORDER_LINE_NUMBER. END_ORDER_TYPE refers to the pegged entity. In MSC_SUPPLIES PO's have the end order type (order type code = 6), in the SO's the end order type from MSC_DEMAND have the PO's (order type code = 1). New Order Placement Date MDS demand item. Flag to indicate the source of the order. Valid values are: 2 - External and 8 Internal. New Order Placement Date. Order Date Type Code. Schedule Arrival Date.
Latest Acceptable Date. Shipping Method Code. Promise Date. Org Firm Flag. To capture Ship set name. To capture Arrival set name. Please provide the Demand Source Header ID for the Demand Source Header in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Organization ID for the Organization in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Original Item ID for the Original Item in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Demand ID for the Demand in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Inventory Item ID for the Inventory Item in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Customer ID for the Customer in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Bill To Site Use ID for the Bill To Site Use in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Ship to site Use ID for the Ship to site Use in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Demand Source Line for the Demand in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Project Number associated with the transaction. Please provide the Task Number associated with the transaction.
Sales Orders from the SalesOrder.xml file
ication instances. (in this case from Sales Orders) Logic SalesOrders.xml:salesOrder:salesOrderDetail:ite mCode SalesOrders.xml:salesOrder:salesOrderDetail:shipFro mBranchCode
Fields Referenced SalesOrders.xml:salesOrder:salesOrderDetail:ite mCode SalesOrders.xml:salesOrder:salesOrderDetail:shi pFromBranchCode SalesOrders.xml:salesOrder:salesOrderDetail:qua SalesOrders.xml:salesOrder:salesOrderDetail:quantity ntity "0" SalesOrders.xml:salesOrder:salesOrderDetail:requeste SalesOrders.xml:salesOrder:salesOrderDetail:req dDate uestedDate SalesOrders.xml:salesOrder:salesOrderCode SalesOrders.xml:salesOrder:salesOrderCode SalesOrders.xml:salesOrder:salesOrderDetail:line SalesOrders.xml:salesOrder:salesOrderDetail:lineItem Item Parameter.Source_Instance Parameter.SO_Reservation_Type(1) <null> <null> The "Default Demand Class" field used for this customer in TradingPartners.dat (using shipToCustomerCode) <null> <null> Customer.xml:customer.parentName use the site code used for Trading Partner Sites (Partner Type=2)
E1 Table F4211 F4211 F4211
F4211 F4211 F4211
Customer.xml:customerGroup:name
F0101
Customer.xml:customer:parentName Customer.xml:customer:customerCode Customer.xml:customer:name
F0101 F03012 F0101
use the site code used for Trading Partner Sites (Partner Type=2) <null> SalesOrders.xml:salesOrder:priority SalesOrders.xml:salesOrder:salesOrderDetail:requeste dDate
Customer.xml:customer:billtoname
F0101
SalesOrders.xml:salesOrder:priority F4201 SalesOrders.xml:salesOrder:salesOrderDetail:req uestedDate F4211 SalesOrders.xml:salesOrder:salesOrderDetail:unit SalesOrders.xml:salesOrder:salesOrderDetail:unitPrice Price F4211 Parameter.SO Demand Visible(Y) Parameter.SO Forecast Visible(Y) Parameter.SO CTO Flag SalesOrders.xml:salesOrder:salesOrderCode
SalesOrders.xml:salesOrder:salesOrderCode F4211 SalesOrders.xml:salesOrder:salesOrderDetail:line SalesOrders.xml:salesOrder:salesOrderDetail:lineItem Item F4211 "2"
Parameter.CP_Company_Name <null> <null> <null> <null>
<null>
"1" SalesOrders.xml:salesOrder:createdDate <null> 2 SalesOrders.xml:salesOrder:createdDate <null> SalesOrders.xml:salesOrder:salesOrderDetail:arriveDa te MAX(SalesOrders.xml:salesOrder:salesOrderDetail:req uestedDate, SalesOrders.xml:salesOrder:salesOrderDetail:arriveDa te) <null> SalesOrders.xml:salesOrder:salesOrderDetail:arriveDa te <null> <null> <null>
SalesOrders.xml:salesOrder:createdDate
F4201
SalesOrders.xml:salesOrder:createdDate
F4201
SalesOrders.xml:salesOrder:salesOrderDetail:arri veDate F4211 SalesOrders.xml:salesOrder:salesOrderDetail:req uestedDate F4211 SalesOrders.xml:salesOrder:salesOrderDetail:arri veDate F4211 SalesOrders.xml:salesOrder:salesOrderDetail:arri veDate F4211
<null>
<null>
<null>
<null>
<null>
<null>
<null>
<null>
<null> <null> <null>
Return to File Definitions E1 Field ITM MCU calculation calculation = (F4211.UORG - F4211.SOCN) - the result is converted to planning unit of measure Comment
DRQJ concatenation LNID
concatenation = F4211.DOCO|F4211.KCOO|F4211.DCTO
concatenation
ALPH AN8 ALPH
ALPH PRIO DRQJ UPRC
B90CB124/D90CB124 DefaultSoldToShipTo passin F03012.an8 = mnShipToAddress get mnSoldToAddress description is retrieved for UDC H40/PR format = yyyy-mm-ddT00:00:00
concatenation LNID
concatenation = F4211.DOCO|F4211.KCOO|F4211.DCTO
TRDJ
TRDJ
RSDJ DRQJ RSDJ
format = yyyy-mm-ddT00:00:00 format = yyyy-mm-ddT00:00:00 format = yyyy-mm-ddT00:00:00
RSDJ
Table Description VCP-ODS Item Name Organization Code Primary UOM Quantity Completed Quantity
Requirement Date Sales Order Number Line Num Source Instance Code Reservation Type Reservation Quantity Subinventory Demand Class Sales Representative Contact Ordered Item Name
Customer Name
Ship To Site Code
Bill To Site Code Planning Group Demand Priority Request Date Selling Price Demand Visible Forecast Visible
CTO Flag Original System Reference Original System Line Reference Deleted Flag
Company Name Comments Order Release Number End Order Number End Order Release Number End Order Line Number
End Order Type New Order Placement Date Original Item Name Demand Source Type Order Date Type Code Schedule Arrival Date Latest Acceptable Date
Shipping Method Code Promise Date Org Firm Flag Ship Set name Arrival Set Name
Source Demand Source Header ID
Source Original Item ID
Source Demand ID
Source Customer ID
Source Bill To Site Use ID
Source Ship to site Use ID
Source Demand Source Line Project Number Task Number
Supplied by TransferOrder.xml for Orders with ship >Option.Base Date and quantity > 0
MSC_SALES_ORDERS This table stores sales order demand and reservations from source application instances. (in this case from Transfer Orders) Description MDS item name. Organization. Quantity ordered. Shipped quantity.
Need-by date. Order number.
Instance code defined on the planning server. Valid values are: 1 - Soft reservation, 2 - Hard reservation, 3 - Supply order reservation. Reservation quantity. Code for a sub-inventory. Name or identifier of a demand class.
Valid values are: Y - Yes, N - No. Valid values are: Y - Yes, N - No.
Configure to order. Default 2 for legacy/exchange. Valid values are: 1 - Yes, 2 - No. The reference number of a sales order if it is loaded from another source. The reference number of a line on a sales order if it is loaded from another source. Valid values are: 1 - Yes, 2 - No. If 1, then this row is deleted. Required only for Collaborative Planning. You should provide the party name with which the company is registered in CP. For a planning (APS) only environment, this should be left null. Comments for entries posted to the system. Release number in the sales order posted to the system. Order number for each pegged transaction. Order release number for each pegged transaction. END_ORDER_LINE_NUMBER. END_ORDER_TYPE refers to the pegged entity. In MSC_SUPPLIES PO's have the end order type (order type code = 6), in the SO's the end order type from MSC_DEMAND have the PO's (order type code = 1). New Order Placement Date MDS demand item. Flag to indicate the source of the order. Valid values are: 2 - External and 8 Internal. Order Date Type Code. Schedule Arrival Date. Latest Acceptable Date.
Shipping Method Code. Promise Date. Org Firm Flag. To capture Ship set name. To capture Arrival set name. Please provide the Demand Source Header ID for the Demand Source Header in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Organization ID for the Organization in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Original Item ID for the Original Item in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Demand ID for the Demand in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only.
Please provide the Inventory Item ID for the Inventory Item in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Customer ID for the Customer in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Bill To Site Use ID for the Bill To Site Use in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Ship to site Use ID for the Ship to site Use in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Demand Source Line for the Demand in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Project Number associated with the transaction. Please provide the Task Number associated with the transaction.
Supplied by TransferOrder.xml for Orders with ship >Option.Base Date and quantity > 0
ication instances. (in this case from Transfer Orders) Logic Fields Referenced TransferOrders.xml:transferOrder:transferOrderD TransferOrders.xml:transferOrder:transferOrder etail:itemCode Detail:itemCode TransferOrders.xml:transferOrder:originBranchC transferOrders.xml:transferOrder:originBranchCode ode TransferOrders.xml:transferOrder:transferOrderDetail TransferOrders.xml:transferOrder:transferOrder :quantity Detail:quantity "0"
E1 Table F4311 F0006 F4311
transferOrders.xml:transferOrder:transferOrderDetail: transferOrders.xml:transferOrder:transferOrderD shipDate etail:shipDate F4311 TransferOrders.xml:transferOrder:transferOrder transferOrders.xml:transferOrder:transferOrderCode Code F4311 transferOrders.xml:transferOrder:transferOrderDetail: transferOrders.xml:transferOrder:transferOrderD lineItem etail:lineItem F4311 Parameter.Source_Instance <null> <null> <null> <null> <null> <null> If Parameters.Internal_Transfers_Customer is null, then set to <null> otherwise Customer.xml:customer:parentName for the customer pointed to by Parameters.Internal_Transfers_Customer If Parameters.Internal_Transfers_Customer is null, then set to <null> otherwise use the Site Code developed for TradingPartnerSites for Customer.xml:customer:CustomerCode for the customer pointed to by Parameters.Internal_Transfers_Customer If Parameters.Internal_Transfers_Customer is null, then set to <null> otherwise use the Billing to Site Code developed for TradingPartnerSites for Customer.xml:customer:CustomerCode for the customer pointed to by Parameters.Internal_Transfers_Customer <null> <null> <null> <null> Parameter.SO Demand Visible(Y) Parameter.SO Forecast Visible(Y)
Customer.xml:customer:parentName
F0101
Customer.xml:customer:name
F0101
Customer.xml:customer:billtoname
F0101
Parameter.SO CTO Flag TransferOrders.xml:transferOrder:transferOrder transferOrders.xml:transferOrder:transferOrderCode Code F4311 transferOrders.xml:transferOrder:transferOrderDetail: TransferOrders.xml:transferOrder:transferOrder lineItem Detail:lineItem F4311 "2"
Parameter.CP_Company_Name <null> <null> <null> <null> <null>
"1" <null> <null> "8" <null> TransferOrders.xml:transferOrder:transferOrder TransferOrders.xml:transferOrder:transferOrderDetail:arriveDate Detail:arriveDate TransferOrders.xml:transferOrder:transferOrder TransferOrders.xml:transferOrder:transferOrderDetail:arriveDate Detail:arriveDate Distribrution.xml:lane:Transport Distribrution.xml:lane:Transport Mode:transportmode where Mode:transportmode TransferOrders.xml:transferOrder:originBranchCode= TransferOrders.xml:transferOrder:originBranchC Distribution.xml:lane:originBranchCode and ode TransferOrders.xml:transferOrder:destinationBranchC Distribution.xml:lane:originBranchCode ode=Distribution.xml:lane:destinationBranchCode TransferOrders.xml:transferOrder:destinationBra Use same logic as shipmentmethod to determine the nchCode preferred transportmode Distribution.xml:lane:destinationBranchCode TransferOrders.xml:transferOrder:transferOrder TransferOrders.xml:transferOrder:transferOrderDetail:arriveDate Detail:arriveDate <null> <null> <null> F4311 F4311 F3403 F0006 F3403 F4311 F3403 F4311
TransferOrders.xml:transferOrder:transferOrder transferOrders.xml:transferOrder:transferOrderCode Code F4311 TransferOrders.xml:transferOrder:originBranchC ode F0006
transferOrders.xml:transferOrder:originBranchCode
transferOrders.xml:transferOrder:transferOrderDetail: TransferOrders.xml:transferOrder:transferOrder itemCode Detail:itemCode F4311 transferOrders.xml:transferOrder:transferOrderDetail: TransferOrders.xml:transferOrder:transferOrder itemCode Detail:itemCode F4311
transferOrders.xml:transferOrder:transferOrderDetail: TransferOrders.xml:transferOrder:transferOrder itemCode Detail:itemCode F4311
<null>
transferOrders.xml:transferOrder:billToCustomerCode transferOrders.xml:transferOrder:ShipToCustomerCo de transferOrders.xml:transferOrder:transferOrderDetail: lineItem <null> <null> <null>
e Date and
Return to File Definitions E1 Field ITM MCU UOPN MCU is retrieved from F0006 where F0006.AN8 = F4311.AN8 converted to planning unit of measure if F4311.ADDJ is not blank use else LTLV is retrieved from F4102 where F4102.ITM = F4311.ITM and F4102.MCU = F4311.MCU calculation = if F4102.LTLV > 0, then shipDate = F4311.PDDJ - F4102.LTLV else shipDate = F4311.PDDJ format = yyyy-mmddT00:00:00 concatenation = F4311.DOCO|F4311.KCOO|F4311.DCTO|F4311.SFXO Comment
calculation concatenation LNID
ALPH
ALPH
ALPH
B90CB124/D90CB124 DefaultSoldToShipTo passin F03012.an8 = mnShipToAddress get mnSoldToAddress
concatenation LNID
PDDJ PDDJ concat MCU mmcu MCU cmcu PDDJ
format = yyyy-mm-ddT00:00:00 format = yyyy-mm-ddT00:00:00 All UDC values from 00|TM
concatenation
MCU
ITM
ITM
ITM
Table Description VCP-ODS Item Name Organization Code New Schedule Date
Firm Planned Type WIP Entity Name Source Instance Code Revision Unit Number New WIP Start Date New Order Quantity Alternated BOM Designator Alternate Routing Designator Line Code Project Number Task Number
Planning Group Schedule Group Name
Build Sequence
WO Lateness Cost Implement Processing Days Late Supply Date Late Supply Qty Qty Scrapped
Qty Completed
WIP Status Code Bill Name Routing Name Deleted Flag
Company Name Co-Products Supply Order Type Quantity Per Assembly Quantity Issued
Operation Seq Code Effectivity Date Job Op Seq Code
Jump Op Seq Code Jump Op Effectivity Date
Source Org ID
Source Project ID
Source Task ID
Source supply ID
Source Bill Sequence ID
Source Routing Sequence ID
Source Schedule Group ID
Source Wip Entity ID
Select only workorders of type "Production" and those work orders that have at least one work order operation record
MSC_SUPPLIES MSC_Supplies lists all the supplies for this plan - This spreadsheet contains Work Orders Description Inventory item name Organization End date of the supply. WIP completion date.
Flag indicating whether the order is firm or not. WIP entity name. Source instance code defined on the planning server. Inventory item revision code Unit number. New WIP schedule start date. Supply quantity. Alternate BOM designator. Alternate routing designator. Project name. Task name. Project planning group. If more than one project belongs to the same planning group, this column is used to net the demand/supply across projects.
Build sequence for the planned order. Related with the SCHEDULE_GROUP_ID. Within the schedule, each job has a different build sequence ID. Work order lateness cost. Required by SCO to minimize the cost according to Key Performance Indicators (KPIs) specified by the planner on the plan options form. Implement processing days Supply date for the shadow part of the split supplies. Used by HLS. Shadow supply quantity. Used by HLS. Current job scrapped units.
Current job quantity completed.
WIP job status code. BOM should exist in MSC_BOMS. Routing should exist in MSC_ROUTINGS. Valid values are: 1 - Yes, 2 - No. If 1, then this row is deleted. Required only for Collaborative Planning. You should provide the party name with which the company is registered in Collaborative Planning. For a planning (APS) only environment, this should be left null.
Specifies type of order: planned order, purchase order, etc.. Part usage quantity Quantity Issued
Operation Sequence Code Effectivity Date Job sequence number of the current operation. Populated only for lot-based jobs Routing sequence number of the jumped operation. If the operation is outside the network then a value of 50000 is populated. Populated only for lot-based jobs. Jumped Operation Effectivity Date
Please provide the Organization ID for the Organization in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Inventory Item ID for the Inventory Item in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Project ID for the Project in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Task ID for the Task in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide a unique ID to identify this supply in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only Please provide the Disposition ID for the Supply in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Bill Sequence ID for the Bill Sequence in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Routing Sequence ID for the Routing Sequence in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Schedule Group ID for the Schedule Group in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Wip Entity ID for the Wip Entity in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only.
ins Work Orders Logic WorkOrder.xml:workOrder:workOrderProducedItemB om:itemCode WorkOrder.xml:workOrder:branchCode WorkOrder.xml:workOrder:requestedDate
Fields Referenced WorkOrder.xml:workOrder:workOrderProducedI temBom:itemCode WorkOrder.xml:workOrder:branchCode WorkOrder.xml:workOrder:requestedDate
E1 Table F4801 F4801 F4801
Decode(WorkOrder.xml:workOrder:changesAllowed, "Yes", 2, "No", 1) WorkOrder.xml:workOrder:workOrderCode Parameter.Source_Instance <null> <null> WorkOrder.xml:workOrder:startDate WorkOrder.xml:workOrder:workOrderProducedItemB om:quantity <null> <null> <null> <null> <null>
WorkOrder.xml:workOrder:changesAllowed WorkOrder.xml:workOrder:workOrderCode
F4801
WorkOrder.xml:workOrder:startDate F4801 WorkOrder.xml:workOrder:workOrderProducedI temBom:quantity F3111
<null> <null>
<null> Parameter.WO_Lateness_Cost_%/100 * Base.xml:itemBranch.itemPrice <null> <null> <null> <null> WorkOrder.xml:workOrder:workOrderOperation:wor kOrderProducedItemBom:quantity WorkOrder.xml:workOrder:workOrderOperation:wor kOrderProducedItemBom:quantityRemaining Use the user defined translation table to decode WorkOrder.xml:workOrder:status, if a match can not be found set the value to "1" (Unreleased). The expected translations are (but can be amended by users): On Hold 6 Complete 4 Closed 4 WIP 3 Released 3 UnReleased 1 Cancelled 7 Pending 1 Entered 1 Issued 3 Open 1 Attached 1 WorkOrder.xml:workOrder:itemCode WorkOrder.xml:workOrder:itemCode "2"
base.xml:itemBranch:itemPrice
F4106
WorkOrder.xml:workOrder:workOrderOperation :workOrderProducedItemBom:quantity F4801 WorkOrder.xml:workOrder:workOrderOperation :workOrderProducedItemBom:quantityRemainin g
WorkOrder.xml:workOrder:status WorkOrder.xml:workOrder:itemCode WorkOrder.xml:workOrder:itemCode
F34A30
F4801
F4801
Parameter.CP_Company_Name <null> "3" ("3" for standard WIP jobs, 7 for non standard) <null> <null> Search the WorkOrderOperations and retreive all operations codes, sort the operation codes in operation code seq (fifth field) and return the largest (last) operation code seq (fifth field) which has a status of Active or Closed. <null> <null>
<null> <null>
WorkOrder.xml:workOrder:branchCode
F4801
WorkOrder.xml:workOrder:workOrderProducedItemB WorkOrder.xml:workOrder:workOrderProducedI om:itemCode temBom:itemCode F4801
<null>
<null>
WorkOrder.xml:workOrder:workOrderCode
F4801
<null>
<null>
<null>
<null>
<null>
Return to File Definitions E1 Field itm mcu drqj Comment
yyyy-mm-ddT00:00:00 "Yes" - If parts list and routing can be deleted, not frozen, and the status is not greater than the prohibit change status "No" - If parts list or routing cannot be deleted, frozen, or the status is greater than the prohibit status If the stocking type is 'C' (configured item) or 'K' (Kit Item) for the item on work order, then the changes are not allowed on the work order If the quantity scrapped F4801.WASOCN is greater than zero or if the quantity shipped F4801.WASOQS is greater than zero or if the Work Order Frozen Flag is set to 'Y" then no changes are allowed on the Work Order If the RunMachineActual(wlmaca) hours, RunLaborActual (wllaba) hours, and Setuplaboractual (wlseta) hours are reported on a routing step then the routing can not be deleted The Parts list records can only be deleted if the Quantity Issued (wmtrqt), UnaccountedDirectLaborHrs (wmcts1),UnaccountedDirectLaborAmt (wmcts4), UnaccountedScrapAmt (wmcts7) and UnaccountedScrapUnits (wmcts8) are populated with zero's meaning no activity has been performed on parts list records If the material status code is 07, it means that the parts are in Warehouse. This parts list record can not be deleted If the quantities on the parts list are hard commited then Parts list can not be deleted
calculated doco
strt uorg
UPRC
uorg
calculated
converted to planning unit of measure F3112.uorg - F3112.soqs (ordered less completed, for the last operation) converted to planning unit of measure
UDC
itm
Retrieve from F34A30(00, SS) description then Get UDC 34A|WS(description)
itm
mcu
itm
doco
Table Description VCP-ODS Item Name Organization Code Using Requirement Quantity WIP Entity Name Using Assembly Demand Date Source Instance Code Using Assembly Item Name
Operation Sequence Code Origination Type Project Number Task Number Planning Group End Item Unit Number Demand Class Order Number
WIP Status Code WIP Supply Type Deleted Flag
Company Name Routing Name Alternate Routing Designator Operation Effectivity Date
Quantity Per Assembly Quantity Issued
Source Org ID
Source Project ID
Source Task ID
MSC_DEMANDS This table stores sales order demand and reservations from source application instances. (in this case from Work Order Components) Description Inventory item name. Component name for which dependent demand exists. This comes from Production Discrete job. Organization Required quantity for a component. Job name. Operation requirement start date, where this component is going to be used. Instance code defined on the planning server. Assembly item name for which job is created in WIP.
Operation Sequence Code. Valid values are: 2 - Non-standard job, 3 - Discrete job. Project identifier. This should be predefined in MSC_PROJECTS. Task identifier. This should be predefined in MSC_PROJECTS_TASKS. Project planning group End Item Unit Number. Name or identifier of a demand class. Order Number.
Job status. Valid values are: 1 - Unreleased, 3 - Released, 4 - Complete, 6 - On Hold, 7 - Canceled, 12 - Closed. Supply type. Valid values are: 1 - Push, 2 - Assembly Pull, 3 - Operation Pull, 4 - Bulk, 5 - Supplier, 6 - Phantom, 7 - Based on Bill. Valid values are: 1 - Yes, 2 - No. If 1, then is row is deleted. Required only for Collaborative Planning. You should provide the party name with which the company is registered in CP. For a planning (APS) only environment, this should be left null. Routing Name. Alternate Routing Designator. Operation Effectivity Date.
Part usage quantity Quantity issued Please provide the Organization ID for the Organization in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Inventory Item ID for the Item in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Assembly Item ID for the Assembly Item in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Sales Order Line ID for the Sales Order Line in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Project ID for the Project in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Task ID for the Task in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only.
ication instances. (in this case from Work Order Components) Logic WorkOrder.xml:workOrder:workOrderOperation: workOrderConsumedItemBom:itemCode WorkOrder.xml:workOrder:branchCode WorkOrder.xml:workOrder:workOrderOperation:wor kOrderConsumedItemBom:quantity WorkOrder.xml:workOrder:workOrderCode WorkOrder.xml:workOrder:workOrderOperation:start Date Parameter.Source_Instance WorkOrder.xml:workOrder:workOrderOperation:s tartDate
Fields Referenced WorkOrder.xml:workOrder:workOrderOperation :workOrderConsumedItemBom:itemCode WorkOrder.xml:workOrder:branchCode WorkOrder.xml:workOrder:workOrderOperation :workOrderConsumedItemBom:quantity WorkOrder.xml:workOrder:workOrderCode WorkOrder.xml:workOrder:workOrderOperation :startDate
E1 Table F3111 F4801 F3111 F4801 F3112
WorkOrder.xml:workOrder:workOrderProducedI temBom:itemCode F4801
WorkOrder.xml:workOrder:workOrderOperation:oper ationCode (5th field) * 100 "3" <null> <null> <null> <null> <null> WorkOrder.xml:workOrder:demand Use the user defined translation table to decode WorkOrder.xml:workOrder:status, if a match can not be found set the value to "1" (Unreleased). The expected translations are (but can be amended by users): On Hold 6 Complete 4 Closed 4 WIP 3 Released 3 UnReleased 1 Cancelled 7 Pending 1 Entered 1 Issued 3 Open 1 Attached 1 <null> "2"
WorkOrder.xml:workOrder:workOrderOperation :operationCode F3003
WorkOrder.xml:workOrder:demand
F4801
WorkOrder.xml:workOrder:status
F34A30
Parameter.CP_Company_Name <null> <null> Parameters.Base_Effective_Date
Aggregate the quantity for the same work order operation sequence code Aggregate the quantity for the same work order operation sequence code
F4801
WorkOrder.xml:workOrder:workOrderOperation:wor WorkOrder.xml:workOrder:workOrderOperation kOrderConsumedItemBom:itemCode :workOrderConsumedItemBom:itemCode F3111
WorkOrder.xml:workOrder:itemCode
WorkOrder.xml:workOrder:itemCode
F4801
<null>
<null>
<null>
Return to File Definitions E1 Field cpit mcu uorg doco strt|SEST yyyy-mm-ddT00:00:00 Comment
itm Retrieve from F3003 using F112.(mmcu, kit, uorg, trt) if can not find change quantity to 0. Take master routing into account. if UDC(34A|GU).special Handeling = 1 MMCU|KIT|TRT|BQTY|OPSQ|OPSC|LINE|EFFF|F3112.mcu else MMCU|KIT|TRT|BQTY|OPSQ|OPSC|LINE|F3112.mcu
concat
concat
RORN|RKCO|RCTO
UDC
mcu
cpit
itm
Department Code
Resource Code Organization Code
Resource Seq Code Start Date
Operation Hours Required Assigned Units WIP Entity Name Source Instance Code Item Name
Operation Seq Code
Hours Expended Demand Class Basis Type End Date WIP Job Type Scheduled Completion Date Schedule Quantity
Quantity Completed Std. Op. Code Supply Type Deleted Flag
Company Name Routing Name Alternate Routing Designator
Operation Effectivity Date Alternate Number Quantity In Queue Quantity Running Quantity waiting to move YIELD Usage Rate
Schedule Flag Activity group ID Principal Flag Orig Resource Sequence Number
Source Department ID
Source Resource ID
Source Resource Sequence Number
Source Operation Sequence ID
Source WIP Entity ID
Source Operation Sequence Number
MAXIMUM_ASSIGNED_UNITS
Firm_flag
UNADJUSTED_RESOURCE_HOURS
MSC_RESOURCE_REQUIREMENTS This table stores the resource requirments generated by existing supplies. Description
Department unique identifier. Department should already be defined in the DepartmentResource.dat (MSC_ST_DEPARTMENT_RESOURCES). Resource unique identifier. Resources should already be defined in the DepartmentResource.dat (MSC_ST_DEPARTMENT_RESOURCES). Organization identifier on the planning server.
Resource sequence identifier. Start date of the first unit.
Hours required. Stored in RESOURCE_HOURS on the ODS table. Assigned units of resource WIP identifier. Stored in the MSC_ST_SUPPLIES table - validate based on WIP_ENTITY_NAME, INSTANCE_CODE, and ORGANIZATION_CODE. Source instance code defined on the planning server. Inventory item name.
Identifier or code for one step in an operation sequence.
Hours expended. Name or identifier of a demand class. Basis for charging and scheduling resources. Valid values are: 1 - Item, 2 - Lot, 3 Resource Units, 4 - Resource Value 5 - Total Value, 6 - Activity. Completion date. Valid values are: 1 - Standard, 2 - Nonstandard Scheduled completion date Quantity
Completed quantity Std. operation code Supply type of WIP. Valid values are: 1 - Push, 2 - Assembly pull, 3 - Operation pull, 4 - Bulk, 5 - Supply, 6 - Phantom, 7 - Based on bill. Valid values are: 1 - Yes, 2 - No. If 1, then this row is deleted. Required only for Collaborative Planning. You should provide the party name with which the company is registered in CP. For a planning (APS) only environment, this should be left null. Name of routing.
Number of units in queue of operation Number of units in To Run of the operation Number of units Waiting To Move in the operation Yield Rate per assembly or amount per job
Schedule flag Activity group identifier Principal Flag Original Resource Sequence Number Please provide the Organization ID for the Organization in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Department ID for the Department in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Resource ID for the Resource in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Resource Sequence Number for the Resource Sequence in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only.
Please provide the Operation Sequence ID for the Operation Sequence in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only.
Please provide the WIP Entity ID for the WIP Entity in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only.
Please provide the Operation Sequence Number for the Operation Sequence in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only.
NOT FIRM - 0, FIRM_START - 1,FIRM_END - 2, FIRM_RESOURCE -3 ,FIRM_START_END- 4, FIRM_START_RESOURCE - 5, FIRM_END_RESOURCE - 6, FIRM_ALL 7
es. Logic Fields Referenced Manufacturing.xml:machine:workCenter Manufacturing.xml:crew:workCenter Manufacturing.xml:tool:workCenter E1 Table
F34A110 Use the Dept Code on Resources.dat for this resource F34A150 (WorkOrder.xml:workOrder:workOrderOperation:wor WorkOrder.xml:workOrder:workOrderOperati or kOrderBor:resourceCode) on:workOrderBor:resourceCode F34A120 Manufacturing.xml:machine:workCenter WorkOrder.xml:workOrder:workOrderOperation:wor Manufacturing.xml:crew:workCenter kOrderBor:resourceCode Manufacturing.xml:tool:workCenter F34A110 WorkOrder.xml:workOrder:branchCode WorkOrder.xml:workOrder:branchCode F4801 Get the Resource_seq_code from the Operation WorkOrder.xml:workOrder:itemCode F4801 Resource using ROUTING_NAME = WorkOrder.xml:workOrder:itemCode ASSEMBLY_NAME = WorkOrder.xml:workOrder:itemCode OPERATION_SEQ_CODE=WorkOrder.xml:workOrder: WorkOrder.xml:workOrder:workOrderOperation workOrderOperation:operationCode (5th field) :operationCode F3003 RESOURCE_CODE=WorkOrder.xml:workOrder:workOr WorkOrder.xml:workOrder:workOrderOperation derOperation:workOrderBor:resourceCode :workOrderBor:resourceCode WorkOrder.xml:workOrder:workOrderOperation:start WorkOrder.xml:workOrder:workOrderOperation Date :startDate F3112 F34A150 WorkOrder.xml:workOrder:workOrderOperation:wor WorkOrder.xml:workOrder:workOrderOperation or kOrderBor:duration (first record only) :workOrderBor:duration F34A120 <null> (potentially we may need to set this to 1) if easier we can use a Parameter value WorkOrder.xml:workOrder:workOrderCode Parameter.Source_Instance WorkOrder.xml:workOrder:itemCode WorkOrder.xml:workOrder:workOrderCode WorkOrder.xml:workOrder:itemCode F4801 F4801
WorkOrder.xml:workOrder:workOrderOperation:oper WorkOrder.xml:workOrder:workOrderOperation ationCode (5th field) :operationCode F3003 F34A150 WorkOrder.xml:workOrder:workOrderOperation or :workOrderBor:duration F34A120 WorkOrder.xml:workOrder:workOrderOperation :remainingDuration
WorkOrder.xml:workOrder:workOrderOperation:dura tion WorkOrder.xml:workOrder:workOrderOperation:rem ainingDuration <null> Supply demand class
"1" <null> (not mand in APS) "1" workOrder.xml:workOrder:workOrderOperation:sche workOrder.xml:workOrder:workOrderOperation: duledCompletionDate scheduledCompletionDate F3112 WorkOrder.xml:workOrder:quantity WorkOrder.xml:workOrder:quantity F4801
WorkOrder.xml:workOrder:workOrderOperation:qtyC WorkOrder.xml:workOrder:workOrderOperation ompleted :qtyCompleted F3112 <null> Parameter.Work_Order_Resource_Supply_Type (3) "2"
Parameter.Company_Name <null> <null> Use the Effectivity_Date in branchoperation Where Manufacturing.xml:branchoperation:operationCode= WorkOrder.xml:workorderoperation:operationCode and Manufacturing.xml:branchoperation:branchCode=Wo rkOrder.xml:workorder:branchCode ..should be the same as RoutingOperation WorkOrders.xml:workOrders:routingCode <null> <null> <null> <null> WorkOrder.xml:workOrder:workOrderOperation WorkOrder.xml:workOrder:workOrderOperation:yield :yield WorkOrder.xml:workOrder:quantity WorkOrder.xml:workOrder:quantity / WorkOrder.xml:workOrder:workOrderOperation:wor WorkOrder.xml:workOrder:workOrderOperation kOrderBor:duration :workOrderBor:duration "1" <null> <null> <null>
F3003
F3112 F4801 F34A150 or F34A120
F4801
<null> WorkOrder.xml:workOrder:workOrderOperation:wor WorkOrder.xml:workOrder:workOrderOperation kOrderBor:resourceCode :workOrderBor:resourceCode
<null>
WorkOrder.xml:workOrder:workOrderOperation:oper WorkOrder.xml:workOrder:workOrderOperation ationCode (5th field) :operationCode F3003
F4801
WorkOrder.xml:workOrder:workOrderOperation:oper WorkOrder.xml:workOrder:workOrderOperation ationCode (5th field) :operationCode F3003 Capacity Units from DepartmentResource.dat The join key will be organization code and resource code
Decode(WorkOrder.xml:workOrder:changesAllowed, "Yes", 0,7) WorkOrder.xml:workOrder:changesAllowed F34A150 WorkOrder.xml:workOrder:workOrderOperation or WorkOrder.xml:workOrder:workOrderOperation:workOrderBor:duration :workOrderBor:duration F34A120
MCU
rescd
MCU mcu itm Retrieve from F3003 using F112.(mmcu, kit, uorg, trt) if can not find change quantity to 0. Take master routing into account. if UDC(34A|GU).special Handeling = 1 MMCU|KIT|TRT|BQTY|OPSQ|OPSC|LINE|EFFF|F3112.mcu else MMCU|KIT|TRT|BQTY|OPSQ|OPSC|LINE|F3112.mcu
concat
strt|SEST runtm or apsdur
yyyy-mm-ddT00:00:00
Take Time Basis in account
doco itm Retrieve from F3003 using F112.(mmcu, kit, uorg, trt) if can not find change quantity to 0. Take master routing into account. if UDC(34A|GU).special Handeling = 1 MMCU|KIT|TRT|BQTY|OPSQ|OPSC|LINE|EFFF|F3112.mcu else MMCU|KIT|TRT|BQTY|OPSQ|OPSC|LINE|F3112.mcu
concat runtm or apsdur
Take Time Basis in account Remaining Quantity = F4801.uorg - F4801.soqs. Calculation((duration/ uorg)*remainingQty)
strx|SEET uorg
yyyy-mm-ddT00:00:00 converted to planning unit of measure
calculated
uorg - soqs
concat
Retrieve from F3003 using F4801.(mcu, itm, uorg, trt) if can not find change quantity to 0. Take master routing into account if UDC(34A|GU).special Handeling = 1 MMCU|KIT|TRT|BQTY|OPSQ|OPSC|LINE|EFFF else MMCU|KIT|TRT|BQTY|OPSC|LINE
cpyp uorg runtm or apsdur
Using last operation step of work order's routing converted to planning unit of measure
mcu
concat
Retrieve from F3003 using F112.(mmcu, kit, uorg, trt) if can not find change quantity to 0. Take master routing into account. if UDC(34A|GU).special Handeling = 1 MMCU|KIT|TRT|BQTY|OPSQ|OPSC|LINE|EFFF|F3112.mcu else MMCU|KIT|TRT|BQTY|OPSQ|OPSC|LINE|F3112.mcu
doco Retrieve from F3003 using F112.(mmcu, kit, uorg, trt) if can not find change quantity to 0. Take master routing into account. if UDC(34A|GU).special Handeling = 1 MMCU|KIT|TRT|BQTY|OPSQ|OPSC|LINE|EFFF|F3112.mcu else MMCU|KIT|TRT|BQTY|OPSQ|OPSC|LINE|F3112.mcu
concat
"Yes" - If parts list and routing can be deleted, not frozen, and the status is not greater than the prohibit change status "No" - If parts list or routing cannot be deleted, frozen, or the status is greater than the prohibit status If the stocking type is 'C' (configured item) or 'K' (Kit Item) for the item on work order, then the changes are not allowed on the work order If the quantity scrapped F4801.WASOCN is greater than zero or if the quantity shipped F4801.WASOQS is greater than zero or if the Work Order Frozen Flag is set to 'Y" then no changes are allowed on the Work Order If the RunMachineActual(wlmaca) hours, RunLaborActual (wllaba) hours, and Setuplaboractual (wlseta) hours are reported on a routing step then the routing can not be deleted The Parts list records can only be deleted if the Quantity Issued (wmtrqt), UnaccountedDirectLaborHrs (wmcts1),UnaccountedDirectLaborAmt (wmcts4), UnaccountedScrapAmt (wmcts7) and UnaccountedScrapUnits (wmcts8) are populated with zero's meaning no activity has been performed on parts list records If the material status code is 07, it means that the parts are in Warehouse. This parts list record can not be deleted If the quantities on the parts list are hard commited then Parts list can not be deleted
calculated runtm or apsdur
Table Description VCP-ODS ACTUAL_QTY SALES_DATE DM_ITEM_CODE DM_ORG_CODE
DemHistory.dat Demand History Description
DM_SITE_CODE
EBS_SALES_CHANNEL_CODE
EBS_DEMAND_CLASS_CODE EBS_BOOK_HIST_BOOK_QTY_BD EBS_BOOK_HIST_REQ_QTY_BD EBS_BOOK_HIST_BOOK_QTY_RD EBS_BOOK_HIST_REQ_QTY_RD EBS_SHIP_HIST_SHIP_QTY_SD EBS_SHIP_HIST_SHIP_QTY_RD EBS_SHIP_HIST_REQ_QTY_RD Parent Item Code. ( Used for CTO). Not used in phase1 of the JDE-APS project EBS_PARENT_ITEM_CODE Parent Item Code. ( Used for CTO). Not used in phase1 of the JDE-APS project EBS_BASE_MODEL_CODE
Records need to be aggregated by : *Sales Date *Item Code *ORG_Code *Site Code
Logic SUM of SalesOrderHistory.txt:13. Quantity SalesOrderHistory.txt:14. Requested Date SalesOrderHistory.txt:8. Short Item Number SalesOrderHistory.txt:5. Business Unit Customer.xml:customer:parentName + Parameter.Demantra_Field_Delimiter + Customer.xml:customer:parentAddressNumber + Parameter.Demantra_Field_Delimiter customer.xml:customer:customerCode + Parameter.Field_Delimiter + Customer.xml:customer:name + Parameter.Demantra_Field_Delimiter + Customer Category pointed to by Parameter.Sales_Channel_Category. Refer to the FDD on handling of customer category Customer Category pointed to by Parameter.Demand_Class_Category. Refer to the FDD on handling of customer category SUM of SalesOrderHistory.txt:13. Quantity <null> <null> <null> <null> <null> <null>
Fields Referenced SalesOrderHistory.txt:13. Quantity SalesOrderHistory.txt:14. Requested Date SalesOrderHistory.txt:8. Short Item Number SalesOrderHistory.txt:5. Business Unit Customer.xml:customer:parentName Customer.xml:customer:parentAddressNum ber Customer.xml:customer:customerCode Customer.xml:customer:name Customer.xml:customerGroup:name (for Operating Unit) Customer No Ship To Customer.xml:customerGroup:name (for Sales Channel) Customer.xml:customer:customerCode Customer.xml:customerGroup:name (for Demand Classl) Customer.xml:customer:customerCode SalesOrderHistory.txt:13. Quantity
E1 Table F42119/F421 1
F0101 F43090 F03012 F0101 F0101

F42119/F4211
F0101 F03012 F0101 F03012 F42119/F421 1
<null>
<null>
Return to File Definitions E1 Field SOQS Comment
ALPH AN8 AN8 ALPH concatenation SHAN concatenation AN8 concatenation AN8 SOQS
F0101.AN8 = parentAddressNumber F0101.AN8 = parentAddressNumber
concatenation = data dictionary description for data items AC01 AC30|F0101.AC01 - AC30 concatenation = data dictionary description for data items AC01 AC30|F0101.AC01 - AC30 concatenation = data dictionary description for data items AC01 AC30|F0101.AC01 - AC30
Converted to Planning UOM
Table Description VCP-ODS 1. Short Item Number 2. 2nd Item Number 3. 3rd Item Number 4. Branch/Plant
ListPrice.txt Price Lists Description
5. Customer Number 6. Expired Date 7. Effective Date 8. Amount List Price
Primarily a copied file (customer translated)
Logic ListPrice.txt:1. Short Item Number ListPrice.txt:2. 2nd Item Number ListPrice.txt:3. 3rd Item Number ListPrice.txt:4. Branch/Plant If ListPrice.txt:5. Customer Number = 0, leave it as zero, otherwise Customer.xml:customer:parentName + Parameter.Demantra_Field_Delimiter + Customer.xml:customer:parentAddressNumber + Parameter.Demantra_Field_Delimiter + Customer Number (fifth field of ListPrice) + Parameter.Field_Delimiter + ListPrice.txt:6. Expired Date ListPrice.txt:7. Effective Date ListPrice.txt:8. Amount List Price
Fields Referenced ListPrice.txt:1. Short Item Number ListPrice.txt:2. 2nd Item Number ListPrice.txt:3. 3rd Item Number ListPrice.txt:4. Branch/Plant Customer.xml:customer:parentName Customer.xml:customer:parentAddressNumber Customer.xml:customer:customerCode Customer.xml:customer:name Customer.xml:customerGroup:name (for Operating Unit) ListPrice. Customer Number ListPrice.txt:6. Expired Date ListPrice.txt:7. Effective Date ListPrice.txt:8. Amount List Price
E1 Table F4106 F4106 F4106 F4106 F0101 F43090 F03012 F0101 F0101 F4106
Return to File Definitions E1 Field ITM LITM AITM MCU ALPH AN8 AN8 ALPH concatenation AN8 Comment
Table Description VCP-ODS 1. Short Item Number 2. Branch/Plant 3. 2nd Item Number 4. 3rd Item Number 5. Item Cost 6. Cost Method 7. Cost Method Description
ItemCost.txt Item Costs Description
Copied file
No E1 file definition available
Logic Decoded Item using ItemCost.txt:1. Short Item Number ItemCost.txt:2. Branch/Plant ItemCost.txt:3. 2nd Item Number ItemCost.txt:4. 3rd Item Number ItemCost.txt:5. Item Cost ItemCost.txt:6. Cost Method ItemCost.txt:7. Cost Method Description
Fields Referenced ItemCost.txt:1. Short Item Number ItemCost.txt:2. Branch/Plant ItemCost.txt:3. 2nd Item Number ItemCost.txt:4. 3rd Item Number ItemCost.txt:5. Item Cost ItemCost.txt:6. Cost Method ItemCost.txt:7. Cost Method Description
E1 Table
Table Description VCP-ODS 1. Document (Order No, Invoice) 2. Order Type 3. Order Company (Order Number) 4. Line Number 5. Short Item Number
6. Customer No Ship To 7. Business Unit 8. Actual Ship Date 9. Promotion ID 10. Cost Type 11. Amount - Extended Price 12. Order Suffix 13. Price History Alternate Key 14. Price History Alternate Key So 15. Sequence Number 16. Sub-Sequence Number 17. Tier 18. Target Application
Primarily a copied
PriceHistory.txt Price History Description
Primarily a copied file (customer translated)
Logic PriceHistory.txt: 1. Document (Order No, Invoice) PriceHistory.txt: 2. Order Type PriceHistory.txt: 3. Order Company (Order Number) PriceHistory.txt: 4. Line Number PriceHistory.txt: 5. Short Item Number Customer.xml:customer:parentName + Parameter.Demantra_Field_Delimiter + Customer.xml:customer:parentAddressNumber + Parameter.Demantra_Field_Delimiter + Customer No Ship To (sixth field in PriceHistory) + Parameter.Field_Delimiter + Customer.xml:customer:name + Parameter.Demantra_Field_Delimiter + PriceHistory.txt: 7. Business Unit PriceHistory.txt: 8. Actual Ship Date PriceHistory.txt:9. Promotion ID PriceHistory.txt: 10. Cost Type PriceHistory.txt: 11. Amount - Extended Price PriceHistory.txt: 12. Order Suffix PriceHistory.txt: 13. Price History Alternate Key PriceHistory.txt: 14. Price History Alternate Key So PriceHistory.txt: 15. Sequence Number PriceHistory.txt: 16. Sub-Sequence Number PriceHistory.txt: 17. Tier PriceHistory.txt: 18. Target Application
Fields Referenced PriceHistory.txt: 1. Document PriceHistory.txt: 2. Order Type PriceHistory.txt: 3. Order Company PriceHistory.txt: 4. Line Number PriceHistory.txt: 5. Short Item Number Customer.xml:customer:parentName Customer.xml:customer:parentAddressNumber Customer.xml:customer:customerCode Customer.xml:customer:name Customer.xml:customerGroup:name (for Operating Unit) PriceHistory.txt:6. Customer No Ship To PriceHistory.txt: 7. Business Unit PriceHistory.txt: 8. Actual Ship Date PriceHistory.txt:9. Promotion ID PriceHistory.txt: 10. Cost Type PriceHistory.txt: 11. Amount - Extended Price PriceHistory.txt: 12. Order Suffix PriceHistory.txt: 13. Price History Alternate Key PriceHistory.txt: 14. Price History Alternate Key So PriceHistory.txt: 15. Sequence Number PriceHistory.txt: 16. Sub-Sequence Number PriceHistory.txt: 17. Tier PriceHistory.txt: 18. Target Application
E1 Table F42119 F42119 F42119 F42119 F42119 F0101 F43090 F03012 F0101 F0101 F42119 F42119 F42119 F4074 F4074 F4074 F4074 F4074 F4074 F4074 F4074 F4074 F4074
Return to File Definitions E1 Field DOCO DCTO KCOO LNID ITM ALPH AN8 AN8 ALPH concatenation SHAN MCU ADDJ PMTN COSTYP AEXP SFXO AKID SRCFD OSEQ SUBSEQ TIER PA04 Comment
Table Description VCP-ODS 1. Check Request ID 2. Check # 3. Settlement Type 4. Check Amount 5. Currency 6. Check Date 7. Multiple Payments
APConfirm.txt Accounts Payable Confirmations Description
Logic APConfirm.txt:1. Check Request ID APConfirm.txt:2. Check # APConfirm.txt:3. Settlement Type APConfirm.txt:4. Check Amount APConfirm.txt:5. Currency APConfirm.txt:6. Check Date APConfirm.txt:7. Multiple Payments
Copied file
Fields Referenced APConfirm.txt:1. Check Request ID APConfirm.txt:2. Check # APConfirm.txt:3. Settlement Type APConfirm.txt:4. Check Amount APConfirm.txt:5. Currency APConfirm.txt:6. Check Date APConfirm.txt:7. Multiple Payments
E1 Table
E1 Field
Table Description VCP-ODS 1. Deduction ID 2. Date - Deduction Opened 3. Amount - Deduction 4. Transaction Deduction Amount 5. Transaction Currency Code 6. Display Decimals 7. Document Original 8. Document Type Original 9. Document Pay Item Orig 10. Document Company (Original) 11. Date - Invoice 12. Check Number 13. Receipt Date 14. Check Amount 15. Amount - Foreign Receipt 16. Currency Code - From 17. Display Decimals 18. Default 19. New 20. Deduction 21. Company 22. Address Book
Deductions.txt Deductions.txt Description
Copied file
Logic Deduction.txt: 1. Deduction ID Deduction.txt: 2. Date - Deduction Opened Deduction.txt: 3. Amount - Deduction Deduction.txt: 4. Transaction Deduction Amount Deduction.txt: 5. Transaction Currency Code Deduction.txt: 6. Display Decimals Deduction.txt: 7. Document Original Deduction.txt: 8. Document Type Original Deduction.txt: 9. Document Pay Item Orig Deduction.txt: 10. Document Company (Original) Deduction.txt: 11. Date - Invoice Deduction.txt: 12. Check Number Deduction.txt: 13. Receipt Date Deduction.txt: 14. Check Amount Deduction.txt: 15. Amount - Foreign Receipt Deduction.txt: 16. Currency Code - From Deduction.txt: 17. Display Decimals Deduction.txt: 18. Default Deduction.txt: 19. New Deduction.txt: 20. Deduction Deduction.txt: 21. Company Deduction.txt: 22. Address Book (BILL TO NUMBER NOT FORMATED)
Fields Referenced
E1 Table
MSC_BOM_COMPONENTS This table stores Bill of material data for plans in Oracle Advanced Planning and Oracle Supply Chain Hub products. Description
ing and Oracle Supply Chain Hub products. Logic
Fields Referenced
E1 Table
Table Description File Field Name
Plan Header record

purchasePlan: planName purchasePlan: description purchasePlan: planSource purchasePlan: createdDate purchasePlan: snapshotDate purchasePlan: numberOfPeriods purchasePlan: periodSize
PurchasePlanDetails
select $instance_id$ from MSC_APPS_INSTANCES where instance_code=Parameter.Source_Instance; select plan_id from MSC_PLANS where sr_instance_id=$instance_id$ Retrieve from MSC_SUPPLIES where SR_INSTANCE_ID=$instance_id$ and plan_id=$plan_id$ and order_type=1 and supplier_id is not n msc_supplies.transaction_id= MSC_PO_RESCHEDULE_INTERFACE.SOURCE_LINE_ID
Retrieve from MSC_SUPPLIES where SR_INSTANCE_ID=$instance_id$ and plan_id=$plan_id$ and order_type=5 and supplier_id is not n msc_supplies.transaction_id= MSC_PO_REQUISITIONS_INTERFACE.SOURCE_LINE_ID purchasePlan: purchasePlanDetailList: purchaseOrderRecommendationCode
purchasePlan: purchasePlanDetailList: purchaseOrder purchasePlan: purchasePlanDetailList: lineItem purchasePlan: purchasePlanDetailList: quantity
purchasePlan: purchasePlanDetailList: shipDate purchasePlan: purchasePlanDetailList: arriveDate
purchasePlan: purchasePlanDetailList: supplier
purchasePlan: purchasePlanDetailList: item
purchasePlan: purchasePlanDetailList: receivingBranch
delete from MSC_PO_REQUISITIONS_INTERFACE where in xml) delete from MSC_PO_RESCHEDULE_INTERFACE where S in xml)
PurchasePlan.xml Planned Purchases for publish to E1 VCP to File Mapping Parameter.Publish_Plan_Name (ORCL-APS) Parameter.Publish_Plan_Name (ORCL-APS) "ORCL-APS" Plan_Option.Base_Date (in the format YYYY-MM-DDT00:00:00) Plan_Option.Base_Date (in the format YYYY-MM-DDT00:00:00) <null> <null>
E1 Table
stance_code=Parameter.Source_Instance; tance_id$ tance_id$ and plan_id=$plan_id$ and order_type=1 and supplier_id is not null and RFACE.SOURCE_LINE_ID
tance_id$ and plan_id=$plan_id$ and order_type=5 and supplier_id is not null and ERFACE.SOURCE_LINE_ID
MSC_SUPPLIES:TRANSACTION_ID + field_delimiter + $instance_id$ + field_delimiter + $plan_id$
IF MSC_SUPPLIES.ORDER_TYPE=1 MSC_SUPPLIES:ORDER_NUMBER ELSE (MSC_SUPPLIES.ORDER_TYPE=5) <null> MSC_SUPPLIES:PURCH_LINE_NUM MSC_PO_RESCHEDULE_INTERFACE.QUANTITY/ MSC_PO_REQUISITIONS_INTERFACE. QUANTITY
F3411 F3411 F3411
MAX( MSC_PO_RESCHEDULE_INTERFACE.NEED_BY_DATE/ MSC_PO_REQUISITIONS_INTERFACE.NEED_BY_DATE (supplier.xml:supplier:supplierItem:standardLeadTime + Parameter.Purchased Postprocessing Lead Time) where joined by supplier.xml:supplier:supplierCode (see Supplier record below) and supplier.xml:supplier:supplierItem:branchCode (see branch record below) and supplier.xml:supplier:supplierItem:itemCode (see Item record below) , current date
MAX(MSC_PO_RESCHEDULE_INTERFACE.NEED_BY_DATE ,current date) F3411 F3411
Select PARTNER_NUMBER from MSC_TRADING_PARTNERS where PARTNER_ID = (select tp_id from msc_tp_id_lid where sr_tp_id=msc_po_requisitions_interface.suggested_vendor_id and sr_instance_id==$instance_id$) AND PARTNER_TYPE=1 AND sr_instance_id=$instance_id Select ITEM_NAME from MSC_SYSTEM_ITEMS where MSC_SUPPLIES.INVENTORY_ITEM_ID = MSC_SYSTEM_ITEMS.INVENTORY_ITEM_ID AND MSC_SUPPLIES.ORGANIZATION_ID=MSC_SYSTEM_ITEMS.ORGANIZATION_ID and sr_instance_id=$instance_id and plan_id=$plan_id$ Select Organization_Code from MSC_TRADING_PARTNERS where SR_TP_ID = MSC_SUPPLIES.ORGANIZATION_ID AND PARTNER_TYPE=3 AND sr_instance_id=$instance_id (reverse any translation applied during loading)
F3411
F3411
F3411
delete from MSC_PO_REQUISITIONS_INTERFACE where SOURCE_LINE_ID=(transaction_id used in xml) delete from MSC_PO_RESCHEDULE_INTERFACE where SOURCE_LINE_ID=(transaction_id used in xml)
A concatenation of: DOCO|KCOO|DCTO|SFXO|LNID where F3411.DOCO = DOCO F3411.KCOO = KCOO F3411.DCTO = DCTO F3411.SFXO = SFXO concatenation F3411.LNID = LNID LNID Only for VCP TRQT Changed back to transaction quantity
RSTJ RRQJ
VEND
ITM
MCU
Table Description File Field Name Plan Header record deploymentPlan: planName deploymentPlan: description deploymentPlan: planSource deploymentPlan: createdDate deploymentPlan: snapshotDate deploymentPlan: numberOfPeriods deploymentPlan: periodSize deploymentPlanDetail select $instance_id$ from MSC_APPS_INSTANCES where instance_code=Parameter.Source_Instance;
select plan_id from MSC_PLANS where sr_instance_id=$instance_id$ Retrieve from MSC_SUPPLIES where SR_INSTANCE_ID=$instance_id$ and plan_id=$plan_id$ and ORDER_TYPE=2 and source_organisation_id is NOT NULL and source_org_id <> org_id and msc_supplies.transaction_id= MSC_PO_RESCHEDULE_INTERFACE.SOURCE_LINE_ID Retrieve from MSC_SUPPLIES where SR_INSTANCE_ID=$instance_id$ and plan_id=$plan_id$ and ORDER_TYPE= 5 and source_organisation_id is NOT NULL and source_org_id <> org_id and msc_supplies.transaction_id= MSC_PO_REQUISITIONS_INTERFACE.SOURCE_LINE_ID select MSC_DEMAND_INFO from MSC_DEMANDS where (MSC_DEMANDS.DISPOSITION_ID (+)=MSC_SUPPLIES.TRANSACTION_ID) AND MSC_DEMANDS.INVENTORY_ITEM_ID (+)=MSC_SUPPLIES.INVENTORY_ITEM_ID) AND (MSC_DEMANDS.PLAN_ID (+)=MSC_SUPPLIES.PLAN_ID) AND MSC_DEMANDS.SR_INSTANCE_ID (+)=MSC_SUPPLIES.SR_INSTANCE_ID
deploymentPlan: deploymentPlanDetail: deploymentCode
deploymentPlan: deploymentPlanDetail: originBranchCode
deploymentPlan: deploymentPlanDetail: destinationBranchCode
deploymentPlan: deploymentPlanDetail: itemCode deploymentPlan: deploymentPlanDetail: arriveDate deploymentPlan: deploymentPlanDetail: transportMode
deploymentPlan: deploymentPlanDetail:transferOrderCode deploymentPlan: deploymentPlanDetail: lineItem deploymentPlan: deploymentPlanDetail: earliestShipDate deploymentPlan: deploymentPlanDetail: latestShipDate deploymentPlan: deploymentPlanDetail: earliestArriveDate
deploymentPlan: deploymentPlanDetail: shipDate deploymentPlan: deploymentPlanDetail: latestArriveDate deploymentPlan: deploymentPlanDetail: quantity deploymentPlan: deploymentPlanDetail: fix deploymentPlan: deploymentPlanDetail: pullForward
delete from msc_wip_job_schedule_interface where sou xml) delete from msc_wip_job_dtls_interface where parent_h
DeploymentPlan.xml Planned Transfers for publish to E1 VCP to File Mapping Parameter.Publish_Plan_Name (ORCL-APS) Parameter.Publish_Plan_Name (ORCL-APS) "ORCL-APS" Plan_Option.Base_Date (in the format YYYY-MM-DDT00:00:00) Plan_Option.Base_Date (in the format YYYY-MM-DDT00:00:00) <null> <null>
E1 Table
MSC_SUPPLIES:TRANSACTION_ID + field_delimiter + $instance_id$ + field_delimiter + $plan_id$ Select Organization_Code from MSC_TRADING_PARTNERS where SR_TP_ID= MSC_SUPPLIES.SOURCE_ORGANIZATION_ID AND PARTNER_TYPE=3 AND sr_instance_id=$instance_id$ (reverse any translation applied during loading)
F3411
F3411
Select Organization_Code from MSC_TRADING_PARTNERS where SR_TP_ID= MSC_SUPPLIES.ORGANIZATION_ID AND PARTNER_TYPE=3 AND sr_instance_id=$instance_id (reverse any translation applied during loading) Item using msc_system_items.item_name where msc_supplies:inventory_item_id=msc_system_items.inventory_item_id AND PARTNER_TYPE=3 AND sr_instance_id=$instance_id and plan_id=$plan_id$ and MSC_SUPPLIES.ORGANIZATION_ID=MSC_SYSTEM_ITEMS.ORGANIZATION_ID MAX(MSC_PO_RESCHEDULE_INTERFACE.NEED_BY_DATE/ MSC_PO_REQUISITIONS_INTERFACE.NEED_BY_DATE,current_date) MSC_SUPPLIES:SHIP_METHOD
F3411
F3411 F3411
IF MSC_SUPPLIES.ORDER_TYPE=2 MSC_SUPPLIES:ORDER_NUMBER ELSE (MSC_SUPPLIES.ORDER_TYPE=5) <null> MSC_SUPPLIES.PURCH_LINE_NUMBER? <null> <null> MAX(MSC_SUPPLIES:NEW_SCHEDULED_DATE,current_date) nvl(msc_demands.implement_ship_date,msc_demands.planned_ship_date) We should still use nvl(using_assembly_demand_date,sysdate) if msc_demands.planned_ship_date is null. MAX(MSC_PO_RESCHEDULE_INTERFACE.NEED_BY_DATE/ MSC_PO_REQUISITIONS_INTERFACE.NEED_BY_DATE,current_date) MSC_PO_RESCHEDULE_INTERFACE.QUANTITY/ MSC_PO_REQUISITIONS_INTERFACE. QUANTITY MSC_SUPPLIES:FIRM_PLANNED_TYPE = 1 then set to "Yes" otherwise "No" "0"
F3411 F3411
F3411
F3411 F3411
delete from msc_wip_job_schedule_interface where source_line_id=(transaction ids used in xml) delete from msc_wip_job_dtls_interface where parent_header_id=(transaction_id used in xml)
A concatenation of: DOCO|KCOO|DCTO|SFXO|LNID where F3411.DOCO = DOCO F3411.KCOO = KCOO F3411.DCTO = DCTO F3411.SFXO = SFXO F3411.LNID = LNID
MMCU
MCU
ITM RRQJ A concatenation of: DOCO|KCOO|DCTO|SFXO|LNID where F3411.DOCO = DOCO F3411.KCOO = KCOO F3411.DCTO = DCTO F3411.SFXO = SFXO concatenation F3411.LNID = LNID LNID
RSTJ
TRQT HCLD
Changed back to transaction quantity Hard coded X
Plan Header record

deploymentPlan: planName deploymentPlan: description deploymentPlan: planSource deploymentPlan: createdDate deploymentPlan: snapshotDate deploymentPlan: numberOfPeriods deploymentPlan: periodSize
deploymentPlanDetail
select $instance_id$ from MSC_APPS_INSTANCES where instance_code=Parameter.Source_Instance;
select plan_id from MSC_PLANS where sr_instance_id=$instance_id$ Retrieve from MSC_SUPPLIES where SR_INSTANCE_ID=$instance_id$ and plan_id=$plan_id$ and ORDER_TYPE in(2,51) and source_organisation_id is NOT NULL and source_org_id <> org_id and msc_supplies.transaction_id= MSC_PO_RESCHEDULE_INTERFACE.SOURCE_LINE_ID Retreive from mrp_org_transfer_release where TRANSACTION_ID = MSC_SUPPLIES.TRANSACTION_ID and TO_SR_INSTANCE_ID = $instance_id$
deploymentPlan: deploymentPlanDetail: deploymentCode
deploymentPlan: deploymentPlanDetail: originBranchCode
deploymentPlan: deploymentPlanDetail: destinationBranchCode
deploymentPlan: deploymentPlanDetail: itemCode deploymentPlan: deploymentPlanDetail: arriveDate deploymentPlan: deploymentPlanDetail: transportMode
deploymentPlan: deploymentPlanDetail:transferOrderCode deploymentPlan: deploymentPlanDetail: lineItem deploymentPlan: deploymentPlanDetail: earliestShipDate deploymentPlan: deploymentPlanDetail: latestShipDate deploymentPlan: deploymentPlanDetail: earliestArriveDate deploymentPlan: deploymentPlanDetail: shipDate deploymentPlan: deploymentPlanDetail: latestArriveDate deploymentPlan: deploymentPlanDetail: quantity deploymentPlan: deploymentPlanDetail: fix deploymentPlan: deploymentPlanDetail: pullForward
delete from mrp_org_transfer_release where TRANSACT
DeploymentPlan.xml Planned Deployments for publish to E1 from DRP VCP to File Mapping Parameter.Publish_Plan_Name (ORCL-APS) Parameter.Publish_Plan_Name (ORCL-APS) "ORCL-DRP" Plan_Option.Base_Date (in the format YYYY-MM-DDT00:00:00) Plan_Option.Base_Date (in the format YYYY-MM-DDT00:00:00) <null> <null>
E1 Table
MSC_SUPPLIES:TRANSACTION_ID + field_delimiter + $instance_id$ + field_delimiter + $plan_id$ F3411 Select Organization_Code from MSC_TRADING_PARTNERS where SR_TP_ID=NVL(MRP_ORG_TRANSFER_RELEASE.SRC_ORGANIZATION_ID,MSC_SUPPLIES.SOURCE_OR GANIZATION_ID) AND PARTNER_TYPE=3 AND sr_instance_id=$instance_id$ (reverse any translation applied during loading) F3411 Select Organization_Code from MSC_TRADING_PARTNERS where SR_TP_ID= mrp_org_transfer_release.TO_ORGANIZATION_ID AND PARTNER_TYPE=3 AND sr_instance_id=$instance_id (reverse any translation applied during loading) F3411
msc_system_items.item_name where mrp_org_transfer_release:item_id=msc_system_items.SR_inventory_item_id AND sr_instance_id=$instance_id and plan_id=$plan_id$ and mrp_org_transfer_release.TO_ORGANIZATION_ID=MSC_SYSTEM_ITEMS.ORGANIZATION_ID
mrp_org_transfer_release.need_by_date
mrp_org_transfer_release:SHIP_METHOD
F3411 F3411
IF MSC_SUPPLIES.ORDER_TYPE=2 MSC_SUPPLIES:ORDER_NUMBER ELSE (MSC_SUPPLIES.ORDER_TYPE=51) <null> MSC_SUPPLIES.PURCH_LINE_NUM
F3411 F3411
mrp_org_transfer_release:EARLIEST_SHIP_DATE
<null> MAX(mrp_org_transfer_release:NEED_BY_DATE ,current_date) MAX(mrp_org_transfer_release:ship_date,current_date) MAX(mrp_org_transfer_release:ship_date,current_date) mrp_org_transfer_release: QUANTITY MSC_SUPPLIES:FIRM_PLANNED_TYPE = 1 then set to "Yes" otherwise "No" "0"
F3411 F3411 F3411
delete from mrp_org_transfer_release where TRANSACTION_ID=(transaction_id used in xml)
A concatenation of: DOCO|KCOO|DCTO|SFXO|LNID where F3411.DOCO = DOCO F3411.KCOO = KCOO F3411.DCTO = DCTO F3411.SFXO = SFXO F3411.LNID = LNID
MMCU
MCU
ITM RRQJ A concatenation of: DOCO|KCOO|DCTO|SFXO|LNID where F3411.DOCO = DOCO F3411.KCOO = KCOO F3411.DCTO = DCTO F3411.SFXO = SFXO concatenation F3411.LNID = LNID LNID
RSTJ TRQT HCLD Changed back to transaction quantity Hard coded X
Plan Header record

detailedProductionPlan: productionScheduleCode detailedProductionPlan: description detailedProductionPlan: createdDate detailedProductionPlan: source detailedProductionPlan: planningPeriodStartDate detailedProductionPlan: planningPeriodEndDate detailedProductionPlan: planningHorizonLength detailedProductionPlan: horizonUnits
routingInstance
select $instance_id$ from MSC_APPS_INSTANCES where instance_code=Parameter.Source_Instance; select plan_id from MSC_PLANS where sr_instance_id=$instance_id$ select $plan_type$ from msc_plans where plan_id=$plan_id$ and sr_instance_id=$instance_id$
Retrieve from MSC_SUPPLIES where SR_INSTANCE_ID=$instance_id$ and plan_id=$plan_id$ and ORDER_TYPE=5,3, AND and supplier_id is null and (MSC_SUPPLIES.ORGANIZATION_ID=nvl(MSC_SUPPLIES.source_organization_id,MSC_SUPPLIES.organiz AND nvl("DISPOSITION_STATUS_TYPE",9999) in MSC_SUPPLIES <> 2 And (MSC_SUPPLIES.TRANSACTION_ID=(select MSC_WIP_JOB_SCHEDULE_INTERFACE.SOURCE_LINE_ID from MSC_WIP_JOB_SCHEDULE Discard records with ChangesAllowed="No" in WorkOrder.xml where MSC_SUPPLIES:ORDER_NUMBER=WorkOrders.xml:workOrder:w
detailedProductionPlan: routingInstance: routingInstanceCode
detailedProductionPlan: routingInstance: branch
detailedProductionPlan: routingInstance: externalId
detailedProductionPlan: routingInstance: routing
routingInstance : operationInstance
Find the operations against a planned order by
finding routing_sequence_id, operation_sequence_id from MSC_RESOURCE_REQUIREMENTS where SR_INSTANCE_ID=$instance_id$ and plan_id=$plan_id and transaction_id = MSC_SUPPLIES.Transaction_id group by routing_sequence_id, operation_sequence_id
find static operation_information using select xxx from MSC_ROUTING_OPERATIONS WHERE SR_INSTANCE_ID=$instance_id$ and plan_id=$plan_id$ and routing_sequence_id=msc_supplies.routing_sequence_id and ope find scheduled operation_information using select xxx from MSC_RESOURCE_REQUIREMENTS WHERE SR_INSTANCE_ID=$instance_id$ and plan_id=$plan_id$ and supply_id = MSC_SUPPLIES.Transaction_id and parent_id=2 GROUP BY supply_id, operation_sequence_id, operation_sequence_num, resource_id then join with msc_operation_resources and only use resource where SR_INSTANCE_ID=$instance_id$ and principal_flag=1 and MSC_ find duration_information using select xxx from MSC_RESOURCE_REQUIREMENTS , MSC_OPERATION_RESOURCES WHERE SR_INSTANCE_ID=$instance_id$ and plan_id=$plan_id$ and <get join info from Rahul> and MSC_OPERATION_RESOURCES.PRINCIPAL_FLAG=1 and resource = resource in this work order operation Please modify the queries according to this: select MSC_RESOURCE_REQUIREMENTS.FIRM_FLAG,MSC_ROUTING_OPERATIONS.OPERATION_DESCRIPTION,MS C_RESOURCE_REQUIREMENTS.RESOURCE_HOURS,MSC_RESOURCE_REQUIREMENTS.END_DATE,MSC_RES OURCE_REQUIREMENTS.START_DATE,MSC_ROUTING_OPERATIONS.OPERATION_SEQ_NUM, MSC_RESOURCE_REQUIREMENTS.ROUTING_SEQUENCE_ID,MSC_RESOURCE_REQUIREMENTS.OPERATION _SEQUENCE_ID, MSC_ROUTING_OPERATIONS.UOM_CODE from MSC.MSC_RESOURCE_REQUIREMENTS MSC_RESOURCE_REQUIREMENTS, MSC.MSC_OPERATION_RESOURCES MSC_OPERATION_RESOURCES, MSC.MSC_SUPPLIES MSC_SUPPLIES, MSC.MSC_ROUTING_OPERATIONS MSC_ROUTING_OPERATIONS where (1=1) And (MSC_SUPPLIES.PLAN_ID=$plan_id$) And (MSC_SUPPLIES.SUPPLIER_ID is null) And (MSC_SUPPLIES.ORDER_TYPE in(5,3)) And (MSC_RESOURCE_REQUIREMENTS.PARENT_ID=2) And (MSC_SUPPLIES.SR_INSTANCE_ID=$sr_instance_id$) And (MSC_SUPPLIES.ORGANIZATION_ID=nvl(MSC_SUPPLIES.source_organization_id,MSC_SUPPLIES.organizatio n_id) ) And (MSC_OPERATION_RESOURCES.PRINCIPAL_FLAG=1) And ((MSC_SUPPLIES.SR_INSTANCE_ID=MSC_ROUTING_OPERATIONS.SR_INSTANCE_ID) AND MSC_ROUTING_OPERATIONS.PLAN_ID=decode($plan_type$,7,-1,MSC_SUPPLIES.PLAN_ID)) AND (((MSC_RESOURCE_REQUIREMENTS.ROUTING_SEQUENCE_ID=MSC_OPERATION_RESOURCES.ROUTING_SE QUENCE_ID) AND MSC_RESOURCE_REQUIREMENTS.OPERATION_SEQUENCE_ID=MSC_OPERATION_RESOURCES.OPERATION _SEQUENCE_ID) AND MSC_RESOURCE_REQUIREMENTS.RESOURCE_ID=MSC_OPERATION_RESOURCES.RESOURCE_ID) AND (((MSC_SUPPLIES.TRANSACTION_ID=MSC_RESOURCE_REQUIREMENTS.SUPPLY_ID) AND MSC_SUPPLIES.SR_INSTANCE_ID=MSC_RESOURCE_REQUIREMENTS.SR_INSTANCE_ID) AND MSC_SUPPLIES.PLAN_ID=MSC_RESOURCE_REQUIREMENTS.PLAN_ID)
detailedProductionPlan: routingInstance: operationInstance: operationInstanceCode detailedProductionPlan: routingInstance: operationInstance: routingInstance detailedProductionPlan: routingInstance: operationInstance: operationSet
detailedProductionPlan: routingInstance: operationInstance: operation detailedProductionPlan: routingInstance: operationInstance: scheduledStartTime detailedProductionPlan: routingInstance: operationInstance: scheduledEndTime detailedProductionPlan: routingInstance: operationInstance: earliestStartTime detailedProductionPlan: routingInstance: operationInstance: latestEndTime detailedProductionPlan: routingInstance: operationInstance: runTime detailedProductionPlan: routingInstance: operationInstance: elapsedTime detailedProductionPlan: routingInstance: operationInstance: delayTime detailedProductionPlan: routingInstance: operationInstance: timeUom
detailedProductionPlan: routingInstance: operationInstance: fixed
find scheduled operation_information using select xxx from MSC_RESOURCE_REQUIREMENTS WHERE SR_INSTANCE_ID=$instance_id$ and plan_id=$plan_id$ and supply_id = MSC_SUPPLIES.Transaction_id and parent_id=2 And operation_sequence_id=(operation_sequence_id from operationInstance above) and routing_sequence_id=(routing_sequence_id
routingInstance: operationInstance: operationInstanceResource
detailedProductionPlan: routingInstance: operationInstance: operationInstanceResource: resourceSet
detailedProductionPlan: routingInstance: operationInstance: operationInstanceResource: resourceCode detailedProductionPlan: routingInstance: operationInstance: operationInstanceResource: scheduledStartTime detailedProductionPlan: routingInstance: operationInstance: operationInstanceResource: scheduledEndTime detailedProductionPlan: routingInstance: operationInstance: operationInstanceResource: earliestStartTime detailedProductionPlan: routingInstance: operationInstance: operationInstanceResource: latestEndTime detailedProductionPlan: routingInstance: operationInstance: operationInstanceResource: runTime detailedProductionPlan: routingInstance: operationInstance: operationInstanceResource: elapsedTime detailedProductionPlan: routingInstance: operationInstance: operationInstanceResource: delayTime detailedProductionPlan: routingInstance: operationInstance: operationInstanceResource: timeUom
detailedProductionPlan: routingInstance: operationInstance: operationInstanceResource: resourceType
detailedProductionPlan: routingInstance: operationInstance: operationInstanceProducedItem
detailedProductionPlan: routingInstance: operationInstance: operationInstanceProducedItem: item detailedProductionPlan: routingInstance: operationInstance: operationInstanceProducedItem: netQuantity detailedProductionPlan: routingInstance: operationInstance: operationInstanceProducedItem: isPrimaryItem
detailedProductionPlan: routingInstance: operationInstance: operationInstanceConsumedItem: consumedItemSet

select consumed_item_info from MSC_DEMANDS where disposition_id = MSC_SUPPLIES:transaction_id and sR_INSTANCE_ID=$instance_id$ and plan_id = $plan_id$
detailedProductionPlan: routingInstance: operationInstance: operationInstanceConsumedItem: consumedItemSet
detailedProductionPlan: routingInstance: operationInstance: operationInstanceConsumedItem: item detailedProductionPlan: routingInstance: operationInstance: operationInstanceConsumedItem: netQuantity
delete from msc_wip_job_schedule_interface where sou delete from msc_wip_job_dtls_interface where parent_ ProducedItem to be generated under max operation(bas operation_seq_num
note: This works while E1 only supports one operation p
DetailedProductionPlan.xml Work Order Creations and Updates messages VCP to File Mapping Parameter.Publish_Plan_Name (ORCL-APS) Parameter.Publish_Plan_Name (ORCL-APS) Plan_Option.Base_Date (in the format YYYY-MM-DDT00:00:00) "ORCL-APS" Plan_Option.Base_Date (in the format YYYY-MM-DDT00:00:00) Plan_Option.Base_Date (in the format YYYY-MM-DDT00:00:00) + Parameters.Effective_to_Date_Offset Parameters.Effective_to_Date_Offset "Days"
$ and ORDER_TYPE=5,3, ce_organization_id,MSC_SUPPLIES.organization_id) )
CE_LINE_ID from MSC_WIP_JOB_SCHEDULE_INTERFACE for max last_update_date) R_NUMBER=WorkOrders.xml:workOrder:workOrderCode
MSC_SUPPLIES:TRANSACTION_ID + field_delimiter + $instance_id$ + field_delimiter + $plan_id$ Select organization_code from MSC_TRADING_PARTNERS where SR_TP_ID= MSC_SUPPLIES.ORGANIZATION_ID AND PARTNER_TYPE=3 AND sr_instance_id=$instance_id$ (reverse any translation applied during loading) IF MSC_SUPPLIES.ORDER_TYPE=3 decode($plan_type$,7,MSC_WIP_JOB_SCHEDULE_INTERFACE.JOB_NAME,MSC_SUPPLIES.ORDER_N UMBER) ELSE (MSC_SUPPLIES.ORDER_TYPE=5) <null> select ROUTING_COMMENT FROM MSC_ROUTING where MSC_ROUTING.ROUTING_SEQUENCE_ID = MSC_SUPPLIES.ROUTING_SEQUENCE_ID and sr_instance_id=$instance_id$ and plan_id= decode($plan_type$,7,-1,MSC_SUPPLIES.PLAN_ID)
msc_supplies.routing_sequence_id and operation_sequence_id=$operation_sequence_id$ TS LIES.Transaction_id and parent_id=2
stance_id$ and principal_flag=1 and MSC_RESOURCE_REQUIREMENTS.RESOURCE_ID = PERATION_RESOURCES ul> order operation
MSC_SUPPLIES:TRANSACTION_ID + Parameter.Field_Delimiter + MSC_ROUTING_OPERATIONS.OPERATION_SEQ_NUM <not in file> MSC_ROUTING_OPERATIONS.OPERATION_DESCRIPTION
MSC_ROUTING_OPERATIONS.OPERATION_DESCRIPTION duration_information.MSC_RESOURCE_REQUIREMENTS.START_DATE duration_information.MSC_RESOURCE_REQUIREMENTS.END_DATE duration_information.MSC_RESOURCE_REQUIREMENTS.EARLIEST_START_DATE <null> duration_information.MSC_RESOURCE_REQUIREMENTS.runTime <null> <null> MSC_ROUTING_OPERATIONS. UOM_CODE (reverse any translation applied during loading) Firming the operation based on the information at the supply level, if msc_supplies.firm_planned_type=1, firm the operation else check for the resources for a given operation and firm it, if any of the resource is firm,(if msc_resource_requirements.firm_flag is other that null or 0), firm that particular Operation
TS LIES.Transaction_id and parent_id=2 outing_sequence_id=(routing_sequence_id from operationInstance above)
Check if this now being stored in integration translation file get from manufacturing.xml:operation:resourceSet:resourceSetCode where operation= MSC_ROUTING_OPERATIONS.OPERATION_DESCRIPTION and resourceCode=detailedProductionPlan: routingInstance: operationInstance: operationInstanceResource: resourceCode (NEXT field) and sr_instance_id=$instance_id and plan_id=$plan_id$ MSC_DEPARTMENT_RESOURCES.RESOURCE_CODE WHERE sr_instance_id=$instance_id and plan_id=$plan_id$ and $scheduled_operation_information.RESOURCE_ID$=MSC_DEPARTMENT_RESOURCES.RESOURCE_ID detailedProductionPlan: routingInstance: operationInstance: scheduledStartTime detailedProductionPlan: routingInstance: operationInstance: scheduledEndTime <null> <null> MSC_RESOURCE_REQUIREMENT:RESOURCE_HOURS <null> <null> detailedProductionPlan: routingInstance: operationInstance: timeUom (reverse any translation applied during loading)
MSC_DEPARTMENT_RESOURCES.RESOURCE_TYPE WHERE sr_instance_id=$instance_id scheduled_resource_information.RESOURCE_ID=MSC_DEPARTMENT_RESOURCES.RESOURCE_ID And (MSC_RESOURCE_REQUIREMENTS.DEPARTMENT_ID=MSC_DEPARTMENT_RESOURCES.DEPARTMEN T_ID) AND MSC_RESOURCE_REQUIREMENTS.RESOURCE_ID=MSC_DEPARTMENT_RESOURCES.RESOURCE_ID) AND MSC_RESOURCE_REQUIREMENTS.ORGANIZATION_ID=MSC_DEPARTMENT_RESOURCES.ORGANIZAT ION_ID) AND (MSC_DEPARTMENT_RESOURCES.PLAN_ID=decode($plan_type$,7,-1,MSC_SUPPLIES.PLAN_ID)) If resource_type=1, "Machine", 2="Crew", 4="Tool"
msc_system_items.item_name where msc_supplies:inventory_item_id=msc_system_items.inventory_item_id and sr_instance_id=$instance_id and plan_id=$plan_id$ MSC_SYSTEM_ITEMS.PLAN_ID=decode($plan_type$,7,-1,MSC_SUPPLIES.PLAN_ID) AND MSC_SUPPLIES.ORGANIZATION_ID=MSC_SYSTEM_ITEMS.ORGANIZATION_ID msc_supplies:new_order_quantity "Yes"
Check if this now being stored in integration translation file get from manufacturing.xml:operation:consumedItemSet:consumedItemSetCode where operation= MSC_ROUTING_OPERATIONS.OPERATION_DESCRIPTION and itemCode=detailedProductionPlan: routingInstance: operationInstance: operationInstanceConsumedItem: item (NEXT FIELD) and and manufacturing.xml:operation:consumedItemSet:consumedItemSet:branchCode= detailedProductionPlan: routingInstance: branch and sr_instance_id=$instance_id and plan_id=$plan_id$ msc_system_items.item_name where MSC_DEMANDS:INVENTORY_ITEM_ID=msc_system_items.inventory_item_id sr_instance_id=$instance_id and plan_id=$plan_id$ MSC_DEMANDS: using_Requirement_qty
_wip_job_schedule_interface where source_line_id=(transaction ids used in xml) _wip_job_dtls_interface where parent_header_id=(transaction_id used in xml) be generated under max operation(based on operation_seq_num) for each routing ConsumedItem linked to an operation based on
while E1 only supports one operation per operationSet AND does not support alternate materials
E1 Mapping
E1 Table
E1 Field
branchCode
externalId
routingCode
operationCode scheduledStartTime scheduledEndTime
resourceCode scheduledStartTime scheduledEndTime
runTime
timeUom
resourceType
itemCode netQuantity
itemCode netQuantity
medItem linked to an operation based on
Table Description File Field Name masterProductionPlan: planName masterProductionPlan: description masterProductionPlan: planSource masterProductionPlan: createdDate masterProductionPlan: snapshotDate masterProductionPlan: numberOfPeriods masterProductionPlan: periodSize select $instance_id$ from MSC_APPS_INSTANCES where instance_code=Parameter.Source_Instance; select plan_id from MSC_PLANS where sr_instance_id=$instance_id$ Retrieve from MSC_SUPPLIES where SR_INSTANCE_ID=$instance_id$ and plan_id=$plan_id$ and ORDER_TYPE=3, AND and supplier_id is null and (MSC_SUPPLIES.ORGANIZATION_ID=nvl(MSC_SUPPLIES.source_organization_id,MSC_SUPPLIES. organization_id) AND "DISPOSITION_STATUS_TYPE" in MSC_SUPPLIES = 2 and MSC_SUPPLIES:ORDER_NUMBER is not NULL And (MSC_WIP_JOB_SCHEDULE_INTERFACE.SOURCE_LINE_ID=MSC_SUPPLIES.TRANSACTION_ID) Discard records with ChangesAllowed="No" in WorkOrder.xml where MSC_SUPPLIES:ORDER_NUMBER=WorkOrders.xml:workOrder:workOrderCode
masterProductionPlan: masterProductionPlanDetail: netProdReqCode
masterProductionPlan: masterProductionPlanDetail: branchCode
masterProductionPlan: masterProductionPlanDetail: item masterProductionPlan: masterProductionPlanDetail: requestedDate masterProductionPlan: masterProductionPlanDetail: quantity masterProductionPlan: masterProductionPlanDetail: earliestProductionDate masterProductionPlan: masterProductionPlanDetail: latestProductionDate masterProductionPlan: masterProductionPlanDetail: status masterProductionPlan: masterProductionPlanDetail: fix masterProductionPlan: masterProductionPlanDetail: workOrderCode
masterProductionPlan: masterProductionPlanDetail: routingCode
delete from msc_wip_job_schedule_interface where sou delete from msc_wip_job_dtls_interface where parent_
This is created for all records in MSC_SUPPLIES with a ca
MasterProductionPlan.xml Work Order deletion messages VCP to File Mapping Parameter.Publish_Plan_Name (ORCL-APS) Parameter.Publish_Plan_Name (ORCL-APS) "ORCL-APS" Plan_Option.Base_Date (in the format YYYY-MM-DDT00:00:00) Plan_Option.Base_Date (in the format YYYY-MM-DDT00:00:00) <null> "Days"
E1 Table
E1 Field
MSC_SUPPLIES:TRANSACTION_ID + field_delimiter + $instance_id$ + field_delimiter + $plan_id$ Select organization_code from MSC_TRADING_PARTNERS where SR_TP_ID = MSC_SUPPLIES.ORGANIZATION_ID AND PARTNER_TYPE=3 AND sr_instance_id=$instance_id$ (reverse any translation applied during loading) msc_system_items.item_name where msc_supplies:inventory_item_id=msc_system_items.inventory_item_id and sr_instance_id=$instance_id and plan_id=$plan_id$ AND MSC_SUPPLIES.ORGANIZATION_ID=MSC_SYSTEM_ITEMS.ORGANIZATION_ID MSC_SUPPLIES:NEW_SCHEDULE_DATE "0" <null> <null> "Rejected" "No" MSC_SUPPLIES:ORDER_NUMBER select ROUTING_COMMENT FROM MSC_ROUTING where MSC_ROUTING.ROUTING_SEQUENCE_ID = MSC_SUPPLIES.ROUTING_SEQUENCE_ID and sr_instance_id=$instance_id$ and plan_id=$plan_id$
F3411
DOCO
F3411 F3411
ITM RRQJ
F3411
DOCO
rom msc_wip_job_schedule_interface where source_line_id=(transaction ids used in xml) rom msc_wip_job_dtls_interface where parent_header_id=(transaction_id used in xml)
reated for all records in MSC_SUPPLIES with a cancel message
Table Description File Field Name 1. Short Item Number 2. Branch/Plant 3. Unknown 4. Sales Date
5. Customer Number 6. Final Forecast
Just the Customer information needs updating
Forecast_Updated.txt Forecast to be uploaded into E1/PSFT VCP to File Mapping tem using Forecast.txt: 1. Short Item Number Forecast.txt: 2. Branch/Plant Forecast.txt: 3. Unknown Forecast.txt: 4. Sales Date take the fifth field of "Forecast.txt: 5. Customer Number" delimited by Parameter.Demantra Field Delimiter THEN using the result take the first field delimited by Parameter.Field Delimiter Forecast.txt: 6. Final Forecast
E1 Table F3460 F3460 F3460
E1 Field ITM MCU DRQJ
F3460 F3460
AN8 UORG FQT
Table Description File Field Name 1. Promotion Row Id 2. Promotion Name
3. Customer Number 4. Customer Number Description 5. Short Item Number 6. Item Number Description 7. Promotion Effective Date 8. Promotion Expiration Date 9. Promotion Amount 10. Cost Type
PromotionPricing_updated Updates to Promotion Pricing VCP to File Mapping PromotionPricing.txt: 1. Promotion Row Id PromotionPricing.txt: 2. Promotion Name take the third field of "PromotionPricing.txt: 3. Customer Number" delimited by Parameter.Demantra Field Delimiter THEN using the result take the first field delimited by Parameter.Field Delimiter PromotionPricing.txt: 4. Customer Number Description (SHIP TO) PromotionPricing.txt: 5. Short Item Number PromotionPricing.txt: 6. Item Number Description PromotionPricing.txt: 7. Promotion Effective Date PromotionPricing.txt: 8. Promotion Expiration Date PromotionPricing.txt: 9. Promotion Amount PromotionPricing.txt: 10. Cost Type
E1 Table
E1 Field
Table Description File Field Name 1. Promotion Row Id 2. Promotion Name 3. Customer Number 4. Customer Number Description 5. Short Item Number 6. Item Number Description 7. Promotion Effective Date 8. Promotion Expiration Date 9. Promotion Amount 10. Cost Type
Delete_PromotionPricing_Updated Deletes to Promotion Pricing VCP to File Mapping Delete_PromotionPricing.txt: 1. Promotion Row Id Delete_PromotionPricing.txt: 2. Promotion Name Delete_PromotionPricing.txt: 3. Customer Number Delete_PromotionPricing.txt: 4. Customer Number Description Delete_PromotionPricing.txt: 5. Short Item Number Delete_PromotionPricing.txt: 6. Item Number Description Delete_PromotionPricing.txt: 7. Promotion Effective Date Delete_PromotionPricing.txt: 8. Promotion Expiration Date Delete_PromotionPricing.txt: 9. Promotion Amount Delete_PromotionPricing.txt: 10. Cost Type
E1 Table
E1 Field
Table Description File Field Name 1. E1 Deduction Id 2. Settlement Amount 3. Settlement Amount (Native Currency) 4. Deduction Reason Code 5. Status (Approved / Denied)
DeductionDisposition_updated Deduction Disposition VCP to File Mapping Delete_PromotionPricing.txt : 1. E1 Deduction Id Delete_PromotionPricing.txt : 2. Settlement Amount Delete_PromotionPricing.txt : 3. Settlement Amount (Native Currency) Delete_PromotionPricing.txt : 4. Deduction Reason Code Delete_PromotionPricing.txt : 5. Status (Approved / Denied)
E1 Table
E1 Field
Table Description File Field Name 1. Check Request ID 2. Customer / Account 3. Claim Invoice # 4. Claim Invoice Date 5. Settlement Date of Origin 6. Settlement Amount (Base Currency) 7. Settlement Amount (Native Currency) 8. Transaction Currency Code
Delete_PromotionPricing_Updated Deletes to Promotion Pricing VCP to File Mapping E1 Table Claim.txt: 1. Check Request ID Claim.txt: 2. Customer / Account (UNFORMATTED BILL TO NUMBER WITHOUT COMPANY NUMBER) Claim.txt: 3. Claim Invoice # Claim.txt: 4. Claim Invoice Date Claim.txt: 5. Settlement Date of Origin Claim.txt: 6. Settlement Amount (Base Currency) Claim.txt: 7. Settlement Amount (Native Currency) Claim.txt: 8. Transaction Currency Code
E1 Field
Company code can be set to "0000"
XML Field Name

itemCode itemName alternateItemId description
XML Object E1 Database Table E1 Database Field Name

item item item item
Notes
Key
Missing in E1
All items per data selection based on the V4101APS (F4101 joined to F4102 by ITM) business view F4101 ITM y F4101 LITM F4101 AITM F4101 DSC1
planningUom
item
F34A10
assignment
CMUM is retrieved from F34A10 where F34A10.SY = '34A' assignment = if F34A10.CMUM = '01', then planningUom = F4101. UOM1 if F34A10.CMUM = '02', then planningUom = F4101.UOM2 if F34A10.CMUM = '03', then planningUom = F4101.UOM3 if F34A10.CMUM = '04', then planningUom = F4101.UOM4 if F34A10.CMUM = '05', then planningUom = F4101.UOM6 if F34A10.CMUM = '06', then planningUom = F4101.UOM8 if F34A10.CMUM = '07', then planningUom = F4101.UOM9 if F34A10.CMUM = '08', then planningUom = F4101.UWUM if F34A10.CMUM = '09', then planningUom = F4101.UVM1 SVUM is retrieved from F34A10 where F34A10.SY = '34A' assignment = same logic as planningUom except that F34A10.SVUM is used for comparison y
shippingUom item F34A10 assignment weightUom item F4101 UWUM volume item volumeUom item F4101 UVM1 roundToWholeNumbers item F4101 SNS All the standard UOM conversions from the V41003A (small subset of fields from F41003) business view This section has been taken out since the data is defined in itemUom toUom standardUom fromUom unitType factor standardUom standardUom standardUom
y y
y y y y
All item specific UOM conversions from the V41002A (subset of fields from F41002) business view for items selected per data selection based on V4101APS itemCode itemUom F41002 ITM assignment = if F41002.UM = planningUom (value assigned in the item Object), then toUom = F41002.RUM else toUom = F41002.UM From = X To = Y Factor = C if (X = planning UOM) ToUom = Y and factor = C else (toUom = X and Factor = 1/C) assignment = same logic as unitType from standardUom Object
toUom toUomType
itemUom itemUom
F41002 F34A30
assignment assignment
assignment = if F41002.UM = planningUom (value assigned in the item Object), then factor = the inversion of F41002.CONV else factor = F41002.CONV where F41002.UM = planningUom factor itemUom F41002 assignment All items selected per data selection based on V4101APS grouped together by the item category codes from F4101 Category code groups will be created only if the F4101 category code is set up in the F34A40 table (the corresponding F34A40 category code field = '1') possible category code groups = SRP1, SRP2, SRP3, SRP4, SRP5, SRP6, SRP7, SRP8, SRP9, SRP0, CARS, CARP, PRP1, PRP2, PRP3, PRP4, PRP5, PRP6, PRP7, PRP8, PRP9, PRP0, SHCN, SHCM, CYCL y if F4101.CARS or F4101.CARP, then description = F0101.ALPH else description = category code value description
name
itemGroup
F4101
category code value
description itemGroup F0005 DL01 members type="members" itemGroup heading all items who share the category code value itemCode itemGroup F4101 ITM All business units from F41001 for branches processed from the data selection from the F4102 business view branchCode branch F41001 MCU y DL01 is retrieved from F0006 where F0006.MCU = F41001.MCU branchName branch F0006 DL01 alternateBranchId branch F41001 AN8 branchType branch uses F0006.DL01 fetched for branchName description branch F0006 DL01
city stateProvince country postalCode latitude longitude shippingCalendar receivingCalendar
branch branch branch branch branch branch branch branch
F0116 F0116 F0116 F0116
CTY1 ADDS CTR ADDZ
all values from F0116 are fetched where F0116.AN8 = F41001.AN8 and F0116.EFTB = F0101.EFTB (F0101.EFTB was retrieved where F0101.AN8 = F41001.AN8)
y y y y
All locations from F4100 where F4100.MCU = the current MCU being processed by the branch Object storageName storage F4100 LOCN branchCode storage storageType storage F4100 STY1 DL01 is retrieved from F0005 where F0005.SY = '46' and F0005.RT = 'LD' and F0005.KY = F4100.STY1 description storage F0005 DL01 values from F41001 are fetched where F41001.MCU = F4100.MCU and F41001.SY = ' ' today's date is enclosed in ' ' values from F46022 are fetched where F46022.MCU = F4100.MCU and F46022.STY1 = F4100.STY1
y y
storageWeightUnit storageVolumeUnit timeVaryingEvent effectiveDate =' '
storage storage storage
F41001 F41001
UWUM VUMD
storageVolumeCapacity storage F46022 UCUB storageWeightCapacity storage F46022 MAXW All items from F41021 where F41021.MCU and F41021.LOCN = MCU and LOCN from storage Object itemCode itemStorage F41021 ITM y storageName itemStorage y today's date is enclosed in ' ' timeVaryingEvent effectiveDate =' ' itemStorage heading storageCostTime itemStorage storageCostTimeUnit itemStorage storageCost itemStorage if F41021.PBIN = 'P', then preference = "1" if F41021.PBIN = 'S', then preference = "2" preference itemStorage F41021 assignment All branches selected per data selection based on V4101APS grouped together by the branch category codes from F0006 Category code groups will be created only if the F0006 category code is set up in the F34A40 table (the corresponding F34A40 category code field = '1')
y y y y y
name branchGroup F0006 category code value description branchGroup F0005 DL01 members type="members" branchGroup heading branchCode branchGroup F0006 MCU All item branch records selected per data selection based on V4101APS itemCode itemBranch F4102 ITM branchCode itemBranch F4102 MCU
itemType shelfLife shelfLifeUom useFixedMfgLeadTime fixedMfgLeadTime leadTimeUnits saleable constrainedItemTimeFence constrainedItemTimeFenceUnits timeVaryingEvent effectiveDate =' '
itemBranch itemBranch itemBranch itemBranch itemBranch itemBranch itemBranch itemBranch itemBranch itemBranch
F4102 F4102
STKT SLD assignment
if F4102.STKT = 'C' or 'K', then itemType = "C" else itemType = F0005.DL02 where F0005.SY = '41' and F0005.RT = 'I' and F0005.KY = F4102.STKT hard coded to "DAYS" y y y
F4102 F4102
SCPSELL MTF1 assignment heading
if F4102.SCPSELL = '1', the saleable = "Yes" else saleable = "No" hard coded to "DAYS" today's date is enclosed in ' ' UNCS is retrieved from F4105 where F4105.ITM = F4102.ITM and F4105.MCU = F4102.MCU and then converted to the currency for F4102.MCU F4106.AN8 = 0 Default value 0 Item.Branch.Order Policy(OPC)=2 use item.branch:item_value_policy(OPV) otherwise <null> Item.Branch.Order Policy(OPC)=4 use item.branch:item_value_policy(OPV) otherwise <null>
itemCost timeVaryingEvent effectiveDate =' ' itemPrice manufacturingLeadTime
itemBranch itemBranch itemBranch itemBranch
F4105 F4106 F4106 F4102
UNCS EFTJ UPRC LTMF
fixedOrderQuantity
itemBranch
F4102
assignment
fixedDaysSupply orderMultiplier minimumOrderQuantity maximumOrderQuantity abcSales abcInvestmentInventory abcMarginInventory
itemBranch itemBranch itemBranch itemBranch itemBranch itemBranch itemBranch
F4102 F4102 F4102 F4102 F4102 F4102 F4102
assignment MULT RQMN RQMX ABCS ABCI ABCM
fixedLeadTime variableLeadTime plannerNumber plannerName plannerEmail safetyStock freezeTimeFenceDays lotStatusCode shrinkageRate
itemBranch itemBranch itemBranch itemBranch itemBranch itemBranch itemBranch itemBranch itemBranch
F4102 F4102 F4102 F0101 F01151 F4102 F4102 F4102 F4102
LTLV LTPU ANPL ALPH EMAL SAFE MTF2 LOTS SRNK
F0101.An8 = F4102.ANPL
New UDC 34A|MP (3 - MRP planning, 4 - MPS planning, 6 - Not planned, 7 - MRP and DRP planning, 8 - MPS and DRP planning, 9 - DRP planning) planningCode stockingType serialCodeRequired drpPlanned salesCategoryCode1 salesCategoryCode2 salesCategoryCode3 salesCategoryCode4 salesCategoryCode5 salesCategoryCode6 salesCategoryCode7 salesCategoryCode8 salesCategoryCode9 salesCategoryCode10 commodityClass commoditySubClass supplierRebateClass masterPlanningFamily landedCostRule itemDimensionGroup warehouseProcessGroup1 warehouseProcessGroup2 warehouseProcessGroup3 itemPoolCode shippingConditionsCode shippingCommodityClass cycleCountCategory timeVaryingEvent effectiveDate =' ' itemBranch itemBranch itemBranch itemBranch itemBranch itemBranch itemBranch itemBranch itemBranch itemBranch itemBranch itemBranch itemBranch itemBranch itemBranch itemBranch itemBranch itemBranch itemBranch itemBranch itemBranch itemBranch itemBranch itemBranch itemBranch itemBranch itemBranch itemBranch F4102 F4102 F4102 F4102 F4102 F4102 F4102 F4102 F4102 F4102 F4102 F4102 F4102 F4102 F4102 F4102 F4102 F4102 F4102 F4102 F4102 F4102 F4102 F4102 F4102 F4102 F4102 MPST STKT SRNR MPST SRP1 SRP2 SRP3 SRP4 SRP5 SRP6 SRP7 SRP8 SRP9 SRP0 PRP1 PRP2 PRP3 PRP4 PRP5 PRP6 PRP7 PRP8 PRP9 PRP0 SHCN SHCM CYCL heading
Yes if MPST = 1, otherwise "No"
today's date is enclosed in ' '
All inventory policy records selected per data selection based on V4101APS (all item/branch combinations) itemCode inventoryPolicy F4102 ITM y branchCode inventoryPolicy F4102 MCU DL01 is retrieved from F34A30 where F34A30.SY y = '34' and F34A30.RT = 'TF' and F34A30.KY = forecastConsumptionRule inventoryPolicy F0005 DL01 forecastConsumptionTimeFence inventoryPolicy F4102 MTF1 hard coded to "DAYS" timeFenceUnit inventoryPolicy assignment coverageUnit today's date is enclosed in ' ' timeVaryingEvent effectiveDate =' ' inventoryPolicy heading hard coded to "No" useCoverForMaximum inventoryPolicy assignment hard coded to "No" useCoverForSafety inventoryPolicy assignment maximumLevel inventoryPolicy minimumLevel inventoryPolicy stockoutCost inventoryPolicy maximumCoverage inventoryPolicy
y y y y
XML Field Name
XML Object Name
E1 Table
E1 Field
Notes
Key
Missing in E1
All items per data selection based on V41021APS (small subset of fields from F41021) business view and value of Omit Expired Lots processing option on R34A740 (if PO = '1', then expired lots will be excluded) itemCode beginningInventory F41021 ITM branchCode beginningInventory F41021 MCU lotNumber beginningInventory F41021 concatenation concatenation = F41021.LOCN|F41021.LOTN storageName beginningInventory F41021 LOCN calculation = if PO Quantity In Transit = '1', then quantity = F41021.PQOH + F41021.QTTR if PO Quantity In Inspection = '1', then quantity = F41021.PQOH + F41021.QTIN if PO Quantity In Operation 1 = '1', then quantity = F41021.PQOH + F41021.QTO1 if PO Quantity In Operation 2 = '1', then quantity = F41021.PQOH + F41021.QTO2 else quantity = F41021.PQOH retrieves F34A30.DL01 where F34A30.SY = '41' and F34A30.RT = 'L' and F34A30.KY = F41021.LOTS assignment = if F34A30.DL01 = 'P', then lotStatus = 'Pegged' if F34A30.DL01 = 'A', then lotStatus = "Available" if F34A30.DL01 = 'O', then lotStatus = "Onhold" if F34A30.DL01 = 'S', then lotStatus = "Scrap" if F34A30.DL01 = 'E', then lotStatus = "Expired" else lotStatus = " " format = yyyy-mm-ddT00:00:00 format = yyyy-mm-ddT00:00:00 format = yyyy-mm-ddT00:00:00
y y
quantity
beginningInventory
F41021
calculation
lotStatus statusDate manufacturingDate expiryDate holdPeriod qualityCode userComment
beginningInventory beginningInventory beginningInventory beginningInventory beginningInventory beginningInventory beginningInventory
F34A30 F4108 F4108 F4108
assignment DLEJ OHDJ MMEJ
y y y
item code
F4101 - Item Master ITM
XML Field Name
XML Object Name
E1 Table
E1 Field
Notes
Required
y
Key
Missing in E1
All customers per data selection based on V03012APS (small subset of fields from F03012) business view customerCode customer F03012 AN8 y name customer F0101 ALPH all values from F0116 are fetched where F0116.AN8 = F03012.AN8 and F0116.EFTB = F0101.EFTB address1 customer F0116 ADD1 address2 customer F0116 ADD2 address3 customer F0116 ADD3 city customer F0116 CTY1 stateProvince customer F0116 ADDS country customer F0116 CTR postalCode customer F0116 ADDZ longitude customer latitude customer
y y
defaultServiceObjective customerBusinessUnit customerMailingName parentAddressNumber

parentName
customer customer customer customer

customer
F03012 F0101 F0111 F0150

F0101
OPBP MCU MLNM PA8

ALPH
description is retrieved from F0005 for UDC 34A/BO Fetch value where F03012.an8 = F0111.an8F0111.idln = 0 B0100002/D0100381Pass in F03012.AN8Get mnAddressNumberParent
F0101.AN8 = parentAddressNumber B90CB124/D90CB124 DefaultSoldToShipTo passin F03012.an8 = mnShipToAddress get mnSoldToAddress F0101.AN8 = SoldToAddress y y y y y
billToNumber customer billToName customer F0101 ALPH billToCompany billToCompanyList itemCode customerSourcing F40306 ITM branchCode customerSourcing F40306 MCU receivingCalendar customerSourcing F40306.EFTJ is enclosed in ' ' timeVaryingEvent effectiveDate =' ' customerSourcing F40306 EFTJ preference customerSourcing F40306 OSEQ All item prices from F4106 where EXDJ is greater than today's date for the customer being processed from V03012APS itemCode itemPrice F4106 ITM branchCode itemPrice F4106 MCU customerOrGroup itemPrice F4106.EFTJ is enclosed in ' ' timeVaryingEvent effectiveDate =' ' itemPrice F4106 EFTJ price itemPrice F4106 UPRC Customers selected from V03012APS are grouped together by AC01 through AC30 codes from F0101
y y y
y y y
name description members type="members"
customerGroup customerGroup customerGroup
F0101 F0005
concatenation DL01 heading
concatenation = data dictionary description for data items AC01 AC30|F0101.AC01 - AC30 description is retrieved from F0005 for UDC 01/AC01 - AC30
all customers who share the F0101.AC01 - AC30 value customerCode customerGroup F03012 AN8 All item substitutions from F4104 where XRT equals 'S' and EXDJ is greater than today's date for all customers selected from V03012APS All item/branch combinations from F4102 where ITM is equal to ITM from F4104 customerCode customerProductSubstitution F4104 AN8 y itemCode customerProductSubstitution F4104 ITM y branchCode customerProductSubstitution F4102 MCU y ITM for F4104.CITM is retrieved from F4101 substituteItemCode customerProductSubstitution F4104 CITM y multiple customerProductSubstitution if f4104.rato is populated, then hardcoded value = '1' ratio customerProductSubstitution F4104 RATO F4104.EFTJ is enclosed in ' ' timeVaryingEvent effectiveDate =' ' customerProductSubstitution F4104 EFTJ cost customerProductSubstitution if F4104.APSP is populated, then hardcoded value = '1' preference customerProductSubstitution F4104 APSP
y y y y y
item code
ssNumberParent
XML Field Name
XML Object Name
E1 Table
E1 Field
R34A785 - Branch Relationship Based - R34A780 Processing Option equals '1' All branch relationships as data selection allows, based on F3403 business view All records that are currently active, effective dates will be taken into account. laneCode Lane F3403 concat originBranchCode Lane F3403 mmcu destinationBranchCode Lane F3403 cmcu description Lane F0006 concat
One routing entry for each supply/demand branch transportModeCode Transport Mode F3403 description Transport Mode returnTripTime Transport Mode F3403 availabilityCalendar Transport Mode leadTimeUom Transport Mode leadTime Transport Mode F3403 weightCapactiyUom Transport Mode volumeCapacityUom Transport Mode minimumWeightUsage Transport Mode minimumVolumeUsage Transport Mode weightCapacityPerVehicle Transport Mode volumeCapacityPerVehicle Transport Mode timeVaryingEvent effectiveDate = Transport Mode F3403 numberOfVehicles Transport Mode flatRatePerTrip Transport Mode costPerWeightUnit Transport Mode costPerVolumeUnit Transport Mode All lanes implied by item branch/level of specifically logic reading F3403 itemCode Item Transport Mode F3403 transportModeCode Item Transport Mode availabilityCalendar Item Transport Mode shipMultiple Item Transport Mode minimumShipment Item Transport Mode deploymentPullForward Item Transport Mode
concat trlt UDC Days trlt
itm
R34A780 - Transportation Management System Based - R34A780 Processing Option equals '0' All records as the data selection allows, based on F4950 business view laneCode Lane concat originBranchCode destinationBranchCode description Lane Lane Lane F0006 F0006 calculated mcu concat
For each carrier/lane transportModeCode description returnTripTime availabilityCalendar leadTimeUom leadTime weightCapacityUom volumeCapacityUom Transport Mode Transport Mode Transport Mode Transport Mode Transport Mode Transport Mode Transport Mode Transport Mode Transport Mode F4950 F0005 F4950 concat desc ltdt UDC Days ltdt wtum vlum
F4950 F4952 F4952
minimumWeightUsage minimumVolumeUsage weightCapacityPerVehicle volumeCapacityPerVehicle timeVaryingEvent effectiveDate = numberOfVehicles
Transport Mode Transport Mode Transport Mode Transport Mode Transport Mode Transport Mode
F4952 F4952 F4952 F4952 F4950
mnwt mncb mxwt mxcb eftj UDC
flatRatePerTrip
Transport Mode
F4950
calculated
costPerWeightUnit
Transport Mode
calculated
costPerVolumeUnit
Transport Mode
calculated
itemCode transportModeCode availabilityCalendar shipMultiple minimumShipment deploymentPullForward
Item Item Item Item Item Item
Transport Mode Transport Mode Transport Mode Transport Mode Transport Mode Transport Mode
F3403
itm
** Note: Freight Charge Amount 1.) The freight charge amount will be converted to domestic currency 2.) If the rate unit of measure (rtum) is not equal to the weight capacity uom (wtum)
Processing option = 1 lane F3403 Master table F0006 F3403.cmcu F3403.mmcu Transport Mode F3403 Item Transport Mode F3403 Processing option = 0 lane F4950 Master table F0006 F3403.cmcu F3403.mmcu
Transport Mode F4950 F0005 F4950.mot|.cars
F4952
F4950.rtn F4950.cars F4950.mot F4950.cars F4950.mot Item Transport Mode F3403 Getting descriptions and concat F0006 F3403.cmcu F3403.mmcu
UDC 00|TM or or or
Transport Mode F4950 F0005 F4950.mot|.cars F4952 F4950.rtn F4950.cars F4950.mot F4950.cars F4950.mot Item Transport Mode F3403
Notes
Required
Missing in Return to File Definitions E1
mmcu|cmcu mmcu cmcu dl01|dl01 description of originBranchCode & destinationBranchCode All UDC values from 00|TM
y y y
y y
UDC value: 34A/AC - Use 'D', Default hard coded value: Days y y y y y y y Today's date y y y y y y
y y y y y
ption equals '0' originBranchCode|destinationBranchCode y F0006.mcu using F4950.orgn - If F4950.nmcu is blank y F4950.nmcu - everything else Retrieved using F4950.shan y dl01|dl01 using originBranchCode|destinationBranchCode
mot/carrier y UDC value: 00/TM - Use mot|cars if blank no value or tags UDC value: 34A/AC - Use 'D', Default hard coded value: Days . if ltdt blank no value or tags if blank no value or tags y Finds route restrictions (F4952) based in the following order: 1.) F4952.rtn = F4950.rtn 2.) F4952.cars=F4950.cars && F4952.mot=F4950.mot 3.) F4952.cars=F4950.carst 4.) F4952.mot=F4950.mot
Finds route restrictions (F4952) based in the following order: 1.) F4952.rtn = F4950.rtn 2.) F4952.cars=F4950.cars && F4952.mot=F4950.mot 3.) F4952.cars=F4950.carst 4.) F4952.mot=F4950.mot UDC value: 34A/VC - Use F4950.rtn If freight charge amount (F4950.frcg) is not equal to zero**, if the rate type (F4950.frtp) is variable , if the rate basis (rtgb) is weight, it will equal the costPerWeightUnit multiplied by the weight capacity per vehicle (mxwt). If the rate UOM differs from the Weight Capacity UOM, the charge will be converted to the Weight Capacity UOM. If freight charge amount (F4950.frcg) is not equal to zero**, if the rate type (F4950.frtp) is variable , if the rate basis (rtgb) is volume, it will equal the costPerVolumeUnit multiplied by the volume capacity per vehicle (mxcb). If the rate UOM differs from the Volume Capacity UOM, the charge will be converted to the Volume Capacity UOM. If freight charge amount (F4950.frcg) is not equal to zero**, if the rate type (F4950.frtp) is fixed, it will equal the freight charge amount. If freight charge amount (F4950.frcg) is not equal to zero**, if the rate type (F4950.frtp) is variable , if the rate basis (F4950.rtgb) is weight, it will equal the freight charge amount (frcg). If the rate UOM differs from the Weight Capacity UOM, the charge will be converted to the Weight Capacity UOM.
If freight charge amount (F4950.frcg) is not equal to zero**, if the rate type (F4950.frtp) is variable , if the rate basis (F4950.rtgb) is volume, it will equal the freight charge amount (frcg) multiplied by the volume capacity per vehicle (mxcb) divided by the weight capacity per vehicle (mxwt). If the rate UOM differs from the Volume Capacity UOM, the charge will be converted to the Volume Capacity UOM. If freight charge amount (F4950.frcg) is not equal to zero**, if the rate type (F4950.frtp) is fixed , it will equal the freight charge amount divided by the weight capacity per vehicle (mxwt).
If freight charge amount (F4950.frcg) is not equal to zero**, if the rate type (F4950.frtp) is variable , if the rate basis (F4950.rtgb) is weight, it will equal the freight charge amount (frcg) multiplied by the weight capacity per vehicle (mxwt) divided by volume capacity per vehicle (mxcb). If the rate UOM differs from the Weight Capacity UOM, the charge will be converted to the Weight Capacity UOM. If freight charge amount (F4950.frcg) is not equal to zero**, if the rate type (F4950.frtp) is variable , if the rate basis (F4950.rtgb) is volume, it will equal the freight charge amount (frcg). If the rate UOM differs from the Volume Capacity UOM, the charge will be converted to the Volume Capacity UOM. If freight charge amount (F4950.frcg) is not equal to zero**, if the rate type (F4950.frtp) is fixed , it will equal the freight charge amount divided by the volume capacity per vehicle (mxcb). y y y y y y y
ght charge amount will be converted to domestic currency te unit of measure (rtum) is not equal to the weight capacity uom (wtum), the freight charge amount will be converted for the weight capacity uom (wtum)
Getting descriptions and concat
Getting descriptions and concat
UDC 00|TM
or or or
F0006.mcu F0006.mcu
User defined code F4952.rtn F4952.cars F4952.mot F4952.cars F4952.mot
capacity uom (wtum)
XML Field Name
XML Object Name E1 Table
E1 Field
All operations per data selection based on the V3003APS (majority of fields from F3003) business view and where F3003.OPSC is not blank or is equal to 'A' (active or alternate lines)
operationCode description
operation operation
F3003 F3003
concatenation DSC1
durationResourceOrSet factorResourceOrSet primaryOutput batch minRunQty
operation operation operation operation operation
F3003 F3003
concatenation KIT assignment assignment
maxRunQty useRunTime
operation operation
F3003
BQTY assignment
minRunTime maxRunTime runTimeUnit
operation operation operation
calculation assignment assignment
Produced item for each effective routing (primary output only) itemCode producedItem F3003 KIT Produced item BOM for each routing created (the last operation for each effective routing) branchCode producedItemBom F3003 MMCU
quantity producedItemBom F3003 yield producedItemBom timeVaryingEvent effectiveDate =' ' producedItemBom All the items consumed at the 'operation seq.' with effect yes/no
BQTY assignment heading
consumedItemSetCode consumedItemBom branchCode itemCode
consumedItemSet consumedItemBomList consumedItemBom F3003 consumedItemBom F3002
concatenation heading MMCU ITM
scaling timeVaryingEvent effectiveDate =' '
consumedItemBom consumedItemBom
assignment heading
available consumedItemBom assignment quantity consumedItemBom F3002 QNTY scrap consumedItemBom F3002 SCRP consumptionOverheadCost consumedItemBom bomPlanningFactor consumedItemBom F3002 FTRP preference consumedItemBom calculation The Operation BOR will have two for each routing resource. The two records are for the effective yes and no, based on EFFF.
resourceSetCode operationBorList branchCode resourceCode
resourceSet operationBor operationBor
concatenation heading F34A120 MMCU F34A120 RESCD
durationUnit
operationBor
assignment
scaling
operationBor
assignment
minimumRunQuantity minimumRunTime runTimeUnits optimizeRunType timeVaryingEvent effectiveDate =' '
operationBor operationBor operationBor operationBor operationBor
heading
available operationBor assignment duration operationBor F34A120 APSDUR capacityRequired operationBor F34A120 CAPREQ lotMultiple operationBor overheadCost operationBor preference operationBor F34A190 respre Based on F3003, filter the non-blank OPSC (i.e. do not include the alternates) One per the implied routing header. The routing object equates to all the effective routings, current and future, as implied by all possible routing A
routingCode description
routing routing
F3003 F3003
concatenation KITL
primaryOperationOrSet routing F3003 concatenation The Operation Set is a list of details, one each for the routing steps in effect for their header. Alternates will be included. operationSetList routing heading
operationSetCode members
operationSet operationSet
F3003
concatenation heading
operationCode branchOrGroup
operationSet branchOperationSet
F3003 concatenation The Branch Operation Set is a list of details, one each for the routing steps in effect for F3003 MMCU
routingCode
branchOperationSet
F3003
concatenation
operationSetCode
branchOperationSet
F3003
concatenation
preferredOperation branchOperationSet F3003 concatenation Per the Routing, there will be two Branch Operations. One for the effective date (yes) and one for the non-effective date (no). branchCode branchOperation F3003 MMCU
operationCode timeVaryingEvent effectiveDate =' '
branchOperation branchOperation
F3003
concatenation heading
available branchOperation assignment overheadCost branchOperation Per the Routing, there will be two Branch Routings. One for the effective date (yes) and one for the non-effective date (no). branchCode branchRouting F3003 MMCU
routingCode description timeVaryingEvent effectiveDate =' '
branchRouting branchRouting branchRouting
F3003 F3003
concatenation KITL heading
available
branchRouting
assignment
overheadCost All F34A110 as data selection allows - build a crew for each resource / branch combination, where apsrest = 'C' resourceCode crew F34A110 RESCD branchCode crew F34A110 MMCU name crew F34A110 DL01 description crew F34A110 DSC1 availabilityCalendar fixedProductionTimeFence crew crew F0005 DL01 F34A110 FTPF
timeFenceUnits timeunitForCost branchResourceOHCosts
crew crew
assignment
crew branchLaborOHCosts
F30008
crew branchResourceCosts crew branchLaborCosts operatingCalendar shift1 shift2 crew crew crew crew
F30008 MSFR F30008 STLF F30008 F30006 F30006 F30006 WDCK WRHR WRH2
shift3 shift4 shift5 shift6 resourceUtilization resourceEfficiency
crew crew crew crew crew crew
F30006 F30006 F30006 F30006 F30006 F30006
WRH3 WRH4 WRH5 WRH6 WORU WORE
criticalResource crew F30006 CRTW workCenter crew F34A110 MCU timeVaryingEvent effectiveDate =' ' crew F34A110 UPMJ availableCapacity crew F34A110 AVCAP setupCost crew operationgCost crew premiumCost crew fixedCost crew All F34A110 as data selection allows - build a machine for each resource / branch combination, where apsrest = 'M' resourceCode machine F34A110 RESCD branchCode machine F34A110 MMCU name machine F34A110 DL01 description machine F34A110 DSC1 availabilityCalendar fixedProductionTimeFence timeUnitForCost machine machine machine F0005 DL01 F34A110 FTPF
timeFenceUnits optimizeRunLength branchResourceOHCosts
machine machine
assignment
machine branchLaborOHCosts
F30008
machine branchResourceCosts machine branchLaborCosts operatingCalendar shift1 shift2 shift3 shift4 shift5 shift6 resourceUtilization resourceEfficiency criticalResource machine machine machine machine machine machine machine machine machine machine machine
F30008 MSFR F30008 STLF F30008 F30006 F30006 F30006 F30006 F30006 F30006 F30006 F30006 F30006 F30006 WDCK WRHR WRH2 WRH3 WRH4 WRH5 WRH6 WORU WORE UDC 30/CR
workCenter machine F34A110 MCU timeVaryingEvent effectiveDate =' ' machine F34A110 UPMJ availableCapacity machine F34A110 AVCAP setupCost machine operatingCost machine premiumCost machine fixedCost machine All F34A110 as data selection allows - build a machine for each resource / branch combination, where apsrest = 'T' resourceCode tool F34A110 RESCD branchCode tool F34A110 MMCU name tool F34A110 DL01 description tool F34A110 DSC1 availabilityCalendar remainingUses maximumUses fixedProductionTimeFence timeunitForCost tool tool tool tool tool F0005 DL01
F34A110 FTPF
timeFenceUnits branchResourceOHCosts
tool
assignment
tool branchLaborOHCosts
F30008
tool branchResourceCosts tool branchLaborCosts operatingCalendar shift1 shift2 shift3 shift4 shift5 shift6 resourceUtilization resourceEfficiency criticalResource workCenter timeVaryingEvent effectiveDate =' ' availableCapacity setupCost operatingCost premiumCost fixedCost tool tool tool tool tool tool tool tool tool tool tool tool tool tool tool tool tool tool
F30008 MSFR F30008 STLF F30008 F30006 F30006 F30006 F30006 F30006 F30006 F30006 F30006 F30006 F30006 F34A110 F34A110 F34A110 WDCK WRHR WRH2 WRH3 WRH4 WRH5 WRH6 WORU WORE UDC 30/CR MCU UPMJ AVCAP
Based on F3003, 'header' and 'detail' - an entry for each implied in-between operation, ex. from 10.00 to 20.00 routingCode firstOperationSetCode secondOperationSetCode temporalRelation temporalRelation F3003 F3003 concatenation concatenation
relation minSeparation maxSeparation moveTime queueTime setupTime timeUnit resourceCode branchCode name description groupName members description groupName members description branchCode resourceCode fromOperation toOperation description duration durationUnits cost patternPriority availabilityCalendar
temporalRelation temporalRelation temporalRelation temporalRelation temporalRelation temporalRelation temporalRelation resource resource resource resource operationGroup operationGroup operationGroup resourceGroup
F3003 F3003 F3003 F3003 F3003 F3003
assignment calculation calculation MOVD QUED SETL assignment
changeoverPattern changeoverPattern changeoverPattern changeoverPattern changeoverPattern changeoverPattern changeoverPattern changeoverPattern changeoverPattern changeoverPattern
Notes
Required
elds from F3003) business view if UDC(34A|GU).special Handeling = 1 concatenation = F3003.mmcu|F3003.kit|F3003.trt|F3003.bqty|F3003.opsq|F3003.o psc|F3003.line|F3003.efff|F3003.mcu else concatenation = F3003.mmcu|F3003.kit|F3003.trt|F3003.bqty|F3003.opsq|F3003.o psc|F3003.line|F3003.mcu y
retrieves last record from F34A120 using keys from operationCode where F34A120.durr = '1' if UDC(34A|GU).special Handeling = 1 concatenation = F34A120.mmcu|F34A120.kit|F34A120.trt|F34A120.bqty|F34A120. opsq|F34A120.opsc|F34A120.line|F34A120.efff|F34A120.mcu|F3 4A120.rescd else F34A120.mmcu|F34A120.kit|F34A120.trt|F34A120.bqty|F34A120. opsq|F34A120.opsc|F34A120.line|F34A120.mcu|F34A120.rescd y y only written if operationCode keys are the same assignment = if F3003.BQTY equals '0', then batch = "No" else batch = "Yes" assignment = hard coded value of "1" if F3003.BQTY is not equal to '0', then maxRunQty = BQTY converted to planning UOM else maxRunQty = "1" assignment = hard coded value of "Yes" retrieves F30006.PILC from F30006 where F30006.MCU = F3003.MCU and F30006.MMCU = F3003.MMCU calculation = if F30006.PILC = 'B' or 'L', then minRunTime = F3003.RUNL/F3003.TIMB else if F30006.PILC = 'C' or 'M', then minRunTime = F3003.RUNM/F3003.TIMB else minRunTime = "0" assignment = the value calculated for minRunTime assignment = hard coded value of "Hours"
y y if F3003.BQTY > 0, then quantity is converted to planning unit of measure else quantity = "1" assignment = hard coded value of "100" f3003.efff
ch effective routing)
if UDC(34A|GU).special Handeling = 1 (If opsc is not 0 and primary = MMCU|KIT|TRT|BQTY|OPSQ|OPSC|LINE|EFFF|MCU|CPNB else retrieve mcu,line,opsc then MMCU|KIT|TRT|BQTY|OPSQ|OPSC|LINE|EFFF|MCU|CPNB) else (If opsc is not 0 and primary = MMCU|KIT|TRT|BQTY|OPSQ|OPSC|LINE|MCU|CPNB else retrieve mcu,line,opsc then MMCU|KIT|TRT|BQTY|OPSQ|OPSC|LINE|MCU|CPNB)
y y y y
assignment = if F3002.FORQ = 'V' or F3002.FORQ = '%' and F3003.BQTY = '0' then scaling = "V" else if F3002.FORQ = 'F' or F3002.FORQ = '%' and F3003.BQTY > '0' then scaling = "F"
CompareDate = run date of UBE Do while (ValidDate = True) if (CompareDate < EFFF) Then available = 'No' CompareDate = EFFF ValidDate = True timeVaryingEvent effectiveDate = CompareDate if (CompareDate < EFFT) Then available = 'Yes' converted to planning unit of measure y
calcuation = F3002.SBNT + 1 ecords are for the effective yes and no, based on EFFF. if UDC(34A|GU).special Handeling = 1 concatenation = F34A120.MMCU|F34A120.KIT|F34A120.TRT|F34A120.BQTY|F34 A120.OPSQ|F34A120.OPSC|F34A120.LINE|F34A120.EFFF|F34 A120.MCU|F34A190.RSETID else concatenation = F34A120.MMCU|F34A120.KIT|F34A120.TRT|F34A120.BQTY|F34 A120.OPSQ|F34A120.OPSC|F34A120.LINE|F34A120.MCU||F34 A190.RSETID y y y assignment = if F34A120.TUOM = 'S' then durationUnit = "Seconds" else if F34A120.TUOM = 'M' then durationUnit = "Minutes" else if F34A120.TUOM = 'H' then durationUnit = "Hours" else if F34A120.TUOM = 'D' then durationUnit = "Days" else durationUnit = "Hours" assignment = if F3003.BQTY is not equal to '0' then scaling = "F" else scaling = "V"
y y y y Yes' and 'No' when system date >= EFFF, <= EFFT (current data) "Yes' and 'No' when system date < EFFF (future data) "No" everything else (past data)
y y
he effective routings, current and future, as implied by all possible routing As-Of-Dates. if UDC(34A|GU).special Handeling = 1 concatenation = MMCU|KIT|TRT|BQTY|OPSQ|OPSC|LINE|EFFF else concatenation = MMCU|KIT|TRT|BQTY|OPSC|LINE y
operation that produces the primary output - i.e. the last operation if UDC(34A|GU).special Handeling = 1 concatenation = MMCU|KIT|TRT|BQTY|OPSQ|OPSC|LINE|EFFF|MCU else concatenation = MMCU|KIT|TRT|BQTYOPSC|LINE|MCU effect for their header. Alternates will be included. if UDC(34A|GU).special Handeling = 1 concatenation = MMCU|KIT|TRT|BQTY|OPSQ|OPSC|LINE|EFFF|MCU else concatenation = MMCU|KIT|TRT|BQTY|OPSQ|OPSC|LINE|MCU
if UDC(34A|GU).special Handeling = 1 concatenation = MMCU|KIT|TRT|BQTY|OPSQ|OPSC|LINE|EFFF|MCU else concatenation = MMCU|KIT|TRT|BQTY|OPSQ|OPSC|LINE|MCU Operation Set is a list of details, one each for the routing steps in effect for their header. As E1 supports alternate routings, the preferred will be the non-blank O y if UDC(34A|GU).special Handeling = 1 concatenation = MMCU|KIT|TRT|BQTY|OPSQ|OPSC|LINE|EFFF else concatenation = MMCU|KIT|TRT|BQTY|OPSC|LINE y if UDC(34A|GU).special Handeling = 1 concatenation = MMCU|KIT|TRT|BQTY|OPSQ|OPSC|LINE|EFFF|MCU else concatenation = MMCU|KIT|TRT|BQTY|OPSQ|OPSC|LINE|MCU
if UDC(34A|GU).special Handeling = 1 concatenation = MMCU|KIT|TRT|BQTY|OPSQ|OPSC|LINE|EFFF|MCU else concatenation = MMCU|KIT|TRT|BQTY|OPSQ|OPSC|LINE|MCU ctive date (yes) and one for the non-effective date (no).
y y
if UDC(34A|GU).special Handeling = 1 concatenation = MMCU|KIT|TRT|BQTY|OPSQ|OPSC|LINE|EFFF|MCU else concatenation = MMCU|KIT|TRT|BQTY|OPSQ|OPSC|LINE|MCU Yes' and 'No' when system date >= EFFF, <= EFFT (current data) "Yes' and 'No' when system date < EFFF (future data) "No" everything else (past data)
y y if UDC(34A|GU).special Handeling = 1 concatenation = MMCU|KIT|TRT|BQTY|OPSQ|OPSC|LINE|EFFF else concatenation = MMCU|KIT|TRT|BQTY|OPSC|LINE y
ve date (yes) and one for the non-effective date (no).
Yes' and 'No' when system date >= EFFF, <= EFFT (current data) "Yes' and 'No' when system date < EFFF (future data) "No" everything else (past data) y y y
branch combination, where apsrest = 'C'
DL01 is retrieved from F0005 where F0005.SY = '34A' and F0005.RT = 'AC' and F0005.KY = F34A110.AVCAL assignment = if F34A110.TUOM = 'S' then durationUnit = "Seconds" else if F34A110.TUOM = 'M' then durationUnit = "Minutes" else if F34A110.TUOM = 'H' then durationUnit = "Hours" else if F34A110.TUOM = 'D' then durationUnit = "Days" else durationUnit = "Hours" y if(F3009.PORR = 'P') Then rate = (F30008.STRF/100) * F30008.STLF else rate = F30008.STRF F30008 record selected base MCU, MMCU and cost code equal to 07 if(F3009.PORR = 'P') Then rate = (F30008.MSTF/100) * F30008.MSFR else rate = F30008.MSTF F30008 record selected base MCU, MMCU and cost code equal to 07 F30008 record selected base MCU, MMCU and cost code equal to 07 F30008 record selected base MCU, MMCU and cost code equal to 07
y y y y y y
ce / branch combination, where apsrest = 'M'
DL01 is retrieved from F0005 where F0005.SY = '34A' and F0005.RT = 'AC' and F0005.KY = F34A110.AVCAL y assignment = if F34A110.TUOM = 'S' then durationUnit = "Seconds" else if F34A110.TUOM = 'M' then durationUnit = "Minutes" else if F34A110.TUOM = 'H' then durationUnit = "Hours" else if F34A110.TUOM = 'D' then durationUnit = "Days" else durationUnit = "Hours" y if(F3009.PORR = 'P') Then rate = (F30008.STRF/100) * F30008.STLF else rate = F30008.STRF F30008 record selected base MCU, MMCU and cost code equal to 07 if(F3009.PORR = 'P') Then rate = (F30008.MSTF/100) * F30008.MSFR else rate = F30008.MSTF F30008 record selected base MCU, MMCU and cost code equal to 07 F30008 record selected base MCU, MMCU and cost code equal to 07 F30008 record selected base MCU, MMCU and cost code equal to 07
y y y y y y
ce / branch combination, where apsrest = 'T'
DL01 is retrieved from F0005 where F0005.SY = '34A' and F0005.RT = 'AC' and F0005.KY = F34A110.AVCAL y y y assignment = if F34A110.TUOM = 'S' then durationUnit = "Seconds" else if F34A110.TUOM = 'M' then durationUnit = "Minutes" else if F34A110.TUOM = 'H' then durationUnit = "Hours" else if F34A110.TUOM = 'D' then durationUnit = "Days" else durationUnit = "Hours" if(F3009.PORR = 'P') Then rate = (F30008.STRF/100) * F30008.STLF else rate = F30008.STRF F30008 record selected base MCU, MMCU and cost code equal to 07 if(F3009.PORR = 'P') Then rate = (F30008.MSTF/100) * F30008.MSFR else rate = F30008.MSTF F30008 record selected base MCU, MMCU and cost code equal to 07 F30008 record selected base MCU, MMCU and cost code equal to 07 F30008 record selected base MCU, MMCU and cost code equal to 07
today's date is enclosed in ' ' y y y y
ween operation, ex. from 10.00 to 20.00 y concatenation = MMCU|KIT|TRT|BQTY|OPSQ|OPSC|LINE|EFFF|MCU concatenation = MMCU|KIT|TRT|BQTY|OPSQ|OPSC|LINE|EFFF|MCU y y
retrieves F30006.PILC from F30006 where F30006.MCU = F3003.MCU and F30006.MMCU = F3003.MMCU assignment = if F30006.PILC = 'O' then relation = "StartsAfterEnd" else if F3003.POVR = '100' then relation = "StartAfterStart" else relation = "StartsAfterEnd" y calculation = F3003.QUED + F3003.MOVD + F3003.SETL (from next operation) calculation = F3003.QUED + F3003.MOVD + F3003.SETL (from next operation)
assignment = hard coded value of "Hours" y y y y y y y y y y y y y y y y y y y y y y
y y y y
, the preferred will be the non-blank OPSC. Alternates will be excluded.
XML Field Name
XML Object Name
E1 Table
E1 Field
Notes
Key
All purchase orders per data selection based on the V4311APS (small subset of fields from F4311) business view and value of End Date processing option on R34A750 (F4311.PDDJ less than or equal to End Date PO) and value of Version of Supply/Demand Inclusion Rules processing option on R34A750 (only purchase orders that meet inclusion rule) and where F4311.PS01 is not equal to '1' (excludes transfer orders) concatenation = F4311.DOCO|F4311.KCOO|F4311.DCTO|F4311.SFXO purchaseOrderCode purchaseOrder F4311 concatenation supplierCode purchaseOrder F4311 AN8 destinationBranchCode purchaseOrder F4311 MCU All purchase order details (lines) for the purchase orders selected per criteria listed for purchaseOrder Object lineItem purchaseOrderDetail F4311 LNID itemCode purchaseOrderDetail F4311 ITM
y y y y y
shipDate arriveDate transportMode carrierName vehicleId
purchaseOrderDetail purchaseOrderDetail purchaseOrderDetail purchaseOrderDetail purchaseOrderDetail
F4311 F4311 F4311 F4311
calculation PDDJ MOT ANCR
LTLV is retrieved from F4102 where F4102.ITM = F4311.ITM and F4102.MCU = F4311.MCU calculation = if F4102.LTLV > 0, then shipDate = F4311.PDDJ F4102.LTLV else shipDate = F4311.PDDJ format = yyyy-mmddT00:00:00 format = yyyy-mm-ddT00:00:00 y
y retrieves F34A30.DL01 where F34A30.SY = '40' and F34A30.RT = 'AT' and F34A30.KY = F4311.LTTR assignment = if F34A30.DL01 = 'P', then status = "Planned" if F34A30.DL01 = 'A', then status = "Approved" if F34A30.DL01 = 'R', then status = "Rejected" if F34A30.DL01 = 'Q', then status = "Quoted" else status = " " converted to planning unit of measure
orderStatus quantity
purchaseOrderDetail purchaseOrderDetail
F4311 F4311
LTTR UOPN
unitCost
purchaseOrderDetail
F4311
calculation
fix
purchaseOrderDetail
F4311
assignment
calculation = if converting F4311.UOPN to planning unit of measure changed the quantity, then unitCost = F4311.AEXP / F4311.UOPN else unitCost = F4311.AMC3 y assignment = if F4311.UNCD = 'Y' or F4301.HOLD is not blank, then fix = "Yes" else fix = 'No'
item code
XML Field Name
XML Object Name
E1 Table
E1 Field
Notes
Required
Key
Missing in E1
All sales orders per data selection based on the V4211APS (F4211 joined to F49211 by DOCO, DCTO, KCOO, LNID) business view and value of End Date processing option on R34A730 (F4211.PDDJ less than or equal to End Date PO) and value of Version of Supply/Demand Inclusion Rules processing option on R34A730 (only sales orders that meet inclusion rule) salesOrderCode salesOrder F4211 concatenation concatenation = F4211.DOCO|F4211.KCOO|F4211.DCTO y all values from F4201 are fetched where F4201.DOCO = F4211.DOCO and F4201.DCTO = F4211.DCTO and F4201.KCOO = F4211.KCOO retrieval keyed on F4201.AN8 = F0101.AN8 retrieval keyed on F4201.SHAN = F0101.AN8 description is retrieved for UDC 34A/BO
billToCustomerCode billToCustomerName shipToCustomerCode shipToCustomerName serviceObjective status allowMultiSource allowPartialOrders allowPartialLines allowBackOrders priority
salesOrder salesOrder salesOrder salesOrder salesOrder salesOrder salesOrder salesOrder salesOrder salesOrder salesOrder
F4201 F0101 F4201 F0101 F4201
AN8 ALPH SHAN ALPH OPBO
y F4201 F4201 F4201 F4201 F4201 OPMS OPPL OPLL OPBA PRIO if F4201.opms = '1' or 'Y', then hard coded to "Yes" F4201.opms = '0' or 'N', then hard coded to "No" if F4201.oppl = '1' or 'Y', then hard coded to "Yes" F4201.oppl = '0' or 'N', then hard coded to "No" if F4201.opll = '1' or 'Y', then hard coded to "Yes" F4201.opll = '0' or 'N', then hard coded to "No" if F4201.opba = '1' or 'Y', then hard coded to "Yes" F4201.opba = '0' or 'N', then hard coded to "No" description is retrieved for UDC H40/PR all values from F4006 are fetched where F4006.DOCO = F4211.DOCO and F4006.DCTO = F4211.DCTO and F4006.KCOO = F4211.KCOO and F4006.ANTY = '1' if if if if
address1 salesOrder F4006 ADD1 address2 salesOrder F4006 ADD2 address3 salesOrder F4006 ADD3 city salesOrder F4006 CTY1 stateProvince salesOrder F4006 ADDS country salesOrder F4006 CTR postalCode salesOrder F4006 ADDZ createdBy salesOrder F4201 ORBY createdDate salesOrder F4201 TRDJ format = yyyy-mm-ddT00:00:00 All sales order details (lines) for the sales orders selected per criteria listed for salesOrder Object lineItem salesOrderDetail F4211 LNID shipFromBranchCode salesOrderDetail F4211 MCU shipToCustomerName salesOrderDetail F0101 ALPH retrieval keyed on F4211.SHAN = F0101.AN8 shipToCustomerCode salesOrderDetail F4211 SHAN itemCode salesOrderDetail F4211 ITM calculation = (F4211.UORG - F4211.SOCN) - the result is converted to planning unit of measure quantity salesOrderDetail F4211 calculation
y y
unitPrice extendedPrice requestedDate shipDate arriveDate pickDate
salesOrderDetail salesOrderDetail salesOrderDetail salesOrderDetail salesOrderDetail salesOrderDetail
F4211 F4211 F4211 F4211 F4211 F4211
UPRC AEXP DRQJ PPDJ RSDJ PDDJ
format = yyyy-mm-ddT00:00:00 format = yyyy-mm-ddT00:00:00 format = yyyy-mm-ddT00:00:00 format = yyyy-mm-ddT00:00:00 retrieves F34A30.DL01 where F34A30.SY = '40' and F34A30.RT = 'AT' and F34A30.KY = F4211.LTTR assignment = if F34A30.DL01 = 'P', then status = "Planned" if F34A30.DL01 = 'A', then status = "Approved" if F34A30.DL01 = 'R', then status = "Rejected" if F34A30.DL01 = 'Q', then status = "Quoted" else status = " " if F4201.opms = '1' or 'Y', then hard coded to "Yes" if F4201.opms = '0' or 'N', then hard coded to "No" if F4201.opll = '1' or 'Y', then hard coded to "Yes" if F4201.opll = '0' or 'N', then hard coded to "No" if F4201.opba = '1' or 'Y', then hard coded to "Yes" if F4201.opba = '0' or 'N', then hard coded to "No" if F4201.opss = '1' or 'Y', then hard coded to "Yes" if F4201.opss = '0' or 'N', then hard coded to "No" all values from F4006 are fetched where F4006.DOCO = F4211.DOCO and F4006.DCTO = F4211.DCTO and F4006.KCOO = F4211.KCOO and F4006.ANTY = '2'
y y y y
status allowMultiSource allowPartialLines allowBackOrders allowSubstitutions
salesOrderDetail salesOrderDetail salesOrderDetail salesOrderDetail salesOrderDetail
F4211 F4201 F4201 F4201 F4201
LTTR OPMS OPLL OPBA OPSS
address1 address2 address3 city stateProvince country postalCode
salesOrderDetail salesOrderDetail salesOrderDetail salesOrderDetail salesOrderDetail salesOrderDetail salesOrderDetail
F4006 F4006 F4006 F4006 F4006 F4006 F4006
ADD1 ADD2 ADD3 CTY1 ADDS CTR ADDZ
item code
XML Field Name
XML Object Name
E1 Table
E1 Field
Notes
y
Required
Missing in E1
All suppliers per data selection based on the V43090E (F43090 joined to F0101 by AN8) business view supplierCode supplier F43090 AN8 name supplier F43090 ALPH all values from F0116 are fetched where F0116.AN8 = F43090.AN8 and F0116.EFTB = F0101.EFTB city supplier F0116 CTY1 stateProvince supplier F0116 ADDS country supplier F0116 CTR postalCode supplier F0116 ADDZ latitude supplier assignment hard coded to " " longitude supplier assignment hard coded to " " All items from F4102 where ITM and MCU are equal to ITM and MCU on the supplier being processed from V43090E branchCode supplierItem F43090 MCU itemCode supplierItem F43090 ITM standardLeadTime supplierItem F43090 ALTD premiumLeadTime supplierItem leadTimeUom supplierItem assignment hard coded to "Days" orderMultiple supplierItem F4102 MULTt converted to planning unit of measure shippingCalendar supplierItem receivingCalendar supplierItem minmaxOrderPeriod supplierItem minmaxOrderPeriodUnit supplierItem if F4102.OPC = '1', then orderPolicy = "LotForLot" if F4102.OPC = '2', then orderPolicy = "Fixed" if F4102.OPC = '4', then orderPolicy = "DaysOfSupply" orderPolicy supplierItem F4102 OPC demandCoverageUnits supplierItem timeVaryingEvent effectiveDate =' ' supplierItem F43090 CEFJ F43090.CEFJ is enclosed in ' ' converted to the currency for company "00000" if the currency for the supplier differs from company "00000" standardCost supplierItem F43090 ACST premiumCost supplierItem minimumPeriodOrder supplierItem F4102 RQMN converted to planning unit of measure
y y y
y y y y
converted to planning unit of measure if F4102.OPC = '2', then maximumPeriodOrder = F4102.OPV maximumPeriodOrder supplierItem F4102 RQMX fixedOrderQuantity supplierItem demandCoverageOrder supplierItem Suppliers selected from V43090E are grouped together by AC01 through AC30 codes from F0101 if indicated by RP01 through RP30 from F34A40 record is retrieved from F34A40 where F34A40.SY = '01' if F34A40.RP01 -RP30 = '1', name = F0101.AC01 - AC30 name supplierGroup F0101 AC01 - AC30 y description supplierGroup F0005 DL01 description is retrieved from F0005 for UDC 01/AC01 - AC30
y y
members type="members" supplierCode
supplierGroup supplierGroup
F0101
heading AN8
all suppliers who share the F0101.AC01 - AC30 value
item code
XML Field Name
XML Object Name
E1 Table
E1 Field
Notes
Required
All transfer orders per data selection based on the V4311APS (small subset of fields from F4311) business view and value of End Date processing option on R34A760 (F4311.PDDJ less than or equal to End Date PO) and value of Version of Supply/Demand Inclusion Rules processing option on R34A760 (only transfer orders that meet inclusion rule) and where F4311.PS01 is equal to '1' (transfer orders only) concatenation = F4311.DOCO|F4311.KCOO|F4311.DCTO|F4311.SFXO MCU is retrieved from F0006 where F0006.AN8 = F4311.AN8
transferOrderCode
transferOrder
F4311
concatenation
y y y y y
originBranchCode transferOrder F0006 MCU destinationBranchCode transferOrder F4311 MCU All transfer order details (lines) for the transfer orders selected per criteria listed for transferOrder Object lineItem transferOrderDetail F4311 LNID itemCode transferOrderDetail F4311 ITM
shipDate arriveDate transportMode carrierName vehicleId
transferOrderDetail transferOrderDetail transferOrderDetail transferOrderDetail transferOrderDetail
F4311 F4311 F4311 F4311
calculation PDDJ MOT ANCR
if F4311.ADDJ is not blank use else LTLV is retrieved from F4102 where F4102.ITM = F4311.ITM and F4102.MCU = F4311.MCU calculation = if F4102.LTLV > 0, then shipDate = F4311.PDDJ F4102.LTLV else shipDate = F4311.PDDJ format = yyyy-mmddT00:00:00 y format = yyyy-mm-ddT00:00:00 y
y retrieves F34A30.DL01 where F34A30.SY = '40' and F34A30.RT = 'AT' and F34A30.KY = F4311.LTTR assignment = if F34A30.DL01 = 'P', then status = "Planned" if F34A30.DL01 = 'A', then status = "Approved" if F34A30.DL01 = 'R', then status = "Rejected" if F34A30.DL01 = 'Q', then status = "Quoted" else status = " " assignment = if F4311.UNCD = 'Y' or F4301.HOLD is not blank, then fix = "Yes" else fix = 'No' converted to planning unit of measure y
orderStatus
transferOrderDetail
F34A30
assignment
fix quanitity lotNumber
transferOrderDetail transferOrderDetail transferOrderDetail
F4311 F4311 F4311
assignment UOPN LOTN
if F4311.LOTN is not equal to blank, then LOTS retrieval keyed by F4108.LOTN = F4311.LOTN F4108.MCU = F4311.MCU F4108.ITM = F4311.ITM if failed then retrieval key is F4108.LOTN = '1' assignment = if F4108.LOTS = blank, then lotStatus = "Available" else lotStatus = "Not Available" y retrieval keyed by F4108.LOTN = F4311.LOTN F4108.MCU = F4311.MCU F4108.ITM = F4311.ITM expiryDate quanlityCode transferOrderDetail transferOrderDetail F4108 MMEJ if failed then retrieval key is F4108.LOTN = '1' y
lotStatus manufacturingDate
transferOrderDetail transferOrderDetail
F4108
assignment
item code
XML Field Name
XML Object Name
E1 Table
E1 Field
Business view over F34A11 to return BC values to the UBE, but data selection should not be used. Records will be deleted from the F3460 table for every item/branch combination, the dates used to delete between are calculated from the XML's startDate and endDate used along with the fiscal date pattern to calculate the delete data range itemCode branchCode customerCode quantity startDate endDate Enterprise Forecast Detail Enterprise Forecast Detail Enterprise Forecast Detail Enterprise Forecast Detail Enterprise Forecast Detail Enterprise Forecast Detail F3460 F3460 F3460 F3460 F3460 DRQJ TYPF UORG BPFC DCTO F3460 F3460 F3460 F3460 ITM MCU AN8 FQT
Notes
Required
Missing in E1 Return to File Definitions
election should not be used.
mbination, the dates used to delete between are calculated
pattern to calculate the delete data range
converted to primary unit of measure Used with the fiscal data pattern to calculate the delete data range for an item/branch combination Value retrieved from processing options, if left blank 'BF' will be used. Equal to F3460.fqt hard coded value: N hard coded value: FC
XML Field Name
XML Object Name
E1 Table
E1 Field
All records as data selection allows, based on F4801 business view. All records Which also as data include selection inclusion allows, rules based on F4801 business view. Which also in doco workOrderCode Work Order F4801 branchCode Work Order F4801 mcu dl01 description Work Order F4801
type quantity
Work Order Work Order Work Order Work Order Work Order Work Order Work Order Work Order Work Order Work Order Work Order Work Order
F4801 F4801 F4801 F34A30 F34A30 F4801 F4801 F4801 F4801 F4801 F4801
calculated uorg concat lnid UDC UDC trdj drqj strt strx pars mcu
demand
demandLineItem priority status createdDate requestedDate startDate completionDate parentWorkOrderCode parentWorkOrderBranchCode
changesAllowed itemCode
Work Order Work Order
F4801
calculated itm
routingCode
Work Order
concat F3003 All F3112s attached to the work order F4801.doco. Only active routes F3112.opsc
operationSetName operationCode constraintsFlag
Work Order Operation Work Order Operation Work Order Operation
F3003
concat
runTime status
Work Order Operation Work Order Operation
UDC
calculated description
remainingTime timeUnit setupTime
Work Order Operation Work Order Operation Work Order Operation
F3112
calculated Hours setl
queueTime
Work Order Operation
F3112
qued
moveTime overlap
F3112 F3112
movd povr
temporalRelation minSeparation
calculated calculated
calculated maxSeparaton Work Order Operation opyp yield Work Order Operation F3112 cpyp cumulativeYield Work Order Operation F3112 strt|SEST startDate Work Order Operation F3112 drqj requestedDate Work Order Operation F3112 strx|SEET completionDate Work Order Operation F3112 allowOffloading Work Order Operation earliestStart Work Order Operation latestEnd Work Order Operation earliestStart Work Order Operation latestEnd Work Order Operation scheduledCompletionDate Work Order Operation F3112 calculated qtyCompleted Work Order Operation F3112 All F34A150 attached to the work order routing operation. If no F34A150 table use F34A120 key is doco|mcu|opsq
resourceSet
Work Order BOR F34A150 or F34A120 F34A80 F34A150 or F34A120
concat
resourceCode resourceDescription
Work Order BOR Work Order BOR
rescd dl01 runtm or apsdur
duration remainingDuration
Work Order BOR Work Order BOR
timeUnit
Work Order BOR
F34A150 or F34A120
tuom
resourceType
Work Order BOR
UDC
34A|RT
durr durationResource Work Order BOR F34A120 leadTimeOffset Work Order BOR endTimeOffset Work Order BOR All F3111 consumed on the current operation step. Key is doco opsq. If a consumed item is not part of routing opsq add to first one. No text lines
consumedItemSet itemCode quantity
Work Order Consumed Item BOM F3111 Work Order Consumed Item BOM F3111 Work Order Consumed Item BOM F3111
concat cpit uorg
calculated remainingQuantity Work Order Consumed Item BOM stpp scrapFactor Work Order Consumed Item BOM F3111 lovd leadTimeOffset Work Order Consumed Item BOM F3111 endTimeOffset Work Order Consumed Item BOM pars parentWorkOrderCode Work Order Consumed Item BOM F4801 mmcu parentWorkOrderBranchCode Work Order Consumed Item BOM F4801 Only 1 produced item which is the parent item on the work order - Using last operation step itm itemCode Work Order Produced Item BOM F4801 uorg quantity Work Order Produced Item BOM F4801
remainingQuantity yield leadTimeOffset endTimeOffset parentWorkOrderCode parentWorkOrderBranchCode
Work Order Produced Item Work Order Produced Item Work Order Produced Item Work Order Produced Item Work Order Produced Item Work Order Produced Item
BOM BOM BOM BOM BOM BOM
F3112
calculated cpyp
F4801 F4801
pars mmcu
Notes
Required
s data selection allows, based on F4801 business view. Which also include inclusion rules y y
F40039.dcto = F4801.dcto Production - If F40039.document type is equal to '02' or '03' Configured - If F40039.document type is equal to '02' or '03' and F4102.stkt = 'C' Maintenance - If F40039.document type is equal to '04' or '05' y converted to planning unit of measure y RORN|RKCO|RCTO UDC value: 00/PR - Use F4801.prts

yyyy-mm-ddT00:00:00 yyyy-mm-ddT00:00:00 yyyy-mm-ddT00:00:00 yyyy-mm-ddT00:00:00 Retrieved from F4801 using F4801.pars
"Yes" - If parts list and routing can be deleted, not frozen, and the status is not greater than the prohibit change status "No" - If parts list or routing cannot be deleted, frozen, or the status is greater than the prohibit status If the stocking type is 'C' (configured item) or 'K' (Kit Item) for the item on work order, then the changes are not allowed on the work order If the quantity scrapped F4801.WASOCN is greater than zero or if the quantity shipped F4801.WASOQS is greater than zero or if the Work Order Frozen Flag is set to 'Y" then no changes are allowed on the Work Order If the RunMachineActual(wlmaca) hours, RunLaborActual (wllaba) hours, and Setuplaboractual (wlseta) hours are reported on a routing step then the routing can not be deleted The Parts list records can only be deleted if the Quantity Issued (wmtrqt), UnaccountedDirectLaborHrs (wmcts1),UnaccountedDirectLaborAmt (wmcts4), UnaccountedScrapAmt (wmcts7) and UnaccountedScrapUnits (wmcts8) are populated with zero's meaning no activity has been performed on parts list records If the material status code is 07, it means that the parts are in Warehouse. This parts list record can not be deleted If the quantities on the parts list are hard commited then Parts list can not be deleted y Retrieve from F3003 using F4801.(mcu, itm, uorg, trt) if can not find change quantity to 0. Take master routing into account if UDC(34A|GU).special Handeling = 1 MMCU|KIT|TRT|BQTY|OPSQ|OPSC|LINE|EFFF else MMCU|KIT|TRT|BQTY|OPSC|LINE Retrieve from F3003 using F112.(mmcu, kit, uorg, trt) if can not find change quantity to 0. Take master routing into account. if UDC(34A|GU).special Handeling = 1 MMCU|KIT|TRT|BQTY|OPSQ|OPSC|LINE|EFFF|F3112.mcu else MMCU|KIT|TRT|BQTY|OPSQ|OPSC|LINE|F3112.mcu same as operationSetName
ached to the work order F4801.doco. Only active routes F3112.opsc is blank
y y y
If plc = 'B' or 'L' - F3112.runl if plc = 'C' or 'M' - F3112.runm if plc = 'O' -0 else = blank don't put in UDC value: 34A/RS - F34A30(31|OS| F3112.opst)
Remaining Quantity = F4801.uorg - F4801.soqs. Calculation((runTime/ uorg)*remainingQty) hard coded value: Hours yyyy-mm-ddT00:00:00 yyyy-mm-ddT00:00:00 if backscheduling = 1CalcQueueMoveWithoutResourceDate else qued yyyy-mm-ddT00:00:00 if backscheduling = 1CalcQueueMoveWithoutResourceDate else movd yyyy-mm-ddT00:00:00 StartsAfterEnd - If plc equals 'O' StartAfterStart - If F3003.povr equal 100 StartsAfterEnd - everything else F3112.qued + F3112.movd + F3112.setl (from next operation) F3112.qued + F3112.movd + F3112.setl (from next operation)
yyyy-mm-ddT00:00:00 yyyy-mm-ddT00:00:00 yyyy-mm-ddT00:00:00
y y y y y y
If STRX is blank use DRQJ else use STRX uorg - soqs use F34A120 key is doco|mcu|opsq Send out primary and supporting resources from F34A120. if UDC(34A|GU).special Handeling = 1 (F3003.(MMCU|KIT|TRT|BQTY|OPSQ|OPSC|LINE|EFFF) | F3112.MCU | F34A150.RESCD or F3003.(MMCU|KIT|TRT|BQTY|OPSQ|OPSC|LINE|EFFF) | F3112.MCU | F34A120.RESCD) else (F3003.(MMCU|KIT|TRT|BQTY|OPSQ|OPSC|LINE) | F3112.MCU | F34A150.RESCD or F3003.(MMCU|KIT|TRT|BQTY|OPSQ|OPSC|LINE) | F3112.MCU | F34A120.RESCD)
y Retrieved from F34A80 using F34A150.rescd or F34A120.rescd
Take Time Basis in account Remaining Quantity = F4801.uorg - F4801.soqs. Calculation((duration/ uorg)*remainingQty)
S = Seconds M = Minutes H = Hours D = Days Default = Hours UDC(34A|RT|F34A150.apsrest).description or UDC(34A|RT|F34A120.apsrest).description If DURR = 1 Then 'Yes' else 'No' y y if UDC(34A|GU).special Handeling = 1 F3003.(MMCU|KIT|TRT|BQTY|OPSQ|OPSC|LINE|EFFF) | F3112.MCU | F34A150.RESCD | F3111.CPNB else F3003.(MMCU|KIT|TRT|BQTY|OPSQ|OPSC|LINE) | F3112.MCU | F34A150.RESCD | F3111.CPNB
sumed item is not part of routing opsq add to first one. No text lines
y y
F3111.uorg - F3111.trqt converted to planning unit of measure
y Retrieved from F4801 using F4801.pars y converted to planning unit of measure F3112.uorg - F3112.soqs (ordered less completed, for the last operation) converted to planning unit of measure Using last operation step of work order's routing y y
E1 Table
E1 Field
Description
F0007
MMCU
Branch Plant
F30006
MCU
Work Center
F30006 F30006
WDCT WDCK
Calendar Type Calendar Name
Date
F0007
SHFT
Shift Code
F3009 F30006
Duration
F0007
Event Code
Detail
Records selected from F30006 use the following key: F30006.MMCU = F0007.MMCU F30006.WDCK = F0007.WDCK
The branch number that is associated with the calendar. The field is right-justified with leading spaces (for example, M30). Alternatively, if this calendar is the global default calendar, you can enter ALL in this field. The work center associated with this calendar. For example, WELD-101. Blank is a valid value , which indicates that this is a branch plant-level calendar. This value is always blank for transportation calendars. The type of calendar. For example, ROUTE. Blank is a valid value for manufacturing calendars. The type should refer to manufacturing, shipping, or receiving calendar types in SCBM. The descriptive title of the calendar. For example, Calendar A. Blank is a valid value for manufacturing calendars. The date that the calendar event takes effect. The date is derived from the Work Center Master File table (F30006) and the Workday Calendar table (F0007). A user defined code (00/SH) that identifies daily work shifts. Blank is a valid value and indicates a whole day. Any other value indicates a partial day. The value is always blank for transportation calendars. A corresponding start time for this day or shift can be defined in the SCBM calendar event cross-reference. if (F0007.SHFT = 0) Then '0' if (F0007.SHFT =1) Then WRHR if (F0007.SHFT =2) Then WRH2 if (F0007.SHFT =3) Then WRH3 if (F0007.SHFT =4) Then WRH4 if (F0007.SHFT =5) Then WRH5 if (F0007.SHFT =6) Then WRH6 TD concat with the number of the day TD01 TD02 etc
E1 Name
E1 Table
F42119/F4211 F42119/F4211 F42119/F4211 F42119/F4211 F42119/F4211 F42119/F4211 F42119/F4211 F42119/F4211 F42119/F4211 F42119/F4211 F42119/F4211 F42119/F4211 F42119/F4211 F42119/F4211 F42119/F4211 F42119/F4211 F42119/F4211 F42119/F4211 F03012
E1 Column
E1 / Integration Notes
Order Number Order Type Order Company Order Line No Business Unit Customer No Sold To Customer No Ship To Short Item Number 2nd Item Number 3rd Item Number Actual Ship Date Invoice Date Quantity Requested Date Scheduled Pick Date Promised Shipment Date Promised Delivery Date Price Per Unit Company
DOCO DCTO KCOO LNID MCU AN8 SHAN ITM LITM AITM ADDJ IVD SOQS DRQJ PDDJ PPDJ RSDJ UPRC CO Customer No Ship To concatenated with Company
Converted to Planning UOM Converted to the Date Format defined by Demantra
Customer No Ship To concatenated with Company
E1 Table
F4106 F4106 F4106 F4106 F4106 F4106 F4106 calculated
E1 Column
ITM LITM AITM MCU AN8 EXDJ EFTJ
E1 Name
Short Item Number 2nd Item Number 3rd Item Number Branch/Plant Customer Number Expired Date Effective Date Amount - List Price
E1 / Integration Notes
LIST
Converted to the Date Format defined in Integration Constants Converted to the Date Format defined in Integration Constants Converted to the default Company Currency Code and the Planning UOM
E1 Table
E1 Column
E1 Name
F42119
DOCO
Document (Order No, Invoice, e
F42119
DCTO
Order Type
F42119
KCOO
Order Company (Order Number)
F42119 F42119 F42119 F42119 F42119
LNID ITM SHAN MCU ADDJ
Line Number Short Item Number Customer No Ship To Business Unit Actual Ship Date
E1 / Integration Notes Key field to be used to detect duplicates on the Demantra inbound side. Key field to be used to detect duplicates on the Demantra inbound side. Key field to be used to detect duplicates on the Demantra inbound side. Key field to be used to detect duplicates on the Demantra inbound side.
Converted to the Date Format defined in Integration Constants This will be the Promotion ID sent from Demantra to E1 in Inbound Promotion Pricing. May be from F4074 or a cross reference table. This will be the 'O' for off invoice (ACNT=2) or 'B' for bill back (ACNT=4). Converted to the default Company Currency Code.
F4074 F4074 F4074
PMTN COSTYP AEXP
Promotion ID Cost Type Amount - Extended Price
F4074
SFXO
Order Suffix
F4074
AKID
Price History Alternate Key
F4074
SRCFD
Price History Alternate Key So
F4074
OSEQ
Sequence Number
F4074
SUBSEQ
Sub-Sequence Number
F4074
TIER
Tier
F4074
PA04
Target Application
Key field to be used to detect duplicates on the Demantra inbound side. Key field to be used to detect duplicates on the Demantra inbound side. Key field to be used to detect duplicates on the Demantra inbound side. Key field to be used to detect duplicates on the Demantra inbound side. Key field to be used to detect duplicates on the Demantra inbound side. Key field to be used to detect duplicates on the Demantra inbound side. Key field to be used to detect duplicates on the Demantra inbound side.
SCBM Field Name
E1 Table E1 Field
Notes
deploymentPlanDetail
deploymentCode lineItem originBranchCode destinationBranchCode itemCode arriveDate shipDate quantity
F3411 F3411 F3411 F3411 F3411 F3411 F3411 F3411 F3411
LNID MMCU MCU ITM RRQJ RSTJ TRQT Changed back to transaction quantity MSGA Blank if (F34A60.RSDJ < arriveDate) = E if (F34A60.RSDJ > arriveDate) = D if (DOCO is blank) = O if (quantity > F34A60.TRQT) = G if (quantity < F34A60.TRQT) = L E = Expedite D = Defer G = quantity increased L = quantity decreased Hard coded X
Beginning of new Transfer Order A concatenation of: DOCO|KCOO|DCTO|SFXO|LNID where F3411.DOCO = DOCO F3411.KCOO = KCOO F3411.DCTO = DCTO F3411.SFXO = SFXO F3411.LNID = LNID Only for VCP
F3411 F3411
MSGT HCLD
File Definitions
SCBM Field Name purchasePlanDetail
E1 Table E1 Field
purchaseOrderCode lineItem receivingBranchCode supplierCode itemCode arriveDate shipDate quantity
F3411 F3411 F3411 F3411 F3411 F3411 F3411 F3411 F3411
LNID MCU VEND ITM RRQJ RSTJ TRQT MSGA
Notes Beginning of new Purchase Order A concatenation of: DOCO|KCOO|DCTO|SFXO|LNID where F3411.DOCO = DOCO F3411.KCOO = KCOO F3411.DCTO = DCTO F3411.SFXO = SFXO F3411.LNID = LNID Only for VCP
Changed back to transaction quantity Blank if (F34A60.RSDJ < arriveDate) = E if (F34A60.RSDJ > arriveDate) = D if (DOCO is blank) = O if (quantity > F34A60.TRQT) = G if (quantity < F34A60.TRQT) = L E = Expedite D = Defer G = quantity increased L = quantity decreased Hard coded X
F3411 F3411
MSGT HCLD
File Definitions
SCBM Field Name
E1 Table
E1 Field
Notes Beginning of new Work Order
masterProductionPlanDetail workOrderCode branchCode itemCode requestedDate
F3411 F3411 F3411 F3411
DOCO MCU ITM RRQJ If no record in F34A70 associated to the WO then use requestedDate. Otherwise use F34A70.DRQJ F34A70.STRT if no record then blank F34A70.STRT if no record then blank R34A890 processing option Company associated to Branch Plant Zero ? Blank if (F34A60.RSDJ < arriveDate) = E if (F34A60.RSDJ > arriveDate) = D if (DOCO is blank) = O if (quantity > F34A60.TRQT) = G if (quantity < F34A60.TRQT) = L E = Expedite D = Defer G = quantity increased L = quantity decreased Hard coded X Process for all components with M type routings from F3002 using the above keys Blank F3411 unique ID F3002 component short number
F3411 F3411 F3411 F3411 F3411 F3411 F3411 F3411
DRQJ STRT RSTJ DCTO KCOO LNID SFXO MSGA
F3411 F3411
MSGT HCLD
branchCode requestedDate
F3412 F3412 F3412 F3412 F3412
RORN PLNK KIT MMCU DRQJ
itemCode workOrderCode
F3412 F3412 F3412 F3412 F3412 F3412
UORG ITM MCU DOCO DCTO LOVD
Components quantity based on transaction quantity F3002 branch component Hard coded "WP" F3002.LOVD
Parent SCBM Field Name
SCBM Field Name
F4801 Add
detailedProductionPlan detailedProductionPlan detailedProductionPlan detailedProductionPlan routingInstanceList routingInstance routingInstance productionScheduleCode createdDate routingInstanceList routingInstance routingInstanceCode branchCode
MMCU E1 Creates new DOCO TBM = TRT TRT = TRT
routingInstance routingInstance routingInstance operationInstanceList operationInstance operationInstance
externalId routingCode operationInstanceList operationInstance operationInstanceCode operationSet
operationInstance operationInstance operationInstance
operationCode scheduledStartTime scheduledEndTime STRT The earliest date DRQJ The last end date
operationInstance operationInstance operationInstance operationInstance operationInstance operationInstance operationInstance operationInstance operationInstanceResourceList operationInstanceResource operationInstanceResource
earliestStartTime latestEndTime runTime elapsedTime delayTime timeUom fixed operationInstanceResourceList operationInstanceResource resourceSet resourceCode
operationInstanceResource
scheduledStartTime
operationInstanceResource operationInstanceResource operationInstanceResource
scheduledEndTime earliestStartTime latestEndTime
operationInstanceResource operationInstanceResource operationInstanceResource operationInstanceResource operationInstanceResource operationInstance
runTime elapsedTime delayTime timeUom resourceType operationInstanceConsumedItemList
operationInstanceConsumedItemList operationInstanceConsumedItem operationInstanceConsumedItem operationInstanceConsumedItem consumedItemSet itemCode
operationInstanceConsumedItem operationInstance operationInstanceProducedItemList operationInstanceProducedItem
netQuantity operationInstanceProducedItemList operationInstanceProducedItem itemCode ITM UORG changed from planning UOM to transaction UOM
operationInstanceProducedItem
netQuantity
The following information is not from Detail Production Plan XML MCU Retrieve Company From Business Unit TRDJ Date R34A900 ran UOM Transaction UOM SRST status from P48013 referenced in processing options DCTO populated from R34A900 processing option
F4801 Update
Retrieve old record and keep data not changed below
F4801T
F3112
All records related to the DOCO will be deleted and then readded.
F3111
F34A150
All records related to All records related to DOCO will be deleted DOCO will be deleted and re-added. If no and re-added consumed item information from PS If old record will grab then will keep old data that is already records. populated, so data is not lost during the When fetching F3002 delete. info TBM = M Text lines will be If item is not in F3002 retrieved from F3003 then check F34A90 to add to F3112 for phantom information. Will grab text lines from F3002
DOCO TBM = TRT TRT = TRT
DOCO related to F4801 record
WMCU DOCO related to F4801 record
CMCU DOCO related to F4801 record
DOCO related to F4801 record
MMCU KIT TRT OPSQ OPSC LINE MCU STRT The earliest date DRQJ The last end date SEST The earliest time SEET the last end time STRT DRQJ
OPSQ
OPSQ OPSC MCU
RESCD SCHST formatted in JDEUTIME SCHET formatted in JDEUTIME
RUNL RUNM Go through and find crew and machine time for the operation.
RUNTM
TUOM APSREST
CPIT UORG converted to primary UOM
UORG changed from planning UOM to transaction UOM
UORG changed from planning UOM to transaction UOM
XEVT Hard coded to '1' TRDJ Date R34A900 ran QUED = F3003.QUED TRDJ Date R34A900 ran AING = F3002.AING
PID hard coded "R34A900"
UOM Transaction UOM
MOVD = F3003.MOVD
ITC = F3002.ITC
FORQ = SETL = F3003.SETL F3002.FORQ BSEQ = SETC = F3003.SETC F3002.BSEQ POVR = F3003.POVR UM = F3002.UM OPYP = F3003.OPYP CPYP = F3003.CPYP APID = F3003.APID AN8 = F3003.AN8 DSC1 = F3003.DSC1 SHNO = F3003.SHNO BFPF = F3003.BFPF TIMB = F3003.TIMB CMRQ = F3003.CMRQ
Notes
MMCU|KIT|TRT|BQTY|OPSC|LINE
MMCU|KIT|TRT|BQTY|OPSQ|OPSC|LINE|MCU
SCBM Field Name
E1 Table
E1 Field
enterpriseForecastDetailList enterpriseForecastDetail provenance itemCode branchCode customerCode bucketList bucket endDate quantity
F3460 F3460 F3460
ITM MCU AN8
F3460 F3460 F3460 F3460 F3460 F3460 F3460
DRQJ UORG FQT TYPF DCTO BPFC RVIS PID
Notes
Converted to planning UOM R34A860 processing option. If processing option is blank then hard coded to BF. Hard coded "FC" Hard coded "n". No bypassing. hard coded blank Hard coded "R34A860"
Depending on if the forecast is weekly or monthly old forecast records will be deleted.
Time.dat (old DP file not needed for Demantra integration)

Use this file to define time aggregation in demand planning. Field Name Source Instance Code Calendar Code Year Year Description Year Start Date Year End Date Quarter Quarter Description Quarter Start Date Quarter End Date Month Month Description Month Start Date Month End Date Aggregate Demand Flag
Source Source Org ID
Source SR TP ID
(old DP file not needed for Demantra integration)
fine time aggregation in demand planning. Description Source instance code defined on the planning server. Identifier or code for calendar. Identifier for year (fiscal, calendar, or other year specification). Description of the year (fiscal, calendar, or other year specification). Start date of the year. End date of the year. Identifier for the quarter (fiscal, calendar, or other quarter). Description of the quarter (fiscal, calendar, or other quarter). Start date of the quarter. End date of the quarter. Identifier for the month or fiscal period. Description of the month (fiscal, calendar, or other monthly period specifications). Start date of the month. End date of the month. Aggregate Demand Flag Please provide the Organization ID for the Organization in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Trading partner ID for the Trading partner in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only.
Return to Entity List Mapping Parameter.Source_Instance "Time Aggregation" file "Time Aggregation" file "Time Aggregation" file "Time Aggregation" file "Time Aggregation" file "Time Aggregation" file "Time Aggregation" file "Time Aggregation" file "Time Aggregation" file "Time Aggregation" file "Time Aggregation" file "Time Aggregation" file "Time Aggregation" file "Time Aggregation" file
<null>
<null>
DPUOMConversion.dat (old DP file not needed for Demantra inte

Use this file to specify the unit of measure conversion rates used in demand planning Field Name Source Instance Code From UOM Class To UOM Class From UOM Code To UOM Code Base UOM Flag
Conversion Rate Item
onversion.dat (old DP file not needed for Demantra integration)
ecify the unit of measure conversion rates used in demand planning Description Source instance code defined on the planning server. The UOM class from which the conversion is computed. The UOM class to which the conversion is computed. The UOM code from which the conversion is computed. The UOM code to which the conversion is computed. No more in use, has been retained for backward compatibility.
Conversion rate between the converting-from andconverting-to UOMs. Item name
Return to Entity List Mapping Parameter.Source_Instance
Item_UOM.txt:Primary_UOM
Item_UOM.txt:Shipping UOM Multiple Item_UOM.txt:Weight UOM Multiple Item_UOM.txt:Planning UOM Multiple Item_UOM.txt:Short Item Number
ResourceChange.dat (not needed as we are not doing simulation

Field Name Department Code Resource Code Shift Name From Date Simulation Set Action Type Organization Code Source Instance Code To Date From Time To Time Capacity Change Deleted Flag
Company Name
Change.dat (not needed as we are not doing simulations)

Description Department unique identifier. Departments are already defined in table MSC_ST_DEPARTMENT_RESOURCES. Resource unique identifier. Resources are already defined in table MSC_ST_DEPARTMENT_RESOURCES. Shift name defined in calendar BO. Simulation set that starts this change. Type of capacity modification. Valid values are: 1 - Add, 2 - Change, 3 - Delete. Organization code where this resource and department exist. Source instance code defined on the planning server. From time To time Valid values are: 1 - Yes, 2 - No. If 1, then this row is deleted. Required only for Collaborative Planning. You should provide the party name with which the company is registered in CP. For a planning (APS) only environment, this should be left null.
This table is optional and is used in simulations, we can leave this empty for phase one.
Return to Entity List Mapping use the Dept Code on Resources.dat for this resource
DemandMDS.dat
Use this file to define a master demand schedule used as an input to a supply plan. Field Name Item Name Schedule Date Organization Code Using Requirement Quantity Demand Type Schedule Line Num Source Instance Code Assembly Demand Comp Date Daily Demand Rate Demand Schedule Name Planning Group End Item Unit Number Dmd Lateness Cost Request Date Using Assembly Item Name Using Assembly Demand Date Customer Name Demand Class Demand Source Type Order Number Order Priority Selling Price Deleted Flag
Company Name Comments Order Date Type Code Schedule Arrival Date Latest Acceptable Date Shipping Method Code
Source Org ID
Source Inventory Item ID Source Using Assembly Item ID
Source Project ID
Source Task ID
Source Customer Site ID Source Bill ID
Source Customer ID
DS.dat
fine a master demand schedule used as an input to a supply plan. Description Inventory item name. Schedule Date. Organization. Quantity of demand for an item. Valid values are: 1 - For discrete demand, 2 - If repetitive demand Schedule Line Number. Source instance code defined on the planning server. The rate end date for repetitive demand. Daily demand rate Demand schedule name; same as the designator. Planning group Unit number Required for SCO Required for SCO Not required Not required Customer Name Name or identifier of a demand class. Forecast billing address identifier Wip entity name Order priority Selling price Valid values are: 1 - Yes, 2 - No. If 1, then this row is deleted. Required only for Collaborative Planning. You should provide the party name with which the company is registered in CP. For a planning (APS) only environment, this should be left null. Comments for entries posted to the system. Order Date Type Code. Schedule Arrival Date. Latest Acceptable Date. Shipping Method Code. Please provide the Organization ID for the Organization in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only.
Please provide the Inventory Item ID for the Item in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Assembly Item ID for the Assembly Item in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Project ID for the Project in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Task ID for the Task in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Customer Site ID for the Customer Site in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Bill ID for the Bill in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide a unique ID to identify this MDS in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Customer ID for the Customer in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only.
Return to Entity List Mapping
DesignatorMDS.dat (not needed)

Use this file to specify attributes of a master demand schedule Field Name Designator Organization Code MPS Relief Inventory ATP Flag Description Disable Date Demand Class Organization Selection Production Auto-Release Flag Recommendation Release Source Instance Code
Company Name
rMDS.dat (not needed)
ecify attributes of a master demand schedule Description Master demand schedule name. Organization Flag indicating whether MPS relief has been performed against this designator. Valid values are: 1 - Yes, 2 - No. Flag indicating whether the demand is used in ATP calculation or not. Valid values are: 1 - Yes, 2 - No. Description Disable date for designator. Name or identifier of a demand class. Valid values are: 1 - Multiple, 2 - Single. Valid values are: 1 - Yes, 2 - No. Planned order release flag. Valid values are: 1 - Yes, 2 - No. Instance code defined on the planning server. Required only for Collaborative Planning. You should provide the party name with which the company is registered in CP. For a planning (APS) only environment, this should be left null.
Return to Entity List Mapping Directly from "MDS Designators" Directly from "MDS Designators" Directly from "MDS Designators" Directly from "MDS Designators" Directly from "MDS Designators" Directly from "MDS Designators" Directly from "MDS Designators" Directly from "MDS Designators" Directly from "MDS Designators" Directly from "MDS Designators" Directly from "MDS Designators"
Directly from "MDS Designators"
DesignatorPlanOrder.dat (not needed)

Use this file to specify planning attributes of planned orders Field Name Designator Organization Code MPS Relief Inventory ATP Flag Description Disable Date Demand Class Organization Selection Production Auto-Release Flag Source Instance Code
Company Name Bucket Type
rPlanOrder.dat (not needed)
ecify planning attributes of planned orders Description Source application schedule name. Organization Flag indicating whether MPS relief is performed against this designator. ATP supply flag. Valid values are: 1 - Yes, 2 - No. Description Disable date for the designator. Name or identifier of a demand class. Single or multiple organizations. Valid values are: 1 - Multiple, 2 - Single. Valid values are: 1 - Yes, 2 - No. Instance code defined on the planning server. Required only for Collaborative Planning. You should provide the party name with which the company is registered in CP. For a planning (APS) only environment, this should be left null. Valid values are: 1 - Days, 2 - Weeks, 3 - Periods.
Return to Entity List Mapping Directly from "Planned Order Designators" Directly from "Planned Order Designators" Directly from "Planned Order Designators" Directly from "Planned Order Designators" Directly from "Planned Order Designators" Directly from "Planned Order Designators" Directly from "Planned Order Designators" Directly from "Planned Order Designators" Directly from "Planned Order Designators" Directly from "Planned Order Designators"
Directly from "Planned Order Designators" Directly from "Planned Order Designators"
ManufacturingForecast.dat (not needed)

Use this file to define a manufacturing forecast. Field Name Source Instance Code Forecast Set Forecast Designator Customer Item Inv Org Sales Channel Ship-To Loc User Defined1 User Defined Level1 User Defined2 User Defined Level2 Demand Class Bucket Type Forecast Date Rate End Date Original Quantity Current Quantity
uringForecast.dat (not needed)
fine a manufacturing forecast. Description Source instance code defined on the planning server. Identifier used to distinguish a forecast set. Name or identifier of a forecast. Customer name Inventory item name Organization identifier on the planning server. Inv Org is the same as Organization Code. Sales channel Ship-to location Value of the first user defined dimension. Value of the second user defined dimension. Demand Class. Valid values are: 1 - Days, 2 - Weeks, 3 - Months Start date of the time period that a forecast entry covers. End date of the time period that a forecast entry covers. Expected (forecast) quantity due to customer orders. Expected quantity net of customer orders that have been already received. ( Original quantiry - customer orders).
Reservations.dat (customer reservations are not coming through

Use this file to define sales order reservations. Field Name Item Name Organization Code Sales Order Number Line Number Requirement Date Reserved Quantity Sub-inventory Demand Class Project Number Task Number Planning Group
Company Name Source Instance Code Deleted Flag Reservation Type Demand Order Number Supply Order Number Purchase Line Number Supply Org Code
ons.dat (customer reservations are not coming through in current extrac
fine sales order reservations. Description Inventory item name. Organization Order identifier on a sales order. Need-by date. Code for a sub-inventory. Name or identifier of a demand class.
Required only for Collaborative Planning. You should provide the party name with which the company is registered in CP. For a planning (APS) only environment, this should be left null. Source instance code on the planning server. Valid values are: 1 - Yes, 2 - No. If 1, then this row is deleted. Reservation Type Demand Order Number Supply Order Number Purchase Line Number Supply Organization Code
Leave Empty
PlannedOrderSupply.dat (can leave empty, was for original EBS MRP system
Use this file to load information for planned orders from supply planning. Field Name Item Name Organization Code New Schedule Date Firm Planned Type Schedule Line Num Source Instance Code Unit Number Last Unit Start Date New Order Quantity Project Number Task Number Planning Group Schedule Designator Daily Rate From Organization Code Deleted Flag
Company Name
Source Org Instance Code
Source Org ID
Source Project ID
Source Task ID Source From Organization ID
Source supply ID
rderSupply.dat (can leave empty, was for original EBS MRP system to feed planned orde
ad information for planned orders from supply planning. Description Inventory item name Organization End date of the supply (completion date of the first unit). Flag indicating the order is firm. Valid values are: 1 - Yes, 2 - No. Identifies a line in the schedule. Source instance code defined on the planning server. Unit number Last unit start date for repetitive schedules. Supply quantity. Project name Task name. Project planning group. Refers to valid schedule designator. Daily rate for recommended repetitive schedules. From organization code. Valid values are: 1 - Yes, 2 - No. If 1, then this row is deleted. Required only for Collaborative Planning. You should provide the party name with which the company is registered in Collaborative Planning. For a planning (APS) only environment, this should be left null. Please provide the Organization Instance Code for the Organization Instance in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Organization ID for the Organization in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Inventory Item ID for the Item in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Project ID for the Project in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Task ID for the Task in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the From Organization Id for the Sourcing Organization (mentioned in the From Organization Code) in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only.
Please provide a unique ID to identify this supply in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only Please provide the Disposition ID for the Supply in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only.
Return to Entity List Mapping <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null>
<null>
<null>
<null>
<null>
<null>
<null>
<null>
<null>
<null>
SupplyDemand.dat (Later phase - used in Collab Planning)

Use this file to load supply/demand information into Collaborative Planning. Field Name Sync Indicator Item Name Order Type Designator Version Quantity UOM Publisher Company Publisher Site Customer Company Customer Site Supplier Company Supplier Site Ship From Party Name Ship From Party Site Ship To Party Name Ship To Party Site Ship To Address End Order Publisher Name End Order Publisher Site Ship Date Receipt Date Request Date Original Promised Date New Order Placement Date Actual Date Bucket End Date WIP Start Date WIP End Date Bucket Type Order Identifier Release Number Line Number Pegging Order Identifier Ref Release Number Ref Line Number Comments Attachment URL
Serial Number Tracking Number Bill Of Lading Number Carrier Code Vehicle Number Container Type Container Qty Owner Item Name Customer Item Name Supplier Item Name End Order Type Designator Version Serial Number Context Attribute1 Attribute2 Attribute3 Attribute4 Attribute5 Attribute6 Attribute7 Attribute8 Attribute9 Attribute10 Attribute11 Attribute12 Attribute13 Attribute14 Attribute15 Use this file to load supply/demand information into Collaborative Planning. Note: The Date fields should be in the format specified in the profile option "ICX:Date format mask". Key dates for supplydemand.dat
For any given order type that you may be loading using the supplydemand.dat file, you will need to provide a The key date for each order type is listed below.
Order Type ASN Allocated onhand Unallocated onhand Consumption advice Historical sales Negotiated capacity Order forecast Projected available balance Purchase order Purchase order acknowledgement Purchase requisition Safety stock Sales forecast Sales order Sell through forecast Shipment receipt Supply commit Work order
mand.dat (Later phase - used in Collab Planning)
ad supply/demand information into Collaborative Planning. Description Valid values are: R - Replace an existing record; if one does not exist, a new record is created, D - Delete an existing record Inventory item name Required field Provide an optional plan name or identifier for this stream Provide an optional version number for this stream of data
Context column used for descriptive flex-field. Attribute column used for descriptive flex-field. Attribute column used for descriptive flex-field. Attribute column used for descriptive flex-field. Attribute column used for descriptive flex-field. Attribute column used for descriptive flex-field. Attribute column used for descriptive flex-field. Attribute column used for descriptive flex-field. Attribute column used for descriptive flex-field. Attribute column used for descriptive flex-field. Attribute column used for descriptive flex-field. Attribute column used for descriptive flex-field. Attribute column used for descriptive flex-field. Attribute column used for descriptive flex-field. Attribute column used for descriptive flex-field. Attribute column used for descriptive flex-field.
d supply/demand information into Collaborative Planning.
elds should be in the format specified in the profile option "ICX:Date format mask".
for supplydemand.dat
en order type that you may be loading using the supplydemand.dat file, you will need to provide a key date. te for each order type is listed below.
Description A notice to the customer from the supplier that goods have been shipped Quantity in stock that is intended for use by a trading partner Quantity in stock that is not intended for use by any specific trading partner Quantity consumed by a customer from consigned stock Sales for a period in the past Capacity that has been negotiated between customer and supplier A projection of future purchases by customer Projection of the available balance of inventory A customer's commitment to procure goods A supplier's commitment to the customer to supply goods A customer's request to procure goods Quantity presently held by customer or supplier to protect against demand fluctuations A projection of future retail sales Supplier's reference to a customer's order A projection of future withdrawals from a location by the customer Customer's reference to goods received Anticipated future shipments from supplier Quantity in production at a customer or supplier site
Return to Entity List Mapping <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null>
<null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null>
rovide a key date.
CurrencyConversion.dat
Use this file to define currency conversion rates. Field Name Source Instance Code From Currency To Currency Conversion Date Conversion Rate
Conversion.dat
fine currency conversion rates. Description Source instance code is defined on the planning server. Base currency, which will be converted Currency that is expressed after conversion. Conversion Date. Currency conversion rate.
Leave this table empty initially
Return to Entity List Mapping Parameter.Source_Instance Shortcode P0015A Shortcode P0015A Shortcode P0015A Shortcode P0015A
ItemRelationship.dat (not currently being extracted)

:Use this file to load the Item Relationships. Field Name Source Instance Code Inventory Item Related Item Relationship Type
onship.dat (not currently being extracted)
oad the Item Relationships. Description Source instance code defined on the planning server. Name of the inventory item. Name of the Related Item. Name of the Relationship Type.Kept for future use, not to be entered by the user.Internally generating Relationship type as Superseded.
Engineering and Kitting information is not currently being extracted We can use Kitting or Configurations to formulate this data
Return to Entity List Mapping <null> <null> <null> <null>
OperationNetwork.dat - MSC_ST_OPERATION_N
Use this file to define a network routing. Field Name ColumnName From Operation Sequence Code FROM_OPERATION_SEQ_CODE From Operation Effectivity Date FROM_OP_EFFECTIVITY_DATE From Operation Disable FROM_OP_DISABLE_DATE Date To Operation Sequence TO_OPERATION_SEQ_CODECode To Operation Effectivity TO_OP_EFFECTIVITY_DATE Date
TO_OP_DISABLE_DATE ROUTING_NAME ASSEMBLY_NAME
To Operation Disable Date Routing Name
Assembly Name Alternate Routing Designator ALTERNATE_ROUTING_DESIGNATOR

TRANSITION_TYPE PLANNING_PCT CUMMULATIVE_PCT DISABLE_DATE EFECTIVITY_DATE
Transition Type Planning Percentage Cumulative Percentage Disable Date Effectivity Date Organization Code Source Instance Code Deleted Flag
ORGANIZATION_CODE SR_INSTANCE_CODE DELETED_FLAG
COMPANY_NAME
Company Name
Network.dat - MSC_ST_OPERATION_NETWORKS
fine a network routing. Description The operation sequence from which the path in the network is defined. The date from which the operation sequence is valid. The date from which the operation sequence is disabled. The operation sequence to which the path in the network is defined. The date from which the to operation sequence is valid. The date from which the to operation sequence is disabled. The routing name for which the operation network is defined. The assembly name for which the operation network is defined. Identifier to specify an alternate routing. Valid values are: 1 - Primary path, 2 - Alternate path. There should be only one primary path from an operation sequence within a routing. Planning percentages are the percent splits of orders expected out of the manufacturing process. Commutative percentage of the operation network path. The date from which the path in the operation network is valid. The date from which the path in the operation network is disabled. The organization code in which the CO-product is being defined. Source instance code defined on the planning server. Valid values are: 1 - Yes, 2 - No. If 1, then this row is deleted. Required only for Collaborative Planning. You should provide the party name with which the company is registered in CP. For a planning (APS) only environment, this should be left null.
We wont have network routings from E1 - in threory this file should be empty
Return to Entity List Mapping Can be derived by analysing OperationSetList and Network use effectivity dates on Manufacturing.xml:branchoperation use effectivity dates on Manufacturing.xml:branchoperation Can be derived by analysing OperationSetList and Network use effectivity dates on Manufacturing.xml:branchoperation use effectivity dates on Manufacturing.xml:branchoperation Manufacturing.xml:RoutingList:routing:routingCode 28004|59412|M |1| | (second field) Manufacturing.xml:RoutingList:routing:routingCode 28004|59412|M |1| | (second field) <null> "1" 100 default to 0 Parameter.Effective tO Date Offset + Plan_Option.Current Date Parameter.Effective From Date Offset + Plan_Option.Current Date Organisation associated with Manufacturing.xml:RoutingList:routing:routingCode 28004|59412|M |1| | (first field) Parameter.Source_Instance 2
PriceList.dat
Use this file to specify your customer items that are cross-referenced to master items. Field Name Source Instance Code Organization Level Sr. Organization Level Value Product Level Sr. Product Level Value Sales Channel Level Sr. Sales Channel Level Value Sales Rep Level Sr. Sales Rep Level Value Geography Level Sr. Geography Level Value User Defined 1 Level Sr. User Defined 1 Level Value User Defined 2 Level Sr. User Defined 2 Level Value Demand Class Level Sr. Demand Class Level Value Price List Name Start Date
End Date Price Priority Price List UOM
ecify your customer items that are cross-referenced to master items. Description Source instance code defined on the planning server. Level name within the organization dimension. Value of level member within the organization dimension. Level name within the product dimension. Value of level member within the product dimension. Level name within the sales channel dimension. Value of level member within sales channel dimension. Level name within sales representative dimension. Value of level member within sales representative dimension. Level name within geography dimension. Value of level member within geography dimension. Level name of user-defined dimension. Value of level member within user-defined dimension. Level name of user defined dimension. Value of level member within user-defined dimension. Level name within demand class dimension. Value of level member within demand class dimension. Name of price list.
Kept for future use . It should be kept NULL
Return to Entity List Mapping Parameter.Source_Instance "Organization" Customer.xml:customer:itemPrice:branchCode "Item" Customer.xml:customer:itemPrice:itemCode <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> <null> Parameter.Price_List_Code (<null>) Customer.xml:customer:itemPrice:timeVaryingEve nt:effectiveDate Customer.xmlcustomer:itemPrice:timeVaryingEven t:effectiveDate - 1 (of next record) Parameter.Effective To Date Offset + Plan_Option.Current Date (last record) Customer.xmlcustomer:itemPrice:timeVaryingEven t:price <null> <null> <null>
DemHistory.dat
Use this file to define the Booking and Shipment History. Field Name ACTUAL_QTY SALES_DATE DM_ITEM_CODE DM_ORG_CODE DM_SITE_CODE
EBS_SALES_CHANNEL_CODE EBS_DEMAND_CLASS_CODE EBS_BOOK_HIST_BOOK_QTY_BD EBS_BOOK_HIST_REQ_QTY_BD EBS_BOOK_HIST_BOOK_QTY_RD EBS_BOOK_HIST_REQ_QTY_RD EBS_SHIP_HIST_SHIP_QTY_SD EBS_SHIP_HIST_SHIP_QTY_RD EBS_SHIP_HIST_REQ_QTY_RD
oking and Shipment History. Description Actual Quantity(Shipment History - Requested Items - Shipped Date) Sales Date. Item Code. Organization Code. Site Code.
Sales Channel Code. Demand Class Code. Booking History - Booked Date. Booking History - Requested Items - Booked Date. Booking History - Requested Date. Booking History - Requested Items - Requested Date. Shipment History - Shipped Date. Shipment History - Requested Date. Shipment History - Requested Items - Requested Date.
Description refers to dates..but sample import files refer to quantities. Confirmed it is quantities
Return to Entity List Mapping SalesOrderHistory.xml:quantity SalesOrderHistory.xml:requestedDate SalesOrderHistory.xml:item SalesOrderHistory.xml:branch SalesOrderHistory.xml:billToCustomer Take the <description> field in the customer category pointed to by the Parameter.Sales_channel_category
Example: Use 'Retailer' instead of 'RET' Customer Categories pointed to by Parameter.Demand_Class_Fields SalesOrderHistory.xml:quantity SalesOrderHistory.xml:quantity SalesOrderHistory.xml:quantity SalesOrderHistory.xml:quantity SalesOrderHistory.xml:quantity SalesOrderHistory.xml:quantity SalesOrderHistory.xml:quantity
CoProduct.dat
ColumnName
Use this file to define the co-product of a manufacturing process. Field Name
COMPONENT_NAME
Component Name
CO_PRODUCT_NAME
Co-product Name Spilt Primary Flag Organization Code Source Instance Code Deleted Flag
SPLIT PRIMARY_FLAG ORGANIZATION_CODE SR_INSTANCE_CODE DELETED_FLAG
COMPANY_NAME
Company Name
MSC_ST_CO_PRODUCTS
fine the co-product of a manufacturing process. Description
The name of the component for which the CO-product is defined.
The CO-product name for the component. The split percentage indicating the percentage of each CO-product Normally the primary CO-product has the highest percent value. Valid values are: 1 - Primary CO-product, 2 - Non-primary CO-product Organization Identifier on the planning server. Source instance code defined on the planning server. Valid values are: 1 - Yes, 2 - No. If 1, then this row is deleted. Required only for Collaborative Planning. You should provide the party name with which the company is registered in CP. For a planning (APS) only environment, this should be left null.
Used when there is more than one product exists in produceditemList for Operations Co product/bi product is identified in E1 by a "C" or a "B"
Return to Entity List Mapping Where there are multiple items in the producedItemList, this would be the item that appears in the operation code or is marked as the primary product Where there are multiple items in the producedItemList, this would be the other produced item (that is, the one that does NOT appear in the operation code or is marked as the primary product) Determined from the quantity on the coproduct and the total of all products in the produceditemlist indicate if it is a principal output or not. Manufacturing.xml:operation:operation Code (first component) Parameter.Source_Instance "2"
ComponentSubstitute.dat - MSC_ST_COMPONENT
ColumnName ORGANIZATION_CODE BOM_NAME ASSEMBLY_NAME
Use this file to define component's substitutes belonging to an item's bill of material Field Name Organization Code BOM Name Assembly Name Component Name Substitute Item Name Usage Quantity
COMPONENT_NAME
SUB_ITEM_NAME USAGE_QUANTITY PRIORITY
Priority Source Instance Code Alternate BOM Designator ALTERNATE_BOM_DESIGNATOR

SR_INSTANCE_CODE OPERATION_SEQ_CODE
Operation Seq code
COMPANY_NAME EFFECTIVITY_DATE ROUNDING_DIRECTION
Company Name Effectivity Date Rounding Direction
ntSubstitute.dat - MSC_ST_COMPONENT_SUBSTITUTES
fine component's substitutes belonging to an item's bill of material Description Organization Identifier on the planning server. Bill of material name. Defaults to Assembly Name if null. Item name. Component's item name. Substitute Item name for the Component's item name. Component's quantity per assembly. Priority of the Substituted Item. Source Instance Code is defined on the planning server. Alternate BOM's reference. Identifier or code for a single step in an operation sequence. Required only for Collaborative Planning. You should provide the party name with which the company is registered in CP. For a planning (APS) only environment, this should be left null. Date from which the component becomes effective on the bill of material. Rounding Direction.
Primarily retreived from consumedItemSet in Operation using the components NOT ;list in BOMComponent Substitutes are not being extracted from E1 SO this file will always be empty until we upgrade the extracts
Return to Entity List Mapping Manufacturing.xml:routing:routingCode (first component) Manufacturing.xml:routing:routingCode (second component) Manufacturing.xml:routing:routingCode (second component) Manufacturing.xml:operation:consumedItemSet :consumedItemBom:itemCode (from lowest priorty record in consumedItemSet) Manufacturing.xml:operation:consumedItemSet :consumedItemBom:itemCode (lower priority consumed items) Manufacturing.xml:operation:consumedItemBo m:quantity Manufacturing.xml:operation:consumedItemBo m:preference Parameters.Source_Instance <null> Calculated from Operation Network for Routing
Parameter.CP_Company_Name operation:consumedItemSet:consumedItemBo m:timeVaryingEvent:effectiveDate Parameter.Rounding_Direction
PartnerContact.dat
Use this file to define the contacts for your trading partner sites. Only one contact can exist for each trading p Field Name Partner Name TP Site Code Partner Type Name Source Instance Code Display Name Email Fax Deleted Flag
Company Name
ntact.dat
fine the contacts for your trading partner sites. Only one contact can exist for each trading partner site. Description Name of the trading partner company Trading partner site code Valid values are: 1 - Vendor, 2 - Customer, 3 - Organization , 4 - Others Name of individual partner contact Source instance code defined on the planning server Partner's display name. Partner's email address. Partner's FAX number Valid values are: 1 - Yes, 2- No. If 1 then this row is deleted Required only for Collaborative Planning. You should provide the party name with which the company is registered in Collaborative Planning. For a planning (APS) only environment, this should be left null.
rading partner site.
Project.dat
Use this file to specify attributes of a project. Field Name Project Number Seiban Number Flag Organization Code Task Number Source Instance Code Project Description Planning Group WIP Account Class Code Costing Group Code Material Account Project Start Date Project Completion Date Description Manager Start Date End Date Manager Contact
Company Name
ecify attributes of a project. Description Project name Flag indicating whether project_id identifies a project or seiban. Organization code for legacy users. Task name Source instance code defined on the planning server. Project description Planning group assigned to this project. Default WIP accounting class assigned to this project. Costing group code assigned to this project.
Task description Manager of the task Effective date of the task Disable date of the task Manager contact Required only for Collaborative Planning. You should provide the party name with which the company is registered in CP. For a planning (APS) only environment, this should be left null.
SubInventory.dat
Use this file to define a sub-inventory or subdivision of an organization, representing a physical area or logica Field Name Organization Code Sub Inventory Code Source Instance Code Description Disable Date Netting Type Demand Class Project Number Task Number Inventory ATP Code
Company Name Resource Name SR Customer Account ID Condition Type
ory.dat
fine a sub-inventory or subdivision of an organization, representing a physical area or logical grouping of items such as a Description Organization code for legacy users. Code or identifier for a sub-inventory. Source instance code defined on the planning server. Description of sub-inventory.
Name of identifier of a demand class.
Required only for Collaborative Planning. You should provide the party name with which the company is registered in Collaborative Planning. For a planning (APS) only environment, this should be left null. Owner Resource name .Only used by SRP(optional). Source side customer account id. Only used by SRP(optional). Type of subinventory. Valid values are: G-Good, B-Bad. Only used by SRP. If condition_type is other than G and B it is defaulted to G.
or logical grouping of items such as a storeroom or a receiving dock.
SupplierCapacity.dat
Use this file to load supplier's capacity for items and sites. Field Name Organization Code Item Name Vendor Name From Date Capacity Source Instance Code Vendor Site Code To Date Deleted Flag
Company Name
apacity.dat
ad supplier's capacity for items and sites. Description Organization code for legacy users. Inventory item name Supplier name First date of valid capacity Capacity Source instance code defined on the planning server. Supplier site code. Last date of valid capacity. Valid values are: 1 - Yes, 2 - No. If 1, then this row is deleted. Required only for Collaborative Planning. You should provide the party name with which the company is registered in Collaborative Planning. For a planning (APS) only environment, this should be left null.
SupplierFlexFence.dat
Use this file to define a supplier's ability to adjust capacity over a time period Field Name Organization Code Vendor Name Fence Days Source Instance Code Item Name Vendor Site Code Tolerance Percentage Deleted Flag
Company Name
lexFence.dat
fine a supplier's ability to adjust capacity over a time period Description Organization code for legacy users. Vendor name should exist in the MSC_ITEM_SUPPLIERS table. Number of advance days. Source instance code defined on the planning server. Inventory item name. Supplier site code should exist in the MSC_ITEM_SUPPLIERS table. Capacity tolerance percentage. Valid values are: 1 - Yes, 2 - No. If 1, then this row is deleted. Required only for Collaborative Planning. You should provide the party name with which the company is registered in Collaborative Planning. For a planning (APS) only environment, this should be left null.
IROSupplies.dat
Use this file to define Internal Repair Order Supplies. Field Name Item Name Organization Code New Schedule Date Repair Number Source Instance Code Revision New Order Quantity Project Number Task Number Deleted Flag UOM Code Customer Product ID Source Repair Type ID RO Status Code Asset Serial Number Source Repair Group ID Schedule Priority RO Creation Date Repair Lead Time
es.dat
fine Internal Repair Order Supplies. Description Name of the item. Organization Code New Schedule Date. This should not be null. Repair Number Source instance code defined on the planning server. Revision Please give a value here. This should not be NULL. Project Number Task Number Valid values are: 1 - Yes, 2 - No. If 1, then this row is deleted. Please give a valid UOM Code. Customer Product ID Source Repair Type ID RO Status Code Asset Serial Number Source Repair Group ID Schedule Priority Repair Order Creation Date. This should not be null. Repair Lead Time
IRODemand.dat
Use this file to define Internal Repair Order Demand. Field Name Item Name Organization Code Using Requirement Quantity Repair Number WIP Entity Name Operation Sequence Number Using Assembly Demand Date Source Instance Code Using Assembly Item Name Project Number Task Number Demand Class Deleted Flag RO Status Code Quantity Issued Component Scaling Type Component Yield Factor
fine Internal Repair Order Demand. Description Name of the item. Organization Code. Using Requirement Quantity. This should not be null. Repair Number. This should not be null. If it is null, value of Repair Number gets substituted in this field. Operation Seq Number. If value is not specified, defaults to 1. Using Assembly Demand Date. This should not be null. Source instance code defined on the planning server. Using Assembly Item Name. Project Number Task Number Demand Class Valid values are: 1 - Yes, 2 - No. If 1, then this row is deleted. RO Status Code Quantity Issued Component Scaling Type. Component Yield Factor.
EROSupplies.dat
Use this file to define External Repair Order Supplies. Field Name Item Name Organization Code New Schedule Date Firm Planned Type WIP Entity Name Source Instance Code Revision Unit Number New WIP Start Date New Order Quantity Alternated BOM Designator Alternate Routing Designator Line Code Project Number Task Number Planning Group Schedule Group Name Build Sequence WO Lateness Cost Implement Processing Days Late Supply Date Late Supply Qty Qty Scrapped Qty Completed WIP Status Code Bill Name Routing Name Deleted Flag
Company Name Co-Products Supply Quantity Per Assembly Quantity Issued
WIP Start Quantity Operation Seq Code Effectivity Date Job Op Seq Code Jump Op Seq Code Jump Op Effectivity Date
Source Org ID
Source Project ID
Source Task ID
Source supply ID
Source Bill Sequence ID
Source Routing Sequence ID
Source Schedule Group ID
Source Wip Entity ID Actual Start Date
lies.dat
fine External Repair Order Supplies. Description Inventory item name Organization End date of the supply. WIP completion date. Flag indicating whether the order is firm or not. WIP entity name. Source instance code defined on the planning server. Inventory item revision code Unit number. New WIP schedule start date. Supply quantity. Alternate BOM designator. Alternate routing designator. Project name. Task name. Project planning group. If more than one project belongs to the same planning group, this column is used to net the demand/supply across projects. Build sequence for the planned order. Related with the SCHEDULE_GROUP_ID. Within the schedule, each job has a different build sequence ID. Work order lateness cost. Required by SCO to minimize the cost according to Key Performance Indicators (KPIs) specified by the planner on the plan options form. Implement processing days Supply date for the shadow part of the split supplies. Used by HLS. Shadow supply quantity. Used by HLS. Current job scrapped units. Current job quantity completed. WIP job status code. BOM should exist in MSC_BOMS. Routing should exist in MSC_ROUTINGS. Valid values are: 1 - Yes, 2 - No. If 1, then this row is deleted. Required only for Collaborative Planning. You should provide the party name with which the company is registered in Collaborative Planning. For a planning (APS) only environment, this should be left null. Part usage quantity Quantity Issued
WIP Start Quantity. Operation Sequence Code Effectivity Date Job sequence number of the current operation. Populated only for lot-based jobs Routing sequence number of the jumped operation. If the operation is outside the network then a value of 50000 is populated. Populated only for lot-based jobs. Jumped Operation Effectivity Date Please provide the Organization ID for the Organization in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Inventory Item ID for the Inventory Item in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Project ID for the Project in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Task ID for the Task in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide a unique ID to identify this supply in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only Please provide the Disposition ID for the Supply in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Bill Sequence ID for the Bill Sequence in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Routing Sequence ID for the Routing Sequence in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Schedule Group ID for the Schedule Group in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Wip Entity ID for the Wip Entity in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Actual Start Date.
ERODemand.dat
Use this file to define External Repair Order Demand. Field Name Item Name Organization Code Using Requirement Quantity WIP Entity Name Using Assembly Demand Date Source Instance Code Using Assembly Item Name Operation Sequence Code Project Number Task Number Planning Group End Item Unit Number Demand Class Order Number WIP Status Code WIP Supply Type Deleted Flag
Company Name Routing Name Alternate Routing Designator Operation Effectivity Date Quantity Per Assembly Quantity Issued
Source Org ID
Source WIP Entity ID
Source Project ID
Source Task ID Component Scaling Type Component Yield Factor
and.dat
fine External Repair Order Demand. Description Inventory item name. Component name for which dependent demand exists. This comes from Production Discrete job. Organization Required quantity for a component. Job name. Operation requirement start date, where this component is going to be used. Instance code defined on the planning server. Assembly item name for which job is created in WIP. Operation Sequence Code. Project identifier. This should be predefined in MSC_PROJECTS. Task identifier. This should be predefined in MSC_PROJECTS_TASKS. Project planning group End Item Unit Number. Name or identifier of a demand class. Order Number. Job status. Valid values are: 1 - Unreleased, 3 - Released, 4 - Complete, 6 - On Hold, 7 Canceled, 12 - Closed. Supply type. Valid values are: 1 - Push, 2 - Assembly Pull, 3 - Operation Pull, 4 - Bulk, 5 - Supplier, 6 - Phantom, 7 - Based on Bill. Valid values are: 1 - Yes, 2 - No. If 1, then is row is deleted. Required only for Collaborative Planning. You should provide the party name with which the company is registered in CP. For a planning (APS) only environment, this should be left null. Routing Name. Alternate Routing Designator. Operation Effectivity Date. Part usage quantity Quantity issued Please provide the Organization ID for the Organization in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Inventory Item ID for the Item in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only.
Please provide the Assembly Item ID for the Assembly Item in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the WIP Entity ID for the Assembly Item in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Sales Order Line ID for the Sales Order Line in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Project ID for the Project in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Please provide the Task ID for the Task in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. Component Scaling Type. component Yield Factor.
CompanyUser.dat
Use this file to associate a user to a company in APS. An existing user in Oracle ERP can be associated to a co Field Name User Name Company Name Source Instance Code
User.dat
sociate a user to a company in APS. An existing user in Oracle ERP can be associated to a company using this file. This fi Description User name Name of the company that the user is associated with. Source instance code defined on the planning server
d to a company using this file. This file must be used to load third party users on CP/APS. Since these third party compan
e these third party companies are not directly interacting with the OEM, they must be setup using flat files. Note: If a new
up using flat files. Note: If a new user who is not associated with a customer or supplier is created on the ERP/APS and a
s created on the ERP/APS and a full data collection is run before loading the CompanyUser.dat file, the new user automa
er.dat file, the new user automatically becomes part of the OEM who owns the APS/ERP.
CustomerItem.dat
Use this file to specify your customer items that are cross-referenced to master items. Field Name Item Name Customer Item Name Description Customer Name Customer Site Name Source Instance Code Lead Time UOM Code List Price Planner Code
Company Name
Item.dat
ecify your customer items that are cross-referenced to master items. Description Inventory item name Customer item name Item description Customer name Customer name Source instance code defined on the planning server Processing lead time of supplier Unit of Measure code. List Price. Planner Code Required only for Collaborative Planning. You should provide the party name with which the company is registered in Collaborative Planning. For a planning (APS) only environment, this should be left null
Group.dat
Use this file to load trading partner groups' information into Collaborative Planning. Field Name Group Name Description Group Type
Contact User Name Contract Doc URL Effective From Date Effective To Date Source Instance Code Context Attribute1 Attribute2 Attribute3 Attribute4 Attribute5 Attribute6 Attribute7 Attribute8 Attribute9 Attribute10 Attribute11 Attribute12 Attribute13 Attribute14 Attribute15
ad trading partner groups' information into Collaborative Planning. Description Name of trading partner group. Description of trading partner group. Whether the group is public or private. Valid values are: 1 - Public, 2 - Private Name of the contact user from the group owner company. Group owner company is the company loading group definition. The user should be a valid user in the system and should be associated with the same company from which the group definition is getting loaded. URL pointing to group's contract document. The date from which the group is effective. The date to which the group is effective. Source instance code defined on the planning server. Context column used for descriptive flex-field. Attribute column used for descriptive flex-field. Attribute column used for descriptive flex-field. Attribute column used for descriptive flex-field. Attribute column used for descriptive flex-field. Attribute column used for descriptive flex-field. Attribute column used for descriptive flex-field. Attribute column used for descriptive flex-field. Attribute column used for descriptive flex-field. Attribute column used for descriptive flex-field. Attribute column used for descriptive flex-field. Attribute column used for descriptive flex-field. Attribute column used for descriptive flex-field. Attribute column used for descriptive flex-field. Attribute column used for descriptive flex-field. Attribute column used for descriptive flex-field.
GroupCompany.dat
Use this file to load member companies of a trading partner group. You can load members for multiple group Field Name Group Name Company Name Effective From Date Effective To Date Contact User Name Source Instance Code Context Attribute1 Attribute2 Attribute3 Attribute4 Attribute5 Attribute6 Attribute7 Attribute8 Attribute9 Attribute10 Attribute11 Attribute12 Attribute13 Attribute14 Attribute15
mpany.dat
ad member companies of a trading partner group. You can load members for multiple groups in the same file. Description Name of trading partner group. Name of company. The date from which the membership is effective. The date to which the membership is effective. Name of the member company's contact person for the group. Source instance code defined on the planning server. Context column used for descriptive flex-field. Attribute column used for descriptive flex-field. Attribute column used for descriptive flex-field. Attribute column used for descriptive flex-field. Attribute column used for descriptive flex-field. Attribute column used for descriptive flex-field. Attribute column used for descriptive flex-field. Attribute column used for descriptive flex-field. Attribute column used for descriptive flex-field. Attribute column used for descriptive flex-field. Attribute column used for descriptive flex-field. Attribute column used for descriptive flex-field. Attribute column used for descriptive flex-field. Attribute column used for descriptive flex-field. Attribute column used for descriptive flex-field. Attribute column used for descriptive flex-field.
le groups in the same file.
SerialNumber.dat
Use this file to load serial number level details for Unallocated Onhand Field Name Sync Indicator Publisher Company Publisher Site
Order Type Master Item Name Publisher Item Name Serial Number Attachment URL User Defined1 User Defined2 User Defined3 User Defined4 User Defined5 User Defined6 User Defined7 User Defined8 User Defined9 User Defined10 Context Attribute1 Attribute2 Attribute3 Attribute4 Attribute5 Attribute6 Attribute7 Attribute8 Attribute9 Attribute10 Attribute11 Attribute12 Attribute13 Attribute14 Attribute15 Line ID
mber.dat
ad serial number level details for Unallocated Onhand Description Valid values are: R - Replace an existing record; if one does not exist, a new record is created, D - Delete an existing record. Company publishing the onhand data. Publishing company's site for which the inhand is posted. Should be "Unallocated Onhand". If you have renamed this order type in your system to another equivalent name, you have to provide its equivalent order type name in this field. Name of master item. Name of publisher's item.. Serial number of the unit. URL pointing to any attached document. Column used for user defined field. Column used for user defined field. Column used for user defined field. Column used for user defined field. Column used for user defined field. Column used for user defined field. Column used for user defined field. Column used for user defined field. Column used for user defined field. Column used for user defined field. Context column used for descriptive flex-field. Attribute column used for descriptive flex-field. Attribute column used for descriptive flex-field. Attribute column used for descriptive flex-field. Attribute column used for descriptive flex-field. Attribute column used for descriptive flex-field. Attribute column used for descriptive flex-field. Attribute column used for descriptive flex-field. Attribute column used for descriptive flex-field. Attribute column used for descriptive flex-field. Attribute column used for descriptive flex-field. Attribute column used for descriptive flex-field. Attribute column used for descriptive flex-field. Attribute column used for descriptive flex-field. Attribute column used for descriptive flex-field. Attribute column used for descriptive flex-field. Contains the line identifier.
OSFMMaterialRequirement.dat
Use this file to define OFSM material requirement in different operations. Field Name WIP Entity Name Organization code Operation Seq Code Source Instance Code Component Name Assembly Item Name Routing Name Alternate Routing Designator WIP Supply type Primary Component Name Recommended Recommended Date Required Component Priority Department Code Quantity Per Assembly Component Yield Factor Effectivity Date Planning Factor Low Quantity High Quantity Operation lead time percent From end item unit number To end item unit number Deleted Flag Company Name Alternate BOM designator Operation effectivity date Source Phantom Name
erialRequirement.dat
fine OFSM material requirement in different operations. Description WIP Entity Name. Organization code. Operation Sequence Code. Source instance code on the planning server.. Component item identifier. Name of the Assembly Item. Routing identifier of that particulat operation. Alternate routing designator WIP Supply type. Component Identifier of the Primary Component for the current Component. Recommended by planning or scheduling; or user preferred. Operation requirement start date ,Recommended by planning or scheduling; or user preferred. Priority of Component. Department Code. Quantity of component in bill of material. Factor used to multiply component quantity with to obtain required component quantity. Effective date. Factor used to multiply component quantity with to obtain planning quantity. Minimum quantity allowed on an order. Maximum quantity allowed on an order. Operation offset from first operation in routing. From End Item Unit Number. To End Item Unit Number. Yes/No flag indicates whether corresponding record in ODS will be deleted. Company Name. Alternate BOM designator. Operation effectivity date. Source phantom item name
OSFMOperationResource.dat
Use this file to define OFSM operation resources Field Name WIP Entity Name Organization code Operation Seq Code Source Instance Code Routing Name Item Name Alternate Routing Designator Resource Sequence Code Alternate Number Recommended Recommended Start Date Recommended Completion Date Resoucre Code Assigned units Usage rate or amount UOM code Basis Type Schedule Flag Resource Offset percent Schedule sequence number Principal flag Department Code Operation Effectivity Date Activity Group ID
rationResource.dat
fine OFSM operation resources Description WIP Entity Name. Organization code. Operation Sequence Code. Source instance code on the planning server.. Routing identifier of that particulat operation. Item Name. Alternate routing designator Resource Sequence Code. Alternate Number. Recommended by planning or scheduling; or user preferred. Scheduled start date of the resource , Recommended by planning or scheduling; or user preferred. Scheduled completion date of the resource , Recommended by planning or scheduling; or user preferred. Resoucre Code. Assigned units. Resource usage rate. Unit of measure code. Basis type identifier. Schedule flag. Resource offset percent from the start of the routing. Schedule sequence number. Principal flag. Department Code. Operation Effectivity Date. Activity Group ID .
OSFMOperation.dat
Use this file to define OFSM operations. Field Name WIP Entity Name Organization code Operation Seq Code Source Instance Code Routing Name Assembly Name Alternate Routing Designator Recommended Start Date Recommended Completion Date Recommended Standard Operation Code Network Start End Department Code Operation lead time percent Minimum transfer quantity Effectivity Date Disable Date Operation Type Yield Cummulative Yield Reverse Cummulative Yield Net planning percent Deleted Flag Company Name
ration.dat
fine OFSM operations. Description WIP Entity Name. Organization code. Operation Sequence Code. Source instance code on the planning server.. Routing identifier of that particulat operation. Assembly Name. Alternate routing designator Scheduled start date of the resource , Recommended by planning or scheduling; or user preferred. Scheduled completion date of the resource , Recommended by planning or scheduling; or user preferred. Recommended by planning or scheduling; or user preferred. Standard Operation Code. Specifies Start or End Operation of Network Routing. Department Code. Indicates the amount of overlap its lead time has with the parent's lead time. Minimum operation transfer quantity. Date operation is effective. Date operation is no longer effective effectivity lasts until the end of the disable date. Process Line Operation or Event. Process yield at this operation. Cumulative process yield from beginning of routing to this operation. Cumulative process yield from end of routing to comparable operation. Cumulative planning percents derived from the operation network. Yes/No flag indicates whether corresponding record in ODS will be deleted. Company Name
OSFMOperationNetwork.dat
Use this file to define OFSM operation network Field Name WIP Entity Name Organization code From Operation Seq Code To Operation Seq Code From Operation effectivity date To Operation effectivity date Routing Name Assembly Name Source Instance Code Alternate Routing Designator Transition Type Planning percent Recommended Company Name Deleted Flag
rationNetwork.dat
fine OFSM operation network Description WIP Entity Name. Organization code. From Operation Sequence Code. To Operation Sequence Code. From routing operation effectivity date. To routing operation effectivity date. Routing identifier of that particulat operation. Assembly Name. Source instance code on the planning server.. Alternate routing designator Primary Alternate or Rework connection. Planning Percentage. Recommended by planning or scheduling; or user preferred. Company Name. Yes/No flag indicates whether corresponding record in ODS will be deleted.
Profile.dat
Use this file to define the profile option values at instance level. Field Name Source Instance Code MSC_ORG_FOR_BOM_EX PLOSION WSM_CREATE_LBJ_COP Y_ROUTING
fine the profile option values at instance level. Description Source Instance Code. MSC: organization containing generic BOM for forecast explosion. WSM: Create Lot Based Job Copy Routing.
ShipmentData.dat
Use this file to specify your customer items that are cross-referenced to master items. Field Name Source Instance Code Inv Org Item Customer Sales Channel Sales Representative Ship To Loc User Defined Level1 User Defined1 User Defined Level 2 User Defined2 Demand Class Booked Date Requested Date Promised Date Shipped Date Schedule Ship Date Schedule Arrival Date Amount Quantity Shipped Original Item Parent Item Name
Data.dat
ecify your customer items that are cross-referenced to master items. Description Source instance code defined on the planning server. Organization identifier on the planning server. The Inv Org is the same as the Organization. Inventory item name. Customer name;No Validation is being done against this column. This column has been obsoleted and has been retained for the sake of backward compatibility Sales channel through which order is fulfilled. Sales representative. Ship-to location.
Name of the Demand Class.Defaulted, if not provided. Date the order is booked. Date the order is requested; customer's request date. Date the order is promised. Date the order is shipped.
Amount in the demand plan currency. Quantity The name of the Parent Item
BookingData.dat
Use this file to load order bookings used in Oracle Demand Planning. Field Name Source Instance Code Inv Org Item Customer Sales Channel Sales Rep Ship To Loc User Defined Level 1 User Defined 1 User Defined Level 2 User Defined 2 Demand Class Booked Date Requested Date Promised Date Scheduled Date Schedule Arrival Date Amount Dollar Quantity Ordered Original Item Parent Item Name
ata.dat
ad order bookings used in Oracle Demand Planning. Description Source Instance Code is defined on the planning server. Organization Identifier on the planner server. The Inv Org is the same as the Organization Code. The name of the item being ordered. Customer name. No Validation is being done against this column. This column has been obsoleted and has been retained for the sake of backward compatibility Name of the sales channel. Name of the sales representative. Ship to location.
Name of the Demand Class.Defaulted, if not provided. Date the order was booked. Request date on order. Promise date on order. Date order is scheduled to arrive at the customer's location. Amount of value of the order. Quantity of the item ordered. The name of the Parent Item
CompositeCalendar.dat
Use this file to define composite calendar in demand planning. Field Name Source Instance Code Calendar Code Year Year Description Year Start Date Year End Date Quarter Quarter Description Quarter Start Date Quarter End Date Month Month Description Month Start Date Month End Date Week Week Description Week Start Date Week End Date
eCalendar.dat
fine composite calendar in demand planning. Description Source instance code defined on the planning server. Identifier or code for calendar. Identifier for year Description of the year Start date of the year. End date of the year. Identifier for the quarter Description of the quarter Start date of the quarter. End date of the quarter. Identifier for the month or period. Description of the month Start date of the month. End date of the month. Identifier for the week. Description of the week Start date of the week. End date of the week.
CSData.dat
Use this file to upload Custom Stream Data used in Oracle Demand Planning.This .dat file can be used for loa Field Name Source Instance Code Data Stream Name Data Stream Designator Delete Flag Product Level Product Level Value Geography Level Geography Level Value Ship From Location Level Ship From Location Level Value Parent Item Level Parent Item Name Sales Representative Level Sales Representative Level Value Sales Channel Level Sales Channel Level Value User Defined Dimension 1 Level User Defined Dimension 1 Level Value User Defined Dimension 2 Level User Defined Dimension 2 Level Value Demand Class Level Demand Class Level Value Time Level ID QUANTITY AMOUNT END_DATE PRICE CS Data ID
pload Custom Stream Data used in Oracle Demand Planning.This .dat file can be used for loading manufacturing forecas Description Source instance code defined on the planning server. Custom Stream Definition Name. Stream Name. This column is no longer used.Kept for backward compatibility Level name for the Product Dimension Level value for the Product Dimension Level name for the Geography Dimension. Level value for the Geography Dimension. Level name for the Ship From Location Dimension. Level value for the Ship From Location Dimension Parent Item Level.Auto populated by the validation program whenever value is provided for Parent Item Name. Parent Item Name or Sub assembly Name. Level name for the Sales Representative Dimension. Level value for the Sales Representative Dimension. Level name for the Sales Channel Dimension. Level value for the Sales Channel Dimension. Level name for the User Defined Dimension 1. Level value for the User Defined Dimension 1. Level name for the User Defined Dimension 2. Level value for the User Defined Dimension 2. Level name for the Demand Class Dimension. Level value for the Demand Class Dimension. Level Identifier for Time Dimension. Quantity Amount Date,YYYY/MM/DD Price Pseudo Data ID Column , not to be entered by the user.
d for loading manufacturing forecast in demand Planning.
LevelAssociation.dat
Use this file to define a hierarchy or level associations in demand planning. Field Name Source Instance Code Level Name Sr. Level Value Parent Level Name Sr. Parent Level Value Attribute1 Attribute2 Attribute3 Attribute4 Attribute5
ociation.dat
fine a hierarchy or level associations in demand planning. Description Source instance code defined on the planning server. Name of a level in a demand planning hierarchy. Value of this level. Name of the parent's level in the demand planning hierarchy. Value of the parent level.
LevelOrgAsscns.dat
Use this file to load the Level Org Associations Field Name Source Instance Code Level Name Level Value Org Level Name Org Level Value
Asscns.dat
ad the Level Org Associations Description Source instance code defined on the planning server. Name of the level in a demand planning hierarchy. Value of the level. Organization level Name. Organization Level value.
LevelValue.dat
Use this file to define level members within a level of a demand planning hierarchy. Field Name Source Instance Code Level Name Level Value Level Value Description Attribute1 Attribute2 Attribute3 Attribute4 Attribute5
fine level members within a level of a demand planning hierarchy. Description Source instance code defined on the planning server. Name of the level in a demand planning hierarchy. Value of the level. Description of the level value.
SetupParameter.dat
Use this file to upload application parameters for Oracle Demand Planning, such as Master organization, Cat Field Name Source Instance Code Parameter Value Parameter Field
ameter.dat
pload application parameters for Oracle Demand Planning, such as Master organization, Category Set, Demand Planning Description Source instance code defined on the planning server.
ion, Category Set, Demand Planning currency, and so on.

E1-VCP Mapping 2011-01-12 AIA 3 1 Release

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

E1-VCP Mapping 2011-01-12 AIA 3 1 Release

Uploaded by

Copyright:

Available Formats

This document defines the mapping for the E1 to VCP integration and the

Flow from E1 Extracts to VCP

Category Sets Item Categories Safety Stocks

Price List Item Substitutes Resource Groups

Work Order Component Demands Resource Requirements

PromotionPricing Delete_PromotionPricing DeductionDisposition Claim

Column headings for XML files

File mapping definitions

Unused ODS Legacy Mapping

*99 Old Demand Planning

to VCP integration and the return publish

arent UBE that generates them)

th the parent UBE that generates it

s not supported / populated by E1

Table Description VCP-ODS

CALENDAR_CODE CALENDAR_START_DATE CALENDAR_END_DATE QUARTERLY_CALENDAR_TYPE SR_INSTANCE_CODE DESCRIPTION WEEK_START_DAY

Fields Referenced Calendar.txt:BranchPlant Calendar.txt:WorkCenter Calendar.txt:Calendar Type Calendar.txt:Calendar Name

Return to File Definitions Comment

Table Description VCP-ODS

CALENDAR_CODE DAYS_ON DAYS_OFF SR_INSTANCE_CODE

SHIFT_NUM SHIFT_NAME DESCRIPTION

Workday calendar identifier. Should refer to a valid calendar code in MSC_CALENDARS.

Source instance code defined on the planning server.

Fields Referenced Calendar.txt:BranchPlant Calendar.txt:WorkCenter Calendar.txt:Calendar Type Calendar.txt:Calendar Name

E1 Table F0007 F0007 F0007 F0007

E1 Field MMCU MCU WDCT WDCK

Return to File Definitions Comment

Table Description VCP-ODS

CALENDAR_CODE SHIFT_NAME SR_INSTANCE_CODE FROM_TIME TO_TIME

Fields Referenced Calendar.txt:BranchPlant Calendar.txt:WorkCenter Calendar.txt:Calendar Type Calendar.txt:Calendar Name

E1 Table F0007 F0007 F0007 F0007

E1 Field MMCU MCU WDCT WDCK

ith the user

Return to File Definitions Comment

Table Description VCP-ODS

MSC_CALENDAR_EXCEPTIONS EXCEPTION_DATE EXCEPTION_TYPE SR_INSTANCE_CODE

Return to File Definitions

Table Description VCP-ODS

CALENDAR_CODE EXCEPTION_DATE EXCEPTION_TYPE SR_INSTANCE_CODE SHIFT_NAME

Fields Referenced Calendar.txt:BranchPlant Calendar.txt:WorkCenter Calendar.txt:Calendar Type Calendar.txt:Calendar Name

E1 Table F0007 F0007 F0007 F0007

E1 Field MMCU MCU WDCT WDCK

Return to File Definitions Comment

Table Description VCP-ODS

@ Association Type Valid values are: Value 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

Association type 10,11 7,8 9 5,6 1,2 3 4

Partner_name Not Null Not Null Not Null Not Null

Supplier.xml:supplierList:supplier:supplierCode <null> Parameter.Source_Instance <null> <null> <null> decode(ASSOCIATION_TYPE,11,1,10,1,9,3,8,3,7,3,6,2,5,2,4,4,3,4,2,4,1,4)

Return to File Definitions Comment

Table Description VCP-ODS

BASE_UOM_FLAG SR_INSTANCE_CODE DISABLE_DATE DESCRIPTION

Aggregated values for Base.xml:item for each of the listed UOMs.

Base.xml:item:shippingUom Base.xml:item:weightUom Base.xml:item:volumeUom Base.xml:itemUom:toUOM

F34A10 F4101 F4101 V41003A

assignment UWUM UVM1

Table Description VCP-ODS

UNIT_OF_MEASURE UOM_CODE UOM_CLASS

DEFAULT_CONVERSION_FLAG SR_INSTANCE_CODE DISABLE_DATE ITEM_NAME

sions Logic Fields Referenced E1 Table E1 Field

Base.xml:itemUom:toUom see UNIT_OF_MEASURE see UOM_CLASS from Unit of Measure mapping

1/Base.xml:itemUom:factor * Base_UOM_Conv(# see below) Base.xml:itemUom:factor

"1" if from itemUom Parameter.Source_Instance <null> Base.xml:itemUom:itemCode Base.xml:itemUom:itemCode F41002 ITM

Table Description VCP-ODS

CONVERSION_RATE SR_INSTANCE_CODE DISABLE_DATE ITEM_NAME