Please Wait a Moment
X

Infor LX Tips, Infor LN Tips, BPCS Tips, Baan Tips, Infor M3 Tips & Infor ERP News

Crossroads Connections

Infor ERP Tips & News from the Experts

Infor LX | Infor LN | BPCS | Baan | Infor M3

Infor LN & Baan Tip: Did you know? PBOM – Effective Dates
Kathy Barthelt

Infor LN & Baan Tip: Did you know? PBOM – Effective Dates

Materials and Manufacturing

Did you know? PBOM – Effective Dates

Some customers have noticed that when a PBOM is pushed from Engineering to Production, the effective date of the PBOM component lines does not match the effective date of the revision of the PBOM component.

Here is how it works:

1. The effective date on a PBOM line is the date the item became effective in PBOM. This means that if the parent item is revision controlled, the effective date on the line relates to one of the revision dates of the parent item.
2. The effective date in a PBOM can be changed. This will lead to a disconnect between engineering and PBOM dates.
3. The a PBOM line can have a revision. However, the effective date on the PBOM line is not the effect of the revision of this component.

Previous Article Crossroads RMC's support team is friendly, well trained, experienced, and committed to resolving your support & technical issues as quickly & effectively as possible.
Next Article Infor LN & Baan Finance Tip: How to clear balances on invoices that will be moved to a new company
Print
63416 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

To utilize the Security Rules Optimization feature, a system administrator can assign security codes to 100 pre-defined user groups. User groups are created in the Group Security Maintenance (SYS603) program. All users assigned to this group possess the same level of security.   

A system administrator can assign security codes for up to 100 of the user groups. All user groups over 100 are still administered by all security reject/allow rules assigned to them but are not able to utilize the optimized process. 

Each of the security codes and access levels are assigned to user groups and are mapped to the account strings and stored in the Account Cross Reference (CEA106D1) file.   

Once security codes have been assigned, the system administrator must: 

  • Determine which level each group is allowed access.

  • Determine which segment values/account strings are assigned to which user groups.

  • Create security rules for specific segment values/account strings and assign these groups to the created rules.

  • Select the rules to be processed.  Processing can be done in either batch mode or interactively.

  • The Security Rules flag must be on in the CEA Control Parameters program before any rules are effective. 

This feature provides a parameter that allows the user to enter expiration dates on the Inventory Transaction Posting screen, INV500, and Purchase Order Receipts screen, PUR5505, when they have received a lot controlled item that is not QMS controlled. This new field allows an expiration date to be entered and not overridden. A system parameter was added to Advanced Process Industries Parameters, API820D. When the parameter is set to Yes, a new lot expiration date is available in the Inventory Transaction Posting, INV500D2, and Purchase Order Receipts, PUR550D2, screens.

FirstLast

Tips: LN | Baan

Categories