This document is to give user possible means to debug any issue derived from Header To Detail option in P4210 (Sales Order Entry) and P4310 (Purchase Order Entry). So this document shall explain as-is behavior, constraint (in both Technical and Business) and known issues.
Below information is to be updated according.
A. Explanation of P40HDR
(To be implemented)
B. Explanation of P4210
(Detail information will be added)
The enhancement request is not to be implemented any time soon neither P4310 nor P4210 because it disrupts current application behavior as described in E1: 42/43: P40HDR: Automatically Default Fields from the Header to Detail in Order Entry (P40HDR/P4210/P4310) (Doc ID 1095199.1).
As described in the uploaded file <doseo_P40HDR.SDEMCU_Clarification.doc> P4210 Adds/Updates F4211.EMCU = F4201.MCU when you have set P40HDR.SHEMCU = 1.
Simplified routine to handle Header To Detail is,
W4210G - Sales Order Header
|--- F4211FSBeginDoc: to validate/default and create cache for sales order based on changed value
|--- DetermineChangedSOHeaderValues (N4201090, Determine Changed SO Header Values) to determine whether any value has changed or not
|--- CacheProcessHeaderToDetailChange (B4002390, Cache Process Header To Detail Changes) to store cache because the informtion change has to be used in different form (say W4210A)
W4210A - Sales Order Detail
|--- LoadChangedSOHeaderValues (N4201090, Load Changed SO Header Values) to load cache and return it before we call F4211FSEditLine which validates/default and create cache for Sales Order Detail File
|--- F4211FSEditLine
|--- LoadChangedSOHeaderValues (N4201090, Load Changed SO Header Values)
|--- CacheProcessHeaderToDetailChange B4002390 Cache Process Header To Detail Changes
Value to be handled by Header To Detail functions: Note that only limited columns can be updated as below,
Load Changed SO Header Values
FC Order Number <> BF mnOrderNumber
FC Order Type <> BF szOrderType
FC Order Company <> BF szOrderKeyCompany
FC Address Number <> BF mnSoldTo
GC Customer PO <> BF szCustomerPO
GC Revenue Business Unit <> BF szHeaderBranch
GC Ship To Number <> BF mnShipTo
FC Order Date <> BF jdOrderDate
GC Requested Date <> BF jdDateRequested
GC Scheduled Pick <> BF jdPromisedDeliveryDate
GC Cancel Date <> BF jdCancelDate
GC Print Message <> BF szPrintMessage
VA frm_TaxExplanationCode <> BF szTaxExplanationCode
VA frm_TaxRateArea <> BF szTaxArea
VA frm_PaymentTermsCode <> BF szPaymentTerms
GC Pay Inst <> BF cPaymentInstrument
GC Carrier Number <> BF mnCarrier
VA frm_cApplyFreightChg_AFT <> BF cApplyFreightYN
VA frm_szFreightCodeChg_FRTH <> BF szFreightHandlingCode
VA frm_szChangedRouteCode_ROUT <> BF szRouteCode
VA frm_szChangedStopCode_STOP <> BF szStopCode
VA frm_szChangedZoneNum_ZON <> BF szZoneNumber
VA frm_Salesperson1 <> BF mnCommissionCode1
VA frm_SalespersonCommission1 <> BF mnRateCommission1
VA frm_Salesperson2 <> BF mnCommissionCode2
VA frm_SalespersonCommission2 <> BF mnRateCommission2
VA frm_szUserReservedCode_URCD <> BF szUserReservedCode
VA frm_jdUserReservedDate_URDT <> BF jdUserReservedDate
VA frm_mnUserReservedAmt_URAT <> BF mnUserReservedAmount
VA frm_mnUserReservedNumber_URAB <> BF mnUserReservedNumber
VA frm_szUserReservedRef_URRF <> BF szUserReservedReference
GC Adj. Schedule <> BF szPriceAdjustmentSchedule
VA frm_mnTradeDiscount_TRDC <> BF mnDiscountTrade
GC Requested Time <> BF mnRequestedDeliveryTime
GC Mod Trn <> BF szModeOfTransport
VA frm_szReasonCode <> BF szReasonCode
GC Deliver To <> BF mnDeliveredTo
C. Explanation of P4310
(To be implemented)
Would you please publish this document? I am going to refine this document as early as possible - but not within usual time frame.