Entity ListThis document defines the mapping for the E1 to VCP integration and the return publish There are two sets of worksheets: E1:Extract/Import file Mapping and ODS:File Mapping

ODS MappingNotes:Sections highlighted at the end of the worksheet define high level selection criteriaField 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", etc.References to fields from the files use the following structure:For XML files: "::"For flat files (including User Defined Data) ":"Flow from E1 Extracts to VCPEntity GroupEntity NameOA Template File name*02 CalendarCalendarsCalendar*02 CalendarWorkday PatternsWorkdayPatterns*02 CalendarShift TimesShiftTime*02 CalendarCalendar ExceptionsCalendarException*02 CalendarShift ExceptionsShiftException*99 Existing Demantra IntegCalendarAssignmentsCalendarAssignments*04 Unit of MeasureUnits of MeasuresUOM*04 Unit of MeasureUnits of Measure ConversionsUOMConversion*04 Unit of MeasureUnits of Measure Class ConversionsUOMClassConversion*05 Analysis CodesDemand ClassesDemandClass*05 Analysis CodesSales Channel SalesChannel*05 Analysis CodesPlannersPlanner*07 Trading PartnersTrading Partners - SuppliersTradingPartner*07 Trading PartnersTrading Partners - CustomersTradingPartner*07 Trading PartnersTrading Partners - OrganizationsTradingPartner*07 Trading PartnersTrading Partner Sites - SuppliersTradingPartnerSite*07 Trading PartnersTrading Partner Sites- CustomersTradingPartnerSite*07 Trading PartnersTrading Partner Sites- OrganizationsTradingPartnerSite*07 Trading PartnersLocation Associations - SuppliersLocationAssociation*07 Trading PartnersLocation Associations - CustomersLocationAssociation*07 Trading PartnersLocation Associations - OrganizationsLocationAssociation*10 ItemItems - MainItem*10 ItemItems - Master Product FamiliesItem*10 Item Category SetsCategorySet*10 ItemItem CategoriesCategory*10 ItemSafety StocksSafetyStock*10 ItemOnhand SuppliesSupplyOnhand*10 ItemPrice ListPrice List*15 Item Subst/etc.Item SubstitutesItemSubstitutes*30 ResourcesResource GroupsResourceGroup*30 ResourcesResourcesDepartmentResource*30 ResourcesResource ShiftsResourceShift*40 RoutingsRoutingsRouting*40 RoutingsRouting OperationsRoutingOperation*40 RoutingsOperation ResourcesOperationResource*50 BOMsBills of Material HeadersBOM*50 BOMsBills of Material ComponentsBOMComponent*55 Change Over TablesResource SetupsResource Setups*55 Change Over TablesSetup TransitionsSetup Transitions*55 Change Over TablesStandard Operation ResourcesStandard Operation Resources*63 Distribution and Supply SetupShipping Methods - PurchasingShipmentMethod*63 Distribution and Supply SetupShipping Methods - DistributionShipmentMethod*63 Distribution and Supply SetupShipping Methods - SalesShipmentMethod*63 Distribution and Supply SetupSupplier ItemsSupplierItem*63 Distribution and Supply SetupItem Sourcing - PurchasingSourcingRuleNot used in integration*63 Distribution and Supply SetupItem Sourcing - Inter OrgSourcingRuleNot used in integration*63 Distribution and Supply SetupItem Sourcing - ManufacturingSourcingRuleNot used in integration*63 Distribution and Supply SetupItem Sourcing - CustomersSourcingRuleNot used in integration*65 Supplies TransactionsPurchase Order SuppliesPurchaseOrderSupply*65 Supplies TransactionsRequisition SuppliesPurchaseRequisitionSupply*65 Supplies TransactionsIntransit Supplies - Purchase OrdersSupplyInTransit*65 Supplies TransactionsIntransit Supplies - Transfer OrdersSupplyInTransit*68 Demand TransactionsForecast DemandsDemandForecast*68 Demand TransactionsForecast DesignatorsDesignator*68 Demand TransactionsSales Order Demands(Sales Orders)SalesOrder*68 Demand TransactionsSales Order Demands(Transfer Orders)SalesOrder*70 Work OrdersWork Order SuppliesWorkOrderSupply*70 Work OrdersWork Order Component DemandsDemandWorkOrder*70 Work OrdersResource RequirementsResourceDemand*80 Demantra Flat file extractsDemand HistoryDemHistory.dat (flat file)*80 Demantra Flat file extractsList PriceListPrice.txt*80 Demantra Flat file extractsItemCost.txtItemCost.txt*80 Demantra Flat file extractsPrice HistoryPriceHistory.txt*80 Demantra Flat file extractsAPConfirm.txtAPConfirm.txt*80 Demantra Flat file extractsDeductions.txtDeductions.txtFlow from VCP Plans to E1*90 Publish Files into E1PurchaseplanPublish Purchase Plan to E1*90 Publish Files into E1deploymentplan - MainPublish Transfers to E1*90 Publish Files into E1deploymentplan - DRPPublish Transfers to E1*90 Publish Files into E1Detailed Production PlanPublish Work Orders to E1*90 Publish Files into E1Master Production PlanPublish work order (deletions) to E1*95 Demantra Flat file updatesForecast.txtPublish Forecast.txt to E1*95 Demantra Flat file updatesPromotionPricingPublish Promotion Pricing to E1*95 Demantra Flat file updatesDelete_PromotionPricingPublish "Delete Promotion Pricing" to E1*95 Demantra Flat file updatesDeductionDispositionPublish Deduction Dispositions to E1*95 Demantra Flat file updatesClaimPublish Claims to E1Entries below this line have NOT being integratedEntries below this line have NOT being integrated*70 Work OrdersFiscal CalendarsTime*30 ResourcesUOM ConversionsDPUOMConversion*05 Base DataResources AvailabilityResourceChange*30 ResourcesDemand Schedule DemandsDemandMDS*55 DemandsDemand Schedule DesignatorsDesignatorMDS*55 DemandsPlan Order DesignatorsDesignatorPlanOrder*55 DemandsManufacturing Forecast#ManufacturingForecast#*55 DemandsReservationsReservations*58 ForecastsPlan Order SuppliesPlannedOrderSupply*65 SuppliesSupply DemandSupplyDemand*65 SuppliesCurrency ConversionsCurrencyConversion*15 Item Subst/etc.ItemRelationshipsItemRelationship*15 Item Subst/etc.Item SubstitutesItemSubstitutes*40 RoutingsOperation NetworksOperationNetwork*68 Demand TransactionsPrice List#PriceList#*68 Demand TransactionsBooking and Shipment HistoryDemHistory*90 Publish Files into E1enterpriseforecastPublish to E1*90 Publish Files into E1sourcing recommendationPublish to E1*50 BOMsCo ProductsCOProduct*50 BOMsComponent Substitute ComponentSubstitute*95 OtherPartner ContactsPartnerContact*98 Out of ScopeProject TasksProject*98 Out of ScopeSub InventoriesSubInventory*98 Out of ScopeSupplier CapacitiesSupplierCapacity*98 Out of ScopeSupplier Flex FencesSupplierFlexFence*98 Out of ScopeIROSupplies IROSupplies*98 Out of ScopeIRODemand IRODemand*98 Out of ScopeEROSupplies EROSupplies*98 Out of ScopeERODemand ERODemand*99 CPCompany UsersCompanyUser*99 CPCustomer ItemsCustomerItem*99 CPGroupsGroup*99 CPGroup Company AssociationsGroupCompany*99 CPSerial Number DetailsSerialNumber*99 Not NeededOSFM Material RequirementOSFMMaterialRequirement*99 Not NeededOSFM Operation ResourceOSFMOperationResource*99 Not NeededOSFM OperationOSFMOperation*99 Not NeededOSFM Operation NetworkOSFMOperationNetwork*99 Not NeededProfileProfile*99 Existing Demantra IntegShipment Data#ShipmentData#*99 Existing Demantra IntegBooking Data#BookingData#*99 Old Demand PlanningComposite Calendars#CompositeCalendar#*99 Old Demand PlanningCustom Stream Data#CSData#*99 Old Demand PlanningLevel AssociationsLevelAssociation*99 Old Demand PlanningLevelOrgAsscnsLevelOrgAsscns*99 Old Demand PlanningLevel ValuesLevelValue*99 Old Demand PlanningSetup ParametersSetupParameterE1 MappingWorksheets for XML files have the suffix ".xml" in the work sheet nameWorksheets for flat files will have ".txt" in the work sheet name (followed by the parent UBE that generates them)

Column headings for XML filesE1 TableThe table in E1 where the data is sourced fromE1 FieldThe field name in the above table for this data itemXML Field NameThe field (or tag) name used in the XML fileXML Object NameNotesAny processing notes sasociated with this entryRequiredIs the field a required fieldKeyIs this field part of the key for this entityMissing in E1This XML field is defined in the XML file definition but is not supported / populated by E1Integration UseInternal only

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 itE1 ColumnThe field name in the above table for this data itemE1 NameThe descriptive name for the field nameE1 TableThe table in E1 where the data is sourced fromE1 Integration NotesAny additional notesFile mapping definitionsE1 ExtractsBase.xmlBeginningInventory.xmlCustomer.xmlDistribution.xmlManufacturing.xmlPurchaseOrders.xmlSalesOrders.xmlSupplier.xml TransferOrders.xmlTimeSeries.xmlWorkOrders.xmlCalendar.txt (R34A705)SalesOrderHistory.txt (R34A400)PriceList.txt (R34A400)PriceHistory.txt (R34A400)E1 ImportsDeploymentPlan.xmlPurchasePlan.xmlMasterProductionPlan.xmlDetailedProductionPlan.xmlEnterpriseForecast.xmlUnused ODS Legacy MappingFlow from E1 Extracts to VCPEntity GroupEntity NameOA Template File name*70 Work OrdersFiscal CalendarsTime*30 ResourcesUOM ConversionsDPUOMConversion*05 Base DataResources AvailabilityResourceChange*30 ResourcesDemand Schedule DemandsDemandMDS*55 DemandsDemand Schedule DesignatorsDesignatorMDS*55 DemandsPlan Order DesignatorsDesignatorPlanOrder*55 DemandsManufacturing Forecast#ManufacturingForecast#*55 DemandsReservationsReservations*58 ForecastsPlan Order SuppliesPlannedOrderSupply*65 SuppliesSupply DemandSupplyDemand*65 SuppliesCurrency ConversionsCurrencyConversion*15 Item Subst/etc.ItemRelationshipsItemRelationship*40 RoutingsOperation NetworksOperationNetwork*68 Demand TransactionsPrice List#PriceList#*68 Demand TransactionsBooking and Shipment HistoryDemHistory*50 BOMsCo ProductsCOProduct*50 BOMsComponent Substitute ComponentSubstitute*95 OtherPartner ContactsPartnerContact*98 Out of ScopeProject TasksProject*98 Out of ScopeSub InventoriesSubInventory*98 Out of ScopeSupplier CapacitiesSupplierCapacity*98 Out of ScopeSupplier Flex FencesSupplierFlexFence*98 Out of ScopeIROSupplies IROSupplies*98 Out of ScopeIRODemand IRODemand*98 Out of ScopeEROSupplies EROSupplies*98 Out of ScopeERODemand ERODemand*99 CPCompany UsersCompanyUser*99 CPCustomer ItemsCustomerItem*99 CPGroupsGroup*99 CPGroup Company AssociationsGroupCompany*99 CPSerial Number DetailsSerialNumber*99 Not NeededOSFM Material RequirementOSFMMaterialRequirement*99 Not NeededOSFM Operation ResourceOSFMOperationResource*99 Not NeededOSFM OperationOSFMOperation*99 Not NeededOSFM Operation NetworkOSFMOperationNetwork*99 Not NeededProfileProfile*99 Existing Demantra IntegShipment Data#ShipmentData#*99 Existing Demantra IntegBooking Data#BookingData#*99 Old Demand PlanningComposite Calendars#CompositeCalendar#*99 Old Demand PlanningCustom Stream Data#CSData#*99 Old Demand PlanningLevel AssociationsLevelAssociation*99 Old Demand PlanningLevelOrgAsscnsLevelOrgAsscns*99 Old Demand PlanningLevel ValuesLevelValue*99 Old Demand PlanningSetup ParametersSetupParameter

CalendarsTableMSC_CALENDARSReturn to File DefinitionsDescriptionMSC_CALENDARS stores the definition of your workday calendarVCP-ODSDescriptionLogicFields ReferencedE1 TableE1 FieldCommentCALENDAR_CODEWorkday calendar identifier. Calendar code and source instance code should be unique.Refer to Comment for detailed processing
John Chivers: The Calendar flat file has the following fields: Branch Plant Work Center Calendar Type Calendar Name Date Shift Code Duration Event Code

The Calendar name used in EBS is a concatenation of several of these fields. But it is dependent upon the content of the fields.

All fields should have quotes removed and leading and trailing blanks removed as well.

Note: EBS does not support calendars at a work center level so only the branch level calendars will be used ultimately.

The following is the rules for the formulation of the calendar name:

If Work Centre is blank# Formulating a branch level Calendar Name If Calendar Type is blank Set Calendar_Type_var to M Else Set Calendar_Type_var to first_char of Calendar_Type End if

If Calendar_Name is blank EBS_Calendar_Name = Concat (Calendar_Type_var, field_delimiter, Branch_plant) Else EBS_Calendar_Name = Concat (Calendar_Type_var, field_delimiter, Branch_plant, field_delimiter, Calendar_Name) End ifElse Ignore records with a non blank work center End if

10.2 Customer and Supplier Calendars.Calendars can be associated with a customers and suppliers.

If a calendar has been set up against a customer or supplier then the calendar_code will be populated against the TradingPartner table, otherwise calendar_code will be set to .

In E1, all calendars will be setup against branch codes including those for customers and suppliers. However in ORCL APS, calendars for customers and suppliers are not associated with branches.

Therefore, in order to formulate the calendar for an ORCL APS customer, supplier a master branch will be used. This will be pointed to by parameter.master_branch.Calendar.txt:BranchPlantF0007MMCUCalendar.txt:WorkCenterF0007MCUCalendar.txt:Calendar TypeF0007WDCTCalendar.txt:Calendar NameF0007WDCKCALENDAR_START_DATEBeginning date for the calendarParameters.Base_Effective_DateCALENDAR_END_DATEEnding date for the calendarParameter.Calendar_End_Offset + Plan Option.Base_DateQUARTERLY_CALENDAR_TYPEQuarterly calendar type code. Valid values are: 1 - 4/4/5 Week pattern, 2 - 5/4/4 Week pattern, 3 - Calendar months, 4 - 13 Periods.Parameter.Quarterly_Calendar_TypeSR_INSTANCE_CODESource instance code defined on the planning serverParameter.Source_InstanceDESCRIPTIONDescription of the calendarWEEK_START_DAYValid values are: 1 - Monday, 2 - First day of the calendarParameter. Work Start DayOVERWRITE_FLAGValid 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.Should be N when loaded first time that particular code otherwise YCOMPANY_NAMERequired 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.Parameter.CP_Company_Name

Workday PatternsTableMSC_WORKDAY_PATTERNSReturn to File DefinitionsDescriptionMSC_CALENDARS stores the definition of your workday calendarVCP-ODSDescriptionLogicFields ReferencedE1 TableE1 FieldCommentCALENDAR_CODEWorkday calendar identifier. Should refer to a valid calendar code in MSC_CALENDARS.Refer to Comment for detailed processing
John Chivers: The Calendar flat file has the following fields: Branch Plant Work Center Calendar Type Calendar Name Date Shift Code Duration Event Code

The Calendar name used in EBS is a concatenation of several of these fields. But it is dependent upon the content of the fields.

All fields should have quotes removed and leading and trailing blanks removed as well.

Note: EBS does not support calendars at a work center level so only the branch level calendars will be used ultimately.

The following is the rules for the formulation of the calendar name:

If Work Centre is blank# Formulating a branch level Calendar Name If Calendar Type is blank Set Calendar_Type_var to M Else Set Calendar_Type_var to first_char of Calendar_Type End if

If Calendar_Name is blank EBS_Calendar_Name = Concat (Calendar_Type_var, field_delimiter, Branch_plant) Else EBS_Calendar_Name = Concat (Calendar_Type_var, field_delimiter, Branch_plant, field_delimiter, Calendar_Name) End ifElse Ignore records with a non blank work center End if

10.2 Customer and Supplier Calendars.Calendars can be associated with a customers and suppliers.

If a calendar has been set up against a customer or supplier then the calendar_code will be populated against the TradingPartner table, otherwise calendar_code will be set to .

In E1, all calendars will be setup against branch codes including those for customers and suppliers. However in ORCL APS, calendars for customers and suppliers are not associated with branches.

Therefore, in order to formulate the calendar for an ORCL APS customer, supplier a master branch will be used. This will be pointed to by parameter.master_branch.Calendar.txt:BranchPlantF0007MMCUCalendar.txt:WorkCenterF0007MCUCalendar.txt:Calendar TypeF0007WDCTCalendar.txt:Calendar NameF0007WDCKDAYS_ONParameter.Days OnDAYS_OFFParameter.Days OffSR_INSTANCE_CODESource instance code defined on the planning server.Parameter.Source_InstanceSHIFT_NUMEither 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."Shift Information".Shift Number (shift numbers relavent for this calendar can be deduced from searching the extract extensions of Work Centre)SHIFT_NAMEEither 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."Shift Information".Shift NameDESCRIPTIONDescription"Shift Information".Shift DescriptionCOMPANY_NAMERequired 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.Parameter.CP_Company_Name

Shift TimesTableMSC_SHIFT_TIMESReturn to File DefinitionsDescriptionMSC_CALENDARS stores the definition of your workday calendarVCP-ODSDescriptionLogicFields ReferencedE1 TableE1 FieldCommentCALENDAR_CODEWorkday calendar identifier. Should refer to a valid calendar code in MSC_CALENDARS.Refer to Comment for detailed processing
John Chivers: The Calendar flat file has the following fields: Branch Plant Work Center Calendar Type Calendar Name Date Shift Code Duration Event Code

The Calendar name used in EBS is a concatenation of several of these fields. But it is dependent upon the content of the fields.

All fields should have quotes removed and leading and trailing blanks removed as well.

Note: EBS does not support calendars at a work center level so only the branch level calendars will be used ultimately.

The following is the rules for the formulation of the calendar name:

If Work Centre is blank# Formulating a branch level Calendar Name If Calendar Type is blank Set Calendar_Type_var to M Else Set Calendar_Type_var to first_char of Calendar_Type End if

If Calendar_Name is blank EBS_Calendar_Name = Concat (Calendar_Type_var, field_delimiter, Branch_plant) Else EBS_Calendar_Name = Concat (Calendar_Type_var, field_delimiter, Branch_plant, field_delimiter, Calendar_Name) End ifElse Ignore records with a non blank work center End if

10.2 Customer and Supplier Calendars.Calendars can be associated with a customers and suppliers.

If a calendar has been set up against a customer or supplier then the calendar_code will be populated against the TradingPartner table, otherwise calendar_code will be set to .

In E1, all calendars will be setup against branch codes including those for customers and suppliers. However in ORCL APS, calendars for customers and suppliers are not associated with branches.

Therefore, in order to formulate the calendar for an ORCL APS customer, supplier a master branch will be used. This will be pointed to by parameter.master_branch.Calendar.txt:BranchPlantF0007MMCUCalendar.txt:WorkCenterF0007MCUCalendar.txt:Calendar TypeF0007WDCTCalendar.txt:Calendar NameF0007WDCKSHIFT_NAME"Shift Information".Shift Name (numeric)SR_INSTANCE_CODESource instance code defined on the planning server."Parameters".Source_InstanceFROM_TIMEShift time should not overlap with the already-defined timings"Shift Information Details".From Time converted to secondsTO_TIMEShift time should not overlap with the already defined timings"Shift Information Details".To Time converted to secondsCOMPANY_NAMERequired 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.Parameter.CP_Company_Name

This table will be primarily formed by joining the Calendar file with the user data "ShiftTimes".

Calendar ExceptionsTableMSC_CALENDAR_EXCEPTIONSReturn to File DefinitionsDescriptionMSC_CALENDAR_EXCEPTIONS stores exception dates for a calendar. You can define these exception dates to be working or non-working days. The workday calendar program uses this information to generate your workday calendarVCP-ODSDescriptionLogicFields ReferencedE1 TableE1 FieldCommentMSC_CALENDAR_EXCEPTIONSWorkday calendar identifier. Should refer to a valid calendar code in MSC_CALENDARS.Refer to Comment for detailed processing
John Chivers: The Calendar flat file has the following fields: Branch Plant Work Center Calendar Type Calendar Name Date Shift Code Duration Event Code

The Calendar name used in EBS is a concatenation of several of these fields. But it is dependent upon the content of the fields.

All fields should have quotes removed and leading and trailing blanks removed as well.

Note: EBS does not support calendars at a work center level so only the branch level calendars will be used ultimately.

The following is the rules for the formulation of the calendar name:

If Work Centre is blank# Formulating a branch level Calendar Name If Calendar Type is blank Set Calendar_Type_var to M Else Set Calendar_Type_var to first_char of Calendar_Type End if

If Calendar_Name is blank EBS_Calendar_Name = Concat (Calendar_Type_var, field_delimiter, Branch_plant) Else EBS_Calendar_Name = Concat (Calendar_Type_var, field_delimiter, Branch_plant, field_delimiter, Calendar_Name) End ifElse Ignore records with a non blank work center End if

10.2 Customer and Supplier Calendars.Calendars can be associated with a customers and suppliers.

If a calendar has been set up against a customer or supplier then the calendar_code will be populated against the TradingPartner table, otherwise calendar_code will be set to .

In E1, all calendars will be setup against branch codes including those for customers and suppliers. However in ORCL APS, calendars for customers and suppliers are not associated with branches.

Therefore, in order to formulate the calendar for an ORCL APS customer, supplier a master branch will be used. This will be pointed to by parameter.master_branch.Calendar.txt:BranchPlantF0007MMCUCalendar.txt:WorkCenterF0007MCUCalendar.txt:Calendar TypeF0007WDCTCalendar.txt:Calendar NameF0007WDCKEXCEPTION_DATEShould be within the calendar start date and end date.Where there is a conflict between OBDWCAL and WorkingDaysEXCEPTION_TYPEException type. Valid values are: 1- On, 2 - Off.Nature of conflictSR_INSTANCE_CODESource instance code defined on the planning serverParameter.Source_InstanceCOMPANY_NAMERequired 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 nullParameter.CP_Company_Name

OBDWCAL gives us the actual working days, Where there is a difference, there will be a CalendarException record created

Shift ExceptionTableMSC_SHIFT_EXCEPTIONSReturn to File DefinitionsDescriptionWorkday calendar shift exceptionsVCP-ODSDescriptionLogicFields ReferencedE1 TableE1 FieldCommentCALENDAR_CODEWorkday calendar identifier. Should refer to a valid calendar code in MSC_CALENDARS.Refer to Comment for detailed processing
John Chivers: The Calendar flat file has the following fields: Branch Plant Work Center Calendar Type Calendar Name Date Shift Code Duration Event Code

The Calendar name used in EBS is a concatenation of several of these fields. But it is dependent upon the content of the fields.

All fields should have quotes removed and leading and trailing blanks removed as well.

Note: EBS does not support calendars at a work center level so only the branch level calendars will be used ultimately.

The following is the rules for the formulation of the calendar name:

If Work Centre is blank# Formulating a branch level Calendar Name If Calendar Type is blank Set Calendar_Type_var to M Else Set Calendar_Type_var to first_char of Calendar_Type End if

If Calendar_Name is blank EBS_Calendar_Name = Concat (Calendar_Type_var, field_delimiter, Branch_plant) Else EBS_Calendar_Name = Concat (Calendar_Type_var, field_delimiter, Branch_plant, field_delimiter, Calendar_Name) End ifElse Ignore records with a non blank work center End if

10.2 Customer and Supplier Calendars.Calendars can be associated with a customers and suppliers.

If a calendar has been set up against a customer or supplier then the calendar_code will be populated against the TradingPartner table, otherwise calendar_code will be set to .

In E1, all calendars will be setup against branch codes including those for customers and suppliers. However in ORCL APS, calendars for customers and suppliers are not associated with branches.

Therefore, in order to formulate the calendar for an ORCL APS customer, supplier a master branch will be used. This will be pointed to by parameter.master_branch.Calendar.txt:BranchPlantF0007MMCUCalendar.txt:WorkCenterF0007MCUCalendar.txt:Calendar TypeF0007WDCTCalendar.txt:Calendar NameF0007WDCKEXCEPTION_DATEException date. Should be within the calendar periodWhere there is a conflict between OBDECAL and WorkingDaysEXCEPTION_TYPEException type. Valid values are: 1 - On, 2 - Off.Nature of conflictSR_INSTANCE_CODESource instance code defined on the planning server.Parameter.Source_InstanceSHIFT_NAMEName or SHIFT_NUM may be provided to identify a shift."Shift Information".Shift NameCOMPANY_NAMERequired 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.Parameter.CP_Company_Name

OBDWCAL gives us the actual working days, Where there is a difference, there will be a ShiftException record created

CalendarAssignment-SupplierShipTableCalendar Assignment.datReturn to File DefinitionsDescriptionAssign suppliers to calendarsVCP-ODSDescriptionLogicFields ReferencedE1 TableE1 FieldCommentCALENDAR_CODEWorkday calendar identifier. Should refer to a valid calendar code in MSC_CALENDARS."S",parameter.field_delimiter Parameter.Master_Branch, parameter.field_delimiter, supplier.xml:supplierList:supplier:supplierCodesupplier.xml:supplierList:supplier:supplierCodeF43090AN8Calendar TypeValid values are RECEIVING, 'SHIPPING, CARRIER'"SHIPPING"Association Type @Valid values are 1-15"5"Partner TypeValid values are 1-supplier, 2- customer, 3- Org, 4- Carrier "1"Partner NamePartner Name (Refer table below)Supplier.xml:supplierList:supplier:nameSupplier.xml:supplierList:supplier:nameF43090ALPHPartner Site CodePartner site code (Refer table below)Supplier.xml:supplierList:supplier:supplierCodesupplier.xml:supplierList:supplier:supplierCodeF43090AN8Organization CodeOrganization code (Refer table below)Source Instance CodeSource Instance Code is defined on the planning server. Parameter.Source_InstanceCarrier Partner CodeCarrier partner code (Refer table below)Ship Method Code Ship method code Company NameCompany Name Association LevelValid values are 1,2,3,4decode(ASSOCIATION_TYPE,11,1,10,1,9,3,8,3,7,3,6,2,5,2,4,4,3,4,2,4,1,4)

@ Association Type Valid values are:

ValueDescription1Vendor2Customer3Organization4Carrier5Vendor Site6Customer Site7Carrier/Vendor8Carrier/Customer9Carrier/Organization10Carrier/Vendor Site11Carrier/Customer Site12Item/Vendor13Item/Vendor Site14Calendar15Association Type

Association typePartner_nameOrganization Code10,11Not Null7,8Not Null9Not Null5,6Not Null1,2Not Null3Not Null4

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 recordSame logic as specifying calendar in "Trading Partner - 1"

Unit of MeasuresTableMSC_UNITS_OF_MEASUREReturn to File DefinitionsDescriptionUnit of measure definitionsVCP-ODSDescriptionLogicFields ReferencedE1 TableE1 FieldCommentUNIT_OF_MEASUREUnit Of MeasureBase.xml:item:planningUom orBase.xml:item:shippingUom orBase.xml:item:weightUom orBase.xml:item:volumeUom orBase.xml:itemUom:toUOM orManufacturing.xml:operation:operationdur:durationUnit orParameters.Base_Time_UOM

REFER to FDD for detailed processing stepsBase.xml:item:planningUomF34A10see commentCMUM 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.UVM1Base.xml:item:shippingUomF34A10assignmentSVUM is retrieved from F34A10 where F34A10.SY = '34A' assignment = same logic as planningUom except that F34A10.SVUM is used for comparisonBase.xml:item:weightUomF4101UWUMBase.xml:item:volumeUomF4101UVM1Base.xml:itemUom:toUOMV41003AManufacturing.xml:operation:operationdur:durationUnitsee commentassignment = 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"UOM_CODEUOM CodeBase.xml:item:planningUom orBase.xml:item:shippingUom orBase.xml:item:weightUom orBase.xml:item:volumeUom orBase.xml:itemUom:toUOM orManufacturing.xml:operation:runTimeUnit orParameters.Base_Time_UOM see UNIT_OF_MEASUREUOM_CLASSUOM ClassBase.xml:item:planningUom need to look up orBase.xml:item:shippingUom orBase.xml:item:weightUom orBase.xml:item:volumeUom orBase.xml:itemUom:toUOM "toUOMType" (Count if null)

"Time" for records from Manufactoring.xml or Parameters.Base_Time_UOM see UNIT_OF_MEASUREBase.xml:itemUom:toUomTypeF34A30BASE_UOM_FLAGWhether Base UOM (Yes) or not (No). One class can have one and only one Base UOM."Y" if UOM =Parameter.Base_Time_UOM|Parameter.Base_UOM_Volume | Weight | Count and to_uom_type = "Time"|"Volume"|Weight"|"Count" otherwise "N"SR_INSTANCE_CODESource instance code defined on the planning server.Parameter.Source_InstanceDISABLE_DATEDESCRIPTIONsames as "Unit Of Measure"COMPANY_NAMERequired 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.Parameter.CP_Company_Name

Aggregated values for Base.xml:item for each of the listed UOMs. REFER TO FDD FOR DETAILED PROCESSING STEPS

UOM ConversionTableMSC_UOM_CONVERSIONSReturn to File DefinitionsDescriptionThis table stores the different non-base unit of measures known conversionsVCP-ODSDescriptionLogicFields ReferencedE1 TableE1 FieldCommentUNIT_OF_MEASUREPrimary unit of measure long name. You should refer to a valid unit of measure in MSC_UNITS_OF_MEASURE.Base.xml:itemUomList:toUomREFER TO FDD FOR DETAILED PROCESSING STEPSBase.xml:itemUom:toUomF41002see commentassignment = if F41002.UM = planningUom (value assigned in the item Object), then toUom = F41002.RUM else toUom = F41002.UM

From = XTo = YFactor = Cif (X = planning UOM) ToUom = Y and factor = Celse (toUom = X and Factor = 1/C)UOM_CODEDestination unit of measure short name. You should refer to a valid unit of measure code in MSC_UNITS_OF_MEASURE.Base.xml:itemUomList:toUomsee UNIT_OF_MEASUREUOM_CLASSDestination class of conversion.Class for the above UOM_CODE fieldsee UOM_CLASS from Unit of Measure mappingCONVERSION_RATEConversion rate from conversion unit to base unit of class. Conversion rate should be greater than zero.1/Base.xml:itemUom:factor * Base_UOM_Conv(# see below)Base.xml:itemUom:factorF41002see commentassignment = 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 DEFAULT_CONVERSION_FLAGIndicates 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."1" if from itemUomSR_INSTANCE_CODESource instance code defined on the planning server.Parameter.Source_InstanceDISABLE_DATEDate when the conversion is no longer valid to be used in the system (transactions, etc).ITEM_NAMEItem name should already be defined on the planning server if DEFAULT_CONVERSION_FLAG = NBase.xml:itemUom:itemCodeBase.xml:itemUom:itemCodeF41002ITMCOMPANY_NAMERequired 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.Parameter.CP_Company_Name

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 recordONLY 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=1else Base_UOM_Conv = Base.xml:itemUOM where itemCode=current item and toUom=Parameters. Base_UOM_Volume/Weight/Count toUomType=Current Class

UOM Class ConversionTableMSC_UOM_CLASS_CONVERSIONSReturn to File DefinitionsDescriptionConversions between base units of two different classesVCP-ODSDescriptionLogicFields ReferencedE1 TableE1 FieldCommentFROM_UNIT_OF_MEASUREBase 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.xml:item:planningUomREFER TO FDD FOR DETAILED PROCESSING STEPSBase.xml:item:planningUomF34A10see commentCMUM 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.UVM1FROM_UOM_CODEBase 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.xml:item:planningUomsee FROM_UNIT_OF_MEASUREFROM_UOM_CLASSBase class of the item.From UOM.dat for From UOM Codesee UOM_CLASS for "From" Unit from Unit of Measure mappingTO_UNIT_OF_MEASUREBase 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.xml:itemUomList:toUomBase.xml:itemUom:toUomF41002see commentassignment = if F41002.UM = planningUom (value assigned in the item Object), then toUom = F41002.RUM else toUom = F41002.UM

From = XTo = YFactor = Cif (X = planning UOM) ToUom = Y and factor = Celse (toUom = X and Factor = 1/C)assignment = if F41002.UM = planningUom (value assigned in the item Object), then toUom = F41002.RUM else toUom = F41002.UM

From = XTo = YFactor = Cif (X = planning UOM) ToUom = Y and factor = Celse (toUom = X and Factor = 1/C)TO_UOM_CODEBase 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.Base.xml:itemUomList:toUomSee TO_UNIT_OF_MEASURETO_UOM_CLASSClass to which the conversion is defined.From UOM.dat for To UOM Codesee UOM_CLASS for "To" Unit to Unit of Measure mappingCONVERSION_RATEConversion rate from the item's class base unit to the "To" class base unit. Conversion rate should be greater than zero.Base.xml:itemUom:factorBase.xml:itemUom:factorF41002see commentassignment = 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 SR_INSTANCE_CODESource instance code defined on the planner server.Parameter.Source_InstanceDISABLE_DATEDate when the define interclass conversion rate can no longer be used.ITEM_NAMEInventory item name. Item name should be defined in MSC_SYSTEM_ITEMS table.Base.xml:itemUom:itemCodeBase.xml:itemUom:itemCodeF41002ITMCOMPANY_NAMERequired 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.Parameter.CP_Company_Name

Not needed when toUOM is in the base UOM

Demand ClassesTableMSC_DEMAND_CLASSESReturn to File DefinitionsDescriptionThis table stores the demand classesVCP-ODSDescriptionLogicFields ReferencedE1 TableE1 FieldCommentDemand ClassName of the demand class.Customer Categories pointed to by Parameter.Demand_Class_CategoryRefer to the FDD Complex modelling seciton on categroy codesCustomer.xml:customerGroup:nameF0101concatenationconcatenation = data dictionary description for data items AC01 - AC30|F0101.AC01 - AC30 MeaningMeaningCustomer Categories pointed to by Parameter.Demand_Class_CategoryRefer to the FDD Complex modelling section on category codessee "Demand Class"DescriptionDescription of the demand class.If customergroup:description is not null,use customergroup:description;else use customergroup:nameCustomer.xml:customerGroup:descriptionF0005DL01From DateFrom DateParameters.Base_Effective_Dateassignment = if F41002.UM = planningUom (value assigned in the item Object), then toUom = F41002.RUM else toUom = F41002.UM

From = XTo = YFactor = Cif (X = planning UOM) ToUom = Y and factor = Celse (toUom = X and Factor = 1/C)To DateTo DateEnabled FlagEnabled Flag"1"Source Instance CodeSource instance code defined on the planning server.Parameter.Source_InstanceCompany NameRequired 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.Parameter.CP_Company_NameDeleted FlagValid values are: 1 - Yes, 2 - No. If 1, then this row is deleted."2"

Derived from CustomerGroup using the Parameter "Demand_Class_Category" (refer to complex modelling on Category Codes in FDD)

Sales ChannelTableMSC_SALES_CHANNELReturn to File DefinitionsDescriptionThis table stores the Sales ChannelsVCP-ODSDescriptionLogicFields ReferencedE1 TableE1 FieldCommentLookup CodeName of the sales channel. 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.xml:customerGroup:nameF0101concatenationconcatenation = data dictionary description for data items AC01 - AC30|F0101.AC01 - AC30 MeaningMeaningCustomer Categories pointed to by Parameter.Demand_Class_CategoryRefer to the FDD Complex modelling section on category codessee "Demand Class"DescriptionDescription of the demand class.If customergroup:description is not null,use customergroup:description;else use customergroup:nameCustomer.xml:customerGroup:descriptionF0005DL01From DateFrom DateParameters.Base_Effective_Dateassignment = if F41002.UM = planningUom (value assigned in the item Object), then toUom = F41002.RUM else toUom = F41002.UM

From = XTo = YFactor = Cif (X = planning UOM) ToUom = Y and factor = Celse (toUom = X and Factor = 1/C)To DateTo DateEnabled FlagEnabled Flag"1"Source Instance CodeSource instance code defined on the planning server.Parameter.Source_InstanceCompany NameRequired 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.Parameter.CP_Company_NameDeleted FlagValid values are: 1 - Yes, 2 - No. If 1, then this row is deleted."2"LOOKUP_TYPE"SALES CHANNEL"

Derived from CustomerGroup using the Parameter "Sales_Channel_Category" (refer to complex modelling on Category Codes in FDD)

PlannersTableMSC_PLANNERSReturn to File DefinitionsDescriptionThis table stores and maintains a list of planner codes.VCP-ODSDescriptionLogicFields ReferencedE1 TableE1 FieldCommentPLANNER_CODEPlanner codeBase.xml: itemBranch.plannerNumberBase.xml: itemBranch.plannerNumberF4102ANPLORGANIZATION_CODEOrganization code in which the planner code is being createdBase.xml: itemBranch:branchCodeBase.xml: itemBranch:branchCodeF4102MCUDESCRIPTIONDescription of codeBase.xml: itemBranch.plannerNameBase.xml: itemBranch.plannerNameF0101ALPHDISABLE_DATEDate on which the planner record is disable.assignment = if F41002.UM = planningUom (value assigned in the item Object), then toUom = F41002.RUM else toUom = F41002.UM

From = XTo = YFactor = Cif (X = planning UOM) ToUom = Y and factor = Celse (toUom = X and Factor = 1/C)ELECTRONIC_MAIL_ADDRESSPlanner's Email address.Base.xml: itemBranch.plannerEmailBase.xml: itemBranch.plannerEmailF01151EMALCURRENT_EMPLOYEE_FLAGFlag indicating whether the employee record is current.1USER_NAMEPlanner's user name.Base.xml: itemBranch.plannerNumberBase.xml: itemBranch.plannerNumberF4102ANPLSR_INSTANCE_CODESource instance code defined on the planning server.Parameter.Source_InstanceCOMPANY_NAMERequired 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.DELETED_FLAGValid values are: 1 - Yes, 2- No. If 1 then this row is deleted"2"

Aggregrate plannernumber in itembranch by branch and planner

Trading Partners - SuppliersTableMSC_TRADING_PARTNERS (Suppliers)Return to File DefinitionsDescriptionThis table stores information about the different organizations: customers, vendors, and planned organizations. Suppliers in this caseVCP-ODSDescriptionLogicFields ReferencedE1 TableE1 FieldCommentPARTNER_TYPEValid values are: 1 - Vendor, 2 - supplier, 3 - Organization , 4 - Others."1" (Supplier)PARTNER_NAMESupplier.xml:supplierList:supplier:nameSupplier.xml:supplierList:supplier:nameF43090ALPHSR_INSTANCE_CODESource instance code defined on the planning server.Parameter.Source_InstanceORGANIZATION_CODEOrganization name of the organization being loaded. Required only if partner type is Organization.assignment = if F41002.UM = planningUom (value assigned in the item Object), then toUom = F41002.RUM else toUom = F41002.UM

From = XTo = YFactor = Cif (X = planning UOM) ToUom = Y and factor = Celse (toUom = X and Factor = 1/C)DISABLE_DATESTATUSValid values are: 1 - Active, 2 - Inactive."1"MASTER_ORGANIZATION_CODEPARTNER_NUMBERFor example, a DUNSNUMBER is the Dun & Bradstreet global identifier of organizations used in the classic commercial credit tracking service.Supplier.xml:supplierList:supplier:supplierCodeSupplier.xml:supplierList:supplier:supplierCodeF43090AN8CALENDAR_CODECalendar used for this partner. The code includes instance code and calendar code from the source apps.if ("S",parameter.field_delimiter Parameter.Master_Branch, parameter.field_delimiter, supplier.xml:supplierList:supplier:supplierCode) exists in Calendar.dat then use thisotherwise use Supplier.xml:supplierList:supplier:supplierCodeF43090AN8MAXIMUM_WEIGHTWeight capacity.MAXIMUM_VOLUMEVolume capacity.WEIGHT_UOMWeight unit of measure.VOLUME_UOMVolume unit of measure.PROJECT_REFERENCE_ENABLEDFlag indicates whether project references are allowed in the organization or not.PROJECT_CONTROL_LEVELSpecifies whether project references are being tracked at the project or task level.DEMAND_LATENESS_COSTDemand lateness cost.SUPPLIER_CAP_OVERUTIL_COSTSupplier over-utilization cost.RESOURCE_CAP_OVERUTIL_COSTResource over-utilization cost.TRANSPORT_CAP_OVER_UTIL_COSTThe penalty cost for transportation capacity.USE_PHANTOM_ROUTINGSUse phantom-routings flag.INHERIT_PHANTOM_OP_SEQInherit phantom op-sequence flag.DEFAULT_ATP_RULE_NAMEFutureDEFAULT_DEMAND_CLASSMATERIAL_ACCOUNTEXPENSE_ACCOUNTORGANIZATION_TYPEValid value 1 (Discrete Org)SERVICE_LEVELCOMPANY_NAMERequired 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.Parameter.CP_Company_NamePLANNING_ENABLED_FLAGMODELED_supplier_NAMEsupplier that is modeled as inventory organization.MODELED_supplier_SITE_CODEsupplier site which is modeled as inventory organization.MODELED_SUPPLIER_NAMESupplier that is modeled as inventory organization.MODELED_SUPPLIER_SITE_CODESupplier site which is modeled as inventory organization.INHERIT_OC_OP_SEQ_NUMValue of profile option INHERIT_OPTION_CLASS_OP_SEQRESOURCE_TYPEUsed 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.

Trading Partners - CustomersTableMSC_TRADING_PARTNERS Customers)Return to File DefinitionsDescriptionThis table stores information about the different organizations: customers, vendors, and planned organizations. Customers in this caseVCP-ODSDescriptionLogicFields ReferencedE1 TableE1 FieldCommentPARTNER_TYPEValid values are: 1 - Vendor, 2 - supplier, 3 - Organization , 4 - Others."2" (Customer)PARTNER_NAMECustomer.xml:customer:parentNameUSE the record pointed to by the parentaddressnumber if null or zero use the current recordCustomer.xml:customer:parentNameF0101ALPHF0101.AN8 = parentAddressNumberSR_INSTANCE_CODESource instance code defined on the planning server.Parameter.Source_InstanceORGANIZATION_CODEOrganization name of the organization being loaded. Required only if partner type is Organization.assignment = if F41002.UM = planningUom (value assigned in the item Object), then toUom = F41002.RUM else toUom = F41002.UM

From = XTo = YFactor = Cif (X = planning UOM) ToUom = Y and factor = Celse (toUom = X and Factor = 1/C)DISABLE_DATESTATUSValid values are: 1 - Active, 2 - Inactive.MASTER_ORGANIZATION_CODEPARTNER_NUMBERFor example, a DUNSNUMBER is the Dun & Bradstreet global identifier of organizations used in the classic commercial credit tracking service.Customer.xml:customer:parentAddressNumber (see the logic below)Customer.xml:customer:parentAddressNumberF43090AN8F0101.AN8 = parentAddressNumberCALENDAR_CODECalendar used for this partner. The code includes instance code and calendar code from the source apps.if ("C",parameter.field_delimiter, Parameter.Master_Branch, parameter.field_delimiter, customer.xml:customerList:customer:customerCode) exists in Calendar.dat then use thiselse )USE the record pointed to by the parentaddressnumberCustomer.xml:customer:parentAddressNumberF43090AN8F0101.AN8 = parentAddressNumberMAXIMUM_WEIGHTWeight capacity.MAXIMUM_VOLUMEVolume capacity.WEIGHT_UOMWeight unit of measure.VOLUME_UOMVolume unit of measure.PROJECT_REFERENCE_ENABLEDFlag indicates whether project references are allowed in the organization or not.PROJECT_CONTROL_LEVELSpecifies whether project references are being tracked at the project or task level.DEMAND_LATENESS_COSTDemand lateness cost.SUPPLIER_CAP_OVERUTIL_COSTSupplier over-utilization cost.RESOURCE_CAP_OVERUTIL_COSTResource over-utilization cost.TRANSPORT_CAP_OVER_UTIL_COSTThe penalty cost for transportation capacity.USE_PHANTOM_ROUTINGSUse phantom-routings flag.INHERIT_PHANTOM_OP_SEQInherit phantom op-sequence flag.DEFAULT_ATP_RULE_NAMEFutureDEFAULT_DEMAND_CLASSFrom 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 parentaddressnumberCustomer.xml:customerGroup:nameF0101concatenationconcatenation = data dictionary description for data items AC01 - AC30|F0101.AC01 - AC30 MATERIAL_ACCOUNTEXPENSE_ACCOUNTORGANIZATION_TYPEValid value 1 (Discrete Org)SERVICE_LEVELCOMPANY_NAMERequired 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.Parameter.CP_Company_NamePLANNING_ENABLED_FLAGMODELED_supplier_NAMEsupplier that is modeled as inventory organization.MODELED_supplier_SITE_CODEsupplier site which is modeled as inventory organization.MODELED_SUPPLIER_NAMESupplier that is modeled as inventory organization.MODELED_SUPPLIER_SITE_CODESupplier site which is modeled as inventory organization.INHERIT_OC_OP_SEQ_NUMValue of profile option INHERIT_OPTION_CLASS_OP_SEQRESOURCE_TYPEUsed 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.CUSTOMER_NUMBERCustomer.xml:customer:parentAddressNumber (see the logic below)Customer.xml:customer:parentAddressNumberF43090AN8CUSTOMER_CLASS_CODEPROPOSED Aug 11 bug 8787342From 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 parentaddressnumberCustomer.xml:customerGroup:nameF0101concatenationconcatenation = data dictionary description for data items AC01 - AC30|F0101.AC01 - AC30

If or is null, the set them to the current and Check all records exist in Tcustomer.xml, ifthe parentdoes not exist then set and to and *** At this point all records should have a valid customer record for the parent ***Extract all the and aggregate by *** 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 record pointed to by parentAddressNumberNon key fields will be derived from the record pointed to by the aggregated parentAdderessNumber used above

Non key fields will be derived from the record pointed to by the aggregated parentAdderessNumber used above

Trading Partners - OrganizationTableMSC_TRADING_PARTNERS (Branches/Organizations)Return to File DefinitionsDescriptionThis table stores information about the different organizations: customers, vendors, and planned organizations.Organizations in this caseVCP-ODSDescriptionLogicFields ReferencedE1 TableE1 FieldCommentPARTNER_TYPEValid values are: 1 - Vendor, 2 - Customer, 3 - Organization , 4 - Others."3" (Branch)PARTNER_NAMEBase.xml:branchList:branch:branchName Base.xml:branchList:branch:branchName F0006DL01SR_INSTANCE_CODESource instance code defined on the planning server.Parameter.Source_InstanceORGANIZATION_CODEOrganization name of the organization being loaded. Required only if partner type is Organization.Base.xml:branchList:branch:branchCodeassignment = if F41002.UM = planningUom (value assigned in the item Object), then toUom = F41002.RUM else toUom = F41002.UM

From = XTo = YFactor = Cif (X = planning UOM) ToUom = Y and factor = Celse (toUom = X and Factor = 1/C)DISABLE_DATESTATUSValid values are: 1 - Active, 2 - Inactive.1MASTER_ORGANIZATION_CODEOperating/financial unitBase.xml:branchList:branch:branchCodePARTNER_NUMBERFor example, a DUNSNUMBER is the Dun & Bradstreet global identifier of organizations used in the classic commercial credit tracking service.CALENDAR_CODECalendar used for this partner. The code includes instance code and calendar code from the source apps.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 Base.xml:branchList:branch:branchCodeF41001MCUMAXIMUM_WEIGHTWeight capacity.MAXIMUM_VOLUMEVolume capacity.WEIGHT_UOMWeight unit of measure.VOLUME_UOMVolume unit of measure.PROJECT_REFERENCE_ENABLEDFlag indicates whether project references are allowed in the organization or not.PROJECT_CONTROL_LEVELSpecifies whether project references are being tracked at the project or task level.DEMAND_LATENESS_COSTDemand lateness cost.SUPPLIER_CAP_OVERUTIL_COSTSupplier over-utilization cost.RESOURCE_CAP_OVERUTIL_COSTResource over-utilization cost.TRANSPORT_CAP_OVER_UTIL_COSTThe penalty cost for transportation capacity.USE_PHANTOM_ROUTINGSUse phantom-routings flag.Parameter.Phantom Routings flag(2)INHERIT_PHANTOM_OP_SEQInherit phantom op-sequence flag.Parameter.Inherit phantom op-sequence flag("2")DEFAULT_ATP_RULE_NAMEFutureDEFAULT_DEMAND_CLASSMATERIAL_ACCOUNTEXPENSE_ACCOUNTORGANIZATION_TYPEValid value 1 (Discrete Org)1- Discrete(Process is not supported in phase one)SERVICE_LEVELCOMPANY_NAMERequired 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.Parameter.CP_Company_NamePLANNING_ENABLED_FLAGNot usedMODELED_CUSTOMER_NAMECustomer that is modeled as inventory organization.MODELED_CUSTOMER_SITE_CODECustomer site which is modeled as inventory organization.MODELED_SUPPLIER_NAMESupplier that is modeled as inventory organization.MODELED_SUPPLIER_SITE_CODESupplier site which is modeled as inventory organization.INHERIT_OC_OP_SEQ_NUMValue of profile option INHERIT_OPTION_CLASS_OP_SEQ"2"RESOURCE_TYPEUsed 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. used in SPP onlyOPERATING_UNIT_NAMENot supported by OATemplateCategory code pointed to by Parameters.Branch_Operating_Unit_CategoryRefer to the Complex Modeling section, on the use of Category Codes in the FDDBase.xml:branchGroup:nameF0006category code valuepossible category code groups = RP01 through RP30BUSINESS_GROUP_NAMECategory code pointed to by Parameters.Branch_Business_Group_Category Refer to the Complex Modeling section, on the use of Category Codes in the FDDBase.xml:branchGroup:nameF0006category code valuepossible category code groups = RP01 through RP30LEGAL_ENTITY_NAMECategory code pointed to by Parameters.Branch_Legal_Entity_CategoryRefer to the Complex Modeling section, on the use of Category Codes in the FDDBase.xml:branchGroup:nameF0006category code valuepossible category code groups = RP01 through RP30CALENDAR_CODEParameter.Default_Currency_CodeBug 9711346Calendar Exception Set id"-1"

Trading Partner Site - SupplierTableMSC_TRADING_PARTNER_SITES(Suppliers)Return to File DefinitionsDescriptionThis table stores information about the different sites of an organization. Suppliers in this caseVCP-ODSDescriptionLogicFields ReferencedE1 TableE1 FieldCommentPARTNER_NAMEPARTNER_NAME for PARTNER_TYPE 1 and 2; Organization code for PARTNER_TYPE - 3Supplier.xml:supplierList:supplier:nameSupplier.xml:supplierList:supplier:nameF43090ALPHTP_SITE_CODETrading partner site code (Not Null for PARTNER_TYPE 1 and 2 and NULL for 3)Supplier.xml:supplierList:supplier:supplierCodeSupplier.xml:supplierList:supplier:supplierCodeF43090AN8PARTNER_TYPEValid values are: 1 - Vendor, 2 - Customer, 3 - Organization"1"PARTNER_ADDRESSAddress of the partner siteSupplier.xml:supplierList:supplier:city/stateProvince/country/postalCode seperated by Parameter.Field delimiterSupplier.xml:supplierList:supplier:cityF0116CTY1assignment = if F41002.UM = planningUom (value assigned in the item Object), then toUom = F41002.RUM else toUom = F41002.UM

From = XTo = YFactor = Cif (X = planning UOM) ToUom = Y and factor = Celse (toUom = X and Factor = 1/C)Supplier.xml:supplierList:supplier:stateProvinceF0116ADDSSupplier.xml:supplierList:supplier:countryF0116CTRSupplier.xml:supplierList:supplier:postalCodeF0116ADDZLOCATIONLocation of the site (Not Null for PARTNER_TYPE -3 )LONGITUDESupplier.xml:supplierList:supplier:longitudeSupplier.xml:supplierList:supplier:longitudeNot mappedLATITUDESupplier.xml:supplierList:supplier:latitudeSupplier.xml:supplierList:supplier:latitudeNot mappedSR_INSTANCE_CODESource instance code defined on the planning server.Parameter.Source_InstanceCOMPANY_NAMERequired 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.SHIPPING_CONTROLValid Values - 'BUYER','SUPPLIER','NONE'."SUPPLIER"SOURCE_SR_TP_IDPlease 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.SOURCE_SR_TP_SITE_IDPlease 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.OPERATING_UNIT_NAMENot supported by OATemplateCOUNTRYSupplier.xml:supplier:countrySupplier.xml:supplierList:supplier:countryF0116CTRSTATESupplier.xml:supplier:stateProvinceSupplier.xml:supplierList:supplier:stateProvinceF0116ADDSCITYSupplier.xml:supplier:citySupplier.xml:supplierList:supplier:cityF0116CTY1POSTAL_CODESupplier.xml:supplier:postalCodeSupplier.xml:supplierList:supplier:postalCodeF0116ADDZdeleted flag2

Trading Partner Site - CustomerTableMSC_TRADING_PARTNER_SITES(Customers)Return to File DefinitionsDescriptionThis table stores information about the different sites of an organization. Customers in this caseVCP-ODSDescriptionLogicFields ReferencedE1 TableE1 FieldCommentPARTNER_NAMEPARTNER_NAME for PARTNER_TYPE 1 and 2; Organization code for PARTNER_TYPE - 31.Customer.xml:customer.parentName2.Customer.xml:customer.parentNameif parentName is null or zero, set to Customer.xml:customer:nameCustomer.xml:customer:parentNameF0101ALPHF0101.AN8 = parentAddressNumberCustomer.xml:customer:nameF0101ALPHTP_SITE_CODETrading partner site code (Not Null for PARTNER_TYPE 1 and 2 and NULL for 3)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 nameCustomer.xml:customer:customerCodeF03012AN8Customer.xml:customer:nameF0101ALPHCustomer.xml:customer:billtonameF0101ALPHB90CB124/D90CB124DefaultSoldToShipTopassin F03012.an8 = mnShipToAddressget mnSoldToAddressPARTNER_TYPEValid values are: 1 - Vendor, 2 - Customer, 3 - Organization"2"PARTNER_ADDRESSAddress of the partner site1.Customer.xml:customerList:customer:city/stateProvince/country/postalCode seperated by Parameter.Field delimiter2."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 insteadCustomer.xml:customerList:customer:cityF0116CTY1assignment = if F41002.UM = planningUom (value assigned in the item Object), then toUom = F41002.RUM else toUom = F41002.UM

From = XTo = YFactor = Cif (X = planning UOM) ToUom = Y and factor = Celse (toUom = X and Factor = 1/C)Customer.xml:customerList:customer:stateProvinceF0116ADDSCustomer.xml:customerList:customer:city:countryF0116CTRCustomer.xml:customerList:customer:postalCodeF0116ADDZCustomer.xml:customer:customerCodeF03012AN8Customer.xml:customer:billtonameF0101ALPHB90CB124/D90CB124DefaultSoldToShipTopassin F03012.an8 = mnShipToAddressget mnSoldToAddressCustomer.xml:customer:billToNumberLOCATIONLocation of the site (Not Null for PARTNER_TYPE -3 )LONGITUDELATITUDESR_INSTANCE_CODESource instance code defined on the planning server.Parameter.Source_InstanceCOMPANY_NAMERequired 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.SHIPPING_CONTROLValid Values - 'BUYER','SUPPLIER','NONE'."BUYER"SOURCE_SR_TP_IDPlease 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.SOURCE_SR_TP_SITE_IDPlease 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.OPERATING_UNIT_NAMENot supported by OATemplate1 & 2.Category code pointed to by Parameters.Operating_Unit_CategoryRefer to the Complex Modeling section, on the use of Category Codes in the FDDCustomer.xml:customerGroup:nameF0101concatenationconcatenation = data dictionary description for data items AC01 - AC30|F0101.AC01 - AC30 COUNTRYcustomer.xml:customer:countryCustomer.xml:customerList:customer:cityF0116CTY1STATEcustomer.xml:customer:stateProvinceCustomer.xml:customerList:customer:stateProvinceF0116ADDSCITYcustomer.xml:customer:cityCustomer.xml:customerList:customer:city:countryF0116CTRPOSTAL_CODEcustomer.xml:customer:postalCodeCustomer.xml:customerList:customer:postalCodeF0116ADDZCUST_ACCOUNT_NUMBERCustomer.xml:customer:parentAddressNumber ,if null customercodeCustomer.xml:customer:parentAddressNumberF0150PA8Customer.xml:customer:customerCodeF03012AN8deleted flag2

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

Trading Partner Site - OrganisnTableMSC_TRADING_PARTNER_SITES(Organizations)Return to File DefinitionsDescriptionThis table stores information about the different sites of an organization. Organizations in this caseVCP-ODSDescriptionLogicFields ReferencedE1 TableE1 FieldCommentPARTNER_NAMEPARTNER_NAME for PARTNER_TYPE 1 and 2; Organization code for PARTNER_TYPE - 3Base.xml:branchList:branch:branchCodeBase.xml:branchList:branch:branchCodeF41001MCUTP_SITE_CODETrading partner site code (Not Null for PARTNER_TYPE 1 and 2 and NULL for 3)PARTNER_TYPEValid values are: 1 - Vendor, 2 - Customer, 3 - Organization"3"PARTNER_ADDRESSAddress of the partner siteBase.xml:branchList:branch:city/stateProvince/country/postalCode seperated by Parameter.Field delimiterBase.xml:branchList:branch:cityF0116CTY1assignment = if F41002.UM = planningUom (value assigned in the item Object), then toUom = F41002.RUM else toUom = F41002.UM

From = XTo = YFactor = Cif (X = planning UOM) ToUom = Y and factor = Celse (toUom = X and Factor = 1/C)Base.xml:branchList:branch:stateProvinceF0116ADDSBase.xml:branchList:branch:countryF0116CTRBase.xml:branchList:branch:postalCodeF0116ADDZLOCATIONLocation of the site (Not Null for PARTNER_TYPE -3 )Base.xml:branchList:branch:branchCodeF41001MCULONGITUDELATITUDESR_INSTANCE_CODESource instance code defined on the planning server.Parameter.Source_InstanceCOMPANY_NAMERequired 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.SHIPPING_CONTROLValid Values - 'BUYER','SUPPLIER','NONE'."SUPPLIER"SOURCE_SR_TP_IDPlease 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.SOURCE_SR_TP_SITE_IDPlease 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.OPERATING_UNIT_NAMENot supported by OATemplateCOUNTRYBase.xml:branchList:branch:countryBase.xml:branchList:branch:cityF0116CTY1STATEBase.xml:branchList:branch:stateProvinceBase.xml:branchList:branch:stateProvinceF0116ADDSCITYBase.xml:branchList:branch:cityBase.xml:branchList:branch:countryF0116CTRPOSTAL_CODEBase.xml:branchList:branch:postalCodeBase.xml:branchList:branch:postalCodeF0116ADDZdeleted flag2

Location Association - SupplierTableMSC_LOCATION_ASSOCIATIONS(Suppliers)Return to File DefinitionsDescriptionThis table stores location associations for organization, customer, customer sites, supplier, and supplier sites. Suppliers in this caseVCP-ODSDescriptionLogicFields ReferencedE1 TableE1 FieldCommentLOCATION_CODELocation codeSupplier.xml:supplierList:supplier:supplierCodeSupplier.xml:supplierList:supplier:supplierCodeF43090AN8PARTNER_NAMEPartner nameSupplier.xml:supplierList:supplier:nameSupplier.xml:supplierList:supplier:nameF43090ALPHTP_SITE_CODETrading partner site codeSupplier.xml:supplierList:supplier:supplierCodeSupplier.xml:supplierList:supplier:supplierCodeF43090AN8PARTNER_TYPEValid values are: 1 - Vendor, 2 - Customer, 3 - Organization, 4 - Others, etc."1"SR_INSTANCE_CODESource instance code defined on the planning server.Parameter.Source_InstanceORGANIZATION_CODEOrganization code for legacy users.SUPPLIER.SUPPLIERCODEDELETED_FLAGValid values are: 1 - Yes, 2 - No. If 1, then this row is deleted."2"COMPANY_NAMERequired 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.Parameter.CP_Company_NameSOURCE_SR_TP_IDPlease 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.SOURCE_SR_TP_SITE_IDPlease 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.SOURCE_LOCATION_IDPlease 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.

Location Association - CustomerTableMSC_LOCATION_ASSOCIATIONS(Suppliers)Return to File DefinitionsDescriptionThis table stores location associations for organization, customer, customer sites, supplier, and supplier sites. Suppliers in this caseVCP-ODSDescriptionLogicFields ReferencedE1 TableE1 FieldCommentLOCATION_CODELocation codeuse the site code used for Trading Partner Sites (Partner Type=2)PARTNER_NAMEPartner namecustomer.xml:customerList:customer:nameCustomer.xml:customer:nameF0101ALPHTP_SITE_CODETrading partner site codeuse the site code used for Trading Partner Sites (Partner Type=2)PARTNER_TYPEValid values are: 1 - Vendor, 2 - Customer, 3 - Organization, 4 - Others, etc."2"SR_INSTANCE_CODESource instance code defined on the planning server.Parameter.Source_InstanceORGANIZATION_CODEOrganization code for legacy users.CUSTOMERCODE.CUSTOMERCODEDELETED_FLAGValid values are: 1 - Yes, 2 - No. If 1, then this row is deleted."2"COMPANY_NAMERequired 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.Parameter.CP_Company_NameSOURCE_SR_TP_IDPlease 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.SOURCE_SR_TP_SITE_IDPlease 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.SOURCE_LOCATION_IDPlease 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.

Location Association - OrganiznTableMSC_LOCATION_ASSOCIATIONS(Suppliers)Return to File DefinitionsDescriptionThis table stores location associations for organization, customer, customer sites, supplier, and supplier sites. Suppliers in this caseVCP-ODSDescriptionLogicFields ReferencedE1 TableE1 FieldCommentLOCATION_CODELocation codeBase.xml:branchList:branch:branchCodeBase.xml:branchList:branch:branchCodeF41001MCUPARTNER_NAMEPartner nameBase.xml:branchList:branch:branchCodeBase.xml:branchList:branch:branchCodeF41001MCUTP_SITE_CODETrading partner site codeBase.xml:branchList:branch:branchCodeBase.xml:branchList:branch:branchCodeF41001MCUPARTNER_TYPEValid values are: 1 - Vendor, 2 - Customer, 3 - Organization, 4 - Others, etc."3"SR_INSTANCE_CODESource instance code defined on the planning server.Parameter.Source_InstanceORGANIZATION_CODEOrganization code for legacy users.Base.xml:branchList:branch:branchCodeBase.xml:branchList:branch:branchCodeF41001MCUDELETED_FLAGValid values are: 1 - Yes, 2 - No. If 1, then this row is deleted."2"COMPANY_NAMERequired 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.Parameter.CP_Company_NameSOURCE_SR_TP_IDPlease 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.SOURCE_SR_TP_SITE_IDPlease 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.SOURCE_LOCATION_IDPlease 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.

Items - MainTableMSC_ST_SYSTEM_ITEMSReturn to File DefinitionsDescriptionMSC_SYSTEM_ITEMS stores the organization items defined at source applications. It also stores a copy of items planned by the planning process. Most of the columns in MSC_SYSTEM_ITEMS correspond to columns from the Oracle Inventory Item masterVCP-ODSDescriptionLogicFields ReferencedE1 TableE1 FieldCommentORGANIZATION_CODEThe organization in which the item is being defined.Base.xml:itemBranch:branchCodeBase.xml:itemBranch:branchCodeF4102MCUITEM_NAMEThe name of the item that you are creating.Base.xml:itemBranch:itemCodeBase.xml:itemBranch:itemCodeF4102ITMLOT_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.Base.xml:itemBranch:lotStatusCodeBase.xml:itemBranch:lotStatusCodeF4102LOTSROUNDING_CONTROL_TYPE Valid values are: 1 - Round order quantities, 2 - Do not round order quantities.Base.xml:item:roundToWholeNumbersY -> 1 -> 2N -> 2U -> Parameter(Setting_to_use_on_round_up)Base.xml:item:roundToWholeNumbersF4101SNSIN_SOURCE_PLAN Flag indicating whether the item is in the plan. (The snapshot initially gets more items than planned items.)

MRP_PLANNING_CODEValid values are: 3 - MRP planning, 4 - MPS planning, 6 - Not planned, 7 - MRP and DRP planning, 8 - MPS and DRP planning, 9 - DRP planning.Base.xml:itemBranch:planningCodein E1 we will have a UDC translation table based on MPST.Base.xml:item:planningCodeF4102MPSTFULL_LEAD_TIMEFull lead timeIf shipping from the supplier its start date to the dock dateIf Purchased (base.xml:itemBranch:itemType = "P"): then Supplier.xml:supplier:supplieritem:standardLeadTime (LVLT) (key is item/branch) (use lowest cost record)else base.xml:itemBranch:fixedLeadTimeBase.xml:itemBranch:itemTypeF4102STKTSupplier.xml:supplier:supplieritem:standardLeadTime F43090ALTDBase.xml:itemBranch:fixedLeadTimeF4102LTLVUOM_CODEUnit of measure code.Base.xml:item:planningUomBase.xml:item:planningUomF34A10see commentCMUM is retrieved from F34A10 where F34A10.SY = '34A' assignment = if F34A10.CMUM = '01', then planningUom = F4101. UOM1if F34A10.CMUM = '02', then planningUom = F4101.UOM2if F34A10.CMUM = '03', then planningUom = F4101.UOM3if F34A10.CMUM = '04', then planningUom = F4101.UOM4if F34A10.CMUM = '05', then planningUom = F4101.UOM6 if F34A10.CMUM = '06', then planningUom = F4101.UOM8if F34A10.CMUM = '07', then planningUom = F4101.UOM9if F34A10.CMUM = '08', then planningUom = F4101.UWUMif F34A10.CMUM = '09', then planningUom = F4101.UVM1MRP_CALCULATE_ATP_FLAG Valid values are: 1 - Yes, 2 - No.Parameter.MRP Calculate ATP Flag(2)ATP_COMPONENTS_FLAG Valid values are: Y - Item may have component requiring ATP check, N - No.Parameter.ATP Components Flag(n)BUILT_IN_WIP_FLAG Valid values are: 1 - Yes, 2 - No.Parameter.Built_In_WIP (1)PURCHASING_ENABLED_FLAG Valid values are: 1 - Yes, 2 - No.If Purchased (base.xml:itemBranch:itemType = "P") then 1 otherwise 2Base.xml:itemBranch:itemTypeF4102STKTPLANNING_MAKE_BUY_CODE Indicate if this item should be made or bought. Make(1), Buy(2)Base.xml:itemBranch:itemType (M->1, p->2)Base.xml:itemBranch:itemTypeF4102STKTREPETITIVE_TYPE Flag to indicate whether the item is built repetitiveParameter.Repititive Type (1)ENGINEERING_ITEM_FLAG Valid values are: 1 - Yes, 2 - No. Flag indicates if engineering items are used for prototypes or research. Used for UI and reports."2"MRP_SAFETY_STOCK_CODE Valid values are: 1 - User-defined quantity, 2 - User-defined percentage, or mean absolute deviation.Parameter.Safety Stock Code (1)EFFECTIVITY_CONTROLParameter.Effectivity Control (1)INVENTORY_PLANNING_CODEparameter.Inventory Planning Code (6)ATP_FLAG Valid values are: 1 - Yes, 2 - No."2"SR_INSTANCE_CODESource instance code defined on the planning server.Parameter.Source_InstanceDESCRIPTIONItem description.Base.xml:item:descriptionBase.xml:item:descriptionF4101DSC1LOTS_EXPIRATIONBase.xml:itemBranch:shelfLifeBug 2010-05-27Base.xml:itemBranch:shelfLifeF4102SLDSHRINKAGE_RATEPercentage of shinkage for this itemBase.xml:itemBranch:shrinkageRate / 100Documentation Note: make sure user set shrink method to "%"Base.xml:itemBranch:shrinkageRateF4102SRNKFIXED_DAYS_SUPPLYOrder Modifier:Period of the supply days (in days)Base.xml:itemBranch:fixedDaysSupplyBase.xml:itemBranch:fixedDaysSupplyF4102see commentItem.Branch.Order Policy(OPC)=4 use item.branch:item_value_policy(OPV) otherwise FIXED_ORDER_QUANTITYOrder Modifier:Fixed size for the ordersBase.xml:itemBranch:fixedOrderQuantityBase.xml:itemBranch:fixedOrderQuantityF4102see commentItem.Branch.Order Policy(OPC)=2 use item.branch:item_value_policy(OPV) otherwise FIXED_LOT_MULTIPLIEROrder Modifier:Fixed size for the lotIf Base.xml:itemBranch:orderMultiplier=0 then else Base.xml:itemBranch:orderMultiplier(Bug 10135494)Base.xml:itemBranch:orderMultiplierF4102MULTMINIMUM_ORDER_QUANTITYOrder Modifier:Minimum size of an orderBase.xml:itemBranch:minimumOrderQuantityBase.xml:itemBranch:minimumOrderQuantityF4102RQMNMAXIMUM_ORDER_QUANTITYOrder Modifier:Maximum size of an orderIf Base.xml:itemBranch:maximumOrderQuantity=0 then else Base.xml:itemBranch:maximumOrderQuantity (Bug 10135494)Base.xml:itemBranch:maximumOrderQuantityF4102RQMXOrder Modifier: field is addressed to aboveBase.xml:item:roundToWholeNumbersBase.xml:item:roundToWholeNumbersF4101SNSPLANNING_TIME_FENCE_DAYSPlanning time fences days of the itemBase.xml:itemBranch:freezeTimeFenceDaysBase.xml:itemBranch:freezeTimeFenceDaysF4102MTF2DEMAND_TIME_FENCE_DAYSDemand time fence daysBase.xml:inventoryPolicy:forecastConsumptionTimeFenceDocumentation Note: Make sure forecastConsumptionRule is "Order - Greater" and UOM is "Days"Base.xml:inventoryPolicy:forecastConsumptionTimeFenceF4102MTF1RELEASE_TIME_FENCE_CODERelease time fence codeParameter.Release Time Fence CodeRELEASE_TIME_FENCE_DAYSRelease time fence timeParameter.Release Time Fence DaysREVISIONItem revision codeParameter.Revision ()CATEGORY_NAMECategory name for the planning categoryBase.xml:itemgroup..refer to the FDD section on Category Codes, the parameter for this field will be Parameter.Item_Default_CategoryBase.xml:itemgroupF4101see commentpossible 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, CYCLABC_CLASS_NAMEInventory item identifier ABC class (use for UI and reports)Base.xml:itembranch:ABCS orBase.xml:itembranch:ABCI orBase.xml:itembranch:ABCMThe parameter.ABC field name will determine which to useBase.xml:itembranch:abcSalesF4102ABCSBase.xml:itembranch:abcInvestmentInventoryF4102ABCIBase.xml:itembranch:abcMarginInventoryF4102ABCMFIXED_LEAD_TIMEFixed lead timeBase.xml:itemBranch:fixedLeadTimeBase.xml:itemBranch:fixedLeadTimeVARIABLE_LEAD_TIMEVariable lead timeBase.xml:itemBranch:variableLeadTimeBase.xml:itemBranch:variableLeadTimePREPROCESSING_LEAD_TIMEPreprocessing lead timeIf Purchased (supplier item record exists in Supplier.xml (key is item&branch)):): Parameter.Purchased Preprocessing Lead Time ()For Manufactured Items: Parameter.manufactured Preprocessing Lead Time ()Base.xml:itemBranch:itemTypeF4102STKTPOSTPROCESSING_LEAD_TIMEPostprocessing lead timeFor Purchased Items ((base.xml:itemBranch:itemType = "P" ): Parameter.Purchased Postprocessing Lead Time ()For Manufactured Items: Parameter.manufactured Postprocessing Lead Time ()Base.xml:itemBranch:itemTypeF4102STKTCUMULATIVE_TOTAL_LEAD_TIMECumulative total lead timeFor Purchased Items: Parameter.Purchased Cumm Total Lead Time ()For Manufacturing Items: Parameter.manufactured Cumm Total Lead Time ()Base.xml:itemBranch:itemTypeF4102STKTCUM_MANUFACTURING_LEAD_TIMECumulative manufacturing lead timeUNIT_WEIGHTWeight of the itemWork with UOM Conversions in Base.xml:item:weightUomBase.xml:item:weightUomF4101UWUMitemCode and toUOMType in JOIN critereaBase.xml:itemUom:factorF41002see commentassignment = 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 UNIT_VOLUMEVolume of the itemWork with UOM Conversions in Base.xmlBase.xml:item:volumeUomF4101UVM1itemCode and toUOMType in JOIN critereaBase.xml:itemUom:factorF41002see commentassignment = 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 WEIGHT_UOMUnit of measure for the weightBase.xml:item:weightUomBase.xml:item:weightUomF4101UWUMVOLUME_UOMUnit of measure for the volumeBase.xml:item:volumeUomBase.xml:item:volumeUomF4101UVM1PRODUCT_FAMILY_ITEM_NAMEProduct Family to which the item belongs Base.xml:itembranch:masterPlanningFamily Base.xml:itembranch:masterPlanningFamilyF4102PRP4ATP_RULE_CODEATP rule identifierParameter.ATP Rule Code()STANDARD_COSTStandard cost of an itemBase.xml:itenBranch:itemCostBase.xml:itenBranch:itemCostF4105UNCSCARRYING_COSTCarrying costParameter.Carrying Cost % of standard costBase.xml:itenBranch:itemCostF4105UNCSORDER_COSTOrder costParameter.Order Cost % of standard cost * (Standard Cost/100)Base.xml:itenBranch:itemCostF4105UNCSDMD_LATENESS_COSTDemand lateness cost for itemParameter.Demand Lateness Cost % of standard cost * (Standard Cost/100)Base.xml:itenBranch:itemCostF4105UNCSSS_PENALTY_COSTPenalty cost for saftety stock violationsParameter.SS Penalty Cost % of standard cost * (Standard Cost/100)Base.xml:itenBranch:itemCostF4105UNCSSUPPLIER_CAP_OVERUTIL_COSTSupplier cap over utilization costParameter.Supplier Cap Over Utilization Cost % of standard cost * (Standard Cost/100)Base.xml:itenBranch:itemCostF4105UNCSLIST_PRICEList price of the itemBase.xml:itemBranch:timeVaryingEvent:itemPrice (time varying event..use the one which covers Options.Base_Date)Base.xml:itemBranch:timeVaryingEvent:itemPriceF4106UPRCAVERAGE_DISCOUNTAverage discountParameter.Average DiscountEND_ASSEMBLY_PEGGING_FLAG 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.Parameter.End Assembly Pegging Flag (B)END_ASSEMBLY_PEGGINGPeg to the end assembly on reports (value is populated by the plan)Parameter.End Assembly Pegging ()FULL_PEGGINGFull pegging flagParameter. Full Pegging (1)WIP_SUPPLY_TYPE Valid values are: 1 - Push, 2 - Assembly pull, 3 - Operation pull, 4 - Bulk, 5 - Supplier, 6 - Phantom, 7 - Based on bill.MRP_SAFETY_STOCK_PERCENT Percent of average gross requirement for dynamically calculated safety-stocks.Parameter.MRP Safety Stock Percent()SAFETY_STOCK_BUCKET_DAYS Days over an average demand for MRP planned safety stock percent.Parameter.Safety Stock Bucket Days()INVENTORY_USE_UP_DATEUse-up dateBUYER_NAMEName of buyer (for reporting) Buyer number on Item Master not needed as not supporting requisitionsPLANNER_CODEPlanner code (for reporting)IF 'Base.xml:itemBranch:plannerNumber' 0 use 'Base.xml:itemBranch:plannerNumber' otherwise use Parameters.Default_Planner_NumberBase.xml:itemBranch:plannerNumberF4102ANPLPLANNING_EXCEPTION_SETIdentifier of the planning exception setParameter.Planning Exception Set (null)EXCESS_QUANTITYExcess quantity of this itemEXCEPTION_SHORTAGE_DAYSException shortage daysParameter.Exception Shortage Days ()EXCEPTION_EXCESS_DAYSException excess daysParameter.Exception Excess Days ()EXCEPTION_OVERPROMISED_DAYSException over-promised daysParameter.Exception Over Promised DaysREPETITIVE_VARIANCE_DAYSParameter.Repetitive Variance DaysBASE_ITEM_NAME (used in end_item_substitution).BOM_ITEM_TYPEValid values are: 1 - Model, 2 - Option Class, 3 - Planning, 4 - Standard, 5 - Product familyParameter.BOM Item Type (4) (1) for ATO items if ATO comes into scopeATO_FORECAST_CONTROLValid values are: 1 - Consume, 2- Consume and derive, 3 - None.Parameter.ATO Forecast (2)ACCEPTABLE_EARLY_DELIVERYAcceptable early daysParameter.Acceptable Early Delivery ()ACCEPTABLE_RATE_INCREASEParameter.Acceptable Rate Increase ()ACCEPTABLE_RATE_DECREASEParameter.Acceptable Rate Decrease ()PRIMARY_SUPPLIER_NAMEPrimary supplierSupplier.xml:supplier:supplierItem:item = current item (key is item/branch)Use the Supplier with the lowest costSupplier.xml:supplier:supplierItem:itemF43090ITMINVENTORY_ITEM_FLAG Valid values are: 1- Yes, 2 - No.Parameter.Inventory Item Flag (1)REVISION_QTY_CONTROL_CODE1 Not under revision quantity control 2 Under revision quantity controlParameter.Revision Quantity Control Code(1)EXPENSE_ACCOUNTExpense AccountParameter.Expense Account ()INVENTORY_ASSET_FLAGValid values are: 1 - Yes, 2 - No.Parameter.Inventory Asset Flag(N)MATERIAL_COSTItem Material CostRESOURCE_COSTItem Resource CostSOURCE_ORG_CODESource Organization CodeIf in Manufacturing.xml there is a producedItem with itemCode=Base.xml:itemBranch:itemCode andbranchCode= Base.xml:itemBranch:branchCodeThen set to Base.xml:itemBranch:branchCodeElse Search distribution.xml where Distribution.xml:lane:destinationBranchCode= Base.xml:itemBranch:branchCode andDistribution.xml:lane: transportModeCode: itemCode= Base.xml:itemBranch:itemCodeNote Branch is translatableManufacturing.xml:operation:producedItemF3003KITManufacturing.xml:operation:producedItem:producedItemBomF3003MMCUBase.xml:itemBranch:branchCodeF4102MCUDistribution.xml:lane:destinationBranchCodeF3403cmcuDistribution.xml:lane:transportMode:itemTransportMode:itemCodeF3403itmDistribution.xml:lane:originBranchCodeF3403mmcuPICK_COMPONENTS_FLAG Flag indicating whether all shippable components should be picked.Parameter.Pick Components Flag ()Kits and configured items are not covered by the current extractsALLOWED_UNITS_LOOKUP_CODESERVICE_LEVELService levelParameter.Service Level ()REPLENISH_TO_ORDER_FLAGFlag indicating item to be planned as replenish to orderParameter.Replenish To Order Flag(N)COMPANY_NAMERequired 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.Parameter.CP_Company_NameMIN_MINMAX_QUANTITYMin Minmax QuantityMAX_MINMAX_QUANTITYMax Minmax QuantitySERIAL_NUMBER_CONTROL_CODEWhether the item is serial number controlled in this Organization. Valid values are 1 - Yes and 2 - No.Parameter.Serial Number Control Code("2")PIP_FLAGParameter.PIP Flag ()SUBSTITUTION_WINDOWSubstitution Window for the Item.Parameter.Substitution Window()CREATE_SUPPLY_FLAGCreate supply flag (1=Yes, 2=No).Parameter.Create Supply Flag(1)SERIAL_NUMBER_CONTROL_CODEParameter.Serial Number Control Code()CRITICAL_COMPONENT_FLAG Flag for indicating item is critical or not.Parameter.Critical Component Flag ()REDUCE_MPSIndicates how MPS orders are reduce when the plan is re-run.Parameter.Reduce MPS ()VMI_MINIMUM_UNITSMinimum quantity in units.VMI_MINIMUM_DAYSMinimum quantity in days.VMI_MAXIMUM_UNITSMaximum quantity in units.VMI_MAXIMUM_DAYSMaximum quantity in days.VMI_FIXED_ORDER_QUANTITYFixed order quantity in units.SO_AUTHORIZATION_FLAGSO release authorization flag 1- authorization by customer required 2- authorization not required.CONSIGNED_FLAG VMI Consigned flag 1-consigned, 2-unconsigned.Parameter.Consigned_FlagASN_AUTOEXPIRE_FLAG Auto-expiring ASN flag 1 ASN auto-expired, 2- ASN not auto-expired.Parameter.ASN Autoexpire Flag ()VMI_FORECAST_TYPEForecast type for average flag 1- order forecast, 2- sales forecast, 3- historical sales.FORECAST_HORIZONForecast horizon for average daily demand calculation.Parameter.Forecast Horizon ()BUDGET_CONSTRAINED Budget Constrained Flag 1-Yes, 2-No.Parameter.Budget Constrained (2)DAYS_TGT_INV_SUPPLYTarget inventory level days supply.Parameter.Days TGT Inv Supply ()DAYS_TGT_INV_WINDOWTarget Inventory level window.Parameter.Days TGT Inv Window ()DAYS_MAX_INV_SUPPLYMax inventory level days supply.Parameter.Days Max Inv Supply ()DAYS_MAX_INV_WINDOWMax inventory level windowParameter.Days Max Inv Window ()CONTINOUS_TRANSFERContinuous Inter Organization transfers 1-Yes, 2-No, 3-Use Global Value.Parameter.Continuous Transfer()CONVERGENCE Convergent Supply Consumption Pattern 1-Series, 2-Parallel, 3-Use Global Value.Parameter.Convergence()DIVERGENCE Divergent Supply Feeding Pattern 1-Series, 2-Series with MTQ, 3-Use Global Value.Parameter.Divergence()SOURCE_SR_INVENTORY_ITEM_IDPlease 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.Same as "Item Code" aboveSOURCE_SOURCE_ORG_IDPlease 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.Same as "Organisation Code" aboveSOURCE_PRIMARY_SUPPLIER_IDPlease 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.use the value populated into "Primary Supplier Name"SOURCE_BASE_ITEM_IDPlease 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.SOURCE_ABC_CLASS_IDPlease 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.use the same value used for "ABC Class Name" aboveREPAIR_LEAD_TIMERepair lead time(days). Required only for Service Requirement Planning (SRP).PREPOSITION_POINTPreposition Inventory. Required only for Service Requirement Planning (SRP). Valid values are 'Y' and 'N'.REPAIR_YIELDRepair yield percenta