This document discusses columns populated in the Purchase Order when it is generated from a Sales Order. It is specific to the following types of transactions: Direct Ship Orders (SD/OD), Transfer Orders (ST/OT) and Intercompany Orders (SK/OK).
This document is written based on EnterpriseOne application release 9.0.
This document explains
The below relationship is to show how the system handles data, and the relationship among sales order detail, purchase order detail, and purchase order header
F4211FSEditLine: This function validates/default sales order detail information and create Sales Order Detail Cache
- F4311EditLine: Depends on option you set this function gets called by F4211FSEditLine to create Purchase Order Detail Cache
- IXTF4311Z2_CallBeginDocForNewHeaderRec(): Assignment takes place in this internal routine
- F4311BeginDoc: Based on given information in F4311EditLine it defaults and creates Purchase Order Header Cache
F4211FSEndDoc: Commit Sales Order Header/Detail Cache
As we can see above, values to Purchase Order is determined through F4211FSEditLine routine
Now we may discuss the relationship in detail.
Currently F4211FSEditLine (B4200311) calls F4311EditLine (XT4311Z2) directly to populate Purchase Order with parameter name dsPOEditLineParms in internal function I4200310_ProcessPurchaseOrderLine.
The sequence of parameters written below is based on the sequence in internal function I4200310_ProcessPurchaseOrderLine.
Important: Data Structure used in the routine (To identify the source of data)
Next, the F4311EditLine calls F4311BeginDocument to populate the Purchase Order Header based on the value handled in the Edit Line routine.
Internal function IXTF4311Z2_CallBeginDocForNewHeaderRec() in XT4311Z2 gets/assigns the data structure of dsBeginDocParms. So the column/parameter listed below is the parameter of dsBeginDocParms. A number of assignment are not used in creating purchase orders based on Sales Orders. Parameters does not have assignment in Detail for the applications P43011 or P43360.
Target Parameter on dsBeginDocParm | Source From (F4311EditLine) | Reference/Implemented By | Considerations |
---|---|---|---|
H1. szComputerID | lpDS->szCMComputerID | * Unique Cache/Work File ID | |
H2. mnProcessID | &lpDS->mnProcessID | <Bug 10691321>: CACHE SHARED WITH MULTI PROCES - SAR: 3046995 | * Unique Cache/Work File ID |
H3. mnTransactionID | &lpDS->mnTransactionID | Refer #H2 | * Unique Cache/Work File ID |
H4. cUpdateOrWriteWorkFile | 'A' | Hard Coded to 'A' for ADD | |
H5. cProcessEdits | lpDS->cProcessEdits | Refer #D3 | |
H6. cUpdateOrWriteToWorkFile | lpDS->cUpdateOrWriteWorkFile | Refer #D4 | |
H7. cCurrencyProcessingFlag | lpDS->cCurrencyProcessingFlag | Refer #D13 | |
H8. szPurchaseOrderPrOptVersion | lpDS->szPurchaseOrderPrOptVersion | Refer #D15 | |
H9. szOrderCOmpany | lpDS->szOrderCompany | Refer #D17 | |
H10. mnOrderNumber | &lpDS->mnOrderNumber | Refer #D18 | |
H11. szOrderType | lpDS->szOrderType | Refer #D14 | |
H12. szOrderSuffix | lpDS->szOrderSuffix | Refer #D23 | |
H13. szBranchPlant | lpDS->szBranchPlant | Refer #D24 | |
H14. mnSupplierNumber | &lpDS->mnSupplierNumber | Refer #D29 | |
H15. mnShipToNumber | &lpDS->mnShipToNumber | Refer #D31 | |
H16. mnCarrierNumber | &lpDS->mnCarrierNumber | Refer #D55 | |
H17. jdRequestedDate | &lpDS->jdRequestedDate | Refer #D32 | |
H18. jdOrderDate | &lpDS->jdTransactionDate | Refer #D33 | |
H19. jdPromisedDate | &lpDS->jdPromisedDate | Refer #D34 | |
H20. jdCancelDate | &lpDS->jdCancelDate | Refer #D35 | |
H21. szLandedCostRule | lpDS->szLandedCostRule | Refer #D46 | |
H22. cCurrencyMode | lpDS->cCurrencyMode | N/A | |
H23. szTransactionCurrencyCode | lpDS->szTransactionCurrencyCode | N/A | |
H24. mnCurrencyExchangeRate | &lpDS->mnCurrencyExchangeRate | N/A | |
H25. szProgramID | lpDS->szProgramID | Refer #D52 | |
H26. szPrintMessage | lpDS->szPrintMessage | <Bug 10735782>: PRINT MSG NOT ON DIRECT SHIP - SAR: 4482916 (Print Msg Not on Direct Ship Sys 43) <Bug 10907606>: SD DETAIL PRINT MESSAGE GOING - SAR: 7883088 (Rolled back the changes made by SAR 4482916 as it was incorrectly passing the detail print message from SD to the header of OD. The SAR 4482916 has to be fixed some where else so that Print message from the SD header is passed to the OD header) |
Refer #D47 Print Message is copied only for detail For header it is disabled by SAR 7883088 |
H27. szPriceAdjustmentScheduleN | lpDS->szAdjustmentSchedule | N/A | |
H28. szUserID | lpDS->szUserID | Refer #D53 | |
H29. szTaxExplanationCode | lpDS->szTaxExplanationCode | Pass original order information to header | Refer #D7 |
H30. szTaxRateArea | lpDS->szTaxRateArea | <Bug 10743192>: SUPPLIER TAX NOT USED IN PO - SAR: 4789272 (Add Tax Rate Area) | Refer #D6 |
H31. szOriginalOrderCompany | lpDS->szOriginalOrderCompany | N/A | |
H32. szOriginalOrderNumber | lpDS->szOriginalOrderNumber | N/A | |
H33. szOriginalOrderType | lpDS->szOriginalOrderType | N/A | |
H34. szRMADocType | lpDS->szRMADocType | <Bug 10740506>: OTC: POE - INTEGRATED RETURNS - SAR: 4655493 (Add RMA Doc # and Doc Type into Begin Doc Parms) | N/A |
H35. mnRMADocNumber | &lpDS->mnRMADocNumber | N/A | |
H36. szFreightHandlingCode | lpDS->szFreightHandlingCode | <Bug 10924418>: PDFRTH BLANKED AFTER PARTIAL S - SAR: 8082717 (For populating the freight handling code (FRTH) in the F4301 record for the associated OD in which the freight handling code (FRTH) entered in the SD when entering direct ship orders) | Refer #D56 |
H37. mnBuyerNumber | &lpDS->mnBuyerNumber | <Bug 12504327>: BUYER # NOT DEFAULTIN ON HEADR - SAR: 6150561 (When generating POs from Purchase Order Generator, default in Buyer Number from Item/BP) <Bug 10959726>: BUYER NUMBR NOT CARRIED OVER - SAR: 8482614 (Added an OR condition as when the PO is generated from P43360 the BuyerNumber was not copied) |
N/A Only when szProgramID is "EP43011" OR "EP43360" |
H38. cSendMethod | lpDS->cSendMethod | <Bug 10972318>: ERROR NOT DISAPPEARING WHEN LI - SAR: 8629962 (Pass send method to begin doc.) | N/A |
Refer to <Document 1390905.1> E1: 42: How to maintain Order Integrity between SD/OD and ST/OT to understand integrity checking routine between Sales and Purchase when both are tightly related.
This note is created based on EnterpriseOne application release 9.0. This note can be updated to accommodate any enhancement we put in place in the future.