Skip navigation

The majority of MRP service requests received for 2016, pertain to issues within the Branch Plant Relationship (P3403) table. While troubleshooting the Branch Plant Relationship Table, we have come across a startling revelation. The Effective Thru Dates for each branch record contains the Effective Thru Date of 12/31/20.

 

We all know that 2016 is in full swing but can you believe that in just four short years, 2020 will be here? Who remembers back in the 1980's when the manufacturing data dictionary item #CYR (Century Change Year) was implemented to be used as the default for the Effective Thru Date fields? When data dictionary field #CYR contains the value of 20, Effective Thru Dates default to 12/31/20 when this field is left blank. Back in the 1980's when 2020 was the default, we had 30+ years to update the #CYR field. Or, so we thought. The majority of service requests entered still display Branch Relationship Revisions with the Effective Thru Date of 12/31/20.

 

Multi-Plant MRP (P3483) contains processing option 3 in each dream writer version where planning horizon periods are defined. The periods are defined in days, weeks and months. The maximum number of periods in any combination cannot exceed 52 periods. So, let's say that 52 months are added with no days or weeks. This takes MRP out to June 2020. Should the Effective Thru date in Branch Plant Constants contain 12/31/20 as the Effective Thru Date, the branch plant relationship line is only good for another 8 months which is too close for comfort.

 

Back in 2010, JDE introduced a program Effective Thru Date Update (P4028) that runs over 70+ data files where Effective Thru Dates and Expiration Dates are changed for Manufacturing and Distribution programs. The data dictionary field #CYR can be changed to the year of your choice as long as you follow the 100 year rule principal. When running the P4028, the files listed in UDC 40/EF are updated to include a new Effective Thru Date so that your data does not expire.

 

Even though this program has been available for many years, we still see customers that have not run the Effective Thru Date Update. The sooner that this program is run, the less likely issues will exist with invalid Effective Thru Dates and Expiration Dates in Distribution.

 

As a reminder Effective-Thru Dates and #CYR (P4028) (Doc ID 656831.1) explains what this program does for both Manufacturing & Distribution files.

 

Branch Plant Relationships contain default values when adding new relationships, the following information will default if left blank:

  • The Effective From date defaults to today's date     
  • The Effective Thru date defaults to December 31 and reads #CYR for the default year.     
  • The level for the component branch defaults to one  more than the level from the header for the source branch.                                              

 

Keeping your setup tables/files current avoids any future problems where data is no longer valid.


For more information see Branch Plant Relationships P3403 (Doc ID 782525.1).

The Preferred Cost Center Preference allows the default of a detail Branch Plant (BP) on the sales order detail line based on preference profile set up.

 

Isn’t this Inventory Commitment Preference Profiles? It is, but it is specifically meant only to do the following:

  1. Default a Preferred BP for any given product at the sales order detail level regardless of the availability of an item.
  2. Default a Preferred BP in the detail even if the item does not exist on the header BP.

 

This preference:

  1. Does not exist on Preference Profiles P4007 set up. It uses the set up for Inventory Commitment Preferences.
  2. Must be flagged on the Preference Selection P40400 batch program.
  3. The version of the P40400 must be attached to sales order entry P4211 to preference the BP.

 

For more on using a slimmed down version of preferred cost center for sourcing inventory read document Preference Profiles in Sales(Doc ID 626656.1) / section Preferred Cost Center.

Once again, a new year is upon us. It is already 2016. We know that a new year is here and now, human intervention is required to inform the manufacturing programs of this as well. Several manufacturing functions require up to date calendars in manufacturing. An example of this is:

 

     Backscheduling: Work Orders perform back scheduling in order to calculate the correct start date to begin production.

     Lead-times:         Lead-time calculations are performed which depends on Shop Floor Calendars existing and being up to date.

 

Manufacturing requires calendars to be set up five years in the future along with two years back. Since it is already 2016, adding five years takes your calendars out to 2021.

 

To check if your calendars are up to date the menu, Shop Floor Control Setup (15/G3141) can assist you. Simply inquire on your branch plant along with the calendar month of 01 and year 2016 and begin paging down. Confirm that every month in 2016 displays a calendar through 2021. Should the calendar not exist, a message displays at the bottom of the Shop Floor Calendar screen (P0071) stating: Enter key must be pressed to add record.

 

For customers operating A92 and above, you have access of pressing the F5 function key to call the Calendar Generation (P0007G) program. The days of adding calendars one at a time is gone. The Calendar Generation program can add as many calendar years as you want. Enter the From month/year and update the Thru month/year to any year of you liking. For example, select to run the Calendar Generation program for 01/2016 through 12/2021.

 

Remember to add your work days as code W, Holiday's as code H and shut down as an S in your calendars. This way, backscheduling will not include a holiday when calculating work order start dates. If using Calendar Generation, add a normal calendar and then access the calendars that need some tweaking for holidays or shut down days.

 

Adding the calendar information ensures that your work order start dates calculate with a valid start date. Also, when running any MRP program such as Single Plant (P3482) or Multi-plant (P3483)following the rules of calendars five years out and two years back eliminates error JDE3401 - Errors occurred calculating the dates required for MPS/MRP/DRP processing, which seems to hide in an MRP job log.

 

More information can be located on P00071 Shop Floor Calendar Setup and Use (Doc ID 631273.1) and Work Day or Shop Floor Calendar and Branch Plant 'ALL' (Doc ID 813265.1).

Did you know that as of Worldsoftware Release A9.3, you can now incorporate costs from the Cost Revisions file (F4105) into a formula based adjustment?

  • When you set up a formula based adjustment in Price Adjustment Detail (P4072) you are now required to input a Cost Method.
  • You use field COUNCS to reference an F4105 cost in a formula.
  • The system knows to retrieve a cost from the F4105 based on the Inventory Cost Level assigned to the item in Item Master Information (P4101).


In addition, there are opportunities for you to incorporate sales order unit price (SDUPRC) into a formula, the value now retrieved is the most recent net price for the sales order line. Clients on A9.3 who want SDUPRC to represent base price can change the field to SDLPRC (list price).

  • Increased Security for Cost and Price Information
  • New Advanced Pricing Report
  • Improved Calculations and Formulas
  • New Functionality for Free Goods
  • Added Flexibility for Reprice Adjustments
  • Better Visibility for Rebates
  • Improved Usability

 

Given the new Increased Security for Cost and Price Information you’ll need to find another way to spend your time, instead of worrying.  Many the concerns can now be alleviated with the ability to do the following.

  • Suppress cost related fields in Customer Service Inquiry
  • Suppress price related fields in Customer Service Inquiry
  • Suppress cost related fields in Check Price & Availability
  • Set “No Base Price in Effect” Notification at Order Entry


To further put your mind on easy street, and eliminate the guesswork, you can now generate a report displaying the end price for each of your items after price adjustments are applied. The report also displays the individual adjustments used to derive the end price for each item. While you’re taking it easy make sure you rest your fingers and allow the system to print prices by customer, customer group, or by item for you.  Lastly don’t doubt for a moment that all this convenience can be yours even in conjunction with the Electronic Document Delivery system and BI Publisher.

 

Check out the added flexibility of our versatile World A9.3 Advanced Pricing functionality!  See World A9.3 Enhancements to Advanced Pricing(Doc ID 1451682.1).

calendar.jpgFiscal year end is approaching and your business objective is to process all reported activity for Work Orders during the current fiscal year to result in a 'balanced' cutover in Manufacturing Accounting, and, start the new fiscal year with new costs for new WO activity reporting.

 

When and the frequency to change frozen manufacturing and inventory costs is a business decision.  However, bad timing in the execution of the final cost change could create unwanted WIP variances and imbalances between inventory values and the corresponding accounts in the General Ledger.


Unwanted and unexpected Work Order Variances, (Planned, Actual and Other) can be produced due to frozen cost changes done to items in ‘open’ Work Orders. So, it is clear now that before a cost update first you need to process open and partially completed work orders that have pending accounting activity not yet reported in the books (unaccounted units).
By generating and posting these transactions, before a final cost change, you’ll process the manufacturing journal entries at the same cost that was used to report the work order hours and your inventory activity in the Cardex.  Manufacturing Accounting will clear the unaccounted fields and the Work Order Production file will be ready to be used by the Work Order Variances program to generate the calculated IV transactions.

 

It never hurts to review, re-evaluate or change the steps of your yearly process. It is a good opportunity for brainstorming and sharing some best practices and considerations with your team.  Many of the steps delimited you may already be familiar with when you upgraded. The main objective was and is to ensure a ‘clean’ cutover in Manufacturing Accounting.  Review our previous blog Upgrade Best Practices for Discrete Work Orders  – JD Edwards World  as well as section "Planning a Mass Cost Update" in Standard Cost Simulation (P30820), Cost Update (P30835) and WIP Revaluation (P30837) in A8.1, A9.1 Onward (Doc ID 1541652.1).

 

Remember, a ‘closed work order’ term and status in manufacturing is driven by the value updated in field Variance Flag (PPFG) stored in the Work Order Header file.  Yes, the Work Order status plays a role too as it informs users what stage has been completed during the work order activity reporting.  However, the manufacturing accounting programs and some reports will validate the PPFG value to confirm if a WO has been fully completed, processed and ‘closed’ in the General Ledger.  While the WO status field in the header can be easily changed by a user aside programs setup to do so, if the variance flag is not set to a closed status, for the system this order is still considered open and active, even if the status in the header is 99.  For a better understanding of this concept, review Purpose of the Variance Flag (PPFG) In Manufacturing (Doc ID 661187.1).

Reporting for the Affordable Care Act (ACA) is just around the corner.  Here are a few things you should know:

 

Centralized Information Repository
JD Edwards World and EnterpriseOne have created a centralized knowledge document to assist in providing you information pertaining to ACA. Refer to JD Edwards EnterpriseOne and World – Affordable Care Act Overview (Doc ID 2038044.2) before logging a service request as this document just might answer your questions!


Service Request Create
In the event you need to enter an SR, please ensure that the Product and Component (Problem Type) are correct.  You should enter:

Product = Human Resources Management

Component (Problem Type) = Affordable Care Act


Advisor Webcasts
Register for the next Advisor Webcast:  Affordable Care Act - Preparing for Reporting for EnterpriseOne (December 15th)  and World (December 9th).

https://blogs.oracle.com/supportportal/resource/banners/banner-monday-mix-1b.jpg
https://blogs.oracle.com/supportportal/resource/backgrounds/email-shadow-gradient.gif

Relax, Kick Up Your Feet, Network

Join us for a fun and relaxing happy hour at the annual My Oracle Support Monday Mix. This year's gathering is Monday, October 26 from 6:00 to 8:00 p.m. at a new location—Fang Restaurant—a half-block from Moscone Center on Howard Street.

After a busy day at Oracle OpenWorld, take a break and unwind with your peers. Stop by and get to know the Oracle Support Engineers you depend on, as well as key Oracle Support executives and developers over drinks and hors d'oeuvres at Fang—a family owned restaurant known for its exciting and seasonal fare.

Admission is free for Premier Support customers with your Oracle OpenWorld badge.

Visit the Monday Mix event web site for more details. We'll see you there!

When:
Monday, October 26, 2015
6:00 - 8:00 p.m. PT

Where:
Fang Restaurant
660 Howard St. @ 3rd St.
San Francisco, CA

Fang logo

Fang logo used with permission.

Have you struggled for a solution to error message 0027 - User Defined Code Error?  If so, you're not alone. Customers often log service requests and perform searches to understand and troubleshoot this error.

 

The challenge with the 0027 - User Defined Code Error which states: “The entered code was not found in the User Defined Codes” is that the Item/Account Number (UITM) or Description (DSC1) field is highlighted and neither field is associated to a user defined code (UDC).  Due to this you do not know which UDC is in need of correction.

 

Troubleshooting Voucher Match (P4314) (Doc ID 1531063.1) provides help with this issue. Section D. Error 0027: User Defined Code Error explains that this issue is new to the A9.2C1 release, and occurs when one of the address book category codes assigned to the supplier is not valid. Document 1531063.1 provides step by step instructions on how to identify and update the UDC table in error so the error is no longer given. The document also contains information about a list of UDC tables that do not contain blank as a valid value.  Adding the “blank” value to these tables may also help correct the 0027 error issue from occurring in the future.

https://blogs.oracle.com/supportportal/resource/banners/banner-stars-bar-1.jpg
https://blogs.oracle.com/supportportal/resource/backgrounds/email-shadow-gradient.gif

Ask Questions, Attend a 10-minute Briefing, Get Entered for Prizes

Visit us October 26–28 in the Moscone West Exhibition Hall, booth 3361 for answers to your toughest support questions. Senior support engineers will be on hand spanning all major Oracle product areas, from systems and database products to middleware, applications, and Oracle Cloud.

While there, take advantage of our 10-minute mini-briefings for tips on maintaining, supporting, and upgrading Oracle products. All mini-briefing attendees are entered to win on-the-spot prizes.

Visit the Stars Bar and Mini-briefing website for more information.

Don't miss it!

Where:
Moscone West, Booth 3361

When:
October 26 and 27 (Mon & Tues)
10:15 a.m. to 6:00 p.m. PT
October 28 (Weds)
10:15 a.m. to 4:15 p.m. PT

https://blogs.oracle.com/supportportal/resource/banners/banner-general-support-services-1.jpg
https://blogs.oracle.com/supportportal/resource/backgrounds/email-shadow-gradient.gif

Come See Us in the Heart of Oracle OpenWorld

More than 500 experts from across Support Services will be on hand at Oracle OpenWorld from October 25–29 to share tips and tools for adopting and optimizing Oracle technology.

Take advantage of 50+ sessions to gain valuable insights into getting the most out of your hardware and software. Learn best practices and customer examples from Oracle Consulting, and develop sharper strategies that drive innovation and create value to meet today's changing business requirements.

Where:
Moscone West, Moscone South, Palace Hotel

When:
October 26–29, 2015

What to Look For:

  • DEMOgrounds for your products
  • Oracle University trainings on Sunday, Oct. 25
  • The My Oracle Support Monday Mix on Oct. 26
  • And more!

It is fall and most of us are dreaming of that steamy pumpkin pie and apple cider. It is also toward the end of the calendar year so it is time to clean up payroll data for end of year. This process is similar to deep cleaning your house. We all know that if we pick things up daily, then when the deep cleaning time occurs, there is less work to be done. The same is true with cleaning payroll data prior to the end of the year. This way, when you are ready to process your year end for your employees, the data will be squeaky clean.

 

Why would your payroll data need cleaning? There are many reasons that your data might be out of sync:

  • You might have made an adjustment to a certain employee records and now the summary/detail files are no longer the same.
  • You might have acquired a new company and processed payroll prior to receiving the corporate tax ID. Now you have history records with blank/incorrect tax ID and one with the correct tax ID. 
  • The infamous power outage right in the middle of your final update of your payroll might have caused the out of sync in some of the history files.
  • You created a manual check and you overrode the taxes but the gross wages didn’t come across to history the way you wanted. Just to list a few.


How can you find out if your data need cleaning?


There are a few integrity reports you can run to identify the errors for your data.

  • For U.S. payroll, access the Data Integrity & Global Updates located on menu G0731. Create and run both of these integrity reports: Taxation History F06136 (067011) and Payroll Month PDBAs F06146 (067021).
  • For Canadian payroll, access the Data Integrity & Global Updates located on menu G7731.  Create and run both of these versions: Taxation History F0713 (J077011) and Payroll Month PDBAs    F06146 (J077021). Additionally, Canadian payroll also has an EI (Employment Insurance) integrity report that you can run on menu G77311.


These integrity reports will provide you with a list of errors if any discrepancies are found. If no errors are produced, then your data are clean. If you need to know what each of the errors means or how to correct the errors, please see Payroll Tax History Integrity Report (Doc ID 645601.1) for more detail.

If your fiscal year-end is fast approaching, you might want to review information pertinent to encumbrance/commitment accounting as it pertains to the JDE World software.

 

An encumbrance accounting system allows you to reserve budgeted funds for outstanding obligations. In the World Procurement system, an encumbrance is represented by an open purchase order or contract. Since funds are typically expended on a fiscal year basis, an encumbrance should be negated (relieved) in the same fiscal year in which it was encumbered.

 

The terms ‘commitment’ and ‘encumbrance’ are interchangeable in the World Procurement applications. The term commitment is typically used for non-stock purchasing or managing contracts. The term encumbrance is typically used in conjunction with services and expense based purchasing.

 

The system tracks encumbrances and actual amounts logged against each pertinent account number for the fiscal year to determine the remaining budget available.

 

Encumbrances versus Actual Amounts, points to remember:

 

  • An encumbered expense is one that pertains to an ‘open’ purchase order. Encumbered amounts are tracked in the Account Balances file (F0902) using a ‘PA’ ledger type.
  • An actual expense is one that represents an actual cost incurred. Actual amounts are tracked in the F0902 using an ‘AA’ ledger type.
  • An encumbered amount becomes an actual amount when a purchase order is either:
    • Received via the Enter Receipts program (P4312) using a 3-way match and the resulting batch is posted
    • Matched to the invoice using the Voucher Match program (P4314) via a 2-way match and the resulting batch is posted.

 

Encumbrance dates to remember:

 

  • An expense is encumbered as of the G/L Date entered on the purchase order line.
  • An encumbrance is relieved as of the G/L Date assigned to the journal entries created at P4312 or P4314 (as of the A9.1 release), OR as of the date the purchase order is cancelled.

 

The cancel date for a purchase order line is recognized as the date the cancellation occurs. However, the cancel date is not maintained in any file. If you run the repost, the commitment date is used as the cancel date.

 

When encumbrance amounts display incorrectly on the Commitment Information (P40230), OR Budget Comparison (P43121) videos, you may want to run the purge, rebuild and repost processes to recalculate the amounts. For more information about these processes, see Commitment/Encumbrance Accounting (Doc ID 626811.1).

 

At fiscal year-end you must either close or rollover all open purchase orders to the next fiscal year. The Encumbrance Rollover program (P4317) is an automated batch process you can use to:

 

  • Cancel all open purchase order lines in the prior year.
  • Roll over open purchase order lines and amounts from the prior fiscal year to the new year.

 

For information about P4317, please see Encumbrance Rollovers (Doc ID 626672.1). Important changes to the program were made in the A9.3 release. For information regarding the changes, please see doc ID 1908390.1 – Program Changes for Encumbrance Rollover.  As well, a 2014 archived webcast is available titled JD Edwards World: Reviewing Encumbrance Rollover (P4317) & Program Changes in Release A9.3 Update 1 (Doc ID 1455377.1).

No one wants to sit in the office trying to reconcile the payroll bank account, marking off each of hundreds of paychecks against your statement. 


It’s summer time!   Get outside to enjoy the weather! 

Let Positive Pay come to the rescue...        super_hero_lifting_text_12717-400x400.jpg

 

We know that managing check fraud risk and reducing exposure to fraud is more important than ever to today's payroll managers. The Payroll Positive Pay process is an optional process that creates a work file with data for each payroll check printed in the payroll system.


This work file is then used to generate a bank transmittal file which is sent to your company's financial institution to be used for check verification. Financial institutions have a variety of Positive Pay file formats and the file generated by this process will meet the basic requirements for most financial institutions.


For complete information on creating the Positive Pay file, see Positive Pay for Payroll Checks (Doc ID 2018511.1)


So get out and play and leave the work to Positive Pay!

Vertex is a 3rd party tax system that links to JD Edwards. The geocode from Vertex indicates what tax should be applied to a transaction. This can be a straight tax or a tax with a Tax Decision Maker table (TDM table) applied.

 

If you run Vertex Sales Tax with JD Edwards World (JDE) for your taxes and transact internationally, you may wonder how the system handles taxes with foreign entities. Foreign Entities means any business outside of the U.S. and Canada. So... what about those ‘foreign entities’ and their taxes? How does Vertex handle this set up?

 

Vertex does not define GeoCodes for non-U.S. or non-Canadian jurisdictions and does not maintain tax rates for these jurisdictions. You will need to know the correct tax rates for the rest of the world but you can add this information into Vertex. Vertex allows the creation of foreign GeoCodes, each beginning with value = 77 (in the state part). Once a geocode is set up, a Vertex Override table to maintain tax rates for each foreign taxing authority may be added to the Vertex system.

 

For a simple overview on setting up a TDM for Override Table review Vertex: TDMs (Tax Decision Maker) (Doc ID 626692.1). To understand TDM set up with foreign entities more fully contact Vertex Support. The customer support number for Vertex is 800.281.1900. 

taxes.jpgDoes it feel like Vertex tax updates are weighing you down? 

 

Did you know the new Vertex 4.1 update applies to 4 specific states:  Iowa, Missouri, Oregon & Alabama?  You only need the JD Edwards update along with Vertex 4.1 if you do business in one of these states AND process multi-state payrolls.  If you only process payrolls for a single state, you do not need the JD Edwards update at this time.

 

If the above DOES apply to your business needs…..JD Edwards can help with that heavy load! 

 

We have software updates for A9.2, A9.3 & A9.4 to accompany the Vertex 4.1 update.  Don’t feel like applying a software update?  Try one of the code changes instead.

 

See Vertex 4.1 Compatibility with JD Edwards Releases (Doc ID 2022493.1) for the update and code change numbers for each release.

 

Also check out A9.3/A9.3.1 HCM Updates (Doc ID 1465468.1) for a list of all available updates for each release.

Welcome to the My Oracle Support Community! We highly encourage you to personalize your community display name to make your activity more memorable. Please see https://community.oracle.com/docs/DOC-1022508 for instructions.