Infor LN SettingsBOD Triggering BOD publishing is triggered from the initial-load sessions, and from other business processes. For BOD-specific triggering, refer to Chapter 6. General As described in the Infor LN- ION Integration Guide, Infor LN BOD publishing uses a staging mechanism. Using the BOD Implementation Registration (bobod1100m000) session, you can enable the staging for master data BODs. However, you cannot enable staging for the transactional BODs that are part of the LN - PCL integration. An exception is made for ProjectBudget, which is a transactional BOD and must use staging. For recommended staging settings and frequencies, refer to Chapter 6. ProjectBudget ProjectBudget publishing always uses the staging mechanism. The end user cannot change the staging option for this object. Staging of ProjectBudget BODs is triggered when a project is activated, and when the Generate Control Data (tpptc1230m000) session has resulted in project changes. To publish the staged BODs, you must run the Publish Staged BODs (bobod2200m000) session. It is recommended that you place the session in a job, and run this job with a frequency required for PCL reporting. LnContractLineBillingDate For PCL reporting, billing dates are published by contract line, and project. Based on the last and nearest billing dates, PCL calculates the to-be-billed amounts, due and overdue. After completing each billing cycle, the last and next billing dates are changed. Therefore, the LnContractLineBillingDate BOD must be published with a frequency that is equal to the billing frequency. The recommended BOD publishing frequency is 2 times the billing frequency. LN publishes each open contract line that must be billed, according to the particular billing cycle. A single BOD message is generated for each contract line. The LnContractLineBillingDate BOD is published from the Publish Billing Dates (tpbod5230m000) session, which is the alternative option. It is recommended to create various continuous jobs for this session, by a range of billing cycles that have the same billing frequency. This results in various jobs that are automated and have different running frequencies. The LnContractLineBillingDate publishing must be enabled for all active billing cycles, regardless of the frequency; this is relevant for both reporting and alerting purposes. If a billing cycle, that is linked to an open contract line, is complete, the last billing date of the billing cycle must be published for reporting purposes. Note The LnContractLineBillingDate publishing must be enabled for all active billing cycles, regardless of the frequency. If a billing cycle, linked to an open contract line, is complete; the last billing date of the billing cycle must be published for overdue billing figures in PCL.
| |||